{"6105":{"script_id":"6105","0":"6105","script_name":"difffilter","1":"difffilter","script_type":"utility","2":"utility","summary":"Selectively compare lines as you want in diff","3":"Selectively compare lines as you want in diff","description":"The standard \"diff\" command supports \"--ignore-matching-lines=regexp (-I regexp)\" option to ignore hunks. This plugin provides similar functionality but tries a line-level filtering based on regexp and other matching criteria.\r\n\r\nFor details and demo samples, please visit the following git repository: https:\/\/github.com\/rickhowe\/difffilter.","4":"The standard \"diff\" command supports \"--ignore-matching-lines=regexp (-I regexp)\" option to ignore hunks. This plugin provides similar functionality but tries a line-level filtering based on regexp and other matching criteria.\r\n\r\nFor details and demo samples, please visit the following git repository: https:\/\/github.com\/rickhowe\/difffilter.","install_details":"Install 'rickhowe\/difffilter' by using your plugin manager. Or manually unzip and copy all folders in your ~\/.vim or ~\/vimfiles.","5":"Install 'rickhowe\/difffilter' by using your plugin manager. Or manually unzip and copy all folders in your ~\/.vim or ~\/vimfiles.","first_name":"Rick","6":"Rick","last_name":"Howe","7":"Howe","releases":[{"0":"6105","vim_version":"9.0","1":"9.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"difffilter1.0.zip","4":"difffilter1.0.zip","src_id":"28675","5":"28675","creation_date":"1713531959","6":"1713531959"}]},"6104":{"script_id":"6104","0":"6104","script_name":"fancyterm.vim","1":"fancyterm.vim","script_type":"utility","2":"utility","summary":"Simple plugin that allows sending buffer text into an active terminal.","3":"Simple plugin that allows sending buffer text into an active terminal.","description":"fancyterm is a simple plugin that helps with sending entire buffers\r\nor just lines or selections into repls or shells\r\n\r\nfancyterm isn't actually as fancy as some more advanced live-repl\r\nenvironments, but because it aims to be somewhat universal, it works\r\nwith many repls\/shells out of the box, without any extra configuration.\r\n\r\nSo it can easily become a quick-and-easy way to start a live-repl programming\r\nsession.\r\n\r\nDemo video:\r\nhttps:\/\/www.youtube.com\/watch?v=j8QnTPhQMKo","4":"fancyterm is a simple plugin that helps with sending entire buffers\r\nor just lines or selections into repls or shells\r\n\r\nfancyterm isn't actually as fancy as some more advanced live-repl\r\nenvironments, but because it aims to be somewhat universal, it works\r\nwith many repls\/shells out of the box, without any extra configuration.\r\n\r\nSo it can easily become a quick-and-easy way to start a live-repl programming\r\nsession.\r\n\r\nDemo video:\r\nhttps:\/\/www.youtube.com\/watch?v=j8QnTPhQMKo","install_details":"The official git repository can be found here:\r\nhttps:\/\/bitbucket.org\/g0zar\/vim-fancyterm\r\n\r\n\r\n\r\n# Installation\r\n\r\n## Manual installation\t\r\n\r\nCopy `plugin\/fancyterm.vim` and `doc\/fancyterm.txt` and `doc\/tags`\r\ninto a plugin directory in your runtime path\r\n\r\n## Pathogen\r\n\r\nClone the repo into `~\/.vim\/bundle\/`\r\nRun `:Helptags` to generate the tags for the help file.\r\n\r\n## Vim bulit-in packages\r\n\r\nClone the repository to path like\r\n```\r\ngit clone ~\/.vim\/pack\/plugins\/opt\/fancyterm\/`\r\n```\r\nReplace the actuall url of this repository.\r\nAnd add the following to your `.vimrc` file\r\n```\r\npackadd fancyterm\r\n```\r\n\r\nIf you don't want the default bindings you can also write right before\r\n```\r\nlet g:fancyterm_map_keys = 0\r\npackadd fancyterm \r\n```\r\n","5":"The official git repository can be found here:\r\nhttps:\/\/bitbucket.org\/g0zar\/vim-fancyterm\r\n\r\n\r\n\r\n# Installation\r\n\r\n## Manual installation\t\r\n\r\nCopy `plugin\/fancyterm.vim` and `doc\/fancyterm.txt` and `doc\/tags`\r\ninto a plugin directory in your runtime path\r\n\r\n## Pathogen\r\n\r\nClone the repo into `~\/.vim\/bundle\/`\r\nRun `:Helptags` to generate the tags for the help file.\r\n\r\n## Vim bulit-in packages\r\n\r\nClone the repository to path like\r\n```\r\ngit clone ~\/.vim\/pack\/plugins\/opt\/fancyterm\/`\r\n```\r\nReplace the actuall url of this repository.\r\nAnd add the following to your `.vimrc` file\r\n```\r\npackadd fancyterm\r\n```\r\n\r\nIf you don't want the default bindings you can also write right before\r\n```\r\nlet g:fancyterm_map_keys = 0\r\npackadd fancyterm \r\n```\r\n","first_name":"Ernest","6":"Ernest","last_name":"Deak","7":"Deak","releases":[{"0":"6104","vim_version":"9.0","1":"9.0","script_version":"2.0.0","2":"2.0.0","version_comment":"Since version 2.0.0 the default bindings have been removed.\r\nInstead, the key has been used in their place. This is because\r\nI didn't realize what was actually used for, and choose it pretty much\r\nat random.\r\nIf you set `let g:fancyterm_map_keys = 0` then this change doesn't affect you\r\n","3":"Since version 2.0.0 the default bindings have been removed.\r\nInstead, the key has been used in their place. This is because\r\nI didn't realize what was actually used for, and choose it pretty much\r\nat random.\r\nIf you set `let g:fancyterm_map_keys = 0` then this change doesn't affect you\r\n","package":"fancyterm-2.0.0.tgz","4":"fancyterm-2.0.0.tgz","src_id":"28674","5":"28674","creation_date":"1713370455","6":"1713370455"},{"0":"6104","vim_version":"9.0","1":"9.0","script_version":"1.2.2","2":"1.2.2","version_comment":"fix for TermSendCurrentLine() not expanding tabs to spaces upon sending them to the terminal\r\nfix for TermSendVisual() sending the visual selection several times","3":"fix for TermSendCurrentLine() not expanding tabs to spaces upon sending them to the terminal\r\nfix for TermSendVisual() sending the visual selection several times","package":"fancyterm-1.2.2.tgz","4":"fancyterm-1.2.2.tgz","src_id":"28672","5":"28672","creation_date":"1713204144","6":"1713204144"},{"0":"6104","vim_version":"9.0","1":"9.0","script_version":"1.2.0","2":"1.2.0","version_comment":"Tab expansion now happens based on the &tabstop global setting.\r\nFixed a bug where the current line would not be escaped before being sent to the terminal.","3":"Tab expansion now happens based on the &tabstop global setting.\r\nFixed a bug where the current line would not be escaped before being sent to the terminal.","package":"fancyterm-1.2.0.tgz","4":"fancyterm-1.2.0.tgz","src_id":"28671","5":"28671","creation_date":"1713191653","6":"1713191653"},{"0":"6104","vim_version":"9.0","1":"9.0","script_version":"1.1.0","2":"1.1.0","version_comment":"Added a command to set the active terminal via :TermSetActive","3":"Added a command to set the active terminal via :TermSetActive","package":"fancyterm-1.1.0.tgz","4":"fancyterm-1.1.0.tgz","src_id":"28670","5":"28670","creation_date":"1713183038","6":"1713183038"},{"0":"6104","vim_version":"9.0","1":"9.0","script_version":"1.0.0","2":"1.0.0","version_comment":"Initial upload","3":"Initial upload","package":"fancyterm-1.0.0.tgz","4":"fancyterm-1.0.0.tgz","src_id":"28666","5":"28666","creation_date":"1713101006","6":"1713101006"}]},"6103":{"script_id":"6103","0":"6103","script_name":"findgrep.vim","1":"findgrep.vim","script_type":"utility","2":"utility","summary":"An interactive FindGrep command to mimic emacs find-grep command","3":"An interactive FindGrep command to mimic emacs find-grep command","description":"This script provides you with a command to launch vimgrep interactively similar to emacs find-grep","4":"This script provides you with a command to launch vimgrep interactively similar to emacs find-grep","install_details":"put this in your plugin\/ directory or source it","5":"put this in your plugin\/ directory or source it","first_name":"Raveen","6":"Raveen","last_name":"Kumar","7":"Kumar","releases":[{"0":"6103","vim_version":"7.0","1":"7.0","script_version":"1","2":"1","version_comment":"Initial upload","3":"Initial upload","package":"findgrep.vim","4":"findgrep.vim","src_id":"28656","5":"28656","creation_date":"1711291572","6":"1711291572"}]},"6102":{"script_id":"6102","0":"6102","script_name":"vim-md-link","1":"vim-md-link","script_type":"utility","2":"utility","summary":"Keep long URLs out of your way in Markdown documents","3":"Keep long URLs out of your way in Markdown documents","description":"This plugin keeps long URLs out of your way in Markdown documents.\r\n\r\nIt accomplishes this by converting inline Markdown links into reference links. For instance, the following:\r\n\r\n # Notes\r\n\r\n [Vim](https:\/\/www.vim.org) and [Neovim](https:\/\/neovim.io) are text editors.\r\n\r\nwill be turned into\r\n\r\n # Notes\r\n\r\n [Vim][0] and [Neovim][1] are text editors.\r\n\r\n ## Links\r\n\r\n [0]: https:\/\/www.vim.org\r\n [1]: https:\/\/neovim.io\r\n\r\nvim-md-link adds commands for converting a single link or all links, opening a link in your browser, jumping to a link, deleting links, and more.\r\nSee https:\/\/github.com\/qadzek\/vim-md-link for the details.","4":"This plugin keeps long URLs out of your way in Markdown documents.\r\n\r\nIt accomplishes this by converting inline Markdown links into reference links. For instance, the following:\r\n\r\n # Notes\r\n\r\n [Vim](https:\/\/www.vim.org) and [Neovim](https:\/\/neovim.io) are text editors.\r\n\r\nwill be turned into\r\n\r\n # Notes\r\n\r\n [Vim][0] and [Neovim][1] are text editors.\r\n\r\n ## Links\r\n\r\n [0]: https:\/\/www.vim.org\r\n [1]: https:\/\/neovim.io\r\n\r\nvim-md-link adds commands for converting a single link or all links, opening a link in your browser, jumping to a link, deleting links, and more.\r\nSee https:\/\/github.com\/qadzek\/vim-md-link for the details.","install_details":"Use your favorite plugin manager to install this plugin.\r\nIf you use vim-plug: Plug 'qadzek\/vim-md-link'\r\n","5":"Use your favorite plugin manager to install this plugin.\r\nIf you use vim-plug: Plug 'qadzek\/vim-md-link'\r\n","first_name":"Qad","6":"Qad","last_name":"Zek","7":"Zek","releases":[{"0":"6102","vim_version":"8.2","1":"8.2","script_version":"0.1.0","2":"0.1.0","version_comment":"Initial upload","3":"Initial upload","package":"vim-md-link.zip","4":"vim-md-link.zip","src_id":"28651","5":"28651","creation_date":"1710693707","6":"1710693707"}]},"6101":{"script_id":"6101","0":"6101","script_name":"vim-weaselwords","1":"vim-weaselwords","script_type":"utility","2":"utility","summary":"Crafting polished prose by highlighting weasel words and passive use in Vim","3":"Crafting polished prose by highlighting weasel words and passive use in Vim","description":"Improve your writing in Vim by highlighting weasel words. The plugin highlights weaselwords in red and passive sentences in blue.\r\n\r\nFeatures\r\n Simply based on word lists that the user can edit or a community can maintain.\r\n No need to connect to the internet. Your texts stay in your editor.\r\n Experimental passive detection for English\r\n\r\nSupported Languages\r\n English\r\n German\r\n French (basic)\r\n Spanish (basic)","4":"Improve your writing in Vim by highlighting weasel words. The plugin highlights weaselwords in red and passive sentences in blue.\r\n\r\nFeatures\r\n Simply based on word lists that the user can edit or a community can maintain.\r\n No need to connect to the internet. Your texts stay in your editor.\r\n Experimental passive detection for English\r\n\r\nSupported Languages\r\n English\r\n German\r\n French (basic)\r\n Spanish (basic)","install_details":"","5":"","first_name":"Moritz","6":"Moritz","last_name":"","7":"","releases":[{"0":"6101","vim_version":"7.0","1":"7.0","script_version":"1.2.0","2":"1.2.0","version_comment":"Initial upload","3":"Initial upload","package":"vim-weaselwords-1.2.0.zip","4":"vim-weaselwords-1.2.0.zip","src_id":"28650","5":"28650","creation_date":"1710578469","6":"1710578469"}]},"6100":{"script_id":"6100","0":"6100","script_name":"sharegpt-vim-editor","1":"sharegpt-vim-editor","script_type":"utility","2":"utility","summary":"sharegpt ai ml dataset viewer\/edit jsonl json","3":"sharegpt ai ml dataset viewer\/edit jsonl json","description":"This Vim plugin provides a UI for editing JSONL (JSON Lines) files, specifically tailored for ShareGPT conversations. It includes features like navigation through JSONL entries, custom syntax highlighting, and in-place editing of JSONL data.\r\n\r\nhttps:\/\/github.com\/draganjovanovich\/sharegpt-vim-editor\r\n","4":"This Vim plugin provides a UI for editing JSONL (JSON Lines) files, specifically tailored for ShareGPT conversations. It includes features like navigation through JSONL entries, custom syntax highlighting, and in-place editing of JSONL data.\r\n\r\nhttps:\/\/github.com\/draganjovanovich\/sharegpt-vim-editor\r\n","install_details":"Plugin 'draganjovanovich\/sharegpt-vim-editor'\r\nPlug 'draganjovanovich\/sharegpt-vim-editor'\r\n","5":"Plugin 'draganjovanovich\/sharegpt-vim-editor'\r\nPlug 'draganjovanovich\/sharegpt-vim-editor'\r\n","first_name":"Dragan","6":"Dragan","last_name":"Jovanovic","7":"Jovanovic","releases":[{"0":"6100","vim_version":"8.0","1":"8.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"sharegpt-vim-editor-main.zip","4":"sharegpt-vim-editor-main.zip","src_id":"28616","5":"28616","creation_date":"1708390768","6":"1708390768"}]},"6099":{"script_id":"6099","0":"6099","script_name":"vim-chore","1":"vim-chore","script_type":"utility","2":"utility","summary":"v0.1","3":"v0.1","description":"Search for common string like 'TODO' and 'FIXME' in a large codebase and place them into the quickfix buffer\r\n\r\nOnly command is ':ChoreOpen' which performs the search","4":"Search for common string like 'TODO' and 'FIXME' in a large codebase and place them into the quickfix buffer\r\n\r\nOnly command is ':ChoreOpen' which performs the search","install_details":"Any normal installation method works\r\n\r\nGitHub repository may be useful for this: https:\/\/github.com\/jsnal\/vim-chore","5":"Any normal installation method works\r\n\r\nGitHub repository may be useful for this: https:\/\/github.com\/jsnal\/vim-chore","first_name":"Jason","6":"Jason","last_name":"Long","7":"Long","releases":[{"0":"6099","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"vim-chore.zip","4":"vim-chore.zip","src_id":"28613","5":"28613","creation_date":"1708212478","6":"1708212478"}]},"6098":{"script_id":"6098","0":"6098","script_name":"vim-gpt-commit","1":"vim-gpt-commit","script_type":"utility","2":"utility","summary":"Generate git commit message using ChatGPT in Vim","3":"Generate git commit message using ChatGPT in Vim","description":"This plugin provides a :GptCommit command to generate commit message and append in the current buffer.\r\n\r\nUsually, it can be used when editing the COMMIT_EDITMSG file, or in a fugitive commit window.\r\n\r\nSee the GIF: \r\nhttps:\/\/skywind3000.github.io\/images\/p\/misc\/2024\/gptcommit1.gif\r\n\r\nFor more information, please visit the homepage:\r\nhttps:\/\/github.com\/skywind3000\/vim-gpt-commit","4":"This plugin provides a :GptCommit command to generate commit message and append in the current buffer.\r\n\r\nUsually, it can be used when editing the COMMIT_EDITMSG file, or in a fugitive commit window.\r\n\r\nSee the GIF: \r\nhttps:\/\/skywind3000.github.io\/images\/p\/misc\/2024\/gptcommit1.gif\r\n\r\nFor more information, please visit the homepage:\r\nhttps:\/\/github.com\/skywind3000\/vim-gpt-commit","install_details":"Plug 'skywind3000\/vim-gpt-commit'","5":"Plug 'skywind3000\/vim-gpt-commit'","first_name":"Wei","6":"Wei","last_name":"Lin","7":"Lin","releases":[{"0":"6098","vim_version":"8.0","1":"8.0","script_version":"1.0.2","2":"1.0.2","version_comment":"- Refactor gptcommit.py to dynamically form the API URL based on the provided options.\r\n- Update a test case function with new URL and additional arguments.\r\n","3":"- Refactor gptcommit.py to dynamically form the API URL based on the provided options.\r\n- Update a test case function with new URL and additional arguments.\r\n","package":"vim-gpt-commit-1.0.2.zip","4":"vim-gpt-commit-1.0.2.zip","src_id":"28654","5":"28654","creation_date":"1711042026","6":"1711042026"},{"0":"6098","vim_version":"8.0","1":"8.0","script_version":"1.0.1","2":"1.0.1","version_comment":"add ollama support","3":"add ollama support","package":"vim-gpt-commit-1.0.1.zip","4":"vim-gpt-commit-1.0.1.zip","src_id":"28618","5":"28618","creation_date":"1708483388","6":"1708483388"},{"0":"6098","vim_version":"8.0","1":"8.0","script_version":"1.0.0","2":"1.0.0","version_comment":"Initial upload","3":"Initial upload","package":"vim-gpt-commit-1.0.0.zip","4":"vim-gpt-commit-1.0.0.zip","src_id":"28611","5":"28611","creation_date":"1708057246","6":"1708057246"}]},"6097":{"script_id":"6097","0":"6097","script_name":"vim-stream-editing","1":"vim-stream-editing","script_type":"patch","2":"patch","summary":"Edit text without moving your cursor!","3":"Edit text without moving your cursor!","description":"Edit text without moving your cursor!\r\n\r\nHave you ever made a typo in a word? Do you find it annoying to move your cursor or use lengthy commands to correct it? This plug frees you from boxing with annoying cursor and complex commands!\r\n\r\nGit hub link: https:\/\/github.com\/lsp59862\/vim-stream-editing","4":"Edit text without moving your cursor!\r\n\r\nHave you ever made a typo in a word? Do you find it annoying to move your cursor or use lengthy commands to correct it? This plug frees you from boxing with annoying cursor and complex commands!\r\n\r\nGit hub link: https:\/\/github.com\/lsp59862\/vim-stream-editing","install_details":"<>\r\n\r\nCopy plugin\/vim-stream-editing.vim to ~\/.vim\/plugin\r\n\r\ngit clone git:\/\/github.com\/lsp59862\/vim-stream-editing.git ~\/.vim\/bundle\/vim-stream-editing\r\n\r\nPlugin 'lsp59862\/vim-stream-editing'\r\n\r\nPlug 'lsp59862\/vim-stream-editing'\r\n\r\n<>\r\nHit (Alt+f) to use the plug in normal\/insert mode if you enabled. Then:\r\nEnter text(pattern) to modify.\r\nHit [n\/b] to choose the text.\r\nHit [i\/r\/a] to insert\/replace\/append.\r\nEnter a new text.\r\nYou can exit the process by whenever you want.\r\n\r\n<>\r\ng:vim_stream_editing_enable\r\nDefault: 0\r\nEnable this plug when set it to 1.\r\n\r\n<>\r\ng:vim_stream_editing_enable maps as the shortcut key to activate the process:\r\n\r\nnnoremap :call VimStreamEditingEditText()\r\ninoremap :call VimStreamEditing#EditText()a \r\nIf you don't want to use this key, please map the function directly and set g:vim_stream_editing_enable to 0 :\r\n\r\nnnoremap :call VimStreamEditingEditText()\r\ninoremap :call VimStreamEditingEditText()a\r\nlet g:vim_stream_editing_enable = 0\r\n","5":"<>\r\n\r\nCopy plugin\/vim-stream-editing.vim to ~\/.vim\/plugin\r\n\r\ngit clone git:\/\/github.com\/lsp59862\/vim-stream-editing.git ~\/.vim\/bundle\/vim-stream-editing\r\n\r\nPlugin 'lsp59862\/vim-stream-editing'\r\n\r\nPlug 'lsp59862\/vim-stream-editing'\r\n\r\n<>\r\nHit (Alt+f) to use the plug in normal\/insert mode if you enabled. Then:\r\nEnter text(pattern) to modify.\r\nHit [n\/b] to choose the text.\r\nHit [i\/r\/a] to insert\/replace\/append.\r\nEnter a new text.\r\nYou can exit the process by whenever you want.\r\n\r\n<>\r\ng:vim_stream_editing_enable\r\nDefault: 0\r\nEnable this plug when set it to 1.\r\n\r\n<>\r\ng:vim_stream_editing_enable maps as the shortcut key to activate the process:\r\n\r\nnnoremap :call VimStreamEditingEditText()\r\ninoremap :call VimStreamEditing#EditText()a \r\nIf you don't want to use this key, please map the function directly and set g:vim_stream_editing_enable to 0 :\r\n\r\nnnoremap :call VimStreamEditingEditText()\r\ninoremap :call VimStreamEditingEditText()a\r\nlet g:vim_stream_editing_enable = 0\r\n","first_name":"Lipsiz","6":"Lipsiz","last_name":"Terry","7":"Terry","releases":[{"0":"6097","vim_version":"9.0","1":"9.0","script_version":"V1.1","2":"V1.1","version_comment":"Fixed a Bug","3":"Fixed a Bug","package":"vim-stream-editing-main.zip","4":"vim-stream-editing-main.zip","src_id":"28607","5":"28607","creation_date":"1707731700","6":"1707731700"}]},"6096":{"script_id":"6096","0":"6096","script_name":"vim-color-export","1":"vim-color-export","script_type":"utility","2":"utility","summary":"A tool to backport NeoVim colorschemes to Vim","3":"A tool to backport NeoVim colorschemes to Vim","description":"Export current colorscheme in traditional Vim color format:\r\n\r\n1) Can export NeoVim dedicated colors to Vim.\r\n2) Can export GUI colors to terminal 256 colors format.\r\n\r\nUsage:\r\n\r\n:ColorExport ~\/.vim\/colors\/tokyonight.vim\r\n\r\nand you can use 'tokyonight' in Vim\r\n\r\nFor more information, please visit the homepage:\r\n\r\nhttps:\/\/github.com\/skywind3000\/vim-color-export","4":"Export current colorscheme in traditional Vim color format:\r\n\r\n1) Can export NeoVim dedicated colors to Vim.\r\n2) Can export GUI colors to terminal 256 colors format.\r\n\r\nUsage:\r\n\r\n:ColorExport ~\/.vim\/colors\/tokyonight.vim\r\n\r\nand you can use 'tokyonight' in Vim\r\n\r\nFor more information, please visit the homepage:\r\n\r\nhttps:\/\/github.com\/skywind3000\/vim-color-export","install_details":"vim-plug:\r\n\r\nPlug 'skywind3000\/vim-color-export'\r\n\r\n","5":"vim-plug:\r\n\r\nPlug 'skywind3000\/vim-color-export'\r\n\r\n","first_name":"Wei","6":"Wei","last_name":"Lin","7":"Lin","releases":[{"0":"6096","vim_version":"8.0","1":"8.0","script_version":"1.0.1","2":"1.0.1","version_comment":"- remove highlight group contains @ character.\r\n- minor fixes.","3":"- remove highlight group contains @ character.\r\n- minor fixes.","package":"vim-color-export-1.0.1.zip","4":"vim-color-export-1.0.1.zip","src_id":"28604","5":"28604","creation_date":"1706842775","6":"1706842775"},{"0":"6096","vim_version":"8.0","1":"8.0","script_version":"1.0.0","2":"1.0.0","version_comment":"Initial upload","3":"Initial upload","package":"vim-color-export-1.0.0.zip","4":"vim-color-export-1.0.0.zip","src_id":"28602","5":"28602","creation_date":"1706806677","6":"1706806677"}]},"6095":{"script_id":"6095","0":"6095","script_name":"vim-color-patch","1":"vim-color-patch","script_type":"utility","2":"utility","summary":"Load colorscheme patch script automatically after \":color xxx\" command !! ","3":"Load colorscheme patch script automatically after \":color xxx\" command !! ","description":"I usually like to make some modifications for the colorschemes I love to match my personal preference. In the past, I had three options:\r\n\r\n1) Creating a PR for that colorscheme: It's my own preference, and I don't think it's likely to be accepted.\r\n2) Maintaining my own fork: I need to track the upstream updates myself.\r\n3) Writing ad hoc code for different colors in my .vimrc: Ugly.\r\n\r\nTherefore, I created this plugin to centralize all colorscheme patches in one place, typically in my dotfiles repository, and have them load automatically when I type :color xxx .\r\n\r\nFor more information, please visit the homepage: \r\nhttps:\/\/github.com\/skywind3000\/vim-color-patch","4":"I usually like to make some modifications for the colorschemes I love to match my personal preference. In the past, I had three options:\r\n\r\n1) Creating a PR for that colorscheme: It's my own preference, and I don't think it's likely to be accepted.\r\n2) Maintaining my own fork: I need to track the upstream updates myself.\r\n3) Writing ad hoc code for different colors in my .vimrc: Ugly.\r\n\r\nTherefore, I created this plugin to centralize all colorscheme patches in one place, typically in my dotfiles repository, and have them load automatically when I type :color xxx .\r\n\r\nFor more information, please visit the homepage: \r\nhttps:\/\/github.com\/skywind3000\/vim-color-patch","install_details":"vim-plug:\r\n\r\nPlug 'skywind3000\/vim-color-patch'\r\n","5":"vim-plug:\r\n\r\nPlug 'skywind3000\/vim-color-patch'\r\n","first_name":"Wei","6":"Wei","last_name":"Lin","7":"Lin","releases":[{"0":"6095","vim_version":"8.0","1":"8.0","script_version":"1.0.1","2":"1.0.1","version_comment":"improve compatibilities for vim 8.0.x","3":"improve compatibilities for vim 8.0.x","package":"vim-color-patch-1.0.1.zip","4":"vim-color-patch-1.0.1.zip","src_id":"28615","5":"28615","creation_date":"1708268118","6":"1708268118"},{"0":"6095","vim_version":"8.0","1":"8.0","script_version":"1.0.0","2":"1.0.0","version_comment":"Initial upload","3":"Initial upload","package":"vim-color-patch-1.0.0.zip","4":"vim-color-patch-1.0.0.zip","src_id":"28598","5":"28598","creation_date":"1706521270","6":"1706521270"}]},"6094":{"script_id":"6094","0":"6094","script_name":"FixUp-GetLatestVimScripts","1":"FixUp-GetLatestVimScripts","script_type":"patch","2":"patch","summary":"after\/ plugin that fixes settings for stock GetLatestVimScripts.vim plugin","3":"after\/ plugin that fixes settings for stock GetLatestVimScripts.vim plugin","description":"An after\/ plugin that works as a patch, to setup paths and settings for the stock GetLastestVimScripts.vim plugin.\r\n\r\nGetLatestVimScripts is a long time out-of-date plugin, that has always shiped with Vim, and is still in the oficiall documentation, to provide basic plugin management functions in Vim:\r\n - download plugins listed in GetLatest\/GetLatestVimScripts.dat file\r\n - optionally auto-install or update plugins after download, if plugins are marked as such in the .dat file, or the author marks them as auto-installable\r\n\r\nThe stock plugin stopped working a long time ago, and it must have been never used since, because the hard-coded ! download URL Vim scripts has since changed, and the old one no longer works.\r\n\r\nThis patch plugin tries to fix the issues, as follows:\r\n - add wrapper script around curl command, to replace the old URL with the new one\r\n - add support to install vimball archives with the newer .vmb extension (transparently rename it to .vba instead)\r\n - several fixes for Windows OS, where the stock plugin was likely never working:\r\n - add wrapper scripts for external tools like gunzip, bunzip2, unxz ... that internally invoke 7-zip\r\n - 7-zip is a requirement for this plugin on Windows\r\n - fix default values set by the plugin in global variables.\r\n - the default tar command provided by Windows may still be unable to unpack some archive types like .taz, .txz ...\r\n Instead, users should install a proper version of tar command and put it on PATH.\r\n - open a new tab page the first time :GetLatestVimScripts command is used, to prevent some issues with the stock plugin\r\n during installation\r\n\r\nThere is no configuration and no command you need to run to use this plugin. You only install this plugin and then use the stock :GetLatestVimScripts (:GLVS) command, and the known fixes will be applied at auto-loading time of the old plugin.\r\n\r\nOn Linux you should run the main :GLVS command in an empty Vim window, to prevent other issues, resulting in E36 \"Not enough room\" (for new windows) in Vim.\r\n\r\nPerl is needed for Linux, and PowerShell + 7-zip for Windows.\r\n\r\nBeware GetLatestVimScripts only provides a very basic plugin management function, most users should use a more popular plugin manager instead, like Vundle, Plug or Pathogen....\r\n\r\nAfter installation make sure the after\/ subdirectory, under the local runtime directory, is appeneded to &runtimepath option. It should be there by default, but append it manually if needed, in the local vimrc file.\r\n\r\nNote the current version of stock GetLastestVimScripts plugin provided by Vim is ahead of the online versions on vim.org and github. So for now do not use GLVS to update GLVS.","4":"An after\/ plugin that works as a patch, to setup paths and settings for the stock GetLastestVimScripts.vim plugin.\r\n\r\nGetLatestVimScripts is a long time out-of-date plugin, that has always shiped with Vim, and is still in the oficiall documentation, to provide basic plugin management functions in Vim:\r\n - download plugins listed in GetLatest\/GetLatestVimScripts.dat file\r\n - optionally auto-install or update plugins after download, if plugins are marked as such in the .dat file, or the author marks them as auto-installable\r\n\r\nThe stock plugin stopped working a long time ago, and it must have been never used since, because the hard-coded ! download URL Vim scripts has since changed, and the old one no longer works.\r\n\r\nThis patch plugin tries to fix the issues, as follows:\r\n - add wrapper script around curl command, to replace the old URL with the new one\r\n - add support to install vimball archives with the newer .vmb extension (transparently rename it to .vba instead)\r\n - several fixes for Windows OS, where the stock plugin was likely never working:\r\n - add wrapper scripts for external tools like gunzip, bunzip2, unxz ... that internally invoke 7-zip\r\n - 7-zip is a requirement for this plugin on Windows\r\n - fix default values set by the plugin in global variables.\r\n - the default tar command provided by Windows may still be unable to unpack some archive types like .taz, .txz ...\r\n Instead, users should install a proper version of tar command and put it on PATH.\r\n - open a new tab page the first time :GetLatestVimScripts command is used, to prevent some issues with the stock plugin\r\n during installation\r\n\r\nThere is no configuration and no command you need to run to use this plugin. You only install this plugin and then use the stock :GetLatestVimScripts (:GLVS) command, and the known fixes will be applied at auto-loading time of the old plugin.\r\n\r\nOn Linux you should run the main :GLVS command in an empty Vim window, to prevent other issues, resulting in E36 \"Not enough room\" (for new windows) in Vim.\r\n\r\nPerl is needed for Linux, and PowerShell + 7-zip for Windows.\r\n\r\nBeware GetLatestVimScripts only provides a very basic plugin management function, most users should use a more popular plugin manager instead, like Vundle, Plug or Pathogen....\r\n\r\nAfter installation make sure the after\/ subdirectory, under the local runtime directory, is appeneded to &runtimepath option. It should be there by default, but append it manually if needed, in the local vimrc file.\r\n\r\nNote the current version of stock GetLastestVimScripts plugin provided by Vim is ahead of the online versions on vim.org and github. So for now do not use GLVS to update GLVS.","install_details":"Download and unpack the .bz2 archive.\r\nRun Vim in the same directory as the extractied file:\r\n vim FixUp-GetLatestVimScripts.vmb\r\n :source %\r\n :quit\r\n\r\nMake sure ~\/.vim\/after (or ~\\vimfiles\\after on Windows) is appened to &runtimepath option. This should be the default anyway.","5":"Download and unpack the .bz2 archive.\r\nRun Vim in the same directory as the extractied file:\r\n vim FixUp-GetLatestVimScripts.vmb\r\n :source %\r\n :quit\r\n\r\nMake sure ~\/.vim\/after (or ~\\vimfiles\\after on Windows) is appened to &runtimepath option. This should be the default anyway.","first_name":"Timothy","6":"Timothy","last_name":"Madden","7":"Madden","releases":[{"0":"6094","vim_version":"9.0","1":"9.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"FixUp-GetLatestVimScript.vmb.bz2","4":"FixUp-GetLatestVimScript.vmb.bz2","src_id":"28597","5":"28597","creation_date":"1705993835","6":"1705993835"}]},"6093":{"script_id":"6093","0":"6093","script_name":"ProjectConfig","1":"ProjectConfig","script_type":"utility","2":"utility","summary":"Per-project Vim configuration","3":"Per-project Vim configuration","description":"Write a Vim script that will be sourced every time you enter a project directory, with :cd or :NERDTree, or when you :edit a file from the directory. The project directories are specified in the local vimrc file, so ProjectConfig plugin does not need to search parent directories of your open files for a special file (like .project or .git or .editorconfig).\r\n\r\nThe script can use simple API functions to generated tags files for your project, and to populate the Vim options 'tags' and 'path'. The simple API works by defining simple\r\nlogical modules within your project, for example one per executable or per external library. Such modules have a set of include directories and source directories.\r\n\r\nSee the include help file, or the README.md page on github, for more details.\r\n\r\nProject repository at https:\/\/github.com\/terminatorul\/ProjectConfig","4":"Write a Vim script that will be sourced every time you enter a project directory, with :cd or :NERDTree, or when you :edit a file from the directory. The project directories are specified in the local vimrc file, so ProjectConfig plugin does not need to search parent directories of your open files for a special file (like .project or .git or .editorconfig).\r\n\r\nThe script can use simple API functions to generated tags files for your project, and to populate the Vim options 'tags' and 'path'. The simple API works by defining simple\r\nlogical modules within your project, for example one per executable or per external library. Such modules have a set of include directories and source directories.\r\n\r\nSee the include help file, or the README.md page on github, for more details.\r\n\r\nProject repository at https:\/\/github.com\/terminatorul\/ProjectConfig","install_details":"Unpack the archive with unxz or 7-zip, open Vim in the same directory as the resulting file, and run:\r\n :edit ProjectConfig.vmb\r\n :source %\r\n :quit\r\n\r\nYou can also use a plugin manager (like Vundle) to install the plugin directly from the source repository. For Vundle use\r\n\r\n call vundle#begin()\r\n\r\n\t#\r\n\t# .. other plugins you use with Vundle\r\n\t#\r\n\r\n\tPlugin 'terminatorul\/ProjectConfig'\r\n call vundle#end()","5":"Unpack the archive with unxz or 7-zip, open Vim in the same directory as the resulting file, and run:\r\n :edit ProjectConfig.vmb\r\n :source %\r\n :quit\r\n\r\nYou can also use a plugin manager (like Vundle) to install the plugin directly from the source repository. For Vundle use\r\n\r\n call vundle#begin()\r\n\r\n\t#\r\n\t# .. other plugins you use with Vundle\r\n\t#\r\n\r\n\tPlugin 'terminatorul\/ProjectConfig'\r\n call vundle#end()","first_name":"Timothy","6":"Timothy","last_name":"Madden","7":"Madden","releases":[{"0":"6093","vim_version":"9.0","1":"9.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"ProjectConfig.vmb.xz","4":"ProjectConfig.vmb.xz","src_id":"28595","5":"28595","creation_date":"1705931258","6":"1705931258"}]},"6092":{"script_id":"6092","0":"6092","script_name":"HiTags","1":"HiTags","script_type":"utility","2":"utility","summary":"dynamic symbol (e.g variable) highlighting with minimalistic requirements","3":"dynamic symbol (e.g variable) highlighting with minimalistic requirements","description":"Dynamic symbol (e.g variable, function) name highlighting with minimalistic requirements.\r\n\r\nDependencies:\r\n- mimetype (sadly, `file -i` does not suffice)\r\n- python3 (system installation, not Vim compile flag)\r\n- ctags (tested with Universal ctags)\r\n- gcc\/clang (to preprocess C\/C++ files)\r\n\r\nHome page: https:\/\/github.com\/agvxov\/Vim-HiTags\/","4":"Dynamic symbol (e.g variable, function) name highlighting with minimalistic requirements.\r\n\r\nDependencies:\r\n- mimetype (sadly, `file -i` does not suffice)\r\n- python3 (system installation, not Vim compile flag)\r\n- ctags (tested with Universal ctags)\r\n- gcc\/clang (to preprocess C\/C++ files)\r\n\r\nHome page: https:\/\/github.com\/agvxov\/Vim-HiTags\/","install_details":"1. extract the tar over your .vim\/\r\n2. Configure Vim to actually invoke the plugin. Achive this by appending \/ overriding the following definition in your .vimrc.\r\nlet g:hitags_events = [\"BufWrite\"] \" trigger a symbol update on writes\r\n3. (Optional) Further configure HiTags by editing ~\/.vim\/plugin\/hitags.vim. All required details are commented right there in the script.","5":"1. extract the tar over your .vim\/\r\n2. Configure Vim to actually invoke the plugin. Achive this by appending \/ overriding the following definition in your .vimrc.\r\nlet g:hitags_events = [\"BufWrite\"] \" trigger a symbol update on writes\r\n3. (Optional) Further configure HiTags by editing ~\/.vim\/plugin\/hitags.vim. All required details are commented right there in the script.","first_name":"Anon","6":"Anon","last_name":"Nymous","7":"Nymous","releases":[{"0":"6092","vim_version":"7.0","1":"7.0","script_version":"1","2":"1","version_comment":"Initial upload","3":"Initial upload","package":"hitags.tar","4":"hitags.tar","src_id":"28581","5":"28581","creation_date":"1702650533","6":"1702650533"}]},"6091":{"script_id":"6091","0":"6091","script_name":"gnt_poignant","1":"gnt_poignant","script_type":"color scheme","2":"color scheme","summary":"color scheme based on why_poignant","3":"color scheme based on why_poignant","description":"a clone of why_poignant, some colors modified to be more php friendly and more modern","4":"a clone of why_poignant, some colors modified to be more php friendly and more modern","install_details":"","5":"","first_name":"GN","6":"GN","last_name":"Trifanoff","7":"Trifanoff","releases":[{"0":"6091","vim_version":"7.0","1":"7.0","script_version":"1","2":"1","version_comment":"Initial upload","3":"Initial upload","package":"gnt_poignant.vim","4":"gnt_poignant.vim","src_id":"28580","5":"28580","creation_date":"1701177427","6":"1701177427"}]},"6090":{"script_id":"6090","0":"6090","script_name":"wrapwidth","1":"wrapwidth","script_type":"utility","2":"utility","summary":"Wraps long lines virtually at a specific column","3":"Wraps long lines virtually at a specific column","description":"This plugin provides the 'Wrapwidth' command to set a column at which a longer line will be virtually wrapped. When 'wrap' is on, the required number of blank spaces are inserted as virtual-text at right edge of each screen line.\r\n\r\nFor details and demo samples, please visit the following git repository: https:\/\/github.com\/rickhowe\/wrapwidth.","4":"This plugin provides the 'Wrapwidth' command to set a column at which a longer line will be virtually wrapped. When 'wrap' is on, the required number of blank spaces are inserted as virtual-text at right edge of each screen line.\r\n\r\nFor details and demo samples, please visit the following git repository: https:\/\/github.com\/rickhowe\/wrapwidth.","install_details":"Install 'rickhowe\/wrapwidth' by using your plugin manager. Or manually unzip and copy all folders in your ~\/.vim or ~\/vimfiles.","5":"Install 'rickhowe\/wrapwidth' by using your plugin manager. Or manually unzip and copy all folders in your ~\/.vim or ~\/vimfiles.","first_name":"Rick","6":"Rick","last_name":"Howe","7":"Howe","releases":[{"0":"6090","vim_version":"9.0","1":"9.0","script_version":"3.4","2":"3.4","version_comment":"Improved to allow multi-byte and multi-column characters to use in the wrapwidth_sign option.","3":"Improved to allow multi-byte and multi-column characters to use in the wrapwidth_sign option.","package":"wrapwidth3.4.zip","4":"wrapwidth3.4.zip","src_id":"28652","5":"28652","creation_date":"1710839559","6":"1710839559"},{"0":"6090","vim_version":"9.0","1":"9.0","script_version":"3.3","2":"3.3","version_comment":"Improved to automatically adjust the virtual spaces while typing in insert mode. Added 2 options.","3":"Improved to automatically adjust the virtual spaces while typing in insert mode. Added 2 options.","package":"wrapwidth3.3.zip","4":"wrapwidth3.3.zip","src_id":"28646","5":"28646","creation_date":"1710301590","6":"1710301590"},{"0":"6090","vim_version":"9.0","1":"9.0","script_version":"3.2","2":"3.2","version_comment":"Added ! flag to the :Wrapwidth command to redraw the wrapwidth virtual spaces for an accidental displacement.","3":"Added ! flag to the :Wrapwidth command to redraw the wrapwidth virtual spaces for an accidental displacement.","package":"wrapwidth3.2.zip","4":"wrapwidth3.2.zip","src_id":"28612","5":"28612","creation_date":"1708164293","6":"1708164293"},{"0":"6090","vim_version":"9.0","1":"9.0","script_version":"3.1","2":"3.1","version_comment":"Improved to ignore many WinResized events and work smoothly while resizing a window by mouse.","3":"Improved to ignore many WinResized events and work smoothly while resizing a window by mouse.","package":"wrapwidth3.1.zip","4":"wrapwidth3.1.zip","src_id":"28596","5":"28596","creation_date":"1705933310","6":"1705933310"},{"0":"6090","vim_version":"9.0","1":"9.0","script_version":"3.0","2":"3.0","version_comment":"Added [range] to the :Wrapwidth command to specify and set more than one different sets of wrapwidth lines.","3":"Added [range] to the :Wrapwidth command to specify and set more than one different sets of wrapwidth lines.","package":"wrapwidth3.0.zip","4":"wrapwidth3.0.zip","src_id":"28586","5":"28586","creation_date":"1704708509","6":"1704708509"},{"0":"6090","vim_version":"9.0","1":"9.0","script_version":"2.0","2":"2.0","version_comment":"Improved to check changed lines and update virtual spaces only on them while editing.","3":"Improved to check changed lines and update virtual spaces only on them while editing.","package":"wrapwidth2.0.zip","4":"wrapwidth2.0.zip","src_id":"28582","5":"28582","creation_date":"1702718268","6":"1702718268"},{"0":"6090","vim_version":"9.0","1":"9.0","script_version":"1.2","2":"1.2","version_comment":"Initial upload","3":"Initial upload","package":"wrapwidth1.2.zip","4":"wrapwidth1.2.zip","src_id":"28562","5":"28562","creation_date":"1697868189","6":"1697868189"}]},"6089":{"script_id":"6089","0":"6089","script_name":"ipxe","1":"ipxe","script_type":"syntax","2":"syntax","summary":"Syntax highlighing of ipxe scripts","3":"Syntax highlighing of ipxe scripts","description":"iPXE is an open source network boot firmware, with a scriptable command line interface for which language this plugin provides syntax highlighting. As these files typically either have \"txt\" or simply no file extension, filetype detection relies on their first line being `#!ipxe`.","4":"iPXE is an open source network boot firmware, with a scriptable command line interface for which language this plugin provides syntax highlighting. As these files typically either have \"txt\" or simply no file extension, filetype detection relies on their first line being `#!ipxe`.","install_details":"","5":"","first_name":"Martin","6":"Martin","last_name":"","7":"","releases":[{"0":"6089","vim_version":"7.0","1":"7.0","script_version":"1","2":"1","version_comment":"Initial upload","3":"Initial upload","package":"ipxe-1.zip","4":"ipxe-1.zip","src_id":"28558","5":"28558","creation_date":"1697789509","6":"1697789509"}]},"6088":{"script_id":"6088","0":"6088","script_name":"Popcorn","1":"Popcorn","script_type":"utility","2":"utility","summary":"You can define your own pop-up menu.","3":"You can define your own pop-up menu.","description":"Prerequisites:\r\n\r\n- Vim9\r\n- `+popupwin`\r\n\r\n\r\nUsage:\r\n\r\n:Popcorn\r\n\r\n\r\n\r\n- j, k: up, down\r\n- h, l(enter): menu level (h: go up, l: go down)\r\n- enter: execute\r\n- q, esc: quit\r\n- \/: search mode\r\n- upper case: search mode when g:PopcornSearchOnUpper\r\n\r\n\r\n\r\n- ctrl-n, ctrl-p: up, down\r\n- enter: execute\r\n- esc: normal mode\r\n- backspace, ctrl-h: backspace\r\n- alpha nuberic: search\r\n\r\n\r\nCustomize:\r\n\r\n```\r\n# vim9script\r\n\r\ng:PopcornItems = [\r\n {name: 'LSP', sub: [\r\n {name: 'Hover', execute: 'LspHover', default: true},\r\n {name: 'Definition', execute: 'LspDefinition'},\r\n {name: 'Rename', execute: 'LspRename'},\r\n ]},\r\n {name: 'Window', sub: [\r\n {name: 'Alt', executeeval: '\"buffer \" .. bufnr(\"#\")', default: true},\r\n {name: '-'},\r\n {name: 'Split(--)', execute: 'split'},\r\n {name: 'Split(|)', execute: 'vsplit'},\r\n ]},\r\n {name: '-'},\r\n {name: 'Time', nameeval: 'strftime(\"%Y-%m-%d %H:%M:%S\")', skip: true},\r\n]\r\n```\r\n\r\nYou can set menu items directly to g:PopcornItems.\r\n\r\nYou can also use g:Popcorn_clear(), g:Popcorn_add() and g:Popcorn_remove().\r\n\r\n\r\nRule:\r\n\r\n1. Each item must have `name`\r\n2. Must have one of (`execute`, `executeeval`, `sub`)\r\n3. `nameeval` is eval()-ed when displayed (priority: `nameeval` > `name`)\r\n4. `executeeval` is eval()-ed when executed (priority: `executeeval` > `execute`)\r\n5. 'execute' (and 'executeeval') can be a string or a list of strings\r\n6. 'default' item is executed when enter is pressed on its parent\r\n7. A separator is {name: '-'}\r\n8. 'skip' is true if the cursor skips the item\r\n\r\nHighlights:\r\n\r\n- g:PopcornGroupHighlight = 'Comment'\r\n- g:PopcornSeparatorHighlight = 'Comment'\r\n- g:PopcornSearchOnUpper = false\r\n\r\n\r\nhttps:\/\/github.com\/shu-vim\/Popcorn","4":"Prerequisites:\r\n\r\n- Vim9\r\n- `+popupwin`\r\n\r\n\r\nUsage:\r\n\r\n:Popcorn\r\n\r\n\r\n\r\n- j, k: up, down\r\n- h, l(enter): menu level (h: go up, l: go down)\r\n- enter: execute\r\n- q, esc: quit\r\n- \/: search mode\r\n- upper case: search mode when g:PopcornSearchOnUpper\r\n\r\n\r\n\r\n- ctrl-n, ctrl-p: up, down\r\n- enter: execute\r\n- esc: normal mode\r\n- backspace, ctrl-h: backspace\r\n- alpha nuberic: search\r\n\r\n\r\nCustomize:\r\n\r\n```\r\n# vim9script\r\n\r\ng:PopcornItems = [\r\n {name: 'LSP', sub: [\r\n {name: 'Hover', execute: 'LspHover', default: true},\r\n {name: 'Definition', execute: 'LspDefinition'},\r\n {name: 'Rename', execute: 'LspRename'},\r\n ]},\r\n {name: 'Window', sub: [\r\n {name: 'Alt', executeeval: '\"buffer \" .. bufnr(\"#\")', default: true},\r\n {name: '-'},\r\n {name: 'Split(--)', execute: 'split'},\r\n {name: 'Split(|)', execute: 'vsplit'},\r\n ]},\r\n {name: '-'},\r\n {name: 'Time', nameeval: 'strftime(\"%Y-%m-%d %H:%M:%S\")', skip: true},\r\n]\r\n```\r\n\r\nYou can set menu items directly to g:PopcornItems.\r\n\r\nYou can also use g:Popcorn_clear(), g:Popcorn_add() and g:Popcorn_remove().\r\n\r\n\r\nRule:\r\n\r\n1. Each item must have `name`\r\n2. Must have one of (`execute`, `executeeval`, `sub`)\r\n3. `nameeval` is eval()-ed when displayed (priority: `nameeval` > `name`)\r\n4. `executeeval` is eval()-ed when executed (priority: `executeeval` > `execute`)\r\n5. 'execute' (and 'executeeval') can be a string or a list of strings\r\n6. 'default' item is executed when enter is pressed on its parent\r\n7. A separator is {name: '-'}\r\n8. 'skip' is true if the cursor skips the item\r\n\r\nHighlights:\r\n\r\n- g:PopcornGroupHighlight = 'Comment'\r\n- g:PopcornSeparatorHighlight = 'Comment'\r\n- g:PopcornSearchOnUpper = false\r\n\r\n\r\nhttps:\/\/github.com\/shu-vim\/Popcorn","install_details":"Put this plugin in your plugin directory(e.g. $VIMRUNTIME\/plugin).\r\nThen restart Vim.","5":"Put this plugin in your plugin directory(e.g. $VIMRUNTIME\/plugin).\r\nThen restart Vim.","first_name":"Shuhei","6":"Shuhei","last_name":"Kubota","7":"Kubota","releases":[{"0":"6088","vim_version":"9.0","1":"9.0","script_version":"0.5.2","2":"0.5.2","version_comment":"* execute nested default item\r\n* skipped items are highlighted Comment and centered","3":"* execute nested default item\r\n* skipped items are highlighted Comment and centered","package":"popcorn.zip","4":"popcorn.zip","src_id":"28673","5":"28673","creation_date":"1713266858","6":"1713266858"},{"0":"6088","vim_version":"9.0","1":"9.0","script_version":"0.5.0","2":"0.5.0","version_comment":"add skip","3":"add skip","package":"popcorn.zip","4":"popcorn.zip","src_id":"28665","5":"28665","creation_date":"1713060805","6":"1713060805"},{"0":"6088","vim_version":"9.0","1":"9.0","script_version":"0.4.0","2":"0.4.0","version_comment":"search mode","3":"search mode","package":"popcorn.zip","4":"popcorn.zip","src_id":"28565","5":"28565","creation_date":"1698073152","6":"1698073152"},{"0":"6088","vim_version":"9.0","1":"9.0","script_version":"0.3.0","2":"0.3.0","version_comment":"separator, highlights","3":"separator, highlights","package":"popcorn.zip","4":"popcorn.zip","src_id":"28564","5":"28564","creation_date":"1697888844","6":"1697888844"},{"0":"6088","vim_version":"9.0","1":"9.0","script_version":"0.2.0","2":"0.2.0","version_comment":"'execute' (and 'executeeval') can be a string or a list of strings.","3":"'execute' (and 'executeeval') can be a string or a list of strings.","package":"popcorn.zip","4":"popcorn.zip","src_id":"28563","5":"28563","creation_date":"1697876945","6":"1697876945"},{"0":"6088","vim_version":"9.0","1":"9.0","script_version":"0.1.0","2":"0.1.0","version_comment":"Initial upload","3":"Initial upload","package":"popcorn.vim","4":"popcorn.vim","src_id":"28557","5":"28557","creation_date":"1697635733","6":"1697635733"}]},"6087":{"script_id":"6087","0":"6087","script_name":"preseed","1":"preseed","script_type":"syntax","2":"syntax","summary":"Provide syntax highlighing of debian preseed files","3":"Provide syntax highlighing of debian preseed files","description":"Preseed files enable automated installation of the Debian operating systems and some of its derivatives. As the preseed files typically either have \"txt\" or simply no file extension, filetype detection relies on their first line being `#_preseed_V1`.","4":"Preseed files enable automated installation of the Debian operating systems and some of its derivatives. As the preseed files typically either have \"txt\" or simply no file extension, filetype detection relies on their first line being `#_preseed_V1`.","install_details":"","5":"","first_name":"Martin","6":"Martin","last_name":"","7":"","releases":[{"0":"6087","vim_version":"7.3","1":"7.3","script_version":"8","2":"8","version_comment":"Add support for embedded sh commands","3":"Add support for embedded sh commands","package":"preseed-8.zip","4":"preseed-8.zip","src_id":"28578","5":"28578","creation_date":"1699607364","6":"1699607364"},{"0":"6087","vim_version":"7.3","1":"7.3","script_version":"7","2":"7","version_comment":"Adapt to findings from preseed.debian.net","3":"Adapt to findings from preseed.debian.net","package":"preseed-7.zip","4":"preseed-7.zip","src_id":"28572","5":"28572","creation_date":"1698917023","6":"1698917023"},{"0":"6087","vim_version":"7.3","1":"7.3","script_version":"5","2":"5","version_comment":"Initial upload","3":"Initial upload","package":"preseed-5.zip","4":"preseed-5.zip","src_id":"28556","5":"28556","creation_date":"1697379909","6":"1697379909"}]},"6086":{"script_id":"6086","0":"6086","script_name":"KeySound","1":"KeySound","script_type":"utility","2":"utility","summary":"Turn Vim into a typewriter! ","3":"Turn Vim into a typewriter! ","description":"KeySound is an essential plugin that adds typewriter sounds to Vim in Insert mode. It can also associate sounds to any auto-command event. It requires Vim 9.0 or later compiled with +sound. Features: customize sounds; define distinct sounds for distinct keys or events; define multiple sounds for the same key or event (randomization); disable sounds for specific keys. Happy writing!\r\n\r\nFor additional sounds, see https:\/\/github.com\/lifepillar\/typewriter-sounds.","4":"KeySound is an essential plugin that adds typewriter sounds to Vim in Insert mode. It can also associate sounds to any auto-command event. It requires Vim 9.0 or later compiled with +sound. Features: customize sounds; define distinct sounds for distinct keys or events; define multiple sounds for the same key or event (randomization); disable sounds for specific keys. Happy writing!\r\n\r\nFor additional sounds, see https:\/\/github.com\/lifepillar\/typewriter-sounds.","install_details":"","5":"","first_name":"","6":"","last_name":"Lifepillar","7":"Lifepillar","releases":[{"0":"6086","vim_version":"9.0","1":"9.0","script_version":"0.0.4","2":"0.0.4","version_comment":"The indispensable plugin that turns Vim into a typewriter! What's new: sounds are now in WAV format for better compatibility. Event sounds can be left on even when keyboard sounds are off. Improved debug info dialog. Added PlaySoundFor() for custom plugs. Help extended with examples on resolving conflicting mappings.","3":"The indispensable plugin that turns Vim into a typewriter! What's new: sounds are now in WAV format for better compatibility. Event sounds can be left on even when keyboard sounds are off. Improved debug info dialog. Added PlaySoundFor() for custom plugs. Help extended with examples on resolving conflicting mappings.","package":"vim-keysound-0.0.4.tar.gz","4":"vim-keysound-0.0.4.tar.gz","src_id":"28566","5":"28566","creation_date":"1698087909","6":"1698087909"}]},"6085":{"script_id":"6085","0":"6085","script_name":"SudoEdit-TEST","1":"SudoEdit-TEST","script_type":"utility","2":"utility","summary":"test-upload","3":"test-upload","description":"test-upload","4":"test-upload","install_details":"test-upload","5":"test-upload","first_name":"Christian","6":"Christian","last_name":"Brabandt","7":"Brabandt","releases":[{"0":"6085","vim_version":"9.0","1":"9.0","script_version":"1.1","2":"1.1","version_comment":"Initial upload","3":"Initial upload","package":"SudoEdit-0.21.vmb","4":"SudoEdit-0.21.vmb","src_id":"28553","5":"28553","creation_date":"1697355107","6":"1697355107"}]},"6078":{"script_id":"6078","0":"6078","script_name":"vim-navigator","1":"vim-navigator","script_type":"utility","2":"utility","summary":"An whichkey alternative to provide keymap hints.","3":"An whichkey alternative to provide keymap hints.","description":"Vim has got several whichkey like plugins for keymap hints and I've tried each of them one\r\nby one and found them always lacking in some way. As a result, I've made the decision to \r\ncreate my own plugin, which is similar to whichkey but with some exciting enhancements.\r\n\r\nFeatures:\r\n\r\n- Better layout: each column can have different width. \r\n- Columns with short texts will not occupy a lot of space.\r\n- Fully customizable: separator style and visibility, bracket (around key character) visibility, spacing, padding, highlighting, and position.\r\n- Zero timeout mode and adaptive window size.\r\n- Buffer local keymaps for different file types.\r\n- Unambiguity syntax to define a command or key sequence.\r\n- Runtime keymap generation, items can be decided at runtime.\r\n- Can use popup for vim 8.2+ and floatwin for nvim 0.6.0+\r\n- Legacy Vim compatibility (only requires Vim 7.4.2364).\r\n\r\nHomepage:\r\n\r\nhttps:\/\/github.com\/skywind3000\/vim-navigator\r\n\r\n","4":"Vim has got several whichkey like plugins for keymap hints and I've tried each of them one\r\nby one and found them always lacking in some way. As a result, I've made the decision to \r\ncreate my own plugin, which is similar to whichkey but with some exciting enhancements.\r\n\r\nFeatures:\r\n\r\n- Better layout: each column can have different width. \r\n- Columns with short texts will not occupy a lot of space.\r\n- Fully customizable: separator style and visibility, bracket (around key character) visibility, spacing, padding, highlighting, and position.\r\n- Zero timeout mode and adaptive window size.\r\n- Buffer local keymaps for different file types.\r\n- Unambiguity syntax to define a command or key sequence.\r\n- Runtime keymap generation, items can be decided at runtime.\r\n- Can use popup for vim 8.2+ and floatwin for nvim 0.6.0+\r\n- Legacy Vim compatibility (only requires Vim 7.4.2364).\r\n\r\nHomepage:\r\n\r\nhttps:\/\/github.com\/skywind3000\/vim-navigator\r\n\r\n","install_details":"Plug 'skywind3000\/vim-quickui'\r\nPlug 'skywind3000\/vim-navigator'","5":"Plug 'skywind3000\/vim-quickui'\r\nPlug 'skywind3000\/vim-navigator'","first_name":"Wei","6":"Wei","last_name":"Lin","7":"Lin","releases":[{"0":"6078","vim_version":"8.0","1":"8.0","script_version":"0.0.3","2":"0.0.3","version_comment":"- fix: popup mode in the center may be unable to calculate paging information.\r\n- fix: crash when min_height is above max_height \r\n- minor fixes.","3":"- fix: popup mode in the center may be unable to calculate paging information.\r\n- fix: crash when min_height is above max_height \r\n- minor fixes.","package":"vim-navigator-0.0.3.zip","4":"vim-navigator-0.0.3.zip","src_id":"28647","5":"28647","creation_date":"1710402386","6":"1710402386"},{"0":"6078","vim_version":"8.0","1":"8.0","script_version":"0.0.2","2":"0.0.2","version_comment":"- Add special key names and display values for function keys in the script\r\n","3":"- Add special key names and display values for function keys in the script\r\n","package":"vim-navigator-0.0.2.zip","4":"vim-navigator-0.0.2.zip","src_id":"28620","5":"28620","creation_date":"1708676693","6":"1708676693"},{"0":"6078","vim_version":"8.0","1":"8.0","script_version":"0.0.1","2":"0.0.1","version_comment":"Initial upload","3":"Initial upload","package":"vim-navigator-0.0.1.zip","4":"vim-navigator-0.0.1.zip","src_id":"28520","5":"28520","creation_date":"1690591357","6":"1690591357"}]},"6077":{"script_id":"6077","0":"6077","script_name":"rpi-vim","1":"rpi-vim","script_type":"utility","2":"utility","summary":"Vim integration for emulated Raspberry PIs","3":"Vim integration for emulated Raspberry PIs","description":"Designed for Docker-hosted RPi OS images, but suitable for any RPi with a running SSH server.\r\nSource files are copied to the RPi with rsync and compiled with the native GCC toolchain.\r\n\r\nVisit https:\/\/github.com\/rdipardo\/rpi-vim#readme for complete details\r\n\r\n\r\nSetup\r\n---------\r\nThese configuration variables can be set in a '.env' file in your current working directory:\r\n\r\nOS_VERSION\r\n Raspberry Pi OS version string\r\n Default: '2022-01-28-raspios-bullseye-arm64-lite'\r\n\r\nOS_IMAGE_URL\r\n URL where 'OS_VERSION' is hosted\r\n Default: 'https:\/\/downloads.raspberrypi.org\/raspios_lite_arm64\/images\/raspios_lite_arm64-2022-01-28'\r\n\r\nRPI_BOARD\r\n Model number of the board to virtualize\r\n Default: 'pi3'\r\n\r\n~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~\r\nNOTE\r\nValid options are: 'pi1', 'pi2', 'pi3' or '' (empty).\r\nIf the model number is empty, and 'OS_VERSION' targets `armhf`,\r\nthe image is mounted to a virtual ARM Versatile board by default.\r\n\r\nSee:\r\n https:\/\/github.com\/lukechilds\/dockerpi#which-machines-are-supported\r\n https:\/\/www.qemu.org\/docs\/master\/system\/arm\/versatile.html\r\n~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~\r\n\r\nSSH_HOST\r\n User and host name of the RPi's SSH server\r\n Default: 'pi@localhost'\r\n\r\nSSH_PORT\r\n Port number the RPi's SSH server is listening on\r\n Default: 5022\r\n\r\nSSH_PASSWORD\r\n Login password for 'SSH_HOST'\r\n Default: ''\r\n\r\nSSH_PARAMS\r\n Additional options for the ssh client\r\n Default: ''\r\n\r\nWORK_DIR\r\n Directory on the RPi where source files will be copied\r\n Default: '~'\r\n\r\nA CFLAGS, CXXFLAGS or LDFLAGS variable can also be passed to the RPi's compiler by creating a '.cflags' file in the current working directory, e.g.,\r\n\r\n CFLAGS='-I\/opt\/vc\/include -std=c11'\r\n CXXFLAGS='-std=gnu++2b'\r\n LDFLAGS='-L\/opt\/vc\/lib -lbcm_host'\r\n\r\n\r\nCommands\r\n----------------\r\n:RPiRun Default mapping: {Normal}\r\n\r\nExecute the active buffer on the RPi.\r\n\r\n\r\n:RPiCompile Default mapping: {Normal}\r\n\r\nCopy the active buffer to the RPi and compile it.\r\n\r\n\r\n:RPiMake [{target}] Default mapping: {Normal}\r\n\r\nIf the working directory contains a Makefile, copy all source files to the RPi\r\nand run `make` with the given {target}, if any.\r\n\r\nIf no Makefile exits, copy, compile and link all source files using the\r\n'CFLAGS', 'CXXFLAGS' and 'LDFLAGS' variables in the user's '.cflags' file.\r\n\r\n\r\n:RPiSetup [{key_file_path}] [{key_file_password}]\r\n\r\nCreate a new SSH key file at {key_file_path} with {key_file_password} and copy\r\nit to the RPi at 'SSH_HOST'. Also copy the plugin's required build scripts\r\nafter a successful connection is made. All parameters are optional.\r\n\r\n\r\n:RPiBoot [{image_file_directory}]\r\n\r\nSearch {image_file_directory} for an RPi OS image file matching 'OS_VERSION'\r\nand mount it inside a Docker container.\r\n\r\nIf no {image_file_directory} is given, search the plugin's installation path.\r\nIf no image matching 'OS_VERSION' is found, try downloading it from 'OS_IMAGE_URL'.","4":"Designed for Docker-hosted RPi OS images, but suitable for any RPi with a running SSH server.\r\nSource files are copied to the RPi with rsync and compiled with the native GCC toolchain.\r\n\r\nVisit https:\/\/github.com\/rdipardo\/rpi-vim#readme for complete details\r\n\r\n\r\nSetup\r\n---------\r\nThese configuration variables can be set in a '.env' file in your current working directory:\r\n\r\nOS_VERSION\r\n Raspberry Pi OS version string\r\n Default: '2022-01-28-raspios-bullseye-arm64-lite'\r\n\r\nOS_IMAGE_URL\r\n URL where 'OS_VERSION' is hosted\r\n Default: 'https:\/\/downloads.raspberrypi.org\/raspios_lite_arm64\/images\/raspios_lite_arm64-2022-01-28'\r\n\r\nRPI_BOARD\r\n Model number of the board to virtualize\r\n Default: 'pi3'\r\n\r\n~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~\r\nNOTE\r\nValid options are: 'pi1', 'pi2', 'pi3' or '' (empty).\r\nIf the model number is empty, and 'OS_VERSION' targets `armhf`,\r\nthe image is mounted to a virtual ARM Versatile board by default.\r\n\r\nSee:\r\n https:\/\/github.com\/lukechilds\/dockerpi#which-machines-are-supported\r\n https:\/\/www.qemu.org\/docs\/master\/system\/arm\/versatile.html\r\n~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~\r\n\r\nSSH_HOST\r\n User and host name of the RPi's SSH server\r\n Default: 'pi@localhost'\r\n\r\nSSH_PORT\r\n Port number the RPi's SSH server is listening on\r\n Default: 5022\r\n\r\nSSH_PASSWORD\r\n Login password for 'SSH_HOST'\r\n Default: ''\r\n\r\nSSH_PARAMS\r\n Additional options for the ssh client\r\n Default: ''\r\n\r\nWORK_DIR\r\n Directory on the RPi where source files will be copied\r\n Default: '~'\r\n\r\nA CFLAGS, CXXFLAGS or LDFLAGS variable can also be passed to the RPi's compiler by creating a '.cflags' file in the current working directory, e.g.,\r\n\r\n CFLAGS='-I\/opt\/vc\/include -std=c11'\r\n CXXFLAGS='-std=gnu++2b'\r\n LDFLAGS='-L\/opt\/vc\/lib -lbcm_host'\r\n\r\n\r\nCommands\r\n----------------\r\n:RPiRun Default mapping: {Normal}\r\n\r\nExecute the active buffer on the RPi.\r\n\r\n\r\n:RPiCompile Default mapping: {Normal}\r\n\r\nCopy the active buffer to the RPi and compile it.\r\n\r\n\r\n:RPiMake [{target}] Default mapping: {Normal}\r\n\r\nIf the working directory contains a Makefile, copy all source files to the RPi\r\nand run `make` with the given {target}, if any.\r\n\r\nIf no Makefile exits, copy, compile and link all source files using the\r\n'CFLAGS', 'CXXFLAGS' and 'LDFLAGS' variables in the user's '.cflags' file.\r\n\r\n\r\n:RPiSetup [{key_file_path}] [{key_file_password}]\r\n\r\nCreate a new SSH key file at {key_file_path} with {key_file_password} and copy\r\nit to the RPi at 'SSH_HOST'. Also copy the plugin's required build scripts\r\nafter a successful connection is made. All parameters are optional.\r\n\r\n\r\n:RPiBoot [{image_file_directory}]\r\n\r\nSearch {image_file_directory} for an RPi OS image file matching 'OS_VERSION'\r\nand mount it inside a Docker container.\r\n\r\nIf no {image_file_directory} is given, search the plugin's installation path.\r\nIf no image matching 'OS_VERSION' is found, try downloading it from 'OS_IMAGE_URL'.","install_details":"With Vim 8 or newer, copy the plugin source tree into Vim's 'packages' path:\r\n\r\n mkdir -p ~\/.vim\/pack\/plugins\/start\r\n git clone https:\/\/github.com\/rdipardo\/rpi-vim.git ~\/.vim\/pack\/plugins\/start\/rpi-vim\r\n\r\nVisit https:\/\/github.com\/rdipardo\/rpi-vim#readme for instructions on using a third-party plugin manager","5":"With Vim 8 or newer, copy the plugin source tree into Vim's 'packages' path:\r\n\r\n mkdir -p ~\/.vim\/pack\/plugins\/start\r\n git clone https:\/\/github.com\/rdipardo\/rpi-vim.git ~\/.vim\/pack\/plugins\/start\/rpi-vim\r\n\r\nVisit https:\/\/github.com\/rdipardo\/rpi-vim#readme for instructions on using a third-party plugin manager","first_name":"Robert","6":"Robert","last_name":"Di Pardo","7":"Di Pardo","releases":[{"0":"6077","vim_version":"8.0","1":"8.0","script_version":"1.2.0","2":"1.2.0","version_comment":"Adapt commands to Neovim's terminal protocol; support local '.env' and '.cflags' configurations","3":"Adapt commands to Neovim's terminal protocol; support local '.env' and '.cflags' configurations","package":"rpi-vim.1.2.0.tar.gz","4":"rpi-vim.1.2.0.tar.gz","src_id":"28577","5":"28577","creation_date":"1699229058","6":"1699229058"},{"0":"6077","vim_version":"8.0","1":"8.0","script_version":"1.1.1","2":"1.1.1","version_comment":"Initial upload","3":"Initial upload","package":"rpi-vim.1.1.1.tar.gz","4":"rpi-vim.1.1.1.tar.gz","src_id":"28519","5":"28519","creation_date":"1690179186","6":"1690179186"}]},"6076":{"script_id":"6076","0":"6076","script_name":"terminal-drawer.vim","1":"terminal-drawer.vim","script_type":"utility","2":"utility","summary":"Vim plugin for quick open\/close terminal drawer","3":"Vim plugin for quick open\/close terminal drawer","description":"The purpose of this plugin is quite simple: use `` or any key mapping to toggle terminal. \r\n\r\nMost time, you just need a terminal to run a single command like a `make`. But you need to:\r\n- `:term` to open a terminal\r\n- `:hid` to hidden the terminal Or bare it use some of you coding space\r\n- remember the buffer number of terminal OR use some tools like fzf to search buffer\r\n- `:sp {bufnr}` to find back you terminal\r\nNow you can do with only one key mapping you chosen.\r\n\r\nGithub: https:\/\/github.com\/iaalm\/terminal-drawer.vim","4":"The purpose of this plugin is quite simple: use `` or any key mapping to toggle terminal. \r\n\r\nMost time, you just need a terminal to run a single command like a `make`. But you need to:\r\n- `:term` to open a terminal\r\n- `:hid` to hidden the terminal Or bare it use some of you coding space\r\n- remember the buffer number of terminal OR use some tools like fzf to search buffer\r\n- `:sp {bufnr}` to find back you terminal\r\nNow you can do with only one key mapping you chosen.\r\n\r\nGithub: https:\/\/github.com\/iaalm\/terminal-drawer.vim","install_details":"","5":"","first_name":"iaalm","6":"iaalm","last_name":"simon","7":"simon","releases":[{"0":"6076","vim_version":"8.2","1":"8.2","script_version":"1.1","2":"1.1","version_comment":"Initial upload","3":"Initial upload","package":"terminal-drawer.vim-1.1.zip","4":"terminal-drawer.vim-1.1.zip","src_id":"28509","5":"28509","creation_date":"1687913824","6":"1687913824"}]},"6075":{"script_id":"6075","0":"6075","script_name":"vim-highlight-yanked","1":"vim-highlight-yanked","script_type":"utility","2":"utility","summary":"Highlight yanked text.","3":"Highlight yanked text.","description":"Highlight yanked text.","4":"Highlight yanked text.","install_details":"","5":"","first_name":"Ubaldo","6":"Ubaldo","last_name":"Tiberi","7":"Tiberi","releases":[{"0":"6075","vim_version":"9.0","1":"9.0","script_version":"v1.0.0","2":"v1.0.0","version_comment":"Initial Release","3":"Initial Release","package":"vim-highlight-yanked-1.0.0.zip","4":"vim-highlight-yanked-1.0.0.zip","src_id":"28495","5":"28495","creation_date":"1685552414","6":"1685552414"}]},"6074":{"script_id":"6074","0":"6074","script_name":"vim-conda-activate","1":"vim-conda-activate","script_type":"utility","2":"utility","summary":"Activate Conda environments in Vim.","3":"Activate Conda environments in Vim.","description":"Change Conda environment in Vim. ","4":"Change Conda environment in Vim. ","install_details":"","5":"","first_name":"Ubaldo","6":"Ubaldo","last_name":"Tiberi","7":"Tiberi","releases":[{"0":"6074","vim_version":"9.0","1":"9.0","script_version":"v1.0.0","2":"v1.0.0","version_comment":"Initial Release.","3":"Initial Release.","package":"vim-conda-activate-1.0.0.zip","4":"vim-conda-activate-1.0.0.zip","src_id":"28494","5":"28494","creation_date":"1685552284","6":"1685552284"}]},"6073":{"script_id":"6073","0":"6073","script_name":"vim-writegood","1":"vim-writegood","script_type":"utility","2":"utility","summary":"Check your English prose in vim.","3":"Check your English prose in vim.","description":"Vim-writegood naively check your English prose. It is nothing but a simple Vim9 wrapper around prose linters.","4":"Vim-writegood naively check your English prose. It is nothing but a simple Vim9 wrapper around prose linters.","install_details":"You must have a prose linter installed. \r\nCurrently supported linters are write-good and vale. Check their docs for installation and configuration guidelines.\r\n\r\nOh, and you need Vim9 of course.","5":"You must have a prose linter installed. \r\nCurrently supported linters are write-good and vale. Check their docs for installation and configuration guidelines.\r\n\r\nOh, and you need Vim9 of course.","first_name":"Ubaldo","6":"Ubaldo","last_name":"Tiberi","7":"Tiberi","releases":[{"0":"6073","vim_version":"9.0","1":"9.0","script_version":"v1.1.1","2":"v1.1.1","version_comment":"* Updated License.","3":"* Updated License.","package":"vim-writegood-1.1.1.zip","4":"vim-writegood-1.1.1.zip","src_id":"28492","5":"28492","creation_date":"1685552108","6":"1685552108"}]},"6072":{"script_id":"6072","0":"6072","script_name":"fuzzyy","1":"fuzzyy","script_type":"utility","2":"utility","summary":"A fuzzy finder for vim","3":"A fuzzy finder for vim","description":"A fuzzy finder for files, strings, help documents and many other things.\r\n\r\nIt ultilizes vim's native matchfuzzypos function and popup window feature.\r\n\r\nhttps:\/\/github.com\/Donaldttt\/fuzzyy","4":"A fuzzy finder for files, strings, help documents and many other things.\r\n\r\nIt ultilizes vim's native matchfuzzypos function and popup window feature.\r\n\r\nhttps:\/\/github.com\/Donaldttt\/fuzzyy","install_details":"","5":"","first_name":"Nachuan","6":"Nachuan","last_name":"Tang","7":"Tang","releases":[{"0":"6072","vim_version":"9.0","1":"9.0","script_version":"1.1.5","2":"1.1.5","version_comment":"https:\/\/github.com\/Donaldttt\/fuzzyy","3":"https:\/\/github.com\/Donaldttt\/fuzzyy","package":"fuzzyy.zip","4":"fuzzyy.zip","src_id":"28614","5":"28614","creation_date":"1708237051","6":"1708237051"},{"0":"6072","vim_version":"9.0","1":"9.0","script_version":"1.1.4","2":"1.1.4","version_comment":"For more detail please refer to github page: https:\/\/github.com\/Donaldttt\/fuzzyy.","3":"For more detail please refer to github page: https:\/\/github.com\/Donaldttt\/fuzzyy.","package":"fuzzyy.zip","4":"fuzzyy.zip","src_id":"28591","5":"28591","creation_date":"1705157222","6":"1705157222"}]},"6071":{"script_id":"6071","0":"6071","script_name":"organ","1":"organ","script_type":"utility","2":"utility","summary":"Generalize Orgmode to Markdown and any Folded file","3":"Generalize Orgmode to Markdown and any Folded file","description":"# What is it ?\r\n\r\nOrgan generalizes the great concepts of Orgmode to Markdown and any folded file. It is primarily focused on editing these documents with ease and agility.\r\n\r\n# More information\r\n\r\nSee the github repository :\r\n\r\n[organ](https:\/\/github.com\/chimay\/organ)\r\n\r\n# Compatibilty\r\n\r\nOrgan supports :\r\n\r\norg files\r\nmarkdown\r\nasciidoc : headings only\r\nfolded files with markers\r\nindent folded files : basic navigation only\r\nIt is written in vimscript and is compatible with both Vim and Neovim.\r\n\r\n# Features\r\n\r\n- folding based on headings in org and markdown files\r\n- headings base on folding in folded files\r\n + you can handle your folds like in orgmode\r\n- navigate in headings or list items hierarchy\r\n + next, previous : any level\r\n + forward, backward : same level as current one\r\n + parent heading, upper level\r\n + child heading, lower level :\r\n - loosely speaking : first headline of level + 1, forward\r\n - strictly speaking : must be in the current subtree\r\n + go to another headline with prompt completion of full path\r\n- modify headings or list items\r\n + new headline or list item\r\n + select, yank, delete subtree\r\n + promote, demote heading or list item\r\n + move subtree up or down\r\n + move current subtree in another one (aka org-refile)\r\n- expand shortcut to template (aka org-structure-template)\r\n + markdown support limited to code blocks\r\n- links\r\n + store url at cursor\r\n + create link with url completion\r\n + goto link under or close to cursor\r\n + goto next\/previous link\r\n- tables\r\n + inside of table : align columns\r\n + outside of table : align following a pattern\r\n + add new row, colum\r\n + delete row, colum\r\n + move row up or down\r\n + move column left or right\r\n- cycle todo status\r\n- insert timestamp\r\n- export in another format using\r\n + pandoc\r\n + emacs\r\n + asciidoc or asciidoctor\r\n + view exported document\r\n- convert headings and links org <-> markdown\r\n\r\n# Differences with standard orgmode\r\n\r\n- speed keys are also available in first char of list item line\r\n- movements can\r\n + wrap around the end of the file\r\n + cross over a parent headline\r\n\r\n# Dependencies\r\n\r\nThe core part runs on its own.\r\n\r\nSome extra-features need external tools, see below.\r\n\r\n## Export\r\n\r\nIf you want to export your file to another format, you just need to have\r\npandoc installed, and the plugin takes care of the rest. For org files,\r\nit can also be done with emacs installed, at least for the formats\r\nsupported by orgmode.\r\n\r\nFor asciidoc files, you need to install asciidoc or asciidoctor.\r\n\r\n## Across files\r\n\r\nIf you want to add interactions between org or markdown files, you can\r\ninstall [wheel](https:\/\/github.com\/chimay\/wheel). With it, you can :\r\n\r\n- quickly jump to another org\/markdown\/whatever file\r\n- look for headlines in all orgmode or markdown files of a group (aka outline)\r\n- grep all your group files for special keywords, like TODO","4":"# What is it ?\r\n\r\nOrgan generalizes the great concepts of Orgmode to Markdown and any folded file. It is primarily focused on editing these documents with ease and agility.\r\n\r\n# More information\r\n\r\nSee the github repository :\r\n\r\n[organ](https:\/\/github.com\/chimay\/organ)\r\n\r\n# Compatibilty\r\n\r\nOrgan supports :\r\n\r\norg files\r\nmarkdown\r\nasciidoc : headings only\r\nfolded files with markers\r\nindent folded files : basic navigation only\r\nIt is written in vimscript and is compatible with both Vim and Neovim.\r\n\r\n# Features\r\n\r\n- folding based on headings in org and markdown files\r\n- headings base on folding in folded files\r\n + you can handle your folds like in orgmode\r\n- navigate in headings or list items hierarchy\r\n + next, previous : any level\r\n + forward, backward : same level as current one\r\n + parent heading, upper level\r\n + child heading, lower level :\r\n - loosely speaking : first headline of level + 1, forward\r\n - strictly speaking : must be in the current subtree\r\n + go to another headline with prompt completion of full path\r\n- modify headings or list items\r\n + new headline or list item\r\n + select, yank, delete subtree\r\n + promote, demote heading or list item\r\n + move subtree up or down\r\n + move current subtree in another one (aka org-refile)\r\n- expand shortcut to template (aka org-structure-template)\r\n + markdown support limited to code blocks\r\n- links\r\n + store url at cursor\r\n + create link with url completion\r\n + goto link under or close to cursor\r\n + goto next\/previous link\r\n- tables\r\n + inside of table : align columns\r\n + outside of table : align following a pattern\r\n + add new row, colum\r\n + delete row, colum\r\n + move row up or down\r\n + move column left or right\r\n- cycle todo status\r\n- insert timestamp\r\n- export in another format using\r\n + pandoc\r\n + emacs\r\n + asciidoc or asciidoctor\r\n + view exported document\r\n- convert headings and links org <-> markdown\r\n\r\n# Differences with standard orgmode\r\n\r\n- speed keys are also available in first char of list item line\r\n- movements can\r\n + wrap around the end of the file\r\n + cross over a parent headline\r\n\r\n# Dependencies\r\n\r\nThe core part runs on its own.\r\n\r\nSome extra-features need external tools, see below.\r\n\r\n## Export\r\n\r\nIf you want to export your file to another format, you just need to have\r\npandoc installed, and the plugin takes care of the rest. For org files,\r\nit can also be done with emacs installed, at least for the formats\r\nsupported by orgmode.\r\n\r\nFor asciidoc files, you need to install asciidoc or asciidoctor.\r\n\r\n## Across files\r\n\r\nIf you want to add interactions between org or markdown files, you can\r\ninstall [wheel](https:\/\/github.com\/chimay\/wheel). With it, you can :\r\n\r\n- quickly jump to another org\/markdown\/whatever file\r\n- look for headlines in all orgmode or markdown files of a group (aka outline)\r\n- grep all your group files for special keywords, like TODO","install_details":"","5":"","first_name":"chimay","6":"chimay","last_name":"orduval","7":"orduval","releases":[{"0":"6071","vim_version":"8.0","1":"8.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"organ-1.0.tar.gz","4":"organ-1.0.tar.gz","src_id":"28464","5":"28464","creation_date":"1683766115","6":"1683766115"}]},"6070":{"script_id":"6070","0":"6070","script_name":"GoSeigen","1":"GoSeigen","script_type":"color scheme","2":"color scheme","summary":"A programmer's color scheme","3":"A programmer's color scheme","description":"A homage of Go Seigen, a Chinese born Japonese professional go player. He was a legend in his time, one the most briliant minds of the last century.","4":"A homage of Go Seigen, a Chinese born Japonese professional go player. He was a legend in his time, one the most briliant minds of the last century.","install_details":"Just copy to to color scheme folder.","5":"Just copy to to color scheme folder.","first_name":"Gabor","6":"Gabor","last_name":"Urban","7":"Urban","releases":[{"0":"6070","vim_version":"7.4","1":"7.4","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"goseigen.vim","4":"goseigen.vim","src_id":"28459","5":"28459","creation_date":"1683642378","6":"1683642378"}]},"6069":{"script_id":"6069","0":"6069","script_name":"vim-helpme","1":"vim-helpme","script_type":"utility","2":"utility","summary":"Try this if you can't remember all that stuff!","3":"Try this if you can't remember all that stuff!","description":"Have you ever found yourself staring at a blinking cursor on Vim's command line, trying your hardest to remember what the command you're trying to perform is?\r\n\r\nAre you learning a new SuperCoolLanguage library but you could not really remember that specific command and you are too tired to go through all the API documentation to find it out?\r\n\r\nWell, I have both of these problems and this plugin may help you too.\r\n\r\nHelpMe! is nothing more than a tiny customizable popup menu for Vim 9.0+ that you can fill as you want and that you can recall whenever you want.\r\n\r\nChek :h helpme.txt to figure how to use it. \r\n","4":"Have you ever found yourself staring at a blinking cursor on Vim's command line, trying your hardest to remember what the command you're trying to perform is?\r\n\r\nAre you learning a new SuperCoolLanguage library but you could not really remember that specific command and you are too tired to go through all the API documentation to find it out?\r\n\r\nWell, I have both of these problems and this plugin may help you too.\r\n\r\nHelpMe! is nothing more than a tiny customizable popup menu for Vim 9.0+ that you can fill as you want and that you can recall whenever you want.\r\n\r\nChek :h helpme.txt to figure how to use it. \r\n","install_details":"","5":"","first_name":"Ubaldo","6":"Ubaldo","last_name":"Tiberi","7":"Tiberi","releases":[{"0":"6069","vim_version":"9.0","1":"9.0","script_version":"v1.0.1","2":"v1.0.1","version_comment":"* Updated License.","3":"* Updated License.","package":"vim-helpme-1.0.1.zip","4":"vim-helpme-1.0.1.zip","src_id":"28491","5":"28491","creation_date":"1685551999","6":"1685551999"}]},"6068":{"script_id":"6068","0":"6068","script_name":"vim-outline","1":"vim-outline","script_type":"utility","2":"utility","summary":"A simple outline sketcher for Vim.","3":"A simple outline sketcher for Vim.","description":"Vim-outline parse your current buffer and slam an outline in a side-window.\r\n\r\nThat's all!\r\n\r\nWell, in reality is not, in-fact Vim-outline further provides you with the following features:\r\n\r\n- Locate your current position on the outline,\r\n- Jump from outline entries to the corresponding buffer lines,\r\n- Feed you with random motivational quote if a filetype is not supported. [Cringe mode ON!]\r\n\r\nAt the time I was working with Python and Vim9script, hence Python and Vim9Script are supported by default, but you can easily add other languages. See :h OutlineAddNewLanguages.\r\n\r\nGithub repo here: \"https:\/\/github.com\/ubaldot\/vim-outline\"","4":"Vim-outline parse your current buffer and slam an outline in a side-window.\r\n\r\nThat's all!\r\n\r\nWell, in reality is not, in-fact Vim-outline further provides you with the following features:\r\n\r\n- Locate your current position on the outline,\r\n- Jump from outline entries to the corresponding buffer lines,\r\n- Feed you with random motivational quote if a filetype is not supported. [Cringe mode ON!]\r\n\r\nAt the time I was working with Python and Vim9script, hence Python and Vim9Script are supported by default, but you can easily add other languages. See :h OutlineAddNewLanguages.\r\n\r\nGithub repo here: \"https:\/\/github.com\/ubaldot\/vim-outline\"","install_details":"","5":"","first_name":"Ubaldo","6":"Ubaldo","last_name":"Tiberi","7":"Tiberi","releases":[{"0":"6068","vim_version":"9.0","1":"9.0","script_version":"v1.0.2","2":"v1.0.2","version_comment":"* Updated License.","3":"* Updated License.","package":"vim-outline-1.0.2.zip","4":"vim-outline-1.0.2.zip","src_id":"28490","5":"28490","creation_date":"1685551878","6":"1685551878"}]},"6067":{"script_id":"6067","0":"6067","script_name":"vim-replica","1":"vim-replica","script_type":"utility","2":"utility","summary":"Enjoy Jupyter through Vim!","3":"Enjoy Jupyter through Vim!","description":"Replica allows REPL shells such as IPython or Julia inside Vim in a seamless way.\r\n\r\nReplica supports the following key features:\r\n\r\n- Sending lines, files and code-cells to a REPL,\r\n- Code-cells highlighting.\r\n\r\nEach REPL is a jupyter console initiated with a specific kernel running in a terminal buffer. \r\nFor each filetype Replica provides you with one available REPL to send text in.\r\n\r\nRepo on GitHub \"https:\/\/github.com\/ubaldot\/vim-replica\"","4":"Replica allows REPL shells such as IPython or Julia inside Vim in a seamless way.\r\n\r\nReplica supports the following key features:\r\n\r\n- Sending lines, files and code-cells to a REPL,\r\n- Code-cells highlighting.\r\n\r\nEach REPL is a jupyter console initiated with a specific kernel running in a terminal buffer. \r\nFor each filetype Replica provides you with one available REPL to send text in.\r\n\r\nRepo on GitHub \"https:\/\/github.com\/ubaldot\/vim-replica\"","install_details":"Replica is entirely written in Vim9script so you need at least Vim 9.0.\r\nIf you are using Windows be sure that Python and Vim are both 32- or 64-bit.\r\nYou also need jupyter console and the kernels of the language you would like to use.","5":"Replica is entirely written in Vim9script so you need at least Vim 9.0.\r\nIf you are using Windows be sure that Python and Vim are both 32- or 64-bit.\r\nYou also need jupyter console and the kernels of the language you would like to use.","first_name":"Ubaldo","6":"Ubaldo","last_name":"Tiberi","7":"Tiberi","releases":[{"0":"6067","vim_version":"9.0","1":"9.0","script_version":"v1.0.3","2":"v1.0.3","version_comment":"* Updated License.","3":"* Updated License.","package":"vim-replica-1.0.3.zip","4":"vim-replica-1.0.3.zip","src_id":"28489","5":"28489","creation_date":"1685551759","6":"1685551759"}]},"6066":{"script_id":"6066","0":"6066","script_name":"vi-si-weg","1":"vi-si-weg","script_type":"utility","2":"utility","summary":"Toggle text into tags","3":"Toggle text into tags","description":" Toggles the tag under cursor (normal mode).\r\n\r\nTags are simply []\r\n\r\nWhen closed the have a [name<] which allows them to be opened into [name]. Simple and effective. And with conceal, also beautiful.\r\n\r\nTags can be named automatically (sequential numbers, hidden or in subfolder) or manually named.","4":" Toggles the tag under cursor (normal mode).\r\n\r\nTags are simply []\r\n\r\nWhen closed the have a [name<] which allows them to be opened into [name]. Simple and effective. And with conceal, also beautiful.\r\n\r\nTags can be named automatically (sequential numbers, hidden or in subfolder) or manually named.","install_details":"Download here or clone form \r\nhttps:\/\/github.com\/PhilGrunewald\/vi-si-weg\r\n\r\nPlace inside your plugin location\r\n","5":"Download here or clone form \r\nhttps:\/\/github.com\/PhilGrunewald\/vi-si-weg\r\n\r\nPlace inside your plugin location\r\n","first_name":"Phil","6":"Phil","last_name":"Grunewald","7":"Grunewald","releases":[{"0":"6066","vim_version":"8.0","1":"8.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"vi-si-weg.zip","4":"vi-si-weg.zip","src_id":"28436","5":"28436","creation_date":"1682835373","6":"1682835373"}]},"6064":{"script_id":"6064","0":"6064","script_name":"vim-py-kid","1":"vim-py-kid","script_type":"ftplugin","2":"ftplugin","summary":"Block-wise python script execution in vim (bit like Jupyter)","3":"Block-wise python script execution in vim (bit like Jupyter)","description":"Break up a python script into blocks. Blocks are separated with lines starting with:\r\n#>\r\n\r\nSince the `#` renders the line as a comment, the script remains compatible to be run in any other environment.\r\n\r\n opens the terminal in a split view to present the output of the current block.\r\n\r\nAll variables are stored ('shelved') and picked up when executing subsequent blocks.\r\n\r\nThe state of all stored variables can be inspected with this line:\r\n#<\r\n\r\nAny line starting with > (even if indented) gets converted into a print\r\nstatement. E.g.\r\n\r\n >\"bob\"\r\n\r\nbecomes\r\n\r\n print(\"bob\")\r\n\r\nafter execution. This is just for laziness. It avoids having to type `print` and putting brackets around the statement (speaking like a disgruntled python2 user).","4":"Break up a python script into blocks. Blocks are separated with lines starting with:\r\n#>\r\n\r\nSince the `#` renders the line as a comment, the script remains compatible to be run in any other environment.\r\n\r\n opens the terminal in a split view to present the output of the current block.\r\n\r\nAll variables are stored ('shelved') and picked up when executing subsequent blocks.\r\n\r\nThe state of all stored variables can be inspected with this line:\r\n#<\r\n\r\nAny line starting with > (even if indented) gets converted into a print\r\nstatement. E.g.\r\n\r\n >\"bob\"\r\n\r\nbecomes\r\n\r\n print(\"bob\")\r\n\r\nafter execution. This is just for laziness. It avoids having to type `print` and putting brackets around the statement (speaking like a disgruntled python2 user).","install_details":"Plug from https:\/\/github.com\/PhilGrunewald\/vim-py-kid\r\n\r\nOR\r\ncopy downloaded folder into your plugin folder\r\n\r\nPython dependencies: sys, shelve, types, pandas, datetime","5":"Plug from https:\/\/github.com\/PhilGrunewald\/vim-py-kid\r\n\r\nOR\r\ncopy downloaded folder into your plugin folder\r\n\r\nPython dependencies: sys, shelve, types, pandas, datetime","first_name":"Phil","6":"Phil","last_name":"Grunewald","7":"Grunewald","releases":[{"0":"6064","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"vim-py.zip","4":"vim-py.zip","src_id":"28422","5":"28422","creation_date":"1682140959","6":"1682140959"}]},"6063":{"script_id":"6063","0":"6063","script_name":"vim-table","1":"vim-table","script_type":"ftplugin","2":"ftplugin","summary":"Edit tabular data with the ease of vim","3":"Edit tabular data with the ease of vim","description":"This vim plugin was created to simply lay out and edit tables. \r\nFor some reason spreadsheets have taken over and there wasn't \r\nanything out there that brought the simplicity of vim editing\r\nto tables. Visidata and Sc-im are powerful tools, but often I\r\njust want to list information, without fancy spreadsheet tools.\r\n\r\nVim-table let's you\r\n\r\n- size column widths\r\n- conceal long lines\r\n- move row, columns and cells around\r\n- auto populate sequential numbers\r\n- auto advances in rows or columns\r\n\r\n","4":"This vim plugin was created to simply lay out and edit tables. \r\nFor some reason spreadsheets have taken over and there wasn't \r\nanything out there that brought the simplicity of vim editing\r\nto tables. Visidata and Sc-im are powerful tools, but often I\r\njust want to list information, without fancy spreadsheet tools.\r\n\r\nVim-table let's you\r\n\r\n- size column widths\r\n- conceal long lines\r\n- move row, columns and cells around\r\n- auto populate sequential numbers\r\n- auto advances in rows or columns\r\n\r\n","install_details":"Download here or clone from:\r\nhttps:\/\/github.com\/PhilGrunewald\/vim-table\r\n\r\nPlace the `vim-table` folder inside your vim `plugged` folder.\r\n\r\nOR (neovim)\r\n\r\nadd this to `init.vim`:\r\n\r\n call plug#begin('$NVIM\/plugged')\r\n Plug 'philgrunewald\/vim-table'\r\n call plug#end()\r\n\r\nwhere $NVIM is the location of your `plugged` folder. Then follow the :UpdateRemotePlugins procedures\r\n\r\nOR (more manually)\r\n\r\nPlace the .vim files in their respective folders (`after\/ftplugin`, `after\/syntax`) and add the line in `ftdetect` to your .vimrc.","5":"Download here or clone from:\r\nhttps:\/\/github.com\/PhilGrunewald\/vim-table\r\n\r\nPlace the `vim-table` folder inside your vim `plugged` folder.\r\n\r\nOR (neovim)\r\n\r\nadd this to `init.vim`:\r\n\r\n call plug#begin('$NVIM\/plugged')\r\n Plug 'philgrunewald\/vim-table'\r\n call plug#end()\r\n\r\nwhere $NVIM is the location of your `plugged` folder. Then follow the :UpdateRemotePlugins procedures\r\n\r\nOR (more manually)\r\n\r\nPlace the .vim files in their respective folders (`after\/ftplugin`, `after\/syntax`) and add the line in `ftdetect` to your .vimrc.","first_name":"Phil","6":"Phil","last_name":"Grunewald","7":"Grunewald","releases":[{"0":"6063","vim_version":"7.0","1":"7.0","script_version":"1.1","2":"1.1","version_comment":"Added functionality to insert the sum of a column (type `==` OR :Sum) or its average (:Avg) for all numerical values above the current row.","3":"Added functionality to insert the sum of a column (type `==` OR :Sum) or its average (:Avg) for all numerical values above the current row.","package":"vim-table.zip","4":"vim-table.zip","src_id":"28424","5":"28424","creation_date":"1682209772","6":"1682209772"},{"0":"6063","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"vim-table.zip","4":"vim-table.zip","src_id":"28419","5":"28419","creation_date":"1682094662","6":"1682094662"}]},"6062":{"script_id":"6062","0":"6062","script_name":"gpt-vim","1":"gpt-vim","script_type":"utility","2":"utility","summary":"brings chat gpt to Vim and NVim","3":"brings chat gpt to Vim and NVim","description":"# vim-gpt\r\n\r\nThis plugin brings chat gpt to Vim and NVim\r\nThe purpose of this pugin is to assist you for your various development tasks.\r\n\r\nDemo time: https:\/\/github.com\/kamou\/gpt-vim\/blob\/master\/uml2rust.gif\r\n## Current Features\r\n\r\n - Chat with GPT (currently gpt3.5-turbo) in a separate buffer. The output is in markdown.\r\n - GPT can recall previous messages from the current session.\r\n - Selected text\/code is appended to the prompt.\r\n - GPT is aware of the language of your current buffer.\r\n - Multiple sessions. You can save a session and continue the conversation later if needed.\r\n\r\n## Requirements\r\n\r\nRequirement can be installed using the following command:\r\n```\r\npip3 install -r requirements.txt\r\n```\r\n\r\n## Installation\r\n```vim\r\nPlug 'kamou\/gpt-vim'\r\n```\r\n\r\n## Available commands\r\n```\r\n:call gpt#Assist(0) # Launch the prompt\r\n:'<,'>call gpt#Assist(1) # Launch the prompt and append the current selection\r\n```\r\n\r\n## Default keymapping configuration\r\n```\r\nnmap gpa (gpt-vim-assist)\r\nxmap gpa (gpt-vim-assist-vis)\r\nvmap gpa (gpt-vim-assist-vis)\r\n```\r\nYou may update it in you .vimrc file.\r\n\r\n## GPT buffer keys\r\n - `r` reset current session memory, GPT will forget everything, the buffer will be cleared\r\n - `q` close gpt buffer. Memory is kept untouched, gpt will recall previous (most recent) messages.\r\n - `s` save the current session history\r\n - `L` list previously saved sessions (press enter to load selected session)\r\n - `c` Cancel the current stream. (The answer will be lost, and not saved in the database)\r\n - `Y` Enter Yank Mode. [Experimental, mapping willl change soon]\r\n\r\n## Yank Mode\r\n - `j` Cycle down to next fenced code block.\r\n - `k` Cycle up to next fenced code block.\r\n - `` Copy current block and leave Yank Mode.\r\n\r\n## Session list keys\r\n - `q` close the list\r\n - `d` delete the session under the cursor\r\n - `` select the session under the cursor\r\n - `s`: Open the conversation under the cursor in a horizontal split.\r\n - `v`: Open the conversation under the cursor in a vertical split.\r\n\r\n","4":"# vim-gpt\r\n\r\nThis plugin brings chat gpt to Vim and NVim\r\nThe purpose of this pugin is to assist you for your various development tasks.\r\n\r\nDemo time: https:\/\/github.com\/kamou\/gpt-vim\/blob\/master\/uml2rust.gif\r\n## Current Features\r\n\r\n - Chat with GPT (currently gpt3.5-turbo) in a separate buffer. The output is in markdown.\r\n - GPT can recall previous messages from the current session.\r\n - Selected text\/code is appended to the prompt.\r\n - GPT is aware of the language of your current buffer.\r\n - Multiple sessions. You can save a session and continue the conversation later if needed.\r\n\r\n## Requirements\r\n\r\nRequirement can be installed using the following command:\r\n```\r\npip3 install -r requirements.txt\r\n```\r\n\r\n## Installation\r\n```vim\r\nPlug 'kamou\/gpt-vim'\r\n```\r\n\r\n## Available commands\r\n```\r\n:call gpt#Assist(0) # Launch the prompt\r\n:'<,'>call gpt#Assist(1) # Launch the prompt and append the current selection\r\n```\r\n\r\n## Default keymapping configuration\r\n```\r\nnmap gpa (gpt-vim-assist)\r\nxmap gpa (gpt-vim-assist-vis)\r\nvmap gpa (gpt-vim-assist-vis)\r\n```\r\nYou may update it in you .vimrc file.\r\n\r\n## GPT buffer keys\r\n - `r` reset current session memory, GPT will forget everything, the buffer will be cleared\r\n - `q` close gpt buffer. Memory is kept untouched, gpt will recall previous (most recent) messages.\r\n - `s` save the current session history\r\n - `L` list previously saved sessions (press enter to load selected session)\r\n - `c` Cancel the current stream. (The answer will be lost, and not saved in the database)\r\n - `Y` Enter Yank Mode. [Experimental, mapping willl change soon]\r\n\r\n## Yank Mode\r\n - `j` Cycle down to next fenced code block.\r\n - `k` Cycle up to next fenced code block.\r\n - `` Copy current block and leave Yank Mode.\r\n\r\n## Session list keys\r\n - `q` close the list\r\n - `d` delete the session under the cursor\r\n - `` select the session under the cursor\r\n - `s`: Open the conversation under the cursor in a horizontal split.\r\n - `v`: Open the conversation under the cursor in a vertical split.\r\n\r\n","install_details":"## Requirements\r\n\r\n - an openai [api key](https:\/\/platform.openai.com\/account\/api-keys) (add `g:gpt_api_key` to your config)\r\n - sqlite3, openai and tiktoken python package\r\n ```sh\r\n pip install sqlite3\r\n pip install openai\r\n pip install tiktoken\r\n ```\r\n\r\n## Installation\r\n```vim\r\nPlug 'kamou\/gpt-vim'\r\n```\r\n\r\n## Available commands\r\n```\r\n:call gpt#assist([sessionname]) # Launch the prompt\r\n:'<,'>call gpt#visual_assist([sessionname]) # Launch the prompt and append the current selection\r\n```\r\n\r\n\r\n## Sample keymapping configuration\r\n```\r\nmap :call gpt#assist()\r\nxnoremap :'<,'>call gpt#visual_assist()\r\nvnoremap :'<,'>call gpt#visual_assist()\r\n```","5":"## Requirements\r\n\r\n - an openai [api key](https:\/\/platform.openai.com\/account\/api-keys) (add `g:gpt_api_key` to your config)\r\n - sqlite3, openai and tiktoken python package\r\n ```sh\r\n pip install sqlite3\r\n pip install openai\r\n pip install tiktoken\r\n ```\r\n\r\n## Installation\r\n```vim\r\nPlug 'kamou\/gpt-vim'\r\n```\r\n\r\n## Available commands\r\n```\r\n:call gpt#assist([sessionname]) # Launch the prompt\r\n:'<,'>call gpt#visual_assist([sessionname]) # Launch the prompt and append the current selection\r\n```\r\n\r\n\r\n## Sample keymapping configuration\r\n```\r\nmap :call gpt#assist()\r\nxnoremap :'<,'>call gpt#visual_assist()\r\nvnoremap :'<,'>call gpt#visual_assist()\r\n```","first_name":"ayman","6":"ayman","last_name":"khamouma","7":"khamouma","releases":[{"0":"6062","vim_version":"8.1","1":"8.1","script_version":"0.10","2":"0.10","version_comment":"Bump openai python package version","3":"Bump openai python package version","package":"gpt-vim.tgz","4":"gpt-vim.tgz","src_id":"28584","5":"28584","creation_date":"1704122918","6":"1704122918"},{"0":"6062","vim_version":"9.0","1":"9.0","script_version":"0.9","2":"0.9","version_comment":"The assistant can now execute generated python and lua code just like int chat-gpt interpreter mode\r\nThe assistant can also search the web (google, ddg and wikipedia) and read web pages content.","3":"The assistant can now execute generated python and lua code just like int chat-gpt interpreter mode\r\nThe assistant can also search the web (google, ddg and wikipedia) and read web pages content.","package":"gpt-vim.tgz","4":"gpt-vim.tgz","src_id":"28543","5":"28543","creation_date":"1693815766","6":"1693815766"},{"0":"6062","vim_version":"8.0","1":"8.0","script_version":"0.8","2":"0.8","version_comment":"more refactoring. multiple chat buffers support. fenced code block Yank Mode support","3":"more refactoring. multiple chat buffers support. fenced code block Yank Mode support","package":"gpt-vim.tgz","4":"gpt-vim.tgz","src_id":"28434","5":"28434","creation_date":"1682606433","6":"1682606433"},{"0":"6062","vim_version":"8.0","1":"8.0","script_version":"0.7","2":"0.7","version_comment":"Fix crash on missing database","3":"Fix crash on missing database","package":"gpt-vim.tgz","4":"gpt-vim.tgz","src_id":"28430","5":"28430","creation_date":"1682374584","6":"1682374584"},{"0":"6062","vim_version":"8.0","1":"8.0","script_version":"0.6","2":"0.6","version_comment":"Refactoring, Bugfixes, and a doc generated by the plugin \u00c2\u00af\\_(ツ)_\/\u00c2\u00af","3":"Refactoring, Bugfixes, and a doc generated by the plugin \u00c2\u00af\\_(ツ)_\/\u00c2\u00af","package":"gpt-vim.tgz","4":"gpt-vim.tgz","src_id":"28427","5":"28427","creation_date":"1682366833","6":"1682366833"},{"0":"6062","vim_version":"8.0","1":"8.0","script_version":"0.5","2":"0.5","version_comment":"Bugfix (empty list after buffer quit)","3":"Bugfix (empty list after buffer quit)","package":"gpt-vim.tgz","4":"gpt-vim.tgz","src_id":"28423","5":"28423","creation_date":"1682207907","6":"1682207907"},{"0":"6062","vim_version":"8.0","1":"8.0","script_version":"0.4","2":"0.4","version_comment":"Bugfixes + ability to delete a session.","3":"Bugfixes + ability to delete a session.","package":"gpt-vim.tgz","4":"gpt-vim.tgz","src_id":"28421","5":"28421","creation_date":"1682139894","6":"1682139894"},{"0":"6062","vim_version":"7.0","1":"7.0","script_version":"0.2","2":"0.2","version_comment":"Improved sessions","3":"Improved sessions","package":"gpt-vim.tgz","4":"gpt-vim.tgz","src_id":"28417","5":"28417","creation_date":"1682022424","6":"1682022424"},{"0":"6062","vim_version":"8.0","1":"8.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"gpt-vim.tgz","4":"gpt-vim.tgz","src_id":"28416","5":"28416","creation_date":"1681949562","6":"1681949562"}]},"6061":{"script_id":"6061","0":"6061","script_name":"template.vim","1":"template.vim","script_type":"ftplugin","2":"ftplugin","summary":"A template plugin for LaTeX","3":"A template plugin for LaTeX","description":"A template plugin for LaTeX\r\n\r\n1. In the normal mode, press , the command line will appear the *.tex templates under the dir ~\/.vim\/ftplugin\/tex\/template\/, select the No., it will insert the selected template at the beginning of the document.\r\n2. In the normal mode, press ( for the old version), the command line will appear the *.txt templates under the dir ~\/.vim\/ftplugin\/tex\/template\/, select the No., it will insert the selected template after the cursor line.\r\n3. You can put your own templates in dir ~\/.vim\/ftplugin\/tex\/template\/\r\n\r\nhttps:\/\/github.com\/fangyq09\/VimTeXtric","4":"A template plugin for LaTeX\r\n\r\n1. In the normal mode, press , the command line will appear the *.tex templates under the dir ~\/.vim\/ftplugin\/tex\/template\/, select the No., it will insert the selected template at the beginning of the document.\r\n2. In the normal mode, press ( for the old version), the command line will appear the *.txt templates under the dir ~\/.vim\/ftplugin\/tex\/template\/, select the No., it will insert the selected template after the cursor line.\r\n3. You can put your own templates in dir ~\/.vim\/ftplugin\/tex\/template\/\r\n\r\nhttps:\/\/github.com\/fangyq09\/VimTeXtric","install_details":"extract the temp.7z, copy the template.vim and the template dir to ~\/.vim\/ftplugin\/tex\/","5":"extract the temp.7z, copy the template.vim and the template dir to ~\/.vim\/ftplugin\/tex\/","first_name":"Yangqin","6":"Yangqin","last_name":"Fang","7":"Fang","releases":[{"0":"6061","vim_version":"7.0","1":"7.0","script_version":"1.2","2":"1.2","version_comment":"To prevent accidental operation, a confirmation dialog box has been added.","3":"To prevent accidental operation, a confirmation dialog box has been added.","package":"temp.7z","4":"temp.7z","src_id":"28449","5":"28449","creation_date":"1683233974","6":"1683233974"},{"0":"6061","vim_version":"7.0","1":"7.0","script_version":"1.1","2":"1.1","version_comment":"Initial upload","3":"Initial upload","package":"template.7z","4":"template.7z","src_id":"28409","5":"28409","creation_date":"1681264738","6":"1681264738"}]},"6060":{"script_id":"6060","0":"6060","script_name":"tex_compile.vim","1":"tex_compile.vim","script_type":"ftplugin","2":"ftplugin","summary":"A compile plugin for LaTeX","3":"A compile plugin for LaTeX","description":"Usage:\r\nIn you tex source file, in noraml mode, press to run pdflatex, press to run xelatex, press to compile bibtex or biblatex.\r\nIn case you split your project with several chapters, for example, chapter1.tex, chapter2.tex, ..., in any chapter, you press the shortcuts, it will find the main tex file automatically.\r\n\r\nhttps:\/\/github.com\/fangyq09\/VimTeXtric","4":"Usage:\r\nIn you tex source file, in noraml mode, press to run pdflatex, press to run xelatex, press to compile bibtex or biblatex.\r\nIn case you split your project with several chapters, for example, chapter1.tex, chapter2.tex, ..., in any chapter, you press the shortcuts, it will find the main tex file automatically.\r\n\r\nhttps:\/\/github.com\/fangyq09\/VimTeXtric","install_details":"Put the latexmk.vim in the dir ~\/.vim\/compiler\/, and put the compiler.vim in the dir ~\/.vim\/ftplugin\/tex\/\r\n\r\nOn linux, you need zathura pdf to be installed, and for the backward search, you should put the following two commands into ~\/.config\/zathura\/zathurarc:\r\nset synctex true\r\nset synctex-editor-command \"gvim --servername GVIM10000 --remote-silent +exec\\ %{line} %{input}\"\r\n\r\nOn windows you need SumatraPDF to be installed, and it should be in PATH environment variable, or you alter the SumatraSynctexForward(file) function in the vimscript. ","5":"Put the latexmk.vim in the dir ~\/.vim\/compiler\/, and put the compiler.vim in the dir ~\/.vim\/ftplugin\/tex\/\r\n\r\nOn linux, you need zathura pdf to be installed, and for the backward search, you should put the following two commands into ~\/.config\/zathura\/zathurarc:\r\nset synctex true\r\nset synctex-editor-command \"gvim --servername GVIM10000 --remote-silent +exec\\ %{line} %{input}\"\r\n\r\nOn windows you need SumatraPDF to be installed, and it should be in PATH environment variable, or you alter the SumatraSynctexForward(file) function in the vimscript. ","first_name":"Yangqin","6":"Yangqin","last_name":"Fang","7":"Fang","releases":[{"0":"6060","vim_version":"7.0","1":"7.0","script_version":"1.2","2":"1.2","version_comment":"fixed a bug, and make it support both bibtex and biblatex","3":"fixed a bug, and make it support both bibtex and biblatex","package":"vim.7z","4":"vim.7z","src_id":"28420","5":"28420","creation_date":"1682116444","6":"1682116444"},{"0":"6060","vim_version":"7.0","1":"7.0","script_version":"1.1","2":"1.1","version_comment":"Initial upload","3":"Initial upload","package":"vim.7z","4":"vim.7z","src_id":"28406","5":"28406","creation_date":"1680934243","6":"1680934243"}]},"6059":{"script_id":"6059","0":"6059","script_name":"omni.vim","1":"omni.vim","script_type":"ftplugin","2":"ftplugin","summary":"An omni completion plugin for LaTeX","3":"An omni completion plugin for LaTeX","description":"The best omni completion plugin for writing LaTeX in vim.\r\n\r\nUsage: \r\nExample 1. after the command \"\\input{\" , you press Ctrl-x Ctrl-o, you will get a list of *.tex files under the current pwd.\r\nExample 2. In you vim editor, in the insert mode, after the command \"\\setmainfont{\", press Ctrl-x Ctrl-o, you will get a list of fonts\r\nExample 3. after \\includepdf{, press Ctrl-x Ctrl-o, you will get a list of *.pdf files.\r\nExample 4. after \\includegraphics{, press Ctrl-x Ctrl-o, you will get a list of pictures.\r\nExample 5. after \\usepackage{, press Ctrl-x Ctrl-o, you will get a list of packages.\r\nExample 6. after \\cite{, press Ctrl-x Ctrl-o, you will get a list of bibitems in you bibtex sourece.\r\nExample 6. after \\ref{, press Ctrl-x Ctrl-o, you will get a list of labels in your tex sourece.\r\n\r\nIt support \\anyprefix, \\input{...}, \\include{...}, \\usepackage[...]{...}, \\RequirePackage[...]{...}, \r\n\\setmainfont[...]{...}, \\setsanfont{...}, \\setmonofont{...}, \\setmathfont{...}, \\setCJKmainfont[...]{...}, \r\n\\includepdf[...]{...}, \\includepdfmerge[...]{...}, \\includegraphics[...]{...}, \r\n\\cite[...]{...}, \\ref{...}, \\eqref{...}, \\begin{...}, \\end{...}.\r\n\r\nYou can write any of your own prefered commands into ~\/.vim\/tex\/completion\/commands.txt, and any of environment names into ~\/.vim\/tex\/completion\/environments.txt, etc.\r\n\r\nClick the following link to see the pictures for the usage and the installation place. \r\nhttps:\/\/github.com\/fangyq09\/VimTeXtric","4":"The best omni completion plugin for writing LaTeX in vim.\r\n\r\nUsage: \r\nExample 1. after the command \"\\input{\" , you press Ctrl-x Ctrl-o, you will get a list of *.tex files under the current pwd.\r\nExample 2. In you vim editor, in the insert mode, after the command \"\\setmainfont{\", press Ctrl-x Ctrl-o, you will get a list of fonts\r\nExample 3. after \\includepdf{, press Ctrl-x Ctrl-o, you will get a list of *.pdf files.\r\nExample 4. after \\includegraphics{, press Ctrl-x Ctrl-o, you will get a list of pictures.\r\nExample 5. after \\usepackage{, press Ctrl-x Ctrl-o, you will get a list of packages.\r\nExample 6. after \\cite{, press Ctrl-x Ctrl-o, you will get a list of bibitems in you bibtex sourece.\r\nExample 6. after \\ref{, press Ctrl-x Ctrl-o, you will get a list of labels in your tex sourece.\r\n\r\nIt support \\anyprefix, \\input{...}, \\include{...}, \\usepackage[...]{...}, \\RequirePackage[...]{...}, \r\n\\setmainfont[...]{...}, \\setsanfont{...}, \\setmonofont{...}, \\setmathfont{...}, \\setCJKmainfont[...]{...}, \r\n\\includepdf[...]{...}, \\includepdfmerge[...]{...}, \\includegraphics[...]{...}, \r\n\\cite[...]{...}, \\ref{...}, \\eqref{...}, \\begin{...}, \\end{...}.\r\n\r\nYou can write any of your own prefered commands into ~\/.vim\/tex\/completion\/commands.txt, and any of environment names into ~\/.vim\/tex\/completion\/environments.txt, etc.\r\n\r\nClick the following link to see the pictures for the usage and the installation place. \r\nhttps:\/\/github.com\/fangyq09\/VimTeXtric","install_details":"extract the 7zip file, and copy the \"omni.vim\" and the \"completion\" directory to ~\/.vim\/ftplugin\/tex\/ on linux system, or put they into $home\\vimfiles\\ftplugin\\tex\\ on windows system.","5":"extract the 7zip file, and copy the \"omni.vim\" and the \"completion\" directory to ~\/.vim\/ftplugin\/tex\/ on linux system, or put they into $home\\vimfiles\\ftplugin\\tex\\ on windows system.","first_name":"Yangqin","6":"Yangqin","last_name":"Fang","7":"Fang","releases":[{"0":"6059","vim_version":"7.0","1":"7.0","script_version":"1.4","2":"1.4","version_comment":"fixed a bug","3":"fixed a bug","package":"tex.7z","4":"tex.7z","src_id":"28455","5":"28455","creation_date":"1683347845","6":"1683347845"},{"0":"6059","vim_version":"7.0","1":"7.0","script_version":"1.3","2":"1.3","version_comment":"some bug fixed, and added some new features","3":"some bug fixed, and added some new features","package":"tex.7z","4":"tex.7z","src_id":"28414","5":"28414","creation_date":"1681836293","6":"1681836293"},{"0":"6059","vim_version":"7.0","1":"7.0","script_version":"1.1","2":"1.1","version_comment":"Initial upload","3":"Initial upload","package":"ftplugin.7z","4":"ftplugin.7z","src_id":"28405","5":"28405","creation_date":"1680843139","6":"1680843139"}]},"6058":{"script_id":"6058","0":"6058","script_name":"parbermad.vim","1":"parbermad.vim","script_type":"color scheme","2":"color scheme","summary":"A color scheme","3":"A color scheme","description":"A color scheme file, especially suitable for LaTeX\r\n\r\nhttps:\/\/github.com\/fangyq09\/VimTeXtric","4":"A color scheme file, especially suitable for LaTeX\r\n\r\nhttps:\/\/github.com\/fangyq09\/VimTeXtric","install_details":"put it into dir \"~\/.vim\/colors\/\", then write \"colorscheme parbermad\" into your vimrc\r\n","5":"put it into dir \"~\/.vim\/colors\/\", then write \"colorscheme parbermad\" into your vimrc\r\n","first_name":"Yangqin","6":"Yangqin","last_name":"Fang","7":"Fang","releases":[{"0":"6058","vim_version":"7.0","1":"7.0","script_version":"1.1","2":"1.1","version_comment":"Initial upload","3":"Initial upload","package":"parbermad.vim","4":"parbermad.vim","src_id":"28403","5":"28403","creation_date":"1680716104","6":"1680716104"}]},"6057":{"script_id":"6057","0":"6057","script_name":"tex_fold.vim","1":"tex_fold.vim","script_type":"ftplugin","2":"ftplugin","summary":"A manual LaTeX fold plugin by analogy to syntax fold","3":"A manual LaTeX fold plugin by analogy to syntax fold","description":"This plugin provides a LaTeX syntax fold similar to syntax folding. It is similar to the folding scheme provided by latex-suite but is faster and can avoid the side effects of nested environments.\r\n\r\nhttps:\/\/github.com\/fangyq09\/VimTeXtric","4":"This plugin provides a LaTeX syntax fold similar to syntax folding. It is similar to the folding scheme provided by latex-suite but is faster and can avoid the side effects of nested environments.\r\n\r\nhttps:\/\/github.com\/fangyq09\/VimTeXtric","install_details":"Put it into the directory ~\/.vim\/ftplugin\/","5":"Put it into the directory ~\/.vim\/ftplugin\/","first_name":"Yangqin","6":"Yangqin","last_name":"Fang","7":"Fang","releases":[{"0":"6057","vim_version":"7.0","1":"7.0","script_version":"1.5","2":"1.5","version_comment":"fix bugs","3":"fix bugs","package":"tex_fold.vim","4":"tex_fold.vim","src_id":"28501","5":"28501","creation_date":"1687025543","6":"1687025543"},{"0":"6057","vim_version":"7.0","1":"7.0","script_version":"1.3","2":"1.3","version_comment":"fixed a bug, for very loog chapter\/section\/subsection names","3":"fixed a bug, for very loog chapter\/section\/subsection names","package":"tex_fold.vim","4":"tex_fold.vim","src_id":"28461","5":"28461","creation_date":"1683752713","6":"1683752713"}]},"6056":{"script_id":"6056","0":"6056","script_name":"octave.vim","1":"octave.vim","script_type":"indent","2":"indent","summary":"Indent file for the GNU Octave language","3":"Indent file for the GNU Octave language","description":"This file provides automatic indenting for the GNU Octave programming language.\r\n\r\nFeatures\r\n* Indents entire Octave grammar (endwhile, endfor, etc.), not just Matlab keywords\r\n* Indents according to best practices of Octave Core Maintainers\r\n\r\nNotes\r\n* Simplistic algorithm is not a true replacement for a specialized indenter\r\n\r\nFor Octave syntax highlighting see vimscript #3600.","4":"This file provides automatic indenting for the GNU Octave programming language.\r\n\r\nFeatures\r\n* Indents entire Octave grammar (endwhile, endfor, etc.), not just Matlab keywords\r\n* Indents according to best practices of Octave Core Maintainers\r\n\r\nNotes\r\n* Simplistic algorithm is not a true replacement for a specialized indenter\r\n\r\nFor Octave syntax highlighting see vimscript #3600.","install_details":"Syntax file install on a UNIX-like system\r\n\r\n1) mkdir -p ~\/.vim\/indent\r\n2) cp octave.vim ~\/.vim\/indent\/\r\n3) Add the following lines to your ~\/.vimrc to have ViM use the file\r\n\r\n----- SNIP -----\r\n\" Octave filetype detection\r\naugroup filetypedetect\r\n au! BufRead,BufNewFile *.m set filetype=octave\r\naugroup END\r\n----- SNIP -----","5":"Syntax file install on a UNIX-like system\r\n\r\n1) mkdir -p ~\/.vim\/indent\r\n2) cp octave.vim ~\/.vim\/indent\/\r\n3) Add the following lines to your ~\/.vimrc to have ViM use the file\r\n\r\n----- SNIP -----\r\n\" Octave filetype detection\r\naugroup filetypedetect\r\n au! BufRead,BufNewFile *.m set filetype=octave\r\naugroup END\r\n----- SNIP -----","first_name":"Rik","6":"Rik","last_name":"***","7":"***","releases":[{"0":"6056","vim_version":"6.0","1":"6.0","script_version":"1.2","2":"1.2","version_comment":"Initial upload","3":"Initial upload","package":"octave.vim","4":"octave.vim","src_id":"28397","5":"28397","creation_date":"1679989630","6":"1679989630"}]},"6055":{"script_id":"6055","0":"6055","script_name":"vim-softwrap","1":"vim-softwrap","script_type":"utility","2":"utility","summary":"Soft-wrap current line when they spill beyond the available textwidth","3":"Soft-wrap current line when they spill beyond the available textwidth","description":"If you can't bother moving with $ to the end of lines that spill out of view because you want to see the rest of the file too, this plugin might help you. It's a way to wrap only the current line without actually modifying it. It uses a plugin to accomplish the task.","4":"If you can't bother moving with $ to the end of lines that spill out of view because you want to see the rest of the file too, this plugin might help you. It's a way to wrap only the current line without actually modifying it. It uses a plugin to accomplish the task.","install_details":"Can install with any plugin manager. I use junegunn's vim-plug.","5":"Can install with any plugin manager. I use junegunn's vim-plug.","first_name":"Enrico Maria","6":"Enrico Maria","last_name":"De Angelis","7":"De Angelis","releases":[{"0":"6055","vim_version":"8.2","1":"8.2","script_version":"1","2":"1","version_comment":"Initial upload","3":"Initial upload","package":"softwrap.vim","4":"softwrap.vim","src_id":"28395","5":"28395","creation_date":"1679880793","6":"1679880793"}]},"6054":{"script_id":"6054","0":"6054","script_name":"WinZoZ","1":"WinZoZ","script_type":"utility","2":"utility","summary":"Plugin for easy window-oriented movemets","3":"Plugin for easy window-oriented movemets","description":"If you are a Vim user that makes use of windows-oriented workflows (as opposed to just buffer-oriented workflows) you must have thought that it\\\\\\'s a bit annoying to move across several windows as you have to press Ctrl+W before any movement. And maybe that\\\\\\'s precisely the reason why you don\\\\\\'t use windows at all.\r\n\r\nMy plugin is a solution, as it gives you a way to define a mapping, defaulted to w, to activate a pseudo-mode where all keystrokes are prepended a Ctrl+W, so that moving across the main diagonal of a 4x4 grid of windows is as easy as tjljljl\r\n\r\n(I\\\\\\'ve not bothered taking the time to see what\\\\\\'s the minimal Vim to make this work, but I used it since Vim 8.something.)","4":"If you are a Vim user that makes use of windows-oriented workflows (as opposed to just buffer-oriented workflows) you must have thought that it\\\\\\'s a bit annoying to move across several windows as you have to press Ctrl+W before any movement. And maybe that\\\\\\'s precisely the reason why you don\\\\\\'t use windows at all.\r\n\r\nMy plugin is a solution, as it gives you a way to define a mapping, defaulted to w, to activate a pseudo-mode where all keystrokes are prepended a Ctrl+W, so that moving across the main diagonal of a 4x4 grid of windows is as easy as tjljljl\r\n\r\n(I\\\\\\'ve not bothered taking the time to see what\\\\\\'s the minimal Vim to make this work, but I used it since Vim 8.something.)","install_details":"Can install with any plugin manager. I use junegunn\\\\\\'s vim-plug.","5":"Can install with any plugin manager. I use junegunn\\\\\\'s vim-plug.","first_name":"Enrico Maria","6":"Enrico Maria","last_name":"De Angelis","7":"De Angelis","releases":[{"0":"6054","vim_version":"8.2","1":"8.2","script_version":"1","2":"1","version_comment":"Initial upload","3":"Initial upload","package":"WinZoZ-main.zip","4":"WinZoZ-main.zip","src_id":"28394","5":"28394","creation_date":"1679880237","6":"1679880237"}]},"6053":{"script_id":"6053","0":"6053","script_name":"HexX","1":"HexX","script_type":"utility","2":"utility","summary":"Hex editor","3":"Hex editor","description":"As any seasoned Vim user knows, Vim does not support editing of binary files in any meaningful way; it's not Vim's fault - it was never designed for that\r\n\r\nHexX hopes to plug that gap. It provides a working and useful hex editing environment. Because of the way it works, it does not support the huge range of normal Vim editing features, but it does provide the basics plus some surprise-and-delight features as well\r\n\r\nBe sure to fully read the README file before using this - there is a lot of useful information in it that should answer any questions you may have. There is also the usual 'help' file too but this deliberately only provides (mostly) command and mapping information\r\n\r\nNOTE: I really have no idea what the minimum vim version requirement is to run HexX and I don't know of a practical way of finding out. The best I can suggest is to try it; it will probably work and if it doesn't then let me know and I'll see if I can sort it\r\n\r\n*** I would really value any feedback on this plugin. If you have any suggestions for improving this, then please let me know. If you think it's rubbish then PLEASE let me know why - it's far more useful than just 'voting it down' (which really doesn't help at all). Contact details are in the top of the README file *** ","4":"As any seasoned Vim user knows, Vim does not support editing of binary files in any meaningful way; it's not Vim's fault - it was never designed for that\r\n\r\nHexX hopes to plug that gap. It provides a working and useful hex editing environment. Because of the way it works, it does not support the huge range of normal Vim editing features, but it does provide the basics plus some surprise-and-delight features as well\r\n\r\nBe sure to fully read the README file before using this - there is a lot of useful information in it that should answer any questions you may have. There is also the usual 'help' file too but this deliberately only provides (mostly) command and mapping information\r\n\r\nNOTE: I really have no idea what the minimum vim version requirement is to run HexX and I don't know of a practical way of finding out. The best I can suggest is to try it; it will probably work and if it doesn't then let me know and I'll see if I can sort it\r\n\r\n*** I would really value any feedback on this plugin. If you have any suggestions for improving this, then please let me know. If you think it's rubbish then PLEASE let me know why - it's far more useful than just 'voting it down' (which really doesn't help at all). Contact details are in the top of the README file *** ","install_details":"Just un-tar into ~\/.vim\/bundle\/ as usual and read the README file for config options","5":"Just un-tar into ~\/.vim\/bundle\/ as usual and read the README file for config options","first_name":"Richard","6":"Richard","last_name":"Bentley-Green","7":"Bentley-Green","releases":[{"0":"6053","vim_version":"7.0","1":"7.0","script_version":"10\/01\/2024","2":"10\/01\/2024","version_comment":"Very minor bug fix related to exiting\/suspending HexX","3":"Very minor bug fix related to exiting\/suspending HexX","package":"hexx.tar.gz","4":"hexx.tar.gz","src_id":"28590","5":"28590","creation_date":"1704881440","6":"1704881440"},{"0":"6053","vim_version":"7.0","1":"7.0","script_version":"18\/03\/23","2":"18\/03\/23","version_comment":"Initial upload","3":"Initial upload","package":"hexx.tar.gz","4":"hexx.tar.gz","src_id":"28389","5":"28389","creation_date":"1679178165","6":"1679178165"}]},"6052":{"script_id":"6052","0":"6052","script_name":"Neural","1":"Neural","script_type":"utility","2":"utility","summary":"ChatGPT Vim plugin, OpenAI Vim plugin, and more!","3":"ChatGPT Vim plugin, OpenAI Vim plugin, and more!","description":"A ChatGPT Vim plugin, an OpenAI Neovim plugin, and so much more! Neural integrates various machine learning tools so you can let AI write code for you in Vim\/Neovim, among other helpful things.\r\n\r\nSee GitHub for latest version: https:\/\/github.com\/dense-analysis\/neural\r\n\r\nExperience lightning-fast code generation and completion with asynchronous streaming.","4":"A ChatGPT Vim plugin, an OpenAI Neovim plugin, and so much more! Neural integrates various machine learning tools so you can let AI write code for you in Vim\/Neovim, among other helpful things.\r\n\r\nSee GitHub for latest version: https:\/\/github.com\/dense-analysis\/neural\r\n\r\nExperience lightning-fast code generation and completion with asynchronous streaming.","install_details":"Extra to ~\/.vim\/pack\/git-plugins\/start\/neural or your start directory of choice, and that's it. You need a decent version of Python installed on your system.","5":"Extra to ~\/.vim\/pack\/git-plugins\/start\/neural or your start directory of choice, and that's it. You need a decent version of Python installed on your system.","first_name":"w0rp","6":"w0rp","last_name":" ","7":" ","releases":[{"0":"6052","vim_version":"8.0","1":"8.0","script_version":"v0.0.0","2":"v0.0.0","version_comment":"Initial upload","3":"Initial upload","package":"neural-v0.0.0.zip","4":"neural-v0.0.0.zip","src_id":"28388","5":"28388","creation_date":"1679171677","6":"1679171677"}]},"6051":{"script_id":"6051","0":"6051","script_name":"vim-rebrackets","1":"vim-rebrackets","script_type":"utility","2":"utility","summary":"Recursive parentheses","3":"Recursive parentheses","description":"This plugin makes it easier and more emphatic to type the Japanese slang parentheses syntax.\r\n\r\nThe user executes the command with the word and the number of recursions as arguments, and it yanks the text with the word enclosed in parentheses for the specified number of times.","4":"This plugin makes it easier and more emphatic to type the Japanese slang parentheses syntax.\r\n\r\nThe user executes the command with the word and the number of recursions as arguments, and it yanks the text with the word enclosed in parentheses for the specified number of times.","install_details":"Pathogen:\r\n git clone https:\/\/github.com\/momozo2251\/vim-rebrackets.git \\\r\n ~\/.vim\/bundle\/vim-rebrackets\r\n\r\nvim-plug:\r\n 1. Add Plug 'momozo2251\/vim-rebrackets' to .vimrc\r\n 2. Run :PlugInstall","5":"Pathogen:\r\n git clone https:\/\/github.com\/momozo2251\/vim-rebrackets.git \\\r\n ~\/.vim\/bundle\/vim-rebrackets\r\n\r\nvim-plug:\r\n 1. Add Plug 'momozo2251\/vim-rebrackets' to .vimrc\r\n 2. Run :PlugInstall","first_name":"momozo","6":"momozo","last_name":"2251","7":"2251","releases":[{"0":"6051","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"vim-rebrackets-main.zip","4":"vim-rebrackets-main.zip","src_id":"28387","5":"28387","creation_date":"1679170023","6":"1679170023"}]},"6050":{"script_id":"6050","0":"6050","script_name":"Vim is done","1":"Vim is done","script_type":"utility","2":"utility","summary":"A Todo UI for vim","3":"A Todo UI for vim","description":"Vim is done is a TODO List plugin for Vim\r\n\r\nThe plugin is essentially displaying a menu on your window to keep track of what you need to do, achieve.\r\n\r\nIt also saves what you did in the past as reminder.\r\n\r\nThere are maily 2 commands to 'Vim is done':\r\n\r\n - AddTODO()\r\n - Complete()\r\n\r\nMore commands will be added in the future.\r\n\r\nFor easier use, i recommand mapping these functions that you need to call:\r\n\r\n - nnoremap : call AddTODO()\r\n - nnoremap : call Complete()\r\n\r\nWhen using AddTODO(), it will display a prompt where you can type whatever you want.\r\nThe Complete() function takes one argument which is the number of the TODO you finished.\r\n\r\n - call Complete(1) \" If i want to complete the TODO n1\r\n\r\nThere is also a variable g:cookies which counts how many TODOs you finished.\r\nIf using the plugin airline, it will display it on the status line as 'cookies: {g:cookies}'\r\n\r\nIf any question or want to contribute to the plugin, my email is leo.fresnay@apyretechs.com, my github is @Apyre83 and my discord is LeoBis#2064","4":"Vim is done is a TODO List plugin for Vim\r\n\r\nThe plugin is essentially displaying a menu on your window to keep track of what you need to do, achieve.\r\n\r\nIt also saves what you did in the past as reminder.\r\n\r\nThere are maily 2 commands to 'Vim is done':\r\n\r\n - AddTODO()\r\n - Complete()\r\n\r\nMore commands will be added in the future.\r\n\r\nFor easier use, i recommand mapping these functions that you need to call:\r\n\r\n - nnoremap : call AddTODO()\r\n - nnoremap : call Complete()\r\n\r\nWhen using AddTODO(), it will display a prompt where you can type whatever you want.\r\nThe Complete() function takes one argument which is the number of the TODO you finished.\r\n\r\n - call Complete(1) \" If i want to complete the TODO n1\r\n\r\nThere is also a variable g:cookies which counts how many TODOs you finished.\r\nIf using the plugin airline, it will display it on the status line as 'cookies: {g:cookies}'\r\n\r\nIf any question or want to contribute to the plugin, my email is leo.fresnay@apyretechs.com, my github is @Apyre83 and my discord is LeoBis#2064","install_details":"If you don't already have, create the following folder:\r\n\r\n mkdir $HOME\/.vim\/plugged\r\n\r\nGo to the folder using\r\n\r\n cd $HOME\/.vim\/plugged\r\n\r\nIf you are using the tar file:\r\n untar the file in your $HOME\/.vim\/plugged using\r\n tar xvzf TODO.tar.gz (on ubuntu)\r\n\r\nIf you are using my github, just clone the following repo:\r\n git clone https:\/\/github.com\/Apyre83\/TODO.vim\r\n\r\nThen, if you don't already have a $HOME\/.vimrc file, create one using:\r\n touch $HOME\/.vimrc\r\n\r\nAnd start editing it using vim:\r\n vim $HOME\/.vimrc\r\n\r\nThen add the following line to it:\r\n source $HOME\/.vim\/plugged\/TODO.vim\/plugin\/TODO.vim\r\n\r\nAnd you will be able to use it !","5":"If you don't already have, create the following folder:\r\n\r\n mkdir $HOME\/.vim\/plugged\r\n\r\nGo to the folder using\r\n\r\n cd $HOME\/.vim\/plugged\r\n\r\nIf you are using the tar file:\r\n untar the file in your $HOME\/.vim\/plugged using\r\n tar xvzf TODO.tar.gz (on ubuntu)\r\n\r\nIf you are using my github, just clone the following repo:\r\n git clone https:\/\/github.com\/Apyre83\/TODO.vim\r\n\r\nThen, if you don't already have a $HOME\/.vimrc file, create one using:\r\n touch $HOME\/.vimrc\r\n\r\nAnd start editing it using vim:\r\n vim $HOME\/.vimrc\r\n\r\nThen add the following line to it:\r\n source $HOME\/.vim\/plugged\/TODO.vim\/plugin\/TODO.vim\r\n\r\nAnd you will be able to use it !","first_name":"Leo","6":"Leo","last_name":"Fresnay","7":"Fresnay","releases":[{"0":"6050","vim_version":"5.7","1":"5.7","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"TODO.tar.gz","4":"TODO.tar.gz","src_id":"28382","5":"28382","creation_date":"1678557748","6":"1678557748"}]},"6049":{"script_id":"6049","0":"6049","script_name":"make-my-code-better.vim","1":"make-my-code-better.vim","script_type":"utility","2":"utility","summary":"Use ChatGPT to suggest ways to make your code better","3":"Use ChatGPT to suggest ways to make your code better","description":"Make My Code Better is a vim plugin to ask ChatGPT recommendations about\r\nhow to make your code better.\r\n\r\nIt will send your selected code (or the whole file is no code is selected)\r\nto the ChatGPT api, and provide its answer in a split window.\r\n\r\n\r\nINSTALLATION AND SETUP\r\n\r\nMake My Code Better requires vim to be built with python3 support (check\r\nthe output of `vim --version` if you have +python3) and depends on tiktoken,\r\nopenai's token counting module which you can install this way:\r\n\r\n pip install tiktoken\r\n\r\nAdditionally, you must provide your openai api ( https:\/\/platform.openai.com\/ )\r\nkey, which you can set up in your vimrc file:\r\n\r\n let g:open_ai_key=\"\"\r\n\r\nIf you prefer to use a vim plugin manager to install it, you can use the repos\r\n\"oelmekki\/make-my-code-better.vim\" on github ( https:\/\/github.com\/oelmekki\/make-my-code-better.vim ).\r\n\r\nUSAGE\r\n\r\nAfter that, you can use `:MakeMyCodeBetter` to run the plugin. This command\r\naccepts a range, so you can just send one or two functions. Given the\r\nlimitation in number of tokens, this will probably be your most common\r\nusage. You will be warned if you exceed the amount of tokens allowed, and\r\nno request will be performed.\r\n\r\n\r\nINSTRUCTIONS\r\n\r\nThe default instructions for ChatGPT are:\r\n\r\n I'm going to show you my code, and you're going to make it better, providing\r\n your version and explaining your changes, or congratulating me if it's already\r\n perfect. You don't consider coding style preferences, you only suggest changes\r\n that could make the code more performant, less buggy or easier to maintain.\r\n\r\n\r\nYou can change that and use your own instructions instead by setting this\r\nvariable:\r\n\r\n let g:make_my_code_better_instructions='\r\n \\ I''m going to show you my code. You''re going to say you found a way to\r\n \\ make it more performant, and you will rewrite my code in C.'\r\n\r\n\r\nLIMITATIONS\r\n\r\nThe plugin waits for the whole response to be provided by the api before\r\ndisplaying it, so you might be hanging for a while waiting for it. I could\r\nhave used the new vim-9.0 api to stream it, but I've never used that and\r\nI'm not even sure if it would work through python support. It was just not\r\npainful enough for me to investigate, just don't be surprised if you send\r\na lot of code and it takes 30 seconds to complete.\r\n\r\nChatGPT is limited to 4096 tokens per request (a token being usually a part\r\nof a word, but the token count on code can shoot up high fast). This\r\nincludes the instructions, your code, and the answer of ChatGPT. Since we\r\nask it to rewrite the code, it can be up to the same length than the code\r\nyou provided (hopefully, it will be more concise than your code) and will\r\ninclude some explanations. For that reason, I limited the code you provide\r\nto 2000 tokens. You can tweak that number by setting the\r\n`g:make_my_code_better_max_tokens` variable.\r\n\r\nAnd of course, this is ChatGPT : just because it tells you something\r\ndoesn't mean it's true! Check the code it recommends and apply good\r\njudgment. Despite that, it's worth it. I've been a webdeveloper for 15\r\nyears and it taught me new things. Has this very plugin been written with\r\nthe help of ChatGPT? Of course it has! And was done in less than a day for\r\nit. Roxor.\r\n","4":"Make My Code Better is a vim plugin to ask ChatGPT recommendations about\r\nhow to make your code better.\r\n\r\nIt will send your selected code (or the whole file is no code is selected)\r\nto the ChatGPT api, and provide its answer in a split window.\r\n\r\n\r\nINSTALLATION AND SETUP\r\n\r\nMake My Code Better requires vim to be built with python3 support (check\r\nthe output of `vim --version` if you have +python3) and depends on tiktoken,\r\nopenai's token counting module which you can install this way:\r\n\r\n pip install tiktoken\r\n\r\nAdditionally, you must provide your openai api ( https:\/\/platform.openai.com\/ )\r\nkey, which you can set up in your vimrc file:\r\n\r\n let g:open_ai_key=\"\"\r\n\r\nIf you prefer to use a vim plugin manager to install it, you can use the repos\r\n\"oelmekki\/make-my-code-better.vim\" on github ( https:\/\/github.com\/oelmekki\/make-my-code-better.vim ).\r\n\r\nUSAGE\r\n\r\nAfter that, you can use `:MakeMyCodeBetter` to run the plugin. This command\r\naccepts a range, so you can just send one or two functions. Given the\r\nlimitation in number of tokens, this will probably be your most common\r\nusage. You will be warned if you exceed the amount of tokens allowed, and\r\nno request will be performed.\r\n\r\n\r\nINSTRUCTIONS\r\n\r\nThe default instructions for ChatGPT are:\r\n\r\n I'm going to show you my code, and you're going to make it better, providing\r\n your version and explaining your changes, or congratulating me if it's already\r\n perfect. You don't consider coding style preferences, you only suggest changes\r\n that could make the code more performant, less buggy or easier to maintain.\r\n\r\n\r\nYou can change that and use your own instructions instead by setting this\r\nvariable:\r\n\r\n let g:make_my_code_better_instructions='\r\n \\ I''m going to show you my code. You''re going to say you found a way to\r\n \\ make it more performant, and you will rewrite my code in C.'\r\n\r\n\r\nLIMITATIONS\r\n\r\nThe plugin waits for the whole response to be provided by the api before\r\ndisplaying it, so you might be hanging for a while waiting for it. I could\r\nhave used the new vim-9.0 api to stream it, but I've never used that and\r\nI'm not even sure if it would work through python support. It was just not\r\npainful enough for me to investigate, just don't be surprised if you send\r\na lot of code and it takes 30 seconds to complete.\r\n\r\nChatGPT is limited to 4096 tokens per request (a token being usually a part\r\nof a word, but the token count on code can shoot up high fast). This\r\nincludes the instructions, your code, and the answer of ChatGPT. Since we\r\nask it to rewrite the code, it can be up to the same length than the code\r\nyou provided (hopefully, it will be more concise than your code) and will\r\ninclude some explanations. For that reason, I limited the code you provide\r\nto 2000 tokens. You can tweak that number by setting the\r\n`g:make_my_code_better_max_tokens` variable.\r\n\r\nAnd of course, this is ChatGPT : just because it tells you something\r\ndoesn't mean it's true! Check the code it recommends and apply good\r\njudgment. Despite that, it's worth it. I've been a webdeveloper for 15\r\nyears and it taught me new things. Has this very plugin been written with\r\nthe help of ChatGPT? Of course it has! And was done in less than a day for\r\nit. Roxor.\r\n","install_details":"","5":"","first_name":"Olivier","6":"Olivier","last_name":"El Mekki","7":"El Mekki","releases":[{"0":"6049","vim_version":"7.0","1":"7.0","script_version":"1.0.0","2":"1.0.0","version_comment":"Initial upload","3":"Initial upload","package":"make-my-code-better.vim","4":"make-my-code-better.vim","src_id":"28380","5":"28380","creation_date":"1678214451","6":"1678214451"}]},"6048":{"script_id":"6048","0":"6048","script_name":"vim-ai","1":"vim-ai","script_type":"utility","2":"utility","summary":"AI-powered code assistant for Vim. OpenAI and ChatGPT plugin for Vim and Neovim","3":"AI-powered code assistant for Vim. OpenAI and ChatGPT plugin for Vim and Neovim","description":"This plugin adds Artificial Intelligence (AI) capabilities to your Vim and Neovim.\r\nYou can generate code, edit text, or have an interactive conversation with GPT models, all powered by OpenAI's API.\r\n\r\nRepository:\r\nhttps:\/\/github.com\/madox2\/vim-ai\r\n\r\nFeatures:\r\n- Generate text or code, answer questions with AI\r\n- Edit selected text in-place with AI\r\n- Interactive conversation with ChatGPT\r\n\r\nCommands:\r\n- :AI - complete text\r\n- :AIEdit - edit selected text\r\n- :AIChat - start\/continue conversation with OpenAI chat models\r\n\r\nDisclaimer:\r\n- Accuracy: GPT is good at producing text and code that looks correct at first glance, but may be completely wrong. Be sure to thoroughly review, read and test all output generated by this plugin!\r\n- Privacy: This plugin sends text to OpenAI when generating completions and edits. Therefore, do not use it on files containing sensitive information.\r\n\r\nMore details:\r\nhttps:\/\/github.com\/madox2\/vim-ai","4":"This plugin adds Artificial Intelligence (AI) capabilities to your Vim and Neovim.\r\nYou can generate code, edit text, or have an interactive conversation with GPT models, all powered by OpenAI's API.\r\n\r\nRepository:\r\nhttps:\/\/github.com\/madox2\/vim-ai\r\n\r\nFeatures:\r\n- Generate text or code, answer questions with AI\r\n- Edit selected text in-place with AI\r\n- Interactive conversation with ChatGPT\r\n\r\nCommands:\r\n- :AI - complete text\r\n- :AIEdit - edit selected text\r\n- :AIChat - start\/continue conversation with OpenAI chat models\r\n\r\nDisclaimer:\r\n- Accuracy: GPT is good at producing text and code that looks correct at first glance, but may be completely wrong. Be sure to thoroughly review, read and test all output generated by this plugin!\r\n- Privacy: This plugin sends text to OpenAI when generating completions and edits. Therefore, do not use it on files containing sensitive information.\r\n\r\nMore details:\r\nhttps:\/\/github.com\/madox2\/vim-ai","install_details":"Works in Vim 8+, requires python 3 and openai-python","5":"Works in Vim 8+, requires python 3 and openai-python","first_name":"Martin","6":"Martin","last_name":"Bielik","7":"Bielik","releases":[{"0":"6048","vim_version":"8.0","1":"8.0","script_version":"1.6.0","2":"1.6.0","version_comment":"removed obsolete models","3":"removed obsolete models","package":"vim-ai.tar.gz","4":"vim-ai.tar.gz","src_id":"28551","5":"28551","creation_date":"1696415819","6":"1696415819"},{"0":"6048","vim_version":"8.0","1":"8.0","script_version":"1.5.0","2":"1.5.0","version_comment":"- Added custom commands\r\n- new :AINewChat command\r\n- Improving completion responses\r\n- Open chat presets\r\n- Chat per viewport support","3":"- Added custom commands\r\n- new :AINewChat command\r\n- Improving completion responses\r\n- Open chat presets\r\n- Chat per viewport support","package":"vim-ai.tar.gz","4":"vim-ai.tar.gz","src_id":"28431","5":"28431","creation_date":"1682383691","6":"1682383691"},{"0":"6048","vim_version":"8.0","1":"8.0","script_version":"1.4.0","2":"1.4.0","version_comment":"removed openai dependency, added chat-options","3":"removed openai dependency, added chat-options","package":"vim-ai.tar.gz","4":"vim-ai.tar.gz","src_id":"28411","5":"28411","creation_date":"1681492568","6":"1681492568"},{"0":"6048","vim_version":"8.0","1":"8.0","script_version":"1.3.0","2":"1.3.0","version_comment":"Added syntax highlighting in chat","3":"Added syntax highlighting in chat","package":"vim-ai.tar.gz","4":"vim-ai.tar.gz","src_id":"28408","5":"28408","creation_date":"1680985233","6":"1680985233"},{"0":"6048","vim_version":"8.0","1":"8.0","script_version":"1.3.0","2":"1.3.0","version_comment":"Chat interface configuration, complete\/edit engines to allow chat models","3":"Chat interface configuration, complete\/edit engines to allow chat models","package":"vim-ai.tar.gz","4":"vim-ai.tar.gz","src_id":"28404","5":"28404","creation_date":"1680758735","6":"1680758735"},{"0":"6048","vim_version":"7.0","1":"7.0","script_version":"1.2.0","2":"1.2.0","version_comment":"openai configuration and other small improvements","3":"openai configuration and other small improvements","package":"vim-ai.tar.gz","4":"vim-ai.tar.gz","src_id":"28392","5":"28392","creation_date":"1679614153","6":"1679614153"},{"0":"6048","vim_version":"8.0","1":"8.0","script_version":"1.1.0","2":"1.1.0","version_comment":"live streaming AI responses","3":"live streaming AI responses","package":"vim-ai.tar.gz","4":"vim-ai.tar.gz","src_id":"28385","5":"28385","creation_date":"1678940384","6":"1678940384"},{"0":"6048","vim_version":"8.0","1":"8.0","script_version":"1.0.0","2":"1.0.0","version_comment":"Initial upload","3":"Initial upload","package":"vim-ai.tar.gz","4":"vim-ai.tar.gz","src_id":"28378","5":"28378","creation_date":"1678171381","6":"1678171381"}]},"6047":{"script_id":"6047","0":"6047","script_name":"vim-dirdifftree","1":"vim-dirdifftree","script_type":"utility","2":"utility","summary":"Diff two directories and represent them as a tree","3":"Diff two directories and represent them as a tree","description":"Diff two directories and represent them as a tree\r\n\r\nGitHub\r\nhttps:\/\/github.com\/taze55\/vim-dirdifftree","4":"Diff two directories and represent them as a tree\r\n\r\nGitHub\r\nhttps:\/\/github.com\/taze55\/vim-dirdifftree","install_details":"Requires python 3.8.10 or later to work","5":"Requires python 3.8.10 or later to work","first_name":"ta","6":"ta","last_name":"ze","7":"ze","releases":[{"0":"6047","vim_version":"9.0","1":"9.0","script_version":"1.0.2","2":"1.0.2","version_comment":"Fixed behavior with Neovim.\r\nAdd exclude directories option.\r\nAdd ignorecase option.","3":"Fixed behavior with Neovim.\r\nAdd exclude directories option.\r\nAdd ignorecase option.","package":"vim-dirdifftree.zip","4":"vim-dirdifftree.zip","src_id":"28381","5":"28381","creation_date":"1678557398","6":"1678557398"},{"0":"6047","vim_version":"9.0","1":"9.0","script_version":"1.0.0","2":"1.0.0","version_comment":"Initial upload","3":"Initial upload","package":"vim-dirdifftree.zip","4":"vim-dirdifftree.zip","src_id":"28377","5":"28377","creation_date":"1678033393","6":"1678033393"}]},"6046":{"script_id":"6046","0":"6046","script_name":"wrapfiller","1":"wrapfiller","script_type":"utility","2":"utility","summary":"Align each wrapped line virtually between windows","3":"Align each wrapped line virtually between windows","description":"This plugin fills with virtual lines to visually align the position of each line between two or more windows, even when the 'wrap' option is on, and makes it easier to find the lines you want to compare.\r\n\r\nFor details and demo samples, please visit the following git repository: https:\/\/github.com\/rickhowe\/wrapfiller","4":"This plugin fills with virtual lines to visually align the position of each line between two or more windows, even when the 'wrap' option is on, and makes it easier to find the lines you want to compare.\r\n\r\nFor details and demo samples, please visit the following git repository: https:\/\/github.com\/rickhowe\/wrapfiller","install_details":"Install 'rickhowe\/wrapfiller' by using your plugin manager. Or manually unzip and copy all folders in your ~\/.vim or ~\/vimfiles.","5":"Install 'rickhowe\/wrapfiller' by using your plugin manager. Or manually unzip and copy all folders in your ~\/.vim or ~\/vimfiles.","first_name":"Rick","6":"Rick","last_name":"Howe","7":"Howe","releases":[{"0":"6046","vim_version":"9.0","1":"9.0","script_version":"2.2","2":"2.2","version_comment":"Improved to check a change of several options, text, and window width to automatically adjust virtual lines.","3":"Improved to check a change of several options, text, and window width to automatically adjust virtual lines.","package":"wrapfiller2.2.zip","4":"wrapfiller2.2.zip","src_id":"28639","5":"28639","creation_date":"1709639162","6":"1709639162"},{"0":"6046","vim_version":"9.0","1":"9.0","script_version":"2.1","2":"2.1","version_comment":"Changed to show the virtual lines as diff filler lines in diff mode.","3":"Changed to show the virtual lines as diff filler lines in diff mode.","package":"wrapfiller2.1.zip","4":"wrapfiller2.1.zip","src_id":"28535","5":"28535","creation_date":"1692877278","6":"1692877278"},{"0":"6046","vim_version":"9.0","1":"9.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"wrapfiller1.0.zip","4":"wrapfiller1.0.zip","src_id":"28369","5":"28369","creation_date":"1676826546","6":"1676826546"}]},"6045":{"script_id":"6045","0":"6045","script_name":"iBasic.vim","1":"iBasic.vim","script_type":"syntax","2":"syntax","summary":"VIM Syntax file for iBasic","3":"VIM Syntax file for iBasic","description":"I uploaded this to the development list because I could not figure out how to add a script to the list of scripts I keep. Well, my IQ might be three - but I finally figured out how to upload it and here it is! Enjoy! So Mathias - you can use this one if you want.","4":"I uploaded this to the development list because I could not figure out how to add a script to the list of scripts I keep. Well, my IQ might be three - but I finally figured out how to upload it and here it is! Enjoy! So Mathias - you can use this one if you want.","install_details":"","5":"","first_name":"Mark","6":"Mark","last_name":"Manning","7":"Manning","releases":[{"0":"6045","vim_version":"7.0","1":"7.0","script_version":"1.2","2":"1.2","version_comment":"Initial upload","3":"Initial upload","package":"ibasic.vim","4":"ibasic.vim","src_id":"28362","5":"28362","creation_date":"1675609810","6":"1675609810"}]},"6044":{"script_id":"6044","0":"6044","script_name":"iwbasic.vim","1":"iwbasic.vim","script_type":"syntax","2":"syntax","summary":"A syntax file for IWBasic","3":"A syntax file for IWBasic","description":"This syntax file is for the newer IWBasic (*.iba). The older IBasic.vim syntax file still works but since IBasic has been disontinued; this new syntax file should be used on the newer IWBasic files or \"*.iba\" files. IWBasic is sold by Ionic Wind and was created by Larry Sikes at Rock Ridge Farm.","4":"This syntax file is for the newer IWBasic (*.iba). The older IBasic.vim syntax file still works but since IBasic has been disontinued; this new syntax file should be used on the newer IWBasic files or \"*.iba\" files. IWBasic is sold by Ionic Wind and was created by Larry Sikes at Rock Ridge Farm.","install_details":"Drag to your syntax folder in the gvim directory.","5":"Drag to your syntax folder in the gvim directory.","first_name":"Mark","6":"Mark","last_name":"Manning","7":"Manning","releases":[{"0":"6044","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"iwbasic.vim","4":"iwbasic.vim","src_id":"28359","5":"28359","creation_date":"1674626941","6":"1674626941"}]},"6043":{"script_id":"6043","0":"6043","script_name":"camelcomplete","1":"camelcomplete","script_type":"utility","2":"utility","summary":"Vim 9 plugin to complete CamelCase and snake_case identifier abbreviations.","3":"Vim 9 plugin to complete CamelCase and snake_case identifier abbreviations.","description":"This plugin provides a lightweight insert-mode completion function that allows you to expand CamelCase and snake_case abbreviations into their full identifiers. It is purely textual, and doesn't require setting up language servers or defining a project structure; rather, it operates like \/, but on identifier abbreviations rather than prefixes.\r\n\r\nAs an example (with * representing the cursor position),\r\n\r\n obj.sFM* --> (invoke camelcomplete) --> obj.setForwardMark*","4":"This plugin provides a lightweight insert-mode completion function that allows you to expand CamelCase and snake_case abbreviations into their full identifiers. It is purely textual, and doesn't require setting up language servers or defining a project structure; rather, it operates like \/, but on identifier abbreviations rather than prefixes.\r\n\r\nAs an example (with * representing the cursor position),\r\n\r\n obj.sFM* --> (invoke camelcomplete) --> obj.setForwardMark*","install_details":"Grab the latest version from\r\n\r\n https:\/\/github.com\/jessepav\/vim-camelcomplete\/\r\n\r\nOr use your favorite plugin manager.\r\n\r\nFor instace, with vim-plug:\r\n\r\nPlug 'jessepav\/vim-camelcomplete'","5":"Grab the latest version from\r\n\r\n https:\/\/github.com\/jessepav\/vim-camelcomplete\/\r\n\r\nOr use your favorite plugin manager.\r\n\r\nFor instace, with vim-plug:\r\n\r\nPlug 'jessepav\/vim-camelcomplete'","first_name":"Jesse","6":"Jesse","last_name":"Pavel","7":"Pavel","releases":[{"0":"6043","vim_version":"9.0","1":"9.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"vim-camelcomplete-master.zip","4":"vim-camelcomplete-master.zip","src_id":"28347","5":"28347","creation_date":"1673526611","6":"1673526611"}]},"6042":{"script_id":"6042","0":"6042","script_name":"vim-hex-rework","1":"vim-hex-rework","script_type":"utility","2":"utility","summary":"vim hex edit plugin","3":"vim hex edit plugin","description":"Vim embeds with xxd to display hex strings, the hex string can be changed only when the number of hex strings is the same, thus you can't insert new hex character, or delete some existing hex character.\r\n\r\nvim-hex-rework add one command: Hexrework. You can insert new hex characters, delete hex characters in the hex string, then run 'Hexrework' command, the 'Hexrework' command will change current buffer's content, make it match with xxd format. When the file is written, the binary file is updated accordingly.\r\n\r\nThe whole document can be found at https:\/\/github.com\/rargo\/vim-hex-rework","4":"Vim embeds with xxd to display hex strings, the hex string can be changed only when the number of hex strings is the same, thus you can't insert new hex character, or delete some existing hex character.\r\n\r\nvim-hex-rework add one command: Hexrework. You can insert new hex characters, delete hex characters in the hex string, then run 'Hexrework' command, the 'Hexrework' command will change current buffer's content, make it match with xxd format. When the file is written, the binary file is updated accordingly.\r\n\r\nThe whole document can be found at https:\/\/github.com\/rargo\/vim-hex-rework","install_details":"copy the script file into your ~\/.vim\/plugin directory or use vim install plugin tools like Vundle.\r\n\r\n","5":"copy the script file into your ~\/.vim\/plugin directory or use vim install plugin tools like Vundle.\r\n\r\n","first_name":"Zhanqian","6":"Zhanqian","last_name":"Ye","7":"Ye","releases":[{"0":"6042","vim_version":"7.0","1":"7.0","script_version":"1.1","2":"1.1","version_comment":"fix error infomation","3":"fix error infomation","package":"vim-hex-rework.vim","4":"vim-hex-rework.vim","src_id":"28320","5":"28320","creation_date":"1671475216","6":"1671475216"},{"0":"6042","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"vim-hex-rework.vim","4":"vim-hex-rework.vim","src_id":"28319","5":"28319","creation_date":"1671474115","6":"1671474115"}]},"6041":{"script_id":"6041","0":"6041","script_name":"vim-unitex","1":"vim-unitex","script_type":"utility","2":"utility","summary":"Superior alternative for vim's conceal feature","3":"Superior alternative for vim's conceal feature","description":"Git repository: https:\/\/github.com\/juiyung\/vim-unitex. You can see a screencast there (https:\/\/github.com\/juiyung\/vim-unitex\/blob\/master\/demo.gif).\r\n\r\nThis plugin makes sophisticated use of the unitex program (https:\/\/github.com\/juiyung\/unitex) to create an effect resembling vim's syntax concealment for tex files. Through using a new mechanism, however, many drawbacks of the conceal feature are eliminated. If you like vim's conceal feature, this plugin is probably worth trying out, it's not only an alternative but also suitable for using in combination with the conceal feature.\r\n\r\nThis plugin takes a few more steps to set up than the general, but nothing about the steps is particularly complex. Once successfully deployed, I consider it easy and cool to use. If you feel interested, you can find its usage and more information in the README contained in the zip file, which you may also read in https:\/\/github.com\/juiyung\/vim-unitex#readme. Going through the README is well-recommended.","4":"Git repository: https:\/\/github.com\/juiyung\/vim-unitex. You can see a screencast there (https:\/\/github.com\/juiyung\/vim-unitex\/blob\/master\/demo.gif).\r\n\r\nThis plugin makes sophisticated use of the unitex program (https:\/\/github.com\/juiyung\/unitex) to create an effect resembling vim's syntax concealment for tex files. Through using a new mechanism, however, many drawbacks of the conceal feature are eliminated. If you like vim's conceal feature, this plugin is probably worth trying out, it's not only an alternative but also suitable for using in combination with the conceal feature.\r\n\r\nThis plugin takes a few more steps to set up than the general, but nothing about the steps is particularly complex. Once successfully deployed, I consider it easy and cool to use. If you feel interested, you can find its usage and more information in the README contained in the zip file, which you may also read in https:\/\/github.com\/juiyung\/vim-unitex#readme. Going through the README is well-recommended.","install_details":"Download the zip file and extract it under ~\/.vim\/pack\/foo\/start\/ (the name \"foo\" is arbitrary; \"~\/.vim\" is a default value for Unix-like systems, what suits your case depends on the 'runtimepath' option). You may also use vim-plug or vundle to install from \"juiyung\/vim-unitex\".\r\n\r\nunitex needs to be installed and configured. A quick guide for Unix-like systems: clone https:\/\/github.com\/juiyung\/unitex.git, enter the resulting directory, then \"sudo make install\" would install the program. You could then copy the rules.tsv file in the directory to ~\/.config\/unitex\/ as a quick configuration (\"~\/.config\" needs to be changed to $XDG_CONFIG_HOME if the environment variable is set differently). Refer to the README in unitex's repository if you have problems.\r\n\r\nVim's 'encoding', as well as the encoding of files you will work on using this plugin, should be utf-8. If you encounter problems, make sure to read the document carefully, open an issue in github if necessary.","5":"Download the zip file and extract it under ~\/.vim\/pack\/foo\/start\/ (the name \"foo\" is arbitrary; \"~\/.vim\" is a default value for Unix-like systems, what suits your case depends on the 'runtimepath' option). You may also use vim-plug or vundle to install from \"juiyung\/vim-unitex\".\r\n\r\nunitex needs to be installed and configured. A quick guide for Unix-like systems: clone https:\/\/github.com\/juiyung\/unitex.git, enter the resulting directory, then \"sudo make install\" would install the program. You could then copy the rules.tsv file in the directory to ~\/.config\/unitex\/ as a quick configuration (\"~\/.config\" needs to be changed to $XDG_CONFIG_HOME if the environment variable is set differently). Refer to the README in unitex's repository if you have problems.\r\n\r\nVim's 'encoding', as well as the encoding of files you will work on using this plugin, should be utf-8. If you encounter problems, make sure to read the document carefully, open an issue in github if necessary.","first_name":"Juiyung","6":"Juiyung","last_name":"Hsu","7":"Hsu","releases":[{"0":"6041","vim_version":"8.2","1":"8.2","script_version":"1","2":"1","version_comment":"minor fixes","3":"minor fixes","package":"vim-unitex.zip","4":"vim-unitex.zip","src_id":"28314","5":"28314","creation_date":"1671114210","6":"1671114210"}]},"6040":{"script_id":"6040","0":"6040","script_name":"irclog.vim","1":"irclog.vim","script_type":"syntax","2":"syntax","summary":"Syntax Highlighting for X-Chat and Irssi Log Files","3":"Syntax Highlighting for X-Chat and Irssi Log Files","description":"This syntax script provides highlighting for X-Chat and Irssi log files. Based on vimscript #1629.","4":"This syntax script provides highlighting for X-Chat and Irssi log files. Based on vimscript #1629.","install_details":"source irclog.vim","5":"source irclog.vim","first_name":"Andreas","6":"Andreas","last_name":"Gruenbacher","7":"Gruenbacher","releases":[{"0":"6040","vim_version":"5.7","1":"5.7","script_version":"1.1","2":"1.1","version_comment":"Update the maintainer email address as well.","3":"Update the maintainer email address as well.","package":"irclog.vim","4":"irclog.vim","src_id":"28303","5":"28303","creation_date":"1670701712","6":"1670701712"},{"0":"6040","vim_version":"5.7","1":"5.7","script_version":"1.1","2":"1.1","version_comment":"Initial upload","3":"Initial upload","package":"irclog.vim","4":"irclog.vim","src_id":"28302","5":"28302","creation_date":"1670699775","6":"1670699775"}]},"6039":{"script_id":"6039","0":"6039","script_name":"noodle.vim","1":"noodle.vim","script_type":"utility","2":"utility","summary":"A minutes-timer vim plugin","3":"A minutes-timer vim plugin","description":"https:\/\/github.com\/yukiomoto\/noodle.vim#noodlevim-provides-a-minutes-timer-feature","4":"https:\/\/github.com\/yukiomoto\/noodle.vim#noodlevim-provides-a-minutes-timer-feature","install_details":"","5":"","first_name":"Yuki","6":"Yuki","last_name":"Omoto","7":"Omoto","releases":[{"0":"6039","vim_version":"8.2","1":"8.2","script_version":"0.1.0","2":"0.1.0","version_comment":"Initial upload","3":"Initial upload","package":"noodle.zip","4":"noodle.zip","src_id":"28300","5":"28300","creation_date":"1670629065","6":"1670629065"}]},"6037":{"script_id":"6037","0":"6037","script_name":"Miesl.vim","1":"Miesl.vim","script_type":"color scheme","2":"color scheme","summary":"Monochrome colorscheme.","3":"Monochrome colorscheme.","description":"DEPRECATED in favor of Mies.vim with `set background=light` --> https:\/\/www.vim.org\/scripts\/script.php?script_id=6036\r\n\r\nThis script is not updated with the latest changes.\r\n\r\nMonochrome colorscheme, a variation on fogbell.vim. Light version.","4":"DEPRECATED in favor of Mies.vim with `set background=light` --> https:\/\/www.vim.org\/scripts\/script.php?script_id=6036\r\n\r\nThis script is not updated with the latest changes.\r\n\r\nMonochrome colorscheme, a variation on fogbell.vim. Light version.","install_details":"","5":"","first_name":"Jared","6":"Jared","last_name":"Gorski","7":"Gorski","releases":[{"0":"6037","vim_version":"7.0","1":"7.0","script_version":"0.0.0","2":"0.0.0","version_comment":"Initial","3":"Initial","package":"miesl.vim","4":"miesl.vim","src_id":"28291","5":"28291","creation_date":"1669924138","6":"1669924138"}]},"6036":{"script_id":"6036","0":"6036","script_name":"Mies.vim","1":"Mies.vim","script_type":"color scheme","2":"color scheme","summary":"Bauhaus monochrome colorscheme.","3":"Bauhaus monochrome colorscheme.","description":"Bauhaus monochrome colorscheme; a variation on fogbell.vim (https:\/\/github.com\/jaredgorski\/fogbell.vim).\r\n\r\nInspired by Mies Van Der Rohe's architecture in the Chicago area, particularly Farnsworth House, Illinois Institute of Technology's S. R. Crown Hall, and 860-880 Lake Shore Drive. Diff colors inspired by Dieter Rams' Braun ET66 calculator.\r\n\r\nScreenshot: https:\/\/raw.githubusercontent.com\/jaredgorski\/Mies.vim\/main\/.media\/full-screenshot_mies.png\r\n\r\nAll the usual plugin managers should work.","4":"Bauhaus monochrome colorscheme; a variation on fogbell.vim (https:\/\/github.com\/jaredgorski\/fogbell.vim).\r\n\r\nInspired by Mies Van Der Rohe's architecture in the Chicago area, particularly Farnsworth House, Illinois Institute of Technology's S. R. Crown Hall, and 860-880 Lake Shore Drive. Diff colors inspired by Dieter Rams' Braun ET66 calculator.\r\n\r\nScreenshot: https:\/\/raw.githubusercontent.com\/jaredgorski\/Mies.vim\/main\/.media\/full-screenshot_mies.png\r\n\r\nAll the usual plugin managers should work.","install_details":"","5":"","first_name":"Jared","6":"Jared","last_name":"Gorski","7":"Gorski","releases":[{"0":"6036","vim_version":"7.0","1":"7.0","script_version":"0.0.0","2":"0.0.0","version_comment":"Initial upload","3":"Initial upload","package":"mies.vim","4":"mies.vim","src_id":"28295","5":"28295","creation_date":"1670332978","6":"1670332978"}]},"6035":{"script_id":"6035","0":"6035","script_name":"VimRegDeluxe","1":"VimRegDeluxe","script_type":"utility","2":"utility","summary":"VimRegDeluxe - edit registers as files, e.g. system clipboard & recorded macros","3":"VimRegDeluxe - edit registers as files, e.g. system clipboard & recorded macros","description":"This plugin creates command line abbrevations, each starting with \"vr\" (standing for \"vim register\").\r\n\r\nExamples\r\n- Open registers a, b, c\r\n :vr abc\r\n- Edit the computer clipboard (or any register)\r\n :vre +\r\n- Close any single register or group of register windows\r\n :vrc ab\r\n- Resize register windows\r\n :vrs 5\r\n- Refresh register windows\r\n :vrr\r\n\r\nSee https:\/\/github.com\/m6z\/VimRegDeluxe for more information.\r\n","4":"This plugin creates command line abbrevations, each starting with \"vr\" (standing for \"vim register\").\r\n\r\nExamples\r\n- Open registers a, b, c\r\n :vr abc\r\n- Edit the computer clipboard (or any register)\r\n :vre +\r\n- Close any single register or group of register windows\r\n :vrc ab\r\n- Resize register windows\r\n :vrs 5\r\n- Refresh register windows\r\n :vrr\r\n\r\nSee https:\/\/github.com\/m6z\/VimRegDeluxe for more information.\r\n","install_details":"Copy vimreg_deluxe.vim to ~\/.vim\/plugin","5":"Copy vimreg_deluxe.vim to ~\/.vim\/plugin","first_name":"Michael","6":"Michael","last_name":"Graz","7":"Graz","releases":[{"0":"6035","vim_version":"7.0","1":"7.0","script_version":"1.1","2":"1.1","version_comment":"Initial upload","3":"Initial upload","package":"vimreg_deluxe.vim","4":"vimreg_deluxe.vim","src_id":"28257","5":"28257","creation_date":"1667864458","6":"1667864458"}]},"6034":{"script_id":"6034","0":"6034","script_name":"ecfdef","1":"ecfdef","script_type":"syntax","2":"syntax","summary":"Syntax high","3":"Syntax high","description":"Syntax for ecflow .def files","4":"Syntax for ecflow .def files","install_details":"","5":"","first_name":"Rostislav","6":"Rostislav","last_name":"Kouznetsov","7":"Kouznetsov","releases":[{"0":"6034","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"ecfdef.tar.gz","4":"ecfdef.tar.gz","src_id":"28251","5":"28251","creation_date":"1667765815","6":"1667765815"}]},"6033":{"script_id":"6033","0":"6033","script_name":"vim-deadc0de","1":"vim-deadc0de","script_type":"ftplugin","2":"ftplugin","summary":"Hex editor for Vim. It uses UNIX utility xxd for conversion.","3":"Hex editor for Vim. It uses UNIX utility xxd for conversion.","description":"- Open hex editor by pressing . (Of course, you can set your own\r\n keybinding.) It does buffer conversion.\r\n- When you complete editing, convert to plain text\/blob back by pressing\r\n .\r\n- Vim almost supports hex edition, but it lacks of very important features.\r\n This plugin updates ASCII block of edited blob while you're changing the\r\n HEXes.\r\n- Reverse action is supported too. Edit the ASCII block and it changes the\r\n HEX.\r\n But be sure the edited ASCII line doesn't contain any unprintable\r\n characters, i. e. control sequences. Such characters are presented by\r\n dotas (.).\r\n- The plugin highlights the currently selected byte in HEX block and the\r\n corresponding character in ASCII block.\r\n- Reverse is done too.\r\n- Switch between them by entering \"gs\". (Again, you can set your own\r\n keybinding.)\r\n- Data protection prevents you from breaking a hex file.\r\n Assume you has entered \"x\" character, which is not hexadecimal character.\r\n Buffer would be restored immidiately.\r\n- Data protection can be toggled by \"gp\". (Or another keybinding.)\r\n- xxd utility supports only 7-bit ASCII table encoding that outputs in ASCII\r\n block. (Not all special characters work even so.).\r\n Extended encodings which use eight bit are not supported by xxd.\r\n But this plugin adds support of all printable characters. (One-byte encodings\r\n Latin 1, KOI8-R, CP1251, CP866 are tested; One-byte characters from UTF-8 are\r\n tested.)\r\n- Work with newlines accurately.\r\n Please, set binary mode and turn off EOL if you are editing an blob.\r\n- Open hexadecimal editor in a new buffer. (Due to safety.)\r\n It is saved to temporary directory, usually, \/tmp\/.\r\n- Some options allow to tune the plugin. (Number of them will increase in\r\n future.)","4":"- Open hex editor by pressing . (Of course, you can set your own\r\n keybinding.) It does buffer conversion.\r\n- When you complete editing, convert to plain text\/blob back by pressing\r\n .\r\n- Vim almost supports hex edition, but it lacks of very important features.\r\n This plugin updates ASCII block of edited blob while you're changing the\r\n HEXes.\r\n- Reverse action is supported too. Edit the ASCII block and it changes the\r\n HEX.\r\n But be sure the edited ASCII line doesn't contain any unprintable\r\n characters, i. e. control sequences. Such characters are presented by\r\n dotas (.).\r\n- The plugin highlights the currently selected byte in HEX block and the\r\n corresponding character in ASCII block.\r\n- Reverse is done too.\r\n- Switch between them by entering \"gs\". (Again, you can set your own\r\n keybinding.)\r\n- Data protection prevents you from breaking a hex file.\r\n Assume you has entered \"x\" character, which is not hexadecimal character.\r\n Buffer would be restored immidiately.\r\n- Data protection can be toggled by \"gp\". (Or another keybinding.)\r\n- xxd utility supports only 7-bit ASCII table encoding that outputs in ASCII\r\n block. (Not all special characters work even so.).\r\n Extended encodings which use eight bit are not supported by xxd.\r\n But this plugin adds support of all printable characters. (One-byte encodings\r\n Latin 1, KOI8-R, CP1251, CP866 are tested; One-byte characters from UTF-8 are\r\n tested.)\r\n- Work with newlines accurately.\r\n Please, set binary mode and turn off EOL if you are editing an blob.\r\n- Open hexadecimal editor in a new buffer. (Due to safety.)\r\n It is saved to temporary directory, usually, \/tmp\/.\r\n- Some options allow to tune the plugin. (Number of them will increase in\r\n future.)","install_details":"Install xxd.\r\nInstall Perl interpreter and Iconv binding for it:\r\n\r\n$ sudo apt install xxd\r\n$ sudo apt install perl libtext-iconv-perl\r\n\r\nCopy the plugin to your Vim directory (usually, ~\/.vim\/):\r\n\r\n+ doc\/vim-deadc0de.txt\r\n+ plugin\/vim-deadc0de.vim\r\n+ ftplugin\/xxd.vim \r\n\r\nRebuild the Vim documentation:\r\n\r\n:helptags ~\/.vim\/doc\/\r\n\r\nThen add to your .vimrc:\r\n\r\n\" General behavior\r\nfiletype on \" Enable file detection\r\nfiletype plugin on \" Enable loading the plug-in files for specific file types\r\nsyntax on \" Enable syntax highlighting\r\n\r\n\" Load hex editor\r\nruntime plugins\/vim-deadc0de.vim\r\n\r\n\" Convert to hex \/ convert back using vim-deadc0de\r\nnoremap :HexConvert\r\nimap \r\n\r\n\" Toggle hex file protection by entering \"gp\".\r\n\" This protection is also controlled by g:deadc0de_protection.\r\nmap gp hexprotectiontoggle\r\n\r\n\" Move cursor to the corresponding ASCII character (and then back) by entering\r\n\" \"gs\"\r\nmap gs hexblockscycle\r\n\r\n(You can use any other available keybindings for this purpose.)\r\n\r\nvim-deadc0de is filetype plugin (ftplugin), not syntax plugin.\r\nBut it works in conjunction with xxd.vim syntax plugin by Charles E. Campbell.\r\nxxd.vim should be already installed in your system, check it:\r\n\r\n$ ls \/usr\/share\/vim\/vim*\/syntax\/xxd.vim # Debian- and Ubuntu-based distros path","5":"Install xxd.\r\nInstall Perl interpreter and Iconv binding for it:\r\n\r\n$ sudo apt install xxd\r\n$ sudo apt install perl libtext-iconv-perl\r\n\r\nCopy the plugin to your Vim directory (usually, ~\/.vim\/):\r\n\r\n+ doc\/vim-deadc0de.txt\r\n+ plugin\/vim-deadc0de.vim\r\n+ ftplugin\/xxd.vim \r\n\r\nRebuild the Vim documentation:\r\n\r\n:helptags ~\/.vim\/doc\/\r\n\r\nThen add to your .vimrc:\r\n\r\n\" General behavior\r\nfiletype on \" Enable file detection\r\nfiletype plugin on \" Enable loading the plug-in files for specific file types\r\nsyntax on \" Enable syntax highlighting\r\n\r\n\" Load hex editor\r\nruntime plugins\/vim-deadc0de.vim\r\n\r\n\" Convert to hex \/ convert back using vim-deadc0de\r\nnoremap :HexConvert\r\nimap \r\n\r\n\" Toggle hex file protection by entering \"gp\".\r\n\" This protection is also controlled by g:deadc0de_protection.\r\nmap gp hexprotectiontoggle\r\n\r\n\" Move cursor to the corresponding ASCII character (and then back) by entering\r\n\" \"gs\"\r\nmap gs hexblockscycle\r\n\r\n(You can use any other available keybindings for this purpose.)\r\n\r\nvim-deadc0de is filetype plugin (ftplugin), not syntax plugin.\r\nBut it works in conjunction with xxd.vim syntax plugin by Charles E. Campbell.\r\nxxd.vim should be already installed in your system, check it:\r\n\r\n$ ls \/usr\/share\/vim\/vim*\/syntax\/xxd.vim # Debian- and Ubuntu-based distros path","first_name":"Artem","6":"Artem","last_name":"Korotchenko","7":"Korotchenko","releases":[{"0":"6033","vim_version":"8.2","1":"8.2","script_version":"0.2.1","2":"0.2.1","version_comment":"Increase performance (i. e. speed) of extended HEX-ASCII conversion by multiple thousands of times","3":"Increase performance (i. e. speed) of extended HEX-ASCII conversion by multiple thousands of times","package":"vim-deadc0de.tar.xz","4":"vim-deadc0de.tar.xz","src_id":"28470","5":"28470","creation_date":"1684330148","6":"1684330148"},{"0":"6033","vim_version":"8.2","1":"8.2","script_version":"0.1.9","2":"0.1.9","version_comment":"Plugin rename to vim-deadc0de","3":"Plugin rename to vim-deadc0de","package":"vim-deadc0de.tar.xz","4":"vim-deadc0de.tar.xz","src_id":"28466","5":"28466","creation_date":"1683979159","6":"1683979159"},{"0":"6033","vim_version":"8.2","1":"8.2","script_version":"0.1.7","2":"0.1.7","version_comment":"- Data protection can be toggled by \"gp\". (Or another keybinding.)\r\n\r\nMany bugs had been fixed.","3":"- Data protection can be toggled by \"gp\". (Or another keybinding.)\r\n\r\nMany bugs had been fixed.","package":"vim-hec5.tar.xz","4":"vim-hec5.tar.xz","src_id":"28264","5":"28264","creation_date":"1668344074","6":"1668344074"},{"0":"6033","vim_version":"8.2","1":"8.2","script_version":"0.1.1","2":"0.1.1","version_comment":"Blocks cycle mapping bug fix","3":"Blocks cycle mapping bug fix","package":"vim-hec5.tar.xz","4":"vim-hec5.tar.xz","src_id":"28256","5":"28256","creation_date":"1667823184","6":"1667823184"},{"0":"6033","vim_version":"8.2","1":"8.2","script_version":"0.1.0","2":"0.1.0","version_comment":"- Data protection prevents you from breaking a hex file.\r\n Assume you has entered \"x\" character, which is not hexadecimal character.\r\n Buffer would be restored immidiately.\r\n- Some options allow to tune the plugin. (Number of them will increase in\r\n future.)\r\n\r\nAnd other improvements and bug fixes.","3":"- Data protection prevents you from breaking a hex file.\r\n Assume you has entered \"x\" character, which is not hexadecimal character.\r\n Buffer would be restored immidiately.\r\n- Some options allow to tune the plugin. (Number of them will increase in\r\n future.)\r\n\r\nAnd other improvements and bug fixes.","package":"vim-hec5.tar.xz","4":"vim-hec5.tar.xz","src_id":"28255","5":"28255","creation_date":"1667821466","6":"1667821466"},{"0":"6033","vim_version":"8.2","1":"8.2","script_version":"0.0.11","2":"0.0.11","version_comment":"Initial upload","3":"Initial upload","package":"vim-hec5.tar.xz","4":"vim-hec5.tar.xz","src_id":"28247","5":"28247","creation_date":"1667475970","6":"1667475970"}]},"6032":{"script_id":"6032","0":"6032","script_name":"dialog.vim","1":"dialog.vim","script_type":"syntax","2":"syntax","summary":"Syntax for dialog","3":"Syntax for dialog","description":"Syntax highlighting for the dialog interactive fiction language https:\/\/linusakesson.net\/dialog\/","4":"Syntax highlighting for the dialog interactive fiction language https:\/\/linusakesson.net\/dialog\/","install_details":"","5":"","first_name":"Ptolom","6":"Ptolom","last_name":"","7":"","releases":[{"0":"6032","vim_version":"7.0","1":"7.0","script_version":"1.2","2":"1.2","version_comment":"Nested brackets are highlighted correctly.","3":"Nested brackets are highlighted correctly.","package":"dialog.vim","4":"dialog.vim","src_id":"28226","5":"28226","creation_date":"1666155151","6":"1666155151"}]},"6031":{"script_id":"6031","0":"6031","script_name":"FX-602P Bundle","1":"FX-602P Bundle","script_type":"syntax","2":"syntax","summary":"Preparation Release to create a script on vim.org","3":"Preparation Release to create a script on vim.org","description":"Syntax bundle for the FX-602P series of pocket calculators.","4":"Syntax bundle for the FX-602P series of pocket calculators.","install_details":"use dein","5":"use dein","first_name":"Martin","6":"Martin","last_name":"Krischik","7":"Krischik","releases":[{"0":"6031","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":" Move to deim compatible github repository","3":" Move to deim compatible github repository","package":"vim-fx602p-v_0.1.zip","4":"vim-fx602p-v_0.1.zip","src_id":"28197","5":"28197","creation_date":"1664772055","6":"1664772055"},{"0":"6031","vim_version":"7.0","1":"7.0","script_version":"0.0","2":"0.0","version_comment":"Initial upload","3":"Initial upload","package":"vim-fx602p-v_0.0.zip","4":"vim-fx602p-v_0.0.zip","src_id":"28196","5":"28196","creation_date":"1664757244","6":"1664757244"}]},"6030":{"script_id":"6030","0":"6030","script_name":"fuzzy","1":"fuzzy","script_type":"utility","2":"utility","summary":"Add fuzzy search capabilities to your Vi editor","3":"Add fuzzy search capabilities to your Vi editor","description":"Homepage: https:\/\/github.com\/eranfrie\/fuzzy.vim","4":"Homepage: https:\/\/github.com\/eranfrie\/fuzzy.vim","install_details":"","5":"","first_name":"Eran","6":"Eran","last_name":"Friedman","7":"Friedman","releases":[{"0":"6030","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"fuzzy.zip","4":"fuzzy.zip","src_id":"28195","5":"28195","creation_date":"1664582505","6":"1664582505"}]},"6029":{"script_id":"6029","0":"6029","script_name":"MOS 6502 Assembler","1":"MOS 6502 Assembler","script_type":"syntax","2":"syntax","summary":"Vim syntax highlighting for the ca65 assembler","3":"Vim syntax highlighting for the ca65 assembler","description":"Provides a Vim syntax-highlighting plugin, auto-indent plugin, and filetype plugin for the ca65 assembly language..\r\n\r\n| Vim-Script\t|| https:\/\/www.vim.org\/scripts\/script.php?script_id=6029\r\n| Source\t|| https:\/\/github.com\/krischik\/vim-asm_ca65\r\n| Wiki\t\t|| https:\/\/github.com\/krischik\/vim-asm_ca65\/wiki\r\n| Releases\t|| https:\/\/github.com\/krischik\/vim-asm_ca65\/releases\r\n| Issues\t|| https:\/\/github.com\/krischik\/vim-asm_ca65\/issues\r\n| Discussions\t|| https:\/\/github.com\/krischik\/vim-asm_ca65\/discussions\r\n","4":"Provides a Vim syntax-highlighting plugin, auto-indent plugin, and filetype plugin for the ca65 assembly language..\r\n\r\n| Vim-Script\t|| https:\/\/www.vim.org\/scripts\/script.php?script_id=6029\r\n| Source\t|| https:\/\/github.com\/krischik\/vim-asm_ca65\r\n| Wiki\t\t|| https:\/\/github.com\/krischik\/vim-asm_ca65\/wiki\r\n| Releases\t|| https:\/\/github.com\/krischik\/vim-asm_ca65\/releases\r\n| Issues\t|| https:\/\/github.com\/krischik\/vim-asm_ca65\/issues\r\n| Discussions\t|| https:\/\/github.com\/krischik\/vim-asm_ca65\/discussions\r\n","install_details":"\r\nInstall from https:\/\/github.com\/krischik\/vim-asm_ca65 using dein (https:\/\/github.com\/Shougo\/dein.vim) or similar:\r\n\r\ncall dein#begin('$HOME\/vimfiles\/bundles')\r\ncall dein#add('krischik\/vim-asm_ca65')\r\ncall dein#end()\r\ncall dein#install()","5":"\r\nInstall from https:\/\/github.com\/krischik\/vim-asm_ca65 using dein (https:\/\/github.com\/Shougo\/dein.vim) or similar:\r\n\r\ncall dein#begin('$HOME\/vimfiles\/bundles')\r\ncall dein#add('krischik\/vim-asm_ca65')\r\ncall dein#end()\r\ncall dein#install()","first_name":"Martin","6":"Martin","last_name":"Krischik","7":"Krischik","releases":[{"0":"6029","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"vim-asm_ca65-v_1.0.0.zip","4":"vim-asm_ca65-v_1.0.0.zip","src_id":"28192","5":"28192","creation_date":"1664397194","6":"1664397194"}]},"6028":{"script_id":"6028","0":"6028","script_name":"tinygo.vim","1":"tinygo.vim","script_type":"utility","2":"utility","summary":"TinyGo support to Vim","3":"TinyGo support to Vim","description":"tinygo.vim\r\n\r\nThis is a simple extension to add TinyGo support to Vim and Neovim. Add environment variables for tinygo and restart LSP-server. Using tinygo.vim, you can easily integrate with gopls.\r\n\r\nUsage\r\n\r\nIf an argument is specified, vim-lsp will be restarted with that target setting. If no argument is specified, it will open a list of targets. In that case, target can be selected by pressing ENTER.\r\n\r\n:TinygoTarget open a list of targets.\r\n:TinygoTarget [target] LSP-server will be restarted with that target setting\r\n:TinygoTarget - stop integration\r\n\r\nSupport\r\n\r\n Vim8 + vim-lsp\r\n Vim8 + coc.nvim\r\n Neovim (native LSP client)\r\n Neovim + coc.nvim\r\n\r\nThe GitHub repository is here: https:\/\/github.com\/sago35\/tinygo.vim","4":"tinygo.vim\r\n\r\nThis is a simple extension to add TinyGo support to Vim and Neovim. Add environment variables for tinygo and restart LSP-server. Using tinygo.vim, you can easily integrate with gopls.\r\n\r\nUsage\r\n\r\nIf an argument is specified, vim-lsp will be restarted with that target setting. If no argument is specified, it will open a list of targets. In that case, target can be selected by pressing ENTER.\r\n\r\n:TinygoTarget open a list of targets.\r\n:TinygoTarget [target] LSP-server will be restarted with that target setting\r\n:TinygoTarget - stop integration\r\n\r\nSupport\r\n\r\n Vim8 + vim-lsp\r\n Vim8 + coc.nvim\r\n Neovim (native LSP client)\r\n Neovim + coc.nvim\r\n\r\nThe GitHub repository is here: https:\/\/github.com\/sago35\/tinygo.vim","install_details":"Extract in ~\/.vim (~\\vimfiles on Windows).\r\n\r\nIt depends on the following.\r\n\r\n* gopls + LSP client (vim-lsp, coc.nvim, nvim native LSP client)","5":"Extract in ~\/.vim (~\\vimfiles on Windows).\r\n\r\nIt depends on the following.\r\n\r\n* gopls + LSP client (vim-lsp, coc.nvim, nvim native LSP client)","first_name":"Masaaki","6":"Masaaki","last_name":"Takasago","7":"Takasago","releases":[{"0":"6028","vim_version":"8.0","1":"8.0","script_version":"0.2.0","2":"0.2.0","version_comment":"Initial upload","3":"Initial upload","package":"tinygo.vim.zip","4":"tinygo.vim.zip","src_id":"28190","5":"28190","creation_date":"1664110390","6":"1664110390"}]},"6026":{"script_id":"6026","0":"6026","script_name":"The ObjectSense Programming Language","1":"The ObjectSense Programming Language","script_type":"utility","2":"utility","summary":"An object-oriented reincarnation of VimL","3":"An object-oriented reincarnation of VimL","description":"ObjectSense is a superset of VimL8, and has all the main features of a modern object-oriented language, such as data encapsulation, polymorphism, inheritance, etc. On top of the language implementation, rose - a module manager is provided, which is also built into the language runtime. It's very developer friendly, especially for those who already have a working knowledge of VimL8 can effortlessly expand their skills to code in ObjectSense. \r\n\r\nAs a bonus feature, polyglot programming is easily doable in ObjectSense. Currently vim8 and vim9 are supported, with minimal work the list can grow longer to include other languages, such as, python, ruby, lua, etc. However, as far as the operating system is concerned, only Linux and MacOS are supported at the moment. There is a user-defined command, UT, for doing unit tests of the current class. It's very convenient for accessing class data in unit tests. No need for finding workaround to the language barrier when accessing such data in white box testing. Every component can be properly tested! Pure and simple! By following a few simple conventions and thanks to the built-in modular mechanism in the language runtime, ObjectSense programs are very scalable and development work can be distributed comfortably among team members.\r\n\r\nIn a more programming linguistic point of view, ObjectSense is of imperative paradigm on the surface, but carries functional programming abilities. In the language runtime, each object has its own data and functions, there's nothing shared. An object is entirely in its own universe just like functional programming. Because the lack of time, we haven't explored such property of the language much. Hopefully, the community can shed new lights on such nice combination.\r\n\r\nThis is a strong demonstration of what VimL8 is capable of. ObjectSense takes less than 5000 lines of code for the core of the language implementation. Although it's a superset of an existing language, it's very hard to imagine using such little code for implementing a non-trivial programming language. VimL8 has a lot of unrealised potentials, people really shouldn't jump off the bandwagon too quickly.\r\n\r\nThe best argument for vim9 is performance. We have found a way kind of 'compile' or speedup the load time for ObjectSense. In practice, we could really compile such code into binary and wire it with the language runtime, and without asking developers to learn a completely new language, i.e., being 100% compatible with existing VimL8 syntax and have the acclaimed performance at the same time. However, in our scenario ObjectSense performance issues have been tackled by the semi-compile approach, so no effort was directed to do the real compiling work which could bloat the code base exponentially. \r\n\r\nPlease download and untar the tarball, start from object\/doc\/readme.txt.","4":"ObjectSense is a superset of VimL8, and has all the main features of a modern object-oriented language, such as data encapsulation, polymorphism, inheritance, etc. On top of the language implementation, rose - a module manager is provided, which is also built into the language runtime. It's very developer friendly, especially for those who already have a working knowledge of VimL8 can effortlessly expand their skills to code in ObjectSense. \r\n\r\nAs a bonus feature, polyglot programming is easily doable in ObjectSense. Currently vim8 and vim9 are supported, with minimal work the list can grow longer to include other languages, such as, python, ruby, lua, etc. However, as far as the operating system is concerned, only Linux and MacOS are supported at the moment. There is a user-defined command, UT, for doing unit tests of the current class. It's very convenient for accessing class data in unit tests. No need for finding workaround to the language barrier when accessing such data in white box testing. Every component can be properly tested! Pure and simple! By following a few simple conventions and thanks to the built-in modular mechanism in the language runtime, ObjectSense programs are very scalable and development work can be distributed comfortably among team members.\r\n\r\nIn a more programming linguistic point of view, ObjectSense is of imperative paradigm on the surface, but carries functional programming abilities. In the language runtime, each object has its own data and functions, there's nothing shared. An object is entirely in its own universe just like functional programming. Because the lack of time, we haven't explored such property of the language much. Hopefully, the community can shed new lights on such nice combination.\r\n\r\nThis is a strong demonstration of what VimL8 is capable of. ObjectSense takes less than 5000 lines of code for the core of the language implementation. Although it's a superset of an existing language, it's very hard to imagine using such little code for implementing a non-trivial programming language. VimL8 has a lot of unrealised potentials, people really shouldn't jump off the bandwagon too quickly.\r\n\r\nThe best argument for vim9 is performance. We have found a way kind of 'compile' or speedup the load time for ObjectSense. In practice, we could really compile such code into binary and wire it with the language runtime, and without asking developers to learn a completely new language, i.e., being 100% compatible with existing VimL8 syntax and have the acclaimed performance at the same time. However, in our scenario ObjectSense performance issues have been tackled by the semi-compile approach, so no effort was directed to do the real compiling work which could bloat the code base exponentially. \r\n\r\nPlease download and untar the tarball, start from object\/doc\/readme.txt.","install_details":"1. move the downloaded tarball to ~\/.vim directory, and untar it\r\n mv onecloud-object-sense.tar.gz ~\/.vim\r\n cd ~\/.vim\r\n tar -xvf onecloud-object-sense.tar.gz\r\n\r\n2. open .vimrc and add a line\r\n so ~\/.vim\/object\/ObjectSense.vim\r\n\r\n3. add the following in .vimrc for doing ObjectSense development\r\n const g:OBJECT_SENSE_DEV = 1\r\n\r\n4. to get a taste of the language, check out ~\/.vim\/object\/demo subdirectories","5":"1. move the downloaded tarball to ~\/.vim directory, and untar it\r\n mv onecloud-object-sense.tar.gz ~\/.vim\r\n cd ~\/.vim\r\n tar -xvf onecloud-object-sense.tar.gz\r\n\r\n2. open .vimrc and add a line\r\n so ~\/.vim\/object\/ObjectSense.vim\r\n\r\n3. add the following in .vimrc for doing ObjectSense development\r\n const g:OBJECT_SENSE_DEV = 1\r\n\r\n4. to get a taste of the language, check out ~\/.vim\/object\/demo subdirectories","first_name":"Yiu","6":"Yiu","last_name":"Wing","7":"Wing","releases":[{"0":"6026","vim_version":"8.2","1":"8.2","script_version":"2.1.0","2":"2.1.0","version_comment":"This release focuses on supporting nvim and bug fixes.\r\n\r\n1. ObjectSense works fine with NVIM v0.9.0 onward.\r\n\r\n2. Added memery class support. Developer can generate classes on the\r\n fly, which only exist on the runtime, but not on the hard disk.","3":"This release focuses on supporting nvim and bug fixes.\r\n\r\n1. ObjectSense works fine with NVIM v0.9.0 onward.\r\n\r\n2. Added memery class support. Developer can generate classes on the\r\n fly, which only exist on the runtime, but not on the hard disk.","package":"onecloud-object-sense-2.1.0.tar.gz","4":"onecloud-object-sense-2.1.0.tar.gz","src_id":"28589","5":"28589","creation_date":"1704803791","6":"1704803791"},{"0":"6026","vim_version":"8.2","1":"8.2","script_version":"2.0.0","2":"2.0.0","version_comment":"This is a tremendous update, which really takes ObjectSense into another level and no other language has done before! It can be the ultimate form of literate programming or even beyond literate programming. We started out doing object-oriented programming in vimL, never thought would end up anything like this.\r\n\r\nNow we can have functional, procedural, object-oriented, imperative, declarative, or any existing programming paradigms under one host language - vimL. Polyglot programming can be as easy as abc.\r\n\r\nA new directive Let is added to the language. As a result, we no longer need to have CreateInstance calls when creating new objects. Thusly, making ObjectSense very clean from vimL, only ObjectSense directives and annotations are required when expressing the language. Also there are other new directives added to aid with day to day programming chores from this release.\r\n\r\n1. A new programming construct called micro is introduced. This feature is\r\n conceptually like lisp macro, which blends in the host language seamlessly\r\n and extends linguistic functionality on source code level. Because the\r\n name macro is already taken by vim to mean something else, in order to\r\n avoid confusion and make the distinction of lisp macro, the word 'micro'\r\n is chosen to depict a small piece of code that can have special\r\n interpreting meaning other than the host language, which is vimL in here.\r\n\r\n However, unlike other lisp-like macros, there's no AST involve in our\r\n micro implementation, since vim doesn't use AST at runtime and its parser\r\n is hand-crafted. As a result, ObjectSense requires developers to manually\r\n define the parser, and have the result presented as a vim statement that\r\n can be executed. Nevertheless, because there's no host language or AST\r\n restriction, it can make the DSL much more expressive and have free style\r\n syntax. It's a breeze to embed code from any programming language in\r\n ObjectSense. VimL already has a tone of built-in functions to deal with\r\n strings, it shouldn't be too much effort for a workable DSL parser.\r\n Basically, what the parser does is to take an input of string and convert\r\n it into a vim statement. The micro framework will execute the statement\r\n once it's returned from the parser.\r\n\r\n In lisp-like macros implementations, macros are often compiled, making\r\n them as effective as the host language. However, the current\r\n implementation of micro is not compiled, it has some performance cost.\r\n Future work is planning to compile ObjectSense into vimL9 instructions\r\n while retaining it as a superset of vimL8 syntactically. So vimL9 would\r\n act some kind of VM just like the famous JVM, and ObjectSense will provide\r\n compiler tools for micro\/DSL implementations that need performance boost.\r\nFrom a different perspective, micro puts a layer between the host language\r\n and the guest language, whereas lisp-like macros are sharing the same\r\n execution context directly with the host language. Micro provides better\r\n protection to the host language runtime than traditional APIs and macros,\r\n because the interface between them are strictly available only through the\r\n guest language parser. Also, micros can have richer expressiveness and\r\n abstraction than APIs and macros.\r\n\r\n In real project practice and as time progresses, it's very easy for APIs\r\n and macros to leak internal details to the client code. However,\r\n abstraction through micro DSL would make it much harder to leak the\r\n encapsulating data, because they don't share the same runtime.\r\n Inherently, the side-effects for the usage of micros are much manageable\r\n albeit not immutable.\r\n\r\n Programmers can define their extensions to the language as they like by\r\n using micro. The module dependency mechanism from rose also works with\r\n micro. We can export APIs as well as micros in module description file\r\n Sense.ose. However, the following example demonstrates only exporting\r\n micros, no functions, from MyClass.\r\n export mycompany.business.MyClass\r\n export mycompany.business.MyClass.!\r\n\r\n For the client code that uses micros from MyClass\r\n Import! mycompany.business.MyClass\r\n\r\n Notice or '!' version of Import was adapted to work with importing\r\n micros from a class.\r\n\r\n To create a new micro called Python with the interpreter defined in\r\n s:RunPython, we would have something like the following\r\n Micro Python s:RunPython\r\n\r\n function! s:RunPython(code, extra)\r\n \" just print out whatever was in code\r\n echo a:code\r\n return \"\"\r\n endfun\r\n\r\n To run Python micro, we could have,\r\n Python hello world\r\n Or define a function that would be interpreted by Python micro,\r\n Python! s:Greeting()\r\n This is greeting from python.\r\n End\r\n\r\n call s:Greeting() \"<--- print 'This is greeting from python'\r\n\r\n Variable expansion and string interpolating are taken place before\r\n invoking the interpreter for the micro.\r\n\r\n2. Introduced Let directive, the first letter is upper case L, for assigning\r\n and declaring new objects. We have Dart 2.0 like syntax for create new\r\n objects with the Let directive. For example,\r\n Let object = MyClass()\r\n\r\n This directive let us drop the use of global function CreateInstance, so\r\n being a superset of vimL, the semantics of the language can be defined by\r\n the ObjectSense language directives and annotations only, no exposure to\r\n any functions or other language constructs from vimL.\r\n\r\n The Let directive also supports static constants. To define a static\r\n constant we have the following syntax, in Preload\r\n Class MyClass\r\n\r\n function! s:Preload()\r\n Let! GLOBAL_VAR = \"this is a global variable\"\r\n endfun\r\n\r\n To access in another class, we have to borrow it first,\r\n Borrow! MyClass\r\n\r\n Class ClientCode\r\n\r\n function! s:Move()\r\n echo s:GLOBAL_VAR \" <--- prints \"this is a global variable\"\r\n endfun\r\n\r\n The Let directive also supports inline variable. The following is an\r\n example use of such construct.\r\n Class MyClass\r\n\r\n function! s:Preload()\r\n Let >> context = \"http context\"\r\n endfun\r\n\r\n To use the inline variable context in another class, we will have\r\n Borrow! MyClass\r\n\r\n Class ClientCode\r\n\r\n function! s:Demo()\r\n Let << context\r\n echo context \" <--- prints \"http context\"\r\n endfun\r\n3. Switch statements are supported now, which can take different operators\r\n which are compatible with vim operator, see :h expr4, there's one more\r\n operator, instanceof, added to support type checking.\r\n Switch object instanceof\r\n Case v:t_string echo \"this is a string\"\r\n Case MyClass echo \"this my class\"\r\n Default echo \"not recognised class from object: \" . string(object)\r\n\r\n4. Refine control over module dependency, making the mechanism more workable\r\n with real-life projects. Before sourcing ObjectSense.vim, users can set\r\n g:PRIVILEGED_MODULES variable to allow 3 or less modules that have the\r\n privilege to add dependent modules at runtime.\r\n\r\n5. For more examples, see demo\/micro directory.\r\n\r\n6. The next release will focus on supporting Nvim. Hopefully, ObjectSense\r\n can bring vim and nvim plugin developers under the same roof again.","3":"This is a tremendous update, which really takes ObjectSense into another level and no other language has done before! It can be the ultimate form of literate programming or even beyond literate programming. We started out doing object-oriented programming in vimL, never thought would end up anything like this.\r\n\r\nNow we can have functional, procedural, object-oriented, imperative, declarative, or any existing programming paradigms under one host language - vimL. Polyglot programming can be as easy as abc.\r\n\r\nA new directive Let is added to the language. As a result, we no longer need to have CreateInstance calls when creating new objects. Thusly, making ObjectSense very clean from vimL, only ObjectSense directives and annotations are required when expressing the language. Also there are other new directives added to aid with day to day programming chores from this release.\r\n\r\n1. A new programming construct called micro is introduced. This feature is\r\n conceptually like lisp macro, which blends in the host language seamlessly\r\n and extends linguistic functionality on source code level. Because the\r\n name macro is already taken by vim to mean something else, in order to\r\n avoid confusion and make the distinction of lisp macro, the word 'micro'\r\n is chosen to depict a small piece of code that can have special\r\n interpreting meaning other than the host language, which is vimL in here.\r\n\r\n However, unlike other lisp-like macros, there's no AST involve in our\r\n micro implementation, since vim doesn't use AST at runtime and its parser\r\n is hand-crafted. As a result, ObjectSense requires developers to manually\r\n define the parser, and have the result presented as a vim statement that\r\n can be executed. Nevertheless, because there's no host language or AST\r\n restriction, it can make the DSL much more expressive and have free style\r\n syntax. It's a breeze to embed code from any programming language in\r\n ObjectSense. VimL already has a tone of built-in functions to deal with\r\n strings, it shouldn't be too much effort for a workable DSL parser.\r\n Basically, what the parser does is to take an input of string and convert\r\n it into a vim statement. The micro framework will execute the statement\r\n once it's returned from the parser.\r\n\r\n In lisp-like macros implementations, macros are often compiled, making\r\n them as effective as the host language. However, the current\r\n implementation of micro is not compiled, it has some performance cost.\r\n Future work is planning to compile ObjectSense into vimL9 instructions\r\n while retaining it as a superset of vimL8 syntactically. So vimL9 would\r\n act some kind of VM just like the famous JVM, and ObjectSense will provide\r\n compiler tools for micro\/DSL implementations that need performance boost.\r\nFrom a different perspective, micro puts a layer between the host language\r\n and the guest language, whereas lisp-like macros are sharing the same\r\n execution context directly with the host language. Micro provides better\r\n protection to the host language runtime than traditional APIs and macros,\r\n because the interface between them are strictly available only through the\r\n guest language parser. Also, micros can have richer expressiveness and\r\n abstraction than APIs and macros.\r\n\r\n In real project practice and as time progresses, it's very easy for APIs\r\n and macros to leak internal details to the client code. However,\r\n abstraction through micro DSL would make it much harder to leak the\r\n encapsulating data, because they don't share the same runtime.\r\n Inherently, the side-effects for the usage of micros are much manageable\r\n albeit not immutable.\r\n\r\n Programmers can define their extensions to the language as they like by\r\n using micro. The module dependency mechanism from rose also works with\r\n micro. We can export APIs as well as micros in module description file\r\n Sense.ose. However, the following example demonstrates only exporting\r\n micros, no functions, from MyClass.\r\n export mycompany.business.MyClass\r\n export mycompany.business.MyClass.!\r\n\r\n For the client code that uses micros from MyClass\r\n Import! mycompany.business.MyClass\r\n\r\n Notice or '!' version of Import was adapted to work with importing\r\n micros from a class.\r\n\r\n To create a new micro called Python with the interpreter defined in\r\n s:RunPython, we would have something like the following\r\n Micro Python s:RunPython\r\n\r\n function! s:RunPython(code, extra)\r\n \" just print out whatever was in code\r\n echo a:code\r\n return \"\"\r\n endfun\r\n\r\n To run Python micro, we could have,\r\n Python hello world\r\n Or define a function that would be interpreted by Python micro,\r\n Python! s:Greeting()\r\n This is greeting from python.\r\n End\r\n\r\n call s:Greeting() \"<--- print 'This is greeting from python'\r\n\r\n Variable expansion and string interpolating are taken place before\r\n invoking the interpreter for the micro.\r\n\r\n2. Introduced Let directive, the first letter is upper case L, for assigning\r\n and declaring new objects. We have Dart 2.0 like syntax for create new\r\n objects with the Let directive. For example,\r\n Let object = MyClass()\r\n\r\n This directive let us drop the use of global function CreateInstance, so\r\n being a superset of vimL, the semantics of the language can be defined by\r\n the ObjectSense language directives and annotations only, no exposure to\r\n any functions or other language constructs from vimL.\r\n\r\n The Let directive also supports static constants. To define a static\r\n constant we have the following syntax, in Preload\r\n Class MyClass\r\n\r\n function! s:Preload()\r\n Let! GLOBAL_VAR = \"this is a global variable\"\r\n endfun\r\n\r\n To access in another class, we have to borrow it first,\r\n Borrow! MyClass\r\n\r\n Class ClientCode\r\n\r\n function! s:Move()\r\n echo s:GLOBAL_VAR \" <--- prints \"this is a global variable\"\r\n endfun\r\n\r\n The Let directive also supports inline variable. The following is an\r\n example use of such construct.\r\n Class MyClass\r\n\r\n function! s:Preload()\r\n Let >> context = \"http context\"\r\n endfun\r\n\r\n To use the inline variable context in another class, we will have\r\n Borrow! MyClass\r\n\r\n Class ClientCode\r\n\r\n function! s:Demo()\r\n Let << context\r\n echo context \" <--- prints \"http context\"\r\n endfun\r\n3. Switch statements are supported now, which can take different operators\r\n which are compatible with vim operator, see :h expr4, there's one more\r\n operator, instanceof, added to support type checking.\r\n Switch object instanceof\r\n Case v:t_string echo \"this is a string\"\r\n Case MyClass echo \"this my class\"\r\n Default echo \"not recognised class from object: \" . string(object)\r\n\r\n4. Refine control over module dependency, making the mechanism more workable\r\n with real-life projects. Before sourcing ObjectSense.vim, users can set\r\n g:PRIVILEGED_MODULES variable to allow 3 or less modules that have the\r\n privilege to add dependent modules at runtime.\r\n\r\n5. For more examples, see demo\/micro directory.\r\n\r\n6. The next release will focus on supporting Nvim. Hopefully, ObjectSense\r\n can bring vim and nvim plugin developers under the same roof again.","package":"onecloud-object-sense-2.0.0.tar.gz","4":"onecloud-object-sense-2.0.0.tar.gz","src_id":"28542","5":"28542","creation_date":"1693770761","6":"1693770761"},{"0":"6026","vim_version":"8.2","1":"8.2","script_version":"1.1.5","2":"1.1.5","version_comment":"1. Supported the granularity of export level down to each accessible function\r\n of a class for a module without compromising performance. Three are three\r\n levels of access rights are supported in module export, namely, they are\r\n package, class, and function.\r\n\r\n For the export function to work, we have to export its class first, and\r\n then the function export of a class follows either explicit rule or\r\n implicit rule. If there's no explicit rule specified for an export class,\r\n then all the functions for that class will be implicitly exported.\r\n Otherwise, only those explicitly specified functions will be exported.\r\n\r\n There are three levels of access controls for a class. The first one is\r\n module export which is available for all the modules. This is equivalent\r\n of 'open' for Swift. The next one is internally available within a module\r\n this is where 'accessible' is specified for a function, which is the\r\n equivalent of 'internal' for Swift. The third one is private access\r\n within a class, for functions that have no 'accessible' annotation\r\n attached but have a 's:' in front of the function name.\r\n\r\n2. Support adding pluggable commands to rose. First at all, developer use\r\n the 'command' attribute to define the command name and command callback in\r\n Sense.ose. For example:\r\n command bundle mycompany.object.bundle.BundleCommand\r\n\r\n defines a command called 'bundle', and have the BundleCommand in the\r\n above package as the command callback which inherits a new export class\r\n object.RoseCommand and implement the details in function s:Execute(...).\r\n\r\n3. Introduced a new export class SenseParser which helps customised attributes\r\n to be defined by developers to store module specific data or settings.\r\n This works very much like command attribute. First at all, define the\r\n attribute name and the parser to the attribute.\r\n For example\r\n parser cockpit mycompany.object.cockpit.CockpitParser\r\n \r\n define an attribute called 'cockpit', which will have its data parsed by\r\n CockpitParser. It has three methods, namely, s:OnCommence, s:Process and\r\n s:OnCompletion. The first method is called before the parsing. The\r\n second one is called by the framework when parsing each line of attribute\r\n data. The final one is invoked when finished parsing Sense.ose file.\r\n\r\n4. Supported export class for inheritance.\r\n\r\n5. Support loading multiple modules in QuickStart.\r\n\r\n6. Added bash command line completion for rose.\r\n\r\n7. Fixed some bugs in module accessibility.\r\n\r\n8. Adding more test cases. ","3":"1. Supported the granularity of export level down to each accessible function\r\n of a class for a module without compromising performance. Three are three\r\n levels of access rights are supported in module export, namely, they are\r\n package, class, and function.\r\n\r\n For the export function to work, we have to export its class first, and\r\n then the function export of a class follows either explicit rule or\r\n implicit rule. If there's no explicit rule specified for an export class,\r\n then all the functions for that class will be implicitly exported.\r\n Otherwise, only those explicitly specified functions will be exported.\r\n\r\n There are three levels of access controls for a class. The first one is\r\n module export which is available for all the modules. This is equivalent\r\n of 'open' for Swift. The next one is internally available within a module\r\n this is where 'accessible' is specified for a function, which is the\r\n equivalent of 'internal' for Swift. The third one is private access\r\n within a class, for functions that have no 'accessible' annotation\r\n attached but have a 's:' in front of the function name.\r\n\r\n2. Support adding pluggable commands to rose. First at all, developer use\r\n the 'command' attribute to define the command name and command callback in\r\n Sense.ose. For example:\r\n command bundle mycompany.object.bundle.BundleCommand\r\n\r\n defines a command called 'bundle', and have the BundleCommand in the\r\n above package as the command callback which inherits a new export class\r\n object.RoseCommand and implement the details in function s:Execute(...).\r\n\r\n3. Introduced a new export class SenseParser which helps customised attributes\r\n to be defined by developers to store module specific data or settings.\r\n This works very much like command attribute. First at all, define the\r\n attribute name and the parser to the attribute.\r\n For example\r\n parser cockpit mycompany.object.cockpit.CockpitParser\r\n \r\n define an attribute called 'cockpit', which will have its data parsed by\r\n CockpitParser. It has three methods, namely, s:OnCommence, s:Process and\r\n s:OnCompletion. The first method is called before the parsing. The\r\n second one is called by the framework when parsing each line of attribute\r\n data. The final one is invoked when finished parsing Sense.ose file.\r\n\r\n4. Supported export class for inheritance.\r\n\r\n5. Support loading multiple modules in QuickStart.\r\n\r\n6. Added bash command line completion for rose.\r\n\r\n7. Fixed some bugs in module accessibility.\r\n\r\n8. Adding more test cases. ","package":"onecloud-object-sense-1.1.5.tar.gz","4":"onecloud-object-sense-1.1.5.tar.gz","src_id":"28335","5":"28335","creation_date":"1672577553","6":"1672577553"},{"0":"6026","vim_version":"8.2","1":"8.2","script_version":"1.1.4","2":"1.1.4","version_comment":"1. 'rose test' is able to give a line-based test coverage report and\r\n highlight the lines that are not covered by test\r\n\r\n For example, run the test coverage on rose package that comes with ObjectSense,\r\n cd object\r\n rose test rose -c\r\n Open the browser and visit the generated html.\r\n\r\n2. supported polyglot in QuickStart\r\n\r\n3. introduce UnitTestBelow directive which prevents loading unit test code in\r\n production environment\r\n\r\n4. refactor quite a few number of variable and function names\r\n\r\n5. tighten up some loose logic and fixed a bunch of bugs\r\n\r\n6. provide object.Runtime class to work with the modules at runtime","3":"1. 'rose test' is able to give a line-based test coverage report and\r\n highlight the lines that are not covered by test\r\n\r\n For example, run the test coverage on rose package that comes with ObjectSense,\r\n cd object\r\n rose test rose -c\r\n Open the browser and visit the generated html.\r\n\r\n2. supported polyglot in QuickStart\r\n\r\n3. introduce UnitTestBelow directive which prevents loading unit test code in\r\n production environment\r\n\r\n4. refactor quite a few number of variable and function names\r\n\r\n5. tighten up some loose logic and fixed a bunch of bugs\r\n\r\n6. provide object.Runtime class to work with the modules at runtime","package":"onecloud-object-sense-1.1.4.tar.gz","4":"onecloud-object-sense-1.1.4.tar.gz","src_id":"28171","5":"28171","creation_date":"1662848712","6":"1662848712"},{"0":"6026","vim_version":"8.2","1":"8.2","script_version":"1.1.3","2":"1.1.3","version_comment":"Initial upload","3":"Initial upload","package":"onecloud-object-sense-1.1.3.tar.gz","4":"onecloud-object-sense-1.1.3.tar.gz","src_id":"28125","5":"28125","creation_date":"1660516886","6":"1660516886"}]},"6025":{"script_id":"6025","0":"6025","script_name":"astro","1":"astro","script_type":"ftplugin","2":"ftplugin","summary":"Astro language indentation and syntax support in Vim or Neovim","3":"Astro language indentation and syntax support in Vim or Neovim","description":"https:\/\/github.com\/wuelnerdotexe\/vim-astro#astro-support-for-vim-or-neovim","4":"https:\/\/github.com\/wuelnerdotexe\/vim-astro#astro-support-for-vim-or-neovim","install_details":"https:\/\/github.com\/wuelnerdotexe\/vim-astro#installation","5":"https:\/\/github.com\/wuelnerdotexe\/vim-astro#installation","first_name":"Wuelner","6":"Wuelner","last_name":"Mart\u00c3\u00adnez","7":"Mart\u00c3\u00adnez","releases":[{"0":"6025","vim_version":"7.0","1":"7.0","script_version":"1.2.0","2":"1.2.0","version_comment":"https:\/\/github.com\/wuelnerdotexe\/vim-astro\/blob\/main\/CHANGELOG.md#120---2022-10-06","3":"https:\/\/github.com\/wuelnerdotexe\/vim-astro\/blob\/main\/CHANGELOG.md#120---2022-10-06","package":"vim-astro.zip","4":"vim-astro.zip","src_id":"28561","5":"28561","creation_date":"1697864811","6":"1697864811"}]},"6024":{"script_id":"6024","0":"6024","script_name":"cscope_helper.vim","1":"cscope_helper.vim","script_type":"utility","2":"utility","summary":"Loads and updates cscope.out when gvim\/vim is invoked in subdirectories.","3":"Loads and updates cscope.out when gvim\/vim is invoked in subdirectories.","description":"This Vim plugin is based on prior work from a number of authors. See the\r\ncscope_helper.vim comment header block for details.\r\n\r\nA prerequisite for use is that an initial Cscope database has been generated\r\nin the base directory of the source code file tree. To do so, Cscope can be\r\nexecuted on the command line, or a script like cscope_db_gen can be used\r\nto generate the database. See https:\/\/github.com\/dnygren\/cscope_db_gen\r\nfor an example of how to generate a Cscope database for C\/C++.\r\n\r\nThis plugin will automatically load a cscope.out database (created manually in\r\nthe base directory of a source code file tree) into Vim when you open a file.\r\n\r\nIt performs a search starting at the directory that the edited file is in,\r\nchecking the parent directories until it finds the cscope.out file. Therefore\r\nyou can start editing a file deep in a project directory, and it will find the\r\ncorrect Cscope database. It will also automatically update the Cscope database\r\nafter file saves. If new files are created, the cscope.out database must be\r\nrecreated manually.\r\n\r\nKeystroke macros and a pull down menu are provided to invoke the Cscope\r\nfunctions.\r\n\r\nA cheatsheet is provided to assist in executing the keystroke macros.","4":"This Vim plugin is based on prior work from a number of authors. See the\r\ncscope_helper.vim comment header block for details.\r\n\r\nA prerequisite for use is that an initial Cscope database has been generated\r\nin the base directory of the source code file tree. To do so, Cscope can be\r\nexecuted on the command line, or a script like cscope_db_gen can be used\r\nto generate the database. See https:\/\/github.com\/dnygren\/cscope_db_gen\r\nfor an example of how to generate a Cscope database for C\/C++.\r\n\r\nThis plugin will automatically load a cscope.out database (created manually in\r\nthe base directory of a source code file tree) into Vim when you open a file.\r\n\r\nIt performs a search starting at the directory that the edited file is in,\r\nchecking the parent directories until it finds the cscope.out file. Therefore\r\nyou can start editing a file deep in a project directory, and it will find the\r\ncorrect Cscope database. It will also automatically update the Cscope database\r\nafter file saves. If new files are created, the cscope.out database must be\r\nrecreated manually.\r\n\r\nKeystroke macros and a pull down menu are provided to invoke the Cscope\r\nfunctions.\r\n\r\nA cheatsheet is provided to assist in executing the keystroke macros.","install_details":"Save this file in your plugin directory (e.g. ~\/.vim\/plugin\/cscope_helper.vim ).","5":"Save this file in your plugin directory (e.g. ~\/.vim\/plugin\/cscope_helper.vim ).","first_name":"Dan","6":"Dan","last_name":"Nygren","7":"Nygren","releases":[{"0":"6024","vim_version":"8.1","1":"8.1","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"cscope_helper.tar.gz","4":"cscope_helper.tar.gz","src_id":"28117","5":"28117","creation_date":"1659576815","6":"1659576815"}]},"6023":{"script_id":"6023","0":"6023","script_name":"The NERD term","1":"The NERD term","script_type":"utility","2":"utility","summary":"A term toggle plugin","3":"A term toggle plugin","description":"https:\/\/github.com\/wuelnerdotexe\/nerdterm#the-nerdterm","4":"https:\/\/github.com\/wuelnerdotexe\/nerdterm#the-nerdterm","install_details":"https:\/\/github.com\/wuelnerdotexe\/nerdterm#installation","5":"https:\/\/github.com\/wuelnerdotexe\/nerdterm#installation","first_name":"Wuelner","6":"Wuelner","last_name":"Mart\u00c3\u00adnez","7":"Mart\u00c3\u00adnez","releases":[{"0":"6023","vim_version":"7.0","1":"7.0","script_version":"1.2.0","2":"1.2.0","version_comment":"https:\/\/github.com\/wuelnerdotexe\/nerdterm\/blob\/main\/CHANGELOG.md#120---2023-01-20","3":"https:\/\/github.com\/wuelnerdotexe\/nerdterm\/blob\/main\/CHANGELOG.md#120---2023-01-20","package":"NERD_term.zip","4":"NERD_term.zip","src_id":"28356","5":"28356","creation_date":"1674291203","6":"1674291203"}]},"6022":{"script_id":"6022","0":"6022","script_name":"human","1":"human","script_type":"utility","2":"utility","summary":"Collection of vim default options for humans.","3":"Collection of vim default options for humans.","description":"https:\/\/github.com\/wuelnerdotexe\/human.vim#vim-for-humans","4":"https:\/\/github.com\/wuelnerdotexe\/human.vim#vim-for-humans","install_details":"https:\/\/github.com\/wuelnerdotexe\/human.vim#installation","5":"https:\/\/github.com\/wuelnerdotexe\/human.vim#installation","first_name":"Wuelner","6":"Wuelner","last_name":"Mart\u00c3\u00adnez","7":"Mart\u00c3\u00adnez","releases":[{"0":"6022","vim_version":"8.0","1":"8.0","script_version":"2.2.0","2":"2.2.0","version_comment":"https:\/\/github.com\/wuelnerdotexe\/human.vim\/blob\/main\/CHANGELOG.md#220---2023-10-20","3":"https:\/\/github.com\/wuelnerdotexe\/human.vim\/blob\/main\/CHANGELOG.md#220---2023-10-20","package":"human.zip","4":"human.zip","src_id":"28559","5":"28559","creation_date":"1697863489","6":"1697863489"}]},"6021":{"script_id":"6021","0":"6021","script_name":"Ebitengine Kage","1":"Ebitengine Kage","script_type":"syntax","2":"syntax","summary":"Basic Kage language support for Ebitengine","3":"Basic Kage language support for Ebitengine","description":"Ebitengine adopts an original shading language 'Kage'. This has a compatible syntax with Go, but the details are different. Kage has high portability. Ebitengine uses graphics libraries like OpenGL or Metal and this depends on environments, but Kage is compiled on the fly so that this works equally everywhere.\r\n\r\nThis plugin provides basic Kage language support for Ebitengine. It includes keywords, types, literals and snippets.\r\n","4":"Ebitengine adopts an original shading language 'Kage'. This has a compatible syntax with Go, but the details are different. Kage has high portability. Ebitengine uses graphics libraries like OpenGL or Metal and this depends on environments, but Kage is compiled on the fly so that this works equally everywhere.\r\n\r\nThis plugin provides basic Kage language support for Ebitengine. It includes keywords, types, literals and snippets.\r\n","install_details":"### Make sure you are using vim > 8.0.2 with python3 support. Building the latest version of vim\r\n\r\ngit clone https:\/\/github.com\/vim\/vim.git\r\ncd vim\/src\/\r\n.\/configure --enable-python3interp\r\nmake\r\nsudo make install\r\n\r\n### Install vim-plug plugin manager\r\n\r\ncurl -fLo ~\/.vim\/autoload\/plug.vim --create-dirs \\\r\nhttps:\/\/raw.githubusercontent.com\/junegunn\/vim-plug\/master\/plug.vim\r\n\r\n### Install vim-easycomplete and ultisnips to support hints and snippets\r\n\r\nPlug 'jayli\/vim-easycomplete'\r\nPlug 'SirVer\/ultisnips'\r\n\r\n\r\n### Install sedyh\/ebitengine-kage-vim to enable syntax highlighting and snippet support for Kage\r\n\r\nPlug 'sedyh\/ebitengine-kage-vim'","5":"### Make sure you are using vim > 8.0.2 with python3 support. Building the latest version of vim\r\n\r\ngit clone https:\/\/github.com\/vim\/vim.git\r\ncd vim\/src\/\r\n.\/configure --enable-python3interp\r\nmake\r\nsudo make install\r\n\r\n### Install vim-plug plugin manager\r\n\r\ncurl -fLo ~\/.vim\/autoload\/plug.vim --create-dirs \\\r\nhttps:\/\/raw.githubusercontent.com\/junegunn\/vim-plug\/master\/plug.vim\r\n\r\n### Install vim-easycomplete and ultisnips to support hints and snippets\r\n\r\nPlug 'jayli\/vim-easycomplete'\r\nPlug 'SirVer\/ultisnips'\r\n\r\n\r\n### Install sedyh\/ebitengine-kage-vim to enable syntax highlighting and snippet support for Kage\r\n\r\nPlug 'sedyh\/ebitengine-kage-vim'","first_name":"-","6":"-","last_name":"-","7":"-","releases":[{"0":"6021","vim_version":"8.2","1":"8.2","script_version":"0.1.0","2":"0.1.0","version_comment":"Added snippets support","3":"Added snippets support","package":"ebitengine-kage.zip","4":"ebitengine-kage.zip","src_id":"28100","5":"28100","creation_date":"1658220610","6":"1658220610"},{"0":"6021","vim_version":"7.0","1":"7.0","script_version":"0.0.9","2":"0.0.9","version_comment":"Initial upload","3":"Initial upload","package":"ebitengine-kage.zip","4":"ebitengine-kage.zip","src_id":"28094","5":"28094","creation_date":"1657932475","6":"1657932475"}]},"6020":{"script_id":"6020","0":"6020","script_name":"popdef","1":"popdef","script_type":"utility","2":"utility","summary":"Displays a list of function and class names in the popup window","3":"Displays a list of function and class names in the popup window","description":"This plugin displays a list of function and class names in the popup window.\r\nYou can move to the selected line from the displayed list. It is useful to get\r\nan overview of the source code.\r\n\r\nBy default, the following file types are supported: AsciiDoc, C, C++, Go,\r\nMarkdown, Perl, Python, Ruby, Rust, Scheme, Vim. File types not supported by\r\ndefault can be easily added by setting the pattern to the variable `popdef-patterns`.\r\n\r\nThis plugin was inspired by rdefs.\r\n\r\n https:\/\/github.com\/knsmr\/rdefs\r\n\r\nDevelopment: https:\/\/github.com\/teppey\/popdef\r\n","4":"This plugin displays a list of function and class names in the popup window.\r\nYou can move to the selected line from the displayed list. It is useful to get\r\nan overview of the source code.\r\n\r\nBy default, the following file types are supported: AsciiDoc, C, C++, Go,\r\nMarkdown, Perl, Python, Ruby, Rust, Scheme, Vim. File types not supported by\r\ndefault can be easily added by setting the pattern to the variable `popdef-patterns`.\r\n\r\nThis plugin was inspired by rdefs.\r\n\r\n https:\/\/github.com\/knsmr\/rdefs\r\n\r\nDevelopment: https:\/\/github.com\/teppey\/popdef\r\n","install_details":"Place autoload\/popdef.vim and plugin\/popdef.vim into runtime directory:\r\n\r\n Unix\/macOS:\r\n ~\/.vim\/autoload\/popdef.vim\r\n ~\/.vim\/plugin\/popdef.vim\r\n\r\n Windows:\r\n %USERPROFILE%\\vimfiles\\autoload\\popdef.vim\r\n %USERPROFILE%\\vimfiles\\plugin\\popdef.vim\r\n\r\nIf you need a help file, place doc\/popdef.txt into runtime directory and run\r\n`:helptags ~\/.vim\/doc` (Unix\/macOS) or `:helptags %USERPROFILE%\\vimfiles\\doc` (Windows).\r\n\r\nThis plugin is invoked with the command `:PopDef`. To assign the execution of\r\nthis command to a keymap, for example, set the following in ~\/.vimrc:\r\n\r\n nnoremap d :PopDef\r\n","5":"Place autoload\/popdef.vim and plugin\/popdef.vim into runtime directory:\r\n\r\n Unix\/macOS:\r\n ~\/.vim\/autoload\/popdef.vim\r\n ~\/.vim\/plugin\/popdef.vim\r\n\r\n Windows:\r\n %USERPROFILE%\\vimfiles\\autoload\\popdef.vim\r\n %USERPROFILE%\\vimfiles\\plugin\\popdef.vim\r\n\r\nIf you need a help file, place doc\/popdef.txt into runtime directory and run\r\n`:helptags ~\/.vim\/doc` (Unix\/macOS) or `:helptags %USERPROFILE%\\vimfiles\\doc` (Windows).\r\n\r\nThis plugin is invoked with the command `:PopDef`. To assign the execution of\r\nthis command to a keymap, for example, set the following in ~\/.vimrc:\r\n\r\n nnoremap d :PopDef\r\n","first_name":"Teppei","6":"Teppei","last_name":"Hamada","7":"Hamada","releases":[{"0":"6020","vim_version":"8.2","1":"8.2","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"popdef.zip","4":"popdef.zip","src_id":"28090","5":"28090","creation_date":"1657405566","6":"1657405566"}]},"6019":{"script_id":"6019","0":"6019","script_name":"tabs.vim","1":"tabs.vim","script_type":"utility","2":"utility","summary":"Tabs manager, handy when you open 10+ tabs.","3":"Tabs manager, handy when you open 10+ tabs.","description":"Just a tool to help you manage a heavy amount of tabs on your vim editor.\r\n\r\nUse command :Tabsm or map tm to display the tab manager window.\r\nUse command :Tabsh to show the abridged command help.\r\n\r\nDefault mappings:\r\nEsc+1 to Esc+0 (Win+1, Win+0): move to window number 1 to 10.\r\nEsc+l and Esc+h (Win+l, Win+h): move to next or previous tab.\r\nEsc+, and Esc+. (Win+l, Win+h): move tab a spot right or left.\r\n\r\nConfiguration:\r\n- Deactivate default mappings (tm, ts, tr)\r\n let g:Tabs_useDefaultMappings=0\r\n-Deactivate default tab movement mappings:\r\n let g:Tabs_useDefaultMoveMappings=0\r\n-Deactivate default move to tab number mappings:\r\n let g:g:Tabs_useDefaultGotoMappings=0\r\n","4":"Just a tool to help you manage a heavy amount of tabs on your vim editor.\r\n\r\nUse command :Tabsm or map tm to display the tab manager window.\r\nUse command :Tabsh to show the abridged command help.\r\n\r\nDefault mappings:\r\nEsc+1 to Esc+0 (Win+1, Win+0): move to window number 1 to 10.\r\nEsc+l and Esc+h (Win+l, Win+h): move to next or previous tab.\r\nEsc+, and Esc+. (Win+l, Win+h): move tab a spot right or left.\r\n\r\nConfiguration:\r\n- Deactivate default mappings (tm, ts, tr)\r\n let g:Tabs_useDefaultMappings=0\r\n-Deactivate default tab movement mappings:\r\n let g:Tabs_useDefaultMoveMappings=0\r\n-Deactivate default move to tab number mappings:\r\n let g:g:Tabs_useDefaultGotoMappings=0\r\n","install_details":"Minimum version: Vim 7.0+\r\nRecomended version: Vim 8.0+\r\n\r\nInstall vimball:\r\ndownload tabs_0.0.1.vmb\r\nvim tabs_0.0.1.vmb\r\n:so %\r\n:q ","5":"Minimum version: Vim 7.0+\r\nRecomended version: Vim 8.0+\r\n\r\nInstall vimball:\r\ndownload tabs_0.0.1.vmb\r\nvim tabs_0.0.1.vmb\r\n:so %\r\n:q ","first_name":"Javier","6":"Javier","last_name":"Puigdevall","7":"Puigdevall","releases":[{"0":"6019","vim_version":"7.0","1":"7.0","script_version":"0.0.1","2":"0.0.1","version_comment":"Initial upload","3":"Initial upload","package":"tabs_0.0.1.vmb","4":"tabs_0.0.1.vmb","src_id":"28088","5":"28088","creation_date":"1657319064","6":"1657319064"}]},"6018":{"script_id":"6018","0":"6018","script_name":"Modern Borland","1":"Modern Borland","script_type":"color scheme","2":"color scheme","summary":"A modern Borland-like colorscheme for Vim","3":"A modern Borland-like colorscheme for Vim","description":"The Modern Borland colorscheme for Vim is a tribute to the classic IDE developed by Borland International Inc. in the early 1990'ties. It mimics the look of the interface and the syntax highlighting. Modern Borland is not related to the Borland colorscheme that often ships with vim.\r\n\r\nFor screenshots, issues and more details please visit the project's GitHub page: https:\/\/github.com\/letorbi\/vim-colors-modern-borland","4":"The Modern Borland colorscheme for Vim is a tribute to the classic IDE developed by Borland International Inc. in the early 1990'ties. It mimics the look of the interface and the syntax highlighting. Modern Borland is not related to the Borland colorscheme that often ships with vim.\r\n\r\nFor screenshots, issues and more details please visit the project's GitHub page: https:\/\/github.com\/letorbi\/vim-colors-modern-borland","install_details":"The Modern Borland colorscheme can be easily installed via a plugin-manager like Plug or Vundle. Just add the address of the GitHub repo to your list of plugins:\r\n\r\n \u00e2\u0080\u00a2 Plug: Plug 'letorbi\/vim-colors-modern-borland'\r\n \u00e2\u0080\u00a2 Vundle: Plugin 'letorbi\/vim-colors-modern-borland'\r\n\r\nSome might want to use Vim's native plugin-management or Pathogen instead. In that case you just have to clone the repository into the appropiate path in your Vim config-directory:\r\n\r\n $ git clone https:\/\/github.com\/letorbi\/vim-colors-modern-borland ~\/.vim\/pack\/github\/start\/vim-colors-modern-borland\r\n\r\nIf you don't want to use a plugin-manager at all, you can simply clone the repository and copy the file colors\/borland.vim into your Vim config-directory:\r\n\r\n $ git clone https:\/\/github.com\/letorbi\/vim-colors-modern-borland \/tmp\/vim-colors-modern-borland\r\n $ cp \/tmp\/vim-colors-modern-borland\/colors\/borland.vim ~\/.vim\/colors\/borland.vim","5":"The Modern Borland colorscheme can be easily installed via a plugin-manager like Plug or Vundle. Just add the address of the GitHub repo to your list of plugins:\r\n\r\n \u00e2\u0080\u00a2 Plug: Plug 'letorbi\/vim-colors-modern-borland'\r\n \u00e2\u0080\u00a2 Vundle: Plugin 'letorbi\/vim-colors-modern-borland'\r\n\r\nSome might want to use Vim's native plugin-management or Pathogen instead. In that case you just have to clone the repository into the appropiate path in your Vim config-directory:\r\n\r\n $ git clone https:\/\/github.com\/letorbi\/vim-colors-modern-borland ~\/.vim\/pack\/github\/start\/vim-colors-modern-borland\r\n\r\nIf you don't want to use a plugin-manager at all, you can simply clone the repository and copy the file colors\/borland.vim into your Vim config-directory:\r\n\r\n $ git clone https:\/\/github.com\/letorbi\/vim-colors-modern-borland \/tmp\/vim-colors-modern-borland\r\n $ cp \/tmp\/vim-colors-modern-borland\/colors\/borland.vim ~\/.vim\/colors\/borland.vim","first_name":"Torben","6":"Torben","last_name":"","7":"","releases":[{"0":"6018","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"vim-colors-borland-1.0.zip","4":"vim-colors-borland-1.0.zip","src_id":"28063","5":"28063","creation_date":"1653718470","6":"1653718470"}]},"6017":{"script_id":"6017","0":"6017","script_name":"vim-groff-viewer","1":"vim-groff-viewer","script_type":"ftplugin","2":"ftplugin","summary":"Display Groff files in a document viewer","3":"Display Groff files in a document viewer","description":"A Vim filetype plugin for displaying Groff files in a document viewer as determined by the system default or chosen by the user. The document viewer used should auto-reload and preferably support the postscript file format - examples are Zathura, Evince, Okular or Xreader.\r\n\r\nUsage, configuration, etc: https:\/\/preciouschicken.com\/software\/vim-groff-viewer\/\r\n\r\nVideo demonstration: https:\/\/www.youtube.com\/watch?v=-NOvAKriByM ","4":"A Vim filetype plugin for displaying Groff files in a document viewer as determined by the system default or chosen by the user. The document viewer used should auto-reload and preferably support the postscript file format - examples are Zathura, Evince, Okular or Xreader.\r\n\r\nUsage, configuration, etc: https:\/\/preciouschicken.com\/software\/vim-groff-viewer\/\r\n\r\nVideo demonstration: https:\/\/www.youtube.com\/watch?v=-NOvAKriByM ","install_details":"Install using your preferred plugin manager, for instance with vim-plug:\r\n\r\n Plug 'PreciousChicken\/vim-groff-viewer'\r\n\r\nor dein.vim:\r\n\r\n call dein#add('PreciousChicken\/vim-groff-viewer')\r\n\r\nAlternatively manually install using the Linux terminal:\r\n\r\n mkdir -p ~\/.vim\/pack\/preciouschicken\/start\/groff-viewer\r\n git clone https:\/\/github.com\/PreciousChicken\/vim-groff-viewer.git ~\/.vim\/pack\/preciouschicken\/start\/groff-viewer\r\n\r\nEnsure that you have the line 'filetype plugin on' added to your .vimrc if not already.\r\n\r\nHelptags for the plugin can be loaded by using the command ':helptags ALL' when a groff file is open. Help will then be accessible within Vim via ':help groff-viewer'.","5":"Install using your preferred plugin manager, for instance with vim-plug:\r\n\r\n Plug 'PreciousChicken\/vim-groff-viewer'\r\n\r\nor dein.vim:\r\n\r\n call dein#add('PreciousChicken\/vim-groff-viewer')\r\n\r\nAlternatively manually install using the Linux terminal:\r\n\r\n mkdir -p ~\/.vim\/pack\/preciouschicken\/start\/groff-viewer\r\n git clone https:\/\/github.com\/PreciousChicken\/vim-groff-viewer.git ~\/.vim\/pack\/preciouschicken\/start\/groff-viewer\r\n\r\nEnsure that you have the line 'filetype plugin on' added to your .vimrc if not already.\r\n\r\nHelptags for the plugin can be loaded by using the command ':helptags ALL' when a groff file is open. Help will then be accessible within Vim via ':help groff-viewer'.","first_name":"Gene","6":"Gene","last_name":"","7":"","releases":[{"0":"6017","vim_version":"7.0","1":"7.0","script_version":"v2.0.2","2":"v2.0.2","version_comment":"Fixes breaking change in Neovim where plugin disabled by default.","3":"Fixes breaking change in Neovim where plugin disabled by default.","package":"vim-groff-viewer-2.0.2.tar.gz","4":"vim-groff-viewer-2.0.2.tar.gz","src_id":"28525","5":"28525","creation_date":"1692150446","6":"1692150446"},{"0":"6017","vim_version":"7.0","1":"7.0","script_version":"v2.0.1","2":"v2.0.1","version_comment":"Disabled wordcount functionality for mom macro only.","3":"Disabled wordcount functionality for mom macro only.","package":"vim-groff-viewer-2.0.1.tar.gz","4":"vim-groff-viewer-2.0.1.tar.gz","src_id":"28503","5":"28503","creation_date":"1687142759","6":"1687142759"},{"0":"6017","vim_version":"7.0","1":"7.0","script_version":"v2.0.0","2":"v2.0.0","version_comment":"Added word \/ character count functionality, changed all mapping from to .","3":"Added word \/ character count functionality, changed all mapping from to .","package":"vim-groff-viewer-2.0.0.tar.gz","4":"vim-groff-viewer-2.0.0.tar.gz","src_id":"28258","5":"28258","creation_date":"1667887454","6":"1667887454"},{"0":"6017","vim_version":"7.0","1":"7.0","script_version":"v1.0.4","2":"v1.0.4","version_comment":"Fixed error with printing of non me macro documents, fixed error message when non-groff buffer open at same time.","3":"Fixed error with printing of non me macro documents, fixed error message when non-groff buffer open at same time.","package":"vim-groff-viewer-1.0.4.tar.gz","4":"vim-groff-viewer-1.0.4.tar.gz","src_id":"28170","5":"28170","creation_date":"1662844720","6":"1662844720"},{"0":"6017","vim_version":"7.0","1":"7.0","script_version":"v1.0.2","2":"v1.0.2","version_comment":"Fixed error where whitespace in path would create empty file.","3":"Fixed error where whitespace in path would create empty file.","package":"vim-groff-viewer-1.0.2.tar.gz","4":"vim-groff-viewer-1.0.2.tar.gz","src_id":"28169","5":"28169","creation_date":"1662692045","6":"1662692045"},{"0":"6017","vim_version":"7.0","1":"7.0","script_version":"v1.0.1","2":"v1.0.1","version_comment":"Fixed error where mupdf was unable to open a pdf created with `-T pdf` flag.","3":"Fixed error where mupdf was unable to open a pdf created with `-T pdf` flag.","package":"vim-groff-viewer-1.0.1.tar.gz","4":"vim-groff-viewer-1.0.1.tar.gz","src_id":"28119","5":"28119","creation_date":"1659909997","6":"1659909997"},{"0":"6017","vim_version":"7.0","1":"7.0","script_version":"v1.0.0","2":"v1.0.0","version_comment":"Initial upload","3":"Initial upload","package":"vim-groff-viewer.tar.gz","4":"vim-groff-viewer.tar.gz","src_id":"28048","5":"28048","creation_date":"1652933595","6":"1652933595"}]},"6016":{"script_id":"6016","0":"6016","script_name":"vindent.vim","1":"vindent.vim","script_type":"utility","2":"utility","summary":"Navigate and select text based on indentations.","3":"Navigate and select text based on indentations.","description":"This plugin provides two functionalities:\r\n\r\n1. Jump to previous\/next line with same indentation. (vindent motion)\r\n2. Select adjacent lines with \"same or more or ...\" indentation. (vindent text object: 4 variations)\r\n\r\nThis plugin was partially inspired by vimscript #5106 and vimscript #3037. This plugin is essentially a simplified version of the two plugins combined, but reimplemented with less than 100 lines of vimscript at its core!\r\n\r\nMore details and latest version at: https:\/\/github.com\/jessekelighine\/vindent.vim","4":"This plugin provides two functionalities:\r\n\r\n1. Jump to previous\/next line with same indentation. (vindent motion)\r\n2. Select adjacent lines with \"same or more or ...\" indentation. (vindent text object: 4 variations)\r\n\r\nThis plugin was partially inspired by vimscript #5106 and vimscript #3037. This plugin is essentially a simplified version of the two plugins combined, but reimplemented with less than 100 lines of vimscript at its core!\r\n\r\nMore details and latest version at: https:\/\/github.com\/jessekelighine\/vindent.vim","install_details":"Clone it from Github for latest version: https:\/\/github.com\/jessekelighine\/vindent.vim","5":"Clone it from Github for latest version: https:\/\/github.com\/jessekelighine\/vindent.vim","first_name":"Jesse","6":"Jesse","last_name":"Kelighine","7":"Kelighine","releases":[{"0":"6016","vim_version":"8.2","1":"8.2","script_version":"4.1.1","2":"4.1.1","version_comment":"- Make the auto mappings work.\r\n\r\nNo one told me that this didn't work for so long :'(","3":"- Make the auto mappings work.\r\n\r\nNo one told me that this didn't work for so long :'(","package":"vindent.vim-4.1.1.tar.gz","4":"vindent.vim-4.1.1.tar.gz","src_id":"28069","5":"28069","creation_date":"1654181964","6":"1654181964"},{"0":"6016","vim_version":"8.0","1":"8.0","script_version":"v4.0.0","2":"v4.0.0","version_comment":"v4.0.0: 2022-May-20\r\n\t- Reimplement how indentation is compared and handled: Previously use\r\n\t a custom function to handle the determining of a line's indentation\r\n\t level, now use Vim's native function `indent()`. This change has 2\r\n\t benefits:\r\n\t 1. It automatically assumes equivalence between a and\r\n\t |tabstop| number of s. This is more flexible since Vim\r\n\t can infer filetype specific |tabstop| setting automatically.\r\n\t 2. It returns a number representing the indent level. This makes\r\n\t comparing indent level much faster.\r\n\t As a result, |g:vindent_tabstop| is now obsolete and the user can no\r\n\t longer choose whether s and s should be considered\r\n\t differently.\r\n\t- No longer refuse to select the entire document.\r\n\t- Restructure `autoload` to be more concise.","3":"v4.0.0: 2022-May-20\r\n\t- Reimplement how indentation is compared and handled: Previously use\r\n\t a custom function to handle the determining of a line's indentation\r\n\t level, now use Vim's native function `indent()`. This change has 2\r\n\t benefits:\r\n\t 1. It automatically assumes equivalence between a and\r\n\t |tabstop| number of s. This is more flexible since Vim\r\n\t can infer filetype specific |tabstop| setting automatically.\r\n\t 2. It returns a number representing the indent level. This makes\r\n\t comparing indent level much faster.\r\n\t As a result, |g:vindent_tabstop| is now obsolete and the user can no\r\n\t longer choose whether s and s should be considered\r\n\t differently.\r\n\t- No longer refuse to select the entire document.\r\n\t- Restructure `autoload` to be more concise.","package":"vindent.vim-4.0.0.tar.gz","4":"vindent.vim-4.0.0.tar.gz","src_id":"28052","5":"28052","creation_date":"1653146168","6":"1653146168"},{"0":"6016","vim_version":"8.2","1":"8.2","script_version":"v3.0.2","2":"v3.0.2","version_comment":"v3.0.0 above:\r\n\r\n- Add |vindent_Block_Motions|.\r\n- Expand |vindent_Text_Object|s to be customizable and take counts.","3":"v3.0.0 above:\r\n\r\n- Add |vindent_Block_Motions|.\r\n- Expand |vindent_Text_Object|s to be customizable and take counts.","package":"vindent.vim-3.0.3.tar.gz","4":"vindent.vim-3.0.3.tar.gz","src_id":"28047","5":"28047","creation_date":"1652840756","6":"1652840756"}]},"6015":{"script_id":"6015","0":"6015","script_name":"SwitchColor","1":"SwitchColor","script_type":"utility","2":"utility","summary":"Lets you switch colorschemes easily, and make vim remember your choice.","3":"Lets you switch colorschemes easily, and make vim remember your choice.","description":"SwitchColor loops you though color schemes by hotkey,\r\nand makes Vim remember your choice.\r\n\r\nEnables organizing your colorschemes into themes if you make\r\nsymbolic links to color schemes files in dedicated folders,\r\nand edit a ready boilerplate function in the plugin.\r\n\r\nAuthor: Tommy Bollman (tommy.bollman AT gmail DOT com)\r\nFor Vim version 7.0 and above Last change: May 3, 2022\r\n\r\nVim License. \r\n\r\n\r\n","4":"SwitchColor loops you though color schemes by hotkey,\r\nand makes Vim remember your choice.\r\n\r\nEnables organizing your colorschemes into themes if you make\r\nsymbolic links to color schemes files in dedicated folders,\r\nand edit a ready boilerplate function in the plugin.\r\n\r\nAuthor: Tommy Bollman (tommy.bollman AT gmail DOT com)\r\nFor Vim version 7.0 and above Last change: May 3, 2022\r\n\r\nVim License. \r\n\r\n\r\n","install_details":"* Drop\/copy the plugin SwitchColor.vim into your plugins\r\n\tfolder in your ~\/.vim or $HOME\/vimfiles folder. \r\n\r\n* Drop\/copy the help file SwitchColor.txt into you doc\r\n\tfolder in your ~\/.vim or $HOME\/vimfiles folder. \r\n\r\n* Fire up vim and run the command\t\t:helptags ~\/.vim\/doc or\r\n\t:helptags c:\\Vimfiles\\doc You should now be able to see\r\n\tthe help document by writing |:help SwitchColor| \r\n\r\n* Having seen you can get up the help, with the\r\n\tconfiguration information, its\r\n* time to play with the hotkeys. You may want to change\r\n\tthem. \r\n\r\n|Basics:|\r\n\r\n* opt\/alt 5\/6 goes back\/forward in your colorschemes, loopwise.\r\n\r\n*\t opt\/alt c runs: |:colorschemes | to let you easily cherrypick.\r\n\r\n* opt\/alt g prints the name of the current colorscheme.\r\n\r\n* Try exiting and starting vim again, and control that your\r\n\tlast choosen colorscheme is active. On the rare occasion\r\n\tthat it isn`t, read about |g:SC_dotfilename| in\r\n\tSwitchColor.txt (:h SwitchColor)\r\n\r\n","5":"* Drop\/copy the plugin SwitchColor.vim into your plugins\r\n\tfolder in your ~\/.vim or $HOME\/vimfiles folder. \r\n\r\n* Drop\/copy the help file SwitchColor.txt into you doc\r\n\tfolder in your ~\/.vim or $HOME\/vimfiles folder. \r\n\r\n* Fire up vim and run the command\t\t:helptags ~\/.vim\/doc or\r\n\t:helptags c:\\Vimfiles\\doc You should now be able to see\r\n\tthe help document by writing |:help SwitchColor| \r\n\r\n* Having seen you can get up the help, with the\r\n\tconfiguration information, its\r\n* time to play with the hotkeys. You may want to change\r\n\tthem. \r\n\r\n|Basics:|\r\n\r\n* opt\/alt 5\/6 goes back\/forward in your colorschemes, loopwise.\r\n\r\n*\t opt\/alt c runs: |:colorschemes | to let you easily cherrypick.\r\n\r\n* opt\/alt g prints the name of the current colorscheme.\r\n\r\n* Try exiting and starting vim again, and control that your\r\n\tlast choosen colorscheme is active. On the rare occasion\r\n\tthat it isn`t, read about |g:SC_dotfilename| in\r\n\tSwitchColor.txt (:h SwitchColor)\r\n\r\n","first_name":"Tommy","6":"Tommy","last_name":"Bollman","7":"Bollman","releases":[{"0":"6015","vim_version":"7.0","1":"7.0","script_version":"0.0.7","2":"0.0.7","version_comment":"Improved keybindings thanks to CoolioDood @ Reditt.\r\nHopefully correct retrivial of color files on MS Windows.\r\nRebuilt plugin for lazy load.\r\nReally improved the helpfile.\r\n\r\nEnjoy.","3":"Improved keybindings thanks to CoolioDood @ Reditt.\r\nHopefully correct retrivial of color files on MS Windows.\r\nRebuilt plugin for lazy load.\r\nReally improved the helpfile.\r\n\r\nEnjoy.","package":"SwitchColor.tar.gz","4":"SwitchColor.tar.gz","src_id":"28034","5":"28034","creation_date":"1651875698","6":"1651875698"},{"0":"6015","vim_version":"7.0","1":"7.0","script_version":"0.0.5","2":"0.0.5","version_comment":"Removed reintroduced typo.","3":"Removed reintroduced typo.","package":"SwitchColor.tar.gz","4":"SwitchColor.tar.gz","src_id":"28031","5":"28031","creation_date":"1651712509","6":"1651712509"},{"0":"6015","vim_version":"7.0","1":"7.0","script_version":"0.0.4","2":"0.0.4","version_comment":"Removed an overlooked problem with keymappings.","3":"Removed an overlooked problem with keymappings.","package":"SwitchColor.tar.gz","4":"SwitchColor.tar.gz","src_id":"28030","5":"28030","creation_date":"1651710892","6":"1651710892"},{"0":"6015","vim_version":"7.0","1":"7.0","script_version":"0.0.3","2":"0.0.3","version_comment":"Improved two key bindings to actuate error messages if not unique.","3":"Improved two key bindings to actuate error messages if not unique.","package":"SwitchColor.tar.gz","4":"SwitchColor.tar.gz","src_id":"28029","5":"28029","creation_date":"1651708132","6":"1651708132"},{"0":"6015","vim_version":"7.0","1":"7.0","script_version":"0.0.2","2":"0.0.2","version_comment":"Upgraded key mappings to follow recommended scheme for plugins.\r\nAdded variable for disabling the plugin in .vimrc.\r\nRemoved typo regarding mapping of opt\/alt-g to show current colorscheme.","3":"Upgraded key mappings to follow recommended scheme for plugins.\r\nAdded variable for disabling the plugin in .vimrc.\r\nRemoved typo regarding mapping of opt\/alt-g to show current colorscheme.","package":"SwitchColor.tar.gz","4":"SwitchColor.tar.gz","src_id":"28028","5":"28028","creation_date":"1651706111","6":"1651706111"},{"0":"6015","vim_version":"7.0","1":"7.0","script_version":"0.0.1","2":"0.0.1","version_comment":"Initial upload","3":"Initial upload","package":"SwitchColor.tar.gz","4":"SwitchColor.tar.gz","src_id":"28027","5":"28027","creation_date":"1651685820","6":"1651685820"}]},"6014":{"script_id":"6014","0":"6014","script_name":"highlight.vim","1":"highlight.vim","script_type":"color scheme","2":"color scheme","summary":"A Vim colorscheme with almost no highlighting, except where it matters!","3":"A Vim colorscheme with almost no highlighting, except where it matters!","description":"View screenshots and additional details at: https:\/\/github.com\/igemnace\/highlight.vim\r\n\r\nA simple, low-contrast Vim colorscheme with (drastically) reduced syntax highlighting.\r\n\r\nhttps:\/\/files.emnace.org\/igemnace\/highlight.vim\/c.png\r\n\r\nHighlight only when exceptional. Such is the way of highlight.vim.\r\n\r\nhttps:\/\/files.emnace.org\/igemnace\/highlight.vim\/statusline-default.png\r\nhttps:\/\/files.emnace.org\/igemnace\/highlight.vim\/statusline-modified.png\r\nhttps:\/\/files.emnace.org\/igemnace\/highlight.vim\/statusline-readonly.png\r\nYou can see it in the editor's own UI elements. Notice how the statusline remains unassuming, unless something of note appears.\r\n\r\nhttps:\/\/files.emnace.org\/igemnace\/highlight.vim\/js.png\r\nYou can see it in the syntax highlighting itself. Notice how everything is a colorless white by default. Comments are melded into a background gray. Strings are highlighted.","4":"View screenshots and additional details at: https:\/\/github.com\/igemnace\/highlight.vim\r\n\r\nA simple, low-contrast Vim colorscheme with (drastically) reduced syntax highlighting.\r\n\r\nhttps:\/\/files.emnace.org\/igemnace\/highlight.vim\/c.png\r\n\r\nHighlight only when exceptional. Such is the way of highlight.vim.\r\n\r\nhttps:\/\/files.emnace.org\/igemnace\/highlight.vim\/statusline-default.png\r\nhttps:\/\/files.emnace.org\/igemnace\/highlight.vim\/statusline-modified.png\r\nhttps:\/\/files.emnace.org\/igemnace\/highlight.vim\/statusline-readonly.png\r\nYou can see it in the editor's own UI elements. Notice how the statusline remains unassuming, unless something of note appears.\r\n\r\nhttps:\/\/files.emnace.org\/igemnace\/highlight.vim\/js.png\r\nYou can see it in the syntax highlighting itself. Notice how everything is a colorless white by default. Comments are melded into a background gray. Strings are highlighted.","install_details":"Copy the contents of colors into ~\/.vim on UNIX-like systems, or install with your favorite plugin manager.","5":"Copy the contents of colors into ~\/.vim on UNIX-like systems, or install with your favorite plugin manager.","first_name":"Ian","6":"Ian","last_name":"Emnace","7":"Emnace","releases":[{"0":"6014","vim_version":"7.0","1":"7.0","script_version":"1.0.0","2":"1.0.0","version_comment":"Initial upload","3":"Initial upload","package":"highlight_1.0.0.tar.gz","4":"highlight_1.0.0.tar.gz","src_id":"28009","5":"28009","creation_date":"1650667777","6":"1650667777"}]},"6013":{"script_id":"6013","0":"6013","script_name":"gitTools","1":"gitTools","script_type":"utility","2":"utility","summary":"Set of tools to perform multiple git commands.","3":"Set of tools to perform multiple git commands.","description":"This plugin allows to perform multiple git commands from within vim and show the results.\r\n\r\nAlso: https:\/\/github.com\/javipv\/gitTools.vim\r\n\r\nYou will be able to perferom the basic git commands like, checkout, commit, push, pull, merge, cherry-pick, show-ref, log, navigate through branches and display diffs and vimdiffs on changes.\r\n\r\nThis is a port of plugin svnTools, modified to use git instead of svn.\r\n\r\nUse :Gith to view an abridged command help.\r\n\r\nUse :Git to show the commands on menu to select and launch a commands non requiring arguments. \r\nWhen using a parameter, search all commands and show matching strings.\r\nBy instance: :Git merge to show all commands matching merge screen\r\n\r\nIt is advisable to install hi.vim (https:\/\/www.vim.org\/scripts\/script.php?script_id=5887) to display results colorized.\r\n","4":"This plugin allows to perform multiple git commands from within vim and show the results.\r\n\r\nAlso: https:\/\/github.com\/javipv\/gitTools.vim\r\n\r\nYou will be able to perferom the basic git commands like, checkout, commit, push, pull, merge, cherry-pick, show-ref, log, navigate through branches and display diffs and vimdiffs on changes.\r\n\r\nThis is a port of plugin svnTools, modified to use git instead of svn.\r\n\r\nUse :Gith to view an abridged command help.\r\n\r\nUse :Git to show the commands on menu to select and launch a commands non requiring arguments. \r\nWhen using a parameter, search all commands and show matching strings.\r\nBy instance: :Git merge to show all commands matching merge screen\r\n\r\nIt is advisable to install hi.vim (https:\/\/www.vim.org\/scripts\/script.php?script_id=5887) to display results colorized.\r\n","install_details":"Minimum version: Vim 7.0+\r\nRecomended version: Vim 8.0+\r\n\r\nInstall vimball:\r\ndownload gitTools_0.1.0.vmb\r\nvim gitTools_0.1.0.vmb\r\n:so %\r\n:q ","5":"Minimum version: Vim 7.0+\r\nRecomended version: Vim 8.0+\r\n\r\nInstall vimball:\r\ndownload gitTools_0.1.0.vmb\r\nvim gitTools_0.1.0.vmb\r\n:so %\r\n:q ","first_name":"Javier","6":"Javier","last_name":"Puigdevall","7":"Puigdevall","releases":[{"0":"6013","vim_version":"7.0","1":"7.0","script_version":"0.1.0","2":"0.1.0","version_comment":"- New: command Gitcp (cherry-pick), Gitcpe (cherry-pick --edit) and GitcpNC (chrerry-pick --no-commit)\r\n If no hash provided, try extract hash from current line or word under cursor.\r\n- New: Gitro and Gitrov to change default remote (by default set to: origin, modify on g:gitTools_origin).\r\n- New: Gitc to show git config.\r\n- New: Gitbc to show git config of current branch.\r\n- Fix: on :Gitda show commit log header strings commented.\r\n- NEW!: menu to select options. Apply this menu to every local\/remote branch selection.\r\n- NEW!: command Git, to open a menu and select a git command to launch.\r\n- New: command Gitmcs to search merge tags when solving conflicts.\r\n- New: command GitlG to show graph with only oneline per commit.\r\n- New: Gitreseth and Gitresetm to launch hard and medium resets.\r\n- Change: Gitreset to launch soft reset on provided hash number or hash number under cursor.","3":"- New: command Gitcp (cherry-pick), Gitcpe (cherry-pick --edit) and GitcpNC (chrerry-pick --no-commit)\r\n If no hash provided, try extract hash from current line or word under cursor.\r\n- New: Gitro and Gitrov to change default remote (by default set to: origin, modify on g:gitTools_origin).\r\n- New: Gitc to show git config.\r\n- New: Gitbc to show git config of current branch.\r\n- Fix: on :Gitda show commit log header strings commented.\r\n- NEW!: menu to select options. Apply this menu to every local\/remote branch selection.\r\n- NEW!: command Git, to open a menu and select a git command to launch.\r\n- New: command Gitmcs to search merge tags when solving conflicts.\r\n- New: command GitlG to show graph with only oneline per commit.\r\n- New: Gitreseth and Gitresetm to launch hard and medium resets.\r\n- Change: Gitreset to launch soft reset on provided hash number or hash number under cursor.","package":"gitTools_0.1.0.vmb","4":"gitTools_0.1.0.vmb","src_id":"28498","5":"28498","creation_date":"1686846499","6":"1686846499"},{"0":"6013","vim_version":"7.0","1":"7.0","script_version":"0.0.7","2":"0.0.7","version_comment":"- New: Gitsr ARGS (git show-ref ARGS) and Gitsrt (git show-ref --tags) to call show-ref commands.\r\n- New: Gitid info describe (--tags --always --dirty).\r\n- Fix: improve isGitAvailable time by moving to git branch command.\r\n- New: command Gitrso to show remote branches origin.\r\n- New: command Gitbr to show remote branches.\r\n- Change: for Gitb, Gitsw, Gitbd... improve command speed, do not aswk isGitAvailable.\r\n use git branch response to know if git is available.\r\n- Change: rename git commit all from Gitcma to GitcmAll.\r\n- Change: rename git commit ammend from GitcmA to GitcmAm.\r\n- Change: change conflict merge commands to Gitmc[f\/p\/h\/rm].\r\n- New: command GitmbS to merge branch with squash parameter, merge as a\r\n single commit.\r\n- New: command Gitmb to merge branch.\r\n- New: improve GitRM command to remove files from disk, adding menu option 'a' to\r\n remove all files selected.\r\n- New: command Gitbmv to rename branches.\r\n- Fix: Gitb nor working on empty buffer.\r\n- New: command git status :Gitsta execution on background.\r\n- New: command :Gitreset.\r\n- New: show Gitsw output on new window and highlight.\r\n- New: on status commands Gita, Gitrm, Gitu, GitR and GitRM, accept % as\r\n first argument, and substitute for current file.\r\n- New: commands Gitlf get file's log, and Gitlfd get file's log and diff.\r\n- New: on Gitd commands, add branch names to the buffer name.\r\n- Fix: git merge issue (Gitm) bad substitution removing 'u' from path.\r\n- New: add color highlighting to git pull buffer.\r\n- New: add date to git push and git pull buffer names.\r\n- New: adapt to Jobs.vim change. g:loaded_jobs renamed to g:VimJobsLoaded\r\n- New: launch push and pull commands on background.\r\n- New: on help command (:Gith), add color highlighting.\r\n- New: remote branch merge command Gitmr.\r\n- New: remote branch merge --squash command GitmrS, merge as a single commit.\r\n- New: checkout command Gitco\r\n- New: checkout and new branch command Gitcob","3":"- New: Gitsr ARGS (git show-ref ARGS) and Gitsrt (git show-ref --tags) to call show-ref commands.\r\n- New: Gitid info describe (--tags --always --dirty).\r\n- Fix: improve isGitAvailable time by moving to git branch command.\r\n- New: command Gitrso to show remote branches origin.\r\n- New: command Gitbr to show remote branches.\r\n- Change: for Gitb, Gitsw, Gitbd... improve command speed, do not aswk isGitAvailable.\r\n use git branch response to know if git is available.\r\n- Change: rename git commit all from Gitcma to GitcmAll.\r\n- Change: rename git commit ammend from GitcmA to GitcmAm.\r\n- Change: change conflict merge commands to Gitmc[f\/p\/h\/rm].\r\n- New: command GitmbS to merge branch with squash parameter, merge as a\r\n single commit.\r\n- New: command Gitmb to merge branch.\r\n- New: improve GitRM command to remove files from disk, adding menu option 'a' to\r\n remove all files selected.\r\n- New: command Gitbmv to rename branches.\r\n- Fix: Gitb nor working on empty buffer.\r\n- New: command git status :Gitsta execution on background.\r\n- New: command :Gitreset.\r\n- New: show Gitsw output on new window and highlight.\r\n- New: on status commands Gita, Gitrm, Gitu, GitR and GitRM, accept % as\r\n first argument, and substitute for current file.\r\n- New: commands Gitlf get file's log, and Gitlfd get file's log and diff.\r\n- New: on Gitd commands, add branch names to the buffer name.\r\n- Fix: git merge issue (Gitm) bad substitution removing 'u' from path.\r\n- New: add color highlighting to git pull buffer.\r\n- New: add date to git push and git pull buffer names.\r\n- New: adapt to Jobs.vim change. g:loaded_jobs renamed to g:VimJobsLoaded\r\n- New: launch push and pull commands on background.\r\n- New: on help command (:Gith), add color highlighting.\r\n- New: remote branch merge command Gitmr.\r\n- New: remote branch merge --squash command GitmrS, merge as a single commit.\r\n- New: checkout command Gitco\r\n- New: checkout and new branch command Gitcob","package":"gitTools_0.0.7.vmb","4":"gitTools_0.0.7.vmb","src_id":"28401","5":"28401","creation_date":"1680634289","6":"1680634289"},{"0":"6013","vim_version":"7.0","1":"7.0","script_version":"0.0.6","2":"0.0.6","version_comment":"- New: highlight command help window.\r\n- New: branch delete command Gitbd.\r\n- New: remote branch push command Gitpush.\r\n- New: remote branch delete command Gitpushd.\r\n- New: remote branch pull command Gitpull.\r\n- New: command Gitreme to edit saved remote branches.","3":"- New: highlight command help window.\r\n- New: branch delete command Gitbd.\r\n- New: remote branch push command Gitpush.\r\n- New: remote branch delete command Gitpushd.\r\n- New: remote branch pull command Gitpull.\r\n- New: command Gitreme to edit saved remote branches.","package":"gitTools_0.0.6.vmb","4":"gitTools_0.0.6.vmb","src_id":"28235","5":"28235","creation_date":"1666908307","6":"1666908307"},{"0":"6013","vim_version":"7.0","1":"7.0","script_version":"0.0.5","2":"0.0.5","version_comment":"- Fix: Gitvda, get current branch error.\r\n- New: after commit ask user if merge files should be removed.\r\n- New: command Gitmrm to delete the temporary files (REMOTE, LOCAL, BACKUP)\r\n from previous merge.\r\n- New: for commands Gitm, Gitd and Gitvd, use git diff to get unmerged or modified\r\n files instead of git status.\r\n- Fix: issue on merge command Gitm, error opening layout 3A.\r\n- New: command Gitsthmv to move staged changes to stash.\r\n- New: command Gitsthcp to copy staged changes to stash and keep local copy.\r\n- New: command Gitstha to apply changes from stash.\r\n- New: command Gitsthd to delete apply changes from stash.\r\n- Change: rename Gitsh command to Gitsth.\r\n- New: command Gitsw to perform git switch.\r\n- Change: rename command Gita (show branches) to Gitb.","3":"- Fix: Gitvda, get current branch error.\r\n- New: after commit ask user if merge files should be removed.\r\n- New: command Gitmrm to delete the temporary files (REMOTE, LOCAL, BACKUP)\r\n from previous merge.\r\n- New: for commands Gitm, Gitd and Gitvd, use git diff to get unmerged or modified\r\n files instead of git status.\r\n- Fix: issue on merge command Gitm, error opening layout 3A.\r\n- New: command Gitsthmv to move staged changes to stash.\r\n- New: command Gitsthcp to copy staged changes to stash and keep local copy.\r\n- New: command Gitstha to apply changes from stash.\r\n- New: command Gitsthd to delete apply changes from stash.\r\n- Change: rename Gitsh command to Gitsth.\r\n- New: command Gitsw to perform git switch.\r\n- Change: rename command Gita (show branches) to Gitb.","package":"gitTools_0.0.5.vmb","4":"gitTools_0.0.5.vmb","src_id":"28228","5":"28228","creation_date":"1666283996","6":"1666283996"},{"0":"6013","vim_version":"7.0","1":"7.0","script_version":"0.0.4","2":"0.0.4","version_comment":"- New: on commands Gitda, Gitdf..., add date, hour and branch name to the generated diff file name.\r\n- Fix: commands Gitm, Gitmf, Gitmp used to merge conlicts. Allowed layouts: 1, 2, 3, 4.\r\n- New: command GitcmA to ammend previous commit\r\n- New: command Gitcma to commit all changed files already tracked skipping stage area.\r\n- New: command GitlS to display log changing string.\r\n- New: command Gitla to display log from author.\r\n- New: command Gitrl to display reference log.\r\n- New: command Gitlg to display log graph. Add color highligting with hi.vim plugin.\r\n- Fix: on Gitsh, prevent showing diff path with a\/ and b\/ prefixes.\r\n- Fix: on Gitr, prevent showing diff path with a\/ and b\/ prefixes.\r\n- New: on Gitsh display both git list and git list --stat. Add color highlighting.","3":"- New: on commands Gitda, Gitdf..., add date, hour and branch name to the generated diff file name.\r\n- Fix: commands Gitm, Gitmf, Gitmp used to merge conlicts. Allowed layouts: 1, 2, 3, 4.\r\n- New: command GitcmA to ammend previous commit\r\n- New: command Gitcma to commit all changed files already tracked skipping stage area.\r\n- New: command GitlS to display log changing string.\r\n- New: command Gitla to display log from author.\r\n- New: command Gitrl to display reference log.\r\n- New: command Gitlg to display log graph. Add color highligting with hi.vim plugin.\r\n- Fix: on Gitsh, prevent showing diff path with a\/ and b\/ prefixes.\r\n- Fix: on Gitr, prevent showing diff path with a\/ and b\/ prefixes.\r\n- New: on Gitsh display both git list and git list --stat. Add color highlighting.","package":"gitTools_0.0.4.vmb","4":"gitTools_0.0.4.vmb","src_id":"28191","5":"28191","creation_date":"1664224411","6":"1664224411"},{"0":"6013","vim_version":"7.0","1":"7.0","script_version":"0.0.3","2":"0.0.3","version_comment":"- New: stash command Gitsh [STASH_NUM]\r\n- Fix: perform Gitst on foreground, no need of Jobs.vim.\r\n- New: Gitcm [FILE\/DESC] command.\r\n Launch without arguments to open commit message on first launch, then commit on\r\n second launch.\r\n- New: Gitds command to show diff with all staged chages.\r\n- New: when callign Gitsta, if current buffer already shows a git status,\r\n refresh it, do not ask user to open a new window\/tab.","3":"- New: stash command Gitsh [STASH_NUM]\r\n- Fix: perform Gitst on foreground, no need of Jobs.vim.\r\n- New: Gitcm [FILE\/DESC] command.\r\n Launch without arguments to open commit message on first launch, then commit on\r\n second launch.\r\n- New: Gitds command to show diff with all staged chages.\r\n- New: when callign Gitsta, if current buffer already shows a git status,\r\n refresh it, do not ask user to open a new window\/tab.","package":"gitTools_0.0.3.vmb","4":"gitTools_0.0.3.vmb","src_id":"28115","5":"28115","creation_date":"1659115699","6":"1659115699"},{"0":"6013","vim_version":"7.0","1":"7.0","script_version":"0.0.2","2":"0.0.2","version_comment":"- New: Gitvdf, do not open new tab when asking for vimdiff of current file.\r\n- Fix: Gitvdf always shows file is not modified.\r\n- New: remove from disk command GitRM.\r\n- New: git move command Gitmv.\r\n- New: remove from disk command Gitrm.\r\n- New: git restore command Gitr.\r\n- New: git unstage command Gitu.\r\n- New: git add command Gita.\r\n- Fix: call again ChooseBranchMenu(), when no branch choosen.\r\n- New: Gitm (git merge) command to show on vimdiff the files with conflicts.\r\n- Fix: Gitvd... and GitVD... commands not showing merge issues.","3":"- New: Gitvdf, do not open new tab when asking for vimdiff of current file.\r\n- Fix: Gitvdf always shows file is not modified.\r\n- New: remove from disk command GitRM.\r\n- New: git move command Gitmv.\r\n- New: remove from disk command Gitrm.\r\n- New: git restore command Gitr.\r\n- New: git unstage command Gitu.\r\n- New: git add command Gita.\r\n- Fix: call again ChooseBranchMenu(), when no branch choosen.\r\n- New: Gitm (git merge) command to show on vimdiff the files with conflicts.\r\n- Fix: Gitvd... and GitVD... commands not showing merge issues.","package":"gitTools_0.0.2.vmb","4":"gitTools_0.0.2.vmb","src_id":"28086","5":"28086","creation_date":"1657316668","6":"1657316668"},{"0":"6013","vim_version":"7.0","1":"7.0","script_version":"0.0.1","2":"0.0.1","version_comment":"Initial upload","3":"Initial upload","package":"gitTools_0.0.1.vmb","4":"gitTools_0.0.1.vmb","src_id":"28007","5":"28007","creation_date":"1650408713","6":"1650408713"}]},"6012":{"script_id":"6012","0":"6012","script_name":"soicode.vim","1":"soicode.vim","script_type":"utility","2":"utility","summary":"Soicode plugin for vim","3":"Soicode plugin for vim","description":"# soicode.vim\r\n\r\nMy implementation of the soicode\r\n[vscode plugin](https:\/\/marketplace.visualstudio.com\/items?itemName=swissolyinfo.soicode)\r\nmade for the [Swiss Olympiad in Informatics](https:\/\/soi.ch).\r\ninside of vim.\r\n\r\n## Features\r\n\r\nThis plugin only activates if you are in a working directory which contains\r\nthe word `soi`.\r\n\r\n- You can Create a `.stoml` file with the `:SOICreateStoml` command.\r\n It automatically pastes your clipboard to this file,\r\n so you have to copy the `.stoml` file first.\r\n\r\n The created `.stoml` file has the same name\r\nas the previous file without the file ending.\r\n\r\n- You can run one sample from the `.stoml` file\r\n with the `:SOIRunOneSample ` command.\r\n The cpp file will be compiled and run with the input\r\n from the `.input` value from the `.stoml` file.\r\n\r\n After that the output of the program will be shown in a new tab.\r\n\r\n- You can run all samples from the `.stoml` file\r\n with the `SOI:RunAllSamples` command.\r\n The cpp file will be compiled and run with the input\r\n of all the declared samples from the `.stoml` file.\r\n\r\n After that the output of the program for each sample will be shown in a new tab.\r\n\r\n- You can add a template into the current file with the `:ISOInsertTemplate` command.\r\n If you set the `g:soicode_auto_insert_template` option to 1 in your config file\r\n the template will automatically be inserted if you open a new cpp file in a directory\r\n that contains the word `soi`\r\n\r\n### Todo\r\n\r\n- [x] Create a `.stoml` file with the given in- and outputs.\r\n- [x] Run one sample from the `.stoml` file.\r\n- [x] Run all samples from the `.stoml` file.\r\n- [ ] Run with manual input\r\n- [ ] Debug code\r\n- [x] Insert a template\r\n","4":"# soicode.vim\r\n\r\nMy implementation of the soicode\r\n[vscode plugin](https:\/\/marketplace.visualstudio.com\/items?itemName=swissolyinfo.soicode)\r\nmade for the [Swiss Olympiad in Informatics](https:\/\/soi.ch).\r\ninside of vim.\r\n\r\n## Features\r\n\r\nThis plugin only activates if you are in a working directory which contains\r\nthe word `soi`.\r\n\r\n- You can Create a `.stoml` file with the `:SOICreateStoml` command.\r\n It automatically pastes your clipboard to this file,\r\n so you have to copy the `.stoml` file first.\r\n\r\n The created `.stoml` file has the same name\r\nas the previous file without the file ending.\r\n\r\n- You can run one sample from the `.stoml` file\r\n with the `:SOIRunOneSample ` command.\r\n The cpp file will be compiled and run with the input\r\n from the `.input` value from the `.stoml` file.\r\n\r\n After that the output of the program will be shown in a new tab.\r\n\r\n- You can run all samples from the `.stoml` file\r\n with the `SOI:RunAllSamples` command.\r\n The cpp file will be compiled and run with the input\r\n of all the declared samples from the `.stoml` file.\r\n\r\n After that the output of the program for each sample will be shown in a new tab.\r\n\r\n- You can add a template into the current file with the `:ISOInsertTemplate` command.\r\n If you set the `g:soicode_auto_insert_template` option to 1 in your config file\r\n the template will automatically be inserted if you open a new cpp file in a directory\r\n that contains the word `soi`\r\n\r\n### Todo\r\n\r\n- [x] Create a `.stoml` file with the given in- and outputs.\r\n- [x] Run one sample from the `.stoml` file.\r\n- [x] Run all samples from the `.stoml` file.\r\n- [ ] Run with manual input\r\n- [ ] Debug code\r\n- [x] Insert a template\r\n","install_details":"Use your package manager or clone it manually from github https:\/\/github.com\/MrSpoony\/soicode.vim\r\n","5":"Use your package manager or clone it manually from github https:\/\/github.com\/MrSpoony\/soicode.vim\r\n","first_name":"Kimi","6":"Kimi","last_name":"L\u00c3\u00b6ffel","7":"L\u00c3\u00b6ffel","releases":[{"0":"6012","vim_version":"7.0","1":"7.0","script_version":"0.0.1","2":"0.0.1","version_comment":"Initial upload","3":"Initial upload","package":"soicode.vim.tar.gz","4":"soicode.vim.tar.gz","src_id":"27993","5":"27993","creation_date":"1649741405","6":"1649741405"}]},"6011":{"script_id":"6011","0":"6011","script_name":"vim-linebox","1":"vim-linebox","script_type":"utility","2":"utility","summary":"The VIM lines and boxes plugin","3":"The VIM lines and boxes plugin","description":"For more info, visit https:\/\/github.com\/yoshi1123\/vim-linebox\r\n\r\nDemo here: https:\/\/github.com\/yoshi1123\/vim-linebox\/blob\/master\/doc\/vim-linebox-demo.gif\r\n\r\nlinebox is a vim plugin to draw boxes and lines. Boxes are drawn by visually\r\nselecting a rectangle, and then pressing either `b` or `B`\r\n(with default mappings, enabled in vimrc). Lines are drawn by setting a start\r\nand end mark, and pressing `L` (with default mappings, enabled in\r\nvimrc). This will find the shortest path, from start to end (if there is a\r\npath), no matter where the start and end positions are, avoiding any text.\r\nLines can start and stop on other lines, and will merge with them.\r\n\r\n\r\nFeatures:\r\n\r\n- Draw boxes with b\r\n- Draw blended boxes with B\r\n- Draw lines with L\r\n\r\n\r\nQuick Start:\r\n\r\nAdd let g:linebox_default_maps = 1 to your vimrc (see \"Default mappings\" below).\r\n\r\nBoxes:\r\n\r\nUse visual mode to select a rectable, and make a box with b.\r\n\r\nUse visual mode to select a rectable, and make a box with B to blend with other lines.\r\n\r\nLines:\r\n\r\nMake a start and end mark with marks `a and `b. Then draw a line with L.\r\n\r\nNOTE: There must be a path of whitespace from mark a to mark b.","4":"For more info, visit https:\/\/github.com\/yoshi1123\/vim-linebox\r\n\r\nDemo here: https:\/\/github.com\/yoshi1123\/vim-linebox\/blob\/master\/doc\/vim-linebox-demo.gif\r\n\r\nlinebox is a vim plugin to draw boxes and lines. Boxes are drawn by visually\r\nselecting a rectangle, and then pressing either `b` or `B`\r\n(with default mappings, enabled in vimrc). Lines are drawn by setting a start\r\nand end mark, and pressing `L` (with default mappings, enabled in\r\nvimrc). This will find the shortest path, from start to end (if there is a\r\npath), no matter where the start and end positions are, avoiding any text.\r\nLines can start and stop on other lines, and will merge with them.\r\n\r\n\r\nFeatures:\r\n\r\n- Draw boxes with b\r\n- Draw blended boxes with B\r\n- Draw lines with L\r\n\r\n\r\nQuick Start:\r\n\r\nAdd let g:linebox_default_maps = 1 to your vimrc (see \"Default mappings\" below).\r\n\r\nBoxes:\r\n\r\nUse visual mode to select a rectable, and make a box with b.\r\n\r\nUse visual mode to select a rectable, and make a box with B to blend with other lines.\r\n\r\nLines:\r\n\r\nMake a start and end mark with marks `a and `b. Then draw a line with L.\r\n\r\nNOTE: There must be a path of whitespace from mark a to mark b.","install_details":"NOTE: On Windows, replace the directory ~\/.vim with ~\/vimfiles\r\n\r\nGithub:\r\n\r\n Vim Packages\r\n Linux\/Unix\/OSX:\r\n git clone --recursive https:\/\/github.com\/yoshi1123\/vim-linebox ~\/.vim\/pack\/bundle\/start\/vim-linebox\r\n Run :helptags ~\/.vim\/pack\/bundle\/start\/vim-linebox\/doc\r\n Windows:\r\n git clone --recursive https:\/\/github.com\/yoshi1123\/vim-linebox ~\/vimfiles\/pack\/bundle\/start\/vim-linebox\r\n Run :helptags ~\/vimfiles\/pack\/bundle\/start\/vim-linebox\/doc\r\n Pathogen\r\n Linux\/Unix\/OSX:\r\n git clone --recursive https:\/\/github.com\/yoshi1123\/vim-linebox ~\/.vim\/bundle\/vim-linebox\r\n Windows:\r\n git clone --recursive https:\/\/github.com\/yoshi1123\/vim-linebox ~\/.vim\/bundle\/vim-linebox\r\n Vundle\r\n Add Bundle 'https:\/\/github.com\/yoshi1123\/vim-linebox' to .vimrc\r\n Run :BundleInstall\r\n NeoBundle\r\n Add NeoBundle 'https:\/\/github.com\/yoshi1123\/vim-linebox' to .vimrc\r\n Run :NeoBundleInstall\r\n vim-plug\r\n Add Plug 'https:\/\/github.com\/yoshi1123\/vim-linebox' to .vimrc\r\n Run :PlugInstall\r\n\r\n\r\nZIP:\r\n\r\n Unzip to ~\/.vim\/pack\/bundle\/start\/vim-linebox \r\n Run :helptags ~\/.vim\/pack\/bundle\/start\/vim-linebox\/doc","5":"NOTE: On Windows, replace the directory ~\/.vim with ~\/vimfiles\r\n\r\nGithub:\r\n\r\n Vim Packages\r\n Linux\/Unix\/OSX:\r\n git clone --recursive https:\/\/github.com\/yoshi1123\/vim-linebox ~\/.vim\/pack\/bundle\/start\/vim-linebox\r\n Run :helptags ~\/.vim\/pack\/bundle\/start\/vim-linebox\/doc\r\n Windows:\r\n git clone --recursive https:\/\/github.com\/yoshi1123\/vim-linebox ~\/vimfiles\/pack\/bundle\/start\/vim-linebox\r\n Run :helptags ~\/vimfiles\/pack\/bundle\/start\/vim-linebox\/doc\r\n Pathogen\r\n Linux\/Unix\/OSX:\r\n git clone --recursive https:\/\/github.com\/yoshi1123\/vim-linebox ~\/.vim\/bundle\/vim-linebox\r\n Windows:\r\n git clone --recursive https:\/\/github.com\/yoshi1123\/vim-linebox ~\/.vim\/bundle\/vim-linebox\r\n Vundle\r\n Add Bundle 'https:\/\/github.com\/yoshi1123\/vim-linebox' to .vimrc\r\n Run :BundleInstall\r\n NeoBundle\r\n Add NeoBundle 'https:\/\/github.com\/yoshi1123\/vim-linebox' to .vimrc\r\n Run :NeoBundleInstall\r\n vim-plug\r\n Add Plug 'https:\/\/github.com\/yoshi1123\/vim-linebox' to .vimrc\r\n Run :PlugInstall\r\n\r\n\r\nZIP:\r\n\r\n Unzip to ~\/.vim\/pack\/bundle\/start\/vim-linebox \r\n Run :helptags ~\/.vim\/pack\/bundle\/start\/vim-linebox\/doc","first_name":"","6":"","last_name":"","7":"","releases":[{"0":"6011","vim_version":"7.0","1":"7.0","script_version":"1.0c2","2":"1.0c2","version_comment":"Workaround for mark bug in Vim","3":"Workaround for mark bug in Vim","package":"vim-linebox-1.0c2.zip","4":"vim-linebox-1.0c2.zip","src_id":"27994","5":"27994","creation_date":"1649747834","6":"1649747834"},{"0":"6011","vim_version":"7.0","1":"7.0","script_version":"1.0c1","2":"1.0c1","version_comment":"Initial upload","3":"Initial upload","package":"vim-linebox-master.zip","4":"vim-linebox-master.zip","src_id":"27991","5":"27991","creation_date":"1649690839","6":"1649690839"}]},"6010":{"script_id":"6010","0":"6010","script_name":"Birdie","1":"Birdie","script_type":"utility","2":"utility","summary":"A Vim plugin that facilitates Verilog netlist tracing.","3":"A Vim plugin that facilitates Verilog netlist tracing.","description":"Available commands\r\n\r\nCommands should be invoked in the window showing the netlist.\r\n\r\nParse a Verilog netlist using the closed source parser:\r\n\r\n:Parse\r\n:ParseAll\r\n\r\n:Parse just extracts the user-defined Verilog modules and instances; whereas :ParseAll extracts everything, and standard cells will be shown in the hierarchy.\r\n\r\nShow the information of the module under the cursor:\r\n\r\n:Module\r\n\r\nGo to the definition of the module whose name matches with the given regular expression:\r\n\r\n:GoToModule \r\n\r\nGo to the declaration of the instance whose instance path matches with the given regular expression:\r\n\r\n:GoToInstance \r\n\r\nExtract the definition of a module and put it on a separate buffer\/window:\r\n\r\n:OneModule \r\n\r\nShow the hierarchy of the design:\r\n\r\n:Hier\r\n\r\nSource hosted at github: https:\/\/github.com\/tklam\/birdie\r\nDemo .gif also available on github\r\nThanks a lot for using","4":"Available commands\r\n\r\nCommands should be invoked in the window showing the netlist.\r\n\r\nParse a Verilog netlist using the closed source parser:\r\n\r\n:Parse\r\n:ParseAll\r\n\r\n:Parse just extracts the user-defined Verilog modules and instances; whereas :ParseAll extracts everything, and standard cells will be shown in the hierarchy.\r\n\r\nShow the information of the module under the cursor:\r\n\r\n:Module\r\n\r\nGo to the definition of the module whose name matches with the given regular expression:\r\n\r\n:GoToModule \r\n\r\nGo to the declaration of the instance whose instance path matches with the given regular expression:\r\n\r\n:GoToInstance \r\n\r\nExtract the definition of a module and put it on a separate buffer\/window:\r\n\r\n:OneModule \r\n\r\nShow the hierarchy of the design:\r\n\r\n:Hier\r\n\r\nSource hosted at github: https:\/\/github.com\/tklam\/birdie\r\nDemo .gif also available on github\r\nThanks a lot for using","install_details":"pip install hdlConverter\r\n\r\nor you can install the Wheel file available on github.\r\n\r\nJust :source the given vim_plugin\/birdie.vim\r\nThis plugin works in x86_64 Linux only","5":"pip install hdlConverter\r\n\r\nor you can install the Wheel file available on github.\r\n\r\nJust :source the given vim_plugin\/birdie.vim\r\nThis plugin works in x86_64 Linux only","first_name":"TK","6":"TK","last_name":"Lam","7":"Lam","releases":[{"0":"6010","vim_version":"7.0","1":"7.0","script_version":"2.0","2":"2.0","version_comment":"hdlConverter is used instead of the the proprietary parser.\r\n\r\nThe problem with the proprietary parser is that its data structures are not available in Python. As a result, communication between the proprietary parser and the Vim script is based on a big JSON file, which is extremely inefficient. Using hdlConverter boosts the overall performance significantly. This script now requries the user to install hdlConverter, though.","3":"hdlConverter is used instead of the the proprietary parser.\r\n\r\nThe problem with the proprietary parser is that its data structures are not available in Python. As a result, communication between the proprietary parser and the Vim script is based on a big JSON file, which is extremely inefficient. Using hdlConverter boosts the overall performance significantly. This script now requries the user to install hdlConverter, though.","package":"birdie.zip","4":"birdie.zip","src_id":"28623","5":"28623","creation_date":"1709090108","6":"1709090108"},{"0":"6010","vim_version":"7.0","1":"7.0","script_version":"1.2","2":"1.2","version_comment":"- Support Python 3.10\r\n- Print instance path before module name","3":"- Support Python 3.10\r\n- Print instance path before module name","package":"birdie.zip","4":"birdie.zip","src_id":"28038","5":"28038","creation_date":"1652400141","6":"1652400141"},{"0":"6010","vim_version":"7.0","1":"7.0","script_version":"1.1","2":"1.1","version_comment":"Increased the parser's stack size so that it can process large netlists.","3":"Increased the parser's stack size so that it can process large netlists.","package":"birdie.zip","4":"birdie.zip","src_id":"28010","5":"28010","creation_date":"1650672926","6":"1650672926"},{"0":"6010","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"birdie.zip","4":"birdie.zip","src_id":"27986","5":"27986","creation_date":"1649623532","6":"1649623532"}]},"6009":{"script_id":"6009","0":"6009","script_name":"MarkX","1":"MarkX","script_type":"utility","2":"utility","summary":"Places signs in the margin to indicate where marks are, (auto-)sel. & del marks,","3":"Places signs in the margin to indicate where marks are, (auto-)sel. & del marks,","description":"NTRODUCTION\r\n\r\nThe primary function of MarkX is to place signs in the left margin (in the signs margin, oddly enough) to indicate where marks are placed, and keep them updated (something that existing solutions to this problem - at least the ones that I tried - don't seem to do very well, which is why I wrote MarkX in the first place).\r\n\r\nMarkX also provides some extra functionality to help with marks; the most significant being that it can auto-select a free mark for you (so you don't have to remember which marks are free) and place it for you.\r\n\r\nThere are quite a few configuration options that control exactly how MarkX behaves - I strongly suggest you read the README file so you can configure MarkX to get the best out of it.\r\n\r\nNOTE: I really have no idea what the minimum vim version requirement is to run MarkX and I don't know of a practical way of finding out (I've only used it on v8.2). The best I can suggest is to try it; it will probably work and if it doesn't then let me know and I'll see if I can sort it\r\n\r\n*** If you have any suggestions for improving this, then please let me know. If you think it's rubbish then PLEASE let me know why - it's far more useful than just 'voting it down' (which really doesn't help at all). Contact details are in the top of the README file ***","4":"NTRODUCTION\r\n\r\nThe primary function of MarkX is to place signs in the left margin (in the signs margin, oddly enough) to indicate where marks are placed, and keep them updated (something that existing solutions to this problem - at least the ones that I tried - don't seem to do very well, which is why I wrote MarkX in the first place).\r\n\r\nMarkX also provides some extra functionality to help with marks; the most significant being that it can auto-select a free mark for you (so you don't have to remember which marks are free) and place it for you.\r\n\r\nThere are quite a few configuration options that control exactly how MarkX behaves - I strongly suggest you read the README file so you can configure MarkX to get the best out of it.\r\n\r\nNOTE: I really have no idea what the minimum vim version requirement is to run MarkX and I don't know of a practical way of finding out (I've only used it on v8.2). The best I can suggest is to try it; it will probably work and if it doesn't then let me know and I'll see if I can sort it\r\n\r\n*** If you have any suggestions for improving this, then please let me know. If you think it's rubbish then PLEASE let me know why - it's far more useful than just 'voting it down' (which really doesn't help at all). Contact details are in the top of the README file ***","install_details":"Just un-tar into ~\/.vim\/bundle\/ as usual and read the README file for config options","5":"Just un-tar into ~\/.vim\/bundle\/ as usual and read the README file for config options","first_name":"Richard","6":"Richard","last_name":"Bentley-Green","7":"Bentley-Green","releases":[{"0":"6009","vim_version":"7.0","1":"7.0","script_version":"22\/03\/2023","2":"22\/03\/2023","version_comment":"Typo correction in docs for mapping 'm'","3":"Typo correction in docs for mapping 'm'","package":"markx.tar.gz","4":"markx.tar.gz","src_id":"28391","5":"28391","creation_date":"1679527124","6":"1679527124"},{"0":"6009","vim_version":"7.0","1":"7.0","script_version":"06\/03\/2023","2":"06\/03\/2023","version_comment":"- Suppress auto-scan\/refresh if the current buffer is the 'Command Line' (ref. `q:`). Trying to scan in this case causes an error to be output.\r\n- Trivial typo correction to documentation (not important)\r\n","3":"- Suppress auto-scan\/refresh if the current buffer is the 'Command Line' (ref. `q:`). Trying to scan in this case causes an error to be output.\r\n- Trivial typo correction to documentation (not important)\r\n","package":"markx.tar.gz","4":"markx.tar.gz","src_id":"28379","5":"28379","creation_date":"1678174893","6":"1678174893"},{"0":"6009","vim_version":"7.0","1":"7.0","script_version":"08\/05\/2022","2":"08\/05\/2022","version_comment":"- Added protection against an error that can occur if '&secure' is set. I don't really understand this, but the fix seems to address the problem. I saw the issue when using the vim-abolish plugin by Tim Pope. To reproduce the error, when over a word, press 'cr' and then wait until the 'CursorHold' event kicks in, which causes markx#RefreshAll() to execute. It's at this point that the error manifests itself.\r\n","3":"- Added protection against an error that can occur if '&secure' is set. I don't really understand this, but the fix seems to address the problem. I saw the issue when using the vim-abolish plugin by Tim Pope. To reproduce the error, when over a word, press 'cr' and then wait until the 'CursorHold' event kicks in, which causes markx#RefreshAll() to execute. It's at this point that the error manifests itself.\r\n","package":"markx.tar.gz","4":"markx.tar.gz","src_id":"28036","5":"28036","creation_date":"1652059104","6":"1652059104"},{"0":"6009","vim_version":"7.0","1":"7.0","script_version":"16\/04\/2022","2":"16\/04\/2022","version_comment":"- Corrected help filename - was .doc, should be .txt - oops!","3":"- Corrected help filename - was .doc, should be .txt - oops!","package":"markx.tar.gz","4":"markx.tar.gz","src_id":"28004","5":"28004","creation_date":"1650147872","6":"1650147872"},{"0":"6009","vim_version":"7.2","1":"7.2","script_version":"10\/04\/2022","2":"10\/04\/2022","version_comment":"- Added `m@` mapping to toggle displaying of signs for ALL marks\r\n- Corrected a number of comparisons which should be case-sensitive but may not be in some vim configurations\r\n- Corrected some configuration setting names - oops!","3":"- Added `m@` mapping to toggle displaying of signs for ALL marks\r\n- Corrected a number of comparisons which should be case-sensitive but may not be in some vim configurations\r\n- Corrected some configuration setting names - oops!","package":"markx.tar.gz","4":"markx.tar.gz","src_id":"27990","5":"27990","creation_date":"1649639284","6":"1649639284"},{"0":"6009","vim_version":"7.2","1":"7.2","script_version":"30\/03\/22","2":"30\/03\/22","version_comment":"Initial upload","3":"Initial upload","package":"markx.tar.gz","4":"markx.tar.gz","src_id":"27983","5":"27983","creation_date":"1649386461","6":"1649386461"}]},"6008":{"script_id":"6008","0":"6008","script_name":"vim-board","1":"vim-board","script_type":"utility","2":"utility","summary":"Easy notes and shortcuts","3":"Easy notes and shortcuts","description":"This plugin introduces a file type \"board\" where you can write quick notes and some shortcuts to\r\nfiles, directories and additional commands.\r\n\r\nFEATURE\r\n\r\n After setting a custom \"Key\", you can use the following key sequence to bring up the board:\r\n\r\n Key Enter\r\n\r\n and to return:\r\n\r\n Key Esc\r\n\r\nREADME\r\n \r\n https:\/\/github.com\/azabiong\/vim-board\r\n\r\nHELP\r\n\r\n :h vim-board\r\n\r\n\r\n","4":"This plugin introduces a file type \"board\" where you can write quick notes and some shortcuts to\r\nfiles, directories and additional commands.\r\n\r\nFEATURE\r\n\r\n After setting a custom \"Key\", you can use the following key sequence to bring up the board:\r\n\r\n Key Enter\r\n\r\n and to return:\r\n\r\n Key Esc\r\n\r\nREADME\r\n \r\n https:\/\/github.com\/azabiong\/vim-board\r\n\r\nHELP\r\n\r\n :h vim-board\r\n\r\n\r\n","install_details":"If you have a plugin manager, it would be handy to use it.\r\n\r\nTo install the plugin from the downloaded archive using Vim's built-in package feature, it may be\r\nconvenient to run the following commands using copy and paste from the downloaded location.\r\n\r\n(Linux, Mac)\r\n PLUG=\"$HOME\/.vim\/pack\/azabiong\/start\"\r\n mkdir -p \"$PLUG\"\r\n unzip -o -d \"$PLUG\" vim-board.zip\r\n vim -u NONE -c \"helptags $PLUG\/vim-board\/doc\" -c q\r\n\r\n(Windows)\r\n cmd.exe\r\n set PLUG=\"%USERPROFILE%\/vimfiles\/pack\/azabiong\/start\"\r\n mkdir %PLUG%\r\n unzip -o -d %PLUG% vim-board.zip\r\n vim -u NONE -c \"helptags %PLUG%\/vim-board\/doc\" -c q\r\n\r\n","5":"If you have a plugin manager, it would be handy to use it.\r\n\r\nTo install the plugin from the downloaded archive using Vim's built-in package feature, it may be\r\nconvenient to run the following commands using copy and paste from the downloaded location.\r\n\r\n(Linux, Mac)\r\n PLUG=\"$HOME\/.vim\/pack\/azabiong\/start\"\r\n mkdir -p \"$PLUG\"\r\n unzip -o -d \"$PLUG\" vim-board.zip\r\n vim -u NONE -c \"helptags $PLUG\/vim-board\/doc\" -c q\r\n\r\n(Windows)\r\n cmd.exe\r\n set PLUG=\"%USERPROFILE%\/vimfiles\/pack\/azabiong\/start\"\r\n mkdir %PLUG%\r\n unzip -o -d %PLUG% vim-board.zip\r\n vim -u NONE -c \"helptags %PLUG%\/vim-board\/doc\" -c q\r\n\r\n","first_name":"Azabiong","6":"Azabiong","last_name":" ","7":" ","releases":[{"0":"6008","vim_version":"8.2","1":"8.2","script_version":"1.25.3","2":"1.25.3","version_comment":"Update basic samples\r\n ","3":"Update basic samples\r\n ","package":"vim-board.zip","4":"vim-board.zip","src_id":"28573","5":"28573","creation_date":"1699074715","6":"1699074715"},{"0":"6008","vim_version":"8.2","1":"8.2","script_version":"1.25.2","2":"1.25.2","version_comment":"Support filetype plugin \r\nImprove optional menu keys","3":"Support filetype plugin \r\nImprove optional menu keys","package":"vim-board.zip","4":"vim-board.zip","src_id":"28570","5":"28570","creation_date":"1698490349","6":"1698490349"},{"0":"6008","vim_version":"8.2","1":"8.2","script_version":"1.16","2":"1.16","version_comment":"Add default color set \r\n dark, light","3":"Add default color set \r\n dark, light","package":"vim-board.zip","4":"vim-board.zip","src_id":"28328","5":"28328","creation_date":"1671921862","6":"1671921862"},{"0":"6008","vim_version":"8.2","1":"8.2","script_version":"1.12","2":"1.12","version_comment":"Add syntax type '?!' \r\nSupport inline comment","3":"Add syntax type '?!' \r\nSupport inline comment","package":"vim-board.zip","4":"vim-board.zip","src_id":"28324","5":"28324","creation_date":"1671671305","6":"1671671305"},{"0":"6008","vim_version":"8.2","1":"8.2","script_version":"1.06","2":"1.06","version_comment":"Add sync terminal current working directory\r\n :h BoardTermCd","3":"Add sync terminal current working directory\r\n :h BoardTermCd","package":"vim-board.zip","4":"vim-board.zip","src_id":"27982","5":"27982","creation_date":"1649355867","6":"1649355867"},{"0":"6008","vim_version":"8.2","1":"8.2","script_version":"1.0","2":"1.0","version_comment":"Version 1.0","3":"Version 1.0","package":"vim-board.zip","4":"vim-board.zip","src_id":"27975","5":"27975","creation_date":"1649010131","6":"1649010131"}]},"6006":{"script_id":"6006","0":"6006","script_name":"Tumnus","1":"Tumnus","script_type":"color scheme","2":"color scheme","summary":"Vim colors approved by Mr. Tumnus","3":"Vim colors approved by Mr. Tumnus","description":"A wintery color palette inspired partly by Nord and partly by my own experimenting. Who's the most wintery figure of all (besides Santa)? Well, Mr. Tumnus, of course!","4":"A wintery color palette inspired partly by Nord and partly by my own experimenting. Who's the most wintery figure of all (besides Santa)? Well, Mr. Tumnus, of course!","install_details":"Download, unzip, copy-and-paste the file tumnus.vim into your vim colors directory (~\/.vim\/colors\/). Then add `colorscheme tumnus` to your .vimrc file.","5":"Download, unzip, copy-and-paste the file tumnus.vim into your vim colors directory (~\/.vim\/colors\/). Then add `colorscheme tumnus` to your .vimrc file.","first_name":"Taylor","6":"Taylor","last_name":"Gamache","7":"Gamache","releases":[{"0":"6006","vim_version":"7.0","1":"7.0","script_version":"0.2","2":"0.2","version_comment":"add background color support for gui vim","3":"add background color support for gui vim","package":"tumnus.vim","4":"tumnus.vim","src_id":"27963","5":"27963","creation_date":"1646782235","6":"1646782235"},{"0":"6006","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"tumnus.vim","4":"tumnus.vim","src_id":"27959","5":"27959","creation_date":"1646630236","6":"1646630236"}]},"6005":{"script_id":"6005","0":"6005","script_name":"auto-marks","1":"auto-marks","script_type":"ftplugin","2":"ftplugin","summary":"auto set a mark to A-Z.","3":"auto set a mark to A-Z.","description":"auto-marks is a mark generator, which auto set a mark to {A-Z}.\r\n\r\n:AutoMark auto set a mark to {A-Z}.\r\n\r\n:Marks list all the current marks of {A-Z}.\r\n\r\n:DelMarks delete all marks of {A-Z}.","4":"auto-marks is a mark generator, which auto set a mark to {A-Z}.\r\n\r\n:AutoMark auto set a mark to {A-Z}.\r\n\r\n:Marks list all the current marks of {A-Z}.\r\n\r\n:DelMarks delete all marks of {A-Z}.","install_details":"Just decompressing the auto-marks.zip and put auto-marks directory in your .vim directory, such as run the command \"mv auto-marks ~\/.vim\" on your terminal. And update the runtimepath with .vim\/auto-marks path.\r\nFor example, in your vimrc: set rtp+=~\/.vim\/auto-marks\r\n\r\nFor installing and managing your vim plugins easily, i recommand you to use vim-plug, which is a minimalist Vim Plugin Manager.\r\nIf you use Plug to install , just add \"Plug 'codcodog\/auto-marks'\" , and run ':PlugInstall'.\r\n\r\nFor more information you can see https:\/\/github.com\/codcodog\/auto-marks.","5":"Just decompressing the auto-marks.zip and put auto-marks directory in your .vim directory, such as run the command \"mv auto-marks ~\/.vim\" on your terminal. And update the runtimepath with .vim\/auto-marks path.\r\nFor example, in your vimrc: set rtp+=~\/.vim\/auto-marks\r\n\r\nFor installing and managing your vim plugins easily, i recommand you to use vim-plug, which is a minimalist Vim Plugin Manager.\r\nIf you use Plug to install , just add \"Plug 'codcodog\/auto-marks'\" , and run ':PlugInstall'.\r\n\r\nFor more information you can see https:\/\/github.com\/codcodog\/auto-marks.","first_name":"Cryven","6":"Cryven","last_name":"mo","7":"mo","releases":[{"0":"6005","vim_version":"7.0","1":"7.0","script_version":"1.0.0","2":"1.0.0","version_comment":"Initial upload","3":"Initial upload","package":"auto-marks.zip","4":"auto-marks.zip","src_id":"27952","5":"27952","creation_date":"1645291670","6":"1645291670"}]},"6004":{"script_id":"6004","0":"6004","script_name":"extend_line","1":"extend_line","script_type":"utility","2":"utility","summary":"extend_list: add new elements to existing lists","3":"extend_list: add new elements to existing lists","description":"This plugin will find the most recent list, and add a new element to it.\r\nIndentation and whitespace will be maintained, and the element number will be\r\nincremented.\r\n\r\nThis plugin displays three distinct behaviors:\r\n\r\n- If this is called within a list, a new element will be placed immediately\r\n following the existing list.\r\n- If this is called on a blank line below a list, the new element will be placed\r\n on the current line.\r\n- If there is no list, a new list will be started using the default.\r\n\r\nOriginal plugin by Matt.\r\n\r\nMaintained by Michael Henry (vim at drmikehenry.com).\r\n\r\nDistributed under Vim's license.\r\n\r\nGit repository: https:\/\/github.com\/drmikehenry\/vim-extend_list\r\n","4":"This plugin will find the most recent list, and add a new element to it.\r\nIndentation and whitespace will be maintained, and the element number will be\r\nincremented.\r\n\r\nThis plugin displays three distinct behaviors:\r\n\r\n- If this is called within a list, a new element will be placed immediately\r\n following the existing list.\r\n- If this is called on a blank line below a list, the new element will be placed\r\n on the current line.\r\n- If there is no list, a new list will be started using the default.\r\n\r\nOriginal plugin by Matt.\r\n\r\nMaintained by Michael Henry (vim at drmikehenry.com).\r\n\r\nDistributed under Vim's license.\r\n\r\nGit repository: https:\/\/github.com\/drmikehenry\/vim-extend_list\r\n","install_details":"To install this plugin with Pathogen, you should clone this repository into your\r\nbundle directory.\r\n\r\nAfter generating the help tags (using `:Helptags`), the detailed documentation\r\ncan be found at `:help extend_list`.\r\n","5":"To install this plugin with Pathogen, you should clone this repository into your\r\nbundle directory.\r\n\r\nAfter generating the help tags (using `:Helptags`), the detailed documentation\r\ncan be found at `:help extend_list`.\r\n","first_name":"Michael","6":"Michael","last_name":"Henry","7":"Henry","releases":[{"0":"6004","vim_version":"7.0","1":"7.0","script_version":"0.1.0","2":"0.1.0","version_comment":"Initial upload","3":"Initial upload","package":"extend_list-0.1.0.zip","4":"extend_list-0.1.0.zip","src_id":"27949","5":"27949","creation_date":"1645167204","6":"1645167204"}]},"6003":{"script_id":"6003","0":"6003","script_name":"pr0kter.vim","1":"pr0kter.vim","script_type":"color scheme","2":"color scheme","summary":"Vim colorscheme (a clear one)","3":"Vim colorscheme (a clear one)","description":" Vim color file\r\n pr0kter v0.6\r\n https:\/\/github.com\/pedromg\/vim_pr0kter\r\n \r\n Maintainer: Pedro Mota \r\n\r\n * Place :colo pr0kter in your VimRC\/GVimRC file\r\n * GvimRC if using GUI any\r\n\r\n - I\\'m using this mostly with MacVim on Mac OSX (please report issues on github)\r\n - This is a version of bayQua (which is derived from baycomb)\r\n - Thanks to RShawn Axsom for his bayQua","4":" Vim color file\r\n pr0kter v0.6\r\n https:\/\/github.com\/pedromg\/vim_pr0kter\r\n \r\n Maintainer: Pedro Mota \r\n\r\n * Place :colo pr0kter in your VimRC\/GVimRC file\r\n * GvimRC if using GUI any\r\n\r\n - I\\'m using this mostly with MacVim on Mac OSX (please report issues on github)\r\n - This is a version of bayQua (which is derived from baycomb)\r\n - Thanks to RShawn Axsom for his bayQua","install_details":"Copy the script to your .vim\/colors folder and add the following to your .vimrc (or .gvimrc):\r\n\r\ncolorscheme pr0kter","5":"Copy the script to your .vim\/colors folder and add the following to your .vimrc (or .gvimrc):\r\n\r\ncolorscheme pr0kter","first_name":"pedro","6":"pedro","last_name":"mg","7":"mg","releases":[{"0":"6003","vim_version":"7.0","1":"7.0","script_version":"0.6","2":"0.6","version_comment":"Initial upload","3":"Initial upload","package":"pr0kter.vim","4":"pr0kter.vim","src_id":"27943","5":"27943","creation_date":"1644356047","6":"1644356047"}]},"6002":{"script_id":"6002","0":"6002","script_name":"clrzr","1":"clrzr","script_type":"syntax","2":"syntax","summary":"Color highlighting for Hex & CSS color representations","3":"Color highlighting for Hex & CSS color representations","description":"Highly efficient, on-the-fly, color highlighting for Hex & CSS color representations. (requires AWK, any version will do)\r\n\r\nSource available at: https:\/\/github.com\/BourgeoisBear\/clrzr","4":"Highly efficient, on-the-fly, color highlighting for Hex & CSS color representations. (requires AWK, any version will do)\r\n\r\nSource available at: https:\/\/github.com\/BourgeoisBear\/clrzr","install_details":"Extract package folder to ~\/.vim\/pack\/plugins\/start and restart Vim.","5":"Extract package folder to ~\/.vim\/pack\/plugins\/start and restart Vim.","first_name":"Jason","6":"Jason","last_name":"Stewart","7":"Stewart","releases":[{"0":"6002","vim_version":"8.2","1":"8.2","script_version":"1.8.2","2":"1.8.2","version_comment":"Initial upload","3":"Initial upload","package":"clrzr-1.8.2.zip","4":"clrzr-1.8.2.zip","src_id":"27927","5":"27927","creation_date":"1643190919","6":"1643190919"}]},"6001":{"script_id":"6001","0":"6001","script_name":"vim-rsvp","1":"vim-rsvp","script_type":"utility","2":"utility","summary":"rapid serial visual presentation speed-reader","3":"rapid serial visual presentation speed-reader","description":"Load a text into a buffer. Place the cursor where you'd like to begin reading. Issue a simple :RsvpGo command, and you're off!\r\n\r\nContext-sensitive controls are displayed in the message bar.\r\n\r\nSource code available here: https:\/\/github.com\/BourgeoisBear\/vim-rsvp","4":"Load a text into a buffer. Place the cursor where you'd like to begin reading. Issue a simple :RsvpGo command, and you're off!\r\n\r\nContext-sensitive controls are displayed in the message bar.\r\n\r\nSource code available here: https:\/\/github.com\/BourgeoisBear\/vim-rsvp","install_details":"download the archive, unzip to ~\/.vim\/pack\/plugins\/start, and restart","5":"download the archive, unzip to ~\/.vim\/pack\/plugins\/start, and restart","first_name":"Jason","6":"Jason","last_name":"Stewart","7":"Stewart","releases":[{"0":"6001","vim_version":"8.2","1":"8.2","script_version":"1.0b","2":"1.0b","version_comment":"Initial upload","3":"Initial upload","package":"vim-rsvp-1.0b.zip","4":"vim-rsvp-1.0b.zip","src_id":"27926","5":"27926","creation_date":"1643190526","6":"1643190526"}]},"6000":{"script_id":"6000","0":"6000","script_name":"vim_hdl_trace","1":"vim_hdl_trace","script_type":"utility","2":"utility","summary":" similar verdi trace connect.","3":" similar verdi trace connect.","description":"if use gvim write verilog and systemverilog code. this vim plugin help you. It\\\\\\\\\\\\\\'s similar verdi trace connect.","4":"if use gvim write verilog and systemverilog code. this vim plugin help you. It\\\\\\\\\\\\\\'s similar verdi trace connect.","install_details":"vim_hdl_trace\r\nif use gvim write verilog and systemverilog code. this vim plugin help you. It\\\\\\\\\\\\\\'s similar verdi trace connect.\r\n\r\nadd hotkey open ~\/.vimrc file, in this file. add this txts : \\\\\\\\\\\\\\\"nmap fc :call Trace_c()\\\\\\\\\\\\\\\"\r\nit\\\\\\\\\\\\\\'s set \\\\\\\\\\\\\\'fc\\\\\\\\\\\\\\' hotkey.\r\n\r\nsave file save Trace_c.vim to ~\/.vim\/plugin\r\n\r\nuse it. move on any word , push hotkey \\\\\\\\\\\\\\'fc\\\\\\\\\\\\\\' , next display this word of any quto.","5":"vim_hdl_trace\r\nif use gvim write verilog and systemverilog code. this vim plugin help you. It\\\\\\\\\\\\\\'s similar verdi trace connect.\r\n\r\nadd hotkey open ~\/.vimrc file, in this file. add this txts : \\\\\\\\\\\\\\\"nmap fc :call Trace_c()\\\\\\\\\\\\\\\"\r\nit\\\\\\\\\\\\\\'s set \\\\\\\\\\\\\\'fc\\\\\\\\\\\\\\' hotkey.\r\n\r\nsave file save Trace_c.vim to ~\/.vim\/plugin\r\n\r\nuse it. move on any word , push hotkey \\\\\\\\\\\\\\'fc\\\\\\\\\\\\\\' , next display this word of any quto.","first_name":"hank","6":"hank","last_name":"yuan","7":"yuan","releases":[{"0":"6000","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"Trace_c.vim","4":"Trace_c.vim","src_id":"27925","5":"27925","creation_date":"1643126003","6":"1643126003"}]},"5999":{"script_id":"5999","0":"5999","script_name":"nginx_conf_syntax_highlighting","1":"nginx_conf_syntax_highlighting","script_type":"syntax","2":"syntax","summary":"Syntax Highlighting for NGINX Conf Files","3":"Syntax Highlighting for NGINX Conf Files","description":"Syntax Highlighting for NGINX Files.\r\nInitial source: http:\/\/www.vim.org\/scripts\/download_script.php?src_id=19394\r\n\r\nI just added 'least_conn' keyword to it.\r\n\r\n\r\ngist: https:\/\/gist.github.com\/majidalaeinia\/fd79282367ed26e4e291bb0a29ecfcf4","4":"Syntax Highlighting for NGINX Files.\r\nInitial source: http:\/\/www.vim.org\/scripts\/download_script.php?src_id=19394\r\n\r\nI just added 'least_conn' keyword to it.\r\n\r\n\r\ngist: https:\/\/gist.github.com\/majidalaeinia\/fd79282367ed26e4e291bb0a29ecfcf4","install_details":"mkdir -p ~\/.vim\/syntax\/\r\nwget https:\/\/www.vim.org\/scripts\/download_script.php?src_id=27919 -O ~\/.vim\/syntax\/nginx.vim\r\n\r\ncat > ~\/.vim\/filetype.vim < ~\/.vim\/filetype.vim < vim9","1":"vim8 > vim9","script_type":"utility","2":"utility","summary":"Be happy with vim8!","3":"Be happy with vim8!","description":"With vim9 is on the horizon and rational has been augmented for making such\r\nlinguistic changes. However, vim8 has the full potential of becoming pure\r\nobject-oriented language and provides the ability of crafting your own domain\r\nspecific programming language as well. Combining with all the latest offers\r\nfrom vim8 is a blessing to apply design patterns and other OO techniques in\r\nyour program, which have much more than vim9 and other scripting languages\r\nhave to offer.\r\n\r\nThis package serves as a practical framework for doing object-oriented in vim8\r\nwithout the hassle of learning vim9 syntax, which puts a lot of burden on\r\ndevelopers. Just use the existing vim8 alone, we can easily add more cool\r\nfeatures that are existing other programming languages.\r\n\r\nThe main script ObjectBuilder.vim is less than 150 lines! Nevertheless, it\r\nsupports class declaration, method override, etc, most of the familiar\r\nobject-oriented features, even including multiple inheritance.\r\n\r\nThis is not a revolution against vim like Neovim, but a religious practice of\r\nembracing vim8. There are already suggestions of porting vim8 scripts to\r\nvim9, I'm strongly against that, because there's no real benefit and\r\njustification to it. Rather than wasting time learning an ego-driven and\r\nmeritless language, just live with vim8 and be happy!\r\n","4":"With vim9 is on the horizon and rational has been augmented for making such\r\nlinguistic changes. However, vim8 has the full potential of becoming pure\r\nobject-oriented language and provides the ability of crafting your own domain\r\nspecific programming language as well. Combining with all the latest offers\r\nfrom vim8 is a blessing to apply design patterns and other OO techniques in\r\nyour program, which have much more than vim9 and other scripting languages\r\nhave to offer.\r\n\r\nThis package serves as a practical framework for doing object-oriented in vim8\r\nwithout the hassle of learning vim9 syntax, which puts a lot of burden on\r\ndevelopers. Just use the existing vim8 alone, we can easily add more cool\r\nfeatures that are existing other programming languages.\r\n\r\nThe main script ObjectBuilder.vim is less than 150 lines! Nevertheless, it\r\nsupports class declaration, method override, etc, most of the familiar\r\nobject-oriented features, even including multiple inheritance.\r\n\r\nThis is not a revolution against vim like Neovim, but a religious practice of\r\nembracing vim8. There are already suggestions of porting vim8 scripts to\r\nvim9, I'm strongly against that, because there's no real benefit and\r\njustification to it. Rather than wasting time learning an ego-driven and\r\nmeritless language, just live with vim8 and be happy!\r\n","install_details":"Untar the tar ball and source Bit.vim to run the example. If your want to use the framework, just source ObjectBuilder.vim in your script.","5":"Untar the tar ball and source Bit.vim to run the example. If your want to use the framework, just source ObjectBuilder.vim in your script.","first_name":"Yiu","6":"Yiu","last_name":"Wing","7":"Wing","releases":[{"0":"5997","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"JustVim8.tar.gz","4":"JustVim8.tar.gz","src_id":"27895","5":"27895","creation_date":"1641755596","6":"1641755596"}]},"5996":{"script_id":"5996","0":"5996","script_name":"ColorScheme2CSS","1":"ColorScheme2CSS","script_type":"utility","2":"utility","summary":"Converter Vim colorschemes in CSS files","3":"Converter Vim colorschemes in CSS files","description":"Оговорка по тексту:\r\nThis is a machine translation of the Яandex service. I apologize for possible mistakes.\r\nДля тех, кто думает по‐русски (говорит и пишет) ниже по тексту есть описание.\r\n\r\nThis plugin is designed to convert the current color scheme of the program Vim editor into a ready-made Cascading Style Sheets (CSS) file. The CSS files prepared by this plugin meet the requirements CSS Validation Service (https:\/\/jigsaw.w3.org\/css-validator\/) and can be used to connect to an HTML or XHTML document (web page).\r\n\r\nThe plugin can be used both for converting only the current color scheme, and for batch processing of several files of color schemes of the Vim editor.\r\n\r\nWhen converting a color scheme, you can set the desired background \u00e2\u0080\u0094 dark or light. It is also possible to specify the directory where the finished CSS files will be written.\r\n\r\nThis plugin requires a program Vim version 8.2 or newer to work. To convert color schemes, a variant of the program with support for a graphical user interface (GUI) is used.\r\n\r\nDisclaimer on the text:\r\nThe English text is located above the text\r\n\r\nДанный подключаемый модуль предназначен для преобразования текущей цветовой схемы программы \u00c2\u00abРедактор Vim\u00c2\u00bb в готовый файл \u00c2\u00abкаскадной таблицы стилей\u00c2\u00bb (Cascading Style Sheets, CSS). Файлы CSS, подготовленные этим подключаемым модулем, соответствуют требованиям CSS Validation Service (https:\/\/jigsaw.w3.org\/css-validator\/) и могут быть использованы для подключения к документу (веб‐странице) HTML или XHTML.\r\n\r\nПодключаемый модуль может быть использован как для преобразования только текущей цветовой схемы, так и для пакетной обработки нескольких файлов цветовых схем редактора Vim.\r\n\r\nПри конвертации цветовой схемы можно задать требуемый фон \u00e2\u0080\u0094 тёмный или светлый (dark or light). Также возможно указать каталог, куда будут записаны готовые файлы CSS.\r\n\r\nДля работы этого подключаемого модуля требуется программа Vim версии 8.2 или старше. Для преобразования цветовых схем используется вариант программы с поддержкой графического интерфейса пользователя (ГИП, graphical user interface, GUI).\r\n","4":"Оговорка по тексту:\r\nThis is a machine translation of the Яandex service. I apologize for possible mistakes.\r\nДля тех, кто думает по‐русски (говорит и пишет) ниже по тексту есть описание.\r\n\r\nThis plugin is designed to convert the current color scheme of the program Vim editor into a ready-made Cascading Style Sheets (CSS) file. The CSS files prepared by this plugin meet the requirements CSS Validation Service (https:\/\/jigsaw.w3.org\/css-validator\/) and can be used to connect to an HTML or XHTML document (web page).\r\n\r\nThe plugin can be used both for converting only the current color scheme, and for batch processing of several files of color schemes of the Vim editor.\r\n\r\nWhen converting a color scheme, you can set the desired background \u00e2\u0080\u0094 dark or light. It is also possible to specify the directory where the finished CSS files will be written.\r\n\r\nThis plugin requires a program Vim version 8.2 or newer to work. To convert color schemes, a variant of the program with support for a graphical user interface (GUI) is used.\r\n\r\nDisclaimer on the text:\r\nThe English text is located above the text\r\n\r\nДанный подключаемый модуль предназначен для преобразования текущей цветовой схемы программы \u00c2\u00abРедактор Vim\u00c2\u00bb в готовый файл \u00c2\u00abкаскадной таблицы стилей\u00c2\u00bb (Cascading Style Sheets, CSS). Файлы CSS, подготовленные этим подключаемым модулем, соответствуют требованиям CSS Validation Service (https:\/\/jigsaw.w3.org\/css-validator\/) и могут быть использованы для подключения к документу (веб‐странице) HTML или XHTML.\r\n\r\nПодключаемый модуль может быть использован как для преобразования только текущей цветовой схемы, так и для пакетной обработки нескольких файлов цветовых схем редактора Vim.\r\n\r\nПри конвертации цветовой схемы можно задать требуемый фон \u00e2\u0080\u0094 тёмный или светлый (dark or light). Также возможно указать каталог, куда будут записаны готовые файлы CSS.\r\n\r\nДля работы этого подключаемого модуля требуется программа Vim версии 8.2 или старше. Для преобразования цветовых схем используется вариант программы с поддержкой графического интерфейса пользователя (ГИП, graphical user interface, GUI).\r\n","install_details":"https:\/\/github.com\/RestorerZ\/Colo2CSS","5":"https:\/\/github.com\/RestorerZ\/Colo2CSS","first_name":"","6":"","last_name":"","7":"","releases":[{"0":"5996","vim_version":"8.2","1":"8.2","script_version":"1.9.3","2":"1.9.3","version_comment":"In X11, when batch processing color schemes, gvim works collapsed into an icon.\r\nFixed bugs.\r\nA little code optimization.","3":"In X11, when batch processing color schemes, gvim works collapsed into an icon.\r\nFixed bugs.\r\nA little code optimization.","package":"colo2css_v193.vmb.zip","4":"colo2css_v193.vmb.zip","src_id":"27932","5":"27932","creation_date":"1643489454","6":"1643489454"},{"0":"5996","vim_version":"8.2","1":"8.2","script_version":"1.8.29","2":"1.8.29","version_comment":"Bug fixed, minor optimization","3":"Bug fixed, minor optimization","package":"colo2css_v1829.vmb.zip","4":"colo2css_v1829.vmb.zip","src_id":"27906","5":"27906","creation_date":"1642285530","6":"1642285530"},{"0":"5996","vim_version":"8.2","1":"8.2","script_version":"1.8.15","2":"1.8.15","version_comment":"small code optimization (refactoring)","3":"small code optimization (refactoring)","package":"colo2css_v1815.vmb.zip","4":"colo2css_v1815.vmb.zip","src_id":"27896","5":"27896","creation_date":"1641757515","6":"1641757515"},{"0":"5996","vim_version":"8.2","1":"8.2","script_version":"1.8.12","2":"1.8.12","version_comment":"Initial upload","3":"Initial upload","package":"colo2css_v1812.vmb.zip","4":"colo2css_v1812.vmb.zip","src_id":"27894","5":"27894","creation_date":"1641682511","6":"1641682511"}]},"5995":{"script_id":"5995","0":"5995","script_name":"vim-slime-cells","1":"vim-slime-cells","script_type":"utility","2":"utility","summary":"A plugin on top of vim-slime to enhance its cell feature. ","3":"A plugin on top of vim-slime to enhance its cell feature. ","description":"A plugin on top of vim-slime (https:\/\/github.com\/jpalardy\/vim-slime) to enhance its cell feature. It adds the possibility to jump between cells and to send the current cell then jump to the next one.\r\n\r\nThere is also a nice syntax-highlighting feature for cell boundaries.\r\n\r\nA screencast is available here : https:\/\/asciinema.org\/a\/459056 .\r\n\r\nPlease, see the Readme file ( https:\/\/github.com\/Klafyvel\/vim-slime-cells ) or read the documentation of the plugin for further information on how to use and configure the plugin.","4":"A plugin on top of vim-slime (https:\/\/github.com\/jpalardy\/vim-slime) to enhance its cell feature. It adds the possibility to jump between cells and to send the current cell then jump to the next one.\r\n\r\nThere is also a nice syntax-highlighting feature for cell boundaries.\r\n\r\nA screencast is available here : https:\/\/asciinema.org\/a\/459056 .\r\n\r\nPlease, see the Readme file ( https:\/\/github.com\/Klafyvel\/vim-slime-cells ) or read the documentation of the plugin for further information on how to use and configure the plugin.","install_details":"You need vim-slime (https:\/\/github.com\/jpalardy\/vim-slime) installed.\r\n\r\nYou can use Vim-Plug:\r\n```vim\r\nPlug 'klafyvel\/vim-slime-cells'\r\n```\r\n","5":"You need vim-slime (https:\/\/github.com\/jpalardy\/vim-slime) installed.\r\n\r\nYou can use Vim-Plug:\r\n```vim\r\nPlug 'klafyvel\/vim-slime-cells'\r\n```\r\n","first_name":"Hugo","6":"Hugo","last_name":"Levy-Falk","7":"Levy-Falk","releases":[{"0":"5995","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"vim-slime-cells.tar.gz","4":"vim-slime-cells.tar.gz","src_id":"27890","5":"27890","creation_date":"1641405428","6":"1641405428"}]},"5994":{"script_id":"5994","0":"5994","script_name":"replacer.vim","1":"replacer.vim","script_type":"utility","2":"utility","summary":"Find and replace in vim","3":"Find and replace in vim","description":"This vim plugin can be used to find and replace terms across multiple files and subdirectories in a folder. Renaming multiple files at once is also possible with this plugin. While other packages that perform similar tasks exist, I've found that they don't always perform well on slower machines. This plugin works well on systems that can run simple shell commands.\r\n\r\nLatest version is on github - https:\/\/github.com\/kohrVid\/replacer.vim","4":"This vim plugin can be used to find and replace terms across multiple files and subdirectories in a folder. Renaming multiple files at once is also possible with this plugin. While other packages that perform similar tasks exist, I've found that they don't always perform well on slower machines. This plugin works well on systems that can run simple shell commands.\r\n\r\nLatest version is on github - https:\/\/github.com\/kohrVid\/replacer.vim","install_details":"The use of a plugin manager is advised and instructions on how to install this with pathogen and vim-plug can be found here - https:\/\/github.com\/kohrVid\/replacer.vim#installation\r\n\r\nHowever, it is also possible to install this plugin by extracting it in the ~\/.vim directory. This will save the scripts in ~\/.vim\/plugin and the documentation in ~\/.vim\/doc.","5":"The use of a plugin manager is advised and instructions on how to install this with pathogen and vim-plug can be found here - https:\/\/github.com\/kohrVid\/replacer.vim#installation\r\n\r\nHowever, it is also possible to install this plugin by extracting it in the ~\/.vim directory. This will save the scripts in ~\/.vim\/plugin and the documentation in ~\/.vim\/doc.","first_name":"Jessica","6":"Jessica","last_name":"\u00c3\u0089t\u00c3\u00a9","7":"\u00c3\u0089t\u00c3\u00a9","releases":[{"0":"5994","vim_version":"7.0","1":"7.0","script_version":"1.0.0","2":"1.0.0","version_comment":"Initial upload","3":"Initial upload","package":"replacer.vim.zip","4":"replacer.vim.zip","src_id":"27884","5":"27884","creation_date":"1641161855","6":"1641161855"}]},"5993":{"script_id":"5993","0":"5993","script_name":"ag-search","1":"ag-search","script_type":"utility","2":"utility","summary":"search with ag\/grep in background, save\/load searches on quickfix","3":"search with ag\/grep in background, save\/load searches on quickfix","description":"ag-search allows you to launch ag (silver searcher) or grep commands in background and display the results on quickfix window.\r\n\r\nLaunch :Agh for abridged help and examples.\r\n\r\nag-search is a plugin to:\r\n- Launch a search in background (Ags path pattern [options]).\r\n- Concatenate searches (:Ags pattern1,pattern2,pattern3 path [options]).\r\n- Concatenate searches. Remove not matching pattern2 (:Ags pattern1,-pattern2 path [options]).\r\n- Launch again a previous search (:AgS)\r\n- Save\/load\/open\/delete saved search results (:Agsv, :Agl, :Agd, :AgD, :Ago).\r\n- Automatically save last N searches performed.\r\n- Retrieve search information of the last searches performed (:Agi, :Agic).\r\n- Create custom mappings and abbreviations to launch user searches more easily.\r\n- Force search with context (:Agc, :Agc 4, :Agc 2 4).\r\n- Fold\/unfold the context on the quickfix window (:Agf)\r\n\r\nThis plugin uses jobs.vim to launch the search in backgraund.\r\nUse command :Jobsl to show information about your searches running in backgraund.\r\nUse command :Jobsk to kill any searche running in backgraund.\r\n\r\nDefault mappings:\r\nf : search word under cursor (or visual selection) in current buffer.\r\nd : search word under cursor (or visual selection) in current buffer file's directory.\r\np : search word under cursor (or visual selection) in current buffer file's parent directory.\r\nw : search word under cursor (or visual selection) in working directory.\r\n\r\nDefault abbreviations:\r\n_agf : search in current buffer.\r\n_agd : search in current buffer's directory.\r\n_agp : search in current buffer's previous directory.\r\n_agw : search in working directory.\r\n\r\nThe doc page is still pending meanwhile you can check :Agh for an abridged command help and examples:\r\n\r\nAny feedback will be welcome.\r\n\r\nAgs command options:\r\n-ID=path1,path2 : ignore (comma separed) directories.\r\n-IF=pattern1,pattern2 : ignore (comma separed) patterns.\r\n-RP=pattern : ask user to replace on the provided path any words on g:AgSearch_defaultReplacePatterns (Defaults: _DIR_, _DIR1_, _DIR2..., _FILE_).\r\n\r\n\r\nADVANCED:\r\nCustomizations you can add to your .vimrc file.\r\n\r\n\" Fold\/unfold the context on quickfix window:\r\nnnoremap f :Agf\r\n\r\nCreate mapping to search on a folder projects, ask user to replace _DIR_ with the directory name or use wildcard * to search all directories:\r\nnnoremap as :Ags \/home\/jp\/projects\/_DIR_\/source\/ =\"-s \".expand('')\r\n\r\nCreate command :Agss, map as and abbreviation _ags to search on directory sources, inside directory projets, and ask user to replace _DIR_ with a directory name (project name) or wildcard (like: *) to search all directories (projects):\r\n\" Remove previous user commands:\r\ncall agsearch#AddUserCmdMapAbbrev( { 'reset':1 } )\r\n\" Add new user commands:\r\ncall agsearch#AddUserCmdMapAbbrev( { 'default':\"s\", 'path':'\/home\/jp\/projects\/_DIR_\/source\/', 'help':\"Search source dir on projects\" } )\r\ncall agsearch#AddUserCmdMapAbbrev( { 'default':\"c\", 'path':'.\/home\/jp\/config\/myconfig\/', 'help':\"Search config dir\" } )\r\n\r\n","4":"ag-search allows you to launch ag (silver searcher) or grep commands in background and display the results on quickfix window.\r\n\r\nLaunch :Agh for abridged help and examples.\r\n\r\nag-search is a plugin to:\r\n- Launch a search in background (Ags path pattern [options]).\r\n- Concatenate searches (:Ags pattern1,pattern2,pattern3 path [options]).\r\n- Concatenate searches. Remove not matching pattern2 (:Ags pattern1,-pattern2 path [options]).\r\n- Launch again a previous search (:AgS)\r\n- Save\/load\/open\/delete saved search results (:Agsv, :Agl, :Agd, :AgD, :Ago).\r\n- Automatically save last N searches performed.\r\n- Retrieve search information of the last searches performed (:Agi, :Agic).\r\n- Create custom mappings and abbreviations to launch user searches more easily.\r\n- Force search with context (:Agc, :Agc 4, :Agc 2 4).\r\n- Fold\/unfold the context on the quickfix window (:Agf)\r\n\r\nThis plugin uses jobs.vim to launch the search in backgraund.\r\nUse command :Jobsl to show information about your searches running in backgraund.\r\nUse command :Jobsk to kill any searche running in backgraund.\r\n\r\nDefault mappings:\r\nf : search word under cursor (or visual selection) in current buffer.\r\nd : search word under cursor (or visual selection) in current buffer file's directory.\r\np : search word under cursor (or visual selection) in current buffer file's parent directory.\r\nw : search word under cursor (or visual selection) in working directory.\r\n\r\nDefault abbreviations:\r\n_agf : search in current buffer.\r\n_agd : search in current buffer's directory.\r\n_agp : search in current buffer's previous directory.\r\n_agw : search in working directory.\r\n\r\nThe doc page is still pending meanwhile you can check :Agh for an abridged command help and examples:\r\n\r\nAny feedback will be welcome.\r\n\r\nAgs command options:\r\n-ID=path1,path2 : ignore (comma separed) directories.\r\n-IF=pattern1,pattern2 : ignore (comma separed) patterns.\r\n-RP=pattern : ask user to replace on the provided path any words on g:AgSearch_defaultReplacePatterns (Defaults: _DIR_, _DIR1_, _DIR2..., _FILE_).\r\n\r\n\r\nADVANCED:\r\nCustomizations you can add to your .vimrc file.\r\n\r\n\" Fold\/unfold the context on quickfix window:\r\nnnoremap f :Agf\r\n\r\nCreate mapping to search on a folder projects, ask user to replace _DIR_ with the directory name or use wildcard * to search all directories:\r\nnnoremap as :Ags \/home\/jp\/projects\/_DIR_\/source\/ =\"-s \".expand('')\r\n\r\nCreate command :Agss, map as and abbreviation _ags to search on directory sources, inside directory projets, and ask user to replace _DIR_ with a directory name (project name) or wildcard (like: *) to search all directories (projects):\r\n\" Remove previous user commands:\r\ncall agsearch#AddUserCmdMapAbbrev( { 'reset':1 } )\r\n\" Add new user commands:\r\ncall agsearch#AddUserCmdMapAbbrev( { 'default':\"s\", 'path':'\/home\/jp\/projects\/_DIR_\/source\/', 'help':\"Search source dir on projects\" } )\r\ncall agsearch#AddUserCmdMapAbbrev( { 'default':\"c\", 'path':'.\/home\/jp\/config\/myconfig\/', 'help':\"Search config dir\" } )\r\n\r\n","install_details":"Minimum version: Vim 7.0+\r\nRecomended version: Vim 8.0+\r\n\r\nInstall vimball:\r\ndownload agsearch_0.0.3.vmb\r\nvim agsearch_0.0.3.vmb\r\n:so %\r\n:q ","5":"Minimum version: Vim 7.0+\r\nRecomended version: Vim 8.0+\r\n\r\nInstall vimball:\r\ndownload agsearch_0.0.3.vmb\r\nvim agsearch_0.0.3.vmb\r\n:so %\r\n:q ","first_name":"Javier","6":"Javier","last_name":"Puigdevall","7":"Puigdevall","releases":[{"0":"5993","vim_version":"7.0","1":"7.0","script_version":"0.0.3","2":"0.0.3","version_comment":"- New: use path __FILES__ to search in all files open on current vim session.\r\n Use __FILES:pattern__ to search only files matching pattern.\r\n Use __FILES:--pattern__ to search only files not matching pattern.\r\n- New: AgF command, _agF abbreviation, aF map. to search all files\r\n open on current vim session.\r\n- Remove: Agb command (_agb abbreviation, ab mapping) removed.","3":"- New: use path __FILES__ to search in all files open on current vim session.\r\n Use __FILES:pattern__ to search only files matching pattern.\r\n Use __FILES:--pattern__ to search only files not matching pattern.\r\n- New: AgF command, _agF abbreviation, aF map. to search all files\r\n open on current vim session.\r\n- Remove: Agb command (_agb abbreviation, ab mapping) removed.","package":"agsearch_0.0.3.vmb","4":"agsearch_0.0.3.vmb","src_id":"27930","5":"27930","creation_date":"1643401720","6":"1643401720"},{"0":"5993","vim_version":"7.0","1":"7.0","script_version":"0.0.2","2":"0.0.2","version_comment":"Fix: auto save files rotation. Not deleting old files.","3":"Fix: auto save files rotation. Not deleting old files.","package":"agsearch_0.0.2.vmb","4":"agsearch_0.0.2.vmb","src_id":"27903","5":"27903","creation_date":"1641926738","6":"1641926738"},{"0":"5993","vim_version":"7.0","1":"7.0","script_version":"0.0.1","2":"0.0.1","version_comment":"Initial upload","3":"Initial upload","package":"agsearch_0.0.1.vmb","4":"agsearch_0.0.1.vmb","src_id":"27864","5":"27864","creation_date":"1640285328","6":"1640285328"}]},"5992":{"script_id":"5992","0":"5992","script_name":"tosvg","1":"tosvg","script_type":"utility","2":"utility","summary":"Exports the current buffer as a SVG.","3":"Exports the current buffer as a SVG.","description":"See https:\/\/github.com\/phmarek\/vim-tosvg for details.","4":"See https:\/\/github.com\/phmarek\/vim-tosvg for details.","install_details":"Put script in the autoload\/ directory.","5":"Put script in the autoload\/ directory.","first_name":"Philipp","6":"Philipp","last_name":"Marek","7":"Marek","releases":[{"0":"5992","vim_version":"7.0","1":"7.0","script_version":"20211222","2":"20211222","version_comment":"Fixed loading the plugin -- misunderstood \"autoload\".","3":"Fixed loading the plugin -- misunderstood \"autoload\".","package":"to-svg-2021-12-22.zip","4":"to-svg-2021-12-22.zip","src_id":"27863","5":"27863","creation_date":"1640200331","6":"1640200331"},{"0":"5992","vim_version":"7.0","1":"7.0","script_version":"20211221","2":"20211221","version_comment":"Initial upload","3":"Initial upload","package":"to-svg-2021-12-21.zip","4":"to-svg-2021-12-21.zip","src_id":"27862","5":"27862","creation_date":"1640109875","6":"1640109875"}]},"5991":{"script_id":"5991","0":"5991","script_name":"vim-ivy","1":"vim-ivy","script_type":"syntax","2":"syntax","summary":"Syntax plugin for the IVy language","3":"Syntax plugin for the IVy language","description":"This is a syntax plugin for Microsoft Research's IVy protocol verification language. You can find out more about IVy and its use-cases here: http:\/\/microsoft.github.io\/ivy\/\r\n\r\nThis page contains a tarball derived from the plugin's Git repository: https:\/\/github.com\/dijkstracula\/vim-ivy .","4":"This is a syntax plugin for Microsoft Research's IVy protocol verification language. You can find out more about IVy and its use-cases here: http:\/\/microsoft.github.io\/ivy\/\r\n\r\nThis page contains a tarball derived from the plugin's Git repository: https:\/\/github.com\/dijkstracula\/vim-ivy .","install_details":"Please consult the \"installation\" section of the plugin's README for up-to-date details: https:\/\/github.com\/dijkstracula\/vim-ivy\/blob\/main\/README.md#installation .","5":"Please consult the \"installation\" section of the plugin's README for up-to-date details: https:\/\/github.com\/dijkstracula\/vim-ivy\/blob\/main\/README.md#installation .","first_name":"Nathan","6":"Nathan","last_name":"Taylor","7":"Taylor","releases":[{"0":"5991","vim_version":"7.0","1":"7.0","script_version":"0.0.1","2":"0.0.1","version_comment":"Initial upload","3":"Initial upload","package":"vim-ivy.tar.gz","4":"vim-ivy.tar.gz","src_id":"27861","5":"27861","creation_date":"1640056444","6":"1640056444"}]},"5987":{"script_id":"5987","0":"5987","script_name":"dev-goodies","1":"dev-goodies","script_type":"utility","2":"utility","summary":"useful commands for working with code.","3":"useful commands for working with code.","description":"Vim plugin - useful commands for working with code. Adds the following commands: (See doc file https:\/\/raw.githubusercontent.com\/MoserMichael\/devgoodies\/master\/doc\/devgoodies.txt for more details) Project page: https:\/\/github.com\/MoserMichael\/devgoodies\r\n\r\nAlso, all this goodness is best used in conjunction with the GitBlame plugin (link: https:\/\/github.com\/MoserMichael\/gitblame)\r\n\r\nCommands:\r\n\r\nBuild\/StopBuild\/PrevBuildResults - Asynchronous build commands\r\n\r\nLint - Static analysis of the file that is backing the current buffer. (options for shell, python, perl and go)\r\n\r\nFormat - Pretty print the file that is backing the current buffer (options for python, go, cpp)\r\n\r\nComment\/UnComment - Comment and un-comment a block of code\r\n\r\nMakeTags\/UseTags - building and using tag file (options for c\/c++, java, python, go)\r\n\r\nDoGrep - Running grep from vim, recursively from current directory down.\r\n\r\nRedir - run a command and put output in scratch buffer.\r\n\r\n","4":"Vim plugin - useful commands for working with code. Adds the following commands: (See doc file https:\/\/raw.githubusercontent.com\/MoserMichael\/devgoodies\/master\/doc\/devgoodies.txt for more details) Project page: https:\/\/github.com\/MoserMichael\/devgoodies\r\n\r\nAlso, all this goodness is best used in conjunction with the GitBlame plugin (link: https:\/\/github.com\/MoserMichael\/gitblame)\r\n\r\nCommands:\r\n\r\nBuild\/StopBuild\/PrevBuildResults - Asynchronous build commands\r\n\r\nLint - Static analysis of the file that is backing the current buffer. (options for shell, python, perl and go)\r\n\r\nFormat - Pretty print the file that is backing the current buffer (options for python, go, cpp)\r\n\r\nComment\/UnComment - Comment and un-comment a block of code\r\n\r\nMakeTags\/UseTags - building and using tag file (options for c\/c++, java, python, go)\r\n\r\nDoGrep - Running grep from vim, recursively from current directory down.\r\n\r\nRedir - run a command and put output in scratch buffer.\r\n\r\n","install_details":"Install from git: mkdir -p ~\/.vim\/pack\/vendor\/start\/devgoodies; git clone --depth 1 https:\/\/github.com\/MoserMichael\/devgoodies ~\/.vim\/pack\/vendor\/start\/devgoodies\r\n\r\nInstall from zip file:\r\n\r\nmkdir -p ~\/.vim\/pack\/vendor\/start\/devgoodies; unzip devgoodies.zip -d ~\/.vim\/pack\/vendor\/start\/devgoodies","5":"Install from git: mkdir -p ~\/.vim\/pack\/vendor\/start\/devgoodies; git clone --depth 1 https:\/\/github.com\/MoserMichael\/devgoodies ~\/.vim\/pack\/vendor\/start\/devgoodies\r\n\r\nInstall from zip file:\r\n\r\nmkdir -p ~\/.vim\/pack\/vendor\/start\/devgoodies; unzip devgoodies.zip -d ~\/.vim\/pack\/vendor\/start\/devgoodies","first_name":"Michael","6":"Michael","last_name":"Moser","7":"Moser","releases":[{"0":"5987","vim_version":"7.0","1":"7.0","script_version":"0.0.2","2":"0.0.2","version_comment":"fix docs","3":"fix docs","package":"devgoodies.zip","4":"devgoodies.zip","src_id":"27820","5":"27820","creation_date":"1638047851","6":"1638047851"},{"0":"5987","vim_version":"7.0","1":"7.0","script_version":"0.0.1","2":"0.0.1","version_comment":"Initial upload","3":"Initial upload","package":"devgoodies.zip","4":"devgoodies.zip","src_id":"27808","5":"27808","creation_date":"1637021645","6":"1637021645"}]},"5986":{"script_id":"5986","0":"5986","script_name":"vim-yank-window","1":"vim-yank-window","script_type":"utility","2":"utility","summary":"A small plugin to yank and paste windows","3":"A small plugin to yank and paste windows","description":"A small plugin to yank and paste windows.\r\n\r\nThe plugin is maintained at https:\/\/github.com\/MisanthropicBit\/vim-yank-window.","4":"A small plugin to yank and paste windows.\r\n\r\nThe plugin is maintained at https:\/\/github.com\/MisanthropicBit\/vim-yank-window.","install_details":"Extract the zip in ~\/.vim (or ~\\vimfiles on Windows) or see https:\/\/github.com\/MisanthropicBit\/vim-yank-window for alternative install details.","5":"Extract the zip in ~\/.vim (or ~\\vimfiles on Windows) or see https:\/\/github.com\/MisanthropicBit\/vim-yank-window for alternative install details.","first_name":"","6":"","last_name":"","7":"","releases":[{"0":"5986","vim_version":"7.4","1":"7.4","script_version":"1.0.0","2":"1.0.0","version_comment":"Initial upload","3":"Initial upload","package":"vim-yank-1.0.0.zip","4":"vim-yank-1.0.0.zip","src_id":"27805","5":"27805","creation_date":"1636868199","6":"1636868199"}]},"5985":{"script_id":"5985","0":"5985","script_name":"vimcrypt2","1":"vimcrypt2","script_type":"utility","2":"utility","summary":"open encrypted files in vim, enter password once for the same buffer","3":"open encrypted files in vim, enter password once for the same buffer","description":"The vimcrypt2 extension will encrypt\/decrypt files when read\/written by vim.\r\nYou will have to enter the password that the encryption key is derived from once, for the same buffer.\r\nThis is different from other solutions, where you have to enter the password each time that the buffer is saved.\r\n\r\nThe plugin encrypts files of the following extensions: *.aes,*.cast,*.rc5,*.desx\r\n\r\n- needs a vim that has been compiled with python3 option enabled.\r\n- use the same openssl for reading and writing the same encrypted file. You can't decrypt with LibreSSL, what has been encrypted with OpenSSL.\r\n\r\nSee on github page: https:\/\/github.com\/MoserMichael\/vimcrypt2\r\n","4":"The vimcrypt2 extension will encrypt\/decrypt files when read\/written by vim.\r\nYou will have to enter the password that the encryption key is derived from once, for the same buffer.\r\nThis is different from other solutions, where you have to enter the password each time that the buffer is saved.\r\n\r\nThe plugin encrypts files of the following extensions: *.aes,*.cast,*.rc5,*.desx\r\n\r\n- needs a vim that has been compiled with python3 option enabled.\r\n- use the same openssl for reading and writing the same encrypted file. You can't decrypt with LibreSSL, what has been encrypted with OpenSSL.\r\n\r\nSee on github page: https:\/\/github.com\/MoserMichael\/vimcrypt2\r\n","install_details":"Install from downloaded zip file\r\n\r\nmkdir -p ~\/.vim\/pack\/vendor\/start\/vimcrypt2; unzip vimcrypt2.zip -d ~\/.vim\/pack\/vendor\/start\/vimcrypt2\r\n\r\n\r\nInstall from git\r\n\r\nmkdir -p ~\/.vim\/pack\/vendor\/start\/vimcrypt2; git clone --depth 1 https:\/\/github.com\/MoserMichael\/vimcrypt2 ~\/.vim\/pack\/vendor\/start\/vimcrypt2\r\n","5":"Install from downloaded zip file\r\n\r\nmkdir -p ~\/.vim\/pack\/vendor\/start\/vimcrypt2; unzip vimcrypt2.zip -d ~\/.vim\/pack\/vendor\/start\/vimcrypt2\r\n\r\n\r\nInstall from git\r\n\r\nmkdir -p ~\/.vim\/pack\/vendor\/start\/vimcrypt2; git clone --depth 1 https:\/\/github.com\/MoserMichael\/vimcrypt2 ~\/.vim\/pack\/vendor\/start\/vimcrypt2\r\n","first_name":"Michael","6":"Michael","last_name":"Moser","7":"Moser","releases":[{"0":"5985","vim_version":"7.0","1":"7.0","script_version":"1.1","2":"1.1","version_comment":"adding g:vimcrypt2_cipher (default aes-256-ecb) and g:vimcrypt2_addopt (default -md md5)","3":"adding g:vimcrypt2_cipher (default aes-256-ecb) and g:vimcrypt2_addopt (default -md md5)","package":"vimcrypt2.zip","4":"vimcrypt2.zip","src_id":"28497","5":"28497","creation_date":"1685642589","6":"1685642589"}]},"5984":{"script_id":"5984","0":"5984","script_name":"enfocado","1":"enfocado","script_type":"color scheme","2":"color scheme","summary":"How themes should be.","3":"How themes should be.","description":"https:\/\/github.com\/wuelnerdotexe\/vim-enfocado#enfocado-for-vim","4":"https:\/\/github.com\/wuelnerdotexe\/vim-enfocado#enfocado-for-vim","install_details":"https:\/\/github.com\/wuelnerdotexe\/vim-enfocado#installation","5":"https:\/\/github.com\/wuelnerdotexe\/vim-enfocado#installation","first_name":"Wuelner","6":"Wuelner","last_name":"Mart\u00c3\u00adnez","7":"Mart\u00c3\u00adnez","releases":[{"0":"5984","vim_version":"8.0","1":"8.0","script_version":"6.4.0","2":"6.4.0","version_comment":"https:\/\/github.com\/wuelnerdotexe\/vim-enfocado\/blob\/main\/CHANGELOG.md#640---2023-10-20","3":"https:\/\/github.com\/wuelnerdotexe\/vim-enfocado\/blob\/main\/CHANGELOG.md#640---2023-10-20","package":"vim-enfocado.zip","4":"vim-enfocado.zip","src_id":"28560","5":"28560","creation_date":"1697863581","6":"1697863581"}]},"5983":{"script_id":"5983","0":"5983","script_name":"sign-marks","1":"sign-marks","script_type":"utility","2":"utility","summary":"Unlimited marks. Save\/restore marks. Display marks quickfix\/window. MarksConfig","3":"Unlimited marks. Save\/restore marks. Display marks quickfix\/window. MarksConfig","description":"Sign-marks allows you to have unlimited marks by making use of the vim signs.\r\n\r\nSign-marks is a plugin to: \r\n- Add signs with different levels.\r\n- Display the marks and signs on a quickfix or new window\r\n- Save and restore the marks and signs.\r\n- Navigate the signs and marks.\r\n\r\nThis plugin is a perfect complement for plugin vim-signature (https:\/\/www.vim.org\/scripts\/script.php?script_id=4118)\r\n\r\nI use sign-marks to \r\n- Add signs to lines (:Sm or :Sma) on large logs.\r\n- Remove signs (:Sm or Smd).\r\n- Navigate the log sigsn\/marks (:Smn\/:Smp)\r\n- Open a view window with all signs and marks (:Smw or SmW) or quickfix window (:Smq or :SmQ). \r\n- Open a menu to choose the view (:Smv).\r\n- Save the signs and marks to a config file (:Smsv) or restore them from file (:Sml) \r\n- Save the marks and signs on the file itself as a config line on the bottom of the file (:Smcl).\r\n- Synchronize main and view window (:Smg)\r\n- Show signs resume on new window but filter signs by level (:Smw s1 s3 s10:s15 s30:)\r\n- Show all signs and marks used on current vim session (:Smw a or :Smq a, :SmW a, SmQ a)\r\n- Show all signs and marks used on current vim session filter by file name and sign level (:Smw s3:s14 a +cpp)\r\n\r\nIn case the file's highlighted using hi.vim plugin (https:\/\/www.vim.org\/scripts\/script.php?script_id=5887), the highlighting configuration is also aplied to the marks when opening them on a new window (:Smw) or quickfix window .(:Smq)\r\n\r\nMappings:\r\ns+1 to s+0 to add\/delete a sign on the current line or selected lines.\r\ns+tab+1 to s+tab+5 to open the different view windows.\r\ns+enter to switch between main and view window\r\ns+del or s+supr to remove a sign on current or selected lines.\r\n\r\nThis last option I use it mainly when navigating code and I want to search one line a previously marked or just to understand the code viewing just the code snippets I need. Very handy when using it along with bookmarks.vim (https:\/\/www.vim.org\/scripts\/script.php?script_id=5956)\r\n\r\nThe doc is still pending meanwhile you can check :Smh for an abridged command help and examples:\r\n\r\nAny feedback will be welcome.\r\n\r\n\r\n\r\nADVANCED:\r\nCustomizations you can add to your .vimrc file.\r\n\r\nOverwrite maps s+1 to s+0 used on any other plugin.\r\nlet g:SignMarks_remapPrevMappings = \"yes\"\r\n\r\nRemap s+0 to sign 24:\r\nlet g:SignMarks_userSignMappinsList = []\r\nlet g:SignMarks_userSignMappinsList += [['s0', 24]]\r\n\r\nAdd new view command :Smwt, will show all marks and signs on new tab applying options:\"FH1IMSU.fn.lf\"\r\nlet g:SignMarks_userViewList = []\r\nlet g:SignMarks_userViewList += [ ['' , \"tabnew\" , \"marks&signs\" , \"FH1IMSU.fn.lf\" , \"wt\"] ]\r\n\r\nSame as above but assign also map s+6 and add new command Smv6:\r\nlet g:SignMarks_userViewList = []\r\nlet g:SignMarks_userViewList += [ [6 , \"tabnew\" , \"marks&signs\" , \"FH1IMSU.fn.lf\" , \"wt\"] ]\r\n\r\nYou can see the new signs with command :Smv\r\n\r\nAdd new sign with symbol '=='\r\nlet g:SignMarks_userSignsList = []\r\nlet g:SignMarks_userSignsList += [ [\"==\", \"\", \"\"] ]\r\n\r\nAdd new sign with symbol '=>', use sign highlighing: Error, and content highlighting: ErrorMsg\r\nlet g:SignMarks_userSignsList += [ [\"=>\", \"Error\", \"ErrorMsg\"] ]\r\n\r\nYou can see the new signs with command :Smsh\r\n\r\n\r\n\r\n","4":"Sign-marks allows you to have unlimited marks by making use of the vim signs.\r\n\r\nSign-marks is a plugin to: \r\n- Add signs with different levels.\r\n- Display the marks and signs on a quickfix or new window\r\n- Save and restore the marks and signs.\r\n- Navigate the signs and marks.\r\n\r\nThis plugin is a perfect complement for plugin vim-signature (https:\/\/www.vim.org\/scripts\/script.php?script_id=4118)\r\n\r\nI use sign-marks to \r\n- Add signs to lines (:Sm or :Sma) on large logs.\r\n- Remove signs (:Sm or Smd).\r\n- Navigate the log sigsn\/marks (:Smn\/:Smp)\r\n- Open a view window with all signs and marks (:Smw or SmW) or quickfix window (:Smq or :SmQ). \r\n- Open a menu to choose the view (:Smv).\r\n- Save the signs and marks to a config file (:Smsv) or restore them from file (:Sml) \r\n- Save the marks and signs on the file itself as a config line on the bottom of the file (:Smcl).\r\n- Synchronize main and view window (:Smg)\r\n- Show signs resume on new window but filter signs by level (:Smw s1 s3 s10:s15 s30:)\r\n- Show all signs and marks used on current vim session (:Smw a or :Smq a, :SmW a, SmQ a)\r\n- Show all signs and marks used on current vim session filter by file name and sign level (:Smw s3:s14 a +cpp)\r\n\r\nIn case the file's highlighted using hi.vim plugin (https:\/\/www.vim.org\/scripts\/script.php?script_id=5887), the highlighting configuration is also aplied to the marks when opening them on a new window (:Smw) or quickfix window .(:Smq)\r\n\r\nMappings:\r\ns+1 to s+0 to add\/delete a sign on the current line or selected lines.\r\ns+tab+1 to s+tab+5 to open the different view windows.\r\ns+enter to switch between main and view window\r\ns+del or s+supr to remove a sign on current or selected lines.\r\n\r\nThis last option I use it mainly when navigating code and I want to search one line a previously marked or just to understand the code viewing just the code snippets I need. Very handy when using it along with bookmarks.vim (https:\/\/www.vim.org\/scripts\/script.php?script_id=5956)\r\n\r\nThe doc is still pending meanwhile you can check :Smh for an abridged command help and examples:\r\n\r\nAny feedback will be welcome.\r\n\r\n\r\n\r\nADVANCED:\r\nCustomizations you can add to your .vimrc file.\r\n\r\nOverwrite maps s+1 to s+0 used on any other plugin.\r\nlet g:SignMarks_remapPrevMappings = \"yes\"\r\n\r\nRemap s+0 to sign 24:\r\nlet g:SignMarks_userSignMappinsList = []\r\nlet g:SignMarks_userSignMappinsList += [['s0', 24]]\r\n\r\nAdd new view command :Smwt, will show all marks and signs on new tab applying options:\"FH1IMSU.fn.lf\"\r\nlet g:SignMarks_userViewList = []\r\nlet g:SignMarks_userViewList += [ ['' , \"tabnew\" , \"marks&signs\" , \"FH1IMSU.fn.lf\" , \"wt\"] ]\r\n\r\nSame as above but assign also map s+6 and add new command Smv6:\r\nlet g:SignMarks_userViewList = []\r\nlet g:SignMarks_userViewList += [ [6 , \"tabnew\" , \"marks&signs\" , \"FH1IMSU.fn.lf\" , \"wt\"] ]\r\n\r\nYou can see the new signs with command :Smv\r\n\r\nAdd new sign with symbol '=='\r\nlet g:SignMarks_userSignsList = []\r\nlet g:SignMarks_userSignsList += [ [\"==\", \"\", \"\"] ]\r\n\r\nAdd new sign with symbol '=>', use sign highlighing: Error, and content highlighting: ErrorMsg\r\nlet g:SignMarks_userSignsList += [ [\"=>\", \"Error\", \"ErrorMsg\"] ]\r\n\r\nYou can see the new signs with command :Smsh\r\n\r\n\r\n\r\n","install_details":"Minimum version: Vim 7.0+\r\nRecomended version: Vim 8.0+\r\n\r\nInstall vimball:\r\ndownload signmarks.vmb\r\nvim signmarks.vmb\r\n:so %\r\n:q ","5":"Minimum version: Vim 7.0+\r\nRecomended version: Vim 8.0+\r\n\r\nInstall vimball:\r\ndownload signmarks.vmb\r\nvim signmarks.vmb\r\n:so %\r\n:q ","first_name":"Javier","6":"Javier","last_name":"Puigdevall","7":"Puigdevall","releases":[{"0":"5983","vim_version":"7.0","1":"7.0","script_version":"0.3.1","2":"0.3.1","version_comment":"- Fix: gvim menu issues.\r\n- New: command Smclw to save current signs and marks replacing any\r\n existant config line and save the file, all without user confirmation.\r\n- New: (On commands Sm, Sma, Smo, Smd) when only one sign changed, show a\r\n one line message only.\r\n- New: Smqf2f by default shows only signs and marks on current window\r\n unless options A or W used.\r\n- New: option W for function signmarks#OpenView.\r\n- Fix: remove from all mappings.\r\n- New: add mapping s++ for :Sma\r\n- New: add mapping s+- and s+supr for :Smd","3":"- Fix: gvim menu issues.\r\n- New: command Smclw to save current signs and marks replacing any\r\n existant config line and save the file, all without user confirmation.\r\n- New: (On commands Sm, Sma, Smo, Smd) when only one sign changed, show a\r\n one line message only.\r\n- New: Smqf2f by default shows only signs and marks on current window\r\n unless options A or W used.\r\n- New: option W for function signmarks#OpenView.\r\n- Fix: remove from all mappings.\r\n- New: add mapping s++ for :Sma\r\n- New: add mapping s+- and s+supr for :Smd","package":"signmarks_0.3.1.vmb","4":"signmarks_0.3.1.vmb","src_id":"28087","5":"28087","creation_date":"1657316915","6":"1657316915"},{"0":"5983","vim_version":"7.0","1":"7.0","script_version":"0.3.0","2":"0.3.0","version_comment":"- NEW: change plugin name from marksConfig.vim to signmarks.vim.\r\n- NEW: change all 'Mk...' commands to 'Sm...'.\r\n- New: commands :Smc, SmC, Smo, Smv 1, Smg (map+enter).\r\n- New: when no level selected on Smsa and Sm commands show menu to choose the sign level.","3":"- NEW: change plugin name from marksConfig.vim to signmarks.vim.\r\n- NEW: change all 'Mk...' commands to 'Sm...'.\r\n- New: commands :Smc, SmC, Smo, Smv 1, Smg (map+enter).\r\n- New: when no level selected on Smsa and Sm commands show menu to choose the sign level.","package":"signmarks_0.3.0.vmb","4":"signmarks_0.3.0.vmb","src_id":"27824","5":"27824","creation_date":"1638305762","6":"1638305762"},{"0":"5983","vim_version":"7.0","1":"7.0","script_version":"0.2.0","2":"0.2.0","version_comment":"- New: mapping m+0 to m+9 to add sign with different level.\r\n- New: mapping m+tab+1 to m+tab+5 to open a view.\r\n- New: option \"a\" to show all windows's signs on the view window.\r\n- New: option \"sN\", \"sN:M\", to filter signs on view window by level.\r\n- New: option \"+pattern\", \"-pattern\", to filter files on view window.\r\n- New: option \"M\" to replicate all marks on view window.\r\n- New: option \"I\" to replicate all signs on view window.\r\n- New: option \"_\" to switch to another view window.\r\n- New: command :Mkqf2f to dump all marks and signs to file in quickfix format.\r\n- New: command :Mkg, mapping m+enter to switch to same line on main window.\r\n- Change: all Mkm... commands to Mks\r\n- Change: Mks commands to Mkcl and all Mkm... commands to Mks... (Mks, Mksa, Mksd, MksD).","3":"- New: mapping m+0 to m+9 to add sign with different level.\r\n- New: mapping m+tab+1 to m+tab+5 to open a view.\r\n- New: option \"a\" to show all windows's signs on the view window.\r\n- New: option \"sN\", \"sN:M\", to filter signs on view window by level.\r\n- New: option \"+pattern\", \"-pattern\", to filter files on view window.\r\n- New: option \"M\" to replicate all marks on view window.\r\n- New: option \"I\" to replicate all signs on view window.\r\n- New: option \"_\" to switch to another view window.\r\n- New: command :Mkqf2f to dump all marks and signs to file in quickfix format.\r\n- New: command :Mkg, mapping m+enter to switch to same line on main window.\r\n- Change: all Mkm... commands to Mks\r\n- Change: Mks commands to Mkcl and all Mkm... commands to Mks... (Mks, Mksa, Mksd, MksD).","package":"marksConfig_0.2.0.vmb","4":"marksConfig_0.2.0.vmb","src_id":"27801","5":"27801","creation_date":"1636590207","6":"1636590207"},{"0":"5983","vim_version":"7.0","1":"7.0","script_version":"0.1.1","2":"0.1.1","version_comment":"- New: complete refactoring of function OpenInWindow.\r\n- New: allow to add user options on commands: Mkw, MkW, MkQ and Mkq.\r\n- New: commands Mkqo and Mkwo for user to set all options.\r\n- New: option 'help', to show the available options on OpenInWindow function.\r\n- New: option T, for OpenInWindow function's to preserve line indentation on\r\n quickfix window when the marks\/sings names are not displayed.\r\n- New global variables to configure sign's character and highlight:\r\n g:MarksConfig_signCharacater and g:MarksConfig_signHighlight.","3":"- New: complete refactoring of function OpenInWindow.\r\n- New: allow to add user options on commands: Mkw, MkW, MkQ and Mkq.\r\n- New: commands Mkqo and Mkwo for user to set all options.\r\n- New: option 'help', to show the available options on OpenInWindow function.\r\n- New: option T, for OpenInWindow function's to preserve line indentation on\r\n quickfix window when the marks\/sings names are not displayed.\r\n- New global variables to configure sign's character and highlight:\r\n g:MarksConfig_signCharacater and g:MarksConfig_signHighlight.","package":"marksConfig_0.1.1.vmb","4":"marksConfig_0.1.1.vmb","src_id":"27782","5":"27782","creation_date":"1634322473","6":"1634322473"},{"0":"5983","vim_version":"7.0","1":"7.0","script_version":"0.1.0","2":"0.1.0","version_comment":"- New unnamed marks concept usign vim signs, unnamed marks only exist on the plugin.\r\n They allow to extend marks behind the 25 letters allowed from vim Marks.\r\n- New Mkm, Mkma and Mkmd, MkmD to add\/delete unnamed marks.\r\n- New Mkn and Mkp to navigate the marks, goto line previous\/next\r\n- Link with hi.vim plugin, allow to colorize the buffer window containing all marks\r\n Apply the colors on the main window to the split with marks opened with Mkw\r\n- Set config line default position at end of the file.\r\n","3":"- New unnamed marks concept usign vim signs, unnamed marks only exist on the plugin.\r\n They allow to extend marks behind the 25 letters allowed from vim Marks.\r\n- New Mkm, Mkma and Mkmd, MkmD to add\/delete unnamed marks.\r\n- New Mkn and Mkp to navigate the marks, goto line previous\/next\r\n- Link with hi.vim plugin, allow to colorize the buffer window containing all marks\r\n Apply the colors on the main window to the split with marks opened with Mkw\r\n- Set config line default position at end of the file.\r\n","package":"marksConfig_0.1.0.vmb","4":"marksConfig_0.1.0.vmb","src_id":"27769","5":"27769","creation_date":"1633473406","6":"1633473406"},{"0":"5983","vim_version":"7.0","1":"7.0","script_version":"0.0.1","2":"0.0.1","version_comment":"Initial upload","3":"Initial upload","package":"marksConfig_0.0.1.vmb","4":"marksConfig_0.0.1.vmb","src_id":"27757","5":"27757","creation_date":"1633019252","6":"1633019252"}]},"5982":{"script_id":"5982","0":"5982","script_name":"YANP","1":"YANP","script_type":"utility","2":"utility","summary":"Notetaking plugin with recurring topics structure and customisable syntax.","3":"Notetaking plugin with recurring topics structure and customisable syntax.","description":"Long story short, here are the main features of this plugin that may distinguish it from the others:\r\n\r\nRecursive structure. Every topic is represented with its own directory within recursive structure of subdirectories. YANP handles creation of files and directories, maintains this structure as well as provides simple user interface for defining links to different files.\r\n \r\nCustomizable syntax plugin. YANP doesn't handle syntax by itself - thus you can choose any markup syntax (like Markdown, HTML, etc) you want to define links between files, provided you have a plugin that utilizes YANP API. By default, YANP works with MarkdowneyJr Markdown formatting plugin. The list plugins know to integrate YANP can be found here.\r\n\r\nAPI for syntax formatting plugins. YANP delegates syntax formatting (like replacing selected text with a link to a desired file) to other plugins while providing a clear API that allows maintaining a unified structure of notes. Definition of exact paths to files and its creation is done by YANP, syntax plugin is only responsible for replacing a text with a link. Documentation for the API is provided to make syntax plugin integration easier.\r\n\r\nLinks. Links are everywhere. Defined with a single keystroke.\r\n\r\nCustomization. You can change quite a lot of stuff, starting from names of index files and default contents of created files, till how the path for different types of files will look like.\r\n\r\nFast access to last created files, last visited index files, today's fast notes, and other supplementary, but useful features.\r\n\r\n\r\nPlease refer to the plugin's repo to find a detailed wiki - https:\/\/github.com\/boson-joe\/YANP\r\n\r\n\r\n","4":"Long story short, here are the main features of this plugin that may distinguish it from the others:\r\n\r\nRecursive structure. Every topic is represented with its own directory within recursive structure of subdirectories. YANP handles creation of files and directories, maintains this structure as well as provides simple user interface for defining links to different files.\r\n \r\nCustomizable syntax plugin. YANP doesn't handle syntax by itself - thus you can choose any markup syntax (like Markdown, HTML, etc) you want to define links between files, provided you have a plugin that utilizes YANP API. By default, YANP works with MarkdowneyJr Markdown formatting plugin. The list plugins know to integrate YANP can be found here.\r\n\r\nAPI for syntax formatting plugins. YANP delegates syntax formatting (like replacing selected text with a link to a desired file) to other plugins while providing a clear API that allows maintaining a unified structure of notes. Definition of exact paths to files and its creation is done by YANP, syntax plugin is only responsible for replacing a text with a link. Documentation for the API is provided to make syntax plugin integration easier.\r\n\r\nLinks. Links are everywhere. Defined with a single keystroke.\r\n\r\nCustomization. You can change quite a lot of stuff, starting from names of index files and default contents of created files, till how the path for different types of files will look like.\r\n\r\nFast access to last created files, last visited index files, today's fast notes, and other supplementary, but useful features.\r\n\r\n\r\nPlease refer to the plugin's repo to find a detailed wiki - https:\/\/github.com\/boson-joe\/YANP\r\n\r\n\r\n","install_details":"THIS PLUGIN REQUIRES an additional syntax plugin installation. You can install markdowneyJr, or other plugin that supports YANP. See these pages below for more information:\r\n\r\nmarkdowneyJr plugin - https:\/\/www.vim.org\/scripts\/script.php?script_id=5974\r\nfull installation guide - https:\/\/github.com\/boson-joe\/YANP\/wiki\/YANP-Installation-Guide.\r\n\r\n\r\nYou can install the plugin by simply putting the files of the plugin in `plugin\/` directory in your `.vim\/` directory. One of the commands that could be used is `wget`. Type this in your terminal:\r\n\r\n> wget https:\/\/github.com\/boson-joe\/YANP\/blob\/master\/plugin\/yanp.vim\r\n\r\nTo have documentation, do the same with files in `doc\/` directory - you need to put them into `doc\/` directory in your `.vim\/` directory.","5":"THIS PLUGIN REQUIRES an additional syntax plugin installation. You can install markdowneyJr, or other plugin that supports YANP. See these pages below for more information:\r\n\r\nmarkdowneyJr plugin - https:\/\/www.vim.org\/scripts\/script.php?script_id=5974\r\nfull installation guide - https:\/\/github.com\/boson-joe\/YANP\/wiki\/YANP-Installation-Guide.\r\n\r\n\r\nYou can install the plugin by simply putting the files of the plugin in `plugin\/` directory in your `.vim\/` directory. One of the commands that could be used is `wget`. Type this in your terminal:\r\n\r\n> wget https:\/\/github.com\/boson-joe\/YANP\/blob\/master\/plugin\/yanp.vim\r\n\r\nTo have documentation, do the same with files in `doc\/` directory - you need to put them into `doc\/` directory in your `.vim\/` directory.","first_name":"boson","6":"boson","last_name":"joe","7":"joe","releases":[{"0":"5982","vim_version":"8.2","1":"8.2","script_version":"1.0.0","2":"1.0.0","version_comment":"v1.0.0, with documentation and license.","3":"v1.0.0, with documentation and license.","package":"yanp.tar.xz","4":"yanp.tar.xz","src_id":"27751","5":"27751","creation_date":"1632717485","6":"1632717485"},{"0":"5982","vim_version":"8.2","1":"8.2","script_version":"1.0.0","2":"1.0.0","version_comment":"Initial upload","3":"Initial upload","package":"yanp.vim","4":"yanp.vim","src_id":"27750","5":"27750","creation_date":"1632717369","6":"1632717369"}]},"5981":{"script_id":"5981","0":"5981","script_name":"vim-adif","1":"vim-adif","script_type":"syntax","2":"syntax","summary":"ADIF syntax support","3":"ADIF syntax support","description":"Vim file detect and syntax definition files for Amateur Data Interchange Format (ADIF), a file format for exchanging amateur radio logging data between programs and various online services for radio amateurs.\r\n\r\nRepository: https:\/\/gitlab.com\/Nate_B\/vim-adif","4":"Vim file detect and syntax definition files for Amateur Data Interchange Format (ADIF), a file format for exchanging amateur radio logging data between programs and various online services for radio amateurs.\r\n\r\nRepository: https:\/\/gitlab.com\/Nate_B\/vim-adif","install_details":"Favorite package method.","5":"Favorite package method.","first_name":"Nate","6":"Nate","last_name":"Bargmann","7":"Bargmann","releases":[{"0":"5981","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"vim-adif_0.1.tar.gz","4":"vim-adif_0.1.tar.gz","src_id":"27743","5":"27743","creation_date":"1632046853","6":"1632046853"}]},"5980":{"script_id":"5980","0":"5980","script_name":"verilog_smn.vim","1":"verilog_smn.vim","script_type":"utility","2":"utility","summary":"To display the module name and instance name when viewing verilog file","3":"To display the module name and instance name when viewing verilog file","description":"When you view a verilog file, especially there are multiple instances in one file, you may want to know which module or instance under the cursor. Without this script, you have to scroll or search back to find the module and instance name. After install this script, you only need to type :SMN command (i.e. ShowModuleName) to echo the module and instance name in the status line.","4":"When you view a verilog file, especially there are multiple instances in one file, you may want to know which module or instance under the cursor. Without this script, you have to scroll or search back to find the module and instance name. After install this script, you only need to type :SMN command (i.e. ShowModuleName) to echo the module and instance name in the status line.","install_details":"Put the file into your ~\/.vim\/plugin directory or use the Pathogen to put the script into bundle\/verilog_smn\/plugin directory.","5":"Put the file into your ~\/.vim\/plugin directory or use the Pathogen to put the script into bundle\/verilog_smn\/plugin directory.","first_name":"","6":"","last_name":"","7":"","releases":[{"0":"5980","vim_version":"7.4","1":"7.4","script_version":"1.3","2":"1.3","version_comment":"Fix some bugs and print the line number of the found module and instance.","3":"Fix some bugs and print the line number of the found module and instance.","package":"verilog_smn.vim","4":"verilog_smn.vim","src_id":"27740","5":"27740","creation_date":"1631384289","6":"1631384289"},{"0":"5980","vim_version":"7.4","1":"7.4","script_version":"1.1","2":"1.1","version_comment":"Initial upload","3":"Initial upload","package":"verilog_smn.vim","4":"verilog_smn.vim","src_id":"27739","5":"27739","creation_date":"1631301602","6":"1631301602"}]},"5978":{"script_id":"5978","0":"5978","script_name":"taberian","1":"taberian","script_type":"utility","2":"utility","summary":"Clickable tabs per VIM window","3":"Clickable tabs per VIM window","description":"Taberian applies the concept of tabs to VIM windows. Each VIM window (split)\r\nmay contain a number of tabs, so user can switch between them, rearrange,\r\nclose etc.\r\n\r\nTaberian works out of the box and does not require any configuration. If there\r\nare no tabs created then Taberian will not display anything. To start, create a\r\nnew tab via `CTRL-W t`.\r\n\r\nGitHub: https:\/\/github.com\/noscript\/taberian.vim","4":"Taberian applies the concept of tabs to VIM windows. Each VIM window (split)\r\nmay contain a number of tabs, so user can switch between them, rearrange,\r\nclose etc.\r\n\r\nTaberian works out of the box and does not require any configuration. If there\r\nare no tabs created then Taberian will not display anything. To start, create a\r\nnew tab via `CTRL-W t`.\r\n\r\nGitHub: https:\/\/github.com\/noscript\/taberian.vim","install_details":"Extract to ~\/.vim\/ ","5":"Extract to ~\/.vim\/ ","first_name":"Sergey","6":"Sergey","last_name":"Vlasov","7":"Vlasov","releases":[{"0":"5978","vim_version":"9.0","1":"9.0","script_version":"0.6","2":"0.6","version_comment":"- rewrite with popups\r\n- middle click to close tab\r\n- option to hide tab index\r\n- option to hide buffer number","3":"- rewrite with popups\r\n- middle click to close tab\r\n- option to hide tab index\r\n- option to hide buffer number","package":"taberian-0.6.zip","4":"taberian-0.6.zip","src_id":"28524","5":"28524","creation_date":"1691571069","6":"1691571069"},{"0":"5978","vim_version":"9.0","1":"9.0","script_version":"0.5","2":"0.5","version_comment":"vim9script rewrite","3":"vim9script rewrite","package":"taberian-0.5.zip","4":"taberian-0.5.zip","src_id":"28092","5":"28092","creation_date":"1657688358","6":"1657688358"},{"0":"5978","vim_version":"8.2","1":"8.2","script_version":"0.4","2":"0.4","version_comment":"dropped vim 8.2.3524 compatibility\r\nstate import \/ export functions","3":"dropped vim 8.2.3524 compatibility\r\nstate import \/ export functions","package":"taberian-0.4.zip","4":"taberian-0.4.zip","src_id":"27817","5":"27817","creation_date":"1637894292","6":"1637894292"},{"0":"5978","vim_version":"8.2","1":"8.2","script_version":"0.3","2":"0.3","version_comment":"Vim 8.2.3524 compatibility","3":"Vim 8.2.3524 compatibility","package":"taberian-0.3.zip","4":"taberian-0.3.zip","src_id":"27810","5":"27810","creation_date":"1637184082","6":"1637184082"},{"0":"5978","vim_version":"8.0","1":"8.0","script_version":"0.2","2":"0.2","version_comment":"- handle unnamed buffers\r\n- confirm window close","3":"- handle unnamed buffers\r\n- confirm window close","package":"taberian-0.2.zip","4":"taberian-0.2.zip","src_id":"27783","5":"27783","creation_date":"1634513204","6":"1634513204"},{"0":"5978","vim_version":"8.0","1":"8.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"taberian.zip","4":"taberian.zip","src_id":"27729","5":"27729","creation_date":"1630700365","6":"1630700365"}]},"5977":{"script_id":"5977","0":"5977","script_name":"cmap.vim","1":"cmap.vim","script_type":"syntax","2":"syntax","summary":"Save time in C in Vim","3":"Save time in C in Vim","description":"https:\/\/notabug.org\/doriscarson\/cmap.vim","4":"https:\/\/notabug.org\/doriscarson\/cmap.vim","install_details":"","5":"","first_name":"Doris","6":"Doris","last_name":"Carson","7":"Carson","releases":[{"0":"5977","vim_version":"8.0","1":"8.0","script_version":"1.2","2":"1.2","version_comment":"added function support\r\n","3":"added function support\r\n","package":"cmap.vim.tar.gz","4":"cmap.vim.tar.gz","src_id":"27727","5":"27727","creation_date":"1630662345","6":"1630662345"},{"0":"5977","vim_version":"8.0","1":"8.0","script_version":"1.1","2":"1.1","version_comment":"Added const support","3":"Added const support","package":"cmap.vim.tar.gz","4":"cmap.vim.tar.gz","src_id":"27725","5":"27725","creation_date":"1630610057","6":"1630610057"},{"0":"5977","vim_version":"8.0","1":"8.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"cmap.vim.tar.gz","4":"cmap.vim.tar.gz","src_id":"27724","5":"27724","creation_date":"1630582345","6":"1630582345"}]},"5976":{"script_id":"5976","0":"5976","script_name":"4colors","1":"4colors","script_type":"color scheme","2":"color scheme","summary":"Distraction-free theme that only uses 4 colors","3":"Distraction-free theme that only uses 4 colors","description":"Easy to customise colorscheme that only uses 4 colors and provides a distraction-free environment that lets you focus on your code.\r\n\r\nRepository:\r\n\r\nhttps:\/\/github.com\/mihaifm\/4colors","4":"Easy to customise colorscheme that only uses 4 colors and provides a distraction-free environment that lets you focus on your code.\r\n\r\nRepository:\r\n\r\nhttps:\/\/github.com\/mihaifm\/4colors","install_details":"","5":"","first_name":"Mihai","6":"Mihai","last_name":"Ciuraru","7":"Ciuraru","releases":[{"0":"5976","vim_version":"7.0","1":"7.0","script_version":"1.0.0","2":"1.0.0","version_comment":"Initial upload","3":"Initial upload","package":"4colors.zip","4":"4colors.zip","src_id":"27722","5":"27722","creation_date":"1630211293","6":"1630211293"}]},"5975":{"script_id":"5975","0":"5975","script_name":"GitBlame","1":"GitBlame","script_type":"utility","2":"utility","summary":"plugin provides minimal command set for working with git","3":"plugin provides minimal command set for working with git","description":"This project is a minimal vim plugin for working with git; with a focus on git blame, git grep, git log --graph, git ls-files, git diff commands, allows to check out local and remote branches, view git status, stage and unstage files. It's not too complicated, so there is a chance that it will work for your installation too.\r\n\r\nsee https:\/\/github.com\/MoserMichael\/gitblame\r\n\r\nThis plugin is currently not supporting merging\/rebasing, as I am used to doing these from the command line. You have got a different plugin, vim fugitive, if you need to merge or rebase from within vim.\r\n\r\nLink to presentation on this plugin on youtube: https:\/\/www.youtube.com\/watch?v=7ug8cWKAuO8\r\n\r\n","4":"This project is a minimal vim plugin for working with git; with a focus on git blame, git grep, git log --graph, git ls-files, git diff commands, allows to check out local and remote branches, view git status, stage and unstage files. It's not too complicated, so there is a chance that it will work for your installation too.\r\n\r\nsee https:\/\/github.com\/MoserMichael\/gitblame\r\n\r\nThis plugin is currently not supporting merging\/rebasing, as I am used to doing these from the command line. You have got a different plugin, vim fugitive, if you need to merge or rebase from within vim.\r\n\r\nLink to presentation on this plugin on youtube: https:\/\/www.youtube.com\/watch?v=7ug8cWKAuO8\r\n\r\n","install_details":"with git:\r\n\r\nmkdir -p ~\/.vim\/pack\/vendor\/start\/gitblame; git clone --depth 1 https:\/\/github.com\/MoserMichael\/gitblame ~\/.vim\/pack\/vendor\/start\/gitblame\r\n\r\notherwise unzip the downloaded file into ~\/.vim\/plugin\/gitblame, like this:\r\n\r\nmkdir -p ~\/.vim\/pack\/vendor\/start\/gitblame; unzip gitblame.zip -d ~\/.vim\/pack\/vendor\/start\/gitblame\r\n\r\nTo generate the help text run the following vim command:\r\n\r\n:helptags ALL\r\n\r\nAfter that you can view the help file of plugin via vim command:\r\n\r\n:help gitblame\r\n\r\nYou can also view the documentation online: https:\/\/raw.githubusercontent.com\/MoserMichael\/gitblame\/master\/doc\/gitblame.txt\r\n","5":"with git:\r\n\r\nmkdir -p ~\/.vim\/pack\/vendor\/start\/gitblame; git clone --depth 1 https:\/\/github.com\/MoserMichael\/gitblame ~\/.vim\/pack\/vendor\/start\/gitblame\r\n\r\notherwise unzip the downloaded file into ~\/.vim\/plugin\/gitblame, like this:\r\n\r\nmkdir -p ~\/.vim\/pack\/vendor\/start\/gitblame; unzip gitblame.zip -d ~\/.vim\/pack\/vendor\/start\/gitblame\r\n\r\nTo generate the help text run the following vim command:\r\n\r\n:helptags ALL\r\n\r\nAfter that you can view the help file of plugin via vim command:\r\n\r\n:help gitblame\r\n\r\nYou can also view the documentation online: https:\/\/raw.githubusercontent.com\/MoserMichael\/gitblame\/master\/doc\/gitblame.txt\r\n","first_name":"Michael","6":"Michael","last_name":"Moser","7":"Moser","releases":[{"0":"5975","vim_version":"7.0","1":"7.0","script_version":"0.8.6","2":"0.8.6","version_comment":" change gitdiff\r\n\r\n ignore numbers in status following R\r\n gitdiff between two commit, fix wrong command to show file at\r\n from_commit","3":" change gitdiff\r\n\r\n ignore numbers in status following R\r\n gitdiff between two commit, fix wrong command to show file at\r\n from_commit","package":"gitblame.zip","4":"gitblame.zip","src_id":"28026","5":"28026","creation_date":"1651653002","6":"1651653002"},{"0":"5975","vim_version":"7.0","1":"7.0","script_version":"0.8.5","2":"0.8.5","version_comment":"fix renaming of buffers in git diff ","3":"fix renaming of buffers in git diff ","package":"gitblame.zip","4":"gitblame.zip","src_id":"27797","5":"27797","creation_date":"1636304616","6":"1636304616"}]},"5974":{"script_id":"5974","0":"5974","script_name":"MarkdowneyJr","1":"MarkdowneyJr","script_type":"utility","2":"utility","summary":"Format Markdown files with simple keystrokes.","3":"Format Markdown files with simple keystrokes.","description":"Hi!\r\n\r\nMy name is Markdowney Jr, nice to meet you! I am a Vim plugin that makes editing markdown files easy using simple keystrokes. Depending on the formatting option, I can do transformations on visual selection, line range or motion (like 3wd, for example) or combinations of those. Hit a keystroke once - and transformation is made. If you then hit the same keystroke once or multiple times again, I will toggle through options for a particular transformation and change the text accordingly. For example, if you select a word and hit a keystroke responsible for emphasis multiple times, I will make selected text cursive, bold and then both, and once again, toggling between the options. Please refer to the User Guide to see how we can interact - https:\/\/github.com\/boson-joe\/markdowneyJR\/wiki\/MarkdowneyJr-User-Guide.\r\n\r\nThere is no need to set remaps for all the formatting options - you can define just two remaps in your vimrc, and I will take care of the rest. In case you don't want to set any remaps at all, I can give you default ones. You can also remap any or all formatting options to your liking. To see how you can set remaps and customize your experience please refer to the Customization Guide - https:\/\/github.com\/boson-joe\/markdowneyJR\/wiki\/MarkdowneyJr-Customization-Guide.\r\n\r\nAt the moment I can handle basic basic markdown syntax for you, but if you write my devs, they would be happy to introduce more features.","4":"Hi!\r\n\r\nMy name is Markdowney Jr, nice to meet you! I am a Vim plugin that makes editing markdown files easy using simple keystrokes. Depending on the formatting option, I can do transformations on visual selection, line range or motion (like 3wd, for example) or combinations of those. Hit a keystroke once - and transformation is made. If you then hit the same keystroke once or multiple times again, I will toggle through options for a particular transformation and change the text accordingly. For example, if you select a word and hit a keystroke responsible for emphasis multiple times, I will make selected text cursive, bold and then both, and once again, toggling between the options. Please refer to the User Guide to see how we can interact - https:\/\/github.com\/boson-joe\/markdowneyJR\/wiki\/MarkdowneyJr-User-Guide.\r\n\r\nThere is no need to set remaps for all the formatting options - you can define just two remaps in your vimrc, and I will take care of the rest. In case you don't want to set any remaps at all, I can give you default ones. You can also remap any or all formatting options to your liking. To see how you can set remaps and customize your experience please refer to the Customization Guide - https:\/\/github.com\/boson-joe\/markdowneyJR\/wiki\/MarkdowneyJr-Customization-Guide.\r\n\r\nAt the moment I can handle basic basic markdown syntax for you, but if you write my devs, they would be happy to introduce more features.","install_details":"To make sure the plugin works properly, we suggest you to check that your Vim has version 8.2 or higher (:echo v:version >= 802 should print out 1).\r\n\r\n\r\nManual\r\n\r\nYou can install the plugin by simply putting the files of the plugin in plugin\/ directory in your .vim\/ directory. One of the commands that could be used is wget. Type this in your terminal:\r\n\r\n wget https:\/\/github.com\/boson-joe\/markdowneyJR\/blob\/master\/plugin\/markdowneyjr.vim\r\n\r\nTo have documentation, do the same with files in doc\/ directory - you need to put them into doc\/ directory in your .vim\/ directory.\r\n\r\n\r\nPlugin manager\r\n\r\nYou may find plugin managers convenient to install and manage plugins you want in your Vim, including MarkdowneyJr.\r\n\r\nvim-plug\r\n\r\nIf you are using vim-plug plugin manager, refer to their manual here - https:\/\/github.com\/junegunn\/vim-plug#usage\r\n\r\nVundle\r\n\r\nIf you are using Vundle plugin manager, refer to their manual here - https:\/\/github.com\/VundleVim\/Vundle.vim#quick-start.\r\n\r\nPathogen\r\n\r\nIf you are using Pathogen plugin manager, refer to their manual here - https:\/\/github.com\/tpope\/vim-pathogen#installation.\r\n","5":"To make sure the plugin works properly, we suggest you to check that your Vim has version 8.2 or higher (:echo v:version >= 802 should print out 1).\r\n\r\n\r\nManual\r\n\r\nYou can install the plugin by simply putting the files of the plugin in plugin\/ directory in your .vim\/ directory. One of the commands that could be used is wget. Type this in your terminal:\r\n\r\n wget https:\/\/github.com\/boson-joe\/markdowneyJR\/blob\/master\/plugin\/markdowneyjr.vim\r\n\r\nTo have documentation, do the same with files in doc\/ directory - you need to put them into doc\/ directory in your .vim\/ directory.\r\n\r\n\r\nPlugin manager\r\n\r\nYou may find plugin managers convenient to install and manage plugins you want in your Vim, including MarkdowneyJr.\r\n\r\nvim-plug\r\n\r\nIf you are using vim-plug plugin manager, refer to their manual here - https:\/\/github.com\/junegunn\/vim-plug#usage\r\n\r\nVundle\r\n\r\nIf you are using Vundle plugin manager, refer to their manual here - https:\/\/github.com\/VundleVim\/Vundle.vim#quick-start.\r\n\r\nPathogen\r\n\r\nIf you are using Pathogen plugin manager, refer to their manual here - https:\/\/github.com\/tpope\/vim-pathogen#installation.\r\n","first_name":"boson","6":"boson","last_name":"joe","7":"joe","releases":[{"0":"5974","vim_version":"8.2","1":"8.2","script_version":"1.1.0","2":"1.1.0","version_comment":"markdowneyjr (v. 1.1.0), with documentation and license.","3":"markdowneyjr (v. 1.1.0), with documentation and license.","package":"markdowneyjr.tar.xz","4":"markdowneyjr.tar.xz","src_id":"27753","5":"27753","creation_date":"1632717630","6":"1632717630"},{"0":"5974","vim_version":"8.2","1":"8.2","script_version":"1.1.0","2":"1.1.0","version_comment":"Added integration with YANP plugin - https:\/\/www.vim.org\/scripts\/script.php?script_id=5982","3":"Added integration with YANP plugin - https:\/\/www.vim.org\/scripts\/script.php?script_id=5982","package":"markdowneyjr.vim","4":"markdowneyjr.vim","src_id":"27752","5":"27752","creation_date":"1632717567","6":"1632717567"},{"0":"5974","vim_version":"8.2","1":"8.2","script_version":"1.0.0","2":"1.0.0","version_comment":"markdowneyjr (v. 1.0.0), with documentation and license.","3":"markdowneyjr (v. 1.0.0), with documentation and license.","package":"markdowneyjr.tar.xz","4":"markdowneyjr.tar.xz","src_id":"27704","5":"27704","creation_date":"1628639182","6":"1628639182"},{"0":"5974","vim_version":"8.2","1":"8.2","script_version":"1.0.0","2":"1.0.0","version_comment":"Initial upload","3":"Initial upload","package":"markdowneyjr.vim","4":"markdowneyjr.vim","src_id":"27703","5":"27703","creation_date":"1628639075","6":"1628639075"}]},"5973":{"script_id":"5973","0":"5973","script_name":"vim-qf-diagnostics","1":"vim-qf-diagnostics","script_type":"utility","2":"utility","summary":"Highlight quickfix errors, and display error messages in a popup window","3":"Highlight quickfix errors, and display error messages in a popup window","description":"- Highlight the diagnostics (of a project-build, linter, grep) stored in a quickfix list in the buffer and sign column.\r\n- Display the error message for the current line in a popup window next to the cursor.\r\n\r\nPopup window:\r\n\r\n (qf-diagnostics-popup-quickfix) -- Display a popup window at the current cursor position with the error message found for the current line in the quickfix list. If the line contains several errors, all entries are collected and displayed in the same popup window.\r\n (qf-diagnostics-popup-loclist) -- Same as above but display the error messages from the current location-list of the current window.\r\n\r\nIf not all quickfix errors (for the current line) fit into the popup window, a scrollbar will appear on the right side. The popup window can then be scrolled with CTRL-J and CTRL-K, or alternatively, using the mouse wheel. Pressing CTRL-C or moving the cursor in any direction will close the popup window.\r\n\r\nExample:\r\n\r\n nmap gh (qf-diagnostics-popup-quickfix)\r\n nmap gH (qf-diagnostics-popup-loclist)\r\n\r\n\r\nSigns and text highlightings:\r\n\r\nThe items in the quickfix and location list can be highlighted in the sign column and in the buffer directly. Both highlightings are optional and can be individually configured in g:qfdiagnostics. By default, only signs are placed.\r\n\r\n :DiagnosticsPlace -- Highlight the diagnostics from the current quickfix list.\r\n :LDiagnosticsPlace -- Same as :DiagnosticsPlace but use the current location list of the current window.\r\n :DiagnosticsClear -- Remove the highlightings placed by :DiagnosticsPlace.\r\n :LDiagnosticsClear[!] -- Remove the highlightings placed by :LDiagnosticsPlace.\r\n :DiagnosticsToggle -- Toggle the diagnostics from the quickfix list.\r\n :LDiagnosticsToggle -- Toggle the diagnostics from the location list.\r\n\r\nNotes:\r\n\r\n :DiagnosticsPlace and :LDiagnosticsPlace will first remove any highlightings that have been previously placed by the respective command.\r\n :LDiagnosticsPlace can be run in multiple windows to simultaneously highlight diagnostics from several location lists.\r\n :LDiagnosticsClear must always be run in the same window where :LDiagnosticsPlace has been executed to remove the previously placed diagnostics.\r\n To remove the highlightings of all diagnostics from all location lists at once, run :LDiagnosticsClear!.\r\n\r\nExamples:\r\n\r\nToggle the diagnostics of the quickfix and location lists with F7 and F8, respectively:\r\n\r\n nnoremap DiagnosticsToggle\r\n nnoremap LDiagnosticsToggle\r\n\r\nIf you want to place the diagnostics automatically after running :make or :lmake, add the following to your vimrc:\r\n\r\n augroup qf-diagnostics-user\r\n autocmd!\r\n autocmd QuickfixCmdPost make DiagnosticsPlace\r\n autocmd QuickfixCmdPost lmake LDiagnosticsPlace\r\n augroup END\r\n\r\nhttps:\/\/github.com\/bfrg\/vim-qf-diagnostics","4":"- Highlight the diagnostics (of a project-build, linter, grep) stored in a quickfix list in the buffer and sign column.\r\n- Display the error message for the current line in a popup window next to the cursor.\r\n\r\nPopup window:\r\n\r\n (qf-diagnostics-popup-quickfix) -- Display a popup window at the current cursor position with the error message found for the current line in the quickfix list. If the line contains several errors, all entries are collected and displayed in the same popup window.\r\n (qf-diagnostics-popup-loclist) -- Same as above but display the error messages from the current location-list of the current window.\r\n\r\nIf not all quickfix errors (for the current line) fit into the popup window, a scrollbar will appear on the right side. The popup window can then be scrolled with CTRL-J and CTRL-K, or alternatively, using the mouse wheel. Pressing CTRL-C or moving the cursor in any direction will close the popup window.\r\n\r\nExample:\r\n\r\n nmap gh (qf-diagnostics-popup-quickfix)\r\n nmap gH (qf-diagnostics-popup-loclist)\r\n\r\n\r\nSigns and text highlightings:\r\n\r\nThe items in the quickfix and location list can be highlighted in the sign column and in the buffer directly. Both highlightings are optional and can be individually configured in g:qfdiagnostics. By default, only signs are placed.\r\n\r\n :DiagnosticsPlace -- Highlight the diagnostics from the current quickfix list.\r\n :LDiagnosticsPlace -- Same as :DiagnosticsPlace but use the current location list of the current window.\r\n :DiagnosticsClear -- Remove the highlightings placed by :DiagnosticsPlace.\r\n :LDiagnosticsClear[!] -- Remove the highlightings placed by :LDiagnosticsPlace.\r\n :DiagnosticsToggle -- Toggle the diagnostics from the quickfix list.\r\n :LDiagnosticsToggle -- Toggle the diagnostics from the location list.\r\n\r\nNotes:\r\n\r\n :DiagnosticsPlace and :LDiagnosticsPlace will first remove any highlightings that have been previously placed by the respective command.\r\n :LDiagnosticsPlace can be run in multiple windows to simultaneously highlight diagnostics from several location lists.\r\n :LDiagnosticsClear must always be run in the same window where :LDiagnosticsPlace has been executed to remove the previously placed diagnostics.\r\n To remove the highlightings of all diagnostics from all location lists at once, run :LDiagnosticsClear!.\r\n\r\nExamples:\r\n\r\nToggle the diagnostics of the quickfix and location lists with F7 and F8, respectively:\r\n\r\n nnoremap DiagnosticsToggle\r\n nnoremap LDiagnosticsToggle\r\n\r\nIf you want to place the diagnostics automatically after running :make or :lmake, add the following to your vimrc:\r\n\r\n augroup qf-diagnostics-user\r\n autocmd!\r\n autocmd QuickfixCmdPost make DiagnosticsPlace\r\n autocmd QuickfixCmdPost lmake LDiagnosticsPlace\r\n augroup END\r\n\r\nhttps:\/\/github.com\/bfrg\/vim-qf-diagnostics","install_details":"Run the following in the terminal:\r\n\r\n cd ~\/.vim\/pack\/git-plugins\/start\r\n git clone https:\/\/github.com\/bfrg\/vim-qf-diagnostics\r\n vim -u NONE -c 'helptags vim-qf-diagnostics\/doc | quit'\r\n\r\nNote: The directory name git-plugins is arbitrary, you can pick any other name. For more details see :help packages. Alternatively, use your favorite plugin manager.","5":"Run the following in the terminal:\r\n\r\n cd ~\/.vim\/pack\/git-plugins\/start\r\n git clone https:\/\/github.com\/bfrg\/vim-qf-diagnostics\r\n vim -u NONE -c 'helptags vim-qf-diagnostics\/doc | quit'\r\n\r\nNote: The directory name git-plugins is arbitrary, you can pick any other name. For more details see :help packages. Alternatively, use your favorite plugin manager.","first_name":"foo","6":"foo","last_name":"bar","7":"bar","releases":[{"0":"5973","vim_version":"8.1","1":"8.1","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"vim-qf-diagnostics.tar.gz","4":"vim-qf-diagnostics.tar.gz","src_id":"27673","5":"27673","creation_date":"1627081293","6":"1627081293"}]},"5972":{"script_id":"5972","0":"5972","script_name":"vim-jqplay","1":"vim-jqplay","script_type":"utility","2":"utility","summary":"Run jq interactively in Vim","3":"Run jq interactively in Vim","description":"Run jq on a json buffer, and interactively update the output window whenever the input buffer or the jq filter buffer are modified similar to jqplay.org.\r\n\r\nCommands:\r\n\r\n :Jqplay [{args}] -- Start an interactive session using the current json buffer and the jq options {args}.\r\n :JqplayScratch [{args}] -- Like :Jqplay but creates a new scratch buffer as input.\r\n :JqplayScratch! [{args}] -- Like :JqplayScratch but forces --null-input and doesn't pass any input to jq.\r\n\r\nOnce an interactive session was started the following commands are available:\r\n\r\n :JqplayClose[!] -- Stop the interactive session. Add a ! to also delete all associated scratch buffers.\r\n :Jqrun [{args}] -- Invoke jq manually with the jq options {args}.\r\n :Jqstop -- Terminate a running jq process started by this plugin.\r\n\r\nhttps:\/\/github.com\/bfrg\/vim-jqplay","4":"Run jq on a json buffer, and interactively update the output window whenever the input buffer or the jq filter buffer are modified similar to jqplay.org.\r\n\r\nCommands:\r\n\r\n :Jqplay [{args}] -- Start an interactive session using the current json buffer and the jq options {args}.\r\n :JqplayScratch [{args}] -- Like :Jqplay but creates a new scratch buffer as input.\r\n :JqplayScratch! [{args}] -- Like :JqplayScratch but forces --null-input and doesn't pass any input to jq.\r\n\r\nOnce an interactive session was started the following commands are available:\r\n\r\n :JqplayClose[!] -- Stop the interactive session. Add a ! to also delete all associated scratch buffers.\r\n :Jqrun [{args}] -- Invoke jq manually with the jq options {args}.\r\n :Jqstop -- Terminate a running jq process started by this plugin.\r\n\r\nhttps:\/\/github.com\/bfrg\/vim-jqplay","install_details":"Run the following in your terminal:\r\n\r\n cd ~\/.vim\/pack\/git-plugins\/start\r\n git clone https:\/\/github.com\/bfrg\/vim-jqplay\r\n vim -u NONE -c 'helptags vim-jqplay\/doc | quit'\r\n\r\nNote: The directory name git-plugins is arbitrary, you can pick any other name. For more details see :help packages.\r\n\r\nAlternatively, use your favorite plugin manager.","5":"Run the following in your terminal:\r\n\r\n cd ~\/.vim\/pack\/git-plugins\/start\r\n git clone https:\/\/github.com\/bfrg\/vim-jqplay\r\n vim -u NONE -c 'helptags vim-jqplay\/doc | quit'\r\n\r\nNote: The directory name git-plugins is arbitrary, you can pick any other name. For more details see :help packages.\r\n\r\nAlternatively, use your favorite plugin manager.","first_name":"foo","6":"foo","last_name":"bar","7":"bar","releases":[{"0":"5972","vim_version":"8.1","1":"8.1","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"vim-jqplay.tar.gz","4":"vim-jqplay.tar.gz","src_id":"27672","5":"27672","creation_date":"1627080688","6":"1627080688"}]},"5971":{"script_id":"5971","0":"5971","script_name":"vim-jq","1":"vim-jq","script_type":"ftplugin","2":"ftplugin","summary":"Runtime files for jq (the command-line JSON processor)","3":"Runtime files for jq (the command-line JSON processor)","description":"Vim runtime files for jq script files (the command-line JSON processor).\r\n\r\nSyntax highlighting of:\r\n\r\n - Builtin filters and user functions\r\n - Module prefix, like NAME::\r\n - Imported JSON file prefix, like $NAME::\r\n - Objects like .foo\r\n\r\nMappings:\r\n\r\n - Move to next\/previous function definition: ]], [[\r\n - Move to next\/previous nested function definition: ]m, [m\r\n - Enhanced gf: when pressed on an included module path foo\/bar edits the file foo\/bar.jq if the file can be found in Vim's 'path', \r\n otherwise tries to edit foo\/bar\/bar.jq.\r\n - Move between matching if\/elif\/else\/end, try\/catch, and function definition boundaries def\/; with %.\r\n\r\nInclude file searches:\r\n\r\n - Proper settings for include, includeexpr, suffixesadd and define.\r\n - Jq's default search paths for modules, ~\/.jq and $ORIGIN\/..\/lib\/jq are appended to 'path' only if they exist.\r\n\r\nhttps:\/\/github.com\/bfrg\/vim-jq","4":"Vim runtime files for jq script files (the command-line JSON processor).\r\n\r\nSyntax highlighting of:\r\n\r\n - Builtin filters and user functions\r\n - Module prefix, like NAME::\r\n - Imported JSON file prefix, like $NAME::\r\n - Objects like .foo\r\n\r\nMappings:\r\n\r\n - Move to next\/previous function definition: ]], [[\r\n - Move to next\/previous nested function definition: ]m, [m\r\n - Enhanced gf: when pressed on an included module path foo\/bar edits the file foo\/bar.jq if the file can be found in Vim's 'path', \r\n otherwise tries to edit foo\/bar\/bar.jq.\r\n - Move between matching if\/elif\/else\/end, try\/catch, and function definition boundaries def\/; with %.\r\n\r\nInclude file searches:\r\n\r\n - Proper settings for include, includeexpr, suffixesadd and define.\r\n - Jq's default search paths for modules, ~\/.jq and $ORIGIN\/..\/lib\/jq are appended to 'path' only if they exist.\r\n\r\nhttps:\/\/github.com\/bfrg\/vim-jq","install_details":"Run the following in your terminal:\r\n\r\n cd ~\/.vim\/pack\/git-plugins\/start\r\n git clone https:\/\/github.com\/bfrg\/vim-jq\r\n\r\nNote: The directory name git-plugins is arbitrary, you can pick any other name. For more details see :help packages.","5":"Run the following in your terminal:\r\n\r\n cd ~\/.vim\/pack\/git-plugins\/start\r\n git clone https:\/\/github.com\/bfrg\/vim-jq\r\n\r\nNote: The directory name git-plugins is arbitrary, you can pick any other name. For more details see :help packages.","first_name":"foo","6":"foo","last_name":"bar","7":"bar","releases":[{"0":"5971","vim_version":"7.4","1":"7.4","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"vim-jq.tar.gz","4":"vim-jq.tar.gz","src_id":"27671","5":"27671","creation_date":"1627080588","6":"1627080588"}]},"5970":{"script_id":"5970","0":"5970","script_name":"vim-qf-history","1":"vim-qf-history","script_type":"utility","2":"utility","summary":"Navigate the quickfix or location-list stack using a popup menu","3":"Navigate the quickfix or location-list stack using a popup menu","description":"Quickly navigate Vim's quickfix and location-list history using a popup menu.\r\n\r\nBackground:\r\n\r\nVim remembers the ten last used quickfix lists, and the ten last used location-lists for each window. The entire quickfix and location-list stack can be displayed with :chistory and :lhistory, respectively. Older quickfix lists are accessed through :colder and :cnewer, or directly with :[count]chistory (and similar for location-lists). See :help quickfix-error-lists for more details.\r\n\r\nThis plugin will display the quickfix and location-list stack in a popup menu allowing the user to easily switch to an earlier error list. If one of the lists contains different error types, the total number of each error type (E, W, I, N) is shown along with the total number of entries. Unknown error types are displayed in column \"?\", and empty lists are greyed out.\r\n\r\nCommands:\r\n\r\n :Chistory -- Display the quickfix history in a popup window and make the selected list the current list, similar to :[count]chistory.\r\n :Lhistory -- Same as above, but display the location-list history of the current window, similar to :[count]lhistory.\r\n\r\nAfter switching the quickfix or location list through the popup menu, the plugin triggers the QuickFixCmdPost event with the pattern \"chistory\" and \"lhistory\", respectively.\r\n\r\nhttps:\/\/github.com\/bfrg\/vim-qf-history","4":"Quickly navigate Vim's quickfix and location-list history using a popup menu.\r\n\r\nBackground:\r\n\r\nVim remembers the ten last used quickfix lists, and the ten last used location-lists for each window. The entire quickfix and location-list stack can be displayed with :chistory and :lhistory, respectively. Older quickfix lists are accessed through :colder and :cnewer, or directly with :[count]chistory (and similar for location-lists). See :help quickfix-error-lists for more details.\r\n\r\nThis plugin will display the quickfix and location-list stack in a popup menu allowing the user to easily switch to an earlier error list. If one of the lists contains different error types, the total number of each error type (E, W, I, N) is shown along with the total number of entries. Unknown error types are displayed in column \"?\", and empty lists are greyed out.\r\n\r\nCommands:\r\n\r\n :Chistory -- Display the quickfix history in a popup window and make the selected list the current list, similar to :[count]chistory.\r\n :Lhistory -- Same as above, but display the location-list history of the current window, similar to :[count]lhistory.\r\n\r\nAfter switching the quickfix or location list through the popup menu, the plugin triggers the QuickFixCmdPost event with the pattern \"chistory\" and \"lhistory\", respectively.\r\n\r\nhttps:\/\/github.com\/bfrg\/vim-qf-history","install_details":"Run the following commands in your terminal:\r\n\r\n cd ~\/.vim\/pack\/git-plugins\/start\r\n git clone https:\/\/github.com\/bfrg\/vim-qf-history\r\n vim -u NONE -c 'helptags vim-qf-history\/doc | quit'\r\n\r\nNote: The directory name git-plugins is arbitrary, you can pick any other name. For more details see :help packages. Alternatively, use your favorite plugin manager.","5":"Run the following commands in your terminal:\r\n\r\n cd ~\/.vim\/pack\/git-plugins\/start\r\n git clone https:\/\/github.com\/bfrg\/vim-qf-history\r\n vim -u NONE -c 'helptags vim-qf-history\/doc | quit'\r\n\r\nNote: The directory name git-plugins is arbitrary, you can pick any other name. For more details see :help packages. Alternatively, use your favorite plugin manager.","first_name":"foo","6":"foo","last_name":"bar","7":"bar","releases":[{"0":"5970","vim_version":"8.1","1":"8.1","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"vim-qf-history.tar.gz","4":"vim-qf-history.tar.gz","src_id":"27670","5":"27670","creation_date":"1627079276","6":"1627079276"}]},"5969":{"script_id":"5969","0":"5969","script_name":"vim-qf-preview","1":"vim-qf-preview","script_type":"utility","2":"utility","summary":"Preview the location of a quickfix item in a popup window","3":"Preview the location of a quickfix item in a popup window","description":"A plugin for the quickfix and location list window to quickly preview the location of the quickfix item under the cursor in a popup window.\r\n\r\nUsage:\r\n\r\nTo avoid conflicts with other plugins no default key mappings for opening the popup window are provided. You will first have to bind (qf-preview-open) to a key-sequence of your choice.\r\n\r\nFor example, to open the popup window with p, add the following to ~\/.vim\/after\/ftplugin\/qf.vim:\r\n\r\n nmap p (qf-preview-open)\r\n\r\nOr alternatively, if you prefer to keep your plugin settings in your vimrc:\r\n\r\n augroup qfpreview\r\n autocmd!\r\n autocmd FileType qf nmap p (qf-preview-open)\r\n augroup END\r\n\r\nNow navigate the cursor in the quickfix window to the desired quickfix item and press p to open a popup window with the file containing the error. The window is scrolled such that the buffer line with the error is at the top of the popup window.\r\n\r\nhttps:\/\/github.com\/bfrg\/vim-qf-preview","4":"A plugin for the quickfix and location list window to quickly preview the location of the quickfix item under the cursor in a popup window.\r\n\r\nUsage:\r\n\r\nTo avoid conflicts with other plugins no default key mappings for opening the popup window are provided. You will first have to bind (qf-preview-open) to a key-sequence of your choice.\r\n\r\nFor example, to open the popup window with p, add the following to ~\/.vim\/after\/ftplugin\/qf.vim:\r\n\r\n nmap p (qf-preview-open)\r\n\r\nOr alternatively, if you prefer to keep your plugin settings in your vimrc:\r\n\r\n augroup qfpreview\r\n autocmd!\r\n autocmd FileType qf nmap p (qf-preview-open)\r\n augroup END\r\n\r\nNow navigate the cursor in the quickfix window to the desired quickfix item and press p to open a popup window with the file containing the error. The window is scrolled such that the buffer line with the error is at the top of the popup window.\r\n\r\nhttps:\/\/github.com\/bfrg\/vim-qf-preview","install_details":"Run the following commands in the terminal:\r\n\r\n cd ~\/.vim\/pack\/git-plugins\/start\r\n git clone https:\/\/github.com\/bfrg\/vim-qf-preview\r\n vim -u NONE -c 'helptags vim-qf-preview\/doc | quit'\r\n\r\nNote: The directory name git-plugins is arbitrary, you can pick any other name. For more details see :help packages. Alternatively, use your favorite plugin manager.","5":"Run the following commands in the terminal:\r\n\r\n cd ~\/.vim\/pack\/git-plugins\/start\r\n git clone https:\/\/github.com\/bfrg\/vim-qf-preview\r\n vim -u NONE -c 'helptags vim-qf-preview\/doc | quit'\r\n\r\nNote: The directory name git-plugins is arbitrary, you can pick any other name. For more details see :help packages. Alternatively, use your favorite plugin manager.","first_name":"foo","6":"foo","last_name":"bar","7":"bar","releases":[{"0":"5969","vim_version":"8.1","1":"8.1","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"vim-qf-preview.tar.gz","4":"vim-qf-preview.tar.gz","src_id":"27669","5":"27669","creation_date":"1627078916","6":"1627078916"}]},"5968":{"script_id":"5968","0":"5968","script_name":"vim-fzy","1":"vim-fzy","script_type":"utility","2":"utility","summary":"Navigate projects using fzy in a (popup) terminal-window","3":"Navigate projects using fzy in a (popup) terminal-window","description":"Quickly navigate to files under a directory, jump to lines matching a pattern using grep, open buffers, tags generated by ctags, Vim's help tags, old files, and file marks using the fuzzy-searcher fzy [https:\/\/github.com\/jhawthorn\/fzy].\r\n\r\nThe terminal buffer can be displayed in a normal terminal window at the bottom of the screen or in a popup window.\r\n\r\nRequirements:\r\n\r\n - Vim >= 8.1.1828 (>= 8.2.0204 for popup terminal)\r\n - fzy [https:\/\/github.com\/jhawthorn\/fzy]\r\n - cut(1) (for the :FzyHelp command)\r\n - find(1) or similar (for the :FzyFind command)\r\n - grep(1) or similar (for the :FzyGrep command)\r\n\r\nCommands:\r\n\r\n :FzyFind [dir] \t-- Find files in [dir], edit selected file in the current window.\r\n :FzyGrep {args} \t-- Grep lines using pattern {args}, jump to selected location in the current window.\r\n :FzyBuffer \t\t-- List buffers, edit selected buffer in the current window.\r\n :FzyArgs \t\t-- List global arglist, edit selected file in the current window.\r\n :FzyLargs \t\t-- List local arglist, edit selected file in the current window.\r\n :FzyOldfiles \t-- List most recently used files, edit selected file in current window.\r\n :FzyTjump \t\t-- List tags, jump to selected tag in the current window.\r\n :FzyMarks \t\t-- List marks, jump to the selected mark in the current window.\r\n :FzyHelp \t\t-- List help tags, open help page with the selected tag in a new split.\r\n\r\nEach command has a related command that opens the selected item in a new split, like :FzyBufferSplit. These commands accept a command modifier. For example, to open a buffer in a new vertical split, run :vert FzyBufferSplit, :tab FzyBufferSplit will open the selected buffer in a new tab. For a full list of supported command modifiers, see :help fzy-commands-split.\r\n\r\nCustom commands:\r\n\r\nInternally, all above commands call the fzy#start() function to pass the items to fzy in a terminal window. The function is thoroughly documented in :help fzy-api. Examples on how to write your own commands that invoke fzy can be found in :help fzy-api-examples.\r\n\r\nhttps:\/\/github.com\/bfrg\/vim-fzy","4":"Quickly navigate to files under a directory, jump to lines matching a pattern using grep, open buffers, tags generated by ctags, Vim's help tags, old files, and file marks using the fuzzy-searcher fzy [https:\/\/github.com\/jhawthorn\/fzy].\r\n\r\nThe terminal buffer can be displayed in a normal terminal window at the bottom of the screen or in a popup window.\r\n\r\nRequirements:\r\n\r\n - Vim >= 8.1.1828 (>= 8.2.0204 for popup terminal)\r\n - fzy [https:\/\/github.com\/jhawthorn\/fzy]\r\n - cut(1) (for the :FzyHelp command)\r\n - find(1) or similar (for the :FzyFind command)\r\n - grep(1) or similar (for the :FzyGrep command)\r\n\r\nCommands:\r\n\r\n :FzyFind [dir] \t-- Find files in [dir], edit selected file in the current window.\r\n :FzyGrep {args} \t-- Grep lines using pattern {args}, jump to selected location in the current window.\r\n :FzyBuffer \t\t-- List buffers, edit selected buffer in the current window.\r\n :FzyArgs \t\t-- List global arglist, edit selected file in the current window.\r\n :FzyLargs \t\t-- List local arglist, edit selected file in the current window.\r\n :FzyOldfiles \t-- List most recently used files, edit selected file in current window.\r\n :FzyTjump \t\t-- List tags, jump to selected tag in the current window.\r\n :FzyMarks \t\t-- List marks, jump to the selected mark in the current window.\r\n :FzyHelp \t\t-- List help tags, open help page with the selected tag in a new split.\r\n\r\nEach command has a related command that opens the selected item in a new split, like :FzyBufferSplit. These commands accept a command modifier. For example, to open a buffer in a new vertical split, run :vert FzyBufferSplit, :tab FzyBufferSplit will open the selected buffer in a new tab. For a full list of supported command modifiers, see :help fzy-commands-split.\r\n\r\nCustom commands:\r\n\r\nInternally, all above commands call the fzy#start() function to pass the items to fzy in a terminal window. The function is thoroughly documented in :help fzy-api. Examples on how to write your own commands that invoke fzy can be found in :help fzy-api-examples.\r\n\r\nhttps:\/\/github.com\/bfrg\/vim-fzy","install_details":"Run the following in the terminal:\r\n\r\n cd ~\/.vim\/pack\/git-plugins\/start\r\n git clone https:\/\/github.com\/bfrg\/vim-fzy\r\n vim -u NONE -c 'helptags vim-fzy\/doc | quit'\r\n\r\nNote: The directory name git-plugins is arbitrary, you can pick any other name. For more details see :help packages.\r\n\r\nAlternatively, use your favorite plugin manager.","5":"Run the following in the terminal:\r\n\r\n cd ~\/.vim\/pack\/git-plugins\/start\r\n git clone https:\/\/github.com\/bfrg\/vim-fzy\r\n vim -u NONE -c 'helptags vim-fzy\/doc | quit'\r\n\r\nNote: The directory name git-plugins is arbitrary, you can pick any other name. For more details see :help packages.\r\n\r\nAlternatively, use your favorite plugin manager.","first_name":"foo","6":"foo","last_name":"bar","7":"bar","releases":[{"0":"5968","vim_version":"8.1","1":"8.1","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"vim-fzy.tar.gz","4":"vim-fzy.tar.gz","src_id":"27668","5":"27668","creation_date":"1627078018","6":"1627078018"}]},"5967":{"script_id":"5967","0":"5967","script_name":"vim-cmake-help","1":"vim-cmake-help","script_type":"ftplugin","2":"ftplugin","summary":"View CMake Documentation inside Vim ","3":"View CMake Documentation inside Vim ","description":"View CMake documentation inside Vim (>= 8.1.2250).\r\n\r\nThe plugin provides three methods for quickly displaying CMake documentation:\r\n\r\n - Open the documentation in a new split window.\r\n - Open the documentation in a popup window at the current cursor position (or mouse pointer using a balloonexpr).\r\n - Open the CMake reference documentation directly in your browser.\r\n\r\nhttps:\/\/github.com\/bfrg\/vim-cmake-help","4":"View CMake documentation inside Vim (>= 8.1.2250).\r\n\r\nThe plugin provides three methods for quickly displaying CMake documentation:\r\n\r\n - Open the documentation in a new split window.\r\n - Open the documentation in a popup window at the current cursor position (or mouse pointer using a balloonexpr).\r\n - Open the CMake reference documentation directly in your browser.\r\n\r\nhttps:\/\/github.com\/bfrg\/vim-cmake-help","install_details":"Run the following in the terminal:\r\n\r\n cd ~\/.vim\/pack\/git-plugins\/start\r\n git clone https:\/\/github.com\/bfrg\/vim-cmake-help\r\n vim -u NONE -c 'helptags vim-cmake-help\/doc | quit'\r\n\r\nNote: The directory name git-plugins is arbitrary, you can pick any other name. For more details see :help packages.\r\n\r\nAlternatively, use your favorite plugin manager.","5":"Run the following in the terminal:\r\n\r\n cd ~\/.vim\/pack\/git-plugins\/start\r\n git clone https:\/\/github.com\/bfrg\/vim-cmake-help\r\n vim -u NONE -c 'helptags vim-cmake-help\/doc | quit'\r\n\r\nNote: The directory name git-plugins is arbitrary, you can pick any other name. For more details see :help packages.\r\n\r\nAlternatively, use your favorite plugin manager.","first_name":"foo","6":"foo","last_name":"bar","7":"bar","releases":[{"0":"5967","vim_version":"8.1","1":"8.1","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"vim-cmake-help.tar.gz","4":"vim-cmake-help.tar.gz","src_id":"27667","5":"27667","creation_date":"1627076966","6":"1627076966"}]},"5966":{"script_id":"5966","0":"5966","script_name":"vim-cuda-syntax","1":"vim-cuda-syntax","script_type":"syntax","2":"syntax","summary":"CUDA syntax highlighting for Vim ","3":"CUDA syntax highlighting for Vim ","description":"Syntax highlighting for CUDA in Vim. Compared to Vim's default CUDA syntax file, it adds highlighting of all CUDA defined:\r\n\r\n- types\r\n- enums\r\n- constants\r\n- global variables\r\n- namespaces\r\n- thrust keywords\r\n\r\nAll keywords are accumulated from the CUDA Toolkit Documentation.\r\n\r\nOptionally triple-angle brackets in CUDA kernel calls can be highlighted.\r\n\r\nhttps:\/\/github.com\/bfrg\/vim-cuda-syntax","4":"Syntax highlighting for CUDA in Vim. Compared to Vim's default CUDA syntax file, it adds highlighting of all CUDA defined:\r\n\r\n- types\r\n- enums\r\n- constants\r\n- global variables\r\n- namespaces\r\n- thrust keywords\r\n\r\nAll keywords are accumulated from the CUDA Toolkit Documentation.\r\n\r\nOptionally triple-angle brackets in CUDA kernel calls can be highlighted.\r\n\r\nhttps:\/\/github.com\/bfrg\/vim-cuda-syntax","install_details":"Run the following in the terminal:\r\n\r\ncd ~\/.vim\/pack\/git-plugins\/start\r\ngit clone https:\/\/github.com\/bfrg\/vim-cuda-syntax\r\n\r\nNote: The directory name git-plugins is arbitrary, you can pick any other name. For more details see :help packages.\r\n\r\nAlternatively, use your favorite plugin manager.","5":"Run the following in the terminal:\r\n\r\ncd ~\/.vim\/pack\/git-plugins\/start\r\ngit clone https:\/\/github.com\/bfrg\/vim-cuda-syntax\r\n\r\nNote: The directory name git-plugins is arbitrary, you can pick any other name. For more details see :help packages.\r\n\r\nAlternatively, use your favorite plugin manager.","first_name":"foo","6":"foo","last_name":"bar","7":"bar","releases":[{"0":"5966","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"vim-cuda-syntax.tar.gz","4":"vim-cuda-syntax.tar.gz","src_id":"27666","5":"27666","creation_date":"1627076588","6":"1627076588"}]},"5965":{"script_id":"5965","0":"5965","script_name":"vim-cpp-modern","1":"vim-cpp-modern","script_type":"syntax","2":"syntax","summary":"Extended syntax highlighting for C and C++ (C++11\/14\/17\/20)","3":"Extended syntax highlighting for C and C++ (C++11\/14\/17\/20)","description":"Keyword and regex-based syntax highlighting for C and C++11\/14\/17\/20 in Vim.\r\n\r\nThe syntax files provide highlighting of:\r\n\r\n- Common ANSI C keywords\r\n- C++ standard library namespaces, types, helper types, helper template variables, and constants\r\n- C++11 attributes\r\n- Latest C++20 language features like coroutines and concepts\r\n- Function declarations\/definitions and function calls (basically all words followed by an opening parenthesis)\r\n- Optionally a simpler (less colorful) highlighting of standard C and C++ keywords\r\n\r\nhttps:\/\/github.com\/bfrg\/vim-cpp-modern","4":"Keyword and regex-based syntax highlighting for C and C++11\/14\/17\/20 in Vim.\r\n\r\nThe syntax files provide highlighting of:\r\n\r\n- Common ANSI C keywords\r\n- C++ standard library namespaces, types, helper types, helper template variables, and constants\r\n- C++11 attributes\r\n- Latest C++20 language features like coroutines and concepts\r\n- Function declarations\/definitions and function calls (basically all words followed by an opening parenthesis)\r\n- Optionally a simpler (less colorful) highlighting of standard C and C++ keywords\r\n\r\nhttps:\/\/github.com\/bfrg\/vim-cpp-modern","install_details":"Run the following in the terminal:\r\n\r\ncd ~\/.vim\/pack\/git-plugins\/start\r\ngit clone --depth=1 https:\/\/github.com\/bfrg\/vim-cpp-modern\r\n\r\nThe directory name git-plugins is arbitrary, any other name can be picked. See :help packages for more details.","5":"Run the following in the terminal:\r\n\r\ncd ~\/.vim\/pack\/git-plugins\/start\r\ngit clone --depth=1 https:\/\/github.com\/bfrg\/vim-cpp-modern\r\n\r\nThe directory name git-plugins is arbitrary, any other name can be picked. See :help packages for more details.","first_name":"foo","6":"foo","last_name":"bar","7":"bar","releases":[{"0":"5965","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"vim-cpp-modern.tar.gz","4":"vim-cpp-modern.tar.gz","src_id":"27665","5":"27665","creation_date":"1627076267","6":"1627076267"}]},"5964":{"script_id":"5964","0":"5964","script_name":"viora.vim","1":"viora.vim","script_type":"utility","2":"utility","summary":"Access Oracle from Vim","3":"Access Oracle from Vim","description":"This script shall be used when one writes PL\/SQL for Oracle in vim and wants to have\r\nquick and convenient way to test things out, or simply see results of queries.\r\n\r\nIt takes queries directly from buffer. One can configure delimiters for that. Results are shown in separate buffer. In case of error, the script attempts to position cursor to the first error. For PL\/SQL Quickfix mode is used, to mark positions of all errors.\r\n","4":"This script shall be used when one writes PL\/SQL for Oracle in vim and wants to have\r\nquick and convenient way to test things out, or simply see results of queries.\r\n\r\nIt takes queries directly from buffer. One can configure delimiters for that. Results are shown in separate buffer. In case of error, the script attempts to position cursor to the first error. For PL\/SQL Quickfix mode is used, to mark positions of all errors.\r\n","install_details":"Unpack archive into your .vim directory. Start vim and run\r\n\r\n:helptags ALL\r\n\r\nto update tags file for help.\r\n\r\nThe module is written in perl, so this interpreter should be compiled into vim. Also one should have perl modules DBI and DBD::Oracle installed.\r\n\r\nAfter installation, run\r\n\r\n:h viora\r\n\r\nto see all details about usage and configuration","5":"Unpack archive into your .vim directory. Start vim and run\r\n\r\n:helptags ALL\r\n\r\nto update tags file for help.\r\n\r\nThe module is written in perl, so this interpreter should be compiled into vim. Also one should have perl modules DBI and DBD::Oracle installed.\r\n\r\nAfter installation, run\r\n\r\n:h viora\r\n\r\nto see all details about usage and configuration","first_name":"Andrey","6":"Andrey","last_name":"Voropaev","7":"Voropaev","releases":[{"0":"5964","vim_version":"7.0","1":"7.0","script_version":"4","2":"4","version_comment":"Fixed problem with recognizing query on the very first line of buffer\r\n\r\nFixed searching for error position if perl variables are in use in query","3":"Fixed problem with recognizing query on the very first line of buffer\r\n\r\nFixed searching for error position if perl variables are in use in query","package":"viora-4.tar.bz2","4":"viora-4.tar.bz2","src_id":"27784","5":"27784","creation_date":"1634849003","6":"1634849003"},{"0":"5964","vim_version":"7.0","1":"7.0","script_version":"3","2":"3","version_comment":"Added check for validity of DB connection\r\n\r\nFixed problem with query as last line in the buffer","3":"Added check for validity of DB connection\r\n\r\nFixed problem with query as last line in the buffer","package":"viora-3.tar.bz2","4":"viora-3.tar.bz2","src_id":"27746","5":"27746","creation_date":"1632411978","6":"1632411978"},{"0":"5964","vim_version":"7.0","1":"7.0","script_version":"2.0","2":"2.0","version_comment":"Added support for perl variables in SQL. Also number of affected rows is reported, where available. It is not available for SELECT!","3":"Added support for perl variables in SQL. Also number of affected rows is reported, where available. It is not available for SELECT!","package":"viora.tar.bz2","4":"viora.tar.bz2","src_id":"27742","5":"27742","creation_date":"1631662979","6":"1631662979"},{"0":"5964","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"viora.tar.bz2","4":"viora.tar.bz2","src_id":"27664","5":"27664","creation_date":"1627007053","6":"1627007053"}]},"5963":{"script_id":"5963","0":"5963","script_name":"vimwintab","1":"vimwintab","script_type":"utility","2":"utility","summary":"\"IDE-like\" tabs in Vim","3":"\"IDE-like\" tabs in Vim","description":"In Vim, we don\\'t really have tabs in its regular meaning. Vim tabs encompass windows, but don\\'t show what files are opened in these windows. So, long story short, vimwintab plugin adds to Vim a functionality of regular tabs that you can find in many text editors. Hence the name - \\\"Vim Windows Tabs\\\".\r\n\r\nEach tab represents a buffer associated with a window. Multiple windows may have the same buffer opened as a tab. At one point of time any window may have one current tab, with the represented buffer displayed in the window. Current tab may be switched to the left or right one, and if you try to go beyond any end of the tab bar it will wrap.\r\n\r\nNavigation between tabs is not interconnected with the buffer list and is done via plugin\\'s own commands.\r\n\r\nTabs are added to windows according to the mode the plugin operates in. There are several of those, each of them provides different detection patterns which the plugin will follow to determine if a buffer needs to be added to a tab bar.\r\n\r\nIn general, plugin is very customizable - you can determine, how it will operate, in which mode, how individual tabs will look like, etc. \r\n\r\nPlease visit the plugin\\'s wiki to find User Guide, Customization Guide, and other useful information - https:\/\/github.com\/boson-joe\/vimwintab\/wiki .\r\nPlugin itself and its documentation could be downloaded directly from GitHub - https:\/\/github.com\/boson-joe\/vimwintab . ","4":"In Vim, we don\\'t really have tabs in its regular meaning. Vim tabs encompass windows, but don\\'t show what files are opened in these windows. So, long story short, vimwintab plugin adds to Vim a functionality of regular tabs that you can find in many text editors. Hence the name - \\\"Vim Windows Tabs\\\".\r\n\r\nEach tab represents a buffer associated with a window. Multiple windows may have the same buffer opened as a tab. At one point of time any window may have one current tab, with the represented buffer displayed in the window. Current tab may be switched to the left or right one, and if you try to go beyond any end of the tab bar it will wrap.\r\n\r\nNavigation between tabs is not interconnected with the buffer list and is done via plugin\\'s own commands.\r\n\r\nTabs are added to windows according to the mode the plugin operates in. There are several of those, each of them provides different detection patterns which the plugin will follow to determine if a buffer needs to be added to a tab bar.\r\n\r\nIn general, plugin is very customizable - you can determine, how it will operate, in which mode, how individual tabs will look like, etc. \r\n\r\nPlease visit the plugin\\'s wiki to find User Guide, Customization Guide, and other useful information - https:\/\/github.com\/boson-joe\/vimwintab\/wiki .\r\nPlugin itself and its documentation could be downloaded directly from GitHub - https:\/\/github.com\/boson-joe\/vimwintab . ","install_details":"Requirements\r\n\r\nTo make sure the plugin works properly, we suggest you to check that your Vim has version 8.2 or higher (`:echo v:version >= 802` should print out 1), has `popupwin` option set during compilation (`:echo has(\\\"popupwin\\\")` should print out 1), and `compatible` option is off (`:echo &compatible` should print out 0).\r\n\r\n\r\nManual\r\n\r\nYou can install the plugin by simply putting the files of the plugin in `plugin` folder in your `.vim` directory. One of the commands that could be used is `wget`. Type this in your terminal:\r\n\r\nwget https:\/\/github.com\/boson-joe\/vimwintab\/blob\/master\/plugin\/vimwintab.vim\r\n\r\nTo have documentation, do the same with files in doc\/ directory - you need to put them into doc\/ directory in your .vim directory.\r\n\r\n\r\nPlugin manager\r\n\r\nYou may find plugin managers convenient to install and manage plugins you want in your Vim, including vimwintab.\r\n\r\nvim-plug - https:\/\/github.com\/junegunn\/vim-plug\r\n\r\nIf you are using vim-plug plugin manager, refer to their manual (https:\/\/github.com\/junegunn\/vim-plug#usage).\r\n\r\nVundle - https:\/\/github.com\/VundleVim\/Vundle.vim\r\n\r\nVundle plugin manager seems to require `filetype off`, which is desirable, though not required, to be `on` for vimwintab smooth operation, so we are not describing the procedure here.\r\n\r\nPathogen - https:\/\/github.com\/tpope\/vim-pathogen\r\n\r\nIf you are using Pathogen plugin manager, refer to their manual here(https:\/\/github.com\/tpope\/vim-pathogen#installation).","5":"Requirements\r\n\r\nTo make sure the plugin works properly, we suggest you to check that your Vim has version 8.2 or higher (`:echo v:version >= 802` should print out 1), has `popupwin` option set during compilation (`:echo has(\\\"popupwin\\\")` should print out 1), and `compatible` option is off (`:echo &compatible` should print out 0).\r\n\r\n\r\nManual\r\n\r\nYou can install the plugin by simply putting the files of the plugin in `plugin` folder in your `.vim` directory. One of the commands that could be used is `wget`. Type this in your terminal:\r\n\r\nwget https:\/\/github.com\/boson-joe\/vimwintab\/blob\/master\/plugin\/vimwintab.vim\r\n\r\nTo have documentation, do the same with files in doc\/ directory - you need to put them into doc\/ directory in your .vim directory.\r\n\r\n\r\nPlugin manager\r\n\r\nYou may find plugin managers convenient to install and manage plugins you want in your Vim, including vimwintab.\r\n\r\nvim-plug - https:\/\/github.com\/junegunn\/vim-plug\r\n\r\nIf you are using vim-plug plugin manager, refer to their manual (https:\/\/github.com\/junegunn\/vim-plug#usage).\r\n\r\nVundle - https:\/\/github.com\/VundleVim\/Vundle.vim\r\n\r\nVundle plugin manager seems to require `filetype off`, which is desirable, though not required, to be `on` for vimwintab smooth operation, so we are not describing the procedure here.\r\n\r\nPathogen - https:\/\/github.com\/tpope\/vim-pathogen\r\n\r\nIf you are using Pathogen plugin manager, refer to their manual here(https:\/\/github.com\/tpope\/vim-pathogen#installation).","first_name":"boson","6":"boson","last_name":"joe","7":"joe","releases":[{"0":"5963","vim_version":"8.2","1":"8.2","script_version":"1.0.1","2":"1.0.1","version_comment":"vimwintab (v. 1.0.1), with documentation and license.","3":"vimwintab (v. 1.0.1), with documentation and license.","package":"vimwintab.tar.xz","4":"vimwintab.tar.xz","src_id":"27694","5":"27694","creation_date":"1628127041","6":"1628127041"},{"0":"5963","vim_version":"8.2","1":"8.2","script_version":"1.0.1","2":"1.0.1","version_comment":"Additional guards added against multiple sources of the script. ","3":"Additional guards added against multiple sources of the script. ","package":"vimwintab.vim","4":"vimwintab.vim","src_id":"27693","5":"27693","creation_date":"1628126953","6":"1628126953"},{"0":"5963","vim_version":"8.2","1":"8.2","script_version":"1.0.0","2":"1.0.0","version_comment":"vimwintab (v. 1.0.0), with documentation and license.","3":"vimwintab (v. 1.0.0), with documentation and license.","package":"vimwintab.tar.xz","4":"vimwintab.tar.xz","src_id":"27654","5":"27654","creation_date":"1626200802","6":"1626200802"},{"0":"5963","vim_version":"8.2","1":"8.2","script_version":"1.0.0","2":"1.0.0","version_comment":"Initial upload","3":"Initial upload","package":"vimwintab.vim","4":"vimwintab.vim","src_id":"27653","5":"27653","creation_date":"1626130781","6":"1626130781"}]},"5962":{"script_id":"5962","0":"5962","script_name":"doas.conf syntax","1":"doas.conf syntax","script_type":"syntax","2":"syntax","summary":"Syntax Highlighting for doas.conf(5)","3":"Syntax Highlighting for doas.conf(5)","description":"doasconf.vim highlights configuration files for doas, a simpler and safer sudo replacement","4":"doasconf.vim highlights configuration files for doas, a simpler and safer sudo replacement","install_details":"Download doasconf.vim to ~\/.vim\/syntax\/, and then add this line to ~\/.vim\/ftdetect\/doasconf.vim:\r\n\r\nau BufNewFile,BufRead doas.conf set filetype=doasconf","5":"Download doasconf.vim to ~\/.vim\/syntax\/, and then add this line to ~\/.vim\/ftdetect\/doasconf.vim:\r\n\r\nau BufNewFile,BufRead doas.conf set filetype=doasconf","first_name":"Anna","6":"Anna","last_name":"\"CyberTailor\"","7":"\"CyberTailor\"","releases":[{"0":"5962","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"doasconf.vim","4":"doasconf.vim","src_id":"27652","5":"27652","creation_date":"1626029091","6":"1626029091"}]},"5961":{"script_id":"5961","0":"5961","script_name":"vsh","1":"vsh","script_type":"ftplugin","2":"ftplugin","summary":"vim shell, https:\/\/github.com\/zetatez\/vsh","3":"vim shell, https:\/\/github.com\/zetatez\/vsh","description":"# VSH \r\n\r\nVSH is a vim shell, a vim plugin! It's elegant and efficient.\r\n\r\nWith VSH, we can take full advantage of the vim to interact with the terminal. For example, we can extend `vsh` with [ultisnips](https:\/\/github.com\/SirVer\/ultisnips) plugin by creating a bunch of snippets to achieve our own auto-completion.\r\n\r\n[BiliBili](https:\/\/b23.tv\/437IxV)\r\n\r\n![vsh](https:\/\/raw.githubusercontent.com\/zetatez\/vsh\/main\/pic\/20210627022724.png)\r\n\r\n[Github](https:\/\/github.com\/zetatez\/vsh)","4":"# VSH \r\n\r\nVSH is a vim shell, a vim plugin! It's elegant and efficient.\r\n\r\nWith VSH, we can take full advantage of the vim to interact with the terminal. For example, we can extend `vsh` with [ultisnips](https:\/\/github.com\/SirVer\/ultisnips) plugin by creating a bunch of snippets to achieve our own auto-completion.\r\n\r\n[BiliBili](https:\/\/b23.tv\/437IxV)\r\n\r\n![vsh](https:\/\/raw.githubusercontent.com\/zetatez\/vsh\/main\/pic\/20210627022724.png)\r\n\r\n[Github](https:\/\/github.com\/zetatez\/vsh)","install_details":"### Installation\r\n- vim-plug is required, add following lines to your vim-plug session of your vimrc file.\r\n```vim\r\n\"\"\"\"\"\"\r\n\"\"\"\"\"\" vsh\r\nplug \"zetatez\/vsh\"\r\n\" let g:vsh_send_line = \"\"\r\n\" let g:vsh_send_selection= \"\"\r\n\" let g:vsh_exit = \"\"\r\n\" let g:vsh_exit_cmd = \"qq\"\r\n\r\n\"\"\"\"\"\"\r\n\"\"\"\"\"\" optional: snippets\r\nPlug 'SirVer\/ultisnips'\r\nPlug 'honza\/vim-snippets'\r\n\" Trigger configuration. You need to change this to something other than <\\> if you use one of the following:\r\n\" - https:\/\/github.com\/Valloric\/YouCompleteMe\r\n\" - https:\/\/github.com\/nvim-lua\/completion-nvim\r\nlet g:UltiSnipsExpandTrigger = ''\r\nlet g:UltiSnipsJumpForwardTrigger = ''\r\nlet g:UltiSnipsJumpBackwardTrigger = ''\r\nlet g:UltiSnipsEditSplit='vertical'\r\nlet g:UltiSnipsSnippetDirectories = ['~\/.ultisnips\/']\r\n```\r\nthen\r\n```bash\r\nvim +PlugInstall\r\n```\r\n\r\n- install vsh cli tool\r\n```bash\r\ngit clone git@github.com:zetatez\/vsh.git\r\ncd vsh\r\n\r\n# vsh\r\nsudo make install\r\n\r\n# optional: ultisnips\r\nmkdir ~\/.ultisnips\r\ncp vsh.snippets ~\/.ultisnips\/\r\n```\r\n\r\n### Usage\r\nHere we go !\r\n```bash\r\nvsh\r\n\r\n```\r\n\r\nHints,\r\n```\r\nnormal mode, `` send current line to the terminal\r\nvisual mode, `` send selected lines to the terminal\r\nnormal mode, `` quit vsh\r\ncli mode, `:qq` quit vsh\r\n```\r\n\r\n### One more tip !\r\n- Try to use [ultisnips](https:\/\/github.com\/SirVer\/ultisnips) plugin to create some your own snippets. \r\n\r\n","5":"### Installation\r\n- vim-plug is required, add following lines to your vim-plug session of your vimrc file.\r\n```vim\r\n\"\"\"\"\"\"\r\n\"\"\"\"\"\" vsh\r\nplug \"zetatez\/vsh\"\r\n\" let g:vsh_send_line = \"\"\r\n\" let g:vsh_send_selection= \"\"\r\n\" let g:vsh_exit = \"\"\r\n\" let g:vsh_exit_cmd = \"qq\"\r\n\r\n\"\"\"\"\"\"\r\n\"\"\"\"\"\" optional: snippets\r\nPlug 'SirVer\/ultisnips'\r\nPlug 'honza\/vim-snippets'\r\n\" Trigger configuration. You need to change this to something other than <\\> if you use one of the following:\r\n\" - https:\/\/github.com\/Valloric\/YouCompleteMe\r\n\" - https:\/\/github.com\/nvim-lua\/completion-nvim\r\nlet g:UltiSnipsExpandTrigger = ''\r\nlet g:UltiSnipsJumpForwardTrigger = ''\r\nlet g:UltiSnipsJumpBackwardTrigger = ''\r\nlet g:UltiSnipsEditSplit='vertical'\r\nlet g:UltiSnipsSnippetDirectories = ['~\/.ultisnips\/']\r\n```\r\nthen\r\n```bash\r\nvim +PlugInstall\r\n```\r\n\r\n- install vsh cli tool\r\n```bash\r\ngit clone git@github.com:zetatez\/vsh.git\r\ncd vsh\r\n\r\n# vsh\r\nsudo make install\r\n\r\n# optional: ultisnips\r\nmkdir ~\/.ultisnips\r\ncp vsh.snippets ~\/.ultisnips\/\r\n```\r\n\r\n### Usage\r\nHere we go !\r\n```bash\r\nvsh\r\n\r\n```\r\n\r\nHints,\r\n```\r\nnormal mode, `` send current line to the terminal\r\nvisual mode, `` send selected lines to the terminal\r\nnormal mode, `` quit vsh\r\ncli mode, `:qq` quit vsh\r\n```\r\n\r\n### One more tip !\r\n- Try to use [ultisnips](https:\/\/github.com\/SirVer\/ultisnips) plugin to create some your own snippets. \r\n\r\n","first_name":"Lorenzo","6":"Lorenzo","last_name":"F","7":"F","releases":[{"0":"5961","vim_version":"8.2","1":"8.2","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"vsh.tar","4":"vsh.tar","src_id":"27640","5":"27640","creation_date":"1625142726","6":"1625142726"}]},"5960":{"script_id":"5960","0":"5960","script_name":"FZF-Ack-Project","1":"FZF-Ack-Project","script_type":"ftplugin","2":"ftplugin","summary":"Auxiliary tools of FZF&Ack","3":"Auxiliary tools of FZF&Ack","description":"When using FZF\/Ack\r\n\r\nDetermine the project root directory according to the project identification file :)","4":"When using FZF\/Ack\r\n\r\nDetermine the project root directory according to the project identification file :)","install_details":"","5":"","first_name":"ojer","6":"ojer","last_name":".","7":".","releases":[{"0":"5960","vim_version":"7.0","1":"7.0","script_version":"1.1","2":"1.1","version_comment":"modify file retrieval method","3":"modify file retrieval method","package":"FZF-Ack-Project.tar.gz","4":"FZF-Ack-Project.tar.gz","src_id":"27643","5":"27643","creation_date":"1625239177","6":"1625239177"}]},"5959":{"script_id":"5959","0":"5959","script_name":"smartq","1":"smartq","script_type":"utility","2":"utility","summary":"Master key for quitting vim buffers","3":"Master key for quitting vim buffers","description":"Sensibly close buffers with respect to tabs and window splits, and other types of buffer.\r\n\r\nhttps:\/\/github.com\/marklcrns\/vim-smartq","4":"Sensibly close buffers with respect to tabs and window splits, and other types of buffer.\r\n\r\nhttps:\/\/github.com\/marklcrns\/vim-smartq","install_details":"Plug and play. Extract then place files in ~\/.vim\r\n\r\nor follow the instructions in the official repo: https:\/\/github.com\/marklcrns\/vim-smartq#installation using package managers","5":"Plug and play. Extract then place files in ~\/.vim\r\n\r\nor follow the instructions in the official repo: https:\/\/github.com\/marklcrns\/vim-smartq#installation using package managers","first_name":"Mark","6":"Mark","last_name":"Lucernas","7":"Lucernas","releases":[{"0":"5959","vim_version":"7.0","1":"7.0","script_version":"v1.4","2":"v1.4","version_comment":"- Add folke\/zen-mode.nvim support\r\n- Add g:smartq_goyo_integration\r\n- Add g:smartq_zenmode_integration\r\n- Improve Goyo support","3":"- Add folke\/zen-mode.nvim support\r\n- Add g:smartq_goyo_integration\r\n- Add g:smartq_zenmode_integration\r\n- Improve Goyo support","package":"vim-smartq-1.4.tar.gz","4":"vim-smartq-1.4.tar.gz","src_id":"28163","5":"28163","creation_date":"1662362227","6":"1662362227"},{"0":"5959","vim_version":"7.0","1":"7.0","script_version":"v1.3","2":"v1.3","version_comment":"- Add floating window support (neovim only)\r\n- Silenced all command execution\r\n- Add more global variables config\r\n - g:smartq_auto_wipe_emtpy\r\n - g:smartq_auto_close_splits\r\n - g:g:smartq_no_exit\r\n- Improved smartq quit prioritization\r\n- Better echo logging system","3":"- Add floating window support (neovim only)\r\n- Silenced all command execution\r\n- Add more global variables config\r\n - g:smartq_auto_wipe_emtpy\r\n - g:smartq_auto_close_splits\r\n - g:g:smartq_no_exit\r\n- Improved smartq quit prioritization\r\n- Better echo logging system","package":"vim-smartq-1.3.tar.gz","4":"vim-smartq-1.3.tar.gz","src_id":"28162","5":"28162","creation_date":"1662362208","6":"1662362208"},{"0":"5959","vim_version":"7.0","1":"7.0","script_version":"1.2","2":"1.2","version_comment":"Completely preserve splits. Add buftype support.\r\n\r\n- Splits are preserved to the final non-empty buffer.\r\n- Add options to exclude and include buftype\r\n- All splits collapse on the last empty modifiable buffer, else quit vim regardless of other non-modifiable splits\r\n- Auto wipe empty buffers when deleting\/wiping a buffer\r\n- Bug fixes","3":"Completely preserve splits. Add buftype support.\r\n\r\n- Splits are preserved to the final non-empty buffer.\r\n- Add options to exclude and include buftype\r\n- All splits collapse on the last empty modifiable buffer, else quit vim regardless of other non-modifiable splits\r\n- Auto wipe empty buffers when deleting\/wiping a buffer\r\n- Bug fixes","package":"vim-smartq-1.2.tar.gz","4":"vim-smartq-1.2.tar.gz","src_id":"27648","5":"27648","creation_date":"1625726871","6":"1625726871"},{"0":"5959","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"New Features\r\n\r\n- Add bang (!) support for SmartQ and SmartQWipeEmpty.\r\n - SmartQ! and SmartQWipeEmpty! force delete\/wipe\/close buffers.\r\n- SmartQ(!) now accepts one optional args to manually delete buffer\r\n - Accepts both bufname or bufnr. Also supports tab completion.\r\n - e.q. SmartQ autoload\/smartq.vim\r\n - e.q. SmartQ! 1\r\n- Add s:new_tmp_buf() for creating temporary buffer that self-destructs.\r\n- Create LICENCE\r\n\r\nFixes\r\n\r\n- Fix non-empty unspecified readonly buffer from using :q to :bd\r\n\r\nMisc\r\n\r\n- Remove g:smartq_bd_filetypes and make it default\r\n- Update default global settings\r\n- Use default let variable inside functions instead of let s:variable\r\n- Snakecase script functions.\r\n- Update README\r\n- Add MIT LICENSE","3":"New Features\r\n\r\n- Add bang (!) support for SmartQ and SmartQWipeEmpty.\r\n - SmartQ! and SmartQWipeEmpty! force delete\/wipe\/close buffers.\r\n- SmartQ(!) now accepts one optional args to manually delete buffer\r\n - Accepts both bufname or bufnr. Also supports tab completion.\r\n - e.q. SmartQ autoload\/smartq.vim\r\n - e.q. SmartQ! 1\r\n- Add s:new_tmp_buf() for creating temporary buffer that self-destructs.\r\n- Create LICENCE\r\n\r\nFixes\r\n\r\n- Fix non-empty unspecified readonly buffer from using :q to :bd\r\n\r\nMisc\r\n\r\n- Remove g:smartq_bd_filetypes and make it default\r\n- Update default global settings\r\n- Use default let variable inside functions instead of let s:variable\r\n- Snakecase script functions.\r\n- Update README\r\n- Add MIT LICENSE","package":"vim-smartq.tar.gz","4":"vim-smartq.tar.gz","src_id":"27632","5":"27632","creation_date":"1623683016","6":"1623683016"},{"0":"5959","vim_version":"7.0","1":"7.0","script_version":"0.2","2":"0.2","version_comment":"feat(smartq): First major update\r\n\r\nGeneral\r\n\r\n- Modularize script\r\n - Moved all functions in autoload dir\r\n- Add default mappings\r\n- Add SmartQCloseSplits\r\n- Add SmartQWipeEmpty\r\n - Remove auto wipe empty buffers feature\r\n\r\nSmartQ\r\n\r\n- Fix filetype detection\r\n- Add option to delete buffer using :bw with g:smartq_bw_filetypes\r\n- Improve performance\r\n\r\nDocs\r\n\r\n- Remove redundant comments\r\n- Update README","3":"feat(smartq): First major update\r\n\r\nGeneral\r\n\r\n- Modularize script\r\n - Moved all functions in autoload dir\r\n- Add default mappings\r\n- Add SmartQCloseSplits\r\n- Add SmartQWipeEmpty\r\n - Remove auto wipe empty buffers feature\r\n\r\nSmartQ\r\n\r\n- Fix filetype detection\r\n- Add option to delete buffer using :bw with g:smartq_bw_filetypes\r\n- Improve performance\r\n\r\nDocs\r\n\r\n- Remove redundant comments\r\n- Update README","package":"vim-smartq.tar.gz","4":"vim-smartq.tar.gz","src_id":"27631","5":"27631","creation_date":"1623655994","6":"1623655994"},{"0":"5959","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"smartq.vim","4":"smartq.vim","src_id":"27629","5":"27629","creation_date":"1623574424","6":"1623574424"}]},"5958":{"script_id":"5958","0":"5958","script_name":"Minimd","1":"Minimd","script_type":"utility","2":"utility","summary":"A fast, folding Markdown outliner.","3":"A fast, folding Markdown outliner.","description":"Minimd is a Vim plugin that helps with writing long Markdown documents by folding sections and showing outlines of their contents.\r\n\r\nThe basic idea is that pressing spacebar on an unfolded level 1 header will fold that header, while pressing spacebar on a folded level 1 header will both unfold it and fold all the level 2 headers it contains. If you fold then unfold a level 3 header, any level 4 headers are folded, and so on. Pressing a number followed by the spacebar folds all headers of that number, which gives you an outline.\r\n\r\nMinimd also has a few other features to make working with long documents easier:\r\n\r\n- Header motion command that ignore code blocks (so don't mistake # comments for headers);\r\n- Minimal syntax highlighting (headers, code blocks, square brackets, checkboxes, and the task markers ACTV, TODO, WAIT, CNCL, and DONE) so as not to be too distracting and to speed up the folding a bit\r\n- Shortcuts to simultaneously change the levels of all headers within a fold\r\n- A fast word count (in the status line by default) that updates only when toggling between insert and normal modes.\r\n\r\nUsage is simple: folds and unfolds individual headers while [count] (i. e. \"1\" followed by spacebar) folds all headers at level [count]. When unfolding a specific header with level n, contained headers with level n+1 are folded, providing an outline of the unfolded header's contents. Jumping to the next header can be done with or ]h, and to the previous with or [h; prefixing either movement with [count] jumps to the next header of level [count] in the given direction.","4":"Minimd is a Vim plugin that helps with writing long Markdown documents by folding sections and showing outlines of their contents.\r\n\r\nThe basic idea is that pressing spacebar on an unfolded level 1 header will fold that header, while pressing spacebar on a folded level 1 header will both unfold it and fold all the level 2 headers it contains. If you fold then unfold a level 3 header, any level 4 headers are folded, and so on. Pressing a number followed by the spacebar folds all headers of that number, which gives you an outline.\r\n\r\nMinimd also has a few other features to make working with long documents easier:\r\n\r\n- Header motion command that ignore code blocks (so don't mistake # comments for headers);\r\n- Minimal syntax highlighting (headers, code blocks, square brackets, checkboxes, and the task markers ACTV, TODO, WAIT, CNCL, and DONE) so as not to be too distracting and to speed up the folding a bit\r\n- Shortcuts to simultaneously change the levels of all headers within a fold\r\n- A fast word count (in the status line by default) that updates only when toggling between insert and normal modes.\r\n\r\nUsage is simple: folds and unfolds individual headers while [count] (i. e. \"1\" followed by spacebar) folds all headers at level [count]. When unfolding a specific header with level n, contained headers with level n+1 are folded, providing an outline of the unfolded header's contents. Jumping to the next header can be done with or ]h, and to the previous with or [h; prefixing either movement with [count] jumps to the next header of level [count] in the given direction.","install_details":"Just copy the vim-minimd directory to ~\/.vim\/pack\/plugins\/start.\r\n\r\nThe included syntax file only specifies headers, code blocks, and task management entities. If you would like to use Minimd with Vim's default syntax (which will be around 3x slower in my experience), `let g:default_markdown_syntax = 1` in your `vimrc`.\r\n\r\nThis plugin is developed at https:\/\/github.com\/shushcat\/vim-minimd, so the most recent version will appear there; only versions with significant bug fixes or changes to functionality will be posted here.","5":"Just copy the vim-minimd directory to ~\/.vim\/pack\/plugins\/start.\r\n\r\nThe included syntax file only specifies headers, code blocks, and task management entities. If you would like to use Minimd with Vim's default syntax (which will be around 3x slower in my experience), `let g:default_markdown_syntax = 1` in your `vimrc`.\r\n\r\nThis plugin is developed at https:\/\/github.com\/shushcat\/vim-minimd, so the most recent version will appear there; only versions with significant bug fixes or changes to functionality will be posted here.","first_name":"J.","6":"J.","last_name":"B.","7":"B.","releases":[{"0":"5958","vim_version":"7.0","1":"7.0","script_version":"1.4","2":"1.4","version_comment":"Fix a bug that excluded empty headers appearing at the ends of files from their parent folds.","3":"Fix a bug that excluded empty headers appearing at the ends of files from their parent folds.","package":"minimd.tar.gz","4":"minimd.tar.gz","src_id":"28049","5":"28049","creation_date":"1652960145","6":"1652960145"},{"0":"5958","vim_version":"7.0","1":"7.0","script_version":"1.3","2":"1.3","version_comment":"Fix header search regular expression for substantial speedup.","3":"Fix header search regular expression for substantial speedup.","package":"minimd.tar.gz","4":"minimd.tar.gz","src_id":"27843","5":"27843","creation_date":"1639641997","6":"1639641997"},{"0":"5958","vim_version":"7.0","1":"7.0","script_version":"1.2","2":"1.2","version_comment":"Allow using default Markdown syntax. Jump to headers of specified number.","3":"Allow using default Markdown syntax. Jump to headers of specified number.","package":"minimd.tar.gz","4":"minimd.tar.gz","src_id":"27685","5":"27685","creation_date":"1627604658","6":"1627604658"},{"0":"5958","vim_version":"7.0","1":"7.0","script_version":"1.1","2":"1.1","version_comment":"Allows unfolding at the location of a search inside a folded region.","3":"Allows unfolding at the location of a search inside a folded region.","package":"minimd.tar.gz","4":"minimd.tar.gz","src_id":"27637","5":"27637","creation_date":"1624712541","6":"1624712541"},{"0":"5958","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"minimd.tar.gz","4":"minimd.tar.gz","src_id":"27628","5":"27628","creation_date":"1623551026","6":"1623551026"}]},"5957":{"script_id":"5957","0":"5957","script_name":"vim-movelines","1":"vim-movelines","script_type":"indent","2":"indent","summary":"Vim plugin for moving lines in normal and visual mode.","3":"Vim plugin for moving lines in normal and visual mode.","description":"Vim plugin for moving lines in normal and visual mode.\r\n\r\nhttps:\/\/github.com\/krcs\/vim-movelines\r\n","4":"Vim plugin for moving lines in normal and visual mode.\r\n\r\nhttps:\/\/github.com\/krcs\/vim-movelines\r\n","install_details":"Copy movelines.vim into ~\/.vim\/plugin or $HOME\/vimfiles\/plugin directory.\r\n\r\nFor normal mode call MoveLineNormal(direction). For virtual mode call MoveLinesVisual(direcion).\r\n\r\ndirection - Up,Down,Left,Right, words or only first letter.\r\n\r\nIn the .vimrc file insert following lines to map keys, I am using Alt+[cursor key]:\r\n\r\nnnoremap :call MoveLineNormal(\\\"d\\\")\r\nnnoremap :call MoveLineNormal(\\\"l\\\")\r\nnnoremap :call MoveLineNormal(\\\"r\\\")\r\n\r\nxnoremap :call MoveLinesVisual(\\\"left\\\")\r\nxnoremap :call MoveLinesVisual(\\\"Right\\\")\r\nxnoremap :call MoveLinesVisual(\\\"down\\\")","5":"Copy movelines.vim into ~\/.vim\/plugin or $HOME\/vimfiles\/plugin directory.\r\n\r\nFor normal mode call MoveLineNormal(direction). For virtual mode call MoveLinesVisual(direcion).\r\n\r\ndirection - Up,Down,Left,Right, words or only first letter.\r\n\r\nIn the .vimrc file insert following lines to map keys, I am using Alt+[cursor key]:\r\n\r\nnnoremap :call MoveLineNormal(\\\"d\\\")\r\nnnoremap :call MoveLineNormal(\\\"l\\\")\r\nnnoremap :call MoveLineNormal(\\\"r\\\")\r\n\r\nxnoremap :call MoveLinesVisual(\\\"left\\\")\r\nxnoremap :call MoveLinesVisual(\\\"Right\\\")\r\nxnoremap :call MoveLinesVisual(\\\"down\\\")","first_name":"Krzysztof","6":"Krzysztof","last_name":"Cieslak","7":"Cieslak","releases":[{"0":"5957","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"MoveLines.vim","4":"MoveLines.vim","src_id":"27625","5":"27625","creation_date":"1623009962","6":"1623009962"}]},"5956":{"script_id":"5956","0":"5956","script_name":"bookmarks.vim","1":"bookmarks.vim","script_type":"utility","2":"utility","summary":"enhanced bookmarks","3":"enhanced bookmarks","description":"Abridged command help: \r\n \r\n- Add bookmarks: \r\n Bka [SEP] [COMMENTS] : add new mark to bookmarks session file (SEP: = - # _ . *). \r\n Bkai [OPT] : add new mark and indent the text (OPT: ?\/number\/d\/i\/q\/s\/r). \r\n \r\n- Remove bookmarks: \r\n Bkd : delete bookmark on cursor position. \r\n Bku : delete last saved bookmark. \r\n \r\n- Manage bookmarks session: \r\n Bksh : show marks session file name. \r\n Bkl [FILE] : load bookmarks session marks into quickfix. \r\n BkU : unload bookmarks session file. \r\n \r\n- Edit the saved bookmarks (only on bookmarks' file or quickfix window): \r\n Bke : open marks session file on new tab. \r\n [range]Bkrv : reverse the selected lines (last line on top, first line on bottom). \r\n [range]Bki [OPT] : indent bookmarks file (OPT: ?\/num\/-\/+\/=). \r\n [range]BkI [OPT] : indent bookmarks file in reverse order (OPT: ?\/num\/d\/i\/q). \r\n [range]Bkirm : remove indentation on bookmarks file. \r\n Bkin : show current bookmark line indentation level number. \r\n BkiN : set current bookmark line indentation level number as the new indentation number. \r\n \r\n- Settings (bookmarks' file settings): \r\n Bkpl [LINE] : position on line number. Set indentation number to the current line indentation. \r\n \u00c2\u00a6 \u00c2\u00a6 \u00c2\u00a6 \u00c2\u00a6 \u00c2\u00a6 \u00c2\u00a6 position on current line (and current indentation) when no line provided. \r\n Bkm [MODE] : change\/show direction mode (f:fordwards, b:backwards). \r\n \u00c2\u00a6 \u00c2\u00a6 \u00c2\u00a6 \u00c2\u00a6 \u00c2\u00a6 \u00c2\u00a6 toogle current mode when no argument found. \r\n \u00c2\u00a6 \u00c2\u00a6 \u00c2\u00a6 \u00c2\u00a6 \u00c2\u00a6 \u00c2\u00a6 show current mode when argument is ?. \r\n \r\n- Yank\/Paste commands: \r\n Bky : yank bookmark (file, position and line text) into system clipboard. \r\n \u00c2\u00a6 \u00c2\u00a6 \u00c2\u00a6 \u00c2\u00a6 \u00c2\u00a6 \u00c2\u00a6 add the bookmark to the yank buffer too. \r\n BkY : yank bookmark (file and position only) into system clipboard. \r\n \r\n- Yank buffer commands: \r\n Bkym [MODE] : set yank mode (insert\/append). \r\n \u00c2\u00a6 \u00c2\u00a6 \u00c2\u00a6 \u00c2\u00a6 \u00c2\u00a6 \u00c2\u00a6 toogle current mode when no argument found. \r\n \u00c2\u00a6 \u00c2\u00a6 \u00c2\u00a6 \u00c2\u00a6 \u00c2\u00a6 \u00c2\u00a6 show current mode when argument is ?. \r\n Bkp : paste all bookmarks previosly yanked. \r\n BkP : paste all bookmarks previosly yanked on previous line. \r\n Bky0 : empty all bookmarks previosly yanked. \r\n Bkp0 : empty all bookmarks previosly yanked. \r\n BkyR : recover all previous bookmarks on yank buffer. \r\n Bkyr : reverse the order on all bookmarks on yank buffer. \r\n Bkysh : show main yank buffer. \r\n Bkyshp : show previous yank buffer. \r\n \r\n- Others: \r\n Bkqf2f : replace qf file format to save as bookmarks file. \r\n Bkv LEVEL : Change plugin verbose level. \r\n \r\nOptions hepl: \r\n SEP: use separator characater. Characters allowed = - # _ . * \r\n \r\n OPT ?: show indentation configuration. \r\n OPT number: add number to the current indentation and add bookmarks. \r\n OPT d: decrease indentation and add bookmark indented. \r\n OPT =: keep previous indentation and add bookmark indented. \r\n OPT r: reset indentation number to 0 and add bookmark. \r\n OPT s: increase indentation number and add bookmark indented without indentation number (if active). \r\n\r\n---------------------------------------------------------------------------------------------------------------------------------- \r\n \r\nEXAMPLES: \r\n \r\n:Bka \r\n Add new bookmark on current position. \r\n Result: \r\n filepath:line:column:...... current line text \r\n \r\n:Bka Comment text \r\n Add new bookmark with a previous comment line. \r\n Result: \r\n Comment text filepath:line:column:...... current line text \r\n \r\n:Bka == Title text with separator up and down \r\n Add new bookmark with title and separators from current line. \r\n Result: \r\n ========================================= \r\n Title text with separator up and down \r\n ========================================= \r\n filepath:line:column:...... current line text \r\n \r\n:Bka ## Title text with separator up and down \r\n Add new bookmark with title and separators from current line. \r\n Result: \r\n ######################################### \r\n Title text with separator up and down \r\n ######################################### \r\n filepath:line:column:...... current line text \r\n \r\n:Bka - Title text with one separator \r\n Add new bookmark with title and separators from current line. \r\n Result: \r\n ----------------------------------------- \r\n Title text with one separator \r\n filepath:line:column:...... current line text \r\n \r\n:Bkai 3 \r\n Add new bookmark with indentation. \r\n Result: \r\n filepath:line:column:...... current line text 1 \r\n \r\n:Bkai \r\n Add new bookmark and increase previous indentation (indentation will be 5 spaces). \r\n Result: \r\n filepath:line:column:...... previous line text 1 \r\n filepath:line:column:...... current line text \r\n \r\n:Bkai q \r\n Add new bookmark and keep previous indentation (indentation will be 5 spaces). \r\n Result: \r\n filepath:line:column:...... previous line text 1 \r\n filepath:line:column:...... previous line text 2 \r\n filepath:line:column:...... current line text \r\n \r\n:Bkai d \r\n Add new bookmark and decrease previous indentation (indentation will be 4 spaces). \r\n Result: \r\n filepath:line:column:...... previous line text 1 \r\n filepath:line:column:...... previous line text 2 \r\n filepath:line:column:...... previous line text 3 \r\n filepath:line:column:...... current line text \r\n \r\n:Bkai r \r\n Add new bookmark and decrease previous indentation (indentation will be 0 spaces). \r\n Result: \r\n filepath:line:column:...... previous line text 1 \r\n filepath:line:column:...... previous line text 2 \r\n filepath:line:column:...... previous line text 3 \r\n filepath:line:column:...... previous line text \r\n filepath:line:column:......current line text ","4":"Abridged command help: \r\n \r\n- Add bookmarks: \r\n Bka [SEP] [COMMENTS] : add new mark to bookmarks session file (SEP: = - # _ . *). \r\n Bkai [OPT] : add new mark and indent the text (OPT: ?\/number\/d\/i\/q\/s\/r). \r\n \r\n- Remove bookmarks: \r\n Bkd : delete bookmark on cursor position. \r\n Bku : delete last saved bookmark. \r\n \r\n- Manage bookmarks session: \r\n Bksh : show marks session file name. \r\n Bkl [FILE] : load bookmarks session marks into quickfix. \r\n BkU : unload bookmarks session file. \r\n \r\n- Edit the saved bookmarks (only on bookmarks' file or quickfix window): \r\n Bke : open marks session file on new tab. \r\n [range]Bkrv : reverse the selected lines (last line on top, first line on bottom). \r\n [range]Bki [OPT] : indent bookmarks file (OPT: ?\/num\/-\/+\/=). \r\n [range]BkI [OPT] : indent bookmarks file in reverse order (OPT: ?\/num\/d\/i\/q). \r\n [range]Bkirm : remove indentation on bookmarks file. \r\n Bkin : show current bookmark line indentation level number. \r\n BkiN : set current bookmark line indentation level number as the new indentation number. \r\n \r\n- Settings (bookmarks' file settings): \r\n Bkpl [LINE] : position on line number. Set indentation number to the current line indentation. \r\n \u00c2\u00a6 \u00c2\u00a6 \u00c2\u00a6 \u00c2\u00a6 \u00c2\u00a6 \u00c2\u00a6 position on current line (and current indentation) when no line provided. \r\n Bkm [MODE] : change\/show direction mode (f:fordwards, b:backwards). \r\n \u00c2\u00a6 \u00c2\u00a6 \u00c2\u00a6 \u00c2\u00a6 \u00c2\u00a6 \u00c2\u00a6 toogle current mode when no argument found. \r\n \u00c2\u00a6 \u00c2\u00a6 \u00c2\u00a6 \u00c2\u00a6 \u00c2\u00a6 \u00c2\u00a6 show current mode when argument is ?. \r\n \r\n- Yank\/Paste commands: \r\n Bky : yank bookmark (file, position and line text) into system clipboard. \r\n \u00c2\u00a6 \u00c2\u00a6 \u00c2\u00a6 \u00c2\u00a6 \u00c2\u00a6 \u00c2\u00a6 add the bookmark to the yank buffer too. \r\n BkY : yank bookmark (file and position only) into system clipboard. \r\n \r\n- Yank buffer commands: \r\n Bkym [MODE] : set yank mode (insert\/append). \r\n \u00c2\u00a6 \u00c2\u00a6 \u00c2\u00a6 \u00c2\u00a6 \u00c2\u00a6 \u00c2\u00a6 toogle current mode when no argument found. \r\n \u00c2\u00a6 \u00c2\u00a6 \u00c2\u00a6 \u00c2\u00a6 \u00c2\u00a6 \u00c2\u00a6 show current mode when argument is ?. \r\n Bkp : paste all bookmarks previosly yanked. \r\n BkP : paste all bookmarks previosly yanked on previous line. \r\n Bky0 : empty all bookmarks previosly yanked. \r\n Bkp0 : empty all bookmarks previosly yanked. \r\n BkyR : recover all previous bookmarks on yank buffer. \r\n Bkyr : reverse the order on all bookmarks on yank buffer. \r\n Bkysh : show main yank buffer. \r\n Bkyshp : show previous yank buffer. \r\n \r\n- Others: \r\n Bkqf2f : replace qf file format to save as bookmarks file. \r\n Bkv LEVEL : Change plugin verbose level. \r\n \r\nOptions hepl: \r\n SEP: use separator characater. Characters allowed = - # _ . * \r\n \r\n OPT ?: show indentation configuration. \r\n OPT number: add number to the current indentation and add bookmarks. \r\n OPT d: decrease indentation and add bookmark indented. \r\n OPT =: keep previous indentation and add bookmark indented. \r\n OPT r: reset indentation number to 0 and add bookmark. \r\n OPT s: increase indentation number and add bookmark indented without indentation number (if active). \r\n\r\n---------------------------------------------------------------------------------------------------------------------------------- \r\n \r\nEXAMPLES: \r\n \r\n:Bka \r\n Add new bookmark on current position. \r\n Result: \r\n filepath:line:column:...... current line text \r\n \r\n:Bka Comment text \r\n Add new bookmark with a previous comment line. \r\n Result: \r\n Comment text filepath:line:column:...... current line text \r\n \r\n:Bka == Title text with separator up and down \r\n Add new bookmark with title and separators from current line. \r\n Result: \r\n ========================================= \r\n Title text with separator up and down \r\n ========================================= \r\n filepath:line:column:...... current line text \r\n \r\n:Bka ## Title text with separator up and down \r\n Add new bookmark with title and separators from current line. \r\n Result: \r\n ######################################### \r\n Title text with separator up and down \r\n ######################################### \r\n filepath:line:column:...... current line text \r\n \r\n:Bka - Title text with one separator \r\n Add new bookmark with title and separators from current line. \r\n Result: \r\n ----------------------------------------- \r\n Title text with one separator \r\n filepath:line:column:...... current line text \r\n \r\n:Bkai 3 \r\n Add new bookmark with indentation. \r\n Result: \r\n filepath:line:column:...... current line text 1 \r\n \r\n:Bkai \r\n Add new bookmark and increase previous indentation (indentation will be 5 spaces). \r\n Result: \r\n filepath:line:column:...... previous line text 1 \r\n filepath:line:column:...... current line text \r\n \r\n:Bkai q \r\n Add new bookmark and keep previous indentation (indentation will be 5 spaces). \r\n Result: \r\n filepath:line:column:...... previous line text 1 \r\n filepath:line:column:...... previous line text 2 \r\n filepath:line:column:...... current line text \r\n \r\n:Bkai d \r\n Add new bookmark and decrease previous indentation (indentation will be 4 spaces). \r\n Result: \r\n filepath:line:column:...... previous line text 1 \r\n filepath:line:column:...... previous line text 2 \r\n filepath:line:column:...... previous line text 3 \r\n filepath:line:column:...... current line text \r\n \r\n:Bkai r \r\n Add new bookmark and decrease previous indentation (indentation will be 0 spaces). \r\n Result: \r\n filepath:line:column:...... previous line text 1 \r\n filepath:line:column:...... previous line text 2 \r\n filepath:line:column:...... previous line text 3 \r\n filepath:line:column:...... previous line text \r\n filepath:line:column:......current line text ","install_details":"Minimum version: Vim 7.0+\r\nRecomended version: Vim 8.0+\r\n\r\nBinaries: ag (silver searcher) or grep needed to open the filter window.\r\n\r\nInstall vimball:\r\ndownload bookmarks_1.0.0.vmb\r\nvim bookmarks_1.0.0.vmb\r\n:so %\r\n:q ","5":"Minimum version: Vim 7.0+\r\nRecomended version: Vim 8.0+\r\n\r\nBinaries: ag (silver searcher) or grep needed to open the filter window.\r\n\r\nInstall vimball:\r\ndownload bookmarks_1.0.0.vmb\r\nvim bookmarks_1.0.0.vmb\r\n:so %\r\n:q ","first_name":"Javier","6":"Javier","last_name":"Puigdevall","7":"Puigdevall","releases":[{"0":"5956","vim_version":"7.0","1":"7.0","script_version":"1.0.0","2":"1.0.0","version_comment":"Initial upload","3":"Initial upload","package":"bookmarks_1.0.0.vmb","4":"bookmarks_1.0.0.vmb","src_id":"27622","5":"27622","creation_date":"1622655447","6":"1622655447"}]},"5955":{"script_id":"5955","0":"5955","script_name":"ruted-vim","1":"ruted-vim","script_type":"utility","2":"utility","summary":"The ruted-vim plugin allows you to enter Unicode symbols easily in Vim","3":"The ruted-vim plugin allows you to enter Unicode symbols easily in Vim","description":"The ruted-vim plugin is part of √𝚎𝚍, the rich Unicode text editing (RUTED, pronounced ˈruːtɪd) suite. Ruted-vim allows you to enter Unicode symbols easily in Vim. For example, to enter \"⇒\" while in Vim insert mode, you switch to the arrow symbol mode and type =>. Ruted-vim automatically replaces \"=>\" by \"⇒\". Ruted-vim uses ruted-format (https:\/\/gitlab.com\/ruted\/ruted-format) as the source for the available symbol modes and their replacement rules.","4":"The ruted-vim plugin is part of √𝚎𝚍, the rich Unicode text editing (RUTED, pronounced ˈruːtɪd) suite. Ruted-vim allows you to enter Unicode symbols easily in Vim. For example, to enter \"⇒\" while in Vim insert mode, you switch to the arrow symbol mode and type =>. Ruted-vim automatically replaces \"=>\" by \"⇒\". Ruted-vim uses ruted-format (https:\/\/gitlab.com\/ruted\/ruted-format) as the source for the available symbol modes and their replacement rules.","install_details":"Install ruted-vim like any other Vim plugin. If you use Vim's help system, you can also install the accompanying help file. This help file\r\ncontains the same information as README.md file in ruted-vim's GitLab repository at https:\/\/gitlab.com\/ruted\/ruted-vim.\r\n\r\nRuted-vim has two prerequisites:\r\n\r\n1. Ruted-vim uses the program ruted-format (https:\/\/gitlab.com\/ruted\/ruted-format). Install it before you install ruted-vim.\r\n2. To render the Unicode symbols you enter in Vim, you need a Unicode font that support these symbols. You find fairly complete Unicode fonts on most modern operating systems, but you can also install new ones. See https:\/\/en.wikipedia.org\/wiki\/Open-source_Unicode_typefaces for a list of open-source Unicode fonts.","5":"Install ruted-vim like any other Vim plugin. If you use Vim's help system, you can also install the accompanying help file. This help file\r\ncontains the same information as README.md file in ruted-vim's GitLab repository at https:\/\/gitlab.com\/ruted\/ruted-vim.\r\n\r\nRuted-vim has two prerequisites:\r\n\r\n1. Ruted-vim uses the program ruted-format (https:\/\/gitlab.com\/ruted\/ruted-format). Install it before you install ruted-vim.\r\n2. To render the Unicode symbols you enter in Vim, you need a Unicode font that support these symbols. You find fairly complete Unicode fonts on most modern operating systems, but you can also install new ones. See https:\/\/en.wikipedia.org\/wiki\/Open-source_Unicode_typefaces for a list of open-source Unicode fonts.","first_name":"Huub","6":"Huub","last_name":"de Beer","7":"de Beer","releases":[{"0":"5955","vim_version":"7.0","1":"7.0","script_version":"1","2":"1","version_comment":"Initial upload","3":"Initial upload","package":"ruted-vim.zip","4":"ruted-vim.zip","src_id":"27612","5":"27612","creation_date":"1621973190","6":"1621973190"}]},"5954":{"script_id":"5954","0":"5954","script_name":"enwise","1":"enwise","script_type":"utility","2":"utility","summary":"Press `enter` to close unbalanced brackets in cursorline.","3":"Press `enter` to close unbalanced brackets in cursorline.","description":"A vim plugin that allows you to use Enter key to close brackets.\r\n\r\nFeatures:\r\n\r\n- Free you mind from closing unbalanced brackets { ( [.\r\n- Respect your tab size and space size when inserting newline.\r\n- Smart enough to escape brackets inside quoted string.\r\n- Behave soundly when you press enter before some trailing characters in cursorline.\r\n- Brackets inside comments like \/\/ { \/* { *\/ are normally escaped.\r\n\r\nSee https:\/\/github.com\/mapkts\/enwise for more information about this plugin.","4":"A vim plugin that allows you to use Enter key to close brackets.\r\n\r\nFeatures:\r\n\r\n- Free you mind from closing unbalanced brackets { ( [.\r\n- Respect your tab size and space size when inserting newline.\r\n- Smart enough to escape brackets inside quoted string.\r\n- Behave soundly when you press enter before some trailing characters in cursorline.\r\n- Brackets inside comments like \/\/ { \/* { *\/ are normally escaped.\r\n\r\nSee https:\/\/github.com\/mapkts\/enwise for more information about this plugin.","install_details":"Install enwise with your favorite plugin manager, e.g vim-plug:\r\n\r\nPlug 'mapkts\/enwise'\r\n\r\nor install manually by unzipping the src listed below to ~\/.vim\/pack\/vendor\/start\/ (Vim 8+ only).","5":"Install enwise with your favorite plugin manager, e.g vim-plug:\r\n\r\nPlug 'mapkts\/enwise'\r\n\r\nor install manually by unzipping the src listed below to ~\/.vim\/pack\/vendor\/start\/ (Vim 8+ only).","first_name":"Aaron","6":"Aaron","last_name":"Taner","7":"Taner","releases":[{"0":"5954","vim_version":"7.0","1":"7.0","script_version":"v0.4.1","2":"v0.4.1","version_comment":"Enwise now works as expected even when current editing file don't have a recognized filetype.","3":"Enwise now works as expected even when current editing file don't have a recognized filetype.","package":"enwise.zip","4":"enwise.zip","src_id":"27756","5":"27756","creation_date":"1632850711","6":"1632850711"}]},"5953":{"script_id":"5953","0":"5953","script_name":"vim-highlighter","1":"vim-highlighter","script_type":"utility","2":"utility","summary":"Highlight words and expressions","3":"Highlight words and expressions","description":"Highlighting keywords or lines can be useful when analyzing code, reviewing summaries,\r\nand quickly comparing spellings. This plugin provides easy commands and shortcuts for\r\nsetting and deleting highlights, and additional features such as Move to Highlight, Save \r\nand Load, Find Pattern, and Customize Colors.\r\n\r\nFEATURES SUMMARY\r\n\r\n * Easy highlighting words under the cursor or pattern\r\n * Jump to Highlight\r\n * One Time Highlight\r\n * Following Highlight\r\n * Find in Files Highlight\r\n * Save & Load\r\n * Customizing Colors\r\n\r\nREADME\r\n\r\n https:\/\/github.com\/azabiong\/vim-highlighter\r\n\r\nHELP\r\n\r\n :h Highlighter\r\n\r\n\r\n","4":"Highlighting keywords or lines can be useful when analyzing code, reviewing summaries,\r\nand quickly comparing spellings. This plugin provides easy commands and shortcuts for\r\nsetting and deleting highlights, and additional features such as Move to Highlight, Save \r\nand Load, Find Pattern, and Customize Colors.\r\n\r\nFEATURES SUMMARY\r\n\r\n * Easy highlighting words under the cursor or pattern\r\n * Jump to Highlight\r\n * One Time Highlight\r\n * Following Highlight\r\n * Find in Files Highlight\r\n * Save & Load\r\n * Customizing Colors\r\n\r\nREADME\r\n\r\n https:\/\/github.com\/azabiong\/vim-highlighter\r\n\r\nHELP\r\n\r\n :h Highlighter\r\n\r\n\r\n","install_details":"If you have a plugin manager, it would be handy to use it.\r\n\r\nTo install the plugin from the downloaded archive using Vim's built-in package feature, it may be\r\nconvenient to run the following commands using copy and paste from the downloaded location.\r\n\r\n(Linux, Mac)\r\n PLUG=\"$HOME\/.vim\/pack\/azabiong\/start\"\r\n mkdir -p \"$PLUG\"\r\n unzip -o -d \"$PLUG\" vim-highlighter.zip\r\n vim -u NONE -c \"helptags $PLUG\/vim-highlighter\/doc\" -c q\r\n\r\n(Windows)\r\n cmd.exe\r\n set PLUG=\"%USERPROFILE%\/vimfiles\/pack\/azabiong\/start\"\r\n mkdir %PLUG%\r\n unzip -o -d %PLUG% vim-highlighter.zip\r\n vim -u NONE -c \"helptags %PLUG%\/vim-highlighter\/doc\" -c q\r\n\r\n In your vimrc:\r\n set encoding=utf-8 \" recommended for correct Unicode characters output\r\n\r\n\r\n","5":"If you have a plugin manager, it would be handy to use it.\r\n\r\nTo install the plugin from the downloaded archive using Vim's built-in package feature, it may be\r\nconvenient to run the following commands using copy and paste from the downloaded location.\r\n\r\n(Linux, Mac)\r\n PLUG=\"$HOME\/.vim\/pack\/azabiong\/start\"\r\n mkdir -p \"$PLUG\"\r\n unzip -o -d \"$PLUG\" vim-highlighter.zip\r\n vim -u NONE -c \"helptags $PLUG\/vim-highlighter\/doc\" -c q\r\n\r\n(Windows)\r\n cmd.exe\r\n set PLUG=\"%USERPROFILE%\/vimfiles\/pack\/azabiong\/start\"\r\n mkdir %PLUG%\r\n unzip -o -d %PLUG% vim-highlighter.zip\r\n vim -u NONE -c \"helptags %PLUG%\/vim-highlighter\/doc\" -c q\r\n\r\n In your vimrc:\r\n set encoding=utf-8 \" recommended for correct Unicode characters output\r\n\r\n\r\n","first_name":"Azabiong","6":"Azabiong","last_name":" ","7":" ","releases":[{"0":"5953","vim_version":"8.2","1":"8.2","script_version":"1.61.5","2":"1.61.5","version_comment":"Fix TabNew error\r\n ","3":"Fix TabNew error\r\n ","package":"vim-highlighter.zip","4":"vim-highlighter.zip","src_id":"28664","5":"28664","creation_date":"1713059045","6":"1713059045"},{"0":"5953","vim_version":"8.2","1":"8.2","script_version":"1.58.4","2":"1.58.4","version_comment":"Support \"Positional Highlight\" associated with a buffer\r\n :h Hi-Pos","3":"Support \"Positional Highlight\" associated with a buffer\r\n :h Hi-Pos","package":"vim-highlighter.zip","4":"vim-highlighter.zip","src_id":"28514","5":"28514","creation_date":"1689096432","6":"1689096432"},{"0":"5953","vim_version":"8.2","1":"8.2","script_version":"1.56","2":"1.56","version_comment":"Support jump in \"One Time Highlight\" and \"Following Highlight\" modes\r\n :h Hi-jump","3":"Support jump in \"One Time Highlight\" and \"Following Highlight\" modes\r\n :h Hi-jump","package":"vim-highlighter.zip","4":"vim-highlighter.zip","src_id":"28333","5":"28333","creation_date":"1672455463","6":"1672455463"},{"0":"5953","vim_version":"8.2","1":"8.2","script_version":"1.50.2","2":"1.50.2","version_comment":"Support jump to highlights \r\n :h Hi-jump","3":"Support jump to highlights \r\n :h Hi-jump","package":"vim-highlighter.zip","4":"vim-highlighter.zip","src_id":"28054","5":"28054","creation_date":"1653482403","6":"1653482403"},{"0":"5953","vim_version":"8.2","1":"8.2","script_version":"1.38","2":"1.38","version_comment":"Add highlighting using expression \r\n :Hi + pattern","3":"Add highlighting using expression \r\n :Hi + pattern","package":"vim-highlighter.zip","4":"vim-highlighter.zip","src_id":"27966","5":"27966","creation_date":"1647542595","6":"1647542595"},{"0":"5953","vim_version":"8.0","1":"8.0","script_version":"1.28","2":"1.28","version_comment":"Add command mode key completion \r\n- grep long options, directory and file names","3":"Add command mode key completion \r\n- grep long options, directory and file names","package":"vim-highlighter.zip","4":"vim-highlighter.zip","src_id":"27720","5":"27720","creation_date":"1630022711","6":"1630022711"},{"0":"5953","vim_version":"8.0","1":"8.0","script_version":"1.25","2":"1.25","version_comment":"Add commands - save, load highlights \r\nImprove \"Find\" window split location","3":"Add commands - save, load highlights \r\nImprove \"Find\" window split location","package":"vim-highlighter.zip","4":"vim-highlighter.zip","src_id":"27679","5":"27679","creation_date":"1627478960","6":"1627478960"},{"0":"5953","vim_version":"8.0","1":"8.0","script_version":"1.18","2":"1.18","version_comment":"Support multiple -e --regexp option\r\nHighlight line (visual mode)","3":"Support multiple -e --regexp option\r\nHighlight line (visual mode)","package":"vim-highlighter.zip","4":"vim-highlighter.zip","src_id":"27646","5":"27646","creation_date":"1625497737","6":"1625497737"},{"0":"5953","vim_version":"8.0","1":"8.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"vim-highlighter.zip","4":"vim-highlighter.zip","src_id":"27594","5":"27594","creation_date":"1620491494","6":"1620491494"}]},"5951":{"script_id":"5951","0":"5951","script_name":"addr2line","1":"addr2line","script_type":"utility","2":"utility","summary":"Perform address to line on a backtrace, load results on quickfix window..","3":"Perform address to line on a backtrace, load results on quickfix window..","description":"Given a buffer with an execution backtrace, this utility launches addr2line tool to obtain the code lines belonging to the addresses on the backtrace.\r\n\r\nIf no line selected, the current cursor position line will be used to search for the address ([0x...]) and perform the addr2line.\r\n\r\nIf there are lines selected, addr2line will be performed for the addresses found on each line.\r\n\r\nThe result of addr2line will be displayed on a quickfix window.\r\n\r\n\r\nCONFIGURATION:\r\n\r\nlet g:Addr2line_symbols = \"\/myPath\/myProject.symbols\"\r\nlet g:Addr2line_bin = \"addr2line\"\r\n\r\n\r\nCOMMANDS:\r\n\r\nPerform address to line on current cursor position, use default symbols and binary.\r\n:A2l\r\n\r\nPerform address to line on current selected lines, use default symbols and binary.\r\n:'<,'>A2l\r\n\r\nPerform address to line from current cursor position line and next three lines, use default the symbols and binary paths provided.\r\n:A2l mypath\/project.symbols \/bin\/arm_addr2line 3\r\n\r\nPerform address to line on selected lines, use default the symbols and binary paths provided.\r\n:'<,'>A2l mypath\/project.symbols \/bin\/arm_addr2line\r\n","4":"Given a buffer with an execution backtrace, this utility launches addr2line tool to obtain the code lines belonging to the addresses on the backtrace.\r\n\r\nIf no line selected, the current cursor position line will be used to search for the address ([0x...]) and perform the addr2line.\r\n\r\nIf there are lines selected, addr2line will be performed for the addresses found on each line.\r\n\r\nThe result of addr2line will be displayed on a quickfix window.\r\n\r\n\r\nCONFIGURATION:\r\n\r\nlet g:Addr2line_symbols = \"\/myPath\/myProject.symbols\"\r\nlet g:Addr2line_bin = \"addr2line\"\r\n\r\n\r\nCOMMANDS:\r\n\r\nPerform address to line on current cursor position, use default symbols and binary.\r\n:A2l\r\n\r\nPerform address to line on current selected lines, use default symbols and binary.\r\n:'<,'>A2l\r\n\r\nPerform address to line from current cursor position line and next three lines, use default the symbols and binary paths provided.\r\n:A2l mypath\/project.symbols \/bin\/arm_addr2line 3\r\n\r\nPerform address to line on selected lines, use default the symbols and binary paths provided.\r\n:'<,'>A2l mypath\/project.symbols \/bin\/arm_addr2line\r\n","install_details":"Minimum version: Vim 7.0+\r\nRecomended version: Vim 8.0+\r\n\r\nBinaries: addr2line.\r\n\r\nInstall vimball:\r\ndownload addr2line_0.0.1.vba\r\nvim addr2line_0.0.1.vba\r\n:so %\r\n:q ","5":"Minimum version: Vim 7.0+\r\nRecomended version: Vim 8.0+\r\n\r\nBinaries: addr2line.\r\n\r\nInstall vimball:\r\ndownload addr2line_0.0.1.vba\r\nvim addr2line_0.0.1.vba\r\n:so %\r\n:q ","first_name":"Javier","6":"Javier","last_name":"Puigdevall","7":"Puigdevall","releases":[{"0":"5951","vim_version":"7.0","1":"7.0","script_version":"0.0.1","2":"0.0.1","version_comment":"Initial upload","3":"Initial upload","package":"addr2line_0.0.1.vmb","4":"addr2line_0.0.1.vmb","src_id":"27553","5":"27553","creation_date":"1617064883","6":"1617064883"}]},"5950":{"script_id":"5950","0":"5950","script_name":"ge-qwerty-keymap","1":"ge-qwerty-keymap","script_type":"utility","2":"utility","summary":"Georgian QWERTY keyboard layout","3":"Georgian QWERTY keyboard layout","description":"Implements a QWERTY keymap for Georgian (and some other Caucasian) languages The QWERTY keyboard layout is what most Georgians use nowadays The layout for non-Georgian and archaic characters follows the Microsoft standard as seen on SWIFT-key\r\n","4":"Implements a QWERTY keymap for Georgian (and some other Caucasian) languages The QWERTY keyboard layout is what most Georgians use nowadays The layout for non-Georgian and archaic characters follows the Microsoft standard as seen on SWIFT-key\r\n","install_details":"Drop the `ge-qwerty.vim` file into `.vim\/keymap\/`\r\n\r\nEnable the keymap `with :set keymap=ge-qwerty`","5":"Drop the `ge-qwerty.vim` file into `.vim\/keymap\/`\r\n\r\nEnable the keymap `with :set keymap=ge-qwerty`","first_name":"Szymon","6":"Szymon","last_name":"Py\u017calski","7":"Pyżalski","releases":[{"0":"5950","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"ge-qwerty.vim","4":"ge-qwerty.vim","src_id":"27548","5":"27548","creation_date":"1616944307","6":"1616944307"}]},"5949":{"script_id":"5949","0":"5949","script_name":"projmakers","1":"projmakers","script_type":"ftplugin","2":"ftplugin","summary":"auto create makeprg commands per project","3":"auto create makeprg commands per project","description":"This plugin is maintained on https:\/\/github.com\/sagi-z\/projmakers\r\n\r\nThe description here is mostly a copy-paste from https:\/\/github.com\/sagi-z\/projmakers\/blob\/master\/README.md\r\n\r\n# Projmakers\r\n\r\nVim - auto create makeprg commands per project.\r\n \r\n## Description\r\n\r\nAdd simple entries to your [projectionist] json file to define make commands\r\nwhich set the *:compiler* and optionally also override the *makeprg*.\r\n\r\n## Dependencies\r\n\r\n* Required - [projectionist].\r\n* Recommended - [dispatch].\r\n\r\n### Or Manual\r\n\r\n* Install [projectionist].\r\n* Install this plugin:\r\n\r\n```text\r\n:!git clone https:\/\/github.com\/sagi-z\/projmakers ~\/.vim\/plugin\/projmakers\r\n```\r\n\r\n## Usage by example\r\n\r\n(See also [projectionist] for the '.projections.json' file).\r\n\r\nLets assume you're using a *.\/test.sh* script for testing, which runs several\r\n*pytest* executables (with different session setups), and you want to use it as\r\nthe testsuite for the project.\r\nAll you need in order to automatically create a main **:ProjTestSuite** command\r\nand some helper commands which use this script is to add this to your\r\n*.projections.json* file:\r\n\r\n```json\r\n {\r\n ...\r\n \"*\": {\r\n \"makeprgs\": {\r\n \"ProjTestSuite\" : {\r\n \"compiler\": \"pytest\",\r\n \"makeprg\": \"{project}\/test.sh\",\r\n \"args\": \"--all --short -- -v\",\r\n \"complete\": [\r\n \"--all\",\r\n \"--allow-fail\",\r\n \"--report\",\r\n \"--coverage\",\r\n \"--clean\",\r\n \"--refresh-req\",\r\n \"--no-reinstall\",\r\n \"--short\",\r\n \"--medium\",\r\n \"test_client\",\r\n \"test_commons\",\r\n \"test_mocked_client\",\r\n \"test_mocked_server\",\r\n \"test_server\"\r\n ]\r\n },\r\n \"ProjTestMockedClient\" : {\r\n \"compiler\": \"pytest\",\r\n \"makeprg\": \"{project}\/test.sh\",\r\n \"args\": \"-- -v test_mocked_client\"\r\n },\r\n \"ProjTestMockedServer\" : {\r\n \"compiler\": \"pytest\",\r\n \"makeprg\": \"{project}\/test.sh\",\r\n \"args\": \"-- -v test_mocked_server\"\r\n }\r\n ...\r\n }\r\n ...\r\n }\r\n```\r\n\r\nOther projects can have a different *:compiler* and *makeprgs* associated\r\nwith the same command.\r\n\r\nNow when a buffer is loaded and a *.projections.json* file is loaded for it, a\r\nnew **:ProjTestSuite** command will be defined in this buffer to use the\r\ncompiler and makeprg and invoke *:Make* if [dispatch] is installed or *:make*\r\notherwise (of course **:ProjTestMockedClient** and **:ProjTestMockedServer**\r\ncommands are created the same way as defined in the json file).\r\n\r\nIf you supply options on the vim command line then they replace the *args* in\r\nthe json file.\r\n\r\nTo sum up:\r\n\r\n* Add a *\"makeprgs\"* dictionary entry to files in your *.projections.json* file.\r\n* In this dictionary add your command dictionaries: a dictionary per command\r\n to create.\r\n* Each command dictionary will cause a command to be created for the current\r\n buffer of the relevant file, when loaded.\r\n* Each new command must have a *\"compiler\"* defined for it.\r\n* Each new command can optionally override the *\"makeprg\"* which the\r\n *:compiler* sets.\r\n* Each new command can optionally supply an *\"args\"* string which will be used as\r\n default arguments to the *\"makeprg\"* if none are supplied.\r\n* Each new command can optionally supply a *\"complete\"* list or string which\r\n will be used to help the user complete arguments for the command.\r\n\r\n## More help\r\n\r\nFor the most up to date docs use [:help projmakers](doc\/projmakers.txt)\r\n\r\n## License\r\n\r\nMIT\r\n\r\n[projectionist]: https:\/\/github.com\/tpope\/vim-projectionist\r\n[dispatch]: https:\/\/github.com\/tpope\/vim-dispatch\r\n[projmakers]: https:\/\/github.com\/sagi-z\/projmakers\r\n","4":"This plugin is maintained on https:\/\/github.com\/sagi-z\/projmakers\r\n\r\nThe description here is mostly a copy-paste from https:\/\/github.com\/sagi-z\/projmakers\/blob\/master\/README.md\r\n\r\n# Projmakers\r\n\r\nVim - auto create makeprg commands per project.\r\n \r\n## Description\r\n\r\nAdd simple entries to your [projectionist] json file to define make commands\r\nwhich set the *:compiler* and optionally also override the *makeprg*.\r\n\r\n## Dependencies\r\n\r\n* Required - [projectionist].\r\n* Recommended - [dispatch].\r\n\r\n### Or Manual\r\n\r\n* Install [projectionist].\r\n* Install this plugin:\r\n\r\n```text\r\n:!git clone https:\/\/github.com\/sagi-z\/projmakers ~\/.vim\/plugin\/projmakers\r\n```\r\n\r\n## Usage by example\r\n\r\n(See also [projectionist] for the '.projections.json' file).\r\n\r\nLets assume you're using a *.\/test.sh* script for testing, which runs several\r\n*pytest* executables (with different session setups), and you want to use it as\r\nthe testsuite for the project.\r\nAll you need in order to automatically create a main **:ProjTestSuite** command\r\nand some helper commands which use this script is to add this to your\r\n*.projections.json* file:\r\n\r\n```json\r\n {\r\n ...\r\n \"*\": {\r\n \"makeprgs\": {\r\n \"ProjTestSuite\" : {\r\n \"compiler\": \"pytest\",\r\n \"makeprg\": \"{project}\/test.sh\",\r\n \"args\": \"--all --short -- -v\",\r\n \"complete\": [\r\n \"--all\",\r\n \"--allow-fail\",\r\n \"--report\",\r\n \"--coverage\",\r\n \"--clean\",\r\n \"--refresh-req\",\r\n \"--no-reinstall\",\r\n \"--short\",\r\n \"--medium\",\r\n \"test_client\",\r\n \"test_commons\",\r\n \"test_mocked_client\",\r\n \"test_mocked_server\",\r\n \"test_server\"\r\n ]\r\n },\r\n \"ProjTestMockedClient\" : {\r\n \"compiler\": \"pytest\",\r\n \"makeprg\": \"{project}\/test.sh\",\r\n \"args\": \"-- -v test_mocked_client\"\r\n },\r\n \"ProjTestMockedServer\" : {\r\n \"compiler\": \"pytest\",\r\n \"makeprg\": \"{project}\/test.sh\",\r\n \"args\": \"-- -v test_mocked_server\"\r\n }\r\n ...\r\n }\r\n ...\r\n }\r\n```\r\n\r\nOther projects can have a different *:compiler* and *makeprgs* associated\r\nwith the same command.\r\n\r\nNow when a buffer is loaded and a *.projections.json* file is loaded for it, a\r\nnew **:ProjTestSuite** command will be defined in this buffer to use the\r\ncompiler and makeprg and invoke *:Make* if [dispatch] is installed or *:make*\r\notherwise (of course **:ProjTestMockedClient** and **:ProjTestMockedServer**\r\ncommands are created the same way as defined in the json file).\r\n\r\nIf you supply options on the vim command line then they replace the *args* in\r\nthe json file.\r\n\r\nTo sum up:\r\n\r\n* Add a *\"makeprgs\"* dictionary entry to files in your *.projections.json* file.\r\n* In this dictionary add your command dictionaries: a dictionary per command\r\n to create.\r\n* Each command dictionary will cause a command to be created for the current\r\n buffer of the relevant file, when loaded.\r\n* Each new command must have a *\"compiler\"* defined for it.\r\n* Each new command can optionally override the *\"makeprg\"* which the\r\n *:compiler* sets.\r\n* Each new command can optionally supply an *\"args\"* string which will be used as\r\n default arguments to the *\"makeprg\"* if none are supplied.\r\n* Each new command can optionally supply a *\"complete\"* list or string which\r\n will be used to help the user complete arguments for the command.\r\n\r\n## More help\r\n\r\nFor the most up to date docs use [:help projmakers](doc\/projmakers.txt)\r\n\r\n## License\r\n\r\nMIT\r\n\r\n[projectionist]: https:\/\/github.com\/tpope\/vim-projectionist\r\n[dispatch]: https:\/\/github.com\/tpope\/vim-dispatch\r\n[projmakers]: https:\/\/github.com\/sagi-z\/projmakers\r\n","install_details":"## Install\r\n\r\n### Either with plug.vim\r\n\r\nOf course make sure [projectionist] is installed:\r\n\r\n```vim\r\nPlug 'tpope\/vim-projectionist'\r\n```\r\n\r\nAnd also add this plugin:\r\n\r\n```vim\r\nPlug 'sagi-z\/projmakers'\r\n```\r\n","5":"## Install\r\n\r\n### Either with plug.vim\r\n\r\nOf course make sure [projectionist] is installed:\r\n\r\n```vim\r\nPlug 'tpope\/vim-projectionist'\r\n```\r\n\r\nAnd also add this plugin:\r\n\r\n```vim\r\nPlug 'sagi-z\/projmakers'\r\n```\r\n","first_name":"sagi","6":"sagi","last_name":"zeevi","7":"zeevi","releases":[{"0":"5949","vim_version":"8.2","1":"8.2","script_version":"0.9.1","2":"0.9.1","version_comment":"Initial upload","3":"Initial upload","package":"projmakers-0.9.1.tar.gz","4":"projmakers-0.9.1.tar.gz","src_id":"27543","5":"27543","creation_date":"1616625086","6":"1616625086"}]},"5948":{"script_id":"5948","0":"5948","script_name":"vimspectorpy","1":"vimspectorpy","script_type":"ftplugin","2":"ftplugin","summary":"python default configurations for vimspector","3":"python default configurations for vimspector","description":"This plugin is maintained on github - https:\/\/github.com\/sagi-z\/vimspectorpy\r\n\r\n# vimspectorpy - python default configurations for vimspector\r\n\r\n## Description\r\n\r\nBeing able to simply debug a piece of code with 'ipython' or set a breakpoint\r\nin a *pytest\/nose* is priceless. Also to use the correct python\r\nenvironment for debugging automatically should be transparent.\r\n\r\nThis plugin adds some python customization to [vimspector]:\r\n\r\n* Choose the correct python executable if in a VIRTUAL_ENV.\r\n* Run pytest\/nosetests for the project or test file, with breakpoints in\r\n [vimspector].\r\n* Debug the current file as a program.\r\n* Launch ipython and attach a debugger to it to debug your code with vimspector.\r\n* Add a strategy to [vim-test] to allow running a test case in a debugger.\r\n\r\n## Usage\r\n\r\n### Vimspector new configurations\r\n\r\nNext time you are on a python source and start a debug session (F5) you'll get\r\nthis option:\r\n\r\n1. debug this file - launch a debug session for the current file, using the\r\n python from your $VIRTUAL_ENV if there is one, or *python3*.\r\n\r\n### ipython\/pytest\/nosetests with vim breakpoints\r\n\r\nThese commands are available to you:\r\n\r\n```vim\r\n\" ipython started with debugpy, ready to attach to, but not attached.\r\n\" The default name is 'Pyconsole' - it is mapped to a port number you\r\n\" can attach to with :Pyattach.\r\n:Pyconsole [name]\r\n\r\n\" start a debug session with vimspector against the port mapped to by\r\n\" 'name'. The default name is 'Pyconsole'.\r\n:Pyattach [name]\r\n\r\n\" pytest started with debugpy, attached to immediately with vimspector.\r\n\" The default name is 'PytestD' - it is mapped to a port number you\r\n\" can attach to with :Pyattach, if you accidentally detach from it.\r\n\" 'options' are passed on to pytest.\r\n:PytestD [name] [options]\r\n\r\n\" pytest started with debugpy for the current file, attached to immediately\r\n\" with vimspector. The default name is 'PytestD' - it is mapped to a port\r\n\" number you can attach to with :Pyattach, if you accidentally detach from it.\r\n\" 'options' are passed on to pytest. The path to the current file is appended.\r\n:PytestDThis [name] [options]\r\n\r\n\" nosetests started with debugpy, attached to immediately with vimspector.\r\n\" The default name is 'NosetestsD' - it is mapped to a port number you\r\n\" can attach to with :Pyattach, if you accidentally detach from it.\r\n\" 'options' are passed on to nosetests.\r\n:NosetestsD [name] [options]\r\n\r\n\" nosetests started with debugpy for the current file, attached to immediately\r\n\" with vimspector. The default name is 'NosetestsD' - it is mapped to a port\r\n\" number you can attach to with :Pyattach, if you accidentally detach from it.\r\n\" 'options' are passed on to nosetests. The path to the current file is appended.\r\n:NosetestsDThis [name] [options]\r\n```\r\n\r\n### other commands\r\n\r\n```vim\r\n\" This installs\/updates this plugin's external dependencies:\r\n\" * A virtualenv with ipython and debugpy.\r\n\" * Some default configurations for {vimspector} python filetype.\r\n:VimspectorpyUpdate\r\n```\r\n\r\n## Settings\r\n\r\n### g:vimspectorpy#cmd_prefix\r\n\r\nThis plugin will not override command names you defined yourself. To avoid\r\nnaming conflicts you could add a prefix to its commands.\r\n\r\nThis will make all the 'Py...' commands start with 'VS' (VSPyconsole,\r\nVSPyattach, ...):\r\n\r\n```vim\r\nlet g:vimspectorpy#cmd_prefix = \"VS\"\r\n```\r\n\r\n### g:vimspectorpy#launcher\r\n\r\nFor starting another window the plugin will use [tmux] automatically in a\r\nconsole and 'xterm' in GUI.\r\n\r\nYou could choose 'rxvt' or force 'xterm' using:\r\n\r\n```vim\r\nlet g:vimspectorpy#launcher = \"rxvt\"\r\n```\r\n\r\n## Vim-test\r\n\r\nIf you are using the excellent [vim-test] plugin, then now you can choose a\r\nstrategy to open the test in a [vimspector] debugger:\r\n\r\n```vim\r\nlet test#strategy = \"vimspectorpy\"\r\n```\r\n\r\n## More help\r\n\r\nFor the most up to date docs use [:help vimspectorpy](doc\/vimspectorpy.txt)\r\n\r\n## License\r\n\r\nMIT\r\n\r\n[vimspector]: https:\/\/github.com\/puremourning\/vimspector\r\n[tmux]: https:\/\/github.com\/tmux\/tmux\/wiki\r\n[vim-test]: https:\/\/github.com\/vim-test\/vim-test\r\n","4":"This plugin is maintained on github - https:\/\/github.com\/sagi-z\/vimspectorpy\r\n\r\n# vimspectorpy - python default configurations for vimspector\r\n\r\n## Description\r\n\r\nBeing able to simply debug a piece of code with 'ipython' or set a breakpoint\r\nin a *pytest\/nose* is priceless. Also to use the correct python\r\nenvironment for debugging automatically should be transparent.\r\n\r\nThis plugin adds some python customization to [vimspector]:\r\n\r\n* Choose the correct python executable if in a VIRTUAL_ENV.\r\n* Run pytest\/nosetests for the project or test file, with breakpoints in\r\n [vimspector].\r\n* Debug the current file as a program.\r\n* Launch ipython and attach a debugger to it to debug your code with vimspector.\r\n* Add a strategy to [vim-test] to allow running a test case in a debugger.\r\n\r\n## Usage\r\n\r\n### Vimspector new configurations\r\n\r\nNext time you are on a python source and start a debug session (F5) you'll get\r\nthis option:\r\n\r\n1. debug this file - launch a debug session for the current file, using the\r\n python from your $VIRTUAL_ENV if there is one, or *python3*.\r\n\r\n### ipython\/pytest\/nosetests with vim breakpoints\r\n\r\nThese commands are available to you:\r\n\r\n```vim\r\n\" ipython started with debugpy, ready to attach to, but not attached.\r\n\" The default name is 'Pyconsole' - it is mapped to a port number you\r\n\" can attach to with :Pyattach.\r\n:Pyconsole [name]\r\n\r\n\" start a debug session with vimspector against the port mapped to by\r\n\" 'name'. The default name is 'Pyconsole'.\r\n:Pyattach [name]\r\n\r\n\" pytest started with debugpy, attached to immediately with vimspector.\r\n\" The default name is 'PytestD' - it is mapped to a port number you\r\n\" can attach to with :Pyattach, if you accidentally detach from it.\r\n\" 'options' are passed on to pytest.\r\n:PytestD [name] [options]\r\n\r\n\" pytest started with debugpy for the current file, attached to immediately\r\n\" with vimspector. The default name is 'PytestD' - it is mapped to a port\r\n\" number you can attach to with :Pyattach, if you accidentally detach from it.\r\n\" 'options' are passed on to pytest. The path to the current file is appended.\r\n:PytestDThis [name] [options]\r\n\r\n\" nosetests started with debugpy, attached to immediately with vimspector.\r\n\" The default name is 'NosetestsD' - it is mapped to a port number you\r\n\" can attach to with :Pyattach, if you accidentally detach from it.\r\n\" 'options' are passed on to nosetests.\r\n:NosetestsD [name] [options]\r\n\r\n\" nosetests started with debugpy for the current file, attached to immediately\r\n\" with vimspector. The default name is 'NosetestsD' - it is mapped to a port\r\n\" number you can attach to with :Pyattach, if you accidentally detach from it.\r\n\" 'options' are passed on to nosetests. The path to the current file is appended.\r\n:NosetestsDThis [name] [options]\r\n```\r\n\r\n### other commands\r\n\r\n```vim\r\n\" This installs\/updates this plugin's external dependencies:\r\n\" * A virtualenv with ipython and debugpy.\r\n\" * Some default configurations for {vimspector} python filetype.\r\n:VimspectorpyUpdate\r\n```\r\n\r\n## Settings\r\n\r\n### g:vimspectorpy#cmd_prefix\r\n\r\nThis plugin will not override command names you defined yourself. To avoid\r\nnaming conflicts you could add a prefix to its commands.\r\n\r\nThis will make all the 'Py...' commands start with 'VS' (VSPyconsole,\r\nVSPyattach, ...):\r\n\r\n```vim\r\nlet g:vimspectorpy#cmd_prefix = \"VS\"\r\n```\r\n\r\n### g:vimspectorpy#launcher\r\n\r\nFor starting another window the plugin will use [tmux] automatically in a\r\nconsole and 'xterm' in GUI.\r\n\r\nYou could choose 'rxvt' or force 'xterm' using:\r\n\r\n```vim\r\nlet g:vimspectorpy#launcher = \"rxvt\"\r\n```\r\n\r\n## Vim-test\r\n\r\nIf you are using the excellent [vim-test] plugin, then now you can choose a\r\nstrategy to open the test in a [vimspector] debugger:\r\n\r\n```vim\r\nlet test#strategy = \"vimspectorpy\"\r\n```\r\n\r\n## More help\r\n\r\nFor the most up to date docs use [:help vimspectorpy](doc\/vimspectorpy.txt)\r\n\r\n## License\r\n\r\nMIT\r\n\r\n[vimspector]: https:\/\/github.com\/puremourning\/vimspector\r\n[tmux]: https:\/\/github.com\/tmux\/tmux\/wiki\r\n[vim-test]: https:\/\/github.com\/vim-test\/vim-test\r\n","install_details":"## Install\r\n\r\n### with plug.vim\r\n\r\nOf course make sure [vimspector] is installed:\r\n\r\n`Plug 'puremourning\/vimspector'`\r\n\r\nAnd also add this:\r\n\r\n`Plug 'sagi-z\/vimspectorpy', { 'do': { -> vimspectorpy#update() } }`\r\n\r\n### Manual\r\n\r\n* Install [vimspector].\r\n* Clone this repository into your *~\/.vim\/plugin\/* directory.\r\n* From vim execute this command:\r\n\r\n```vim\r\n:VimspectorpyUpdate \r\n```","5":"## Install\r\n\r\n### with plug.vim\r\n\r\nOf course make sure [vimspector] is installed:\r\n\r\n`Plug 'puremourning\/vimspector'`\r\n\r\nAnd also add this:\r\n\r\n`Plug 'sagi-z\/vimspectorpy', { 'do': { -> vimspectorpy#update() } }`\r\n\r\n### Manual\r\n\r\n* Install [vimspector].\r\n* Clone this repository into your *~\/.vim\/plugin\/* directory.\r\n* From vim execute this command:\r\n\r\n```vim\r\n:VimspectorpyUpdate \r\n```","first_name":"sagi","6":"sagi","last_name":"zeevi","7":"zeevi","releases":[{"0":"5948","vim_version":"8.2","1":"8.2","script_version":"0.9.3","2":"0.9.3","version_comment":"Fixed these issues:\r\nIssue 10: Unable to install via vim-plug (missing nvim support)\r\nIssue 9: Cannot step into code in other packages","3":"Fixed these issues:\r\nIssue 10: Unable to install via vim-plug (missing nvim support)\r\nIssue 9: Cannot step into code in other packages","package":"vimspectorpy-0.9.3.zip","4":"vimspectorpy-0.9.3.zip","src_id":"27588","5":"27588","creation_date":"1619972529","6":"1619972529"},{"0":"5948","vim_version":"8.2","1":"8.2","script_version":"0.9.2","2":"0.9.2","version_comment":"Handle race conditions during installation. Also verifies debugpy is installed by vimspector.","3":"Handle race conditions during installation. Also verifies debugpy is installed by vimspector.","package":"vimspectorpy-0.9.2.tar.gz","4":"vimspectorpy-0.9.2.tar.gz","src_id":"27545","5":"27545","creation_date":"1616706844","6":"1616706844"},{"0":"5948","vim_version":"8.2","1":"8.2","script_version":"0.9.1","2":"0.9.1","version_comment":"Initial upload","3":"Initial upload","package":"vimspectorpy-0.9.1.tar.gz","4":"vimspectorpy-0.9.1.tar.gz","src_id":"27542","5":"27542","creation_date":"1616619626","6":"1616619626"}]},"5947":{"script_id":"5947","0":"5947","script_name":"redebug","1":"redebug","script_type":"utility","2":"utility","summary":"An interactive Python regular expression debugger.","3":"An interactive Python regular expression debugger.","description":"1. INTRODUCTION\r\n\r\nA Python regular expression debugger within Vim.\r\n\r\nThis is my first release of a VPE based plugin.\r\n\r\nThere are a number of these on-line, such as https:\/\/pythex.org\/, but I do not\r\nlike having to switch to a browser to debug a regular expression. Also, I have\r\nnot found one that works really well for me.\r\n\r\n\r\n2. QUICK START\r\n\r\nA single command |Redebug| is added by this plugin. Run this command, press\r\n to expand the help and try it out.\r\n\r\nRun:\r\n\r\n :help redebug.txt\r\n\r\nFor more information.\r\n\r\n\r\n3. FUTURE PLANS\r\n\r\nThis version represents the minimum quality I want for day-to-day use. I do\r\nhave plans to upgrade it.\r\n\r\n - Do a better job of keeping the most useful information visible\r\n when editing windows are opened.\r\n - Provide a way for users to change the colours.\r\n - Ideally make the default colours be based on the user's colour scheme.\r\n This needs to work in a way that uses background colours in an\r\n intelligent manner.\r\n - Add some clean ways to set the test text and regular expression from\r\n other buffers.\r\n - Also allow ways to view the results of other operations, such as\r\n re.split().\r\n - Support debugging of Vim regular expressions.\r\n\r\nSome more ambitious possible future enhancements.\r\n\r\n - Some form of advanced expression analysis.\r\n - Store a history of previous debug sessions.","4":"1. INTRODUCTION\r\n\r\nA Python regular expression debugger within Vim.\r\n\r\nThis is my first release of a VPE based plugin.\r\n\r\nThere are a number of these on-line, such as https:\/\/pythex.org\/, but I do not\r\nlike having to switch to a browser to debug a regular expression. Also, I have\r\nnot found one that works really well for me.\r\n\r\n\r\n2. QUICK START\r\n\r\nA single command |Redebug| is added by this plugin. Run this command, press\r\n to expand the help and try it out.\r\n\r\nRun:\r\n\r\n :help redebug.txt\r\n\r\nFor more information.\r\n\r\n\r\n3. FUTURE PLANS\r\n\r\nThis version represents the minimum quality I want for day-to-day use. I do\r\nhave plans to upgrade it.\r\n\r\n - Do a better job of keeping the most useful information visible\r\n when editing windows are opened.\r\n - Provide a way for users to change the colours.\r\n - Ideally make the default colours be based on the user's colour scheme.\r\n This needs to work in a way that uses background colours in an\r\n intelligent manner.\r\n - Add some clean ways to set the test text and regular expression from\r\n other buffers.\r\n - Also allow ways to view the results of other operations, such as\r\n re.split().\r\n - Support debugging of Vim regular expressions.\r\n\r\nSome more ambitious possible future enhancements.\r\n\r\n - Some form of advanced expression analysis.\r\n - Store a history of previous debug sessions.","install_details":"Redebug requires at least Vim 8.0 + Python 3.6 support and the VPE extensions\r\n(https:\/\/www.vim.org\/scripts\/script.php?script_id=5905).\r\n\r\nThis needs VPE 0.5.2 or better.\r\n\r\nRedebug needs syntax highlighting to be enabled in order to get useful\r\nbenefit.\r\n\r\nRedebug is a VPE plug-in. To install:\r\n\r\n 1. If not done already, install VPE.\r\n\r\n 2. Change to your $HOME\/.vim (Linux) or $HOME\/vimfiles directory.\r\n\r\n 3. Unzip the installation file.\r\n\r\nThis will create files in sub-directories vpe_plugins and vpe_plugins\/doc.\r\n\r\nHelp is provided, run:\r\n\r\n :helptags ALL\r\n\r\nto generate the help tags.","5":"Redebug requires at least Vim 8.0 + Python 3.6 support and the VPE extensions\r\n(https:\/\/www.vim.org\/scripts\/script.php?script_id=5905).\r\n\r\nThis needs VPE 0.5.2 or better.\r\n\r\nRedebug needs syntax highlighting to be enabled in order to get useful\r\nbenefit.\r\n\r\nRedebug is a VPE plug-in. To install:\r\n\r\n 1. If not done already, install VPE.\r\n\r\n 2. Change to your $HOME\/.vim (Linux) or $HOME\/vimfiles directory.\r\n\r\n 3. Unzip the installation file.\r\n\r\nThis will create files in sub-directories vpe_plugins and vpe_plugins\/doc.\r\n\r\nHelp is provided, run:\r\n\r\n :helptags ALL\r\n\r\nto generate the help tags.","first_name":"Paul","6":"Paul","last_name":"Ollis","7":"Ollis","releases":[{"0":"5947","vim_version":"8.0","1":"8.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"redebug-0.1.zip","4":"redebug-0.1.zip","src_id":"27539","5":"27539","creation_date":"1616282701","6":"1616282701"}]},"5946":{"script_id":"5946","0":"5946","script_name":"onetags","1":"onetags","script_type":"ftplugin","2":"ftplugin","summary":"vim tag files management","3":"vim tag files management","description":"This plugin maintains a tags file for ctags supported file types.\r\n* Each file is assigned a tags file automatically depending on its automatically detected project and file type.\r\n* You can add shared tag files of your owns per detected project and file type.\r\n\r\nHelp\r\n====\r\nThis plugin simply works out of the box.\r\n\r\nFor some tweaking, settings and commands install and type :help onetags\r\n\r\nFor dependencies and more info see https:\/\/github.com\/sagi-z\/onetags\/blob\/master\/doc\/onetags.txt","4":"This plugin maintains a tags file for ctags supported file types.\r\n* Each file is assigned a tags file automatically depending on its automatically detected project and file type.\r\n* You can add shared tag files of your owns per detected project and file type.\r\n\r\nHelp\r\n====\r\nThis plugin simply works out of the box.\r\n\r\nFor some tweaking, settings and commands install and type :help onetags\r\n\r\nFor dependencies and more info see https:\/\/github.com\/sagi-z\/onetags\/blob\/master\/doc\/onetags.txt","install_details":"Plug 'sagi-z\/onetags'\r\n","5":"Plug 'sagi-z\/onetags'\r\n","first_name":"sagi","6":"sagi","last_name":"zeevi","7":"zeevi","releases":[{"0":"5946","vim_version":"8.2","1":"8.2","script_version":"0.9.7","2":"0.9.7","version_comment":"Fixes:\r\nIssue 16: nvim support\r\nIssue 15: Fix for large projects\r\nIssue 14: Improve performance for large projects","3":"Fixes:\r\nIssue 16: nvim support\r\nIssue 15: Fix for large projects\r\nIssue 14: Improve performance for large projects","package":"onetags-0.9.7.zip","4":"onetags-0.9.7.zip","src_id":"27586","5":"27586","creation_date":"1619972205","6":"1619972205"},{"0":"5946","vim_version":"8.2","1":"8.2","script_version":"0.9.5","2":"0.9.5","version_comment":"## Version 0.9.5 solved issues\r\nIssue 10: Failed to update external tags from .onetags.json\r\nIssue 9: plugin ignore user overriding defaults\r\nIssue 8: marker file in inner directory is skipped\r\nIssue 7: Conflicts with Gdiffsplit\r\nIssue 6: add marker files","3":"## Version 0.9.5 solved issues\r\nIssue 10: Failed to update external tags from .onetags.json\r\nIssue 9: plugin ignore user overriding defaults\r\nIssue 8: marker file in inner directory is skipped\r\nIssue 7: Conflicts with Gdiffsplit\r\nIssue 6: add marker files","package":"onetags-0.9.5.zip","4":"onetags-0.9.5.zip","src_id":"27563","5":"27563","creation_date":"1617558447","6":"1617558447"},{"0":"5946","vim_version":"8.2","1":"8.2","script_version":"0.9.4","2":"0.9.4","version_comment":"Doesn't break if ctags is not installed yet","3":"Doesn't break if ctags is not installed yet","package":"onetags-0.9.4.tar.gz","4":"onetags-0.9.4.tar.gz","src_id":"27544","5":"27544","creation_date":"1616706704","6":"1616706704"},{"0":"5946","vim_version":"8.2","1":"8.2","script_version":"0.9.3","2":"0.9.3","version_comment":"Fixed some bugs","3":"Fixed some bugs","package":"onetags-0.9.3.tar.gz","4":"onetags-0.9.3.tar.gz","src_id":"27541","5":"27541","creation_date":"1616619227","6":"1616619227"},{"0":"5946","vim_version":"8.2","1":"8.2","script_version":"0.9.1","2":"0.9.1","version_comment":"Initial upload","3":"Initial upload","package":"onetags-0.9.1.tar.gz","4":"onetags-0.9.1.tar.gz","src_id":"27526","5":"27526","creation_date":"1615260308","6":"1615260308"}]},"5945":{"script_id":"5945","0":"5945","script_name":"oonav","1":"oonav","script_type":"ftplugin","2":"ftplugin","summary":"Plugin for navigating object oriented code","3":"Plugin for navigating object oriented code","description":"* Navigate to method implementations in derived classes.\r\n* Navigate to method in parent class.\r\n* Use fzf - optional.\r\n* Using tags, preferably for the entire project.\r\n\r\nkeeping an updated tags for the project should be done manually or with another plugin (i.e onetags or gutentags).\r\n\r\nFor more details see https:\/\/github.com\/sagi-z\/oonav","4":"* Navigate to method implementations in derived classes.\r\n* Navigate to method in parent class.\r\n* Use fzf - optional.\r\n* Using tags, preferably for the entire project.\r\n\r\nkeeping an updated tags for the project should be done manually or with another plugin (i.e onetags or gutentags).\r\n\r\nFor more details see https:\/\/github.com\/sagi-z\/oonav","install_details":"Plug 'sagi-z\/oonav'\r\n","5":"Plug 'sagi-z\/oonav'\r\n","first_name":"sagi","6":"sagi","last_name":"zeevi","7":"zeevi","releases":[{"0":"5945","vim_version":"8.2","1":"8.2","script_version":"0.9.4","2":"0.9.4","version_comment":"Added nvim support","3":"Added nvim support","package":"oonav-0.9.4.zip","4":"oonav-0.9.4.zip","src_id":"27587","5":"27587","creation_date":"1619972339","6":"1619972339"},{"0":"5945","vim_version":"8.2","1":"8.2","script_version":"0.9.3","2":"0.9.3","version_comment":"Initial upload","3":"Initial upload","package":"oonav-0.9.3.tar.gz","4":"oonav-0.9.3.tar.gz","src_id":"27525","5":"27525","creation_date":"1615255895","6":"1615255895"}]},"5943":{"script_id":"5943","0":"5943","script_name":"VimBlame.vim","1":"VimBlame.vim","script_type":"utility","2":"utility","summary":"Open \"git blame\" info in a new tab","3":"Open \"git blame\" info in a new tab","description":"# VimBlame.vim\r\n\r\nDiplay git blame info in vim buffer.\r\n","4":"# VimBlame.vim\r\n\r\nDiplay git blame info in vim buffer.\r\n","install_details":"# Installation\r\n\r\nCopy `VimBlame.vim` into your ~\/.vim\/plugin directory.\r\nOr `:source VimBlame.vim` to load it into your running session.\r\n\r\nYou can set a keyboard shortcut if you want by placing something like: \r\n\r\n map :call VimBlame.vim()\r\n\r\nin your `~\/.vimrc` file. Yes, the `` is literally there at the end\r\nas the four characters shown.\r\n\r\n## Installing with Vundle\r\nAdd `Plugin 'ericcurtin\/VimBlame.vim'` to your your plugin definitions\r\nin your `.vimrc`\r\n","5":"# Installation\r\n\r\nCopy `VimBlame.vim` into your ~\/.vim\/plugin directory.\r\nOr `:source VimBlame.vim` to load it into your running session.\r\n\r\nYou can set a keyboard shortcut if you want by placing something like: \r\n\r\n map :call VimBlame.vim()\r\n\r\nin your `~\/.vimrc` file. Yes, the `` is literally there at the end\r\nas the four characters shown.\r\n\r\n## Installing with Vundle\r\nAdd `Plugin 'ericcurtin\/VimBlame.vim'` to your your plugin definitions\r\nin your `.vimrc`\r\n","first_name":"Eric","6":"Eric","last_name":"Curtin","7":"Curtin","releases":[{"0":"5943","vim_version":"7.4","1":"7.4","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"VimBlame.vim","4":"VimBlame.vim","src_id":"27498","5":"27498","creation_date":"1614284543","6":"1614284543"}]},"5942":{"script_id":"5942","0":"5942","script_name":"VimSub","1":"VimSub","script_type":"color scheme","2":"color scheme","summary":"A color scheme that looks like the default Sublime Text 3 theme","3":"A color scheme that looks like the default Sublime Text 3 theme","description":"VimSub is a Vim color scheme that looks like the default Sublime Text 3 theme. This script currently has 34 lines.","4":"VimSub is a Vim color scheme that looks like the default Sublime Text 3 theme. This script currently has 34 lines.","install_details":"To install this color scheme, copy script file and paste it to \/usr\/share\/vim\/vim82\/colors.","5":"To install this color scheme, copy script file and paste it to \/usr\/share\/vim\/vim82\/colors.","first_name":"Arian","6":"Arian","last_name":"H","7":"H","releases":[{"0":"5942","vim_version":"8.2","1":"8.2","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"vimsub.vim","4":"vimsub.vim","src_id":"27494","5":"27494","creation_date":"1614088837","6":"1614088837"}]},"5941":{"script_id":"5941","0":"5941","script_name":"VimAtom","1":"VimAtom","script_type":"color scheme","2":"color scheme","summary":"A color scheme that looks like the default Atom theme","3":"A color scheme that looks like the default Atom theme","description":"VimAtom is a Vim color scheme that looks like the default Atom theme. This script currently has 34 lines.","4":"VimAtom is a Vim color scheme that looks like the default Atom theme. This script currently has 34 lines.","install_details":"To install this color scheme, copy script file and paste it to \/usr\/share\/vim\/vim82\/colors.","5":"To install this color scheme, copy script file and paste it to \/usr\/share\/vim\/vim82\/colors.","first_name":"Arian","6":"Arian","last_name":"H","7":"H","releases":[{"0":"5941","vim_version":"8.2","1":"8.2","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"vimatom.vim","4":"vimatom.vim","src_id":"27493","5":"27493","creation_date":"1614053034","6":"1614053034"}]},"5940":{"script_id":"5940","0":"5940","script_name":"VimVSCode","1":"VimVSCode","script_type":"color scheme","2":"color scheme","summary":"A color scheme that looks like the default VSCode theme","3":"A color scheme that looks like the default VSCode theme","description":"VimVSCode is a Vim color scheme that looks like the default VSCode theme. This script currently has 34 lines.","4":"VimVSCode is a Vim color scheme that looks like the default VSCode theme. This script currently has 34 lines.","install_details":"To install this color scheme, copy script file and paste it to \/usr\/share\/vim\/vim82\/colors.","5":"To install this color scheme, copy script file and paste it to \/usr\/share\/vim\/vim82\/colors.","first_name":"Arian","6":"Arian","last_name":"H","7":"H","releases":[{"0":"5940","vim_version":"8.2","1":"8.2","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"vimvscode.vim","4":"vimvscode.vim","src_id":"27492","5":"27492","creation_date":"1614039565","6":"1614039565"}]},"5939":{"script_id":"5939","0":"5939","script_name":"gitgrep","1":"gitgrep","script_type":"utility","2":"utility","summary":"An easy way to issue a git grep command and navigate between the results","3":"An easy way to issue a git grep command and navigate between the results","description":"Homepage: https:\/\/github.com\/eranfrie\/gitgrep.vim","4":"Homepage: https:\/\/github.com\/eranfrie\/gitgrep.vim","install_details":"","5":"","first_name":"Eran","6":"Eran","last_name":"Friedman","7":"Friedman","releases":[{"0":"5939","vim_version":"7.0","1":"7.0","script_version":"1.1","2":"1.1","version_comment":"Can be configured to jump automatically in case of one match","3":"Can be configured to jump automatically in case of one match","package":"gitgrep.vim.zip","4":"gitgrep.vim.zip","src_id":"27496","5":"27496","creation_date":"1614217635","6":"1614217635"},{"0":"5939","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"gitgrep.vim.zip","4":"gitgrep.vim.zip","src_id":"27491","5":"27491","creation_date":"1613850513","6":"1613850513"}]},"5937":{"script_id":"5937","0":"5937","script_name":"deleft.vim","1":"deleft.vim","script_type":"utility","2":"utility","summary":" Delete a wrapping if-clause, try-catch block, etc. and shift left. ","3":" Delete a wrapping if-clause, try-catch block, etc. and shift left. ","description":"This plugin allows you to delete wrapping if-clauses, try-catch blocks, and similar constructs. For example:\r\n\r\n
\r\n Something<\/a>\r\n <\/div>\r\n\r\nExecuting the :Deleft command or using the provided \"dh\" mapping on the container div results in just:\r\n\r\n Something<\/a>\r\n\r\nSo, the mapping\/command deletes the opening and closing HTML tag and shifts the code to the left (hence the name \"deleft\", from \"delete left\").\r\n\r\nNote that \"dh\" is a built-in mapping, but it's a synonym to \"x\", so I'm okay with overwriting it. Set \"g:deleft_mapping\" to \"\" (or whatever else you like) to avoid this.\r\n\r\nThe plugin attempts to use the extended match definitions from \"matchit\". In ruby, for instance, the \"matchit.vim\" (built-in) plugin lets you jump between any related `if`\/`elsif`\/`else`\/`end` lines:\r\n\r\n if one?\r\n two\r\n elsif two?\r\n three\r\n else\r\n four\r\n end\r\n\r\nDelefting the if-clause will also remove all other else-like lines, anything that the matchit plugin jumps to, as long as it's at the same level of indent, leaving you with just this:\r\n\r\n two\r\n three\r\n four\r\n\r\nPlease read the built-in documentation for settings and additional informaiton.\r\n","4":"This plugin allows you to delete wrapping if-clauses, try-catch blocks, and similar constructs. For example:\r\n\r\n
\r\n Something<\/a>\r\n <\/div>\r\n\r\nExecuting the :Deleft command or using the provided \"dh\" mapping on the container div results in just:\r\n\r\n Something<\/a>\r\n\r\nSo, the mapping\/command deletes the opening and closing HTML tag and shifts the code to the left (hence the name \"deleft\", from \"delete left\").\r\n\r\nNote that \"dh\" is a built-in mapping, but it's a synonym to \"x\", so I'm okay with overwriting it. Set \"g:deleft_mapping\" to \"\" (or whatever else you like) to avoid this.\r\n\r\nThe plugin attempts to use the extended match definitions from \"matchit\". In ruby, for instance, the \"matchit.vim\" (built-in) plugin lets you jump between any related `if`\/`elsif`\/`else`\/`end` lines:\r\n\r\n if one?\r\n two\r\n elsif two?\r\n three\r\n else\r\n four\r\n end\r\n\r\nDelefting the if-clause will also remove all other else-like lines, anything that the matchit plugin jumps to, as long as it's at the same level of indent, leaving you with just this:\r\n\r\n two\r\n three\r\n four\r\n\r\nPlease read the built-in documentation for settings and additional informaiton.\r\n","install_details":"The easiest way to install the plugin is with a plugin manager:\r\n\r\n- vim-plug: https:\/\/github.com\/junegunn\/vim-plug\r\n- Vundle: https:\/\/github.com\/VundleVim\/Vundle.vim\r\n\r\nIf you use one, just follow the instructions in its documentation.\r\n\r\nYou can install the plugin yourself using Vim's \"packages\" functionality by cloning the project (or adding it as a submodule) under `~\/.vim\/pack\/\/start\/`. For example:\r\n\r\n git clone https:\/\/github.com\/AndrewRadev\/deleft.vim ~\/.vim\/pack\/_\/start\/deleft\r\n\r\nThis should automatically load the plugin for you on Vim start. Alternatively, you can add it to `~\/.vim\/pack\/\/opt\/` instead and load it in your .vimrc manually with:\r\n\r\n packadd deleft\r\n\r\nIf you'd rather not use git, you can download the files from the \"releases\" tab and unzip them in the relevant directory: https:\/\/github.com\/AndrewRadev\/deleft.vim\/releases.\r\n","5":"The easiest way to install the plugin is with a plugin manager:\r\n\r\n- vim-plug: https:\/\/github.com\/junegunn\/vim-plug\r\n- Vundle: https:\/\/github.com\/VundleVim\/Vundle.vim\r\n\r\nIf you use one, just follow the instructions in its documentation.\r\n\r\nYou can install the plugin yourself using Vim's \"packages\" functionality by cloning the project (or adding it as a submodule) under `~\/.vim\/pack\/\/start\/`. For example:\r\n\r\n git clone https:\/\/github.com\/AndrewRadev\/deleft.vim ~\/.vim\/pack\/_\/start\/deleft\r\n\r\nThis should automatically load the plugin for you on Vim start. Alternatively, you can add it to `~\/.vim\/pack\/\/opt\/` instead and load it in your .vimrc manually with:\r\n\r\n packadd deleft\r\n\r\nIf you'd rather not use git, you can download the files from the \"releases\" tab and unzip them in the relevant directory: https:\/\/github.com\/AndrewRadev\/deleft.vim\/releases.\r\n","first_name":"Andrew","6":"Andrew","last_name":"Radev","7":"Radev","releases":[{"0":"5937","vim_version":"7.4","1":"7.4","script_version":"0.1.1","2":"0.1.1","version_comment":"- Load matchit dependency if it's not loaded\r\n- Implement python fallback","3":"- Load matchit dependency if it's not loaded\r\n- Implement python fallback","package":"deleft.zip","4":"deleft.zip","src_id":"27487","5":"27487","creation_date":"1613672566","6":"1613672566"},{"0":"5937","vim_version":"7.4","1":"7.4","script_version":"0.1.0","2":"0.1.0","version_comment":"Initial upload","3":"Initial upload","package":"deleft.zip","4":"deleft.zip","src_id":"27483","5":"27483","creation_date":"1613429705","6":"1613429705"}]},"5936":{"script_id":"5936","0":"5936","script_name":"flipdir.vim","1":"flipdir.vim","script_type":"utility","2":"utility","summary":"Direcotry viewer","3":"Direcotry viewer","description":"This plugin was inspired by the concept of split explorer presented by Drew Neil. It uses unix ls to list files and directory. If you don't like this, you can use vim globpath function with some adjusts. Check the github page https:\/\/github.com\/jpaulogg\/vim-flipdir\r\n\r\nI switched from netrw to vim-dirvish when I started using a very old laptop and felt the need for a faster plugin. I think dirvish is a great plugin, but I found it a little difficult to make customizations, since I'm just a beginner in Vimscript. So I decided to write my own plugin, based on my use of dirvish.\r\n\r\nUsage: '-' flips current window to parent directory. Use 'h' and 'l' (or ) to browse directories, 'l' (or ) to open files in the current window, 's' and 'v' to open files and directories in new windows. You can select more than one target in visual mode and then use 'l' or 'v' commands, for example.\r\n\r\nCommands: Flipdir and Splitdir opens the parent directory or any path you pass as argument. For example, ':vert Sp $VIMRUNTIME' will open your runtime directory in a new vertical split.","4":"This plugin was inspired by the concept of split explorer presented by Drew Neil. It uses unix ls to list files and directory. If you don't like this, you can use vim globpath function with some adjusts. Check the github page https:\/\/github.com\/jpaulogg\/vim-flipdir\r\n\r\nI switched from netrw to vim-dirvish when I started using a very old laptop and felt the need for a faster plugin. I think dirvish is a great plugin, but I found it a little difficult to make customizations, since I'm just a beginner in Vimscript. So I decided to write my own plugin, based on my use of dirvish.\r\n\r\nUsage: '-' flips current window to parent directory. Use 'h' and 'l' (or ) to browse directories, 'l' (or ) to open files in the current window, 's' and 'v' to open files and directories in new windows. You can select more than one target in visual mode and then use 'l' or 'v' commands, for example.\r\n\r\nCommands: Flipdir and Splitdir opens the parent directory or any path you pass as argument. For example, ':vert Sp $VIMRUNTIME' will open your runtime directory in a new vertical split.","install_details":"Use vim's built-in package support. From the shell:\r\ncurl -o flipdir.zip 'https:\/\/www.vim.org\/scripts\/download_script.php?src_id=27475'\r\nunzip flipdir.zip -d ~\/.vim\/pack\/start\/","5":"Use vim's built-in package support. From the shell:\r\ncurl -o flipdir.zip 'https:\/\/www.vim.org\/scripts\/download_script.php?src_id=27475'\r\nunzip flipdir.zip -d ~\/.vim\/pack\/start\/","first_name":"Jo\u00c3\u00a3o","6":"Jo\u00c3\u00a3o","last_name":"Garcia","7":"Garcia","releases":[{"0":"5936","vim_version":"7.0","1":"7.0","script_version":"v2","2":"v2","version_comment":"correcting temporary buffer management","3":"correcting temporary buffer management","package":"vim-flipdir.zip","4":"vim-flipdir.zip","src_id":"27477","5":"27477","creation_date":"1612853773","6":"1612853773"},{"0":"5936","vim_version":"7.0","1":"7.0","script_version":"v1","2":"v1","version_comment":"correct zip file","3":"correct zip file","package":"vim-flipdir.zip","4":"vim-flipdir.zip","src_id":"27475","5":"27475","creation_date":"1612723775","6":"1612723775"}]},"5935":{"script_id":"5935","0":"5935","script_name":"tagasort.vim","1":"tagasort.vim","script_type":"utility","2":"utility","summary":"Sort and format the attributes of html and jsx tags.","3":"Sort and format the attributes of html and jsx tags.","description":"INTRODUCTION\r\n\r\nThe idea of Tagasort is to improve the readability of attributes of html and jsx tags. To do so, the attributes are sorted alphabetically and formatted to enforce a consistent style. Note that this plugin was designed with Vim's autoload functionality in mind to keep your Vim startup time low.\r\n\r\nEXAMPLE\r\n\r\nThe following case shows a tag before and after using the plugin.\r\n\r\nBefore:\r\n\r\n onClick(id )} a={5 } >\r\n\r\nAfter:\r\n\r\n onClick( id ) } z={ 1 }>\r\n\r\nUSAGE\r\n\r\nTagasort works in normal mode. To use it, place your cursor anywhere inside a tag and then hit the space bar twice. If you use it outside a tag, it will search for the next tag in the current line and use that as the target.\r\n\r\nMAPPINGS\r\n\r\nYou can easily change the key combination that triggers the plugin. For example, if you wanted to change the default mapping to 0 , you would have to add the following line to your vimrc:\r\n\r\n nmap 0 Tagasort_FormatTag\r\n\r\nLIMITATIONS\r\n\r\n- This plugin doesn't work with tags whose attributes are spread across multiple lines.\r\n- Nvim has magic enabled by default. Make sure to keep it this way, or else the plugin will have serious performance issues.\r\n\r\nGITHUB REPOSITORY\r\n\r\n https:\/\/github.com\/jose-villar\/vim-tagasort\r\n","4":"INTRODUCTION\r\n\r\nThe idea of Tagasort is to improve the readability of attributes of html and jsx tags. To do so, the attributes are sorted alphabetically and formatted to enforce a consistent style. Note that this plugin was designed with Vim's autoload functionality in mind to keep your Vim startup time low.\r\n\r\nEXAMPLE\r\n\r\nThe following case shows a tag before and after using the plugin.\r\n\r\nBefore:\r\n\r\n onClick(id )} a={5 } >\r\n\r\nAfter:\r\n\r\n onClick( id ) } z={ 1 }>\r\n\r\nUSAGE\r\n\r\nTagasort works in normal mode. To use it, place your cursor anywhere inside a tag and then hit the space bar twice. If you use it outside a tag, it will search for the next tag in the current line and use that as the target.\r\n\r\nMAPPINGS\r\n\r\nYou can easily change the key combination that triggers the plugin. For example, if you wanted to change the default mapping to 0 , you would have to add the following line to your vimrc:\r\n\r\n nmap 0 Tagasort_FormatTag\r\n\r\nLIMITATIONS\r\n\r\n- This plugin doesn't work with tags whose attributes are spread across multiple lines.\r\n- Nvim has magic enabled by default. Make sure to keep it this way, or else the plugin will have serious performance issues.\r\n\r\nGITHUB REPOSITORY\r\n\r\n https:\/\/github.com\/jose-villar\/vim-tagasort\r\n","install_details":"Use your favorite plugin manager.\r\n\r\nUSING PLUG\r\n\r\n1. Add the following line to your vimrc:\r\n \r\n Plug 'jose-villar\/vim-tagasort'\r\n\r\n2. From within Vim, run:\r\n\r\n :PlugInstall\r\n","5":"Use your favorite plugin manager.\r\n\r\nUSING PLUG\r\n\r\n1. Add the following line to your vimrc:\r\n \r\n Plug 'jose-villar\/vim-tagasort'\r\n\r\n2. From within Vim, run:\r\n\r\n :PlugInstall\r\n","first_name":"Jos\u00c3\u00a9","6":"Jos\u00c3\u00a9","last_name":"Villar","7":"Villar","releases":[{"0":"5935","vim_version":"7.0","1":"7.0","script_version":"1.2.4","2":"1.2.4","version_comment":"Fix bug regarding colon characters.","3":"Fix bug regarding colon characters.","package":"vim-tagasort-main.zip","4":"vim-tagasort-main.zip","src_id":"27573","5":"27573","creation_date":"1618566021","6":"1618566021"},{"0":"5935","vim_version":"7.0","1":"7.0","script_version":"1.2.3","2":"1.2.3","version_comment":"Fix bug regarding non single-byte characters\r\n\r\nThe bug prevented it from working with tags that had attributes\r\ncontaining certain characters such as \u00c3\u00a4 or \u00c3\u00a1.\r\n","3":"Fix bug regarding non single-byte characters\r\n\r\nThe bug prevented it from working with tags that had attributes\r\ncontaining certain characters such as \u00c3\u00a4 or \u00c3\u00a1.\r\n","package":"vim-tagasort-main.zip","4":"vim-tagasort-main.zip","src_id":"27569","5":"27569","creation_date":"1618129047","6":"1618129047"},{"0":"5935","vim_version":"7.0","1":"7.0","script_version":"1.2.2","2":"1.2.2","version_comment":"Fix bug regarding whitespace characters after commas.","3":"Fix bug regarding whitespace characters after commas.","package":"vim-tagasort-main.zip","4":"vim-tagasort-main.zip","src_id":"27564","5":"27564","creation_date":"1617698050","6":"1617698050"},{"0":"5935","vim_version":"7.0","1":"7.0","script_version":"1.2.1","2":"1.2.1","version_comment":"Add compatibility with Tim Pope's vim-repeat plugin","3":"Add compatibility with Tim Pope's vim-repeat plugin","package":"vim-tagasort-main.zip","4":"vim-tagasort-main.zip","src_id":"27486","5":"27486","creation_date":"1613640443","6":"1613640443"},{"0":"5935","vim_version":"7.0","1":"7.0","script_version":"1.1","2":"1.1","version_comment":"Add support for single quote string attributes","3":"Add support for single quote string attributes","package":"vim-tagasort-main.zip","4":"vim-tagasort-main.zip","src_id":"27478","5":"27478","creation_date":"1612918075","6":"1612918075"},{"0":"5935","vim_version":"7.0","1":"7.0","script_version":"1.0.1","2":"1.0.1","version_comment":"Fix typo in the documentation","3":"Fix typo in the documentation","package":"tagasort.zip","4":"tagasort.zip","src_id":"27468","5":"27468","creation_date":"1612404892","6":"1612404892"},{"0":"5935","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"tagasort.zip","4":"tagasort.zip","src_id":"27467","5":"27467","creation_date":"1612399430","6":"1612399430"}]},"5934":{"script_id":"5934","0":"5934","script_name":"nerdtree-harvest","1":"nerdtree-harvest","script_type":"utility","2":"utility","summary":"Yank modified file paths from NERD Tree","3":"Yank modified file paths from NERD Tree","description":"This is a Vim plugin that adds several ways to \u00e2\u0080\u009charvest\u00e2\u0080\u009d file paths from the NERD Tree directory browser.\r\n\r\nHarvest creates four mappings in the NERD Tree window: y, Y, ;, and !. Each mapping reads one or more additional characters to pick a path modifier and then performs an operation with the modified path. For example, yh yanks the path to the file's parent directory, much as :cd %:h changes the current directory to the parent of the file in the current buffer. See :help filename-modifiers for details on how these transform a file path.\r\n\r\nNERD Tree only shows these four mappings in the help list; you can hit ? after starting a mapping to see a summary of available modifiers, or consult the tables below. If the vim window is wide enough, ? will print names after each modifier key, otherwise just keys shown. Pressing ? a second time will show the full explanation, wrapping the echo line.\r\n\r\nModifier\tName\tPath Modification\r\n.\trelative\t:. File path from current working directory\r\n~\thome\t:~ File path from home directory, or absolute\r\np\tabsolute\t:p Absolute path from filesystem root\r\nh\thead\t:h Path without the last component (parent directory)\r\nH\trel+head\t:.:h Relative path to parent directory\r\nt\ttail\t:t Final path component (file name)\r\nr\troot\t:r Path with last extension removed (\/a\/b.c → \/a\/b)\r\nR\ttail+root\t:t:r Tail with last extension removed (\/a\/b.c → b)\r\ne\textension\t:e Last extension of the file name (\/a\/b.c → c)\r\n:\tmodifier\t: Arbitrary modifier, type enter to end e.g. :~:h\r\n?\thelp\tEcho a list of modifiers, continue reading next one\r\nA doubled mapping (yy, YY, ;;, or !!) reuses the previous modifier for the given type (yank, Ex, shell).\r\n\r\nThe : modifier type reads additional keys until you press enter (). The full input is used as a modifier of arbitrary length. Example uses of : are shown in the following table, read :help filename-modifiers for a full list.\r\n\r\nCommand\tEffect\r\ny:~:h\tYank the parent directory of a file, relative to your home directory\r\ny:h:h\tYank the path to the parent\u00e2\u0080\u0099s parent\r\ny:t:S\tYank the shell-quoted\/escaped file name, without leading path\r\ny:8\t(Windows-only) Yanks the \u00e2\u0080\u009c8.3\u00e2\u0080\u009d DOS form of a path\r\ny:.:gs#\/#.#:r\tYank the relative path with \/ replaced by . and file extension removed\r\nThe final example could be useful to reference a fully-qualified Java class.\r\n\r\nMore documentation and latest version at https:\/\/github.com\/flwyd\/nerdtree-harvest","4":"This is a Vim plugin that adds several ways to \u00e2\u0080\u009charvest\u00e2\u0080\u009d file paths from the NERD Tree directory browser.\r\n\r\nHarvest creates four mappings in the NERD Tree window: y, Y, ;, and !. Each mapping reads one or more additional characters to pick a path modifier and then performs an operation with the modified path. For example, yh yanks the path to the file's parent directory, much as :cd %:h changes the current directory to the parent of the file in the current buffer. See :help filename-modifiers for details on how these transform a file path.\r\n\r\nNERD Tree only shows these four mappings in the help list; you can hit ? after starting a mapping to see a summary of available modifiers, or consult the tables below. If the vim window is wide enough, ? will print names after each modifier key, otherwise just keys shown. Pressing ? a second time will show the full explanation, wrapping the echo line.\r\n\r\nModifier\tName\tPath Modification\r\n.\trelative\t:. File path from current working directory\r\n~\thome\t:~ File path from home directory, or absolute\r\np\tabsolute\t:p Absolute path from filesystem root\r\nh\thead\t:h Path without the last component (parent directory)\r\nH\trel+head\t:.:h Relative path to parent directory\r\nt\ttail\t:t Final path component (file name)\r\nr\troot\t:r Path with last extension removed (\/a\/b.c → \/a\/b)\r\nR\ttail+root\t:t:r Tail with last extension removed (\/a\/b.c → b)\r\ne\textension\t:e Last extension of the file name (\/a\/b.c → c)\r\n:\tmodifier\t: Arbitrary modifier, type enter to end e.g. :~:h\r\n?\thelp\tEcho a list of modifiers, continue reading next one\r\nA doubled mapping (yy, YY, ;;, or !!) reuses the previous modifier for the given type (yank, Ex, shell).\r\n\r\nThe : modifier type reads additional keys until you press enter (). The full input is used as a modifier of arbitrary length. Example uses of : are shown in the following table, read :help filename-modifiers for a full list.\r\n\r\nCommand\tEffect\r\ny:~:h\tYank the parent directory of a file, relative to your home directory\r\ny:h:h\tYank the path to the parent\u00e2\u0080\u0099s parent\r\ny:t:S\tYank the shell-quoted\/escaped file name, without leading path\r\ny:8\t(Windows-only) Yanks the \u00e2\u0080\u009c8.3\u00e2\u0080\u009d DOS form of a path\r\ny:.:gs#\/#.#:r\tYank the relative path with \/ replaced by . and file extension removed\r\nThe final example could be useful to reference a fully-qualified Java class.\r\n\r\nMore documentation and latest version at https:\/\/github.com\/flwyd\/nerdtree-harvest","install_details":"Point your favorite plugin manager at https:\/\/github.com\/flwyd\/nerdtree-harvest or unpack the zip file somewhere and add the directory to your runtimepath.","5":"Point your favorite plugin manager at https:\/\/github.com\/flwyd\/nerdtree-harvest or unpack the zip file somewhere and add the directory to your runtimepath.","first_name":"Trevor","6":"Trevor","last_name":"Stone","7":"Stone","releases":[{"0":"5934","vim_version":"7.3","1":"7.3","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"nerdtree-harvest-1_0.zip","4":"nerdtree-harvest-1_0.zip","src_id":"27466","5":"27466","creation_date":"1612366430","6":"1612366430"}]},"5933":{"script_id":"5933","0":"5933","script_name":"gen_clang_conf","1":"gen_clang_conf","script_type":"utility","2":"utility","summary":"easy generate simple clang config.","3":"easy generate simple clang config.","description":"# gen_clang_conf.vim\r\n\r\nplugin for [Vim](https:\/\/github.com\/vim\/vim)\/[NeoVim](https:\/\/github.com\/neovim\/neovim) to easy use clang config.<\/br>\r\n\r\nIt is used for generate simple config file for `clangd`, `ccls`, `ycm`, tested on Windows\/Linux. <\/br>\r\n\r\nget file list default use `rg`, if not have, use vim script(may be slow). <\/br>\r\n\r\n## Installation\r\n* [vim-plug](https:\/\/github.com\/junegunn\/vim-plug)\r\n\r\n `Plug 'fcying\/gen_clang_conf.vim'`\r\n\r\n## Options\r\n* `g:gencconf_ignore_dir`\r\n\r\n Specify the directories you want to exclude while generate config or tags.<\/br>\r\n default value:\r\n ```vim\r\n let g:gencconf_ignore_dir = ['__pycache__', 'out', 'lib', 'build',\r\n \\ 'cache', 'doc', 'docs']\r\n ```\r\n\r\n\r\n* `g:gencconf_ignore_file`\r\n\r\n Specify the files you want to exclude while generate config or tags.<\/br>\r\n default value:\r\n ```vim\r\n let g:gencconf_ignore_file = []\r\n ```\r\n\r\n\r\n* `g:gencconf_root_markers`\r\n\r\n Specify the which directoriy is root_marker dir.<\/br>\r\n default value:\r\n ```vim\r\n let g:gencconf_root_markers = ['.root', '.git', '.svn', '.hg']\r\n ```\r\n\r\n\r\n* `g:gencconf_suffix_list`\r\n\r\n Specify the which suffix file will be found.<\/br>\r\n default value:\r\n ```vim\r\n let g:gencconf_suffix_list = { 'c': ['c'], 'cpp': ['cc', 'cpp'], 'h': ['h', 'hh']}\r\n ```\r\n\r\n\r\n* `g:gencconf_storein_rootmarker`\r\n\r\n `1`, config will save in root_marker dir, `0`, save in root_marker's parent dir.<\/br>\r\n default value: 1\r\n\r\n\r\n* `g:gencconf_relative_path`\r\n\r\n `0`: full path, `1`: relative path.<\/br>\r\n default value: 1\r\n\r\n\r\n* `g:gencconf_default_option`\r\n\r\n Default options, add before autogen config.<\/br>\r\n only`compile_commands.json` use `cpp` options.\r\n\r\n default value:\r\n ```vim\r\n let g:gencconf_default_option = {'c': ['gcc', '-c', '-std=c11'], 'cpp': ['g++', '-c', '-std=c++14']}\r\n ```\r\n\r\n\r\n* `g:gencconf_conf_name`\r\n\r\n Specify clang config file name, ex: `compile_commands.json`, `compile_flags.txt`, `.ccls`, `.ycm_extra_conf.py`.<\/br>\r\n default value: \r\n ```vim\r\n let g:gencconf_conf_name = 'compile_commands.json'\r\n ```\r\n\r\n\r\n* `g:gencconf_ctags_bin`\r\n\r\n Set path of ctags bin.<\/br>\r\n default value: `ctags`\r\n\r\n\r\n* `g:gencconf_ctags_option`\r\n\r\n Set ctags option.<\/br>\r\n default value: `--languages=c++ --languages=+c`\r\n\r\n\r\n* `g:gencconf_autoload_tag`\r\n\r\n Auto load tags in root_marker.<\/br>\r\n default value: `1`\r\n\r\n\r\n## Commands\r\n* `:GenClangConf`\r\n\r\n Gen `compile_flags.txt` in root_marker's parent dir, it will add all the directories<\/br>\r\n containing the specified suffix files.<\/br>\r\n if not found root_marker dir, gen `compile_flags.txt` in current dir.\r\n\r\n* `:ClearClangConf`\r\n\r\n Remove the generated file.\r\n\r\n* `:GenCtags`\r\n\r\n Gen `prj_tags` in root_marker's dir.<\/br>\r\n if not found root_marker dir, gen in current dir.\r\n\r\n* `:ClearCtags`\r\n\r\n Remove the generated tags.\r\n\r\n\r\nGithub:\r\nhttps:\/\/github.com\/fcying\/gen_clang_conf.vim","4":"# gen_clang_conf.vim\r\n\r\nplugin for [Vim](https:\/\/github.com\/vim\/vim)\/[NeoVim](https:\/\/github.com\/neovim\/neovim) to easy use clang config.<\/br>\r\n\r\nIt is used for generate simple config file for `clangd`, `ccls`, `ycm`, tested on Windows\/Linux. <\/br>\r\n\r\nget file list default use `rg`, if not have, use vim script(may be slow). <\/br>\r\n\r\n## Installation\r\n* [vim-plug](https:\/\/github.com\/junegunn\/vim-plug)\r\n\r\n `Plug 'fcying\/gen_clang_conf.vim'`\r\n\r\n## Options\r\n* `g:gencconf_ignore_dir`\r\n\r\n Specify the directories you want to exclude while generate config or tags.<\/br>\r\n default value:\r\n ```vim\r\n let g:gencconf_ignore_dir = ['__pycache__', 'out', 'lib', 'build',\r\n \\ 'cache', 'doc', 'docs']\r\n ```\r\n\r\n\r\n* `g:gencconf_ignore_file`\r\n\r\n Specify the files you want to exclude while generate config or tags.<\/br>\r\n default value:\r\n ```vim\r\n let g:gencconf_ignore_file = []\r\n ```\r\n\r\n\r\n* `g:gencconf_root_markers`\r\n\r\n Specify the which directoriy is root_marker dir.<\/br>\r\n default value:\r\n ```vim\r\n let g:gencconf_root_markers = ['.root', '.git', '.svn', '.hg']\r\n ```\r\n\r\n\r\n* `g:gencconf_suffix_list`\r\n\r\n Specify the which suffix file will be found.<\/br>\r\n default value:\r\n ```vim\r\n let g:gencconf_suffix_list = { 'c': ['c'], 'cpp': ['cc', 'cpp'], 'h': ['h', 'hh']}\r\n ```\r\n\r\n\r\n* `g:gencconf_storein_rootmarker`\r\n\r\n `1`, config will save in root_marker dir, `0`, save in root_marker's parent dir.<\/br>\r\n default value: 1\r\n\r\n\r\n* `g:gencconf_relative_path`\r\n\r\n `0`: full path, `1`: relative path.<\/br>\r\n default value: 1\r\n\r\n\r\n* `g:gencconf_default_option`\r\n\r\n Default options, add before autogen config.<\/br>\r\n only`compile_commands.json` use `cpp` options.\r\n\r\n default value:\r\n ```vim\r\n let g:gencconf_default_option = {'c': ['gcc', '-c', '-std=c11'], 'cpp': ['g++', '-c', '-std=c++14']}\r\n ```\r\n\r\n\r\n* `g:gencconf_conf_name`\r\n\r\n Specify clang config file name, ex: `compile_commands.json`, `compile_flags.txt`, `.ccls`, `.ycm_extra_conf.py`.<\/br>\r\n default value: \r\n ```vim\r\n let g:gencconf_conf_name = 'compile_commands.json'\r\n ```\r\n\r\n\r\n* `g:gencconf_ctags_bin`\r\n\r\n Set path of ctags bin.<\/br>\r\n default value: `ctags`\r\n\r\n\r\n* `g:gencconf_ctags_option`\r\n\r\n Set ctags option.<\/br>\r\n default value: `--languages=c++ --languages=+c`\r\n\r\n\r\n* `g:gencconf_autoload_tag`\r\n\r\n Auto load tags in root_marker.<\/br>\r\n default value: `1`\r\n\r\n\r\n## Commands\r\n* `:GenClangConf`\r\n\r\n Gen `compile_flags.txt` in root_marker's parent dir, it will add all the directories<\/br>\r\n containing the specified suffix files.<\/br>\r\n if not found root_marker dir, gen `compile_flags.txt` in current dir.\r\n\r\n* `:ClearClangConf`\r\n\r\n Remove the generated file.\r\n\r\n* `:GenCtags`\r\n\r\n Gen `prj_tags` in root_marker's dir.<\/br>\r\n if not found root_marker dir, gen in current dir.\r\n\r\n* `:ClearCtags`\r\n\r\n Remove the generated tags.\r\n\r\n\r\nGithub:\r\nhttps:\/\/github.com\/fcying\/gen_clang_conf.vim","install_details":"vim-plug: Plug 'fcying\/gen_clang_conf.vim'\r\nor untar in ~\/.vim","5":"vim-plug: Plug 'fcying\/gen_clang_conf.vim'\r\nor untar in ~\/.vim","first_name":"fcy","6":"fcy","last_name":"ing","7":"ing","releases":[{"0":"5933","vim_version":"7.0","1":"7.0","script_version":"1.1","2":"1.1","version_comment":"support ctags\r\nsupport gen compile_commands.json","3":"support ctags\r\nsupport gen compile_commands.json","package":"gen_clang_conf.vim-master.zip","4":"gen_clang_conf.vim-master.zip","src_id":"27772","5":"27772","creation_date":"1633560668","6":"1633560668"},{"0":"5933","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"gen_clang_conf.vim-master.zip","4":"gen_clang_conf.vim-master.zip","src_id":"27461","5":"27461","creation_date":"1612291403","6":"1612291403"}]},"5932":{"script_id":"5932","0":"5932","script_name":"vim-auto-popmenu","1":"vim-auto-popmenu","script_type":"utility","2":"utility","summary":"Display the Completion Menu Automantically (next AutoComplPop) !! ","3":"Display the Completion Menu Automantically (next AutoComplPop) !! ","description":" A tiny and portable script (169 lines) to provide you YouCompleteMe like experience for buffer, \r\n dictionary and tags completion without installing heavy completion engines and building \r\n background servers.\r\n\r\nHomePage: \r\n\r\n https:\/\/github.com\/skywind3000\/vim-auto-popmenu\r\n\r\nWhat Is It ?\r\n\r\n Semantic completion is great, but sometimes, when you are coding in an obscure laguange \r\n which is lack of LSP support, or you are working in a temporary system and you don't want \r\n waste time to set up a heavyweight completion engine and build a background server.\r\n\r\n In these circumstances, vim's built-in completion system is good enough for you, it can \r\n collect keywords from buffers and dictionary or ctag files, but requires you to press or \r\n manually.\r\n\r\n This tiny little script will help you to trigger the completion menu when you have entered \r\n 1 or 2 alphabets and provide you exact the same experience like YouCompleteMe:\r\n\r\nScreenshot:\r\n\r\n https:\/\/raw.githubusercontent.com\/skywind3000\/images\/master\/p\/auto-popmenu\/demo.gif\r\n\r\nFeatures:\r\n\r\n - Popup the completion menu automatically.\r\n - Tab or shift+TAB to cycle keywords, to cancel.\r\n - Same experience like YouCompleteMe for buffer, dict and tags completion.\r\n - Green, everything is local to buffer, will not pollute your vim or disturb other plugins.\r\n - Capable to co-exist with other completion plugins.\r\n - No heavy engines, no need to build background servers.\r\n - Faster and more handy than the old famous AutoComplPop.\r\n - Portable, just a simple apc.vim script, easy to be distributed.\r\n - Only 169 lines, you can even copy it to your vimrc.\r\n - Convenience as a backup way for big completion plugins.\r\n","4":" A tiny and portable script (169 lines) to provide you YouCompleteMe like experience for buffer, \r\n dictionary and tags completion without installing heavy completion engines and building \r\n background servers.\r\n\r\nHomePage: \r\n\r\n https:\/\/github.com\/skywind3000\/vim-auto-popmenu\r\n\r\nWhat Is It ?\r\n\r\n Semantic completion is great, but sometimes, when you are coding in an obscure laguange \r\n which is lack of LSP support, or you are working in a temporary system and you don't want \r\n waste time to set up a heavyweight completion engine and build a background server.\r\n\r\n In these circumstances, vim's built-in completion system is good enough for you, it can \r\n collect keywords from buffers and dictionary or ctag files, but requires you to press or \r\n manually.\r\n\r\n This tiny little script will help you to trigger the completion menu when you have entered \r\n 1 or 2 alphabets and provide you exact the same experience like YouCompleteMe:\r\n\r\nScreenshot:\r\n\r\n https:\/\/raw.githubusercontent.com\/skywind3000\/images\/master\/p\/auto-popmenu\/demo.gif\r\n\r\nFeatures:\r\n\r\n - Popup the completion menu automatically.\r\n - Tab or shift+TAB to cycle keywords, to cancel.\r\n - Same experience like YouCompleteMe for buffer, dict and tags completion.\r\n - Green, everything is local to buffer, will not pollute your vim or disturb other plugins.\r\n - Capable to co-exist with other completion plugins.\r\n - No heavy engines, no need to build background servers.\r\n - Faster and more handy than the old famous AutoComplPop.\r\n - Portable, just a simple apc.vim script, easy to be distributed.\r\n - Only 169 lines, you can even copy it to your vimrc.\r\n - Convenience as a backup way for big completion plugins.\r\n","install_details":"\r\n Plug 'skywind3000\/vim-auto-popmenu'\r\n\r\n \" enable this plugin for filetypes, '*' for all files.\r\n let g:apc_enable_ft = {'text':1, 'markdown':1, 'php':1}\r\n\r\n \" source for dictionary, current or other loaded buffers, see ':help cpt'\r\n set cpt=.,k,w,b\r\n\r\n \" don't select the first item.\r\n set completeopt=menu,menuone,noselect\r\n\r\n \" suppress annoy messages.\r\n set shortmess+=c","5":"\r\n Plug 'skywind3000\/vim-auto-popmenu'\r\n\r\n \" enable this plugin for filetypes, '*' for all files.\r\n let g:apc_enable_ft = {'text':1, 'markdown':1, 'php':1}\r\n\r\n \" source for dictionary, current or other loaded buffers, see ':help cpt'\r\n set cpt=.,k,w,b\r\n\r\n \" don't select the first item.\r\n set completeopt=menu,menuone,noselect\r\n\r\n \" suppress annoy messages.\r\n set shortmess+=c","first_name":"Wei","6":"Wei","last_name":"Lin","7":"Lin","releases":[{"0":"5932","vim_version":"7.4","1":"7.4","script_version":"1.0.2","2":"1.0.2","version_comment":"new option g:apc_cr_confirm to change behavior.","3":"new option g:apc_cr_confirm to change behavior.","package":"apc.vim","4":"apc.vim","src_id":"27528","5":"27528","creation_date":"1615510006","6":"1615510006"},{"0":"5932","vim_version":"7.4","1":"7.4","script_version":"1.0.1","2":"1.0.1","version_comment":"fixed: stop working when set hidden.","3":"fixed: stop working when set hidden.","package":"apc.vim","4":"apc.vim","src_id":"27522","5":"27522","creation_date":"1615075902","6":"1615075902"},{"0":"5932","vim_version":"7.4","1":"7.4","script_version":"1.0.0","2":"1.0.0","version_comment":"Initial upload","3":"Initial upload","package":"apc.vim","4":"apc.vim","src_id":"27456","5":"27456","creation_date":"1611686984","6":"1611686984"}]},"5931":{"script_id":"5931","0":"5931","script_name":"tangram.vim","1":"tangram.vim","script_type":"utility","2":"utility","summary":"Lightes snippet plugin in the vim market! Only ~90 lines of code.","3":"Lightes snippet plugin in the vim market! Only ~90 lines of code.","description":"This is the 'raw' branch of tangram.vim. Check https:\/\/github.com\/jpaulogg\/vim-tangram for more info.\r\n\r\nThis plugin was written in an attempt to be simple enough that users could make any changes directly to it. I believe that this gives users more control and a wider range of possible changes. In addition, the script has comments that help to make some customizations. It's almost as simple as doing it in your vimrc.\r\n\r\nUsage: i inserts snippets files (ex: foo.snip) from tangram-directorie (by default ~\/.config\/nvim\/snippets\/{filetype}). Create placeholders with delimiters '<{' and '}>' in your snippets files. Jump through placeholders with n and p. e expands vim expressions within a placeholder and r prompts for a text to replace all ocurrences of seleceted placeholder.","4":"This is the 'raw' branch of tangram.vim. Check https:\/\/github.com\/jpaulogg\/vim-tangram for more info.\r\n\r\nThis plugin was written in an attempt to be simple enough that users could make any changes directly to it. I believe that this gives users more control and a wider range of possible changes. In addition, the script has comments that help to make some customizations. It's almost as simple as doing it in your vimrc.\r\n\r\nUsage: i inserts snippets files (ex: foo.snip) from tangram-directorie (by default ~\/.config\/nvim\/snippets\/{filetype}). Create placeholders with delimiters '<{' and '}>' in your snippets files. Jump through placeholders with n and p. e expands vim expressions within a placeholder and r prompts for a text to replace all ocurrences of seleceted placeholder.","install_details":"Copy tangram.vim file to \"plugin\" directory in your runtime.","5":"Copy tangram.vim file to \"plugin\" directory in your runtime.","first_name":"Jo\u00c3\u00a3o","6":"Jo\u00c3\u00a3o","last_name":"Garcia","7":"Garcia","releases":[{"0":"5931","vim_version":"7.0","1":"7.0","script_version":"v2","2":"v2","version_comment":"Better completion function","3":"Better completion function","package":"tangram.vim","4":"tangram.vim","src_id":"27471","5":"27471","creation_date":"1612657563","6":"1612657563"},{"0":"5931","vim_version":"7.0","1":"7.0","script_version":"v1","2":"v1","version_comment":"Initial upload","3":"Initial upload","package":"tangram.vim","4":"tangram.vim","src_id":"27454","5":"27454","creation_date":"1611546928","6":"1611546928"}]},"5930":{"script_id":"5930","0":"5930","script_name":"vim-simplified-surround","1":"vim-simplified-surround","script_type":"utility","2":"utility","summary":"Very simplified version of Tpope's vim-surround.","3":"Very simplified version of Tpope's vim-surround.","description":"I wrote this script because the way \"(\" and \")\" works differently in the Tpope's plugin confuses me. I prefer to deal with the spaces separately. Also because I like to keep things minimal. Check https:\/\/github.com\/jpaulogg\/vim-simplified-surround for more info.\r\n\r\nThis plugin was written in an attempt to be simple enough that users could make any changes directly to it. I believe that this gives users more control and a wider range of possible changes. In addition, the script has comments that help to make some customizations (for example, to create custom pairs). It's almost as simple as doing it in your vimrc.\r\n\r\nUsage: ys{motion}{character} in normal mode surrounds motion with character pair. ds{character} deletes it and cs{char1}{char2} changes it to 'char2'. S{character} surrounds selection in visual mode.\r\n\r\n","4":"I wrote this script because the way \"(\" and \")\" works differently in the Tpope's plugin confuses me. I prefer to deal with the spaces separately. Also because I like to keep things minimal. Check https:\/\/github.com\/jpaulogg\/vim-simplified-surround for more info.\r\n\r\nThis plugin was written in an attempt to be simple enough that users could make any changes directly to it. I believe that this gives users more control and a wider range of possible changes. In addition, the script has comments that help to make some customizations (for example, to create custom pairs). It's almost as simple as doing it in your vimrc.\r\n\r\nUsage: ys{motion}{character} in normal mode surrounds motion with character pair. ds{character} deletes it and cs{char1}{char2} changes it to 'char2'. S{character} surrounds selection in visual mode.\r\n\r\n","install_details":"Just copy surround.vim to the \"plugin\" directory in your runtime.","5":"Just copy surround.vim to the \"plugin\" directory in your runtime.","first_name":"Jo\u00c3\u00a3o","6":"Jo\u00c3\u00a3o","last_name":"Garcia","7":"Garcia","releases":[{"0":"5930","vim_version":"7.0","1":"7.0","script_version":"v1","2":"v1","version_comment":"Initial upload","3":"Initial upload","package":"surround.vim","4":"surround.vim","src_id":"27453","5":"27453","creation_date":"1611546462","6":"1611546462"}]},"5929":{"script_id":"5929","0":"5929","script_name":"leftmargin.vim","1":"leftmargin.vim","script_type":"utility","2":"utility","summary":"Vim plugin that adds left margin to vim windows. Similar to goyo.vim","3":"Vim plugin that adds left margin to vim windows. Similar to goyo.vim","description":"I wrote this script because I don't like the way the goyo.vim plugin handles windows and statusline. Also because I like to keep things minimal. Check https:\/\/github.com\/jpaulogg\/vim-leftmargin for more info.\r\n\r\nThis plugin was written in an attempt to be simple enough that users could make any changes directly to it. I believe that this gives users more control and a wider range of possible changes. In addition, the script has comments that help to make some customizations (for example, hide the statusline). It's almost as simple as doing it on your `vimrc`.\r\n\r\nCommands: 'LeftMargin' adds left margin to current window; 'NoMargin' removes it.\r\nMapping: p toggles left margin.","4":"I wrote this script because I don't like the way the goyo.vim plugin handles windows and statusline. Also because I like to keep things minimal. Check https:\/\/github.com\/jpaulogg\/vim-leftmargin for more info.\r\n\r\nThis plugin was written in an attempt to be simple enough that users could make any changes directly to it. I believe that this gives users more control and a wider range of possible changes. In addition, the script has comments that help to make some customizations (for example, hide the statusline). It's almost as simple as doing it on your `vimrc`.\r\n\r\nCommands: 'LeftMargin' adds left margin to current window; 'NoMargin' removes it.\r\nMapping: p toggles left margin.","install_details":"Just copy leftmargin.vim to the \"plugin\" directory in your runtime.","5":"Just copy leftmargin.vim to the \"plugin\" directory in your runtime.","first_name":"Jo\u00c3\u00a3o","6":"Jo\u00c3\u00a3o","last_name":"Garcia","7":"Garcia","releases":[{"0":"5929","vim_version":"7.0","1":"7.0","script_version":"v2","2":"v2","version_comment":"Better \"width\" function","3":"Better \"width\" function","package":"leftmargin.vim","4":"leftmargin.vim","src_id":"27472","5":"27472","creation_date":"1612657701","6":"1612657701"},{"0":"5929","vim_version":"7.0","1":"7.0","script_version":"v1","2":"v1","version_comment":"Initial upload","3":"Initial upload","package":"leftmargin.vim","4":"leftmargin.vim","src_id":"27452","5":"27452","creation_date":"1611546290","6":"1611546290"}]},"5928":{"script_id":"5928","0":"5928","script_name":"conjoin","1":"conjoin","script_type":"utility","2":"utility","summary":"Remove continuation characters when joining lines in vim","3":"Remove continuation characters when joining lines in vim","description":"conjoin is a plugin that handles line joining in the presence of line continuation characters. Vim's normal behavior for `J` and `:join` on the following shell script:\r\n cat file.txt \\\r\n | sort \\\r\n | uniq -c\r\nleaves the backslash continuation characters in place:\r\n cat file.txt \\ | sort \\ | uniq -c\r\nWith conjoin, running join commands will produce\r\n cat file.txt | sort | uniq -c\r\n\r\nString literals concatenated over several lines in languages like Python and Java are merged too.\r\n\r\nBy default, conjoin will create mappings for `J` and `gJ` as well as a `:Join` command. If a mapping already exists, conjoin will call the prior mapping after removing continuation characters. This lets it work well with splitjoin (vimscript #3613) as long as splitjoin appears before conjoin in runtimepath.\r\n\r\nconjoin comes with support for continuation characters in many programming languages. See `:help conjoin` or https:\/\/github.com\/flwyd\/vim-conjoin for details on defining your own.","4":"conjoin is a plugin that handles line joining in the presence of line continuation characters. Vim's normal behavior for `J` and `:join` on the following shell script:\r\n cat file.txt \\\r\n | sort \\\r\n | uniq -c\r\nleaves the backslash continuation characters in place:\r\n cat file.txt \\ | sort \\ | uniq -c\r\nWith conjoin, running join commands will produce\r\n cat file.txt | sort | uniq -c\r\n\r\nString literals concatenated over several lines in languages like Python and Java are merged too.\r\n\r\nBy default, conjoin will create mappings for `J` and `gJ` as well as a `:Join` command. If a mapping already exists, conjoin will call the prior mapping after removing continuation characters. This lets it work well with splitjoin (vimscript #3613) as long as splitjoin appears before conjoin in runtimepath.\r\n\r\nconjoin comes with support for continuation characters in many programming languages. See `:help conjoin` or https:\/\/github.com\/flwyd\/vim-conjoin for details on defining your own.","install_details":"Unzip the script package and add the path to vim-conjoin to your runtimepath. Alternatively, use a plugin manager:\r\n\" vim-plug:\r\nPlug 'flwyd\/vim-conjoin'\r\n\" Vundle:\r\nPlugin 'flwyd\/vim-conjoin'\r\n\" vim-addon-manager\r\nVAMActivate github:flwyd\/vim-conjoin","5":"Unzip the script package and add the path to vim-conjoin to your runtimepath. Alternatively, use a plugin manager:\r\n\" vim-plug:\r\nPlug 'flwyd\/vim-conjoin'\r\n\" Vundle:\r\nPlugin 'flwyd\/vim-conjoin'\r\n\" vim-addon-manager\r\nVAMActivate github:flwyd\/vim-conjoin","first_name":"Trevor","6":"Trevor","last_name":"Stone","7":"Stone","releases":[{"0":"5928","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"vim-conjoin-1_0.zip","4":"vim-conjoin-1_0.zip","src_id":"27451","5":"27451","creation_date":"1611498673","6":"1611498673"}]},"5927":{"script_id":"5927","0":"5927","script_name":"vim-files","1":"vim-files","script_type":"utility","2":"utility","summary":"This is a simple plugin to create directories and files from vim, and even using","3":"This is a simple plugin to create directories and files from vim, and even using","description":"With vim open in the path ~\/Projects\/test, I call the VimFiles#CreateDir() function, and enter python\/component, the result is that now I have this complete path ~\/Projects\/test\/python\/component\r\n\r\nWith vim open in the path ~\/Projects\/test, I call the VimFiles#CreateFile() function, and enter python\/view\/User.py, the result is that now the file is created and also opened, if not have the necessary folders created, the function will create them\r\n\r\nFor more detailed, better formatted documentation, see the README on GitHub:\r\n\r\nhttp:\/\/github.com\/SergioRibera\/vim-files","4":"With vim open in the path ~\/Projects\/test, I call the VimFiles#CreateDir() function, and enter python\/component, the result is that now I have this complete path ~\/Projects\/test\/python\/component\r\n\r\nWith vim open in the path ~\/Projects\/test, I call the VimFiles#CreateFile() function, and enter python\/view\/User.py, the result is that now the file is created and also opened, if not have the necessary folders created, the function will create them\r\n\r\nFor more detailed, better formatted documentation, see the README on GitHub:\r\n\r\nhttp:\/\/github.com\/SergioRibera\/vim-files","install_details":"Plug 'SergioRibera\/vim-files'","5":"Plug 'SergioRibera\/vim-files'","first_name":"Sergio Alejandro","6":"Sergio Alejandro","last_name":"Ribera Costa","7":"Ribera Costa","releases":[{"0":"5927","vim_version":"7.0","1":"7.0","script_version":"2.2","2":"2.2","version_comment":"Added all functions for file manipulation, refactoring and changing namespaces, Please, I recommend installing it as indicated in the repository so that you can have the correct updates and on time http:\/\/github.com\/SergioRibera\/vim-files","3":"Added all functions for file manipulation, refactoring and changing namespaces, Please, I recommend installing it as indicated in the repository so that you can have the correct updates and on time http:\/\/github.com\/SergioRibera\/vim-files","package":"vim-files.tar.gz","4":"vim-files.tar.gz","src_id":"27450","5":"27450","creation_date":"1611335801","6":"1611335801"},{"0":"5927","vim_version":"7.0","1":"7.0","script_version":"2.1","2":"2.1","version_comment":"Fix somes bugs and add new Images to odcumentation, you can see the complete documentation on http:\/\/github.com\/SergioRibera\/vim-files\/wiki","3":"Fix somes bugs and add new Images to odcumentation, you can see the complete documentation on http:\/\/github.com\/SergioRibera\/vim-files\/wiki","package":"vim-files.tar.gz","4":"vim-files.tar.gz","src_id":"27449","5":"27449","creation_date":"1611132794","6":"1611132794"},{"0":"5927","vim_version":"7.0","1":"7.0","script_version":"2.0","2":"2.0","version_comment":"Simple added template system, also allow creating a directory structure with a single command","3":"Simple added template system, also allow creating a directory structure with a single command","package":"vim-files.tar.gz","4":"vim-files.tar.gz","src_id":"27447","5":"27447","creation_date":"1611124088","6":"1611124088"},{"0":"5927","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"vim-files.tar.gz","4":"vim-files.tar.gz","src_id":"27446","5":"27446","creation_date":"1611115647","6":"1611115647"}]},"5926":{"script_id":"5926","0":"5926","script_name":"vim-shitespace","1":"vim-shitespace","script_type":"utility","2":"utility","summary":"Show bad whitespace","3":"Show bad whitespace","description":"Highlights all the bad whitespace in your files:\r\n\r\n- Whitespace at the end of lines\r\n- Spaces followed by tabs\r\n- Mixed tabs and spaces (if configured)\r\n\r\nGitLab project: https:\/\/gitlab.com\/h3xx\/vim-shitespace","4":"Highlights all the bad whitespace in your files:\r\n\r\n- Whitespace at the end of lines\r\n- Spaces followed by tabs\r\n- Mixed tabs and spaces (if configured)\r\n\r\nGitLab project: https:\/\/gitlab.com\/h3xx\/vim-shitespace","install_details":"Just untar into your ~\/.vim directory, or use the following to get the latest version from Git:\r\n\r\nVim 8+:\r\nmkdir -p ~\/.vim\/pack\/dist\/start\r\ngit clone https:\/\/gitlab.com\/h3xx\/vim-shitespace.git ~\/.vim\/pack\/dist\/start\/vim-shitespace\r\n\r\nVim 7 and older:\r\nmkdir -p ~\/.vim\/{autoload,plugin}\r\nwget -O ~\/.vim\/autoload\/shitespace.vim https:\/\/gitlab.com\/h3xx\/vim-shitespace\/-\/raw\/main\/autoload\/shitespace.vim\r\nwget -O ~\/.vim\/plugin\/shitespace.vim https:\/\/gitlab.com\/h3xx\/vim-shitespace\/-\/raw\/main\/plugin\/shitespace.vim","5":"Just untar into your ~\/.vim directory, or use the following to get the latest version from Git:\r\n\r\nVim 8+:\r\nmkdir -p ~\/.vim\/pack\/dist\/start\r\ngit clone https:\/\/gitlab.com\/h3xx\/vim-shitespace.git ~\/.vim\/pack\/dist\/start\/vim-shitespace\r\n\r\nVim 7 and older:\r\nmkdir -p ~\/.vim\/{autoload,plugin}\r\nwget -O ~\/.vim\/autoload\/shitespace.vim https:\/\/gitlab.com\/h3xx\/vim-shitespace\/-\/raw\/main\/autoload\/shitespace.vim\r\nwget -O ~\/.vim\/plugin\/shitespace.vim https:\/\/gitlab.com\/h3xx\/vim-shitespace\/-\/raw\/main\/plugin\/shitespace.vim","first_name":"Dan","6":"Dan","last_name":"Church","7":"Church","releases":[{"0":"5926","vim_version":"7.0","1":"7.0","script_version":"0.3.1","2":"0.3.1","version_comment":"- Highlight fancy Unicode whitespace characters","3":"- Highlight fancy Unicode whitespace characters","package":"vim-shitespace-v0.3.1.tar.xz","4":"vim-shitespace-v0.3.1.tar.xz","src_id":"28259","5":"28259","creation_date":"1667972991","6":"1667972991"},{"0":"5926","vim_version":"7.0","1":"7.0","script_version":"0.3.0","2":"0.3.0","version_comment":"- Fix missing `match` call - if toggling on in the current file, it would fail to highlight\r\n- Remove automatic keystroke support\r\n- Add functions for explicitly toggling on\/off","3":"- Fix missing `match` call - if toggling on in the current file, it would fail to highlight\r\n- Remove automatic keystroke support\r\n- Add functions for explicitly toggling on\/off","package":"vim-shitespace-v0.3.0.tar.gz","4":"vim-shitespace-v0.3.0.tar.gz","src_id":"28240","5":"28240","creation_date":"1667004958","6":"1667004958"},{"0":"5926","vim_version":"7.0","1":"7.0","script_version":"0.2.0","2":"0.2.0","version_comment":"- Changed installation slightly (vim 7.x); 8.x is unaffected\r\n- Minor improvements","3":"- Changed installation slightly (vim 7.x); 8.x is unaffected\r\n- Minor improvements","package":"vim-shitespace-0.2.0.tar.xz","4":"vim-shitespace-0.2.0.tar.xz","src_id":"28194","5":"28194","creation_date":"1664511795","6":"1664511795"},{"0":"5926","vim_version":"7.0","1":"7.0","script_version":"0.1.0","2":"0.1.0","version_comment":"Initial upload","3":"Initial upload","package":"vim-shitespace-0.1.0.tar.xz","4":"vim-shitespace-0.1.0.tar.xz","src_id":"27445","5":"27445","creation_date":"1611033199","6":"1611033199"}]},"5925":{"script_id":"5925","0":"5925","script_name":"vim-numbers","1":"vim-numbers","script_type":"utility","2":"utility","summary":"Text objects for numbers","3":"Text objects for numbers","description":"A small plugin that provides text objects for numbers.\r\n\r\nDemo:\r\nhttps:\/\/raw.githubusercontent.com\/MisanthropicBit\/vim-numbers\/master\/vim-numbers-demo.gif\r\n\r\n- Typing van or vin selects an integral or floating-point number (optionally with scientific notation and\/or thousand separators).\r\n- Typing vai or vii selects a binary number (prefixed by 0b or 0B).\r\n- Typing vax or vix selects a hexadecimal number (prefixed by 0x, 0X, or #).\r\n- Typing vao or vio selects an octal number (prefixed by 0 or 0o).\r\n- There is no difference in selecting \"a number\" or \"inner number\".\r\n\r\nThe plugin is maintained at https:\/\/github.com\/MisanthropicBit\/vim-numbers.","4":"A small plugin that provides text objects for numbers.\r\n\r\nDemo:\r\nhttps:\/\/raw.githubusercontent.com\/MisanthropicBit\/vim-numbers\/master\/vim-numbers-demo.gif\r\n\r\n- Typing van or vin selects an integral or floating-point number (optionally with scientific notation and\/or thousand separators).\r\n- Typing vai or vii selects a binary number (prefixed by 0b or 0B).\r\n- Typing vax or vix selects a hexadecimal number (prefixed by 0x, 0X, or #).\r\n- Typing vao or vio selects an octal number (prefixed by 0 or 0o).\r\n- There is no difference in selecting \"a number\" or \"inner number\".\r\n\r\nThe plugin is maintained at https:\/\/github.com\/MisanthropicBit\/vim-numbers.","install_details":"Extract the zip in ~\/.vim (or ~\\vimfiles on Windows) or see https:\/\/github.com\/MisanthropicBit\/vim-numbers for alternative install details.","5":"Extract the zip in ~\/.vim (or ~\\vimfiles on Windows) or see https:\/\/github.com\/MisanthropicBit\/vim-numbers for alternative install details.","first_name":"","6":"","last_name":"","7":"","releases":[{"0":"5925","vim_version":"7.4","1":"7.4","script_version":"1.0.3","2":"1.0.3","version_comment":"* Fix number vselect contexts\r\n* Recognise comma-separated numbers with scientific notation\r\n* Add more test cases","3":"* Fix number vselect contexts\r\n* Recognise comma-separated numbers with scientific notation\r\n* Add more test cases","package":"vim-numbers-1.0.3.zip","4":"vim-numbers-1.0.3.zip","src_id":"27821","5":"27821","creation_date":"1638083700","6":"1638083700"},{"0":"5925","vim_version":"7.4","1":"7.4","script_version":"1.0.2","2":"1.0.2","version_comment":"Fix bug in selecting octal numbers at the beginning of lines, make selecting octal numbers with multiple valid prefixes (e.g. `041407357` more robust), update documentation with `0O` as a valid octal prefix.","3":"Fix bug in selecting octal numbers at the beginning of lines, make selecting octal numbers with multiple valid prefixes (e.g. `041407357` more robust), update documentation with `0O` as a valid octal prefix.","package":"vim-numbers-1.0.2.zip","4":"vim-numbers-1.0.2.zip","src_id":"27734","5":"27734","creation_date":"1631066607","6":"1631066607"},{"0":"5925","vim_version":"7.4","1":"7.4","script_version":"1.0.1","2":"1.0.1","version_comment":"Select octal numbers prefixed with a zero and capital o: '0O'.","3":"Select octal numbers prefixed with a zero and capital o: '0O'.","package":"vim-numbers-1.0.1.zip","4":"vim-numbers-1.0.1.zip","src_id":"27732","5":"27732","creation_date":"1630990111","6":"1630990111"},{"0":"5925","vim_version":"7.4","1":"7.4","script_version":"1.0.0","2":"1.0.0","version_comment":"Initial upload","3":"Initial upload","package":"vim-numbers-1.0.0.zip","4":"vim-numbers-1.0.0.zip","src_id":"27433","5":"27433","creation_date":"1609356798","6":"1609356798"}]},"5924":{"script_id":"5924","0":"5924","script_name":"vanity (colour scheme manager for vim)","1":"vanity (colour scheme manager for vim)","script_type":"utility","2":"utility","summary":"Manage vim colour schemes with ease","3":"Manage vim colour schemes with ease","description":"Cycle through colour schemes, set default, create a favourite list: \r\n \r\nRecommended mapping for cycling through colour schemes: \r\nnnoremap :call VPrevCol()\r\nnnoremap :call VNextCol()\r\n \r\n\r\nREADME: https:\/\/github.com\/whatever555\/vanity\r\n","4":"Cycle through colour schemes, set default, create a favourite list: \r\n \r\nRecommended mapping for cycling through colour schemes: \r\nnnoremap :call VPrevCol()\r\nnnoremap :call VNextCol()\r\n \r\n\r\nREADME: https:\/\/github.com\/whatever555\/vanity\r\n","install_details":"https:\/\/github.com\/whatever555\/vanity#installation\r\n \r\nVundle: \r\nPlugin 'whatever555\/vanity'","5":"https:\/\/github.com\/whatever555\/vanity#installation\r\n \r\nVundle: \r\nPlugin 'whatever555\/vanity'","first_name":"what","6":"what","last_name":"ever","7":"ever","releases":[{"0":"5924","vim_version":"7.0","1":"7.0","script_version":"0.1.1","2":"0.1.1","version_comment":"Fixed issues with neovim","3":"Fixed issues with neovim","package":"vanity.vim","4":"vanity.vim","src_id":"27826","5":"27826","creation_date":"1638515409","6":"1638515409"},{"0":"5924","vim_version":"8.0","1":"8.0","script_version":"0.1.0","2":"0.1.0","version_comment":"Added commands","3":"Added commands","package":"vanity.vim","4":"vanity.vim","src_id":"27438","5":"27438","creation_date":"1609837040","6":"1609837040"},{"0":"5924","vim_version":"8.0","1":"8.0","script_version":"0.0.1","2":"0.0.1","version_comment":"Initial upload","3":"Initial upload","package":"vanity.vim","4":"vanity.vim","src_id":"27421","5":"27421","creation_date":"1609147369","6":"1609147369"}]},"5923":{"script_id":"5923","0":"5923","script_name":"gift.vim","1":"gift.vim","script_type":"syntax","2":"syntax","summary":"Syntax Highlighting for Moodle's GIFT format","3":"Syntax Highlighting for Moodle's GIFT format","description":"Syntax highlighting for the popular learning management system Moodle's GIFT (General Import Format Template) format.\r\n\r\nMore information and other Moodle GIFT tools are available on:\r\n\r\nhttp:\/\/selimtemizer.com\/software\/gift","4":"Syntax highlighting for the popular learning management system Moodle's GIFT (General Import Format Template) format.\r\n\r\nMore information and other Moodle GIFT tools are available on:\r\n\r\nhttp:\/\/selimtemizer.com\/software\/gift","install_details":"Copy the file in the following folder:\r\n\r\nOn *nix : ~\/.vim\/syntax\r\nOn Windows: $vim\\vimfiles\\syntax","5":"Copy the file in the following folder:\r\n\r\nOn *nix : ~\/.vim\/syntax\r\nOn Windows: $vim\\vimfiles\\syntax","first_name":"Selim","6":"Selim","last_name":"Temizer","7":"Temizer","releases":[{"0":"5923","vim_version":"7.0","1":"7.0","script_version":"1.1","2":"1.1","version_comment":"\"set\" is replaced with \"setlocal\".","3":"\"set\" is replaced with \"setlocal\".","package":"gift.vim","4":"gift.vim","src_id":"27418","5":"27418","creation_date":"1608855151","6":"1608855151"},{"0":"5923","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"gift.vim","4":"gift.vim","src_id":"27417","5":"27417","creation_date":"1608799770","6":"1608799770"}]},"5922":{"script_id":"5922","0":"5922","script_name":"vim-highlight-hero","1":"vim-highlight-hero","script_type":"syntax","2":"syntax","summary":"Highlights multiple words and visual selections in different colors","3":"Highlights multiple words and visual selections in different colors","description":"The highlight-hero highlights multiple words and visual selections in different colors.\r\nIt is particularly useful for\r\n\r\n- spotting typos\r\n- finding variable usages\r\n- resolving merge conflicts (see :help highlight-hero-merge-conflicts)\r\n\r\nQuick start >> :HHauto or :HH, :1HH!, ...\r\n","4":"The highlight-hero highlights multiple words and visual selections in different colors.\r\nIt is particularly useful for\r\n\r\n- spotting typos\r\n- finding variable usages\r\n- resolving merge conflicts (see :help highlight-hero-merge-conflicts)\r\n\r\nQuick start >> :HHauto or :HH, :1HH!, ...\r\n","install_details":"As all other plugins. Example for Plug:\r\n\r\ncall plug#begin()\r\n Plug 'borisbrodski\/vim-highlight-hero'\r\ncall plug#end()\r\n","5":"As all other plugins. Example for Plug:\r\n\r\ncall plug#begin()\r\n Plug 'borisbrodski\/vim-highlight-hero'\r\ncall plug#end()\r\n","first_name":"Boris","6":"Boris","last_name":"Brodski","7":"Brodski","releases":[{"0":"5922","vim_version":"8.0","1":"8.0","script_version":"0.9","2":"0.9","version_comment":"Initial upload","3":"Initial upload","package":"vim-highlight-hero-0.9.zip","4":"vim-highlight-hero-0.9.zip","src_id":"27416","5":"27416","creation_date":"1608764304","6":"1608764304"}]},"5921":{"script_id":"5921","0":"5921","script_name":"NERDTree react\/ts component ","1":"NERDTree react\/ts component ","script_type":"ftplugin","2":"ftplugin","summary":"Adds an option for adding react component folders through NERDTree","3":"Adds an option for adding react component folders through NERDTree","description":"https:\/\/github.com\/whatever555\/nerdtree-react-component\r\n\r\nAdds an option for adding react component folders through NERDTree","4":"https:\/\/github.com\/whatever555\/nerdtree-react-component\r\n\r\nAdds an option for adding react component folders through NERDTree","install_details":"Vundle install: \r\nPlugin 'whatever555\/nerdtree-react-component'\r\n\r\nvim-plug install:\r\nPlug 'whatever555\/nerdtree-react-component'","5":"Vundle install: \r\nPlugin 'whatever555\/nerdtree-react-component'\r\n\r\nvim-plug install:\r\nPlug 'whatever555\/nerdtree-react-component'","first_name":"what","6":"what","last_name":"ever","7":"ever","releases":[{"0":"5921","vim_version":"7.0","1":"7.0","script_version":"0.0.1","2":"0.0.1","version_comment":"Initial upload","3":"Initial upload","package":"NERD_tree_react_components.vim","4":"NERD_tree_react_components.vim","src_id":"27406","5":"27406","creation_date":"1608352090","6":"1608352090"}]},"5920":{"script_id":"5920","0":"5920","script_name":"vim-earthbound-themes","1":"vim-earthbound-themes","script_type":"color scheme","2":"color scheme","summary":"A set of 10+ color themes inspired by the SNES game Earthbound","3":"A set of 10+ color themes inspired by the SNES game Earthbound","description":"Vim color schemes inspired by the memorable and bizarre locations from the Super Nintendo game Earthbound (aka Mother 2).\r\n\r\nThe set of themes contains over 10 different themes, including a light theme and two monochromatic themes. All themes are generated using a single Lua build script, and are available for other editors as well. \r\n\r\nGitHub: https:\/\/github.com\/benbusby\/earthbound-themes\r\n\r\nVim-specific submodule: https:\/\/github.com\/benbusby\/vim-earthbound-themes","4":"Vim color schemes inspired by the memorable and bizarre locations from the Super Nintendo game Earthbound (aka Mother 2).\r\n\r\nThe set of themes contains over 10 different themes, including a light theme and two monochromatic themes. All themes are generated using a single Lua build script, and are available for other editors as well. \r\n\r\nGitHub: https:\/\/github.com\/benbusby\/earthbound-themes\r\n\r\nVim-specific submodule: https:\/\/github.com\/benbusby\/vim-earthbound-themes","install_details":"-- Vundle --\r\nPlugin 'benbusby\/vim-earthbound-themes'\r\n\r\n-- vim-plug --\r\nPlug 'benbusby\/vim-earthbound-themes'\r\n\r\nDownload the latest release zip\/tar.gz from https:\/\/github.com\/benbusby\/vim-earthbound-themes\/releases\r\n\r\nIf you want to build\/customize the themes yourself, you can clone the parent repo and generate the themes to your heart's content:\r\n\r\ngit clone https:\/\/github.com\/benbusby\/earthbound-themes.git\r\ncd earthbound-themes\r\ngit submodule init\r\ngit submodule update\r\n.\/build.lua vim","5":"-- Vundle --\r\nPlugin 'benbusby\/vim-earthbound-themes'\r\n\r\n-- vim-plug --\r\nPlug 'benbusby\/vim-earthbound-themes'\r\n\r\nDownload the latest release zip\/tar.gz from https:\/\/github.com\/benbusby\/vim-earthbound-themes\/releases\r\n\r\nIf you want to build\/customize the themes yourself, you can clone the parent repo and generate the themes to your heart's content:\r\n\r\ngit clone https:\/\/github.com\/benbusby\/earthbound-themes.git\r\ncd earthbound-themes\r\ngit submodule init\r\ngit submodule update\r\n.\/build.lua vim","first_name":"Ben","6":"Ben","last_name":"Busby","7":"Busby","releases":[{"0":"5920","vim_version":"7.0","1":"7.0","script_version":"1.1.0","2":"1.1.0","version_comment":"Add \"Devil's Machine\" theme","3":"Add \"Devil's Machine\" theme","package":"vim-earthbound-themes.tar.gz","4":"vim-earthbound-themes.tar.gz","src_id":"27627","5":"27627","creation_date":"1623486427","6":"1623486427"},{"0":"5920","vim_version":"7.0","1":"7.0","script_version":"1.0.2","2":"1.0.2","version_comment":"Add support for notermguicolors \/ cterm theme colors","3":"Add support for notermguicolors \/ cterm theme colors","package":"vim-earthbound-themes.tar.gz","4":"vim-earthbound-themes.tar.gz","src_id":"27415","5":"27415","creation_date":"1608711542","6":"1608711542"},{"0":"5920","vim_version":"7.0","1":"7.0","script_version":"1.0.1","2":"1.0.1","version_comment":"Fix TODO\/FIXME tag contrast\r\nRemove unnecessary underline on constants","3":"Fix TODO\/FIXME tag contrast\r\nRemove unnecessary underline on constants","package":"vim-earthbound-themes.tar.gz","4":"vim-earthbound-themes.tar.gz","src_id":"27405","5":"27405","creation_date":"1608329970","6":"1608329970"},{"0":"5920","vim_version":"7.0","1":"7.0","script_version":"1.0.0","2":"1.0.0","version_comment":"Initial upload","3":"Initial upload","package":"vim-earthbound-themes.tar.gz","4":"vim-earthbound-themes.tar.gz","src_id":"27404","5":"27404","creation_date":"1608189909","6":"1608189909"}]},"5919":{"script_id":"5919","0":"5919","script_name":"jreplace.vim","1":"jreplace.vim","script_type":"utility","2":"utility","summary":"Repeat you last SEARCH+REPLACE with your grepprg","3":"Repeat you last SEARCH+REPLACE with your grepprg","description":"Searches files under the current directory,\r\nlooking for your last search pattern with your grepprg\r\nto replace occurrences in the next quickfix target line\r\nwith the same replacement you just did before calling this script.\r\n...closely organized like jcallers script is .. @see Vim wiki\r\n\r\n1 - Starts with a :normal mA .. AS A GLOBAL MARK [A] .. you can jump back to as a return point.\r\n2 - Calls your grepprg to build a quickfix list used to navigate to the next occurrence under the current working directory.\r\n3 - Each call to the content of the [q register] with the @q command will attempt the next replacement.\r\n4 - The result is a highlighted replaced text you can undo at will before your next call to @q.\r\n5 - Lets you navigate the grep quickfix resulting list to review or undo any of those replacements.\r\n6 - Calling @q while moving back and forth the quickfix list will attempt the next replacement from that slot.\r\n\r\nNotes:\r\n- F_replace(old,new) function applies a global substitute of all occurrences on each quickfix-target-line.\r\n\r\n- USES [A global mark] as a call return point.\r\n...(there are 2 calls to [A mark] you can adjust to use another mark :normal mA and :normal 'A\r\n\r\n- USES [q register] to store jump and replacement for the next quickfix entry.\r\n...@q will execute the next substitution\r\n...you can check the results one step at a time\r\n...( :nnoremap Q @q .. may help )","4":"Searches files under the current directory,\r\nlooking for your last search pattern with your grepprg\r\nto replace occurrences in the next quickfix target line\r\nwith the same replacement you just did before calling this script.\r\n...closely organized like jcallers script is .. @see Vim wiki\r\n\r\n1 - Starts with a :normal mA .. AS A GLOBAL MARK [A] .. you can jump back to as a return point.\r\n2 - Calls your grepprg to build a quickfix list used to navigate to the next occurrence under the current working directory.\r\n3 - Each call to the content of the [q register] with the @q command will attempt the next replacement.\r\n4 - The result is a highlighted replaced text you can undo at will before your next call to @q.\r\n5 - Lets you navigate the grep quickfix resulting list to review or undo any of those replacements.\r\n6 - Calling @q while moving back and forth the quickfix list will attempt the next replacement from that slot.\r\n\r\nNotes:\r\n- F_replace(old,new) function applies a global substitute of all occurrences on each quickfix-target-line.\r\n\r\n- USES [A global mark] as a call return point.\r\n...(there are 2 calls to [A mark] you can adjust to use another mark :normal mA and :normal 'A\r\n\r\n- USES [q register] to store jump and replacement for the next quickfix entry.\r\n...@q will execute the next substitution\r\n...you can check the results one step at a time\r\n...( :nnoremap Q @q .. may help )","install_details":"- put the file where you put your other scripts (it has no dependency)\r\n- then map something to source it.\r\n...mine is:\r\n:nnoremap r :so ~\/VIM\/scripts\/jreplace.vim\r\n\r\n...and the mass-destruction version:\r\n:nmap r :so ~\/VIM\/scripts\/jreplace.vim:silent! normal 99Q:silent normal z.:crew:cn","5":"- put the file where you put your other scripts (it has no dependency)\r\n- then map something to source it.\r\n...mine is:\r\n:nnoremap r :so ~\/VIM\/scripts\/jreplace.vim\r\n\r\n...and the mass-destruction version:\r\n:nmap r :so ~\/VIM\/scripts\/jreplace.vim:silent! normal 99Q:silent normal z.:crew:cn","first_name":"ivan","6":"ivan","last_name":"wellesz","7":"wellesz","releases":[{"0":"5919","vim_version":"7.0","1":"7.0","script_version":"201209","2":"201209","version_comment":"Initial upload","3":"Initial upload","package":"jreplace.vim","4":"jreplace.vim","src_id":"27398","5":"27398","creation_date":"1607570866","6":"1607570866"}]},"5918":{"script_id":"5918","0":"5918","script_name":"vim-ffs","1":"vim-ffs","script_type":"utility","2":"utility","summary":"Web searching scoped to the current filetype","3":"Web searching scoped to the current filetype","description":"Run the current word or a given query through a search engine along with the current filetype to give more relevant, focused search results.\r\n\r\nComes with some configuration options to provide more customisation over the scope of the search, for example scoping searches from kubernetes yaml configuration files to ensure that searches come with a predefined scope of kubernetes (or kubectl, k8s etc.).\r\n\r\nSee https:\/\/github.com\/dbatten5\/vim-ffs for more details.","4":"Run the current word or a given query through a search engine along with the current filetype to give more relevant, focused search results.\r\n\r\nComes with some configuration options to provide more customisation over the scope of the search, for example scoping searches from kubernetes yaml configuration files to ensure that searches come with a predefined scope of kubernetes (or kubectl, k8s etc.).\r\n\r\nSee https:\/\/github.com\/dbatten5\/vim-ffs for more details.","install_details":"Use your preferred installation method; for example, with vim-plug, use:\r\n\r\nPlug 'dbatten5\/vim-ffs'\r\n\r\nEither call the main command directly or configure a mapping, examples in the docs.","5":"Use your preferred installation method; for example, with vim-plug, use:\r\n\r\nPlug 'dbatten5\/vim-ffs'\r\n\r\nEither call the main command directly or configure a mapping, examples in the docs.","first_name":"Dom","6":"Dom","last_name":"Batten","7":"Batten","releases":[{"0":"5918","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"vim-ffs.zip","4":"vim-ffs.zip","src_id":"27396","5":"27396","creation_date":"1607413574","6":"1607413574"}]},"5917":{"script_id":"5917","0":"5917","script_name":"complete_filename_keepenv","1":"complete_filename_keepenv","script_type":"utility","2":"utility","summary":"complete filename without expanding envrionment variables","3":"complete filename without expanding envrionment variables","description":"Complete filename without expanding envrionment variables,\r\n\r\nUsually in insert mode , filename-completion will auto expand env variables, like this \r\n $HOME\/ ---> \/home\/user\/abc\r\n\r\nThis script let you do not touch the env vars while completion . \r\n $HOME\/ ---> $HOME\/abc\r\n\r\nSupport env format : $ENV, ${ENV} , $(ENV), $env(VAR) (tcl only)\r\nSupport searching system env with prefix, e.g.: $H\r\n\r\nUsage: \r\n 1) Insert mode: \r\n 2) Insert mode: \r\n\r\nNote: Just tested under Linux (Centos6, Ubuntu20.04), other OS may not work~ \r\n","4":"Complete filename without expanding envrionment variables,\r\n\r\nUsually in insert mode , filename-completion will auto expand env variables, like this \r\n $HOME\/ ---> \/home\/user\/abc\r\n\r\nThis script let you do not touch the env vars while completion . \r\n $HOME\/ ---> $HOME\/abc\r\n\r\nSupport env format : $ENV, ${ENV} , $(ENV), $env(VAR) (tcl only)\r\nSupport searching system env with prefix, e.g.: $H\r\n\r\nUsage: \r\n 1) Insert mode: \r\n 2) Insert mode: \r\n\r\nNote: Just tested under Linux (Centos6, Ubuntu20.04), other OS may not work~ \r\n","install_details":"Drag this file into vim plugin directory. ( ~\/.vim\/plugin\/ )","5":"Drag this file into vim plugin directory. ( ~\/.vim\/plugin\/ )","first_name":"jinhu","6":"jinhu","last_name":"lu","7":"lu","releases":[{"0":"5917","vim_version":"7.0","1":"7.0","script_version":"0.6","2":"0.6","version_comment":"fix env pattern bug in tcl file","3":"fix env pattern bug in tcl file","package":"complete_file_keepenv.vim","4":"complete_file_keepenv.vim","src_id":"27754","5":"27754","creation_date":"1632756367","6":"1632756367"},{"0":"5917","vim_version":"7.0","1":"7.0","script_version":"0.5","2":"0.5","version_comment":"1) add home symbol '~' supported\r\n2) exclude base start with '-\/'\r\n3) fix a bug on vim8","3":"1) add home symbol '~' supported\r\n2) exclude base start with '-\/'\r\n3) fix a bug on vim8","package":"complete_file_keepenv.vim","4":"complete_file_keepenv.vim","src_id":"27422","5":"27422","creation_date":"1609148076","6":"1609148076"},{"0":"5917","vim_version":"7.0","1":"7.0","script_version":"0.4","2":"0.4","version_comment":"1) exclude base start with \\'[{}()-]\\'\r\n2) remove compatibility with ","3":"1) exclude base start with \\'[{}()-]\\'\r\n2) remove compatibility with ","package":"complete_file_keepenv.vim","4":"complete_file_keepenv.vim","src_id":"27394","5":"27394","creation_date":"1606941834","6":"1606941834"},{"0":"5917","vim_version":"7.0","1":"7.0","script_version":"0.3","2":"0.3","version_comment":"fixed base len error when start at middle line","3":"fixed base len error when start at middle line","package":"complete_file_keepenv.vim","4":"complete_file_keepenv.vim","src_id":"27390","5":"27390","creation_date":"1606901737","6":"1606901737"},{"0":"5917","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"complete_file_keepenv.vim","4":"complete_file_keepenv.vim","src_id":"27381","5":"27381","creation_date":"1606059185","6":"1606059185"}]},"5916":{"script_id":"5916","0":"5916","script_name":"rust-snippets","1":"rust-snippets","script_type":"utility","2":"utility","summary":"Rust snippets for Vim","3":"Rust snippets for Vim","description":"rust-snippets\r\n\r\nRusty snippets for Vim\r\n\r\nYou can edit your snippets as well (they are located in ~\/.vim\/bundle\/rust-snippets\/snippets) or even change your snippets folder by changing the path variable in your ~\/.vimrc (let g:snips_path = \"$PATH2SNIPPETS\")\r\n\r\nYou can also change the leader for this plugin if & is already used (let g:rusty_map = \"$NEW_LEADER\" in your .vimrc)\r\nInstallation\r\nVlugger\r\n\r\nRun vlugger install wafelack\/rust-snippets in terminal.\r\nPathogen\r\n\r\nRun cd ~\/.vim\/bundle\/ && git clone https:\/\/github.com\/wafelack\/rust-snippets.git in terminal.\r\nVimPlug\r\n\r\nPlace this in your .vimrc:\r\n\r\nPlug 'wafelack\/rust-snippets'\r\n\r\n\u00e2\u0080\u00a6 then run the following in Vim:\r\n\r\n:source %\r\n:PlugInstall\r\n\r\nVundle\r\n\r\nPlace this in your .vimrc:\r\n\r\nPlugin 'wafelack\/rust-snippets'\r\n\r\n\u00e2\u0080\u00a6 then run the following in Vim:\r\n\r\n:source %\r\n:PluginInstall\r\n","4":"rust-snippets\r\n\r\nRusty snippets for Vim\r\n\r\nYou can edit your snippets as well (they are located in ~\/.vim\/bundle\/rust-snippets\/snippets) or even change your snippets folder by changing the path variable in your ~\/.vimrc (let g:snips_path = \"$PATH2SNIPPETS\")\r\n\r\nYou can also change the leader for this plugin if & is already used (let g:rusty_map = \"$NEW_LEADER\" in your .vimrc)\r\nInstallation\r\nVlugger\r\n\r\nRun vlugger install wafelack\/rust-snippets in terminal.\r\nPathogen\r\n\r\nRun cd ~\/.vim\/bundle\/ && git clone https:\/\/github.com\/wafelack\/rust-snippets.git in terminal.\r\nVimPlug\r\n\r\nPlace this in your .vimrc:\r\n\r\nPlug 'wafelack\/rust-snippets'\r\n\r\n\u00e2\u0080\u00a6 then run the following in Vim:\r\n\r\n:source %\r\n:PlugInstall\r\n\r\nVundle\r\n\r\nPlace this in your .vimrc:\r\n\r\nPlugin 'wafelack\/rust-snippets'\r\n\r\n\u00e2\u0080\u00a6 then run the following in Vim:\r\n\r\n:source %\r\n:PluginInstall\r\n","install_details":"","5":"","first_name":"Wafelack","6":"Wafelack","last_name":"Wafelack","7":"Wafelack","releases":[{"0":"5916","vim_version":"8.0","1":"8.0","script_version":"8.2","2":"8.2","version_comment":"Initial upload","3":"Initial upload","package":"snippets.vim","4":"snippets.vim","src_id":"27380","5":"27380","creation_date":"1606013625","6":"1606013625"}]},"5915":{"script_id":"5915","0":"5915","script_name":"DrawX","1":"DrawX","script_type":"utility","2":"utility","summary":"ASCII and Unicode Art (etch-a-sketch style)","3":"ASCII and Unicode Art (etch-a-sketch style)","description":"NOTE: Version 16\/05\/21 onwards changes the mapping for entering trace mode from '0' to '00'. This is unfortunate, but was necessary in order to accommodate some of the new paste operations\r\n\r\n**GUI PASTE BUG** It has come to my attention that there seems to be a bug in some GUI vim versions that means that getregtype() does not return the correct value for the default clipboard register. I have seen this myself with nvim-qt on Windows but I have read reports of it on other GUI versions (not just nvim, but possibly limited to Windows). Anyway, this bug will cause \\0p (and P) mappings to refuse to work. A way around this seems to be to use another register (specify \" for yank and paste), or you may find that using \"00p (or P) works ok to paste the last yank to the default register. Or just use the terminal version of vim :-)\r\n\r\nINTRODUCTION\r\n\r\nDrawX makes ASCII-art drawing relatively easy. You can draw boxes and lines, and there is support for easily including special characters in your drawings. As well as supporting standard ASCII characters, it also supports a number of different line-drawing styles courtesy of the wider Unicode character set\r\n\r\nThere are several drawing functions provided;-\r\n\r\n1\/ Box and ellipse drawing - This allows quick drawing of arbitrary-sized boxes and ellipses, optionally filled with blank space\r\n\r\n2\/ Tracing - This allows you to move the cursor around and trace a path as you go. Support is provided for joining lines, and placing special characters etc\r\n\r\n3\/ A flood-fill operation that allows you to fill any arbitrary shape with any character you like\r\n\r\n4\/ Some special cut and paste operations that are better suited than the standard operations to dealing with ASCII art; they all operate in-place rather than performing any delete or insert operations (basically they are less likely to make a mess of things!). They also provide support for centre cut-out, upside-down and back-to-front pasting\r\n\r\nThere are several built-in drawing styles. You can also define your own based on any character you like, so you can draw an ellipse with '@' characters if you want\r\n\r\nNOTE: I really have no idea what the minimum vim version requirement is to run DrawX and I don't know of a practical way of finding out (I've only used it on v8.2). The best I can suggest is to try it; it will probably work and if it doesn't then let me know and I'll see if I can sort it\r\n\r\n*** If you have any suggestions for improving this, then please let me know. If you think it's rubbish then PLEASE let me know why - it's far more useful than just 'voting it down' (which really doesn't help at all). Contact details are in the top of the README file ***\r\n\r\nHere is a (rather uninspiring) example. I know it doesn't display very well because it needs a fixed-width font (I have manually jiggled it about a bit to try and improve it), but it's better than nothing and should give you an idea...\r\n\r\n ┌────────────┐ ╔════════════╗\r\n │Here's a Box │ ║ Here's a Box ║\r\n └─────┬──────┘ ╚═════╤══════╝\r\n │ │\r\n ╰────────┬───────╯\r\n │\r\n ╭╌╌╌╌╌╌╌┴╌╌╌╌╌╌╌╮\r\n ╎ And another Box ╎\r\n ╰╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╯\r\n\r\n ┏━━━━━┓\r\n ■┃◍ ◍┃■\r\n ┃ ═══ ┃\r\n ┗━━╦━━┛\r\n ┌──┳━━━╩━━━┳──┐\r\n │ ┌┨ ┏┅┅┅┓ ┠┐ │\r\n │ │┃ ┗┅┅┅┛ ┃│ │\r\n │ │┃ DrawX ┃│ │\r\n │ │┃ ┃│ │\r\n └─┘┃ ┃└─┘\r\n ┗┳━┳━┳━┳┛\r\n ┃ ┃ ┃ ┃\r\n ┃ ┃ ┃ ┃\r\n ┃ ┃ ┃ ┃\r\n ┗━┛ ┗━┛\r\n\r\nCopy and paste upside-down and back-to-front....\r\n\r\n ┏┓\r\n ══════┃┃\r\n ════════┃┃══\r\n┌────────────┐\r\n│┌──┐ ┌──┐│\r\n││ │┌─┐ │ │ │\r\n│└──┘│ │ └──┘│\r\n└────┴─┴─────┘\r\n\r\n┌─────┬─┬────┐\r\n│┌──┐ │ │┌──┐│\r\n││ │ └─┘│ ││\r\n│└──┘ └──┘│\r\n└────────────┘\r\n ══┃┃════════\r\n ┃┃══════\r\n ┗┛\r\n\r\n","4":"NOTE: Version 16\/05\/21 onwards changes the mapping for entering trace mode from '0' to '00'. This is unfortunate, but was necessary in order to accommodate some of the new paste operations\r\n\r\n**GUI PASTE BUG** It has come to my attention that there seems to be a bug in some GUI vim versions that means that getregtype() does not return the correct value for the default clipboard register. I have seen this myself with nvim-qt on Windows but I have read reports of it on other GUI versions (not just nvim, but possibly limited to Windows). Anyway, this bug will cause \\0p (and P) mappings to refuse to work. A way around this seems to be to use another register (specify \" for yank and paste), or you may find that using \"00p (or P) works ok to paste the last yank to the default register. Or just use the terminal version of vim :-)\r\n\r\nINTRODUCTION\r\n\r\nDrawX makes ASCII-art drawing relatively easy. You can draw boxes and lines, and there is support for easily including special characters in your drawings. As well as supporting standard ASCII characters, it also supports a number of different line-drawing styles courtesy of the wider Unicode character set\r\n\r\nThere are several drawing functions provided;-\r\n\r\n1\/ Box and ellipse drawing - This allows quick drawing of arbitrary-sized boxes and ellipses, optionally filled with blank space\r\n\r\n2\/ Tracing - This allows you to move the cursor around and trace a path as you go. Support is provided for joining lines, and placing special characters etc\r\n\r\n3\/ A flood-fill operation that allows you to fill any arbitrary shape with any character you like\r\n\r\n4\/ Some special cut and paste operations that are better suited than the standard operations to dealing with ASCII art; they all operate in-place rather than performing any delete or insert operations (basically they are less likely to make a mess of things!). They also provide support for centre cut-out, upside-down and back-to-front pasting\r\n\r\nThere are several built-in drawing styles. You can also define your own based on any character you like, so you can draw an ellipse with '@' characters if you want\r\n\r\nNOTE: I really have no idea what the minimum vim version requirement is to run DrawX and I don't know of a practical way of finding out (I've only used it on v8.2). The best I can suggest is to try it; it will probably work and if it doesn't then let me know and I'll see if I can sort it\r\n\r\n*** If you have any suggestions for improving this, then please let me know. If you think it's rubbish then PLEASE let me know why - it's far more useful than just 'voting it down' (which really doesn't help at all). Contact details are in the top of the README file ***\r\n\r\nHere is a (rather uninspiring) example. I know it doesn't display very well because it needs a fixed-width font (I have manually jiggled it about a bit to try and improve it), but it's better than nothing and should give you an idea...\r\n\r\n ┌────────────┐ ╔════════════╗\r\n │Here's a Box │ ║ Here's a Box ║\r\n └─────┬──────┘ ╚═════╤══════╝\r\n │ │\r\n ╰────────┬───────╯\r\n │\r\n ╭╌╌╌╌╌╌╌┴╌╌╌╌╌╌╌╮\r\n ╎ And another Box ╎\r\n ╰╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╯\r\n\r\n ┏━━━━━┓\r\n ■┃◍ ◍┃■\r\n ┃ ═══ ┃\r\n ┗━━╦━━┛\r\n ┌──┳━━━╩━━━┳──┐\r\n │ ┌┨ ┏┅┅┅┓ ┠┐ │\r\n │ │┃ ┗┅┅┅┛ ┃│ │\r\n │ │┃ DrawX ┃│ │\r\n │ │┃ ┃│ │\r\n └─┘┃ ┃└─┘\r\n ┗┳━┳━┳━┳┛\r\n ┃ ┃ ┃ ┃\r\n ┃ ┃ ┃ ┃\r\n ┃ ┃ ┃ ┃\r\n ┗━┛ ┗━┛\r\n\r\nCopy and paste upside-down and back-to-front....\r\n\r\n ┏┓\r\n ══════┃┃\r\n ════════┃┃══\r\n┌────────────┐\r\n│┌──┐ ┌──┐│\r\n││ │┌─┐ │ │ │\r\n│└──┘│ │ └──┘│\r\n└────┴─┴─────┘\r\n\r\n┌─────┬─┬────┐\r\n│┌──┐ │ │┌──┐│\r\n││ │ └─┘│ ││\r\n│└──┘ └──┘│\r\n└────────────┘\r\n ══┃┃════════\r\n ┃┃══════\r\n ┗┛\r\n\r\n","install_details":"Just un-tar into ~\/.vim\/bundle\/ as usual and read the README file for config options","5":"Just un-tar into ~\/.vim\/bundle\/ as usual and read the README file for config options","first_name":"Richard","6":"Richard","last_name":"Bentley-Green","7":"Bentley-Green","releases":[{"0":"5915","vim_version":"7.0","1":"7.0","script_version":"15\/06\/2022","2":"15\/06\/2022","version_comment":"Trivial improvement to error reporting of visually selected operations\r\n","3":"Trivial improvement to error reporting of visually selected operations\r\n","package":"drawx.tar.gz","4":"drawx.tar.gz","src_id":"28442","5":"28442","creation_date":"1683062948","6":"1683062948"},{"0":"5915","vim_version":"7.0","1":"7.0","script_version":"20\/04\/2022","2":"20\/04\/2022","version_comment":"- Fixed a bug that completely broke DrawX if 'mapleader' was not defined","3":"- Fixed a bug that completely broke DrawX if 'mapleader' was not defined","package":"drawx.tar.gz","4":"drawx.tar.gz","src_id":"28008","5":"28008","creation_date":"1650486013","6":"1650486013"},{"0":"5915","vim_version":"7.0","1":"7.0","script_version":"17\/04\/2022","2":"17\/04\/2022","version_comment":"- Added mappings to allow drawing style to be set outside of trace mode; ie, `\\0-`, ``\\0.`, `\\0~`, and `\\0s`, and the 'place special' mapping `\\0+`; it was a bit annoying having to go into trace mode to change the style for box\/ellipse drawing and fill operations\r\n- Swapped a few thing around and generally updated the help following recent additions\r\n","3":"- Added mappings to allow drawing style to be set outside of trace mode; ie, `\\0-`, ``\\0.`, `\\0~`, and `\\0s`, and the 'place special' mapping `\\0+`; it was a bit annoying having to go into trace mode to change the style for box\/ellipse drawing and fill operations\r\n- Swapped a few thing around and generally updated the help following recent additions\r\n","package":"drawx.tar.gz","4":"drawx.tar.gz","src_id":"28006","5":"28006","creation_date":"1650247792","6":"1650247792"},{"0":"5915","vim_version":"7.0","1":"7.0","script_version":"16\/04\/2020","2":"16\/04\/2020","version_comment":"- Added flood fill operation - ref. `) has to be pressed twice to confirm exit. This is to give further protection against accidentally dropping out\r\n- Added undo and redo mappings to trace mode\r\n- Added 'a' and 'A' arrow-placing mappings\r\n- Trivial changes to some status messages\r\n- Minor corrections and changes to the documentation\r\n","3":"- Reworked how the trace mode mappings work. This allows a much more robust operation (trace mode won't just drop-out any more when a bad key is pressed). This allows DrawX to detect exactly when it is active, and (more to the point) when the user wants to exit (the way the mappings worked previously meant that a bad key would cause DrawX to silently exit which was really annoying)\r\n- To exit trace mode, the exit key () has to be pressed twice to confirm exit. This is to give further protection against accidentally dropping out\r\n- Added undo and redo mappings to trace mode\r\n- Added 'a' and 'A' arrow-placing mappings\r\n- Trivial changes to some status messages\r\n- Minor corrections and changes to the documentation\r\n","package":"drawx.tar.gz","4":"drawx.tar.gz","src_id":"27989","5":"27989","creation_date":"1649631785","6":"1649631785"},{"0":"5915","vim_version":"7.0","1":"7.0","script_version":"05\/08\/2021","2":"05\/08\/2021","version_comment":"Fixed glaring syntax error that broke 'x' command. Amazed it's taken this long to spot!","3":"Fixed glaring syntax error that broke 'x' command. Amazed it's taken this long to spot!","package":"drawx.tar.gz","4":"drawx.tar.gz","src_id":"27695","5":"27695","creation_date":"1628206870","6":"1628206870"},{"0":"5915","vim_version":"7.0","1":"7.0","script_version":"26\/05\/21","2":"26\/05\/21","version_comment":"- Made 't' and 'x' operations more 'intelligent' when deciding which character to place (now take account of more variations of character to replace)\r\n- Added operations 'T' and 'X'; these are deliberately 'less intelligent' versions of 't' and 'x'\r\n- Added '!' operation (cancels active direction - useful for T placement - see docs)\r\n","3":"- Made 't' and 'x' operations more 'intelligent' when deciding which character to place (now take account of more variations of character to replace)\r\n- Added operations 'T' and 'X'; these are deliberately 'less intelligent' versions of 't' and 'x'\r\n- Added '!' operation (cancels active direction - useful for T placement - see docs)\r\n","package":"drawx.tar.gz","4":"drawx.tar.gz","src_id":"27624","5":"27624","creation_date":"1622847241","6":"1622847241"},{"0":"5915","vim_version":"7.0","1":"7.0","script_version":"16\/05\/21","2":"16\/05\/21","version_comment":"Added cut and paste command and assoc. configuration commands","3":"Added cut and paste command and assoc. configuration commands","package":"drawx.tar.gz","4":"drawx.tar.gz","src_id":"27607","5":"27607","creation_date":"1621196039","6":"1621196039"},{"0":"5915","vim_version":"7.0","1":"7.0","script_version":"02\/03\/21","2":"02\/03\/21","version_comment":"Improved 'X' placement (see mapping 'x') and special character placement to prevent them being overwritten (in some cases) when moving away from the place position\r\n\r\n","3":"Improved 'X' placement (see mapping 'x') and special character placement to prevent them being overwritten (in some cases) when moving away from the place position\r\n\r\n","package":"drawx.tar.gz","4":"drawx.tar.gz","src_id":"27507","5":"27507","creation_date":"1614751565","6":"1614751565"},{"0":"5915","vim_version":"7.0","1":"7.0","script_version":"29\/01\/21","2":"29\/01\/21","version_comment":"- Added `s` mapping and `DrawXStyle` command to allow setting of arbitrary styles - you can not set a style based on any single character and use it in all drawing functions\r\n- Fixed a bug whereby box drawing function was not drawing dotted lines and curved corners correctly\r\n","3":"- Added `s` mapping and `DrawXStyle` command to allow setting of arbitrary styles - you can not set a style based on any single character and use it in all drawing functions\r\n- Fixed a bug whereby box drawing function was not drawing dotted lines and curved corners correctly\r\n","package":"drawx.tar.gz","4":"drawx.tar.gz","src_id":"27460","5":"27460","creation_date":"1611953624","6":"1611953624"},{"0":"5915","vim_version":"7.0","1":"7.0","script_version":"26\/01\/21","2":"26\/01\/21","version_comment":"- Added ellipse drawing function and associated mappings\r\n- Added fill\/no fill option for box drawing; unfortunately, also changed box draw mapping as a result\r\n","3":"- Added ellipse drawing function and associated mappings\r\n- Added fill\/no fill option for box drawing; unfortunately, also changed box draw mapping as a result\r\n","package":"drawx.tar.gz","4":"drawx.tar.gz","src_id":"27457","5":"27457","creation_date":"1611731610","6":"1611731610"},{"0":"5915","vim_version":"7.0","1":"7.0","script_version":"03\/01\/20","2":"03\/01\/20","version_comment":"- Added 'erase' mode toggle\r\n- Added new mappings to allow moving cursor without tracing (but staying in trace mode)\r\n","3":"- Added 'erase' mode toggle\r\n- Added new mappings to allow moving cursor without tracing (but staying in trace mode)\r\n","package":"drawx.tar.gz","4":"drawx.tar.gz","src_id":"27436","5":"27436","creation_date":"1609728134","6":"1609728134"},{"0":"5915","vim_version":"7.0","1":"7.0","script_version":"30\/12\/20","2":"30\/12\/20","version_comment":"- Documented 'cursor keys' and 'exit trace' mappings\r\n- Added ability to change 'exit trace' and `exit menu` keys (both default to ``) to avoid conflicts with cursor keys\r\n","3":"- Documented 'cursor keys' and 'exit trace' mappings\r\n- Added ability to change 'exit trace' and `exit menu` keys (both default to ``) to avoid conflicts with cursor keys\r\n","package":"drawx.tar.gz","4":"drawx.tar.gz","src_id":"27434","5":"27434","creation_date":"1609373703","6":"1609373703"},{"0":"5915","vim_version":"7.0","1":"7.0","script_version":"20\/11\/20","2":"20\/11\/20","version_comment":"Initial upload","3":"Initial upload","package":"drawx.tar.gz","4":"drawx.tar.gz","src_id":"27379","5":"27379","creation_date":"1605932139","6":"1605932139"}]},"5914":{"script_id":"5914","0":"5914","script_name":"vim-macroscope","1":"vim-macroscope","script_type":"utility","2":"utility","summary":"Quick macro editing","3":"Quick macro editing","description":"Quick visual editing of existing macros by dropping the contents of the macro in a scratch window. The macro will be automatically updated upon leaving the window.\r\n\r\nSee https:\/\/github.com\/dbatten5\/vim-macroscope for more details.","4":"Quick visual editing of existing macros by dropping the contents of the macro in a scratch window. The macro will be automatically updated upon leaving the window.\r\n\r\nSee https:\/\/github.com\/dbatten5\/vim-macroscope for more details.","install_details":"Use your preferred installation method; for example, with vim-plug, use:\r\n\r\nPlug 'dbatten5\/vim-macroscope'\r\n\r\nEither call the main command directly or configure a mapping, examples in the docs.","5":"Use your preferred installation method; for example, with vim-plug, use:\r\n\r\nPlug 'dbatten5\/vim-macroscope'\r\n\r\nEither call the main command directly or configure a mapping, examples in the docs.","first_name":"Dom","6":"Dom","last_name":"Batten","7":"Batten","releases":[{"0":"5914","vim_version":"7.0","1":"7.0","script_version":"1.1","2":"1.1","version_comment":"Use rather than so macroscope can be called like :Macroscope q rather than :Macroscope 'q'","3":"Use rather than so macroscope can be called like :Macroscope q rather than :Macroscope 'q'","package":"vim-macroscope.zip","4":"vim-macroscope.zip","src_id":"27383","5":"27383","creation_date":"1606093490","6":"1606093490"},{"0":"5914","vim_version":"7.2","1":"7.2","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"vim-macroscope.zip","4":"vim-macroscope.zip","src_id":"27373","5":"27373","creation_date":"1605636655","6":"1605636655"}]},"5913":{"script_id":"5913","0":"5913","script_name":"vim-scranch","1":"vim-scranch","script_type":"utility","2":"utility","summary":"Git branch based note-taking","3":"Git branch based note-taking","description":"This script is based on the motivation that the need to make a quick note in vim is often related to the current feature\/bug\/task, which is typically tied to a git branch. Opening the scranch note window brings up a new note in a (faux-)scratch window tied to the current git branch. New branch, new note.\r\n\r\nThis script provides a main command :Scranch which either creates a new note, identified by the current git branch, or returns an existing one.\r\n\r\nSee https:\/\/github.com\/dbatten5\/vim-scranch for more details","4":"This script is based on the motivation that the need to make a quick note in vim is often related to the current feature\/bug\/task, which is typically tied to a git branch. Opening the scranch note window brings up a new note in a (faux-)scratch window tied to the current git branch. New branch, new note.\r\n\r\nThis script provides a main command :Scranch which either creates a new note, identified by the current git branch, or returns an existing one.\r\n\r\nSee https:\/\/github.com\/dbatten5\/vim-scranch for more details","install_details":"Use your preferred installation method; for example, with vim-plug, use:\r\n\r\nPlug 'dbatten5\/vim-scranch'\r\n\r\nEither call the main commands directly or configure a mapping, examples in the docs. ","5":"Use your preferred installation method; for example, with vim-plug, use:\r\n\r\nPlug 'dbatten5\/vim-scranch'\r\n\r\nEither call the main commands directly or configure a mapping, examples in the docs. ","first_name":"Dom","6":"Dom","last_name":"Batten","7":"Batten","releases":[{"0":"5913","vim_version":"7.2","1":"7.2","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"vim-scranch.zip","4":"vim-scranch.zip","src_id":"27363","5":"27363","creation_date":"1605432401","6":"1605432401"}]},"5912":{"script_id":"5912","0":"5912","script_name":"vim wiki","1":"vim wiki","script_type":"utility","2":"utility","summary":"Recognizes wiki-like hyperlinks [[word]] and jumps to the corresponding file.","3":"Recognizes wiki-like hyperlinks [[word]] and jumps to the corresponding file.","description":"Poor man's wiki. Any text file can have wiki-words (words enclosed in [[ and ]]). Pressing 'K' (or a different mapped key) on such a word causes a file corresponding to the wiki-word to be loaded (in another tab or same tab).","4":"Poor man's wiki. Any text file can have wiki-words (words enclosed in [[ and ]]). Pressing 'K' (or a different mapped key) on such a word causes a file corresponding to the wiki-word to be loaded (in another tab or same tab).","install_details":"Extract under 'bundle' directory (if using pathogen). Or extract elsewhere and copy to your vim scripts directory.","5":"Extract under 'bundle' directory (if using pathogen). Or extract elsewhere and copy to your vim scripts directory.","first_name":"Suresh","6":"Suresh","last_name":"Srinivasan","7":"Srinivasan","releases":[{"0":"5912","vim_version":"7.0","1":"7.0","script_version":"1.1","2":"1.1","version_comment":"Simplified logic.","3":"Simplified logic.","package":"wiki_vimfiles.zip","4":"wiki_vimfiles.zip","src_id":"27791","5":"27791","creation_date":"1635516352","6":"1635516352"},{"0":"5912","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"wiki.zip","4":"wiki.zip","src_id":"27362","5":"27362","creation_date":"1605343183","6":"1605343183"}]},"5910":{"script_id":"5910","0":"5910","script_name":"Toast","1":"Toast","script_type":"color scheme","2":"color scheme","summary":"A colorful, medium-contrast light and dark theme with full Vim and Nvim support","3":"A colorful, medium-contrast light and dark theme with full Vim and Nvim support","description":"A colorful, medium-contrast theme with full Vim and Neovim support, true color\r\nand 256-color support, and automatic light and dark variants. Easy to read\r\nwithout frying your retinae. \r\n\r\nScreenshots here: https:\/\/www.flickr.com\/photos\/topdownjimmy\/albums\/72157716599140642\r\nGit repository here: https:\/\/github.com\/jsit\/toast.vim\/ \r\n\r\nToast is not meant to be a \"color system\" or anything fancy like that, although\r\nit does operate within a few parameters to make its development easier and to\r\naim for some degree of theoretical color harmony. \r\n\r\n- All text has (or should have) a contrast ratio of at least 3:1, meeting WCAG\r\nlevel A. (Level AA across the board makes the colors too drab for my taste, but\r\nthere will be an option for this in the future, because a11y is important.)\r\n- All hues are multiples of 15 degrees apart on the color wheel, because why not.\r\n- Within these parameters, saturation and luminance levels are chosen based on\r\nwhat I think looks good while dogfooding the themes. \r\n\r\nMuch of the basis for this code and approach comes from Chris Kempson's\r\nvenerable Tomorrow theme.","4":"A colorful, medium-contrast theme with full Vim and Neovim support, true color\r\nand 256-color support, and automatic light and dark variants. Easy to read\r\nwithout frying your retinae. \r\n\r\nScreenshots here: https:\/\/www.flickr.com\/photos\/topdownjimmy\/albums\/72157716599140642\r\nGit repository here: https:\/\/github.com\/jsit\/toast.vim\/ \r\n\r\nToast is not meant to be a \"color system\" or anything fancy like that, although\r\nit does operate within a few parameters to make its development easier and to\r\naim for some degree of theoretical color harmony. \r\n\r\n- All text has (or should have) a contrast ratio of at least 3:1, meeting WCAG\r\nlevel A. (Level AA across the board makes the colors too drab for my taste, but\r\nthere will be an option for this in the future, because a11y is important.)\r\n- All hues are multiples of 15 degrees apart on the color wheel, because why not.\r\n- Within these parameters, saturation and luminance levels are chosen based on\r\nwhat I think looks good while dogfooding the themes. \r\n\r\nMuch of the basis for this code and approach comes from Chris Kempson's\r\nvenerable Tomorrow theme.","install_details":"Copy to your .vim\/colors directory","5":"Copy to your .vim\/colors directory","first_name":"Jay","6":"Jay","last_name":"Sitter","7":"Sitter","releases":[{"0":"5910","vim_version":"7.0","1":"7.0","script_version":"0.2.4","2":"0.2.4","version_comment":"Fixing some greys for 256-color dark background","3":"Fixing some greys for 256-color dark background","package":"toast.vim","4":"toast.vim","src_id":"27349","5":"27349","creation_date":"1603750482","6":"1603750482"},{"0":"5910","vim_version":"7.0","1":"7.0","script_version":"0.2.2","2":"0.2.2","version_comment":"Initial upload","3":"Initial upload","package":"toast.vim","4":"toast.vim","src_id":"27348","5":"27348","creation_date":"1603698355","6":"1603698355"}]},"5908":{"script_id":"5908","0":"5908","script_name":"vim-jira","1":"vim-jira","script_type":"utility","2":"utility","summary":"Browse JIRA inside Vim!","3":"Browse JIRA inside Vim!","description":"Basically a clone of [vim-reddit](https:\/\/github.com\/joshhartigan\/vim-reddit)\r\nwith some ux tweaks from [gv.vim](https:\/\/github.com\/junegunn\/gv.vim)\r\n\r\n## Usage\r\n\r\nOpen issues browser for the current sprint for your jira board\r\n\r\n```vim\r\n :JiraSprint\r\n```\r\nThese mappings are available in the jira browser\r\n\r\n- `o` or `` on a issue to display the content of it\r\n- `]]` and `[[` to move between issues\r\n- to go to next\/prev issue\r\n- `q` to close\r\n\r\n","4":"Basically a clone of [vim-reddit](https:\/\/github.com\/joshhartigan\/vim-reddit)\r\nwith some ux tweaks from [gv.vim](https:\/\/github.com\/junegunn\/gv.vim)\r\n\r\n## Usage\r\n\r\nOpen issues browser for the current sprint for your jira board\r\n\r\n```vim\r\n :JiraSprint\r\n```\r\nThese mappings are available in the jira browser\r\n\r\n- `o` or `` on a issue to display the content of it\r\n- `]]` and `[[` to move between issues\r\n- to go to next\/prev issue\r\n- `q` to close\r\n\r\n","install_details":"## Installation\r\n\r\nThis plugin requires python3\r\n\r\nUsing [vim-plug]( https:\/\/github.com\/junegunn\/vim-plug )\r\n\r\n```vim\r\n Plug \\'deepredsky\/vim-jira\\'\r\n```\r\n\r\n## Configuration\r\n\r\nYou can configure the following settings which is required to make this plugin work\r\n\r\nSet this to board_id and the base url of the jira installation.\r\n\r\n```vim\r\n let g:jira_url = \\'https:\/\/acme.atlassian.net\\'\r\n let g:jira_board_id = 31\r\n```\r\n\r\nConfigure username and secret to access your jira installation. Api token can\r\nbe generated at https:\/\/id.atlassian.com\/manage\/api-tokens\r\n\r\n```vim\r\n export JIRA_USERNAME=your.jira.email@acme.com\r\n export JIRA_API_TOKEN=super-secret-token\r\n```\r\n\r\n","5":"## Installation\r\n\r\nThis plugin requires python3\r\n\r\nUsing [vim-plug]( https:\/\/github.com\/junegunn\/vim-plug )\r\n\r\n```vim\r\n Plug \\'deepredsky\/vim-jira\\'\r\n```\r\n\r\n## Configuration\r\n\r\nYou can configure the following settings which is required to make this plugin work\r\n\r\nSet this to board_id and the base url of the jira installation.\r\n\r\n```vim\r\n let g:jira_url = \\'https:\/\/acme.atlassian.net\\'\r\n let g:jira_board_id = 31\r\n```\r\n\r\nConfigure username and secret to access your jira installation. Api token can\r\nbe generated at https:\/\/id.atlassian.com\/manage\/api-tokens\r\n\r\n```vim\r\n export JIRA_USERNAME=your.jira.email@acme.com\r\n export JIRA_API_TOKEN=super-secret-token\r\n```\r\n\r\n","first_name":"Rajesh","6":"Rajesh","last_name":"Sharma","7":"Sharma","releases":[{"0":"5908","vim_version":"7.0","1":"7.0","script_version":"0.0.2","2":"0.0.2","version_comment":" * Add mappings to open issue in browser\r\n * Allow Jira command to open a single issue\r\n * Fix opening issue in browser\r\n","3":" * Add mappings to open issue in browser\r\n * Allow Jira command to open a single issue\r\n * Fix opening issue in browser\r\n","package":"vim-jira.zip","4":"vim-jira.zip","src_id":"27340","5":"27340","creation_date":"1603063868","6":"1603063868"},{"0":"5908","vim_version":"7.0","1":"7.0","script_version":"0.0.1","2":"0.0.1","version_comment":"Initial upload","3":"Initial upload","package":"vim-jira.zip","4":"vim-jira.zip","src_id":"27338","5":"27338","creation_date":"1602978743","6":"1602978743"}]},"5907":{"script_id":"5907","0":"5907","script_name":"hcch","1":"hcch","script_type":"utility","2":"utility","summary":"Vim plugin for creating header\/source pair for c\/c++ languages","3":"Vim plugin for creating header\/source pair for c\/c++ languages","description":"Vim plugin for creating header\/source pair for c\/c++ languages\r\n## usage\r\n`:CreateSource `\r\n\r\nSource type sould be \"c\" or \"cpp\"","4":"Vim plugin for creating header\/source pair for c\/c++ languages\r\n## usage\r\n`:CreateSource `\r\n\r\nSource type sould be \"c\" or \"cpp\"","install_details":"- [vim-plug] Plug 'angelskieglazki\/hcch.vim'\r\n- [Vundle] Plugin 'angelskieglazki\/hcch.vim'","5":"- [vim-plug] Plug 'angelskieglazki\/hcch.vim'\r\n- [Vundle] Plugin 'angelskieglazki\/hcch.vim'","first_name":"max","6":"max","last_name":"ponka","7":"ponka","releases":[{"0":"5907","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"hcch.vim-0.1.tar.gz","4":"hcch.vim-0.1.tar.gz","src_id":"27337","5":"27337","creation_date":"1602972995","6":"1602972995"}]},"5906":{"script_id":"5906","0":"5906","script_name":"Zeef","1":"Zeef","script_type":"utility","2":"utility","summary":"Interactively filter a list of items","3":"Interactively filter a list of items","description":"Zeef is a 100% Vim script. minimalist, pure autoload, dynamic interactive filter for a list of items. Think of it as a wise man's CtrlP. It is used by invoking zeef#open(). Zeef does not define any command or mapping. The arguments of the function are:\r\n\r\n1. A list of items;\r\n2. The name of a callback function;\r\n3. The text for the command line prompt.\r\n\r\n(The function accepts an optional fourth argument to set up custom key mappings: see `:help zeef` for the details).\r\n\r\nTry this \"zeef\":\r\n\r\n fun Callback(result)\r\n echo a:result\r\n endf\r\n\r\n call zeef#open(['January', 'July', 'Lily', 'Lyric', 'Nucleus'], 'Callback', 'Choose')\r\n\r\nStart typing to filter the list. Press Enter to invoke the callback with the selected item(s) (multiple selections are possible\u00e2\u0080\u0094see below). Press Esc to cancel. The following is the complete list of keys you can use when the Zeef buffer is open (these can be customized with g:zeef_keymap):\r\n\r\nCTRL-K or up arrow: move up one line;\r\nCTRL-J or down arrow: move down one line;\r\nleft and right arrows: scroll horizontally;\r\nCTRL-B, CTRL-F, CTRL-D, CTRL-U, CTRL-E, CTRL-Y: usual movements;\r\nCTRL-L: clear the prompt;\r\nCTRL-G: clear the prompt and deselect all items;\r\nCTRL-Z: select\/deselect the current line;\r\nCTRL-A: select all currently filtered lines;\r\nCTRL-R: deselect all currently filtered lines;\r\nEsc, CTRL-C: close Zeef without performing any action;\r\nEnter: accept the current choice;\r\nCTRL-S, CTRL-V, CTRL-T: like Enter, but also open a split, vertical split or tab.\r\n\r\nHow does Zeef differ from the several similar plugins already out there, you ask? The implementation is likely *the simplest possible*: as you type, :global is used to remove the lines that do not match what you are typing. When you press backspace, :undo is used to restore the previous state. Yes, the core of this plugin is based on just those two Vim commands. It works surprisingly well, unless your list is huge (hundreds of thousands of lines).\r\n\r\nWhat can you do with Zeef? Whatever you want! Zeef is not bloated with features that you will never use: it is for people who wish to implement their own functionality with minimal help. That said, Zeef does come with a few \"sample applications\":\r\n\r\n- a buffer switcher;\r\n- a path filter;\r\n- a quickfix\/location list filter;\r\n- a color scheme selector;\r\n- a buffer tag chooser.\r\n\r\nUse the source code as the authoritative reference. It's not that complicated. And don't forget to read the full (albeit short) documentation: see :help zeef.txt.\r\n\r\nAh, before you ask: the answer is no. Zeef does not perform fuzzy search, approximate search, match rankings, or other esoteric stuff. All that is out of the scope of this project. Those are features that are well covered by other plugins, after all.\r\n\r\nLICENSE\r\n\r\nCopyright \u00c2\u00a92020 Lifepillar\r\n\r\nPermission is hereby granted, free of charge, to any person obtaining a copy of\r\nthis software and associated documentation files (the \"Software\"), to deal in\r\nthe Software without restriction, including without limitation the rights to\r\nuse, copy, modify, merge, publish, distribute, sublicense, and\/or sell copies of\r\nthe Software, and to permit persons to whom the Software is furnished to do so,\r\nsubject to the following conditions:\r\n\r\nThe above copyright notice and this permission notice shall be included in all\r\ncopies or substantial portions of the Software.\r\n\r\nTHE SOFTWARE IS PROVIDED \"AS IS\", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR\r\nIMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS\r\nFOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR\r\nCOPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER\r\nIN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN\r\nCONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.","4":"Zeef is a 100% Vim script. minimalist, pure autoload, dynamic interactive filter for a list of items. Think of it as a wise man's CtrlP. It is used by invoking zeef#open(). Zeef does not define any command or mapping. The arguments of the function are:\r\n\r\n1. A list of items;\r\n2. The name of a callback function;\r\n3. The text for the command line prompt.\r\n\r\n(The function accepts an optional fourth argument to set up custom key mappings: see `:help zeef` for the details).\r\n\r\nTry this \"zeef\":\r\n\r\n fun Callback(result)\r\n echo a:result\r\n endf\r\n\r\n call zeef#open(['January', 'July', 'Lily', 'Lyric', 'Nucleus'], 'Callback', 'Choose')\r\n\r\nStart typing to filter the list. Press Enter to invoke the callback with the selected item(s) (multiple selections are possible\u00e2\u0080\u0094see below). Press Esc to cancel. The following is the complete list of keys you can use when the Zeef buffer is open (these can be customized with g:zeef_keymap):\r\n\r\nCTRL-K or up arrow: move up one line;\r\nCTRL-J or down arrow: move down one line;\r\nleft and right arrows: scroll horizontally;\r\nCTRL-B, CTRL-F, CTRL-D, CTRL-U, CTRL-E, CTRL-Y: usual movements;\r\nCTRL-L: clear the prompt;\r\nCTRL-G: clear the prompt and deselect all items;\r\nCTRL-Z: select\/deselect the current line;\r\nCTRL-A: select all currently filtered lines;\r\nCTRL-R: deselect all currently filtered lines;\r\nEsc, CTRL-C: close Zeef without performing any action;\r\nEnter: accept the current choice;\r\nCTRL-S, CTRL-V, CTRL-T: like Enter, but also open a split, vertical split or tab.\r\n\r\nHow does Zeef differ from the several similar plugins already out there, you ask? The implementation is likely *the simplest possible*: as you type, :global is used to remove the lines that do not match what you are typing. When you press backspace, :undo is used to restore the previous state. Yes, the core of this plugin is based on just those two Vim commands. It works surprisingly well, unless your list is huge (hundreds of thousands of lines).\r\n\r\nWhat can you do with Zeef? Whatever you want! Zeef is not bloated with features that you will never use: it is for people who wish to implement their own functionality with minimal help. That said, Zeef does come with a few \"sample applications\":\r\n\r\n- a buffer switcher;\r\n- a path filter;\r\n- a quickfix\/location list filter;\r\n- a color scheme selector;\r\n- a buffer tag chooser.\r\n\r\nUse the source code as the authoritative reference. It's not that complicated. And don't forget to read the full (albeit short) documentation: see :help zeef.txt.\r\n\r\nAh, before you ask: the answer is no. Zeef does not perform fuzzy search, approximate search, match rankings, or other esoteric stuff. All that is out of the scope of this project. Those are features that are well covered by other plugins, after all.\r\n\r\nLICENSE\r\n\r\nCopyright \u00c2\u00a92020 Lifepillar\r\n\r\nPermission is hereby granted, free of charge, to any person obtaining a copy of\r\nthis software and associated documentation files (the \"Software\"), to deal in\r\nthe Software without restriction, including without limitation the rights to\r\nuse, copy, modify, merge, publish, distribute, sublicense, and\/or sell copies of\r\nthe Software, and to permit persons to whom the Software is furnished to do so,\r\nsubject to the following conditions:\r\n\r\nThe above copyright notice and this permission notice shall be included in all\r\ncopies or substantial portions of the Software.\r\n\r\nTHE SOFTWARE IS PROVIDED \"AS IS\", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR\r\nIMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS\r\nFOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR\r\nCOPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER\r\nIN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN\r\nCONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.","install_details":"mkdir -p ~\/.vim\/pack\/plugins\/start\r\ngit clone https:\/\/github.com\/lifepillar\/vim-zeef.git ~\/.vim\/pack\/plugins\/start\/zeef","5":"mkdir -p ~\/.vim\/pack\/plugins\/start\r\ngit clone https:\/\/github.com\/lifepillar\/vim-zeef.git ~\/.vim\/pack\/plugins\/start\/zeef","first_name":"","6":"","last_name":"Lifepillar","7":"Lifepillar","releases":[{"0":"5906","vim_version":"7.4","1":"7.4","script_version":"1.0.1","2":"1.0.1","version_comment":"Allows overriding mappings for a single call of zeef#open(). Allows (de)selecting all filtered items at once. Shows the number of selected items in the status line. Adds zeef#result() and zeef#keypressed() to get the list of selected items and the last key pressed, respectively (useful in callbacks in some cases). Bug fixes in parsing tags and highlighting. Improved documentation and compatibility with older Vim. Licensed under MIT.","3":"Allows overriding mappings for a single call of zeef#open(). Allows (de)selecting all filtered items at once. Shows the number of selected items in the status line. Adds zeef#result() and zeef#keypressed() to get the list of selected items and the last key pressed, respectively (useful in callbacks in some cases). Bug fixes in parsing tags and highlighting. Improved documentation and compatibility with older Vim. Licensed under MIT.","package":"vim-zeef-v1.0.1.tar.gz","4":"vim-zeef-v1.0.1.tar.gz","src_id":"27365","5":"27365","creation_date":"1605504157","6":"1605504157"},{"0":"5906","vim_version":"7.4","1":"7.4","script_version":"1.0.0","2":"1.0.0","version_comment":"Initial upload","3":"Initial upload","package":"vim-zeef-1.0.0.tar.gz","4":"vim-zeef-1.0.0.tar.gz","src_id":"27323","5":"27323","creation_date":"1602134512","6":"1602134512"}]},"5905":{"script_id":"5905","0":"5905","script_name":"VPE - Vim Python Extensions","1":"VPE - Vim Python Extensions","script_type":"utility","2":"utility","summary":"Extension for Vim scripting using Python 3","3":"Extension for Vim scripting using Python 3","description":"News \r\n \r\n The official documentation is now at https:\/\/vim-vpe.readthedocs.io\/en\/stable.\r\n This documentation is working towards a comprehensive user guide, including\r\n API documentation. The help file included with VPE is mainly only the API. \r\n\r\n A lot has been added since version 0.4, most significantly in areas that\r\n make writing and maintaining non-trivial plug-ins easier.\r\n\r\nRequirements\r\n\r\n VPE requires a minimum of Vim 8.0.0700 and Python 3.6.\r\n\r\n VPE is tested on Linux and Windows 10. On Windows, testing is done using Vim\r\n 8.2.1970 and Python 3.8.6. On Linux testing is done using\r\n Vim-8.0.0700\/Python-3.6.0 and very recent versions of both vim and Python.\r\n\r\nStatus\r\n Although it has not yet reached a version 1.0 release, I believe that VPE\r\n is quite stable. I make heavy, daily use of VPE within my (Linux) Vim\r\n environment without problems.\r\n\r\n While the API should be considered unstable, it has actually proven fairly\r\n stable, with only a few, minor incompatible changes since version 0.1.\r\n\r\nIntroduction\r\n\r\n VPE adds to Vim\u00e2\u0080\u0099s built-in support for Python scripting. This is a brief list\r\n of VPE\u00e2\u0080\u0099s features.\r\n\r\n - A Vim class that provides an enhanced, drop-in replacement for the standard\r\n python-vim module.\r\n\r\n - Classes Window, Buffer, TabPage are enhanced wrappers around the standard\r\n vim versions.\r\n\r\n - Support for cleanly invoking Python functions for keyboard mappings, user\r\n defined commands and events.\r\n\r\n New in 0.5 is support for using Python decorators to set up these mappings.\r\n\r\n - Pythonic support for using popup-windows. (Requires Vim 8.2.)\r\n\r\n - Pythonic support for using timers; when a timer fires a Python function is\r\n invoked.\r\n\r\n - Pythonic support for channels.\r\n\r\n - Syntax class and supporting context managers to define highlighting.\r\n\r\n - Logging to a buffer. Useful when developing and debugging plug-ins.\r\n When active in a window, the window automatically scrolls to show new\r\n output.\r\n\r\n - A plug-in support mechanism. I find this more convenient for non-trivial\r\n Python based plug-ins.\r\n\r\n - Other relatively high level support for non-trivial plug-ins. This includes\r\n management of configuration values, scratch (display only) buffers,\r\n user-interface like components (panels and fields).\r\n\r\n The above just scratches the surface, see :help vpe.txt for detailed\r\n documentation or the more readable form at https:\/\/vim-vpe.readthedocs.io\/.\r\n\r\nSource code\r\n\r\n The source code is maintained at https:\/\/github.com\/paul-ollis\/vim-vpe.git.\r\n You can raise bugs or feature requests there.\r\n\r\nQuick start\r\n\r\n The quickest way to start using VPE is to import the vim object:\r\n\r\n from vpe import vim\r\n\r\n The vim object is an instance of the Vim class and is intended to be a drop\r\n in replacement for Vim\u00e2\u0080\u0099s standard python-vim module, but with a number of\r\n enhancements.\r\n\r\n - Most of Vim\u00e2\u0080\u0099s functions appear as members, for example:\r\n\r\n vim.cursor(4, 10) # Position cursor at row 4, column 10.\r\n m = vim.execute('messages') # Get all the recent Vim messages.\r\n\r\n - The attributes buffers, current, options, tabpages, vars, vvars and\r\n windows provide enhanced access to the corresponding Vim objects. For\r\n example vim.current.buffer provides a Buffer instance in place of Vim\u00e2\u0080\u0099s\r\n standard python-buffer.\r\n\r\n - The Vim registers are available using the registers attribute.\r\n\r\n - When errors occur a VimError is raised, which provides a better\r\n breakdown of the error. This is a subclass of vim.error so existing\r\n code that catches vim.error still works.\r\n\r\nExamples\r\n\r\n Please treat the examples as demo, minimally tested code.\r\n\r\n The examples provided with VPE are:\r\n\r\n vpe_filenav - start with, ':runtime examples\/vpe_filenav.vim'\r\n\r\n A very simple file explorer that can be used to open files.\r\n\r\n vpe_bufnav - start with, ':runtime examples\/vpe_bufnav.vim'\r\n\r\n An explorer for buffers. This is heavily inspired by Jeff\r\n Lanzarotta's excellent vimscript #42, but it does not attempt to be\r\n a clone.","4":"News \r\n \r\n The official documentation is now at https:\/\/vim-vpe.readthedocs.io\/en\/stable.\r\n This documentation is working towards a comprehensive user guide, including\r\n API documentation. The help file included with VPE is mainly only the API. \r\n\r\n A lot has been added since version 0.4, most significantly in areas that\r\n make writing and maintaining non-trivial plug-ins easier.\r\n\r\nRequirements\r\n\r\n VPE requires a minimum of Vim 8.0.0700 and Python 3.6.\r\n\r\n VPE is tested on Linux and Windows 10. On Windows, testing is done using Vim\r\n 8.2.1970 and Python 3.8.6. On Linux testing is done using\r\n Vim-8.0.0700\/Python-3.6.0 and very recent versions of both vim and Python.\r\n\r\nStatus\r\n Although it has not yet reached a version 1.0 release, I believe that VPE\r\n is quite stable. I make heavy, daily use of VPE within my (Linux) Vim\r\n environment without problems.\r\n\r\n While the API should be considered unstable, it has actually proven fairly\r\n stable, with only a few, minor incompatible changes since version 0.1.\r\n\r\nIntroduction\r\n\r\n VPE adds to Vim\u00e2\u0080\u0099s built-in support for Python scripting. This is a brief list\r\n of VPE\u00e2\u0080\u0099s features.\r\n\r\n - A Vim class that provides an enhanced, drop-in replacement for the standard\r\n python-vim module.\r\n\r\n - Classes Window, Buffer, TabPage are enhanced wrappers around the standard\r\n vim versions.\r\n\r\n - Support for cleanly invoking Python functions for keyboard mappings, user\r\n defined commands and events.\r\n\r\n New in 0.5 is support for using Python decorators to set up these mappings.\r\n\r\n - Pythonic support for using popup-windows. (Requires Vim 8.2.)\r\n\r\n - Pythonic support for using timers; when a timer fires a Python function is\r\n invoked.\r\n\r\n - Pythonic support for channels.\r\n\r\n - Syntax class and supporting context managers to define highlighting.\r\n\r\n - Logging to a buffer. Useful when developing and debugging plug-ins.\r\n When active in a window, the window automatically scrolls to show new\r\n output.\r\n\r\n - A plug-in support mechanism. I find this more convenient for non-trivial\r\n Python based plug-ins.\r\n\r\n - Other relatively high level support for non-trivial plug-ins. This includes\r\n management of configuration values, scratch (display only) buffers,\r\n user-interface like components (panels and fields).\r\n\r\n The above just scratches the surface, see :help vpe.txt for detailed\r\n documentation or the more readable form at https:\/\/vim-vpe.readthedocs.io\/.\r\n\r\nSource code\r\n\r\n The source code is maintained at https:\/\/github.com\/paul-ollis\/vim-vpe.git.\r\n You can raise bugs or feature requests there.\r\n\r\nQuick start\r\n\r\n The quickest way to start using VPE is to import the vim object:\r\n\r\n from vpe import vim\r\n\r\n The vim object is an instance of the Vim class and is intended to be a drop\r\n in replacement for Vim\u00e2\u0080\u0099s standard python-vim module, but with a number of\r\n enhancements.\r\n\r\n - Most of Vim\u00e2\u0080\u0099s functions appear as members, for example:\r\n\r\n vim.cursor(4, 10) # Position cursor at row 4, column 10.\r\n m = vim.execute('messages') # Get all the recent Vim messages.\r\n\r\n - The attributes buffers, current, options, tabpages, vars, vvars and\r\n windows provide enhanced access to the corresponding Vim objects. For\r\n example vim.current.buffer provides a Buffer instance in place of Vim\u00e2\u0080\u0099s\r\n standard python-buffer.\r\n\r\n - The Vim registers are available using the registers attribute.\r\n\r\n - When errors occur a VimError is raised, which provides a better\r\n breakdown of the error. This is a subclass of vim.error so existing\r\n code that catches vim.error still works.\r\n\r\nExamples\r\n\r\n Please treat the examples as demo, minimally tested code.\r\n\r\n The examples provided with VPE are:\r\n\r\n vpe_filenav - start with, ':runtime examples\/vpe_filenav.vim'\r\n\r\n A very simple file explorer that can be used to open files.\r\n\r\n vpe_bufnav - start with, ':runtime examples\/vpe_bufnav.vim'\r\n\r\n An explorer for buffers. This is heavily inspired by Jeff\r\n Lanzarotta's excellent vimscript #42, but it does not attempt to be\r\n a clone.","install_details":"The VPE directory tree is structured as a package with a single plugin.\r\nAssuming your Vim files are in the \u00e2\u0080\u009c~\/.vim\u00e2\u0080\u009d directory, add a \u00e2\u0080\u009cpack\u00e2\u0080\u009d sub-\r\ndirectory and install VPE into the \u00e2\u0080\u009c~\/.vim\/pack\u00e2\u0080\u009d directory.\r\n\r\n $ cd ~\/.vim\/pack\r\n $ unzip vim-vpe.zip\r\n\r\nThe package includes a \u00e2\u0080\u009cvim-vpe\/start\/vpe\/plugin\/vpe.vim\u00e2\u0080\u009d startup script that\r\nupdates the Python path so that the vpe package can be imported.\r\n\r\nThe source code is at https:\/\/github.com\/paul-ollis\/vim-vpe.git. You can clone\r\nthis into ~\/.vim\/pack, but that will, currently, not include the Vim help file.","5":"The VPE directory tree is structured as a package with a single plugin.\r\nAssuming your Vim files are in the \u00e2\u0080\u009c~\/.vim\u00e2\u0080\u009d directory, add a \u00e2\u0080\u009cpack\u00e2\u0080\u009d sub-\r\ndirectory and install VPE into the \u00e2\u0080\u009c~\/.vim\/pack\u00e2\u0080\u009d directory.\r\n\r\n $ cd ~\/.vim\/pack\r\n $ unzip vim-vpe.zip\r\n\r\nThe package includes a \u00e2\u0080\u009cvim-vpe\/start\/vpe\/plugin\/vpe.vim\u00e2\u0080\u009d startup script that\r\nupdates the Python path so that the vpe package can be imported.\r\n\r\nThe source code is at https:\/\/github.com\/paul-ollis\/vim-vpe.git. You can clone\r\nthis into ~\/.vim\/pack, but that will, currently, not include the Vim help file.","first_name":"Paul","6":"Paul","last_name":"Ollis","7":"Ollis","releases":[{"0":"5905","vim_version":"8.0","1":"8.0","script_version":"0.6","2":"0.6","version_comment":"Version 0.6\r\n\r\n- The main activity has been writing more of a user guide. The built-in Vim\r\n style help is now mainly reference. The full help is in HTML form - currently\r\n available at https:\/\/vim-vpe.readthedocs.io\/en\/userguide\/.\r\n\r\n- General\r\n\r\n - Fixed issue where VPE could fail to load its plugins.\r\n\r\n - Prevent some errors when getting application window information.\r\n\r\n - Reduce the likelyhood of callback failures passing silently.\r\n\r\n - The define_command function now allows the range argument to be True, which\r\n is equivalent to the Vim '-range' option without arguments.\r\n\r\n - The call_soon mechanism now logs a traceback upon failure.\r\n\r\n- Refactoring\r\n\r\n - Cleaned up how single-shot timers are handled.\r\n\r\n - Moved a lot of code into vpe.common.\r\n\r\n- AutoCmdGroup\r\n\r\n - Additional keyword arguments may now be passed to the function handling an\r\n event.\r\n\r\n- Channel\r\n\r\n - The on_connect method is now invoked via call_soon.\r\n\r\n - The closed property was fixed to prevent an exception.\r\n\r\n - The on_message method is now invoked via call_soon.\r\n\r\n - Added a read method to allow explicit channel reading.\r\n\r\n - Prevent Vim error when closing an already closed channel.\r\n\r\n- Popup windows\r\n\r\n - Better detection of mouse events, by adding hard coded sequences.\r\n\r\n - Made the textprop, textpropif and textpropwin properties read\/write.\r\n\r\n - Tidied up handling of keys with modifiers.\r\n\r\n - The buffer property is now None where it would previously raise an\r\n exception.\r\n\r\n - Added setoptions and move methods.\r\n\r\n- Buffer\r\n\r\n - Added an add_listener method. Provides a hook into Vim's listener_add\r\n mechanism. Treat this feature as quite experimental.\r\n\r\n- ScratchBuffer\r\n\r\n - The init_options method now does nothing, it exists only to be\r\n over-ridden by subclasses.","3":"Version 0.6\r\n\r\n- The main activity has been writing more of a user guide. The built-in Vim\r\n style help is now mainly reference. The full help is in HTML form - currently\r\n available at https:\/\/vim-vpe.readthedocs.io\/en\/userguide\/.\r\n\r\n- General\r\n\r\n - Fixed issue where VPE could fail to load its plugins.\r\n\r\n - Prevent some errors when getting application window information.\r\n\r\n - Reduce the likelyhood of callback failures passing silently.\r\n\r\n - The define_command function now allows the range argument to be True, which\r\n is equivalent to the Vim '-range' option without arguments.\r\n\r\n - The call_soon mechanism now logs a traceback upon failure.\r\n\r\n- Refactoring\r\n\r\n - Cleaned up how single-shot timers are handled.\r\n\r\n - Moved a lot of code into vpe.common.\r\n\r\n- AutoCmdGroup\r\n\r\n - Additional keyword arguments may now be passed to the function handling an\r\n event.\r\n\r\n- Channel\r\n\r\n - The on_connect method is now invoked via call_soon.\r\n\r\n - The closed property was fixed to prevent an exception.\r\n\r\n - The on_message method is now invoked via call_soon.\r\n\r\n - Added a read method to allow explicit channel reading.\r\n\r\n - Prevent Vim error when closing an already closed channel.\r\n\r\n- Popup windows\r\n\r\n - Better detection of mouse events, by adding hard coded sequences.\r\n\r\n - Made the textprop, textpropif and textpropwin properties read\/write.\r\n\r\n - Tidied up handling of keys with modifiers.\r\n\r\n - The buffer property is now None where it would previously raise an\r\n exception.\r\n\r\n - Added setoptions and move methods.\r\n\r\n- Buffer\r\n\r\n - Added an add_listener method. Provides a hook into Vim's listener_add\r\n mechanism. Treat this feature as quite experimental.\r\n\r\n- ScratchBuffer\r\n\r\n - The init_options method now does nothing, it exists only to be\r\n over-ridden by subclasses.","package":"vim-vpe-0.6.zip","4":"vim-vpe-0.6.zip","src_id":"27741","5":"27741","creation_date":"1631589024","6":"1631589024"},{"0":"5905","vim_version":"8.0","1":"8.0","script_version":"0.5.2","2":"0.5.2","version_comment":"Version 0.5.2\r\n\r\n- Big change to colors.py. Should not affect the existing API.\r\n\r\n- Better window size behaviour when displaying ScratchBuffers.\r\n\r\n- Fix invalid characters in generated autogrp names.\r\n\r\n- Add support for VPE plugin help files.\r\n\r\n- Better preserve types for option access.","3":"Version 0.5.2\r\n\r\n- Big change to colors.py. Should not affect the existing API.\r\n\r\n- Better window size behaviour when displaying ScratchBuffers.\r\n\r\n- Fix invalid characters in generated autogrp names.\r\n\r\n- Add support for VPE plugin help files.\r\n\r\n- Better preserve types for option access.","package":"vim-vpe-0.5.2.zip","4":"vim-vpe-0.5.2.zip","src_id":"27537","5":"27537","creation_date":"1616276667","6":"1616276667"},{"0":"5905","vim_version":"8.0","1":"8.0","script_version":"0.5.1","2":"0.5.1","version_comment":"Version 0.5.1\r\n\r\n- Added a load of missing API documentation that I foolishly forgot about.\r\n\r\n- The temp_active_buffer context manager now also preserves the window's\r\n view.","3":"Version 0.5.1\r\n\r\n- Added a load of missing API documentation that I foolishly forgot about.\r\n\r\n- The temp_active_buffer context manager now also preserves the window's\r\n view.","package":"vim-vpe-0.5.1.zip","4":"vim-vpe-0.5.1.zip","src_id":"27530","5":"27530","creation_date":"1615520008","6":"1615520008"},{"0":"5905","vim_version":"8.0","1":"8.0","script_version":"0.5","2":"0.5","version_comment":"Version 0.5\r\n\r\n- Try to prevent VPE's help obscuring help for standard Vim commands and\r\n functions.\r\n\r\n- Added plugin system; I find this easier to use for Python based plug-ins.\r\n\r\n- Key mappings, user commands and auto commands now show the Python function\r\n name.\r\n\r\n- Allow key mappings and user commands that do not pass an info object.\r\n\r\n- Support creating key mappings that simply expand as strings; for when a Python\r\n fucnction is overkill.\r\n\r\n- All commands available via vpe.commands now get prefixed with 'keepalt' by\r\n default. This is a backwardly incompatible change, but should have minimal\r\n impact on existing code.\r\n\r\n- New modules.\r\n\r\n - vpe.windows. Provides a wrapping around the output of winlayout().\r\n\r\n - vpe.app_ui_support. Provides a way to query information about Vim's\r\n application window when runninf on an X-desktop.\r\n\r\n - vpe.config. Provides a mechanism defined configuration values which can\r\n stored on disk.\r\n\r\n - vpe.panels. Provides an extension to ScratchBuffer that horizontally\r\n divides the buffer into one or more independent panels.\r\n\r\n - vpe.ui. Adds user interaction support, building on vpe.panels. Currently\r\n it is focussed on supporting interactive modification of values managed by\r\n vpe.config.\r\n\r\n- New and modified functions.\r\n\r\n - Added 'soon' argument to error_msg.\r\n\r\n - Added echo_msg and warning_msg (to match error_msg).\r\n\r\n - Added temp_active_window context manager.\r\n\r\n - Added saved_current_window and temp_active_buffer context managers.\r\n\r\n- New classes\r\n\r\n - CommandHandler, EventHandler, BufEventHandler and KeyHandler. These support\r\n using Python decorators as a clean way to map user commands, event and key\r\n sequences to Python methods.\r\n\r\n- Buffer class\r\n\r\n - Enhanced the show method to allow vertical splits and provide more\r\n flexibility in how line\/columns are allocated to each half of the split.\r\n\r\n - Added a split_and_show method.\r\n\r\n - Added is_active method. Return True if the buffer is showing in the current\r\n window.\r\n\r\n - Methods find_active_windows and goto_active_window now only search the\r\n current tab page by default. This is backwardly incompatible. Also added\r\n find_best_active_window.\r\n\r\n- TemporaryOptions class\r\n\r\n - Added a save method.\r\n\r\n- Syntax class\r\n\r\n - Can be used without clearing previous syntax items.\r\n\r\n- Window class\r\n\r\n - Added a close method.\r\n\r\n- Vim class\r\n\r\n - Added iter_all_windows method.\r\n\r\n- Syntax class\r\n\r\n - It is not possible to prevent automatic deletion of old syntax.\r\n\r\n- ScratchBuffer class\r\n\r\n - New method on_first_showing is invoked when the buffer is first shown. This\r\n is intended to be over-ridden or extended.\r\n\r\n - Added auto_grp_name and syntax_prefix properties. These are useful to avoid\r\n name clashes when adding syntax and auto commands.\r\n\r\n- Added support for vertical, aboveleft, belowright, topleft, botright and\r\n keepalt modifiers for vpe.commands.\r\n\r\n- Provide mechanism to reset a Vim option to its default value.\r\n\r\n- Work around an issue where Vim can consume large amounts of memory due to\r\n code executed by timer. This could only occur when a Vim session was left\r\n without focus.","3":"Version 0.5\r\n\r\n- Try to prevent VPE's help obscuring help for standard Vim commands and\r\n functions.\r\n\r\n- Added plugin system; I find this easier to use for Python based plug-ins.\r\n\r\n- Key mappings, user commands and auto commands now show the Python function\r\n name.\r\n\r\n- Allow key mappings and user commands that do not pass an info object.\r\n\r\n- Support creating key mappings that simply expand as strings; for when a Python\r\n fucnction is overkill.\r\n\r\n- All commands available via vpe.commands now get prefixed with 'keepalt' by\r\n default. This is a backwardly incompatible change, but should have minimal\r\n impact on existing code.\r\n\r\n- New modules.\r\n\r\n - vpe.windows. Provides a wrapping around the output of winlayout().\r\n\r\n - vpe.app_ui_support. Provides a way to query information about Vim's\r\n application window when runninf on an X-desktop.\r\n\r\n - vpe.config. Provides a mechanism defined configuration values which can\r\n stored on disk.\r\n\r\n - vpe.panels. Provides an extension to ScratchBuffer that horizontally\r\n divides the buffer into one or more independent panels.\r\n\r\n - vpe.ui. Adds user interaction support, building on vpe.panels. Currently\r\n it is focussed on supporting interactive modification of values managed by\r\n vpe.config.\r\n\r\n- New and modified functions.\r\n\r\n - Added 'soon' argument to error_msg.\r\n\r\n - Added echo_msg and warning_msg (to match error_msg).\r\n\r\n - Added temp_active_window context manager.\r\n\r\n - Added saved_current_window and temp_active_buffer context managers.\r\n\r\n- New classes\r\n\r\n - CommandHandler, EventHandler, BufEventHandler and KeyHandler. These support\r\n using Python decorators as a clean way to map user commands, event and key\r\n sequences to Python methods.\r\n\r\n- Buffer class\r\n\r\n - Enhanced the show method to allow vertical splits and provide more\r\n flexibility in how line\/columns are allocated to each half of the split.\r\n\r\n - Added a split_and_show method.\r\n\r\n - Added is_active method. Return True if the buffer is showing in the current\r\n window.\r\n\r\n - Methods find_active_windows and goto_active_window now only search the\r\n current tab page by default. This is backwardly incompatible. Also added\r\n find_best_active_window.\r\n\r\n- TemporaryOptions class\r\n\r\n - Added a save method.\r\n\r\n- Syntax class\r\n\r\n - Can be used without clearing previous syntax items.\r\n\r\n- Window class\r\n\r\n - Added a close method.\r\n\r\n- Vim class\r\n\r\n - Added iter_all_windows method.\r\n\r\n- Syntax class\r\n\r\n - It is not possible to prevent automatic deletion of old syntax.\r\n\r\n- ScratchBuffer class\r\n\r\n - New method on_first_showing is invoked when the buffer is first shown. This\r\n is intended to be over-ridden or extended.\r\n\r\n - Added auto_grp_name and syntax_prefix properties. These are useful to avoid\r\n name clashes when adding syntax and auto commands.\r\n\r\n- Added support for vertical, aboveleft, belowright, topleft, botright and\r\n keepalt modifiers for vpe.commands.\r\n\r\n- Provide mechanism to reset a Vim option to its default value.\r\n\r\n- Work around an issue where Vim can consume large amounts of memory due to\r\n code executed by timer. This could only occur when a Vim session was left\r\n without focus.","package":"vim-vpe-0.5.zip","4":"vim-vpe-0.5.zip","src_id":"27527","5":"27527","creation_date":"1615320951","6":"1615320951"},{"0":"5905","vim_version":"8.0","1":"8.0","script_version":"0.4.1","2":"0.4.1","version_comment":"- Log class.\r\n - Changed the way the buffer contents are trimmed. Prevents (or at least\r\n reduces) annoying window redraws\/corruption.","3":"- Log class.\r\n - Changed the way the buffer contents are trimmed. Prevents (or at least\r\n reduces) annoying window redraws\/corruption.","package":"vim-vpe-0.4.1.zip","4":"vim-vpe-0.4.1.zip","src_id":"27384","5":"27384","creation_date":"1606166736","6":"1606166736"},{"0":"5905","vim_version":"8.0","1":"8.0","script_version":"0.4","2":"0.4","version_comment":"- Works on Windows (10).\r\n- General\r\n - Added dot_vim_dir function.\r\n - List style options are now always converted \r\n from bytes to str.\r\n- Buffer class\r\n - Added find_active_windows method.\r\n - The ScratchBuffer can now be usefully sub-classed.\r\n - Added set_ext_name method.\r\n- Windows class.\r\n - Added visible_line_range property.\r\n- Timers\r\n - Fixed bug for single shot timers.","3":"- Works on Windows (10).\r\n- General\r\n - Added dot_vim_dir function.\r\n - List style options are now always converted \r\n from bytes to str.\r\n- Buffer class\r\n - Added find_active_windows method.\r\n - The ScratchBuffer can now be usefully sub-classed.\r\n - Added set_ext_name method.\r\n- Windows class.\r\n - Added visible_line_range property.\r\n- Timers\r\n - Fixed bug for single shot timers.","package":"vim-vpe-0.4.zip","4":"vim-vpe-0.4.zip","src_id":"27376","5":"27376","creation_date":"1605917155","6":"1605917155"},{"0":"5905","vim_version":"8.0","1":"8.0","script_version":"0.3","2":"0.3","version_comment":"- Fixed issue with examples running 'out-of-the-box'.\r\n- Added a version() function to the vpe module.\r\n- Added define_command function.\r\n - User commands that call Python.\r\n- Timers\r\n - Added fire_count attribute.\r\n - Added dead attribute.\r\n - Fixed timer clean up.\r\n- Fix to error_msg to restore message colour.\r\n- Add Syntax.include method.","3":"- Fixed issue with examples running 'out-of-the-box'.\r\n- Added a version() function to the vpe module.\r\n- Added define_command function.\r\n - User commands that call Python.\r\n- Timers\r\n - Added fire_count attribute.\r\n - Added dead attribute.\r\n - Fixed timer clean up.\r\n- Fix to error_msg to restore message colour.\r\n- Add Syntax.include method.","package":"vim-vpe-0.3.zip","4":"vim-vpe-0.3.zip","src_id":"27355","5":"27355","creation_date":"1604627686","6":"1604627686"},{"0":"5905","vim_version":"8.0","1":"8.0","script_version":"0.2","2":"0.2","version_comment":"Documentation improvements (still needs work).\r\nSome internal code refactoring.\r\nImproved logging of run-time errors (to log buffer).\r\nSyntax class:\r\n - Added link_to argument to group method.\r\nScratchBuffer:\r\n - Prevent annoying warning message.\r\nBuffer class:\r\n - Added new properties: type, location, long_display_name,\r\n short_display_name, short_description, bufnr, changed, changedtick,\r\n lastused, lnum, linecount, loaded, variables, windows and popups.\r\n - Added goto_active_window method.\r\nStarted adding some examples as a supplement to the documentation.\r\nThe HTML help is now available on readthdocs.","3":"Documentation improvements (still needs work).\r\nSome internal code refactoring.\r\nImproved logging of run-time errors (to log buffer).\r\nSyntax class:\r\n - Added link_to argument to group method.\r\nScratchBuffer:\r\n - Prevent annoying warning message.\r\nBuffer class:\r\n - Added new properties: type, location, long_display_name,\r\n short_display_name, short_description, bufnr, changed, changedtick,\r\n lastused, lnum, linecount, loaded, variables, windows and popups.\r\n - Added goto_active_window method.\r\nStarted adding some examples as a supplement to the documentation.\r\nThe HTML help is now available on readthdocs.","package":"vim-vpe-0.2.zip","4":"vim-vpe-0.2.zip","src_id":"27350","5":"27350","creation_date":"1603770282","6":"1603770282"},{"0":"5905","vim_version":"8.0","1":"8.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"vim-vpe.zip","4":"vim-vpe.zip","src_id":"27319","5":"27319","creation_date":"1601668281","6":"1601668281"}]},"5904":{"script_id":"5904","0":"5904","script_name":"todo.vim","1":"todo.vim","script_type":"syntax","2":"syntax","summary":"Syntax coloring for todo lists.","3":"Syntax coloring for todo lists.","description":"Syntax coloring for simple todo files.\r\n\r\nSee test\/test.todo for examples.\r\n\r\nNOTE: this is a new version of todo.vim (https:\/\/www.vim.org\/scripts\/script.php?script_id=1938). Forgot my password, so had to create a new account and upload as new script.","4":"Syntax coloring for simple todo files.\r\n\r\nSee test\/test.todo for examples.\r\n\r\nNOTE: this is a new version of todo.vim (https:\/\/www.vim.org\/scripts\/script.php?script_id=1938). Forgot my password, so had to create a new account and upload as new script.","install_details":"If using pathogen, extract under the bundle directory. Otherwise, extract elsewhere and copy todo.vim to your scripts directory.","5":"If using pathogen, extract under the bundle directory. Otherwise, extract elsewhere and copy todo.vim to your scripts directory.","first_name":"Suresh","6":"Suresh","last_name":"Srinivasan","7":"Srinivasan","releases":[{"0":"5904","vim_version":"7.0","1":"7.0","script_version":"1.1","2":"1.1","version_comment":"Simplified logic.","3":"Simplified logic.","package":"todo_vimfiles.zip","4":"todo_vimfiles.zip","src_id":"27793","5":"27793","creation_date":"1635516416","6":"1635516416"},{"0":"5904","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"todo_vimfiles.zip","4":"todo_vimfiles.zip","src_id":"27316","5":"27316","creation_date":"1601439438","6":"1601439438"}]},"5903":{"script_id":"5903","0":"5903","script_name":"tabpages","1":"tabpages","script_type":"utility","2":"utility","summary":"Load multiple files in tabs upon startup.","3":"Load multiple files in tabs upon startup.","description":"Load multiple files in tabs upon startup. See file for details.","4":"Load multiple files in tabs upon startup. See file for details.","install_details":"Extract under 'bundle' directory (if using pathogen). Or extract elsewhere and copy tabpages.vim to your scripts directory.","5":"Extract under 'bundle' directory (if using pathogen). Or extract elsewhere and copy tabpages.vim to your scripts directory.","first_name":"Suresh","6":"Suresh","last_name":"Srinivasan","7":"Srinivasan","releases":[{"0":"5903","vim_version":"7.0","1":"7.0","script_version":"1.1","2":"1.1","version_comment":"Simplified logic.","3":"Simplified logic.","package":"tabpages_vimfiles.zip","4":"tabpages_vimfiles.zip","src_id":"27792","5":"27792","creation_date":"1635516390","6":"1635516390"},{"0":"5903","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"tabpages_vimfiles.zip","4":"tabpages_vimfiles.zip","src_id":"27315","5":"27315","creation_date":"1601439020","6":"1601439020"}]},"5902":{"script_id":"5902","0":"5902","script_name":"unintellisense.vim","1":"unintellisense.vim","script_type":"utility","2":"utility","summary":"A plugin that generates + inserts a random variable name into the editor","3":"A plugin that generates + inserts a random variable name into the editor","description":"A vim plugin that generates an adjective + noun variable name and inserts it into the editor.\r\n\r\nInvoke from normal mode with the command :Unintellisense\r\n\r\nhttps:\/\/github.com\/a3qz\/Unintellisense-Vim ","4":"A vim plugin that generates an adjective + noun variable name and inserts it into the editor.\r\n\r\nInvoke from normal mode with the command :Unintellisense\r\n\r\nhttps:\/\/github.com\/a3qz\/Unintellisense-Vim ","install_details":"Copy the .vim file into your plugin directory","5":"Copy the .vim file into your plugin directory","first_name":"Ryan","6":"Ryan","last_name":"Michalec","7":"Michalec","releases":[{"0":"5902","vim_version":"7.0","1":"7.0","script_version":"1.0.0","2":"1.0.0","version_comment":"Initial upload","3":"Initial upload","package":"unintellisense.vim","4":"unintellisense.vim","src_id":"27314","5":"27314","creation_date":"1600906183","6":"1600906183"}]},"5901":{"script_id":"5901","0":"5901","script_name":"vim-shoot","1":"vim-shoot","script_type":"utility","2":"utility","summary":"Vim plugin to take screenshots of code","3":"Vim plugin to take screenshots of code","description":"Use the command :TOpng to capture a screenshot of the selected lines (or the whole buffer if no lines are selected).\r\n\r\nThe image will be saved in vim's working directory.\r\n\r\nOptions\r\n- g:shoot_zoom_factor - Used to zoom image (default: 2)\r\n\r\nGitHub repo: https:\/\/github.com\/JMcKiern\/vim-shoot","4":"Use the command :TOpng to capture a screenshot of the selected lines (or the whole buffer if no lines are selected).\r\n\r\nThe image will be saved in vim's working directory.\r\n\r\nOptions\r\n- g:shoot_zoom_factor - Used to zoom image (default: 2)\r\n\r\nGitHub repo: https:\/\/github.com\/JMcKiern\/vim-shoot","install_details":"Requirements\r\n\r\n- Vim compiled with python3 support (check this with :echo has('python3'))\r\n- Python 3\r\n- Chrome or Firefox (a browser based on either of these should work too)\r\n\r\nInstallation\r\n\r\nAfter downloading the plugin, run the install.py script in the plugin's directory. It must take an argument specifying the webdriver to use:\r\nFor Chromium-based browsers:\r\n .\/install.py chromedriver\r\nFor Firefox-based browsers:\r\n .\/install.py geckodriver\r\n\r\nThis script does two things. First, it installs the selenium and requests packages. Second, it downloads the appropriate binary for the specified webdriver. These are all isolated to the plugin's local directory.","5":"Requirements\r\n\r\n- Vim compiled with python3 support (check this with :echo has('python3'))\r\n- Python 3\r\n- Chrome or Firefox (a browser based on either of these should work too)\r\n\r\nInstallation\r\n\r\nAfter downloading the plugin, run the install.py script in the plugin's directory. It must take an argument specifying the webdriver to use:\r\nFor Chromium-based browsers:\r\n .\/install.py chromedriver\r\nFor Firefox-based browsers:\r\n .\/install.py geckodriver\r\n\r\nThis script does two things. First, it installs the selenium and requests packages. Second, it downloads the appropriate binary for the specified webdriver. These are all isolated to the plugin's local directory.","first_name":"Jack","6":"Jack","last_name":"McKiernan","7":"McKiernan","releases":[{"0":"5901","vim_version":"8.0","1":"8.0","script_version":"0.0.1","2":"0.0.1","version_comment":"Initial upload","3":"Initial upload","package":"vim-shoot-0.0.1.zip","4":"vim-shoot-0.0.1.zip","src_id":"27308","5":"27308","creation_date":"1599335658","6":"1599335658"}]},"5900":{"script_id":"5900","0":"5900","script_name":"blockwisediff.vim","1":"blockwisediff.vim","script_type":"utility","2":"utility","summary":"A block-oriented diff to compare selected lines virtually","3":"A block-oriented diff to compare selected lines virtually","description":"Vim shows differences in diff mode. But it is a line-oriented comparison and can not properly handle sentences and paragraphs which are broken into several lines. This plugin virtually compares selected two block of lines as if there were no line break and show their character or word level exact differences.\r\n\r\nFor details and demo samples, please visit the following git repository: https:\/\/github.com\/rickhowe\/blockwisediff.vim","4":"Vim shows differences in diff mode. But it is a line-oriented comparison and can not properly handle sentences and paragraphs which are broken into several lines. This plugin virtually compares selected two block of lines as if there were no line break and show their character or word level exact differences.\r\n\r\nFor details and demo samples, please visit the following git repository: https:\/\/github.com\/rickhowe\/blockwisediff.vim","install_details":"Install 'rickhowe\/blockwisediff.vim' by using your plugin manager. Or manually unzip and copy all folders in your ~\/.vim or ~\/vimfiles.","5":"Install 'rickhowe\/blockwisediff.vim' by using your plugin manager. Or manually unzip and copy all folders in your ~\/.vim or ~\/vimfiles.","first_name":"Rick","6":"Rick","last_name":"Howe","7":"Howe","releases":[{"0":"5900","vim_version":"8.0","1":"8.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"blockwisediff1.0.zip","4":"blockwisediff1.0.zip","src_id":"27306","5":"27306","creation_date":"1599244876","6":"1599244876"}]},"5899":{"script_id":"5899","0":"5899","script_name":"vim-easy-term","1":"vim-easy-term","script_type":"utility","2":"utility","summary":"The Easy Term makes using vim's terminal feature easier to use.","3":"The Easy Term makes using vim's terminal feature easier to use.","description":"GitHub repo: https:\/\/github.com\/BeomjoonGoh\/vim-easy-term","4":"GitHub repo: https:\/\/github.com\/BeomjoonGoh\/vim-easy-term","install_details":"","5":"","first_name":"Beomjoon","6":"Beomjoon","last_name":"Goh","7":"Goh","releases":[{"0":"5899","vim_version":"8.0","1":"8.0","script_version":"0.0.1","2":"0.0.1","version_comment":"Initial upload","3":"Initial upload","package":"vim-easy-term-0.0.1.zip","4":"vim-easy-term-0.0.1.zip","src_id":"27304","5":"27304","creation_date":"1598992727","6":"1598992727"}]},"5898":{"script_id":"5898","0":"5898","script_name":"viMTG","1":"viMTG","script_type":"game","2":"game","summary":"The VIM 'Magic: The Gathering' deck builder","3":"The VIM 'Magic: The Gathering' deck builder","description":"Github: https:\/\/github.com\/yoshi1123\/vim-mtg\r\n\r\nFeatures:\r\n Preview cards completely inside Vim \r\n display your deck's stats p (manacost, mana curve, legalities, and more)\r\n Format deck into sections p\r\n Easily move cards to different sections gm, gs, go (Main, Sideboard, Other)\r\n Search for cards s\r\n Add searched cards to deck a, s, o (Main, Sideboard, Other)\r\n Select sort order for search o\r\n Limit Search to a format f\r\n Import decks by copying and pasting universal MTG deck export format\r\n\r\nHelp:\r\n :help vim-mtg\r\n\r\nGetting started:\r\n\r\n 1. Type in cards lines in the format '4 Ancient Den', or 'a'\r\n 2. :MTGSearch type:artifact\r\n 3. Use 'a' to add the current card in search buffer to the deck, 's' to add to sideboard, and 'o' to add to other, with an optional COUNT (e.g., 4a adds four of the currently selected card)\r\n 4. Use'p' to process the deck\r\n","4":"Github: https:\/\/github.com\/yoshi1123\/vim-mtg\r\n\r\nFeatures:\r\n Preview cards completely inside Vim \r\n display your deck's stats p (manacost, mana curve, legalities, and more)\r\n Format deck into sections p\r\n Easily move cards to different sections gm, gs, go (Main, Sideboard, Other)\r\n Search for cards s\r\n Add searched cards to deck a, s, o (Main, Sideboard, Other)\r\n Select sort order for search o\r\n Limit Search to a format f\r\n Import decks by copying and pasting universal MTG deck export format\r\n\r\nHelp:\r\n :help vim-mtg\r\n\r\nGetting started:\r\n\r\n 1. Type in cards lines in the format '4 Ancient Den', or 'a'\r\n 2. :MTGSearch type:artifact\r\n 3. Use 'a' to add the current card in search buffer to the deck, 's' to add to sideboard, and 'o' to add to other, with an optional COUNT (e.g., 4a adds four of the currently selected card)\r\n 4. Use'p' to process the deck\r\n","install_details":"Use your plugin manager of choice. On Windows, replace the directory ~\/.vim with ~\/vimfiles.\r\n\r\nZip:\r\n\r\n Unzip to ~\/.vim\/pack\/bundle\/start\/\r\n\r\nGithub:\r\n\r\n Vim Packages\r\n git clone --recursive https:\/\/github.com\/yoshi1123\/vim-mtg ~\/.vim\/pack\/bundle\/start\/vim-mtg\r\n Run :helptags ~\/.vim\/pack\/bundle\/start\/vim-mtg\/doc\r\n Pathogen\r\n git clone --reursive https:\/\/github.com\/yoshi1123\/vim-mtg ~\/.vim\/bundle\/vim-mtg\r\n Vundle\r\n Add Bundle 'https:\/\/github.com\/yoshi1123\/vim-mtg' to .vimrc\r\n Run :BundleInstall\r\n NeoBundle\r\n Add NeoBundle 'https:\/\/github.com\/yoshi1123\/vim-mtg' to .vimrc\r\n Run :NeoBundleInstall\r\n vim-plug\r\n Add Plug 'https:\/\/github.com\/yoshi1123\/vim-mtg' to .vimrc\r\n Run :PlugInstall\r\n","5":"Use your plugin manager of choice. On Windows, replace the directory ~\/.vim with ~\/vimfiles.\r\n\r\nZip:\r\n\r\n Unzip to ~\/.vim\/pack\/bundle\/start\/\r\n\r\nGithub:\r\n\r\n Vim Packages\r\n git clone --recursive https:\/\/github.com\/yoshi1123\/vim-mtg ~\/.vim\/pack\/bundle\/start\/vim-mtg\r\n Run :helptags ~\/.vim\/pack\/bundle\/start\/vim-mtg\/doc\r\n Pathogen\r\n git clone --reursive https:\/\/github.com\/yoshi1123\/vim-mtg ~\/.vim\/bundle\/vim-mtg\r\n Vundle\r\n Add Bundle 'https:\/\/github.com\/yoshi1123\/vim-mtg' to .vimrc\r\n Run :BundleInstall\r\n NeoBundle\r\n Add NeoBundle 'https:\/\/github.com\/yoshi1123\/vim-mtg' to .vimrc\r\n Run :NeoBundleInstall\r\n vim-plug\r\n Add Plug 'https:\/\/github.com\/yoshi1123\/vim-mtg' to .vimrc\r\n Run :PlugInstall\r\n","first_name":"","6":"","last_name":"","7":"","releases":[{"0":"5898","vim_version":"7.0","1":"7.0","script_version":"0.1a1","2":"0.1a1","version_comment":"Initial upload","3":"Initial upload","package":"vim-mtg-0.1a1.zip","4":"vim-mtg-0.1a1.zip","src_id":"27289","5":"27289","creation_date":"1597796896","6":"1597796896"}]},"5897":{"script_id":"5897","0":"5897","script_name":"jcallers.vim","1":"jcallers.vim","script_type":"utility","2":"utility","summary":"grep calls to function under the cursor","3":"grep calls to function under the cursor","description":"Grep every calls to the function under the cursor with your grepprg.\r\n...closely organized like jreplace script is .. @see Vim wiki\r\n\r\n1 - Starts with a :normal mA .. AS A GLOBAL MARK [A] .. you can jump back to as a return point.\r\n\r\n2 - The resulting list will be inserted as a multi-line comment in the current buffer .. you can undo at will:\r\n \/* CALLERS::\r\n src\/file.js:485 caller_f:493: callee_f(args);\r\n src\/file.java:485 caller_f:493: callee_f(args);\r\n *\/\r\n3 - Let you navigate the grep quickfix resulting list.\r\n\r\nNotes:\r\n- Currently tuned up to catch .js and .java calling function def lines into the list third field.\r\n- And you will figure out how to get more by adjusting the F_callers:fdef pattern.\r\n\r\n- USES [A global mark] as a call return point\r\n...(there are 2 calls to [A mark] you can adjust to use another mark :normal mA and :normal 'A\r\n\r\n- USES [b register] to store the resulting multi-line-comment\r\n...(so as you can undo the insertion .. but keep the results handy)\r\n...(there are 3 setreg(b) calls you can adjust to use another register\r\n\r\n- USES [q register] to store the generated :grep call\r\n...(so you can use @q to edit and call it yourself later)\r\n...( :nnoremap Q @q .. may help )\r\n","4":"Grep every calls to the function under the cursor with your grepprg.\r\n...closely organized like jreplace script is .. @see Vim wiki\r\n\r\n1 - Starts with a :normal mA .. AS A GLOBAL MARK [A] .. you can jump back to as a return point.\r\n\r\n2 - The resulting list will be inserted as a multi-line comment in the current buffer .. you can undo at will:\r\n \/* CALLERS::\r\n src\/file.js:485 caller_f:493: callee_f(args);\r\n src\/file.java:485 caller_f:493: callee_f(args);\r\n *\/\r\n3 - Let you navigate the grep quickfix resulting list.\r\n\r\nNotes:\r\n- Currently tuned up to catch .js and .java calling function def lines into the list third field.\r\n- And you will figure out how to get more by adjusting the F_callers:fdef pattern.\r\n\r\n- USES [A global mark] as a call return point\r\n...(there are 2 calls to [A mark] you can adjust to use another mark :normal mA and :normal 'A\r\n\r\n- USES [b register] to store the resulting multi-line-comment\r\n...(so as you can undo the insertion .. but keep the results handy)\r\n...(there are 3 setreg(b) calls you can adjust to use another register\r\n\r\n- USES [q register] to store the generated :grep call\r\n...(so you can use @q to edit and call it yourself later)\r\n...( :nnoremap Q @q .. may help )\r\n","install_details":"- put the file where you put your other scripts (it has no dependency)\r\n- then map something to source it.\r\n...mine is:\r\n:nnoremap :so ~\/VIM\/scripts\/jcallers.vim\r\n\r\n","5":"- put the file where you put your other scripts (it has no dependency)\r\n- then map something to source it.\r\n...mine is:\r\n:nnoremap :so ~\/VIM\/scripts\/jcallers.vim\r\n\r\n","first_name":"ivan","6":"ivan","last_name":"wellesz","7":"wellesz","releases":[{"0":"5897","vim_version":"7.0","1":"7.0","script_version":"210626","2":"210626","version_comment":"added \\\\\\\",}\\\\\\\" to callee pattern to catch literal object embedding","3":"added \\\\\\\",}\\\\\\\" to callee pattern to catch literal object embedding","package":"jcallers.vim","4":"jcallers.vim","src_id":"27638","5":"27638","creation_date":"1624743710","6":"1624743710"},{"0":"5897","vim_version":"7.0","1":"7.0","script_version":"210430","2":"210430","version_comment":"1. Added egrep flavor dependent code comments:\r\n...so you can select regex that works for you.\r\n2. Inserted callee search pattern within results:\r\n...so you have an idea about why those results.","3":"1. Added egrep flavor dependent code comments:\r\n...so you can select regex that works for you.\r\n2. Inserted callee search pattern within results:\r\n...so you have an idea about why those results.","package":"jcallers.vim","4":"jcallers.vim","src_id":"27584","5":"27584","creation_date":"1619805609","6":"1619805609"},{"0":"5897","vim_version":"7.0","1":"7.0","script_version":"210320","2":"210320","version_comment":"...added [declared caller function] look-behind pattern (i.e. no var,let or const)","3":"...added [declared caller function] look-behind pattern (i.e. no var,let or const)","package":"jcallers.vim","4":"jcallers.vim","src_id":"27538","5":"27538","creation_date":"1616279502","6":"1616279502"},{"0":"5897","vim_version":"7.0","1":"7.0","script_version":"200830","2":"200830","version_comment":"Previous version sends untouched vim [*] search pattern to egrep... BUT:\r\n...regex escaping may be required .. depending on egrep flavors.\r\nPlease report about what you had to do at lines 65-66 to make it work for you...","3":"Previous version sends untouched vim [*] search pattern to egrep... BUT:\r\n...regex escaping may be required .. depending on egrep flavors.\r\nPlease report about what you had to do at lines 65-66 to make it work for you...","package":"jcallers.vim","4":"jcallers.vim","src_id":"27300","5":"27300","creation_date":"1598779611","6":"1598779611"},{"0":"5897","vim_version":"7.0","1":"7.0","script_version":"200805","2":"200805","version_comment":"previous version issue corrected .. first quickfix list entry was missed","3":"previous version issue corrected .. first quickfix list entry was missed","package":"jcallers.vim","4":"jcallers.vim","src_id":"27266","5":"27266","creation_date":"1596668241","6":"1596668241"},{"0":"5897","vim_version":"7.0","1":"7.0","script_version":"200731","2":"200731","version_comment":"Added protected access modifier to catch java caller's def-line","3":"Added protected access modifier to catch java caller's def-line","package":"jcallers.vim","4":"jcallers.vim","src_id":"27258","5":"27258","creation_date":"1596231589","6":"1596231589"},{"0":"5897","vim_version":"7.0","1":"7.0","script_version":"200729","2":"200729","version_comment":"- Some comments added near script lines that could be worth tuning\r\n...(so you can adjust to your liking)\r\n\r\n- Commented-out [word boundaries removal] from the searched function pattern\r\n..(so as to look for the EXACT word-under-the-cursor)","3":"- Some comments added near script lines that could be worth tuning\r\n...(so you can adjust to your liking)\r\n\r\n- Commented-out [word boundaries removal] from the searched function pattern\r\n..(so as to look for the EXACT word-under-the-cursor)","package":"jcallers.vim","4":"jcallers.vim","src_id":"27256","5":"27256","creation_date":"1596093256","6":"1596093256"},{"0":"5897","vim_version":"7.0","1":"7.0","script_version":"200728","2":"200728","version_comment":"Initial upload","3":"Initial upload","package":"jcallers.vim","4":"jcallers.vim","src_id":"27253","5":"27253","creation_date":"1595985800","6":"1595985800"}]},"5896":{"script_id":"5896","0":"5896","script_name":"vim-readonly","1":"vim-readonly","script_type":"utility","2":"utility","summary":"Automatically set readonly option on specific files.","3":"Automatically set readonly option on specific files.","description":"# readonly.vim\n[![Script manager: vishop](https:\/\/img.shields.io\/badge\/script%20manager-vishop-blueviolet)](https:\/\/github.com\/Xvezda\/vishop)\n\nAutomatically set readonly option on specific files.\n\nThis plugin is useful when if you are person like me,\nwho likes to look around internal or package manager managed (i.e. pip, npm, etc.)\nsource codes with vim.\n\nIt protects original source code from modifying accidentally by user.\n\n\n## Installation\n\nUsing vim-plug:\n```vim\nPlug 'Xvezda\/vim-readonly'\n```\n\nor\n\n```sh\nmake install\n```\n\n## Usage\n\n`g:readonly_automatic` is enabled by default.\n\nUse `:Readonly` to manually enable readonly option, and `:Readonly!` to disable.\n\n\n## Global options\n\n| Flag | Description | Default |\n| ---------------------- | -------------------------------------------------- | ------- |\n| `g:readonly_automatic` | Automatically set readonly when patterns are match | `1` |\n| `g:readonly_paths` | Set patterns of path to set readonly option | `['\/usr\/bin\/lib\/', '\/usr\/local\/lib\/', '\/usr\/local\/include\/']` |\n| `g:readonly_nodejs` | Add NodeJs package path to readonly paths | `1` |\n| `g:readonly_python` | Add python package path to readonly paths | `1` |\n| `g:readonly_check_virtualenv` | Add python virtualenv path to readonly paths when virtualenv is activated | `1` |\n\n\n## Homepage\n\nhttps:\/\/github.com\/Xvezda\/vim-readonly\n\n\n## Copyright\n\nCopyright (C) 2020 Xvezda\n\nMIT License\n","4":"# readonly.vim\n[![Script manager: vishop](https:\/\/img.shields.io\/badge\/script%20manager-vishop-blueviolet)](https:\/\/github.com\/Xvezda\/vishop)\n\nAutomatically set readonly option on specific files.\n\nThis plugin is useful when if you are person like me,\nwho likes to look around internal or package manager managed (i.e. pip, npm, etc.)\nsource codes with vim.\n\nIt protects original source code from modifying accidentally by user.\n\n\n## Installation\n\nUsing vim-plug:\n```vim\nPlug 'Xvezda\/vim-readonly'\n```\n\nor\n\n```sh\nmake install\n```\n\n## Usage\n\n`g:readonly_automatic` is enabled by default.\n\nUse `:Readonly` to manually enable readonly option, and `:Readonly!` to disable.\n\n\n## Global options\n\n| Flag | Description | Default |\n| ---------------------- | -------------------------------------------------- | ------- |\n| `g:readonly_automatic` | Automatically set readonly when patterns are match | `1` |\n| `g:readonly_paths` | Set patterns of path to set readonly option | `['\/usr\/bin\/lib\/', '\/usr\/local\/lib\/', '\/usr\/local\/include\/']` |\n| `g:readonly_nodejs` | Add NodeJs package path to readonly paths | `1` |\n| `g:readonly_python` | Add python package path to readonly paths | `1` |\n| `g:readonly_check_virtualenv` | Add python virtualenv path to readonly paths when virtualenv is activated | `1` |\n\n\n## Homepage\n\nhttps:\/\/github.com\/Xvezda\/vim-readonly\n\n\n## Copyright\n\nCopyright (C) 2020 Xvezda\n\nMIT License\n","install_details":"","5":"","first_name":"Y.","6":"Y.","last_name":"Choi","7":"Choi","releases":[{"0":"5896","vim_version":"7.0","1":"7.0","script_version":"1.3","2":"1.3","version_comment":"+ Add vim runtime path","3":"+ Add vim runtime path","package":"vim-readonly-1.3.tar.gz","4":"vim-readonly-1.3.tar.gz","src_id":"27407","5":"27407","creation_date":"1608425499","6":"1608425499"},{"0":"5896","vim_version":"7.0","1":"7.0","script_version":"1.2","2":"1.2","version_comment":"+ Fix performance issue (startup time)","3":"+ Fix performance issue (startup time)","package":"vim-readonly-1.2.tar.gz","4":"vim-readonly-1.2.tar.gz","src_id":"27312","5":"27312","creation_date":"1600505245","6":"1600505245"},{"0":"5896","vim_version":"7.0","1":"7.0","script_version":"1.1","2":"1.1","version_comment":"+ Fix python develop mode issue","3":"+ Fix python develop mode issue","package":"vim-readonly-1.1.tar.gz","4":"vim-readonly-1.1.tar.gz","src_id":"27233","5":"27233","creation_date":"1593950101","6":"1593950101"},{"0":"5896","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"vim-readonly-1.0.tar.gz","4":"vim-readonly-1.0.tar.gz","src_id":"27231","5":"27231","creation_date":"1593883446","6":"1593883446"}]},"5895":{"script_id":"5895","0":"5895","script_name":"vim-bujo","1":"vim-bujo","script_type":"utility","2":"utility","summary":"Manage todolist with vim","3":"Manage todolist with vim","description":"This plugin allows people to easily access and\r\nmanage a todo list.\r\n\r\nYou can stable versions of this plugin at: \r\n\r\nhttps:\/\/github.com\/vuciv\/vim-bujo\r\n\r\nFeedback and bug reports are welcomed and encouraged.\r\nIf you want new features, please do let me know. I\r\nwould be honored at the opportunity to make a tool\r\nbetter.\r\n\r\nI built this because I wanted the ease of vim bindings\r\nwith the benefits of keeping a todo list on hand. It is\r\nvery simple and minimialist.\r\n","4":"This plugin allows people to easily access and\r\nmanage a todo list.\r\n\r\nYou can stable versions of this plugin at: \r\n\r\nhttps:\/\/github.com\/vuciv\/vim-bujo\r\n\r\nFeedback and bug reports are welcomed and encouraged.\r\nIf you want new features, please do let me know. I\r\nwould be honored at the opportunity to make a tool\r\nbetter.\r\n\r\nI built this because I wanted the ease of vim bindings\r\nwith the benefits of keeping a todo list on hand. It is\r\nvery simple and minimialist.\r\n","install_details":"If you use a plugin manager, such as vim-plug, follow its instructions on how to install plugins from github.\r\n\r\nTo install the stable version of the plugin, if using vim-plug, put this in your vimrc\/init.vim:\r\n\r\nPlug 'vuciv\/vim-bujo'\r\n","5":"If you use a plugin manager, such as vim-plug, follow its instructions on how to install plugins from github.\r\n\r\nTo install the stable version of the plugin, if using vim-plug, put this in your vimrc\/init.vim:\r\n\r\nPlug 'vuciv\/vim-bujo'\r\n","first_name":"Jersey","6":"Jersey","last_name":"Fonseca","7":"Fonseca","releases":[{"0":"5895","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"vim-bujo-master.zip","4":"vim-bujo-master.zip","src_id":"27215","5":"27215","creation_date":"1593087160","6":"1593087160"}]},"5894":{"script_id":"5894","0":"5894","script_name":"jobs.vim","1":"jobs.vim","script_type":"utility","2":"utility","summary":"Run system commands in background.","3":"Run system commands in background.","description":"Tool to be used on other plugins to launch system commands in background.\r\n\r\nIncludes several commands to check the commands in progress (Jobsl).\r\n\r\nStop all commands in background (Jobska)\r\n\r\nChoose wich commands in background to stop (Jobsk)\r\n\r\nShoww all commands in background related to current vim window (Jobshw)\r\n\r\nShoww all commands history (Jobshy)\r\n\r\nUse :Jobsh to show command help.\r\n\r\nExample:\r\n function! svnTools#Blame()\r\n \u00c2\u00a6 let file = expand(\"%\")\r\n \u00c2\u00a6 let name = expand(\"%:t\")\r\n \u00c2\u00a6 let pos = line('.')\r\n \u00c2\u00a6 let ext = s:GetSyntax()\r\n\r\n \u00c2\u00a6 let command = \"svn blame -v \".l:file\r\n \u00c2\u00a6 let callback = \"svnTools#SvnBlameEnd(\\\"\".l:pos.\"\\\",\\\"\".l:ext.\"\\\",\\\"\".l:name.\"\\\",\"\r\n \u00c2\u00a6 let l:async = 1\r\n\r\n \u00c2\u00a6 call jobs#RunCmd(a:command, a:callback, l:async, \"svn\")\r\n endfunction\r\n\r\n function! svnTools#SvnBlameEnd(pos,ext,name,resfile)\r\n \u00c2\u00a6 if exists('a:resfile') && !empty(glob(a:resfile))\r\n \u00c2\u00a6 \u00c2\u00a6 \" Process the svn blame file\r\n \u00c2\u00a6 else\r\n \u00c2\u00a6 \u00c2\u00a6 echo \"ERROR. Svn blame empty\"\r\n \u00c2\u00a6 endif\r\n endfunction\r\n\r\n","4":"Tool to be used on other plugins to launch system commands in background.\r\n\r\nIncludes several commands to check the commands in progress (Jobsl).\r\n\r\nStop all commands in background (Jobska)\r\n\r\nChoose wich commands in background to stop (Jobsk)\r\n\r\nShoww all commands in background related to current vim window (Jobshw)\r\n\r\nShoww all commands history (Jobshy)\r\n\r\nUse :Jobsh to show command help.\r\n\r\nExample:\r\n function! svnTools#Blame()\r\n \u00c2\u00a6 let file = expand(\"%\")\r\n \u00c2\u00a6 let name = expand(\"%:t\")\r\n \u00c2\u00a6 let pos = line('.')\r\n \u00c2\u00a6 let ext = s:GetSyntax()\r\n\r\n \u00c2\u00a6 let command = \"svn blame -v \".l:file\r\n \u00c2\u00a6 let callback = \"svnTools#SvnBlameEnd(\\\"\".l:pos.\"\\\",\\\"\".l:ext.\"\\\",\\\"\".l:name.\"\\\",\"\r\n \u00c2\u00a6 let l:async = 1\r\n\r\n \u00c2\u00a6 call jobs#RunCmd(a:command, a:callback, l:async, \"svn\")\r\n endfunction\r\n\r\n function! svnTools#SvnBlameEnd(pos,ext,name,resfile)\r\n \u00c2\u00a6 if exists('a:resfile') && !empty(glob(a:resfile))\r\n \u00c2\u00a6 \u00c2\u00a6 \" Process the svn blame file\r\n \u00c2\u00a6 else\r\n \u00c2\u00a6 \u00c2\u00a6 echo \"ERROR. Svn blame empty\"\r\n \u00c2\u00a6 endif\r\n endfunction\r\n\r\n","install_details":"Minimum version: Vim 8.0+\r\n\r\nSimplest method:\r\n- Just unzip to your .vim folder.\r\n\r\nPlugin manager:\r\n- Either vim-pathogen or Vundle are recommended. ","5":"Minimum version: Vim 8.0+\r\n\r\nSimplest method:\r\n- Just unzip to your .vim folder.\r\n\r\nPlugin manager:\r\n- Either vim-pathogen or Vundle are recommended. ","first_name":"Javier","6":"Javier","last_name":"Puigdevall","7":"Puigdevall","releases":[{"0":"5894","vim_version":"7.0","1":"7.0","script_version":"0.1.1","2":"0.1.1","version_comment":"- New: hide passwords, prevent showing command passwords on the command line, instead replace the password with * characters. \r\n Use option: g:jobs_hidePsswd to dissable it password hidding. ","3":"- New: hide passwords, prevent showing command passwords on the command line, instead replace the password with * characters. \r\n Use option: g:jobs_hidePsswd to dissable it password hidding. ","package":"jobs_0.1.1.vmb","4":"jobs_0.1.1.vmb","src_id":"27621","5":"27621","creation_date":"1622244956","6":"1622244956"},{"0":"5894","vim_version":"8.0","1":"8.0","script_version":"0.0..1","2":"0.0..1","version_comment":"Initial upload","3":"Initial upload","package":"jobs.tar.gz","4":"jobs.tar.gz","src_id":"27212","5":"27212","creation_date":"1592865385","6":"1592865385"}]},"5893":{"script_id":"5893","0":"5893","script_name":"svnTools","1":"svnTools","script_type":"utility","2":"utility","summary":"Perform subversion commands from within vim.","3":"Perform subversion commands from within vim.","description":"Allows to launch several svn commands from within vim.\r\n\r\nAlso at: https:\/\/github.com\/javipv\/svnTools\r\n\r\nUse :Svnh to show a command help.\r\n\r\n- Info commands:\r\n Svni : get current revision info.\r\n Svnif : get current file revision info.\r\n\r\n- Blame commands:\r\n Svnbl : get blame of current file.\r\n Svnblv : get verbose blame of current file.\r\n\r\n- Status commands:\r\n Svnst : show file's status (conceal symbols: X and ?).\r\n Svnsta : show status files (show all symbols).\r\n Svnstf : show current file status.\r\n Svnstd : show current directory status.\r\n Svnsth : show the svn status symbols' help.\r\n\r\n- Log commands:\r\n Svnl [NUM] : get subversion log (num. commits, defaults to 3000).\r\n Svnls PATTERN [NUM] : log search pattern (num. commits, defaults to 3000).\r\n Svnlf FILEPATH : show file log.\r\n\r\n- Diff commands:\r\n Svndf : get diff of changes on current file.\r\n Svndd : get diff of changes on current directory.\r\n Svnda : get diff of changes on current workind directory.\r\n\r\n- Diff files with vimdiff commands:\r\n Svnvda : show (vimdiff) all files with changes (alows to skip binaries).\r\n SvnvdA : show (vimdiff) selected files with changes (alows to skip binaries).\r\n Svnvdf : show (vimdiff) current file changes.\r\n Svnvdd : show (vimdiff) current directory changes.\r\n Svnvdr REV : show revision log and open the selected revision changes with vimdiff. \r\n \r\n- Directory compare commands (sandbox compare):\r\n Svndc DIR1 DIR2 : show (diff) changes between two directories.\r\n SvndC DIR1 DIR2 : show (diff) changes between two directories, skip binaries.\r\n Svnvdc DIR1 DIR2 : show (vimdiff) changes between two directories.\r\n SvnvdC DIR1 DIR2 : show (vimdiff) changes between two directories, skip binaries, files not differing.\r\n - Revision commands:\r\n Svnr REV : get diff of selected revision number.\r\n Svncr REV : cat revision number\r\n\r\n- Conflicts commands:\r\n Svnm [LAYOUT] : merge all conflicts with vimdiff. Layouts: 0 1 2 (default layout: 2).\r\n Svnmf [LAYOUT] : merge current file conflict with vimdiff. Layouts: 0 1 2 (default layout: 2).\r\n Svnmp FILE [LAYOUT] : merge file conflict with vimdiff. Layouts: 0 1 2 (default layout: 2).\r\n Svnres [all] : perform svn resolve. Use 'all' to resolve all conflicts.\r\n Svnmh : show merge layout help.\r\n\r\n- Password settings:\r\n Optional, if you don't want to use keyring or similar programs.\r\n The svn password will only be stored for the current vim session.\r\n let g:svnTools_userAndPsswd = 1\r\n let g:svnTools_svnUser = \"MY_SVN_USER\"\r\n let g:svnTools_storeSvnPsswd = 1\r\n","4":"Allows to launch several svn commands from within vim.\r\n\r\nAlso at: https:\/\/github.com\/javipv\/svnTools\r\n\r\nUse :Svnh to show a command help.\r\n\r\n- Info commands:\r\n Svni : get current revision info.\r\n Svnif : get current file revision info.\r\n\r\n- Blame commands:\r\n Svnbl : get blame of current file.\r\n Svnblv : get verbose blame of current file.\r\n\r\n- Status commands:\r\n Svnst : show file's status (conceal symbols: X and ?).\r\n Svnsta : show status files (show all symbols).\r\n Svnstf : show current file status.\r\n Svnstd : show current directory status.\r\n Svnsth : show the svn status symbols' help.\r\n\r\n- Log commands:\r\n Svnl [NUM] : get subversion log (num. commits, defaults to 3000).\r\n Svnls PATTERN [NUM] : log search pattern (num. commits, defaults to 3000).\r\n Svnlf FILEPATH : show file log.\r\n\r\n- Diff commands:\r\n Svndf : get diff of changes on current file.\r\n Svndd : get diff of changes on current directory.\r\n Svnda : get diff of changes on current workind directory.\r\n\r\n- Diff files with vimdiff commands:\r\n Svnvda : show (vimdiff) all files with changes (alows to skip binaries).\r\n SvnvdA : show (vimdiff) selected files with changes (alows to skip binaries).\r\n Svnvdf : show (vimdiff) current file changes.\r\n Svnvdd : show (vimdiff) current directory changes.\r\n Svnvdr REV : show revision log and open the selected revision changes with vimdiff. \r\n \r\n- Directory compare commands (sandbox compare):\r\n Svndc DIR1 DIR2 : show (diff) changes between two directories.\r\n SvndC DIR1 DIR2 : show (diff) changes between two directories, skip binaries.\r\n Svnvdc DIR1 DIR2 : show (vimdiff) changes between two directories.\r\n SvnvdC DIR1 DIR2 : show (vimdiff) changes between two directories, skip binaries, files not differing.\r\n - Revision commands:\r\n Svnr REV : get diff of selected revision number.\r\n Svncr REV : cat revision number\r\n\r\n- Conflicts commands:\r\n Svnm [LAYOUT] : merge all conflicts with vimdiff. Layouts: 0 1 2 (default layout: 2).\r\n Svnmf [LAYOUT] : merge current file conflict with vimdiff. Layouts: 0 1 2 (default layout: 2).\r\n Svnmp FILE [LAYOUT] : merge file conflict with vimdiff. Layouts: 0 1 2 (default layout: 2).\r\n Svnres [all] : perform svn resolve. Use 'all' to resolve all conflicts.\r\n Svnmh : show merge layout help.\r\n\r\n- Password settings:\r\n Optional, if you don't want to use keyring or similar programs.\r\n The svn password will only be stored for the current vim session.\r\n let g:svnTools_userAndPsswd = 1\r\n let g:svnTools_svnUser = \"MY_SVN_USER\"\r\n let g:svnTools_storeSvnPsswd = 1\r\n","install_details":"Minimum version: Vim 7.0+\r\nRecomended version: Vim 8.0+ \r\n\r\nInstall vimball:\r\ndownload svnTools_2.0.1.vmb\r\nvim svnTools_2.0.1.vmb\r\n:so %\r\n:q ","5":"Minimum version: Vim 7.0+\r\nRecomended version: Vim 8.0+ \r\n\r\nInstall vimball:\r\ndownload svnTools_2.0.1.vmb\r\nvim svnTools_2.0.1.vmb\r\n:so %\r\n:q ","first_name":"Javier","6":"Javier","last_name":"Puigdevall","7":"Puigdevall","releases":[{"0":"5893","vim_version":"7.0","1":"7.0","script_version":"2.0.1","2":"2.0.1","version_comment":"- New: command Vdd, compare with vimdiff all files found on different directories.\r\n allows to filter files (flags: +fileX, -fileY), skip\/keep-only binaries (flags: SB, BO) and\/or skip\/keep-only equal files (flags: SE, EO).\r\n- New: command Vdf, compare current file with same file on a different directory.\r\n When the structure paths are the same in both sides, passing as argument the other working directory is enough. ex: 'Vdf ~\/Projects\/dir2\/'\r\n When comparing directories on the same path, only need to change the directory name. ex: compare same file on sandbox1 with dir2: 'Vdf sandbox1 dir2'\r\n When comparing directories on the same path, only need to change the directory part to be replaced.ex: compare same file on dir1 with dir2: 'Vdf 1 2'\r\n- New: commands SvnD, SvnDD and SvnDA. Advanced diff on path, allows to filter files (flags: +fileX, -fileY), and skip\/keep-only binaries (flags: SB, BO).\r\n- New: commands SvnVD, SvnVDD and SvnVDA. Advanced vimdiff on path, allows to filter files (flags: +fileX -fileY), and skip\/keep-only binaries (flags: SB, BO).\r\n- New: Svndc and Svnvdc admit flags SE and SB to skip equal files and binary files. use falgs C1 or C2 to check only changes on path1 or path2.","3":"- New: command Vdd, compare with vimdiff all files found on different directories.\r\n allows to filter files (flags: +fileX, -fileY), skip\/keep-only binaries (flags: SB, BO) and\/or skip\/keep-only equal files (flags: SE, EO).\r\n- New: command Vdf, compare current file with same file on a different directory.\r\n When the structure paths are the same in both sides, passing as argument the other working directory is enough. ex: 'Vdf ~\/Projects\/dir2\/'\r\n When comparing directories on the same path, only need to change the directory name. ex: compare same file on sandbox1 with dir2: 'Vdf sandbox1 dir2'\r\n When comparing directories on the same path, only need to change the directory part to be replaced.ex: compare same file on dir1 with dir2: 'Vdf 1 2'\r\n- New: commands SvnD, SvnDD and SvnDA. Advanced diff on path, allows to filter files (flags: +fileX, -fileY), and skip\/keep-only binaries (flags: SB, BO).\r\n- New: commands SvnVD, SvnVDD and SvnVDA. Advanced vimdiff on path, allows to filter files (flags: +fileX -fileY), and skip\/keep-only binaries (flags: SB, BO).\r\n- New: Svndc and Svnvdc admit flags SE and SB to skip equal files and binary files. use falgs C1 or C2 to check only changes on path1 or path2.","package":"svnTools_2.0.1.vmb","4":"svnTools_2.0.1.vmb","src_id":"27954","5":"27954","creation_date":"1645815888","6":"1645815888"},{"0":"5893","vim_version":"7.4","1":"7.4","script_version":"2.0.0","2":"2.0.0","version_comment":"- REFACTORING of the plugin to divide in different files.\r\n- New: on SvnvdC and Svnvdc commands: allow to skip or keep only the files matching the required patterns.\r\n- New: Svnedit command, not showing the plugint\/svnTools.vim file.\r\n New autoload\/svnTools\/ folder to save the plugin files.\r\n- New: save and restore changes' functions: Svncsv, Svncvd, Svncvdd, Svncr.\r\n Allowing to save, compare and restore changes.\r\n Every time we save changes a new directory is created: _svnTools_changes_YYMMDD_HHMMSS\/\r\n Every modified file is saved as: dir1___dir2___dir3__filename.ext\r\n- New: Svnpwd command, enter user and password.\r\n- New: on Svndvda, Svnvdd commands: allow user to select the files to perform the vimdiff.\r\n- New: on Svndvda, Svnvdd commands: allow user to filter files adding splace separated filter patterns.","3":"- REFACTORING of the plugin to divide in different files.\r\n- New: on SvnvdC and Svnvdc commands: allow to skip or keep only the files matching the required patterns.\r\n- New: Svnedit command, not showing the plugint\/svnTools.vim file.\r\n New autoload\/svnTools\/ folder to save the plugin files.\r\n- New: save and restore changes' functions: Svncsv, Svncvd, Svncvdd, Svncr.\r\n Allowing to save, compare and restore changes.\r\n Every time we save changes a new directory is created: _svnTools_changes_YYMMDD_HHMMSS\/\r\n Every modified file is saved as: dir1___dir2___dir3__filename.ext\r\n- New: Svnpwd command, enter user and password.\r\n- New: on Svndvda, Svnvdd commands: allow user to select the files to perform the vimdiff.\r\n- New: on Svndvda, Svnvdd commands: allow user to filter files adding splace separated filter patterns.","package":"svnTools_2.0.0.vmb","4":"svnTools_2.0.0.vmb","src_id":"27917","5":"27917","creation_date":"1642807266","6":"1642807266"},{"0":"5893","vim_version":"7.0","1":"7.0","script_version":"1.0.6","2":"1.0.6","version_comment":"- New: Svndvdr command, when placed on an svn log and diff file (obtained from Svnr, Svnda, Svndd or Svndf), for each file open the vimdiff of the current log's file revision. \r\n- New configuration option g:svnTools_userAndPsswd to use non interactive snv and send user and password in the same command: let g:svnTools_userAndPsswd = 1 \r\n- New options to manage svn user and password: g:svnTools_svnUser, g:svnTool_storeSvnPsswd.","3":"- New: Svndvdr command, when placed on an svn log and diff file (obtained from Svnr, Svnda, Svndd or Svndf), for each file open the vimdiff of the current log's file revision. \r\n- New configuration option g:svnTools_userAndPsswd to use non interactive snv and send user and password in the same command: let g:svnTools_userAndPsswd = 1 \r\n- New options to manage svn user and password: g:svnTools_svnUser, g:svnTool_storeSvnPsswd.","package":"svnTools_1.0.6.vmb","4":"svnTools_1.0.6.vmb","src_id":"27620","5":"27620","creation_date":"1622244567","6":"1622244567"},{"0":"5893","vim_version":"7.0","1":"7.0","script_version":"1.0.5","2":"1.0.5","version_comment":"- New: Svnlr command, when placed on an svn log file, for each revision\r\n number get its log and diff changes.\r\n- Fix Svnm command, treat status ' C ' as file in conflict.\r\n- Fix Svnm command, treat status !.*C as file in conflict.\r\n- Fix Svnm command, do not try opening merge tool when file in confict is not found.\r\n- Fix GetStatusFilesList function, file path is last column not second one.\r\n- New Svnvmb command, development command to create a vimball release of the plugin.\r\n","3":"- New: Svnlr command, when placed on an svn log file, for each revision\r\n number get its log and diff changes.\r\n- Fix Svnm command, treat status ' C ' as file in conflict.\r\n- Fix Svnm command, treat status !.*C as file in conflict.\r\n- Fix Svnm command, do not try opening merge tool when file in confict is not found.\r\n- Fix GetStatusFilesList function, file path is last column not second one.\r\n- New Svnvmb command, development command to create a vimball release of the plugin.\r\n","package":"svnTools_1.0.5.vmb","4":"svnTools_1.0.5.vmb","src_id":"27500","5":"27500","creation_date":"1614368019","6":"1614368019"},{"0":"5893","vim_version":"7.0","1":"7.0","script_version":"1.0.4","2":"1.0.4","version_comment":"- New on Svnda, Svndd, Svndf: do not allow to modify or save the revision file on vimdiff. \r\n- New Svndc command, show diff between files with changes on two different directories. \r\n- New Svndc command, show diff between files with changes on two different directories, skip binary files. \r\n- New Svnmh command: show merge layout help. ","3":"- New on Svnda, Svndd, Svndf: do not allow to modify or save the revision file on vimdiff. \r\n- New Svndc command, show diff between files with changes on two different directories. \r\n- New Svndc command, show diff between files with changes on two different directories, skip binary files. \r\n- New Svnmh command: show merge layout help. ","package":"svnTools.vmb","4":"svnTools.vmb","src_id":"27403","5":"27403","creation_date":"1608142406","6":"1608142406"},{"0":"5893","vim_version":"7.0","1":"7.0","script_version":"1.0.3","2":"1.0.3","version_comment":"- New SvnvdA command. For every modifed file, allows user to get vimdiff, skip (this\/all\/none) file, \r\n skip (this\/all\/none) binaries. \r\n- New on Svnvdf\/Svnvdd\/Svnvda check if file is binary, ask user to skip binary files. \r\n- New on Svnvdc will now show only files with differecnes, omitt any files that do not differ. \r\n- New Svnvdca command to show all changes between directories. \r\n- Fix GetStatusFilesString issue affecting svnTools#VimDiffCompareDirChanges. \r\n- Add Svnm command to merge commit upon conflict. \r\n- Add Svnrv command to resolve commit conflicts. \r\n- Add Svnst commands to show svn status. \r\n- Adapt to jobs.vim 0.1.0 \r\n- Add Svnvdr command to show vimdiff on files modified on selected revision. ","3":"- New SvnvdA command. For every modifed file, allows user to get vimdiff, skip (this\/all\/none) file, \r\n skip (this\/all\/none) binaries. \r\n- New on Svnvdf\/Svnvdd\/Svnvda check if file is binary, ask user to skip binary files. \r\n- New on Svnvdc will now show only files with differecnes, omitt any files that do not differ. \r\n- New Svnvdca command to show all changes between directories. \r\n- Fix GetStatusFilesString issue affecting svnTools#VimDiffCompareDirChanges. \r\n- Add Svnm command to merge commit upon conflict. \r\n- Add Svnrv command to resolve commit conflicts. \r\n- Add Svnst commands to show svn status. \r\n- Adapt to jobs.vim 0.1.0 \r\n- Add Svnvdr command to show vimdiff on files modified on selected revision. ","package":"svnTools.vmb","4":"svnTools.vmb","src_id":"27400","5":"27400","creation_date":"1607630516","6":"1607630516"},{"0":"5893","vim_version":"7.0","1":"7.0","script_version":"1.01","2":"1.01","version_comment":"Initial upload","3":"Initial upload","package":"svnTools.tar.gz","4":"svnTools.tar.gz","src_id":"27211","5":"27211","creation_date":"1592865214","6":"1592865214"}]},"5892":{"script_id":"5892","0":"5892","script_name":"kanvim","1":"kanvim","script_type":"ftplugin","2":"ftplugin","summary":"Simple Kanban board for Vim","3":"Simple Kanban board for Vim","description":"Simple Kanban board for Vim\r\nProject website: \r\n","4":"Simple Kanban board for Vim\r\nProject website: \r\n","install_details":"","5":"","first_name":"Vitor","6":"Vitor","last_name":"Guia","7":"Guia","releases":[{"0":"5892","vim_version":"7.0","1":"7.0","script_version":"1.0.0","2":"1.0.0","version_comment":"Initial upload","3":"Initial upload","package":"kanvim.tar.gz","4":"kanvim.tar.gz","src_id":"27207","5":"27207","creation_date":"1592618061","6":"1592618061"}]},"5891":{"script_id":"5891","0":"5891","script_name":"winStack","1":"winStack","script_type":"utility","2":"utility","summary":"Commands to manage window splits as a window stack.","3":"Commands to manage window splits as a window stack.","description":"Based on a window layout configuration with two vertical splits, one without horizontal splits (main window), the other with several horizontal splits (window stack).\r\n\r\nAso on: https:\/\/github.com\/javipv\/winStack\r\n\r\n1) Window layout with stack on the right:\r\n\r\n Main Stack\r\n+-------------+---------------+\r\n| | Window 2 |\r\n| +---------------+\r\n| | Window 3 |\r\n| Window 1+---------------+\r\n| | Window 4 |\r\n+-------------+---------------+\r\n\r\n2) Window layout with stack on the left:\r\nlet g:windowStack_defaultSide = \"left\"\r\n\r\n Stack Main\r\n+---------------+---------------+\r\n| Window 1 | |\r\n+---------------+ |\r\n| Window 2 | Window 4 |\r\n+---------------+ |\r\n| Window 3 | |\r\n+---------------+---------------+\r\n\r\nThe plugin helps moving a buffer to the main window, add it to the window stack as a new split, or exchange buffers between stack tnd main window.\r\n\r\nQuickix items can be opened too on the stack or main window directly from the quickfix list .\r\n\r\nRecomended .vimrc mappings:\r\nnmap :WinUnstack\r\nnmap :WinStack\r\n\r\nCommands:\r\n\r\n:WinStack, ws or \r\nStack a window, move it to the bottom of the window stack.\r\n\r\n:WinUnstack, wu or \r\nUnstack a window, move it to the main window split.\r\n\r\n:WinStTest\r\nOpen an example window layout to test the commands.\r\n","4":"Based on a window layout configuration with two vertical splits, one without horizontal splits (main window), the other with several horizontal splits (window stack).\r\n\r\nAso on: https:\/\/github.com\/javipv\/winStack\r\n\r\n1) Window layout with stack on the right:\r\n\r\n Main Stack\r\n+-------------+---------------+\r\n| | Window 2 |\r\n| +---------------+\r\n| | Window 3 |\r\n| Window 1+---------------+\r\n| | Window 4 |\r\n+-------------+---------------+\r\n\r\n2) Window layout with stack on the left:\r\nlet g:windowStack_defaultSide = \"left\"\r\n\r\n Stack Main\r\n+---------------+---------------+\r\n| Window 1 | |\r\n+---------------+ |\r\n| Window 2 | Window 4 |\r\n+---------------+ |\r\n| Window 3 | |\r\n+---------------+---------------+\r\n\r\nThe plugin helps moving a buffer to the main window, add it to the window stack as a new split, or exchange buffers between stack tnd main window.\r\n\r\nQuickix items can be opened too on the stack or main window directly from the quickfix list .\r\n\r\nRecomended .vimrc mappings:\r\nnmap :WinUnstack\r\nnmap :WinStack\r\n\r\nCommands:\r\n\r\n:WinStack, ws or \r\nStack a window, move it to the bottom of the window stack.\r\n\r\n:WinUnstack, wu or \r\nUnstack a window, move it to the main window split.\r\n\r\n:WinStTest\r\nOpen an example window layout to test the commands.\r\n","install_details":"Simplest method:\r\n- Just unzip to your .vim folder.\r\n\r\nPlugin manager:\r\n- Either vim-pathogen or Vundle are recommended. ","5":"Simplest method:\r\n- Just unzip to your .vim folder.\r\n\r\nPlugin manager:\r\n- Either vim-pathogen or Vundle are recommended. ","first_name":"Javier","6":"Javier","last_name":"Puigdevall","7":"Puigdevall","releases":[{"0":"5891","vim_version":"7.0","1":"7.0","script_version":"0.0.1","2":"0.0.1","version_comment":"Initial upload","3":"Initial upload","package":"winStack.tar.gz","4":"winStack.tar.gz","src_id":"27206","5":"27206","creation_date":"1592422806","6":"1592422806"}]},"5890":{"script_id":"5890","0":"5890","script_name":"vim-nobin","1":"vim-nobin","script_type":"utility","2":"utility","summary":"Plugin to load original source code instead of executable binary.","3":"Plugin to load original source code instead of executable binary.","description":"# nobin.vim\r\n\r\n![Demo](https:\/\/gist.githubusercontent.com\/Xvezda\/ee6613c4ae2ce743b445f2cfc6e837b2\/raw\/17ceb993c092c12207d0a0f12a62ad763723af61\/vim-nobin.gif)\r\n\r\nI made this plugin because of auto-completion on shell environment always lead me to open a binary, not a source code.\r\n\r\n`gcc test.c -o test`\r\n\r\nIn this case, there are two files in the same directory. `test.c` and `test`.\r\n\r\n`vim t`\r\n\r\nNow, if I press tab to edit `test.c` again, `test` will appears.\r\nI need to press tab again to make `test` to `test.c`\r\n\r\nBut most of times, I accidently open `test` binary instead.\r\nIt's way too frustrating. :(\r\n\r\nThis plugin will automatically finds original source code of executable binary, which you opened by mistake. :)\r\n\r\n## Installation\r\n\r\nUsing [vim-plug](https:\/\/github.com\/junegunn\/vim-plug):\r\n\r\n`Plug 'Xvezda\/vim-nobin'`\r\n\r\nor\r\n\r\n`make install`\r\n\r\n\r\n## Global options\r\n\r\n| Flag | Description |\r\n|-------------------------------|---------------------------------------------------------- |\r\n| `g:nobin_always_yes` | Automatically select [y]es on select screen |\r\n| `g:nobin_well_known_files` | Regular expression list for well known binary patterns |\r\n| `g:nobin_accept_trailing_dot` | Accept trailing dot file name (Useful when you type and tab completion including dot) |\r\n| `g:nobin_except_files` | Exception patterns of non-binary files |\r\n","4":"# nobin.vim\r\n\r\n![Demo](https:\/\/gist.githubusercontent.com\/Xvezda\/ee6613c4ae2ce743b445f2cfc6e837b2\/raw\/17ceb993c092c12207d0a0f12a62ad763723af61\/vim-nobin.gif)\r\n\r\nI made this plugin because of auto-completion on shell environment always lead me to open a binary, not a source code.\r\n\r\n`gcc test.c -o test`\r\n\r\nIn this case, there are two files in the same directory. `test.c` and `test`.\r\n\r\n`vim t`\r\n\r\nNow, if I press tab to edit `test.c` again, `test` will appears.\r\nI need to press tab again to make `test` to `test.c`\r\n\r\nBut most of times, I accidently open `test` binary instead.\r\nIt's way too frustrating. :(\r\n\r\nThis plugin will automatically finds original source code of executable binary, which you opened by mistake. :)\r\n\r\n## Installation\r\n\r\nUsing [vim-plug](https:\/\/github.com\/junegunn\/vim-plug):\r\n\r\n`Plug 'Xvezda\/vim-nobin'`\r\n\r\nor\r\n\r\n`make install`\r\n\r\n\r\n## Global options\r\n\r\n| Flag | Description |\r\n|-------------------------------|---------------------------------------------------------- |\r\n| `g:nobin_always_yes` | Automatically select [y]es on select screen |\r\n| `g:nobin_well_known_files` | Regular expression list for well known binary patterns |\r\n| `g:nobin_accept_trailing_dot` | Accept trailing dot file name (Useful when you type and tab completion including dot) |\r\n| `g:nobin_except_files` | Exception patterns of non-binary files |\r\n","install_details":"","5":"","first_name":"Y.","6":"Y.","last_name":"Choi","7":"Choi","releases":[{"0":"5890","vim_version":"7.0","1":"7.0","script_version":"1.1","2":"1.1","version_comment":"+ Add exception option and rules","3":"+ Add exception option and rules","package":"vim-nobin-1.1.tar.gz","4":"vim-nobin-1.1.tar.gz","src_id":"27229","5":"27229","creation_date":"1593878919","6":"1593878919"},{"0":"5890","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"vim-nobin-1.0.tar.gz","4":"vim-nobin-1.0.tar.gz","src_id":"27203","5":"27203","creation_date":"1592177819","6":"1592177819"}]},"5889":{"script_id":"5889","0":"5889","script_name":"vim-nobin","1":"vim-nobin","script_type":"utility","2":"utility","summary":"Plugin to load original source code instead of executable binary.","3":"Plugin to load original source code instead of executable binary.","description":"# nobin.vim\n[![Script manager: vishop](https:\/\/img.shields.io\/badge\/script%20manager-vishop-blueviolet)](https:\/\/github.com\/Xvezda\/vishop)\n\n![Demo](https:\/\/gist.githubusercontent.com\/Xvezda\/6f3773debe7982129d789981b4d9a72e\/raw\/vim-nobin.gif)\n\nI made this plugin because of auto-completion on shell environment always lead me to open a binary, not a source code.\n\n`gcc test.c -o test`\n\nIn this case, there are two files in the same directory. `test.c` and `test`.\n\n`vim t`\n\nNow, if I press tab to edit `test.c` again, `test` will appears.\nI need to press tab again to make `test` to `test.c`\n\nBut most of times, I accidently open `test` binary instead.\nIt's way too frustrating. :(\n\nThis plugin will automatically finds original source code of executable binary, which you opened by mistake. :)\n\n## Installation\n\nUsing [vim-plug](https:\/\/github.com\/junegunn\/vim-plug):\n\n`Plug 'Xvezda\/vim-nobin'`\n\nor\n\n`make install`\n\n\n## Global options\n\n| Flag | Description |\n|-------------------------------|---------------------------------------------------------- |\n| `g:nobin_always_yes` | Automatically select [y]es on select screen |\n| `g:nobin_well_known_files` | Regular expression list for well known binary patterns |\n| `g:nobin_except_files` | Exception patterns of non-binary files |\n## Homepage\n\nhttps:\/\/github.com\/Xvezda\/vim-nobin\n\n\n## Copyright\n\nCopyright (C) 2020 Xvezda\n\nMIT License\n\n","4":"# nobin.vim\n[![Script manager: vishop](https:\/\/img.shields.io\/badge\/script%20manager-vishop-blueviolet)](https:\/\/github.com\/Xvezda\/vishop)\n\n![Demo](https:\/\/gist.githubusercontent.com\/Xvezda\/6f3773debe7982129d789981b4d9a72e\/raw\/vim-nobin.gif)\n\nI made this plugin because of auto-completion on shell environment always lead me to open a binary, not a source code.\n\n`gcc test.c -o test`\n\nIn this case, there are two files in the same directory. `test.c` and `test`.\n\n`vim t`\n\nNow, if I press tab to edit `test.c` again, `test` will appears.\nI need to press tab again to make `test` to `test.c`\n\nBut most of times, I accidently open `test` binary instead.\nIt's way too frustrating. :(\n\nThis plugin will automatically finds original source code of executable binary, which you opened by mistake. :)\n\n## Installation\n\nUsing [vim-plug](https:\/\/github.com\/junegunn\/vim-plug):\n\n`Plug 'Xvezda\/vim-nobin'`\n\nor\n\n`make install`\n\n\n## Global options\n\n| Flag | Description |\n|-------------------------------|---------------------------------------------------------- |\n| `g:nobin_always_yes` | Automatically select [y]es on select screen |\n| `g:nobin_well_known_files` | Regular expression list for well known binary patterns |\n| `g:nobin_except_files` | Exception patterns of non-binary files |\n## Homepage\n\nhttps:\/\/github.com\/Xvezda\/vim-nobin\n\n\n## Copyright\n\nCopyright (C) 2020 Xvezda\n\nMIT License\n\n","install_details":"","5":"","first_name":"Y.","6":"Y.","last_name":"Choi","7":"Choi","releases":[{"0":"5889","vim_version":"7.0","1":"7.0","script_version":"1.2","2":"1.2","version_comment":"+ Remove obsolete option","3":"+ Remove obsolete option","package":"vim-nobin-1.2.tar.gz","4":"vim-nobin-1.2.tar.gz","src_id":"27540","5":"27540","creation_date":"1616377558","6":"1616377558"},{"0":"5889","vim_version":"7.0","1":"7.0","script_version":"1.1","2":"1.1","version_comment":"+ Add exception option and rules","3":"+ Add exception option and rules","package":"vim-nobin-1.1.tar.gz","4":"vim-nobin-1.1.tar.gz","src_id":"27230","5":"27230","creation_date":"1593879277","6":"1593879277"},{"0":"5889","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"vim-nobin-1.0.tar.gz","4":"vim-nobin-1.0.tar.gz","src_id":"27202","5":"27202","creation_date":"1592177485","6":"1592177485"}]},"5888":{"script_id":"5888","0":"5888","script_name":"vim-cpywrite","1":"vim-cpywrite","script_type":"utility","2":"utility","summary":"Generate copyright headers for any open source license","3":"Generate copyright headers for any open source license","description":"Pass a license identifier to the :CPYwrite command and it will insert the\r\nstandard header, if available, at the top of the current buffer.\r\n\r\nWhen g:cpywrite#verbatim_mode is off, licenses with no standard header will\r\nbe acknowledged below your author line. Turn on g:cpywrite#verbatim_mode to\r\nuse the full license text instead.\r\n\r\nWhen g:cpywrite#machine_readable is on, license and copyright are formatted\r\nfor easier parsing by a validation tool like reuse (https:\/\/reuse.readthedocs.io).\r\n\r\nThis plugin learns your name and email by invoking `git`; it falls back to\r\nyour OS user and host names.\r\n\r\n\r\nQuick Reference\r\n----------------------\r\n:CPYwrite [{spdx_short_name}]\r\n\r\nFetches the license identified by `spdx_short_name` (without quotes)\r\n-- uses the current value of `g:cpywrite#default_license` when no argument is\r\ngiven -- supports completion\r\n\r\n\r\n:CPYwriteKeepShebangs\r\n\r\nToggles the state of the g:cpywrite#preserve_shebangs option and prints a\r\ndescription of the current state:\r\n\r\n 0 == \"overwrite\"\r\n 1 == \"preserve existing\"\r\n\r\n\r\n:CPYwriteDefaultLicense [{spdx_short_name}]\r\n\r\nSets g:cpywrite#default_license to the given SPDX license identifier (without\r\nquotes) and prints the updated value. Use for name completion.\r\n\r\nSimply prints g:cpywrite#default_license when called with no argument.\r\n\r\n\r\n:CPYwriteToggleMode\r\n\r\nToggles the state of the g:cpywrite#verbatim_mode option and prints a\r\ndescription of the current state:\r\n\r\n 0 == \"standard header\/brief\"\r\n 1 == \"verbatim\"\r\n\r\n\r\n:CPYwriteToggleStyle\r\n\r\nToggles the state of the g:cpywrite#machine_readable option and prints a\r\ndescription of the current state:\r\n\r\n 0 == \"descriptive\"\r\n 1 == \"machine readable\"\r\n\r\n\r\n:CPYwriteToggleFilename\r\n\r\nToggles the state of the g:cpywrite#hide_filename option and prints a\r\ndescription of the current state:\r\n\r\n 0 == \"showing\"\r\n 1 == \"hidden\"\r\n\r\n\r\n:CPYwriteAllowAnonymous\r\n\r\nToggles the state of the g:cpywrite#no_anonymous option and prints a\r\ndescription of the current state:\r\n\r\n 0 == \"Public Domain only\"\r\n 1 == \"never\" \/\/ meaning, \"always state the copyright holder\"\r\n\r\n\r\n(cpywrite)\r\n\r\nDoes the same as calling :CPYwrite with no argument\r\n\r\n\r\n{Normal}LH\r\n\r\nMaps to (cpywrite)\r\n\r\n\r\nOptions\r\n----------\r\ng:cpywrite#default_license (string; default: 'Apache-2.0')\r\n\r\nSet this to the SPDX identifier of your favourite license. Press after\r\nthe :CPYwriteDefaultLicense or :CPYwrite command for suggestions.\r\n\r\n\r\ng:cpywrite#preserve_shebangs (number; default: 1)\r\n\r\nWhen set to a non-zero value, the license header is inserted after any shebang\r\nline: `#! . . .`, or encoding directive: `# -*- coding: . . . -*-`\r\n\r\nWhen set to 0, shebangs and encoding directives will be overwritten. A template\r\nshebang line is inserted at the top of perl, python, and shell script files.\r\n\r\n\r\ng:cpywrite#verbatim_mode (number; default: 0)\r\n\r\nWhen set to a non-zero value, the full license text will be requested, whether\r\nor not a standard header exists. You should only choose this when the license\r\nis no longer than 3-4 paragraphs (e.g. Unlicense, MIT, BSD 1- 2- 3-Clause, etc.)\r\n\r\nWhen set to 0, only standard headers are requested. Licenses with no standard\r\nheader will be briefly mentioned below your copyright line.\r\n\r\n\r\ng:cpywrite#no_anonymous (number; default: 0)\r\n\r\n~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~\r\nWARNING\r\nthis option has no effect when g:cpywrite#machine_readable is on\r\n~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~\r\n\r\nWhen set to a non-zero value, copyright information is never omitted, even if\r\nthe license implies a Public Domain grant.\r\n\r\nWhen set to 0, a copyright will not appear above Public-Domain-licenses.\r\n\r\n\r\ng:cpywrite#machine_readable (number; default: 0)\r\n\r\n~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~\r\nWARNING\r\nthis option overrides g:cpywrite#verbatim_mode and g:cpywrite#no_anonymous\r\n~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~\r\n\r\nWhen set to a non-zero value, the license and copyright statement are\r\nformatted as tags, for example:\r\n\r\n #\r\n # __main__.py\r\n #\r\n # SPDX-FileCopyrightText: 2020 Jane Doe \r\n #\r\n # SPDX-License-Identifier: GPL-3.0-or-later\r\n #\r\n\r\nIn this mode, copyright information is never omitted, regardless of how\r\ng:cpywrite#no_anonymous has been set, e.g.\r\n\r\n \/**\r\n * main.js\r\n *\r\n * SPDX-FileCopyrightText: 2020 John Doe \r\n *\r\n * SPDX-License-Identifier: Unlicense\r\n *\/\r\n\r\nWhen set to 0, the license format will be a standard header, or full text,\r\ndepending on how g:cpywrite#verbatim_mode is set. A copyright statement\r\nmay also be left out if g:cpywrite#no_anonymous is 0 and the chosen\r\nlicense is a Public Domain license.\r\n\r\n\r\ng:cpywrite#hide_filename (number; default: 0)\r\n\r\nWhen set to a non-zero value, hides the name of the current buffer from the\r\nlicense header in all modes. Otherwise, the buffer's name will appear on the\r\nfirst line.\r\n\r\n\r\ng:cpywrite#java#add_class_doc (number; default: 1)\r\n\r\n~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~\r\nNOTE\r\nif not set by the user, this option will be enabled automatically when 'filetype' is 'java'\r\n~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~\r\n\r\nWhen set to a non-zero value, adds a JavaDoc '@author' tag to the main class\r\ndefinition of the current Java file, if:\r\n\r\n 1. the class already has a doc comment of >= 3 lines; and\r\n 2. at least one line is blank, e.g.\r\n\r\n \/**\r\n *\r\n *\/\r\n public class Main {}\r\n\r\n\r\nTesting Locally\r\n--------------------\r\n * install vader.vim (vimscript #4832) into your runtime path\r\n\r\n * alternatively, run `git clone https:\/\/github.com\/junegunn\/vader.vim.git` and\r\n edit `test\/vimrc` by changing\r\n\r\n set rtp+=vader.vim\r\n\r\n to\r\n\r\n set rtp+=\/path\/to\/cloned\/source\/of\/vader.vim\r\n\r\n * change directories into \/your\/plugin\/path\/vim-cpywrite\r\n\r\n * issue these commands:\r\n\r\n pip install -r test\/requirements.txt\r\n coverage run -m pytest -v && coverage report\r\n vim -ENsu test\/vimrc -c '+Vader! test\/vader\/**' > \/dev\/null\r\n\r\n","4":"Pass a license identifier to the :CPYwrite command and it will insert the\r\nstandard header, if available, at the top of the current buffer.\r\n\r\nWhen g:cpywrite#verbatim_mode is off, licenses with no standard header will\r\nbe acknowledged below your author line. Turn on g:cpywrite#verbatim_mode to\r\nuse the full license text instead.\r\n\r\nWhen g:cpywrite#machine_readable is on, license and copyright are formatted\r\nfor easier parsing by a validation tool like reuse (https:\/\/reuse.readthedocs.io).\r\n\r\nThis plugin learns your name and email by invoking `git`; it falls back to\r\nyour OS user and host names.\r\n\r\n\r\nQuick Reference\r\n----------------------\r\n:CPYwrite [{spdx_short_name}]\r\n\r\nFetches the license identified by `spdx_short_name` (without quotes)\r\n-- uses the current value of `g:cpywrite#default_license` when no argument is\r\ngiven -- supports completion\r\n\r\n\r\n:CPYwriteKeepShebangs\r\n\r\nToggles the state of the g:cpywrite#preserve_shebangs option and prints a\r\ndescription of the current state:\r\n\r\n 0 == \"overwrite\"\r\n 1 == \"preserve existing\"\r\n\r\n\r\n:CPYwriteDefaultLicense [{spdx_short_name}]\r\n\r\nSets g:cpywrite#default_license to the given SPDX license identifier (without\r\nquotes) and prints the updated value. Use for name completion.\r\n\r\nSimply prints g:cpywrite#default_license when called with no argument.\r\n\r\n\r\n:CPYwriteToggleMode\r\n\r\nToggles the state of the g:cpywrite#verbatim_mode option and prints a\r\ndescription of the current state:\r\n\r\n 0 == \"standard header\/brief\"\r\n 1 == \"verbatim\"\r\n\r\n\r\n:CPYwriteToggleStyle\r\n\r\nToggles the state of the g:cpywrite#machine_readable option and prints a\r\ndescription of the current state:\r\n\r\n 0 == \"descriptive\"\r\n 1 == \"machine readable\"\r\n\r\n\r\n:CPYwriteToggleFilename\r\n\r\nToggles the state of the g:cpywrite#hide_filename option and prints a\r\ndescription of the current state:\r\n\r\n 0 == \"showing\"\r\n 1 == \"hidden\"\r\n\r\n\r\n:CPYwriteAllowAnonymous\r\n\r\nToggles the state of the g:cpywrite#no_anonymous option and prints a\r\ndescription of the current state:\r\n\r\n 0 == \"Public Domain only\"\r\n 1 == \"never\" \/\/ meaning, \"always state the copyright holder\"\r\n\r\n\r\n(cpywrite)\r\n\r\nDoes the same as calling :CPYwrite with no argument\r\n\r\n\r\n{Normal}LH\r\n\r\nMaps to (cpywrite)\r\n\r\n\r\nOptions\r\n----------\r\ng:cpywrite#default_license (string; default: 'Apache-2.0')\r\n\r\nSet this to the SPDX identifier of your favourite license. Press after\r\nthe :CPYwriteDefaultLicense or :CPYwrite command for suggestions.\r\n\r\n\r\ng:cpywrite#preserve_shebangs (number; default: 1)\r\n\r\nWhen set to a non-zero value, the license header is inserted after any shebang\r\nline: `#! . . .`, or encoding directive: `# -*- coding: . . . -*-`\r\n\r\nWhen set to 0, shebangs and encoding directives will be overwritten. A template\r\nshebang line is inserted at the top of perl, python, and shell script files.\r\n\r\n\r\ng:cpywrite#verbatim_mode (number; default: 0)\r\n\r\nWhen set to a non-zero value, the full license text will be requested, whether\r\nor not a standard header exists. You should only choose this when the license\r\nis no longer than 3-4 paragraphs (e.g. Unlicense, MIT, BSD 1- 2- 3-Clause, etc.)\r\n\r\nWhen set to 0, only standard headers are requested. Licenses with no standard\r\nheader will be briefly mentioned below your copyright line.\r\n\r\n\r\ng:cpywrite#no_anonymous (number; default: 0)\r\n\r\n~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~\r\nWARNING\r\nthis option has no effect when g:cpywrite#machine_readable is on\r\n~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~\r\n\r\nWhen set to a non-zero value, copyright information is never omitted, even if\r\nthe license implies a Public Domain grant.\r\n\r\nWhen set to 0, a copyright will not appear above Public-Domain-licenses.\r\n\r\n\r\ng:cpywrite#machine_readable (number; default: 0)\r\n\r\n~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~\r\nWARNING\r\nthis option overrides g:cpywrite#verbatim_mode and g:cpywrite#no_anonymous\r\n~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~\r\n\r\nWhen set to a non-zero value, the license and copyright statement are\r\nformatted as tags, for example:\r\n\r\n #\r\n # __main__.py\r\n #\r\n # SPDX-FileCopyrightText: 2020 Jane Doe \r\n #\r\n # SPDX-License-Identifier: GPL-3.0-or-later\r\n #\r\n\r\nIn this mode, copyright information is never omitted, regardless of how\r\ng:cpywrite#no_anonymous has been set, e.g.\r\n\r\n \/**\r\n * main.js\r\n *\r\n * SPDX-FileCopyrightText: 2020 John Doe \r\n *\r\n * SPDX-License-Identifier: Unlicense\r\n *\/\r\n\r\nWhen set to 0, the license format will be a standard header, or full text,\r\ndepending on how g:cpywrite#verbatim_mode is set. A copyright statement\r\nmay also be left out if g:cpywrite#no_anonymous is 0 and the chosen\r\nlicense is a Public Domain license.\r\n\r\n\r\ng:cpywrite#hide_filename (number; default: 0)\r\n\r\nWhen set to a non-zero value, hides the name of the current buffer from the\r\nlicense header in all modes. Otherwise, the buffer's name will appear on the\r\nfirst line.\r\n\r\n\r\ng:cpywrite#java#add_class_doc (number; default: 1)\r\n\r\n~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~\r\nNOTE\r\nif not set by the user, this option will be enabled automatically when 'filetype' is 'java'\r\n~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~\r\n\r\nWhen set to a non-zero value, adds a JavaDoc '@author' tag to the main class\r\ndefinition of the current Java file, if:\r\n\r\n 1. the class already has a doc comment of >= 3 lines; and\r\n 2. at least one line is blank, e.g.\r\n\r\n \/**\r\n *\r\n *\/\r\n public class Main {}\r\n\r\n\r\nTesting Locally\r\n--------------------\r\n * install vader.vim (vimscript #4832) into your runtime path\r\n\r\n * alternatively, run `git clone https:\/\/github.com\/junegunn\/vader.vim.git` and\r\n edit `test\/vimrc` by changing\r\n\r\n set rtp+=vader.vim\r\n\r\n to\r\n\r\n set rtp+=\/path\/to\/cloned\/source\/of\/vader.vim\r\n\r\n * change directories into \/your\/plugin\/path\/vim-cpywrite\r\n\r\n * issue these commands:\r\n\r\n pip install -r test\/requirements.txt\r\n coverage run -m pytest -v && coverage report\r\n vim -ENsu test\/vimrc -c '+Vader! test\/vader\/**' > \/dev\/null\r\n\r\n","install_details":"Make sure your environment has the requirements listed at https:\/\/github.com\/rdipardo\/vim-cpywrite#requirements\r\n\r\n~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~\r\nNOTE\r\npython 3.10 requires neovim 0.6.0 or newer; \r\nall vim versions from 7.4 and up should be compatible\r\n~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~\r\n\r\nFor a detailed installation guide, refer to https:\/\/github.com\/rdipardo\/vim-cpywrite#installation","5":"Make sure your environment has the requirements listed at https:\/\/github.com\/rdipardo\/vim-cpywrite#requirements\r\n\r\n~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~\r\nNOTE\r\npython 3.10 requires neovim 0.6.0 or newer; \r\nall vim versions from 7.4 and up should be compatible\r\n~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~\r\n\r\nFor a detailed installation guide, refer to https:\/\/github.com\/rdipardo\/vim-cpywrite#installation","first_name":"Robert","6":"Robert","last_name":"Di Pardo","7":"Di Pardo","releases":[{"0":"5888","vim_version":"7.4","1":"7.4","script_version":"0.8.1","2":"0.8.1","version_comment":"Bugfix for generated author bylines; new licenses; python 2.7 is no longer supported","3":"Bugfix for generated author bylines; new licenses; python 2.7 is no longer supported","package":"vim-cpywrite-0.8.1.tar.gz","4":"vim-cpywrite-0.8.1.tar.gz","src_id":"28521","5":"28521","creation_date":"1690772810","6":"1690772810"},{"0":"5888","vim_version":"7.4","1":"7.4","script_version":"0.7","2":"0.7","version_comment":"Fix missing copyright in GPL v1 and 2 headers; use the `&syntax` property to improve detection of dotfiles, makefiles, and scripts; add support for reStructuredText, YAML, and more\r\n","3":"Fix missing copyright in GPL v1 and 2 headers; use the `&syntax` property to improve detection of dotfiles, makefiles, and scripts; add support for reStructuredText, YAML, and more\r\n","package":"vim-cpywrite-0.7.0.tar.gz","4":"vim-cpywrite-0.7.0.tar.gz","src_id":"27902","5":"27902","creation_date":"1641899794","6":"1641899794"},{"0":"5888","vim_version":"7.4","1":"7.4","script_version":"0.6","2":"0.6","version_comment":"New option to format license and copyright as machine readable tags (REUSE compatible), support for DOS Batch files","3":"New option to format license and copyright as machine readable tags (REUSE compatible), support for DOS Batch files","package":"vim-cpywrite-0.6.0.tar.gz","4":"vim-cpywrite-0.6.0.tar.gz","src_id":"27761","5":"27761","creation_date":"1633150878","6":"1633150878"},{"0":"5888","vim_version":"7.4","1":"7.4","script_version":"0.5.0","2":"0.5.0","version_comment":"Support three new file types, insert header after [X|HT]ML metadata","3":"Support three new file types, insert header after [X|HT]ML metadata","package":"vim-cpywrite-0.5.0.tar.gz","4":"vim-cpywrite-0.5.0.tar.gz","src_id":"27644","5":"27644","creation_date":"1625350993","6":"1625350993"},{"0":"5888","vim_version":"7.4","1":"7.4","script_version":"0.4.0","2":"0.4.0","version_comment":"- include recent additions to the SPDX License List\r\n- drop the deprecated FreeBSD variant of the BSD 2-Clause License\r\n- change default license","3":"- include recent additions to the SPDX License List\r\n- drop the deprecated FreeBSD variant of the BSD 2-Clause License\r\n- change default license","package":"vim-cpywrite-0.4.0.tar.gz","4":"vim-cpywrite-0.4.0.tar.gz","src_id":"27611","5":"27611","creation_date":"1621933094","6":"1621933094"},{"0":"5888","vim_version":"7.4","1":"7.4","script_version":"0.3.4","2":"0.3.4","version_comment":"Handle missing emails, fix regex bugs, reduce plugin size","3":"Handle missing emails, fix regex bugs, reduce plugin size","package":"vim-cpywrite-0.3.4.tar.gz","4":"vim-cpywrite-0.3.4.tar.gz","src_id":"27560","5":"27560","creation_date":"1617540499","6":"1617540499"},{"0":"5888","vim_version":"7.4","1":"7.4","script_version":"0.3.0","2":"0.3.0","version_comment":"Provide option to hide buffer name in license header, support for more file types","3":"Provide option to hide buffer name in license header, support for more file types","package":"vim-cpywrite-0.3.0.tar.gz","4":"vim-cpywrite-0.3.0.tar.gz","src_id":"27329","5":"27329","creation_date":"1602504778","6":"1602504778"},{"0":"5888","vim_version":"7.4","1":"7.4","script_version":"0.2.1","2":"0.2.1","version_comment":"Support more file types, detect public domain licenses","3":"Support more file types, detect public domain licenses","package":"vim-cpywrite-0.2.1.tar.gz","4":"vim-cpywrite-0.2.1.tar.gz","src_id":"27287","5":"27287","creation_date":"1597647348","6":"1597647348"},{"0":"5888","vim_version":"7.4","1":"7.4","script_version":"0.1.0","2":"0.1.0","version_comment":"Initial upload","3":"Initial upload","package":"vim-cpywrite.tar.gz","4":"vim-cpywrite.tar.gz","src_id":"27201","5":"27201","creation_date":"1592026460","6":"1592026460"}]},"5887":{"script_id":"5887","0":"5887","script_name":"hi.vim","1":"hi.vim","script_type":"utility","2":"utility","summary":"Syntax highlighting and text filter tool, enhanced log analyzer.","3":"Syntax highlighting and text filter tool, enhanced log analyzer.","description":"Log analisys.\r\nText highlighting.\r\n\r\nThis is a complex tool for log analysis. Take into account this is a work in progress project.\r\n\r\nAlso: https:\/\/github.com\/javipv\/hi.vim\r\n\r\nThis script allows you to highlight the words, sentences or regular expressions you need, on up to 82 colors, and 410 color configurations, when including foreground colors, background colors, bold and underline configurations.\r\n\r\nIf you LIKED THE PLUGIN, or you have some improvements, or you dislike it and found it complicated, no matter what, please drop a few lines to my e-mail and TELL ME! (javierpuigdevall@gmail.com)\r\n\r\n\r\n----------------------------------------------------------------------------------------------------------------------------------\r\nUSAGE:\r\n----------------------------------------------------------------------------------------------------------------------------------\r\n\r\n1) HIGHLIGHT COLORS:\r\n\r\nCommands Hicol (highlight colors) and Hiid (highlight IDs) display the available colors.\r\nExamples:\r\n- Show basic color IDs: :Hiid\r\n- Show all color IDs: :Hiid all\r\n- Show red color IDs: :Hicol r\r\n- Show red color IDs including bold, underline and background colors: :Hicol r all\r\n- Show red and orange color IDs: :Hiid r o\r\n- Show red and orange color IDs including bold, underline and background colors: :Hicol r o all\r\n\r\nThe N color ID is a special ID with no color highlight, its use is to mark patterns to be included later on the filter window without highlighting them.\r\n\r\n\r\n2) TEXT EXAMPLE:\r\n\r\nThis is a little complex to explain so, let's write a text example to try the commands.\r\nWrite the following lines to a new buffer:\r\n\r\nExample pattern1\r\nSome more text with no highlights\r\nExample pattern2\r\nEXAMPLE PATTERN3\r\nExample pattern4\r\nSome more text with no highlights\r\nExample pattern5\r\nExample pattern6\r\nSome more text with no highlights\r\nExample pattern7\r\nExample pattern8\r\nSome more text with no highlights\r\nSome more text with no highlights\r\nExample pattern9\r\nThis is my pattern_10 example number 10\r\nExample pattern_11 add to filter without highlighting\r\nSome more text with no highlights\r\nSome more text with no highlights\r\nExample pattern_12\r\nExample pattern_13\r\nExample pattern_14\r\n\r\n\r\n3) HIGHLIGHT COMMANDS:\r\n\r\nTo perform a color highlight, use command :Hic pattern colorID.\r\n\r\nThrere are some modifiers that can be appended to color ID in order to obtain a different color result:\r\n- Append * to to color ID to highlight all line.\r\n- Append @ to to color ID to highlight the background instead of foreground (default).\r\n- Append ! to to color ID to highlight in bold characters.\r\n- Append _ to to color ID to highlight underlined.\r\n- Append 0 to to color ID to highlight on top of a previous highlight.\r\n\r\nExamples:\r\nExamples:\r\n- Highlight word pattern1 in red color :Hic pattern1 r\r\n- Highlight word pattern2 in green color :Hic pattern2 g\r\n- Highlight word pattern3, case sensitive, in green2 color :Hic \\CPattern3 g2\r\n- Highlight word pattern4, no case sensitive, in green5 color :Hic \\cpattern4 g5\r\n- Highlight word pattern5 in yellow and bold :Hic pattern5 y!\r\n- Highlight word pattern6 in magenta underlined :Hic pattern6 m_\r\n- Highlight word pattern7 in violet background :Hic pattern7 v@\r\n- Highlight word pattern8 in violet background and bold text :Hic pattern8 v@!\r\n- Highlight the whole line containing word pattern9 background in red color :Hic pattern9 r@*\r\n- Highlight the regular expression my.*pattern_10 in green4 color :Hic my.*pattern_10 g4\r\n- Highlight in 'none' color :Hic pattern_11 n\r\n- Highlight word pattern_12 in blue3 and bold text :Hic pattern_12 b3!\r\n- Highlight word pattern_13 in cyan and underline text :Hic pattern_13 c_\r\n- Highlight the whole line containing pattern_14 in cyan and underline text :Hic pattern_14 c_*\r\n- Highlight the character 8 on top of the already highlighted pattern6 in cyan background :Hic 6 c0\r\n- Highlight the character 8 on top of the already highlighted pattern8 in cyan background :Hic 8 c@0\r\n\r\nOmit the color ID to choose the color from a menu showing the basic colors :Hic patternX\r\n\r\nUse ':Hish' to display the current color highlighting configuration.\r\n\r\nUse hw to highlight a word.\r\nUse hW to highlight the whole word.\r\n\r\n\r\n4) SEARCH COMMAND:\r\n\r\nUse command :Hics colorId, to search all patterns highlighted with the selected color IDs.\r\nExamples:\r\n- Search all red highlighted patterns :Hics r\r\n- Search all red and yellow highlighted patterns :Hics r y\r\n- Search all red foreground and red background highlighted patterns :Hics r@ r\r\n\r\n\r\n5) CONFIGURATION SAVE COMMANDS:\r\n\r\nConfigurations can be saved on file to use them later again.\r\nThere are three basic configuration files:\r\ncurrenFile_vim_hi.cfg: configurations only visible when vim is editing this file (currentFile).\r\ncurrenDir\/.vim_hi.cfg: configurations only visible when vim is open on this directory.\r\n~\/.vim_hi.cfg: general configurations, always available.\r\nExamples:\r\n- Save current highlight configuration with name :Hisv MyConfig (You will be asked the file where the configuration will be saved)\r\n- Add a new configuration file :Hil MyConfigFile\r\n- Edit all configuration files availble :Hicfg\r\n\r\n\r\n6) CONFIGURATION FORMAT:\r\n\r\nThe configuration file is saved with ini file format.\r\n\r\nThis are all the allowed field names:\r\n- [Name]: this is the configuration name.\r\n- Mark: apply a highlight.\r\n- Filt: open a filter window with the selected patterns or colors.\r\n- Conf: apply a saved configuration type.\r\n- Find: search a pattern or a highlight color\r\n- Goto: change focus to main (init) window, filter window (parent\/son) or last filter window.\r\n\r\nConfiguration format example:\r\n\r\n[ConfigName]\r\nMark = ColorID|Flags|Patterns\r\nConf = clean\r\n# this is a commented line\r\nConf = configName\r\nConf = configName1 configName2 configNameN\r\nConf = edit\r\nFilt = close\r\nFilt = colorID\r\nFilt = colorID1 colorID2 colorIDN\r\nFind = colorID\r\nFind = colorID1 colorID2 colorIDN\r\nFind = pattern colorID\r\nGoto = init\r\nGoto = son\r\nGoto = parent\r\nGoto = last\r\n\r\n\r\n7) CONFIGURATION LOAD COMMANDS:\r\n\r\nConfigurations can be loaded with command :Hit (highlight types).\r\nExamples:\r\n- Show all available configurations :Hit\r\n- Load the first configuration :Hit 1\r\n- Load a configuration with name MyConfig :Hit MyConfig\r\n- Remove any configuration, clean all highlighting :Hit 0\r\n\r\nWhen launching Hit command you should see a menu like this:\r\n\r\n 0) Clear all\r\n 1) MyConfig\r\nSelect type:\r\n\r\n\r\n\r\n8) FILTER WINDOW:\r\n\r\nFilter tool, allows to open a separated split containing only the selected highlights with command Hif (highlight filter).\r\nUse command Hif color\/pattern.\r\nExamples:\r\n- Open a filter window displaying all lines with highlights :Hif\r\n- Close previous filter and open a filter window displaying all lines with red highlights :close | Hif r\r\n- Close previous filter and open a filter window displaying all lines with red and green highlights :close | Hif r g2\r\n- Close previous filter and open a filter window displaying all lines with green and green1 highlights :close | Hif g2 g5\r\n- Close previous filter and open a filter window displaying all lines with background green and red highlights :close | Hif v@ r@\r\n- Close previous filter and open a filter window displaying all lines with word example :close | Hif example\r\n- Close previous filter and open a filter window displaying all lines with word example and any red highlighted pattern :close | Hif This r\r\n\r\nWhen launching this last command you'll see a new split showing:\r\n\r\n\u00e2\u0094\u008f\u00e2\u0094\u0081\u00e2\u0094\u0081\u00e2\u0094\u0081\u00e2\u0094\u0081\u00e2\u0094\u0081\u00e2\u0094\u0081\u00e2\u0094\u0081\u00e2\u0094\u0081\u00e2\u0094\u0081\u00e2\u0094\u0081\u00e2\u0094\u0081\u00e2\u0094\u0081\u00e2\u0094\u0081\u00e2\u0094\u0081\u00e2\u0094\u0081\u00e2\u0094\u0081\u00e2\u0094\u0081\u00e2\u0094\u0081\u00e2\u0094\u0081\u00e2\u0094\u0081\u00e2\u0094\u0081\u00e2\u0094\u0081\u00e2\u0094\u0081\u00e2\u0094\u0081\u00e2\u0094\u0081\u00e2\u0094\u0081\u00e2\u0094\u0081\u00e2\u0094\u0081\u00e2\u0094\u0081\u00e2\u0094\u0081\u00e2\u0094\u0081\u00e2\u0094\u0081\u00e2\u0094\u0081\u00e2\u0094\u0081\u00e2\u0094\u0081\u00e2\u0094\u0081\u00e2\u0094\u0081\u00e2\u0094\u0081\u00e2\u0094\u0081\u00e2\u0094\u0081\u00e2\u0094\u0081\u00e2\u0094\u0081\u00e2\u0094\u0081\u00e2\u0094\u0081\u00e2\u0094\u0081\u00e2\u0094\u0081\u00e2\u0094\u0081\u00e2\u0094\u0093\r\n\u00e2\u0094\u0083 HI PLUGIN. FILTER WINDOW \u00e2\u0094\u0083\r\n\u00e2\u0094\u0083 Filter patterns: \"pattern1|This\" \u00e2\u0094\u0083\r\n\u00e2\u0094\u0097\u00e2\u0094\u0081\u00e2\u0094\u0081\u00e2\u0094\u0081\u00e2\u0094\u0081\u00e2\u0094\u0081\u00e2\u0094\u0081\u00e2\u0094\u0081\u00e2\u0094\u0081\u00e2\u0094\u0081\u00e2\u0094\u0081\u00e2\u0094\u0081\u00e2\u0094\u0081\u00e2\u0094\u0081\u00e2\u0094\u0081\u00e2\u0094\u0081\u00e2\u0094\u0081\u00e2\u0094\u0081\u00e2\u0094\u0081\u00e2\u0094\u0081\u00e2\u0094\u0081\u00e2\u0094\u0081\u00e2\u0094\u0081\u00e2\u0094\u0081\u00e2\u0094\u0081\u00e2\u0094\u0081\u00e2\u0094\u0081\u00e2\u0094\u0081\u00e2\u0094\u0081\u00e2\u0094\u0081\u00e2\u0094\u0081\u00e2\u0094\u0081\u00e2\u0094\u0081\u00e2\u0094\u0081\u00e2\u0094\u0081\u00e2\u0094\u0081\u00e2\u0094\u0081\u00e2\u0094\u0081\u00e2\u0094\u0081\u00e2\u0094\u0081\u00e2\u0094\u0081\u00e2\u0094\u0081\u00e2\u0094\u0081\u00e2\u0094\u0081\u00e2\u0094\u0081\u00e2\u0094\u0081\u00e2\u0094\u0081\u00e2\u0094\u0081\u00e2\u0094\u009b\r\nExample pattern1\r\nThis is my pattern_10 example number 10\r\n\r\n\r\nOnce the filter window's opened, use ENTER key to synchronize the window position between main and filter windows (you can use :Hip command too).\r\n\r\nOnce the filter window's opened, use Alt+ENTER key to synchronize the window position between main and filter windows and switch the focus between main and filter splits (you can use :Hips command too).\r\n\r\n\r\n9) EDITOR window:\r\n\r\nThe highlight configuration editor window allows a more convenient edit of the highlights and filters to apply. Open it with Hie (highlight edit).\r\nUse :Hie to open the editor window (he too) on vertical split on the right side.\r\n\r\nIf you followed the previous example you'll see:\r\n\r\n\u00e2\u0094\u008c\u00e2\u0094\u0080\u00e2\u0094\u0080\u00e2\u0094\u0080\u00e2\u0094\u0080\u00e2\u0094\u0080\u00e2\u0094\u0080\u00e2\u0094\u0080\u00e2\u0094\u0080\u00e2\u0094\u0080\u00e2\u0094\u0080\u00e2\u0094\u0080\u00e2\u0094\u0080\u00e2\u0094\u0080\u00e2\u0094\u0080\u00e2\u0094\u0080\u00e2\u0094\u0080\u00e2\u0094\u0080\u00e2\u0094\u0080\u00e2\u0094\u0080\u00e2\u0094\u0080\u00e2\u0094\u0080\u00e2\u0094\u0080\u00e2\u0094\u0080\u00e2\u0094\u0080\u00e2\u0094\u0080\u00e2\u0094\u0080\u00e2\u0094\u0080\u00e2\u0094\u0080\u00e2\u0094\u0080\u00e2\u0094\u0080\u00e2\u0094\u0080\u00e2\u0094\u0080\u00e2\u0094\u0080\u00e2\u0094\u0080\u00e2\u0094\u0080\u00e2\u0094\u0080\u00e2\u0094\u0080\u00e2\u0094\u0080\u00e2\u0094\u0080\u00e2\u0094\u0090\r\n\u00e2\u0094\u0082 HIGHLIGHT CONFIG: \u00e2\u0094\u0082\r\n\u00e2\u0094\u0094\u00e2\u0094\u0080\u00e2\u0094\u0080\u00e2\u0094\u0080\u00e2\u0094\u0080\u00e2\u0094\u0080\u00e2\u0094\u0080\u00e2\u0094\u0080\u00e2\u0094\u0080\u00e2\u0094\u0080\u00e2\u0094\u0080\u00e2\u0094\u0080\u00e2\u0094\u0080\u00e2\u0094\u0080\u00e2\u0094\u0080\u00e2\u0094\u0080\u00e2\u0094\u0080\u00e2\u0094\u0080\u00e2\u0094\u0080\u00e2\u0094\u0080\u00e2\u0094\u0080\u00e2\u0094\u0080\u00e2\u0094\u0080\u00e2\u0094\u0080\u00e2\u0094\u0080\u00e2\u0094\u0080\u00e2\u0094\u0080\u00e2\u0094\u0080\u00e2\u0094\u0080\u00e2\u0094\u0080\u00e2\u0094\u0080\u00e2\u0094\u0080\u00e2\u0094\u0080\u00e2\u0094\u0080\u00e2\u0094\u0080\u00e2\u0094\u0080\u00e2\u0094\u0080\u00e2\u0094\u0080\u00e2\u0094\u0080\u00e2\u0094\u0080\u00e2\u0094\u0098\r\nMark = r | C |pattern1\r\nMark = g | C |pattern2\r\nMark = g2 | C |PATTERN3\r\nMark = g5 | c |Pattern4\r\nMark = y! | C |pattern5\r\nMark = m_ | C |pattern6\r\nMark = v@ | C |pattern7\r\nMark = v | Cl |pattern8\r\nMark = r@ | Cl |pattern9\r\nMark = g4 | C |my.*pattern_10\r\nMark = n | C |pattern_11\r\nMark = b3! | C |pattern_12\r\nMark = c3_ | C |pattern_13\r\nMark = c3_ | Cl |pattern_14\r\nMark = c | CT |6\r\nMark = c@ | CT |8\r\n\r\nEdit the highlight configuration paragraph and replace it with this self explanatory one:\r\n\r\n\u00e2\u0094\u008c\u00e2\u0094\u0080\u00e2\u0094\u0080\u00e2\u0094\u0080\u00e2\u0094\u0080\u00e2\u0094\u0080\u00e2\u0094\u0080\u00e2\u0094\u0080\u00e2\u0094\u0080\u00e2\u0094\u0080\u00e2\u0094\u0080\u00e2\u0094\u0080\u00e2\u0094\u0080\u00e2\u0094\u0080\u00e2\u0094\u0080\u00e2\u0094\u0080\u00e2\u0094\u0080\u00e2\u0094\u0080\u00e2\u0094\u0080\u00e2\u0094\u0080\u00e2\u0094\u0080\u00e2\u0094\u0080\u00e2\u0094\u0080\u00e2\u0094\u0080\u00e2\u0094\u0080\u00e2\u0094\u0080\u00e2\u0094\u0080\u00e2\u0094\u0080\u00e2\u0094\u0080\u00e2\u0094\u0080\u00e2\u0094\u0080\u00e2\u0094\u0080\u00e2\u0094\u0080\u00e2\u0094\u0080\u00e2\u0094\u0080\u00e2\u0094\u0080\u00e2\u0094\u0080\u00e2\u0094\u0080\u00e2\u0094\u0080\u00e2\u0094\u0080\u00e2\u0094\u0090\r\n\u00e2\u0094\u0082 HIGHLIGHT CONFIG: \u00e2\u0094\u0082\r\n\u00e2\u0094\u0094\u00e2\u0094\u0080\u00e2\u0094\u0080\u00e2\u0094\u0080\u00e2\u0094\u0080\u00e2\u0094\u0080\u00e2\u0094\u0080\u00e2\u0094\u0080\u00e2\u0094\u0080\u00e2\u0094\u0080\u00e2\u0094\u0080\u00e2\u0094\u0080\u00e2\u0094\u0080\u00e2\u0094\u0080\u00e2\u0094\u0080\u00e2\u0094\u0080\u00e2\u0094\u0080\u00e2\u0094\u0080\u00e2\u0094\u0080\u00e2\u0094\u0080\u00e2\u0094\u0080\u00e2\u0094\u0080\u00e2\u0094\u0080\u00e2\u0094\u0080\u00e2\u0094\u0080\u00e2\u0094\u0080\u00e2\u0094\u0080\u00e2\u0094\u0080\u00e2\u0094\u0080\u00e2\u0094\u0080\u00e2\u0094\u0080\u00e2\u0094\u0080\u00e2\u0094\u0080\u00e2\u0094\u0080\u00e2\u0094\u0080\u00e2\u0094\u0080\u00e2\u0094\u0080\u00e2\u0094\u0080\u00e2\u0094\u0080\u00e2\u0094\u0080\u00e2\u0094\u0098\r\n#------------------------------------------\r\n# Clean previous highlights and filters\r\nConf = clear\r\nFilt = close\r\n#------------------------------------------\r\n# Highlight commands:\r\nMark = r | C |pattern1\r\nMark = g | C |pattern2\r\nMark = g2 | C |PATTERN3\r\nMark = g5 | c |Pattern4\r\nMark = y! | C |pattern5\r\nMark = m_ | C |pattern6\r\nMark = v@ | C |pattern7\r\nMark = v | Cl |pattern8\r\nMark = r@ | Cl |pattern9\r\nMark = g4 | C |my.*pattern_10\r\nMark = n | C |pattern_11\r\nMark = b3! | C |pattern_12\r\nMark = c3_ | C |pattern_13\r\nMark = c3_ | Cl |pattern_14\r\nMark = c | CT |6\r\nMark = c@ | CT |8\r\n#------------------------------------------\r\n# Filter commands:\r\nFilt = all\r\n#Filt = r g4 m r@\r\n#------------------------------------------\r\n# Search commands:\r\nFind g4\r\n\r\nAttention: the firs blank line will end the configuration parser on the editor window.\r\nA blank line is mandatory to at the configuration end to stop config parser.\r\n\r\nWhen changing to any other split the editor window will stay minimized, if you change the focus to the editor split again it will expand to its original size.\r\n\r\nAdd # character at the beginning of line to comment any configuration command.\r\n\r\nUse ENTER key to apply the configuration once finished editing\r\n\r\nUse command :Hiy to yank this configuration to the default buffer and :Hicfg to open the configuration files and paste the configuration on the file you want.\r\n\r\n\r\n\r\n10) AUTOLOAD CONFIG LINE (NEW Version 2.0.2)\r\n\r\nAutoload a config highlight type defined on firs\/last five lines of the file.\r\n\r\nThe configuration line will be checked and applied, if found, on file's open or reload.\r\n\r\nAtuo configuration line examples:\r\n\r\nExample 1: load highlight type MY_CONFIG (must be present on the default configuration files: ~\/.vim_hi.cfg or .\/.vim_hi.cfg)\r\nvim_hi:cfg=MY_CONFIG\r\n\r\nExample 2: load configuration file MY_CONFIG_FILE and then apply the highlight type MY_CONFIG.\r\nvim_hi:cfg=MY_CONFIG::cfgfile=MY_CONFIG_FILE\r\n\r\nExample 3 and 4: same as example 2\r\n# vim_hi:cfg=MY_CONFIG::cfgfile=MY_CONFIG_FILE\r\n\/\/ vim_hi:cfg=MY_CONFIG::cfgfile=MY_CONFIG_FILE\r\n\r\n\r\nIf you want to perform a highlight config auto load whenever a .log file is opened, add to your .vimrc:\r\n\r\naugroup HiAutoConfig\r\n au BufRead *.log call hi#autoConfig#ApplyConfig(\"MyLogConfig\", \"MyConfigFile.cfg\")\r\n augroup END\r\n\r\nLast version (2.0.7) allow to have both configuration and autoload line on the file you want to highlitght by defining cfgFile as %.\r\nThe configuration selected (ErrorHighlightConfig) will be searched on the first and last 150 lines of the current file.\r\ne.g:\r\n[ErrorHighlightConfig]\r\nMark = r | CT | Error:\r\nMark = r | CT | Failure:\r\nvim_hi:cfg=ErrorHighlightConfig::cfgFile=% \r\n\r\n\r\n\r\n\r\n11) HIGHLIGHT GROUPS (NEW Version 2.0.2)\r\n\r\nNew tag '??' allows to filter several configurations at a time.\r\n\r\nExample 1: filter all background highlighted patterns.\r\n:Hif @??\r\n\r\nExample 2: filter all underlined patterns.\r\n:Hif _??\r\n\r\nExample 3: filter all bold highlighted patterns.\r\n:Hif !??\r\n\r\nExample 4: filter all red highlighted patterns.\r\n:Hif r*??\r\n\r\nExample 5: filter all red backgraound highlighted patterns.\r\n:Hif r*@??\r\n\r\n\r\n12) HELP menu:\r\n\r\nThere is a small help you can display using command :Hih.\r\nThis will show you the previous (basic) commands and some more.\r\n\r\n","4":"Log analisys.\r\nText highlighting.\r\n\r\nThis is a complex tool for log analysis. Take into account this is a work in progress project.\r\n\r\nAlso: https:\/\/github.com\/javipv\/hi.vim\r\n\r\nThis script allows you to highlight the words, sentences or regular expressions you need, on up to 82 colors, and 410 color configurations, when including foreground colors, background colors, bold and underline configurations.\r\n\r\nIf you LIKED THE PLUGIN, or you have some improvements, or you dislike it and found it complicated, no matter what, please drop a few lines to my e-mail and TELL ME! (javierpuigdevall@gmail.com)\r\n\r\n\r\n----------------------------------------------------------------------------------------------------------------------------------\r\nUSAGE:\r\n----------------------------------------------------------------------------------------------------------------------------------\r\n\r\n1) HIGHLIGHT COLORS:\r\n\r\nCommands Hicol (highlight colors) and Hiid (highlight IDs) display the available colors.\r\nExamples:\r\n- Show basic color IDs: :Hiid\r\n- Show all color IDs: :Hiid all\r\n- Show red color IDs: :Hicol r\r\n- Show red color IDs including bold, underline and background colors: :Hicol r all\r\n- Show red and orange color IDs: :Hiid r o\r\n- Show red and orange color IDs including bold, underline and background colors: :Hicol r o all\r\n\r\nThe N color ID is a special ID with no color highlight, its use is to mark patterns to be included later on the filter window without highlighting them.\r\n\r\n\r\n2) TEXT EXAMPLE:\r\n\r\nThis is a little complex to explain so, let's write a text example to try the commands.\r\nWrite the following lines to a new buffer:\r\n\r\nExample pattern1\r\nSome more text with no highlights\r\nExample pattern2\r\nEXAMPLE PATTERN3\r\nExample pattern4\r\nSome more text with no highlights\r\nExample pattern5\r\nExample pattern6\r\nSome more text with no highlights\r\nExample pattern7\r\nExample pattern8\r\nSome more text with no highlights\r\nSome more text with no highlights\r\nExample pattern9\r\nThis is my pattern_10 example number 10\r\nExample pattern_11 add to filter without highlighting\r\nSome more text with no highlights\r\nSome more text with no highlights\r\nExample pattern_12\r\nExample pattern_13\r\nExample pattern_14\r\n\r\n\r\n3) HIGHLIGHT COMMANDS:\r\n\r\nTo perform a color highlight, use command :Hic pattern colorID.\r\n\r\nThrere are some modifiers that can be appended to color ID in order to obtain a different color result:\r\n- Append * to to color ID to highlight all line.\r\n- Append @ to to color ID to highlight the background instead of foreground (default).\r\n- Append ! to to color ID to highlight in bold characters.\r\n- Append _ to to color ID to highlight underlined.\r\n- Append 0 to to color ID to highlight on top of a previous highlight.\r\n\r\nExamples:\r\nExamples:\r\n- Highlight word pattern1 in red color :Hic pattern1 r\r\n- Highlight word pattern2 in green color :Hic pattern2 g\r\n- Highlight word pattern3, case sensitive, in green2 color :Hic \\CPattern3 g2\r\n- Highlight word pattern4, no case sensitive, in green5 color :Hic \\cpattern4 g5\r\n- Highlight word pattern5 in yellow and bold :Hic pattern5 y!\r\n- Highlight word pattern6 in magenta underlined :Hic pattern6 m_\r\n- Highlight word pattern7 in violet background :Hic pattern7 v@\r\n- Highlight word pattern8 in violet background and bold text :Hic pattern8 v@!\r\n- Highlight the whole line containing word pattern9 background in red color :Hic pattern9 r@*\r\n- Highlight the regular expression my.*pattern_10 in green4 color :Hic my.*pattern_10 g4\r\n- Highlight in 'none' color :Hic pattern_11 n\r\n- Highlight word pattern_12 in blue3 and bold text :Hic pattern_12 b3!\r\n- Highlight word pattern_13 in cyan and underline text :Hic pattern_13 c_\r\n- Highlight the whole line containing pattern_14 in cyan and underline text :Hic pattern_14 c_*\r\n- Highlight the character 8 on top of the already highlighted pattern6 in cyan background :Hic 6 c0\r\n- Highlight the character 8 on top of the already highlighted pattern8 in cyan background :Hic 8 c@0\r\n\r\nOmit the color ID to choose the color from a menu showing the basic colors :Hic patternX\r\n\r\nUse ':Hish' to display the current color highlighting configuration.\r\n\r\nUse hw to highlight a word.\r\nUse hW to highlight the whole word.\r\n\r\n\r\n4) SEARCH COMMAND:\r\n\r\nUse command :Hics colorId, to search all patterns highlighted with the selected color IDs.\r\nExamples:\r\n- Search all red highlighted patterns :Hics r\r\n- Search all red and yellow highlighted patterns :Hics r y\r\n- Search all red foreground and red background highlighted patterns :Hics r@ r\r\n\r\n\r\n5) CONFIGURATION SAVE COMMANDS:\r\n\r\nConfigurations can be saved on file to use them later again.\r\nThere are three basic configuration files:\r\ncurrenFile_vim_hi.cfg: configurations only visible when vim is editing this file (currentFile).\r\ncurrenDir\/.vim_hi.cfg: configurations only visible when vim is open on this directory.\r\n~\/.vim_hi.cfg: general configurations, always available.\r\nExamples:\r\n- Save current highlight configuration with name :Hisv MyConfig (You will be asked the file where the configuration will be saved)\r\n- Add a new configuration file :Hil MyConfigFile\r\n- Edit all configuration files availble :Hicfg\r\n\r\n\r\n6) CONFIGURATION FORMAT:\r\n\r\nThe configuration file is saved with ini file format.\r\n\r\nThis are all the allowed field names:\r\n- [Name]: this is the configuration name.\r\n- Mark: apply a highlight.\r\n- Filt: open a filter window with the selected patterns or colors.\r\n- Conf: apply a saved configuration type.\r\n- Find: search a pattern or a highlight color\r\n- Goto: change focus to main (init) window, filter window (parent\/son) or last filter window.\r\n\r\nConfiguration format example:\r\n\r\n[ConfigName]\r\nMark = ColorID|Flags|Patterns\r\nConf = clean\r\n# this is a commented line\r\nConf = configName\r\nConf = configName1 configName2 configNameN\r\nConf = edit\r\nFilt = close\r\nFilt = colorID\r\nFilt = colorID1 colorID2 colorIDN\r\nFind = colorID\r\nFind = colorID1 colorID2 colorIDN\r\nFind = pattern colorID\r\nGoto = init\r\nGoto = son\r\nGoto = parent\r\nGoto = last\r\n\r\n\r\n7) CONFIGURATION LOAD COMMANDS:\r\n\r\nConfigurations can be loaded with command :Hit (highlight types).\r\nExamples:\r\n- Show all available configurations :Hit\r\n- Load the first configuration :Hit 1\r\n- Load a configuration with name MyConfig :Hit MyConfig\r\n- Remove any configuration, clean all highlighting :Hit 0\r\n\r\nWhen launching Hit command you should see a menu like this:\r\n\r\n 0) Clear all\r\n 1) MyConfig\r\nSelect type:\r\n\r\n\r\n\r\n8) FILTER WINDOW:\r\n\r\nFilter tool, allows to open a separated split containing only the selected highlights with command Hif (highlight filter).\r\nUse command Hif color\/pattern.\r\nExamples:\r\n- Open a filter window displaying all lines with highlights :Hif\r\n- Close previous filter and open a filter window displaying all lines with red highlights :close | Hif r\r\n- Close previous filter and open a filter window displaying all lines with red and green highlights :close | Hif r g2\r\n- Close previous filter and open a filter window displaying all lines with green and green1 highlights :close | Hif g2 g5\r\n- Close previous filter and open a filter window displaying all lines with background green and red highlights :close | Hif v@ r@\r\n- Close previous filter and open a filter window displaying all lines with word example :close | Hif example\r\n- Close previous filter and open a filter window displaying all lines with word example and any red highlighted pattern :close | Hif This r\r\n\r\nWhen launching this last command you'll see a new split showing:\r\n\r\n\u00e2\u0094\u008f\u00e2\u0094\u0081\u00e2\u0094\u0081\u00e2\u0094\u0081\u00e2\u0094\u0081\u00e2\u0094\u0081\u00e2\u0094\u0081\u00e2\u0094\u0081\u00e2\u0094\u0081\u00e2\u0094\u0081\u00e2\u0094\u0081\u00e2\u0094\u0081\u00e2\u0094\u0081\u00e2\u0094\u0081\u00e2\u0094\u0081\u00e2\u0094\u0081\u00e2\u0094\u0081\u00e2\u0094\u0081\u00e2\u0094\u0081\u00e2\u0094\u0081\u00e2\u0094\u0081\u00e2\u0094\u0081\u00e2\u0094\u0081\u00e2\u0094\u0081\u00e2\u0094\u0081\u00e2\u0094\u0081\u00e2\u0094\u0081\u00e2\u0094\u0081\u00e2\u0094\u0081\u00e2\u0094\u0081\u00e2\u0094\u0081\u00e2\u0094\u0081\u00e2\u0094\u0081\u00e2\u0094\u0081\u00e2\u0094\u0081\u00e2\u0094\u0081\u00e2\u0094\u0081\u00e2\u0094\u0081\u00e2\u0094\u0081\u00e2\u0094\u0081\u00e2\u0094\u0081\u00e2\u0094\u0081\u00e2\u0094\u0081\u00e2\u0094\u0081\u00e2\u0094\u0081\u00e2\u0094\u0081\u00e2\u0094\u0081\u00e2\u0094\u0081\u00e2\u0094\u0093\r\n\u00e2\u0094\u0083 HI PLUGIN. FILTER WINDOW \u00e2\u0094\u0083\r\n\u00e2\u0094\u0083 Filter patterns: \"pattern1|This\" \u00e2\u0094\u0083\r\n\u00e2\u0094\u0097\u00e2\u0094\u0081\u00e2\u0094\u0081\u00e2\u0094\u0081\u00e2\u0094\u0081\u00e2\u0094\u0081\u00e2\u0094\u0081\u00e2\u0094\u0081\u00e2\u0094\u0081\u00e2\u0094\u0081\u00e2\u0094\u0081\u00e2\u0094\u0081\u00e2\u0094\u0081\u00e2\u0094\u0081\u00e2\u0094\u0081\u00e2\u0094\u0081\u00e2\u0094\u0081\u00e2\u0094\u0081\u00e2\u0094\u0081\u00e2\u0094\u0081\u00e2\u0094\u0081\u00e2\u0094\u0081\u00e2\u0094\u0081\u00e2\u0094\u0081\u00e2\u0094\u0081\u00e2\u0094\u0081\u00e2\u0094\u0081\u00e2\u0094\u0081\u00e2\u0094\u0081\u00e2\u0094\u0081\u00e2\u0094\u0081\u00e2\u0094\u0081\u00e2\u0094\u0081\u00e2\u0094\u0081\u00e2\u0094\u0081\u00e2\u0094\u0081\u00e2\u0094\u0081\u00e2\u0094\u0081\u00e2\u0094\u0081\u00e2\u0094\u0081\u00e2\u0094\u0081\u00e2\u0094\u0081\u00e2\u0094\u0081\u00e2\u0094\u0081\u00e2\u0094\u0081\u00e2\u0094\u0081\u00e2\u0094\u0081\u00e2\u0094\u0081\u00e2\u0094\u009b\r\nExample pattern1\r\nThis is my pattern_10 example number 10\r\n\r\n\r\nOnce the filter window's opened, use ENTER key to synchronize the window position between main and filter windows (you can use :Hip command too).\r\n\r\nOnce the filter window's opened, use Alt+ENTER key to synchronize the window position between main and filter windows and switch the focus between main and filter splits (you can use :Hips command too).\r\n\r\n\r\n9) EDITOR window:\r\n\r\nThe highlight configuration editor window allows a more convenient edit of the highlights and filters to apply. Open it with Hie (highlight edit).\r\nUse :Hie to open the editor window (he too) on vertical split on the right side.\r\n\r\nIf you followed the previous example you'll see:\r\n\r\n\u00e2\u0094\u008c\u00e2\u0094\u0080\u00e2\u0094\u0080\u00e2\u0094\u0080\u00e2\u0094\u0080\u00e2\u0094\u0080\u00e2\u0094\u0080\u00e2\u0094\u0080\u00e2\u0094\u0080\u00e2\u0094\u0080\u00e2\u0094\u0080\u00e2\u0094\u0080\u00e2\u0094\u0080\u00e2\u0094\u0080\u00e2\u0094\u0080\u00e2\u0094\u0080\u00e2\u0094\u0080\u00e2\u0094\u0080\u00e2\u0094\u0080\u00e2\u0094\u0080\u00e2\u0094\u0080\u00e2\u0094\u0080\u00e2\u0094\u0080\u00e2\u0094\u0080\u00e2\u0094\u0080\u00e2\u0094\u0080\u00e2\u0094\u0080\u00e2\u0094\u0080\u00e2\u0094\u0080\u00e2\u0094\u0080\u00e2\u0094\u0080\u00e2\u0094\u0080\u00e2\u0094\u0080\u00e2\u0094\u0080\u00e2\u0094\u0080\u00e2\u0094\u0080\u00e2\u0094\u0080\u00e2\u0094\u0080\u00e2\u0094\u0080\u00e2\u0094\u0080\u00e2\u0094\u0090\r\n\u00e2\u0094\u0082 HIGHLIGHT CONFIG: \u00e2\u0094\u0082\r\n\u00e2\u0094\u0094\u00e2\u0094\u0080\u00e2\u0094\u0080\u00e2\u0094\u0080\u00e2\u0094\u0080\u00e2\u0094\u0080\u00e2\u0094\u0080\u00e2\u0094\u0080\u00e2\u0094\u0080\u00e2\u0094\u0080\u00e2\u0094\u0080\u00e2\u0094\u0080\u00e2\u0094\u0080\u00e2\u0094\u0080\u00e2\u0094\u0080\u00e2\u0094\u0080\u00e2\u0094\u0080\u00e2\u0094\u0080\u00e2\u0094\u0080\u00e2\u0094\u0080\u00e2\u0094\u0080\u00e2\u0094\u0080\u00e2\u0094\u0080\u00e2\u0094\u0080\u00e2\u0094\u0080\u00e2\u0094\u0080\u00e2\u0094\u0080\u00e2\u0094\u0080\u00e2\u0094\u0080\u00e2\u0094\u0080\u00e2\u0094\u0080\u00e2\u0094\u0080\u00e2\u0094\u0080\u00e2\u0094\u0080\u00e2\u0094\u0080\u00e2\u0094\u0080\u00e2\u0094\u0080\u00e2\u0094\u0080\u00e2\u0094\u0080\u00e2\u0094\u0080\u00e2\u0094\u0098\r\nMark = r | C |pattern1\r\nMark = g | C |pattern2\r\nMark = g2 | C |PATTERN3\r\nMark = g5 | c |Pattern4\r\nMark = y! | C |pattern5\r\nMark = m_ | C |pattern6\r\nMark = v@ | C |pattern7\r\nMark = v | Cl |pattern8\r\nMark = r@ | Cl |pattern9\r\nMark = g4 | C |my.*pattern_10\r\nMark = n | C |pattern_11\r\nMark = b3! | C |pattern_12\r\nMark = c3_ | C |pattern_13\r\nMark = c3_ | Cl |pattern_14\r\nMark = c | CT |6\r\nMark = c@ | CT |8\r\n\r\nEdit the highlight configuration paragraph and replace it with this self explanatory one:\r\n\r\n\u00e2\u0094\u008c\u00e2\u0094\u0080\u00e2\u0094\u0080\u00e2\u0094\u0080\u00e2\u0094\u0080\u00e2\u0094\u0080\u00e2\u0094\u0080\u00e2\u0094\u0080\u00e2\u0094\u0080\u00e2\u0094\u0080\u00e2\u0094\u0080\u00e2\u0094\u0080\u00e2\u0094\u0080\u00e2\u0094\u0080\u00e2\u0094\u0080\u00e2\u0094\u0080\u00e2\u0094\u0080\u00e2\u0094\u0080\u00e2\u0094\u0080\u00e2\u0094\u0080\u00e2\u0094\u0080\u00e2\u0094\u0080\u00e2\u0094\u0080\u00e2\u0094\u0080\u00e2\u0094\u0080\u00e2\u0094\u0080\u00e2\u0094\u0080\u00e2\u0094\u0080\u00e2\u0094\u0080\u00e2\u0094\u0080\u00e2\u0094\u0080\u00e2\u0094\u0080\u00e2\u0094\u0080\u00e2\u0094\u0080\u00e2\u0094\u0080\u00e2\u0094\u0080\u00e2\u0094\u0080\u00e2\u0094\u0080\u00e2\u0094\u0080\u00e2\u0094\u0080\u00e2\u0094\u0090\r\n\u00e2\u0094\u0082 HIGHLIGHT CONFIG: \u00e2\u0094\u0082\r\n\u00e2\u0094\u0094\u00e2\u0094\u0080\u00e2\u0094\u0080\u00e2\u0094\u0080\u00e2\u0094\u0080\u00e2\u0094\u0080\u00e2\u0094\u0080\u00e2\u0094\u0080\u00e2\u0094\u0080\u00e2\u0094\u0080\u00e2\u0094\u0080\u00e2\u0094\u0080\u00e2\u0094\u0080\u00e2\u0094\u0080\u00e2\u0094\u0080\u00e2\u0094\u0080\u00e2\u0094\u0080\u00e2\u0094\u0080\u00e2\u0094\u0080\u00e2\u0094\u0080\u00e2\u0094\u0080\u00e2\u0094\u0080\u00e2\u0094\u0080\u00e2\u0094\u0080\u00e2\u0094\u0080\u00e2\u0094\u0080\u00e2\u0094\u0080\u00e2\u0094\u0080\u00e2\u0094\u0080\u00e2\u0094\u0080\u00e2\u0094\u0080\u00e2\u0094\u0080\u00e2\u0094\u0080\u00e2\u0094\u0080\u00e2\u0094\u0080\u00e2\u0094\u0080\u00e2\u0094\u0080\u00e2\u0094\u0080\u00e2\u0094\u0080\u00e2\u0094\u0080\u00e2\u0094\u0098\r\n#------------------------------------------\r\n# Clean previous highlights and filters\r\nConf = clear\r\nFilt = close\r\n#------------------------------------------\r\n# Highlight commands:\r\nMark = r | C |pattern1\r\nMark = g | C |pattern2\r\nMark = g2 | C |PATTERN3\r\nMark = g5 | c |Pattern4\r\nMark = y! | C |pattern5\r\nMark = m_ | C |pattern6\r\nMark = v@ | C |pattern7\r\nMark = v | Cl |pattern8\r\nMark = r@ | Cl |pattern9\r\nMark = g4 | C |my.*pattern_10\r\nMark = n | C |pattern_11\r\nMark = b3! | C |pattern_12\r\nMark = c3_ | C |pattern_13\r\nMark = c3_ | Cl |pattern_14\r\nMark = c | CT |6\r\nMark = c@ | CT |8\r\n#------------------------------------------\r\n# Filter commands:\r\nFilt = all\r\n#Filt = r g4 m r@\r\n#------------------------------------------\r\n# Search commands:\r\nFind g4\r\n\r\nAttention: the firs blank line will end the configuration parser on the editor window.\r\nA blank line is mandatory to at the configuration end to stop config parser.\r\n\r\nWhen changing to any other split the editor window will stay minimized, if you change the focus to the editor split again it will expand to its original size.\r\n\r\nAdd # character at the beginning of line to comment any configuration command.\r\n\r\nUse ENTER key to apply the configuration once finished editing\r\n\r\nUse command :Hiy to yank this configuration to the default buffer and :Hicfg to open the configuration files and paste the configuration on the file you want.\r\n\r\n\r\n\r\n10) AUTOLOAD CONFIG LINE (NEW Version 2.0.2)\r\n\r\nAutoload a config highlight type defined on firs\/last five lines of the file.\r\n\r\nThe configuration line will be checked and applied, if found, on file's open or reload.\r\n\r\nAtuo configuration line examples:\r\n\r\nExample 1: load highlight type MY_CONFIG (must be present on the default configuration files: ~\/.vim_hi.cfg or .\/.vim_hi.cfg)\r\nvim_hi:cfg=MY_CONFIG\r\n\r\nExample 2: load configuration file MY_CONFIG_FILE and then apply the highlight type MY_CONFIG.\r\nvim_hi:cfg=MY_CONFIG::cfgfile=MY_CONFIG_FILE\r\n\r\nExample 3 and 4: same as example 2\r\n# vim_hi:cfg=MY_CONFIG::cfgfile=MY_CONFIG_FILE\r\n\/\/ vim_hi:cfg=MY_CONFIG::cfgfile=MY_CONFIG_FILE\r\n\r\n\r\nIf you want to perform a highlight config auto load whenever a .log file is opened, add to your .vimrc:\r\n\r\naugroup HiAutoConfig\r\n au BufRead *.log call hi#autoConfig#ApplyConfig(\"MyLogConfig\", \"MyConfigFile.cfg\")\r\n augroup END\r\n\r\nLast version (2.0.7) allow to have both configuration and autoload line on the file you want to highlitght by defining cfgFile as %.\r\nThe configuration selected (ErrorHighlightConfig) will be searched on the first and last 150 lines of the current file.\r\ne.g:\r\n[ErrorHighlightConfig]\r\nMark = r | CT | Error:\r\nMark = r | CT | Failure:\r\nvim_hi:cfg=ErrorHighlightConfig::cfgFile=% \r\n\r\n\r\n\r\n\r\n11) HIGHLIGHT GROUPS (NEW Version 2.0.2)\r\n\r\nNew tag '??' allows to filter several configurations at a time.\r\n\r\nExample 1: filter all background highlighted patterns.\r\n:Hif @??\r\n\r\nExample 2: filter all underlined patterns.\r\n:Hif _??\r\n\r\nExample 3: filter all bold highlighted patterns.\r\n:Hif !??\r\n\r\nExample 4: filter all red highlighted patterns.\r\n:Hif r*??\r\n\r\nExample 5: filter all red backgraound highlighted patterns.\r\n:Hif r*@??\r\n\r\n\r\n12) HELP menu:\r\n\r\nThere is a small help you can display using command :Hih.\r\nThis will show you the previous (basic) commands and some more.\r\n\r\n","install_details":"Minimum version: Vim 7.0+\r\nRecomended version: Vim 8.0+\r\n\r\nBinaries: ag (silver searcher) or grep needed to open the filter window.\r\n\r\nInstall vimball:\r\ndownload hi_2.0.7.vmb\r\nvim hi_2.0.7.vmb\r\n:so %\r\n:q\r\n\r\nIf you LIKED THE PLUGIN, or you have some improvements, or you dislike it and found it complicated, no matter what, please drop a few lines to my e-mail and TELL ME! (javierpuigdevall@gmail.com)","5":"Minimum version: Vim 7.0+\r\nRecomended version: Vim 8.0+\r\n\r\nBinaries: ag (silver searcher) or grep needed to open the filter window.\r\n\r\nInstall vimball:\r\ndownload hi_2.0.7.vmb\r\nvim hi_2.0.7.vmb\r\n:so %\r\n:q\r\n\r\nIf you LIKED THE PLUGIN, or you have some improvements, or you dislike it and found it complicated, no matter what, please drop a few lines to my e-mail and TELL ME! (javierpuigdevall@gmail.com)","first_name":"Javier","6":"Javier","last_name":"Puigdevall","7":"Puigdevall","releases":[{"0":"5887","vim_version":"7.0","1":"7.0","script_version":"2.0.8","2":"2.0.8","version_comment":"- Fix: enhance the config tags parsing when using functions: IsTitle, IsCommand, IsColor.\r\n Title line format should match format: ^\\[[a-aA-Z].*\\]$\r\n- New: on help (:Hih) command, add color highlighting.\r\n- Fix: bug on Hic when highlighting blocs, tag & not discarded correctly as color modifier.","3":"- Fix: enhance the config tags parsing when using functions: IsTitle, IsCommand, IsColor.\r\n Title line format should match format: ^\\[[a-aA-Z].*\\]$\r\n- New: on help (:Hih) command, add color highlighting.\r\n- Fix: bug on Hic when highlighting blocs, tag & not discarded correctly as color modifier.","package":"hi_2.0.8.vmb","4":"hi_2.0.8.vmb","src_id":"28402","5":"28402","creation_date":"1680634665","6":"1680634665"},{"0":"5887","vim_version":"7.0","1":"7.0","script_version":"2.0.7","2":"2.0.7","version_comment":"- New: when usign an auto config line, and fileConfig='%', the highlight configuration is expected to be found\r\n on the same file, on the first or last 150 lines (defined by: g:HiFileConfigCheckLinesMax).\r\n e.g.:\r\n [ErrorHighlight]\r\n Mark = r | CT | Error:\r\n Mark = r | CT | Failure:\r\n vim_hi:cfg=ErrorHighlight::cfgFile=%\r\n","3":"- New: when usign an auto config line, and fileConfig='%', the highlight configuration is expected to be found\r\n on the same file, on the first or last 150 lines (defined by: g:HiFileConfigCheckLinesMax).\r\n e.g.:\r\n [ErrorHighlight]\r\n Mark = r | CT | Error:\r\n Mark = r | CT | Failure:\r\n vim_hi:cfg=ErrorHighlight::cfgFile=%\r\n","package":"hi_2.0.7.vmb","4":"hi_2.0.7.vmb","src_id":"27956","5":"27956","creation_date":"1646088017","6":"1646088017"},{"0":"5887","vim_version":"7.0","1":"7.0","script_version":"2.0.6","2":"2.0.6","version_comment":"- Fix: Hivba, autoConfig file not included on the vimball file.\r\n- New: command :Hicsb to search in backward direction.\r\n- Fix: autoConfig not initialized.\r\n- Fix: not parsing last file's line when trying to find config line.","3":"- Fix: Hivba, autoConfig file not included on the vimball file.\r\n- New: command :Hicsb to search in backward direction.\r\n- Fix: autoConfig not initialized.\r\n- Fix: not parsing last file's line when trying to find config line.","package":"hi_2.0.6.vmb","4":"hi_2.0.6.vmb","src_id":"27831","5":"27831","creation_date":"1638950659","6":"1638950659"},{"0":"5887","vim_version":"7.0","1":"7.0","script_version":"2.0.4","2":"2.0.4","version_comment":"- New: named groups with configuration command: 'Group = NAME1 NAME2 NAMEN'. Disable group with 'Group = '.\r\n- New: filter commands :Filtw\/Hifw. Perform filter and show results on the same window.\r\n- New: Configuration command Cmd to execute vim commands:\r\n- New: filter option to remove from filter window colorIDs or patters, adding prefix '--' to the pattern or colorId.\r\n- New: Configuration command for Conf options to enable and disable the highlighting: on, off, won, woff\r\n- New: allow pattern search on :Hics or :Hisb commands and 'Find' configuration command.\r\n- New: enable\/disable highlighting commands: Hioff, Hion, Hiwoff, Hiwoff.","3":"- New: named groups with configuration command: 'Group = NAME1 NAME2 NAMEN'. Disable group with 'Group = '.\r\n- New: filter commands :Filtw\/Hifw. Perform filter and show results on the same window.\r\n- New: Configuration command Cmd to execute vim commands:\r\n- New: filter option to remove from filter window colorIDs or patters, adding prefix '--' to the pattern or colorId.\r\n- New: Configuration command for Conf options to enable and disable the highlighting: on, off, won, woff\r\n- New: allow pattern search on :Hics or :Hisb commands and 'Find' configuration command.\r\n- New: enable\/disable highlighting commands: Hioff, Hion, Hiwoff, Hiwoff.","package":"hi.vmb","4":"hi.vmb","src_id":"27334","5":"27334","creation_date":"1602713487","6":"1602713487"},{"0":"5887","vim_version":"7.0","1":"7.0","script_version":"2.0.3","2":"2.0.3","version_comment":"- New: hidden config types, not displayed on Hit command, when the config name starts with '__', like [__hiddenConfig].\r\n- New: colors\/hi.vim. Add on term config 256, colors N1...N8 N1!...N8! N1_...N8_ N1@...N8@ N1@!...N8@!\r\n- New: colors\/hi.vim. Add on gui config, colors: N1...N6 N1!...N6! N1_...N6_ N1@...N6@ N1@!...N6@!\r\n- New: colors\/hi.vim. Align columns.\r\n- New: help.vim. Open help in new split, show plugin version.\r\n- New: test.vim. Improve the tests, include the usage example.\r\n- Fix: Hif command not rejects to filter when no highlighting set.\r\n allow to filer patterns without color highlighting.\r\n- New: highlight only option to omitt a pattern from any filter.\r\n Use '-' (for line command) and 'h' (for config files).\r\n ex: :Hic r- MyPattern\r\n ex: Mark = r | h | MyPattern\r\n- New: highlight groups. Used to filter groups.\r\n Use '&g' (for line command) and 'g' (for config files).\r\n ex: Mark = r | g1 | MyRedPattern\r\n ex: Mark = g | g1 | MyGreenPattern\r\n ex: :Hif &g1\r\n- New: command Hitf CONFIG_NAME CONFIG_FILE to load a highlight config type from file.\r\n- New: config file's command \"Conf\", new \"add\" subcommand to source a new previous defined config.\r\n ex: Conf = add | CONFIG_NAME\r\n- Fix: for config types: \"Conf = add...\" do not show on Hish command neither on the config editor.\r\n- Fix: filter patterns that cotain character '\/' caused and error on the configReload.\r\n- New: enable\/disable highlighting commands: Hi0, Hi1, Hiw0, Hiw1.","3":"- New: hidden config types, not displayed on Hit command, when the config name starts with '__', like [__hiddenConfig].\r\n- New: colors\/hi.vim. Add on term config 256, colors N1...N8 N1!...N8! N1_...N8_ N1@...N8@ N1@!...N8@!\r\n- New: colors\/hi.vim. Add on gui config, colors: N1...N6 N1!...N6! N1_...N6_ N1@...N6@ N1@!...N6@!\r\n- New: colors\/hi.vim. Align columns.\r\n- New: help.vim. Open help in new split, show plugin version.\r\n- New: test.vim. Improve the tests, include the usage example.\r\n- Fix: Hif command not rejects to filter when no highlighting set.\r\n allow to filer patterns without color highlighting.\r\n- New: highlight only option to omitt a pattern from any filter.\r\n Use '-' (for line command) and 'h' (for config files).\r\n ex: :Hic r- MyPattern\r\n ex: Mark = r | h | MyPattern\r\n- New: highlight groups. Used to filter groups.\r\n Use '&g' (for line command) and 'g' (for config files).\r\n ex: Mark = r | g1 | MyRedPattern\r\n ex: Mark = g | g1 | MyGreenPattern\r\n ex: :Hif &g1\r\n- New: command Hitf CONFIG_NAME CONFIG_FILE to load a highlight config type from file.\r\n- New: config file's command \"Conf\", new \"add\" subcommand to source a new previous defined config.\r\n ex: Conf = add | CONFIG_NAME\r\n- Fix: for config types: \"Conf = add...\" do not show on Hish command neither on the config editor.\r\n- Fix: filter patterns that cotain character '\/' caused and error on the configReload.\r\n- New: enable\/disable highlighting commands: Hi0, Hi1, Hiw0, Hiw1.","package":"hi.vmb","4":"hi.vmb","src_id":"27320","5":"27320","creation_date":"1601941781","6":"1601941781"},{"0":"5887","vim_version":"7.0","1":"7.0","script_version":"2.0.2","2":"2.0.2","version_comment":"- New color option ??, used to select all similar colors.\r\n Changes on hi#config#GetColorPatterns and hi#config#GetNonColorPatterns\r\n example: ':Hif g??' will filter all green highlighted colors.\r\n example: ':Hif _??' will filter all underlined colors.\r\n example: ':Hif r*@??' will filter all red background highlighted colors.\r\n- Fix :Hishp, missing function hi#config#ShowPatterns\r\n- New: set config editor buffer nowrite. Prevent writting to file.\r\n- New: config editor use q to close the editor window.\r\n- Fix: configuration file and config editor parsing pattern containing '=' characater.\r\n- New option to autolad a config highlight when a header 'vim_hi:cfg=my_config::cfgfile=my_file' found on top\/bottom when openening or reloading the file.\r\n","3":"- New color option ??, used to select all similar colors.\r\n Changes on hi#config#GetColorPatterns and hi#config#GetNonColorPatterns\r\n example: ':Hif g??' will filter all green highlighted colors.\r\n example: ':Hif _??' will filter all underlined colors.\r\n example: ':Hif r*@??' will filter all red background highlighted colors.\r\n- Fix :Hishp, missing function hi#config#ShowPatterns\r\n- New: set config editor buffer nowrite. Prevent writting to file.\r\n- New: config editor use q to close the editor window.\r\n- Fix: configuration file and config editor parsing pattern containing '=' characater.\r\n- New option to autolad a config highlight when a header 'vim_hi:cfg=my_config::cfgfile=my_file' found on top\/bottom when openening or reloading the file.\r\n","package":"hi.vmb","4":"hi.vmb","src_id":"27302","5":"27302","creation_date":"1598925647","6":"1598925647"},{"0":"5887","vim_version":"7.0","1":"7.0","script_version":"2.0.1","2":"2.0.1","version_comment":"Fix tar.gz error","3":"Fix tar.gz error","package":"hi.tar.gz","4":"hi.tar.gz","src_id":"27205","5":"27205","creation_date":"1592421235","6":"1592421235"},{"0":"5887","vim_version":"7.0","1":"7.0","script_version":"2.0.1","2":"2.0.1","version_comment":"Fix highlight on top of other highlights.\r\nFix Hiid all command.","3":"Fix highlight on top of other highlights.\r\nFix Hiid all command.","package":"hi.tar.gz","4":"hi.tar.gz","src_id":"27199","5":"27199","creation_date":"1591927037","6":"1591927037"},{"0":"5887","vim_version":"7.0","1":"7.0","script_version":"2.0","2":"2.0","version_comment":"Initial upload","3":"Initial upload","package":"hi.tar.gz","4":"hi.tar.gz","src_id":"27198","5":"27198","creation_date":"1591836138","6":"1591836138"}]},"5886":{"script_id":"5886","0":"5886","script_name":"boxcar","1":"boxcar","script_type":"utility","2":"utility","summary":"unicode boxes in vim","3":"unicode boxes in vim","description":"See https:\/\/github.com\/HP4k1h5\/boxcar for details.","4":"See https:\/\/github.com\/HP4k1h5\/boxcar for details.","install_details":"Works with plugin managers.","5":"Works with plugin managers.","first_name":"bob","6":"bob","last_name":"Walker","7":"Walker","releases":[{"0":"5886","vim_version":"8.0","1":"8.0","script_version":"v0.1","2":"v0.1","version_comment":"Initial upload","3":"Initial upload","package":"boxcar_v0.1.zip","4":"boxcar_v0.1.zip","src_id":"27196","5":"27196","creation_date":"1591521603","6":"1591521603"}]},"5885":{"script_id":"5885","0":"5885","script_name":"spaceline.vim","1":"spaceline.vim","script_type":"patch","2":"patch","summary":"emacs spaceline port on vim","3":"emacs spaceline port on vim","description":"We have airline, lightline, eleline, why make this plugin? They are great plugins, but they are limited and you can't set more separators.\r\nMore separator combinations make the status bar look better, and spaceline handles combinations in different situations, very well. The combination of each area is very good in different situations.\r\nspaceline is faster than lightline and airline\r\nmiddle color of spaceline will match your colorscheme background color (now only default colorscheme space support)\r\nsupport scroll bar","4":"We have airline, lightline, eleline, why make this plugin? They are great plugins, but they are limited and you can't set more separators.\r\nMore separator combinations make the status bar look better, and spaceline handles combinations in different situations, very well. The combination of each area is very good in different situations.\r\nspaceline is faster than lightline and airline\r\nmiddle color of spaceline will match your colorscheme background color (now only default colorscheme space support)\r\nsupport scroll bar","install_details":"Plug 'hardcoreplayers\/spaceline.vim'","5":"Plug 'hardcoreplayers\/spaceline.vim'","first_name":"rapheal","6":"rapheal","last_name":"huan","7":"huan","releases":[{"0":"5885","vim_version":"8.0","1":"8.0","script_version":"0.0.1","2":"0.0.1","version_comment":"Initial upload","3":"Initial upload","package":"spaceline.vim.zip","4":"spaceline.vim.zip","src_id":"27186","5":"27186","creation_date":"1591125214","6":"1591125214"}]},"5884":{"script_id":"5884","0":"5884","script_name":"vim-venter","1":"vim-venter","script_type":"utility","2":"utility","summary":"Vim plugin to horizontally center the current window(s)","3":"Vim plugin to horizontally center the current window(s)","description":"vim-venter is a plugin to horizontally center the current window(s)\r\n\r\nGitHub repo: https:\/\/github.com\/JMcKiern\/vim-venter\r\n\r\nCommands\r\n\r\n:Venter - Open venter\r\n:VenterClose - Open venter\r\n:VenterToggle - Toggle venter\r\n:VenterResize - Force a window resize (usually only happens on VimResized, TabEnter and WinEnter events)\r\n\r\nOptions\r\n\r\ng:venter_disable_vertsplit - Set to v:true before calling :Venter to disable the vertical window separators\r\ng:venter_width - Manually set width of padding windows (defaults to &columns\/4)","4":"vim-venter is a plugin to horizontally center the current window(s)\r\n\r\nGitHub repo: https:\/\/github.com\/JMcKiern\/vim-venter\r\n\r\nCommands\r\n\r\n:Venter - Open venter\r\n:VenterClose - Open venter\r\n:VenterToggle - Toggle venter\r\n:VenterResize - Force a window resize (usually only happens on VimResized, TabEnter and WinEnter events)\r\n\r\nOptions\r\n\r\ng:venter_disable_vertsplit - Set to v:true before calling :Venter to disable the vertical window separators\r\ng:venter_width - Manually set width of padding windows (defaults to &columns\/4)","install_details":"","5":"","first_name":"Jack","6":"Jack","last_name":"McKiernan","7":"McKiernan","releases":[{"0":"5884","vim_version":"8.0","1":"8.0","script_version":"0.0.2","2":"0.0.2","version_comment":"Add :VenterToggle","3":"Add :VenterToggle","package":"vim-venter-0.0.2.zip","4":"vim-venter-0.0.2.zip","src_id":"27303","5":"27303","creation_date":"1598926781","6":"1598926781"}]},"5883":{"script_id":"5883","0":"5883","script_name":"gitdraw.vim","1":"gitdraw.vim","script_type":"ftplugin","2":"ftplugin","summary":"draw git heat map by vim","3":"draw git heat map by vim","description":"enew\r\nset ft=gitdraw\r\nTemplate\r\n\" then press and to change the color of block.\r\n\" set your git repo website\r\nCompile\r\n\" then your git heap map will change as your gitdraw file.\r\n\" More info see https:\/\/github.com\/Freed-Wu\/gitdraw.vim\r\n\" Screenshots see https:\/\/zhuanlan.zhihu.com\/p\/141065072","4":"enew\r\nset ft=gitdraw\r\nTemplate\r\n\" then press and to change the color of block.\r\n\" set your git repo website\r\nCompile\r\n\" then your git heap map will change as your gitdraw file.\r\n\" More info see https:\/\/github.com\/Freed-Wu\/gitdraw.vim\r\n\" Screenshots see https:\/\/zhuanlan.zhihu.com\/p\/141065072","install_details":"","5":"","first_name":"Zhenyu","6":"Zhenyu","last_name":"Wu","7":"Wu","releases":[{"0":"5883","vim_version":"7.0","1":"7.0","script_version":"v0.0.1","2":"v0.0.1","version_comment":"Initial upload","3":"Initial upload","package":"gitdraw.vim.7z","4":"gitdraw.vim.7z","src_id":"27176","5":"27176","creation_date":"1590341865","6":"1590341865"}]},"5881":{"script_id":"5881","0":"5881","script_name":"vim-pastebins ","1":"vim-pastebins ","script_type":"utility","2":"utility","summary":"A vim plugin that helps you using pastebin services!","3":"A vim plugin that helps you using pastebin services!","description":"Vim Pastebins\r\n=============\r\nA vim plugin that helps you to use pastebin services, inspired by [webpaste.el](https:\/\/github.com\/etu\/webpaste.el).\r\n\r\nRequirement\r\n-----------\r\n- vim needs to have `+python3` compiled\r\n\r\nSupported Feature\r\n-----------------\r\n- Paste current visual selection\r\n- Paste the entire buffer\r\n- List previously posted pastes\r\n\r\nSupported Pastebin Service\r\n--------------------------\r\n- [Mozilla Paste](paste.mozilla.org) *default*\r\n- [dpaste.org](https:\/\/dpaste.org\/)\r\n\r\nUsage\r\n-----\r\n- Paste Visual Selection\r\n`PastebinPaste` - `` is required to clear the `'<,'>` from the command.\r\n\r\n- Paste the entire buffer\r\n`PastebinPasteAll`\r\n\r\n- List Previous Posted Pastes\r\n`PastebinPasteList`\r\n\r\n\r\nCustomization\r\n-------------\r\n- Change the service provider\r\n`let g:enabled_pastebin_service = \"mozilla\"`\r\n\r\nGithub: https:\/\/github.com\/sefeng211\/vim-pastebins\r\n","4":"Vim Pastebins\r\n=============\r\nA vim plugin that helps you to use pastebin services, inspired by [webpaste.el](https:\/\/github.com\/etu\/webpaste.el).\r\n\r\nRequirement\r\n-----------\r\n- vim needs to have `+python3` compiled\r\n\r\nSupported Feature\r\n-----------------\r\n- Paste current visual selection\r\n- Paste the entire buffer\r\n- List previously posted pastes\r\n\r\nSupported Pastebin Service\r\n--------------------------\r\n- [Mozilla Paste](paste.mozilla.org) *default*\r\n- [dpaste.org](https:\/\/dpaste.org\/)\r\n\r\nUsage\r\n-----\r\n- Paste Visual Selection\r\n`PastebinPaste` - `` is required to clear the `'<,'>` from the command.\r\n\r\n- Paste the entire buffer\r\n`PastebinPasteAll`\r\n\r\n- List Previous Posted Pastes\r\n`PastebinPasteList`\r\n\r\n\r\nCustomization\r\n-------------\r\n- Change the service provider\r\n`let g:enabled_pastebin_service = \"mozilla\"`\r\n\r\nGithub: https:\/\/github.com\/sefeng211\/vim-pastebins\r\n","install_details":"","5":"","first_name":"Sean","6":"Sean","last_name":"Feng","7":"Feng","releases":[{"0":"5881","vim_version":"7.0","1":"7.0","script_version":"0.2.0","2":"0.2.0","version_comment":"- Fallback to text when the file type is not supported\r\n- Allow to paste the entire buffer\r\n\r\n","3":"- Fallback to text when the file type is not supported\r\n- Allow to paste the entire buffer\r\n\r\n","package":"vim-pastebins-0.2.0.zip","4":"vim-pastebins-0.2.0.zip","src_id":"27175","5":"27175","creation_date":"1590312789","6":"1590312789"}]},"5880":{"script_id":"5880","0":"5880","script_name":"Buffer selector","1":"Buffer selector","script_type":"utility","2":"utility","summary":"Buffer Selector - Vim plugin for selecting a buffer to edit using a popup menu","3":"Buffer Selector - Vim plugin for selecting a buffer to edit using a popup menu","description":"The Buffer Selector plugin provides an easy access to jump to a buffer from the Vim buffer list.\r\n\r\nThis plugin needs Vim 8.2 and above and will work on all the platforms where Vim is supported. This plugin will work in both terminal and GUI Vim.\r\n\r\nThe Github repository for the Buffer Selector plugin is available at:\r\n\r\n https:\/\/github.com\/yegappan\/bufselect\r\n\r\nThe command :Bufselect opens a popup menu with a list of names of buffers in the Vim buffer list (|:buffers|). When you press on a buffer name, the buffer is opened. If the selected buffer is already opened in a window, the cursor will move to that window. If the buffer it not present in any of the windows, then the selected buffer will be opened in the current window. You can use the up and down arrow keys to move the currently selected entry in the popup menu.\r\n\r\nIn the popup menu, you can type a series of characters to narrow down the list of displayed buffer names. The characters entered so far is displayed in the popup menu title. You can press backspace to erase the previously entered set of characters. The popup menu displays all the buffer names containing the series of typed characters.\r\n\r\nYou can close the popup menu by pressing the escape key or by pressing CTRL-C.\r\n\r\nIn the popup menu, the complete directory path to a buffer is displayed in parenthesis after the buffer name. If this is too long, then the path is shortened and an abbreviated path is displayed.\r\n","4":"The Buffer Selector plugin provides an easy access to jump to a buffer from the Vim buffer list.\r\n\r\nThis plugin needs Vim 8.2 and above and will work on all the platforms where Vim is supported. This plugin will work in both terminal and GUI Vim.\r\n\r\nThe Github repository for the Buffer Selector plugin is available at:\r\n\r\n https:\/\/github.com\/yegappan\/bufselect\r\n\r\nThe command :Bufselect opens a popup menu with a list of names of buffers in the Vim buffer list (|:buffers|). When you press on a buffer name, the buffer is opened. If the selected buffer is already opened in a window, the cursor will move to that window. If the buffer it not present in any of the windows, then the selected buffer will be opened in the current window. You can use the up and down arrow keys to move the currently selected entry in the popup menu.\r\n\r\nIn the popup menu, you can type a series of characters to narrow down the list of displayed buffer names. The characters entered so far is displayed in the popup menu title. You can press backspace to erase the previously entered set of characters. The popup menu displays all the buffer names containing the series of typed characters.\r\n\r\nYou can close the popup menu by pressing the escape key or by pressing CTRL-C.\r\n\r\nIn the popup menu, the complete directory path to a buffer is displayed in parenthesis after the buffer name. If this is too long, then the path is shortened and an abbreviated path is displayed.\r\n","install_details":"You can install this plugin either using the bufselect.zip file or by cloning the repository from Github.\r\n\r\nTo install using the bufselect.zip file:\r\n\r\n Download the bufselect.zip file and extract the files into the ~\/.vim\/pack\/downloads\/opt or the %HOMEPATH%\\vimfiles\\pack\\downloads\\opt directory.\r\n\r\nTo install from Github:\r\n\r\n For Linux, MacOS and other Unix-like systems:\r\n\r\n $ mkdir -p ~\/.vim\/pack\/downloads\/opt\r\n $ cd ~\/.vim\/pack\/downloads\/opt\r\n $ git clone https:\/\/github.com\/yegappan\/bufselect\r\n\r\n For MS-Windows:\r\n\r\n C:\\> mkdir %HOMEPATH%\\vimfiles\\pack\\downloads\\opt\r\n C:\\> cd %HOMEPATH%\\vimfiles\\pack\\downloads\\opt\r\n C:\\> git clone https:\/\/github.com\/yegappan\/bufselect\r\n\r\nTo load the plugin, add the following command to the ~\/.vimrc file:\r\n\r\n packadd bufselect\r\n\r\nTo uninstall the plugin, remove the $HOME\/.vim\/pack\/downloads\/opt\/bufselect directory.\r\n\r\nTo create the help tags for the plugin help file, run the following command from Vim:\r\n\r\n :helptags ~\/.vim\/pack\/downloads\/opt\/bufselect\/doc\r\n","5":"You can install this plugin either using the bufselect.zip file or by cloning the repository from Github.\r\n\r\nTo install using the bufselect.zip file:\r\n\r\n Download the bufselect.zip file and extract the files into the ~\/.vim\/pack\/downloads\/opt or the %HOMEPATH%\\vimfiles\\pack\\downloads\\opt directory.\r\n\r\nTo install from Github:\r\n\r\n For Linux, MacOS and other Unix-like systems:\r\n\r\n $ mkdir -p ~\/.vim\/pack\/downloads\/opt\r\n $ cd ~\/.vim\/pack\/downloads\/opt\r\n $ git clone https:\/\/github.com\/yegappan\/bufselect\r\n\r\n For MS-Windows:\r\n\r\n C:\\> mkdir %HOMEPATH%\\vimfiles\\pack\\downloads\\opt\r\n C:\\> cd %HOMEPATH%\\vimfiles\\pack\\downloads\\opt\r\n C:\\> git clone https:\/\/github.com\/yegappan\/bufselect\r\n\r\nTo load the plugin, add the following command to the ~\/.vimrc file:\r\n\r\n packadd bufselect\r\n\r\nTo uninstall the plugin, remove the $HOME\/.vim\/pack\/downloads\/opt\/bufselect directory.\r\n\r\nTo create the help tags for the plugin help file, run the following command from Vim:\r\n\r\n :helptags ~\/.vim\/pack\/downloads\/opt\/bufselect\/doc\r\n","first_name":"Yegappan","6":"Yegappan","last_name":"Lakshmanan","7":"Lakshmanan","releases":[{"0":"5880","vim_version":"8.0","1":"8.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"bufselect.zip","4":"bufselect.zip","src_id":"27157","5":"27157","creation_date":"1589529078","6":"1589529078"}]},"5879":{"script_id":"5879","0":"5879","script_name":"ephemeris","1":"ephemeris","script_type":"utility","2":"utility","summary":"diary, agenda, notes plugin ","3":"diary, agenda, notes plugin ","description":"homepage: https:\/\/github.com\/HP4k1h5\/ephemeris\r\n\r\n! experimental and unstable see BUGS (https:\/\/github.com\/HP4k1h5\/ephemeris#bugs)\r\n\r\n**see `README.md` and `doc\/ephemeris.txt` for additional help**\r\n\r\n","4":"homepage: https:\/\/github.com\/HP4k1h5\/ephemeris\r\n\r\n! experimental and unstable see BUGS (https:\/\/github.com\/HP4k1h5\/ephemeris#bugs)\r\n\r\n**see `README.md` and `doc\/ephemeris.txt` for additional help**\r\n\r\n","install_details":"use your preferred vim plugin manager or download\/clone this plugin\/repo and continue with manual install (see `:help plugin`). ","5":"use your preferred vim plugin manager or download\/clone this plugin\/repo and continue with manual install (see `:help plugin`). ","first_name":"bob","6":"bob","last_name":"Walker","7":"Walker","releases":[{"0":"5879","vim_version":"8.0","1":"8.0","script_version":"v0.9","2":"v0.9","version_comment":"new features:\r\n - archive\r\n - agenda\r\n - folding","3":"new features:\r\n - archive\r\n - agenda\r\n - folding","package":"ephemeris_v0.9.zip","4":"ephemeris_v0.9.zip","src_id":"27222","5":"27222","creation_date":"1593753817","6":"1593753817"},{"0":"5879","vim_version":"8.0","1":"8.0","script_version":"v0.7","2":"v0.7","version_comment":"- filter to archive\r\n- docs\r\n- tests","3":"- filter to archive\r\n- docs\r\n- tests","package":"ephemeris_v0.7.zip","4":"ephemeris_v0.7.zip","src_id":"27184","5":"27184","creation_date":"1590962142","6":"1590962142"},{"0":"5879","vim_version":"8.0","1":"8.0","script_version":"0.5","2":"0.5","version_comment":"vader tests\r\ndocs\r\nfixes","3":"vader tests\r\ndocs\r\nfixes","package":"ephemeris_0.5.zip","4":"ephemeris_0.5.zip","src_id":"27177","5":"27177","creation_date":"1590399837","6":"1590399837"}]},"5878":{"script_id":"5878","0":"5878","script_name":"easter","1":"easter","script_type":"utility","2":"utility","summary":"compute the date of Gregorian Easter for a given year","3":"compute the date of Gregorian Easter for a given year","description":"easter#date(year), where year is an integer > 1582, returns (if no error) a Dictionary with keys 'year' 'month' and 'day'. Each key value is an integer.\r\n\r\n- Strings are converted to integers the usual Vim way\r\n- Floats are truncated to an Integer by discarding any fractional part\r\n- Other non-integer types, or values < 1583, cause an error and return an empty Dictionary.\r\n\r\nYears in the far future are accepted but may cause unspecified behaviour (e.g. there is talk of making years 4000, 8000, 12000, etc. non-leap: this eventuality has not been taken into account).\r\n\r\nSee also the comments in the script source.\r\n\r\nKnown limitation: To be used for Gregorian Easter only. Dates for Julian (Orthodox) Easter, or for Pesach, are nor computed.","4":"easter#date(year), where year is an integer > 1582, returns (if no error) a Dictionary with keys 'year' 'month' and 'day'. Each key value is an integer.\r\n\r\n- Strings are converted to integers the usual Vim way\r\n- Floats are truncated to an Integer by discarding any fractional part\r\n- Other non-integer types, or values < 1583, cause an error and return an empty Dictionary.\r\n\r\nYears in the far future are accepted but may cause unspecified behaviour (e.g. there is talk of making years 4000, 8000, 12000, etc. non-leap: this eventuality has not been taken into account).\r\n\r\nSee also the comments in the script source.\r\n\r\nKnown limitation: To be used for Gregorian Easter only. Dates for Julian (Orthodox) Easter, or for Pesach, are nor computed.","install_details":"Drop the script in the autolad\/ subdirectory of a 'runtimepath' directory other than $VIMRUNTIME","5":"Drop the script in the autolad\/ subdirectory of a 'runtimepath' directory other than $VIMRUNTIME","first_name":"Antoine","6":"Antoine","last_name":"Mechelynck","7":"Mechelynck","releases":[{"0":"5878","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"easter.vim","4":"easter.vim","src_id":"27146","5":"27146","creation_date":"1588469153","6":"1588469153"}]},"5877":{"script_id":"5877","0":"5877","script_name":"vim-mr-interface","1":"vim-mr-interface","script_type":"utility","2":"utility","summary":"vim plugin that support doing CRs and MRs in gitlab from vim","3":"vim plugin that support doing CRs and MRs in gitlab from vim","description":"Active development of the plugin is done here:\r\nhttps:\/\/github.com\/omrisarig13\/vim-mr-interface\r\nfor full information about it, with more updated versions and more issues, please look at the project there.\r\n\r\nIntroduction\r\n\r\nWriting code require doing code reviews (CRs) on this code. Since you are writing the code in vim, why not do the CR inside vim as well?\r\n\r\nThe aim of this plugin is to let you do CR on code in gitlab from vim. CR usually include opening a merge request (MR), and then moving over the diff in the code and adding comments into the gitlab\\'s MR. Since you are reading about vim plugins, you probably know and understand why vim is a good tool for writing and reading code. Why won\\'t you want to do your CR in vim as well? This plugin let you do the CR from vim, adding comments and discussion threads wherever you want and updating all this information on the gitlab\\'s MR.\r\n\r\nThe plugin does all this by using gitlab\\'s API, which let you get, add, change or delete comments from MRs in it (with a lot of other stuff that this plugin doesn\\'t touch).\r\nUsage\r\n\r\nThis plugin lets you review the code and add comments directly into an open MR.\r\n\r\nIn order to use it, you should have an open MR in gitlab. Add your comments from vim using the various commands of the plugin, instead of by opening gitlab\\'s web.\r\nCommands\r\nGitlab Commands\r\n\r\n MRInterfaceAddComment - Add a comment into the MR.\r\n MRInterfaceAddGeneralDiscussionThread - Add a general discussion thread into the MR. A general discussion thread is the same as a comment, but it can be resolved.\r\n MRInterfaceAddCodeDiscussionThread - Add a discussion thread on specific location for the MR. This location currently can be only a line of text in one of the changed files (which is enough for almost anything).\r\n\r\nCache Commands\r\n\r\nThe plugin has some commands that can control the internal cache it keeps. This cache will make you type the common values for the MR just once for every merge request. You can read in the help file more about this cache mechanism.\r\n\r\nThe commands are:\r\n\r\n MRInterfaceResetCache - Reset the cache.\r\n MRInterfaceSetCache - Set all the values in the cache. You will be prompted to insert the values for the different keys one by one.\r\n MRInterfaceUpdateValueInCache - Set a specific value in the cache.\r\n\r\nConfiguration Options\r\n\r\nThese flags can be configured for the plugin. These flags should be configured using Glaive.\r\n\r\n gitlab_server_address - The address of the gitlab server to use (in case you are not using gitlab.com).\r\n gitlab_private_token - Your private token to authenticate with gitlab.\r\n automatically_insert_cache - Should the cache be inserted authomatically, or should it be only the default.\r\n","4":"Active development of the plugin is done here:\r\nhttps:\/\/github.com\/omrisarig13\/vim-mr-interface\r\nfor full information about it, with more updated versions and more issues, please look at the project there.\r\n\r\nIntroduction\r\n\r\nWriting code require doing code reviews (CRs) on this code. Since you are writing the code in vim, why not do the CR inside vim as well?\r\n\r\nThe aim of this plugin is to let you do CR on code in gitlab from vim. CR usually include opening a merge request (MR), and then moving over the diff in the code and adding comments into the gitlab\\'s MR. Since you are reading about vim plugins, you probably know and understand why vim is a good tool for writing and reading code. Why won\\'t you want to do your CR in vim as well? This plugin let you do the CR from vim, adding comments and discussion threads wherever you want and updating all this information on the gitlab\\'s MR.\r\n\r\nThe plugin does all this by using gitlab\\'s API, which let you get, add, change or delete comments from MRs in it (with a lot of other stuff that this plugin doesn\\'t touch).\r\nUsage\r\n\r\nThis plugin lets you review the code and add comments directly into an open MR.\r\n\r\nIn order to use it, you should have an open MR in gitlab. Add your comments from vim using the various commands of the plugin, instead of by opening gitlab\\'s web.\r\nCommands\r\nGitlab Commands\r\n\r\n MRInterfaceAddComment - Add a comment into the MR.\r\n MRInterfaceAddGeneralDiscussionThread - Add a general discussion thread into the MR. A general discussion thread is the same as a comment, but it can be resolved.\r\n MRInterfaceAddCodeDiscussionThread - Add a discussion thread on specific location for the MR. This location currently can be only a line of text in one of the changed files (which is enough for almost anything).\r\n\r\nCache Commands\r\n\r\nThe plugin has some commands that can control the internal cache it keeps. This cache will make you type the common values for the MR just once for every merge request. You can read in the help file more about this cache mechanism.\r\n\r\nThe commands are:\r\n\r\n MRInterfaceResetCache - Reset the cache.\r\n MRInterfaceSetCache - Set all the values in the cache. You will be prompted to insert the values for the different keys one by one.\r\n MRInterfaceUpdateValueInCache - Set a specific value in the cache.\r\n\r\nConfiguration Options\r\n\r\nThese flags can be configured for the plugin. These flags should be configured using Glaive.\r\n\r\n gitlab_server_address - The address of the gitlab server to use (in case you are not using gitlab.com).\r\n gitlab_private_token - Your private token to authenticate with gitlab.\r\n automatically_insert_cache - Should the cache be inserted authomatically, or should it be only the default.\r\n","install_details":"This plugin is written in pure vimscript, but it require some other plugins and system commands in the system.\r\n\r\nThe plugin can be installed using any method of plugin installation for vim as long as all the Dependencies will be present when the plugin is loaded and run.\r\n\r\nVundle\r\n\r\nAn example of how to install this plugin using Vundle:\r\n\r\nPlugin \\'google\/vim-maktaba\\'\r\nPlugin \\'google\/vim-glaive\\'\r\nPlugin \\'LucHermitte\/lh-vim-lib\\'\r\nPlugin \\'omrisarig13\/vim-mr-interface\\'\r\n\r\nDependencies\r\n\r\n Curl - command line tool and library for transferring data with URLs\r\n google\/vim-maktaba - A vimscript plugin library. Used internally by the plugin.\r\n google\/vim-glaive - utility for configuring maktaba plugins. It is used to set the different configurable variables in the plugin.\r\n LucHermitte\/lh-vim-lib - Library of Vim functions.\r\n\r\nSupported platforms\r\n\r\nThis plugin should work on any platform that can run the CURL from within vim. However, it was tested only on Linux, so it is not guaranteed to work the same under other systems.","5":"This plugin is written in pure vimscript, but it require some other plugins and system commands in the system.\r\n\r\nThe plugin can be installed using any method of plugin installation for vim as long as all the Dependencies will be present when the plugin is loaded and run.\r\n\r\nVundle\r\n\r\nAn example of how to install this plugin using Vundle:\r\n\r\nPlugin \\'google\/vim-maktaba\\'\r\nPlugin \\'google\/vim-glaive\\'\r\nPlugin \\'LucHermitte\/lh-vim-lib\\'\r\nPlugin \\'omrisarig13\/vim-mr-interface\\'\r\n\r\nDependencies\r\n\r\n Curl - command line tool and library for transferring data with URLs\r\n google\/vim-maktaba - A vimscript plugin library. Used internally by the plugin.\r\n google\/vim-glaive - utility for configuring maktaba plugins. It is used to set the different configurable variables in the plugin.\r\n LucHermitte\/lh-vim-lib - Library of Vim functions.\r\n\r\nSupported platforms\r\n\r\nThis plugin should work on any platform that can run the CURL from within vim. However, it was tested only on Linux, so it is not guaranteed to work the same under other systems.","first_name":"Omri","6":"Omri","last_name":"Sarig","7":"Sarig","releases":[{"0":"5877","vim_version":"7.0","1":"7.0","script_version":"v0.2","2":"v0.2","version_comment":"Adds lots of new features to the plugin:\r\n* Change comments to use temporary buffers\r\n* Print errors for bad requests\r\n* Add option to create a comment on current line\r\n* Add parameter calculation to the plugin\r\n* Add documentation and recommended mappings","3":"Adds lots of new features to the plugin:\r\n* Change comments to use temporary buffers\r\n* Print errors for bad requests\r\n* Add option to create a comment on current line\r\n* Add parameter calculation to the plugin\r\n* Add documentation and recommended mappings","package":"vim-mr-interface-0.2.tar.gz","4":"vim-mr-interface-0.2.tar.gz","src_id":"27152","5":"27152","creation_date":"1589084700","6":"1589084700"},{"0":"5877","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"vim-mr-interface-0.1.tar.gz","4":"vim-mr-interface-0.1.tar.gz","src_id":"27144","5":"27144","creation_date":"1588439992","6":"1588439992"}]},"5876":{"script_id":"5876","0":"5876","script_name":"indent-bar","1":"indent-bar","script_type":"utility","2":"utility","summary":"Use vertical bar to display indentation level","3":"Use vertical bar to display indentation level","description":"This plugin uses vertical bars to display indentation level, pretty much like the indentation display in Sublime Text.","4":"This plugin uses vertical bars to display indentation level, pretty much like the indentation display in Sublime Text.","install_details":"Simply download the plugin files and put them in ~\/.vim (Linux) or ~\/vimfile (Windows) to achieve the effects. Or, you can also use a third party package manager to install the plugin, for example, if you use 'junegunn\/vim-plug' as your package manager, you can put below line into your ~\/.vimrc\r\n\r\nPlug 'juniway\/indent-bar'\r\n\r\nCustomization\r\nYou can change the style of vertical bar by setting g:indenters_char variable:\r\n\r\nfor example:\r\nset let g:indent_bar_char = '\u00c2\u00a6'\r\nthe provided options are: \u00c2\u00a6, ┆ or │ \r\n\r\nNote: these characters will only work with files whose encoding is UTF-8.\r\n\r\nGithub Repository:\r\nhttps:\/\/github.com\/juniway\/indent-bar\r\n","5":"Simply download the plugin files and put them in ~\/.vim (Linux) or ~\/vimfile (Windows) to achieve the effects. Or, you can also use a third party package manager to install the plugin, for example, if you use 'junegunn\/vim-plug' as your package manager, you can put below line into your ~\/.vimrc\r\n\r\nPlug 'juniway\/indent-bar'\r\n\r\nCustomization\r\nYou can change the style of vertical bar by setting g:indenters_char variable:\r\n\r\nfor example:\r\nset let g:indent_bar_char = '\u00c2\u00a6'\r\nthe provided options are: \u00c2\u00a6, ┆ or │ \r\n\r\nNote: these characters will only work with files whose encoding is UTF-8.\r\n\r\nGithub Repository:\r\nhttps:\/\/github.com\/juniway\/indent-bar\r\n","first_name":"Jux","6":"Jux","last_name":"Shi","7":"Shi","releases":[{"0":"5876","vim_version":"8.0","1":"8.0","script_version":"0.1.1","2":"0.1.1","version_comment":"fix typo","3":"fix typo","package":"indent-bar.zip","4":"indent-bar.zip","src_id":"27145","5":"27145","creation_date":"1588444552","6":"1588444552"},{"0":"5876","vim_version":"8.0","1":"8.0","script_version":"0.1.0","2":"0.1.0","version_comment":"Initial upload","3":"Initial upload","package":"indenters.zip","4":"indenters.zip","src_id":"27140","5":"27140","creation_date":"1588345297","6":"1588345297"}]},"5875":{"script_id":"5875","0":"5875","script_name":"SelX","1":"SelX","script_type":"utility","2":"utility","summary":"A Rainbow of Vim selection\/highlighting & search","3":"A Rainbow of Vim selection\/highlighting & search","description":"INTRODUCTION\r\n\r\n!!! New commands now allow highlights to be set and controlled across all tabs, as well as just the current tab !!!\r\n\r\nSelX provides additional selection\/highlighting\/search functions that operate in a very similar way to the standard '*' (and similar) key mappings and the standard '\/' (and similar) command line search operations; the difference is that multiple, multi-coloured highlights are supported, operating on a per-tab basis. Highlights can also be set and controlled across ALL tabs. Up to 99 different highlight colours may be defined.\r\n\r\nThe selection\/highlight selections can also (optionally) be saved as part of a vim session. This is also supported by my SessX plugin - vimscript #5874\r\n\r\nSelX is intended to complement rather then replace the standard vim selection\/search highlight facility\r\n\r\nNOTE: I really have no idea what the minimum vim version requirement is to run SelX and I don't know of a practical way of finding out (I've only used it on v8.2). The best I can suggest is to try it; it will probably work and if it doesn't then let me know and I'll see if I can sort it\r\n\r\n*** If you have any suggestions for improving this, then please let me know. If you think it's rubbish then PLEASE let me know why - it's far more useful than just 'voting it down' (which really doesn't help at all). Contact details are in the top of the README file ***\r\n\r\nHIGHLIGHT USAGE MAP\r\n\r\nIn order to keep track of which selections\/highlights are set, a Highlight Usage Map is automatically displayed on the in-focus window's status line. This Highlight Usage Map looks something like the following;-\r\n\r\n [ 1 | 2 | 3 | | | 6 |^ | | ]\r\n\r\nThe Map has an entry for each of the available SelX highlight colours (in reality, the map entries are appropriately coloured)\r\n\r\nIf a particular highlight is not set then it is shown with just its colour (for example, numbers 4 and 5)\r\n\r\nIf a particular highlight is set then it is shown with its number (for example, numbers 1, 2 and 3)\r\n\r\nThe '^' is always displayed and points to the next highlight that will be used when the auto-selection command is used\r\n\r\nMarkers are also placed (not shown in the above drawing - see the README) to show whether a selection\/highlight is a whole word or arbitrary, and whether or not it is case-sensitive. The case-sensitivity can be set prior to the selection and both of these attributes can be toggled after a selection has been made\r\n\r\nMAPPINGS\r\n\r\nThere are several mappings\/commands for selecting\/highlighting and searching for a specific selection which mirror the normal '*' (and other) mappings and command line '\/' and '?' commands\r\n\r\nThere are also some optional mappings that enhance (depending on your point of view) the standard vim highlight\/search operation\r\n","4":"INTRODUCTION\r\n\r\n!!! New commands now allow highlights to be set and controlled across all tabs, as well as just the current tab !!!\r\n\r\nSelX provides additional selection\/highlighting\/search functions that operate in a very similar way to the standard '*' (and similar) key mappings and the standard '\/' (and similar) command line search operations; the difference is that multiple, multi-coloured highlights are supported, operating on a per-tab basis. Highlights can also be set and controlled across ALL tabs. Up to 99 different highlight colours may be defined.\r\n\r\nThe selection\/highlight selections can also (optionally) be saved as part of a vim session. This is also supported by my SessX plugin - vimscript #5874\r\n\r\nSelX is intended to complement rather then replace the standard vim selection\/search highlight facility\r\n\r\nNOTE: I really have no idea what the minimum vim version requirement is to run SelX and I don't know of a practical way of finding out (I've only used it on v8.2). The best I can suggest is to try it; it will probably work and if it doesn't then let me know and I'll see if I can sort it\r\n\r\n*** If you have any suggestions for improving this, then please let me know. If you think it's rubbish then PLEASE let me know why - it's far more useful than just 'voting it down' (which really doesn't help at all). Contact details are in the top of the README file ***\r\n\r\nHIGHLIGHT USAGE MAP\r\n\r\nIn order to keep track of which selections\/highlights are set, a Highlight Usage Map is automatically displayed on the in-focus window's status line. This Highlight Usage Map looks something like the following;-\r\n\r\n [ 1 | 2 | 3 | | | 6 |^ | | ]\r\n\r\nThe Map has an entry for each of the available SelX highlight colours (in reality, the map entries are appropriately coloured)\r\n\r\nIf a particular highlight is not set then it is shown with just its colour (for example, numbers 4 and 5)\r\n\r\nIf a particular highlight is set then it is shown with its number (for example, numbers 1, 2 and 3)\r\n\r\nThe '^' is always displayed and points to the next highlight that will be used when the auto-selection command is used\r\n\r\nMarkers are also placed (not shown in the above drawing - see the README) to show whether a selection\/highlight is a whole word or arbitrary, and whether or not it is case-sensitive. The case-sensitivity can be set prior to the selection and both of these attributes can be toggled after a selection has been made\r\n\r\nMAPPINGS\r\n\r\nThere are several mappings\/commands for selecting\/highlighting and searching for a specific selection which mirror the normal '*' (and other) mappings and command line '\/' and '?' commands\r\n\r\nThere are also some optional mappings that enhance (depending on your point of view) the standard vim highlight\/search operation\r\n","install_details":"Un-tar into ~\/.vim\/bundle\/ as usual and read the README file for setup and config options\r\n\r\nNote that there is some initial setup required to integrate this into your vim installation","5":"Un-tar into ~\/.vim\/bundle\/ as usual and read the README file for setup and config options\r\n\r\nNote that there is some initial setup required to integrate this into your vim installation","first_name":"Richard","6":"Richard","last_name":"Bentley-Green","7":"Bentley-Green","releases":[{"0":"5875","vim_version":"7.0","1":"7.0","script_version":"15\/04\/2023","2":"15\/04\/2023","version_comment":"Added new commands and mappings to allow highlights to be set and controlled across all tabs","3":"Added new commands and mappings to allow highlights to be set and controlled across all tabs","package":"selx.tar.gz","4":"selx.tar.gz","src_id":"28425","5":"28425","creation_date":"1682303277","6":"1682303277"},{"0":"5875","vim_version":"7.0","1":"7.0","script_version":"14\/01\/2023","2":"14\/01\/2023","version_comment":"I discovered that defining the dummy version of selx#Statusline() - see change on 26\/04\/2020 above - actually has the effect of bringing-in and parsing the SelX autoload code! I think this is a bug in vim but is (apparently) expected behaviour. So I have now removed this dummy function and replaced it with the function g:SelxStatusline(). Using this wrapper function will ensure that the autoload code is not brought in\/parsed unnecessarily. The README has been updated to reflect the change when using this for the vim buffer status bar\r\n","3":"I discovered that defining the dummy version of selx#Statusline() - see change on 26\/04\/2020 above - actually has the effect of bringing-in and parsing the SelX autoload code! I think this is a bug in vim but is (apparently) expected behaviour. So I have now removed this dummy function and replaced it with the function g:SelxStatusline(). Using this wrapper function will ensure that the autoload code is not brought in\/parsed unnecessarily. The README has been updated to reflect the change when using this for the vim buffer status bar\r\n","package":"selx.tar.gz","4":"selx.tar.gz","src_id":"28350","5":"28350","creation_date":"1673754866","6":"1673754866"},{"0":"5875","vim_version":"7.0","1":"7.0","script_version":"02\/08\/2022","2":"02\/08\/2022","version_comment":"- The search index (used by (`n` and ``\/`N`) now operates per-tab (the auto-selection index has always done)\r\n- The auto-selection index, and the search index are now transposed to a new tab opened with the `tt` mapping\r\n- Added facility to (optionally) copy the auto-selection index and the search index between tabs (via the \\'SelXPaseteAll` command)\r\n- Added g:SelxPasteNextIdx and g:SelxPasteSearchIdx options to support (switching on\/off) this functionality\r\n- The usage map and output from the `SelXList` function now displays which highlight (if any) is the target of the search operations (`n` and ``\/`N`)\r\n- Added new command; `>\\'\/`>` to set search to last defined highlight (per tab) - surprisingly useful!\r\n- The auto-selection index, and the search index are now saved to the session (if the appropriate config is set up, of course)\r\n- Added `g:SelxStripDecor` option to allow the output of some commands\/mappings to produce cleaner output\r\n- Some of the command line output showing the highlight colours did not include the highlight attributes. This has now been added\r\n","3":"- The search index (used by (`n` and ``\/`N`) now operates per-tab (the auto-selection index has always done)\r\n- The auto-selection index, and the search index are now transposed to a new tab opened with the `tt` mapping\r\n- Added facility to (optionally) copy the auto-selection index and the search index between tabs (via the \\'SelXPaseteAll` command)\r\n- Added g:SelxPasteNextIdx and g:SelxPasteSearchIdx options to support (switching on\/off) this functionality\r\n- The usage map and output from the `SelXList` function now displays which highlight (if any) is the target of the search operations (`n` and ``\/`N`)\r\n- Added new command; `>\\'\/`>` to set search to last defined highlight (per tab) - surprisingly useful!\r\n- The auto-selection index, and the search index are now saved to the session (if the appropriate config is set up, of course)\r\n- Added `g:SelxStripDecor` option to allow the output of some commands\/mappings to produce cleaner output\r\n- Some of the command line output showing the highlight colours did not include the highlight attributes. This has now been added\r\n","package":"selx.tar.gz","4":"selx.tar.gz","src_id":"28126","5":"28126","creation_date":"1660600965","6":"1660600965"},{"0":"5875","vim_version":"7.0","1":"7.0","script_version":"02\/05\/2022","2":"02\/05\/2022","version_comment":"- Added g:SelxDispMapNextCol option to allow further possibilities with configuring the highlight usage map\r\n","3":"- Added g:SelxDispMapNextCol option to allow further possibilities with configuring the highlight usage map\r\n","package":"selx.tar.gz","4":"selx.tar.gz","src_id":"28025","5":"28025","creation_date":"1651549984","6":"1651549984"},{"0":"5875","vim_version":"7.0","1":"7.0","script_version":"29\/04\/2022","2":"29\/04\/2022","version_comment":"- Expanded the maximum number of highlight colours from 9 to 99\r\n- Added g:SelxExtKeyMap to support additional colours (> 10)\r\n- Added g:SelxDispMapMarks option to allow small reduction in map size\r\n","3":"- Expanded the maximum number of highlight colours from 9 to 99\r\n- Added g:SelxExtKeyMap to support additional colours (> 10)\r\n- Added g:SelxDispMapMarks option to allow small reduction in map size\r\n","package":"selx.tar.gz","4":"selx.tar.gz","src_id":"28021","5":"28021","creation_date":"1651360163","6":"1651360163"},{"0":"5875","vim_version":"7.0","1":"7.0","script_version":"24\/04\/2022","2":"24\/04\/2022","version_comment":"- Corrected a minor but annoying bug whereby if a 'normal' vim highlight was active (displayed) and a 'SelX' highlight was created in visual selection mode, the 'SelX' highlight would be created ok, but the original 'normal' highlight would get re-assigned to the same as the 'SelX' highlight. The correction means that the 'normal' highlight is left as-is now\r\n- Improved the `n` mapping so that it now visually selects the next located text. This makes repeated use of this mapping much more usable\r\n- Corrected some comparisons which should be case-sensitive but may not be in some vim configurations\r\n","3":"- Corrected a minor but annoying bug whereby if a 'normal' vim highlight was active (displayed) and a 'SelX' highlight was created in visual selection mode, the 'SelX' highlight would be created ok, but the original 'normal' highlight would get re-assigned to the same as the 'SelX' highlight. The correction means that the 'normal' highlight is left as-is now\r\n- Improved the `n` mapping so that it now visually selects the next located text. This makes repeated use of this mapping much more usable\r\n- Corrected some comparisons which should be case-sensitive but may not be in some vim configurations\r\n","package":"selx.tar.gz","4":"selx.tar.gz","src_id":"28018","5":"28018","creation_date":"1651029953","6":"1651029953"},{"0":"5875","vim_version":"7.0","1":"7.0","script_version":"15\/06\/21","2":"15\/06\/21","version_comment":"- Oops! Fixed incorrect command-line feedback\/reporting of case toggle mapping\r\n 'cH' (the actual operation is\/was correct)\r\n","3":"- Oops! Fixed incorrect command-line feedback\/reporting of case toggle mapping\r\n 'cH' (the actual operation is\/was correct)\r\n","package":"selx.tar.gz","4":"selx.tar.gz","src_id":"27633","5":"27633","creation_date":"1623801046","6":"1623801046"},{"0":"5875","vim_version":"7.0","1":"7.0","script_version":"04\/06\/21","2":"04\/06\/21","version_comment":"- Added commands to copy and paste highlight config between tabs\r\n- Improved feedback text on command line for some commands\/mappings","3":"- Added commands to copy and paste highlight config between tabs\r\n- Improved feedback text on command line for some commands\/mappings","package":"selx.tar.gz","4":"selx.tar.gz","src_id":"27623","5":"27623","creation_date":"1622846889","6":"1622846889"},{"0":"5875","vim_version":"7.0","1":"7.0","script_version":"01\/03\/21","2":"01\/03\/21","version_comment":"- README\/help text improvements\r\n- Changed the characters displayed in the Unicode version of the 'whole word' and 'case-insensitive' markers to something a bit more subtle (smaller)\r\n","3":"- README\/help text improvements\r\n- Changed the characters displayed in the Unicode version of the 'whole word' and 'case-insensitive' markers to something a bit more subtle (smaller)\r\n","package":"selx.tar.gz","4":"selx.tar.gz","src_id":"27506","5":"27506","creation_date":"1614657385","6":"1614657385"},{"0":"5875","vim_version":"7.0","1":"7.0","script_version":"27\/02\/21","2":"27\/02\/21","version_comment":"- Some minor improvements to this README and documentation\r\n- Added support for case selection\/toggling, inc new mappings toggling case-sensitivity, both default and per-selection - see the new mappings C and cH\r\n- Highlight Selection Map now shows markers to indicate word\/arbitrary selection and case-sensitivity for each highlight - see README for details\r\n","3":"- Some minor improvements to this README and documentation\r\n- Added support for case selection\/toggling, inc new mappings toggling case-sensitivity, both default and per-selection - see the new mappings C and cH\r\n- Highlight Selection Map now shows markers to indicate word\/arbitrary selection and case-sensitivity for each highlight - see README for details\r\n","package":"selx.tar.gz","4":"selx.tar.gz","src_id":"27502","5":"27502","creation_date":"1614470918","6":"1614470918"},{"0":"5875","vim_version":"7.0","1":"7.0","script_version":"24\/11\/20","2":"24\/11\/20","version_comment":"- Improved feedback for 'full word\/arbitrary' selection toggle operation\r\n- Added search success\/failure feedback; printed to command line\r\n- Minor comment corrections\r\n","3":"- Improved feedback for 'full word\/arbitrary' selection toggle operation\r\n- Added search success\/failure feedback; printed to command line\r\n- Minor comment corrections\r\n","package":"selx.tar.gz","4":"selx.tar.gz","src_id":"27385","5":"27385","creation_date":"1606288207","6":"1606288207"},{"0":"5875","vim_version":"7.0","1":"7.0","script_version":"27\/10\/2020","2":"27\/10\/2020","version_comment":"- Modified visual selection version of '*' so that it does not immediately jump to next occurrence; ie - works like the 'normal' version\r\n- Modified list of suggested highlight colours\r\n","3":"- Modified visual selection version of '*' so that it does not immediately jump to next occurrence; ie - works like the 'normal' version\r\n- Modified list of suggested highlight colours\r\n","package":"selx.tar.gz","4":"selx.tar.gz","src_id":"27377","5":"27377","creation_date":"1605931211","6":"1605931211"},{"0":"5875","vim_version":"7.0","1":"7.0","script_version":"01\/05\/20","2":"01\/05\/20","version_comment":"Added :SelXList command to print details of active selections\/highlights","3":"Added :SelXList command to print details of active selections\/highlights","package":"selx.tar.gz","4":"selx.tar.gz","src_id":"27142","5":"27142","creation_date":"1588359027","6":"1588359027"},{"0":"5875","vim_version":"7.0","1":"7.0","script_version":"27\/04\/20","2":"27\/04\/20","version_comment":"Added 'default' to setting StatusMsg colour. Without this, colour override would be hit-and-miss\r\nRemoved a stray mapping for '*' from autoload\/selx.vim - oops!\r\n","3":"Added 'default' to setting StatusMsg colour. Without this, colour override would be hit-and-miss\r\nRemoved a stray mapping for '*' from autoload\/selx.vim - oops!\r\n","package":"selx.tar.gz","4":"selx.tar.gz","src_id":"27137","5":"27137","creation_date":"1588057457","6":"1588057457"},{"0":"5875","vim_version":"7.0","1":"7.0","script_version":"26\/04\/20","2":"26\/04\/20","version_comment":"Documentation improvements.\r\nMinor functional changes - nothing serious, but worth having\r\nSee version information at bottom of README for full details","3":"Documentation improvements.\r\nMinor functional changes - nothing serious, but worth having\r\nSee version information at bottom of README for full details","package":"selx.tar.gz","4":"selx.tar.gz","src_id":"27136","5":"27136","creation_date":"1588009914","6":"1588009914"},{"0":"5875","vim_version":"7.0","1":"7.0","script_version":"25\/04\/20","2":"25\/04\/20","version_comment":"Documentation improvements. Improved control over mappings. Corrected one use of 'normal' to 'normal!'","3":"Documentation improvements. Improved control over mappings. Corrected one use of 'normal' to 'normal!'","package":"selx.tar.gz","4":"selx.tar.gz","src_id":"27130","5":"27130","creation_date":"1587839288","6":"1587839288"}]},"5874":{"script_id":"5874","0":"5874","script_name":"SessX","1":"SessX","script_type":"utility","2":"utility","summary":"Simple session management","3":"Simple session management","description":"INTRODUCTION\r\n\r\nSessX defines some simple, but very useful, enhancements to the standard session operation. Includes support for saving and restoring the `SelX` plugin status - #vimscript #5875\r\n\r\nNOTE: I really have no idea what the minimum vim version requirement is to run SessX and I don't know of a practical way of finding out (I've only used it on v8.2). The best I can suggest is to try it; it will probably work and if it doesn't then let me know and I'll see if I can sort it\r\n\r\n*** If you have any suggestions for improving this, then please let me know. If you think it's rubbish then PLEASE let me know why - it's far more useful than just 'voting it down' (which really doesn't help at all). Contact details are in the top of the README file ***\r\n\r\nBASIC CONCEPTS\r\n\r\nSessX uses the normal vim session facility; it doesn't replace it or subvert it any way - it just makes it a little more convenient to use. If no session is in force then SessX will not interfere\r\n\r\nSessX makes sure that you always save your session files in the editor's startup directory so that you can easily find them again later. To make best use of this, start vim from the root of the source tree you are working with\r\n\r\nYou can easily give your session a unique name, and change it whenever you want, and SessX also reminds you to save your session on exiting vim\r\n\r\nIf you are using the SelX plugin, then SessX shall also save the SelX selection\/highlight configuration too\r\n\r\nIn normal vim fashion, you can reload the session when you start vim with `vim -S {filename}` where `{filename}` defaults to `Session.vim` if not specified\r\n","4":"INTRODUCTION\r\n\r\nSessX defines some simple, but very useful, enhancements to the standard session operation. Includes support for saving and restoring the `SelX` plugin status - #vimscript #5875\r\n\r\nNOTE: I really have no idea what the minimum vim version requirement is to run SessX and I don't know of a practical way of finding out (I've only used it on v8.2). The best I can suggest is to try it; it will probably work and if it doesn't then let me know and I'll see if I can sort it\r\n\r\n*** If you have any suggestions for improving this, then please let me know. If you think it's rubbish then PLEASE let me know why - it's far more useful than just 'voting it down' (which really doesn't help at all). Contact details are in the top of the README file ***\r\n\r\nBASIC CONCEPTS\r\n\r\nSessX uses the normal vim session facility; it doesn't replace it or subvert it any way - it just makes it a little more convenient to use. If no session is in force then SessX will not interfere\r\n\r\nSessX makes sure that you always save your session files in the editor's startup directory so that you can easily find them again later. To make best use of this, start vim from the root of the source tree you are working with\r\n\r\nYou can easily give your session a unique name, and change it whenever you want, and SessX also reminds you to save your session on exiting vim\r\n\r\nIf you are using the SelX plugin, then SessX shall also save the SelX selection\/highlight configuration too\r\n\r\nIn normal vim fashion, you can reload the session when you start vim with `vim -S {filename}` where `{filename}` defaults to `Session.vim` if not specified\r\n","install_details":"Just un-tar into ~\/.vim\/bundle\/ as usual and read the README file for config options","5":"Just un-tar into ~\/.vim\/bundle\/ as usual and read the README file for config options","first_name":"Richard","6":"Richard","last_name":"Bentley-Green","7":"Bentley-Green","releases":[{"0":"5874","vim_version":"7.0","1":"7.0","script_version":"10\/03\/2022","2":"10\/03\/2022","version_comment":"The 'MKS {name}' command now accepts '.' as the `name` to explicitly specify the default session name \"Session.vim\". Prior to this, once a non-default name had been specified, it was not possible to revert back to the default name\r\n","3":"The 'MKS {name}' command now accepts '.' as the `name` to explicitly specify the default session name \"Session.vim\". Prior to this, once a non-default name had been specified, it was not possible to revert back to the default name\r\n","package":"sessx.tar.gz","4":"sessx.tar.gz","src_id":"27970","5":"27970","creation_date":"1648511097","6":"1648511097"},{"0":"5874","vim_version":"7.0","1":"7.0","script_version":"17\/11\/2020","2":"17\/11\/2020","version_comment":"- Corrected variable use in SaveSession() - was non-local","3":"- Corrected variable use in SaveSession() - was non-local","package":"sessx.tar.gz","4":"sessx.tar.gz","src_id":"27378","5":"27378","creation_date":"1605931368","6":"1605931368"},{"0":"5874","vim_version":"7.0","1":"7.0","script_version":"27\/04\/20","2":"27\/04\/20","version_comment":"Added MKSInfo command\r\nAdded 'default' to setting StatusMsg colour. Without this, colour override would be hit-and-miss","3":"Added MKSInfo command\r\nAdded 'default' to setting StatusMsg colour. Without this, colour override would be hit-and-miss","package":"sessx.tar.gz","4":"sessx.tar.gz","src_id":"27138","5":"27138","creation_date":"1588057542","6":"1588057542"},{"0":"5874","vim_version":"7.0","1":"7.0","script_version":"26\/04\/20","2":"26\/04\/20","version_comment":"Documentation improvements (no code changes)","3":"Documentation improvements (no code changes)","package":"sessx.tar.gz","4":"sessx.tar.gz","src_id":"27135","5":"27135","creation_date":"1588009736","6":"1588009736"}]},"5873":{"script_id":"5873","0":"5873","script_name":"painless-digraph","1":"painless-digraph","script_type":"utility","2":"utility","summary":"Enter a sequence of digraphs with ease! ","3":"Enter a sequence of digraphs with ease! ","description":"# Intro\r\n\r\nVim digraphs provide a useful mechanism to enter special characters normally\r\nnot found on a keyboard. But since the methods to enter digraphs require\r\nadditional keypresses, it becomes tedious to input sequences or short phrases\r\n(e.g. in hiragana, katakana or greek).\r\nThe *painless-digraph* plugin relieves you from this pain and provides a\r\ndigraph-mode which allows you to enter digraphs directly, without additional\r\nkeypresses.\r\nYou can post issues at https:\/\/github.com\/DrCracket\/painless-digraph\r\n\r\n# Mappings\r\n\r\n## Internal Mappings\r\n\r\n### \\(PainlessdigraphEnable)\r\n\r\nThis internal mapping enables the painless-digraph functionality. After calling\r\nthis mapping you can e.g. write `kon5nitiwa` to get the hiragana `こんにちわ`.\r\n\r\n### \\(PainlessdigraphDisable)\r\n\r\nDisables the painless-digraph digraph-mode.\r\n\r\n### \\(PainlessdigraphToggle)\r\n\r\nToggles the painless-digraph digraph-mode.\r\n\r\n## Default Mappings\r\n\r\nThe default mappings of this plugin are as follows: \r\n```vim\r\n map de (PainlessdigraphEnable)\r\n map dd (PainlessdigraphDisable)\r\n map dt (PainlessdigraphToggle)\r\n```\r\nTo change them just put your desired mappings in your vimrc.","4":"# Intro\r\n\r\nVim digraphs provide a useful mechanism to enter special characters normally\r\nnot found on a keyboard. But since the methods to enter digraphs require\r\nadditional keypresses, it becomes tedious to input sequences or short phrases\r\n(e.g. in hiragana, katakana or greek).\r\nThe *painless-digraph* plugin relieves you from this pain and provides a\r\ndigraph-mode which allows you to enter digraphs directly, without additional\r\nkeypresses.\r\nYou can post issues at https:\/\/github.com\/DrCracket\/painless-digraph\r\n\r\n# Mappings\r\n\r\n## Internal Mappings\r\n\r\n### \\(PainlessdigraphEnable)\r\n\r\nThis internal mapping enables the painless-digraph functionality. After calling\r\nthis mapping you can e.g. write `kon5nitiwa` to get the hiragana `こんにちわ`.\r\n\r\n### \\(PainlessdigraphDisable)\r\n\r\nDisables the painless-digraph digraph-mode.\r\n\r\n### \\(PainlessdigraphToggle)\r\n\r\nToggles the painless-digraph digraph-mode.\r\n\r\n## Default Mappings\r\n\r\nThe default mappings of this plugin are as follows: \r\n```vim\r\n map de (PainlessdigraphEnable)\r\n map dd (PainlessdigraphDisable)\r\n map dt (PainlessdigraphToggle)\r\n```\r\nTo change them just put your desired mappings in your vimrc.","install_details":"You can install this plugin using any vim plugin manager by using the path on\r\nGitHub for this repository. For vim-plug just add the following:\r\n\r\n```vim\r\nPlug 'DrCracket\/painless-digraph'\r\n```\r\n","5":"You can install this plugin using any vim plugin manager by using the path on\r\nGitHub for this repository. For vim-plug just add the following:\r\n\r\n```vim\r\nPlug 'DrCracket\/painless-digraph'\r\n```\r\n","first_name":"Jonas","6":"Jonas","last_name":"B","7":"B","releases":[{"0":"5873","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"painless-digraph.zip","4":"painless-digraph.zip","src_id":"27124","5":"27124","creation_date":"1587492954","6":"1587492954"}]},"5872":{"script_id":"5872","0":"5872","script_name":"vim-macaw","1":"vim-macaw","script_type":"color scheme","2":"color scheme","summary":"A colorscheme editor for terminal vim","3":"A colorscheme editor for terminal vim","description":"Macaw is a tool to interactively change colors in vim\/nvim terminal. It aims to streamline the process of designing and tweaking terminal vim colorschemes.\r\n\r\nFor more details, see https:\/\/github.com\/urbainvaes\/vim-macaw and :help macaw.","4":"Macaw is a tool to interactively change colors in vim\/nvim terminal. It aims to streamline the process of designing and tweaking terminal vim colorschemes.\r\n\r\nFor more details, see https:\/\/github.com\/urbainvaes\/vim-macaw and :help macaw.","install_details":"","5":"","first_name":"Urbain","6":"Urbain","last_name":"Vaes","7":"Vaes","releases":[{"0":"5872","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"vim-macaw-0.1.tar","4":"vim-macaw-0.1.tar","src_id":"27117","5":"27117","creation_date":"1586889011","6":"1586889011"}]},"5871":{"script_id":"5871","0":"5871","script_name":"vim-ripple","1":"vim-ripple","script_type":"utility","2":"utility","summary":"Minimalist plugin to interact with a REPL","3":"Minimalist plugin to interact with a REPL","description":"This thin plugin makes it easy to send code to a REPL (read-evaluate-print loop) running within vim or nvim.\r\n\r\nFor a more detailed description, see https:\/\/github.com\/urbainvaes\/vim-ripple","4":"This thin plugin makes it easy to send code to a REPL (read-evaluate-print loop) running within vim or nvim.\r\n\r\nFor a more detailed description, see https:\/\/github.com\/urbainvaes\/vim-ripple","install_details":"","5":"","first_name":"Urbain","6":"Urbain","last_name":"Vaes","7":"Vaes","releases":[{"0":"5871","vim_version":"8.0","1":"8.0","script_version":"0.3","2":"0.3","version_comment":"- Distinguish between isolated (specific to buffer) and common (specific to filetype) REPLs;\r\n- Enable prepending `yr` and `yp` with `\"here<\/a> for details. Default: 0\r\n- 'g:yoinkAutoFormatPaste' - When set to 1, after a paste occurs it will automatically be formatted (using '=' key). Default: 0. Note that you can also leave this off and use the toggle key instead for cases where you want to format after the paste.\r\n- 'g:yoinkMoveCursorToEndOfPaste' - When set to 1, the cursor will always be placed at the end of the paste. Default is 0 which will match normal Vim behaviour and place the cursor at the beginning when pasting multiline yanks. Setting to 1 can be nicer because it makes the post-paste cursor position more consistent between multiline and non-multiline pastes (that is, the cursor will be at the end in both cases). And also causes consecutive multiline pastes to be ordered correctly instead of interleaved together.\r\n- 'g:yoinkSwapClampAtEnds' - When set to '1', when we reach the beginning or end of the yank history, the swap will stop there. When set to '0', it will cycle back to the other end of the history so you can swap in the same direction forever. Default: '1'\r\n- 'g:yoinkIncludeNamedRegisters' - When set to '1', all yanks for all registers will be included in the history. When set to '0', only changes to the default register will be recorded. Default: '1'\r\n- 'g:yoinkSyncSystemClipboardOnFocus' - When set to '0', the System Clipboard feature described below will be disabled. Default: '1'\r\n\r\nPERSISTENT HISTORY\t\t\t\t\t'yoink-persistent-history'\r\n\r\nWhen 'g:yoinkSavePersistently' is set to 1, the yank history will be saved persistently by taking advantage of Neovim's \"ShaDa\" feature. Note that since ShaDa support only exists in Neovim this feature is not available for Vim.\r\n\r\nYou can also use this feature to sync the yank history across multiple running instances of Vim by updating Neovim's shada file. For example, if you execute ':wshada' in the first instance and then ':rshada' in the second instance, the second instance will be synced with the yank history in the first instance. If this becomes a common operation you might consider using key bindings for this.\r\n\r\nNote also that the ! option must be added to Neovims 'shada' setting for this feature to work. For example: \"set shada=!,'100,<50,s10,h\"\r\n\r\nSYSTEM CLIPBOARD SYNC\t\t\t\t\t'yoink-system-clipboard-sync'\r\n\r\nAnother feature worth mentioning is that if you have 'clipboard' set to either 'unnamed' or 'unnamedplus' then Yoink will automatically record yanks that occur outside of Vim. It does this by checking if the system clipboard was changed every time Vim gains focus and if so adding the new yank to the history.\r\n\r\nNote that if you don't like this behaviour you can disable it by setting 'g:yoinkSyncSystemClipboardOnFocus' to 0\r\n\r\nCUTLASS INTEGRATION\t\t\t\t\t'yoink-cutlass-integration'\r\n\r\nIf you also have vim-cutlass (https:\/\/github.com\/svermeulen\/vim-cutlass) installed then I suggest you set 'g:yoinkIncludeDeleteOperations' to 1. Otherwise the 'cut' operator that you use will not be added to the yank history.\r\n\r\nFAQ\t\t\t\t\t'yoink-faq'\r\n\r\n- 'I want the yank history in the autocomplete list'\r\n\r\nIf you're using ncm2 (https:\/\/github.com\/ncm2\/ncm2) for autocomplete you can use this (https:\/\/github.com\/svermeulen\/ncm2-yoink). If you're using something else please create a github issue and we can look at adding a source for that\r\n\r\n- 'I want to rotate to a specific number in the :Yanks list. How do I do this?'\r\n\r\nJust pass a count to the '[y' command. For example, to rotate to yank #12 as displayed in the ':Yanks' list, execute '12[y'\r\n\r\n- 'I want to add to the yank history manually from my own vimscript'\r\n\r\nYou can call 'yoink#manualYank' for this. Note that calling this will also set the contents of the default register with the given value. If you just want to add to history without affecting the default register, you can call 'yoink#addTextToHistory' instead\r\n\r\n","4":"See github repo for latest updates: https:\/\/github.com\/svermeulen\/vim-yoink\r\n\r\n\r\nINTRODUCTION 'yoink'\r\n\r\nYoink will automatically maintain a history of yanks that you can choose between when pasting.\r\n\r\nIt provides very similar functionality to nvim-miniyank (https:\/\/github.com\/bfredl\/nvim-miniyank), YankRing.vim (https:\/\/github.com\/vim-scripts\/YankRing.vim), vim-yankstack (https:\/\/github.com\/maxbrunsfeld\/vim-yankstack) or the yank features in vim-easyclip (https:\/\/github.com\/svermeulen\/vim-easyclip).\r\n\r\nMAPPINGS\t\t\t\t\t'yoink-mappings'\r\n\r\nNote that by default Yoink will not affect the way Vim behaves in any way. You have to add one or more of the following maps or enable one of the optional settings to produce an effect.\r\n\r\nFor example, if you want to add a key to swap the most recent paste around in the yank history:\r\n\r\n nmap (YoinkPostPasteSwapBack)\r\n nmap (YoinkPostPasteSwapForward)\r\n\r\n nmap p (YoinkPaste_p)\r\n nmap P (YoinkPaste_P)\r\n\r\nWith these mappings, immediately after performing a paste, you can cycle through the history by hitting and \r\n\r\nWe also need to override the 'p' and 'P' keys to notify Yoink that a paste has occurred, so that swapping via the and keys can be enabled. Otherwise paste functionality should be the same as default.\r\n\r\nNote that yoink does not support swapping when doing paste in visual mode and so we do not add an 'xmap' for 'p' here. However, the vim-subversive (https:\/\/github.com\/svermeulen\/vim-subversive) plugin integrates with Yoink and does provide that functionality.\r\n\r\nNote that the swap operations above will only affect the current paste and the history order will be unchanged. However - if you do want to permanently cycle through the history, you can do that too:\r\n\r\n nmap [y (YoinkRotateBack)\r\n nmap ]y (YoinkRotateForward)\r\n\r\nNow when you hit [y or ]y the current yank will change and you will see a preview of it in the status bar\r\n\r\nYou might also want to add a map for toggling whether the current paste is formatted or not:\r\n\r\n nmap (YoinkPostPasteToggleFormat)\r\n\r\nNow, hitting after a paste will toggle between formatted and unformatted (equivalent to using the '=' key). By default pastes will not be formatted until you toggle it afterwards using (however you can also change this with the 'yoinkAutoFormatPaste' setting as described below)\r\n\r\nFinally, you can also optionally add the following map:\r\n\r\n nmap y (YoinkYankPreserveCursorPosition)\r\n xmap y (YoinkYankPreserveCursorPosition)\r\n\r\nAfter adding this map, yank will function exactly the same as previously with the one difference being that the cursor position will not change after performing a yank. This can be more useful especially when yanking a large text object such as a paragraph.\r\n\r\nCOMMANDS\t\t\t\t\t'yoink-commands'\r\n\r\n':Yanks' - Display the current yank history\r\n\r\n':ClearYanks' - Delete history. This will reduce the history down to 1 entry taken from the default register.\r\n\r\nSETTINGS\t\t\t\t\t'yoink-settings'\r\n\r\nYou can optionally override the default behaviour with the following settings:\r\n\r\n- 'g:yoinkMaxItems' - History size. Default: 10.\r\n- 'g:yoinkSyncNumberedRegisters' - When set to 1, every time the yank history changes the numbered registers 1 - 9 will be updated to sync with the first 9 entries in the yank history. See this article (http:\/\/vimcasts.org\/blog\/2013\/11\/registers-the-good-the-bad-and-the-ugly-parts\/) for an explanation of why we would want do do this. Default: 0.\r\n- 'g:yoinkIncludeDeleteOperations' - When set to 1, delete operations such as 'x' or 'd' or 's' will also be added to the yank history. Default: 0\r\n- 'g:yoinkSavePersistently' - When set to 1, the yank history will be saved persistently across sessions of Vim. Note: Requires Neovim. See here<\/a> for details. Default: 0\r\n- 'g:yoinkAutoFormatPaste' - When set to 1, after a paste occurs it will automatically be formatted (using '=' key). Default: 0. Note that you can also leave this off and use the toggle key instead for cases where you want to format after the paste.\r\n- 'g:yoinkMoveCursorToEndOfPaste' - When set to 1, the cursor will always be placed at the end of the paste. Default is 0 which will match normal Vim behaviour and place the cursor at the beginning when pasting multiline yanks. Setting to 1 can be nicer because it makes the post-paste cursor position more consistent between multiline and non-multiline pastes (that is, the cursor will be at the end in both cases). And also causes consecutive multiline pastes to be ordered correctly instead of interleaved together.\r\n- 'g:yoinkSwapClampAtEnds' - When set to '1', when we reach the beginning or end of the yank history, the swap will stop there. When set to '0', it will cycle back to the other end of the history so you can swap in the same direction forever. Default: '1'\r\n- 'g:yoinkIncludeNamedRegisters' - When set to '1', all yanks for all registers will be included in the history. When set to '0', only changes to the default register will be recorded. Default: '1'\r\n- 'g:yoinkSyncSystemClipboardOnFocus' - When set to '0', the System Clipboard feature described below will be disabled. Default: '1'\r\n\r\nPERSISTENT HISTORY\t\t\t\t\t'yoink-persistent-history'\r\n\r\nWhen 'g:yoinkSavePersistently' is set to 1, the yank history will be saved persistently by taking advantage of Neovim's \"ShaDa\" feature. Note that since ShaDa support only exists in Neovim this feature is not available for Vim.\r\n\r\nYou can also use this feature to sync the yank history across multiple running instances of Vim by updating Neovim's shada file. For example, if you execute ':wshada' in the first instance and then ':rshada' in the second instance, the second instance will be synced with the yank history in the first instance. If this becomes a common operation you might consider using key bindings for this.\r\n\r\nNote also that the ! option must be added to Neovims 'shada' setting for this feature to work. For example: \"set shada=!,'100,<50,s10,h\"\r\n\r\nSYSTEM CLIPBOARD SYNC\t\t\t\t\t'yoink-system-clipboard-sync'\r\n\r\nAnother feature worth mentioning is that if you have 'clipboard' set to either 'unnamed' or 'unnamedplus' then Yoink will automatically record yanks that occur outside of Vim. It does this by checking if the system clipboard was changed every time Vim gains focus and if so adding the new yank to the history.\r\n\r\nNote that if you don't like this behaviour you can disable it by setting 'g:yoinkSyncSystemClipboardOnFocus' to 0\r\n\r\nCUTLASS INTEGRATION\t\t\t\t\t'yoink-cutlass-integration'\r\n\r\nIf you also have vim-cutlass (https:\/\/github.com\/svermeulen\/vim-cutlass) installed then I suggest you set 'g:yoinkIncludeDeleteOperations' to 1. Otherwise the 'cut' operator that you use will not be added to the yank history.\r\n\r\nFAQ\t\t\t\t\t'yoink-faq'\r\n\r\n- 'I want the yank history in the autocomplete list'\r\n\r\nIf you're using ncm2 (https:\/\/github.com\/ncm2\/ncm2) for autocomplete you can use this (https:\/\/github.com\/svermeulen\/ncm2-yoink). If you're using something else please create a github issue and we can look at adding a source for that\r\n\r\n- 'I want to rotate to a specific number in the :Yanks list. How do I do this?'\r\n\r\nJust pass a count to the '[y' command. For example, to rotate to yank #12 as displayed in the ':Yanks' list, execute '12[y'\r\n\r\n- 'I want to add to the yank history manually from my own vimscript'\r\n\r\nYou can call 'yoink#manualYank' for this. Note that calling this will also set the contents of the default register with the given value. If you just want to add to history without affecting the default register, you can call 'yoink#addTextToHistory' instead\r\n\r\n","install_details":"","5":"","first_name":"Steve","6":"Steve","last_name":"Vermeulen","7":"Vermeulen","releases":[{"0":"5761","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"vim-yoink.zip","4":"vim-yoink.zip","src_id":"26318","5":"26318","creation_date":"1546664167","6":"1546664167"}]},"5760":{"script_id":"5760","0":"5760","script_name":"vim-rzip","1":"vim-rzip","script_type":"utility","2":"utility","summary":"Extends stock zip.vim to allow recursively browsing and writing zip files","3":"Extends stock zip.vim to allow recursively browsing and writing zip files","description":"https:\/\/github.com\/lbrayner\/vim-rzip\r\n\r\nExtends stock zipPlugin.vim to allow recursively browsing and writing\r\nzip files.\r\n\r\nVimL and system calls only (zip, unzip and copy file).\r\n\r\nREQUIREMENTS\r\n\r\n- Vim 7.4✝ or Neovim 0.1.7.\r\n\r\n✝ Confirmed working on Vim 7.4-1024 for Windows.\r\n\r\n\r\nTo browse\r\n\r\nIn $PATH:\r\n\r\n- an unzip compatible command.\r\n\r\n\r\nTo write\r\n\r\nIn $PATH:\r\n\r\n- a zip compatible command.\r\n\r\nCONFIGURATION\r\n\r\nExtra file extensions can be added with g:rzipPlugin_extra_ext. For\r\nexample:\r\n\r\n let g:rzipPlugin_extra_ext = '*.odt,*.mfh'\r\n","4":"https:\/\/github.com\/lbrayner\/vim-rzip\r\n\r\nExtends stock zipPlugin.vim to allow recursively browsing and writing\r\nzip files.\r\n\r\nVimL and system calls only (zip, unzip and copy file).\r\n\r\nREQUIREMENTS\r\n\r\n- Vim 7.4✝ or Neovim 0.1.7.\r\n\r\n✝ Confirmed working on Vim 7.4-1024 for Windows.\r\n\r\n\r\nTo browse\r\n\r\nIn $PATH:\r\n\r\n- an unzip compatible command.\r\n\r\n\r\nTo write\r\n\r\nIn $PATH:\r\n\r\n- a zip compatible command.\r\n\r\nCONFIGURATION\r\n\r\nExtra file extensions can be added with g:rzipPlugin_extra_ext. For\r\nexample:\r\n\r\n let g:rzipPlugin_extra_ext = '*.odt,*.mfh'\r\n","install_details":"Vim 8.0+ (+packages)\r\n\r\nIf you\u00e2\u0080\u0099re using Vim 8.0 or greater (if :echo has(\"packages\") returns 1),\r\nyou can add vim-rzip as a package.\r\n\r\nWhen you\u00e2\u0080\u0099re done with the following steps make sure to read about\r\npackages: :h packages.\r\n\r\n- If your .vim folder is NOT a git repository:\r\n\r\n $ mkdir -p ~\/.vim\/pack\/bundle\/start\/vim-rzip\r\n $ unzip ~\/Downloads\/vim-rzip.zip -d ~\/.vim\/pack\/bundle\/start\/vim-rzip\r\n\r\nOr you can clone the *Git* repository:\r\n\r\n $ mkdir -p ~\/.vim\/pack\/bundle\/start\r\n $ cd ~\/.vim\/pack\/bundle\/start\r\n start $ git clone 'https:\/\/github.com\/lbrayner\/vim-rzip'\r\n\r\n- If your .vim folder IS a git repository:\r\n\r\n $ mkdir -p ~\/.vim\/pack\/bundle\/start\r\n $ cd ~\/.vim\r\n .vim $ git submodule add 'https:\/\/github.com\/lbrayner\/vim-rzip' pack\/bundle\/start\/vim-rzip\r\n\r\nThis will install vim-rzip as a git submodule.\r\n\r\n\r\nPlugin manager\r\n\r\nEither vim-pathogen or Vundle are recommended.\r\n\r\n\r\nVerifying the installation\r\n\r\nWhen you open a file with any of these extensions (per default) \u00e2\u0080\u0094\r\n.apk, .celzip, .crtx, .docm, .docx, .dotm, .dotx, .ear,\r\n.epub, .gcsx, .glox, .gqsx, .ja, .jar, .kmz, .oxt,\r\n.potm, .potx, .ppam, .ppsm, .ppsx, .pptm, .pptx, .sldx,\r\n.thmx, .vdw, .war, .wsz, .xap, .xlam, .xlam, .xlsb,\r\n.xlsm, .xlsx, .xltm, .xltx, .xpi, .zip \u00e2\u0080\u0094 you\u00e2\u0080\u0099ll see the\r\ndefault zipPlugin.vim message, except that:\r\nthe plugin name is *rzip.vim*; and the version, on the first line, should read\r\nsomething like *v014*.\r\n\r\nSimplest method\r\n\r\nJust unzip to your .vim folder.\r\n\r\nYou can unzip anywhere in the RUNTIMEPATH really (as long as it comes before $VIMRUNTIME).","5":"Vim 8.0+ (+packages)\r\n\r\nIf you\u00e2\u0080\u0099re using Vim 8.0 or greater (if :echo has(\"packages\") returns 1),\r\nyou can add vim-rzip as a package.\r\n\r\nWhen you\u00e2\u0080\u0099re done with the following steps make sure to read about\r\npackages: :h packages.\r\n\r\n- If your .vim folder is NOT a git repository:\r\n\r\n $ mkdir -p ~\/.vim\/pack\/bundle\/start\/vim-rzip\r\n $ unzip ~\/Downloads\/vim-rzip.zip -d ~\/.vim\/pack\/bundle\/start\/vim-rzip\r\n\r\nOr you can clone the *Git* repository:\r\n\r\n $ mkdir -p ~\/.vim\/pack\/bundle\/start\r\n $ cd ~\/.vim\/pack\/bundle\/start\r\n start $ git clone 'https:\/\/github.com\/lbrayner\/vim-rzip'\r\n\r\n- If your .vim folder IS a git repository:\r\n\r\n $ mkdir -p ~\/.vim\/pack\/bundle\/start\r\n $ cd ~\/.vim\r\n .vim $ git submodule add 'https:\/\/github.com\/lbrayner\/vim-rzip' pack\/bundle\/start\/vim-rzip\r\n\r\nThis will install vim-rzip as a git submodule.\r\n\r\n\r\nPlugin manager\r\n\r\nEither vim-pathogen or Vundle are recommended.\r\n\r\n\r\nVerifying the installation\r\n\r\nWhen you open a file with any of these extensions (per default) \u00e2\u0080\u0094\r\n.apk, .celzip, .crtx, .docm, .docx, .dotm, .dotx, .ear,\r\n.epub, .gcsx, .glox, .gqsx, .ja, .jar, .kmz, .oxt,\r\n.potm, .potx, .ppam, .ppsm, .ppsx, .pptm, .pptx, .sldx,\r\n.thmx, .vdw, .war, .wsz, .xap, .xlam, .xlam, .xlsb,\r\n.xlsm, .xlsx, .xltm, .xltx, .xpi, .zip \u00e2\u0080\u0094 you\u00e2\u0080\u0099ll see the\r\ndefault zipPlugin.vim message, except that:\r\nthe plugin name is *rzip.vim*; and the version, on the first line, should read\r\nsomething like *v014*.\r\n\r\nSimplest method\r\n\r\nJust unzip to your .vim folder.\r\n\r\nYou can unzip anywhere in the RUNTIMEPATH really (as long as it comes before $VIMRUNTIME).","first_name":"LEONARDO","6":"LEONARDO","last_name":"Brayner e SILVA","7":"Brayner e SILVA","releases":[{"0":"5760","vim_version":"7.4","1":"7.4","script_version":"0.1.5","2":"0.1.5","version_comment":"Based on v28 with URI scheme fix present in v32\r\n\r\nChanges present in Neovim 0.6.1 (from 0.5.0) brought about this\r\nrestructuring. Builtin functions such as expand and bufname had their\r\nbehavior modified, which is probably related to the URI scheme fix\r\npresent in v32.\r\n\r\nTo prevent future surprises, vim-rzip is now based on zip.vim v28.","3":"Based on v28 with URI scheme fix present in v32\r\n\r\nChanges present in Neovim 0.6.1 (from 0.5.0) brought about this\r\nrestructuring. Builtin functions such as expand and bufname had their\r\nbehavior modified, which is probably related to the URI scheme fix\r\npresent in v32.\r\n\r\nTo prevent future surprises, vim-rzip is now based on zip.vim v28.","package":"vim-rzip.zip","4":"vim-rzip.zip","src_id":"27951","5":"27951","creation_date":"1645240002","6":"1645240002"},{"0":"5760","vim_version":"7.4","1":"7.4","script_version":"0.1.3","2":"0.1.3","version_comment":"Fixes bug in netrw integration when browse windows are closed.","3":"Fixes bug in netrw integration when browse windows are closed.","package":"vim-rzip.zip","4":"vim-rzip.zip","src_id":"27662","5":"27662","creation_date":"1626917931","6":"1626917931"},{"0":"5760","vim_version":"7.4","1":"7.4","script_version":"0.1.2","2":"0.1.2","version_comment":"'bufhidden' set to wipe & fixed a URI related bug\r\n\r\nAvoided an error when trying to obtain a buffer variable from the alternate buffer after trying to edit a zipfile: URI directly.\r\n","3":"'bufhidden' set to wipe & fixed a URI related bug\r\n\r\nAvoided an error when trying to obtain a buffer variable from the alternate buffer after trying to edit a zipfile: URI directly.\r\n","package":"vim-rzip.zip","4":"vim-rzip.zip","src_id":"27659","5":"27659","creation_date":"1626731116","6":"1626731116"},{"0":"5760","vim_version":"7.0","1":"7.0","script_version":"0.1.1","2":"0.1.1","version_comment":"Fixed a unix file name issue: unzip special characters *,? and square brackets (][).","3":"Fixed a unix file name issue: unzip special characters *,? and square brackets (][).","package":"vim-rzip.zip","4":"vim-rzip.zip","src_id":"27197","5":"27197","creation_date":"1591615706","6":"1591615706"},{"0":"5760","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"vim-rzip.zip","4":"vim-rzip.zip","src_id":"26314","5":"26314","creation_date":"1546416539","6":"1546416539"}]},"5759":{"script_id":"5759","0":"5759","script_name":"vertical_region.vim","1":"vertical_region.vim","script_type":"utility","2":"utility","summary":"Move to lines bounding a vertical indent region","3":"Move to lines bounding a vertical indent region","description":"This plugin provides mapping targets to move up or down to lines that have non-space characters before or in the current column, usually to find lines that begin or end blocks in languages where indenting is used to show or specify structure.\r\n\r\nhttps:\/\/dev.sanctum.geek.nz\/cgit\/vim-vertical-region.git\/","4":"This plugin provides mapping targets to move up or down to lines that have non-space characters before or in the current column, usually to find lines that begin or end blocks in languages where indenting is used to show or specify structure.\r\n\r\nhttps:\/\/dev.sanctum.geek.nz\/cgit\/vim-vertical-region.git\/","install_details":"Drop plugin\/vertical_region.vim in your ~\/.vim\/plugin directory, and autoload\/vertical_region.vim in ~\/.vim\/autoload. Add doc\/vertical_region.txt in ~\/.vim\/doc if you want the help file. Otherwise, use your favourite Vim plugin package manager.\r\n\r\nThere are no default key mappings; you should define those yourself in your vimrc. Here are the author's choices, using \\{ and \\} in all three modes:\r\n\r\n nmap { (VerticalRegionUp)\r\n nmap } (VerticalRegionDown)\r\n omap { (VerticalRegionUp)\r\n omap } (VerticalRegionDown) \r\n xmap { (VerticalRegionUp)\r\n xmap } (VerticalRegionDown)","5":"Drop plugin\/vertical_region.vim in your ~\/.vim\/plugin directory, and autoload\/vertical_region.vim in ~\/.vim\/autoload. Add doc\/vertical_region.txt in ~\/.vim\/doc if you want the help file. Otherwise, use your favourite Vim plugin package manager.\r\n\r\nThere are no default key mappings; you should define those yourself in your vimrc. Here are the author's choices, using \\{ and \\} in all three modes:\r\n\r\n nmap { (VerticalRegionUp)\r\n nmap } (VerticalRegionDown)\r\n omap { (VerticalRegionUp)\r\n omap } (VerticalRegionDown) \r\n xmap { (VerticalRegionUp)\r\n xmap } (VerticalRegionDown)","first_name":"Tom","6":"Tom","last_name":"Ryder","7":"Ryder","releases":[{"0":"5759","vim_version":"7.0","1":"7.0","script_version":"1.3.1","2":"1.3.1","version_comment":"Code and documentation refactoring and cleanup, no significant usage changes","3":"Code and documentation refactoring and cleanup, no significant usage changes","package":"vim-vertical-region-1.3.1.tar.gz","4":"vim-vertical-region-1.3.1.tar.gz","src_id":"27577","5":"27577","creation_date":"1619203146","6":"1619203146"}]},"5758":{"script_id":"5758","0":"5758","script_name":"vim-docvim","1":"vim-docvim","script_type":"syntax","2":"syntax","summary":"Syntax highlighting for Docvim comments","3":"Syntax highlighting for Docvim comments","description":"*docvim.txt* Syntax highlighting for docvim comments *docvim*\r\n\r\nCONTENTS *docvim-contents*\r\n\r\n1. Intro |docvim-intro|\r\n2. Installation |docvim-installation|\r\n3. Related |docvim-related|\r\n4. Website |docvim-website|\r\n5. License |docvim-license|\r\n6. Development |docvim-development|\r\n7. Authors |docvim-authors|\r\n8. History |docvim-history|\r\n\r\n\r\n *vim-docvim*\r\nINTRO *docvim-intro*\r\n\r\nvim-docvim provides additional syntax highlighting for Vim script files that\r\ncontain embedded docvim comments.\r\n\r\ndocvim (the tool, not this plug-in) is a documentation generator that\r\nprocesses those embedded comments and produces documentation in Markdown and\r\nVim \"help\" formats. To avoid confusion, this document refers to the Vim\r\nplug-in as \"vim-docvim\" and the separate generation tool as \"docvim\".\r\n\r\nINSTALLATION *docvim-installation*\r\n\r\nTo install vim-docvim, use your plug-in management system of choice.\r\n\r\nIf you don't have a \"plug-in management system of choice\", I recommend\r\nPathogen (https:\/\/github.com\/tpope\/vim-pathogen) due to its simplicity and\r\nrobustness. Assuming that you have Pathogen installed and configured, and\r\nthat you want to install vim-docvim into `~\/.vim\/bundle`, you can do so with:\r\n>\r\n git clone https:\/\/github.com\/wincent\/vim-docvim.git ~\/.vim\/bundle\/vim-docvim\r\n<\r\nAlternatively, if you use a Git submodule for each Vim plug-in, you could do\r\nthe following after `cd`-ing into the top-level of your Git superproject:\r\n>\r\n git submodule add https:\/\/github.com\/wincent\/vim-docvim.git ~\/vim\/bundle\/vim-docvim\r\n git submodule init\r\n<\r\nTo generate help tags under Pathogen, you can do so from inside Vim with:\r\n>\r\n :call pathogen#helptags()\r\n<\r\nRELATED *docvim-related*\r\n\r\nDocvim ~\r\n\r\nThe Docvim tool itself is a Haskell module, available at:\r\n\r\nhttp:\/\/hackage.haskell.org\/package\/docvim\r\n\r\nThe official source code repo is at:\r\n\r\nhttp:\/\/git.wincent.com\/docvim.git\r\n\r\nMirrors exist at:\r\n\r\n- https:\/\/github.com\/wincent\/docvim\r\n- https:\/\/gitlab.com\/wincent\/docvim\r\n- https:\/\/bitbucket.org\/ghurrell\/docvim\r\n\r\nWEBSITE *docvim-website*\r\n\r\nThe official vim-docvim source code repo is at:\r\n\r\nhttp:\/\/git.wincent.com\/vim-docvim.git\r\n\r\nMirrors exist at:\r\n\r\n- https:\/\/github.com\/wincent\/vim-docvim\r\n- https:\/\/gitlab.com\/wincent\/vim-docvim\r\n- https:\/\/bitbucket.org\/ghurrell\/vim-docvim\r\n\r\nOfficial releases are listed at:\r\n\r\nhttp:\/\/www.vim.org\/scripts\/script.php?script_id=5758\r\n\r\nLICENSE *docvim-license*\r\n\r\nCopyright (c) 2015-present Greg Hurrell\r\n\r\nPermission is hereby granted, free of charge, to any person obtaining a copy\r\nof this software and associated documentation files (the \"Software\"), to\r\ndeal in the Software without restriction, including without limitation the\r\nrights to use, copy, modify, merge, publish, distribute, sublicense, and\/or\r\nsell copies of the Software, and to permit persons to whom the Software is\r\nfurnished to do so, subject to the following conditions:\r\n\r\nThe above copyright notice and this permission notice shall be included in\r\nall copies or substantial portions of the Software.\r\n\r\nTHE SOFTWARE IS PROVIDED \"AS IS\", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR\r\nIMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,\r\nFITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE\r\nAUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER\r\nLIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING\r\nFROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS\r\nIN THE SOFTWARE.\r\n\r\nDEVELOPMENT *docvim-development*\r\n\r\nContributing patches ~\r\n\r\nPatches can be sent via mail to greg@hurrell.net, or as GitHub pull requests\r\nat: https:\/\/github.com\/wincent\/vim-docvim\/pulls\r\n\r\nCutting a new release ~\r\n\r\nAt the moment the release process is manual:\r\n\r\n- Perform final sanity checks and manual testing\r\n- Update the |docvim-history| section of the documentation\r\n- Verify clean work tree:\r\n>\r\n git status\r\n<\r\n- Tag the release:\r\n>\r\n git tag -s -m \"$VERSION release\" $VERSION\r\n<\r\n- Publish the code:\r\n>\r\n git push origin master --follow-tags\r\n git push github master --follow-tags\r\n<\r\n- Produce the release archive:\r\n>\r\n git archive -o vim-docvim-$VERSION.zip HEAD -- .\r\n<\r\n- Upload to http:\/\/www.vim.org\/scripts\/script.php?script_id=5758\r\n\r\nAUTHORS *docvim-authors*\r\n\r\nvim-docvim is written and maintained by Greg Hurrell .\r\n\r\n","4":"*docvim.txt* Syntax highlighting for docvim comments *docvim*\r\n\r\nCONTENTS *docvim-contents*\r\n\r\n1. Intro |docvim-intro|\r\n2. Installation |docvim-installation|\r\n3. Related |docvim-related|\r\n4. Website |docvim-website|\r\n5. License |docvim-license|\r\n6. Development |docvim-development|\r\n7. Authors |docvim-authors|\r\n8. History |docvim-history|\r\n\r\n\r\n *vim-docvim*\r\nINTRO *docvim-intro*\r\n\r\nvim-docvim provides additional syntax highlighting for Vim script files that\r\ncontain embedded docvim comments.\r\n\r\ndocvim (the tool, not this plug-in) is a documentation generator that\r\nprocesses those embedded comments and produces documentation in Markdown and\r\nVim \"help\" formats. To avoid confusion, this document refers to the Vim\r\nplug-in as \"vim-docvim\" and the separate generation tool as \"docvim\".\r\n\r\nINSTALLATION *docvim-installation*\r\n\r\nTo install vim-docvim, use your plug-in management system of choice.\r\n\r\nIf you don't have a \"plug-in management system of choice\", I recommend\r\nPathogen (https:\/\/github.com\/tpope\/vim-pathogen) due to its simplicity and\r\nrobustness. Assuming that you have Pathogen installed and configured, and\r\nthat you want to install vim-docvim into `~\/.vim\/bundle`, you can do so with:\r\n>\r\n git clone https:\/\/github.com\/wincent\/vim-docvim.git ~\/.vim\/bundle\/vim-docvim\r\n<\r\nAlternatively, if you use a Git submodule for each Vim plug-in, you could do\r\nthe following after `cd`-ing into the top-level of your Git superproject:\r\n>\r\n git submodule add https:\/\/github.com\/wincent\/vim-docvim.git ~\/vim\/bundle\/vim-docvim\r\n git submodule init\r\n<\r\nTo generate help tags under Pathogen, you can do so from inside Vim with:\r\n>\r\n :call pathogen#helptags()\r\n<\r\nRELATED *docvim-related*\r\n\r\nDocvim ~\r\n\r\nThe Docvim tool itself is a Haskell module, available at:\r\n\r\nhttp:\/\/hackage.haskell.org\/package\/docvim\r\n\r\nThe official source code repo is at:\r\n\r\nhttp:\/\/git.wincent.com\/docvim.git\r\n\r\nMirrors exist at:\r\n\r\n- https:\/\/github.com\/wincent\/docvim\r\n- https:\/\/gitlab.com\/wincent\/docvim\r\n- https:\/\/bitbucket.org\/ghurrell\/docvim\r\n\r\nWEBSITE *docvim-website*\r\n\r\nThe official vim-docvim source code repo is at:\r\n\r\nhttp:\/\/git.wincent.com\/vim-docvim.git\r\n\r\nMirrors exist at:\r\n\r\n- https:\/\/github.com\/wincent\/vim-docvim\r\n- https:\/\/gitlab.com\/wincent\/vim-docvim\r\n- https:\/\/bitbucket.org\/ghurrell\/vim-docvim\r\n\r\nOfficial releases are listed at:\r\n\r\nhttp:\/\/www.vim.org\/scripts\/script.php?script_id=5758\r\n\r\nLICENSE *docvim-license*\r\n\r\nCopyright (c) 2015-present Greg Hurrell\r\n\r\nPermission is hereby granted, free of charge, to any person obtaining a copy\r\nof this software and associated documentation files (the \"Software\"), to\r\ndeal in the Software without restriction, including without limitation the\r\nrights to use, copy, modify, merge, publish, distribute, sublicense, and\/or\r\nsell copies of the Software, and to permit persons to whom the Software is\r\nfurnished to do so, subject to the following conditions:\r\n\r\nThe above copyright notice and this permission notice shall be included in\r\nall copies or substantial portions of the Software.\r\n\r\nTHE SOFTWARE IS PROVIDED \"AS IS\", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR\r\nIMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,\r\nFITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE\r\nAUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER\r\nLIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING\r\nFROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS\r\nIN THE SOFTWARE.\r\n\r\nDEVELOPMENT *docvim-development*\r\n\r\nContributing patches ~\r\n\r\nPatches can be sent via mail to greg@hurrell.net, or as GitHub pull requests\r\nat: https:\/\/github.com\/wincent\/vim-docvim\/pulls\r\n\r\nCutting a new release ~\r\n\r\nAt the moment the release process is manual:\r\n\r\n- Perform final sanity checks and manual testing\r\n- Update the |docvim-history| section of the documentation\r\n- Verify clean work tree:\r\n>\r\n git status\r\n<\r\n- Tag the release:\r\n>\r\n git tag -s -m \"$VERSION release\" $VERSION\r\n<\r\n- Publish the code:\r\n>\r\n git push origin master --follow-tags\r\n git push github master --follow-tags\r\n<\r\n- Produce the release archive:\r\n>\r\n git archive -o vim-docvim-$VERSION.zip HEAD -- .\r\n<\r\n- Upload to http:\/\/www.vim.org\/scripts\/script.php?script_id=5758\r\n\r\nAUTHORS *docvim-authors*\r\n\r\nvim-docvim is written and maintained by Greg Hurrell .\r\n\r\n","install_details":"","5":"","first_name":"Greg","6":"Greg","last_name":"Hurrell","7":"Hurrell","releases":[{"0":"5758","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"vim-docvim-1.0.zip","4":"vim-docvim-1.0.zip","src_id":"26307","5":"26307","creation_date":"1545800049","6":"1545800049"}]},"5757":{"script_id":"5757","0":"5757","script_name":"vim-decode-qp","1":"vim-decode-qp","script_type":"ftplugin","2":"ftplugin","summary":"Decode Quoted-Printable text","3":"Decode Quoted-Printable text","description":"Decode Quoted-Printable text in ASC files. \r\n\r\nRelies on g:decodeqp_command which can be customized, otherwise a Perl regexp will be used.\r\n\r\n# Usage\r\n\r\n:[range]DecodeQP \" Decode [range] lines. Defaults to the whole file.\r\n\r\n{Visual}gcp \" Decode the highlighted lines.\r\n\r\ngcp \" Decode the whole file.\r\n\r\n\r\n---\r\nhttps:\/\/github.com\/akarzim\/vim-decode-qp","4":"Decode Quoted-Printable text in ASC files. \r\n\r\nRelies on g:decodeqp_command which can be customized, otherwise a Perl regexp will be used.\r\n\r\n# Usage\r\n\r\n:[range]DecodeQP \" Decode [range] lines. Defaults to the whole file.\r\n\r\n{Visual}gcp \" Decode the highlighted lines.\r\n\r\ngcp \" Decode the whole file.\r\n\r\n\r\n---\r\nhttps:\/\/github.com\/akarzim\/vim-decode-qp","install_details":"## with Plug\r\n\r\nPlug 'akarzim\/vim-decode-qp', { 'for': 'asc' }","5":"## with Plug\r\n\r\nPlug 'akarzim\/vim-decode-qp', { 'for': 'asc' }","first_name":"Fran\u00c3\u00a7ois","6":"Fran\u00c3\u00a7ois","last_name":"Vantomme","7":"Vantomme","releases":[{"0":"5757","vim_version":"7.0","1":"7.0","script_version":"0.5","2":"0.5","version_comment":"Initial upload","3":"Initial upload","package":"vim-decode-qp.zip","4":"vim-decode-qp.zip","src_id":"26306","5":"26306","creation_date":"1545705628","6":"1545705628"}]},"5756":{"script_id":"5756","0":"5756","script_name":"ctrlp-grep","1":"ctrlp-grep","script_type":"utility","2":"utility","summary":"grep your files via ctrlp interactively","3":"grep your files via ctrlp interactively","description":"https:\/\/github.com\/ompugao\/ctrlp-grep","4":"https:\/\/github.com\/ompugao\/ctrlp-grep","install_details":"","5":"","first_name":"Shohei","6":"Shohei","last_name":"Fujii","7":"Fujii","releases":[{"0":"5756","vim_version":"7.4","1":"7.4","script_version":"0.0.1","2":"0.0.1","version_comment":"Initial upload","3":"Initial upload","package":"ctrlp-grep.zip","4":"ctrlp-grep.zip","src_id":"26302","5":"26302","creation_date":"1545127275","6":"1545127275"}]},"5755":{"script_id":"5755","0":"5755","script_name":"vim-ls","1":"vim-ls","script_type":"ftplugin","2":"ftplugin","summary":"LiveScript support for Vim","3":"LiveScript support for Vim","description":"LiveScript is a language which compiles to JavaScript. It has a straightforward mapping to JavaScript and allows you to write expressive code devoid of repetitive boilerplate. While LiveScript adds many features to assist in functional style programming, it also has many improvements for object oriented and imperative programming.\r\n\r\nLiveScript is a fork of Coco and an indirect descendant of CoffeeScript, with which it has much compatibility.","4":"LiveScript is a language which compiles to JavaScript. It has a straightforward mapping to JavaScript and allows you to write expressive code devoid of repetitive boilerplate. While LiveScript adds many features to assist in functional style programming, it also has many improvements for object oriented and imperative programming.\r\n\r\nLiveScript is a fork of Coco and an indirect descendant of CoffeeScript, with which it has much compatibility.","install_details":"### LiveScript\r\nFor more information about LiveScript see [gkz.github.com\/LiveScript](http:\/\/gkz.github.com\/LiveScript\/).\r\n\r\n### Installing and Using\r\n\r\n1. Install [tpope's][tpope] [pathogen] into `~\/.vim\/autoload\/` and add the\r\n following line to your `~\/.vimrc`:\r\n\r\n call pathogen#infect()\r\n\r\n Be aware that it must be added before any `filetype plugin indent on`\r\n lines according to the install page:\r\n\r\n > Note that you need to invoke the pathogen functions before invoking\r\n > \"filetype plugin indent on\" if you want it to load ftdetect files. On\r\n > Debian (and probably other distros), the system vimrc does this early on,\r\n > so you actually need to \"filetype off\" before \"filetype plugin indent on\"\r\n > to force reloading.\r\n\r\n[pathogen]: http:\/\/www.vim.org\/scripts\/script.php?script_id=2332\r\n[tpope]: http:\/\/github.com\/tpope\/vim-pathogen\r\n\r\n2. Create, and change into, the `~\/.vim\/bundle\/` directory:\r\n\r\n $ mkdir -p ~\/.vim\/bundle\r\n $ cd ~\/.vim\/bundle\r\n\r\n3. Make a clone of the `vim-ls` repository:\r\n\r\n $ git clone git:\/\/github.com\/gkz\/vim-ls.git\r\n [...]\r\n $ ls\r\n vim-ls\/\r\n\r\nThat's it. Pathogen should handle the rest. Opening a file with a `.ls`\r\nextension or a `Slakefile` will load everything.\r\n\r\n### Updating\r\n\r\n1. Change into the `~\/.vim\/bundle\/vim-ls\/` directory:\r\n\r\n $ cd ~\/.vim\/bundle\/vim-ls\r\n\r\n2. Pull in the latest changes:\r\n\r\n $ git pull\r\n\r\nEverything will then be brought up to date.\r\n\r\n### LiveScriptMake: Compile the Current File\r\n\r\nThe `LiveScriptMake` command compiles the current file and parses any errors.\r\n\r\nThe full signature of the command is:\r\n\r\n :[silent] LiveScriptMake[!] [ls-OPTIONS]...\r\n\r\nBy default, `LiveScriptMake` shows all compiler output and jumps to the first line\r\nreported as an error by `livescript`:\r\n\r\n :LiveScriptMake\r\n\r\nCompiler output can be hidden with `silent`:\r\n\r\n :silent LiveScriptMake\r\n\r\nLine-jumping can be turned off by adding a bang:\r\n\r\n :LiveScriptMake!\r\n\r\nOptions given to `LiveScriptMake` are passed along to `livescript`:\r\n\r\n :LiveScriptMake --bare\r\n\r\n`LiveScriptMake` can be manually loaded for a file with:\r\n\r\n :compiler ls\r\n\r\n#### Recompile on write\r\n\r\nTo recompile a file when it's written, add an `autocmd` like this to your\r\n`vimrc`:\r\n\r\n au BufWritePost *.ls silent LiveScriptMake!\r\n\r\nAll of the customizations above can be used, too. This one compiles silently\r\nand with the `-b` option, but shows any errors:\r\n\r\n au BufWritePost *.ls silent LiveScriptMake! -b | cwindow | redraw!\r\n\r\nThe `redraw!` command is needed to fix a redrawing quirk in terminal vim, but\r\ncan removed for gVim.\r\n\r\n#### Default compiler options\r\n\r\nThe `LiveScriptMake` command passes any options in the `livescript_make_options`\r\nvariable along to the compiler. You can use this to set default options:\r\n\r\n let livescript_make_options = '--bare'\r\n\r\n#### Path to compiler\r\n\r\nTo change the compiler used by `LiveScriptMake` and `LiveScriptCompile`, set\r\n`livescript_compiler` to the full path of an executable or the filename of one\r\nin your `$PATH`:\r\n\r\n let livescript_compiler = '\/usr\/bin\/livescript'\r\n\r\nThis option is set to `livescript` by default.\r\n\r\n### LiveScriptCompile: Compile Snippets of LiveScript\r\n\r\nThe `LiveScriptCompile` command shows how the current file or a snippet of\r\nLiveScript is compiled to JavaScript. The full signature of the command is:\r\n\r\n :[RANGE] LiveScriptCompile [watch|unwatch] [vert[ical]] [WINDOW-SIZE]\r\n\r\nCalling `LiveScriptCompile` without a range compiles the whole file.\r\n\r\nCalling `LiveScriptCompile` with a range, like in visual mode, compiles the selected\r\nsnippet of LiveScript.\r\n\r\nThe scratch buffer can be quickly closed by hitting the `q` key.\r\n\r\nUsing `vert` splits the LiveScriptCompile buffer vertically instead of horizontally:\r\n\r\n :LiveScriptCompile vert\r\n\r\nSet the `ls_compile_vert` variable to split the buffer vertically by\r\ndefault:\r\n\r\n let ls_compile_vert = 1\r\n\r\nThe initial size of the LiveScriptCompile buffer can be given as a number:\r\n\r\n :LiveScriptCompile 4\r\n\r\n#### Watch (live preview) mode\r\n\r\nWriting some code and then exiting insert mode automatically updates the\r\ncompiled JavaScript buffer.\r\n\r\nUse `watch` to start watching a buffer (`vert` is also recommended):\r\n\r\n :LiveScriptCompile watch vert\r\n\r\nAfter making some changes in insert mode, hit escape and your code will\r\nbe recompiled. Changes made outside of insert mode don't trigger this recompile,\r\nbut calling `LiveScriptCompile` will compile these changes without any bad effects.\r\n\r\nTo get synchronized scrolling of a LiveScript and LiveScriptCompile buffer, set\r\n`scrollbind` on each:\r\n\r\n :setl scrollbind\r\n\r\nUse `unwatch` to stop watching a buffer:\r\n\r\n :LiveScriptCompile unwatch\r\n\r\n### Configure Syntax Highlighting\r\n\r\nAdd these lines to your `vimrc` to disable the relevant syntax group.\r\n\r\n#### Disable trailing whitespace error\r\n\r\nTrailing whitespace is highlighted as an error by default. This can be disabled\r\nwith:\r\n\r\n hi link lsSpaceError NONE\r\n\r\n#### Disable reserved words error\r\n\r\nReserved words like `function` and `var` are highlighted as an error where\r\nthey're not allowed in LiveScript. This can be disabled with:\r\n\r\n hi link lsReservedError NONE\r\n\r\n### Tune Vim for LiveScript\r\n\r\nChanging these core settings can make vim more LiveScript friendly.\r\n\r\n#### Fold by indentation\r\n\r\nFolding by indentation works well for LiveScript functions and classes.\r\nTo fold by indentation in LiveScript files, add this line to your `vimrc`:\r\n\r\n au BufNewFile,BufReadPost *.ls setl foldmethod=indent nofoldenable\r\n\r\nWith this, folding is disabled by default but can be quickly toggled per-file\r\nby hitting `zi`. To enable folding by default, remove `nofoldenable`:\r\n\r\n au BufNewFile,BufReadPost *.ls setl foldmethod=indent\r\n\r\n#### Two-space indentation\r\n\r\nTo get standard two-space indentation in LiveScript files, add this line to\r\nyour `vimrc`:\r\n\r\n au BufNewFile,BufReadPost *.ls setl shiftwidth=2 expandtab","5":"### LiveScript\r\nFor more information about LiveScript see [gkz.github.com\/LiveScript](http:\/\/gkz.github.com\/LiveScript\/).\r\n\r\n### Installing and Using\r\n\r\n1. Install [tpope's][tpope] [pathogen] into `~\/.vim\/autoload\/` and add the\r\n following line to your `~\/.vimrc`:\r\n\r\n call pathogen#infect()\r\n\r\n Be aware that it must be added before any `filetype plugin indent on`\r\n lines according to the install page:\r\n\r\n > Note that you need to invoke the pathogen functions before invoking\r\n > \"filetype plugin indent on\" if you want it to load ftdetect files. On\r\n > Debian (and probably other distros), the system vimrc does this early on,\r\n > so you actually need to \"filetype off\" before \"filetype plugin indent on\"\r\n > to force reloading.\r\n\r\n[pathogen]: http:\/\/www.vim.org\/scripts\/script.php?script_id=2332\r\n[tpope]: http:\/\/github.com\/tpope\/vim-pathogen\r\n\r\n2. Create, and change into, the `~\/.vim\/bundle\/` directory:\r\n\r\n $ mkdir -p ~\/.vim\/bundle\r\n $ cd ~\/.vim\/bundle\r\n\r\n3. Make a clone of the `vim-ls` repository:\r\n\r\n $ git clone git:\/\/github.com\/gkz\/vim-ls.git\r\n [...]\r\n $ ls\r\n vim-ls\/\r\n\r\nThat's it. Pathogen should handle the rest. Opening a file with a `.ls`\r\nextension or a `Slakefile` will load everything.\r\n\r\n### Updating\r\n\r\n1. Change into the `~\/.vim\/bundle\/vim-ls\/` directory:\r\n\r\n $ cd ~\/.vim\/bundle\/vim-ls\r\n\r\n2. Pull in the latest changes:\r\n\r\n $ git pull\r\n\r\nEverything will then be brought up to date.\r\n\r\n### LiveScriptMake: Compile the Current File\r\n\r\nThe `LiveScriptMake` command compiles the current file and parses any errors.\r\n\r\nThe full signature of the command is:\r\n\r\n :[silent] LiveScriptMake[!] [ls-OPTIONS]...\r\n\r\nBy default, `LiveScriptMake` shows all compiler output and jumps to the first line\r\nreported as an error by `livescript`:\r\n\r\n :LiveScriptMake\r\n\r\nCompiler output can be hidden with `silent`:\r\n\r\n :silent LiveScriptMake\r\n\r\nLine-jumping can be turned off by adding a bang:\r\n\r\n :LiveScriptMake!\r\n\r\nOptions given to `LiveScriptMake` are passed along to `livescript`:\r\n\r\n :LiveScriptMake --bare\r\n\r\n`LiveScriptMake` can be manually loaded for a file with:\r\n\r\n :compiler ls\r\n\r\n#### Recompile on write\r\n\r\nTo recompile a file when it's written, add an `autocmd` like this to your\r\n`vimrc`:\r\n\r\n au BufWritePost *.ls silent LiveScriptMake!\r\n\r\nAll of the customizations above can be used, too. This one compiles silently\r\nand with the `-b` option, but shows any errors:\r\n\r\n au BufWritePost *.ls silent LiveScriptMake! -b | cwindow | redraw!\r\n\r\nThe `redraw!` command is needed to fix a redrawing quirk in terminal vim, but\r\ncan removed for gVim.\r\n\r\n#### Default compiler options\r\n\r\nThe `LiveScriptMake` command passes any options in the `livescript_make_options`\r\nvariable along to the compiler. You can use this to set default options:\r\n\r\n let livescript_make_options = '--bare'\r\n\r\n#### Path to compiler\r\n\r\nTo change the compiler used by `LiveScriptMake` and `LiveScriptCompile`, set\r\n`livescript_compiler` to the full path of an executable or the filename of one\r\nin your `$PATH`:\r\n\r\n let livescript_compiler = '\/usr\/bin\/livescript'\r\n\r\nThis option is set to `livescript` by default.\r\n\r\n### LiveScriptCompile: Compile Snippets of LiveScript\r\n\r\nThe `LiveScriptCompile` command shows how the current file or a snippet of\r\nLiveScript is compiled to JavaScript. The full signature of the command is:\r\n\r\n :[RANGE] LiveScriptCompile [watch|unwatch] [vert[ical]] [WINDOW-SIZE]\r\n\r\nCalling `LiveScriptCompile` without a range compiles the whole file.\r\n\r\nCalling `LiveScriptCompile` with a range, like in visual mode, compiles the selected\r\nsnippet of LiveScript.\r\n\r\nThe scratch buffer can be quickly closed by hitting the `q` key.\r\n\r\nUsing `vert` splits the LiveScriptCompile buffer vertically instead of horizontally:\r\n\r\n :LiveScriptCompile vert\r\n\r\nSet the `ls_compile_vert` variable to split the buffer vertically by\r\ndefault:\r\n\r\n let ls_compile_vert = 1\r\n\r\nThe initial size of the LiveScriptCompile buffer can be given as a number:\r\n\r\n :LiveScriptCompile 4\r\n\r\n#### Watch (live preview) mode\r\n\r\nWriting some code and then exiting insert mode automatically updates the\r\ncompiled JavaScript buffer.\r\n\r\nUse `watch` to start watching a buffer (`vert` is also recommended):\r\n\r\n :LiveScriptCompile watch vert\r\n\r\nAfter making some changes in insert mode, hit escape and your code will\r\nbe recompiled. Changes made outside of insert mode don't trigger this recompile,\r\nbut calling `LiveScriptCompile` will compile these changes without any bad effects.\r\n\r\nTo get synchronized scrolling of a LiveScript and LiveScriptCompile buffer, set\r\n`scrollbind` on each:\r\n\r\n :setl scrollbind\r\n\r\nUse `unwatch` to stop watching a buffer:\r\n\r\n :LiveScriptCompile unwatch\r\n\r\n### Configure Syntax Highlighting\r\n\r\nAdd these lines to your `vimrc` to disable the relevant syntax group.\r\n\r\n#### Disable trailing whitespace error\r\n\r\nTrailing whitespace is highlighted as an error by default. This can be disabled\r\nwith:\r\n\r\n hi link lsSpaceError NONE\r\n\r\n#### Disable reserved words error\r\n\r\nReserved words like `function` and `var` are highlighted as an error where\r\nthey're not allowed in LiveScript. This can be disabled with:\r\n\r\n hi link lsReservedError NONE\r\n\r\n### Tune Vim for LiveScript\r\n\r\nChanging these core settings can make vim more LiveScript friendly.\r\n\r\n#### Fold by indentation\r\n\r\nFolding by indentation works well for LiveScript functions and classes.\r\nTo fold by indentation in LiveScript files, add this line to your `vimrc`:\r\n\r\n au BufNewFile,BufReadPost *.ls setl foldmethod=indent nofoldenable\r\n\r\nWith this, folding is disabled by default but can be quickly toggled per-file\r\nby hitting `zi`. To enable folding by default, remove `nofoldenable`:\r\n\r\n au BufNewFile,BufReadPost *.ls setl foldmethod=indent\r\n\r\n#### Two-space indentation\r\n\r\nTo get standard two-space indentation in LiveScript files, add this line to\r\nyour `vimrc`:\r\n\r\n au BufNewFile,BufReadPost *.ls setl shiftwidth=2 expandtab","first_name":"","6":"","last_name":"","7":"","releases":[{"0":"5755","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"vim-ls.zip","4":"vim-ls.zip","src_id":"26299","5":"26299","creation_date":"1544489833","6":"1544489833"}]},"5754":{"script_id":"5754","0":"5754","script_name":"Venu","1":"Venu","script_type":"utility","2":"utility","summary":"Simple menu for vim ","3":"Simple menu for vim ","description":"# V̂enu\r\n\r\nV̂enu is a vim plugin that allows the definition of menus for different filetypes removing the need to remember commands and key combinations.\r\n\r\n## Install\r\n\r\nUsing vim plug:\r\n```\r\nPlug 'Timoses\/vim-venu'\r\n```\r\n\r\nOr use any other vim plugin manager.\r\n\r\n## Example Usage\r\n\r\nA simple example:\r\n```\r\nlet s:menu1 = venu#create('My first Venu')\r\ncall venu#addOption(s:menu1, 'Option of first menu', 'echo \"Called first option\"')\r\ncall venu#register(s:menu1)\r\n\r\nfunction! s:myfunction() abort\r\n echo \"I called myfunction\"\r\nendfunction\r\n\r\nlet s:menu2 = venu#create('My second Venu')\r\ncall venu#addOption(s:menu2, 'Call a function ref', function(\"s:myfunction\"))\r\n\r\nlet s:submenu = venu#create('My awesome subVenu')\r\ncall venu#addOption(s:submenu, 'Option 1', ':echo \"First option of submenu!\"')\r\ncall venu#addOption(s:submenu, 'Option 2', ':echo \"Second option of submenu!\"')\r\n\r\n\" Add the submenu to the second menu\r\ncall venu#addOption(s:menu2, 'Sub menu', s:submenu)\r\n\r\ncall venu#register(s:menu2)\r\n```\r\n\r\nThe following command will open the V̂enu:\r\n```\r\n:VenuPrint\r\n```\r\n\r\nCalling `:VenuPrint` again will close the menu without any action.\r\n\r\n## Documentation\r\n\r\n----\r\n```\r\nvenu#create(name)\r\n```\r\nCreates a menu with the given name and returns a handle to it.\r\n\r\n----\r\n```\r\nvenu#addOption(menuHandle, name, cmd [, filetype])\r\n```\r\nAdd an option with the given `name` to the menu with the handle `menuHandle`.\r\n`cmd` can be a\r\n* string - executed with `exe `\r\n* FuncRef - executed with `call `\r\n* another menu handle - a submenu is displayed\r\n\r\n`filetype` can be a string or an array of strings. This argument allows showing an option only for specific filetypes. Note that when `venu#register` is not called with the filetype the menu will not be shown. Logically, the herein specified `filetype` argument should be a subset of the filetypes passed to `venu#register`.\r\n\r\n\r\n----\r\n```\r\nvenu#register(menuHandle [, filetype])\r\n```\r\nRegister the menu so that it is displayed with `venu#print`. If only one menu is available its options are directly displayed. If several menus are registered the user has to select the menu which to show the options of.\r\n\r\n----\r\n```\r\nvenu#print()\r\n```\r\nPrints the menu.\r\n\r\n\r\n## Contribute\r\n\r\nSource code: https:\/\/github.com\/Timoses\/vim-venu\r\n\r\nIf you would like to contribute feel free to create a Pull Request or mention your ideas and problems as an Issue.\r\n\r\n## The ^ in V̂enu ?\r\nI personally mapped `:VenuPrint` to the `^` key on a German keyboard which is easily reachable. Hence, the name.\r\n\r\n## Alternatives\r\n* quickmenu: https:\/\/github.com\/skywind3000\/quickmenu.vim\r\n * opens a menu on the side, can use cmdline menu as well\r\n * no support for submenus\r\n","4":"# V̂enu\r\n\r\nV̂enu is a vim plugin that allows the definition of menus for different filetypes removing the need to remember commands and key combinations.\r\n\r\n## Install\r\n\r\nUsing vim plug:\r\n```\r\nPlug 'Timoses\/vim-venu'\r\n```\r\n\r\nOr use any other vim plugin manager.\r\n\r\n## Example Usage\r\n\r\nA simple example:\r\n```\r\nlet s:menu1 = venu#create('My first Venu')\r\ncall venu#addOption(s:menu1, 'Option of first menu', 'echo \"Called first option\"')\r\ncall venu#register(s:menu1)\r\n\r\nfunction! s:myfunction() abort\r\n echo \"I called myfunction\"\r\nendfunction\r\n\r\nlet s:menu2 = venu#create('My second Venu')\r\ncall venu#addOption(s:menu2, 'Call a function ref', function(\"s:myfunction\"))\r\n\r\nlet s:submenu = venu#create('My awesome subVenu')\r\ncall venu#addOption(s:submenu, 'Option 1', ':echo \"First option of submenu!\"')\r\ncall venu#addOption(s:submenu, 'Option 2', ':echo \"Second option of submenu!\"')\r\n\r\n\" Add the submenu to the second menu\r\ncall venu#addOption(s:menu2, 'Sub menu', s:submenu)\r\n\r\ncall venu#register(s:menu2)\r\n```\r\n\r\nThe following command will open the V̂enu:\r\n```\r\n:VenuPrint\r\n```\r\n\r\nCalling `:VenuPrint` again will close the menu without any action.\r\n\r\n## Documentation\r\n\r\n----\r\n```\r\nvenu#create(name)\r\n```\r\nCreates a menu with the given name and returns a handle to it.\r\n\r\n----\r\n```\r\nvenu#addOption(menuHandle, name, cmd [, filetype])\r\n```\r\nAdd an option with the given `name` to the menu with the handle `menuHandle`.\r\n`cmd` can be a\r\n* string - executed with `exe `\r\n* FuncRef - executed with `call `\r\n* another menu handle - a submenu is displayed\r\n\r\n`filetype` can be a string or an array of strings. This argument allows showing an option only for specific filetypes. Note that when `venu#register` is not called with the filetype the menu will not be shown. Logically, the herein specified `filetype` argument should be a subset of the filetypes passed to `venu#register`.\r\n\r\n\r\n----\r\n```\r\nvenu#register(menuHandle [, filetype])\r\n```\r\nRegister the menu so that it is displayed with `venu#print`. If only one menu is available its options are directly displayed. If several menus are registered the user has to select the menu which to show the options of.\r\n\r\n----\r\n```\r\nvenu#print()\r\n```\r\nPrints the menu.\r\n\r\n\r\n## Contribute\r\n\r\nSource code: https:\/\/github.com\/Timoses\/vim-venu\r\n\r\nIf you would like to contribute feel free to create a Pull Request or mention your ideas and problems as an Issue.\r\n\r\n## The ^ in V̂enu ?\r\nI personally mapped `:VenuPrint` to the `^` key on a German keyboard which is easily reachable. Hence, the name.\r\n\r\n## Alternatives\r\n* quickmenu: https:\/\/github.com\/skywind3000\/quickmenu.vim\r\n * opens a menu on the side, can use cmdline menu as well\r\n * no support for submenus\r\n","install_details":"To install the plugin use any vim plugin manager.","5":"To install the plugin use any vim plugin manager.","first_name":"Tol","6":"Tol","last_name":"Ida","7":"Ida","releases":[{"0":"5754","vim_version":"7.0","1":"7.0","script_version":"0.0.1","2":"0.0.1","version_comment":"Initial upload","3":"Initial upload","package":"vim-venu.tar.gz","4":"vim-venu.tar.gz","src_id":"26298","5":"26298","creation_date":"1544335997","6":"1544335997"}]},"5753":{"script_id":"5753","0":"5753","script_name":"cosmic-barf.vim","1":"cosmic-barf.vim","script_type":"color scheme","2":"color scheme","summary":"A dark, solarized based colorscheme","3":"A dark, solarized based colorscheme","description":"GitHub Repo\r\n---------------------\r\n\r\nhttps:\/\/github.com\/evturn\/cosmic-barf\r\n\r\nScreenshots\r\n---------------------\r\n\r\nhttps:\/\/raw.githubusercontent.com\/evturn\/cosmic-barf\/master\/screenshots\/javascript.png\r\nhttps:\/\/raw.githubusercontent.com\/evturn\/cosmic-barf\/master\/screenshots\/vim.png\r\nhttps:\/\/raw.githubusercontent.com\/evturn\/cosmic-barf\/master\/screenshots\/haskell.png","4":"GitHub Repo\r\n---------------------\r\n\r\nhttps:\/\/github.com\/evturn\/cosmic-barf\r\n\r\nScreenshots\r\n---------------------\r\n\r\nhttps:\/\/raw.githubusercontent.com\/evturn\/cosmic-barf\/master\/screenshots\/javascript.png\r\nhttps:\/\/raw.githubusercontent.com\/evturn\/cosmic-barf\/master\/screenshots\/vim.png\r\nhttps:\/\/raw.githubusercontent.com\/evturn\/cosmic-barf\/master\/screenshots\/haskell.png","install_details":"Installation\r\n---------------------\r\n\r\nOption 1: Manual installation\r\n\r\n1. After downloading the vim script or package, move the\r\n `cosmic-barf.vim` file to the `.vim\/colors` directory.\r\n\r\n $ cd cosmic-barf\/colors\r\n $ mv cosmic-barf.vim ~\/.vim\/colors\/\r\n\r\nOption 2: Pathogen installation\r\n\r\n1. Move or clone the `cosmic-barf` directory so that it is \r\n a subdirectory of the `.vim\/bundle` directory.\r\n\r\n $ cd ~\/.vim\/bundle\r\n $ git clone git@github.com:evturn\/cosmic-barf.git\r\n\r\nModify .vimrc\r\n---------------------\r\n\r\nsyntax enable\r\nset background=dark\r\ncolorscheme cosmic-barf\r\nlet g:colors_name = 'cosmic-barf'","5":"Installation\r\n---------------------\r\n\r\nOption 1: Manual installation\r\n\r\n1. After downloading the vim script or package, move the\r\n `cosmic-barf.vim` file to the `.vim\/colors` directory.\r\n\r\n $ cd cosmic-barf\/colors\r\n $ mv cosmic-barf.vim ~\/.vim\/colors\/\r\n\r\nOption 2: Pathogen installation\r\n\r\n1. Move or clone the `cosmic-barf` directory so that it is \r\n a subdirectory of the `.vim\/bundle` directory.\r\n\r\n $ cd ~\/.vim\/bundle\r\n $ git clone git@github.com:evturn\/cosmic-barf.git\r\n\r\nModify .vimrc\r\n---------------------\r\n\r\nsyntax enable\r\nset background=dark\r\ncolorscheme cosmic-barf\r\nlet g:colors_name = 'cosmic-barf'","first_name":"Evan","6":"Evan","last_name":"Turner","7":"Turner","releases":[{"0":"5753","vim_version":"7.0","1":"7.0","script_version":"1.1","2":"1.1","version_comment":"Extend highlighting for nerdtree","3":"Extend highlighting for nerdtree","package":"cosmic-barf.zip","4":"cosmic-barf.zip","src_id":"26297","5":"26297","creation_date":"1544255274","6":"1544255274"},{"0":"5753","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"cosmic-barf.zip","4":"cosmic-barf.zip","src_id":"26296","5":"26296","creation_date":"1544229847","6":"1544229847"}]},"5752":{"script_id":"5752","0":"5752","script_name":"glsl.vim","1":"glsl.vim","script_type":"syntax","2":"syntax","summary":"Syntax File for the Desktop OpenGL Shading Language Version 4.6 GLSL GLSlang ","3":"Syntax File for the Desktop OpenGL Shading Language Version 4.6 GLSL GLSlang ","description":"Syntax file for the OpenGL Shading Language version 4.6. The following is highlighted (as defined in the Orange Book):\r\n\r\n- All gl_ variables\r\n- All built-in functions\r\n- All keywords\r\n\r\nThis is an updated version of the top hit on duckduckgo and bing (script 1002), which hasn't been updated in 14 years.\r\n\r\nThe syntax file was modified from c.vim, so you can expect that your GLSL shaders will be highlighted similar to C files.\r\n\r\nAll reserved keywords (that GLSL currently does not use) are highlighted as errors. User labels are highlighted as errors.\r\n\r\nKeywords: glsl glslang opengl shading language","4":"Syntax file for the OpenGL Shading Language version 4.6. The following is highlighted (as defined in the Orange Book):\r\n\r\n- All gl_ variables\r\n- All built-in functions\r\n- All keywords\r\n\r\nThis is an updated version of the top hit on duckduckgo and bing (script 1002), which hasn't been updated in 14 years.\r\n\r\nThe syntax file was modified from c.vim, so you can expect that your GLSL shaders will be highlighted similar to C files.\r\n\r\nAll reserved keywords (that GLSL currently does not use) are highlighted as errors. User labels are highlighted as errors.\r\n\r\nKeywords: glsl glslang opengl shading language","install_details":"Place glsl.vim in your syntax directory:\r\n\r\ncp glsl.vim ~\/.vim\/syntax\/.\r\n\r\nEnable highlighting with glsl.vim in your .vimrc with:\r\n\r\nau BufNewFile,BufRead *.comp,*.frag,*.tese,*.tesc,*.geom,*.vert,*.glsl setf glsl\r\n\r\nor explicitly set the syntax with:\r\n\r\nset syntax=glsl","5":"Place glsl.vim in your syntax directory:\r\n\r\ncp glsl.vim ~\/.vim\/syntax\/.\r\n\r\nEnable highlighting with glsl.vim in your .vimrc with:\r\n\r\nau BufNewFile,BufRead *.comp,*.frag,*.tese,*.tesc,*.geom,*.vert,*.glsl setf glsl\r\n\r\nor explicitly set the syntax with:\r\n\r\nset syntax=glsl","first_name":"Richard","6":"Richard","last_name":"Van Natta","7":"Van Natta","releases":[{"0":"5752","vim_version":"6.0","1":"6.0","script_version":"2.0","2":"2.0","version_comment":"Initial upload","3":"Initial upload","package":"glsl.vim","4":"glsl.vim","src_id":"26276","5":"26276","creation_date":"1542524411","6":"1542524411"}]},"5751":{"script_id":"5751","0":"5751","script_name":"vim-mac-dictionary","1":"vim-mac-dictionary","script_type":"utility","2":"utility","summary":"A Vim plugin that helps you find words using Mac's dictionary app.","3":"A Vim plugin that helps you find words using Mac's dictionary app.","description":"https:\/\/github.com\/johngrib\/vim-mac-dictionary\/blob\/master\/README.md","4":"https:\/\/github.com\/johngrib\/vim-mac-dictionary\/blob\/master\/README.md","install_details":"","5":"","first_name":"JohnGrib","6":"JohnGrib","last_name":"Lee","7":"Lee","releases":[{"0":"5751","vim_version":"8.0","1":"8.0","script_version":"1.0.0","2":"1.0.0","version_comment":"Initial upload","3":"Initial upload","package":"vim-mac-dictionary-1.0.0.tar.gz","4":"vim-mac-dictionary-1.0.0.tar.gz","src_id":"26265","5":"26265","creation_date":"1541629981","6":"1541629981"}]},"5750":{"script_id":"5750","0":"5750","script_name":"vim-git-msg-wheel","1":"vim-git-msg-wheel","script_type":"ftplugin","2":"ftplugin","summary":"Show recent git commit messages and support line autocompletion.","3":"Show recent git commit messages and support line autocompletion.","description":"It would not be a good git usage habit to reuse commit messages.\r\n\r\nSometimes, however, I see the old commit message and try to recycle it.\r\n\r\nView recent commit messages as a list.\r\nYou can autocomplete and modify old commit messages and write new commit messages.\r\n","4":"It would not be a good git usage habit to reuse commit messages.\r\n\r\nSometimes, however, I see the old commit message and try to recycle it.\r\n\r\nView recent commit messages as a list.\r\nYou can autocomplete and modify old commit messages and write new commit messages.\r\n","install_details":"https:\/\/github.com\/johngrib\/vim-git-msg-wheel\/blob\/master\/README.md","5":"https:\/\/github.com\/johngrib\/vim-git-msg-wheel\/blob\/master\/README.md","first_name":"JohnGrib","6":"JohnGrib","last_name":"Lee","7":"Lee","releases":[{"0":"5750","vim_version":"8.0","1":"8.0","script_version":"v1.0.0","2":"v1.0.0","version_comment":"Initial upload","3":"Initial upload","package":"vim-git-msg-wheel-1.0.0.tar.gz","4":"vim-git-msg-wheel-1.0.0.tar.gz","src_id":"26250","5":"26250","creation_date":"1540375544","6":"1540375544"}]},"5749":{"script_id":"5749","0":"5749","script_name":"vim-headfirst","1":"vim-headfirst","script_type":"utility","2":"utility","summary":"Edit sibling files like a boss","3":"Edit sibling files like a boss","description":"This plugin is a small wrapper around :e, :sp, :vsp, and :tabe for editing sibling files. That is, it's comparable to typing :e %:h\/, but it also let's you supply multiple files to open.\r\n\r\nSee https:\/\/github.com\/tandrewnichols\/vim-headfirst for details.","4":"This plugin is a small wrapper around :e, :sp, :vsp, and :tabe for editing sibling files. That is, it's comparable to typing :e %:h\/, but it also let's you supply multiple files to open.\r\n\r\nSee https:\/\/github.com\/tandrewnichols\/vim-headfirst for details.","install_details":"Via Plug: \r\n\r\n Plug 'tandrewnichols\/vim-headfirst' \r\n :PlugInstall \r\n\r\nVia Vundle: \r\n\r\n Plugin 'tandrewnichols\/vim-headfirst' \r\n :BundleInstall \r\n\r\nVia NeoBundle: \r\n\r\n NeoBundle 'tandrewnichols\/vim-headfirst' \r\n :BundleInstall \r\n\r\nVia Pathogen: \r\n\r\n git clone https:\/\/github.com\/tandrewnichols\/vim-headfirst.git ~\/.vim\/bundle\/vim-headfirst","5":"Via Plug: \r\n\r\n Plug 'tandrewnichols\/vim-headfirst' \r\n :PlugInstall \r\n\r\nVia Vundle: \r\n\r\n Plugin 'tandrewnichols\/vim-headfirst' \r\n :BundleInstall \r\n\r\nVia NeoBundle: \r\n\r\n NeoBundle 'tandrewnichols\/vim-headfirst' \r\n :BundleInstall \r\n\r\nVia Pathogen: \r\n\r\n git clone https:\/\/github.com\/tandrewnichols\/vim-headfirst.git ~\/.vim\/bundle\/vim-headfirst","first_name":"Andrew","6":"Andrew","last_name":"Nichols","7":"Nichols","releases":[{"0":"5749","vim_version":"7.0","1":"7.0","script_version":"1.0.1","2":"1.0.1","version_comment":"Fixes a bug with reverse()","3":"Fixes a bug with reverse()","package":"vim-headfirst-v1.0.1.tar.gz","4":"vim-headfirst-v1.0.1.tar.gz","src_id":"26239","5":"26239","creation_date":"1538446858","6":"1538446858"},{"0":"5749","vim_version":"7.0","1":"7.0","script_version":"1.0.0","2":"1.0.0","version_comment":"Initial upload","3":"Initial upload","package":"vim-headfirst-v1.0.0.tar.gz","4":"vim-headfirst-v1.0.0.tar.gz","src_id":"26237","5":"26237","creation_date":"1538199203","6":"1538199203"}]},"5748":{"script_id":"5748","0":"5748","script_name":"typecast","1":"typecast","script_type":"utility","2":"utility","summary":"add type cast surrouding.","3":"add type cast surrouding.","description":"Typecast is a plugin to add type cast surrouding.\r\n\r\nhttps:\/\/github.com\/tenfyzhong\/typecast.vim\r\n\r\n","4":"Typecast is a plugin to add type cast surrouding.\r\n\r\nhttps:\/\/github.com\/tenfyzhong\/typecast.vim\r\n\r\n","install_details":"\r\nI suggest you to use a plugin manager, such vim-plug or other.\r\n\r\nvim-plug\r\nPlug 'tenfyzhong\/typecast.vim' \r\n\r\nManual\r\ngit clone https:\/\/github.com\/tenfyzhong\/typecast.vim.git ~\/.vim\/bundle\/typecast.vim\r\necho 'set rtp+=~\/.vim\/bundle\/typecast.vim' >> ~\/.vimrc\r\nvim -c 'helptag ~\/.vim\/bundle\/typecast.vim\/doc' -c qa!","5":"\r\nI suggest you to use a plugin manager, such vim-plug or other.\r\n\r\nvim-plug\r\nPlug 'tenfyzhong\/typecast.vim' \r\n\r\nManual\r\ngit clone https:\/\/github.com\/tenfyzhong\/typecast.vim.git ~\/.vim\/bundle\/typecast.vim\r\necho 'set rtp+=~\/.vim\/bundle\/typecast.vim' >> ~\/.vimrc\r\nvim -c 'helptag ~\/.vim\/bundle\/typecast.vim\/doc' -c qa!","first_name":"tenfy","6":"tenfy","last_name":"zhong","7":"zhong","releases":[{"0":"5748","vim_version":"7.4","1":"7.4","script_version":"0.1.0","2":"0.1.0","version_comment":"Initial upload","3":"Initial upload","package":"typecast.vim-0.1.0.tar.gz","4":"typecast.vim-0.1.0.tar.gz","src_id":"26235","5":"26235","creation_date":"1538054138","6":"1538054138"}]},"5747":{"script_id":"5747","0":"5747","script_name":"vim-determined","1":"vim-determined","script_type":"utility","2":"utility","summary":"A wrapper to make term_start more friendly","3":"A wrapper to make term_start more friendly","description":"Vim 8 added asynchronous terminal support via term_start, and it's really neat. Except it's a pain to use. I basically have to do :h term_start every time I think I might want to use it. But it seems like it wasn't really intended to be used directly, since there's no command for it. You have to invoke it with :call term_start. I could've made a simple command like :Term cmd { args } but that's annoying to type every time, so instead, this plugin exposes the determined#command function, which you should call in your vim config setup (e.g. in vimrc). This function will create commands for you that wrap specific invocations of :call term_start to make it easy to use.\r\n\r\nSee https:\/\/github.com\/tandrewnichols\/vim-determined for more details.","4":"Vim 8 added asynchronous terminal support via term_start, and it's really neat. Except it's a pain to use. I basically have to do :h term_start every time I think I might want to use it. But it seems like it wasn't really intended to be used directly, since there's no command for it. You have to invoke it with :call term_start. I could've made a simple command like :Term cmd { args } but that's annoying to type every time, so instead, this plugin exposes the determined#command function, which you should call in your vim config setup (e.g. in vimrc). This function will create commands for you that wrap specific invocations of :call term_start to make it easy to use.\r\n\r\nSee https:\/\/github.com\/tandrewnichols\/vim-determined for more details.","install_details":"Via Plug: \r\n\r\n Plug 'tandrewnichols\/vim-determined' \r\n :PlugInstall \r\n\r\nVia Vundle: \r\n\r\n Plugin 'tandrewnichols\/vim-determined' \r\n :BundleInstall \r\n\r\nVia NeoBundle: \r\n\r\n NeoBundle 'tandrewnichols\/vim-determined' \r\n :BundleInstall \r\n\r\nVia Pathogen: \r\n\r\n git clone https:\/\/github.com\/tandrewnichols\/vim-determined.git ~\/.vim\/bundle\/vim-determined","5":"Via Plug: \r\n\r\n Plug 'tandrewnichols\/vim-determined' \r\n :PlugInstall \r\n\r\nVia Vundle: \r\n\r\n Plugin 'tandrewnichols\/vim-determined' \r\n :BundleInstall \r\n\r\nVia NeoBundle: \r\n\r\n NeoBundle 'tandrewnichols\/vim-determined' \r\n :BundleInstall \r\n\r\nVia Pathogen: \r\n\r\n git clone https:\/\/github.com\/tandrewnichols\/vim-determined.git ~\/.vim\/bundle\/vim-determined","first_name":"Andrew","6":"Andrew","last_name":"Nichols","7":"Nichols","releases":[{"0":"5747","vim_version":"8.0","1":"8.0","script_version":"1.1.1","2":"1.1.1","version_comment":"Documentation update","3":"Documentation update","package":"vim-determined-v1.1.1.tar.gz","4":"vim-determined-v1.1.1.tar.gz","src_id":"26269","5":"26269","creation_date":"1541860120","6":"1541860120"},{"0":"5747","vim_version":"7.0","1":"7.0","script_version":"1.1.0","2":"1.1.0","version_comment":"Added support for custom completion","3":"Added support for custom completion","package":"vim-determined-v1.1.0.tar.gz","4":"vim-determined-v1.1.0.tar.gz","src_id":"26268","5":"26268","creation_date":"1541859605","6":"1541859605"},{"0":"5747","vim_version":"8.0","1":"8.0","script_version":"1.0.0","2":"1.0.0","version_comment":"Initial upload","3":"Initial upload","package":"vim-determined-v1.0.0.tar.gz","4":"vim-determined-v1.0.0.tar.gz","src_id":"26231","5":"26231","creation_date":"1537855710","6":"1537855710"}]},"5746":{"script_id":"5746","0":"5746","script_name":"vim-whelp","1":"vim-whelp","script_type":"utility","2":"utility","summary":"A historical record of your help queries","3":"A historical record of your help queries","description":"Keep track of what you've looked up in vim's help. Then peruse the list later, reopen entries, or prune old queries.\r\n\r\nSee also: https:\/\/github.com\/tandrewnichols\/vim-whelp","4":"Keep track of what you've looked up in vim's help. Then peruse the list later, reopen entries, or prune old queries.\r\n\r\nSee also: https:\/\/github.com\/tandrewnichols\/vim-whelp","install_details":"Via Plug: \r\n\r\n Plug 'tandrewnichols\/vim-whelp' \r\n :PlugInstall \r\n\r\nVia Vundle: \r\n\r\n Plugin 'tandrewnichols\/vim-whelp' \r\n :BundleInstall \r\n\r\nVia NeoBundle: \r\n\r\n NeoBundle 'tandrewnichols\/vim-whelp' \r\n :BundleInstall \r\n\r\nVia Pathogen: \r\n\r\n git clone https:\/\/github.com\/tandrewnichols\/vim-whelp.git ~\/.vim\/bundle\/vim-whelp","5":"Via Plug: \r\n\r\n Plug 'tandrewnichols\/vim-whelp' \r\n :PlugInstall \r\n\r\nVia Vundle: \r\n\r\n Plugin 'tandrewnichols\/vim-whelp' \r\n :BundleInstall \r\n\r\nVia NeoBundle: \r\n\r\n NeoBundle 'tandrewnichols\/vim-whelp' \r\n :BundleInstall \r\n\r\nVia Pathogen: \r\n\r\n git clone https:\/\/github.com\/tandrewnichols\/vim-whelp.git ~\/.vim\/bundle\/vim-whelp","first_name":"Andrew","6":"Andrew","last_name":"Nichols","7":"Nichols","releases":[{"0":"5746","vim_version":"7.0","1":"7.0","script_version":"1.0.1","2":"1.0.1","version_comment":"Adds keepjumps and hide to the buffer creation","3":"Adds keepjumps and hide to the buffer creation","package":"vim-whelp-v1.0.1.tar.gz","4":"vim-whelp-v1.0.1.tar.gz","src_id":"26233","5":"26233","creation_date":"1537927175","6":"1537927175"},{"0":"5746","vim_version":"7.0","1":"7.0","script_version":"1.0.0","2":"1.0.0","version_comment":"Initial upload","3":"Initial upload","package":"vim-whelp-1.0.0.tar.gz","4":"vim-whelp-1.0.0.tar.gz","src_id":"26229","5":"26229","creation_date":"1537842177","6":"1537842177"}]},"5745":{"script_id":"5745","0":"5745","script_name":"vim-rumrunner","1":"vim-rumrunner","script_type":"utility","2":"utility","summary":"A better MRU list.","3":"A better MRU list.","description":"I have two problems with existing MRU (most recently used) implementations for vim. First, they're isolated, so while you can install, say, mru.vim, other plugins like BufExplorer can't use the list it maintains. Thus BufExplorer implements its own mru list. Which means multiple plugins you use are, potentially, doing the same work to keep the same list. What we need is an MRU plugin with a public-facing API for accessing and manipulating the most recently used list, so that it only needs to be implemented and maintained once and can be shared by all.\r\n\r\nThe second problem is that most MRU implementations don't provide a clean way to move around the list. That's because, once you go to the second most recently used file, it becomes the most recently used file, so repeating the action over and over will only toggle you between the two most recently used files instead of walking back through the entire list.\r\n\r\nVim-rumrunner attempts to solve both these problems: the first by providing methods to access the list it maintains and the second by temporarily suspending mru recordization when navigating up and down the mru tree.\r\n\r\nSee https:\/\/github.com\/tandrewnichols\/vim-rumrunner for more details.","4":"I have two problems with existing MRU (most recently used) implementations for vim. First, they're isolated, so while you can install, say, mru.vim, other plugins like BufExplorer can't use the list it maintains. Thus BufExplorer implements its own mru list. Which means multiple plugins you use are, potentially, doing the same work to keep the same list. What we need is an MRU plugin with a public-facing API for accessing and manipulating the most recently used list, so that it only needs to be implemented and maintained once and can be shared by all.\r\n\r\nThe second problem is that most MRU implementations don't provide a clean way to move around the list. That's because, once you go to the second most recently used file, it becomes the most recently used file, so repeating the action over and over will only toggle you between the two most recently used files instead of walking back through the entire list.\r\n\r\nVim-rumrunner attempts to solve both these problems: the first by providing methods to access the list it maintains and the second by temporarily suspending mru recordization when navigating up and down the mru tree.\r\n\r\nSee https:\/\/github.com\/tandrewnichols\/vim-rumrunner for more details.","install_details":"Via Plug:\r\n\r\n Plug 'tandrewnichols\/vim-rumrunner'\r\n :PlugInstall\r\n\r\nVia Vundle:\r\n\r\n Plugin 'tandrewnichols\/vim-rumrunner'\r\n :BundleInstall\r\n\r\nVia NeoBundle:\r\n\r\n NeoBundle 'tandrewnichols\/vim-rumrunner'\r\n :BundleInstall\r\n\r\nVia Pathogen:\r\n\r\n git clone https:\/\/github.com\/tandrewnichols\/vim-rumrunner.git ~\/.vim\/bundle\/vim-rumrunner","5":"Via Plug:\r\n\r\n Plug 'tandrewnichols\/vim-rumrunner'\r\n :PlugInstall\r\n\r\nVia Vundle:\r\n\r\n Plugin 'tandrewnichols\/vim-rumrunner'\r\n :BundleInstall\r\n\r\nVia NeoBundle:\r\n\r\n NeoBundle 'tandrewnichols\/vim-rumrunner'\r\n :BundleInstall\r\n\r\nVia Pathogen:\r\n\r\n git clone https:\/\/github.com\/tandrewnichols\/vim-rumrunner.git ~\/.vim\/bundle\/vim-rumrunner","first_name":"Andrew","6":"Andrew","last_name":"Nichols","7":"Nichols","releases":[{"0":"5745","vim_version":"8.0","1":"8.0","script_version":"2.0.1","2":"2.0.1","version_comment":"Don't make this plugin dependent on vim-vigor.","3":"Don't make this plugin dependent on vim-vigor.","package":"vim-rumrunner-v2.0.1.tar.gz","4":"vim-rumrunner-v2.0.1.tar.gz","src_id":"26234","5":"26234","creation_date":"1538014474","6":"1538014474"},{"0":"5745","vim_version":"8.0","1":"8.0","script_version":"2.0.0","2":"2.0.0","version_comment":"Adds a Rumrunner buffer for viewing and manipulating the current MRU list. Plus bug fixes.","3":"Adds a Rumrunner buffer for viewing and manipulating the current MRU list. Plus bug fixes.","package":"vim-rumrunner-v2.0.0.tar.gz","4":"vim-rumrunner-v2.0.0.tar.gz","src_id":"26232","5":"26232","creation_date":"1537926742","6":"1537926742"},{"0":"5745","vim_version":"8.0","1":"8.0","script_version":"1.0.1","2":"1.0.1","version_comment":"Fixes some documentation and fixes [r when there's only one entry and it's not the current buffer.","3":"Fixes some documentation and fixes [r when there's only one entry and it's not the current buffer.","package":"vim-rumrunner-1.0.1.tar.gz","4":"vim-rumrunner-1.0.1.tar.gz","src_id":"26230","5":"26230","creation_date":"1537843797","6":"1537843797"},{"0":"5745","vim_version":"8.0","1":"8.0","script_version":"1.0.0","2":"1.0.0","version_comment":"Initial upload","3":"Initial upload","package":"vim-rumrunner-1.0.0.tar.gz","4":"vim-rumrunner-1.0.0.tar.gz","src_id":"26227","5":"26227","creation_date":"1537577174","6":"1537577174"}]},"5744":{"script_id":"5744","0":"5744","script_name":"devops.vim","1":"devops.vim","script_type":"utility","2":"utility","summary":"DevOps ide for VIM","3":"DevOps ide for VIM","description":"DevOps ide for VIM. This plugin provides some useful tools for DevOps developers.","4":"DevOps ide for VIM. This plugin provides some useful tools for DevOps developers.","install_details":"","5":"","first_name":"suren","6":"suren","last_name":"yufu","7":"yufu","releases":[{"0":"5744","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"devops.vim.tar.gz","4":"devops.vim.tar.gz","src_id":"26224","5":"26224","creation_date":"1536834714","6":"1536834714"}]},"5743":{"script_id":"5743","0":"5743","script_name":"squeeze_repeat_blanks.vim","1":"squeeze_repeat_blanks.vim","script_type":"utility","2":"utility","summary":"Squeeze repeated blank lines into one","3":"Squeeze repeated blank lines into one","description":"This plugin provides a user command to reduce multiple blank lines to the last blank line in that group, for the given range or the whole buffer by default. What constitutes a \"blank\" line is configurable per-buffer.\r\n\r\nhttps:\/\/dev.sanctum.geek.nz\/cgit\/vim-squeeze-repeat-blanks.git\/","4":"This plugin provides a user command to reduce multiple blank lines to the last blank line in that group, for the given range or the whole buffer by default. What constitutes a \"blank\" line is configurable per-buffer.\r\n\r\nhttps:\/\/dev.sanctum.geek.nz\/cgit\/vim-squeeze-repeat-blanks.git\/","install_details":"Drop plugin\/squeeze_repeat_blanks.vim in your ~\/.vim\/plugin directory, and autoload\/squeeze_repeat_blanks.vim in ~\/.vim\/autoload. Add doc\/squeeze_repeat_blanks.txt in ~\/.vim\/doc if you want the help file. Otherwise, use your favourite Vim plugin package manager.\r\n","5":"Drop plugin\/squeeze_repeat_blanks.vim in your ~\/.vim\/plugin directory, and autoload\/squeeze_repeat_blanks.vim in ~\/.vim\/autoload. Add doc\/squeeze_repeat_blanks.txt in ~\/.vim\/doc if you want the help file. Otherwise, use your favourite Vim plugin package manager.\r\n","first_name":"Tom","6":"Tom","last_name":"Ryder","7":"Ryder","releases":[{"0":"5743","vim_version":"7.0","1":"7.0","script_version":"0.1.1","2":"0.1.1","version_comment":"Initial upload","3":"Initial upload","package":"vim-squeeze-repeat-blanks-0.1.1.tar.gz","4":"vim-squeeze-repeat-blanks-0.1.1.tar.gz","src_id":"26219","5":"26219","creation_date":"1536222753","6":"1536222753"}]},"5742":{"script_id":"5742","0":"5742","script_name":"replace_operator.vim","1":"replace_operator.vim","script_type":"utility","2":"utility","summary":"Replace text from register with a motion","3":"Replace text from register with a motion","description":"This plugin provides normal and visual mode mapping targets to replace the text bounded by a motion with the contents of a register, by default the unnamed register.\r\n\r\nThis allows you, for example, to select a set of lines and replace any other set of lines with it in one repeatable operation. The text you replace stacks up in the numbered registers as normal, if you do end up needing it back.\r\n\r\nhttps:\/\/dev.sanctum.geek.nz\/cgit\/vim-replace-operator.git\/\r\n","4":"This plugin provides normal and visual mode mapping targets to replace the text bounded by a motion with the contents of a register, by default the unnamed register.\r\n\r\nThis allows you, for example, to select a set of lines and replace any other set of lines with it in one repeatable operation. The text you replace stacks up in the numbered registers as normal, if you do end up needing it back.\r\n\r\nhttps:\/\/dev.sanctum.geek.nz\/cgit\/vim-replace-operator.git\/\r\n","install_details":"Drop plugin\/replace_operator.vim in your ~\/.vim\/plugin directory, and autoload\/replace_operator.vim in ~\/.vim\/autoload. Add doc\/replace_operator.txt in ~\/.vim\/doc if you want the help file. Otherwise, use your favourite Vim plugin package manager. \r\n\r\nThe normal and visual mode mapping targets are both named\r\n(RepeatOperator). There are no default key mappings; you should define\r\nsome yourself in your vimrc. For example:\r\n\r\n nmap r (ReplaceOperator)\r\n xmap r (ReplaceOperator)","5":"Drop plugin\/replace_operator.vim in your ~\/.vim\/plugin directory, and autoload\/replace_operator.vim in ~\/.vim\/autoload. Add doc\/replace_operator.txt in ~\/.vim\/doc if you want the help file. Otherwise, use your favourite Vim plugin package manager. \r\n\r\nThe normal and visual mode mapping targets are both named\r\n(RepeatOperator). There are no default key mappings; you should define\r\nsome yourself in your vimrc. For example:\r\n\r\n nmap r (ReplaceOperator)\r\n xmap r (ReplaceOperator)","first_name":"Tom","6":"Tom","last_name":"Ryder","7":"Ryder","releases":[{"0":"5742","vim_version":"7.0","1":"7.0","script_version":"1.0.2","2":"1.0.2","version_comment":"Switch to much simpler expression-mapping and visual replacement approach","3":"Switch to much simpler expression-mapping and visual replacement approach","package":"vim-replace-operator-1.0.2.tar.gz","4":"vim-replace-operator-1.0.2.tar.gz","src_id":"26311","5":"26311","creation_date":"1546113535","6":"1546113535"}]},"5741":{"script_id":"5741","0":"5741","script_name":"colon_operator.vim","1":"colon_operator.vim","script_type":"utility","2":"utility","summary":"Use colon commands with motions","3":"Use colon commands with motions","description":"This plugin provides a mapping target to use an Ex command as an operator, in a way repeatable with the . (dot) operator. This allows you to, for example, :sort a text object like a paragraph, and then repeat it on another paragraph. Think of it as the : analogue to the ! motion.\r\n\r\nhttps:\/\/sanctum.geek.nz\/cgit\/vim-colon-operator.git\/","4":"This plugin provides a mapping target to use an Ex command as an operator, in a way repeatable with the . (dot) operator. This allows you to, for example, :sort a text object like a paragraph, and then repeat it on another paragraph. Think of it as the : analogue to the ! motion.\r\n\r\nhttps:\/\/sanctum.geek.nz\/cgit\/vim-colon-operator.git\/","install_details":"Drop plugin\/colon_operator.vim in your ~\/.vim\/plugin directory, and autoload\/colon_operator.vim in ~\/.vim\/autoload. Add doc\/colon_operator.txt in ~\/.vim\/doc if you want the help file. Otherwise, use your favourite Vim plugin package manager. \r\n\r\nThe single normal mode mapping target is (ColonOperator). There is no default key mapping; you should define one yourself in your vimrc. For example:\r\n\r\n nmap g: (ColonOperator)","5":"Drop plugin\/colon_operator.vim in your ~\/.vim\/plugin directory, and autoload\/colon_operator.vim in ~\/.vim\/autoload. Add doc\/colon_operator.txt in ~\/.vim\/doc if you want the help file. Otherwise, use your favourite Vim plugin package manager. \r\n\r\nThe single normal mode mapping target is (ColonOperator). There is no default key mapping; you should define one yourself in your vimrc. For example:\r\n\r\n nmap g: (ColonOperator)","first_name":"Tom","6":"Tom","last_name":"Ryder","7":"Ryder","releases":[{"0":"5741","vim_version":"7.0","1":"7.0","script_version":"0.5.0","2":"0.5.0","version_comment":"Code and documentation refactoring and cleanup, no significant usage changes","3":"Code and documentation refactoring and cleanup, no significant usage changes","package":"vim-colon-operator-0.5.0.tar.gz","4":"vim-colon-operator-0.5.0.tar.gz","src_id":"27578","5":"27578","creation_date":"1619203288","6":"1619203288"}]},"5740":{"script_id":"5740","0":"5740","script_name":"cursorline_current.vim","1":"cursorline_current.vim","script_type":"utility","2":"utility","summary":"Show cursorline only in active window","3":"Show cursorline only in active window","description":"This plugin tweaks the behaviour of the 'cursorline' and 'cursorcolumn' options to enable them only in the current window, when not in insert mode, and\/or when Vim has focus.\r\n\r\nIn its default configuration, it essentially makes 'cursorline' and 'cursorcolumn' follow the cursor around in normal mode as much as possible. It uses each window's global value of both options as its default, so setting each option in your |vimrc| before the plugin loads should do the trick.\r\n\r\nhttps:\/\/dev.sanctum.geek.nz\/cgit\/vim-cursorline-current.git\/","4":"This plugin tweaks the behaviour of the 'cursorline' and 'cursorcolumn' options to enable them only in the current window, when not in insert mode, and\/or when Vim has focus.\r\n\r\nIn its default configuration, it essentially makes 'cursorline' and 'cursorcolumn' follow the cursor around in normal mode as much as possible. It uses each window's global value of both options as its default, so setting each option in your |vimrc| before the plugin loads should do the trick.\r\n\r\nhttps:\/\/dev.sanctum.geek.nz\/cgit\/vim-cursorline-current.git\/","install_details":"Drop plugin\/cursorline_current.vim in your ~\/.vim\/plugin directory. Add doc\/cursorline_current.txt in ~\/.vim\/doc if you want the help file. Otherwise, use your favourite Vim plugin package manager.","5":"Drop plugin\/cursorline_current.vim in your ~\/.vim\/plugin directory. Add doc\/cursorline_current.txt in ~\/.vim\/doc if you want the help file. Otherwise, use your favourite Vim plugin package manager.","first_name":"Tom","6":"Tom","last_name":"Ryder","7":"Ryder","releases":[{"0":"5740","vim_version":"7.0","1":"7.0","script_version":"3.0.0","2":"3.0.0","version_comment":"Rewrite adding 'cursorcolumn' support, more options controlling behaviour, resumes sessions without changing window","3":"Rewrite adding 'cursorcolumn' support, more options controlling behaviour, resumes sessions without changing window","package":"vim-cursorline-current-3.0.0.tar.gz","4":"vim-cursorline-current-3.0.0.tar.gz","src_id":"26552","5":"26552","creation_date":"1561051499","6":"1561051499"}]},"5739":{"script_id":"5739","0":"5739","script_name":"EXtend","1":"EXtend","script_type":"utility","2":"utility","summary":" When the Ex commands evolve into operators ","3":" When the Ex commands evolve into operators ","description":"Some commands like :substitute and :global are extremely powerfull, but with that great power comes a lot of trouble. The dealing with regular expressions, with search of complete words or free text, the case-sensitiveness, magicness, line ranges that we can't visualize and most importantly, the fact that these commands can't be applied as if they were operators are just some of the points that make these Ex commands so awkward to use in the common workflow.\r\n\r\nIn response of all that concerns comes EXtend.vim, that provides the functionality of those venerable Ex commands packed into easy to use operators, a highlight system that provides visual feedback by shows the range of operation and the text to be operated in the fly and an steroids-provided input line with two virtual cursors: one for editing the text you type as in any other input line, and a second one that moves over the text of the buffer and lets you pick up words from it and insert them on the input line.\r\n\r\nTake all that and add the ability to customize every color, keystroke and mapping to your own needs and you got a tool that can easily merge into your vim workflow and make your life much easier.","4":"Some commands like :substitute and :global are extremely powerfull, but with that great power comes a lot of trouble. The dealing with regular expressions, with search of complete words or free text, the case-sensitiveness, magicness, line ranges that we can't visualize and most importantly, the fact that these commands can't be applied as if they were operators are just some of the points that make these Ex commands so awkward to use in the common workflow.\r\n\r\nIn response of all that concerns comes EXtend.vim, that provides the functionality of those venerable Ex commands packed into easy to use operators, a highlight system that provides visual feedback by shows the range of operation and the text to be operated in the fly and an steroids-provided input line with two virtual cursors: one for editing the text you type as in any other input line, and a second one that moves over the text of the buffer and lets you pick up words from it and insert them on the input line.\r\n\r\nTake all that and add the ability to customize every color, keystroke and mapping to your own needs and you got a tool that can easily merge into your vim workflow and make your life much easier.","install_details":"If using pathogen, just extract the files in your vim directory.","5":"If using pathogen, just extract the files in your vim directory.","first_name":"Saul Axel","6":"Saul Axel","last_name":"Mart\u00c3\u00adnez Ortiz","7":"Mart\u00c3\u00adnez Ortiz","releases":[{"0":"5739","vim_version":"7.0","1":"7.0","script_version":"0.2","2":"0.2","version_comment":"Initial upload","3":"Initial upload","package":"EXtend.vim-0.2.zip","4":"EXtend.vim-0.2.zip","src_id":"26199","5":"26199","creation_date":"1535894310","6":"1535894310"}]},"5738":{"script_id":"5738","0":"5738","script_name":"rle.vim","1":"rle.vim","script_type":"syntax","2":"syntax","summary":"Hyperion Financial Management (HFM) rule syntax file","3":"Hyperion Financial Management (HFM) rule syntax file","description":"Hyperion Financial Management (HFM) rule syntax file, should be up-to-date with all features of HFM 11. If anything is missing, broken, not working well on your setup, or an inconvenience for you, please let me know, all feedback is welcome: .\r\n\r\nScreenshots:\r\n-------------\r\nhttps:\/\/www.flickr.com\/photos\/yyq123\/30529478388\/","4":"Hyperion Financial Management (HFM) rule syntax file, should be up-to-date with all features of HFM 11. If anything is missing, broken, not working well on your setup, or an inconvenience for you, please let me know, all feedback is welcome: .\r\n\r\nScreenshots:\r\n-------------\r\nhttps:\/\/www.flickr.com\/photos\/yyq123\/30529478388\/","install_details":"1. Copy rle.vim to: ~\/.vim\/syntax\/rle.vim or\r\n$VIMFILES\\syntax\\rle.vim\r\n\r\n2. Add the following ommands to your vimrc file:\r\naugroup filetypedetect\r\n au BufNewFile,BufRead *.rle setfiletype rle\r\naugroup END","5":"1. Copy rle.vim to: ~\/.vim\/syntax\/rle.vim or\r\n$VIMFILES\\syntax\\rle.vim\r\n\r\n2. Add the following ommands to your vimrc file:\r\naugroup filetypedetect\r\n au BufNewFile,BufRead *.rle setfiletype rle\r\naugroup END","first_name":"Anthony","6":"Anthony","last_name":"Yuan","7":"Yuan","releases":[{"0":"5738","vim_version":"7.0","1":"7.0","script_version":"1","2":"1","version_comment":"Initial upload","3":"Initial upload","package":"rle.vim","4":"rle.vim","src_id":"26198","5":"26198","creation_date":"1535808481","6":"1535808481"}]},"5737":{"script_id":"5737","0":"5737","script_name":"vim-eyaml-gpg","1":"vim-eyaml-gpg","script_type":"ftplugin","2":"ftplugin","summary":"Plugin to fold gpg encrypted blocks managed by eyaml.","3":"Plugin to fold gpg encrypted blocks managed by eyaml.","description":"Development is here https:\/\/github.com\/ccdale\/vim-eyaml-gpg\r\n\r\nUsage\r\n\r\nwhen opening a yaml format file that has encrypted blocks managed by eyaml this plugin attempts to detect them and creates manual folds of them. You can open the fold by putting the cursor on the fold and typing za. The same key sequence will close the fold again.\r\n\r\nDecrypting\r\n\r\nYou can decrypt the encrypted block with d (localleader is '\\' on my system). The decrypted value is placed onto the message tree and should appear on the vim command line. Should it have scrolled off, or not show you the 'Press Enter to continue' message, you can view it with :messages.\r\n\r\nThe decryption uses a tempory buffer, completely in memory, so nothing is written to disk. It is destroyed immediately after decrypting. The registers used to pass encrypted and decrypted strings around are reset to the values they had before decryption started, so there is no chance of the data being written out to any .viminfo files.\r\nversions\r\n\r\nTested on ubuntu 16.04 with:\r\n\r\n GNU coreutils base64 8.25\r\n GnuPG 1.4.20\r\n\r\nubuntu 18.04 with:\r\n\r\n GNU coreutils base64 8.28\r\n GnuPg 2.2.4\r\n","4":"Development is here https:\/\/github.com\/ccdale\/vim-eyaml-gpg\r\n\r\nUsage\r\n\r\nwhen opening a yaml format file that has encrypted blocks managed by eyaml this plugin attempts to detect them and creates manual folds of them. You can open the fold by putting the cursor on the fold and typing za. The same key sequence will close the fold again.\r\n\r\nDecrypting\r\n\r\nYou can decrypt the encrypted block with d (localleader is '\\' on my system). The decrypted value is placed onto the message tree and should appear on the vim command line. Should it have scrolled off, or not show you the 'Press Enter to continue' message, you can view it with :messages.\r\n\r\nThe decryption uses a tempory buffer, completely in memory, so nothing is written to disk. It is destroyed immediately after decrypting. The registers used to pass encrypted and decrypted strings around are reset to the values they had before decryption started, so there is no chance of the data being written out to any .viminfo files.\r\nversions\r\n\r\nTested on ubuntu 16.04 with:\r\n\r\n GNU coreutils base64 8.25\r\n GnuPG 1.4.20\r\n\r\nubuntu 18.04 with:\r\n\r\n GNU coreutils base64 8.28\r\n GnuPg 2.2.4\r\n","install_details":"use pathogen (https:\/\/github.com\/tpope\/vim-pathogen) to manage your plugins.\r\n\r\ngit clone this repo into `$HOME\/.vim\/bundle\/\r\n\r\nrestart vim","5":"use pathogen (https:\/\/github.com\/tpope\/vim-pathogen) to manage your plugins.\r\n\r\ngit clone this repo into `$HOME\/.vim\/bundle\/\r\n\r\nrestart vim","first_name":"Chris","6":"Chris","last_name":"Allison","7":"Allison","releases":[{"0":"5737","vim_version":"7.4","1":"7.4","script_version":"1.0.0","2":"1.0.0","version_comment":"Initial upload","3":"Initial upload","package":"vim-eyaml-gpg-1.0.0.tar.gz","4":"vim-eyaml-gpg-1.0.0.tar.gz","src_id":"26193","5":"26193","creation_date":"1535255535","6":"1535255535"}]},"5736":{"script_id":"5736","0":"5736","script_name":"vim-the-little-commenter","1":"vim-the-little-commenter","script_type":"utility","2":"utility","summary":"This is a little vim plugin to comment single lines using ","3":"This is a little vim plugin to comment single lines using ","description":"This is a little vim plugin to comment single lines using just like in vscode and chrome\r\nIn normal mode press to comment a single line\r\nIn OSX Terminal that key combination is not supported, use instead\r\n\r\n","4":"This is a little vim plugin to comment single lines using just like in vscode and chrome\r\nIn normal mode press to comment a single line\r\nIn OSX Terminal that key combination is not supported, use instead\r\n\r\n","install_details":"Use pathogen and add the directory to bundles\/","5":"Use pathogen and add the directory to bundles\/","first_name":"Daniele","6":"Daniele","last_name":"Piccone","7":"Piccone","releases":[{"0":"5736","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"vim-the-little-commenter-master.zip","4":"vim-the-little-commenter-master.zip","src_id":"26192","5":"26192","creation_date":"1535223817","6":"1535223817"}]},"5735":{"script_id":"5735","0":"5735","script_name":"vim-branch-stack","1":"vim-branch-stack","script_type":"utility","2":"utility","summary":"plugin helping to find the branching path to current line of code","3":"plugin helping to find the branching path to current line of code","description":"vim-branch-stack\r\n================\r\n\r\n*vim-branch-stack* is a Vim plugin helping to find the branching path to current line of code.\r\n\r\nIntroduction\r\n------------\r\n\r\n`vim-branch-stack` plugin is intended to help working on legacy C\/C++ code where\r\nfunctions are long and have many nested branches (`if-else`, `switch-case`,\r\n`try-catch`, `while`, `for`).\r\n\r\n\r\n\r\nUsage\r\n-----\r\n\r\nThe stack is shown in the location window after `BranchStack` command\r\nexecuiton while cursor is placed on the target line.\r\n\r\n#### Example\r\n##### main.cpp\r\n```\r\nint main ()\r\n{\r\n const int meaning = 42;\r\n const int pi_floor = 3;\r\n \r\n if (meaning)\r\n {\r\n if (pi_floor == 4)\r\n {\r\n \/\/ Do the stuff\r\n }\r\n else\r\n {\r\n \/\/ Cursor is here\r\n }\r\n }\r\n \r\n return 0;\r\n}\r\n```\r\n\r\n##### Location window\r\n\r\n```\r\n1 main.cpp |6| if (meaning)\r\n2 main.cpp |12| + else\r\n```\r\n\r\n\r\nLimitations\r\n-----------\r\n\r\nThe plugin has the following limitations:\r\n\r\n * Commented out code is not supported\r\n * `goto` is not supported\r\n * `do-while` is not supported\r\n * Preprocessing is not supported\r\n\r\n\r\nContribution\r\n------------\r\n\r\nSource code and issues are hosted on GitHub:\r\n\r\n```\r\nhttps:\/\/github.com\/aserebryakov\/vim-branch-stack\r\n```\r\n\r\nLicense\r\n-------\r\n\r\n[MIT License](https:\/\/opensource.org\/licenses\/MIT)","4":"vim-branch-stack\r\n================\r\n\r\n*vim-branch-stack* is a Vim plugin helping to find the branching path to current line of code.\r\n\r\nIntroduction\r\n------------\r\n\r\n`vim-branch-stack` plugin is intended to help working on legacy C\/C++ code where\r\nfunctions are long and have many nested branches (`if-else`, `switch-case`,\r\n`try-catch`, `while`, `for`).\r\n\r\n\r\n\r\nUsage\r\n-----\r\n\r\nThe stack is shown in the location window after `BranchStack` command\r\nexecuiton while cursor is placed on the target line.\r\n\r\n#### Example\r\n##### main.cpp\r\n```\r\nint main ()\r\n{\r\n const int meaning = 42;\r\n const int pi_floor = 3;\r\n \r\n if (meaning)\r\n {\r\n if (pi_floor == 4)\r\n {\r\n \/\/ Do the stuff\r\n }\r\n else\r\n {\r\n \/\/ Cursor is here\r\n }\r\n }\r\n \r\n return 0;\r\n}\r\n```\r\n\r\n##### Location window\r\n\r\n```\r\n1 main.cpp |6| if (meaning)\r\n2 main.cpp |12| + else\r\n```\r\n\r\n\r\nLimitations\r\n-----------\r\n\r\nThe plugin has the following limitations:\r\n\r\n * Commented out code is not supported\r\n * `goto` is not supported\r\n * `do-while` is not supported\r\n * Preprocessing is not supported\r\n\r\n\r\nContribution\r\n------------\r\n\r\nSource code and issues are hosted on GitHub:\r\n\r\n```\r\nhttps:\/\/github.com\/aserebryakov\/vim-branch-stack\r\n```\r\n\r\nLicense\r\n-------\r\n\r\n[MIT License](https:\/\/opensource.org\/licenses\/MIT)","install_details":"\r\n#### Requirements\r\n\r\n * python3\r\n\r\n#### Vim 8+\r\n\r\n```\r\n$ cd ~\/.vim\/pack\/directory_name\/start\/\r\n$ git clone --recurse-submodules https:\/\/github.com\/aserebryakov\/vim-branch-stack.git\r\n```\r\n\r\n#### Pathogen\r\n\r\n```\r\n$ cd ~\/.vim\/bundle\r\n$ git clone --recurse-submodules https:\/\/github.com\/aserebryakov\/vim-branch-stack.git\r\n```\r\n\r\n#### NeoBundle\r\n\r\n```\r\nNeoBundle 'aserebryakov\/vim-branch-stack'\r\n```\r\n\r\nWithout plugin manager:\r\n\r\nClone or download this repository and copy its contents to your ~\/.vim\/\r\ndirectory.\r\n\r\n","5":"\r\n#### Requirements\r\n\r\n * python3\r\n\r\n#### Vim 8+\r\n\r\n```\r\n$ cd ~\/.vim\/pack\/directory_name\/start\/\r\n$ git clone --recurse-submodules https:\/\/github.com\/aserebryakov\/vim-branch-stack.git\r\n```\r\n\r\n#### Pathogen\r\n\r\n```\r\n$ cd ~\/.vim\/bundle\r\n$ git clone --recurse-submodules https:\/\/github.com\/aserebryakov\/vim-branch-stack.git\r\n```\r\n\r\n#### NeoBundle\r\n\r\n```\r\nNeoBundle 'aserebryakov\/vim-branch-stack'\r\n```\r\n\r\nWithout plugin manager:\r\n\r\nClone or download this repository and copy its contents to your ~\/.vim\/\r\ndirectory.\r\n\r\n","first_name":"Alexander","6":"Alexander","last_name":"Serebryakov","7":"Serebryakov","releases":[{"0":"5735","vim_version":"8.0","1":"8.0","script_version":"0.1.1","2":"0.1.1","version_comment":"* Fixed handling of single line comments","3":"* Fixed handling of single line comments","package":"vim-branch-stack-0.1.1.zip","4":"vim-branch-stack-0.1.1.zip","src_id":"26194","5":"26194","creation_date":"1535327536","6":"1535327536"},{"0":"5735","vim_version":"8.0","1":"8.0","script_version":"0.1.0","2":"0.1.0","version_comment":"Initial upload","3":"Initial upload","package":"vim-branch-stack-0.1.0.zip","4":"vim-branch-stack-0.1.0.zip","src_id":"26191","5":"26191","creation_date":"1535120279","6":"1535120279"}]},"5734":{"script_id":"5734","0":"5734","script_name":"vim-browser-search","1":"vim-browser-search","script_type":"utility","2":"utility","summary":"A Neovim\/Vim plugin to open your browser and search for text selected in","3":"A Neovim\/Vim plugin to open your browser and search for text selected in","description":"This plugin helps perform a quick web search for the text selected in Vim.\r\n\r\nThis plugin supports many search engines such as Google, GitHub and so on. You can also add your own search engine\r\n\r\n\r\nFor the configuration and more info, see https:\/\/github.com\/voldikss\/vim-browser-search","4":"This plugin helps perform a quick web search for the text selected in Vim.\r\n\r\nThis plugin supports many search engines such as Google, GitHub and so on. You can also add your own search engine\r\n\r\n\r\nFor the configuration and more info, see https:\/\/github.com\/voldikss\/vim-browser-search","install_details":"Use vim-plug:\r\n\r\nPlug 'voldikss\/vim-browser-search'","5":"Use vim-plug:\r\n\r\nPlug 'voldikss\/vim-browser-search'","first_name":"\u6700","6":"最","last_name":"\u4e0a\u5ddd","7":"上川","releases":[{"0":"5734","vim_version":"7.4","1":"7.4","script_version":"1.0.0","2":"1.0.0","version_comment":"Refactor","3":"Refactor","package":"vim-browser-search.tar.gz","4":"vim-browser-search.tar.gz","src_id":"26920","5":"26920","creation_date":"1579040702","6":"1579040702"}]},"5733":{"script_id":"5733","0":"5733","script_name":"vim-pivotal-tracker-jump","1":"vim-pivotal-tracker-jump","script_type":"utility","2":"utility","summary":"Jump to the Pivotal Tracker story under the cursor","3":"Jump to the Pivotal Tracker story under the cursor","description":"Using the GitHub integration, Pivotal Tracker stories can be referenced in Git commit messages like: [#TRACKER_STORY_ID]\r\n\r\nThis plugin adds functionality to `gx`, which normally opens URLs in your default web browser. When the cursor is on a story reference press `gx` to jump to the story in your web browser.\r\n\r\n","4":"Using the GitHub integration, Pivotal Tracker stories can be referenced in Git commit messages like: [#TRACKER_STORY_ID]\r\n\r\nThis plugin adds functionality to `gx`, which normally opens URLs in your default web browser. When the cursor is on a story reference press `gx` to jump to the story in your web browser.\r\n\r\n","install_details":"","5":"","first_name":"Michael","6":"Michael","last_name":"Foley","7":"Foley","releases":[{"0":"5733","vim_version":"5.7","1":"5.7","script_version":"1.1","2":"1.1","version_comment":"Add changeable g:pivotal_tracker_jump_url variable","3":"Add changeable g:pivotal_tracker_jump_url variable","package":"vim-pivotal-tracker-jump.zip","4":"vim-pivotal-tracker-jump.zip","src_id":"26184","5":"26184","creation_date":"1534564892","6":"1534564892"},{"0":"5733","vim_version":"5.7","1":"5.7","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"vim-pivotal-tracker-jump.zip","4":"vim-pivotal-tracker-jump.zip","src_id":"26183","5":"26183","creation_date":"1534489521","6":"1534489521"}]},"5732":{"script_id":"5732","0":"5732","script_name":"Smart Mark","1":"Smart Mark","script_type":"utility","2":"utility","summary":"Display current marks in the buffer","3":"Display current marks in the buffer","description":"Display the marks for a buffer in the gutter. Functionally auto-updates, making sure that there is no desynchronizatoin between the marks displayed, and the current active marks. \r\n\r\nThis script is hosted in the gitlab repo https:\/\/gitlab.com\/Jrahme\/smart-mark, and usage details can be found in the README.md file, though the plugin should work out of the box. \r\n\r\nRequires Vim to have been compiled with the +timers feature. ","4":"Display the marks for a buffer in the gutter. Functionally auto-updates, making sure that there is no desynchronizatoin between the marks displayed, and the current active marks. \r\n\r\nThis script is hosted in the gitlab repo https:\/\/gitlab.com\/Jrahme\/smart-mark, and usage details can be found in the README.md file, though the plugin should work out of the box. \r\n\r\nRequires Vim to have been compiled with the +timers feature. ","install_details":"Untar and place in one of your packages in your vim home; ~\/.vim\/pack\/core\/start for example.","5":"Untar and place in one of your packages in your vim home; ~\/.vim\/pack\/core\/start for example.","first_name":"Jacob","6":"Jacob","last_name":"Rahme","7":"Rahme","releases":[{"0":"5732","vim_version":"8.0","1":"8.0","script_version":"0.0.1","2":"0.0.1","version_comment":"Initial upload","3":"Initial upload","package":"smart-mark.tar.gz","4":"smart-mark.tar.gz","src_id":"26179","5":"26179","creation_date":"1534284562","6":"1534284562"}]},"5731":{"script_id":"5731","0":"5731","script_name":"vim-term","1":"vim-term","script_type":"utility","2":"utility","summary":"Run programs in a terminal via :terminal command.","3":"Run programs in a terminal via :terminal command.","description":"Vim commands to open and run programs in terminal \/ shell with support for nix-shell.\r\nLet you easily reuse terminal window, list (and select) running async jobs. Some examples:\r\n\r\n:Shell - (re)-open shell\r\n:Shell ++termwin - (re)-open shell in current terminal window\r\n\r\n:Term - list async jobs\r\n:Term args - run async job args\r\n:Term ++termwin args - run async job in current terminal window\r\n:Term ++hidden args - run async job, in windowless mode\r\n\r\n:Shell and :Term commands accept all :terminal options (they are convenient wrappers around :terminal command) with a few additional options.\r\n\r\nCheck documentation at https:\/\/github.com\/coot\/vim-term\/blob\/master\/doc\/term.txt","4":"Vim commands to open and run programs in terminal \/ shell with support for nix-shell.\r\nLet you easily reuse terminal window, list (and select) running async jobs. Some examples:\r\n\r\n:Shell - (re)-open shell\r\n:Shell ++termwin - (re)-open shell in current terminal window\r\n\r\n:Term - list async jobs\r\n:Term args - run async job args\r\n:Term ++termwin args - run async job in current terminal window\r\n:Term ++hidden args - run async job, in windowless mode\r\n\r\n:Shell and :Term commands accept all :terminal options (they are convenient wrappers around :terminal command) with a few additional options.\r\n\r\nCheck documentation at https:\/\/github.com\/coot\/vim-term\/blob\/master\/doc\/term.txt","install_details":"","5":"","first_name":"Marcin","6":"Marcin","last_name":"Szamotulski","7":"Szamotulski","releases":[{"0":"5731","vim_version":"8.0","1":"8.0","script_version":"1.0.1","2":"1.0.1","version_comment":"Changed plugin name","3":"Changed plugin name","package":"vim-term-1.0.1.tar.gz","4":"vim-term-1.0.1.tar.gz","src_id":"26178","5":"26178","creation_date":"1534112780","6":"1534112780"}]},"5730":{"script_id":"5730","0":"5730","script_name":"gsql-vim","1":"gsql-vim","script_type":"syntax","2":"syntax","summary":"Syntax highlighting for gsql","3":"Syntax highlighting for gsql","description":"See github for more details: https:\/\/github.com\/jmeekhof\/gsql-vim","4":"See github for more details: https:\/\/github.com\/jmeekhof\/gsql-vim","install_details":"","5":"","first_name":"Josh","6":"Josh","last_name":"Meekhof","7":"Meekhof","releases":[{"0":"5730","vim_version":"7.0","1":"7.0","script_version":"v1.0","2":"v1.0","version_comment":"Initial upload","3":"Initial upload","package":"gsql-vim-1.0.tar.gz","4":"gsql-vim-1.0.tar.gz","src_id":"26159","5":"26159","creation_date":"1533175805","6":"1533175805"}]},"5729":{"script_id":"5729","0":"5729","script_name":"vim-systemverilog-syntax","1":"vim-systemverilog-syntax","script_type":"syntax","2":"syntax","summary":"systemverilog syntax","3":"systemverilog syntax","description":"syntax support for systemverilog language","4":"syntax support for systemverilog language","install_details":"","5":"","first_name":"bravy","6":"bravy","last_name":"wang","7":"wang","releases":[{"0":"5729","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"vim-systemverilog-syntax.zip","4":"vim-systemverilog-syntax.zip","src_id":"26158","5":"26158","creation_date":"1533146688","6":"1533146688"}]},"5728":{"script_id":"5728","0":"5728","script_name":"vim-buffest","1":"vim-buffest","script_type":"utility","2":"utility","summary":"Edit registers and the quickfix\/location list as buffers","3":"Edit registers and the quickfix\/location list as buffers","description":"Allows you to open a representation of registers and the quickfix\/location lists in buffers opened in a new split\/tab.\r\n\r\nAutomatically adds autocommands to these buffers so you can read\/write with commands like `:w`, `:e!`, `ZZ`, etc.\r\n\r\nFor editing registers, it saves time pasting\/yanking\/cleaning up when editing macros or yanked content.\r\nIt can also allow you to easily preview the contents of a register.\r\nFor lists, it adds powerful filtering and creation functionality through built-in vim commands.\r\n\r\nAdds the intuitive bindings `c@{register}` to open a register, `c,q` to open the quickfix list, and `c,l` to open the location list.\r\nEverything is bindable and re-bindable.\r\n\r\nThis command is inspired by emacs and, in my opinion, adds a very simple but powerful feature missing in vim.\r\n\r\nFor some examples, a demo, and the most up-to-date code, see https:\/\/github.com\/rbong\/vim-buffest","4":"Allows you to open a representation of registers and the quickfix\/location lists in buffers opened in a new split\/tab.\r\n\r\nAutomatically adds autocommands to these buffers so you can read\/write with commands like `:w`, `:e!`, `ZZ`, etc.\r\n\r\nFor editing registers, it saves time pasting\/yanking\/cleaning up when editing macros or yanked content.\r\nIt can also allow you to easily preview the contents of a register.\r\nFor lists, it adds powerful filtering and creation functionality through built-in vim commands.\r\n\r\nAdds the intuitive bindings `c@{register}` to open a register, `c,q` to open the quickfix list, and `c,l` to open the location list.\r\nEverything is bindable and re-bindable.\r\n\r\nThis command is inspired by emacs and, in my opinion, adds a very simple but powerful feature missing in vim.\r\n\r\nFor some examples, a demo, and the most up-to-date code, see https:\/\/github.com\/rbong\/vim-buffest","install_details":"","5":"","first_name":"Roger","6":"Roger","last_name":"Bongers","7":"Bongers","releases":[{"0":"5728","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"vim-buffest-1.0.zip","4":"vim-buffest-1.0.zip","src_id":"26155","5":"26155","creation_date":"1533017677","6":"1533017677"}]},"5725":{"script_id":"5725","0":"5725","script_name":"undoquit.vim","1":"undoquit.vim","script_type":"utility","2":"utility","summary":" Undo a :quit -- reopen the last window you closed ","3":" Undo a :quit -- reopen the last window you closed ","description":"Github repo is at: https:\/\/github.com\/AndrewRadev\/undoquit.vim\r\n\r\nWhenever you execute a `:quit` on a window, that window's position is stored in a stack. Pressing `u` (or executing the `:Undoquit` command) is going to \"undo\" that quit, restoring the window to its original position.\r\n\r\nCheck the documentation for more details, corner cases, and settings.","4":"Github repo is at: https:\/\/github.com\/AndrewRadev\/undoquit.vim\r\n\r\nWhenever you execute a `:quit` on a window, that window's position is stored in a stack. Pressing `u` (or executing the `:Undoquit` command) is going to \"undo\" that quit, restoring the window to its original position.\r\n\r\nCheck the documentation for more details, corner cases, and settings.","install_details":"Download undoquit.zip.\r\n\r\nIf you're using pathogen (vimscript #2332), extract it to a directory in your bundles or just clone the git repository at https:\/\/github.com\/AndrewRadev\/undoquit.vim\r\n\r\nAlternatively, extract it to your vimfiles root (~\/.vim on *nix, ~\/vimfiles on Windows).","5":"Download undoquit.zip.\r\n\r\nIf you're using pathogen (vimscript #2332), extract it to a directory in your bundles or just clone the git repository at https:\/\/github.com\/AndrewRadev\/undoquit.vim\r\n\r\nAlternatively, extract it to your vimfiles root (~\/.vim on *nix, ~\/vimfiles on Windows).","first_name":"Andrew","6":"Andrew","last_name":"Radev","7":"Radev","releases":[{"0":"5725","vim_version":"7.4","1":"7.4","script_version":"0.1.0","2":"0.1.0","version_comment":"Initial upload","3":"Initial upload","package":"undoquit.zip","4":"undoquit.zip","src_id":"26137","5":"26137","creation_date":"1531850837","6":"1531850837"}]},"5724":{"script_id":"5724","0":"5724","script_name":"digraph_search.vim","1":"digraph_search.vim","script_type":"utility","2":"utility","summary":"Search for a digraph by name while inserting","3":"Search for a digraph by name while inserting","description":"This plugin provides an insert mode mapping target to search for digraphs by searching for a substring of the character's official name, per :help digraph-table and :help digraph-table-multibyte. This is for situations where you might be able to remember part of the official name for a character, but you can't remember the digraph pieces.\r\n\r\nhttps:\/\/dev.sanctum.geek.nz\/cgit\/vim-digraph-search.git\/","4":"This plugin provides an insert mode mapping target to search for digraphs by searching for a substring of the character's official name, per :help digraph-table and :help digraph-table-multibyte. This is for situations where you might be able to remember part of the official name for a character, but you can't remember the digraph pieces.\r\n\r\nhttps:\/\/dev.sanctum.geek.nz\/cgit\/vim-digraph-search.git\/","install_details":"Drop plugin\/digraph_search.vim in your ~\/.vim\/plugin directory and autoload\/digraph_search.vim in ~\/.vim\/autoload. Add doc\/digraph_search.txt in ~\/.vim\/doc if you want the help file. Otherwise, use your favourite Vim plugin package manager.\r\n","5":"Drop plugin\/digraph_search.vim in your ~\/.vim\/plugin directory and autoload\/digraph_search.vim in ~\/.vim\/autoload. Add doc\/digraph_search.txt in ~\/.vim\/doc if you want the help file. Otherwise, use your favourite Vim plugin package manager.\r\n","first_name":"Tom","6":"Tom","last_name":"Ryder","7":"Ryder","releases":[{"0":"5724","vim_version":"7.0","1":"7.0","script_version":"0.1.2","2":"0.1.2","version_comment":"Correct mapping flags","3":"Correct mapping flags","package":"vim-digraph-search-0.1.2.tar.gz","4":"vim-digraph-search-0.1.2.tar.gz","src_id":"26148","5":"26148","creation_date":"1532623588","6":"1532623588"}]},"5723":{"script_id":"5723","0":"5723","script_name":"insert_timeout.vim","1":"insert_timeout.vim","script_type":"utility","2":"utility","summary":"Leave insert mode after a period of inactivity","3":"Leave insert mode after a period of inactivity","description":"This plugin leaves insert mode automatically if there is no activity for a certain number of seconds, with an 'updatetime' hook. This is just a plugin packaging of vimtip #1540.\r\n\r\nhttps:\/\/dev.sanctum.geek.nz\/cgit\/vim-insert-timeout.git\/","4":"This plugin leaves insert mode automatically if there is no activity for a certain number of seconds, with an 'updatetime' hook. This is just a plugin packaging of vimtip #1540.\r\n\r\nhttps:\/\/dev.sanctum.geek.nz\/cgit\/vim-insert-timeout.git\/","install_details":"Drop plugin\/insert_timeout.vim in your ~\/.vim\/plugin directory. Add doc\/insert_timeout.txt in ~\/.vim\/doc if you want the help file. Otherwise, use your favourite Vim plugin package manager. ","5":"Drop plugin\/insert_timeout.vim in your ~\/.vim\/plugin directory. Add doc\/insert_timeout.txt in ~\/.vim\/doc if you want the help file. Otherwise, use your favourite Vim plugin package manager. ","first_name":"Tom","6":"Tom","last_name":"Ryder","7":"Ryder","releases":[{"0":"5723","vim_version":"7.0","1":"7.0","script_version":"0.2.1","2":"0.2.1","version_comment":"Initial upload","3":"Initial upload","package":"vim-insert-timeout-0.2.1.tar.gz","4":"vim-insert-timeout-0.2.1.tar.gz","src_id":"26129","5":"26129","creation_date":"1531384986","6":"1531384986"}]},"5722":{"script_id":"5722","0":"5722","script_name":"jsonpath","1":"jsonpath","script_type":"utility","2":"utility","summary":"Navigate JSON documents using dot.notation.paths","3":"Navigate JSON documents using dot.notation.paths","description":"Provides the :JsonPath command which does two things:\r\n:JsonPath - Echoes the path to the identifier under the cursor.\r\n:JsonPath path.to.prop - Searches the active buffer for the given path, placing the cursor on it if found.\r\n\r\nBug reports, feature requests, patches and other feedback is appreciated and can be posted to GitHub:\r\nhttps:\/\/github.com\/mogelbrod\/vim-jsonpath\r\nGitHub is also where you are guaranteed to find the latest version.","4":"Provides the :JsonPath command which does two things:\r\n:JsonPath - Echoes the path to the identifier under the cursor.\r\n:JsonPath path.to.prop - Searches the active buffer for the given path, placing the cursor on it if found.\r\n\r\nBug reports, feature requests, patches and other feedback is appreciated and can be posted to GitHub:\r\nhttps:\/\/github.com\/mogelbrod\/vim-jsonpath\r\nGitHub is also where you are guaranteed to find the latest version.","install_details":"The recommended way to install this plugin is using Vundle, pathogen.vim or another Vim package manager.\r\nIf you do not wish to use any of them, simply extract the archive to ~\/.vim (~\\vimfiles on Windows).\r\n","5":"The recommended way to install this plugin is using Vundle, pathogen.vim or another Vim package manager.\r\nIf you do not wish to use any of them, simply extract the archive to ~\/.vim (~\\vimfiles on Windows).\r\n","first_name":"Victor","6":"Victor","last_name":"Hallberg","7":"Hallberg","releases":[{"0":"5722","vim_version":"8.0","1":"8.0","script_version":"v0.5.2","2":"v0.5.2","version_comment":"- Avoid error if from_line is less than 1\r\n- Avoid printing goto() outcome on the same line as input","3":"- Avoid error if from_line is less than 1\r\n- Avoid printing goto() outcome on the same line as input","package":"vim-jsonpath-0.5.2.zip","4":"vim-jsonpath-0.5.2.zip","src_id":"27204","5":"27204","creation_date":"1592347122","6":"1592347122"},{"0":"5722","vim_version":"7.0","1":"7.0","script_version":"v0.5.0","2":"v0.5.0","version_comment":"New recommended mapping syntax + parser fixes","3":"New recommended mapping syntax + parser fixes","package":"vim-jsonpath-0.5.0.zip","4":"vim-jsonpath-0.5.0.zip","src_id":"27194","5":"27194","creation_date":"1591391651","6":"1591391651"},{"0":"5722","vim_version":"7.0","1":"7.0","script_version":"v0.4.1","2":"v0.4.1","version_comment":"Fixed parsing bugs + enables range support for the JsonPath command.","3":"Fixed parsing bugs + enables range support for the JsonPath command.","package":"vim-jsonpath-0.4.1.zip","4":"vim-jsonpath-0.4.1.zip","src_id":"27188","5":"27188","creation_date":"1591293497","6":"1591293497"},{"0":"5722","vim_version":"7.4","1":"7.4","script_version":"v0.3.0","2":"v0.3.0","version_comment":"Add an optional python implementation of the existing JSON scanning algorithm. Using it greatly reduces scanning time (~0.5s vs 19.5s for a 330kb json file).","3":"Add an optional python implementation of the existing JSON scanning algorithm. Using it greatly reduces scanning time (~0.5s vs 19.5s for a 330kb json file).","package":"vim-jsonpath-0.3.0.zip","4":"vim-jsonpath-0.3.0.zip","src_id":"27164","5":"27164","creation_date":"1589785657","6":"1589785657"},{"0":"5722","vim_version":"7.0","1":"7.0","script_version":"v0.2.0","2":"v0.2.0","version_comment":"Add g:jsonpath_register option allowing automatic yanking of path to a register when calling :JsonPath (or jsonpath#echo())","3":"Add g:jsonpath_register option allowing automatic yanking of path to a register when calling :JsonPath (or jsonpath#echo())","package":"vim-jsonpath-0.2.0.zip","4":"vim-jsonpath-0.2.0.zip","src_id":"26682","5":"26682","creation_date":"1564442002","6":"1564442002"},{"0":"5722","vim_version":"7.0","1":"7.0","script_version":"0.1.0","2":"0.1.0","version_comment":"Initial upload","3":"Initial upload","package":"vim-jsonpath-master.zip","4":"vim-jsonpath-master.zip","src_id":"26123","5":"26123","creation_date":"1531189080","6":"1531189080"}]},"5721":{"script_id":"5721","0":"5721","script_name":"git-backups","1":"git-backups","script_type":"utility","2":"utility","summary":"uses git to back up all files","3":"uses git to back up all files","description":"uses git to back up all files\r\n\r\ninspired by https:\/\/www.reddit.com\/r\/vim\/comments\/8w3udw\/topnotch_vim_file_backup_history_with_no_plugins\/","4":"uses git to back up all files\r\n\r\ninspired by https:\/\/www.reddit.com\/r\/vim\/comments\/8w3udw\/topnotch_vim_file_backup_history_with_no_plugins\/","install_details":"","5":"","first_name":"Travis","6":"Travis","last_name":"Cline","7":"Cline","releases":[{"0":"5721","vim_version":"8.0","1":"8.0","script_version":"0.2","2":"0.2","version_comment":"rename file, change default dir","3":"rename file, change default dir","package":"git-backups.vim","4":"git-backups.vim","src_id":"26113","5":"26113","creation_date":"1530974831","6":"1530974831"}]},"5720":{"script_id":"5720","0":"5720","script_name":"perl_version_bump.vim","1":"perl_version_bump.vim","script_type":"ftplugin","2":"ftplugin","summary":"Increment Perl version numbers","3":"Increment Perl version numbers","description":"This filetype plugin for Perl code (\"perl\" filetype) provides buffer-local mapping targets for normal mode to increment either the major or minor version number of a package-scoped $VERSION assignment.\r\n\r\nSo with this format:\r\n\r\n our $VERSION = '1.23';\r\n\r\nKeying a map to (PerlVersionBumpMinor) would yield:\r\n\r\n our $VERSION = '1.24';\r\n\r\nKeying a map to (PerlVersionBumpMajor) would yield:\r\n\r\n our $VERSION = '2.00';\r\n\r\nThere is no support for development versions with underscore prefixes like 1.23_001 (yet).\r\n\r\nhttps:\/\/dev.sanctum.geek.nz\/cgit\/vim-perl-version-bump.git\r\n","4":"This filetype plugin for Perl code (\"perl\" filetype) provides buffer-local mapping targets for normal mode to increment either the major or minor version number of a package-scoped $VERSION assignment.\r\n\r\nSo with this format:\r\n\r\n our $VERSION = '1.23';\r\n\r\nKeying a map to (PerlVersionBumpMinor) would yield:\r\n\r\n our $VERSION = '1.24';\r\n\r\nKeying a map to (PerlVersionBumpMajor) would yield:\r\n\r\n our $VERSION = '2.00';\r\n\r\nThere is no support for development versions with underscore prefixes like 1.23_001 (yet).\r\n\r\nhttps:\/\/dev.sanctum.geek.nz\/cgit\/vim-perl-version-bump.git\r\n","install_details":"This should probably be saved as ~\/.vim\/after\/ftplugin\/perl\/version_bump.vim (per the distribution layout) or ~\/.vim\/after\/ftplugin\/perl_version_bump.vim (if you prefer), so that it definitely loads *after* the primary perl.vim plugin. Save the autoload file in ~\/.vim\/autoload\/perl\/version\/bump.vim. Or, just use your favourite Vim plugin manager.","5":"This should probably be saved as ~\/.vim\/after\/ftplugin\/perl\/version_bump.vim (per the distribution layout) or ~\/.vim\/after\/ftplugin\/perl_version_bump.vim (if you prefer), so that it definitely loads *after* the primary perl.vim plugin. Save the autoload file in ~\/.vim\/autoload\/perl\/version\/bump.vim. Or, just use your favourite Vim plugin manager.","first_name":"Tom","6":"Tom","last_name":"Ryder","7":"Ryder","releases":[{"0":"5720","vim_version":"7.0","1":"7.0","script_version":"1.0.0","2":"1.0.0","version_comment":"Parenthesize map names","3":"Parenthesize map names","package":"vim-perl-version-bump-1.0.0.tar.gz","4":"vim-perl-version-bump-1.0.0.tar.gz","src_id":"26215","5":"26215","creation_date":"1536221665","6":"1536221665"}]},"5719":{"script_id":"5719","0":"5719","script_name":"simpleterm.vim","1":"simpleterm.vim","script_type":"utility","2":"utility","summary":"simple terminal in vim","3":"simple terminal in vim","description":"See https:\/\/github.com\/gu-fan\/simpleterm.vim","4":"See https:\/\/github.com\/gu-fan\/simpleterm.vim","install_details":"Require\r\nVim 8.1+ with +terminal\r\n\r\nInstall\r\nPlug 'gu-fan\/simpleterm.vim'\r\n","5":"Require\r\nVim 8.1+ with +terminal\r\n\r\nInstall\r\nPlug 'gu-fan\/simpleterm.vim'\r\n","first_name":"gu","6":"gu","last_name":"fan","7":"fan","releases":[{"0":"5719","vim_version":"8.0","1":"8.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"simpleterm.vim-master.zip","4":"simpleterm.vim-master.zip","src_id":"26105","5":"26105","creation_date":"1530685299","6":"1530685299"}]},"5718":{"script_id":"5718","0":"5718","script_name":"require.vim","1":"require.vim","script_type":"utility","2":"utility","summary":"require vim easy","3":"require vim easy","description":"See https:\/\/github.com\/gu-fan\/require.vim","4":"See https:\/\/github.com\/gu-fan\/require.vim","install_details":"Plug 'gu-fan\/require.vim'","5":"Plug 'gu-fan\/require.vim'","first_name":"gu","6":"gu","last_name":"fan","7":"fan","releases":[{"0":"5718","vim_version":"8.0","1":"8.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"require.vim-master.zip","4":"require.vim-master.zip","src_id":"26104","5":"26104","creation_date":"1530685077","6":"1530685077"}]},"5717":{"script_id":"5717","0":"5717","script_name":"insert_cancel.vim","1":"insert_cancel.vim","script_type":"utility","2":"utility","summary":"Cancel an insert mode operation","3":"Cancel an insert mode operation","description":"This plugin provides a mapping target to cancel an insert operation. It leaves insert mode normally, firing InsertLeave, and then runs :undo if the buffer was changed by the insert. This is intended as a remap of Ctrl-C in insert mode.\r\n\r\nhttps:\/\/dev.sanctum.geek.nz\/cgit\/vim-insert-cancel.git\/","4":"This plugin provides a mapping target to cancel an insert operation. It leaves insert mode normally, firing InsertLeave, and then runs :undo if the buffer was changed by the insert. This is intended as a remap of Ctrl-C in insert mode.\r\n\r\nhttps:\/\/dev.sanctum.geek.nz\/cgit\/vim-insert-cancel.git\/","install_details":"Drop plugin\/insert_cancel.vim in your ~\/.vim\/plugin directory. Add doc\/insert_cancel.txt in ~\/.vim\/doc if you want the help file. Otherwise, use your favourite Vim plugin package manager.\r\n\r\nTo remap insert CTRL-C to use this instead of its default function, you could put this in your vimrc:\r\n\r\n imap (InsertCancel)","5":"Drop plugin\/insert_cancel.vim in your ~\/.vim\/plugin directory. Add doc\/insert_cancel.txt in ~\/.vim\/doc if you want the help file. Otherwise, use your favourite Vim plugin package manager.\r\n\r\nTo remap insert CTRL-C to use this instead of its default function, you could put this in your vimrc:\r\n\r\n imap (InsertCancel)","first_name":"Tom","6":"Tom","last_name":"Ryder","7":"Ryder","releases":[{"0":"5717","vim_version":"7.0","1":"7.0","script_version":"3.1.1","2":"3.1.1","version_comment":"Use BufEnter event for setup","3":"Use BufEnter event for setup","package":"vim-insert-cancel-3.1.1.tar.gz","4":"vim-insert-cancel-3.1.1.tar.gz","src_id":"26214","5":"26214","creation_date":"1536221614","6":"1536221614"}]},"5716":{"script_id":"5716","0":"5716","script_name":"cmdwin_ctrlc.vim","1":"cmdwin_ctrlc.vim","script_type":"utility","2":"utility","summary":"Tweak CTRL-C command line window behavior to be a bit more useful","3":"Tweak CTRL-C command line window behavior to be a bit more useful","description":"This plugin tweaks CTRL-C in cmdline-window mode to close the command line window and insert the command or search line the cursor was on at a new command of the appropriate type, with the cursor at the end of the line.\r\n\r\nhttps:\/\/dev.sanctum.geek.nz\/cgit\/vim-cmdwin-ctrlc.git","4":"This plugin tweaks CTRL-C in cmdline-window mode to close the command line window and insert the command or search line the cursor was on at a new command of the appropriate type, with the cursor at the end of the line.\r\n\r\nhttps:\/\/dev.sanctum.geek.nz\/cgit\/vim-cmdwin-ctrlc.git","install_details":"Drop plugin\/cmdwin_ctrlc.vim in your ~\/.vim\/plugin directory. Add doc\/cmdwin_ctrlc.txt in ~\/.vim\/doc if you want the help file. Otherwise, use your favourite Vim plugin package manager.","5":"Drop plugin\/cmdwin_ctrlc.vim in your ~\/.vim\/plugin directory. Add doc\/cmdwin_ctrlc.txt in ~\/.vim\/doc if you want the help file. Otherwise, use your favourite Vim plugin package manager.","first_name":"Tom","6":"Tom","last_name":"Ryder","7":"Ryder","releases":[{"0":"5716","vim_version":"7.0","1":"7.0","script_version":"0.2.1","2":"0.2.1","version_comment":"Fix function scope","3":"Fix function scope","package":"vim-cmdwin-ctrlc-0.2.1.tar.gz","4":"vim-cmdwin-ctrlc-0.2.1.tar.gz","src_id":"26128","5":"26128","creation_date":"1531384504","6":"1531384504"}]},"5715":{"script_id":"5715","0":"5715","script_name":"make_target.vim","1":"make_target.vim","script_type":"ftplugin","2":"ftplugin","summary":"Make target for Makefile recipe under cursor","3":"Make target for Makefile recipe under cursor","description":"This filetype plugin for Makefiles (\"make\" filetype) provides an autoload function make#target#Make() and buffer-local mapping (MakeTarget) to make! the target for the recipe under the cursor, if it can be identified.\r\n\r\nhttps:\/\/dev.sanctum.geek.nz\/cgit\/vim-make-target.git","4":"This filetype plugin for Makefiles (\"make\" filetype) provides an autoload function make#target#Make() and buffer-local mapping (MakeTarget) to make! the target for the recipe under the cursor, if it can be identified.\r\n\r\nhttps:\/\/dev.sanctum.geek.nz\/cgit\/vim-make-target.git","install_details":"Put autoload\/make\/target.vim in ~\/.vim\/autoload\/make\/target.vim. The ftplugin itself should probably be saved as ~\/.vim\/after\/ftplugin\/make\/target.vim (per the distribution layout) or ~\/.vim\/after\/ftplugin\/make_target.vim (if you prefer), so that it definitely loads *after* the primary make.vim plugin; or, just use your favourite Vim plugin manager.\r\n\r\nThere is no default key binding; to bind m, you could add this to after\/ftplugin\/make.vim: \r\n\r\n nmap m (MakeTarget)\r\n let b:undo_ftplugin .= '|nunmap _m'","5":"Put autoload\/make\/target.vim in ~\/.vim\/autoload\/make\/target.vim. The ftplugin itself should probably be saved as ~\/.vim\/after\/ftplugin\/make\/target.vim (per the distribution layout) or ~\/.vim\/after\/ftplugin\/make_target.vim (if you prefer), so that it definitely loads *after* the primary make.vim plugin; or, just use your favourite Vim plugin manager.\r\n\r\nThere is no default key binding; to bind m, you could add this to after\/ftplugin\/make.vim: \r\n\r\n nmap m (MakeTarget)\r\n let b:undo_ftplugin .= '|nunmap _m'","first_name":"Tom","6":"Tom","last_name":"Ryder","7":"Ryder","releases":[{"0":"5715","vim_version":"7.0","1":"7.0","script_version":"1.1.0","2":"1.1.0","version_comment":"Correct documentation","3":"Correct documentation","package":"vim-make-target-1.1.0.tar.gz","4":"vim-make-target-1.1.0.tar.gz","src_id":"26289","5":"26289","creation_date":"1543431129","6":"1543431129"}]},"5714":{"script_id":"5714","0":"5714","script_name":"vim-json-format","1":"vim-json-format","script_type":"utility","2":"utility","summary":"format json text ","3":"format json text ","description":"vim-json-format，a vim plugin for formating json text https:\/\/github.com\/forevernull\/vim-json-format","4":"vim-json-format，a vim plugin for formating json text https:\/\/github.com\/forevernull\/vim-json-format","install_details":"unzip vim-json-format.zip then cp vim-json-format\/plugin\/vim-format.vim ~\/.vim\/plugin","5":"unzip vim-json-format.zip then cp vim-json-format\/plugin\/vim-format.vim ~\/.vim\/plugin","first_name":"gawain","6":"gawain","last_name":"liu","7":"liu","releases":[{"0":"5714","vim_version":"7.0","1":"7.0","script_version":"0.0.1","2":"0.0.1","version_comment":"init","3":"init","package":"vim-json-format.zip","4":"vim-json-format.zip","src_id":"26078","5":"26078","creation_date":"1529971850","6":"1529971850"}]},"5713":{"script_id":"5713","0":"5713","script_name":"clear_local_maps.vim","1":"clear_local_maps.vim","script_type":"utility","2":"utility","summary":"Clear buffer-local leader mappings","3":"Clear buffer-local leader mappings","description":"This plugin provides an autoload function that clears all buffer-local mappings that begin with maplocalleader. It's intended for use at the start of an augroup that sets up filetype mappings, to clear away existing ones in the buffer first.\r\n\r\nhttps:\/\/dev.sanctum.geek.nz\/cgit\/vim-clear-local-maps.git\/","4":"This plugin provides an autoload function that clears all buffer-local mappings that begin with maplocalleader. It's intended for use at the start of an augroup that sets up filetype mappings, to clear away existing ones in the buffer first.\r\n\r\nhttps:\/\/dev.sanctum.geek.nz\/cgit\/vim-clear-local-maps.git\/","install_details":"Drop autoload\/clear_local_maps.vim in your ~\/.vim\/autoload directory. Add doc\/clear_local_maps.txt in ~\/.vim\/doc if you want the help file. Otherwise, use your favourite Vim plugin package manager.\r\n\r\nYou might use it in your vimrc like this:\r\n\r\n let g:maplocalleader = '_'\r\n augroup vimrc_filetype_mappings\r\n autocmd!\r\n autocmd FileType * call clear_local_maps#Clear()\r\n \" Filetype-local mappings go here...\r\n augroup END","5":"Drop autoload\/clear_local_maps.vim in your ~\/.vim\/autoload directory. Add doc\/clear_local_maps.txt in ~\/.vim\/doc if you want the help file. Otherwise, use your favourite Vim plugin package manager.\r\n\r\nYou might use it in your vimrc like this:\r\n\r\n let g:maplocalleader = '_'\r\n augroup vimrc_filetype_mappings\r\n autocmd!\r\n autocmd FileType * call clear_local_maps#Clear()\r\n \" Filetype-local mappings go here...\r\n augroup END","first_name":"Tom","6":"Tom","last_name":"Ryder","7":"Ryder","releases":[{"0":"5713","vim_version":"7.0","1":"7.0","script_version":"0.2.0","2":"0.2.0","version_comment":"Clear global aux variable after use","3":"Clear global aux variable after use","package":"vim-clear-local-maps-0.2.0.tar.gz","4":"vim-clear-local-maps-0.2.0.tar.gz","src_id":"26079","5":"26079","creation_date":"1530001497","6":"1530001497"}]},"5712":{"script_id":"5712","0":"5712","script_name":"diff_prune.vim","1":"diff_prune.vim","script_type":"ftplugin","2":"ftplugin","summary":"Reverse changes in selected lines of a diff","3":"Reverse changes in selected lines of a diff","description":"This filetype plugin for diffs\/patches (\"diff\" filetype) provides buffer-local mappings in normal and visual mode to \"undo\" lines of changes defined by a linewise motion or visual mode selection: leading minus signs are removed, and lines with leading plus signs are deleted.\r\n\r\nThis can be handy for using with the -e or --edit option to git-add, which allows you to edit a diff before applying changes to the staging area.\r\n\r\nhttps:\/\/dev.sanctum.geek.nz\/cgit\/vim-diff-prune.git\/","4":"This filetype plugin for diffs\/patches (\"diff\" filetype) provides buffer-local mappings in normal and visual mode to \"undo\" lines of changes defined by a linewise motion or visual mode selection: leading minus signs are removed, and lines with leading plus signs are deleted.\r\n\r\nThis can be handy for using with the -e or --edit option to git-add, which allows you to edit a diff before applying changes to the staging area.\r\n\r\nhttps:\/\/dev.sanctum.geek.nz\/cgit\/vim-diff-prune.git\/","install_details":"This should probably be saved as ~\/.vim\/after\/ftplugin\/diff\/prune.vim (per the distribution layout) or ~\/.vim\/after\/ftplugin\/diff_prune.vim (if you prefer), so that it definitely loads *after* the primary diff.vim plugin--or, just use your favourite Vim plugin manager.\r\n\r\nThere is no default key mapping. You could put this in ~\/.vim\/after\/ftplugin\/diff.vim to use p, with pp to prune the current line:\r\n\r\n nmap p (DiffPrune)\r\n xmap p (DiffPrune)\r\n nmap pp (DiffPrune)_\r\n let b:undo_ftplugin = b:undo_ftplugin\r\n \\ . '|nunmap p'\r\n \\ . '|xunmap p'\r\n \\ . '|nunmap pp'","5":"This should probably be saved as ~\/.vim\/after\/ftplugin\/diff\/prune.vim (per the distribution layout) or ~\/.vim\/after\/ftplugin\/diff_prune.vim (if you prefer), so that it definitely loads *after* the primary diff.vim plugin--or, just use your favourite Vim plugin manager.\r\n\r\nThere is no default key mapping. You could put this in ~\/.vim\/after\/ftplugin\/diff.vim to use p, with pp to prune the current line:\r\n\r\n nmap p (DiffPrune)\r\n xmap p (DiffPrune)\r\n nmap pp (DiffPrune)_\r\n let b:undo_ftplugin = b:undo_ftplugin\r\n \\ . '|nunmap p'\r\n \\ . '|xunmap p'\r\n \\ . '|nunmap pp'","first_name":"Tom","6":"Tom","last_name":"Ryder","7":"Ryder","releases":[{"0":"5712","vim_version":"7.0","1":"7.0","script_version":"1.2.0","2":"1.2.0","version_comment":"Stop breaking select mode","3":"Stop breaking select mode","package":"vim-diff-prune-1.2.0.tar.gz","4":"vim-diff-prune-1.2.0.tar.gz","src_id":"26212","5":"26212","creation_date":"1536221435","6":"1536221435"}]},"5711":{"script_id":"5711","0":"5711","script_name":"paste_open.vim","1":"paste_open.vim","script_type":"utility","2":"utility","summary":"Mapping targets for opening new lines in paste mode","3":"Mapping targets for opening new lines in paste mode","description":"This plugin provides mapping targets for opening new lines in insert mode, above or below the cursor position (same as O and o), but precedes them with a :set paste. It restores that option's previous value once the insert operation finishes. This makes a \"one-shot paste\".\r\n\r\nThe excellent unimpaired.vim, vimscript #1590, provides pretty much the same mapping. However, newer versions of that plugin deprecated the two-key binding I liked, and I wanted something simpler without loading all the other bindings that I never used anyway.\r\n\r\nhttps:\/\/dev.sanctum.geek.nz\/cgit\/vim-paste-open.git","4":"This plugin provides mapping targets for opening new lines in insert mode, above or below the cursor position (same as O and o), but precedes them with a :set paste. It restores that option's previous value once the insert operation finishes. This makes a \"one-shot paste\".\r\n\r\nThe excellent unimpaired.vim, vimscript #1590, provides pretty much the same mapping. However, newer versions of that plugin deprecated the two-key binding I liked, and I wanted something simpler without loading all the other bindings that I never used anyway.\r\n\r\nhttps:\/\/dev.sanctum.geek.nz\/cgit\/vim-paste-open.git","install_details":"Drop plugin\/paste_open.vim in your ~\/.vim\/plugin directory. Add doc\/paste_open.txt in ~\/.vim\/doc if you want the help file. Otherwise, use your favourite Vim plugin package manager.\r\n\r\nThe author uses the mappings like this in his .vimrc:\r\n\r\n nmap \\o (PasteOpenBelow)\r\n nmap \\O (PasteOpenAbove)\r\n\r\nTo get the old unimpaired.vim bindings back, you might do this:\r\n\r\n nmap yo (PasteOpenBelow)\r\n nmap yO (PasteOpenAbove)","5":"Drop plugin\/paste_open.vim in your ~\/.vim\/plugin directory. Add doc\/paste_open.txt in ~\/.vim\/doc if you want the help file. Otherwise, use your favourite Vim plugin package manager.\r\n\r\nThe author uses the mappings like this in his .vimrc:\r\n\r\n nmap \\o (PasteOpenBelow)\r\n nmap \\O (PasteOpenAbove)\r\n\r\nTo get the old unimpaired.vim bindings back, you might do this:\r\n\r\n nmap yo (PasteOpenBelow)\r\n nmap yO (PasteOpenAbove)","first_name":"Tom","6":"Tom","last_name":"Ryder","7":"Ryder","releases":[{"0":"5711","vim_version":"7.0","1":"7.0","script_version":"1.0.1","2":"1.0.1","version_comment":"Parenthesize map names, remove autoload, correct documentation","3":"Parenthesize map names, remove autoload, correct documentation","package":"vim-paste-open-1.0.1.tar.gz","4":"vim-paste-open-1.0.1.tar.gz","src_id":"26211","5":"26211","creation_date":"1536221293","6":"1536221293"}]},"5710":{"script_id":"5710","0":"5710","script_name":"object.vim","1":"object.vim","script_type":"utility","2":"utility","summary":"A pythonic object oriented framework.","3":"A pythonic object oriented framework.","description":"An object oriented framework that utilizes dict function feature of Vim-7. It targets Python3 as API reference so that plugin writers can write code that looks and works like in Python3. Features include C3-based multiple inheritance, class-based exception, iterator and many protocol functions.","4":"An object oriented framework that utilizes dict function feature of Vim-7. It targets Python3 as API reference so that plugin writers can write code that looks and works like in Python3. Features include C3-based multiple inheritance, class-based exception, iterator and many protocol functions.","install_details":"In you $MYVIMRC, with Vundle:\r\nPlugin 'cgsdfc\/object.vim'\r\nWith Plug:\r\nPlug 'cgsdfc\/object.vim'","5":"In you $MYVIMRC, with Vundle:\r\nPlugin 'cgsdfc\/object.vim'\r\nWith Plug:\r\nPlug 'cgsdfc\/object.vim'","first_name":"Cong","6":"Cong","last_name":"Feng","7":"Feng","releases":[{"0":"5710","vim_version":"7.0","1":"7.0","script_version":"0.04","2":"0.04","version_comment":"Initial upload","3":"Initial upload","package":"object.vim-0.0.4.zip","4":"object.vim-0.0.4.zip","src_id":"26064","5":"26064","creation_date":"1529418331","6":"1529418331"}]},"5709":{"script_id":"5709","0":"5709","script_name":"peachpuff256mod","1":"peachpuff256mod","script_type":"color scheme","2":"color scheme","summary":"peachpuff256mod is the terminal version of the vim builtin peachpuff color theme","3":"peachpuff256mod is the terminal version of the vim builtin peachpuff color theme","description":"Origin colors are taken from the VIM builtin peachpuff.vim GUI color theme and can be used either on the 88- or 256-color compatible xterm. The RGB grid is the translation of the Henry So's programmatic approximation colors algorithm (see a desert256 theme). Also, some part of the following script belongs to Martin Baeuml baeuml@gmail.com, the author, and the maintainer of the summerfruit256 vim color theme. The original 'summerfruit256' color scheme along with 'desert256' are available on vim.org","4":"Origin colors are taken from the VIM builtin peachpuff.vim GUI color theme and can be used either on the 88- or 256-color compatible xterm. The RGB grid is the translation of the Henry So's programmatic approximation colors algorithm (see a desert256 theme). Also, some part of the following script belongs to Martin Baeuml baeuml@gmail.com, the author, and the maintainer of the summerfruit256 vim color theme. The original 'summerfruit256' color scheme along with 'desert256' are available on vim.org","install_details":"","5":"","first_name":"Illia","6":"Illia","last_name":"Danko","7":"Danko","releases":[{"0":"5709","vim_version":"7.0","1":"7.0","script_version":"1.0.1","2":"1.0.1","version_comment":"fixed comments","3":"fixed comments","package":"peachpuff256mod.vim","4":"peachpuff256mod.vim","src_id":"26081","5":"26081","creation_date":"1530088680","6":"1530088680"},{"0":"5709","vim_version":"7.0","1":"7.0","script_version":"1.0.0","2":"1.0.0","version_comment":"Initial upload","3":"Initial upload","package":"peachpuff256mod.vim","4":"peachpuff256mod.vim","src_id":"26036","5":"26036","creation_date":"1528507002","6":"1528507002"}]},"5708":{"script_id":"5708","0":"5708","script_name":"vim-colors-nobold","1":"vim-colors-nobold","script_type":"color scheme","2":"color scheme","summary":"Vim color schemes with \"bold\" attribute removed - except for text console.","3":"Vim color schemes with \"bold\" attribute removed - except for text console.","description":"vim-colors-nobold is a collection of Vim color schemes, with \"bold\" attribute removed in GUI and terminal, but not in text console. I wasn't entirely happy with how fonts, which I use in Vim, looked when rendered in bold, so I decided to create modified versions of my favourite Vim color schemes, with \"bold\" attribute removed. At the same time, I didn't want new color schemes to look different in text console, compared to original color schemes. In some cases, I also changed colors of some of the elements - for example, to make active and inactive status lines look different.\r\n\r\nThe collection is split into two parts:\r\n\r\n* base:\r\n * Contains color schemes based on the 18 standard schemes shipped with Vim.\r\n * Requires standard Vim color schemes to be present locally.\r\n* extra:\r\n * Contains additional color schemes, based on schemes created by Vim users.\r\n * Does not require original color schemes to be present locally. This is because \"extra\" color schemes include code from original scripts, with permission from their authors.\r\n\r\nSample screenshots can be found here: https:\/\/gitlab.com\/tomac\/vim-colors-nobold\/wikis\/screenshots\r\n\r\nHome page: https:\/\/gitlab.com\/tomac\/vim-colors-nobold","4":"vim-colors-nobold is a collection of Vim color schemes, with \"bold\" attribute removed in GUI and terminal, but not in text console. I wasn't entirely happy with how fonts, which I use in Vim, looked when rendered in bold, so I decided to create modified versions of my favourite Vim color schemes, with \"bold\" attribute removed. At the same time, I didn't want new color schemes to look different in text console, compared to original color schemes. In some cases, I also changed colors of some of the elements - for example, to make active and inactive status lines look different.\r\n\r\nThe collection is split into two parts:\r\n\r\n* base:\r\n * Contains color schemes based on the 18 standard schemes shipped with Vim.\r\n * Requires standard Vim color schemes to be present locally.\r\n* extra:\r\n * Contains additional color schemes, based on schemes created by Vim users.\r\n * Does not require original color schemes to be present locally. This is because \"extra\" color schemes include code from original scripts, with permission from their authors.\r\n\r\nSample screenshots can be found here: https:\/\/gitlab.com\/tomac\/vim-colors-nobold\/wikis\/screenshots\r\n\r\nHome page: https:\/\/gitlab.com\/tomac\/vim-colors-nobold","install_details":"1. Download vim-colors-nobold scripts. Available sources:\r\n * vim-colors-nobold git repository: git clone https:\/\/gitlab.com\/tomac\/vim-colors-nobold.git\r\n * Archives available on \"releases\" page on GitLab: https:\/\/gitlab.com\/tomac\/vim-colors-nobold\/-\/releases\r\n * Scripts repository on vim.org.\r\n * Direct link: https:\/\/www.vim.org\/scripts\/script.php?script_id=5708.\r\n * Or, search for \"vim-colors-nobold\" here: https:\/\/www.vim.org\/scripts\/index.php\r\n\r\n2. Copy *.vim scripts from base and extra directories (all of them, or just ones you're interested in) to directory below - don't create any subdirectories there. If the directory does not exist, then create it.\r\n * Unix: ~\/.vim\/colors\r\n * Windows: C:\\Users\\your_user_name\\vimfiles\\colors","5":"1. Download vim-colors-nobold scripts. Available sources:\r\n * vim-colors-nobold git repository: git clone https:\/\/gitlab.com\/tomac\/vim-colors-nobold.git\r\n * Archives available on \"releases\" page on GitLab: https:\/\/gitlab.com\/tomac\/vim-colors-nobold\/-\/releases\r\n * Scripts repository on vim.org.\r\n * Direct link: https:\/\/www.vim.org\/scripts\/script.php?script_id=5708.\r\n * Or, search for \"vim-colors-nobold\" here: https:\/\/www.vim.org\/scripts\/index.php\r\n\r\n2. Copy *.vim scripts from base and extra directories (all of them, or just ones you're interested in) to directory below - don't create any subdirectories there. If the directory does not exist, then create it.\r\n * Unix: ~\/.vim\/colors\r\n * Windows: C:\\Users\\your_user_name\\vimfiles\\colors","first_name":"Tomasz","6":"Tomasz","last_name":"Bywalec","7":"Bywalec","releases":[{"0":"5708","vim_version":"8.0","1":"8.0","script_version":"1.1","2":"1.1","version_comment":"1. Added 4 \"extra\" color schemes: fruidle-nobold, ibmedit-nobold, monogreen-nobold and nuvola-nobold.","3":"1. Added 4 \"extra\" color schemes: fruidle-nobold, ibmedit-nobold, monogreen-nobold and nuvola-nobold.","package":"vim-colors-nobold-v1.1.zip","4":"vim-colors-nobold-v1.1.zip","src_id":"26655","5":"26655","creation_date":"1564032258","6":"1564032258"},{"0":"5708","vim_version":"8.0","1":"8.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"vim-colors-nobold-v1.0.zip","4":"vim-colors-nobold-v1.0.zip","src_id":"26035","5":"26035","creation_date":"1528433591","6":"1528433591"}]},"5707":{"script_id":"5707","0":"5707","script_name":"redact_pass.vim","1":"redact_pass.vim","script_type":"utility","2":"utility","summary":"Set options to edit pass(1) files securely","3":"Set options to edit pass(1) files securely","description":"This plugin switches off the 'viminfo', 'backup', 'writebackup', 'swapfile', and 'undofile' options globally when editing a password in pass(1).\r\n\r\nThis is to prevent anyone being able to extract passwords from your Vim cache files in the event of a compromise.\r\n\r\nYou should test this after installation to ensure you see this message printed whenever you `pass edit`:\r\n\r\n Editing password file--disabled leaky options!\r\n\r\nhttps:\/\/sanctum.geek.nz\/cgit\/vim-redact-pass.git","4":"This plugin switches off the 'viminfo', 'backup', 'writebackup', 'swapfile', and 'undofile' options globally when editing a password in pass(1).\r\n\r\nThis is to prevent anyone being able to extract passwords from your Vim cache files in the event of a compromise.\r\n\r\nYou should test this after installation to ensure you see this message printed whenever you `pass edit`:\r\n\r\n Editing password file--disabled leaky options!\r\n\r\nhttps:\/\/sanctum.geek.nz\/cgit\/vim-redact-pass.git","install_details":"Drop plugin\/redact_pass.vim in your ~\/.vim\/plugin directory. Add doc\/redact_pass.txt in ~\/.vim\/doc if you want the help file. Otherwise, use your favourite Vim plugin package manager.","5":"Drop plugin\/redact_pass.vim in your ~\/.vim\/plugin directory. Add doc\/redact_pass.txt in ~\/.vim\/doc if you want the help file. Otherwise, use your favourite Vim plugin package manager.","first_name":"Tom","6":"Tom","last_name":"Ryder","7":"Ryder","releases":[{"0":"5707","vim_version":"6.0","1":"6.0","script_version":"2.0.0","2":"2.0.0","version_comment":"Refactored to use autocmd patterns in place of clunky manual functions","3":"Refactored to use autocmd patterns in place of clunky manual functions","package":"vim-redact-pass-2.0.0.tar.gz","4":"vim-redact-pass-2.0.0.tar.gz","src_id":"26080","5":"26080","creation_date":"1530001766","6":"1530001766"}]},"5706":{"script_id":"5706","0":"5706","script_name":"markdown_autoformat.vim","1":"markdown_autoformat.vim","script_type":"ftplugin","2":"ftplugin","summary":"Automatic formatting heuristics for Markdown","3":"Automatic formatting heuristics for Markdown","description":"This filetype plugin for Markdown documents (\"markdown\" filetype) attempts to apply the 'formatoptions' flag a for auto-format intelligently in three ways:\r\n\r\n Turn it on automatically on load if the buffer looks wrapped\r\n Suspend it if editing a line in a code block (indented by four spaces)\r\n Suspend it if pasting something with a linebreak in it\r\n\r\nIt defaults to doing all three, but that can be disabled with options.\r\n\r\nThe proper way to do this is with a formatexpr for Markdown, but a good one doesn't seem to exist yet. This plugin might eventually take the form of writing one.\r\n\r\nhttps:\/\/sanctum.geek.nz\/cgit\/vim-markdown-autoformat.git","4":"This filetype plugin for Markdown documents (\"markdown\" filetype) attempts to apply the 'formatoptions' flag a for auto-format intelligently in three ways:\r\n\r\n Turn it on automatically on load if the buffer looks wrapped\r\n Suspend it if editing a line in a code block (indented by four spaces)\r\n Suspend it if pasting something with a linebreak in it\r\n\r\nIt defaults to doing all three, but that can be disabled with options.\r\n\r\nThe proper way to do this is with a formatexpr for Markdown, but a good one doesn't seem to exist yet. This plugin might eventually take the form of writing one.\r\n\r\nhttps:\/\/sanctum.geek.nz\/cgit\/vim-markdown-autoformat.git","install_details":"This should probably be saved as ~\/.vim\/after\/ftplugin\/markdown\/autoformat.vim (per the distribution layout) or ~\/.vim\/after\/ftplugin\/markdown_autoformat.vim (if you prefer), so that it definitely loads *after* the primary markdown.vim plugin. Put the autoload script in ~\/.vim\/autoload\/markdown\/autoformat.vim. Or, just use your favourite Vim plugin manager.","5":"This should probably be saved as ~\/.vim\/after\/ftplugin\/markdown\/autoformat.vim (per the distribution layout) or ~\/.vim\/after\/ftplugin\/markdown_autoformat.vim (if you prefer), so that it definitely loads *after* the primary markdown.vim plugin. Put the autoload script in ~\/.vim\/autoload\/markdown\/autoformat.vim. Or, just use your favourite Vim plugin manager.","first_name":"Tom","6":"Tom","last_name":"Ryder","7":"Ryder","releases":[{"0":"5706","vim_version":"7.0","1":"7.0","script_version":"0.5.0","2":"0.5.0","version_comment":"More efficient string matching","3":"More efficient string matching","package":"vim-markdown-autoformat-0.5.0.tar.gz","4":"vim-markdown-autoformat-0.5.0.tar.gz","src_id":"26210","5":"26210","creation_date":"1536221135","6":"1536221135"}]},"5705":{"script_id":"5705","0":"5705","script_name":"put_blank_lines.vim","1":"put_blank_lines.vim","script_type":"utility","2":"utility","summary":"Mapping targets to insert blank lines","3":"Mapping targets to insert blank lines","description":"This plugin provides mapping targets for inserting blank lines above or below the current line without going into insert mode.\r\n\r\nhttps:\/\/sanctum.geek.nz\/cgit\/vim-put-blank-lines.git","4":"This plugin provides mapping targets for inserting blank lines above or below the current line without going into insert mode.\r\n\r\nhttps:\/\/sanctum.geek.nz\/cgit\/vim-put-blank-lines.git","install_details":"Drop plugin\/put_blank_lines.vim in your ~\/.vim\/plugin directory, and autoload\/put_blank_lines.vim in your ~\/.vim\/autoload directory. Add doc\/put_blank_lines.txt in ~\/.vim\/doc if you want the help file. Otherwise, use your favourite Vim plugin package manager.\r\n\r\nTo use the same bindings as unimpaired.vim, you could put this in your .vimrc:\r\n\r\n nmap [ (PutBlankLinesAbove)\r\n nmap ] (PutBlankLinesBelow)\r\n","5":"Drop plugin\/put_blank_lines.vim in your ~\/.vim\/plugin directory, and autoload\/put_blank_lines.vim in your ~\/.vim\/autoload directory. Add doc\/put_blank_lines.txt in ~\/.vim\/doc if you want the help file. Otherwise, use your favourite Vim plugin package manager.\r\n\r\nTo use the same bindings as unimpaired.vim, you could put this in your .vimrc:\r\n\r\n nmap [ (PutBlankLinesAbove)\r\n nmap ] (PutBlankLinesBelow)\r\n","first_name":"Tom","6":"Tom","last_name":"Ryder","7":"Ryder","releases":[{"0":"5705","vim_version":"7.0","1":"7.0","script_version":"3.0.0","2":"3.0.0","version_comment":"Refactor to use mappings and 'operatorfunc' to remove repeat.vim requirement for repetition, but losing 6.0 compatibility in process","3":"Refactor to use mappings and 'operatorfunc' to remove repeat.vim requirement for repetition, but losing 6.0 compatibility in process","package":"vim-put-blank-lines-3.0.0.tar.gz","4":"vim-put-blank-lines-3.0.0.tar.gz","src_id":"26209","5":"26209","creation_date":"1536220965","6":"1536220965"}]},"5704":{"script_id":"5704","0":"5704","script_name":"git-blame.vim","1":"git-blame.vim","script_type":"utility","2":"utility","summary":" See Git Blame information in the status bar for the currently selected line.","3":" See Git Blame information in the status bar for the currently selected line.","description":"See Git Blame information in the status bar for the currently selected line.\r\n\r\nhttps:\/\/wx3.sinaimg.cn\/large\/bceaad1fly1frwfmv58g4j21kw0ingph.jpg\r\n\r\nhttps:\/\/wx3.sinaimg.cn\/large\/bceaad1fly1frwfmv539mj21kw0inq7e.jpg\r\n\r\nhttps:\/\/wx2.sinaimg.cn\/large\/bceaad1fly1frwfmv50ytj21kw0in42a.jpg\r\n","4":"See Git Blame information in the status bar for the currently selected line.\r\n\r\nhttps:\/\/wx3.sinaimg.cn\/large\/bceaad1fly1frwfmv58g4j21kw0ingph.jpg\r\n\r\nhttps:\/\/wx3.sinaimg.cn\/large\/bceaad1fly1frwfmv539mj21kw0inq7e.jpg\r\n\r\nhttps:\/\/wx2.sinaimg.cn\/large\/bceaad1fly1frwfmv50ytj21kw0in42a.jpg\r\n","install_details":"Installation\r\n--------------\r\n\r\nUsing vim-plug: Plug 'zivyangll\/git-blame.vim'\r\n\r\nUsing Vundle: Plugin 'zivyangll\/git-blame.vim'\r\n\r\nDefault bindings\r\n-----------------\r\n\r\nThe default leader has been changed to `s` to avoid\r\nconflicts with other plugins you may have installed.** This can easily be\r\nchanged by rebinding the leader in your vimrc:\r\n\r\nnnoremap s :call gitblame#echo()\r\n\r\nGitHub: https:\/\/github.com\/zivyangll\/git-blame.vim","5":"Installation\r\n--------------\r\n\r\nUsing vim-plug: Plug 'zivyangll\/git-blame.vim'\r\n\r\nUsing Vundle: Plugin 'zivyangll\/git-blame.vim'\r\n\r\nDefault bindings\r\n-----------------\r\n\r\nThe default leader has been changed to `s` to avoid\r\nconflicts with other plugins you may have installed.** This can easily be\r\nchanged by rebinding the leader in your vimrc:\r\n\r\nnnoremap s :call gitblame#echo()\r\n\r\nGitHub: https:\/\/github.com\/zivyangll\/git-blame.vim","first_name":"ziv","6":"ziv","last_name":"yangll","7":"yangll","releases":[{"0":"5704","vim_version":"7.0","1":"7.0","script_version":"1.0.6","2":"1.0.6","version_comment":"feat(neovim): use virtual text","3":"feat(neovim): use virtual text","package":"git-blame.tar.gz","4":"git-blame.tar.gz","src_id":"26585","5":"26585","creation_date":"1562243335","6":"1562243335"},{"0":"5704","vim_version":"7.0","1":"7.0","script_version":"1.0.6","2":"1.0.6","version_comment":"Code reorg - Return dict instead of string","3":"Code reorg - Return dict instead of string","package":"git-blame.tar.gz","4":"git-blame.tar.gz","src_id":"26505","5":"26505","creation_date":"1559216427","6":"1559216427"},{"0":"5704","vim_version":"7.0","1":"7.0","script_version":"1.0.5","2":"1.0.5","version_comment":"support Neovim","3":"support Neovim","package":"git-blame.tar.gz","4":"git-blame.tar.gz","src_id":"26455","5":"26455","creation_date":"1554898443","6":"1554898443"},{"0":"5704","vim_version":"7.0","1":"7.0","script_version":"1.0.4","2":"1.0.4","version_comment":"fix: author time","3":"fix: author time","package":"git-blame.tar.gz","4":"git-blame.tar.gz","src_id":"26336","5":"26336","creation_date":"1547216434","6":"1547216434"},{"0":"5704","vim_version":"7.0","1":"7.0","script_version":"1.0.3","2":"1.0.3","version_comment":"fix: time format","3":"fix: time format","package":"git-blame.tar.gz","4":"git-blame.tar.gz","src_id":"26331","5":"26331","creation_date":"1546951255","6":"1546951255"},{"0":"5704","vim_version":"7.0","1":"7.0","script_version":"1.0.2","2":"1.0.2","version_comment":"fix: blame time info","3":"fix: blame time info","package":"git-blame.tar.gz","4":"git-blame.tar.gz","src_id":"26330","5":"26330","creation_date":"1546904122","6":"1546904122"},{"0":"5704","vim_version":"7.0","1":"7.0","script_version":"1.0.1","2":"1.0.1","version_comment":"feat: remove default bindings.","3":"feat: remove default bindings.","package":"git-blame.tar.gz","4":"git-blame.tar.gz","src_id":"26300","5":"26300","creation_date":"1544808741","6":"1544808741"},{"0":"5704","vim_version":"7.0","1":"7.0","script_version":"1.0.0","2":"1.0.0","version_comment":"Initial upload","3":"Initial upload","package":"git-blame.tar.gz","4":"git-blame.tar.gz","src_id":"26023","5":"26023","creation_date":"1527925090","6":"1527925090"}]},"5703":{"script_id":"5703","0":"5703","script_name":"k.vim","1":"k.vim","script_type":"syntax","2":"syntax","summary":"syntax for the k language.","3":"syntax for the k language.","description":"Based upon the k language as explained at http:\/\/kparc.com\/\r\n","4":"Based upon the k language as explained at http:\/\/kparc.com\/\r\n","install_details":"To install\r\nPut k.vim into .vim\/syntax (vimfiles\/syntax on windows)\r\n","5":"To install\r\nPut k.vim into .vim\/syntax (vimfiles\/syntax on windows)\r\n","first_name":"sm","6":"sm","last_name":"smithfield","7":"smithfield","releases":[{"0":"5703","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"k.vim","4":"k.vim","src_id":"26021","5":"26021","creation_date":"1527865513","6":"1527865513"}]},"5702":{"script_id":"5702","0":"5702","script_name":"j.vim","1":"j.vim","script_type":"syntax","2":"syntax","summary":"j syntax","3":"j syntax","description":"This is easier to demonstrate than to explain.\r\nj.vim will work correctly in all situations, the following demonstration is GUI only. \r\nDo this.\r\nGet voodoochild.vim - a colorscheme, also by this author.\r\nPut voodoochild into .vim\/colors (vimfiles\/colors on windows)\r\nType\r\n :colorscheme voodoochild \r\non the command line.\r\n\r\nNow, you have a linguistic heat map for j.\r\n\r\nHeat Map Key:\r\n
\r\n   red      - delimiter, numeric base, argument within a function.\r\n   orange   - adverb.\r\n   yellow   - verb.\r\n   green    - conjunction.\r\n   dk green - control word.\r\n   sky      - constant.\r\n   indigo   - infinity, alphabet and ace, (all j's nouns)\r\n              self-reference,\r\n              start and end of a define clause, \r\n              the _z_ locative.\r\n<\/pre>\r\nThe color spectrum is a hardwired pattern in the human brain matter.\r\nYellow is the center of attention, being the brightest.\r\nOrange retreats slightly.\r\nRed retreats further but is still warm. \r\nGreen is near yellow, but cool. \r\nSky is cool and stands apart.\r\nIndigo draws attention to exceptional elements.\r\nWarmth implies action.  Cool implies distance. \r\n\r\nInline functions written as strings are colored as code. \r\nRank adverb 'captures' and colors the digits that follow it correctly.\r\nCut variations 'capture' the digits that follow and indicate (the digits as) 'adverb'.\r\nLocatives are colored. \r\nTerm output can also be pasted into vim and colored for improved legibility, \r\nspecifically, boxes and errors.\r\n","4":"This is easier to demonstrate than to explain.\r\nj.vim will work correctly in all situations, the following demonstration is GUI only. \r\nDo this.\r\nGet voodoochild.vim - a colorscheme, also by this author.\r\nPut voodoochild into .vim\/colors (vimfiles\/colors on windows)\r\nType\r\n   :colorscheme voodoochild \r\non the command line.\r\n\r\nNow, you have a linguistic heat map for j.\r\n\r\nHeat Map Key:\r\n
\r\n   red      - delimiter, numeric base, argument within a function.\r\n   orange   - adverb.\r\n   yellow   - verb.\r\n   green    - conjunction.\r\n   dk green - control word.\r\n   sky      - constant.\r\n   indigo   - infinity, alphabet and ace, (all j's nouns)\r\n              self-reference,\r\n              start and end of a define clause, \r\n              the _z_ locative.\r\n<\/pre>\r\nThe color spectrum is a hardwired pattern in the human brain matter.\r\nYellow is the center of attention, being the brightest.\r\nOrange retreats slightly.\r\nRed retreats further but is still warm. \r\nGreen is near yellow, but cool. \r\nSky is cool and stands apart.\r\nIndigo draws attention to exceptional elements.\r\nWarmth implies action.  Cool implies distance. \r\n\r\nInline functions written as strings are colored as code. \r\nRank adverb 'captures' and colors the digits that follow it correctly.\r\nCut variations 'capture' the digits that follow and indicate (the digits as) 'adverb'.\r\nLocatives are colored. \r\nTerm output can also be pasted into vim and colored for improved legibility, \r\nspecifically, boxes and errors.\r\n","install_details":"To install\r\nPut j.vim into .vim\/syntax (vimfiles\/syntax on windows)\r\n","5":"To install\r\nPut j.vim into .vim\/syntax (vimfiles\/syntax on windows)\r\n","first_name":"sm","6":"sm","last_name":"smithfield","7":"smithfield","releases":[{"0":"5702","vim_version":"7.0","1":"7.0","script_version":"0.2","2":"0.2","version_comment":"more..","3":"more..","package":"j.vim","4":"j.vim","src_id":"27113","5":"27113","creation_date":"1586613728","6":"1586613728"},{"0":"5702","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"j.vim","4":"j.vim","src_id":"26020","5":"26020","creation_date":"1527865281","6":"1527865281"}]},"5701":{"script_id":"5701","0":"5701","script_name":"smullyan.vim","1":"smullyan.vim","script_type":"color scheme","2":"color scheme","summary":"Light colorscheme for brightly lit conditions.","3":"Light colorscheme for brightly lit conditions.","description":":Smullyan            - change certain setting dynamically.\r\n:Smullyan (no args)  - displays current settings \r\n:Smullyan bold?      - diplays current value of bold. works similarly for all options.\r\n:Smullyan bold!      - toggles bold value for 'categorical' colors\r\n:Smullyan underline! - toggles the appearance of Underlined. \r\n                         smullyan.vim uses Underlined as an additional color\r\n                         without the underline as default.\r\n                         If you want the Underline back, turn it back on.\r\n:Smullyan ignore!    - toggles the appearance of Ignore'd text from nearly\r\n                        invisible to invisible, ie. same color as background.\r\n:Smullyan conceal!   - toggles the appearance of Conceal'd text \r\n                         from Comment to Ignore.\r\n\r\nThis means ... you can dynamically make Conceal'd text invisible, nearly\r\ninvisible or appear as a Comment in both gui and xterm-256 environments.\r\n\r\nThis colorscheme is designed to be a replacement for black on white in gui\r\nenvironments.  smullyan.vim is a very high contrast colorscheme that is\r\nmost appropriate for brightly lit conditions.\r\n\r\nGui color support is complete and includes the latest highlight commands from 801. \r\n\r\nIn your vimrc file put (for example),\r\n    Smullyan bold 0\r\n    Smullyan underline 1\r\nto establish your own preferences.\r\n\r\nThe 'categorical' colors are the colors which are used by syntax files to match\r\nlinguistic elements.  'Categorical' colors are treated as an ad hoc linguistic\r\nheat map. In order of 'heat' they are..\r\n\r\n    PreProc - includes Delimiter as a remap\r\n    Statement\r\n    Type\r\n    Special\r\n    Identifier\r\n    Constant\r\n    Underlined\r\n\r\nThe emphasis - yellow - is placed upon 'Type'.\r\nThe rest of the colors are 'interface' colors.\r\n","4":":Smullyan            - change certain setting dynamically.\r\n:Smullyan (no args)  - displays current settings \r\n:Smullyan bold?      - diplays current value of bold. works similarly for all options.\r\n:Smullyan bold!      - toggles bold value for 'categorical' colors\r\n:Smullyan underline! - toggles the appearance of Underlined. \r\n                         smullyan.vim uses Underlined as an additional color\r\n                         without the underline as default.\r\n                         If you want the Underline back, turn it back on.\r\n:Smullyan ignore!    - toggles the appearance of Ignore'd text from nearly\r\n                        invisible to invisible, ie. same color as background.\r\n:Smullyan conceal!   - toggles the appearance of Conceal'd text \r\n                         from Comment to Ignore.\r\n\r\nThis means ... you can dynamically make Conceal'd text invisible, nearly\r\ninvisible or appear as a Comment in both gui and xterm-256 environments.\r\n\r\nThis colorscheme is designed to be a replacement for black on white in gui\r\nenvironments.  smullyan.vim is a very high contrast colorscheme that is\r\nmost appropriate for brightly lit conditions.\r\n\r\nGui color support is complete and includes the latest highlight commands from 801. \r\n\r\nIn your vimrc file put (for example),\r\n    Smullyan bold 0\r\n    Smullyan underline 1\r\nto establish your own preferences.\r\n\r\nThe 'categorical' colors are the colors which are used by syntax files to match\r\nlinguistic elements.  'Categorical' colors are treated as an ad hoc linguistic\r\nheat map. In order of 'heat' they are..\r\n\r\n    PreProc - includes Delimiter as a remap\r\n    Statement\r\n    Type\r\n    Special\r\n    Identifier\r\n    Constant\r\n    Underlined\r\n\r\nThe emphasis - yellow - is placed upon 'Type'.\r\nThe rest of the colors are 'interface' colors.\r\n","install_details":"Install:\r\n    place smullyan.vim in \r\n    ~\/.vim\/colors\/ \r\n    (~\/vimfiles\/colors on PC)","5":"Install:\r\n    place smullyan.vim in \r\n    ~\/.vim\/colors\/ \r\n    (~\/vimfiles\/colors on PC)","first_name":"sm","6":"sm","last_name":"smithfield","7":"smithfield","releases":[{"0":"5701","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"smullyan.vim","4":"smullyan.vim","src_id":"26019","5":"26019","creation_date":"1527864878","6":"1527864878"}]},"5700":{"script_id":"5700","0":"5700","script_name":"voodooChild.vim","1":"voodooChild.vim","script_type":"color scheme","2":"color scheme","summary":"Low contrast colorscheme for low light conditions.","3":"Low contrast colorscheme for low light conditions.","description":":VoodooChild            - change certain setting dynamically.\r\n:VoodooChild (no args)  - displays current settings \r\n:VoodooChild bold?      - diplays current value of bold. works similarly for all options.\r\n:VoodooChild bold!      - toggles bold value for 'categorical' colors\r\n:VoodooChild underline! - toggles the appearance of Underlined. \r\n                          voodooChild.vim uses Underlined as an additional color\r\n                          without the underline as default.\r\n                          If you want the Underline back, turn it back on.\r\n:VoodooChild ignore!    - toggles the appearance of Ignore'd text \r\n                          from nearly invisible to invisible, ie. same color as background.\r\n:VoodooChild conceal!   - toggles the appearance of Conceal'd text \r\n                          from Comment to Ignore.\r\n\r\nThis means ... you can dynamically make Conceal'd text invisible, nearly\r\ninvisible or appear as a Comment in both gui and xterm-256 environments.\r\n\r\nThis colorscheme is designed to reduce eyestrain by using a much lower contrast\r\nthan black on white. voodooChild is a very low contrast colorscheme that is most\r\nappropriate for low light conditions.\r\n\r\nIncludes several palettes of color, support for RainbowLevels and Vimwiki\r\nheaders. This is a toolkit for anyone who wants to play around with such\r\nthings.\r\n\r\nGui color support is complete. Includes the latest highlight commands from 801. \r\n\r\nIn your vimrc file put (for example),\r\n    VoodooChild bold 0\r\n    VoodooChild underline 1\r\nto establish your own preferences.\r\n\r\nThe 'categorical' colors are the colors which are used by syntax files to match\r\nlinguistic elements.  'Categorical' colors are treated as an ad hoc linguistic\r\nheat map. In order of 'heat' they are..\r\n\r\n    PreProc - includes Delimiter as a remap\r\n    Statement\r\n    Type\r\n    Special\r\n    Identifier\r\n    Constant\r\n    Underlined\r\n\r\nThe emphasis - yellow - is placed upon 'Type'.\r\nThe rest of the colors are 'interface' colors.\r\n","4":":VoodooChild            - change certain setting dynamically.\r\n:VoodooChild (no args)  - displays current settings \r\n:VoodooChild bold?      - diplays current value of bold. works similarly for all options.\r\n:VoodooChild bold!      - toggles bold value for 'categorical' colors\r\n:VoodooChild underline! - toggles the appearance of Underlined. \r\n                          voodooChild.vim uses Underlined as an additional color\r\n                          without the underline as default.\r\n                          If you want the Underline back, turn it back on.\r\n:VoodooChild ignore!    - toggles the appearance of Ignore'd text \r\n                          from nearly invisible to invisible, ie. same color as background.\r\n:VoodooChild conceal!   - toggles the appearance of Conceal'd text \r\n                          from Comment to Ignore.\r\n\r\nThis means ... you can dynamically make Conceal'd text invisible, nearly\r\ninvisible or appear as a Comment in both gui and xterm-256 environments.\r\n\r\nThis colorscheme is designed to reduce eyestrain by using a much lower contrast\r\nthan black on white. voodooChild is a very low contrast colorscheme that is most\r\nappropriate for low light conditions.\r\n\r\nIncludes several palettes of color, support for RainbowLevels and Vimwiki\r\nheaders. This is a toolkit for anyone who wants to play around with such\r\nthings.\r\n\r\nGui color support is complete. Includes the latest highlight commands from 801. \r\n\r\nIn your vimrc file put (for example),\r\n    VoodooChild bold 0\r\n    VoodooChild underline 1\r\nto establish your own preferences.\r\n\r\nThe 'categorical' colors are the colors which are used by syntax files to match\r\nlinguistic elements.  'Categorical' colors are treated as an ad hoc linguistic\r\nheat map. In order of 'heat' they are..\r\n\r\n    PreProc - includes Delimiter as a remap\r\n    Statement\r\n    Type\r\n    Special\r\n    Identifier\r\n    Constant\r\n    Underlined\r\n\r\nThe emphasis - yellow - is placed upon 'Type'.\r\nThe rest of the colors are 'interface' colors.\r\n","install_details":"Install:\r\n    place voodooChild.vim in \r\n    ~\/.vim\/colors\/ \r\n    (~\/vimfiles\/colors on PC)\r\n","5":"Install:\r\n    place voodooChild.vim in \r\n    ~\/.vim\/colors\/ \r\n    (~\/vimfiles\/colors on PC)\r\n","first_name":"sm","6":"sm","last_name":"smithfield","7":"smithfield","releases":[{"0":"5700","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"voodooChild.vim","4":"voodooChild.vim","src_id":"26018","5":"26018","creation_date":"1527864792","6":"1527864792"}]},"5699":{"script_id":"5699","0":"5699","script_name":"vim-indexer","1":"vim-indexer","script_type":"utility","2":"utility","summary":"Vim plugin that provides async tags generation with project management.","3":"Vim plugin that provides async tags generation with project management.","description":"# Indexer\r\n\r\nVim Indexer plugin that provides async tags generation with project management.\r\n\r\nUsage: `:Indexer [module] [action] [params ...]`\r\n\r\nInstall this plugin and everything will be DONE!\r\n\r\nUse CTRL-]<\/kbd> to jump anywhere.\r\n\r\n## Options\r\n\r\n    \" Project root folders, used to identify ancestor path of project root directory.\r\n    let g:indexer_root_folders = [$HOME]\r\n\r\n    \" Project root markers, used to identify project root directory.\r\n    let g:indexer_root_markers = ['.git']\r\n\r\n    \" JSON formatted configuration file which located in the project root directory,\r\n    \" makes you could specify different options for each project.\r\n    let g:indexer_root_setting = 'indexer.json'\r\n\r\n    \" Enabled user modules.\r\n    let g:indexer_user_modules = ['log', 'tag']\r\n\r\n## Modules\r\n\r\n### log\r\nModule that provides logging, usually used for debugging modules themselves.\r\n\r\nUsage: `:Indexer log`\r\n\r\n### tag\r\nModule that provides painless transparent tags generation (Vim8 with +job feature required).\r\n\r\nUsage: `:Indexer tag [locate|reload|status|update]`\r\n\r\n## Options (module)\r\n\r\n    \" Module: log\r\n    \"\r\n    let g:indexer_logs_maxsize = 100\r\n\r\n    \" Module: tag\r\n    \"\r\n    \" This module can also read the configuration of the current project.\r\n    \" For example you can have a JSON formatted file in the project directory:\r\n    \"\r\n    \" > indexer.json:\r\n    \" {\r\n    \"    \"tags_watches\": [\"*.php\"],\r\n    \"    \"tags_command\": \"ctags\",\r\n    \"    \"tags_options\": \"-R --sort=yes --languages=php\",\r\n    \"    \"tags_savedir\": \"~\/.vim_indexer_tags\/\",\r\n    \"    \"tags_handler_locate\": [\"locate\"],\r\n    \"    \"tags_handler_reload\": [\"reload\", \"-1\"],\r\n    \"    \"tags_handler_update\": [\"update\"],\r\n    \" }\r\n    \"\r\n    \" And\/Or settings in global:\r\n    \"\r\n    let g:indexer_tags_watches = [\"*.c\", \"*.h\", \"*.c++\", \"*.cpp\", \"*.php\", \"*.py\"]\r\n    let g:indexer_tags_command = \"ctags\"\r\n    let g:indexer_tags_options = \"-R --sort=yes --c++-kinds=+p+l --fields=+iaS --extra=+q --languages=c,c++,php,python\"\r\n    let g:indexer_tags_savedir = \"~\/.vim_indexer_tags\/\"\r\n    let g:indexer_tags_handler_locate = [\"locate\"]\r\n    let g:indexer_tags_handler_reload = [\"reload\", \"-1\"]\r\n    let g:indexer_tags_handler_update = [\"update\"]\r\n\r\n\r\n","4":"# Indexer\r\n\r\nVim Indexer plugin that provides async tags generation with project management.\r\n\r\nUsage: `:Indexer [module] [action] [params ...]`\r\n\r\nInstall this plugin and everything will be DONE!\r\n\r\nUse CTRL-]<\/kbd> to jump anywhere.\r\n\r\n## Options\r\n\r\n    \" Project root folders, used to identify ancestor path of project root directory.\r\n    let g:indexer_root_folders = [$HOME]\r\n\r\n    \" Project root markers, used to identify project root directory.\r\n    let g:indexer_root_markers = ['.git']\r\n\r\n    \" JSON formatted configuration file which located in the project root directory,\r\n    \" makes you could specify different options for each project.\r\n    let g:indexer_root_setting = 'indexer.json'\r\n\r\n    \" Enabled user modules.\r\n    let g:indexer_user_modules = ['log', 'tag']\r\n\r\n## Modules\r\n\r\n### log\r\nModule that provides logging, usually used for debugging modules themselves.\r\n\r\nUsage: `:Indexer log`\r\n\r\n### tag\r\nModule that provides painless transparent tags generation (Vim8 with +job feature required).\r\n\r\nUsage: `:Indexer tag [locate|reload|status|update]`\r\n\r\n## Options (module)\r\n\r\n    \" Module: log\r\n    \"\r\n    let g:indexer_logs_maxsize = 100\r\n\r\n    \" Module: tag\r\n    \"\r\n    \" This module can also read the configuration of the current project.\r\n    \" For example you can have a JSON formatted file in the project directory:\r\n    \"\r\n    \" > indexer.json:\r\n    \" {\r\n    \"    \"tags_watches\": [\"*.php\"],\r\n    \"    \"tags_command\": \"ctags\",\r\n    \"    \"tags_options\": \"-R --sort=yes --languages=php\",\r\n    \"    \"tags_savedir\": \"~\/.vim_indexer_tags\/\",\r\n    \"    \"tags_handler_locate\": [\"locate\"],\r\n    \"    \"tags_handler_reload\": [\"reload\", \"-1\"],\r\n    \"    \"tags_handler_update\": [\"update\"],\r\n    \" }\r\n    \"\r\n    \" And\/Or settings in global:\r\n    \"\r\n    let g:indexer_tags_watches = [\"*.c\", \"*.h\", \"*.c++\", \"*.cpp\", \"*.php\", \"*.py\"]\r\n    let g:indexer_tags_command = \"ctags\"\r\n    let g:indexer_tags_options = \"-R --sort=yes --c++-kinds=+p+l --fields=+iaS --extra=+q --languages=c,c++,php,python\"\r\n    let g:indexer_tags_savedir = \"~\/.vim_indexer_tags\/\"\r\n    let g:indexer_tags_handler_locate = [\"locate\"]\r\n    let g:indexer_tags_handler_reload = [\"reload\", \"-1\"]\r\n    let g:indexer_tags_handler_update = [\"update\"]\r\n\r\n\r\n","install_details":"Just put the files into ~\/.vim\/ or \\vimfiles\\ (for Windows).\r\n\r\nUse plugin installer:\r\n\r\n  Plugin 'alvan\/vim-indexer'\r\n","5":"Just put the files into ~\/.vim\/ or \\vimfiles\\ (for Windows).\r\n\r\nUse plugin installer:\r\n\r\n  Plugin 'alvan\/vim-indexer'\r\n","first_name":"A","6":"A","last_name":"L","7":"L","releases":[{"0":"5699","vim_version":"8.0","1":"8.0","script_version":"0.9.3","2":"0.9.3","version_comment":"update version","3":"update version","package":"vim-indexer-master.zip","4":"vim-indexer-master.zip","src_id":"26449","5":"26449","creation_date":"1554473083","6":"1554473083"}]},"5698":{"script_id":"5698","0":"5698","script_name":"auto_cache_dirs.vim","1":"auto_cache_dirs.vim","script_type":"utility","2":"utility","summary":"Create and set cache file directories easily","3":"Create and set cache file directories easily","description":"This plugin attempts to intelligently set and create the directories for the 'backupdir', 'directory', and 'undodir' options in a sensible root location. It chooses the root directory by trying each of these in succession:\r\n\r\n* If g:auto_cache_dirs_root is set when the plugin loads, it uses that.\r\n* If the environment variable $XDG_CONFIG_HOME is set, it uses that, with \"\/vim\" appended.\r\n* If the system is Unix, it uses ~\/.cache\/vim.\r\n* Otherwise, it uses the first element of the value of 'runtimepath'.\r\n\r\nThe plugin tries hard to create the directories, trying Vim's native mkdir() function if available first, and falling back to shell commands otherwise. At the time of writing, the latter only works for Unix and Windows. If you use another system and would like to see a routine for it added, please send a patch through.\r\n\r\nIf the directory can be created, it sets the relevant option feature flag and prepends the path to that option path list.\r\n\r\nIf the directory cannot be created, a warning is printed, and the options as the plugin found them are left untouched.\r\n\r\nhttps:\/\/sanctum.geek.nz\/cgit\/vim-auto-cache-dirs.git","4":"This plugin attempts to intelligently set and create the directories for the 'backupdir', 'directory', and 'undodir' options in a sensible root location. It chooses the root directory by trying each of these in succession:\r\n\r\n* If g:auto_cache_dirs_root is set when the plugin loads, it uses that.\r\n* If the environment variable $XDG_CONFIG_HOME is set, it uses that, with \"\/vim\" appended.\r\n* If the system is Unix, it uses ~\/.cache\/vim.\r\n* Otherwise, it uses the first element of the value of 'runtimepath'.\r\n\r\nThe plugin tries hard to create the directories, trying Vim's native mkdir() function if available first, and falling back to shell commands otherwise. At the time of writing, the latter only works for Unix and Windows. If you use another system and would like to see a routine for it added, please send a patch through.\r\n\r\nIf the directory can be created, it sets the relevant option feature flag and prepends the path to that option path list.\r\n\r\nIf the directory cannot be created, a warning is printed, and the options as the plugin found them are left untouched.\r\n\r\nhttps:\/\/sanctum.geek.nz\/cgit\/vim-auto-cache-dirs.git","install_details":"Drop plugin\/auto_cache_dirs.vim in your ~\/.vim\/plugin directory. Add doc\/auto_cache_dirs.txt in ~\/.vim\/doc if you want the help file. Otherwise, use your favourite Vim plugin package manager.","5":"Drop plugin\/auto_cache_dirs.vim in your ~\/.vim\/plugin directory. Add doc\/auto_cache_dirs.txt in ~\/.vim\/doc if you want the help file. Otherwise, use your favourite Vim plugin package manager.","first_name":"Tom","6":"Tom","last_name":"Ryder","7":"Ryder","releases":[{"0":"5698","vim_version":"6.0","1":"6.0","script_version":"0.4.4","2":"0.4.4","version_comment":"Delete stray file again","3":"Delete stray file again","package":"vim-auto-cache-dirs-0.4.4.tar.gz","4":"vim-auto-cache-dirs-0.4.4.tar.gz","src_id":"26207","5":"26207","creation_date":"1536220714","6":"1536220714"}]},"5697":{"script_id":"5697","0":"5697","script_name":"uncap_ex.vim","1":"uncap_ex.vim","script_type":"utility","2":"utility","summary":"Correct accidentally capitalised ex commands","3":"Correct accidentally capitalised ex commands","description":"This plugin defines custom commands like :W, :Qa, and :Wq to match their lowercase analogues, to forgive me when my pinky finger doesn't roll off the Shift key quite soon enough after pressing the colon key.\r\n\r\nhttps:\/\/sanctum.geek.nz\/cgit\/vim-uncap-ex.git","4":"This plugin defines custom commands like :W, :Qa, and :Wq to match their lowercase analogues, to forgive me when my pinky finger doesn't roll off the Shift key quite soon enough after pressing the colon key.\r\n\r\nhttps:\/\/sanctum.geek.nz\/cgit\/vim-uncap-ex.git","install_details":"Drop plugin\/uncap_ex.vim in your ~\/.vim\/plugin directory. Add doc\/uncap_ex.txt in ~\/.vim\/doc if you want the help file. Otherwise, use your favourite Vim plugin package manager.\r\n","5":"Drop plugin\/uncap_ex.vim in your ~\/.vim\/plugin directory. Add doc\/uncap_ex.txt in ~\/.vim\/doc if you want the help file. Otherwise, use your favourite Vim plugin package manager.\r\n","first_name":"Tom","6":"Tom","last_name":"Ryder","7":"Ryder","releases":[{"0":"5697","vim_version":"6.0","1":"6.0","script_version":"0.2.0","2":"0.2.0","version_comment":"Verified working on 6.0","3":"Verified working on 6.0","package":"vim-uncap-ex-0.2.0.tar.gz","4":"vim-uncap-ex-0.2.0.tar.gz","src_id":"26053","5":"26053","creation_date":"1529266004","6":"1529266004"}]},"5696":{"script_id":"5696","0":"5696","script_name":"big_file_options.vim","1":"big_file_options.vim","script_type":"utility","2":"utility","summary":"Automatically set options to speed up working with big files","3":"Automatically set options to speed up working with big files","description":"This plugin adds an autocmd hook to check the file size of an incoming buffer, and if it's over a certain threshold, disables certain options in order to make the file a bit easier to edit. It makes the buffer read-only, and disables filetypes, swap files, undo files, and syntax highlighting.\r\n\r\nIt's similar to the much older and more sophisticated LargeFile plugin by Charles Campbell, which is based on vimtip #611.\r\n\r\nIf you want more options and bells and whistles, you should definitely use that instead. I'm intentionally keeping this very small and simple; it should be install-and-forget.\r\n\r\nhttps:\/\/sanctum.geek.nz\/cgit\/vim-big-file-options.git","4":"This plugin adds an autocmd hook to check the file size of an incoming buffer, and if it's over a certain threshold, disables certain options in order to make the file a bit easier to edit. It makes the buffer read-only, and disables filetypes, swap files, undo files, and syntax highlighting.\r\n\r\nIt's similar to the much older and more sophisticated LargeFile plugin by Charles Campbell, which is based on vimtip #611.\r\n\r\nIf you want more options and bells and whistles, you should definitely use that instead. I'm intentionally keeping this very small and simple; it should be install-and-forget.\r\n\r\nhttps:\/\/sanctum.geek.nz\/cgit\/vim-big-file-options.git","install_details":"Drop plugin\/big_file_options.vim in your ~\/.vim\/plugin directory. Add doc\/big_file_options.txt in ~\/.vim\/doc if you want the help file. Otherwise, use your favourite Vim plugin package manager.","5":"Drop plugin\/big_file_options.vim in your ~\/.vim\/plugin directory. Add doc\/big_file_options.txt in ~\/.vim\/doc if you want the help file. Otherwise, use your favourite Vim plugin package manager.","first_name":"Tom","6":"Tom","last_name":"Ryder","7":"Ryder","releases":[{"0":"5696","vim_version":"6.0","1":"6.0","script_version":"1.0.0","2":"1.0.0","version_comment":"Overhaul; remove broken backup disabling, fix option names, add new readonly option, refine detection algorithm, and more.","3":"Overhaul; remove broken backup disabling, fix option names, add new readonly option, refine detection algorithm, and more.","package":"vim-big-file-options-1.0.0.tar.gz","4":"vim-big-file-options-1.0.0.tar.gz","src_id":"26114","5":"26114","creation_date":"1530976051","6":"1530976051"}]},"5695":{"script_id":"5695","0":"5695","script_name":"strip_trailing_whitespace.vim","1":"strip_trailing_whitespace.vim","script_type":"utility","2":"utility","summary":"Strip trailing whitespace exactly the way this author wants","3":"Strip trailing whitespace exactly the way this author wants","description":"This plugin provides a user command with the author's approach to stripping trailing whitespace from an entire buffer, including removing empty or whitespace-only lines at the end of the buffer, without making command noise and without moving the cursor from its current position.\r\n\r\nThis is a very commonly written and implemented plugin, but I wrote my own because I could not find a plugin that did this in exactly the way I wanted:\r\n\r\n- Accept an optional range\r\n- Strip trailing lines as well as trailing spaces\r\n- Report what was changed, accurately\r\n- Work with even very old Vim (>=6.0)\r\n- Work with a single undo\r\n- Don't move the cursor\r\n- Don't change the search pattern\r\n- Don't define an autocmd\r\n- Don't force a key mapping\r\n- Don't define a global function\r\n\r\nhttps:\/\/sanctum.geek.nz\/cgit\/vim-strip-trailing-whitespace.git","4":"This plugin provides a user command with the author's approach to stripping trailing whitespace from an entire buffer, including removing empty or whitespace-only lines at the end of the buffer, without making command noise and without moving the cursor from its current position.\r\n\r\nThis is a very commonly written and implemented plugin, but I wrote my own because I could not find a plugin that did this in exactly the way I wanted:\r\n\r\n- Accept an optional range\r\n- Strip trailing lines as well as trailing spaces\r\n- Report what was changed, accurately\r\n- Work with even very old Vim (>=6.0)\r\n- Work with a single undo\r\n- Don't move the cursor\r\n- Don't change the search pattern\r\n- Don't define an autocmd\r\n- Don't force a key mapping\r\n- Don't define a global function\r\n\r\nhttps:\/\/sanctum.geek.nz\/cgit\/vim-strip-trailing-whitespace.git","install_details":"Drop plugin\/strip_trailing_whitespace.vim in your ~\/.vim\/plugin directory. Add doc\/strip_trailing_whitespace.txt in ~\/.vim\/doc if you want the help file. Otherwise, use your favourite Vim plugin package manager.","5":"Drop plugin\/strip_trailing_whitespace.vim in your ~\/.vim\/plugin directory. Add doc\/strip_trailing_whitespace.txt in ~\/.vim\/doc if you want the help file. Otherwise, use your favourite Vim plugin package manager.","first_name":"Tom","6":"Tom","last_name":"Ryder","7":"Ryder","releases":[{"0":"5695","vim_version":"6.0","1":"6.0","script_version":"2.0.2","2":"2.0.2","version_comment":"Complete rewrite, accept range, define user command rather than plugin map","3":"Complete rewrite, accept range, define user command rather than plugin map","package":"vim-strip-trailing-whitespace-2.0.2.tar.gz","4":"vim-strip-trailing-whitespace-2.0.2.tar.gz","src_id":"26141","5":"26141","creation_date":"1532118334","6":"1532118334"}]},"5694":{"script_id":"5694","0":"5694","script_name":"sahara.vim","1":"sahara.vim","script_type":"color scheme","2":"color scheme","summary":"Tweaked desert256 colorscheme","3":"Tweaked desert256 colorscheme","description":"Tweaked version of the desert256 colorscheme for Vim, without the clunky color detection code. More subdued status bars, tab bars, and line numbers.\r\n\r\nhttps:\/\/sanctum.geek.nz\/cgit\/vim-sahara.git","4":"Tweaked version of the desert256 colorscheme for Vim, without the clunky color detection code. More subdued status bars, tab bars, and line numbers.\r\n\r\nhttps:\/\/sanctum.geek.nz\/cgit\/vim-sahara.git","install_details":" Drop colors\/sahara.vim in your ~\/.vim\/colors directory, or use your favourite Vim package manager.","5":" Drop colors\/sahara.vim in your ~\/.vim\/colors directory, or use your favourite Vim package manager.","first_name":"Tom","6":"Tom","last_name":"Ryder","7":"Ryder","releases":[{"0":"5694","vim_version":"6.0","1":"6.0","script_version":"0.4.0","2":"0.4.0","version_comment":"Fix colors for cursorline and cursorcolumn","3":"Fix colors for cursorline and cursorcolumn","package":"vim-sahara-0.4.0.tar.gz","4":"vim-sahara-0.4.0.tar.gz","src_id":"26208","5":"26208","creation_date":"1536220815","6":"1536220815"}]},"5693":{"script_id":"5693","0":"5693","script_name":"copy_linebreak.vim","1":"copy_linebreak.vim","script_type":"utility","2":"utility","summary":"Switch between readable and terminal-copy-friendly wrapping options","3":"Switch between readable and terminal-copy-friendly wrapping options","description":"This plugin provides mapping targets for a user to set, unset, or toggle 'linebreak'-related settings when 'wrap' is enabled, to switch between human-readable output and a format friendly for copy-pasting with terminal emulators or screen\/tmux.\r\n\r\nhttps:\/\/sanctum.geek.nz\/cgit\/vim-copy-linebreak.git","4":"This plugin provides mapping targets for a user to set, unset, or toggle 'linebreak'-related settings when 'wrap' is enabled, to switch between human-readable output and a format friendly for copy-pasting with terminal emulators or screen\/tmux.\r\n\r\nhttps:\/\/sanctum.geek.nz\/cgit\/vim-copy-linebreak.git","install_details":"Drop plugin\/copy_linebreak.vim in your ~\/.vim\/plugin directory. Add doc\/copy_linebreak.txt in ~\/.vim\/doc if you want the help file. Otherwise, use your favourite Vim plugin package manager.\r\n","5":"Drop plugin\/copy_linebreak.vim in your ~\/.vim\/plugin directory. Add doc\/copy_linebreak.txt in ~\/.vim\/doc if you want the help file. Otherwise, use your favourite Vim plugin package manager.\r\n","first_name":"Tom","6":"Tom","last_name":"Ryder","7":"Ryder","releases":[{"0":"5693","vim_version":"6.0","1":"6.0","script_version":"0.6.0","2":"0.6.0","version_comment":"Parenthesize plugin maps","3":"Parenthesize plugin maps","package":"vim-copy-linebreak-0.6.0.tar.gz","4":"vim-copy-linebreak-0.6.0.tar.gz","src_id":"26206","5":"26206","creation_date":"1536220641","6":"1536220641"}]},"5692":{"script_id":"5692","0":"5692","script_name":"toggle_flags.vim","1":"toggle_flags.vim","script_type":"utility","2":"utility","summary":"Toggle flags in option values","3":"Toggle flags in option values","description":"This plugin provides :ToggleFlag and :ToggleFlagLocal commands to toggle flags in the values of options like 'formatoptions' or 'complete' that have values comprised of single-character or comma-separated flags. The author originally designed it for toggling flags in 'formatoptions' quickly.\r\n\r\nhttps:\/\/sanctum.geek.nz\/cgit\/vim-toggle-flags.git","4":"This plugin provides :ToggleFlag and :ToggleFlagLocal commands to toggle flags in the values of options like 'formatoptions' or 'complete' that have values comprised of single-character or comma-separated flags. The author originally designed it for toggling flags in 'formatoptions' quickly.\r\n\r\nhttps:\/\/sanctum.geek.nz\/cgit\/vim-toggle-flags.git","install_details":"Drop plugin\/toggle_flags.vim in your ~\/.vim\/plugin directory. Add doc\/toggle_flags.txt in ~\/.vim\/doc if you want the help file. Otherwise, use your favourite Vim plugin package manager.","5":"Drop plugin\/toggle_flags.vim in your ~\/.vim\/plugin directory. Add doc\/toggle_flags.txt in ~\/.vim\/doc if you want the help file. Otherwise, use your favourite Vim plugin package manager.","first_name":"Tom","6":"Tom","last_name":"Ryder","7":"Ryder","releases":[{"0":"5692","vim_version":"6.0","1":"6.0","script_version":"1.0.2","2":"1.0.2","version_comment":"Rename, refactor a little","3":"Rename, refactor a little","package":"vim-toggle-flags-1.0.2.tar.gz","4":"vim-toggle-flags-1.0.2.tar.gz","src_id":"26140","5":"26140","creation_date":"1532109073","6":"1532109073"}]},"5691":{"script_id":"5691","0":"5691","script_name":"fixed_join.vim","1":"fixed_join.vim","script_type":"utility","2":"utility","summary":"Join lines without jumping around","3":"Join lines without jumping around","description":"This plugin provides a mapping target and an optional command to :join lines in normal mode while keeping the cursor in-place, and still supporting a count prefix.\r\n\r\nhttps:\/\/sanctum.geek.nz\/cgit\/vim-fixed-join.git","4":"This plugin provides a mapping target and an optional command to :join lines in normal mode while keeping the cursor in-place, and still supporting a count prefix.\r\n\r\nhttps:\/\/sanctum.geek.nz\/cgit\/vim-fixed-join.git","install_details":"Drop plugin\/fixed_join.vim in your ~\/.vim\/plugin directory. Add doc\/fixed_join.txt in ~\/.vim\/doc if you want the help file. Otherwise, use your favourite Vim plugin package manager.\r\n\r\nTo remap normal J to use this instead of its default function, you could put this in your vimrc:\r\n\r\n    nmap J FixedJoin\r\n","5":"Drop plugin\/fixed_join.vim in your ~\/.vim\/plugin directory. Add doc\/fixed_join.txt in ~\/.vim\/doc if you want the help file. Otherwise, use your favourite Vim plugin package manager.\r\n\r\nTo remap normal J to use this instead of its default function, you could put this in your vimrc:\r\n\r\n    nmap J FixedJoin\r\n","first_name":"Tom","6":"Tom","last_name":"Ryder","7":"Ryder","releases":[{"0":"5691","vim_version":"6.0","1":"6.0","script_version":"0.5.0","2":"0.5.0","version_comment":"Restore \"restore cursor position\" code","3":"Restore \"restore cursor position\" code","package":"vim-fixed-join-0.5.0.tar.gz","4":"vim-fixed-join-0.5.0.tar.gz","src_id":"26087","5":"26087","creation_date":"1530186127","6":"1530186127"}]},"5690":{"script_id":"5690","0":"5690","script_name":"insert_suspend_hlsearch.vim","1":"insert_suspend_hlsearch.vim","script_type":"utility","2":"utility","summary":"Suspend search highlighting in insert mode","3":"Suspend search highlighting in insert mode","description":"This plugin quietly disables 'hlsearch' search highlighting if enabled when an insert operation is started, and puts it back once done, to avoid the distracting effect the highlighting can cause while writing.\r\n\r\nhttps:\/\/sanctum.geek.nz\/cgit\/vim-insert-suspend-hlsearch.git","4":"This plugin quietly disables 'hlsearch' search highlighting if enabled when an insert operation is started, and puts it back once done, to avoid the distracting effect the highlighting can cause while writing.\r\n\r\nhttps:\/\/sanctum.geek.nz\/cgit\/vim-insert-suspend-hlsearch.git","install_details":"Drop plugin\/insert_suspend_hlsearch.vim in your ~\/.vim\/plugin directory and autoload\/insert_suspend_hlsearch.vim in ~\/.vim\/autoload. Add doc\/insert_suspend_hlsearch.txt in ~\/.vim\/doc if you want the help file. Otherwise, use your favourite Vim plugin package manager.","5":"Drop plugin\/insert_suspend_hlsearch.vim in your ~\/.vim\/plugin directory and autoload\/insert_suspend_hlsearch.vim in ~\/.vim\/autoload. Add doc\/insert_suspend_hlsearch.txt in ~\/.vim\/doc if you want the help file. Otherwise, use your favourite Vim plugin package manager.","first_name":"Tom","6":"Tom","last_name":"Ryder","7":"Ryder","releases":[{"0":"5690","vim_version":"7.0","1":"7.0","script_version":"0.6.0","2":"0.6.0","version_comment":"Remove autoload","3":"Remove autoload","package":"vim-insert-suspend-hlsearch-0.6.0.tar.gz","4":"vim-insert-suspend-hlsearch-0.6.0.tar.gz","src_id":"26205","5":"26205","creation_date":"1536220484","6":"1536220484"}]},"5689":{"script_id":"5689","0":"5689","script_name":"nextag.vim","1":"nextag.vim","script_type":"utility","2":"utility","summary":"Move to next\/previous XML\/HTML tag","3":"Move to next\/previous XML\/HTML tag","description":"Move to next and previous tags in a SGML document, including XML and HTML. Use . and , to search for the next and previous tags, respectively. Prepended counts work, e.g. 5. as do operations, e.g. d. and visual mode e.g. v,. Doesn't match SGML comments or !DOCTYPES.\r\n\r\nhttps:\/\/sanctum.geek.nz\/cgit\/vim-nextag.git","4":"Move to next and previous tags in a SGML document, including XML and HTML. Use . and , to search for the next and previous tags, respectively. Prepended counts work, e.g. 5. as do operations, e.g. d. and visual mode e.g. v,. Doesn't match SGML comments or !DOCTYPES.\r\n\r\nhttps:\/\/sanctum.geek.nz\/cgit\/vim-nextag.git","install_details":"Drop plugin\/nextag.vim in your ~\/.vim\/plugin directory. Add doc\/nextag.txt in ~\/.vim\/doc if you want the help file. Otherwise, use your favourite Vim plugin package manager.","5":"Drop plugin\/nextag.vim in your ~\/.vim\/plugin directory. Add doc\/nextag.txt in ~\/.vim\/doc if you want the help file. Otherwise, use your favourite Vim plugin package manager.","first_name":"Tom","6":"Tom","last_name":"Ryder","7":"Ryder","releases":[{"0":"5689","vim_version":"7.0","1":"7.0","script_version":"0.2.0","2":"0.2.0","version_comment":"Structural tweaks, documentation reformat","3":"Structural tweaks, documentation reformat","package":"vim-nextag-0.2.0.tar.gz","4":"vim-nextag-0.2.0.tar.gz","src_id":"26048","5":"26048","creation_date":"1529265637","6":"1529265637"}]},"5688":{"script_id":"5688","0":"5688","script_name":"juvenile.vim","1":"juvenile.vim","script_type":"color scheme","2":"color scheme","summary":"Colorscheme with only grey comments and non-text","3":"Colorscheme with only grey comments and non-text","description":"Show comments and non-text elements in grey if GUI or 256 colours available, in defiance of Commander Rob Pike, but change nothing else, in deference to Commander Rob Pike:\r\n\r\n> Syntax highlighting is juvenile. When I was a child, I was taught\r\n> arithmetic using colored rods\r\n> (http:\/\/en.wikipedia.org\/wiki\/Cuisenaire_rods). I grew up and today I\r\n> use monochromatic numerals.\r\n> \r\n> -rob\r\n\r\nQuote source: https:\/\/groups.google.com\/forum\/message\/raw?msg=golang-nuts\/hJHCAaiL0so\/kG3BHV6QFfIJ\r\n\r\nhttps:\/\/sanctum.geek.nz\/cgit\/vim-juvenile.git","4":"Show comments and non-text elements in grey if GUI or 256 colours available, in defiance of Commander Rob Pike, but change nothing else, in deference to Commander Rob Pike:\r\n\r\n> Syntax highlighting is juvenile. When I was a child, I was taught\r\n> arithmetic using colored rods\r\n> (http:\/\/en.wikipedia.org\/wiki\/Cuisenaire_rods). I grew up and today I\r\n> use monochromatic numerals.\r\n> \r\n> -rob\r\n\r\nQuote source: https:\/\/groups.google.com\/forum\/message\/raw?msg=golang-nuts\/hJHCAaiL0so\/kG3BHV6QFfIJ\r\n\r\nhttps:\/\/sanctum.geek.nz\/cgit\/vim-juvenile.git","install_details":"Drop colors\/juvenile.vim in your ~\/.vim\/colors directory, or use your favourite Vim package manager.","5":"Drop colors\/juvenile.vim in your ~\/.vim\/colors directory, or use your favourite Vim package manager.","first_name":"Tom","6":"Tom","last_name":"Ryder","7":"Ryder","releases":[{"0":"5688","vim_version":"6.0","1":"6.0","script_version":"0.3.0","2":"0.3.0","version_comment":"Dark background for GUI, 16-color fallback","3":"Dark background for GUI, 16-color fallback","package":"vim-juvenile-0.3.0.tar.gz","4":"vim-juvenile-0.3.0.tar.gz","src_id":"26096","5":"26096","creation_date":"1530395733","6":"1530395733"}]},"5687":{"script_id":"5687","0":"5687","script_name":"vimteractive","1":"vimteractive","script_type":"ftplugin","2":"ftplugin","summary":"Sending commands from vim to interactive programs","3":"Sending commands from vim to interactive programs","description":"*vimteractive.txt*   Sending commands from vim to interactive programs\r\n\r\n                    Vimteractive - main help file\r\n\r\n\r\n==============================================================================\r\nCONTENTS                                               *vimteractive-contents*\r\n\r\n    1.Intro........................................|vimteractive-intro|\r\n    2.Usage........................................|vimteractive-usage|\r\n    3.Extending functionality......................|vimteractive-extending|\r\n    4.About........................................|vimteractive-about|\r\n    5.License......................................|vimteractive-license|\r\n\r\n==============================================================================\r\n1. Intro                                                  *vimteractive-intro*\r\n\r\nVimteractive was inspired by the workflow of the vim-ipython plugin:\r\n\r\n    https:\/\/github.com\/ivanov\/vim-ipython\r\n\r\nThis plugin is designed to extend a subset of the functionality of vim-ipython\r\nto other interpreters (including ipython). It is based around the unix\r\nphilosophy of \"do one thing and do it well\".  It aims to provide a robust and\r\nsimple link between text files and interactive interpreters. Vimteractive will\r\nnever aim to do things like autocompletion, leaving that to other, more\r\ndeveloped tools such as YouCompleteMe.\r\n\r\nThe activating commands are \r\n- ipython |:Iipython| \r\n- python  |:Ipython| \r\n- julia   |:Ijulia|\r\n- maple   |:Imaple|\r\n- bash    |:Ibash|\r\n- clojure |:Iclojure|\r\n- zsh     |:Izsh|\r\n\r\nYou can also let Vimteractive detect interpreter using |:Iterm| or just send\r\nsome lines: Vimteractive will create terminal if needed. Note: it's highly\r\nrecommended to use IPython as your default Python interpreter. You can set it\r\nlike this:\r\n\r\n\tlet g:vimteractive_default_shells = { 'python': 'ipython' }\r\n\r\nDefault Python REPL support for pasting is really bad and you should use\r\nIPython whenever possible. If you need to use default Python REPL, you must\r\nput newline after every top-level block.\r\n\r\nCommands may be sent from a text file to the chosen terminal using CTRL-S. \r\nSee |v_CTRL_S| for more details.\r\n\r\nSince this package leverages the native vim interactive terminal, it is \r\nonly compatible with vim 8 or greater.\r\n\r\n\r\n==============================================================================\r\n2. Usage                                                  *vimteractive-usage*\r\n\r\nTo use the key-bindings, you should first disable the CTRL-S default, which is\r\na terminal command to freeze the output. You can disable this by putting\r\n\r\nstty -ixon\r\n\r\ninto your .bashrc (or equivalent shell profile file)\r\n\r\n------------------------------------------------------------------------------\r\nExample usage:\r\n\r\nCreate a python file \"test.py\" with the following content:\r\n\r\n    import matplotlib.pyplot as plt\r\n    import numpy\r\n\r\n    fig, ax = plt.subplots()\r\n    x = numpy.linspace(-2,2,1000)\r\n    y = x**3-x\r\n    ax.plot(x, y)\r\n    ax.set_xlabel('$x$')\r\n    ax.set_ylabel('$y$')\r\n\r\nNow start an ipython interpreter in vim with :Iipython. You should see a\r\npreview window open above with your ipython prompt. Position your cursor over\r\nthe first line of test.py, and press  CTRL-S. You should see this\r\nline now appear in the first prompt of the preview window. Do the same with\r\nthe second and fourth lines. At the fourth line, you should see a figure\r\nappear once it's constructed with plt.subplots(). Continue by sending lines to\r\nthe interpreter. You can send multiple lines by doing a visual selection and\r\npressing CTRL-S.\r\n\r\nIf you switch windows with CTRL-W k, you will see the terminal buffer switch\r\nto a more usual looking normal-mode buffer, from which you can perform\r\ntraditional normal mode commands. However, if you try to insert, you will\r\nenter the terminal, and be able to enter commands interactively into the\r\nprompt as if you had run it in the command line. You can save this buffer if\r\nyou wish to a new file if it contains valuable output\r\n\r\nBy default every buffer is connected to separate terminal. If you want to\r\nconnect two buffers to one terminal, use |:Iconn| command.\r\n\r\n\r\nSupported terminals                                   *vimteractive-terminals*\r\n\r\n*:Iipython* \tActivate an ipython terminal\r\n*:Ipython*  \tActivate a python terminal\r\n*:Ijulia*   \tActivate a julia terminal\r\n*:Imaple*   \tActivate a maple terminal\r\n*:Ibash*    \tActivate a bash terminal\r\n*:Izsh*     \tActivate a zsh terminal\r\n*:Iclojure*\t\tActivate a clojure terminal\r\n*:Iterm*\t\tActivate a terminal based on current filetype\r\n\r\nSending commands                                                    *v_CTRL_S*\r\n\r\nCTRL-S sends lines of text to the interpreter in a mode-dependent manner:\r\n\r\nIn |Normal-mode|, CTRL-S sends the line currently occupied by the cursor\r\nthe terminal.\r\n\r\nIn |Insert-mode|, CTRL-S sends the line currently being edited, and then\r\nreturns to insert mode at the same location.\r\n\r\nIn |Visual-mode|, CTRL-S sends the current selection to the terminal.\r\n\r\nALT-S sends all lines from the start to the current line.\r\n\r\nIf there is no active terminal for current buffer, CTRL-S will automatically\r\ncreate one for you using |:Iterm|.\r\n\r\n==============================================================================\r\n3. Connecting to existing REPLs             *:Iconn* *vimteractive-connecting*\r\n:Iconn [{buffer}]\tConnect current buffer to REPL in {buffer}. You can\r\n\t\t\t\t\tconnect any number of buffers to one REPL. {buffer}\r\n\t\t\t\t\tcan be omitted if there is only one terminal.\r\n\r\n==============================================================================\r\n4. Extending functionality                            *vimteractive-extending*\r\n\r\nTo add a new interpreter to Vimteractive, you should define\r\ng:vimteractive_commands variable. For example:\r\n\r\n\tlet g:vimteractive_commands = { 'pythonasync': 'python -m asyncio' }\r\n\r\nwill provide you :Ipythonasync command starting Python 3.8+ asyncio REPL.\r\nIf you want to make this command default for python filetype, you should do\r\n\r\n\tlet g:vimteractive_default_shells = { 'python': 'pythonasync' }\r\n\r\nIf you see escape sequences appearing when you do CTRL-S for your interpreter,\r\nyou may try to disable bracketed paste mode for it:\r\n\r\n\tlet g:vimteractive_bracketed_paste = { 'pythonasync': 0 }\r\n\r\nIf your interpreter has slow-starting REPL (like Clojure), you may want to\r\nwait before sending data to it at the first time. Specify time to wait in\r\nmilliseconds like this:\r\n\r\n\tlet g:vimteractive_slow_prompt = { 'pythonasync': 200 }\r\n\r\nThis project is very much in an alpha phase, so if you have any issues that\r\narise on your system, feel free to contact me:\r\n\r\n    williamjameshandley@gmail.com.\r\n\r\n==============================================================================\r\n5. About                                          *vimteractive-functionality*\r\n\r\nThe core maintainer of vimteractive is:\r\n\r\n    Will Handley (GitHub: williamjameshandley)\r\n\r\nFind the latest version of vimteractive at:\r\n\r\n    http:\/\/github.com\/williamjameshandley\/vimteractive\r\n\r\n==============================================================================\r\n6. License                                              *vimteractive-license*\r\n\r\nVimteractive is licensed under GPL 3.0\r\n","4":"*vimteractive.txt*   Sending commands from vim to interactive programs\r\n\r\n                    Vimteractive - main help file\r\n\r\n\r\n==============================================================================\r\nCONTENTS                                               *vimteractive-contents*\r\n\r\n    1.Intro........................................|vimteractive-intro|\r\n    2.Usage........................................|vimteractive-usage|\r\n    3.Extending functionality......................|vimteractive-extending|\r\n    4.About........................................|vimteractive-about|\r\n    5.License......................................|vimteractive-license|\r\n\r\n==============================================================================\r\n1. Intro                                                  *vimteractive-intro*\r\n\r\nVimteractive was inspired by the workflow of the vim-ipython plugin:\r\n\r\n    https:\/\/github.com\/ivanov\/vim-ipython\r\n\r\nThis plugin is designed to extend a subset of the functionality of vim-ipython\r\nto other interpreters (including ipython). It is based around the unix\r\nphilosophy of \"do one thing and do it well\".  It aims to provide a robust and\r\nsimple link between text files and interactive interpreters. Vimteractive will\r\nnever aim to do things like autocompletion, leaving that to other, more\r\ndeveloped tools such as YouCompleteMe.\r\n\r\nThe activating commands are \r\n- ipython |:Iipython| \r\n- python  |:Ipython| \r\n- julia   |:Ijulia|\r\n- maple   |:Imaple|\r\n- bash    |:Ibash|\r\n- clojure |:Iclojure|\r\n- zsh     |:Izsh|\r\n\r\nYou can also let Vimteractive detect interpreter using |:Iterm| or just send\r\nsome lines: Vimteractive will create terminal if needed. Note: it's highly\r\nrecommended to use IPython as your default Python interpreter. You can set it\r\nlike this:\r\n\r\n\tlet g:vimteractive_default_shells = { 'python': 'ipython' }\r\n\r\nDefault Python REPL support for pasting is really bad and you should use\r\nIPython whenever possible. If you need to use default Python REPL, you must\r\nput newline after every top-level block.\r\n\r\nCommands may be sent from a text file to the chosen terminal using CTRL-S. \r\nSee |v_CTRL_S| for more details.\r\n\r\nSince this package leverages the native vim interactive terminal, it is \r\nonly compatible with vim 8 or greater.\r\n\r\n\r\n==============================================================================\r\n2. Usage                                                  *vimteractive-usage*\r\n\r\nTo use the key-bindings, you should first disable the CTRL-S default, which is\r\na terminal command to freeze the output. You can disable this by putting\r\n\r\nstty -ixon\r\n\r\ninto your .bashrc (or equivalent shell profile file)\r\n\r\n------------------------------------------------------------------------------\r\nExample usage:\r\n\r\nCreate a python file \"test.py\" with the following content:\r\n\r\n    import matplotlib.pyplot as plt\r\n    import numpy\r\n\r\n    fig, ax = plt.subplots()\r\n    x = numpy.linspace(-2,2,1000)\r\n    y = x**3-x\r\n    ax.plot(x, y)\r\n    ax.set_xlabel('$x$')\r\n    ax.set_ylabel('$y$')\r\n\r\nNow start an ipython interpreter in vim with :Iipython. You should see a\r\npreview window open above with your ipython prompt. Position your cursor over\r\nthe first line of test.py, and press  CTRL-S. You should see this\r\nline now appear in the first prompt of the preview window. Do the same with\r\nthe second and fourth lines. At the fourth line, you should see a figure\r\nappear once it's constructed with plt.subplots(). Continue by sending lines to\r\nthe interpreter. You can send multiple lines by doing a visual selection and\r\npressing CTRL-S.\r\n\r\nIf you switch windows with CTRL-W k, you will see the terminal buffer switch\r\nto a more usual looking normal-mode buffer, from which you can perform\r\ntraditional normal mode commands. However, if you try to insert, you will\r\nenter the terminal, and be able to enter commands interactively into the\r\nprompt as if you had run it in the command line. You can save this buffer if\r\nyou wish to a new file if it contains valuable output\r\n\r\nBy default every buffer is connected to separate terminal. If you want to\r\nconnect two buffers to one terminal, use |:Iconn| command.\r\n\r\n\r\nSupported terminals                                   *vimteractive-terminals*\r\n\r\n*:Iipython* \tActivate an ipython terminal\r\n*:Ipython*  \tActivate a python terminal\r\n*:Ijulia*   \tActivate a julia terminal\r\n*:Imaple*   \tActivate a maple terminal\r\n*:Ibash*    \tActivate a bash terminal\r\n*:Izsh*     \tActivate a zsh terminal\r\n*:Iclojure*\t\tActivate a clojure terminal\r\n*:Iterm*\t\tActivate a terminal based on current filetype\r\n\r\nSending commands                                                    *v_CTRL_S*\r\n\r\nCTRL-S sends lines of text to the interpreter in a mode-dependent manner:\r\n\r\nIn |Normal-mode|, CTRL-S sends the line currently occupied by the cursor\r\nthe terminal.\r\n\r\nIn |Insert-mode|, CTRL-S sends the line currently being edited, and then\r\nreturns to insert mode at the same location.\r\n\r\nIn |Visual-mode|, CTRL-S sends the current selection to the terminal.\r\n\r\nALT-S sends all lines from the start to the current line.\r\n\r\nIf there is no active terminal for current buffer, CTRL-S will automatically\r\ncreate one for you using |:Iterm|.\r\n\r\n==============================================================================\r\n3. Connecting to existing REPLs             *:Iconn* *vimteractive-connecting*\r\n:Iconn [{buffer}]\tConnect current buffer to REPL in {buffer}. You can\r\n\t\t\t\t\tconnect any number of buffers to one REPL. {buffer}\r\n\t\t\t\t\tcan be omitted if there is only one terminal.\r\n\r\n==============================================================================\r\n4. Extending functionality                            *vimteractive-extending*\r\n\r\nTo add a new interpreter to Vimteractive, you should define\r\ng:vimteractive_commands variable. For example:\r\n\r\n\tlet g:vimteractive_commands = { 'pythonasync': 'python -m asyncio' }\r\n\r\nwill provide you :Ipythonasync command starting Python 3.8+ asyncio REPL.\r\nIf you want to make this command default for python filetype, you should do\r\n\r\n\tlet g:vimteractive_default_shells = { 'python': 'pythonasync' }\r\n\r\nIf you see escape sequences appearing when you do CTRL-S for your interpreter,\r\nyou may try to disable bracketed paste mode for it:\r\n\r\n\tlet g:vimteractive_bracketed_paste = { 'pythonasync': 0 }\r\n\r\nIf your interpreter has slow-starting REPL (like Clojure), you may want to\r\nwait before sending data to it at the first time. Specify time to wait in\r\nmilliseconds like this:\r\n\r\n\tlet g:vimteractive_slow_prompt = { 'pythonasync': 200 }\r\n\r\nThis project is very much in an alpha phase, so if you have any issues that\r\narise on your system, feel free to contact me:\r\n\r\n    williamjameshandley@gmail.com.\r\n\r\n==============================================================================\r\n5. About                                          *vimteractive-functionality*\r\n\r\nThe core maintainer of vimteractive is:\r\n\r\n    Will Handley (GitHub: williamjameshandley)\r\n\r\nFind the latest version of vimteractive at:\r\n\r\n    http:\/\/github.com\/williamjameshandley\/vimteractive\r\n\r\n==============================================================================\r\n6. License                                              *vimteractive-license*\r\n\r\nVimteractive is licensed under GPL 3.0\r\n","install_details":"","5":"","first_name":"Will","6":"Will","last_name":"Handley","7":"Handley","releases":[{"0":"5687","vim_version":"8.1","1":"8.1","script_version":"2.4.1","2":"2.4.1","version_comment":"Bug fix to 2.4.0","3":"Bug fix to 2.4.0","package":"vimteractive.tar.gz","4":"vimteractive.tar.gz","src_id":"27441","5":"27441","creation_date":"1610246841","6":"1610246841"},{"0":"5687","vim_version":"7.0","1":"7.0","script_version":"2.4.0","2":"2.4.0","version_comment":"Fix for automatic scroll","3":"Fix for automatic scroll","package":"vimteractive.tar.gz","4":"vimteractive.tar.gz","src_id":"27435","5":"27435","creation_date":"1609376322","6":"1609376322"},{"0":"5687","vim_version":"8.0","1":"8.0","script_version":"2.2.0","2":"2.2.0","version_comment":"Added support for vertical terminals","3":"Added support for vertical terminals","package":"vimteractive.tar.gz","4":"vimteractive.tar.gz","src_id":"26867","5":"26867","creation_date":"1576261627","6":"1576261627"},{"0":"5687","vim_version":"7.0","1":"7.0","script_version":"2.1.0","2":"2.1.0","version_comment":"Visual selection improvement","3":"Visual selection improvement","package":"vimteractive.tar.gz","4":"vimteractive.tar.gz","src_id":"26810","5":"26810","creation_date":"1572901629","6":"1572901629"},{"0":"5687","vim_version":"8.0","1":"8.0","script_version":"2.0","2":"2.0","version_comment":"Now with multiple terminals","3":"Now with multiple terminals","package":"vimteractive.tar.gz","4":"vimteractive.tar.gz","src_id":"26692","5":"26692","creation_date":"1565053120","6":"1565053120"},{"0":"5687","vim_version":"7.0","1":"7.0","script_version":"1.7","2":"1.7","version_comment":"Added support for autodetection of terminal types","3":"Added support for autodetection of terminal types","package":"vimteractive.tar.gz","4":"vimteractive.tar.gz","src_id":"26586","5":"26586","creation_date":"1562281933","6":"1562281933"},{"0":"5687","vim_version":"8.0","1":"8.0","script_version":"1.5","2":"1.5","version_comment":"Added julia support","3":"Added julia support","package":"vimteractive.tar.gz","4":"vimteractive.tar.gz","src_id":"26560","5":"26560","creation_date":"1561324180","6":"1561324180"},{"0":"5687","vim_version":"8.0","1":"8.0","script_version":"1.1","2":"1.1","version_comment":"Better pasting into ipython","3":"Better pasting into ipython","package":"vimteractive.tar.gz","4":"vimteractive.tar.gz","src_id":"26243","5":"26243","creation_date":"1539397459","6":"1539397459"},{"0":"5687","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Switch from pexpect to native vim terminal","3":"Switch from pexpect to native vim terminal","package":"vimteractive.tar.gz","4":"vimteractive.tar.gz","src_id":"26066","5":"26066","creation_date":"1529561378","6":"1529561378"},{"0":"5687","vim_version":"8.0","1":"8.0","script_version":"0.2","2":"0.2","version_comment":"Further robustness improvements","3":"Further robustness improvements","package":"vimteractive.tar.gz","4":"vimteractive.tar.gz","src_id":"25995","5":"25995","creation_date":"1527410567","6":"1527410567"},{"0":"5687","vim_version":"8.0","1":"8.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"vimteractive.tar.gz","4":"vimteractive.tar.gz","src_id":"25993","5":"25993","creation_date":"1527403420","6":"1527403420"}]},"5686":{"script_id":"5686","0":"5686","script_name":"Exoskeleton","1":"Exoskeleton","script_type":"utility","2":"utility","summary":"Skeleton - improved!","3":"Skeleton - improved!","description":"NOTE: Development happens on github: https:\/\/github.com\/joereynolds\/exoskeleton.vim\r\n \r\n# Exoskeleton - Skeleton improved\r\n\r\nOpen files and evaluates vimscript from a template.\r\n\r\nExample:\r\n\r\n```\r\nThe year is {{strftime(\"%Y\")}}\r\n```\r\n\r\nTransforms to\r\n\r\n```\r\nThe year is 2018\r\n```\r\n\r\n# Installation\r\n\r\nUsing vim-plug\r\n\r\n```\r\nPlug 'joereynolds\/exoskeleton.vim'\r\n```\r\n\r\n# Templates\r\n\r\nThere are two kinds of templates `ft` and `place`.\r\n\r\n## ft\r\n\r\n`ft` is the traditional skeleton that you're used to, but this time with vimscript!\r\n     Dump your `ft` templates in `~\/.vim\/exoskeleton\/ft` e.g. `~\/.vim\/exoskeleton\/ft\/test.php`\r\n\r\nAny vimscript enclosed in these (configurable) delimiters will be evaluated.\r\n\r\n```\r\nCopyright {{strftime(\"%Y\")}}\r\nThe year is {{strftime(\"%Y\")}}\r\n\r\nThis string has no placeholder\r\n\r\nThe files in here are: \r\n{{glob(\".\/*\")}}\r\n```\r\nTransforms to\r\n```\r\nCopyright 2018\r\nThe year is 2018\r\n\r\nThis string has no placeholder\r\n\r\nThe files in here are:\r\n.\/Desktop\r\n.\/Documents\r\n.\/Downloads\r\n.\/Music\r\n.\/Pictures\r\n.\/Public\r\n.\/Templates\r\n.\/Videos\r\n.\/a.php\r\n.\/code\r\n.\/examples.desktop\r\n.\/examples.desktop.gpg\r\n.\/install-inspect-deb\r\n.\/neovim-gtk\r\n.\/npm-debug.log\r\n.\/phpactor.log\r\n.\/programs\r\n.\/salutem\r\n.\/snap\r\n.\/sqlp\r\n.\/test\r\n.\/test_file\r\n.\/test_file.sig\r\n```\r\n\r\n## place examples\r\n\r\n`place` is a mapping to a directory on your filesystem, this is mega handy for the newer\r\n         frameworks that are cropping up and force you to a specific structure.\r\n         Dump your `place` templates in `~\/.vim\/exoskeleton\/place`\r\n\r\n\r\n(Nested in ~\/.vim\/exoskeleton\/place\/home-joe-code-models)\r\n\r\n```\r\n mappings to switch between vim or tmux tabs when no vim or tmux split is available, similarly to what happens in the i3 window manager in a workspace with both tabs and splits. It can additionally be configured to automatically create a container when reaching the boundary of the navigation space.","4":"Inspired by vim-tmux-navigator, this plugin further extends the  mappings to switch between vim or tmux tabs when no vim or tmux split is available, similarly to what happens in the i3 window manager in a workspace with both tabs and splits. It can additionally be configured to automatically create a container when reaching the boundary of the navigation space.","install_details":"See the github page: http:\/\/github.com\/urbainvaes\/vim-tmux-pilot","5":"See the github page: http:\/\/github.com\/urbainvaes\/vim-tmux-pilot","first_name":"Urbain","6":"Urbain","last_name":"Vaes","7":"Vaes","releases":[{"0":"5681","vim_version":"8.0","1":"8.0","script_version":"1.0","2":"1.0","version_comment":"- Fix minor bugs.\r\n- Add support for vim teminal, if available; the plugin should now work equally well in vim and neovim.\r\n- Introduce g:pilot_split_or_new, which determines whether to :split or :new when creating a new window.","3":"- Fix minor bugs.\r\n- Add support for vim teminal, if available; the plugin should now work equally well in vim and neovim.\r\n- Introduce g:pilot_split_or_new, which determines whether to :split or :new when creating a new window.","package":"vim-tmux-pilot-1.0.tar","4":"vim-tmux-pilot-1.0.tar","src_id":"27193","5":"27193","creation_date":"1591307012","6":"1591307012"},{"0":"5681","vim_version":"8.0","1":"8.0","script_version":"0.2","2":"0.2","version_comment":"- Enable user-defined keybindings.\r\n- Add keybinding  to move to previous pane.","3":"- Enable user-defined keybindings.\r\n- Add keybinding  to move to previous pane.","package":"vim-tmux-pilot-0.2.tar.gz","4":"vim-tmux-pilot-0.2.tar.gz","src_id":"26789","5":"26789","creation_date":"1571701689","6":"1571701689"},{"0":"5681","vim_version":"8.0","1":"8.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"vim-tmux-pilot-0.1.tar.gz","4":"vim-tmux-pilot-0.1.tar.gz","src_id":"25965","5":"25965","creation_date":"1525735086","6":"1525735086"}]},"5680":{"script_id":"5680","0":"5680","script_name":"yaTranslator","1":"yaTranslator","script_type":"utility","2":"utility","summary":" Translation inside VIM","3":" Translation inside VIM","description":"Translate text with the Yandex.Translate service (https:\/\/tech.yandex.com\/translate\/)","4":"Translate text with the Yandex.Translate service (https:\/\/tech.yandex.com\/translate\/)","install_details":"Please refer to GitHub page (https:\/\/github.com\/ademin\/yaTranslator) to find out installation details.","5":"Please refer to GitHub page (https:\/\/github.com\/ademin\/yaTranslator) to find out installation details.","first_name":"Alexey","6":"Alexey","last_name":"Demin","7":"Demin","releases":[{"0":"5680","vim_version":"7.0","1":"7.0","script_version":"0.7","2":"0.7","version_comment":"Initial upload","3":"Initial upload","package":"yaTranslator.tar.gz","4":"yaTranslator.tar.gz","src_id":"25964","5":"25964","creation_date":"1525730816","6":"1525730816"}]},"5679":{"script_id":"5679","0":"5679","script_name":"vim-remembrall","1":"vim-remembrall","script_type":"utility","2":"utility","summary":"Helps users remember their mappings","3":"Helps users remember their mappings","description":"This plugin makes it possible to automatically open a helper window with a list of mappings that start with a given key when that key is pressed. \r\n\r\nSee the github repository for more details: http:\/\/github.com\/urbainvaes\/vim-remembrall","4":"This plugin makes it possible to automatically open a helper window with a list of mappings that start with a given key when that key is pressed. \r\n\r\nSee the github repository for more details: http:\/\/github.com\/urbainvaes\/vim-remembrall","install_details":"","5":"","first_name":"Urbain","6":"Urbain","last_name":"Vaes","7":"Vaes","releases":[{"0":"5679","vim_version":"8.0","1":"8.0","script_version":"v0.2","2":"v0.2","version_comment":"Initial upload","3":"Initial upload","package":"vim-remembrall-v0.2.tar.gz","4":"vim-remembrall-v0.2.tar.gz","src_id":"25963","5":"25963","creation_date":"1525665043","6":"1525665043"}]},"5678":{"script_id":"5678","0":"5678","script_name":"vim-preview","1":"vim-preview","script_type":"utility","2":"utility","summary":"The missing preview window for vim","3":"The missing preview window for vim","description":"This plugin solves a series of user experience problems in vim's preview window and provide a handy way to preview tags, files and function signatures.\r\n\r\nCommands\r\n\r\nPreviewTag\t[tagname]\tDisplay the tag in the preview window circularly\r\nPreviewFile\t[+cmd] filename\tDisplay the file in the preview window\r\nPreviewClose\tN\/A\tClose the preview window\r\nPreviewGoto\tcommand\tOpen the previewing file in a non-preview window\r\nPreviewScroll\toffset\tScroll preview window without leaving current window or inser mode\r\nPreviewQuickfix\t[linenr]\tPreview file in quickfix list\r\nPreviewSignature\t[function name]\tPreview the function signature circularly in the command line\r\n\r\nDocumentation\r\n\r\nhttps:\/\/github.com\/skywind3000\/vim-preview","4":"This plugin solves a series of user experience problems in vim's preview window and provide a handy way to preview tags, files and function signatures.\r\n\r\nCommands\r\n\r\nPreviewTag\t[tagname]\tDisplay the tag in the preview window circularly\r\nPreviewFile\t[+cmd] filename\tDisplay the file in the preview window\r\nPreviewClose\tN\/A\tClose the preview window\r\nPreviewGoto\tcommand\tOpen the previewing file in a non-preview window\r\nPreviewScroll\toffset\tScroll preview window without leaving current window or inser mode\r\nPreviewQuickfix\t[linenr]\tPreview file in quickfix list\r\nPreviewSignature\t[function name]\tPreview the function signature circularly in the command line\r\n\r\nDocumentation\r\n\r\nhttps:\/\/github.com\/skywind3000\/vim-preview","install_details":"Extract files into ~\/.vim or use vim-plug:\r\n\r\nPlug 'skywind3000\/vim-preview'","5":"Extract files into ~\/.vim or use vim-plug:\r\n\r\nPlug 'skywind3000\/vim-preview'","first_name":"Wei","6":"Wei","last_name":"Lin","7":"Lin","releases":[{"0":"5678","vim_version":"7.4","1":"7.4","script_version":"1.0.0","2":"1.0.0","version_comment":"Initial upload","3":"Initial upload","package":"vim-preview.zip","4":"vim-preview.zip","src_id":"25962","5":"25962","creation_date":"1525527221","6":"1525527221"}]},"5677":{"script_id":"5677","0":"5677","script_name":"traces.vim","1":"traces.vim","script_type":"utility","2":"utility","summary":"Range, pattern and substitute preview for Vim ","3":"Range, pattern and substitute preview for Vim ","description":"This plugin highlights patterns and ranges for Ex commands in Command-line mode.\r\n\r\nIt also provides live preview for the following Ex commands:\r\n:substitute\r\n:smagic\r\n:snomagic\r\n\r\nRequirements: Vim v8.0.1206+\r\n\r\ngit repository: https:\/\/github.com\/markonm\/traces.vim","4":"This plugin highlights patterns and ranges for Ex commands in Command-line mode.\r\n\r\nIt also provides live preview for the following Ex commands:\r\n:substitute\r\n:smagic\r\n:snomagic\r\n\r\nRequirements: Vim v8.0.1206+\r\n\r\ngit repository: https:\/\/github.com\/markonm\/traces.vim","install_details":"unzip the archive to ~\/.vim\/pack\/plugins\/start\/","5":"unzip the archive to ~\/.vim\/pack\/plugins\/start\/","first_name":"Marko","6":"Marko","last_name":"Nimac","7":"Nimac","releases":[{"0":"5677","vim_version":"8.0","1":"8.0","script_version":"v1.1.0","2":"v1.1.0","version_comment":"New options\r\n  g:traces_num_range_preview\r\n  g:traces_enabled\r\nPattern preview for :sort\r\nVarious bugs fixed\r\n\r\n","3":"New options\r\n  g:traces_num_range_preview\r\n  g:traces_enabled\r\nPattern preview for :sort\r\nVarious bugs fixed\r\n\r\n","package":"traces.vim-1.1.0.zip","4":"traces.vim-1.1.0.zip","src_id":"26355","5":"26355","creation_date":"1548125718","6":"1548125718"},{"0":"5677","vim_version":"8.0","1":"8.0","script_version":"v1.0.0","2":"v1.0.0","version_comment":"Initial upload","3":"Initial upload","package":"traces.vim-1.0.0.zip","4":"traces.vim-1.0.0.zip","src_id":"25956","5":"25956","creation_date":"1525155996","6":"1525155996"}]},"5676":{"script_id":"5676","0":"5676","script_name":"Flexagon","1":"Flexagon","script_type":"utility","2":"utility","summary":"Fold switcher with variety of prepackaged folds","3":"Fold switcher with variety of prepackaged folds","description":"A variety of useful vim fold expressions with a tab completing \"Fold\" command.\r\nPublic git at https:\/\/github.com\/fourjay\/vim-flexagon\r\nMany of the folds are meant to cue off of \"natural\" markers, including:\r\n* Blank line separators (an ad-hoc \"paragraph\")\r\n* Doxygen style comments\r\n* Embedded wiki or markdown style headers in comments","4":"A variety of useful vim fold expressions with a tab completing \"Fold\" command.\r\nPublic git at https:\/\/github.com\/fourjay\/vim-flexagon\r\nMany of the folds are meant to cue off of \"natural\" markers, including:\r\n* Blank line separators (an ad-hoc \"paragraph\")\r\n* Doxygen style comments\r\n* Embedded wiki or markdown style headers in comments","install_details":"Packaged as a tar of plugin, autoload and doc directory. Install has only been tested with plugin managers, but should work OK with manual install","5":"Packaged as a tar of plugin, autoload and doc directory. Install has only been tested with plugin managers, but should work OK with manual install","first_name":"Josef","6":"Josef","last_name":"Fortier","7":"Fortier","releases":[{"0":"5676","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"vim-flexagon.tgz","4":"vim-flexagon.tgz","src_id":"25942","5":"25942","creation_date":"1524432026","6":"1524432026"}]},"5675":{"script_id":"5675","0":"5675","script_name":"git-remote-open","1":"git-remote-open","script_type":"utility","2":"utility","summary":"Copy\/Open url of files directly from vim on github\/bitbucket","3":"Copy\/Open url of files directly from vim on github\/bitbucket","description":"Open\/copy the current line or a selection of lines on github\/bitbucket directly from vim\r\n\r\nMore details:\r\n\r\nhttps:\/\/github.com\/nwochaadim\/git-remote-open\/blob\/master\/README.md\r\n","4":"Open\/copy the current line or a selection of lines on github\/bitbucket directly from vim\r\n\r\nMore details:\r\n\r\nhttps:\/\/github.com\/nwochaadim\/git-remote-open\/blob\/master\/README.md\r\n","install_details":"Use either Pathogen or Vundle.\r\n\r\nInstallation details: https:\/\/github.com\/nwochaadim\/git-remote-open\/blob\/master\/README.md#installation","5":"Use either Pathogen or Vundle.\r\n\r\nInstallation details: https:\/\/github.com\/nwochaadim\/git-remote-open\/blob\/master\/README.md#installation","first_name":"Adim","6":"Adim","last_name":"Nwocha","7":"Nwocha","releases":[{"0":"5675","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"git-remote-open.tar.gz","4":"git-remote-open.tar.gz","src_id":"25941","5":"25941","creation_date":"1524394432","6":"1524394432"}]},"5674":{"script_id":"5674","0":"5674","script_name":"move-less","1":"move-less","script_type":"utility","2":"utility","summary":"plugin for faster navigation without changing the cursor position","3":"plugin for faster navigation without changing the cursor position","description":"This plugin is a tool for navigating inside of a file without moving the cursor to another line.\r\nThe idea is that you fold the space between your line and the target destination and then jump to the target position. \r\n\r\nTo archive this there is a so called move-less-mode which you can enter by typing m.\r\n\r\nYou can now also use it to generate a temporary upper and or bottom folding. So, you can place to distance section from the upper and the bottom together. (see meaning of 'p' while in move less mode)\r\n\r\nIf you want to remap the setting you can just create a mapping which calls the function MoveLessMode.\r\n\r\nIf you are in the move-less mode you can navigate like the following:\r\n\r\nj: Type once and your line will be displayed at the top (if possible). Every further click will fold lines below your cursor. So you can see the text under your cursor. The number of lines which are fold are defined by the scroll attribute.\r\n\r\nk: Type once and your line will be displayed at the bottom (if possible). Every further click will fold lines below your cursor, so you can see the upper text. The number of lines which are fold are defined by the scroll attribute.\r\n\r\nJ: Type once and your line will be displayed at the top (if possible). Any further click will reduce the fold below your cursor position. So, that you are able to see text again which you already have fold (kind of an undo of j)\r\n\r\nK: Type once and your line will be displayed at the bottom. Any further click will reduce the fold above your cursor position. So, that you are able to see text again which you already have fold (kind of an undo of k)\r\n\r\nk: Type once and your line will be displayed at the middle. Any further click will fold the text above and below your cursor position. So, that you are able to search your target positon in both directions.\r\n\r\nh: Type once and your line will be displayed at the middle. Any further click will reduce the fold above and below your cursor position. So, you can see the text again which you already fold. It's kind of an undo for k.\r\n\r\n: Abort move less mode and delete all foldings, you are not able to jump to Any distance place now.\r\n\r\np: Stop the move less mode but let the folding remain (p)ermanently. In fact it's just more permanent then the normal behaviour it's also temporary until you use the mode less mode next time. If you just want to unfold later you can go to move less mode and end it directly with . This new feature permanent feature should be handy if you want to edit two places in the file which has a big distance.\r\n\r\nAny other key: Move less mode will directly be ended, but folding will be temporary remain. From now on, you can jump over the folding to get to your target position. You can use Any vim method you like for this action. For example move-less is intended to work pretty well with easymotion.\r\nAfter such an action the folding will be immediately removed. It is only intended to be used for navigation without moving.\r\n\r\nIt's also available at github:\r\nhttps:\/\/github.com\/anschnapp\/move-less\r\n","4":"This plugin is a tool for navigating inside of a file without moving the cursor to another line.\r\nThe idea is that you fold the space between your line and the target destination and then jump to the target position. \r\n\r\nTo archive this there is a so called move-less-mode which you can enter by typing m.\r\n\r\nYou can now also use it to generate a temporary upper and or bottom folding. So, you can place to distance section from the upper and the bottom together. (see meaning of 'p' while in move less mode)\r\n\r\nIf you want to remap the setting you can just create a mapping which calls the function MoveLessMode.\r\n\r\nIf you are in the move-less mode you can navigate like the following:\r\n\r\nj: Type once and your line will be displayed at the top (if possible). Every further click will fold lines below your cursor. So you can see the text under your cursor. The number of lines which are fold are defined by the scroll attribute.\r\n\r\nk: Type once and your line will be displayed at the bottom (if possible). Every further click will fold lines below your cursor, so you can see the upper text. The number of lines which are fold are defined by the scroll attribute.\r\n\r\nJ: Type once and your line will be displayed at the top (if possible). Any further click will reduce the fold below your cursor position. So, that you are able to see text again which you already have fold (kind of an undo of j)\r\n\r\nK: Type once and your line will be displayed at the bottom. Any further click will reduce the fold above your cursor position. So, that you are able to see text again which you already have fold (kind of an undo of k)\r\n\r\nk: Type once and your line will be displayed at the middle. Any further click will fold the text above and below your cursor position. So, that you are able to search your target positon in both directions.\r\n\r\nh: Type once and your line will be displayed at the middle. Any further click will reduce the fold above and below your cursor position. So, you can see the text again which you already fold. It's kind of an undo for k.\r\n\r\n: Abort move less mode and delete all foldings, you are not able to jump to Any distance place now.\r\n\r\np: Stop the move less mode but let the folding remain (p)ermanently. In fact it's just more permanent then the normal behaviour it's also temporary until you use the mode less mode next time. If you just want to unfold later you can go to move less mode and end it directly with . This new feature permanent feature should be handy if you want to edit two places in the file which has a big distance.\r\n\r\nAny other key: Move less mode will directly be ended, but folding will be temporary remain. From now on, you can jump over the folding to get to your target position. You can use Any vim method you like for this action. For example move-less is intended to work pretty well with easymotion.\r\nAfter such an action the folding will be immediately removed. It is only intended to be used for navigation without moving.\r\n\r\nIt's also available at github:\r\nhttps:\/\/github.com\/anschnapp\/move-less\r\n","install_details":"","5":"","first_name":"Andreas","6":"Andreas","last_name":"Schnapp","7":"Schnapp","releases":[{"0":"5674","vim_version":"7.0","1":"7.0","script_version":"1.4","2":"1.4","version_comment":"* record the jump over the fold regardless if the user navigation was a jump command\r\n* Provides mappings for shortcuts used in MoveLess Mode","3":"* record the jump over the fold regardless if the user navigation was a jump command\r\n* Provides mappings for shortcuts used in MoveLess Mode","package":"move-less-1.4.tar.gz","4":"move-less-1.4.tar.gz","src_id":"26368","5":"26368","creation_date":"1549427295","6":"1549427295"},{"0":"5674","vim_version":"7.0","1":"7.0","script_version":"1.3","2":"1.3","version_comment":"If move less mode is ended with p (for permanent) the folding will remain. \r\nHandy for editing far away distances form up and below together. \r\n\r\nThen you can more easily yank, paste, replace, create macros etc. between this two places.","3":"If move less mode is ended with p (for permanent) the folding will remain. \r\nHandy for editing far away distances form up and below together. \r\n\r\nThen you can more easily yank, paste, replace, create macros etc. between this two places.","package":"move-less-1.3.tar.gz","4":"move-less-1.3.tar.gz","src_id":"26112","5":"26112","creation_date":"1530862098","6":"1530862098"},{"0":"5674","vim_version":"7.0","1":"7.0","script_version":"1.2.1","2":"1.2.1","version_comment":"* just fix a bug when ending move less mode via ESC","3":"* just fix a bug when ending move less mode via ESC","package":"move-less-1.2.1.tar.gz","4":"move-less-1.2.1.tar.gz","src_id":"25968","5":"25968","creation_date":"1525839693","6":"1525839693"},{"0":"5674","vim_version":"7.0","1":"7.0","script_version":"1.2","2":"1.2","version_comment":"* move-less navigation will not add entries to the jumplist any more\r\n* make buffer local variables more unique to avoid collisions","3":"* move-less navigation will not add entries to the jumplist any more\r\n* make buffer local variables more unique to avoid collisions","package":"move-less-1.2.tar.gz","4":"move-less-1.2.tar.gz","src_id":"25967","5":"25967","creation_date":"1525837887","6":"1525837887"},{"0":"5674","vim_version":"7.0","1":"7.0","script_version":"1.1","2":"1.1","version_comment":"* support a walk over the folding where the folding remains until the cursor is outside of the folding area\r\n* if the move less mode was ended but no jump or walk over the fold appears the move less code will be continued where it was stopped when it is started again\r\n* remove duplicate tag in move less doc","3":"* support a walk over the folding where the folding remains until the cursor is outside of the folding area\r\n* if the move less mode was ended but no jump or walk over the fold appears the move less code will be continued where it was stopped when it is started again\r\n* remove duplicate tag in move less doc","package":"move-less-1.1.tar.gz","4":"move-less-1.1.tar.gz","src_id":"25955","5":"25955","creation_date":"1525125778","6":"1525125778"},{"0":"5674","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"move-less.tar.gz","4":"move-less.tar.gz","src_id":"25940","5":"25940","creation_date":"1524392285","6":"1524392285"}]},"5673":{"script_id":"5673","0":"5673","script_name":"vim-hardaway","1":"vim-hardaway","script_type":"color scheme","2":"color scheme","summary":"Vim colorscheme with Airline integration. ","3":"Vim colorscheme with Airline integration. ","description":"A dark vim colorscheme with color support for both terminal and gui.\r\n\r\nScreenshot - https:\/\/evturn.com\/static\/vim-hardaway-screenshot.png\r\n\r\n* Includes a matching vim-airline theme\r\n* Extended syntax highlighting for less common filetypes (Haskell, PostCSS, netrw, NERDTree)","4":"A dark vim colorscheme with color support for both terminal and gui.\r\n\r\nScreenshot - https:\/\/evturn.com\/static\/vim-hardaway-screenshot.png\r\n\r\n* Includes a matching vim-airline theme\r\n* Extended syntax highlighting for less common filetypes (Haskell, PostCSS, netrw, NERDTree)","install_details":"Unzip the script package \r\nor \r\nclone the repo https:\/\/github.com\/evturn\/vim-hardaway\r\n\r\nWith the package contents located in your runtimepath, set colorscheme to vimhardaway your .vimrc","5":"Unzip the script package \r\nor \r\nclone the repo https:\/\/github.com\/evturn\/vim-hardaway\r\n\r\nWith the package contents located in your runtimepath, set colorscheme to vimhardaway your .vimrc","first_name":"Evan","6":"Evan","last_name":"Turner","7":"Turner","releases":[{"0":"5673","vim_version":"7.0","1":"7.0","script_version":"0.1.0","2":"0.1.0","version_comment":"Rename colorscheme and airline global variables","3":"Rename colorscheme and airline global variables","package":"vim-hardaway.zip","4":"vim-hardaway.zip","src_id":"26255","5":"26255","creation_date":"1541250981","6":"1541250981"},{"0":"5673","vim_version":"7.0","1":"7.0","script_version":"0.0.2","2":"0.0.2","version_comment":"Remove color set to none causing error output on load","3":"Remove color set to none causing error output on load","package":"vim-hardaway-0.0.2.zip","4":"vim-hardaway-0.0.2.zip","src_id":"25958","5":"25958","creation_date":"1525278013","6":"1525278013"},{"0":"5673","vim_version":"7.0","1":"7.0","script_version":"0.0.1","2":"0.0.1","version_comment":"Initial upload","3":"Initial upload","package":"vim-hardaway.zip","4":"vim-hardaway.zip","src_id":"25915","5":"25915","creation_date":"1523459984","6":"1523459984"}]},"5672":{"script_id":"5672","0":"5672","script_name":"rested","1":"rested","script_type":"color scheme","2":"color scheme","summary":"A desert based scheme with more colors.","3":"A desert based scheme with more colors.","description":"The rested.vim is based on desert.vim by Hans Fugal.\r\n\r\nIt is a dark color scheme, and more or less resembles standard\r\ndark color schemes provided with Vim.\r\n\r\nSee the link below for a screenshot with common elements taken\r\nfrom :help syntax.\r\n\r\n    https:\/\/github.com\/Radialsum\/config\/blob\/master\/rested.png\r\n\r\nIt was triggered by the quest to find perceptually equidistant\r\ncolors or perceptually-distinct colors. However, the currently\r\nused colors do not necessarily fit either criteria though!\r\n\r\nThe colors are mostly influenced by the C\/C++ source syntax\r\nhighlighting, and therefore it is deliberate that the Comment\r\nis somewhat darker and Macro is even more darker, and so on...\r\n\r\nSee link below for latest version:\r\n\r\n    https:\/\/github.com\/Radialsum\/config\/tree\/master\/vim\/colors\r\n","4":"The rested.vim is based on desert.vim by Hans Fugal.\r\n\r\nIt is a dark color scheme, and more or less resembles standard\r\ndark color schemes provided with Vim.\r\n\r\nSee the link below for a screenshot with common elements taken\r\nfrom :help syntax.\r\n\r\n    https:\/\/github.com\/Radialsum\/config\/blob\/master\/rested.png\r\n\r\nIt was triggered by the quest to find perceptually equidistant\r\ncolors or perceptually-distinct colors. However, the currently\r\nused colors do not necessarily fit either criteria though!\r\n\r\nThe colors are mostly influenced by the C\/C++ source syntax\r\nhighlighting, and therefore it is deliberate that the Comment\r\nis somewhat darker and Macro is even more darker, and so on...\r\n\r\nSee link below for latest version:\r\n\r\n    https:\/\/github.com\/Radialsum\/config\/tree\/master\/vim\/colors\r\n","install_details":"copy the rested.vim to your ~\/.vim\/colors\/ on Unixes or\r\nto $HOME\\vimfiles\\colors on Windows.","5":"copy the rested.vim to your ~\/.vim\/colors\/ on Unixes or\r\nto $HOME\\vimfiles\\colors on Windows.","first_name":"skycolor","6":"skycolor","last_name":"radialsum","7":"radialsum","releases":[{"0":"5672","vim_version":"8.0","1":"8.0","script_version":"0.1.0","2":"0.1.0","version_comment":"Initial upload","3":"Initial upload","package":"rested.vim","4":"rested.vim","src_id":"25894","5":"25894","creation_date":"1521652139","6":"1521652139"}]},"5671":{"script_id":"5671","0":"5671","script_name":"vinegar.vim","1":"vinegar.vim","script_type":"utility","2":"utility","summary":"Combine with netrw to create a delicious salad dressing","3":"Combine with netrw to create a delicious salad dressing","description":"https:\/\/tpope.io\/vim\/vinegar.git","4":"https:\/\/tpope.io\/vim\/vinegar.git","install_details":"Extract in ~\/.vim (~\\vimfiles on Windows).","5":"Extract in ~\/.vim (~\\vimfiles on Windows).","first_name":"Tim","6":"Tim","last_name":"Pope","7":"Pope","releases":[{"0":"5671","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"vinegar.zip","4":"vinegar.zip","src_id":"25886","5":"25886","creation_date":"1521231987","6":"1521231987"}]},"5670":{"script_id":"5670","0":"5670","script_name":"simplebuffer","1":"simplebuffer","script_type":"utility","2":"utility","summary":"a very simple buffer manager.","3":"a very simple buffer manager.","description":"It is a very simple buffer manager for switching and deleting buffers. \r\n","4":"It is a very simple buffer manager for switching and deleting buffers. \r\n","install_details":"Just decompressing the simplebuffer.tar and put simplebuffer.vim directory in your .vim directory, such as run the command \"mv simplebuffer.vim ~\/.vim\" on your terminal. And update the runtimepath with .vim\/simplebuffer.vim path.\r\nFor example, in your vimrc: set rtp+=~\/.vim\/simplebuffer.vim\r\n\r\nFor installing and managing your vim plugins easily, i recommand you to use vim-plug, which is a minimalist Vim Plugin Manager.\r\nIf you use Plug to install , just add \"Plug  'codcodog\/simplebuffer.vim'\" , and run ':PlugInstall'.\r\n\r\nFor more information you can see https:\/\/github.com\/codcodog\/simplebuffer.vim.","5":"Just decompressing the simplebuffer.tar and put simplebuffer.vim directory in your .vim directory, such as run the command \"mv simplebuffer.vim ~\/.vim\" on your terminal. And update the runtimepath with .vim\/simplebuffer.vim path.\r\nFor example, in your vimrc: set rtp+=~\/.vim\/simplebuffer.vim\r\n\r\nFor installing and managing your vim plugins easily, i recommand you to use vim-plug, which is a minimalist Vim Plugin Manager.\r\nIf you use Plug to install , just add \"Plug  'codcodog\/simplebuffer.vim'\" , and run ':PlugInstall'.\r\n\r\nFor more information you can see https:\/\/github.com\/codcodog\/simplebuffer.vim.","first_name":"Cryven","6":"Cryven","last_name":"mo","7":"mo","releases":[{"0":"5670","vim_version":"7.0","1":"7.0","script_version":"1.0.0","2":"1.0.0","version_comment":"Initial upload","3":"Initial upload","package":"simplebuffer.tar","4":"simplebuffer.tar","src_id":"25883","5":"25883","creation_date":"1521174276","6":"1521174276"}]},"5669":{"script_id":"5669","0":"5669","script_name":"nimble-anyjump.vim","1":"nimble-anyjump.vim","script_type":"utility","2":"utility","summary":"Initial upload.","3":"Initial upload.","description":"nimble-anyjump is a plugin that performs tag jump, file open, and URL open in the browser according to character strings on the cursor and character strings of the cursor line.\r\n\r\nHomepage: https:\/\/github.com\/ToruIwashita\/nimble-anyjump.vim","4":"nimble-anyjump is a plugin that performs tag jump, file open, and URL open in the browser according to character strings on the cursor and character strings of the cursor line.\r\n\r\nHomepage: https:\/\/github.com\/ToruIwashita\/nimble-anyjump.vim","install_details":"","5":"","first_name":"Toru","6":"Toru","last_name":"Hoyano","7":"Hoyano","releases":[{"0":"5669","vim_version":"8.0","1":"8.0","script_version":"1.4.0","2":"1.4.0","version_comment":"Fix URL parsing","3":"Fix URL parsing","package":"nimble-anyjump.vim-1.4.0.zip","4":"nimble-anyjump.vim-1.4.0.zip","src_id":"26713","5":"26713","creation_date":"1566907120","6":"1566907120"},{"0":"5669","vim_version":"8.0","1":"8.0","script_version":"1.3.0","2":"1.3.0","version_comment":"Fix URL parsing","3":"Fix URL parsing","package":"nimble-anyjump.vim-1.3.0.zip","4":"nimble-anyjump.vim-1.3.0.zip","src_id":"26712","5":"26712","creation_date":"1566906511","6":"1566906511"},{"0":"5669","vim_version":"8.0","1":"8.0","script_version":"1.2.0","2":"1.2.0","version_comment":"Improve url parsing","3":"Improve url parsing","package":"nimble-anyjump.vim-v.1.2.0.zip","4":"nimble-anyjump.vim-v.1.2.0.zip","src_id":"26359","5":"26359","creation_date":"1548416545","6":"1548416545"},{"0":"5669","vim_version":"8.0","1":"8.0","script_version":"1.1.0","2":"1.1.0","version_comment":"Improvement of filename jump and correspondence to '--extra=+f' option of ctags.","3":"Improvement of filename jump and correspondence to '--extra=+f' option of ctags.","package":"nimble-anyjump.vim-1.1.0.zip","4":"nimble-anyjump.vim-1.1.0.zip","src_id":"25957","5":"25957","creation_date":"1525173875","6":"1525173875"},{"0":"5669","vim_version":"8.0","1":"8.0","script_version":"1.0.0","2":"1.0.0","version_comment":"Initial upload","3":"Initial upload","package":"nimble-anyjump.vim-1.0.0.zip","4":"nimble-anyjump.vim-1.0.0.zip","src_id":"25879","5":"25879","creation_date":"1520922408","6":"1520922408"}]},"5668":{"script_id":"5668","0":"5668","script_name":"open-browser-github.vim","1":"open-browser-github.vim","script_type":"utility","2":"utility","summary":"Open GitHub URL of file, issue, pull request (GitHub Enterprise supported)","3":"Open GitHub URL of file, issue, pull request (GitHub Enterprise supported)","description":"Requirements\r\n\r\n  This plugin requires:\r\n  * open-browser.vim\r\n  * git command in your PATH\r\n\r\nUsage\r\n\r\n  There are 4 commands.\r\n\r\n  :OpenGithubFile\r\n    Opens a specific file in github.com repository(it also opens in the current branch by default).\r\n\r\n    \" Opens current files URL in github.com\r\n    :OpenGithubFile\r\n    \" Opens current files highlighted place in github.com \r\n    :'<,'>OpenGithubFile\r\n    \" Opens a specific file in github.com\r\n    :OpenGithubFile PATH\/TO\/FILE\r\n\r\n  :OpenGithubIssue\r\n    Opens a specific Issue.\r\n\r\n    \" Opens current repositories Issue #1\r\n    :OpenGithubIssue 1\r\n    \" Opens a specific repositories Issue #1\r\n    :OpenGithubIssue 1 tyru\/open-browser.vim\r\n    \" Opens current repositories Issue List\r\n    :OpenGithubIssue\r\n    \" Opens a specific repositories Issue list\r\n    :OpenGithubIssue tyru\/open-browser.vim\r\n\r\n  :OpenGithubPullReq\r\n    This command opens \/pulls page when it has no argument. Otherwise, it does entirely the same thing as :OpenGithubIssue since GitHub redirects \/issues\/1 to \/pull\/1 if #1 is a Pull Request.\r\n\r\n  :OpenGithubProject\r\n    Opens a project page.\r\n\r\n    \" Opens current opening file's repository.\r\n    \" ex) https:\/\/{hostname}\/{user}\/{name}\r\n    :OpenGithubProject\r\n\r\n    \" Opens current opening file's repository.\r\n    \" ex) https:\/\/{hostname}\/tyru\/open-browser.vim\r\n    :OpenGithubProject tyru\/open-browser.vim\r\n\r\nGitHub Enterprise setting\r\n\r\n  If you have hub command in your PATH, openbrowser-github executes the following command:\r\n\r\n    hub browse -u -- {path}\r\n\r\n  And it will open the returned (output) URL.\r\n\r\n  If you don't have hub command in your PATH, openbrowser-github tries to get each part of URL from the following gitconfig key:\r\n\r\n    * hub.host\r\n\r\n  You can specify GitHub Enterprise repository URL by setting above keys in gitconfig.\r\n\r\n  For example, you can set hub.host by executing the following command in your git repository which you want to specify GitHub Enterprise repository URL.\r\n\r\n    git config --local hub.host my.git.org\r\n\r\nLatest source\r\n  https:\/\/github.com\/tyru\/open-browser-github.vim\r\n","4":"Requirements\r\n\r\n  This plugin requires:\r\n  * open-browser.vim\r\n  * git command in your PATH\r\n\r\nUsage\r\n\r\n  There are 4 commands.\r\n\r\n  :OpenGithubFile\r\n    Opens a specific file in github.com repository(it also opens in the current branch by default).\r\n\r\n    \" Opens current files URL in github.com\r\n    :OpenGithubFile\r\n    \" Opens current files highlighted place in github.com \r\n    :'<,'>OpenGithubFile\r\n    \" Opens a specific file in github.com\r\n    :OpenGithubFile PATH\/TO\/FILE\r\n\r\n  :OpenGithubIssue\r\n    Opens a specific Issue.\r\n\r\n    \" Opens current repositories Issue #1\r\n    :OpenGithubIssue 1\r\n    \" Opens a specific repositories Issue #1\r\n    :OpenGithubIssue 1 tyru\/open-browser.vim\r\n    \" Opens current repositories Issue List\r\n    :OpenGithubIssue\r\n    \" Opens a specific repositories Issue list\r\n    :OpenGithubIssue tyru\/open-browser.vim\r\n\r\n  :OpenGithubPullReq\r\n    This command opens \/pulls page when it has no argument. Otherwise, it does entirely the same thing as :OpenGithubIssue since GitHub redirects \/issues\/1 to \/pull\/1 if #1 is a Pull Request.\r\n\r\n  :OpenGithubProject\r\n    Opens a project page.\r\n\r\n    \" Opens current opening file's repository.\r\n    \" ex) https:\/\/{hostname}\/{user}\/{name}\r\n    :OpenGithubProject\r\n\r\n    \" Opens current opening file's repository.\r\n    \" ex) https:\/\/{hostname}\/tyru\/open-browser.vim\r\n    :OpenGithubProject tyru\/open-browser.vim\r\n\r\nGitHub Enterprise setting\r\n\r\n  If you have hub command in your PATH, openbrowser-github executes the following command:\r\n\r\n    hub browse -u -- {path}\r\n\r\n  And it will open the returned (output) URL.\r\n\r\n  If you don't have hub command in your PATH, openbrowser-github tries to get each part of URL from the following gitconfig key:\r\n\r\n    * hub.host\r\n\r\n  You can specify GitHub Enterprise repository URL by setting above keys in gitconfig.\r\n\r\n  For example, you can set hub.host by executing the following command in your git repository which you want to specify GitHub Enterprise repository URL.\r\n\r\n    git config --local hub.host my.git.org\r\n\r\nLatest source\r\n  https:\/\/github.com\/tyru\/open-browser-github.vim\r\n","install_details":"...","5":"...","first_name":"tyru","6":"tyru","last_name":" ","7":" ","releases":[{"0":"5668","vim_version":"7.4","1":"7.4","script_version":"v1.0.1","2":"v1.0.1","version_comment":"[Fix] Fix undefined variable when openbrowser's global variable is not defined at startup (#27)","3":"[Fix] Fix undefined variable when openbrowser's global variable is not defined at startup (#27)","package":"open-browser-github-v1.0.1.zip","4":"open-browser-github-v1.0.1.zip","src_id":"25899","5":"25899","creation_date":"1521889669","6":"1521889669"},{"0":"5668","vim_version":"7.4","1":"7.4","script_version":"v1.0.0","2":"v1.0.0","version_comment":"Initial upload","3":"Initial upload","package":"open-browser-github-v1.0.0.zip","4":"open-browser-github-v1.0.0.zip","src_id":"25875","5":"25875","creation_date":"1520773282","6":"1520773282"}]},"5667":{"script_id":"5667","0":"5667","script_name":"open-browser-unicode.vim","1":"open-browser-unicode.vim","script_type":"utility","2":"utility","summary":"Open fileformat.info page about character on current cursor \/ given character","3":"Open fileformat.info page about character on current cursor \/ given character","description":"Opens Unicode character information from Vim on https:\/\/www.fileformat.info\/ website.\r\n\r\nNOTE: You must install open-browser.vim to use this plugin.\r\nhttps:\/\/github.com\/tyru\/open-browser.vim\r\n\r\n1. :OpenBrowserUnicode\r\n2. :OpenBrowserUnicode U+{hex}\r\n3. :OpenBrowserUnicode {char}\r\n\r\n\tOpens a unicode character information of given character if specified, or\r\n\tcurrent cursor character if not specified.\r\n\r\n\tOn 1st form, this command opens a page of the character under current\r\n\tcursor.\r\n\r\n\t\\\" Opens the page of the character under current cursor\r\n\t:OpenBrowserUnicode\r\n\r\n\tIf arguments were given, and it is prefixed with \\\"U+\\\" and subsequent\r\n\tcharacters are all of hex-characters (|\/\\\\x|), 2nd form is applied. Then\r\n\tthis command opens a page of the hex-encoded character.\r\n\r\n\t\\\" Opens http:\/\/www.fileformat.info\/info\/unicode\/char\/21ba\/\r\n\t:OpenBrowserUnicode U+21ba\r\n\r\n\tIf arguments were given and 2nd form is NOT applied, the 3rd form is\r\n\tapplied. Then this command opens a page of the character. If {char} is\r\n\ta string of 2 more than characters, the first character is used.\r\n\r\n\t\\\" Opens http:\/\/www.fileformat.info\/info\/unicode\/char\/21ba\/\r\n\t:OpenBrowserUnicode ↺\r\n\r\nLatest source\r\n  https:\/\/github.com\/tyru\/open-browser-unicode.vim","4":"Opens Unicode character information from Vim on https:\/\/www.fileformat.info\/ website.\r\n\r\nNOTE: You must install open-browser.vim to use this plugin.\r\nhttps:\/\/github.com\/tyru\/open-browser.vim\r\n\r\n1. :OpenBrowserUnicode\r\n2. :OpenBrowserUnicode U+{hex}\r\n3. :OpenBrowserUnicode {char}\r\n\r\n\tOpens a unicode character information of given character if specified, or\r\n\tcurrent cursor character if not specified.\r\n\r\n\tOn 1st form, this command opens a page of the character under current\r\n\tcursor.\r\n\r\n\t\\\" Opens the page of the character under current cursor\r\n\t:OpenBrowserUnicode\r\n\r\n\tIf arguments were given, and it is prefixed with \\\"U+\\\" and subsequent\r\n\tcharacters are all of hex-characters (|\/\\\\x|), 2nd form is applied. Then\r\n\tthis command opens a page of the hex-encoded character.\r\n\r\n\t\\\" Opens http:\/\/www.fileformat.info\/info\/unicode\/char\/21ba\/\r\n\t:OpenBrowserUnicode U+21ba\r\n\r\n\tIf arguments were given and 2nd form is NOT applied, the 3rd form is\r\n\tapplied. Then this command opens a page of the character. If {char} is\r\n\ta string of 2 more than characters, the first character is used.\r\n\r\n\t\\\" Opens http:\/\/www.fileformat.info\/info\/unicode\/char\/21ba\/\r\n\t:OpenBrowserUnicode ↺\r\n\r\nLatest source\r\n  https:\/\/github.com\/tyru\/open-browser-unicode.vim","install_details":"...","5":"...","first_name":"tyru","6":"tyru","last_name":" ","7":" ","releases":[{"0":"5667","vim_version":"7.4","1":"7.4","script_version":"v1.0.0","2":"v1.0.0","version_comment":"Initial upload","3":"Initial upload","package":"open-browser-unicode-v1.0.0.zip","4":"open-browser-unicode-v1.0.0.zip","src_id":"25874","5":"25874","creation_date":"1520772589","6":"1520772589"}]},"5665":{"script_id":"5665","0":"5665","script_name":"dadbod.vim","1":"dadbod.vim","script_type":"utility","2":"utility","summary":"Modern database interface for Vim","3":"Modern database interface for Vim","description":"Dadbod is a Vim plugin for interacting with databases.  It's a more modern take on dbext.vim (vimscript #356), improving on it on the following ways:\r\n\r\n* Connections are specified with a single URL, rather than prompting you for 14 separate variables\r\n* All interaction is through invoking :DB, not 53 different commands and 35 different maps (omitting many of the more esoteric features, of course)\r\n* Supports a modern array of backends, including NoSQL databases:\r\n  - MongoDB\r\n  - MySQL\r\n  - PostgreSQL\r\n  - Redis\r\n  - Sqlite\r\n  - Your own easily implemented adapter\r\n* Easily configurable based on a project directory (as seen in rails.vim (vimscript #1567), for example), rather than just globally or in a per-file modeline\r\n\r\n## Usage\r\n\r\nThe :DB command has a few different usages.  All forms accept a URL as the first parameter, which can be omitted if a default is configured or provided by a plugin.\r\n\r\nOmit further arguments to spawn an interactive console (like `psql` or `redis-cli`).\r\n\r\n   :DB postgresql:\/\/\/foobar\r\n   :DB redis:\r\n\r\nIf additional arguments are provided, they are interpreted as a query string to pass to the database.  Results are displayed in a preview window.\r\n\r\n    :DB sqlite:myfile.sqlite3 select count(*) from widgets\r\n    :DB redis:\/\/\/ CLIENT LIST\r\n\r\nGive a range to run part or all of the current buffer as a query.\r\n\r\n    :%DB mysql:\/\/root@localhost\/bazquux\r\n\r\nUse `<` to pass in a filename.\r\n\r\n    :DB mongo:\/\/\/test < big_query.js\r\n\r\nThere's also a special assignment syntax for saving a URL to a Vim variable for later use.\r\n\r\n    :DB g:prod = postgres:\/\/user:pass@db.example.com\/production_database\r\n    :DB g:prod drop table users\r\n\r\nA few additonal URL like formats are accepted for interop:\r\n\r\n* `:DB jdbc:postgresql:\/\/...`\r\n* `:DB dbext:profile_name`\r\n* `:DB dbext:type=PGSQL:host=...`\r\n* `:DB $DATABASE_URL` (with optional dotenv.vim (vimscript #5176) support)\r\n\r\nPlugins can provide their own URL handlers as well.  For example, heroku.vim (vimscript #4915) provides support for `heroku:appname` style URLs.","4":"Dadbod is a Vim plugin for interacting with databases.  It's a more modern take on dbext.vim (vimscript #356), improving on it on the following ways:\r\n\r\n* Connections are specified with a single URL, rather than prompting you for 14 separate variables\r\n* All interaction is through invoking :DB, not 53 different commands and 35 different maps (omitting many of the more esoteric features, of course)\r\n* Supports a modern array of backends, including NoSQL databases:\r\n  - MongoDB\r\n  - MySQL\r\n  - PostgreSQL\r\n  - Redis\r\n  - Sqlite\r\n  - Your own easily implemented adapter\r\n* Easily configurable based on a project directory (as seen in rails.vim (vimscript #1567), for example), rather than just globally or in a per-file modeline\r\n\r\n## Usage\r\n\r\nThe :DB command has a few different usages.  All forms accept a URL as the first parameter, which can be omitted if a default is configured or provided by a plugin.\r\n\r\nOmit further arguments to spawn an interactive console (like `psql` or `redis-cli`).\r\n\r\n   :DB postgresql:\/\/\/foobar\r\n   :DB redis:\r\n\r\nIf additional arguments are provided, they are interpreted as a query string to pass to the database.  Results are displayed in a preview window.\r\n\r\n    :DB sqlite:myfile.sqlite3 select count(*) from widgets\r\n    :DB redis:\/\/\/ CLIENT LIST\r\n\r\nGive a range to run part or all of the current buffer as a query.\r\n\r\n    :%DB mysql:\/\/root@localhost\/bazquux\r\n\r\nUse `<` to pass in a filename.\r\n\r\n    :DB mongo:\/\/\/test < big_query.js\r\n\r\nThere's also a special assignment syntax for saving a URL to a Vim variable for later use.\r\n\r\n    :DB g:prod = postgres:\/\/user:pass@db.example.com\/production_database\r\n    :DB g:prod drop table users\r\n\r\nA few additonal URL like formats are accepted for interop:\r\n\r\n* `:DB jdbc:postgresql:\/\/...`\r\n* `:DB dbext:profile_name`\r\n* `:DB dbext:type=PGSQL:host=...`\r\n* `:DB $DATABASE_URL` (with optional dotenv.vim (vimscript #5176) support)\r\n\r\nPlugins can provide their own URL handlers as well.  For example, heroku.vim (vimscript #4915) provides support for `heroku:appname` style URLs.","install_details":"Extract in ~\/.vim (~\\vimfiles on Windows). Or use https:\/\/tpope.io\/vim\/dadbod.git with your favorite package manager.","5":"Extract in ~\/.vim (~\\vimfiles on Windows). Or use https:\/\/tpope.io\/vim\/dadbod.git with your favorite package manager.","first_name":"Tim","6":"Tim","last_name":"Pope","7":"Pope","releases":[{"0":"5665","vim_version":"7.0","1":"7.0","script_version":"1.4","2":"1.4","version_comment":"Fix issue passing password to redis-cli.\r\nFix error calling bufnr() on older Vim.","3":"Fix issue passing password to redis-cli.\r\nFix error calling bufnr() on older Vim.","package":"dadbod.zip","4":"dadbod.zip","src_id":"27713","5":"27713","creation_date":"1629731840","6":"1629731840"},{"0":"5665","vim_version":"7.0","1":"7.0","script_version":"1.3","2":"1.3","version_comment":"Add ClickHouse adapter.\r\nAdd impala adapter.\r\nAdd jq adapter.\r\nAdd osquery adapter.\r\nAdd Presto adapter.\r\nSupport arbitrary MongoDB parameters, including authSource= and ssl=.\r\nSupport protocol=, login-path=, and ssl-*= for MySQL.\r\nSupport encrypt= and trustServerCertificate= for SQL server.\r\nSupport tab completion for SQL server.\r\nSupport command modifiers like :tab.\r\nSupport prefix to query for range selection (e.g., :%DB EXPLAIN).\r\nProvide gq map to close results window.\r\nBug fixes.","3":"Add ClickHouse adapter.\r\nAdd impala adapter.\r\nAdd jq adapter.\r\nAdd osquery adapter.\r\nAdd Presto adapter.\r\nSupport arbitrary MongoDB parameters, including authSource= and ssl=.\r\nSupport protocol=, login-path=, and ssl-*= for MySQL.\r\nSupport encrypt= and trustServerCertificate= for SQL server.\r\nSupport tab completion for SQL server.\r\nSupport command modifiers like :tab.\r\nSupport prefix to query for range selection (e.g., :%DB EXPLAIN).\r\nProvide gq map to close results window.\r\nBug fixes.","package":"dadbod.zip","4":"dadbod.zip","src_id":"27601","5":"27601","creation_date":"1621004459","6":"1621004459"},{"0":"5665","vim_version":"7.0","1":"7.0","script_version":"1.2","2":"1.2","version_comment":"Support SQL Server.\r\nSupport Oracle.\r\nProvide automatic management of dbext configuration.\r\nFix tab completion issues.\r\nMinor bug fixes.","3":"Support SQL Server.\r\nSupport Oracle.\r\nProvide automatic management of dbext configuration.\r\nFix tab completion issues.\r\nMinor bug fixes.","package":"dadbod.zip","4":"dadbod.zip","src_id":"25944","5":"25944","creation_date":"1524629547","6":"1524629547"},{"0":"5665","vim_version":"7.0","1":"7.0","script_version":"1.1","2":"1.1","version_comment":"Rename to Dadbod.\r\nFix issue with screen failing to redraw.\r\nFix various issues with shell execution.\r\nRearrange psql arguments to avoid warning.\r\nSupport SSL for MongoDB.\r\nSupport custom port in dbext wrapper.","3":"Rename to Dadbod.\r\nFix issue with screen failing to redraw.\r\nFix various issues with shell execution.\r\nRearrange psql arguments to avoid warning.\r\nSupport SSL for MongoDB.\r\nSupport custom port in dbext wrapper.","package":"dadbod.zip","4":"dadbod.zip","src_id":"25888","5":"25888","creation_date":"1521255432","6":"1521255432"},{"0":"5665","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"db.zip","4":"db.zip","src_id":"25870","5":"25870","creation_date":"1520486911","6":"1520486911"}]},"5664":{"script_id":"5664","0":"5664","script_name":"copy paste finder","1":"copy paste finder","script_type":"utility","2":"utility","summary":"utility for viewing copied-pasted code side-by-side","3":"utility for viewing copied-pasted code side-by-side","description":"Copy\/Paste Finder (CPF) makes PMD\/CPD's or Sloppy's output easier to navigate.\r\nCPF shows detected copied\/pasted regions in vertical splits and highlights\r\nthe found regions.\r\n\r\nHomepage for development:\r\n    https:\/\/github.com\/Radialsum\/copy-paste-finder\r\n\r\nScreenshot:\r\n    https:\/\/github.com\/Radialsum\/copy-paste-finder\/blob\/master\/cpf-v002.png\r\n\r\n\r\nCPF depends on PMD or Sloppy software and needs Vim's quickfix feature.\r\n\r\nPMD\/CPD:\r\nPMD's Copy\/Paste Detector (CPD) finds duplicated code.\r\nPMD is an extensible cross-language static code analyzer.\r\nPMD is an open source project.\r\n\r\nsee https:\/\/pmd.github.io\/ to download it and for more info.\r\n\r\nSloppy:\r\nSloppy scans all source code in a directory and generates a report on how\r\n'sloppy' the code is... sloppiness being a measurement of a repetitive code\r\nstyle: under abstraction (copy \/ pasting) and over abstraction (pointless\r\ncomplexity).\r\n\r\nSloppy is written by Wouter van Oortmerssen.\r\n\r\nsee http:\/\/strlen.com\/sloppy\/ to download it and for more info.\r\n\r\nTested with Vim version 8.0 on Microsoft Windows; it may work with older vim,\r\nbut not fully verified.\r\n\r\nsee the doc\/cpf.txt for usage and installation instructions.\r\n\r\n\r\nUsage:\r\n\r\nSteps below targets Microsoft Windows. Similar steps can be used with\r\nLinux or Unix* operating systems.\r\n\r\n  - ensure java environment or sloppy executable in path\r\n  - Run gvim to open a new gvim window\r\n  - Ensure current working directory is correct in gvim\r\n  - During an editing session:\r\n      :compiler pmdcpd\r\n      :set makeprg=cpd.bat\\ --minimum-tokens\\ 20\\ --language\\ cpp\\ --files\\ .\r\n      :make!\r\n      :CpfNext\r\n\r\nOr\r\n      :compiler sloppy\r\n      :makeprg=sloppy.bat\r\n      :make!\r\n      :CpfNext\r\n\r\ncan be used with sloppy.\r\n\r\nThe command CpfNext can be repeated to see more duplicates\r\n\r\nWith Vim 8.0, if  ':make!'  is called then script automatically reloads the\r\nquickfix list.\r\n\r\nWith Vim 7.4, automatic reloading of quickfix list is not possible after\r\n':make!'  is called. The workaround is to call the command below to reload:\r\n\r\n      :call Cpf_LoadQflist()\r\n\r\n\r\nLimitations:\r\n\r\n  - can only see two windows with a (vertical) split at a time\r\n  - work along with other plugins (e.g. taglist, nerdtree...)\r\n  - support more windows; now only 2 (see wincount)\r\n  - support showing previous duplicate (opposite of Cpf_Next())\r\n  - silent, normal or execute may be redundant in some cases\r\n  - need to skip lines with no code or lines with comment only\r\n  - deciding whether to save buffers before jumping to next section\r\n  - if quickfix windows is visible may need to scroll\/redraw\r\n  - may need to check and add ':noautocmd' to wincmd\r\n","4":"Copy\/Paste Finder (CPF) makes PMD\/CPD's or Sloppy's output easier to navigate.\r\nCPF shows detected copied\/pasted regions in vertical splits and highlights\r\nthe found regions.\r\n\r\nHomepage for development:\r\n    https:\/\/github.com\/Radialsum\/copy-paste-finder\r\n\r\nScreenshot:\r\n    https:\/\/github.com\/Radialsum\/copy-paste-finder\/blob\/master\/cpf-v002.png\r\n\r\n\r\nCPF depends on PMD or Sloppy software and needs Vim's quickfix feature.\r\n\r\nPMD\/CPD:\r\nPMD's Copy\/Paste Detector (CPD) finds duplicated code.\r\nPMD is an extensible cross-language static code analyzer.\r\nPMD is an open source project.\r\n\r\nsee https:\/\/pmd.github.io\/ to download it and for more info.\r\n\r\nSloppy:\r\nSloppy scans all source code in a directory and generates a report on how\r\n'sloppy' the code is... sloppiness being a measurement of a repetitive code\r\nstyle: under abstraction (copy \/ pasting) and over abstraction (pointless\r\ncomplexity).\r\n\r\nSloppy is written by Wouter van Oortmerssen.\r\n\r\nsee http:\/\/strlen.com\/sloppy\/ to download it and for more info.\r\n\r\nTested with Vim version 8.0 on Microsoft Windows; it may work with older vim,\r\nbut not fully verified.\r\n\r\nsee the doc\/cpf.txt for usage and installation instructions.\r\n\r\n\r\nUsage:\r\n\r\nSteps below targets Microsoft Windows. Similar steps can be used with\r\nLinux or Unix* operating systems.\r\n\r\n  - ensure java environment or sloppy executable in path\r\n  - Run gvim to open a new gvim window\r\n  - Ensure current working directory is correct in gvim\r\n  - During an editing session:\r\n      :compiler pmdcpd\r\n      :set makeprg=cpd.bat\\ --minimum-tokens\\ 20\\ --language\\ cpp\\ --files\\ .\r\n      :make!\r\n      :CpfNext\r\n\r\nOr\r\n      :compiler sloppy\r\n      :makeprg=sloppy.bat\r\n      :make!\r\n      :CpfNext\r\n\r\ncan be used with sloppy.\r\n\r\nThe command CpfNext can be repeated to see more duplicates\r\n\r\nWith Vim 8.0, if  ':make!'  is called then script automatically reloads the\r\nquickfix list.\r\n\r\nWith Vim 7.4, automatic reloading of quickfix list is not possible after\r\n':make!'  is called. The workaround is to call the command below to reload:\r\n\r\n      :call Cpf_LoadQflist()\r\n\r\n\r\nLimitations:\r\n\r\n  - can only see two windows with a (vertical) split at a time\r\n  - work along with other plugins (e.g. taglist, nerdtree...)\r\n  - support more windows; now only 2 (see wincount)\r\n  - support showing previous duplicate (opposite of Cpf_Next())\r\n  - silent, normal or execute may be redundant in some cases\r\n  - need to skip lines with no code or lines with comment only\r\n  - deciding whether to save buffers before jumping to next section\r\n  - if quickfix windows is visible may need to scroll\/redraw\r\n  - may need to check and add ':noautocmd' to wincmd\r\n","install_details":"  * copy pmdcpd.vim to the compiler directory\r\n  * copy sloppy.vim to the compiler directory\r\n  * copy cpf.vim to plugin directory\r\n      i.e. inside $HOME\/vimfiles (or runtime directory):\r\n        compiler\/pmdcpd.vim\r\n        compiler\/sloppy.vim\r\n        plugin\/cpf.vim\r\n  * ensure java environment or sloppy executable in path\r\n  * ensure cpd (e.g. cpd.bat) is found in the path\r\n  * ensure cpd or sloppy runs correctly\r\n\r\nThe Sloppy release has sloppy.exe which runs on windows.\r\nHowever for the original sloppy, a batch file is required.\r\nFor example: sloppy.bat\r\n     @echo off\r\n     echo. | sloppy %*\r\nAbove batch file helps sloppy to exit---otherwise it waits for\r\nenter key to be pressed.\r\n","5":"  * copy pmdcpd.vim to the compiler directory\r\n  * copy sloppy.vim to the compiler directory\r\n  * copy cpf.vim to plugin directory\r\n      i.e. inside $HOME\/vimfiles (or runtime directory):\r\n        compiler\/pmdcpd.vim\r\n        compiler\/sloppy.vim\r\n        plugin\/cpf.vim\r\n  * ensure java environment or sloppy executable in path\r\n  * ensure cpd (e.g. cpd.bat) is found in the path\r\n  * ensure cpd or sloppy runs correctly\r\n\r\nThe Sloppy release has sloppy.exe which runs on windows.\r\nHowever for the original sloppy, a batch file is required.\r\nFor example: sloppy.bat\r\n     @echo off\r\n     echo. | sloppy %*\r\nAbove batch file helps sloppy to exit---otherwise it waits for\r\nenter key to be pressed.\r\n","first_name":"skycolor","6":"skycolor","last_name":"radialsum","7":"radialsum","releases":[{"0":"5664","vim_version":"8.0","1":"8.0","script_version":"0.0.2","2":"0.0.2","version_comment":"getqflist() vs Vim version patches\r\npartial support for Vim 7.4","3":"getqflist() vs Vim version patches\r\npartial support for Vim 7.4","package":"cpf-v002.zip","4":"cpf-v002.zip","src_id":"25882","5":"25882","creation_date":"1521048328","6":"1521048328"},{"0":"5664","vim_version":"8.0","1":"8.0","script_version":"0.0.1","2":"0.0.1","version_comment":"Initial upload","3":"Initial upload","package":"cpf-v001.zip","4":"cpf-v001.zip","src_id":"25861","5":"25861","creation_date":"1520261222","6":"1520261222"}]},"5663":{"script_id":"5663","0":"5663","script_name":"aa","1":"aa","script_type":"utility","2":"utility","summary":"A plugin for managing time and note taking","3":"A plugin for managing time and note taking","description":"(the formatting is broken because this is a Vim help file.\r\nMight be ok if you use a mono font.\r\nInstall this plugin to have a nicely formated documentation)\r\n\r\n*aa.txt*        A plugin for managing time and note taking        version 0.01b\r\n                     __                    __     \r\n                    \/\\  \\                   \/\\  \\    \r\n                   \/::\\  \\                 \/::\\  \\   \r\n                  \/:\/\\:\\  \\               \/:\/\\:\\  \\  \r\n                 \/::\\~\\:\\  \\            \/::\\~\\:\\  \\ \r\n                \/:\/\\:\\ \\:\\__\\         \/:\/\\:\\ \\:\\__\\\r\n                \\\/__\\:\\\/:\/  \/         \\\/_\\:\\\/:\/  \/\r\n                     \\::\/  \/                 \\::\/  \/ \r\n                     \/:\/  \/                  \/:\/  \/  \r\n                    \/:\/  \/                  \/:\/  \/   \r\n                    \\\/_\/ lgorithmic  \\\/_\/ utoregulation\r\n\r\n==============================================================================\r\nCONTENTS                                                            *aa-index*\r\n                           *aa*\r\n\r\n    1. Intro                                    |aa-intro|\r\n        1.1. AA (Algorithmic Autoregulation)    |AA|\r\n             |aa-shout|  |aa-literature|  |aa-shout-usage|\r\n             |aa-session|  |aa-slot|  |aa-repr|  |aa-plugin|\r\n\r\n        1.2. Related plugins                    |aa-related-plugins|\r\n        1.3. Usage examples                     |aa-usage-examples|\r\n        1.4. |aa| help                            |aa-helphelp|\r\n             |aa-help-cheatsheet|, |aa-cheatsheet|\r\n\r\n    2. Install                                  |aa-install|\r\n             |aa-install-recommended|  |aa-install-Vimball|\r\n             |aa-install-root|  |aa-prv|\r\n\r\n    3. Options, variables and general settings  |aa-settings|\r\n                                                |aa-options|\r\n             |aa_g:aa|  |aa-leaders|  |aa_leader|  |aa_localleader| \r\n             |aa-session-cues|  |aa-color-columns|  |aa-speech| \r\n             |aa-hack-settings|\r\n\r\n    4. Mappings                                 |aa-mappings|\r\n             |aa-shout-mappings|  |aa-session-mappings| \r\n             |aa-hack-mappings|  |aa-general-mappings|\r\n\r\n    5. Commands                                 |aa-commands|\r\n             |aa-main-commands|  |aa-util-commands|\r\n\r\n    6. Functions                                |aa-functions|\r\n             |aa-implementation|\r\n\r\n    7. Files                                    |aa-files|\r\n             |aashouts.txt|  |aasessions.txt|  |aa.vim|\r\n             |aashouts.vim|  |aa-syntax|  |aaftdetect.vim| \r\n             |aastartup.vim| |aa-aa.txt|\r\n\r\n    8. Final words                              |aa-final-words|\r\n        8.1. Advantages and drawbacks of |aa|     |aa-compare|\r\n        8.2. Further work \/ Todo                |aa-todo|\r\n        8.3. |AA| Tradition                       |aa-tradition|\r\n             |aa-activism|\r\n\r\n        8.4. Disclaimer                         |aa-disclaimer|\r\n        8.5. License                            |aa-license|\r\n        8.6. Acknowledgements                   |aa-ack|\r\n        8.7. Contact                            |aa-contact|\r\n\r\n\r\n==============================================================================\r\n1. Intro                                                            *aa-intro*\r\n\r\nThis plugin enables the |AA| personal time-tracking and note-taking mechanism\r\ninside Vim.\r\n\r\n|AA| as been useful for personal and collective work-forces, in both\r\nprofessional and voluntary dedication, employing either formal and informal\r\nlogging of shouts, for scientific research and for software development (see\r\n|aa-literature|).  This plugin holds considerable advantages over the\r\npreceding implementations, although the sharing interface is not still\r\nimplemented and it is in a very early stage of development.  See |AA| and\r\n|aa-compare|\r\n\r\nIts use is very context dependent, and in many cases maximal exploitation is\r\nachieved by also using other advanced self-management facilities, such as\r\nVimwiki.  See |aa-related-plugins|\r\n\r\n------------------------------------------------------------------------------\r\n1.1. AA (Algorithmic Autoregulation)                                      *AA*\r\n                                                                    *aa-shout*\r\n\r\nThe main idea of AA is sending messages, which are notes about ongoing work\r\n(but not strictly) for managing personal or group dedication, sharing ongoing\r\nprocesses, automated documentation of efforts, self-transparency, and other\r\nresounding goals.  Such messages are herein called _shouts_.  This method (or\r\nstrategy) has proved itself valuable though time, specially in fine-tuning\r\nefforts and tackling complex tasks. [1][2][3][4]  One might also want to look\r\nat the Pomodoro Technique for time management.\r\n\r\n                                                               *aa-literature*\r\n[1]: Fabbri, R. (2017). The Algorithmic-Autoregulation (AA) Methodology and\r\nSoftware: a collective focus on self-transparency.\r\narXiv preprint https:\/\/arxiv.org\/abs\/1711.04612\r\n[2]: Fabbri, R., Fabbri, R., Vieira, V., Negrao, A., Zambianchi, L.,\r\nMendon\u00c3\u00a7a, M., ... & Shiga, D. (2013). AA: The Algorithmic Autoregulation\r\n(Distributed Software Development) Methodology.\r\narXiv preprint https:\/\/arxiv.org\/abs\/1604.08255\r\n[3]: https:\/\/github.com\/ttm\/aa01\r\n[4]: http:\/\/wiki.nosdigitais.teia.org.br\/Lab_Macambira\r\n\r\nThe use of shouts is by no means strict.  As |AA| is straight-forward meant\r\nfor the user to harness its mechanisms, one should continually adapt its use\r\nto fit personal needs and desires.  Propaganda shouts are considered useless,\r\na deviation from the purposes of AA, and are most often found in shouts from\r\nnew users.  Notes about ongoing tasks are preferred against those exhibiting\r\nfinished products, although a note on finishing something is often the most\r\nappropriate shout.  See |aa-usage-examples|\r\n\r\n                                                                  *aa-session*\r\nThese shouts might or not be grouped into sessions, which are sets of\r\nconsecutive (and usually also somewhat periodic) shouts.  Sessions are often\r\ndedicated to some ongoing project or task, might be the recipient of other\r\nmedia, such as a video screenscast or a final message, and metadata, such as\r\nrating by other |AA| users.\r\n\r\n                                                                     *aa-slot*\r\nMost traditionally, a session is comprised of 8 slots of 15 minutes.  One\r\nshould send a shout at the beginning of the session and after each slot is\r\nfinished.  Sometimes a tolerance of +- 5 minutes is used as a reference, but\r\nit is all up to the user, of course.  Slot duration ranges from about a minute\r\nto hours.\r\n\r\n                                                                     *aa-repr*\r\n|AA| shouts and sessions have traditionally been represented as texts, with\r\ne.g.  videos and blogs being uploaded in any third-party online platform, and\r\nthen the URLs used as convenient.\r\n\r\n                                                                   *aa-plugin*\r\n|aa| is a plugin for using |AA| inside Vim.  With |aa| you can:\r\n    - Write a shout at any time, with convenient mappings and commands.\r\n      See |aa-shout-mappings| and |aa-commands|\r\n    - Keep track of your shouts, edit and input them though automated routines\r\n      or editing |aashouts.txt| directly as a normal file in Vim.\r\n    - Make AA sessions, with visual and audio cues for: slots finished, shouts\r\n      expected, time inside a session of a slot or a session, etc.\r\n      See |aa-mappings|\r\n    - Have a clear understanding of AA state (shouts, sessions, paths,\r\n      initialization, variables) with convenient mappings.  See |aa-leader-i|\r\n    - Hack a very tweak-friendly interface of functions, commands and\r\n      mappings.  See |aa.vim|\r\n    - Share your shouts and sessions with other AA users through linked data\r\n      protocols (RDF, SparQL, OWL, etc).  Not Implemented, see |aa-todo|\r\n\r\n------------------------------------------------------------------------------\r\n1.2. Related plugins                                      *aa-related-plugins*\r\n\r\n|aa| is being developed as part of the PRV (Python, RDF and VIM) framework.\r\nOne might benefit from the other PRV plugins:\r\n    - |prv| is a set of utilities that I used in a disordered manner beforehand:\r\n      save and load sessions, mappings, functions, syntax highlighting, etc.\r\n    - |realcolors| is a set of utilities for tweaking and creating 24 bit 'true\r\n      color' color schemes for Vim.  The color schemes, default color sets,\r\n      ways to navigate the color space, and more are obtained through\r\n      techniques derived from psychophysics, data visualization, and simple\r\n      mathematics.\r\n    - |tokipona| is a set of utilities for the Toki Pona minimalist conlang:\r\n      syntax highlighting, vocabulary mining, text synthesis, and preliminary\r\n      Toki Pona wordnets.\r\n\r\nOther plugins are envisioned in PRV, partly mentioned in the documentation:\r\n    https:\/\/github.com\/ttm\/prv\r\n\r\nVimwiki has been very symbiotic with my |aa| usage.\r\nSee the |aa-bare-vim-wiki| intended.\r\n\r\nPlease suggest me other plugins.\r\n\r\n------------------------------------------------------------------------------\r\n1.3. Usage examples                                        *aa-usage-examples*\r\n\r\nAs |AA| is a very open methodology, there are countless ways to use AA.  The\r\ncore ideas are given in |aa-intro|. This section presents some procedures\r\nwhich might be followed while using |aa|.\r\n\r\nIn writing some documents (say scripts and latex files), one has many ideas\r\nabout possible enhancements and recognizes potential bugs.  These notes might\r\nbe taken without leaving the window by using |aa-leader-a|.  More elaborate\r\nnotes might be taken using |aa-leader-A| at any time, editing directly the\r\nshouts.txt (see |aashouts.txt|).  To access the notes, one might use\r\n|aa-leader-v|, |aa-leader-t| and |aa-leader-e|, as explained in |aa-mappings|\r\n\r\nA researcher and developer with many tasks relating to diverse subjects is\r\ntrying to better keep track of the ideas and issues that spark all the time,\r\nwhile having focus on the intended tasks for relevant periods of time.  He\r\nadopts the standard |AA| session of 2h: 8 slots of 15 minutes each.  Such\r\nsessions (and variations) are conveniently started wih |aa-leader-s|,\r\n|aa-leader-S|, and |aa-leader-localleader-S|, while |aa-leader-l|,\r\n|aa-leader-L|, and |aa-leader-O| assists sessions by providing the selected\r\ninfo of: time left in slot, time since slot started, session on.  Full context\r\nis exposed with |aa-leader-i|\r\n\r\nA newbie starts using |aa|.  First she starts to test the mappings and write\r\nshouts with notes about how to use |aa|.  Next, she writes new mappings, some\r\nbased on those notes, and starts hacking |aa| functions in order to achieve\r\ndesired functionalities.  Eager to use shouts with appropriate tagging\r\nmechanisms, she uses `:lv` to browse though tags created on the fly.  Finally,\r\nthe enhancements are sent for evaluation to the main |aa| repository as a pull\r\nrequest or a Git patch.\r\n\r\n------------------------------------------------------------------------------\r\n1.4. |aa| help                                                   *aa-helphelp*\r\n\r\nReload this help file (:e or :e %) to edit it, as specified in the final\r\nline of this aa.txt file (see :h modeline).\r\nRender the |aa| help tags e.g. with\r\n\r\n    `:helptags %`\r\n    (Press TAB and then remove the aa.txt at the end)\r\n\r\nPlease enhance this documentation within this or another file e.g. by copying\r\n.\/aa.txt to .\/anything.txt as a template.\r\n\r\n                                                          *aa-help-cheatsheet*\r\nStandard Highlighting and functions:\r\n    *Tag*\r\n    |hyperlink|\r\n    'option'\r\n    `:command` >\r\n    function SomeFunc()\r\n        echo \"Yes, I am verbatim\"\r\n    endf\r\n<    |AFunction()|\r\n    {braces} CTRL-X \r\n    Column heading~\r\n    Note Notes\r\n\r\nMore details in $VIMRUNTIME\/syntax\/help.vim, and in browsing other help files.\r\n\r\nThese require tabs (use `:se list!` to see them):\r\n\t*Todo\tsomething to do\r\n\t*Error\tsomething wrong\r\n        *Todo   make a syntax rule to always color the line when starting with\r\n                                    ^\\s{x,y}\\*\\U.\r\n                If possible, color the line according to a calculation leading\r\n                the * to RGB space.\r\n    \r\nMannerisms and default usability: \r\n    `:se ft=`      to see the chars being used in formatting the help file\r\n    `:se ft=help`  set syntax again (reload with `:e `usually works as well)\r\n    Copy aa.txt or any other help file as a template\r\n    You might follow any tag with .\r\n    You see every incidence of a tag in current file with\r\n                `:lv \/|tag< remove me>|\/ %`\r\n                (% might be replaced to any path according to {file})\r\n                Similarly:\r\n                `:lh |tag< remove me>|`\r\n                and then `:lop` to navigate the lines where they occur\r\n                (also, :vim and :helpg with :copen)\r\n    Type `:h aa-` and press  to see all the matches.\r\n    You reach a list of all |aa| tags with `:ts` \/aa or with `:h aa-index`\r\n    If you load aa.txt not using a help-related command, the tags available\r\n    will only be related to aa.vim, and browsing documentation with external\r\n    tags becomes broken.\r\n\r\nThe documentation does not leave much more information about conventions\r\non help files.  Check $VIMRUNTIME\/syntax\/help.vim for more details.\r\n\r\n\r\n                                                               *aa-cheatsheet*\r\nJust look into |aa-mappings| and |aa-options|.\r\n\r\n\r\n==============================================================================\r\n2. Install                                                        *aa-install*\r\n\r\nThere are various ways to install Vim plugins.  If you have not picked your\r\npreferred way, this section summarizes what I understand about the issue.\r\n\r\nIn Vim manual (e.g. see |usr_toc|), a Vim plugin is described as a single file,\r\nwhich is sourced at startup right after vimrc according to `:h` 'rtp'\r\n\r\n                                                       *aa-install-recomended*\r\nThe way I find most clean and simple is to copy the whole |aa| file tree to\r\nany pack\/*\/opt\/ directory in your 'runtimepath', such as .vim\/pack\/prv\/opt\/.\r\nThis might be done for any plugin, with care for eventual after\/ directories,\r\nas described in |prv-after|\r\n\r\nThen put:\r\n    `packadd aa`\r\nin your vimrc.\r\n\r\nThe correspondent pack\/*\/*\/opt\/aa directory is added to the base directories\r\n(stored in 'runtimepath') where Vim looks for standard directories and files.\r\nIf you have problems, close and open Vim again.\r\n\r\n                                                                      *aa-prv*\r\nThis plugin is being developed as part of the PRV framework.  |aa|, at the\r\nmoment, uses only the `:PRVBuf`  and `:PRVLeader` commands, which are copied\r\ninto aux\/prvdependence.vim and sourced when prv is not found loaded.\r\n\r\nIf you want to integrate |prv| and |aa|, the best and easiest way is just to\r\nclone |prv| into pack\/ttm\/prv\/ and add `:packadd prv` to vimrc before\r\n`:packadd aa` NOTE: you do not need to initialize |prv| (with `:PRVInit`),\r\nwhich will add all |prv| mappings to your session.  NOTE: you may change ttm\/\r\nto any directory.  This layers is only for organization of the packages.\r\n\r\n                                                          *aa-install-vimball*\r\nAlso, this same installation is performed with Vimball: >\r\n\r\n        vim aa.vmb \r\n        :so %\r\n        :q\r\n\r\n to create a path with the filename under the cursor,\r\n      as does Vimwiki\r\n    - maybe use  to decorate (link, tag-link, tag-reference,\r\n      (option,command,function)-(link or reference)\r\n    - exploit deeply the concept of a \"react-wiki\": hypertexts with executable\r\n      code.\r\n    - use a directory as wiki root, \r\n    - use a new or standard suffix (e.g. *.mwiki)?\r\n    - use gf to follow pages\r\n    - write token or word with starting \/ or . if internal link intended\r\n    - reuse Vim's capabilities with help files and (parallel help files?) with\r\n      tags and searching (and what more?).\r\n    - integrate with |aa| and the rest of PRV.  See |aa-related-plugins|\r\n    - manage to link paths of wiki pages and of repository trees.\r\n      E.g. .py files use a specific &path, .vim files, other &path etc...\r\n    - it might be condensed in just a couple of settings with optional\r\n      advanced functions\r\n    - it should be very friendly to making collage of files to render, e.g. a\r\n      latex or HTML file.\r\n\r\n------------------------------------------------------------------------------\r\n8.3. |AA| Tradition                                             *aa-tradition* \r\n                                             \r\n                                                                 *aa-activism*\r\n|AA| has often been envisioned and used for social transformation.\r\nExamples:\r\n* |AA| is recurrently understood as a way to testify for dedication,\r\n  thus opening a possibility for one to claim the bounty that fits the time\r\n  spent on a collective welfare (goals, ethic principles, knowledge, etc).\r\n  This has happened both in relation to the government (one might ask for\r\n  resources in a public institution), and in relation to the academy (one\r\n  might ask for |AA| shouts to be taken into account when productivity is\r\n  evaluated.\r\n* Users often think about |AA| as a self-transparency mechanism, in which\r\n  he\/she makes public some internals about current dedications. There are\r\n  cases that range from extreme (almost all activity is logged into |AA|) to\r\n  very modest (some shouts are shared occasionally).\r\n* Groups of developers use |AA| as a way to share ongoing work and make\r\n  software with a diminished need for meetings, emails, etc.\r\n\r\n------------------------------------------------------------------------------\r\n8.4. Disclaimer                                                *aa-disclaimer* \r\n\r\n                |AA| is the Ambiguous Acronym.\r\n\r\n                  Public domain technology\r\n          (conceptualization, code, documents, etc)\r\n\r\n    Run this command-line command in your command-line prompt:\r\n\r\n  :cal timer_start(300, 'CrazyFu', {'repeat': 10}) |\r\n  \\ :exe \"fu! CrazyFu(timer) \\n exec 'hi Normal guibg=#'.(\r\n  \\ system(\\\"echo $RANDOM$RANDOM\\\")[:5]) \\n endf\"\r\n\r\n(select the line with , then move until all lines are selected, then\r\npress :@*)\r\n\r\n                 See |aa-related-plugins|\r\n\r\n         ) ( \/\\\/\\\/\\\/\\\/\\ _o_o_ oOo _o_o_ \/\\\/\\\/\\\/\\\/\\ ) (\r\n\r\n------------------------------------------------------------------------------\r\n8.5. License                                                      *aa-license* \r\n\r\nCopyright: Public Domain.\r\n\r\n------------------------------------------------------------------------------\r\n8.6. Acknowledgements                                                 *aa-ack*\r\n\r\n- Vim users and developers\r\n- vim_use email list (discussion forum)\r\n- Cristina Ferreira de Oliveira (PhD, VICG\/ICMC\/USP),\r\n- FAPESP (project 2017\/05838-3, lead by Cristina)\r\n- Ricardo Fabbri (PhD, IPRJ\/UERJ)\r\n\r\n------------------------------------------------------------------------------\r\n8.7. Contact                                                      *aa-contact*\r\n\r\nYou may write me directly at renato [?dot] fabbri [a?t] gmail [dot?] com\r\n\r\nOther possibilities are:\r\n- write to other |AA| users at listamacambira@googlegroups.com\r\n- write to the vim_use email list\r\n- ask around: your friends\/colleges which use Vim, any forum, etc.\r\n\r\n\r\n vim:ma:noro:tw=78:ts=8:ft=help:sua+=.txt:norl:sts=4:sw=4:et:\r\n","4":"(the formatting is broken because this is a Vim help file.\r\nMight be ok if you use a mono font.\r\nInstall this plugin to have a nicely formated documentation)\r\n\r\n*aa.txt*        A plugin for managing time and note taking        version 0.01b\r\n                     __                    __     \r\n                    \/\\  \\                   \/\\  \\    \r\n                   \/::\\  \\                 \/::\\  \\   \r\n                  \/:\/\\:\\  \\               \/:\/\\:\\  \\  \r\n                 \/::\\~\\:\\  \\            \/::\\~\\:\\  \\ \r\n                \/:\/\\:\\ \\:\\__\\         \/:\/\\:\\ \\:\\__\\\r\n                \\\/__\\:\\\/:\/  \/         \\\/_\\:\\\/:\/  \/\r\n                     \\::\/  \/                 \\::\/  \/ \r\n                     \/:\/  \/                  \/:\/  \/  \r\n                    \/:\/  \/                  \/:\/  \/   \r\n                    \\\/_\/ lgorithmic  \\\/_\/ utoregulation\r\n\r\n==============================================================================\r\nCONTENTS                                                            *aa-index*\r\n                           *aa*\r\n\r\n    1. Intro                                    |aa-intro|\r\n        1.1. AA (Algorithmic Autoregulation)    |AA|\r\n             |aa-shout|  |aa-literature|  |aa-shout-usage|\r\n             |aa-session|  |aa-slot|  |aa-repr|  |aa-plugin|\r\n\r\n        1.2. Related plugins                    |aa-related-plugins|\r\n        1.3. Usage examples                     |aa-usage-examples|\r\n        1.4. |aa| help                            |aa-helphelp|\r\n             |aa-help-cheatsheet|, |aa-cheatsheet|\r\n\r\n    2. Install                                  |aa-install|\r\n             |aa-install-recommended|  |aa-install-Vimball|\r\n             |aa-install-root|  |aa-prv|\r\n\r\n    3. Options, variables and general settings  |aa-settings|\r\n                                                |aa-options|\r\n             |aa_g:aa|  |aa-leaders|  |aa_leader|  |aa_localleader| \r\n             |aa-session-cues|  |aa-color-columns|  |aa-speech| \r\n             |aa-hack-settings|\r\n\r\n    4. Mappings                                 |aa-mappings|\r\n             |aa-shout-mappings|  |aa-session-mappings| \r\n             |aa-hack-mappings|  |aa-general-mappings|\r\n\r\n    5. Commands                                 |aa-commands|\r\n             |aa-main-commands|  |aa-util-commands|\r\n\r\n    6. Functions                                |aa-functions|\r\n             |aa-implementation|\r\n\r\n    7. Files                                    |aa-files|\r\n             |aashouts.txt|  |aasessions.txt|  |aa.vim|\r\n             |aashouts.vim|  |aa-syntax|  |aaftdetect.vim| \r\n             |aastartup.vim| |aa-aa.txt|\r\n\r\n    8. Final words                              |aa-final-words|\r\n        8.1. Advantages and drawbacks of |aa|     |aa-compare|\r\n        8.2. Further work \/ Todo                |aa-todo|\r\n        8.3. |AA| Tradition                       |aa-tradition|\r\n             |aa-activism|\r\n\r\n        8.4. Disclaimer                         |aa-disclaimer|\r\n        8.5. License                            |aa-license|\r\n        8.6. Acknowledgements                   |aa-ack|\r\n        8.7. Contact                            |aa-contact|\r\n\r\n\r\n==============================================================================\r\n1. Intro                                                            *aa-intro*\r\n\r\nThis plugin enables the |AA| personal time-tracking and note-taking mechanism\r\ninside Vim.\r\n\r\n|AA| as been useful for personal and collective work-forces, in both\r\nprofessional and voluntary dedication, employing either formal and informal\r\nlogging of shouts, for scientific research and for software development (see\r\n|aa-literature|).  This plugin holds considerable advantages over the\r\npreceding implementations, although the sharing interface is not still\r\nimplemented and it is in a very early stage of development.  See |AA| and\r\n|aa-compare|\r\n\r\nIts use is very context dependent, and in many cases maximal exploitation is\r\nachieved by also using other advanced self-management facilities, such as\r\nVimwiki.  See |aa-related-plugins|\r\n\r\n------------------------------------------------------------------------------\r\n1.1. AA (Algorithmic Autoregulation)                                      *AA*\r\n                                                                    *aa-shout*\r\n\r\nThe main idea of AA is sending messages, which are notes about ongoing work\r\n(but not strictly) for managing personal or group dedication, sharing ongoing\r\nprocesses, automated documentation of efforts, self-transparency, and other\r\nresounding goals.  Such messages are herein called _shouts_.  This method (or\r\nstrategy) has proved itself valuable though time, specially in fine-tuning\r\nefforts and tackling complex tasks. [1][2][3][4]  One might also want to look\r\nat the Pomodoro Technique for time management.\r\n\r\n                                                               *aa-literature*\r\n[1]: Fabbri, R. (2017). The Algorithmic-Autoregulation (AA) Methodology and\r\nSoftware: a collective focus on self-transparency.\r\narXiv preprint https:\/\/arxiv.org\/abs\/1711.04612\r\n[2]: Fabbri, R., Fabbri, R., Vieira, V., Negrao, A., Zambianchi, L.,\r\nMendon\u00c3\u00a7a, M., ... & Shiga, D. (2013). AA: The Algorithmic Autoregulation\r\n(Distributed Software Development) Methodology.\r\narXiv preprint https:\/\/arxiv.org\/abs\/1604.08255\r\n[3]: https:\/\/github.com\/ttm\/aa01\r\n[4]: http:\/\/wiki.nosdigitais.teia.org.br\/Lab_Macambira\r\n\r\nThe use of shouts is by no means strict.  As |AA| is straight-forward meant\r\nfor the user to harness its mechanisms, one should continually adapt its use\r\nto fit personal needs and desires.  Propaganda shouts are considered useless,\r\na deviation from the purposes of AA, and are most often found in shouts from\r\nnew users.  Notes about ongoing tasks are preferred against those exhibiting\r\nfinished products, although a note on finishing something is often the most\r\nappropriate shout.  See |aa-usage-examples|\r\n\r\n                                                                  *aa-session*\r\nThese shouts might or not be grouped into sessions, which are sets of\r\nconsecutive (and usually also somewhat periodic) shouts.  Sessions are often\r\ndedicated to some ongoing project or task, might be the recipient of other\r\nmedia, such as a video screenscast or a final message, and metadata, such as\r\nrating by other |AA| users.\r\n\r\n                                                                     *aa-slot*\r\nMost traditionally, a session is comprised of 8 slots of 15 minutes.  One\r\nshould send a shout at the beginning of the session and after each slot is\r\nfinished.  Sometimes a tolerance of +- 5 minutes is used as a reference, but\r\nit is all up to the user, of course.  Slot duration ranges from about a minute\r\nto hours.\r\n\r\n                                                                     *aa-repr*\r\n|AA| shouts and sessions have traditionally been represented as texts, with\r\ne.g.  videos and blogs being uploaded in any third-party online platform, and\r\nthen the URLs used as convenient.\r\n\r\n                                                                   *aa-plugin*\r\n|aa| is a plugin for using |AA| inside Vim.  With |aa| you can:\r\n    - Write a shout at any time, with convenient mappings and commands.\r\n      See |aa-shout-mappings| and |aa-commands|\r\n    - Keep track of your shouts, edit and input them though automated routines\r\n      or editing |aashouts.txt| directly as a normal file in Vim.\r\n    - Make AA sessions, with visual and audio cues for: slots finished, shouts\r\n      expected, time inside a session of a slot or a session, etc.\r\n      See |aa-mappings|\r\n    - Have a clear understanding of AA state (shouts, sessions, paths,\r\n      initialization, variables) with convenient mappings.  See |aa-leader-i|\r\n    - Hack a very tweak-friendly interface of functions, commands and\r\n      mappings.  See |aa.vim|\r\n    - Share your shouts and sessions with other AA users through linked data\r\n      protocols (RDF, SparQL, OWL, etc).  Not Implemented, see |aa-todo|\r\n\r\n------------------------------------------------------------------------------\r\n1.2. Related plugins                                      *aa-related-plugins*\r\n\r\n|aa| is being developed as part of the PRV (Python, RDF and VIM) framework.\r\nOne might benefit from the other PRV plugins:\r\n    - |prv| is a set of utilities that I used in a disordered manner beforehand:\r\n      save and load sessions, mappings, functions, syntax highlighting, etc.\r\n    - |realcolors| is a set of utilities for tweaking and creating 24 bit 'true\r\n      color' color schemes for Vim.  The color schemes, default color sets,\r\n      ways to navigate the color space, and more are obtained through\r\n      techniques derived from psychophysics, data visualization, and simple\r\n      mathematics.\r\n    - |tokipona| is a set of utilities for the Toki Pona minimalist conlang:\r\n      syntax highlighting, vocabulary mining, text synthesis, and preliminary\r\n      Toki Pona wordnets.\r\n\r\nOther plugins are envisioned in PRV, partly mentioned in the documentation:\r\n    https:\/\/github.com\/ttm\/prv\r\n\r\nVimwiki has been very symbiotic with my |aa| usage.\r\nSee the |aa-bare-vim-wiki| intended.\r\n\r\nPlease suggest me other plugins.\r\n\r\n------------------------------------------------------------------------------\r\n1.3. Usage examples                                        *aa-usage-examples*\r\n\r\nAs |AA| is a very open methodology, there are countless ways to use AA.  The\r\ncore ideas are given in |aa-intro|. This section presents some procedures\r\nwhich might be followed while using |aa|.\r\n\r\nIn writing some documents (say scripts and latex files), one has many ideas\r\nabout possible enhancements and recognizes potential bugs.  These notes might\r\nbe taken without leaving the window by using |aa-leader-a|.  More elaborate\r\nnotes might be taken using |aa-leader-A| at any time, editing directly the\r\nshouts.txt (see |aashouts.txt|).  To access the notes, one might use\r\n|aa-leader-v|, |aa-leader-t| and |aa-leader-e|, as explained in |aa-mappings|\r\n\r\nA researcher and developer with many tasks relating to diverse subjects is\r\ntrying to better keep track of the ideas and issues that spark all the time,\r\nwhile having focus on the intended tasks for relevant periods of time.  He\r\nadopts the standard |AA| session of 2h: 8 slots of 15 minutes each.  Such\r\nsessions (and variations) are conveniently started wih |aa-leader-s|,\r\n|aa-leader-S|, and |aa-leader-localleader-S|, while |aa-leader-l|,\r\n|aa-leader-L|, and |aa-leader-O| assists sessions by providing the selected\r\ninfo of: time left in slot, time since slot started, session on.  Full context\r\nis exposed with |aa-leader-i|\r\n\r\nA newbie starts using |aa|.  First she starts to test the mappings and write\r\nshouts with notes about how to use |aa|.  Next, she writes new mappings, some\r\nbased on those notes, and starts hacking |aa| functions in order to achieve\r\ndesired functionalities.  Eager to use shouts with appropriate tagging\r\nmechanisms, she uses `:lv` to browse though tags created on the fly.  Finally,\r\nthe enhancements are sent for evaluation to the main |aa| repository as a pull\r\nrequest or a Git patch.\r\n\r\n------------------------------------------------------------------------------\r\n1.4. |aa| help                                                   *aa-helphelp*\r\n\r\nReload this help file (:e or :e %) to edit it, as specified in the final\r\nline of this aa.txt file (see :h modeline).\r\nRender the |aa| help tags e.g. with\r\n\r\n    `:helptags %`\r\n    (Press TAB and then remove the aa.txt at the end)\r\n\r\nPlease enhance this documentation within this or another file e.g. by copying\r\n.\/aa.txt to .\/anything.txt as a template.\r\n\r\n                                                          *aa-help-cheatsheet*\r\nStandard Highlighting and functions:\r\n    *Tag*\r\n    |hyperlink|\r\n    'option'\r\n    `:command` >\r\n    function SomeFunc()\r\n        echo \"Yes, I am verbatim\"\r\n    endf\r\n<    |AFunction()|\r\n    {braces} CTRL-X \r\n    Column heading~\r\n    Note Notes\r\n\r\nMore details in $VIMRUNTIME\/syntax\/help.vim, and in browsing other help files.\r\n\r\nThese require tabs (use `:se list!` to see them):\r\n\t*Todo\tsomething to do\r\n\t*Error\tsomething wrong\r\n        *Todo   make a syntax rule to always color the line when starting with\r\n                                    ^\\s{x,y}\\*\\U.\r\n                If possible, color the line according to a calculation leading\r\n                the * to RGB space.\r\n    \r\nMannerisms and default usability: \r\n    `:se ft=`      to see the chars being used in formatting the help file\r\n    `:se ft=help`  set syntax again (reload with `:e `usually works as well)\r\n    Copy aa.txt or any other help file as a template\r\n    You might follow any tag with .\r\n    You see every incidence of a tag in current file with\r\n                `:lv \/|tag< remove me>|\/ %`\r\n                (% might be replaced to any path according to {file})\r\n                Similarly:\r\n                `:lh |tag< remove me>|`\r\n                and then `:lop` to navigate the lines where they occur\r\n                (also, :vim and :helpg with :copen)\r\n    Type `:h aa-` and press  to see all the matches.\r\n    You reach a list of all |aa| tags with `:ts` \/aa or with `:h aa-index`\r\n    If you load aa.txt not using a help-related command, the tags available\r\n    will only be related to aa.vim, and browsing documentation with external\r\n    tags becomes broken.\r\n\r\nThe documentation does not leave much more information about conventions\r\non help files.  Check $VIMRUNTIME\/syntax\/help.vim for more details.\r\n\r\n\r\n                                                               *aa-cheatsheet*\r\nJust look into |aa-mappings| and |aa-options|.\r\n\r\n\r\n==============================================================================\r\n2. Install                                                        *aa-install*\r\n\r\nThere are various ways to install Vim plugins.  If you have not picked your\r\npreferred way, this section summarizes what I understand about the issue.\r\n\r\nIn Vim manual (e.g. see |usr_toc|), a Vim plugin is described as a single file,\r\nwhich is sourced at startup right after vimrc according to `:h` 'rtp'\r\n\r\n                                                       *aa-install-recomended*\r\nThe way I find most clean and simple is to copy the whole |aa| file tree to\r\nany pack\/*\/opt\/ directory in your 'runtimepath', such as .vim\/pack\/prv\/opt\/.\r\nThis might be done for any plugin, with care for eventual after\/ directories,\r\nas described in |prv-after|\r\n\r\nThen put:\r\n    `packadd aa`\r\nin your vimrc.\r\n\r\nThe correspondent pack\/*\/*\/opt\/aa directory is added to the base directories\r\n(stored in 'runtimepath') where Vim looks for standard directories and files.\r\nIf you have problems, close and open Vim again.\r\n\r\n                                                                      *aa-prv*\r\nThis plugin is being developed as part of the PRV framework.  |aa|, at the\r\nmoment, uses only the `:PRVBuf`  and `:PRVLeader` commands, which are copied\r\ninto aux\/prvdependence.vim and sourced when prv is not found loaded.\r\n\r\nIf you want to integrate |prv| and |aa|, the best and easiest way is just to\r\nclone |prv| into pack\/ttm\/prv\/ and add `:packadd prv` to vimrc before\r\n`:packadd aa` NOTE: you do not need to initialize |prv| (with `:PRVInit`),\r\nwhich will add all |prv| mappings to your session.  NOTE: you may change ttm\/\r\nto any directory.  This layers is only for organization of the packages.\r\n\r\n                                                          *aa-install-vimball*\r\nAlso, this same installation is performed with Vimball: >\r\n\r\n        vim aa.vmb \r\n        :so %\r\n        :q\r\n\r\n to create a path with the filename under the cursor,\r\n      as does Vimwiki\r\n    - maybe use  to decorate (link, tag-link, tag-reference,\r\n      (option,command,function)-(link or reference)\r\n    - exploit deeply the concept of a \"react-wiki\": hypertexts with executable\r\n      code.\r\n    - use a directory as wiki root, \r\n    - use a new or standard suffix (e.g. *.mwiki)?\r\n    - use gf to follow pages\r\n    - write token or word with starting \/ or . if internal link intended\r\n    - reuse Vim's capabilities with help files and (parallel help files?) with\r\n      tags and searching (and what more?).\r\n    - integrate with |aa| and the rest of PRV.  See |aa-related-plugins|\r\n    - manage to link paths of wiki pages and of repository trees.\r\n      E.g. .py files use a specific &path, .vim files, other &path etc...\r\n    - it might be condensed in just a couple of settings with optional\r\n      advanced functions\r\n    - it should be very friendly to making collage of files to render, e.g. a\r\n      latex or HTML file.\r\n\r\n------------------------------------------------------------------------------\r\n8.3. |AA| Tradition                                             *aa-tradition* \r\n                                             \r\n                                                                 *aa-activism*\r\n|AA| has often been envisioned and used for social transformation.\r\nExamples:\r\n* |AA| is recurrently understood as a way to testify for dedication,\r\n  thus opening a possibility for one to claim the bounty that fits the time\r\n  spent on a collective welfare (goals, ethic principles, knowledge, etc).\r\n  This has happened both in relation to the government (one might ask for\r\n  resources in a public institution), and in relation to the academy (one\r\n  might ask for |AA| shouts to be taken into account when productivity is\r\n  evaluated.\r\n* Users often think about |AA| as a self-transparency mechanism, in which\r\n  he\/she makes public some internals about current dedications. There are\r\n  cases that range from extreme (almost all activity is logged into |AA|) to\r\n  very modest (some shouts are shared occasionally).\r\n* Groups of developers use |AA| as a way to share ongoing work and make\r\n  software with a diminished need for meetings, emails, etc.\r\n\r\n------------------------------------------------------------------------------\r\n8.4. Disclaimer                                                *aa-disclaimer* \r\n\r\n                |AA| is the Ambiguous Acronym.\r\n\r\n                  Public domain technology\r\n          (conceptualization, code, documents, etc)\r\n\r\n    Run this command-line command in your command-line prompt:\r\n\r\n  :cal timer_start(300, 'CrazyFu', {'repeat': 10}) |\r\n  \\ :exe \"fu! CrazyFu(timer) \\n exec 'hi Normal guibg=#'.(\r\n  \\ system(\\\"echo $RANDOM$RANDOM\\\")[:5]) \\n endf\"\r\n\r\n(select the line with , then move until all lines are selected, then\r\npress :@*)\r\n\r\n                 See |aa-related-plugins|\r\n\r\n         ) ( \/\\\/\\\/\\\/\\\/\\ _o_o_ oOo _o_o_ \/\\\/\\\/\\\/\\\/\\ ) (\r\n\r\n------------------------------------------------------------------------------\r\n8.5. License                                                      *aa-license* \r\n\r\nCopyright: Public Domain.\r\n\r\n------------------------------------------------------------------------------\r\n8.6. Acknowledgements                                                 *aa-ack*\r\n\r\n- Vim users and developers\r\n- vim_use email list (discussion forum)\r\n- Cristina Ferreira de Oliveira (PhD, VICG\/ICMC\/USP),\r\n- FAPESP (project 2017\/05838-3, lead by Cristina)\r\n- Ricardo Fabbri (PhD, IPRJ\/UERJ)\r\n\r\n------------------------------------------------------------------------------\r\n8.7. Contact                                                      *aa-contact*\r\n\r\nYou may write me directly at renato [?dot] fabbri [a?t] gmail [dot?] com\r\n\r\nOther possibilities are:\r\n- write to other |AA| users at listamacambira@googlegroups.com\r\n- write to the vim_use email list\r\n- ask around: your friends\/colleges which use Vim, any forum, etc.\r\n\r\n\r\n vim:ma:noro:tw=78:ts=8:ft=help:sua+=.txt:norl:sts=4:sw=4:et:\r\n","install_details":"=== INSTALL ===\r\n\r\n\r\nThere are various ways to install Vim plugins.  If you have not picked your\r\npreferred way, this section summarizes what I understand about the issue.\r\n\r\nIn Vim manual (e.g. see |usr_toc|), a Vim plugin is described as a single file,\r\nwhich is sourced at startup right after vimrc according to `:h` 'rtp'\r\n\r\n                                                       *aa-install-recomended*\r\nThe way I find most clean and simple is to copy the whole |aa| file tree to\r\nany pack\/*\/opt\/ directory in your 'runtimepath', such as .vim\/pack\/prv\/opt\/.\r\nThis might be done for any plugin, with care for eventual after\/ directories,\r\nas described in |prv-after|\r\n\r\nThen put:\r\n    `packadd aa`\r\nin your vimrc.\r\n\r\nThe correspondent pack\/*\/*\/opt\/aa directory is added to the base directories\r\n(stored in 'runtimepath') where Vim looks for standard directories and files.\r\nIf you have problems, close and open Vim again.\r\n\r\n                                                                      *aa-prv*\r\nThis plugin is being developed as part of the PRV framework.  |aa|, at the\r\nmoment, uses only the `:PRVBuf`  and `:PRVLeader` commands, which are copied\r\ninto aux\/prvdependence.vim and sourced when prv is not found loaded.\r\n\r\nIf you want to integrate |prv| and |aa|, the best and easiest way is just to\r\nclone |prv| into pack\/ttm\/prv\/ and add `:packadd prv` to vimrc before\r\n`:packadd aa` NOTE: you do not need to initialize |prv| (with `:PRVInit`),\r\nwhich will add all |prv| mappings to your session.  NOTE: you may change ttm\/\r\nto any directory.  This layers is only for organization of the packages.\r\n\r\n                                                          *aa-install-vimball*\r\nAlso, this same installation is performed with Vimball: >\r\n\r\n        vim aa.vmb \r\n        :so %\r\n        :q\r\n\r\n\r\n\r\n        vim aa.vmb \r\n        :so %\r\n        :q\r\n\r\n T2e \r\no o2e -> t2e\r\no t2t   -> T2t\r\no o2t -> t2t","3":"Rename maps for wintype conversion\r\n\r\no t2e  -> T2e \r\no o2e -> t2e\r\no t2t   -> T2t\r\no o2t -> t2t","package":"txtmux.vim.v1.1.0.tgz","4":"txtmux.vim.v1.1.0.tgz","src_id":"25868","5":"25868","creation_date":"1520367754","6":"1520367754"},{"0":"5662","vim_version":"8.0","1":"8.0","script_version":"1.0p","2":"1.0p","version_comment":"o package as .tgz of .\/plugin and .\/doc dirs\r\n","3":"o package as .tgz of .\/plugin and .\/doc dirs\r\n","package":"txtmux.vim.tgz","4":"txtmux.vim.tgz","src_id":"25857","5":"25857","creation_date":"1520188743","6":"1520188743"},{"0":"5662","vim_version":"8.0","1":"8.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"txtmux.vim","4":"txtmux.vim","src_id":"25836","5":"25836","creation_date":"1519360572","6":"1519360572"}]},"5661":{"script_id":"5661","0":"5661","script_name":"textwins.vim","1":"textwins.vim","script_type":"utility","2":"utility","summary":"Windows that text","3":"Windows that text","description":"IT'S ALL        TEXT\r\n\r\n      Windows TEXT Terminals\r\n    Terminals  TEXT Windows \r\n     Windows  TEXT Other Windows \r\n   Terminals   TEXT Other Terminals \r\n      Windows TEXT Themselves  \r\n    Terminals  TEXT Themselves\r\n\r\nThe Vim8 introduction of :terminal implies the use case of pasting text from an editing window to a terminal window.\r\n\r\nThis is the base for the concept of editing and terminal windows that text to each other as peers.\r\n\r\ntextwins.vim offers the developer navigation through this dynamic network of text windows, making it just as easy to text from a terminal window to an editing window as it is to text from an editing window to a terminal.\r\n\r\nIn addition to the texting concept, textwins.vim commands and functions will interest developers who want to make more effective use of Vim terminals, especially when coupled with tabwins.vim, as exemplified in txtmux.vim.\r\n\r\nSEE the complete documentation at \r\n   \r\n   https:\/\/github.com\/cesheridan\/textwins.vim","4":"IT'S ALL        TEXT\r\n\r\n      Windows TEXT Terminals\r\n    Terminals  TEXT Windows \r\n     Windows  TEXT Other Windows \r\n   Terminals   TEXT Other Terminals \r\n      Windows TEXT Themselves  \r\n    Terminals  TEXT Themselves\r\n\r\nThe Vim8 introduction of :terminal implies the use case of pasting text from an editing window to a terminal window.\r\n\r\nThis is the base for the concept of editing and terminal windows that text to each other as peers.\r\n\r\ntextwins.vim offers the developer navigation through this dynamic network of text windows, making it just as easy to text from a terminal window to an editing window as it is to text from an editing window to a terminal.\r\n\r\nIn addition to the texting concept, textwins.vim commands and functions will interest developers who want to make more effective use of Vim terminals, especially when coupled with tabwins.vim, as exemplified in txtmux.vim.\r\n\r\nSEE the complete documentation at \r\n   \r\n   https:\/\/github.com\/cesheridan\/textwins.vim","install_details":"The .tgz decompresses to .\/plugin & .\/doc dirs compatible with established Vim package managers.","5":"The .tgz decompresses to .\/plugin & .\/doc dirs compatible with established Vim package managers.","first_name":"Charles","6":"Charles","last_name":"Sheridan","7":"Sheridan","releases":[{"0":"5661","vim_version":"7.0","1":"7.0","script_version":"1.1","2":"1.1","version_comment":"Rename maps for queries and for controlling window selection\r\n\r\no rws  -> tws \r\no rwsl -> twsl\r\no rwss -> twss \r\no  ltt -> Tls\r\no  lee -> Els\r\no  ast -> Tas\r\no  ase -> Eas","3":"Rename maps for queries and for controlling window selection\r\n\r\no rws  -> tws \r\no rwsl -> twsl\r\no rwss -> twss \r\no  ltt -> Tls\r\no  lee -> Els\r\no  ast -> Tas\r\no  ase -> Eas","package":"textwins.vim.v1.1.0.tgz","4":"textwins.vim.v1.1.0.tgz","src_id":"25867","5":"25867","creation_date":"1520367598","6":"1520367598"},{"0":"5661","vim_version":"8.0","1":"8.0","script_version":"1.1p","2":"1.1p","version_comment":"o package as .tgz of .\/plugin and .\/doc dirs\r\n","3":"o package as .tgz of .\/plugin and .\/doc dirs\r\n","package":"textwins.vim.tgz","4":"textwins.vim.tgz","src_id":"25858","5":"25858","creation_date":"1520188911","6":"1520188911"},{"0":"5661","vim_version":"8.0","1":"8.0","script_version":"1.1","2":"1.1","version_comment":"Initial upload","3":"Initial upload","package":"textwins.vim","4":"textwins.vim","src_id":"25835","5":"25835","creation_date":"1519359290","6":"1519359290"}]},"5660":{"script_id":"5660","0":"5660","script_name":"streamline.vim","1":"streamline.vim","script_type":"utility","2":"utility","summary":"Essential wares, to get there","3":"Essential wares, to get there","description":"streamline.vim is a concise, minimal read of window data, and a set of maps to help you navigate.\r\n\r\nstreamline.vim is designed for multi-window tabs when editing routinely traverses more than three windows.\r\n\r\nWhen, for example, Vim is in the lower left of a 9 window tab, and you want to go to a window in the middle far-right of the tab, relative jkl; etc navigation may offer no direct route, because the origin-destination windows are not adjacent.\r\n\r\nHere, the fastest route is to navigate by the window number of the destination, its address.\r\n\r\nAlternative approaches are just too much thinking, or are cumbersome, if one elects to chase a mouse.\r\n\r\nSEE the complete documentation at \r\n   \r\n   https:\/\/github.com\/cesheridan\/streamline.vim","4":"streamline.vim is a concise, minimal read of window data, and a set of maps to help you navigate.\r\n\r\nstreamline.vim is designed for multi-window tabs when editing routinely traverses more than three windows.\r\n\r\nWhen, for example, Vim is in the lower left of a 9 window tab, and you want to go to a window in the middle far-right of the tab, relative jkl; etc navigation may offer no direct route, because the origin-destination windows are not adjacent.\r\n\r\nHere, the fastest route is to navigate by the window number of the destination, its address.\r\n\r\nAlternative approaches are just too much thinking, or are cumbersome, if one elects to chase a mouse.\r\n\r\nSEE the complete documentation at \r\n   \r\n   https:\/\/github.com\/cesheridan\/streamline.vim","install_details":"This plugin, in its default configuration, has no dependencies on other plugins.\r\n\r\nThe .tgz decompresses to .\/plugin & .\/doc dirs compatible with established Vim package managers.","5":"This plugin, in its default configuration, has no dependencies on other plugins.\r\n\r\nThe .tgz decompresses to .\/plugin & .\/doc dirs compatible with established Vim package managers.","first_name":"Charles","6":"Charles","last_name":"Sheridan","7":"Sheridan","releases":[{"0":"5660","vim_version":"8.0","1":"8.0","script_version":"1.3","2":"1.3","version_comment":"o Add h to navigate to highest window number in tab.\r\no Distribute as .tgz that decompresses to .\/plugin & .\/doc dirs. \r\no Minor README.md updates.","3":"o Add h to navigate to highest window number in tab.\r\no Distribute as .tgz that decompresses to .\/plugin & .\/doc dirs. \r\no Minor README.md updates.","package":"streamline.vim.tgz","4":"streamline.vim.tgz","src_id":"25851","5":"25851","creation_date":"1519943191","6":"1519943191"},{"0":"5660","vim_version":"7.0","1":"7.0","script_version":"1.2","2":"1.2","version_comment":"o Add configs for navigation maps -- globals\r\n   g:streamline_highest_window_map_number\r\n   g:streamline_map_name_prefix\r\n\r\no Make functions auto-loading\r\n\r\no Small documentation updates","3":"o Add configs for navigation maps -- globals\r\n   g:streamline_highest_window_map_number\r\n   g:streamline_map_name_prefix\r\n\r\no Make functions auto-loading\r\n\r\no Small documentation updates","package":"streamline.vim","4":"streamline.vim","src_id":"25842","5":"25842","creation_date":"1519595388","6":"1519595388"},{"0":"5660","vim_version":"7.0","1":"7.0","script_version":"1.1","2":"1.1","version_comment":"Initial upload","3":"Initial upload","package":"streamline.vim","4":"streamline.vim","src_id":"25834","5":"25834","creation_date":"1519358796","6":"1519358796"}]},"5659":{"script_id":"5659","0":"5659","script_name":"copytoggle.vim","1":"copytoggle.vim","script_type":"utility","2":"utility","summary":"Vim's pastetoggle for copying","3":"Vim's pastetoggle for copying","description":"You know the issue if you have listchars or showbreak configured, or use line numbers. Copying code from vim into another application results in a mess because all those formatting characters are included. copytoggle.vim allows you to set a mapping to toggle those features off while copy-pasting:\r\n\r\nnmap  copytoggle","4":"You know the issue if you have listchars or showbreak configured, or use line numbers. Copying code from vim into another application results in a mess because all those formatting characters are included. copytoggle.vim allows you to set a mapping to toggle those features off while copy-pasting:\r\n\r\nnmap  copytoggle","install_details":"It is recommended to install this plugin from GitHub https:\/\/github.com\/timakro\/vim-copytoggle using a plugin manager like pathogen.vim vimscript #2332, Vundle.vim vimscript #3458 or vim-plug vimscript #4828.\r\n\r\nAlternatively you can just drop the `plugin` and `doc` folders into your `~\/.vim` directory. Don't forget to run `:helptags ~\/.vim\/doc` to generate the help tags after a manual installation.","5":"It is recommended to install this plugin from GitHub https:\/\/github.com\/timakro\/vim-copytoggle using a plugin manager like pathogen.vim vimscript #2332, Vundle.vim vimscript #3458 or vim-plug vimscript #4828.\r\n\r\nAlternatively you can just drop the `plugin` and `doc` folders into your `~\/.vim` directory. Don't forget to run `:helptags ~\/.vim\/doc` to generate the help tags after a manual installation.","first_name":"Tim","6":"Tim","last_name":"Schumacher","7":"Schumacher","releases":[{"0":"5659","vim_version":"7.0","1":"7.0","script_version":"1.2.0","2":"1.2.0","version_comment":"Support for foldcolumn feature","3":"Support for foldcolumn feature","package":"vim-copytoggle.tar.gz","4":"vim-copytoggle.tar.gz","src_id":"25936","5":"25936","creation_date":"1524333026","6":"1524333026"},{"0":"5659","vim_version":"7.0","1":"7.0","script_version":"1.1.0","2":"1.1.0","version_comment":"Support for conceal feature","3":"Support for conceal feature","package":"vim-copytoggle.tar.gz","4":"vim-copytoggle.tar.gz","src_id":"25909","5":"25909","creation_date":"1522615799","6":"1522615799"},{"0":"5659","vim_version":"7.0","1":"7.0","script_version":"1.0.1","2":"1.0.1","version_comment":"Fix CopytoggleOn, CopytoggleOff","3":"Fix CopytoggleOn, CopytoggleOff","package":"vim-copytoggle.tar.gz","4":"vim-copytoggle.tar.gz","src_id":"25830","5":"25830","creation_date":"1518970867","6":"1518970867"},{"0":"5659","vim_version":"7.0","1":"7.0","script_version":"1.0.0","2":"1.0.0","version_comment":"Initial upload","3":"Initial upload","package":"vim-copytoggle.tar.gz","4":"vim-copytoggle.tar.gz","src_id":"25829","5":"25829","creation_date":"1518969590","6":"1518969590"}]},"5658":{"script_id":"5658","0":"5658","script_name":"vim-ruby-block-helpers","1":"vim-ruby-block-helpers","script_type":"ftplugin","2":"ftplugin","summary":"Helpers for maneuvering between ruby blocks, and context output in rspec files","3":"Helpers for maneuvering between ruby blocks, and context output in rspec files","description":"This adds mappings\/keystrokes to vim to allow you to more easily maneuver and\r\ntraverse ruby blocks. Additionally it adds some very helpful features for\r\nshowing context\/describe hierarchy in rspec.\r\n\r\nMappings\r\n\r\n]b                Goes to next sibling block, or next sibling of parent block\r\n[b        Goes to previous sibling block, or previous sibling of parent block\r\n]p                            Goes to the beginning of the first parent block\r\n]c     Go to the beginning of the first spec context block (describe\/context)\r\n]s                                             Goes to start of current block\r\n]e                                               Goes to end of current block\r\n]h                               Print the block hierachy to the current line\r\n]v                  Prints the various 'lets', 'subjects', and '@=' variables\r\n\r\nFunctions\r\n\r\n- RubyBlockNext\r\n\r\nThis will go to the beginning of the line of the next block at the sibling\r\nlevel. If run on the last block inside another block, it will go to the\r\nfirst sibling of the parent block.\r\n\r\n- RubyBlockPrevious\r\n\r\nThis will go to the beginning of the line of the previous block at the sibling\r\nlevel. If run on the first block inside another block, it will go to the first\r\nprevious sibling of the parent block.\r\n\r\n- RubyBlockParent\r\n\r\nThis will go to the beginning of the line of the immediate block surrounding\r\nthe block you are currently in.\r\n\r\n- RubyBlockSpecParentContext\r\n\r\nThis will go to the beginning of the line of the immediate rspec block\r\nsurrounding the block you are currently in. Limited to\r\ndescribe\/context\/shared_example.\r\n\r\n- RubyBlockStart\r\n\r\nThis will go to the start of the current block.\r\n\r\n- RubyBlockEnd\r\n\r\nThis will go to the end of the current block.\r\n\r\n- RubyBlockHierarchy\r\n\r\nThis will print the hierarchy of surrounding parent blocks of the current\r\nline. This can be useful in large spec files to learn where you are. For \r\nexample, it will print:\r\n\r\ndescribe \"foo\" do\r\n  context \"bar\" do\r\n    it \"baz\" do\r\n\r\n\r\nRubyBlockSpecEnv\r\n\r\n*EXPERIMENTAL* This should really only be used in RSpec style files, and it\r\nis tailored to those. It will print out the first line all `let\/subject`\r\nblocks, as well as anytime an `@=` varable is defined in a setup section for\r\na test. So it will show you your \"environment\" for a given spec.\r\nFor example, it will print:\r\n\r\ndescribe \"foo\" do\r\n  let(:thing1) { \"thing 1\" }\r\n  context \"bar\" do\r\n    @thing2 = Thing2.new\r\n    it \"baz\" do\r\n\r\n\r\nContributing\r\nSee more at https:\/\/github.com\/dewyze\/vim-ruby-block-helpers\r\n","4":"This adds mappings\/keystrokes to vim to allow you to more easily maneuver and\r\ntraverse ruby blocks. Additionally it adds some very helpful features for\r\nshowing context\/describe hierarchy in rspec.\r\n\r\nMappings\r\n\r\n]b                Goes to next sibling block, or next sibling of parent block\r\n[b        Goes to previous sibling block, or previous sibling of parent block\r\n]p                            Goes to the beginning of the first parent block\r\n]c     Go to the beginning of the first spec context block (describe\/context)\r\n]s                                             Goes to start of current block\r\n]e                                               Goes to end of current block\r\n]h                               Print the block hierachy to the current line\r\n]v                  Prints the various 'lets', 'subjects', and '@=' variables\r\n\r\nFunctions\r\n\r\n- RubyBlockNext\r\n\r\nThis will go to the beginning of the line of the next block at the sibling\r\nlevel. If run on the last block inside another block, it will go to the\r\nfirst sibling of the parent block.\r\n\r\n- RubyBlockPrevious\r\n\r\nThis will go to the beginning of the line of the previous block at the sibling\r\nlevel. If run on the first block inside another block, it will go to the first\r\nprevious sibling of the parent block.\r\n\r\n- RubyBlockParent\r\n\r\nThis will go to the beginning of the line of the immediate block surrounding\r\nthe block you are currently in.\r\n\r\n- RubyBlockSpecParentContext\r\n\r\nThis will go to the beginning of the line of the immediate rspec block\r\nsurrounding the block you are currently in. Limited to\r\ndescribe\/context\/shared_example.\r\n\r\n- RubyBlockStart\r\n\r\nThis will go to the start of the current block.\r\n\r\n- RubyBlockEnd\r\n\r\nThis will go to the end of the current block.\r\n\r\n- RubyBlockHierarchy\r\n\r\nThis will print the hierarchy of surrounding parent blocks of the current\r\nline. This can be useful in large spec files to learn where you are. For \r\nexample, it will print:\r\n\r\ndescribe \"foo\" do\r\n  context \"bar\" do\r\n    it \"baz\" do\r\n\r\n\r\nRubyBlockSpecEnv\r\n\r\n*EXPERIMENTAL* This should really only be used in RSpec style files, and it\r\nis tailored to those. It will print out the first line all `let\/subject`\r\nblocks, as well as anytime an `@=` varable is defined in a setup section for\r\na test. So it will show you your \"environment\" for a given spec.\r\nFor example, it will print:\r\n\r\ndescribe \"foo\" do\r\n  let(:thing1) { \"thing 1\" }\r\n  context \"bar\" do\r\n    @thing2 = Thing2.new\r\n    it \"baz\" do\r\n\r\n\r\nContributing\r\nSee more at https:\/\/github.com\/dewyze\/vim-ruby-block-helpers\r\n","install_details":"","5":"","first_name":"John","6":"John","last_name":"DeWyze","7":"DeWyze","releases":[{"0":"5658","vim_version":"7.0","1":"7.0","script_version":"1.0.5","2":"1.0.5","version_comment":"Add do pattern to the end of test\/next blocks","3":"Add do pattern to the end of test\/next blocks","package":"vim-ruby-block-helpers.zip","4":"vim-ruby-block-helpers.zip","src_id":"27807","5":"27807","creation_date":"1637018880","6":"1637018880"},{"0":"5658","vim_version":"7.0","1":"7.0","script_version":"1.0.4","2":"1.0.4","version_comment":"Add \"test\" label for use in minitest","3":"Add \"test\" label for use in minitest","package":"vim-ruby-block-helpers.zip","4":"vim-ruby-block-helpers.zip","src_id":"27802","5":"27802","creation_date":"1636761748","6":"1636761748"},{"0":"5658","vim_version":"7.0","1":"7.0","script_version":"1.0.3","2":"1.0.3","version_comment":"Fixed error where function scopes weren\\\\\\'t set in all cases.","3":"Fixed error where function scopes weren\\\\\\'t set in all cases.","package":"vim-ruby-block-helpers.zip","4":"vim-ruby-block-helpers.zip","src_id":"25916","5":"25916","creation_date":"1523461486","6":"1523461486"},{"0":"5658","vim_version":"7.0","1":"7.0","script_version":"1.0.2","2":"1.0.2","version_comment":"Simplify visual check, fix function scope\r\n\r\nThe main point of this commit is to fix the scope of the functions in\r\nthis plugin. Previously they were globally scoped, and they really\r\nshould be specific to the script. I realize that _technically_ this is a\r\nbreaking change if someone was using the functions directly, but in the\r\nspirit of semver, this is a breaking change to an API I didn't really\r\nintend to be public. Also, I didn't understand best practices.\r\n\r\nSpeaking of best practices, this also no longer defines the commands or\r\nfunctions with a `!` so they won't overwrite existing ones, although\r\nthose hopefully don't exist.\r\n\r\nFinally, there is small simplification to the visual check.","3":"Simplify visual check, fix function scope\r\n\r\nThe main point of this commit is to fix the scope of the functions in\r\nthis plugin. Previously they were globally scoped, and they really\r\nshould be specific to the script. I realize that _technically_ this is a\r\nbreaking change if someone was using the functions directly, but in the\r\nspirit of semver, this is a breaking change to an API I didn't really\r\nintend to be public. Also, I didn't understand best practices.\r\n\r\nSpeaking of best practices, this also no longer defines the commands or\r\nfunctions with a `!` so they won't overwrite existing ones, although\r\nthose hopefully don't exist.\r\n\r\nFinally, there is small simplification to the visual check.","package":"vim-ruby-block-helpers.zip","4":"vim-ruby-block-helpers.zip","src_id":"25897","5":"25897","creation_date":"1521775520","6":"1521775520"},{"0":"5658","vim_version":"7.0","1":"7.0","script_version":"1.0.1","2":"1.0.1","version_comment":"Adjust visual mode, fix next block when on end\r\n\r\nPreviously, the visual mappings would always enter visual mode and never\r\nvisual line mode. For now, I am defaulting to always be in visual line\r\nmode. If this is a problem I can properly set apart the two mappings.\r\n\r\nAdditionally, if you are on an `end` line, then the next ruby block\r\nwould often not find a sibling, but instead would jump to the parent's\r\nsibling because it goes to the end of a block first. This makes sure it\r\nonly goes to block end if it is NOT on an end.","3":"Adjust visual mode, fix next block when on end\r\n\r\nPreviously, the visual mappings would always enter visual mode and never\r\nvisual line mode. For now, I am defaulting to always be in visual line\r\nmode. If this is a problem I can properly set apart the two mappings.\r\n\r\nAdditionally, if you are on an `end` line, then the next ruby block\r\nwould often not find a sibling, but instead would jump to the parent's\r\nsibling because it goes to the end of a block first. This makes sure it\r\nonly goes to block end if it is NOT on an end.","package":"trello-card-numbers.zip","4":"trello-card-numbers.zip","src_id":"25884","5":"25884","creation_date":"1521212058","6":"1521212058"},{"0":"5658","vim_version":"7.0","1":"7.0","script_version":"1.0.0","2":"1.0.0","version_comment":"Initial upload","3":"Initial upload","package":"vim-ruby-block-helpers-1.0.0.zip","4":"vim-ruby-block-helpers-1.0.0.zip","src_id":"25828","5":"25828","creation_date":"1518840754","6":"1518840754"}]},"5657":{"script_id":"5657","0":"5657","script_name":"JumpToVerticalBlock","1":"JumpToVerticalBlock","script_type":"utility","2":"utility","summary":"Like W \/ E, but vertically in the same column.","3":"Like W \/ E, but vertically in the same column.","description":"DESCRIPTION\r\nThere are far fewer vertical motions, especially those that maintain the\r\ncurrent column (which can be influenced via 'nostartofline'). Mostly, one uses\r\nk \/ j to move up \/ down. With 'relativenumber', this can already be quite\r\nprecise, but it's tedious to handle the [count] yourself. Many text formats\r\nhave a natural structure of different indents and line lengths. So, like word-\r\nand WORD-wise motion within a line, a notion of vertical \"blocks\", comprised\r\nof a sequence of non-whitespace characters under each other, can be helpful\r\nfor quick navigation.\r\n\r\nThis plugin provides ]w and ]W mappings that move vertically along the\r\ncurrent screen column, to the beginning or end of a block of non-whitespace\r\ncharacters. That is, they operate like W and E, but vertically.\r\n\r\nSEE ALSO\r\n- The JumpToVerticalOccurrence.vim plugin (vimscript #4841) has several\r\n  other vertical motions, like a vertical version of f{char}, and a move to\r\n  the next line with non-whitespace in the current column.\r\n- Check out the CountJump.vim plugin page (vimscript #3130) for a full list\r\n  of motions and text objects powered by it.\r\n\r\nRELATED WORKS\r\n- columnMove (vimscript #5402) moves to the end \/ start of vertical blocks of\r\n  non-whitespace; i.e. it has a single mapping combining ]w and ]W. So far\r\n  uses character columns instead of virtual screen ones. It inspired this\r\n  plugin.\r\n\r\nUSAGE\r\n]w                      To [count]'th next start of a block of non-whitespace\r\n                        characters at the current screen column.\r\n                        Like W, but vertically.\r\n]W                      To [count]'th next end of a block of non-whitespace\r\n                        characters at the current screen column.\r\n                        Like E, but vertically.\r\n[w                      To [count]'th previous start of a block of\r\n                        non-whitespace characters at the current screen column.\r\n                        Like B, but vertically.\r\n[W                      To [count]'th previous end of a block of\r\n                        non-whitespace characters at the current screen column.\r\n                        Like gE, but vertically.\r\n\r\nEXAMPLE\r\nWith the cursor starting at 0, it will move to positions 1, 2, ... when\r\ninvoking the command next to it:\r\n\r\n]w   3]w   ]W\r\n|    |     |\r\n0....0.....0.....3..2.\r\n\r\n1......\r\n..............\r\n..       ..1.    2...\r\n.......          ...1\r\n....\r\n        ........\r\n        .........1\r\n        ...2..\r\n2....1\r\n....\r\n...........3.....0..0\r\n                 |  |\r\n                 [w [W","4":"DESCRIPTION\r\nThere are far fewer vertical motions, especially those that maintain the\r\ncurrent column (which can be influenced via 'nostartofline'). Mostly, one uses\r\nk \/ j to move up \/ down. With 'relativenumber', this can already be quite\r\nprecise, but it's tedious to handle the [count] yourself. Many text formats\r\nhave a natural structure of different indents and line lengths. So, like word-\r\nand WORD-wise motion within a line, a notion of vertical \"blocks\", comprised\r\nof a sequence of non-whitespace characters under each other, can be helpful\r\nfor quick navigation.\r\n\r\nThis plugin provides ]w and ]W mappings that move vertically along the\r\ncurrent screen column, to the beginning or end of a block of non-whitespace\r\ncharacters. That is, they operate like W and E, but vertically.\r\n\r\nSEE ALSO\r\n- The JumpToVerticalOccurrence.vim plugin (vimscript #4841) has several\r\n  other vertical motions, like a vertical version of f{char}, and a move to\r\n  the next line with non-whitespace in the current column.\r\n- Check out the CountJump.vim plugin page (vimscript #3130) for a full list\r\n  of motions and text objects powered by it.\r\n\r\nRELATED WORKS\r\n- columnMove (vimscript #5402) moves to the end \/ start of vertical blocks of\r\n  non-whitespace; i.e. it has a single mapping combining ]w and ]W. So far\r\n  uses character columns instead of virtual screen ones. It inspired this\r\n  plugin.\r\n\r\nUSAGE\r\n]w                      To [count]'th next start of a block of non-whitespace\r\n                        characters at the current screen column.\r\n                        Like W, but vertically.\r\n]W                      To [count]'th next end of a block of non-whitespace\r\n                        characters at the current screen column.\r\n                        Like E, but vertically.\r\n[w                      To [count]'th previous start of a block of\r\n                        non-whitespace characters at the current screen column.\r\n                        Like B, but vertically.\r\n[W                      To [count]'th previous end of a block of\r\n                        non-whitespace characters at the current screen column.\r\n                        Like gE, but vertically.\r\n\r\nEXAMPLE\r\nWith the cursor starting at 0, it will move to positions 1, 2, ... when\r\ninvoking the command next to it:\r\n\r\n]w   3]w   ]W\r\n|    |     |\r\n0....0.....0.....3..2.\r\n\r\n1......\r\n..............\r\n..       ..1.    2...\r\n.......          ...1\r\n....\r\n        ........\r\n        .........1\r\n        ...2..\r\n2....1\r\n....\r\n...........3.....0..0\r\n                 |  |\r\n                 [w [W","install_details":"INSTALLATION\r\nThe code is hosted in a Git repo at\r\n    https:\/\/github.com\/inkarkat\/vim-JumpToVerticalBlock\r\nYou can use your favorite plugin manager, or \"git clone\" into a directory used\r\nfor Vim packages. Releases are on the \"stable\" branch, the latest unstable\r\ndevelopment snapshot on \"master\".\r\n\r\nThis script is also packaged as a vimball. If you have the \"gunzip\"\r\ndecompressor in your PATH, simply edit the *.vmb.gz package in Vim; otherwise,\r\ndecompress the archive first, e.g. using WinZip. Inside Vim, install by\r\nsourcing the vimball or via the :UseVimball command.\r\n    vim JumpToVerticalBlock*.vmb.gz\r\n    :so %\r\nTo uninstall, use the :RmVimball command.\r\n\r\nDEPENDENCIES\r\n- Requires Vim 7.0 or higher.\r\n- Requires the CountJump plugin (vimscript #3130), version 1.90 or higher.\r\n\r\nCONFIGURATION\r\nFor a permanent configuration, put the following commands into your vimrc:\r\n\r\nTo change the default motion mappings, use:\r\n    let g:JumpToVerticalBlock_ToBeginMapping = 'w'\r\n    let g:JumpToVerticalBlock_ToEndMapping = 'W'\r\nTo also change the [ \/ ] prefix to something else, follow the instructions for\r\nCountJump-remap-motions.","5":"INSTALLATION\r\nThe code is hosted in a Git repo at\r\n    https:\/\/github.com\/inkarkat\/vim-JumpToVerticalBlock\r\nYou can use your favorite plugin manager, or \"git clone\" into a directory used\r\nfor Vim packages. Releases are on the \"stable\" branch, the latest unstable\r\ndevelopment snapshot on \"master\".\r\n\r\nThis script is also packaged as a vimball. If you have the \"gunzip\"\r\ndecompressor in your PATH, simply edit the *.vmb.gz package in Vim; otherwise,\r\ndecompress the archive first, e.g. using WinZip. Inside Vim, install by\r\nsourcing the vimball or via the :UseVimball command.\r\n    vim JumpToVerticalBlock*.vmb.gz\r\n    :so %\r\nTo uninstall, use the :RmVimball command.\r\n\r\nDEPENDENCIES\r\n- Requires Vim 7.0 or higher.\r\n- Requires the CountJump plugin (vimscript #3130), version 1.90 or higher.\r\n\r\nCONFIGURATION\r\nFor a permanent configuration, put the following commands into your vimrc:\r\n\r\nTo change the default motion mappings, use:\r\n    let g:JumpToVerticalBlock_ToBeginMapping = 'w'\r\n    let g:JumpToVerticalBlock_ToEndMapping = 'W'\r\nTo also change the [ \/ ] prefix to something else, follow the instructions for\r\nCountJump-remap-motions.","first_name":"Ingo","6":"Ingo","last_name":"Karkat","7":"Karkat","releases":[{"0":"5657","vim_version":"7.0","1":"7.0","script_version":"1.00","2":"1.00","version_comment":"Initial upload","3":"Initial upload","package":"JumpToVerticalBlock-1.00.vmb.gz","4":"JumpToVerticalBlock-1.00.vmb.gz","src_id":"25824","5":"25824","creation_date":"1518371367","6":"1518371367"}]},"5656":{"script_id":"5656","0":"5656","script_name":"Toki Pona","1":"Toki Pona","script_type":"syntax","2":"syntax","summary":"syntax coloring and filetype settings for the Toki Pona minimalist conlang","3":"syntax coloring and filetype settings for the Toki Pona minimalist conlang","description":"A syntax highlighting utilities for the minimalist conlang (a.k.a. planned language,\r\nsuch as Esperanto). [1]\r\nThis plugin also performs a filetype detection and sets\r\nthe file with reasonable settings.\r\n\r\n\r\n== Usage ==\r\nOpen or create a file with a .tokipona or .tp extension.\r\n\r\nWrite in toki pona, i.e. using toki pona words.\r\nE.g. mi wile pana e ilo tawa sina.\r\nThe words should be colored according to the\r\nclasses prescribed in the official dictionary\r\nand the (configurable) criteria described in [1].\r\n\r\nYou might change and tweak the color schemes\r\napplied to the Toki Pona texts using commands\r\nsuch as\r\n:colo zellner\r\nor using Realcolors [2] to fine-tune individual colors,\r\nload experimental and cognitive color schemes,\r\nscrutinize Vim's syntax association to token at window cursor,\r\nand more.\r\n\r\n\r\n== A minimalistic template for Vim plugins ==\r\n\r\nAlso, the plugin is proposed as a very simple model for plugins.\r\n\r\nThe template is in fact a complete filetype plugin,\r\nwhich is a very general template.\r\nThus, variations and simpler plugin architectures\r\n(e.g. for general search or indentation)\r\nare obtained with relative ease.\r\n\r\nThe functionalities included, which might be associated to the main\r\ncomponents of a plugin, are:\r\n- Filetype detection (in plugin\/ftdetect\/tokipona.vim)\r\n- Filetype settings (in\r\n  plugin\/ftplugin\/tokipona\/[basic,folding].vim)\r\n- Filetype syntax (in syntax\/tokipona.vim)\r\n\r\nThe syntax file is rendered by a Python script\r\nthough analysis of the official\r\nToki Pona dictionary in [3], and according to configurable routines\r\ndescribed in [1].\r\nThe workings of Vim syntax highlighting and color schemes\r\nmight be promptly grasped by consulting [4].\r\n\r\n\r\n== Tweaking ==\r\n\r\nOne might obtain other syntax highlighting schemes\r\nfor Toki Pona by:\r\n\r\n1. editing the file ~\/.vim\/syntax\/tokipona.vim to change token\r\n   membership to syntax classes, association of syntax classes to visual\r\n   cues, and the comment format and visual characteristics.\r\n   (reloading a *.tokipona file with :e will apply the changes written)\r\n2. Changing the configurations or routines\r\n   in the Python script tokipona\/makeVimSyntax.py\r\n   found in https:\/\/github.com\/ttm\/tokipona\r\n3. Tweaking the colorschemes might more what you are looking for.\r\n   Take a look at Realcolors [2]. \r\n\r\n\r\n== TODO ==\r\n\r\n- Include POS tagging to achieve highlighting schemes that are\r\n  adequate to each sentence.\r\n- Include a Fuzzy mode in which a token is colored\r\nwith respect to their fuzzy set membership ratios.\r\n  * Each POS tag might have a membership function.\r\n  * One trivial case is when the membership ratios to each of the tokens\r\n    are equal and proportional to the number of classes. \r\n    E.g. let 'ale' have membership 1\/3 1\/3 1\/3 in the classes of adjective, noun\r\n    and number. If adjectives are associated with one color, nouns and\r\n    numbers with other two colors, the membership ratios yield\r\n    sound syntax coloring schemes in this very trivial sense.\r\n    It is a baseline.\r\n- Shape the tokipona Python package in\r\n  https:\/\/github.com\/ttm\/tokipona\r\n  into a package and integrate the\r\n  routines to be used (set, run, update files, update syntax and color\r\n  scheme being applied, etc) within Vim as functions, commands and\r\n  mappings.\r\n  * This might require integration with Realcolors [2]. \r\n- Inclusion of non-official words and corpus statistics into the\r\n  syntax and coloring schemes.\r\n- Include usage within Vim of the other resource in [1]: toki pona\r\n  wordnets, statistics obtained from the official vocabulary,\r\n  synthesis of texts (poems, sentences, etc).\r\n- Better relate this Vim plugin, the Python package, Realcolors\r\n  plugin, PRV and related endeavors.\r\n\r\n\r\nAcknowledgements\r\n----------------\r\nThis work is sponsored by FAPESP (project 2017\/05838-3) in a project lead by \r\nProfa. Dra. Maria Cristina Ferreira de Oliveira at VICG\/ICMC\/USP, S\u00c3\u00a3o Carlos, Brazil.\r\n\r\n\r\n[1]: Basic concepts and tools for the Toki Pona minimalist and\r\nconstructed language: description of the language and main issues;\r\nWordnet synsets; analysis of the vocabulary; synthesis and syntax\r\nhighlighting of texts.\r\nhttps:\/\/arxiv.org\/abs\/1712.09359\r\n\r\n[2]: Realcolors: Utilities for tweaking and creating 24-bit true color\r\nschemes for Vim at runtime.\r\nhttp:\/\/www.vim.org\/scripts\/script.php?script_id=5650\r\n\r\n[3]: Lang, Sonja. Toki Pona: The language of good. 2014.\r\n\r\n[4]: An anthropological account of the Vim text editor:\r\nfeatures and tweaks after 10 years of ouroboros.\r\nhttps:\/\/arxiv.org\/abs\/1712.06933\r\n\r\n=====================\r\n=====================\r\n","4":"A syntax highlighting utilities for the minimalist conlang (a.k.a. planned language,\r\nsuch as Esperanto). [1]\r\nThis plugin also performs a filetype detection and sets\r\nthe file with reasonable settings.\r\n\r\n\r\n== Usage ==\r\nOpen or create a file with a .tokipona or .tp extension.\r\n\r\nWrite in toki pona, i.e. using toki pona words.\r\nE.g. mi wile pana e ilo tawa sina.\r\nThe words should be colored according to the\r\nclasses prescribed in the official dictionary\r\nand the (configurable) criteria described in [1].\r\n\r\nYou might change and tweak the color schemes\r\napplied to the Toki Pona texts using commands\r\nsuch as\r\n:colo zellner\r\nor using Realcolors [2] to fine-tune individual colors,\r\nload experimental and cognitive color schemes,\r\nscrutinize Vim's syntax association to token at window cursor,\r\nand more.\r\n\r\n\r\n== A minimalistic template for Vim plugins ==\r\n\r\nAlso, the plugin is proposed as a very simple model for plugins.\r\n\r\nThe template is in fact a complete filetype plugin,\r\nwhich is a very general template.\r\nThus, variations and simpler plugin architectures\r\n(e.g. for general search or indentation)\r\nare obtained with relative ease.\r\n\r\nThe functionalities included, which might be associated to the main\r\ncomponents of a plugin, are:\r\n- Filetype detection (in plugin\/ftdetect\/tokipona.vim)\r\n- Filetype settings (in\r\n  plugin\/ftplugin\/tokipona\/[basic,folding].vim)\r\n- Filetype syntax (in syntax\/tokipona.vim)\r\n\r\nThe syntax file is rendered by a Python script\r\nthough analysis of the official\r\nToki Pona dictionary in [3], and according to configurable routines\r\ndescribed in [1].\r\nThe workings of Vim syntax highlighting and color schemes\r\nmight be promptly grasped by consulting [4].\r\n\r\n\r\n== Tweaking ==\r\n\r\nOne might obtain other syntax highlighting schemes\r\nfor Toki Pona by:\r\n\r\n1. editing the file ~\/.vim\/syntax\/tokipona.vim to change token\r\n   membership to syntax classes, association of syntax classes to visual\r\n   cues, and the comment format and visual characteristics.\r\n   (reloading a *.tokipona file with :e will apply the changes written)\r\n2. Changing the configurations or routines\r\n   in the Python script tokipona\/makeVimSyntax.py\r\n   found in https:\/\/github.com\/ttm\/tokipona\r\n3. Tweaking the colorschemes might more what you are looking for.\r\n   Take a look at Realcolors [2]. \r\n\r\n\r\n== TODO ==\r\n\r\n- Include POS tagging to achieve highlighting schemes that are\r\n  adequate to each sentence.\r\n- Include a Fuzzy mode in which a token is colored\r\nwith respect to their fuzzy set membership ratios.\r\n  * Each POS tag might have a membership function.\r\n  * One trivial case is when the membership ratios to each of the tokens\r\n    are equal and proportional to the number of classes. \r\n    E.g. let 'ale' have membership 1\/3 1\/3 1\/3 in the classes of adjective, noun\r\n    and number. If adjectives are associated with one color, nouns and\r\n    numbers with other two colors, the membership ratios yield\r\n    sound syntax coloring schemes in this very trivial sense.\r\n    It is a baseline.\r\n- Shape the tokipona Python package in\r\n  https:\/\/github.com\/ttm\/tokipona\r\n  into a package and integrate the\r\n  routines to be used (set, run, update files, update syntax and color\r\n  scheme being applied, etc) within Vim as functions, commands and\r\n  mappings.\r\n  * This might require integration with Realcolors [2]. \r\n- Inclusion of non-official words and corpus statistics into the\r\n  syntax and coloring schemes.\r\n- Include usage within Vim of the other resource in [1]: toki pona\r\n  wordnets, statistics obtained from the official vocabulary,\r\n  synthesis of texts (poems, sentences, etc).\r\n- Better relate this Vim plugin, the Python package, Realcolors\r\n  plugin, PRV and related endeavors.\r\n\r\n\r\nAcknowledgements\r\n----------------\r\nThis work is sponsored by FAPESP (project 2017\/05838-3) in a project lead by \r\nProfa. Dra. Maria Cristina Ferreira de Oliveira at VICG\/ICMC\/USP, S\u00c3\u00a3o Carlos, Brazil.\r\n\r\n\r\n[1]: Basic concepts and tools for the Toki Pona minimalist and\r\nconstructed language: description of the language and main issues;\r\nWordnet synsets; analysis of the vocabulary; synthesis and syntax\r\nhighlighting of texts.\r\nhttps:\/\/arxiv.org\/abs\/1712.09359\r\n\r\n[2]: Realcolors: Utilities for tweaking and creating 24-bit true color\r\nschemes for Vim at runtime.\r\nhttp:\/\/www.vim.org\/scripts\/script.php?script_id=5650\r\n\r\n[3]: Lang, Sonja. Toki Pona: The language of good. 2014.\r\n\r\n[4]: An anthropological account of the Vim text editor:\r\nfeatures and tweaks after 10 years of ouroboros.\r\nhttps:\/\/arxiv.org\/abs\/1712.06933\r\n\r\n=====================\r\n=====================\r\n","install_details":"Download the Vimball.\r\n\r\nInstall with:\r\n$ vim tokipona.vmb\r\nor\r\n:source tokipona.vmb\r\nif inside Vim.\r\n\r\n(it will place the files e.g. in .vim\/plugins\/\r\nI am not shure if and when \r\nyou shout restart Vim)\r\n\r\nYou might also install Toki Pona syntax by visiting\r\nhttps:\/\/github.com\/ttm\/tokipona\r\nand copying these files:\r\nsyntax\/tokipona.vim\r\nplugin\/ftdetect\/tokipona.vim\r\nplugin\/ftplugin\/tokipona\/folding.vim\r\nplugin\/ftplugin\/tokipona\/basic.vim\r\n\r\nto your .vim\/ or anywhere in you runtimepath.","5":"Download the Vimball.\r\n\r\nInstall with:\r\n$ vim tokipona.vmb\r\nor\r\n:source tokipona.vmb\r\nif inside Vim.\r\n\r\n(it will place the files e.g. in .vim\/plugins\/\r\nI am not shure if and when \r\nyou shout restart Vim)\r\n\r\nYou might also install Toki Pona syntax by visiting\r\nhttps:\/\/github.com\/ttm\/tokipona\r\nand copying these files:\r\nsyntax\/tokipona.vim\r\nplugin\/ftdetect\/tokipona.vim\r\nplugin\/ftplugin\/tokipona\/folding.vim\r\nplugin\/ftplugin\/tokipona\/basic.vim\r\n\r\nto your .vim\/ or anywhere in you runtimepath.","first_name":"Renato","6":"Renato","last_name":"Fabbri","7":"Fabbri","releases":[{"0":"5656","vim_version":"8.0","1":"8.0","script_version":"0.01b","2":"0.01b","version_comment":"Initial upload","3":"Initial upload","package":"tokipona.vmb","4":"tokipona.vmb","src_id":"25822","5":"25822","creation_date":"1518355923","6":"1518355923"}]},"5655":{"script_id":"5655","0":"5655","script_name":"vim-masquerade","1":"vim-masquerade","script_type":"utility","2":"utility","summary":"Tools to edit multiple selections","3":"Tools to edit multiple selections","description":"vim-masquerade provides wrapped operators to work with vim-multiselect. These operators edit texts as repeating sets of visual selection and calling the original operator for each multi-selected regions.\r\n\r\nLatest version: https:\/\/github.com\/machakann\/vim-masquerade","4":"vim-masquerade provides wrapped operators to work with vim-multiselect. These operators edit texts as repeating sets of visual selection and calling the original operator for each multi-selected regions.\r\n\r\nLatest version: https:\/\/github.com\/machakann\/vim-masquerade","install_details":"Unzip and just put all folders in your ~\/.vim.","5":"Unzip and just put all folders in your ~\/.vim.","first_name":"Masaaki","6":"Masaaki","last_name":"Nakamura","7":"Nakamura","releases":[{"0":"5655","vim_version":"8.0","1":"8.0","script_version":"0.5","2":"0.5","version_comment":"Initial upload","3":"Initial upload","package":"vim-masquerade-0.5.zip","4":"vim-masquerade-0.5.zip","src_id":"25819","5":"25819","creation_date":"1517829987","6":"1517829987"}]},"5654":{"script_id":"5654","0":"5654","script_name":"vim-multiselect","1":"vim-multiselect","script_type":"utility","2":"utility","summary":"A library for multiple selection","3":"A library for multiple selection","description":"vim-multiselect is a library to handle multiple selection areas in Vim text editor. This plugin only serves functions to select\/unselect multiple areas. The editing functions are supplied by other plugins. Check out \r\n\r\nLatest version: https:\/\/github.com\/machakann\/vim-multiselect\r\n\r\n","4":"vim-multiselect is a library to handle multiple selection areas in Vim text editor. This plugin only serves functions to select\/unselect multiple areas. The editing functions are supplied by other plugins. Check out \r\n\r\nLatest version: https:\/\/github.com\/machakann\/vim-multiselect\r\n\r\n","install_details":"Unzip and just put all folders in your ~\/.vim.","5":"Unzip and just put all folders in your ~\/.vim.","first_name":"Masaaki","6":"Masaaki","last_name":"Nakamura","7":"Nakamura","releases":[{"0":"5654","vim_version":"8.0","1":"8.0","script_version":"0.5","2":"0.5","version_comment":"Initial upload","3":"Initial upload","package":"vim-multiselect-0.5.zip","4":"vim-multiselect-0.5.zip","src_id":"25818","5":"25818","creation_date":"1517829688","6":"1517829688"}]},"5653":{"script_id":"5653","0":"5653","script_name":"vim-auf","1":"vim-auf","script_type":"utility","2":"utility","summary":"Format Your Lines And Be Reminded By Coloring","3":"Format Your Lines And Be Reminded By Coloring","description":"Actively developed at: https:\/\/github.com\/umitkablan\/vim-auf\r\n\r\nJIT format code with Auf on the fly and only your changes easily.\r\n\r\nAuf not only formats *only* the lines you edited but also will use highlighting to remind you:\r\n  - newly added lines highlighted; those are going to be formatted as you save\r\n  - wrong formatted lines are highlighted; those were already there and Auf won't touch them if you don't explicitly\r\n\r\n* Features in a Nutshell\r\n  - Works with basic command line formatters (clang-format, js-beautify etc.)\r\n  - Format only touched lines after a save - JITing.\r\n  - Avoid formatting with a bang :w! - accept as is.\r\n  - Configurable and sufficient highlighting - changed (to be formatted) lines, wrong-format lines.\r\n  - Already defined popular formatters for different filetypes.\r\n  - Pure VimScript.\r\n  - Automatic formatter selection based on formatter dot-files in project directory - use those settings.\r\n  - Vim settings (buffer or global) are respected and defined into formatter parameters.\r\n","4":"Actively developed at: https:\/\/github.com\/umitkablan\/vim-auf\r\n\r\nJIT format code with Auf on the fly and only your changes easily.\r\n\r\nAuf not only formats *only* the lines you edited but also will use highlighting to remind you:\r\n  - newly added lines highlighted; those are going to be formatted as you save\r\n  - wrong formatted lines are highlighted; those were already there and Auf won't touch them if you don't explicitly\r\n\r\n* Features in a Nutshell\r\n  - Works with basic command line formatters (clang-format, js-beautify etc.)\r\n  - Format only touched lines after a save - JITing.\r\n  - Avoid formatting with a bang :w! - accept as is.\r\n  - Configurable and sufficient highlighting - changed (to be formatted) lines, wrong-format lines.\r\n  - Already defined popular formatters for different filetypes.\r\n  - Pure VimScript.\r\n  - Automatic formatter selection based on formatter dot-files in project directory - use those settings.\r\n  - Vim settings (buffer or global) are respected and defined into formatter parameters.\r\n","install_details":"Old school way: Put it under plugins\/\r\nModern way: Use pathogen, vim-plug etc.\r\n\r\nAs the main logic of finding unsaved lines or filtering is built on diff-file processing, you need to install *diff(.exe), filterdiff(.exe), and patch(.exe)* utilities (some call it diff-utils). Windows users might need to install Cygwin with those diff-utils inside.\r\n\r\nAlso install command line utilities of the formatters you want. E.g. clang-format, jsbeautify..","5":"Old school way: Put it under plugins\/\r\nModern way: Use pathogen, vim-plug etc.\r\n\r\nAs the main logic of finding unsaved lines or filtering is built on diff-file processing, you need to install *diff(.exe), filterdiff(.exe), and patch(.exe)* utilities (some call it diff-utils). Windows users might need to install Cygwin with those diff-utils inside.\r\n\r\nAlso install command line utilities of the formatters you want. E.g. clang-format, jsbeautify..","first_name":"umit","6":"umit","last_name":"kablan","7":"kablan","releases":[{"0":"5653","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"vim-auf-1.0.tar.gz","4":"vim-auf-1.0.tar.gz","src_id":"25811","5":"25811","creation_date":"1517384026","6":"1517384026"}]},"5652":{"script_id":"5652","0":"5652","script_name":"vim-fetlang","1":"vim-fetlang","script_type":"syntax","2":"syntax","summary":"Vim language support for Fetlang, the fetish-themed programming language","3":"Vim language support for Fetlang, the fetish-themed programming language","description":"https:\/\/github.com\/kutsan\/vim-fetlang","4":"https:\/\/github.com\/kutsan\/vim-fetlang","install_details":"","5":"","first_name":"Kutsan","6":"Kutsan","last_name":"Kaplan","7":"Kaplan","releases":[{"0":"5652","vim_version":"7.0","1":"7.0","script_version":"2677c31","2":"2677c31","version_comment":"Initial upload","3":"Initial upload","package":"vim-fetlang-2677c31.zip","4":"vim-fetlang-2677c31.zip","src_id":"25808","5":"25808","creation_date":"1517311135","6":"1517311135"}]},"5651":{"script_id":"5651","0":"5651","script_name":"qt-support.vim","1":"qt-support.vim","script_type":"ftplugin","2":"ftplugin","summary":"Simple Qt support for Vim","3":"Simple Qt support for Vim","description":"Simple Qt support for Qt-based projects.\r\n\r\nMore details here: https:\/\/github.com\/fedorenchik\/qt-support.vim","4":"Simple Qt support for Qt-based projects.\r\n\r\nMore details here: https:\/\/github.com\/fedorenchik\/qt-support.vim","install_details":"Use your favourite package manager for Vim.\r\n\r\nIf you don't have a preferred installation method, I recommend using Vim's native package management support, simply copy and paste:\r\n\r\nmkdir -p ~\/.vim\/pack\/bundle\/start\r\ncd ~\/.vim\/pack\/bundle\/start\r\ngit clone https:\/\/github.com\/fedorenchik\/qt-support.vim.git\r\n","5":"Use your favourite package manager for Vim.\r\n\r\nIf you don't have a preferred installation method, I recommend using Vim's native package management support, simply copy and paste:\r\n\r\nmkdir -p ~\/.vim\/pack\/bundle\/start\r\ncd ~\/.vim\/pack\/bundle\/start\r\ngit clone https:\/\/github.com\/fedorenchik\/qt-support.vim.git\r\n","first_name":"Leonid","6":"Leonid","last_name":"Fedorenchik","7":"Fedorenchik","releases":[{"0":"5651","vim_version":"7.0","1":"7.0","script_version":"1.1","2":"1.1","version_comment":"* Support *.ui and *.ts files (as xml)\r\n* Use Qt indent settings in qmake\r\n* Add few more Qt macros","3":"* Support *.ui and *.ts files (as xml)\r\n* Use Qt indent settings in qmake\r\n* Add few more Qt macros","package":"qt-support.vim-1.1.zip","4":"qt-support.vim-1.1.zip","src_id":"25934","5":"25934","creation_date":"1524103583","6":"1524103583"},{"0":"5651","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"qt-support.vim-1.0.zip","4":"qt-support.vim-1.0.zip","src_id":"25806","5":"25806","creation_date":"1517201166","6":"1517201166"}]},"5650":{"script_id":"5650","0":"5650","script_name":"Realcolors","1":"Realcolors","script_type":"color scheme","2":"color scheme","summary":"Utilities for tweaking and creating 24-bit true color schemes for Vim at runtime","3":"Utilities for tweaking and creating 24-bit true color schemes for Vim at runtime","description":"THIS IS A VERY PRELIMINARY RELEASE TO UNDERSTAND vim.org\r\nAND START SHARING SOME ROUTINES\r\n\r\nFORECAST: I should upload a more organized version in a couple of hours\r\nor few days (max).\r\n(these are scripts I and only I am using)\r\n\r\n\r\nContext\r\n-----------\r\n\r\nRealcolors is a plugin to help you tweak and create color schemes.\r\nThis is useful for a number of reasons:\r\n* Colors influence how well you perform is different tasts [1].\r\n* There seems to be no serious study of using color palletes for syntax highlighting [2].\r\n* Each person has a unique sensibility and tolerance to the colors (e.g. red, blue...) [3].\r\n* Different contexts entail different color characteristics that are more suitable [3]. E.g. if you are presenting code you might want a more pleasant combination whereas if you are coding for many hours, you might want more stimulant color characteristics. If you are just skimming though files to know their content, you might want a color scheme that makes the content very evident.\r\n* One might want to experiment with the coloring possibilities.\r\n* One might want to create color schemes for private use or for sharing with others.\r\n* One might want to tweak favorite color schemes to fit their taste and\/or achieve a greater clarity.\r\n\r\n[1]: Mehta, R., & Zhu, R. J. (2009). Blue or red? Exploring the effect of\r\ncolor on cognitive task performances. Science, 323(5918), 1226-1229.)\r\n[2]: https:\/\/softwareengineering.stackexchange.com\/questions\/89936\/syntax-highlighting-color-scheme-studies\r\n[3]: Ware, Colin. Information visualization: perception for design. Elsevier, 2012.\r\n\r\n\r\nPlease visit the repository: https:\/\/github.com\/ttm\/vim\r\nspecially the plugin and plugin\/realcolors\/ directories.\r\n\r\n\r\nFunctionalities\r\n-------------------\r\n\r\nThe following functionalities are implemented (you might need to start\r\nRealcolors with i as explained below):\r\n\r\n* Change the Foreground and\/or Background colors of the char under cursor:\r\nc\r\n\r\n* Get the name of the syntax groups related to the char under cursor\r\n(these groups are related to colors, bold and underline):\r\ns\r\n\r\n* Make a detailed windows with the colors defined for your Vim,\r\nagainst your default colors (related to the Normal syntax group),\r\nwith:\r\nww, w1, w2 or w3,\r\n\r\n* Start\/Restart your coloring scheme with:\r\ni or I\r\n(the last reloads configuration scripts before restartin realcolors\r\nwith:\r\nnoremap I :w:runtime **\/*.vim:call InitializeColors()\r\n\r\n* Load a number of color schemes with the ApplyCS function\r\n(after initialization with the command above).\r\nChoose any XX color scheme in keys(ccs), then\r\n:call ApplyCS(ccs.XX, 'c')\r\n\r\nOther functionalities are skeched in the realcolor Vim files.\r\nSee realcolors\/mappings.vim and the other files for a complete\r\noverview.\r\nAdd new color schemes to the functions in realcolors\/cs.vim\r\n\r\n\r\nFurther information\r\n-------------------------\r\n\r\nThe following articles might help one to grasp and tweak\r\nthe Realcolors plugin:\r\n* \"An anthropological account of the Vim text editor: features and\r\n   tweaks after 10 years of usage\": https:\/\/arxiv.org\/abs\/1712.06933\r\n* \"Basic concepts and tools for the Toki Pona minimalist and\r\n   constructed language: Wordnet synsets; analysis of the vocabulary;\r\n   synthesis and syntax highlighting of texts\": https:\/\/arxiv.org\/abs\/1712.09359\r\n\r\n\r\n== A word about 24 bit true color ==\r\n\r\nThis plugins relies in using 24 bit true color (each color defined by\r\n8 bits, i.e. in [0,255] or [00,ff].\r\nAs far as I know, gVim uses true color by default.\r\nIn terminal Vim (which I use) I achieve true color by setting:\r\nset termguicolors\r\nin my vimrc.\r\nBecause I also use Byobu (screen) I also had to put these lines\r\nin the vimrc:\r\nlet &t_8f = \"\\[38;2;%lu;%lu;%lum\"\r\nlet &t_8b = \"\\[48;2;%lu;%lu;%lum\"\r\n\r\n\r\nAcknowledgements\r\n--------------------------\r\nThis work is sponsored by FAPESP (project 2017\/05838-3) in a project lead by\r\nProfa. Dra. Maria Cristina Ferreira de Oliveira at VICG\/ICMC\/USP, S\u00c3\u00a3o Carlos, Brazil.","4":"THIS IS A VERY PRELIMINARY RELEASE TO UNDERSTAND vim.org\r\nAND START SHARING SOME ROUTINES\r\n\r\nFORECAST: I should upload a more organized version in a couple of hours\r\nor few days (max).\r\n(these are scripts I and only I am using)\r\n\r\n\r\nContext\r\n-----------\r\n\r\nRealcolors is a plugin to help you tweak and create color schemes.\r\nThis is useful for a number of reasons:\r\n* Colors influence how well you perform is different tasts [1].\r\n* There seems to be no serious study of using color palletes for syntax highlighting [2].\r\n* Each person has a unique sensibility and tolerance to the colors (e.g. red, blue...) [3].\r\n* Different contexts entail different color characteristics that are more suitable [3]. E.g. if you are presenting code you might want a more pleasant combination whereas if you are coding for many hours, you might want more stimulant color characteristics. If you are just skimming though files to know their content, you might want a color scheme that makes the content very evident.\r\n* One might want to experiment with the coloring possibilities.\r\n* One might want to create color schemes for private use or for sharing with others.\r\n* One might want to tweak favorite color schemes to fit their taste and\/or achieve a greater clarity.\r\n\r\n[1]: Mehta, R., & Zhu, R. J. (2009). Blue or red? Exploring the effect of\r\ncolor on cognitive task performances. Science, 323(5918), 1226-1229.)\r\n[2]: https:\/\/softwareengineering.stackexchange.com\/questions\/89936\/syntax-highlighting-color-scheme-studies\r\n[3]: Ware, Colin. Information visualization: perception for design. Elsevier, 2012.\r\n\r\n\r\nPlease visit the repository: https:\/\/github.com\/ttm\/vim\r\nspecially the plugin and plugin\/realcolors\/ directories.\r\n\r\n\r\nFunctionalities\r\n-------------------\r\n\r\nThe following functionalities are implemented (you might need to start\r\nRealcolors with i as explained below):\r\n\r\n* Change the Foreground and\/or Background colors of the char under cursor:\r\nc\r\n\r\n* Get the name of the syntax groups related to the char under cursor\r\n(these groups are related to colors, bold and underline):\r\ns\r\n\r\n* Make a detailed windows with the colors defined for your Vim,\r\nagainst your default colors (related to the Normal syntax group),\r\nwith:\r\nww, w1, w2 or w3,\r\n\r\n* Start\/Restart your coloring scheme with:\r\ni or I\r\n(the last reloads configuration scripts before restartin realcolors\r\nwith:\r\nnoremap I :w:runtime **\/*.vim:call InitializeColors()\r\n\r\n* Load a number of color schemes with the ApplyCS function\r\n(after initialization with the command above).\r\nChoose any XX color scheme in keys(ccs), then\r\n:call ApplyCS(ccs.XX, 'c')\r\n\r\nOther functionalities are skeched in the realcolor Vim files.\r\nSee realcolors\/mappings.vim and the other files for a complete\r\noverview.\r\nAdd new color schemes to the functions in realcolors\/cs.vim\r\n\r\n\r\nFurther information\r\n-------------------------\r\n\r\nThe following articles might help one to grasp and tweak\r\nthe Realcolors plugin:\r\n* \"An anthropological account of the Vim text editor: features and\r\n   tweaks after 10 years of usage\": https:\/\/arxiv.org\/abs\/1712.06933\r\n* \"Basic concepts and tools for the Toki Pona minimalist and\r\n   constructed language: Wordnet synsets; analysis of the vocabulary;\r\n   synthesis and syntax highlighting of texts\": https:\/\/arxiv.org\/abs\/1712.09359\r\n\r\n\r\n== A word about 24 bit true color ==\r\n\r\nThis plugins relies in using 24 bit true color (each color defined by\r\n8 bits, i.e. in [0,255] or [00,ff].\r\nAs far as I know, gVim uses true color by default.\r\nIn terminal Vim (which I use) I achieve true color by setting:\r\nset termguicolors\r\nin my vimrc.\r\nBecause I also use Byobu (screen) I also had to put these lines\r\nin the vimrc:\r\nlet &t_8f = \"\\[38;2;%lu;%lu;%lum\"\r\nlet &t_8b = \"\\[48;2;%lu;%lu;%lum\"\r\n\r\n\r\nAcknowledgements\r\n--------------------------\r\nThis work is sponsored by FAPESP (project 2017\/05838-3) in a project lead by\r\nProfa. Dra. Maria Cristina Ferreira de Oliveira at VICG\/ICMC\/USP, S\u00c3\u00a3o Carlos, Brazil.","install_details":"Download the Vimball.\r\n\r\nInstall with:\r\n$ vim realcolors.vmb\r\n\r\nor inside vim with:\r\n\r\n:source realcolors.vmb\r\n\r\n(it will place the files e.g. in .vim\/plugins\/\r\nand next time you start Vim, it will have the\r\nrealcolors plugin installed)\r\n\r\nYou might also install realcolors with by visiting\r\nhttps:\/\/github.com\/ttm\/vim\r\nand copying these files:\r\nplugin\/realcolors.vim\r\nplugin\/realcolors\/cs.vim\r\nplugin\/realcolors\/dynamic.vim\r\nplugin\/realcolors\/mappings.vim\r\nplugin\/realcolors\/tools.vim\r\nplugin\/realcolors\/utils.vim\r\nplugin\/realcolors\/data\/realcolorsVimballInfo.txt\r\n\r\nto your .vim\/ or anywhere in you runtimepath.","5":"Download the Vimball.\r\n\r\nInstall with:\r\n$ vim realcolors.vmb\r\n\r\nor inside vim with:\r\n\r\n:source realcolors.vmb\r\n\r\n(it will place the files e.g. in .vim\/plugins\/\r\nand next time you start Vim, it will have the\r\nrealcolors plugin installed)\r\n\r\nYou might also install realcolors with by visiting\r\nhttps:\/\/github.com\/ttm\/vim\r\nand copying these files:\r\nplugin\/realcolors.vim\r\nplugin\/realcolors\/cs.vim\r\nplugin\/realcolors\/dynamic.vim\r\nplugin\/realcolors\/mappings.vim\r\nplugin\/realcolors\/tools.vim\r\nplugin\/realcolors\/utils.vim\r\nplugin\/realcolors\/data\/realcolorsVimballInfo.txt\r\n\r\nto your .vim\/ or anywhere in you runtimepath.","first_name":"Renato","6":"Renato","last_name":"Fabbri","7":"Fabbri","releases":[{"0":"5650","vim_version":"8.0","1":"8.0","script_version":"0.01b","2":"0.01b","version_comment":"Initial upload","3":"Initial upload","package":"realcolors.vmb","4":"realcolors.vmb","src_id":"25801","5":"25801","creation_date":"1516993638","6":"1516993638"}]},"5649":{"script_id":"5649","0":"5649","script_name":"Gruvbox 8","1":"Gruvbox 8","script_type":"color scheme","2":"color scheme","summary":"Simplified and optimized Gruvbox colorscheme","3":"Simplified and optimized Gruvbox colorscheme","description":"This is a simplified and optimized* version of Gruvbox that I have developed to address some issues I had with the official colorscheme.\r\n\r\nThese are the main differences compared to the official Gruvbox:\r\n\r\n- no plugin and filetype highlight groups to avoid messing up syntax highlighting after switching colorschemes;\r\n- reduced number of options;\r\n- all options are documented;\r\n- slightly different (and, IMHO, better) 256-color palette;\r\n- no 16-color version;\r\n- support for transparent backgrounds in terminals;\r\n- no autoload folder, no shell scripts;\r\n- up to date highlight group definitions (e.g., includes ToolbarLine and ToolbarButton).\r\n- generated by Colortemplate (https:\/\/github.com\/lifepillar\/vim-colortemplate), i.e., easily hackable.\r\n\r\n* Loads in ~1.5ms compared to the >9ms required by Gruvbox.","4":"This is a simplified and optimized* version of Gruvbox that I have developed to address some issues I had with the official colorscheme.\r\n\r\nThese are the main differences compared to the official Gruvbox:\r\n\r\n- no plugin and filetype highlight groups to avoid messing up syntax highlighting after switching colorschemes;\r\n- reduced number of options;\r\n- all options are documented;\r\n- slightly different (and, IMHO, better) 256-color palette;\r\n- no 16-color version;\r\n- support for transparent backgrounds in terminals;\r\n- no autoload folder, no shell scripts;\r\n- up to date highlight group definitions (e.g., includes ToolbarLine and ToolbarButton).\r\n- generated by Colortemplate (https:\/\/github.com\/lifepillar\/vim-colortemplate), i.e., easily hackable.\r\n\r\n* Loads in ~1.5ms compared to the >9ms required by Gruvbox.","install_details":"","5":"","first_name":"","6":"","last_name":"Lifepillar","7":"Lifepillar","releases":[{"0":"5649","vim_version":"7.0","1":"7.0","script_version":"0.1.0","2":"0.1.0","version_comment":"Define g:terminal_colors. Add options for activating filetype- and plugin-specific highlight groups (which are off by default).","3":"Define g:terminal_colors. Add options for activating filetype- and plugin-specific highlight groups (which are off by default).","package":"vim-gruvbox8-0.1.0.tar.gz","4":"vim-gruvbox8-0.1.0.tar.gz","src_id":"26167","5":"26167","creation_date":"1533427753","6":"1533427753"},{"0":"5649","vim_version":"7.0","1":"7.0","script_version":"0.0.1","2":"0.0.1","version_comment":"Initial upload","3":"Initial upload","package":"vim-gruvbox8-0.0.1.tar.gz","4":"vim-gruvbox8-0.0.1.tar.gz","src_id":"25799","5":"25799","creation_date":"1516740213","6":"1516740213"}]},"5648":{"script_id":"5648","0":"5648","script_name":"textfilter","1":"textfilter","script_type":"utility","2":"utility","summary":"Several useful text filters.","3":"Several useful text filters.","description":"Several useful text filters for text manipulations frequently used in \r\nprogramming, text processing and raw data manipulation: sort lines, number lines,\r\ncolumnate lists, split lines, sequence of numbers and others.\r\nGUI only, Windows and Linux \/ U**x. Please see the textfilter help for details.","4":"Several useful text filters for text manipulations frequently used in \r\nprogramming, text processing and raw data manipulation: sort lines, number lines,\r\ncolumnate lists, split lines, sequence of numbers and others.\r\nGUI only, Windows and Linux \/ U**x. Please see the textfilter help for details.","install_details":"The subdirectories in the zip archive  textfilter.zip  mirror the directory\r\nstructure which is needed below the local installation directory $HOME\/.vim\/ .\r\n\r\nCopy the zip archive  textfilter.zip to $HOME\/.vim and run\r\n\r\n  unzip textfilter.zip\r\n\r\nRestart gVim, create the help tags\r\n\r\n  :helptags $HOME\/.vim\/doc\/\r\n\r\nand look at the textfilter help with\r\n\r\n  :help textfilter\r\n","5":"The subdirectories in the zip archive  textfilter.zip  mirror the directory\r\nstructure which is needed below the local installation directory $HOME\/.vim\/ .\r\n\r\nCopy the zip archive  textfilter.zip to $HOME\/.vim and run\r\n\r\n  unzip textfilter.zip\r\n\r\nRestart gVim, create the help tags\r\n\r\n  :helptags $HOME\/.vim\/doc\/\r\n\r\nand look at the textfilter help with\r\n\r\n  :help textfilter\r\n","first_name":"Fritz","6":"Fritz","last_name":"Mehner","7":"Mehner","releases":[{"0":"5648","vim_version":"7.0","1":"7.0","script_version":"2.0","2":"2.0","version_comment":"Initial upload","3":"Initial upload","package":"textfilter.zip","4":"textfilter.zip","src_id":"25786","5":"25786","creation_date":"1516382698","6":"1516382698"}]},"5647":{"script_id":"5647","0":"5647","script_name":"jbuilder.vim","1":"jbuilder.vim","script_type":"syntax","2":"syntax","summary":"Jbuilder syntax hilighting","3":"Jbuilder syntax hilighting","description":"Syntax hilighting for Jane Streets OCaml build tool https:\/\/github.com\/janestreet\/jbuilder. \r\n\r\nGithub repository at https:\/\/github.com\/juanchanco\/vim-jbuilder","4":"Syntax hilighting for Jane Streets OCaml build tool https:\/\/github.com\/janestreet\/jbuilder. \r\n\r\nGithub repository at https:\/\/github.com\/juanchanco\/vim-jbuilder","install_details":"","5":"","first_name":"Juan","6":"Juan","last_name":"Chanco","7":"Chanco","releases":[{"0":"5647","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"jbuilder.tgz","4":"jbuilder.tgz","src_id":"25785","5":"25785","creation_date":"1516308961","6":"1516308961"}]},"5646":{"script_id":"5646","0":"5646","script_name":"Pickachu","1":"Pickachu","script_type":"utility","2":"utility","summary":"Color, date, and file picker for Vim using Zenity","3":"Color, date, and file picker for Vim using Zenity","description":"Pickachu\r\n---\r\n\r\n## Demo\r\n\r\n[Watch the GIF](https:\/\/gfycat.com\/AccomplishedTintedJoey)\r\n\r\n## Usage\r\n\r\n### Commands\r\n\r\n```\r\n:Pick\r\n```\r\n\r\nor...\r\n\r\n```\r\n:Pick [app] [optional: format]\r\n```\r\n\r\n**Note:** The full command of `:Pick` is `:Pickachu`. Use whatever feels more intuitive for you.\r\n\r\n**Note:** By default, `app` is set to `color` and `format` has different defaults depending on what app you choose. See more about defaults and how to change them in the [Configuration](#configuration) section\r\n\r\n**Availible Apps**:\r\n\r\n- **color** - The color-picker utility. Default format = `hex`.\r\n- **date** - The date-picker utility. Default format is `%m\/%d\/%Y`. More about formatting is discussed in the [Configuration](#configuration) section.\r\n- **file** - The file-picker utility. There are no format options for this utility.\r\n\r\n### Keyboard shortcuts\r\n\r\nBy default, there are no keyboard mappings to avoid conflicts with mappings you currently use.\r\n\r\nHowever, here are some ideas:\r\n\r\n**Mapping the default color picker to `alt+c`:**\r\n\r\n```\r\nmap  :Pickachu\r\n```\r\n\r\n**Mapping the file chooser to `alt+f`:**\r\n\r\n```\r\nmap  :Pickachu file\r\n```\r\n\r\n**Mapping the date chooser to `alt+d`:**\r\n\r\n```\r\nmap  :Pickachu date\r\n```\r\n\r\n## Configuration\r\n\r\n### Global Variables\r\n\r\n#### Default Color Format\r\n\r\n`let g:pickachu_default_color_format = \"hex\"`\r\n\r\n**Availible color formats are:**\r\n\r\n- hex\r\n- rgb\r\n- rgba\r\n\r\n#### Default Date Format:\r\n\r\n`let g:pickachu_default_date_format = \"%m\/%d\/%Y\"`\r\n\r\nDate formatting is done through [Python datetime](https:\/\/docs.python.org\/2\/library\/datetime.html).\r\n\r\n### KDE \/ Qt5 \/ Qarma support\r\n\r\nIf you are a KDE and\/or would rather use Qt5's color picker, install `qarma`.\r\n\r\nAfter doing so, add the following line to your configuration:\r\n\r\n`let g:pickachu_default_command = \"qarma\"`\r\n","4":"Pickachu\r\n---\r\n\r\n## Demo\r\n\r\n[Watch the GIF](https:\/\/gfycat.com\/AccomplishedTintedJoey)\r\n\r\n## Usage\r\n\r\n### Commands\r\n\r\n```\r\n:Pick\r\n```\r\n\r\nor...\r\n\r\n```\r\n:Pick [app] [optional: format]\r\n```\r\n\r\n**Note:** The full command of `:Pick` is `:Pickachu`. Use whatever feels more intuitive for you.\r\n\r\n**Note:** By default, `app` is set to `color` and `format` has different defaults depending on what app you choose. See more about defaults and how to change them in the [Configuration](#configuration) section\r\n\r\n**Availible Apps**:\r\n\r\n- **color** - The color-picker utility. Default format = `hex`.\r\n- **date** - The date-picker utility. Default format is `%m\/%d\/%Y`. More about formatting is discussed in the [Configuration](#configuration) section.\r\n- **file** - The file-picker utility. There are no format options for this utility.\r\n\r\n### Keyboard shortcuts\r\n\r\nBy default, there are no keyboard mappings to avoid conflicts with mappings you currently use.\r\n\r\nHowever, here are some ideas:\r\n\r\n**Mapping the default color picker to `alt+c`:**\r\n\r\n```\r\nmap  :Pickachu\r\n```\r\n\r\n**Mapping the file chooser to `alt+f`:**\r\n\r\n```\r\nmap  :Pickachu file\r\n```\r\n\r\n**Mapping the date chooser to `alt+d`:**\r\n\r\n```\r\nmap  :Pickachu date\r\n```\r\n\r\n## Configuration\r\n\r\n### Global Variables\r\n\r\n#### Default Color Format\r\n\r\n`let g:pickachu_default_color_format = \"hex\"`\r\n\r\n**Availible color formats are:**\r\n\r\n- hex\r\n- rgb\r\n- rgba\r\n\r\n#### Default Date Format:\r\n\r\n`let g:pickachu_default_date_format = \"%m\/%d\/%Y\"`\r\n\r\nDate formatting is done through [Python datetime](https:\/\/docs.python.org\/2\/library\/datetime.html).\r\n\r\n### KDE \/ Qt5 \/ Qarma support\r\n\r\nIf you are a KDE and\/or would rather use Qt5's color picker, install `qarma`.\r\n\r\nAfter doing so, add the following line to your configuration:\r\n\r\n`let g:pickachu_default_command = \"qarma\"`\r\n","install_details":"**Notes**: \r\n- You must have a Vim installation with Python3 support. If you're using NeoVim, you can simply type `pip3 install neovim`.\r\n- You must have Zenity installed on your computer. On most Linux operating systems, this is already installed.\r\n- If you're on a Mac, there may still be hope. [Here is a guide on installing Zenity with Homebrew on Mac](https:\/\/brewinstall.org\/install-zenity-on-mac-with-brew\/)\r\n\r\n### Plug\r\n\r\nAdd this line to your plugin loop:\r\n\r\n```\r\nPlug 'DougBeney\/pickachu'\r\n```\r\n\r\n### Pathogen\r\n\r\n```\r\ngit clone https:\/\/github.com\/DougBeney\/pickachu.git ~\/.vim\/bundle\/nerdtree\r\n```\r\n\r\n### Apt-Vim\r\n\r\n```\r\napt-vim install -y https:\/\/github.com\/DougBeney\/pickachu.git\r\n```","5":"**Notes**: \r\n- You must have a Vim installation with Python3 support. If you're using NeoVim, you can simply type `pip3 install neovim`.\r\n- You must have Zenity installed on your computer. On most Linux operating systems, this is already installed.\r\n- If you're on a Mac, there may still be hope. [Here is a guide on installing Zenity with Homebrew on Mac](https:\/\/brewinstall.org\/install-zenity-on-mac-with-brew\/)\r\n\r\n### Plug\r\n\r\nAdd this line to your plugin loop:\r\n\r\n```\r\nPlug 'DougBeney\/pickachu'\r\n```\r\n\r\n### Pathogen\r\n\r\n```\r\ngit clone https:\/\/github.com\/DougBeney\/pickachu.git ~\/.vim\/bundle\/nerdtree\r\n```\r\n\r\n### Apt-Vim\r\n\r\n```\r\napt-vim install -y https:\/\/github.com\/DougBeney\/pickachu.git\r\n```","first_name":"Doug","6":"Doug","last_name":"Beney","7":"Beney","releases":[{"0":"5646","vim_version":"7.0","1":"7.0","script_version":"0.0.1","2":"0.0.1","version_comment":"Initial upload","3":"Initial upload","package":"pickachu-master.zip","4":"pickachu-master.zip","src_id":"25784","5":"25784","creation_date":"1516298613","6":"1516298613"}]},"5645":{"script_id":"5645","0":"5645","script_name":"cmod.vim","1":"cmod.vim","script_type":"syntax","2":"syntax","summary":"Cmod syntax colouring (Pike development)","3":"Cmod syntax colouring (Pike development)","description":"Supports Cmod files, including embedded Autodoc formatting.","4":"Supports Cmod files, including embedded Autodoc formatting.","install_details":"You need a line in filetype.vim (or .vimrc) that reads:\r\nau BufNewFile,BufRead *.cmod                     setf cmod\r\n\r\nIt needs autodoc.vim (vimscript #5641) too (or comment out the include).\r\nIt's probably simplest to just put this file in your ~\/.vim dir, which (by default) is at the top of your runtimepath.\r\nOn my system I install both cmod.vim and autodoc.vim in \/usr\/share\/vim\/vim80\/syntax.\r\nIf you don't have matchit, simply comment out the corresponding line in cmod.vim referencing it (if you do, you lose if\/then\/else\/elif\/endif cycling; the rest will work fine).\r\n\r\nTo edit pike files, you can use pike.vim (vimscript #5640).","5":"You need a line in filetype.vim (or .vimrc) that reads:\r\nau BufNewFile,BufRead *.cmod                     setf cmod\r\n\r\nIt needs autodoc.vim (vimscript #5641) too (or comment out the include).\r\nIt's probably simplest to just put this file in your ~\/.vim dir, which (by default) is at the top of your runtimepath.\r\nOn my system I install both cmod.vim and autodoc.vim in \/usr\/share\/vim\/vim80\/syntax.\r\nIf you don't have matchit, simply comment out the corresponding line in cmod.vim referencing it (if you do, you lose if\/then\/else\/elif\/endif cycling; the rest will work fine).\r\n\r\nTo edit pike files, you can use pike.vim (vimscript #5640).","first_name":"Stephen R.","6":"Stephen R.","last_name":"van den Berg","7":"van den Berg","releases":[{"0":"5645","vim_version":"7.0","1":"7.0","script_version":"2.3","2":"2.3","version_comment":"Avoid triggering embedded autodoc on every exclamation mark.","3":"Avoid triggering embedded autodoc on every exclamation mark.","package":"cmod.vim","4":"cmod.vim","src_id":"25782","5":"25782","creation_date":"1516280560","6":"1516280560"},{"0":"5645","vim_version":"7.0","1":"7.0","script_version":"2.2.1b","2":"2.2.1b","version_comment":"Added a lot of keywords.","3":"Added a lot of keywords.","package":"cmod.vim","4":"cmod.vim","src_id":"25780","5":"25780","creation_date":"1516277644","6":"1516277644"},{"0":"5645","vim_version":"7.0","1":"7.0","script_version":"2.2.1a","2":"2.2.1a","version_comment":"Workaround for bug in matchit.","3":"Workaround for bug in matchit.","package":"cmod.vim","4":"cmod.vim","src_id":"25779","5":"25779","creation_date":"1516269734","6":"1516269734"},{"0":"5645","vim_version":"7.0","1":"7.0","script_version":"2.2.1","2":"2.2.1","version_comment":"Initial upload","3":"Initial upload","package":"cmod.vim","4":"cmod.vim","src_id":"25777","5":"25777","creation_date":"1516268359","6":"1516268359"}]},"5644":{"script_id":"5644","0":"5644","script_name":"If I Only...","1":"If I Only...","script_type":"utility","2":"utility","summary":"An only slightly smarter :only","3":"An only slightly smarter :only","description":"If I Only... is an only slightly smarter :only.\r\n\r\nIf there are any unmodifiable buffers open (NERDTree, :Gstatus, quickfix window, etc.), close them leaving any modifiable buffers alone. If there are only modifiable splits open, make the current one the only one\u00e2\u0080\u0094i.e., call plain old :only. If you are in an unmodifiable buffer, jump to the first modifiable one (this last point is configurable; see :help ifionly).\r\n\r\nIf invoking :IfIOnly leaves one buffer, calling it again to bring back any windows that were closed (ie, it acts as a poor man's WinZoom. This is available until quitting Vim.\r\n\r\nUsage\r\n\r\nThere is only one command (:IfIOnly) and one mapping (O).\r\n\r\nI would suggest using an even simpler mapping. Personally, I use L.\r\n\r\nI made this because my default vim state is to have two buffers open, side-by-side. Sometimes I'll find myself in a position where git status, the quickfix window, and sometimes even NERDTree--(or, ahem the twiggy window) are all open and I want to quickly get back to my default state in one or two keystokes.\r\n\r\nIf this sounds useful to you yet you like to have something like NERDTree open at all times, g:ifionly_filetypes can be set in your vimrc. For example:\r\n\r\nlet g:ifionly_filetypes = ['nerdtree']\r\n\r\nDevelopment is done at https:\/\/github.com\/sodapopcan\/vim-ifionly\r\n\r\nIf I Only...'s namesake is a song by Toronto, ON band Do Make Say Think.","4":"If I Only... is an only slightly smarter :only.\r\n\r\nIf there are any unmodifiable buffers open (NERDTree, :Gstatus, quickfix window, etc.), close them leaving any modifiable buffers alone. If there are only modifiable splits open, make the current one the only one\u00e2\u0080\u0094i.e., call plain old :only. If you are in an unmodifiable buffer, jump to the first modifiable one (this last point is configurable; see :help ifionly).\r\n\r\nIf invoking :IfIOnly leaves one buffer, calling it again to bring back any windows that were closed (ie, it acts as a poor man's WinZoom. This is available until quitting Vim.\r\n\r\nUsage\r\n\r\nThere is only one command (:IfIOnly) and one mapping (O).\r\n\r\nI would suggest using an even simpler mapping. Personally, I use L.\r\n\r\nI made this because my default vim state is to have two buffers open, side-by-side. Sometimes I'll find myself in a position where git status, the quickfix window, and sometimes even NERDTree--(or, ahem the twiggy window) are all open and I want to quickly get back to my default state in one or two keystokes.\r\n\r\nIf this sounds useful to you yet you like to have something like NERDTree open at all times, g:ifionly_filetypes can be set in your vimrc. For example:\r\n\r\nlet g:ifionly_filetypes = ['nerdtree']\r\n\r\nDevelopment is done at https:\/\/github.com\/sodapopcan\/vim-ifionly\r\n\r\nIf I Only...'s namesake is a song by Toronto, ON band Do Make Say Think.","install_details":"","5":"","first_name":"Andrew","6":"Andrew","last_name":"Haust","7":"Haust","releases":[{"0":"5644","vim_version":"7.0","1":"7.0","script_version":"1.1","2":"1.1","version_comment":"Bring back recently closed splits","3":"Bring back recently closed splits","package":"vim-ifionly.zip","4":"vim-ifionly.zip","src_id":"26524","5":"26524","creation_date":"1559857078","6":"1559857078"},{"0":"5644","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"ifionly.zip","4":"ifionly.zip","src_id":"25775","5":"25775","creation_date":"1516202681","6":"1516202681"}]},"5643":{"script_id":"5643","0":"5643","script_name":"twiggy","1":"twiggy","script_type":"utility","2":"utility","summary":"Git branch management","3":"Git branch management","description":"+++Maintain your bearings while branching with git.+++\r\n\r\nTwiggy is a fugitive extension that loads, decorates and sorts(!) git branches into an interactive buffer. It provides basic merge and rebase support, stashing, and some other goodies.\r\n\r\nSee https:\/\/github.com\/sodapopcan\/vim-twiggy for details.","4":"+++Maintain your bearings while branching with git.+++\r\n\r\nTwiggy is a fugitive extension that loads, decorates and sorts(!) git branches into an interactive buffer. It provides basic merge and rebase support, stashing, and some other goodies.\r\n\r\nSee https:\/\/github.com\/sodapopcan\/vim-twiggy for details.","install_details":"I personally recommend vim-plug, but NeoBundle, Vundle or pathogen are all fine options as well.\r\n\r\nYou must have fugitive installed!","5":"I personally recommend vim-plug, but NeoBundle, Vundle or pathogen are all fine options as well.\r\n\r\nYou must have fugitive installed!","first_name":"Andrew","6":"Andrew","last_name":"Haust","7":"Haust","releases":[{"0":"5643","vim_version":"7.0","1":"7.0","script_version":"0.3","2":"0.3","version_comment":"Initial upload","3":"Initial upload","package":"twiggy.zip","4":"twiggy.zip","src_id":"25769","5":"25769","creation_date":"1516053051","6":"1516053051"}]},"5641":{"script_id":"5641","0":"5641","script_name":"autodoc.vim","1":"autodoc.vim","script_type":"syntax","2":"syntax","summary":"Autodoc syntax colouring","3":"Autodoc syntax colouring","description":"Autodoc syntax colouring; used as an include for embedded colouring from inside pike.vim (vimscript #5640) and cmod.vim (vimscript #5645).","4":"Autodoc syntax colouring; used as an include for embedded colouring from inside pike.vim (vimscript #5640) and cmod.vim (vimscript #5645).","install_details":"","5":"","first_name":"Stephen R.","6":"Stephen R.","last_name":"van den Berg","7":"van den Berg","releases":[{"0":"5641","vim_version":"7.0","1":"7.0","script_version":"2.3","2":"2.3","version_comment":"Bump version number to stay in sync with pike.vim and cmod.vim.","3":"Bump version number to stay in sync with pike.vim and cmod.vim.","package":"autodoc.vim","4":"autodoc.vim","src_id":"25783","5":"25783","creation_date":"1516280597","6":"1516280597"},{"0":"5641","vim_version":"7.0","1":"7.0","script_version":"2.2.1","2":"2.2.1","version_comment":"Added error highlights for misspelled keywords.","3":"Added error highlights for misspelled keywords.","package":"autodoc.vim","4":"autodoc.vim","src_id":"25774","5":"25774","creation_date":"1516194983","6":"1516194983"},{"0":"5641","vim_version":"7.0","1":"7.0","script_version":"2.2","2":"2.2","version_comment":"Use SpecialComment colour to mark the ! of autodoc.","3":"Use SpecialComment colour to mark the ! of autodoc.","package":"autodoc.vim","4":"autodoc.vim","src_id":"25771","5":"25771","creation_date":"1516139644","6":"1516139644"},{"0":"5641","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"autodoc.vim","4":"autodoc.vim","src_id":"25765","5":"25765","creation_date":"1516025243","6":"1516025243"}]},"5640":{"script_id":"5640","0":"5640","script_name":"pike.vim","1":"pike.vim","script_type":"syntax","2":"syntax","summary":"New and improved Pike syntax colouring","3":"New and improved Pike syntax colouring","description":"This Pike syntax colouring definition supersedes any older ones.\r\nIt contains support for embedded SQL and embedded Autodoc.\r\n\r\nThis version started with the C syntax file, fixes several bugs in that file, speeds it up, and adds Pike syntax recognition (including parens for arrays, multisets and mappings), including mismatched paren highlights for all of the above.\r\nIt also supports cycling through preprocessor if\/else\/elif\/endif chains.\r\n\r\nIt's up-to-date for Pike 8.1","4":"This Pike syntax colouring definition supersedes any older ones.\r\nIt contains support for embedded SQL and embedded Autodoc.\r\n\r\nThis version started with the C syntax file, fixes several bugs in that file, speeds it up, and adds Pike syntax recognition (including parens for arrays, multisets and mappings), including mismatched paren highlights for all of the above.\r\nIt also supports cycling through preprocessor if\/else\/elif\/endif chains.\r\n\r\nIt's up-to-date for Pike 8.1","install_details":"It needs autodoc.vim (vimscript #5641) too (or comment out the include).\r\nIt's probably simplest to just put this file in your ~\/.vim dir, which (by default) is at the top of your runtimepath.\r\nThe file references sqloracle.vim (vimscript #2371) and the matchit (vimscript #39) package; both should be available and included already in standard Vim 8.0+ installs.\r\nOn my system I install both pike.vim and autodoc.vim in \/usr\/share\/vim\/vim80\/syntax.\r\nIf you don't have sqloracle.vim or matchit, simply comment out the two corresponding lines in pike.vim referencing those (if you do, you lose embedded SQL highlighting and if\/then\/else\/elif\/endif cycling; the rest will work fine).\r\n\r\nTo edit Cmod files, you can use cmod.vim (vimscript #5645).","5":"It needs autodoc.vim (vimscript #5641) too (or comment out the include).\r\nIt's probably simplest to just put this file in your ~\/.vim dir, which (by default) is at the top of your runtimepath.\r\nThe file references sqloracle.vim (vimscript #2371) and the matchit (vimscript #39) package; both should be available and included already in standard Vim 8.0+ installs.\r\nOn my system I install both pike.vim and autodoc.vim in \/usr\/share\/vim\/vim80\/syntax.\r\nIf you don't have sqloracle.vim or matchit, simply comment out the two corresponding lines in pike.vim referencing those (if you do, you lose embedded SQL highlighting and if\/then\/else\/elif\/endif cycling; the rest will work fine).\r\n\r\nTo edit Cmod files, you can use cmod.vim (vimscript #5645).","first_name":"Stephen R.","6":"Stephen R.","last_name":"van den Berg","7":"van den Berg","releases":[{"0":"5640","vim_version":"7.0","1":"7.0","script_version":"2.3","2":"2.3","version_comment":"Avoid triggering embedded autodoc on every exclamation mark.","3":"Avoid triggering embedded autodoc on every exclamation mark.","package":"pike.vim","4":"pike.vim","src_id":"25781","5":"25781","creation_date":"1516280529","6":"1516280529"},{"0":"5640","vim_version":"7.0","1":"7.0","script_version":"2.2.1","2":"2.2.1","version_comment":"Cosmetic change, allowing easier reuse of the syntax file.","3":"Cosmetic change, allowing easier reuse of the syntax file.","package":"pike.vim","4":"pike.vim","src_id":"25778","5":"25778","creation_date":"1516268439","6":"1516268439"},{"0":"5640","vim_version":"7.0","1":"7.0","script_version":"2.2","2":"2.2","version_comment":"Improved preprocessor directives colouring.","3":"Improved preprocessor directives colouring.","package":"pike.vim","4":"pike.vim","src_id":"25770","5":"25770","creation_date":"1516139565","6":"1516139565"},{"0":"5640","vim_version":"7.0","1":"7.0","script_version":"2.1","2":"2.1","version_comment":"Initial upload","3":"Initial upload","package":"pike.vim","4":"pike.vim","src_id":"25764","5":"25764","creation_date":"1516025133","6":"1516025133"}]},"5635":{"script_id":"5635","0":"5635","script_name":"Hearts of Iron Syntax","1":"Hearts of Iron Syntax","script_type":"syntax","2":"syntax","summary":"Add syntax highlight for Hearts of Iron files","3":"Add syntax highlight for Hearts of Iron files","description":"Add syntax support of Hearts of Iron files.\r\n\r\nThe script highlights txt files in Hearts of Iron folder.\r\n\r\n\r\nSteam workshop at http:\/\/steamcommunity.com\/sharedfiles\/filedetails\/?id=1255330994\r\n\r\nThe repository of this mod is at https:\/\/github.com\/gqqnbig\/VimHoiSupport","4":"Add syntax support of Hearts of Iron files.\r\n\r\nThe script highlights txt files in Hearts of Iron folder.\r\n\r\n\r\nSteam workshop at http:\/\/steamcommunity.com\/sharedfiles\/filedetails\/?id=1255330994\r\n\r\nThe repository of this mod is at https:\/\/github.com\/gqqnbig\/VimHoiSupport","install_details":"Download and unzip the file, put all folders to $HOME\/vimfiles folder.\r\n\r\nOr install from VundleVim\r\n\r\nPut the following to your vimrc\r\n\r\nPlugin 'gqqnbig\/VimHoiSupport'\r\n\r\n","5":"Download and unzip the file, put all folders to $HOME\/vimfiles folder.\r\n\r\nOr install from VundleVim\r\n\r\nPut the following to your vimrc\r\n\r\nPlugin 'gqqnbig\/VimHoiSupport'\r\n\r\n","first_name":"gqq","6":"gqq","last_name":"nbig","7":"nbig","releases":[{"0":"5635","vim_version":"8.0","1":"8.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"vimfiles.zip","4":"vimfiles.zip","src_id":"25748","5":"25748","creation_date":"1514955442","6":"1514955442"}]},"5634":{"script_id":"5634","0":"5634","script_name":"debugstring","1":"debugstring","script_type":"utility","2":"utility","summary":"Debug printf()-style at the speed of light ","3":"Debug printf()-style at the speed of light ","description":"For a detailed and more up-to-date description of the plugin refer to the Github Page (https:\/\/github.com\/bergercookie\/vim-debugstring)\r\ndebugstring aims to automate standard debugging operations (e.g., segfaults). It does that by facilitating the ubiquitous printf()-debugging i.e., scatter logging statements around the various code snippets that you want to test.\r\n\r\nThe form and syntax of the logging statements target the language at hand (e.g., use printf() in C\/C++ but puts() in Ruby)\r\n\r\nFor a more detailed outline of debugstring check the docs (:h debugstring)","4":"For a detailed and more up-to-date description of the plugin refer to the Github Page (https:\/\/github.com\/bergercookie\/vim-debugstring)\r\ndebugstring aims to automate standard debugging operations (e.g., segfaults). It does that by facilitating the ubiquitous printf()-debugging i.e., scatter logging statements around the various code snippets that you want to test.\r\n\r\nThe form and syntax of the logging statements target the language at hand (e.g., use printf() in C\/C++ but puts() in Ruby)\r\n\r\nFor a more detailed outline of debugstring check the docs (:h debugstring)","install_details":"Using a runtimepath\/package manage\r\n\r\nI would personally recommend using Pathogen for installing the plugin but any other installation method (e.g., Vundle) should do the job (if not please raise an issue on Github)\r\n\r\ngit clone https:\/\/github.com\/bergercookie\/vim-debustring.git ~\/.vim\/bundle\/vim-debugstring\r\n\r\nManual installation\r\n\r\nCopy the plugin files into the corresponding directories under ${HOME}\/.vim (Linux) or $VIMFILES (Windows).\r\n","5":"Using a runtimepath\/package manage\r\n\r\nI would personally recommend using Pathogen for installing the plugin but any other installation method (e.g., Vundle) should do the job (if not please raise an issue on Github)\r\n\r\ngit clone https:\/\/github.com\/bergercookie\/vim-debustring.git ~\/.vim\/bundle\/vim-debugstring\r\n\r\nManual installation\r\n\r\nCopy the plugin files into the corresponding directories under ${HOME}\/.vim (Linux) or $VIMFILES (Windows).\r\n","first_name":"Nikos","6":"Nikos","last_name":"Koukis","7":"Koukis","releases":[{"0":"5634","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"debugstring.tar.gz","4":"debugstring.tar.gz","src_id":"25747","5":"25747","creation_date":"1514853758","6":"1514853758"}]},"5633":{"script_id":"5633","0":"5633","script_name":"readline.vim","1":"readline.vim","script_type":"utility","2":"utility","summary":"Readline-style mappings for command-line mode","3":"Readline-style mappings for command-line mode","description":"To get the latest version it is recommended to download from Github instead: https:\/\/github.com\/ryvnf\/readline.vim\r\n\r\nReadline is a library used for implementing line editing across many command-line tools (including `bash` and other shells and interpreters).  Readline ships with a default set of key-bindings that you are probably already familiar with.  The Readline default bindings is a mixture of traditional Unix and Emacs bindings.\r\n\r\nThis plugins implements a subset of Readline's default keyboard commands to Vim's command-line mode.  Mappings available include deletion and navigation by words and other useful stuff.\r\n\r\nWhat makes this plugin different from similar plugins is that it implements a larger subset of the Readline mappings, and each command is carefully implemented to behave exactly like in Readline.\r\n\r\nThe word movement and deletion commands have different behavior between Vim and Readline.  The biggest difference is that in Readline punctuation is always skipped when searching for a word boundary.  Another difference is that _ (underscore) is treated as a word delimiter.  This plugin implements the Readline behavior for word movement and deletion commands.\r\n\r\nFollowing is a summary of the mappings implemented by this plugin:\r\n\r\nC-b                                  Move backward\r\nC-f                                   Move forward\r\nM-b                                  Move one word backward\r\nM-f                                   Move one word forward\r\nC-a                                  Move to start of line\r\nC-e                                  Move to end of line\r\nC-d                                  Delete character\r\nM-Backspace                   Rubout word\r\nM-d                                  Delete word\r\nC-w                                  Rubout space-delimited word\r\nC-u, C-x Backspace          Delete to start of line\r\nC-k                                   Deleted to end of line (can be disabled with g:readline_ctrl_k)\r\nC-y                                   Yank (paste) previously deleted text\r\nC-t                                    Transpose characters\r\nM-t                                    Transpose words\r\nM-u                                   Make word UPPERCASE\r\nM-l                                    Make word lowercase\r\nM-c                                   Make word Capitalized\r\nM-#                                   Comment out and execute the command-line\r\nM-=, M-?                           List possible completions\r\nM-*                                    Insert possible completions\r\nC-x C-e                              Open command-line window (like default Vim C-f)\r\n\r\nThe word boundaries for movement and deletion differ between Vim and Readline.  The biggest difference is that in Readline punctuation is always skipped when searching for a word boundary.  Another difference is that _ (underscore) is treated as a word delimiter.  This plugin implements the Readline behaivor for word movement and deletion commands.\r\n\r\nThis plugin does not use the Meta-key directly, because it causes conflicts with inserting accented characters on some keyboard layouts.  Instead Meta-key mappings can only be accessed by prefixing the keys with Esc.  Meta mappings using modifiers can be explicitly enabled using g:readline_meta. Most terminal emulators can be configured to send keys prefixed with Esc when the Alt modifier is held.","4":"To get the latest version it is recommended to download from Github instead: https:\/\/github.com\/ryvnf\/readline.vim\r\n\r\nReadline is a library used for implementing line editing across many command-line tools (including `bash` and other shells and interpreters).  Readline ships with a default set of key-bindings that you are probably already familiar with.  The Readline default bindings is a mixture of traditional Unix and Emacs bindings.\r\n\r\nThis plugins implements a subset of Readline's default keyboard commands to Vim's command-line mode.  Mappings available include deletion and navigation by words and other useful stuff.\r\n\r\nWhat makes this plugin different from similar plugins is that it implements a larger subset of the Readline mappings, and each command is carefully implemented to behave exactly like in Readline.\r\n\r\nThe word movement and deletion commands have different behavior between Vim and Readline.  The biggest difference is that in Readline punctuation is always skipped when searching for a word boundary.  Another difference is that _ (underscore) is treated as a word delimiter.  This plugin implements the Readline behavior for word movement and deletion commands.\r\n\r\nFollowing is a summary of the mappings implemented by this plugin:\r\n\r\nC-b                                  Move backward\r\nC-f                                   Move forward\r\nM-b                                  Move one word backward\r\nM-f                                   Move one word forward\r\nC-a                                  Move to start of line\r\nC-e                                  Move to end of line\r\nC-d                                  Delete character\r\nM-Backspace                   Rubout word\r\nM-d                                  Delete word\r\nC-w                                  Rubout space-delimited word\r\nC-u, C-x Backspace          Delete to start of line\r\nC-k                                   Deleted to end of line (can be disabled with g:readline_ctrl_k)\r\nC-y                                   Yank (paste) previously deleted text\r\nC-t                                    Transpose characters\r\nM-t                                    Transpose words\r\nM-u                                   Make word UPPERCASE\r\nM-l                                    Make word lowercase\r\nM-c                                   Make word Capitalized\r\nM-#                                   Comment out and execute the command-line\r\nM-=, M-?                           List possible completions\r\nM-*                                    Insert possible completions\r\nC-x C-e                              Open command-line window (like default Vim C-f)\r\n\r\nThe word boundaries for movement and deletion differ between Vim and Readline.  The biggest difference is that in Readline punctuation is always skipped when searching for a word boundary.  Another difference is that _ (underscore) is treated as a word delimiter.  This plugin implements the Readline behaivor for word movement and deletion commands.\r\n\r\nThis plugin does not use the Meta-key directly, because it causes conflicts with inserting accented characters on some keyboard layouts.  Instead Meta-key mappings can only be accessed by prefixing the keys with Esc.  Meta mappings using modifiers can be explicitly enabled using g:readline_meta. Most terminal emulators can be configured to send keys prefixed with Esc when the Alt modifier is held.","install_details":"Extract the files to ~\/.vim using the `unzip' command:\r\n\r\n    $ unzip readline.zip -d ~\/.vim\r\n\r\nAfter doing that. Open Vim and run the `helptags' to generate tags for documentation:\r\n\r\n    :helptags ~\/.vim\/doc\r\n\r\nIf using a plug-in manager, refer to its documentation.","5":"Extract the files to ~\/.vim using the `unzip' command:\r\n\r\n    $ unzip readline.zip -d ~\/.vim\r\n\r\nAfter doing that. Open Vim and run the `helptags' to generate tags for documentation:\r\n\r\n    :helptags ~\/.vim\/doc\r\n\r\nIf using a plug-in manager, refer to its documentation.","first_name":"Elias","6":"Elias","last_name":"\u00c3\u0085str\u00c3\u00b6m","7":"\u00c3\u0085str\u00c3\u00b6m","releases":[{"0":"5633","vim_version":"7.0","1":"7.0","script_version":"20191228","2":"20191228","version_comment":"- Allow for backwards compatibility of strchars pre vim 8\r\n- Simplify script","3":"- Allow for backwards compatibility of strchars pre vim 8\r\n- Simplify script","package":"readline.zip","4":"readline.zip","src_id":"26879","5":"26879","creation_date":"1577597223","6":"1577597223"},{"0":"5633","vim_version":"7.0","1":"7.0","script_version":"20190824","2":"20190824","version_comment":"- Add option to disable C-t in incremental searches\r\n- To preserve Vim 8's command to go to previous match","3":"- Add option to disable C-t in incremental searches\r\n- To preserve Vim 8's command to go to previous match","package":"readline.zip","4":"readline.zip","src_id":"26707","5":"26707","creation_date":"1566714949","6":"1566714949"},{"0":"5633","vim_version":"7.0","1":"7.0","script_version":"20190609","2":"20190609","version_comment":"- Change default behavior for escape\r\n- Add option g:readline_esc to get the old behavior back","3":"- Change default behavior for escape\r\n- Add option g:readline_esc to get the old behavior back","package":"readline.zip","4":"readline.zip","src_id":"26532","5":"26532","creation_date":"1560135648","6":"1560135648"},{"0":"5633","vim_version":"7.0","1":"7.0","script_version":"20190510","2":"20190510","version_comment":"- Fix plugin compatibility with Vim version 7.0\r\n- Switch to date based versioning","3":"- Fix plugin compatibility with Vim version 7.0\r\n- Switch to date based versioning","package":"readline.zip","4":"readline.zip","src_id":"26488","5":"26488","creation_date":"1557888868","6":"1557888868"}]},"5632":{"script_id":"5632","0":"5632","script_name":"DumpX","1":"DumpX","script_type":"utility","2":"utility","summary":"Disassemble C\/C++ code","3":"Disassemble C\/C++ code","description":"Disassemble current source file C\/C++ and view assembly code in window.\r\nNot need rebuild all project\r\nCan split on top, bottom, left, right\r\nCan view partial line disassembly, full assembly code and mixed mode\r\nin Mixed mode automatic jump to correspective line where you have start command\r\n\r\n:help DumpX\r\n\r\nfor more detail\r\n\r\nrepository https:\/\/github.com\/vbextreme\/dumpx","4":"Disassemble current source file C\/C++ and view assembly code in window.\r\nNot need rebuild all project\r\nCan split on top, bottom, left, right\r\nCan view partial line disassembly, full assembly code and mixed mode\r\nin Mixed mode automatic jump to correspective line where you have start command\r\n\r\n:help DumpX\r\n\r\nfor more detail\r\n\r\nrepository https:\/\/github.com\/vbextreme\/dumpx","install_details":"copy on .vim\/bundle\r\ncopy dumpx\/syntax\/dumpx.vim in .vim\/syntax\r\n","5":"copy on .vim\/bundle\r\ncopy dumpx\/syntax\/dumpx.vim in .vim\/syntax\r\n","first_name":"vbextreme","6":"vbextreme","last_name":"vbextreme","7":"vbextreme","releases":[{"0":"5632","vim_version":"7.0","1":"7.0","script_version":"0.3","2":"0.3","version_comment":"initial support for automatic flags and center decompiler output.\r\ngithub repo https:\/\/github.com\/vbextreme\/dumpx","3":"initial support for automatic flags and center decompiler output.\r\ngithub repo https:\/\/github.com\/vbextreme\/dumpx","package":"dumpx.tar.xz","4":"dumpx.tar.xz","src_id":"25749","5":"25749","creation_date":"1515142582","6":"1515142582"},{"0":"5632","vim_version":"7.0","1":"7.0","script_version":"0.2","2":"0.2","version_comment":"Initial upload","3":"Initial upload","package":"dumpx.tar.xz","4":"dumpx.tar.xz","src_id":"25733","5":"25733","creation_date":"1514038871","6":"1514038871"}]},"5631":{"script_id":"5631","0":"5631","script_name":"place.vim","1":"place.vim","script_type":"utility","2":"utility","summary":"Enter characters without moving","3":"Enter characters without moving","description":"Note that development happens on Github\r\n\r\nhttps:\/\/github.com\/joereynolds\/place.vim\/\r\n\r\n# place.vim\r\n\r\nplace.vim allows you to add insertions to your text without moving your cursor.\r\nIf you suffer from the following problems, this plugin might be for you:\r\n\r\n- Forgotten to add a ';' at the end of a line.\r\n- Forgotten var, let, $ or any other variant at the beginning of a line.\r\n- Wanted to insert some text without having to enter insert mode, move to the place, leave insert mode, and go back\r\n\r\n![](https:\/\/i.imgur.com\/N3rcDUi.gif)\r\n\r\n## Mapping\r\n\r\nAdd a mapping of your choice to get place.vim working for you.\r\n\r\nExample:\r\n\r\n```\r\nnmap ga (place-insert)\r\n```\r\n\r\n## Examples\r\n\r\n(Examples are using `ga` as the prefix key but it can be anything you want)\r\n\r\nplace.vim works in the 'vim' way. Here are a few examples of what it does\r\n\r\n\r\n`|` denotes cursor position\r\n\r\n\r\n### #1\r\n```\r\nfunction(na|me, $age)\r\ngab$\r\n```\r\nResults in\r\n```\r\nfunction($name, $age)\r\n```\r\n\r\n### #2\r\n```\r\n$thi|s->doSomeStuff = 5\r\nga$;\r\n```\r\nResults in\r\n```\r\n$this->doSomeStuff = 5;\r\n```\r\n\r\n### #3\r\n\r\nIt also supports multiple line motions\r\n```\r\nThis\r\nis\r\na\r\nreally long\r\nline\r\ngaG.\r\n```\r\nResults in\r\n```\r\nThis\r\nis\r\na\r\nreally long\r\nline.\r\n```\r\n\r\n### #4\r\n\r\nA more complex motion (t)\r\n```\r\nT|his is Y sentence\r\ngatYM\r\n```\r\nResults in\r\n```\r\nThis is MY sentence\r\n```\r\n\r\n## FAQ\r\n\r\n> I want to enter 'var' or 'let' like you said I could in the README!\r\n\r\nSure thing, there's a separate mapping `(place-insert-multiple)` to map to.\r\nRead the docs.\r\n\r\nEither that or you can enable it globally:\r\n\r\n`let g:place_single_character_mode = 0`\r\n\r\nNow, when you finish your motion, an input box will appear with what you want to insert.\r\nThis is turned off by default because I imagine the majority of people want to insert small things like $ or ;.","4":"Note that development happens on Github\r\n\r\nhttps:\/\/github.com\/joereynolds\/place.vim\/\r\n\r\n# place.vim\r\n\r\nplace.vim allows you to add insertions to your text without moving your cursor.\r\nIf you suffer from the following problems, this plugin might be for you:\r\n\r\n- Forgotten to add a ';' at the end of a line.\r\n- Forgotten var, let, $ or any other variant at the beginning of a line.\r\n- Wanted to insert some text without having to enter insert mode, move to the place, leave insert mode, and go back\r\n\r\n![](https:\/\/i.imgur.com\/N3rcDUi.gif)\r\n\r\n## Mapping\r\n\r\nAdd a mapping of your choice to get place.vim working for you.\r\n\r\nExample:\r\n\r\n```\r\nnmap ga (place-insert)\r\n```\r\n\r\n## Examples\r\n\r\n(Examples are using `ga` as the prefix key but it can be anything you want)\r\n\r\nplace.vim works in the 'vim' way. Here are a few examples of what it does\r\n\r\n\r\n`|` denotes cursor position\r\n\r\n\r\n### #1\r\n```\r\nfunction(na|me, $age)\r\ngab$\r\n```\r\nResults in\r\n```\r\nfunction($name, $age)\r\n```\r\n\r\n### #2\r\n```\r\n$thi|s->doSomeStuff = 5\r\nga$;\r\n```\r\nResults in\r\n```\r\n$this->doSomeStuff = 5;\r\n```\r\n\r\n### #3\r\n\r\nIt also supports multiple line motions\r\n```\r\nThis\r\nis\r\na\r\nreally long\r\nline\r\ngaG.\r\n```\r\nResults in\r\n```\r\nThis\r\nis\r\na\r\nreally long\r\nline.\r\n```\r\n\r\n### #4\r\n\r\nA more complex motion (t)\r\n```\r\nT|his is Y sentence\r\ngatYM\r\n```\r\nResults in\r\n```\r\nThis is MY sentence\r\n```\r\n\r\n## FAQ\r\n\r\n> I want to enter 'var' or 'let' like you said I could in the README!\r\n\r\nSure thing, there's a separate mapping `(place-insert-multiple)` to map to.\r\nRead the docs.\r\n\r\nEither that or you can enable it globally:\r\n\r\n`let g:place_single_character_mode = 0`\r\n\r\nNow, when you finish your motion, an input box will appear with what you want to insert.\r\nThis is turned off by default because I imagine the majority of people want to insert small things like $ or ;.","install_details":"Using vim-plug you can do the following\r\n\r\nPlug 'joereynolds\/place.vim'","5":"Using vim-plug you can do the following\r\n\r\nPlug 'joereynolds\/place.vim'","first_name":"Joe","6":"Joe","last_name":"Reynolds","7":"Reynolds","releases":[{"0":"5631","vim_version":"7.4","1":"7.4","script_version":"0.2","2":"0.2","version_comment":"Features\r\n=======\r\n\r\n- Remove default mapping of ga and expose  mapping instead\r\n- Expose  mapping to insert multiple characters\r\n- Blink on insertion for visual feedback\r\n- Add support for the following motions:\r\n    - gg\r\n    - F\r\n    - T\r\n    - f\r\n    - {\r\n    - }\r\n- Make plugin repeatable with . command if repeat.vim is installed\r\n- Don't jump the cursor on undo of insertion made by place.vim\r\n    \r\n\r\n\r\n","3":"Features\r\n=======\r\n\r\n- Remove default mapping of ga and expose  mapping instead\r\n- Expose  mapping to insert multiple characters\r\n- Blink on insertion for visual feedback\r\n- Add support for the following motions:\r\n    - gg\r\n    - F\r\n    - T\r\n    - f\r\n    - {\r\n    - }\r\n- Make plugin repeatable with . command if repeat.vim is installed\r\n- Don't jump the cursor on undo of insertion made by place.vim\r\n    \r\n\r\n\r\n","package":"place.vim","4":"place.vim","src_id":"25738","5":"25738","creation_date":"1514214180","6":"1514214180"},{"0":"5631","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"place.vim.zip","4":"place.vim.zip","src_id":"25726","5":"25726","creation_date":"1513936772","6":"1513936772"}]},"5630":{"script_id":"5630","0":"5630","script_name":"vim-terminal","1":"vim-terminal","script_type":"utility","2":"utility","summary":"A Vim plugin that opens an interactive terminal in a buffer for running programs","3":"A Vim plugin that opens an interactive terminal in a buffer for running programs","description":"vim-terminal is a Vim plugin which allows you to run interactive programs, such as bash on Linux or powershell.exe on Windows, inside a Vim buffer. In other words, it is a terminal emulator which uses a Vim buffer to display the program output.\r\n\r\nType :Terminal to run your command in vim, for example:\r\n\r\n:Terminal bash\r\n:Terminal mysql -h localhost -u joe -p sock_collection\r\n:Terminal Powershell.exe\r\n:Terminal C:\\Python27\\python.exe\r\n\r\nTo open Terminal in a new horizontal or vertical buffer use:\r\n\r\n:TerminalSplit \r\n:TerminalVSplit \r\n:TerminalTab \r\n\r\nAll text typed in insert mode will be sent to your shell. Use the key to send a visual selection from any buffer to the shell.\r\n\r\nFor more help type :help Terminal\r\n\r\nNote: this plugin was inspired by Conque","4":"vim-terminal is a Vim plugin which allows you to run interactive programs, such as bash on Linux or powershell.exe on Windows, inside a Vim buffer. In other words, it is a terminal emulator which uses a Vim buffer to display the program output.\r\n\r\nType :Terminal to run your command in vim, for example:\r\n\r\n:Terminal bash\r\n:Terminal mysql -h localhost -u joe -p sock_collection\r\n:Terminal Powershell.exe\r\n:Terminal C:\\Python27\\python.exe\r\n\r\nTo open Terminal in a new horizontal or vertical buffer use:\r\n\r\n:TerminalSplit \r\n:TerminalVSplit \r\n:TerminalTab \r\n\r\nAll text typed in insert mode will be sent to your shell. Use the key to send a visual selection from any buffer to the shell.\r\n\r\nFor more help type :help Terminal\r\n\r\nNote: this plugin was inspired by Conque","install_details":"For the latest use\r\napt-vim install -y https:\/\/github.com\/tc50cal\/vim-terminal.git\r\n\r\nor just extract and merge the zip file into the proper place within your .vim directory.","5":"For the latest use\r\napt-vim install -y https:\/\/github.com\/tc50cal\/vim-terminal.git\r\n\r\nor just extract and merge the zip file into the proper place within your .vim directory.","first_name":"Chad","6":"Chad","last_name":"Hughes","7":"Hughes","releases":[{"0":"5630","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"vim-terminal-1.0.zip","4":"vim-terminal-1.0.zip","src_id":"25725","5":"25725","creation_date":"1513897069","6":"1513897069"}]},"5629":{"script_id":"5629","0":"5629","script_name":"rainbow_levels.vim","1":"rainbow_levels.vim","script_type":"indent","2":"indent","summary":"A different approach to code highlighting.","3":"A different approach to code highlighting.","description":"INTRODUCTION\r\n\r\nThis plugin highlights code by indentation level instead of language syntax.\r\nIt is specially useful when dealing with deeply nested code or callback hells.\r\n\r\n\r\nUSAGE\r\n\r\nThis plugin exposes three self-explanatory commands:\r\n\r\n\t:RainbowLevelsOn\r\n\t:RainbowLevelsOff\r\n\t:RainbowLevelsToggle\r\n\r\nAnd you can use them in a variety of ways, for example:\r\n\r\n\t\" Creating a mapping to turn it on and off:\r\n\tmap l :RainbowLevelsToggle\r\n\r\n\t\" Or automatically turning it on for certain file types:\r\n\tau FileType javascript,python,php,xml,yaml :RainbowLevelsOn\r\n\r\n\r\nCUSTOMIZATION\r\n\r\nTo customize the levels you just need to define highlight groups whith the\r\nname RainbowLevelsN, where N is the number of the level.\r\n\r\nBy default this plugin defines 7 highlight groups, simply linking to common\r\nexisting highlight groups, in order to respect your colorscheme.\r\n\r\nBut you are free to define as many levels you wish. Check the examples below\r\nand also the User-Contributed Themes page for inspiration.\r\nhttps:\/\/github.com\/thiagoalessio\/rainbow_levels.vim\/wiki\/User-Contributed-Themes\r\n\r\n\r\nEXAMPLE: Jellybeans Rainbow\r\n\r\nUsing groups defined by jellybeans colorscheme in a \"rainbow\" sequence.\r\n\r\n\thi! link RainbowLevel0 Constant\r\n\thi! link RainbowLevel1 Type\r\n\thi! link RainbowLevel2 Function\r\n\thi! link RainbowLevel3 String\r\n\thi! link RainbowLevel4 PreProc\r\n\thi! link RainbowLevel5 Statement\r\n\thi! link RainbowLevel6 Identifier\r\n\thi! link RainbowLevel7 Normal\r\n\thi! link RainbowLevel8 Comment\r\n\r\n\r\nEXAMPLE: Background Only\r\n\r\nWant to keep syntax highlight? No problem! You can change only the background\r\ncolors instead.\r\n\r\n\thi! RainbowLevel0 ctermbg=240 guibg=#585858\r\n\thi! RainbowLevel1 ctermbg=239 guibg=#4e4e4e\r\n\thi! RainbowLevel2 ctermbg=238 guibg=#444444\r\n\thi! RainbowLevel3 ctermbg=237 guibg=#3a3a3a\r\n\thi! RainbowLevel4 ctermbg=236 guibg=#303030\r\n\thi! RainbowLevel5 ctermbg=235 guibg=#262626\r\n\thi! RainbowLevel6 ctermbg=234 guibg=#1c1c1c\r\n\thi! RainbowLevel7 ctermbg=233 guibg=#121212\r\n\thi! RainbowLevel8 ctermbg=232 guibg=#080808\r\n\r\n\r\nEXAMPLE: Cycle colors\r\n\r\nUsing a loop to automate the tedious work of defining all highlight groups.\r\n\r\n\tfor level in range(0, 10, 2)\r\n\t\texe 'hi! RainbowLevel'.level.' ctermfg=magenta'\r\n\t\texe 'hi! RainbowLevel'.(level+1).' ctermfg=cyan'\r\n\tendfor\r\n\r\n\r\nEXAMPLE: Level Alert\r\n\r\nNothing shows up until a certain threshold, warning you that the code is going\r\ntoo deep.\r\n\r\n\r\n\thi! RainbowLevel0 ctermbg=none ctermfg=none cterm=none\r\n\thi! RainbowLevel2 ctermbg=none ctermfg=none cterm=none\r\n\thi! RainbowLevel3 ctermbg=none ctermfg=none cterm=none\r\n\thi! RainbowLevel4 ctermbg=none ctermfg=none cterm=none\r\n\thi! link RainbowLevel5 WarningMsg\r\n\tfor level in range(6, 10)\r\n\t\texe 'hi! link RainbowLevel'.level.' ErrorMsg'\r\n\tendfor\r\n\r\n\r\nSPECIAL THANKS\r\n\r\n* Campbell Vertesi and Victor Schroeder for the idea to fade levels in shades\r\n  of a single color.\r\n\r\n* David De Sousa and Lucas Caton for the idea of highlighting only the\r\n  background, to keep syntax highlight.\r\n\r\n* Derek Shoemaker for creating the very first User-Contributed Theme with a\r\n  different \"rainbow\" order, making a beautiful contrast between levels.\r\n\r\n* Ingo Karkat for identifying and fixing several issues present on the initial\r\n  implementation.\r\n\r\n\r\nWHERE TO GET HELP\r\n\r\nJoin the chat at https:\/\/gitter.im\/thiagoalessio\/rainbow_levels.vim\r\n\r\n\r\nBUGS\r\n\r\nPlease report any bugs you may find on the GitHub issue tracker:\r\nhttp:\/\/github.com\/thiagoalessio\/rainbow_levels.vim\/issues\r\n\r\n\r\nLICENSE\r\n\r\nrainbow_levels.vim is released under the MIT License.\r\n\r\n------------------------------------------------------------------------------\r\n                           Made with love in Berlin","4":"INTRODUCTION\r\n\r\nThis plugin highlights code by indentation level instead of language syntax.\r\nIt is specially useful when dealing with deeply nested code or callback hells.\r\n\r\n\r\nUSAGE\r\n\r\nThis plugin exposes three self-explanatory commands:\r\n\r\n\t:RainbowLevelsOn\r\n\t:RainbowLevelsOff\r\n\t:RainbowLevelsToggle\r\n\r\nAnd you can use them in a variety of ways, for example:\r\n\r\n\t\" Creating a mapping to turn it on and off:\r\n\tmap l :RainbowLevelsToggle\r\n\r\n\t\" Or automatically turning it on for certain file types:\r\n\tau FileType javascript,python,php,xml,yaml :RainbowLevelsOn\r\n\r\n\r\nCUSTOMIZATION\r\n\r\nTo customize the levels you just need to define highlight groups whith the\r\nname RainbowLevelsN, where N is the number of the level.\r\n\r\nBy default this plugin defines 7 highlight groups, simply linking to common\r\nexisting highlight groups, in order to respect your colorscheme.\r\n\r\nBut you are free to define as many levels you wish. Check the examples below\r\nand also the User-Contributed Themes page for inspiration.\r\nhttps:\/\/github.com\/thiagoalessio\/rainbow_levels.vim\/wiki\/User-Contributed-Themes\r\n\r\n\r\nEXAMPLE: Jellybeans Rainbow\r\n\r\nUsing groups defined by jellybeans colorscheme in a \"rainbow\" sequence.\r\n\r\n\thi! link RainbowLevel0 Constant\r\n\thi! link RainbowLevel1 Type\r\n\thi! link RainbowLevel2 Function\r\n\thi! link RainbowLevel3 String\r\n\thi! link RainbowLevel4 PreProc\r\n\thi! link RainbowLevel5 Statement\r\n\thi! link RainbowLevel6 Identifier\r\n\thi! link RainbowLevel7 Normal\r\n\thi! link RainbowLevel8 Comment\r\n\r\n\r\nEXAMPLE: Background Only\r\n\r\nWant to keep syntax highlight? No problem! You can change only the background\r\ncolors instead.\r\n\r\n\thi! RainbowLevel0 ctermbg=240 guibg=#585858\r\n\thi! RainbowLevel1 ctermbg=239 guibg=#4e4e4e\r\n\thi! RainbowLevel2 ctermbg=238 guibg=#444444\r\n\thi! RainbowLevel3 ctermbg=237 guibg=#3a3a3a\r\n\thi! RainbowLevel4 ctermbg=236 guibg=#303030\r\n\thi! RainbowLevel5 ctermbg=235 guibg=#262626\r\n\thi! RainbowLevel6 ctermbg=234 guibg=#1c1c1c\r\n\thi! RainbowLevel7 ctermbg=233 guibg=#121212\r\n\thi! RainbowLevel8 ctermbg=232 guibg=#080808\r\n\r\n\r\nEXAMPLE: Cycle colors\r\n\r\nUsing a loop to automate the tedious work of defining all highlight groups.\r\n\r\n\tfor level in range(0, 10, 2)\r\n\t\texe 'hi! RainbowLevel'.level.' ctermfg=magenta'\r\n\t\texe 'hi! RainbowLevel'.(level+1).' ctermfg=cyan'\r\n\tendfor\r\n\r\n\r\nEXAMPLE: Level Alert\r\n\r\nNothing shows up until a certain threshold, warning you that the code is going\r\ntoo deep.\r\n\r\n\r\n\thi! RainbowLevel0 ctermbg=none ctermfg=none cterm=none\r\n\thi! RainbowLevel2 ctermbg=none ctermfg=none cterm=none\r\n\thi! RainbowLevel3 ctermbg=none ctermfg=none cterm=none\r\n\thi! RainbowLevel4 ctermbg=none ctermfg=none cterm=none\r\n\thi! link RainbowLevel5 WarningMsg\r\n\tfor level in range(6, 10)\r\n\t\texe 'hi! link RainbowLevel'.level.' ErrorMsg'\r\n\tendfor\r\n\r\n\r\nSPECIAL THANKS\r\n\r\n* Campbell Vertesi and Victor Schroeder for the idea to fade levels in shades\r\n  of a single color.\r\n\r\n* David De Sousa and Lucas Caton for the idea of highlighting only the\r\n  background, to keep syntax highlight.\r\n\r\n* Derek Shoemaker for creating the very first User-Contributed Theme with a\r\n  different \"rainbow\" order, making a beautiful contrast between levels.\r\n\r\n* Ingo Karkat for identifying and fixing several issues present on the initial\r\n  implementation.\r\n\r\n\r\nWHERE TO GET HELP\r\n\r\nJoin the chat at https:\/\/gitter.im\/thiagoalessio\/rainbow_levels.vim\r\n\r\n\r\nBUGS\r\n\r\nPlease report any bugs you may find on the GitHub issue tracker:\r\nhttp:\/\/github.com\/thiagoalessio\/rainbow_levels.vim\/issues\r\n\r\n\r\nLICENSE\r\n\r\nrainbow_levels.vim is released under the MIT License.\r\n\r\n------------------------------------------------------------------------------\r\n                           Made with love in Berlin","install_details":"VUNDLE\r\n\r\nPlace this in your .vimrc:\r\n\r\nPlugin 'thiagoalessio\/rainbow_levels.vim'\r\n\u00e2\u0080\u00a6 then run the following in Vim:\r\n\r\n:source %\r\n:PluginInstall\r\nFor Vundle version < 0.10.2, replace Plugin with Bundle above.\r\n\r\n\r\nNEOBUNDLE\r\n\r\nPlace this in your .vimrc:\r\n\r\nNeoBundle 'thiagoalessio\/rainbow_levels.vim'\r\n\u00e2\u0080\u00a6 then run the following in Vim:\r\n\r\n:source %\r\n:NeoBundleInstall\r\n\r\n\r\nVIMPLUG\r\n\r\nPlace this in your .vimrc:\r\n\r\nPlug 'thiagoalessio\/rainbow_levels.vim'\r\n\u00e2\u0080\u00a6 then run the following in Vim:\r\n\r\n:source %\r\n:PlugInstall\r\n\r\n\r\nPATHOGEN\r\nRun the following in a terminal:\r\n\r\ncd ~\/.vim\/bundle\r\ngit clone https:\/\/github.com\/thiagoalessio\/rainbow_levels.vim","5":"VUNDLE\r\n\r\nPlace this in your .vimrc:\r\n\r\nPlugin 'thiagoalessio\/rainbow_levels.vim'\r\n\u00e2\u0080\u00a6 then run the following in Vim:\r\n\r\n:source %\r\n:PluginInstall\r\nFor Vundle version < 0.10.2, replace Plugin with Bundle above.\r\n\r\n\r\nNEOBUNDLE\r\n\r\nPlace this in your .vimrc:\r\n\r\nNeoBundle 'thiagoalessio\/rainbow_levels.vim'\r\n\u00e2\u0080\u00a6 then run the following in Vim:\r\n\r\n:source %\r\n:NeoBundleInstall\r\n\r\n\r\nVIMPLUG\r\n\r\nPlace this in your .vimrc:\r\n\r\nPlug 'thiagoalessio\/rainbow_levels.vim'\r\n\u00e2\u0080\u00a6 then run the following in Vim:\r\n\r\n:source %\r\n:PlugInstall\r\n\r\n\r\nPATHOGEN\r\nRun the following in a terminal:\r\n\r\ncd ~\/.vim\/bundle\r\ngit clone https:\/\/github.com\/thiagoalessio\/rainbow_levels.vim","first_name":"Thiago","6":"Thiago","last_name":"Alessio","7":"Alessio","releases":[{"0":"5629","vim_version":"7.0","1":"7.0","script_version":"0.8.0","2":"0.8.0","version_comment":"Default colors for popular colorschemes","3":"Default colors for popular colorschemes","package":"rainbow_levels-0.8.0.zip","4":"rainbow_levels-0.8.0.zip","src_id":"26203","5":"26203","creation_date":"1536121468","6":"1536121468"},{"0":"5629","vim_version":"7.0","1":"7.0","script_version":"0.7.1","2":"0.7.1","version_comment":"Patch: Fix unintended syntax highlight overrides","3":"Patch: Fix unintended syntax highlight overrides","package":"rainbow_levels-0.7.1.zip","4":"rainbow_levels-0.7.1.zip","src_id":"26071","5":"26071","creation_date":"1529784632","6":"1529784632"},{"0":"5629","vim_version":"7.0","1":"7.0","script_version":"0.7.0","2":"0.7.0","version_comment":"Easy access to documentation, by :h RainbowLevels","3":"Easy access to documentation, by :h RainbowLevels","package":"rainbow_levels-0.7.0.zip","4":"rainbow_levels-0.7.0.zip","src_id":"25945","5":"25945","creation_date":"1524696134","6":"1524696134"},{"0":"5629","vim_version":"7.0","1":"7.0","script_version":"0.6.0","2":"0.6.0","version_comment":"Simplified way to customize levels, without custom variable","3":"Simplified way to customize levels, without custom variable","package":"rainbow_levels-0.6.0.zip","4":"rainbow_levels-0.6.0.zip","src_id":"25930","5":"25930","creation_date":"1524073442","6":"1524073442"},{"0":"5629","vim_version":"7.0","1":"7.0","script_version":"0.5.0","2":"0.5.0","version_comment":"Allow use of same color for different levels","3":"Allow use of same color for different levels","package":"rainbow_levels-0.5.0.zip","4":"rainbow_levels-0.5.0.zip","src_id":"25732","5":"25732","creation_date":"1514035921","6":"1514035921"},{"0":"5629","vim_version":"7.0","1":"7.0","script_version":"0.4.0","2":"0.4.0","version_comment":"Better support for softtabstop","3":"Better support for softtabstop","package":"rainbow_levels-0.4.0.zip","4":"rainbow_levels-0.4.0.zip","src_id":"25729","5":"25729","creation_date":"1513956986","6":"1513956986"},{"0":"5629","vim_version":"7.0","1":"7.0","script_version":"0.3.0","2":"0.3.0","version_comment":"Correctly match levels with mixed tabs and spaces","3":"Correctly match levels with mixed tabs and spaces","package":"rainbow_levels-0.3.0.zip","4":"rainbow_levels-0.3.0.zip","src_id":"25724","5":"25724","creation_date":"1513888567","6":"1513888567"},{"0":"5629","vim_version":"7.0","1":"7.0","script_version":"0.2.0","2":"0.2.0","version_comment":"Fixes match priority and color override by loading sequence","3":"Fixes match priority and color override by loading sequence","package":"rainbow_levels-0.2.0.zip","4":"rainbow_levels-0.2.0.zip","src_id":"25723","5":"25723","creation_date":"1513785944","6":"1513785944"},{"0":"5629","vim_version":"7.0","1":"7.0","script_version":"0.1.0","2":"0.1.0","version_comment":"Initial upload","3":"Initial upload","package":"rainbow_levels-0.1.0.zip","4":"rainbow_levels-0.1.0.zip","src_id":"25720","5":"25720","creation_date":"1513640537","6":"1513640537"}]},"5628":{"script_id":"5628","0":"5628","script_name":"bioSyntax","1":"bioSyntax","script_type":"syntax","2":"syntax","summary":"Syntax Highlighting for Computational Biology","3":"Syntax Highlighting for Computational Biology","description":"For more info + most recent updates visit: http:\/\/bioSyntax.org\r\n\r\nA syntax highlighting suite for computational biology \/ bioinformatics to grok your data.\r\n\r\nFile formats supported are SAM, VCF, FASTA, FASTQ, PDB, GTF, WIG, BED, and more.\r\n\r\n\r\n","4":"For more info + most recent updates visit: http:\/\/bioSyntax.org\r\n\r\nA syntax highlighting suite for computational biology \/ bioinformatics to grok your data.\r\n\r\nFile formats supported are SAM, VCF, FASTA, FASTQ, PDB, GTF, WIG, BED, and more.\r\n\r\n\r\n","install_details":"Full Instructions: http:\/\/biosyntax.org\/install\r\n\r\n# quick install\r\ncp $bioSyntax\/vim\/syntax\/*       ~\/.vim\/syntax\/\r\ncp $bioSyntax\/vim\/colors\/*       ~\/.vim\/colors\/\r\ncp $bioSyntax\/vim\/ftdetect\/*     ~\/.vim\/ftdetect\/\r\n\r\n\r\n## via Pathogen\r\ncd ~\/.vim\/bundle &&\r\ngit clone https:\/\/github.com\/bioSyntax\/bioSyntax-vim.git\r\n\r\n","5":"Full Instructions: http:\/\/biosyntax.org\/install\r\n\r\n# quick install\r\ncp $bioSyntax\/vim\/syntax\/*       ~\/.vim\/syntax\/\r\ncp $bioSyntax\/vim\/colors\/*       ~\/.vim\/colors\/\r\ncp $bioSyntax\/vim\/ftdetect\/*     ~\/.vim\/ftdetect\/\r\n\r\n\r\n## via Pathogen\r\ncd ~\/.vim\/bundle &&\r\ngit clone https:\/\/github.com\/bioSyntax\/bioSyntax-vim.git\r\n\r\n","first_name":"Artem","6":"Artem","last_name":"Babaian","7":"Babaian","releases":[{"0":"5628","vim_version":"7.0","1":"7.0","script_version":"v0.1-beta3","2":"v0.1-beta3","version_comment":"See https:\/\/github.com\/bioSyntax\/bioSyntax for full release notes\r\n- Pathogen Installation support added\r\n- Some minor bug fixes.\r\n","3":"See https:\/\/github.com\/bioSyntax\/bioSyntax for full release notes\r\n- Pathogen Installation support added\r\n- Some minor bug fixes.\r\n","package":"bioSyntax-vim_v0.1-beta3.tar.gz","4":"bioSyntax-vim_v0.1-beta3.tar.gz","src_id":"25758","5":"25758","creation_date":"1515778321","6":"1515778321"},{"0":"5628","vim_version":"7.0","1":"7.0","script_version":"v0.1","2":"v0.1","version_comment":"Initial upload","3":"Initial upload","package":"bioSyntax-0.1-beta.tar.gz","4":"bioSyntax-0.1-beta.tar.gz","src_id":"25717","5":"25717","creation_date":"1513533236","6":"1513533236"}]},"5627":{"script_id":"5627","0":"5627","script_name":"i3config.vim","1":"i3config.vim","script_type":"syntax","2":"syntax","summary":"Vim syntax highlighting for i3 config","3":"Vim syntax highlighting for i3 config","description":"https:\/\/github.com\/mboughaba\/i3config.vim\r\ni3config.vim - vim i3 config syntax highlighting\r\n\r\nThis file contains syntax highlighting that I use for i3 config in Vim. Compared to the vim standard conf syntax highlighting, i3config adds highlighting of all keywords, types and options as defined in the i3 configuration manual.\r\nI build this based on the current specification provided (as of Sat 12 Mar 2016) in:\r\nhttp:\/\/i3wm.org\/docs\/userguide.html#configuring\r\n\r\nFeatures:\r\ni3config does what a syntax highlighting would do and additionally provide some sort of syntax checking. If you end up with Bold Red lines in your i3 config file this would mean that your syntax is wrong or there is an issue in the plugin. If that is the case please report the issue and\/or make a pull request to cover the case.\r\n\r\nFile type detection:\r\nThere is no specific extension for i3 config file. For auto detection, the recommended method is to rename your file to something like:\r\n\r\n.i3.config\r\ni3.config\r\nsomething.i3config\r\nsomething.i3.config\r\nThis way you can keep your file clean somewhere in a dotfile repository and have it symlinked to ~\/.i3\/config\r\nIf you don't want to, then you can always do:\r\n:set ft=i3config\r\nor\r\n:set filetype=i3config","4":"https:\/\/github.com\/mboughaba\/i3config.vim\r\ni3config.vim - vim i3 config syntax highlighting\r\n\r\nThis file contains syntax highlighting that I use for i3 config in Vim. Compared to the vim standard conf syntax highlighting, i3config adds highlighting of all keywords, types and options as defined in the i3 configuration manual.\r\nI build this based on the current specification provided (as of Sat 12 Mar 2016) in:\r\nhttp:\/\/i3wm.org\/docs\/userguide.html#configuring\r\n\r\nFeatures:\r\ni3config does what a syntax highlighting would do and additionally provide some sort of syntax checking. If you end up with Bold Red lines in your i3 config file this would mean that your syntax is wrong or there is an issue in the plugin. If that is the case please report the issue and\/or make a pull request to cover the case.\r\n\r\nFile type detection:\r\nThere is no specific extension for i3 config file. For auto detection, the recommended method is to rename your file to something like:\r\n\r\n.i3.config\r\ni3.config\r\nsomething.i3config\r\nsomething.i3.config\r\nThis way you can keep your file clean somewhere in a dotfile repository and have it symlinked to ~\/.i3\/config\r\nIf you don't want to, then you can always do:\r\n:set ft=i3config\r\nor\r\n:set filetype=i3config","install_details":"Follow one of the steps below and reload vim afterwards.\r\n\r\nVundle\r\n\r\nInstal using vundle by adding\r\n\r\nPlugin 'mboughaba\/i3config.vim'\r\nto .vimrc and run :PluginInstall.\r\n\r\nI use Vundle myself, the two steps below may not be fully correct, you need to change them to fit your needs.\r\nGit submodule + Pathogen\r\n\r\nIf you have pathogen installed, and you prefer to use git submodules, run\r\n\r\ncd ~\/.vim\r\ngit submodule add https:\/\/github.com\/mboughaba\/i3config.vim.git bundle\/syntax\/\r\nManual installation\r\n\r\nIf you don't have either Vundle or Pathogen installed, copy both i3config.vim file to .vim\/after\/syntax and .vim\/after\/ftdetect respectively.\r\n\r\ngit clone https:\/\/github.com\/mboughaba\/i3config.git \/tmp\/i3config.vim\r\nmkdir -p ~\/.vim\/after\/syntax\/\r\nmv \/tmp\/i3config.vim\/after\/syntax\/i3config.vim ~\/.vim\/after\/syntax\/i3config.vim\r\nrm -rf \/tmp\/i3config.vim","5":"Follow one of the steps below and reload vim afterwards.\r\n\r\nVundle\r\n\r\nInstal using vundle by adding\r\n\r\nPlugin 'mboughaba\/i3config.vim'\r\nto .vimrc and run :PluginInstall.\r\n\r\nI use Vundle myself, the two steps below may not be fully correct, you need to change them to fit your needs.\r\nGit submodule + Pathogen\r\n\r\nIf you have pathogen installed, and you prefer to use git submodules, run\r\n\r\ncd ~\/.vim\r\ngit submodule add https:\/\/github.com\/mboughaba\/i3config.vim.git bundle\/syntax\/\r\nManual installation\r\n\r\nIf you don't have either Vundle or Pathogen installed, copy both i3config.vim file to .vim\/after\/syntax and .vim\/after\/ftdetect respectively.\r\n\r\ngit clone https:\/\/github.com\/mboughaba\/i3config.git \/tmp\/i3config.vim\r\nmkdir -p ~\/.vim\/after\/syntax\/\r\nmv \/tmp\/i3config.vim\/after\/syntax\/i3config.vim ~\/.vim\/after\/syntax\/i3config.vim\r\nrm -rf \/tmp\/i3config.vim","first_name":"Mohamed","6":"Mohamed","last_name":"Boughaba","7":"Boughaba","releases":[{"0":"5627","vim_version":"7.0","1":"7.0","script_version":"0.3.0","2":"0.3.0","version_comment":"Initial upload","3":"Initial upload","package":"i3config.vim-0.3.0.zip","4":"i3config.vim-0.3.0.zip","src_id":"25696","5":"25696","creation_date":"1512676831","6":"1512676831"}]},"5626":{"script_id":"5626","0":"5626","script_name":"Libertine","1":"Libertine","script_type":"color scheme","2":"color scheme","summary":"A complex mix of seven strong bodied colors with citrus flavors and pine notes","3":"A complex mix of seven strong bodied colors with citrus flavors and pine notes","description":"For use in any 256 color terminals, Gui, or  Termguicolors supported terminals.  \r\n\r\nFor more info: https:\/\/github.com\/AlessandroYorba\/Libertine\r\n","4":"For use in any 256 color terminals, Gui, or  Termguicolors supported terminals.  \r\n\r\nFor more info: https:\/\/github.com\/AlessandroYorba\/Libertine\r\n","install_details":"Unix users, place libertine.vim in ~\/.vim\/colors\r\nWindows users, place libertine.vim in  ~\\vimfiles\\colors\r\n","5":"Unix users, place libertine.vim in ~\/.vim\/colors\r\nWindows users, place libertine.vim in  ~\\vimfiles\\colors\r\n","first_name":"Alessandro","6":"Alessandro","last_name":"Yorba","7":"Yorba","releases":[{"0":"5626","vim_version":"7.0","1":"7.0","script_version":"1e66d66","2":"1e66d66","version_comment":"* Added darker modes that can be set from your .vimrc. [Sunset, Twilight, Midnight, Pitch]\r\n* Added terminal support for all modes\r\n\r\nFor screenshots and config settings, checkout:\r\nhttps:\/\/github.com\/AlessandroYorba\/Libertine","3":"* Added darker modes that can be set from your .vimrc. [Sunset, Twilight, Midnight, Pitch]\r\n* Added terminal support for all modes\r\n\r\nFor screenshots and config settings, checkout:\r\nhttps:\/\/github.com\/AlessandroYorba\/Libertine","package":"libertine.vim","4":"libertine.vim","src_id":"25686","5":"25686","creation_date":"1512428914","6":"1512428914"}]},"5625":{"script_id":"5625","0":"5625","script_name":"Github.vim","1":"Github.vim","script_type":"utility","2":"utility","summary":"Another github v3 api implemented in vim script","3":"Another github v3 api implemented in vim script","description":"This is a vim script library to access the Github API v3. With it, you can manage Github resources (repositories, user profiles, organizations, etc.) from viml scripts.\r\n\r\nfor example, to creat an issue:\r\n\r\nfunction! CreateIssue(owner, repo) abort\r\n    let username = input('your github username:')\r\n    let password = input('your github password:')\r\n    let title = input('Issue title: ')\r\n    let issue = {\r\n                \\ 'title': title,\r\n                \\ 'body': s:body(),\r\n                \\ }\r\n    let response = github#api#issues#Create(a:owner, a:repo,\r\n                \\ username, password, issue)\r\n    if !empty(response)\r\n        echomsg 'Create successed! ' . response.url\r\n    else\r\n        echom 'Create failed!'\r\n    endif\r\nendfunction\r\n\r\nfunc! s:body()\r\n    return 'Testting Github.vim...'\r\nendf","4":"This is a vim script library to access the Github API v3. With it, you can manage Github resources (repositories, user profiles, organizations, etc.) from viml scripts.\r\n\r\nfor example, to creat an issue:\r\n\r\nfunction! CreateIssue(owner, repo) abort\r\n    let username = input('your github username:')\r\n    let password = input('your github password:')\r\n    let title = input('Issue title: ')\r\n    let issue = {\r\n                \\ 'title': title,\r\n                \\ 'body': s:body(),\r\n                \\ }\r\n    let response = github#api#issues#Create(a:owner, a:repo,\r\n                \\ username, password, issue)\r\n    if !empty(response)\r\n        echomsg 'Create successed! ' . response.url\r\n    else\r\n        echom 'Create failed!'\r\n    endif\r\nendfunction\r\n\r\nfunc! s:body()\r\n    return 'Testting Github.vim...'\r\nendf","install_details":"For unauthenticated requests, the rate limit allows for up to 60 requests per hour. Unauthenticated requests are associated with the originating IP address, and not the user making requests.Increasing the unauthenticated rate limit, you need Create OAuth app, and set EVN: CLIENTID and CLIENTSECRET.","5":"For unauthenticated requests, the rate limit allows for up to 60 requests per hour. Unauthenticated requests are associated with the originating IP address, and not the user making requests.Increasing the unauthenticated rate limit, you need Create OAuth app, and set EVN: CLIENTID and CLIENTSECRET.","first_name":"Shidong","6":"Shidong","last_name":"Wang","7":"Wang","releases":[{"0":"5625","vim_version":"7.0","1":"7.0","script_version":"v0.1.1","2":"v0.1.1","version_comment":"Initial upload","3":"Initial upload","package":"GitHub.vim-master.zip","4":"GitHub.vim-master.zip","src_id":"25679","5":"25679","creation_date":"1512094366","6":"1512094366"}]},"5624":{"script_id":"5624","0":"5624","script_name":"match-up","1":"match-up","script_type":"utility","2":"utility","summary":"even better %, navigate & highlight matching word, modern matchit replacement","3":"even better %, navigate & highlight matching word, modern matchit replacement","description":"The current version of this plugin is always available from:\r\n\r\n    https:\/\/github.com\/andymass\/vim-matchup.\r\n\r\nmatch-up is a plugin that lets you visualize, navigate, and operate on\r\nsets of matching text.  The plugin:\r\n\r\n- Extends vim's % motion to language-specific words instead of just single\r\n  characters.  The words depend on the specific filetype plugin.  The\r\n  following built-in vim filetype plugins currently provide support for\r\n  match-up:\r\n\r\n    abaqus, ada, aspvbs, c, clojure, cobol, config, context, csc, csh, dtd,\r\n    dtrace, eiffel, eruby, falcon, fortran, framescript, haml, hamster, hog,\r\n    html, ishd, j, jsp, kconfig, liquid, lua, make, matlab, mf, mp, ocaml,\r\n    pascal, pdf, perl, php, plaintex, postscr, ruby, sh, spec, sql, tex, vb,\r\n    verilog, vhdl, vim, xhtml, xml, zimbu, zsh\r\n\r\n- Highlights symbols and words under the cursor along with their matches.\r\n\r\n- Displays off-screen matches in the status-line.\r\n\r\n- Adds motions g%, [%, ]%, and z%.\r\n\r\n- Provides analogous text objects i% and a%.\r\n\r\nmatch-up is a replacement for the venerable vim plugin matchit.  match-up\r\nreplicates all of matchit's features, fixes a number of its deficiencies\r\nand bugs, and adds a few totally new features.  It also replaces the\r\nstandard plugin matchparen, allowing all of matchit's words to be\r\nhighlighted along with the 'matchpairs' symbols such as (), {}, and [].\r\n","4":"The current version of this plugin is always available from:\r\n\r\n    https:\/\/github.com\/andymass\/vim-matchup.\r\n\r\nmatch-up is a plugin that lets you visualize, navigate, and operate on\r\nsets of matching text.  The plugin:\r\n\r\n- Extends vim's % motion to language-specific words instead of just single\r\n  characters.  The words depend on the specific filetype plugin.  The\r\n  following built-in vim filetype plugins currently provide support for\r\n  match-up:\r\n\r\n    abaqus, ada, aspvbs, c, clojure, cobol, config, context, csc, csh, dtd,\r\n    dtrace, eiffel, eruby, falcon, fortran, framescript, haml, hamster, hog,\r\n    html, ishd, j, jsp, kconfig, liquid, lua, make, matlab, mf, mp, ocaml,\r\n    pascal, pdf, perl, php, plaintex, postscr, ruby, sh, spec, sql, tex, vb,\r\n    verilog, vhdl, vim, xhtml, xml, zimbu, zsh\r\n\r\n- Highlights symbols and words under the cursor along with their matches.\r\n\r\n- Displays off-screen matches in the status-line.\r\n\r\n- Adds motions g%, [%, ]%, and z%.\r\n\r\n- Provides analogous text objects i% and a%.\r\n\r\nmatch-up is a replacement for the venerable vim plugin matchit.  match-up\r\nreplicates all of matchit's features, fixes a number of its deficiencies\r\nand bugs, and adds a few totally new features.  It also replaces the\r\nstandard plugin matchparen, allowing all of matchit's words to be\r\nhighlighted along with the 'matchpairs' symbols such as (), {}, and [].\r\n","install_details":"The preferred method of installation is to use vim-plug or another plugin\r\nmanager to ensure you always have the most up-to-date version of match-up.\r\n\r\n    Plug 'andymass\/vim-matchup'\r\n\r\nAlternatively, download and extract the package and install manually using any\r\nstandard vim way.\r\n","5":"The preferred method of installation is to use vim-plug or another plugin\r\nmanager to ensure you always have the most up-to-date version of match-up.\r\n\r\n    Plug 'andymass\/vim-matchup'\r\n\r\nAlternatively, download and extract the package and install manually using any\r\nstandard vim way.\r\n","first_name":"andy","6":"andy","last_name":"massimino","7":"massimino","releases":[{"0":"5624","vim_version":"7.4","1":"7.4","script_version":"0.7.0","2":"0.7.0","version_comment":"Improved the off-screen popup window, including adding extended highlighting.  Made miscellaneous bug fixes.","3":"Improved the off-screen popup window, including adding extended highlighting.  Made miscellaneous bug fixes.","package":"vim-matchup-0.7.0.zip","4":"vim-matchup-0.7.0.zip","src_id":"27879","5":"27879","creation_date":"1641003965","6":"1641003965"},{"0":"5624","vim_version":"7.4","1":"7.4","script_version":"0.6.0","2":"0.6.0","version_comment":"Adds \"same character\" matching (currently for tex and javascript). Miscellaneous fixes.","3":"Adds \"same character\" matching (currently for tex and javascript). Miscellaneous fixes.","package":"vim-matchup-0.6.0.zip","4":"vim-matchup-0.6.0.zip","src_id":"27495","5":"27495","creation_date":"1614090854","6":"1614090854"},{"0":"5624","vim_version":"7.4","1":"7.4","script_version":"0.5.0","2":"0.5.0","version_comment":"Use popup window to show off-screen matches.  Improve matching with lua and ruby.  Add :MatchupWhereAmI? to show breadcrumb-style location in code.  Fix miscellaneous bugs in motions and text-objects.","3":"Use popup window to show off-screen matches.  Improve matching with lua and ruby.  Add :MatchupWhereAmI? to show breadcrumb-style location in code.  Fix miscellaneous bugs in motions and text-objects.","package":"vim-matchup-0.5.0.zip","4":"vim-matchup-0.5.0.zip","src_id":"27149","5":"27149","creation_date":"1588932539","6":"1588932539"},{"0":"5624","vim_version":"7.4","1":"7.4","script_version":"0.4.0","2":"0.4.0","version_comment":"Add off-screen line adjustment for C-like languages.  Add match highlight fading feature.  Fix many bugs.\r\nNote: now distributed on vim scripts as a flat archive.\r\n","3":"Add off-screen line adjustment for C-like languages.  Add match highlight fading feature.  Fix many bugs.\r\nNote: now distributed on vim scripts as a flat archive.\r\n","package":"vim-matchup-0.4.0.zip","4":"vim-matchup-0.4.0.zip","src_id":"26418","5":"26418","creation_date":"1552080526","6":"1552080526"},{"0":"5624","vim_version":"7.4","1":"7.4","script_version":"0.3","2":"0.3","version_comment":"Add html highlighting of tag only. Add surround and highlight background features. Fix many bugs.","3":"Add html highlighting of tag only. Add surround and highlight background features. Fix many bugs.","package":"vim-matchup-0.3.0.zip","4":"vim-matchup-0.3.0.zip","src_id":"26273","5":"26273","creation_date":"1542337107","6":"1542337107"},{"0":"5624","vim_version":"7.4","1":"7.4","script_version":"0.2","2":"0.2","version_comment":"Numerous improvements have been made including better support for LaTeX.\r\n","3":"Numerous improvements have been made including better support for LaTeX.\r\n","package":"vim-matchup-0.2.0.zip","4":"vim-matchup-0.2.0.zip","src_id":"25866","5":"25866","creation_date":"1520359990","6":"1520359990"},{"0":"5624","vim_version":"7.4","1":"7.4","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"match-up.zip","4":"match-up.zip","src_id":"25676","5":"25676","creation_date":"1512074593","6":"1512074593"}]},"5623":{"script_id":"5623","0":"5623","script_name":"SQHell.vim","1":"SQHell.vim","script_type":"utility","2":"utility","summary":"A lightweight SQL wrapper for vim","3":"A lightweight SQL wrapper for vim","description":"Note that development happens on github\r\nhttps:\/\/github.com\/joereynolds\/SQHell.vim\r\n\r\n# SQHell.vim\r\n\r\nAn SQL wrapper for Vim.\r\nExecute commands, sort results, navigate tables and databases and so much more!\r\n\r\nThe supported providers at the moment are\r\n- MySQL\r\n- Postgres\r\n- Sqlite\r\n\r\n## Examples\r\n\r\n(Gifs are using the data from my punk rock band [bogans](http:\/\/bogans.uk))\r\n### Execute a command using `SQHExecute!`\r\n\r\nExecute a line with `SQHExecute`.\r\n\r\nExecute a visual block with `SQHExecute` over a visual selection.\r\n\r\nExecute an arbitrary command with `SQHExecute!`.\r\n\r\n![](https:\/\/i.imgur.com\/osjpU6u.gif)\r\n\r\n### Execute a file using `SQHExecuteFile`\r\n\r\n`SQHExecuteFile` will work on the current buffer if no file is supplied\r\n\r\n![](https:\/\/i.imgur.com\/67nONqC.gif)\r\n\r\n### Explore the database with buffer aware mappings\r\n\r\n![](https:\/\/i.imgur.com\/E12LHnA.gif)\r\n\r\n## Installation\r\n\r\n\r\n### Vim Plug\r\n\r\n```\r\nPlug 'joereynolds\/SQHell.vim'\r\n```\r\n\r\n## Configuration\r\n\r\nConnection details will need to be supplied in order for SQHell.vim to connect\r\nto your DBMS of choice. The connections are in a dictionary to let you manage\r\nmultiple hosts. By default SQHell uses the 'default' key details (no surprise there)\r\n\r\nExample:\r\n\r\n```\r\nlet g:sqh_connections = {\r\n    \\ 'default': {\r\n    \\   'user': 'root',\r\n    \\   'password': 'testing345',\r\n    \\   'host': 'localhost'\r\n    \\},\r\n    \\ 'live': {\r\n    \\   'user': 'root',\r\n    \\   'password': 'jerw5Y^$Hdfj',\r\n    \\   'host': '46.121.44.392'\r\n    \\}\r\n\\}\r\n```\r\n\r\nYou can use the `SQHSwitchConnection` function to change hosts.\r\ni.e. `SQHSwitchConnection live`\r\n\r\nI **strongly** suggest that the above configuration details are kept *outside*\r\nof version control and gitignored in your global gitignore.\r\n\r\n## Default Keybindings\r\n\r\nSQHell creates 3 filetypes to make navigation a nicer experience.\r\nThese are SQHDatabase, SQHTable, and SQHResult\r\n\r\n### SQHDatabase\r\n\r\nInside an SQHDatabase you can press the following\r\n\r\n`dd` - Drop the database (don't worry there's a prompt).\r\n\r\n`e` - To see all the tables in that database. This will open an SQHTable buffer.\r\n\r\n\r\n### SQHTable\r\n\r\nInside an SQHDatabase you can press the following\r\n\r\n`dd` - Drop the table (don't worry there's a prompt).\r\n\r\n`e` - To see all the results for that table with a limit of `g:sqh_results_limit`.\r\n      This will open an SQHResult buffer\r\n\r\n### SQHResult\r\n\r\nInside an SQHResult you can press the following\r\n\r\n`s` to sort results by the column the cursor is on.\r\n\r\n`S` to sort results by the column the cursor is on (in reverse).\r\n\r\n`dd` to delete the row WHERE the column is the value under the cursor (don't worry... there's a prompt).\r\n\r\n`e` to edit the current row. This will open an SQHInsert buffer\r\n\r\n\r\n### SQHInsert\r\n\r\nInside an SQHInsert you can press the following\r\n\r\n`ZZ` to close and save the edited row. This will reopen the previous SQHResult buffer\r\n\r\n\r\nFor more sorting options, you can use `:SQHSortResults` with extra arguments for the unix sort command, a la `:SQHSortResults -rn`. It will always sort by the column the cursor is located on.\r\n\r\n## Contributing\r\n\r\nPlease see the [Contributing guidelines](CONTRIBUTING.md) if you would like to make SQHell even better!\r\n\r\n## Tests\r\n\r\nTests use [vader](https:\/\/github.com\/junegunn\/vader.vim).\r\n\r\nTests are housed in the `test` directory and can be ran by\r\n`vim`ing into the test file and running `:Vader`.\r\n\r\n## What about dbext, vim-sql-workbench and others?\r\n\r\nDBExt is very featureful (and very good) but comes in at a whopping 12000 lines\r\nof code. By contrast SQHell.vim is a mere ~200 lines\r\n\r\nThe setup and installation process for vim-sql-workbench is something that I\r\naim to avoid with SQHell.vim, ideally a 'set and forget' plugin.\r\n\r\nThere are no clever inferences inside SQHell.vim.","4":"Note that development happens on github\r\nhttps:\/\/github.com\/joereynolds\/SQHell.vim\r\n\r\n# SQHell.vim\r\n\r\nAn SQL wrapper for Vim.\r\nExecute commands, sort results, navigate tables and databases and so much more!\r\n\r\nThe supported providers at the moment are\r\n- MySQL\r\n- Postgres\r\n- Sqlite\r\n\r\n## Examples\r\n\r\n(Gifs are using the data from my punk rock band [bogans](http:\/\/bogans.uk))\r\n### Execute a command using `SQHExecute!`\r\n\r\nExecute a line with `SQHExecute`.\r\n\r\nExecute a visual block with `SQHExecute` over a visual selection.\r\n\r\nExecute an arbitrary command with `SQHExecute!`.\r\n\r\n![](https:\/\/i.imgur.com\/osjpU6u.gif)\r\n\r\n### Execute a file using `SQHExecuteFile`\r\n\r\n`SQHExecuteFile` will work on the current buffer if no file is supplied\r\n\r\n![](https:\/\/i.imgur.com\/67nONqC.gif)\r\n\r\n### Explore the database with buffer aware mappings\r\n\r\n![](https:\/\/i.imgur.com\/E12LHnA.gif)\r\n\r\n## Installation\r\n\r\n\r\n### Vim Plug\r\n\r\n```\r\nPlug 'joereynolds\/SQHell.vim'\r\n```\r\n\r\n## Configuration\r\n\r\nConnection details will need to be supplied in order for SQHell.vim to connect\r\nto your DBMS of choice. The connections are in a dictionary to let you manage\r\nmultiple hosts. By default SQHell uses the 'default' key details (no surprise there)\r\n\r\nExample:\r\n\r\n```\r\nlet g:sqh_connections = {\r\n    \\ 'default': {\r\n    \\   'user': 'root',\r\n    \\   'password': 'testing345',\r\n    \\   'host': 'localhost'\r\n    \\},\r\n    \\ 'live': {\r\n    \\   'user': 'root',\r\n    \\   'password': 'jerw5Y^$Hdfj',\r\n    \\   'host': '46.121.44.392'\r\n    \\}\r\n\\}\r\n```\r\n\r\nYou can use the `SQHSwitchConnection` function to change hosts.\r\ni.e. `SQHSwitchConnection live`\r\n\r\nI **strongly** suggest that the above configuration details are kept *outside*\r\nof version control and gitignored in your global gitignore.\r\n\r\n## Default Keybindings\r\n\r\nSQHell creates 3 filetypes to make navigation a nicer experience.\r\nThese are SQHDatabase, SQHTable, and SQHResult\r\n\r\n### SQHDatabase\r\n\r\nInside an SQHDatabase you can press the following\r\n\r\n`dd` - Drop the database (don't worry there's a prompt).\r\n\r\n`e` - To see all the tables in that database. This will open an SQHTable buffer.\r\n\r\n\r\n### SQHTable\r\n\r\nInside an SQHDatabase you can press the following\r\n\r\n`dd` - Drop the table (don't worry there's a prompt).\r\n\r\n`e` - To see all the results for that table with a limit of `g:sqh_results_limit`.\r\n      This will open an SQHResult buffer\r\n\r\n### SQHResult\r\n\r\nInside an SQHResult you can press the following\r\n\r\n`s` to sort results by the column the cursor is on.\r\n\r\n`S` to sort results by the column the cursor is on (in reverse).\r\n\r\n`dd` to delete the row WHERE the column is the value under the cursor (don't worry... there's a prompt).\r\n\r\n`e` to edit the current row. This will open an SQHInsert buffer\r\n\r\n\r\n### SQHInsert\r\n\r\nInside an SQHInsert you can press the following\r\n\r\n`ZZ` to close and save the edited row. This will reopen the previous SQHResult buffer\r\n\r\n\r\nFor more sorting options, you can use `:SQHSortResults` with extra arguments for the unix sort command, a la `:SQHSortResults -rn`. It will always sort by the column the cursor is located on.\r\n\r\n## Contributing\r\n\r\nPlease see the [Contributing guidelines](CONTRIBUTING.md) if you would like to make SQHell even better!\r\n\r\n## Tests\r\n\r\nTests use [vader](https:\/\/github.com\/junegunn\/vader.vim).\r\n\r\nTests are housed in the `test` directory and can be ran by\r\n`vim`ing into the test file and running `:Vader`.\r\n\r\n## What about dbext, vim-sql-workbench and others?\r\n\r\nDBExt is very featureful (and very good) but comes in at a whopping 12000 lines\r\nof code. By contrast SQHell.vim is a mere ~200 lines\r\n\r\nThe setup and installation process for vim-sql-workbench is something that I\r\naim to avoid with SQHell.vim, ideally a 'set and forget' plugin.\r\n\r\nThere are no clever inferences inside SQHell.vim.","install_details":"Using vim-plug you can just add the following to your .vimrc\r\n\r\nPlug 'joereynolds\/SQHell.vim'","5":"Using vim-plug you can just add the following to your .vimrc\r\n\r\nPlug 'joereynolds\/SQHell.vim'","first_name":"Joe","6":"Joe","last_name":"Reynolds","7":"Reynolds","releases":[{"0":"5623","vim_version":"7.4","1":"7.4","script_version":"0.4","2":"0.4","version_comment":"Features\r\n------------\r\n\r\n- Added support for Sqlite\r\n- Allow results to be in new split each time or stay in current buffer\r\n- Allow postgres to work with multiple queries\r\n- Better documentation","3":"Features\r\n------------\r\n\r\n- Added support for Sqlite\r\n- Allow results to be in new split each time or stay in current buffer\r\n- Allow postgres to work with multiple queries\r\n- Better documentation","package":"sqhell.zip","4":"sqhell.zip","src_id":"25712","5":"25712","creation_date":"1513152771","6":"1513152771"},{"0":"5623","vim_version":"7.0","1":"7.0","script_version":"0.3","2":"0.3","version_comment":"Features\r\n--------\r\n\r\n- Reuse the same buffer instead of creating new ones.\r\n- Add statusline variable\r\n- Codebase now has tests\r\n- Ability to UPDATE a row in an SQHResult\r\n- Sort is now on -n by default\r\n- No longer clobbers the register when entering any SHQ* buffer\r\n- Add command completion for SQHSwitchConnection and SQHExecuteFile\r\n\r\n","3":"Features\r\n--------\r\n\r\n- Reuse the same buffer instead of creating new ones.\r\n- Add statusline variable\r\n- Codebase now has tests\r\n- Ability to UPDATE a row in an SQHResult\r\n- Sort is now on -n by default\r\n- No longer clobbers the register when entering any SHQ* buffer\r\n- Add command completion for SQHSwitchConnection and SQHExecuteFile\r\n\r\n","package":"sqhell.zip","4":"sqhell.zip","src_id":"25704","5":"25704","creation_date":"1512920550","6":"1512920550"},{"0":"5623","vim_version":"7.0","1":"7.0","script_version":"0.2","2":"0.2","version_comment":"Features\r\n------------\r\n\r\n- ability to sort results with SQHSortResults or using S and s on SQHResult filetype\r\n- Improved postgres support\r\n- e on sqhtable works on all providers\r\n- k on sqhtable works on all providers\r\n- e on sqhdatabase works on all providers\r\n- fixed some lint errors\r\n- Merged 3 commands into one, SQHExecute now works on line, block, or argument\r\n","3":"Features\r\n------------\r\n\r\n- ability to sort results with SQHSortResults or using S and s on SQHResult filetype\r\n- Improved postgres support\r\n- e on sqhtable works on all providers\r\n- k on sqhtable works on all providers\r\n- e on sqhdatabase works on all providers\r\n- fixed some lint errors\r\n- Merged 3 commands into one, SQHExecute now works on line, block, or argument\r\n","package":"sqhell.zip","4":"sqhell.zip","src_id":"25682","5":"25682","creation_date":"1512212908","6":"1512212908"},{"0":"5623","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"sqhell.zip","4":"sqhell.zip","src_id":"25675","5":"25675","creation_date":"1512065429","6":"1512065429"}]},"5622":{"script_id":"5622","0":"5622","script_name":"vim-lessmess","1":"vim-lessmess","script_type":"ftplugin","2":"ftplugin","summary":"Removes trailing white-space, fix mixed-indent and remove empty lines at the EOF","3":"Removes trailing white-space, fix mixed-indent and remove empty lines at the EOF","description":"Lessmess: ViM even better whitespaces Plugin\r\n\r\nhttps:\/\/github.com\/mboughaba\/vim-lessmess\r\n\r\nThis plugin is capable of doing the following things for you:\r\n\r\nRemove trailing white-spaces at the end of a line;\r\nFix mixed-indent, in other words, replace all sequences of 'Tab' character with new string of white-space;\r\nRemove empty lines at the end of the file;\r\nBy default the plugin does all of the above when you save a file, but this can be disabled to be able to execute clean-up on demand only. Additionally, The plugin can be configuration to request user confirmation before removing white-spaces.","4":"Lessmess: ViM even better whitespaces Plugin\r\n\r\nhttps:\/\/github.com\/mboughaba\/vim-lessmess\r\n\r\nThis plugin is capable of doing the following things for you:\r\n\r\nRemove trailing white-spaces at the end of a line;\r\nFix mixed-indent, in other words, replace all sequences of 'Tab' character with new string of white-space;\r\nRemove empty lines at the end of the file;\r\nBy default the plugin does all of the above when you save a file, but this can be disabled to be able to execute clean-up on demand only. Additionally, The plugin can be configuration to request user confirmation before removing white-spaces.","install_details":"Instalation\r\n\r\n(natively) Using ViM 8 packages\r\nFirst, create a directory structure representing a plugin-group, say whitespace, as follows:\r\n\r\nmkdir -p ~\/.vim\/pack\/whitespace\/start\/\r\nNext, clone (or alternatively, download the zip, and unzip) the plugins you want to install inside the start directory:\r\n\r\ncd ~\/.vim\/pack\/whitespace\/start\/\r\ngit clone https:\/\/github.com\/mboughaba\/vim-lessmess.git\r\ngit clone https:\/\/github.com\/mboughaba\/vim-lessmess.git\r\n\r\nUsing Vundle\r\nFirst, declare the plugin in you .vimrc\r\nPlugin 'mboughaba\/vim-lessmess'\r\nThen run plugin install command:PluginInstall\r\n\r\nUsing Plug\r\nFirst, declare the plug in you .vimrc\r\nPlug 'mboughaba\/vim-lessmess'\r\nThen run plug install command :PlugInstall","5":"Instalation\r\n\r\n(natively) Using ViM 8 packages\r\nFirst, create a directory structure representing a plugin-group, say whitespace, as follows:\r\n\r\nmkdir -p ~\/.vim\/pack\/whitespace\/start\/\r\nNext, clone (or alternatively, download the zip, and unzip) the plugins you want to install inside the start directory:\r\n\r\ncd ~\/.vim\/pack\/whitespace\/start\/\r\ngit clone https:\/\/github.com\/mboughaba\/vim-lessmess.git\r\ngit clone https:\/\/github.com\/mboughaba\/vim-lessmess.git\r\n\r\nUsing Vundle\r\nFirst, declare the plugin in you .vimrc\r\nPlugin 'mboughaba\/vim-lessmess'\r\nThen run plugin install command:PluginInstall\r\n\r\nUsing Plug\r\nFirst, declare the plug in you .vimrc\r\nPlug 'mboughaba\/vim-lessmess'\r\nThen run plug install command :PlugInstall","first_name":"Mohamed","6":"Mohamed","last_name":"Boughaba","7":"Boughaba","releases":[{"0":"5622","vim_version":"7.2","1":"7.2","script_version":"v1.1.0","2":"v1.1.0","version_comment":"The plugin now support confirmation. By default the feature is disabled.\r\nOnce enabled, the user will be asked before proceeding with the white-space removal.","3":"The plugin now support confirmation. By default the feature is disabled.\r\nOnce enabled, the user will be asked before proceeding with the white-space removal.","package":"vim-lessmess-1.1.0.tar.gz","4":"vim-lessmess-1.1.0.tar.gz","src_id":"25671","5":"25671","creation_date":"1511900653","6":"1511900653"},{"0":"5622","vim_version":"7.2","1":"7.2","script_version":"v1.0.0","2":"v1.0.0","version_comment":"Initial upload","3":"Initial upload","package":"vim-lessmess-1.0.0.tar.gz","4":"vim-lessmess-1.0.0.tar.gz","src_id":"25670","5":"25670","creation_date":"1511900614","6":"1511900614"}]},"5620":{"script_id":"5620","0":"5620","script_name":"mkdx.vim","1":"mkdx.vim","script_type":"ftplugin","2":"ftplugin","summary":"Adds useful mappings for working with markdown files","3":"Adds useful mappings for working with markdown files","description":"This is a mirror of https:\/\/github.com\/SidOfc\/mkdx. The version there will always be up-to-date.\r\n\r\nmkdx.vim is a markdown plugin that aims to reduce the time you spend formatting your markdown documents. It does this by adding some configurable mappings for files with a markdown filetype. Functions are included to handle lists, checkboxes (even lists of checkboxes!), fenced code blocks, shortcuts, headers and links. In addition to that, this plugin provides a mapping to convert a selection of CSV data to a markdown table. and well, lots more even! Visit :h mkdx or :h mkdx-helptags for more information.","4":"This is a mirror of https:\/\/github.com\/SidOfc\/mkdx. The version there will always be up-to-date.\r\n\r\nmkdx.vim is a markdown plugin that aims to reduce the time you spend formatting your markdown documents. It does this by adding some configurable mappings for files with a markdown filetype. Functions are included to handle lists, checkboxes (even lists of checkboxes!), fenced code blocks, shortcuts, headers and links. In addition to that, this plugin provides a mapping to convert a selection of CSV data to a markdown table. and well, lots more even! Visit :h mkdx or :h mkdx-helptags for more information.","install_details":"Plugin installation is possible using a package manager like Vundle (https:\/\/github.com\/VundleVim\/Vundle.vim) or Pathogen (https:\/\/github.com\/tpope\/vim-pathogen).\r\nIf you're downloading the ZIP, I'm just going to assume you know what you're doing and that it is exactly what you want to do, 21st century installation is always an option to fall back to :)\r\nIMPORTANT: Github is updated more frequently, therefore I highly recommend using a package manager instead of doing a manual install, you could be missing some patches otherwise.","5":"Plugin installation is possible using a package manager like Vundle (https:\/\/github.com\/VundleVim\/Vundle.vim) or Pathogen (https:\/\/github.com\/tpope\/vim-pathogen).\r\nIf you're downloading the ZIP, I'm just going to assume you know what you're doing and that it is exactly what you want to do, 21st century installation is always an option to fall back to :)\r\nIMPORTANT: Github is updated more frequently, therefore I highly recommend using a package manager instead of doing a manual install, you could be missing some patches otherwise.","first_name":"Sidney","6":"Sidney","last_name":"Liebrand","7":"Liebrand","releases":[{"0":"5620","vim_version":"8.0","1":"8.0","script_version":"1.10.0","2":"1.10.0","version_comment":"- Add: mkdx#gf_visual function which mimicks mkdx#gf using visually selected text (#119)\r\n- Add: opt-in support for TOML and JSON frontmatter and settings to control which syntax is supported.\r\n- Add: feature to renumber numbered list items with tab\/shift+tab (#113)\r\n- Fix: eager-load settings to ensure settings are properly initialized before loading a markdown file (#125 by @victorkristof)\r\n- Fix: using mkdx#gf with multiple lines with a link always opening first link (#122 by @Delayless)\r\n- Fix: non plaintext files now also open using open instead of in (n)vim (#116 by @kraxli)\r\n- Fix: links with subdomains failed to open using mkdx#gf (#116 by @kraxli)\r\n- Fix: issue when setting let g:markdown_folding = 1 causing Pattern not found: g:mkdx#settings.fold.enable = 0\r\n- Fix: use maparg to check exact mappings exist instead of mapcheck (#112 by @Mayrixon)\r\n- Fix: issue in neovim reporting external links as broken due to unbuffered stdout\r\n- Fix: add missing highlight groups to clear when toggling highlighting on\/off by updating the setting","3":"- Add: mkdx#gf_visual function which mimicks mkdx#gf using visually selected text (#119)\r\n- Add: opt-in support for TOML and JSON frontmatter and settings to control which syntax is supported.\r\n- Add: feature to renumber numbered list items with tab\/shift+tab (#113)\r\n- Fix: eager-load settings to ensure settings are properly initialized before loading a markdown file (#125 by @victorkristof)\r\n- Fix: using mkdx#gf with multiple lines with a link always opening first link (#122 by @Delayless)\r\n- Fix: non plaintext files now also open using open instead of in (n)vim (#116 by @kraxli)\r\n- Fix: links with subdomains failed to open using mkdx#gf (#116 by @kraxli)\r\n- Fix: issue when setting let g:markdown_folding = 1 causing Pattern not found: g:mkdx#settings.fold.enable = 0\r\n- Fix: use maparg to check exact mappings exist instead of mapcheck (#112 by @Mayrixon)\r\n- Fix: issue in neovim reporting external links as broken due to unbuffered stdout\r\n- Fix: add missing highlight groups to clear when toggling highlighting on\/off by updating the setting","package":"mkdx-1.10.0.zip","4":"mkdx-1.10.0.zip","src_id":"27310","5":"27310","creation_date":"1599857775","6":"1599857775"},{"0":"5620","vim_version":"8.0","1":"8.0","script_version":"1.9.4","2":"1.9.4","version_comment":"-  Add: when conceallevel is set, markdown link urls are now also hidden (#108 by @Ginner)\r\n-  Fix: improved cursor position after unwrapping text","3":"-  Add: when conceallevel is set, markdown link urls are now also hidden (#108 by @Ginner)\r\n-  Fix: improved cursor position after unwrapping text","package":"mkdx-1.9.4.zip","4":"mkdx-1.9.4.zip","src_id":"27173","5":"27173","creation_date":"1590211767","6":"1590211767"},{"0":"5620","vim_version":"8.0","1":"8.0","script_version":"1.9.3","2":"1.9.3","version_comment":"-  Add: ability to press enter in the middle of a list-item to split it into two (#107 by @samarulmeu)\r\n-  Fix: wrapping last word shifting word to right in some cases (#101 by @samarulmeu","3":"-  Add: ability to press enter in the middle of a list-item to split it into two (#107 by @samarulmeu)\r\n-  Fix: wrapping last word shifting word to right in some cases (#101 by @samarulmeu","package":"mkdx-1.9.3.zip","4":"mkdx-1.9.3.zip","src_id":"27168","5":"27168","creation_date":"1590098567","6":"1590098567"},{"0":"5620","vim_version":"8.0","1":"8.0","script_version":"1.9.2","2":"1.9.2","version_comment":"-  Add: text wrap mappings can now be prefixed with a count tada (#103 by @victorkristof)\r\n-  Add: ability to toggle bold \/ italic \/ strikethrough \/ inline-code \/ link wrapping (#101 by @victorkristof)\r\n-  Add: enhanced versions of gf and gx and g:mkdx#settings.gf_on_steroids (#100 by @victorkristof and @samarulmeu)\r\n-  Add: support YAML frontmatter\r\n-  Add: ability to create multi-paragraph quotes\r\n-  Add: toggling a quote with a multi-line selection no longer skips empty lines (#94 by @samarulmeu)\r\n-  Add: toggling code will now toggle a code-block instead when in Visual-linewise mode (#93)\r\n-  Add: CriticMarkup highlighting\r\n-  Fix: no-op folding functions when g:markdown_folding is enabled\r\n-  Fix: allow mkdx to work with plasticboy\/vim-markdown enabled\r\n-  Fix: insertion of double quote marks on enter\r\n-  Fix: removed duplicate helptag causing Vundle to crash\r\n-  Fix: 
 TOC not unindenting properly when &sw is 0\r\n-  Fix: typo in README (#88 by @Ginner)\r\n","3":"-  Add: text wrap mappings can now be prefixed with a count tada (#103 by @victorkristof)\r\n-  Add: ability to toggle bold \/ italic \/ strikethrough \/ inline-code \/ link wrapping (#101 by @victorkristof)\r\n-  Add: enhanced versions of gf and gx and g:mkdx#settings.gf_on_steroids (#100 by @victorkristof and @samarulmeu)\r\n-  Add: support YAML frontmatter\r\n-  Add: ability to create multi-paragraph quotes\r\n-  Add: toggling a quote with a multi-line selection no longer skips empty lines (#94 by @samarulmeu)\r\n-  Add: toggling code will now toggle a code-block instead when in Visual-linewise mode (#93)\r\n-  Add: CriticMarkup highlighting\r\n-  Fix: no-op folding functions when g:markdown_folding is enabled\r\n-  Fix: allow mkdx to work with plasticboy\/vim-markdown enabled\r\n-  Fix: insertion of double quote marks on enter\r\n-  Fix: removed duplicate helptag causing Vundle to crash\r\n-  Fix: 
 TOC not unindenting properly when &sw is 0\r\n-  Fix: typo in README (#88 by @Ginner)\r\n","package":"mkdx-1.9.2.zip","4":"mkdx-1.9.2.zip","src_id":"27163","5":"27163","creation_date":"1589775536","6":"1589775536"},{"0":"5620","vim_version":"7.0","1":"7.0","script_version":"1.9.1","2":"1.9.1","version_comment":"- Fix: Handle non-ascii characters in header (TOC) links (https:\/\/github.com\/SidOfc\/mkdx\/pull\/85 by @totpet)","3":"- Fix: Handle non-ascii characters in header (TOC) links (https:\/\/github.com\/SidOfc\/mkdx\/pull\/85 by @totpet)","package":"mkdx-1.9.1.zip","4":"mkdx-1.9.1.zip","src_id":"26485","5":"26485","creation_date":"1557553894","6":"1557553894"},{"0":"5620","vim_version":"7.0","1":"7.0","script_version":"1.9.0","2":"1.9.0","version_comment":"- Add: Table of contents supports configurable nested details tags\r\n- Add: g:mkdx#settings.toc.details.nesting_level to control nested details generation\r\n- Add: g:mkdx#settings.toc.details.child_count to control after how many children a nested details tag will appear\r\n- Add: g:mkdx#settings.toc.details.child_summary to control summary text inside nested details","3":"- Add: Table of contents supports configurable nested details tags\r\n- Add: g:mkdx#settings.toc.details.nesting_level to control nested details generation\r\n- Add: g:mkdx#settings.toc.details.child_count to control after how many children a nested details tag will appear\r\n- Add: g:mkdx#settings.toc.details.child_summary to control summary text inside nested details","package":"mkdx-1.9.0.zip","4":"mkdx-1.9.0.zip","src_id":"26286","5":"26286","creation_date":"1542967513","6":"1542967513"},{"0":"5620","vim_version":"7.0","1":"7.0","script_version":"1.8.3","2":"1.8.3","version_comment":"- Fix: handle unicode characters in list items (#80 - https:\/\/github.com\/SidOfc\/mkdx\/issues\/80)\r\n- Fix: handle unicode characters in CSV (#81 - https:\/\/github.com\/SidOfc\/mkdx\/issues\/81)","3":"- Fix: handle unicode characters in list items (#80 - https:\/\/github.com\/SidOfc\/mkdx\/issues\/80)\r\n- Fix: handle unicode characters in CSV (#81 - https:\/\/github.com\/SidOfc\/mkdx\/issues\/81)","package":"mkdx-1.8.3.zip","4":"mkdx-1.8.3.zip","src_id":"26284","5":"26284","creation_date":"1542782273","6":"1542782273"},{"0":"5620","vim_version":"7.0","1":"7.0","script_version":"1.8.2","2":"1.8.2","version_comment":"- Fix: handle &shiftwidth = 0 (Thanks to @marcdeop -- https:\/\/github.com\/marcdeop).","3":"- Fix: handle &shiftwidth = 0 (Thanks to @marcdeop -- https:\/\/github.com\/marcdeop).","package":"mkdx-1.8.2.zip","4":"mkdx-1.8.2.zip","src_id":"26271","5":"26271","creation_date":"1542175571","6":"1542175571"},{"0":"5620","vim_version":"7.0","1":"7.0","script_version":"1.8.1","2":"1.8.1","version_comment":"- Add: Mkdx can convert tables back to CSV\r\n- Fix: Only open quickfix when broken links are present(#56)\r\n- Fix: Table highlighting now stops at the end of a table (#57)\r\n- Fix: Empty cells in CSV also get a border (#61)\r\n- Fix: All hasmapto calls are mode specific (#64)\r\n- Fix: g:mkdx#settings.restore_visual can now be disabled during runtime (#65)\r\n- Fix: Wrapping at end of line no longer breaks when line ends with non word characters (#67)\r\n- Fix: No longer pollute register when updating table of contents (#68)\r\n- Fix: Empty setex-style headers are no longer added to quickfix headers or the table of contents (#69)\r\n- Fix: Always empty quickfix list before showing dead links (#70)","3":"- Add: Mkdx can convert tables back to CSV\r\n- Fix: Only open quickfix when broken links are present(#56)\r\n- Fix: Table highlighting now stops at the end of a table (#57)\r\n- Fix: Empty cells in CSV also get a border (#61)\r\n- Fix: All hasmapto calls are mode specific (#64)\r\n- Fix: g:mkdx#settings.restore_visual can now be disabled during runtime (#65)\r\n- Fix: Wrapping at end of line no longer breaks when line ends with non word characters (#67)\r\n- Fix: No longer pollute register when updating table of contents (#68)\r\n- Fix: Empty setex-style headers are no longer added to quickfix headers or the table of contents (#69)\r\n- Fix: Always empty quickfix list before showing dead links (#70)","package":"mkdx-1.8.1.zip","4":"mkdx-1.8.1.zip","src_id":"26222","5":"26222","creation_date":"1536517370","6":"1536517370"},{"0":"5620","vim_version":"7.0","1":"7.0","script_version":"1.8.0","2":"1.8.0","version_comment":"- Add: Setting to control updating TOC before writing the buffer (https:\/\/github.com\/SidOfc\/mkdx\/pull\/54)\r\n- Fix: Unable to position TOC as last header (https:\/\/github.com\/SidOfc\/mkdx\/pull\/53)","3":"- Add: Setting to control updating TOC before writing the buffer (https:\/\/github.com\/SidOfc\/mkdx\/pull\/54)\r\n- Fix: Unable to position TOC as last header (https:\/\/github.com\/SidOfc\/mkdx\/pull\/53)","package":"mkdx-1.8.0.zip","4":"mkdx-1.8.0.zip","src_id":"26161","5":"26161","creation_date":"1533334680","6":"1533334680"},{"0":"5620","vim_version":"7.0","1":"7.0","script_version":"1.7.1","2":"1.7.1","version_comment":"- Add: Pressing  after an inline list item creates a new list item instead of a blank line.","3":"- Add: Pressing  after an inline list item creates a new list item instead of a blank line.","package":"mkdx-1.7.1.zip","4":"mkdx-1.7.1.zip","src_id":"26154","5":"26154","creation_date":"1533012783","6":"1533012783"},{"0":"5620","vim_version":"7.0","1":"7.0","script_version":"1.7.0","2":"1.7.0","version_comment":"Add: Support Setex style headings (- \/ = characters below nonblank line)\r\nAdd: Support Setex style headings in completion menu\r\nAdd: Support Setex style headings in TOC generation\r\n- Add: Support Setex style headings in header listing\r\n- Add: Setting to allow customizing strikethrough style (#49)\r\n- Fix: TOC without any nested elements created too many closing tags when generated using 
 tag\r\n- Fix: Non-list items sometimes got detected as list items when starting with a number on shift+O\r\n- Fix: overriding g:mkdx#settings with has('*dictwatcheradd') crashing Vim","3":"Add: Support Setex style headings (- \/ = characters below nonblank line)\r\nAdd: Support Setex style headings in completion menu\r\nAdd: Support Setex style headings in TOC generation\r\n- Add: Support Setex style headings in header listing\r\n- Add: Setting to allow customizing strikethrough style (#49)\r\n- Fix: TOC without any nested elements created too many closing tags when generated using 
 tag\r\n- Fix: Non-list items sometimes got detected as list items when starting with a number on shift+O\r\n- Fix: overriding g:mkdx#settings with has('*dictwatcheradd') crashing Vim","package":"mkdx-1.7.0.zip","4":"mkdx-1.7.0.zip","src_id":"26072","5":"26072","creation_date":"1529875941","6":"1529875941"},{"0":"5620","vim_version":"7.0","1":"7.0","script_version":"1.6.1","2":"1.6.1","version_comment":"Add: Highlighting for tables,  shortcuts and _**bolditalic**_.\r\nAdd: shift+enter support to create multiline items (#44).\r\nFix: shift+enter no longer require double escape to exit insert mode.\r\nFix: Dead link detection, incorrect external label and relative links were always skipped.\r\nFix: grep and ggrep do not count line column properly (byte-offset is converted now).","3":"Add: Highlighting for tables,  shortcuts and _**bolditalic**_.\r\nAdd: shift+enter support to create multiline items (#44).\r\nFix: shift+enter no longer require double escape to exit insert mode.\r\nFix: Dead link detection, incorrect external label and relative links were always skipped.\r\nFix: grep and ggrep do not count line column properly (byte-offset is converted now).","package":"mkdx-1.6.1.zip","4":"mkdx-1.6.1.zip","src_id":"25979","5":"25979","creation_date":"1526317485","6":"1526317485"},{"0":"5620","vim_version":"7.0","1":"7.0","script_version":"1.6.0","2":"1.6.0","version_comment":"\r\nFix: Handle URLS starting with \"..\/..\/\" correctly.\r\n- Fix: Removed hardcoded hashtag as header identifier in function.\r\n- Fix: (#35) Generating a TOC in the details didn't generate the final closing tags.\r\n- Fix: (#40) Shift-o (O) prepending a list item to a line starting with a number.\r\n- Fix: (#39) Set autoindent, it is enabled by default in Neovim but disabled by default in Vim.\r\n- Add: (#41) Fold support for the table of contents and fenced code blocks (opt-in).\r\n- Add setting to enable folding: g:mkdx#settings.fold.enable = 0.\r\n- Add setting to modify what is folded: g:mkdx#settings.fold.components = ['toc', 'fence'].\r\n- NEOVIM\r\n    - Add: (#32) dictionarywatcher that watches settings and immediately updates the document.\r\n    - Add: setting to control auto-updates: g:mkdx#settings.auto_update.enable = 1.","3":"\r\nFix: Handle URLS starting with \"..\/..\/\" correctly.\r\n- Fix: Removed hardcoded hashtag as header identifier in function.\r\n- Fix: (#35) Generating a TOC in the details didn't generate the final closing tags.\r\n- Fix: (#40) Shift-o (O) prepending a list item to a line starting with a number.\r\n- Fix: (#39) Set autoindent, it is enabled by default in Neovim but disabled by default in Vim.\r\n- Add: (#41) Fold support for the table of contents and fenced code blocks (opt-in).\r\n- Add setting to enable folding: g:mkdx#settings.fold.enable = 0.\r\n- Add setting to modify what is folded: g:mkdx#settings.fold.components = ['toc', 'fence'].\r\n- NEOVIM\r\n    - Add: (#32) dictionarywatcher that watches settings and immediately updates the document.\r\n    - Add: setting to control auto-updates: g:mkdx#settings.auto_update.enable = 1.","package":"mkdx-1.6.0.zip","4":"mkdx-1.6.0.zip","src_id":"25974","5":"25974","creation_date":"1526016536","6":"1526016536"},{"0":"5620","vim_version":"7.0","1":"7.0","script_version":"1.5.1","2":"1.5.1","version_comment":"- dead link detection (https:\/\/github.com\/sidofc\/mkdx#dead-link-detection) uses a grep program and job when available\r\n- jumping to headers (https:\/\/github.com\/sidofc\/mkdx#jump-to-header) uses a grep program and job when available\r\n- insert autocompletion (https:\/\/github.com\/sidofc\/mkdx#insert-mode-fragment-completion) uses a grep program and job when available","3":"- dead link detection (https:\/\/github.com\/sidofc\/mkdx#dead-link-detection) uses a grep program and job when available\r\n- jumping to headers (https:\/\/github.com\/sidofc\/mkdx#jump-to-header) uses a grep program and job when available\r\n- insert autocompletion (https:\/\/github.com\/sidofc\/mkdx#insert-mode-fragment-completion) uses a grep program and job when available","package":"mkdx-1.5.1.zip","4":"mkdx-1.5.1.zip","src_id":"25961","5":"25961","creation_date":"1525509356","6":"1525509356"},{"0":"5620","vim_version":"7.0","1":"7.0","script_version":"1.5.0","2":"1.5.0","version_comment":"Add insert mode completion for fragment links (https:\/\/github.com\/SidOfc\/mkdx#insert-mode-fragment-completion).\r\n- Add setting (https:\/\/github.com\/SidOfc\/mkdx#gmkdxsettingslinksfragmentcomplete) to control completions.\r\n- Add support for anchor fragment links (#24 (https:\/\/github.com\/SidOfc\/mkdx\/issues\/24)) (<\/a> \/ <\/a>) for jumping (https:\/\/github.com\/SidOfc\/mkdx#jump-to-header), detection (https:\/\/github.com\/SidOfc\/mkdx#dead-link-detection) and completion (https:\/\/github.com\/SidOfc\/mkdx#insert-mode-fragment-completion).\r\n- Fix issue where double slashes in the URL would not be removed in external link checks.\r\n- Fix nested <\/a> tags in generated TOC links.","3":"Add insert mode completion for fragment links (https:\/\/github.com\/SidOfc\/mkdx#insert-mode-fragment-completion).\r\n- Add setting (https:\/\/github.com\/SidOfc\/mkdx#gmkdxsettingslinksfragmentcomplete) to control completions.\r\n- Add support for anchor fragment links (#24 (https:\/\/github.com\/SidOfc\/mkdx\/issues\/24)) (<\/a> \/ <\/a>) for jumping (https:\/\/github.com\/SidOfc\/mkdx#jump-to-header), detection (https:\/\/github.com\/SidOfc\/mkdx#dead-link-detection) and completion (https:\/\/github.com\/SidOfc\/mkdx#insert-mode-fragment-completion).\r\n- Fix issue where double slashes in the URL would not be removed in external link checks.\r\n- Fix nested <\/a> tags in generated TOC links.","package":"mkdx-1.5.0.zip","4":"mkdx-1.5.0.zip","src_id":"25952","5":"25952","creation_date":"1524933685","6":"1524933685"},{"0":"5620","vim_version":"7.0","1":"7.0","script_version":"1.4.3","2":"1.4.3","version_comment":"(#17 - https:\/\/github.com\/SidOfc\/mkdx\/issues\/17) Add a mapping to go to fragment link location. (https:\/\/github.com\/sidofc\/mkdx#jump-to-header)\r\n(#18 - https:\/\/github.com\/SidOfc\/mkdx\/issues\/18) Add alignment options for columns in a table generated from CSV. (https:\/\/github.com\/sidofc\/mkdx#gmkdxsettingstablealign)\r\n(#18 - https:\/\/github.com\/SidOfc\/mkdx\/issues\/18) Add alignment options for specific column names or indexes in a table generated from CSV. (https:\/\/github.com\/sidofc\/mkdx#gmkdxsettingstablealign)\r\nList items require a space after them to be recognized as a list item.","3":"(#17 - https:\/\/github.com\/SidOfc\/mkdx\/issues\/17) Add a mapping to go to fragment link location. (https:\/\/github.com\/sidofc\/mkdx#jump-to-header)\r\n(#18 - https:\/\/github.com\/SidOfc\/mkdx\/issues\/18) Add alignment options for columns in a table generated from CSV. (https:\/\/github.com\/sidofc\/mkdx#gmkdxsettingstablealign)\r\n(#18 - https:\/\/github.com\/SidOfc\/mkdx\/issues\/18) Add alignment options for specific column names or indexes in a table generated from CSV. (https:\/\/github.com\/sidofc\/mkdx#gmkdxsettingstablealign)\r\nList items require a space after them to be recognized as a list item.","package":"mkdx-1.4.3.zip","4":"mkdx-1.4.3.zip","src_id":"25948","5":"25948","creation_date":"1524788275","6":"1524788275"},{"0":"5620","vim_version":"7.0","1":"7.0","script_version":"1.4.2","2":"1.4.2","version_comment":"- Convert CSV to table (https:\/\/github.com\/SidOfc\/mkdx#convert-csv-to-table) now also supports quoted CSV and TSV data","3":"- Convert CSV to table (https:\/\/github.com\/SidOfc\/mkdx#convert-csv-to-table) now also supports quoted CSV and TSV data","package":"mkdx-1.4.2.zip","4":"mkdx-1.4.2.zip","src_id":"25922","5":"25922","creation_date":"1523814745","6":"1523814745"},{"0":"5620","vim_version":"7.0","1":"7.0","script_version":"1.4.1","2":"1.4.1","version_comment":"- Dead link detection will now also scan any `href=\"\"` attribute content.","3":"- Dead link detection will now also scan any `href=\"\"` attribute content.","package":"mkdx-1.4.1.zip","4":"mkdx-1.4.1.zip","src_id":"25914","5":"25914","creation_date":"1523202981","6":"1523202981"},{"0":"5620","vim_version":"7.0","1":"7.0","script_version":"1.4.0","2":"1.4.0","version_comment":"- Update Dead link detection (https:\/\/github.com\/SidOfc\/mkdx#dead-link-detection) to include support for external and relative links.\r\n- Add new settings (https:\/\/github.com\/SidOfc\/mkdx#gmkdxsettingslinksexternalenable) to control request timeout and relative link host etc.","3":"- Update Dead link detection (https:\/\/github.com\/SidOfc\/mkdx#dead-link-detection) to include support for external and relative links.\r\n- Add new settings (https:\/\/github.com\/SidOfc\/mkdx#gmkdxsettingslinksexternalenable) to control request timeout and relative link host etc.","package":"mkdx-1.4.0.zip","4":"mkdx-1.4.0.zip","src_id":"25913","5":"25913","creation_date":"1523189700","6":"1523189700"},{"0":"5620","vim_version":"7.0","1":"7.0","script_version":"1.3.0","2":"1.3.0","version_comment":"- Added feature: Dead fragment link detection\r\n- Automatically remove \"r\" from \"formatoptions\" inside markdown files (buffer local override)\r\n- Fix table of contents eating a header when there is no blank line between the table of contents and the next heading\r\n- Cursor stays on the same line after updating table of contents\r\n- mkdx#QuickfixHeaders() shows amount of headers and doesn't open quickfix when no headers are present.","3":"- Added feature: Dead fragment link detection\r\n- Automatically remove \"r\" from \"formatoptions\" inside markdown files (buffer local override)\r\n- Fix table of contents eating a header when there is no blank line between the table of contents and the next heading\r\n- Cursor stays on the same line after updating table of contents\r\n- mkdx#QuickfixHeaders() shows amount of headers and doesn't open quickfix when no headers are present.","package":"mkdx-1.3.0.zip","4":"mkdx-1.3.0.zip","src_id":"25910","5":"25910","creation_date":"1522680225","6":"1522680225"},{"0":"5620","vim_version":"7.0","1":"7.0","script_version":"1.2.0","2":"1.2.0","version_comment":"Added feature: Support generating table of contents inside 
 tag. (https:\/\/github.com\/sidofc\/mkdx#generate-or-update-toc-as-details)","3":"Added feature: Support generating table of contents inside 
 tag. (https:\/\/github.com\/sidofc\/mkdx#generate-or-update-toc-as-details)","package":"mkdx-1.2.0.zip","4":"mkdx-1.2.0.zip","src_id":"25908","5":"25908","creation_date":"1522586231","6":"1522586231"},{"0":"5620","vim_version":"7.0","1":"7.0","script_version":"1.1.0","2":"1.1.0","version_comment":"- Stricter rules for highlighting (do not highlight bold markers at start of line as list items).\r\n- Fix TOC links using headings containing  tags.\r\n- Fix deep merging of `g:mkdx#settings` hash.\r\n- Add setting to place TOC in fixed position.","3":"- Stricter rules for highlighting (do not highlight bold markers at start of line as list items).\r\n- Fix TOC links using headings containing  tags.\r\n- Fix deep merging of `g:mkdx#settings` hash.\r\n- Add setting to place TOC in fixed position.","package":"mkdx-1.1.0.zip","4":"mkdx-1.1.0.zip","src_id":"25906","5":"25906","creation_date":"1522525512","6":"1522525512"},{"0":"5620","vim_version":"7.0","1":"7.0","script_version":"1.0.2","2":"1.0.2","version_comment":"- Fix incorrect mapping detection\r\n- Update README, add remapping section","3":"- Fix incorrect mapping detection\r\n- Update README, add remapping section","package":"mkdx-1.0.2.zip","4":"mkdx-1.0.2.zip","src_id":"25902","5":"25902","creation_date":"1521984357","6":"1521984357"},{"0":"5620","vim_version":"7.0","1":"7.0","script_version":"1.0.1","2":"1.0.1","version_comment":"- All mappings now use (mkdx-*) structure","3":"- All mappings now use (mkdx-*) structure","package":"mkdx-1.0.1.zip","4":"mkdx-1.0.1.zip","src_id":"25901","5":"25901","creation_date":"1521917269","6":"1521917269"},{"0":"5620","vim_version":"7.0","1":"7.0","script_version":"1.0.0","2":"1.0.0","version_comment":"- Fix #11 - `mkdx#ToggleQuote` inserting `0` on empty lines\r\n- Fix #12 - Update (task-)lists inside a quote\r\n- Fix #13 - Add \/ remove (task-)lists inside a quote\r\n- Add `(mkdx-o)` in favor of directly mapping to `A` to trigger `mkdx#EnterHandler`\r\n- Add `(mkdx-shift-o)` in favor of directly mapping to `:call mkdx#ShiftOHandler()`","3":"- Fix #11 - `mkdx#ToggleQuote` inserting `0` on empty lines\r\n- Fix #12 - Update (task-)lists inside a quote\r\n- Fix #13 - Add \/ remove (task-)lists inside a quote\r\n- Add `(mkdx-o)` in favor of directly mapping to `A` to trigger `mkdx#EnterHandler`\r\n- Add `(mkdx-shift-o)` in favor of directly mapping to `:call mkdx#ShiftOHandler()`","package":"mkdx-1.0.0.zip","4":"mkdx-1.0.0.zip","src_id":"25900","5":"25900","creation_date":"1521904444","6":"1521904444"},{"0":"5620","vim_version":"7.0","1":"7.0","script_version":"0.9.0","2":"0.9.0","version_comment":"- Fix `mkdx#HeaderToQF` wrong function ref.\r\n- Fix `g:mkdx#settings.enter.enable` and `g:mkdx#settings.enter.shifto` can be disabled during runtime.\r\n- Fix insert mode \"\\~\\~\\~\" and \"\\`\\`\\`\" recursion.\r\n- Add support for [toggling \\ shortcuts](#toggling-kbd--shortcuts) in normal and visual mode.","3":"- Fix `mkdx#HeaderToQF` wrong function ref.\r\n- Fix `g:mkdx#settings.enter.enable` and `g:mkdx#settings.enter.shifto` can be disabled during runtime.\r\n- Fix insert mode \"\\~\\~\\~\" and \"\\`\\`\\`\" recursion.\r\n- Add support for [toggling \\ shortcuts](#toggling-kbd--shortcuts) in normal and visual mode.","package":"mkdx-0.9.0.zip","4":"mkdx-0.9.0.zip","src_id":"25805","5":"25805","creation_date":"1517164149","6":"1517164149"},{"0":"5620","vim_version":"7.0","1":"7.0","script_version":"0.8.0","2":"0.8.0","version_comment":"- Fix some issues with `mkdx#WrapLink`.\r\n- `mkdx#WrapLink` handles selections that include newline character correctly.\r\n- Headers can now also be toggled on \/ off using `mkdx#ToggleHeader`.\r\n- When deleting a list item anywhere in the list, following list items are decremented by 1.\r\n- Added more tests for\r\n    - decrementing list items\r\n    - promoting \/ demoting headers\r\n    - Wrapping links and images\r\n","3":"- Fix some issues with `mkdx#WrapLink`.\r\n- `mkdx#WrapLink` handles selections that include newline character correctly.\r\n- Headers can now also be toggled on \/ off using `mkdx#ToggleHeader`.\r\n- When deleting a list item anywhere in the list, following list items are decremented by 1.\r\n- Added more tests for\r\n    - decrementing list items\r\n    - promoting \/ demoting headers\r\n    - Wrapping links and images\r\n","package":"mkdx-0.8.0.zip","4":"mkdx-0.8.0.zip","src_id":"25787","5":"25787","creation_date":"1516538849","6":"1516538849"},{"0":"5620","vim_version":"7.0","1":"7.0","script_version":"0.7.1","2":"0.7.1","version_comment":"Adds shift-o support alongside regular o and enter in insert mode. when pressing shift-o in the middle of a list, an item will be inserted above the current line and the cursor will be moved there.\r\n","3":"Adds shift-o support alongside regular o and enter in insert mode. when pressing shift-o in the middle of a list, an item will be inserted above the current line and the cursor will be moved there.\r\n","package":"mkdx-0.7.1.zip","4":"mkdx-0.7.1.zip","src_id":"25763","5":"25763","creation_date":"1515870371","6":"1515870371"},{"0":"5620","vim_version":"7.0","1":"7.0","script_version":"0.7.0","2":"0.7.0","version_comment":"Adds menu support if it is available to the installed vim. menu will be displayed in the top bar in gvim\/macvim and can be accessed through :menu Plugin.mkdx from terminal vims that support it.","3":"Adds menu support if it is available to the installed vim. menu will be displayed in the top bar in gvim\/macvim and can be accessed through :menu Plugin.mkdx from terminal vims that support it.","package":"mkdx-0.7.0.zip","4":"mkdx-0.7.0.zip","src_id":"25762","5":"25762","creation_date":"1515857929","6":"1515857929"},{"0":"5620","vim_version":"7.0","1":"7.0","script_version":"0.6.1","2":"0.6.1","version_comment":"Fixes space prepended when wrapping the only word on a line in a link","3":"Fixes space prepended when wrapping the only word on a line in a link","package":"mkdx-0.6.1.zip","4":"mkdx-0.6.1.zip","src_id":"25757","5":"25757","creation_date":"1515617871","6":"1515617871"},{"0":"5620","vim_version":"7.0","1":"7.0","script_version":"0.6.0","2":"0.6.0","version_comment":"Adds opt-in highlighting for different checkbox states. See GH README for gifs. or :h mkdx-highlighting within Vim for more information.","3":"Adds opt-in highlighting for different checkbox states. See GH README for gifs. or :h mkdx-highlighting within Vim for more information.","package":"mkdx-0.6.0.zip","4":"mkdx-0.6.0.zip","src_id":"25753","5":"25753","creation_date":"1515338750","6":"1515338750"},{"0":"5620","vim_version":"7.0","1":"7.0","script_version":"0.5.0","2":"0.5.0","version_comment":"Added feature to open the quickfix list containing all markdown headers in the current file.","3":"Added feature to open the quickfix list containing all markdown headers in the current file.","package":"mkdx-0.5.0.zip","4":"mkdx-0.5.0.zip","src_id":"25751","5":"25751","creation_date":"1515244186","6":"1515244186"},{"0":"5620","vim_version":"7.0","1":"7.0","script_version":"0.4.3.1","2":"0.4.3.1","version_comment":"HOTFIX: EnterHandler not inserting enters in some cases (prepends a \"0\" to the current line instead)","3":"HOTFIX: EnterHandler not inserting enters in some cases (prepends a \"0\" to the current line instead)","package":"mkdx-0.4.3.1.zip","4":"mkdx-0.4.3.1.zip","src_id":"25750","5":"25750","creation_date":"1515191753","6":"1515191753"},{"0":"5620","vim_version":"7.0","1":"7.0","script_version":"0.4.3","2":"0.4.3","version_comment":"Complete rewrite of mkdx#EnterHandler.\r\nTask lists are updated when an item is removed (pressing enter twice at the end of an existing list item).\r\nBetter updating \/ inserting of regular lines of checkboxes.\r\nHappy new year too, everyone :)","3":"Complete rewrite of mkdx#EnterHandler.\r\nTask lists are updated when an item is removed (pressing enter twice at the end of an existing list item).\r\nBetter updating \/ inserting of regular lines of checkboxes.\r\nHappy new year too, everyone :)","package":"mkdx-0.4.3.zip","4":"mkdx-0.4.3.zip","src_id":"25746","5":"25746","creation_date":"1514850810","6":"1514850810"},{"0":"5620","vim_version":"7.0","1":"7.0","script_version":"0.4.2","2":"0.4.2","version_comment":"Fixes issue where enter would be offset by 1 character horizontally.\r\nIn addition to completing list items, quotes and checklist items, pressing enter after a checkbox task will now add a checkbox on the new line as well :)\r\nMajor settings refactor that maintains backward compatibility. See :h mkdx-var-settings for more information.","3":"Fixes issue where enter would be offset by 1 character horizontally.\r\nIn addition to completing list items, quotes and checklist items, pressing enter after a checkbox task will now add a checkbox on the new line as well :)\r\nMajor settings refactor that maintains backward compatibility. See :h mkdx-var-settings for more information.","package":"mkdx-0.4.2.zip","4":"mkdx-0.4.2.zip","src_id":"25745","5":"25745","creation_date":"1514697345","6":"1514697345"},{"0":"5620","vim_version":"7.0","1":"7.0","script_version":"0.4.1","2":"0.4.1","version_comment":"Adds better support for toggling from and to specific types of lines such as checkboxes, checklists and lists.\r\nRENAMED: mkdx#ToggleCheckbox to mkdx#ToggleCheckboxState.","3":"Adds better support for toggling from and to specific types of lines such as checkboxes, checklists and lists.\r\nRENAMED: mkdx#ToggleCheckbox to mkdx#ToggleCheckboxState.","package":"mkdx-0.4.1.zip","4":"mkdx-0.4.1.zip","src_id":"25744","5":"25744","creation_date":"1514656041","6":"1514656041"},{"0":"5620","vim_version":"7.0","1":"7.0","script_version":"0.4.0","2":"0.4.0","version_comment":"This version adds support for toggling between regular lines and list\/checkbox\/checklist lines.\r\nIt also fixes an issue where pressing ENTER at the start of a line would actually execute ENTER after the first character (thus leaving a character \"hanging\").\r\nWhen updating the table of contents, the cursor position is correctly restored to its original position.","3":"This version adds support for toggling between regular lines and list\/checkbox\/checklist lines.\r\nIt also fixes an issue where pressing ENTER at the start of a line would actually execute ENTER after the first character (thus leaving a character \"hanging\").\r\nWhen updating the table of contents, the cursor position is correctly restored to its original position.","package":"mkdx-0.4.0.zip","4":"mkdx-0.4.0.zip","src_id":"25737","5":"25737","creation_date":"1514133468","6":"1514133468"},{"0":"5620","vim_version":"7.0","1":"7.0","script_version":"0.3.0","2":"0.3.0","version_comment":"Add support for wrapping text in bold, italic, strikethrough and inline-code in normal and visual mode.\r\nFixes a bug where wrapping link at end of line would not respect spacing.","3":"Add support for wrapping text in bold, italic, strikethrough and inline-code in normal and visual mode.\r\nFixes a bug where wrapping link at end of line would not respect spacing.","package":"mkdx-0.3.0.zip","4":"mkdx-0.3.0.zip","src_id":"25719","5":"25719","creation_date":"1513630956","6":"1513630956"},{"0":"5620","vim_version":"7.0","1":"7.0","script_version":"0.2.0","2":"0.2.0","version_comment":"Add support for wrapping images in image links and pressing  in a tasklist now updates the tasklist after adding a new empty task.","3":"Add support for wrapping images in image links and pressing  in a tasklist now updates the tasklist after adding a new empty task.","package":"mkdx-0.2.0.zip","4":"mkdx-0.2.0.zip","src_id":"25697","5":"25697","creation_date":"1512729854","6":"1512729854"},{"0":"5620","vim_version":"7.0","1":"7.0","script_version":"0.1.8","2":"0.1.8","version_comment":"This version provides better support for malformed indentation when updating checkboxes in nested lists.","3":"This version provides better support for malformed indentation when updating checkboxes in nested lists.","package":"mkdx-0.1.8.zip","4":"mkdx-0.1.8.zip","src_id":"25691","5":"25691","creation_date":"1512585743","6":"1512585743"},{"0":"5620","vim_version":"7.0","1":"7.0","script_version":"0.1.7","2":"0.1.7","version_comment":"This version adds support for updating parent and child checklist items in markdown lists.","3":"This version adds support for updating parent and child checklist items in markdown lists.","package":"mkdx-0.1.7.zip","4":"mkdx-0.1.7.zip","src_id":"25684","5":"25684","creation_date":"1512344433","6":"1512344433"},{"0":"5620","vim_version":"7.0","1":"7.0","script_version":"0.0.7","2":"0.0.7","version_comment":"This version adds support for checkboxes in list items. When a checkbox is detected on the line where  was pressed, an empty checkbox will be inserted in the new empty line.","3":"This version adds support for checkboxes in list items. When a checkbox is detected on the line where  was pressed, an empty checkbox will be inserted in the new empty line.","package":"mkdx-0.0.7.zip","4":"mkdx-0.0.7.zip","src_id":"25660","5":"25660","creation_date":"1511644631","6":"1511644631"},{"0":"5620","vim_version":"7.0","1":"7.0","script_version":"0.0.6","2":"0.0.6","version_comment":"Initial upload","3":"Initial upload","package":"mkdx-0.0.6.zip","4":"mkdx-0.0.6.zip","src_id":"25659","5":"25659","creation_date":"1511633531","6":"1511633531"}]},"5619":{"script_id":"5619","0":"5619","script_name":"SearchAsQuickJump","1":"SearchAsQuickJump","script_type":"utility","2":"utility","summary":"Quick search without affecting 'hlsearch', search pattern and history.","3":"Quick search without affecting 'hlsearch', search pattern and history.","description":"DESCRIPTION\r\nI use the built-in search (\/, ?, n and N) for two different purposes:\r\n1. For quick mouseless navigation to a place not far away, or as a {motion}\r\n   e.g. in d\/{pattern}\/.\r\n2. For actual searches, when I'm looking for and examining all occurrences\r\n   inside the buffer or even multiple windows.\r\n\r\nUnfortunately, there's a tension in how to configure the search-related\r\nsettings: For quick searches, highlighting of matches is not important, as my\r\neyes are already focused on the target text, I just want to get there with the\r\nfewest keystrokes, and figured that a search for \"\/:le\" is faster than\r\n\"3fA4whhh\". Because the search pattern is mostly incomplete, the highlighting\r\nshould not continue to distract after the search; it should be off (but\r\n'incsearch' helps to recognize when enough of the pattern is typed to reach\r\nthe desired location). Likewise, the search pattern is useless in the search\r\nhistory and as the last pattern for the n command, as I am unlikely to\r\nrepeat that search. On the other hand, for actual searches, history recall,\r\nrepeated search and highlighting of matches are vital and central to the task.\r\n\r\nHow can this be reconciled? This plugin sets up alternative mappings to the\r\n key which normally concludes entering of the search pattern in\r\ncommand-line mode. By pressing , a quick search is triggered instead of\r\na normal one. This quick search does not use search highlighting and the\r\nsearch pattern is not added to the search history, so it can be used without\r\naffecting the normal search. Likewise, in a non-search command-line, the\r\nexecuted command (for example, a :substitute) does not affect the current\r\nsearch pattern and search history.\r\n\r\nNext \/ previous matches can be jumped to via separate mappings, but not via\r\nthe default n \/ N commands. (Even if the integration with the SearchRepeat\r\nplugin is used; contrary to most other integrations, this quick search must be\r\nexplicitly activated via the gnq \/ gNq mapping. )\r\n\r\nSEE ALSO\r\n- Check out the SearchSpecial.vim plugin page (vimscript #4948) for a full\r\n  list of special searches powered by it.\r\n- Check out the SearchRepeat.vim plugin page (vimscript #4949) for a full\r\n  list of custom searches that integrate with it.\r\n\r\nUSAGE\r\n\/{pattern}[\/]     When a search via \/ or ? is sent off by pressing\r\n?{pattern}[?]     , a quick forward \/ backward search is\r\n                        performed. Matches will not be highlighted via\r\n                        'hlsearch', and the search pattern will not be added\r\n                        to the search history or used as the last pattern for\r\n                        n \/ N search repeats.\r\n                        Use this for a quick search without the formality and\r\n                        persistence of a normal search, which can still be\r\n                        obtained by concluding the pattern input with the\r\n                        default  at the end.\r\n                        In the :... Ex command-line (and also >... debug\r\n                        command-line), any change to the search pattern and\r\n                        history is undone. For example, this is useful to do a\r\n                        substitution without affecting the current search:\r\n                        \/foo :s\/X\/Y\/ n (keep searching for \"foo\")\r\n\r\nThe special searches all start with 'go...' (mnemonic: \"go once to special\r\nmatch\"); and come in search forward (go...) and backward (gO...) variants.\r\n\r\n[count]goq \/ gOq        Search forward \/ backward to the [count]'th occurrence\r\n                        of the quick search pattern. This is the equivalent to\r\n                        the default n \/ N search repeat commands.\r\n\r\nThe following commands are optional; cp. the SearchAsQuickJump-configuration\r\nsection below.\r\n\r\nq*, q#                  Search forward \/ backward for the [count]'th\r\n                        occurrence of the word nearest to the cursor.\r\ngq*, gq#                Like above, but don't put \"\\<\" and \"\\>\" around the\r\n                        word. This makes the search also find matches that are\r\n                        not a whole word.\r\n{Visual}q*              Do a quick search forward \/ backward for the [count]'th\r\n{Visual}q#              occurrence of the current selection, like the built-in\r\n                        gstar and g# commands.\r\n\r\n                        These mappings are based on the built-in star and\r\n                        # commands. Like with them, 'ignorecase' is used,\r\n                        'smartcase' is not.","4":"DESCRIPTION\r\nI use the built-in search (\/, ?, n and N) for two different purposes:\r\n1. For quick mouseless navigation to a place not far away, or as a {motion}\r\n   e.g. in d\/{pattern}\/.\r\n2. For actual searches, when I'm looking for and examining all occurrences\r\n   inside the buffer or even multiple windows.\r\n\r\nUnfortunately, there's a tension in how to configure the search-related\r\nsettings: For quick searches, highlighting of matches is not important, as my\r\neyes are already focused on the target text, I just want to get there with the\r\nfewest keystrokes, and figured that a search for \"\/:le\" is faster than\r\n\"3fA4whhh\". Because the search pattern is mostly incomplete, the highlighting\r\nshould not continue to distract after the search; it should be off (but\r\n'incsearch' helps to recognize when enough of the pattern is typed to reach\r\nthe desired location). Likewise, the search pattern is useless in the search\r\nhistory and as the last pattern for the n command, as I am unlikely to\r\nrepeat that search. On the other hand, for actual searches, history recall,\r\nrepeated search and highlighting of matches are vital and central to the task.\r\n\r\nHow can this be reconciled? This plugin sets up alternative mappings to the\r\n key which normally concludes entering of the search pattern in\r\ncommand-line mode. By pressing , a quick search is triggered instead of\r\na normal one. This quick search does not use search highlighting and the\r\nsearch pattern is not added to the search history, so it can be used without\r\naffecting the normal search. Likewise, in a non-search command-line, the\r\nexecuted command (for example, a :substitute) does not affect the current\r\nsearch pattern and search history.\r\n\r\nNext \/ previous matches can be jumped to via separate mappings, but not via\r\nthe default n \/ N commands. (Even if the integration with the SearchRepeat\r\nplugin is used; contrary to most other integrations, this quick search must be\r\nexplicitly activated via the gnq \/ gNq mapping. )\r\n\r\nSEE ALSO\r\n- Check out the SearchSpecial.vim plugin page (vimscript #4948) for a full\r\n  list of special searches powered by it.\r\n- Check out the SearchRepeat.vim plugin page (vimscript #4949) for a full\r\n  list of custom searches that integrate with it.\r\n\r\nUSAGE\r\n\/{pattern}[\/]     When a search via \/ or ? is sent off by pressing\r\n?{pattern}[?]     , a quick forward \/ backward search is\r\n                        performed. Matches will not be highlighted via\r\n                        'hlsearch', and the search pattern will not be added\r\n                        to the search history or used as the last pattern for\r\n                        n \/ N search repeats.\r\n                        Use this for a quick search without the formality and\r\n                        persistence of a normal search, which can still be\r\n                        obtained by concluding the pattern input with the\r\n                        default  at the end.\r\n                        In the :... Ex command-line (and also >... debug\r\n                        command-line), any change to the search pattern and\r\n                        history is undone. For example, this is useful to do a\r\n                        substitution without affecting the current search:\r\n                        \/foo :s\/X\/Y\/ n (keep searching for \"foo\")\r\n\r\nThe special searches all start with 'go...' (mnemonic: \"go once to special\r\nmatch\"); and come in search forward (go...) and backward (gO...) variants.\r\n\r\n[count]goq \/ gOq        Search forward \/ backward to the [count]'th occurrence\r\n                        of the quick search pattern. This is the equivalent to\r\n                        the default n \/ N search repeat commands.\r\n\r\nThe following commands are optional; cp. the SearchAsQuickJump-configuration\r\nsection below.\r\n\r\nq*, q#                  Search forward \/ backward for the [count]'th\r\n                        occurrence of the word nearest to the cursor.\r\ngq*, gq#                Like above, but don't put \"\\<\" and \"\\>\" around the\r\n                        word. This makes the search also find matches that are\r\n                        not a whole word.\r\n{Visual}q*              Do a quick search forward \/ backward for the [count]'th\r\n{Visual}q#              occurrence of the current selection, like the built-in\r\n                        gstar and g# commands.\r\n\r\n                        These mappings are based on the built-in star and\r\n                        # commands. Like with them, 'ignorecase' is used,\r\n                        'smartcase' is not.","install_details":"INSTALLATION\r\nThe code is hosted in a Git repo at\r\n    https:\/\/github.com\/inkarkat\/vim-SearchAsQuickJump\r\nYou can use your favorite plugin manager, or \"git clone\" into a directory used\r\nfor Vim packages. Releases are on the \"stable\" branch, the latest unstable\r\ndevelopment snapshot on \"master\".\r\n\r\nThis script is also packaged as a vimball. If you have the \"gunzip\"\r\ndecompressor in your PATH, simply edit the *.vmb.gz package in Vim; otherwise,\r\ndecompress the archive first, e.g. using WinZip. Inside Vim, install by\r\nsourcing the vimball or via the :UseVimball command.\r\n    vim SearchAsQuickJump*.vmb.gz\r\n    :so %\r\nTo uninstall, use the :RmVimball command.\r\n\r\nDEPENDENCIES\r\n- Requires Vim 7.0 or higher.\r\n- Requires the SearchSpecial.vim plugin (vimscript #4948), version 1.20 or\r\n  higher.\r\n- SearchRepeat.vim (vimscript #4949) plugin, version 2.00 or higher (optional)\r\n\r\nINTEGRATION\r\nIf the SearchRepeat plugin is installed, a parallel set of \"go now and for\r\nnext searches\" mappings (starting with 'gn...' instead of 'go...') is\r\ninstalled. These mappings have the same effect, but in addition re-program the\r\n'n\/N' keys to repeat this particular search (until another gn... search is\r\nused).\r\n\r\nCONFIGURATION\r\nFor a permanent configuration, put the following commands into your vimrc:\r\n\r\nIf you don't want additional commands like the built-in '*', 'g*', '#' and\r\n'g#' commands (but prefixed with 'q' and not affecting the current search),\r\nuse:\r\n    :let g:SearchAsQuickJump_DefineStarCommands = 0\r\n\r\nIf you want to use different mappings, map your keys to the\r\n(SearchAsQuickJump...) mapping targets _before_ sourcing the script\r\n(e.g. in your vimrc):\r\n    cmap  (SearchAsQuickJump)\r\nNote that the default mapping only works in GVIM, but not in the terminal. A\r\npossible alternative would be this:\r\n    cmap  (SearchAsQuickJump)\r\nYou can also define different mappings for terminal and GVIM:\r\n    if ! has('gui_running')\r\n        cmap  (SearchAsQuickJump)\r\n    endif\r\n\r\n    nmap q* (SearchAsQuickJumpStar)\r\n    nmap q# (SearchAsQuickJumpHash)\r\n    nmap gq* (SearchAsQuickJumpGStar)\r\n    nmap gq# (SearchAsQuickJumpGHash)\r\n    xmap q* (SearchAsQuickJumpStar)\r\n    xmap q# (SearchAsQuickJumpHash)\r\n\r\n    nmap goq (SearchAsQuickJumpNext)\r\n    nmap gOq (SearchAsQuickJumpPrev)","5":"INSTALLATION\r\nThe code is hosted in a Git repo at\r\n    https:\/\/github.com\/inkarkat\/vim-SearchAsQuickJump\r\nYou can use your favorite plugin manager, or \"git clone\" into a directory used\r\nfor Vim packages. Releases are on the \"stable\" branch, the latest unstable\r\ndevelopment snapshot on \"master\".\r\n\r\nThis script is also packaged as a vimball. If you have the \"gunzip\"\r\ndecompressor in your PATH, simply edit the *.vmb.gz package in Vim; otherwise,\r\ndecompress the archive first, e.g. using WinZip. Inside Vim, install by\r\nsourcing the vimball or via the :UseVimball command.\r\n    vim SearchAsQuickJump*.vmb.gz\r\n    :so %\r\nTo uninstall, use the :RmVimball command.\r\n\r\nDEPENDENCIES\r\n- Requires Vim 7.0 or higher.\r\n- Requires the SearchSpecial.vim plugin (vimscript #4948), version 1.20 or\r\n  higher.\r\n- SearchRepeat.vim (vimscript #4949) plugin, version 2.00 or higher (optional)\r\n\r\nINTEGRATION\r\nIf the SearchRepeat plugin is installed, a parallel set of \"go now and for\r\nnext searches\" mappings (starting with 'gn...' instead of 'go...') is\r\ninstalled. These mappings have the same effect, but in addition re-program the\r\n'n\/N' keys to repeat this particular search (until another gn... search is\r\nused).\r\n\r\nCONFIGURATION\r\nFor a permanent configuration, put the following commands into your vimrc:\r\n\r\nIf you don't want additional commands like the built-in '*', 'g*', '#' and\r\n'g#' commands (but prefixed with 'q' and not affecting the current search),\r\nuse:\r\n    :let g:SearchAsQuickJump_DefineStarCommands = 0\r\n\r\nIf you want to use different mappings, map your keys to the\r\n(SearchAsQuickJump...) mapping targets _before_ sourcing the script\r\n(e.g. in your vimrc):\r\n    cmap  (SearchAsQuickJump)\r\nNote that the default mapping only works in GVIM, but not in the terminal. A\r\npossible alternative would be this:\r\n    cmap  (SearchAsQuickJump)\r\nYou can also define different mappings for terminal and GVIM:\r\n    if ! has('gui_running')\r\n        cmap  (SearchAsQuickJump)\r\n    endif\r\n\r\n    nmap q* (SearchAsQuickJumpStar)\r\n    nmap q# (SearchAsQuickJumpHash)\r\n    nmap gq* (SearchAsQuickJumpGStar)\r\n    nmap gq# (SearchAsQuickJumpGHash)\r\n    xmap q* (SearchAsQuickJumpStar)\r\n    xmap q# (SearchAsQuickJumpHash)\r\n\r\n    nmap goq (SearchAsQuickJumpNext)\r\n    nmap gOq (SearchAsQuickJumpPrev)","first_name":"Ingo","6":"Ingo","last_name":"Karkat","7":"Karkat","releases":[{"0":"5619","vim_version":"7.0","1":"7.0","script_version":"1.10","2":"1.10","version_comment":"- ENH: Handle \/...\/{offset} (instead of just ignoring the {offset}). *** You need to update to SearchSpecial.vim (vimscript #4948) version 1.20! ***","3":"- ENH: Handle \/...\/{offset} (instead of just ignoring the {offset}). *** You need to update to SearchSpecial.vim (vimscript #4948) version 1.20! ***","package":"SearchAsQuickJump-1.10.vmb.gz","4":"SearchAsQuickJump-1.10.vmb.gz","src_id":"26249","5":"26249","creation_date":"1540237354","6":"1540237354"},{"0":"5619","vim_version":"7.0","1":"7.0","script_version":"1.00","2":"1.00","version_comment":"Initial upload","3":"Initial upload","package":"SearchAsQuickJump-1.00.vmb.gz","4":"SearchAsQuickJump-1.00.vmb.gz","src_id":"25651","5":"25651","creation_date":"1511162448","6":"1511162448"}]},"5618":{"script_id":"5618","0":"5618","script_name":"AutoSave","1":"AutoSave","script_type":"utility","2":"utility","summary":"Automatically persist a buffer frequently.","3":"Automatically persist a buffer frequently.","description":"DESCRIPTION\r\nWhen developing scripts or programs, one frequently switches between a short\r\nedit in Vim and a test or compiler run in a terminal. If one forgets to\r\npersist the changes in Vim (:w), that run is of no avail, and one has to\r\nswitch back to Vim, save, and repeat.\r\n\r\nThis plugin allows to designate certain buffers for automatic persistence when\r\nGVIM (and Vim in terminals that support the FocusLost event) lose focus, or\r\noptionally also when 'updatetime' passes without a keypress in Vim. With that,\r\nyou can just make your edits, switch to another application, and the changes\r\nwill have been saved to the file, regardless of whether that file was\r\ncurrently active inside Vim.\r\n\r\nRELATED WORKS\r\n- The todo.txt has an entry for an 'autosave' option, which would persist a\r\n  buffer shortly after the last change.\r\n- vim-auto-save (vimscript #4521) automatically persists _all_ (toggled with\r\n  :AutoSaveToggle) buffers on CursorHold events (and reduces 'updatetime' to\r\n  200 ms).\r\n- vim-autosave (https:\/\/github.com\/chrisbra\/vim-autosave) uses Vim 8 timers to\r\n  persist a backup copy every 5 minutes.\r\n\r\nUSAGE\r\n:AutoSave[!], :NoAutoSave\r\n                        Turn on \/ off automatic saving of the current buffer\r\n                        whenever Vim loses focus (in the GUI) or exits; with !\r\n                        also on CursorHold.\r\n                        Note: The saving may trigger |:autocmd|s, and these\r\n                        may (depending on your configuration) trigger dialogs,\r\n                        or run external commands. If you do not want that,\r\n                        either use :noautocmd AutoSave (to disable this for\r\n                        the current buffer only), or globally by adding that\r\n                        to the g:AutoSave_UpdateModifiers configuration.","4":"DESCRIPTION\r\nWhen developing scripts or programs, one frequently switches between a short\r\nedit in Vim and a test or compiler run in a terminal. If one forgets to\r\npersist the changes in Vim (:w), that run is of no avail, and one has to\r\nswitch back to Vim, save, and repeat.\r\n\r\nThis plugin allows to designate certain buffers for automatic persistence when\r\nGVIM (and Vim in terminals that support the FocusLost event) lose focus, or\r\noptionally also when 'updatetime' passes without a keypress in Vim. With that,\r\nyou can just make your edits, switch to another application, and the changes\r\nwill have been saved to the file, regardless of whether that file was\r\ncurrently active inside Vim.\r\n\r\nRELATED WORKS\r\n- The todo.txt has an entry for an 'autosave' option, which would persist a\r\n  buffer shortly after the last change.\r\n- vim-auto-save (vimscript #4521) automatically persists _all_ (toggled with\r\n  :AutoSaveToggle) buffers on CursorHold events (and reduces 'updatetime' to\r\n  200 ms).\r\n- vim-autosave (https:\/\/github.com\/chrisbra\/vim-autosave) uses Vim 8 timers to\r\n  persist a backup copy every 5 minutes.\r\n\r\nUSAGE\r\n:AutoSave[!], :NoAutoSave\r\n                        Turn on \/ off automatic saving of the current buffer\r\n                        whenever Vim loses focus (in the GUI) or exits; with !\r\n                        also on CursorHold.\r\n                        Note: The saving may trigger |:autocmd|s, and these\r\n                        may (depending on your configuration) trigger dialogs,\r\n                        or run external commands. If you do not want that,\r\n                        either use :noautocmd AutoSave (to disable this for\r\n                        the current buffer only), or globally by adding that\r\n                        to the g:AutoSave_UpdateModifiers configuration.","install_details":"INSTALLATION\r\nThe code is hosted in a Git repo at\r\n    https:\/\/github.com\/inkarkat\/vim-AutoSave\r\nYou can use your favorite plugin manager, or \"git clone\" into a directory used\r\nfor Vim packages. Releases are on the \"stable\" branch, the latest unstable\r\ndevelopment snapshot on \"master\".\r\n\r\nThis script is also packaged as a vimball. If you have the \"gunzip\"\r\ndecompressor in your PATH, simply edit the *.vmb.gz package in Vim; otherwise,\r\ndecompress the archive first, e.g. using WinZip. Inside Vim, install by\r\nsourcing the vimball or via the :UseVimball command.\r\n    vim AutoSave*.vmb.gz\r\n    :so %\r\nTo uninstall, use the :RmVimball command.\r\n\r\nDEPENDENCIES\r\n- Requires Vim 7.0 or higher.\r\n- Requires the ingo-library.vim plugin (vimscript #4433), version 1.033 or\r\n  higher.\r\n\r\nCONFIGURATION\r\nFor a permanent configuration, put the following commands into your vimrc:\r\n\r\nThe contents of this configuration are prepended to the :update command; you\r\ncan use noautocmd to suppress triggering |autocmd|s, or silent to suppress\r\nthe save messages:\r\n    let g:AutoSave_UpdateModifiers = ''","5":"INSTALLATION\r\nThe code is hosted in a Git repo at\r\n    https:\/\/github.com\/inkarkat\/vim-AutoSave\r\nYou can use your favorite plugin manager, or \"git clone\" into a directory used\r\nfor Vim packages. Releases are on the \"stable\" branch, the latest unstable\r\ndevelopment snapshot on \"master\".\r\n\r\nThis script is also packaged as a vimball. If you have the \"gunzip\"\r\ndecompressor in your PATH, simply edit the *.vmb.gz package in Vim; otherwise,\r\ndecompress the archive first, e.g. using WinZip. Inside Vim, install by\r\nsourcing the vimball or via the :UseVimball command.\r\n    vim AutoSave*.vmb.gz\r\n    :so %\r\nTo uninstall, use the :RmVimball command.\r\n\r\nDEPENDENCIES\r\n- Requires Vim 7.0 or higher.\r\n- Requires the ingo-library.vim plugin (vimscript #4433), version 1.033 or\r\n  higher.\r\n\r\nCONFIGURATION\r\nFor a permanent configuration, put the following commands into your vimrc:\r\n\r\nThe contents of this configuration are prepended to the :update command; you\r\ncan use noautocmd to suppress triggering |autocmd|s, or silent to suppress\r\nthe save messages:\r\n    let g:AutoSave_UpdateModifiers = ''","first_name":"Ingo","6":"Ingo","last_name":"Karkat","7":"Karkat","releases":[{"0":"5618","vim_version":"7.0","1":"7.0","script_version":"1.10","2":"1.10","version_comment":"- ENH: Allow customization of :update command via :noautocmd AutoSave, or g:AutoSave_UpdateModifiers configuration. *** You need to update to ingo-library (vimscript #4433) version 1.033! ***\r\n- ENH: Record use of [!] for each buffer, and only update those with :AutoSave! during CursorHold[I] events.","3":"- ENH: Allow customization of :update command via :noautocmd AutoSave, or g:AutoSave_UpdateModifiers configuration. *** You need to update to ingo-library (vimscript #4433) version 1.033! ***\r\n- ENH: Record use of [!] for each buffer, and only update those with :AutoSave! during CursorHold[I] events.","package":"AutoSave-1.10.vmb.gz","4":"AutoSave-1.10.vmb.gz","src_id":"26968","5":"26968","creation_date":"1581308321","6":"1581308321"},{"0":"5618","vim_version":"7.0","1":"7.0","script_version":"1.00","2":"1.00","version_comment":"Initial upload","3":"Initial upload","package":"AutoSave-1.00.vmb.gz","4":"AutoSave-1.00.vmb.gz","src_id":"25646","5":"25646","creation_date":"1510574150","6":"1510574150"}]},"5617":{"script_id":"5617","0":"5617","script_name":"files-complete","1":"files-complete","script_type":"utility","2":"utility","summary":"completefunc which looks to all files in the current directory","3":"completefunc which looks to all files in the current directory","description":"completefunc which uses for completion all files in the current directory with the same file extension as the current file.\r\n\r\nRequires external grep command, so Windows users have to install some port of it. (requires ``-h`` and ``-o`` non-POSIX switches, but all BSD and GNU versions of grep have them).\r\n\r\nFor example when you have per-chapter organization of novel, then this will complete using all words in the novel.\r\n\r\nFor support, issue tracking etc. you can use website https:\/\/gitlab.com\/mcepl\/vim-files-complete\r\n\r\nWorks with any plugin management system using Git URL https:\/\/gitlab.com\/mcepl\/vim-files-complete.git\r\n\r\nBased on ideas from the answer on StackExchange https:\/\/stackoverflow.com\/a\/18203966\/164233","4":"completefunc which uses for completion all files in the current directory with the same file extension as the current file.\r\n\r\nRequires external grep command, so Windows users have to install some port of it. (requires ``-h`` and ``-o`` non-POSIX switches, but all BSD and GNU versions of grep have them).\r\n\r\nFor example when you have per-chapter organization of novel, then this will complete using all words in the novel.\r\n\r\nFor support, issue tracking etc. you can use website https:\/\/gitlab.com\/mcepl\/vim-files-complete\r\n\r\nWorks with any plugin management system using Git URL https:\/\/gitlab.com\/mcepl\/vim-files-complete.git\r\n\r\nBased on ideas from the answer on StackExchange https:\/\/stackoverflow.com\/a\/18203966\/164233","install_details":"For activation add::\r\n\r\n   set completefunc=filescompl#complete\r\n\r\nto your ``~\/.vimrc`` and then you can use ```` to invoke the completion.","5":"For activation add::\r\n\r\n   set completefunc=filescompl#complete\r\n\r\nto your ``~\/.vimrc`` and then you can use ```` to invoke the completion.","first_name":"Matej","6":"Matej","last_name":"Cepl","7":"Cepl","releases":[{"0":"5617","vim_version":"7.0","1":"7.0","script_version":"1","2":"1","version_comment":"Initial upload","3":"Initial upload","package":"files-complete.tar.gz","4":"files-complete.tar.gz","src_id":"25631","5":"25631","creation_date":"1509574432","6":"1509574432"}]},"5616":{"script_id":"5616","0":"5616","script_name":"Archery","1":"Archery","script_type":"color scheme","2":"color scheme","summary":"Vim colorscheme inspired by Arch Linux colors","3":"Vim colorscheme inspired by Arch Linux colors","description":"Archery is a dark colorscheme for Vim, inspired by Arch Linux color palette. This is where beautiful shades of blue meet mysterious shades of gray!\r\n\r\nhttps:\/\/github.com\/Badacadabra\/vim-archery","4":"Archery is a dark colorscheme for Vim, inspired by Arch Linux color palette. This is where beautiful shades of blue meet mysterious shades of gray!\r\n\r\nhttps:\/\/github.com\/Badacadabra\/vim-archery","install_details":"It is recommended to install Archery with a Vim plugin manager:\r\n\r\n- Pathogen\r\n- Vundle\r\n- Plug\r\n- NeoBundle\r\n- Dein\r\n\r\nThen enable the colorscheme in your vimrc with the following command: \"colorscheme archery\"\r\n\r\nIf you only use GVim, you're done! If you use terminal Vim, read on...\r\n\r\n1. Archery supports 256 colors terminals, so you do not need plugins like CSApprox or GUIColorscheme to use it.\r\n2. Open your vimrc with Vim in your terminal and try \":set termguicolors\". If colors are rendered properly, you can add this command in your vimrc to use GUI colors directly (these are defined using the hexadecimal notation).\r\n3. If \"termguicolors\" does not work, add \"set t_Co=256\" in your vimrc before setting the colorscheme and configure your terminal emulator to use the Archery color palette given on GitHub.","5":"It is recommended to install Archery with a Vim plugin manager:\r\n\r\n- Pathogen\r\n- Vundle\r\n- Plug\r\n- NeoBundle\r\n- Dein\r\n\r\nThen enable the colorscheme in your vimrc with the following command: \"colorscheme archery\"\r\n\r\nIf you only use GVim, you're done! If you use terminal Vim, read on...\r\n\r\n1. Archery supports 256 colors terminals, so you do not need plugins like CSApprox or GUIColorscheme to use it.\r\n2. Open your vimrc with Vim in your terminal and try \":set termguicolors\". If colors are rendered properly, you can add this command in your vimrc to use GUI colors directly (these are defined using the hexadecimal notation).\r\n3. If \"termguicolors\" does not work, add \"set t_Co=256\" in your vimrc before setting the colorscheme and configure your terminal emulator to use the Archery color palette given on GitHub.","first_name":"Baptiste","6":"Baptiste","last_name":"Vannesson","7":"Vannesson","releases":[{"0":"5616","vim_version":"8.0","1":"8.0","script_version":"1.0.0","2":"1.0.0","version_comment":"Initial upload","3":"Initial upload","package":"vim-archery.tgz","4":"vim-archery.tgz","src_id":"25620","5":"25620","creation_date":"1508939423","6":"1508939423"}]},"5615":{"script_id":"5615","0":"5615","script_name":"man.vim","1":"man.vim","script_type":"utility","2":"utility","summary":"open man pages within vim using :e man:page or :e man:section:page","3":"open man pages within vim using :e man:page or :e man:section:page","description":"This allows you to edit man pages by using:\r\n\r\n:e man:bash\r\n  or\r\n:e man:1:stat \" Shows man page for userspace command\r\n:e man:2:stat \" Shows man page for system call\r\n\r\n","4":"This allows you to edit man pages by using:\r\n\r\n:e man:bash\r\n  or\r\n:e man:1:stat \" Shows man page for userspace command\r\n:e man:2:stat \" Shows man page for system call\r\n\r\n","install_details":"Throw it in your plugins directory.\r\n","5":"Throw it in your plugins directory.\r\n","first_name":"rich","6":"rich","last_name":"paul","7":"paul","releases":[{"0":"5615","vim_version":"7.0","1":"7.0","script_version":"1.2","2":"1.2","version_comment":"Cleanup","3":"Cleanup","package":"man.vim","4":"man.vim","src_id":"25669","5":"25669","creation_date":"1511896329","6":"1511896329"},{"0":"5615","vim_version":"7.0","1":"7.0","script_version":"1.1","2":"1.1","version_comment":"Ooops ... removed stray debug call.\r\n","3":"Ooops ... removed stray debug call.\r\n","package":"man.vim","4":"man.vim","src_id":"25608","5":"25608","creation_date":"1507977656","6":"1507977656"},{"0":"5615","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"man.vim","4":"man.vim","src_id":"25607","5":"25607","creation_date":"1507973456","6":"1507973456"}]},"5614":{"script_id":"5614","0":"5614","script_name":"Colortemplate","1":"Colortemplate","script_type":"ftplugin","2":"ftplugin","summary":"The Toolkit for Color Scheme Designers!","3":"The Toolkit for Color Scheme Designers!","description":"GitHub repo: https:\/\/github.com\/lifepillar\/vim-colortemplate\r\n\r\nColortemplate is a plugin for Vim 8 and later that allows you to easily develop color schemes. Its ambitious goal is to become *the* way to create new color schemes for Vim!\r\n\r\nColortemplate is based on a very simple but very flexible template format. This is a minimal template:\r\n\r\nFull name:  My Gorgeous Theme\r\nShort name: gorgeous\r\nAuthor:     Me \r\n\r\nVariant:    gui 256\r\nBackground: dark\r\n\r\n; Color palette\r\nColor:      myblack #333333 ~\r\nColor:      mywhite #fafafa ~\r\n\r\n; Highlight group definitions\r\nNormal      mywhite myblack\r\n\r\nTerm colors: mywhite mywhite mywhite mywhite mywhite mywhite mywhite mywhite\r\nTerm colors: myblack myblack myblack myblack myblack myblack myblack myblack\r\n\r\nUse :Colortemplate to turn a template into a full-fledged colorscheme. For example:\r\n\r\n:Colortemplate ~\/.vim\r\n\r\nwill translate your template and write your new shining color scheme into ~\/.vim\/colors\/gorgeous.vim, ready to be used!\r\n\r\nMain Features:\r\n\r\n- Generates color schemes that support all environments, from black&white to\r\n  millions of colors, and both terminal and GUI Vim.\r\n- Generates color schemes that load efficiently and have a consistent structure\r\n  following best practices.\r\n- Automatically provides xterm approximations for GUI colors.\r\n- Imports any color scheme. You do not have to start from scratch!\r\n- Provides a sophisticated style picker. Create color schemes in real-time\r\n  directly within Vim!\r\n- Displays information about the highlight group under the cursor.\r\n- Computes useful statistics about your color scheme.\r\n- Supports generating any kind of auxiliary files (say,\r\n  `autoload\/gorgeous.vim` or `scripts\/foo.sh`).\r\n- Has syntax completion for highlight groups, keywords and common colors.\r\n- \u00e2\u0080\u00a6And a lot more!\r\n\r\nColortemplate is fully documented: to learn everything about it, read `:help\r\ncolortemplate.txt`.","4":"GitHub repo: https:\/\/github.com\/lifepillar\/vim-colortemplate\r\n\r\nColortemplate is a plugin for Vim 8 and later that allows you to easily develop color schemes. Its ambitious goal is to become *the* way to create new color schemes for Vim!\r\n\r\nColortemplate is based on a very simple but very flexible template format. This is a minimal template:\r\n\r\nFull name:  My Gorgeous Theme\r\nShort name: gorgeous\r\nAuthor:     Me \r\n\r\nVariant:    gui 256\r\nBackground: dark\r\n\r\n; Color palette\r\nColor:      myblack #333333 ~\r\nColor:      mywhite #fafafa ~\r\n\r\n; Highlight group definitions\r\nNormal      mywhite myblack\r\n\r\nTerm colors: mywhite mywhite mywhite mywhite mywhite mywhite mywhite mywhite\r\nTerm colors: myblack myblack myblack myblack myblack myblack myblack myblack\r\n\r\nUse :Colortemplate to turn a template into a full-fledged colorscheme. For example:\r\n\r\n:Colortemplate ~\/.vim\r\n\r\nwill translate your template and write your new shining color scheme into ~\/.vim\/colors\/gorgeous.vim, ready to be used!\r\n\r\nMain Features:\r\n\r\n- Generates color schemes that support all environments, from black&white to\r\n  millions of colors, and both terminal and GUI Vim.\r\n- Generates color schemes that load efficiently and have a consistent structure\r\n  following best practices.\r\n- Automatically provides xterm approximations for GUI colors.\r\n- Imports any color scheme. You do not have to start from scratch!\r\n- Provides a sophisticated style picker. Create color schemes in real-time\r\n  directly within Vim!\r\n- Displays information about the highlight group under the cursor.\r\n- Computes useful statistics about your color scheme.\r\n- Supports generating any kind of auxiliary files (say,\r\n  `autoload\/gorgeous.vim` or `scripts\/foo.sh`).\r\n- Has syntax completion for highlight groups, keywords and common colors.\r\n- \u00e2\u0080\u00a6And a lot more!\r\n\r\nColortemplate is fully documented: to learn everything about it, read `:help\r\ncolortemplate.txt`.","install_details":"","5":"","first_name":"","6":"","last_name":"Lifepillar","7":"Lifepillar","releases":[{"0":"5614","vim_version":"8.0","1":"8.0","script_version":"2.1.0","2":"2.1.0","version_comment":"The toolkit for color scheme developers! What's new: 1. 🎨 The Style Picker: edit color schemes in real-time directly within Vim! 2. 🎬 Import function to generate a template from any color scheme: you don't need to start from scratch! 3. 🐞 Bug fixes.\r\n\r\nBring your color schemes to another level!","3":"The toolkit for color scheme developers! What's new: 1. 🎨 The Style Picker: edit color schemes in real-time directly within Vim! 2. 🎬 Import function to generate a template from any color scheme: you don't need to start from scratch! 3. 🐞 Bug fixes.\r\n\r\nBring your color schemes to another level!","package":"vim-colortemplate-2.1.0.tar.gz","4":"vim-colortemplate-2.1.0.tar.gz","src_id":"27313","5":"27313","creation_date":"1600578342","6":"1600578342"},{"0":"5614","vim_version":"8.0","1":"8.0","script_version":"2.0.0","2":"2.0.0","version_comment":"After applying the final touches, the v2.0 milestone has been reached! What are you expecting to start designing your color schemes?","3":"After applying the final touches, the v2.0 milestone has been reached! What are you expecting to start designing your color schemes?","package":"vim-colortemplate-2.0.0.tar.gz","4":"vim-colortemplate-2.0.0.tar.gz","src_id":"26615","5":"26615","creation_date":"1563164993","6":"1563164993"},{"0":"5614","vim_version":"8.0","1":"8.0","script_version":"2.0.0rc1","2":"2.0.0rc1","version_comment":"The v2.0 milestone is approaching! This release fixes a few minor issues and adds a couple more options to control the output of your color scheme (now even from the template itself via the `Colortemplate Options` key!). New features: `omit` keyword to omit parts of a highlight group definition (e.g., `hi Foo white omit` defines only the foreground color); RGB names are not converted to hex values in the output. Please test and provide feedback so v2.0 will be a rock solid release!","3":"The v2.0 milestone is approaching! This release fixes a few minor issues and adds a couple more options to control the output of your color scheme (now even from the template itself via the `Colortemplate Options` key!). New features: `omit` keyword to omit parts of a highlight group definition (e.g., `hi Foo white omit` defines only the foreground color); RGB names are not converted to hex values in the output. Please test and provide feedback so v2.0 will be a rock solid release!","package":"vim-colortemplate-2.0.0rc1.tar.gz","4":"vim-colortemplate-2.0.0rc1.tar.gz","src_id":"26583","5":"26583","creation_date":"1562127928","6":"1562127928"},{"0":"5614","vim_version":"8.0","1":"8.0","script_version":"2.0.0rc1","2":"2.0.0rc1","version_comment":"The v2.0 milestone is approaching! This release fixes a few minor issues and adds a couple more options to control the output of your color scheme (now even from the template itself via the `Colortemplate Options` key!). New features: `omit` keyword to omit parts of a highlight group definition (e.g., `hi Foo white omit` defines only the foreground color); RGB names are not converted to hex values in the output. Please test and provide feedback so v2.0 will be a rock solid release!","3":"The v2.0 milestone is approaching! This release fixes a few minor issues and adds a couple more options to control the output of your color scheme (now even from the template itself via the `Colortemplate Options` key!). New features: `omit` keyword to omit parts of a highlight group definition (e.g., `hi Foo white omit` defines only the foreground color); RGB names are not converted to hex values in the output. Please test and provide feedback so v2.0 will be a rock solid release!","package":"vim-colortemplate-2.0.0rc1.tar.gz","4":"vim-colortemplate-2.0.0rc1.tar.gz","src_id":"26582","5":"26582","creation_date":"1562127714","6":"1562127714"},{"0":"5614","vim_version":"8.0","1":"8.0","script_version":"2.0.0b3","2":"2.0.0b3","version_comment":"Ironed out a few features and added new ones: `ga` now shows colors; statistics has been extended with \u00e2\u0080\u009ccritical pairs\u00e2\u0080\u009d of fg\/bg colors; file extension may be omitted when including files; added #if, #let, #unlet, #call commands to streamline some verbatim blocks. And several bugs were removed!","3":"Ironed out a few features and added new ones: `ga` now shows colors; statistics has been extended with \u00e2\u0080\u009ccritical pairs\u00e2\u0080\u009d of fg\/bg colors; file extension may be omitted when including files; added #if, #let, #unlet, #call commands to streamline some verbatim blocks. And several bugs were removed!","package":"vim-colortemplate-2.0.0b3.tar.gz","4":"vim-colortemplate-2.0.0b3.tar.gz","src_id":"26534","5":"26534","creation_date":"1560266995","6":"1560266995"},{"0":"5614","vim_version":"8.0","1":"8.0","script_version":"2.0.0b1","2":"2.0.0b1","version_comment":"Fixed a couple of regressions, notably one breaking mappings.","3":"Fixed a couple of regressions, notably one breaking mappings.","package":"vim-colortemplate-2.0.0b1.tar.gz","4":"vim-colortemplate-2.0.0b1.tar.gz","src_id":"26513","5":"26513","creation_date":"1559665455","6":"1559665455"},{"0":"5614","vim_version":"8.0","1":"8.0","script_version":"2.0.0b","2":"2.0.0b","version_comment":"The toolkit for color scheme designers, pure 100% VimScript. Colortemplate aspires to become your favourite way to make color schemes! V2 is a complete overhaul of the script with a lot of new features\u00e2\u0080\u0094too many to mention here! Streamlined UI with window toolbar (if your Vim supports it), variants, mappings, new commands, improved documentation, etc\u00e2\u0080\u00a6 but it is still very easy to use!","3":"The toolkit for color scheme designers, pure 100% VimScript. Colortemplate aspires to become your favourite way to make color schemes! V2 is a complete overhaul of the script with a lot of new features\u00e2\u0080\u0094too many to mention here! Streamlined UI with window toolbar (if your Vim supports it), variants, mappings, new commands, improved documentation, etc\u00e2\u0080\u00a6 but it is still very easy to use!","package":"vim-colortemplate-2.0.0b.tar.gz","4":"vim-colortemplate-2.0.0b.tar.gz","src_id":"26512","5":"26512","creation_date":"1559543151","6":"1559543151"},{"0":"5614","vim_version":"8.0","1":"8.0","script_version":"1.3.0","2":"1.3.0","version_comment":"Output a statistics tab when compiling a template, with useful information about your colorscheme (contrast ratio, color difference, brightness difference, GUI\/terminal differences). Create colorschemes that transparently fallback to using 16 colors when t_Co < 256. Many other minor changes.","3":"Output a statistics tab when compiling a template, with useful information about your colorscheme (contrast ratio, color difference, brightness difference, GUI\/terminal differences). Create colorschemes that transparently fallback to using 16 colors when t_Co < 256. Many other minor changes.","package":"vim-colortemplate-1.3.0.tar.gz","4":"vim-colortemplate-1.3.0.tar.gz","src_id":"26170","5":"26170","creation_date":"1533428656","6":"1533428656"},{"0":"5614","vim_version":"8.0","1":"8.0","script_version":"1.2.2","2":"1.2.2","version_comment":"Enable completion of Colortemplate keywords. Add syntax highlighting for debugPC and debugBreakpoint. Minor updates to the documentation.","3":"Enable completion of Colortemplate keywords. Add syntax highlighting for debugPC and debugBreakpoint. Minor updates to the documentation.","package":"vim-colortemplate-1.2.2.tar.gz","4":"vim-colortemplate-1.2.2.tar.gz","src_id":"25855","5":"25855","creation_date":"1520159509","6":"1520159509"},{"0":"5614","vim_version":"8.0","1":"8.0","script_version":"1.2.1","2":"1.2.1","version_comment":"A few bug fixes, especially a couple related to the Include: directive. Clean up the templates folder.","3":"A few bug fixes, especially a couple related to the Include: directive. Clean up the templates folder.","package":"vim-colortemplate-1.2.1.tar.gz","4":"vim-colortemplate-1.2.1.tar.gz","src_id":"25798","5":"25798","creation_date":"1516739271","6":"1516739271"},{"0":"5614","vim_version":"7.0","1":"7.0","script_version":"1.2.0","2":"1.2.0","version_comment":"Lots of small (and not so small) fixes! Improved documentation. Add Palette directive to include generated palettes. New functions to generate Vimspectr color palettes. Making top notch colorschemes has never been easier!","3":"Lots of small (and not so small) fixes! Improved documentation. Add Palette directive to include generated palettes. New functions to generate Vimspectr color palettes. Making top notch colorschemes has never been easier!","package":"vim-colortemplate-1.2.0.tar.gz","4":"vim-colortemplate-1.2.0.tar.gz","src_id":"25792","5":"25792","creation_date":"1516554243","6":"1516554243"},{"0":"5614","vim_version":"8.0","1":"8.0","script_version":"1.1.1","2":"1.1.1","version_comment":"Lots of new goodies! \"Include\" directive to import files; \"auxfile\" blocks to generate additional files (e.g., in autoload); warnings for undefined basic highlight groups; more and stricter checks; improved documentation (with new Best practices section!). There are some backward incompatible changes wrt v1.0.0: please see the help file.","3":"Lots of new goodies! \"Include\" directive to import files; \"auxfile\" blocks to generate additional files (e.g., in autoload); warnings for undefined basic highlight groups; more and stricter checks; improved documentation (with new Best practices section!). There are some backward incompatible changes wrt v1.0.0: please see the help file.","package":"vim-colortemplate-1.1.1.tar.gz","4":"vim-colortemplate-1.1.1.tar.gz","src_id":"25642","5":"25642","creation_date":"1510436013","6":"1510436013"},{"0":"5614","vim_version":"8.0","1":"8.0","script_version":"1.0.0","2":"1.0.0","version_comment":"The toolkit for colorschemes developers!\r\nLots of new features and bug fixes: new parser; better error handling; generate colorschemes supporting 16 colors, 256 colors and true colors, with dark and\/or light background; infer the best approximate colors automatically using DeltaE*; embed the documentation directly in the template; new information fields and interpolation possibilities; utility function to explore approximated colors; toggle the display of details about the highlight group under the cursor; tests added.","3":"The toolkit for colorschemes developers!\r\nLots of new features and bug fixes: new parser; better error handling; generate colorschemes supporting 16 colors, 256 colors and true colors, with dark and\/or light background; infer the best approximate colors automatically using DeltaE*; embed the documentation directly in the template; new information fields and interpolation possibilities; utility function to explore approximated colors; toggle the display of details about the highlight group under the cursor; tests added.","package":"vim-colortemplate-1.0.0.tar.gz","4":"vim-colortemplate-1.0.0.tar.gz","src_id":"25624","5":"25624","creation_date":"1509205015","6":"1509205015"},{"0":"5614","vim_version":"8.0","1":"8.0","script_version":"v0.0.2","2":"v0.0.2","version_comment":"Bug fixes in error handling.","3":"Bug fixes in error handling.","package":"vim-colortemplate-0.0.2.tar.gz","4":"vim-colortemplate-0.0.2.tar.gz","src_id":"25597","5":"25597","creation_date":"1506881384","6":"1506881384"},{"0":"5614","vim_version":"8.0","1":"8.0","script_version":"0.0.1","2":"0.0.1","version_comment":"Initial upload","3":"Initial upload","package":"vim-colortemplate-0.0.1.tar.gz","4":"vim-colortemplate-0.0.1.tar.gz","src_id":"25596","5":"25596","creation_date":"1506877330","6":"1506877330"}]},"5613":{"script_id":"5613","0":"5613","script_name":"WORDComplete","1":"WORDComplete","script_type":"utility","2":"utility","summary":"Insert mode completion that completes an entire sequence of non-blank characters","3":"Insert mode completion that completes an entire sequence of non-blank characters","description":"DESCRIPTION\r\nThe built-in insert mode completion i_CTRL-N searches for keywords.\r\nDepending on the 'iskeyword' setting, this can be very fine-grained, so that\r\nfragments like '--quit-if-one-screen' or '\/^Vim\\%((\\a\\+)\\)\\=:E123\/' can take\r\nmany completion commands and are thus tedious to complete.\r\nThis plugin offers completion of sequences of non-blank characters (a.k.a.\r\n|WORD|s), i.e. everything separated by whitespace or the start \/ end of line.\r\nWith this, one can quickly complete entire text fragments which are delimited\r\nby whitespace.\r\n\r\nSEE ALSO\r\n- Check out the CompleteHelper.vim plugin page (vimscript #3914) for a full\r\n  list of insert mode completions powered by it.\r\n\r\nUSAGE\r\nIn insert mode, invoke the WORD completion via CTRL-X CTRL-W.\r\nYou can then search forward and backward via CTRL-N \/ CTRL-P, as usual.\r\n\r\nCTRL-X CTRL-W           Find matches for WORDs that start with the non-blank\r\n                        characters in front of the cursor and end at the next\r\n                        whitespace.\r\n                        First, a match must start after whitespace (or at the\r\n                        beginning of the line); if that returns no results, it\r\n                        may match anywhere.\r\n                        Further use of CTRL-X W will copy the text including\r\n                        the next WORDs following the previous expansion in\r\n                        other contexts.\r\n\r\n{Visual}CTRL-X CTRL-W   Find matches for WORDs that start with selected text\r\n                        and end at the next whitespace.\r\n\r\nEXAMPLE\r\nTo query the entire command argument --foo-bar (when \"-\" is not part of\r\n'iskeyword'), just type \"--f\" and trigger the completion.\r\n\r\nWith the relaxed search, \"pos(\" will complete the entire call \"pos([1,2,3])\"\r\nfound in \"searchpos([1,2,3])\".","4":"DESCRIPTION\r\nThe built-in insert mode completion i_CTRL-N searches for keywords.\r\nDepending on the 'iskeyword' setting, this can be very fine-grained, so that\r\nfragments like '--quit-if-one-screen' or '\/^Vim\\%((\\a\\+)\\)\\=:E123\/' can take\r\nmany completion commands and are thus tedious to complete.\r\nThis plugin offers completion of sequences of non-blank characters (a.k.a.\r\n|WORD|s), i.e. everything separated by whitespace or the start \/ end of line.\r\nWith this, one can quickly complete entire text fragments which are delimited\r\nby whitespace.\r\n\r\nSEE ALSO\r\n- Check out the CompleteHelper.vim plugin page (vimscript #3914) for a full\r\n  list of insert mode completions powered by it.\r\n\r\nUSAGE\r\nIn insert mode, invoke the WORD completion via CTRL-X CTRL-W.\r\nYou can then search forward and backward via CTRL-N \/ CTRL-P, as usual.\r\n\r\nCTRL-X CTRL-W           Find matches for WORDs that start with the non-blank\r\n                        characters in front of the cursor and end at the next\r\n                        whitespace.\r\n                        First, a match must start after whitespace (or at the\r\n                        beginning of the line); if that returns no results, it\r\n                        may match anywhere.\r\n                        Further use of CTRL-X W will copy the text including\r\n                        the next WORDs following the previous expansion in\r\n                        other contexts.\r\n\r\n{Visual}CTRL-X CTRL-W   Find matches for WORDs that start with selected text\r\n                        and end at the next whitespace.\r\n\r\nEXAMPLE\r\nTo query the entire command argument --foo-bar (when \"-\" is not part of\r\n'iskeyword'), just type \"--f\" and trigger the completion.\r\n\r\nWith the relaxed search, \"pos(\" will complete the entire call \"pos([1,2,3])\"\r\nfound in \"searchpos([1,2,3])\".","install_details":" INSTALLATION\r\nThe code is hosted in a Git repo at\r\n    https:\/\/github.com\/inkarkat\/vim-WORDComplete\r\nYou can use your favorite plugin manager, or \"git clone\" into a directory used\r\nfor Vim packages. Releases are on the \"stable\" branch, the latest unstable\r\ndevelopment snapshot on \"master\".\r\n\r\nThis script is also packaged as a vimball. If you have the \"gunzip\"\r\ndecompressor in your PATH, simply edit the *.vmb.gz package in Vim; otherwise,\r\ndecompress the archive first, e.g. using WinZip. Inside Vim, install by\r\nsourcing the vimball or via the :UseVimball command.\r\n    vim WORDComplete*.vmb.gz\r\n    :so %\r\nTo uninstall, use the :RmVimball command.\r\n\r\nDEPENDENCIES\r\n- Requires Vim 7.0 or higher.\r\n- Requires the ingo-library.vim plugin (vimscript #4433), version 1.010 or\r\n  higher.\r\n- Requires the CompleteHelper.vim plugin (vimscript #3914), version 1.40 or\r\n  higher.\r\n\r\nCONFIGURATION\r\nFor a permanent configuration, put the following commands into your vimrc:\r\n\r\nBy default, the 'complete' option controls which buffers will be scanned for\r\ncompletion candidates. You can override that either for the entire plugin, or\r\nonly for particular buffers; see CompleteHelper_complete for supported\r\nvalues.\r\n    let g:WORDComplete_complete = '.,w,b,u'\r\n\r\nIf you want to use a different mapping, map your keys to the\r\n(WORDComplete) mapping target _before_ sourcing the script (e.g.\r\nin your vimrc):\r\n    imap  (WORDComplete)\r\n    vmap  (WORDComplete)","5":" INSTALLATION\r\nThe code is hosted in a Git repo at\r\n    https:\/\/github.com\/inkarkat\/vim-WORDComplete\r\nYou can use your favorite plugin manager, or \"git clone\" into a directory used\r\nfor Vim packages. Releases are on the \"stable\" branch, the latest unstable\r\ndevelopment snapshot on \"master\".\r\n\r\nThis script is also packaged as a vimball. If you have the \"gunzip\"\r\ndecompressor in your PATH, simply edit the *.vmb.gz package in Vim; otherwise,\r\ndecompress the archive first, e.g. using WinZip. Inside Vim, install by\r\nsourcing the vimball or via the :UseVimball command.\r\n    vim WORDComplete*.vmb.gz\r\n    :so %\r\nTo uninstall, use the :RmVimball command.\r\n\r\nDEPENDENCIES\r\n- Requires Vim 7.0 or higher.\r\n- Requires the ingo-library.vim plugin (vimscript #4433), version 1.010 or\r\n  higher.\r\n- Requires the CompleteHelper.vim plugin (vimscript #3914), version 1.40 or\r\n  higher.\r\n\r\nCONFIGURATION\r\nFor a permanent configuration, put the following commands into your vimrc:\r\n\r\nBy default, the 'complete' option controls which buffers will be scanned for\r\ncompletion candidates. You can override that either for the entire plugin, or\r\nonly for particular buffers; see CompleteHelper_complete for supported\r\nvalues.\r\n    let g:WORDComplete_complete = '.,w,b,u'\r\n\r\nIf you want to use a different mapping, map your keys to the\r\n(WORDComplete) mapping target _before_ sourcing the script (e.g.\r\nin your vimrc):\r\n    imap  (WORDComplete)\r\n    vmap  (WORDComplete)","first_name":"Ingo","6":"Ingo","last_name":"Karkat","7":"Karkat","releases":[{"0":"5613","vim_version":"7.0","1":"7.0","script_version":"1.00","2":"1.00","version_comment":"Initial upload","3":"Initial upload","package":"WORDComplete-1.00.vmb.gz","4":"WORDComplete-1.00.vmb.gz","src_id":"25589","5":"25589","creation_date":"1506581477","6":"1506581477"}]},"5612":{"script_id":"5612","0":"5612","script_name":"highlight-groups.vim","1":"highlight-groups.vim","script_type":"utility","2":"utility","summary":"Add words in highlight groups on the fly.","3":"Add words in highlight groups on the fly.","description":"highlight-groups.vim\r\n====================\r\n\r\nAllow the user to add words in highlight groups on the fly. Each group has a different color.\r\nThe goal of this plugin is to allow the user to mark words and increase readabilty of certain lines of code.\r\n\r\nhttps:\/\/raw.githubusercontent.com\/antoinemadec\/gif\/master\/highlightgroups.gif\r\n\r\nProject home (latest version): \r\nhttps:\/\/github.com\/antoinemadec\/vim-highlight-groups\r\n\r\nQuick start guide\r\n-----------------\r\n\r\nHere is an example of mapping in your `.vimrc`:\r\nnnoremap   :HighlightGroupsAddWord 4 0\r\nnnoremap   :HighlightGroupsAddWord 6 0\r\nnnoremap   :HighlightGroupsClearGroup 4 0\r\nnnoremap   :HighlightGroupsClearGroup 6 0\r\nnnoremap   :HighlightGroupsAddWord 4 1\r\nnnoremap   :HighlightGroupsAddWord 6 1\r\nnnoremap   :HighlightGroupsClearGroup 4 1\r\nnnoremap   :HighlightGroupsClearGroup 6 1\r\n\r\nAuthor\r\n------\r\n\r\nInspired by Mario Trentini's highlights.vim\r\nAntoine Madec: https:\/\/github.com\/antoinemadec\r\n\r\nLicense\r\n------\r\n\r\nCopyright (c) Antoine Madec. Distributed under the same terms as Vim itself. See :help license.","4":"highlight-groups.vim\r\n====================\r\n\r\nAllow the user to add words in highlight groups on the fly. Each group has a different color.\r\nThe goal of this plugin is to allow the user to mark words and increase readabilty of certain lines of code.\r\n\r\nhttps:\/\/raw.githubusercontent.com\/antoinemadec\/gif\/master\/highlightgroups.gif\r\n\r\nProject home (latest version): \r\nhttps:\/\/github.com\/antoinemadec\/vim-highlight-groups\r\n\r\nQuick start guide\r\n-----------------\r\n\r\nHere is an example of mapping in your `.vimrc`:\r\nnnoremap   :HighlightGroupsAddWord 4 0\r\nnnoremap   :HighlightGroupsAddWord 6 0\r\nnnoremap   :HighlightGroupsClearGroup 4 0\r\nnnoremap   :HighlightGroupsClearGroup 6 0\r\nnnoremap   :HighlightGroupsAddWord 4 1\r\nnnoremap   :HighlightGroupsAddWord 6 1\r\nnnoremap   :HighlightGroupsClearGroup 4 1\r\nnnoremap   :HighlightGroupsClearGroup 6 1\r\n\r\nAuthor\r\n------\r\n\r\nInspired by Mario Trentini's highlights.vim\r\nAntoine Madec: https:\/\/github.com\/antoinemadec\r\n\r\nLicense\r\n------\r\n\r\nCopyright (c) Antoine Madec. Distributed under the same terms as Vim itself. See :help license.","install_details":"Use your favorite plugin manager. Using vim-plug:\r\nPlug 'antoinemadec\/vim-highlight-groups'","5":"Use your favorite plugin manager. Using vim-plug:\r\nPlug 'antoinemadec\/vim-highlight-groups'","first_name":"Antoine","6":"Antoine","last_name":"Madec","7":"Madec","releases":[{"0":"5612","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"vim-highlight-groups-1.0.zip","4":"vim-highlight-groups-1.0.zip","src_id":"25581","5":"25581","creation_date":"1505865321","6":"1505865321"}]},"5611":{"script_id":"5611","0":"5611","script_name":"verilog-instance.vim","1":"verilog-instance.vim","script_type":"utility","2":"utility","summary":"Create SystemVerilog port instantiation from port declaration.","3":"Create SystemVerilog port instantiation from port declaration.","description":"verilog-instance.vim\r\n====================\r\n\r\nCreate SystemVerilog port instantiation from port declaration.\r\nWork on modules, tasks, functions and all other similar structures.\r\n\r\nhttps:\/\/raw.githubusercontent.com\/antoinemadec\/gif\/master\/veriloginstance.gif\r\n\r\nProject home (latest version): \r\nhttps:\/\/github.com\/antoinemadec\/vim-verilog-instance\r\n\r\nQuick start guide\r\n-----------------\r\n\r\ntry these commands:\r\n\r\n- gbi(\r\n    - Start VerilogInstance command (gb) for inner parenthesis\r\n- vjjgb\r\n    - visual-select, down twice\r\n    - Start VerilogInstance command (gb) on the 3 selected lines\r\n\r\nOther vim plugins for Verilog\/SystemVerilog\r\n---------------------------------------\r\n\r\nverilog_systemverilog: https:\/\/github.com\/vhda\/verilog_systemverilog.vim is a syntax plugin for Verilog and SystemVerilog\r\n\r\nAuthor\r\n------\r\n\r\nAntoine Madec: https:\/\/github.com\/antoinemadec\r\n\r\nLicense\r\n------\r\n\r\nCopyright (c) Antoine Madec. Distributed under the same terms as Vim itself. See :help license.","4":"verilog-instance.vim\r\n====================\r\n\r\nCreate SystemVerilog port instantiation from port declaration.\r\nWork on modules, tasks, functions and all other similar structures.\r\n\r\nhttps:\/\/raw.githubusercontent.com\/antoinemadec\/gif\/master\/veriloginstance.gif\r\n\r\nProject home (latest version): \r\nhttps:\/\/github.com\/antoinemadec\/vim-verilog-instance\r\n\r\nQuick start guide\r\n-----------------\r\n\r\ntry these commands:\r\n\r\n- gbi(\r\n    - Start VerilogInstance command (gb) for inner parenthesis\r\n- vjjgb\r\n    - visual-select, down twice\r\n    - Start VerilogInstance command (gb) on the 3 selected lines\r\n\r\nOther vim plugins for Verilog\/SystemVerilog\r\n---------------------------------------\r\n\r\nverilog_systemverilog: https:\/\/github.com\/vhda\/verilog_systemverilog.vim is a syntax plugin for Verilog and SystemVerilog\r\n\r\nAuthor\r\n------\r\n\r\nAntoine Madec: https:\/\/github.com\/antoinemadec\r\n\r\nLicense\r\n------\r\n\r\nCopyright (c) Antoine Madec. Distributed under the same terms as Vim itself. See :help license.","install_details":"Use your favorite plugin manager. Using vim-plug:\r\nPlug 'antoinemadec\/vim-verilog-instance'","5":"Use your favorite plugin manager. Using vim-plug:\r\nPlug 'antoinemadec\/vim-verilog-instance'","first_name":"Antoine","6":"Antoine","last_name":"Madec","7":"Madec","releases":[{"0":"5611","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"vim-verilog-instance-1.0.zip","4":"vim-verilog-instance-1.0.zip","src_id":"25580","5":"25580","creation_date":"1505864665","6":"1505864665"}]},"5610":{"script_id":"5610","0":"5610","script_name":"makery.vim","1":"makery.vim","script_type":"utility","2":"utility","summary":"A plugin for managing makeprgs.","3":"A plugin for managing makeprgs.","description":"I made this plugin because I was tired of having to change my `makeprg` or\r\n`compiler` every time I wanted to run a different task. Switching between\r\n`:compiler eslint` and `:compiler jest` gets old really fast.\r\n\r\nSure, you can map, but it gets harder when you start to work across different\r\nprojects: some use different linters or test runners, some use a Makefile, some\r\nuse an `npm` script, some need to generate tags, etc. Madness!\r\n\r\nWith this plugin, all I have to do is specify my make-related tasks in a\r\n`.makery.json` file in my project root. For example, one of my React Native\r\nprojects has the following `.makery.json`:\r\n\r\n{\r\n  \"lint\": {\"compiler\": \"eslint\"},\r\n  \"reload\": {\"makeprg\": \"adb shell input keyevent 82\"},\r\n  \"tags\": {\"makeprg\": \"es-ctags -R src\"},\r\n  \"test\": {\"compiler\": \"jest\"}\r\n}\r\n\r\nNow I can just run `:Mlint` to lint, `:Mreload` to reload the JS code on my\r\nconnected Android device, `:Mtags` to generate tags, and `:Mtest` to run tests.\r\nNifty!\r\n\r\nI can even do `:LMlint %` to lint the current file and have it appear in the\r\ncorresponding location list instead of the global quickfix!\r\n\r\nIn case you already have an existing command with the same name, you can still\r\naccess the commands through the full `:Makery` form, e.g. `:Makery lint` or\r\n`:Makery compile`.\r\n\r\nThe best part is I can specify different behavior for `:Mlint` or `:Mtest`\r\ndepending on which project I'm in, by providing the necessary `.makery.json` for\r\neach of my projects!\r\n\r\nEven programs like ctags or adb fit well because of this, even though you don't\r\nnecessarily need the quickfix for them. Instead of fiddling with different `:!`\r\nincantations for different projects, you can just use `:Mtags` and be done with\r\nit!\r\n","4":"I made this plugin because I was tired of having to change my `makeprg` or\r\n`compiler` every time I wanted to run a different task. Switching between\r\n`:compiler eslint` and `:compiler jest` gets old really fast.\r\n\r\nSure, you can map, but it gets harder when you start to work across different\r\nprojects: some use different linters or test runners, some use a Makefile, some\r\nuse an `npm` script, some need to generate tags, etc. Madness!\r\n\r\nWith this plugin, all I have to do is specify my make-related tasks in a\r\n`.makery.json` file in my project root. For example, one of my React Native\r\nprojects has the following `.makery.json`:\r\n\r\n{\r\n  \"lint\": {\"compiler\": \"eslint\"},\r\n  \"reload\": {\"makeprg\": \"adb shell input keyevent 82\"},\r\n  \"tags\": {\"makeprg\": \"es-ctags -R src\"},\r\n  \"test\": {\"compiler\": \"jest\"}\r\n}\r\n\r\nNow I can just run `:Mlint` to lint, `:Mreload` to reload the JS code on my\r\nconnected Android device, `:Mtags` to generate tags, and `:Mtest` to run tests.\r\nNifty!\r\n\r\nI can even do `:LMlint %` to lint the current file and have it appear in the\r\ncorresponding location list instead of the global quickfix!\r\n\r\nIn case you already have an existing command with the same name, you can still\r\naccess the commands through the full `:Makery` form, e.g. `:Makery lint` or\r\n`:Makery compile`.\r\n\r\nThe best part is I can specify different behavior for `:Mlint` or `:Mtest`\r\ndepending on which project I'm in, by providing the necessary `.makery.json` for\r\neach of my projects!\r\n\r\nEven programs like ctags or adb fit well because of this, even though you don't\r\nnecessarily need the quickfix for them. Instead of fiddling with different `:!`\r\nincantations for different projects, you can just use `:Mtags` and be done with\r\nit!\r\n","install_details":"Untar into your ~\/.vim directory, or install with your favorite plugin manager (plugin is hosted at https:\/\/github.com\/igemnace\/vim-makery).\r\n\r\nVim 7.0 or higher should be fine. JSON support requires Vim 8.0 or higher.","5":"Untar into your ~\/.vim directory, or install with your favorite plugin manager (plugin is hosted at https:\/\/github.com\/igemnace\/vim-makery).\r\n\r\nVim 7.0 or higher should be fine. JSON support requires Vim 8.0 or higher.","first_name":"Ian","6":"Ian","last_name":"Emnace","7":"Emnace","releases":[{"0":"5610","vim_version":"7.0","1":"7.0","script_version":"1.9","2":"1.9","version_comment":"Add location list support, courtesy of :lmake","3":"Add location list support, courtesy of :lmake","package":"makery.tar.gz","4":"makery.tar.gz","src_id":"26156","5":"26156","creation_date":"1533046816","6":"1533046816"},{"0":"5610","vim_version":"7.0","1":"7.0","script_version":"1.8","2":"1.8","version_comment":"Add Projectionist support for setting up Makery config","3":"Add Projectionist support for setting up Makery config","package":"makery.tar.gz","4":"makery.tar.gz","src_id":"25951","5":"25951","creation_date":"1524832125","6":"1524832125"},{"0":"5610","vim_version":"7.0","1":"7.0","script_version":"1.7","2":"1.7","version_comment":"Fix bug where recursion loops forever for fugitive:\/\/ buffers","3":"Fix bug where recursion loops forever for fugitive:\/\/ buffers","package":"makery.tar.gz","4":"makery.tar.gz","src_id":"25776","5":"25776","creation_date":"1516256218","6":"1516256218"},{"0":"5610","vim_version":"7.0","1":"7.0","script_version":"1.6","2":"1.6","version_comment":"Recurses up the directory tree to find .makery.json, for when opening Vim from a project subdirectory","3":"Recurses up the directory tree to find .makery.json, for when opening Vim from a project subdirectory","package":"makery.tar.gz","4":"makery.tar.gz","src_id":"25755","5":"25755","creation_date":"1515566578","6":"1515566578"},{"0":"5610","vim_version":"7.0","1":"7.0","script_version":"1.5","2":"1.5","version_comment":"Expose :Makery command for conflicting existing commands","3":"Expose :Makery command for conflicting existing commands","package":"makery.tar.gz","4":"makery.tar.gz","src_id":"25584","5":"25584","creation_date":"1505965468","6":"1505965468"},{"0":"5610","vim_version":"7.0","1":"7.0","script_version":"1.4","2":"1.4","version_comment":"Refactor autoload functions","3":"Refactor autoload functions","package":"makery.tar.gz","4":"makery.tar.gz","src_id":"25578","5":"25578","creation_date":"1505800294","6":"1505800294"},{"0":"5610","vim_version":"7.0","1":"7.0","script_version":"1.3","2":"1.3","version_comment":"Fix bug where setting both \"compiler\" and \"makeprg\" options fails to actually use the makeprg","3":"Fix bug where setting both \"compiler\" and \"makeprg\" options fails to actually use the makeprg","package":"makery.tar.gz","4":"makery.tar.gz","src_id":"25575","5":"25575","creation_date":"1505743523","6":"1505743523"},{"0":"5610","vim_version":"7.0","1":"7.0","script_version":"1.2","2":"1.2","version_comment":"Fix bug with makery#Compile: wrong number of args","3":"Fix bug with makery#Compile: wrong number of args","package":"makery.tar.gz","4":"makery.tar.gz","src_id":"25572","5":"25572","creation_date":"1505706291","6":"1505706291"},{"0":"5610","vim_version":"7.0","1":"7.0","script_version":"1.1","2":"1.1","version_comment":"Now allows setting both \"compiler\" and \"makeprg\" keys for a single command","3":"Now allows setting both \"compiler\" and \"makeprg\" keys for a single command","package":"makery.tar.gz","4":"makery.tar.gz","src_id":"25571","5":"25571","creation_date":"1505645875","6":"1505645875"},{"0":"5610","vim_version":"7.0","1":"7.0","script_version":"1","2":"1","version_comment":"Initial upload","3":"Initial upload","package":"makery.tar.gz","4":"makery.tar.gz","src_id":"25570","5":"25570","creation_date":"1505639551","6":"1505639551"}]},"5609":{"script_id":"5609","0":"5609","script_name":"qcvim","1":"qcvim","script_type":"syntax","2":"syntax","summary":"Highlighter for quantum chemistry input files","3":"Highlighter for quantum chemistry input files","description":"This is intended to be a collection of filetype plugins of input files for various quantum chemistry packages.\r\n\r\nCurrently Gaussian16 and VASP syntax highlighting is supported.\r\n\r\nThe scripts used to generate the syntax highlighting script can be found at:\r\n\r\nhttps:\/\/github.com\/xis19\/qcvim","4":"This is intended to be a collection of filetype plugins of input files for various quantum chemistry packages.\r\n\r\nCurrently Gaussian16 and VASP syntax highlighting is supported.\r\n\r\nThe scripts used to generate the syntax highlighting script can be found at:\r\n\r\nhttps:\/\/github.com\/xis19\/qcvim","install_details":"Download the zip file, decompress it to a temporary folder.\r\n\r\nCopy the files to the corresponding vim directories, in Linux:\r\n\r\nftdetect\/*.vim -> $HOME\/.vim\/ftdetect\/*.vim\r\nsyntax\/*.vim -> $HOME\/.vim\/syntax\/*.vim","5":"Download the zip file, decompress it to a temporary folder.\r\n\r\nCopy the files to the corresponding vim directories, in Linux:\r\n\r\nftdetect\/*.vim -> $HOME\/.vim\/ftdetect\/*.vim\r\nsyntax\/*.vim -> $HOME\/.vim\/syntax\/*.vim","first_name":"Xiaoge","6":"Xiaoge","last_name":"Su","7":"Su","releases":[{"0":"5609","vim_version":"6.0","1":"6.0","script_version":"0.2","2":"0.2","version_comment":"Add VASP INCAR support","3":"Add VASP INCAR support","package":"qcvim.tgz","4":"qcvim.tgz","src_id":"26109","5":"26109","creation_date":"1530726358","6":"1530726358"},{"0":"5609","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"qcvim.tgz","4":"qcvim.tgz","src_id":"25568","5":"25568","creation_date":"1505600790","6":"1505600790"}]},"5608":{"script_id":"5608","0":"5608","script_name":"vim.emacs","1":"vim.emacs","script_type":"utility","2":"utility","summary":"vim.emacs is a vim plugin to evaluate elisp expressions in Emacs.","3":"vim.emacs is a vim plugin to evaluate elisp expressions in Emacs.","description":"vim.emacs is a vim plugin to evaluate elisp expressions in Emacs with a server running.\r\n\r\nMay be useful if you edit your .emacs file with vim.\r\n\r\nIsn't it awesome?!\r\n\r\nhttps:\/\/github.com\/ollej\/vim-emacs\r\n\r\n\r\nUsage\r\n\r\nSelect a range of lines with Elisp expressions and run the command :Emacs\r\n\r\nEach line will be executed in Emacs and any output will be displayed in Vim.\r\n\r\n","4":"vim.emacs is a vim plugin to evaluate elisp expressions in Emacs with a server running.\r\n\r\nMay be useful if you edit your .emacs file with vim.\r\n\r\nIsn't it awesome?!\r\n\r\nhttps:\/\/github.com\/ollej\/vim-emacs\r\n\r\n\r\nUsage\r\n\r\nSelect a range of lines with Elisp expressions and run the command :Emacs\r\n\r\nEach line will be executed in Emacs and any output will be displayed in Vim.\r\n\r\n","install_details":"Use Vim 8, pathogen or vundle to install vim.emacs.\r\n\r\nUnzip the package into ~\/.vim\/bundle","5":"Use Vim 8, pathogen or vundle to install vim.emacs.\r\n\r\nUnzip the package into ~\/.vim\/bundle","first_name":"Olle","6":"Olle","last_name":"Johansson","7":"Johansson","releases":[{"0":"5608","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"vim-emacs-1_0.zip","4":"vim-emacs-1_0.zip","src_id":"25566","5":"25566","creation_date":"1505563852","6":"1505563852"}]},"5607":{"script_id":"5607","0":"5607","script_name":"purge_undodir.vim","1":"purge_undodir.vim","script_type":"utility","2":"utility","summary":"Purging useless undofile on exit","3":"Purging useless undofile on exit","description":"Inspired by https:\/\/blog.debiania.in.ua\/posts\/2012-07-31-purging-vim-undodir.html\r\nImplement it with pure vimscript for multiple platform support.\r\n\r\nvim persistent-undo feature is very useful, but it will always keep the undofile in undodir, even the original file was already deleted.\r\nThis plugin will purge these undofile for you. 😄\r\n\r\nTested in vim\/neovim on Windows\/Linux\/macOS\r\n\r\nThis plugin will running on VimLeave.\r\nYou can also run it manually by :call purge_undodir#purge()\r\n\r\nYou can always get the latest version on github\r\nhttps:\/\/github.com\/jsfaint\/purge_undodir.vim","4":"Inspired by https:\/\/blog.debiania.in.ua\/posts\/2012-07-31-purging-vim-undodir.html\r\nImplement it with pure vimscript for multiple platform support.\r\n\r\nvim persistent-undo feature is very useful, but it will always keep the undofile in undodir, even the original file was already deleted.\r\nThis plugin will purge these undofile for you. 😄\r\n\r\nTested in vim\/neovim on Windows\/Linux\/macOS\r\n\r\nThis plugin will running on VimLeave.\r\nYou can also run it manually by :call purge_undodir#purge()\r\n\r\nYou can always get the latest version on github\r\nhttps:\/\/github.com\/jsfaint\/purge_undodir.vim","install_details":"1. Plugin Manager\r\n\r\nUse your favorite plugin and add \"jsfaint\/purge_undodir.vim\"\r\n\r\n2. Traditional method \r\n\r\nUnzip the zip file under your .vim (*nux) or vimfiles(windows) directory.","5":"1. Plugin Manager\r\n\r\nUse your favorite plugin and add \"jsfaint\/purge_undodir.vim\"\r\n\r\n2. Traditional method \r\n\r\nUnzip the zip file under your .vim (*nux) or vimfiles(windows) directory.","first_name":"Jia","6":"Jia","last_name":"Sui","7":"Sui","releases":[{"0":"5607","vim_version":"7.3","1":"7.3","script_version":"v1.0","2":"v1.0","version_comment":"Initial upload","3":"Initial upload","package":"purge_undodir.vim-1.0.zip","4":"purge_undodir.vim-1.0.zip","src_id":"25562","5":"25562","creation_date":"1505438979","6":"1505438979"}]},"5606":{"script_id":"5606","0":"5606","script_name":"MarkdownCopy","1":"MarkdownCopy","script_type":"utility","2":"utility","summary":"Copy Markdown to clipboard as HTML","3":"Copy Markdown to clipboard as HTML","description":"A simple plugin to allow copying of buffers formatted as markdown to the clipboard as formatted HTML text.  This can be used, for example, to write emails in markdown in Vim and then paste them into Outlook as formatted text.\r\n\r\nThe plugin currently only supports Windows, although it wouldn't be too hard to port `HtmlClipboard.py` to support other operating systems and I'd welcome pull requests.  I only wrote this to allow me to write Outlook emails in Vim, so haven't tried to support Linux\/Mac OS X at the moment.\r\n\r\nNote that this uses the `HtmlClipboard` python class written by Phillip Piper and published on activestate.com.  Links in the README.md file included in the zip file.\r\n\r\nI only added the vim code.\r\n\r\nThe plugin offers two commands:\r\n\r\n:CopyToClipboardAsHtml\r\n:PasteFromClipboardAsMarkdown\r\n\r\nHopefully the names make it fairly clear what they mean.  CopyToClipboardAsHtml accepts a range, but will default to sending the entirety of the current buffer.\r\n\r\nSource code is held in a repository at https:\/\/bitbucket.org\/abudden\/vim-markdowncopy","4":"A simple plugin to allow copying of buffers formatted as markdown to the clipboard as formatted HTML text.  This can be used, for example, to write emails in markdown in Vim and then paste them into Outlook as formatted text.\r\n\r\nThe plugin currently only supports Windows, although it wouldn't be too hard to port `HtmlClipboard.py` to support other operating systems and I'd welcome pull requests.  I only wrote this to allow me to write Outlook emails in Vim, so haven't tried to support Linux\/Mac OS X at the moment.\r\n\r\nNote that this uses the `HtmlClipboard` python class written by Phillip Piper and published on activestate.com.  Links in the README.md file included in the zip file.\r\n\r\nI only added the vim code.\r\n\r\nThe plugin offers two commands:\r\n\r\n:CopyToClipboardAsHtml\r\n:PasteFromClipboardAsMarkdown\r\n\r\nHopefully the names make it fairly clear what they mean.  CopyToClipboardAsHtml accepts a range, but will default to sending the entirety of the current buffer.\r\n\r\nSource code is held in a repository at https:\/\/bitbucket.org\/abudden\/vim-markdowncopy","install_details":"Requirements\r\n\r\n1. Vim >= 8.0.254 (this plugin uses `:pyx` commands to interact with python).\r\n2. Vim must be compiled with working python support.\r\n3. Python compatible with Vim.  I've only tested this with python 3.6 at present, although it should work with any python 2.7+.\r\n4. Python module pywin32.\r\n5. A markdown-to-html (and vice-versa) conversion tool.  I use pandoc.\r\n\r\nI have tested this with 64-bit Anaconda Python 3.6.1 (which comes with pywin32 as standard), 64-bit Vim 8.0.776 from tuxproject.de and pandoc 1.19.2.1.  It was written in about half an hour so may well have a lot of bugs!\r\n\r\nInstall as per any other Vim plugin - I'd recommend pathogen, but there are plenty of other plugin managers available.","5":"Requirements\r\n\r\n1. Vim >= 8.0.254 (this plugin uses `:pyx` commands to interact with python).\r\n2. Vim must be compiled with working python support.\r\n3. Python compatible with Vim.  I've only tested this with python 3.6 at present, although it should work with any python 2.7+.\r\n4. Python module pywin32.\r\n5. A markdown-to-html (and vice-versa) conversion tool.  I use pandoc.\r\n\r\nI have tested this with 64-bit Anaconda Python 3.6.1 (which comes with pywin32 as standard), 64-bit Vim 8.0.776 from tuxproject.de and pandoc 1.19.2.1.  It was written in about half an hour so may well have a lot of bugs!\r\n\r\nInstall as per any other Vim plugin - I'd recommend pathogen, but there are plenty of other plugin managers available.","first_name":"Al","6":"Al","last_name":"Budden","7":"Budden","releases":[{"0":"5606","vim_version":"8.0","1":"8.0","script_version":"1.1.0","2":"1.1.0","version_comment":"Added inline styles to allow syntax-highlighted code to be copied into Outlook (or similar) with colours.","3":"Added inline styles to allow syntax-highlighted code to be copied into Outlook (or similar) with colours.","package":"MarkdownCopy_1.1.0.zip","4":"MarkdownCopy_1.1.0.zip","src_id":"25561","5":"25561","creation_date":"1505332443","6":"1505332443"},{"0":"5606","vim_version":"8.0","1":"8.0","script_version":"1.0.0","2":"1.0.0","version_comment":"Initial upload","3":"Initial upload","package":"MarkdownCopy_8f9d8fe836c1.zip","4":"MarkdownCopy_8f9d8fe836c1.zip","src_id":"25560","5":"25560","creation_date":"1505151567","6":"1505151567"}]},"5605":{"script_id":"5605","0":"5605","script_name":"vim-Verdin","1":"vim-Verdin","script_type":"ftplugin","2":"ftplugin","summary":"An omni-complete function for Vim script","3":"An omni-complete function for Vim script","description":" * Usage *\r\nInstall this plugin, open a vim script file and press \r\n\r\n * Auto completion *\r\nWrite this in your vimrc. Do not enable if you are using another auto-complete plugin.\r\nlet g:Verdin#autocomplete = 1\r\n\r\n* Latest version *\r\nhttps:\/\/github.com\/machakann\/vim-Verdin","4":" * Usage *\r\nInstall this plugin, open a vim script file and press \r\n\r\n * Auto completion *\r\nWrite this in your vimrc. Do not enable if you are using another auto-complete plugin.\r\nlet g:Verdin#autocomplete = 1\r\n\r\n* Latest version *\r\nhttps:\/\/github.com\/machakann\/vim-Verdin","install_details":"Unzip and just put all folders in your ~\/.vim.","5":"Unzip and just put all folders in your ~\/.vim.","first_name":"Masaaki","6":"Masaaki","last_name":"Nakamura","7":"Nakamura","releases":[{"0":"5605","vim_version":"8.0","1":"8.0","script_version":"1.0.0","2":"1.0.0","version_comment":"Initial upload","3":"Initial upload","package":"vim-Verdin-1.0.0.zip","4":"vim-Verdin-1.0.0.zip","src_id":"25552","5":"25552","creation_date":"1504626528","6":"1504626528"}]},"5604":{"script_id":"5604","0":"5604","script_name":"vim-scratchpad","1":"vim-scratchpad","script_type":"utility","2":"utility","summary":"toggle a scratchpad","3":"toggle a scratchpad","description":"This plug-in adds a key binding, by default 'dsp' (= 'Display Scratch Pad'), that toggles\r\na scratchpad. It assumes the file type 'FT' and working directory 'CWD' of the\r\ncurrently opened buffer, and is stored in 'CWD\/.scratchpads\/scratchpad.FT'\r\n\r\nThe subdirectory where the scratchpad is stored in is set by the variable\r\n\r\n    let g:scratchpad_path = '.scratchpads'\r\n\r\nand the key binding is set by the mapping\r\n\r\n    nmap dsp (ToggleScratchPad)\r\n\r\n\r\n\r\nvim-scratchpad is developed at\r\n\r\nhttps:\/\/github.com\/konfekt\/vim-scratchpad\r\n\r\nwhere issues can be filed. ","4":"This plug-in adds a key binding, by default 'dsp' (= 'Display Scratch Pad'), that toggles\r\na scratchpad. It assumes the file type 'FT' and working directory 'CWD' of the\r\ncurrently opened buffer, and is stored in 'CWD\/.scratchpads\/scratchpad.FT'\r\n\r\nThe subdirectory where the scratchpad is stored in is set by the variable\r\n\r\n    let g:scratchpad_path = '.scratchpads'\r\n\r\nand the key binding is set by the mapping\r\n\r\n    nmap dsp (ToggleScratchPad)\r\n\r\n\r\n\r\nvim-scratchpad is developed at\r\n\r\nhttps:\/\/github.com\/konfekt\/vim-scratchpad\r\n\r\nwhere issues can be filed. ","install_details":"Unzip vim-scratchpad.zip into  ~\/.vim on Linux or %USERPROFILE%\\vimfiles on Windows.","5":"Unzip vim-scratchpad.zip into  ~\/.vim on Linux or %USERPROFILE%\\vimfiles on Windows.","first_name":"Enno","6":"Enno","last_name":"Nagel","7":"Nagel","releases":[{"0":"5604","vim_version":"7.0","1":"7.0","script_version":"1.3","2":"1.3","version_comment":"permit forcing filetype, make detection of current working directory and file type more robust","3":"permit forcing filetype, make detection of current working directory and file type more robust","package":"vim-scratchpad.zip","4":"vim-scratchpad.zip","src_id":"26295","5":"26295","creation_date":"1544127479","6":"1544127479"},{"0":"5604","vim_version":"7.0","1":"7.0","script_version":"1.2","2":"1.2","version_comment":"autosave pad and ensure correct path  ","3":"autosave pad and ensure correct path  ","package":"vim-scratchpad.zip","4":"vim-scratchpad.zip","src_id":"26100","5":"26100","creation_date":"1530598106","6":"1530598106"},{"0":"5604","vim_version":"6.0","1":"6.0","script_version":"1.1","2":"1.1","version_comment":"place the scratchpad window more conveniently","3":"place the scratchpad window more conveniently","package":"vim-scratchpad.zip","4":"vim-scratchpad.zip","src_id":"25973","5":"25973","creation_date":"1525987319","6":"1525987319"},{"0":"5604","vim_version":"5.7","1":"5.7","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"vim-scratchpad.zip","4":"vim-scratchpad.zip","src_id":"25550","5":"25550","creation_date":"1504547437","6":"1504547437"}]},"5602":{"script_id":"5602","0":"5602","script_name":"fix-vim-pasting","1":"fix-vim-pasting","script_type":"utility","2":"utility","summary":"Fixes pasting in Vim, so it works as you expect.","3":"Fixes pasting in Vim, so it works as you expect.","description":"Vim tends to hate indenting code properly that is pasted into it. This even works with tmux. If you aren't into plugins, you can paste the contents of the script right into your .vimrc.","4":"Vim tends to hate indenting code properly that is pasted into it. This even works with tmux. If you aren't into plugins, you can paste the contents of the script right into your .vimrc.","install_details":"mkdir -p ~\/.vim\/plugin\/\r\nwget -N https:\/\/raw.githubusercontent.com\/ryanpcmcquen\/fix-vim-pasting\/master\/plugin\/fix-vim-pasting.vim -P ~\/.vim\/plugin\/","5":"mkdir -p ~\/.vim\/plugin\/\r\nwget -N https:\/\/raw.githubusercontent.com\/ryanpcmcquen\/fix-vim-pasting\/master\/plugin\/fix-vim-pasting.vim -P ~\/.vim\/plugin\/","first_name":"Ryan","6":"Ryan","last_name":"McQuen","7":"McQuen","releases":[{"0":"5602","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"fix-vim-pasting.vim","4":"fix-vim-pasting.vim","src_id":"25539","5":"25539","creation_date":"1504046575","6":"1504046575"}]},"5601":{"script_id":"5601","0":"5601","script_name":"AutoOrigami.vim","1":"AutoOrigami.vim","script_type":"utility","2":"utility","summary":"Automatically set \\'foldcolumn\\'","3":"Automatically set \\'foldcolumn\\'","description":"See README.md and :help auto-origami\r\n\r\nhttps:\/\/github.com\/benknoble\/vim-auto-origami","4":"See README.md and :help auto-origami\r\n\r\nhttps:\/\/github.com\/benknoble\/vim-auto-origami","install_details":"I recommend using Pathogen (https:\/\/github.com\/tpope\/vim-pathogen), then just extract the files to your ~\/.vim\/bundle directory.","5":"I recommend using Pathogen (https:\/\/github.com\/tpope\/vim-pathogen), then just extract the files to your ~\/.vim\/bundle directory.","first_name":"David","6":"David","last_name":"Knoble","7":"Knoble","releases":[{"0":"5601","vim_version":"7.0","1":"7.0","script_version":"v1.1.0","2":"v1.1.0","version_comment":"New 'foldenable' feature","3":"New 'foldenable' feature","package":"auto-origami-1.1.0.tar.gz","4":"auto-origami-1.1.0.tar.gz","src_id":"25832","5":"25832","creation_date":"1519060284","6":"1519060284"},{"0":"5601","vim_version":"8.0","1":"8.0","script_version":"v1.0.0","2":"v1.0.0","version_comment":"Initial upload","3":"Initial upload","package":"AutoOrigami.tar.gz","4":"AutoOrigami.tar.gz","src_id":"25533","5":"25533","creation_date":"1503811884","6":"1503811884"}]},"5600":{"script_id":"5600","0":"5600","script_name":"vim-CtrlXA","1":"vim-CtrlXA","script_type":"utility","2":"utility","summary":" make Ctrl-X and Ctrl-A run through keyword cycles","3":" make Ctrl-X and Ctrl-A run through keyword cycles","description":"With this Vim plug-in, the key bindings ||\/|| (and |g|\/|g|) additionally cycle through lists of keywords such as |true|\/|false|, |yes|\/|no|, |yesterday|\/|today|\/|tomorrow| or roman numerals |I|, |II|, |III|...\r\nUseful, for example:\r\n\r\n- for toggling settings in a configuration file,\r\n- for toggling language modifiers such as |public|\/|private|,\r\n- for switching between |pick|, |squash|, |reword|, ... a |git| commit when rebasing, ...\r\n\r\nKeyword cycles are provided for common programming and natural languages\r\n(inspectable in the `ftplugin` respectively `autoload\/CtrlXA\/langs` folders).\r\n\r\nRepetition of the last command by hitting |.| (see |:help .|) is achieved\r\n\r\n- in normal mode by vim-repeat[1], and\r\n- in visual mode by vim-visualrepeat[2].\r\n\r\n[1]: https:\/\/github.com\/tpope\/vim-repeat\r\n[2]: https:\/\/github.com\/inkarkat\/vim-visualrepeat\r\n\r\nGLOBAL SETUP ~\r\n\r\nThese keyword cycles are configurable by the variable |g:CtrlXA_Toggles| whose default value can be seen in https:\/\/github.com\/Konfekt\/vim-CtrlXA\/blob\/master\/plugin\/CtrlXA\/toggles.vim\r\n\r\nIf you want to add a cycle, say the pair |['sweet', 'bitter']|, to the default list of cycles, then\r\n\r\n- either put\r\n\r\n    let g:CtrlXA_Toggles = [\r\n    \\ ['sweet', 'bitter'],\r\n    \\ ] + g:CtrlXA_Toggles\r\n\r\ninto a file |~\/.vim\/after\/plugin\/CtrlXA.vim| on Linux (respectively |%USERPROFILE%\\vimfiles\\after\\plugin\\CtrlXA.vim| on Microsoft Windows), or\r\n- put into your |vimrc| the lines\r\n\r\n    augroup VimAfter\r\n    autocmd!\r\n    autocmd VimEnter let g:CtrlXA_Toggles = [\r\n    \\ ['sweet', 'bitter'],\r\n    \\ ] + g:CtrlXA_Toggles\r\n    augroup END\r\n\r\nKeywords consist of the keyword characters determined by the global variable |g:CtrlXA_iskeyword|.\r\nBy default, this variable takes the same value as |&g:iskeyword| (see |:help iskeyword|) with the exception of the underscore |_| which is removed from |g:CtrlXA_iskeyword|.\r\n\r\nIf you want the cursor to move to the keyword (among |g:CtrlXA_Toggles|) that was changed after hitting a key (mapped to |(CtrlXA-CtrlA)| or |(CtrlXA-CtrlX)|), then set the global variable |g:CtrlXA_move| to |1|.\r\nBy default, the cursor only moves to a changed number, as Vim does by default.\r\n\r\nIf you prefer |i|, |v| and |I|, |V| to run through the letters of the Latin\r\nalphabet instead of the Roman numerals, move these letters from the pair of\r\narrays containing the roman numerals to that containing the Latin alphabet.\r\n\r\nBUFFER-LOCAL SETUP ~\r\n\r\nThere is also the buffer-local list of keyword cycles |b:CtrlXA_iskeyword|, which allows for file-type specific keyword cycles.\r\nFor example, as included by default:\r\n\r\n    autocmd FileType gitrebase\r\n    \\ let b:CtrlXA_Toggles = [\r\n    \\ ['pick', 'fixup', 'squash', 'break', 'reword', 'edit', 'drop'],\r\n    \\ ] + get(b:, 'CtrlXA_Toggles', g:CtrlXA_Toggles)\r\n\r\nThis will\r\n\r\n- include all keyword cycles of the global variable, and\r\n- add (buffer-)local keyword cycles which have precedence over the global cycles.\r\n\r\nTo add keyword cycles for other file types, add\r\n\r\n- either the four lines above to |~\/.vimrc| on Linux or MacOS (respectively |%USERPROFILE%\\_vimrc| on Microsoft Windows), or\r\n- the last three lines above to |~\/.vim\/after\/ftplugin\/gitrebase.vim| on Linux (respectively |%USERPROFILE%\\vimfiles\\after\/ftplugin\\gitrebase.vim| on Microsoft Windows).\r\n","4":"With this Vim plug-in, the key bindings ||\/|| (and |g|\/|g|) additionally cycle through lists of keywords such as |true|\/|false|, |yes|\/|no|, |yesterday|\/|today|\/|tomorrow| or roman numerals |I|, |II|, |III|...\r\nUseful, for example:\r\n\r\n- for toggling settings in a configuration file,\r\n- for toggling language modifiers such as |public|\/|private|,\r\n- for switching between |pick|, |squash|, |reword|, ... a |git| commit when rebasing, ...\r\n\r\nKeyword cycles are provided for common programming and natural languages\r\n(inspectable in the `ftplugin` respectively `autoload\/CtrlXA\/langs` folders).\r\n\r\nRepetition of the last command by hitting |.| (see |:help .|) is achieved\r\n\r\n- in normal mode by vim-repeat[1], and\r\n- in visual mode by vim-visualrepeat[2].\r\n\r\n[1]: https:\/\/github.com\/tpope\/vim-repeat\r\n[2]: https:\/\/github.com\/inkarkat\/vim-visualrepeat\r\n\r\nGLOBAL SETUP ~\r\n\r\nThese keyword cycles are configurable by the variable |g:CtrlXA_Toggles| whose default value can be seen in https:\/\/github.com\/Konfekt\/vim-CtrlXA\/blob\/master\/plugin\/CtrlXA\/toggles.vim\r\n\r\nIf you want to add a cycle, say the pair |['sweet', 'bitter']|, to the default list of cycles, then\r\n\r\n- either put\r\n\r\n    let g:CtrlXA_Toggles = [\r\n    \\ ['sweet', 'bitter'],\r\n    \\ ] + g:CtrlXA_Toggles\r\n\r\ninto a file |~\/.vim\/after\/plugin\/CtrlXA.vim| on Linux (respectively |%USERPROFILE%\\vimfiles\\after\\plugin\\CtrlXA.vim| on Microsoft Windows), or\r\n- put into your |vimrc| the lines\r\n\r\n    augroup VimAfter\r\n    autocmd!\r\n    autocmd VimEnter let g:CtrlXA_Toggles = [\r\n    \\ ['sweet', 'bitter'],\r\n    \\ ] + g:CtrlXA_Toggles\r\n    augroup END\r\n\r\nKeywords consist of the keyword characters determined by the global variable |g:CtrlXA_iskeyword|.\r\nBy default, this variable takes the same value as |&g:iskeyword| (see |:help iskeyword|) with the exception of the underscore |_| which is removed from |g:CtrlXA_iskeyword|.\r\n\r\nIf you want the cursor to move to the keyword (among |g:CtrlXA_Toggles|) that was changed after hitting a key (mapped to |(CtrlXA-CtrlA)| or |(CtrlXA-CtrlX)|), then set the global variable |g:CtrlXA_move| to |1|.\r\nBy default, the cursor only moves to a changed number, as Vim does by default.\r\n\r\nIf you prefer |i|, |v| and |I|, |V| to run through the letters of the Latin\r\nalphabet instead of the Roman numerals, move these letters from the pair of\r\narrays containing the roman numerals to that containing the Latin alphabet.\r\n\r\nBUFFER-LOCAL SETUP ~\r\n\r\nThere is also the buffer-local list of keyword cycles |b:CtrlXA_iskeyword|, which allows for file-type specific keyword cycles.\r\nFor example, as included by default:\r\n\r\n    autocmd FileType gitrebase\r\n    \\ let b:CtrlXA_Toggles = [\r\n    \\ ['pick', 'fixup', 'squash', 'break', 'reword', 'edit', 'drop'],\r\n    \\ ] + get(b:, 'CtrlXA_Toggles', g:CtrlXA_Toggles)\r\n\r\nThis will\r\n\r\n- include all keyword cycles of the global variable, and\r\n- add (buffer-)local keyword cycles which have precedence over the global cycles.\r\n\r\nTo add keyword cycles for other file types, add\r\n\r\n- either the four lines above to |~\/.vimrc| on Linux or MacOS (respectively |%USERPROFILE%\\_vimrc| on Microsoft Windows), or\r\n- the last three lines above to |~\/.vim\/after\/ftplugin\/gitrebase.vim| on Linux (respectively |%USERPROFILE%\\vimfiles\\after\/ftplugin\\gitrebase.vim| on Microsoft Windows).\r\n","install_details":"unzip vim-CtrlXA.zip into ~\/.vim (respectivley %USERPROFILE\/_vim in Microsoft Windows).","5":"unzip vim-CtrlXA.zip into ~\/.vim (respectivley %USERPROFILE\/_vim in Microsoft Windows).","first_name":"Enno","6":"Enno","last_name":"Nagel","7":"Nagel","releases":[{"0":"5600","vim_version":"7.0","1":"7.0","script_version":"1.12","2":"1.12","version_comment":"reorganize localized lists for easier customization","3":"reorganize localized lists for easier customization","package":"vim-CtrlXA.zip","4":"vim-CtrlXA.zip","src_id":"28658","5":"28658","creation_date":"1711565524","6":"1711565524"},{"0":"5600","vim_version":"7.0","1":"7.0","script_version":"1.11","2":"1.11","version_comment":"add many general, localized and file type specific keyword cycles","3":"add many general, localized and file type specific keyword cycles","package":"vim-CtrlXA.zip","4":"vim-CtrlXA.zip","src_id":"28635","5":"28635","creation_date":"1709366628","6":"1709366628"},{"0":"5600","vim_version":"7.0","1":"7.0","script_version":"1.10","2":"1.10","version_comment":"support nested keywords","3":"support nested keywords","package":"vim-CtrlXA.zip","4":"vim-CtrlXA.zip","src_id":"27856","5":"27856","creation_date":"1639927140","6":"1639927140"},{"0":"5600","vim_version":"7.0","1":"7.0","script_version":"1.9","2":"1.9","version_comment":"simplify and speed up numeral increment","3":"simplify and speed up numeral increment","package":"vim-CtrlXA.zip","4":"vim-CtrlXA.zip","src_id":"27515","5":"27515","creation_date":"1614899603","6":"1614899603"},{"0":"5600","vim_version":"7.0","1":"7.0","script_version":"1.8","2":"1.8","version_comment":"toggle keywords behind cursor word","3":"toggle keywords behind cursor word","package":"vim-CtrlXA.zip","4":"vim-CtrlXA.zip","src_id":"27288","5":"27288","creation_date":"1597679642","6":"1597679642"},{"0":"5600","vim_version":"7.0","1":"7.0","script_version":"1.7","2":"1.7","version_comment":"fix corner cases of g","3":"fix corner cases of g","package":"vim-CtrlXA.zip","4":"vim-CtrlXA.zip","src_id":"27090","5":"27090","creation_date":"1585007573","6":"1585007573"},{"0":"5600","vim_version":"7.0","1":"7.0","script_version":"1.6","2":"1.6","version_comment":"add visual mappings","3":"add visual mappings","package":"vim-CtrlXA.zip","4":"vim-CtrlXA.zip","src_id":"26966","5":"26966","creation_date":"1581041090","6":"1581041090"},{"0":"5600","vim_version":"7.0","1":"7.0","script_version":"1.5","2":"1.5","version_comment":"various additions and corrections; see the commits in the GitHub repo","3":"various additions and corrections; see the commits in the GitHub repo","package":"vim-CtrlXA.zip","4":"vim-CtrlXA.zip","src_id":"26892","5":"26892","creation_date":"1578516031","6":"1578516031"},{"0":"5600","vim_version":"7.0","1":"7.0","script_version":"1.4","2":"1.4","version_comment":"make ctrl-x\/a act oppositely; add enumeration markers","3":"make ctrl-x\/a act oppositely; add enumeration markers","package":"vim-CtrlXA.zip","4":"vim-CtrlXA.zip","src_id":"26446","5":"26446","creation_date":"1554233806","6":"1554233806"},{"0":"5600","vim_version":"6.0","1":"6.0","script_version":"1.3","2":"1.3","version_comment":"more default lists","3":"more default lists","package":"vim-CtrlXA.zip","4":"vim-CtrlXA.zip","src_id":"26294","5":"26294","creation_date":"1544127329","6":"1544127329"},{"0":"5600","vim_version":"5.7","1":"5.7","script_version":"1.2","2":"1.2","version_comment":"allow for non-keyword characters","3":"allow for non-keyword characters","package":"vim-CtrlXA.zip","4":"vim-CtrlXA.zip","src_id":"25545","5":"25545","creation_date":"1504191266","6":"1504191266"},{"0":"5600","vim_version":"5.7","1":"5.7","script_version":"1.1","2":"1.1","version_comment":"Support file-type specific keyword cycles.","3":"Support file-type specific keyword cycles.","package":"vim-CtrlXA.zip","4":"vim-CtrlXA.zip","src_id":"25538","5":"25538","creation_date":"1503964904","6":"1503964904"},{"0":"5600","vim_version":"5.7","1":"5.7","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"vim-CtrlXA.zip","4":"vim-CtrlXA.zip","src_id":"25530","5":"25530","creation_date":"1503774618","6":"1503774618"}]},"5599":{"script_id":"5599","0":"5599","script_name":"octopus.vim","1":"octopus.vim","script_type":"syntax","2":"syntax","summary":"syntax highlighting for octopus","3":"syntax highlighting for octopus","description":"Syntax highlighting for the (TD)DFT code octopus (see http:\/\/octopus-code.org).","4":"Syntax highlighting for the (TD)DFT code octopus (see http:\/\/octopus-code.org).","install_details":"Place the script in ~\/.vim\/syntax\/. You can then activate the syntax highlighting via :set filetype=octopus.\r\n\r\nTo automatically activate the syntax highlighting when opening a file named inp put the following line in a file ~\/.vim\/ftdetect\/octopus.vim\r\n  au BufRead,BufNewFile inp set filetype=octopus\r\n\r\nFor more information see\r\n  :help mysyntaxfile\r\n  :help new-filetype","5":"Place the script in ~\/.vim\/syntax\/. You can then activate the syntax highlighting via :set filetype=octopus.\r\n\r\nTo automatically activate the syntax highlighting when opening a file named inp put the following line in a file ~\/.vim\/ftdetect\/octopus.vim\r\n  au BufRead,BufNewFile inp set filetype=octopus\r\n\r\nFor more information see\r\n  :help mysyntaxfile\r\n  :help new-filetype","first_name":"Christian Richard","6":"Christian Richard","last_name":"Kalh\u00c3\u00b6fer","7":"Kalh\u00c3\u00b6fer","releases":[{"0":"5599","vim_version":"8.0","1":"8.0","script_version":"8.0","2":"8.0","version_comment":"Syntax highlighting for octopus 8.0 input files","3":"Syntax highlighting for octopus 8.0 input files","package":"octopus.vim","4":"octopus.vim","src_id":"26061","5":"26061","creation_date":"1529349984","6":"1529349984"},{"0":"5599","vim_version":"8.0","1":"8.0","script_version":"7.1","2":"7.1","version_comment":"Syntax highlighting for octopus 7.1 input files","3":"Syntax highlighting for octopus 7.1 input files","package":"octopus.vim","4":"octopus.vim","src_id":"25619","5":"25619","creation_date":"1508937930","6":"1508937930"}]},"5598":{"script_id":"5598","0":"5598","script_name":"mbed-vim","1":"mbed-vim","script_type":"utility","2":"utility","summary":"Execute mbed CLI commands without exiting Vim!","3":"Execute mbed CLI commands without exiting Vim!","description":"Github repository: https:\/\/github.com\/marrakchino\/mbed-vim\r\n\r\nThis file contains routines that may be used to execute mbed CLI commands\r\nfrom within VIM. It depends on mbed OS. Therefore, \r\nyou must have mbed CLI correctly installed \r\n(see https:\/\/github.com\/ARMmbed\/mbed-cli#installation).\r\n\r\n* Used variables:\r\ng:mbed_target \/ g:mbed_toolchain : These variables default to the content read from the ~\/.mbed file, and eventually overwritten by the local .mbed file.\r\nThey can be forced to reset by calling MbedSetTargetandToolchain(1) (mapped to  key) or serparately using the :SetTarget and :SetToolchain commands.\r\n\r\n* In command mode:\r\n  c:   Compile the current application\r\n  C:  Clean the build directory and compile the current application\r\n  cf:  Compile and flash the built firmware onto a connected target\r\n  cv: Compile the current application in verbose mode\r\n  cV: Compile the current application in very verbose mode\r\n  n:   Create a new mbed program or library\r\n  s:   Synchronize all library and dependency references\r\n  t:    Find, build and run tests\r\n  d:   Import missing dependencies\r\n  a:   Prompt for an mbed library to add\r\n  r:    Prompt for an mbed library to remove\r\n  l:    Display dependency tree\r\n  :           Close the error buffer (when open)\r\n  :         Set the current application\\\\\\'s target and toolchain \r\n\r\n  Add  --       Add the specified library. When no argument is given,\r\n                            you are prompted for the name of the library\r\n  Remove  --    Remove the specified library. When no argument is given,\r\n                            you are prompted for the name of the library\r\n  SetToolchain  -- Set a toolchain (ARM, GCC_ARM, IAR)\r\n  SetTarget  --       Set a target\r\n","4":"Github repository: https:\/\/github.com\/marrakchino\/mbed-vim\r\n\r\nThis file contains routines that may be used to execute mbed CLI commands\r\nfrom within VIM. It depends on mbed OS. Therefore, \r\nyou must have mbed CLI correctly installed \r\n(see https:\/\/github.com\/ARMmbed\/mbed-cli#installation).\r\n\r\n* Used variables:\r\ng:mbed_target \/ g:mbed_toolchain : These variables default to the content read from the ~\/.mbed file, and eventually overwritten by the local .mbed file.\r\nThey can be forced to reset by calling MbedSetTargetandToolchain(1) (mapped to  key) or serparately using the :SetTarget and :SetToolchain commands.\r\n\r\n* In command mode:\r\n  c:   Compile the current application\r\n  C:  Clean the build directory and compile the current application\r\n  cf:  Compile and flash the built firmware onto a connected target\r\n  cv: Compile the current application in verbose mode\r\n  cV: Compile the current application in very verbose mode\r\n  n:   Create a new mbed program or library\r\n  s:   Synchronize all library and dependency references\r\n  t:    Find, build and run tests\r\n  d:   Import missing dependencies\r\n  a:   Prompt for an mbed library to add\r\n  r:    Prompt for an mbed library to remove\r\n  l:    Display dependency tree\r\n  :           Close the error buffer (when open)\r\n  :         Set the current application\\\\\\'s target and toolchain \r\n\r\n  Add  --       Add the specified library. When no argument is given,\r\n                            you are prompted for the name of the library\r\n  Remove  --    Remove the specified library. When no argument is given,\r\n                            you are prompted for the name of the library\r\n  SetToolchain  -- Set a toolchain (ARM, GCC_ARM, IAR)\r\n  SetTarget  --       Set a target\r\n","install_details":"Copy the mbed.vim script to your $HOME\/.vim\/plugin directory to install it. This operation can be done easiy by executing the following command in a terminal:\r\n$ wget https:\/\/raw.githubusercontent.com\/nelqatib\/mbed-vim\/master\/plugin\/mbed.vim -O ~\/.vim\/plugin\/mbed.vim\r\n\r\n Make sure you have properly installed mbed CLI before using this plugin.","5":"Copy the mbed.vim script to your $HOME\/.vim\/plugin directory to install it. This operation can be done easiy by executing the following command in a terminal:\r\n$ wget https:\/\/raw.githubusercontent.com\/nelqatib\/mbed-vim\/master\/plugin\/mbed.vim -O ~\/.vim\/plugin\/mbed.vim\r\n\r\n Make sure you have properly installed mbed CLI before using this plugin.","first_name":"Nabil","6":"Nabil","last_name":"Elqatib","7":"Elqatib","releases":[{"0":"5598","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"First major version\r\n\r\nUseful variables are window-scoped, MbedList() resulting buffer is nofile type, useful variables are read from global configuration and eventually overwritten if a local config exists.\r\n\r\nFixes #12 , fixes #15 , fixes #14 , closes #16\r\n","3":"First major version\r\n\r\nUseful variables are window-scoped, MbedList() resulting buffer is nofile type, useful variables are read from global configuration and eventually overwritten if a local config exists.\r\n\r\nFixes #12 , fixes #15 , fixes #14 , closes #16\r\n","package":"mbed.vim","4":"mbed.vim","src_id":"25524","5":"25524","creation_date":"1503429681","6":"1503429681"},{"0":"5598","vim_version":"7.0","1":"7.0","script_version":"0.2","2":"0.2","version_comment":"Minor bug fixes, new mappings","3":"Minor bug fixes, new mappings","package":"mbed.vim","4":"mbed.vim","src_id":"25513","5":"25513","creation_date":"1502971477","6":"1502971477"},{"0":"5598","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"mbed.vim","4":"mbed.vim","src_id":"25497","5":"25497","creation_date":"1502406403","6":"1502406403"}]},"5596":{"script_id":"5596","0":"5596","script_name":"SubstituteExpression","1":"SubstituteExpression","script_type":"utility","2":"utility","summary":"Pass text through an expression.","3":"Pass text through an expression.","description":"DESCRIPTION\r\nVim has powerful built-in functions for text manipulation, and maybe you have\r\nwritten some custom ones. To apply one of those to text in the buffer, you'd\r\nhave to use sub-replace-expression, or a getline() \/ setline() combo.\r\nThis works for whole lines, but what if you need to change only parts?\r\nYou may have an external program that transforms text. Again, filtering entire\r\nlines is easy with built-in :range!, but what about arbitrary text?\r\n\r\nThis plugin allows to pass text covered by a {motion}, or arbitrary visual\r\nselections, through a queried Vimscript expression, or external shell command,\r\nor an Ex command that is applied in a separate scratch buffer, and then\r\nreplace the original text with the result.\r\nAs substitutions are a particularly common use case, the plugin offers a\r\nspecial shortcut mapping for those.\r\n\r\nSOURCE\r\nExtracted from my Substitutions.vim plugin; incorporated mappings and ideas\r\nfrom the Express plugin.\r\n\r\nRELATED WORKS\r\n- express.vim (https:\/\/github.com\/tommcdo\/vim-express) by Tom McDonald offers\r\n  an almost identical implementation. It also allows on-the-fly creation of\r\n  operators via :MapExpress and :MapSubpress, something for which I would use\r\n  my TextTransform.vim plugin. My plugin offers more advanced (cross-mode)\r\n  repeats, and the :Ex-command expression variant.\r\n\r\nUSAGE\r\ng={motion}              Query for an expression, and pass the text defined by\r\n                        {motion} to it, then replace the text in the buffer\r\n                        with the result.\r\n                        The expression can be:\r\n                        - a Vimscript expression; v:val will contain the\r\n                          text.\r\n                        - a function name (without parentheses); the function\r\n                          will be passed the text as a single String argument.\r\n                        - If the expression begins with '!', it will be\r\n                          treated as an external command, and passed to the\r\n                          system() function, with the text as stdin. (To use\r\n                          an expression beginning with logical not (expr-!),\r\n                          include a space before the '!' character.)\r\n                        - If the expression begins with ':', the text will be\r\n                          placed in a scratch buffer (of the same 'filetype'),\r\n                          and the Ex command(s) will be applied.\r\n\r\n{Visual}g=              Like g=, but for the current selection.\r\ng==                     Like g=, but for the current line. linewise\r\n\r\ng:{motion}              Like g=, but input `pattern\/replace\/flags` similar to\r\n                        :substitute. Individual lines are filtered through\r\n                        the substitute() function, as if invoked by g=\r\n                        using 'substitute(v:val, ...)'.\r\n                        Note: Despite looking like a :substitute command,\r\n                        this is really one call to substitute() for each\r\n                        line, so the behavior is slightly different.\r\n{Visual}g:              Like g:, but for the current selection.\r\ng::                     Like g:, but for the current line. linewise","4":"DESCRIPTION\r\nVim has powerful built-in functions for text manipulation, and maybe you have\r\nwritten some custom ones. To apply one of those to text in the buffer, you'd\r\nhave to use sub-replace-expression, or a getline() \/ setline() combo.\r\nThis works for whole lines, but what if you need to change only parts?\r\nYou may have an external program that transforms text. Again, filtering entire\r\nlines is easy with built-in :range!, but what about arbitrary text?\r\n\r\nThis plugin allows to pass text covered by a {motion}, or arbitrary visual\r\nselections, through a queried Vimscript expression, or external shell command,\r\nor an Ex command that is applied in a separate scratch buffer, and then\r\nreplace the original text with the result.\r\nAs substitutions are a particularly common use case, the plugin offers a\r\nspecial shortcut mapping for those.\r\n\r\nSOURCE\r\nExtracted from my Substitutions.vim plugin; incorporated mappings and ideas\r\nfrom the Express plugin.\r\n\r\nRELATED WORKS\r\n- express.vim (https:\/\/github.com\/tommcdo\/vim-express) by Tom McDonald offers\r\n  an almost identical implementation. It also allows on-the-fly creation of\r\n  operators via :MapExpress and :MapSubpress, something for which I would use\r\n  my TextTransform.vim plugin. My plugin offers more advanced (cross-mode)\r\n  repeats, and the :Ex-command expression variant.\r\n\r\nUSAGE\r\ng={motion}              Query for an expression, and pass the text defined by\r\n                        {motion} to it, then replace the text in the buffer\r\n                        with the result.\r\n                        The expression can be:\r\n                        - a Vimscript expression; v:val will contain the\r\n                          text.\r\n                        - a function name (without parentheses); the function\r\n                          will be passed the text as a single String argument.\r\n                        - If the expression begins with '!', it will be\r\n                          treated as an external command, and passed to the\r\n                          system() function, with the text as stdin. (To use\r\n                          an expression beginning with logical not (expr-!),\r\n                          include a space before the '!' character.)\r\n                        - If the expression begins with ':', the text will be\r\n                          placed in a scratch buffer (of the same 'filetype'),\r\n                          and the Ex command(s) will be applied.\r\n\r\n{Visual}g=              Like g=, but for the current selection.\r\ng==                     Like g=, but for the current line. linewise\r\n\r\ng:{motion}              Like g=, but input `pattern\/replace\/flags` similar to\r\n                        :substitute. Individual lines are filtered through\r\n                        the substitute() function, as if invoked by g=\r\n                        using 'substitute(v:val, ...)'.\r\n                        Note: Despite looking like a :substitute command,\r\n                        this is really one call to substitute() for each\r\n                        line, so the behavior is slightly different.\r\n{Visual}g:              Like g:, but for the current selection.\r\ng::                     Like g:, but for the current line. linewise","install_details":"INSTALLATION\r\nThe code is hosted in a Git repo at\r\n    https:\/\/github.com\/inkarkat\/vim-SubstituteExpression\r\nYou can use your favorite plugin manager, or \"git clone\" into a directory used\r\nfor Vim packages. Releases are on the \"stable\" branch, the latest unstable\r\ndevelopment snapshot on \"master\".\r\n\r\nThis script is also packaged as a vimball. If you have the \"gunzip\"\r\ndecompressor in your PATH, simply edit the *.vmb.gz package in Vim; otherwise,\r\ndecompress the archive first, e.g. using WinZip. Inside Vim, install by\r\nsourcing the vimball or via the :UseVimball command.\r\n    vim SubstituteExpression*.vmb.gz\r\n    :so %\r\nTo uninstall, use the :RmVimball command.\r\n\r\nDEPENDENCIES\r\n- Requires Vim 7.0 or higher.\r\n- Requires the ingo-library.vim plugin (vimscript #4433), version 1.027 or\r\n  higher.\r\n- Requires the TextTransform.vim plugin (vimscript #4005), version 1.25 or\r\n  higher.\r\n\r\nCONFIGURATION\r\nFor a permanent configuration, put the following commands into your vimrc:\r\n\r\nIf you want to use different mappings, map your keys to the\r\nTextTSubstituteExpression#... mapping targets _before_ sourcing the\r\nscript (e.g. in your vimrc):\r\n    nmap g== TextTSubstituteExpression#ExpressionLine\r\n    nmap g= TextTSubstituteExpression#ExpressionOperator\r\n    xmap g= TextTSubstituteExpression#ExpressionVisual\r\n    nmap g:: TextTSubstituteExpression#SubstituteLine\r\n    nmap g: TextTSubstituteExpression#SubstituteOperator\r\n    xmap g: TextTSubstituteExpression#SubstituteVisual","5":"INSTALLATION\r\nThe code is hosted in a Git repo at\r\n    https:\/\/github.com\/inkarkat\/vim-SubstituteExpression\r\nYou can use your favorite plugin manager, or \"git clone\" into a directory used\r\nfor Vim packages. Releases are on the \"stable\" branch, the latest unstable\r\ndevelopment snapshot on \"master\".\r\n\r\nThis script is also packaged as a vimball. If you have the \"gunzip\"\r\ndecompressor in your PATH, simply edit the *.vmb.gz package in Vim; otherwise,\r\ndecompress the archive first, e.g. using WinZip. Inside Vim, install by\r\nsourcing the vimball or via the :UseVimball command.\r\n    vim SubstituteExpression*.vmb.gz\r\n    :so %\r\nTo uninstall, use the :RmVimball command.\r\n\r\nDEPENDENCIES\r\n- Requires Vim 7.0 or higher.\r\n- Requires the ingo-library.vim plugin (vimscript #4433), version 1.027 or\r\n  higher.\r\n- Requires the TextTransform.vim plugin (vimscript #4005), version 1.25 or\r\n  higher.\r\n\r\nCONFIGURATION\r\nFor a permanent configuration, put the following commands into your vimrc:\r\n\r\nIf you want to use different mappings, map your keys to the\r\nTextTSubstituteExpression#... mapping targets _before_ sourcing the\r\nscript (e.g. in your vimrc):\r\n    nmap g== TextTSubstituteExpression#ExpressionLine\r\n    nmap g= TextTSubstituteExpression#ExpressionOperator\r\n    xmap g= TextTSubstituteExpression#ExpressionVisual\r\n    nmap g:: TextTSubstituteExpression#SubstituteLine\r\n    nmap g: TextTSubstituteExpression#SubstituteOperator\r\n    xmap g: TextTSubstituteExpression#SubstituteVisual","first_name":"Ingo","6":"Ingo","last_name":"Karkat","7":"Karkat","releases":[{"0":"5596","vim_version":"7.0","1":"7.0","script_version":"1.00","2":"1.00","version_comment":"Initial upload","3":"Initial upload","package":"SubstituteExpression-1.00.vmb.gz","4":"SubstituteExpression-1.00.vmb.gz","src_id":"25447","5":"25447","creation_date":"1500987763","6":"1500987763"}]},"5595":{"script_id":"5595","0":"5595","script_name":"smart-tabline.vim","1":"smart-tabline.vim","script_type":"utility","2":"utility","summary":"maintains buffers for the tab it belongs to","3":"maintains buffers for the tab it belongs to","description":"This plugin is fork from vim-ctrlspace\/vim-ctrlspace. It remove all features but not tabline. You can't use it with vim-ctrlspace together.\r\n\r\nThis plugin maintains buffers for the tab it belongs to.\r\n\r\nFor example, you have two tabs. The first tab has 2 buffers, a.txt and b.txt. The second tab has 2 buffers, 1.txt and 2.txt. The tabline only show a.txt and b.txt when you are in the first tab. If you go to the second tab use gt, The tabline will show 1.txt and 2.txt.\r\n\r\n","4":"This plugin is fork from vim-ctrlspace\/vim-ctrlspace. It remove all features but not tabline. You can't use it with vim-ctrlspace together.\r\n\r\nThis plugin maintains buffers for the tab it belongs to.\r\n\r\nFor example, you have two tabs. The first tab has 2 buffers, a.txt and b.txt. The second tab has 2 buffers, 1.txt and 2.txt. The tabline only show a.txt and b.txt when you are in the first tab. If you go to the second tab use gt, The tabline will show 1.txt and 2.txt.\r\n\r\n","install_details":"vim-plug\r\nPlug 'tenfyzhong\/smart-tabline.vim'\r\nManual\r\ngit clone https:\/\/github.com\/tenfyzhong\/smart-tabline.vim.git ~\/.vim\/bundle\/smart-tabline.vim\r\necho 'set rtp+=~\/.vim\/bundle\/smart-tabline.vim' >> ~\/.vimrc\r\nvim -c 'helptag ~\/.vim\/bundle\/smart-tabline.vim\/doc' -c qa!\r\n","5":"vim-plug\r\nPlug 'tenfyzhong\/smart-tabline.vim'\r\nManual\r\ngit clone https:\/\/github.com\/tenfyzhong\/smart-tabline.vim.git ~\/.vim\/bundle\/smart-tabline.vim\r\necho 'set rtp+=~\/.vim\/bundle\/smart-tabline.vim' >> ~\/.vimrc\r\nvim -c 'helptag ~\/.vim\/bundle\/smart-tabline.vim\/doc' -c qa!\r\n","first_name":"tenfy","6":"tenfy","last_name":"zhong","7":"zhong","releases":[{"0":"5595","vim_version":"7.0","1":"7.0","script_version":"0.0.2","2":"0.0.2","version_comment":"Add options. ","3":"Add options. ","package":"smart-tabline.vim-0.0.2.tar.gz","4":"smart-tabline.vim-0.0.2.tar.gz","src_id":"25446","5":"25446","creation_date":"1500966630","6":"1500966630"},{"0":"5595","vim_version":"7.0","1":"7.0","script_version":"0.0.1","2":"0.0.1","version_comment":"Initial upload","3":"Initial upload","package":"smart-tabline.vim-0.0.1.tar.gz","4":"smart-tabline.vim-0.0.1.tar.gz","src_id":"25443","5":"25443","creation_date":"1500902100","6":"1500902100"}]},"5594":{"script_id":"5594","0":"5594","script_name":"subnetquicksearch.vim","1":"subnetquicksearch.vim","script_type":"utility","2":"utility","summary":"Searches for a highlighted subnet","3":"Searches for a highlighted subnet","description":"This script requires python 2.7 and the ipaddress module (pip install ipaddress).  Will build a regular expression to search for all ip addresses that fall within a subnet highlighted in text with the form X.X.X.X\/X (an IPv4 CIDR format) after highlighting the text and pressing F10 (F10 is selected arbitrarily - just change that part of the script to use a different key).","4":"This script requires python 2.7 and the ipaddress module (pip install ipaddress).  Will build a regular expression to search for all ip addresses that fall within a subnet highlighted in text with the form X.X.X.X\/X (an IPv4 CIDR format) after highlighting the text and pressing F10 (F10 is selected arbitrarily - just change that part of the script to use a different key).","install_details":"Make sure your vim can run python 2.7, install the ipaddress module (pip install ipaddress), then copy to your vim plugin directory","5":"Make sure your vim can run python 2.7, install the ipaddress module (pip install ipaddress), then copy to your vim plugin directory","first_name":"John","6":"John","last_name":"Biederstedt","7":"Biederstedt","releases":[{"0":"5594","vim_version":"7.4","1":"7.4","script_version":".01","2":".01","version_comment":"Initial upload","3":"Initial upload","package":"subnetquicksearch.vim","4":"subnetquicksearch.vim","src_id":"25433","5":"25433","creation_date":"1500616308","6":"1500616308"}]},"5593":{"script_id":"5593","0":"5593","script_name":"VimRpc","1":"VimRpc","script_type":"utility","2":"utility","summary":"VimRpc is a Vim plugin that helps you embed vim in your programs","3":"VimRpc is a Vim plugin that helps you embed vim in your programs","description":"VimRpc is a vim plugin that brings scripting to Vim,\r\nwith VimRpc you can run vim as a \"REMOTE PROCEDURE CALL DAEMON\" and the connects to it as a client from any language of your choice. ex \"python\", \"perl\" etc\r\nVimRpc also comes bundled with 20+ API Functions that to make embedding vim in your programs much easier.\r\nVimRpc currently Supports 2 RPC PROTOCOLS \"JSON\" & \"XML\", you can change to whichever you want to.\r\n VimRpc Development happens here \"http:\/\/github.com\/da-emzy\/VimRpc.\r\nIssues should be forwarded to \"http:\/\/github.com\/da-emzy\/VimRpc\/issues .\r\nAnd a lot more............\r\nRun `:help VimRpc.txt` to get started on using VimRpc","4":"VimRpc is a vim plugin that brings scripting to Vim,\r\nwith VimRpc you can run vim as a \"REMOTE PROCEDURE CALL DAEMON\" and the connects to it as a client from any language of your choice. ex \"python\", \"perl\" etc\r\nVimRpc also comes bundled with 20+ API Functions that to make embedding vim in your programs much easier.\r\nVimRpc currently Supports 2 RPC PROTOCOLS \"JSON\" & \"XML\", you can change to whichever you want to.\r\n VimRpc Development happens here \"http:\/\/github.com\/da-emzy\/VimRpc.\r\nIssues should be forwarded to \"http:\/\/github.com\/da-emzy\/VimRpc\/issues .\r\nAnd a lot more............\r\nRun `:help VimRpc.txt` to get started on using VimRpc","install_details":"download VimRpc.zip.\r\nunzip the Zip archive\r\nchange directory to the unzipped archive\r\nthen run these command:\r\n\"\"\"\r\nmkdir -p ~\/.vim\r\ncp -r * ~\/.vim\r\n\"\"\"\r\nAND THAT IS THAT!!!!\r\n","5":"download VimRpc.zip.\r\nunzip the Zip archive\r\nchange directory to the unzipped archive\r\nthen run these command:\r\n\"\"\"\r\nmkdir -p ~\/.vim\r\ncp -r * ~\/.vim\r\n\"\"\"\r\nAND THAT IS THAT!!!!\r\n","first_name":"da","6":"da","last_name":"emzy","7":"emzy","releases":[{"0":"5593","vim_version":"7.4","1":"7.4","script_version":"1.01","2":"1.01","version_comment":"Fixed Bug in documentation","3":"Fixed Bug in documentation","package":"VimRpc.zip","4":"VimRpc.zip","src_id":"25426","5":"25426","creation_date":"1500286014","6":"1500286014"}]},"5592":{"script_id":"5592","0":"5592","script_name":"mintycode","1":"mintycode","script_type":"color scheme","2":"color scheme","summary":"Dark color scheme focusing on cool colors","3":"Dark color scheme focusing on cool colors","description":"A dark color scheme focusing on cool colors, with emphasis on purples, dark blues, and minty colors (where 256 colors are available). \r\n\r\nCertain language-specific colors help you know when you are coding correctly. ","4":"A dark color scheme focusing on cool colors, with emphasis on purples, dark blues, and minty colors (where 256 colors are available). \r\n\r\nCertain language-specific colors help you know when you are coding correctly. ","install_details":"Unzip folder in your ~\/.vim\/bundle directory (or make one, if it does not exist). \r\nThen, in vim, type \\\":colo minty\\\". ","5":"Unzip folder in your ~\/.vim\/bundle directory (or make one, if it does not exist). \r\nThen, in vim, type \\\":colo minty\\\". ","first_name":"Bryce","6":"Bryce","last_name":"Aidukaitis","7":"Aidukaitis","releases":[{"0":"5592","vim_version":"7.0","1":"7.0","script_version":"1.01","2":"1.01","version_comment":"Color scheme now correctly identifies as \"minty\". Colors are no longer affected by previous color scheme.","3":"Color scheme now correctly identifies as \"minty\". Colors are no longer affected by previous color scheme.","package":"mintycode.tar.gz","4":"mintycode.tar.gz","src_id":"25412","5":"25412","creation_date":"1500075115","6":"1500075115"},{"0":"5592","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"mintycode.tar.gz","4":"mintycode.tar.gz","src_id":"25411","5":"25411","creation_date":"1500069929","6":"1500069929"}]},"5591":{"script_id":"5591","0":"5591","script_name":"dirconf.vim","1":"dirconf.vim","script_type":"utility","2":"utility","summary":"project specific vim config and notes","3":"project specific vim config and notes","description":"This vim plugin is for maintaining project specific configuration and keeping\r\nnotes associated with the project.  The configuration and notes are kept\r\noutside of the project source directory.\r\n\r\nI created this plugin because I wanted to change settings between different\r\nprojects I am working on that use different plugin settings and be able to\r\nwork on these projects in the same vim instance.\r\n\r\nFor example:\r\n\r\nOne project uses `eslint` with a specific configuration, while another project\r\nuses `eslint` with a different configuration.\r\n\r\nOne of these projects uses `tern` for JS completion, where another uses\r\n`vim-flow` completion.\r\n\r\nWith this plugin I am able to work on these projects within the same vim\r\ninstance using something like the following context files:\r\n\r\nOne for running `eslint` and `flow`:\r\n\r\n  let g:javascript_plugin_flow = 1\r\n\r\n  \" Source the file to define flowcomplete#Complete\r\n  if ! exists('*flowcomplete#Complete')\r\n    let g:tern_disable = 1\r\n    let g:flow#flowpath = a:dir . '\/node_modules\/.bin\/flow'\r\n    let g:neomake_javascript_enabled_makers = ['eslint']\r\n    let g:neomake_javascript_eslint_args = ' --config ' . $HOME . '\/.eslintrc-react'\r\n    source ~\/.vim\/bundle\/vim-flow\/autoload\/flowcomplete.vim  \r\n  endif\r\n\r\n  set omnifunc=flowcomplete#Complete\r\n\r\nAnother dirconf context file for running `eslint` and `ternjs` for completion:\r\n\r\n  let g:neomake_javascript_enabled_makers = ['eslint']\r\n  let g:neomake_javascript_eslint_exe = a:dir . '\/node_modules\/.bin\/eslint'\r\n  let g:neomake_javascript_eslint_args = ' --config ' . $HOME . '\/.eslintrc-backend'\r\n  let g:tern_show_argument_hints = 1\r\n  let g:tern_show_signature_in_pum = 1\r\n\r\n\r\nPlease send comments and bugreports here: https:\/\/github.com\/aklt\/dirconf.vim","4":"This vim plugin is for maintaining project specific configuration and keeping\r\nnotes associated with the project.  The configuration and notes are kept\r\noutside of the project source directory.\r\n\r\nI created this plugin because I wanted to change settings between different\r\nprojects I am working on that use different plugin settings and be able to\r\nwork on these projects in the same vim instance.\r\n\r\nFor example:\r\n\r\nOne project uses `eslint` with a specific configuration, while another project\r\nuses `eslint` with a different configuration.\r\n\r\nOne of these projects uses `tern` for JS completion, where another uses\r\n`vim-flow` completion.\r\n\r\nWith this plugin I am able to work on these projects within the same vim\r\ninstance using something like the following context files:\r\n\r\nOne for running `eslint` and `flow`:\r\n\r\n  let g:javascript_plugin_flow = 1\r\n\r\n  \" Source the file to define flowcomplete#Complete\r\n  if ! exists('*flowcomplete#Complete')\r\n    let g:tern_disable = 1\r\n    let g:flow#flowpath = a:dir . '\/node_modules\/.bin\/flow'\r\n    let g:neomake_javascript_enabled_makers = ['eslint']\r\n    let g:neomake_javascript_eslint_args = ' --config ' . $HOME . '\/.eslintrc-react'\r\n    source ~\/.vim\/bundle\/vim-flow\/autoload\/flowcomplete.vim  \r\n  endif\r\n\r\n  set omnifunc=flowcomplete#Complete\r\n\r\nAnother dirconf context file for running `eslint` and `ternjs` for completion:\r\n\r\n  let g:neomake_javascript_enabled_makers = ['eslint']\r\n  let g:neomake_javascript_eslint_exe = a:dir . '\/node_modules\/.bin\/eslint'\r\n  let g:neomake_javascript_eslint_args = ' --config ' . $HOME . '\/.eslintrc-backend'\r\n  let g:tern_show_argument_hints = 1\r\n  let g:tern_show_signature_in_pum = 1\r\n\r\n\r\nPlease send comments and bugreports here: https:\/\/github.com\/aklt\/dirconf.vim","install_details":"Unzip in your vim folder or use your favourite plugin manager","5":"Unzip in your vim folder or use your favourite plugin manager","first_name":"Anders","6":"Anders","last_name":"Th\u00c3\u00b8gersen","7":"Th\u00c3\u00b8gersen","releases":[{"0":"5591","vim_version":"7.4","1":"7.4","script_version":"0.3.0","2":"0.3.0","version_comment":"Initial upload","3":"Initial upload","package":"dirconf.vim.zip","4":"dirconf.vim.zip","src_id":"25403","5":"25403","creation_date":"1499986891","6":"1499986891"}]},"5590":{"script_id":"5590","0":"5590","script_name":"VimCalc3","1":"VimCalc3","script_type":"utility","2":"utility","summary":"Plugin that provides a convenient interactive calculator inside a Vim buffer","3":"Plugin that provides a convenient interactive calculator inside a Vim buffer","description":"This is port of vimscript http:\/\/www.vim.org\/scripts\/script.php?script_id=3329 to python 3.\r\n\r\nSome of the Vims out there have only +python3, hence this port (of very useful plugin).\r\n\r\nThe main development is done at https:\/\/github.com\/fedorenchik\/VimCalc3\r\n\r\nVimCalc provides a convenient way to access a powerful interactive calculator whilst inside a Vim session. Quickly rattle off a few sums to test an idea. Perform complex calculations using built-in functions to validate answers. Quickly and simply convert from octal to hex to decimal and back again. Setup a bunch of variables to be used in a complex expression. Change variables easily and then simply re-evaluate the expression. Whatever you may need a calculator for, VimCalc is up to the task.\r\n\r\nNot only can VimCalc calculate but it uses Vim for input and editing. Quickly and easily perform edits on previous calculations using the power of Vim and then re-evaluate them by simply hitting return. Once you've got the answers yank them into several registers and paste with ease into other buffers. All whilst never leaving your Vim editing session!\r\n\r\nSee VimCalc's homepage for screenshots: http:\/\/fedorenchik.com\/vim\/vimcalc3\/\r\n\r\nHere are some example expressions run in a VimCalc session:\r\n\r\n> 5+4\r\nans = 9.0\r\n> let x = 4\r\nx = 4.0\r\n> 9 * sqrt(4)\r\nans = 18.0\r\n> 9**2 - (sqrt(4)+2)\r\nans = 77.0\r\n> 0xff + 2\r\nans = 257.0\r\n\r\nHere is an example of calculating the roots of a quadratic equation:\r\n\r\n> let a = 2\r\na = 2.0\r\n> let b = -1\r\nb = -1.0\r\n> let c = -6\r\nc = -6.0\r\n> ((b*-1) + sqrt(b**2 - 4*a*c))\/(2*a)\r\nans = 2.0\r\n> ((b*-1) - sqrt(b**2 - 4*a*c))\/(2*a)\r\nans = -1.5","4":"This is port of vimscript http:\/\/www.vim.org\/scripts\/script.php?script_id=3329 to python 3.\r\n\r\nSome of the Vims out there have only +python3, hence this port (of very useful plugin).\r\n\r\nThe main development is done at https:\/\/github.com\/fedorenchik\/VimCalc3\r\n\r\nVimCalc provides a convenient way to access a powerful interactive calculator whilst inside a Vim session. Quickly rattle off a few sums to test an idea. Perform complex calculations using built-in functions to validate answers. Quickly and simply convert from octal to hex to decimal and back again. Setup a bunch of variables to be used in a complex expression. Change variables easily and then simply re-evaluate the expression. Whatever you may need a calculator for, VimCalc is up to the task.\r\n\r\nNot only can VimCalc calculate but it uses Vim for input and editing. Quickly and easily perform edits on previous calculations using the power of Vim and then re-evaluate them by simply hitting return. Once you've got the answers yank them into several registers and paste with ease into other buffers. All whilst never leaving your Vim editing session!\r\n\r\nSee VimCalc's homepage for screenshots: http:\/\/fedorenchik.com\/vim\/vimcalc3\/\r\n\r\nHere are some example expressions run in a VimCalc session:\r\n\r\n> 5+4\r\nans = 9.0\r\n> let x = 4\r\nx = 4.0\r\n> 9 * sqrt(4)\r\nans = 18.0\r\n> 9**2 - (sqrt(4)+2)\r\nans = 77.0\r\n> 0xff + 2\r\nans = 257.0\r\n\r\nHere is an example of calculating the roots of a quadratic equation:\r\n\r\n> let a = 2\r\na = 2.0\r\n> let b = -1\r\nb = -1.0\r\n> let c = -6\r\nc = -6.0\r\n> ((b*-1) + sqrt(b**2 - 4*a*c))\/(2*a)\r\nans = 2.0\r\n> ((b*-1) - sqrt(b**2 - 4*a*c))\/(2*a)\r\nans = -1.5","install_details":"Requirements\r\n\r\nVim 7.0+ with +python3.\r\nPython 3 installed.\r\n\r\nIf you're compiling Vim from source, be sure to use the --enable-python3interp option. Otherwise check your OS's package distro for a version of Vim with Python support. On OS X the best option is MacVim. VimCalc should work on Windows too, you will need to install the correct python dll for the version of Vim you are using. Please see the web for help with this.\r\n\r\nInstallation\r\n\r\nIf you don't have a preferred installation method, I recommend using Vim's packages feature, run:\r\n\r\nmkdir -p ~\/.vim\/pack\/bundle\/start\r\ncd ~\/.vim\/pack\/bundle\/start\r\ngit clone https:\/\/github.com\/fedorenchik\/VimCalc3.git\r\n\r\nThen update your help tags file to enable VimCalc3 help. See :help add-local-help in Vim for details.\r\n\r\nIf you like and find VimCalc useful be sure to vote for this script! ","5":"Requirements\r\n\r\nVim 7.0+ with +python3.\r\nPython 3 installed.\r\n\r\nIf you're compiling Vim from source, be sure to use the --enable-python3interp option. Otherwise check your OS's package distro for a version of Vim with Python support. On OS X the best option is MacVim. VimCalc should work on Windows too, you will need to install the correct python dll for the version of Vim you are using. Please see the web for help with this.\r\n\r\nInstallation\r\n\r\nIf you don't have a preferred installation method, I recommend using Vim's packages feature, run:\r\n\r\nmkdir -p ~\/.vim\/pack\/bundle\/start\r\ncd ~\/.vim\/pack\/bundle\/start\r\ngit clone https:\/\/github.com\/fedorenchik\/VimCalc3.git\r\n\r\nThen update your help tags file to enable VimCalc3 help. See :help add-local-help in Vim for details.\r\n\r\nIf you like and find VimCalc useful be sure to vote for this script! ","first_name":"Leonid","6":"Leonid","last_name":"Fedorenchik","7":"Fedorenchik","releases":[{"0":"5590","vim_version":"7.0","1":"7.0","script_version":"3.3","2":"3.3","version_comment":"Add support for binary (:bin, 0b1101, etc.) numbers.","3":"Add support for binary (:bin, 0b1101, etc.) numbers.","package":"VimCalc3-3.3.zip","4":"VimCalc3-3.3.zip","src_id":"25656","5":"25656","creation_date":"1511541585","6":"1511541585"},{"0":"5590","vim_version":"7.0","1":"7.0","script_version":"3.2","2":"3.2","version_comment":"Add autoload support: move most of the functionality to autoload directory.","3":"Add autoload support: move most of the functionality to autoload directory.","package":"VimCalc3-3.2.zip","4":"VimCalc3-3.2.zip","src_id":"25496","5":"25496","creation_date":"1502385762","6":"1502385762"},{"0":"5590","vim_version":"7.0","1":"7.0","script_version":"3.1.1","2":"3.1.1","version_comment":"Bugfix Release. Fixed bugs which led to errors when using VimCalc3 with other plugins (clang_complete, VOoM, etc.).","3":"Bugfix Release. Fixed bugs which led to errors when using VimCalc3 with other plugins (clang_complete, VOoM, etc.).","package":"VimCalc3-3.1.1.zip","4":"VimCalc3-3.1.1.zip","src_id":"25484","5":"25484","creation_date":"1502090751","6":"1502090751"},{"0":"5590","vim_version":"7.0","1":"7.0","script_version":"3.1","2":"3.1","version_comment":"Allow real numbers without leading 0 and with capital E.","3":"Allow real numbers without leading 0 and with capital E.","package":"VimCalc3-3.1.zip","4":"VimCalc3-3.1.zip","src_id":"25413","5":"25413","creation_date":"1500113901","6":"1500113901"},{"0":"5590","vim_version":"7.0","1":"7.0","script_version":"3.0","2":"3.0","version_comment":"Initial upload","3":"Initial upload","package":"VimCalc3-3.0.zip","4":"VimCalc3-3.0.zip","src_id":"25398","5":"25398","creation_date":"1499945226","6":"1499945226"}]},"5589":{"script_id":"5589","0":"5589","script_name":"quickmenu","1":"quickmenu","script_type":"utility","2":"utility","summary":"A nice popup menu for vim","3":"A nice popup menu for vim","description":"There are many keymaps defined in my `.vimrc`. Tired to check my `.vimrc` again and again when I forget some, so I made this `quickmenu` plugin which can be fully customized:\r\n\r\n- Well formatted and carefully colored to ensure neat and handy.\r\n- Press `` to popup `quickmenu` on the right, use `j` and `k` to move up and down.\r\n- Press `` or `1` to `9` to select an item.\r\n- `Help` details will display in the cmdline when you are moving around the cursor.\r\n- Items can be filtered by `filetype`, different items for different filetypes.\r\n- Macros in `%{...}` form from `text` and `help` will be evaluated and expanded.\r\n- No longer have to be afraid for forgetting keymaps.\r\n\r\nJust see this GIF demonstration below:\r\n\r\nhttp:\/\/skywind3000.github.io\/word\/images\/menu\/menu-2.gif\r\n\r\nTrying to share my configuration to my friends, I found that they did't have patience to remember all the keymaps in my vimrc, but a quickmenu is quite accaptable for them. Vim is lack of ui components, that's ok for experienced user, but hard for the others, but a quickmenu is easier for them.\r\n\r\nHomepage:\r\nhttps:\/\/github.com\/skywind3000\/quickmenu.vim\r\n\r\nSetup:\r\n\r\n\" clear all the items\r\ncall g:quickmenu#reset()\r\n\r\n\" section 1\r\ncall g:quickmenu#append('# Develop', '')\r\n\r\ncall g:quickmenu#append('item 1.1', 'echo \"1.1 is selected\"', 'select item 1.1')\r\ncall g:quickmenu#append('item 1.2', 'echo \"1.2 is selected\"', 'select item 1.2')\r\ncall g:quickmenu#append('item 1.3', 'echo \"1.3 is selected\"', 'select item 1.3')\r\n\r\n\" section 2\r\n\r\ncall g:quickmenu#append('# Misc', '')\r\n\r\ncall g:quickmenu#append('item 2.1', 'echo \"2.1 is selected\"', 'select item 2.1')\r\ncall g:quickmenu#append('item 2.2', 'echo \"2.2 is selected\"', 'select item 2.2')\r\ncall g:quickmenu#append('item 2.3', 'echo \"2.3 is selected\"', 'select item 2.3')\r\ncall g:quickmenu#append('item 2.4', 'echo \"2.4 is selected\"', 'select item 2.4')\r\n\r\n\r\n\r\n\r\n","4":"There are many keymaps defined in my `.vimrc`. Tired to check my `.vimrc` again and again when I forget some, so I made this `quickmenu` plugin which can be fully customized:\r\n\r\n- Well formatted and carefully colored to ensure neat and handy.\r\n- Press `` to popup `quickmenu` on the right, use `j` and `k` to move up and down.\r\n- Press `` or `1` to `9` to select an item.\r\n- `Help` details will display in the cmdline when you are moving around the cursor.\r\n- Items can be filtered by `filetype`, different items for different filetypes.\r\n- Macros in `%{...}` form from `text` and `help` will be evaluated and expanded.\r\n- No longer have to be afraid for forgetting keymaps.\r\n\r\nJust see this GIF demonstration below:\r\n\r\nhttp:\/\/skywind3000.github.io\/word\/images\/menu\/menu-2.gif\r\n\r\nTrying to share my configuration to my friends, I found that they did't have patience to remember all the keymaps in my vimrc, but a quickmenu is quite accaptable for them. Vim is lack of ui components, that's ok for experienced user, but hard for the others, but a quickmenu is easier for them.\r\n\r\nHomepage:\r\nhttps:\/\/github.com\/skywind3000\/quickmenu.vim\r\n\r\nSetup:\r\n\r\n\" clear all the items\r\ncall g:quickmenu#reset()\r\n\r\n\" section 1\r\ncall g:quickmenu#append('# Develop', '')\r\n\r\ncall g:quickmenu#append('item 1.1', 'echo \"1.1 is selected\"', 'select item 1.1')\r\ncall g:quickmenu#append('item 1.2', 'echo \"1.2 is selected\"', 'select item 1.2')\r\ncall g:quickmenu#append('item 1.3', 'echo \"1.3 is selected\"', 'select item 1.3')\r\n\r\n\" section 2\r\n\r\ncall g:quickmenu#append('# Misc', '')\r\n\r\ncall g:quickmenu#append('item 2.1', 'echo \"2.1 is selected\"', 'select item 2.1')\r\ncall g:quickmenu#append('item 2.2', 'echo \"2.2 is selected\"', 'select item 2.2')\r\ncall g:quickmenu#append('item 2.3', 'echo \"2.3 is selected\"', 'select item 2.3')\r\ncall g:quickmenu#append('item 2.4', 'echo \"2.4 is selected\"', 'select item 2.4')\r\n\r\n\r\n\r\n\r\n","install_details":"Extract the zip to your ~\/.vim\/ and edit your .vimrc:\r\n\r\n\" choose a favorite key to show\/hide quickmenu\r\nnoremap  :call quickmenu#toggle(0)\r\n\r\n\" enable cursorline (L) and cmdline help (H)\r\nlet g:quickmenu_options = \"LH\"\r\n\r\n","5":"Extract the zip to your ~\/.vim\/ and edit your .vimrc:\r\n\r\n\" choose a favorite key to show\/hide quickmenu\r\nnoremap  :call quickmenu#toggle(0)\r\n\r\n\" enable cursorline (L) and cmdline help (H)\r\nlet g:quickmenu_options = \"LH\"\r\n\r\n","first_name":"Wei","6":"Wei","last_name":"Lin","7":"Lin","releases":[{"0":"5589","vim_version":"7.3","1":"7.3","script_version":"1.2.4","2":"1.2.4","version_comment":"supports funcref now.","3":"supports funcref now.","package":"quickmenu-1.2.4.zip","4":"quickmenu-1.2.4.zip","src_id":"25489","5":"25489","creation_date":"1502178448","6":"1502178448"},{"0":"5589","vim_version":"7.4","1":"7.4","script_version":"1.2.3","2":"1.2.3","version_comment":"add `` befor noremap to avoid delay when you press 'c'","3":"add `` befor noremap to avoid delay when you press 'c'","package":"quickmenu-1.2.3.zip","4":"quickmenu-1.2.3.zip","src_id":"25452","5":"25452","creation_date":"1501144632","6":"1501144632"},{"0":"5589","vim_version":"7.3","1":"7.3","script_version":"1.2.2","2":"1.2.2","version_comment":"remember cursor position when quickmenu reopen, clear help text in cmdline after closed.","3":"remember cursor position when quickmenu reopen, clear help text in cmdline after closed.","package":"quickmenu-1.2.2.zip","4":"quickmenu-1.2.2.zip","src_id":"25423","5":"25423","creation_date":"1500274467","6":"1500274467"},{"0":"5589","vim_version":"7.3","1":"7.3","script_version":"1.2.1","2":"1.2.1","version_comment":"use redraw to clear previous help text in the cmdline after quickmenu window closed","3":"use redraw to clear previous help text in the cmdline after quickmenu window closed","package":"quickmenu-1.2.1.zip","4":"quickmenu-1.2.1.zip","src_id":"25419","5":"25419","creation_date":"1500187133","6":"1500187133"},{"0":"5589","vim_version":"7.3","1":"7.3","script_version":"1.2.0","2":"1.2.0","version_comment":"new feature `quickmenu#bottom` to popup on the bottom. ","3":"new feature `quickmenu#bottom` to popup on the bottom. ","package":"quickmenu-1.2.0.zip","4":"quickmenu-1.2.0.zip","src_id":"25416","5":"25416","creation_date":"1500147196","6":"1500147196"},{"0":"5589","vim_version":"7.0","1":"7.0","script_version":"1.1.15","2":"1.1.15","version_comment":"fixed: quickmenu will always popup on the right, no matter `splitright` is set or unset","3":"fixed: quickmenu will always popup on the right, no matter `splitright` is set or unset","package":"quickmenu-1.1.15.zip","4":"quickmenu-1.1.15.zip","src_id":"25408","5":"25408","creation_date":"1500052324","6":"1500052324"},{"0":"5589","vim_version":"7.0","1":"7.0","script_version":"1.1.14","2":"1.1.14","version_comment":"fixed incompatible issue with vim 7.4.2201 and older version.","3":"fixed incompatible issue with vim 7.4.2201 and older version.","package":"quickmenu-1.1.14.zip","4":"quickmenu-1.1.14.zip","src_id":"25407","5":"25407","creation_date":"1500029146","6":"1500029146"},{"0":"5589","vim_version":"7.0","1":"7.0","script_version":"1.1.13","2":"1.1.13","version_comment":"New option to set default left\/right padding size, useful when running vim in a small window.","3":"New option to set default left\/right padding size, useful when running vim in a small window.","package":"quickmenu-1.1.13.zip","4":"quickmenu-1.1.13.zip","src_id":"25401","5":"25401","creation_date":"1499967187","6":"1499967187"},{"0":"5589","vim_version":"7.0","1":"7.0","script_version":"1.1.12","2":"1.1.12","version_comment":"Full version include syntax files of 1.1.12","3":"Full version include syntax files of 1.1.12","package":"quickmenu-1.1.12.zip","4":"quickmenu-1.1.12.zip","src_id":"25396","5":"25396","creation_date":"1499942259","6":"1499942259"}]},"5588":{"script_id":"5588","0":"5588","script_name":"vim-todo-lists","1":"vim-todo-lists","script_type":"utility","2":"utility","summary":"Plugin for TODO lists management","3":"Plugin for TODO lists management","description":"Plugin is automatically applied for files with `.todo` extension.\r\n\r\nUsage\r\n-----\r\n\r\nPlugin is automatically applied for files with `.todo.md` extension.\r\n\r\n##### TODO Items\r\n\r\nThe following example represents TODO items definition by default.\r\n\r\n###### Example\r\n\r\n```\r\n- [ ] Not done\r\n- [X] Done\r\n```\r\n\r\n###### Custom Configuration\r\n\r\nYou can customize the representation of the item by defining the following variables\r\nto your `.vimrc`\r\n\r\n```\r\nlet g:VimTodoListsUndoneItem = '- [X]'\r\nlet g:VimTodoListsDoneItem = '- [V]'\r\n```\r\n\r\n###### Important Item\r\n\r\nImportant item is defined as `undone item string !`.\r\n\r\n```\r\n- [ ] ! Important item\r\n```\r\n\r\n##### Items Hierarchy\r\n\r\nIf one item has lesser indentation than the next one then the first one is meant\r\nto be **parent** and the second to be **child**.\r\n\r\n###### Example\r\n\r\n```\r\n- [ ] Parent\r\n  - [ ] Child1\r\n  - [ ] Child2\r\n```\r\n\r\n###### Rules:\r\n\r\n* Changing state of the parent item changes the state of all children items accordantly\r\n* If all children items are marked done, parent will also be marked as done\r\n* If parent is marked as done and one of the children changes state to not done\r\n  parent will also be marked as not done\r\n\r\n##### Items Highlighting\r\n\r\nItems are highlighted in accordance to the following scheme:\r\n\r\n```\r\n- [ ] ! Important item (Underlined)\r\n- [ ] Normal item (Normal)\r\n- [X] Done item (Comment)\r\n```\r\n\r\n##### Items moving on state change\r\n\r\nBy default item when its status is changed is moved in the list in accordance\r\nto the following rules\r\n\r\n###### Mark item done\r\n\r\nItem marked as done is moved to the end of all done items list.\r\nIf done list doesn't exist, item is placed just after the last not done item.\r\n\r\n*Before*\r\n\r\n```\r\n- [ ] Not Done 1\r\n- [ ] Will be done now\r\n- [ ] Not Done 2\r\n- [X] Done\r\n```\r\n\r\n*After*\r\n\r\n```\r\n- [ ] Not Done 1\r\n- [ ] Not Done 2\r\n- [X] Done\r\n- [X] Will be done now\r\n```\r\n\r\n###### Mark item undone\r\n\r\nUndone item is moved to the end of all not done items list.\r\nIf all items are marked done, the items is moved before the first done item.\r\n\r\n*Before*\r\n\r\n```\r\n- [ ] Not Done 1\r\n- [ ] Not Done 2\r\n- [X] Done\r\n- [X] Will be undone now\r\n```\r\n*After*\r\n\r\n```\r\n- [ ] Not Done 1\r\n- [ ] Not Done 2\r\n- [ ] Will be done now\r\n- [X] Done\r\n```\r\n\r\n###### Interaction with items hierarchy\r\n\r\nThis feature also affect the items in hierarchy in accordance to the rules above.\r\n\r\n###### Disable the items moving\r\n\r\nIf you don't want items to be moved after state change, you may add the following\r\nline into your `.vimrc` file:\r\n\r\n```\r\nlet g:VimTodoListsMoveItems = 0\r\n```\r\n\r\n##### Commands\r\n\r\n* `:VimTodoListsCreateNewItemAbove` - creates a new item in a line above cursor\r\n* `:VimTodoListsCreateNewItemBelow` - creates a new item in a line below cursor\r\n* `:VimTodoListsCreateNewItem`      - creates a new item in current line\r\n* `:VimTodoListsGoToNextItem`       - go to the next item\r\n* `:VimTodoListsGoToPreviousItem`   - go to the previous item\r\n* `:VimTodoListsToggleItem`         - toggles the current item (or selected items in visual mode)\r\n* `:VimTodoListsIncreaseIndent`     - increases the indent of current line\r\n* `:VimTodoListsDecreaseIndent`     - decreases the indent of current line\r\n\r\n##### Default key mappings\r\n\r\n###### Item editing mode\r\n\r\n* `j` - go to next item\r\n* `k` - go to previous item\r\n* `O` - create new item above the cursor\r\n* `o` - create new item below the cursor\r\n* `` - toggle current item\r\n* `` - create new item in `insert mode`\r\n* `` - increases the indent of current (or selected) line(s)\r\n* `` - decreases the indent of current (or selected) line(s)\r\n* `e` - switch to normal editing mode\r\n\r\n###### Normal editing mode\r\n\r\n* `j`, `k`, `o`, `O`, `` - no special behavior\r\n* `` - toggle current item\r\n* `e` - switch to item editing mode\r\n\r\n##### Custom key mappings\r\n\r\nThe `g:VimTodoListsCustomKeyMapper` variable should contain a name of the function\r\nimplementing custom mappings.\r\n\r\n###### Example\r\n\r\n```\r\nlet g:VimTodoListsCustomKeyMapper = 'VimTodoListsCustomMappings'\r\n\r\nfunction! VimTodoListsCustomMappings()\r\n  nnoremap  s :VimTodoListsToggleItem\r\n  nnoremap   :VimTodoListsToggleItem\r\n  noremap  e :silent call VimTodoListsSetItemMode()\r\nendfunction\r\n```\r\n\r\n##### Automatic date insertion\r\n\r\nAutomatic date insertion may be enabled by setting the following in `.vimrc`:\r\n\r\n```\r\nlet g:VimTodoListsDatesEnabled = 1\r\n```\r\n\r\nDate format may be changed by setting the format variable to a valid\r\n`strftime()` string:\r\n\r\n```\r\nlet g:VimTodoListsDatesFormat = \"%a %b, %Y\"\r\n```\r\n\r\nContribution\r\n------------\r\n\r\nSource code and issues are hosted on GitHub:\r\n\r\n    https:\/\/github.com\/aserebryakov\/vim-todo-lists\r\n\r\nIf you are going to make a pull request, you should use `dev` branch for\r\nfunctionality implementation to simplify the merge procedure.\r\n\r\nLicense\r\n-------\r\n\r\n[MIT License](https:\/\/opensource.org\/licenses\/MIT)","4":"Plugin is automatically applied for files with `.todo` extension.\r\n\r\nUsage\r\n-----\r\n\r\nPlugin is automatically applied for files with `.todo.md` extension.\r\n\r\n##### TODO Items\r\n\r\nThe following example represents TODO items definition by default.\r\n\r\n###### Example\r\n\r\n```\r\n- [ ] Not done\r\n- [X] Done\r\n```\r\n\r\n###### Custom Configuration\r\n\r\nYou can customize the representation of the item by defining the following variables\r\nto your `.vimrc`\r\n\r\n```\r\nlet g:VimTodoListsUndoneItem = '- [X]'\r\nlet g:VimTodoListsDoneItem = '- [V]'\r\n```\r\n\r\n###### Important Item\r\n\r\nImportant item is defined as `undone item string !`.\r\n\r\n```\r\n- [ ] ! Important item\r\n```\r\n\r\n##### Items Hierarchy\r\n\r\nIf one item has lesser indentation than the next one then the first one is meant\r\nto be **parent** and the second to be **child**.\r\n\r\n###### Example\r\n\r\n```\r\n- [ ] Parent\r\n  - [ ] Child1\r\n  - [ ] Child2\r\n```\r\n\r\n###### Rules:\r\n\r\n* Changing state of the parent item changes the state of all children items accordantly\r\n* If all children items are marked done, parent will also be marked as done\r\n* If parent is marked as done and one of the children changes state to not done\r\n  parent will also be marked as not done\r\n\r\n##### Items Highlighting\r\n\r\nItems are highlighted in accordance to the following scheme:\r\n\r\n```\r\n- [ ] ! Important item (Underlined)\r\n- [ ] Normal item (Normal)\r\n- [X] Done item (Comment)\r\n```\r\n\r\n##### Items moving on state change\r\n\r\nBy default item when its status is changed is moved in the list in accordance\r\nto the following rules\r\n\r\n###### Mark item done\r\n\r\nItem marked as done is moved to the end of all done items list.\r\nIf done list doesn't exist, item is placed just after the last not done item.\r\n\r\n*Before*\r\n\r\n```\r\n- [ ] Not Done 1\r\n- [ ] Will be done now\r\n- [ ] Not Done 2\r\n- [X] Done\r\n```\r\n\r\n*After*\r\n\r\n```\r\n- [ ] Not Done 1\r\n- [ ] Not Done 2\r\n- [X] Done\r\n- [X] Will be done now\r\n```\r\n\r\n###### Mark item undone\r\n\r\nUndone item is moved to the end of all not done items list.\r\nIf all items are marked done, the items is moved before the first done item.\r\n\r\n*Before*\r\n\r\n```\r\n- [ ] Not Done 1\r\n- [ ] Not Done 2\r\n- [X] Done\r\n- [X] Will be undone now\r\n```\r\n*After*\r\n\r\n```\r\n- [ ] Not Done 1\r\n- [ ] Not Done 2\r\n- [ ] Will be done now\r\n- [X] Done\r\n```\r\n\r\n###### Interaction with items hierarchy\r\n\r\nThis feature also affect the items in hierarchy in accordance to the rules above.\r\n\r\n###### Disable the items moving\r\n\r\nIf you don't want items to be moved after state change, you may add the following\r\nline into your `.vimrc` file:\r\n\r\n```\r\nlet g:VimTodoListsMoveItems = 0\r\n```\r\n\r\n##### Commands\r\n\r\n* `:VimTodoListsCreateNewItemAbove` - creates a new item in a line above cursor\r\n* `:VimTodoListsCreateNewItemBelow` - creates a new item in a line below cursor\r\n* `:VimTodoListsCreateNewItem`      - creates a new item in current line\r\n* `:VimTodoListsGoToNextItem`       - go to the next item\r\n* `:VimTodoListsGoToPreviousItem`   - go to the previous item\r\n* `:VimTodoListsToggleItem`         - toggles the current item (or selected items in visual mode)\r\n* `:VimTodoListsIncreaseIndent`     - increases the indent of current line\r\n* `:VimTodoListsDecreaseIndent`     - decreases the indent of current line\r\n\r\n##### Default key mappings\r\n\r\n###### Item editing mode\r\n\r\n* `j` - go to next item\r\n* `k` - go to previous item\r\n* `O` - create new item above the cursor\r\n* `o` - create new item below the cursor\r\n* `` - toggle current item\r\n* `` - create new item in `insert mode`\r\n* `` - increases the indent of current (or selected) line(s)\r\n* `` - decreases the indent of current (or selected) line(s)\r\n* `e` - switch to normal editing mode\r\n\r\n###### Normal editing mode\r\n\r\n* `j`, `k`, `o`, `O`, `` - no special behavior\r\n* `` - toggle current item\r\n* `e` - switch to item editing mode\r\n\r\n##### Custom key mappings\r\n\r\nThe `g:VimTodoListsCustomKeyMapper` variable should contain a name of the function\r\nimplementing custom mappings.\r\n\r\n###### Example\r\n\r\n```\r\nlet g:VimTodoListsCustomKeyMapper = 'VimTodoListsCustomMappings'\r\n\r\nfunction! VimTodoListsCustomMappings()\r\n  nnoremap  s :VimTodoListsToggleItem\r\n  nnoremap   :VimTodoListsToggleItem\r\n  noremap  e :silent call VimTodoListsSetItemMode()\r\nendfunction\r\n```\r\n\r\n##### Automatic date insertion\r\n\r\nAutomatic date insertion may be enabled by setting the following in `.vimrc`:\r\n\r\n```\r\nlet g:VimTodoListsDatesEnabled = 1\r\n```\r\n\r\nDate format may be changed by setting the format variable to a valid\r\n`strftime()` string:\r\n\r\n```\r\nlet g:VimTodoListsDatesFormat = \"%a %b, %Y\"\r\n```\r\n\r\nContribution\r\n------------\r\n\r\nSource code and issues are hosted on GitHub:\r\n\r\n    https:\/\/github.com\/aserebryakov\/vim-todo-lists\r\n\r\nIf you are going to make a pull request, you should use `dev` branch for\r\nfunctionality implementation to simplify the merge procedure.\r\n\r\nLicense\r\n-------\r\n\r\n[MIT License](https:\/\/opensource.org\/licenses\/MIT)","install_details":"##### Pathogen\r\n\r\n    $ cd ~\/.vim\/bundle\r\n    $ git clone https:\/\/github.com\/aserebryakov\/vim-todo-lists.git\r\n\r\n##### NeoBundle\r\n\r\n    NeoBundle \\'aserebryakov\/vim-todo-lists\\'\r\n\r\n##### Without plugin manager\r\n\r\nClone or download this repository and copy its contents to your `~\/.vim\/`\r\ndirectory.","5":"##### Pathogen\r\n\r\n    $ cd ~\/.vim\/bundle\r\n    $ git clone https:\/\/github.com\/aserebryakov\/vim-todo-lists.git\r\n\r\n##### NeoBundle\r\n\r\n    NeoBundle \\'aserebryakov\/vim-todo-lists\\'\r\n\r\n##### Without plugin manager\r\n\r\nClone or download this repository and copy its contents to your `~\/.vim\/`\r\ndirectory.","first_name":"Alexander","6":"Alexander","last_name":"Serebryakov","7":"Serebryakov","releases":[{"0":"5588","vim_version":"8.0","1":"8.0","script_version":"0.8.0","2":"0.8.0","version_comment":"**Breaking Change**\r\n\r\n* Added option to configure TODO items\r\n* File extension changed to `.todo.md` from `.todo`\r\n* Item indentation level is kept when creating a new one\r\n* Removed migration from older formats\r\n* Added plugin initialization for `todo` filetype\r\n* New item can be created with keypad Enter key\r\n* Makes normal mode keys more consistent","3":"**Breaking Change**\r\n\r\n* Added option to configure TODO items\r\n* File extension changed to `.todo.md` from `.todo`\r\n* Item indentation level is kept when creating a new one\r\n* Removed migration from older formats\r\n* Added plugin initialization for `todo` filetype\r\n* New item can be created with keypad Enter key\r\n* Makes normal mode keys more consistent","package":"vim-todo-lists-0.8.0.zip","4":"vim-todo-lists-0.8.0.zip","src_id":"27218","5":"27218","creation_date":"1593448648","6":"1593448648"},{"0":"5588","vim_version":"8.0","1":"8.0","script_version":"0.7.1","2":"0.7.1","version_comment":"* Syntax highlight is fixed","3":"* Syntax highlight is fixed","package":"vim-todo-lists-0.7.1.zip","4":"vim-todo-lists-0.7.1.zip","src_id":"26420","5":"26420","creation_date":"1552413806","6":"1552413806"},{"0":"5588","vim_version":"8.0","1":"8.0","script_version":"0.7.0","2":"0.7.0","version_comment":"* Added automatic date insertion feature\r\n* Added mappings for fast increasing\/decreasing indent\r\n* Items list are made markdown compatible (old are files updated automatically\r\non load)","3":"* Added automatic date insertion feature\r\n* Added mappings for fast increasing\/decreasing indent\r\n* Items list are made markdown compatible (old are files updated automatically\r\non load)","package":"vim-todo-lists-0.7.0.zip","4":"vim-todo-lists-0.7.0.zip","src_id":"26382","5":"26382","creation_date":"1550174708","6":"1550174708"},{"0":"5588","vim_version":"7.4","1":"7.4","script_version":"0.6.0","2":"0.6.0","version_comment":"* Adds items moving on state change","3":"* Adds items moving on state change","package":"vim-todo-lists-0.6.0.zip","4":"vim-todo-lists-0.6.0.zip","src_id":"25591","5":"25591","creation_date":"1506631515","6":"1506631515"},{"0":"5588","vim_version":"7.4","1":"7.4","script_version":"0.5.1","2":"0.5.1","version_comment":"* Fixed the annoying noise when navigating over items in default mode\r\n* Fixed the cursor position after the item is toggled\r\n","3":"* Fixed the annoying noise when navigating over items in default mode\r\n* Fixed the cursor position after the item is toggled\r\n","package":"vim-todo-lists-0.5.1.zip","4":"vim-todo-lists-0.5.1.zip","src_id":"25551","5":"25551","creation_date":"1504551548","6":"1504551548"},{"0":"5588","vim_version":"7.4","1":"7.4","script_version":"0.5.0","2":"0.5.0","version_comment":"* Added items highlighting","3":"* Added items highlighting","package":"vim-todo-lists-0.5.0.zip","4":"vim-todo-lists-0.5.0.zip","src_id":"25546","5":"25546","creation_date":"1504342004","6":"1504342004"},{"0":"5588","vim_version":"7.4","1":"7.4","script_version":"0.4.0","2":"0.4.0","version_comment":"* Added items hierarchy support","3":"* Added items hierarchy support","package":"vim-todo-lists-0.4.0.zip","4":"vim-todo-lists-0.4.0.zip","src_id":"25534","5":"25534","creation_date":"1503917158","6":"1503917158"},{"0":"5588","vim_version":"7.4","1":"7.4","script_version":"0.3.0","2":"0.3.0","version_comment":"* Added items toggling in visual mode\r\n* Improves work with indentations of list items\r\n* Fixed the error when trying to navigate the buffer that doesn't contain items\r\n","3":"* Added items toggling in visual mode\r\n* Improves work with indentations of list items\r\n* Fixed the error when trying to navigate the buffer that doesn't contain items\r\n","package":"vim-todo-lists-0.3.0.zip","4":"vim-todo-lists-0.3.0.zip","src_id":"25521","5":"25521","creation_date":"1503260369","6":"1503260369"},{"0":"5588","vim_version":"7.4","1":"7.4","script_version":"0.2.0","2":"0.2.0","version_comment":"* Adds an option to configure custom key mappings","3":"* Adds an option to configure custom key mappings","package":"vim-todo-lists-0.2.0.zip","4":"vim-todo-lists-0.2.0.zip","src_id":"25437","5":"25437","creation_date":"1500818930","6":"1500818930"},{"0":"5588","vim_version":"7.4","1":"7.4","script_version":"0.1.1","2":"0.1.1","version_comment":"Fixes broken compatibility with the 'filestyle' plugin","3":"Fixes broken compatibility with the 'filestyle' plugin","package":"vim-todo-lists-0.1.1.zip","4":"vim-todo-lists-0.1.1.zip","src_id":"25429","5":"25429","creation_date":"1500445797","6":"1500445797"},{"0":"5588","vim_version":"7.4","1":"7.4","script_version":"0.1.0","2":"0.1.0","version_comment":"Initial upload","3":"Initial upload","package":"vim-todo-lists-0.1.0.zip","4":"vim-todo-lists-0.1.0.zip","src_id":"25377","5":"25377","creation_date":"1499241490","6":"1499241490"}]},"5587":{"script_id":"5587","0":"5587","script_name":"vim-game-code-break","1":"vim-game-code-break","script_type":"game","2":"game","summary":"block-breaking game","3":"block-breaking game","description":"block-breaking game in vim\r\n\r\n\r\n==============================================================================\r\nHow to start\r\n\r\n1. open your code or text file on Vim\r\n2. :VimGameCodeBreak\r\n3. enjoy block breaking\r\n\r\n==============================================================================\r\nHow to play \r\n\r\n* h : ←\r\n* l : →\r\n* space : new ball\r\n* ` : cheat key\r\n* ] : enable god mode\r\n* [ : disable god mode\r\n* q : end game\r\n* Q : quit & close game\r\n\r\n==============================================================================\r\nSetting\r\n\r\nIf you want to play with more than three balls, you can modify the following:\r\n\r\n\" .vimrc\r\nlet g:vim_game_code_break_item_limit = 4    \" default value is 2\r\n\r\nWARNING: Too many balls can slow down the game or cause bugs. \r\nI recommend the default value : 2 \r\nIf the game speed is too slow, try :syntax off before starting the game.\r\n\r\ngithub repository : https:\/\/github.com\/johngrib\/vim-game-code-break","4":"block-breaking game in vim\r\n\r\n\r\n==============================================================================\r\nHow to start\r\n\r\n1. open your code or text file on Vim\r\n2. :VimGameCodeBreak\r\n3. enjoy block breaking\r\n\r\n==============================================================================\r\nHow to play \r\n\r\n* h : ←\r\n* l : →\r\n* space : new ball\r\n* ` : cheat key\r\n* ] : enable god mode\r\n* [ : disable god mode\r\n* q : end game\r\n* Q : quit & close game\r\n\r\n==============================================================================\r\nSetting\r\n\r\nIf you want to play with more than three balls, you can modify the following:\r\n\r\n\" .vimrc\r\nlet g:vim_game_code_break_item_limit = 4    \" default value is 2\r\n\r\nWARNING: Too many balls can slow down the game or cause bugs. \r\nI recommend the default value : 2 \r\nIf the game speed is too slow, try :syntax off before starting the game.\r\n\r\ngithub repository : https:\/\/github.com\/johngrib\/vim-game-code-break","install_details":"Copy all files or plugin directory into your Vim runtimepath, like $HOME\/.vim or $VIM\/vimfiles.","5":"Copy all files or plugin directory into your Vim runtimepath, like $HOME\/.vim or $VIM\/vimfiles.","first_name":"JohnGrib","6":"JohnGrib","last_name":"Lee","7":"Lee","releases":[{"0":"5587","vim_version":"8.0","1":"8.0","script_version":"1.3.0","2":"1.3.0","version_comment":"If you want to play with more than three balls, you can modify the following:\r\n\r\n\" .vimrc\r\nlet g:vim_game_code_break_item_limit = 4    \" default value is 2\r\n\r\nWARNING: Too many balls can slow down the game or cause bugs. \r\nI recommend the default value : 2 \r\nIf the game speed is too slow, try :syntax off before starting the game.","3":"If you want to play with more than three balls, you can modify the following:\r\n\r\n\" .vimrc\r\nlet g:vim_game_code_break_item_limit = 4    \" default value is 2\r\n\r\nWARNING: Too many balls can slow down the game or cause bugs. \r\nI recommend the default value : 2 \r\nIf the game speed is too slow, try :syntax off before starting the game.","package":"vim-game-code-break-1.3.0.zip","4":"vim-game-code-break-1.3.0.zip","src_id":"25453","5":"25453","creation_date":"1501146276","6":"1501146276"},{"0":"5587","vim_version":"8.0","1":"8.0","script_version":"1.2.0","2":"1.2.0","version_comment":"add 'Q' : quit and close game","3":"add 'Q' : quit and close game","package":"vim-game-code-break-1.2.0.zip","4":"vim-game-code-break-1.2.0.zip","src_id":"25418","5":"25418","creation_date":"1500176006","6":"1500176006"},{"0":"5587","vim_version":"7.0","1":"7.0","script_version":"1.1.7","2":"1.1.7","version_comment":"[bugfix] Grouping autocmds to hide cursors.","3":"[bugfix] Grouping autocmds to hide cursors.","package":"vim-game-code-break-1.1.7.zip","4":"vim-game-code-break-1.1.7.zip","src_id":"25384","5":"25384","creation_date":"1499508917","6":"1499508917"},{"0":"5587","vim_version":"8.0","1":"8.0","script_version":"1.1.6","2":"1.1.6","version_comment":"minor bug fixed","3":"minor bug fixed","package":"vim-game-code-break-1.1.6.zip","4":"vim-game-code-break-1.1.6.zip","src_id":"25380","5":"25380","creation_date":"1499342293","6":"1499342293"},{"0":"5587","vim_version":"8.0","1":"8.0","script_version":"1.1.2","2":"1.1.2","version_comment":"fold bug fixed","3":"fold bug fixed","package":"vim-game-code-break-1.1.2.zip","4":"vim-game-code-break-1.1.2.zip","src_id":"25375","5":"25375","creation_date":"1499161435","6":"1499161435"},{"0":"5587","vim_version":"8.0","1":"8.0","script_version":"1.1.1","2":"1.1.1","version_comment":"minor bug fix","3":"minor bug fix","package":"vim-game-code-break-1.1.1.zip","4":"vim-game-code-break-1.1.1.zip","src_id":"25371","5":"25371","creation_date":"1499045909","6":"1499045909"},{"0":"5587","vim_version":"8.0","1":"8.0","script_version":"1.0.0","2":"1.0.0","version_comment":"Initial upload","3":"Initial upload","package":"vim-game-code-break-1.0.0.zip","4":"vim-game-code-break-1.0.0.zip","src_id":"25369","5":"25369","creation_date":"1499043582","6":"1499043582"}]},"5586":{"script_id":"5586","0":"5586","script_name":"factorus","1":"factorus","script_type":"utility","2":"utility","summary":"Vim plugin for automated refactoring","3":"Vim plugin for automated refactoring","description":"Git repo:  https:\/\/github.com\/apalmer1377\/factorus.git\r\n\r\nFactorus is a Vim plugin for automated refactoring. It provides many of the refactoring features found in IDEs like Eclipse or IntelliJ, without sacrificing the lightness of Vim.\r\n\r\nCurrently, Factorus supports automated versions of the following refactoring tools for the following languages:\r\n\r\nAdd Parameter--Java, Python, C, C++\r\nEncapsulate Variable--Java\r\nExtract Method (automated)--Java, Python, C, C++\r\nExtract Method (manual)--Java, Python, C, C++\r\nRename Argument--Java, Python, C, C++\r\nRename Class--Java, Python\r\nRename Method--Java, Python, C, C++\r\nRename Field--Java, C, C++\r\nRename Type--C, C++\r\nRename Macro--C, C++\r\n\r\nNOTE: C++ functionality is limited, and may not work with more complex code bases.\r\n\r\nFactorus also has commands for reverting changes and rebuilding projects, for stability and sanity testing.","4":"Git repo:  https:\/\/github.com\/apalmer1377\/factorus.git\r\n\r\nFactorus is a Vim plugin for automated refactoring. It provides many of the refactoring features found in IDEs like Eclipse or IntelliJ, without sacrificing the lightness of Vim.\r\n\r\nCurrently, Factorus supports automated versions of the following refactoring tools for the following languages:\r\n\r\nAdd Parameter--Java, Python, C, C++\r\nEncapsulate Variable--Java\r\nExtract Method (automated)--Java, Python, C, C++\r\nExtract Method (manual)--Java, Python, C, C++\r\nRename Argument--Java, Python, C, C++\r\nRename Class--Java, Python\r\nRename Method--Java, Python, C, C++\r\nRename Field--Java, C, C++\r\nRename Type--C, C++\r\nRename Macro--C, C++\r\n\r\nNOTE: C++ functionality is limited, and may not work with more complex code bases.\r\n\r\nFactorus also has commands for reverting changes and rebuilding projects, for stability and sanity testing.","install_details":"To install Factorus, you can:\r\n\r\n- Use a plugin manager like pathogen or vim-plug, \r\n- Clone the git repository into your \\'runtimepath\\',  or\r\n- Download the tar file and extract it into a directory in your \\'runtimepath\\'.","5":"To install Factorus, you can:\r\n\r\n- Use a plugin manager like pathogen or vim-plug, \r\n- Clone the git repository into your \\'runtimepath\\',  or\r\n- Download the tar file and extract it into a directory in your \\'runtimepath\\'.","first_name":"Austin","6":"Austin","last_name":"Palmer","7":"Palmer","releases":[{"0":"5586","vim_version":"7.0","1":"7.0","script_version":"2.0","2":"2.0","version_comment":"Limited C++ functionality has been added; it works the exact same as the C functionality, so it can fail with more complex C++ code. Improvements were also made to extractMethod across the board.","3":"Limited C++ functionality has been added; it works the exact same as the C functionality, so it can fail with more complex C++ code. Improvements were also made to extractMethod across the board.","package":"factorus.tar","4":"factorus.tar","src_id":"26755","5":"26755","creation_date":"1568856929","6":"1568856929"},{"0":"5586","vim_version":"7.0","1":"7.0","script_version":"1.984375","2":"1.984375","version_comment":"GENERAL:\r\n\r\nBugs\r\n----\r\n- strange \"find\" error occasionally with large codebases or frequent use of system('find')\r\n- A lot of issues with extractMethod (frequently extracts invalid code snippets, lines from mismatched blocks, etc.)\r\n\r\nTasks\r\n-----\r\n- Manual extraction (methods, types, etc.)\r\n- Add default argument to function with added parameter\r\n- Add examples to README (prelim 2017-07-26)\r\n- Improve FRebuild output\r\n- look in project root directory for build file before searching (DONE 2017-07-27)\r\n\r\nJAVA:\r\n\r\nBugs\r\n----\r\n- getSubClasses sometimes causes unwanted tabs to stay open, and wanted tabs to close\r\n- getSubClasses not always getting correct class (nested class implements superclasses, but gets marked as outer level instead of inner level)\r\n\r\nTasks\r\n-----\r\n- Add optional 'name' parameter for FEncapsulate\r\n\r\nC:\r\n\r\nBugs\r\n----\r\n- Typedefs not noticed in renameField\r\n- Structs defined within structs not properly identified in renameField\r\n- Arrays of structs not identified in renameField\r\n- Method declarations without implementation not noticed as tags\r\n- Struct definition with no name shouldn't be noticed as a tag \r\n- renameType doesn't search all header files (header files don't need to include base file)\r\n- rollbackRename sometimes throws 'unable to open swap file' error\r\n- rename needs to update include files in case of static\r\n","3":"GENERAL:\r\n\r\nBugs\r\n----\r\n- strange \"find\" error occasionally with large codebases or frequent use of system('find')\r\n- A lot of issues with extractMethod (frequently extracts invalid code snippets, lines from mismatched blocks, etc.)\r\n\r\nTasks\r\n-----\r\n- Manual extraction (methods, types, etc.)\r\n- Add default argument to function with added parameter\r\n- Add examples to README (prelim 2017-07-26)\r\n- Improve FRebuild output\r\n- look in project root directory for build file before searching (DONE 2017-07-27)\r\n\r\nJAVA:\r\n\r\nBugs\r\n----\r\n- getSubClasses sometimes causes unwanted tabs to stay open, and wanted tabs to close\r\n- getSubClasses not always getting correct class (nested class implements superclasses, but gets marked as outer level instead of inner level)\r\n\r\nTasks\r\n-----\r\n- Add optional 'name' parameter for FEncapsulate\r\n\r\nC:\r\n\r\nBugs\r\n----\r\n- Typedefs not noticed in renameField\r\n- Structs defined within structs not properly identified in renameField\r\n- Arrays of structs not identified in renameField\r\n- Method declarations without implementation not noticed as tags\r\n- Struct definition with no name shouldn't be noticed as a tag \r\n- renameType doesn't search all header files (header files don't need to include base file)\r\n- rollbackRename sometimes throws 'unable to open swap file' error\r\n- rename needs to update include files in case of static\r\n","package":"factorus.tar","4":"factorus.tar","src_id":"25461","5":"25461","creation_date":"1501513833","6":"1501513833"},{"0":"5586","vim_version":"7.0","1":"7.0","script_version":"1.96875","2":"1.96875","version_comment":"C SUPPORT--RELEASE 1.96875\r\n\r\n=======\r\nGENERAL\r\n=======\r\n\r\nTasks\r\n-----\r\n- Added support for C programming language (addParam, renameArg, renameType, renameMethod, extractMethod, renameMacro, renameField)\r\n\r\nBugs\r\n----\r\n- Rollback for renameClass doesn't work properly (FIXED 2017-07-17)\r\n- updateQuickFix breaks if only one file is read (FIXED 2017-07-17)\r\n\r\n====\r\nJAVA\r\n====\r\n\r\nBugs\r\n----\r\n- single-line, no-bracket for and while loops screw with getAllBlocks (FIXED 2017-07-17 for while, for is tricker)\r\n\r\nTasks\r\n-----\r\n- add ability to rename enum field (i.e., if you have enum DayOfWeek, rename Monday to MONDAY) (DONE 2017-07-17)\r\n","3":"C SUPPORT--RELEASE 1.96875\r\n\r\n=======\r\nGENERAL\r\n=======\r\n\r\nTasks\r\n-----\r\n- Added support for C programming language (addParam, renameArg, renameType, renameMethod, extractMethod, renameMacro, renameField)\r\n\r\nBugs\r\n----\r\n- Rollback for renameClass doesn't work properly (FIXED 2017-07-17)\r\n- updateQuickFix breaks if only one file is read (FIXED 2017-07-17)\r\n\r\n====\r\nJAVA\r\n====\r\n\r\nBugs\r\n----\r\n- single-line, no-bracket for and while loops screw with getAllBlocks (FIXED 2017-07-17 for while, for is tricker)\r\n\r\nTasks\r\n-----\r\n- add ability to rename enum field (i.e., if you have enum DayOfWeek, rename Monday to MONDAY) (DONE 2017-07-17)\r\n","package":"factorus.tar","4":"factorus.tar","src_id":"25444","5":"25444","creation_date":"1500908467","6":"1500908467"},{"0":"5586","vim_version":"7.0","1":"7.0","script_version":"1.9375","2":"1.9375","version_comment":"=======\r\nGENERAL\r\n=======\r\n\r\nBug Fixes\r\n---------\r\n- FRollback doesn't work properly if quickfix file gets opened (FIXED 07-11-2017)\r\n\r\nNew Features\/Improvements\r\n-------------------------\r\n- Rebuild command to validate code changes (ant\/gradle\/make\/maven builds)\r\n- Make all methods atomic--if an error is thrown or the function is interrupted, roll back the changes\r\n- Provide list of all files\/ all changes made after a rename\r\n- Provide list of all changes NOT made after a rename\r\n- Allow both changes and unchanges to be seen (I know that isn't a word)\r\n\r\n====\r\nJAVA\r\n====\r\n\r\nBug Fixes\r\n---------\r\n- When breaking up lines in extractMethod, function hangs when line length == g:factorus_line_length\r\n- When other declarations were before return declaration, extractMethod incorrectly added declaration into conditional block\r\n- End message doesn't display when running FRollback from other tab\r\n- Multiple declarations on the same line (int i,j) don't get noticed\r\n- When constructed type contains question mark (Foo), declarations don't get noticed\r\n- extractMethod still sometimes not noticing conditionals\r\n- When subclass declaration extends multiple lines, subclass doesn't get noticed\r\n- Classes with the same name in the same package should be considered the same entity\r\n\r\nNew Features\/Improvements\r\n-------------------------\r\n- Speed up renameMethod (again)\r\n\r\n======\r\nPYTHON\r\n======\r\n\r\nBug Fixes\r\n---------\r\n- Some changes can't be seen in rename, and so are overwritten\r\n\r\nNew Features\/Improvements\r\n-------------------------\r\n- Rollback function--when things don't go as expected, provide a rollback to undo the previous action\r\n- extractMethod function\r\n","3":"=======\r\nGENERAL\r\n=======\r\n\r\nBug Fixes\r\n---------\r\n- FRollback doesn't work properly if quickfix file gets opened (FIXED 07-11-2017)\r\n\r\nNew Features\/Improvements\r\n-------------------------\r\n- Rebuild command to validate code changes (ant\/gradle\/make\/maven builds)\r\n- Make all methods atomic--if an error is thrown or the function is interrupted, roll back the changes\r\n- Provide list of all files\/ all changes made after a rename\r\n- Provide list of all changes NOT made after a rename\r\n- Allow both changes and unchanges to be seen (I know that isn't a word)\r\n\r\n====\r\nJAVA\r\n====\r\n\r\nBug Fixes\r\n---------\r\n- When breaking up lines in extractMethod, function hangs when line length == g:factorus_line_length\r\n- When other declarations were before return declaration, extractMethod incorrectly added declaration into conditional block\r\n- End message doesn't display when running FRollback from other tab\r\n- Multiple declarations on the same line (int i,j) don't get noticed\r\n- When constructed type contains question mark (Foo), declarations don't get noticed\r\n- extractMethod still sometimes not noticing conditionals\r\n- When subclass declaration extends multiple lines, subclass doesn't get noticed\r\n- Classes with the same name in the same package should be considered the same entity\r\n\r\nNew Features\/Improvements\r\n-------------------------\r\n- Speed up renameMethod (again)\r\n\r\n======\r\nPYTHON\r\n======\r\n\r\nBug Fixes\r\n---------\r\n- Some changes can't be seen in rename, and so are overwritten\r\n\r\nNew Features\/Improvements\r\n-------------------------\r\n- Rollback function--when things don't go as expected, provide a rollback to undo the previous action\r\n- extractMethod function\r\n","package":"factorus.tar","4":"factorus.tar","src_id":"25400","5":"25400","creation_date":"1499957456","6":"1499957456"},{"0":"5586","vim_version":"7.0","1":"7.0","script_version":"1.875","2":"1.875","version_comment":"JAVA BUG FIXES: \r\n- When two references to a method occur on the same line, only the first gets updated (FIXED)\r\n- Methods of superclasses don't get checked in updateOutliers (FIXED)\r\n- Methods returning Collections or other structures(Trees, Lists, Sets) don't get updated (CLOSED 07-07-2017)\r\n- getSuperClasses method causes strange \"find: too many open files\" error (FIXED)\r\n- Methods that are the initiater of a chain don't get updated (CLOSED 07-07-2017)\r\n- Methods with the 'synchronized' keyword aren't noticed (FIXED 07-06-2017)\r\n- When renaming a method or field, we should find the base class in which it's declared (CLOSED 07-07-2017)\r\n- When a class inherits from multiple other classes\/interfaces, only the first is retrieved (FIXED 07-06-2017)\r\n- When a reflected type inherits from something in a class definition (), the reflected type is considered a superclass (FIXED 07-06-2017)\r\n- Switch statements are not recognized as blocks in extractMethod (TESTING 07-07-2017)\r\n- Increment and decrement operators not counted as left references (FIXED 07-07-2017)\r\n- Slight formatting error in formatMethod (FIXED 07-07-2017)\r\n- Methods with only one declared variable cause infinite loop (FIXED 07-07-2017)\r\n\r\nJAVA IMPROVEMENTS:\r\n- Rollback function--when things don't go as expected, provide a rollback to undo the previous action (DONE 07-06-2017)\r\n- Speed up renameMethod\r\n\r\n","3":"JAVA BUG FIXES: \r\n- When two references to a method occur on the same line, only the first gets updated (FIXED)\r\n- Methods of superclasses don't get checked in updateOutliers (FIXED)\r\n- Methods returning Collections or other structures(Trees, Lists, Sets) don't get updated (CLOSED 07-07-2017)\r\n- getSuperClasses method causes strange \"find: too many open files\" error (FIXED)\r\n- Methods that are the initiater of a chain don't get updated (CLOSED 07-07-2017)\r\n- Methods with the 'synchronized' keyword aren't noticed (FIXED 07-06-2017)\r\n- When renaming a method or field, we should find the base class in which it's declared (CLOSED 07-07-2017)\r\n- When a class inherits from multiple other classes\/interfaces, only the first is retrieved (FIXED 07-06-2017)\r\n- When a reflected type inherits from something in a class definition (), the reflected type is considered a superclass (FIXED 07-06-2017)\r\n- Switch statements are not recognized as blocks in extractMethod (TESTING 07-07-2017)\r\n- Increment and decrement operators not counted as left references (FIXED 07-07-2017)\r\n- Slight formatting error in formatMethod (FIXED 07-07-2017)\r\n- Methods with only one declared variable cause infinite loop (FIXED 07-07-2017)\r\n\r\nJAVA IMPROVEMENTS:\r\n- Rollback function--when things don't go as expected, provide a rollback to undo the previous action (DONE 07-06-2017)\r\n- Speed up renameMethod\r\n\r\n","package":"factorus.tar","4":"factorus.tar","src_id":"25383","5":"25383","creation_date":"1499442932","6":"1499442932"},{"0":"5586","vim_version":"7.0","1":"7.0","script_version":"1.75","2":"1.75","version_comment":"*Added addParam, renameClass, renameMethod, and renameArg for Python* *Changed various regex bugs that caused failures in Java* *Improved method renaming algorithm in Java*","3":"*Added addParam, renameClass, renameMethod, and renameArg for Python* *Changed various regex bugs that caused failures in Java* *Improved method renaming algorithm in Java*","package":"factorus.tar","4":"factorus.tar","src_id":"25364","5":"25364","creation_date":"1498859694","6":"1498859694"},{"0":"5586","vim_version":"7.0","1":"7.0","script_version":"1.5","2":"1.5","version_comment":"patch for overlong regular expression","3":"patch for overlong regular expression","package":"factorus.tar","4":"factorus.tar","src_id":"25362","5":"25362","creation_date":"1498778979","6":"1498778979"},{"0":"5586","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"factorus.tar","4":"factorus.tar","src_id":"25357","5":"25357","creation_date":"1498513211","6":"1498513211"}]},"5585":{"script_id":"5585","0":"5585","script_name":"stunter.vim","1":"stunter.vim","script_type":"utility","2":"utility","summary":"stunter.vim: run vim test","3":"stunter.vim: run vim test","description":"Stunter is for running test of vim scripts.\r\n\r\nHere is a sample script:\r\n\r\n    runtime stunter.vim\r\n\r\n    \" Need this to get the script id of the script being tested\r\n    fun! s:SID()\r\n      return matchstr(expand(\\'\\'), \\'\\\\zs\\\\d\\\\+\\\\ze_SID$\\')\r\n    endfun\r\n\r\n    \" Get the Test(functionName, arguments, expectedReturnValue) function\r\n    let Test = Stunter(s:SID())\r\n\r\n    fun! s:TestMe1(a)\r\n      return 30 + a:a\r\n    endfun\r\n\r\n    fun! g:TestMe2(a)\r\n      return 10 * a:a\r\n    endfun\r\n\r\n    fun! TestMe3(a, b)\r\n      return a:a + a:b\r\n    endfun\r\n\r\n    call Test(\\'s:TestMe1\\', [12], 42)\r\n    call Test(\\'g:TestMe2\\', [12], 120)\r\n    call Test(\\'TestMe3\\', [100, 8], 108)\r\n\r\nIf you `:source` a file with the above contents it should output:\r\n\r\n    ok..1  s:TestMe1(12) == 42\r\n    ok..2  g:TestMe2(12) == 120\r\n    ok..3  TestMe3(100, 8) == 108\r\n\r\nPlease report bugs and issues here:\r\n\r\n    https:\/\/github.com\/aklt\/stunter.vim\/issues\r\n","4":"Stunter is for running test of vim scripts.\r\n\r\nHere is a sample script:\r\n\r\n    runtime stunter.vim\r\n\r\n    \" Need this to get the script id of the script being tested\r\n    fun! s:SID()\r\n      return matchstr(expand(\\'\\'), \\'\\\\zs\\\\d\\\\+\\\\ze_SID$\\')\r\n    endfun\r\n\r\n    \" Get the Test(functionName, arguments, expectedReturnValue) function\r\n    let Test = Stunter(s:SID())\r\n\r\n    fun! s:TestMe1(a)\r\n      return 30 + a:a\r\n    endfun\r\n\r\n    fun! g:TestMe2(a)\r\n      return 10 * a:a\r\n    endfun\r\n\r\n    fun! TestMe3(a, b)\r\n      return a:a + a:b\r\n    endfun\r\n\r\n    call Test(\\'s:TestMe1\\', [12], 42)\r\n    call Test(\\'g:TestMe2\\', [12], 120)\r\n    call Test(\\'TestMe3\\', [100, 8], 108)\r\n\r\nIf you `:source` a file with the above contents it should output:\r\n\r\n    ok..1  s:TestMe1(12) == 42\r\n    ok..2  g:TestMe2(12) == 120\r\n    ok..3  TestMe3(100, 8) == 108\r\n\r\nPlease report bugs and issues here:\r\n\r\n    https:\/\/github.com\/aklt\/stunter.vim\/issues\r\n","install_details":"unpack stunter.vim.zip from your ~\/.vim directory or clone it from https:\/\/github.com\/aklt\/stunter.vim\r\nusing your favorite vim plugin manager. ","5":"unpack stunter.vim.zip from your ~\/.vim directory or clone it from https:\/\/github.com\/aklt\/stunter.vim\r\nusing your favorite vim plugin manager. ","first_name":"Anders","6":"Anders","last_name":"Th\u00c3\u00b8gersen","7":"Th\u00c3\u00b8gersen","releases":[{"0":"5585","vim_version":"8.0","1":"8.0","script_version":"0.1.0","2":"0.1.0","version_comment":"Initial upload","3":"Initial upload","package":"stunter.vim.zip","4":"stunter.vim.zip","src_id":"25344","5":"25344","creation_date":"1498395565","6":"1498395565"}]},"5584":{"script_id":"5584","0":"5584","script_name":"Vim PHP Wrapper","1":"Vim PHP Wrapper","script_type":"ftplugin","2":"ftplugin","summary":"A plug-in to speed up PHP development","3":"A plug-in to speed up PHP development","description":"Vim PHP Wrapper (vphpw) is a Vim plug-in to help improve PHP development\r\nproductivity. It provides functions for common tasks such as importing classes,\r\nrunning, testing, or documenting PHP code as well as simple APIs for custom\r\ntasks.\r\n\r\nFor unit testing, vphpw supports PHPUnit out of the box. Codeception is also\r\nsupported to a certain extent.\r\n\r\nFor more information and demos,\r\n\r\nhttps:\/\/github.com\/diepm\/vim-php-wrapper\r\n\r\nRequirements:\r\n\r\n  * Tested with Vim 7.4 and 8. Might still work with 7.3.\r\n  * Vim's `tags` for class import functions.\r\n\r\nSome features vphpw provides:\r\n\r\n  * Check for syntax (not in real-time).\r\n  * Import classes.\r\n  * Run the current PHP buffer with default or manually specified options.\r\n  * Test with default or manually specified options.\r\n  * Run a test class or specific test case.\r\n  * Execute the last command on the last or current target.\r\n  * Generate docblock.\r\n  * Align docblock.\r\n  * Reset\/Delete docblock.","4":"Vim PHP Wrapper (vphpw) is a Vim plug-in to help improve PHP development\r\nproductivity. It provides functions for common tasks such as importing classes,\r\nrunning, testing, or documenting PHP code as well as simple APIs for custom\r\ntasks.\r\n\r\nFor unit testing, vphpw supports PHPUnit out of the box. Codeception is also\r\nsupported to a certain extent.\r\n\r\nFor more information and demos,\r\n\r\nhttps:\/\/github.com\/diepm\/vim-php-wrapper\r\n\r\nRequirements:\r\n\r\n  * Tested with Vim 7.4 and 8. Might still work with 7.3.\r\n  * Vim's `tags` for class import functions.\r\n\r\nSome features vphpw provides:\r\n\r\n  * Check for syntax (not in real-time).\r\n  * Import classes.\r\n  * Run the current PHP buffer with default or manually specified options.\r\n  * Test with default or manually specified options.\r\n  * Run a test class or specific test case.\r\n  * Execute the last command on the last or current target.\r\n  * Generate docblock.\r\n  * Align docblock.\r\n  * Reset\/Delete docblock.","install_details":"","5":"","first_name":"diepm","6":"diepm","last_name":" ","7":" ","releases":[{"0":"5584","vim_version":"7.4","1":"7.4","script_version":"1.0.2","2":"1.0.2","version_comment":"* Set default value of import-as to the class under cursor.\r\n* Sort use statements ignoring case by default.","3":"* Set default value of import-as to the class under cursor.\r\n* Sort use statements ignoring case by default.","package":"vim-php-wrapper-1.0.2.tgz","4":"vim-php-wrapper-1.0.2.tgz","src_id":"25427","5":"25427","creation_date":"1500340395","6":"1500340395"},{"0":"5584","vim_version":"7.4","1":"7.4","script_version":"1.0.1","2":"1.0.1","version_comment":"* Fix closing a tagged file also wipes out an existing buffer.\r\n* Fix tag conflict in help file.\r\n* Add CHANGELOG.md","3":"* Fix closing a tagged file also wipes out an existing buffer.\r\n* Fix tag conflict in help file.\r\n* Add CHANGELOG.md","package":"vim-php-wrapper-1.0.1.tgz","4":"vim-php-wrapper-1.0.1.tgz","src_id":"25360","5":"25360","creation_date":"1498628004","6":"1498628004"},{"0":"5584","vim_version":"7.4","1":"7.4","script_version":"1.0.0","2":"1.0.0","version_comment":"Initial upload","3":"Initial upload","package":"vim-php-wrapper-1.0.0.tgz","4":"vim-php-wrapper-1.0.0.tgz","src_id":"25329","5":"25329","creation_date":"1498013865","6":"1498013865"}]},"5583":{"script_id":"5583","0":"5583","script_name":"DeleteHiddenBuffers","1":"DeleteHiddenBuffers","script_type":"utility","2":"utility","summary":"Clean your file buffer when you work for long periods on a large project","3":"Clean your file buffer when you work for long periods on a large project","description":"Description\r\n----------------\r\nWhen you work on a project for a long period you tend you accumulate a lot of background buffers. This plug-in will clear any unused buffers that are hidden. Don't worry this will not delete any active or unsaved buffers.\r\n\r\nUsage \r\n--------\r\n:DeleteHiddenBuffers\r\n\r\n\r\nGithub\r\n---------\r\nCheck the GitHub repo the latest updates.\r\nhttps:\/\/github.com\/arithran\/vim-delete-hidden-buffers\r\n","4":"Description\r\n----------------\r\nWhen you work on a project for a long period you tend you accumulate a lot of background buffers. This plug-in will clear any unused buffers that are hidden. Don't worry this will not delete any active or unsaved buffers.\r\n\r\nUsage \r\n--------\r\n:DeleteHiddenBuffers\r\n\r\n\r\nGithub\r\n---------\r\nCheck the GitHub repo the latest updates.\r\nhttps:\/\/github.com\/arithran\/vim-delete-hidden-buffers\r\n","install_details":"This plugin follows the standard runtime path structure, and as such it can be installed with a variety of plugin managers:\r\n\r\n\r\nThis plugin follows the standard runtime path structure, and as such, it can be installed with a variety of plugin managers:\r\n\r\n\r\nNeoBundle:     NeoBundle 'arithran\/vim-delete-hidden-buffers'\r\nVundle:\t     Plugin 'arithran\/vim-delete-hidden-buffers'\r\nPlug:\t             Plug 'arithran\/vim-delete-hidden-buffers'\r\nmanual:\t     copy all of the files into your ~\/.vim directory\r\n","5":"This plugin follows the standard runtime path structure, and as such it can be installed with a variety of plugin managers:\r\n\r\n\r\nThis plugin follows the standard runtime path structure, and as such, it can be installed with a variety of plugin managers:\r\n\r\n\r\nNeoBundle:     NeoBundle 'arithran\/vim-delete-hidden-buffers'\r\nVundle:\t     Plugin 'arithran\/vim-delete-hidden-buffers'\r\nPlug:\t             Plug 'arithran\/vim-delete-hidden-buffers'\r\nmanual:\t     copy all of the files into your ~\/.vim directory\r\n","first_name":"Arithran","6":"Arithran","last_name":"Thurairetnam","7":"Thurairetnam","releases":[{"0":"5583","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"vim-delete-hidden-buffers-master.zip","4":"vim-delete-hidden-buffers-master.zip","src_id":"25328","5":"25328","creation_date":"1498001904","6":"1498001904"}]},"5582":{"script_id":"5582","0":"5582","script_name":"ZFVimFoldBlock","1":"ZFVimFoldBlock","script_type":"utility","2":"utility","summary":"fold code block using regexp","3":"fold code block using regexp","description":"fold code block using regexp, multiline supported, best fold plugin for general usage\r\n\r\ngit repo: https:\/\/github.com\/ZSaberLv0\/ZFVimFoldBlock\r\n\r\npreview:\r\n\r\n* see all virtual functions `:ZFFoldBlock \/\/virtual\/`\r\n\r\n    https:\/\/raw.githubusercontent.com\/ZSaberLv0\/ZFVimFoldBlock\/master\/example0.png\r\n\r\n* filter out all comments `:ZFFoldBlock \/^[ \\t]*#\/\/`\r\n\r\n    https:\/\/raw.githubusercontent.com\/ZSaberLv0\/ZFVimFoldBlock\/master\/example1.png\r\n\r\n* fold by xml tags `:ZFFoldBlock \/(?<=<[a-z =\\\"_0-9]+> *\\n).*\/<\\\/[a-z0-9_]+>\/` (with `othree\/eregex.vim`)\r\n\r\n    https:\/\/raw.githubusercontent.com\/ZSaberLv0\/ZFVimFoldBlock\/master\/example2.png\r\n","4":"fold code block using regexp, multiline supported, best fold plugin for general usage\r\n\r\ngit repo: https:\/\/github.com\/ZSaberLv0\/ZFVimFoldBlock\r\n\r\npreview:\r\n\r\n* see all virtual functions `:ZFFoldBlock \/\/virtual\/`\r\n\r\n    https:\/\/raw.githubusercontent.com\/ZSaberLv0\/ZFVimFoldBlock\/master\/example0.png\r\n\r\n* filter out all comments `:ZFFoldBlock \/^[ \\t]*#\/\/`\r\n\r\n    https:\/\/raw.githubusercontent.com\/ZSaberLv0\/ZFVimFoldBlock\/master\/example1.png\r\n\r\n* fold by xml tags `:ZFFoldBlock \/(?<=<[a-z =\\\"_0-9]+> *\\n).*\/<\\\/[a-z0-9_]+>\/` (with `othree\/eregex.vim`)\r\n\r\n    https:\/\/raw.githubusercontent.com\/ZSaberLv0\/ZFVimFoldBlock\/master\/example2.png\r\n","install_details":"1. use Vundle(https:\/\/github.com\/VundleVim\/Vundle.vim) or any other plugin manager is recommended\r\n\r\n    Plugin 'ZSaberLv0\/ZFVimFoldBlock'\r\n\r\n    when `othree\/eregex.vim` installed (recommended), perl style regexp would be used instead of vim style\r\n\r\n    Plugin 'othree\/eregex.vim'\r\n\r\n    or, unzip and copy content to your vim's rtp ($HOME\/.vim)\r\n\r\n2. `foldmethod` must be set to `manual`\r\n\r\n    set foldmethod = manual\r\n\r\n    by default, `foldmethod` would be set to `manual` when `ZFFoldBlock` called,\r\n    you may disable it by `let g:ZFVimFoldBlock_resetFoldmethodWhenUse=0`\r\n\r\n3. `foldminlines` recommended set to `0`, which allow fold even for single line\r\n\r\n    set foldminlines=0\r\n\r\n4. recommended to have these key map:\r\n\r\n    nnoremap ZB q::call ZF_FoldBlockTemplate()\r\n    nnoremap ZF :ZFFoldBlock \/\/\r\n\r\n5. or, use the functions directly:\r\n\r\n    \" fold by begin and end regexp\r\n    :ZFFoldBlock \/begin_regexp\/end_regexp\/\r\n\r\n    \" same as :ZFFoldBlock \/regexp\/\/\r\n    :ZFFoldIfMatch regexp\r\n\r\n    \" same as :ZFFoldBlock \/\/regexp\/\r\n    :ZFFoldIfNotMatch regexp\r\n","5":"1. use Vundle(https:\/\/github.com\/VundleVim\/Vundle.vim) or any other plugin manager is recommended\r\n\r\n    Plugin 'ZSaberLv0\/ZFVimFoldBlock'\r\n\r\n    when `othree\/eregex.vim` installed (recommended), perl style regexp would be used instead of vim style\r\n\r\n    Plugin 'othree\/eregex.vim'\r\n\r\n    or, unzip and copy content to your vim's rtp ($HOME\/.vim)\r\n\r\n2. `foldmethod` must be set to `manual`\r\n\r\n    set foldmethod = manual\r\n\r\n    by default, `foldmethod` would be set to `manual` when `ZFFoldBlock` called,\r\n    you may disable it by `let g:ZFVimFoldBlock_resetFoldmethodWhenUse=0`\r\n\r\n3. `foldminlines` recommended set to `0`, which allow fold even for single line\r\n\r\n    set foldminlines=0\r\n\r\n4. recommended to have these key map:\r\n\r\n    nnoremap ZB q::call ZF_FoldBlockTemplate()\r\n    nnoremap ZF :ZFFoldBlock \/\/\r\n\r\n5. or, use the functions directly:\r\n\r\n    \" fold by begin and end regexp\r\n    :ZFFoldBlock \/begin_regexp\/end_regexp\/\r\n\r\n    \" same as :ZFFoldBlock \/regexp\/\/\r\n    :ZFFoldIfMatch regexp\r\n\r\n    \" same as :ZFFoldBlock \/\/regexp\/\r\n    :ZFFoldIfNotMatch regexp\r\n","first_name":"zero","6":"zero","last_name":"fighter","7":"fighter","releases":[{"0":"5582","vim_version":"7.3","1":"7.3","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"ZFVimFoldBlock.zip","4":"ZFVimFoldBlock.zip","src_id":"25327","5":"25327","creation_date":"1497942063","6":"1497942063"}]},"5581":{"script_id":"5581","0":"5581","script_name":"ZFVimIndentMove","1":"ZFVimIndentMove","script_type":"utility","2":"utility","summary":"move cursor quickly accorrding to indent","3":"move cursor quickly accorrding to indent","description":"vim script to move cursor quickly accorrding indent\r\n\r\ngit repo: https:\/\/github.com\/ZSaberLv0\/ZFVimIndentMove\r\n\r\ncheck the above git repo for preview","4":"vim script to move cursor quickly accorrding indent\r\n\r\ngit repo: https:\/\/github.com\/ZSaberLv0\/ZFVimIndentMove\r\n\r\ncheck the above git repo for preview","install_details":"1. use Vundle(https:\/\/github.com\/VundleVim\/Vundle.vim) or any other plugin manager you like to install\r\n\r\n    Plugin 'ZSaberLv0\/ZFVimIndentMove'\r\n\r\n    or, unzip and copy content to your vim's rtp ($HOME\/.vim) \r\n\r\n2. have your own keymap in your vimrc, recommended keymap:\r\n\r\n    nnoremap EE ``\r\n    nnoremap EH :call ZF_IndentMoveParent('n')\r\n    xnoremap EH :call ZF_IndentMoveParent('v')\r\n    nnoremap EL :call ZF_IndentMoveParentEnd('n')\r\n    xnoremap EL :call ZF_IndentMoveParentEnd('v')\r\n    nnoremap EK :call ZF_IndentMovePrev('n')\r\n    xnoremap EK :call ZF_IndentMovePrev('v')\r\n    nnoremap EJ :call ZF_IndentMoveNext('n')\r\n    xnoremap EJ :call ZF_IndentMoveNext('v')\r\n    nnoremap EI :call ZF_IndentMoveChild('n')\r\n    xnoremap EI :call ZF_IndentMoveChild('v')","5":"1. use Vundle(https:\/\/github.com\/VundleVim\/Vundle.vim) or any other plugin manager you like to install\r\n\r\n    Plugin 'ZSaberLv0\/ZFVimIndentMove'\r\n\r\n    or, unzip and copy content to your vim's rtp ($HOME\/.vim) \r\n\r\n2. have your own keymap in your vimrc, recommended keymap:\r\n\r\n    nnoremap EE ``\r\n    nnoremap EH :call ZF_IndentMoveParent('n')\r\n    xnoremap EH :call ZF_IndentMoveParent('v')\r\n    nnoremap EL :call ZF_IndentMoveParentEnd('n')\r\n    xnoremap EL :call ZF_IndentMoveParentEnd('v')\r\n    nnoremap EK :call ZF_IndentMovePrev('n')\r\n    xnoremap EK :call ZF_IndentMovePrev('v')\r\n    nnoremap EJ :call ZF_IndentMoveNext('n')\r\n    xnoremap EJ :call ZF_IndentMoveNext('v')\r\n    nnoremap EI :call ZF_IndentMoveChild('n')\r\n    xnoremap EI :call ZF_IndentMoveChild('v')","first_name":"zero","6":"zero","last_name":"fighter","7":"fighter","releases":[{"0":"5581","vim_version":"7.3","1":"7.3","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"ZFVimIndentMove.zip","4":"ZFVimIndentMove.zip","src_id":"25326","5":"25326","creation_date":"1497941377","6":"1497941377"}]},"5580":{"script_id":"5580","0":"5580","script_name":"ZFVimTxtHighlight","1":"ZFVimTxtHighlight","script_type":"syntax","2":"syntax","summary":"highlight plain text files, suit most cases","3":"highlight plain text files, suit most cases","description":"vim script to highlight plain text files\r\n\r\nscreenshot: https:\/\/raw.githubusercontent.com\/ZSaberLv0\/ZFVimTxtHighlight\/master\/screenshot.png\r\n\r\ngit repo: https:\/\/github.com\/ZSaberLv0\/ZFVimTxtHighlight","4":"vim script to highlight plain text files\r\n\r\nscreenshot: https:\/\/raw.githubusercontent.com\/ZSaberLv0\/ZFVimTxtHighlight\/master\/screenshot.png\r\n\r\ngit repo: https:\/\/github.com\/ZSaberLv0\/ZFVimTxtHighlight","install_details":"1. use Vundle(https:\/\/github.com\/VundleVim\/Vundle.vim) or any other plugin manager you like to install\r\n\r\n    Plugin 'ZSaberLv0\/ZFVimTxtHighlight'\r\n\r\n    or, unzip and copy content to your vim's rtp ($HOME\/.vim)\r\n\r\n2. by default, all `text` files or any other file that have no `syntax` specified,\r\n    would be set to `zftxt` as `syntax`\r\n\r\n    you can disable it by setting:\r\n\r\n    let g:zf_txt_auto_highlight=0\r\n\r\n    or, you may want to set `syntax` manually when necessary:\r\n\r\n    set syntax=zftxt\r\n","5":"1. use Vundle(https:\/\/github.com\/VundleVim\/Vundle.vim) or any other plugin manager you like to install\r\n\r\n    Plugin 'ZSaberLv0\/ZFVimTxtHighlight'\r\n\r\n    or, unzip and copy content to your vim's rtp ($HOME\/.vim)\r\n\r\n2. by default, all `text` files or any other file that have no `syntax` specified,\r\n    would be set to `zftxt` as `syntax`\r\n\r\n    you can disable it by setting:\r\n\r\n    let g:zf_txt_auto_highlight=0\r\n\r\n    or, you may want to set `syntax` manually when necessary:\r\n\r\n    set syntax=zftxt\r\n","first_name":"zero","6":"zero","last_name":"fighter","7":"fighter","releases":[{"0":"5580","vim_version":"7.3","1":"7.3","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"ZFVimTxtHighlight.zip","4":"ZFVimTxtHighlight.zip","src_id":"25325","5":"25325","creation_date":"1497941011","6":"1497941011"}]},"5579":{"script_id":"5579","0":"5579","script_name":"change-case.vim","1":"change-case.vim","script_type":"utility","2":"utility","summary":"Operator to change case (camelCase, snake_case, UPPER CASE etc.) of text","3":"Operator to change case (camelCase, snake_case, UPPER CASE etc.) of text","description":"The change case operator allows to change the case of text objects to one of seven different types:\r\n\r\n  * camelCase\r\n  * PascalCase\r\n  * snake_case\r\n  * kebab-case\r\n  * UPPER CASE\r\n  * lower case\r\n  * Title Case\r\n\r\nIf those types are not enough, custom case modifiers can be integrated seamlessly into the operator.\r\n\r\nCan be repeated with repeat.vim vimscript #2136.","4":"The change case operator allows to change the case of text objects to one of seven different types:\r\n\r\n  * camelCase\r\n  * PascalCase\r\n  * snake_case\r\n  * kebab-case\r\n  * UPPER CASE\r\n  * lower case\r\n  * Title Case\r\n\r\nIf those types are not enough, custom case modifiers can be integrated seamlessly into the operator.\r\n\r\nCan be repeated with repeat.vim vimscript #2136.","install_details":"Extract into ~\/.vim\r\nRun :helptags ~\/.vim\/doc in vim\r\n\r\nOr use a plugin manager (Vundle, Pathogen, vim-addon-manager)","5":"Extract into ~\/.vim\r\nRun :helptags ~\/.vim\/doc in vim\r\n\r\nOr use a plugin manager (Vundle, Pathogen, vim-addon-manager)","first_name":"Mohammed","6":"Mohammed","last_name":"Chelouti","7":"Chelouti","releases":[{"0":"5579","vim_version":"7.0","1":"7.0","script_version":"1.0.1","2":"1.0.1","version_comment":"Change mapping in visual mode from 'cC' to 'C'.","3":"Change mapping in visual mode from 'cC' to 'C'.","package":"vim-change-case.zip","4":"vim-change-case.zip","src_id":"25410","5":"25410","creation_date":"1500068071","6":"1500068071"},{"0":"5579","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"vim-change-case.zip","4":"vim-change-case.zip","src_id":"25321","5":"25321","creation_date":"1497864517","6":"1497864517"}]},"5578":{"script_id":"5578","0":"5578","script_name":"LiterateVimrc","1":"LiterateVimrc","script_type":"utility","2":"utility","summary":"Plugin for creating ","3":"Plugin for creating ","description":"\"Literate\" Vimrc is more than a bit of a misnomer. It, unlike Donald Knuth's\r\nvision of Literate Programming, does not support a loosely coupled web of macros\r\n-- instead it just lets you write a file in Markdown that has codeblocks (as\r\ndefined by v0.27 of the CommonMark spec) containing Vimscript as your\r\n`~\/.vimrc` file.\r\n\r\nhttps:\/\/github.com\/thcipriani\/literate-vimrc","4":"\"Literate\" Vimrc is more than a bit of a misnomer. It, unlike Donald Knuth's\r\nvision of Literate Programming, does not support a loosely coupled web of macros\r\n-- instead it just lets you write a file in Markdown that has codeblocks (as\r\ndefined by v0.27 of the CommonMark spec) containing Vimscript as your\r\n`~\/.vimrc` file.\r\n\r\nhttps:\/\/github.com\/thcipriani\/literate-vimrc","install_details":"1. Add autoload\/literatevimrc.vim to your autoload directory\r\n2. Move your ~\/.vimrc file to ~\/.vimrc.md and surround the actual contents in codeblock fence delimiters (i.e., ``` or ~~~)\r\n3. Add the line: execute literatevim#load(\"~\/.vimrc.md\") to your actual vimrc file","5":"1. Add autoload\/literatevimrc.vim to your autoload directory\r\n2. Move your ~\/.vimrc file to ~\/.vimrc.md and surround the actual contents in codeblock fence delimiters (i.e., ``` or ~~~)\r\n3. Add the line: execute literatevim#load(\"~\/.vimrc.md\") to your actual vimrc file","first_name":"Tyler","6":"Tyler","last_name":"Cipriani","7":"Cipriani","releases":[{"0":"5578","vim_version":"7.0","1":"7.0","script_version":"0.0.2","2":"0.0.2","version_comment":"Updated README, left version alone on this one.","3":"Updated README, left version alone on this one.","package":"literatevimrc.tar.gz","4":"literatevimrc.tar.gz","src_id":"25316","5":"25316","creation_date":"1497550170","6":"1497550170"},{"0":"5578","vim_version":"7.0","1":"7.0","script_version":"0.0.2","2":"0.0.2","version_comment":"* Fix inconsistent naming (literatevim vs literatevimrc) as pointed out by NoahTheDuke on github","3":"* Fix inconsistent naming (literatevim vs literatevimrc) as pointed out by NoahTheDuke on github","package":"LiterateVimrc.tar.gz","4":"LiterateVimrc.tar.gz","src_id":"25315","5":"25315","creation_date":"1497541348","6":"1497541348"},{"0":"5578","vim_version":"7.0","1":"7.0","script_version":"0.0.1","2":"0.0.1","version_comment":"Initial upload","3":"Initial upload","package":"literatevimrc.tar.gz","4":"literatevimrc.tar.gz","src_id":"25312","5":"25312","creation_date":"1497469305","6":"1497469305"}]},"5577":{"script_id":"5577","0":"5577","script_name":"CompleteParameter","1":"CompleteParameter","script_type":"utility","2":"utility","summary":"complete parameter after select the completion.","3":"complete parameter after select the completion.","description":"source: https:\/\/github.com\/tenfyzhong\/CompleteParameter.vim\r\n\r\nFeatures\r\n\r\nComplete parameters after select a complete item from the complete menu.\r\nAfter complete the parameters, jump to the first parameter and the select it.\r\ntype (default mapping) to jump to the next parameter in any position.\r\ntype (default mapping) to jump to the previous parameter in any position.\r\n\r\nUsage\r\n\r\nInstall a complete engine we have supported. Goto the complete item of the complete menu you want to select, and then type ((default mapping), the parameters will be completed and jump the the first parameter. \/(default mapping) will jump to the next\/previous parameter and select it.","4":"source: https:\/\/github.com\/tenfyzhong\/CompleteParameter.vim\r\n\r\nFeatures\r\n\r\nComplete parameters after select a complete item from the complete menu.\r\nAfter complete the parameters, jump to the first parameter and the select it.\r\ntype (default mapping) to jump to the next parameter in any position.\r\ntype (default mapping) to jump to the previous parameter in any position.\r\n\r\nUsage\r\n\r\nInstall a complete engine we have supported. Goto the complete item of the complete menu you want to select, and then type ((default mapping), the parameters will be completed and jump the the first parameter. \/(default mapping) will jump to the next\/previous parameter and select it.","install_details":"vim-plug\r\nPlug 'tenfyzhong\/CompleteParameter.vim'\r\n\r\nManual\r\ngit clone https:\/\/github.com\/tenfyzhong\/CompleteParameter.vim.git ~\/.vim\/bundle\/CompleteParameter.vim\r\necho 'set rtp+=~\/.vim\/bundle\/CompleteParameter.vim' >> ~\/.vimrc\r\nvim -c 'helptag ~\/.vim\/bundle\/CompleteParameter.vim\/doc' -c qa!","5":"vim-plug\r\nPlug 'tenfyzhong\/CompleteParameter.vim'\r\n\r\nManual\r\ngit clone https:\/\/github.com\/tenfyzhong\/CompleteParameter.vim.git ~\/.vim\/bundle\/CompleteParameter.vim\r\necho 'set rtp+=~\/.vim\/bundle\/CompleteParameter.vim' >> ~\/.vimrc\r\nvim -c 'helptag ~\/.vim\/bundle\/CompleteParameter.vim\/doc' -c qa!","first_name":"tenfy","6":"tenfy","last_name":"zhong","7":"zhong","releases":[{"0":"5577","vim_version":"7.4","1":"7.4","script_version":"0.6.1","2":"0.6.1","version_comment":"Python support keep default value and select the value only. \r\nAdd option g:complete_parameter_py_keep_value. \r\nSupport jeci. ","3":"Python support keep default value and select the value only. \r\nAdd option g:complete_parameter_py_keep_value. \r\nSupport jeci. ","package":"CompleteParameter.vim-0.6.1.tar.gz","4":"CompleteParameter.vim-0.6.1.tar.gz","src_id":"25558","5":"25558","creation_date":"1505012297","6":"1505012297"},{"0":"5577","vim_version":"7.4","1":"7.4","script_version":"0.6.0","2":"0.6.0","version_comment":"Rename file.\r\n\r\nInsert parameter if there are some content after the cursor.\r\nFix bug.","3":"Rename file.\r\n\r\nInsert parameter if there are some content after the cursor.\r\nFix bug.","package":"CompleteParameter.vim-0.6.0.tar.gz","4":"CompleteParameter.vim-0.6.0.tar.gz","src_id":"25520","5":"25520","creation_date":"1503222315","6":"1503222315"},{"0":"5577","vim_version":"7.4","1":"7.4","script_version":"0.5.0","2":"0.5.0","version_comment":"show signature.","3":"show signature.","package":"CompleteParameter.vim-0.5.0.tar.gz","4":"CompleteParameter.vim-0.5.0.tar.gz","src_id":"25492","5":"25492","creation_date":"1502328763","6":"1502328763"},{"0":"5577","vim_version":"7.4","1":"7.4","script_version":"0.4.0","2":"0.4.0","version_comment":"Hidden message. ","3":"Hidden message. ","package":"CompleteParameter.vim-0.4.0.tar.gz","4":"CompleteParameter.vim-0.4.0.tar.gz","src_id":"25487","5":"25487","creation_date":"1502156476","6":"1502156476"},{"0":"5577","vim_version":"7.3","1":"7.3","script_version":"0.3.1","2":"0.3.1","version_comment":"Refactor normal mapping to  mapping.\r\n    Remove mapping options:\r\n       g:complete_parameter_goto_next_mode,\r\n       g:complete_parameter_mapping_goto_next,\r\n       g:complete_parameter_goto_previous_mode,\r\n       g:complete_parameter_mapping_goto_previous,\r\n       g:complete_parameter_mapping_overload_up_mode,\r\n       g:complete_parameter_mapping_overload_up,\r\n       g:complete_parameter_mapping_overload_down_mode,\r\n       g:complete_parameter_mapping_overload_down,\r\n       g:complete_parameter_mapping_complete,\r\n       g:complete_parameter_failed_insert,\r\n       g:complete_parameter_mapping_complete_for_ft\r\n\tAdd mapping.\r\n       (complete_parameter#goto_next_parameter),\r\n       (complete_parameter#goto_previous_parameter),\r\n       (complete_parameter#overload_up),\r\n       (complete_parameter#overload_down)\r\n    Add options: g:complete_parameter_use_ultisnips_mappings\r\n","3":"Refactor normal mapping to  mapping.\r\n    Remove mapping options:\r\n       g:complete_parameter_goto_next_mode,\r\n       g:complete_parameter_mapping_goto_next,\r\n       g:complete_parameter_goto_previous_mode,\r\n       g:complete_parameter_mapping_goto_previous,\r\n       g:complete_parameter_mapping_overload_up_mode,\r\n       g:complete_parameter_mapping_overload_up,\r\n       g:complete_parameter_mapping_overload_down_mode,\r\n       g:complete_parameter_mapping_overload_down,\r\n       g:complete_parameter_mapping_complete,\r\n       g:complete_parameter_failed_insert,\r\n       g:complete_parameter_mapping_complete_for_ft\r\n\tAdd mapping.\r\n       (complete_parameter#goto_next_parameter),\r\n       (complete_parameter#goto_previous_parameter),\r\n       (complete_parameter#overload_up),\r\n       (complete_parameter#overload_down)\r\n    Add options: g:complete_parameter_use_ultisnips_mappings\r\n","package":"CompleteParameter.vim-0.3.1.tar.gz","4":"CompleteParameter.vim-0.3.1.tar.gz","src_id":"25457","5":"25457","creation_date":"1501248270","6":"1501248270"},{"0":"5577","vim_version":"7.4","1":"7.4","script_version":"0.2.2","2":"0.2.2","version_comment":"Only jump between the scope\r\nFix bugs.","3":"Only jump between the scope\r\nFix bugs.","package":"CompleteParameter.vim-0.2.2.tar.gz","4":"CompleteParameter.vim-0.2.2.tar.gz","src_id":"25382","5":"25382","creation_date":"1499414570","6":"1499414570"},{"0":"5577","vim_version":"7.4","1":"7.4","script_version":"0.2.0.1","2":"0.2.0.1","version_comment":"Support neocomplete. \r\nSupport clang_complete.\r\nSupport deoplete.","3":"Support neocomplete. \r\nSupport clang_complete.\r\nSupport deoplete.","package":"CompleteParameter.vim-0.2.0.1.tar.gz","4":"CompleteParameter.vim-0.2.0.1.tar.gz","src_id":"25363","5":"25363","creation_date":"1498817921","6":"1498817921"},{"0":"5577","vim_version":"7.4","1":"7.4","script_version":"0.1.4","2":"0.1.4","version_comment":"Toggle an event CompleteParameterFailed if complete failed.\r\nAdd a variable `g:complete_parameter_last_failed_insert` to set the failed_insert.\r\n\r\nFixed bug, delete select text when call the jump mapping.","3":"Toggle an event CompleteParameterFailed if complete failed.\r\nAdd a variable `g:complete_parameter_last_failed_insert` to set the failed_insert.\r\n\r\nFixed bug, delete select text when call the jump mapping.","package":"CompleteParameter.vim-0.1.4.tar.gz","4":"CompleteParameter.vim-0.1.4.tar.gz","src_id":"25337","5":"25337","creation_date":"1498312764","6":"1498312764"},{"0":"5577","vim_version":"7.4","1":"7.4","script_version":"0.0.3.2","2":"0.0.3.2","version_comment":"Support multi called for a file.                                                                                                                                                                                                              Support cpp class template.","3":"Support multi called for a file.                                                                                                                                                                                                              Support cpp class template.","package":"CompleteParameter.vim-0.0.3.2.tar.gz","4":"CompleteParameter.vim-0.0.3.2.tar.gz","src_id":"25314","5":"25314","creation_date":"1497500388","6":"1497500388"},{"0":"5577","vim_version":"7.4","1":"7.4","script_version":"0.0.2.1","2":"0.0.2.1","version_comment":"Initial upload","3":"Initial upload","package":"CompleteParameter.vim-0.0.2.1.tar.gz","4":"CompleteParameter.vim-0.0.2.1.tar.gz","src_id":"25311","5":"25311","creation_date":"1497417144","6":"1497417144"}]},"5576":{"script_id":"5576","0":"5576","script_name":"Absolute","1":"Absolute","script_type":"color scheme","2":"color scheme","summary":"Light Colorscheme","3":"Light Colorscheme","description":"for future update and screenshots: https:\/\/github.com\/AlessandroYorba\/Absolute","4":"for future update and screenshots: https:\/\/github.com\/AlessandroYorba\/Absolute","install_details":"","5":"","first_name":"Alessandro","6":"Alessandro","last_name":"Yorba","7":"Yorba","releases":[{"0":"5576","vim_version":"7.0","1":"7.0","script_version":"1","2":"1","version_comment":"New Tabline, StatusLine, and LineNr","3":"New Tabline, StatusLine, and LineNr","package":"absolute.vim","4":"absolute.vim","src_id":"25308","5":"25308","creation_date":"1497380608","6":"1497380608"}]},"5575":{"script_id":"5575","0":"5575","script_name":"WWDC17","1":"WWDC17","script_type":"color scheme","2":"color scheme","summary":"Colorful light color scheme inspired by WWDC17 page","3":"Colorful light color scheme inspired by WWDC17 page","description":"Code on GitHub: https:\/\/github.com\/lifepillar\/vim-wwdc17-theme \r\n\r\nA colorful light theme for Vim inspired by the colors of 2017's WWDC event. Better served with true-color terminals! \r\n\r\nWith support for italics and transparent background in the terminal, and customizable \u00e2\u0080\u009cframe\u00e2\u0080\u009d colors (status line, tab line, vertical splits).","4":"Code on GitHub: https:\/\/github.com\/lifepillar\/vim-wwdc17-theme \r\n\r\nA colorful light theme for Vim inspired by the colors of 2017's WWDC event. Better served with true-color terminals! \r\n\r\nWith support for italics and transparent background in the terminal, and customizable \u00e2\u0080\u009cframe\u00e2\u0080\u009d colors (status line, tab line, vertical splits).","install_details":"","5":"","first_name":"","6":"","last_name":"Lifepillar","7":"Lifepillar","releases":[{"0":"5575","vim_version":"7.0","1":"7.0","script_version":"2.2.0","2":"2.2.0","version_comment":"License under the MIT license.","3":"License under the MIT license.","package":"vim-wwdc17-v2.2.0.tar.gz","4":"vim-wwdc17-v2.2.0.tar.gz","src_id":"27370","5":"27370","creation_date":"1605509360","6":"1605509360"},{"0":"5575","vim_version":"7.0","1":"7.0","script_version":"2.1.0","2":"2.1.0","version_comment":"Increase contrast of some color combinations used as fg\/bg pairs so that they are ISO compliant.","3":"Increase contrast of some color combinations used as fg\/bg pairs so that they are ISO compliant.","package":"vim-wwdc17-theme-2.1.0.tar.gz","4":"vim-wwdc17-theme-2.1.0.tar.gz","src_id":"26165","5":"26165","creation_date":"1533427251","6":"1533427251"},{"0":"5575","vim_version":"7.0","1":"7.0","script_version":"2.1.0","2":"2.1.0","version_comment":"Increase contrast of some color combinations used as fg\/bg pairs so that they are ISO compliant.","3":"Increase contrast of some color combinations used as fg\/bg pairs so that they are ISO compliant.","package":"vim-wwdc17-theme-2.1.0.tar.gz","4":"vim-wwdc17-theme-2.1.0.tar.gz","src_id":"26164","5":"26164","creation_date":"1533427249","6":"1533427249"},{"0":"5575","vim_version":"7.0","1":"7.0","script_version":"2.0.0","2":"2.0.0","version_comment":"Updated palette (with slightly increased contrast for better readability). A few changes on frame colors. Removed 16-color variant. Defines g:terminal_ansi_colors. Updated terminal profiles.","3":"Updated palette (with slightly increased contrast for better readability). A few changes on frame colors. Removed 16-color variant. Defines g:terminal_ansi_colors. Updated terminal profiles.","package":"vim-wwdc17-theme-2.0.0.tar.gz","4":"vim-wwdc17-theme-2.0.0.tar.gz","src_id":"26065","5":"26065","creation_date":"1529446230","6":"1529446230"},{"0":"5575","vim_version":"7.0","1":"7.0","script_version":"1.2.1","2":"1.2.1","version_comment":"Prefer to fallback to 256 color palette. Update Search, IncSearch, LineNr, CursorLineNr, CursorColumn, FoldColumn hi groups. Add Terminal, ToolbarLine, ToolbarButton hi groups. Use transparent background in terminal when g:wwdc17_transp_bg=1. Remove filetype-specific highlight groups.","3":"Prefer to fallback to 256 color palette. Update Search, IncSearch, LineNr, CursorLineNr, CursorColumn, FoldColumn hi groups. Add Terminal, ToolbarLine, ToolbarButton hi groups. Use transparent background in terminal when g:wwdc17_transp_bg=1. Remove filetype-specific highlight groups.","package":"vim-wwdc17-theme-1.2.1.tar.gz","4":"vim-wwdc17-theme-1.2.1.tar.gz","src_id":"25789","5":"25789","creation_date":"1516553809","6":"1516553809"},{"0":"5575","vim_version":"7.0","1":"7.0","script_version":"v1.2.0","2":"v1.2.0","version_comment":"Allow using xterm's 256 color palette in terminals not supporting true colors.\r\nThe colorscheme is now built from a Colortemplate's template.","3":"Allow using xterm's 256 color palette in terminals not supporting true colors.\r\nThe colorscheme is now built from a Colortemplate's template.","package":"vim-wwdc17-theme-1.2.0.tar.gz","4":"vim-wwdc17-theme-1.2.0.tar.gz","src_id":"25626","5":"25626","creation_date":"1509215562","6":"1509215562"},{"0":"5575","vim_version":"7.0","1":"7.0","script_version":"1.1.0","2":"1.1.0","version_comment":"Too many changes to list here. Most relevant: added new Vim highlight groups QuickfixLine, StatuLineTerm and StatusLineTermNC; highlighting for bad spelling does not rely only on underline\/udercurl; the ANSI terminal palette has been fixed (i.e., Green is green, Yellow is yellow, etc\u00e2\u0080\u00a6). If you have intstalled WWDC17 for your terminal, do not forget to update terminal profile!","3":"Too many changes to list here. Most relevant: added new Vim highlight groups QuickfixLine, StatuLineTerm and StatusLineTermNC; highlighting for bad spelling does not rely only on underline\/udercurl; the ANSI terminal palette has been fixed (i.e., Green is green, Yellow is yellow, etc\u00e2\u0080\u00a6). If you have intstalled WWDC17 for your terminal, do not forget to update terminal profile!","package":"vim-wwdc17-theme-1.1.0.tar.gz","4":"vim-wwdc17-theme-1.1.0.tar.gz","src_id":"25553","5":"25553","creation_date":"1504638253","6":"1504638253"},{"0":"5575","vim_version":"7.0","1":"7.0","script_version":"1.0.0","2":"1.0.0","version_comment":"Initial upload","3":"Initial upload","package":"vim-wwdc17-theme-1.0.0.tar.gz","4":"vim-wwdc17-theme-1.0.0.tar.gz","src_id":"25303","5":"25303","creation_date":"1497172581","6":"1497172581"}]},"5574":{"script_id":"5574","0":"5574","script_name":"golint-fixer.vim","1":"golint-fixer.vim","script_type":"ftplugin","2":"ftplugin","summary":"A vim tool for fix goling warnings, which generate by vim-go or ale.","3":"A vim tool for fix goling warnings, which generate by vim-go or ale.","description":"Install\r\n\r\nUse a plugin manager\r\n\r\nfor vim-plug:\r\nAdd PlugAdd 'tenfyzhong\/golint-fixer.vim' to you .vimrc if you use .\r\n\r\nManual\r\n\r\nclone the repo.\r\ngit clone https:\/\/github.com\/tenfyzhong\/golint-fixer.vim.git ~\/.vim\/bundle\r\nadd rtp+=~\/.vim\/bundle\/golint-fixer.vim to you .vimrc\r\nDependence\r\n\r\nvim-go or ale\r\n\r\nUsage\r\n\r\nUse vim-go or ale to lint check. It'll add the warning to the quickfix or loclist.\r\nGo to the warning line. Run command :GoLintFix or nmap lf(if used).\r\nCommand\r\n\r\n:GoLintFix\r\nTry to fix the warning.\r\n\r\nNmap\r\n\r\nlf, if g:golint_fixer_use_default_mapping equal 1.\r\nTry to fix the warning.\r\n\r\nSetting\r\n\r\ng:golint_fixer_use_default_mapping\r\n\r\nType: bool\r\nDefault: 1\r\nMap lf to fix warning.\r\nlet g:golint_fixer_use_default_mapping = 1\r\n\r\ng:golint_fixer_use_go_rename\r\n\r\nType: bool\r\nDefault: 1\r\nUse :GoRename to rename identify if usable.\r\nlet g:golint_fixer_use_go_rename = 1","4":"Install\r\n\r\nUse a plugin manager\r\n\r\nfor vim-plug:\r\nAdd PlugAdd 'tenfyzhong\/golint-fixer.vim' to you .vimrc if you use .\r\n\r\nManual\r\n\r\nclone the repo.\r\ngit clone https:\/\/github.com\/tenfyzhong\/golint-fixer.vim.git ~\/.vim\/bundle\r\nadd rtp+=~\/.vim\/bundle\/golint-fixer.vim to you .vimrc\r\nDependence\r\n\r\nvim-go or ale\r\n\r\nUsage\r\n\r\nUse vim-go or ale to lint check. It'll add the warning to the quickfix or loclist.\r\nGo to the warning line. Run command :GoLintFix or nmap lf(if used).\r\nCommand\r\n\r\n:GoLintFix\r\nTry to fix the warning.\r\n\r\nNmap\r\n\r\nlf, if g:golint_fixer_use_default_mapping equal 1.\r\nTry to fix the warning.\r\n\r\nSetting\r\n\r\ng:golint_fixer_use_default_mapping\r\n\r\nType: bool\r\nDefault: 1\r\nMap lf to fix warning.\r\nlet g:golint_fixer_use_default_mapping = 1\r\n\r\ng:golint_fixer_use_go_rename\r\n\r\nType: bool\r\nDefault: 1\r\nUse :GoRename to rename identify if usable.\r\nlet g:golint_fixer_use_go_rename = 1","install_details":"mkdir -p ~\/.vim\/bundle\r\nmv golint-fixer.vim.tar.gz ~\/.vim\/bundle\r\ncd ~\/.vim\/bundle\r\ntar xzf golint-fixer.vim.tar.gz\r\necho 'rtp+=~\/.vim\/bundle\/golint-fixer' >> ~\/.vimrc ","5":"mkdir -p ~\/.vim\/bundle\r\nmv golint-fixer.vim.tar.gz ~\/.vim\/bundle\r\ncd ~\/.vim\/bundle\r\ntar xzf golint-fixer.vim.tar.gz\r\necho 'rtp+=~\/.vim\/bundle\/golint-fixer' >> ~\/.vimrc ","first_name":"tenfy","6":"tenfy","last_name":"zhong","7":"zhong","releases":[{"0":"5574","vim_version":"8.0","1":"8.0","script_version":"1.0.0","2":"1.0.0","version_comment":"Initial upload","3":"Initial upload","package":"golint-fixer.vim.tar.gz","4":"golint-fixer.vim.tar.gz","src_id":"25281","5":"25281","creation_date":"1496624270","6":"1496624270"}]},"5573":{"script_id":"5573","0":"5573","script_name":"yankee","1":"yankee","script_type":"utility","2":"utility","summary":"minimal plugin to make yanking more fun","3":"minimal plugin to make yanking more fun","description":"Yankee is a minimal plugin to fix some of the annoyances around yanking and maybe more in the future.\r\n\r\nCurrent features:\r\n\r\n* locking default paste register (so that `p` will keep pasting the same thing, even if you delete\/change\/yank\r\n  something else in between).\r\n\r\nv1.0 features:\r\n\r\n* easily paste from system clipboard\r\n\r\nMore details? See https:\/\/github.com\/nielsmadan\/yankee","4":"Yankee is a minimal plugin to fix some of the annoyances around yanking and maybe more in the future.\r\n\r\nCurrent features:\r\n\r\n* locking default paste register (so that `p` will keep pasting the same thing, even if you delete\/change\/yank\r\n  something else in between).\r\n\r\nv1.0 features:\r\n\r\n* easily paste from system clipboard\r\n\r\nMore details? See https:\/\/github.com\/nielsmadan\/yankee","install_details":"yankee depends on venom. Best way to install is with [vim-plug](https:\/\/github.com\/junegunn\/vim-plug):\r\n\r\n Plug 'nielsmadan\/venom' | Plug 'nielsmadan\/yankee'","5":"yankee depends on venom. Best way to install is with [vim-plug](https:\/\/github.com\/junegunn\/vim-plug):\r\n\r\n Plug 'nielsmadan\/venom' | Plug 'nielsmadan\/yankee'","first_name":"Niels","6":"Niels","last_name":"Madan","7":"Madan","releases":[{"0":"5573","vim_version":"7.0","1":"7.0","script_version":"0.5","2":"0.5","version_comment":"Initial upload","3":"Initial upload","package":"yankee.zip","4":"yankee.zip","src_id":"25260","5":"25260","creation_date":"1495809127","6":"1495809127"}]},"5572":{"script_id":"5572","0":"5572","script_name":"vim-prettier","1":"vim-prettier","script_type":"utility","2":"utility","summary":"A vim plugin wrapper for prettier","3":"A vim plugin wrapper for prettier","description":"## vim-prettier\r\n\r\nA vim plugin wrapper for prettier, pre-configured with custom default prettier\r\nsettings.\r\n\r\n---\r\n\r\nBy default it will auto format **javascript**, **typescript**, **less**,\r\n**scss**, **css**, **json**, **graphql** and **markdown** files if they\r\nhave\/support the \"@format\" pragma annotation in the header of the file.\r\n\r\n### Prettier Executable resolution\r\n\r\nWhen installed via vim-plug, a default prettier executable is installed inside\r\nvim-prettier.\r\n\r\nvim-prettier executable resolution:\r\n\r\n1. Look for user defined prettier cli path from vim configuration file\r\n2. Traverse parents and search for Prettier installation inside `node_modules`\r\n3. Look for a global prettier installation\r\n4. Use locally installed vim-prettier prettier executable\r\n\r\n### USAGE\r\n\r\nPrettier by default will run on auto save but can also be manually triggered by:\r\n\r\n```vim\r\np\r\n```\r\n\r\nor\r\n\r\n```vim\r\n:Prettier\r\n```\r\n\r\nIf your are on vim 8+ you can also trigger async formatting by:\r\n\r\n```vim\r\n:PrettierAsync\r\n```\r\n\r\nYou can check what is the `vim-prettier` plugin version by:\r\n\r\n```vim\r\n:PrettierVersion\r\n```\r\n\r\nYou can send commands to the resolved `prettier` cli by:\r\n\r\n```\r\n:PrettierCli \r\n```\r\n\r\nYou can check what is the resolved `prettier` cli path by:\r\n\r\n```vim\r\n:PrettierCliPath\r\n```\r\n\r\nYou can check what is the resolved `prettier` cli version by:\r\n\r\n```vim\r\n:PrettierCliVersion\r\n```\r\n\r\n### Configuration\r\n\r\nChange the mapping to run from the default of `p`\r\n\r\n```vim\r\nnmap py (Prettier)\r\n```\r\n\r\nDisable auto formatting of files that have \"@format\" tag\r\n\r\n```vim\r\nlet g:prettier#autoformat = 0\r\n```\r\n\r\nSet the prettier CLI executable path\r\n\r\n```vim\r\nlet g:prettier#exec_cmd_path = \"~\/path\/to\/cli\/prettier\"\r\n```\r\n\r\nThe command `:Prettier` by default is synchronous but can also be forced async\r\n\r\n```vim\r\nlet g:prettier#exec_cmd_async = 1\r\n```\r\n\r\nBy default parsing errors will open the quickfix but can also be disabled\r\n\r\n```vim\r\nlet g:prettier#quickfix_enabled = 0\r\n```\r\n\r\nTo enable vim-prettier to run in files without requiring the \"@format\" doc tag.\r\nFirst disable the default autoformat, then update to your own custom behaviour\r\n\r\nRunning before saving sync:\r\n\r\n```vim\r\nlet g:prettier#autoformat = 0\r\nautocmd BufWritePre *.js,*.jsx,*.mjs,*.ts,*.tsx,*.css,*.less,*.scss,*.json,*.graphql,*.md Prettier\r\n```\r\n\r\nRunning before saving async (vim 8+):\r\n\r\n```vim\r\nlet g:prettier#autoformat = 0\r\nautocmd BufWritePre *.js,*.jsx,*.mjs,*.ts,*.tsx,*.css,*.less,*.scss,*.json,*.graphql,*.md PrettierAsync\r\n```\r\n\r\nRunning before saving, changing text or leaving insert mode:\r\n\r\n```vim\r\n\" when running at every change you may want to disable quickfix\r\nlet g:prettier#quickfix_enabled = 0\r\n\r\nlet g:prettier#autoformat = 0\r\nautocmd BufWritePre,TextChanged,InsertLeave *.js,*.jsx,*.mjs,*.ts,*.tsx,*.css,*.less,*.scss,*.json,*.graphql,*.md PrettierAsync\r\n```\r\n\r\n### Overwrite default prettier configuration\r\n\r\n**Note:** vim-prettier default settings differ from prettier intentionally.\r\nHowever they can be configured by:\r\n\r\n```vim\r\n\" max line length that prettier will wrap on\r\nlet g:prettier#config#print_width = 80\r\n\r\n\" number of spaces per indentation level\r\nlet g:prettier#config#tab_width = 2\r\n\r\n\" use tabs over spaces\r\nlet g:prettier#config#use_tabs = 'false'\r\n\r\n\" print semicolons\r\nlet g:prettier#config#semi = 'true'\r\n\r\n\" single quotes over double quotes\r\nlet g:prettier#config#single_quote = 'true'\r\n\r\n\" print spaces between brackets\r\nlet g:prettier#config#bracket_spacing = 'false'\r\n\r\n\" put > on the last line instead of new line\r\nlet g:prettier#config#jsx_bracket_same_line = 'true'\r\n\r\n\" none|es5|all\r\nlet g:prettier#config#trailing_comma = 'all'\r\n\r\n\" flow|babylon|typescript|css|less|scss|json|graphql|markdown\r\nlet g:prettier#config#parser = 'flow'\r\n\r\n\" cli-override|file-override|prefer-file\r\nlet g:prettier#config#config_precedence = 'prefer-file'\r\n```\r\n\r\n### REQUIREMENT(S)\r\n\r\nIf prettier installation can't be found no code formatting will happen\r\n","4":"## vim-prettier\r\n\r\nA vim plugin wrapper for prettier, pre-configured with custom default prettier\r\nsettings.\r\n\r\n---\r\n\r\nBy default it will auto format **javascript**, **typescript**, **less**,\r\n**scss**, **css**, **json**, **graphql** and **markdown** files if they\r\nhave\/support the \"@format\" pragma annotation in the header of the file.\r\n\r\n### Prettier Executable resolution\r\n\r\nWhen installed via vim-plug, a default prettier executable is installed inside\r\nvim-prettier.\r\n\r\nvim-prettier executable resolution:\r\n\r\n1. Look for user defined prettier cli path from vim configuration file\r\n2. Traverse parents and search for Prettier installation inside `node_modules`\r\n3. Look for a global prettier installation\r\n4. Use locally installed vim-prettier prettier executable\r\n\r\n### USAGE\r\n\r\nPrettier by default will run on auto save but can also be manually triggered by:\r\n\r\n```vim\r\np\r\n```\r\n\r\nor\r\n\r\n```vim\r\n:Prettier\r\n```\r\n\r\nIf your are on vim 8+ you can also trigger async formatting by:\r\n\r\n```vim\r\n:PrettierAsync\r\n```\r\n\r\nYou can check what is the `vim-prettier` plugin version by:\r\n\r\n```vim\r\n:PrettierVersion\r\n```\r\n\r\nYou can send commands to the resolved `prettier` cli by:\r\n\r\n```\r\n:PrettierCli \r\n```\r\n\r\nYou can check what is the resolved `prettier` cli path by:\r\n\r\n```vim\r\n:PrettierCliPath\r\n```\r\n\r\nYou can check what is the resolved `prettier` cli version by:\r\n\r\n```vim\r\n:PrettierCliVersion\r\n```\r\n\r\n### Configuration\r\n\r\nChange the mapping to run from the default of `p`\r\n\r\n```vim\r\nnmap py (Prettier)\r\n```\r\n\r\nDisable auto formatting of files that have \"@format\" tag\r\n\r\n```vim\r\nlet g:prettier#autoformat = 0\r\n```\r\n\r\nSet the prettier CLI executable path\r\n\r\n```vim\r\nlet g:prettier#exec_cmd_path = \"~\/path\/to\/cli\/prettier\"\r\n```\r\n\r\nThe command `:Prettier` by default is synchronous but can also be forced async\r\n\r\n```vim\r\nlet g:prettier#exec_cmd_async = 1\r\n```\r\n\r\nBy default parsing errors will open the quickfix but can also be disabled\r\n\r\n```vim\r\nlet g:prettier#quickfix_enabled = 0\r\n```\r\n\r\nTo enable vim-prettier to run in files without requiring the \"@format\" doc tag.\r\nFirst disable the default autoformat, then update to your own custom behaviour\r\n\r\nRunning before saving sync:\r\n\r\n```vim\r\nlet g:prettier#autoformat = 0\r\nautocmd BufWritePre *.js,*.jsx,*.mjs,*.ts,*.tsx,*.css,*.less,*.scss,*.json,*.graphql,*.md Prettier\r\n```\r\n\r\nRunning before saving async (vim 8+):\r\n\r\n```vim\r\nlet g:prettier#autoformat = 0\r\nautocmd BufWritePre *.js,*.jsx,*.mjs,*.ts,*.tsx,*.css,*.less,*.scss,*.json,*.graphql,*.md PrettierAsync\r\n```\r\n\r\nRunning before saving, changing text or leaving insert mode:\r\n\r\n```vim\r\n\" when running at every change you may want to disable quickfix\r\nlet g:prettier#quickfix_enabled = 0\r\n\r\nlet g:prettier#autoformat = 0\r\nautocmd BufWritePre,TextChanged,InsertLeave *.js,*.jsx,*.mjs,*.ts,*.tsx,*.css,*.less,*.scss,*.json,*.graphql,*.md PrettierAsync\r\n```\r\n\r\n### Overwrite default prettier configuration\r\n\r\n**Note:** vim-prettier default settings differ from prettier intentionally.\r\nHowever they can be configured by:\r\n\r\n```vim\r\n\" max line length that prettier will wrap on\r\nlet g:prettier#config#print_width = 80\r\n\r\n\" number of spaces per indentation level\r\nlet g:prettier#config#tab_width = 2\r\n\r\n\" use tabs over spaces\r\nlet g:prettier#config#use_tabs = 'false'\r\n\r\n\" print semicolons\r\nlet g:prettier#config#semi = 'true'\r\n\r\n\" single quotes over double quotes\r\nlet g:prettier#config#single_quote = 'true'\r\n\r\n\" print spaces between brackets\r\nlet g:prettier#config#bracket_spacing = 'false'\r\n\r\n\" put > on the last line instead of new line\r\nlet g:prettier#config#jsx_bracket_same_line = 'true'\r\n\r\n\" none|es5|all\r\nlet g:prettier#config#trailing_comma = 'all'\r\n\r\n\" flow|babylon|typescript|css|less|scss|json|graphql|markdown\r\nlet g:prettier#config#parser = 'flow'\r\n\r\n\" cli-override|file-override|prefer-file\r\nlet g:prettier#config#config_precedence = 'prefer-file'\r\n```\r\n\r\n### REQUIREMENT(S)\r\n\r\nIf prettier installation can't be found no code formatting will happen\r\n","install_details":"### INSTALL\r\n\r\nInstall with [vim-plug](https:\/\/github.com\/junegunn\/vim-plug), assumes node and\r\nyarn|npm installed globally.\r\n\r\n```vim\r\n\" post install (yarn install | npm install) then load plugin only for editing supported files\r\nPlug 'prettier\/vim-prettier', {\r\n  \\ 'do': 'yarn install',\r\n  \\ 'for': ['javascript', 'typescript', 'css', 'less', 'scss', 'json', 'graphql', 'markdown'] }\r\n```\r\n\r\nor simply enable for all formats by:\r\n\r\n```vim\r\n\" post install (yarn install | npm install) then load plugin only for editing supported files\r\nPlug 'prettier\/vim-prettier', { 'do': 'yarn install' }\r\n```\r\n\r\nIf using other vim plugin managers or doing manual setup make sure to have\r\n`prettier` installed globally or go to your vim-prettier directory and either do\r\n`npm install` or `yarn install`","5":"### INSTALL\r\n\r\nInstall with [vim-plug](https:\/\/github.com\/junegunn\/vim-plug), assumes node and\r\nyarn|npm installed globally.\r\n\r\n```vim\r\n\" post install (yarn install | npm install) then load plugin only for editing supported files\r\nPlug 'prettier\/vim-prettier', {\r\n  \\ 'do': 'yarn install',\r\n  \\ 'for': ['javascript', 'typescript', 'css', 'less', 'scss', 'json', 'graphql', 'markdown'] }\r\n```\r\n\r\nor simply enable for all formats by:\r\n\r\n```vim\r\n\" post install (yarn install | npm install) then load plugin only for editing supported files\r\nPlug 'prettier\/vim-prettier', { 'do': 'yarn install' }\r\n```\r\n\r\nIf using other vim plugin managers or doing manual setup make sure to have\r\n`prettier` installed globally or go to your vim-prettier directory and either do\r\n`npm install` or `yarn install`","first_name":"mtermayer","6":"mtermayer","last_name":"reis","7":"reis","releases":[{"0":"5572","vim_version":"7.4","1":"7.4","script_version":"0.2.6","2":"0.2.6","version_comment":"feature - adding support for prettier 1.9.1","3":"feature - adding support for prettier 1.9.1","package":"vim-prettier-0.2.6.zip","4":"vim-prettier-0.2.6.zip","src_id":"25703","5":"25703","creation_date":"1512770892","6":"1512770892"},{"0":"5572","vim_version":"7.4","1":"7.4","script_version":"0.2.5","2":"0.2.5","version_comment":"feature: Adding support for prettier 1.8\r\nfeature: Adding support for formatting markdown files","3":"feature: Adding support for prettier 1.8\r\nfeature: Adding support for formatting markdown files","package":"vim-prettier-0.2.5.zip","4":"vim-prettier-0.2.5.zip","src_id":"25637","5":"25637","creation_date":"1510169905","6":"1510169905"},{"0":"5572","vim_version":"7.4","1":"7.4","script_version":"0.2.4","2":"0.2.4","version_comment":"bugfix: fixing bug where vim-prettier would incorrectly resolve the prettier configuration file","3":"bugfix: fixing bug where vim-prettier would incorrectly resolve the prettier configuration file","package":"vim-prettier-0.2.4.zip","4":"vim-prettier-0.2.4.zip","src_id":"25613","5":"25613","creation_date":"1508474211","6":"1508474211"},{"0":"5572","vim_version":"7.4","1":"7.4","script_version":"0.2.3","2":"0.2.3","version_comment":"feature: adding support for vim 8.0-0015+","3":"feature: adding support for vim 8.0-0015+","package":"vim-prettier-0.2.3.zip","4":"vim-prettier-0.2.3.zip","src_id":"25604","5":"25604","creation_date":"1507434185","6":"1507434185"},{"0":"5572","vim_version":"7.4","1":"7.4","script_version":"0.2.2","2":"0.2.2","version_comment":"feature: supporting formatting hidden buffers that already had scheduled jobs running","3":"feature: supporting formatting hidden buffers that already had scheduled jobs running","package":"vim-prettier-0.2.2.zip","4":"vim-prettier-0.2.2.zip","src_id":"25603","5":"25603","creation_date":"1507414794","6":"1507414794"},{"0":"5572","vim_version":"7.4","1":"7.4","script_version":"0.2.1","2":"0.2.1","version_comment":"bugfix: fixing race conditions ","3":"bugfix: fixing race conditions ","package":"vim-prettier-0.2.1.zip","4":"vim-prettier-0.2.1.zip","src_id":"25602","5":"25602","creation_date":"1507361050","6":"1507361050"},{"0":"5572","vim_version":"7.4","1":"7.4","script_version":"0.2.0","2":"0.2.0","version_comment":"bugfix: Non javascript parsers were broken due to parser flag been ignored by prettier when using configPrecedence, this make sure all non javascript parsers can leverage from custom config","3":"bugfix: Non javascript parsers were broken due to parser flag been ignored by prettier when using configPrecedence, this make sure all non javascript parsers can leverage from custom config","package":"vim-prettier-0.2.0.zip","4":"vim-prettier-0.2.0.zip","src_id":"25600","5":"25600","creation_date":"1507096864","6":"1507096864"},{"0":"5572","vim_version":"7.4","1":"7.4","script_version":"0.1.3","2":"0.1.3","version_comment":"bugfix: Non javascript parsers were broken due to parser flag been ignored by prettier when using configPrecedence\r\n","3":"bugfix: Non javascript parsers were broken due to parser flag been ignored by prettier when using configPrecedence\r\n","package":"vim-prettier-0.1.3.zip","4":"vim-prettier-0.1.3.zip","src_id":"25594","5":"25594","creation_date":"1506748157","6":"1506748157"},{"0":"5572","vim_version":"7.4","1":"7.4","script_version":"0.1.2","2":"0.1.2","version_comment":"feature: Adding support to overwrite prettier cli path via vim configuration ","3":"feature: Adding support to overwrite prettier cli path via vim configuration ","package":"vim-prettier-0.1.2.zip","4":"vim-prettier-0.1.2.zip","src_id":"25587","5":"25587","creation_date":"1506404507","6":"1506404507"},{"0":"5572","vim_version":"7.4","1":"7.4","script_version":"0.1.1","2":"0.1.1","version_comment":"feature: Adding new commands\r\n\r\n- `:PrettierVersion` - prints the `vim-prettier` plugin version\r\n- `:PrettierCli ` - send commands to the resolved `prettier` cli \r\n- `:PrettierCliPath` - check what is the resolved `prettier` cli path\r\n- `:PrettierCliVersion` - check what is the resolved `prettier` cli version \r\n\r\n","3":"feature: Adding new commands\r\n\r\n- `:PrettierVersion` - prints the `vim-prettier` plugin version\r\n- `:PrettierCli ` - send commands to the resolved `prettier` cli \r\n- `:PrettierCliPath` - check what is the resolved `prettier` cli path\r\n- `:PrettierCliVersion` - check what is the resolved `prettier` cli version \r\n\r\n","package":"vim-prettier-0.1.1.zip","4":"vim-prettier-0.1.1.zip","src_id":"25573","5":"25573","creation_date":"1505717738","6":"1505717738"},{"0":"5572","vim_version":"7.4","1":"7.4","script_version":"0.1.0","2":"0.1.0","version_comment":"Breaking Change: requires prettier 1.7+\r\nfeature: adding support for prettier 1.7 \r\nfeature: adds support for prettier custom configuration '.prettierrc' - refer to prettier website\r\n","3":"Breaking Change: requires prettier 1.7+\r\nfeature: adding support for prettier 1.7 \r\nfeature: adds support for prettier custom configuration '.prettierrc' - refer to prettier website\r\n","package":"vim-prettier-0.1.0.zip","4":"vim-prettier-0.1.0.zip","src_id":"25569","5":"25569","creation_date":"1505623739","6":"1505623739"},{"0":"5572","vim_version":"7.4","1":"7.4","script_version":"0.0.15","2":"0.0.15","version_comment":"bugfix: after formatting making sure cursor jump history does not take cursor to first line of file","3":"bugfix: after formatting making sure cursor jump history does not take cursor to first line of file","package":"vim-prettier-0.0.15.zip","4":"vim-prettier-0.0.15.zip","src_id":"25542","5":"25542","creation_date":"1504074075","6":"1504074075"},{"0":"5572","vim_version":"7.4","1":"7.4","script_version":"0.0.14","2":"0.0.14","version_comment":"bugfix: fixing support for :PrettierAsync for windows users","3":"bugfix: fixing support for :PrettierAsync for windows users","package":"vim-prettier-0.0.14.zip","4":"vim-prettier-0.0.14.zip","src_id":"25527","5":"25527","creation_date":"1503590988","6":"1503590988"},{"0":"5572","vim_version":"7.4","1":"7.4","script_version":"0.0.13","2":"0.0.13","version_comment":"bugfix: making sure quickfix errors are only cleared if opened by vim-prettier itself","3":"bugfix: making sure quickfix errors are only cleared if opened by vim-prettier itself","package":"vim-prettier-0.0.13.zip","4":"vim-prettier-0.0.13.zip","src_id":"25504","5":"25504","creation_date":"1502584738","6":"1502584738"},{"0":"5572","vim_version":"7.4","1":"7.4","script_version":"0.0.12","2":"0.0.12","version_comment":"feature: Bumping internal prettier version to 1.5.3","3":"feature: Bumping internal prettier version to 1.5.3","package":"vim-prettier-0.0.12.zip","4":"vim-prettier-0.0.12.zip","src_id":"25481","5":"25481","creation_date":"1502048345","6":"1502048345"},{"0":"5572","vim_version":"7.4","1":"7.4","script_version":"0.0.11","2":"0.0.11","version_comment":"feature: Adding support for vim 7.4","3":"feature: Adding support for vim 7.4","package":"vim-prettier-0.0.11.zip","4":"vim-prettier-0.0.11.zip","src_id":"25393","5":"25393","creation_date":"1499838107","6":"1499838107"},{"0":"5572","vim_version":"8.0","1":"8.0","script_version":"0.0.10","2":"0.0.10","version_comment":"bugfix: fixing bug where json parser could create invalid json by adding extra comma to the end","3":"bugfix: fixing bug where json parser could create invalid json by adding extra comma to the end","package":"vim-prettier-0.0.10.zip","4":"vim-prettier-0.0.10.zip","src_id":"25368","5":"25368","creation_date":"1498972006","6":"1498972006"},{"0":"5572","vim_version":"8.0","1":"8.0","script_version":"0.0.9","2":"0.0.9","version_comment":"feature: file type detection support","3":"feature: file type detection support","package":"vim-prettier-0.0.9.zip","4":"vim-prettier-0.0.9.zip","src_id":"25366","5":"25366","creation_date":"1498889075","6":"1498889075"},{"0":"5572","vim_version":"8.0","1":"8.0","script_version":"0.0.8","2":"0.0.8","version_comment":"feature: Adding support for JSON and GraphQL formatting","3":"feature: Adding support for JSON and GraphQL formatting","package":"vim-prettier-0.0.8.zip","4":"vim-prettier-0.0.8.zip","src_id":"25365","5":"25365","creation_date":"1498884115","6":"1498884115"},{"0":"5572","vim_version":"8.0","1":"8.0","script_version":"0.0.7","2":"0.0.7","version_comment":"feature: enabling partial buffer conversion when using visual selection","3":"feature: enabling partial buffer conversion when using visual selection","package":"vim-prettier-0.0.7.zip","4":"vim-prettier-0.0.7.zip","src_id":"25324","5":"25324","creation_date":"1497933099","6":"1497933099"},{"0":"5572","vim_version":"8.0","1":"8.0","script_version":"0.0.6","2":"0.0.6","version_comment":"feature: Adding configuration toggle for controlling error quick fix parsing\r\nfeature: Adding PrettierAsync command\r\nbugfix: Fixing configuration bug where boolean values where not correctly  parsed\r\nbugfix: Making sure that async jobs do not execute if already in progress\r\n","3":"feature: Adding configuration toggle for controlling error quick fix parsing\r\nfeature: Adding PrettierAsync command\r\nbugfix: Fixing configuration bug where boolean values where not correctly  parsed\r\nbugfix: Making sure that async jobs do not execute if already in progress\r\n","package":"vim-prettier-0.0.6.zip","4":"vim-prettier-0.0.6.zip","src_id":"25290","5":"25290","creation_date":"1496859678","6":"1496859678"},{"0":"5572","vim_version":"8.0","1":"8.0","script_version":"0.0.5","2":"0.0.5","version_comment":"feature: Bumping support to latest prettier ^1.4.X\r\nfeature:  Support for formatting css, scss, less, typescript\r\nfeature:  Allowing user configuration setting to enable async as the default for the `:Prettier` command","3":"feature: Bumping support to latest prettier ^1.4.X\r\nfeature:  Support for formatting css, scss, less, typescript\r\nfeature:  Allowing user configuration setting to enable async as the default for the `:Prettier` command","package":"vim-prettier-0.0.5.zip","4":"vim-prettier-0.0.5.zip","src_id":"25286","5":"25286","creation_date":"1496777466","6":"1496777466"},{"0":"5572","vim_version":"8.0","1":"8.0","script_version":"0.0.4","2":"0.0.4","version_comment":"feature: Adding support for error parsing on quickfix\r\n","3":"feature: Adding support for error parsing on quickfix\r\n","package":"vim-prettier-0.0.4.zip","4":"vim-prettier-0.0.4.zip","src_id":"25275","5":"25275","creation_date":"1496270362","6":"1496270362"},{"0":"5572","vim_version":"8.0","1":"8.0","script_version":"0.0.3","2":"0.0.3","version_comment":"feature: Adding support for Async formatting  and making it default for auto save\r\nbugfix: Fixing params sent to prettier CLI \r\nbugfix: Fix bug where default prettier plugin installation path was never used","3":"feature: Adding support for Async formatting  and making it default for auto save\r\nbugfix: Fixing params sent to prettier CLI \r\nbugfix: Fix bug where default prettier plugin installation path was never used","package":"vim-prettier-0.0.3.zip","4":"vim-prettier-0.0.3.zip","src_id":"25269","5":"25269","creation_date":"1495954933","6":"1495954933"},{"0":"5572","vim_version":"8.0","1":"8.0","script_version":"0.0.2","2":"0.0.2","version_comment":"bugfix: Should not overwrite buffer when prettier fails to parse file","3":"bugfix: Should not overwrite buffer when prettier fails to parse file","package":"vim-prettier-0.0.2.zip","4":"vim-prettier-0.0.2.zip","src_id":"25256","5":"25256","creation_date":"1495758139","6":"1495758139"},{"0":"5572","vim_version":"8.0","1":"8.0","script_version":"0.0.1","2":"0.0.1","version_comment":"Initial upload","3":"Initial upload","package":"vim-prettier-0.0.1.zip","4":"vim-prettier-0.0.1.zip","src_id":"25255","5":"25255","creation_date":"1495739548","6":"1495739548"}]},"5571":{"script_id":"5571","0":"5571","script_name":"remaining-todos","1":"remaining-todos","script_type":"utility","2":"utility","summary":"There are remaining TODOs in this file!","3":"There are remaining TODOs in this file!","description":"Github repository: https:\/\/github.com\/Marrakchino\/remaining-todos.vim\r\n\r\nThis vim script warns the user that there are a certain number (specified in the sentence) of \"TODO\" marks when leaving the file.\r\nThe message is echoed on the status line during 250ms just before closing the buffer (configurable).\r\n\r\n","4":"Github repository: https:\/\/github.com\/Marrakchino\/remaining-todos.vim\r\n\r\nThis vim script warns the user that there are a certain number (specified in the sentence) of \"TODO\" marks when leaving the file.\r\nThe message is echoed on the status line during 250ms just before closing the buffer (configurable).\r\n\r\n","install_details":"Simply put the file in ~\/.vim\/plugin or any equivalent directory.","5":"Simply put the file in ~\/.vim\/plugin or any equivalent directory.","first_name":"Nabil","6":"Nabil","last_name":"Elqatib","7":"Elqatib","releases":[{"0":"5571","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"remaining-todos.vim","4":"remaining-todos.vim","src_id":"25240","5":"25240","creation_date":"1495648023","6":"1495648023"}]},"5570":{"script_id":"5570","0":"5570","script_name":"quickEditTab","1":"quickEditTab","script_type":"utility","2":"utility","summary":"A new command to open files in the same or another tab.","3":"A new command to open files in the same or another tab.","description":"`QuickEditTab` provides a new command, `QuickEditTabPage`, to open files in the same or another tab according to a predefined file list.  Two global variables, `g:path2FileList_quickEditTab` and `g:path2Placeholder_quickEditTab`, are added to store plugin settings.  The plugin requires Vim 8.0 or higher.\r\n\r\nGit repository:\r\n\r\nhttps:\/\/github.com\/Bozar\/quickEditTab","4":"`QuickEditTab` provides a new command, `QuickEditTabPage`, to open files in the same or another tab according to a predefined file list.  Two global variables, `g:path2FileList_quickEditTab` and `g:path2Placeholder_quickEditTab`, are added to store plugin settings.  The plugin requires Vim 8.0 or higher.\r\n\r\nGit repository:\r\n\r\nhttps:\/\/github.com\/Bozar\/quickEditTab","install_details":"","5":"","first_name":"Tommy","6":"Tommy","last_name":"Chen","7":"Chen","releases":[{"0":"5570","vim_version":"8.0","1":"8.0","script_version":"1.0.0","2":"1.0.0","version_comment":"Initial upload","3":"Initial upload","package":"quickEditTab-1.0.0.zip","4":"quickEditTab-1.0.0.zip","src_id":"25225","5":"25225","creation_date":"1495512057","6":"1495512057"}]},"5569":{"script_id":"5569","0":"5569","script_name":"botlang-syntax","1":"botlang-syntax","script_type":"syntax","2":"syntax","summary":"Botlang support for vim","3":"Botlang support for vim","description":"Adds syntax highlighting and snippets to Botlang files (*.bot, *.botlang) in vim.\r\n\r\nVisit https:\/\/botlang.org\/ for further information.","4":"Adds syntax highlighting and snippets to Botlang files (*.bot, *.botlang) in vim.\r\n\r\nVisit https:\/\/botlang.org\/ for further information.","install_details":"Place botlang.vim file in ~\/.vim\/syntax\/ folder. ","5":"Place botlang.vim file in ~\/.vim\/syntax\/ folder. ","first_name":"Mathias","6":"Mathias","last_name":"Schilling","7":"Schilling","releases":[{"0":"5569","vim_version":"7.0","1":"7.0","script_version":"1.0.0","2":"1.0.0","version_comment":"Initial upload","3":"Initial upload","package":"botlang.vim","4":"botlang.vim","src_id":"25222","5":"25222","creation_date":"1495303369","6":"1495303369"}]},"5568":{"script_id":"5568","0":"5568","script_name":"vim-transit","1":"vim-transit","script_type":"utility","2":"utility","summary":"Translates a given text from source language to target language via Google Trans","3":"Translates a given text from source language to target language via Google Trans","description":"vim-transit translates a given text from source language to target language via Google Translate API.\r\n\r\nfor more information, check out git repository https:\/\/github.com\/makerj\/vim-transit\/blob\/master\/README.md","4":"vim-transit translates a given text from source language to target language via Google Translate API.\r\n\r\nfor more information, check out git repository https:\/\/github.com\/makerj\/vim-transit\/blob\/master\/README.md","install_details":"source vim-transit.vim","5":"source vim-transit.vim","first_name":"junhee","6":"junhee","last_name":"lee","7":"lee","releases":[{"0":"5568","vim_version":"7.4","1":"7.4","script_version":"20170519","2":"20170519","version_comment":"Initial upload","3":"Initial upload","package":"vim-transit.vim","4":"vim-transit.vim","src_id":"25218","5":"25218","creation_date":"1495173874","6":"1495173874"}]},"5567":{"script_id":"5567","0":"5567","script_name":"bal.vim","1":"bal.vim","script_type":"syntax","2":"syntax","summary":"Provides ballerina support to vim, when coupled with the bal ft script.","3":"Provides ballerina support to vim, when coupled with the bal ft script.","description":"Ballerina is a general purpose, concurrent and strongly typed programming language with both textual and graphical syntaxes birthed with the internet and integration in mind. \r\n\r\nFind out more about Ballerina here: http:\/\/ballerinalang.org\/. \r\n\r\nContribute to the ballerina vim plugin through: https:\/\/github.com\/ballerinalang\/plugin-vim\/tree\/master\/","4":"Ballerina is a general purpose, concurrent and strongly typed programming language with both textual and graphical syntaxes birthed with the internet and integration in mind. \r\n\r\nFind out more about Ballerina here: http:\/\/ballerinalang.org\/. \r\n\r\nContribute to the ballerina vim plugin through: https:\/\/github.com\/ballerinalang\/plugin-vim\/tree\/master\/","install_details":"Installation\r\n\r\n1. Download the ballerina ft script. \r\n2. Go to your home directory & locate .vim folder. \r\n3. Create folders ftdetect and syntax if they don\u00e2\u0080\u0099t exist. \r\n4. Copy the ballerina ft script and syntax scripts into the corresponding folders.","5":"Installation\r\n\r\n1. Download the ballerina ft script. \r\n2. Go to your home directory & locate .vim folder. \r\n3. Create folders ftdetect and syntax if they don\u00e2\u0080\u0099t exist. \r\n4. Copy the ballerina ft script and syntax scripts into the corresponding folders.","first_name":"Dumidu","6":"Dumidu","last_name":"Handakumbura","7":"Handakumbura","releases":[{"0":"5567","vim_version":"7.0","1":"7.0","script_version":"0.8","2":"0.8","version_comment":"Initial upload","3":"Initial upload","package":"bal.vim","4":"bal.vim","src_id":"25209","5":"25209","creation_date":"1494907334","6":"1494907334"}]},"5566":{"script_id":"5566","0":"5566","script_name":"tiny-todo","1":"tiny-todo","script_type":"utility","2":"utility","summary":"A simple todo list.","3":"A simple todo list.","description":"Overview:\r\n\r\nA simple todo-list with a possibility for time tracking.\r\n\r\nUsage:\r\n\r\nThe script registers the filetype tiny-todo associated with files with the\r\npostfix todo. An example of a todo file:\r\n\r\n\r\n* Project 1\r\n\r\n- task 1\r\n\r\n* Project 2\r\n\r\n- task 2\r\n\r\n* Archive \r\n\r\n- completed task\r\n+active 20161207133819\r\n+inactive 20161207133824\r\n+completed 20161207133825 (Project 2)\r\n\r\n\r\nLines beginning with a star indicate the name of the project. Inside each project, \r\nadd new tasks with french lines. It is recommended that you add an archive\r\nas the last project because completed tasks are moved to the end of the file.\r\n\r\nThe following functions are provided in the filetype plugin:\r\n\r\ng:TTodoStartWorking     -  Mark a task as active\r\ng:TTodoStopWorking     -  Mark a task as inactive\r\ng:TTodoCompleteTask   -  Mark a task as completed (moves the task to the end of the file)\r\ng:TTodoAddAnnotation  -  Add extra information to the task. This may be useful for adding additional \r\n                                          timestamped information for an external parser\/analyzer of your tasks.\r\n\r\nAn example configuration in .vimrc:\r\n\r\nautocmd Filetype tiny-todo nnore tta :call g:TTodoStartWorking()\r\nautocmd Filetype tiny-todo nnore tti :call g:TTodoStopWorking()\r\nautocmd Filetype tiny-todo nnore ttc :call g:TTodoCompleteTask()\r\n\r\nIn order to keep track of time spent, you may write a script to parse the archived tasks.","4":"Overview:\r\n\r\nA simple todo-list with a possibility for time tracking.\r\n\r\nUsage:\r\n\r\nThe script registers the filetype tiny-todo associated with files with the\r\npostfix todo. An example of a todo file:\r\n\r\n\r\n* Project 1\r\n\r\n- task 1\r\n\r\n* Project 2\r\n\r\n- task 2\r\n\r\n* Archive \r\n\r\n- completed task\r\n+active 20161207133819\r\n+inactive 20161207133824\r\n+completed 20161207133825 (Project 2)\r\n\r\n\r\nLines beginning with a star indicate the name of the project. Inside each project, \r\nadd new tasks with french lines. It is recommended that you add an archive\r\nas the last project because completed tasks are moved to the end of the file.\r\n\r\nThe following functions are provided in the filetype plugin:\r\n\r\ng:TTodoStartWorking     -  Mark a task as active\r\ng:TTodoStopWorking     -  Mark a task as inactive\r\ng:TTodoCompleteTask   -  Mark a task as completed (moves the task to the end of the file)\r\ng:TTodoAddAnnotation  -  Add extra information to the task. This may be useful for adding additional \r\n                                          timestamped information for an external parser\/analyzer of your tasks.\r\n\r\nAn example configuration in .vimrc:\r\n\r\nautocmd Filetype tiny-todo nnore tta :call g:TTodoStartWorking()\r\nautocmd Filetype tiny-todo nnore tti :call g:TTodoStopWorking()\r\nautocmd Filetype tiny-todo nnore ttc :call g:TTodoCompleteTask()\r\n\r\nIn order to keep track of time spent, you may write a script to parse the archived tasks.","install_details":"Untar the package in your .vim directory.","5":"Untar the package in your .vim directory.","first_name":"","6":"","last_name":"","7":"","releases":[{"0":"5566","vim_version":"7.0","1":"7.0","script_version":"0.8","2":"0.8","version_comment":"Add ftdetect file.","3":"Add ftdetect file.","package":"tiny-todo.tar","4":"tiny-todo.tar","src_id":"26928","5":"26928","creation_date":"1579483020","6":"1579483020"}]},"5565":{"script_id":"5565","0":"5565","script_name":"rst-robotframework-syntax-vim","1":"rst-robotframework-syntax-vim","script_type":"syntax","2":"syntax","summary":"Extends RST syntax to highlight Robot Framework code snippets","3":"Extends RST syntax to highlight Robot Framework code snippets","description":"This syntax file extends the RST syntax file to support embedded Robot Framework code.\r\n\r\nTo contribute, leave messages, or open issues, visit https:\/\/github.com\/evedovelli\/rst-robotframework-syntax-vim","4":"This syntax file extends the RST syntax file to support embedded Robot Framework code.\r\n\r\nTo contribute, leave messages, or open issues, visit https:\/\/github.com\/evedovelli\/rst-robotframework-syntax-vim","install_details":"Install via pathogen:\r\n- cd ~\/.vim\/bundle\r\n- git clone https:\/\/github.com\/shmargum\/vim-sass-colors.git\r\n\r\nUse vim-plug as:\r\n- Plug 'evedovelli\/rst-robotframework-syntax-vim'\r\n\r\nOr install the repository manually:\r\n- git clone git:\/\/github.com\/evedovelli\/rst-robotframework-syntax-vim.git\r\n- cd rst-robotframework-syntax-vim && cp -R * ~\/.vim\/\r\n\r\nOr download the zip file and uncompress it inside ~\/.vim\/","5":"Install via pathogen:\r\n- cd ~\/.vim\/bundle\r\n- git clone https:\/\/github.com\/shmargum\/vim-sass-colors.git\r\n\r\nUse vim-plug as:\r\n- Plug 'evedovelli\/rst-robotframework-syntax-vim'\r\n\r\nOr install the repository manually:\r\n- git clone git:\/\/github.com\/evedovelli\/rst-robotframework-syntax-vim.git\r\n- cd rst-robotframework-syntax-vim && cp -R * ~\/.vim\/\r\n\r\nOr download the zip file and uncompress it inside ~\/.vim\/","first_name":"Estevan","6":"Estevan","last_name":"Vedovelli","7":"Vedovelli","releases":[{"0":"5565","vim_version":"7.0","1":"7.0","script_version":"0.0.1","2":"0.0.1","version_comment":"Initial upload","3":"Initial upload","package":"rst-robotframework-syntax-vim.zip","4":"rst-robotframework-syntax-vim.zip","src_id":"25194","5":"25194","creation_date":"1494519772","6":"1494519772"}]},"5564":{"script_id":"5564","0":"5564","script_name":"opensips.vim","1":"opensips.vim","script_type":"syntax","2":"syntax","summary":"Syntax highlighting for OpenSIPS script","3":"Syntax highlighting for OpenSIPS script","description":"Written for OpenSIPS 2.x, but will behave decently with older versions as well.\r\n\r\nFeatures:\r\n\r\n* global param validation\r\n* keyword validation\r\n* multi-line strings and comments\r\n* variable highlighting\r\n* transformation highlighting","4":"Written for OpenSIPS 2.x, but will behave decently with older versions as well.\r\n\r\nFeatures:\r\n\r\n* global param validation\r\n* keyword validation\r\n* multi-line strings and comments\r\n* variable highlighting\r\n* transformation highlighting","install_details":"* Place \"opensips.vim\" in ~\/.vim\/syntax\/opensips.vim\r\n\r\n* Enable auto filetype detection in your ~\/.vimrc with the following two lines (edit the last one as per your taste):\r\n\r\nset filetype=on\r\nau BufNewFile,BufRead *.{cfg,os,osips,opensips},*opensips*.m4 set filetype=opensips","5":"* Place \"opensips.vim\" in ~\/.vim\/syntax\/opensips.vim\r\n\r\n* Enable auto filetype detection in your ~\/.vimrc with the following two lines (edit the last one as per your taste):\r\n\r\nset filetype=on\r\nau BufNewFile,BufRead *.{cfg,os,osips,opensips},*opensips*.m4 set filetype=opensips","first_name":"Liviu","6":"Liviu","last_name":"Chircu","7":"Chircu","releases":[{"0":"5564","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"opensips.vim","4":"opensips.vim","src_id":"25192","5":"25192","creation_date":"1494447178","6":"1494447178"}]},"5563":{"script_id":"5563","0":"5563","script_name":"vim-game-snake","1":"vim-game-snake","script_type":"game","2":"game","summary":"snake game","3":"snake game","description":"==============================================================================\r\nHow to start\r\n\r\n    \" game start\r\n    :VimGameSnake\r\n\r\n==============================================================================\r\nHow to play \r\n\r\n    key | Details\r\n    ----|------------\r\n    h   | ←\r\n    j   | ↓\r\n    k   | ↑\r\n    l   | →\r\n    c   | end game\r\n    q   | quit game\r\n\r\ngithub repository : https:\/\/github.com\/johngrib\/vim-game-snake","4":"==============================================================================\r\nHow to start\r\n\r\n    \" game start\r\n    :VimGameSnake\r\n\r\n==============================================================================\r\nHow to play \r\n\r\n    key | Details\r\n    ----|------------\r\n    h   | ←\r\n    j   | ↓\r\n    k   | ↑\r\n    l   | →\r\n    c   | end game\r\n    q   | quit game\r\n\r\ngithub repository : https:\/\/github.com\/johngrib\/vim-game-snake","install_details":"Copy all files or plugin directory into your Vim runtimepath, like $HOME\/.vim or $VIM\/vimfiles.","5":"Copy all files or plugin directory into your Vim runtimepath, like $HOME\/.vim or $VIM\/vimfiles.","first_name":"JohnGrib","6":"JohnGrib","last_name":"Lee","7":"Lee","releases":[{"0":"5563","vim_version":"8.0","1":"8.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"vim-game-snake-0.1.zip","4":"vim-game-snake-0.1.zip","src_id":"25188","5":"25188","creation_date":"1494398438","6":"1494398438"}]},"5562":{"script_id":"5562","0":"5562","script_name":"bal.vim","1":"bal.vim","script_type":"ftplugin","2":"ftplugin","summary":"Provides ballerina support to vim, when coupled with the bal syntax plugin. ","3":"Provides ballerina support to vim, when coupled with the bal syntax plugin. ","description":"Ballerina is a general purpose, concurrent and strongly typed programming language with both textual and graphical syntaxes birthed with the internet and integration in mind. \r\n\r\nFind out more about Ballerina here: \"http:\/\/ballerinalang.org\/\\\". \r\n\r\nContribute to the ballerina vim plugin through: \"https:\/\/github.com\/ballerinalang\/plugin-vim\/tree\/master\/\\\"","4":"Ballerina is a general purpose, concurrent and strongly typed programming language with both textual and graphical syntaxes birthed with the internet and integration in mind. \r\n\r\nFind out more about Ballerina here: \"http:\/\/ballerinalang.org\/\\\". \r\n\r\nContribute to the ballerina vim plugin through: \"https:\/\/github.com\/ballerinalang\/plugin-vim\/tree\/master\/\\\"","install_details":"1. Download the ballerina syntax plugin\r\n2. Go to your home directory & locate .vim folder\r\n3. Create folders ftdetect and syntax if they don\u00e2\u0080\u0099t exist.\r\n4. Copy the ballerina ft script and syntax scripts into the corresponding folders. ","5":"1. Download the ballerina syntax plugin\r\n2. Go to your home directory & locate .vim folder\r\n3. Create folders ftdetect and syntax if they don\u00e2\u0080\u0099t exist.\r\n4. Copy the ballerina ft script and syntax scripts into the corresponding folders. ","first_name":"Dumidu","6":"Dumidu","last_name":"Handakumbura","7":"Handakumbura","releases":[{"0":"5562","vim_version":"7.4","1":"7.4","script_version":"0.8","2":"0.8","version_comment":"Initial upload","3":"Initial upload","package":"bal.vim","4":"bal.vim","src_id":"25162","5":"25162","creation_date":"1494221465","6":"1494221465"}]},"5560":{"script_id":"5560","0":"5560","script_name":"VIM MySQL Suggestions","1":"VIM MySQL Suggestions","script_type":"utility","2":"utility","summary":"A plugin of VIM to show suggestions from MySQL database structure.","3":"A plugin of VIM to show suggestions from MySQL database structure.","description":"A plugin of VIM to show suggestions from MySQL database structure. \r\nDetailed info and demo: https:\/\/github.com\/borissov\/vim-mysql-suggestions","4":"A plugin of VIM to show suggestions from MySQL database structure. \r\nDetailed info and demo: https:\/\/github.com\/borissov\/vim-mysql-suggestions","install_details":"Via Plugin Mnager\r\n    -Vundle\r\n        Plugin 'borissov\/vim-mysql-suggestions'\r\n\r\n    -VIM Plug\r\n        Plug 'borissov\/vim-mysql-suggestions'\r\n\r\nManual Installation\r\n    cd ~\/.vim\/bundle\r\n    git clone git:\/\/github.com\/borissov\/vim-mysql-suggestions","5":"Via Plugin Mnager\r\n    -Vundle\r\n        Plugin 'borissov\/vim-mysql-suggestions'\r\n\r\n    -VIM Plug\r\n        Plug 'borissov\/vim-mysql-suggestions'\r\n\r\nManual Installation\r\n    cd ~\/.vim\/bundle\r\n    git clone git:\/\/github.com\/borissov\/vim-mysql-suggestions","first_name":"Radoslav","6":"Radoslav","last_name":"Borissov","7":"Borissov","releases":[{"0":"5560","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial release tar.gz version.","3":"Initial release tar.gz version.","package":"vim-mysql-suggestions-1.0.tar.gz","4":"vim-mysql-suggestions-1.0.tar.gz","src_id":"25131","5":"25131","creation_date":"1493922710","6":"1493922710"},{"0":"5560","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial release zip version.","3":"Initial release zip version.","package":"vim-mysql-suggestions-1.0.zip","4":"vim-mysql-suggestions-1.0.zip","src_id":"25130","5":"25130","creation_date":"1493922680","6":"1493922680"}]},"5559":{"script_id":"5559","0":"5559","script_name":"vim-yaml-folds","1":"vim-yaml-folds","script_type":"ftplugin","2":"ftplugin","summary":"Folding rules for YAML, RAML and SaltStack SLS files","3":"Folding rules for YAML, RAML and SaltStack SLS files","description":"Very simple folding configuration for YAML, RAML and SaltStack SLS files.  For more details and screenshots, please read my blog post:\r\n\r\n  - https:\/\/droun.in\/posts\/programming\/yaml_vim_folds\/\r\n\r\nSource can be found at:\r\n\r\n  - https:\/\/github.com\/digitalrounin\/vim-yaml-folds\r\n\r\n","4":"Very simple folding configuration for YAML, RAML and SaltStack SLS files.  For more details and screenshots, please read my blog post:\r\n\r\n  - https:\/\/droun.in\/posts\/programming\/yaml_vim_folds\/\r\n\r\nSource can be found at:\r\n\r\n  - https:\/\/github.com\/digitalrounin\/vim-yaml-folds\r\n\r\n","install_details":"Install using either Pathogen, Vundle, or similar.","5":"Install using either Pathogen, Vundle, or similar.","first_name":"Pedro","6":"Pedro","last_name":"H.","7":"H.","releases":[{"0":"5559","vim_version":"8.0","1":"8.0","script_version":"0.0.1","2":"0.0.1","version_comment":"Added RAML support, updated README. MIGHT work on Vim 7.0.","3":"Added RAML support, updated README. MIGHT work on Vim 7.0.","package":"vim-yaml-folds-0.0.1.zip","4":"vim-yaml-folds-0.0.1.zip","src_id":"25273","5":"25273","creation_date":"1496220597","6":"1496220597"},{"0":"5559","vim_version":"8.0","1":"8.0","script_version":"0.0","2":"0.0","version_comment":"Initial upload","3":"Initial upload","package":"vim-yaml-folds-0.0.zip","4":"vim-yaml-folds-0.0.zip","src_id":"25122","5":"25122","creation_date":"1493881899","6":"1493881899"}]},"5558":{"script_id":"5558","0":"5558","script_name":"vim-sass-colors","1":"vim-sass-colors","script_type":"utility","2":"utility","summary":"sass\/scss\/less\/css color variable highlighting (works with imports)","3":"sass\/scss\/less\/css color variable highlighting (works with imports)","description":"vim plugin that highlights sass\/scss\/less\/css colors and color variables\r\nit also recursively imports color variables\r\nhttps:\/\/github.com\/shmargum\/vim-sass-colors","4":"vim plugin that highlights sass\/scss\/less\/css colors and color variables\r\nit also recursively imports color variables\r\nhttps:\/\/github.com\/shmargum\/vim-sass-colors","install_details":"Install via pathogen\r\n\r\ncd ~\/.vim\/bundle\r\ngit clone https:\/\/github.com\/shmargum\/vim-sass-colors.git","5":"Install via pathogen\r\n\r\ncd ~\/.vim\/bundle\r\ngit clone https:\/\/github.com\/shmargum\/vim-sass-colors.git","first_name":"Maxim","6":"Maxim","last_name":"Ivanov","7":"Ivanov","releases":[{"0":"5558","vim_version":"7.0","1":"7.0","script_version":"1.0.1","2":"1.0.1","version_comment":"Run plugin on less and css filetypes","3":"Run plugin on less and css filetypes","package":"vim-sass-colors-1.0.1.tar.gz","4":"vim-sass-colors-1.0.1.tar.gz","src_id":"27122","5":"27122","creation_date":"1587226443","6":"1587226443"},{"0":"5558","vim_version":"7.0","1":"7.0","script_version":"1.0.0","2":"1.0.0","version_comment":"Add support foor 3 digit hex, hsl(a), and regular css colors.\r\nAdd support for configurable automatic import files and folders.","3":"Add support foor 3 digit hex, hsl(a), and regular css colors.\r\nAdd support for configurable automatic import files and folders.","package":"vim-sass-colors-1.0.0.tar.gz","4":"vim-sass-colors-1.0.0.tar.gz","src_id":"27121","5":"27121","creation_date":"1587225707","6":"1587225707"},{"0":"5558","vim_version":"7.0","1":"7.0","script_version":"0.7.2","2":"0.7.2","version_comment":"Add more default style folders.\r\nAdditionally checks if current file is in a \/style\/ or \/styles\/ directory for more robust default color importing support.","3":"Add more default style folders.\r\nAdditionally checks if current file is in a \/style\/ or \/styles\/ directory for more robust default color importing support.","package":"vim-sass-colors.tar.gz","4":"vim-sass-colors.tar.gz","src_id":"26131","5":"26131","creation_date":"1531445605","6":"1531445605"},{"0":"5558","vim_version":"7.0","1":"7.0","script_version":"0.7.1","2":"0.7.1","version_comment":"Handles creation of new windows without necessarily reading in a new file.","3":"Handles creation of new windows without necessarily reading in a new file.","package":"vim-sass-colors-0.7.1.zip","4":"vim-sass-colors-0.7.1.zip","src_id":"25715","5":"25715","creation_date":"1513375490","6":"1513375490"},{"0":"5558","vim_version":"7.0","1":"7.0","script_version":"0.7","2":"0.7","version_comment":"Restricts imports to match the file suffix. (only imports .scss files if you open a .scss file)\r\nResolves bug when import file matches other file name with wrong suffix","3":"Restricts imports to match the file suffix. (only imports .scss files if you open a .scss file)\r\nResolves bug when import file matches other file name with wrong suffix","package":"vim-sass-colors.zip","4":"vim-sass-colors.zip","src_id":"25708","5":"25708","creation_date":"1513034420","6":"1513034420"},{"0":"5558","vim_version":"7.0","1":"7.0","script_version":"0.6.5","2":"0.6.5","version_comment":"Add support for reading in new buffers.\r\nFix some issues when loading\/unloading buffers.","3":"Add support for reading in new buffers.\r\nFix some issues when loading\/unloading buffers.","package":"vim-sass-colors-0.6.5.zip","4":"vim-sass-colors-0.6.5.zip","src_id":"25335","5":"25335","creation_date":"1498260554","6":"1498260554"},{"0":"5558","vim_version":"7.0","1":"7.0","script_version":"0.6.4","2":"0.6.4","version_comment":"Fix for using with vim split","3":"Fix for using with vim split","package":"vim-sass-colors-0.6.4.zip","4":"vim-sass-colors-0.6.4.zip","src_id":"25313","5":"25313","creation_date":"1497483216","6":"1497483216"},{"0":"5558","vim_version":"7.0","1":"7.0","script_version":"0.6.3","2":"0.6.3","version_comment":"Fix interaction of plugin with other plugins using matchadd()\r\nFix typo to enhance performance when parsing color literals that are not assigned to a variable.","3":"Fix interaction of plugin with other plugins using matchadd()\r\nFix typo to enhance performance when parsing color literals that are not assigned to a variable.","package":"vim-sass-colors-0.6.3.zip","4":"vim-sass-colors-0.6.3.zip","src_id":"25305","5":"25305","creation_date":"1497279094","6":"1497279094"},{"0":"5558","vim_version":"7.0","1":"7.0","script_version":"0.6.2","2":"0.6.2","version_comment":"Enhance performance.  No more slow down after re-saving many times in a row.","3":"Enhance performance.  No more slow down after re-saving many times in a row.","package":"vim-sass-colors-0.6.2.zip","4":"vim-sass-colors-0.6.2.zip","src_id":"25299","5":"25299","creation_date":"1497058591","6":"1497058591"},{"0":"5558","vim_version":"7.0","1":"7.0","script_version":"0.6.1","2":"0.6.1","version_comment":"clean up imports","3":"clean up imports","package":"vim-sass-colors.zip","4":"vim-sass-colors.zip","src_id":"25183","5":"25183","creation_date":"1494355339","6":"1494355339"},{"0":"5558","vim_version":"7.0","1":"7.0","script_version":"0.6","2":"0.6","version_comment":"more robust importing","3":"more robust importing","package":"vim-sass-colors.zip","4":"vim-sass-colors.zip","src_id":"25164","5":"25164","creation_date":"1494267313","6":"1494267313"},{"0":"5558","vim_version":"7.0","1":"7.0","script_version":"0.5.1","2":"0.5.1","version_comment":"Updated documentation","3":"Updated documentation","package":"vim-sass-colors.zip","4":"vim-sass-colors.zip","src_id":"25140","5":"25140","creation_date":"1494097450","6":"1494097450"},{"0":"5558","vim_version":"7.0","1":"7.0","script_version":"0.5","2":"0.5","version_comment":"add support for rgba","3":"add support for rgba","package":"vim-sass-colors.zip","4":"vim-sass-colors.zip","src_id":"25135","5":"25135","creation_date":"1493935449","6":"1493935449"},{"0":"5558","vim_version":"7.0","1":"7.0","script_version":"0.4.1","2":"0.4.1","version_comment":"Initial upload","3":"Initial upload","package":"vim-sass-colors.zip","4":"vim-sass-colors.zip","src_id":"25121","5":"25121","creation_date":"1493856018","6":"1493856018"}]},"5557":{"script_id":"5557","0":"5557","script_name":"auto_update_cscope_ctags_database","1":"auto_update_cscope_ctags_database","script_type":"ftplugin","2":"ftplugin","summary":"1:auto update cscope ctags database2:easy create database 3: auto plugn database","3":"1:auto update cscope ctags database2:easy create database 3: auto plugn database","description":"\r\ngithub link :    https:\/\/github.com\/haolongzhangm\/auto_update_cscope_ctags_database ","4":"\r\ngithub link :    https:\/\/github.com\/haolongzhangm\/auto_update_cscope_ctags_database ","install_details":"https:\/\/github.com\/haolongzhangm\/auto_update_cscope_ctags_database\/blob\/master\/README.md","5":"https:\/\/github.com\/haolongzhangm\/auto_update_cscope_ctags_database\/blob\/master\/README.md","first_name":"Hidin","6":"Hidin","last_name":"zhang","7":"zhang","releases":[{"0":"5557","vim_version":"8.0","1":"8.0","script_version":"a.0","2":"a.0","version_comment":"1:fix issue\r\n2:add more file type","3":"1:fix issue\r\n2:add more file type","package":"auto_update_cscope_ctags_database.tar.gz","4":"auto_update_cscope_ctags_database.tar.gz","src_id":"26823","5":"26823","creation_date":"1573582272","6":"1573582272"},{"0":"5557","vim_version":"7.0","1":"7.0","script_version":"v5","2":"v5","version_comment":"V5 release","3":"V5 release","package":"auto_update_cscope_ctags_database.tar.gz","4":"auto_update_cscope_ctags_database.tar.gz","src_id":"26236","5":"26236","creation_date":"1538061825","6":"1538061825"},{"0":"5557","vim_version":"7.0","1":"7.0","script_version":"v4.0.1","2":"v4.0.1","version_comment":"commit 2923a91f76d85244476b8e22564c0b0ce1cca0ee\r\nAuthor: haolong.zhang \r\nDate:   Wed May 2 10:19:46 2018 +0800\r\n\r\n    support MAC OS support\r\n    v4.0.1 release\r\n\r\ncommit 18b7049fd5c2b15cca3c75b54eac6fddd644f0ef\r\nAuthor: haolong.zhang \r\nDate:   Fri Apr 20 14:49:03 2018 +0800\r\n\r\n    Add support .cmake file\r\n\r\ncommit b357fe856099ed4a855950553e6ff1b81e56c191\r\nAuthor: haolong.zhang \r\nDate:   Mon Apr 2 18:02:47 2018 +0800\r\n\r\n    fix:\r\n        compat vim with python3, or vim support\r\n        both python2 and python3\r\n\r\ncommit f0350d88d9ce23113cc65eb27b9a6763c2d11403\r\nAuthor: haolong.zhang \r\nDate:   Sat Feb 24 17:09:36 2018 +0800\r\n\r\n    support cl file\r\n\r\n","3":"commit 2923a91f76d85244476b8e22564c0b0ce1cca0ee\r\nAuthor: haolong.zhang \r\nDate:   Wed May 2 10:19:46 2018 +0800\r\n\r\n    support MAC OS support\r\n    v4.0.1 release\r\n\r\ncommit 18b7049fd5c2b15cca3c75b54eac6fddd644f0ef\r\nAuthor: haolong.zhang \r\nDate:   Fri Apr 20 14:49:03 2018 +0800\r\n\r\n    Add support .cmake file\r\n\r\ncommit b357fe856099ed4a855950553e6ff1b81e56c191\r\nAuthor: haolong.zhang \r\nDate:   Mon Apr 2 18:02:47 2018 +0800\r\n\r\n    fix:\r\n        compat vim with python3, or vim support\r\n        both python2 and python3\r\n\r\ncommit f0350d88d9ce23113cc65eb27b9a6763c2d11403\r\nAuthor: haolong.zhang \r\nDate:   Sat Feb 24 17:09:36 2018 +0800\r\n\r\n    support cl file\r\n\r\n","package":"auto_update_cscope_ctags_database.tar.gz","4":"auto_update_cscope_ctags_database.tar.gz","src_id":"25960","5":"25960","creation_date":"1525376290","6":"1525376290"},{"0":"5557","vim_version":"7.0","1":"7.0","script_version":"v3.0.2","2":"v3.0.2","version_comment":"    optimize support python API logic\r\n    \r\n    U may choose support python API or not\r\n    when create 'not_kernel' project:\r\n    eg:\r\n        ...\r\n        ...\r\n        A not_kernel project will create\r\n    \r\n                Support soft link file or not? (while add -L to find commmand)\r\n                Yes: please input 'yes' to support soft link file, default 'NO'>>>\r\n                Customization disable soft link file\r\n    \r\n                Support python API or not? only take effect when project have python file\r\n                (if U care about python lib API, U may input yes)\r\n                Yes: please input 'yes' to support pythonlib API, default 'NO'>>>\r\n\r\n-------------------------------------------------------------------------------------------------------------\r\n    Fix Issue(Fuc imp)\r\n        do not call remove cscope database when leave from *.py\r\n        caused by python lib API dir do not include a database\r\n        when into python Lib dir ,we want to use old database\r\n    \r\n        will cause new 'issue' TODO:\r\n            when in python project, while do not support\r\n            diff project databse swith\r\n    \r\n        if U do not want to support python lib use old databse\r\n        U can remove 'au BufNewFile,BufEnter *.py let g:python_file=1'\r\n        from autoload_cscope_ctags.vim file\r\n","3":"    optimize support python API logic\r\n    \r\n    U may choose support python API or not\r\n    when create 'not_kernel' project:\r\n    eg:\r\n        ...\r\n        ...\r\n        A not_kernel project will create\r\n    \r\n                Support soft link file or not? (while add -L to find commmand)\r\n                Yes: please input 'yes' to support soft link file, default 'NO'>>>\r\n                Customization disable soft link file\r\n    \r\n                Support python API or not? only take effect when project have python file\r\n                (if U care about python lib API, U may input yes)\r\n                Yes: please input 'yes' to support pythonlib API, default 'NO'>>>\r\n\r\n-------------------------------------------------------------------------------------------------------------\r\n    Fix Issue(Fuc imp)\r\n        do not call remove cscope database when leave from *.py\r\n        caused by python lib API dir do not include a database\r\n        when into python Lib dir ,we want to use old database\r\n    \r\n        will cause new 'issue' TODO:\r\n            when in python project, while do not support\r\n            diff project databse swith\r\n    \r\n        if U do not want to support python lib use old databse\r\n        U can remove 'au BufNewFile,BufEnter *.py let g:python_file=1'\r\n        from autoload_cscope_ctags.vim file\r\n","package":"auto_update_cscope_ctags_database.tar.gz","4":"auto_update_cscope_ctags_database.tar.gz","src_id":"25522","5":"25522","creation_date":"1503395530","6":"1503395530"},{"0":"5557","vim_version":"7.0","1":"7.0","script_version":" v2.0.6","2":" v2.0.6","version_comment":"v2.0.6: 20170724 type file issue fix, care_file_type * include","3":"v2.0.6: 20170724 type file issue fix, care_file_type * include","package":"auto_update_cscope_ctags_database.tar.gz","4":"auto_update_cscope_ctags_database.tar.gz","src_id":"25442","5":"25442","creation_date":"1500881781","6":"1500881781"},{"0":"5557","vim_version":"7.0","1":"7.0","script_version":"1.0.1","2":"1.0.1","version_comment":"fix v1.0 issue","3":"fix v1.0 issue","package":"auto_update_cscope_ctags_database.tar.gz","4":"auto_update_cscope_ctags_database.tar.gz","src_id":"25198","5":"25198","creation_date":"1494578897","6":"1494578897"}]},"5555":{"script_id":"5555","0":"5555","script_name":"Multiplayer","1":"Multiplayer","script_type":"utility","2":"utility","summary":"Collaborative Editing","3":"Collaborative Editing","description":"This Vim plugin allows multiple players (users) to edit the same file at the\r\nsame time.\r\nInstall the plugin on one computer. Now all players should ssh into this\r\ncomputer. If a player opens a file that is already open by another player\r\n(there is a .swp-file), then that player is invited to join as multiplayer.\r\n(press 'M'). Users can also explicitly connect and disconnect.\r\nEach player can set some player specific options that are stored in a profile\r\nand loaded the next time that player enters vim.\r\nYou can read other players registers, so you can put (paste) what an other\r\nuser has yanked (copied).\r\nYou can also read other players ':'-register and '\/'-register, so you can\r\nre-use thier ex-commands and search patterns.\r\nYou can jump to an other players location (file, line, column) or to an\r\nother players last visual selection.\r\nYou can configure Multiplayer to follow other players in split windows if\r\nthey move out of your field of view. Either in the same file, or in to\r\nan other file.\r\n","4":"This Vim plugin allows multiple players (users) to edit the same file at the\r\nsame time.\r\nInstall the plugin on one computer. Now all players should ssh into this\r\ncomputer. If a player opens a file that is already open by another player\r\n(there is a .swp-file), then that player is invited to join as multiplayer.\r\n(press 'M'). Users can also explicitly connect and disconnect.\r\nEach player can set some player specific options that are stored in a profile\r\nand loaded the next time that player enters vim.\r\nYou can read other players registers, so you can put (paste) what an other\r\nuser has yanked (copied).\r\nYou can also read other players ':'-register and '\/'-register, so you can\r\nre-use thier ex-commands and search patterns.\r\nYou can jump to an other players location (file, line, column) or to an\r\nother players last visual selection.\r\nYou can configure Multiplayer to follow other players in split windows if\r\nthey move out of your field of view. Either in the same file, or in to\r\nan other file.\r\n","install_details":"Use Vundle or other Pathogen compatible package manager","5":"Use Vundle or other Pathogen compatible package manager","first_name":"Rolf","6":"Rolf","last_name":"Asmund","7":"Asmund","releases":[{"0":"5555","vim_version":"8.0","1":"8.0","script_version":"0.9","2":"0.9","version_comment":"Initial upload","3":"Initial upload","package":"multiplayer.vim.tar","4":"multiplayer.vim.tar","src_id":"25094","5":"25094","creation_date":"1493460765","6":"1493460765"}]},"5554":{"script_id":"5554","0":"5554","script_name":"SumOfSelection","1":"SumOfSelection","script_type":"utility","2":"utility","summary":"Calculate sum of visual (block) selected numbers","3":"Calculate sum of visual (block) selected numbers","description":"This plugin sums up a visual (block) selection of numbers and echoes the result. \r\n\r\nArithmetic operators: ^ ** * % \/ - + (). Math functions: sqrt, log, log2, log10,\r\nexp, abs, sin, cos, tan, base. Hex numbers start with 0x, and binary numbers\r\nwith 0b. \r\n\r\nMath functions can be abbreviated to the first letter of the function name,\r\nexcept r=sqrt, l2=log2, l10=log10. \r\n\r\nWithout an operator the addition sign is added between numbers. Characters not a\r\nnumber, operator or math function are ignored, as well as any character between\r\nbrackets to support commenting. \r\n\r\nAfter visual (block) selection press 't' to echo the sum on the command line. In\r\ninsert mode press Alt-= to insert the value of the last expression found on the\r\ncurrent line. \r\n\r\nIf you want to use other keys to calculate the sum, please add the following to\r\nyour .vimrc, and replace  with the desired key sequence: \r\n\r\n    vmap  SumOfSelectionLastSelection\r\n    imap  SumOfSelectionLastExpression\r\n\r\nThe number of decimals can be configured by adding:\r\n\r\n    let g:sumofselection_nrofdecimals = [Nr of decimals]\r\n\r\nA negative number means full precision. The default value is 2 decimal places.\r\nThe rounding method is set to 'common' (i.e. half round up).\r\n\r\nThe result is stored in the unnamed register \"\" and register \"0.  You can paste\r\nthe result in normal mode with p or \"0p. And in insert mode with 0. The sum\r\nis stored in register \"s.\r\n\r\nExample usage in insert mode:\r\n\r\n              2^10 = [ Press Alt-= ]\r\nResult:  2^10 = 1024\r\n              2^10 = 1024 \/ 8 = [ Press Alt-= ]\r\nResult:  2^10 = 1024 \/ 8 = 128\r\n\r\nExample of possible sums for visual block selection:\r\n\r\n           (10          12 * 5.5     12.52\r\n            20          25 * 2.5     17.59\r\n            30)*2     32 * 4.5     15.45\r\n\r\nShorthand:\r\n\r\n           r144 \/ r16  =  sqrt(144) \/ sqrt(16)\r\n           l2               =  log(2)\r\n           l2 0x400   =  log2(0x400)\r\n           b1966,62  = Vi\r\n           b2^10,16  = 0x400\r\n           b0xf,2       = 0b1111\r\n\r\nPlease note that due to regex restrictions brackets can't be used inside the\r\nargument to log2 and log10 e.g. l2(r(64)) != l2(r64).\r\n\r\nLinks:\r\n\r\nUsing vim as calculator http:\/\/vim.wikia.com\/wiki\/VimTip73\r\nVimCalc interactive calculator vimscript#3329\r\nHowMuch : A Vim calculator for visual selections vimscript#4761\r\nScientific Calculator http:\/\/vim.wikia.com\/wiki\/VimTip1235\r\nCrunch : An easier way to perform calculations inside Vim vimscript#4686\r\n","4":"This plugin sums up a visual (block) selection of numbers and echoes the result. \r\n\r\nArithmetic operators: ^ ** * % \/ - + (). Math functions: sqrt, log, log2, log10,\r\nexp, abs, sin, cos, tan, base. Hex numbers start with 0x, and binary numbers\r\nwith 0b. \r\n\r\nMath functions can be abbreviated to the first letter of the function name,\r\nexcept r=sqrt, l2=log2, l10=log10. \r\n\r\nWithout an operator the addition sign is added between numbers. Characters not a\r\nnumber, operator or math function are ignored, as well as any character between\r\nbrackets to support commenting. \r\n\r\nAfter visual (block) selection press 't' to echo the sum on the command line. In\r\ninsert mode press Alt-= to insert the value of the last expression found on the\r\ncurrent line. \r\n\r\nIf you want to use other keys to calculate the sum, please add the following to\r\nyour .vimrc, and replace  with the desired key sequence: \r\n\r\n    vmap  SumOfSelectionLastSelection\r\n    imap  SumOfSelectionLastExpression\r\n\r\nThe number of decimals can be configured by adding:\r\n\r\n    let g:sumofselection_nrofdecimals = [Nr of decimals]\r\n\r\nA negative number means full precision. The default value is 2 decimal places.\r\nThe rounding method is set to 'common' (i.e. half round up).\r\n\r\nThe result is stored in the unnamed register \"\" and register \"0.  You can paste\r\nthe result in normal mode with p or \"0p. And in insert mode with 0. The sum\r\nis stored in register \"s.\r\n\r\nExample usage in insert mode:\r\n\r\n              2^10 = [ Press Alt-= ]\r\nResult:  2^10 = 1024\r\n              2^10 = 1024 \/ 8 = [ Press Alt-= ]\r\nResult:  2^10 = 1024 \/ 8 = 128\r\n\r\nExample of possible sums for visual block selection:\r\n\r\n           (10          12 * 5.5     12.52\r\n            20          25 * 2.5     17.59\r\n            30)*2     32 * 4.5     15.45\r\n\r\nShorthand:\r\n\r\n           r144 \/ r16  =  sqrt(144) \/ sqrt(16)\r\n           l2               =  log(2)\r\n           l2 0x400   =  log2(0x400)\r\n           b1966,62  = Vi\r\n           b2^10,16  = 0x400\r\n           b0xf,2       = 0b1111\r\n\r\nPlease note that due to regex restrictions brackets can't be used inside the\r\nargument to log2 and log10 e.g. l2(r(64)) != l2(r64).\r\n\r\nLinks:\r\n\r\nUsing vim as calculator http:\/\/vim.wikia.com\/wiki\/VimTip73\r\nVimCalc interactive calculator vimscript#3329\r\nHowMuch : A Vim calculator for visual selections vimscript#4761\r\nScientific Calculator http:\/\/vim.wikia.com\/wiki\/VimTip1235\r\nCrunch : An easier way to perform calculations inside Vim vimscript#4686\r\n","install_details":"Copy script file into Vim's plugin directory.\r\nPlugin requires Vim to be compiled with the +perl feature.","5":"Copy script file into Vim's plugin directory.\r\nPlugin requires Vim to be compiled with the +perl feature.","first_name":"Ivo","6":"Ivo","last_name":"van Kamp","7":"van Kamp","releases":[{"0":"5554","vim_version":"7.0","1":"7.0","script_version":"1.16","2":"1.16","version_comment":"- Added base[decimal\/hex\/bin, base n] function \r\n- Refactoring","3":"- Added base[decimal\/hex\/bin, base n] function \r\n- Refactoring","package":"SumOfSelection-1.16.vim","4":"SumOfSelection-1.16.vim","src_id":"25356","5":"25356","creation_date":"1498500104","6":"1498500104"},{"0":"5554","vim_version":"7.0","1":"7.0","script_version":"1.15","2":"1.15","version_comment":"Small regex bugfix","3":"Small regex bugfix","package":"SumOfSelection-1.15.vim","4":"SumOfSelection-1.15.vim","src_id":"25300","5":"25300","creation_date":"1497093723","6":"1497093723"},{"0":"5554","vim_version":"7.0","1":"7.0","script_version":"1.14","2":"1.14","version_comment":"- Added support for basic math functions: sqrt, log, log2, log10, exp, abs, sin, cos, tan \r\n- Added support for hex strings with 0x, and binary strings with 0b","3":"- Added support for basic math functions: sqrt, log, log2, log10, exp, abs, sin, cos, tan \r\n- Added support for hex strings with 0x, and binary strings with 0b","package":"SumOfSelection-1.14.vim","4":"SumOfSelection-1.14.vim","src_id":"25264","5":"25264","creation_date":"1495831906","6":"1495831906"},{"0":"5554","vim_version":"7.0","1":"7.0","script_version":"1.13","2":"1.13","version_comment":"Small regex bugfixes + refactoring","3":"Small regex bugfixes + refactoring","package":"SumOfSelection-1.13.vim","4":"SumOfSelection-1.13.vim","src_id":"25216","5":"25216","creation_date":"1495121144","6":"1495121144"},{"0":"5554","vim_version":"7.0","1":"7.0","script_version":"1.12","2":"1.12","version_comment":"- Regex refactoring \r\n- Improved error handling","3":"- Regex refactoring \r\n- Improved error handling","package":"SumOfSelection-1.12.vim","4":"SumOfSelection-1.12.vim","src_id":"25196","5":"25196","creation_date":"1494542876","6":"1494542876"},{"0":"5554","vim_version":"7.0","1":"7.0","script_version":"1.11","2":"1.11","version_comment":"- Refactoring \r\n- Added support for inline comments","3":"- Refactoring \r\n- Added support for inline comments","package":"SumOfSelection-1.11.vim","4":"SumOfSelection-1.11.vim","src_id":"25179","5":"25179","creation_date":"1494321248","6":"1494321248"},{"0":"5554","vim_version":"7.0","1":"7.0","script_version":"1.10","2":"1.10","version_comment":"- Improved code efficiency \r\n- Added configuration option to set nr of decimal places","3":"- Improved code efficiency \r\n- Added configuration option to set nr of decimal places","package":"SumOfSelection-1.10.vim","4":"SumOfSelection-1.10.vim","src_id":"25160","5":"25160","creation_date":"1494192372","6":"1494192372"},{"0":"5554","vim_version":"7.0","1":"7.0","script_version":"1.9","2":"1.9","version_comment":"- Added function to find the first equation in front of the cursor after an equality sign \r\n- Added plugin support \r\n- Refactoring, small bugfixes and improvements","3":"- Added function to find the first equation in front of the cursor after an equality sign \r\n- Added plugin support \r\n- Refactoring, small bugfixes and improvements","package":"SumOfSelection-1.9.vim","4":"SumOfSelection-1.9.vim","src_id":"25133","5":"25133","creation_date":"1493928106","6":"1493928106"},{"0":"5554","vim_version":"7.0","1":"7.0","script_version":"1.8","2":"1.8","version_comment":"Refactoring + small bugfixes","3":"Refactoring + small bugfixes","package":"SumOfSelection-1.8.vim","4":"SumOfSelection-1.8.vim","src_id":"25115","5":"25115","creation_date":"1493661202","6":"1493661202"},{"0":"5554","vim_version":"7.0","1":"7.0","script_version":"1.7","2":"1.7","version_comment":"- Added support for parenthesis\r\n- After calculation the result can now be pasted","3":"- Added support for parenthesis\r\n- After calculation the result can now be pasted","package":"SumOfSelection-1.7.vim","4":"SumOfSelection-1.7.vim","src_id":"25104","5":"25104","creation_date":"1493549952","6":"1493549952"},{"0":"5554","vim_version":"7.0","1":"7.0","script_version":"1.6","2":"1.6","version_comment":"Added support for arithmetic operators","3":"Added support for arithmetic operators","package":"SumOfSelection-1.6.vim","4":"SumOfSelection-1.6.vim","src_id":"25099","5":"25099","creation_date":"1493495983","6":"1493495983"},{"0":"5554","vim_version":"7.0","1":"7.0","script_version":"1.5","2":"1.5","version_comment":"Added constant to configure nr of decimals","3":"Added constant to configure nr of decimals","package":"SumOfSelection-1.5.vim","4":"SumOfSelection-1.5.vim","src_id":"25097","5":"25097","creation_date":"1493495540","6":"1493495540"},{"0":"5554","vim_version":"7.0","1":"7.0","script_version":"1.4","2":"1.4","version_comment":"Initial upload","3":"Initial upload","package":"SumOfSelection-1.4.vim","4":"SumOfSelection-1.4.vim","src_id":"25093","5":"25093","creation_date":"1493404201","6":"1493404201"}]},"5553":{"script_id":"5553","0":"5553","script_name":"vim-daps","1":"vim-daps","script_type":"utility","2":"utility","summary":"Adds daps (https:\/\/opensuse.github.io\/daps) functionality to the Vim text editor","3":"Adds daps (https:\/\/opensuse.github.io\/daps) functionality to the Vim text editor","description":"This plugin is a wrapper around daps (https:\/\/opensuse.github.io\/daps\/) functionality for the Vim text editor.\r\nSee its development at https:\/\/github.com\/tbazant\/vim-daps","4":"This plugin is a wrapper around daps (https:\/\/opensuse.github.io\/daps\/) functionality for the Vim text editor.\r\nSee its development at https:\/\/github.com\/tbazant\/vim-daps","install_details":"","5":"","first_name":"Tom\u00c3\u00a1\u00c5\u00a1","6":"Tom\u00c3\u00a1\u00c5\u00a1","last_name":"Ba\u00c5\u00beant","7":"Ba\u00c5\u00beant","releases":[{"0":"5553","vim_version":"7.0","1":"7.0","script_version":"0.3.0","2":"0.3.0","version_comment":"- added new 'dobook45.vim', 'docbook50', and 'geekodoc5' XML dictionaries\r\n- added :DapsValidateFile for listing validation errors in a quickfix window\r\n- added :DapsSetDoctype for choosing between DB40\/50\/GeekoDoc5\r\n- added missing documentation\r\n- added this CHANGELOG","3":"- added new 'dobook45.vim', 'docbook50', and 'geekodoc5' XML dictionaries\r\n- added :DapsValidateFile for listing validation errors in a quickfix window\r\n- added :DapsSetDoctype for choosing between DB40\/50\/GeekoDoc5\r\n- added missing documentation\r\n- added this CHANGELOG","package":"vim-daps-0.3.0.tar.gz","4":"vim-daps-0.3.0.tar.gz","src_id":"25674","5":"25674","creation_date":"1512050201","6":"1512050201"},{"0":"5553","vim_version":"7.0","1":"7.0","script_version":"0.1.0","2":"0.1.0","version_comment":"When you place a cursor on a line with id=\"...\", then only the selected snippet will be built. Note that the deepest element supported is .","3":"When you place a cursor on a line with id=\"...\", then only the selected snippet will be built. Note that the deepest element supported is .","package":"vim-daps-0.1.0.tar.gz","4":"vim-daps-0.1.0.tar.gz","src_id":"25123","5":"25123","creation_date":"1493887190","6":"1493887190"},{"0":"5553","vim_version":"7.0","1":"7.0","script_version":"0.0.1","2":"0.0.1","version_comment":"Initial upload","3":"Initial upload","package":"vim-daps-0.0.1.tar.gz","4":"vim-daps-0.0.1.tar.gz","src_id":"25092","5":"25092","creation_date":"1493282502","6":"1493282502"}]},"5552":{"script_id":"5552","0":"5552","script_name":"foldtext","1":"foldtext","script_type":"ftplugin","2":"ftplugin","summary":"Folding support for some filetypes that don't do so by default","3":"Folding support for some filetypes that don't do so by default","description":"This plugin provides `folding` support for filetypes that don't do so by default:\r\n\r\n- markdown, pandoc\r\n- viki\r\n- LaTeX\r\n- org mode\r\n- mediawiki\r\n\r\nIt is assumed that a file with one of these filetypes contains a few heading \r\nand many lines of text in between.\r\n","4":"This plugin provides `folding` support for filetypes that don't do so by default:\r\n\r\n- markdown, pandoc\r\n- viki\r\n- LaTeX\r\n- org mode\r\n- mediawiki\r\n\r\nIt is assumed that a file with one of these filetypes contains a few heading \r\nand many lines of text in between.\r\n","install_details":"Either use the zip archive:\r\n\r\n- Download the zip archive\r\n- Extract it to ~\/.vim\/pack\/tml\/start\/foldtext_vim\r\n\r\nor install from github:\r\n\r\n- Start a terminal\r\n- Change the working directory to ~\/.vim\/pack\/tml\/start\/\r\n- Type: git clone https:\/\/github.com\/tomtom\/foldtext_vim\r\n\r\nNOTE: On Windows, ~\/.vim might be ~\/vimfiles. Please see 'runtimepath' for \r\ndetails.\r\n","5":"Either use the zip archive:\r\n\r\n- Download the zip archive\r\n- Extract it to ~\/.vim\/pack\/tml\/start\/foldtext_vim\r\n\r\nor install from github:\r\n\r\n- Start a terminal\r\n- Change the working directory to ~\/.vim\/pack\/tml\/start\/\r\n- Type: git clone https:\/\/github.com\/tomtom\/foldtext_vim\r\n\r\nNOTE: On Windows, ~\/.vim might be ~\/vimfiles. Please see 'runtimepath' for \r\ndetails.\r\n","first_name":"Tom","6":"Tom","last_name":"Link","7":"Link","releases":[{"0":"5552","vim_version":"8.0","1":"8.0","script_version":"0.01","2":"0.01","version_comment":"Initial upload","3":"Initial upload","package":"foldtext.zip","4":"foldtext.zip","src_id":"25085","5":"25085","creation_date":"1492762577","6":"1492762577"}]},"5551":{"script_id":"5551","0":"5551","script_name":"vikibase","1":"vikibase","script_type":"syntax","2":"syntax","summary":"A slimmed-down version of the viki plugin: a personal wiki","3":"A slimmed-down version of the viki plugin: a personal wiki","description":"This plugin provides a slimmed-down |ftplugin| (with respect to the original \r\nviki[0] vimscript #861) with support for syntax highlighting, indentation, and \r\nfolding.\r\n\r\nSome features are delegated to other plugins. Support for hyperlinking is \r\nprovided by the autolinker plugin[1]. Support for folding by the foldtext \r\nplugin[2].\r\n\r\nThe deplate[3] converter (written in ruby 1.8) can be used to convert viki \r\nmarkup to LaTeX, HTML, or DocBook. On its homepage (http:\/\/deplate.sf.net) you \r\ncan also find a more detailed specification of the viki markup.\r\n\r\n[0] https:\/\/github.com\/tomtom\/viki_vim\r\n[1] https:\/\/github.com\/tomtom\/autolinker_vim\r\n[2] https:\/\/github.com\/tomtom\/foldtext_vim\r\n[3] http:\/\/sourceforge.net\/projects\/deplate\/\r\n","4":"This plugin provides a slimmed-down |ftplugin| (with respect to the original \r\nviki[0] vimscript #861) with support for syntax highlighting, indentation, and \r\nfolding.\r\n\r\nSome features are delegated to other plugins. Support for hyperlinking is \r\nprovided by the autolinker plugin[1]. Support for folding by the foldtext \r\nplugin[2].\r\n\r\nThe deplate[3] converter (written in ruby 1.8) can be used to convert viki \r\nmarkup to LaTeX, HTML, or DocBook. On its homepage (http:\/\/deplate.sf.net) you \r\ncan also find a more detailed specification of the viki markup.\r\n\r\n[0] https:\/\/github.com\/tomtom\/viki_vim\r\n[1] https:\/\/github.com\/tomtom\/autolinker_vim\r\n[2] https:\/\/github.com\/tomtom\/foldtext_vim\r\n[3] http:\/\/sourceforge.net\/projects\/deplate\/\r\n","install_details":"Either use the zip archive:\r\n    - Download the zip archive\r\n    - Extract it to ~\/.vim\/pack\/tml\/start\/vikibase_vim\r\n\r\nor install from github:\r\n    - Start a terminal\r\n    - Change the working directory to ~\/.vim\/pack\/tml\/start\/\r\n    - Type: git clone https:\/\/github.com\/tomtom\/vikibase_vim\r\n\r\nNOTE: On Windows, ~\/.vim might be ~\/vimfiles. Please see 'runtimepath' for \r\ndetails.\r\n\r\n\r\nRequirements~\r\n\r\nThis script requires tlib (vimscript #1863) to be installed -- see \r\nhttps:\/\/github.com\/tomtom\/tlib_vim.\r\n\r\n\r\nOptional enhancements~\r\n- vikitasks (vimscript #2894): Distributed TODO lists (discontinued plugin)\r\n- vxfold (vimscript #3004): Provides org-mode like fold cycling\r\n- VOoM (vimscript #2657): A two-pane outliner with support for viki\r\n\r\n\r\nPost-Install~\r\n\r\nViki requires the following minimal lines to be added to |vimrc|: >\r\n\r\n    :set nocompatible\r\n    :filetype plugin indent on\r\n    :syntax on\r\n","5":"Either use the zip archive:\r\n    - Download the zip archive\r\n    - Extract it to ~\/.vim\/pack\/tml\/start\/vikibase_vim\r\n\r\nor install from github:\r\n    - Start a terminal\r\n    - Change the working directory to ~\/.vim\/pack\/tml\/start\/\r\n    - Type: git clone https:\/\/github.com\/tomtom\/vikibase_vim\r\n\r\nNOTE: On Windows, ~\/.vim might be ~\/vimfiles. Please see 'runtimepath' for \r\ndetails.\r\n\r\n\r\nRequirements~\r\n\r\nThis script requires tlib (vimscript #1863) to be installed -- see \r\nhttps:\/\/github.com\/tomtom\/tlib_vim.\r\n\r\n\r\nOptional enhancements~\r\n- vikitasks (vimscript #2894): Distributed TODO lists (discontinued plugin)\r\n- vxfold (vimscript #3004): Provides org-mode like fold cycling\r\n- VOoM (vimscript #2657): A two-pane outliner with support for viki\r\n\r\n\r\nPost-Install~\r\n\r\nViki requires the following minimal lines to be added to |vimrc|: >\r\n\r\n    :set nocompatible\r\n    :filetype plugin indent on\r\n    :syntax on\r\n","first_name":"Tom","6":"Tom","last_name":"Link","7":"Link","releases":[{"0":"5551","vim_version":"8.0","1":"8.0","script_version":"5.00","2":"5.00","version_comment":"Initial upload","3":"Initial upload","package":"vikibase.zip","4":"vikibase.zip","src_id":"25084","5":"25084","creation_date":"1492762037","6":"1492762037"}]},"5550":{"script_id":"5550","0":"5550","script_name":"autoproject","1":"autoproject","script_type":"utility","2":"utility","summary":"Set buffer-local options, the working directory etc. specific to a project","3":"Set buffer-local options, the working directory etc. specific to a project","description":"In most IDEs users have to manually set up a list of projects. The goal of this \r\nplugin is to semi-automatically maintain such a list of projects and corresponding \r\nsessions.\r\n\r\nProjects are defined by their root directory. A project directory is detected \r\nwhen creating a buffer or reading a file into a buffer by searching for certain \r\nfiles that typically define a project, like Makefile, setup.py etc. -- see \r\n|g:autoproject#cd#markers| for a full list. If no such a marker is found, the \r\nbuffer's directory is used.\r\n\r\nIf the detection of the project's root directory goes wrong, users can use \r\n|:Autoprojectregister| to define a directory as a root directory. Such custom \r\nroot directories will be reused when opening the respective file again.\r\n\r\nAfter the working directory is determined, it checks whether there is a file \r\n`project.vim` or `.autoproject\/buffer.vim` (see also \r\n|g:autoproject#projectrc#buffer_conig|). If the file exists, it gets loaded. This \r\nfile typically sets project-related settings and variables, i.e., you have to \r\nuse |:setlocal| (instead of :set) and use buffer-local |b:| variables.\r\n\r\nThe autoproject plugin keeps track of projects so that you can switch back to a \r\nproject later on (see |:Autoprojectselect|). It also provides support for \r\ncreating sessions (see |:Autoprojectmksession|) that will automatically be \r\nloaded when entering the respective project.\r\n\r\nFeatures:~\r\n\r\n- Detect a file's project root directory (see |g:autoproject#cd#markers|).\r\n- Load a project-specific vim configuration file (see \r\n  |g:autoproject#projectrc#buffer_conig|).\r\n- Maintain a list of projects (i.e. project root directories). Use \r\n  |:Autoprojectregister| to register an arbitrary directory. Use \r\n  |:Autoprojectselect| to quickly open a file in a previously opened project. \r\n  When a project is selected this way, the file `.autoproject\/global.vim` (see \r\n  |g:autoproject#projectrc#global_config|) is loaded if it exists.\r\n- Maintain project-specific sessions that were created with \r\n  |:Autoprojectmksession| (see also |g:autoproject_enable_sessions| and \r\n  |:Autoprojectleavesession|).\r\n\r\nHow to use this plugin:~\r\n\r\n- Load a file ... done\r\n    - Report wrongly detected project directories to the plugin author\r\n- Use |:Autoprojectselect| to switch to a project.\r\n- Optionally, use |:Autoprojectmksession| to create a session for the current \r\n  project. Don't forget to use |:Autoprojectleavesession| to save changes to \r\n  the session file when you're done.\r\n","4":"In most IDEs users have to manually set up a list of projects. The goal of this \r\nplugin is to semi-automatically maintain such a list of projects and corresponding \r\nsessions.\r\n\r\nProjects are defined by their root directory. A project directory is detected \r\nwhen creating a buffer or reading a file into a buffer by searching for certain \r\nfiles that typically define a project, like Makefile, setup.py etc. -- see \r\n|g:autoproject#cd#markers| for a full list. If no such a marker is found, the \r\nbuffer's directory is used.\r\n\r\nIf the detection of the project's root directory goes wrong, users can use \r\n|:Autoprojectregister| to define a directory as a root directory. Such custom \r\nroot directories will be reused when opening the respective file again.\r\n\r\nAfter the working directory is determined, it checks whether there is a file \r\n`project.vim` or `.autoproject\/buffer.vim` (see also \r\n|g:autoproject#projectrc#buffer_conig|). If the file exists, it gets loaded. This \r\nfile typically sets project-related settings and variables, i.e., you have to \r\nuse |:setlocal| (instead of :set) and use buffer-local |b:| variables.\r\n\r\nThe autoproject plugin keeps track of projects so that you can switch back to a \r\nproject later on (see |:Autoprojectselect|). It also provides support for \r\ncreating sessions (see |:Autoprojectmksession|) that will automatically be \r\nloaded when entering the respective project.\r\n\r\nFeatures:~\r\n\r\n- Detect a file's project root directory (see |g:autoproject#cd#markers|).\r\n- Load a project-specific vim configuration file (see \r\n  |g:autoproject#projectrc#buffer_conig|).\r\n- Maintain a list of projects (i.e. project root directories). Use \r\n  |:Autoprojectregister| to register an arbitrary directory. Use \r\n  |:Autoprojectselect| to quickly open a file in a previously opened project. \r\n  When a project is selected this way, the file `.autoproject\/global.vim` (see \r\n  |g:autoproject#projectrc#global_config|) is loaded if it exists.\r\n- Maintain project-specific sessions that were created with \r\n  |:Autoprojectmksession| (see also |g:autoproject_enable_sessions| and \r\n  |:Autoprojectleavesession|).\r\n\r\nHow to use this plugin:~\r\n\r\n- Load a file ... done\r\n    - Report wrongly detected project directories to the plugin author\r\n- Use |:Autoprojectselect| to switch to a project.\r\n- Optionally, use |:Autoprojectmksession| to create a session for the current \r\n  project. Don't forget to use |:Autoprojectleavesession| to save changes to \r\n  the session file when you're done.\r\n","install_details":"Either use the zip archive:\r\n    - Download the zip archive\r\n    - Extract it to `~\/.vim\/pack\/tml\/start\/autoproject`\r\n\r\nor install from github:\r\n    - Start a terminal\r\n    - Change the working directory to `~\/.vim\/pack\/tml\/start\/`\r\n    - Type: `git clone https:\/\/github.com\/tomtom\/autoproject_vim`\r\n\r\nNOTE: If you don't want to run this plugin on startup, use \r\n`~\/.vim\/pack\/tml\/opt\/`.\r\n\r\nNOTE: On Windows, ~\/.vim might be ~\/vimfiles. Please see 'runtimepath' for \r\ndetails.\r\n\r\n\r\nRequirements~\r\n\r\nThis script requires tlib (vimscript #1863) to be installed -- see \r\nhttps:\/\/github.com\/tomtom\/tlib_vim.\r\n","5":"Either use the zip archive:\r\n    - Download the zip archive\r\n    - Extract it to `~\/.vim\/pack\/tml\/start\/autoproject`\r\n\r\nor install from github:\r\n    - Start a terminal\r\n    - Change the working directory to `~\/.vim\/pack\/tml\/start\/`\r\n    - Type: `git clone https:\/\/github.com\/tomtom\/autoproject_vim`\r\n\r\nNOTE: If you don't want to run this plugin on startup, use \r\n`~\/.vim\/pack\/tml\/opt\/`.\r\n\r\nNOTE: On Windows, ~\/.vim might be ~\/vimfiles. Please see 'runtimepath' for \r\ndetails.\r\n\r\n\r\nRequirements~\r\n\r\nThis script requires tlib (vimscript #1863) to be installed -- see \r\nhttps:\/\/github.com\/tomtom\/tlib_vim.\r\n","first_name":"Tom","6":"Tom","last_name":"Link","7":"Link","releases":[{"0":"5550","vim_version":"7.0","1":"7.0","script_version":"0.02","2":"0.02","version_comment":"- autoproject#cd#ChangeDir(): FIX properly handle fallback markers & home directory\n- On startup: Don't forget about the current buffer (opened from the command line)\n- Use the BufEnter event to set the cd\n- g:autoproject#projectrc#buffer_config: .project.vim and _project.vim replaces project.vim\n- Maps: properly escape filenames\nSHA256 checksum: c7d6b45462f66016eb4f8acac9725d645c4b0f28759cad81bf6bf980b1d5016a","3":"- autoproject#cd#ChangeDir(): FIX properly handle fallback markers & home directory\n- On startup: Don't forget about the current buffer (opened from the command line)\n- Use the BufEnter event to set the cd\n- g:autoproject#projectrc#buffer_config: .project.vim and _project.vim replaces project.vim\n- Maps: properly escape filenames\nSHA256 checksum: c7d6b45462f66016eb4f8acac9725d645c4b0f28759cad81bf6bf980b1d5016a","package":"autoproject.zip","4":"autoproject.zip","src_id":"25118","5":"25118","creation_date":"1493711101","6":"1493711101"},{"0":"5550","vim_version":"8.0","1":"8.0","script_version":"0.01","2":"0.01","version_comment":"Initial upload","3":"Initial upload","package":"autoproject.zip","4":"autoproject.zip","src_id":"25083","5":"25083","creation_date":"1492761238","6":"1492761238"}]},"5549":{"script_id":"5549","0":"5549","script_name":"tstatus","1":"tstatus","script_type":"utility","2":"utility","summary":"Monitor buffer-local options and variables in the statusline","3":"Monitor buffer-local options and variables in the statusline","description":"This plugin provides a still rather simple statusline manager to monitor \r\noptions and variables. If an option's or variable's value changes, it is \r\ndisplayed in the statusline.\r\n\r\nIn order to monitor options\/variables, either set |g:tstatus_names| in \r\n|vimrc| or call |:TStatusregister|.\r\n\r\nCall |:TStatus| to set or reset the status line or the ruler.\r\n","4":"This plugin provides a still rather simple statusline manager to monitor \r\noptions and variables. If an option's or variable's value changes, it is \r\ndisplayed in the statusline.\r\n\r\nIn order to monitor options\/variables, either set |g:tstatus_names| in \r\n|vimrc| or call |:TStatusregister|.\r\n\r\nCall |:TStatus| to set or reset the status line or the ruler.\r\n","install_details":"Install~\r\n\r\nEither use the zip archive:\r\n\r\n- Download the zip archive\r\n- Extract it to ~\/.vim\/pack\/tml\/start\/tstatus\r\n\r\nor install from github:\r\n\r\n- Start a terminal\r\n- Change the working directory to ~\/.vim\/pack\/tml\/start\/\r\n- Type: git clone https:\/\/github.com\/tomtom\/tstatus_vim\r\n\r\nNOTE: On Windows, ~\/.vim might be ~\/vimfiles. Please see 'runtimepath' for \r\ndetails.\r\n","5":"Install~\r\n\r\nEither use the zip archive:\r\n\r\n- Download the zip archive\r\n- Extract it to ~\/.vim\/pack\/tml\/start\/tstatus\r\n\r\nor install from github:\r\n\r\n- Start a terminal\r\n- Change the working directory to ~\/.vim\/pack\/tml\/start\/\r\n- Type: git clone https:\/\/github.com\/tomtom\/tstatus_vim\r\n\r\nNOTE: On Windows, ~\/.vim might be ~\/vimfiles. Please see 'runtimepath' for \r\ndetails.\r\n","first_name":"Tom","6":"Tom","last_name":"Link","7":"Link","releases":[{"0":"5549","vim_version":"8.0","1":"8.0","script_version":"0.02","2":"0.02","version_comment":"Initial upload","3":"Initial upload","package":"tstatus.zip","4":"tstatus.zip","src_id":"25082","5":"25082","creation_date":"1492761073","6":"1492761073"}]},"5548":{"script_id":"5548","0":"5548","script_name":"js_alternate","1":"js_alternate","script_type":"utility","2":"utility","summary":"A JavaScript plugin to easily navigate between alternate files","3":"A JavaScript plugin to easily navigate between alternate files","description":"Project https:\/\/github.com\/dunckr\/js_alternate.vim\r\n\r\nEasy navigation of a JavaScript directory structure. Inspired by the amazing vim-rails.\r\n\r\nThere is one command, `:A` (alternate) for easy jumping between a JavaScript source file and it\u00e2\u0080\u0099s corresponding test.\r\n\r\nUsage\r\n\r\n\t\" Switch between JavaScript source and it's test file\r\n\t:A\r\n\r\n\t\" Mapping to t\r\n\tnnoremap t :call js_alternate#run()\r\n\r\nExtend\r\n\r\n\tlet g:js_alternate#src_types = ['lib', 'src', 'app', 'scripts', 'js', 'javascript', 'frontend']\r\n\tlet g:js_alternate#test_types = ['tests', 'test', 'spec', 'features']\r\n\tlet g:js_alternate#extension_types = ['js', 'jsx', 'coffee', 'ts', 'elm', 'purs']\r\n","4":"Project https:\/\/github.com\/dunckr\/js_alternate.vim\r\n\r\nEasy navigation of a JavaScript directory structure. Inspired by the amazing vim-rails.\r\n\r\nThere is one command, `:A` (alternate) for easy jumping between a JavaScript source file and it\u00e2\u0080\u0099s corresponding test.\r\n\r\nUsage\r\n\r\n\t\" Switch between JavaScript source and it's test file\r\n\t:A\r\n\r\n\t\" Mapping to t\r\n\tnnoremap t :call js_alternate#run()\r\n\r\nExtend\r\n\r\n\tlet g:js_alternate#src_types = ['lib', 'src', 'app', 'scripts', 'js', 'javascript', 'frontend']\r\n\tlet g:js_alternate#test_types = ['tests', 'test', 'spec', 'features']\r\n\tlet g:js_alternate#extension_types = ['js', 'jsx', 'coffee', 'ts', 'elm', 'purs']\r\n","install_details":"Download zip, extract and put it in ~\/.vim\/autoload\/","5":"Download zip, extract and put it in ~\/.vim\/autoload\/","first_name":"Duncan","6":"Duncan","last_name":"Beaton","7":"Beaton","releases":[{"0":"5548","vim_version":"7.0","1":"7.0","script_version":"0.1.0","2":"0.1.0","version_comment":"Initial upload","3":"Initial upload","package":"js_alternate.vim-master.zip","4":"js_alternate.vim-master.zip","src_id":"25067","5":"25067","creation_date":"1491662283","6":"1491662283"}]},"5547":{"script_id":"5547","0":"5547","script_name":"vim-custom-surround","1":"vim-custom-surround","script_type":"utility","2":"utility","summary":" Define your own surround patterns ","3":" Define your own surround patterns ","description":"It's a simple plugin that lets you surround the word under cursor or the current selection with custom strings.\r\n\r\nTo use it, just call one of the mode-specific commands:\r\n\r\n    :SurroundWord  \r\n    :SurroundSelection  \r\n\r\nOr, even better, define a normal and visual mapping for the specified surround strings using the function customsurround#map. For example, to map a LaTeX inline math function just do:\r\n\r\n     call customsurround#map('m', '\\(', '\\)')\r\n\r\nSee the doc for more detailed explanations:\r\n\r\n     :h vim-custom-surround","4":"It's a simple plugin that lets you surround the word under cursor or the current selection with custom strings.\r\n\r\nTo use it, just call one of the mode-specific commands:\r\n\r\n    :SurroundWord  \r\n    :SurroundSelection  \r\n\r\nOr, even better, define a normal and visual mapping for the specified surround strings using the function customsurround#map. For example, to map a LaTeX inline math function just do:\r\n\r\n     call customsurround#map('m', '\\(', '\\)')\r\n\r\nSee the doc for more detailed explanations:\r\n\r\n     :h vim-custom-surround","install_details":"Use your prefered plugin manager. For Vundle, add\r\n\r\n    Plugin 'augustold\/vim-custom-surround'\r\n\r\nto your .vimrc.","5":"Use your prefered plugin manager. For Vundle, add\r\n\r\n    Plugin 'augustold\/vim-custom-surround'\r\n\r\nto your .vimrc.","first_name":"Augusto","6":"Augusto","last_name":"Dantas","7":"Dantas","releases":[{"0":"5547","vim_version":"7.0","1":"7.0","script_version":"1.1","2":"1.1","version_comment":"Make {strafter} parameter optional.","3":"Make {strafter} parameter optional.","package":"vim-custom-surround-1.1.tar.gz","4":"vim-custom-surround-1.1.tar.gz","src_id":"25072","5":"25072","creation_date":"1491932289","6":"1491932289"},{"0":"5547","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"vim-custom-surround-1.0.tar.gz","4":"vim-custom-surround-1.0.tar.gz","src_id":"25066","5":"25066","creation_date":"1491528726","6":"1491528726"}]},"5546":{"script_id":"5546","0":"5546","script_name":"goyo-doc","1":"goyo-doc","script_type":"utility","2":"utility","summary":"Vim","3":"Vim","description":"This is helpfile for goyo.vim plugin. The plugin goyo.vim helps writer to focus on their writing while they are writing. This plugin only contains a helpfile. For using the [goyo.vim] plugin, you have to install that plugin. The native plugin does not contain any kind of vim specific helpfile. Installing this plugin will allow you to play with the helpfile in your vim editor.\r\n\r\nHow to install?\r\n\r\nYou can use any of automated plugin installer such as vim-pathogen, Vundle etc.\r\n\r\nHow to use?\r\n\r\n:help goyo_doc.txt\r\n\r\nFAQ\r\n-------\r\n\r\nWhy to create new plugin for just helpfile?\r\n\r\nReading description of this Github issue will answer your this question.","4":"This is helpfile for goyo.vim plugin. The plugin goyo.vim helps writer to focus on their writing while they are writing. This plugin only contains a helpfile. For using the [goyo.vim] plugin, you have to install that plugin. The native plugin does not contain any kind of vim specific helpfile. Installing this plugin will allow you to play with the helpfile in your vim editor.\r\n\r\nHow to install?\r\n\r\nYou can use any of automated plugin installer such as vim-pathogen, Vundle etc.\r\n\r\nHow to use?\r\n\r\n:help goyo_doc.txt\r\n\r\nFAQ\r\n-------\r\n\r\nWhy to create new plugin for just helpfile?\r\n\r\nReading description of this Github issue will answer your this question.","install_details":"","5":"","first_name":"Jaysinh","6":"Jaysinh","last_name":"Shukla","7":"Shukla","releases":[{"0":"5546","vim_version":"7.0","1":"7.0","script_version":"0.0.1","2":"0.0.1","version_comment":"Initial upload","3":"Initial upload","package":"goyo-doc.zip","4":"goyo-doc.zip","src_id":"25059","5":"25059","creation_date":"1490910690","6":"1490910690"}]},"5545":{"script_id":"5545","0":"5545","script_name":"CurtineIncSw.vim","1":"CurtineIncSw.vim","script_type":"utility","2":"utility","summary":"Easily toggle between *.c* and *.h* buffers.","3":"Easily toggle between *.c* and *.h* buffers.","description":"Some assumptions: \r\n\r\n* The filenames of the header and body (implementation) are identical\r\nexcept for the extension or the directory.\r\n  - That is, foo.c -> foo.h is supported, \r\n  - whereas  foo.c -> bar.h is not supported.\r\n* The user opens files from the base of the repository. Or the other file is\r\n  somewhere within the directory of the file you are opening or it's\r\n  subdirectories.\r\n* The repository contains both the header and body (implementation) files.\r\n\r\nBased on these assumptions, you should not need to reconfigure when you switch \r\nbetween repositories.\r\n\r\nhttps:\/\/github.com\/ericcurtin\/CurtineIncSw.vim\r\n","4":"Some assumptions: \r\n\r\n* The filenames of the header and body (implementation) are identical\r\nexcept for the extension or the directory.\r\n  - That is, foo.c -> foo.h is supported, \r\n  - whereas  foo.c -> bar.h is not supported.\r\n* The user opens files from the base of the repository. Or the other file is\r\n  somewhere within the directory of the file you are opening or it's\r\n  subdirectories.\r\n* The repository contains both the header and body (implementation) files.\r\n\r\nBased on these assumptions, you should not need to reconfigure when you switch \r\nbetween repositories.\r\n\r\nhttps:\/\/github.com\/ericcurtin\/CurtineIncSw.vim\r\n","install_details":"## Installation\r\nCopy CurtineIncSw.vim into your ~\/.vim\/plugin directory.\r\nOr :source CurtineIncSw.vim to load it into your running session.\r\n\r\nYou can set a keyboard shortcut if you want by placing something like: \r\n\r\n  map \\ :call CurtineIncSw()\\\r\n\r\nin your ~\/.vimrc file.  Yes, the  is literally there at the end\r\nas the four characters shown.\r\n\r\nInstalling with Vundle\r\n\r\nAdd Plugin 'ericcurtin\/CurtineIncSw.vim' to your your plugin definitions\r\nin your .vimrc\r\n","5":"## Installation\r\nCopy CurtineIncSw.vim into your ~\/.vim\/plugin directory.\r\nOr :source CurtineIncSw.vim to load it into your running session.\r\n\r\nYou can set a keyboard shortcut if you want by placing something like: \r\n\r\n  map \\ :call CurtineIncSw()\\\r\n\r\nin your ~\/.vimrc file.  Yes, the  is literally there at the end\r\nas the four characters shown.\r\n\r\nInstalling with Vundle\r\n\r\nAdd Plugin 'ericcurtin\/CurtineIncSw.vim' to your your plugin definitions\r\nin your .vimrc\r\n","first_name":"Eric","6":"Eric","last_name":"Curtin","7":"Curtin","releases":[{"0":"5545","vim_version":"7.4","1":"7.4","script_version":"0.4","2":"0.4","version_comment":"Bugfixes from various contributors\r\n","3":"Bugfixes from various contributors\r\n","package":"CurtineIncSw.vim","4":"CurtineIncSw.vim","src_id":"27497","5":"27497","creation_date":"1614284342","6":"1614284342"},{"0":"5545","vim_version":"7.4","1":"7.4","script_version":"0.3","2":"0.3","version_comment":"Support inconsistent extensions. Also search recursively from path of opened file","3":"Support inconsistent extensions. Also search recursively from path of opened file","package":"CurtinIncSw.vim","4":"CurtinIncSw.vim","src_id":"25632","5":"25632","creation_date":"1509574625","6":"1509574625"},{"0":"5545","vim_version":"7.4","1":"7.4","script_version":"0.2","2":"0.2","version_comment":"Initial upload","3":"Initial upload","package":"CurtineIncSw.vim","4":"CurtineIncSw.vim","src_id":"25058","5":"25058","creation_date":"1490899415","6":"1490899415"}]},"5544":{"script_id":"5544","0":"5544","script_name":"vim-sourcer","1":"vim-sourcer","script_type":"utility","2":"utility","summary":"Several new commands for sourcing vimscript files","3":"Several new commands for sourcing vimscript files","description":"Adds commands :Source, :SourceDirs, :SourceBufs and :SourceWins to make the sourcing of vimscript files easier.\r\nGithub: https:\/\/github.com\/carlsmedstad\/vim-sourcer","4":"Adds commands :Source, :SourceDirs, :SourceBufs and :SourceWins to make the sourcing of vimscript files easier.\r\nGithub: https:\/\/github.com\/carlsmedstad\/vim-sourcer","install_details":"Unzip and place files in their respective folders.","5":"Unzip and place files in their respective folders.","first_name":"Carl","6":"Carl","last_name":"Smedstad","7":"Smedstad","releases":[{"0":"5544","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"vim-sourcer.zip","4":"vim-sourcer.zip","src_id":"25053","5":"25053","creation_date":"1490753466","6":"1490753466"}]},"5543":{"script_id":"5543","0":"5543","script_name":"eclipse-lite","1":"eclipse-lite","script_type":"color scheme","2":"color scheme","summary":"a vim scheme appears to eclipse","3":"a vim scheme appears to eclipse","description":"A vim scheme appears to eclipse, mainly for java.\r\nWork on GUI and\/or 256-color term. Not work on vim 5.80 or lower.","4":"A vim scheme appears to eclipse, mainly for java.\r\nWork on GUI and\/or 256-color term. Not work on vim 5.80 or lower.","install_details":"$ mkdir -p $HOME\/.vim\/colors\r\n$ cp vim\/colors\/eclipse-lite.vim $HOME\/.vim\/colors\/","5":"$ mkdir -p $HOME\/.vim\/colors\r\n$ cp vim\/colors\/eclipse-lite.vim $HOME\/.vim\/colors\/","first_name":"","6":"","last_name":"","7":"","releases":[{"0":"5543","vim_version":"6.0","1":"6.0","script_version":"1.0.1","2":"1.0.1","version_comment":"fix: incorrect keywords result in losting matched symbol","3":"fix: incorrect keywords result in losting matched symbol","package":"eclipse-lite.vim","4":"eclipse-lite.vim","src_id":"25065","5":"25065","creation_date":"1491467174","6":"1491467174"},{"0":"5543","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"eclipse-lite.vim","4":"eclipse-lite.vim","src_id":"25052","5":"25052","creation_date":"1490714816","6":"1490714816"}]},"5542":{"script_id":"5542","0":"5542","script_name":"note.vim","1":"note.vim","script_type":"syntax","2":"syntax","summary":"A syntax highlighting for general text notes","3":"A syntax highlighting for general text notes","description":"A syntax highlighting that works with plain text files. The only difference is that the filetype will need to set to be \".note\". You can decide what to highlight in your file instead of following preset keywords.\r\n\r\nDetails and screenshots can be viewed at:\r\nhttps:\/\/github.com\/Neur1n\/note.vim\r\n\r\nAnd any suggestion is welcomed!","4":"A syntax highlighting that works with plain text files. The only difference is that the filetype will need to set to be \".note\". You can decide what to highlight in your file instead of following preset keywords.\r\n\r\nDetails and screenshots can be viewed at:\r\nhttps:\/\/github.com\/Neur1n\/note.vim\r\n\r\nAnd any suggestion is welcomed!","install_details":"","5":"","first_name":"Jihang","6":"Jihang","last_name":"Li","7":"Li","releases":[{"0":"5542","vim_version":"7.0","1":"7.0","script_version":"1.0.0","2":"1.0.0","version_comment":"Initial upload","3":"Initial upload","package":"note.vim.zip","4":"note.vim.zip","src_id":"25050","5":"25050","creation_date":"1490649330","6":"1490649330"}]},"5541":{"script_id":"5541","0":"5541","script_name":"R4vim","1":"R4vim","script_type":"utility","2":"utility","summary":"Plugin to work with R scripts.","3":"Plugin to work with R scripts.","description":"# R4vim\r\n\r\nThis plugin was inspired by wanting the power of Vim for editing R scripts, while\r\nhaving the capability of running commands and code snippets in R.\r\n\r\n## Goals\r\n* Provide this functionality for Vim.\r\n* Simplicity. Send commands to R, display output in a buffer.\r\n\r\n## Dependencies\r\n* [R](https:\/\/cran.r-project.org\/)\r\n* [tmux](https:\/\/tmux.github.io\/)\r\n","4":"# R4vim\r\n\r\nThis plugin was inspired by wanting the power of Vim for editing R scripts, while\r\nhaving the capability of running commands and code snippets in R.\r\n\r\n## Goals\r\n* Provide this functionality for Vim.\r\n* Simplicity. Send commands to R, display output in a buffer.\r\n\r\n## Dependencies\r\n* [R](https:\/\/cran.r-project.org\/)\r\n* [tmux](https:\/\/tmux.github.io\/)\r\n","install_details":"It can be installed using Pathogen (vimscript #2332)","5":"It can be installed using Pathogen (vimscript #2332)","first_name":"Rene","6":"Rene","last_name":"Vergara","7":"Vergara","releases":[{"0":"5541","vim_version":"7.0","1":"7.0","script_version":"1.0.0","2":"1.0.0","version_comment":"Initial upload","3":"Initial upload","package":"R4vim.zip","4":"R4vim.zip","src_id":"25048","5":"25048","creation_date":"1490634925","6":"1490634925"}]},"5540":{"script_id":"5540","0":"5540","script_name":"vim-fileHeader","1":"vim-fileHeader","script_type":"utility","2":"utility","summary":"add information about source file at head of file","3":"add information about source file at head of file","description":"https:\/\/github.com\/pandapan0021\/vim-fileHeader.git","4":"https:\/\/github.com\/pandapan0021\/vim-fileHeader.git","install_details":"","5":"","first_name":"\u9ad8","6":"高","last_name":"\u6500","7":"攀","releases":[{"0":"5540","vim_version":"7.0","1":"7.0","script_version":"1.0.0","2":"1.0.0","version_comment":"Initial upload","3":"Initial upload","package":"vim-fileHeader.zip","4":"vim-fileHeader.zip","src_id":"25045","5":"25045","creation_date":"1490186400","6":"1490186400"}]},"5539":{"script_id":"5539","0":"5539","script_name":"GVFilter.vim","1":"GVFilter.vim","script_type":"utility","2":"utility","summary":"VIm plugin to filter current buffer by given arguments, like :g or :v","3":"VIm plugin to filter current buffer by given arguments, like :g or :v","description":"The plugin filters the current buffer so that only lines matching the given arguments remain in the file or all others, non-matching lines.\r\n\r\nIt is a wrapper for the global\/v commands, adding a bit more functionality like being able to repeat the last command executed, or starting a timer to continuously execute the last command.\r\n\r\nIt makes it easy for the user to assemble the global\/v command by defining commands for each and letting the user just enumerate the filter arguments. The executed VIm command is deletion.\r\n\r\nGeneral forms of the commands the plugin executes are:\r\n\r\n    :g\/pattern\/d\r\n\r\n    :v\/pattern\/d\r\n\r\n'pattern' can be a list of arguments in case more than one argument is passed to the plugin.\r\n\r\n:v\/arg1\\|arg2\\|arg3\/d\r\n\r\nIn this case only lines matching arg1 or arg2 or arg3 will be shown in the buffer and all the other lines deleted.\r\n\r\nGet the plugin from here on Github: https:\/\/github.com\/robcsi\/gvfilter.vim.git\r\n\r\nOther features include:\r\n\r\n    - The last command can be repeated by calling a command created specially for that purpose. The plugin remembers the last assembled command\r\n\r\n    - The user is also able to continuously filter the current buffer, by using two commands which use VIm's timer mechanisms. The _Start and _Stop commands facilitate this. This is very useful when wanting to filter growing files, like logs.\r\n\r\n    - The assembled command can be displayed for the user to see what has been executed.\r\n\r\nCheck the help file for more information: https:\/\/github.com\/robcsi\/gvfilter.vim\/blob\/master\/doc\/gvfilter.txt\r\nVersion\r\n\r\n0.1.0\r\nCopyright - 2016 - 2017\r\n\r\nRobert Sarkozi","4":"The plugin filters the current buffer so that only lines matching the given arguments remain in the file or all others, non-matching lines.\r\n\r\nIt is a wrapper for the global\/v commands, adding a bit more functionality like being able to repeat the last command executed, or starting a timer to continuously execute the last command.\r\n\r\nIt makes it easy for the user to assemble the global\/v command by defining commands for each and letting the user just enumerate the filter arguments. The executed VIm command is deletion.\r\n\r\nGeneral forms of the commands the plugin executes are:\r\n\r\n    :g\/pattern\/d\r\n\r\n    :v\/pattern\/d\r\n\r\n'pattern' can be a list of arguments in case more than one argument is passed to the plugin.\r\n\r\n:v\/arg1\\|arg2\\|arg3\/d\r\n\r\nIn this case only lines matching arg1 or arg2 or arg3 will be shown in the buffer and all the other lines deleted.\r\n\r\nGet the plugin from here on Github: https:\/\/github.com\/robcsi\/gvfilter.vim.git\r\n\r\nOther features include:\r\n\r\n    - The last command can be repeated by calling a command created specially for that purpose. The plugin remembers the last assembled command\r\n\r\n    - The user is also able to continuously filter the current buffer, by using two commands which use VIm's timer mechanisms. The _Start and _Stop commands facilitate this. This is very useful when wanting to filter growing files, like logs.\r\n\r\n    - The assembled command can be displayed for the user to see what has been executed.\r\n\r\nCheck the help file for more information: https:\/\/github.com\/robcsi\/gvfilter.vim\/blob\/master\/doc\/gvfilter.txt\r\nVersion\r\n\r\n0.1.0\r\nCopyright - 2016 - 2017\r\n\r\nRobert Sarkozi","install_details":"Install by using pathogen.","5":"Install by using pathogen.","first_name":"Robert","6":"Robert","last_name":"Sarkozi","7":"Sarkozi","releases":[{"0":"5539","vim_version":"7.4","1":"7.4","script_version":"0.1.0","2":"0.1.0","version_comment":"Initial upload","3":"Initial upload","package":"gvfilter.vim.zip","4":"gvfilter.vim.zip","src_id":"25039","5":"25039","creation_date":"1489834602","6":"1489834602"}]},"5538":{"script_id":"5538","0":"5538","script_name":"vnote","1":"vnote","script_type":"ftplugin","2":"ftplugin","summary":"A dairy or note edit and manage tool in vim","3":"A dairy or note edit and manage tool in vim","description":"GitHub repository: https:\/\/github.com\/lymslive\/vnote\r\n\r\n## Introduction\r\n\r\n* note is a markdown plain text file. while note public, diary private.\r\n* notebook is a directory to orginaze many note files in a way.\r\n* vnote is a plugin to edit note and manage notebook, almost in vim.\r\n\r\n## Dependent:\r\n\r\nmust install vimloo first\r\nhttps:\/\/github.com\/lymslive\/vimloo\r\nor http:\/\/www.vim.org\/scripts\/script.php?script_id=5537\r\n\r\n## Fast Usage\r\n\r\n* `:NoteNew` create a new note\r\n* `:NoteNew -` create a new diary\r\n* `:w` save note file as normal\r\n* `:NoteList` browse note in notebook\r\n* `:Unite notelist` is available if unite.vim installed\r\n* default notebook is `~\/notebook`\r\n* `:help vnote` for detail and online document","4":"GitHub repository: https:\/\/github.com\/lymslive\/vnote\r\n\r\n## Introduction\r\n\r\n* note is a markdown plain text file. while note public, diary private.\r\n* notebook is a directory to orginaze many note files in a way.\r\n* vnote is a plugin to edit note and manage notebook, almost in vim.\r\n\r\n## Dependent:\r\n\r\nmust install vimloo first\r\nhttps:\/\/github.com\/lymslive\/vimloo\r\nor http:\/\/www.vim.org\/scripts\/script.php?script_id=5537\r\n\r\n## Fast Usage\r\n\r\n* `:NoteNew` create a new note\r\n* `:NoteNew -` create a new diary\r\n* `:w` save note file as normal\r\n* `:NoteList` browse note in notebook\r\n* `:Unite notelist` is available if unite.vim installed\r\n* default notebook is `~\/notebook`\r\n* `:help vnote` for detail and online document","install_details":"$ mkdir -p ~\/.vim\/bundle\/vimloo \r\n$ cd ~\/.vim\/bundle\/vimloo \r\n$ tar xzvf vimloo.tgz\r\n\r\n$ mkdir -p ~\/.vim\/bundle\/vnote\r\n$ cd ~\/.vim\/bundle\/vnote\r\n$ tar xzvf vnote.tgz\r\n","5":"$ mkdir -p ~\/.vim\/bundle\/vimloo \r\n$ cd ~\/.vim\/bundle\/vimloo \r\n$ tar xzvf vimloo.tgz\r\n\r\n$ mkdir -p ~\/.vim\/bundle\/vnote\r\n$ cd ~\/.vim\/bundle\/vnote\r\n$ tar xzvf vnote.tgz\r\n","first_name":"Tan","6":"Tan","last_name":"Shuilong","7":"Shuilong","releases":[{"0":"5538","vim_version":"7.4","1":"7.4","script_version":"0.51","2":"0.51","version_comment":"Initial upload","3":"Initial upload","package":"vnote.tgz","4":"vnote.tgz","src_id":"25037","5":"25037","creation_date":"1489819471","6":"1489819471"}]},"5537":{"script_id":"5537","0":"5537","script_name":"vimloo","1":"vimloo","script_type":"utility","2":"utility","summary":"Write VimL Script in an Object Orient Style","3":"Write VimL Script in an Object Orient Style","description":"GitHub repository: https:\/\/github.com\/lymslive\/vimloo\r\n\r\n## Introduction\r\n\r\n* class is a dict variable defined in a script which under the autoload\r\n  subdirecotry, class name is the relative path to autoload.\r\n* object instance is a copy of class, may with modified data keys.\r\n* derived class is also a copy of base class, may add data or\/and function\r\n  keys.\r\n* module is a isolate class by itself with no child, parent nor even instance.\r\n\r\n## Functionality\r\n\r\n* base class design, providing many fundamental methods and functions.\r\n* module management, wich can import both standard classfied module and non-standard\r\n  modules.\r\n* template files to make it easy to create custome class and module.\r\n* some other smart commands used in script to help writting viml code in a more\r\n  pretty way.","4":"GitHub repository: https:\/\/github.com\/lymslive\/vimloo\r\n\r\n## Introduction\r\n\r\n* class is a dict variable defined in a script which under the autoload\r\n  subdirecotry, class name is the relative path to autoload.\r\n* object instance is a copy of class, may with modified data keys.\r\n* derived class is also a copy of base class, may add data or\/and function\r\n  keys.\r\n* module is a isolate class by itself with no child, parent nor even instance.\r\n\r\n## Functionality\r\n\r\n* base class design, providing many fundamental methods and functions.\r\n* module management, wich can import both standard classfied module and non-standard\r\n  modules.\r\n* template files to make it easy to create custome class and module.\r\n* some other smart commands used in script to help writting viml code in a more\r\n  pretty way.","install_details":"$ mkdir -p ~\/.vim\/bundle\/vimloo\r\n$ cd ~\/.vim\/bundle\/vimloo\r\n$ tar xzvf vimloo.tgz","5":"$ mkdir -p ~\/.vim\/bundle\/vimloo\r\n$ cd ~\/.vim\/bundle\/vimloo\r\n$ tar xzvf vimloo.tgz","first_name":"Tan","6":"Tan","last_name":"Shuilong","7":"Shuilong","releases":[{"0":"5537","vim_version":"7.4","1":"7.4","script_version":"0.51","2":"0.51","version_comment":"Initial upload","3":"Initial upload","package":"vimloo.tgz","4":"vimloo.tgz","src_id":"25036","5":"25036","creation_date":"1489818506","6":"1489818506"}]},"5536":{"script_id":"5536","0":"5536","script_name":"Agrep","1":"Agrep","script_type":"utility","2":"utility","summary":"Asynchronous grep plugin for Vim","3":"Asynchronous grep plugin for Vim","description":"* Designed for search - Vim's quickfix is great, but is not the best choice to use for searching. Agrep uses a simpler mechanism to manage the results and makes the list of matches very easy to read and navigate.\r\n\r\n* Fully asynchronous - Search is done in the background. There is no need to wait for the entire process to finish -the matches are displayed as they are found in the Agrep window and you can start exploring them immediately. You can keep working in Vim as usual while the search is active.\r\n\r\n* Fast and lightweight - Most likely the fastest search tool you can get in Vim, or in any other editor. Grep is fast, however, integrating it into other tools should be done carefully. Agrep is optimized to preserve the speed of grep and to keep Vim fully functional while search is running, even for massive searches with thousands of matches.\r\n\r\nhttp:\/\/i.imgur.com\/gW8q0Kk.gif\r\n\r\n*** Please check https:\/\/github.com\/ramele\/agrep for updates","4":"* Designed for search - Vim's quickfix is great, but is not the best choice to use for searching. Agrep uses a simpler mechanism to manage the results and makes the list of matches very easy to read and navigate.\r\n\r\n* Fully asynchronous - Search is done in the background. There is no need to wait for the entire process to finish -the matches are displayed as they are found in the Agrep window and you can start exploring them immediately. You can keep working in Vim as usual while the search is active.\r\n\r\n* Fast and lightweight - Most likely the fastest search tool you can get in Vim, or in any other editor. Grep is fast, however, integrating it into other tools should be done carefully. Agrep is optimized to preserve the speed of grep and to keep Vim fully functional while search is running, even for massive searches with thousands of matches.\r\n\r\nhttp:\/\/i.imgur.com\/gW8q0Kk.gif\r\n\r\n*** Please check https:\/\/github.com\/ramele\/agrep for updates","install_details":"","5":"","first_name":"Ramel","6":"Ramel","last_name":"Eshed","7":"Eshed","releases":[{"0":"5536","vim_version":"8.0","1":"8.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"agrep.rar","4":"agrep.rar","src_id":"25025","5":"25025","creation_date":"1489185241","6":"1489185241"}]},"5535":{"script_id":"5535","0":"5535","script_name":"bargreybars.vim","1":"bargreybars.vim","script_type":"utility","2":"utility","summary":"remove gray bars from maximised gvim windows, on Windows ","3":"remove gray bars from maximised gvim windows, on Windows ","description":"# bargreybars.vim\r\n\r\nThis plugin is stored at https:\/\/github.com\/dreadnaut\/vim-bargreybars\r\n\r\nGvim windows have a grey as default background color, behind the text area. When a window is maximised and its dimensions stop being a multiple of the font size, the grey background shows as bars on the right and bottom side of the windows.\r\n\r\nThis plugin keeps the windows background in sync with the background of your color scheme, calling an external library that modifies the window attributes. Source code for the library is included in the dll directory.\r\n\r\nGrey bars gone, the world is safe again!\r\n\r\nNote: the plugin works only on Windows. GTK-based Vim can be tweaked in a different way, and an issue exists in the vim issue tracker:\r\n\r\n  https:\/\/github.com\/vim\/vim\/issues\/349\r\n  http:\/\/pastebin.com\/N0G333nP\r\n\r\n## Features\r\n\r\nBy default, bargreybars.vim runs automatically when you start gvim and when you switch colorscheme. This behaviour can be disabled in your `.vimrc` file with:\r\n\r\n  let g:bargreybars_auto = 0\r\n\r\nIf the automatic color-matching is disabled, you can use the `Colorscheme` command to apply a scheme and match the window background color. It works the same way as the standard `colorscheme` command.\r\n\r\n  :Colorscheme zenburn\r\n","4":"# bargreybars.vim\r\n\r\nThis plugin is stored at https:\/\/github.com\/dreadnaut\/vim-bargreybars\r\n\r\nGvim windows have a grey as default background color, behind the text area. When a window is maximised and its dimensions stop being a multiple of the font size, the grey background shows as bars on the right and bottom side of the windows.\r\n\r\nThis plugin keeps the windows background in sync with the background of your color scheme, calling an external library that modifies the window attributes. Source code for the library is included in the dll directory.\r\n\r\nGrey bars gone, the world is safe again!\r\n\r\nNote: the plugin works only on Windows. GTK-based Vim can be tweaked in a different way, and an issue exists in the vim issue tracker:\r\n\r\n  https:\/\/github.com\/vim\/vim\/issues\/349\r\n  http:\/\/pastebin.com\/N0G333nP\r\n\r\n## Features\r\n\r\nBy default, bargreybars.vim runs automatically when you start gvim and when you switch colorscheme. This behaviour can be disabled in your `.vimrc` file with:\r\n\r\n  let g:bargreybars_auto = 0\r\n\r\nIf the automatic color-matching is disabled, you can use the `Colorscheme` command to apply a scheme and match the window background color. It works the same way as the standard `colorscheme` command.\r\n\r\n  :Colorscheme zenburn\r\n","install_details":"The plugin is compatible with pathogen.vim and a similar plugin managers.\r\n\r\nHere's the clone command for you copy-paste convenience:\r\n\r\n  git clone https:\/\/github.com\/dreadnaut\/vim-bargreybars.git\r\n","5":"The plugin is compatible with pathogen.vim and a similar plugin managers.\r\n\r\nHere's the clone command for you copy-paste convenience:\r\n\r\n  git clone https:\/\/github.com\/dreadnaut\/vim-bargreybars.git\r\n","first_name":"dreadnaut","6":"dreadnaut","last_name":"","7":"","releases":[{"0":"5535","vim_version":"7.3","1":"7.3","script_version":"0.0.2","2":"0.0.2","version_comment":"Improved x64 support:\r\n- The package now includes DLLs for both x86 and x64 builds of Vim\r\n- The plugin loads the correct one automatically","3":"Improved x64 support:\r\n- The package now includes DLLs for both x86 and x64 builds of Vim\r\n- The plugin loads the correct one automatically","package":"vim-bargreybars.zip","4":"vim-bargreybars.zip","src_id":"27046","5":"27046","creation_date":"1583139251","6":"1583139251"},{"0":"5535","vim_version":"7.3","1":"7.3","script_version":"0.0.1","2":"0.0.1","version_comment":"Initial upload","3":"Initial upload","package":"vim-bargreybars.zip","4":"vim-bargreybars.zip","src_id":"25016","5":"25016","creation_date":"1489009971","6":"1489009971"}]},"5534":{"script_id":"5534","0":"5534","script_name":"nonclobbering-shift","1":"nonclobbering-shift","script_type":"utility","2":"utility","summary":"Visual shift without clobbering formatting","3":"Visual shift without clobbering formatting","description":"Causes the visual shift functions to add\/remove only leading tabs, preserve all formatting.","4":"Causes the visual shift functions to add\/remove only leading tabs, preserve all formatting.","install_details":"Copy to \/autoload\/","5":"Copy to \/autoload\/","first_name":"Yarin","6":"Yarin","last_name":"Licht","7":"Licht","releases":[{"0":"5534","vim_version":"7.0","1":"7.0","script_version":"1","2":"1","version_comment":"Initial upload","3":"Initial upload","package":"nonclobbering-shift.vim","4":"nonclobbering-shift.vim","src_id":"25008","5":"25008","creation_date":"1488555556","6":"1488555556"}]},"5533":{"script_id":"5533","0":"5533","script_name":"visual-search","1":"visual-search","script_type":"utility","2":"utility","summary":"Search for or only within visual selection","3":"Search for or only within visual selection","description":"By default, applying a search with Slash in visual mode moves the cursor, and the selection with it, this behavior is unintuitive at best and useless except in the rarest of circumstances.\r\nSo, we make search-forward search within the current selection, and search-backward search the whole buffer for the current selection.\r\n","4":"By default, applying a search with Slash in visual mode moves the cursor, and the selection with it, this behavior is unintuitive at best and useless except in the rarest of circumstances.\r\nSo, we make search-forward search within the current selection, and search-backward search the whole buffer for the current selection.\r\n","install_details":"Copy to \/autoload\/","5":"Copy to \/autoload\/","first_name":"Yarin","6":"Yarin","last_name":"Licht","7":"Licht","releases":[{"0":"5533","vim_version":"7.0","1":"7.0","script_version":"1","2":"1","version_comment":"Initial upload","3":"Initial upload","package":"visual-search.vim","4":"visual-search.vim","src_id":"25007","5":"25007","creation_date":"1488550481","6":"1488550481"}]},"5532":{"script_id":"5532","0":"5532","script_name":"dubs-midnight","1":"dubs-midnight","script_type":"color scheme","2":"color scheme","summary":"An other member of the dubs color scheme family","3":"An other member of the dubs color scheme family","description":"It is intended mainly for sortware development and to be comfortable for the eyes.","4":"It is intended mainly for sortware development and to be comfortable for the eyes.","install_details":"Just copy in the appropriate directory.","5":"Just copy in the appropriate directory.","first_name":"Gabor","6":"Gabor","last_name":"Urban","7":"Urban","releases":[{"0":"5532","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"dubs_midnight.vim","4":"dubs_midnight.vim","src_id":"25001","5":"25001","creation_date":"1488093483","6":"1488093483"}]},"5531":{"script_id":"5531","0":"5531","script_name":"gina.vim","1":"gina.vim","script_type":"utility","2":"utility","summary":" Asynchronously control git repositories in Neovim\/Vim 8","3":" Asynchronously control git repositories in Neovim\/Vim 8","description":"gina.vim (gina) is a plugin to asynchrnously control git repositories.\r\n\r\nSupports\r\n-------------------------------------------------------------------------------\r\n- Git 1.8.5.6 or above\r\n- Vim 8.0.0027 or above or Neovim 0.2.0\r\n- All major platforms\r\n  - Linux (Tested on TravisCI, author use Linux)\r\n  - macOS (Tested on TravisCI, author use OS X Elcapitan)\r\n  - Windows (Tested on AppVeyor, main contributor use Windows)\r\n\r\nSee https:\/\/github.com\/lambdalisue\/gina.vim for more detail.","4":"gina.vim (gina) is a plugin to asynchrnously control git repositories.\r\n\r\nSupports\r\n-------------------------------------------------------------------------------\r\n- Git 1.8.5.6 or above\r\n- Vim 8.0.0027 or above or Neovim 0.2.0\r\n- All major platforms\r\n  - Linux (Tested on TravisCI, author use Linux)\r\n  - macOS (Tested on TravisCI, author use OS X Elcapitan)\r\n  - Windows (Tested on AppVeyor, main contributor use Windows)\r\n\r\nSee https:\/\/github.com\/lambdalisue\/gina.vim for more detail.","install_details":"","5":"","first_name":"Alisue","6":"Alisue","last_name":"Lambda","7":"Lambda","releases":[{"0":"5531","vim_version":"8.0","1":"8.0","script_version":"v0.3.1","2":"v0.3.1","version_comment":"Fix buffer parse issue","3":"Fix buffer parse issue","package":"gina-v0.3.1.zip","4":"gina-v0.3.1.zip","src_id":"25474","5":"25474","creation_date":"1501702161","6":"1501702161"},{"0":"5531","vim_version":"8.0","1":"8.0","script_version":"v0.3.0","2":"v0.3.0","version_comment":"- Add\r\n  - Gina stash\r\n  - statusline\/tabline components\r\n  - command completion\r\n  - diff jumps on diff\/commit buffer\r\n  - shell\/term execution via Gina!!\r\n  - Yank actions\r\n- Fix\r\n  - 'Not allowed here' exceptions\r\n  - Scroll position on Gina blame\r\n  - Gina show --opener=edit :\r\n  - Gina init\r\n\r\nRef: https:\/\/github.com\/lambdalisue\/gina.vim\/milestone\/3?closed=1","3":"- Add\r\n  - Gina stash\r\n  - statusline\/tabline components\r\n  - command completion\r\n  - diff jumps on diff\/commit buffer\r\n  - shell\/term execution via Gina!!\r\n  - Yank actions\r\n- Fix\r\n  - 'Not allowed here' exceptions\r\n  - Scroll position on Gina blame\r\n  - Gina show --opener=edit :\r\n  - Gina init\r\n\r\nRef: https:\/\/github.com\/lambdalisue\/gina.vim\/milestone\/3?closed=1","package":"gina-v0.3.0.zip","4":"gina-v0.3.0.zip","src_id":"25472","5":"25472","creation_date":"1501697930","6":"1501697930"},{"0":"5531","vim_version":"8.0","1":"8.0","script_version":"v0.2.1","2":"v0.2.1","version_comment":"- Bug fixes\r\n  - Fix commit issue on a newly checked out repository\r\n  - Fix tabpage issue of Vim.Buffer.Group module\r\n  - Fix 'modeline' issue on several commands\r\n  - Fix colorscheme issue for highlights\r\n  - Fix no action error\r\n- Improve actions\r\n  - Add mods support\r\n  - Add mark features to mark candidates prior to the actions\r\n  - Add \"show:commit\" action to show a commit rather than a content\r\n  - Add \"xxx:split\/vsplit\"\r\n  - Move \"xxx:above\/below\/...\" to aliases\r\n  - Do NOT repeat action by mappings\r\n  - Do NOT restore selections after repeat\r\n  - Do NOT alias choice\/repeat\r\n- Fix Gina show\r\n  - Enable --line\/--col only when {path} has specified\r\n- Fix Gina log\r\n  - Allow \"Gina log v0.1.0...\" to show log from v0.1.0 to HEAD\r\n- Guess --line\/--col from the current buffer if possible\r\n- Add Gina blame","3":"- Bug fixes\r\n  - Fix commit issue on a newly checked out repository\r\n  - Fix tabpage issue of Vim.Buffer.Group module\r\n  - Fix 'modeline' issue on several commands\r\n  - Fix colorscheme issue for highlights\r\n  - Fix no action error\r\n- Improve actions\r\n  - Add mods support\r\n  - Add mark features to mark candidates prior to the actions\r\n  - Add \"show:commit\" action to show a commit rather than a content\r\n  - Add \"xxx:split\/vsplit\"\r\n  - Move \"xxx:above\/below\/...\" to aliases\r\n  - Do NOT repeat action by mappings\r\n  - Do NOT restore selections after repeat\r\n  - Do NOT alias choice\/repeat\r\n- Fix Gina show\r\n  - Enable --line\/--col only when {path} has specified\r\n- Fix Gina log\r\n  - Allow \"Gina log v0.1.0...\" to show log from v0.1.0 to HEAD\r\n- Guess --line\/--col from the current buffer if possible\r\n- Add Gina blame","package":"gina-v0.2.1.zip","4":"gina-v0.2.1.zip","src_id":"25010","5":"25010","creation_date":"1488669284","6":"1488669284"},{"0":"5531","vim_version":"8.0","1":"8.0","script_version":"v0.1.0","2":"v0.1.0","version_comment":"Initial upload","3":"Initial upload","package":"gina-0.1.0.zip","4":"gina-0.1.0.zip","src_id":"24996","5":"24996","creation_date":"1487964070","6":"1487964070"}]},"5530":{"script_id":"5530","0":"5530","script_name":"doctabs","1":"doctabs","script_type":"utility","2":"utility","summary":"A plugin to manage large files","3":"A plugin to manage large files","description":"DocTabs is like having screen\/tmux for a single buffer. Vim already lets you manage different buffers very efficiently, but within a buffer you are limited to jumping by searches or tags. With DocTabs, however, you can organize a large file into sections, which you can visualize and jump between. Each section keeps its own editing view so you can jump back to where you were easily. The prefix-style switching should be familiar to screen\/tmux users. The tabline is used to show all the sections and highlight the currently active one, hence the plugin's name.\r\n\r\nThis is useful for a wide range of scenarios: documentation, source code, HTML, project plans, todo or GTD files, reminder files, journals, novels, your ~\/.vimrc, etc. The DocTabs plugin and documentation were both written using DocTabs. \r\n\r\nhttps:\/\/github.com\/jbarbero\/doctabs.vim\r\n\r\nAsciicast:\r\nhttps:\/\/asciinema.org\/a\/107382","4":"DocTabs is like having screen\/tmux for a single buffer. Vim already lets you manage different buffers very efficiently, but within a buffer you are limited to jumping by searches or tags. With DocTabs, however, you can organize a large file into sections, which you can visualize and jump between. Each section keeps its own editing view so you can jump back to where you were easily. The prefix-style switching should be familiar to screen\/tmux users. The tabline is used to show all the sections and highlight the currently active one, hence the plugin's name.\r\n\r\nThis is useful for a wide range of scenarios: documentation, source code, HTML, project plans, todo or GTD files, reminder files, journals, novels, your ~\/.vimrc, etc. The DocTabs plugin and documentation were both written using DocTabs. \r\n\r\nhttps:\/\/github.com\/jbarbero\/doctabs.vim\r\n\r\nAsciicast:\r\nhttps:\/\/asciinema.org\/a\/107382","install_details":"If you are using Pathogen, just clone the repo or unzip the package into ~\/.vim\/bundle, restart vim, and run :Helptags\r\n\r\nIf you are not using pathogen, unzip this package in your ~\/.vim folder:\r\nautoload\/dtab.vim   ->  ~\/.vim\/autoload\/dtab.vim\r\ndoc\/doctabs.txt     ->  ~\/.vim\/doc\/doctabs.txt\r\nplugin\/doctabs.vim  ->  ~\/.vim\/plugin\/doctabs.vim\r\n\r\nthen run :helptags (notice the different case).\r\n","5":"If you are using Pathogen, just clone the repo or unzip the package into ~\/.vim\/bundle, restart vim, and run :Helptags\r\n\r\nIf you are not using pathogen, unzip this package in your ~\/.vim folder:\r\nautoload\/dtab.vim   ->  ~\/.vim\/autoload\/dtab.vim\r\ndoc\/doctabs.txt     ->  ~\/.vim\/doc\/doctabs.txt\r\nplugin\/doctabs.vim  ->  ~\/.vim\/plugin\/doctabs.vim\r\n\r\nthen run :helptags (notice the different case).\r\n","first_name":"Janos","6":"Janos","last_name":"Barbero","7":"Barbero","releases":[{"0":"5530","vim_version":"7.3","1":"7.3","script_version":"0.9","2":"0.9","version_comment":"Pick up section changes sooner (on lines changing rather than on buffer write), allow spaces in section names by default","3":"Pick up section changes sooner (on lines changing rather than on buffer write), allow spaces in section names by default","package":"doctabs-0.9.zip","4":"doctabs-0.9.zip","src_id":"25137","5":"25137","creation_date":"1493963175","6":"1493963175"},{"0":"5530","vim_version":"7.3","1":"7.3","script_version":"0.8","2":"0.8","version_comment":"Allow user-specified keybinding prefix, analogous to screen's \"escape ^A\" or tmux's \"set -g prefix C-a\"","3":"Allow user-specified keybinding prefix, analogous to screen's \"escape ^A\" or tmux's \"set -g prefix C-a\"","package":"doctabs-0.8.zip","4":"doctabs-0.8.zip","src_id":"25051","5":"25051","creation_date":"1490650243","6":"1490650243"},{"0":"5530","vim_version":"7.3","1":"7.3","script_version":"0.7","2":"0.7","version_comment":"Allow alphanumeric labels (qwert...) to allow fast switching with more than 10 sections.","3":"Allow alphanumeric labels (qwert...) to allow fast switching with more than 10 sections.","package":"doctabs.zip","4":"doctabs.zip","src_id":"25032","5":"25032","creation_date":"1489512389","6":"1489512389"},{"0":"5530","vim_version":"7.3","1":"7.3","script_version":"0.5.3","2":"0.5.3","version_comment":"0.5.3   Highlight section headings by default, only update section views when leaving a section via jump commands, minor bugfixes","3":"0.5.3   Highlight section headings by default, only update section views when leaving a section via jump commands, minor bugfixes","package":"doctabs.zip","4":"doctabs.zip","src_id":"25031","5":"25031","creation_date":"1489468895","6":"1489468895"},{"0":"5530","vim_version":"7.3","1":"7.3","script_version":"0.4","2":"0.4","version_comment":"Initial upload","3":"Initial upload","package":"doctabs.zip","4":"doctabs.zip","src_id":"24992","5":"24992","creation_date":"1487908506","6":"1487908506"}]},"5529":{"script_id":"5529","0":"5529","script_name":"verilog-support.vim","1":"verilog-support.vim","script_type":"utility","2":"utility","summary":"Verilog IDE -- Insert UVM & SystemVerilog code snippets, classes, comment, etc","3":"Verilog IDE -- Insert UVM & SystemVerilog code snippets, classes, comment, etc","description":"IDE Heavily based on perl-support by Fritz and Wolfgang Mehner. I've followed their architecture to add similar support for UVM on SystemVerilog. Verilog-support.vim currently supports SystemVerilog and UVM on SV.\r\n\r\nFEATURES\r\n-------------------------------------------------------\r\n\r\nThe verilog-support.vim plugin adds a set of templates that can be used to insert blocks of code into SystemVerilog files.\r\n\r\n - Comment templates: Insert comment headers for Tasks, Functions, Classes, Modules, etc. with menu or hot-key. Comments are suitable for NaturalDoc usage.\r\n - UVM Class templates: Insert class boilerplate for a new UVM class with a menu or hot-key\r\n - UVM Phase templates: Insert the various UVM phase tasks and functions with a menu or hot-key\r\n - UVM idioms template: Insert various UVM code snippets (config_db, objections, etc.) using menu or hot-key.\r\n\r\nTemplates are user-configurable and extendable. If you have changes that you think others would find useful, please push them to me.\r\n\r\nThe help file online :  https:\/\/github.com\/jmcneal\/verilog-support\/blob\/master\/doc\/verilogsupport.txt\r\n\r\n\r\nDOCUMENTATION \r\n-------------------------------------------------------- \r\nThis plug-in comes with a help file (verilogsupport.txt). Read it with \r\n\r\n    :help verilogsupport \r\n\r\n** PLEASE READ THE DOCUMENTATION ** \r\n\r\nEditing actions differ for different modes! There are a lot of features which \r\ncan be configured or customized to match your needs. \r\n\r\n\r\nGitHub \r\n-------------------------------------------------------- \r\nVerilog Support is on github:\r\n\r\nhttps:\/\/github.com\/jmcneal\/verilog-support\r\n","4":"IDE Heavily based on perl-support by Fritz and Wolfgang Mehner. I've followed their architecture to add similar support for UVM on SystemVerilog. Verilog-support.vim currently supports SystemVerilog and UVM on SV.\r\n\r\nFEATURES\r\n-------------------------------------------------------\r\n\r\nThe verilog-support.vim plugin adds a set of templates that can be used to insert blocks of code into SystemVerilog files.\r\n\r\n - Comment templates: Insert comment headers for Tasks, Functions, Classes, Modules, etc. with menu or hot-key. Comments are suitable for NaturalDoc usage.\r\n - UVM Class templates: Insert class boilerplate for a new UVM class with a menu or hot-key\r\n - UVM Phase templates: Insert the various UVM phase tasks and functions with a menu or hot-key\r\n - UVM idioms template: Insert various UVM code snippets (config_db, objections, etc.) using menu or hot-key.\r\n\r\nTemplates are user-configurable and extendable. If you have changes that you think others would find useful, please push them to me.\r\n\r\nThe help file online :  https:\/\/github.com\/jmcneal\/verilog-support\/blob\/master\/doc\/verilogsupport.txt\r\n\r\n\r\nDOCUMENTATION \r\n-------------------------------------------------------- \r\nThis plug-in comes with a help file (verilogsupport.txt). Read it with \r\n\r\n    :help verilogsupport \r\n\r\n** PLEASE READ THE DOCUMENTATION ** \r\n\r\nEditing actions differ for different modes! There are a lot of features which \r\ncan be configured or customized to match your needs. \r\n\r\n\r\nGitHub \r\n-------------------------------------------------------- \r\nVerilog Support is on github:\r\n\r\nhttps:\/\/github.com\/jmcneal\/verilog-support\r\n","install_details":"PATHOGEN\r\n--------------------------------------------------------\r\nI highly recommend using Tim Pope's pathogen.vim to manage vim plugins. Once you have installed that, copy and paste:\r\n\r\n    cd ~\/.vim\/bundle\r\n    git clone git:\/\/github.com\/jmcneal\/verilog-support.git\r\n\r\nOR\r\n\r\nMANUAL\r\n\r\nCopy the zip archive verilog-support.zip to $HOME\/.vim\/ or $VIM\/vimfiles \r\n(on the Windows platforms) and run \r\n    unzip verilog-support.zip \r\nIf you have already an older version of this plug-in and you have modified the \r\ntemplate files you may want to save your templates first or copy the files from \r\nthe archive by hand.","5":"PATHOGEN\r\n--------------------------------------------------------\r\nI highly recommend using Tim Pope's pathogen.vim to manage vim plugins. Once you have installed that, copy and paste:\r\n\r\n    cd ~\/.vim\/bundle\r\n    git clone git:\/\/github.com\/jmcneal\/verilog-support.git\r\n\r\nOR\r\n\r\nMANUAL\r\n\r\nCopy the zip archive verilog-support.zip to $HOME\/.vim\/ or $VIM\/vimfiles \r\n(on the Windows platforms) and run \r\n    unzip verilog-support.zip \r\nIf you have already an older version of this plug-in and you have modified the \r\ntemplate files you may want to save your templates first or copy the files from \r\nthe archive by hand.","first_name":"Jeff","6":"Jeff","last_name":"McNeal","7":"McNeal","releases":[{"0":"5529","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"verilog-support.zip","4":"verilog-support.zip","src_id":"24982","5":"24982","creation_date":"1487695987","6":"1487695987"}]},"5528":{"script_id":"5528","0":"5528","script_name":"add-git-managed-file-to-buffer.vim","1":"add-git-managed-file-to-buffer.vim","script_type":"utility","2":"utility","summary":"Add files that are changed, modifiled, untracked in git to the buffer.","3":"Add files that are changed, modifiled, untracked in git to the buffer.","description":"This plugin provides the ability to add files that are changed, modifiled, untracked in git to the buffer.\r\n\r\nHomepage: https:\/\/github.com\/ToruIwashita\/add-git-managed-file-to-buffer.vim","4":"This plugin provides the ability to add files that are changed, modifiled, untracked in git to the buffer.\r\n\r\nHomepage: https:\/\/github.com\/ToruIwashita\/add-git-managed-file-to-buffer.vim","install_details":"","5":"","first_name":"Toru","6":"Toru","last_name":"Hoyano","7":"Hoyano","releases":[{"0":"5528","vim_version":"8.0","1":"8.0","script_version":"1.3.0","2":"1.3.0","version_comment":"Fix to read changed files even if it is not root directory.","3":"Fix to read changed files even if it is not root directory.","package":"add-git-managed-file-to-buffer.vim-1.3.0.zip","4":"add-git-managed-file-to-buffer.vim-1.3.0.zip","src_id":"25212","5":"25212","creation_date":"1494927010","6":"1494927010"},{"0":"5528","vim_version":"8.0","1":"8.0","script_version":"1.2.0","2":"1.2.0","version_comment":"Fix 'Cannot close last tab page' error.","3":"Fix 'Cannot close last tab page' error.","package":"add-git-managed-file-to-buffer.vim-1.2.0.zip","4":"add-git-managed-file-to-buffer.vim-1.2.0.zip","src_id":"25018","5":"25018","creation_date":"1489048386","6":"1489048386"},{"0":"5528","vim_version":"8.0","1":"8.0","script_version":"1.1.0","2":"1.1.0","version_comment":"Add tabpagemax = 100 setting to the OpenAllBuffersInTab command.","3":"Add tabpagemax = 100 setting to the OpenAllBuffersInTab command.","package":"add-git-managed-file-to-buffer.vim-1.1.0.zip","4":"add-git-managed-file-to-buffer.vim-1.1.0.zip","src_id":"24976","5":"24976","creation_date":"1487303099","6":"1487303099"},{"0":"5528","vim_version":"8.0","1":"8.0","script_version":"1.0.0","2":"1.0.0","version_comment":"Initial upload","3":"Initial upload","package":"add-git-managed-file-to-buffer.vim-1.0.0.zip","4":"add-git-managed-file-to-buffer.vim-1.0.0.zip","src_id":"24973","5":"24973","creation_date":"1487233314","6":"1487233314"}]},"5527":{"script_id":"5527","0":"5527","script_name":"workbook","1":"workbook","script_type":"utility","2":"utility","summary":"Notebook-like interaction with R etc.","3":"Notebook-like interaction with R etc.","description":"The long-term goal of this plugin is to provide notebook-like interaction with \r\ninterpreted languages similar to the Mathematica or Jupyter (within the limits \r\nof a text editor like vim).\r\n\r\nFeatures~\r\n- Run an interpreter as an inferior process.\r\n- Send code to this process (asynchronously without blocking vim).\r\n- Insert (or dynamically update) the results into the source code (as \r\n  commented out block below the respective source code).\r\n- Transcribe the interaction with the interpreter.\r\n- Provide code completion (see 'omnifunc') for supported filetypes.\r\n\r\nHow to use this plugin~\r\n- Open a file with a supported filetype (see below or \r\n  |workbook#GetSupportedFiletypes()|).\r\n- Type |:Workbook| or add the filetype to \r\n  |g:workbook_autosetup_filetypes| to automatically enable the workbook \r\n  mode for the specified filetypes.\r\n- Press  to evaluate the current paragraph.\r\n- Press w for help on other commands and maps.\r\n\r\nThe following filetypes are supported~\r\n- R (supports code completion)\r\n- vim\r\n- sh (default: bash)\r\n\r\nCurrenty, the main use case is to interact with R. Other than other \r\nwell-known R-related vim plugins, the workbook plugin has no non-vim \r\ndependencies and works at least on Linux and Windows with no problems. \r\nThe vim and the bash backend are mostly there to get the code right.\r\n","4":"The long-term goal of this plugin is to provide notebook-like interaction with \r\ninterpreted languages similar to the Mathematica or Jupyter (within the limits \r\nof a text editor like vim).\r\n\r\nFeatures~\r\n- Run an interpreter as an inferior process.\r\n- Send code to this process (asynchronously without blocking vim).\r\n- Insert (or dynamically update) the results into the source code (as \r\n  commented out block below the respective source code).\r\n- Transcribe the interaction with the interpreter.\r\n- Provide code completion (see 'omnifunc') for supported filetypes.\r\n\r\nHow to use this plugin~\r\n- Open a file with a supported filetype (see below or \r\n  |workbook#GetSupportedFiletypes()|).\r\n- Type |:Workbook| or add the filetype to \r\n  |g:workbook_autosetup_filetypes| to automatically enable the workbook \r\n  mode for the specified filetypes.\r\n- Press  to evaluate the current paragraph.\r\n- Press w for help on other commands and maps.\r\n\r\nThe following filetypes are supported~\r\n- R (supports code completion)\r\n- vim\r\n- sh (default: bash)\r\n\r\nCurrenty, the main use case is to interact with R. Other than other \r\nwell-known R-related vim plugins, the workbook plugin has no non-vim \r\ndependencies and works at least on Linux and Windows with no problems. \r\nThe vim and the bash backend are mostly there to get the code right.\r\n","install_details":"Either use the zip archive:\r\n    - Download the zip archive\r\n    - Extract it to ~\/.vim\/pack\/tml\/start\/workbook\r\n\r\nor install from github:\r\n    - Start a terminal\r\n    - Change the working directory to ~\/.vim\/pack\/tml\/start\/\r\n    - Type: git clone https:\/\/github.com\/tomtom\/workbook_vim\r\n\r\nNOTE: On Windows, ~\/.vim might be ~\/vimfiles. Please see 'runtimepath' for \r\ndetails.\r\n\r\n\r\nRequirements~\r\n\r\nThis script requires tlib (vimscript #1863) to be installed -- see \r\nhttps:\/\/github.com\/tomtom\/tlib_vim.\r\n","5":"Either use the zip archive:\r\n    - Download the zip archive\r\n    - Extract it to ~\/.vim\/pack\/tml\/start\/workbook\r\n\r\nor install from github:\r\n    - Start a terminal\r\n    - Change the working directory to ~\/.vim\/pack\/tml\/start\/\r\n    - Type: git clone https:\/\/github.com\/tomtom\/workbook_vim\r\n\r\nNOTE: On Windows, ~\/.vim might be ~\/vimfiles. Please see 'runtimepath' for \r\ndetails.\r\n\r\n\r\nRequirements~\r\n\r\nThis script requires tlib (vimscript #1863) to be installed -- see \r\nhttps:\/\/github.com\/tomtom\/tlib_vim.\r\n","first_name":"Tom","6":"Tom","last_name":"Link","7":"Link","releases":[{"0":"5527","vim_version":"7.0","1":"7.0","script_version":"0.02","2":"0.02","version_comment":"- Script ID\n- vim_raw, vim_nl: NEW wait_after_startup property\n- Command-line completion for :Workbook\n- Proper error for unsupported filetypes\n- g:workbook#map_evalblock: Block expression is configurable\n- Improve maps & movements\n- Misc enhancements + exprimental filetypes\n- FIX fsharp\n- Experimental support for scala\n- workbook#OmniComplete: Always include omnifunc results if available\n- Slightly improved: f#, scala\n- Eval: always wrap code\n- r: use save & restore by default; support for codetools::checkUsage(), formatR::tidy_source()\n- FIX maps; FIX rmd support; FIX R support for formatR\n- Misc enhancements: Improved Rmarkdown (rmd) support etc.\n- Support for ruby\nMD5 checksum: 873d7f1fec86456cd267c9e29e8796cd","3":"- Script ID\n- vim_raw, vim_nl: NEW wait_after_startup property\n- Command-line completion for :Workbook\n- Proper error for unsupported filetypes\n- g:workbook#map_evalblock: Block expression is configurable\n- Improve maps & movements\n- Misc enhancements + exprimental filetypes\n- FIX fsharp\n- Experimental support for scala\n- workbook#OmniComplete: Always include omnifunc results if available\n- Slightly improved: f#, scala\n- Eval: always wrap code\n- r: use save & restore by default; support for codetools::checkUsage(), formatR::tidy_source()\n- FIX maps; FIX rmd support; FIX R support for formatR\n- Misc enhancements: Improved Rmarkdown (rmd) support etc.\n- Support for ruby\nMD5 checksum: 873d7f1fec86456cd267c9e29e8796cd","package":"workbook.zip","4":"workbook.zip","src_id":"25034","5":"25034","creation_date":"1489692683","6":"1489692683"},{"0":"5527","vim_version":"8.0","1":"8.0","script_version":"0.01","2":"0.01","version_comment":"Initial upload","3":"Initial upload","package":"workbook.zip","4":"workbook.zip","src_id":"24969","5":"24969","creation_date":"1487070035","6":"1487070035"}]},"5526":{"script_id":"5526","0":"5526","script_name":"autopack","1":"autopack","script_type":"utility","2":"utility","summary":"Load optional packs by command, map, filetype etc.","3":"Load optional packs by command, map, filetype etc.","description":"VIM 8.0 introduced a new way to handle (optional) plugins via the \r\n|:packload| command. This plugin aims at facilitating the handling of \r\noptional packs by loading packs when certain triggers are invoked. The \r\ngoal of this approach is to reduce startup time without interferring \r\nwith your workflow.\r\n\r\nA trigger could be\r\n- Invocation of a command (see |:Autocommand|)\r\n- Invocation of a map (see |:Automap|)\r\n- Editing a file with a specific filetype (see |:Autofiletype|)\r\n- Editing a file matching a specific file pattern (see \r\n  |:Autofilepattern|)\r\n\r\nHow to use this plugin~\r\n- Edit ~\/.vim\/packrc\/autorc.vim\r\n- Add autopack commands (|:Autocommand|, |:Automap|, |:Autofiletype|, \r\n  |:Autofilepattern| as needed)\r\n- \"Filetype packs\", i.e. packs matching `pack\/ft_{FILETYPE}\/opt\/*` in \r\n  you 'runtimepath' are automatically enabled when editing a file with \r\n  the respective filetype\r\n- Restart vim\r\n\r\nExample autorc.vim file >\r\n    Automap ttoc_vim nnoremap cc :TToC\r\n    Autocommand trag_vim Trag\r\n    Autofiletype workbook_vim r\r\n    Autofilepattern ttodo_vim *todo.txt *TODO.TX","4":"VIM 8.0 introduced a new way to handle (optional) plugins via the \r\n|:packload| command. This plugin aims at facilitating the handling of \r\noptional packs by loading packs when certain triggers are invoked. The \r\ngoal of this approach is to reduce startup time without interferring \r\nwith your workflow.\r\n\r\nA trigger could be\r\n- Invocation of a command (see |:Autocommand|)\r\n- Invocation of a map (see |:Automap|)\r\n- Editing a file with a specific filetype (see |:Autofiletype|)\r\n- Editing a file matching a specific file pattern (see \r\n  |:Autofilepattern|)\r\n\r\nHow to use this plugin~\r\n- Edit ~\/.vim\/packrc\/autorc.vim\r\n- Add autopack commands (|:Autocommand|, |:Automap|, |:Autofiletype|, \r\n  |:Autofilepattern| as needed)\r\n- \"Filetype packs\", i.e. packs matching `pack\/ft_{FILETYPE}\/opt\/*` in \r\n  you 'runtimepath' are automatically enabled when editing a file with \r\n  the respective filetype\r\n- Restart vim\r\n\r\nExample autorc.vim file >\r\n    Automap ttoc_vim nnoremap cc :TToC\r\n    Autocommand trag_vim Trag\r\n    Autofiletype workbook_vim r\r\n    Autofilepattern ttodo_vim *todo.txt *TODO.TX","install_details":"Either use the zip archive:\r\n    - Download the zip archive\r\n    - Extract it to `~\/.vim\/pack\/tml\/start\/autopack`\r\n\r\nor install from github:\r\n    - Start a terminal\r\n    - Change the working directory to `~\/.vim\/pack\/tml\/start\/`\r\n    - Type: `git clone https:\/\/github.com\/tomtom\/autopack_vim`\r\n\r\nNOTE: If you don't want to run this plugin on startup, use \r\n`~\/.vim\/pack\/tml\/opt\/`.\r\n\r\nNOTE: On Windows, ~\/.vim might be ~\/vimfiles. Please see 'runtimepath' \r\nfor details.\r\n\r\nNOTE: If you want to have autopack-related commands available in your VIMRC \r\nfile or if you want to load packrc configuration files for packs in a \r\n`start` subdirectory, you should move the plugin directory to \r\n`pack\/tml\/opt\/autopack_vim` instead and add `:packadd autopack_vim` to \r\nyour vimrc file.\r\n","5":"Either use the zip archive:\r\n    - Download the zip archive\r\n    - Extract it to `~\/.vim\/pack\/tml\/start\/autopack`\r\n\r\nor install from github:\r\n    - Start a terminal\r\n    - Change the working directory to `~\/.vim\/pack\/tml\/start\/`\r\n    - Type: `git clone https:\/\/github.com\/tomtom\/autopack_vim`\r\n\r\nNOTE: If you don't want to run this plugin on startup, use \r\n`~\/.vim\/pack\/tml\/opt\/`.\r\n\r\nNOTE: On Windows, ~\/.vim might be ~\/vimfiles. Please see 'runtimepath' \r\nfor details.\r\n\r\nNOTE: If you want to have autopack-related commands available in your VIMRC \r\nfile or if you want to load packrc configuration files for packs in a \r\n`start` subdirectory, you should move the plugin directory to \r\n`pack\/tml\/opt\/autopack_vim` instead and add `:packadd autopack_vim` to \r\nyour vimrc file.\r\n","first_name":"Tom","6":"Tom","last_name":"Link","7":"Link","releases":[{"0":"5526","vim_version":"7.0","1":"7.0","script_version":"0.02","2":"0.02","version_comment":"- Autocommand, autopack#NewAutocommand: Support for multiple commands\n- g:autopack_config: Check for has('vim_starting')\n- NEW :Automakeprelude command (collect ftdetect information)\n- g:autopack#use_cmdundefined: Option to use the CmdUndefined event\n- Make sure not to redefine auto-commands or maps\n- autopack#NewFilepattern(): FIX only the last plugins per pattern was loaded\nMD5 checksum: e0525313c600e33aebb5f6f81bdbc90b","3":"- Autocommand, autopack#NewAutocommand: Support for multiple commands\n- g:autopack_config: Check for has('vim_starting')\n- NEW :Automakeprelude command (collect ftdetect information)\n- g:autopack#use_cmdundefined: Option to use the CmdUndefined event\n- Make sure not to redefine auto-commands or maps\n- autopack#NewFilepattern(): FIX only the last plugins per pattern was loaded\nMD5 checksum: e0525313c600e33aebb5f6f81bdbc90b","package":"autopack.zip","4":"autopack.zip","src_id":"25116","5":"25116","creation_date":"1493710130","6":"1493710130"},{"0":"5526","vim_version":"8.0","1":"8.0","script_version":"0.01","2":"0.01","version_comment":"Initial upload","3":"Initial upload","package":"autopack.zip","4":"autopack.zip","src_id":"24968","5":"24968","creation_date":"1487068255","6":"1487068255"}]},"5525":{"script_id":"5525","0":"5525","script_name":"vim-indentguides","1":"vim-indentguides","script_type":"syntax","2":"syntax","summary":"Simple indentation guides for your buffers","3":"Simple indentation guides for your buffers","description":"Space indents are visually identified by the \"┆\" character, while tabs are distinguished by \"|\". Manually calling the command IndentGuidesToggle will toggle indent guides scoped to a specific buffer.\r\n\r\nIf there are any files you would like to not add indent guides for, add the filetype to the ignore list: \r\nlet g:indentguides_ignorelist = ['text']","4":"Space indents are visually identified by the \"┆\" character, while tabs are distinguished by \"|\". Manually calling the command IndentGuidesToggle will toggle indent guides scoped to a specific buffer.\r\n\r\nIf there are any files you would like to not add indent guides for, add the filetype to the ignore list: \r\nlet g:indentguides_ignorelist = ['text']","install_details":"Plugin managers are recommended, such as Plug or Vundle, which directly pull from the git repo for the latest version. Installation instructions for such plugins are available in the README.md file. \r\nAny configuration available is also documented in the README.md file. \r\n\r\nFor those that prefer a static variant, decompress the archive's folder content into your ~\/.vim directory, which should place the plugin into the path ~\/.vim\/plugin\/indentguides.vim ","5":"Plugin managers are recommended, such as Plug or Vundle, which directly pull from the git repo for the latest version. Installation instructions for such plugins are available in the README.md file. \r\nAny configuration available is also documented in the README.md file. \r\n\r\nFor those that prefer a static variant, decompress the archive's folder content into your ~\/.vim directory, which should place the plugin into the path ~\/.vim\/plugin\/indentguides.vim ","first_name":"Thaer","6":"Thaer","last_name":"Khawaja","7":"Khawaja","releases":[{"0":"5525","vim_version":"7.3","1":"7.3","script_version":"0.1.0","2":"0.1.0","version_comment":"Initial upload","3":"Initial upload","package":"vim-indentguides-0.1.0.tar.gz","4":"vim-indentguides-0.1.0.tar.gz","src_id":"24965","5":"24965","creation_date":"1487016087","6":"1487016087"}]},"5524":{"script_id":"5524","0":"5524","script_name":"rel.vim","1":"rel.vim","script_type":"utility","2":"utility","summary":"Follow and define links to files","3":"Follow and define links to files","description":"# Vim Rel - Resource links for vim\r\n\r\nThis is a Vim plugin for following and defining links to other files.\r\nYou can define which programs to use to open files according to\r\nthe file suffix.  It is also possible to define custom schemes for\r\nopening files.\r\n\r\nThis script requires at least Vim v8.0.0020 or Neovim v0.2.0. \r\n\r\nSee [doc\/rel.txt](doc\/rel.txt) for more info\r\n\r\nPlease report any bugs and issues here:\r\n\r\n  https:\/\/github.com\/aklt\/rel.vim\r\n\r\n## The name\r\n\r\nREL stands for Resource Locator and sounds almost like URL if said quickly.\r\n","4":"# Vim Rel - Resource links for vim\r\n\r\nThis is a Vim plugin for following and defining links to other files.\r\nYou can define which programs to use to open files according to\r\nthe file suffix.  It is also possible to define custom schemes for\r\nopening files.\r\n\r\nThis script requires at least Vim v8.0.0020 or Neovim v0.2.0. \r\n\r\nSee [doc\/rel.txt](doc\/rel.txt) for more info\r\n\r\nPlease report any bugs and issues here:\r\n\r\n  https:\/\/github.com\/aklt\/rel.vim\r\n\r\n## The name\r\n\r\nREL stands for Resource Locator and sounds almost like URL if said quickly.\r\n","install_details":"Unzip in ~\/.vim or clone the git repo using your favourite plugin manager.","5":"Unzip in ~\/.vim or clone the git repo using your favourite plugin manager.","first_name":"Anders","6":"Anders","last_name":"Th\u00c3\u00b8gersen","7":"Th\u00c3\u00b8gersen","releases":[{"0":"5524","vim_version":"8.0","1":"8.0","script_version":"0.3.0","2":"0.3.0","version_comment":"* Use autoload\r\n* Open folds when following a link to a file in vim\r\n* Include ^, \\\\ and others in links\r\n* find link text under cursor more accurately\r\n* better tests\r\n* Arguments to :Rel command","3":"* Use autoload\r\n* Open folds when following a link to a file in vim\r\n* Include ^, \\\\ and others in links\r\n* find link text under cursor more accurately\r\n* better tests\r\n* Arguments to :Rel command","package":"rel.vim.zip","4":"rel.vim.zip","src_id":"25379","5":"25379","creation_date":"1499262098","6":"1499262098"},{"0":"5524","vim_version":"8.0","1":"8.0","script_version":"0.2.2","2":"0.2.2","version_comment":"* rename to rel.vim\r\n* version check: need at least vim 8.0.0020 or nvim 0.2.0\r\n* fix: spaces in #\/ search fragment\r\n* recognize markdown links\r\n","3":"* rename to rel.vim\r\n* version check: need at least vim 8.0.0020 or nvim 0.2.0\r\n* fix: spaces in #\/ search fragment\r\n* recognize markdown links\r\n","package":"rel.vim.zip","4":"rel.vim.zip","src_id":"25319","5":"25319","creation_date":"1497785805","6":"1497785805"},{"0":"5524","vim_version":"7.4","1":"7.4","script_version":"v0.2.1","2":"v0.2.1","version_comment":"* case insensitive scheme and link syntax highlighting\r\n* bugfix undefined variable\r\n* fix doc link\r\n","3":"* case insensitive scheme and link syntax highlighting\r\n* bugfix undefined variable\r\n* fix doc link\r\n","package":"vim-rel.zip","4":"vim-rel.zip","src_id":"25309","5":"25309","creation_date":"1497395049","6":"1497395049"},{"0":"5524","vim_version":"7.0","1":"7.0","script_version":"0.2.0","2":"0.2.0","version_comment":"* Allow defining custom link schemes\r\n* Customizable syntax highlight links recognized by rel.vim\r\n* Enable Jumping to fragment in preview window also \r\n* Arbitrary characters in rel links using url encoding\r\n* Various bugfixes\r\n* Better docs ","3":"* Allow defining custom link schemes\r\n* Customizable syntax highlight links recognized by rel.vim\r\n* Enable Jumping to fragment in preview window also \r\n* Arbitrary characters in rel links using url encoding\r\n* Various bugfixes\r\n* Better docs ","package":"vim-rel.zip","4":"vim-rel.zip","src_id":"25276","5":"25276","creation_date":"1496314232","6":"1496314232"},{"0":"5524","vim_version":"7.0","1":"7.0","script_version":"0.1.1","2":"0.1.1","version_comment":"Initial upload","3":"Initial upload","package":"vim-rel.zip","4":"vim-rel.zip","src_id":"24964","5":"24964","creation_date":"1486992018","6":"1486992018"}]},"5523":{"script_id":"5523","0":"5523","script_name":"VIM syntax highlighting & filetype plugi","1":"VIM syntax highlighting & filetype plugi","script_type":"ftplugin","2":"ftplugin","summary":"Makes for easier writing and viewing of HP-25 calculator program files","3":"Makes for easier writing and viewing of HP-25 calculator program files","description":"HP-25: SYNTAX AND FILETYPE PLUGIN\r\n=================================\r\n\r\nVIM SYNTAX HIGHLIGHTING FOR HP-25 PROGRAM FILES (\\*.25)\r\n\r\n  The HP-25 syntax highlighting goes well with the HP-25 file type plugin to facilitate easy writing of HP-25 programs in VIM.\r\n\r\n  INSTALL DETAILS\r\n\r\n    Drop the hp25.vim syntax file into your .vim\/syntax\/ directory and register the file globally or add to your .vimrc file:\r\n\r\n    `autocmd BufRead,BufNewFile *.25 :source ~\/.vim\/syntax\/hp25.vim`\r\n\r\n    Then all files with the .25 extesion will be highlighted appropriately.\r\n\r\nVIM FILETYPE PLUGIN FOR HP-25 PROGRAM FILES (\\*.25)\r\n\r\n  This ftplugin has the following features:\r\n\r\n  Auto-line-numbering: Upon pressing  after a line, the next line has the correct line number. It even renumbers the whole file automatically. So, if you add new lines in the middle of a program, it renumbers the whole file. If you delete a line, just hit Enter to renumber the file (either in Normal or Insert mode) \r\n\r\n  INSTALL DETAILS\r\n\r\n    Drop the hp25.vim syntax file into your .vim\/ftplugin\/ directory and register the file globally or add to your .vimrc file:\r\n\r\n    `autocmd BufRead,BufNewFile *.25 :source ~\/.vim\/ftplugin\/hp25.vim`\r\n\r\n...and you are ready for easy HP-25 program writing.\r\n","4":"HP-25: SYNTAX AND FILETYPE PLUGIN\r\n=================================\r\n\r\nVIM SYNTAX HIGHLIGHTING FOR HP-25 PROGRAM FILES (\\*.25)\r\n\r\n  The HP-25 syntax highlighting goes well with the HP-25 file type plugin to facilitate easy writing of HP-25 programs in VIM.\r\n\r\n  INSTALL DETAILS\r\n\r\n    Drop the hp25.vim syntax file into your .vim\/syntax\/ directory and register the file globally or add to your .vimrc file:\r\n\r\n    `autocmd BufRead,BufNewFile *.25 :source ~\/.vim\/syntax\/hp25.vim`\r\n\r\n    Then all files with the .25 extesion will be highlighted appropriately.\r\n\r\nVIM FILETYPE PLUGIN FOR HP-25 PROGRAM FILES (\\*.25)\r\n\r\n  This ftplugin has the following features:\r\n\r\n  Auto-line-numbering: Upon pressing  after a line, the next line has the correct line number. It even renumbers the whole file automatically. So, if you add new lines in the middle of a program, it renumbers the whole file. If you delete a line, just hit Enter to renumber the file (either in Normal or Insert mode) \r\n\r\n  INSTALL DETAILS\r\n\r\n    Drop the hp25.vim syntax file into your .vim\/ftplugin\/ directory and register the file globally or add to your .vimrc file:\r\n\r\n    `autocmd BufRead,BufNewFile *.25 :source ~\/.vim\/ftplugin\/hp25.vim`\r\n\r\n...and you are ready for easy HP-25 program writing.\r\n","install_details":"","5":"","first_name":"Geir","6":"Geir","last_name":"Isene","7":"Isene","releases":[{"0":"5523","vim_version":"7.0","1":"7.0","script_version":"0.2","2":"0.2","version_comment":"Initial upload","3":"Initial upload","package":"hp-25.vmb","4":"hp-25.vmb","src_id":"24962","5":"24962","creation_date":"1486974482","6":"1486974482"}]},"5522":{"script_id":"5522","0":"5522","script_name":"vim-eslint-fix","1":"vim-eslint-fix","script_type":"patch","2":"patch","summary":"A vim plugin that fix the current file by eslint","3":"A vim plugin that fix the current file by eslint","description":"A vim plugin that fix the current file by eslint\r\n","4":"A vim plugin that fix the current file by eslint\r\n","install_details":"usage:\r\n\r\n\".vimrc\r\nfunction! PrettyFile()\r\n  if &filetype==\"javascript\"\r\n    if exists('g:loaded_Beautifier')\r\n      call JsBeautify()\r\n    endif\r\n    if exists('g:loaded_ESLintFix')\r\n      call ESLintFix()\r\n    endif\r\n  end\r\nendfunction\r\n\r\n\"pretty the file before saving.\r\nautocmd BufWritePre * execute 'call PrettyFile()'\r\n\r\n\"see more https:\/\/github.com\/josudoey\/vim-eslint-fix","5":"usage:\r\n\r\n\".vimrc\r\nfunction! PrettyFile()\r\n  if &filetype==\"javascript\"\r\n    if exists('g:loaded_Beautifier')\r\n      call JsBeautify()\r\n    endif\r\n    if exists('g:loaded_ESLintFix')\r\n      call ESLintFix()\r\n    endif\r\n  end\r\nendfunction\r\n\r\n\"pretty the file before saving.\r\nautocmd BufWritePre * execute 'call PrettyFile()'\r\n\r\n\"see more https:\/\/github.com\/josudoey\/vim-eslint-fix","first_name":"joey","6":"joey","last_name":"fang","7":"fang","releases":[{"0":"5522","vim_version":"7.0","1":"7.0","script_version":"0.0.0","2":"0.0.0","version_comment":"Initial upload","3":"Initial upload","package":"vim-eslint-fix.vim","4":"vim-eslint-fix.vim","src_id":"24960","5":"24960","creation_date":"1486887168","6":"1486887168"}]},"5521":{"script_id":"5521","0":"5521","script_name":"vim-numbers","1":"vim-numbers","script_type":"utility","2":"utility","summary":"A plugin for intelligently switching between absolute and relative line numbers","3":"A plugin for intelligently switching between absolute and relative line numbers","description":"This is a fork of the numbers.vim plugin originally developed by Mahdi Yusuf.\r\nThe majority of the plugin codes have been rewritten, including bug fixes and\r\nan alternative approach to determine whether a number column is needed.\r\nManual toggle commands have been removed from the original plugin.\r\n\r\nThis plugin alternates between relative numbering (`relativenumber`) and\r\nabsolute numbering (`number`) for the active window depending on the current\r\nmode. Relative numbering is used in `Normal` mode while absolute numbering is\r\nused in `Insert` mode. In a GUI, it also functions based on whether or not the\r\napp has focus.\r\n\r\nGit repository: https:\/\/github.com\/akanosora\/vimfiles\/tree\/master\/bundle\/vim-numbers\r\nOriginal version repository: https:\/\/github.com\/myusuf3\/numbers.vim","4":"This is a fork of the numbers.vim plugin originally developed by Mahdi Yusuf.\r\nThe majority of the plugin codes have been rewritten, including bug fixes and\r\nan alternative approach to determine whether a number column is needed.\r\nManual toggle commands have been removed from the original plugin.\r\n\r\nThis plugin alternates between relative numbering (`relativenumber`) and\r\nabsolute numbering (`number`) for the active window depending on the current\r\nmode. Relative numbering is used in `Normal` mode while absolute numbering is\r\nused in `Insert` mode. In a GUI, it also functions based on whether or not the\r\napp has focus.\r\n\r\nGit repository: https:\/\/github.com\/akanosora\/vimfiles\/tree\/master\/bundle\/vim-numbers\r\nOriginal version repository: https:\/\/github.com\/myusuf3\/numbers.vim","install_details":"Unpack and copy all files to ~\/.vim","5":"Unpack and copy all files to ~\/.vim","first_name":"Zhenhuan","6":"Zhenhuan","last_name":"Hu","7":"Hu","releases":[{"0":"5521","vim_version":"7.4","1":"7.4","script_version":"1.0.1","2":"1.0.1","version_comment":"Minor bug fix.","3":"Minor bug fix.","package":"vim-numbers.zip","4":"vim-numbers.zip","src_id":"24958","5":"24958","creation_date":"1486709234","6":"1486709234"}]},"5520":{"script_id":"5520","0":"5520","script_name":"Terminalogy","1":"Terminalogy","script_type":"utility","2":"utility","summary":" Show and tell with a shell ","3":" Show and tell with a shell ","description":"GitHub repository: https:\/\/github.com\/idanarye\/vim-terminalogy\r\n\r\nTerminalogy is a plugin for embedding examples of shell commands in text.","4":"GitHub repository: https:\/\/github.com\/idanarye\/vim-terminalogy\r\n\r\nTerminalogy is a plugin for embedding examples of shell commands in text.","install_details":"","5":"","first_name":"Idan","6":"Idan","last_name":"Arye","7":"Arye","releases":[{"0":"5520","vim_version":"7.4","1":"7.4","script_version":"0.1.3","2":"0.1.3","version_comment":"Fix crash problem with latest version of ALE","3":"Fix crash problem with latest version of ALE","package":"terminalogy_v0.1.3.zip","4":"terminalogy_v0.1.3.zip","src_id":"25386","5":"25386","creation_date":"1499634886","6":"1499634886"},{"0":"5520","vim_version":"7.4","1":"7.4","script_version":"0.1.2","2":"0.1.2","version_comment":"Fix problem with changed bufffer wiping process ","3":"Fix problem with changed bufffer wiping process ","package":"terminalogy_v0.1.2.zip","4":"terminalogy_v0.1.2.zip","src_id":"25224","5":"25224","creation_date":"1495481882","6":"1495481882"},{"0":"5520","vim_version":"7.4","1":"7.4","script_version":"0.1.1","2":"0.1.1","version_comment":"Fix the reading of `b:terminalogy_templates` ","3":"Fix the reading of `b:terminalogy_templates` ","package":"terminalogy_v0.1.1.zip","4":"terminalogy_v0.1.1.zip","src_id":"24930","5":"24930","creation_date":"1485550898","6":"1485550898"},{"0":"5520","vim_version":"7.4","1":"7.4","script_version":"0.1.0","2":"0.1.0","version_comment":"Initial upload","3":"Initial upload","package":"terminalogy_v0.1.0.zip","4":"terminalogy_v0.1.0.zip","src_id":"24929","5":"24929","creation_date":"1485543775","6":"1485543775"}]},"5516":{"script_id":"5516","0":"5516","script_name":"showhidefoldsby","1":"showhidefoldsby","script_type":"utility","2":"utility","summary":"Show and hide folds by various criteria.","3":"Show and hide folds by various criteria.","description":"The initial 1.0.0 release shows and hides folds by highlight group.  The author uses it on source files that have interleaved code and documentation.  One keystroke shows just the documentation (all code is folded), and another keystroke switches to the code (all documentation is folded).  Example mappings are included in the documentation.","4":"The initial 1.0.0 release shows and hides folds by highlight group.  The author uses it on source files that have interleaved code and documentation.  One keystroke shows just the documentation (all code is folded), and another keystroke switches to the code (all documentation is folded).  Example mappings are included in the documentation.","install_details":"The zip archive and repository at https:\/\/github.com\/rcaputo\/vim-showhidefoldsby.git are intended to be installed the usual ways. Put the files in the appropriate places, and generate help tags.\r\n\r\nCheck the repository if you believe the zip archive is outdated.","5":"The zip archive and repository at https:\/\/github.com\/rcaputo\/vim-showhidefoldsby.git are intended to be installed the usual ways. Put the files in the appropriate places, and generate help tags.\r\n\r\nCheck the repository if you believe the zip archive is outdated.","first_name":"Rocco","6":"Rocco","last_name":"Caputo","7":"Caputo","releases":[{"0":"5516","vim_version":"7.4","1":"7.4","script_version":"1.0.0","2":"1.0.0","version_comment":"Initial upload","3":"Initial upload","package":"showhidefoldsby.zip","4":"showhidefoldsby.zip","src_id":"24920","5":"24920","creation_date":"1485303364","6":"1485303364"}]},"5514":{"script_id":"5514","0":"5514","script_name":"z.vim","1":"z.vim","script_type":"utility","2":"utility","summary":"Help jumping to the most used directories in vim.","3":"Help jumping to the most used directories in vim.","description":"Help jumping to the most used directories in vim.\r\n\r\nThis plugin make vim work with z. So you need to install https:\/\/github.com\/rupa\/z first.\r\n\r\nIf you always do cd ~\/workspace\/document\/nice in shell. Do following to open the folder:\r\n\r\n    :Z nice\r\n\r\nSource: https:\/\/github.com\/lingceng\/z.vim","4":"Help jumping to the most used directories in vim.\r\n\r\nThis plugin make vim work with z. So you need to install https:\/\/github.com\/rupa\/z first.\r\n\r\nIf you always do cd ~\/workspace\/document\/nice in shell. Do following to open the folder:\r\n\r\n    :Z nice\r\n\r\nSource: https:\/\/github.com\/lingceng\/z.vim","install_details":"If you don't have a preferred installation method, I recommend installing Vundle.vim, and add following to your ~\/.vimrc:\r\n\r\n    Plugin 'lingceng\/z.vim'","5":"If you don't have a preferred installation method, I recommend installing Vundle.vim, and add following to your ~\/.vimrc:\r\n\r\n    Plugin 'lingceng\/z.vim'","first_name":"Kexian","6":"Kexian","last_name":"Zhong","7":"Zhong","releases":[{"0":"5514","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"z.vim-0.1.zip","4":"z.vim-0.1.zip","src_id":"24906","5":"24906","creation_date":"1484632307","6":"1484632307"}]},"5513":{"script_id":"5513","0":"5513","script_name":"istanbul.vim","1":"istanbul.vim","script_type":"utility","2":"utility","summary":"Visualize code coverage and summarize uncovered lines into quickfix","3":"Visualize code coverage and summarize uncovered lines into quickfix","description":"Visualize code coverage and summarize uncovered lines into quickfix by reading coverage.json\r\n\r\nCurrently, the following JSON output are confirmed:\r\n\r\n- istanbul (https:\/\/www.npmjs.com\/package\/istanbul)\r\n- nyc --report=json (https:\/\/www.npmjs.com\/package\/nyc)\r\n\r\n100% Vim Script! Works on Linux, Windows, and Mac OS, including non-Python(-python) and non-Ruby(-ruby) environments.\r\n\r\nThe latest version and documentation can be found at https:\/\/github.com\/retorillo\/istanbul.vim","4":"Visualize code coverage and summarize uncovered lines into quickfix by reading coverage.json\r\n\r\nCurrently, the following JSON output are confirmed:\r\n\r\n- istanbul (https:\/\/www.npmjs.com\/package\/istanbul)\r\n- nyc --report=json (https:\/\/www.npmjs.com\/package\/nyc)\r\n\r\n100% Vim Script! Works on Linux, Windows, and Mac OS, including non-Python(-python) and non-Ruby(-ruby) environments.\r\n\r\nThe latest version and documentation can be found at https:\/\/github.com\/retorillo\/istanbul.vim","install_details":"Extract the contents of the zip files into your vim runtime path.\r\n\r\nThe preferred installation method is to use Pathogen, or some other similar plugin manager.\r\n\r\nFor Vim < 7.4.1304, must additionaly install json-ponyfill.vim\r\nhttp:\/\/www.vim.org\/scripts\/script.php?script_id=5512","5":"Extract the contents of the zip files into your vim runtime path.\r\n\r\nThe preferred installation method is to use Pathogen, or some other similar plugin manager.\r\n\r\nFor Vim < 7.4.1304, must additionaly install json-ponyfill.vim\r\nhttp:\/\/www.vim.org\/scripts\/script.php?script_id=5512","first_name":"Retorillo","6":"Retorillo","last_name":" ","7":" ","releases":[{"0":"5513","vim_version":"7.0","1":"7.0","script_version":"1.3","2":"1.3","version_comment":"- Support nyc output (coverage\/coverage-final.json) and improve JSON search procedure\r\n  - Many thanks: Anders Th\u00c3\u00b8gersen (@aklt)\r\n- Add option to use location-list instead of quickfix g:istanbul#store\r\n- Add IstanbulToggle\r\n- Improve and specialize IstanbulNext and IstanbulBack behaviors\r\n- Add JSON cache to improve performance\r\n- For Vim < 7.4.1304, to decode large JSON, use Python if possible, otherwise show progress bar (Require json-ponyfill.vim >= v1.1)\r\n- Improve error message format\r\n- Fix miscellaneous bugs","3":"- Support nyc output (coverage\/coverage-final.json) and improve JSON search procedure\r\n  - Many thanks: Anders Th\u00c3\u00b8gersen (@aklt)\r\n- Add option to use location-list instead of quickfix g:istanbul#store\r\n- Add IstanbulToggle\r\n- Improve and specialize IstanbulNext and IstanbulBack behaviors\r\n- Add JSON cache to improve performance\r\n- For Vim < 7.4.1304, to decode large JSON, use Python if possible, otherwise show progress bar (Require json-ponyfill.vim >= v1.1)\r\n- Improve error message format\r\n- Fix miscellaneous bugs","package":"istanbul.vim.zip","4":"istanbul.vim.zip","src_id":"25071","5":"25071","creation_date":"1491760191","6":"1491760191"},{"0":"5513","vim_version":"7.0","1":"7.0","script_version":"1.2","2":"1.2","version_comment":"- QuickFix is enabled from this version. Once InstanbulUpdate is invoked, can access coverage information from QuickFix commands like \":clist\" and \":cn\".\r\n- Fix bug that IstanbulUpdate always remove all signs including non-current buffer.","3":"- QuickFix is enabled from this version. Once InstanbulUpdate is invoked, can access coverage information from QuickFix commands like \":clist\" and \":cn\".\r\n- Fix bug that IstanbulUpdate always remove all signs including non-current buffer.","package":"istanbul.vim.zip","4":"istanbul.vim.zip","src_id":"24998","5":"24998","creation_date":"1488036918","6":"1488036918"},{"0":"5513","vim_version":"7.0","1":"7.0","script_version":"1.1","2":"1.1","version_comment":"- Change to json-ponyfill.vim\r\n- Remove keymaps to prevent confliction with CTRL-I (Go to newer cursor position)","3":"- Change to json-ponyfill.vim\r\n- Remove keymaps to prevent confliction with CTRL-I (Go to newer cursor position)","package":"istanbul.vim.zip","4":"istanbul.vim.zip","src_id":"24911","5":"24911","creation_date":"1484991963","6":"1484991963"},{"0":"5513","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"istanbul.vim.zip","4":"istanbul.vim.zip","src_id":"24893","5":"24893","creation_date":"1484276555","6":"1484276555"}]},"5512":{"script_id":"5512","0":"5512","script_name":"json-ponyfill.vim","1":"json-ponyfill.vim","script_type":"utility","2":"utility","summary":"Provide json_decode and json_encode to VIM < 7.4.1304","3":"Provide json_decode and json_encode to VIM < 7.4.1304","description":"Provide json_decode and json_encode to VIM < 7.4.1304\r\n\r\nThe latest version can be found at https:\/\/github.com\/retorillo\/json-ponyfill.vim\r\n","4":"Provide json_decode and json_encode to VIM < 7.4.1304\r\n\r\nThe latest version can be found at https:\/\/github.com\/retorillo\/json-ponyfill.vim\r\n","install_details":"Extract the contents of the zip files into your vim runtime path.\r\n\r\nThe preferred installation method is to use Pathogen or some other similar plugin manager.","5":"Extract the contents of the zip files into your vim runtime path.\r\n\r\nThe preferred installation method is to use Pathogen or some other similar plugin manager.","first_name":"Retorillo","6":"Retorillo","last_name":" ","7":" ","releases":[{"0":"5512","vim_version":"7.0","1":"7.0","script_version":"1.1","2":"1.1","version_comment":"The following options are implemented to handle performance problem working with large JSON:\r\n\r\n- Use Python to process faster, if possible\r\n- Display progress bar when processing in Vim Script","3":"The following options are implemented to handle performance problem working with large JSON:\r\n\r\n- Use Python to process faster, if possible\r\n- Display progress bar when processing in Vim Script","package":"json-ponyfill.vim.zip","4":"json-ponyfill.vim.zip","src_id":"25069","5":"25069","creation_date":"1491759364","6":"1491759364"},{"0":"5512","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"- Change name to json-ponyfill.vim\r\n- Implement json_ponyfill#json_encode","3":"- Change name to json-ponyfill.vim\r\n- Implement json_ponyfill#json_encode","package":"json-ponyfill.vim.zip","4":"json-ponyfill.vim.zip","src_id":"24910","5":"24910","creation_date":"1484991811","6":"1484991811"},{"0":"5512","vim_version":"7.0","1":"7.0","script_version":"0.9","2":"0.9","version_comment":"Initial upload","3":"Initial upload","package":"json.vim.zip","4":"json.vim.zip","src_id":"24892","5":"24892","creation_date":"1484276225","6":"1484276225"}]},"5511":{"script_id":"5511","0":"5511","script_name":"ruta.vim","1":"ruta.vim","script_type":"syntax","2":"syntax","summary":"Syntax for Apache UIMA Ruta Script","3":"Syntax for Apache UIMA Ruta Script","description":"Syntax definition for Apache UIMA Ruta rules script. Currently, it only aims to help quick updates on the server.\r\n\r\nMajor updates will be available here, but most up-to-date version with minor changes can be found at https:\/\/github.com\/soysal\/ruta.vim\r\n\r\n","4":"Syntax definition for Apache UIMA Ruta rules script. Currently, it only aims to help quick updates on the server.\r\n\r\nMajor updates will be available here, but most up-to-date version with minor changes can be found at https:\/\/github.com\/soysal\/ruta.vim\r\n\r\n","install_details":"Extract zip file to your ~\/.vim folder.","5":"Extract zip file to your ~\/.vim folder.","first_name":"Ergin","6":"Ergin","last_name":"Soysal","7":"Soysal","releases":[{"0":"5511","vim_version":"7.0","1":"7.0","script_version":"0.2","2":"0.2","version_comment":"Initial upload","3":"Initial upload","package":"ruta-vim-0.2.zip","4":"ruta-vim-0.2.zip","src_id":"24886","5":"24886","creation_date":"1483934496","6":"1483934496"}]},"5510":{"script_id":"5510","0":"5510","script_name":"madlang-vim","1":"madlang-vim","script_type":"syntax","2":"syntax","summary":"Syntax highlighting for the Madlibs DSL","3":"Syntax highlighting for the Madlibs DSL","description":"View readme here:\r\nhttps:\/\/github.com\/vmchale\/madlang-vim#readme","4":"View readme here:\r\nhttps:\/\/github.com\/vmchale\/madlang-vim#readme","install_details":"","5":"","first_name":"Vanessa","6":"Vanessa","last_name":"McHale","7":"McHale","releases":[{"0":"5510","vim_version":"7.0","1":"7.0","script_version":"0.1.0.0","2":"0.1.0.0","version_comment":"Initial upload","3":"Initial upload","package":"madlang.vim","4":"madlang.vim","src_id":"24882","5":"24882","creation_date":"1483904438","6":"1483904438"}]},"5509":{"script_id":"5509","0":"5509","script_name":"spotdiff.vim","1":"spotdiff.vim","script_type":"utility","2":"utility","summary":"A range and area selectable diffthis to compare partially","3":"A range and area selectable diffthis to compare partially","description":"Vim provides diff mode which is useful to see differences between windows. However, it always shows the differences for entire line. And can not compare a sequence of words within a line, and sentences and paragraphs which are separated into several lines.\r\n\r\nTo compare partially everywhere in windows, this plugin provides two groups of commands, which are alternative to vim original :diffthis, :diffoff, and :diffupdate. One is for which allows to select a range of lines to be compared in diff mode. Another is for which allows to select the Visual area to be compared in non-diff normal mode. Both work independently in a tab page.\r\n\r\nFor details and demo samples, please visit the following git repository: https:\/\/github.com\/rickhowe\/spotdiff.vim","4":"Vim provides diff mode which is useful to see differences between windows. However, it always shows the differences for entire line. And can not compare a sequence of words within a line, and sentences and paragraphs which are separated into several lines.\r\n\r\nTo compare partially everywhere in windows, this plugin provides two groups of commands, which are alternative to vim original :diffthis, :diffoff, and :diffupdate. One is for which allows to select a range of lines to be compared in diff mode. Another is for which allows to select the Visual area to be compared in non-diff normal mode. Both work independently in a tab page.\r\n\r\nFor details and demo samples, please visit the following git repository: https:\/\/github.com\/rickhowe\/spotdiff.vim","install_details":"Install 'rickhowe\/spotdiff.vim' by using your plugin manager. Or manually unzip and copy all folders in your ~\/.vim or ~\/vimfiles.","5":"Install 'rickhowe\/spotdiff.vim' by using your plugin manager. Or manually unzip and copy all folders in your ~\/.vim or ~\/vimfiles.","first_name":"Rick","6":"Rick","last_name":"Howe","7":"Howe","releases":[{"0":"5509","vim_version":"8.2","1":"8.2","script_version":"5.1","2":"5.1","version_comment":"Added to open a temporary new window at left or right in :Diffthis command.","3":"Added to open a temporary new window at left or right in :Diffthis command.","package":"spotdiff5.1.zip","4":"spotdiff5.1.zip","src_id":"28593","5":"28593","creation_date":"1705646063","6":"1705646063"},{"0":"5509","vim_version":"8.2","1":"8.2","script_version":"5.0","2":"5.0","version_comment":"Changed to support vim 8.2 and nvim 0.4.4 or later.","3":"Changed to support vim 8.2 and nvim 0.4.4 or later.","package":"spotdiff5.0.zip","4":"spotdiff5.0.zip","src_id":"28393","5":"28393","creation_date":"1679865660","6":"1679865660"},{"0":"5509","vim_version":"8.0","1":"8.0","script_version":"4.5","2":"4.5","version_comment":"Updated g:DiffUnit and g:DiffColors options to reflect those updated in the diffchar.vim 9.1.","3":"Updated g:DiffUnit and g:DiffColors options to reflect those updated in the diffchar.vim 9.1.","package":"spotdiff4.5.zip","4":"spotdiff4.5.zip","src_id":"28237","5":"28237","creation_date":"1666976223","6":"1666976223"},{"0":"5509","vim_version":"7.4","1":"7.4","script_version":"2.2","2":"2.2","version_comment":"Added :Diffupdate command.","3":"Added :Diffupdate command.","package":"spotdiff2.2.zip","4":"spotdiff2.2.zip","src_id":"25683","5":"25683","creation_date":"1512279687","6":"1512279687"},{"0":"5509","vim_version":"7.4","1":"7.4","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"spotdiff1.0.zip","4":"spotdiff1.0.zip","src_id":"24876","5":"24876","creation_date":"1483694330","6":"1483694330"}]},"5508":{"script_id":"5508","0":"5508","script_name":"greek_mac.vim","1":"greek_mac.vim","script_type":"utility","2":"utility","summary":"Vim keymap to write traditional (\u00e2\u0080\u009cpolytonic\u00e2\u0080\u009d) Greek in the Mac OS way.","3":"Vim keymap to write traditional (\u00e2\u0080\u009cpolytonic\u00e2\u0080\u009d) Greek in the Mac OS way.","description":"Vim keymap that enables one to write traditional (\u00e2\u0080\u009cpolytonic\u00e2\u0080\u009d) Greek.\r\n\r\nThe keymap is based on the corresponding Mac OS keyboard layout for polytonic Greek.\r\nAll diacritics except the \u00e2\u0080\u009cbreve below\u00e2\u0080\u009d are typed before the corresponding letter.\r\nIn case of two diacritics the order is not important.\r\nThe code is also available at \"https:\/\/github.com\/christosc\/greek_mac\" .\r\n\r\nAccents\r\n-----------\r\nacute         ;\r\ngrave         ]\r\ncircumflex  [\r\n\r\n\r\nSmooth breathing\r\n------------------------\r\nsmooth         '\r\n+ acute        \/\r\n+ grave        =\r\n+ circumflex  -\r\n\r\n\r\nRough breathing\r\n----------------------\r\nrough          \"\r\n+ acute        ?\r\n+ grave        +\r\n+ circumflex  _\r\n\r\n\r\nIota subscript\r\n------------------\r\niota subscript                      {\r\n+ acute                              ; {\r\n+ grave                              ] {\r\n+ smooth                           ' {\r\n+ smooth and acute          \/ {\r\n+ smooth and grave         = {\r\n+ smooth and circumflex  - {\r\n+ rough                            \" {\r\n+ rough and acute           ? {\r\n+ rough and grave           + {\r\n+ rough and circumflex    _ {\r\n\r\n\r\nDiaeresis\/Dialytika\r\n-------------------------\r\ndiaeresis  :\r\n+ acute    :;\r\n+ grave    :]\r\n\r\n\r\nBreve Below\r\n------------------\r\nbreve below   \\u  \r\nε̮                     e\\u  \r\nι̮                      i\\u  \r\ntilde below      ~\r\nι̰                      i~\r\n\r\n\r\nPunctuation\r\n----------------\r\nMiddle dot (\u00e2\u0080\u009cano teleia\u00e2\u0080\u009d)   ; . or W\r\nApostrophe                      '\r\nLeft quote                        <<\r\nRight quote                      >>\r\nen dash                            --\r\nem dash                           ---\r\n\r\n\r\nSymbols\r\n------------\r\nEuro sign                      E$\r\nNumerical Sign             ;#\r\nLower numerical sign   ;##\r\nStigma (Ϛ)                    #ST\r\nSmall stigma (ϛ)           #st\r\nKoppa (Ϟ)                     #Q\r\nSmall koppa (ϟ)            #q\r\nSampi (Ϡ)                     #SP\r\nSmall sampi (ϡ)            #sp\r\nDigamma (Ϝ)                #G\r\nKai ligature (ϗ)             &&\r\nTheta symbol (ϑ)         ;u\r\nKappa symbol (ϰ)        ;k\r\nBeta symbol (ϐ)           ;b\r\nEpsilon symbol (ϵ)       !e\r\nPhi symbol (ϕ)             ;f\r\nPi symbol (ϖ)              ;p\r\nRho symbol (ϱ)            ;r\r\n\r\nYou can find more keyboard shortcuts by looking at the code of the keymap.","4":"Vim keymap that enables one to write traditional (\u00e2\u0080\u009cpolytonic\u00e2\u0080\u009d) Greek.\r\n\r\nThe keymap is based on the corresponding Mac OS keyboard layout for polytonic Greek.\r\nAll diacritics except the \u00e2\u0080\u009cbreve below\u00e2\u0080\u009d are typed before the corresponding letter.\r\nIn case of two diacritics the order is not important.\r\nThe code is also available at \"https:\/\/github.com\/christosc\/greek_mac\" .\r\n\r\nAccents\r\n-----------\r\nacute         ;\r\ngrave         ]\r\ncircumflex  [\r\n\r\n\r\nSmooth breathing\r\n------------------------\r\nsmooth         '\r\n+ acute        \/\r\n+ grave        =\r\n+ circumflex  -\r\n\r\n\r\nRough breathing\r\n----------------------\r\nrough          \"\r\n+ acute        ?\r\n+ grave        +\r\n+ circumflex  _\r\n\r\n\r\nIota subscript\r\n------------------\r\niota subscript                      {\r\n+ acute                              ; {\r\n+ grave                              ] {\r\n+ smooth                           ' {\r\n+ smooth and acute          \/ {\r\n+ smooth and grave         = {\r\n+ smooth and circumflex  - {\r\n+ rough                            \" {\r\n+ rough and acute           ? {\r\n+ rough and grave           + {\r\n+ rough and circumflex    _ {\r\n\r\n\r\nDiaeresis\/Dialytika\r\n-------------------------\r\ndiaeresis  :\r\n+ acute    :;\r\n+ grave    :]\r\n\r\n\r\nBreve Below\r\n------------------\r\nbreve below   \\u  \r\nε̮                     e\\u  \r\nι̮                      i\\u  \r\ntilde below      ~\r\nι̰                      i~\r\n\r\n\r\nPunctuation\r\n----------------\r\nMiddle dot (\u00e2\u0080\u009cano teleia\u00e2\u0080\u009d)   ; . or W\r\nApostrophe                      '\r\nLeft quote                        <<\r\nRight quote                      >>\r\nen dash                            --\r\nem dash                           ---\r\n\r\n\r\nSymbols\r\n------------\r\nEuro sign                      E$\r\nNumerical Sign             ;#\r\nLower numerical sign   ;##\r\nStigma (Ϛ)                    #ST\r\nSmall stigma (ϛ)           #st\r\nKoppa (Ϟ)                     #Q\r\nSmall koppa (ϟ)            #q\r\nSampi (Ϡ)                     #SP\r\nSmall sampi (ϡ)            #sp\r\nDigamma (Ϝ)                #G\r\nKai ligature (ϗ)             &&\r\nTheta symbol (ϑ)         ;u\r\nKappa symbol (ϰ)        ;k\r\nBeta symbol (ϐ)           ;b\r\nEpsilon symbol (ϵ)       !e\r\nPhi symbol (ϕ)             ;f\r\nPi symbol (ϖ)              ;p\r\nRho symbol (ϱ)            ;r\r\n\r\nYou can find more keyboard shortcuts by looking at the code of the keymap.","install_details":"Copy the file greek_mac.vim to your home .vim  keymap directory \r\n  (~\/.vim\/keymap\/). If the directory does not exist, create it. \r\n\r\nAdd to .vimrc the following:\r\n\r\nset keymap=greek_mac\r\nset iminsert=0\r\nset imsearch=-1\r\n\r\nSet your terminal or gvim to use a font that includes the \u00e2\u0080\u009cextended\u00e2\u0080\u009d Greek characters and symbols. \r\nExamples of suitable fonts include the following:\r\n\r\nMenlo\r\nDejavu Sans mono \r\nConsolas \r\n\r\nYou can change keyboard with Ctrl-^ in insert and command-line modes.","5":"Copy the file greek_mac.vim to your home .vim  keymap directory \r\n  (~\/.vim\/keymap\/). If the directory does not exist, create it. \r\n\r\nAdd to .vimrc the following:\r\n\r\nset keymap=greek_mac\r\nset iminsert=0\r\nset imsearch=-1\r\n\r\nSet your terminal or gvim to use a font that includes the \u00e2\u0080\u009cextended\u00e2\u0080\u009d Greek characters and symbols. \r\nExamples of suitable fonts include the following:\r\n\r\nMenlo\r\nDejavu Sans mono \r\nConsolas \r\n\r\nYou can change keyboard with Ctrl-^ in insert and command-line modes.","first_name":"Christos","6":"Christos","last_name":"Chryssochoidis","7":"Chryssochoidis","releases":[{"0":"5508","vim_version":"7.0","1":"7.0","script_version":"1.0.5","2":"1.0.5","version_comment":"Add shortcut for tilde below, and change the one for breve below.","3":"Add shortcut for tilde below, and change the one for breve below.","package":"greek_mac.vim","4":"greek_mac.vim","src_id":"25078","5":"25078","creation_date":"1492446496","6":"1492446496"}]},"5507":{"script_id":"5507","0":"5507","script_name":"Arcadia","1":"Arcadia","script_type":"color scheme","2":"color scheme","summary":"Term and Gui","3":"Term and Gui","description":"For screenshots, color options, and future downloads check out the GitHub repo here: https:\/\/github.com\/AlessandroYorba\/Arcadia\r\n","4":"For screenshots, color options, and future downloads check out the GitHub repo here: https:\/\/github.com\/AlessandroYorba\/Arcadia\r\n","install_details":"For Unix users, place arcadia.vim in ~\/.vim\/colors \r\nWindows users, place arcadia.vim in ~\\vimfiles\\colors \r\n\r\nor use your favorite package manager","5":"For Unix users, place arcadia.vim in ~\/.vim\/colors \r\nWindows users, place arcadia.vim in ~\\vimfiles\\colors \r\n\r\nor use your favorite package manager","first_name":"Alessandro","6":"Alessandro","last_name":"Yorba","7":"Yorba","releases":[{"0":"5507","vim_version":"7.0","1":"7.0","script_version":"0b8b26e","2":"0b8b26e","version_comment":"Enjoy","3":"Enjoy","package":"arcadia.vim","4":"arcadia.vim","src_id":"26943","5":"26943","creation_date":"1580309150","6":"1580309150"},{"0":"5507","vim_version":"7.0","1":"7.0","script_version":"3acdc8d","2":"3acdc8d","version_comment":"added light version and revised colors for better cohesion","3":"added light version and revised colors for better cohesion","package":"arcadia.vim","4":"arcadia.vim","src_id":"25617","5":"25617","creation_date":"1508821456","6":"1508821456"},{"0":"5507","vim_version":"7.0","1":"7.0","script_version":"0.01","2":"0.01","version_comment":"complete redesign. Terminal themes and Xresources coming soon.","3":"complete redesign. Terminal themes and Xresources coming soon.","package":"arcadia.vim","4":"arcadia.vim","src_id":"25245","5":"25245","creation_date":"1495662490","6":"1495662490"}]},"5506":{"script_id":"5506","0":"5506","script_name":"ipynb_notedown.vim","1":"ipynb_notedown.vim","script_type":"utility","2":"utility","summary":"plugin for editing jupyter notebook (ipynb) files through notedown","3":"plugin for editing jupyter notebook (ipynb) files through notedown","description":"When you open a Jupyter Notebook (*.ipynb) file, it is automatically\r\nconverted from json to markdown through the `notedown` utility\r\n(https:\/\/github.com\/aaren\/notedown). Upon saving the file, the content is\r\nconverted back to the json notebook format.\r\n\r\nThe purpose of this plugin is to allow editing notebooks directly in vim.\r\nThe conversion json -> markdown -> json is relatively lossless, although\r\nsome of the restrictions of the `notedown` utility apply. In particular,\r\nnotebook and cell metadata are lost, and consecutive markdown cells are\r\nmerged into once cell.\r\n\r\nNOTE: This plugin is superseded by the jupytext.vim plugin (vimscript #5764)\r\n\r\nThis script is developed at https:\/\/github.com\/goerz\/ipynb_notedown.vim\r\n\r\nSee documentation in script for details.","4":"When you open a Jupyter Notebook (*.ipynb) file, it is automatically\r\nconverted from json to markdown through the `notedown` utility\r\n(https:\/\/github.com\/aaren\/notedown). Upon saving the file, the content is\r\nconverted back to the json notebook format.\r\n\r\nThe purpose of this plugin is to allow editing notebooks directly in vim.\r\nThe conversion json -> markdown -> json is relatively lossless, although\r\nsome of the restrictions of the `notedown` utility apply. In particular,\r\nnotebook and cell metadata are lost, and consecutive markdown cells are\r\nmerged into once cell.\r\n\r\nNOTE: This plugin is superseded by the jupytext.vim plugin (vimscript #5764)\r\n\r\nThis script is developed at https:\/\/github.com\/goerz\/ipynb_notedown.vim\r\n\r\nSee documentation in script for details.","install_details":" Copy the ipynb_notedown.vim script to your vim plugin directory (e.g. $HOME\/.vim\/plugin)","5":" Copy the ipynb_notedown.vim script to your vim plugin directory (e.g. $HOME\/.vim\/plugin)","first_name":"Michael","6":"Michael","last_name":"Goerz","7":"Goerz","releases":[{"0":"5506","vim_version":"7.0","1":"7.0","script_version":"0.1.1","2":"0.1.1","version_comment":"Add option g:notedown_enable to disable plugin","3":"Add option g:notedown_enable to disable plugin","package":"ipynb_notedown.vim","4":"ipynb_notedown.vim","src_id":"24834","5":"24834","creation_date":"1482789961","6":"1482789961"},{"0":"5506","vim_version":"7.0","1":"7.0","script_version":"0.1.0","2":"0.1.0","version_comment":"Initial upload","3":"Initial upload","package":"ipynb_notedown.vim","4":"ipynb_notedown.vim","src_id":"24832","5":"24832","creation_date":"1482783006","6":"1482783006"}]},"5505":{"script_id":"5505","0":"5505","script_name":"vmux","1":"vmux","script_type":"utility","2":"utility","summary":"vim\/neovim session handler within tmux","3":"vim\/neovim session handler within tmux","description":"vmux leverages vim's server feature to have just one instance of vim running in your tmux session or even globally if you like.\r\n\r\nvmux is a simple wrapper around vim\/neovim\/kakoune that will automatically start a server.  Subsequent calls of the wrapper script will open new files in the existing vim server.\r\n\r\nDevelopment happens here: https:\/\/github.com\/jceb\/vmux","4":"vmux leverages vim's server feature to have just one instance of vim running in your tmux session or even globally if you like.\r\n\r\nvmux is a simple wrapper around vim\/neovim\/kakoune that will automatically start a server.  Subsequent calls of the wrapper script will open new files in the existing vim server.\r\n\r\nDevelopment happens here: https:\/\/github.com\/jceb\/vmux","install_details":"Run:\r\n\r\n  make install DESTDIR=~\/.local\r\n  # make sure ~\/.local\/bin is in your PATH variable\r\n\r\nStart tmux, run vim with the following command:\r\n\r\n  vim.vmux FILE\r\n\r\nOpen a new pane in tmux and edit another file by running:\r\n\r\n  vim.vmux ANOTHER_FILE","5":"Run:\r\n\r\n  make install DESTDIR=~\/.local\r\n  # make sure ~\/.local\/bin is in your PATH variable\r\n\r\nStart tmux, run vim with the following command:\r\n\r\n  vim.vmux FILE\r\n\r\nOpen a new pane in tmux and edit another file by running:\r\n\r\n  vim.vmux ANOTHER_FILE","first_name":"Jan Christoph","6":"Jan Christoph","last_name":"Ebersbach","7":"Ebersbach","releases":[{"0":"5505","vim_version":"7.0","1":"7.0","script_version":"0.6.1","2":"0.6.1","version_comment":"Fix syntax error","3":"Fix syntax error","package":"vmux-0.6.1.tar.gz","4":"vmux-0.6.1.tar.gz","src_id":"24856","5":"24856","creation_date":"1482993805","6":"1482993805"},{"0":"5505","vim_version":"7.0","1":"7.0","script_version":"0.6","2":"0.6","version_comment":"Add support for kakoune","3":"Add support for kakoune","package":"vmux-0.6.tar.gz","4":"vmux-0.6.tar.gz","src_id":"24830","5":"24830","creation_date":"1482742059","6":"1482742059"},{"0":"5505","vim_version":"7.0","1":"7.0","script_version":"0.5","2":"0.5","version_comment":"Initial upload","3":"Initial upload","package":"vmux-v0.5.tar.gz","4":"vmux-v0.5.tar.gz","src_id":"24829","5":"24829","creation_date":"1482739595","6":"1482739595"}]},"5504":{"script_id":"5504","0":"5504","script_name":"Sprint","1":"Sprint","script_type":"utility","2":"utility","summary":"Async file running","3":"Async file running","description":"Sprint\r\n\r\nAsync file running\r\n\r\ntl;dr\r\nJust like any IDE's run button this plugins just runs your code.\r\n\r\nFor more info on the plugin check the github repo\r\nhttps:\/\/github.com\/pedsm\/sprint\/tree\/v1.0","4":"Sprint\r\n\r\nAsync file running\r\n\r\ntl;dr\r\nJust like any IDE's run button this plugins just runs your code.\r\n\r\nFor more info on the plugin check the github repo\r\nhttps:\/\/github.com\/pedsm\/sprint\/tree\/v1.0","install_details":"Installing\r\n\r\nUse any package manager of your liking if you have Vim 8.0 and Async run. My recommendation is to use vundle with the following code.\r\n\r\n\"This checks for vim 8.0 or above before installing plugins\r\nif v:version >= 800\r\n    Plugin 'skywind3000\/asyncrun.vim'\r\n    Plugin 'pedsm\/sprint'\r\nendif","5":"Installing\r\n\r\nUse any package manager of your liking if you have Vim 8.0 and Async run. My recommendation is to use vundle with the following code.\r\n\r\n\"This checks for vim 8.0 or above before installing plugins\r\nif v:version >= 800\r\n    Plugin 'skywind3000\/asyncrun.vim'\r\n    Plugin 'pedsm\/sprint'\r\nendif","first_name":"Pedro","6":"Pedro","last_name":"Mendonca","7":"Mendonca","releases":[{"0":"5504","vim_version":"8.0","1":"8.0","script_version":"1.1.1","2":"1.1.1","version_comment":"Optimizations on Haskell Sprints\r\nAdded SprintStop function\r\nAdded customization options","3":"Optimizations on Haskell Sprints\r\nAdded SprintStop function\r\nAdded customization options","package":"sprint-1.1.1.zip","4":"sprint-1.1.1.zip","src_id":"24837","5":"24837","creation_date":"1482812374","6":"1482812374"},{"0":"5504","vim_version":"8.0","1":"8.0","script_version":"v1.0","2":"v1.0","version_comment":"Initial upload","3":"Initial upload","package":"sprint-1.0.zip","4":"sprint-1.0.zip","src_id":"24828","5":"24828","creation_date":"1482712219","6":"1482712219"}]},"5503":{"script_id":"5503","0":"5503","script_name":"yarn.vim","1":"yarn.vim","script_type":"utility","2":"utility","summary":"Yarn for Vim.","3":"Yarn for Vim.","description":"Repository: \r\n  https:\/\/github.com\/trkw\/yarn.vim \r\n\r\n\r\nWorking and using Yarn in Vim editor. \r\nyarn.vim is a Vim plugin to manage and work with Yarn easily. \r\n","4":"Repository: \r\n  https:\/\/github.com\/trkw\/yarn.vim \r\n\r\n\r\nWorking and using Yarn in Vim editor. \r\nyarn.vim is a Vim plugin to manage and work with Yarn easily. \r\n","install_details":"","5":"","first_name":"Naohiro","6":"Naohiro","last_name":"Terakawa","7":"Terakawa","releases":[{"0":"5503","vim_version":"8.0","1":"8.0","script_version":"0.1.0","2":"0.1.0","version_comment":"Initial upload","3":"Initial upload","package":"yarn.vim","4":"yarn.vim","src_id":"24824","5":"24824","creation_date":"1482679655","6":"1482679655"}]},"5502":{"script_id":"5502","0":"5502","script_name":"vim-workspace","1":"vim-workspace","script_type":"utility","2":"utility","summary":"Automated Vim session management and file auto-save","3":"Automated Vim session management and file auto-save","description":"The latest version can be found in the vim-workspace GitHub repository:\r\nhttps:\/\/github.com\/thaerkh\/vim-workspace\r\n\r\nDemo:\r\nhttps:\/\/raw.githubusercontent.com\/thaerkh\/vim-workspace\/master\/wiki\/screenshots\/demo.gif\r\n\r\nContents:   \r\n1.   Workspace Sessions  \r\n1.1. Hidden Buffers      \r\n1.2. Undo History        \r\n1.3. Omni Completion     \r\n2.   Autosave            \r\n2.1. Untrailing Spaces   \r\n2.2. Autosave Ignore List\r\n\r\n\r\nFor details and configuration options on each feature, please refer to GitHub repo linked above, or the README.md file in the latest package listed below.","4":"The latest version can be found in the vim-workspace GitHub repository:\r\nhttps:\/\/github.com\/thaerkh\/vim-workspace\r\n\r\nDemo:\r\nhttps:\/\/raw.githubusercontent.com\/thaerkh\/vim-workspace\/master\/wiki\/screenshots\/demo.gif\r\n\r\nContents:   \r\n1.   Workspace Sessions  \r\n1.1. Hidden Buffers      \r\n1.2. Undo History        \r\n1.3. Omni Completion     \r\n2.   Autosave            \r\n2.1. Untrailing Spaces   \r\n2.2. Autosave Ignore List\r\n\r\n\r\nFor details and configuration options on each feature, please refer to GitHub repo linked above, or the README.md file in the latest package listed below.","install_details":"Plugin managers are recommended, such as Plug or Vundle, which directly pull from the git repo for the latest version. Installation instructions for such plugins are available in the README.md file.\r\nAny configuration available is also documented in the README.md file.\r\n\r\nFor those that prefer a static variant, decompress the archive's folder content into your ~\/.vim directory, which should place the plugin into the path ~\/.vim\/plugin\/workspace.vim\r\n","5":"Plugin managers are recommended, such as Plug or Vundle, which directly pull from the git repo for the latest version. Installation instructions for such plugins are available in the README.md file.\r\nAny configuration available is also documented in the README.md file.\r\n\r\nFor those that prefer a static variant, decompress the archive's folder content into your ~\/.vim directory, which should place the plugin into the path ~\/.vim\/plugin\/workspace.vim\r\n","first_name":"Thaer","6":"Thaer","last_name":"Khawaja","7":"Khawaja","releases":[{"0":"5502","vim_version":"8.0","1":"8.0","script_version":"1.8.3","2":"1.8.3","version_comment":"Includes various functionality tweaks for the autosave feature.","3":"Includes various functionality tweaks for the autosave feature.","package":"vim-workspace-1.8.3.tar.gz","4":"vim-workspace-1.8.3.tar.gz","src_id":"25507","5":"25507","creation_date":"1502660347","6":"1502660347"},{"0":"5502","vim_version":"8.0","1":"8.0","script_version":"1.8.2","2":"1.8.2","version_comment":"Changes: \r\nsessions won't load if vim is being opened with stdin. \r\nAutocommand trigger threshold is lowered to be more responsive. \r\nInclude nerdtree filetypes in autosave ignore defaults.","3":"Changes: \r\nsessions won't load if vim is being opened with stdin. \r\nAutocommand trigger threshold is lowered to be more responsive. \r\nInclude nerdtree filetypes in autosave ignore defaults.","package":"vim-workspace-1.8.2.tar.gz","4":"vim-workspace-1.8.2.tar.gz","src_id":"25027","5":"25027","creation_date":"1489255715","6":"1489255715"},{"0":"5502","vim_version":"8.0","1":"8.0","script_version":"1.8.1","2":"1.8.1","version_comment":"Release notes:\r\nPulled sensible settings as a feature.\r\nFix session load flicker issue (set nocompatible before session load).\r\nSet any user defined autoread value after turning autosave off.\r\n","3":"Release notes:\r\nPulled sensible settings as a feature.\r\nFix session load flicker issue (set nocompatible before session load).\r\nSet any user defined autoread value after turning autosave off.\r\n","package":"vim-workspace-1.8.1.tar.gz","4":"vim-workspace-1.8.1.tar.gz","src_id":"24972","5":"24972","creation_date":"1487215236","6":"1487215236"},{"0":"5502","vim_version":"8.0","1":"8.0","script_version":"1.8.0","2":"1.8.0","version_comment":"Separate indent guides feature into its own plugin.","3":"Separate indent guides feature into its own plugin.","package":"vim-workspace-1.8.0.tar.gz","4":"vim-workspace-1.8.0.tar.gz","src_id":"24966","5":"24966","creation_date":"1487016175","6":"1487016175"},{"0":"5502","vim_version":"8.0","1":"8.0","script_version":"1.7.3","2":"1.7.3","version_comment":"Release notes: \r\n- Add ToggleAutosave option. \r\n- Add option to to always have autosave on (including when not in a session). \r\n- bug fix: don't autosave when popup menu is visible (preview buffer updates trigger BufLeave autocommand). \r\n- bug fix: CloseHiddenBuffers command now uses wipe instead of delete (fully removes buffers).","3":"Release notes: \r\n- Add ToggleAutosave option. \r\n- Add option to to always have autosave on (including when not in a session). \r\n- bug fix: don't autosave when popup menu is visible (preview buffer updates trigger BufLeave autocommand). \r\n- bug fix: CloseHiddenBuffers command now uses wipe instead of delete (fully removes buffers).","package":"vim-workspace-1.7.3.tar.gz","4":"vim-workspace-1.7.3.tar.gz","src_id":"24961","5":"24961","creation_date":"1486967723","6":"1486967723"},{"0":"5502","vim_version":"8.0","1":"8.0","script_version":"1.7.2","2":"1.7.2","version_comment":"More updates to indent guides feature:\r\nFix edge case with toggles (when not enabled by default, toggles wouldn't work).\r\nSyntax match in a more friendly way (plays nicely with external plugins that might work on the same syntax group).\r\nAdd option for first level of indent guides (default to 0).","3":"More updates to indent guides feature:\r\nFix edge case with toggles (when not enabled by default, toggles wouldn't work).\r\nSyntax match in a more friendly way (plays nicely with external plugins that might work on the same syntax group).\r\nAdd option for first level of indent guides (default to 0).","package":"vim-workspace-1.7.2.tar.gz","4":"vim-workspace-1.7.2.tar.gz","src_id":"24948","5":"24948","creation_date":"1486237080","6":"1486237080"},{"0":"5502","vim_version":"8.0","1":"8.0","script_version":"1.7.1","2":"1.7.1","version_comment":"Bug fix: Handle edge cases where indent guides won't toggle correctly if a buffer's opened in multiple windows. Syntax matches are ensured to be loaded, including colorscheme changes.","3":"Bug fix: Handle edge cases where indent guides won't toggle correctly if a buffer's opened in multiple windows. Syntax matches are ensured to be loaded, including colorscheme changes.","package":"vim-workspace-1.7.1.tar.gz","4":"vim-workspace-1.7.1.tar.gz","src_id":"24946","5":"24946","creation_date":"1486022765","6":"1486022765"},{"0":"5502","vim_version":"8.0","1":"8.0","script_version":"1.7.0","2":"1.7.0","version_comment":"New feature: optional indent guides (with ignore list) - cleanly distinguish tabs from space indents.\r\nBug fix: don't try to autosave read-only files.\r\nBug fix: Fixed issue where terminals with focus triggers could trigger autosave (and fail) if switching between windows in command mode.","3":"New feature: optional indent guides (with ignore list) - cleanly distinguish tabs from space indents.\r\nBug fix: don't try to autosave read-only files.\r\nBug fix: Fixed issue where terminals with focus triggers could trigger autosave (and fail) if switching between windows in command mode.","package":"vim-workspace-1.7.0.tar.gz","4":"vim-workspace-1.7.0.tar.gz","src_id":"24938","5":"24938","creation_date":"1485939195","6":"1485939195"},{"0":"5502","vim_version":"7.0","1":"7.0","script_version":"1.6.3","2":"1.6.3","version_comment":"Release notes: \r\n\r\nFeature: Autosave invokes BufWritePost and the frequency can be modulated. This is great for allowing autocommands to trigger on a workspace autosave (i.e. triggering Neomake linting plugin). \r\nFeature: Add autosave ignore list, with gitcommit and gitrebase as default. \r\n\r\nMerged feature: Autosave ignore list is also used to disable loading of workspaces for a loaded filetype in the set (i.e. git commit files won\\'t be merged with workspaces). \r\nMerged feature: Add the ability to autocreate workspaces. This is disabled by default, but can be enabled if it\\'s a preferred behaviour. \r\n\r\nBug fix: \\'\\\\s\\' includes tabs and trailing tabs were also being removed, which is unsafe for any tab-separated files.","3":"Release notes: \r\n\r\nFeature: Autosave invokes BufWritePost and the frequency can be modulated. This is great for allowing autocommands to trigger on a workspace autosave (i.e. triggering Neomake linting plugin). \r\nFeature: Add autosave ignore list, with gitcommit and gitrebase as default. \r\n\r\nMerged feature: Autosave ignore list is also used to disable loading of workspaces for a loaded filetype in the set (i.e. git commit files won\\'t be merged with workspaces). \r\nMerged feature: Add the ability to autocreate workspaces. This is disabled by default, but can be enabled if it\\'s a preferred behaviour. \r\n\r\nBug fix: \\'\\\\s\\' includes tabs and trailing tabs were also being removed, which is unsafe for any tab-separated files.","package":"vim-workspace-1.6.3.tar.gz","4":"vim-workspace-1.6.3.tar.gz","src_id":"24934","5":"24934","creation_date":"1485683151","6":"1485683151"},{"0":"5502","vim_version":"8.0","1":"8.0","script_version":"1.6.2","2":"1.6.2","version_comment":"- Last writer wins in workspaces: if multiple Vim sessions have the same files open at the same time, this ensures that there's no clobbering of data and files update seamlessly between the two instances. \r\n- FocusGained and FocusLost will now trigger file autosave (and\/or sync) when in\/out of editor focus. \r\n- Bug fix: fixed sporadic redraw issue coming from toggling a workspace off.\r\n- Bug fix: typo in a variable that meant autosave could persist outside the confines of a workspace session.","3":"- Last writer wins in workspaces: if multiple Vim sessions have the same files open at the same time, this ensures that there's no clobbering of data and files update seamlessly between the two instances. \r\n- FocusGained and FocusLost will now trigger file autosave (and\/or sync) when in\/out of editor focus. \r\n- Bug fix: fixed sporadic redraw issue coming from toggling a workspace off.\r\n- Bug fix: typo in a variable that meant autosave could persist outside the confines of a workspace session.","package":"vim-workspace-1.6.2.tar.gz","4":"vim-workspace-1.6.2.tar.gz","src_id":"24913","5":"24913","creation_date":"1485004597","6":"1485004597"},{"0":"5502","vim_version":"8.0","1":"8.0","script_version":"1.6.1","2":"1.6.1","version_comment":"Minor updates to omni completion: \r\n- Have a better popup menu with completeopt settings (menuone,longest,preview) \r\n- Should only close preview windows on InsertLeave and not immediately after a selection is made as the documentation can be a useful reference while completing a function.","3":"Minor updates to omni completion: \r\n- Have a better popup menu with completeopt settings (menuone,longest,preview) \r\n- Should only close preview windows on InsertLeave and not immediately after a selection is made as the documentation can be a useful reference while completing a function.","package":"vim-workspace-1.6.1.tar.gz","4":"vim-workspace-1.6.1.tar.gz","src_id":"24900","5":"24900","creation_date":"1484544405","6":"1484544405"},{"0":"5502","vim_version":"8.0","1":"8.0","script_version":"1.6.0","2":"1.6.0","version_comment":"** New feature: Omni completion.\r\n- Vim comes bundled with the SyntaxComplete plugin since 7.2. This functionality is now enabled by default (default shortcut remains as ).\r\n- Plugin feature added that will automatically remove the function preview window once an omni completion selection has been made.\r\n\r\n- Workspace plugin now does a nested autocommand session load, and depends on the vimrc options to re-populate session settings. This statelessness enables any vimrc changes to be reflected when an old session is reloaded, and it also plays nicely with plugins such as Airline that depend on internal state to redraw properly.","3":"** New feature: Omni completion.\r\n- Vim comes bundled with the SyntaxComplete plugin since 7.2. This functionality is now enabled by default (default shortcut remains as ).\r\n- Plugin feature added that will automatically remove the function preview window once an omni completion selection has been made.\r\n\r\n- Workspace plugin now does a nested autocommand session load, and depends on the vimrc options to re-populate session settings. This statelessness enables any vimrc changes to be reflected when an old session is reloaded, and it also plays nicely with plugins such as Airline that depend on internal state to redraw properly.","package":"vim-workspace-1.6.0.tar.gz","4":"vim-workspace-1.6.0.tar.gz","src_id":"24895","5":"24895","creation_date":"1484419569","6":"1484419569"},{"0":"5502","vim_version":"8.0","1":"8.0","script_version":"1.5.0","2":"1.5.0","version_comment":"- Updates to sensible settings: swapsync=\"\" and up the updatetime frequency by default.\r\n- Cleaner way of deleting session files.","3":"- Updates to sensible settings: swapsync=\"\" and up the updatetime frequency by default.\r\n- Cleaner way of deleting session files.","package":"vim-workspace-1.5.0.tar.gz","4":"vim-workspace-1.5.0.tar.gz","src_id":"24891","5":"24891","creation_date":"1484176093","6":"1484176093"},{"0":"5502","vim_version":"8.0","1":"8.0","script_version":"1.4.9","2":"1.4.9","version_comment":"Several updates to sensible settings, and cleaned up unnecessary autosave triggers.\r\n- Disable Ex mode, remove hidden, and remove included files from complete (sensible\/faster with path+=** and included tags).\r\n- BufLeave is sufficient for autosave with respect to TabLeave and WinLeave triggers, hence both can be safely removed.","3":"Several updates to sensible settings, and cleaned up unnecessary autosave triggers.\r\n- Disable Ex mode, remove hidden, and remove included files from complete (sensible\/faster with path+=** and included tags).\r\n- BufLeave is sufficient for autosave with respect to TabLeave and WinLeave triggers, hence both can be safely removed.","package":"vim-workspace-1.4.9.tar.gz","4":"vim-workspace-1.4.9.tar.gz","src_id":"24884","5":"24884","creation_date":"1483912620","6":"1483912620"},{"0":"5502","vim_version":"8.0","1":"8.0","script_version":"1.4.8","2":"1.4.8","version_comment":"Add in more intelligent file argument loading - no more prompts!\r\nHighlights:\r\n- If Vim is run with a file argument and it's already in the directory workspace, you'll be redirected to the tab window that contains it. Otherwise, the file will be loaded in a new tab. \r\n- Also save sessions on BufEnter triggers just in case Vim exits unexpectedly.\r\n- Fix issue where Vim can run without ever hitting VimEnter trigger. This can occur when Vim's being executed to run a command and immediately exit.\r\n- Guard CursorHold trigger against any updatetime < 1000 that might be set by the user or other plugins.","3":"Add in more intelligent file argument loading - no more prompts!\r\nHighlights:\r\n- If Vim is run with a file argument and it's already in the directory workspace, you'll be redirected to the tab window that contains it. Otherwise, the file will be loaded in a new tab. \r\n- Also save sessions on BufEnter triggers just in case Vim exits unexpectedly.\r\n- Fix issue where Vim can run without ever hitting VimEnter trigger. This can occur when Vim's being executed to run a command and immediately exit.\r\n- Guard CursorHold trigger against any updatetime < 1000 that might be set by the user or other plugins.","package":"vim-workspace-1.4.8.tar.gz","4":"vim-workspace-1.4.8.tar.gz","src_id":"24868","5":"24868","creation_date":"1483170073","6":"1483170073"},{"0":"5502","vim_version":"8.0","1":"8.0","script_version":"1.4.7","2":"1.4.7","version_comment":"Guard CursorHold trigger against any updatetime < 1000. \r\nSimplify prompt string and Simplify prompt string.","3":"Guard CursorHold trigger against any updatetime < 1000. \r\nSimplify prompt string and Simplify prompt string.","package":"vim-workspace-1.4.7.tar.gz","4":"vim-workspace-1.4.7.tar.gz","src_id":"24865","5":"24865","creation_date":"1483045151","6":"1483045151"},{"0":"5502","vim_version":"8.0","1":"8.0","script_version":"1.4.0","2":"1.4.0","version_comment":"Add the option for including common sensible settings.","3":"Add the option for including common sensible settings.","package":"vim-workspace-1.4.0.tar.gz","4":"vim-workspace-1.4.0.tar.gz","src_id":"24849","5":"24849","creation_date":"1482899340","6":"1482899340"},{"0":"5502","vim_version":"8.0","1":"8.0","script_version":"1.3.2","2":"1.3.2","version_comment":"Include feature to trim trailing spaces on autosave.","3":"Include feature to trim trailing spaces on autosave.","package":"vim-workspace-1.3.2.tar.gz","4":"vim-workspace-1.3.2.tar.gz","src_id":"24848","5":"24848","creation_date":"1482885834","6":"1482885834"},{"0":"5502","vim_version":"8.0","1":"8.0","script_version":"1.3.0","2":"1.3.0","version_comment":"Add workspace file autosave feature.","3":"Add workspace file autosave feature.","package":"vim-workspace-1.3.0.tar.gz","4":"vim-workspace-1.3.0.tar.gz","src_id":"24846","5":"24846","creation_date":"1482873102","6":"1482873102"}]},"5501":{"script_id":"5501","0":"5501","script_name":"rpgle.vim","1":"rpgle.vim","script_type":"syntax","2":"syntax","summary":"Free (7.1) syntax highlight, folds, indent, etc for RPG\/ILE","3":"Free (7.1) syntax highlight, folds, indent, etc for RPG\/ILE","description":"RPG\/ILE bundle for vim, this bundle provides syntax highlighting, syntax folds, auto indent and more match words.\r\n\r\nSee https:\/\/github.com\/andlrc\/rpgle.vim","4":"RPG\/ILE bundle for vim, this bundle provides syntax highlighting, syntax folds, auto indent and more match words.\r\n\r\nSee https:\/\/github.com\/andlrc\/rpgle.vim","install_details":"","5":"","first_name":"Andreas","6":"Andreas","last_name":"Louv","7":"Louv","releases":[{"0":"5501","vim_version":"7.0","1":"7.0","script_version":"1.1.0","2":"1.1.0","version_comment":"See https:\/\/github.com\/andlrc\/rpgle.vim","3":"See https:\/\/github.com\/andlrc\/rpgle.vim","package":"rpgle.vim.tar.gz","4":"rpgle.vim.tar.gz","src_id":"24864","5":"24864","creation_date":"1483045061","6":"1483045061"},{"0":"5501","vim_version":"7.4","1":"7.4","script_version":"1.0.0","2":"1.0.0","version_comment":"Initial upload","3":"Initial upload","package":"rpgle.vim.tar.gz","4":"rpgle.vim.tar.gz","src_id":"24819","5":"24819","creation_date":"1482631788","6":"1482631788"}]},"5500":{"script_id":"5500","0":"5500","script_name":"vim-paragraph","1":"vim-paragraph","script_type":"utility","2":"utility","summary":"Vim plain text utilities","3":"Vim plain text utilities","description":"vim-paragraph\r\n\r\nA simple paragraph for working with text files, this allows for hard word wrapping ideal for working with Latex and Markdown files\r\n\r\nFunctionality\r\n\r\nVim will automatically hard wrap your lines allowing for easier line navigation on long lines of text such as paragraphs on .tex and .md files\r\n\r\nCtrl-hjkl\r\n\r\nWhile on insert mode vim-paragraph allows you to use the famous hjkl without leaving insert mode while holding Ctrl. Never reach for those arrow keys again.","4":"vim-paragraph\r\n\r\nA simple paragraph for working with text files, this allows for hard word wrapping ideal for working with Latex and Markdown files\r\n\r\nFunctionality\r\n\r\nVim will automatically hard wrap your lines allowing for easier line navigation on long lines of text such as paragraphs on .tex and .md files\r\n\r\nCtrl-hjkl\r\n\r\nWhile on insert mode vim-paragraph allows you to use the famous hjkl without leaving insert mode while holding Ctrl. Never reach for those arrow keys again.","install_details":"Use vundle\r\nPlugin 'pedsm\/vim-paragraph'","5":"Use vundle\r\nPlugin 'pedsm\/vim-paragraph'","first_name":"Pedro","6":"Pedro","last_name":"Mendonca","7":"Mendonca","releases":[{"0":"5500","vim_version":"7.0","1":"7.0","script_version":"v2.0.1","2":"v2.0.1","version_comment":"-Now default is soft wrap (:ToggleWrap will turn hard wrapping back )\r\n-HJKL can visually navigate on a paragraph long line\r\n-C-hjkl on insert mode was slightly modified to work with new softwrap\r\n-:SpellCheck now allows for a spell toggle on en_gb by default\r\n-SpellCheck will be on by default on .tex, .txt, .md and LICENSE files","3":"-Now default is soft wrap (:ToggleWrap will turn hard wrapping back )\r\n-HJKL can visually navigate on a paragraph long line\r\n-C-hjkl on insert mode was slightly modified to work with new softwrap\r\n-:SpellCheck now allows for a spell toggle on en_gb by default\r\n-SpellCheck will be on by default on .tex, .txt, .md and LICENSE files","package":"vim-paragraph-2.0.1.zip","4":"vim-paragraph-2.0.1.zip","src_id":"24836","5":"24836","creation_date":"1482812308","6":"1482812308"},{"0":"5500","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"vim-paragraph.zip","4":"vim-paragraph.zip","src_id":"24818","5":"24818","creation_date":"1482607831","6":"1482607831"}]},"5499":{"script_id":"5499","0":"5499","script_name":"gen_tags.vim","1":"gen_tags.vim","script_type":"utility","2":"utility","summary":"Async plugin for vim and neovim to ease the use of ctags\/gtags","3":"Async plugin for vim and neovim to ease the use of ctags\/gtags","description":"This plugin aim to simple the usage of ctags and gtags for Vim and NeoVim.\r\nIt is used for generate and maintain tags for you.\r\n\r\nThis plugin support both ctags and gtags(aka GNU global).\r\n\r\ngen_tags.vim will detect git root and use it as the project root path.\r\n\r\nGenerate\/Update ctags and gtags will run in background.\r\nYou can always get the latest version from https:\/\/github.com\/jsfaint\/gen_tags.vim\r\nFor more detail please read the README.md\r\n\r\nThanks for reading","4":"This plugin aim to simple the usage of ctags and gtags for Vim and NeoVim.\r\nIt is used for generate and maintain tags for you.\r\n\r\nThis plugin support both ctags and gtags(aka GNU global).\r\n\r\ngen_tags.vim will detect git root and use it as the project root path.\r\n\r\nGenerate\/Update ctags and gtags will run in background.\r\nYou can always get the latest version from https:\/\/github.com\/jsfaint\/gen_tags.vim\r\nFor more detail please read the README.md\r\n\r\nThanks for reading","install_details":"# Neobundle\r\n\r\nAdd NeoBundle 'jsfaint\/gen_tags.vim' to your vimrc\r\nThen launch vim and run :NeobundleCheck\r\n\r\n# Vundle\r\n\r\nAdd Plugin 'jsfaint\/gen_tags.vim' to your vimrc\r\nThen launch vim and run :PluginInstall\r\n\r\n# Traditional method\r\n\r\nUnzip the zip file under your .vim (*nux) or vimfiles(windows) directory.","5":"# Neobundle\r\n\r\nAdd NeoBundle 'jsfaint\/gen_tags.vim' to your vimrc\r\nThen launch vim and run :NeobundleCheck\r\n\r\n# Vundle\r\n\r\nAdd Plugin 'jsfaint\/gen_tags.vim' to your vimrc\r\nThen launch vim and run :PluginInstall\r\n\r\n# Traditional method\r\n\r\nUnzip the zip file under your .vim (*nux) or vimfiles(windows) directory.","first_name":"Jia","6":"Jia","last_name":"Sui","7":"Sui","releases":[{"0":"5499","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"1. Add help file\r\n2. Add gtags source for ncm (optional)\r\n3. Add option to specific ctags location\r\n4. Add LICENSE file\r\n5. Optimize source code\r\n6. Restructure plugin\r\n7. Fix known issues","3":"1. Add help file\r\n2. Add gtags source for ncm (optional)\r\n3. Add option to specific ctags location\r\n4. Add LICENSE file\r\n5. Optimize source code\r\n6. Restructure plugin\r\n7. Fix known issues","package":"gen_tags.vim-1.0.zip","4":"gen_tags.vim-1.0.zip","src_id":"25424","5":"25424","creation_date":"1500276100","6":"1500276100"},{"0":"5499","vim_version":"7.0","1":"7.0","script_version":"0.9","2":"0.9","version_comment":"1. Cache the project root variable for further use.\r\n2. Fix some warning reported by vint\r\n3. Refactor code\r\n4. Add auto generate feature when project is in a git repository.\r\n5. Extend ctags database will be generate automatically after modify ext.conf\r\n6. Remove some commands (GenAll, GenExt) and refactor gen_ctags.vim\r\n7. Add verbose mode\r\n8. Add two options to disable ctags\/gtags support","3":"1. Cache the project root variable for further use.\r\n2. Fix some warning reported by vint\r\n3. Refactor code\r\n4. Add auto generate feature when project is in a git repository.\r\n5. Extend ctags database will be generate automatically after modify ext.conf\r\n6. Remove some commands (GenAll, GenExt) and refactor gen_ctags.vim\r\n7. Add verbose mode\r\n8. Add two options to disable ctags\/gtags support","package":"gen_tags.vim-0.9.tar.gz","4":"gen_tags.vim-0.9.tar.gz","src_id":"25061","5":"25061","creation_date":"1490948198","6":"1490948198"},{"0":"5499","vim_version":"7.0","1":"7.0","script_version":"0.8.1","2":"0.8.1","version_comment":"Fix neovim support, fix callback issue on vim8 when generate gtags","3":"Fix neovim support, fix callback issue on vim8 when generate gtags","package":"gen_tags.vim-0.8.1.zip","4":"gen_tags.vim-0.8.1.zip","src_id":"24850","5":"24850","creation_date":"1482903395","6":"1482903395"},{"0":"5499","vim_version":"7.0","1":"7.0","script_version":"0.8","2":"0.8","version_comment":"Initial upload","3":"Initial upload","package":"gen_tags.vim-0.8.zip","4":"gen_tags.vim-0.8.zip","src_id":"24809","5":"24809","creation_date":"1482276250","6":"1482276250"}]},"5498":{"script_id":"5498","0":"5498","script_name":"Broduo Color Scheme","1":"Broduo Color Scheme","script_type":"color scheme","2":"color scheme","summary":"A dark color scheme for Vim.","3":"A dark color scheme for Vim.","description":"A dark color scheme for Vim.\r\n\r\nScreenshot : https:\/\/i.sli.mg\/t5NcEY.png\r\n","4":"A dark color scheme for Vim.\r\n\r\nScreenshot : https:\/\/i.sli.mg\/t5NcEY.png\r\n","install_details":"Copy broduo.vim to your `~\/.vim\/colors` directory.\r\n\r\nTo set broduo as your default color scheme, add `colorscheme broduo` to\r\nyour .vimrc file.\r\n\r\nIf you want to test the color scheme first, type `:colorscheme broduo` inside\r\nVim.\r\n","5":"Copy broduo.vim to your `~\/.vim\/colors` directory.\r\n\r\nTo set broduo as your default color scheme, add `colorscheme broduo` to\r\nyour .vimrc file.\r\n\r\nIf you want to test the color scheme first, type `:colorscheme broduo` inside\r\nVim.\r\n","first_name":"Jeremy","6":"Jeremy","last_name":"Blain","7":"Blain","releases":[{"0":"5498","vim_version":"7.0","1":"7.0","script_version":"1.0.0","2":"1.0.0","version_comment":"Initial upload","3":"Initial upload","package":"broduo-color-scheme.zip","4":"broduo-color-scheme.zip","src_id":"24807","5":"24807","creation_date":"1482023293","6":"1482023293"}]},"5497":{"script_id":"5497","0":"5497","script_name":"Grammalecte","1":"Grammalecte","script_type":"utility","2":"utility","summary":"Vim plugin for the Grammalecte French grammar checker","3":"Vim plugin for the Grammalecte French grammar checker","description":"This plugin integrates Grammalecte into Vim. Grammalecte is an Open Source\r\nstyle and grammar checker for French.\r\n\r\nSee http:\/\/www.dicollecte.org\/grammalecte for more details about Grammalecte.\r\n\r\nIf you don't have time to read help files, this screenshot will give you\r\nan idea of what the Grammalecte plugin does:\r\n\r\n  http:\/\/dominique.pelle.free.fr\/pic\/GrammalecteVimPlugin.png\r\n\r\nThe Grammalecte plugin defines 2 commands :GrammalecteCheck and\r\n:GrammalecteClean.\r\n\r\n:GrammalecteCheck      \r\n\r\nUse the :GrammalecteCheck command to check the grammar in the current\r\nbuffer. This will highlight errors in the buffer. It will also open a new\r\nscratch window with the list of grammar mistakes with further explanations\r\nfor each error. It also populates the location-list for the window.\r\n\r\nThe :GrammalecteCheck command accepts a range. You can for example check\r\ngrammar between lines 100 and 200 in buffer with :100,200GrammalecteCheck,\r\ncheck grammar in the visual selection with :<',>'GrammalecteCheck, etc.\r\nThe default range is 1,$ (whole buffer).\r\n\r\n:GrammalecteClear\r\n\r\nUse the :GrammalecteClear command to clear highlighting of grammar\r\nmistakes, close the scratch window containing the list of errors, clear\r\nand close the location-list.","4":"This plugin integrates Grammalecte into Vim. Grammalecte is an Open Source\r\nstyle and grammar checker for French.\r\n\r\nSee http:\/\/www.dicollecte.org\/grammalecte for more details about Grammalecte.\r\n\r\nIf you don't have time to read help files, this screenshot will give you\r\nan idea of what the Grammalecte plugin does:\r\n\r\n  http:\/\/dominique.pelle.free.fr\/pic\/GrammalecteVimPlugin.png\r\n\r\nThe Grammalecte plugin defines 2 commands :GrammalecteCheck and\r\n:GrammalecteClean.\r\n\r\n:GrammalecteCheck      \r\n\r\nUse the :GrammalecteCheck command to check the grammar in the current\r\nbuffer. This will highlight errors in the buffer. It will also open a new\r\nscratch window with the list of grammar mistakes with further explanations\r\nfor each error. It also populates the location-list for the window.\r\n\r\nThe :GrammalecteCheck command accepts a range. You can for example check\r\ngrammar between lines 100 and 200 in buffer with :100,200GrammalecteCheck,\r\ncheck grammar in the visual selection with :<',>'GrammalecteCheck, etc.\r\nThe default range is 1,$ (whole buffer).\r\n\r\n:GrammalecteClear\r\n\r\nUse the :GrammalecteClear command to clear highlighting of grammar\r\nmistakes, close the scratch window containing the list of errors, clear\r\nand close the location-list.","install_details":"Unzip file Grammalecte.zip plugin from in your personal |vimfiles| directory\r\n(~\/.vim under Unix or %HOMEPATH%\\vimfiles under Windows): \r\n\r\n  $ mkdir ~\/.vim\r\n  $ cd ~\/.vim\r\n  $ unzip \/path-to\/Grammalecte.zip\r\n  $ vim -c 'helptags ~\/.vim\/doc'\r\n\r\nThe zip file contains the following files: >\r\n\r\n  plugin\/Grammalecte.vim\r\n  doc\/Grammalecte.vim\r\n\r\nYou have to enable plugins by adding these two lines in your |.vimrc| file: >\r\n\r\n  set nocompatible\r\n  filetype plugin on\r\n\r\nAlternatively, if you prefer to use Vundle or Pathogen plugin managers,\r\nthe plugin is available on github at:\r\n\r\n  https:\/\/github.com\/dpelle\/vim-Grammalecte\r\n\r\nFor example, using Vundle, you can install the plugin by adding\r\nthis line in you ~\/.vimrc:\r\n\r\n  Plugin 'dpelle\/vim-Grammalecte'\r\n\r\nTo use this plugin, you also need to install the Python Grammalecte grammar checker.  Download and unzip the file Grammalecte-fr-v0.5.*.oxt available at  http:\/\/www.dicollecte.org\/grammalecte\/telecharger.php\r\n\r\nYou then need to specify in your ~\/.vimrc the location of Grammalecte using something like:\r\n\r\nlet g:grammalecte_cli_py='~\/Downloads\/Grammalecte-fr-v0.5.14\/pythonpath\/cli.py'\r\n","5":"Unzip file Grammalecte.zip plugin from in your personal |vimfiles| directory\r\n(~\/.vim under Unix or %HOMEPATH%\\vimfiles under Windows): \r\n\r\n  $ mkdir ~\/.vim\r\n  $ cd ~\/.vim\r\n  $ unzip \/path-to\/Grammalecte.zip\r\n  $ vim -c 'helptags ~\/.vim\/doc'\r\n\r\nThe zip file contains the following files: >\r\n\r\n  plugin\/Grammalecte.vim\r\n  doc\/Grammalecte.vim\r\n\r\nYou have to enable plugins by adding these two lines in your |.vimrc| file: >\r\n\r\n  set nocompatible\r\n  filetype plugin on\r\n\r\nAlternatively, if you prefer to use Vundle or Pathogen plugin managers,\r\nthe plugin is available on github at:\r\n\r\n  https:\/\/github.com\/dpelle\/vim-Grammalecte\r\n\r\nFor example, using Vundle, you can install the plugin by adding\r\nthis line in you ~\/.vimrc:\r\n\r\n  Plugin 'dpelle\/vim-Grammalecte'\r\n\r\nTo use this plugin, you also need to install the Python Grammalecte grammar checker.  Download and unzip the file Grammalecte-fr-v0.5.*.oxt available at  http:\/\/www.dicollecte.org\/grammalecte\/telecharger.php\r\n\r\nYou then need to specify in your ~\/.vimrc the location of Grammalecte using something like:\r\n\r\nlet g:grammalecte_cli_py='~\/Downloads\/Grammalecte-fr-v0.5.14\/pythonpath\/cli.py'\r\n","first_name":"Dominique","6":"Dominique","last_name":"Pell\u00c3\u00a9","7":"Pell\u00c3\u00a9","releases":[{"0":"5497","vim_version":"8.0","1":"8.0","script_version":"0.2","2":"0.2","version_comment":"- Avoid using lambda, so that plugin works on older Vim versions.\r\n- Updated documentation, to explain how to customize colors","3":"- Avoid using lambda, so that plugin works on older Vim versions.\r\n- Updated documentation, to explain how to customize colors","package":"Grammalecte.zip","4":"Grammalecte.zip","src_id":"24890","5":"24890","creation_date":"1484167601","6":"1484167601"},{"0":"5497","vim_version":"8.0","1":"8.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"Grammalecte.zip","4":"Grammalecte.zip","src_id":"24800","5":"24800","creation_date":"1481609885","6":"1481609885"}]},"5496":{"script_id":"5496","0":"5496","script_name":"coverage.vim","1":"coverage.vim","script_type":"utility","2":"utility","summary":"Show code coverage as signs","3":"Show code coverage as signs","description":"Coverage.vim\r\n\r\nGreatly inspired by vim-gitgutter\r\n\r\nA vim plugin which shows code coverage like wallabyjs\r\n\r\nrequires vim8\r\n\r\nSee: https:\/\/github.com\/ruanyl\/coverage.vim\r\n\r\nInstall\r\n\r\nPlug 'ruanyl\/coverage.vim'\r\nHow it works\r\n\r\nThis plugin uses vim8 new feature timer_start() to read the .json in an interval. Whenver the file changed, it will update the signs of current buffer.\r\n\r\nThe plugin awares of signs from other plugins, for example: syntastic, ale ... But it will overwrite the signs of gitgutter.\r\n\r\nConfig\r\n\r\nSpecify the path to coverage.json file relative to your current working directory.\r\n\r\nCurrently it supports istanbul json reporter nicely, and should also support istanbul based tools like nyc and karma-coverage:\r\nlet g:coverage_json_report_path = 'coverage\/coverage.json'\r\n\r\nDefine the symbol display for covered lines:\r\nlet g:coverage_sign_covered = '⦿'\r\n\r\nDefine the interval time of updating the coverage lines:\r\nlet g:coverage_interval = 5000\r\n\r\nMIT License","4":"Coverage.vim\r\n\r\nGreatly inspired by vim-gitgutter\r\n\r\nA vim plugin which shows code coverage like wallabyjs\r\n\r\nrequires vim8\r\n\r\nSee: https:\/\/github.com\/ruanyl\/coverage.vim\r\n\r\nInstall\r\n\r\nPlug 'ruanyl\/coverage.vim'\r\nHow it works\r\n\r\nThis plugin uses vim8 new feature timer_start() to read the .json in an interval. Whenver the file changed, it will update the signs of current buffer.\r\n\r\nThe plugin awares of signs from other plugins, for example: syntastic, ale ... But it will overwrite the signs of gitgutter.\r\n\r\nConfig\r\n\r\nSpecify the path to coverage.json file relative to your current working directory.\r\n\r\nCurrently it supports istanbul json reporter nicely, and should also support istanbul based tools like nyc and karma-coverage:\r\nlet g:coverage_json_report_path = 'coverage\/coverage.json'\r\n\r\nDefine the symbol display for covered lines:\r\nlet g:coverage_sign_covered = '⦿'\r\n\r\nDefine the interval time of updating the coverage lines:\r\nlet g:coverage_interval = 5000\r\n\r\nMIT License","install_details":"","5":"","first_name":"Yulong","6":"Yulong","last_name":"Ruan","7":"Ruan","releases":[{"0":"5496","vim_version":"8.0","1":"8.0","script_version":"0.1.0","2":"0.1.0","version_comment":"Initial upload","3":"Initial upload","package":"coverage.zip","4":"coverage.zip","src_id":"24796","5":"24796","creation_date":"1481452596","6":"1481452596"}]},"5495":{"script_id":"5495","0":"5495","script_name":"ExpandBackspace","1":"ExpandBackspace","script_type":"utility","2":"utility","summary":"Make backspace eat white space to the last tabstop","3":"Make backspace eat white space to the last tabstop","description":"This plugin is based on GreedyBackspace #1390 plugin.\r\n\r\nThis plugin will cause your backspace key to delete all the white spaces to the previous tabstop. For example, if you typed \"printf(\"Hello World!\");      \" and then hit backspace, you'd only have \"printf(\"Hello World!\");  \". Its behavior is similar to softtabstop, but it doesn't care of how do you put white spaces - with tab key or spacebar.\r\n\r\nThis plugin will cause your delete key to delete &tabstop or less white spaces after character. For example, if you typed \"printf(\"Hello World!\");      \" and then twice hit hit left and then delete, you'd only have \"printf(\"Hello World!\");    \".\r\n\r\nThis plugin works only when expandtab is enabled. You are free to set or unset this option. Plugin will switch on or off accordingly.\r\n","4":"This plugin is based on GreedyBackspace #1390 plugin.\r\n\r\nThis plugin will cause your backspace key to delete all the white spaces to the previous tabstop. For example, if you typed \"printf(\"Hello World!\");      \" and then hit backspace, you'd only have \"printf(\"Hello World!\");  \". Its behavior is similar to softtabstop, but it doesn't care of how do you put white spaces - with tab key or spacebar.\r\n\r\nThis plugin will cause your delete key to delete &tabstop or less white spaces after character. For example, if you typed \"printf(\"Hello World!\");      \" and then twice hit hit left and then delete, you'd only have \"printf(\"Hello World!\");    \".\r\n\r\nThis plugin works only when expandtab is enabled. You are free to set or unset this option. Plugin will switch on or off accordingly.\r\n","install_details":"Source the script from your vimrc or just place it in your plugin directory.","5":"Source the script from your vimrc or just place it in your plugin directory.","first_name":"Yury","6":"Yury","last_name":"Shvedov","7":"Shvedov","releases":[{"0":"5495","vim_version":"7.0","1":"7.0","script_version":"0.6-1","2":"0.6-1","version_comment":"Fix buffer reseting","3":"Fix buffer reseting","package":"ExpandBackspace.vim","4":"ExpandBackspace.vim","src_id":"24786","5":"24786","creation_date":"1481104050","6":"1481104050"},{"0":"5495","vim_version":"7.0","1":"7.0","script_version":"0.6","2":"0.6","version_comment":"Initial upload","3":"Initial upload","package":"ExpandBackspace.vim","4":"ExpandBackspace.vim","src_id":"24783","5":"24783","creation_date":"1481020763","6":"1481020763"}]},"5494":{"script_id":"5494","0":"5494","script_name":"vtags","1":"vtags","script_type":"utility","2":"utility","summary":"verdi like, verilog code signal trace and show topo script  ","3":"verdi like, verilog code signal trace and show topo script  ","description":"---------------------------------------------------------------------------------\r\n Key                                    function                                         \r\n---------------------------------------------------------------------------------\r\n                             Build vtags.db                                      \r\n---------------------------------------------------------------------------------\r\n vtags                                   Build vtags data base at current dir and include  design at current dir and it\u00e2\u0080\u0099s sub dir           \r\n---------------------------------------------------------------------------------\r\n -v                   Specify signal design file                       \r\n---------------------------------------------------------------------------------\r\n -f             Specify design file list and direct use vcs and  verdi file list                                  \r\n---------------------------------------------------------------------------------\r\n +vtags_incdir+   Add dir and it\u00e2\u0080\u0099s sub dir\u00e2\u0080\u0099s design files into vtags data base                                  \r\n---------------------------------------------------------------------------------\r\n +incdir+             Same like vcs\/verdi , and include file search  path                                             \r\n---------------------------------------------------------------------------------\r\n                          Function in Gvim\/VIM window                             \r\n---------------------------------------------------------------------------------\r\n gi                                        go into submodule                                \r\n---------------------------------------------------------------------------------\r\n gu                                       go upper module                                  \r\n---------------------------------------------------------------------------------\r\n mt                                       Print the module call trace from top to current module [3.00 +]                                  \r\n---------------------------------------------------------------------------------\r\n ct                                        Clear vtags module call trace (used when gi\/gu ...) [3.00 +]                   \r\n---------------------------------------------------------------------------------\r\n                   trace source                                     \r\n---------------------------------------------------------------------------------\r\n                 trace destination                                \r\n---------------------------------------------------------------------------------\r\n                roll back                                        \r\n---------------------------------------------------------------------------------\r\n                    go forward                                       \r\n---------------------------------------------------------------------------------\r\n  + v                      Show the sidebar, fold or unfold module\u00e2\u0080\u0099s topt Dynamic build vtags data base for current file  and file dir [3.00+]                             \r\n---------------------------------------------------------------------------------\r\n  + c                     Add check point                                           \r\n---------------------------------------------------------------------------------\r\n  + b                     Add base module                                           \r\n---------------------------------------------------------------------------------\r\n  + d                     Delete check point or base module                         \r\n---------------------------------------------------------------------------------\r\n  +h                      Hold current window                                       \r\n---------------------------------------------------------------------------------\r\n                             Fast access：                                    \r\n                                           1.Sidebar module                                 \r\n                                           2.Trace Report                                   \r\n                                           3.mt command report [3.00+]                               \r\n---------------------------------------------------------------------------------\r\n  + s                      Save snap short                                           \r\n---------------------------------------------------------------------------------\r\n  +r                        Reload snap short at current window [3.00+]          \r\n---------------------------------------------------------------------------------\r\n  + q                      Close all open gvim windows [3.00+]                       \r\n---------------------------------------------------------------------------------\r\n                          Function when Gvim\/VIM opening                                   \r\n---------------------------------------------------------------------------------\r\n gvim\/vim    Reload snap short saved at [3.00+]   \r\n                                             Open top most 10 module [3.10+]\r\n---------------------------------------------------------------------------------\r\n                          Offline function base on vtags.db                                \r\n---------------------------------------------------------------------------------\r\n vtags -db  \"mtrace(  )\"                              \r\n At  corresponding design, list  all the call trace   \r\n from most top module to                                                      \r\n---------------------------------------------------------------------------------\r\n vtags -db  \"mfilelist(  )\"                           \r\n At  corresponding design, list \u00e2\u0080\u0099s used file list              \r\n---------------------------------------------------------------------------------\r\n vtags -db  \"mtopo( , depth, mask )\"                  \r\n At  corresponding design, list module call instance topo          \r\n depth : optional parm, topo depth                                                \r\n mask  : optional parm,  when sub module call more than mask times not list it \r\n             one by one                                                                            \r\n---------------------------------------------------------------------------------\r\n vtags -db  \u00e2\u0080\u009cmopen( )\u00e2\u0080\u009d                                \r\n At  corresponding design, open  file                          \r\n---------------------------------------------------------------------------------\r\n\r\nattention:\r\n(1)  when you update your vtags from 2.xx to 3.x please delate old vtags.db in your folder， and use command  \"vtags\"  generate new vtags.db  again !\r\n(2)  if your design file not all use  \"v\"  as the postfix, you need add you own postfix at  vtags-3.xx\/vim_glb_config.py line:46 support_verilog_postfix , If not, vtags will not treat other postfix other than 'v' as your design files. \r\n        exp:   I use  xxx.v,  xxx.sv,   xxx.V,   xxx.d in my design i need set as :  support_verilog_postfix     = ['v', 'sv', 'V', 'd' ] ","4":"---------------------------------------------------------------------------------\r\n Key                                    function                                         \r\n---------------------------------------------------------------------------------\r\n                             Build vtags.db                                      \r\n---------------------------------------------------------------------------------\r\n vtags                                   Build vtags data base at current dir and include  design at current dir and it\u00e2\u0080\u0099s sub dir           \r\n---------------------------------------------------------------------------------\r\n -v                   Specify signal design file                       \r\n---------------------------------------------------------------------------------\r\n -f             Specify design file list and direct use vcs and  verdi file list                                  \r\n---------------------------------------------------------------------------------\r\n +vtags_incdir+   Add dir and it\u00e2\u0080\u0099s sub dir\u00e2\u0080\u0099s design files into vtags data base                                  \r\n---------------------------------------------------------------------------------\r\n +incdir+             Same like vcs\/verdi , and include file search  path                                             \r\n---------------------------------------------------------------------------------\r\n                          Function in Gvim\/VIM window                             \r\n---------------------------------------------------------------------------------\r\n gi                                        go into submodule                                \r\n---------------------------------------------------------------------------------\r\n gu                                       go upper module                                  \r\n---------------------------------------------------------------------------------\r\n mt                                       Print the module call trace from top to current module [3.00 +]                                  \r\n---------------------------------------------------------------------------------\r\n ct                                        Clear vtags module call trace (used when gi\/gu ...) [3.00 +]                   \r\n---------------------------------------------------------------------------------\r\n                   trace source                                     \r\n---------------------------------------------------------------------------------\r\n                 trace destination                                \r\n---------------------------------------------------------------------------------\r\n                roll back                                        \r\n---------------------------------------------------------------------------------\r\n                    go forward                                       \r\n---------------------------------------------------------------------------------\r\n  + v                      Show the sidebar, fold or unfold module\u00e2\u0080\u0099s topt Dynamic build vtags data base for current file  and file dir [3.00+]                             \r\n---------------------------------------------------------------------------------\r\n  + c                     Add check point                                           \r\n---------------------------------------------------------------------------------\r\n  + b                     Add base module                                           \r\n---------------------------------------------------------------------------------\r\n  + d                     Delete check point or base module                         \r\n---------------------------------------------------------------------------------\r\n  +h                      Hold current window                                       \r\n---------------------------------------------------------------------------------\r\n                             Fast access：                                    \r\n                                           1.Sidebar module                                 \r\n                                           2.Trace Report                                   \r\n                                           3.mt command report [3.00+]                               \r\n---------------------------------------------------------------------------------\r\n  + s                      Save snap short                                           \r\n---------------------------------------------------------------------------------\r\n  +r                        Reload snap short at current window [3.00+]          \r\n---------------------------------------------------------------------------------\r\n  + q                      Close all open gvim windows [3.00+]                       \r\n---------------------------------------------------------------------------------\r\n                          Function when Gvim\/VIM opening                                   \r\n---------------------------------------------------------------------------------\r\n gvim\/vim    Reload snap short saved at [3.00+]   \r\n                                             Open top most 10 module [3.10+]\r\n---------------------------------------------------------------------------------\r\n                          Offline function base on vtags.db                                \r\n---------------------------------------------------------------------------------\r\n vtags -db  \"mtrace(  )\"                              \r\n At  corresponding design, list  all the call trace   \r\n from most top module to                                                      \r\n---------------------------------------------------------------------------------\r\n vtags -db  \"mfilelist(  )\"                           \r\n At  corresponding design, list \u00e2\u0080\u0099s used file list              \r\n---------------------------------------------------------------------------------\r\n vtags -db  \"mtopo( , depth, mask )\"                  \r\n At  corresponding design, list module call instance topo          \r\n depth : optional parm, topo depth                                                \r\n mask  : optional parm,  when sub module call more than mask times not list it \r\n             one by one                                                                            \r\n---------------------------------------------------------------------------------\r\n vtags -db  \u00e2\u0080\u009cmopen( )\u00e2\u0080\u009d                                \r\n At  corresponding design, open  file                          \r\n---------------------------------------------------------------------------------\r\n\r\nattention:\r\n(1)  when you update your vtags from 2.xx to 3.x please delate old vtags.db in your folder， and use command  \"vtags\"  generate new vtags.db  again !\r\n(2)  if your design file not all use  \"v\"  as the postfix, you need add you own postfix at  vtags-3.xx\/vim_glb_config.py line:46 support_verilog_postfix , If not, vtags will not treat other postfix other than 'v' as your design files. \r\n        exp:   I use  xxx.v,  xxx.sv,   xxx.V,   xxx.d in my design i need set as :  support_verilog_postfix     = ['v', 'sv', 'V', 'd' ] ","install_details":"(1)  tar -zxvf vtags-3.xx.tar.gz    \/\/ unpack the file to the path you want to install. we assuming to \"~\/\"\r\n(2)  in  \"~\/.cshrc\"   add line:  alias vtags 'python  ~\/vtags-3.xx\/vtags.py'\r\n      or  \"~\/.bashrc\"  add line:  alias=vtags 'python  ~\/vtags-3.xx\/vtags.py'\r\n      \"source ~\/.cshrc\"  or  \"source ~\/.bashrc\"\r\n(3)  in \"~\/.vimrc\"  add line： source  ~\/vtags-3.xx\/vtags_vim_api.vim\r\n(4)  config vtags-3.xx\/vim_glb_config.py as it decribe in vim_glb_config.py. (can do it in local_config.py see below)\r\n","5":"(1)  tar -zxvf vtags-3.xx.tar.gz    \/\/ unpack the file to the path you want to install. we assuming to \"~\/\"\r\n(2)  in  \"~\/.cshrc\"   add line:  alias vtags 'python  ~\/vtags-3.xx\/vtags.py'\r\n      or  \"~\/.bashrc\"  add line:  alias=vtags 'python  ~\/vtags-3.xx\/vtags.py'\r\n      \"source ~\/.cshrc\"  or  \"source ~\/.bashrc\"\r\n(3)  in \"~\/.vimrc\"  add line： source  ~\/vtags-3.xx\/vtags_vim_api.vim\r\n(4)  config vtags-3.xx\/vim_glb_config.py as it decribe in vim_glb_config.py. (can do it in local_config.py see below)\r\n","first_name":"Jun","6":"Jun","last_name":"Cao","7":"Cao","releases":[{"0":"5494","vim_version":"8.0","1":"8.0","script_version":"3.11","2":"3.11","version_comment":"fix vtags must need filelist bug.\r\nfix install name not vtags.xx has error bug.\r\nfix other misc bug.\r\n","3":"fix vtags must need filelist bug.\r\nfix install name not vtags.xx has error bug.\r\nfix other misc bug.\r\n","package":"vtags-3.11.tar.gz","4":"vtags-3.11.tar.gz","src_id":"28365","5":"28365","creation_date":"1676396815","6":"1676396815"},{"0":"5494","vim_version":"7.0","1":"7.0","script_version":"3.10","2":"3.10","version_comment":"function improve:\r\n1. support env variable at filelist.\r\n2.add function \"vim\/gvim vtags.db\" to list and choise to open 10(configed) most deeper top modules.\r\n3.extend \"gi\" to open module if cursor on string of module name.\r\n4.extend snapshot function, allow multi-user to read only open snapshort\r\n\r\nbug fix:\r\n1. fix bug at auto add supported postfix from file list.\r\n2. fix bug at install folder name.\r\n3. fix bug at \"trace source\" not  correct problem.  \r\n ","3":"function improve:\r\n1. support env variable at filelist.\r\n2.add function \"vim\/gvim vtags.db\" to list and choise to open 10(configed) most deeper top modules.\r\n3.extend \"gi\" to open module if cursor on string of module name.\r\n4.extend snapshot function, allow multi-user to read only open snapshort\r\n\r\nbug fix:\r\n1. fix bug at auto add supported postfix from file list.\r\n2. fix bug at install folder name.\r\n3. fix bug at \"trace source\" not  correct problem.  \r\n ","package":"vtags-3.10.tar.gz","4":"vtags-3.10.tar.gz","src_id":"27765","5":"27765","creation_date":"1633350965","6":"1633350965"},{"0":"5494","vim_version":"7.3","1":"7.3","script_version":"3.01","2":"3.01","version_comment":"some bug fix and function expansion.","3":"some bug fix and function expansion.","package":"vtags-3.01.tar.gz","4":"vtags-3.01.tar.gz","src_id":"26794","5":"26794","creation_date":"1571914968","6":"1571914968"},{"0":"5494","vim_version":"7.3","1":"7.3","script_version":"3.00","2":"3.00","version_comment":"1. support both gvim with python2 or python3. \r\n2. rebuild the verilog syntax parser with c, which is more fast(x10~100), accurate and powerful than old python parser. \r\n3. all other provide function all changed to relay on new c-parser result, which also more more fast and accurate. \r\n4. provide new function for easy view code and design detail see bellow.","3":"1. support both gvim with python2 or python3. \r\n2. rebuild the verilog syntax parser with c, which is more fast(x10~100), accurate and powerful than old python parser. \r\n3. all other provide function all changed to relay on new c-parser result, which also more more fast and accurate. \r\n4. provide new function for easy view code and design detail see bellow.","package":"vtags-3.00.tar.gz","4":"vtags-3.00.tar.gz","src_id":"26545","5":"26545","creation_date":"1560776175","6":"1560776175"},{"0":"5494","vim_version":"7.3","1":"7.3","script_version":"2.24","2":"2.24","version_comment":"fix the bug caused by 2.23 which not write back report log, so when open a new log it will not found it and repeat open same file, cause new vtags log file can not open.","3":"fix the bug caused by 2.23 which not write back report log, so when open a new log it will not found it and repeat open same file, cause new vtags log file can not open.","package":"vtags-2.24.tar.gz","4":"vtags-2.24.tar.gz","src_id":"26220","5":"26220","creation_date":"1536403420","6":"1536403420"},{"0":"5494","vim_version":"7.3","1":"7.3","script_version":"2.23","2":"2.23","version_comment":"Remove self writeback Report file and  Frame file(no related with rtl, just vtags's report file), user need save yourself if needed when close those file, to bypass vim's unsolved E323 bugs.","3":"Remove self writeback Report file and  Frame file(no related with rtl, just vtags's report file), user need save yourself if needed when close those file, to bypass vim's unsolved E323 bugs.","package":"vtags-2.23.tar.gz","4":"vtags-2.23.tar.gz","src_id":"26204","5":"26204","creation_date":"1536147063","6":"1536147063"},{"0":"5494","vim_version":"7.3","1":"7.3","script_version":"2.22","2":"2.22","version_comment":"Fix database save file name limited problem.\r\nFix some import problem.","3":"Fix database save file name limited problem.\r\nFix some import problem.","package":"vtags-2.22.tar.gz","4":"vtags-2.22.tar.gz","src_id":"26152","5":"26152","creation_date":"1532775713","6":"1532775713"},{"0":"5494","vim_version":"7.3","1":"7.3","script_version":"2.21","2":"2.21","version_comment":"fix bug for vim.buffer cannot pickle when +s","3":"fix bug for vim.buffer cannot pickle when +s","package":"vtags-2.21.tar.gz","4":"vtags-2.21.tar.gz","src_id":"25549","5":"25549","creation_date":"1504512040","6":"1504512040"},{"0":"5494","vim_version":"7.3","1":"7.3","script_version":"2.20","2":"2.20","version_comment":"1. vtags support file(or folder) list now, you can list all the design file or it's folder in the filelist and then use command \"vtags -f filelist\" to generate vtags database. \r\n2. add new   shortcut keys :  \"mt\" , which used to print the current module's instantiation trace from top module. \r\n3. enhanced shortcut keys :  \"gu\",  new version you can go to any upper module in the vtags.db, no need open it before. \r\n4. enhanced shortcut keys :  \" \", \"\"  new version you can trace cross module from any module, no need open from top module as before. \r\n\r\nAttention: for people update to new vtags 2.20 version needs use command \"vtags or vtags -f filelist\" to refresh your old vtags.db, then you can use all the new function in new version listed before.","3":"1. vtags support file(or folder) list now, you can list all the design file or it's folder in the filelist and then use command \"vtags -f filelist\" to generate vtags database. \r\n2. add new   shortcut keys :  \"mt\" , which used to print the current module's instantiation trace from top module. \r\n3. enhanced shortcut keys :  \"gu\",  new version you can go to any upper module in the vtags.db, no need open it before. \r\n4. enhanced shortcut keys :  \" \", \"\"  new version you can trace cross module from any module, no need open from top module as before. \r\n\r\nAttention: for people update to new vtags 2.20 version needs use command \"vtags or vtags -f filelist\" to refresh your old vtags.db, then you can use all the new function in new version listed before.","package":"vtags-2.20.tar.gz","4":"vtags-2.20.tar.gz","src_id":"25436","5":"25436","creation_date":"1500815607","6":"1500815607"},{"0":"5494","vim_version":"7.3","1":"7.3","script_version":"2.12","2":"2.12","version_comment":"fix bug for offerline function \"print_module_list(module_name)\", pre version if multi module in one hdl file maybe can not list second match module list, current fix it.","3":"fix bug for offerline function \"print_module_list(module_name)\", pre version if multi module in one hdl file maybe can not list second match module list, current fix it.","package":"vtags-2.12.tar.gz","4":"vtags-2.12.tar.gz","src_id":"25150","5":"25150","creation_date":"1494134081","6":"1494134081"},{"0":"5494","vim_version":"7.3","1":"7.3","script_version":"2.11","2":"2.11","version_comment":"fix a bug at CodeLib.py line:443-443, which will made can not trace following subcall s_c, s_d signal:\r\nA  #(p_a,p_b,p_c) A_inst (s_a, {s_b, s_c, s_d }, ...  )","3":"fix a bug at CodeLib.py line:443-443, which will made can not trace following subcall s_c, s_d signal:\r\nA  #(p_a,p_b,p_c) A_inst (s_a, {s_b, s_c, s_d }, ...  )","package":"vtags-2.11.tar.gz","4":"vtags-2.11.tar.gz","src_id":"25090","5":"25090","creation_date":"1493042373","6":"1493042373"},{"0":"5494","vim_version":"7.3","1":"7.3","script_version":"2.10","2":"2.10","version_comment":"fix 3 bugs and not active vtags when vim not open a valid  rtl or not find vtags.db.","3":"fix 3 bugs and not active vtags when vim not open a valid  rtl or not find vtags.db.","package":"vtags-2.10.tar.gz","4":"vtags-2.10.tar.gz","src_id":"25040","5":"25040","creation_date":"1489922050","6":"1489922050"},{"0":"5494","vim_version":"7.3","1":"7.3","script_version":"2.0","2":"2.0","version_comment":"vtags 2.x version is my current most satisfied version, hoping to share with you.\r\nvtags-2.x almost completely refactored vtags-1.x all the features and implementation, both in function, speed and user experience have a qualitative leap, the main changes are reflected in:\r\n1. The new version greatly expanded support for verilog multiple syntaxes.\r\n2. The new version of the implementation of a complete and fast database dynamic update mechanism, vtags will change with the design of dynamic with the new.\r\n3. The new version uses a new recognition algorithm, which greatly improves the accuracy and speed of recognition.\r\n4. The new version uses a decentralized and lazy loading technology, which greatly saves the resources that vtags runs.\r\n5. The new version provides a set of functions and APIs to facilitate the use of vtags and the database when the user does not open vim.\r\n6. The new version optimized vtags's import, so that the vim open non-vtags support file is almost no delay.","3":"vtags 2.x version is my current most satisfied version, hoping to share with you.\r\nvtags-2.x almost completely refactored vtags-1.x all the features and implementation, both in function, speed and user experience have a qualitative leap, the main changes are reflected in:\r\n1. The new version greatly expanded support for verilog multiple syntaxes.\r\n2. The new version of the implementation of a complete and fast database dynamic update mechanism, vtags will change with the design of dynamic with the new.\r\n3. The new version uses a new recognition algorithm, which greatly improves the accuracy and speed of recognition.\r\n4. The new version uses a decentralized and lazy loading technology, which greatly saves the resources that vtags runs.\r\n5. The new version provides a set of functions and APIs to facilitate the use of vtags and the database when the user does not open vim.\r\n6. The new version optimized vtags's import, so that the vim open non-vtags support file is almost no delay.","package":"vtags-2.0.tar.gz","4":"vtags-2.0.tar.gz","src_id":"25012","5":"25012","creation_date":"1488871043","6":"1488871043"},{"0":"5494","vim_version":"7.3","1":"7.3","script_version":"1.23","2":"1.23","version_comment":"fix a bug in Code.py line 465, need 'Source' but use source, if you open Debug mode may find this error.\r\nfix a bug in Base.py line 986, add i += 1 in while loop, if your code wrong and has endmodule without module define it will loop forever.","3":"fix a bug in Code.py line 465, need 'Source' but use source, if you open Debug mode may find this error.\r\nfix a bug in Base.py line 986, add i += 1 in while loop, if your code wrong and has endmodule without module define it will loop forever.","package":"vtags-1.23.tar.gz","4":"vtags-1.23.tar.gz","src_id":"24914","5":"24914","creation_date":"1485068006","6":"1485068006"},{"0":"5494","vim_version":"7.3","1":"7.3","script_version":"1.22","2":"1.22","version_comment":"fix the bug when use B add last topo line module to base module, and refresh the topo will not work .","3":"fix the bug when use B add last topo line module to base module, and refresh the topo will not work .","package":"vtags-1.22.tar.gz","4":"vtags-1.22.tar.gz","src_id":"24877","5":"24877","creation_date":"1483766459","6":"1483766459"},{"0":"5494","vim_version":"7.0","1":"7.0","script_version":"1.21","2":"1.21","version_comment":"add some optimize for trace speed and accuracy， some case pre version can not deside if source or dest current can sure is' source or dest. ","3":"add some optimize for trace speed and accuracy， some case pre version can not deside if source or dest current can sure is' source or dest. ","package":"vtags-1.21.tar.gz","4":"vtags-1.21.tar.gz","src_id":"24790","5":"24790","creation_date":"1481185192","6":"1481185192"},{"0":"5494","vim_version":"7.2","1":"7.2","script_version":"1.20","2":"1.20","version_comment":"Initial upload","3":"Initial upload","package":"vtags-1.20.tar.gz","4":"vtags-1.20.tar.gz","src_id":"24782","5":"24782","creation_date":"1481001176","6":"1481001176"}]},"5493":{"script_id":"5493","0":"5493","script_name":"far.vim","1":"far.vim","script_type":"utility","2":"utility","summary":"Find And Replace Vim plugin","3":"Find And Replace Vim plugin","description":"Far.vim makes it easier to find and replace text through multiple files. It's inspired by fancy IDEs, like IntelliJ and Eclipse, that provide cozy tools for such tasks.\r\n\r\nVisit GitHub for demos - https:\/\/github.com\/brooth\/far.vim\r\nVisit :help far.vim for details ;)","4":"Far.vim makes it easier to find and replace text through multiple files. It's inspired by fancy IDEs, like IntelliJ and Eclipse, that provide cozy tools for such tasks.\r\n\r\nVisit GitHub for demos - https:\/\/github.com\/brooth\/far.vim\r\nVisit :help far.vim for details ;)","install_details":"Install via vim-plug (https:\/\/github.com\/junegunn\/vim-plug)\r\nPlug 'brooth\/far.vim' ","5":"Install via vim-plug (https:\/\/github.com\/junegunn\/vim-plug)\r\nPlug 'brooth\/far.vim' ","first_name":"Oleg","6":"Oleg","last_name":"Khalidov","7":"Khalidov","releases":[{"0":"5493","vim_version":"7.4","1":"7.4","script_version":"beta 2","2":"beta 2","version_comment":"Initial upload","3":"Initial upload","package":"far.vim-beta2.zip","4":"far.vim-beta2.zip","src_id":"24781","5":"24781","creation_date":"1480923593","6":"1480923593"}]},"5492":{"script_id":"5492","0":"5492","script_name":"vim-loggly-search","1":"vim-loggly-search","script_type":"utility","2":"utility","summary":"A vim plug-in to easily search in loggly","3":"A vim plug-in to easily search in loggly","description":"Searches for the visually selected text in Loggly.\r\n\r\nSee https:\/\/github.com\/christianrondeau\/vim-loggly-search","4":"Searches for the visually selected text in Loggly.\r\n\r\nSee https:\/\/github.com\/christianrondeau\/vim-loggly-search","install_details":"","5":"","first_name":"Christian","6":"Christian","last_name":"Rondeau","7":"Rondeau","releases":[{"0":"5492","vim_version":"7.4","1":"7.4","script_version":"7.4","2":"7.4","version_comment":"Initial upload","3":"Initial upload","package":"vim-loggly-search-0.1.tar.gz","4":"vim-loggly-search-0.1.tar.gz","src_id":"24779","5":"24779","creation_date":"1480704720","6":"1480704720"}]},"5491":{"script_id":"5491","0":"5491","script_name":"vim-base64","1":"vim-base64","script_type":"utility","2":"utility","summary":"Vim plugin to encode\/decode base64 strings","3":"Vim plugin to encode\/decode base64 strings","description":"Encodes\/decodes base64 strings using base64 on Linux and Python on Windows\r\n\r\nSee https:\/\/github.com\/christianrondeau\/vim-base64","4":"Encodes\/decodes base64 strings using base64 on Linux and Python on Windows\r\n\r\nSee https:\/\/github.com\/christianrondeau\/vim-base64","install_details":"","5":"","first_name":"Christian","6":"Christian","last_name":"Rondeau","7":"Rondeau","releases":[{"0":"5491","vim_version":"7.4","1":"7.4","script_version":"v1.2","2":"v1.2","version_comment":"Reverse btoa and atob! (Oops!)","3":"Reverse btoa and atob! (Oops!)","package":"vim-base64.tar.gz","4":"vim-base64.tar.gz","src_id":"25812","5":"25812","creation_date":"1517682567","6":"1517682567"},{"0":"5491","vim_version":"7.4","1":"7.4","script_version":"v1.1","2":"v1.1","version_comment":"MacOS support","3":"MacOS support","package":"vim-base64-1.1.tar.gz","4":"vim-base64-1.1.tar.gz","src_id":"25014","5":"25014","creation_date":"1488993797","6":"1488993797"},{"0":"5491","vim_version":"7.4","1":"7.4","script_version":"7.4","2":"7.4","version_comment":"Initial upload","3":"Initial upload","package":"vim-base64-1.0.tar.gz","4":"vim-base64-1.0.tar.gz","src_id":"24778","5":"24778","creation_date":"1480704663","6":"1480704663"}]},"5490":{"script_id":"5490","0":"5490","script_name":"minimalist.vim","1":"minimalist.vim","script_type":"color scheme","2":"color scheme","summary":"A Material Color Scheme Darker for Vim","3":"A Material Color Scheme Darker for Vim","description":"Minimalist is a Material Color Scheme Darker for Vim & inspired by https:\/\/github.com\/equinusocio\/material-theme.\r\n\r\nScreenshot & Details: https:\/\/github.com\/dikiaap\/minimalist\r\n\r\nAs you know, color scheme in vim by default supports many programming languages.\r\nAt this time minimalist is looks beautiful & focused on:\r\n\r\n- C++\r\n- CSS\/CSS3\r\n- HTML\/HTML5\r\n- JavaScript\r\n- Markdown\r\n- PHP\r\n- Python\r\n- Ruby\r\n- Sass\r\n- Shell\r\n- XML","4":"Minimalist is a Material Color Scheme Darker for Vim & inspired by https:\/\/github.com\/equinusocio\/material-theme.\r\n\r\nScreenshot & Details: https:\/\/github.com\/dikiaap\/minimalist\r\n\r\nAs you know, color scheme in vim by default supports many programming languages.\r\nAt this time minimalist is looks beautiful & focused on:\r\n\r\n- C++\r\n- CSS\/CSS3\r\n- HTML\/HTML5\r\n- JavaScript\r\n- Markdown\r\n- PHP\r\n- Python\r\n- Ruby\r\n- Sass\r\n- Shell\r\n- XML","install_details":"Copy minimalist.vim file\r\n\r\ncp colors\/minimalist.vim ~\/.vim\/colors\r\n\r\nOR\r\n\r\nUse Vundle by adding to your .vimrc plugin section:\r\n\r\nPlugin 'dikiaap\/minimalist'\r\n\r\nThen run :PluginInstall\r\n\r\nOR\r\n\r\nUse vim-plug by adding to your .vimrc vim-plug section:\r\n\r\nPlug 'dikiaap\/minimalist'\r\n\r\nThen run :PlugInstall\r\n\r\nAfter finishing installation, put this code to your .vimrc:\r\n\r\nset t_Co=256\r\nsyntax on\r\ncolorscheme minimalist\r\n\r\nThis color scheme also built-in with airline theme. If you wanna use:\r\n\r\nlet g:airline_theme='minimalist'\r\nlet g:airline_powerline_fonts = 1\r\nlet g:airline#extensions#tabline#enabled = 1","5":"Copy minimalist.vim file\r\n\r\ncp colors\/minimalist.vim ~\/.vim\/colors\r\n\r\nOR\r\n\r\nUse Vundle by adding to your .vimrc plugin section:\r\n\r\nPlugin 'dikiaap\/minimalist'\r\n\r\nThen run :PluginInstall\r\n\r\nOR\r\n\r\nUse vim-plug by adding to your .vimrc vim-plug section:\r\n\r\nPlug 'dikiaap\/minimalist'\r\n\r\nThen run :PlugInstall\r\n\r\nAfter finishing installation, put this code to your .vimrc:\r\n\r\nset t_Co=256\r\nsyntax on\r\ncolorscheme minimalist\r\n\r\nThis color scheme also built-in with airline theme. If you wanna use:\r\n\r\nlet g:airline_theme='minimalist'\r\nlet g:airline_powerline_fonts = 1\r\nlet g:airline#extensions#tabline#enabled = 1","first_name":"Diki","6":"Diki","last_name":"Ananta","7":"Ananta","releases":[{"0":"5490","vim_version":"7.0","1":"7.0","script_version":"v1.6","2":"v1.6","version_comment":"- Refactoring airline theme.","3":"- Refactoring airline theme.","package":"minimalist-1.6.zip","4":"minimalist-1.6.zip","src_id":"26032","5":"26032","creation_date":"1528378137","6":"1528378137"},{"0":"5490","vim_version":"7.0","1":"7.0","script_version":"v1.5","2":"v1.5","version_comment":"- Add airline theme.\r\n- Fix comments color which is hardly visible.\r\n- Minor improvements.","3":"- Add airline theme.\r\n- Fix comments color which is hardly visible.\r\n- Minor improvements.","package":"minimalist-1.5.zip","4":"minimalist-1.5.zip","src_id":"25773","5":"25773","creation_date":"1516156040","6":"1516156040"},{"0":"5490","vim_version":"7.0","1":"7.0","script_version":"v1.4","2":"v1.4","version_comment":"- Added red accent in airline theme.\r\n- Enhancement in general colorscheme.\r\n- Enhancement in syntax highlighting.\r\n- `MoreMsg`, `Question`, and `WildMenu`.\r\n- `FoldColumn`, `Error`, and `Spell`.\r\n- Minor improvements.","3":"- Added red accent in airline theme.\r\n- Enhancement in general colorscheme.\r\n- Enhancement in syntax highlighting.\r\n- `MoreMsg`, `Question`, and `WildMenu`.\r\n- `FoldColumn`, `Error`, and `Spell`.\r\n- Minor improvements.","package":"minimalist.vim","4":"minimalist.vim","src_id":"25289","5":"25289","creation_date":"1496857725","6":"1496857725"},{"0":"5490","vim_version":"7.0","1":"7.0","script_version":"v1.3","2":"v1.3","version_comment":"- Fixed vendor prefixes in CSS Property.\r\n- Fixed XML end tag.\r\n- Update syntax highlighting.\r\n- Bug fixes and minor improvements.","3":"- Fixed vendor prefixes in CSS Property.\r\n- Fixed XML end tag.\r\n- Update syntax highlighting.\r\n- Bug fixes and minor improvements.","package":"minimalist.vim","4":"minimalist.vim","src_id":"25091","5":"25091","creation_date":"1493069114","6":"1493069114"},{"0":"5490","vim_version":"7.0","1":"7.0","script_version":"v1.2","2":"v1.2","version_comment":"- Fixed colors warning and error in airline theme.\r\n- Change line number fg & bg colors like in material-theme.","3":"- Fixed colors warning and error in airline theme.\r\n- Change line number fg & bg colors like in material-theme.","package":"minimalist.vim","4":"minimalist.vim","src_id":"24872","5":"24872","creation_date":"1483464772","6":"1483464772"},{"0":"5490","vim_version":"7.0","1":"7.0","script_version":"v1.1","2":"v1.1","version_comment":"- Added airline theme.\r\n- Added Sass, XML, and Markdown syntax highlighting.\r\n- Update syntax highlighting.\r\n- Added NERDTree support.\r\n- Improve blue light and white colors.\r\n- Bug fixes and minor improvements.","3":"- Added airline theme.\r\n- Added Sass, XML, and Markdown syntax highlighting.\r\n- Update syntax highlighting.\r\n- Added NERDTree support.\r\n- Improve blue light and white colors.\r\n- Bug fixes and minor improvements.","package":"minimalist.vim","4":"minimalist.vim","src_id":"24793","5":"24793","creation_date":"1481294202","6":"1481294202"},{"0":"5490","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"minimalist.vim","4":"minimalist.vim","src_id":"24777","5":"24777","creation_date":"1480673617","6":"1480673617"}]},"5489":{"script_id":"5489","0":"5489","script_name":"vim-DetectSpellLang","1":"vim-DetectSpellLang","script_type":"utility","2":"utility","summary":"autodetect the spell-check language of the current buffer","3":"autodetect the spell-check language of the current buffer","description":"This Vim plug-in autodetects the tongue (= `&spelllang`) of the text in a\r\nbuffer (if it is spell checked, that is, `&spell` is set, and `&spelllang` has\r\nnot been explicitly set, say by a modeline :help modeline).\r\n\r\nIt uses either the spell checker aspell or hunspell (which are installed\r\nin many Linux distributions, in Mac OS, and both available for Microsoft\r\nWindows.\r\n\r\nIn Microsoft Windows the path to the executable must\r\n\r\n- be either added to the `%PATH%` environment variable (say by Rapidee from \r\n  http:\/\/www.rapidee.com), or\r\n- set by g:detectspelllang_program, say\r\n\r\n    let g:detectspelllang_program = 'C:\\Program Files (x86)\\Aspell\\bin\\aspell.exe'\r\n\r\n===========================================================================\r\nINITIAL SET-UP\r\n===========================================================================\r\n\r\nThis plug-in only operates in buffers that are spell checked, that is,\r\n&l:spell is set. To ensure that certain file types, for example 'text',\r\n'markdown' and 'mail', are spell checked, add either the line\r\n\r\n  autocmd FileType text,markdown,mail setlocal spell\r\n\r\nor the line\r\n\r\n  setlocal spell\r\n\r\nto ~\/.vim\/ftplugin\/text.vim (respectively markdown.vim and mail.vim).\r\n\r\nThe language is detected, depending on whether aspell respectively hunspell \r\nis used, among those listed in g:detectspelllang_langs.aspell respectively\r\ng:detectspelllang_langs.hunspell. It is *empty* by default and has to be\r\nset by the user to a list of languages included in that of the output of the \r\ncommand aspell dicts respectively hunspell -D! \r\n\r\nFor example, in case you use aspell,\r\n\r\n  let g:detectspelllang_langs = {}\r\n  let g:detectspelllang_langs.aspell = [ 'en_US', 'de_DE', 'es', 'it' ]\r\n\r\nrespectively, in case you use hunspell,\r\n\r\n  let g:detectspelllang_langs.hunspell = [ 'en_US', 'de_DE', 'es_ES', 'it_IT' ]\r\n\r\n===========================================================================\r\nCONFIGURATION\r\n===========================================================================\r\n\r\n- The value of 'g:detectspelllang_lines' defines how many lines are tested for\r\n  spelling mistakes by hunspell to derive the suitable spellcheck-language.\r\n  By default\r\n\r\n  let g:detectspelllang_lines = 1000\r\n\r\n- The values in the dictionary 'g:detectspelllang_ftoptions' define filetype-\r\n  dependent options for aspell respectively hunspell (to specify the filter mode, for example).\r\n  By default\r\n\r\n  let g:detectspelllang_ftoptions.aspell = {\r\n    \\ 'tex'   : ['--mode=tex', '--dont-tex-check-comments'],\r\n    \\ 'html'  : ['--mode=html'],\r\n    \\ 'nroff' : ['--mode=nroff'],\r\n    \\ 'perl'  : ['--mode=perl'],\r\n    \\ 'c'     : ['--mode=ccpp'],\r\n    \\ 'cpp'   : ['--mode=ccpp'],\r\n    \\ 'sgml'  : ['--mode=sgml'],\r\n    \\ 'xml'   : ['--mode=sgml'],\r\n    \\}\r\n\r\n  and\r\n\r\n  let g:detectspelllang_ftoptions.hunspell = {\r\n    \\ 'tex'   : ['-t'],\r\n    \\ 'html'  : ['-H'],\r\n    \\ 'nroff' : ['-n'],\r\n    \\ 'odt'   : ['-O'],\r\n    \\ 'xml'   : ['-X'],\r\n    \\}\r\n\r\n  Note that on Windows the most recent official aspell binaries are from\r\n  2002 and do not support all above file type options, for example, for 'tex'.\r\n\r\n- The value of 'g:detectspelllang_threshold' defines the percentage of spelling\r\n  mistakes among all words below which a spellcheck-language is recognized as\r\n  correct. For example, if\r\n\r\n  let g:detectspelllang_threshold = 20\r\n\r\n  and g:detectspelllang_langs.aspell = [ 'en_US', 'de_DE' ] and if less than 20%\r\n  of all words in the buffer are spelling mistakes for 'en_US', then\r\n  'DetectSpellLang' does not verify if the percentage of spelling mistakes for\r\n  'de_DE' is below that for 'en_US'.\r\n\r\n- The autocommand event\r\n\r\n  User DetectSpellLangUpdate\r\n\r\n  provides by the buffer-local variables b:detectspelllang_old and\r\n  b:detectspelllang_new the previous and current value of '&l:spelllang', the\r\n  spell-check language. This way, a user command, for example for adding and\r\n  removing abbreviations specific to a language, can hook in.\r\n\r\n===========================================================================\r\nISSUES\r\n===========================================================================\r\n\r\nThis plug-in vim-DetectSpellLang is developed at\r\nhttps:\/\/github.com\/konfekt\/vim-DetectSpellLang where issues can be filed.\r\n","4":"This Vim plug-in autodetects the tongue (= `&spelllang`) of the text in a\r\nbuffer (if it is spell checked, that is, `&spell` is set, and `&spelllang` has\r\nnot been explicitly set, say by a modeline :help modeline).\r\n\r\nIt uses either the spell checker aspell or hunspell (which are installed\r\nin many Linux distributions, in Mac OS, and both available for Microsoft\r\nWindows.\r\n\r\nIn Microsoft Windows the path to the executable must\r\n\r\n- be either added to the `%PATH%` environment variable (say by Rapidee from \r\n  http:\/\/www.rapidee.com), or\r\n- set by g:detectspelllang_program, say\r\n\r\n    let g:detectspelllang_program = 'C:\\Program Files (x86)\\Aspell\\bin\\aspell.exe'\r\n\r\n===========================================================================\r\nINITIAL SET-UP\r\n===========================================================================\r\n\r\nThis plug-in only operates in buffers that are spell checked, that is,\r\n&l:spell is set. To ensure that certain file types, for example 'text',\r\n'markdown' and 'mail', are spell checked, add either the line\r\n\r\n  autocmd FileType text,markdown,mail setlocal spell\r\n\r\nor the line\r\n\r\n  setlocal spell\r\n\r\nto ~\/.vim\/ftplugin\/text.vim (respectively markdown.vim and mail.vim).\r\n\r\nThe language is detected, depending on whether aspell respectively hunspell \r\nis used, among those listed in g:detectspelllang_langs.aspell respectively\r\ng:detectspelllang_langs.hunspell. It is *empty* by default and has to be\r\nset by the user to a list of languages included in that of the output of the \r\ncommand aspell dicts respectively hunspell -D! \r\n\r\nFor example, in case you use aspell,\r\n\r\n  let g:detectspelllang_langs = {}\r\n  let g:detectspelllang_langs.aspell = [ 'en_US', 'de_DE', 'es', 'it' ]\r\n\r\nrespectively, in case you use hunspell,\r\n\r\n  let g:detectspelllang_langs.hunspell = [ 'en_US', 'de_DE', 'es_ES', 'it_IT' ]\r\n\r\n===========================================================================\r\nCONFIGURATION\r\n===========================================================================\r\n\r\n- The value of 'g:detectspelllang_lines' defines how many lines are tested for\r\n  spelling mistakes by hunspell to derive the suitable spellcheck-language.\r\n  By default\r\n\r\n  let g:detectspelllang_lines = 1000\r\n\r\n- The values in the dictionary 'g:detectspelllang_ftoptions' define filetype-\r\n  dependent options for aspell respectively hunspell (to specify the filter mode, for example).\r\n  By default\r\n\r\n  let g:detectspelllang_ftoptions.aspell = {\r\n    \\ 'tex'   : ['--mode=tex', '--dont-tex-check-comments'],\r\n    \\ 'html'  : ['--mode=html'],\r\n    \\ 'nroff' : ['--mode=nroff'],\r\n    \\ 'perl'  : ['--mode=perl'],\r\n    \\ 'c'     : ['--mode=ccpp'],\r\n    \\ 'cpp'   : ['--mode=ccpp'],\r\n    \\ 'sgml'  : ['--mode=sgml'],\r\n    \\ 'xml'   : ['--mode=sgml'],\r\n    \\}\r\n\r\n  and\r\n\r\n  let g:detectspelllang_ftoptions.hunspell = {\r\n    \\ 'tex'   : ['-t'],\r\n    \\ 'html'  : ['-H'],\r\n    \\ 'nroff' : ['-n'],\r\n    \\ 'odt'   : ['-O'],\r\n    \\ 'xml'   : ['-X'],\r\n    \\}\r\n\r\n  Note that on Windows the most recent official aspell binaries are from\r\n  2002 and do not support all above file type options, for example, for 'tex'.\r\n\r\n- The value of 'g:detectspelllang_threshold' defines the percentage of spelling\r\n  mistakes among all words below which a spellcheck-language is recognized as\r\n  correct. For example, if\r\n\r\n  let g:detectspelllang_threshold = 20\r\n\r\n  and g:detectspelllang_langs.aspell = [ 'en_US', 'de_DE' ] and if less than 20%\r\n  of all words in the buffer are spelling mistakes for 'en_US', then\r\n  'DetectSpellLang' does not verify if the percentage of spelling mistakes for\r\n  'de_DE' is below that for 'en_US'.\r\n\r\n- The autocommand event\r\n\r\n  User DetectSpellLangUpdate\r\n\r\n  provides by the buffer-local variables b:detectspelllang_old and\r\n  b:detectspelllang_new the previous and current value of '&l:spelllang', the\r\n  spell-check language. This way, a user command, for example for adding and\r\n  removing abbreviations specific to a language, can hook in.\r\n\r\n===========================================================================\r\nISSUES\r\n===========================================================================\r\n\r\nThis plug-in vim-DetectSpellLang is developed at\r\nhttps:\/\/github.com\/konfekt\/vim-DetectSpellLang where issues can be filed.\r\n","install_details":"Unzip vim-guesslang.zip into  ~\/.vim on Linux (or MacOS) respectively %USERPROFILE%\\vimfiles on Windows.","5":"Unzip vim-guesslang.zip into  ~\/.vim on Linux (or MacOS) respectively %USERPROFILE%\\vimfiles on Windows.","first_name":"Enno","6":"Enno","last_name":"Nagel","7":"Nagel","releases":[{"0":"5489","vim_version":"7.0","1":"7.0","script_version":"2.2","2":"2.2","version_comment":"support hunspell as well as aspell and autodetect spelllang on enabling spell check","3":"support hunspell as well as aspell and autodetect spelllang on enabling spell check","package":"vim-DetectSpellLang.zip","4":"vim-DetectSpellLang.zip","src_id":"26917","5":"26917","creation_date":"1578943296","6":"1578943296"},{"0":"5489","vim_version":"7.0","1":"7.0","script_version":"1.2","2":"1.2","version_comment":"restrict to lines likely to contain prose ","3":"restrict to lines likely to contain prose ","package":"vim-DetectSpellLang.zip","4":"vim-DetectSpellLang.zip","src_id":"26891","5":"26891","creation_date":"1578515799","6":"1578515799"},{"0":"5489","vim_version":"7.0","1":"7.0","script_version":"1.1","2":"1.1","version_comment":"add configuration options and fix tidbits","3":"add configuration options and fix tidbits","package":"vim-DetectSpellLang.zip","4":"vim-DetectSpellLang.zip","src_id":"26603","5":"26603","creation_date":"1562794853","6":"1562794853"},{"0":"5489","vim_version":"7.4","1":"7.4","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"vim-guesslang.zip","4":"vim-guesslang.zip","src_id":"24767","5":"24767","creation_date":"1480285893","6":"1480285893"}]},"5488":{"script_id":"5488","0":"5488","script_name":"flatwhite","1":"flatwhite","script_type":"color scheme","2":"color scheme","summary":"A Vim port of biletskyy\u00e2\u0080\u0099s flatwhite-syntax for Atom","3":"A Vim port of biletskyy\u00e2\u0080\u0099s flatwhite-syntax for Atom","description":"A Vim port of https:\/\/github.com\/biletskyy\/flatwhite-syntax (see for screenshots).","4":"A Vim port of https:\/\/github.com\/biletskyy\/flatwhite-syntax (see for screenshots).","install_details":"Drop in ~\/.vim\/colors\r\nor better yet\r\nuse this GitHub address with your plugin manager of choice: https:\/\/github.com\/kamwitsta\/flatwhite-vim","5":"Drop in ~\/.vim\/colors\r\nor better yet\r\nuse this GitHub address with your plugin manager of choice: https:\/\/github.com\/kamwitsta\/flatwhite-vim","first_name":"kamil","6":"kamil","last_name":"stachowski","7":"stachowski","releases":[{"0":"5488","vim_version":"8.0","1":"8.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"flatwhite.vim","4":"flatwhite.vim","src_id":"24763","5":"24763","creation_date":"1480094647","6":"1480094647"}]},"5487":{"script_id":"5487","0":"5487","script_name":"ViewMaps","1":"ViewMaps","script_type":"utility","2":"utility","summary":"Lightweight plugin for viewing mappings from vimrc","3":"Lightweight plugin for viewing mappings from vimrc","description":"You can use this plugin to populate a list of your vimrc mappings in the QuickFix window. The mappings can be retrieved by VIm mode types (like normal, insert, visual, select and operator-pending mode).\r\n\r\nThe :map command displays all availabe and loaded mappings in VIm and that list contains too much to process just by looking at it. This plugin helps you view only the ones defined by you with comments related to them.\r\n\r\nMappings can be many, this is why filtering is possible for different modes. By populating the QuickFix window you can quickly jump to the vimrc file on the exact line where the mappings are defined. Comments are also displayed: currently it only displays one line comments from the line right above the mappings or comments at the end of the mapping line, starting with the last available \" character to the end of the line.\r\n\r\nGet the plugin from here on Github: https:\/\/github.com\/robcsi\/viewmaps.vim.git\r\n\r\nYou can use Pathogen to include it into your plugin bundle.\r\n\r\nOther features include:\r\n\r\n    The plugin tries to detect rc files that are sourced in your main vimrc. Only lines starting with 'source' are parsed and mappings loaded from those files, too\r\n\r\n    Mappings can be displayed in the Quickfix window or an echoed list, like the 'map' command does, just for quick reference. The display formatting is different in this case, compared to the QuickFix format\r\n\r\n    In the Quickfix window (leveraging its functionality) you can press and go to the selected line in the main or sourced vimrc file. There you can edit the mapping or its comment as desired and maybe reload the list of mappings into the QuickFix window\r\n\r\n    There is an option for configuring the position of the QuickFix window, g:viewmaps_quickfix_orientation (horizontal or vertical)\r\n\r\n    There is an option for configuring the width or height of the Quickfix window depending on what its position is: g:viewmaps_quickfix_dimension\r\n\r\n    The plugin leverages the functionality of the QuickFix window by using jumping to lines in the rc files, also leverages the [q and ]q et.al. keyboard shortcuts defined by the vim-unimpaired plugin\r\n\r\nFor more information read the help file. :h viewmaps","4":"You can use this plugin to populate a list of your vimrc mappings in the QuickFix window. The mappings can be retrieved by VIm mode types (like normal, insert, visual, select and operator-pending mode).\r\n\r\nThe :map command displays all availabe and loaded mappings in VIm and that list contains too much to process just by looking at it. This plugin helps you view only the ones defined by you with comments related to them.\r\n\r\nMappings can be many, this is why filtering is possible for different modes. By populating the QuickFix window you can quickly jump to the vimrc file on the exact line where the mappings are defined. Comments are also displayed: currently it only displays one line comments from the line right above the mappings or comments at the end of the mapping line, starting with the last available \" character to the end of the line.\r\n\r\nGet the plugin from here on Github: https:\/\/github.com\/robcsi\/viewmaps.vim.git\r\n\r\nYou can use Pathogen to include it into your plugin bundle.\r\n\r\nOther features include:\r\n\r\n    The plugin tries to detect rc files that are sourced in your main vimrc. Only lines starting with 'source' are parsed and mappings loaded from those files, too\r\n\r\n    Mappings can be displayed in the Quickfix window or an echoed list, like the 'map' command does, just for quick reference. The display formatting is different in this case, compared to the QuickFix format\r\n\r\n    In the Quickfix window (leveraging its functionality) you can press and go to the selected line in the main or sourced vimrc file. There you can edit the mapping or its comment as desired and maybe reload the list of mappings into the QuickFix window\r\n\r\n    There is an option for configuring the position of the QuickFix window, g:viewmaps_quickfix_orientation (horizontal or vertical)\r\n\r\n    There is an option for configuring the width or height of the Quickfix window depending on what its position is: g:viewmaps_quickfix_dimension\r\n\r\n    The plugin leverages the functionality of the QuickFix window by using jumping to lines in the rc files, also leverages the [q and ]q et.al. keyboard shortcuts defined by the vim-unimpaired plugin\r\n\r\nFor more information read the help file. :h viewmaps","install_details":"Clone the plugin from Github and install with Pathogen: https:\/\/github.com\/robcsi\/viewmaps.vim.git","5":"Clone the plugin from Github and install with Pathogen: https:\/\/github.com\/robcsi\/viewmaps.vim.git","first_name":"Robert","6":"Robert","last_name":"Sarkozi","7":"Sarkozi","releases":[{"0":"5487","vim_version":"7.4","1":"7.4","script_version":"0.1.0","2":"0.1.0","version_comment":"Initial upload","3":"Initial upload","package":"viewmaps.zip","4":"viewmaps.zip","src_id":"24759","5":"24759","creation_date":"1479838563","6":"1479838563"}]},"5486":{"script_id":"5486","0":"5486","script_name":"vim-yesod","1":"vim-yesod","script_type":"syntax","2":"syntax","summary":"Syntax and utility for the Haskell Yesod web framework","3":"Syntax and utility for the Haskell Yesod web framework","description":"This may be out of date, use:   https:\/\/github.com\/alx741\/vim-yesod\r\n\r\nSyntax and utility for the Haskell Yesod web framework","4":"This may be out of date, use:   https:\/\/github.com\/alx741\/vim-yesod\r\n\r\nSyntax and utility for the Haskell Yesod web framework","install_details":"","5":"","first_name":"Daniel","6":"Daniel","last_name":"Campoverde","7":"Campoverde","releases":[{"0":"5486","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"vim-yesod.tar.gz","4":"vim-yesod.tar.gz","src_id":"24748","5":"24748","creation_date":"1479502915","6":"1479502915"}]},"5485":{"script_id":"5485","0":"5485","script_name":"vim-shaderlab","1":"vim-shaderlab","script_type":"syntax","2":"syntax","summary":"Unity ShaderLab","3":"Unity ShaderLab","description":"Unity ShaderLab Syntax highlighting","4":"Unity ShaderLab Syntax highlighting","install_details":"Pathogen compatible","5":"Pathogen compatible","first_name":"mingchao","6":"mingchao","last_name":"yan","7":"yan","releases":[{"0":"5485","vim_version":"7.0","1":"7.0","script_version":"0.0.1","2":"0.0.1","version_comment":"Initial upload","3":"Initial upload","package":"vim-shaderlab-0.0.1.tar.gz","4":"vim-shaderlab-0.0.1.tar.gz","src_id":"24747","5":"24747","creation_date":"1479476083","6":"1479476083"}]},"5484":{"script_id":"5484","0":"5484","script_name":"syn-preproc","1":"syn-preproc","script_type":"syntax","2":"syntax","summary":"C preprocessor syntax on top of other syntaxes.","3":"C preprocessor syntax on top of other syntaxes.","description":"DESCRIPTION\r\nThis syntax extension highlights C preprocessor directives and (optionally)\r\nfolds preprocessor conditions. You can use this as a standalone syntax, or add\r\nthis on top of another filetype.\r\n\r\nUSAGE\r\nIf you have certain files of a particular filetype (e.g. Tcl) that contain\r\npreprocessing directives, you can add a custom filetype detection (here: for a\r\n\"Tcl template\" .tclt file extension; cp. new-filetype), and set a compound\r\nfiletype:\r\n    autocmd BufNewFile,BufRead *.tclt setf tcl.preproc\r\n\r\nTo add the highlighting to the file's existing syntax, use:\r\n    :setf =&filetype.preproc\r\n\r\nTo just have preprocessing highlighting (and no other syntax), use:\r\n    :setlocal syntax=preproc\r\n\r\nNote: This script supports both the normal \"#...\" syntax as well as the\r\nalternative \"%:...\" digraph (or alternative token) for the '#' punctuator.\r\n","4":"DESCRIPTION\r\nThis syntax extension highlights C preprocessor directives and (optionally)\r\nfolds preprocessor conditions. You can use this as a standalone syntax, or add\r\nthis on top of another filetype.\r\n\r\nUSAGE\r\nIf you have certain files of a particular filetype (e.g. Tcl) that contain\r\npreprocessing directives, you can add a custom filetype detection (here: for a\r\n\"Tcl template\" .tclt file extension; cp. new-filetype), and set a compound\r\nfiletype:\r\n    autocmd BufNewFile,BufRead *.tclt setf tcl.preproc\r\n\r\nTo add the highlighting to the file's existing syntax, use:\r\n    :setf =&filetype.preproc\r\n\r\nTo just have preprocessing highlighting (and no other syntax), use:\r\n    :setlocal syntax=preproc\r\n\r\nNote: This script supports both the normal \"#...\" syntax as well as the\r\nalternative \"%:...\" digraph (or alternative token) for the '#' punctuator.\r\n","install_details":"INSTALLATION\r\nThis script is packaged as a vimball. If you have the \"gunzip\" decompressor\r\nin your PATH, simply edit the *.vmb.gz package in Vim; otherwise, decompress\r\nthe archive first, e.g. using WinZip. Inside Vim, install by sourcing the\r\nvimball or via the :UseVimball command.\r\n    vim syn-preproc*.vmb.gz\r\n    :so %\r\nTo uninstall, use the :RmVimball command.\r\n\r\nDEPENDENCIES\r\n- Requires Vim 7.0 or higher.\r\n\r\nCONFIGURATION\r\nFor a permanent configuration, put the following commands into your vimrc:\r\n\r\nC\/C++-style comments are typically removed by the preprocessor and thus\r\nhighlighted as other comments. You can define a different highlighting if you\r\nwant to visually distinguish them from the default comments of that filetype:\r\n    hi link preprocComment NonText\r\nOr turn highlighting of comments off:\r\n    let preproc_no_comments = 1\r\nMulti-line C-style comments are folded; if you do not want this, use:\r\n    let preproc_no_comment_fold = 1\r\n\r\nTo turn off folding of #if ... #endif conditions, use:\r\n    :let preproc_no_fold_conditions = 1\r\nLines commented out via #if 0 will still be folded. To turn that of, too,\r\nuse:\r\n    :let preproc_no_if0_fold = 1\r\nTo completely turn off highlighting (as comments) of #if 0 blocks, use:\r\n    :let preproc_no_if0 = 1\r\n","5":"INSTALLATION\r\nThis script is packaged as a vimball. If you have the \"gunzip\" decompressor\r\nin your PATH, simply edit the *.vmb.gz package in Vim; otherwise, decompress\r\nthe archive first, e.g. using WinZip. Inside Vim, install by sourcing the\r\nvimball or via the :UseVimball command.\r\n    vim syn-preproc*.vmb.gz\r\n    :so %\r\nTo uninstall, use the :RmVimball command.\r\n\r\nDEPENDENCIES\r\n- Requires Vim 7.0 or higher.\r\n\r\nCONFIGURATION\r\nFor a permanent configuration, put the following commands into your vimrc:\r\n\r\nC\/C++-style comments are typically removed by the preprocessor and thus\r\nhighlighted as other comments. You can define a different highlighting if you\r\nwant to visually distinguish them from the default comments of that filetype:\r\n    hi link preprocComment NonText\r\nOr turn highlighting of comments off:\r\n    let preproc_no_comments = 1\r\nMulti-line C-style comments are folded; if you do not want this, use:\r\n    let preproc_no_comment_fold = 1\r\n\r\nTo turn off folding of #if ... #endif conditions, use:\r\n    :let preproc_no_fold_conditions = 1\r\nLines commented out via #if 0 will still be folded. To turn that of, too,\r\nuse:\r\n    :let preproc_no_if0_fold = 1\r\nTo completely turn off highlighting (as comments) of #if 0 blocks, use:\r\n    :let preproc_no_if0 = 1\r\n","first_name":"Ingo","6":"Ingo","last_name":"Karkat","7":"Karkat","releases":[{"0":"5484","vim_version":"7.0","1":"7.0","script_version":"1.00","2":"1.00","version_comment":"Initial upload","3":"Initial upload","package":"syn-preproc-1.00.vmb.gz","4":"syn-preproc-1.00.vmb.gz","src_id":"24741","5":"24741","creation_date":"1479395022","6":"1479395022"}]},"5483":{"script_id":"5483","0":"5483","script_name":"Replay","1":"Replay","script_type":"utility","2":"utility","summary":"Convenient re-run of last recorded Vim macro","3":"Convenient re-run of last recorded Vim macro","description":"*replay.txt*                    Replay plug-in for Vim                    *replay*\r\n\r\nCONTENTS                                                       *replay-contents*\r\n\r\n1. Intro             |replay-intro|\r\n2. Implementation    |replay-implementation|\r\n3. Installation      |replay-installation|\r\n4. Website           |replay-website|\r\n5. License           |replay-license|\r\n6. Development       |replay-development|\r\n7. Authors           |replay-authors|\r\n8. History           |replay-history|\r\n\r\nINTRO                                                             *replay-intro*\r\n\r\nReplay sets up a mapping (|| by default) to execute the last recorded\r\nmacro.\r\n\r\nWithout Replay, you can execute a macro in register \"q\" by hitting |@|\r\nfollowed by \"q\", but that is relatively uncomfortable to type. Once you've\r\nplayed the macro back once, you can play it again with |@@|, which is easier\r\nbut still not as comfortable as just hitting ||.\r\n\r\n|| is chosen because its standard behavior is not super useful (moves down\r\na line, placing the cursor on the first non-blank character). You can still\r\nuse |+| to the same effect, or an alternative like |j| which is similar but does\r\nnot move to the first non-blank character.\r\n\r\nReplay won't do anything in \"special\" buffers such as |quickfix| listings or\r\n[NERDTree](https:\/\/github.com\/scrooloose\/nerdtree) explorers, because in\r\nthose the || actually does have useful navigation behavior.\r\n\r\nIMPLEMENTATION                                           *replay-implementation*\r\n\r\nI originally had this idea implemented as a simple mapping of || to |@@|,\r\nbut that was problematic for a couple of reasons: |@@| would only replay the\r\nlast executed macro, which meant that on the first run it would complain\r\nwith error |E748| that there was \"No previously used register\"; this behavior\r\nwas confusing because it would still work, sometimes, based on information\r\nrecovered from the |viminfo| file. If you're one of those who mostly records\r\ninto the \"q\" register, this meant that the mapping usually worked, but not\r\nalways, which is a pretty annoying state of affairs.\r\n\r\nAs such, Replay tries to provide \"last recorded\" rather than \"last executed\"\r\nsemantics. It does this by overriding the |q| mapping to take a snapshot of\r\nthe current register state when recording a macro. When you hit ||, it\r\nfigures out which register was updated and executes that one.\r\n\r\nNote that this is an imprecise art because Vim doesn't provide any hooks\r\nthat would allow you to know for sure which is the last-modified register\r\n(for example if you recorded to multiple registers); Replay will detect the\r\nfirst one with updated contents.\r\n\r\nOnce you've replayed a macro once with ||, you can mash it repeatedly at\r\nwill. You can also make use of recursion (ie. hitting || during a macro\r\nrecording) like you would recording any other Vim macro (although note that\r\n|| won't do anything during recording, only during playback).\r\n\r\nIf you then execute a macro from a different register (say, \"w\"), then\r\nhitting || will repeat that macro instead of the last recorded one. This\r\nbehavior is based on the notion that you usually want to repeat the last\r\nthing you did, whether that be the last thing you recorded or the last thing\r\nyou executed, whichever happened later.\r\n\r\nNote that the heuristic here will do what you want most of the time, but it\r\nis not infallible. For example, you could record into register \"q\", then\r\nplay back register \"w\", and when you hit || Replay will execute register\r\n\"q\" rather than \"w\". This is due to the lack of hooks already mentioned\r\nabove.\r\n\r\nINSTALLATION                                               *replay-installation*\r\n\r\nTo install Replay, use your plug-in management system of choice.\r\n\r\nIf you don't have a \"plug-in management system of choice\" and your version\r\nof Vim has `packages` support (ie. `+packages` appears in the output of\r\n`:version`) then you can simply place the plugin at a location under your\r\n`'packpath'` (eg. `~\/.vim\/pack\/bundle\/start\/replay` or similar).\r\n\r\nFor older versions of Vim, I recommend\r\n[Pathogen](https:\/\/github.com\/tpope\/vim-pathogen) due to its simplicity and\r\nrobustness. Assuming that you have Pathogen installed and configured, and\r\nthat you want to install Replay into `~\/.vim\/bundle`, you can do so with:\r\n>\r\n    git clone https:\/\/github.com\/wincent\/replay.git ~\/.vim\/bundle\/replay\r\n<\r\nAlternatively, if you use a Git submodule for each Vim plug-in, you could do\r\nthe following after `cd`-ing into the top-level of your Git superproject:\r\n>\r\n    git submodule add https:\/\/github.com\/wincent\/replay.git ~\/vim\/bundle\/replay\r\n    git submodule init\r\n<\r\nTo generate help tags under Pathogen, you can do so from inside Vim with:\r\n>\r\n    :call pathogen#helptags()\r\n<\r\nWEBSITE                                                         *replay-website*\r\n\r\nThe official Replay source code repo is at:\r\n\r\nhttp:\/\/git.wincent.com\/replay.git\r\n\r\nMirrors exist at:\r\n\r\n- https:\/\/github.com\/wincent\/replay\r\n- https:\/\/gitlab.com\/wincent\/replay\r\n- https:\/\/bitbucket.org\/ghurrell\/replay\r\n\r\nOfficial releases are listed at:\r\n\r\nhttp:\/\/www.vim.org\/scripts\/script.php?script_id=5483\r\n\r\nLICENSE                                                         *replay-license*\r\n\r\nCopyright (c) 2016-present Greg Hurrell\r\n\r\nPermission is hereby granted, free of charge, to any person obtaining a copy\r\nof this software and associated documentation files (the \"Software\"), to\r\ndeal in the Software without restriction, including without limitation the\r\nrights to use, copy, modify, merge, publish, distribute, sublicense, and\/or\r\nsell copies of the Software, and to permit persons to whom the Software is\r\nfurnished to do so, subject to the following conditions:\r\n\r\nThe above copyright notice and this permission notice shall be included in\r\nall copies or substantial portions of the Software.\r\n\r\nTHE SOFTWARE IS PROVIDED \"AS IS\", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR\r\nIMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,\r\nFITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE\r\nAUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER\r\nLIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING\r\nFROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS\r\nIN THE SOFTWARE.\r\n\r\nDEVELOPMENT                                                 *replay-development*\r\n\r\nContributing patches ~\r\n\r\nPatches can be sent via mail to greg@hurrell.net, or as GitHub pull requests\r\nat: https:\/\/github.com\/wincent\/replay\/pulls\r\n\r\nCutting a new release ~\r\n\r\nAt the moment the release process is manual:\r\n\r\n- Perform final sanity checks and manual testing.\r\n- Update the [replay-history](#user-content-replay-history) section of the\r\n  documentation.\r\n- Regenerate the documentation:\r\n>\r\n    docvim README.md doc\/replay.txt\r\n<\r\n- Verify clean work tree:\r\n>\r\n    git status\r\n<\r\n- Tag the release:\r\n>\r\n    git tag -s -m \"$VERSION release\" $VERSION\r\n<\r\n- Publish the code:\r\n>\r\n    git push origin master --follow-tags\r\n    git push github master --follow-tags\r\n<\r\n- Produce the release archive:\r\n>\r\n    git archive -o replay-$VERSION.zip HEAD -- .\r\n<\r\n- Upload to http:\/\/www.vim.org\/scripts\/script.php?script_id=5483\r\n\r\nAUTHORS                                                         *replay-authors*\r\n\r\nReplay is written and maintained by Greg Hurrell .\r\n","4":"*replay.txt*                    Replay plug-in for Vim                    *replay*\r\n\r\nCONTENTS                                                       *replay-contents*\r\n\r\n1. Intro             |replay-intro|\r\n2. Implementation    |replay-implementation|\r\n3. Installation      |replay-installation|\r\n4. Website           |replay-website|\r\n5. License           |replay-license|\r\n6. Development       |replay-development|\r\n7. Authors           |replay-authors|\r\n8. History           |replay-history|\r\n\r\nINTRO                                                             *replay-intro*\r\n\r\nReplay sets up a mapping (|| by default) to execute the last recorded\r\nmacro.\r\n\r\nWithout Replay, you can execute a macro in register \"q\" by hitting |@|\r\nfollowed by \"q\", but that is relatively uncomfortable to type. Once you've\r\nplayed the macro back once, you can play it again with |@@|, which is easier\r\nbut still not as comfortable as just hitting ||.\r\n\r\n|| is chosen because its standard behavior is not super useful (moves down\r\na line, placing the cursor on the first non-blank character). You can still\r\nuse |+| to the same effect, or an alternative like |j| which is similar but does\r\nnot move to the first non-blank character.\r\n\r\nReplay won't do anything in \"special\" buffers such as |quickfix| listings or\r\n[NERDTree](https:\/\/github.com\/scrooloose\/nerdtree) explorers, because in\r\nthose the || actually does have useful navigation behavior.\r\n\r\nIMPLEMENTATION                                           *replay-implementation*\r\n\r\nI originally had this idea implemented as a simple mapping of || to |@@|,\r\nbut that was problematic for a couple of reasons: |@@| would only replay the\r\nlast executed macro, which meant that on the first run it would complain\r\nwith error |E748| that there was \"No previously used register\"; this behavior\r\nwas confusing because it would still work, sometimes, based on information\r\nrecovered from the |viminfo| file. If you're one of those who mostly records\r\ninto the \"q\" register, this meant that the mapping usually worked, but not\r\nalways, which is a pretty annoying state of affairs.\r\n\r\nAs such, Replay tries to provide \"last recorded\" rather than \"last executed\"\r\nsemantics. It does this by overriding the |q| mapping to take a snapshot of\r\nthe current register state when recording a macro. When you hit ||, it\r\nfigures out which register was updated and executes that one.\r\n\r\nNote that this is an imprecise art because Vim doesn't provide any hooks\r\nthat would allow you to know for sure which is the last-modified register\r\n(for example if you recorded to multiple registers); Replay will detect the\r\nfirst one with updated contents.\r\n\r\nOnce you've replayed a macro once with ||, you can mash it repeatedly at\r\nwill. You can also make use of recursion (ie. hitting || during a macro\r\nrecording) like you would recording any other Vim macro (although note that\r\n|| won't do anything during recording, only during playback).\r\n\r\nIf you then execute a macro from a different register (say, \"w\"), then\r\nhitting || will repeat that macro instead of the last recorded one. This\r\nbehavior is based on the notion that you usually want to repeat the last\r\nthing you did, whether that be the last thing you recorded or the last thing\r\nyou executed, whichever happened later.\r\n\r\nNote that the heuristic here will do what you want most of the time, but it\r\nis not infallible. For example, you could record into register \"q\", then\r\nplay back register \"w\", and when you hit || Replay will execute register\r\n\"q\" rather than \"w\". This is due to the lack of hooks already mentioned\r\nabove.\r\n\r\nINSTALLATION                                               *replay-installation*\r\n\r\nTo install Replay, use your plug-in management system of choice.\r\n\r\nIf you don't have a \"plug-in management system of choice\" and your version\r\nof Vim has `packages` support (ie. `+packages` appears in the output of\r\n`:version`) then you can simply place the plugin at a location under your\r\n`'packpath'` (eg. `~\/.vim\/pack\/bundle\/start\/replay` or similar).\r\n\r\nFor older versions of Vim, I recommend\r\n[Pathogen](https:\/\/github.com\/tpope\/vim-pathogen) due to its simplicity and\r\nrobustness. Assuming that you have Pathogen installed and configured, and\r\nthat you want to install Replay into `~\/.vim\/bundle`, you can do so with:\r\n>\r\n    git clone https:\/\/github.com\/wincent\/replay.git ~\/.vim\/bundle\/replay\r\n<\r\nAlternatively, if you use a Git submodule for each Vim plug-in, you could do\r\nthe following after `cd`-ing into the top-level of your Git superproject:\r\n>\r\n    git submodule add https:\/\/github.com\/wincent\/replay.git ~\/vim\/bundle\/replay\r\n    git submodule init\r\n<\r\nTo generate help tags under Pathogen, you can do so from inside Vim with:\r\n>\r\n    :call pathogen#helptags()\r\n<\r\nWEBSITE                                                         *replay-website*\r\n\r\nThe official Replay source code repo is at:\r\n\r\nhttp:\/\/git.wincent.com\/replay.git\r\n\r\nMirrors exist at:\r\n\r\n- https:\/\/github.com\/wincent\/replay\r\n- https:\/\/gitlab.com\/wincent\/replay\r\n- https:\/\/bitbucket.org\/ghurrell\/replay\r\n\r\nOfficial releases are listed at:\r\n\r\nhttp:\/\/www.vim.org\/scripts\/script.php?script_id=5483\r\n\r\nLICENSE                                                         *replay-license*\r\n\r\nCopyright (c) 2016-present Greg Hurrell\r\n\r\nPermission is hereby granted, free of charge, to any person obtaining a copy\r\nof this software and associated documentation files (the \"Software\"), to\r\ndeal in the Software without restriction, including without limitation the\r\nrights to use, copy, modify, merge, publish, distribute, sublicense, and\/or\r\nsell copies of the Software, and to permit persons to whom the Software is\r\nfurnished to do so, subject to the following conditions:\r\n\r\nThe above copyright notice and this permission notice shall be included in\r\nall copies or substantial portions of the Software.\r\n\r\nTHE SOFTWARE IS PROVIDED \"AS IS\", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR\r\nIMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,\r\nFITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE\r\nAUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER\r\nLIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING\r\nFROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS\r\nIN THE SOFTWARE.\r\n\r\nDEVELOPMENT                                                 *replay-development*\r\n\r\nContributing patches ~\r\n\r\nPatches can be sent via mail to greg@hurrell.net, or as GitHub pull requests\r\nat: https:\/\/github.com\/wincent\/replay\/pulls\r\n\r\nCutting a new release ~\r\n\r\nAt the moment the release process is manual:\r\n\r\n- Perform final sanity checks and manual testing.\r\n- Update the [replay-history](#user-content-replay-history) section of the\r\n  documentation.\r\n- Regenerate the documentation:\r\n>\r\n    docvim README.md doc\/replay.txt\r\n<\r\n- Verify clean work tree:\r\n>\r\n    git status\r\n<\r\n- Tag the release:\r\n>\r\n    git tag -s -m \"$VERSION release\" $VERSION\r\n<\r\n- Publish the code:\r\n>\r\n    git push origin master --follow-tags\r\n    git push github master --follow-tags\r\n<\r\n- Produce the release archive:\r\n>\r\n    git archive -o replay-$VERSION.zip HEAD -- .\r\n<\r\n- Upload to http:\/\/www.vim.org\/scripts\/script.php?script_id=5483\r\n\r\nAUTHORS                                                         *replay-authors*\r\n\r\nReplay is written and maintained by Greg Hurrell .\r\n","install_details":"","5":"","first_name":"Greg","6":"Greg","last_name":"Hurrell","7":"Hurrell","releases":[{"0":"5483","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"- Guard against user remapping of `@`<\/strong> (https:\/\/github.com\/wincent\/replay\/issues\/4).","3":"- Guard against user remapping of `@`<\/strong> (https:\/\/github.com\/wincent\/replay\/issues\/4).","package":"replay-1.0.zip","4":"replay-1.0.zip","src_id":"26409","5":"26409","creation_date":"1551902218","6":"1551902218"},{"0":"5483","vim_version":"7.0","1":"7.0","script_version":"0.3","2":"0.3","version_comment":"- Don't move down a line when hitting || during macro recording.","3":"- Don't move down a line when hitting || during macro recording.","package":"replay-0.3.zip","4":"replay-0.3.zip","src_id":"24736","5":"24736","creation_date":"1479263967","6":"1479263967"},{"0":"5483","vim_version":"7.0","1":"7.0","script_version":"0.2","2":"0.2","version_comment":"- Make mapping customizable via |(Replay)|.\r\n- Avoid ugly stack traces for recursive macros that exceed |'maxfuncdepth'|.","3":"- Make mapping customizable via |(Replay)|.\r\n- Avoid ugly stack traces for recursive macros that exceed |'maxfuncdepth'|.","package":"replay-0.2.zip","4":"replay-0.2.zip","src_id":"24733","5":"24733","creation_date":"1479192530","6":"1479192530"},{"0":"5483","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"replay-0.1.zip","4":"replay-0.1.zip","src_id":"24731","5":"24731","creation_date":"1479142266","6":"1479142266"}]},"5482":{"script_id":"5482","0":"5482","script_name":"vim-matchit","1":"vim-matchit","script_type":"utility","2":"utility","summary":"Extended matching with \"%\"","3":"Extended matching with \"%\"","description":"This is the last version from the matchit plugin that is found on the official vim repository.\r\nThe goal is to allow use with plugin managers.\r\n\r\nGithub repository: https:\/\/github.com\/adelarsq\/vim-matchit","4":"This is the last version from the matchit plugin that is found on the official vim repository.\r\nThe goal is to allow use with plugin managers.\r\n\r\nGithub repository: https:\/\/github.com\/adelarsq\/vim-matchit","install_details":"There are several ways to install the plugin. I recommend use vim plug with this configuration on .vimrc file:\r\n\r\nPlug 'https:\/\/github.com\/adelarsq\/vim-matchit'\r\n","5":"There are several ways to install the plugin. I recommend use vim plug with this configuration on .vimrc file:\r\n\r\nPlug 'https:\/\/github.com\/adelarsq\/vim-matchit'\r\n","first_name":"Adelar","6":"Adelar","last_name":"da Silva Queir\u00c3\u00b3z","7":"da Silva Queir\u00c3\u00b3z","releases":[{"0":"5482","vim_version":"7.0","1":"7.0","script_version":"1.13.2","2":"1.13.2","version_comment":"Initial upload","3":"Initial upload","package":"matchit.vim","4":"matchit.vim","src_id":"24728","5":"24728","creation_date":"1478971324","6":"1478971324"}]},"5481":{"script_id":"5481","0":"5481","script_name":"gnugo.vim","1":"gnugo.vim","script_type":"game","2":"game","summary":"Play a game of Go in your text editor, using GnuGo","3":"Play a game of Go in your text editor, using GnuGo","description":"Play the game of Go in your Vim! Use the cursor to move around on the board, press `` to place a stone. Ask the computer to `:Undo` your move or `:Cheat` and play for you. Save and load games by writing or editing a filename.\r\n\r\nDemonstration: http:\/\/i.andrewradev.com\/d1f1769d687d198b89a96decba4c8952.gif\r\n\r\nFor more documentation, check the project at Github: https:\/\/github.com\/AndrewRadev\/gnugo.vim\r\n","4":"Play the game of Go in your Vim! Use the cursor to move around on the board, press `` to place a stone. Ask the computer to `:Undo` your move or `:Cheat` and play for you. Save and load games by writing or editing a filename.\r\n\r\nDemonstration: http:\/\/i.andrewradev.com\/d1f1769d687d198b89a96decba4c8952.gif\r\n\r\nFor more documentation, check the project at Github: https:\/\/github.com\/AndrewRadev\/gnugo.vim\r\n","install_details":"There are several ways to install the plugin. The recommended one is by using\r\nTim Pope's pathogen (http:\/\/www.vim.org\/scripts\/script.php?script_id=2332). In\r\nthat case, you can clone the plugin's git repository like so:\r\n\r\n    git clone https:\/\/github.com\/AndrewRadev\/gnugo.vim ~\/.vim\/bundle\/gnugo\r\n\r\nIf your vim configuration is under git version control, you could also set up\r\nthe repository as a submodule, which would allow you to update more easily.\r\nThe command is (provided you're in ~\/.vim):\r\n\r\n    git submodule add https:\/\/github.com\/AndrewRadev\/gnugo.vim bundle\/gnugo\r\n\r\n\r\nAnother way is to simply copy all the essential directories inside the ~\/.vim\r\ndirectory: autoload, doc, ftdetect, ftplugin, plugin, syntax.","5":"There are several ways to install the plugin. The recommended one is by using\r\nTim Pope's pathogen (http:\/\/www.vim.org\/scripts\/script.php?script_id=2332). In\r\nthat case, you can clone the plugin's git repository like so:\r\n\r\n    git clone https:\/\/github.com\/AndrewRadev\/gnugo.vim ~\/.vim\/bundle\/gnugo\r\n\r\nIf your vim configuration is under git version control, you could also set up\r\nthe repository as a submodule, which would allow you to update more easily.\r\nThe command is (provided you're in ~\/.vim):\r\n\r\n    git submodule add https:\/\/github.com\/AndrewRadev\/gnugo.vim bundle\/gnugo\r\n\r\n\r\nAnother way is to simply copy all the essential directories inside the ~\/.vim\r\ndirectory: autoload, doc, ftdetect, ftplugin, plugin, syntax.","first_name":"Andrew","6":"Andrew","last_name":"Radev","7":"Radev","releases":[{"0":"5481","vim_version":"8.0","1":"8.0","script_version":"0.2.0","2":"0.2.0","version_comment":"Initial upload","3":"Initial upload","package":"gnugo.zip","4":"gnugo.zip","src_id":"24714","5":"24714","creation_date":"1478593995","6":"1478593995"}]},"5480":{"script_id":"5480","0":"5480","script_name":"StyleGuide","1":"StyleGuide","script_type":"utility","2":"utility","summary":"Code with google-syleguide. Readability, quality and unity well be better","3":"Code with google-syleguide. Readability, quality and unity well be better","description":"Code with google-syleguide. Readability, quality and unity of your code will be better\r\nOr if you have own styleguide, share with your team members\r\n\r\ngoogle-syleguide 를 참고하면서 프로그래밍하세요. 코드의 가독성과 품질이 좋아지고, 통일성이 유지될 것입니다.\r\n또는 당신만의 styleguide 가 있다면 팀원들과 공유하세요\r\n\r\nThis vim plugin comes with following features:\r\n* Show the google-syleguide in split window\r\n* Good to see as folding by same contents\r\n* Shortcuts to toggle folds and to navigate\r\n\r\nSee the GitHub page (https:\/\/github.com\/ltlkodae\/StyleGuide.vim) ","4":"Code with google-syleguide. Readability, quality and unity of your code will be better\r\nOr if you have own styleguide, share with your team members\r\n\r\ngoogle-syleguide 를 참고하면서 프로그래밍하세요. 코드의 가독성과 품질이 좋아지고, 통일성이 유지될 것입니다.\r\n또는 당신만의 styleguide 가 있다면 팀원들과 공유하세요\r\n\r\nThis vim plugin comes with following features:\r\n* Show the google-syleguide in split window\r\n* Good to see as folding by same contents\r\n* Shortcuts to toggle folds and to navigate\r\n\r\nSee the GitHub page (https:\/\/github.com\/ltlkodae\/StyleGuide.vim) ","install_details":"1. Copy StyleGuide.vim to your ~\/.vim\/plugin\r\n2. Store styleguide xml files of google-syleguide to g:StyleGuideXmlPath.\r\n3. Put the following lines in your .vimrc\r\n\r\n\" the path where styleguide files are stored (shoud be changed to yours)\r\nlet g:StyleGuideXmlPath = '\/user\/ltlkodae\/.vim\/doc\/styleguide'\r\n\r\nSee the GitHub page (https:\/\/github.com\/ltlkodae\/StyleGuide.vim) ","5":"1. Copy StyleGuide.vim to your ~\/.vim\/plugin\r\n2. Store styleguide xml files of google-syleguide to g:StyleGuideXmlPath.\r\n3. Put the following lines in your .vimrc\r\n\r\n\" the path where styleguide files are stored (shoud be changed to yours)\r\nlet g:StyleGuideXmlPath = '\/user\/ltlkodae\/.vim\/doc\/styleguide'\r\n\r\nSee the GitHub page (https:\/\/github.com\/ltlkodae\/StyleGuide.vim) ","first_name":"daesung","6":"daesung","last_name":"ko","7":"ko","releases":[{"0":"5480","vim_version":"7.0","1":"7.0","script_version":"1.0.0","2":"1.0.0","version_comment":"Initial upload","3":"Initial upload","package":"vim_style_guide_1.0.0.zip","4":"vim_style_guide_1.0.0.zip","src_id":"24709","5":"24709","creation_date":"1478531141","6":"1478531141"}]},"5479":{"script_id":"5479","0":"5479","script_name":"vim-makejob","1":"vim-makejob","script_type":"utility","2":"utility","summary":"Minimal, asynchronous quickfix commands for Vim 8.0","3":"Minimal, asynchronous quickfix commands for Vim 8.0","description":"This is a plugin for folks who think that Vim's quickfix feature is great, but who don't like how calls to :make and :grep freeze the editor. MakeJob implements asynchronous versions of the builtin commands in just over 150 lines of Vimscript.\r\n\r\nMore details: https:\/\/git.danielmoch.com\/vim-makejob\/file\/README.md.html","4":"This is a plugin for folks who think that Vim's quickfix feature is great, but who don't like how calls to :make and :grep freeze the editor. MakeJob implements asynchronous versions of the builtin commands in just over 150 lines of Vimscript.\r\n\r\nMore details: https:\/\/git.danielmoch.com\/vim-makejob\/file\/README.md.html","install_details":"Unassisted: Extract in ~\/.vim\r\n\r\nPathogen: Extract in ~\/.vim\/bundle, or wherever you host your Pathogen-managed plugins\r\n\r\nPlug.vim: Plug 'git:\/\/git.danielmoch.com\/vim-makejob.git'\r\n\r\n(For Windows, change ~\/.vim to ~\\vimfiles).\r\n\r\nArch Linux users can install system-wide by using the vim-makejob package in the AUR.","5":"Unassisted: Extract in ~\/.vim\r\n\r\nPathogen: Extract in ~\/.vim\/bundle, or wherever you host your Pathogen-managed plugins\r\n\r\nPlug.vim: Plug 'git:\/\/git.danielmoch.com\/vim-makejob.git'\r\n\r\n(For Windows, change ~\/.vim to ~\\vimfiles).\r\n\r\nArch Linux users can install system-wide by using the vim-makejob package in the AUR.","first_name":"Daniel","6":"Daniel","last_name":"Moch","7":"Moch","releases":[{"0":"5479","vim_version":"8.0","1":"8.0","script_version":"1.3.1","2":"1.3.1","version_comment":"Minor bug fixes","3":"Minor bug fixes","package":"vim-makejob.zip","4":"vim-makejob.zip","src_id":"26304","5":"26304","creation_date":"1545336684","6":"1545336684"},{"0":"5479","vim_version":"8.0","1":"8.0","script_version":"1.3.0","2":"1.3.0","version_comment":"Added method to cancel a running job (see vimdoc).\r\n\r\nVarious bug fixes and enhancements.","3":"Added method to cancel a running job (see vimdoc).\r\n\r\nVarious bug fixes and enhancements.","package":"vim-makejob.zip","4":"vim-makejob.zip","src_id":"25727","5":"25727","creation_date":"1513953308","6":"1513953308"},{"0":"5479","vim_version":"8.0","1":"8.0","script_version":"1.2","2":"1.2","version_comment":"Add a global option to hide the preview window during execution","3":"Add a global option to hide the preview window during execution","package":"vim-makejob.zip","4":"vim-makejob.zip","src_id":"25064","5":"25064","creation_date":"1491168667","6":"1491168667"},{"0":"5479","vim_version":"8.0","1":"8.0","script_version":"1.1.2","2":"1.1.2","version_comment":"Bug fixes and enhancements:\r\n1. Properly handle escaped special characters in makeprg and grepprg.\r\n2. Follow best practices for plugin loading","3":"Bug fixes and enhancements:\r\n1. Properly handle escaped special characters in makeprg and grepprg.\r\n2. Follow best practices for plugin loading","package":"vim-makejob.zip","4":"vim-makejob.zip","src_id":"24951","5":"24951","creation_date":"1486466639","6":"1486466639"},{"0":"5479","vim_version":"8.0","1":"8.0","script_version":"1.1.1","2":"1.1.1","version_comment":"Proper expansion of special characters in makeprg and grepprg","3":"Proper expansion of special characters in makeprg and grepprg","package":"vim-makejob.zip","4":"vim-makejob.zip","src_id":"24794","5":"24794","creation_date":"1481374427","6":"1481374427"},{"0":"5479","vim_version":"8.0","1":"8.0","script_version":"1.1","2":"1.1","version_comment":"Add support for GrepJob and friends","3":"Add support for GrepJob and friends","package":"vim-makejob.zip","4":"vim-makejob.zip","src_id":"24762","5":"24762","creation_date":"1480011918","6":"1480011918"},{"0":"5479","vim_version":"8.0","1":"8.0","script_version":"1.0.1","2":"1.0.1","version_comment":"Bug fixes:\r\n1. Use 'echomsg' instead of 'echo' for warning message\r\n2. Handle 'stderr' in addition to 'stdout'","3":"Bug fixes:\r\n1. Use 'echomsg' instead of 'echo' for warning message\r\n2. Handle 'stderr' in addition to 'stdout'","package":"vim-makejob.zip","4":"vim-makejob.zip","src_id":"24751","5":"24751","creation_date":"1479558080","6":"1479558080"},{"0":"5479","vim_version":"8.0","1":"8.0","script_version":"1.0","2":"1.0","version_comment":"Version 1.0 release!\r\nMakeJob now opens a buffer to display job output, approximating the behavior of :make without interrupting your workflow.","3":"Version 1.0 release!\r\nMakeJob now opens a buffer to display job output, approximating the behavior of :make without interrupting your workflow.","package":"vim-makejob.zip","4":"vim-makejob.zip","src_id":"24727","5":"24727","creation_date":"1478970433","6":"1478970433"}]},"5478":{"script_id":"5478","0":"5478","script_name":"mythos","1":"mythos","script_type":"color scheme","2":"color scheme","summary":"A dark, low contrast, Cthulhu-esque colour scheme","3":"A dark, low contrast, Cthulhu-esque colour scheme","description":"See the screenshots at the GitHub page at https:\/\/github.com\/kamwitsta\/mythos","4":"See the screenshots at the GitHub page at https:\/\/github.com\/kamwitsta\/mythos","install_details":"Copy to ~\/.vim\/colors or use your favourite package manager with this address: https:\/\/github.com\/kamwitsta\/mythos.","5":"Copy to ~\/.vim\/colors or use your favourite package manager with this address: https:\/\/github.com\/kamwitsta\/mythos.","first_name":"kamil","6":"kamil","last_name":"stachowski","7":"stachowski","releases":[{"0":"5478","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"mythos.vim","4":"mythos.vim","src_id":"24705","5":"24705","creation_date":"1478450831","6":"1478450831"}]},"5477":{"script_id":"5477","0":"5477","script_name":"vim-codequery","1":"vim-codequery","script_type":"utility","2":"utility","summary":"An asynchronous code searcher","3":"An asynchronous code searcher","description":"\r\n\r\n\r\nOfficial Website:https:\/\/github.com\/devjoe\r\n\r\n\r\n\r\n\r\n![](https:\/\/github.com\/ruben2020\/codequery\/raw\/master\/doc\/logotitle.png)\r\n  \r\n  \r\n  \r\n> Choose what you want to know! 😼\r\n     \r\n```vim\r\n\" Open menu\r\n:CodeQueryMenu Unite Full\r\n\r\n\" Or query directly\r\n:CodeQuery Definition get_user_id\r\n```\r\n  
  \r\n  
\r\n\r\n# vim-codequery\r\n  \r\nThis Vim plugin is built on top of the great tool [CodeQuery](https:\/\/github.com\/ruben2020\/codequery) created by ruben2020, and aims at providing three primary functions to help you to:\r\n  \r\n1. **Search source code gracefully within Vim**.\r\n    * You can find: `definition, call, caller, callee, symbol, class, parent, child` and more for a string.\r\n    * Convenient menus are created for you.\r\n    * Well-formated results are shown in a custom Quickfix window with usable key bindings.\r\n    * Support asynchronous search (Vim version >= 8.0)\r\n2. **Manage your database easily**.\r\n    * Load, make and move your database file by custom Vim commands.\r\n    * Support asynchronous build (Vim version >= 8.0 or by `Dispatch` plugin)\r\n    * `Note: CodeQuery's SQLite database is built on top of ctags and cscope.`\r\n3. **Know your code more instantly**.\r\n    * (TBD)\r\n  \r\n
\r\n\r\n##  Supported languages\r\n  * [x] `Python` 😎\r\n  * [x] `Javascript`\r\n  * [x] `Ruby`\r\n  * [x] `Go` \r\n  * [x] `Java`\r\n  * [x] `C, C++`\r\n  \r\n
\r\n  \r\n## Demo\r\n\r\n`Choose a query from menu ➙ Get results`  \r\n\r\n![](https:\/\/db.tt\/rf6fO2eJ)\r\n\r\n`... ➙ Switch to different query ➙ Get results ... ➙ Filter them ➙ Get Results ➙ Undo ➙ Redo`  \r\n\r\n![](https:\/\/db.tt\/KoZORec3)\r\n  \r\n[more demo and screenshots](https:\/\/github.com\/devjoe\/vim-codequery\/wiki\/Screenshots-and-Demo)  \r\n    \r\n```\r\nThese videos are quite old.   \r\nNow vim-codequery works better than what you see by using Vim8's async feature.\r\n```\r\n
\r\n  \r\n## Schedule\r\n\r\n> **This project is almost ready to be released.**   \r\n>  \r\n> Main TODO:\r\n> * ~~Use Vim8's new features to enhance usability.~~\r\n> * ~~Do lazy-loading.~~\r\n> * Enhance usability.\r\n> * Test it.\r\n> * Doc it.\r\n>  \r\n> Completeness: 94%  \r\n> Current Version: v0.9  \r\n>  \r\n> Welcome to try it! 👌  \r\n  \r\n
\r\n  \r\n## Installation\r\n\r\n#### 1. Make sure these commands are in your system\r\n
\r\n\/bin\/sh echo mkdir mv cut find awk stat git(optional)\r\n<\/pre>\r\n\r\n#### 2. Install CodeQuery\r\n* Linux => Install [binaries](https:\/\/sourceforge.net\/projects\/codequery\/files\/) or [build it](https:\/\/github.com\/ruben2020\/codequery\/blob\/master\/doc\/INSTALL-LINUX.md).\r\n* Mac => `brew install codequery` 🍺 (make sure codequery version >= v0.17.0)\r\n\r\n#### 3. Install additional ctags\/cscope tools for your languages\r\n| Language | Tools | How to install |\r\n| --- | --- | --- |  \r\n| Python | [PyCscope](https:\/\/github.com\/portante\/pycscope) | `sudo pip install pycscope` | \r\n| Javascript | [Starscope](https:\/\/github.com\/eapache\/starscope) | `sudo gem install starscope` |\r\n| Ruby | [Starscope](https:\/\/github.com\/eapache\/starscope) | `sudo gem install starscope` |\r\n| Go | [Starscope](https:\/\/github.com\/eapache\/starscope) | `sudo gem install starscope` |\r\n\r\n> `Java`, `C` and `C++` users do not need to install additional ctags\/cscope tools.  \r\n> Starscope has been [packaged for Arch Linux](https:\/\/aur.archlinux.org\/packages\/ruby-starscope\/)    \r\n\r\n#### 4. Install Vim plugins\r\n* Use your favorite plugins manager: [pathogen](https:\/\/github.com\/tpope\/vim-pathogen), [Vundle](https:\/\/github.com\/VundleVim\/Vundle.vim), [Plug](https:\/\/github.com\/junegunn\/vim-plug), [NeoBundle](https:\/\/github.com\/Shougo\/neobundle.vim), [Dein](https:\/\/github.com\/Shougo\/dein.vim),  ...\r\n* Take Plug as an example:  \r\n```vim\r\n\" Required\r\nPlug 'Shougo\/unite.vim'\r\nPlug 'devjoe\/vim-codequery'\r\n  \r\n\" Optional\r\n\" if your vim version < 8.0\r\nPlug 'tpope\/vim-dispatch'\r\n\" if you don't have an :Ack (or :Ag) liked command\r\nPlug 'mileszs\/ack.vim'\r\n```\r\n  \r\n
\r\n  \r\n## Usage\r\n\r\n#### 1. Setup\r\n\r\n* Go to the (git) root directory of your project. Open vim and type:\r\n```vim\r\n\" Index Python files\r\n:CodeQueryMakeDB python\r\n  \r\n\" Or index Python + Javascript files\r\n:CodeQueryMakeDB python javascript \r\n```\r\n* That's all. `python.db`, `javascript.db` ... will be created in the root directory. \r\n* It's recommended that you should use `:CodeQueryMoveDBToGitDir python` to hide the DB file to `.git\/codequery\/` directory. If you do so, next time you can call `:CodeQueryMakeDB` directly in any opened Python buffer to rebuild the DB file.\r\n\r\n\r\n#### 2. Search\r\n* **Find symbol under your cursor**  \r\n\r\n```vim  \r\n:CodeQuery\r\n```  \r\n\r\n* **Find word (by subcommands) under your cursor**  \r\n\r\n```vim  \r\n:CodeQuery [SubCommand]  \r\n  \r\n\" Supported SubCommands are: `Symbol, Text, Call, Caller, Callee, Class, Parent, Child, Member, FunctionList, FileImporter`.  \r\n```  \r\n\r\n* **Find arbitrary word**\r\n\r\n```vim\r\n:CodeQuery [SubCommand] [word]  \r\n```\r\n  \r\n* **Find again with the same word**\r\n\r\n```vim\r\n:CodeQueryAgain [SubCommand]  \r\n```\r\n\r\n* **Use fuzzy Option**    \r\n\r\n```vim\r\n:CodeQuery [SubCommand] [word] -f  \r\n  \r\n\" [word] can be: get_* or *user_info or find_*_by_id\r\n```\r\n\r\n* **Use append Option** (results will be added to the current Quickfix)    \r\n\r\n```vim\r\n:CodeQuery [SubCommand] [word] -a  \r\n```\r\n\r\n* **Filter Search Results**  \r\n\r\n```vim\r\n:CodeQueryFilter [string]  \r\n  \r\n\" [string] can be a regex\r\n```\r\n    \r\n#### 3. Use Quickfix\r\n* **Move your cursor inside Quickfix window to use these key bindings**\r\n\r\n| Key | Action | Note | \r\n| --- | --- | --- | \r\n| s | `:CodeQueryAgain Symbol` | |\r\n| x | `:CodeQueryAgain Text` | use `:Ack!` by default. #1 | \r\n| c | `:CodeQueryAgain Call` | |\r\n| r | `:CodeQueryAgain Caller` | |\r\n| e | `:CodeQueryAgain Callee` | |\r\n| d | `:CodeQueryAgain Definition` | |\r\n| C | `:CodeQueryAgain Class` | |\r\n| M | `:CodeQueryAgain Member` | |\r\n| P | `:CodeQueryAgain Parent` | |\r\n| D | `:CodeQueryAgain Child` | |\r\n| m | `:CodeQueryMenu Unite Magic` | |\r\n| q | `:cclose` | |\r\n| \\ | `:CodeQueryFilter` | |\r\n| p | `p` | Preview |\r\n| u | `:colder \\| CodeQueryShowQF` | Older Quickfix Result | \r\n| \\ | `:cnewer \\| CodeQueryShowQF` | Newer Quickfix Result | \r\n  \r\n>  #1 \r\n> You can override `g:codequery_find_text_cmd` to change it.\r\n\r\n* **Show Quickfix with above key bindings**\r\n\r\n```vim\r\n:CodeQueryShowQF  \r\n  \r\n\" This command can also be used to **patch** standard Quickfix.\r\n```\r\n\r\n#### 4. Open Menu\r\n\r\nCurrently, vim-codequery only provides [Unite](https:\/\/github.com\/Shougo\/unite.vim) menu because I love it ⭐.  There are two types of menu:\r\n\r\n* **Full Unite menu**\r\n\r\n```vim\r\n:CodeQueryMenu Unite Full  \r\n  \r\n\" The string between :: and :: is the word under cursor\r\n\" [F] means this action is for 'function variable only'\r\n\" [C] is for 'class variable only'  \r\n```\r\n   \r\n    \r\n* **Magic Unite menu**\r\n\r\n```vim\r\n:CodeQueryMenu Unite Magic  \r\n  \r\n\" This menu changes dynamically:\r\n\" 1. If the word under your cursor begins with a capital letter (possible be class): show [C] actions\r\n\" 2. vice versa (possible be function): show [F] actions\r\n\" 3. Show reasonable actions within Quickfix\r\n```\r\n   \r\n  \r\n
\r\n  \r\n## Tips\r\n#### Open Menu  \r\n```vim\r\nnnoremap c :CodeQueryMenu Unite Full\r\nnnoremap ; :CodeQueryMenu Unite Magic\r\n  \r\n\" Or enable typing (to search menu items) by default\r\nnnoremap \\ :CodeQueryMenu Unite MagicA\r\n```\r\n  \r\n#### Query  \r\n```vim\r\nnnoremap  :CodeQuery Symbol\r\n  \r\n\" Chain commands to find possible tests (for python)\r\nnnoremap t :CodeQuery Caller:CodeQueryFilter test_\r\n```\r\n  \r\n#### Filter  \r\n```vim\r\n\" Filter reversely by adding '!'\r\n:CodeQueryFilter ! [word]\r\n```\r\n  \r\n#### Build  \r\n```vim\r\n\" Trigger db building (in current filetype) when your query fails\r\nlet g:codequery_trigger_build_db_when_db_not_found = 1\r\n```\r\n\r\n#### Find Text \r\n```vim\r\n\" Custom your `CodeQuery Text` commands\r\nlet g:codequery_find_text_cmd = 'Ack!'\r\n  \r\nlet g:codequery_find_text_from_current_file_dir = 0\r\n\" 0 => search from project dir (git root directory -> then the directory containing xxx.db file)\r\n\" 1 => search from the directory containing current file\r\n  \r\n\" If you use ':CodeQuery Symbol' in a txt file, of course, it will fail due to wrong filetype.\r\n\" With the following option set to 1, ':CodeQuery Text' will be automatically sent when your query fails.\r\nlet g:codequery_auto_switch_to_find_text_for_wrong_filetype = 0\r\n```  \r\n  \r\n#### Load Ctags File\r\n```vim\r\n\" Set tags option\r\nset tags=.\/javascript_tags;\/\r\nset tags+=.\/python_tags;\/\r\nset tags+=.\/ruby_tags;\/\r\nset tags+=.\/go_tags;\/\r\nset tags+=.\/java_tags;\/\r\nset tags+=.\/c_tags;\/\r\n```\r\n  \r\n#### Clean Ctags, Cscope ... Files by Languages\r\n```vim\r\nlet g:codequery_enable_auto_clean_languages = ['python']\r\n  \r\n\" It accpepts a list of your languages written in lowercase\r\n```\r\n  \r\n#### Custom Database Building\r\n```vim\r\n\" Make sure to generate a python.db or xxxx.db file as a result\r\nlet g:codequery_build_python_db_cmd = '...'\r\nlet g:codequery_build_javascript_db_cmd = '...'\r\nlet g:codequery_build_ruby_db_cmd = '...'\r\nlet g:codequery_build_go_db_cmd = '...'  \r\nlet g:codequery_build_java_db_cmd = '...'  \r\nlet g:codequery_build_c_db_cmd = '...'  \r\n```\r\n  \r\n  \r\n#### Others\r\n```vim\r\n\" You can disable key binding within quickfix\r\nlet g:codequery_disable_qf_key_bindings = 1\r\n  \r\n\" if your function usually begins with a capital letter ..., you can change your magic menu to a not-so-magic one\r\nlet g:codequery_enable_not_so_magic_menu = 1\r\n```\r\n  \r\n
\r\n  \r\n## FAQ \r\n\r\n#### Why writing this plugin?\r\n\r\n> Because I need it. \r\n>   \r\n> I already shared the story of making this plugin in local Python user groups [Taipei.py](http:\/\/www.meetup.com\/Taipei-py\/) and [Tainan.py](http:\/\/www.meetup.com\/Tainan-py-Python-Tainan-User-Group\/).  \r\n> Slides are available here: [Taipei.py](http:\/\/www.slideshare.net\/excusemejoe\/joe-vim-plugin-taipeipy20160825) \/ [Tainan.py](http:\/\/www.slideshare.net\/excusemejoe\/vim-plugin-20160827) (Language: Traditional Chinese)\r\n  \r\n#### Why not using Ctags or Cscope directly?\r\n  \r\n> Read what @ruben2020 the author of CodeQuery said: [Link](https:\/\/github.com\/ruben2020\/codequery#how-is-it-different-from-cscope-and-ctags-what-are-the-advantages)   \r\n> \r\n> In addittion, vim-codequery provides: \r\n>   \r\n> 1. Good interface.\r\n> 2. Separated Database Management Mechanism.  \r\n> (You can open as many projects as you wish in a single Vim session without worrying about messing up Ctags or Cscope files or getting wrong result!) \r\n>    \r\n> for Vim users.\r\n  \r\n#### More Questions\r\n\r\n> Ask [here](https:\/\/docs.google.com\/document\/d\/1gIvP9wrp1i3xLPDEKNVy76gUeYt1QkIUoqSvJDEbOfM\/edit?usp=sharing) or create an issue. \r\n   \r\n
\r\n   \r\n## How to Contribute\r\n#### Use It\r\n\r\n> And give me [feedback](https:\/\/goo.gl\/forms\/9r8sOS6xTCBjNQEW2) or [bug report](https:\/\/docs.google.com\/spreadsheets\/d\/1eSweAzJKYdzeNdTUVfhujEAOy1RHq1_bEBSX8DQ6xvA\/edit?usp=sharing).\r\n\r\n#### Fork It\r\n\r\n> And give me PR. It would be better if you open an [issue](https:\/\/github.com\/devjoe\/vim-codequery\/issues) and discuss with me before sending PR.\r\n  \r\n#### Star It\r\n\r\n> If you like it. 👍\r\n   \r\n
\r\n   \r\n## Credits\r\n\r\nThank all for working on these great projects!\r\n\r\n* [CodeQuery](https:\/\/github.com\/ruben2020\/codequery)\r\n* [Starscope](https:\/\/github.com\/eapache\/starscope)\r\n* [PyCscope](https:\/\/github.com\/portante\/pycscope)\r\n* [Unite.vim](https:\/\/github.com\/Shougo\/unite.vim)\r\n* [dispatch.vim](https:\/\/github.com\/tpope\/vim-dispatch)\r\n* [ack.vim](https:\/\/github.com\/mileszs\/ack.vim)\r\n* [vim-addon-qf-layout](https:\/\/github.com\/MarcWeber\/vim-addon-qf-layout)\r\n","4":"\r\n\r\n\r\nOfficial Website:https:\/\/github.com\/devjoe\r\n\r\n\r\n\r\n\r\n![](https:\/\/github.com\/ruben2020\/codequery\/raw\/master\/doc\/logotitle.png)\r\n  \r\n  \r\n  \r\n> Choose what you want to know! 😼\r\n     \r\n```vim\r\n\" Open menu\r\n:CodeQueryMenu Unite Full\r\n\r\n\" Or query directly\r\n:CodeQuery Definition get_user_id\r\n```\r\n  
  \r\n  
\r\n\r\n# vim-codequery\r\n  \r\nThis Vim plugin is built on top of the great tool [CodeQuery](https:\/\/github.com\/ruben2020\/codequery) created by ruben2020, and aims at providing three primary functions to help you to:\r\n  \r\n1. **Search source code gracefully within Vim**.\r\n    * You can find: `definition, call, caller, callee, symbol, class, parent, child` and more for a string.\r\n    * Convenient menus are created for you.\r\n    * Well-formated results are shown in a custom Quickfix window with usable key bindings.\r\n    * Support asynchronous search (Vim version >= 8.0)\r\n2. **Manage your database easily**.\r\n    * Load, make and move your database file by custom Vim commands.\r\n    * Support asynchronous build (Vim version >= 8.0 or by `Dispatch` plugin)\r\n    * `Note: CodeQuery's SQLite database is built on top of ctags and cscope.`\r\n3. **Know your code more instantly**.\r\n    * (TBD)\r\n  \r\n
\r\n\r\n##  Supported languages\r\n  * [x] `Python` 😎\r\n  * [x] `Javascript`\r\n  * [x] `Ruby`\r\n  * [x] `Go` \r\n  * [x] `Java`\r\n  * [x] `C, C++`\r\n  \r\n
\r\n  \r\n## Demo\r\n\r\n`Choose a query from menu ➙ Get results`  \r\n\r\n![](https:\/\/db.tt\/rf6fO2eJ)\r\n\r\n`... ➙ Switch to different query ➙ Get results ... ➙ Filter them ➙ Get Results ➙ Undo ➙ Redo`  \r\n\r\n![](https:\/\/db.tt\/KoZORec3)\r\n  \r\n[more demo and screenshots](https:\/\/github.com\/devjoe\/vim-codequery\/wiki\/Screenshots-and-Demo)  \r\n    \r\n```\r\nThese videos are quite old.   \r\nNow vim-codequery works better than what you see by using Vim8's async feature.\r\n```\r\n
\r\n  \r\n## Schedule\r\n\r\n> **This project is almost ready to be released.**   \r\n>  \r\n> Main TODO:\r\n> * ~~Use Vim8's new features to enhance usability.~~\r\n> * ~~Do lazy-loading.~~\r\n> * Enhance usability.\r\n> * Test it.\r\n> * Doc it.\r\n>  \r\n> Completeness: 94%  \r\n> Current Version: v0.9  \r\n>  \r\n> Welcome to try it! 👌  \r\n  \r\n
\r\n  \r\n## Installation\r\n\r\n#### 1. Make sure these commands are in your system\r\n
\r\n\/bin\/sh echo mkdir mv cut find awk stat git(optional)\r\n<\/pre>\r\n\r\n#### 2. Install CodeQuery\r\n* Linux => Install [binaries](https:\/\/sourceforge.net\/projects\/codequery\/files\/) or [build it](https:\/\/github.com\/ruben2020\/codequery\/blob\/master\/doc\/INSTALL-LINUX.md).\r\n* Mac => `brew install codequery` 🍺 (make sure codequery version >= v0.17.0)\r\n\r\n#### 3. Install additional ctags\/cscope tools for your languages\r\n| Language | Tools | How to install |\r\n| --- | --- | --- |  \r\n| Python | [PyCscope](https:\/\/github.com\/portante\/pycscope) | `sudo pip install pycscope` | \r\n| Javascript | [Starscope](https:\/\/github.com\/eapache\/starscope) | `sudo gem install starscope` |\r\n| Ruby | [Starscope](https:\/\/github.com\/eapache\/starscope) | `sudo gem install starscope` |\r\n| Go | [Starscope](https:\/\/github.com\/eapache\/starscope) | `sudo gem install starscope` |\r\n\r\n> `Java`, `C` and `C++` users do not need to install additional ctags\/cscope tools.  \r\n> Starscope has been [packaged for Arch Linux](https:\/\/aur.archlinux.org\/packages\/ruby-starscope\/)    \r\n\r\n#### 4. Install Vim plugins\r\n* Use your favorite plugins manager: [pathogen](https:\/\/github.com\/tpope\/vim-pathogen), [Vundle](https:\/\/github.com\/VundleVim\/Vundle.vim), [Plug](https:\/\/github.com\/junegunn\/vim-plug), [NeoBundle](https:\/\/github.com\/Shougo\/neobundle.vim), [Dein](https:\/\/github.com\/Shougo\/dein.vim),  ...\r\n* Take Plug as an example:  \r\n```vim\r\n\" Required\r\nPlug 'Shougo\/unite.vim'\r\nPlug 'devjoe\/vim-codequery'\r\n  \r\n\" Optional\r\n\" if your vim version < 8.0\r\nPlug 'tpope\/vim-dispatch'\r\n\" if you don't have an :Ack (or :Ag) liked command\r\nPlug 'mileszs\/ack.vim'\r\n```\r\n  \r\n
\r\n  \r\n## Usage\r\n\r\n#### 1. Setup\r\n\r\n* Go to the (git) root directory of your project. Open vim and type:\r\n```vim\r\n\" Index Python files\r\n:CodeQueryMakeDB python\r\n  \r\n\" Or index Python + Javascript files\r\n:CodeQueryMakeDB python javascript \r\n```\r\n* That's all. `python.db`, `javascript.db` ... will be created in the root directory. \r\n* It's recommended that you should use `:CodeQueryMoveDBToGitDir python` to hide the DB file to `.git\/codequery\/` directory. If you do so, next time you can call `:CodeQueryMakeDB` directly in any opened Python buffer to rebuild the DB file.\r\n\r\n\r\n#### 2. Search\r\n* **Find symbol under your cursor**  \r\n\r\n```vim  \r\n:CodeQuery\r\n```  \r\n\r\n* **Find word (by subcommands) under your cursor**  \r\n\r\n```vim  \r\n:CodeQuery [SubCommand]  \r\n  \r\n\" Supported SubCommands are: `Symbol, Text, Call, Caller, Callee, Class, Parent, Child, Member, FunctionList, FileImporter`.  \r\n```  \r\n\r\n* **Find arbitrary word**\r\n\r\n```vim\r\n:CodeQuery [SubCommand] [word]  \r\n```\r\n  \r\n* **Find again with the same word**\r\n\r\n```vim\r\n:CodeQueryAgain [SubCommand]  \r\n```\r\n\r\n* **Use fuzzy Option**    \r\n\r\n```vim\r\n:CodeQuery [SubCommand] [word] -f  \r\n  \r\n\" [word] can be: get_* or *user_info or find_*_by_id\r\n```\r\n\r\n* **Use append Option** (results will be added to the current Quickfix)    \r\n\r\n```vim\r\n:CodeQuery [SubCommand] [word] -a  \r\n```\r\n\r\n* **Filter Search Results**  \r\n\r\n```vim\r\n:CodeQueryFilter [string]  \r\n  \r\n\" [string] can be a regex\r\n```\r\n    \r\n#### 3. Use Quickfix\r\n* **Move your cursor inside Quickfix window to use these key bindings**\r\n\r\n| Key | Action | Note | \r\n| --- | --- | --- | \r\n| s | `:CodeQueryAgain Symbol` | |\r\n| x | `:CodeQueryAgain Text` | use `:Ack!` by default. #1 | \r\n| c | `:CodeQueryAgain Call` | |\r\n| r | `:CodeQueryAgain Caller` | |\r\n| e | `:CodeQueryAgain Callee` | |\r\n| d | `:CodeQueryAgain Definition` | |\r\n| C | `:CodeQueryAgain Class` | |\r\n| M | `:CodeQueryAgain Member` | |\r\n| P | `:CodeQueryAgain Parent` | |\r\n| D | `:CodeQueryAgain Child` | |\r\n| m | `:CodeQueryMenu Unite Magic` | |\r\n| q | `:cclose` | |\r\n| \\ | `:CodeQueryFilter` | |\r\n| p | `p` | Preview |\r\n| u | `:colder \\| CodeQueryShowQF` | Older Quickfix Result | \r\n| \\ | `:cnewer \\| CodeQueryShowQF` | Newer Quickfix Result | \r\n  \r\n>  #1 \r\n> You can override `g:codequery_find_text_cmd` to change it.\r\n\r\n* **Show Quickfix with above key bindings**\r\n\r\n```vim\r\n:CodeQueryShowQF  \r\n  \r\n\" This command can also be used to **patch** standard Quickfix.\r\n```\r\n\r\n#### 4. Open Menu\r\n\r\nCurrently, vim-codequery only provides [Unite](https:\/\/github.com\/Shougo\/unite.vim) menu because I love it ⭐.  There are two types of menu:\r\n\r\n* **Full Unite menu**\r\n\r\n```vim\r\n:CodeQueryMenu Unite Full  \r\n  \r\n\" The string between :: and :: is the word under cursor\r\n\" [F] means this action is for 'function variable only'\r\n\" [C] is for 'class variable only'  \r\n```\r\n   \r\n    \r\n* **Magic Unite menu**\r\n\r\n```vim\r\n:CodeQueryMenu Unite Magic  \r\n  \r\n\" This menu changes dynamically:\r\n\" 1. If the word under your cursor begins with a capital letter (possible be class): show [C] actions\r\n\" 2. vice versa (possible be function): show [F] actions\r\n\" 3. Show reasonable actions within Quickfix\r\n```\r\n   \r\n  \r\n
\r\n  \r\n## Tips\r\n#### Open Menu  \r\n```vim\r\nnnoremap c :CodeQueryMenu Unite Full\r\nnnoremap ; :CodeQueryMenu Unite Magic\r\n  \r\n\" Or enable typing (to search menu items) by default\r\nnnoremap \\ :CodeQueryMenu Unite MagicA\r\n```\r\n  \r\n#### Query  \r\n```vim\r\nnnoremap  :CodeQuery Symbol\r\n  \r\n\" Chain commands to find possible tests (for python)\r\nnnoremap t :CodeQuery Caller:CodeQueryFilter test_\r\n```\r\n  \r\n#### Filter  \r\n```vim\r\n\" Filter reversely by adding '!'\r\n:CodeQueryFilter ! [word]\r\n```\r\n  \r\n#### Build  \r\n```vim\r\n\" Trigger db building (in current filetype) when your query fails\r\nlet g:codequery_trigger_build_db_when_db_not_found = 1\r\n```\r\n\r\n#### Find Text \r\n```vim\r\n\" Custom your `CodeQuery Text` commands\r\nlet g:codequery_find_text_cmd = 'Ack!'\r\n  \r\nlet g:codequery_find_text_from_current_file_dir = 0\r\n\" 0 => search from project dir (git root directory -> then the directory containing xxx.db file)\r\n\" 1 => search from the directory containing current file\r\n  \r\n\" If you use ':CodeQuery Symbol' in a txt file, of course, it will fail due to wrong filetype.\r\n\" With the following option set to 1, ':CodeQuery Text' will be automatically sent when your query fails.\r\nlet g:codequery_auto_switch_to_find_text_for_wrong_filetype = 0\r\n```  \r\n  \r\n#### Load Ctags File\r\n```vim\r\n\" Set tags option\r\nset tags=.\/javascript_tags;\/\r\nset tags+=.\/python_tags;\/\r\nset tags+=.\/ruby_tags;\/\r\nset tags+=.\/go_tags;\/\r\nset tags+=.\/java_tags;\/\r\nset tags+=.\/c_tags;\/\r\n```\r\n  \r\n#### Clean Ctags, Cscope ... Files by Languages\r\n```vim\r\nlet g:codequery_enable_auto_clean_languages = ['python']\r\n  \r\n\" It accpepts a list of your languages written in lowercase\r\n```\r\n  \r\n#### Custom Database Building\r\n```vim\r\n\" Make sure to generate a python.db or xxxx.db file as a result\r\nlet g:codequery_build_python_db_cmd = '...'\r\nlet g:codequery_build_javascript_db_cmd = '...'\r\nlet g:codequery_build_ruby_db_cmd = '...'\r\nlet g:codequery_build_go_db_cmd = '...'  \r\nlet g:codequery_build_java_db_cmd = '...'  \r\nlet g:codequery_build_c_db_cmd = '...'  \r\n```\r\n  \r\n  \r\n#### Others\r\n```vim\r\n\" You can disable key binding within quickfix\r\nlet g:codequery_disable_qf_key_bindings = 1\r\n  \r\n\" if your function usually begins with a capital letter ..., you can change your magic menu to a not-so-magic one\r\nlet g:codequery_enable_not_so_magic_menu = 1\r\n```\r\n  \r\n
\r\n  \r\n## FAQ \r\n\r\n#### Why writing this plugin?\r\n\r\n> Because I need it. \r\n>   \r\n> I already shared the story of making this plugin in local Python user groups [Taipei.py](http:\/\/www.meetup.com\/Taipei-py\/) and [Tainan.py](http:\/\/www.meetup.com\/Tainan-py-Python-Tainan-User-Group\/).  \r\n> Slides are available here: [Taipei.py](http:\/\/www.slideshare.net\/excusemejoe\/joe-vim-plugin-taipeipy20160825) \/ [Tainan.py](http:\/\/www.slideshare.net\/excusemejoe\/vim-plugin-20160827) (Language: Traditional Chinese)\r\n  \r\n#### Why not using Ctags or Cscope directly?\r\n  \r\n> Read what @ruben2020 the author of CodeQuery said: [Link](https:\/\/github.com\/ruben2020\/codequery#how-is-it-different-from-cscope-and-ctags-what-are-the-advantages)   \r\n> \r\n> In addittion, vim-codequery provides: \r\n>   \r\n> 1. Good interface.\r\n> 2. Separated Database Management Mechanism.  \r\n> (You can open as many projects as you wish in a single Vim session without worrying about messing up Ctags or Cscope files or getting wrong result!) \r\n>    \r\n> for Vim users.\r\n  \r\n#### More Questions\r\n\r\n> Ask [here](https:\/\/docs.google.com\/document\/d\/1gIvP9wrp1i3xLPDEKNVy76gUeYt1QkIUoqSvJDEbOfM\/edit?usp=sharing) or create an issue. \r\n   \r\n
\r\n   \r\n## How to Contribute\r\n#### Use It\r\n\r\n> And give me [feedback](https:\/\/goo.gl\/forms\/9r8sOS6xTCBjNQEW2) or [bug report](https:\/\/docs.google.com\/spreadsheets\/d\/1eSweAzJKYdzeNdTUVfhujEAOy1RHq1_bEBSX8DQ6xvA\/edit?usp=sharing).\r\n\r\n#### Fork It\r\n\r\n> And give me PR. It would be better if you open an [issue](https:\/\/github.com\/devjoe\/vim-codequery\/issues) and discuss with me before sending PR.\r\n  \r\n#### Star It\r\n\r\n> If you like it. 👍\r\n   \r\n
\r\n   \r\n## Credits\r\n\r\nThank all for working on these great projects!\r\n\r\n* [CodeQuery](https:\/\/github.com\/ruben2020\/codequery)\r\n* [Starscope](https:\/\/github.com\/eapache\/starscope)\r\n* [PyCscope](https:\/\/github.com\/portante\/pycscope)\r\n* [Unite.vim](https:\/\/github.com\/Shougo\/unite.vim)\r\n* [dispatch.vim](https:\/\/github.com\/tpope\/vim-dispatch)\r\n* [ack.vim](https:\/\/github.com\/mileszs\/ack.vim)\r\n* [vim-addon-qf-layout](https:\/\/github.com\/MarcWeber\/vim-addon-qf-layout)\r\n","install_details":"","5":"","first_name":"Chun-Yu","6":"Chun-Yu","last_name":"Tseng","7":"Tseng","releases":[{"0":"5477","vim_version":"7.4","1":"7.4","script_version":"0.9.1","2":"0.9.1","version_comment":"Initial upload","3":"Initial upload","package":"vim-codequery-0.9.1.tar.gz","4":"vim-codequery-0.9.1.tar.gz","src_id":"24696","5":"24696","creation_date":"1478026354","6":"1478026354"}]},"5476":{"script_id":"5476","0":"5476","script_name":"xdg_open.vim","1":"xdg_open.vim","script_type":"utility","2":"utility","summary":"Run xdg-open from Vim; re-implements netrw's gx.","3":"Run xdg-open from Vim; re-implements netrw's gx.","description":"Homepage: https:\/\/arp242.net\/code\/xdg_open.vim\/\r\n\r\n---------------------\r\n\r\nRe-implements netrw's `gx` command with a call to `xdg-open` (or a similar\r\ntool of your choosing).\r\n\r\nThis is especially useful if you're using dirvish or some other file-manager\r\nother than netrw.\r\n\r\nIs this fully compatible with netrw?\r\n------------------------------------\r\n\r\nIt should be for most purposes, but feature-for-feature (or bug-for-bug)\r\ncompatibility was not a primary goal. Notable changes are:\r\n\r\n- We just try to run `xdg-open`. No tricks and complicated fallbacks if that\r\n  fails.\r\n\r\n- The default is to get the `` instead of ``. This works better\r\n  with urls which have query parameters.\r\n\r\n- The shell command is run in the background. This is much more sane.\r\n\r\nCan I disable netrw completely?\r\n-------------------------------\r\n\r\n- To only disable gx-related functionality:\r\n\r\n\t\tlet g:netrw_nogx = 1\r\n\r\n- To disable all of netrw:\r\n\r\n\t\tlet g:loaded_netrw = 1\r\n\r\n- To disable the netrw doc files you need to remove the doc file at \r\n  `$VIMRUNTIME\/doc\/pi_netrw.txt` and rebuild the help tags with:\r\n\r\n\t\t:helptags $VIMRUNTIME\/doc\r\n\r\n  This has the advantage of not cluttering `:helpgrep` or tab completion.\r\n\r\n  You will need write permissions here (e.g. run it as root). Unfortunately\r\n  you will nee to re-run this after every upgrade.\r\n\r\nSee `:help xdg_open` for the full documentation.\r\n","4":"Homepage: https:\/\/arp242.net\/code\/xdg_open.vim\/\r\n\r\n---------------------\r\n\r\nRe-implements netrw's `gx` command with a call to `xdg-open` (or a similar\r\ntool of your choosing).\r\n\r\nThis is especially useful if you're using dirvish or some other file-manager\r\nother than netrw.\r\n\r\nIs this fully compatible with netrw?\r\n------------------------------------\r\n\r\nIt should be for most purposes, but feature-for-feature (or bug-for-bug)\r\ncompatibility was not a primary goal. Notable changes are:\r\n\r\n- We just try to run `xdg-open`. No tricks and complicated fallbacks if that\r\n  fails.\r\n\r\n- The default is to get the `` instead of ``. This works better\r\n  with urls which have query parameters.\r\n\r\n- The shell command is run in the background. This is much more sane.\r\n\r\nCan I disable netrw completely?\r\n-------------------------------\r\n\r\n- To only disable gx-related functionality:\r\n\r\n\t\tlet g:netrw_nogx = 1\r\n\r\n- To disable all of netrw:\r\n\r\n\t\tlet g:loaded_netrw = 1\r\n\r\n- To disable the netrw doc files you need to remove the doc file at \r\n  `$VIMRUNTIME\/doc\/pi_netrw.txt` and rebuild the help tags with:\r\n\r\n\t\t:helptags $VIMRUNTIME\/doc\r\n\r\n  This has the advantage of not cluttering `:helpgrep` or tab completion.\r\n\r\n  You will need write permissions here (e.g. run it as root). Unfortunately\r\n  you will nee to re-run this after every upgrade.\r\n\r\nSee `:help xdg_open` for the full documentation.\r\n","install_details":"","5":"","first_name":"Martin","6":"Martin","last_name":"Tournoij","7":"Tournoij","releases":[{"0":"5476","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"download-from-homepage.tar.gz","4":"download-from-homepage.tar.gz","src_id":"24690","5":"24690","creation_date":"1477889575","6":"1477889575"}]},"5475":{"script_id":"5475","0":"5475","script_name":"Install a Plugin in Vim","1":"Install a Plugin in Vim","script_type":"ftplugin","2":"ftplugin","summary":"symlinks don\\\\\\'t overwrite existing files, uninstall only deletes symlinks","3":"symlinks don\\\\\\'t overwrite existing files, uninstall only deletes symlinks","description":"# Easily install vim plugins from a source control checkout (e.g. Github)\r\n#\r\n# alias vim-install=rake -f ~\/.vim\/rakefile-vim-install\r\n# vim-install\r\n# vim-install uninstall\r\n# will be Trying for http:\/\/questionstoaskagirlguy.com\/\r\nrequire \\\\\\\\\\\\\\'ftools\\\\\\\\\\\\\\'\r\nrequire \\\\\\\\\\\\\\'fileutils\\\\\\\\\\\\\\'\r\n\r\ntask :default => :install\r\ndesc \\\\\\\\\\\\\\\"Install a vim plugin the lazy way\\\\\\\\\\\\\\\"\r\ntask :install do\r\n  vim_dir      = File.expand_path(\\\\\\\\\\\\\\\"~\/.vim\\\\\\\\\\\\\\\")\r\n  plugin_dir   = Dir.pwd\r\n\r\n  if not (FileTest.exists? File.join(plugin_dir,\\\\\\\\\\\\\\\".git\\\\\\\\\\\\\\\") or\r\n          FileTest.exists? File.join(plugin_dir,\\\\\\\\\\\\\\\".svn\\\\\\\\\\\\\\\") or\r\n          FileTest.exists? File.join(plugin_dir,\\\\\\\\\\\\\\\".hg\\\\\\\\\\\\\\\"))\r\n      puts \\\\\\\\\\\\\\\"#{plugin_dir} isn\\\\\\\\\\\\\\'t a source controlled directory. Aborting.\\\\\\\\\\\\\\\"\r\n      exit 1\r\n  end\r\n\r\n  Dir[\\\\\\\\\\\\\\'**\/\\\\\\\\\\\\\\'].each do |d|\r\n    FileUtils.mkdir_p File.join(vim_dir, d)\r\n  end\r\n\r\n  Dir[\\\\\\\\\\\\\\\"**\/*.{txt,snippet,snippets,vim,js,wsf}\\\\\\\\\\\\\\\"].each do |f|\r\n    ln File.join(plugin_dir, f), File.join(vim_dir,f)\r\n  end\r\n\r\n  boldred = \\\\\\\\\\\\\\\"\\\\\\\\\\\\\\\\033[1;31m\\\\\\\\\\\\\\\"\r\n  clear = \\\\\\\\\\\\\\\"\\\\\\\\\\\\\\\\033[0m\\\\\\\\\\\\\\\"\r\n  puts \\\\\\\\\\\\\\\"\\\\\\\\\\\\\\\\nDone. Remember to #{boldred}:helptags ~\/.vim\/doc#{clear}\\\\\\\\\\\\\\\"\r\nend\r\n\r\ntask :uninstall do\r\n  vim_dir      = File.expand_path(\\\\\\\\\\\\\\\"~\/.vim\\\\\\\\\\\\\\\")\r\n  plugin_dir   = Dir.pwd\r\n  Dir[\\\\\\\\\\\\\\\"**\/*.{txt,snippet,snippets,vim}\\\\\\\\\\\\\\\"].each do |f|\r\n    safe_rm File.join(vim_dir, f)\r\n  end\r\nend\r\n\r\ndef nicename(path)\r\n    boldgreen = \\\\\\\\\\\\\\\"\\\\\\\\\\\\\\\\033[1;32m\\\\\\\\\\\\\\\"\r\n    clear = \\\\\\\\\\\\\\\"\\\\\\\\\\\\\\\\033[0m\\\\\\\\\\\\\\\"\r\n    return \\\\\\\\\\\\\\\"#{boldgreen}#{File.join(path.split(\\\\\\\\\\\\\\'\/\\\\\\\\\\\\\\')[-2..-1])}#{clear}\\\\\\\\\\\\\\\\t\\\\\\\\\\\\\\\"\r\nend\r\n\r\ndef ln(src, dst)\r\n    begin\r\n        FileUtils.ln_s src, dst\r\n        puts \\\\\\\\\\\\\\\"    Symlink #{nicename src}\\\\\\\\\\\\\\\\t => #{nicename dst}\\\\\\\\\\\\\\\"\r\n    rescue Errno::EEXIST\r\n        puts \\\\\\\\\\\\\\\"  #{nicename dst} exists! Skipping.\\\\\\\\\\\\\\\"\r\n    end\r\nend\r\n\r\ndef cp(src, dst)\r\n  puts \\\\\\\\\\\\\\\"    Copying #{nicename src}\\\\\\\\\\\\\\\\t=> #{nicename dst}\\\\\\\\\\\\\\\"\r\n  FileUtils.cp src, dst\r\nend\r\n\r\ndef safe_rm(target)\r\n    if FileTest.exists? target and FileTest.symlink? target\r\n        puts \\\\\\\\\\\\\\\"    #{nicename target} removed.\\\\\\\\\\\\\\\"\r\n        File.delete target\r\n    else\r\n        puts \\\\\\\\\\\\\\\"  #{nicename target} is not a symlink. Skipping\\\\\\\\\\\\\\\"\r\n    end\r\nend","4":"# Easily install vim plugins from a source control checkout (e.g. Github)\r\n#\r\n# alias vim-install=rake -f ~\/.vim\/rakefile-vim-install\r\n# vim-install\r\n# vim-install uninstall\r\n# will be Trying for http:\/\/questionstoaskagirlguy.com\/\r\nrequire \\\\\\\\\\\\\\'ftools\\\\\\\\\\\\\\'\r\nrequire \\\\\\\\\\\\\\'fileutils\\\\\\\\\\\\\\'\r\n\r\ntask :default => :install\r\ndesc \\\\\\\\\\\\\\\"Install a vim plugin the lazy way\\\\\\\\\\\\\\\"\r\ntask :install do\r\n  vim_dir      = File.expand_path(\\\\\\\\\\\\\\\"~\/.vim\\\\\\\\\\\\\\\")\r\n  plugin_dir   = Dir.pwd\r\n\r\n  if not (FileTest.exists? File.join(plugin_dir,\\\\\\\\\\\\\\\".git\\\\\\\\\\\\\\\") or\r\n          FileTest.exists? File.join(plugin_dir,\\\\\\\\\\\\\\\".svn\\\\\\\\\\\\\\\") or\r\n          FileTest.exists? File.join(plugin_dir,\\\\\\\\\\\\\\\".hg\\\\\\\\\\\\\\\"))\r\n      puts \\\\\\\\\\\\\\\"#{plugin_dir} isn\\\\\\\\\\\\\\'t a source controlled directory. Aborting.\\\\\\\\\\\\\\\"\r\n      exit 1\r\n  end\r\n\r\n  Dir[\\\\\\\\\\\\\\'**\/\\\\\\\\\\\\\\'].each do |d|\r\n    FileUtils.mkdir_p File.join(vim_dir, d)\r\n  end\r\n\r\n  Dir[\\\\\\\\\\\\\\\"**\/*.{txt,snippet,snippets,vim,js,wsf}\\\\\\\\\\\\\\\"].each do |f|\r\n    ln File.join(plugin_dir, f), File.join(vim_dir,f)\r\n  end\r\n\r\n  boldred = \\\\\\\\\\\\\\\"\\\\\\\\\\\\\\\\033[1;31m\\\\\\\\\\\\\\\"\r\n  clear = \\\\\\\\\\\\\\\"\\\\\\\\\\\\\\\\033[0m\\\\\\\\\\\\\\\"\r\n  puts \\\\\\\\\\\\\\\"\\\\\\\\\\\\\\\\nDone. Remember to #{boldred}:helptags ~\/.vim\/doc#{clear}\\\\\\\\\\\\\\\"\r\nend\r\n\r\ntask :uninstall do\r\n  vim_dir      = File.expand_path(\\\\\\\\\\\\\\\"~\/.vim\\\\\\\\\\\\\\\")\r\n  plugin_dir   = Dir.pwd\r\n  Dir[\\\\\\\\\\\\\\\"**\/*.{txt,snippet,snippets,vim}\\\\\\\\\\\\\\\"].each do |f|\r\n    safe_rm File.join(vim_dir, f)\r\n  end\r\nend\r\n\r\ndef nicename(path)\r\n    boldgreen = \\\\\\\\\\\\\\\"\\\\\\\\\\\\\\\\033[1;32m\\\\\\\\\\\\\\\"\r\n    clear = \\\\\\\\\\\\\\\"\\\\\\\\\\\\\\\\033[0m\\\\\\\\\\\\\\\"\r\n    return \\\\\\\\\\\\\\\"#{boldgreen}#{File.join(path.split(\\\\\\\\\\\\\\'\/\\\\\\\\\\\\\\')[-2..-1])}#{clear}\\\\\\\\\\\\\\\\t\\\\\\\\\\\\\\\"\r\nend\r\n\r\ndef ln(src, dst)\r\n    begin\r\n        FileUtils.ln_s src, dst\r\n        puts \\\\\\\\\\\\\\\"    Symlink #{nicename src}\\\\\\\\\\\\\\\\t => #{nicename dst}\\\\\\\\\\\\\\\"\r\n    rescue Errno::EEXIST\r\n        puts \\\\\\\\\\\\\\\"  #{nicename dst} exists! Skipping.\\\\\\\\\\\\\\\"\r\n    end\r\nend\r\n\r\ndef cp(src, dst)\r\n  puts \\\\\\\\\\\\\\\"    Copying #{nicename src}\\\\\\\\\\\\\\\\t=> #{nicename dst}\\\\\\\\\\\\\\\"\r\n  FileUtils.cp src, dst\r\nend\r\n\r\ndef safe_rm(target)\r\n    if FileTest.exists? target and FileTest.symlink? target\r\n        puts \\\\\\\\\\\\\\\"    #{nicename target} removed.\\\\\\\\\\\\\\\"\r\n        File.delete target\r\n    else\r\n        puts \\\\\\\\\\\\\\\"  #{nicename target} is not a symlink. Skipping\\\\\\\\\\\\\\\"\r\n    end\r\nend","install_details":"I think you should have a look at the Pathogen plugin. After you have this installed, you can keep all of your plugins in separate folders in ~\/.vim\/bundle\/, and Pathogen will take care of loading them.","5":"I think you should have a look at the Pathogen plugin. After you have this installed, you can keep all of your plugins in separate folders in ~\/.vim\/bundle\/, and Pathogen will take care of loading them.","first_name":"Questions","6":"Questions","last_name":"toask","7":"toask","releases":[{"0":"5475","vim_version":"7.0","1":"7.0","script_version":"cp","2":"cp","version_comment":"Initial upload","3":"Initial upload","package":"Vim Script.png","4":"Vim Script.png","src_id":"24684","5":"24684","creation_date":"1477799690","6":"1477799690"}]},"5474":{"script_id":"5474","0":"5474","script_name":"auto_mkdir2.vim","1":"auto_mkdir2.vim","script_type":"utility","2":"utility","summary":"Automatically create directories","3":"Automatically create directories","description":"Homepage: https:\/\/arp242.net\/code\/auto_mkdir2.vim\/\r\n\r\n-----------------------------------\r\n\r\nIntroduction\r\n============\r\nAutomatically create direcories that don't exist yet when writing a file.\r\n\r\nThis allows you to do:\r\n\r\n    vim ~\/a\/dir\/tree\/that\/doesnt\/exist\/new-file.txt\r\n\r\nand then just use `:w` (or `ZZ`, or `:up`, etc.) to create the directory tree.\r\n\r\nThis is basically the same as the \"auto_mkdir\" plugin, although it was\r\ndeveloped independently. This version has the option to confirm directory\r\ncreation and includes a bugfix:\r\nhttp:\/\/www.vim.org\/scripts\/script.php?script_id=3352\r\n\r\nOptions\r\n=======\r\n`g:auto_mkdir2_confirm`                 (Boolean, default: 1)\r\nAsk for confirmation before automatically creating a directory.\r\n\r\nCommands\r\n========\r\nMkdirP [directory]                                                   `:MkdirP`\r\n\r\nLike `mkdir -p` from the shell: it will create all intermediate directories\r\nand will not show an error if the [directory] already exists and is a\r\ndirectory.\r\n\r\nThe [directory] is `expand()`-ed. The parameter is optional and [%:h:p] is used\r\nif it is empty.\r\n","4":"Homepage: https:\/\/arp242.net\/code\/auto_mkdir2.vim\/\r\n\r\n-----------------------------------\r\n\r\nIntroduction\r\n============\r\nAutomatically create direcories that don't exist yet when writing a file.\r\n\r\nThis allows you to do:\r\n\r\n    vim ~\/a\/dir\/tree\/that\/doesnt\/exist\/new-file.txt\r\n\r\nand then just use `:w` (or `ZZ`, or `:up`, etc.) to create the directory tree.\r\n\r\nThis is basically the same as the \"auto_mkdir\" plugin, although it was\r\ndeveloped independently. This version has the option to confirm directory\r\ncreation and includes a bugfix:\r\nhttp:\/\/www.vim.org\/scripts\/script.php?script_id=3352\r\n\r\nOptions\r\n=======\r\n`g:auto_mkdir2_confirm`                 (Boolean, default: 1)\r\nAsk for confirmation before automatically creating a directory.\r\n\r\nCommands\r\n========\r\nMkdirP [directory]                                                   `:MkdirP`\r\n\r\nLike `mkdir -p` from the shell: it will create all intermediate directories\r\nand will not show an error if the [directory] already exists and is a\r\ndirectory.\r\n\r\nThe [directory] is `expand()`-ed. The parameter is optional and [%:h:p] is used\r\nif it is empty.\r\n","install_details":"","5":"","first_name":"Martin","6":"Martin","last_name":"Tournoij","7":"Tournoij","releases":[{"0":"5474","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Download from homepage","3":"Download from homepage","package":"download-from-homepage.tar.gz","4":"download-from-homepage.tar.gz","src_id":"24685","5":"24685","creation_date":"1477882613","6":"1477882613"}]},"5473":{"script_id":"5473","0":"5473","script_name":"nordisk","1":"nordisk","script_type":"color scheme","2":"color scheme","summary":"A calm, fairly low contrast, dark color scheme","3":"A calm, fairly low contrast, dark color scheme","description":"A dark, arctically bluish colour scheme for Vim and Lightline closely modelled on Arctic Ice Studio\u00e2\u0080\u0099s Nord palette.\r\n\r\nfairly low contrast | unobtrusive | calm\r\n\r\nScreenshots:\r\nhttps:\/\/raw.githubusercontent.com\/kamwitsta\/nordisk\/master\/img\/vim-1.png\r\nhttps:\/\/raw.githubusercontent.com\/kamwitsta\/nordisk\/master\/img\/vim-2.png\r\n\r\nSee the GitHub page (https:\/\/github.com\/kamwitsta\/nordisk) for an airline and lightline theme, together with .Xdefaults, .gitconfig, and a Gnome Terminal theme.","4":"A dark, arctically bluish colour scheme for Vim and Lightline closely modelled on Arctic Ice Studio\u00e2\u0080\u0099s Nord palette.\r\n\r\nfairly low contrast | unobtrusive | calm\r\n\r\nScreenshots:\r\nhttps:\/\/raw.githubusercontent.com\/kamwitsta\/nordisk\/master\/img\/vim-1.png\r\nhttps:\/\/raw.githubusercontent.com\/kamwitsta\/nordisk\/master\/img\/vim-2.png\r\n\r\nSee the GitHub page (https:\/\/github.com\/kamwitsta\/nordisk) for an airline and lightline theme, together with .Xdefaults, .gitconfig, and a Gnome Terminal theme.","install_details":"Copy to ~\/.vim\/colors\r\nor \r\nuse this address: https:\/\/github.com\/kamwitsta\/nordisk.","5":"Copy to ~\/.vim\/colors\r\nor \r\nuse this address: https:\/\/github.com\/kamwitsta\/nordisk.","first_name":"kamil","6":"kamil","last_name":"stachowski","7":"stachowski","releases":[{"0":"5473","vim_version":"7.0","1":"7.0","script_version":"0.4","2":"0.4","version_comment":"## 0.4 (2016.11.11)\r\n- made into a separate project\r\n- several minor adjustments to the palette\r\n- added Vim airline","3":"## 0.4 (2016.11.11)\r\n- made into a separate project\r\n- several minor adjustments to the palette\r\n- added Vim airline","package":"nordisk.vim","4":"nordisk.vim","src_id":"24724","5":"24724","creation_date":"1478900454","6":"1478900454"},{"0":"5473","vim_version":"7.0","1":"7.0","script_version":"0.3","2":"0.3","version_comment":"changed DiffChange from col14 to col13\r\nadded some language-specific links","3":"changed DiffChange from col14 to col13\r\nadded some language-specific links","package":"nordisk.vim","4":"nordisk.vim","src_id":"24692","5":"24692","creation_date":"1478002587","6":"1478002587"},{"0":"5473","vim_version":"7.0","1":"7.0","script_version":"0.2","2":"0.2","version_comment":"Initial upload","3":"Initial upload","package":"nordisk.vim","4":"nordisk.vim","src_id":"24679","5":"24679","creation_date":"1477770128","6":"1477770128"}]},"5472":{"script_id":"5472","0":"5472","script_name":"pace.vim","1":"pace.vim","script_type":"utility","2":"utility","summary":"Measure the pace of typing (in Insert mode &c.)","3":"Measure the pace of typing (in Insert mode &c.)","description":"The \"pace.vim\" script offers a means to measure the pace of\r\ntyping (in Insert, Replace, & Virtual Replace modes) in\r\na preselected manner: cumulative, buffer-total, or instance\r\n(dumpable on demand).  It provides a tunable policy tool to\r\ninhibit any mode tracing and to control borderline cases\r\n(Ctrl-c exiting, no input).  All data collected in a session\r\nmay be carried over and re-used.\r\n\r\nThe bundled \"demo.vim\" script parades a specialised variant\r\nof \"pace.vim\" in mock-action with a touch of rhyming.\r\n","4":"The \"pace.vim\" script offers a means to measure the pace of\r\ntyping (in Insert, Replace, & Virtual Replace modes) in\r\na preselected manner: cumulative, buffer-total, or instance\r\n(dumpable on demand).  It provides a tunable policy tool to\r\ninhibit any mode tracing and to control borderline cases\r\n(Ctrl-c exiting, no input).  All data collected in a session\r\nmay be carried over and re-used.\r\n\r\nThe bundled \"demo.vim\" script parades a specialised variant\r\nof \"pace.vim\" in mock-action with a touch of rhyming.\r\n","install_details":"In order to install the project files into a writable user's\r\nVim directory, fetch the most recent zipped archive listed\r\nbelow and extract its files.  (There is also a public Git\r\nrepository at https:\/\/github.com\/zzzyxwvut\/pace-vim.)\r\n\r\nSince Vim 8, consider assembling a Vim package for this\r\nextracting:\r\n:help packages\r\n\r\nHaving the files installed, launch Vim and list all \"doc\/\"\r\nlocations:\r\n:echo finddir('doc', &runtimepath, -1)\r\n\r\nNow generate the help tags:\r\n:helptags \/path\/to\/doc\r\n\r\nThen read the documentation:\r\n:help pace.txt\r\n","5":"In order to install the project files into a writable user's\r\nVim directory, fetch the most recent zipped archive listed\r\nbelow and extract its files.  (There is also a public Git\r\nrepository at https:\/\/github.com\/zzzyxwvut\/pace-vim.)\r\n\r\nSince Vim 8, consider assembling a Vim package for this\r\nextracting:\r\n:help packages\r\n\r\nHaving the files installed, launch Vim and list all \"doc\/\"\r\nlocations:\r\n:echo finddir('doc', &runtimepath, -1)\r\n\r\nNow generate the help tags:\r\n:helptags \/path\/to\/doc\r\n\r\nThen read the documentation:\r\n:help pace.txt\r\n","first_name":"Aliaksei","6":"Aliaksei","last_name":"Budavei","7":"Budavei","releases":[{"0":"5472","vim_version":"9.0","1":"9.0","script_version":"2.0","2":"2.0","version_comment":"demo.vim and pace.vim:\r\nThe files have been overhauled to Vim9\r\nscript.\r\n\r\nThe comparison of generated profiling data\r\nfor major script versions shows noticeable\r\nreduction in execution time for functions\r\nwritten in Vim9 syntax, and the improvement\r\nof measuring accuracy seems promising in\r\nconsequence of this observation.\r\n\r\nTO BRAM.\r\n","3":"demo.vim and pace.vim:\r\nThe files have been overhauled to Vim9\r\nscript.\r\n\r\nThe comparison of generated profiling data\r\nfor major script versions shows noticeable\r\nreduction in execution time for functions\r\nwritten in Vim9 syntax, and the improvement\r\nof measuring accuracy seems promising in\r\nconsequence of this observation.\r\n\r\nTO BRAM.\r\n","package":"pace-2.0.zip","4":"pace-2.0.zip","src_id":"28644","5":"28644","creation_date":"1710091689","6":"1710091689"},{"0":"5472","vim_version":"7.0","1":"7.0","script_version":"1.3","2":"1.3","version_comment":"demo.vim and pace.vim:\r\nLinks to a repository of the project and\r\narchives can be found in the file headers.\r\n\r\nWhenever the sub-_second_ unit cannot be\r\nascertained so that ticks can be scaled,\r\n`reltimestr()' is resorted to.\r\n\r\nAn in-procedure time lag between an epoch\r\nand its future referents ceases from being\r\na factor.\r\n\r\nThe core calculations of the measuring\r\nalgorithm have been further whittled down.\r\n\r\ndemo.vim:\r\nAllowance is made for the option value of\r\n'switchbuf' after the demonstration ends.\r\n\r\nFor every header line of a batch to print,\r\nsuccessive unprinted batches are searched.\r\n\r\npace.vim:\r\nThe precedence of 'statusline' over 'ruler'\r\nand 'rulerformat' is recognised as support\r\nwarrants for 'laststatus'.\r\n\r\nA sampling alternative to the continuous\r\nupdating of `g:pace_info' is within reach\r\nwith `g:pace_sample' (and patch 7.0.104 for\r\nVim).\r\n\r\nTO BRAM.\r\n","3":"demo.vim and pace.vim:\r\nLinks to a repository of the project and\r\narchives can be found in the file headers.\r\n\r\nWhenever the sub-_second_ unit cannot be\r\nascertained so that ticks can be scaled,\r\n`reltimestr()' is resorted to.\r\n\r\nAn in-procedure time lag between an epoch\r\nand its future referents ceases from being\r\na factor.\r\n\r\nThe core calculations of the measuring\r\nalgorithm have been further whittled down.\r\n\r\ndemo.vim:\r\nAllowance is made for the option value of\r\n'switchbuf' after the demonstration ends.\r\n\r\nFor every header line of a batch to print,\r\nsuccessive unprinted batches are searched.\r\n\r\npace.vim:\r\nThe precedence of 'statusline' over 'ruler'\r\nand 'rulerformat' is recognised as support\r\nwarrants for 'laststatus'.\r\n\r\nA sampling alternative to the continuous\r\nupdating of `g:pace_info' is within reach\r\nwith `g:pace_sample' (and patch 7.0.104 for\r\nVim).\r\n\r\nTO BRAM.\r\n","package":"pace-1.3.zip","4":"pace-1.3.zip","src_id":"28643","5":"28643","creation_date":"1710088252","6":"1710088252"},{"0":"5472","vim_version":"7.0","1":"7.0","script_version":"1.2","2":"1.2","version_comment":"demo.vim:\r\nThe demo buffers allow to re-run a preview.\r\n\r\npace.vim:\r\nThe initial value of `g:pace_info' now observes\r\nthe amassing `g:pace_policy'.\r\n\r\nThe sequence of leave-enter mode routines is\r\narranged for `InsertChange'.\r\n\r\n`PaceSum' keeps up-to-date its rejects sum.\r\n\r\nThe mode check is omitted on `InsertLeave'.","3":"demo.vim:\r\nThe demo buffers allow to re-run a preview.\r\n\r\npace.vim:\r\nThe initial value of `g:pace_info' now observes\r\nthe amassing `g:pace_policy'.\r\n\r\nThe sequence of leave-enter mode routines is\r\narranged for `InsertChange'.\r\n\r\n`PaceSum' keeps up-to-date its rejects sum.\r\n\r\nThe mode check is omitted on `InsertLeave'.","package":"pace-1.2.zip","4":"pace-1.2.zip","src_id":"25202","5":"25202","creation_date":"1494772979","6":"1494772979"},{"0":"5472","vim_version":"7.0","1":"7.0","script_version":"1.1","2":"1.1","version_comment":"pace.txt:\r\nThe 'laststatus' option is set to 1, if 0 (the\r\ndocumentation is made to agree with the script).\r\n\r\npace.vim:\r\nThe `g:pace_policy' variable allows a new value\r\n(2000) to amass buffer typing.\r\n\r\nThe script-defined commands are supplied with the\r\n`-bar' attribute.","3":"pace.txt:\r\nThe 'laststatus' option is set to 1, if 0 (the\r\ndocumentation is made to agree with the script).\r\n\r\npace.vim:\r\nThe `g:pace_policy' variable allows a new value\r\n(2000) to amass buffer typing.\r\n\r\nThe script-defined commands are supplied with the\r\n`-bar' attribute.","package":"pace-1.1.zip","4":"pace-1.1.zip","src_id":"24831","5":"24831","creation_date":"1482778736","6":"1482778736"},{"0":"5472","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"pace-1.0.zip","4":"pace-1.0.zip","src_id":"24672","5":"24672","creation_date":"1477498223","6":"1477498223"}]},"5471":{"script_id":"5471","0":"5471","script_name":"MUcomplete","1":"MUcomplete","script_type":"utility","2":"utility","summary":"Chained (fallback) completion that works the way you want!","3":"Chained (fallback) completion that works the way you want!","description":"GitHub page: https:\/\/github.com\/lifepillar\/vim-mucomplete\r\n\r\nMUcomplete is a minimalist autocompletion plugin for Vim.\r\n\r\nMUcomplete is an implementation of chained (fallback) completion, whereby several completion methods are attempted one after another until a result is returned.\r\n\r\nUnder the hood, MUcomplete does nothing more than typing some completion mappings for you, either when you press \/ or automatically while you are typing. You choose which completion methods to use and in which order, and MUcomplete does the rest. It does no caching, no asynchronous computation, no intelligent guessing. It just makes use of core Vim features.\r\n\r\nMUcomplete brings Vim completion down to earth again.\r\n\r\nMandatory Vim settings:\r\n\r\n    set completeopt+=menuone\r\n\r\nFor automatic completion, you also need one of the following:\r\n\r\n    set completeopt+=noselect\r\n    set completeopt+=noinsert\r\n\r\nOther recommended settings:\r\n\r\n    set shortmess+=c   \" Shut off completion messages\r\n    set belloff+=ctrlg \" If Vim beeps during completion\r\n\r\nNo other configuration is needed. Just start pressing  or  to complete a word. If you want to enable automatic completion at startup, put\r\n\r\n    let g:mucomplete#enable_auto_at_startup = 1\r\n\r\nin your .vimrc. Automatic completion may be enabled and disabled at any time with :MUcompleteAutoToggle.\r\n\r\nBy default, MUcomplete attempts:\r\n\r\n1. path completion, if the text in front of the cursor looks like a path;\r\n2. omni-completion, if enabled in the current buffer;\r\n3. buffer keyword completion;\r\n4. dictionary completion, if a dictionary is set for the current buffer;\r\n5. spelling completion, if 'spell' is on and 'spelllang' is set;\r\n\r\nin this order (this is called a \u00e2\u0080\u009ccompletion chain\u00e2\u0080\u009d). At the first successful attempt, the pop-up menu shows the results. When the pop-up menu is visible, you may cycle back and forth through the completion chain and try different completion methods by pressing  and , respectively.\r\n\r\nMUcomplete is fully customizable. See :help mucomplete.txt for detailed documentation.\r\n\r\nImportant: by itself, MUcomplete does not provide any \u00e2\u0080\u009cintellisense\u00e2\u0080\u009d\/semantic completion. If you want that, you also need to install suitable omni completion plugins for the languages you are using.","4":"GitHub page: https:\/\/github.com\/lifepillar\/vim-mucomplete\r\n\r\nMUcomplete is a minimalist autocompletion plugin for Vim.\r\n\r\nMUcomplete is an implementation of chained (fallback) completion, whereby several completion methods are attempted one after another until a result is returned.\r\n\r\nUnder the hood, MUcomplete does nothing more than typing some completion mappings for you, either when you press \/ or automatically while you are typing. You choose which completion methods to use and in which order, and MUcomplete does the rest. It does no caching, no asynchronous computation, no intelligent guessing. It just makes use of core Vim features.\r\n\r\nMUcomplete brings Vim completion down to earth again.\r\n\r\nMandatory Vim settings:\r\n\r\n    set completeopt+=menuone\r\n\r\nFor automatic completion, you also need one of the following:\r\n\r\n    set completeopt+=noselect\r\n    set completeopt+=noinsert\r\n\r\nOther recommended settings:\r\n\r\n    set shortmess+=c   \" Shut off completion messages\r\n    set belloff+=ctrlg \" If Vim beeps during completion\r\n\r\nNo other configuration is needed. Just start pressing  or  to complete a word. If you want to enable automatic completion at startup, put\r\n\r\n    let g:mucomplete#enable_auto_at_startup = 1\r\n\r\nin your .vimrc. Automatic completion may be enabled and disabled at any time with :MUcompleteAutoToggle.\r\n\r\nBy default, MUcomplete attempts:\r\n\r\n1. path completion, if the text in front of the cursor looks like a path;\r\n2. omni-completion, if enabled in the current buffer;\r\n3. buffer keyword completion;\r\n4. dictionary completion, if a dictionary is set for the current buffer;\r\n5. spelling completion, if 'spell' is on and 'spelllang' is set;\r\n\r\nin this order (this is called a \u00e2\u0080\u009ccompletion chain\u00e2\u0080\u009d). At the first successful attempt, the pop-up menu shows the results. When the pop-up menu is visible, you may cycle back and forth through the completion chain and try different completion methods by pressing  and , respectively.\r\n\r\nMUcomplete is fully customizable. See :help mucomplete.txt for detailed documentation.\r\n\r\nImportant: by itself, MUcomplete does not provide any \u00e2\u0080\u009cintellisense\u00e2\u0080\u009d\/semantic completion. If you want that, you also need to install suitable omni completion plugins for the languages you are using.","install_details":"","5":"","first_name":"","6":"","last_name":"Lifepillar","7":"Lifepillar","releases":[{"0":"5471","vim_version":"7.2","1":"7.2","script_version":"1.5.0","2":"1.5.0","version_comment":"License under the MIT license.","3":"License under the MIT license.","package":"vim-mucomplete-1.5.0.tar.gz","4":"vim-mucomplete-1.5.0.tar.gz","src_id":"27366","5":"27366","creation_date":"1605506747","6":"1605506747"},{"0":"5471","vim_version":"7.0","1":"7.0","script_version":"1.4.1","2":"1.4.1","version_comment":"Minor bug fixes mostly related to spelling, dictionary and thesaurus completions.","3":"Minor bug fixes mostly related to spelling, dictionary and thesaurus completions.","package":"vim-mucomplete-1.4.1.tar.gz","4":"vim-mucomplete-1.4.1.tar.gz","src_id":"26858","5":"26858","creation_date":"1575232072","6":"1575232072"},{"0":"5471","vim_version":"7.2","1":"7.2","script_version":"1.4.0","2":"1.4.0","version_comment":"MUcomplete keeps improving, thanks to users's feedback! This release features: improved compatibility with LanguageClient (don't skip `:help mucomplete-compatibility`); syntax-aware completion chains (`:help g:mucomplete#scoped_chains`); improved completion for HTML\/XML; new options (g:mucomplete#empty_text_auto and g:mucomplete#reopen_immediately) and a new function (mucomplete#add_user_mapping()). And of course, even better documentation!","3":"MUcomplete keeps improving, thanks to users's feedback! This release features: improved compatibility with LanguageClient (don't skip `:help mucomplete-compatibility`); syntax-aware completion chains (`:help g:mucomplete#scoped_chains`); improved completion for HTML\/XML; new options (g:mucomplete#empty_text_auto and g:mucomplete#reopen_immediately) and a new function (mucomplete#add_user_mapping()). And of course, even better documentation!","package":"vim-mucomplete-1.4.0.tar.gz","4":"vim-mucomplete-1.4.0.tar.gz","src_id":"26463","5":"26463","creation_date":"1556249795","6":"1556249795"},{"0":"5471","vim_version":"7.2","1":"7.2","script_version":"1.3.0","2":"1.3.0","version_comment":"Happy new year! 🥂 MUcomplete has a new completion method called \"list\", which allows you to use your own list of words (yes, per filetype)! Other fixes: path completion now completes paths after an equal sign not followed by spaces; better autocompletion in Vim older than 7.4.775; improved documentation. 🍾","3":"Happy new year! 🥂 MUcomplete has a new completion method called \"list\", which allows you to use your own list of words (yes, per filetype)! Other fixes: path completion now completes paths after an equal sign not followed by spaces; better autocompletion in Vim older than 7.4.775; improved documentation. 🍾","package":"vim-mucomplete-1.3.0.tar.gz","4":"vim-mucomplete-1.3.0.tar.gz","src_id":"26313","5":"26313","creation_date":"1546320037","6":"1546320037"},{"0":"5471","vim_version":"7.2","1":"7.2","script_version":"1.2.1","2":"1.2.1","version_comment":"NEW FEATURES: (1) MUcompletePmenu event is triggered upon successful completion; (2) Notifications: display the name or description of the current completion method in the command line or in the status line; (3) Compatibility with Neosnippet; (4) Optionally delay completion with timers (instead of using CursorHoldI and updatetime); (5) Specific activation patterns for C\/C++ and HTML\/XML; (6) New option to set the minimum number of (keyword) characters before the cursor needed to trigger autocompletion.\r\nOTHER IMPROVEMENTS: More robust path completion. Better support for UltiSnips and SnipMate. Updated documentation.\r\nIf you like MUcomplete, consider donating to the project (see Readme)!\r\n","3":"NEW FEATURES: (1) MUcompletePmenu event is triggered upon successful completion; (2) Notifications: display the name or description of the current completion method in the command line or in the status line; (3) Compatibility with Neosnippet; (4) Optionally delay completion with timers (instead of using CursorHoldI and updatetime); (5) Specific activation patterns for C\/C++ and HTML\/XML; (6) New option to set the minimum number of (keyword) characters before the cursor needed to trigger autocompletion.\r\nOTHER IMPROVEMENTS: More robust path completion. Better support for UltiSnips and SnipMate. Updated documentation.\r\nIf you like MUcomplete, consider donating to the project (see Readme)!\r\n","package":"vim-mucomplete-1.2.1.tar.gz","4":"vim-mucomplete-1.2.1.tar.gz","src_id":"26252","5":"26252","creation_date":"1540611114","6":"1540611114"},{"0":"5471","vim_version":"7.2","1":"7.2","script_version":"1.1.0","2":"1.1.0","version_comment":"MUcomplete's development did not stop with v1.0! There's already a new feature: delayed auto-completion allows MUcomplete to kick in only when you pause typing! Besides, MUcomplete does not map ,  and  any more (requires Vim 8.0.0283 or later), so conflicts with other plugins (e.g., endwise) are avoided. Improved backward compatibility: auto-completion is available in Vim versions as early as 7.4.143 (minimum required version is still 7.2). Option mucomplete#smart_enter has been removed: see `:help mucomplete-tips` for a replacement.","3":"MUcomplete's development did not stop with v1.0! There's already a new feature: delayed auto-completion allows MUcomplete to kick in only when you pause typing! Besides, MUcomplete does not map ,  and  any more (requires Vim 8.0.0283 or later), so conflicts with other plugins (e.g., endwise) are avoided. Improved backward compatibility: auto-completion is available in Vim versions as early as 7.4.143 (minimum required version is still 7.2). Option mucomplete#smart_enter has been removed: see `:help mucomplete-tips` for a replacement.","package":"vim-mucomplete-1.1.0.tar.gz","4":"vim-mucomplete-1.1.0.tar.gz","src_id":"26163","5":"26163","creation_date":"1533408614","6":"1533408614"},{"0":"5471","vim_version":"7.2","1":"7.2","script_version":"1.0.0","2":"1.0.0","version_comment":"MUcomplete reaches milestone release 1.0.0! After 21 months of development, MUcomplete has earned more than 370 stars on GitHub and has 0 (zero!) open issues (at the time of this release)! Much simpler than most other completion plugins, pure Vim script with minimal requirements (works in Vim 7.2 through Vim 8), MUcomplete tries not to reinvent the wheel, but stands on the shoulder of a giant (Vim!), streamlining Vim's own completion methods, but also allowing the flexibility of adding your own. MUcomplete's documentation is longer than MUComplete's code and it rocks! Don't skip it!","3":"MUcomplete reaches milestone release 1.0.0! After 21 months of development, MUcomplete has earned more than 370 stars on GitHub and has 0 (zero!) open issues (at the time of this release)! Much simpler than most other completion plugins, pure Vim script with minimal requirements (works in Vim 7.2 through Vim 8), MUcomplete tries not to reinvent the wheel, but stands on the shoulder of a giant (Vim!), streamlining Vim's own completion methods, but also allowing the flexibility of adding your own. MUcomplete's documentation is longer than MUComplete's code and it rocks! Don't skip it!","package":"vim-mucomplete-1.0.0.tar.gz","4":"vim-mucomplete-1.0.0.tar.gz","src_id":"26143","5":"26143","creation_date":"1532316548","6":"1532316548"},{"0":"5471","vim_version":"7.2","1":"7.2","script_version":"1.0.0rc8","2":"1.0.0rc8","version_comment":"Plugs for extending the current completion (e.g., to expand 'Ne' to 'New York Times') now work with every value of completeopt. Fixed the \u00e2\u0080\u009cnatural\u00e2\u0080\u009d direction for line completion. Minor bug fixes. Added more tests. Updated documentation.\r\n\r\n**Release 1.0.0** is approaching! Please report any issue you may have with this version!","3":"Plugs for extending the current completion (e.g., to expand 'Ne' to 'New York Times') now work with every value of completeopt. Fixed the \u00e2\u0080\u009cnatural\u00e2\u0080\u009d direction for line completion. Minor bug fixes. Added more tests. Updated documentation.\r\n\r\n**Release 1.0.0** is approaching! Please report any issue you may have with this version!","package":"vim-mucomplete-1.0.0rc8.tar.gz","4":"vim-mucomplete-1.0.0rc8.tar.gz","src_id":"25978","5":"25978","creation_date":"1526224734","6":"1526224734"},{"0":"5471","vim_version":"7.2","1":"7.2","script_version":"1.0.0rc7","2":"1.0.0rc7","version_comment":"New feature: extend the completed text by copying the words following the previous expansion in other contexts (requires a mapping by the user). New option: g:mucomplete#smart_enter (when set, always insert a new line when typing Enter to close the popup menu). Omni-complete after dots in Python buffers. Document settings to improve compatibility with auto-pairs and endwise. A couple of bug fixes.\r\nVersion 1.0.0 is approaching! Please report any issues you may have with this release!","3":"New feature: extend the completed text by copying the words following the previous expansion in other contexts (requires a mapping by the user). New option: g:mucomplete#smart_enter (when set, always insert a new line when typing Enter to close the popup menu). Omni-complete after dots in Python buffers. Document settings to improve compatibility with auto-pairs and endwise. A couple of bug fixes.\r\nVersion 1.0.0 is approaching! Please report any issues you may have with this release!","package":"vim-mucomplete-1.0.0rc7.tar.gz","4":"vim-mucomplete-1.0.0rc7.tar.gz","src_id":"25896","5":"25896","creation_date":"1521746483","6":"1521746483"},{"0":"5471","vim_version":"7.2","1":"7.2","script_version":"1.0.0rc6","2":"1.0.0rc6","version_comment":"Further improvements and bug fixes to path completion. Minor fix for users overriding cycling keys. Added a minimal test frameworks and some tests. Version 1.0.0 is approaching! Please report any issues you may have with the current release!","3":"Further improvements and bug fixes to path completion. Minor fix for users overriding cycling keys. Added a minimal test frameworks and some tests. Version 1.0.0 is approaching! Please report any issues you may have with the current release!","package":"vim-mucomplete-1.0.0rc6.tar.gz","4":"vim-mucomplete-1.0.0rc6.tar.gz","src_id":"25854","5":"25854","creation_date":"1520159267","6":"1520159267"},{"0":"5471","vim_version":"7.2","1":"7.2","script_version":"1.0.0rc4","2":"1.0.0rc4","version_comment":"Further tweaks to path completion.\r\nVersion 1.0.0 is approaching: please report any issues you may have with release!\r\n","3":"Further tweaks to path completion.\r\nVersion 1.0.0 is approaching: please report any issues you may have with release!\r\n","package":"vim-mucomplete-1.0.0rc4.tar.gz","4":"vim-mucomplete-1.0.0rc4.tar.gz","src_id":"25815","5":"25815","creation_date":"1517766353","6":"1517766353"},{"0":"5471","vim_version":"7.2","1":"7.2","script_version":"1.0.0rc3","2":"1.0.0rc3","version_comment":"Windows users enjoy! Now you can complete paths with forward slashes, too! Other improvements to completion for all users, in particular when completing paths with spaces. A few minor bug fixes. Updated docs. New options: g:mucomplete#look_behind, g:mucomplete#use_only_windows_paths.\r\nVersion 1.0.0 is approaching: please report any issues you have with this version!","3":"Windows users enjoy! Now you can complete paths with forward slashes, too! Other improvements to completion for all users, in particular when completing paths with spaces. A few minor bug fixes. Updated docs. New options: g:mucomplete#look_behind, g:mucomplete#use_only_windows_paths.\r\nVersion 1.0.0 is approaching: please report any issues you have with this version!","package":"vim-mucomplete-1.0.0rc3.tar.gz","4":"vim-mucomplete-1.0.0rc3.tar.gz","src_id":"25813","5":"25813","creation_date":"1517684065","6":"1517684065"},{"0":"5471","vim_version":"7.2","1":"7.2","script_version":"1.0.0rc2","2":"1.0.0rc2","version_comment":"Simplified configuration (no need to define mappings for ,  and  any longer!). Reduced startup time. A few new options. Better error reporting of conflicting mappings. A few minor bug fixes. Better help file.","3":"Simplified configuration (no need to define mappings for ,  and  any longer!). Reduced startup time. A few new options. Better error reporting of conflicting mappings. A few minor bug fixes. Better help file.","package":"vim-mucomplete-1.0.0rc2.tar.gz","4":"vim-mucomplete-1.0.0rc2.tar.gz","src_id":"25794","5":"25794","creation_date":"1516554575","6":"1516554575"},{"0":"5471","vim_version":"7.2","1":"7.2","script_version":"1.0.0rc1","2":"1.0.0rc1","version_comment":"MUcomplete becomes even better and goes 1.0! The autocompletion mechanism is now based on a synergy between InsertCharPre and TextChangedI for a better user experience. Besides, a couple of minor bug fixes and some code refactoring.","3":"MUcomplete becomes even better and goes 1.0! The autocompletion mechanism is now based on a synergy between InsertCharPre and TextChangedI for a better user experience. Besides, a couple of minor bug fixes and some code refactoring.","package":"vim-mucomplete-1.0.0rc1.tar.gz","4":"vim-mucomplete-1.0.0rc1.tar.gz","src_id":"25086","5":"25086","creation_date":"1492795913","6":"1492795913"},{"0":"5471","vim_version":"7.2","1":"7.2","script_version":"1.0.0.0b3","2":"1.0.0.0b3","version_comment":"MUcomplete becomes even better and goes 1.0! Autocompletion is now based on InsertCharPre instead of TextChangedI. CompleteDone is not used any longer. Removed g:mucomplete#trigger_auto_pattern: use g:mucomplete#can_complete instead.","3":"MUcomplete becomes even better and goes 1.0! Autocompletion is now based on InsertCharPre instead of TextChangedI. CompleteDone is not used any longer. Removed g:mucomplete#trigger_auto_pattern: use g:mucomplete#can_complete instead.","package":"vim-mucomplete-1.0.0b3.tar.gz","4":"vim-mucomplete-1.0.0b3.tar.gz","src_id":"25081","5":"25081","creation_date":"1492591156","6":"1492591156"},{"0":"5471","vim_version":"7.2","1":"7.2","script_version":"1.0.0b2","2":"1.0.0b2","version_comment":"Fixed a critical regression.\r\nMUcomplete becomes even better and goes 1.0! With better autocompletion, other new cool features and bug fixes.","3":"Fixed a critical regression.\r\nMUcomplete becomes even better and goes 1.0! With better autocompletion, other new cool features and bug fixes.","package":"vim-mucomplete-1.0.0b2.tar.gz","4":"vim-mucomplete-1.0.0b2.tar.gz","src_id":"25079","5":"25079","creation_date":"1492497222","6":"1492497222"},{"0":"5471","vim_version":"7.2","1":"7.2","script_version":"1.0.0b1","2":"1.0.0b1","version_comment":"MUcomplete becomes even better and goes 1.0! Much improved autocompletion experience: the pop-up menu does not go on and off on alternating keys any longer! Make  move in the pop-up menu from top to bottom or from bottom to top on a per-completion type basis! Allow path completion relative to the directory of the current buffer! Use 'path' completion by default. Et cetera\u00e2\u0080\u00a6 All of this in the same amount of code! Please check the Readme and the documentation.","3":"MUcomplete becomes even better and goes 1.0! Much improved autocompletion experience: the pop-up menu does not go on and off on alternating keys any longer! Make  move in the pop-up menu from top to bottom or from bottom to top on a per-completion type basis! Allow path completion relative to the directory of the current buffer! Use 'path' completion by default. Et cetera\u00e2\u0080\u00a6 All of this in the same amount of code! Please check the Readme and the documentation.","package":"vim-mucomplete-1.0.0b1.tar.gz","4":"vim-mucomplete-1.0.0b1.tar.gz","src_id":"25076","5":"25076","creation_date":"1492424059","6":"1492424059"},{"0":"5471","vim_version":"7.2","1":"7.2","script_version":"0.5.0","2":"0.5.0","version_comment":"Too many changes to list here. Some highlights: improved spelling method, with new options; ignore `noselect` for manual completion (except for spelling methods); use  instead of  as a right cycling key, for better compatibility; new setting to exit ctrl-x submode (mucomplete#exit_ctrlx_keys has been removed) and new default value (``); bug fixes in 'cmd' and 'ulti' methods, and other critical and less critical bug fixes. Kudos to bug hunter LacyGoIll for reporting and solving several issues!","3":"Too many changes to list here. Some highlights: improved spelling method, with new options; ignore `noselect` for manual completion (except for spelling methods); use  instead of  as a right cycling key, for better compatibility; new setting to exit ctrl-x submode (mucomplete#exit_ctrlx_keys has been removed) and new default value (``); bug fixes in 'cmd' and 'ulti' methods, and other critical and less critical bug fixes. Kudos to bug hunter LacyGoIll for reporting and solving several issues!","package":"vim-mucomplete-0.5.0.tar.gz","4":"vim-mucomplete-0.5.0.tar.gz","src_id":"24803","5":"24803","creation_date":"1481826764","6":"1481826764"},{"0":"5471","vim_version":"7.2","1":"7.2","script_version":"0.4.3","2":"0.4.3","version_comment":"Improved documentation.","3":"Improved documentation.","package":"vim-mucomplete-0.4.3.tar.gz","4":"vim-mucomplete-0.4.3.tar.gz","src_id":"24780","5":"24780","creation_date":"1480872039","6":"1480872039"},{"0":"5471","vim_version":"7.2","1":"7.2","script_version":"0.4.2","2":"0.4.2","version_comment":"Improved documentation.","3":"Improved documentation.","package":"vim-mucomplete-0.4.2.tar.gz","4":"vim-mucomplete-0.4.2.tar.gz","src_id":"24764","5":"24764","creation_date":"1480154183","6":"1480154183"},{"0":"5471","vim_version":"7.2","1":"7.2","script_version":"0.4.1","2":"0.4.1","version_comment":"Added flag variable that tells whether completion is initiated automatically or by pressing a key. Fixed a bug in 'line' completion. Expanded documentation.","3":"Added flag variable that tells whether completion is initiated automatically or by pressing a key. Fixed a bug in 'line' completion. Expanded documentation.","package":"vim-mucomplete-0.4.1.tar.gz","4":"vim-mucomplete-0.4.1.tar.gz","src_id":"24749","5":"24749","creation_date":"1479546324","6":"1479546324"},{"0":"5471","vim_version":"7.2","1":"7.2","script_version":"0.4.0","2":"0.4.0","version_comment":"- New 'path' completion method that works similar to YouCompleteMe.\r\n- New 'uspl' spelling suggestion method, which acts only on the word in front of the cursor.\r\n- Several bug fixes.\r\n- Compatible with Vim 7.2 or later.","3":"- New 'path' completion method that works similar to YouCompleteMe.\r\n- New 'uspl' spelling suggestion method, which acts only on the word in front of the cursor.\r\n- Several bug fixes.\r\n- Compatible with Vim 7.2 or later.","package":"vim-mucomplete-0.4.0.tar.gz","4":"vim-mucomplete-0.4.0.tar.gz","src_id":"24734","5":"24734","creation_date":"1479241173","6":"1479241173"},{"0":"5471","vim_version":"7.3","1":"7.3","script_version":"0.3.1","2":"0.3.1","version_comment":"Respect completeopt's settings, including noinsert and noselect.","3":"Respect completeopt's settings, including noinsert and noselect.","package":"vim-mucomplete-0.3.1.tar.gz","4":"vim-mucomplete-0.3.1.tar.gz","src_id":"24703","5":"24703","creation_date":"1478248127","6":"1478248127"},{"0":"5471","vim_version":"7.3","1":"7.3","script_version":"0.3.0","2":"0.3.0","version_comment":"Added the ability to cycle back and forth through completion methods while the pop-up is visible.\r\nImproved compatibility with older Vim. Other minor additions and a few code optimizations.","3":"Added the ability to cycle back and forth through completion methods while the pop-up is visible.\r\nImproved compatibility with older Vim. Other minor additions and a few code optimizations.","package":"vim-mucomplete-0.3.0.tar.gz","4":"vim-mucomplete-0.3.0.tar.gz","src_id":"24702","5":"24702","creation_date":"1478111321","6":"1478111321"},{"0":"5471","vim_version":"7.4","1":"7.4","script_version":"0.2.0","2":"0.2.0","version_comment":"Improve compatibility with older Vim. Add more options. Add support for suggesting UltiSnips snippets. Other minor fixes.","3":"Improve compatibility with older Vim. Add more options. Add support for suggesting UltiSnips snippets. Other minor fixes.","package":"vim-mucomplete-0.2.0.tar.gz","4":"vim-mucomplete-0.2.0.tar.gz","src_id":"24677","5":"24677","creation_date":"1477689395","6":"1477689395"},{"0":"5471","vim_version":"8.0","1":"8.0","script_version":"0.1.2","2":"0.1.2","version_comment":"Fixed a bug causing completion methods to be skipped even when they return results.","3":"Fixed a bug causing completion methods to be skipped even when they return results.","package":"vim-mucomplete-0.1.2.tar.gz","4":"vim-mucomplete-0.1.2.tar.gz","src_id":"24673","5":"24673","creation_date":"1477511127","6":"1477511127"},{"0":"5471","vim_version":"8.0","1":"8.0","script_version":"0.1.1","2":"0.1.1","version_comment":"Fix a bug preventing tab completion to display the popup menu.","3":"Fix a bug preventing tab completion to display the popup menu.","package":"vim-mucomplete-0.1.1.tar.gz","4":"vim-mucomplete-0.1.1.tar.gz","src_id":"24669","5":"24669","creation_date":"1477290410","6":"1477290410"},{"0":"5471","vim_version":"8.0","1":"8.0","script_version":"0.1.0","2":"0.1.0","version_comment":"Initial upload","3":"Initial upload","package":"vim-mucomplete-0.1.0.tar","4":"vim-mucomplete-0.1.0.tar","src_id":"24666","5":"24666","creation_date":"1477208635","6":"1477208635"}]},"5469":{"script_id":"5469","0":"5469","script_name":"Subnet Search","1":"Subnet Search","script_type":"utility","2":"utility","summary":"Match all IP addresses withing a given IPv4 CIDR address block","3":"Match all IP addresses withing a given IPv4 CIDR address block","description":"This utility will produce a regular expression that matches all IP addresses within a given subnet, then execute that search.  When invoked, it will ask for a CIDR (172.16.24.0\/28 for example) subnet address.  It requires python 2.7, and the backported ipaddress module, and vim compiled with python support.\r\n\r\nFor animated gif, see github repo at https:\/\/github.com\/johnbiederstedt\/subnetsearch\r\n ","4":"This utility will produce a regular expression that matches all IP addresses within a given subnet, then execute that search.  When invoked, it will ask for a CIDR (172.16.24.0\/28 for example) subnet address.  It requires python 2.7, and the backported ipaddress module, and vim compiled with python support.\r\n\r\nFor animated gif, see github repo at https:\/\/github.com\/johnbiederstedt\/subnetsearch\r\n ","install_details":"Place it in your plugins directory.","5":"Place it in your plugins directory.","first_name":"John","6":"John","last_name":"Biederstedt","7":"Biederstedt","releases":[{"0":"5469","vim_version":"7.4","1":"7.4","script_version":".02","2":".02","version_comment":"Compensated for arbitrary unicode errors that popup in the mainline python2.7 ipaddress module","3":"Compensated for arbitrary unicode errors that popup in the mainline python2.7 ipaddress module","package":"subnetsearch.vim","4":"subnetsearch.vim","src_id":"25432","5":"25432","creation_date":"1500615906","6":"1500615906"},{"0":"5469","vim_version":"7.4","1":"7.4","script_version":".01","2":".01","version_comment":"Included GPL2","3":"Included GPL2","package":"subnetsearch.vim","4":"subnetsearch.vim","src_id":"24665","5":"24665","creation_date":"1477174761","6":"1477174761"}]},"5468":{"script_id":"5468","0":"5468","script_name":"glsl.vim","1":"glsl.vim","script_type":"ftplugin","2":"ftplugin","summary":"Utilities for WebGL\/GLSL\/Three.js developers.","3":"Utilities for WebGL\/GLSL\/Three.js developers.","description":"https:\/\/github.com\/petrbroz\/vim-glsl","4":"https:\/\/github.com\/petrbroz\/vim-glsl","install_details":"","5":"","first_name":"Petr","6":"Petr","last_name":"Broz","7":"Broz","releases":[{"0":"5468","vim_version":"7.0","1":"7.0","script_version":"1.0.0","2":"1.0.0","version_comment":"Initial upload","3":"Initial upload","package":"vim-glsl-1.0.0.tar.gz","4":"vim-glsl-1.0.0.tar.gz","src_id":"24644","5":"24644","creation_date":"1476757214","6":"1476757214"}]},"5466":{"script_id":"5466","0":"5466","script_name":"vim-jobs","1":"vim-jobs","script_type":"utility","2":"utility","summary":"Manage async jobs ","3":"Manage async jobs ","description":"The plugin is developed on github: https:\/\/github.com\/coot\/vim-jobs\r\n\r\nCheckout vim-term plugin: https:\/\/www.vim.org\/scripts\/script.php?script_id=5731 it may suit you better.","4":"The plugin is developed on github: https:\/\/github.com\/coot\/vim-jobs\r\n\r\nCheckout vim-term plugin: https:\/\/www.vim.org\/scripts\/script.php?script_id=5731 it may suit you better.","install_details":"Drop the file under `.vim\/plugin` directory.","5":"Drop the file under `.vim\/plugin` directory.","first_name":"Marcin","6":"Marcin","last_name":"Szamotulski","7":"Szamotulski","releases":[{"0":"5466","vim_version":"7.0","1":"7.0","script_version":"1","2":"1","version_comment":"Initial upload","3":"Initial upload","package":"jobs.vim","4":"jobs.vim","src_id":"24630","5":"24630","creation_date":"1476548430","6":"1476548430"}]},"5464":{"script_id":"5464","0":"5464","script_name":"vim-kramdown-tab","1":"vim-kramdown-tab","script_type":"utility","2":"utility","summary":"A vim plugin to resolve indent issue of content nested in Markdown lists, especi","3":"A vim plugin to resolve indent issue of content nested in Markdown lists, especi","description":"In GitHub: https:\/\/github.com\/mzlogin\/vim-kramdown-tab\r\n\r\nScreenshots:\r\n\r\nhttps:\/\/raw.githubusercontent.com\/mzlogin\/vim-kramdown-tab\/master\/screenshots\/test.gif\r\n\r\nWith kramdown(GitHub Pages' default Markdown engine), the indent rule for content nested in lists is:\r\n\r\nGood:\r\n\r\n1. ordered item one\r\n    nested content here\r\n2. ordered item two\r\n\r\n* unorder item one\r\n  nested content here\r\n* unorder item two\r\n\r\nBad:\r\n\r\n1. ordered item one\r\n    nested content here\r\n2. ordered item two\r\n\r\n* unorder item one\r\n    nested content here\r\n* unorder item two\r\n\r\nTab key doesn't know how to indent! This plugin is to rescue your Tab.\r\n\r\nUsage:\r\n\r\nWhen you want to indent your content nested in lists, just press Leader-Tab.","4":"In GitHub: https:\/\/github.com\/mzlogin\/vim-kramdown-tab\r\n\r\nScreenshots:\r\n\r\nhttps:\/\/raw.githubusercontent.com\/mzlogin\/vim-kramdown-tab\/master\/screenshots\/test.gif\r\n\r\nWith kramdown(GitHub Pages' default Markdown engine), the indent rule for content nested in lists is:\r\n\r\nGood:\r\n\r\n1. ordered item one\r\n    nested content here\r\n2. ordered item two\r\n\r\n* unorder item one\r\n  nested content here\r\n* unorder item two\r\n\r\nBad:\r\n\r\n1. ordered item one\r\n    nested content here\r\n2. ordered item two\r\n\r\n* unorder item one\r\n    nested content here\r\n* unorder item two\r\n\r\nTab key doesn't know how to indent! This plugin is to rescue your Tab.\r\n\r\nUsage:\r\n\r\nWhen you want to indent your content nested in lists, just press Leader-Tab.","install_details":"Suggest to manage your vim plugins via Vundle so you can install it simply three steps:\r\n\r\n1. add the following line to your vimrc file\r\n\r\n    Plugin 'mzlogin\/vim-kramdown-tab'\r\n\r\n2. :so $MYVIMRC\r\n\r\n3. :PluginInstall\r\n","5":"Suggest to manage your vim plugins via Vundle so you can install it simply three steps:\r\n\r\n1. add the following line to your vimrc file\r\n\r\n    Plugin 'mzlogin\/vim-kramdown-tab'\r\n\r\n2. :so $MYVIMRC\r\n\r\n3. :PluginInstall\r\n","first_name":"Ma","6":"Ma","last_name":"Zhuang","7":"Zhuang","releases":[{"0":"5464","vim_version":"7.0","1":"7.0","script_version":"v0.1","2":"v0.1","version_comment":"Initial upload","3":"Initial upload","package":"vim-kramdown-tab-0.1.tar.gz","4":"vim-kramdown-tab-0.1.tar.gz","src_id":"24628","5":"24628","creation_date":"1476420598","6":"1476420598"}]},"5463":{"script_id":"5463","0":"5463","script_name":"TabList for terminal vim","1":"TabList for terminal vim","script_type":"utility","2":"utility","summary":"Get list of tab pages and the windows in them in a quickfix like window.","3":"Get list of tab pages and the windows in them in a quickfix like window.","description":"Get a list of tab pages and the windows in them in a quickfix-like window.\r\n\r\nUsage:\r\n1. You can use the UP\/DOWN arrow keys to navigate to any tab page in the list.\r\n2. You can use mouse-doubleclick\/press enter on the items in the list to go to that tab page.\r\n3. You can use 'dd' to close a tab page\r\n4. map a suitable key to \"Tablist#GetTabList\" (without quotes) to use this plugin.\r\n   e.g. I have this in my ~\/.vimrc:\r\n   nnoremap  Tablist#GetTabList\r\n","4":"Get a list of tab pages and the windows in them in a quickfix-like window.\r\n\r\nUsage:\r\n1. You can use the UP\/DOWN arrow keys to navigate to any tab page in the list.\r\n2. You can use mouse-doubleclick\/press enter on the items in the list to go to that tab page.\r\n3. You can use 'dd' to close a tab page\r\n4. map a suitable key to \"Tablist#GetTabList\" (without quotes) to use this plugin.\r\n   e.g. I have this in my ~\/.vimrc:\r\n   nnoremap  Tablist#GetTabList\r\n","install_details":"This script bundle uses vimball.\r\nJust source this script bundle.\r\n\r\n$ vim Tablist.vmb\r\n: source %","5":"This script bundle uses vimball.\r\nJust source this script bundle.\r\n\r\n$ vim Tablist.vmb\r\n: source %","first_name":"Anish","6":"Anish","last_name":"Sane","7":"Sane","releases":[{"0":"5463","vim_version":"7.0","1":"7.0","script_version":"1.01","2":"1.01","version_comment":"Minor fix: Corrected the handling of dd command for the tab. Now, dd will close the tab, but keep the cursor at the same location.","3":"Minor fix: Corrected the handling of dd command for the tab. Now, dd will close the tab, but keep the cursor at the same location.","package":"Tablist.vmb","4":"Tablist.vmb","src_id":"24639","5":"24639","creation_date":"1476681984","6":"1476681984"},{"0":"5463","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"Tablist.vmb","4":"Tablist.vmb","src_id":"24625","5":"24625","creation_date":"1476342135","6":"1476342135"}]},"5462":{"script_id":"5462","0":"5462","script_name":"Despacio","1":"Despacio","script_type":"color scheme","2":"color scheme","summary":"Vim Colorscheme","3":"Vim Colorscheme","description":"description\r\nA warm colorscheme for Terminal Vim and GUI Vim. \r\n\r\nFor Screenshots, color options, and future downloads check out the GitHub repo here: \r\nhttps:\/\/github.com\/AlessandroYorba\/Despacio\r\n\r\n","4":"description\r\nA warm colorscheme for Terminal Vim and GUI Vim. \r\n\r\nFor Screenshots, color options, and future downloads check out the GitHub repo here: \r\nhttps:\/\/github.com\/AlessandroYorba\/Despacio\r\n\r\n","install_details":"For Unix users, place despacio.vim in ~\/.vim\/colors \r\nWindows users, place despacio.vim in ~\\\\vimfiles\\\\colors \r\n\r\nor use your favorite package manager","5":"For Unix users, place despacio.vim in ~\/.vim\/colors \r\nWindows users, place despacio.vim in ~\\\\vimfiles\\\\colors \r\n\r\nor use your favorite package manager","first_name":"Alessandro","6":"Alessandro","last_name":"Yorba","7":"Yorba","releases":[{"0":"5462","vim_version":"7.0","1":"7.0","script_version":"82de4e6","2":"82de4e6","version_comment":"Enjoy!","3":"Enjoy!","package":"despacio.vim","4":"despacio.vim","src_id":"26946","5":"26946","creation_date":"1580309318","6":"1580309318"},{"0":"5462","vim_version":"7.0","1":"7.0","script_version":"8cc515c  ","2":"8cc515c  ","version_comment":"New Pmenu groups, New Tabline groups, New String color, New Normal,  New Terminal Themes\r\n\r\nFor more data: https:\/\/github.com\/AlessandroYorba\/Despacio","3":"New Pmenu groups, New Tabline groups, New String color, New Normal,  New Terminal Themes\r\n\r\nFor more data: https:\/\/github.com\/AlessandroYorba\/Despacio","package":"despacio.vim","4":"despacio.vim","src_id":"25702","5":"25702","creation_date":"1512767514","6":"1512767514"},{"0":"5462","vim_version":"7.0","1":"7.0","script_version":"543556d","2":"543556d","version_comment":"Brand new colors!!\r\nAroma: Medium and balanced. A roast character with subtle fermentation fruitiness\r\nFlavor: A perfect rounded flavor of bitter and sweet with a hint of chocolate notes and coffee\r\nAppearance: Distinctively black full bodied","3":"Brand new colors!!\r\nAroma: Medium and balanced. A roast character with subtle fermentation fruitiness\r\nFlavor: A perfect rounded flavor of bitter and sweet with a hint of chocolate notes and coffee\r\nAppearance: Distinctively black full bodied","package":"despacio.vim","4":"despacio.vim","src_id":"25633","5":"25633","creation_date":"1509689459","6":"1509689459"},{"0":"5462","vim_version":"7.0","1":"7.0","script_version":"4","2":"4","version_comment":"Added 4 new modes to darken Despacio ( Sunset, Twilight, Midnight, Pitch )\r\nAdded Terminal themes and Xresources for all modes\r\nImproved visibility for Prompt Status and Visual Aid Highlight Groups\r\nImproved analogous colors throughout \r\n","3":"Added 4 new modes to darken Despacio ( Sunset, Twilight, Midnight, Pitch )\r\nAdded Terminal themes and Xresources for all modes\r\nImproved visibility for Prompt Status and Visual Aid Highlight Groups\r\nImproved analogous colors throughout \r\n","package":"despacio.vim","4":"despacio.vim","src_id":"24704","5":"24704","creation_date":"1478292652","6":"1478292652"},{"0":"5462","vim_version":"7.0","1":"7.0","script_version":"1","2":"1","version_comment":"Initial upload","3":"Initial upload","package":"despacio.vim","4":"despacio.vim","src_id":"24620","5":"24620","creation_date":"1476202595","6":"1476202595"}]},"5461":{"script_id":"5461","0":"5461","script_name":"dutch_peasants","1":"dutch_peasants","script_type":"color scheme","2":"color scheme","summary":"A dark scheme of earth colours","3":"A dark scheme of earth colours","description":"A dark scheme of earth colours for Vim inspired by Adriaen van Ostade\u00e2\u0080\u0099s \u00e2\u0080\u009cPeasants in an Interior\u00e2\u0080\u009d (1661)","4":"A dark scheme of earth colours for Vim inspired by Adriaen van Ostade\u00e2\u0080\u0099s \u00e2\u0080\u009cPeasants in an Interior\u00e2\u0080\u009d (1661)","install_details":"Copy to ~\/.vim\/colors\r\n\u00e2\u0080\u0093 or \u00e2\u0080\u0093\r\nuse the GitHub repo 'kamwitsta\/dutch_peasants'","5":"Copy to ~\/.vim\/colors\r\n\u00e2\u0080\u0093 or \u00e2\u0080\u0093\r\nuse the GitHub repo 'kamwitsta\/dutch_peasants'","first_name":"kamil","6":"kamil","last_name":"stachowski","7":"stachowski","releases":[{"0":"5461","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"dutch_peasants.vim","4":"dutch_peasants.vim","src_id":"24616","5":"24616","creation_date":"1476196352","6":"1476196352"}]},"5460":{"script_id":"5460","0":"5460","script_name":"vim-markdown-toc","1":"vim-markdown-toc","script_type":"utility","2":"utility","summary":"A plugin to generate table of contents for Markdown files.","3":"A plugin to generate table of contents for Markdown files.","description":"In GitHub: https:\/\/github.com\/mzlogin\/vim-markdown-toc\r\n\r\n## Screenshots\r\n\r\nhttps:\/\/raw.githubusercontent.com\/mzlogin\/vim-markdown-toc\/master\/screenshots\/english.gif\r\nhttps:\/\/raw.githubusercontent.com\/mzlogin\/vim-markdown-toc\/master\/screenshots\/chinese.gif\r\n\r\n## Features\r\n\r\n* Generate table of contents for Markdown files.\r\n\r\n  Supported Markdown parsers:\r\n\r\n  - [x] GFM (GitHub Flavored Markdown)\r\n  - [x] GitLab\r\n  - [x] Marked\r\n  - [x] Redcarpet\r\n\r\n* Update existing table of contents.\r\n\r\n* Auto update existing table of contents on save.\r\n\r\nNote: This plugin only works in Markdown files, that usually have a .[md|mdown|mkd|mkdn|markdown|mdwn|mdx] suffix. To check file type, please run :set ft, Markdown files will echo filetype=markdown.\r\n\r\n## Usage\r\n\r\n### Generate table of contents\r\n\r\nMove the cursor to the line you want to append table of contents, then type a command below suit you. The command will generate **headings after the cursor** into table of contents.\r\n\r\n1. `:GenTocGFM`\r\n\r\n    Generate table of contents in [GFM][2] link style.\r\n\r\n    This command is suitable for Markdown files in GitHub repositories, like `README.md`, and Markdown files for GitBook.\r\n\r\n2. `:GenTocRedcarpet`\r\n\r\n    Generate table of contents in [Redcarpet][3] link style.\r\n\r\n    This command is suitable for Jekyll or anywhere else use Redcarpet as its Markdown parser.\r\n\r\n3. `:GenTocGitLab`\r\n\r\n    Generate table of contents in [GitLab][9] link style.\r\n\r\n    This command is suitable for GitLab repository and wiki.\r\n\r\n4. `:GenTocMarked`\r\n\r\n    Generate table of contents for [iamcco\/markdown-preview.vim][10] which use [Marked][11] markdown parser.\r\n\r\nYou can view [here][1] to know differences between *GFM* and *Redcarpet* style toc links.\r\n\r\n### Update existing table of contents\r\n\r\nGenerally you don't need to do this manually, existing table of contents will auto update on save by default.\r\n\r\nThe `:UpdateToc` command, which is designed to update toc manually, can only work when `g:vmt_auto_update_on_save` turned off, and keep insert fence.\r\n\r\n### Remove table of contents\r\n\r\n`:RemoveToc` command will do this for you, just remember keep insert fence option by default.\r\n\r\n## Options\r\n\r\n1. `g:vmt_auto_update_on_save`\r\n\r\n   default: `1`\r\n\r\n   This plugin will update existing table of contents on save automatic.\r\n\r\n   You can close this feature by add the following line to your vimrc file:\r\n\r\n   ```viml\r\n   let g:vmt_auto_update_on_save = 0\r\n   ```\r\n\r\n2. `g:vmt_dont_insert_fence`\r\n\r\n   default: `0`\r\n\r\n   By default, the `:GenTocXXX` commands will add `` fence to the table of contents, it is designed for feature of auto update table of contents on save and `:UpdateToc` command, it won't effect what your Markdown file looks like after parse.\r\n\r\n   If you don't like this, you can remove the fence by add the following line to your vimrc file:\r\n\r\n   ```viml\r\n   let g:vmt_dont_insert_fence = 1\r\n   ```\r\n\r\n   But then you will lose the convenience of auto update tables of contents on save and `:UpdateToc` command. When you want to update toc, you need to remove existing toc manually and rerun `:GenTocXXX` commands.\r\n\r\n3. `g:vmt_fence_text`\r\n\r\n   default: `vim-markdown-toc`\r\n\r\n   Inner text of the fence marker for the table of contents, see `g:vmt_dont_insert_fence`.\r\n\r\n4. `g:vmt_fence_closing_text`\r\n\r\n   default: `g:vmt_fence_text`\r\n\r\n   Inner text of the closing fence marker. E.g., you could `let g:vmt_fence_text = 'TOC'` and `let g:vmt_fence_closing_text = '\/TOC'` to get\r\n\r\n   ```\r\n   \r\n   [TOC]\r\n   \r\n   ```\r\n\r\n5. `g:vmt_fence_hidden_markdown_style`\r\n\r\n   default: `''`\r\n\r\n   By default, _vim-markdown-toc_ will add the markdown style into the fence of the text for the table of contents. You can avoid this and set a default markdown style with `g:vmt_fence_hidden_markdown_style` that is applied if a fence is found containing the `g:vmt_fence_text` without any markdown style. Obviously, `g:vmt_fence_hidden_markdown_style` has to be supported, i.e. currently one of `['GFM', 'Redcarpet', 'GitLab', 'Marked']`.\r\n\r\n6. `g:vmt_cycle_list_item_markers`\r\n\r\n   default: `0`\r\n\r\n   By default, `*` is used to denote every level of a list:\r\n\r\n   ```\r\n   * [Level 1](#level-1)\r\n       * [Level 1-1](#level-1-1)\r\n       * [Level 1-2](#level-1-2)\r\n           * [Level 1-2-1](#level-1-2-1)\r\n   * [Level 2](level-2)\r\n   ```\r\n\r\n   If you set:\r\n\r\n   ```viml\r\n   let g:vmt_cycle_list_item_markers = 1\r\n   ```\r\n\r\n   every level will instead cycle between the valid list item markers `*`, `-` and `+`:\r\n\r\n   ```\r\n   * [Level 1](#level-1)\r\n       - [Level 1-1](#level-1-1)\r\n       - [Level 1-2](#level-1-2)\r\n           + [Level 1-2-1](#level-1-2-1)\r\n   * [Level 2](level-2)\r\n   ```\r\n\r\n   This renders the same according to Markdown rules, but might appeal to those who care about readability of the source.\r\n\r\n7. `g:vmt_list_item_char`\r\n\r\n    default: `*`\r\n\r\n    The list item marker, it can be `*`, `-` or `+`.\r\n\r\n8. `g:vmt_include_headings_before`\r\n\r\n    default: `0`\r\n\r\n    Include headings before the position you are inserting Table of Contents.\r\n\r\n9. `g:vmt_list_indent_text`\r\n\r\n    default: `''`\r\n\r\n    The indent text of list item. By default, if `expandtab` is set, it will be `shiftwidth`([2, 5]) number of space, otherwise it will be `\\t`. If you set this option, it will override the default behavior.\r\n\r\n10. `g:vmt_link`\r\n\r\n    default: `1`\r\n\r\n    Whether to generate link for headings.\r\n\r\n11. `g:vmt_min_level`\r\n\r\n    default: `1`\r\n\r\n    The minimum level of headings to be included in the table of contents.\r\n\r\n12. `g:vmt_max_level`\r\n\r\n    default: `6`\r\n\r\n    The maximum level of headings to be included in the table of contents.","4":"In GitHub: https:\/\/github.com\/mzlogin\/vim-markdown-toc\r\n\r\n## Screenshots\r\n\r\nhttps:\/\/raw.githubusercontent.com\/mzlogin\/vim-markdown-toc\/master\/screenshots\/english.gif\r\nhttps:\/\/raw.githubusercontent.com\/mzlogin\/vim-markdown-toc\/master\/screenshots\/chinese.gif\r\n\r\n## Features\r\n\r\n* Generate table of contents for Markdown files.\r\n\r\n  Supported Markdown parsers:\r\n\r\n  - [x] GFM (GitHub Flavored Markdown)\r\n  - [x] GitLab\r\n  - [x] Marked\r\n  - [x] Redcarpet\r\n\r\n* Update existing table of contents.\r\n\r\n* Auto update existing table of contents on save.\r\n\r\nNote: This plugin only works in Markdown files, that usually have a .[md|mdown|mkd|mkdn|markdown|mdwn|mdx] suffix. To check file type, please run :set ft, Markdown files will echo filetype=markdown.\r\n\r\n## Usage\r\n\r\n### Generate table of contents\r\n\r\nMove the cursor to the line you want to append table of contents, then type a command below suit you. The command will generate **headings after the cursor** into table of contents.\r\n\r\n1. `:GenTocGFM`\r\n\r\n    Generate table of contents in [GFM][2] link style.\r\n\r\n    This command is suitable for Markdown files in GitHub repositories, like `README.md`, and Markdown files for GitBook.\r\n\r\n2. `:GenTocRedcarpet`\r\n\r\n    Generate table of contents in [Redcarpet][3] link style.\r\n\r\n    This command is suitable for Jekyll or anywhere else use Redcarpet as its Markdown parser.\r\n\r\n3. `:GenTocGitLab`\r\n\r\n    Generate table of contents in [GitLab][9] link style.\r\n\r\n    This command is suitable for GitLab repository and wiki.\r\n\r\n4. `:GenTocMarked`\r\n\r\n    Generate table of contents for [iamcco\/markdown-preview.vim][10] which use [Marked][11] markdown parser.\r\n\r\nYou can view [here][1] to know differences between *GFM* and *Redcarpet* style toc links.\r\n\r\n### Update existing table of contents\r\n\r\nGenerally you don't need to do this manually, existing table of contents will auto update on save by default.\r\n\r\nThe `:UpdateToc` command, which is designed to update toc manually, can only work when `g:vmt_auto_update_on_save` turned off, and keep insert fence.\r\n\r\n### Remove table of contents\r\n\r\n`:RemoveToc` command will do this for you, just remember keep insert fence option by default.\r\n\r\n## Options\r\n\r\n1. `g:vmt_auto_update_on_save`\r\n\r\n   default: `1`\r\n\r\n   This plugin will update existing table of contents on save automatic.\r\n\r\n   You can close this feature by add the following line to your vimrc file:\r\n\r\n   ```viml\r\n   let g:vmt_auto_update_on_save = 0\r\n   ```\r\n\r\n2. `g:vmt_dont_insert_fence`\r\n\r\n   default: `0`\r\n\r\n   By default, the `:GenTocXXX` commands will add `` fence to the table of contents, it is designed for feature of auto update table of contents on save and `:UpdateToc` command, it won't effect what your Markdown file looks like after parse.\r\n\r\n   If you don't like this, you can remove the fence by add the following line to your vimrc file:\r\n\r\n   ```viml\r\n   let g:vmt_dont_insert_fence = 1\r\n   ```\r\n\r\n   But then you will lose the convenience of auto update tables of contents on save and `:UpdateToc` command. When you want to update toc, you need to remove existing toc manually and rerun `:GenTocXXX` commands.\r\n\r\n3. `g:vmt_fence_text`\r\n\r\n   default: `vim-markdown-toc`\r\n\r\n   Inner text of the fence marker for the table of contents, see `g:vmt_dont_insert_fence`.\r\n\r\n4. `g:vmt_fence_closing_text`\r\n\r\n   default: `g:vmt_fence_text`\r\n\r\n   Inner text of the closing fence marker. E.g., you could `let g:vmt_fence_text = 'TOC'` and `let g:vmt_fence_closing_text = '\/TOC'` to get\r\n\r\n   ```\r\n   \r\n   [TOC]\r\n   \r\n   ```\r\n\r\n5. `g:vmt_fence_hidden_markdown_style`\r\n\r\n   default: `''`\r\n\r\n   By default, _vim-markdown-toc_ will add the markdown style into the fence of the text for the table of contents. You can avoid this and set a default markdown style with `g:vmt_fence_hidden_markdown_style` that is applied if a fence is found containing the `g:vmt_fence_text` without any markdown style. Obviously, `g:vmt_fence_hidden_markdown_style` has to be supported, i.e. currently one of `['GFM', 'Redcarpet', 'GitLab', 'Marked']`.\r\n\r\n6. `g:vmt_cycle_list_item_markers`\r\n\r\n   default: `0`\r\n\r\n   By default, `*` is used to denote every level of a list:\r\n\r\n   ```\r\n   * [Level 1](#level-1)\r\n       * [Level 1-1](#level-1-1)\r\n       * [Level 1-2](#level-1-2)\r\n           * [Level 1-2-1](#level-1-2-1)\r\n   * [Level 2](level-2)\r\n   ```\r\n\r\n   If you set:\r\n\r\n   ```viml\r\n   let g:vmt_cycle_list_item_markers = 1\r\n   ```\r\n\r\n   every level will instead cycle between the valid list item markers `*`, `-` and `+`:\r\n\r\n   ```\r\n   * [Level 1](#level-1)\r\n       - [Level 1-1](#level-1-1)\r\n       - [Level 1-2](#level-1-2)\r\n           + [Level 1-2-1](#level-1-2-1)\r\n   * [Level 2](level-2)\r\n   ```\r\n\r\n   This renders the same according to Markdown rules, but might appeal to those who care about readability of the source.\r\n\r\n7. `g:vmt_list_item_char`\r\n\r\n    default: `*`\r\n\r\n    The list item marker, it can be `*`, `-` or `+`.\r\n\r\n8. `g:vmt_include_headings_before`\r\n\r\n    default: `0`\r\n\r\n    Include headings before the position you are inserting Table of Contents.\r\n\r\n9. `g:vmt_list_indent_text`\r\n\r\n    default: `''`\r\n\r\n    The indent text of list item. By default, if `expandtab` is set, it will be `shiftwidth`([2, 5]) number of space, otherwise it will be `\\t`. If you set this option, it will override the default behavior.\r\n\r\n10. `g:vmt_link`\r\n\r\n    default: `1`\r\n\r\n    Whether to generate link for headings.\r\n\r\n11. `g:vmt_min_level`\r\n\r\n    default: `1`\r\n\r\n    The minimum level of headings to be included in the table of contents.\r\n\r\n12. `g:vmt_max_level`\r\n\r\n    default: `6`\r\n\r\n    The maximum level of headings to be included in the table of contents.","install_details":"Suggest to manage your vim plugins via [vim-plug][8] or [Vundle][4], so you can install it simply three steps:\r\n\r\n### vim-plug\r\n\r\n1. add the following line to your vimrc file\r\n\r\n    ```\r\n    Plug 'mzlogin\/vim-markdown-toc'\r\n    ```\r\n\r\n2. `:so $MYVIMRC`\r\n\r\n3. `:PlugInstall`\r\n\r\n### Vundle\r\n\r\n1. add the following line to your vimrc file\r\n\r\n    ```\r\n    Plugin 'mzlogin\/vim-markdown-toc'\r\n    ```\r\n\r\n2. `:so $MYVIMRC`\r\n\r\n3. `:PluginInstall`","5":"Suggest to manage your vim plugins via [vim-plug][8] or [Vundle][4], so you can install it simply three steps:\r\n\r\n### vim-plug\r\n\r\n1. add the following line to your vimrc file\r\n\r\n    ```\r\n    Plug 'mzlogin\/vim-markdown-toc'\r\n    ```\r\n\r\n2. `:so $MYVIMRC`\r\n\r\n3. `:PlugInstall`\r\n\r\n### Vundle\r\n\r\n1. add the following line to your vimrc file\r\n\r\n    ```\r\n    Plugin 'mzlogin\/vim-markdown-toc'\r\n    ```\r\n\r\n2. `:so $MYVIMRC`\r\n\r\n3. `:PluginInstall`","first_name":"Ma","6":"Ma","last_name":"Zhuang","7":"Zhuang","releases":[{"0":"5460","vim_version":"7.4","1":"7.4","script_version":"v1.5.0","2":"v1.5.0","version_comment":"- Compatibility improvments\r\n- Complete documentation","3":"- Compatibility improvments\r\n- Complete documentation","package":"vim-markdown-toc-1.5.0.zip","4":"vim-markdown-toc-1.5.0.zip","src_id":"28669","5":"28669","creation_date":"1713149020","6":"1713149020"},{"0":"5460","vim_version":"7.4","1":"7.4","script_version":"v1.4.0","2":"v1.4.0","version_comment":"Make the TOC fence text be configurable, support assign markdown style in modeline.","3":"Make the TOC fence text be configurable, support assign markdown style in modeline.","package":"vim-markdown-toc-1.4.0.tar.gz","4":"vim-markdown-toc-1.4.0.tar.gz","src_id":"25976","5":"25976","creation_date":"1526054937","6":"1526054937"},{"0":"5460","vim_version":"7.4","1":"7.4","script_version":"1.3.0","2":"1.3.0","version_comment":"Add support for GitLab, add option `list_indent_text`, add support for Cyrillic in headings","3":"Add support for GitLab, add option `list_indent_text`, add support for Cyrillic in headings","package":"vim-markdown-toc-1.3.0.tar.gz","4":"vim-markdown-toc-1.3.0.tar.gz","src_id":"25662","5":"25662","creation_date":"1511796216","6":"1511796216"},{"0":"5460","vim_version":"7.0","1":"7.0","script_version":"v1.2.2","2":"v1.2.2","version_comment":"Add option to cycle list item markers, add command to remove toc","3":"Add option to cycle list item markers, add command to remove toc","package":"vim-markdown-toc-1.2.2.tar.gz","4":"vim-markdown-toc-1.2.2.tar.gz","src_id":"25512","5":"25512","creation_date":"1502848857","6":"1502848857"},{"0":"5460","vim_version":"7.0","1":"7.0","script_version":"v1.2.1","2":"v1.2.1","version_comment":"Compatible with old regexp engine.","3":"Compatible with old regexp engine.","package":"vim-markdown-toc-1.2.1.tar.gz","4":"vim-markdown-toc-1.2.1.tar.gz","src_id":"24760","5":"24760","creation_date":"1479872498","6":"1479872498"},{"0":"5460","vim_version":"7.0","1":"7.0","script_version":"v1.2","2":"v1.2","version_comment":"Compatibility enhancement","3":"Compatibility enhancement","package":"vim-markdown-toc-1.2.tar.gz","4":"vim-markdown-toc-1.2.tar.gz","src_id":"24707","5":"24707","creation_date":"1478489270","6":"1478489270"},{"0":"5460","vim_version":"7.0","1":"7.0","script_version":"v1.0","2":"v1.0","version_comment":"Add features: update existing toc, auto update toc on save.","3":"Add features: update existing toc, auto update toc on save.","package":"vim-markdown-toc-1.0.tar.gz","4":"vim-markdown-toc-1.0.tar.gz","src_id":"24650","5":"24650","creation_date":"1476855205","6":"1476855205"},{"0":"5460","vim_version":"7.0","1":"7.0","script_version":"v0.1","2":"v0.1","version_comment":"Initial upload","3":"Initial upload","package":"vim-markdown-toc-0.1.tar.gz","4":"vim-markdown-toc-0.1.tar.gz","src_id":"24610","5":"24610","creation_date":"1476120888","6":"1476120888"}]},"5459":{"script_id":"5459","0":"5459","script_name":"syntax for verilog 2001","1":"syntax for verilog 2001","script_type":"syntax","2":"syntax","summary":"set vim for verilog","3":"set vim for verilog","description":"au BufNewFile,BufRead *.vt set filetype=verilog \r\nset fileencodings=utf8\r\nset fileformat=unix\r\nsyntax on\r\nset nu\r\nset ruler\r\nset shortmess=atI\r\nset expandtab  \r\nset smarttab  \r\nset shiftwidth=4  \r\nset tabstop=4\r\n\r\nmap  :s\/\\s\\+$\/\/                             \"delete line space\r\nmap  :s\/\\s\\+$\/\/:wq               \"delete line space save and quit\r\nmap!  \/\/                                                 \"mark\r\n\r\n\r\n \"automatic completion symbol\r\ninoremap ( ()i         \r\ninoremap [ []i\r\ninoremap { {}i\r\ninoremap < <>i\r\n","4":"au BufNewFile,BufRead *.vt set filetype=verilog \r\nset fileencodings=utf8\r\nset fileformat=unix\r\nsyntax on\r\nset nu\r\nset ruler\r\nset shortmess=atI\r\nset expandtab  \r\nset smarttab  \r\nset shiftwidth=4  \r\nset tabstop=4\r\n\r\nmap  :s\/\\s\\+$\/\/                             \"delete line space\r\nmap  :s\/\\s\\+$\/\/:wq               \"delete line space save and quit\r\nmap!  \/\/                                                 \"mark\r\n\r\n\r\n \"automatic completion symbol\r\ninoremap ( ()i         \r\ninoremap [ []i\r\ninoremap { {}i\r\ninoremap < <>i\r\n","install_details":"make file .vimrc;copy these to it.","5":"make file .vimrc;copy these to it.","first_name":"homway","6":"homway","last_name":"cheng","7":"cheng","releases":[{"0":"5459","vim_version":"7.3","1":"7.3","script_version":"0.2.1","2":"0.2.1","version_comment":"add description","3":"add description","package":".vimrc","4":".vimrc","src_id":"24660","5":"24660","creation_date":"1477094937","6":"1477094937"},{"0":"5459","vim_version":"7.3","1":"7.3","script_version":"0.2","2":"0.2","version_comment":" add automatic completion symbol","3":" add automatic completion symbol","package":"setvim.txt","4":"setvim.txt","src_id":"24635","5":"24635","creation_date":"1476633119","6":"1476633119"},{"0":"5459","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"setvim.txt","4":"setvim.txt","src_id":"24607","5":"24607","creation_date":"1476026048","6":"1476026048"}]},"5458":{"script_id":"5458","0":"5458","script_name":"vim_comment_toggle","1":"vim_comment_toggle","script_type":"ftplugin","2":"ftplugin","summary":"Simple and lightweight comment toggle scripts","3":"Simple and lightweight comment toggle scripts","description":"A very simple and lightweight way to toggle comments on one or more lines.  It works in normal mode and visual mode.\r\n\r\nBy default, the toggle is mapped to  but can be easily changed.\r\n\r\nFiles included for: C, C++, Python, Erlang, shell scripts.\r\n\r\nCurrently, only one comment type is supported at a time. If a different file type is loaded in the same Vim session, then a warning is given and the keys are not remapped. I'll be looking into making it smarter in the future as long as it stays simple.\r\n\r\nhttps:\/\/github.com\/WarpEngineer\/vim_comment_toggle\r\n","4":"A very simple and lightweight way to toggle comments on one or more lines.  It works in normal mode and visual mode.\r\n\r\nBy default, the toggle is mapped to  but can be easily changed.\r\n\r\nFiles included for: C, C++, Python, Erlang, shell scripts.\r\n\r\nCurrently, only one comment type is supported at a time. If a different file type is loaded in the same Vim session, then a warning is given and the keys are not remapped. I'll be looking into making it smarter in the future as long as it stays simple.\r\n\r\nhttps:\/\/github.com\/WarpEngineer\/vim_comment_toggle\r\n","install_details":"Just copy the scripts to ~\/.vim\/ftplugin or just add the 'ToggleComment()' function and key maps in the files to files that are already in the 'ftplugin' directory.","5":"Just copy the scripts to ~\/.vim\/ftplugin or just add the 'ToggleComment()' function and key maps in the files to files that are already in the 'ftplugin' directory.","first_name":"A. G.","6":"A. G.","last_name":"Madi","7":"Madi","releases":[{"0":"5458","vim_version":"7.0","1":"7.0","script_version":"1.1.2","2":"1.1.2","version_comment":"Added a check to keep different file types from remapping the keys.","3":"Added a check to keep different file types from remapping the keys.","package":"vim_comment_toggle.zip","4":"vim_comment_toggle.zip","src_id":"24718","5":"24718","creation_date":"1478744509","6":"1478744509"},{"0":"5458","vim_version":"7.0","1":"7.0","script_version":"1.1.1","2":"1.1.1","version_comment":"Added a file for shell scripts.","3":"Added a file for shell scripts.","package":"vim_comment_toggle.zip","4":"vim_comment_toggle.zip","src_id":"24641","5":"24641","creation_date":"1476715013","6":"1476715013"},{"0":"5458","vim_version":"7.0","1":"7.0","script_version":"1.1","2":"1.1","version_comment":"Made uncommenting smarter in that the comment character does not have to\r\nbe in the first postion.","3":"Made uncommenting smarter in that the comment character does not have to\r\nbe in the first postion.","package":"vim_comment_toggle.zip","4":"vim_comment_toggle.zip","src_id":"24605","5":"24605","creation_date":"1475983201","6":"1475983201"}]},"5457":{"script_id":"5457","0":"5457","script_name":"vim-tail","1":"vim-tail","script_type":"utility","2":"utility","summary":"Makes vim behave like tail -f","3":"Makes vim behave like tail -f","description":"Vim Tail\r\n==============================================================================\r\n\r\nThis is a simple small plugin to tail an opened file. Once you run the\r\n`TailStart` command, the current buffer will be checked every second for\r\nchanges. If a change is detected, then the file is reloaded and the cursor is\r\nplaced at the end of the file (`normal G`). \r\n\r\nIt would behave basically like `tail -f` on a file. \r\n\r\nThere are 2 commands: `TailStart` will start tailing a file and `TailStop`\r\nwill stop watching the file\r\n\r\nGithub link here: https:\/\/github.com\/cosminadrianpopescu\/vim-tail","4":"Vim Tail\r\n==============================================================================\r\n\r\nThis is a simple small plugin to tail an opened file. Once you run the\r\n`TailStart` command, the current buffer will be checked every second for\r\nchanges. If a change is detected, then the file is reloaded and the cursor is\r\nplaced at the end of the file (`normal G`). \r\n\r\nIt would behave basically like `tail -f` on a file. \r\n\r\nThere are 2 commands: `TailStart` will start tailing a file and `TailStop`\r\nwill stop watching the file\r\n\r\nGithub link here: https:\/\/github.com\/cosminadrianpopescu\/vim-tail","install_details":"","5":"","first_name":"Cosmin","6":"Cosmin","last_name":"Popescu","7":"Popescu","releases":[{"0":"5457","vim_version":"8.0","1":"8.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"vim-tail.tar.gz","4":"vim-tail.tar.gz","src_id":"24590","5":"24590","creation_date":"1475866623","6":"1475866623"}]},"5456":{"script_id":"5456","0":"5456","script_name":"lilycomment.vim","1":"lilycomment.vim","script_type":"utility","2":"utility","summary":"comment plugin for csharp","3":"comment plugin for csharp","description":"lilycomment.vim\r\n\r\nlilycomment is comment plugin for csharp.\r\nOne day, I searched comment plugin. But the one is not in the net.\r\nSo I made this. What I write in the other?\r\n\r\nRequirement\r\n\r\nThis plugin is used lambda function.\r\nYES! It's function was implemented in Vim 8.0.\r\nSO YOU NEED TO UPDATE VIM 8.0!\r\n\r\nInstall\r\n\r\nPLZ use plugin-manager. if you use NeoBundle,\r\n\r\nNeobundle 'hananana\/lilycomment.vim'\r\nOops, you love junegunn? Me to. vim-plug is cool.\r\n\r\nPlug 'hananana\/lilycomment.vim'\r\nAs you like.\r\n\r\nCommands\r\n\r\n:LilyComment\r\n\r\nInsert Comment with tags.\r\n\r\nExample\r\n\r\n\/\/\/\r\n\/\/\/\r\n\/\/\/<\/summary>\r\npublic class Hoge\r\n{\r\n    \/\/\/\r\n    \/\/\/\r\n    \/\/\/<\/summary>\r\n    \/\/\/ foo <\/param>\r\n    \/\/\/ bar <\/param>\r\n    \/\/\/ <\/return>\r\n    string DoSomething(int foo, string bar)\r\n    {\r\n\r\n    }\r\n}","4":"lilycomment.vim\r\n\r\nlilycomment is comment plugin for csharp.\r\nOne day, I searched comment plugin. But the one is not in the net.\r\nSo I made this. What I write in the other?\r\n\r\nRequirement\r\n\r\nThis plugin is used lambda function.\r\nYES! It's function was implemented in Vim 8.0.\r\nSO YOU NEED TO UPDATE VIM 8.0!\r\n\r\nInstall\r\n\r\nPLZ use plugin-manager. if you use NeoBundle,\r\n\r\nNeobundle 'hananana\/lilycomment.vim'\r\nOops, you love junegunn? Me to. vim-plug is cool.\r\n\r\nPlug 'hananana\/lilycomment.vim'\r\nAs you like.\r\n\r\nCommands\r\n\r\n:LilyComment\r\n\r\nInsert Comment with tags.\r\n\r\nExample\r\n\r\n\/\/\/\r\n\/\/\/\r\n\/\/\/<\/summary>\r\npublic class Hoge\r\n{\r\n    \/\/\/\r\n    \/\/\/\r\n    \/\/\/<\/summary>\r\n    \/\/\/ foo <\/param>\r\n    \/\/\/ bar <\/param>\r\n    \/\/\/ <\/return>\r\n    string DoSomething(int foo, string bar)\r\n    {\r\n\r\n    }\r\n}","install_details":"","5":"","first_name":"hana","6":"hana","last_name":"nana","7":"nana","releases":[{"0":"5456","vim_version":"8.0","1":"8.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"lilycomment.vim.zip","4":"lilycomment.vim.zip","src_id":"24583","5":"24583","creation_date":"1475648287","6":"1475648287"}]},"5452":{"script_id":"5452","0":"5452","script_name":"Buffy.vim","1":"Buffy.vim","script_type":"utility","2":"utility","summary":"Switch between buffers with a handy menu","3":"Switch between buffers with a handy menu","description":"Buffy is a text menu (one item per line) consisting of names of currently edited files from all buffers.\r\n\r\nUpon stepping on an item (file name) in the Buffy menu and pressing  key, the buffer with the chosen file will be placed into a current window. To delete a chosen buffer, press x or d.\r\n\r\nBuffy may be invoked inside any window with the :Buffy command. That command may be bound to a key combination. By default, :Buffy is bound to b.\r\n\r\nIf you prefer a different key combination, make sure to disable the default binding first:\r\n\r\n    let g:buffy_default_key_binding = 0\r\n    nnoremap  :Buffy\r\n\r\n\r\nLatest version of Buffy.vim may be found in its Github repo:\r\n\r\n    https:\/\/github.com\/mcmlxxxiii\/Buffy.vim","4":"Buffy is a text menu (one item per line) consisting of names of currently edited files from all buffers.\r\n\r\nUpon stepping on an item (file name) in the Buffy menu and pressing  key, the buffer with the chosen file will be placed into a current window. To delete a chosen buffer, press x or d.\r\n\r\nBuffy may be invoked inside any window with the :Buffy command. That command may be bound to a key combination. By default, :Buffy is bound to b.\r\n\r\nIf you prefer a different key combination, make sure to disable the default binding first:\r\n\r\n    let g:buffy_default_key_binding = 0\r\n    nnoremap  :Buffy\r\n\r\n\r\nLatest version of Buffy.vim may be found in its Github repo:\r\n\r\n    https:\/\/github.com\/mcmlxxxiii\/Buffy.vim","install_details":"Buffy is pathogen-compatible. Just unpack the archive into ~\/.vim\/bundle or git clone it there. Then restart Vim.\r\n\r\ngit clone https:\/\/github.com\/mcmlxxxiii\/Buffy.vim.git ~\/.vim\/bundle\/Buffy","5":"Buffy is pathogen-compatible. Just unpack the archive into ~\/.vim\/bundle or git clone it there. Then restart Vim.\r\n\r\ngit clone https:\/\/github.com\/mcmlxxxiii\/Buffy.vim.git ~\/.vim\/bundle\/Buffy","first_name":"M","6":"M","last_name":"G","7":"G","releases":[{"0":"5452","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"buffy-0.1.tar.gz","4":"buffy-0.1.tar.gz","src_id":"24557","5":"24557","creation_date":"1474742523","6":"1474742523"}]},"5451":{"script_id":"5451","0":"5451","script_name":"vim-seattle","1":"vim-seattle","script_type":"color scheme","2":"color scheme","summary":"An elegant yet efficient color scheme for coders","3":"An elegant yet efficient color scheme for coders","description":"Features\r\n\r\nDecent contrast - not too high and not too low, good for eyes and easy to read.\r\nBeautiful colors - in my opinion.\r\nCterm colors offline generator - change the RGB value and generate cterm 256 colors, simple.\r\nColor palette for customization - never been so easy.\r\nSyntax highlight preview - WYSIWYG\r\n\r\nPlease visit https:\/\/github.com\/mbbill\/vim-seattle for more information.","4":"Features\r\n\r\nDecent contrast - not too high and not too low, good for eyes and easy to read.\r\nBeautiful colors - in my opinion.\r\nCterm colors offline generator - change the RGB value and generate cterm 256 colors, simple.\r\nColor palette for customization - never been so easy.\r\nSyntax highlight preview - WYSIWYG\r\n\r\nPlease visit https:\/\/github.com\/mbbill\/vim-seattle for more information.","install_details":"You know how.","5":"You know how.","first_name":"Ming","6":"Ming","last_name":"Bai","7":"Bai","releases":[{"0":"5451","vim_version":"5.7","1":"5.7","script_version":"1.1","2":"1.1","version_comment":"No longer requires vim8.0","3":"No longer requires vim8.0","package":"vim-seattle-release_1.1.tar.gz","4":"vim-seattle-release_1.1.tar.gz","src_id":"24556","5":"24556","creation_date":"1474738903","6":"1474738903"},{"0":"5451","vim_version":"7.4","1":"7.4","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"vim-seattle-release_1.0.tar.gz","4":"vim-seattle-release_1.0.tar.gz","src_id":"24537","5":"24537","creation_date":"1474245828","6":"1474245828"}]},"5450":{"script_id":"5450","0":"5450","script_name":"unicon","1":"unicon","script_type":"color scheme","2":"color scheme","summary":"uniform contrast light and dark colorscheme","3":"uniform contrast light and dark colorscheme","description":"Official repository: https:\/\/github.com\/andbar-ru\/vim-unicon\r\n\r\nScreenshots and last updates on the official repo.\r\n\r\nUnicon is inspired by solarized (https:\/\/github.com\/altercation\/vim-colors-solarized), gruvbox (https:\/\/github.com\/morhetz\/gruvbox) and lucius (https:\/\/github.com\/jonathanfilip\/vim-lucius). It has light and dark variants and supports GUI and 256-color terminals.\r\n\r\nI like the ideas solarized based on, but was not satisfied with the implementation because of very low contrast. That was the main reason for creating this colorscheme. Palette for unicon was created to provide increased and really even contrast with background. Accent colors are different for light and dark variants. You can toggle between variants with commands:\r\n\r\nset bg=dark\r\nset bg=light","4":"Official repository: https:\/\/github.com\/andbar-ru\/vim-unicon\r\n\r\nScreenshots and last updates on the official repo.\r\n\r\nUnicon is inspired by solarized (https:\/\/github.com\/altercation\/vim-colors-solarized), gruvbox (https:\/\/github.com\/morhetz\/gruvbox) and lucius (https:\/\/github.com\/jonathanfilip\/vim-lucius). It has light and dark variants and supports GUI and 256-color terminals.\r\n\r\nI like the ideas solarized based on, but was not satisfied with the implementation because of very low contrast. That was the main reason for creating this colorscheme. Palette for unicon was created to provide increased and really even contrast with background. Accent colors are different for light and dark variants. You can toggle between variants with commands:\r\n\r\nset bg=dark\r\nset bg=light","install_details":"Put colors\/unicon.vim to ~\/.vim\/colors\/\r\nor  better use any plugin manager: vim-plug, NeoBundle, Vundle or Pathogen.\r\nTo enable colorscheme insert command:\r\n\r\n:colorscheme unicon\r\n\r\nor write down to ~\/.vimrc:\r\n\r\nset background=light  \" or dark\r\ncolorscheme unicon\r\n\r\nIf your terminal supports true colors you may add the following line to ~\/.vimrc before setting colorscheme:\r\n\r\nset termguicolors\r\n\r\n\r\n","5":"Put colors\/unicon.vim to ~\/.vim\/colors\/\r\nor  better use any plugin manager: vim-plug, NeoBundle, Vundle or Pathogen.\r\nTo enable colorscheme insert command:\r\n\r\n:colorscheme unicon\r\n\r\nor write down to ~\/.vimrc:\r\n\r\nset background=light  \" or dark\r\ncolorscheme unicon\r\n\r\nIf your terminal supports true colors you may add the following line to ~\/.vimrc before setting colorscheme:\r\n\r\nset termguicolors\r\n\r\n\r\n","first_name":"Andrey","6":"Andrey","last_name":"Bartashevitch","7":"Bartashevitch","releases":[{"0":"5450","vim_version":"7.0","1":"7.0","script_version":"2.2.0","2":"2.2.0","version_comment":"Highlight SignColumn as LineNr","3":"Highlight SignColumn as LineNr","package":"vim-unicon.zip","4":"vim-unicon.zip","src_id":"27387","5":"27387","creation_date":"1606628213","6":"1606628213"},{"0":"5450","vim_version":"7.3","1":"7.3","script_version":"2.1.0","2":"2.1.0","version_comment":"Pale cyan background for Search","3":"Pale cyan background for Search","package":"vim-unicon.zip","4":"vim-unicon.zip","src_id":"26470","5":"26470","creation_date":"1556472884","6":"1556472884"},{"0":"5450","vim_version":"7.0","1":"7.0","script_version":"2.0.0","2":"2.0.0","version_comment":"Extra colors for diff mode.","3":"Extra colors for diff mode.","package":"vim-unicon.zip","4":"vim-unicon.zip","src_id":"26428","5":"26428","creation_date":"1553294980","6":"1553294980"},{"0":"5450","vim_version":"7.3","1":"7.3","script_version":"1.2","2":"1.2","version_comment":"Take into account 'termguicolors' setting","3":"Take into account 'termguicolors' setting","package":"vim-unicon.zip","4":"vim-unicon.zip","src_id":"25688","5":"25688","creation_date":"1512502597","6":"1512502597"},{"0":"5450","vim_version":"7.3","1":"7.3","script_version":"1.1","2":"1.1","version_comment":"Fixed bug with allocating cterm colors to guisp in terminal","3":"Fixed bug with allocating cterm colors to guisp in terminal","package":"vim-unicon.zip","4":"vim-unicon.zip","src_id":"25347","5":"25347","creation_date":"1498420042","6":"1498420042"},{"0":"5450","vim_version":"7.3","1":"7.3","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"vim-unicon.zip","4":"vim-unicon.zip","src_id":"24536","5":"24536","creation_date":"1474202696","6":"1474202696"}]},"5449":{"script_id":"5449","0":"5449","script_name":"ALE - Asynchronous Lint Engine","1":"ALE - Asynchronous Lint Engine","script_type":"utility","2":"utility","summary":"Lint while you type in Vim","3":"Lint while you type in Vim","description":"The latest version is available here: https:\/\/github.com\/w0rp\/ale\r\n\r\nNOTE: New versions are no longer uploaded here. Please download releases from the GitHub releases page instead.\r\n\r\nThis plugin adds the ability to automatically lint code while you edit in Vim. This plugin requires Vim 8.0 or above to run, or NeoVim, as it requires the asynchronous job and timer features. Errors to echo in a status line, signs, and loclist items should appear whenever files are opened or text is changed in a buffer automatically for all supported languages and tools.\r\n\r\nSee the GitHub page for the current list of supported languages and tools.","4":"The latest version is available here: https:\/\/github.com\/w0rp\/ale\r\n\r\nNOTE: New versions are no longer uploaded here. Please download releases from the GitHub releases page instead.\r\n\r\nThis plugin adds the ability to automatically lint code while you edit in Vim. This plugin requires Vim 8.0 or above to run, or NeoVim, as it requires the asynchronous job and timer features. Errors to echo in a status line, signs, and loclist items should appear whenever files are opened or text is changed in a buffer automatically for all supported languages and tools.\r\n\r\nSee the GitHub page for the current list of supported languages and tools.","install_details":"Copy the contents of the archive somewhere in your Vim runtimepath, or install the plugin via the GitHub link for the latest version with your preferred Vim script installation tool.","5":"Copy the contents of the archive somewhere in your Vim runtimepath, or install the plugin via the GitHub link for the latest version with your preferred Vim script installation tool.","first_name":"w0rp","6":"w0rp","last_name":" ","7":" ","releases":[{"0":"5449","vim_version":"8.0","1":"8.0","script_version":"1.7.1","2":"1.7.1","version_comment":"## Bugs Fixed\r\n\r\n* `rustfmt` will now apply project settings correctly by using stdin and stdout instead. #1254 \r\n* The extra arguments are now passed to `clang-check` correctly. #1255 \r\n* ALE now supports running commands on Windows when the shell is PowerShell. #1298\r\n* Rust errors will now use the correct column numbers instead of byte offsets. #1322 \r\n* `isort` configuration files will now be detected more accurately by changing the working directory instead of setting the configuration file. #1330 ","3":"## Bugs Fixed\r\n\r\n* `rustfmt` will now apply project settings correctly by using stdin and stdout instead. #1254 \r\n* The extra arguments are now passed to `clang-check` correctly. #1255 \r\n* ALE now supports running commands on Windows when the shell is PowerShell. #1298\r\n* Rust errors will now use the correct column numbers instead of byte offsets. #1322 \r\n* `isort` configuration files will now be detected more accurately by changing the working directory instead of setting the configuration file. #1330 ","package":"vim-ale.1.7.1.zip","4":"vim-ale.1.7.1.zip","src_id":"25839","5":"25839","creation_date":"1519569504","6":"1519569504"},{"0":"5449","vim_version":"8.0","1":"8.0","script_version":"1.7.0","2":"1.7.0","version_comment":"## Bugs Fixed\r\n\r\n* ALE will now find files relative to buffers in cygwin. #1180 #1181\r\n* The temporary file for TSLint was being mentioned sometimes in the quickfix list.  #1210\r\n* ALE will now suppress trailing whitespace warnings for `ansible-lint` when the option is on. #1216\r\n* Relative and absolute paths are now resolved better on Windows. #1210\r\n* ALE no longer moves the cursor slightly when briefly escaping insert mode and echoing a message. #1228\r\n\r\n## New Features\r\n\r\n* ALE linting can now be toggled for particular buffers. See `:help ALEToggleBuffer`. #817\r\n* Problems reported by ALE can now be removed with `ALEReset` or `ALEResetBuffer`. #719 \r\n* `b:ale_fix_on_save` can now be used for controlling fixing on save for specific buffers. #857 \r\n* Fixer functions can now be chained, much like linters. #1086 \r\n* Fixer functions can now specify callbacks for post-processing command output.\r\n* Reading the buffer via stdin can now be disabled for fixer commands with `'read_buffer': 0`, just like linters.\r\n* `b:ale_fixers` can now be set to a `List`. #1108\r\n* `b:ale_linters` can now be set to a `List`. #1108\r\n* `b:ale_linters` can now be set to `'all'`. #1108\r\n* `b:ale_linter_aliases` can now be set to a `List`. #1108 \r\n* ALE will now show the echoed severity for type `'I'` problems as `'Info'`.\r\n* ALE now supports formatting echo messages with error codes. #852\r\n* Several linters have now been updated so the error codes are configurable. #852 \r\n* The echo message format can now be configured differently for different buffers. See `:help b:ale_echo_msg_format`\r\n* Messages for loclist and the quickfix list can now be formatted like echoed messages. See  `:help g:ale_loclist_msg_format` #1069 #852\r\n* ALE linters can now be configured to only be enabled explicitly. See `:help g:ale_linters_explicit` #1128\r\n* `:ALEDetail` will now show messages in a preview window. #757\r\n* Line highlights will now be set when signs are disabled. #741\r\n* ALE now supports jumping to definitions for LSP and tsserver linters. See `:help ale-go-to-definition`.\r\n* Warnings about trailing blank lines can be disabled for some linters. See `:help g:ale_warn_about_trailing_blank_lines`. \r\n* Failing executable checks may now be cached with `let g:ale_cache_executable_check_failures = 1` #1176\r\n* An autocmd command `ALELintPre` has been added for running code just before ALE starts linting.\r\n\r\n## Other Changes\r\n\r\n* ALE will no longer modify `runtimepath` when `g:ale_emit_conflict_warnings` is set to `0`.  #1049\r\n* ALE should no longer mess with folds when `ALELint` autocmd commands are set. #1062\r\n* ALE will no longer send an `id` `key` for the LSP notification messages at all, instead of `v:null`. #1110\r\n* Output will now be ignored for fixer commands which output only whitespace.\r\n* When ALE deletes lines as the result of fixing files, the deleted lines will be put in the black hole register. #1165\r\n* `tsserver` completions will now be requested again after completion is done only if the cursor moves, rather than waiting for 100ms. #1041\r\n* The `perl` linter is now disabled by default, as it can execute malicious code. #1186\r\n* The `ALELint` autocmd has been renamed to `ALELintPost`, but the old commands will still be run until version 2.0. On version 2.0, `ALELint` commands will probably be removed.\r\n* ALE will now look for `mypy.ini` files for finding Python project roots.\r\n* ALE will now look for `venv` for finding virtualenv directories by default. #1237\r\n* Cursor messages can now be disabled while Vim is running.\r\n* ALE now cleans up buffer data when buffers are deleted instead of unloaded, so the quickfix list can be maintained.\r\n\r\n## New Linters\r\n\r\n* AsciiDoc - `alex` #1220, `redpen` #1142, `write-good` #643 #811 \r\n* API Blueprint - `drafter` #1152 \r\n* Clojure - `joker` #1133\r\n* Dafny - `dafny` #1093\r\n* Dart - `dart_language_server` #1006\r\n* GLSL - `glslls` #1179\r\n* GraphQL - `eslint`  #1169\r\n* HTML - `alex` #1220, `write-good` #643 #811\r\n* LaTeX - `alex` #1220, `redpen` #1142, `vale` #1230, `write-good` #643 #811\r\n* LESS - `lessc` #1103, `stylelint` #510\r\n* mail - `alex` #1220, `proselint` #1037, `vale` #1044\r\n* Markdown - `alex` #1220, `redpen`  #1137, `write-good` #643 #811\r\n* nroff - `alex` #1220, `write-good` #643 #811 \r\n* OCaml - `ols` #1110\r\n* PHP - `phan` #1026 \r\n* Pod - `alex` #1220, `write-good` #643 #811 \r\n* proto - `protoc-gen-lint` #1098\r\n* Python - `prospector` #565 #1183, `pyflakes` #516, `PyLS` #1097\r\n* Solidarity - `solhint` #1192\r\n* ReasonML - `ols` #1110\r\n* reStructuredText - `alex` #1220, `redpen` #1142, `rstcheck` #1090, `vale` #1230, `write-good` #643 #811 \r\n* Re:VIEW - `redpen` #1142\r\n* Terraform - `tflint` #1046\r\n* Texinfo - `alex` #1220, `write-good` #643 #811\r\n* text - `alex` #1220, `redpen` #1142, `write-good` #643 #811\r\n* Vim help - `alex` #1220, `write-good` #643 #811 \r\n* XHTML - `alex` #1220, `write-good` #643 #811 \r\n\r\n## New Fixers\r\n\r\n* Elixir - `mix format` #1017 \r\n* Go - `goimports` #1123\r\n* Hack - `hackfmt` #1053\r\n* Haskell - `brittany`  #1174, `hfmt` #1027 \r\n* Java - `google-java-format` #1209\r\n* JavaScript - `importjs` #1191\r\n* ReasonML - `refmt` #1059\r\n* Rust - `rustfmt` #1025 \r\n* Shell - `shfmt` #1083\r\n\r\n## Linter Enhancements\r\n\r\n* ALE now captures problems for other files for GCC, clang, and related tools. #1023 \r\n* The `rubocop` and `haml-lint` configuration files will be now used for `ham-lint` automatically. #1047 \r\n* The `shellcheck` linter will now use `-x` and follow sourced files when checking for errors. #491\r\n* The `shellcheck` linter now uses the type `'I'` for notes. #1122\r\n* The `phpcs` linter will now include the error code in the message. #1009\r\n* Errors for missing ESLint configuration files can now be disabled. See `:help g:ale_javascript_eslint_suppress_missing_config`. #971\r\n* `cargo check` and `cargo check --all-targets` will now automatically be used when `cargo` is new enough. `g:ale_rust_cargo_use_check` or `g:ale_rust_cargo_check_all_targets` can be set to disable either.  #626 \r\n* The `phpmd` executable can now be configured, and error checking should be more reliable. #1076\r\n* The `flow` linter will now include more information for errors in the `:ALEDetail` message. #946\r\n* Error codes can now be configured for messages from ESLint.  #852\r\n* Error codes can now be configured for messages from TSLint.  #852\r\n* Error codes can now be configured for messages from flake8.  #852\r\n* Error codes can now be configured for messages from rubocop.  #852\r\n* Error codes can now be configured for messages from ansible-lint.  #852 \r\n* Error codes can now be configured for messages from cpplint.  #852 \r\n* Error codes can now be configured for messages from shellcheck.  #852 \r\n* Error codes can now be configured for messages from pylint.  #852 \r\n* Error codes can now be configured for messages from checkmake. #852 #1135\r\n* Error codes can now be configured for messages from checkstyle. #852\r\n* Error codes can now be configured for messages from pycodestyle.  #852 \r\n* Error codes can now be configured for messages from csslint.  #852\r\n* Error codes can now be configured for messages from jscs.  #852\r\n* Error codes can now be configured for messages from luacheck.  #852\r\n* Error codes can now be configured for messages from mcs and mcsc.  #852\r\n* Error codes can now be configured for messages from nimcheck.  #852\r\n* Error codes can now be configured for messages from reek.  #852\r\n* Error codes can now be configured for messages from slim-lint.  #852\r\n* Error codes can now be configured for messages from stylelint.  #852\r\n* Error codes can now be configured for messages from swaglint.  #852\r\n* Error codes can now be configured for messages from swiftlint.  #852\r\n* Error codes can now be configured for messages from tflint.  #852\r\n* Error codes can now be configured for messages from foodcritic.  #852\r\n* `msgid` values (like `E0103`) are no longer reported for pylint, which aren't human-readable.  #852 \r\n* pycodestyle errors and warnings are now style errors and warnings.  #852 \r\n* Rails-specific syntax will now automatically be stripped from `erb` files. #580 #1114\r\n* The GCC executable for ASM may now be configured. #1138\r\n* Options can now be configured for `iverilog`. #1143\r\n* The `javac` linter now includes test source paths for test files. #859\r\n* The `javac` linter now includes jaxb source paths when available. #859\r\n* Problems in other files will now appear in lists for the `gobuild` linter. #1154\r\n* The `foodcritic` linter has been overhauled to check only files on disk with better error messages. #1151\r\n* `flow` will no longer check files with home directory configuration files by default, which can eat all of your CPU and RAM. Set `g:ale_javascript_flow_use_home_config` to `1` to use home directory configuration files, if you really must. #783\r\n* Prettier text will now be saved for detailed messages for Haskell linters. #918\r\n* Different toolchains for `rls` can now be selected. See `:help g:ale_rust_rls_toolchain`  #1166\r\n* The `ruby` executable is now configurable. #1168\r\n* Warnings about trailing blank lines can be disabled for `flake8` and `pycodestyle`.\r\n* The `phpcbf` linter should now work properly, apparently. #1188 \r\n* The `puppet` linter now parses output which doesn't include column numbers.  #1182\r\n* The executable for `perl` is now properly escaped. \r\n* `gometalinter` can now be configured to report problems from other files. See `:help g:ale_go_gometalinter_lint_package` #1156\r\n* The `php` linter now handles error output from PHP 7.2, which has slightly different output.\r\n* The `vale` linter now parses end column numbers, for better highlighting.\r\n* The `erb` linter now works on puppet style templates.  #1221\r\n* The `mcsc` linter paths and escaping should now work on Windows.\r\n* The `ember-template-lint` linter will now parse line and column numbers for fatal errors if they are included.\r\n* Some of the options for `rustc` can now be configured, so `-Z no-trans` can be replaced with something else. #1031\r\n\r\n## Fixer Enhancements\r\n\r\n* The `prettier` fixer will now use the `--stdin-filepath` argument when the version is 1.6.0 or greater. #1095\r\n* The `prettier_eslint` fixer will now use the `--stdin-filepath` argument when the version is 4.4.0 or greater. #1095\r\n* The `prettier_eslint` fixer will now use the `--eslint-config-path` argument only when the version is 4.2.0 or greater. The old legacy option has been removed, as it is no longer needed. #1095\r\n* `'prettier-eslint'` may now be used in place of `'prettier_eslint'` for fixers.\r\n* `'prettier-standard'` may now be used in place of `'prettier_standard'` for fixers.\r\n* `--fix-to-stdout` is now used for better configuration detection for `eslint_d` where available. #988\r\n* `--fix-dry-run` is now used for ESLint 4.9.0 and up for fixing files with better configuration file detection. #988","3":"## Bugs Fixed\r\n\r\n* ALE will now find files relative to buffers in cygwin. #1180 #1181\r\n* The temporary file for TSLint was being mentioned sometimes in the quickfix list.  #1210\r\n* ALE will now suppress trailing whitespace warnings for `ansible-lint` when the option is on. #1216\r\n* Relative and absolute paths are now resolved better on Windows. #1210\r\n* ALE no longer moves the cursor slightly when briefly escaping insert mode and echoing a message. #1228\r\n\r\n## New Features\r\n\r\n* ALE linting can now be toggled for particular buffers. See `:help ALEToggleBuffer`. #817\r\n* Problems reported by ALE can now be removed with `ALEReset` or `ALEResetBuffer`. #719 \r\n* `b:ale_fix_on_save` can now be used for controlling fixing on save for specific buffers. #857 \r\n* Fixer functions can now be chained, much like linters. #1086 \r\n* Fixer functions can now specify callbacks for post-processing command output.\r\n* Reading the buffer via stdin can now be disabled for fixer commands with `'read_buffer': 0`, just like linters.\r\n* `b:ale_fixers` can now be set to a `List`. #1108\r\n* `b:ale_linters` can now be set to a `List`. #1108\r\n* `b:ale_linters` can now be set to `'all'`. #1108\r\n* `b:ale_linter_aliases` can now be set to a `List`. #1108 \r\n* ALE will now show the echoed severity for type `'I'` problems as `'Info'`.\r\n* ALE now supports formatting echo messages with error codes. #852\r\n* Several linters have now been updated so the error codes are configurable. #852 \r\n* The echo message format can now be configured differently for different buffers. See `:help b:ale_echo_msg_format`\r\n* Messages for loclist and the quickfix list can now be formatted like echoed messages. See  `:help g:ale_loclist_msg_format` #1069 #852\r\n* ALE linters can now be configured to only be enabled explicitly. See `:help g:ale_linters_explicit` #1128\r\n* `:ALEDetail` will now show messages in a preview window. #757\r\n* Line highlights will now be set when signs are disabled. #741\r\n* ALE now supports jumping to definitions for LSP and tsserver linters. See `:help ale-go-to-definition`.\r\n* Warnings about trailing blank lines can be disabled for some linters. See `:help g:ale_warn_about_trailing_blank_lines`. \r\n* Failing executable checks may now be cached with `let g:ale_cache_executable_check_failures = 1` #1176\r\n* An autocmd command `ALELintPre` has been added for running code just before ALE starts linting.\r\n\r\n## Other Changes\r\n\r\n* ALE will no longer modify `runtimepath` when `g:ale_emit_conflict_warnings` is set to `0`.  #1049\r\n* ALE should no longer mess with folds when `ALELint` autocmd commands are set. #1062\r\n* ALE will no longer send an `id` `key` for the LSP notification messages at all, instead of `v:null`. #1110\r\n* Output will now be ignored for fixer commands which output only whitespace.\r\n* When ALE deletes lines as the result of fixing files, the deleted lines will be put in the black hole register. #1165\r\n* `tsserver` completions will now be requested again after completion is done only if the cursor moves, rather than waiting for 100ms. #1041\r\n* The `perl` linter is now disabled by default, as it can execute malicious code. #1186\r\n* The `ALELint` autocmd has been renamed to `ALELintPost`, but the old commands will still be run until version 2.0. On version 2.0, `ALELint` commands will probably be removed.\r\n* ALE will now look for `mypy.ini` files for finding Python project roots.\r\n* ALE will now look for `venv` for finding virtualenv directories by default. #1237\r\n* Cursor messages can now be disabled while Vim is running.\r\n* ALE now cleans up buffer data when buffers are deleted instead of unloaded, so the quickfix list can be maintained.\r\n\r\n## New Linters\r\n\r\n* AsciiDoc - `alex` #1220, `redpen` #1142, `write-good` #643 #811 \r\n* API Blueprint - `drafter` #1152 \r\n* Clojure - `joker` #1133\r\n* Dafny - `dafny` #1093\r\n* Dart - `dart_language_server` #1006\r\n* GLSL - `glslls` #1179\r\n* GraphQL - `eslint`  #1169\r\n* HTML - `alex` #1220, `write-good` #643 #811\r\n* LaTeX - `alex` #1220, `redpen` #1142, `vale` #1230, `write-good` #643 #811\r\n* LESS - `lessc` #1103, `stylelint` #510\r\n* mail - `alex` #1220, `proselint` #1037, `vale` #1044\r\n* Markdown - `alex` #1220, `redpen`  #1137, `write-good` #643 #811\r\n* nroff - `alex` #1220, `write-good` #643 #811 \r\n* OCaml - `ols` #1110\r\n* PHP - `phan` #1026 \r\n* Pod - `alex` #1220, `write-good` #643 #811 \r\n* proto - `protoc-gen-lint` #1098\r\n* Python - `prospector` #565 #1183, `pyflakes` #516, `PyLS` #1097\r\n* Solidarity - `solhint` #1192\r\n* ReasonML - `ols` #1110\r\n* reStructuredText - `alex` #1220, `redpen` #1142, `rstcheck` #1090, `vale` #1230, `write-good` #643 #811 \r\n* Re:VIEW - `redpen` #1142\r\n* Terraform - `tflint` #1046\r\n* Texinfo - `alex` #1220, `write-good` #643 #811\r\n* text - `alex` #1220, `redpen` #1142, `write-good` #643 #811\r\n* Vim help - `alex` #1220, `write-good` #643 #811 \r\n* XHTML - `alex` #1220, `write-good` #643 #811 \r\n\r\n## New Fixers\r\n\r\n* Elixir - `mix format` #1017 \r\n* Go - `goimports` #1123\r\n* Hack - `hackfmt` #1053\r\n* Haskell - `brittany`  #1174, `hfmt` #1027 \r\n* Java - `google-java-format` #1209\r\n* JavaScript - `importjs` #1191\r\n* ReasonML - `refmt` #1059\r\n* Rust - `rustfmt` #1025 \r\n* Shell - `shfmt` #1083\r\n\r\n## Linter Enhancements\r\n\r\n* ALE now captures problems for other files for GCC, clang, and related tools. #1023 \r\n* The `rubocop` and `haml-lint` configuration files will be now used for `ham-lint` automatically. #1047 \r\n* The `shellcheck` linter will now use `-x` and follow sourced files when checking for errors. #491\r\n* The `shellcheck` linter now uses the type `'I'` for notes. #1122\r\n* The `phpcs` linter will now include the error code in the message. #1009\r\n* Errors for missing ESLint configuration files can now be disabled. See `:help g:ale_javascript_eslint_suppress_missing_config`. #971\r\n* `cargo check` and `cargo check --all-targets` will now automatically be used when `cargo` is new enough. `g:ale_rust_cargo_use_check` or `g:ale_rust_cargo_check_all_targets` can be set to disable either.  #626 \r\n* The `phpmd` executable can now be configured, and error checking should be more reliable. #1076\r\n* The `flow` linter will now include more information for errors in the `:ALEDetail` message. #946\r\n* Error codes can now be configured for messages from ESLint.  #852\r\n* Error codes can now be configured for messages from TSLint.  #852\r\n* Error codes can now be configured for messages from flake8.  #852\r\n* Error codes can now be configured for messages from rubocop.  #852\r\n* Error codes can now be configured for messages from ansible-lint.  #852 \r\n* Error codes can now be configured for messages from cpplint.  #852 \r\n* Error codes can now be configured for messages from shellcheck.  #852 \r\n* Error codes can now be configured for messages from pylint.  #852 \r\n* Error codes can now be configured for messages from checkmake. #852 #1135\r\n* Error codes can now be configured for messages from checkstyle. #852\r\n* Error codes can now be configured for messages from pycodestyle.  #852 \r\n* Error codes can now be configured for messages from csslint.  #852\r\n* Error codes can now be configured for messages from jscs.  #852\r\n* Error codes can now be configured for messages from luacheck.  #852\r\n* Error codes can now be configured for messages from mcs and mcsc.  #852\r\n* Error codes can now be configured for messages from nimcheck.  #852\r\n* Error codes can now be configured for messages from reek.  #852\r\n* Error codes can now be configured for messages from slim-lint.  #852\r\n* Error codes can now be configured for messages from stylelint.  #852\r\n* Error codes can now be configured for messages from swaglint.  #852\r\n* Error codes can now be configured for messages from swiftlint.  #852\r\n* Error codes can now be configured for messages from tflint.  #852\r\n* Error codes can now be configured for messages from foodcritic.  #852\r\n* `msgid` values (like `E0103`) are no longer reported for pylint, which aren't human-readable.  #852 \r\n* pycodestyle errors and warnings are now style errors and warnings.  #852 \r\n* Rails-specific syntax will now automatically be stripped from `erb` files. #580 #1114\r\n* The GCC executable for ASM may now be configured. #1138\r\n* Options can now be configured for `iverilog`. #1143\r\n* The `javac` linter now includes test source paths for test files. #859\r\n* The `javac` linter now includes jaxb source paths when available. #859\r\n* Problems in other files will now appear in lists for the `gobuild` linter. #1154\r\n* The `foodcritic` linter has been overhauled to check only files on disk with better error messages. #1151\r\n* `flow` will no longer check files with home directory configuration files by default, which can eat all of your CPU and RAM. Set `g:ale_javascript_flow_use_home_config` to `1` to use home directory configuration files, if you really must. #783\r\n* Prettier text will now be saved for detailed messages for Haskell linters. #918\r\n* Different toolchains for `rls` can now be selected. See `:help g:ale_rust_rls_toolchain`  #1166\r\n* The `ruby` executable is now configurable. #1168\r\n* Warnings about trailing blank lines can be disabled for `flake8` and `pycodestyle`.\r\n* The `phpcbf` linter should now work properly, apparently. #1188 \r\n* The `puppet` linter now parses output which doesn't include column numbers.  #1182\r\n* The executable for `perl` is now properly escaped. \r\n* `gometalinter` can now be configured to report problems from other files. See `:help g:ale_go_gometalinter_lint_package` #1156\r\n* The `php` linter now handles error output from PHP 7.2, which has slightly different output.\r\n* The `vale` linter now parses end column numbers, for better highlighting.\r\n* The `erb` linter now works on puppet style templates.  #1221\r\n* The `mcsc` linter paths and escaping should now work on Windows.\r\n* The `ember-template-lint` linter will now parse line and column numbers for fatal errors if they are included.\r\n* Some of the options for `rustc` can now be configured, so `-Z no-trans` can be replaced with something else. #1031\r\n\r\n## Fixer Enhancements\r\n\r\n* The `prettier` fixer will now use the `--stdin-filepath` argument when the version is 1.6.0 or greater. #1095\r\n* The `prettier_eslint` fixer will now use the `--stdin-filepath` argument when the version is 4.4.0 or greater. #1095\r\n* The `prettier_eslint` fixer will now use the `--eslint-config-path` argument only when the version is 4.2.0 or greater. The old legacy option has been removed, as it is no longer needed. #1095\r\n* `'prettier-eslint'` may now be used in place of `'prettier_eslint'` for fixers.\r\n* `'prettier-standard'` may now be used in place of `'prettier_standard'` for fixers.\r\n* `--fix-to-stdout` is now used for better configuration detection for `eslint_d` where available. #988\r\n* `--fix-dry-run` is now used for ESLint 4.9.0 and up for fixing files with better configuration file detection. #988","package":"vim-ale-1.7.0.zip","4":"vim-ale-1.7.0.zip","src_id":"25721","5":"25721","creation_date":"1513708388","6":"1513708388"},{"0":"5449","vim_version":"8.0","1":"8.0","script_version":"1.6.2","2":"1.6.2","version_comment":"## Bugs Fixed\r\n\r\n* ALE's parsing for `stack-build` has been updated so it will parse errors with leading spaces, as returned by newer versions. #1124 \r\n* LSP linters on Windows weren't handling filename URIs correctly. This has been fixed. #1149","3":"## Bugs Fixed\r\n\r\n* ALE's parsing for `stack-build` has been updated so it will parse errors with leading spaces, as returned by newer versions. #1124 \r\n* LSP linters on Windows weren't handling filename URIs correctly. This has been fixed. #1149","package":"vim-ale-1.6.2.zip","4":"vim-ale-1.6.2.zip","src_id":"25654","5":"25654","creation_date":"1511276381","6":"1511276381"},{"0":"5449","vim_version":"8.0","1":"8.0","script_version":"1.6.1","2":"1.6.1","version_comment":"## Bugs Fixed\r\n\r\n* ALE will now read `cargo` output from either `stdout` or `stderr`, to support more versions of `cargo` #1045 \r\n* ALE will no longer try to lint files named `.` #1048 \r\n* `ash` and `dash` are now supported for shell linters #1051 \r\n* Completions will now not be requested shortly after `CompleteDone`, fixing a bug where the menu kept re-opening #1041\r\n* `gosimple` and `staticcheck` will now check only the actual files on disk, because that is all they support. #936\r\n* Running the `php` linter will no longer write to the PHP error log. #1072 \r\n* The `erlc` linter is now supported on Windows. #1071 \r\n* Python fixers weren't working on Windows since version 1.6.0. This has been fixed. #1081 \r\n* When combined with some other plugins in NeoVim, ALE would sometimes through exceptions when trying to stop jobs. These errors are now silenced. #1058\r\n* The `javac` linter wasn't handling errors from other files correctly. This has been fixed. #1061 \r\n* All LSP and `tsserver` messages which include a buffer's text data will now include a final line feed, so tools which complain about missing newline characters will be quiet. #1085 \r\n* Message handling for LSP linters wasn't working in NeoVim, due to improper handling of LSP messages. This has been fixed. #1006\r\n* ALE was reporting `no-implicit-dependencies` for most files with in TSLint's latest version, because TSLint does not fully support checking for errors while you type yet. These errors have been silenced for now. #1101","3":"## Bugs Fixed\r\n\r\n* ALE will now read `cargo` output from either `stdout` or `stderr`, to support more versions of `cargo` #1045 \r\n* ALE will no longer try to lint files named `.` #1048 \r\n* `ash` and `dash` are now supported for shell linters #1051 \r\n* Completions will now not be requested shortly after `CompleteDone`, fixing a bug where the menu kept re-opening #1041\r\n* `gosimple` and `staticcheck` will now check only the actual files on disk, because that is all they support. #936\r\n* Running the `php` linter will no longer write to the PHP error log. #1072 \r\n* The `erlc` linter is now supported on Windows. #1071 \r\n* Python fixers weren't working on Windows since version 1.6.0. This has been fixed. #1081 \r\n* When combined with some other plugins in NeoVim, ALE would sometimes through exceptions when trying to stop jobs. These errors are now silenced. #1058\r\n* The `javac` linter wasn't handling errors from other files correctly. This has been fixed. #1061 \r\n* All LSP and `tsserver` messages which include a buffer's text data will now include a final line feed, so tools which complain about missing newline characters will be quiet. #1085 \r\n* Message handling for LSP linters wasn't working in NeoVim, due to improper handling of LSP messages. This has been fixed. #1006\r\n* ALE was reporting `no-implicit-dependencies` for most files with in TSLint's latest version, because TSLint does not fully support checking for errors while you type yet. These errors have been silenced for now. #1101","package":"vim-ale-1.6.1.zip","4":"vim-ale-1.6.1.zip","src_id":"25639","5":"25639","creation_date":"1510262382","6":"1510262382"},{"0":"5449","vim_version":"8.0","1":"8.0","script_version":"1.6.0","2":"1.6.0","version_comment":"## Bugs Fixed\r\n\r\n- ALE wasn't checking buffers on enter in some cases. This has been fixed. #734 \r\n- The regular expression for parsing `phpmd` errors has been updated, so errors may be handled better in some cases. #1032\r\n\r\n## New Features\r\n\r\n- The maximum number of signs ALE will set can now be configured. See `:help g:ale_max_signs` #965\r\n- The delay before echoing a message can now be configured. See `:help g:ale_echo_delay` #965 \r\n\r\n## Other Changes\r\n\r\n- Linters and some other processing will no longer be run when `v:exiting` is set in NeoVim 0.2.0 and above. #904\r\n- Linters will no longer be run on `:wq` or `:x`, which did nothing useful. #904\r\n\r\n## New Linters\r\n\r\n- C - `clang-tidy` #827\r\n- C# - `mcsc` (See `:help `ale-cs-mcsc`) #952\r\n- GLSL - `glslang` #914\r\n- LLVM IR - llc #979\r\n- Solidity - solium #929\r\n- Thrift - `thrift` #892 \r\n- Markdown - `remark-lint` #1010\r\n\r\n## New Fixers\r\n\r\n- `prettier` for TypeScript, CSS, SCSS, LESS, and JSON #910 #1018\r\n- `elm-format` #916\r\n- `gofmt` #970\r\n- `trim_whitespace` #991\r\n- `tslint` #1001\r\n\r\n## Linter Enhancements\r\n\r\n- ALE will now prefer to use `prettier_d` for `prettier`, if it is installed. #885\r\n- The `javac` linter will now include paths based on gradle build commands. #889 \r\n- CM files are now used for smlnj where available. See `:help ale-sml-smlnj` #884 \r\n- TSLint output can now be ignored for empty files. See `:help g:ale_typescript_tslint_ignore_empty_files`\r\n- The `brakeman` linter will now report problems for other files in quickfix and loclist.\r\n- The `slim-lint` linter will now use rubocop configuration files. #903 #942\r\n- The `shellcheck` linter now arranges the arguments in such a way that manually changing the dialect is possible. #949 \r\n- The `phpstan` configuration file can now be configured. #969\r\n- `$VIRTUAL_ENV` will be used for running Python tools when no local directories can be found. #990\r\n- The `luacheck` linter will now respect the `g:ale_warn_about_trailing_whitespace` option. #968\r\n- ALE will now tell you how to configure `scalastyle` when no configuration file was found. #977\r\n\r\n## Fixer Enhancements\r\n\r\n- Configuration files can now be detected for `prettier`. See `:help g:ale_javascript_prettier_use_local_config` #886\r\n- The `prettier-eslint` fixer now uses the eslint configuration file by default, which will yield better results, but may break things for some users. `See :help g:ale_javascript_prettier_eslint_legacy` #854\r\n- The `yapf` fixer should now run local virtualenv executables on Windows.\r\n- The `standard` fixer can now be used even if the linter is never loaded.","3":"## Bugs Fixed\r\n\r\n- ALE wasn't checking buffers on enter in some cases. This has been fixed. #734 \r\n- The regular expression for parsing `phpmd` errors has been updated, so errors may be handled better in some cases. #1032\r\n\r\n## New Features\r\n\r\n- The maximum number of signs ALE will set can now be configured. See `:help g:ale_max_signs` #965\r\n- The delay before echoing a message can now be configured. See `:help g:ale_echo_delay` #965 \r\n\r\n## Other Changes\r\n\r\n- Linters and some other processing will no longer be run when `v:exiting` is set in NeoVim 0.2.0 and above. #904\r\n- Linters will no longer be run on `:wq` or `:x`, which did nothing useful. #904\r\n\r\n## New Linters\r\n\r\n- C - `clang-tidy` #827\r\n- C# - `mcsc` (See `:help `ale-cs-mcsc`) #952\r\n- GLSL - `glslang` #914\r\n- LLVM IR - llc #979\r\n- Solidity - solium #929\r\n- Thrift - `thrift` #892 \r\n- Markdown - `remark-lint` #1010\r\n\r\n## New Fixers\r\n\r\n- `prettier` for TypeScript, CSS, SCSS, LESS, and JSON #910 #1018\r\n- `elm-format` #916\r\n- `gofmt` #970\r\n- `trim_whitespace` #991\r\n- `tslint` #1001\r\n\r\n## Linter Enhancements\r\n\r\n- ALE will now prefer to use `prettier_d` for `prettier`, if it is installed. #885\r\n- The `javac` linter will now include paths based on gradle build commands. #889 \r\n- CM files are now used for smlnj where available. See `:help ale-sml-smlnj` #884 \r\n- TSLint output can now be ignored for empty files. See `:help g:ale_typescript_tslint_ignore_empty_files`\r\n- The `brakeman` linter will now report problems for other files in quickfix and loclist.\r\n- The `slim-lint` linter will now use rubocop configuration files. #903 #942\r\n- The `shellcheck` linter now arranges the arguments in such a way that manually changing the dialect is possible. #949 \r\n- The `phpstan` configuration file can now be configured. #969\r\n- `$VIRTUAL_ENV` will be used for running Python tools when no local directories can be found. #990\r\n- The `luacheck` linter will now respect the `g:ale_warn_about_trailing_whitespace` option. #968\r\n- ALE will now tell you how to configure `scalastyle` when no configuration file was found. #977\r\n\r\n## Fixer Enhancements\r\n\r\n- Configuration files can now be detected for `prettier`. See `:help g:ale_javascript_prettier_use_local_config` #886\r\n- The `prettier-eslint` fixer now uses the eslint configuration file by default, which will yield better results, but may break things for some users. `See :help g:ale_javascript_prettier_eslint_legacy` #854\r\n- The `yapf` fixer should now run local virtualenv executables on Windows.\r\n- The `standard` fixer can now be used even if the linter is never loaded.","package":"vim-ale-1.6.0.zip","4":"vim-ale-1.6.0.zip","src_id":"25616","5":"25616","creation_date":"1508799042","6":"1508799042"},{"0":"5449","vim_version":"8.0","1":"8.0","script_version":"1.5.2","2":"1.5.2","version_comment":"## Bugs Fixed\r\n\r\n* ALE was sometimes reporting errors when trying to open empty list windows. This has been fixed. #920 \r\n* `staticcheck` and `gosimple` now capture both output streams so they will report errors where they didn't. #921\r\n* ALE wasn't changing the sign column color any more when that option was on since 1.5.0. This has been fixed. #924 \r\n* ALE stopped removing signs properly when multiple signs ended up lying on a single line, since 1.5.0. This has been fixed. #964\r\n* ALE was using the wrong ESLint configuration files in some cases. This has been fixed. #922 \r\n* `eslint --fix` now uses `-c` instead of `--config` for specifying the configuration file, which apparently works better in some versions. #951","3":"## Bugs Fixed\r\n\r\n* ALE was sometimes reporting errors when trying to open empty list windows. This has been fixed. #920 \r\n* `staticcheck` and `gosimple` now capture both output streams so they will report errors where they didn't. #921\r\n* ALE wasn't changing the sign column color any more when that option was on since 1.5.0. This has been fixed. #924 \r\n* ALE stopped removing signs properly when multiple signs ended up lying on a single line, since 1.5.0. This has been fixed. #964\r\n* ALE was using the wrong ESLint configuration files in some cases. This has been fixed. #922 \r\n* `eslint --fix` now uses `-c` instead of `--config` for specifying the configuration file, which apparently works better in some versions. #951","package":"vim-ale-1.5.2.zip","4":"vim-ale-1.5.2.zip","src_id":"25599","5":"25599","creation_date":"1507053512","6":"1507053512"},{"0":"5449","vim_version":"8.0","1":"8.0","script_version":"1.5.1","2":"1.5.1","version_comment":"## Bugs Fixed\r\n\r\n* ALE will now detect the shell dialect for `shellcheck` by parsing hashbang (`#!`) lines. #869\r\n* `pycodestyle` is now disabled by default, as it is also installed when you install `flake8`. #888 \r\n* ALE now uses `node.exe` instead of `node` to execute Node.js scripts on Windows, and the path can be configured if needed. See `:help g:ale_windows_node_executable_path` #895 \r\n* ALE will no longer lint a file when the filetype is initially set if `g:ale_lint_on_enter` is set to `0`. #505 \r\n* ALE should no longer show linting results in ctrlp-funky windows. #891\r\n* Since version 1.5.0, ALE wasn't closing the loclist or quickfix windows most of the time. This has been fixed. #899 #912\r\n* Since version 1.5.0, `tsserver` integration was broken due to a bug in NeoVim. A workaround has been added to fix this issue in ALE. #907","3":"## Bugs Fixed\r\n\r\n* ALE will now detect the shell dialect for `shellcheck` by parsing hashbang (`#!`) lines. #869\r\n* `pycodestyle` is now disabled by default, as it is also installed when you install `flake8`. #888 \r\n* ALE now uses `node.exe` instead of `node` to execute Node.js scripts on Windows, and the path can be configured if needed. See `:help g:ale_windows_node_executable_path` #895 \r\n* ALE will no longer lint a file when the filetype is initially set if `g:ale_lint_on_enter` is set to `0`. #505 \r\n* ALE should no longer show linting results in ctrlp-funky windows. #891\r\n* Since version 1.5.0, ALE wasn't closing the loclist or quickfix windows most of the time. This has been fixed. #899 #912\r\n* Since version 1.5.0, `tsserver` integration was broken due to a bug in NeoVim. A workaround has been added to fix this issue in ALE. #907","package":"vim-ale-1.5.1.zip","4":"vim-ale-1.5.1.zip","src_id":"25556","5":"25556","creation_date":"1504898153","6":"1504898153"},{"0":"5449","vim_version":"8.0","1":"8.0","script_version":"1.5.0","2":"1.5.0","version_comment":"## Bugs Fixed\r\n\r\n- ALE sometimes didn't remove highlights now and again. This has been fixed. #697 \r\n- `eslint --fix` needed to be executed with `node` on Windows when installed via `create-react-app`. This has been fixed. #775 \r\n- The GCC error handler was ignoring errors without column numbers. This has been fixed. #795 \r\n- `scalac` was being run for SBT files with the filetype `scala.sbt`. Now `scalac` is not run for SBT files. #804 \r\n- Many linters which expect JSON output now ignore output which isn't JSON. #810\r\n- ALE was not handling syntax errors from `tsserver`. This has been fixed. #798\r\n- ALE didn't check files some of the time when restoring multiple windows from a saved session. This has been fixed. #734 \r\n- When ALE wrote files with `fileformat=dos`, carriage returns were not included. This has been fixed. #823 \r\n- Now when selections are active when loclist or quickfix windows are opened, the selection will be reset. #788 \r\n- `flake8` wasn't parsing errors if you configured the format option in configuration files. Now the format is always explicitly set in the command, so it works. #837\r\n- The `rubocop` fixer now uses the same options that the linter is configured with. #841 \r\n- Jumping through problems didn't work in some cases with blank lines. This has been fixed. #848 \r\n- If problems were kept from previous linter runs, like a `lint_file` linter, ALE would not downgrade signs in the sign column. This has been fixed. #825\r\n\r\n## New Features\r\n- ALE now comes with LSP (Language Server Protocol) support, for checking files with language servers. See `:help ale-lsp-linters` for documentation on how LSP linters can be defined. #517 \r\n- ALE now offers support for code completion while you type for TypeScript code via `tsserver`. See `:help ale-completion`\r\n- `:ALEFixSuggest` will now suggest tools for fixing problems in a new window, instead of a long echo message.\r\n- ALE will now stop checking buffers for a period of time when exceptions are thrown. See `:help ale-cool-down` #468\r\n- ALE now supports running Python executables from virtualenv directories on Windows. #729\r\n- ALE will now remove any problems previously set when linters are disabled, removed, or when the filetype changes.\r\n- Buffer-local settings can now be set with `g:ale_pattern_options` by using names starting with `&`.\r\n- ALE will now detect Python project roots based on common configuration files, in addition to looking upwards to find the first directory without an `__init__.py` file. #755 \r\n- ALE can now be configured to open quickfix or loclist windows only when files are saved. See `:help g:ale_open_list` #271 \r\n- Buffer local options `b:ale_open_list` and `b:ale_keep_list_window_open` are now supported. #271 \r\n- `ALEInfo` will now print the results of executable checks for linters, which should help you figure out why a linter might not be running.\r\n\r\n## New Linters\r\n- Dart - `dartanalyzer` #308\r\n- Erlang - `SyntaxErl` #774 \r\n- eruby - `erubis` #865\r\n- GraphQL - `gqlint` #863\r\n- Idris - `idris` #838\r\n- PHP - `langserver` #517, `phpstan` #772 \r\n- Python - `pycodestyle` #872\r\n- R - `lintr` #182\r\n- Ruby - `rails_best_practices` #751 \r\n- Rust - `rls` #517\r\n- Scala - `scalastyle` #766\r\n- Stylus - `stylelint` #178\r\n- Tcl - `nagelfar` #821\r\n- YAML - `swaglint` #771\r\n\r\n## New Fixers\r\n- C, C++ - `clang-format` #873\r\n- CSS, SASS, SCSS, stylus - `stylelint` #657 #813\r\n- JavaScript - `prettier-standard` #702 \r\n- JavaScript - `standard` #781 \r\n- PHP - `phpcbf` #862\r\n- Puppet - `puppet-lint` #701 \r\n- Swift - `swiftformat` #842\r\n\r\n## Linter Enhancements\r\n- All C and C++ linters executable paths can now be configured. #711\r\n- The `elm-make` linter now includes end line and column numbers for highlights. #699 \r\n- The `verilator` linter's options can now be configured. #698 \r\n- The `pug-lint` linter now detects `node_modules` executables, like other linters, and supports the same options as most other linters. https:\/\/github.com\/w0rp\/ale\/commit\/79e8e063af1cf7a72ec42075f4eed30aa69607e8\r\n- The `perlcritic` linter now supports more options and will automatically load configuration files. See `:help ale-perl-perlcritic-options` #675\r\n- The `luacheck` linter now includes the error codes in the message. #717 \r\n- The `hadolint` linter can now be run via a Docker image. #720 \r\n- `stylelint` linters will now print exceptions thrown by `stylelint`, including missing configuration files.\r\n- The `gometalinter` linter's executable can now be configured.\r\n- The `jscs` linter can now be used with older versions of jscs. #737 \r\n- The `rubocop` linter now works with older versions of rubocop. #339 #738\r\n- The `rubocop` linter now includes end column numbers for better error highlighting. #738 \r\n- The `rubocop` linter now includes the error type in the error messages. #820\r\n- The `clang-check` linter now uses some additional arguments to avoid generating .plist files if no build directory is set. #703 \r\n- The `hlint` linter now uses type `I` for suggestions. #710\r\n- The `hlint` linter now includes end line and column numbers for better highlighting. #710 \r\n- The `hdevtools` linter's options and executable can now be configured. #799 \r\n- The `ghc-mod` linter will now map the temporary file for better error messages. #846 \r\n- The rule name is now included in the messages for tslint problems.\r\n- The `SyntaxErl` linter will now include the basename option when available. #860 #861 \r\n- Warnings about files ignored by ESLint can now be disabled. #836 \r\n- Some `Vint` problems will be highlighted better.\r\n\r\n## Fixer Enhancements\r\n- The `yapf` fixer now only sets `--no-local-style` if a configuration file is detected. #786","3":"## Bugs Fixed\r\n\r\n- ALE sometimes didn't remove highlights now and again. This has been fixed. #697 \r\n- `eslint --fix` needed to be executed with `node` on Windows when installed via `create-react-app`. This has been fixed. #775 \r\n- The GCC error handler was ignoring errors without column numbers. This has been fixed. #795 \r\n- `scalac` was being run for SBT files with the filetype `scala.sbt`. Now `scalac` is not run for SBT files. #804 \r\n- Many linters which expect JSON output now ignore output which isn't JSON. #810\r\n- ALE was not handling syntax errors from `tsserver`. This has been fixed. #798\r\n- ALE didn't check files some of the time when restoring multiple windows from a saved session. This has been fixed. #734 \r\n- When ALE wrote files with `fileformat=dos`, carriage returns were not included. This has been fixed. #823 \r\n- Now when selections are active when loclist or quickfix windows are opened, the selection will be reset. #788 \r\n- `flake8` wasn't parsing errors if you configured the format option in configuration files. Now the format is always explicitly set in the command, so it works. #837\r\n- The `rubocop` fixer now uses the same options that the linter is configured with. #841 \r\n- Jumping through problems didn't work in some cases with blank lines. This has been fixed. #848 \r\n- If problems were kept from previous linter runs, like a `lint_file` linter, ALE would not downgrade signs in the sign column. This has been fixed. #825\r\n\r\n## New Features\r\n- ALE now comes with LSP (Language Server Protocol) support, for checking files with language servers. See `:help ale-lsp-linters` for documentation on how LSP linters can be defined. #517 \r\n- ALE now offers support for code completion while you type for TypeScript code via `tsserver`. See `:help ale-completion`\r\n- `:ALEFixSuggest` will now suggest tools for fixing problems in a new window, instead of a long echo message.\r\n- ALE will now stop checking buffers for a period of time when exceptions are thrown. See `:help ale-cool-down` #468\r\n- ALE now supports running Python executables from virtualenv directories on Windows. #729\r\n- ALE will now remove any problems previously set when linters are disabled, removed, or when the filetype changes.\r\n- Buffer-local settings can now be set with `g:ale_pattern_options` by using names starting with `&`.\r\n- ALE will now detect Python project roots based on common configuration files, in addition to looking upwards to find the first directory without an `__init__.py` file. #755 \r\n- ALE can now be configured to open quickfix or loclist windows only when files are saved. See `:help g:ale_open_list` #271 \r\n- Buffer local options `b:ale_open_list` and `b:ale_keep_list_window_open` are now supported. #271 \r\n- `ALEInfo` will now print the results of executable checks for linters, which should help you figure out why a linter might not be running.\r\n\r\n## New Linters\r\n- Dart - `dartanalyzer` #308\r\n- Erlang - `SyntaxErl` #774 \r\n- eruby - `erubis` #865\r\n- GraphQL - `gqlint` #863\r\n- Idris - `idris` #838\r\n- PHP - `langserver` #517, `phpstan` #772 \r\n- Python - `pycodestyle` #872\r\n- R - `lintr` #182\r\n- Ruby - `rails_best_practices` #751 \r\n- Rust - `rls` #517\r\n- Scala - `scalastyle` #766\r\n- Stylus - `stylelint` #178\r\n- Tcl - `nagelfar` #821\r\n- YAML - `swaglint` #771\r\n\r\n## New Fixers\r\n- C, C++ - `clang-format` #873\r\n- CSS, SASS, SCSS, stylus - `stylelint` #657 #813\r\n- JavaScript - `prettier-standard` #702 \r\n- JavaScript - `standard` #781 \r\n- PHP - `phpcbf` #862\r\n- Puppet - `puppet-lint` #701 \r\n- Swift - `swiftformat` #842\r\n\r\n## Linter Enhancements\r\n- All C and C++ linters executable paths can now be configured. #711\r\n- The `elm-make` linter now includes end line and column numbers for highlights. #699 \r\n- The `verilator` linter's options can now be configured. #698 \r\n- The `pug-lint` linter now detects `node_modules` executables, like other linters, and supports the same options as most other linters. https:\/\/github.com\/w0rp\/ale\/commit\/79e8e063af1cf7a72ec42075f4eed30aa69607e8\r\n- The `perlcritic` linter now supports more options and will automatically load configuration files. See `:help ale-perl-perlcritic-options` #675\r\n- The `luacheck` linter now includes the error codes in the message. #717 \r\n- The `hadolint` linter can now be run via a Docker image. #720 \r\n- `stylelint` linters will now print exceptions thrown by `stylelint`, including missing configuration files.\r\n- The `gometalinter` linter's executable can now be configured.\r\n- The `jscs` linter can now be used with older versions of jscs. #737 \r\n- The `rubocop` linter now works with older versions of rubocop. #339 #738\r\n- The `rubocop` linter now includes end column numbers for better error highlighting. #738 \r\n- The `rubocop` linter now includes the error type in the error messages. #820\r\n- The `clang-check` linter now uses some additional arguments to avoid generating .plist files if no build directory is set. #703 \r\n- The `hlint` linter now uses type `I` for suggestions. #710\r\n- The `hlint` linter now includes end line and column numbers for better highlighting. #710 \r\n- The `hdevtools` linter's options and executable can now be configured. #799 \r\n- The `ghc-mod` linter will now map the temporary file for better error messages. #846 \r\n- The rule name is now included in the messages for tslint problems.\r\n- The `SyntaxErl` linter will now include the basename option when available. #860 #861 \r\n- Warnings about files ignored by ESLint can now be disabled. #836 \r\n- Some `Vint` problems will be highlighted better.\r\n\r\n## Fixer Enhancements\r\n- The `yapf` fixer now only sets `--no-local-style` if a configuration file is detected. #786","package":"vim-ale-1.5.0.zip","4":"vim-ale-1.5.0.zip","src_id":"25537","5":"25537","creation_date":"1503939641","6":"1503939641"},{"0":"5449","vim_version":"8.0","1":"8.0","script_version":"1.4.1","2":"1.4.1","version_comment":"## Notes\r\n- From this version and onward, ALE remembers the full output of recent commands by default, which helps with filing bug reports and fixing issues. See `:help g:ale_history_log_output` for more information.\r\n\r\n## Bugs Fixed\r\n- When fixers like `yapf` failed, they were removing all of the lines in files. This has been fixed. #706 \r\n- The `brakeman` linter was throwing errors when no output was returned. This has been fixed. #716 \r\n- `ansible-lint` was reporting errors from other files. This has been fixed. #216 \r\n- ALE wasn't setting the configuration file when fixing files with `rubocop`. Now it does. #732 \r\n- The `ghc` linter was showing warning as errors. This has been fixed. #710\r\n- The `flow` linter didn't support older versions of flow. This has been fixed. #735\r\n- Rust linters should now work on Windows. They didn't before, due to how paths were handled. #736\r\n- ALE wasn't checking files on save if it also tried to fix files on save, and no changes were made. This has been fixed. #730 \r\n- When the shell was set to `fish`, some ALE commands didn't work. Now `\/bin\/sh` will be used instead when the shell is set to fish. #749 \r\n- Errors when ALE is unable to set signs will now be silenced. #560 #763","3":"## Notes\r\n- From this version and onward, ALE remembers the full output of recent commands by default, which helps with filing bug reports and fixing issues. See `:help g:ale_history_log_output` for more information.\r\n\r\n## Bugs Fixed\r\n- When fixers like `yapf` failed, they were removing all of the lines in files. This has been fixed. #706 \r\n- The `brakeman` linter was throwing errors when no output was returned. This has been fixed. #716 \r\n- `ansible-lint` was reporting errors from other files. This has been fixed. #216 \r\n- ALE wasn't setting the configuration file when fixing files with `rubocop`. Now it does. #732 \r\n- The `ghc` linter was showing warning as errors. This has been fixed. #710\r\n- The `flow` linter didn't support older versions of flow. This has been fixed. #735\r\n- Rust linters should now work on Windows. They didn't before, due to how paths were handled. #736\r\n- ALE wasn't checking files on save if it also tried to fix files on save, and no changes were made. This has been fixed. #730 \r\n- When the shell was set to `fish`, some ALE commands didn't work. Now `\/bin\/sh` will be used instead when the shell is set to fish. #749 \r\n- Errors when ALE is unable to set signs will now be silenced. #560 #763","package":"vim-ale-1.4.1.zip","4":"vim-ale-1.4.1.zip","src_id":"25434","5":"25434","creation_date":"1500749319","6":"1500749319"},{"0":"5449","vim_version":"8.0","1":"8.0","script_version":"1.4.0","2":"1.4.0","version_comment":"## Bugs Fixed\r\n- Escaping of strings for the shell on Windows has been fixed in a major way. Safe strings are passed on verbatim. Strings with spaces are quoted, and percents and quotes are doubled. All other strings have characters with special meanings escaped with carets (`^`).\r\n- ALE was checking files when `g:ale_run_on_insert_leave` was set to `1`, when it should only check buffers. This has been fixed.\r\n- ALE now uses the `BufWinEnter` event for `g:ale_lint_on_enter` instead of `BufEnter`, which should result in files only being checked when they need to be, and prevent problems with checking files again when moving across split windows. `FileChangedShellPost` is used to check if files are changed outside of Vim. If they are, then the `BufEnter` event will be used to check the file again.\r\n- When `g:ale_open_list` is set, ALE will now allow multiple loclist windows to be opened. #461 \r\n- ALE wasn't finding errors for Flow files when Flow returned relative paths. This has been fixed.\r\n- The Perl linter was showing some errors from other files. Now ALE checks that the errors come from a file with a matching name. #625\r\n- The stylelint linter was ignoring quite a few stylelint errors. This has been fixed. #629 \r\n- When checking files on disk, ALE was sometimes checking buffers where the file hasn't been saved to disk yet. This has been fixed. #651\r\n- Filename escaping has been fixed for the `kotlinc` linter. #662 \r\n- The `ghc-mod` linter will now filter out errors for other files. #690 \r\n- The `pylint` linter wasn't parsing a few errors. This has been fixed. #695\r\n\r\n## New Features\r\n- ALE can now help you fix your code, via a configurable set of integrations for programs for fixing code. See `:help ale-fix`. #541 \r\n- Python functions for fixing files will search for executables in virtualenv directories. #632\r\n- Linters can now add end column indexes and end lines for error highlights, for highlighting words for problems, etc.\r\n- ALE linting can now be disabled for particular buffers with `b:ale_enabled`. #371\r\n- Arbitrary buffer variables can be configured for filename patterns. See `:help g:ale_pattern_options` for more information. #371 \r\n- ALE now supports disabling linting of files above a configurable maximum file size. See `:help g:ale_maximum_file_size`.\r\n- ALE now supports balloon messages. See `:help g:ale_set_balloons`.\r\n- ALE now sets the filename as the quickfix and loclist titles. #588 \r\n- The quickfix window height can now be configured with `g:ale_list_window_size`.\r\n- You can now jump straight to the first or last problem with `:ALEFirst` or `:ALELast`. #616\r\n- ALE now makes results for a single linter available as soon as possible, instead of waiting for other running linters to complete. #406 \r\n- Linter problems types can now be re-mapped via a setting. See `:help g:ale_type_map` for more information. #536 \r\n- C and C++ linters are generally better at detecting the location of header files, but will never be perfect.\r\n\r\n## Misc Changes\r\n- The slower Go linters have been disabled by default. To re-enable them, see `:help ale-go-options`.\r\n\r\n## New Linters\r\n- Awk - gawk #638\r\n- C++ - clang-check #686, cpplint #546\r\n- FusionScript - fusion-lint #648\r\n- Haskell - ghc-mod #496\r\n- Java - checkstyle #551 \r\n- Koitlin - ktlint #610\r\n- Objective C - clang #568\r\n- Objective C++ - clang #568\r\n- TypeScript - eslint #668, tsserver #517\r\n- XML - xmllint #559 \r\n\r\n## New Fixers\r\n- JavaScript - eslint #541, prettier #571, prettier-eslint #571\r\n- Python - autopep8, isort, yapf\r\n- Ruby - rubocop #689\r\n- TypeScript - eslint #668\r\n\r\n## Linter Enhancements\r\n- The `eslint` linter will now output some end column indexes for better error highlighting.\r\n- The `eslint` linter  will now use `eslint_d`, where available, which can be much faster.\r\n- The `php` linter will now output some end column indexes for better error highlighting.\r\n- The executable can now be configured for the `rubocop` linter. #561\r\n- When an executable ends with `'bundle'`, The `rubocop` linter will now automatically add `' exec rubocop'` to the command for executing `rubocop` via Bundle. #561\r\n- The performance of `gometalinter` integration has been substantially improved by using the `--include` option. #566 \r\n- The `koitlinc` linter now supports getting import paths from Maven, just like the `javac` linter. #585 \r\n- The `perl` linter now shows warnings by default. #600 \r\n- The `cargo` and `rustc` linters now report problems with end column and line numbers. #602 \r\n- The `cargo` and `rustc` linters now report problems with more details. #601 \r\n- The `flake8` linter will now report exceptions thrown by `flake8`. #596 \r\n- The `flake8` linter will now include end colum indexes for better highlights for some problems. #538 \r\n- The `flake8` linter now describe E and W errors as style errors, which can be highlighted differently. #430\r\n- The `--version` check run for `vint` will now be run in the background. #624 \r\n- `'lint_file'` has been set to `1` for `nimcheck`, so only files on disk will be checked. #620 \r\n- The `percritic` linter now includes column numbers for problems. #640 \r\n- The `tslint` linter now distinguishes warnings from errors. #663\r\n- The `javac` linter now includes column numbers for better error highlighting. #660\r\n- The `phpcs` linter will now run locally installed versions where available by default. #666 \r\n- The `clang-tidy` linter will now detect `compile_commands.json` files, and let you override the build directory location. See `:help g:ale-cpp-options` #688\r\n- The `tslint` linter now uses the JSON format for parsing errors, which should work better between different versions, and includes end line and column numbers. #684\r\n- The `elm` linter now includes some general errors not previously reported. #637","3":"## Bugs Fixed\r\n- Escaping of strings for the shell on Windows has been fixed in a major way. Safe strings are passed on verbatim. Strings with spaces are quoted, and percents and quotes are doubled. All other strings have characters with special meanings escaped with carets (`^`).\r\n- ALE was checking files when `g:ale_run_on_insert_leave` was set to `1`, when it should only check buffers. This has been fixed.\r\n- ALE now uses the `BufWinEnter` event for `g:ale_lint_on_enter` instead of `BufEnter`, which should result in files only being checked when they need to be, and prevent problems with checking files again when moving across split windows. `FileChangedShellPost` is used to check if files are changed outside of Vim. If they are, then the `BufEnter` event will be used to check the file again.\r\n- When `g:ale_open_list` is set, ALE will now allow multiple loclist windows to be opened. #461 \r\n- ALE wasn't finding errors for Flow files when Flow returned relative paths. This has been fixed.\r\n- The Perl linter was showing some errors from other files. Now ALE checks that the errors come from a file with a matching name. #625\r\n- The stylelint linter was ignoring quite a few stylelint errors. This has been fixed. #629 \r\n- When checking files on disk, ALE was sometimes checking buffers where the file hasn't been saved to disk yet. This has been fixed. #651\r\n- Filename escaping has been fixed for the `kotlinc` linter. #662 \r\n- The `ghc-mod` linter will now filter out errors for other files. #690 \r\n- The `pylint` linter wasn't parsing a few errors. This has been fixed. #695\r\n\r\n## New Features\r\n- ALE can now help you fix your code, via a configurable set of integrations for programs for fixing code. See `:help ale-fix`. #541 \r\n- Python functions for fixing files will search for executables in virtualenv directories. #632\r\n- Linters can now add end column indexes and end lines for error highlights, for highlighting words for problems, etc.\r\n- ALE linting can now be disabled for particular buffers with `b:ale_enabled`. #371\r\n- Arbitrary buffer variables can be configured for filename patterns. See `:help g:ale_pattern_options` for more information. #371 \r\n- ALE now supports disabling linting of files above a configurable maximum file size. See `:help g:ale_maximum_file_size`.\r\n- ALE now supports balloon messages. See `:help g:ale_set_balloons`.\r\n- ALE now sets the filename as the quickfix and loclist titles. #588 \r\n- The quickfix window height can now be configured with `g:ale_list_window_size`.\r\n- You can now jump straight to the first or last problem with `:ALEFirst` or `:ALELast`. #616\r\n- ALE now makes results for a single linter available as soon as possible, instead of waiting for other running linters to complete. #406 \r\n- Linter problems types can now be re-mapped via a setting. See `:help g:ale_type_map` for more information. #536 \r\n- C and C++ linters are generally better at detecting the location of header files, but will never be perfect.\r\n\r\n## Misc Changes\r\n- The slower Go linters have been disabled by default. To re-enable them, see `:help ale-go-options`.\r\n\r\n## New Linters\r\n- Awk - gawk #638\r\n- C++ - clang-check #686, cpplint #546\r\n- FusionScript - fusion-lint #648\r\n- Haskell - ghc-mod #496\r\n- Java - checkstyle #551 \r\n- Koitlin - ktlint #610\r\n- Objective C - clang #568\r\n- Objective C++ - clang #568\r\n- TypeScript - eslint #668, tsserver #517\r\n- XML - xmllint #559 \r\n\r\n## New Fixers\r\n- JavaScript - eslint #541, prettier #571, prettier-eslint #571\r\n- Python - autopep8, isort, yapf\r\n- Ruby - rubocop #689\r\n- TypeScript - eslint #668\r\n\r\n## Linter Enhancements\r\n- The `eslint` linter will now output some end column indexes for better error highlighting.\r\n- The `eslint` linter  will now use `eslint_d`, where available, which can be much faster.\r\n- The `php` linter will now output some end column indexes for better error highlighting.\r\n- The executable can now be configured for the `rubocop` linter. #561\r\n- When an executable ends with `'bundle'`, The `rubocop` linter will now automatically add `' exec rubocop'` to the command for executing `rubocop` via Bundle. #561\r\n- The performance of `gometalinter` integration has been substantially improved by using the `--include` option. #566 \r\n- The `koitlinc` linter now supports getting import paths from Maven, just like the `javac` linter. #585 \r\n- The `perl` linter now shows warnings by default. #600 \r\n- The `cargo` and `rustc` linters now report problems with end column and line numbers. #602 \r\n- The `cargo` and `rustc` linters now report problems with more details. #601 \r\n- The `flake8` linter will now report exceptions thrown by `flake8`. #596 \r\n- The `flake8` linter will now include end colum indexes for better highlights for some problems. #538 \r\n- The `flake8` linter now describe E and W errors as style errors, which can be highlighted differently. #430\r\n- The `--version` check run for `vint` will now be run in the background. #624 \r\n- `'lint_file'` has been set to `1` for `nimcheck`, so only files on disk will be checked. #620 \r\n- The `percritic` linter now includes column numbers for problems. #640 \r\n- The `tslint` linter now distinguishes warnings from errors. #663\r\n- The `javac` linter now includes column numbers for better error highlighting. #660\r\n- The `phpcs` linter will now run locally installed versions where available by default. #666 \r\n- The `clang-tidy` linter will now detect `compile_commands.json` files, and let you override the build directory location. See `:help g:ale-cpp-options` #688\r\n- The `tslint` linter now uses the JSON format for parsing errors, which should work better between different versions, and includes end line and column numbers. #684\r\n- The `elm` linter now includes some general errors not previously reported. #637","package":"vim-ale-1.4.0.zip","4":"vim-ale-1.4.0.zip","src_id":"25359","5":"25359","creation_date":"1498598431","6":"1498598431"},{"0":"5449","vim_version":"8.0","1":"8.0","script_version":"1.3.1","2":"1.3.1","version_comment":"## Bugs Fixed\r\n- Shell escaping has been fixed pretty much everywhere. #540 \r\n- PHP error parsing has been fixed, so more errors will be parsed. #533\r\n- The `gometalinter` handler wasn't filtering file errors correctly. Now errors from other files will be filtered out. #553 \r\n- `csslint` errors without groups weren't being reported. This has been fixed. #555 \r\n- `pytlint` error columns were off-by-one. This has been fixed. #578\r\n- Fatal errors weren't being parsed for `ember-template-lint`. This has been fixed. #589 \r\n- ALE was sometimes highlighting entire lines when buffers were un-hidden. This problem was introduced in version 1.3.0. This bug has been fixed. #574","3":"## Bugs Fixed\r\n- Shell escaping has been fixed pretty much everywhere. #540 \r\n- PHP error parsing has been fixed, so more errors will be parsed. #533\r\n- The `gometalinter` handler wasn't filtering file errors correctly. Now errors from other files will be filtered out. #553 \r\n- `csslint` errors without groups weren't being reported. This has been fixed. #555 \r\n- `pytlint` error columns were off-by-one. This has been fixed. #578\r\n- Fatal errors weren't being parsed for `ember-template-lint`. This has been fixed. #589 \r\n- ALE was sometimes highlighting entire lines when buffers were un-hidden. This problem was introduced in version 1.3.0. This bug has been fixed. #574","package":"vim-ale-1.3.1.zip","4":"vim-ale-1.3.1.zip","src_id":"25285","5":"25285","creation_date":"1496768908","6":"1496768908"},{"0":"5449","vim_version":"8.0","1":"8.0","script_version":"1.3.0","2":"1.3.0","version_comment":"## Bugs Fixed\r\n- Highlights will now be cleared and restored when buffers are hidden and shown.\r\n\r\n## New Features\r\n- Files\/buffers will now be checked when the filetype is changed.\r\n- All ALE commands defined so far may now be combined with `|`. (`command! -bar ...`)\r\n- Commands `ALEEnable` and `ALEDisable` have been added for explicitly turning ALE on or off.\r\n- `g:ale_lint_on_text_changed` now accepts values `'never'`, `'normal'`, and `'always'` for controlling whether `TextChanged` or `TextChangedI` will be listened to. Old options `0` and `1` will continue to be supported until version 2.0.0.\r\n- An option `g:ale_lint_on_insert_leave` for triggering linting on leaving Insert mode. See `:help g:ale_lint_on_insert_leave`.\r\n- Line highlights may now be set for set for signs. See `:help g:ale_set_signs`.\r\n- For all C and C++ linters, errors inside of headers will be reported on the `#include` lines.\r\n- Filetypes may now be aliased to multiple filetypes in a `List`. See `:help g:ale_linter_aliases`.\r\n- All settings for all linters should now be dynamically evaluated, so settings can be changed while Vim is running.\r\n\r\n## New Linters\r\n- ASM - gcc\r\n- Crystal - crystal\r\n- Elixir - dogma\r\n- eruby - erb\r\n- Go - staticcheck, gosimple\r\n- handlebars - ember-template-lint\r\n- Koitlin - koitlinc\r\n- Markdown - Vale\r\n- ReasonML - merlin\r\n- RPM Spec - rpmlint\r\n- Ruby - brakeman, reek, ruby\r\n- SQL - sqlint\r\n- Text - Vale\r\n\r\n## Linter Enhancements\r\n- `cargo check` may now be used instead of `cargo build` See `:help g:ale_rust_cargo_use_check`.\r\n- The `cargo` linter now uses `lint_file` option so it will only run when files are opened, saved, etc.\r\n- The `rubocop` linter's error levels have been improved.\r\n- The `eslint` linter will now automatically detect eslint installed via `create-react-app`.\r\n- The `eslint` linter will now report invalid configuration file settings as errors at line 1.\r\n- The `tslint` linter will now detect executables installed in `node_modules`.\r\n- The `csslint` linter will now use `.csslintrc` files defined in ancestor directories.\r\n- The `javac` linter will now create `.class` files in temporary directories, deleted at the end of lint cycles.\r\n- The `javac` linter will now include source paths like `src\/main\/java`.\r\n- The `javac` linter will now get class paths from Maven automatically.\r\n- The `javac` linter will now report symbol names in undefined symbol errors for types.\r\n- The executable and some options may now be configured for the `foodcritic` linter.\r\n- The `nimcheck` linter now turns thread support on, so code using threads can be checked.\r\n- Error parsing for the `sml` linter has been improved.\r\n- The executable and some options may now be configured for the `shellcheck` linter.\r\n- The `go build` linter will now only check files on disk, but is now capable of understanding paths correctly.\r\n- Options and the executable can now be set for the `puppetlint` linter.\r\n- The Fortran `gcc` linter can now be configured to check fixed form layouts. See `:help g:ale_fortran_gcc_use_free_form`\r\n- The Fortran `gcc` linter's executable can now be configured. See `:help g:ale_fortran_gcc_executable`\r\n- The `flow` linter will now filter out errors\/warnings from other files.\r\n- The `tslint` linter can now be set to prefer the global executable, like many other linters.\r\n- The `laucheck` linter can now be configured with different options.\r\n- The `cppcheck` linter will now detect and use `compile_commands.json` files and switch to the directory they are in, when detected in ancestor directories.\r\n- The `clang-tidy` linter now checks files on disk and uses `compile_commands.json` files, with no extra options by default. See `:help ale-cpp-clangtidy`\r\n- The `pylint` linter will now detect versions of the program in virtualenv automatically. See `:help g:ale_python_pylint_use_global` for disabling this behaviour.\r\n- The `pylint` linter will now check files on disk, and understand import paths.\r\n- The `mypy` linter will now detect versions of the program in virtualenv automatically. See `:help g:ale_python_mypy_use_global` for disabling this behaviour.\r\n- The `mypy` linter will now check files on disk, and understand import paths.\r\n- The `flake8` linter will now detect versions of the program in virtualenv automatically. See `:help g:ale_python_flake8_use_global` for disabling this behaviour.\r\n\r\n## Misc Changes\r\n- Linters now run when files are saved by default.\r\n- The setting `g:ale_linters_sh_shell_default_shell` has been renamed to `g:ale_sh_shell_default_shell`.\r\n- The setting `g:ale_linters_sh_shellcheck_exclusions` has been renamed to `g:ale_sh_shellcheck_exclusions`.","3":"## Bugs Fixed\r\n- Highlights will now be cleared and restored when buffers are hidden and shown.\r\n\r\n## New Features\r\n- Files\/buffers will now be checked when the filetype is changed.\r\n- All ALE commands defined so far may now be combined with `|`. (`command! -bar ...`)\r\n- Commands `ALEEnable` and `ALEDisable` have been added for explicitly turning ALE on or off.\r\n- `g:ale_lint_on_text_changed` now accepts values `'never'`, `'normal'`, and `'always'` for controlling whether `TextChanged` or `TextChangedI` will be listened to. Old options `0` and `1` will continue to be supported until version 2.0.0.\r\n- An option `g:ale_lint_on_insert_leave` for triggering linting on leaving Insert mode. See `:help g:ale_lint_on_insert_leave`.\r\n- Line highlights may now be set for set for signs. See `:help g:ale_set_signs`.\r\n- For all C and C++ linters, errors inside of headers will be reported on the `#include` lines.\r\n- Filetypes may now be aliased to multiple filetypes in a `List`. See `:help g:ale_linter_aliases`.\r\n- All settings for all linters should now be dynamically evaluated, so settings can be changed while Vim is running.\r\n\r\n## New Linters\r\n- ASM - gcc\r\n- Crystal - crystal\r\n- Elixir - dogma\r\n- eruby - erb\r\n- Go - staticcheck, gosimple\r\n- handlebars - ember-template-lint\r\n- Koitlin - koitlinc\r\n- Markdown - Vale\r\n- ReasonML - merlin\r\n- RPM Spec - rpmlint\r\n- Ruby - brakeman, reek, ruby\r\n- SQL - sqlint\r\n- Text - Vale\r\n\r\n## Linter Enhancements\r\n- `cargo check` may now be used instead of `cargo build` See `:help g:ale_rust_cargo_use_check`.\r\n- The `cargo` linter now uses `lint_file` option so it will only run when files are opened, saved, etc.\r\n- The `rubocop` linter's error levels have been improved.\r\n- The `eslint` linter will now automatically detect eslint installed via `create-react-app`.\r\n- The `eslint` linter will now report invalid configuration file settings as errors at line 1.\r\n- The `tslint` linter will now detect executables installed in `node_modules`.\r\n- The `csslint` linter will now use `.csslintrc` files defined in ancestor directories.\r\n- The `javac` linter will now create `.class` files in temporary directories, deleted at the end of lint cycles.\r\n- The `javac` linter will now include source paths like `src\/main\/java`.\r\n- The `javac` linter will now get class paths from Maven automatically.\r\n- The `javac` linter will now report symbol names in undefined symbol errors for types.\r\n- The executable and some options may now be configured for the `foodcritic` linter.\r\n- The `nimcheck` linter now turns thread support on, so code using threads can be checked.\r\n- Error parsing for the `sml` linter has been improved.\r\n- The executable and some options may now be configured for the `shellcheck` linter.\r\n- The `go build` linter will now only check files on disk, but is now capable of understanding paths correctly.\r\n- Options and the executable can now be set for the `puppetlint` linter.\r\n- The Fortran `gcc` linter can now be configured to check fixed form layouts. See `:help g:ale_fortran_gcc_use_free_form`\r\n- The Fortran `gcc` linter's executable can now be configured. See `:help g:ale_fortran_gcc_executable`\r\n- The `flow` linter will now filter out errors\/warnings from other files.\r\n- The `tslint` linter can now be set to prefer the global executable, like many other linters.\r\n- The `laucheck` linter can now be configured with different options.\r\n- The `cppcheck` linter will now detect and use `compile_commands.json` files and switch to the directory they are in, when detected in ancestor directories.\r\n- The `clang-tidy` linter now checks files on disk and uses `compile_commands.json` files, with no extra options by default. See `:help ale-cpp-clangtidy`\r\n- The `pylint` linter will now detect versions of the program in virtualenv automatically. See `:help g:ale_python_pylint_use_global` for disabling this behaviour.\r\n- The `pylint` linter will now check files on disk, and understand import paths.\r\n- The `mypy` linter will now detect versions of the program in virtualenv automatically. See `:help g:ale_python_mypy_use_global` for disabling this behaviour.\r\n- The `mypy` linter will now check files on disk, and understand import paths.\r\n- The `flake8` linter will now detect versions of the program in virtualenv automatically. See `:help g:ale_python_flake8_use_global` for disabling this behaviour.\r\n\r\n## Misc Changes\r\n- Linters now run when files are saved by default.\r\n- The setting `g:ale_linters_sh_shell_default_shell` has been renamed to `g:ale_sh_shell_default_shell`.\r\n- The setting `g:ale_linters_sh_shellcheck_exclusions` has been renamed to `g:ale_sh_shellcheck_exclusions`.","package":"vim-ale-1.3.0.zip","4":"vim-ale-1.3.0.zip","src_id":"25156","5":"25156","creation_date":"1494182448","6":"1494182448"},{"0":"5449","vim_version":"8.0","1":"8.0","script_version":"1.2.1","2":"1.2.1","version_comment":"## Bugs Fixed\r\n- Exceptions will no longer be thrown when the checks for conflicting plugins are run _before_ the rest of the ALE plugin code.\r\n- Various linters no longer set errors at column 1, when there is no column set.\r\n- Linting will no longer be performed from inside of a command window.\r\n- Errors will now be returned for `zsh` scripts for the `shell` linter.\r\n- The `vint` linter wasn't setting the `--no-color` option for versions 0.3.7 and above, due to a typo. This has been fixed.\r\n- The `php` linter was parsing some errors twice. This has been fixed.\r\n- Highlights will now be cleared when buffers are unloaded, so matches will not appear in the wrong files.","3":"## Bugs Fixed\r\n- Exceptions will no longer be thrown when the checks for conflicting plugins are run _before_ the rest of the ALE plugin code.\r\n- Various linters no longer set errors at column 1, when there is no column set.\r\n- Linting will no longer be performed from inside of a command window.\r\n- Errors will now be returned for `zsh` scripts for the `shell` linter.\r\n- The `vint` linter wasn't setting the `--no-color` option for versions 0.3.7 and above, due to a typo. This has been fixed.\r\n- The `php` linter was parsing some errors twice. This has been fixed.\r\n- Highlights will now be cleared when buffers are unloaded, so matches will not appear in the wrong files.","package":"vim-ale-1.2.1.zip","4":"vim-ale-1.2.1.zip","src_id":"25096","5":"25096","creation_date":"1493486703","6":"1493486703"},{"0":"5449","vim_version":"8.0","1":"8.0","script_version":"1.2.0","2":"1.2.0","version_comment":"## Bugs Fixed\r\n- Signs will now be unplaced for Italian users.\r\n- Fixed a bug where loclist items could be set for the wrong buffers.\r\n\r\n## New Features\r\n- A command `:ALEToggle` has been added for turning ALE on or off temporarily.\r\n- A command `:ALELint` has been added for running ALE manually.\r\n- A command `:ALEDetail` has been added for showing more details for an error at the cursor.\r\n- Linters can now use a `read_buffer` option for enabling\/disabling stdin input.\r\n- Linters can now use a `lint_file` option for running checks against files, instead of Vim buffers.\r\n- ALE now highlights errors in the buffer. See  `:help g:ale_set_highlights`\r\n- The `:ALEInfo` command now outputs linter variables.\r\n- The `:ALEInfo` command now outputs a command history. See `:help g:ale_history_enabled`\r\n- ALE will no longer complain if it can't work for empty filetypes or git commits.\r\n- If ALE fails to load properly, it should now still emit airline statusline messages.\r\n\r\n## New Linters\r\n- AsciiDoc - proselint\r\n- C++ - clang\r\n- CMake - cmakelint\r\n- Haml - hamllint\r\n- Haskell - hdevtools\r\n- HTML - proselint\r\n- Java - javac\r\n- JavaScript - standard, xo\r\n- nim - nim\r\n- nix - nix-instantiate\r\n- nroff - proselint\r\n- PHP - phpmd\r\n- Pod - proselint\r\n- reStructuredText - proselint\r\n- Slim - slim-lint\r\n- SML - smlnj\r\n- Texinfo - proselint\r\n- Vim help - proselint\r\n- XHTML - proselint\r\n\r\n## Linter Enhancements\r\n- The `coffee` and `coffeelint` linters now attempt to use the versions of those executables from `node_modules`, if available.\r\n- The `coffelint` linter will now parse more errors.\r\n- The `credo` linter now includes the filename of the file being checked, which can be useful for various checks.\r\n- The `flow` linter will not now no longer run if no `.flowconfig` file exists in an ancestor directory.\r\n- You can now configure options for the `stylelint` linter.\r\n- The `gfortran` linter now supports more kinds of error output.\r\n- The `yamllint` linter can be now be configured with an executable path and options.\r\n- The `pylint` linter now includes the symbol (a short name) for error types.\r\n- PHP error parsing has been improved, so more errors are handled.\r\n- The `eslint` linter will now report problems with the configuration file, using `:ALEDetail`.\r\n- The `perl` linter now supports options. See `:help ale-linter-options-perl-perl`.\r\n- The `clang` and `gcc` linters now support header includes in the same directories files are in.\r\n- The `erlc` linter will no longer leave compiled files lying around.\r\n- The `tslint` linter will now find configuration files, and allow the executable and configuration file to be configured.\r\n\r\n## Misc Changes\r\n- $TMPDIR will now automatically be set to \/tmp on Unix if it is not set.\r\n- ALE will now only run the `cargo` linter for Rust by default. To run other linters, modify `g:ale_linters` appropriately. See `:help ale-integration-rust`.\r\n- ALE will now echo the cursor error messages when linting finishes or when leaving insert mode.","3":"## Bugs Fixed\r\n- Signs will now be unplaced for Italian users.\r\n- Fixed a bug where loclist items could be set for the wrong buffers.\r\n\r\n## New Features\r\n- A command `:ALEToggle` has been added for turning ALE on or off temporarily.\r\n- A command `:ALELint` has been added for running ALE manually.\r\n- A command `:ALEDetail` has been added for showing more details for an error at the cursor.\r\n- Linters can now use a `read_buffer` option for enabling\/disabling stdin input.\r\n- Linters can now use a `lint_file` option for running checks against files, instead of Vim buffers.\r\n- ALE now highlights errors in the buffer. See  `:help g:ale_set_highlights`\r\n- The `:ALEInfo` command now outputs linter variables.\r\n- The `:ALEInfo` command now outputs a command history. See `:help g:ale_history_enabled`\r\n- ALE will no longer complain if it can't work for empty filetypes or git commits.\r\n- If ALE fails to load properly, it should now still emit airline statusline messages.\r\n\r\n## New Linters\r\n- AsciiDoc - proselint\r\n- C++ - clang\r\n- CMake - cmakelint\r\n- Haml - hamllint\r\n- Haskell - hdevtools\r\n- HTML - proselint\r\n- Java - javac\r\n- JavaScript - standard, xo\r\n- nim - nim\r\n- nix - nix-instantiate\r\n- nroff - proselint\r\n- PHP - phpmd\r\n- Pod - proselint\r\n- reStructuredText - proselint\r\n- Slim - slim-lint\r\n- SML - smlnj\r\n- Texinfo - proselint\r\n- Vim help - proselint\r\n- XHTML - proselint\r\n\r\n## Linter Enhancements\r\n- The `coffee` and `coffeelint` linters now attempt to use the versions of those executables from `node_modules`, if available.\r\n- The `coffelint` linter will now parse more errors.\r\n- The `credo` linter now includes the filename of the file being checked, which can be useful for various checks.\r\n- The `flow` linter will not now no longer run if no `.flowconfig` file exists in an ancestor directory.\r\n- You can now configure options for the `stylelint` linter.\r\n- The `gfortran` linter now supports more kinds of error output.\r\n- The `yamllint` linter can be now be configured with an executable path and options.\r\n- The `pylint` linter now includes the symbol (a short name) for error types.\r\n- PHP error parsing has been improved, so more errors are handled.\r\n- The `eslint` linter will now report problems with the configuration file, using `:ALEDetail`.\r\n- The `perl` linter now supports options. See `:help ale-linter-options-perl-perl`.\r\n- The `clang` and `gcc` linters now support header includes in the same directories files are in.\r\n- The `erlc` linter will no longer leave compiled files lying around.\r\n- The `tslint` linter will now find configuration files, and allow the executable and configuration file to be configured.\r\n\r\n## Misc Changes\r\n- $TMPDIR will now automatically be set to \/tmp on Unix if it is not set.\r\n- ALE will now only run the `cargo` linter for Rust by default. To run other linters, modify `g:ale_linters` appropriately. See `:help ale-integration-rust`.\r\n- ALE will now echo the cursor error messages when linting finishes or when leaving insert mode.","package":"vim-ale-1.2.0.zip","4":"vim-ale-1.2.0.zip","src_id":"25047","5":"25047","creation_date":"1490564672","6":"1490564672"},{"0":"5449","vim_version":"8.0","1":"8.0","script_version":"1.1.1","2":"1.1.1","version_comment":"## Bugs Fixed\r\n\r\n* The Pug linter wasn't parsing errors correctly. This has been fixed.\r\n* The gcc\/gfortran linter should now parse errors from more versions.\r\n* Parsing of TypeScript `typecheck` errors has been fixed for some filenames containing the string `ts`.\r\n* The commands for navigating between errors\/warnings should now correctly filter out other buffers.\r\n* The commands for navigating between errors\/warnings will now prefer to use the quickfix list, if `g:ale_set_quickfix` is on.","3":"## Bugs Fixed\r\n\r\n* The Pug linter wasn't parsing errors correctly. This has been fixed.\r\n* The gcc\/gfortran linter should now parse errors from more versions.\r\n* Parsing of TypeScript `typecheck` errors has been fixed for some filenames containing the string `ts`.\r\n* The commands for navigating between errors\/warnings should now correctly filter out other buffers.\r\n* The commands for navigating between errors\/warnings will now prefer to use the quickfix list, if `g:ale_set_quickfix` is on.","package":"vim-ale-1.1.1.zip","4":"vim-ale-1.1.1.zip","src_id":"24985","5":"24985","creation_date":"1487715558","6":"1487715558"},{"0":"5449","vim_version":"8.0","1":"8.0","script_version":"1.1.0","2":"1.1.0","version_comment":"## New Features\r\n- ALE now splits filetypes containing `.` (a dot), and will run all linters for each component of a compound filetype, so files with type `foo.bar` will use linters for filetypes `foo` and `bar`.\r\n- ALE now offers commands and `` keybinds for moving between warnings and errors. See `:help ale-navigation-commands` for more information.\r\n- ALE can now automatically open a window to show the list of errors. See `:help g:ale_open_list` for more information.\r\n- ALE now allows you to get some information about the current linters with a new `:ALEInfo` command.\r\n- ALE now includes a mechanism for chaining commands for running linters, for any linters which need to run multiple commands to check for errors.\r\n\r\n## New Linters\r\n\r\nSupport has been added for the following linters.\r\n- Ansible - ansiblelint\r\n- C\/C++ - clang, cppcheck\r\n- C# - mcs\r\n- Chef - foodcritic\r\n- CSS - stylelint\r\n- Dockerfile - hadolint\r\n- Elm - elm-make\r\n- Erland - erlc\r\n- Go - go build\r\n- JavaScript - flow\r\n- LatTex - chtex, lacheck\r\n- Markdown - mdl, proselint\r\n- MATLAB - mlint\r\n- OCaml - merlin (Another Vim plugin is required)\r\n- PHP - hack\r\n- Puppet - puppet, puppet-lint\r\n- Python - mypy, pylint\r\n- SASS - stylelint\r\n- SCSS - stylelint\r\n- Swift - swiftlint\r\n- Text - proselint\r\n- TypeScript - tslint, typecheck\r\n\r\n## Linter Enhancements\r\n- The `eslint` and `jshint` linters for JavaScript will now attempt to run eslint installed in `node_modules` directories first. The `g:ale_javascript_eslint_use_global` or `g:ale_javascript_jshint_use_global` variables can be set to `1` to force ALE to use the global executables.\r\n- The `eslint` linter can now be configured with more options.\r\n- The default flags for `gcc` and `g++` were changed to use the latest C and C++ standards by default.\r\n- The `htmlhint` options can now be customised with a global variable.\r\n- `htmlhint` will now search for executables in `node_modules` directories to run.\r\n- The `shellcheck` linter now uses Vim's special buffer variables for detecting the shell dialect.\r\n- The `flake8` linter now accept variables for configuring the executable and the command line arguments.\r\n- The `flake8` linter is now informed with the filename, which plugins can use.\r\n- The Haksell linters should produce better error messages.\r\n- C and C++ linter options can now be changed dynamically.\r\n- The Verilator linter was improved so it only produces warnings or errors for the file you are editing.\r\n- The DMD linter should now run on Windows, as the special Linux Bash script has been replaced with\r\n  use of the new command chaining feature.\r\n- The Vint linter for Vim files now recognises commands specific to NeoVim when running under NeoVim.\r\n\r\n## Misc Changes\r\n- The stdin-wrapper script for Unix systems has been simplified, and should see increased support for various systems.\r\n- A bug was fixed with this plugin and newer versions of NeoVim which altered the job control API slightly, which broke everything.","3":"## New Features\r\n- ALE now splits filetypes containing `.` (a dot), and will run all linters for each component of a compound filetype, so files with type `foo.bar` will use linters for filetypes `foo` and `bar`.\r\n- ALE now offers commands and `` keybinds for moving between warnings and errors. See `:help ale-navigation-commands` for more information.\r\n- ALE can now automatically open a window to show the list of errors. See `:help g:ale_open_list` for more information.\r\n- ALE now allows you to get some information about the current linters with a new `:ALEInfo` command.\r\n- ALE now includes a mechanism for chaining commands for running linters, for any linters which need to run multiple commands to check for errors.\r\n\r\n## New Linters\r\n\r\nSupport has been added for the following linters.\r\n- Ansible - ansiblelint\r\n- C\/C++ - clang, cppcheck\r\n- C# - mcs\r\n- Chef - foodcritic\r\n- CSS - stylelint\r\n- Dockerfile - hadolint\r\n- Elm - elm-make\r\n- Erland - erlc\r\n- Go - go build\r\n- JavaScript - flow\r\n- LatTex - chtex, lacheck\r\n- Markdown - mdl, proselint\r\n- MATLAB - mlint\r\n- OCaml - merlin (Another Vim plugin is required)\r\n- PHP - hack\r\n- Puppet - puppet, puppet-lint\r\n- Python - mypy, pylint\r\n- SASS - stylelint\r\n- SCSS - stylelint\r\n- Swift - swiftlint\r\n- Text - proselint\r\n- TypeScript - tslint, typecheck\r\n\r\n## Linter Enhancements\r\n- The `eslint` and `jshint` linters for JavaScript will now attempt to run eslint installed in `node_modules` directories first. The `g:ale_javascript_eslint_use_global` or `g:ale_javascript_jshint_use_global` variables can be set to `1` to force ALE to use the global executables.\r\n- The `eslint` linter can now be configured with more options.\r\n- The default flags for `gcc` and `g++` were changed to use the latest C and C++ standards by default.\r\n- The `htmlhint` options can now be customised with a global variable.\r\n- `htmlhint` will now search for executables in `node_modules` directories to run.\r\n- The `shellcheck` linter now uses Vim's special buffer variables for detecting the shell dialect.\r\n- The `flake8` linter now accept variables for configuring the executable and the command line arguments.\r\n- The `flake8` linter is now informed with the filename, which plugins can use.\r\n- The Haksell linters should produce better error messages.\r\n- C and C++ linter options can now be changed dynamically.\r\n- The Verilator linter was improved so it only produces warnings or errors for the file you are editing.\r\n- The DMD linter should now run on Windows, as the special Linux Bash script has been replaced with\r\n  use of the new command chaining feature.\r\n- The Vint linter for Vim files now recognises commands specific to NeoVim when running under NeoVim.\r\n\r\n## Misc Changes\r\n- The stdin-wrapper script for Unix systems has been simplified, and should see increased support for various systems.\r\n- A bug was fixed with this plugin and newer versions of NeoVim which altered the job control API slightly, which broke everything.","package":"vim-ale-1.1.0.zip","4":"vim-ale-1.1.0.zip","src_id":"24955","5":"24955","creation_date":"1486669011","6":"1486669011"},{"0":"5449","vim_version":"8.0","1":"8.0","script_version":"1.0.0","2":"1.0.0","version_comment":"This is the initial stable release of ALE, the asynchronous linting engine for Vim.\r\n\r\n## Features Implemented\r\n\r\n* ALE will run a variety of linters for various programming languages. For a full list of supported linters, please consult the help file.\r\n* ALE will update the loclist when errors\/warnings are found.\r\n* ALE will echo messages when the cursor moves over warnings or errors.\r\n* ALE will show signs in the sign gutter when errors or warnings are found.\r\n* ALE supports functions for showing statuses in the statusline, with some integration with vim-airline.\r\n\r\nsha256sum: \r\n498d5834472f26d06836700840b92a5ad440189309e5ce91983769739fcf4244  vim-ale-1.0.0.zip","3":"This is the initial stable release of ALE, the asynchronous linting engine for Vim.\r\n\r\n## Features Implemented\r\n\r\n* ALE will run a variety of linters for various programming languages. For a full list of supported linters, please consult the help file.\r\n* ALE will update the loclist when errors\/warnings are found.\r\n* ALE will echo messages when the cursor moves over warnings or errors.\r\n* ALE will show signs in the sign gutter when errors or warnings are found.\r\n* ALE supports functions for showing statuses in the statusline, with some integration with vim-airline.\r\n\r\nsha256sum: \r\n498d5834472f26d06836700840b92a5ad440189309e5ce91983769739fcf4244  vim-ale-1.0.0.zip","package":"vim-ale-1.0.0.zip","4":"vim-ale-1.0.0.zip","src_id":"24653","5":"24653","creation_date":"1476914701","6":"1476914701"}]},"5448":{"script_id":"5448","0":"5448","script_name":"vim-zim","1":"vim-zim","script_type":"utility","2":"utility","summary":"Zim desktop wiki syntax and helper functions","3":"Zim desktop wiki syntax and helper functions","description":"Zim desktop wiki (http:\/\/zim-wiki.org\/) integration for Vim. \r\n\r\nZim is a graphical desktop wiki application, which is useful for browsing or sharing with others. Since it stores its files in .txt format, it's straightforward to integrate with Vim. This script is similar to:\r\nhttp:\/\/www.vim.org\/scripts\/script.php?script_id=3703\r\nhttp:\/\/www.vim.org\/scripts\/script.php?script_id=5231\r\n\r\nOne notable difference is the addition of several keyboard mappings for bolding, italicizing, highlighting, or striking text while working with a Zim file.\r\n\r\nPlease note, as of writing (2016-09-13, version 0.1), the CreateZimHeader() function does not support Linux and probably needs minor tweaks for your time zone, due to buggy strftime() in Windows I worked around.","4":"Zim desktop wiki (http:\/\/zim-wiki.org\/) integration for Vim. \r\n\r\nZim is a graphical desktop wiki application, which is useful for browsing or sharing with others. Since it stores its files in .txt format, it's straightforward to integrate with Vim. This script is similar to:\r\nhttp:\/\/www.vim.org\/scripts\/script.php?script_id=3703\r\nhttp:\/\/www.vim.org\/scripts\/script.php?script_id=5231\r\n\r\nOne notable difference is the addition of several keyboard mappings for bolding, italicizing, highlighting, or striking text while working with a Zim file.\r\n\r\nPlease note, as of writing (2016-09-13, version 0.1), the CreateZimHeader() function does not support Linux and probably needs minor tweaks for your time zone, due to buggy strftime() in Windows I worked around.","install_details":"Unpack the .zip file in your Vim config folder, or download from https:\/\/github.com\/jakykong\/vim-zim if you use Pathogen or similar.","5":"Unpack the .zip file in your Vim config folder, or download from https:\/\/github.com\/jakykong\/vim-zim if you use Pathogen or similar.","first_name":"Jack","6":"Jack","last_name":"Mudge","7":"Mudge","releases":[{"0":"5448","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"vim-zim.zip","4":"vim-zim.zip","src_id":"24524","5":"24524","creation_date":"1473800951","6":"1473800951"}]},"5447":{"script_id":"5447","0":"5447","script_name":"pgn.vim","1":"pgn.vim","script_type":"syntax","2":"syntax","summary":"syntax highlighting for .pgn (chess) files ","3":"syntax highlighting for .pgn (chess) files ","description":"Highlights tag pairs, movetext and comments of Portable Game Notation (PGN) files, which is the most common format for computer processing of chess games.\r\n\r\nRecognizes standard algebraic notation and other commonly used notations, as seen on the Wikipedia page for algebraic notation.\r\n\r\nIt is a new version of Charles Ford\\'s original script, published on this site on 2003-06-14.","4":"Highlights tag pairs, movetext and comments of Portable Game Notation (PGN) files, which is the most common format for computer processing of chess games.\r\n\r\nRecognizes standard algebraic notation and other commonly used notations, as seen on the Wikipedia page for algebraic notation.\r\n\r\nIt is a new version of Charles Ford\\'s original script, published on this site on 2003-06-14.","install_details":"Put the file in your $VIMRUNTIME\/syntax\/ directory. \r\nThen in your $VIMRUNTIME\/filetype.vim file, add this line: \r\n\r\nau BufNewFile,BufRead *.pgn    setf pgn","5":"Put the file in your $VIMRUNTIME\/syntax\/ directory. \r\nThen in your $VIMRUNTIME\/filetype.vim file, add this line: \r\n\r\nau BufNewFile,BufRead *.pgn    setf pgn","first_name":"Ryan","6":"Ryan","last_name":"Sarson","7":"Sarson","releases":[{"0":"5447","vim_version":"8.2","1":"8.2","script_version":"2.1","2":"2.1","version_comment":"null move numbers","3":"null move numbers","package":"pgn.vim","4":"pgn.vim","src_id":"28023","5":"28023","creation_date":"1651377644","6":"1651377644"},{"0":"5447","vim_version":"7.0","1":"7.0","script_version":"2.0","2":"2.0","version_comment":"improved pattern matching, recognizes more commonly used notations","3":"improved pattern matching, recognizes more commonly used notations","package":"pgn.vim","4":"pgn.vim","src_id":"25903","5":"25903","creation_date":"1522159491","6":"1522159491"},{"0":"5447","vim_version":"7.4","1":"7.4","script_version":"1.0","2":"1.0","version_comment":"complete rewrite","3":"complete rewrite","package":"pgn.vim","4":"pgn.vim","src_id":"24529","5":"24529","creation_date":"1473861552","6":"1473861552"}]},"5446":{"script_id":"5446","0":"5446","script_name":"git-switcher.vim","1":"git-switcher.vim","script_type":"utility","2":"utility","summary":"Automatically save and load vim session based on switching of git branch.","3":"Automatically save and load vim session based on switching of git branch.","description":"git-switcher provide the save and load of the session based on switching of git branch. This plugin can be used for session management even if it is outside of git directory.\r\n\r\nHomepage: https:\/\/github.com\/ToruIwashita\/git-switcher.vim","4":"git-switcher provide the save and load of the session based on switching of git branch. This plugin can be used for session management even if it is outside of git directory.\r\n\r\nHomepage: https:\/\/github.com\/ToruIwashita\/git-switcher.vim","install_details":"","5":"","first_name":"Toru","6":"Toru","last_name":"Hoyano","7":"Hoyano","releases":[{"0":"5446","vim_version":"8.2","1":"8.2","script_version":"1.12.0","2":"1.12.0","version_comment":"Add gsw_save_non_project_session_confirm option.","3":"Add gsw_save_non_project_session_confirm option.","package":"git-switcher.vim-1.12.0.zip","4":"git-switcher.vim-1.12.0.zip","src_id":"27386","5":"27386","creation_date":"1606511564","6":"1606511564"},{"0":"5446","vim_version":"8.0","1":"8.0","script_version":"1.11.0","2":"1.11.0","version_comment":"Add feature to save Gutentags state to a session.","3":"Add feature to save Gutentags state to a session.","package":"git-switcher.vim-1.11.0.zip","4":"git-switcher.vim-1.11.0.zip","src_id":"27179","5":"27179","creation_date":"1590629410","6":"1590629410"},{"0":"5446","vim_version":"8.0","1":"8.0","script_version":"1.10.1","2":"1.10.1","version_comment":"Fix NERDTree state bug.","3":"Fix NERDTree state bug.","package":"git-switcher.vim-1.10.1.zip","4":"git-switcher.vim-1.10.1.zip","src_id":"27178","5":"27178","creation_date":"1590627657","6":"1590627657"},{"0":"5446","vim_version":"8.0","1":"8.0","script_version":"1.10.0","2":"1.10.0","version_comment":"Fix NERDTree state bug.\r\nAdd feature to save Tagbar state to a session.","3":"Fix NERDTree state bug.\r\nAdd feature to save Tagbar state to a session.","package":"git-switcher.vim-1.10.0.zip","4":"git-switcher.vim-1.10.0.zip","src_id":"27161","5":"27161","creation_date":"1589650797","6":"1589650797"},{"0":"5446","vim_version":"8.0","1":"8.0","script_version":"1.9.0","2":"1.9.0","version_comment":"Add feature to save NERDTree state to a session.","3":"Add feature to save NERDTree state to a session.","package":"git-switcher.vim-1.9.0.zip","4":"git-switcher.vim-1.9.0.zip","src_id":"26042","5":"26042","creation_date":"1529003167","6":"1529003167"},{"0":"5446","vim_version":"8.0","1":"8.0","script_version":"1.8.0","2":"1.8.0","version_comment":"Add command to remove all merged branches of local repository.\r\n","3":"Add command to remove all merged branches of local repository.\r\n","package":"git-switcher.vim-1.8.0.zip","4":"git-switcher.vim-1.8.0.zip","src_id":"25795","5":"25795","creation_date":"1516592347","6":"1516592347"},{"0":"5446","vim_version":"8.0","1":"8.0","script_version":"1.7.0","2":"1.7.0","version_comment":"Add feature to perform git pull and git fetch asynchronously.\r\n","3":"Add feature to perform git pull and git fetch asynchronously.\r\n","package":"git-switcher.vim-1.7.0.zip","4":"git-switcher.vim-1.7.0.zip","src_id":"25742","5":"25742","creation_date":"1514346493","6":"1514346493"},{"0":"5446","vim_version":"8.0","1":"8.0","script_version":"1.6.2","2":"1.6.2","version_comment":"Make checktime with silent!","3":"Make checktime with silent!","package":"git-switcher.vim-1.6.2.zip","4":"git-switcher.vim-1.6.2.zip","src_id":"25673","5":"25673","creation_date":"1512002843","6":"1512002843"},{"0":"5446","vim_version":"8.0","1":"8.0","script_version":"1.6.1","2":"1.6.1","version_comment":"Fix bug that unnecessary message is displayed.","3":"Fix bug that unnecessary message is displayed.","package":"git-switcher.vim-1.6.1.zip","4":"git-switcher.vim-1.6.1.zip","src_id":"25610","5":"25610","creation_date":"1508228516","6":"1508228516"},{"0":"5446","vim_version":"8.0","1":"8.0","script_version":"1.6.0","2":"1.6.0","version_comment":"Windows support\r\n","3":"Windows support\r\n","package":"git-switcher.vim-1.6.0.zip","4":"git-switcher.vim-1.6.0.zip","src_id":"25605","5":"25605","creation_date":"1507605934","6":"1507605934"},{"0":"5446","vim_version":"8.0","1":"8.0","script_version":"1.5.1","2":"1.5.1","version_comment":"Add GswRemove command to delete specified branch.","3":"Add GswRemove command to delete specified branch.","package":"git-switcher.vim-1.5.1.zip","4":"git-switcher.vim-1.5.1.zip","src_id":"25564","5":"25564","creation_date":"1505470158","6":"1505470158"},{"0":"5446","vim_version":"8.0","1":"8.0","script_version":"1.4.7","2":"1.4.7","version_comment":"Fix GswPrev command","3":"Fix GswPrev command","package":"git-switcher.vim-1.4.7.zip","4":"git-switcher.vim-1.4.7.zip","src_id":"25541","5":"25541","creation_date":"1504073581","6":"1504073581"},{"0":"5446","vim_version":"8.0","1":"8.0","script_version":"1.4.6","2":"1.4.6","version_comment":"Add gsw_load_session_confirm option","3":"Add gsw_load_session_confirm option","package":"git-switcher.vim-1.4.6.zip","4":"git-switcher.vim-1.4.6.zip","src_id":"25456","5":"25456","creation_date":"1501224259","6":"1501224259"},{"0":"5446","vim_version":"8.0","1":"8.0","script_version":"1.4.5","2":"1.4.5","version_comment":"Fix confirmation comment for GswRemote command.","3":"Fix confirmation comment for GswRemote command.","package":"git-switcher.vim-1.4.5.zip","4":"git-switcher.vim-1.4.5.zip","src_id":"25394","5":"25394","creation_date":"1499853102","6":"1499853102"},{"0":"5446","vim_version":"8.0","1":"8.0","script_version":"1.4.3","2":"1.4.3","version_comment":"Make slash available for a session name.","3":"Make slash available for a session name.","package":"git-switcher.vim-1.4.3.zip","4":"git-switcher.vim-1.4.3.zip","src_id":"25208","5":"25208","creation_date":"1494896024","6":"1494896024"},{"0":"5446","vim_version":"8.0","1":"8.0","script_version":"1.4.2","2":"1.4.2","version_comment":"Add gsw_switch_prev_confirm option","3":"Add gsw_switch_prev_confirm option","package":"git-switcher.vim-1.4.2.zip","4":"git-switcher.vim-1.4.2.zip","src_id":"25080","5":"25080","creation_date":"1492501877","6":"1492501877"},{"0":"5446","vim_version":"8.0","1":"8.0","script_version":"1.4.1","2":"1.4.1","version_comment":"Update document.","3":"Update document.","package":"git-switcher.vim-1.4.1.zip","4":"git-switcher.vim-1.4.1.zip","src_id":"25060","5":"25060","creation_date":"1490924467","6":"1490924467"},{"0":"5446","vim_version":"8.0","1":"8.0","script_version":"1.4.0","2":"1.4.0","version_comment":"Add feature to switch to the previous branch","3":"Add feature to switch to the previous branch","package":"git-switcher.vim-1.4.0.zip","4":"git-switcher.vim-1.4.0.zip","src_id":"25055","5":"25055","creation_date":"1490859826","6":"1490859826"},{"0":"5446","vim_version":"8.0","1":"8.0","script_version":"1.3.0","2":"1.3.0","version_comment":"Add GswMove command that move(rename) the current working branch.","3":"Add GswMove command that move(rename) the current working branch.","package":"git-switcher.vim-1.3.0.zip","4":"git-switcher.vim-1.3.0.zip","src_id":"24645","5":"24645","creation_date":"1476783333","6":"1476783333"},{"0":"5446","vim_version":"8.0","1":"8.0","script_version":"1.2.0","2":"1.2.0","version_comment":"Add checktime at the time of no session load switching.","3":"Add checktime at the time of no session load switching.","package":"git-switcher.vim-1.2.0.zip","4":"git-switcher.vim-1.2.0.zip","src_id":"24624","5":"24624","creation_date":"1476266655","6":"1476266655"},{"0":"5446","vim_version":"7.4","1":"7.4","script_version":"1.1.0","2":"1.1.0","version_comment":"Add gsw_save_session_confirm option. It is setting of whether or not to confirm the save of the session when the Gsw command is executed.","3":"Add gsw_save_session_confirm option. It is setting of whether or not to confirm the save of the session when the Gsw command is executed.","package":"git-switcher.vim-1.1.0.zip","4":"git-switcher.vim-1.1.0.zip","src_id":"24520","5":"24520","creation_date":"1473664015","6":"1473664015"},{"0":"5446","vim_version":"7.4","1":"7.4","script_version":"1.0.1","2":"1.0.1","version_comment":"Initial upload","3":"Initial upload","package":"git-switcher.vim-1.0.1.zip","4":"git-switcher.vim-1.0.1.zip","src_id":"24514","5":"24514","creation_date":"1473430120","6":"1473430120"}]},"5443":{"script_id":"5443","0":"5443","script_name":"rimas.vim","1":"rimas.vim","script_type":"utility","2":"utility","summary":"Diccionario de rimas para Vim ","3":"Diccionario de rimas para Vim ","description":"Diccionario de rimas para Vim \r\n\r\nMira la imagen.\r\nhttps:\/\/cloud.githubusercontent.com\/assets\/1724033\/6056518\/f5ade0ea-acdf-11e4-8280-a8416bf43f54.png","4":"Diccionario de rimas para Vim \r\n\r\nMira la imagen.\r\nhttps:\/\/cloud.githubusercontent.com\/assets\/1724033\/6056518\/f5ade0ea-acdf-11e4-8280-a8416bf43f54.png","install_details":"Dependencias\r\n\r\nhttps:\/\/github.com\/xerron\/merimas\r\nConfiguraci\u00c3\u00b3n\r\n\r\nEstablecer el path a merimas.jar\r\n\r\nlet g:rimas_merimas_path = \/path\/to\/merimas\/\r\n\r\nUso\r\n\r\nMostrar rimas consonantes para una palabra:\r\n\r\n:Rima \r\n\r\nMostrar rimas consonantes con n silabas:\r\n\r\n:Rima [numero] \r\n\r\nMostrar rimas consonantes que comienzan con vocal(c) o consonante(c)\r\n\r\n:Rima [v|c] \r\n\r\nUn ejemplo mas completo:\r\n\r\n:Rima [v|c] [numero] \r\n\r\nMostrar rimas asonantes:\r\n\r\n:RimaAsonante [v|c] [numero] \r\n\r\nKeymaps\r\n\r\nRima consonante\r\n\r\nr\r\n\r\nRima Asonante\r\n\r\nR\r\n\r\nLicencia\r\n\r\nMIT.\r\n\r\nhttps:\/\/github.com\/xerron\/rimas.vim","5":"Dependencias\r\n\r\nhttps:\/\/github.com\/xerron\/merimas\r\nConfiguraci\u00c3\u00b3n\r\n\r\nEstablecer el path a merimas.jar\r\n\r\nlet g:rimas_merimas_path = \/path\/to\/merimas\/\r\n\r\nUso\r\n\r\nMostrar rimas consonantes para una palabra:\r\n\r\n:Rima \r\n\r\nMostrar rimas consonantes con n silabas:\r\n\r\n:Rima [numero] \r\n\r\nMostrar rimas consonantes que comienzan con vocal(c) o consonante(c)\r\n\r\n:Rima [v|c] \r\n\r\nUn ejemplo mas completo:\r\n\r\n:Rima [v|c] [numero] \r\n\r\nMostrar rimas asonantes:\r\n\r\n:RimaAsonante [v|c] [numero] \r\n\r\nKeymaps\r\n\r\nRima consonante\r\n\r\nr\r\n\r\nRima Asonante\r\n\r\nR\r\n\r\nLicencia\r\n\r\nMIT.\r\n\r\nhttps:\/\/github.com\/xerron\/rimas.vim","first_name":"Edwin Manuel","6":"Edwin Manuel","last_name":"Cerr\u00c3\u00b3n Angeles","7":"Cerr\u00c3\u00b3n Angeles","releases":[{"0":"5443","vim_version":"7.0","1":"7.0","script_version":"1.1.0","2":"1.1.0","version_comment":"Initial upload","3":"Initial upload","package":"rimas.vim-master.zip","4":"rimas.vim-master.zip","src_id":"24505","5":"24505","creation_date":"1473182482","6":"1473182482"}]},"5442":{"script_id":"5442","0":"5442","script_name":"wordbyword.vim","1":"wordbyword.vim","script_type":"utility","2":"utility","summary":"Word by word search in dictionaries over cursor.","3":"Word by word search in dictionaries over cursor.","description":"See.\r\nhttps:\/\/cloud.githubusercontent.com\/assets\/1724033\/5996942\/d4963796-aa81-11e4-8365-5a60a88932b3.gif\r\nhttps:\/\/cloud.githubusercontent.com\/assets\/1724033\/5996949\/e001d43c-aa81-11e4-9cd7-5873da065ed9.gif","4":"See.\r\nhttps:\/\/cloud.githubusercontent.com\/assets\/1724033\/5996942\/d4963796-aa81-11e4-8365-5a60a88932b3.gif\r\nhttps:\/\/cloud.githubusercontent.com\/assets\/1724033\/5996949\/e001d43c-aa81-11e4-9cd7-5873da065ed9.gif","install_details":"Dependencias\r\n\r\n    sdcv (Linea de comandos de stardict)\r\n    goldendict (beta)\r\n\r\nUse\r\n\r\nAbrir con:\r\n\r\n:Wordbyword\r\n\r\nCerrar con:\r\n\r\n:Wordbyword!\r\n\r\nPara activar la caracteristica de balloon:\r\n\r\n:WordbywordBalloon\r\n\r\nPara desactivar el balloon:\r\n\r\n:WordbywordBalloon!\r\n\r\nhttps:\/\/github.com\/xerron\/wordbyword.vim","5":"Dependencias\r\n\r\n    sdcv (Linea de comandos de stardict)\r\n    goldendict (beta)\r\n\r\nUse\r\n\r\nAbrir con:\r\n\r\n:Wordbyword\r\n\r\nCerrar con:\r\n\r\n:Wordbyword!\r\n\r\nPara activar la caracteristica de balloon:\r\n\r\n:WordbywordBalloon\r\n\r\nPara desactivar el balloon:\r\n\r\n:WordbywordBalloon!\r\n\r\nhttps:\/\/github.com\/xerron\/wordbyword.vim","first_name":"Edwin Manuel","6":"Edwin Manuel","last_name":"Cerr\u00c3\u00b3n Angeles","7":"Cerr\u00c3\u00b3n Angeles","releases":[{"0":"5442","vim_version":"7.0","1":"7.0","script_version":"1.0.0","2":"1.0.0","version_comment":"Initial upload","3":"Initial upload","package":"wordbyword.vim-master.zip","4":"wordbyword.vim-master.zip","src_id":"24504","5":"24504","creation_date":"1473182162","6":"1473182162"}]},"5441":{"script_id":"5441","0":"5441","script_name":"stardict.vim","1":"stardict.vim","script_type":"utility","2":"utility","summary":"Quick access to stardict dicts","3":"Quick access to stardict dicts","description":"Quick access to stardict dicts\r\n\r\n","4":"Quick access to stardict dicts\r\n\r\n","install_details":"Dependencias\r\n\r\n    sdcv\r\n    Diccionarios stardict\r\n\r\nWindows sdcv\r\nUso\r\n\r\nAbre una ventana con el significado de la palabra.\r\n\r\nKeymap: K\r\n\r\nBuscar el significado de una palabra.\r\n\r\n:Stardict \r\n\r\nEscoger el diccionario predeterminado.\r\n\r\n:StardictBooknameChoose\r\n\r\nConfiguraci\u00c3\u00b3n\r\n\r\nDefault path:\r\n\r\nwindows\r\nlet g:stardict_dictionary_path=$STARDICT_DATA_DIR\r\nUnix\r\nlet g:stardict_dictionary_path='\/usr\/share\/stardict\/dic\/'\r\n\r\nCustom keymap:\r\n\r\nlet g:stardict_map_keys=0\r\nnnoremap d :StardictCurrentWord\r\n\r\nhttps:\/\/github.com\/xerron\/stardict.vim","5":"Dependencias\r\n\r\n    sdcv\r\n    Diccionarios stardict\r\n\r\nWindows sdcv\r\nUso\r\n\r\nAbre una ventana con el significado de la palabra.\r\n\r\nKeymap: K\r\n\r\nBuscar el significado de una palabra.\r\n\r\n:Stardict \r\n\r\nEscoger el diccionario predeterminado.\r\n\r\n:StardictBooknameChoose\r\n\r\nConfiguraci\u00c3\u00b3n\r\n\r\nDefault path:\r\n\r\nwindows\r\nlet g:stardict_dictionary_path=$STARDICT_DATA_DIR\r\nUnix\r\nlet g:stardict_dictionary_path='\/usr\/share\/stardict\/dic\/'\r\n\r\nCustom keymap:\r\n\r\nlet g:stardict_map_keys=0\r\nnnoremap d :StardictCurrentWord\r\n\r\nhttps:\/\/github.com\/xerron\/stardict.vim","first_name":"Edwin Manuel","6":"Edwin Manuel","last_name":"Cerr\u00c3\u00b3n Angeles","7":"Cerr\u00c3\u00b3n Angeles","releases":[{"0":"5441","vim_version":"7.0","1":"7.0","script_version":"1.0.0","2":"1.0.0","version_comment":"Initial upload","3":"Initial upload","package":"stardict.vim-master.zip","4":"stardict.vim-master.zip","src_id":"24503","5":"24503","creation_date":"1473181962","6":"1473181962"}]},"5440":{"script_id":"5440","0":"5440","script_name":"WWDC16","1":"WWDC16","script_type":"color scheme","2":"color scheme","summary":"Colorful dark color scheme inspired by WWDC16 page","3":"Colorful dark color scheme inspired by WWDC16 page","description":"Code on GitHub: https:\/\/github.com\/lifepillar\/vim-wwdc16-theme\r\n\r\nA colorful dark theme for Vim inspired by the colors of 2016's WWDC event. Better served with true-color terminals!\r\n\r\nWith support for italics and transparent background in the terminal.","4":"Code on GitHub: https:\/\/github.com\/lifepillar\/vim-wwdc16-theme\r\n\r\nA colorful dark theme for Vim inspired by the colors of 2016's WWDC event. Better served with true-color terminals!\r\n\r\nWith support for italics and transparent background in the terminal.","install_details":"","5":"","first_name":"","6":"","last_name":"Lifepillar","7":"Lifepillar","releases":[{"0":"5440","vim_version":"7.0","1":"7.0","script_version":"1.4.0","2":"1.4.0","version_comment":"License under the MIT license.","3":"License under the MIT license.","package":"vim-wwdc16-v1.4.0.tar.gz","4":"vim-wwdc16-v1.4.0.tar.gz","src_id":"27369","5":"27369","creation_date":"1605509321","6":"1605509321"},{"0":"5440","vim_version":"7.0","1":"7.0","script_version":"1.3.0","2":"1.3.0","version_comment":"Update the color palette to make it ISO compliant. Automatically fallback to 16 colors when t_Co < 256. Define g:terminal_colors. Make vertical split separator visible.","3":"Update the color palette to make it ISO compliant. Automatically fallback to 16 colors when t_Co < 256. Define g:terminal_colors. Make vertical split separator visible.","package":"vim-wwdc16-theme-1.3.0.tar.gz","4":"vim-wwdc16-theme-1.3.0.tar.gz","src_id":"26166","5":"26166","creation_date":"1533427459","6":"1533427459"},{"0":"5440","vim_version":"7.0","1":"7.0","script_version":"1.2.1","2":"1.2.1","version_comment":"Prefer fallback to 256 color palette. Update Search, IncSearch, LineNr, CursorLineNr, FoldColumn highlight groups. Add Terminal, ToolbarLine and ToolbarButton hi groups. Use transparent background for terminal when g:wwdc16_transp_bg=1. Document g:wwdc16_enable_syntax_hi_groups. Re-organize template file.","3":"Prefer fallback to 256 color palette. Update Search, IncSearch, LineNr, CursorLineNr, FoldColumn highlight groups. Add Terminal, ToolbarLine and ToolbarButton hi groups. Use transparent background for terminal when g:wwdc16_transp_bg=1. Document g:wwdc16_enable_syntax_hi_groups. Re-organize template file.","package":"vim-wwdc16-theme-1.2.1.tar.gz","4":"vim-wwdc16-theme-1.2.1.tar.gz","src_id":"25788","5":"25788","creation_date":"1516553641","6":"1516553641"},{"0":"5440","vim_version":"7.0","1":"7.0","script_version":"v1.2.0","2":"v1.2.0","version_comment":"Allow using xterm's 256 color palette in terminal not supporting true colors. Magenta is slightly easier on the eyes.\r\nThe colorscheme is now built from a Colortemplate's template.","3":"Allow using xterm's 256 color palette in terminal not supporting true colors. Magenta is slightly easier on the eyes.\r\nThe colorscheme is now built from a Colortemplate's template.","package":"vim-wwdc16-theme-1.2.0.tar.gz","4":"vim-wwdc16-theme-1.2.0.tar.gz","src_id":"25625","5":"25625","creation_date":"1509215501","6":"1509215501"},{"0":"5440","vim_version":"7.0","1":"7.0","script_version":"1.1.0","2":"1.1.0","version_comment":"Most important changes: added QuickfixLine, StatusLineTerm, StatusLineTerNC highlight groups; highlighting for bad spelling does not rely exclusively on underline\/undercurl; removed a few shades of grey and fixed the terminal palettes to respect the terminal colors (i.e., Yellow is yellow, Green is green, etc\u00e2\u0080\u00a6); italics is enabled by default.","3":"Most important changes: added QuickfixLine, StatusLineTerm, StatusLineTerNC highlight groups; highlighting for bad spelling does not rely exclusively on underline\/undercurl; removed a few shades of grey and fixed the terminal palettes to respect the terminal colors (i.e., Yellow is yellow, Green is green, etc\u00e2\u0080\u00a6); italics is enabled by default.","package":"vim-wwdc16-theme-1.1.0.tar.gz","4":"vim-wwdc16-theme-1.1.0.tar.gz","src_id":"25554","5":"25554","creation_date":"1504638564","6":"1504638564"},{"0":"5440","vim_version":"7.0","1":"7.0","script_version":"1.0.3","2":"1.0.3","version_comment":"Code cleanup.","3":"Code cleanup.","package":"vim-wwdc16-theme-1.0.3.tar.gz","4":"vim-wwdc16-theme-1.0.3.tar.gz","src_id":"25302","5":"25302","creation_date":"1497172454","6":"1497172454"},{"0":"5440","vim_version":"7.0","1":"7.0","script_version":"v1.0.2","2":"v1.0.2","version_comment":"Added iTerm2 profile. Added support for terminal colors in NeoVim.","3":"Added iTerm2 profile. Added support for terminal colors in NeoVim.","package":"vim-wwdc16-theme-1.0.2.tar.gz","4":"vim-wwdc16-theme-1.0.2.tar.gz","src_id":"24995","5":"24995","creation_date":"1487963839","6":"1487963839"},{"0":"5440","vim_version":"7.0","1":"7.0","script_version":"v1.0.1","2":"v1.0.1","version_comment":"Fix bug causing cursor column to override search highlight color. Add custom highlight groups for the main modes (NormalMode, InsertMode, etc\u00e2\u0080\u00a6). Other minor tweaks.","3":"Fix bug causing cursor column to override search highlight color. Add custom highlight groups for the main modes (NormalMode, InsertMode, etc\u00e2\u0080\u00a6). Other minor tweaks.","package":"vim-wwdc16-theme-1.0.1.tar.gz","4":"vim-wwdc16-theme-1.0.1.tar.gz","src_id":"24502","5":"24502","creation_date":"1473153103","6":"1473153103"},{"0":"5440","vim_version":"7.0","1":"7.0","script_version":"1.0.0","2":"1.0.0","version_comment":"Initial upload","3":"Initial upload","package":"vim-wwdc16-theme-1.0.0.tar.gz","4":"vim-wwdc16-theme-1.0.0.tar.gz","src_id":"24499","5":"24499","creation_date":"1473099159","6":"1473099159"}]},"5439":{"script_id":"5439","0":"5439","script_name":"vim-sml","1":"vim-sml","script_type":"ftplugin","2":"ftplugin","summary":"Vim support for Standard ML programming","3":"Vim support for Standard ML programming","description":"Vim support for Standard ML programming.\r\n\r\nProvides:\r\n\r\n* Improved syntax highlighting for Standard ML\r\n* Syntax highlighting for MLBasis, SML\/NJ CM, ML-Lex, ML-Yacc, Smackage\r\n* Improved intendation rules for Standard ML\r\n* Indentation rules for SML\/NJ CM\r\n* Filetype detection:\r\n  - sml: .fun, .ML, .sig, .smi\r\n  - smlcm: .cm\r\n  - mllex: .lex\r\n  - mlyacc: .grm\r\n  - mlbasis: .mlb\r\n  - spackspec: .smackspec\r\n* Comment support for MLBasis, SML\/NJ CM, ML-Lex\r\n* Conceal characters for Standard ML ('a -> α, etc.)\r\n* a.vim support for Standard ML (.sml <-> .sig\/.smi, .lex <-> .grm\/.yacc)\r\n* matchit.vim support for Standard ML and ML-Lex (struct\/sig <-> end, local\/let <-> in)","4":"Vim support for Standard ML programming.\r\n\r\nProvides:\r\n\r\n* Improved syntax highlighting for Standard ML\r\n* Syntax highlighting for MLBasis, SML\/NJ CM, ML-Lex, ML-Yacc, Smackage\r\n* Improved intendation rules for Standard ML\r\n* Indentation rules for SML\/NJ CM\r\n* Filetype detection:\r\n  - sml: .fun, .ML, .sig, .smi\r\n  - smlcm: .cm\r\n  - mllex: .lex\r\n  - mlyacc: .grm\r\n  - mlbasis: .mlb\r\n  - spackspec: .smackspec\r\n* Comment support for MLBasis, SML\/NJ CM, ML-Lex\r\n* Conceal characters for Standard ML ('a -> α, etc.)\r\n* a.vim support for Standard ML (.sml <-> .sig\/.smi, .lex <-> .grm\/.yacc)\r\n* matchit.vim support for Standard ML and ML-Lex (struct\/sig <-> end, local\/let <-> in)","install_details":"1. Download vim-sml.zip and extract it\r\n2. Copy the contents of vim-sml to the corresponding directories of your $VIMHOME\r\n3. Restart vim","5":"1. Download vim-sml.zip and extract it\r\n2. Copy the contents of vim-sml to the corresponding directories of your $VIMHOME\r\n3. Restart vim","first_name":"Thomas","6":"Thomas","last_name":"Allen","7":"Allen","releases":[{"0":"5439","vim_version":"7.0","1":"7.0","script_version":"1.4","2":"1.4","version_comment":"Add missing files.","3":"Add missing files.","package":"vim-sml.zip","4":"vim-sml.zip","src_id":"26245","5":"26245","creation_date":"1539429227","6":"1539429227"}]},"5438":{"script_id":"5438","0":"5438","script_name":"SearchCompleteMotion","1":"SearchCompleteMotion","script_type":"patch","2":"patch","summary":"Updated SearchCompete plugin with support for motions","3":"Updated SearchCompete plugin with support for motions","description":"The original SearchComplete plugin breaks motion commands, such as d\/, y\/, etc.\r\nThis updates that using a separate omap and nmap command to use the expression register during motions.\r\n\r\nI have uploaded to github here: https:\/\/github.com\/jakykong\/SearchComplete.\r\nI've also submitted a pull request for the original SearchComplete author, but do not anticipate a response.\r\n\r\n\r\nEdit: My apologies, it's my first upload here and I've realized I misunderstood a minor detail so the version number listed here is off. Should have been 1.2, not 6.0. Also, this should have been 'utility', not 'patch'. \r\nAs far as I can tell, there's no option to fix these. If I've missed something, please let me know! ","4":"The original SearchComplete plugin breaks motion commands, such as d\/, y\/, etc.\r\nThis updates that using a separate omap and nmap command to use the expression register during motions.\r\n\r\nI have uploaded to github here: https:\/\/github.com\/jakykong\/SearchComplete.\r\nI've also submitted a pull request for the original SearchComplete author, but do not anticipate a response.\r\n\r\n\r\nEdit: My apologies, it's my first upload here and I've realized I misunderstood a minor detail so the version number listed here is off. Should have been 1.2, not 6.0. Also, this should have been 'utility', not 'patch'. \r\nAs far as I can tell, there's no option to fix these. If I've missed something, please let me know! ","install_details":"Using pathogen, clone the above Github repository to your Bundles folder.\r\nOtherwise, just save the file to your plugins folder.","5":"Using pathogen, clone the above Github repository to your Bundles folder.\r\nOtherwise, just save the file to your plugins folder.","first_name":"Jack","6":"Jack","last_name":"Mudge","7":"Mudge","releases":[{"0":"5438","vim_version":"7.4","1":"7.4","script_version":"6.0","2":"6.0","version_comment":"Initial upload","3":"Initial upload","package":"SearchCompleteMovement.vim","4":"SearchCompleteMovement.vim","src_id":"24488","5":"24488","creation_date":"1472845917","6":"1472845917"}]},"5437":{"script_id":"5437","0":"5437","script_name":"hindent","1":"hindent","script_type":"ftplugin","2":"ftplugin","summary":"Automatic Haskell code reformatting","3":"Automatic Haskell code reformatting","description":"Re-indent your Haskell code automatically when saved using Hindent\r\n\r\nOn Github: https:\/\/github.com\/alx741\/vim-hindent","4":"Re-indent your Haskell code automatically when saved using Hindent\r\n\r\nOn Github: https:\/\/github.com\/alx741\/vim-hindent","install_details":"","5":"","first_name":"Daniel","6":"Daniel","last_name":"Campoverde","7":"Campoverde","releases":[{"0":"5437","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"hindent.tar.gz","4":"hindent.tar.gz","src_id":"24487","5":"24487","creation_date":"1472787390","6":"1472787390"}]},"5436":{"script_id":"5436","0":"5436","script_name":"composer.vim","1":"composer.vim","script_type":"utility","2":"utility","summary":"Initial release","3":"Initial release","description":"Composer.vim provides conveniences for working with Composer PHP projects.\r\nSome features include:\r\n\r\n* `:Composer` command wrapper around `composer` with smart completion\r\n* Navigate to source files using Composer's autoloader\r\n* Insert `use` statement for the class\/interface\/trait under cursor\r\n* Projectionist support (e.g., `:Ecomposer` to edit your\r\n  `composer.json`, `:A` to jump to `composer.lock` and back)\r\n* Dispatch support (`:Dispatch` runs `composer dump-autoload`)\r\n\r\nSee `:help composer` for details.","4":"Composer.vim provides conveniences for working with Composer PHP projects.\r\nSome features include:\r\n\r\n* `:Composer` command wrapper around `composer` with smart completion\r\n* Navigate to source files using Composer's autoloader\r\n* Insert `use` statement for the class\/interface\/trait under cursor\r\n* Projectionist support (e.g., `:Ecomposer` to edit your\r\n  `composer.json`, `:A` to jump to `composer.lock` and back)\r\n* Dispatch support (`:Dispatch` runs `composer dump-autoload`)\r\n\r\nSee `:help composer` for details.","install_details":"Using vim-plug, for example:\r\n\r\n\tPlug 'noahfrederick\/vim-composer'\r\n\r\nOptionally install Dispatch.vim and Projectionist.vim for projections and asynchronous command execution:\r\n\r\n\tPlug 'tpope\/vim-dispatch'\r\n\tPlug 'tpope\/vim-projectionist'\r\n\r\nNote: either Projectionist.vim or Vim version 7.4.1304 or later is required for JSON support.","5":"Using vim-plug, for example:\r\n\r\n\tPlug 'noahfrederick\/vim-composer'\r\n\r\nOptionally install Dispatch.vim and Projectionist.vim for projections and asynchronous command execution:\r\n\r\n\tPlug 'tpope\/vim-dispatch'\r\n\tPlug 'tpope\/vim-projectionist'\r\n\r\nNote: either Projectionist.vim or Vim version 7.4.1304 or later is required for JSON support.","first_name":"Noah","6":"Noah","last_name":"Frederick","7":"Frederick","releases":[{"0":"5436","vim_version":"7.3","1":"7.3","script_version":"1.0.1","2":"1.0.1","version_comment":"* Fixes an egregious error that prevented command completion from working","3":"* Fixes an egregious error that prevented command completion from working","package":"composer-1.0.1.zip","4":"composer-1.0.1.zip","src_id":"24485","5":"24485","creation_date":"1472689110","6":"1472689110"},{"0":"5436","vim_version":"7.3","1":"7.3","script_version":"1.0.0","2":"1.0.0","version_comment":"Initial upload","3":"Initial upload","package":"composer-1.0.0.zip","4":"composer-1.0.0.zip","src_id":"24484","5":"24484","creation_date":"1472603295","6":"1472603295"}]},"5435":{"script_id":"5435","0":"5435","script_name":"vim-anyfold","1":"vim-anyfold","script_type":"indent","2":"indent","summary":"Generic folding mechanism and motion based on indentation","3":"Generic folding mechanism and motion based on indentation","description":"For examples and full documentation, visit the official repository\r\nhttps:\/\/github.com\/pseewald\/vim-anyfold\r\n\r\nThis plugin comes with the following features:\r\n* Folding mechanism based on indented blocks that has a very intuitive and predictable behaviour.\r\n* Results comparable to syntax aware folding methods but fast and generic algorithm that does not rely on language specific rules.\r\n* Works out of the box for any filetypes, optimal results for all indented languages (including properly indented curly brace languages).\r\n* Shortcuts to navigate to beginning \/ end of a block and to previous \/ next indented block.\r\n* Can handle corner cases with ease (comments, varying indentation widths, line breaks).\r\n* Fast update mechanism that keeps folds in sync with buffer.\r\n\r\nIt has the following shortcomings:\r\n* Can not correctly fold mismatched indentation and thus should only be used together with disciplined programming style (or in combination with Vim's equalprg autoindent feature).\r\n\r\nSetup and Usage:\r\n1. Install this plugin with a vim plugin manager.\r\n2. Add the following lines to your vimrc (if not already present).\r\n\r\n    filetype plugin indent on\r\n    syntax on\r\n    let anyfold_activate=1\r\n    set foldlevel=0\r\n\r\nChoose a higher foldlevel if you prefer to have folds open by default.\r\n3. Use Vim's fold commands zo, zO, zc, za, ... to fold \/ unfold folds (read :h fold-commands for more information). Use key combinations [[ and ]] to navigate to the beginning and end of the current open fold. Use ]k and [j to navigate to the end of the previous block and to the beginning of the next block.","4":"For examples and full documentation, visit the official repository\r\nhttps:\/\/github.com\/pseewald\/vim-anyfold\r\n\r\nThis plugin comes with the following features:\r\n* Folding mechanism based on indented blocks that has a very intuitive and predictable behaviour.\r\n* Results comparable to syntax aware folding methods but fast and generic algorithm that does not rely on language specific rules.\r\n* Works out of the box for any filetypes, optimal results for all indented languages (including properly indented curly brace languages).\r\n* Shortcuts to navigate to beginning \/ end of a block and to previous \/ next indented block.\r\n* Can handle corner cases with ease (comments, varying indentation widths, line breaks).\r\n* Fast update mechanism that keeps folds in sync with buffer.\r\n\r\nIt has the following shortcomings:\r\n* Can not correctly fold mismatched indentation and thus should only be used together with disciplined programming style (or in combination with Vim's equalprg autoindent feature).\r\n\r\nSetup and Usage:\r\n1. Install this plugin with a vim plugin manager.\r\n2. Add the following lines to your vimrc (if not already present).\r\n\r\n    filetype plugin indent on\r\n    syntax on\r\n    let anyfold_activate=1\r\n    set foldlevel=0\r\n\r\nChoose a higher foldlevel if you prefer to have folds open by default.\r\n3. Use Vim's fold commands zo, zO, zc, za, ... to fold \/ unfold folds (read :h fold-commands for more information). Use key combinations [[ and ]] to navigate to the beginning and end of the current open fold. Use ]k and [j to navigate to the end of the previous block and to the beginning of the next block.","install_details":"Install this plugin with your preferred vim plugin manager.","5":"Install this plugin with your preferred vim plugin manager.","first_name":"Patrick","6":"Patrick","last_name":"Seewald","7":"Seewald","releases":[{"0":"5435","vim_version":"7.4","1":"7.4","script_version":"2.0","2":"2.0","version_comment":"Better defaults for brace based languages and performance optimizations","3":"Better defaults for brace based languages and performance optimizations","package":"vim-anyfold-2.0.zip","4":"vim-anyfold-2.0.zip","src_id":"25893","5":"25893","creation_date":"1521631519","6":"1521631519"},{"0":"5435","vim_version":"7.4","1":"7.4","script_version":"1.1.0","2":"1.1.0","version_comment":"* Toggle key has been removed\r\n* Fast and direct auto-update of folds\r\n* Performance improvements\r\n* Better defaults for curly-brace languages\r\n* Various bug fixes","3":"* Toggle key has been removed\r\n* Fast and direct auto-update of folds\r\n* Performance improvements\r\n* Better defaults for curly-brace languages\r\n* Various bug fixes","package":"vim-anyfold-1.1.0.zip","4":"vim-anyfold-1.1.0.zip","src_id":"24776","5":"24776","creation_date":"1480644528","6":"1480644528"},{"0":"5435","vim_version":"7.3","1":"7.3","script_version":"1.0","2":"1.0","version_comment":"First stable release","3":"First stable release","package":"AnyFold-1.0.zip","4":"AnyFold-1.0.zip","src_id":"24535","5":"24535","creation_date":"1474196446","6":"1474196446"}]},"5434":{"script_id":"5434","0":"5434","script_name":"ctrlp-obsession","1":"ctrlp-obsession","script_type":"utility","2":"utility","summary":"A super simple session-navigator using obsession \/ prosession","3":"A super simple session-navigator using obsession \/ prosession","description":"Allows you to easily switch active sessions using ctrlP.\r\n\r\nDepends on obssession, prosession and ofcourse CtrlP","4":"Allows you to easily switch active sessions using ctrlP.\r\n\r\nDepends on obssession, prosession and ofcourse CtrlP","install_details":"See installation instructions on https\/\/github.com\/gikmx\/ctrlp-obsession.git","5":"See installation instructions on https\/\/github.com\/gikmx\/ctrlp-obsession.git","first_name":"Hector","6":"Hector","last_name":"Menendez","7":"Menendez","releases":[{"0":"5434","vim_version":"7.4","1":"7.4","script_version":"0.0.1","2":"0.0.1","version_comment":"Initial upload","3":"Initial upload","package":"ctrlp-obsession.zip","4":"ctrlp-obsession.zip","src_id":"24477","5":"24477","creation_date":"1472377626","6":"1472377626"}]},"5433":{"script_id":"5433","0":"5433","script_name":"speedy","1":"speedy","script_type":"utility","2":"utility","summary":"super fast gulp task execution","3":"super fast gulp task execution","description":"The plugin executes gulp tasks in a background vim channel. The plugin runs a node server that imports your gulp file which makes running your gulp files much faster than on command line, since only the initial run has to interpret the gulp file.\r\n\r\nVim commands:\r\n\r\n:Gulp task [task, ...]\r\nRuns a gulp task. The output is redirected to vim. You can inspect it with vim :msg command. Upon initial invocation it will also start the background server. The server will be shut down when you exit vim.\r\n\r\n:GulpStop\r\n:GulpStart\r\n:GulpRestart\r\nThese commands stop, start and restart the background node server. This is useful if you want to switch to another project.\r\n\r\nThe projcet is on github: https:\/\/github.com\/coot\/speedy","4":"The plugin executes gulp tasks in a background vim channel. The plugin runs a node server that imports your gulp file which makes running your gulp files much faster than on command line, since only the initial run has to interpret the gulp file.\r\n\r\nVim commands:\r\n\r\n:Gulp task [task, ...]\r\nRuns a gulp task. The output is redirected to vim. You can inspect it with vim :msg command. Upon initial invocation it will also start the background server. The server will be shut down when you exit vim.\r\n\r\n:GulpStop\r\n:GulpStart\r\n:GulpRestart\r\nThese commands stop, start and restart the background node server. This is useful if you want to switch to another project.\r\n\r\nThe projcet is on github: https:\/\/github.com\/coot\/speedy","install_details":"","5":"","first_name":"Marcin","6":"Marcin","last_name":"Szamotulski","7":"Szamotulski","releases":[{"0":"5433","vim_version":"8.0","1":"8.0","script_version":"v1,1","2":"v1,1","version_comment":"https:\/\/github.com\/coot\/speedy\/releases\/tag\/v1.1","3":"https:\/\/github.com\/coot\/speedy\/releases\/tag\/v1.1","package":"speedy-1.1.zip","4":"speedy-1.1.zip","src_id":"24631","5":"24631","creation_date":"1476549011","6":"1476549011"},{"0":"5433","vim_version":"7.4","1":"7.4","script_version":"1","2":"1","version_comment":"Initial upload","3":"Initial upload","package":"speedy-1.0.tar.gz","4":"speedy-1.0.tar.gz","src_id":"24475","5":"24475","creation_date":"1472325491","6":"1472325491"}]},"5432":{"script_id":"5432","0":"5432","script_name":"Omnipytent","1":"Omnipytent","script_type":"utility","2":"utility","summary":"The all powerful Pythonic task runner","3":"The all powerful Pythonic task runner","description":"GitHub repository: https:\/\/github.com\/idanarye\/vim-omnipytent\r\n\r\nOmnipytent is a plugin for creating and running project-specific, user-specific tasks. Programmers should know enough about to programming to be able to script their own workflow - and Omnipytent aims to make this as simple, as accessible and as out-of-your-way as possible. Omnipytent is the successor to Integrake(http:\/\/www.vim.org\/scripts\/script.php?script_id=4732), and follows a similar design - but in Python, so it could be used in neovim(which did not have Ruby support at the time)","4":"GitHub repository: https:\/\/github.com\/idanarye\/vim-omnipytent\r\n\r\nOmnipytent is a plugin for creating and running project-specific, user-specific tasks. Programmers should know enough about to programming to be able to script their own workflow - and Omnipytent aims to make this as simple, as accessible and as out-of-your-way as possible. Omnipytent is the successor to Integrake(http:\/\/www.vim.org\/scripts\/script.php?script_id=4732), and follows a similar design - but in Python, so it could be used in neovim(which did not have Ruby support at the time)","install_details":"","5":"","first_name":"Idan","6":"Idan","last_name":"Arye","7":"Arye","releases":[{"0":"5432","vim_version":"8.0","1":"8.0","script_version":"1.3.0","2":"1.3.0","version_comment":"Added ctx.proj_dir, ctx.task_dir, ctx.cur_dir and ctx.file_dir.\r\nAdded g:omnipytent_projectRootMarkers for picking a parent directory as project root when there is no tasks file.\r\nAdded Async tasks mechanism.\r\nAdded @task.options_multi - like task.options but allows multiple choices.\r\nAdded Generator style for @task.options.\r\nLook the directory tree for a tasks file.\r\nOptions tasks use the chosen selection UI.\r\nFixed vim_eval for lists and dicts.\r\nFixed Input mode handling when starting terminal.","3":"Added ctx.proj_dir, ctx.task_dir, ctx.cur_dir and ctx.file_dir.\r\nAdded g:omnipytent_projectRootMarkers for picking a parent directory as project root when there is no tasks file.\r\nAdded Async tasks mechanism.\r\nAdded @task.options_multi - like task.options but allows multiple choices.\r\nAdded Generator style for @task.options.\r\nLook the directory tree for a tasks file.\r\nOptions tasks use the chosen selection UI.\r\nFixed vim_eval for lists and dicts.\r\nFixed Input mode handling when starting terminal.","package":"omnipytent_v1.3.0.zip","4":"omnipytent_v1.3.0.zip","src_id":"26275","5":"26275","creation_date":"1542358686","6":"1542358686"},{"0":"5432","vim_version":"8.0","1":"8.0","script_version":"1.2.0","2":"1.2.0","version_comment":"Add the OPT helper for easy access to options.\r\nAdd the del operator for VAR.\r\nAdd the in operator for VAR and OPT.\r\nAdd the changed context manager for VAR and OPT.\r\nAdd utils for working with Vim windows - grep_windows, grep_window and other_windows.\r\nAdd window tasks.\r\nAdd terminal shell executor(returned from TERMINAL_PANEL and TERMINAL_TAB)\r\nAdd << operator for shell executors to send raw text.\r\nTests(about time)\r\nA cheat sheet in the doc\r\nFix a doc problem where :! was defining a tag instead of refering to it\r\nFix binary-vs-string problem with Python3 and Vim\r\nFix Python type problems by making all execution.py classes subclass object.\r\nFix bug when cleaning tasks cache.","3":"Add the OPT helper for easy access to options.\r\nAdd the del operator for VAR.\r\nAdd the in operator for VAR and OPT.\r\nAdd the changed context manager for VAR and OPT.\r\nAdd utils for working with Vim windows - grep_windows, grep_window and other_windows.\r\nAdd window tasks.\r\nAdd terminal shell executor(returned from TERMINAL_PANEL and TERMINAL_TAB)\r\nAdd << operator for shell executors to send raw text.\r\nTests(about time)\r\nA cheat sheet in the doc\r\nFix a doc problem where :! was defining a tag instead of refering to it\r\nFix binary-vs-string problem with Python3 and Vim\r\nFix Python type problems by making all execution.py classes subclass object.\r\nFix bug when cleaning tasks cache.","package":"omnipytent_v1.2.0.zip","4":"omnipytent_v1.2.0.zip","src_id":"25722","5":"25722","creation_date":"1513720434","6":"1513720434"},{"0":"5432","vim_version":"7.4","1":"7.4","script_version":"1.1.0","2":"1.1.0","version_comment":"Windows support.\r\nTERMINAL_PANEL and TERMINAL_TAB support for Vim 8.\r\nomnipytent.ext for loading module from omnipytent directories in Vim plugins.\r\nSupport Plumbum's with_env()(Linux+Windows)\r\ng:omnipytent_defaultPythonVersion for picking Python2 or Python3 as the default Python version for new tasks files.\r\nSupport (named) parameters in shell executors.\r\nAdd the size parameter to TERMINAL_PANEL for setting the number of lines.\r\nDon't put blank line at the end of the file - Vim already adds a linefeed...","3":"Windows support.\r\nTERMINAL_PANEL and TERMINAL_TAB support for Vim 8.\r\nomnipytent.ext for loading module from omnipytent directories in Vim plugins.\r\nSupport Plumbum's with_env()(Linux+Windows)\r\ng:omnipytent_defaultPythonVersion for picking Python2 or Python3 as the default Python version for new tasks files.\r\nSupport (named) parameters in shell executors.\r\nAdd the size parameter to TERMINAL_PANEL for setting the number of lines.\r\nDon't put blank line at the end of the file - Vim already adds a linefeed...","package":"omnipytent_v1.1.0.zip","4":"omnipytent_v1.1.0.zip","src_id":"25677","5":"25677","creation_date":"1512090997","6":"1512090997"},{"0":"5432","vim_version":"7.0","1":"7.0","script_version":"1.0.0","2":"1.0.0","version_comment":"Initial upload","3":"Initial upload","package":"omnipytent_v1.0.0.zip","4":"omnipytent_v1.0.0.zip","src_id":"24471","5":"24471","creation_date":"1472242469","6":"1472242469"}]},"5431":{"script_id":"5431","0":"5431","script_name":"asyncrun","1":"asyncrun","script_type":"utility","2":"utility","summary":"Run Async Shell Commands in Vim 8.0 and Output to Quickfix in Realtime","3":"Run Async Shell Commands in Vim 8.0 and Output to Quickfix in Realtime","description":"Maintainer: skywind3000 (at) gmail.com\r\nHomepage: https:\/\/github.com\/skywind3000\/asyncrun.vim\r\n\r\nRun shell commands in background and output to quickfix:\r\n    :AsyncRun[!] [options] {cmd} ...\r\n\r\n    when \"!\" is included, auto-scroll in quickfix will be disabled\r\n    parameters are splited by space, if a parameter contains space,\r\n    it should be escaped as backslash + space (just like ex commands)\r\n\r\nParameters will be expanded if they start with '%', '#' or '<' :\r\n    %:p     - File name of current buffer with full path\r\n    %:t     - File name of current buffer without path\r\n    %:p:h   - File path of current buffer without file name\r\n    %:e     - File extension of current buffer\r\n    %:t:r   - File name of current buffer without path and extension\r\n    %       - File name relativize to current directory\r\n    %:h:.   - File path relativize to current directory\r\n       - Current directory\r\n     - Current word under cursor\r\n     - Current file name under cursor\r\n      - Project root directory\r\n\r\nEnvironment variables are set before executing:\r\n    $VIM_FILEPATH  - File name of current buffer with full path\r\n    $VIM_FILENAME  - File name of current buffer without path\r\n    $VIM_FILEDIR   - Full path of current buffer without the file name\r\n    $VIM_FILEEXT   - File extension of current buffer\r\n    $VIM_FILENOEXT - File name of current buffer without path and extension\r\n    $VIM_CWD       - Current directory\r\n    $VIM_RELDIR    - File path relativize to current directory\r\n    $VIM_RELNAME   - File name relativize to current directory \r\n    $VIM_ROOT      - Project root directory\r\n    $VIM_CWORD     - Current word under cursor\r\n    $VIM_CFILE     - Current filename under cursor\r\n    $VIM_GUI       - Is running under gui ?\r\n    $VIM_VERSION   - Value of v:version\r\n    $VIM_COLUMNS   - How many columns in vim's screen\r\n    $VIM_LINES     - How many lines in vim's screen\r\n\r\n    parameters also accept these environment variables wrapped by \r\n    \"$(...)\", and \"$(VIM_FILEDIR)\" will be expanded as file directory\r\n\r\n    Macro $(VIM_ROOT) and  (new in version 1.3.12) indicate the \r\n    Project Root of the current file.\r\n\r\nThere can be some options before [cmd]:\r\n    -mode=0\/1\/2  - start mode: 0(async,default), 1(makeprg), 2(!)\r\n    -cwd=?       - initial directory, (use current directory if unset)\r\n    -save=0\/1    - non-zero to save unsaved files before executing\r\n    -program=?   - set to 'make' to use '&makeprg'\r\n    -post=?   - vimscript to exec after this job finished, spaces **must** be escaped to '\\ '\r\n    -raw=1    - don't matching the errorformat, output directly in the quickfix window.\r\n\r\n    All options must start with a minus and position **before** `[cmd]`.\r\n    Since no shell command starts with a minus. So they can be \r\n    distinguished from shell command easily without any ambiguity.\r\n\r\nStop the running job by signal TERM:\r\n    :AsyncStop[!]\r\n\r\n    when \"!\" is included, job will be stopped by signal KILL\r\n\r\nSettings:\r\n    g:asyncrun_exit - script will be executed after finished\r\n    g:asyncrun_bell - non-zero to ring a bell after finished (notify you job finished)\r\n    g:asyncrun_mode - 0:async(if support) 1:sync 2:shell\r\n    g:asyncrun_encs - shell program output encoding\r\n\r\nVariables:\r\n    g:asyncrun_code - exit code\r\n    g:asyncrun_status - 'running', 'success' or 'failure'\r\n\r\nRequirements:\r\n    minimal vim version is 7.4.1829 to support async jobs. \r\n    neovim 0.1.4 or later is supported too. \r\n    recommand to use vim 8.0 or above.\r\n\r\nNote: \r\n    AsyncRun uses quickfix window to show job outputs, in order to see the outputs in realtime, \r\n    you need open quickfix window at first by using :copen (see :help copen). And there is a \r\n    function 'asyncrun#quickfix_toggle(size)' for you to open\/close it rapidly (see tutorial 9).\r\n\r\nTutorial 0: async run gcc \/ make to build current file\r\n    :AsyncRun gcc % -o %<\r\n    :AsyncRun g++ -O3 \"%\" -o \"%<\" -lpthread \r\n    :AsyncRun make -f Mymakefile\r\n\r\nTutorial 1: async grep key word\r\n    :AsyncRun! grep -R word . \r\n    :AsyncRun! grep -R  . \r\n\r\nTutorial 2: look up man page\r\n    :AsyncRun! man -S 3:2:1 \r\n\r\nTutorial 3: build go project\r\n    :AsyncRun go build \"%:p:h\"\r\n\r\nTutorial 4: use  to compile current file\r\n    :noremap  :AsyncRun gcc \"%\" -o \"%<\" \r\n\r\nTutorial 5: open quickfix window (see the output)\r\n    :botright copen 8\r\n\r\nTutorial 6: async git push\r\n    :AsyncRun git push origin master\r\n\r\nTutorial 7: compile markdown to pdf\r\n    :AsyncRun pandoc --output \"$(VIM_FILENOEXT).pdf\" \"%:p\" \r\n\r\nTutorial 8: update tags in background while editing (super useful for large projects):\r\n    :AsyncRun ctags -R --fields=+S .\r\n    :AsyncRun ctags -R -f $(VIM_FILEDIR)\/ctags.out --fields=+iaS $(VIM_FILEDIR)\r\n\r\nTutorial 9: a help function to toggle quickfix window in an efficient way (F9 to toggle):\r\n    :noremap  :call asyncrun#quickfix_toggle(8)\r\n\r\nPlease vote it if you like it.\r\n","4":"Maintainer: skywind3000 (at) gmail.com\r\nHomepage: https:\/\/github.com\/skywind3000\/asyncrun.vim\r\n\r\nRun shell commands in background and output to quickfix:\r\n    :AsyncRun[!] [options] {cmd} ...\r\n\r\n    when \"!\" is included, auto-scroll in quickfix will be disabled\r\n    parameters are splited by space, if a parameter contains space,\r\n    it should be escaped as backslash + space (just like ex commands)\r\n\r\nParameters will be expanded if they start with '%', '#' or '<' :\r\n    %:p     - File name of current buffer with full path\r\n    %:t     - File name of current buffer without path\r\n    %:p:h   - File path of current buffer without file name\r\n    %:e     - File extension of current buffer\r\n    %:t:r   - File name of current buffer without path and extension\r\n    %       - File name relativize to current directory\r\n    %:h:.   - File path relativize to current directory\r\n       - Current directory\r\n     - Current word under cursor\r\n     - Current file name under cursor\r\n      - Project root directory\r\n\r\nEnvironment variables are set before executing:\r\n    $VIM_FILEPATH  - File name of current buffer with full path\r\n    $VIM_FILENAME  - File name of current buffer without path\r\n    $VIM_FILEDIR   - Full path of current buffer without the file name\r\n    $VIM_FILEEXT   - File extension of current buffer\r\n    $VIM_FILENOEXT - File name of current buffer without path and extension\r\n    $VIM_CWD       - Current directory\r\n    $VIM_RELDIR    - File path relativize to current directory\r\n    $VIM_RELNAME   - File name relativize to current directory \r\n    $VIM_ROOT      - Project root directory\r\n    $VIM_CWORD     - Current word under cursor\r\n    $VIM_CFILE     - Current filename under cursor\r\n    $VIM_GUI       - Is running under gui ?\r\n    $VIM_VERSION   - Value of v:version\r\n    $VIM_COLUMNS   - How many columns in vim's screen\r\n    $VIM_LINES     - How many lines in vim's screen\r\n\r\n    parameters also accept these environment variables wrapped by \r\n    \"$(...)\", and \"$(VIM_FILEDIR)\" will be expanded as file directory\r\n\r\n    Macro $(VIM_ROOT) and  (new in version 1.3.12) indicate the \r\n    Project Root of the current file.\r\n\r\nThere can be some options before [cmd]:\r\n    -mode=0\/1\/2  - start mode: 0(async,default), 1(makeprg), 2(!)\r\n    -cwd=?       - initial directory, (use current directory if unset)\r\n    -save=0\/1    - non-zero to save unsaved files before executing\r\n    -program=?   - set to 'make' to use '&makeprg'\r\n    -post=?   - vimscript to exec after this job finished, spaces **must** be escaped to '\\ '\r\n    -raw=1    - don't matching the errorformat, output directly in the quickfix window.\r\n\r\n    All options must start with a minus and position **before** `[cmd]`.\r\n    Since no shell command starts with a minus. So they can be \r\n    distinguished from shell command easily without any ambiguity.\r\n\r\nStop the running job by signal TERM:\r\n    :AsyncStop[!]\r\n\r\n    when \"!\" is included, job will be stopped by signal KILL\r\n\r\nSettings:\r\n    g:asyncrun_exit - script will be executed after finished\r\n    g:asyncrun_bell - non-zero to ring a bell after finished (notify you job finished)\r\n    g:asyncrun_mode - 0:async(if support) 1:sync 2:shell\r\n    g:asyncrun_encs - shell program output encoding\r\n\r\nVariables:\r\n    g:asyncrun_code - exit code\r\n    g:asyncrun_status - 'running', 'success' or 'failure'\r\n\r\nRequirements:\r\n    minimal vim version is 7.4.1829 to support async jobs. \r\n    neovim 0.1.4 or later is supported too. \r\n    recommand to use vim 8.0 or above.\r\n\r\nNote: \r\n    AsyncRun uses quickfix window to show job outputs, in order to see the outputs in realtime, \r\n    you need open quickfix window at first by using :copen (see :help copen). And there is a \r\n    function 'asyncrun#quickfix_toggle(size)' for you to open\/close it rapidly (see tutorial 9).\r\n\r\nTutorial 0: async run gcc \/ make to build current file\r\n    :AsyncRun gcc % -o %<\r\n    :AsyncRun g++ -O3 \"%\" -o \"%<\" -lpthread \r\n    :AsyncRun make -f Mymakefile\r\n\r\nTutorial 1: async grep key word\r\n    :AsyncRun! grep -R word . \r\n    :AsyncRun! grep -R  . \r\n\r\nTutorial 2: look up man page\r\n    :AsyncRun! man -S 3:2:1 \r\n\r\nTutorial 3: build go project\r\n    :AsyncRun go build \"%:p:h\"\r\n\r\nTutorial 4: use  to compile current file\r\n    :noremap  :AsyncRun gcc \"%\" -o \"%<\" \r\n\r\nTutorial 5: open quickfix window (see the output)\r\n    :botright copen 8\r\n\r\nTutorial 6: async git push\r\n    :AsyncRun git push origin master\r\n\r\nTutorial 7: compile markdown to pdf\r\n    :AsyncRun pandoc --output \"$(VIM_FILENOEXT).pdf\" \"%:p\" \r\n\r\nTutorial 8: update tags in background while editing (super useful for large projects):\r\n    :AsyncRun ctags -R --fields=+S .\r\n    :AsyncRun ctags -R -f $(VIM_FILEDIR)\/ctags.out --fields=+iaS $(VIM_FILEDIR)\r\n\r\nTutorial 9: a help function to toggle quickfix window in an efficient way (F9 to toggle):\r\n    :noremap  :call asyncrun#quickfix_toggle(8)\r\n\r\nPlease vote it if you like it.\r\n","install_details":"Copy asyncrun.vim to your ~\/.vim\/plugin or use Vundle to install it from skywind3000\/asyncrun.vim .","5":"Copy asyncrun.vim to your ~\/.vim\/plugin or use Vundle to install it from skywind3000\/asyncrun.vim .","first_name":"Wei","6":"Wei","last_name":"Lin","7":"Lin","releases":[{"0":"5431","vim_version":"8.0","1":"8.0","script_version":"2.12.5","2":"2.12.5","version_comment":"- set `g:asyncrun_mode` to 1 during creating a terminal buffer and clear it to 0 after buffer has been created.\r\n- script triggered by the `#TerminalOpen` or `#TermOpen` autocmd can use it to detect if this terminal is created by asyncrun.","3":"- set `g:asyncrun_mode` to 1 during creating a terminal buffer and clear it to 0 after buffer has been created.\r\n- script triggered by the `#TerminalOpen` or `#TermOpen` autocmd can use it to detect if this terminal is created by asyncrun.","package":"asyncrun.vim","4":"asyncrun.vim","src_id":"28655","5":"28655","creation_date":"1711126666","6":"1711126666"},{"0":"5431","vim_version":"8.0","1":"8.0","script_version":"2.12.4","2":"2.12.4","version_comment":"Refactor root locator function and update AsyncRun plugin version to 2.12.4","3":"Refactor root locator function and update AsyncRun plugin version to 2.12.4","package":"asyncrun.vim","4":"asyncrun.vim","src_id":"28617","5":"28617","creation_date":"1708437229","6":"1708437229"},{"0":"5431","vim_version":"8.0","1":"8.0","script_version":"2.12.3","2":"2.12.3","version_comment":"- Added handling for fugitive buffers in \"asyncrun#fullname()\" function","3":"- Added handling for fugitive buffers in \"asyncrun#fullname()\" function","package":"asyncrun.vim","4":"asyncrun.vim","src_id":"28610","5":"28610","creation_date":"1708056492","6":"1708056492"},{"0":"5431","vim_version":"8.0","1":"8.0","script_version":"2.12.2","2":"2.12.2","version_comment":"- accept \"AsyncRun :!!command\" to start GUI programs.\r\n- minor issues fixed.","3":"- accept \"AsyncRun :!!command\" to start GUI programs.\r\n- minor issues fixed.","package":"asyncrun.vim","4":"asyncrun.vim","src_id":"28549","5":"28549","creation_date":"1696097134","6":"1696097134"},{"0":"5431","vim_version":"8.0","1":"8.0","script_version":"2.11.23","2":"2.11.23","version_comment":"- added try\/catch for Ex commands (starting with colon), eg. \":AsyncRun  :echo 123\" and display exception if failed. \r\n- fixed minor issues. ","3":"- added try\/catch for Ex commands (starting with colon), eg. \":AsyncRun  :echo 123\" and display exception if failed. \r\n- fixed minor issues. ","package":"asyncrun.vim","4":"asyncrun.vim","src_id":"28548","5":"28548","creation_date":"1695207081","6":"1695207081"},{"0":"5431","vim_version":"8.0","1":"8.0","script_version":"2.11.20","2":"2.11.20","version_comment":"new api \"asyncrun#current_root()\" can return the current root directory.","3":"new api \"asyncrun#current_root()\" can return the current root directory.","package":"asyncrun.vim","4":"asyncrun.vim","src_id":"28533","5":"28533","creation_date":"1692591263","6":"1692591263"},{"0":"5431","vim_version":"8.0","1":"8.0","script_version":"2.11.19","2":"2.11.19","version_comment":"- new \"-init=script\" option to run a init script for terminal task after successfully opening the terminal window.\r\n- new \"-ft=filetype\" option to set filetype for a terminal buffer.","3":"- new \"-init=script\" option to run a init script for terminal task after successfully opening the terminal window.\r\n- new \"-ft=filetype\" option to set filetype for a terminal buffer.","package":"asyncrun.vim","4":"asyncrun.vim","src_id":"28523","5":"28523","creation_date":"1691081600","6":"1691081600"},{"0":"5431","vim_version":"8.0","1":"8.0","script_version":"2.11.16","2":"2.11.16","version_comment":"Strip message even if process fails","3":"Strip message even if process fails","package":"asyncrun.vim","4":"asyncrun.vim","src_id":"28373","5":"28373","creation_date":"1677797708","6":"1677797708"},{"0":"5431","vim_version":"8.0","1":"8.0","script_version":"2.11.15","2":"2.11.15","version_comment":"- new option \"-runner=xxx\" can work as an alias to \"-mode=term -pos=xxx\".\r\n- polish external function calling","3":"- new option \"-runner=xxx\" can work as an alias to \"-mode=term -pos=xxx\".\r\n- polish external function calling","package":"asyncrun.vim","4":"asyncrun.vim","src_id":"28354","5":"28354","creation_date":"1674077135","6":"1674077135"},{"0":"5431","vim_version":"8.0","1":"8.0","script_version":"2.11.14","2":"2.11.14","version_comment":"- terminal: only reuse terminal window created by asyncrun, prevent side-effect to other terminal plugins;\r\n- terminal: simplify terminal reusable check routine;\r\n- terminal: enable reuse by default for split terminal (can be disabled by -reuse=0);\r\n- terminal: enable autoscroll for terminal buffers in a non-active window (-focus=0);\r\n- terminal: accept \"-scroll=0\" to keep consistency with quickfix window.","3":"- terminal: only reuse terminal window created by asyncrun, prevent side-effect to other terminal plugins;\r\n- terminal: simplify terminal reusable check routine;\r\n- terminal: enable reuse by default for split terminal (can be disabled by -reuse=0);\r\n- terminal: enable autoscroll for terminal buffers in a non-active window (-focus=0);\r\n- terminal: accept \"-scroll=0\" to keep consistency with quickfix window.","package":"asyncrun.vim","4":"asyncrun.vim","src_id":"28282","5":"28282","creation_date":"1669709431","6":"1669709431"},{"0":"5431","vim_version":"8.0","1":"8.0","script_version":"2.11.9","2":"2.11.9","version_comment":"vim-7.4.1829 compliance","3":"vim-7.4.1829 compliance","package":"asyncrun.vim","4":"asyncrun.vim","src_id":"28277","5":"28277","creation_date":"1669595858","6":"1669595858"},{"0":"5431","vim_version":"8.0","1":"8.0","script_version":"2.11.6","2":"2.11.6","version_comment":"- terminal: initialize a proper terminal name for vim-8.2 and above.\r\n- terminal: enable safe-argument-passing mode for vim-8.2 and above.\r\n- terminal: wipe previous finished terminal buffer when '-reuse' is presented.\r\n- remove unnecessary messages.","3":"- terminal: initialize a proper terminal name for vim-8.2 and above.\r\n- terminal: enable safe-argument-passing mode for vim-8.2 and above.\r\n- terminal: wipe previous finished terminal buffer when '-reuse' is presented.\r\n- remove unnecessary messages.","package":"asyncrun.vim","4":"asyncrun.vim","src_id":"28274","5":"28274","creation_date":"1669027177","6":"1669027177"},{"0":"5431","vim_version":"8.0","1":"8.0","script_version":"2.11.3","2":"2.11.3","version_comment":"- new option g:asyncrun_term_wipe, set to non-zero to change the &bufhidden of terminal buffer to 'wipe' when command finished.\r\n- the default value of g:asyncrun_term_wipe is 1.\r\n","3":"- new option g:asyncrun_term_wipe, set to non-zero to change the &bufhidden of terminal buffer to 'wipe' when command finished.\r\n- the default value of g:asyncrun_term_wipe is 1.\r\n","package":"asyncrun.vim","4":"asyncrun.vim","src_id":"28269","5":"28269","creation_date":"1668824448","6":"1668824448"},{"0":"5431","vim_version":"8.0","1":"8.0","script_version":"2.10.9","2":"2.10.9","version_comment":"- revert command completion mode from \"shellcmd\" back to \"file\" because\r\n- The '%' will not be substituted when using \"shellcmd\", see: #264\r\n","3":"- revert command completion mode from \"shellcmd\" back to \"file\" because\r\n- The '%' will not be substituted when using \"shellcmd\", see: #264\r\n","package":"asyncrun.vim","4":"asyncrun.vim","src_id":"28248","5":"28248","creation_date":"1667477491","6":"1667477491"},{"0":"5431","vim_version":"8.0","1":"8.0","script_version":"2.10.8","2":"2.10.8","version_comment":"- improve nomodeline compatibility\r\n- take care of the \"&makeencoding\" option;\r\n- provide more information for runners and translators.","3":"- improve nomodeline compatibility\r\n- take care of the \"&makeencoding\" option;\r\n- provide more information for runners and translators.","package":"asyncrun.vim","4":"asyncrun.vim","src_id":"28246","5":"28246","creation_date":"1667418624","6":"1667418624"},{"0":"5431","vim_version":"8.0","1":"8.0","script_version":"2.10.6","2":"2.10.6","version_comment":"- fix: Use shellcmd completion for AsyncRun, see: #261\r\n- new runner for toggleterm: #257\r\n","3":"- fix: Use shellcmd completion for AsyncRun, see: #261\r\n- new runner for toggleterm: #257\r\n","package":"asyncrun.vim","4":"asyncrun.vim","src_id":"28242","5":"28242","creation_date":"1667130061","6":"1667130061"},{"0":"5431","vim_version":"8.0","1":"8.0","script_version":"2.10.5","2":"2.10.5","version_comment":"- Use  in :doautocmd, see #259.\r\n- new option g:asyncrun_show_time, set to 1 to display the command start time in the first line of quickfix window.\r\n","3":"- Use  in :doautocmd, see #259.\r\n- new option g:asyncrun_show_time, set to 1 to display the command start time in the first line of quickfix window.\r\n","package":"asyncrun.vim","4":"asyncrun.vim","src_id":"28212","5":"28212","creation_date":"1665539006","6":"1665539006"},{"0":"5431","vim_version":"8.0","1":"8.0","script_version":"2.10.0","2":"2.10.0","version_comment":"- new :AsyncReset command to reset all internal status.\r\n- fix: tab page restoration when \"focus=0\" & \"reuse=1\"\r\n- supports quickfix-id\r\n- keep compatible with vim-7.4.1829\r\n- better project root detection.","3":"- new :AsyncReset command to reset all internal status.\r\n- fix: tab page restoration when \"focus=0\" & \"reuse=1\"\r\n- supports quickfix-id\r\n- keep compatible with vim-7.4.1829\r\n- better project root detection.","package":"asyncrun.vim","4":"asyncrun.vim","src_id":"28199","5":"28199","creation_date":"1665036589","6":"1665036589"},{"0":"5431","vim_version":"8.0","1":"8.0","script_version":"2.9.9","2":"2.9.9","version_comment":"- new option g:asyncrun_pathfix to correct relative path mismatching issue in the quickfix window.\r\n- better arguments extracting.\r\n","3":"- new option g:asyncrun_pathfix to correct relative path mismatching issue in the quickfix window.\r\n- better arguments extracting.\r\n","package":"asyncrun.vim","4":"asyncrun.vim","src_id":"27941","5":"27941","creation_date":"1643930604","6":"1643930604"},{"0":"5431","vim_version":"8.0","1":"8.0","script_version":"2.9.7","2":"2.9.7","version_comment":"- new option \"-encoding=?\" makes it possible to specify encoding for each command's stdout independently.\r\n- fixed: \"-focus=0\" can't return previous tabpage with \"-pos=TAB\"","3":"- new option \"-encoding=?\" makes it possible to specify encoding for each command's stdout independently.\r\n- fixed: \"-focus=0\" can't return previous tabpage with \"-pos=TAB\"","package":"asyncrun.vim","4":"asyncrun.vim","src_id":"27867","5":"27867","creation_date":"1640327301","6":"1640327301"},{"0":"5431","vim_version":"8.0","1":"8.0","script_version":"2.9.5","2":"2.9.5","version_comment":"- new `-once` option to buffer all output and flush them at once when job is finished (behave like vim-dispatch)\r\n- fix: when the terminal is the last window `-mode=term -close=1` will exit vim.","3":"- new `-once` option to buffer all output and flush them at once when job is finished (behave like vim-dispatch)\r\n- fix: when the terminal is the last window `-mode=term -close=1` will exit vim.","package":"asyncrun.vim","4":"asyncrun.vim","src_id":"27860","5":"27860","creation_date":"1639979487","6":"1639979487"},{"0":"5431","vim_version":"8.0","1":"8.0","script_version":"2.9.3","2":"2.9.3","version_comment":"- externalize \"-program=xxx\" script to autoload\/asyncrun\/program\r\n- new option \"-scroll=0\" to disable quickfix auto-scrolling","3":"- externalize \"-program=xxx\" script to autoload\/asyncrun\/program\r\n- new option \"-scroll=0\" to disable quickfix auto-scrolling","package":"asyncrun.vim","4":"asyncrun.vim","src_id":"27851","5":"27851","creation_date":"1639807928","6":"1639807928"},{"0":"5431","vim_version":"8.0","1":"8.0","script_version":"2.9.1","2":"2.9.1","version_comment":"- unified terminal closing behavior in both vim & neovim when -mode=term & -close=1","3":"- unified terminal closing behavior in both vim & neovim when -mode=term & -close=1","package":"asyncrun.vim","4":"asyncrun.vim","src_id":"27842","5":"27842","creation_date":"1639618387","6":"1639618387"},{"0":"5431","vim_version":"8.0","1":"8.0","script_version":"2.8.9","2":"2.8.9","version_comment":"- fire AsyncRunInit autocmd when first calling :AsyncRun command.\r\n- new event dispatch mechanism.\r\n- better runner handling.\r\n","3":"- fire AsyncRunInit autocmd when first calling :AsyncRun command.\r\n- new event dispatch mechanism.\r\n- better runner handling.\r\n","package":"asyncrun.vim","4":"asyncrun.vim","src_id":"27841","5":"27841","creation_date":"1639549818","6":"1639549818"},{"0":"5431","vim_version":"8.0","1":"8.0","script_version":"2.8.5","2":"2.8.5","version_comment":"better terminal cwd handling.","3":"better terminal cwd handling.","package":"asyncrun.vim","4":"asyncrun.vim","src_id":"27549","5":"27549","creation_date":"1616973251","6":"1616973251"},{"0":"5431","vim_version":"8.0","1":"8.0","script_version":"2.8.2","2":"2.8.2","version_comment":"new option -pos=TAB for -mode=term to open a terminal in a new tab residing on the left side.\r\nnew option -close for -mode=term to close the terminal automatically when terminal process finished.","3":"new option -pos=TAB for -mode=term to open a terminal in a new tab residing on the left side.\r\nnew option -close for -mode=term to close the terminal automatically when terminal process finished.","package":"asyncrun.vim","4":"asyncrun.vim","src_id":"27465","5":"27465","creation_date":"1612361719","6":"1612361719"},{"0":"5431","vim_version":"8.0","1":"8.0","script_version":"2.8.1","2":"2.8.1","version_comment":"fixed: minor path related issues.\r\nimprove compatibility on windows.\r\n\r\n","3":"fixed: minor path related issues.\r\nimprove compatibility on windows.\r\n\r\n","package":"asyncrun.vim","4":"asyncrun.vim","src_id":"27464","5":"27464","creation_date":"1612320846","6":"1612320846"},{"0":"5431","vim_version":"8.0","1":"8.0","script_version":"2.7.9","2":"2.7.9","version_comment":"new: when -mode=wait is provided, use system() to run your command.","3":"new: when -mode=wait is provided, use system() to run your command.","package":"asyncrun.vim","4":"asyncrun.vim","src_id":"27458","5":"27458","creation_date":"1611925978","6":"1611925978"},{"0":"5431","vim_version":"8.0","1":"8.0","script_version":"2.7.8","2":"2.7.8","version_comment":"expose s:ScriptWrite interface to asyncrun#script_write.","3":"expose s:ScriptWrite interface to asyncrun#script_write.","package":"asyncrun.vim","4":"asyncrun.vim","src_id":"27442","5":"27442","creation_date":"1610485147","6":"1610485147"},{"0":"5431","vim_version":"8.0","1":"8.0","script_version":"2.7.7","2":"2.7.7","version_comment":"add autocmd AsyncRunInterrupt when job is stopped by AsyncStop","3":"add autocmd AsyncRunInterrupt when job is stopped by AsyncStop","package":"asyncrun.vim","4":"asyncrun.vim","src_id":"27430","5":"27430","creation_date":"1609285258","6":"1609285258"},{"0":"5431","vim_version":"8.0","1":"8.0","script_version":"2.7.5","2":"2.7.5","version_comment":"Project root can be overshadowed by b:asyncrun_root, t:asyncrun_root and g:asyncrun_root.","3":"Project root can be overshadowed by b:asyncrun_root, t:asyncrun_root and g:asyncrun_root.","package":"asyncrun.vim","4":"asyncrun.vim","src_id":"27112","5":"27112","creation_date":"1586434868","6":"1586434868"},{"0":"5431","vim_version":"8.0","1":"8.0","script_version":"2.7.3","2":"2.7.3","version_comment":"New macro $(VIM_PWD) to store vim's working directory (:pwd returns), different from $(VIM_CWD) which will follow \"-cwd=xxx\" option.","3":"New macro $(VIM_PWD) to store vim's working directory (:pwd returns), different from $(VIM_CWD) which will follow \"-cwd=xxx\" option.","package":"asyncrun.vim","4":"asyncrun.vim","src_id":"27109","5":"27109","creation_date":"1586319014","6":"1586319014"},{"0":"5431","vim_version":"8.0","1":"8.0","script_version":"2.7.1","2":"2.7.1","version_comment":"keep compatible to vim 7.3 with limited functionality.","3":"keep compatible to vim 7.3 with limited functionality.","package":"asyncrun.vim","4":"asyncrun.vim","src_id":"27092","5":"27092","creation_date":"1585222518","6":"1585222518"},{"0":"5431","vim_version":"8.0","1":"8.0","script_version":"2.7.0","2":"2.7.0","version_comment":"windows: follow \"shellslash\" option","3":"windows: follow \"shellslash\" option","package":"asyncrun.vim","4":"asyncrun.vim","src_id":"27091","5":"27091","creation_date":"1585107935","6":"1585107935"},{"0":"5431","vim_version":"8.0","1":"8.0","script_version":"2.6.9","2":"2.6.9","version_comment":"improve project root detection","3":"improve project root detection","package":"asyncrun.vim","4":"asyncrun.vim","src_id":"27086","5":"27086","creation_date":"1584973730","6":"1584973730"},{"0":"5431","vim_version":"8.0","1":"8.0","script_version":"2.6.8","2":"2.6.8","version_comment":"change: g:asyncrun_rootmarks accepts wildcards like \"*\" or \"?\".\r\nchange: -reuse=0 can be used in split terminals.\r\n\r\n","3":"change: g:asyncrun_rootmarks accepts wildcards like \"*\" or \"?\".\r\nchange: -reuse=0 can be used in split terminals.\r\n\r\n","package":"asyncrun.vim","4":"asyncrun.vim","src_id":"27083","5":"27083","creation_date":"1584896941","6":"1584896941"},{"0":"5431","vim_version":"8.0","1":"8.0","script_version":"2.6.7","2":"2.6.7","version_comment":"fixed: windows - exit code is always zero.","3":"fixed: windows - exit code is always zero.","package":"asyncrun.vim","4":"asyncrun.vim","src_id":"27072","5":"27072","creation_date":"1584043105","6":"1584043105"},{"0":"5431","vim_version":"8.0","1":"8.0","script_version":"2.6.6","2":"2.6.6","version_comment":"new: -pos accepts a new uppercase TAB to open internal terminal on the left of current tab.","3":"new: -pos accepts a new uppercase TAB to open internal terminal on the left of current tab.","package":"asyncrun.vim","4":"asyncrun.vim","src_id":"27069","5":"27069","creation_date":"1583942672","6":"1583942672"},{"0":"5431","vim_version":"8.0","1":"8.0","script_version":"2.6.2","2":"2.6.2","version_comment":"runner function's argument has been changed from string to a dictionary for flexibility.","3":"runner function's argument has been changed from string to a dictionary for flexibility.","package":"asyncrun.vim","4":"asyncrun.vim","src_id":"27060","5":"27060","creation_date":"1583665040","6":"1583665040"},{"0":"5431","vim_version":"8.0","1":"8.0","script_version":"2.6.0","2":"2.6.0","version_comment":"1. change: -post=xxx is available in terminal mode\r\n2. new: -pos=hide in terminal mode\r\n3. new: -name=abc to specify a name for terminal task\r\n4. new: g:asyncrun_name to get terminal task name. ","3":"1. change: -post=xxx is available in terminal mode\r\n2. new: -pos=hide in terminal mode\r\n3. new: -name=abc to specify a name for terminal task\r\n4. new: g:asyncrun_name to get terminal task name. ","package":"asyncrun.vim","4":"asyncrun.vim","src_id":"27058","5":"27058","creation_date":"1583588125","6":"1583588125"},{"0":"5431","vim_version":"8.0","1":"8.0","script_version":"2.5.5","2":"2.5.5","version_comment":"change: \"-mode=term -pos=tab\" now obeys \"-focus=0\".","3":"change: \"-mode=term -pos=tab\" now obeys \"-focus=0\".","package":"asyncrun.vim","4":"asyncrun.vim","src_id":"27056","5":"27056","creation_date":"1583564555","6":"1583564555"},{"0":"5431","vim_version":"8.0","1":"8.0","script_version":"2.5.4","2":"2.5.4","version_comment":"fixed minor issues, windows: correctly passing arguments ","3":"fixed minor issues, windows: correctly passing arguments ","package":"asyncrun.vim","4":"asyncrun.vim","src_id":"27054","5":"27054","creation_date":"1583536203","6":"1583536203"},{"0":"5431","vim_version":"8.0","1":"8.0","script_version":"2.5.3","2":"2.5.3","version_comment":"1. new option -silent to prevent open quickfix window no matter g:asyncrun_open is set or not.\r\n2. new command modifier can define your own \"-program=new_modifer\".\r\n\r\n","3":"1. new option -silent to prevent open quickfix window no matter g:asyncrun_open is set or not.\r\n2. new command modifier can define your own \"-program=new_modifer\".\r\n\r\n","package":"asyncrun.vim","4":"asyncrun.vim","src_id":"27044","5":"27044","creation_date":"1583116274","6":"1583116274"},{"0":"5431","vim_version":"8.0","1":"8.0","script_version":"2.5.0","2":"2.5.0","version_comment":"1. purify and refactor, remove useless codes.\r\n2. new command modifier g:asyncrun_program.\r\n3. the \"-program=xx\" supports msys, mingw32, mingw64 and cygwin.\r\n","3":"1. purify and refactor, remove useless codes.\r\n2. new command modifier g:asyncrun_program.\r\n3. the \"-program=xx\" supports msys, mingw32, mingw64 and cygwin.\r\n","package":"asyncrun.vim","4":"asyncrun.vim","src_id":"27038","5":"27038","creation_date":"1582949554","6":"1582949554"},{"0":"5431","vim_version":"8.0","1":"8.0","script_version":"2.4.9","2":"2.4.9","version_comment":"new: specify customized runner by g:asyncrun_runner, see customize runners.\r\nnew: run command with :execute if command is starting with a colon :.\r\nnew: the colon command can be disabled by setting g:asyncrun_strict to non-zero.\r\n\r\n","3":"new: specify customized runner by g:asyncrun_runner, see customize runners.\r\nnew: run command with :execute if command is starting with a colon :.\r\nnew: the colon command can be disabled by setting g:asyncrun_strict to non-zero.\r\n\r\n","package":"asyncrun.vim","4":"asyncrun.vim","src_id":"27028","5":"27028","creation_date":"1582308958","6":"1582308958"},{"0":"5431","vim_version":"8.0","1":"8.0","script_version":"2.4.6","2":"2.4.6","version_comment":"new macros for -program=wsl on Windows: \r\n$(WSL_FILEPATH) $(WSL_FILENAME) $(WSL_FILEDIR) $(WSL_FILENOEXT) \r\n$(WSL_PATHNOEXT) $(WSL_RELDIR) $(WSL_RELNAME) $(WSL_ROOT) \r\n$(WSL_CWD) $(WSL_CFILE)\r\n","3":"new macros for -program=wsl on Windows: \r\n$(WSL_FILEPATH) $(WSL_FILENAME) $(WSL_FILEDIR) $(WSL_FILENOEXT) \r\n$(WSL_PATHNOEXT) $(WSL_RELDIR) $(WSL_RELNAME) $(WSL_ROOT) \r\n$(WSL_CWD) $(WSL_CFILE)\r\n","package":"asyncrun.vim","4":"asyncrun.vim","src_id":"27007","5":"27007","creation_date":"1582064441","6":"1582064441"},{"0":"5431","vim_version":"8.0","1":"8.0","script_version":"2.4.5","2":"2.4.5","version_comment":"- \"$(VIM_PATHNOEXT)\" is not an absolute path, make it absolute.","3":"- \"$(VIM_PATHNOEXT)\" is not an absolute path, make it absolute.","package":"asyncrun.vim","4":"asyncrun.vim","src_id":"26999","5":"26999","creation_date":"1581979736","6":"1581979736"},{"0":"5431","vim_version":"8.0","1":"8.0","script_version":"2.4.4","2":"2.4.4","version_comment":"1. Fixed：neovim \"-mode=term -safe=1\" will break when home directory contains spaces\r\n2. Optimize in terminal mode.","3":"1. Fixed：neovim \"-mode=term -safe=1\" will break when home directory contains spaces\r\n2. Optimize in terminal mode.","package":"asyncrun.vim","4":"asyncrun.vim","src_id":"26995","5":"26995","creation_date":"1581892699","6":"1581892699"},{"0":"5431","vim_version":"8.0","1":"8.0","script_version":"2.4.3","2":"2.4.3","version_comment":"1. fixed: neovim+windows: arguments containing spaces break on windows.\r\n2. new: VIM_CLINE, VIM_PRONAME, VIM_DIRNAME","3":"1. fixed: neovim+windows: arguments containing spaces break on windows.\r\n2. new: VIM_CLINE, VIM_PRONAME, VIM_DIRNAME","package":"asyncrun.vim","4":"asyncrun.vim","src_id":"26994","5":"26994","creation_date":"1581865934","6":"1581865934"},{"0":"5431","vim_version":"8.0","1":"8.0","script_version":"2.4.2","2":"2.4.2","version_comment":"Add new macro $(VIM_FILETYPE)","3":"Add new macro $(VIM_FILETYPE)","package":"asyncrun.vim","4":"asyncrun.vim","src_id":"26992","5":"26992","creation_date":"1581817901","6":"1581817901"},{"0":"5431","vim_version":"7.0","1":"7.0","script_version":"2.4.1","2":"2.4.1","version_comment":"fixed: focusing issue in an internal terminal window.","3":"fixed: focusing issue in an internal terminal window.","package":"asyncrun.vim","4":"asyncrun.vim","src_id":"26981","5":"26981","creation_date":"1581546435","6":"1581546435"},{"0":"5431","vim_version":"8.0","1":"8.0","script_version":"2.2.9","2":"2.2.9","version_comment":"new terminal mode options: `-safe=1`, `-listed=0` and `-reuse`","3":"new terminal mode options: `-safe=1`, `-listed=0` and `-reuse`","package":"asyncrun.vim","4":"asyncrun.vim","src_id":"26974","5":"26974","creation_date":"1581319187","6":"1581319187"},{"0":"5431","vim_version":"8.0","1":"8.0","script_version":"2.2.6","2":"2.2.6","version_comment":"new: parameter `-hidden` when using `-mode=term` to set `bufhidden` to `hidden`\r\nimprove: keep alternative window when splitting an terminal window\r\nimprove: more safe to start a terminal in a new tab\r\n","3":"new: parameter `-hidden` when using `-mode=term` to set `bufhidden` to `hidden`\r\nimprove: keep alternative window when splitting an terminal window\r\nimprove: more safe to start a terminal in a new tab\r\n","package":"asyncrun.vim","4":"asyncrun.vim","src_id":"26965","5":"26965","creation_date":"1581007646","6":"1581007646"},{"0":"5431","vim_version":"8.0","1":"8.0","script_version":"2.2.3","2":"2.2.3","version_comment":"new: \"-program=wsl\" to run command in wsl (windows 10 only).","3":"new: \"-program=wsl\" to run command in wsl (windows 10 only).","package":"asyncrun.vim","4":"asyncrun.vim","src_id":"26960","5":"26960","creation_date":"1580886362","6":"1580886362"},{"0":"5431","vim_version":"8.0","1":"8.0","script_version":"2.2.2","2":"2.2.2","version_comment":"new option \"-pos=curwin\" to open terminal in current window.","3":"new option \"-pos=curwin\" to open terminal in current window.","package":"asyncrun.vim","4":"asyncrun.vim","src_id":"26958","5":"26958","creation_date":"1580883803","6":"1580883803"},{"0":"5431","vim_version":"8.0","1":"8.0","script_version":"2.2.1","2":"2.2.1","version_comment":"set noreletivenumber for terminal window.","3":"set noreletivenumber for terminal window.","package":"asyncrun.vim","4":"asyncrun.vim","src_id":"26929","5":"26929","creation_date":"1579541125","6":"1579541125"},{"0":"5431","vim_version":"8.0","1":"8.0","script_version":"2.2.0","2":"2.2.0","version_comment":"new `-focus=0` option for `-mode=term` to prevent focus change.","3":"new `-focus=0` option for `-mode=term` to prevent focus change.","package":"asyncrun.vim","4":"asyncrun.vim","src_id":"26925","5":"26925","creation_date":"1579359816","6":"1579359816"},{"0":"5431","vim_version":"8.0","1":"8.0","script_version":"2.1.9","2":"2.1.9","version_comment":"polish `-mode=term`, omit `number` and `signcolunm` in terminal","3":"polish `-mode=term`, omit `number` and `signcolunm` in terminal","package":"asyncrun.vim","4":"asyncrun.vim","src_id":"26914","5":"26914","creation_date":"1578798762","6":"1578798762"},{"0":"5431","vim_version":"8.0","1":"8.0","script_version":"2.1.7","2":"2.1.7","version_comment":"new options `errorformat` in asyncrun#run(...)","3":"new options `errorformat` in asyncrun#run(...)","package":"asyncrun.vim","4":"asyncrun.vim","src_id":"26909","5":"26909","creation_date":"1578711021","6":"1578711021"},{"0":"5431","vim_version":"8.0","1":"8.0","script_version":"2.1.1","2":"2.1.1","version_comment":"new: \"AsyncRun -mode=term -pos=bottom -rows=10 xxx\" to run command in a resuable terminal window.","3":"new: \"AsyncRun -mode=term -pos=bottom -rows=10 xxx\" to run command in a resuable terminal window.","package":"asyncrun.vim","4":"asyncrun.vim","src_id":"26897","5":"26897","creation_date":"1578570683","6":"1578570683"},{"0":"5431","vim_version":"7.4","1":"7.4","script_version":"2.0.8","2":"2.0.8","version_comment":"Handle tcd which was introduced in vim 8.1.1218.","3":"Handle tcd which was introduced in vim 8.1.1218.","package":"asyncrun.vim","4":"asyncrun.vim","src_id":"26469","5":"26469","creation_date":"1556467461","6":"1556467461"},{"0":"5431","vim_version":"8.0","1":"8.0","script_version":"2.0.7","2":"2.0.7","version_comment":"restore g:asyncrun_stdin because rg will break on windows if stdin is not null.","3":"restore g:asyncrun_stdin because rg will break on windows if stdin is not null.","package":"asyncrun.vim","4":"asyncrun.vim","src_id":"26363","5":"26363","creation_date":"1548679397","6":"1548679397"},{"0":"5431","vim_version":"8.0","1":"8.0","script_version":"2.0.6","2":"2.0.6","version_comment":"More adaptive to handle stdin and remove g:asyncrun_stdin option.","3":"More adaptive to handle stdin and remove g:asyncrun_stdin option.","package":"asyncrun.vim","4":"asyncrun.vim","src_id":"26361","5":"26361","creation_date":"1548471778","6":"1548471778"},{"0":"5431","vim_version":"8.0","1":"8.0","script_version":"2.0.5","2":"2.0.5","version_comment":"enable stdin on windows by default to fix cmake stdin warnings on windows.","3":"enable stdin on windows by default to fix cmake stdin warnings on windows.","package":"asyncrun.vim","4":"asyncrun.vim","src_id":"26346","5":"26346","creation_date":"1547391201","6":"1547391201"},{"0":"5431","vim_version":"7.4","1":"7.4","script_version":"2.0.4","2":"2.0.4","version_comment":"new option `g:asyncrun_stdin`, set to 1 to enable stdin (fix cmake warnings on windows).","3":"new option `g:asyncrun_stdin`, set to 1 to enable stdin (fix cmake warnings on windows).","package":"asyncrun.vim","4":"asyncrun.vim","src_id":"26339","5":"26339","creation_date":"1547361020","6":"1547361020"},{"0":"5431","vim_version":"7.4","1":"7.4","script_version":"2.0.3","2":"2.0.3","version_comment":"new environment variable: $VIM_PATHNOEXT - Current file name with full path but without extension\r\nnew environment variable: $VIM_HOME - first runtime path","3":"new environment variable: $VIM_PATHNOEXT - Current file name with full path but without extension\r\nnew environment variable: $VIM_HOME - first runtime path","package":"asyncrun.vim","4":"asyncrun.vim","src_id":"26316","5":"26316","creation_date":"1546626009","6":"1546626009"},{"0":"5431","vim_version":"7.4","1":"7.4","script_version":"2.0.1","2":"2.0.1","version_comment":"New option g:asyncrun_save to save files before executing.","3":"New option g:asyncrun_save to save files before executing.","package":"asyncrun.vim","4":"asyncrun.vim","src_id":"25954","5":"25954","creation_date":"1524951075","6":"1524951075"},{"0":"5431","vim_version":"7.4","1":"7.4","script_version":"2.0.0","2":"2.0.0","version_comment":"Improve neovim compatibility and handle `tcd` command correctly.","3":"Improve neovim compatibility and handle `tcd` command correctly.","package":"asyncrun.vim","4":"asyncrun.vim","src_id":"25949","5":"25949","creation_date":"1524825450","6":"1524825450"},{"0":"5431","vim_version":"7.4","1":"7.4","script_version":"1.3.27","2":"1.3.27","version_comment":"new: can take a range of text in current buffer as job's stdin.","3":"new: can take a range of text in current buffer as job's stdin.","package":"asyncrun.vim","4":"asyncrun.vim","src_id":"25933","5":"25933","creation_date":"1524088763","6":"1524088763"},{"0":"5431","vim_version":"7.4","1":"7.4","script_version":"1.3.26","2":"1.3.26","version_comment":"new option `g:asyncrun_wrapper` to enable setup a command prefix.","3":"new option `g:asyncrun_wrapper` to enable setup a command prefix.","package":"asyncrun.vim","4":"asyncrun.vim","src_id":"25926","5":"25926","creation_date":"1523878148","6":"1523878148"},{"0":"5431","vim_version":"7.4","1":"7.4","script_version":"1.3.25","2":"1.3.25","version_comment":"handle makeprg\/grepprg correctly, accept `%` and `$*` macros.","3":"handle makeprg\/grepprg correctly, accept `%` and `$*` macros.","package":"asyncrun.vim","4":"asyncrun.vim","src_id":"25925","5":"25925","creation_date":"1523868633","6":"1523868633"},{"0":"5431","vim_version":"7.4","1":"7.4","script_version":"1.3.22","2":"1.3.22","version_comment":"new option \"g:asyncrun_open\" to open quickfix automatically.","3":"new option \"g:asyncrun_open\" to open quickfix automatically.","package":"asyncrun.vim","4":"asyncrun.vim","src_id":"25878","5":"25878","creation_date":"1520868875","6":"1520868875"},{"0":"5431","vim_version":"7.4","1":"7.4","script_version":"1.3.19","2":"1.3.19","version_comment":"new option asyncrun_skip to disable specific autocmds","3":"new option asyncrun_skip to disable specific autocmds","package":"asyncrun.vim","4":"asyncrun.vim","src_id":"25711","5":"25711","creation_date":"1513151066","6":"1513151066"},{"0":"5431","vim_version":"7.4","1":"7.4","script_version":"1.3.17","2":"1.3.17","version_comment":"fixed: process will hang when mode is 5\r\nfixed: g:asyncrun_mode issue.\r\nfixed: remove trailing new line in neovim, improve asyncrun#execute.\r\nimprove asyncrun#get_root(), allow user to specify the rootmarkers\r\nnew option \"-raw\" to prevent output matching the errorformat, useful when you are running a script.\r\nRefactor, support  macro to indicate project root (depends on root markers)\r\n","3":"fixed: process will hang when mode is 5\r\nfixed: g:asyncrun_mode issue.\r\nfixed: remove trailing new line in neovim, improve asyncrun#execute.\r\nimprove asyncrun#get_root(), allow user to specify the rootmarkers\r\nnew option \"-raw\" to prevent output matching the errorformat, useful when you are running a script.\r\nRefactor, support  macro to indicate project root (depends on root markers)\r\n","package":"asyncrun.vim","4":"asyncrun.vim","src_id":"25479","5":"25479","creation_date":"1501986222","6":"1501986222"},{"0":"5431","vim_version":"7.4","1":"7.4","script_version":"1.3.11","2":"1.3.11","version_comment":"New option (-save=2) to save all modified buffers before executing.","3":"New option (-save=2) to save all modified buffers before executing.","package":"asyncrun.vim","4":"asyncrun.vim","src_id":"25219","5":"25219","creation_date":"1495182717","6":"1495182717"},{"0":"5431","vim_version":"7.4","1":"7.4","script_version":"1.3.8","2":"1.3.8","version_comment":"1. fixed conflict between caddexpr and command line window.\r\n2. add autocmd AsyncRunPre, AsyncRunStart and AsyncRunStop.","3":"1. fixed conflict between caddexpr and command line window.\r\n2. add autocmd AsyncRunPre, AsyncRunStart and AsyncRunStop.","package":"asyncrun.vim","4":"asyncrun.vim","src_id":"24740","5":"24740","creation_date":"1479385229","6":"1479385229"},{"0":"5431","vim_version":"7.4","1":"7.4","script_version":"1.3.7","2":"1.3.7","version_comment":"1. fixed issues in channel reading and arguments parsing\r\n2. flow control to prevent gui freeze by massive output","3":"1. fixed issues in channel reading and arguments parsing\r\n2. flow control to prevent gui freeze by massive output","package":"asyncrun.vim","4":"asyncrun.vim","src_id":"24729","5":"24729","creation_date":"1479070966","6":"1479070966"},{"0":"5431","vim_version":"7.4","1":"7.4","script_version":"1.3.6","2":"1.3.6","version_comment":"improve performance by add some noautocmd, fixed small issue in bell ringing. improve event hooking","3":"improve performance by add some noautocmd, fixed small issue in bell ringing. improve event hooking","package":"asyncrun.vim","4":"asyncrun.vim","src_id":"24713","5":"24713","creation_date":"1478551513","6":"1478551513"},{"0":"5431","vim_version":"7.4","1":"7.4","script_version":"1.3.5","2":"1.3.5","version_comment":"new option \"g:asyncrun_auto\" and \"-auto=?\" to trigger QuickFixCmdPre and QuickFixCmdPost. and can cooperate with errormaker.vim now","3":"new option \"g:asyncrun_auto\" and \"-auto=?\" to trigger QuickFixCmdPre and QuickFixCmdPost. and can cooperate with errormaker.vim now","package":"asyncrun.vim","4":"asyncrun.vim","src_id":"24699","5":"24699","creation_date":"1478061254","6":"1478061254"},{"0":"5431","vim_version":"7.4","1":"7.4","script_version":"1.3.3","2":"1.3.3","version_comment":"1. new option \"g:asyncrun_local\" to use local value of errorformat rather the global value. \r\n2. prevent job who reads from stdin getting hanging by setting in_io to null. \r\n3. fixed an issue in fast exiting programs","3":"1. new option \"g:asyncrun_local\" to use local value of errorformat rather the global value. \r\n2. prevent job who reads from stdin getting hanging by setting in_io to null. \r\n3. fixed an issue in fast exiting programs","package":"asyncrun.vim","4":"asyncrun.vim","src_id":"24676","5":"24676","creation_date":"1477587100","6":"1477587100"},{"0":"5431","vim_version":"7.4","1":"7.4","script_version":"1.3.2","2":"1.3.2","version_comment":"1. fixed few issues of arguments passing in different modes \r\n2. new \"-post\" option to run a vimscript after the job finished ","3":"1. fixed few issues of arguments passing in different modes \r\n2. new \"-post\" option to run a vimscript after the job finished ","package":"asyncrun.vim","4":"asyncrun.vim","src_id":"24651","5":"24651","creation_date":"1476868833","6":"1476868833"},{"0":"5431","vim_version":"7.4","1":"7.4","script_version":"0.0.0","2":"0.0.0","version_comment":"Initial upload","3":"Initial upload","package":"asyncrun.vim","4":"asyncrun.vim","src_id":"24465","5":"24465","creation_date":"1472027395","6":"1472027395"}]},"5430":{"script_id":"5430","0":"5430","script_name":"FocusPrevious","1":"FocusPrevious","script_type":"utility","2":"utility","summary":"Focus previous window\/tab when closing the current one.","3":"Focus previous window\/tab when closing the current one.","description":"I tend to open multiple tabs in vim and multiple windows within a tab.\r\n\r\nI have a habit of traversing the code in a tree format - I open a tag in a\r\nnew tab, so that my current view of the window remains unchanged. I can simply\r\nclose the newly opened tab\/window to resume to my previous view.\r\nConsider a case where I have window A focused. I open a new split as window B.\r\nNow, when I close window B, it should focus the earlier window A. Currently,\r\nit always focuses the window on left side of B.\r\n\r\nSimilarly, for tab close case, it always selects the tab on the right side of\r\ntab being closed.\r\n\r\nWith this plugin, it maintains the order in which the tabs are switched and\r\nthe order in which windows are switched within a tab.\r\nNOTE that the order of window switching is maintained in per-tab basis.\r\n\r\nWhen any window\/tab is closed, it focuses the tab that was last focussed.\r\n\r\nPlease provide feedback here: http:\/\/vi.stackexchange.com\/a\/9288\/2749 (My question which led me into writing this script.)","4":"I tend to open multiple tabs in vim and multiple windows within a tab.\r\n\r\nI have a habit of traversing the code in a tree format - I open a tag in a\r\nnew tab, so that my current view of the window remains unchanged. I can simply\r\nclose the newly opened tab\/window to resume to my previous view.\r\nConsider a case where I have window A focused. I open a new split as window B.\r\nNow, when I close window B, it should focus the earlier window A. Currently,\r\nit always focuses the window on left side of B.\r\n\r\nSimilarly, for tab close case, it always selects the tab on the right side of\r\ntab being closed.\r\n\r\nWith this plugin, it maintains the order in which the tabs are switched and\r\nthe order in which windows are switched within a tab.\r\nNOTE that the order of window switching is maintained in per-tab basis.\r\n\r\nWhen any window\/tab is closed, it focuses the tab that was last focussed.\r\n\r\nPlease provide feedback here: http:\/\/vi.stackexchange.com\/a\/9288\/2749 (My question which led me into writing this script.)","install_details":"Actual script needs to be copied to ~\/.vim\/plugin.\r\n\r\nThis package us a VIMBall.\r\n\r\nDownload the script as FocusPrevious.vmb using wget\/curl\r\n\r\nOn terminal:\r\n$ wget http:\/\/www.vim.org\/scripts\/download_script.php?src_id=24462 -O FocusPrevious.vmb # The download URL would vary with new version\r\n$ vim FocusPrevious.vmb\r\n\r\nInside vim:\r\n: source %\r\n: quit\r\n","5":"Actual script needs to be copied to ~\/.vim\/plugin.\r\n\r\nThis package us a VIMBall.\r\n\r\nDownload the script as FocusPrevious.vmb using wget\/curl\r\n\r\nOn terminal:\r\n$ wget http:\/\/www.vim.org\/scripts\/download_script.php?src_id=24462 -O FocusPrevious.vmb # The download URL would vary with new version\r\n$ vim FocusPrevious.vmb\r\n\r\nInside vim:\r\n: source %\r\n: quit\r\n","first_name":"Anish","6":"Anish","last_name":"Sane","7":"Sane","releases":[{"0":"5430","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"FocusPrevious.vmb","4":"FocusPrevious.vmb","src_id":"24462","5":"24462","creation_date":"1471853280","6":"1471853280"}]},"5429":{"script_id":"5429","0":"5429","script_name":"Smile","1":"Smile","script_type":"utility","2":"utility","summary":"Vimscript implementation of the :smile command","3":"Vimscript implementation of the :smile command","description":"\r\nGitHub repository: https:\/\/github.com\/idanarye\/vim-smile\r\n\r\n:smile is awesome, but not everyone can use it because some people use older Vim builds and others use Neovim.\r\n\r\nThis plugin implements :Smile in Vimscript, so that everyone can enjoy the pleasure of happiness!","4":"\r\nGitHub repository: https:\/\/github.com\/idanarye\/vim-smile\r\n\r\n:smile is awesome, but not everyone can use it because some people use older Vim builds and others use Neovim.\r\n\r\nThis plugin implements :Smile in Vimscript, so that everyone can enjoy the pleasure of happiness!","install_details":"","5":"","first_name":"Idan","6":"Idan","last_name":"Arye","7":"Arye","releases":[{"0":"5429","vim_version":"7.0","1":"7.0","script_version":"1.0.1","2":"1.0.1","version_comment":"Bugfix for earlier Vim builds","3":"Bugfix for earlier Vim builds","package":"smile_v1.0.1.zip","4":"smile_v1.0.1.zip","src_id":"24456","5":"24456","creation_date":"1471557527","6":"1471557527"},{"0":"5429","vim_version":"7.0","1":"7.0","script_version":"1.0.0","2":"1.0.0","version_comment":"Initial upload","3":"Initial upload","package":"smile_v1.0.0.zip","4":"smile_v1.0.0.zip","src_id":"24454","5":"24454","creation_date":"1471467143","6":"1471467143"}]},"5428":{"script_id":"5428","0":"5428","script_name":"dut.vim","1":"dut.vim","script_type":"syntax","2":"syntax","summary":"Syntax file for the Dut programming language.","3":"Syntax file for the Dut programming language.","description":"Syntax file for the Dut programming language.","4":"Syntax file for the Dut programming language.","install_details":"Copy it to ~\/.vim","5":"Copy it to ~\/.vim","first_name":"Thiago","6":"Thiago","last_name":"Avelino","7":"Avelino","releases":[{"0":"5428","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"dut.vim-master.zip","4":"dut.vim-master.zip","src_id":"24450","5":"24450","creation_date":"1471321625","6":"1471321625"}]},"5427":{"script_id":"5427","0":"5427","script_name":"vim-gotofile","1":"vim-gotofile","script_type":"ftplugin","2":"ftplugin","summary":"Enhance the native `gf` command to go to `node_modules`.","3":"Enhance the native `gf` command to go to `node_modules`.","description":"https:\/\/github.com\/zoubin\/vim-gotofile","4":"https:\/\/github.com\/zoubin\/vim-gotofile","install_details":"Vundle is the recommend way to install vim-gotofile.\r\nJust add a line 'Pluign zoubin\/vim-gotofile' to your vundle plugin intialization section.","5":"Vundle is the recommend way to install vim-gotofile.\r\nJust add a line 'Pluign zoubin\/vim-gotofile' to your vundle plugin intialization section.","first_name":"bin","6":"bin","last_name":"zou","7":"zou","releases":[{"0":"5427","vim_version":"7.4","1":"7.4","script_version":"1.0.0","2":"1.0.0","version_comment":"Initial upload","3":"Initial upload","package":"vim-gotofile.zip","4":"vim-gotofile.zip","src_id":"24444","5":"24444","creation_date":"1471190914","6":"1471190914"}]},"5426":{"script_id":"5426","0":"5426","script_name":"wildignore.vim","1":"wildignore.vim","script_type":"utility","2":"utility","summary":"A simple plugin that reads wildignore patterns from a file","3":"A simple plugin that reads wildignore patterns from a file","description":"A simple plugin that reads wildignore patterns from a file. By default, patterns are read from the wildignore file in runtimepath.\r\n\r\nThe syntax for pattern files is straightforward:\r\n\r\n    pattern1,pattern2\r\n    pattern3 \r\n\r\n    \" Empty lines and comments are permitted\r\n    pattern4 \r\n\r\nInspiration for this script was drawn from Adam Bellaire's excellent gitignore plugin.","4":"A simple plugin that reads wildignore patterns from a file. By default, patterns are read from the wildignore file in runtimepath.\r\n\r\nThe syntax for pattern files is straightforward:\r\n\r\n    pattern1,pattern2\r\n    pattern3 \r\n\r\n    \" Empty lines and comments are permitted\r\n    pattern4 \r\n\r\nInspiration for this script was drawn from Adam Bellaire's excellent gitignore plugin.","install_details":"Download and copy wildignore.vim to $HOME\/.vim\/plugins.\r\n\r\nTo install via pathogen.vim, issue:\r\n\r\n    $ cd $HOME\/.vim\/bundle\r\n    $ git clone git:\/\/github.com\/sstallion\/vim-wildignore.git","5":"Download and copy wildignore.vim to $HOME\/.vim\/plugins.\r\n\r\nTo install via pathogen.vim, issue:\r\n\r\n    $ cd $HOME\/.vim\/bundle\r\n    $ git clone git:\/\/github.com\/sstallion\/vim-wildignore.git","first_name":"Steven","6":"Steven","last_name":"Stallion","7":"Stallion","releases":[{"0":"5426","vim_version":"7.3","1":"7.3","script_version":"1.2","2":"1.2","version_comment":"Check for +wildignore feature","3":"Check for +wildignore feature","package":"wildignore.vim","4":"wildignore.vim","src_id":"24432","5":"24432","creation_date":"1470673884","6":"1470673884"},{"0":"5426","vim_version":"7.3","1":"7.3","script_version":"1.1","2":"1.1","version_comment":"Adjusted default fname behavior","3":"Adjusted default fname behavior","package":"wildignore.vim","4":"wildignore.vim","src_id":"24429","5":"24429","creation_date":"1470275275","6":"1470275275"},{"0":"5426","vim_version":"7.3","1":"7.3","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"wildignore.vim","4":"wildignore.vim","src_id":"24428","5":"24428","creation_date":"1470265166","6":"1470265166"}]},"5425":{"script_id":"5425","0":"5425","script_name":"highlightedyank","1":"highlightedyank","script_type":"utility","2":"utility","summary":"Make the yanked region apparent!","3":"Make the yanked region apparent!","description":"*Usage*\r\n\r\nmap y (highlightedyank)\r\n\r\nIf you want to optimize highlight duration, use g:highlightedyank_highlight_duration , b:highlightedyank_highlight_duration. Assign number of time in milli seconds.\r\n\r\nlet g:highlightedyank_highlight_duration = 1000\r\n\r\nIf a negative number is assigned, the highlight would get persistent.\r\n\r\nlet g:highlightedyank_highlight_duration = -1\r\n\r\nWhen a new text is yanked, the old highlighting would be deleted. Or when former lines are edited, the highlighting would be deleted to prevent shifting the position, also.\r\n\r\nThe latest version is available here. https:\/\/github.com\/machakann\/vim-highlightedyank","4":"*Usage*\r\n\r\nmap y (highlightedyank)\r\n\r\nIf you want to optimize highlight duration, use g:highlightedyank_highlight_duration , b:highlightedyank_highlight_duration. Assign number of time in milli seconds.\r\n\r\nlet g:highlightedyank_highlight_duration = 1000\r\n\r\nIf a negative number is assigned, the highlight would get persistent.\r\n\r\nlet g:highlightedyank_highlight_duration = -1\r\n\r\nWhen a new text is yanked, the old highlighting would be deleted. Or when former lines are edited, the highlighting would be deleted to prevent shifting the position, also.\r\n\r\nThe latest version is available here. https:\/\/github.com\/machakann\/vim-highlightedyank","install_details":"Unzip and just put all folders in your ~\/.vim.","5":"Unzip and just put all folders in your ~\/.vim.","first_name":"Masaaki","6":"Masaaki","last_name":"Nakamura","7":"Nakamura","releases":[{"0":"5425","vim_version":"7.4","1":"7.4","script_version":"1.0.1","2":"1.0.1","version_comment":"Bug fixes.","3":"Bug fixes.","package":"vim-highlightedyank-1.0.1.zip","4":"vim-highlightedyank-1.0.1.zip","src_id":"24455","5":"24455","creation_date":"1471524067","6":"1471524067"},{"0":"5425","vim_version":"7.4","1":"7.4","script_version":"1.0.0","2":"1.0.0","version_comment":"Initial upload","3":"Initial upload","package":"vim-highlightedyank-1.0.0.zip","4":"vim-highlightedyank-1.0.0.zip","src_id":"24416","5":"24416","creation_date":"1469938191","6":"1469938191"}]},"5424":{"script_id":"5424","0":"5424","script_name":"dialect.vim","1":"dialect.vim","script_type":"utility","2":"utility","summary":"Project specific spell files","3":"Project specific spell files","description":"A simple plugin that persists the words added with zG and zW to a spellfile specific to the current directory.\r\n\r\n    1. Keep using zg and zw the way you always did.\r\n\r\n    2. The words you add with zG and zW will be added to \".\/.dialect.{encoding}.add\".\r\n\r\n    3. You can change the default file with \"let g:dialectfile = 'yourfile.utf-8.add'\".\r\n\r\nThat's it!\r\n\r\nCheck https:\/\/github.com\/danielbmarques\/vim-dialect","4":"A simple plugin that persists the words added with zG and zW to a spellfile specific to the current directory.\r\n\r\n    1. Keep using zg and zw the way you always did.\r\n\r\n    2. The words you add with zG and zW will be added to \".\/.dialect.{encoding}.add\".\r\n\r\n    3. You can change the default file with \"let g:dialectfile = 'yourfile.utf-8.add'\".\r\n\r\nThat's it!\r\n\r\nCheck https:\/\/github.com\/danielbmarques\/vim-dialect","install_details":"Install Dialect using your favorite plugin manager or copy dialect.vim to \"~\/.vim\/plugin\".","5":"Install Dialect using your favorite plugin manager or copy dialect.vim to \"~\/.vim\/plugin\".","first_name":"Daniel","6":"Daniel","last_name":"Marques","7":"Marques","releases":[{"0":"5424","vim_version":"7.4","1":"7.4","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"dialect.zip","4":"dialect.zip","src_id":"24415","5":"24415","creation_date":"1469847760","6":"1469847760"}]},"5423":{"script_id":"5423","0":"5423","script_name":"ditto.vim","1":"ditto.vim","script_type":"utility","2":"utility","summary":"Highlight overused words","3":"Highlight overused words","description":"Ditto is a Vim plugin that highlights overused words.\r\n\r\nYou can see the most frequent words in each sentence, paragraph or file, cycle through them, chose which words to ignore and more.\r\n\r\nCheck https:\/\/github.com\/danielbmarques\/vim-ditto.","4":"Ditto is a Vim plugin that highlights overused words.\r\n\r\nYou can see the most frequent words in each sentence, paragraph or file, cycle through them, chose which words to ignore and more.\r\n\r\nCheck https:\/\/github.com\/danielbmarques\/vim-ditto.","install_details":"1. Install Ditto using your favorite plugin manager or copy each file to its corresponding directory under ~\/.vim\/.\r\n\r\n2. Add this to your .vimrc:\r\n\r\n        au FileType markdown,text,tex DittoOn \" Turn on Ditto's autocmds\r\n        \r\n        nmap di ToggleDitto     \" Turn it on and off\r\n        \r\n        nmap =d DittoNext               \" Jump to the next word\r\n        nmap -d DittoPrev               \" Jump to the previous word\r\n        nmap +d DittoGood               \" Ignore the word under the cursor\r\n        nmap _d DittoBad                \" Stop ignoring the word under the cursor\r\n        nmap ]d DittoMore               \" Show the next matches\r\n        nmap [d DittoLess               \" Show the previous matches\r\n\r\n    (Chose the filetypes and mappings you prefer. These are only suggestions.)\r\n\r\n3. Stop procrastinating and write (God knows I should).\r\n\r\n:DittoOn starts a set of autocmds that keep the highlighting up to date. If you don't like that idea or run into any problems, read the full documentation for other options.","5":"1. Install Ditto using your favorite plugin manager or copy each file to its corresponding directory under ~\/.vim\/.\r\n\r\n2. Add this to your .vimrc:\r\n\r\n        au FileType markdown,text,tex DittoOn \" Turn on Ditto's autocmds\r\n        \r\n        nmap di ToggleDitto     \" Turn it on and off\r\n        \r\n        nmap =d DittoNext               \" Jump to the next word\r\n        nmap -d DittoPrev               \" Jump to the previous word\r\n        nmap +d DittoGood               \" Ignore the word under the cursor\r\n        nmap _d DittoBad                \" Stop ignoring the word under the cursor\r\n        nmap ]d DittoMore               \" Show the next matches\r\n        nmap [d DittoLess               \" Show the previous matches\r\n\r\n    (Chose the filetypes and mappings you prefer. These are only suggestions.)\r\n\r\n3. Stop procrastinating and write (God knows I should).\r\n\r\n:DittoOn starts a set of autocmds that keep the highlighting up to date. If you don't like that idea or run into any problems, read the full documentation for other options.","first_name":"Daniel","6":"Daniel","last_name":"Marques","7":"Marques","releases":[{"0":"5423","vim_version":"7.4","1":"7.4","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"ditto.zip","4":"ditto.zip","src_id":"24414","5":"24414","creation_date":"1469847457","6":"1469847457"}]},"5422":{"script_id":"5422","0":"5422","script_name":"vseq.vim","1":"vseq.vim","script_type":"utility","2":"utility","summary":"Generate sequential number vertically","3":"Generate sequential number vertically","description":"Select same numbers vertically by visual block select, and execute `:VSeqIncrDec`.\r\nSo, the numbers become the incremented sequence by decimal number.\r\nUnlike g, this plugin can select radix manually, and automatically aligns by white space or zero padding.\r\n\r\nmore info: https:\/\/github.com\/dalance\/vseq.vim","4":"Select same numbers vertically by visual block select, and execute `:VSeqIncrDec`.\r\nSo, the numbers become the incremented sequence by decimal number.\r\nUnlike g, this plugin can select radix manually, and automatically aligns by white space or zero padding.\r\n\r\nmore info: https:\/\/github.com\/dalance\/vseq.vim","install_details":"Unzip and put all folders in your ~\/.vim.","5":"Unzip and put all folders in your ~\/.vim.","first_name":"","6":"","last_name":"","7":"","releases":[{"0":"5422","vim_version":"7.0","1":"7.0","script_version":"1.0.0","2":"1.0.0","version_comment":"Initial upload","3":"Initial upload","package":"vseq.vim-1.0.0.zip","4":"vseq.vim-1.0.0.zip","src_id":"24392","5":"24392","creation_date":"1469361637","6":"1469361637"}]},"5421":{"script_id":"5421","0":"5421","script_name":"audionote.vim","1":"audionote.vim","script_type":"utility","2":"utility","summary":"Audio note - voice recorder ","3":"Audio note - voice recorder ","description":"Audio note with Vim, unite.vim plugin.\r\n\r\nmore info: https:\/\/github.com\/xerron\/audionote.vim","4":"Audio note with Vim, unite.vim plugin.\r\n\r\nmore info: https:\/\/github.com\/xerron\/audionote.vim","install_details":"Require:\r\n\r\n- Unite.vim\r\n\r\nGNU\/Linux\r\n\r\n    ogg123 (sudo apt-get install install vorbis-tools)\r\n    speex (sudo apt-get install speex)\r\n    alsamixer (arecord command)\r\n\r\nI use speex for encode audio, very good for voice recorder.\r\n\r\nWindows\r\n\r\nI hate windows but try configure global variables. ","5":"Require:\r\n\r\n- Unite.vim\r\n\r\nGNU\/Linux\r\n\r\n    ogg123 (sudo apt-get install install vorbis-tools)\r\n    speex (sudo apt-get install speex)\r\n    alsamixer (arecord command)\r\n\r\nI use speex for encode audio, very good for voice recorder.\r\n\r\nWindows\r\n\r\nI hate windows but try configure global variables. ","first_name":"Edwin Manuel","6":"Edwin Manuel","last_name":"Cerr\u00c3\u00b3n Angeles","7":"Cerr\u00c3\u00b3n Angeles","releases":[{"0":"5421","vim_version":"7.4","1":"7.4","script_version":"1.0.0","2":"1.0.0","version_comment":"Initial upload","3":"Initial upload","package":"audionote.vim-1.0.0.zip","4":"audionote.vim-1.0.0.zip","src_id":"24379","5":"24379","creation_date":"1468803810","6":"1468803810"}]},"5420":{"script_id":"5420","0":"5420","script_name":"cpf_upf_sdc","1":"cpf_upf_sdc","script_type":"utility","2":"utility","summary":"Syntax highlighting for CPF, UPF and SDC","3":"Syntax highlighting for CPF, UPF and SDC","description":"Syntax highlighting for \r\nCommon Power Format(CPF)@2.0, \r\nUnified Power Format(UPF)@2.1, IEEE1801-2013\r\nDesign Constraints Format(SDC)@2.0\r\n\r\nIt recognizes cpf, upf and sdc syntax in *.cpf, *.upf and *.sdc files. \r\n","4":"Syntax highlighting for \r\nCommon Power Format(CPF)@2.0, \r\nUnified Power Format(UPF)@2.1, IEEE1801-2013\r\nDesign Constraints Format(SDC)@2.0\r\n\r\nIt recognizes cpf, upf and sdc syntax in *.cpf, *.upf and *.sdc files. \r\n","install_details":"tar xzvf cpf_upf_sdc.tar.z in $HOME, ","5":"tar xzvf cpf_upf_sdc.tar.z in $HOME, ","first_name":"Gaofeng","6":"Gaofeng","last_name":"Dong","7":"Dong","releases":[{"0":"5420","vim_version":"7.0","1":"7.0","script_version":"1.1","2":"1.1","version_comment":"upgrade CPF@1.0e to CPF@2.0","3":"upgrade CPF@1.0e to CPF@2.0","package":"cpf_upf_sdc.tar.z","4":"cpf_upf_sdc.tar.z","src_id":"26138","5":"26138","creation_date":"1532019165","6":"1532019165"},{"0":"5420","vim_version":"7.0","1":"7.0","script_version":"1","2":"1","version_comment":"Initial upload","3":"Initial upload","package":"cpf_upf_sdc.tar.z","4":"cpf_upf_sdc.tar.z","src_id":"24372","5":"24372","creation_date":"1468308040","6":"1468308040"}]},"5419":{"script_id":"5419","0":"5419","script_name":"gtm-plugin.vim","1":"gtm-plugin.vim","script_type":"utility","2":"utility","summary":"Simple, seamless, lightweight time tracking for all your git projects","3":"Simple, seamless, lightweight time tracking for all your git projects","description":"Git Time Metrics (GTM) is a tool to automatically track time spent reading and working on code that you store in a Git repository. By installing GTM and using supported plug-ins for your favorite editors, you can immediately realize better insight into how you are spending your time and on what files.\r\n\r\nSee https:\/\/github.com\/git-time-metric\/gtm-vim-plugin\/blob\/master\/README.md for feature and usage information.\r\n\r\nTo report a bug, please submit an issue on GitHub https:\/\/github.com\/git-time-metric\/gtm-vim-plugin\/issues","4":"Git Time Metrics (GTM) is a tool to automatically track time spent reading and working on code that you store in a Git repository. By installing GTM and using supported plug-ins for your favorite editors, you can immediately realize better insight into how you are spending your time and on what files.\r\n\r\nSee https:\/\/github.com\/git-time-metric\/gtm-vim-plugin\/blob\/master\/README.md for feature and usage information.\r\n\r\nTo report a bug, please submit an issue on GitHub https:\/\/github.com\/git-time-metric\/gtm-vim-plugin\/issues","install_details":"Installing GTM is a two step process. First, it's recommended you install the GTM executable that the plug-in integrates with and then install the Vim GTM plug-in. Please submit an issue if you have any problems and\/or questions.\r\n\r\n1. Follow the Getting Started section, https:\/\/github.com\/git-time-metric\/gtm\/blob\/master\/README.md,  to install the GTM executable for your operating system.\r\n\r\n2. The easy way to install the plug-in is to use your favorite Vim plug-in manager.\r\n\r\n    Plug             Plug 'git-time-metric\/gtm-vim-plugin'\r\n    NeoBundle  NeoBundle 'git-time-metric\/gtm-vim-plugin'\r\n    Vundle         Plugin 'git-time-metric\/gtm-vim-plugin'\r\n    Pathogen     git clone https:\/\/github.com\/git-time-metric\/gtm ~\/.vim\/bundle\/gtm\r\n\r\nNote - to enable time tracking for a Git repository, you need to initialize it with `gtm init` otherwise it will be ignored by GTM. This is done via the command line.\r\n\r\n> cd \/path\/to\/your\/project\r\n> gtm init\r\n","5":"Installing GTM is a two step process. First, it's recommended you install the GTM executable that the plug-in integrates with and then install the Vim GTM plug-in. Please submit an issue if you have any problems and\/or questions.\r\n\r\n1. Follow the Getting Started section, https:\/\/github.com\/git-time-metric\/gtm\/blob\/master\/README.md,  to install the GTM executable for your operating system.\r\n\r\n2. The easy way to install the plug-in is to use your favorite Vim plug-in manager.\r\n\r\n    Plug             Plug 'git-time-metric\/gtm-vim-plugin'\r\n    NeoBundle  NeoBundle 'git-time-metric\/gtm-vim-plugin'\r\n    Vundle         Plugin 'git-time-metric\/gtm-vim-plugin'\r\n    Pathogen     git clone https:\/\/github.com\/git-time-metric\/gtm ~\/.vim\/bundle\/gtm\r\n\r\nNote - to enable time tracking for a Git repository, you need to initialize it with `gtm init` otherwise it will be ignored by GTM. This is done via the command line.\r\n\r\n> cd \/path\/to\/your\/project\r\n> gtm init\r\n","first_name":"Michael","6":"Michael","last_name":"Schenk","7":"Schenk","releases":[{"0":"5419","vim_version":"7.0","1":"7.0","script_version":"v1.0.7","2":"v1.0.7","version_comment":"Update gtm version constraint to gtm 1.2.5 and readme updates","3":"Update gtm version constraint to gtm 1.2.5 and readme updates","package":"gtm-vim-plugin-1.0.7.tar.gz","4":"gtm-vim-plugin-1.0.7.tar.gz","src_id":"24916","5":"24916","creation_date":"1485124908","6":"1485124908"},{"0":"5419","vim_version":"7.0","1":"7.0","script_version":"1.0.6","2":"1.0.6","version_comment":"Release gtm 1.2.1","3":"Release gtm 1.2.1","package":"gtm-vim-plugin-1.0.6.tar.gz","4":"gtm-vim-plugin-1.0.6.tar.gz","src_id":"24752","5":"24752","creation_date":"1479681452","6":"1479681452"},{"0":"5419","vim_version":"7.0","1":"7.0","script_version":"1.0.5","2":"1.0.5","version_comment":"README updates","3":"README updates","package":"gtm-vim-plugin-1.0.5.tar.gz","4":"gtm-vim-plugin-1.0.5.tar.gz","src_id":"24678","5":"24678","creation_date":"1477765903","6":"1477765903"},{"0":"5419","vim_version":"7.0","1":"7.0","script_version":"v1.0.4","2":"v1.0.4","version_comment":"Update gtm version constraint to 1.1.0\r\n\r\nGTM now supports Terminal tracking!","3":"Update gtm version constraint to 1.1.0\r\n\r\nGTM now supports Terminal tracking!","package":"gtm-vim-plugin-1.0.4.tar.gz","4":"gtm-vim-plugin-1.0.4.tar.gz","src_id":"24596","5":"24596","creation_date":"1475967927","6":"1475967927"},{"0":"5419","vim_version":"7.2","1":"7.2","script_version":"v1.0.3","2":"v1.0.3","version_comment":"- Option to disable version verify\r\n- Remove post processing of status","3":"- Option to disable version verify\r\n- Remove post processing of status","package":"gtm-vim-plugin-1.0.3.tar.gz","4":"gtm-vim-plugin-1.0.3.tar.gz","src_id":"24534","5":"24534","creation_date":"1474156544","6":"1474156544"},{"0":"5419","vim_version":"7.0","1":"7.0","script_version":"v1.0.2","2":"v1.0.2","version_comment":"Require GTM v1.0.0","3":"Require GTM v1.0.0","package":"gtm-vim-plugin-1.0.2.tar","4":"gtm-vim-plugin-1.0.2.tar","src_id":"24434","5":"24434","creation_date":"1470701560","6":"1470701560"},{"0":"5419","vim_version":"7.0","1":"7.0","script_version":"1.0.1","2":"1.0.1","version_comment":" Improve error handling and informing user","3":" Improve error handling and informing user","package":"gtm-vim-plugin-1.0.1.tar","4":"gtm-vim-plugin-1.0.1.tar","src_id":"24388","5":"24388","creation_date":"1469337719","6":"1469337719"},{"0":"5419","vim_version":"7.2","1":"7.2","script_version":"1.0.0","2":"1.0.0","version_comment":"Initial upload","3":"Initial upload","package":"gtm-vim-plugin-v1.0.0.zip","4":"gtm-vim-plugin-v1.0.0.zip","src_id":"24368","5":"24368","creation_date":"1468204319","6":"1468204319"}]},"5418":{"script_id":"5418","0":"5418","script_name":"vimmake","1":"vimmake","script_type":"utility","2":"utility","summary":"Customize shell tools for vim (supports async jobs)","3":"Customize shell tools for vim (supports async jobs)","description":"This script is obsoleted by asyncrun: \r\nhttps:\/\/www.vim.org\/scripts\/script.php?script_id=5431","4":"This script is obsoleted by asyncrun: \r\nhttps:\/\/www.vim.org\/scripts\/script.php?script_id=5431","install_details":"Copy vimmake.vim to your ~\/.vim\/plugin or use Vundle to install it from skywind3000\/vimmake.","5":"Copy vimmake.vim to your ~\/.vim\/plugin or use Vundle to install it from skywind3000\/vimmake.","first_name":"Wei","6":"Wei","last_name":"Lin","7":"Lin","releases":[{"0":"5418","vim_version":"7.4","1":"7.4","script_version":"1.1.9","2":"1.1.9","version_comment":"Handle tcd which was introduced in vim 8.1.1218.","3":"Handle tcd which was introduced in vim 8.1.1218.","package":"vimmake.vim","4":"vimmake.vim","src_id":"26468","5":"26468","creation_date":"1556467419","6":"1556467419"}]},"5417":{"script_id":"5417","0":"5417","script_name":"python-compilers.vim","1":"python-compilers.vim","script_type":"syntax","2":"syntax","summary":"Just a python compilers for VIM","3":"Just a python compilers for VIM","description":"A collection of python compilers (flake8 and pylint)","4":"A collection of python compilers (flake8 and pylint)","install_details":"As usual, you can install it with your prefered VIM plugin manager (like Plug or Vundle). If you want to install it by yourself, just copy the compiler folder to your ~\/.vim folder.","5":"As usual, you can install it with your prefered VIM plugin manager (like Plug or Vundle). If you want to install it by yourself, just copy the compiler folder to your ~\/.vim folder.","first_name":"Diego","6":"Diego","last_name":"Garcia","7":"Garcia","releases":[{"0":"5417","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"python-compilers.vim.zip","4":"python-compilers.vim.zip","src_id":"24360","5":"24360","creation_date":"1467822525","6":"1467822525"}]},"5416":{"script_id":"5416","0":"5416","script_name":"vim-two-firewatch","1":"vim-two-firewatch","script_type":"color scheme","2":"color scheme","summary":"A blend between duotone light and firewatch for atom","3":"A blend between duotone light and firewatch for atom","description":"Vim-Two-Firewatch is a GUI and true color optimised colorscheme that gracefully adapts if your environment supports only 256 colors. It comes with a light and a dark variation.\r\n\r\nOfficial repo: https:\/\/github.com\/rakr\/vim-two-firewatch","4":"Vim-Two-Firewatch is a GUI and true color optimised colorscheme that gracefully adapts if your environment supports only 256 colors. It comes with a light and a dark variation.\r\n\r\nOfficial repo: https:\/\/github.com\/rakr\/vim-two-firewatch","install_details":"","5":"","first_name":"Ramzi","6":"Ramzi","last_name":"Akremi","7":"Akremi","releases":[{"0":"5416","vim_version":"7.4","1":"7.4","script_version":"1.0.0","2":"1.0.0","version_comment":"Initial upload","3":"Initial upload","package":"vim-two-firewatch.zip","4":"vim-two-firewatch.zip","src_id":"24357","5":"24357","creation_date":"1467468701","6":"1467468701"}]},"5415":{"script_id":"5415","0":"5415","script_name":"vim-one","1":"vim-one","script_type":"color scheme","2":"color scheme","summary":"one dark and one light for atom adapted to Vim","3":"one dark and one light for atom adapted to Vim","description":"Light and dark vim colorscheme, shamelessly stolen from atom (another excellent text editor). One is best suited for GUI but does fallback gracefully and automatically if your environment does not support true colors.\r\n\r\nOfficial repo: https:\/\/github.com\/rakr\/vim-one","4":"Light and dark vim colorscheme, shamelessly stolen from atom (another excellent text editor). One is best suited for GUI but does fallback gracefully and automatically if your environment does not support true colors.\r\n\r\nOfficial repo: https:\/\/github.com\/rakr\/vim-one","install_details":"","5":"","first_name":"Ramzi","6":"Ramzi","last_name":"Akremi","7":"Akremi","releases":[{"0":"5415","vim_version":"7.4","1":"7.4","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"vim-one.zip","4":"vim-one.zip","src_id":"24356","5":"24356","creation_date":"1467468567","6":"1467468567"}]},"5414":{"script_id":"5414","0":"5414","script_name":"vim-tf2","1":"vim-tf2","script_type":"syntax","2":"syntax","summary":"TF2 .cfg syntax highlighting. https:\/\/github.com\/au\/vim-tf2","3":"TF2 .cfg syntax highlighting. https:\/\/github.com\/au\/vim-tf2","description":"https:\/\/github.com\/au\/vim-tf2\r\n\r\nThis is a dead simple syntax highlighter for tf2's configuration .cfg files. See the github page for installation instructions and updates.\r\n\r\nScreenshot: https:\/\/raw.githubusercontent.com\/au\/vim-tf2\/master\/screenshot.png\r\n\r\nLicense is MIT.","4":"https:\/\/github.com\/au\/vim-tf2\r\n\r\nThis is a dead simple syntax highlighter for tf2's configuration .cfg files. See the github page for installation instructions and updates.\r\n\r\nScreenshot: https:\/\/raw.githubusercontent.com\/au\/vim-tf2\/master\/screenshot.png\r\n\r\nLicense is MIT.","install_details":"Pathogen:\r\nOSX: git clone git@github.com:au\/vim-tf2.git ~\/.vim\/bundle\/vim-tf2\r\nWindows: git clone git@github.com:au\/vim-tf2.git %userprofile%\/vimfiles\/bundle\/vim-tf2\r\n\r\nFor manual, see the github page.","5":"Pathogen:\r\nOSX: git clone git@github.com:au\/vim-tf2.git ~\/.vim\/bundle\/vim-tf2\r\nWindows: git clone git@github.com:au\/vim-tf2.git %userprofile%\/vimfiles\/bundle\/vim-tf2\r\n\r\nFor manual, see the github page.","first_name":"Aug","6":"Aug","last_name":"F","7":"F","releases":[{"0":"5414","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Upkeep with github.","3":"Upkeep with github.","package":"vim-tf2.zip","4":"vim-tf2.zip","src_id":"24354","5":"24354","creation_date":"1467398247","6":"1467398247"},{"0":"5414","vim_version":"7.0","1":"7.0","script_version":"0.0","2":"0.0","version_comment":"Initial upload","3":"Initial upload","package":"vim-tf2.zip","4":"vim-tf2.zip","src_id":"24353","5":"24353","creation_date":"1467332891","6":"1467332891"}]},"5413":{"script_id":"5413","0":"5413","script_name":"vim-dispatch-vimproc","1":"vim-dispatch-vimproc","script_type":"utility","2":"utility","summary":"the plugin to add vimproc strategy to vim-dispatch","3":"the plugin to add vimproc strategy to vim-dispatch","description":"the plugin to add vimproc strategy to vim-dispatch [https:\/\/github.com\/tpope\/vim-dispatch]\r\n\r\nurl: https:\/\/github.com\/ompugao\/vim-dispatch-vimproc","4":"the plugin to add vimproc strategy to vim-dispatch [https:\/\/github.com\/tpope\/vim-dispatch]\r\n\r\nurl: https:\/\/github.com\/ompugao\/vim-dispatch-vimproc","install_details":"","5":"","first_name":"Shohei","6":"Shohei","last_name":"Fujii","7":"Fujii","releases":[{"0":"5413","vim_version":"7.0","1":"7.0","script_version":"0.0.1","2":"0.0.1","version_comment":"Initial upload","3":"Initial upload","package":"vim-dispatch-vimproc_0.0.1.zip","4":"vim-dispatch-vimproc_0.0.1.zip","src_id":"24350","5":"24350","creation_date":"1467274455","6":"1467274455"}]},"5412":{"script_id":"5412","0":"5412","script_name":"One Half Color Schemes","1":"One Half Color Schemes","script_type":"color scheme","2":"color scheme","summary":"Clean and vibrant light\/dark color schemes for terminal and gui Vim.","3":"Clean and vibrant light\/dark color schemes for terminal and gui Vim.","description":"Clean, vibrant, modern and pleasing light\/dark color schemes for terminal and gui Vim.\r\n\r\nConsistent cterm and gui colors, plus matching themes for plugins such as vim-airline, lightline or NERDTree. Provides harmonious colors and styles for all UI elements and syntax groups.\r\n\r\nScreenshot: https:\/\/github.com\/sonph\/onehalf\/blob\/master\/screenshots\/main.png\r\nMore screenshots: https:\/\/github.com\/sonph\/onehalf\/tree\/master\/screenshots\r\nMore information: https:\/\/github.com\/sonph\/onehalf\r\n\r\nMatching color schemes for other editors and terminals such as gnome-terminal, iTerm, macOS Terminal.app, Sublime Text, etc. are also available.\r\n\r\nPlease report any issues or feature requests at the GitHub repository above.","4":"Clean, vibrant, modern and pleasing light\/dark color schemes for terminal and gui Vim.\r\n\r\nConsistent cterm and gui colors, plus matching themes for plugins such as vim-airline, lightline or NERDTree. Provides harmonious colors and styles for all UI elements and syntax groups.\r\n\r\nScreenshot: https:\/\/github.com\/sonph\/onehalf\/blob\/master\/screenshots\/main.png\r\nMore screenshots: https:\/\/github.com\/sonph\/onehalf\/tree\/master\/screenshots\r\nMore information: https:\/\/github.com\/sonph\/onehalf\r\n\r\nMatching color schemes for other editors and terminals such as gnome-terminal, iTerm, macOS Terminal.app, Sublime Text, etc. are also available.\r\n\r\nPlease report any issues or feature requests at the GitHub repository above.","install_details":"1. Install with Vundle:\r\n\r\n    Plugin 'sonph\/onehalf', {'rtp': 'vim\/'}\r\n\r\nthen restart vim and execute \r\n\r\n    :PluginInstall\r\n\r\nor, manually copy the color scheme files from https:\/\/github.com\/sonph\/onehalf\/tree\/master\/vim into your local ~\/.vim\/colors and optionally ~\/.vim\/autoload (if you use vim-airline).\r\n\r\n2. Set the colorscheme in your ~\/.vimrc\r\n\r\n    syntax on\r\n    set t_Co=256\r\n    \" Use onehalfdark or onehalflight\r\n    colorscheme onehalfdark\r\n    \" If you are using vim-airline\r\n    let g:airline_theme='onehalfdark'","5":"1. Install with Vundle:\r\n\r\n    Plugin 'sonph\/onehalf', {'rtp': 'vim\/'}\r\n\r\nthen restart vim and execute \r\n\r\n    :PluginInstall\r\n\r\nor, manually copy the color scheme files from https:\/\/github.com\/sonph\/onehalf\/tree\/master\/vim into your local ~\/.vim\/colors and optionally ~\/.vim\/autoload (if you use vim-airline).\r\n\r\n2. Set the colorscheme in your ~\/.vimrc\r\n\r\n    syntax on\r\n    set t_Co=256\r\n    \" Use onehalfdark or onehalflight\r\n    colorscheme onehalfdark\r\n    \" If you are using vim-airline\r\n    let g:airline_theme='onehalfdark'","first_name":"Son","6":"Son","last_name":"Pham","7":"Pham","releases":[{"0":"5412","vim_version":"7.0","1":"7.0","script_version":"0.1.2","2":"0.1.2","version_comment":"Initial upload","3":"Initial upload","package":"onehalf.zip","4":"onehalf.zip","src_id":"24349","5":"24349","creation_date":"1467265507","6":"1467265507"}]},"5411":{"script_id":"5411","0":"5411","script_name":"Srcery","1":"Srcery","script_type":"color scheme","2":"color scheme","summary":"Vim color scheme","3":"Vim color scheme","description":"https:\/\/github.com\/srcery-colors\/srcery-vim\r\n\r\nColor scheme with clearly defined contrasting colors and a slightly earthy tone.\r\n\r\nScreenshots:\r\n-----------------\r\nhttps:\/\/raw.githubusercontent.com\/srcery-colors\/srcery-assets\/master\/vim\/py_js.png\r\nhttps:\/\/raw.githubusercontent.com\/srcery-colors\/srcery-assets\/master\/vim\/lisp.png\r\nhttps:\/\/raw.githubusercontent.com\/srcery-colors\/srcery-assets\/master\/vim\/viml_bash.png\r\nhttps:\/\/raw.githubusercontent.com\/srcery-colors\/srcery-assets\/master\/vim\/c_rust.png\r\n\r\nConfiguration, troubleshooting & more\r\n----------------\r\nRefer to the project readme https:\/\/github.com\/srcery-colors\/srcery-vim\r\nOr when installed :help srcery","4":"https:\/\/github.com\/srcery-colors\/srcery-vim\r\n\r\nColor scheme with clearly defined contrasting colors and a slightly earthy tone.\r\n\r\nScreenshots:\r\n-----------------\r\nhttps:\/\/raw.githubusercontent.com\/srcery-colors\/srcery-assets\/master\/vim\/py_js.png\r\nhttps:\/\/raw.githubusercontent.com\/srcery-colors\/srcery-assets\/master\/vim\/lisp.png\r\nhttps:\/\/raw.githubusercontent.com\/srcery-colors\/srcery-assets\/master\/vim\/viml_bash.png\r\nhttps:\/\/raw.githubusercontent.com\/srcery-colors\/srcery-assets\/master\/vim\/c_rust.png\r\n\r\nConfiguration, troubleshooting & more\r\n----------------\r\nRefer to the project readme https:\/\/github.com\/srcery-colors\/srcery-vim\r\nOr when installed :help srcery","install_details":"Requirements\r\n------------------\r\nGUI:\r\nYou don\u00e2\u0080\u0099t need to do anything for this colorscheme to work in GVim or MacVim.\r\n\r\nTUI:\r\nTo use Srcery in the terminal you need to change your terminal emulator\u00e2\u0080\u0099s so-called \u00e2\u0080\u009cASCII\u00e2\u0080\u009d colors. There's a list of terminal configurations in the srcery-terminal repository:\r\nhttps:\/\/github.com\/srcery-colors\/srcery-terminal\r\n\r\nInstallation:\r\n-----------------\r\nPlace srcery.vim in ~\/.vim\/colors\/ (on unix-like systems) or %userprofile%\\vimfiles\\colors\\ (on Windows), or use plugin manager and this repository: \r\nhttps:\/\/github.com\/srcery-colors\/srcery-vim\r\n\r\nUsage\r\n-----------\r\n:color srcery\r\n\r\nIf you like what you see and decide to make srcery your default colorscheme, add the relevant line to your vimrc:\r\n\r\ncolorscheme srcery\r\n","5":"Requirements\r\n------------------\r\nGUI:\r\nYou don\u00e2\u0080\u0099t need to do anything for this colorscheme to work in GVim or MacVim.\r\n\r\nTUI:\r\nTo use Srcery in the terminal you need to change your terminal emulator\u00e2\u0080\u0099s so-called \u00e2\u0080\u009cASCII\u00e2\u0080\u009d colors. There's a list of terminal configurations in the srcery-terminal repository:\r\nhttps:\/\/github.com\/srcery-colors\/srcery-terminal\r\n\r\nInstallation:\r\n-----------------\r\nPlace srcery.vim in ~\/.vim\/colors\/ (on unix-like systems) or %userprofile%\\vimfiles\\colors\\ (on Windows), or use plugin manager and this repository: \r\nhttps:\/\/github.com\/srcery-colors\/srcery-vim\r\n\r\nUsage\r\n-----------\r\n:color srcery\r\n\r\nIf you like what you see and decide to make srcery your default colorscheme, add the relevant line to your vimrc:\r\n\r\ncolorscheme srcery\r\n","first_name":"Daniel","6":"Daniel","last_name":"Berg","7":"Berg","releases":[{"0":"5411","vim_version":"7.0","1":"7.0","script_version":"v1.0.0","2":"v1.0.0","version_comment":"See release notes at: https:\/\/github.com\/srcery-colors\/srcery-vim\/releases\/tag\/v1.0.0","3":"See release notes at: https:\/\/github.com\/srcery-colors\/srcery-vim\/releases\/tag\/v1.0.0","package":"srcery-vim-1.0.0.zip","4":"srcery-vim-1.0.0.zip","src_id":"27617","5":"27617","creation_date":"1622159673","6":"1622159673"},{"0":"5411","vim_version":"7.0","1":"7.0","script_version":"v0.10.0","2":"v0.10.0","version_comment":"See release notes at: https:\/\/github.com\/srcery-colors\/srcery-vim\/releases\/tag\/v0.10.0","3":"See release notes at: https:\/\/github.com\/srcery-colors\/srcery-vim\/releases\/tag\/v0.10.0","package":"srcery-vim-0.10.0.zip","4":"srcery-vim-0.10.0.zip","src_id":"26111","5":"26111","creation_date":"1530832766","6":"1530832766"},{"0":"5411","vim_version":"7.0","1":"7.0","script_version":"v0.8.0","2":"v0.8.0","version_comment":"Includes Lightline support, fixes and some color renames","3":"Includes Lightline support, fixes and some color renames","package":"vim-srcery-0.8.0.zip","4":"vim-srcery-0.8.0.zip","src_id":"25548","5":"25548","creation_date":"1504446023","6":"1504446023"},{"0":"5411","vim_version":"7.0","1":"7.0","script_version":"0.7.0","2":"0.7.0","version_comment":"Improve contrast for various colors.\r\n","3":"Improve contrast for various colors.\r\n","package":"vim-srcery-0.7.0.zip","4":"vim-srcery-0.7.0.zip","src_id":"24476","5":"24476","creation_date":"1472326031","6":"1472326031"},{"0":"5411","vim_version":"7.0","1":"7.0","script_version":"0.6.2","2":"0.6.2","version_comment":"Fix for misnamed color constant","3":"Fix for misnamed color constant","package":"srcery-0.6.2.zip","4":"srcery-0.6.2.zip","src_id":"24445","5":"24445","creation_date":"1471284705","6":"1471284705"},{"0":"5411","vim_version":"7.0","1":"7.0","script_version":"0.6.1","2":"0.6.1","version_comment":"Fix white\/gray positions.","3":"Fix white\/gray positions.","package":"srcery_0.6.1.zip","4":"srcery_0.6.1.zip","src_id":"24355","5":"24355","creation_date":"1467458812","6":"1467458812"},{"0":"5411","vim_version":"7.0","1":"7.0","script_version":"0.6.0","2":"0.6.0","version_comment":"Initial upload","3":"Initial upload","package":"srcery_0.6.0.zip","4":"srcery_0.6.0.zip","src_id":"24347","5":"24347","creation_date":"1467035940","6":"1467035940"}]},"5409":{"script_id":"5409","0":"5409","script_name":"radical.vim","1":"radical.vim","script_type":"utility","2":"utility","summary":"Convert decimal, hex, octal, binary number representations","3":"Convert decimal, hex, octal, binary number representations","description":"Radical.vim is a plugin that converts between the number representations encountered when programming, that is in addition to decimal, hex, octal, and binary representation.\r\n\r\n\"gA\" shows the four representations of the number under the cursor.\r\n\"crd\", \"crx\", \"cro\", \"crb\" convert the number under the cursor to decimal, hex, octal, binary, respectively.\r\n\r\nThese mappings accept a count to force the base used to interpret the targeted number.\r\n\r\nThis plugin depends on the magnum.vim big integer library (vimscript #4877).\r\n\r\nSee also: https:\/\/github.com\/glts\/vim-radical\r\n","4":"Radical.vim is a plugin that converts between the number representations encountered when programming, that is in addition to decimal, hex, octal, and binary representation.\r\n\r\n\"gA\" shows the four representations of the number under the cursor.\r\n\"crd\", \"crx\", \"cro\", \"crb\" convert the number under the cursor to decimal, hex, octal, binary, respectively.\r\n\r\nThese mappings accept a count to force the base used to interpret the targeted number.\r\n\r\nThis plugin depends on the magnum.vim big integer library (vimscript #4877).\r\n\r\nSee also: https:\/\/github.com\/glts\/vim-radical\r\n","install_details":"Unzip the archive in your ~\/.vim directory. (On Windows, replace \"~\/.vim\" with \"%HOME%\\vimfiles\".)\r\n\r\nIf you use a plugin management system use the installation procedure appropriate to your setup. Keep in mind that radical.vim depends on magnum.vim, so be sure to install that as well if your plugin manager doesn't handle dependencies for you.\r\n\r\nFor example, with pathogen.vim the installation goes:\r\n\r\ngit clone https:\/\/github.com\/glts\/vim-magnum.git ~\/.vim\/bundle\/magnum\r\ngit clone https:\/\/github.com\/glts\/vim-radical.git ~\/.vim\/bundle\/radical\r\n","5":"Unzip the archive in your ~\/.vim directory. (On Windows, replace \"~\/.vim\" with \"%HOME%\\vimfiles\".)\r\n\r\nIf you use a plugin management system use the installation procedure appropriate to your setup. Keep in mind that radical.vim depends on magnum.vim, so be sure to install that as well if your plugin manager doesn't handle dependencies for you.\r\n\r\nFor example, with pathogen.vim the installation goes:\r\n\r\ngit clone https:\/\/github.com\/glts\/vim-magnum.git ~\/.vim\/bundle\/magnum\r\ngit clone https:\/\/github.com\/glts\/vim-radical.git ~\/.vim\/bundle\/radical\r\n","first_name":"David","6":"David","last_name":"B\u00c3\u00bcrgin","7":"B\u00c3\u00bcrgin","releases":[{"0":"5409","vim_version":"7.3","1":"7.3","script_version":"1.2.0","2":"1.2.0","version_comment":"Support customising coercion output","3":"Support customising coercion output","package":"radical-1.2.0.zip","4":"radical-1.2.0.zip","src_id":"26850","5":"26850","creation_date":"1574526956","6":"1574526956"},{"0":"5409","vim_version":"7.3","1":"7.3","script_version":"1.1.0","2":"1.1.0","version_comment":"Restore clipboard and registers after coerce\r\nSupport customising mappings","3":"Restore clipboard and registers after coerce\r\nSupport customising mappings","package":"radical-1.1.0.zip","4":"radical-1.1.0.zip","src_id":"26790","5":"26790","creation_date":"1571764110","6":"1571764110"},{"0":"5409","vim_version":"7.3","1":"7.3","script_version":"1.0.1","2":"1.0.1","version_comment":"Initial upload","3":"Initial upload","package":"radical-1.0.1.zip","4":"radical-1.0.1.zip","src_id":"24343","5":"24343","creation_date":"1466614685","6":"1466614685"}]},"5408":{"script_id":"5408","0":"5408","script_name":"vim-java-ununsed-imports","1":"vim-java-ununsed-imports","script_type":"utility","2":"utility","summary":"Allows showing and removing unused imports in a java file.","3":"Allows showing and removing unused imports in a java file.","description":"A simple vim plugin to show unused imports in a java file. Built for purely selfish reasons, open-sourced to help others.\r\n\r\nIf you like this project, please star https:\/\/github.com\/akhaku\/vim-java-unused-imports\/\r\n\r\nUsage\r\n\r\nIn normal mode:\r\n\r\n:UnusedImports \" highlight all unused imports\r\n:UnusedImportsReset \" clear the highlights\r\n:UnusedImportsRemove \" remove all unused imports","4":"A simple vim plugin to show unused imports in a java file. Built for purely selfish reasons, open-sourced to help others.\r\n\r\nIf you like this project, please star https:\/\/github.com\/akhaku\/vim-java-unused-imports\/\r\n\r\nUsage\r\n\r\nIn normal mode:\r\n\r\n:UnusedImports \" highlight all unused imports\r\n:UnusedImportsReset \" clear the highlights\r\n:UnusedImportsRemove \" remove all unused imports","install_details":"This plugin works with pathogen. Simply clone this repository to a subfolder within bundle\/. Alternatively, copy unused-imports.vim to plugin\/","5":"This plugin works with pathogen. Simply clone this repository to a subfolder within bundle\/. Alternatively, copy unused-imports.vim to plugin\/","first_name":"Ammar","6":"Ammar","last_name":"Khaku","7":"Khaku","releases":[{"0":"5408","vim_version":"7.0","1":"7.0","script_version":"1.2.0","2":"1.2.0","version_comment":"Default highlight to \"Error\" highlight and allow customization","3":"Default highlight to \"Error\" highlight and allow customization","package":"vim-java-unused-imports.zip","4":"vim-java-unused-imports.zip","src_id":"27291","5":"27291","creation_date":"1598371973","6":"1598371973"},{"0":"5408","vim_version":"7.0","1":"7.0","script_version":"1.1.1","2":"1.1.1","version_comment":"https:\/\/github.com\/akhaku\/vim-java-unused-imports\/issues\/19","3":"https:\/\/github.com\/akhaku\/vim-java-unused-imports\/issues\/19","package":"vim-java-unused-imports.zip","4":"vim-java-unused-imports.zip","src_id":"26389","5":"26389","creation_date":"1550339599","6":"1550339599"},{"0":"5408","vim_version":"7.0","1":"7.0","script_version":"1.1.0","2":"1.1.0","version_comment":"Added support for kotlin top level declaration and for static imports","3":"Added support for kotlin top level declaration and for static imports","package":"vim-java-unused-imports.zip","4":"vim-java-unused-imports.zip","src_id":"26246","5":"26246","creation_date":"1539578973","6":"1539578973"},{"0":"5408","vim_version":"7.0","1":"7.0","script_version":"1.0.0","2":"1.0.0","version_comment":"Initial upload","3":"Initial upload","package":"vim-java-unused-imports.zip","4":"vim-java-unused-imports.zip","src_id":"24338","5":"24338","creation_date":"1466297044","6":"1466297044"}]},"5407":{"script_id":"5407","0":"5407","script_name":"fluid.vim","1":"fluid.vim","script_type":"indent","2":"indent","summary":"Plugin for the Fluid Template Engine (TYPO3), indenting, and syntax plugin.","3":"Plugin for the Fluid Template Engine (TYPO3), indenting, and syntax plugin.","description":"vim-fluid\r\nVim plugin for the Fluid Template Engine offering indention and syntax highlighting for fluid code together with plain HTML and JavaScript and CSS code.\r\n\r\nFluid is the core template engine of TYPO3.\r\n\r\nUsage\r\n\r\nvim-fluid autodetects .fluid files but in most cases your files will end with .html, so you should set a modeline on top of your file. E.g.:\r\n\r\n","4":"vim-fluid\r\nVim plugin for the Fluid Template Engine offering indention and syntax highlighting for fluid code together with plain HTML and JavaScript and CSS code.\r\n\r\nFluid is the core template engine of TYPO3.\r\n\r\nUsage\r\n\r\nvim-fluid autodetects .fluid files but in most cases your files will end with .html, so you should set a modeline on top of your file. E.g.:\r\n\r\n","install_details":"","5":"","first_name":"Pim","6":"Pim","last_name":"Snel","7":"Snel","releases":[{"0":"5407","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"vim-fluid-master.zip","4":"vim-fluid-master.zip","src_id":"24335","5":"24335","creation_date":"1466194209","6":"1466194209"}]},"5406":{"script_id":"5406","0":"5406","script_name":"Impl Switcher","1":"Impl Switcher","script_type":"utility","2":"utility","summary":"Easily switch between impl and header files","3":"Easily switch between impl and header files","description":"Impl Switcher: switches between implementation and header files (for example, between .h and .cpp files).\r\nNote: only compatible with Linux systems that have the following programs available: dirname, find","4":"Impl Switcher: switches between implementation and header files (for example, between .h and .cpp files).\r\nNote: only compatible with Linux systems that have the following programs available: dirname, find","install_details":"Source from .vimrc.\r\nNote: only compatible with Linux systems that have the following programs available: dirname, find","5":"Source from .vimrc.\r\nNote: only compatible with Linux systems that have the following programs available: dirname, find","first_name":"Nicolas","6":"Nicolas","last_name":"Brailovsky","7":"Brailovsky","releases":[{"0":"5406","vim_version":"7.0","1":"7.0","script_version":"1","2":"1","version_comment":"Initial upload","3":"Initial upload","package":"impl_switcher.vim","4":"impl_switcher.vim","src_id":"24330","5":"24330","creation_date":"1465990275","6":"1465990275"}]},"5405":{"script_id":"5405","0":"5405","script_name":"BTN: Better tab new","1":"BTN: Better tab new","script_type":"utility","2":"utility","summary":"Adds a tab new command accepting file:lin_num as a parameter","3":"Adds a tab new command accepting file:lin_num as a parameter","description":"Better tab new: replaces the default tabnew command with a slightly smarter version, capable of understanding line numbers. This is very useful for programming, where filenames are usually expressed as \"fname:line number\". Even when grepping, the output format will usualy be \"path\/to\/file:42\". BTN won't reject these strings, it will instead open them and move the cursor to the appropiate line.\r\n","4":"Better tab new: replaces the default tabnew command with a slightly smarter version, capable of understanding line numbers. This is very useful for programming, where filenames are usually expressed as \"fname:line number\". Even when grepping, the output format will usualy be \"path\/to\/file:42\". BTN won't reject these strings, it will instead open them and move the cursor to the appropiate line.\r\n","install_details":"Just source from .vimrc: has no dependencies","5":"Just source from .vimrc: has no dependencies","first_name":"Nicolas","6":"Nicolas","last_name":"Brailovsky","7":"Brailovsky","releases":[{"0":"5405","vim_version":"7.0","1":"7.0","script_version":"1","2":"1","version_comment":"Initial upload","3":"Initial upload","package":"bettertabnew.vim","4":"bettertabnew.vim","src_id":"24329","5":"24329","creation_date":"1465989853","6":"1465989853"}]},"5404":{"script_id":"5404","0":"5404","script_name":"searchant.vim","1":"searchant.vim","script_type":"utility","2":"utility","summary":"searchant.vim is obsoleted by vim-searchhi","3":"searchant.vim is obsoleted by vim-searchhi","description":"SEARCHANT.VIM IS OBSOLETED BY VIM-SEARCHHI\r\n\r\nYou should use vim-searchhi (vimscript#5770) instead of searchant.vim. It fixes a bunch of longstanding bugs of searchant.vim and is overall more polished.","4":"SEARCHANT.VIM IS OBSOLETED BY VIM-SEARCHHI\r\n\r\nYou should use vim-searchhi (vimscript#5770) instead of searchant.vim. It fixes a bunch of longstanding bugs of searchant.vim and is overall more polished.","install_details":"","5":"","first_name":"Tim","6":"Tim","last_name":"Schumacher","7":"Schumacher","releases":[{"0":"5404","vim_version":"7.0","1":"7.0","script_version":"v1.1.0","2":"v1.1.0","version_comment":"Removed g:searchant_current setting\r\nAdded toggle functionality (thanks to andykais)","3":"Removed g:searchant_current setting\r\nAdded toggle functionality (thanks to andykais)","package":"vim-searchant.tar.gz","4":"vim-searchant.tar.gz","src_id":"26498","5":"26498","creation_date":"1558475411","6":"1558475411"},{"0":"5404","vim_version":"7.0","1":"7.0","script_version":"1.0.7","2":"1.0.7","version_comment":"Better compatibility with other enhanced search plugins\r\n(namely vim-anzu and vim-asterisk, thanks to qxxxb)","3":"Better compatibility with other enhanced search plugins\r\n(namely vim-anzu and vim-asterisk, thanks to qxxxb)","package":"vim-searchant.tar.gz","4":"vim-searchant.tar.gz","src_id":"26366","5":"26366","creation_date":"1548988190","6":"1548988190"},{"0":"5404","vim_version":"7.0","1":"7.0","script_version":"1.0.6","2":"1.0.6","version_comment":"Fixed folds not opening automatically","3":"Fixed folds not opening automatically","package":"vim-searchant.tar.gz","4":"vim-searchant.tar.gz","src_id":"24361","5":"24361","creation_date":"1467898175","6":"1467898175"},{"0":"5404","vim_version":"7.0","1":"7.0","script_version":"1.0.5","2":"1.0.5","version_comment":"Keep user-defined search mappings","3":"Keep user-defined search mappings","package":"vim-searchant.tar.gz","4":"vim-searchant.tar.gz","src_id":"24337","5":"24337","creation_date":"1466265433","6":"1466265433"},{"0":"5404","vim_version":"7.0","1":"7.0","script_version":"1.0.4","2":"1.0.4","version_comment":"Fixed handling of multiple windows\r\nFixed highlighting staying when searching for non existing pattern","3":"Fixed handling of multiple windows\r\nFixed highlighting staying when searching for non existing pattern","package":"vim-searchant.tar.gz","4":"vim-searchant.tar.gz","src_id":"24336","5":"24336","creation_date":"1466197498","6":"1466197498"},{"0":"5404","vim_version":"7.0","1":"7.0","script_version":"1.0.3","2":"1.0.3","version_comment":"Added support for the ignorecase option\r\nFixed highlighting for patterns using branches\r\nFixed highlighting for non-GUI (broke with GUI fix)","3":"Added support for the ignorecase option\r\nFixed highlighting for patterns using branches\r\nFixed highlighting for non-GUI (broke with GUI fix)","package":"vim-searchant.tar.gz","4":"vim-searchant.tar.gz","src_id":"24334","5":"24334","creation_date":"1466105158","6":"1466105158"},{"0":"5404","vim_version":"7.0","1":"7.0","script_version":"1.0.2","2":"1.0.2","version_comment":"Fixed current result highlighting for GUI","3":"Fixed current result highlighting for GUI","package":"vim-searchant.tar.gz","4":"vim-searchant.tar.gz","src_id":"24331","5":"24331","creation_date":"1465991194","6":"1465991194"},{"0":"5404","vim_version":"7.0","1":"7.0","script_version":"1.0.1","2":"1.0.1","version_comment":"Added requirements to readme","3":"Added requirements to readme","package":"vim-searchant.tar.gz","4":"vim-searchant.tar.gz","src_id":"24328","5":"24328","creation_date":"1465928549","6":"1465928549"},{"0":"5404","vim_version":"5.7","1":"5.7","script_version":"1.0.0","2":"1.0.0","version_comment":"Initial upload","3":"Initial upload","package":"vim-searchant.tar.gz","4":"vim-searchant.tar.gz","src_id":"24326","5":"24326","creation_date":"1465926921","6":"1465926921"}]},"5403":{"script_id":"5403","0":"5403","script_name":"vimport","1":"vimport","script_type":"utility","2":"utility","summary":"Allows you to easily add imports within java, groovy, grails","3":"Allows you to easily add imports within java, groovy, grails","description":"This is a plugin for vim that allows you to easily add imports within java, groovy, grails and kotlin projects.\r\n\r\nThe plugin has a few different mechanisms for finding a class's package. It can search the current working directory, search a text file that lists the full package and classname, or use a gradle build to determine the classpath and find the classes in jar files. Note that the gradle functionality requires VIM with python support.","4":"This is a plugin for vim that allows you to easily add imports within java, groovy, grails and kotlin projects.\r\n\r\nThe plugin has a few different mechanisms for finding a class's package. It can search the current working directory, search a text file that lists the full package and classname, or use a gradle build to determine the classpath and find the classes in jar files. Note that the gradle functionality requires VIM with python support.","install_details":"","5":"","first_name":"Shaun","6":"Shaun","last_name":"Jurgemeyer","7":"Jurgemeyer","releases":[{"0":"5403","vim_version":"7.3","1":"7.3","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"vimport-0.1.zip","4":"vimport-0.1.zip","src_id":"24316","5":"24316","creation_date":"1465431491","6":"1465431491"}]},"5402":{"script_id":"5402","0":"5402","script_name":"columnMove.vim","1":"columnMove.vim","script_type":"utility","2":"utility","summary":"move along vertical axis, to next\/previous character-blocks end\/start","3":"move along vertical axis, to next\/previous character-blocks end\/start","description":"(More readable readme on the repo)\r\nhttps:\/\/github.com\/romgrk\/columnMove.vim\r\n\r\n(Animated low-quality image)\r\nhttps:\/\/raw.githubusercontent.com\/romgrk\/columnMove.vim\/master\/demo.gif\r\n\r\nMove to the end\/start of vertical block.\r\n\r\nIf the cursor is on a whitespace and\/or virtual-column, moves to the next character in column that matches '\\S' (any non-whitespace).\r\nIf the cursor is on a non-whitespace character, moves to the last character in column that matches '\\S' before a '^$' (empty) match is found.\r\n\r\nConsider the following text, with cursor starting at [x]; repeatedly pressing ColumnMoveDown would take you to the marked positions.\r\n\r\n\" [.]..... ... ........ [.].... ... ...         [ ]\r\n\"                                                  \r\n\" 1.....................1......................1...\r\n\" ..........................................       \r\n\" 2.....................2......................2....\r\n\"                                                  \r\n\" 3..................\r\n\"       ..   ........   3....\r\n\" 4... ..    .... ..    ..................\r\n\" .... ..    .... ..    4...................\r\n\" .... ..                                                  \r\n\" .... ..                                                  \r\n\" .... ..                                                  \r\n\" .... ..... .... ..... 5.................\r\n\" 5... ..... .... ..... ...................  ....3...\r\n\"                       ....................  ....4...\r\n\"                       6..................\r\n\"EOF\r\n\r\nUsage: (default mappings)\r\n\r\nnmap gk    ColumnMoveUp\r\nnmap gj    ColumnMoveDown\r\nxmap  ColumnMoveUp\r\nxmap  ColumnMoveDown","4":"(More readable readme on the repo)\r\nhttps:\/\/github.com\/romgrk\/columnMove.vim\r\n\r\n(Animated low-quality image)\r\nhttps:\/\/raw.githubusercontent.com\/romgrk\/columnMove.vim\/master\/demo.gif\r\n\r\nMove to the end\/start of vertical block.\r\n\r\nIf the cursor is on a whitespace and\/or virtual-column, moves to the next character in column that matches '\\S' (any non-whitespace).\r\nIf the cursor is on a non-whitespace character, moves to the last character in column that matches '\\S' before a '^$' (empty) match is found.\r\n\r\nConsider the following text, with cursor starting at [x]; repeatedly pressing ColumnMoveDown would take you to the marked positions.\r\n\r\n\" [.]..... ... ........ [.].... ... ...         [ ]\r\n\"                                                  \r\n\" 1.....................1......................1...\r\n\" ..........................................       \r\n\" 2.....................2......................2....\r\n\"                                                  \r\n\" 3..................\r\n\"       ..   ........   3....\r\n\" 4... ..    .... ..    ..................\r\n\" .... ..    .... ..    4...................\r\n\" .... ..                                                  \r\n\" .... ..                                                  \r\n\" .... ..                                                  \r\n\" .... ..... .... ..... 5.................\r\n\" 5... ..... .... ..... ...................  ....3...\r\n\"                       ....................  ....4...\r\n\"                       6..................\r\n\"EOF\r\n\r\nUsage: (default mappings)\r\n\r\nnmap gk    ColumnMoveUp\r\nnmap gj    ColumnMoveDown\r\nxmap  ColumnMoveUp\r\nxmap  ColumnMoveDown","install_details":"Plug 'romgrk\/columnMove.vim'\r\n\r\nPlugin 'romgrk\/columnMove.vim'\r\n\r\nNeoBundle 'romgrk\/columnMove.vim'","5":"Plug 'romgrk\/columnMove.vim'\r\n\r\nPlugin 'romgrk\/columnMove.vim'\r\n\r\nNeoBundle 'romgrk\/columnMove.vim'","first_name":"Rom","6":"Rom","last_name":"Grk","7":"Grk","releases":[{"0":"5402","vim_version":"7.0","1":"7.0","script_version":"1.1","2":"1.1","version_comment":"fix v:true\/v:false usage","3":"fix v:true\/v:false usage","package":"columnMove.zip","4":"columnMove.zip","src_id":"24320","5":"24320","creation_date":"1465769838","6":"1465769838"},{"0":"5402","vim_version":"7.0","1":"7.0","script_version":"0.9","2":"0.9","version_comment":"Initial upload","3":"Initial upload","package":"columnMove.zip","4":"columnMove.zip","src_id":"24314","5":"24314","creation_date":"1465417957","6":"1465417957"}]},"5401":{"script_id":"5401","0":"5401","script_name":"vim-gencode-cpp","1":"vim-gencode-cpp","script_type":"ftplugin","2":"ftplugin","summary":"auto generate c++ function definition or declaration","3":"auto generate c++ function definition or declaration","description":"more infomation: https:\/\/github.com\/tenfyzhong\/vim-gencode-cpp\r\nFeatures\r\ngenerate the function definitions of class\r\ngenerate the static variable fefinitions of class\r\ngenerate the declaration of the function\r\n\r\nUsage\r\nrun GenDefinition in a function or variable declared\r\nrun GenDeclaration in a definition of a function\r\n\r\nConfiguration\r\ng:cpp_gencode_function_attach_statement\r\nA list of statement, this will be insert into function body before the function return.\r\n\r\nDependency\r\na.vim vimscript #31\r\n","4":"more infomation: https:\/\/github.com\/tenfyzhong\/vim-gencode-cpp\r\nFeatures\r\ngenerate the function definitions of class\r\ngenerate the static variable fefinitions of class\r\ngenerate the declaration of the function\r\n\r\nUsage\r\nrun GenDefinition in a function or variable declared\r\nrun GenDeclaration in a definition of a function\r\n\r\nConfiguration\r\ng:cpp_gencode_function_attach_statement\r\nA list of statement, this will be insert into function body before the function return.\r\n\r\nDependency\r\na.vim vimscript #31\r\n","install_details":"windows users change all occurrencws of ~\/.vim to ~\\vimfiles.\r\n\r\nYou can choose you preferred bundle manager\r\nRun the following commans in a terminal:\r\nmkdir -p ~\/.vim\/bundle  \r\ncd ~\/.vim\/bundle  \r\ngit clone https:\/\/github.com\/tenfyzhong\/vim-gencode-cpp.git  \r\necho 'set runtimepath^=~\/.vim\/bundle\/vim-gencode-cpp' >> ~\/.vimrc  ","5":"windows users change all occurrencws of ~\/.vim to ~\\vimfiles.\r\n\r\nYou can choose you preferred bundle manager\r\nRun the following commans in a terminal:\r\nmkdir -p ~\/.vim\/bundle  \r\ncd ~\/.vim\/bundle  \r\ngit clone https:\/\/github.com\/tenfyzhong\/vim-gencode-cpp.git  \r\necho 'set runtimepath^=~\/.vim\/bundle\/vim-gencode-cpp' >> ~\/.vimrc  ","first_name":"tenfy","6":"tenfy","last_name":"zhong","7":"zhong","releases":[{"0":"5401","vim_version":"7.4","1":"7.4","script_version":"1.3.2","2":"1.3.2","version_comment":"add test","3":"add test","package":"vim-gencode-cpp-1.3.2.tar.gz","4":"vim-gencode-cpp-1.3.2.tar.gz","src_id":"24325","5":"24325","creation_date":"1465908747","6":"1465908747"},{"0":"5401","vim_version":"7.4","1":"7.4","script_version":"1.3.0","2":"1.3.0","version_comment":"support namespace\r\ngenerate declaration support namespace\r\ngenerate definition support template\r\n","3":"support namespace\r\ngenerate declaration support namespace\r\ngenerate definition support template\r\n","package":"vim-gencode-cpp-1.3.0.tar.gz","4":"vim-gencode-cpp-1.3.0.tar.gz","src_id":"24309","5":"24309","creation_date":"1465270114","6":"1465270114"}]},"5400":{"script_id":"5400","0":"5400","script_name":"Cheat40","1":"Cheat40","script_type":"utility","2":"utility","summary":"A cheat sheet that makes sense, inside Vim!","3":"A cheat sheet that makes sense, inside Vim!","description":"Source code on GitHub: https:\/\/github.com\/lifepillar\/vim-cheat40.git\r\n\r\nCheat40 is a foldable extensible 40-column cheat sheet that you may open in Vim by pressing ?. Mappings and commands are organized like the menus of a GUI app: there is a File section, an Edit section, a View section, and so on. For each item the description comes first, because one typically wants to find how to execute a task, not what the meaning of a key sequence is (there is Vim's help for that). Syntax coloring and the use of conceal keep the cheat sheet clutter-free and easy to read.","4":"Source code on GitHub: https:\/\/github.com\/lifepillar\/vim-cheat40.git\r\n\r\nCheat40 is a foldable extensible 40-column cheat sheet that you may open in Vim by pressing ?. Mappings and commands are organized like the menus of a GUI app: there is a File section, an Edit section, a View section, and so on. For each item the description comes first, because one typically wants to find how to execute a task, not what the meaning of a key sequence is (there is Vim's help for that). Syntax coloring and the use of conceal keep the cheat sheet clutter-free and easy to read.","install_details":"","5":"","first_name":"","6":"","last_name":"Lifepillar","7":"Lifepillar","releases":[{"0":"5400","vim_version":"7.0","1":"7.0","script_version":"0.4","2":"0.4","version_comment":"Some changes to the mappings. Allow `gf` to jump to the files mentioned in About section. Hide cheat sheet instead of unloading it. Fix size of Cheat40's window. Check for uniqueness of mapping.","3":"Some changes to the mappings. Allow `gf` to jump to the files mentioned in About section. Hide cheat sheet instead of unloading it. Fix size of Cheat40's window. Check for uniqueness of mapping.","package":"vim-cheat40-0.4.tar.gz","4":"vim-cheat40-0.4.tar.gz","src_id":"25791","5":"25791","creation_date":"1516554006","6":"1516554006"},{"0":"5400","vim_version":"7.0","1":"7.0","script_version":"0.3","2":"0.3","version_comment":"A few new\/updated mappings. Process runtimepath in reverse order.","3":"A few new\/updated mappings. Process runtimepath in reverse order.","package":"vim-cheat40-0.3.tar.gz","4":"vim-cheat40-0.3.tar.gz","src_id":"24391","5":"24391","creation_date":"1469357030","6":"1469357030"},{"0":"5400","vim_version":"7.0","1":"7.0","script_version":"0.2","2":"0.2","version_comment":"Improve syntax highlighting. Add variable to disable default cheat sheet. Several bug fixes.","3":"Improve syntax highlighting. Add variable to disable default cheat sheet. Several bug fixes.","package":"vim-cheat40-0.2.tar.gz","4":"vim-cheat40-0.2.tar.gz","src_id":"24311","5":"24311","creation_date":"1465330586","6":"1465330586"},{"0":"5400","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"vim-cheat40-0.1.tar.gz","4":"vim-cheat40-0.1.tar.gz","src_id":"24305","5":"24305","creation_date":"1465071880","6":"1465071880"}]},"5399":{"script_id":"5399","0":"5399","script_name":"ember_tools.vim","1":"ember_tools.vim","script_type":"utility","2":"utility","summary":"Tools for working with ember.js projects","3":"Tools for working with ember.js projects","description":"Github repo: https:\/\/github.com\/AndrewRadev\/ember_tools.vim\r\n\r\nThis plugin contains various tools to work with ember.js projects. After installing it, just editing files in an ember.js project should be enough to activate them. It's similar to (and inspired by)  rails.vim (vimscript #1567).\r\n\r\nThe tools work both for javascript and coffeescript, and they support both the handlebars and emblem templating languages. For now, there are two tools available:\r\n\r\n- An enhanced `gf` family of mappings (a custom include expression)\r\n- An :Extract command that lets you extract some template code into a component.\r\n- An :Unpack command that unpacks imported modules into local variables and an :Inline command that does the opposite\r\n\r\nRead the documentation for more details.\r\n\r\nIt's recommended to also use the vim-projectionist (vimscript #4989) plugin for easier navigation through the project. Here's a sample json file you might use with it: https:\/\/gist.github.com\/AndrewRadev\/3524ee46bca8ab349329. It sets up the major file types you might want to navigate to, and it connects routes, controllers, and templates, so that the :A command jumps from route to controller, to template, and then back to the route.\r\n","4":"Github repo: https:\/\/github.com\/AndrewRadev\/ember_tools.vim\r\n\r\nThis plugin contains various tools to work with ember.js projects. After installing it, just editing files in an ember.js project should be enough to activate them. It's similar to (and inspired by)  rails.vim (vimscript #1567).\r\n\r\nThe tools work both for javascript and coffeescript, and they support both the handlebars and emblem templating languages. For now, there are two tools available:\r\n\r\n- An enhanced `gf` family of mappings (a custom include expression)\r\n- An :Extract command that lets you extract some template code into a component.\r\n- An :Unpack command that unpacks imported modules into local variables and an :Inline command that does the opposite\r\n\r\nRead the documentation for more details.\r\n\r\nIt's recommended to also use the vim-projectionist (vimscript #4989) plugin for easier navigation through the project. Here's a sample json file you might use with it: https:\/\/gist.github.com\/AndrewRadev\/3524ee46bca8ab349329. It sets up the major file types you might want to navigate to, and it connects routes, controllers, and templates, so that the :A command jumps from route to controller, to template, and then back to the route.\r\n","install_details":"There are several ways to install the plugin. The recommended one is by using Tim Pope's pathogen (vimscript #2332). In that case, you can clone the plugin's git repository like so:\r\n\r\n    git clone git:\/\/github.com\/AndrewRadev\/ember_tools.vim.git ~\/.vim\/bundle\/ember_tools\r\n\r\nIf your vim configuration is under git version control, you could also set up the repository as a submodule, which would allow you to update more easily. The command is (provided you're in ~\/.vim):\r\n\r\n    git submodule add git:\/\/github.com\/AndrewRadev\/ember_tools.vim.git bundle\/ember_tools\r\n\r\nAnother way is to simply copy all the essential directories inside the ~\/.vim directory: autoload, doc, plugin.\r\n","5":"There are several ways to install the plugin. The recommended one is by using Tim Pope's pathogen (vimscript #2332). In that case, you can clone the plugin's git repository like so:\r\n\r\n    git clone git:\/\/github.com\/AndrewRadev\/ember_tools.vim.git ~\/.vim\/bundle\/ember_tools\r\n\r\nIf your vim configuration is under git version control, you could also set up the repository as a submodule, which would allow you to update more easily. The command is (provided you're in ~\/.vim):\r\n\r\n    git submodule add git:\/\/github.com\/AndrewRadev\/ember_tools.vim.git bundle\/ember_tools\r\n\r\nAnother way is to simply copy all the essential directories inside the ~\/.vim directory: autoload, doc, plugin.\r\n","first_name":"Andrew","6":"Andrew","last_name":"Radev","7":"Radev","releases":[{"0":"5399","vim_version":"7.0","1":"7.0","script_version":"0.1.0","2":"0.1.0","version_comment":"- :Unpack and :Inline commands\r\n- More patterns supported by gf\r\n- Pod structure (hopefully) supported by gf\r\n- Various bugfxes and minor improvements","3":"- :Unpack and :Inline commands\r\n- More patterns supported by gf\r\n- Pod structure (hopefully) supported by gf\r\n- Various bugfxes and minor improvements","package":"ember_tools.zip","4":"ember_tools.zip","src_id":"24463","5":"24463","creation_date":"1471965504","6":"1471965504"},{"0":"5399","vim_version":"7.3","1":"7.3","script_version":"0.0.1","2":"0.0.1","version_comment":"Initial upload","3":"Initial upload","package":"ember_tools.zip","4":"ember_tools.zip","src_id":"24302","5":"24302","creation_date":"1464934462","6":"1464934462"}]},"5398":{"script_id":"5398","0":"5398","script_name":"verilog_emacsauto.vim","1":"verilog_emacsauto.vim","script_type":"ftplugin","2":"ftplugin","summary":"Minor update based on vimscript #1875","3":"Minor update based on vimscript #1875","description":"This is a update based on the original verilog_emacsauto.vim: vimscript #1875\r\nFeatures with this update:\r\n    keep alternate file untouched\r\n    better message display for emacs\r\n    keep cursor untouched","4":"This is a update based on the original verilog_emacsauto.vim: vimscript #1875\r\nFeatures with this update:\r\n    keep alternate file untouched\r\n    better message display for emacs\r\n    keep cursor untouched","install_details":"Please refer to vimscript #1875 for more details.","5":"Please refer to vimscript #1875 for more details.","first_name":"Terrence","6":"Terrence","last_name":"Sun","7":"Sun","releases":[{"0":"5398","vim_version":"7.0","1":"7.0","script_version":"0.5","2":"0.5","version_comment":"Initial upload","3":"Initial upload","package":"verilog_emacsauto.vim","4":"verilog_emacsauto.vim","src_id":"24299","5":"24299","creation_date":"1464838753","6":"1464838753"}]},"5397":{"script_id":"5397","0":"5397","script_name":"Closing Brackets","1":"Closing Brackets","script_type":"utility","2":"utility","summary":"A dead-simple Vim plugin to automatically insert closing brackets","3":"A dead-simple Vim plugin to automatically insert closing brackets","description":"https:\/\/github.com\/tpenguinltg\/vim-closing-brackets\r\n\r\nA dead-simple plugin to automatically insert the closing bracket\/brace\/parenthesis based on vimtip #630.\r\n\r\nThis plugin was written because the other solutions interfered with SCIM and were more complex than I needed.\r\n\r\nMappings (\\'(\\' can be replaced with \\'[\\' or \\'{\\'. \\'|\\' is the cursor position):\r\n( -> (|)\r\n() -> (|)\r\n( ->\r\n( -> (|\r\n( -> (|\r\n) (when cursor is before a \\')\\' )-> )|\r\n) -> ))|\r\n) -> )|\r\n","4":"https:\/\/github.com\/tpenguinltg\/vim-closing-brackets\r\n\r\nA dead-simple plugin to automatically insert the closing bracket\/brace\/parenthesis based on vimtip #630.\r\n\r\nThis plugin was written because the other solutions interfered with SCIM and were more complex than I needed.\r\n\r\nMappings (\\'(\\' can be replaced with \\'[\\' or \\'{\\'. \\'|\\' is the cursor position):\r\n( -> (|)\r\n() -> (|)\r\n( ->\r\n( -> (|\r\n( -> (|\r\n) (when cursor is before a \\')\\' )-> )|\r\n) -> ))|\r\n) -> )|\r\n","install_details":"Copy the plugin file to your plugins folder.","5":"Copy the plugin file to your plugins folder.","first_name":"tPenguinLTG","6":"tPenguinLTG","last_name":" ","7":" ","releases":[{"0":"5397","vim_version":"7.0","1":"7.0","script_version":"1.0.0","2":"1.0.0","version_comment":"Initial upload","3":"Initial upload","package":"vim-closing-brackets.vim","4":"vim-closing-brackets.vim","src_id":"24297","5":"24297","creation_date":"1464786420","6":"1464786420"}]},"5396":{"script_id":"5396","0":"5396","script_name":"ranger.vim","1":"ranger.vim","script_type":"ftplugin","2":"ftplugin","summary":"Ranger integration in vim and neovim","3":"Ranger integration in vim and neovim","description":"https:\/\/github.com\/francoiscabrol\/ranger.vim\r\n\r\nThe default shortcut for opening Ranger is f (\\f by default) To disable the default key mapping, add this line in your .vimrc or init.vim: let g:ranger_map_keys = 0\r\n\r\nthen you can add a new mapping with this line: map f :Ranger.\r\n\r\nThe command for opening Ranger in the current file's directory is :Ranger. Vim will open the selected file in the current window. To open the selected file in a new tab instead use :RangerNewTab.\r\n\r\nFor opening Ranger in the current workspace, run :RangerWorkingDirectory. Vim will open the selected file in the current window. :RangerWorkingDirectoryNewTab will open the selected file in a new tab instead.\r\n\r\nIf you want to see vim opening ranger when you open a directory (ex: nvim .\/dir), please add this in your .(n)vimrc:\r\nlet g:NERDTreeHijackNetrw = 0 \/\/ add this line if you use NERDTree\r\nlet g:ranger_replace_netrw = 1 \/\/ open ranger when vim open a directory","4":"https:\/\/github.com\/francoiscabrol\/ranger.vim\r\n\r\nThe default shortcut for opening Ranger is f (\\f by default) To disable the default key mapping, add this line in your .vimrc or init.vim: let g:ranger_map_keys = 0\r\n\r\nthen you can add a new mapping with this line: map f :Ranger.\r\n\r\nThe command for opening Ranger in the current file's directory is :Ranger. Vim will open the selected file in the current window. To open the selected file in a new tab instead use :RangerNewTab.\r\n\r\nFor opening Ranger in the current workspace, run :RangerWorkingDirectory. Vim will open the selected file in the current window. :RangerWorkingDirectoryNewTab will open the selected file in a new tab instead.\r\n\r\nIf you want to see vim opening ranger when you open a directory (ex: nvim .\/dir), please add this in your .(n)vimrc:\r\nlet g:NERDTreeHijackNetrw = 0 \/\/ add this line if you use NERDTree\r\nlet g:ranger_replace_netrw = 1 \/\/ open ranger when vim open a directory","install_details":"Install it with your favorite plugin manager. Example with vim-plug:\r\n\r\n    Plug 'francoiscabrol\/ranger.vim'\r\n\r\nIf you use neovim, you have to add the dependency to the plugin bclose.vim:\r\n\r\n    Plug 'rbgrouleff\/bclose.vim'","5":"Install it with your favorite plugin manager. Example with vim-plug:\r\n\r\n    Plug 'francoiscabrol\/ranger.vim'\r\n\r\nIf you use neovim, you have to add the dependency to the plugin bclose.vim:\r\n\r\n    Plug 'rbgrouleff\/bclose.vim'","first_name":"francois","6":"francois","last_name":"cabrol","7":"cabrol","releases":[{"0":"5396","vim_version":"7.0","1":"7.0","script_version":"2.0","2":"2.0","version_comment":"get the last version at https:\/\/github.com\/francoiscabrol\/ranger.vim","3":"get the last version at https:\/\/github.com\/francoiscabrol\/ranger.vim","package":"ranger.vim-2.0.zip","4":"ranger.vim-2.0.zip","src_id":"25630","5":"25630","creation_date":"1509493356","6":"1509493356"},{"0":"5396","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"ranger.vim-1.0.zip","4":"ranger.vim-1.0.zip","src_id":"24294","5":"24294","creation_date":"1464731805","6":"1464731805"}]},"5395":{"script_id":"5395","0":"5395","script_name":"tabulous","1":"tabulous","script_type":"ftplugin","2":"ftplugin","summary":"Lightweight Vim plugin to enhance the tabline including numbered tab page labels","3":"Lightweight Vim plugin to enhance the tabline including numbered tab page labels","description":"Lightweight Vim plugin to enhance the tabline including numbered tab page labels; it's written entirely in Vim script.\r\n\r\nThe latest version may be found at: https:\/\/github.com\/webdevel\/tabulous\r\n\r\nFeatures\r\n\r\nShows the tab page number on every tab label for quickly navigating to the desired tab gt.\r\nRename the current tab page label.\r\nTabs display an indicator when a buffer has been modified and not saved.\r\nDynamically updates the filename of the currently focused window in the tab page.\r\nEliminates inefficient use of string concatenation operator by using printf where possible.\r\nDoes not show filename extensions to preserve the amount of tab label space.\r\nPerforms runtime calculation of maximum tab label length and truncates accordingly (Dynamic resizing of tab labels).\r\nOptions are configurable from .vimrc.\r\n\r\nPlanned Features\r\nEnhancement of tab label truncation algorithm\r\nToggle tab page numbers on and off by keyboard shortcut\r\nToggle tab label filename extensions on and off by keyboard shortcut\r\nToggle tab label truncation on and off by keyboard shortcut\r\n> In progress: keyboard shortcuts and enhancement of tab label truncation algorithm.","4":"Lightweight Vim plugin to enhance the tabline including numbered tab page labels; it's written entirely in Vim script.\r\n\r\nThe latest version may be found at: https:\/\/github.com\/webdevel\/tabulous\r\n\r\nFeatures\r\n\r\nShows the tab page number on every tab label for quickly navigating to the desired tab gt.\r\nRename the current tab page label.\r\nTabs display an indicator when a buffer has been modified and not saved.\r\nDynamically updates the filename of the currently focused window in the tab page.\r\nEliminates inefficient use of string concatenation operator by using printf where possible.\r\nDoes not show filename extensions to preserve the amount of tab label space.\r\nPerforms runtime calculation of maximum tab label length and truncates accordingly (Dynamic resizing of tab labels).\r\nOptions are configurable from .vimrc.\r\n\r\nPlanned Features\r\nEnhancement of tab label truncation algorithm\r\nToggle tab page numbers on and off by keyboard shortcut\r\nToggle tab label filename extensions on and off by keyboard shortcut\r\nToggle tab label truncation on and off by keyboard shortcut\r\n> In progress: keyboard shortcuts and enhancement of tab label truncation algorithm.","install_details":"You may choose your preferred method of installation from using your .vimrc, Pathogen, Vundle, NeoBundle, VimPlug or some other similar plugin manager.\r\n\r\n > Windows users, change all following occurrences of ~\/.vim to ~\\vimfiles.\r\n\r\nVimrc Tabulous Installation\r\n\r\nRun the following commands in a terminal:\r\n\r\nmkdir -p ~\/.vim\/bundle\r\ncd ~\/.vim\/bundle\r\ngit clone https:\/\/github.com\/webdevel\/tabulous.git\r\necho 'set runtimepath^=~\/.vim\/bundle\/tabulous' >> ~\/.vimrc\r\nRestart Vim.\r\n\r\nPathogen Tabulous Installation\r\n\r\nRun the following commands in a terminal:\r\n\r\nmkdir -p ~\/.vim\/bundle\r\ncd ~\/.vim\/bundle\r\ngit clone https:\/\/github.com\/webdevel\/tabulous.git\r\nRestart Vim.\r\n\r\nVundle Tabulous Installation\r\n\r\nIf your Vundle version is less than 0.10.2, change Plugin to Bundle.\r\nEnter this in your .vimrc:\r\n\r\nPlugin 'webdevel\/tabulous'\r\nThen enter the following command-lines in Vim:\r\n\r\n:source %\r\n:PluginInstall","5":"You may choose your preferred method of installation from using your .vimrc, Pathogen, Vundle, NeoBundle, VimPlug or some other similar plugin manager.\r\n\r\n > Windows users, change all following occurrences of ~\/.vim to ~\\vimfiles.\r\n\r\nVimrc Tabulous Installation\r\n\r\nRun the following commands in a terminal:\r\n\r\nmkdir -p ~\/.vim\/bundle\r\ncd ~\/.vim\/bundle\r\ngit clone https:\/\/github.com\/webdevel\/tabulous.git\r\necho 'set runtimepath^=~\/.vim\/bundle\/tabulous' >> ~\/.vimrc\r\nRestart Vim.\r\n\r\nPathogen Tabulous Installation\r\n\r\nRun the following commands in a terminal:\r\n\r\nmkdir -p ~\/.vim\/bundle\r\ncd ~\/.vim\/bundle\r\ngit clone https:\/\/github.com\/webdevel\/tabulous.git\r\nRestart Vim.\r\n\r\nVundle Tabulous Installation\r\n\r\nIf your Vundle version is less than 0.10.2, change Plugin to Bundle.\r\nEnter this in your .vimrc:\r\n\r\nPlugin 'webdevel\/tabulous'\r\nThen enter the following command-lines in Vim:\r\n\r\n:source %\r\n:PluginInstall","first_name":"Steven","6":"Steven","last_name":"Garcia","7":"Garcia","releases":[{"0":"5395","vim_version":"7.0","1":"7.0","script_version":"0.5.0","2":"0.5.0","version_comment":"Added new feature to rename current tab page label\r\nUpdated documentation for new feature","3":"Added new feature to rename current tab page label\r\nUpdated documentation for new feature","package":"tabulous-0.5.0.zip","4":"tabulous-0.5.0.zip","src_id":"24306","5":"24306","creation_date":"1465095424","6":"1465095424"},{"0":"5395","vim_version":"7.0","1":"7.0","script_version":"0.3.0","2":"0.3.0","version_comment":"Added plugin help text tabulous.txt\r\nUpdated readme","3":"Added plugin help text tabulous.txt\r\nUpdated readme","package":"tabulous-0.3.0.zip","4":"tabulous-0.3.0.zip","src_id":"24301","5":"24301","creation_date":"1464924855","6":"1464924855"},{"0":"5395","vim_version":"7.0","1":"7.0","script_version":"0.2.0","2":"0.2.0","version_comment":"Added dynamic tab label resizing.\r\nAdded more options configurable from .vimrc.","3":"Added dynamic tab label resizing.\r\nAdded more options configurable from .vimrc.","package":"tabulous-0.2.0.zip","4":"tabulous-0.2.0.zip","src_id":"24298","5":"24298","creation_date":"1464797395","6":"1464797395"},{"0":"5395","vim_version":"7.0","1":"7.0","script_version":"0.1.0","2":"0.1.0","version_comment":"Initial upload","3":"Initial upload","package":"tabulous-0.1.0.zip","4":"tabulous-0.1.0.zip","src_id":"24293","5":"24293","creation_date":"1464658829","6":"1464658829"}]},"5394":{"script_id":"5394","0":"5394","script_name":"twig.vim","1":"twig.vim","script_type":"syntax","2":"syntax","summary":"Twig syntax highlighting, indentation and neocomplete snippets","3":"Twig syntax highlighting, indentation and neocomplete snippets","description":"Twig syntax highlighting, indentation and neocomplete snippets\r\n\r\nCheck repository https:\/\/github.com\/nelsyeung\/twig.vim for more details.","4":"Twig syntax highlighting, indentation and neocomplete snippets\r\n\r\nCheck repository https:\/\/github.com\/nelsyeung\/twig.vim for more details.","install_details":"","5":"","first_name":"Nelson","6":"Nelson","last_name":"Yeung","7":"Yeung","releases":[{"0":"5394","vim_version":"7.4","1":"7.4","script_version":"1.0.0","2":"1.0.0","version_comment":"Initial upload","3":"Initial upload","package":"twig.vim.tar.gz","4":"twig.vim.tar.gz","src_id":"24290","5":"24290","creation_date":"1464485361","6":"1464485361"}]},"5393":{"script_id":"5393","0":"5393","script_name":"vim eslint","1":"vim eslint","script_type":"syntax","2":"syntax","summary":"eslint","3":"eslint","description":"eslint plugin for vim","4":"eslint plugin for vim","install_details":"https:\/\/github.com\/sfger\/vim-eslint.git","5":"https:\/\/github.com\/sfger\/vim-eslint.git","first_name":"Water","6":"Water","last_name":"x","7":"x","releases":[{"0":"5393","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"vim-eslint.rar","4":"vim-eslint.rar","src_id":"24288","5":"24288","creation_date":"1464403193","6":"1464403193"}]},"5392":{"script_id":"5392","0":"5392","script_name":"SIDECAR Assembly Syntax Highlighting Fil","1":"SIDECAR Assembly Syntax Highlighting Fil","script_type":"syntax","2":"syntax","summary":"SIDECAR Assembly Syntax Highlighting File","3":"SIDECAR Assembly Syntax Highlighting File","description":"This is a syntax highlighting file for SIDECAR Assembly, used on the Teleydyne HxRG imaging devices.","4":"This is a syntax highlighting file for SIDECAR Assembly, used on the Teleydyne HxRG imaging devices.","install_details":"Copy file to your ~\/.vim\/syntax folder, and then type \"filetype=sidecar\" to see how it works for you.  If it works well, add lines to .vimrc to autoload for .asm files.","5":"Copy file to your ~\/.vim\/syntax folder, and then type \"filetype=sidecar\" to see how it works for you.  If it works well, add lines to .vimrc to autoload for .asm files.","first_name":"Scott","6":"Scott","last_name":"Miller","7":"Miller","releases":[{"0":"5392","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"sidecar.vim","4":"sidecar.vim","src_id":"24279","5":"24279","creation_date":"1464358724","6":"1464358724"}]},"5391":{"script_id":"5391","0":"5391","script_name":"easy-execute","1":"easy-execute","script_type":"utility","2":"utility","summary":"Execute files easy in unix","3":"Execute files easy in unix","description":"Overview:\r\n\r\nOften, there is a single action that is performed often for a given filetype. \r\nFor example, for source code file unit tests are performed if present.\r\n\r\nUsage:\r\n\r\nExecute the file related to the current buffer:\r\ncall g:Exec_file()\r\n\r\nAn example of .vimrc:\r\nnnore  :w:call Exec_file()\r\n\r\ng:easy_execution_pattern associates the file path to pattern handlers (funcref). \r\nSee the examples in the source code. Notice that a handler should return 1 if \r\nthe file was executed and 0 otherwise (0 means the filetype was not recognized).  \r\nThis allows setting handlers for uncertain cases such as shell scripts (which may \r\nor may not have .sh in the end). The handler takes the path of the file and the shell \r\nescaped name as a parameter. \r\n\r\nAs the working directory is also used to determine the file type (e.g. for\r\nPerl modules, we check if Makefile.PL is found). Consequently, changing the\r\nworking directory using e.g. vim-rooter prior to calling g:Exec_file is\r\nadvisable (by adding commands to the key map).\r\n\r\nThe utility function g:Easy_system may be used for forking processes.\r\nUsually the handlers should return 0 in the case of failed execution as \r\nthe filetype was recognized. g:Easy_system does the error handling by \r\nchecking the error code and showing the process output to the user in a \r\nbuffer associated with a temporary file.","4":"Overview:\r\n\r\nOften, there is a single action that is performed often for a given filetype. \r\nFor example, for source code file unit tests are performed if present.\r\n\r\nUsage:\r\n\r\nExecute the file related to the current buffer:\r\ncall g:Exec_file()\r\n\r\nAn example of .vimrc:\r\nnnore  :w:call Exec_file()\r\n\r\ng:easy_execution_pattern associates the file path to pattern handlers (funcref). \r\nSee the examples in the source code. Notice that a handler should return 1 if \r\nthe file was executed and 0 otherwise (0 means the filetype was not recognized).  \r\nThis allows setting handlers for uncertain cases such as shell scripts (which may \r\nor may not have .sh in the end). The handler takes the path of the file and the shell \r\nescaped name as a parameter. \r\n\r\nAs the working directory is also used to determine the file type (e.g. for\r\nPerl modules, we check if Makefile.PL is found). Consequently, changing the\r\nworking directory using e.g. vim-rooter prior to calling g:Exec_file is\r\nadvisable (by adding commands to the key map).\r\n\r\nThe utility function g:Easy_system may be used for forking processes.\r\nUsually the handlers should return 0 in the case of failed execution as \r\nthe filetype was recognized. g:Easy_system does the error handling by \r\nchecking the error code and showing the process output to the user in a \r\nbuffer associated with a temporary file.","install_details":"Installation: Copy easy-execute.vim to your plugin directory.","5":"Installation: Copy easy-execute.vim to your plugin directory.","first_name":"","6":"","last_name":"","7":"","releases":[{"0":"5391","vim_version":"7.0","1":"7.0","script_version":"0.2","2":"0.2","version_comment":"Complete rewrite.","3":"Complete rewrite.","package":"easy-execute.vim","4":"easy-execute.vim","src_id":"25460","5":"25460","creation_date":"1501505797","6":"1501505797"}]},"5390":{"script_id":"5390","0":"5390","script_name":"tortus.vim","1":"tortus.vim","script_type":"color scheme","2":"color scheme","summary":"Dark (grey and yellow on black) color scheme based on on torte.vim","3":"Dark (grey and yellow on black) color scheme based on on torte.vim","description":"Now available on github: https:\/\/github.com\/KnoP-01\/tortus\r\n\r\nDark (grey and yellow on black) color scheme based on on torte.vim\r\n([vimscript #111][1]), motus.vim ([vimscript #1393][2]) and\r\nmetacosm.vim ([vimscript #985][3]).\r\n\r\nDesigned for gvim to be used with vim plugins for KRL ([vimscript #5344][4])\r\nand Rapid ([vimscript #5348][5]). Should work fine on console as well.\r\nIt started as a copy of torte.vim and drifted away more and more.\r\n\r\ntortus.vim gets quiet colorful.\r\nIf it's too colorful for you try tortusless.vim.\r\n\r\nSee github for screenshots.\r\n\r\nCredits goes to Thorsten Maerz, Sergei Matusevich and Robert Melton.\r\n\r\n## install details\r\n","4":"Now available on github: https:\/\/github.com\/KnoP-01\/tortus\r\n\r\nDark (grey and yellow on black) color scheme based on on torte.vim\r\n([vimscript #111][1]), motus.vim ([vimscript #1393][2]) and\r\nmetacosm.vim ([vimscript #985][3]).\r\n\r\nDesigned for gvim to be used with vim plugins for KRL ([vimscript #5344][4])\r\nand Rapid ([vimscript #5348][5]). Should work fine on console as well.\r\nIt started as a copy of torte.vim and drifted away more and more.\r\n\r\ntortus.vim gets quiet colorful.\r\nIf it's too colorful for you try tortusless.vim.\r\n\r\nSee github for screenshots.\r\n\r\nCredits goes to Thorsten Maerz, Sergei Matusevich and Robert Melton.\r\n\r\n## install details\r\n","install_details":"Unzip and copy tortus.vim and tortusless.vim to `~\/.vim\/colors\/`,\r\nWindows users copy it to `c:\\Users\\\\vimfiles\\colors\\`\r\n\r\n\r\nPut the following lines in your .vimrc for using this color scheme:\r\n\r\n    colorscheme tortus \" or tortusless \" a bit less aggressive version\r\n\r\nIf you use this color scheme with krl.vim or rapid.vim >=1.3.0 and <2.0.0 put\r\n\r\n    let g:krlNoHighLink=1\r\n    let g:rapidNoHighLink=1\r\n\r\nin .vimrc as well.","5":"Unzip and copy tortus.vim and tortusless.vim to `~\/.vim\/colors\/`,\r\nWindows users copy it to `c:\\Users\\\\vimfiles\\colors\\`\r\n\r\n\r\nPut the following lines in your .vimrc for using this color scheme:\r\n\r\n    colorscheme tortus \" or tortusless \" a bit less aggressive version\r\n\r\nIf you use this color scheme with krl.vim or rapid.vim >=1.3.0 and <2.0.0 put\r\n\r\n    let g:krlNoHighLink=1\r\n    let g:rapidNoHighLink=1\r\n\r\nin .vimrc as well.","first_name":"Patrick","6":"Patrick","last_name":"Meiser-Knosowski","7":"Meiser-Knosowski","releases":[{"0":"5390","vim_version":"7.4","1":"7.4","script_version":"v1.0.14","2":"v1.0.14","version_comment":"* Optimizations","3":"* Optimizations","package":"tortus.zip","4":"tortus.zip","src_id":"27870","5":"27870","creation_date":"1640333184","6":"1640333184"},{"0":"5390","vim_version":"7.4","1":"7.4","script_version":"1.0.11","2":"1.0.11","version_comment":"* change diff colors\r\n* bring helpExamples\/helpCommands more to foreground\r\n* bring markdownCode\/markdownCodeBlock more to foreground","3":"* change diff colors\r\n* bring helpExamples\/helpCommands more to foreground\r\n* bring markdownCode\/markdownCodeBlock more to foreground","package":"tortus.zip","4":"tortus.zip","src_id":"26814","5":"26814","creation_date":"1573200011","6":"1573200011"},{"0":"5390","vim_version":"7.4","1":"7.4","script_version":"1.0.10","2":"1.0.10","version_comment":"* bring comments a bit more into foreground\r\n* tortusless: change MatchParen","3":"* bring comments a bit more into foreground\r\n* tortusless: change MatchParen","package":"tortus.zip","4":"tortus.zip","src_id":"26754","5":"26754","creation_date":"1568835996","6":"1568835996"},{"0":"5390","vim_version":"7.0","1":"7.0","script_version":"1.0.9","2":"1.0.9","version_comment":"- optimize terminal colors\r\n- added tortusless.vim, a less aggressive version of tortus.vim","3":"- optimize terminal colors\r\n- added tortusless.vim, a less aggressive version of tortus.vim","package":"tortus.zip","4":"tortus.zip","src_id":"26441","5":"26441","creation_date":"1553890613","6":"1553890613"},{"0":"5390","vim_version":"7.4","1":"7.4","script_version":"1.0.7","2":"1.0.7","version_comment":"Changed Conceal and Underlined","3":"Changed Conceal and Underlined","package":"tortus.vim","4":"tortus.vim","src_id":"25615","5":"25615","creation_date":"1508706112","6":"1508706112"},{"0":"5390","vim_version":"7.0","1":"7.0","script_version":"1.0.6","2":"1.0.6","version_comment":"* changes (and hopefully improvements) in terminal colors","3":"* changes (and hopefully improvements) in terminal colors","package":"tortus.vim","4":"tortus.vim","src_id":"25494","5":"25494","creation_date":"1502361931","6":"1502361931"},{"0":"5390","vim_version":"7.0","1":"7.0","script_version":"1.0.4","2":"1.0.4","version_comment":"* darker status line for background windows\r\n* changes in terminal colors","3":"* darker status line for background windows\r\n* changes in terminal colors","package":"tortus.vim","4":"tortus.vim","src_id":"24603","5":"24603","creation_date":"1475976801","6":"1475976801"},{"0":"5390","vim_version":"7.0","1":"7.0","script_version":"1.0.3","2":"1.0.3","version_comment":"In the previouse version I missed to give KRLs CONTINUE a color in terminals.","3":"In the previouse version I missed to give KRLs CONTINUE a color in terminals.","package":"tortus.vim","4":"tortus.vim","src_id":"24427","5":"24427","creation_date":"1470239499","6":"1470239499"},{"0":"5390","vim_version":"7.0","1":"7.0","script_version":"1.0.2","2":"1.0.2","version_comment":"I wanted a special KRL instruction and comments more in the background and made both much darker.\r\nAlso operators are more dark orange now, instead of red.","3":"I wanted a special KRL instruction and comments more in the background and made both much darker.\r\nAlso operators are more dark orange now, instead of red.","package":"tortus.vim","4":"tortus.vim","src_id":"24385","5":"24385","creation_date":"1469326455","6":"1469326455"},{"0":"5390","vim_version":"7.0","1":"7.0","script_version":"1.0.1","2":"1.0.1","version_comment":"* added Pmenu and WildMenu from metacosm.vim","3":"* added Pmenu and WildMenu from metacosm.vim","package":"tortus.vim","4":"tortus.vim","src_id":"24272","5":"24272","creation_date":"1464232050","6":"1464232050"},{"0":"5390","vim_version":"7.0","1":"7.0","script_version":"1.0.0","2":"1.0.0","version_comment":"Initial upload","3":"Initial upload","package":"tortus.vim","4":"tortus.vim","src_id":"24261","5":"24261","creation_date":"1463914636","6":"1463914636"}]},"5389":{"script_id":"5389","0":"5389","script_name":"RougherExp","1":"RougherExp","script_type":"utility","2":"utility","summary":"Changes your search expression into rougher regexp.","3":"Changes your search expression into rougher regexp.","description":"Usage:\r\n  1. Search for something.\r\n  2. Execute ':RougherExp'.\r\n     Then Vim restarts searching by rougher regexp.\r\n                                                                \r\n  Example:\r\n      \/abc123def('a', 'zzz', 0, null);\r\n      or \/neko999inu('p', 'hogehoge', 1, null);\r\n          |\r\n          V\r\n      \/\\a\\+\\d\\+\\a\\+('\\a',\\s'\\a\\+',\\s\\d,\\s\\a\\+);\r\n                                                                \r\n  Recovery:\r\n      To bring back your search expression, use search history.\r\n      (\/ or \/)\r\n","4":"Usage:\r\n  1. Search for something.\r\n  2. Execute ':RougherExp'.\r\n     Then Vim restarts searching by rougher regexp.\r\n                                                                \r\n  Example:\r\n      \/abc123def('a', 'zzz', 0, null);\r\n      or \/neko999inu('p', 'hogehoge', 1, null);\r\n          |\r\n          V\r\n      \/\\a\\+\\d\\+\\a\\+('\\a',\\s'\\a\\+',\\s\\d,\\s\\a\\+);\r\n                                                                \r\n  Recovery:\r\n      To bring back your search expression, use search history.\r\n      (\/ or \/)\r\n","install_details":"Put this plugin in your plugin directory(e.g. $VIMRUNTIME\/plugin). \r\nThen restart VIM. \r\n","5":"Put this plugin in your plugin directory(e.g. $VIMRUNTIME\/plugin). \r\nThen restart VIM. \r\n","first_name":"Shuhei","6":"Shuhei","last_name":"Kubota","7":"Kubota","releases":[{"0":"5389","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"rougherexp.vim","4":"rougherexp.vim","src_id":"24256","5":"24256","creation_date":"1463643016","6":"1463643016"}]},"5388":{"script_id":"5388","0":"5388","script_name":"Solarized 8","1":"Solarized 8","script_type":"color scheme","2":"color scheme","summary":"Optimized Solarized colorschemes. Best served with true-color terminals!","3":"Optimized Solarized colorschemes. Best served with true-color terminals!","description":"Source code on Github: https:\/\/github.com\/lifepillar\/vim-solarized8\r\n\r\nThis is yet another Solarized theme for Vim. It places itself half way between the original Solarized and the Flattened variant. It removes only some of the bullshit. The color palette is exactly the same as in Solarized, of course, although some highlight groups are defined slightly differently (for instance, I have tried to avoid red on blue).\r\n\r\nThe main reason for the existence of this project is that the original Solarized theme does not define guifg and guibg in terminal Vim, making it unsuitable for versions of Vim supporting true-color terminals. Instead, this color scheme works out of the box everywhere. For the best experience, you need:\r\n\r\n- Vim ≥7.4.1799 with termguicolors set, or\r\n- NeoVim,\r\n\r\nand a true-color enabled terminal. Solarized 8 also works in MacVim, gVim, etc\u00e2\u0080\u00a6: no configuration is needed.\r\n\r\nNOTE: for terminals not supporting true colors, Solarized 8 will fall back to use an approximate palette based on xterm's 256 colors. This is a very crude approximation! To get exact colors with such terminals, you must set your terminal's 16 ANSI colors to the Solarized palette (refer to the manual of your terminal) and put this line in your vimrc before loading the colorscheme:\r\n\r\n    let g:solarized_use16 = 1\r\n\r\nBe aware that, if you set the variable above, but your terminal does not use the Solarized palette, your colors will be completely off.","4":"Source code on Github: https:\/\/github.com\/lifepillar\/vim-solarized8\r\n\r\nThis is yet another Solarized theme for Vim. It places itself half way between the original Solarized and the Flattened variant. It removes only some of the bullshit. The color palette is exactly the same as in Solarized, of course, although some highlight groups are defined slightly differently (for instance, I have tried to avoid red on blue).\r\n\r\nThe main reason for the existence of this project is that the original Solarized theme does not define guifg and guibg in terminal Vim, making it unsuitable for versions of Vim supporting true-color terminals. Instead, this color scheme works out of the box everywhere. For the best experience, you need:\r\n\r\n- Vim ≥7.4.1799 with termguicolors set, or\r\n- NeoVim,\r\n\r\nand a true-color enabled terminal. Solarized 8 also works in MacVim, gVim, etc\u00e2\u0080\u00a6: no configuration is needed.\r\n\r\nNOTE: for terminals not supporting true colors, Solarized 8 will fall back to use an approximate palette based on xterm's 256 colors. This is a very crude approximation! To get exact colors with such terminals, you must set your terminal's 16 ANSI colors to the Solarized palette (refer to the manual of your terminal) and put this line in your vimrc before loading the colorscheme:\r\n\r\n    let g:solarized_use16 = 1\r\n\r\nBe aware that, if you set the variable above, but your terminal does not use the Solarized palette, your colors will be completely off.","install_details":"","5":"","first_name":"","6":"","last_name":"Lifepillar","7":"Lifepillar","releases":[{"0":"5388","vim_version":"8.0","1":"8.0","script_version":"1.2.0","2":"1.2.0","version_comment":"Increased contrast in some cases (in particular, in solarized8_high); added \u00e2\u0080\u009cflat\u00e2\u0080\u009d as an allowed value for g:solarized_statusline; improved readability of popup menus in some circumstances; other minor visual tweaks. Color schemes built with Colortemplate v2.0.0.","3":"Increased contrast in some cases (in particular, in solarized8_high); added \u00e2\u0080\u009cflat\u00e2\u0080\u009d as an allowed value for g:solarized_statusline; improved readability of popup menus in some circumstances; other minor visual tweaks. Color schemes built with Colortemplate v2.0.0.","package":"vim-solarized8-1.2.0.tar.gz","4":"vim-solarized8-1.2.0.tar.gz","src_id":"26616","5":"26616","creation_date":"1563167883","6":"1563167883"},{"0":"5388","vim_version":"7.0","1":"7.0","script_version":"1.1.1","2":"1.1.1","version_comment":"Fixed some incorrect terminal colors in light variants. Deprecated names have been removed: if you are still loading a Solarized8 variant called `solarized8_dark\u00e2\u0080\u00a6` or `solarized8_light\u00e2\u0080\u00a6`, please rename it (remove `_dark` or `_light`). You will need to set the background explicitly, instead. See the Readme for the details.","3":"Fixed some incorrect terminal colors in light variants. Deprecated names have been removed: if you are still loading a Solarized8 variant called `solarized8_dark\u00e2\u0080\u00a6` or `solarized8_light\u00e2\u0080\u00a6`, please rename it (remove `_dark` or `_light`). You will need to set the background explicitly, instead. See the Readme for the details.","package":"vim-solarized8-1.1.1.tar.gz","4":"vim-solarized8-1.1.1.tar.gz","src_id":"26248","5":"26248","creation_date":"1540078674","6":"1540078674"},{"0":"5388","vim_version":"7.0","1":"7.0","script_version":"1.1.0","2":"1.1.0","version_comment":"Define g:terminal_colors. Make vertical split separator visible. Add highlight for JavaScript function call. Automatically fallback to 16 colors when t_Co < 256.","3":"Define g:terminal_colors. Make vertical split separator visible. Add highlight for JavaScript function call. Automatically fallback to 16 colors when t_Co < 256.","package":"vim-solarized8-1.1.0.tar.gz","4":"vim-solarized8-1.1.0.tar.gz","src_id":"26168","5":"26168","creation_date":"1533427948","6":"1533427948"},{"0":"5388","vim_version":"7.0","1":"7.0","script_version":"1.0.2","2":"1.0.2","version_comment":"Add Terminal, ToolbarLine, ToolbarButton hi groups. Do not enable italics by default. Add script to change an xterm color palette.","3":"Add Terminal, ToolbarLine, ToolbarButton hi groups. Do not enable italics by default. Add script to change an xterm color palette.","package":"vim-solarized8-1.0.2.tar.gz","4":"vim-solarized8-1.0.2.tar.gz","src_id":"25790","5":"25790","creation_date":"1516553911","6":"1516553911"},{"0":"5388","vim_version":"7.0","1":"7.0","script_version":"1.0.1","2":"1.0.1","version_comment":"Re-introduce the old colorscheme names (solarized_dark* and solarized_light*) for backward compatibility. Such names are DEPRECATED: please update your vimrc to use the new names (see the Readme).","3":"Re-introduce the old colorscheme names (solarized_dark* and solarized_light*) for backward compatibility. Such names are DEPRECATED: please update your vimrc to use the new names (see the Readme).","package":"vim-solarized8-1.0.1.tar.gz","4":"vim-solarized8-1.0.1.tar.gz","src_id":"25645","5":"25645","creation_date":"1510561010","6":"1510561010"},{"0":"5388","vim_version":"7.0","1":"7.0","script_version":"1.0.0","2":"1.0.0","version_comment":"Solarized 8 reaches v1.0! NOTE: this is a backward incompatible upgrade: review the docs!\r\nSolarized 8 now automatically falls back to xterm's 256 color palette when true colors are not available (using 16 colors is still possible, of course).\r\nThere are now 4 variants instead of 8, because dark and light variants have been merged into a single file: please update your vimrc accordingly.\r\nWhen visibility is set to \"high\", spelling errors are shown in reverse colors.\r\nSolarized 8 is built from Colortemplate templates.","3":"Solarized 8 reaches v1.0! NOTE: this is a backward incompatible upgrade: review the docs!\r\nSolarized 8 now automatically falls back to xterm's 256 color palette when true colors are not available (using 16 colors is still possible, of course).\r\nThere are now 4 variants instead of 8, because dark and light variants have been merged into a single file: please update your vimrc accordingly.\r\nWhen visibility is set to \"high\", spelling errors are shown in reverse colors.\r\nSolarized 8 is built from Colortemplate templates.","package":"vim-solarized8-1.0.0.tar.gz","4":"vim-solarized8-1.0.0.tar.gz","src_id":"25643","5":"25643","creation_date":"1510484924","6":"1510484924"},{"0":"5388","vim_version":"7.0","1":"7.0","script_version":"v0.8","2":"v0.8","version_comment":"Reinstated approximate palette based on xterm 256 colors, for terminals not supporting true colors and not using a Solarized theme. Moved away from messy source script: now the colorscheme is built from Colortemplate's templates.","3":"Reinstated approximate palette based on xterm 256 colors, for terminals not supporting true colors and not using a Solarized theme. Moved away from messy source script: now the colorscheme is built from Colortemplate's templates.","package":"vim-solarized8-0.8.tar.gz","4":"vim-solarized8-0.8.tar.gz","src_id":"25627","5":"25627","creation_date":"1509215868","6":"1509215868"},{"0":"5388","vim_version":"7.0","1":"7.0","script_version":"v0.7","2":"v0.7","version_comment":"Add QuickFixLine highlight group (links to Search by default). Allow the user to choose old-style grey Cursor highlight group (looks like in the original Solarized).","3":"Add QuickFixLine highlight group (links to Search by default). Allow the user to choose old-style grey Cursor highlight group (looks like in the original Solarized).","package":"vim-solarized8-0.7.tar.gz","4":"vim-solarized8-0.7.tar.gz","src_id":"25439","5":"25439","creation_date":"1500842622","6":"1500842622"},{"0":"5388","vim_version":"7.0","1":"7.0","script_version":"0.6","2":"0.6","version_comment":"A few tweaks in some highlight groups (MatchParen).","3":"A few tweaks in some highlight groups (MatchParen).","package":"vim-solarized8-0.6.tar.gz","4":"vim-solarized8-0.6.tar.gz","src_id":"25301","5":"25301","creation_date":"1497172404","6":"1497172404"},{"0":"5388","vim_version":"7.0","1":"7.0","script_version":"0.5","2":"0.5","version_comment":"Updated MatchParen in light themes. Added TermCursor\/TermCursorNC highlight groups.","3":"Updated MatchParen in light themes. Added TermCursor\/TermCursorNC highlight groups.","package":"vim-solarized8-0.5.tar.gz","4":"vim-solarized8-0.5.tar.gz","src_id":"25075","5":"25075","creation_date":"1492423197","6":"1492423197"},{"0":"5388","vim_version":"7.0","1":"7.0","script_version":"0.4","2":"0.4","version_comment":"Makes more element transparent when the background is transparent. Fixes an issue in vimdiff colors being mostly grey. Uses uniform colors for status line, vertical splits and tab line.","3":"Makes more element transparent when the background is transparent. Fixes an issue in vimdiff colors being mostly grey. Uses uniform colors for status line, vertical splits and tab line.","package":"vim-solarized8-0.4.tar.gz","4":"vim-solarized8-0.4.tar.gz","src_id":"24804","5":"24804","creation_date":"1481827357","6":"1481827357"},{"0":"5388","vim_version":"7.0","1":"7.0","script_version":"v0.3","2":"v0.3","version_comment":"Add support for transparent background in terminals.","3":"Add support for transparent background in terminals.","package":"vim-solarized8-0.3.tar.gz","4":"vim-solarized8-0.3.tar.gz","src_id":"24501","5":"24501","creation_date":"1473152878","6":"1473152878"},{"0":"5388","vim_version":"7.0","1":"7.0","script_version":"0.2","2":"0.2","version_comment":"A few bug fixes. Several improvements, especially in the flat variant.","3":"A few bug fixes. Several improvements, especially in the flat variant.","package":"vim-solarized8-0.2.tar.gz","4":"vim-solarized8-0.2.tar.gz","src_id":"24289","5":"24289","creation_date":"1464432840","6":"1464432840"},{"0":"5388","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"vim-solarized8-0.1.tar.gz","4":"vim-solarized8-0.1.tar.gz","src_id":"24249","5":"24249","creation_date":"1463391139","6":"1463391139"}]},"5387":{"script_id":"5387","0":"5387","script_name":"definition.vim","1":"definition.vim","script_type":"utility","2":"utility","summary":"Jump to the last place where [command|function|mapping] was set","3":"Jump to the last place where [command|function|mapping] was set","description":"https:\/\/gist.github.com\/romgrk\/71b119c0baa6b0872f0a88106254ce60\r\n\r\nUsage:\r\n\r\n:Goto [com|fu|nmap|imap|\u00e2\u0080\u00a6] NAME\r\n\r\nOpens the file where it was last-set from, and ~tries~ to jump to the correct line.\r\nI usually find it very useful when I can't remember in which file I defined said command\/func\/mapping.\r\nOr when I get mad at some plugin that is not correctly defined and I just go \u00e2\u0080\u009cDAMN-IT, I\u00c2\u00b4LL JUST EDIT MANUALLY\u00e2\u0080\u009d\r\n","4":"https:\/\/gist.github.com\/romgrk\/71b119c0baa6b0872f0a88106254ce60\r\n\r\nUsage:\r\n\r\n:Goto [com|fu|nmap|imap|\u00e2\u0080\u00a6] NAME\r\n\r\nOpens the file where it was last-set from, and ~tries~ to jump to the correct line.\r\nI usually find it very useful when I can't remember in which file I defined said command\/func\/mapping.\r\nOr when I get mad at some plugin that is not correctly defined and I just go \u00e2\u0080\u009cDAMN-IT, I\u00c2\u00b4LL JUST EDIT MANUALLY\u00e2\u0080\u009d\r\n","install_details":"This is just a few lines; copy to your vimrc or in $VIM\/plugin\/, no need for a plugin manager.","5":"This is just a few lines; copy to your vimrc or in $VIM\/plugin\/, no need for a plugin manager.","first_name":"Rom","6":"Rom","last_name":"Grk","7":"Grk","releases":[{"0":"5387","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"definition.vim","4":"definition.vim","src_id":"24244","5":"24244","creation_date":"1463125366","6":"1463125366"}]},"5386":{"script_id":"5386","0":"5386","script_name":"vim-logreview","1":"vim-logreview","script_type":"utility","2":"utility","summary":"plugin to help log reviews and navigation ","3":"plugin to help log reviews and navigation ","description":"https:\/\/github.com\/andreshazard\/vim-logreview\r\n\r\nAt work I usually have go through Java and Apache log files, looking for specific errors, logs at a certain time range, searching for logs of a specific class, etc. I do this using VIM so I created a plugin for it. I'm not sure how useful it is for logs created by other languages and hosting but I think is not that different or it can be tweak to suit the needs of other situations.\r\n\r\nvim-logreview\r\n\r\nPlugin to help review logs files within VIM.\r\nThis was created with Java log files in mind, however the funcionallity could work\r\nfor other log files as well or you can edit this plugin or send a pull requeest to suite your needs.\r\n\r\nUsage\r\n\r\nThe plugin will detect your .log files and set the filetype as logreview.\r\nIf you need work with log files  that do not have the .log extension.\r\nYou can run :\r\n\r\n\r\nset filetype=logreview\r\n\r\n\r\nThe logreview file types will have highlighting on specific keywords like : INFO, DEBUG, WARN, ERROR, etc. You can see\r\nthis on the syntax folder.\r\n\r\nhttp:\/\/i.imgur.com\/uQoem3G.png\r\n\r\n\r\nFunctions\r\n\r\nThe plugin will load the following commands when working with a logreview file types.\r\n\r\n`:RemoveDEBUGLogs` Will remove all lines containing a \"DEBUG\" log 
\r\n`:RemoveINFOLogs` Will remove all lines containing a \"INFO\" log 
\r\n`:RemoveGREENLogs` Will remove all lines containing a \"INFO\" or \"DEBUG\" log 
\r\n`:RemoveWARNLogs` Will remove all lines containing a \"WARN\" log 
\r\n`:RemoveAllButERRORLogs` Will remove all lines that do not contain an \"ERROR\" log 
\r\n`:RemoveAtExpLogs` Will remove all lines that contain an \" at com.project.package classname test\" type log 
\r\n\r\nhttp:\/\/i.imgur.com\/ppv97Qx.gif\r\n\r\n:RemoveButRangeDayTime day start end\r\n\r\nThis will remove all lines except the ones on the range you provided. For example you can call :\r\n\r\nRemoveButRange 09 10:52 10:54\r\n\r\nto get only the logs between 10:52 and 10:54 on day 09. This works\r\nusing the search command so a line containing those lines needs to exist on the file.\r\nExample of a log line where this would work :\r\n\r\n*2016-04-07 10:52:04,459 [AsyncAppender-Dispatcher-Thread-18] DEBUG com.whatever.module.mail.service*\r\n\r\n:RemoveButRangeFullDateTime date start end\r\n\r\nThis will remove all lines except the ones on the range you provided. For example you can call : \r\nRemoveButRange 08.04.2016 10:52 10:54* \r\n\r\nto get only the logs between 10:52 and 10:54 of the date 08.04.2016. This works\r\nusing the search command so a line containing those lines needs to exist on the file.\r\nExample of a log line where this would work \r\n\r\n*08.04.2016 10:52:04,459 [AsyncAppender-Dispatcher-Thread-18] DEBUG com.trainingrocket.module.mail.service*\r\n\r\nRemoveAllButClass\r\n\r\nThis will remove all lines except the ones containing the string you passed to the function.\r\nFor example you can call :\r\n*RemoveAllBut com.example.my_bad_class* to get only logs relatd to this class.\r\n\r\ni.imgur.com\/VsouksS.gif\r\n\r\nFoldStackBelow\r\n\r\nThis will create a mark fold of the stack below the cursor. It assumes that the stack lines start\r\nwith at lease one space.\r\n\r\ni.imgur.com\/rrVUKji.gif\r\n\r\nMappings\r\n\r\nYou can map the commands that you use the most on your vimrc. \r\nFor example : \r\n\r\n:nnoremap bf :call FoldStackBelow()\r\n\r\n","4":"https:\/\/github.com\/andreshazard\/vim-logreview\r\n\r\nAt work I usually have go through Java and Apache log files, looking for specific errors, logs at a certain time range, searching for logs of a specific class, etc. I do this using VIM so I created a plugin for it. I'm not sure how useful it is for logs created by other languages and hosting but I think is not that different or it can be tweak to suit the needs of other situations.\r\n\r\nvim-logreview\r\n\r\nPlugin to help review logs files within VIM.\r\nThis was created with Java log files in mind, however the funcionallity could work\r\nfor other log files as well or you can edit this plugin or send a pull requeest to suite your needs.\r\n\r\nUsage\r\n\r\nThe plugin will detect your .log files and set the filetype as logreview.\r\nIf you need work with log files  that do not have the .log extension.\r\nYou can run :\r\n\r\n\r\nset filetype=logreview\r\n\r\n\r\nThe logreview file types will have highlighting on specific keywords like : INFO, DEBUG, WARN, ERROR, etc. You can see\r\nthis on the syntax folder.\r\n\r\nhttp:\/\/i.imgur.com\/uQoem3G.png\r\n\r\n\r\nFunctions\r\n\r\nThe plugin will load the following commands when working with a logreview file types.\r\n\r\n`:RemoveDEBUGLogs` Will remove all lines containing a \"DEBUG\" log 
\r\n`:RemoveINFOLogs` Will remove all lines containing a \"INFO\" log 
\r\n`:RemoveGREENLogs` Will remove all lines containing a \"INFO\" or \"DEBUG\" log 
\r\n`:RemoveWARNLogs` Will remove all lines containing a \"WARN\" log 
\r\n`:RemoveAllButERRORLogs` Will remove all lines that do not contain an \"ERROR\" log 
\r\n`:RemoveAtExpLogs` Will remove all lines that contain an \" at com.project.package classname test\" type log 
\r\n\r\nhttp:\/\/i.imgur.com\/ppv97Qx.gif\r\n\r\n:RemoveButRangeDayTime day start end\r\n\r\nThis will remove all lines except the ones on the range you provided. For example you can call :\r\n\r\nRemoveButRange 09 10:52 10:54\r\n\r\nto get only the logs between 10:52 and 10:54 on day 09. This works\r\nusing the search command so a line containing those lines needs to exist on the file.\r\nExample of a log line where this would work :\r\n\r\n*2016-04-07 10:52:04,459 [AsyncAppender-Dispatcher-Thread-18] DEBUG com.whatever.module.mail.service*\r\n\r\n:RemoveButRangeFullDateTime date start end\r\n\r\nThis will remove all lines except the ones on the range you provided. For example you can call : \r\nRemoveButRange 08.04.2016 10:52 10:54* \r\n\r\nto get only the logs between 10:52 and 10:54 of the date 08.04.2016. This works\r\nusing the search command so a line containing those lines needs to exist on the file.\r\nExample of a log line where this would work \r\n\r\n*08.04.2016 10:52:04,459 [AsyncAppender-Dispatcher-Thread-18] DEBUG com.trainingrocket.module.mail.service*\r\n\r\nRemoveAllButClass\r\n\r\nThis will remove all lines except the ones containing the string you passed to the function.\r\nFor example you can call :\r\n*RemoveAllBut com.example.my_bad_class* to get only logs relatd to this class.\r\n\r\ni.imgur.com\/VsouksS.gif\r\n\r\nFoldStackBelow\r\n\r\nThis will create a mark fold of the stack below the cursor. It assumes that the stack lines start\r\nwith at lease one space.\r\n\r\ni.imgur.com\/rrVUKji.gif\r\n\r\nMappings\r\n\r\nYou can map the commands that you use the most on your vimrc. \r\nFor example : \r\n\r\n:nnoremap bf :call FoldStackBelow()\r\n\r\n","install_details":"Instalation\r\n\r\nYou can use Pathogen\r\n```\r\ngit clone https:\/\/github.com\/andreshazard\/vim-logreview.git\r\n~\/.vim\/bundle\/vim-logreview.vim\r\n```\r\nFor Vundle\r\nadd to your vimrc\r\n```\r\nPlugin 'andreshazard\/vim-logreview'\r\n```","5":"Instalation\r\n\r\nYou can use Pathogen\r\n```\r\ngit clone https:\/\/github.com\/andreshazard\/vim-logreview.git\r\n~\/.vim\/bundle\/vim-logreview.vim\r\n```\r\nFor Vundle\r\nadd to your vimrc\r\n```\r\nPlugin 'andreshazard\/vim-logreview'\r\n```","first_name":"Andres","6":"Andres","last_name":"Hazard","7":"Hazard","releases":[{"0":"5386","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"vim-logreview.tar","4":"vim-logreview.tar","src_id":"24240","5":"24240","creation_date":"1462827408","6":"1462827408"}]},"5385":{"script_id":"5385","0":"5385","script_name":"vim-freemarker","1":"vim-freemarker","script_type":"ftplugin","2":"ftplugin","summary":"Freemarker syntax and functions","3":"Freemarker syntax and functions","description":"When opening a .ftl file the filetype will be set to \"freemarker\" this will activate the syntax highlighting.\r\n\r\nThe plugin also has some functions for quick editing.\r\n\r\nFunctions and Mapping\r\n\r\nThe plugin has the follwing functions that will only be load when opening a .ftl file, you can map them in your vimrc :\r\n\r\n:call FTLIf()\r\n\r\nIt will insert the basic if tags (#if-#else) and leave the cursor after the if tag in insert mode You can use this map in your vimrc\r\n\r\n                nnoremap fi :call FTLIf()\r\n:call FTLList()\r\n\r\nIt will insert the basic list tags(#list-#else-\/#list). Cursor after the list tag in insert mode You can use this map in your vimrc\r\n\r\n                nnoremap fl :call FTLList()\r\n:call FTLBigList()\r\n\r\nIt will insert the new (since FreeMarker 2.3.23) list tags(#list-#items-\/#items-#else-\/#list). Cursor after the list tag in insert mode You can use this map in your vimrc\r\n\r\n                nnoremap fb :call FTLBigList()\r\n:call FTLSwitch()\r\n\r\nIt will insert the switch tags(#switch, 3 #case and #break, #default, \/#switch). Cursor after the switch tag in insert mode You can use this map in your vimrc\r\n\r\n                nnoremap fs :call FTLSwitch()\r\n:call FTLAssign()\r\n\r\nIt will insert the assign tag and leave the cursor on insert mode\r\n\r\n                nnoremap fa :call FTLAssign()","4":"When opening a .ftl file the filetype will be set to \"freemarker\" this will activate the syntax highlighting.\r\n\r\nThe plugin also has some functions for quick editing.\r\n\r\nFunctions and Mapping\r\n\r\nThe plugin has the follwing functions that will only be load when opening a .ftl file, you can map them in your vimrc :\r\n\r\n:call FTLIf()\r\n\r\nIt will insert the basic if tags (#if-#else) and leave the cursor after the if tag in insert mode You can use this map in your vimrc\r\n\r\n                nnoremap fi :call FTLIf()\r\n:call FTLList()\r\n\r\nIt will insert the basic list tags(#list-#else-\/#list). Cursor after the list tag in insert mode You can use this map in your vimrc\r\n\r\n                nnoremap fl :call FTLList()\r\n:call FTLBigList()\r\n\r\nIt will insert the new (since FreeMarker 2.3.23) list tags(#list-#items-\/#items-#else-\/#list). Cursor after the list tag in insert mode You can use this map in your vimrc\r\n\r\n                nnoremap fb :call FTLBigList()\r\n:call FTLSwitch()\r\n\r\nIt will insert the switch tags(#switch, 3 #case and #break, #default, \/#switch). Cursor after the switch tag in insert mode You can use this map in your vimrc\r\n\r\n                nnoremap fs :call FTLSwitch()\r\n:call FTLAssign()\r\n\r\nIt will insert the assign tag and leave the cursor on insert mode\r\n\r\n                nnoremap fa :call FTLAssign()","install_details":"Installation\r\n\r\nYou can use Pathogen\r\n\r\ngit clone https:\/\/github.com\/andreshazard\/vim-freemarker.git\r\n~\/.vim\/bundle\/vim-freemarker.vim\r\nFor Vundle add to your vimrc\r\n\r\nPlugin 'andreshazard\/vim-freemarker'\r\n","5":"Installation\r\n\r\nYou can use Pathogen\r\n\r\ngit clone https:\/\/github.com\/andreshazard\/vim-freemarker.git\r\n~\/.vim\/bundle\/vim-freemarker.vim\r\nFor Vundle add to your vimrc\r\n\r\nPlugin 'andreshazard\/vim-freemarker'\r\n","first_name":"Andres","6":"Andres","last_name":"Hazard","7":"Hazard","releases":[{"0":"5385","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"vim-freemarker.tar","4":"vim-freemarker.tar","src_id":"24239","5":"24239","creation_date":"1462683257","6":"1462683257"}]},"5384":{"script_id":"5384","0":"5384","script_name":"vim-stackoverflow","1":"vim-stackoverflow","script_type":"utility","2":"utility","summary":"A tiny plugin for searching Stackoverflow from VIM editor ","3":"A tiny plugin for searching Stackoverflow from VIM editor ","description":"vim-stackoverflow is a tiny plugin that allows you to perform a quick Stackoverflow search directly from Vim.\r\n\r\nIt opens a new browser window with results.\r\n\r\nWith inspiration from vim-g\r\n\r\nTo lookup a word (or words) in Stackoverflow use SO command:\r\n\r\n:SO ruby\r\nSO command can use a word under the cursor. Just move the cursor to the word and type the same command in the command line:\r\n\r\n:SO\r\nAdditionally, you can select words in the visual mode exactly in the same way. Just select words and type :SO. You can also prepend your selection with more clues:\r\n\r\n:SO function\r\n:SO ruby\r\nThere is also a special command named SOf to prepend the current file type automatically:\r\n\r\n:SOf\r\n:SOf function\r\n","4":"vim-stackoverflow is a tiny plugin that allows you to perform a quick Stackoverflow search directly from Vim.\r\n\r\nIt opens a new browser window with results.\r\n\r\nWith inspiration from vim-g\r\n\r\nTo lookup a word (or words) in Stackoverflow use SO command:\r\n\r\n:SO ruby\r\nSO command can use a word under the cursor. Just move the cursor to the word and type the same command in the command line:\r\n\r\n:SO\r\nAdditionally, you can select words in the visual mode exactly in the same way. Just select words and type :SO. You can also prepend your selection with more clues:\r\n\r\n:SO function\r\n:SO ruby\r\nThere is also a special command named SOf to prepend the current file type automatically:\r\n\r\n:SOf\r\n:SOf function\r\n","install_details":"Vundle\r\n\r\nAdd to your .vimrc\r\n\r\nPlugin 'hienvd\/vim-stackoverflow'\r\n\r\nthen open VIM, install\r\n\r\n:PluginInstall","5":"Vundle\r\n\r\nAdd to your .vimrc\r\n\r\nPlugin 'hienvd\/vim-stackoverflow'\r\n\r\nthen open VIM, install\r\n\r\n:PluginInstall","first_name":"Hien","6":"Hien","last_name":"Vuong","7":"Vuong","releases":[{"0":"5384","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"stackoverflow.vim","4":"stackoverflow.vim","src_id":"24236","5":"24236","creation_date":"1462615707","6":"1462615707"}]},"5383":{"script_id":"5383","0":"5383","script_name":"caw.vim","1":"caw.vim","script_type":"utility","2":"utility","summary":"Comment plugin: Operator mappings\/Dot-repeatable\/300+ filetypes","3":"Comment plugin: Operator mappings\/Dot-repeatable\/300+ filetypes","description":"Latest version: https:\/\/github.com\/tyru\/caw.vim\r\n\r\n==============================================================================\r\nINTRODUCTION\r\n\r\nThe below are the examples in \"filetype=c\".\r\ncaw.vim supports 300+ filetypes (see |caw-supported-filetypes|).\r\n\r\nType \"gci\" (toggle: \"gcc\", uncomment: \"gcui\")\r\n  before:\r\n    \"   <- inserted here\"\r\n  after:\r\n    \"   # <- inserted here\"\r\n\r\nType \"gcI\" (uncomment: \"gcuI\")\r\n  before:\r\n    \"   inserted the first column\"\r\n  after:\r\n    \"#    inserted the first column\"\r\n\r\nType \"gca\" (uncomment: \"gcua\")\r\n  before:\r\n    \"inserted after this\"\r\n  after:\r\n    \"inserted after this    # \"\r\n\r\nType \"gcw\" (uncomment: \"gcuw\")\r\n  before:\r\n    \"  wrap!\"\r\n  after:\r\n    \"  \/* wrap! *\/\"\r\n\r\nType \"gcb\"\r\n  before:\r\n    \"  box!\"\r\n  after:\r\n    \"  \/********\/\"\r\n    \"  \/* box! *\/\"\r\n    \"  \/********\/\"\r\n\r\nType \"gco\"\r\n  before:\r\n    \"   func1();\"\r\n  after:\r\n    \"   func1()\"\r\n    \"   \/\/ \"  (now cursor is at the end and entered insert-mode)\r\n\r\nType \"gcO\"\r\n  before:\r\n    \"   func1();\"\r\n  after:\r\n    \"   \/\/ \"  (now cursor is at the end and entered insert-mode)\r\n    \"   func1();\"\r\n\r\n==============================================================================\r\nFEATURES\r\n\r\n* Supports 300+ filetypes (see |caw-supported-filetypes|).\r\n  * But caw.vim does not slow down your Vim startup because each comment\r\n    string are defined at ftplugin files (after\/ftplugin\/\/caw.vim).\r\n* Supports operator keymappings (|caw-keymappings-operator|).\r\n  * If |g:caw_operator_keymappings| is non-zero, all default keymappings map\r\n    to operator keymappings.\r\n  * If you need operator-user.vim to use operator keymappings.\r\n    https:\/\/github.com\/kana\/vim-operator-user\r\n* Supports also non-operator keymappings (|caw-keymappings-non-operator|).\r\n* Dot-repeatable if you installed repeat.vim\r\n  https:\/\/github.com\/kana\/vim-repeat\r\n* The comment behavior only depends on 'filetype' by default.\r\n  But if you have installed context_filetype.vim, caw.vim also depends on the\r\n  filetype of the context of the current cursor location.\r\n  https:\/\/github.com\/Shougo\/context_filetype.vim\r\n  So you can comment\/uncomment JavaScript in HTML correctly.\r\n* Well-tested powered by https:\/\/github.com\/thinca\/vim-themis","4":"Latest version: https:\/\/github.com\/tyru\/caw.vim\r\n\r\n==============================================================================\r\nINTRODUCTION\r\n\r\nThe below are the examples in \"filetype=c\".\r\ncaw.vim supports 300+ filetypes (see |caw-supported-filetypes|).\r\n\r\nType \"gci\" (toggle: \"gcc\", uncomment: \"gcui\")\r\n  before:\r\n    \"   <- inserted here\"\r\n  after:\r\n    \"   # <- inserted here\"\r\n\r\nType \"gcI\" (uncomment: \"gcuI\")\r\n  before:\r\n    \"   inserted the first column\"\r\n  after:\r\n    \"#    inserted the first column\"\r\n\r\nType \"gca\" (uncomment: \"gcua\")\r\n  before:\r\n    \"inserted after this\"\r\n  after:\r\n    \"inserted after this    # \"\r\n\r\nType \"gcw\" (uncomment: \"gcuw\")\r\n  before:\r\n    \"  wrap!\"\r\n  after:\r\n    \"  \/* wrap! *\/\"\r\n\r\nType \"gcb\"\r\n  before:\r\n    \"  box!\"\r\n  after:\r\n    \"  \/********\/\"\r\n    \"  \/* box! *\/\"\r\n    \"  \/********\/\"\r\n\r\nType \"gco\"\r\n  before:\r\n    \"   func1();\"\r\n  after:\r\n    \"   func1()\"\r\n    \"   \/\/ \"  (now cursor is at the end and entered insert-mode)\r\n\r\nType \"gcO\"\r\n  before:\r\n    \"   func1();\"\r\n  after:\r\n    \"   \/\/ \"  (now cursor is at the end and entered insert-mode)\r\n    \"   func1();\"\r\n\r\n==============================================================================\r\nFEATURES\r\n\r\n* Supports 300+ filetypes (see |caw-supported-filetypes|).\r\n  * But caw.vim does not slow down your Vim startup because each comment\r\n    string are defined at ftplugin files (after\/ftplugin\/\/caw.vim).\r\n* Supports operator keymappings (|caw-keymappings-operator|).\r\n  * If |g:caw_operator_keymappings| is non-zero, all default keymappings map\r\n    to operator keymappings.\r\n  * If you need operator-user.vim to use operator keymappings.\r\n    https:\/\/github.com\/kana\/vim-operator-user\r\n* Supports also non-operator keymappings (|caw-keymappings-non-operator|).\r\n* Dot-repeatable if you installed repeat.vim\r\n  https:\/\/github.com\/kana\/vim-repeat\r\n* The comment behavior only depends on 'filetype' by default.\r\n  But if you have installed context_filetype.vim, caw.vim also depends on the\r\n  filetype of the context of the current cursor location.\r\n  https:\/\/github.com\/Shougo\/context_filetype.vim\r\n  So you can comment\/uncomment JavaScript in HTML correctly.\r\n* Well-tested powered by https:\/\/github.com\/thinca\/vim-themis","install_details":"","5":"","first_name":"tyru","6":"tyru","last_name":" ","7":" ","releases":[{"0":"5383","vim_version":"7.3","1":"7.3","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"caw-v1.0.zip","4":"caw-v1.0.zip","src_id":"24223","5":"24223","creation_date":"1462287279","6":"1462287279"}]},"5382":{"script_id":"5382","0":"5382","script_name":"ensime-vim","1":"ensime-vim","script_type":"ftplugin","2":"ftplugin","summary":"Ensime support for Scala and Java files","3":"Ensime support for Scala and Java files","description":"Checkout http:\/\/ensime.github.io for details","4":"Checkout http:\/\/ensime.github.io for details","install_details":"Installation instructions at http:\/\/ensime.github.io","5":"Installation instructions at http:\/\/ensime.github.io","first_name":"Chris","6":"Chris","last_name":"Coffey","7":"Coffey","releases":[{"0":"5382","vim_version":"7.4","1":"7.4","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"ensime-vim.tar.gz","4":"ensime-vim.tar.gz","src_id":"24221","5":"24221","creation_date":"1462202498","6":"1462202498"}]},"5381":{"script_id":"5381","0":"5381","script_name":"Scalpel","1":"Scalpel","script_type":"utility","2":"utility","summary":"Fast within-file word replacement for Vim","3":"Fast within-file word replacement for Vim","description":"# Intro\r\n\r\nScalpel provides a streamlined shortcut for replacing all instances of the word currently under the cursor throughout a file.\r\n\r\nIn normal mode pressing `e` (mnemonic: \"edit\") will display a prompt pre-populated with the current word and with the cursor placed so that you can start typing the desired replacement:\r\n\r\n```\r\n:Scalpel\/\\v\/\/\r\n```\r\n\r\nPress `` and Scalpel will prompt to confirm each substitution, starting at the current word (unlike a normal `:%s` command, which starts at the top of the file).\r\n\r\nNote that `:Scalpel` just calls through to an underlying `scalpel#substitute` function that does the real work, ultimately calling Vim's own `:substitute`. As such, be aware that whatever changes you make to the command-line prior to pressing `` must keep it a valid pattern, or bad things will happen.\r\n\r\nThe mapping can be suppressed by setting:\r\n\r\n```\r\nlet g:ScalpelMap=0\r\n```\r\n\r\nOr overridden:\r\n\r\n```\r\n\" Use s instead of default e:\r\nnmap s (Scalpel)\r\n```\r\n\r\nIn any case, Scalpel won't overwrite any pre-existing mapping that you might have defined for `e`, nor will it create an unnecessary redundant mapping if you've already mapped something to `(Scalpel)`.\r\n\r\nThe `:Scalpel` command name can be overridden if desired. For example, you could shorten it to `:S` with:\r\n\r\n```\r\nlet g:ScalpelCommand='S'\r\n```\r\n\r\nThen your Scalpel prompt would look like:\r\n\r\n```\r\n:S\/\\v\/\/\r\n```\r\n\r\nThe command can be entirely suppressed by setting `g:ScalpelCommand` to an empty string:\r\n\r\n```\r\nlet g:ScalpelCommand=''\r\n```\r\n\r\nFinally, all plug-in functionality can be deactivated by setting:\r\n\r\n```\r\nlet g:ScalpelLoaded=1\r\n```\r\n\r\nin your `~\/.vimrc`.\r\n\r\n# Installation\r\n\r\nTo install Scalpel, use your plug-in management system of choice.\r\n\r\nIf you don't have a \"plug-in management system of choice\" and your version of Vim has `packages` support (ie. `+packages` appears in the output of `:version`) then you can simply place the plugin at a location under your `'packpath'` (eg. `~\/.vim\/pack\/bundle\/start\/scalpel` or similar).\r\n\r\nFor older versions of Vim, I recommend [Pathogen](https:\/\/github.com\/tpope\/vim-pathogen) due to its simplicity and robustness. Assuming that you have Pathogen installed and configured, and that you want to install Scalpel into `~\/.vim\/bundle`, you can do so with:\r\n\r\n```\r\ngit clone https:\/\/github.com\/wincent\/scalpel.git ~\/.vim\/bundle\/scalpel\r\n```\r\n\r\nAlternatively, if you use a Git submodule for each Vim plug-in, you could do the following after `cd`-ing into the top-level of your Git superproject:\r\n\r\n```\r\ngit submodule add https:\/\/github.com\/wincent\/scalpel.git ~\/vim\/bundle\/scalpel\r\ngit submodule init\r\n```\r\n\r\nTo generate help tags under Pathogen, you can do so from inside Vim with:\r\n\r\n```\r\n:call pathogen#helptags()\r\n```\r\n\r\n# Website\r\n\r\nThe official Scalpel source code repo is at:\r\n\r\nhttp:\/\/git.wincent.com\/scalpel.git\r\n\r\nMirrors exist at:\r\n\r\n- https:\/\/github.com\/wincent\/scalpel\r\n- https:\/\/gitlab.com\/wincent\/scalpel\r\n- https:\/\/bitbucket.org\/ghurrell\/scalpel\r\n\r\nOfficial releases are listed at:\r\n\r\nhttp:\/\/www.vim.org\/scripts\/script.php?script_id=5381\r\n\r\n# License\r\n\r\nCopyright (c) 2016-present Greg Hurrell\r\n\r\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the \"Software\"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and\/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\r\n\r\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\r\n\r\nTHE SOFTWARE IS PROVIDED \"AS IS\", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.\r\n\r\n# Development\r\n\r\n## Contributing patches\r\n\r\nPatches can be sent via mail to greg@hurrell.net, or as GitHub pull requests at: https:\/\/github.com\/wincent\/scalpel\/pulls\r\n\r\n## Cutting a new release\r\n\r\nAt the moment the release process is manual:\r\n\r\n- Perform final sanity checks and manual testing.\r\n- Update the [scalpel-history](#user-content-scalpel-history) section of the documentation.\r\n- Verify clean work tree:\r\n\r\n```\r\ngit status\r\n```\r\n\r\n- Tag the release:\r\n\r\n```\r\ngit tag -s -m \"$VERSION release\" $VERSION\r\n```\r\n\r\n- Publish the code:\r\n\r\n```\r\ngit push origin master --follow-tags\r\ngit push github master --follow-tags\r\n```\r\n\r\n- Produce the release archive:\r\n\r\n```\r\ngit archive -o scalpel-$VERSION.zip HEAD -- .\r\n```\r\n\r\n- Upload to http:\/\/www.vim.org\/scripts\/script.php?script_id=5381\r\n\r\n# Authors\r\n\r\nScalpel is written and maintained by Greg Hurrell .","4":"# Intro\r\n\r\nScalpel provides a streamlined shortcut for replacing all instances of the word currently under the cursor throughout a file.\r\n\r\nIn normal mode pressing `e` (mnemonic: \"edit\") will display a prompt pre-populated with the current word and with the cursor placed so that you can start typing the desired replacement:\r\n\r\n```\r\n:Scalpel\/\\v\/\/\r\n```\r\n\r\nPress `` and Scalpel will prompt to confirm each substitution, starting at the current word (unlike a normal `:%s` command, which starts at the top of the file).\r\n\r\nNote that `:Scalpel` just calls through to an underlying `scalpel#substitute` function that does the real work, ultimately calling Vim's own `:substitute`. As such, be aware that whatever changes you make to the command-line prior to pressing `` must keep it a valid pattern, or bad things will happen.\r\n\r\nThe mapping can be suppressed by setting:\r\n\r\n```\r\nlet g:ScalpelMap=0\r\n```\r\n\r\nOr overridden:\r\n\r\n```\r\n\" Use s instead of default e:\r\nnmap s (Scalpel)\r\n```\r\n\r\nIn any case, Scalpel won't overwrite any pre-existing mapping that you might have defined for `e`, nor will it create an unnecessary redundant mapping if you've already mapped something to `(Scalpel)`.\r\n\r\nThe `:Scalpel` command name can be overridden if desired. For example, you could shorten it to `:S` with:\r\n\r\n```\r\nlet g:ScalpelCommand='S'\r\n```\r\n\r\nThen your Scalpel prompt would look like:\r\n\r\n```\r\n:S\/\\v\/\/\r\n```\r\n\r\nThe command can be entirely suppressed by setting `g:ScalpelCommand` to an empty string:\r\n\r\n```\r\nlet g:ScalpelCommand=''\r\n```\r\n\r\nFinally, all plug-in functionality can be deactivated by setting:\r\n\r\n```\r\nlet g:ScalpelLoaded=1\r\n```\r\n\r\nin your `~\/.vimrc`.\r\n\r\n# Installation\r\n\r\nTo install Scalpel, use your plug-in management system of choice.\r\n\r\nIf you don't have a \"plug-in management system of choice\" and your version of Vim has `packages` support (ie. `+packages` appears in the output of `:version`) then you can simply place the plugin at a location under your `'packpath'` (eg. `~\/.vim\/pack\/bundle\/start\/scalpel` or similar).\r\n\r\nFor older versions of Vim, I recommend [Pathogen](https:\/\/github.com\/tpope\/vim-pathogen) due to its simplicity and robustness. Assuming that you have Pathogen installed and configured, and that you want to install Scalpel into `~\/.vim\/bundle`, you can do so with:\r\n\r\n```\r\ngit clone https:\/\/github.com\/wincent\/scalpel.git ~\/.vim\/bundle\/scalpel\r\n```\r\n\r\nAlternatively, if you use a Git submodule for each Vim plug-in, you could do the following after `cd`-ing into the top-level of your Git superproject:\r\n\r\n```\r\ngit submodule add https:\/\/github.com\/wincent\/scalpel.git ~\/vim\/bundle\/scalpel\r\ngit submodule init\r\n```\r\n\r\nTo generate help tags under Pathogen, you can do so from inside Vim with:\r\n\r\n```\r\n:call pathogen#helptags()\r\n```\r\n\r\n# Website\r\n\r\nThe official Scalpel source code repo is at:\r\n\r\nhttp:\/\/git.wincent.com\/scalpel.git\r\n\r\nMirrors exist at:\r\n\r\n- https:\/\/github.com\/wincent\/scalpel\r\n- https:\/\/gitlab.com\/wincent\/scalpel\r\n- https:\/\/bitbucket.org\/ghurrell\/scalpel\r\n\r\nOfficial releases are listed at:\r\n\r\nhttp:\/\/www.vim.org\/scripts\/script.php?script_id=5381\r\n\r\n# License\r\n\r\nCopyright (c) 2016-present Greg Hurrell\r\n\r\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the \"Software\"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and\/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\r\n\r\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\r\n\r\nTHE SOFTWARE IS PROVIDED \"AS IS\", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.\r\n\r\n# Development\r\n\r\n## Contributing patches\r\n\r\nPatches can be sent via mail to greg@hurrell.net, or as GitHub pull requests at: https:\/\/github.com\/wincent\/scalpel\/pulls\r\n\r\n## Cutting a new release\r\n\r\nAt the moment the release process is manual:\r\n\r\n- Perform final sanity checks and manual testing.\r\n- Update the [scalpel-history](#user-content-scalpel-history) section of the documentation.\r\n- Verify clean work tree:\r\n\r\n```\r\ngit status\r\n```\r\n\r\n- Tag the release:\r\n\r\n```\r\ngit tag -s -m \"$VERSION release\" $VERSION\r\n```\r\n\r\n- Publish the code:\r\n\r\n```\r\ngit push origin master --follow-tags\r\ngit push github master --follow-tags\r\n```\r\n\r\n- Produce the release archive:\r\n\r\n```\r\ngit archive -o scalpel-$VERSION.zip HEAD -- .\r\n```\r\n\r\n- Upload to http:\/\/www.vim.org\/scripts\/script.php?script_id=5381\r\n\r\n# Authors\r\n\r\nScalpel is written and maintained by Greg Hurrell .","install_details":"","5":"","first_name":"Greg","6":"Greg","last_name":"Hurrell","7":"Hurrell","releases":[{"0":"5381","vim_version":"7.0","1":"7.0","script_version":"1.1","2":"1.1","version_comment":"- Automatically escape characters that may have special meaning for |\/\\v|\r\n  (patch from Keng Kiat Lim, https:\/\/github.com\/wincent\/scalpel\/pull\/11).\r\n","3":"- Automatically escape characters that may have special meaning for |\/\\v|\r\n  (patch from Keng Kiat Lim, https:\/\/github.com\/wincent\/scalpel\/pull\/11).\r\n","package":"scalpel-1.1.zip","4":"scalpel-1.1.zip","src_id":"27200","5":"27200","creation_date":"1592010781","6":"1592010781"},{"0":"5381","vim_version":"7.0","1":"7.0","script_version":"1.0.1","2":"1.0.1","version_comment":"- Prefer |execute()| when available to avoid potential nested |:redir| issues.","3":"- Prefer |execute()| when available to avoid potential nested |:redir| issues.","package":"scalpel-1.0.1.zip","4":"scalpel-1.0.1.zip","src_id":"26411","5":"26411","creation_date":"1551904516","6":"1551904516"},{"0":"5381","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"- Perform multiple replacements per line even when 'gdefault' is on.","3":"- Perform multiple replacements per line even when 'gdefault' is on.","package":"scalpel-1.0.zip","4":"scalpel-1.0.zip","src_id":"26315","5":"26315","creation_date":"1546546298","6":"1546546298"},{"0":"5381","vim_version":"7.0","1":"7.0","script_version":"0.5","2":"0.5","version_comment":"- Fix problem with |Visual| mode operation on older versions of Vim (GitHub issue #8).\r\n","3":"- Fix problem with |Visual| mode operation on older versions of Vim (GitHub issue #8).\r\n","package":"scalpel-0.5.zip","4":"scalpel-0.5.zip","src_id":"26153","5":"26153","creation_date":"1532876997","6":"1532876997"},{"0":"5381","vim_version":"7.0","1":"7.0","script_version":"0.4","2":"0.4","version_comment":"- Fix problem with replacement patterns containing the number 1 (GitHub issue #7).\r\n","3":"- Fix problem with replacement patterns containing the number 1 (GitHub issue #7).\r\n","package":"scalpel-0.4.zip","4":"scalpel-0.4.zip","src_id":"26145","5":"26145","creation_date":"1532447120","6":"1532447120"},{"0":"5381","vim_version":"7.0","1":"7.0","script_version":"0.3","2":"0.3","version_comment":"- Fix compatibility with older versions of Vim that don't implement\r\n  |getcurpos()|.","3":"- Fix compatibility with older versions of Vim that don't implement\r\n  |getcurpos()|.","package":"scalpel-0.3.zip","4":"scalpel-0.3.zip","src_id":"25975","5":"25975","creation_date":"1526022021","6":"1526022021"},{"0":"5381","vim_version":"7.0","1":"7.0","script_version":"0.2","2":"0.2","version_comment":"- Support visual mode.\r\n- Do not show \"N substitutions on N lines\" messages.","3":"- Support visual mode.\r\n- Do not show \"N substitutions on N lines\" messages.","package":"scalpel-0.2.zip","4":"scalpel-0.2.zip","src_id":"24324","5":"24324","creation_date":"1465832342","6":"1465832342"},{"0":"5381","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"scalpel-0.1.zip","4":"scalpel-0.1.zip","src_id":"24215","5":"24215","creation_date":"1461943554","6":"1461943554"}]},"5380":{"script_id":"5380","0":"5380","script_name":"splat-syntax","1":"splat-syntax","script_type":"syntax","2":"syntax","summary":"Syntax for Splat","3":"Syntax for Splat","description":"A vim syntax for the Splat programming language. A functional language written in a couple of days, for a module at the University of Southampton.\r\n\r\nLanguage repo can be found at:\r\nhttps:\/\/github.com\/MarsCapone\/splat","4":"A vim syntax for the Splat programming language. A functional language written in a couple of days, for a module at the University of Southampton.\r\n\r\nLanguage repo can be found at:\r\nhttps:\/\/github.com\/MarsCapone\/splat","install_details":"Move the file to `~\/.vim\/syntax\/splat.vim`","5":"Move the file to `~\/.vim\/syntax\/splat.vim`","first_name":"Samson ","6":"Samson ","last_name":"Danziger","7":"Danziger","releases":[{"0":"5380","vim_version":"7.0","1":"7.0","script_version":"0.1.0","2":"0.1.0","version_comment":"Initial upload","3":"Initial upload","package":"splat.vim","4":"splat.vim","src_id":"24209","5":"24209","creation_date":"1461832920","6":"1461832920"}]},"5378":{"script_id":"5378","0":"5378","script_name":"Mesonic","1":"Mesonic","script_type":"ftplugin","2":"ftplugin","summary":"A Vim plugin for Meson build system","3":"A Vim plugin for Meson build system","description":"Mesonic is a plugin that uses Vim compiler infrastructure to integrate Meson build system (http:\/\/mesonbuild.com\/) into an editor with special handling of out-of-source builds. It sets 'makeprg', 'errorformat' options and provides syntax highlighting for meson.build files.\r\n\r\nUse :MesonInit to initialise build directory for the first time. After that you can issue :make command as usual, which produces correct quickfix list no matter what current directory is. All commands work as expected from any subdirectory of your project.\r\n\r\nYou can customise meson and ninja commands with the following variables, which can be either global or buffer local. Defaults are listed below.\r\n\r\nlet b:meson_command = 'meson'\r\nlet b:meson_ninja_command = 'ninja'\r\n\r\nIf you want to switch between build directories, issue :MesonInit command with an argument. For example, to switch to 'build-special' directory, issue\r\n\r\n:MesonInit 'build-special'\r\n\r\nThe directory will be initialised if it does not exist or does not contain build.ninja file. As of the current version Meson options can be added only via b:meson_command variable.\r\n\r\nMesonic assumes that build directory is a subdirectory of top-level directory of your project, i.e. build directory is located in the same directory where your main meson.build file is. In all other cases it may produce wrong file paths in quickfix list.\r\n\r\nThis plugin was created as a result of my passion for Vim and C++ programming, and as a consequence of reading \"Learn Vimscript the Hard Way\" by Steve Losh (http:\/\/learnvimscriptthehardway.stevelosh.com\/). Feel free to contribute or post a bug at GitHub project page (https:\/\/github.com\/igankevich\/mesonic).","4":"Mesonic is a plugin that uses Vim compiler infrastructure to integrate Meson build system (http:\/\/mesonbuild.com\/) into an editor with special handling of out-of-source builds. It sets 'makeprg', 'errorformat' options and provides syntax highlighting for meson.build files.\r\n\r\nUse :MesonInit to initialise build directory for the first time. After that you can issue :make command as usual, which produces correct quickfix list no matter what current directory is. All commands work as expected from any subdirectory of your project.\r\n\r\nYou can customise meson and ninja commands with the following variables, which can be either global or buffer local. Defaults are listed below.\r\n\r\nlet b:meson_command = 'meson'\r\nlet b:meson_ninja_command = 'ninja'\r\n\r\nIf you want to switch between build directories, issue :MesonInit command with an argument. For example, to switch to 'build-special' directory, issue\r\n\r\n:MesonInit 'build-special'\r\n\r\nThe directory will be initialised if it does not exist or does not contain build.ninja file. As of the current version Meson options can be added only via b:meson_command variable.\r\n\r\nMesonic assumes that build directory is a subdirectory of top-level directory of your project, i.e. build directory is located in the same directory where your main meson.build file is. In all other cases it may produce wrong file paths in quickfix list.\r\n\r\nThis plugin was created as a result of my passion for Vim and C++ programming, and as a consequence of reading \"Learn Vimscript the Hard Way\" by Steve Losh (http:\/\/learnvimscriptthehardway.stevelosh.com\/). Feel free to contribute or post a bug at GitHub project page (https:\/\/github.com\/igankevich\/mesonic).","install_details":"Install via your favourite plugin manager as 'igankevich\/mesonic' or download the package here, unpack it and move all directories to your ~\/.vim folder.","5":"Install via your favourite plugin manager as 'igankevich\/mesonic' or download the package here, unpack it and move all directories to your ~\/.vim folder.","first_name":"Ivan","6":"Ivan","last_name":"Gankevich","7":"Gankevich","releases":[{"0":"5378","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"mesonic-1.0.0.tar.gz","4":"mesonic-1.0.0.tar.gz","src_id":"24206","5":"24206","creation_date":"1461768985","6":"1461768985"}]},"5377":{"script_id":"5377","0":"5377","script_name":"vim-grimmjow","1":"vim-grimmjow","script_type":"color scheme","2":"color scheme","summary":"Light Theme for Gvim, MacVim and Neovim","3":"Light Theme for Gvim, MacVim and Neovim","description":"Light colorscheme for GVim, MacVim and Neovim.\r\n\r\nMain features:\r\n\r\n256 color terminal support\r\nSupport for several plugins\r\n\r\nGithub repository: https:\/\/github.com\/adelarsq\/vim-grimmjow","4":"Light colorscheme for GVim, MacVim and Neovim.\r\n\r\nMain features:\r\n\r\n256 color terminal support\r\nSupport for several plugins\r\n\r\nGithub repository: https:\/\/github.com\/adelarsq\/vim-grimmjow","install_details":"Just copy the file to your .vim\/colors folder. ","5":"Just copy the file to your .vim\/colors folder. ","first_name":"Adelar","6":"Adelar","last_name":"da Silva Queir\u00c3\u00b3z","7":"da Silva Queir\u00c3\u00b3z","releases":[{"0":"5377","vim_version":"7.0","1":"7.0","script_version":"0.0.13","2":"0.0.13","version_comment":"- No more support for dark background\r\n- vim-nerdtree-syntax-highlight support\r\n- EndOfBuffer highlight (Vim 7.4.2213)","3":"- No more support for dark background\r\n- vim-nerdtree-syntax-highlight support\r\n- EndOfBuffer highlight (Vim 7.4.2213)","package":"grimmjow.vim","4":"grimmjow.vim","src_id":"24470","5":"24470","creation_date":"1472076636","6":"1472076636"},{"0":"5377","vim_version":"7.0","1":"7.0","script_version":"0.0.10","2":"0.0.10","version_comment":"Better colors for light theme and others minor changes","3":"Better colors for light theme and others minor changes","package":"grimmjow.vim","4":"grimmjow.vim","src_id":"24248","5":"24248","creation_date":"1463368412","6":"1463368412"},{"0":"5377","vim_version":"7.0","1":"7.0","script_version":"0.0.5","2":"0.0.5","version_comment":"Changes for the light background:\r\n- initial ruby support\r\n- better visual highlight\r\n- change ColorColumn to appear less","3":"Changes for the light background:\r\n- initial ruby support\r\n- better visual highlight\r\n- change ColorColumn to appear less","package":"grimmjow.vim","4":"grimmjow.vim","src_id":"24232","5":"24232","creation_date":"1462499855","6":"1462499855"},{"0":"5377","vim_version":"7.0","1":"7.0","script_version":"0.0.4","2":"0.0.4","version_comment":"Better background support and minor changes","3":"Better background support and minor changes","package":"grimmjow.vim","4":"grimmjow.vim","src_id":"24227","5":"24227","creation_date":"1462408672","6":"1462408672"},{"0":"5377","vim_version":"7.0","1":"7.0","script_version":"0.0.1","2":"0.0.1","version_comment":"Initial upload","3":"Initial upload","package":"grimmjow.vim","4":"grimmjow.vim","src_id":"24204","5":"24204","creation_date":"1461717219","6":"1461717219"}]},"5376":{"script_id":"5376","0":"5376","script_name":"Syntax match","1":"Syntax match","script_type":"utility","2":"utility","summary":"Saving syntax match rules to be loaded next time","3":"Saving syntax match rules to be loaded next time","description":"If you do log investigation it\u00e2\u0080\u0099s handy to differentiate identifiers with colors.\r\nWhen you close Vim and later open the log file again it\u00e2\u0080\u0099s fine to have preserved the colors.\r\n\r\nThis plugin offers functionality to save syntax match rules to an auxiliary file placed beside of file with the original content. Then the syntax highlighting can be restored when the file is opened later by loading from the auxiliary file.\r\n\r\nBeside of having capability to restore defined syntax match rules when specific files is opened again the plugin can solve trouble of saving multiple color highlight matches. The Vim match command (:match Comment \/pattern\/) provides only one pattern at a time. When using match again the previously highlighted text is decolorized. Sure there are commands 2match and 3match but it could not be enough - e.g. if you want to add highlighting dynamically for different regexp patterns (e.g. some identifiers in a log file).\r\n\r\nSee more at\r\nhttps:\/\/github.com\/ochaloup\/vim-syntax-match","4":"If you do log investigation it\u00e2\u0080\u0099s handy to differentiate identifiers with colors.\r\nWhen you close Vim and later open the log file again it\u00e2\u0080\u0099s fine to have preserved the colors.\r\n\r\nThis plugin offers functionality to save syntax match rules to an auxiliary file placed beside of file with the original content. Then the syntax highlighting can be restored when the file is opened later by loading from the auxiliary file.\r\n\r\nBeside of having capability to restore defined syntax match rules when specific files is opened again the plugin can solve trouble of saving multiple color highlight matches. The Vim match command (:match Comment \/pattern\/) provides only one pattern at a time. When using match again the previously highlighted text is decolorized. Sure there are commands 2match and 3match but it could not be enough - e.g. if you want to add highlighting dynamically for different regexp patterns (e.g. some identifiers in a log file).\r\n\r\nSee more at\r\nhttps:\/\/github.com\/ochaloup\/vim-syntax-match","install_details":"The easiest way to install is use pathogen plugin - see http:\/\/www.vim.org\/scripts\/script.php?script_id=2332\r\n\r\n    mkdir -p ~\/.vim\/autoload ~\/.vim\/bundle\r\n\r\n    curl -LSso ~\/.vim\/autoload\/pathogen.vim https:\/\/tpo.pe\/pathogen.vim\r\n\r\n    add line execute pathogen#infect() to your ~\/.vimrc file\r\n\r\nNow the installation of this plugin is easy\r\n\r\n    git clone git@github.com:ochaloup\/vim-syntax-match.git ~\/.vim\/bundle\/vim-syntax-match\r\n\r\n","5":"The easiest way to install is use pathogen plugin - see http:\/\/www.vim.org\/scripts\/script.php?script_id=2332\r\n\r\n    mkdir -p ~\/.vim\/autoload ~\/.vim\/bundle\r\n\r\n    curl -LSso ~\/.vim\/autoload\/pathogen.vim https:\/\/tpo.pe\/pathogen.vim\r\n\r\n    add line execute pathogen#infect() to your ~\/.vimrc file\r\n\r\nNow the installation of this plugin is easy\r\n\r\n    git clone git@github.com:ochaloup\/vim-syntax-match.git ~\/.vim\/bundle\/vim-syntax-match\r\n\r\n","first_name":"Ondrej","6":"Ondrej","last_name":"Chaloupka","7":"Chaloupka","releases":[{"0":"5376","vim_version":"7.0","1":"7.0","script_version":"0.2","2":"0.2","version_comment":"* adding foreground colors highlights (e.g. commands YF \/Yellowfg, GF \/Greenfg, ...)\r\n* adding function to call highlighting on all opened buffers (commands like :YA  (yellow highlight on all buffers), similarly then GA, BA, ...)\r\n* adding user command SCB which aliases call of windo scroll bind as scroll binding on all opened windows\r\n* adding command ClearAllSyntax which remove all syntax hightlighting from all opened buffers\r\n* adding a docker file for testing the plugin functionality","3":"* adding foreground colors highlights (e.g. commands YF \/Yellowfg, GF \/Greenfg, ...)\r\n* adding function to call highlighting on all opened buffers (commands like :YA  (yellow highlight on all buffers), similarly then GA, BA, ...)\r\n* adding user command SCB which aliases call of windo scroll bind as scroll binding on all opened windows\r\n* adding command ClearAllSyntax which remove all syntax hightlighting from all opened buffers\r\n* adding a docker file for testing the plugin functionality","package":"vim-syntax-match-0.2.zip","4":"vim-syntax-match-0.2.zip","src_id":"25959","5":"25959","creation_date":"1525304314","6":"1525304314"},{"0":"5376","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"vim-syntax-match-0.1.zip","4":"vim-syntax-match-0.1.zip","src_id":"24202","5":"24202","creation_date":"1461618218","6":"1461618218"}]},"5375":{"script_id":"5375","0":"5375","script_name":"vim-diction","1":"vim-diction","script_type":"utility","2":"utility","summary":"Write better with vim-diction - find frequently misused, bad or wordy diction","3":"Write better with vim-diction - find frequently misused, bad or wordy diction","description":"Diction, noun:\r\n\r\n    choice of words especially with regard to correctness, clearness, or effectiveness\r\n\r\nhttp:\/\/www.merriam-webster.com\/dictionary\/diction\r\n\r\nvim-diction parses databases, looks for bad diction and fills the\r\nquickfix or location list with explanations and suggestions on how to\r\nimprove the text.\r\n\r\nFor more information read the documentation `:h diction.txt`.\r\n\r\nScreenshot:\r\nhttps:\/\/cloud.githubusercontent.com\/assets\/10514301\/14812812\/2029fbb4-0b9f-11e6-8aac-4abe5223ad39.png\r\n","4":"Diction, noun:\r\n\r\n    choice of words especially with regard to correctness, clearness, or effectiveness\r\n\r\nhttp:\/\/www.merriam-webster.com\/dictionary\/diction\r\n\r\nvim-diction parses databases, looks for bad diction and fills the\r\nquickfix or location list with explanations and suggestions on how to\r\nimprove the text.\r\n\r\nFor more information read the documentation `:h diction.txt`.\r\n\r\nScreenshot:\r\nhttps:\/\/cloud.githubusercontent.com\/assets\/10514301\/14812812\/2029fbb4-0b9f-11e6-8aac-4abe5223ad39.png\r\n","install_details":"","5":"","first_name":"Nelo-T.","6":"Nelo-T.","last_name":"Wallus","7":"Wallus","releases":[{"0":"5375","vim_version":"7.0","1":"7.0","script_version":"4","2":"4","version_comment":"Version: 4\r\nAdd unit tests\r\nWorks over newlines in code comments\r\n\r\nTo Dos:\r\n* Allow ranges to check for bad diction\r\n","3":"Version: 4\r\nAdd unit tests\r\nWorks over newlines in code comments\r\n\r\nTo Dos:\r\n* Allow ranges to check for bad diction\r\n","package":"vim-diction-4.tar.gz","4":"vim-diction-4.tar.gz","src_id":"24219","5":"24219","creation_date":"1462117172","6":"1462117172"},{"0":"5375","vim_version":"7.0","1":"7.0","script_version":"3","2":"3","version_comment":"Version: 3\r\n\r\nMajor speed improvements (~8s on 400 lines down to less then half\r\na second) by using `searchpos()` instead of `match()`.\r\n\r\nUse a dictionary instead of a simple, global list, with a buflocal and\r\nglobal variable to define the active set of databases.\r\n\r\nNew Commands:\r\n* `DictionIndex`\r\n* `DictionAdd`\r\n* `LDictionAdd`\r\n* `DictionSet`\r\n\r\nNew Options:\r\n* `diction_open_window`\r\n* `diction_db_sets`\r\n* `diction_active_set`\r\n\r\nRemoved Options:\r\n* `diction_databases`\r\n\r\nTo Dos:\r\n* Allow ranges to check for bad diction","3":"Version: 3\r\n\r\nMajor speed improvements (~8s on 400 lines down to less then half\r\na second) by using `searchpos()` instead of `match()`.\r\n\r\nUse a dictionary instead of a simple, global list, with a buflocal and\r\nglobal variable to define the active set of databases.\r\n\r\nNew Commands:\r\n* `DictionIndex`\r\n* `DictionAdd`\r\n* `LDictionAdd`\r\n* `DictionSet`\r\n\r\nNew Options:\r\n* `diction_open_window`\r\n* `diction_db_sets`\r\n* `diction_active_set`\r\n\r\nRemoved Options:\r\n* `diction_databases`\r\n\r\nTo Dos:\r\n* Allow ranges to check for bad diction","package":"vim-diction-3.tar.gz","4":"vim-diction-3.tar.gz","src_id":"24213","5":"24213","creation_date":"1461915539","6":"1461915539"},{"0":"5375","vim_version":"7.0","1":"7.0","script_version":"2","2":"2","version_comment":"# Version: 2\r\nRewrite. Doesn't use `diction` anymore.\r\nUsing a similar database format (tsv) is simpler than parsing the output\r\nof diction and also enables vim-diction to ship with multiple databases\r\nby default.\r\n\r\n## New Commands:\r\n* `DictionLog`\r\n\r\n## New Options:\r\n* `diction_databases`\r\n\r\n## To Dos:\r\n* Allow ranges to check for bad diction\r\n* Command to add to existing qf\/loclist\r\n* Allow blacklisting shipped databases\r\n\r\n## Removed:\r\n* `diction_options`\r\n* `diction_suggest`\r\n","3":"# Version: 2\r\nRewrite. Doesn't use `diction` anymore.\r\nUsing a similar database format (tsv) is simpler than parsing the output\r\nof diction and also enables vim-diction to ship with multiple databases\r\nby default.\r\n\r\n## New Commands:\r\n* `DictionLog`\r\n\r\n## New Options:\r\n* `diction_databases`\r\n\r\n## To Dos:\r\n* Allow ranges to check for bad diction\r\n* Command to add to existing qf\/loclist\r\n* Allow blacklisting shipped databases\r\n\r\n## Removed:\r\n* `diction_options`\r\n* `diction_suggest`\r\n","package":"vim-diction.tar.gz","4":"vim-diction.tar.gz","src_id":"24203","5":"24203","creation_date":"1461667660","6":"1461667660"},{"0":"5375","vim_version":"7.0","1":"7.0","script_version":"1","2":"1","version_comment":"Initial upload","3":"Initial upload","package":"vim-diction.tar.gz","4":"vim-diction.tar.gz","src_id":"24198","5":"24198","creation_date":"1461464166","6":"1461464166"}]},"5374":{"script_id":"5374","0":"5374","script_name":"droWMark","1":"droWMark","script_type":"utility","2":"utility","summary":"Post to WordPress using Pandoc Flavoured Markdown","3":"Post to WordPress using Pandoc Flavoured Markdown","description":"droWMark creates WordPress posts accessing to WordPress' XML-RPC API. The posts are written using Pandoc Flavoured MarkDown and a simple configuration header in the top of the files.\r\n\r\nCcreate a new blog entry using:\r\n\r\n:NewWordPress\r\n\r\nThis will insert the template file in the file you are editing and switch the filetype to `drowmark` which automatically activates the `drowmark` syntax highlighting. This filetype is also activated when the extension of the file is `.wp`. The template contains all the information needed to fill the configuration part.\r\n\r\nWhen the blog entry is finished, it is possible to post in WordPress with the following command:\r\n\r\n:PostWordPress\r\n\r\nThis will ask for the username and the password before publishing the post in WordPress.","4":"droWMark creates WordPress posts accessing to WordPress' XML-RPC API. The posts are written using Pandoc Flavoured MarkDown and a simple configuration header in the top of the files.\r\n\r\nCcreate a new blog entry using:\r\n\r\n:NewWordPress\r\n\r\nThis will insert the template file in the file you are editing and switch the filetype to `drowmark` which automatically activates the `drowmark` syntax highlighting. This filetype is also activated when the extension of the file is `.wp`. The template contains all the information needed to fill the configuration part.\r\n\r\nWhen the blog entry is finished, it is possible to post in WordPress with the following command:\r\n\r\n:PostWordPress\r\n\r\nThis will ask for the username and the password before publishing the post in WordPress.","install_details":"It is necessary to have Vim compiled with `+python` option.\r\n\r\nDependencies for the python script are:\r\n\r\n- Panflute package, wich also depends on Pandoc  \r\n  pip install panflute\r\n\r\n- Wordpress XML RPC  \r\n  pip install python_wordpress_xmlrpc\r\n\r\n- ConfigParser package  \r\n  pip install configparser\r\n\r\nGet the latest version from GitHub:\r\nhttps:\/\/github.com\/ekaitz-zarraga\/droWMark\r\n\r\n# Version 1.1 update:\r\nNow depends on Panflute, not Pypandoc.","5":"It is necessary to have Vim compiled with `+python` option.\r\n\r\nDependencies for the python script are:\r\n\r\n- Panflute package, wich also depends on Pandoc  \r\n  pip install panflute\r\n\r\n- Wordpress XML RPC  \r\n  pip install python_wordpress_xmlrpc\r\n\r\n- ConfigParser package  \r\n  pip install configparser\r\n\r\nGet the latest version from GitHub:\r\nhttps:\/\/github.com\/ekaitz-zarraga\/droWMark\r\n\r\n# Version 1.1 update:\r\nNow depends on Panflute, not Pypandoc.","first_name":"Ekaitz","6":"Ekaitz","last_name":"Zarraga","7":"Zarraga","releases":[{"0":"5374","vim_version":"7.4","1":"7.4","script_version":"v1.1","2":"v1.1","version_comment":"Image support. Thumbnail Support.","3":"Image support. Thumbnail Support.","package":"droWMark-1.1.tar.gz","4":"droWMark-1.1.tar.gz","src_id":"24994","5":"24994","creation_date":"1487938400","6":"1487938400"},{"0":"5374","vim_version":"7.4","1":"7.4","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"droWMark-1.0.tar.gz","4":"droWMark-1.0.tar.gz","src_id":"24197","5":"24197","creation_date":"1461431738","6":"1461431738"}]},"5373":{"script_id":"5373","0":"5373","script_name":"Translate Vim","1":"Translate Vim","script_type":"utility","2":"utility","summary":"Translate text directly in vim from the google translate page.","3":"Translate text directly in vim from the google translate page.","description":"The Google_Translate_Py it is very usefully if you need to translate text inside vim.\r\nIt helps to improve your editing time without leaving vim. \r\nOnly select the text and press the key combination \\tt for your translation in whatever language google translate support.\r\nTry it, is very ease, simple and powerfully. \r\n\r\nIt is based in the python API:\r\n\r\nhttps:\/\/github.com\/mouuff\/Google-Translate-API\r\n\r\nPlease, the default languages are English (en) - Spanish (es)\r\n\r\nTo use another language [e.g. Italy (it)-German (de)] it is necessary to define the variables :\r\n\r\nlet g:google_translate_from_lang = \"it\"\r\nlet g:google_translate_to_lang = \"de\"\r\n\r\n\r\nTo change default shortcut keys ( \\tt ) use in your vimrc:\r\n\r\nmap pp :call g:TranslateGoogle()\r\n\r\nto \\pp for example.\r\n\r\n","4":"The Google_Translate_Py it is very usefully if you need to translate text inside vim.\r\nIt helps to improve your editing time without leaving vim. \r\nOnly select the text and press the key combination \\tt for your translation in whatever language google translate support.\r\nTry it, is very ease, simple and powerfully. \r\n\r\nIt is based in the python API:\r\n\r\nhttps:\/\/github.com\/mouuff\/Google-Translate-API\r\n\r\nPlease, the default languages are English (en) - Spanish (es)\r\n\r\nTo use another language [e.g. Italy (it)-German (de)] it is necessary to define the variables :\r\n\r\nlet g:google_translate_from_lang = \"it\"\r\nlet g:google_translate_to_lang = \"de\"\r\n\r\n\r\nTo change default shortcut keys ( \\tt ) use in your vimrc:\r\n\r\nmap pp :call g:TranslateGoogle()\r\n\r\nto \\pp for example.\r\n\r\n","install_details":"Extract the plugin files in your ~\/.vim (*nix) or ~\/vimfiles (Windows).\r\n","5":"Extract the plugin files in your ~\/.vim (*nix) or ~\/vimfiles (Windows).\r\n","first_name":"sr_x","6":"sr_x","last_name":"sr_x","7":"sr_x","releases":[{"0":"5373","vim_version":"9.0","1":"9.0","script_version":"2.0.0","2":"2.0.0","version_comment":"Updated to vim 9, and python3.","3":"Updated to vim 9, and python3.","package":"Google_Translate_Py.tar.gz","4":"Google_Translate_Py.tar.gz","src_id":"28189","5":"28189","creation_date":"1664010807","6":"1664010807"},{"0":"5373","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"Google_Translate_Py.tar.gz","4":"Google_Translate_Py.tar.gz","src_id":"24191","5":"24191","creation_date":"1461368632","6":"1461368632"}]},"5371":{"script_id":"5371","0":"5371","script_name":"extra-instant-markdown","1":"extra-instant-markdown","script_type":"utility","2":"utility","summary":"Instant Markdown previews from VIM!","3":"Instant Markdown previews from VIM!","description":"https:\/\/github.com\/NBUT-Developers\/extra-instant-markdown\r\n\r\nextra-instant-markdown is a fork of vim-instant-markdown.\r\n\r\nWant to instantly preview finnicky markdown files, but don't want to leave your favorite editor, or have to do it in some crappy browser textarea? vim-instant-markdown is your friend! When you open a markdown file in vim, a browser window will open which shows the compiled markdown in real-time, and closes once you close the file in vim.\r\n\r\nAs a bonus, github-flavored-markdown is supported, and styles used while previewing are the same as those github uses!","4":"https:\/\/github.com\/NBUT-Developers\/extra-instant-markdown\r\n\r\nextra-instant-markdown is a fork of vim-instant-markdown.\r\n\r\nWant to instantly preview finnicky markdown files, but don't want to leave your favorite editor, or have to do it in some crappy browser textarea? vim-instant-markdown is your friend! When you open a markdown file in vim, a browser window will open which shows the compiled markdown in real-time, and closes once you close the file in vim.\r\n\r\nAs a bonus, github-flavored-markdown is supported, and styles used while previewing are the same as those github uses!","install_details":"Installation\r\n\r\nYou first need to have node.js with npm installed.\r\n\r\n[sudo] npm -g install instant-markdown-x\r\nIf you're on Linux, the xdg-utils package needs to be installed (is installed by default on Ubuntu).\r\nUsing Vundle and add NBUT-Developers\/extra-instant-markdown.\r\nOpen a markdown file in vim and enjoy!\r\nConfiguration\r\n\r\ng:instant_markdown_slow\r\n\r\nBy default, extra-instant-markdown will update the display in realtime. If that taxes your system too much, you can specify\r\n\r\nlet g:instant_markdown_slow = 1\r\nbefore loading the plugin (for example place that in your ~\/.vimrc). This will cause extra-instant-markdown to only refresh on the following events:\r\n\r\nNo keys have been pressed for a while\r\nA while after you leave insert mode\r\nYou save the file being edited\r\ng:instant_markdown_autostart\r\n\r\nBy default, extra-instant-markdown will automatically launch the preview window when you open a markdown file. If you want to manually control this behavior, you can specify\r\n\r\nlet g:instant_markdown_autostart = 0\r\nin your .vimrc. You can then manually trigger preview via the command :InstantMarkdownPreview. This command is only available inside markdown buffers and when the autostart option is turned off.\r\n\r\nSupported Platforms\r\n\r\nOSX and Unix\/Linuxes*.\r\n\r\n*: One annoyance in Linux is that there's no way to reliably open a browser page in the background, so you'll likely have to manually refocus your vim session everytime you open a Markdown file. If you have ideas on how to address this I'd love to know!\r\n\r\nFAQ\r\n\r\nWhy don't my .md files trigger this plugin?\r\nBy default, vim (7.3 and above) only recognizes files ending with .markdown, .mdown, and README.md as markdown files. If you want .md to be recognized, I recommend installing one of many markdown plugins available, such as this one.\r\n\r\nIt's not working!\r\nMake sure instant-markdown-x was installed as a global module (e.g. using npm -g install)\r\nIf you're on OSX and are using zsh, try to add set shell=bash\\ -i in your .vimrc to set interactive bash as the default vim shell. (See this issue)\r\netc.\r\n\r\nIf you're curious, the code for the mini-server component for this plugin can be found at http:\/\/github.com\/suan\/instant-markdown-d. A plugin can easily be written for any editor to interface with the server to get the same functionality found here.","5":"Installation\r\n\r\nYou first need to have node.js with npm installed.\r\n\r\n[sudo] npm -g install instant-markdown-x\r\nIf you're on Linux, the xdg-utils package needs to be installed (is installed by default on Ubuntu).\r\nUsing Vundle and add NBUT-Developers\/extra-instant-markdown.\r\nOpen a markdown file in vim and enjoy!\r\nConfiguration\r\n\r\ng:instant_markdown_slow\r\n\r\nBy default, extra-instant-markdown will update the display in realtime. If that taxes your system too much, you can specify\r\n\r\nlet g:instant_markdown_slow = 1\r\nbefore loading the plugin (for example place that in your ~\/.vimrc). This will cause extra-instant-markdown to only refresh on the following events:\r\n\r\nNo keys have been pressed for a while\r\nA while after you leave insert mode\r\nYou save the file being edited\r\ng:instant_markdown_autostart\r\n\r\nBy default, extra-instant-markdown will automatically launch the preview window when you open a markdown file. If you want to manually control this behavior, you can specify\r\n\r\nlet g:instant_markdown_autostart = 0\r\nin your .vimrc. You can then manually trigger preview via the command :InstantMarkdownPreview. This command is only available inside markdown buffers and when the autostart option is turned off.\r\n\r\nSupported Platforms\r\n\r\nOSX and Unix\/Linuxes*.\r\n\r\n*: One annoyance in Linux is that there's no way to reliably open a browser page in the background, so you'll likely have to manually refocus your vim session everytime you open a Markdown file. If you have ideas on how to address this I'd love to know!\r\n\r\nFAQ\r\n\r\nWhy don't my .md files trigger this plugin?\r\nBy default, vim (7.3 and above) only recognizes files ending with .markdown, .mdown, and README.md as markdown files. If you want .md to be recognized, I recommend installing one of many markdown plugins available, such as this one.\r\n\r\nIt's not working!\r\nMake sure instant-markdown-x was installed as a global module (e.g. using npm -g install)\r\nIf you're on OSX and are using zsh, try to add set shell=bash\\ -i in your .vimrc to set interactive bash as the default vim shell. (See this issue)\r\netc.\r\n\r\nIf you're curious, the code for the mini-server component for this plugin can be found at http:\/\/github.com\/suan\/instant-markdown-d. A plugin can easily be written for any editor to interface with the server to get the same functionality found here.","first_name":"Chu","6":"Chu","last_name":"Khaidi","7":"Khaidi","releases":[{"0":"5371","vim_version":"7.4","1":"7.4","script_version":"0.1.0","2":"0.1.0","version_comment":"Initial upload","3":"Initial upload","package":"extra-instant-markdown-master.zip","4":"extra-instant-markdown-master.zip","src_id":"24185","5":"24185","creation_date":"1461059897","6":"1461059897"}]},"5370":{"script_id":"5370","0":"5370","script_name":"Vim-janitor","1":"Vim-janitor","script_type":"utility","2":"utility","summary":"Clean up multiple blank lines and trailing spaces.","3":"Clean up multiple blank lines and trailing spaces.","description":"Multiple empty lines and trailing white spaces cleaner for Vim. Vim-janitor supports both Vim and Neovim.\r\n\r\nDocument: http:\/\/kuoe0.github.io\/vim-janitor\/\r\nGithub: https:\/\/github.com\/KuoE0\/vim-janitor\/\r\n","4":"Multiple empty lines and trailing white spaces cleaner for Vim. Vim-janitor supports both Vim and Neovim.\r\n\r\nDocument: http:\/\/kuoe0.github.io\/vim-janitor\/\r\nGithub: https:\/\/github.com\/KuoE0\/vim-janitor\/\r\n","install_details":"","5":"","first_name":"Chih-Hsuan","6":"Chih-Hsuan","last_name":"Kuo","7":"Kuo","releases":[{"0":"5370","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"vim-scavenger.tar.gz","4":"vim-scavenger.tar.gz","src_id":"24184","5":"24184","creation_date":"1460974197","6":"1460974197"}]},"5367":{"script_id":"5367","0":"5367","script_name":"Outlaw","1":"Outlaw","script_type":"ftplugin","2":"ftplugin","summary":"The wanted outliner!","3":"The wanted outliner!","description":"Source code on Github: https:\/\/github.com\/lifepillar\/vim-outlaw\r\n\r\nHi, I am Outlaw, and I am wanted.\r\n\r\nI am wanted because I am an outliner, and although many outliners are already available for Vim, I am different. Striving for the same minimalist philosophy followed by plugins like Commentary, Dirvish or Sneak, I do not try to reinvent the wheel. The price on my head is about 250 LoC.\r\n\r\nHere is a very simple outline which you may start playing with:\r\n\r\n=== My biography\r\n    The secret of a long life is trying not to shorten it.\r\n    === Travel to the East\r\n        === The telegram\r\n            === Meeting with Nobody\r\n            === The bomb\r\n        === Searching for a brother\r\n            === The Wild Bunch\r\n\r\n=== Things to do\r\n    [x] Clean boots\r\n    [ ] Brush the horse\r\n        You may lead him to the water if you want, but don't\r\n        expect him to drink.\r\n    [ ] Wear the sheriff's badge\r\n\r\nI interpret lines starting with ===, [x], [-] or [ ], followed by a space, as topics. Each topic must be on a single line. The pattern defining a topic may be fully customized by setting g:outlaw_topic_mark, shouldn't you like my admittedly biased choice.\r\n\r\nIf you are the task-oriented kind of guy, you may prefer the TaskPaper format, rather than the above. I can't blame you. Just save your document with a .taskpaper suffix and I will format each topic as a project or task.\r\n\r\nWhatever patterns you adopt, topics may be indented to form a hierarchy or outline. I support up to nineteen levels (ten are highlighted by default, see g:outlaw_levels). I don't care whether 'expandtab' is set or not. You only need to set your preferred indentation level with g:outlaw_indent (if you don't define that variable in your vimrc I will use the current value of 'shiftwidth').\r\n\r\nFor me, everything that does not look like a topic (including blank lines) is body text (notes). I couldn't care less about the format or indentation of your notes (although I can help you aligning them with :OutlawAlignNotes): each block of body text always belongs to the topic immediately before it. But don't call it a son of a topic: you'd better think of body text as being at the same level as the topic it belongs to (it is possible to fold notes independently, though: see g:outlaw_note_fold_level and gy).\r\n\r\nNotes are just Normal text, but lines starting with > or | are highlighted (use > for quotations and | for verbatim text or code). Words preceded by @ are highlighted as tags anywhere. You may also use ~~~ or ``` tags to embed any configured filetype (see g:outlaw_fenced_filetypes). The delimiters may be changed, if you want (see g:outlaw_fenced_tag). Hyperlinks are highlighted, too.\r\n\r\nI let you jump over topics quickly: to the previous or next topic ( and ), to the previous or next sibling\/cousin ( and ), parent or uncle (- and +). Press  in Normal mode to quickly add a new sibling below the current topic, or  to add a new sibling above the current topic. Use  to make a new child.\r\n\r\nBesides, I help you move pieces of your outline around using the arrow keys in Visual mode (they accept a count, of course). Fix the indentation with the usual mappings (=, ==, \u00e2\u0080\u00a6) if necessary (your notes will be unaffected).\r\n\r\nFolding and unfolding are performed using Vim's default mappings and controlled using Vim's options (see :h fold-options). In addition, I provide gl to set the fold level according to the level of the current topic (so that all subtopics are closed), and g:outlaw_auto_close (toggled with gA) as a better suited alternative to setting 'foldclose'.\r\n\r\nThere's not much else you need to know about me. But if you want to know all the details, see :help outlaw.txt. Ah, I require Vim 7.4.984 or later.","4":"Source code on Github: https:\/\/github.com\/lifepillar\/vim-outlaw\r\n\r\nHi, I am Outlaw, and I am wanted.\r\n\r\nI am wanted because I am an outliner, and although many outliners are already available for Vim, I am different. Striving for the same minimalist philosophy followed by plugins like Commentary, Dirvish or Sneak, I do not try to reinvent the wheel. The price on my head is about 250 LoC.\r\n\r\nHere is a very simple outline which you may start playing with:\r\n\r\n=== My biography\r\n    The secret of a long life is trying not to shorten it.\r\n    === Travel to the East\r\n        === The telegram\r\n            === Meeting with Nobody\r\n            === The bomb\r\n        === Searching for a brother\r\n            === The Wild Bunch\r\n\r\n=== Things to do\r\n    [x] Clean boots\r\n    [ ] Brush the horse\r\n        You may lead him to the water if you want, but don't\r\n        expect him to drink.\r\n    [ ] Wear the sheriff's badge\r\n\r\nI interpret lines starting with ===, [x], [-] or [ ], followed by a space, as topics. Each topic must be on a single line. The pattern defining a topic may be fully customized by setting g:outlaw_topic_mark, shouldn't you like my admittedly biased choice.\r\n\r\nIf you are the task-oriented kind of guy, you may prefer the TaskPaper format, rather than the above. I can't blame you. Just save your document with a .taskpaper suffix and I will format each topic as a project or task.\r\n\r\nWhatever patterns you adopt, topics may be indented to form a hierarchy or outline. I support up to nineteen levels (ten are highlighted by default, see g:outlaw_levels). I don't care whether 'expandtab' is set or not. You only need to set your preferred indentation level with g:outlaw_indent (if you don't define that variable in your vimrc I will use the current value of 'shiftwidth').\r\n\r\nFor me, everything that does not look like a topic (including blank lines) is body text (notes). I couldn't care less about the format or indentation of your notes (although I can help you aligning them with :OutlawAlignNotes): each block of body text always belongs to the topic immediately before it. But don't call it a son of a topic: you'd better think of body text as being at the same level as the topic it belongs to (it is possible to fold notes independently, though: see g:outlaw_note_fold_level and gy).\r\n\r\nNotes are just Normal text, but lines starting with > or | are highlighted (use > for quotations and | for verbatim text or code). Words preceded by @ are highlighted as tags anywhere. You may also use ~~~ or ``` tags to embed any configured filetype (see g:outlaw_fenced_filetypes). The delimiters may be changed, if you want (see g:outlaw_fenced_tag). Hyperlinks are highlighted, too.\r\n\r\nI let you jump over topics quickly: to the previous or next topic ( and ), to the previous or next sibling\/cousin ( and ), parent or uncle (- and +). Press  in Normal mode to quickly add a new sibling below the current topic, or  to add a new sibling above the current topic. Use  to make a new child.\r\n\r\nBesides, I help you move pieces of your outline around using the arrow keys in Visual mode (they accept a count, of course). Fix the indentation with the usual mappings (=, ==, \u00e2\u0080\u00a6) if necessary (your notes will be unaffected).\r\n\r\nFolding and unfolding are performed using Vim's default mappings and controlled using Vim's options (see :h fold-options). In addition, I provide gl to set the fold level according to the level of the current topic (so that all subtopics are closed), and g:outlaw_auto_close (toggled with gA) as a better suited alternative to setting 'foldclose'.\r\n\r\nThere's not much else you need to know about me. But if you want to know all the details, see :help outlaw.txt. Ah, I require Vim 7.4.984 or later.","install_details":"","5":"","first_name":"","6":"","last_name":"Lifepillar","7":"Lifepillar","releases":[{"0":"5367","vim_version":"7.4","1":"7.4","script_version":"1.2.0","2":"1.2.0","version_comment":"License under the MIT license.","3":"License under the MIT license.","package":"vim-outlaw-v1.2.0.tar.gz","4":"vim-outlaw-v1.2.0.tar.gz","src_id":"27368","5":"27368","creation_date":"1605508627","6":"1605508627"},{"0":"5367","vim_version":"7.4","1":"7.4","script_version":"1.1.0","2":"1.1.0","version_comment":"The wanted outliner! New: 🎉 TaskPaper support 🎉! Other changes: improved highlighting (@tags, hyperlinks, quoted text, verbatim text, file paths), improved topic patterns, jumping across files, filetype detection, better documentation, and a lot of other minor fixes!","3":"The wanted outliner! New: 🎉 TaskPaper support 🎉! Other changes: improved highlighting (@tags, hyperlinks, quoted text, verbatim text, file paths), improved topic patterns, jumping across files, filetype detection, better documentation, and a lot of other minor fixes!","package":"vim-outlaw-1.1.0.tar.gz","4":"vim-outlaw-1.1.0.tar.gz","src_id":"27036","5":"27036","creation_date":"1582916739","6":"1582916739"},{"0":"5367","vim_version":"7.4","1":"7.4","script_version":"1.0.0","2":"1.0.0","version_comment":"Lots of changes since previous version, to make this plugin actually useful (but still minimal)!","3":"Lots of changes since previous version, to make this plugin actually useful (but still minimal)!","package":"vim-outlaw-1.0.0.tar.gz","4":"vim-outlaw-1.0.0.tar.gz","src_id":"24883","5":"24883","creation_date":"1483907573","6":"1483907573"},{"0":"5367","vim_version":"7.4","1":"7.4","script_version":"0.1.0","2":"0.1.0","version_comment":"Initial upload","3":"Initial upload","package":"v0.1.0.tar.gz","4":"v0.1.0.tar.gz","src_id":"24171","5":"24171","creation_date":"1460573593","6":"1460573593"}]},"5366":{"script_id":"5366","0":"5366","script_name":"apthogen","1":"apthogen","script_type":"utility","2":"utility","summary":"Easily manage your vim's plugins","3":"Easily manage your vim's plugins","description":"https:\/\/github.com\/vhalholl\/vim-apthogen#vim-apthogen","4":"https:\/\/github.com\/vhalholl\/vim-apthogen#vim-apthogen","install_details":"https:\/\/github.com\/vhalholl\/vim-apthogen#installation-","5":"https:\/\/github.com\/vhalholl\/vim-apthogen#installation-","first_name":"epp","6":"epp","last_name":"gregory","7":"gregory","releases":[{"0":"5366","vim_version":"7.0","1":"7.0","script_version":"2016.04","2":"2016.04","version_comment":"Initial upload","3":"Initial upload","package":"vim-apthogen-master.zip","4":"vim-apthogen-master.zip","src_id":"24170","5":"24170","creation_date":"1460456944","6":"1460456944"}]},"5365":{"script_id":"5365","0":"5365","script_name":"cpp-devel","1":"cpp-devel","script_type":"ftplugin","2":"ftplugin","summary":"Vim C++ development; This vim script (adopted from kde-devel-vim).","3":"Vim C++ development; This vim script (adopted from kde-devel-vim).","description":"I created this Vimscript (adopted from kde-devel-vim) for myself to be a more generic C++ helper script (not so KDE\/Qt specific). I want to give full credit to the original author(s) so I added a header in the script file with the original writeup and a link to the location where I found it.\r\n\r\nMy main goals for this script when I started modifying the original were to add:\r\n1. Maintenance free makeprog setup which supported \"out-of-source-builds\".\r\n2. Maintenance free tagfile creation.\r\n3. Help me stay consistent with my indent\/coding style (K&R-ish). The original had some formatting helpers and this was a big shortcut for me\r\n\r\nFunctionality provided by this script:\r\n* Automatic brace and parenthesis addition. Intelligence added to place braces on same line as if,while,do,etc.\r\n* Automatic space between keyword and paren addition.\r\n* Quick switching between header and impl file.\r\n* Intelligent includes additions. EG: Automatic #include  statement when cursor is on std::string statement.\r\n* Ability to add \"standard\" (to be overridden for personal or project stds) comment headers.\r\n* Change and TODO log entry helpers.\r\n* (un)comment line toggle. This feature also works with visual selection as well.\r\n* Intelligent directory searching to enable \"out-of-source-building\", like in the use of CMAKE.\r\n* Generic tab completion for braces, parenthesis and quotes. This feature is only meant for convinces, please use a mechanism like \"SnipMate\" for better tab completion.\r\n* Ability to align assignments in surrounding statements.\r\n* Automatic tagfile write for better project source code navigation.\r\n* Automatic 'path' setting for 'gf' command navigation.\r\n* Custom 'Make()' function\/command to support better out-of-source-building; this should build the project from any source code file in the project.","4":"I created this Vimscript (adopted from kde-devel-vim) for myself to be a more generic C++ helper script (not so KDE\/Qt specific). I want to give full credit to the original author(s) so I added a header in the script file with the original writeup and a link to the location where I found it.\r\n\r\nMy main goals for this script when I started modifying the original were to add:\r\n1. Maintenance free makeprog setup which supported \"out-of-source-builds\".\r\n2. Maintenance free tagfile creation.\r\n3. Help me stay consistent with my indent\/coding style (K&R-ish). The original had some formatting helpers and this was a big shortcut for me\r\n\r\nFunctionality provided by this script:\r\n* Automatic brace and parenthesis addition. Intelligence added to place braces on same line as if,while,do,etc.\r\n* Automatic space between keyword and paren addition.\r\n* Quick switching between header and impl file.\r\n* Intelligent includes additions. EG: Automatic #include  statement when cursor is on std::string statement.\r\n* Ability to add \"standard\" (to be overridden for personal or project stds) comment headers.\r\n* Change and TODO log entry helpers.\r\n* (un)comment line toggle. This feature also works with visual selection as well.\r\n* Intelligent directory searching to enable \"out-of-source-building\", like in the use of CMAKE.\r\n* Generic tab completion for braces, parenthesis and quotes. This feature is only meant for convinces, please use a mechanism like \"SnipMate\" for better tab completion.\r\n* Ability to align assignments in surrounding statements.\r\n* Automatic tagfile write for better project source code navigation.\r\n* Automatic 'path' setting for 'gf' command navigation.\r\n* Custom 'Make()' function\/command to support better out-of-source-building; this should build the project from any source code file in the project.","install_details":"If you don't have a preferred installation method, I recommend installing pathogen.vim, and then simply copy and paste:\r\n\r\ncd ~\/.vim\/bundle\r\ngit clone https:\/\/bitbucket.org\/JohnKaul\/cpp-devel-vim.git\r\nvim -u NONE -c \"helptags cpp-devel-vim\/doc\" -c q\r\n\r\nOtherwise you can always download from here and extract it manually (FYI: the cpp-devel-vim.vim file is supposed to be in your vim plugin directory).","5":"If you don't have a preferred installation method, I recommend installing pathogen.vim, and then simply copy and paste:\r\n\r\ncd ~\/.vim\/bundle\r\ngit clone https:\/\/bitbucket.org\/JohnKaul\/cpp-devel-vim.git\r\nvim -u NONE -c \"helptags cpp-devel-vim\/doc\" -c q\r\n\r\nOtherwise you can always download from here and extract it manually (FYI: the cpp-devel-vim.vim file is supposed to be in your vim plugin directory).","first_name":"John","6":"John","last_name":"Kaul","7":"Kaul","releases":[{"0":"5365","vim_version":"7.0","1":"7.0","script_version":"1.0.0","2":"1.0.0","version_comment":"Initial upload","3":"Initial upload","package":"cpp-devel-vim_v1.0.0.tar.gz","4":"cpp-devel-vim_v1.0.0.tar.gz","src_id":"24161","5":"24161","creation_date":"1460065415","6":"1460065415"}]},"5364":{"script_id":"5364","0":"5364","script_name":"vim-alias","1":"vim-alias","script_type":"utility","2":"utility","summary":"versatile vim-command line aliases","3":"versatile vim-command line aliases","description":"This plugin lets you define command-line abbreviations by `:Alias` which only expand at the beginning of the command prompt.\r\n\r\nYou can pass the optional parameters\r\n\r\n  -buffer  or  -range\r\n\r\nto create a buffer local alias or one that accepts a range preceding the\r\nalias.\r\n\r\nThese command line abbreviations work like the bash aliases, except that\r\nthe alias is substituted in-place.\r\n\r\n# Usage\r\n\r\n    :Alias [-range] [-buffer]  \r\n    :UnAlias  ...\r\n    :Aliases [ ...]\r\n\r\n## Examples:\r\n\r\n    :Alias   -range   dg   =&l:diff?\"diffget\":\"dg\"\r\n    :Alias   -buffer  spl  setlocal\\ spellsetlocal\\ spelllang=en\r\n    :Alias            w!!  write\\ !sudo\\ tee\\ >\\ \/dev\/null\\ %\r\n    :Alias            F    find\\ *=EatChar(\"\\ \")\r\n    :Alias            th   tab\\ help\r\n    :Alias            sft  setfiletype\r\n    :Alias            g    !git\r\n    :UnAlias          g\r\n    :Aliases\r\n\r\n  See :help abbreviations for Eatchar(c).\r\n\r\n## Persistent Aliases:\r\n\r\nTo define the Aliases after Vim has started up, put them in ~\/.vim\/after\/plugin\/alias.vim (on Linux) or %USERPROFILE%\/vimfiles\/after\/plugin\/alias.vim (on Microsoft Windows).\r\n\r\n# Configuration\r\n\r\nThe variable `g:cmdaliasCmdPrefixes` lists the patterns of all commands by\r\nwhich an alias command may be preceded and yet expand. It defaults to\r\n\r\n  let g:cmdaliasCmdPrefixes = [\r\n      \\ '\\d*verb\\%[ose]', 'debug', 'sil\\%[ent]!\\?', '\\%uns[ilent]' 'redir\\?!\\?',\r\n      \\ 'ld!\\?', '[cl]fd!\\?', '[cl]f\\?do!\\?',\r\n      \\ '\\%(\\%([.$]\\|\\d\\+\\)\\%([,;]\\%([.$]\\|\\d\\+\\)\\)*\\)\\?\\s*' .\r\n      \\ '\\%(argdo\\?!\\?\\|bufdo\\?!\\?\\|windo\\?\\|tabdo\\?\\)' ]\r\n\r\n# Development\r\n\r\nvim-alias is developed at\r\n\r\nhttps:\/\/github.com\/Konfekt\/vim-alias\r\n\r\nwhere issues can be filed.\r\n\r\n\r\n# Credits\r\n\r\nThis plugin builds and improves on cmdalias.vim 3. 0 by Hari Krishna Dara by\r\n\r\n- allowing for aliases of commands preceded by a range (like :Alias -range dg\r\n  diffget),\r\n- allowing for alias names ending in non-word chars (like :Alias w!! ...),\r\n- having a Vim documentation, and\r\n- more checks for proper usage, more consistent parameter parsing and a finer\r\n  check for blanks or commands (such as :  silent! ) preceding the alias.\r\n","4":"This plugin lets you define command-line abbreviations by `:Alias` which only expand at the beginning of the command prompt.\r\n\r\nYou can pass the optional parameters\r\n\r\n  -buffer  or  -range\r\n\r\nto create a buffer local alias or one that accepts a range preceding the\r\nalias.\r\n\r\nThese command line abbreviations work like the bash aliases, except that\r\nthe alias is substituted in-place.\r\n\r\n# Usage\r\n\r\n    :Alias [-range] [-buffer]  \r\n    :UnAlias  ...\r\n    :Aliases [ ...]\r\n\r\n## Examples:\r\n\r\n    :Alias   -range   dg   =&l:diff?\"diffget\":\"dg\"\r\n    :Alias   -buffer  spl  setlocal\\ spellsetlocal\\ spelllang=en\r\n    :Alias            w!!  write\\ !sudo\\ tee\\ >\\ \/dev\/null\\ %\r\n    :Alias            F    find\\ *=EatChar(\"\\ \")\r\n    :Alias            th   tab\\ help\r\n    :Alias            sft  setfiletype\r\n    :Alias            g    !git\r\n    :UnAlias          g\r\n    :Aliases\r\n\r\n  See :help abbreviations for Eatchar(c).\r\n\r\n## Persistent Aliases:\r\n\r\nTo define the Aliases after Vim has started up, put them in ~\/.vim\/after\/plugin\/alias.vim (on Linux) or %USERPROFILE%\/vimfiles\/after\/plugin\/alias.vim (on Microsoft Windows).\r\n\r\n# Configuration\r\n\r\nThe variable `g:cmdaliasCmdPrefixes` lists the patterns of all commands by\r\nwhich an alias command may be preceded and yet expand. It defaults to\r\n\r\n  let g:cmdaliasCmdPrefixes = [\r\n      \\ '\\d*verb\\%[ose]', 'debug', 'sil\\%[ent]!\\?', '\\%uns[ilent]' 'redir\\?!\\?',\r\n      \\ 'ld!\\?', '[cl]fd!\\?', '[cl]f\\?do!\\?',\r\n      \\ '\\%(\\%([.$]\\|\\d\\+\\)\\%([,;]\\%([.$]\\|\\d\\+\\)\\)*\\)\\?\\s*' .\r\n      \\ '\\%(argdo\\?!\\?\\|bufdo\\?!\\?\\|windo\\?\\|tabdo\\?\\)' ]\r\n\r\n# Development\r\n\r\nvim-alias is developed at\r\n\r\nhttps:\/\/github.com\/Konfekt\/vim-alias\r\n\r\nwhere issues can be filed.\r\n\r\n\r\n# Credits\r\n\r\nThis plugin builds and improves on cmdalias.vim 3. 0 by Hari Krishna Dara by\r\n\r\n- allowing for aliases of commands preceded by a range (like :Alias -range dg\r\n  diffget),\r\n- allowing for alias names ending in non-word chars (like :Alias w!! ...),\r\n- having a Vim documentation, and\r\n- more checks for proper usage, more consistent parameter parsing and a finer\r\n  check for blanks or commands (such as :  silent! ) preceding the alias.\r\n","install_details":"Unpack vim-alias into ~\/.vim on Linux or Mac and into %USERPROFILE%\/vimfiles on Microsoft Windows.","5":"Unpack vim-alias into ~\/.vim on Linux or Mac and into %USERPROFILE%\/vimfiles on Microsoft Windows.","first_name":"Enno","6":"Enno","last_name":"Nagel","7":"Nagel","releases":[{"0":"5364","vim_version":"6.0","1":"6.0","script_version":"1.7","2":"1.7","version_comment":"autoloadize","3":"autoloadize","package":"vim-alias.zip","4":"vim-alias.zip","src_id":"26746","5":"26746","creation_date":"1568411277","6":"1568411277"},{"0":"5364","vim_version":"6.0","1":"6.0","script_version":"1.6","2":"1.6","version_comment":"allow overriding alias, fix two errors","3":"allow overriding alias, fix two errors","package":"vim-alias.zip","4":"vim-alias.zip","src_id":"26730","5":"26730","creation_date":"1567739260","6":"1567739260"},{"0":"5364","vim_version":"6.0","1":"6.0","script_version":"1.5","2":"1.5","version_comment":"separate strictly between buffer-local and global aliases","3":"separate strictly between buffer-local and global aliases","package":"vim-alias.zip","4":"vim-alias.zip","src_id":"25971","5":"25971","creation_date":"1525923269","6":"1525923269"},{"0":"5364","vim_version":"7.0","1":"7.0","script_version":"1.4","2":"1.4","version_comment":"Handle Aliases that extend each other and end in non-word characters","3":"Handle Aliases that extend each other and end in non-word characters","package":"vim-alias.zip","4":"vim-alias.zip","src_id":"24701","5":"24701","creation_date":"1478100047","6":"1478100047"},{"0":"5364","vim_version":"7.0","1":"7.0","script_version":"1.2","2":"1.2","version_comment":"fix minor quirks","3":"fix minor quirks","package":"vim-alias.zip","4":"vim-alias.zip","src_id":"24323","5":"24323","creation_date":"1465820942","6":"1465820942"},{"0":"5364","vim_version":"7.0","1":"7.0","script_version":"1.1","2":"1.1","version_comment":"- secure alias names & expansions\r\n- extend doc\r\n- minor bug fix","3":"- secure alias names & expansions\r\n- extend doc\r\n- minor bug fix","package":"vim-alias.zip","4":"vim-alias.zip","src_id":"24164","5":"24164","creation_date":"1460235776","6":"1460235776"},{"0":"5364","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"vim-alias.zip","4":"vim-alias.zip","src_id":"24159","5":"24159","creation_date":"1459960287","6":"1459960287"}]},"5363":{"script_id":"5363","0":"5363","script_name":"you-debug-it","1":"you-debug-it","script_type":"utility","2":"utility","summary":" Vim plugin that helps to track your debug code","3":" Vim plugin that helps to track your debug code","description":"**you-debug-it** is a Vim plugin that helps to control your debug code.\r\n\r\nUsage\r\n-----\r\n\r\n##### Commands\r\n\r\n* `:YouDebugItStart`      - enables automatical insertion of comment tag into text\r\n* `:YouDebugItStop`       - disables automatical insertion of comment tag into text\r\n* `:YouDebugItClean`      - deletes all the lines containing the tag\r\n* `:YouDebugReviewStart`  - opens location list of tagged lines\r\n* `:YouDebugReviewFinish` - closes and clears location list of tagged lines\r\n\r\nContribution\r\n------------\r\n\r\nSource code and issues are hosted on GitHub:\r\n\r\n    https:\/\/github.com\/aserebryakov\/you-debug-it\r\n\r\nLicense\r\n-------\r\n\r\n[Apache License, Version 2.0](http:\/\/www.apache.org\/licenses\/LICENSE-2.0)","4":"**you-debug-it** is a Vim plugin that helps to control your debug code.\r\n\r\nUsage\r\n-----\r\n\r\n##### Commands\r\n\r\n* `:YouDebugItStart`      - enables automatical insertion of comment tag into text\r\n* `:YouDebugItStop`       - disables automatical insertion of comment tag into text\r\n* `:YouDebugItClean`      - deletes all the lines containing the tag\r\n* `:YouDebugReviewStart`  - opens location list of tagged lines\r\n* `:YouDebugReviewFinish` - closes and clears location list of tagged lines\r\n\r\nContribution\r\n------------\r\n\r\nSource code and issues are hosted on GitHub:\r\n\r\n    https:\/\/github.com\/aserebryakov\/you-debug-it\r\n\r\nLicense\r\n-------\r\n\r\n[Apache License, Version 2.0](http:\/\/www.apache.org\/licenses\/LICENSE-2.0)","install_details":"##### Pathogen\r\n\r\n    $ cd ~\/.vim\/bundle\r\n    $ git clone https:\/\/github.com\/aserebryakov\/you-debug-it.git\r\n\r\n##### NeoBundle\r\n\r\n    NeoBundle 'aserebryakov\/you-debug-it'\r\n\r\n##### Without plugin manager\r\n\r\nClone or download this repository and copy its contents to your `~\/.vim\/`\r\ndirectory.","5":"##### Pathogen\r\n\r\n    $ cd ~\/.vim\/bundle\r\n    $ git clone https:\/\/github.com\/aserebryakov\/you-debug-it.git\r\n\r\n##### NeoBundle\r\n\r\n    NeoBundle 'aserebryakov\/you-debug-it'\r\n\r\n##### Without plugin manager\r\n\r\nClone or download this repository and copy its contents to your `~\/.vim\/`\r\ndirectory.","first_name":"Alexander","6":"Alexander","last_name":"Serebryakov","7":"Serebryakov","releases":[{"0":"5363","vim_version":"7.4","1":"7.4","script_version":"1.0.0","2":"1.0.0","version_comment":"* Review functionality is implemented","3":"* Review functionality is implemented","package":"you-debug-it-1.0.0.zip","4":"you-debug-it-1.0.0.zip","src_id":"25063","5":"25063","creation_date":"1491061420","6":"1491061420"},{"0":"5363","vim_version":"7.4","1":"7.4","script_version":"0.2.2","2":"0.2.2","version_comment":"* Fixed error on `` pressing when buffer is changed after plugin enabling\r\n* Fixed error in case `YouDebugItStop` is executed before `YouDebugItStart`\r\n","3":"* Fixed error on `` pressing when buffer is changed after plugin enabling\r\n* Fixed error in case `YouDebugItStop` is executed before `YouDebugItStart`\r\n","package":"you-debug-it-0.2.2.zip","4":"you-debug-it-0.2.2.zip","src_id":"24235","5":"24235","creation_date":"1462555776","6":"1462555776"},{"0":"5363","vim_version":"7.4","1":"7.4","script_version":"0.2.1","2":"0.2.1","version_comment":"* Fixed `YouDebugItClean` command in case of `commentstring=\/*%s*\/`\r\n* Fixed error in case `YouDebugItClean` is executed before `YouDebugItStart`","3":"* Fixed `YouDebugItClean` command in case of `commentstring=\/*%s*\/`\r\n* Fixed error in case `YouDebugItClean` is executed before `YouDebugItStart`","package":"you-debug-it-0.2.1.zip","4":"you-debug-it-0.2.1.zip","src_id":"24226","5":"24226","creation_date":"1462391494","6":"1462391494"},{"0":"5363","vim_version":"7.4","1":"7.4","script_version":"0.2.0","2":"0.2.0","version_comment":"Added support for all languages where `commentstring` is defined","3":"Added support for all languages where `commentstring` is defined","package":"you-debug-it-you-debug-it-0.2.0.zip","4":"you-debug-it-you-debug-it-0.2.0.zip","src_id":"24224","5":"24224","creation_date":"1462307719","6":"1462307719"},{"0":"5363","vim_version":"7.4","1":"7.4","script_version":"0.1.0","2":"0.1.0","version_comment":"Initial upload","3":"Initial upload","package":"you-debug-it-you-debug-it-0.1.0.zip","4":"you-debug-it-you-debug-it-0.1.0.zip","src_id":"24154","5":"24154","creation_date":"1459628651","6":"1459628651"}]},"5362":{"script_id":"5362","0":"5362","script_name":"vim-shebang","1":"vim-shebang","script_type":"ftplugin","2":"ftplugin","summary":"Better filetype detection by the she\u00c2\u00b7bang line at file","3":"Better filetype detection by the she\u00c2\u00b7bang line at file","description":"Vim filetype detection by the she\u00c2\u00b7bang \/SHəˈbaNG\/ at file if all built-ins type\r\ndetection mechanisms are failed.\r\n\r\nUSE\r\n\r\nPlugin does not require any configuration. Every time you enter to buffer it\r\ntrying to detect current filetype by shebang at first line. New filetype applied\r\nto file on success. Use '!#' shortcut to force reset filetype.\r\n\r\nSome basic shebang patterns for common languages included in distribution, such\r\nas python, ruby, different shells. But if that do not covers your needs feel\r\nfree to add your own. For example:\r\n\r\nAddShebangPattern! lua ^#!.*\/bin\/env\\s\\+lua\\>","4":"Vim filetype detection by the she\u00c2\u00b7bang \/SHəˈbaNG\/ at file if all built-ins type\r\ndetection mechanisms are failed.\r\n\r\nUSE\r\n\r\nPlugin does not require any configuration. Every time you enter to buffer it\r\ntrying to detect current filetype by shebang at first line. New filetype applied\r\nto file on success. Use '!#' shortcut to force reset filetype.\r\n\r\nSome basic shebang patterns for common languages included in distribution, such\r\nas python, ruby, different shells. But if that do not covers your needs feel\r\nfree to add your own. For example:\r\n\r\nAddShebangPattern! lua ^#!.*\/bin\/env\\s\\+lua\\>","install_details":"Use your favorite installation method\r\n\r\nPlug 'vitalk\/vim-shebang'\r\nvim +PlugInstall\r\n\r\ncd ~\/.vim\/bundle\r\ngit clone https:\/\/github.com\/vitalk\/vim-shebang","5":"Use your favorite installation method\r\n\r\nPlug 'vitalk\/vim-shebang'\r\nvim +PlugInstall\r\n\r\ncd ~\/.vim\/bundle\r\ngit clone https:\/\/github.com\/vitalk\/vim-shebang","first_name":"Vital","6":"Vital","last_name":"Kudzelka","7":"Kudzelka","releases":[{"0":"5362","vim_version":"7.0","1":"7.0","script_version":"0.3","2":"0.3","version_comment":"Initial upload","3":"Initial upload","package":"vim-shebang-0.3.zip","4":"vim-shebang-0.3.zip","src_id":"24153","5":"24153","creation_date":"1459585596","6":"1459585596"}]},"5361":{"script_id":"5361","0":"5361","script_name":"expresso.vim","1":"expresso.vim","script_type":"utility","2":"utility","summary":"Evaluate text as a math expression","3":"Evaluate text as a math expression","description":"Evaluate text as a math expression and replace it with the result.","4":"Evaluate text as a math expression and replace it with the result.","install_details":"","5":"","first_name":"Michael","6":"Michael","last_name":"Foley","7":"Foley","releases":[{"0":"5361","vim_version":"5.7","1":"5.7","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"vim-expresso.zip","4":"vim-expresso.zip","src_id":"24150","5":"24150","creation_date":"1459379931","6":"1459379931"}]},"5360":{"script_id":"5360","0":"5360","script_name":"Pinnacle","1":"Pinnacle","script_type":"utility","2":"utility","summary":"Highlight group manipulation for Vim","3":"Highlight group manipulation for Vim","description":"*pinnacle.txt*           Highlight group manipulation for Vim           *pinnacle*\r\n\r\nCONTENTS                                                     *pinnacle-contents*\r\n\r\n1. Intro             |pinnacle-intro|\r\n2. Installation      |pinnacle-installation|\r\n3. Functions         |pinnacle-functions|\r\n4. Website           |pinnacle-website|\r\n5. License           |pinnacle-license|\r\n6. Development       |pinnacle-development|\r\n7. Authors           |pinnacle-authors|\r\n8. History           |pinnacle-history|\r\n\r\nINTRO                                                           *pinnacle-intro*\r\n\r\nPinnacle provides functions for manipulating |:highlight| groups.\r\n\r\nINSTALLATION                                             *pinnacle-installation*\r\n\r\nTo install Pinnacle, use your plug-in management system of choice.\r\n\r\nIf you don't have a \"plug-in management system of choice\", I recommend\r\nPathogen (https:\/\/github.com\/tpope\/vim-pathogen) due to its simplicity and\r\nrobustness. Assuming that you have Pathogen installed and configured, and\r\nthat you want to install Pinnacle into `~\/.vim\/bundle`, you can do so with:\r\n>\r\n    git clone https:\/\/github.com\/wincent\/pinnacle.git ~\/.vim\/bundle\/pinnacle\r\n<\r\nAlternatively, if you use a Git submodule for each Vim plug-in, you could do\r\nthe following after `cd`-ing into the top-level of your Git superproject:\r\n>\r\n    git submodule add https:\/\/github.com\/wincent\/pinnacle.git ~\/vim\/bundle\/pinnacle\r\n    git submodule init\r\n<\r\nTo generate help tags under Pathogen, you can do so from inside Vim with:\r\n>\r\n    :call pathogen#helptags()\r\n<\r\nFUNCTIONS                                                   *pinnacle-functions*\r\n\r\n                                                       *pinnacle#sub_newlines()*\r\npinnacle#sub_newlines() ~\r\n\r\nReplaces newlines with spaces.\r\n\r\n                                                      *pinnacle#capturel_line()*\r\npinnacle#capturel_line() ~\r\n\r\nRuns a command and returns the captured output as a single line.\r\n\r\nUseful when we don't want to let long lines on narrow windows produce\r\nunwanted embedded newlines.\r\n\r\n                                                  *pinnacle#capture_highlight()*\r\npinnacle#capture_highlight() ~\r\n\r\nGets the current value of a highlight group.\r\n\r\n                                                  *pinnacle#extract_highlight()*\r\npinnacle#extract_highlight() ~\r\n\r\nExtracts a highlight string from a group, recursively traversing linked\r\ngroups, and returns a string suitable for passing to `:highlight`.\r\n\r\n                                                         *pinnacle#extract_bg()*\r\npinnacle#extract_bg() ~\r\n\r\nExtracts just the bg portion of the specified highlight group.\r\n\r\n                                                         *pinnacle#extract_fg()*\r\npinnacle#extract_fg() ~\r\n\r\nExtracts just the bg portion of the specified highlight group.\r\n\r\n                                                  *pinnacle#extract_component()*\r\npinnacle#extract_component() ~\r\n\r\nExtracts a single component (eg. \"bg\", \"fg\", \"italic\" etc) from the\r\nspecified highlight group.\r\n\r\n                                                               *pinnacle#dump()*\r\npinnacle#dump() ~\r\n\r\nReturns a dictionary representation of the specified highlight group.\r\n\r\n                                                          *pinnacle#highlight()*\r\npinnacle#highlight() ~\r\n\r\nReturns a string representation of a dictionary containing bg, fg, term,\r\ncterm and guiterm entries.\r\n\r\n                                                          *pinnacle#italicize()*\r\npinnacle#italicize() ~\r\n\r\nReturns an italicized copy of `group` suitable for passing to `:highlight`.\r\n\r\n                                                           *pinnacle#embolden()*\r\npinnacle#embolden() ~\r\n\r\nReturns a bold copy of `group` suitable for passing to `:highlight`.\r\n\r\n                                                          *pinnacle#underline()*\r\npinnacle#underline() ~\r\n\r\nReturns an underlined copy of `group` suitable for passing to `:highlight`.\r\n\r\n                                                           *pinnacle#decorate()*\r\npinnacle#decorate() ~\r\n\r\nReturns a copy of `group` decorated with `style` (eg. \"bold\", \"italic\" etc)\r\nsuitable for passing to `:highlight`.\r\n\r\nWEBSITE                                                       *pinnacle-website*\r\n\r\nThe official Pinnacle source code repo is at:\r\n\r\nhttp:\/\/git.wincent.com\/pinnacle.git\r\n\r\nMirrors exist at:\r\n\r\n- https:\/\/github.com\/wincent\/pinnacle\r\n- https:\/\/gitlab.com\/wincent\/pinnacle\r\n- https:\/\/bitbucket.org\/ghurrell\/pinnacle\r\n\r\nOfficial releases are listed at:\r\n\r\nhttp:\/\/www.vim.org\/scripts\/script.php?script_id=5360\r\n\r\nLICENSE                                                       *pinnacle-license*\r\n\r\nCopyright (c) 2016-present Greg Hurrell\r\n\r\nPermission is hereby granted, free of charge, to any person obtaining a copy\r\nof this software and associated documentation files (the \"Software\"), to\r\ndeal in the Software without restriction, including without limitation the\r\nrights to use, copy, modify, merge, publish, distribute, sublicense, and\/or\r\nsell copies of the Software, and to permit persons to whom the Software is\r\nfurnished to do so, subject to the following conditions:\r\n\r\nThe above copyright notice and this permission notice shall be included in\r\nall copies or substantial portions of the Software.\r\n\r\nTHE SOFTWARE IS PROVIDED \"AS IS\", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR\r\nIMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,\r\nFITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE\r\nAUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER\r\nLIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING\r\nFROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS\r\nIN THE SOFTWARE.\r\n\r\nDEVELOPMENT                                               *pinnacle-development*\r\n\r\nContributing patches ~\r\n\r\nPatches can be sent via mail to greg@hurrell.net, or as GitHub pull requests\r\nat: https:\/\/github.com\/wincent\/pinnacle\/pulls\r\n\r\nCutting a new release ~\r\n\r\nAt the moment the release process is manual:\r\n\r\n- Perform final sanity checks and manual testing\r\n- Update the |pinnacle-history| section of the documentation\r\n- Verify clean work tree:\r\n>\r\n    git status\r\n<\r\n- Tag the release:\r\n>\r\n    git tag -s -m \"$VERSION release\" $VERSION\r\n<\r\n- Publish the code:\r\n>\r\n    git push origin master --follow-tags\r\n    git push github master --follow-tags\r\n<\r\n- Produce the release archive:\r\n>\r\n    git archive -o pinnacle-$VERSION.zip HEAD -- .\r\n<\r\n- Upload to http:\/\/www.vim.org\/scripts\/script.php?script_id=5360\r\n\r\nAUTHORS                                                       *pinnacle-authors*\r\n\r\nPinnacle is written and maintained by Greg Hurrell .\r\n\r\nOther contributors that have submitted patches include (in alphabetical\r\norder):\r\n\r\n- Cody Buell\r\n- Kyle Poole\r\n","4":"*pinnacle.txt*           Highlight group manipulation for Vim           *pinnacle*\r\n\r\nCONTENTS                                                     *pinnacle-contents*\r\n\r\n1. Intro             |pinnacle-intro|\r\n2. Installation      |pinnacle-installation|\r\n3. Functions         |pinnacle-functions|\r\n4. Website           |pinnacle-website|\r\n5. License           |pinnacle-license|\r\n6. Development       |pinnacle-development|\r\n7. Authors           |pinnacle-authors|\r\n8. History           |pinnacle-history|\r\n\r\nINTRO                                                           *pinnacle-intro*\r\n\r\nPinnacle provides functions for manipulating |:highlight| groups.\r\n\r\nINSTALLATION                                             *pinnacle-installation*\r\n\r\nTo install Pinnacle, use your plug-in management system of choice.\r\n\r\nIf you don't have a \"plug-in management system of choice\", I recommend\r\nPathogen (https:\/\/github.com\/tpope\/vim-pathogen) due to its simplicity and\r\nrobustness. Assuming that you have Pathogen installed and configured, and\r\nthat you want to install Pinnacle into `~\/.vim\/bundle`, you can do so with:\r\n>\r\n    git clone https:\/\/github.com\/wincent\/pinnacle.git ~\/.vim\/bundle\/pinnacle\r\n<\r\nAlternatively, if you use a Git submodule for each Vim plug-in, you could do\r\nthe following after `cd`-ing into the top-level of your Git superproject:\r\n>\r\n    git submodule add https:\/\/github.com\/wincent\/pinnacle.git ~\/vim\/bundle\/pinnacle\r\n    git submodule init\r\n<\r\nTo generate help tags under Pathogen, you can do so from inside Vim with:\r\n>\r\n    :call pathogen#helptags()\r\n<\r\nFUNCTIONS                                                   *pinnacle-functions*\r\n\r\n                                                       *pinnacle#sub_newlines()*\r\npinnacle#sub_newlines() ~\r\n\r\nReplaces newlines with spaces.\r\n\r\n                                                      *pinnacle#capturel_line()*\r\npinnacle#capturel_line() ~\r\n\r\nRuns a command and returns the captured output as a single line.\r\n\r\nUseful when we don't want to let long lines on narrow windows produce\r\nunwanted embedded newlines.\r\n\r\n                                                  *pinnacle#capture_highlight()*\r\npinnacle#capture_highlight() ~\r\n\r\nGets the current value of a highlight group.\r\n\r\n                                                  *pinnacle#extract_highlight()*\r\npinnacle#extract_highlight() ~\r\n\r\nExtracts a highlight string from a group, recursively traversing linked\r\ngroups, and returns a string suitable for passing to `:highlight`.\r\n\r\n                                                         *pinnacle#extract_bg()*\r\npinnacle#extract_bg() ~\r\n\r\nExtracts just the bg portion of the specified highlight group.\r\n\r\n                                                         *pinnacle#extract_fg()*\r\npinnacle#extract_fg() ~\r\n\r\nExtracts just the bg portion of the specified highlight group.\r\n\r\n                                                  *pinnacle#extract_component()*\r\npinnacle#extract_component() ~\r\n\r\nExtracts a single component (eg. \"bg\", \"fg\", \"italic\" etc) from the\r\nspecified highlight group.\r\n\r\n                                                               *pinnacle#dump()*\r\npinnacle#dump() ~\r\n\r\nReturns a dictionary representation of the specified highlight group.\r\n\r\n                                                          *pinnacle#highlight()*\r\npinnacle#highlight() ~\r\n\r\nReturns a string representation of a dictionary containing bg, fg, term,\r\ncterm and guiterm entries.\r\n\r\n                                                          *pinnacle#italicize()*\r\npinnacle#italicize() ~\r\n\r\nReturns an italicized copy of `group` suitable for passing to `:highlight`.\r\n\r\n                                                           *pinnacle#embolden()*\r\npinnacle#embolden() ~\r\n\r\nReturns a bold copy of `group` suitable for passing to `:highlight`.\r\n\r\n                                                          *pinnacle#underline()*\r\npinnacle#underline() ~\r\n\r\nReturns an underlined copy of `group` suitable for passing to `:highlight`.\r\n\r\n                                                           *pinnacle#decorate()*\r\npinnacle#decorate() ~\r\n\r\nReturns a copy of `group` decorated with `style` (eg. \"bold\", \"italic\" etc)\r\nsuitable for passing to `:highlight`.\r\n\r\nWEBSITE                                                       *pinnacle-website*\r\n\r\nThe official Pinnacle source code repo is at:\r\n\r\nhttp:\/\/git.wincent.com\/pinnacle.git\r\n\r\nMirrors exist at:\r\n\r\n- https:\/\/github.com\/wincent\/pinnacle\r\n- https:\/\/gitlab.com\/wincent\/pinnacle\r\n- https:\/\/bitbucket.org\/ghurrell\/pinnacle\r\n\r\nOfficial releases are listed at:\r\n\r\nhttp:\/\/www.vim.org\/scripts\/script.php?script_id=5360\r\n\r\nLICENSE                                                       *pinnacle-license*\r\n\r\nCopyright (c) 2016-present Greg Hurrell\r\n\r\nPermission is hereby granted, free of charge, to any person obtaining a copy\r\nof this software and associated documentation files (the \"Software\"), to\r\ndeal in the Software without restriction, including without limitation the\r\nrights to use, copy, modify, merge, publish, distribute, sublicense, and\/or\r\nsell copies of the Software, and to permit persons to whom the Software is\r\nfurnished to do so, subject to the following conditions:\r\n\r\nThe above copyright notice and this permission notice shall be included in\r\nall copies or substantial portions of the Software.\r\n\r\nTHE SOFTWARE IS PROVIDED \"AS IS\", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR\r\nIMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,\r\nFITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE\r\nAUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER\r\nLIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING\r\nFROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS\r\nIN THE SOFTWARE.\r\n\r\nDEVELOPMENT                                               *pinnacle-development*\r\n\r\nContributing patches ~\r\n\r\nPatches can be sent via mail to greg@hurrell.net, or as GitHub pull requests\r\nat: https:\/\/github.com\/wincent\/pinnacle\/pulls\r\n\r\nCutting a new release ~\r\n\r\nAt the moment the release process is manual:\r\n\r\n- Perform final sanity checks and manual testing\r\n- Update the |pinnacle-history| section of the documentation\r\n- Verify clean work tree:\r\n>\r\n    git status\r\n<\r\n- Tag the release:\r\n>\r\n    git tag -s -m \"$VERSION release\" $VERSION\r\n<\r\n- Publish the code:\r\n>\r\n    git push origin master --follow-tags\r\n    git push github master --follow-tags\r\n<\r\n- Produce the release archive:\r\n>\r\n    git archive -o pinnacle-$VERSION.zip HEAD -- .\r\n<\r\n- Upload to http:\/\/www.vim.org\/scripts\/script.php?script_id=5360\r\n\r\nAUTHORS                                                       *pinnacle-authors*\r\n\r\nPinnacle is written and maintained by Greg Hurrell .\r\n\r\nOther contributors that have submitted patches include (in alphabetical\r\norder):\r\n\r\n- Cody Buell\r\n- Kyle Poole\r\n","install_details":"","5":"","first_name":"Greg","6":"Greg","last_name":"Hurrell","7":"Hurrell","releases":[{"0":"5360","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"- Added `pinnacle#dump()`.","3":"- Added `pinnacle#dump()`.","package":"pinnacle-1.0.zip","4":"pinnacle-1.0.zip","src_id":"26410","5":"26410","creation_date":"1551902493","6":"1551902493"},{"0":"5360","vim_version":"7.0","1":"7.0","script_version":"0.3.1","2":"0.3.1","version_comment":"- Fix another bug with augmentation of existing highlights.","3":"- Fix another bug with augmentation of existing highlights.","package":"pinnacle-0.3.1.zip","4":"pinnacle-0.3.1.zip","src_id":"25291","5":"25291","creation_date":"1496886536","6":"1496886536"},{"0":"5360","vim_version":"7.0","1":"7.0","script_version":"0.3","2":"0.3","version_comment":"- Added `pinnacle#extract_bg` and `pinnacle#extract_fg`.\r\n- Fixed bug that could cause existing highlights to be incorrectly augmented.","3":"- Added `pinnacle#extract_bg` and `pinnacle#extract_fg`.\r\n- Fixed bug that could cause existing highlights to be incorrectly augmented.","package":"pinnacle-0.3.zip","4":"pinnacle-0.3.zip","src_id":"25287","5":"25287","creation_date":"1496807146","6":"1496807146"},{"0":"5360","vim_version":"7.0","1":"7.0","script_version":"0.2","2":"0.2","version_comment":"- Added `pinnacle#underline`.","3":"- Added `pinnacle#underline`.","package":"pinnacle-0.2.zip","4":"pinnacle-0.2.zip","src_id":"24885","5":"24885","creation_date":"1483929525","6":"1483929525"},{"0":"5360","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"pinnacle-0.1.zip","4":"pinnacle-0.1.zip","src_id":"24149","5":"24149","creation_date":"1459361857","6":"1459361857"}]},"5359":{"script_id":"5359","0":"5359","script_name":"vim-hdl","1":"vim-hdl","script_type":"utility","2":"utility","summary":"Vim plugin to aid VHDL development","3":"Vim plugin to aid VHDL development","description":"vim-hdl is a Vim plugin that uses hdlcc (https:\/\/github.com\/suoto\/hdlcc) to provide some helpers to VHDL development\r\n\r\n- Syntax checking using third-party-compilers + Syntastic (see https:\/\/github.com\/scrooloose\/syntastic)\r\n- Style checking\r\n\r\nSupported third-party compilers\r\n\r\n- Mentor Graphics\u00c2\u00ae ModelSim\u00c2\u00ae\r\n- ModelSim-Altera\u00c2\u00ae Edition\r\n- GHDL\r\n\r\nStyle checking\r\n\r\n- Signal names in lower case\r\n- Constants and generics in upper case\r\n- Unused signals, constants, generics, shared variables, libraries, types and attributes\r\n- Comment tags (FIXME, TODO, XXX)\r\n\r\nRequirements:\r\n- Requires Vim compiled with Python support, plus features needed by Syntastic itself\r\n- Only Vim 7.4+ are currently tested and supported\r\n\r\nYou can clone https:\/\/github.com\/suoto\/vim-hdl for the latest version.","4":"vim-hdl is a Vim plugin that uses hdlcc (https:\/\/github.com\/suoto\/hdlcc) to provide some helpers to VHDL development\r\n\r\n- Syntax checking using third-party-compilers + Syntastic (see https:\/\/github.com\/scrooloose\/syntastic)\r\n- Style checking\r\n\r\nSupported third-party compilers\r\n\r\n- Mentor Graphics\u00c2\u00ae ModelSim\u00c2\u00ae\r\n- ModelSim-Altera\u00c2\u00ae Edition\r\n- GHDL\r\n\r\nStyle checking\r\n\r\n- Signal names in lower case\r\n- Constants and generics in upper case\r\n- Unused signals, constants, generics, shared variables, libraries, types and attributes\r\n- Comment tags (FIXME, TODO, XXX)\r\n\r\nRequirements:\r\n- Requires Vim compiled with Python support, plus features needed by Syntastic itself\r\n- Only Vim 7.4+ are currently tested and supported\r\n\r\nYou can clone https:\/\/github.com\/suoto\/vim-hdl for the latest version.","install_details":"- Vim.org\r\nExtract the tar.gz file into $VIM\/bundle\r\n- Pathogen\r\n    cd ~\/.vim\/bundle\/\r\n    git clone --recursive https:\/\/github.com\/suoto\/vim-hdl.git\r\n- Vundle\r\n    Add to your vimrc:\r\n    Plugin 'suoto\/vim-hdl'","5":"- Vim.org\r\nExtract the tar.gz file into $VIM\/bundle\r\n- Pathogen\r\n    cd ~\/.vim\/bundle\/\r\n    git clone --recursive https:\/\/github.com\/suoto\/vim-hdl.git\r\n- Vundle\r\n    Add to your vimrc:\r\n    Plugin 'suoto\/vim-hdl'","first_name":"Andre","6":"Andre","last_name":"Souto","7":"Souto","releases":[{"0":"5359","vim_version":"7.4","1":"7.4","script_version":"0.1.0","2":"0.1.0","version_comment":"Initial upload","3":"Initial upload","package":"vim-hdl.tar.gz","4":"vim-hdl.tar.gz","src_id":"24148","5":"24148","creation_date":"1459353378","6":"1459353378"}]},"5358":{"script_id":"5358","0":"5358","script_name":"pgsql","1":"pgsql","script_type":"ftplugin","2":"ftplugin","summary":"The best PostgreSQL plugin for Vim!","3":"The best PostgreSQL plugin for Vim!","description":"This plugin provides syntax highlighting and auto-completion support for PostgreSQL and for some of its extensions, including PL\/pgSQL, PostGIS, pgTap, and many others. Integrates with Vim built-in support for SQL rather than reinventing the wheel. Supports embedded syntax highlighting for any language inside SQL user-defined functions. \r\n\r\nSource code available on GitHub: https:\/\/github.com\/lifepillar\/pgsql.vim","4":"This plugin provides syntax highlighting and auto-completion support for PostgreSQL and for some of its extensions, including PL\/pgSQL, PostGIS, pgTap, and many others. Integrates with Vim built-in support for SQL rather than reinventing the wheel. Supports embedded syntax highlighting for any language inside SQL user-defined functions. \r\n\r\nSource code available on GitHub: https:\/\/github.com\/lifepillar\/pgsql.vim","install_details":"If your Vim supports packages (echo has('packages') prints 1), I strongly recommend that you use them. Just clone this repo inside pack\/*\/start, e.g.,\r\n\r\n  cd ~\/.vim\r\n  git clone https:\/\/github.com\/lifepillar\/pgsql.vim.git pack\/bundle\/start\/pgsql\r\n\r\nOtherwise, if you don't have a preferred installation method, I recommend installing Pathogen, and then simply copy and paste:\r\n\r\n  cd ~\/.vim\/bundle\r\n  git clone https:\/\/github.com\/lifepillar\/pgsql.vim.git","5":"If your Vim supports packages (echo has('packages') prints 1), I strongly recommend that you use them. Just clone this repo inside pack\/*\/start, e.g.,\r\n\r\n  cd ~\/.vim\r\n  git clone https:\/\/github.com\/lifepillar\/pgsql.vim.git pack\/bundle\/start\/pgsql\r\n\r\nOtherwise, if you don't have a preferred installation method, I recommend installing Pathogen, and then simply copy and paste:\r\n\r\n  cd ~\/.vim\/bundle\r\n  git clone https:\/\/github.com\/lifepillar\/pgsql.vim.git","first_name":"","6":"","last_name":"Lifepillar","7":"Lifepillar","releases":[{"0":"5358","vim_version":"7.4","1":"7.4","script_version":"2.3.0","2":"2.3.0","version_comment":"Upgrade for PostgreSQL 13.0. License under Vim license.","3":"Upgrade for PostgreSQL 13.0. License under Vim license.","package":"pgsql.vim-2.3.0.tar.gz","4":"pgsql.vim-2.3.0.tar.gz","src_id":"27367","5":"27367","creation_date":"1605508255","6":"1605508255"},{"0":"5358","vim_version":"7.0","1":"7.0","script_version":"2.1.2","2":"2.1.2","version_comment":"Do not treat backslash as escape char in strings and identifiers. Update tests.","3":"Do not treat backslash as escape char in strings and identifiers. Update tests.","package":"pgsql.vim-2.1.2.tar.gz","4":"pgsql.vim-2.1.2.tar.gz","src_id":"26169","5":"26169","creation_date":"1533428364","6":"1533428364"},{"0":"5358","vim_version":"7.0","1":"7.0","script_version":"2.1.1","2":"2.1.1","version_comment":"Updated for PostgreSQL 10.4.","3":"Updated for PostgreSQL 10.4.","package":"pgsql.vim-2.1.1.tar.gz","4":"pgsql.vim-2.1.1.tar.gz","src_id":"25984","5":"25984","creation_date":"1526839988","6":"1526839988"},{"0":"5358","vim_version":"7.0","1":"7.0","script_version":"2.1.0","2":"2.1.0","version_comment":"Update syntax coloring of data types. Updated for PostgreSQL 10.1.","3":"Update syntax coloring of data types. Updated for PostgreSQL 10.1.","package":"pgsql.vim-2.1.0.tar.gz","4":"pgsql.vim-2.1.0.tar.gz","src_id":"25793","5":"25793","creation_date":"1516554334","6":"1516554334"},{"0":"5358","vim_version":"7.0","1":"7.0","script_version":"2.0.0","2":"2.0.0","version_comment":"Syntax file is now generated automatically from a SQL script, so you won't miss a keyword! And you may rebuild it yourself against your PostgreSQL version! Several other small improvements, e.g., better support for psql commands.","3":"Syntax file is now generated automatically from a SQL script, so you won't miss a keyword! And you may rebuild it yourself against your PostgreSQL version! Several other small improvements, e.g., better support for psql commands.","package":"pgsql.vim-2.0.0.tar.gz","4":"pgsql.vim-2.0.0.tar.gz","src_id":"25438","5":"25438","creation_date":"1500841996","6":"1500841996"},{"0":"5358","vim_version":"7.0","1":"7.0","script_version":"1.1.1","2":"1.1.1","version_comment":"Highlight fixes.","3":"Highlight fixes.","package":"pgsql.vim-1.1.1.tar.gz","4":"pgsql.vim-1.1.1.tar.gz","src_id":"24230","5":"24230","creation_date":"1462477309","6":"1462477309"},{"0":"5358","vim_version":"7.0","1":"7.0","script_version":"1.1.0","2":"1.1.0","version_comment":"More keywords, a few bug fixes.","3":"More keywords, a few bug fixes.","package":"pgsql.vim-1.1.0.tar.gz","4":"pgsql.vim-1.1.0.tar.gz","src_id":"24217","5":"24217","creation_date":"1462021370","6":"1462021370"},{"0":"5358","vim_version":"7.4","1":"7.4","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"pgsql-v1.0.tar.gz","4":"pgsql-v1.0.tar.gz","src_id":"24145","5":"24145","creation_date":"1459238492","6":"1459238492"}]},"5357":{"script_id":"5357","0":"5357","script_name":"md_insert_equation.vim","1":"md_insert_equation.vim","script_type":"ftplugin","2":"ftplugin","summary":"Easily generate link to image of equation in markdown file","3":"Easily generate link to image of equation in markdown file","description":"Notice: This plugin currently only offer the most simplistic interface for simple equation inputting. To make it a full-fledged LaTeX equation editor with all highlighting and auto-completion feature is surely doable(by using split with tex filetype) but it could take some effort and I don't know if there will be people needing it. So if you happen to take interests in this plugin and have the need for such feature, or any other feature you feel nice to have, shout out in the issue section of my github repository and I'll surely work on it as soon as I'm available.\r\n\r\nCode is hosted at: https:\/\/github.com\/ron89\/md_insert_equation.vim\r\n\r\n## Motivation\r\n\r\nInputing math equation into markdown file can be troublesome sometimes as there\r\nis no standard method of it. So far the most fail-proof method to make\r\ngenerally recognized(by github, etc.) equation is to use a third party API to\r\ntranslate $LaTeX$ code into equation image, then generate a link to that image.\r\nHowever, typing the link according to the api in markdown hyperlink format is\r\ncumbersome. To facilitate the process in Vim editor, I made this plugin.\r\n\r\n## How to use\r\n\r\nAll you need to do is to:\r\n  * invoke the keybinding `ee`;\r\n  * type in your equation in LaTeX format.\r\nAnd the equation will be automatically translated into latex.codecogs.com\r\nrecognized image generating API and inserted under your cursor. Invoking the\r\nsame keybinding under existing equation will enable you to edit it in LaTeX\r\nformat.\r\n\r\nscreenshot: https:\/\/imgur.com\/kVwtBD6\r\n","4":"Notice: This plugin currently only offer the most simplistic interface for simple equation inputting. To make it a full-fledged LaTeX equation editor with all highlighting and auto-completion feature is surely doable(by using split with tex filetype) but it could take some effort and I don't know if there will be people needing it. So if you happen to take interests in this plugin and have the need for such feature, or any other feature you feel nice to have, shout out in the issue section of my github repository and I'll surely work on it as soon as I'm available.\r\n\r\nCode is hosted at: https:\/\/github.com\/ron89\/md_insert_equation.vim\r\n\r\n## Motivation\r\n\r\nInputing math equation into markdown file can be troublesome sometimes as there\r\nis no standard method of it. So far the most fail-proof method to make\r\ngenerally recognized(by github, etc.) equation is to use a third party API to\r\ntranslate $LaTeX$ code into equation image, then generate a link to that image.\r\nHowever, typing the link according to the api in markdown hyperlink format is\r\ncumbersome. To facilitate the process in Vim editor, I made this plugin.\r\n\r\n## How to use\r\n\r\nAll you need to do is to:\r\n  * invoke the keybinding `ee`;\r\n  * type in your equation in LaTeX format.\r\nAnd the equation will be automatically translated into latex.codecogs.com\r\nrecognized image generating API and inserted under your cursor. Invoking the\r\nsame keybinding under existing equation will enable you to edit it in LaTeX\r\nformat.\r\n\r\nscreenshot: https:\/\/imgur.com\/kVwtBD6\r\n","install_details":"* Note: I do not recommend installing this plugin by directly downloading the\r\n  tar ball and copying the content to your ~\/.vim\/ftplugin folder, especially\r\n  if you already have installed other markdown related plugins(which is very\r\n  likely to be true). If you still would like to do so, please append the\r\n  content of this plugin's ftplugin\/markdown.vim to your\r\n    ~\/.vim\/ftplugin\/markdown.vim\r\n  if that file already exists.\r\n\r\n## I strongly recommend using one of the package managers for installing\/managing:\r\n  * Pathogen\r\n        git clone https:\/\/github.com\/ron89\/md_insert_equation.vim ~\/.vim\/bundle\/md_insert_equation.vim\r\n  * Vundle\r\n        Add to .vimrc:\r\n            Bundle 'ron89\/md_insert_equation.vim'\r\n        Run\r\n            :BundleInstall\r\n  * NeoBundle\r\n        Add to .vimrc:\r\n            NeoBundle 'ron89\/md_insert_equation.vim'\r\n        Run\r\n            :NeoBundleInstall\r\n  * vim-plug\r\n        Add to .vimrc:\r\n            Plug 'ron89\/md_insert_equation.vim'\r\n        Run\r\n            :PlugInstall\r\n","5":"* Note: I do not recommend installing this plugin by directly downloading the\r\n  tar ball and copying the content to your ~\/.vim\/ftplugin folder, especially\r\n  if you already have installed other markdown related plugins(which is very\r\n  likely to be true). If you still would like to do so, please append the\r\n  content of this plugin's ftplugin\/markdown.vim to your\r\n    ~\/.vim\/ftplugin\/markdown.vim\r\n  if that file already exists.\r\n\r\n## I strongly recommend using one of the package managers for installing\/managing:\r\n  * Pathogen\r\n        git clone https:\/\/github.com\/ron89\/md_insert_equation.vim ~\/.vim\/bundle\/md_insert_equation.vim\r\n  * Vundle\r\n        Add to .vimrc:\r\n            Bundle 'ron89\/md_insert_equation.vim'\r\n        Run\r\n            :BundleInstall\r\n  * NeoBundle\r\n        Add to .vimrc:\r\n            NeoBundle 'ron89\/md_insert_equation.vim'\r\n        Run\r\n            :NeoBundleInstall\r\n  * vim-plug\r\n        Add to .vimrc:\r\n            Plug 'ron89\/md_insert_equation.vim'\r\n        Run\r\n            :PlugInstall\r\n","first_name":"Chong","6":"Chong","last_name":"HE","7":"HE","releases":[{"0":"5357","vim_version":"7.4","1":"7.4","script_version":"v0.1.0","2":"v0.1.0","version_comment":"Initial upload","3":"Initial upload","package":"md_insert_equation.vim-0.1.0.tar.gz","4":"md_insert_equation.vim-0.1.0.tar.gz","src_id":"24140","5":"24140","creation_date":"1458982867","6":"1458982867"}]},"5354":{"script_id":"5354","0":"5354","script_name":"codeFrame","1":"codeFrame","script_type":"utility","2":"utility","summary":"CodeFrame is a vim plugin that makes the skeleton of programming language","3":"CodeFrame is a vim plugin that makes the skeleton of programming language","description":"CodeFrame is a vim plugin that makes the skeleton of programming language, such as c and c++, java, php, python, perl, ruby, html, bash.\r\n\r\n- Demo: https:\/\/www.youtube.com\/watch?v=jpayFgP-Y1M\r\n- Github: https:\/\/github.com\/westporch\/codeFrame\r\n\r\n\r\nYou just create a programming language file through vim.\r\n\r\nvi test.c\r\nvi test.cpp\r\nvi test.java\r\nvi test.php\r\nvi test.py\r\nvi test.pl\r\nvi test.rb\r\nvi test.html\r\nvi test.sh","4":"CodeFrame is a vim plugin that makes the skeleton of programming language, such as c and c++, java, php, python, perl, ruby, html, bash.\r\n\r\n- Demo: https:\/\/www.youtube.com\/watch?v=jpayFgP-Y1M\r\n- Github: https:\/\/github.com\/westporch\/codeFrame\r\n\r\n\r\nYou just create a programming language file through vim.\r\n\r\nvi test.c\r\nvi test.cpp\r\nvi test.java\r\nvi test.php\r\nvi test.py\r\nvi test.pl\r\nvi test.rb\r\nvi test.html\r\nvi test.sh","install_details":"wget https:\/\/raw.githubusercontent.com\/westporch\/codeFrame\/master\/install.sh\r\nchmod 655 install.sh\r\n.\/install.sh","5":"wget https:\/\/raw.githubusercontent.com\/westporch\/codeFrame\/master\/install.sh\r\nchmod 655 install.sh\r\n.\/install.sh","first_name":"Hyun-gwan","6":"Hyun-gwan","last_name":"Seo","7":"Seo","releases":[{"0":"5354","vim_version":"7.4","1":"7.4","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"codeFrame-1.0.zip","4":"codeFrame-1.0.zip","src_id":"24135","5":"24135","creation_date":"1458900511","6":"1458900511"}]},"5353":{"script_id":"5353","0":"5353","script_name":"sqlite.vim","1":"sqlite.vim","script_type":"utility","2":"utility","summary":"Plugin that provides sqlite database access to vimscripts","3":"Plugin that provides sqlite database access to vimscripts","description":"See latest version on github: https:\/\/github.com\/viaa\/VimPlugins\r\n\r\nPlugin that provides sqlite database access to vimscripts. The script was not tested in Linux, but it does work in Windows.\r\n\r\nUsage: Change the s:SqlitePath variable in this script to the path of your sqlite3 executable, then in your script set this variable to the path of your database let g:SVDbPath = ''. After that you can use any of the functions in this script to access sqlite:\r\n\r\nSVReplaceChars(fileName) \" Replace invalid filename characters\r\nSVFormatCSVDates(monthPos) \" Format the dates: if a day or month is less than 10 then add a 0 to have it compatible with Sqlite's date format (the dates formatted here have an initial format m\/d\/yyyy (d\/m\/yyyy could also be formatted) \r\nSVImportCsv(tbl, path, separator, append, removeColumns, dropTable, createTableFromCsvColumns) \" Import a CSV file\r\nSVExe(type, out, stm) \" Execute a SQL statement or a command script. May return the results if specified.\r\nSVExportCsv(qry, path) \" Export the file to csv\r\nSVExportTab(qry, path) \" Export the file to text separated by tabs\r\nSVExportList(qry, path) \" Export the file to list (each field is on its own line)\r\nSVExportListPostProcessing() \" Post processing (to make the file with the first field indented and the multiline text fields with all their text lines on the same line, the line of the field)\r\nSVExportHtml(qry, path, decodeHtml) \" Export a table\/view to an html file\r\nSVViewsToHtml(path, decodeHtml) \" Export each views to 1 html files and create a frameset to navigate the views with a list (menu)\r\nSVTables(out) \" Show table list\r\nSVSchema(out, tblName) \" Show table(s) description(s). If no table name specified then all tables are described.\r\nSVConvertListToCsv(path, fieldsToRemove, separator) \" Format a file that is exported with g:SVExportList() to a CSV file for import\r\nSVSqlColumnNames(sql) \" Returns a list of column names for the given query\r\nSVSqlLoop(sql, callbackFunction) \" Loops the rows returned by a sql statement and for each rows it calls a callback function, passing to it a dictionnary that contains the names and values of each columns in that row.\r\nSVSqlToFile(sql, filePath, mapInstructions, filterInstructions) \" Write the result of a sql query to a file. The mapInstructions and filterIntstructions are lists of strings that will passed to the map() and filter() functions to do processing on the list before to save it.\r\nSVCreateTableFromCsvFile(path, separator, tbl, dropTable) \" Takes the columns on the first line of a csv file and makes a 'create table' statement out of it \r\nSVDropTable(tbl) \" To simply drop a table (helper function)\r\n\r\n","4":"See latest version on github: https:\/\/github.com\/viaa\/VimPlugins\r\n\r\nPlugin that provides sqlite database access to vimscripts. The script was not tested in Linux, but it does work in Windows.\r\n\r\nUsage: Change the s:SqlitePath variable in this script to the path of your sqlite3 executable, then in your script set this variable to the path of your database let g:SVDbPath = ''. After that you can use any of the functions in this script to access sqlite:\r\n\r\nSVReplaceChars(fileName) \" Replace invalid filename characters\r\nSVFormatCSVDates(monthPos) \" Format the dates: if a day or month is less than 10 then add a 0 to have it compatible with Sqlite's date format (the dates formatted here have an initial format m\/d\/yyyy (d\/m\/yyyy could also be formatted) \r\nSVImportCsv(tbl, path, separator, append, removeColumns, dropTable, createTableFromCsvColumns) \" Import a CSV file\r\nSVExe(type, out, stm) \" Execute a SQL statement or a command script. May return the results if specified.\r\nSVExportCsv(qry, path) \" Export the file to csv\r\nSVExportTab(qry, path) \" Export the file to text separated by tabs\r\nSVExportList(qry, path) \" Export the file to list (each field is on its own line)\r\nSVExportListPostProcessing() \" Post processing (to make the file with the first field indented and the multiline text fields with all their text lines on the same line, the line of the field)\r\nSVExportHtml(qry, path, decodeHtml) \" Export a table\/view to an html file\r\nSVViewsToHtml(path, decodeHtml) \" Export each views to 1 html files and create a frameset to navigate the views with a list (menu)\r\nSVTables(out) \" Show table list\r\nSVSchema(out, tblName) \" Show table(s) description(s). If no table name specified then all tables are described.\r\nSVConvertListToCsv(path, fieldsToRemove, separator) \" Format a file that is exported with g:SVExportList() to a CSV file for import\r\nSVSqlColumnNames(sql) \" Returns a list of column names for the given query\r\nSVSqlLoop(sql, callbackFunction) \" Loops the rows returned by a sql statement and for each rows it calls a callback function, passing to it a dictionnary that contains the names and values of each columns in that row.\r\nSVSqlToFile(sql, filePath, mapInstructions, filterInstructions) \" Write the result of a sql query to a file. The mapInstructions and filterIntstructions are lists of strings that will passed to the map() and filter() functions to do processing on the list before to save it.\r\nSVCreateTableFromCsvFile(path, separator, tbl, dropTable) \" Takes the columns on the first line of a csv file and makes a 'create table' statement out of it \r\nSVDropTable(tbl) \" To simply drop a table (helper function)\r\n\r\n","install_details":"Put the script in the vim plugin directory.","5":"Put the script in the vim plugin directory.","first_name":"Alexandre","6":"Alexandre","last_name":"Viau","7":"Viau","releases":[{"0":"5353","vim_version":"7.0","1":"7.0","script_version":"2.0","2":"2.0","version_comment":"Many changes","3":"Many changes","package":"sqlite.vim","4":"sqlite.vim","src_id":"24720","5":"24720","creation_date":"1478816674","6":"1478816674"},{"0":"5353","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"sqlite.vim","4":"sqlite.vim","src_id":"24133","5":"24133","creation_date":"1458824153","6":"1458824153"}]},"5352":{"script_id":"5352","0":"5352","script_name":"cwdtabline.vim","1":"cwdtabline.vim","script_type":"utility","2":"utility","summary":"cwd's in the tabline","3":"cwd's in the tabline","description":"Cwdtabline takes over the tabline and renders each tab as the last component of the cwd of the active window in that tab.\r\n\r\nThe only exception to the above rule is that the home directory is displayed as '~'. And for a string of tabs in the same directory, the leftmost tab will be the cwd and the tabs following will be '\"'. The idea here was to save screen space and to tell at a glance when adjacent tabs are in the same directory.\r\n\r\nMore details: https:\/\/github.com\/lag13\/vim-cwdtabline","4":"Cwdtabline takes over the tabline and renders each tab as the last component of the cwd of the active window in that tab.\r\n\r\nThe only exception to the above rule is that the home directory is displayed as '~'. And for a string of tabs in the same directory, the leftmost tab will be the cwd and the tabs following will be '\"'. The idea here was to save screen space and to tell at a glance when adjacent tabs are in the same directory.\r\n\r\nMore details: https:\/\/github.com\/lag13\/vim-cwdtabline","install_details":"","5":"","first_name":"Lucas","6":"Lucas","last_name":"Groenendaal","7":"Groenendaal","releases":[{"0":"5352","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"cwdtabline.zip","4":"cwdtabline.zip","src_id":"24130","5":"24130","creation_date":"1458762347","6":"1458762347"}]},"5351":{"script_id":"5351","0":"5351","script_name":"Vedict","1":"Vedict","script_type":"utility","2":"utility","summary":"Fast Japanese \/ English Dictionary Lookup ","3":"Fast Japanese \/ English Dictionary Lookup ","description":"This vim plugin provides fast Japanese-to-English and English-to-Japanese\r\ndictionary lookup using files available from the EDICT project.\r\n\r\nSource:\r\nhttps:\/\/github.com\/gglynne\/vedict \r\n\r\nEDICT\r\nhttp:\/\/www.edrdg.org\/jmdict\/edict.html\r\n\r\n","4":"This vim plugin provides fast Japanese-to-English and English-to-Japanese\r\ndictionary lookup using files available from the EDICT project.\r\n\r\nSource:\r\nhttps:\/\/github.com\/gglynne\/vedict \r\n\r\nEDICT\r\nhttp:\/\/www.edrdg.org\/jmdict\/edict.html\r\n\r\n","install_details":"1. Unpack in your plugin directory\r\n\r\n2. Get the dictionaries:\r\n\r\n    :Vedict getdics\r\n\r\n3. Load the dictionaries and mappings e.g. add the following to your .vimrc:\r\n  \r\nVedict load edict edict\r\nVedict load enamdict edict\r\nnmap  :Vedict toggle\r\nvmap  y:Vedict grep \"\"\" edict\r\nvmap  y:Vedict grep \".*\"\" edict\r\nvmap  y:Vedict grep \" enamdict\r\nvmap  y:Vedict grep \".*\"\" enamdict\r\n\r\n4. See https:\/\/github.com\/gglynne\/vedict for usage.","5":"1. Unpack in your plugin directory\r\n\r\n2. Get the dictionaries:\r\n\r\n    :Vedict getdics\r\n\r\n3. Load the dictionaries and mappings e.g. add the following to your .vimrc:\r\n  \r\nVedict load edict edict\r\nVedict load enamdict edict\r\nnmap  :Vedict toggle\r\nvmap  y:Vedict grep \"\"\" edict\r\nvmap  y:Vedict grep \".*\"\" edict\r\nvmap  y:Vedict grep \" enamdict\r\nvmap  y:Vedict grep \".*\"\" enamdict\r\n\r\n4. See https:\/\/github.com\/gglynne\/vedict for usage.","first_name":"Glynne","6":"Glynne","last_name":"Evans","7":"Evans","releases":[{"0":"5351","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"vedict.zip","4":"vedict.zip","src_id":"24129","5":"24129","creation_date":"1458744871","6":"1458744871"}]},"5350":{"script_id":"5350","0":"5350","script_name":"GoDiff","1":"GoDiff","script_type":"utility","2":"utility","summary":"Quick Inline Colored Diff","3":"Quick Inline Colored Diff","description":"A plug-in to quickly compare two sections of text with colors.\r\n\r\ncheckout the wiki here with screenshots:\r\n\r\nhttp:\/\/vim.wikia.com\/wiki\/Script:5350\r\n\r\nFirst copy text-1 (e.g. '3yy' to copy 3 lines) \r\nThen, either\r\n  visually select text-2 (e.g. 'V2j' to visually select 3 lines)\r\n  Now press 'gd' to compare text-1 and text-2\r\nOr\r\n  give a count for number of lines to diff followed by gd (e.g. '3gd')\r\nFinally press 'gd' again to restore colors\r\n                                                                                   \r\nRegisters can also be used. Try '\"a3yy' or '3\"ayy' to copy 3 lines to register 'a'\r\nThen '\"a3gd' or '3\"agd' on text to compare with.\r\n                                                                                   \r\nFor single line compare, simply press 'yy' on text-1 and 'gd' on text-2\r\n","4":"A plug-in to quickly compare two sections of text with colors.\r\n\r\ncheckout the wiki here with screenshots:\r\n\r\nhttp:\/\/vim.wikia.com\/wiki\/Script:5350\r\n\r\nFirst copy text-1 (e.g. '3yy' to copy 3 lines) \r\nThen, either\r\n  visually select text-2 (e.g. 'V2j' to visually select 3 lines)\r\n  Now press 'gd' to compare text-1 and text-2\r\nOr\r\n  give a count for number of lines to diff followed by gd (e.g. '3gd')\r\nFinally press 'gd' again to restore colors\r\n                                                                                   \r\nRegisters can also be used. Try '\"a3yy' or '3\"ayy' to copy 3 lines to register 'a'\r\nThen '\"a3gd' or '3\"agd' on text to compare with.\r\n                                                                                   \r\nFor single line compare, simply press 'yy' on text-1 and 'gd' on text-2\r\n","install_details":"   Source this file\r\nor\r\n   Copy its content into your .vimrc\r\nor\r\n   If using pathogen, copy this file into .vim\/bundle\/godiff\/plugin\/\r\nor\r\n   Copy it to your .vim\/plugin directory to automatically source it when vim\r\n   starts\r\nor\r\n   Copy it to your .vim\/plugins directory (or any other directory) and source\r\n   it explicitly from your .vimrc","5":"   Source this file\r\nor\r\n   Copy its content into your .vimrc\r\nor\r\n   If using pathogen, copy this file into .vim\/bundle\/godiff\/plugin\/\r\nor\r\n   Copy it to your .vim\/plugin directory to automatically source it when vim\r\n   starts\r\nor\r\n   Copy it to your .vim\/plugins directory (or any other directory) and source\r\n   it explicitly from your .vimrc","first_name":"Rolf","6":"Rolf","last_name":"Asmund","7":"Asmund","releases":[{"0":"5350","vim_version":"7.0","1":"7.0","script_version":"1.2","2":"1.2","version_comment":"Support for v:count and v:register","3":"Support for v:count and v:register","package":"godiff.vim","4":"godiff.vim","src_id":"24156","5":"24156","creation_date":"1459845239","6":"1459845239"},{"0":"5350","vim_version":"7.0","1":"7.0","script_version":"1.1","2":"1.1","version_comment":"Support for guifg\/bg (for gvim)\r\nDisable hlsearch and spell while active\r\nIf no selection, do single-line diff","3":"Support for guifg\/bg (for gvim)\r\nDisable hlsearch and spell while active\r\nIf no selection, do single-line diff","package":"godiff.vim","4":"godiff.vim","src_id":"24127","5":"24127","creation_date":"1458591511","6":"1458591511"},{"0":"5350","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"godiff.vim","4":"godiff.vim","src_id":"24124","5":"24124","creation_date":"1458425724","6":"1458425724"}]},"5349":{"script_id":"5349","0":"5349","script_name":"license-to-vim","1":"license-to-vim","script_type":"utility","2":"utility","summary":"Insert code licenses from Vim","3":"Insert code licenses from Vim","description":"License To Vim is a simple plugin that allows you to insert full or partial licenses into your files. A number of licenses are included. See https:\/\/github.com\/ararslan\/license-to-vim for more information.","4":"License To Vim is a simple plugin that allows you to insert full or partial licenses into your files. A number of licenses are included. See https:\/\/github.com\/ararslan\/license-to-vim for more information.","install_details":"I recommend installing the latest version from GitHub using your favorite package manager (I like Vim Plug). Otherwise just make sure the files are in your Vim runtime path.","5":"I recommend installing the latest version from GitHub using your favorite package manager (I like Vim Plug). Otherwise just make sure the files are in your Vim runtime path.","first_name":"Alex","6":"Alex","last_name":"Arslan","7":"Arslan","releases":[{"0":"5349","vim_version":"7.0","1":"7.0","script_version":"v0.0.1","2":"v0.0.1","version_comment":"Initial upload","3":"Initial upload","package":"license-to-vim-0.0.1.tar","4":"license-to-vim-0.0.1.tar","src_id":"24120","5":"24120","creation_date":"1458345264","6":"1458345264"}]},"5348":{"script_id":"5348","0":"5348","script_name":"RAPID-Syntax","1":"RAPID-Syntax","script_type":"syntax","2":"syntax","summary":"Syntax, indent and more for Abb industrial robots","3":"Syntax, indent and more for Abb industrial robots","description":"Now available on github: https:\/\/github.com\/KnoP-01\/rapid-for-vim \r\n\r\nRapid for Vim (7.4 or later) is a collection of Vim scripts to help programing ABB industrial robots (https:\/\/new.abb.com\/products\/robotics\/industrial-robots).\r\n\r\nIt provides\r\n\r\n*    syntax highlighting,\r\n*    indenting,\r\n*    concealing of structure values (e.g. MoveJ * v2500...),\r\n*    support for commentary vimscript #3695, matchit vimscript #39 and matchup vimscript #5624,\r\n*    mappings and settings to navigate through code in a backup folder structure,\r\n*    text objects for functions and\r\n*    completion of words from known or custom global files like EIO.cfg,\r\n*    mappings to insert a body of a new PROC, FUNC, TRAP et al based on user defined templates or hopefully sane defaults.\r\n\r\nNote: Keep your files to be edited in one folder or in a regular robot backup folder structure. Rapid for Vim modifies 'path' accordingly. \r\nNote to Linux users: Keep your files to be edited on a FAT file system. Some features need the case insensitive file system to work properly.\r\n\r\nSee https:\/\/github.com\/KnoP-01\/rapid-for-vim#FAQ on how to use more than just highlight and indent.","4":"Now available on github: https:\/\/github.com\/KnoP-01\/rapid-for-vim \r\n\r\nRapid for Vim (7.4 or later) is a collection of Vim scripts to help programing ABB industrial robots (https:\/\/new.abb.com\/products\/robotics\/industrial-robots).\r\n\r\nIt provides\r\n\r\n*    syntax highlighting,\r\n*    indenting,\r\n*    concealing of structure values (e.g. MoveJ * v2500...),\r\n*    support for commentary vimscript #3695, matchit vimscript #39 and matchup vimscript #5624,\r\n*    mappings and settings to navigate through code in a backup folder structure,\r\n*    text objects for functions and\r\n*    completion of words from known or custom global files like EIO.cfg,\r\n*    mappings to insert a body of a new PROC, FUNC, TRAP et al based on user defined templates or hopefully sane defaults.\r\n\r\nNote: Keep your files to be edited in one folder or in a regular robot backup folder structure. Rapid for Vim modifies 'path' accordingly. \r\nNote to Linux users: Keep your files to be edited on a FAT file system. Some features need the case insensitive file system to work properly.\r\n\r\nSee https:\/\/github.com\/KnoP-01\/rapid-for-vim#FAQ on how to use more than just highlight and indent.","install_details":"### Installation with vim-plug:  ~\r\nPut this in your .vimrc:  >\r\n\r\n    call plug#begin('~\/.vim\/plugged')\r\n      Plug 'KnoP-01\/rapid-for-vim'\r\n    call plug#end()\r\n\r\nFor the first installation run: >\r\n\r\n    :PlugInstall\r\n\r\nUpdate every once in a while with: >\r\n\r\n    :PlugUpdate\r\n\r\n### Manual installation:  ~\r\nExtract the most recent release and copy the folders `\/doc`, `\/ftdetect`, `\/ftplugin`, `\/indent` and `\/syntax`  into your `~\/.vim\/` or `%USERPROFILE%\\vimfiles\\` directory. Overwrite rapid.* files from older installation.\r\nPut the following in your .vimrc: >\r\n\r\n    syntax on                        \" syntax and filetype on in that order\r\n    filetype plugin indent on  \" syntax and filetype on in that order\r\n\r\nYou may have to run >\r\n\r\n    :helptags ~\/.vim\/doc\/\r\n\r\nor >\r\n\r\n    :helptags ~\/vimfiles\/doc\/\r\n\r\nto use the help within Vim after installation. >\r\n\r\n    :help rapid","5":"### Installation with vim-plug:  ~\r\nPut this in your .vimrc:  >\r\n\r\n    call plug#begin('~\/.vim\/plugged')\r\n      Plug 'KnoP-01\/rapid-for-vim'\r\n    call plug#end()\r\n\r\nFor the first installation run: >\r\n\r\n    :PlugInstall\r\n\r\nUpdate every once in a while with: >\r\n\r\n    :PlugUpdate\r\n\r\n### Manual installation:  ~\r\nExtract the most recent release and copy the folders `\/doc`, `\/ftdetect`, `\/ftplugin`, `\/indent` and `\/syntax`  into your `~\/.vim\/` or `%USERPROFILE%\\vimfiles\\` directory. Overwrite rapid.* files from older installation.\r\nPut the following in your .vimrc: >\r\n\r\n    syntax on                        \" syntax and filetype on in that order\r\n    filetype plugin indent on  \" syntax and filetype on in that order\r\n\r\nYou may have to run >\r\n\r\n    :helptags ~\/.vim\/doc\/\r\n\r\nor >\r\n\r\n    :helptags ~\/vimfiles\/doc\/\r\n\r\nto use the help within Vim after installation. >\r\n\r\n    :help rapid","first_name":"Patrick","6":"Patrick","last_name":"Meiser-Knosowski","7":"Meiser-Knosowski","releases":[{"0":"5348","vim_version":"7.4","1":"7.4","script_version":"v2.2.6","2":"v2.2.6","version_comment":"* Fix: Catch E479","3":"* Fix: Catch E479","package":"rapid-for-vim-2.2.6.zip","4":"rapid-for-vim-2.2.6.zip","src_id":"27891","5":"27891","creation_date":"1641410611","6":"1641410611"},{"0":"5348","vim_version":"7.4","1":"7.4","script_version":"v2.2.5","2":"v2.2.5","version_comment":"* Add tool change and some other missing instructions and datatypes\r\n* Add some missing conveyor tracking instructions\r\n* Add rapid numbers in Dec-, Hex-, Oct- and Bin-format\r\n* Fix concealing of structure values\r\n* Use quickfixtextfunc instead of temp file to modify the quickfix\r\n  window\r\n* Raise chars of shortened path in quickfix window from 3 to 5 for\r\n  readability\r\n* Fix false highlight if a ] is part of a string in a struct\r\n* Change highlight of config header\r\n* Optimize 'path' generation\r\n* Enable spell checking only for comments and strings\r\n* Fix false highlight of the end of rapidStructVal","3":"* Add tool change and some other missing instructions and datatypes\r\n* Add some missing conveyor tracking instructions\r\n* Add rapid numbers in Dec-, Hex-, Oct- and Bin-format\r\n* Fix concealing of structure values\r\n* Use quickfixtextfunc instead of temp file to modify the quickfix\r\n  window\r\n* Raise chars of shortened path in quickfix window from 3 to 5 for\r\n  readability\r\n* Fix false highlight if a ] is part of a string in a struct\r\n* Change highlight of config header\r\n* Optimize 'path' generation\r\n* Enable spell checking only for comments and strings\r\n* Fix false highlight of the end of rapidStructVal","package":"rapid-for-vim-2.2.5.zip","4":"rapid-for-vim-2.2.5.zip","src_id":"27871","5":"27871","creation_date":"1640334270","6":"1640334270"},{"0":"5348","vim_version":"7.4","1":"7.4","script_version":"v2.2.2","2":"v2.2.2","version_comment":"* Updt to RW6.10; add missing commands, functions and data types and constants\r\n* Add more commands, functions and data types and constants of optional technology\r\n* Allow umlauts\r\n* Set 'fileencoding' = latin1 (even if Robot Studio accepts UTF8, the robot itself does not!)\r\n* Fix highlight of struct which span over lines\r\n* Add endwise (tpope) support\r\n* Support ]],[[... for .cfg files\r\n* Make mappings for conceal structs work if g:rapidConcealStructs=0\r\n* Highlight of conditional argument\r\n* Highlight -name strings longer than 32 chars as error\r\n* Refactor indent file","3":"* Updt to RW6.10; add missing commands, functions and data types and constants\r\n* Add more commands, functions and data types and constants of optional technology\r\n* Allow umlauts\r\n* Set 'fileencoding' = latin1 (even if Robot Studio accepts UTF8, the robot itself does not!)\r\n* Fix highlight of struct which span over lines\r\n* Add endwise (tpope) support\r\n* Support ]],[[... for .cfg files\r\n* Make mappings for conceal structs work if g:rapidConcealStructs=0\r\n* Highlight of conditional argument\r\n* Highlight -name strings longer than 32 chars as error\r\n* Refactor indent file","package":"rapid-for-vim-2.2.2.zip","4":"rapid-for-vim-2.2.2.zip","src_id":"27412","5":"27412","creation_date":"1608648546","6":"1608648546"},{"0":"5348","vim_version":"7.4","1":"7.4","script_version":"2.1.1","2":"2.1.1","version_comment":"*    enable most features by default\r\n*    add text objects for Proc\/Func\/Trap.. and comment blocks\r\n*    [[, [], ... work in operator pending mode\r\n*    add commands\/types of some technology packages\r\n*    fix bug where unnamed buffers are created for each use of gd, f and u\r\n*    add EIO.cfg etc to 'complete', customizable (see :help rapid-complete)\r\n*    restructure help","3":"*    enable most features by default\r\n*    add text objects for Proc\/Func\/Trap.. and comment blocks\r\n*    [[, [], ... work in operator pending mode\r\n*    add commands\/types of some technology packages\r\n*    fix bug where unnamed buffers are created for each use of gd, f and u\r\n*    add EIO.cfg etc to 'complete', customizable (see :help rapid-complete)\r\n*    restructure help","package":"rapid-for-vim-2.1.1.zip","4":"rapid-for-vim-2.1.1.zip","src_id":"26870","5":"26870","creation_date":"1576285856","6":"1576285856"},{"0":"5348","vim_version":"7.4","1":"7.4","script_version":"1.5.5","2":"1.5.5","version_comment":"* added text objects for functions (depends on g:rapidMoveAroundKeyMap: set this option to 2 to get the textobjects)\r\n\taf (around function): from proc, func, trap or record to endproc et al.\r\n\taF: as af but includes all comments directly above proc et al. and one empty line after endproc et al.\r\n\tif (inner function): from one line after proc et al. to one line before endproc et al. \r\n* made label highlighting more consistent","3":"* added text objects for functions (depends on g:rapidMoveAroundKeyMap: set this option to 2 to get the textobjects)\r\n\taf (around function): from proc, func, trap or record to endproc et al.\r\n\taF: as af but includes all comments directly above proc et al. and one empty line after endproc et al.\r\n\tif (inner function): from one line after proc et al. to one line before endproc et al. \r\n* made label highlighting more consistent","package":"rapid-for-vim-1.5.5.zip","4":"rapid-for-vim-1.5.5.zip","src_id":"25898","5":"25898","creation_date":"1521808176","6":"1521808176"},{"0":"5348","vim_version":"7.4","1":"7.4","script_version":"1.5.3","2":"1.5.3","version_comment":"* changes in help file\r\n* highlight procs and vars >32 char as error","3":"* changes in help file\r\n* highlight procs and vars >32 char as error","package":"rapid-for-vim-1.5.3.zip","4":"rapid-for-vim-1.5.3.zip","src_id":"25730","5":"25730","creation_date":"1513993138","6":"1513993138"},{"0":"5348","vim_version":"7.4","1":"7.4","script_version":"1.5.2","2":"1.5.2","version_comment":"* changed \"highlight link\" to \"highlight default link\" in syntax file\r\n* changed 'path': excluded ..\/PROGMOD\/** and ..\/SYSMOD\/**. This is catched by ..\/..\/..\/RAPID\/TASK*\/** now\r\n* made structure values concealable (eg MoveL *, v2500, z200, ...)\r\n* added optional mappings to quickly change between concealed\/shown (F2\/F3) structure values\r\n  See :help g:rapidConcealStructsKeyMap and g:rapidConcealStructs\r\n* fixed bug related to g:rapidShowError","3":"* changed \"highlight link\" to \"highlight default link\" in syntax file\r\n* changed 'path': excluded ..\/PROGMOD\/** and ..\/SYSMOD\/**. This is catched by ..\/..\/..\/RAPID\/TASK*\/** now\r\n* made structure values concealable (eg MoveL *, v2500, z200, ...)\r\n* added optional mappings to quickly change between concealed\/shown (F2\/F3) structure values\r\n  See :help g:rapidConcealStructsKeyMap and g:rapidConcealStructs\r\n* fixed bug related to g:rapidShowError","package":"rapid_for_vim_v152_20170920.zip","4":"rapid_for_vim_v152_20170920.zip","src_id":"25579","5":"25579","creation_date":"1505863985","6":"1505863985"},{"0":"5348","vim_version":"7.4","1":"7.4","script_version":"1.5.1","2":"1.5.1","version_comment":"* fixed bug in move around comment mapping [! and ]!","3":"* fixed bug in move around comment mapping [! and ]!","package":"rapid_for_vim_v151_20170817.zip","4":"rapid_for_vim_v151_20170817.zip","src_id":"25518","5":"25518","creation_date":"1503004765","6":"1503004765"},{"0":"5348","vim_version":"7.4","1":"7.4","script_version":"1.5.0","2":"1.5.0","version_comment":"* better 'path' generation, also added HOME\/ and BACKINFO\/ to 'path'\r\n* better temp file handling. Sorry to all linux\/unix users for inconvenience with this one.\r\n* made this script compatible to romainls vim-qf (vimscript#5211)\r\n* file comprehensive features should now work on case sensitive file systems","3":"* better 'path' generation, also added HOME\/ and BACKINFO\/ to 'path'\r\n* better temp file handling. Sorry to all linux\/unix users for inconvenience with this one.\r\n* made this script compatible to romainls vim-qf (vimscript#5211)\r\n* file comprehensive features should now work on case sensitive file systems","package":"rapid_for_vim_v150_20170815.zip","4":"rapid_for_vim_v150_20170815.zip","src_id":"25509","5":"25509","creation_date":"1502786711","6":"1502786711"},{"0":"5348","vim_version":"7.0","1":"7.0","script_version":"v1.4.1","2":"v1.4.1","version_comment":"* updated syntax file to RobotWare 6","3":"* updated syntax file to RobotWare 6","package":"rapid_for_vim_v141_20170710.zip","4":"rapid_for_vim_v141_20170710.zip","src_id":"25391","5":"25391","creation_date":"1499797808","6":"1499797808"},{"0":"5348","vim_version":"7.0","1":"7.0","script_version":"1.4.0","2":"1.4.0","version_comment":"* *.cfg file will get a bit highlight and filetype rapid now\r\n* automatically correct mixed dos\/unix line endings in *.cfg files if g:rapidAutoCorrCfgLineEnd is set to 1\r\n* fixed indent bug\r\n* divided up mappings for f and gd into 2 options: g:rapidListDefKeyMap and g:rapidGoDefinitionKeyMap\r\n* added  mappings as an alternative to the configuration variables for mappings \r\n* added auto form feature. Insert a body for a new PROC\/FUNC\/TRAP or RECORD with a few key strokes. See help for more details on this\r\n* added mapping u to list all appearances of the word under the cursor if g:rapidListUsageKeyMap is set\r\n* added option to influence where f, u and gd open the quickfix window: g:rapidRhsQuickfix and g:rapidLhsQuickfix\r\n* improved *.prg file support","3":"* *.cfg file will get a bit highlight and filetype rapid now\r\n* automatically correct mixed dos\/unix line endings in *.cfg files if g:rapidAutoCorrCfgLineEnd is set to 1\r\n* fixed indent bug\r\n* divided up mappings for f and gd into 2 options: g:rapidListDefKeyMap and g:rapidGoDefinitionKeyMap\r\n* added  mappings as an alternative to the configuration variables for mappings \r\n* added auto form feature. Insert a body for a new PROC\/FUNC\/TRAP or RECORD with a few key strokes. See help for more details on this\r\n* added mapping u to list all appearances of the word under the cursor if g:rapidListUsageKeyMap is set\r\n* added option to influence where f, u and gd open the quickfix window: g:rapidRhsQuickfix and g:rapidLhsQuickfix\r\n* improved *.prg file support","package":"rapid_for_vim_v140_20170625.zip","4":"rapid_for_vim_v140_20170625.zip","src_id":"25343","5":"25343","creation_date":"1498348486","6":"1498348486"},{"0":"5348","vim_version":"7.0","1":"7.0","script_version":"1.3.1","2":"1.3.1","version_comment":"* set proper b:undo_indent and b:undo_ftplugin\r\n* added matchit support (vimscript #39)\r\n* added mappings for [[, ]], ... and gd if g:rapidGoDefinitionKeyMap is set\r\n* added mapping of f to list all PROC ect of the current file if g:rapidGoDefinitionKeyMap is set\r\n* added 'path', 'suffixes' and 'suffixesadd' settings for :find or gf\r\n* changed option name from g:rapidNoHighlight to g:rapidNoHighLink (the old one does still work for compatibility)\r\n* additions to syntax","3":"* set proper b:undo_indent and b:undo_ftplugin\r\n* added matchit support (vimscript #39)\r\n* added mappings for [[, ]], ... and gd if g:rapidGoDefinitionKeyMap is set\r\n* added mapping of f to list all PROC ect of the current file if g:rapidGoDefinitionKeyMap is set\r\n* added 'path', 'suffixes' and 'suffixesadd' settings for :find or gf\r\n* changed option name from g:rapidNoHighlight to g:rapidNoHighLink (the old one does still work for compatibility)\r\n* additions to syntax","package":"rapid_for_vim_v131_20161008.zip","4":"rapid_for_vim_v131_20161008.zip","src_id":"24602","5":"24602","creation_date":"1475976097","6":"1475976097"},{"0":"5348","vim_version":"7.0","1":"7.0","script_version":"1.1.2","2":"1.1.2","version_comment":"* a dos formated file type detect file caused error messages on unix like operating systems in the previous version. Sorry for inconvenience!","3":"* a dos formated file type detect file caused error messages on unix like operating systems in the previous version. Sorry for inconvenience!","package":"rapid_for_vim_v112_20160821.zip","4":"rapid_for_vim_v112_20160821.zip","src_id":"24460","5":"24460","creation_date":"1471768455","6":"1471768455"},{"0":"5348","vim_version":"7.0","1":"7.0","script_version":"1.1.2","2":"1.1.2","version_comment":"* this script now setlocal commentstring=!%s for easy use of commentary (vimscript #3695)\r\n* fixed false highlight of num\r\n* updated help\r\n* restructured code","3":"* this script now setlocal commentstring=!%s for easy use of commentary (vimscript #3695)\r\n* fixed false highlight of num\r\n* updated help\r\n* restructured code","package":"rapid_for_vim_v112_20160727.zip","4":"rapid_for_vim_v112_20160727.zip","src_id":"24404","5":"24404","creation_date":"1469620551","6":"1469620551"},{"0":"5348","vim_version":"7.0","1":"7.0","script_version":"1.0.7","2":"1.0.7","version_comment":"* added highlight of rapid char codes within strings\r\n* fixed false highlight of num if it's the name of an \r\n    argument instead of the data type num\r\n* improvements of indent in some special cases\r\n* improved help file","3":"* added highlight of rapid char codes within strings\r\n* fixed false highlight of num if it's the name of an \r\n    argument instead of the data type num\r\n* improvements of indent in some special cases\r\n* improved help file","package":"rapid_for_vim_v107_20160531.zip","4":"rapid_for_vim_v107_20160531.zip","src_id":"24296","5":"24296","creation_date":"1464776763","6":"1464776763"},{"0":"5348","vim_version":"7.0","1":"7.0","script_version":"1.0.4","2":"1.0.4","version_comment":"* fixed indent of wrapped long lines, like long array values or long argument lists\r\n* fixed single parentasis in comments do not cause false indention any more\r\n* fixed UNDO indent","3":"* fixed indent of wrapped long lines, like long array values or long argument lists\r\n* fixed single parentasis in comments do not cause false indention any more\r\n* fixed UNDO indent","package":"rapid_for_vim_v104_20160528.zip","4":"rapid_for_vim_v104_20160528.zip","src_id":"24287","5":"24287","creation_date":"1464393991","6":"1464393991"},{"0":"5348","vim_version":"7.0","1":"7.0","script_version":"1.0.1","2":"1.0.1","version_comment":"* added help\r\n* added file type detect\r\n* added file type plugin\r\n* added indent file\r\n* made the script configurable by options\r\n* minor changes in syntax file","3":"* added help\r\n* added file type detect\r\n* added file type plugin\r\n* added indent file\r\n* made the script configurable by options\r\n* minor changes in syntax file","package":"rapid_for_vim_v101_20160526.zip","4":"rapid_for_vim_v101_20160526.zip","src_id":"24277","5":"24277","creation_date":"1464304066","6":"1464304066"},{"0":"5348","vim_version":"7.0","1":"7.0","script_version":"0.9.3","2":"0.9.3","version_comment":"* used setlocal instead of set","3":"* used setlocal instead of set","package":"rapid.vim","4":"rapid.vim","src_id":"24268","5":"24268","creation_date":"1464117987","6":"1464117987"},{"0":"5348","vim_version":"7.0","1":"7.0","script_version":"0.9","2":"0.9","version_comment":"Initial upload","3":"Initial upload","package":"rapid.vim","4":"rapid.vim","src_id":"24118","5":"24118","creation_date":"1458267652","6":"1458267652"}]},"5347":{"script_id":"5347","0":"5347","script_name":"color.vim","1":"color.vim","script_type":"utility","2":"utility","summary":"color parsing functions - lighten\/darken color under cursor","3":"color parsing functions - lighten\/darken color under cursor","description":"General RGB, HSL and #hex color transforming and basic parsing functions.\r\n\r\nAre implemented two basic functions on top of that: (akin to less\/sass functions with the same name)\r\n \u00e2\u0080\u00a2 color#Lighten(color, [amount=5])  \r\n \u00e2\u0080\u00a2 color#Darken(color, [amount=5])\r\n(both default at 5%, \r\n color can be string\u00e2\u0080\u0094'#599eff'\u00e2\u0080\u0094 or number\u00e2\u0080\u00940x599eff\u00e2\u0080\u0094, \r\n amount can be float\u00e2\u0080\u0094eg 0.05\u00e2\u0080\u0094 or number\u00e2\u0080\u0094eg 5 )\r\n\r\nExample mappings: (alt-minus & alt-equal)\r\n\r\nnnoremap  color#Test(expand(''))\r\n            \\? '\"_ciw' . color#Darken(expand('')) . \"\\\"\r\n            \\: \"\\\"\r\nnnoremap  color#Test(expand(''))\r\n            \\? '\"_ciw' . color#Lighten(expand('')) . \"\\\"\r\n            \\: \"\\\"","4":"General RGB, HSL and #hex color transforming and basic parsing functions.\r\n\r\nAre implemented two basic functions on top of that: (akin to less\/sass functions with the same name)\r\n \u00e2\u0080\u00a2 color#Lighten(color, [amount=5])  \r\n \u00e2\u0080\u00a2 color#Darken(color, [amount=5])\r\n(both default at 5%, \r\n color can be string\u00e2\u0080\u0094'#599eff'\u00e2\u0080\u0094 or number\u00e2\u0080\u00940x599eff\u00e2\u0080\u0094, \r\n amount can be float\u00e2\u0080\u0094eg 0.05\u00e2\u0080\u0094 or number\u00e2\u0080\u0094eg 5 )\r\n\r\nExample mappings: (alt-minus & alt-equal)\r\n\r\nnnoremap  color#Test(expand(''))\r\n            \\? '\"_ciw' . color#Darken(expand('')) . \"\\\"\r\n            \\: \"\\\"\r\nnnoremap  color#Test(expand(''))\r\n            \\? '\"_ciw' . color#Lighten(expand('')) . \"\\\"\r\n            \\: \"\\\"","install_details":"Copy in autoload folder. \r\n\r\nAvailable under the following repo: http:\/\/www.github.com\/romgrk\/lib.kom, with other various general scripting functions.","5":"Copy in autoload folder. \r\n\r\nAvailable under the following repo: http:\/\/www.github.com\/romgrk\/lib.kom, with other various general scripting functions.","first_name":"Rom","6":"Rom","last_name":"Grk","7":"Grk","releases":[{"0":"5347","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"color.vim","4":"color.vim","src_id":"24105","5":"24105","creation_date":"1458107071","6":"1458107071"}]},"5346":{"script_id":"5346","0":"5346","script_name":"Bullets.vim","1":"Bullets.vim","script_type":"utility","2":"utility","summary":"Bullets.vim is a Vim plugin for automated bullet lists.","3":"Bullets.vim is a Vim plugin for automated bullet lists.","description":"Bullets.vim is a Vim plugin for automated bullet lists.\r\n\r\nUsage\r\n----------\r\nIn markdown or a text file start a bulleted list using - or *. Press return to go to the next line, a new list item will be created.\r\n\r\nConfiguration\r\n-------------------\r\nYou can choose which file types this plugin will work on:\r\n\r\nlet g:bullets_enabled_file_types = ['markdown', 'text', 'gitcommit']\r\n\r\nJust add above to your .vimrc\r\n\r\nSee on github:\r\n\r\nhttps:\/\/github.com\/dkarter\/bullets.vim","4":"Bullets.vim is a Vim plugin for automated bullet lists.\r\n\r\nUsage\r\n----------\r\nIn markdown or a text file start a bulleted list using - or *. Press return to go to the next line, a new list item will be created.\r\n\r\nConfiguration\r\n-------------------\r\nYou can choose which file types this plugin will work on:\r\n\r\nlet g:bullets_enabled_file_types = ['markdown', 'text', 'gitcommit']\r\n\r\nJust add above to your .vimrc\r\n\r\nSee on github:\r\n\r\nhttps:\/\/github.com\/dkarter\/bullets.vim","install_details":"With VimPlug:\r\n\r\nPlug 'dkarter\/bullets.vim'\r\nThen source your bundle file and run :PlugInstall.\r\n","5":"With VimPlug:\r\n\r\nPlug 'dkarter\/bullets.vim'\r\nThen source your bundle file and run :PlugInstall.\r\n","first_name":"Dorian","6":"Dorian","last_name":"Karter","7":"Karter","releases":[{"0":"5346","vim_version":"7.0","1":"7.0","script_version":"1.0.2","2":"1.0.2","version_comment":"Initial upload","3":"Initial upload","package":"bullets.vim-1.0.2.zip","4":"bullets.vim-1.0.2.zip","src_id":"24104","5":"24104","creation_date":"1458082165","6":"1458082165"}]},"5345":{"script_id":"5345","0":"5345","script_name":"vim-header","1":"vim-header","script_type":"utility","2":"utility","summary":"Easily Adds Brief Author Info and License Headers","3":"Easily Adds Brief Author Info and License Headers","description":"Easily adds brief author info and license headers at the top of your buffer.\r\n\r\nFor more information and latest version https:\/\/github.com\/alpertuna\/vim-header","4":"Easily adds brief author info and license headers at the top of your buffer.\r\n\r\nFor more information and latest version https:\/\/github.com\/alpertuna\/vim-header","install_details":"Preferred installation method is Pathogen to get latest version\r\ncd ~\/.vim\/bundle\r\ngit clone https:\/\/github.com\/alpertuna\/vim-header\r\n\r\nOr you can extract tarball in your vim plugin folder.","5":"Preferred installation method is Pathogen to get latest version\r\ncd ~\/.vim\/bundle\r\ngit clone https:\/\/github.com\/alpertuna\/vim-header\r\n\r\nOr you can extract tarball in your vim plugin folder.","first_name":"H.Alper","6":"H.Alper","last_name":"Tuna","7":"Tuna","releases":[{"0":"5345","vim_version":"7.0","1":"7.0","script_version":"v0.1.0","2":"v0.1.0","version_comment":"Initial upload","3":"Initial upload","package":"vim-header-0.1.0.tar.gz","4":"vim-header-0.1.0.tar.gz","src_id":"24099","5":"24099","creation_date":"1457889110","6":"1457889110"}]},"5344":{"script_id":"5344","0":"5344","script_name":"KRL-Syntax","1":"KRL-Syntax","script_type":"syntax","2":"syntax","summary":"Syntax, indent and more for Kuka industrial robots","3":"Syntax, indent and more for Kuka industrial robots","description":"KRL for Vim (7.4 to 8.x) is a collection of Vim scripts to help programing KUKA industrial robots (https:\/\/www.kuka.com\/en-de\/products\/robot-systems\/industrial-robots). \r\n\r\nIt provides\r\n\r\n*    syntax highlighting,\r\n*    indenting,\r\n*    folding,\r\n*    support for commentary vimscript #3695, matchit vimscript #39 and matchup vimscript #5624,\r\n*    mappings and settings to navigate through code in a backup folder structure,\r\n*    text objects for functions and folds,\r\n*    optimized folding and concealing for viewing VRKC and\r\n*    completion of words from known or custom global files like $config.dat,\r\n*    mappings to insert a body of a new DEF, DEFFCT or DEFDAT based on user defined templates or hopefully sane defaults.\r\n\r\nNote: Keep your files to be edited in one folder or in a regular robot backup folder structure. KRL for Vim modifies 'path' accordingly. Since version 2.0.0 KRC1 backups are supported too.\r\nNote to Linux users: Keep your files to be edited on a FAT file system. Some features need the case insensitive file system to work properly.\r\n\r\nSee https:\/\/github.com\/KnoP-01\/krl-for-vim#FAQ on how to use more than just highlight and indent.","4":"KRL for Vim (7.4 to 8.x) is a collection of Vim scripts to help programing KUKA industrial robots (https:\/\/www.kuka.com\/en-de\/products\/robot-systems\/industrial-robots). \r\n\r\nIt provides\r\n\r\n*    syntax highlighting,\r\n*    indenting,\r\n*    folding,\r\n*    support for commentary vimscript #3695, matchit vimscript #39 and matchup vimscript #5624,\r\n*    mappings and settings to navigate through code in a backup folder structure,\r\n*    text objects for functions and folds,\r\n*    optimized folding and concealing for viewing VRKC and\r\n*    completion of words from known or custom global files like $config.dat,\r\n*    mappings to insert a body of a new DEF, DEFFCT or DEFDAT based on user defined templates or hopefully sane defaults.\r\n\r\nNote: Keep your files to be edited in one folder or in a regular robot backup folder structure. KRL for Vim modifies 'path' accordingly. Since version 2.0.0 KRC1 backups are supported too.\r\nNote to Linux users: Keep your files to be edited on a FAT file system. Some features need the case insensitive file system to work properly.\r\n\r\nSee https:\/\/github.com\/KnoP-01\/krl-for-vim#FAQ on how to use more than just highlight and indent.","install_details":"### Installation with vim-plug:  ~\r\nPut this in your .vimrc:  >\r\n\r\n    call plug#begin('~\/.vim\/plugged')\r\n      Plug 'KnoP-01\/krl-for-vim'\r\n    call plug#end()\r\n    syntax off                        \" undo what plug#begin() did to syntax\r\n    filetype plugin indent off  \" undo what plugin#begin() did to filetype\r\n    syntax on                        \" syntax and filetype on in that order\r\n    filetype plugin indent on  \" syntax and filetype on in that order\r\n\r\nFor the first installation run: >\r\n\r\n    :PlugInstall\r\n\r\nUpdate every once in a while with: >\r\n\r\n    :PlugUpdate\r\n\r\n### Manual installation:  ~\r\nExtract the most recent release and copy the folders `\/doc`, `\/ftdetect`, `\/ftplugin`, `\/indent` and `\/syntax`  into your `~\/.vim\/` or `%USERPROFILE%\\vimfiles\\` directory. Overwrite krl.* files from older installation. \r\nPut the following in your .vimrc: >\r\n\r\n    syntax on                        \" syntax and filetype on in that order\r\n    filetype plugin indent on  \" syntax and filetype on in that order\r\n\r\nYou may have to run >\r\n\r\n    :helptags ~\/.vim\/doc\/\r\n\r\nor >\r\n\r\n    :helptags ~\/vimfiles\/doc\/\r\n\r\nto use the help within Vim after installation. >\r\n\r\n    :help krl","5":"### Installation with vim-plug:  ~\r\nPut this in your .vimrc:  >\r\n\r\n    call plug#begin('~\/.vim\/plugged')\r\n      Plug 'KnoP-01\/krl-for-vim'\r\n    call plug#end()\r\n    syntax off                        \" undo what plug#begin() did to syntax\r\n    filetype plugin indent off  \" undo what plugin#begin() did to filetype\r\n    syntax on                        \" syntax and filetype on in that order\r\n    filetype plugin indent on  \" syntax and filetype on in that order\r\n\r\nFor the first installation run: >\r\n\r\n    :PlugInstall\r\n\r\nUpdate every once in a while with: >\r\n\r\n    :PlugUpdate\r\n\r\n### Manual installation:  ~\r\nExtract the most recent release and copy the folders `\/doc`, `\/ftdetect`, `\/ftplugin`, `\/indent` and `\/syntax`  into your `~\/.vim\/` or `%USERPROFILE%\\vimfiles\\` directory. Overwrite krl.* files from older installation. \r\nPut the following in your .vimrc: >\r\n\r\n    syntax on                        \" syntax and filetype on in that order\r\n    filetype plugin indent on  \" syntax and filetype on in that order\r\n\r\nYou may have to run >\r\n\r\n    :helptags ~\/.vim\/doc\/\r\n\r\nor >\r\n\r\n    :helptags ~\/vimfiles\/doc\/\r\n\r\nto use the help within Vim after installation. >\r\n\r\n    :help krl","first_name":"Patrick","6":"Patrick","last_name":"Meiser-Knosowski","7":"Meiser-Knosowski","releases":[{"0":"5344","vim_version":"7.4","1":"7.4","script_version":"v2.2.9","2":"v2.2.9","version_comment":"* List use on enum name skipped enum declaration and some more minor fixes","3":"* List use on enum name skipped enum declaration and some more minor fixes","package":"krl-for-vim-2.2.9.zip","4":"krl-for-vim-2.2.9.zip","src_id":"28343","5":"28343","creation_date":"1673395676","6":"1673395676"},{"0":"5344","vim_version":"7.4","1":"7.4","script_version":"v2.2.6","2":"v2.2.6","version_comment":"* Fix: Catch E479\r\n* Add 'bin' and 'binin' to be highlighted in folds","3":"* Fix: Catch E479\r\n* Add 'bin' and 'binin' to be highlighted in folds","package":"krl-for-vim-2.2.6.zip","4":"krl-for-vim-2.2.6.zip","src_id":"27892","5":"27892","creation_date":"1641414060","6":"1641414060"},{"0":"5344","vim_version":"7.4","1":"7.4","script_version":"v2.2.5","2":"v2.2.5","version_comment":"* Fix g:krlKeyWord usage\r\n* Make Go Definition for vkrc binin case insensitive\r\n* Use quickfixtextfunc instead of temp file\r\n* Raise chars of shortened path in quickfix window from 3 to 5 for\r\n    readability\r\n* Use argument for bufnr(), compatiblity with vim <=8.1\r\n* Add missing safe robot build in functions\r\n* Refactor 'path' generation\r\n* Enable spell checking only for comments and strings\r\n* Highlight more stuff in fold lines, especially, but not only, for Vkrc\r\n* Fix integer highlight","3":"* Fix g:krlKeyWord usage\r\n* Make Go Definition for vkrc binin case insensitive\r\n* Use quickfixtextfunc instead of temp file\r\n* Raise chars of shortened path in quickfix window from 3 to 5 for\r\n    readability\r\n* Use argument for bufnr(), compatiblity with vim <=8.1\r\n* Add missing safe robot build in functions\r\n* Refactor 'path' generation\r\n* Enable spell checking only for comments and strings\r\n* Highlight more stuff in fold lines, especially, but not only, for Vkrc\r\n* Fix integer highlight","package":"krl-for-vim-2.2.5.zip","4":"krl-for-vim-2.2.5.zip","src_id":"27868","5":"27868","creation_date":"1640332716","6":"1640332716"},{"0":"5344","vim_version":"7.4","1":"7.4","script_version":"v2.2.2","2":"v2.2.2","version_comment":"* Fix BRAKE highlight\r\n* Fix setlocal foldmethod=marker if syntax is off\r\n* Fix Indent and Auto Form: Accept $ as first character of DEF names\r\n* Fix Auto Form: Don't add GLOBAL if new body starts at line 1\r\n* Fix case sensitivity of file name extentions\r\n* Fix bug in Fold Text Object\r\n* Feature for folding mappings: Enable those mappings (default F2-F4)\r\n  also if g:krlFoldLevel is equal to 0\r\n* Feature for Endwise: Automatically detect upper\/lower case\r\n  (abandoning g:krlEndwiseUpperCase)\r\n* Feature for List Usage: List ENUM values in their declaration\r\n* Feature for Go To Definition: Make look up for definition on ENUM\r\n  values possible","3":"* Fix BRAKE highlight\r\n* Fix setlocal foldmethod=marker if syntax is off\r\n* Fix Indent and Auto Form: Accept $ as first character of DEF names\r\n* Fix Auto Form: Don't add GLOBAL if new body starts at line 1\r\n* Fix case sensitivity of file name extentions\r\n* Fix bug in Fold Text Object\r\n* Feature for folding mappings: Enable those mappings (default F2-F4)\r\n  also if g:krlFoldLevel is equal to 0\r\n* Feature for Endwise: Automatically detect upper\/lower case\r\n  (abandoning g:krlEndwiseUpperCase)\r\n* Feature for List Usage: List ENUM values in their declaration\r\n* Feature for Go To Definition: Make look up for definition on ENUM\r\n  values possible","package":"krl-for-vim-2.2.2.zip","4":"krl-for-vim-2.2.2.zip","src_id":"27402","5":"27402","creation_date":"1608107948","6":"1608107948"},{"0":"5344","vim_version":"7.4","1":"7.4","script_version":"2.1.2","2":"2.1.2","version_comment":"* fix bug where gd does not always work on global def\/deffct (appeared in Vim version 8.2)","3":"* fix bug where gd does not always work on global def\/deffct (appeared in Vim version 8.2)","package":"krl-for-vim-2.1.2.zip","4":"krl-for-vim-2.1.2.zip","src_id":"26921","5":"26921","creation_date":"1579241695","6":"1579241695"},{"0":"5344","vim_version":"7.4","1":"7.4","script_version":"2.1.1","2":"2.1.1","version_comment":"*    add missing KSS functions\r\n*    add $config.dat etc to 'complete', customizable (see :help krl-complete)","3":"*    add missing KSS functions\r\n*    add $config.dat etc to 'complete', customizable (see :help krl-complete)","package":"krl-for-vim-2.1.1.zip","4":"krl-for-vim-2.1.1.zip","src_id":"26869","5":"26869","creation_date":"1576285537","6":"1576285537"},{"0":"5344","vim_version":"7.3","1":"7.3","script_version":"2.0.1","2":"2.0.1","version_comment":"* Fix bug where unnamed buffers are created for each use of gd, f and u\r\n* Fix fold text object\r\n* Clarifications and fixes in documentation","3":"* Fix bug where unnamed buffers are created for each use of gd, f and u\r\n* Fix fold text object\r\n* Clarifications and fixes in documentation","package":"krl-for-vim-2.0.1.zip","4":"krl-for-vim-2.0.1.zip","src_id":"26792","5":"26792","creation_date":"1571785131","6":"1571785131"},{"0":"5344","vim_version":"7.4","1":"7.4","script_version":"2.0.0","2":"2.0.0","version_comment":"* enable most features by default\r\n* change default fold method to syntax to make it case insensitive\r\n* add text objects for DEF\/DEFFCT, folds and comment blocks\r\n* [[, [], ... work in operator pending mode\r\n* add support of KRC1 archives","3":"* enable most features by default\r\n* change default fold method to syntax to make it case insensitive\r\n* add text objects for DEF\/DEFFCT, folds and comment blocks\r\n* [[, [], ... work in operator pending mode\r\n* add support of KRC1 archives","package":"krl-for-vim-2.0.0.zip","4":"krl-for-vim-2.0.0.zip","src_id":"26473","5":"26473","creation_date":"1556573414","6":"1556573414"},{"0":"5344","vim_version":"7.4","1":"7.4","script_version":"1.5.5","2":"1.5.5","version_comment":"* added more spline instructions\r\n* added kss functions and data types\r\n* highlight of vars and funcs >24 chars as error\r\n* highlight of \"interrupt  on\" as error\r\n* fixed minor highlight bug","3":"* added more spline instructions\r\n* added kss functions and data types\r\n* highlight of vars and funcs >24 chars as error\r\n* highlight of \"interrupt  on\" as error\r\n* fixed minor highlight bug","package":"krl-for-vim-1.5.5.zip","4":"krl-for-vim-1.5.5.zip","src_id":"25698","5":"25698","creation_date":"1512755157","6":"1512755157"},{"0":"5344","vim_version":"7.4","1":"7.4","script_version":"1.5.2","2":"1.5.2","version_comment":"* changed highlight to highlight default in syntax file\r\n* added channel to data types for gd\r\n* fixed bug in ftdetext where a defdat was not recognized when there where two spaces between defdat and the name\r\n* made KrlFormatComments() global again\r\n* changes in help file","3":"* changed highlight to highlight default in syntax file\r\n* added channel to data types for gd\r\n* fixed bug in ftdetext where a defdat was not recognized when there where two spaces between defdat and the name\r\n* made KrlFormatComments() global again\r\n* changes in help file","package":"krl-for-vim-1.5.2.zip","4":"krl-for-vim-1.5.2.zip","src_id":"25634","5":"25634","creation_date":"1509769568","6":"1509769568"},{"0":"5344","vim_version":"7.4","1":"7.4","script_version":"1.5.1","2":"1.5.1","version_comment":"* better path generation\r\n* better temp file handling. Sorry to all linux\/unix users for inconvenience with this one.\r\n* made this script compatible to romainls vim-qf (vimscript#5211)\r\n* fixed some minor bugs","3":"* better path generation\r\n* better temp file handling. Sorry to all linux\/unix users for inconvenience with this one.\r\n* made this script compatible to romainls vim-qf (vimscript#5211)\r\n* fixed some minor bugs","package":"krl_for_vim_v151_20170813.zip","4":"krl_for_vim_v151_20170813.zip","src_id":"25508","5":"25508","creation_date":"1502666273","6":"1502666273"},{"0":"5344","vim_version":"7.0","1":"7.0","script_version":"1.5.0","2":"1.5.0","version_comment":"* improved vkrc support: \r\n  * Go Definition now works on UP\\d+, SPSMAKRO\\d+ and M\\d+ in fold lines\r\n  * improved List Usage for vkrc\r\n* fixed Go Definition for comma separated none value declarations in *.dat files\r\n* fixed e6pos return var name in Auto Form\r\n* fixed array function in Auto Form (e.g. deffct char[24] chName() )","3":"* improved vkrc support: \r\n  * Go Definition now works on UP\\d+, SPSMAKRO\\d+ and M\\d+ in fold lines\r\n  * improved List Usage for vkrc\r\n* fixed Go Definition for comma separated none value declarations in *.dat files\r\n* fixed e6pos return var name in Auto Form\r\n* fixed array function in Auto Form (e.g. deffct char[24] chName() )","package":"krl_for_vim_v150_20170624.zip","4":"krl_for_vim_v150_20170624.zip","src_id":"25342","5":"25342","creation_date":"1498343864","6":"1498343864"},{"0":"5344","vim_version":"7.0","1":"7.0","script_version":"1.4.5","2":"1.4.5","version_comment":"* fixed bug in matchit (vimscript #39) support","3":"* fixed bug in matchit (vimscript #39) support","package":"krl_for_vim_v145_20170215.zip","4":"krl_for_vim_v145_20170215.zip","src_id":"24971","5":"24971","creation_date":"1487169540","6":"1487169540"},{"0":"5344","vim_version":"7.0","1":"7.0","script_version":"1.4.4","2":"1.4.4","version_comment":"* divided up mappings for f and gd into 2 options: g:krlListDefKeyMap and g:krlGoDefinitionKeyMap\r\n* added option to influence where f and gd open the quickfix window: g:krlRhsQuickfix and g:krlLhsQuickfix\r\n* added  mappings as an alternative to the configuration variables for mappings\r\n* minor changes in syntax file\r\n* added auto form feature. Insert a body for a new deffct with a few key strokes. See help for more details on this\r\n* added mapping u to list all appearances of the word under the cursor if g:krlListUsageKeyMap is set","3":"* divided up mappings for f and gd into 2 options: g:krlListDefKeyMap and g:krlGoDefinitionKeyMap\r\n* added option to influence where f and gd open the quickfix window: g:krlRhsQuickfix and g:krlLhsQuickfix\r\n* added  mappings as an alternative to the configuration variables for mappings\r\n* minor changes in syntax file\r\n* added auto form feature. Insert a body for a new deffct with a few key strokes. See help for more details on this\r\n* added mapping u to list all appearances of the word under the cursor if g:krlListUsageKeyMap is set","package":"krl_for_vim_v144_20161128.zip","4":"krl_for_vim_v144_20161128.zip","src_id":"24769","5":"24769","creation_date":"1480299569","6":"1480299569"},{"0":"5344","vim_version":"7.0","1":"7.0","script_version":"1.3.8","2":"1.3.8","version_comment":"* changes in help file","3":"* changes in help file","package":"krl_for_vim_v138_20161008.zip","4":"krl_for_vim_v138_20161008.zip","src_id":"24601","5":"24601","creation_date":"1475975949","6":"1475975949"},{"0":"5344","vim_version":"7.0","1":"7.0","script_version":"1.3.8","2":"1.3.8","version_comment":"* set proper b:undo_indent and b:undo_ftplugin\r\n* added matchit support (vimscript #39)\r\n* added mappings for [[, ]], ... and gd if g:krlGoDefinitionKeyMap is set\r\n* added 'path', 'suffixes' and 'suffixesadd' settings for :find or gf\r\n* added 'iskeyword' to match $-variables and #-enums\r\n* changed option name from g:krlNoHighlight to g:krlNoHighLink (the old one does still work for compatibility)\r\nFrom 1.3.6 to 1.3.8\r\n* reorganized 'path' for better search results of gd, :find ...\r\n* optimized KrlGoDefinition()\r\n* made embedded $ chars in variable names possible for gd. Embedded $ chars in DEF or DEFFCT names do still not work\r\n* less noise if g:krlNoVerbose is set\r\n* additions to syntax\r\n* added mapping of f to list all DEF and DEFFCT of the current file if g:krlGoDefinitionKeyMap is set","3":"* set proper b:undo_indent and b:undo_ftplugin\r\n* added matchit support (vimscript #39)\r\n* added mappings for [[, ]], ... and gd if g:krlGoDefinitionKeyMap is set\r\n* added 'path', 'suffixes' and 'suffixesadd' settings for :find or gf\r\n* added 'iskeyword' to match $-variables and #-enums\r\n* changed option name from g:krlNoHighlight to g:krlNoHighLink (the old one does still work for compatibility)\r\nFrom 1.3.6 to 1.3.8\r\n* reorganized 'path' for better search results of gd, :find ...\r\n* optimized KrlGoDefinition()\r\n* made embedded $ chars in variable names possible for gd. Embedded $ chars in DEF or DEFFCT names do still not work\r\n* less noise if g:krlNoVerbose is set\r\n* additions to syntax\r\n* added mapping of f to list all DEF and DEFFCT of the current file if g:krlGoDefinitionKeyMap is set","package":"krl_for_vim_v138_20161005.zip","4":"krl_for_vim_v138_20161005.zip","src_id":"24587","5":"24587","creation_date":"1475761929","6":"1475761929"},{"0":"5344","vim_version":"7.0","1":"7.0","script_version":"1.2.4","2":"1.2.4","version_comment":"* fixed a bug where this script caused an error message about a missing function in some installations of vim\r\n* added new highlight group Continue to be able to highlight continue instructions separately if g:krlNoHighlight is set\r\n* this script now setlocal commentstring=;%s for easy use of commentary (vimscript #3695)\r\n* restructured code","3":"* fixed a bug where this script caused an error message about a missing function in some installations of vim\r\n* added new highlight group Continue to be able to highlight continue instructions separately if g:krlNoHighlight is set\r\n* this script now setlocal commentstring=;%s for easy use of commentary (vimscript #3695)\r\n* restructured code","package":"krl_for_vim_v124_20160727.zip","4":"krl_for_vim_v124_20160727.zip","src_id":"24406","5":"24406","creation_date":"1469626002","6":"1469626002"},{"0":"5344","vim_version":"7.0","1":"7.0","script_version":"1.2.0","2":"1.2.0","version_comment":"* added option (g:krlShowError) to highlight some misuses of =, ==, <= and >=\r\n* added ENABLE\/DISABLE (interrupt enable ..) to keywords\r\n","3":"* added option (g:krlShowError) to highlight some misuses of =, ==, <= and >=\r\n* added ENABLE\/DISABLE (interrupt enable ..) to keywords\r\n","package":"krl_for_vim_v120_20160604.zip","4":"krl_for_vim_v120_20160604.zip","src_id":"24303","5":"24303","creation_date":"1464997760","6":"1464997760"},{"0":"5344","vim_version":"7.0","1":"7.0","script_version":"1.1.3","2":"1.1.3","version_comment":"* added help\r\n* added file type detect\r\n* added file type plugin\r\n* added indent file\r\n* made the script configurable by options\r\n* minor changes in syntax file","3":"* added help\r\n* added file type detect\r\n* added file type plugin\r\n* added indent file\r\n* made the script configurable by options\r\n* minor changes in syntax file","package":"krl_for_vim_v113_20160524.zip","4":"krl_for_vim_v113_20160524.zip","src_id":"24266","5":"24266","creation_date":"1464078016","6":"1464078016"},{"0":"5344","vim_version":"7.0","1":"7.0","script_version":"1.1.1","2":"1.1.1","version_comment":"I think I'm getting closer to how a syntax file is supposed to be done. I changed to much to list here. Depending on your colorscheme it might not look very different.\r\nMain changes:\r\n* fixed false highlighting for structure component names\r\n* added more predefined enums and structures, also from some basic tech packages (BasisTech, GripperTech, SpotTech...)\r\n* enum values are now considered Constant (no need for \"highlight Enum ...\" any more)\r\n* devided stuff into sub groups\r\n* added some missing build in functions","3":"I think I'm getting closer to how a syntax file is supposed to be done. I changed to much to list here. Depending on your colorscheme it might not look very different.\r\nMain changes:\r\n* fixed false highlighting for structure component names\r\n* added more predefined enums and structures, also from some basic tech packages (BasisTech, GripperTech, SpotTech...)\r\n* enum values are now considered Constant (no need for \"highlight Enum ...\" any more)\r\n* devided stuff into sub groups\r\n* added some missing build in functions","package":"krl.vim","4":"krl.vim","src_id":"24178","5":"24178","creation_date":"1460680786","6":"1460680786"},{"0":"5344","vim_version":"7.0","1":"7.0","script_version":"0.9","2":"0.9","version_comment":"Initial upload","3":"Initial upload","package":"krl.vim","4":"krl.vim","src_id":"24076","5":"24076","creation_date":"1457327646","6":"1457327646"}]},"5343":{"script_id":"5343","0":"5343","script_name":"Vimliner Outliner","1":"Vimliner Outliner","script_type":"ftplugin","2":"ftplugin","summary":"The smallest, fastest outliner for vim. One file install.","3":"The smallest, fastest outliner for vim. One file install.","description":"Vimliner is the smallest outliner for vim. It uses vim's existing code \r\nfolding capabilities with some simple configuration. The result is a fast,\r\npowerful outliner using your favourite text editor.\r\n\r\nInstall Vimliner by saving this file to $HOME\/.vim\/ftdetect\/vimliner.vim\r\non unix, or $HOME\/vimfiles\/ftdetect\/vimliner.vim on Windows.\r\n\r\nSave your outliner files with a .out extension for Vimliner to be \r\nautodetected. Otherwise, use :set filetype=vimliner from within vim.\r\n\r\nThe outliner uses an indentation level of 2 white spaces to create \r\nnew levels. You can use vim's default code folding shortcuts to move\r\nthroughout your outline, or just use  to open and close levels.\r\n \r\nThe most frequent shortcut keys you will use are:\r\n\r\n   open or close the current fold\r\n  zx  close all other folds  \r\n\r\nUse :help fold-commands in vim for additional shorcuts.\r\n \r\nThe fold function consumes blank lines. If you need to separate one\r\nfold from another, use a string of space characters that match the\r\ncurrent indent level.\r\n\r\nHomepage: https:\/\/rogerkeays.com\/vimliner\r\nLicense: https:\/\/opensource.org\/licenses\/Apache-2.0\r\nAuthor: Roger Keays\r\n","4":"Vimliner is the smallest outliner for vim. It uses vim's existing code \r\nfolding capabilities with some simple configuration. The result is a fast,\r\npowerful outliner using your favourite text editor.\r\n\r\nInstall Vimliner by saving this file to $HOME\/.vim\/ftdetect\/vimliner.vim\r\non unix, or $HOME\/vimfiles\/ftdetect\/vimliner.vim on Windows.\r\n\r\nSave your outliner files with a .out extension for Vimliner to be \r\nautodetected. Otherwise, use :set filetype=vimliner from within vim.\r\n\r\nThe outliner uses an indentation level of 2 white spaces to create \r\nnew levels. You can use vim's default code folding shortcuts to move\r\nthroughout your outline, or just use  to open and close levels.\r\n \r\nThe most frequent shortcut keys you will use are:\r\n\r\n   open or close the current fold\r\n  zx  close all other folds  \r\n\r\nUse :help fold-commands in vim for additional shorcuts.\r\n \r\nThe fold function consumes blank lines. If you need to separate one\r\nfold from another, use a string of space characters that match the\r\ncurrent indent level.\r\n\r\nHomepage: https:\/\/rogerkeays.com\/vimliner\r\nLicense: https:\/\/opensource.org\/licenses\/Apache-2.0\r\nAuthor: Roger Keays\r\n","install_details":"Copy vimliner.vim to $HOME\/.vim\/ftdetect","5":"Copy vimliner.vim to $HOME\/.vim\/ftdetect","first_name":"Roger","6":"Roger","last_name":"Keays","7":"Keays","releases":[{"0":"5343","vim_version":"5.7","1":"5.7","script_version":"1.2","2":"1.2","version_comment":"Renamed to Vimliner to avoid confusion with rival project.","3":"Renamed to Vimliner to avoid confusion with rival project.","package":"vimliner.vim","4":"vimliner.vim","src_id":"27139","5":"27139","creation_date":"1588255489","6":"1588255489"},{"0":"5343","vim_version":"5.7","1":"5.7","script_version":"1.1","2":"1.1","version_comment":"Smaller, faster, and allows you to add white space after the folds. If you are upgrading, you may find additional white space in your existing outlines which you will have to remove manually.","3":"Smaller, faster, and allows you to add white space after the folds. If you are upgrading, you may find additional white space in your existing outlines which you will have to remove manually.","package":"vimflowy.vim","4":"vimflowy.vim","src_id":"27129","5":"27129","creation_date":"1587779275","6":"1587779275"},{"0":"5343","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"vimflowy.vim","4":"vimflowy.vim","src_id":"24069","5":"24069","creation_date":"1457212957","6":"1457212957"}]},"5342":{"script_id":"5342","0":"5342","script_name":"stata-syntax","1":"stata-syntax","script_type":"syntax","2":"syntax","summary":"Enhanced and updated Stata syntax highlighting in Vim","3":"Enhanced and updated Stata syntax highlighting in Vim","description":"----------------------------------------\r\nVim syntax file for Stata source files\r\n----------------------------------------\r\n\r\nThis is an enhanced and updated Stata syntax hilghlighting file. It is a modification version to the Stata\/Mata syntax highlighting file by Jeff Pitblado.\r\n\r\nGithub: https:\/\/github.com\/zizhongyan\/stata-vim-syntax\/\r\n\r\n----------------------------------------\r\nFeatures\r\n----------------------------------------\r\nApart from Pitblado\\'s syntax highlighting file, the file could further highlight\r\n\r\n1. most of the Stata in-built commands,\r\n\r\n2. some popular user-written commands, \r\n\r\n3. abbreviation of commands, \r\n\r\n4. numbers,\r\n\r\n5. logical and mathematic operators. \r\n\r\n6. enable different colours for commands used for different purpose.\r\n\r\n----------------------------------------\r\nScreenshots\r\n----------------------------------------\r\n\r\nPlease visit:  https:\/\/github.com\/zizhongyan\/stata-vim-syntax\/ \r\n\r\n\r\n----------------------------------------\r\nCompatibility\r\n----------------------------------------\r\n\r\nThis syntax highlighting file is also compatible with Stata 14.\r\n\r\nIt is working under both Windows and Unix\/Linux platforms\r\n\r\n----------------------------------------\r\nLooking for running Stata in the Vim ?\r\n----------------------------------------\r\n\r\nIf you want to RUN THE STATA in VIM editor, please refer to \\\"another Github webpage at https:\/\/github.com\/zizhongyan\/vim-stata\/\\\".\r\n\r\n----------------------------------------\r\nTo keep it updated\r\n----------------------------------------\r\n\r\nI will be trying to keep the file updated with more common used Stata commands. Please also let me know if you want to add more syntax highlightings!\r\n\r\nBy Zizhong Yan (helloyzz@gmail.com) and Chuhong Wang (flora7819@gmail.com) --- 29 Feb 2016.","4":"----------------------------------------\r\nVim syntax file for Stata source files\r\n----------------------------------------\r\n\r\nThis is an enhanced and updated Stata syntax hilghlighting file. It is a modification version to the Stata\/Mata syntax highlighting file by Jeff Pitblado.\r\n\r\nGithub: https:\/\/github.com\/zizhongyan\/stata-vim-syntax\/\r\n\r\n----------------------------------------\r\nFeatures\r\n----------------------------------------\r\nApart from Pitblado\\'s syntax highlighting file, the file could further highlight\r\n\r\n1. most of the Stata in-built commands,\r\n\r\n2. some popular user-written commands, \r\n\r\n3. abbreviation of commands, \r\n\r\n4. numbers,\r\n\r\n5. logical and mathematic operators. \r\n\r\n6. enable different colours for commands used for different purpose.\r\n\r\n----------------------------------------\r\nScreenshots\r\n----------------------------------------\r\n\r\nPlease visit:  https:\/\/github.com\/zizhongyan\/stata-vim-syntax\/ \r\n\r\n\r\n----------------------------------------\r\nCompatibility\r\n----------------------------------------\r\n\r\nThis syntax highlighting file is also compatible with Stata 14.\r\n\r\nIt is working under both Windows and Unix\/Linux platforms\r\n\r\n----------------------------------------\r\nLooking for running Stata in the Vim ?\r\n----------------------------------------\r\n\r\nIf you want to RUN THE STATA in VIM editor, please refer to \\\"another Github webpage at https:\/\/github.com\/zizhongyan\/vim-stata\/\\\".\r\n\r\n----------------------------------------\r\nTo keep it updated\r\n----------------------------------------\r\n\r\nI will be trying to keep the file updated with more common used Stata commands. Please also let me know if you want to add more syntax highlightings!\r\n\r\nBy Zizhong Yan (helloyzz@gmail.com) and Chuhong Wang (flora7819@gmail.com) --- 29 Feb 2016.","install_details":"Download it into the syntax folder.  ","5":"Download it into the syntax folder.  ","first_name":"Zizhong","6":"Zizhong","last_name":"Yan","7":"Yan","releases":[{"0":"5342","vim_version":"7.0","1":"7.0","script_version":"0.3","2":"0.3","version_comment":"Initial upload","3":"Initial upload","package":"stata.vim","4":"stata.vim","src_id":"24057","5":"24057","creation_date":"1456723955","6":"1456723955"}]},"5341":{"script_id":"5341","0":"5341","script_name":"thesaurus_query.vim","1":"thesaurus_query.vim","script_type":"utility","2":"utility","summary":"Multi-language Thesaurus Query and Replacement plugin","3":"Multi-language Thesaurus Query and Replacement plugin","description":"`thesaurus_query.vim` is a plugin for user to lookup synonyms of any word\r\nunder cursor or phrase covered in visual mode, and replace it with an user\r\nchosen synonym. It also accepts word\/phrases from manual input for synonym\r\ncheckup. This plugin has multiple backends, currently support English,\r\nChinese (if so configured), German (if so configured) and Russian(if so\r\nconfigured) thesaurus query.\r\n\r\nThis plugin is written in Python, hence it requires Vim built with either\r\n+Python or +Python3 or both. You may check it by using Vim command\r\n    :echo has('python')+has('python3')\r\nIf returned value is larger than `0`, This plugin will be functional.\r\n\r\nScreencast: http:\/\/i.imgur.com\/3QXxUp7.gif\r\n\r\nThis plugin is also hosted on github:\r\n    https:\/\/github.com\/Ron89\/thesaurus_query.vim\r\nIf you meet any problem while using, please come to my github page and report\r\nthe issue, thanks~\r\n\r\n\r\n## How to Use\r\n\r\n1. Most commonly used: under normal mode, `cs` will query the word\r\n   under cursor and attempt to replace the word with user chosen candidate.\r\n       screenshot: http:\/\/i.imgur.com\/LJpdBwD.png\r\n\r\n2. Under visual mode, same key-binding will query the word under cursor and\r\n   attempt to replace the word with user chosen candidate. \r\n\r\n3. You may also query any word by using the command \r\n        :Thesaurus \r\n   result will be displayed in split buffer.(feature inherited from Anton's\r\n   Online Thesaurus plugin)\r\n       screenshot: http:\/\/i.imgur.com\/3B1i8Di.png\r\n\r\n4. You can also use `ctrl-x ctrl-u` insertmode autocomplete function for\r\n   synonym query.\r\n\r\n\r\n## Multi-language query support and Russian Thesaurus backend.\r\n\r\n   Multi-language Thesaurus Query feature is added since Version 0.3.0.\r\n   Currently English, German and Russian are supported. By default, only English\r\n   backends are activated. Users may activate Russian Thesaurus backends by\r\n   ```\r\n   let g:tq_language = 'ru'\r\n   ```\r\n   or activate all English, German and Russian backends by\r\n   ```\r\n   let g:tq_language = ['de', 'ru', 'en']\r\n   ```\r\n   For detail, please refer to my [Documentation](https:\/\/github.com\/Ron89\/thesaurus_query.vim\/blob\/master\/doc\/thesaurus_query.txt).\r\n\r\n\r\n## About Its Backends:\r\n\r\nAnother feature of this plugin is that under the hood, the plugin uses multiple\r\nbackends sequentially to query for a synonym. To successfully query a synonym,\r\nat least one of the three backends need to function properly.\r\n\r\n* `thesaurus_com`: queries from `http:\/\/thesaurus.com\/` for\r\n  synonym, so internet connection is required for this backend's functionality.\r\n  The returned synonym list from this source has very high quality. But since\r\n  `thesaurus.com` didn't actually provide official API. The functionality of\r\n  this backend might fail when the website changes its design.\r\n\r\n* `datamuse_com` queries from `http:\/\/www.datamuse.com` using its officially\r\n  provided API. The returned synonym list is usually quite relavant with\r\n  reasonable quality. But the synonyms list tend to be short, so it might leave\r\n  out some less-frequently-used synonyms. \r\n\r\n* `mthesaur_txt` queries from local `mthesaur.txt`. It is an useful option when\r\n  you don't have any internet access at all. For this backend to work, be sure\r\n  to download the file from `http:\/\/www.gutenberg.org\/files\/3202\/files\/` and\r\n  place it under \"~\/.vim\/thesaurus\". If you place the file elsewhere, change\r\n  global variable |g:thesaurus_query#mthesaur_file| to point to the file you\r\n  downloaded, eg. put the following line `let\r\n  g:tq_mthesaur_file=\"~\/.config\/nvim\/thesaurus\/mthesaur.txt\"` into\r\n  your `.vimrc` file if your `mthesaur.txt` is placed in folder\r\n  \"~\/.config\/nvim\/thesaurus\/\".\r\n\r\n* `cilin_txt` queries from local `cilin.txt`. It makes use of a Chinese\r\n  thesaurus source \"cilin.txt\". For this backend to\r\n  work, be sure to download the file from\r\n  `https:\/\/github.com\/shijiebei2009\/Algorithms\/blob\/master\/src\/main\/resources\/cilin.txt`\r\n  and place it under \"~\/.vim\/thesaurus\". If you place the file elsewhere,\r\n  change global variable |g:tq_cilin_txt_file| to point to the file you\r\n  downloaded, eg. put the following line `let\r\n  g:tq_cilin_txt_file=\"~\/.config\/nvim\/thesaurus\/cilin.txt\"` into your `.vimrc`\r\n  file if your `cilin.txt` is placed in folder \"~\/.config\/nvim\/thesaurus\/\".\r\n  Note that if you downloaded \"cilin.txt\" from elsewhere, make sure that your\r\n  source `cilin.txt` is utf-8 encoded. Or the plugin won't function correctly\r\n  with the file.\r\n\r\n* `yarn_synsets` is a Russian thesaurus backend. It uses \r\n  [yarn-synsets.csv](http:\/\/russianword.net\/yarn-synsets.csv) as synonym\r\n  resource, providing a fast responding and decent thesaurus query solution.\r\n  Please place `yarn-synsets.csv` in `~\/.vim\/thesaurus`, or use variable\r\n  `g:tq_yarn_synsets_file` to indicate the location of `yarn-synsets.csv` in\r\n  your system.\r\n\r\n* `jeck_ru` is a Russian thesaurus backend. It queries\r\n  [jeck.ru](http:\/\/jeck.ru\/tools\/SynonymsDictionary) for synonym resources.\r\n  This website didn't provide standard API to use. Hence functionality of this\r\n  backend depends on whether the website owner will change the webpage design.\r\n\r\n* `woxikon_de` is a German thesaurus backend. It queries\r\n  [woxikon.de](http:\/\/synonyme.woxikon.de\/synonyme) for synonym resources. This\r\n  website didn't provide standard API to use. Hence functionality of this\r\n  backend depends on whether the website owner will change the webpage design.\r\n\r\n## Requirement\r\n\r\n  * Tested to be working on vim 7.3 or newer.\r\n  * The plugin is written in python, `+python` support version of Vim is\r\n    required.\r\n  * At least one of the below requirements need to be met:\r\n      + For online query backends to work, Internet connection is required;\r\n      + For `mthesaur_txt` backend to work, `mthesaur.txt` is required.\r\n\r\n## Credit:\r\n\r\nThis plugin is functionally based on and extended from the ideas behind\r\nvim-online-thesaurus by Anton Beloglazov:\r\n    http:\/\/www.vim.org\/scripts\/script.php?script_id=4588. \r\nSeveral key improvements were made comparing to his plugin:\r\n - added synonym replacing mechanism\r\n - added fallback backend to ensure functionality even when server down or lack\r\n   of internet connection.\r\n - added multilanguage support. With proper backends, it is possible to extend\r\n   the functionality of this plugin to any western letter based languages.\r\n","4":"`thesaurus_query.vim` is a plugin for user to lookup synonyms of any word\r\nunder cursor or phrase covered in visual mode, and replace it with an user\r\nchosen synonym. It also accepts word\/phrases from manual input for synonym\r\ncheckup. This plugin has multiple backends, currently support English,\r\nChinese (if so configured), German (if so configured) and Russian(if so\r\nconfigured) thesaurus query.\r\n\r\nThis plugin is written in Python, hence it requires Vim built with either\r\n+Python or +Python3 or both. You may check it by using Vim command\r\n    :echo has('python')+has('python3')\r\nIf returned value is larger than `0`, This plugin will be functional.\r\n\r\nScreencast: http:\/\/i.imgur.com\/3QXxUp7.gif\r\n\r\nThis plugin is also hosted on github:\r\n    https:\/\/github.com\/Ron89\/thesaurus_query.vim\r\nIf you meet any problem while using, please come to my github page and report\r\nthe issue, thanks~\r\n\r\n\r\n## How to Use\r\n\r\n1. Most commonly used: under normal mode, `cs` will query the word\r\n   under cursor and attempt to replace the word with user chosen candidate.\r\n       screenshot: http:\/\/i.imgur.com\/LJpdBwD.png\r\n\r\n2. Under visual mode, same key-binding will query the word under cursor and\r\n   attempt to replace the word with user chosen candidate. \r\n\r\n3. You may also query any word by using the command \r\n        :Thesaurus \r\n   result will be displayed in split buffer.(feature inherited from Anton's\r\n   Online Thesaurus plugin)\r\n       screenshot: http:\/\/i.imgur.com\/3B1i8Di.png\r\n\r\n4. You can also use `ctrl-x ctrl-u` insertmode autocomplete function for\r\n   synonym query.\r\n\r\n\r\n## Multi-language query support and Russian Thesaurus backend.\r\n\r\n   Multi-language Thesaurus Query feature is added since Version 0.3.0.\r\n   Currently English, German and Russian are supported. By default, only English\r\n   backends are activated. Users may activate Russian Thesaurus backends by\r\n   ```\r\n   let g:tq_language = 'ru'\r\n   ```\r\n   or activate all English, German and Russian backends by\r\n   ```\r\n   let g:tq_language = ['de', 'ru', 'en']\r\n   ```\r\n   For detail, please refer to my [Documentation](https:\/\/github.com\/Ron89\/thesaurus_query.vim\/blob\/master\/doc\/thesaurus_query.txt).\r\n\r\n\r\n## About Its Backends:\r\n\r\nAnother feature of this plugin is that under the hood, the plugin uses multiple\r\nbackends sequentially to query for a synonym. To successfully query a synonym,\r\nat least one of the three backends need to function properly.\r\n\r\n* `thesaurus_com`: queries from `http:\/\/thesaurus.com\/` for\r\n  synonym, so internet connection is required for this backend's functionality.\r\n  The returned synonym list from this source has very high quality. But since\r\n  `thesaurus.com` didn't actually provide official API. The functionality of\r\n  this backend might fail when the website changes its design.\r\n\r\n* `datamuse_com` queries from `http:\/\/www.datamuse.com` using its officially\r\n  provided API. The returned synonym list is usually quite relavant with\r\n  reasonable quality. But the synonyms list tend to be short, so it might leave\r\n  out some less-frequently-used synonyms. \r\n\r\n* `mthesaur_txt` queries from local `mthesaur.txt`. It is an useful option when\r\n  you don't have any internet access at all. For this backend to work, be sure\r\n  to download the file from `http:\/\/www.gutenberg.org\/files\/3202\/files\/` and\r\n  place it under \"~\/.vim\/thesaurus\". If you place the file elsewhere, change\r\n  global variable |g:thesaurus_query#mthesaur_file| to point to the file you\r\n  downloaded, eg. put the following line `let\r\n  g:tq_mthesaur_file=\"~\/.config\/nvim\/thesaurus\/mthesaur.txt\"` into\r\n  your `.vimrc` file if your `mthesaur.txt` is placed in folder\r\n  \"~\/.config\/nvim\/thesaurus\/\".\r\n\r\n* `cilin_txt` queries from local `cilin.txt`. It makes use of a Chinese\r\n  thesaurus source \"cilin.txt\". For this backend to\r\n  work, be sure to download the file from\r\n  `https:\/\/github.com\/shijiebei2009\/Algorithms\/blob\/master\/src\/main\/resources\/cilin.txt`\r\n  and place it under \"~\/.vim\/thesaurus\". If you place the file elsewhere,\r\n  change global variable |g:tq_cilin_txt_file| to point to the file you\r\n  downloaded, eg. put the following line `let\r\n  g:tq_cilin_txt_file=\"~\/.config\/nvim\/thesaurus\/cilin.txt\"` into your `.vimrc`\r\n  file if your `cilin.txt` is placed in folder \"~\/.config\/nvim\/thesaurus\/\".\r\n  Note that if you downloaded \"cilin.txt\" from elsewhere, make sure that your\r\n  source `cilin.txt` is utf-8 encoded. Or the plugin won't function correctly\r\n  with the file.\r\n\r\n* `yarn_synsets` is a Russian thesaurus backend. It uses \r\n  [yarn-synsets.csv](http:\/\/russianword.net\/yarn-synsets.csv) as synonym\r\n  resource, providing a fast responding and decent thesaurus query solution.\r\n  Please place `yarn-synsets.csv` in `~\/.vim\/thesaurus`, or use variable\r\n  `g:tq_yarn_synsets_file` to indicate the location of `yarn-synsets.csv` in\r\n  your system.\r\n\r\n* `jeck_ru` is a Russian thesaurus backend. It queries\r\n  [jeck.ru](http:\/\/jeck.ru\/tools\/SynonymsDictionary) for synonym resources.\r\n  This website didn't provide standard API to use. Hence functionality of this\r\n  backend depends on whether the website owner will change the webpage design.\r\n\r\n* `woxikon_de` is a German thesaurus backend. It queries\r\n  [woxikon.de](http:\/\/synonyme.woxikon.de\/synonyme) for synonym resources. This\r\n  website didn't provide standard API to use. Hence functionality of this\r\n  backend depends on whether the website owner will change the webpage design.\r\n\r\n## Requirement\r\n\r\n  * Tested to be working on vim 7.3 or newer.\r\n  * The plugin is written in python, `+python` support version of Vim is\r\n    required.\r\n  * At least one of the below requirements need to be met:\r\n      + For online query backends to work, Internet connection is required;\r\n      + For `mthesaur_txt` backend to work, `mthesaur.txt` is required.\r\n\r\n## Credit:\r\n\r\nThis plugin is functionally based on and extended from the ideas behind\r\nvim-online-thesaurus by Anton Beloglazov:\r\n    http:\/\/www.vim.org\/scripts\/script.php?script_id=4588. \r\nSeveral key improvements were made comparing to his plugin:\r\n - added synonym replacing mechanism\r\n - added fallback backend to ensure functionality even when server down or lack\r\n   of internet connection.\r\n - added multilanguage support. With proper backends, it is possible to extend\r\n   the functionality of this plugin to any western letter based languages.\r\n","install_details":"## Manual Install\r\n\r\n1. Untar the package, using `tar -xf [downloaded-package-name]` or otherwise.\r\n2. Go into the extracted folder.\r\n    * For Vim users, copy the folder `plugin`, `autoload`, `syntax` and `doc`\r\n      into your `~\/.vim` folder;\r\n    * For NeoVim users, copy the folder `plugin` `autoload` `syntax` and `doc`\r\n      into your `~\/.config\/nvim` folder.\r\nThe software you use should recognize the plugin files correctly.\r\n\r\n\r\n## Using Package Manager\r\n\r\nFor the ease of organizing and future update, the using of package manager is\r\nrecommended. Here is an installation instruction for some of the most popular\r\npackage managers.\r\n\r\n *  Pathogen\r\n        git clone https:\/\/github.com\/ron89\/thesaurus_query.vim ~\/.vim\/bundle\/thesaurus_query.vim\r\n *  Vundle\r\n        Add to .vimrc:\r\n            Bundle 'ron89\/thesaurus_query.vim'\r\n        Run\r\n            :BundleInstall\r\n *  NeoBundle\r\n        Add to .vimrc:\r\n            NeoBundle 'ron89\/thesaurus_query.vim'\r\n        Run\r\n            :NeoBundleInstall\r\n *  vim-plug\r\n        Add to .vimrc:\r\n            Plug 'ron89\/thesaurus_query.vim'\r\n        Run\r\n            :PlugInstall\r\n\r\n## If you are using Arch flavor linux. You may also install the plugin from AUR:\r\n    https:\/\/aur.archlinux.org\/packages\/vim-thesaurus_query\/\r\n    https:\/\/aur.archlinux.org\/packages\/nvim-thesaurus_query\/","5":"## Manual Install\r\n\r\n1. Untar the package, using `tar -xf [downloaded-package-name]` or otherwise.\r\n2. Go into the extracted folder.\r\n    * For Vim users, copy the folder `plugin`, `autoload`, `syntax` and `doc`\r\n      into your `~\/.vim` folder;\r\n    * For NeoVim users, copy the folder `plugin` `autoload` `syntax` and `doc`\r\n      into your `~\/.config\/nvim` folder.\r\nThe software you use should recognize the plugin files correctly.\r\n\r\n\r\n## Using Package Manager\r\n\r\nFor the ease of organizing and future update, the using of package manager is\r\nrecommended. Here is an installation instruction for some of the most popular\r\npackage managers.\r\n\r\n *  Pathogen\r\n        git clone https:\/\/github.com\/ron89\/thesaurus_query.vim ~\/.vim\/bundle\/thesaurus_query.vim\r\n *  Vundle\r\n        Add to .vimrc:\r\n            Bundle 'ron89\/thesaurus_query.vim'\r\n        Run\r\n            :BundleInstall\r\n *  NeoBundle\r\n        Add to .vimrc:\r\n            NeoBundle 'ron89\/thesaurus_query.vim'\r\n        Run\r\n            :NeoBundleInstall\r\n *  vim-plug\r\n        Add to .vimrc:\r\n            Plug 'ron89\/thesaurus_query.vim'\r\n        Run\r\n            :PlugInstall\r\n\r\n## If you are using Arch flavor linux. You may also install the plugin from AUR:\r\n    https:\/\/aur.archlinux.org\/packages\/vim-thesaurus_query\/\r\n    https:\/\/aur.archlinux.org\/packages\/nvim-thesaurus_query\/","first_name":"Chong","6":"Chong","last_name":"HE","7":"HE","releases":[{"0":"5341","vim_version":"7.3","1":"7.3","script_version":"0.7.0","2":"0.7.0","version_comment":"- Added French Backends using online source `cnrtl.fr` and `synonymo.fr`\r\n- Added German synonym backend based on `openthesaurus.de`, backend identifier `openthesaurus_de`\r\n- Fixed some bugs\r\n- Added `datamuse_en` into default backends list.\r\n- Removed defunc backends such as `thesaurus.com` and `woxikon.de` from default backend list.","3":"- Added French Backends using online source `cnrtl.fr` and `synonymo.fr`\r\n- Added German synonym backend based on `openthesaurus.de`, backend identifier `openthesaurus_de`\r\n- Fixed some bugs\r\n- Added `datamuse_en` into default backends list.\r\n- Removed defunc backends such as `thesaurus.com` and `woxikon.de` from default backend list.","package":"thesaurus_query.vim-0.7.0.tar.gz","4":"thesaurus_query.vim-0.7.0.tar.gz","src_id":"26815","5":"26815","creation_date":"1573322175","6":"1573322175"},{"0":"5341","vim_version":"7.0","1":"7.0","script_version":"0.6.3","2":"0.6.3","version_comment":"Add datamuse.com as one of the default backend to alleviate the problem caused by change in thesaurus.com.","3":"Add datamuse.com as one of the default backend to alleviate the problem caused by change in thesaurus.com.","package":"thesaurus_query.vim-0.6.3.zip","4":"thesaurus_query.vim-0.6.3.zip","src_id":"25985","5":"25985","creation_date":"1526844079","6":"1526844079"},{"0":"5341","vim_version":"7.0","1":"7.0","script_version":"v0.6.2","2":"v0.6.2","version_comment":"fix an unusable variable used to configure source file of Russian synonym backend: change `g:tq_yarn-synsets_file` into `g:tq_yarn_synsets_file`.","3":"fix an unusable variable used to configure source file of Russian synonym backend: change `g:tq_yarn-synsets_file` into `g:tq_yarn_synsets_file`.","package":"thesaurus_query.vim-0.6.2.tar.gz","4":"thesaurus_query.vim-0.6.2.tar.gz","src_id":"25387","5":"25387","creation_date":"1499699893","6":"1499699893"},{"0":"5341","vim_version":"7.3","1":"7.3","script_version":"v0.6.1","2":"v0.6.1","version_comment":"Fix issues of woxikon_de backend due to website design change","3":"Fix issues of woxikon_de backend due to website design change","package":"thesaurus_query.vim-0.6.1.tar.gz","4":"thesaurus_query.vim-0.6.1.tar.gz","src_id":"24932","5":"24932","creation_date":"1485625128","6":"1485625128"},{"0":"5341","vim_version":"7.3","1":"7.3","script_version":"0.6.0","2":"0.6.0","version_comment":"Add interactive backend switching; Add Chinese backend; Add OpenOffice based English backend; Fix bug that make thesaurus replacing feature malfunction for non-English language.","3":"Add interactive backend switching; Add Chinese backend; Add OpenOffice based English backend; Fix bug that make thesaurus replacing feature malfunction for non-English language.","package":"thesaurus_query.vim-0.6.0.tar.gz","4":"thesaurus_query.vim-0.6.0.tar.gz","src_id":"24580","5":"24580","creation_date":"1475391022","6":"1475391022"},{"0":"5341","vim_version":"7.3","1":"7.3","script_version":"v0.5.1","2":"v0.5.1","version_comment":"#Added# `openoffice_en` backend, using OpenOffice's thesaurus extension as thesaurus source.\r\n#Fixed# Bugs in source checking logic of `mthesaur_txt` routine when variable `&thesaurus` is searched\r\n","3":"#Added# `openoffice_en` backend, using OpenOffice's thesaurus extension as thesaurus source.\r\n#Fixed# Bugs in source checking logic of `mthesaur_txt` routine when variable `&thesaurus` is searched\r\n","package":"thesaurus_query.vim-0.5.1.tar.gz","4":"thesaurus_query.vim-0.5.1.tar.gz","src_id":"24483","5":"24483","creation_date":"1472563163","6":"1472563163"},{"0":"5341","vim_version":"7.3","1":"7.3","script_version":"v0.5.0","2":"v0.5.0","version_comment":"dynamic backend managing; split buffer display improvement; phrase replacing algorithm improvement.","3":"dynamic backend managing; split buffer display improvement; phrase replacing algorithm improvement.","package":"thesaurus_query.vim-0.5.0.tar.gz","4":"thesaurus_query.vim-0.5.0.tar.gz","src_id":"24389","5":"24389","creation_date":"1469347562","6":"1469347562"},{"0":"5341","vim_version":"7.3","1":"7.3","script_version":"0.4.1","2":"0.4.1","version_comment":"Fix a bug that prevent the plugin from function properly with Python2.6","3":"Fix a bug that prevent the plugin from function properly with Python2.6","package":"thesaurus_query.vim-0.4.1.tar.gz","4":"thesaurus_query.vim-0.4.1.tar.gz","src_id":"24339","5":"24339","creation_date":"1466509644","6":"1466509644"},{"0":"5341","vim_version":"7.3","1":"7.3","script_version":"0.4.0","2":"0.4.0","version_comment":"Added customizable timeout mechanism. \r\nVisual mode query now also provide replacement functionality.\r\nRemoved datamuse.com from default backend list (to improve performance). \r\nImproved coloring.\r\nMinor bug fixings.","3":"Added customizable timeout mechanism. \r\nVisual mode query now also provide replacement functionality.\r\nRemoved datamuse.com from default backend list (to improve performance). \r\nImproved coloring.\r\nMinor bug fixings.","package":"thesaurus_query.vim-0.4.0.tar.gz","4":"thesaurus_query.vim-0.4.0.tar.gz","src_id":"24295","5":"24295","creation_date":"1464756160","6":"1464756160"},{"0":"5341","vim_version":"7.3","1":"7.3","script_version":"0.3.5","2":"0.3.5","version_comment":"Fixed multiple issues with ctrl-x ctrl-u bound insert-mode thesaurus query:\r\n-- fix the bug making feature not responsive with Python3 built vim.\r\n-- tab symbol '\\t' now excluded from recognized word\r\n-- invoking after non-word symbol now return empty list rather than exception.","3":"Fixed multiple issues with ctrl-x ctrl-u bound insert-mode thesaurus query:\r\n-- fix the bug making feature not responsive with Python3 built vim.\r\n-- tab symbol '\\t' now excluded from recognized word\r\n-- invoking after non-word symbol now return empty list rather than exception.","package":"thesaurus_query.vim-0.3.5.tar.gz","4":"thesaurus_query.vim-0.3.5.tar.gz","src_id":"24260","5":"24260","creation_date":"1463884041","6":"1463884041"},{"0":"5341","vim_version":"7.3","1":"7.3","script_version":"0.3.4","2":"0.3.4","version_comment":"Now support mid-session change of all (except for keymapping related ) variables. \r\nTo make backend changing take effect, `:ThesaurusQueryReset` after changing `g:tq_enabled_backends`","3":"Now support mid-session change of all (except for keymapping related ) variables. \r\nTo make backend changing take effect, `:ThesaurusQueryReset` after changing `g:tq_enabled_backends`","package":"thesaurus_query.vim-0.3.4.tar.gz","4":"thesaurus_query.vim-0.3.4.tar.gz","src_id":"24258","5":"24258","creation_date":"1463816137","6":"1463816137"},{"0":"5341","vim_version":"7.3","1":"7.3","script_version":"0.3.3","2":"0.3.3","version_comment":"Default keybinding to `cs`. Old keybinding `cs` still works, but the use is now depreciated.","3":"Default keybinding to `cs`. Old keybinding `cs` still works, but the use is now depreciated.","package":"thesaurus_query.vim-0.3.3.tar.gz","4":"thesaurus_query.vim-0.3.3.tar.gz","src_id":"24247","5":"24247","creation_date":"1463291204","6":"1463291204"},{"0":"5341","vim_version":"7.3","1":"7.3","script_version":"0.3.2","2":"0.3.2","version_comment":"Add German thesaurus query support, through woxikon.de.","3":"Add German thesaurus query support, through woxikon.de.","package":"thesaurus_query.vim-0.3.2.tar.gz","4":"thesaurus_query.vim-0.3.2.tar.gz","src_id":"24245","5":"24245","creation_date":"1463207331","6":"1463207331"},{"0":"5341","vim_version":"7.3","1":"7.3","script_version":"0.3.1","2":"0.3.1","version_comment":"Add Python3 support, and set as default.","3":"Add Python3 support, and set as default.","package":"thesaurus_query.vim-0.3.1.tar.gz","4":"thesaurus_query.vim-0.3.1.tar.gz","src_id":"24220","5":"24220","creation_date":"1462167157","6":"1462167157"},{"0":"5341","vim_version":"7.3","1":"7.3","script_version":"v0.3.0","2":"v0.3.0","version_comment":"## Added\r\n - multi-language thesaurus query support, currently English('en') and Russian('ru') are supported\r\n - `b:tq_language` and `g:tq_language` to setup which language source you prefer the plugin to query\r\n - use `completefunc` for insertmode autocomplete (Issue #7)\r\n - variable `let g:tq_use_vim_autocomplete = 1` to activate `completefunc`\r\n\r\n## Changed\r\n - (internal) words and query results in Python are now all utf-8 decoded\r\n - made plugin into autoload plugin to speed-up vim startup\r\n\r\n## Depreciated\r\n - all variables starting with `g:thesaurus_query#`, replacing the prefix of all of them by `g:tq_`\r\n\r\n## Removed\r\n - variable `g:thesaurus_query#map_keys`, use `g:tq_map_keys` instead.\r\n\r\n## Fixed\r\n - fix out-of-bound user input exception in candidate choosing.\r\n - add `KeyboardInterrupt` exception handler for candidate choosing.(closes Issue #8 )\r\n","3":"## Added\r\n - multi-language thesaurus query support, currently English('en') and Russian('ru') are supported\r\n - `b:tq_language` and `g:tq_language` to setup which language source you prefer the plugin to query\r\n - use `completefunc` for insertmode autocomplete (Issue #7)\r\n - variable `let g:tq_use_vim_autocomplete = 1` to activate `completefunc`\r\n\r\n## Changed\r\n - (internal) words and query results in Python are now all utf-8 decoded\r\n - made plugin into autoload plugin to speed-up vim startup\r\n\r\n## Depreciated\r\n - all variables starting with `g:thesaurus_query#`, replacing the prefix of all of them by `g:tq_`\r\n\r\n## Removed\r\n - variable `g:thesaurus_query#map_keys`, use `g:tq_map_keys` instead.\r\n\r\n## Fixed\r\n - fix out-of-bound user input exception in candidate choosing.\r\n - add `KeyboardInterrupt` exception handler for candidate choosing.(closes Issue #8 )\r\n","package":"thesaurus_query.vim-0.3.0.tar.gz","4":"thesaurus_query.vim-0.3.0.tar.gz","src_id":"24195","5":"24195","creation_date":"1461392821","6":"1461392821"},{"0":"5341","vim_version":"7.3","1":"7.3","script_version":"0.2.1","2":"0.2.1","version_comment":"plugin is now autoload plugin to speed-up vim startup","3":"plugin is now autoload plugin to speed-up vim startup","package":"thesaurus_query.0.2.1.tar.gz","4":"thesaurus_query.0.2.1.tar.gz","src_id":"24166","5":"24166","creation_date":"1460302435","6":"1460302435"},{"0":"5341","vim_version":"7.2","1":"7.2","script_version":"0.2.0","2":"0.2.0","version_comment":" V0.2 Changelog\r\n  * Added\r\n    - datamuse query routine\r\n    - implement backend enable\/disable by `g:thesaurus_query#enabled_backends`\r\n    - add query system reset function `:ThesaurusQueryReset`\r\n  * Depreciated\r\n    - use of variable `g:thesaurus_query#use_local_thesaurus_source_as_primary`\r\n  * Removed\r\n    - variable `g:thesaurus_query#use_alternative_backend`\r\n","3":" V0.2 Changelog\r\n  * Added\r\n    - datamuse query routine\r\n    - implement backend enable\/disable by `g:thesaurus_query#enabled_backends`\r\n    - add query system reset function `:ThesaurusQueryReset`\r\n  * Depreciated\r\n    - use of variable `g:thesaurus_query#use_local_thesaurus_source_as_primary`\r\n  * Removed\r\n    - variable `g:thesaurus_query#use_alternative_backend`\r\n","package":"thesaurus_query.vim-0.2.0.tar.gz","4":"thesaurus_query.vim-0.2.0.tar.gz","src_id":"24134","5":"24134","creation_date":"1458889888","6":"1458889888"},{"0":"5341","vim_version":"7.2","1":"7.2","script_version":"0.1.1","2":"0.1.1","version_comment":"* Same as 0.1.0d. Released as the first stable version. The plugin is verified to be working on vim 7.3 and 7.2 version. ","3":"* Same as 0.1.0d. Released as the first stable version. The plugin is verified to be working on vim 7.3 and 7.2 version. ","package":"thesaurus_query.vim-0.1.1.zip","4":"thesaurus_query.vim-0.1.1.zip","src_id":"24098","5":"24098","creation_date":"1457880496","6":"1457880496"},{"0":"5341","vim_version":"7.3","1":"7.3","script_version":"0.1.0-d","2":"0.1.0-d","version_comment":"fix :Thesaurus  functionality. ","3":"fix :Thesaurus  functionality. ","package":"thesaurus_query.vim-version0_1_0.zip","4":"thesaurus_query.vim-version0_1_0.zip","src_id":"24080","5":"24080","creation_date":"1457502769","6":"1457502769"},{"0":"5341","vim_version":"7.3","1":"7.3","script_version":"0.1.0-c","2":"0.1.0-c","version_comment":"fix a bug that the plugin replace a wrong word on vims with `w` `c` or `b` remapped to other functions.","3":"fix a bug that the plugin replace a wrong word on vims with `w` `c` or `b` remapped to other functions.","package":"thesaurus_query.vim-version0_1_0.zip","4":"thesaurus_query.vim-version0_1_0.zip","src_id":"24074","5":"24074","creation_date":"1457307381","6":"1457307381"},{"0":"5341","vim_version":"7.3","1":"7.3","script_version":"0.1.0-b","2":"0.1.0-b","version_comment":"Add backend priority swapping mechanism. Backend that return error when query will have its priority lowered.\r\n\r\nFurther improve synonym replacing interface. \r\n\r\nFix issue that might block plugin updating through plugin manager.","3":"Add backend priority swapping mechanism. Backend that return error when query will have its priority lowered.\r\n\r\nFurther improve synonym replacing interface. \r\n\r\nFix issue that might block plugin updating through plugin manager.","package":"thesaurus_query.vim-0.1.0-beta.zip","4":"thesaurus_query.vim-0.1.0-beta.zip","src_id":"24065","5":"24065","creation_date":"1457140708","6":"1457140708"},{"0":"5341","vim_version":"7.3","1":"7.3","script_version":"0.1.0-a","2":"0.1.0-a","version_comment":"Add local query backend based on parsing `mthesaur.txt`.\r\n\r\nRefined synonym replacing interface\r\n\r\nImproved synonym replacing algorithm","3":"Add local query backend based on parsing `mthesaur.txt`.\r\n\r\nRefined synonym replacing interface\r\n\r\nImproved synonym replacing algorithm","package":"thesaurus_query.vim-0.1.0-alpha.zip","4":"thesaurus_query.vim-0.1.0-alpha.zip","src_id":"24060","5":"24060","creation_date":"1457036169","6":"1457036169"},{"0":"5341","vim_version":"7.3","1":"7.3","script_version":"0.0.2","2":"0.0.2","version_comment":"User Interface improvement(mainly the replace candidate choosing interface). \r\nBug fix. \r\nAdd synonym output size control but currently inactive by default.","3":"User Interface improvement(mainly the replace candidate choosing interface). \r\nBug fix. \r\nAdd synonym output size control but currently inactive by default.","package":"thesaurus_query.vim-version0_0_2.zip","4":"thesaurus_query.vim-version0_0_2.zip","src_id":"24048","5":"24048","creation_date":"1456506957","6":"1456506957"},{"0":"5341","vim_version":"7.3","1":"7.3","script_version":"0.0.1","2":"0.0.1","version_comment":"Initial upload","3":"Initial upload","package":"thesaurus_query.vim.tar.gz","4":"thesaurus_query.vim.tar.gz","src_id":"24046","5":"24046","creation_date":"1456469679","6":"1456469679"}]},"5340":{"script_id":"5340","0":"5340","script_name":"password bunny","1":"password bunny","script_type":"utility","2":"utility","summary":"Manage passwords with Vim","3":"Manage passwords with Vim","description":"Homepage: http:\/\/code.arp242.net\/password-bunny\r\n\r\nManage passwords with Vim. See the homepage for the full documentation.","4":"Homepage: http:\/\/code.arp242.net\/password-bunny\r\n\r\nManage passwords with Vim. See the homepage for the full documentation.","install_details":"","5":"","first_name":"Martin","6":"Martin","last_name":"Tournoij","7":"Tournoij","releases":[{"0":"5340","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Download from homepage","3":"Download from homepage","package":"download-from-homepage.tar.gz","4":"download-from-homepage.tar.gz","src_id":"24686","5":"24686","creation_date":"1477882633","6":"1477882633"}]},"5339":{"script_id":"5339","0":"5339","script_name":"helplink.vim","1":"helplink.vim","script_type":"utility","2":"utility","summary":"Link to Vim help pages with ease.","3":"Link to Vim help pages with ease.","description":"Homepage: http:\/\/code.arp242.net\/helplink.vim\r\n\r\n-----------------------------------------\r\n\r\nIntroduction\r\n============\r\nLink to Vim help pages with ease.\r\n\r\nThere are several sites which host the Vim help pages in formatted HTML. It's\r\noften quite useful to link to this when explaining something.\r\n\r\nWith this plugin you can make a link to the help section you're viewing. Just\r\nuse `:Helplink`.\r\n\r\nI originally wrote this here:\r\nhttp:\/\/meta.vi.stackexchange.com\/a\/1250\/51\r\n\r\nCommands\r\n========\r\n:Helplink {format}                                                 `:Helplink`\r\n\r\nTry to find the tag closest to the cursor (backwards search only) and\r\nformat it. If multiple tags are found on the same line, it asks the\r\nuser which one to pick.\r\n\r\nThis will echo the formatted URL and copy them to the registers in\r\n`g:helplink_copy_to_registers`.\r\n\r\nYou can {format} parameter to get a different format; if not given the\r\nvalue of `g:helplink_default_format` is used.\r\n\r\nOptions\r\n=======\r\n`g:helplink_copy_to_registers`                      (List, default: ['+', '\\*'])\r\n\r\nAutomatically copy the link to these registers.\r\n\r\n`g:helplink_url`                                 (URL, default:\r\nhttp:\/\/vimhelp.appspot.com\/%%FILE%%.html#%%TAGNAME_QUOTED%%)\r\n\r\nAvailable placeholders:\r\n- `{%%FILE%%}`          File name (e.g. `options.txt`)\r\n- `%%TAGNAME%%`         Tag name (e.g. 'expandtab')\r\n- `%%TAGNAME_QUOTED%%`  The quoted tag name for use in URLS (e.g. %27expandtab%27)\r\n\r\n`g:helplink_formats`                                        (dict, default:\r\n\r\n    {\r\n    \\\t'markdown':  \"'[`:help ' . l:tagname . '`](' . l:url . ')'\",\r\n    \\\t'html': \"':help ' . l:tagname . '<\/a>'\",\r\n    \\\t'bbcode': \"'[url=' . l:url . '][code]:help ' . l:tagname . '[\/code][\/url]'\"\r\n    \\}\r\n\r\nThis string is `eval`-ed, variables you can use are {l:tagname} and\r\n{l:url}.\r\n\r\n`g:helplink_default_format`                         (String, default: markdown)\r\n\r\nAvailable formats:\r\n- markdown\r\n- html\r\n- bbcode\r\n\r\nYou can add your own in `g:helplink_formats`.\r\n\r\nFunctions\r\n=========\r\n`helplink#link([{format}])`                                    `helplink#link()`\r\n\r\nImplements the `:Helplink` command; the {format} is optional.\r\n","4":"Homepage: http:\/\/code.arp242.net\/helplink.vim\r\n\r\n-----------------------------------------\r\n\r\nIntroduction\r\n============\r\nLink to Vim help pages with ease.\r\n\r\nThere are several sites which host the Vim help pages in formatted HTML. It's\r\noften quite useful to link to this when explaining something.\r\n\r\nWith this plugin you can make a link to the help section you're viewing. Just\r\nuse `:Helplink`.\r\n\r\nI originally wrote this here:\r\nhttp:\/\/meta.vi.stackexchange.com\/a\/1250\/51\r\n\r\nCommands\r\n========\r\n:Helplink {format}                                                 `:Helplink`\r\n\r\nTry to find the tag closest to the cursor (backwards search only) and\r\nformat it. If multiple tags are found on the same line, it asks the\r\nuser which one to pick.\r\n\r\nThis will echo the formatted URL and copy them to the registers in\r\n`g:helplink_copy_to_registers`.\r\n\r\nYou can {format} parameter to get a different format; if not given the\r\nvalue of `g:helplink_default_format` is used.\r\n\r\nOptions\r\n=======\r\n`g:helplink_copy_to_registers`                      (List, default: ['+', '\\*'])\r\n\r\nAutomatically copy the link to these registers.\r\n\r\n`g:helplink_url`                                 (URL, default:\r\nhttp:\/\/vimhelp.appspot.com\/%%FILE%%.html#%%TAGNAME_QUOTED%%)\r\n\r\nAvailable placeholders:\r\n- `{%%FILE%%}`          File name (e.g. `options.txt`)\r\n- `%%TAGNAME%%`         Tag name (e.g. 'expandtab')\r\n- `%%TAGNAME_QUOTED%%`  The quoted tag name for use in URLS (e.g. %27expandtab%27)\r\n\r\n`g:helplink_formats`                                        (dict, default:\r\n\r\n    {\r\n    \\\t'markdown':  \"'[`:help ' . l:tagname . '`](' . l:url . ')'\",\r\n    \\\t'html': \"':help ' . l:tagname . '<\/a>'\",\r\n    \\\t'bbcode': \"'[url=' . l:url . '][code]:help ' . l:tagname . '[\/code][\/url]'\"\r\n    \\}\r\n\r\nThis string is `eval`-ed, variables you can use are {l:tagname} and\r\n{l:url}.\r\n\r\n`g:helplink_default_format`                         (String, default: markdown)\r\n\r\nAvailable formats:\r\n- markdown\r\n- html\r\n- bbcode\r\n\r\nYou can add your own in `g:helplink_formats`.\r\n\r\nFunctions\r\n=========\r\n`helplink#link([{format}])`                                    `helplink#link()`\r\n\r\nImplements the `:Helplink` command; the {format} is optional.\r\n","install_details":"","5":"","first_name":"Martin","6":"Martin","last_name":"Tournoij","7":"Tournoij","releases":[{"0":"5339","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Download from homepage","3":"Download from homepage","package":"download-from-homepage.tar.gz","4":"download-from-homepage.tar.gz","src_id":"24687","5":"24687","creation_date":"1477882668","6":"1477882668"}]},"5338":{"script_id":"5338","0":"5338","script_name":"startscreen.vim","1":"startscreen.vim","script_type":"utility","2":"utility","summary":"Customize Vim's start screen.","3":"Customize Vim's start screen.","description":"Homepage:  http:\/\/arp242.net\/code\/startscreen.vim\r\n----------------------------------------------------------------------------- \r\n\r\nIntroduction\r\n============\r\nCustomize Vim's start screen.\r\n\r\nThis is a much simpler version of vim-startify (which has a lot more\r\nfeatures): https:\/\/github.com\/mhinz\/vim-startify\r\n\r\nBy default it displays a random fortune(6), but this can be configured. Many\r\nLinux systems don't ship with fortune(6) by default any more (shame on them!)\r\nso you may get errors if you don't have it installed.\r\n\r\nOptions\r\n=======\r\n`g:Startscreen_function`                (Funcref, default: `startscreen#fortune`)\r\n\r\nThe function to run; this expects a `Funcref`. Note the capital S!\r\n\r\nExample:\r\n\r\n    function! T()\r\n    \" Read on our TODO file\r\n    read ~\/TODO\r\n\r\n    \" Some margin for readability\r\n    :silent %>>\r\n\r\n    \" Go to line 1\r\n    :1\r\n    endfun\r\n    let g:Startscreen_function = function('T')\r\n","4":"Homepage:  http:\/\/arp242.net\/code\/startscreen.vim\r\n----------------------------------------------------------------------------- \r\n\r\nIntroduction\r\n============\r\nCustomize Vim's start screen.\r\n\r\nThis is a much simpler version of vim-startify (which has a lot more\r\nfeatures): https:\/\/github.com\/mhinz\/vim-startify\r\n\r\nBy default it displays a random fortune(6), but this can be configured. Many\r\nLinux systems don't ship with fortune(6) by default any more (shame on them!)\r\nso you may get errors if you don't have it installed.\r\n\r\nOptions\r\n=======\r\n`g:Startscreen_function`                (Funcref, default: `startscreen#fortune`)\r\n\r\nThe function to run; this expects a `Funcref`. Note the capital S!\r\n\r\nExample:\r\n\r\n    function! T()\r\n    \" Read on our TODO file\r\n    read ~\/TODO\r\n\r\n    \" Some margin for readability\r\n    :silent %>>\r\n\r\n    \" Go to line 1\r\n    :1\r\n    endfun\r\n    let g:Startscreen_function = function('T')\r\n","install_details":"","5":"","first_name":"Martin","6":"Martin","last_name":"Tournoij","7":"Tournoij","releases":[{"0":"5338","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Download from homepage","3":"Download from homepage","package":"download-from-homepage.tar.gz","4":"download-from-homepage.tar.gz","src_id":"24683","5":"24683","creation_date":"1477798557","6":"1477798557"}]},"5337":{"script_id":"5337","0":"5337","script_name":"proto.vim","1":"proto.vim","script_type":"utility","2":"utility","summary":"https:\/\/github.com\/mateusz-pietruch\/proto.vim","3":"https:\/\/github.com\/mateusz-pietruch\/proto.vim","description":"Proto is a library for VimL introduces OOP mechanisms for the language.\r\n\r\nFeatures:\r\n\r\nprototype inheritance\r\naccess to interface of objects by dot notation\r\ndynamic composition of object in runtime\r\nallows creating constructors","4":"Proto is a library for VimL introduces OOP mechanisms for the language.\r\n\r\nFeatures:\r\n\r\nprototype inheritance\r\naccess to interface of objects by dot notation\r\ndynamic composition of object in runtime\r\nallows creating constructors","install_details":"https:\/\/github.com\/mateusz-pietruch\/proto.vim","5":"https:\/\/github.com\/mateusz-pietruch\/proto.vim","first_name":"","6":"","last_name":"","7":"","releases":[{"0":"5337","vim_version":"7.0","1":"7.0","script_version":"1.0.0","2":"1.0.0","version_comment":"Initial upload","3":"Initial upload","package":"proto.vim-master.zip","4":"proto.vim-master.zip","src_id":"24039","5":"24039","creation_date":"1456407638","6":"1456407638"}]},"5336":{"script_id":"5336","0":"5336","script_name":"vim-checksum","1":"vim-checksum","script_type":"utility","2":"utility","summary":"Plugin to cryptographically checksum files ","3":"Plugin to cryptographically checksum files ","description":"USAGE\r\n\r\n    :Checksum\r\n\r\nAfter pressing , a checksum (md5 by default) will be generated for the\r\ncurrent file. It can also be invoked in visual mode to checksum a selection.\r\n\r\nAlternatively the 'c' mapping can be used, which can be overrided by\r\nconfiguring the 'g:checksum_map' variable in the .vimrc file.\r\n\r\nhttps:\/\/github.com\/chilicuil\/vim-checksum","4":"USAGE\r\n\r\n    :Checksum\r\n\r\nAfter pressing , a checksum (md5 by default) will be generated for the\r\ncurrent file. It can also be invoked in visual mode to checksum a selection.\r\n\r\nAlternatively the 'c' mapping can be used, which can be overrided by\r\nconfiguring the 'g:checksum_map' variable in the .vimrc file.\r\n\r\nhttps:\/\/github.com\/chilicuil\/vim-checksum","install_details":"Vundle way (recommended), add the following to your $HOME\/.vimrc file:\r\n\r\n    Bundle 'chilicuil\/vim-checksum'\r\n\r\nAnd run inside of vim:\r\n\r\n    :BundleInstall\r\n\r\nNeoBundle way:\r\n\r\n    NeoBundle 'chilicuil\/vim-checksum'\r\n\r\nAnd run inside of vim:\r\n\r\n    :NeoBundleInstall\r\n\r\nPathogen way:\r\n\r\n    $ git clone https:\/\/github.com\/chilicuil\/vim-checksum.git ~\/.vim\/bundle\/vim-checksum\r\n\r\nManual (simplest if you've never heard of vim plugin managers)\r\n\r\nDownload the zip file and extract it to $HOME\/.vim\r\n\r\n    $ mv vim-checksum*.zip $HOME\/.vim\r\n    $ cd $HOME\/.vim && unzip vim-checksum*.zip\r\n\r\nUpdate the help tags from vim:\r\n\r\n    :helpt ~\/.vim\/doc\/","5":"Vundle way (recommended), add the following to your $HOME\/.vimrc file:\r\n\r\n    Bundle 'chilicuil\/vim-checksum'\r\n\r\nAnd run inside of vim:\r\n\r\n    :BundleInstall\r\n\r\nNeoBundle way:\r\n\r\n    NeoBundle 'chilicuil\/vim-checksum'\r\n\r\nAnd run inside of vim:\r\n\r\n    :NeoBundleInstall\r\n\r\nPathogen way:\r\n\r\n    $ git clone https:\/\/github.com\/chilicuil\/vim-checksum.git ~\/.vim\/bundle\/vim-checksum\r\n\r\nManual (simplest if you've never heard of vim plugin managers)\r\n\r\nDownload the zip file and extract it to $HOME\/.vim\r\n\r\n    $ mv vim-checksum*.zip $HOME\/.vim\r\n    $ cd $HOME\/.vim && unzip vim-checksum*.zip\r\n\r\nUpdate the help tags from vim:\r\n\r\n    :helpt ~\/.vim\/doc\/","first_name":"chili","6":"chili","last_name":"cuil","7":"cuil","releases":[{"0":"5336","vim_version":"7.0","1":"7.0","script_version":"0.0.1","2":"0.0.1","version_comment":"Initial upload","3":"Initial upload","package":"vim-checksum.zip","4":"vim-checksum.zip","src_id":"24028","5":"24028","creation_date":"1456032647","6":"1456032647"}]},"5335":{"script_id":"5335","0":"5335","script_name":"vulkan1.0.vim","1":"vulkan1.0.vim","script_type":"syntax","2":"syntax","summary":"Syntax file for the Vulkan","3":"Syntax file for the Vulkan","description":"Syntax file for the Vulkan in C\/C++. \r\nThe following is highlighted:\r\nTypes\r\nFunctions\r\nConstants\r\n\r\nThe syntax file is modified version of opengl.vim by  Marc Costa ","4":"Syntax file for the Vulkan in C\/C++. \r\nThe following is highlighted:\r\nTypes\r\nFunctions\r\nConstants\r\n\r\nThe syntax file is modified version of opengl.vim by  Marc Costa ","install_details":"Place vulkan1.0.vim in your syntax directory: \r\ncp vulkan1.0.vim $HOME\/.vim\/syntax\/. \r\n\r\nEnable highlighting with vulkan1.0.vim in your .vimrc with: \r\nautocmd FileType cpp,c source ~\/.vim\/syntax\/vulkan1.0.vim","5":"Place vulkan1.0.vim in your syntax directory: \r\ncp vulkan1.0.vim $HOME\/.vim\/syntax\/. \r\n\r\nEnable highlighting with vulkan1.0.vim in your .vimrc with: \r\nautocmd FileType cpp,c source ~\/.vim\/syntax\/vulkan1.0.vim","first_name":"Tom\u00c3\u00a1\u00c5\u00a1","6":"Tom\u00c3\u00a1\u00c5\u00a1","last_name":"Milet","7":"Milet","releases":[{"0":"5335","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"vulkan1.0.vim","4":"vulkan1.0.vim","src_id":"24017","5":"24017","creation_date":"1455718070","6":"1455718070"}]},"5334":{"script_id":"5334","0":"5334","script_name":"wordmotion.vim","1":"wordmotion.vim","script_type":"utility","2":"utility","summary":"More useful word motions for Vim","3":"More useful word motions for Vim","description":"https:\/\/github.com\/chaoren\/vim-wordmotion\r\n\r\nThis is one word under Vim's definition: [CamelCaseACRONYMWords_underscore1234],\r\nwith this plugin, this becomes six words: [Camel][Case][ACRONYM][Words]_[underscore][1234]","4":"https:\/\/github.com\/chaoren\/vim-wordmotion\r\n\r\nThis is one word under Vim's definition: [CamelCaseACRONYMWords_underscore1234],\r\nwith this plugin, this becomes six words: [Camel][Case][ACRONYM][Words]_[underscore][1234]","install_details":"","5":"","first_name":"Chaoren","6":"Chaoren","last_name":"Lin","7":"Lin","releases":[{"0":"5334","vim_version":"7.4","1":"7.4","script_version":"37ab3e6","2":"37ab3e6","version_comment":"https:\/\/github.com\/chaoren\/vim-wordmotion\/commit\/37ab3e6775070215f6fcd6db3bf9b66e5da76b05","3":"https:\/\/github.com\/chaoren\/vim-wordmotion\/commit\/37ab3e6775070215f6fcd6db3bf9b66e5da76b05","package":"wordmotion.zip","4":"wordmotion.zip","src_id":"27474","5":"27474","creation_date":"1612676344","6":"1612676344"},{"0":"5334","vim_version":"7.4","1":"7.4","script_version":"9ea91b6","2":"9ea91b6","version_comment":"https:\/\/github.com\/chaoren\/vim-wordmotion\/commit\/9ea91b6da6c11ab103129757061aa7afbe1e102d","3":"https:\/\/github.com\/chaoren\/vim-wordmotion\/commit\/9ea91b6da6c11ab103129757061aa7afbe1e102d","package":"wordmotion.zip","4":"wordmotion.zip","src_id":"27414","5":"27414","creation_date":"1608696996","6":"1608696996"}]},"5333":{"script_id":"5333","0":"5333","script_name":"vimhelplint","1":"vimhelplint","script_type":"ftplugin","2":"ftplugin","summary":"A lint tool for vim help files.","3":"A lint tool for vim help files.","description":"A filetype plugin to run syntax check of vim help files. It would be helpful for plugin authors.\r\n\r\nUsage\r\nExecute an ex command :VimhelpLint, then it adds errors to quickfix list. Then, for example, use :copen to check quickfix window. If you use :VimhelpLint!, it opens quickfix window automatically.\r\n\r\nLatest version: https:\/\/github.com\/machakann\/vim-vimhelplint","4":"A filetype plugin to run syntax check of vim help files. It would be helpful for plugin authors.\r\n\r\nUsage\r\nExecute an ex command :VimhelpLint, then it adds errors to quickfix list. Then, for example, use :copen to check quickfix window. If you use :VimhelpLint!, it opens quickfix window automatically.\r\n\r\nLatest version: https:\/\/github.com\/machakann\/vim-vimhelplint","install_details":"See the description in  https:\/\/github.com\/machakann\/vim-vimhelplint","5":"See the description in  https:\/\/github.com\/machakann\/vim-vimhelplint","first_name":"Masaaki","6":"Masaaki","last_name":"Nakamura","7":"Nakamura","releases":[{"0":"5333","vim_version":"7.4","1":"7.4","script_version":"1.0.0","2":"1.0.0","version_comment":"Initial upload","3":"Initial upload","package":"vim-vimhelplint-1.0.0.zip","4":"vim-vimhelplint-1.0.0.zip","src_id":"24014","5":"24014","creation_date":"1455628973","6":"1455628973"}]},"5332":{"script_id":"5332","0":"5332","script_name":"braceless.vim","1":"braceless.vim","script_type":"ftplugin","2":"ftplugin","summary":"Text objects, folding, and more for Python and other indented languages","3":"Text objects, folding, and more for Python and other indented languages","description":"Braceless adds text objects, folding, and more for Python and other indented languages.\r\n\r\nEnable with the command: BracelessEnable\r\n\r\nCommand arguments:\r\n\r\n+indent        | Enable indent handling\r\n+fold          | Enable folding\r\n+fold-inner    | Enable folding, but fold on the inner block\r\n+highlight     | Enable indent guide\r\n+highlight-cc  | Enable indent guide, but use colorcolumn\r\n+highlight-cc2 | Enable indent guide and use colorcolumn\r\n\r\n\r\nSee the GitHub page for full details: https:\/\/github.com\/tweekmonster\/braceless.vim","4":"Braceless adds text objects, folding, and more for Python and other indented languages.\r\n\r\nEnable with the command: BracelessEnable\r\n\r\nCommand arguments:\r\n\r\n+indent        | Enable indent handling\r\n+fold          | Enable folding\r\n+fold-inner    | Enable folding, but fold on the inner block\r\n+highlight     | Enable indent guide\r\n+highlight-cc  | Enable indent guide, but use colorcolumn\r\n+highlight-cc2 | Enable indent guide and use colorcolumn\r\n\r\n\r\nSee the GitHub page for full details: https:\/\/github.com\/tweekmonster\/braceless.vim","install_details":"Extract into your configured plugin directory","5":"Extract into your configured plugin directory","first_name":"Tommy","6":"Tommy","last_name":"Allen","7":"Allen","releases":[{"0":"5332","vim_version":"7.3","1":"7.3","script_version":"v0.4.1","2":"v0.4.1","version_comment":"- Faster folding\r\n- Improved block indent\r\n- Customizable indent options\r\n- Automatic line continuations on ","3":"- Faster folding\r\n- Improved block indent\r\n- Customizable indent options\r\n- Automatic line continuations on ","package":"braceless.vim.zip","4":"braceless.vim.zip","src_id":"24119","5":"24119","creation_date":"1458273248","6":"1458273248"},{"0":"5332","vim_version":"7.3","1":"7.3","script_version":"v0.4","2":"v0.4","version_comment":"- Using cache for folds\r\n- Fold pattern is user configurable\r\n- Fixed autoindent on decorated functions\r\n- Added block segment motions","3":"- Using cache for folds\r\n- Fold pattern is user configurable\r\n- Fixed autoindent on decorated functions\r\n- Added block segment motions","package":"braceless.vim.zip","4":"braceless.vim.zip","src_id":"24066","5":"24066","creation_date":"1457152363","6":"1457152363"},{"0":"5332","vim_version":"7.3","1":"7.3","script_version":"v0.3","2":"v0.3","version_comment":"Refactored block selection\r\n\r\n- Block selections now include decorators\r\n- Improved indent operation","3":"Refactored block selection\r\n\r\n- Block selections now include decorators\r\n- Improved indent operation","package":"braceless.vim.zip","4":"braceless.vim.zip","src_id":"24054","5":"24054","creation_date":"1456639971","6":"1456639971"},{"0":"5332","vim_version":"7.3","1":"7.3","script_version":"v0.2","2":"v0.2","version_comment":"- Improved autoindent\r\n- Improved block recognition","3":"- Improved autoindent\r\n- Improved block recognition","package":"braceless.vim.zip","4":"braceless.vim.zip","src_id":"24037","5":"24037","creation_date":"1456295859","6":"1456295859"},{"0":"5332","vim_version":"7.3","1":"7.3","script_version":"v0.1","2":"v0.1","version_comment":"Initial upload","3":"Initial upload","package":"braceless.vim.zip","4":"braceless.vim.zip","src_id":"24012","5":"24012","creation_date":"1455554213","6":"1455554213"}]},"5331":{"script_id":"5331","0":"5331","script_name":"Sierra","1":"Sierra","script_type":"color scheme","2":"color scheme","summary":"A colorscheme for Terminal Vim and GUI Vim. ","3":"A colorscheme for Terminal Vim and GUI Vim. ","description":"A low-contrast colorscheme for Terminal Vim and GUI Vim. \r\n\r\nFor Screenshots, color options, and future downloads check out the GitHub repo here:\r\nhttps:\/\/github.com\/AlessandroYorba\/Sierra","4":"A low-contrast colorscheme for Terminal Vim and GUI Vim. \r\n\r\nFor Screenshots, color options, and future downloads check out the GitHub repo here:\r\nhttps:\/\/github.com\/AlessandroYorba\/Sierra","install_details":"For Unix users, place sierra.vim in ~\/.vim\/colors \r\nWindows users, place sierra.vim in ~\\vimfiles\\colors \r\n\r\nor use your favorite package manager","5":"For Unix users, place sierra.vim in ~\/.vim\/colors \r\nWindows users, place sierra.vim in ~\\vimfiles\\colors \r\n\r\nor use your favorite package manager","first_name":"Alessandro","6":"Alessandro","last_name":"Yorba","7":"Yorba","releases":[{"0":"5331","vim_version":"7.0","1":"7.0","script_version":"be0983a","2":"be0983a","version_comment":"Enjoy!","3":"Enjoy!","package":"sierra.vim","4":"sierra.vim","src_id":"26945","5":"26945","creation_date":"1580309261","6":"1580309261"},{"0":"5331","vim_version":"7.0","1":"7.0","script_version":"4.0","2":"4.0","version_comment":"Major\r\n* Added Sunset Mode\r\n* Refactored all of sierra\r\n* Added ColorHexa references to Palette ### Minor ###\r\n* Unified Pmenu for all modes\r\n* New Comment Colors for all modes\r\n* Added sunset to Campfire mode","3":"Major\r\n* Added Sunset Mode\r\n* Refactored all of sierra\r\n* Added ColorHexa references to Palette ### Minor ###\r\n* Unified Pmenu for all modes\r\n* New Comment Colors for all modes\r\n* Added sunset to Campfire mode","package":"sierra.vim","4":"sierra.vim","src_id":"24619","5":"24619","creation_date":"1476202305","6":"1476202305"},{"0":"5331","vim_version":"7.0","1":"7.0","script_version":"2.3.6","2":"2.3.6","version_comment":"All script notes and revisions can be found @ https:\/\/github.com\/AlessandroYorba\/Sierra\/releases","3":"All script notes and revisions can be found @ https:\/\/github.com\/AlessandroYorba\/Sierra\/releases","package":"sierra.vim","4":"sierra.vim","src_id":"24237","5":"24237","creation_date":"1462659401","6":"1462659401"},{"0":"5331","vim_version":"7.3","1":"7.3","script_version":"1.10.15","2":"1.10.15","version_comment":"Current 1.10.15\r\nUpdated from 1.4.12\r\nNotes on new changes can be found https:\/\/github.com\/AlessandroYorba\/Sierra\/releases","3":"Current 1.10.15\r\nUpdated from 1.4.12\r\nNotes on new changes can be found https:\/\/github.com\/AlessandroYorba\/Sierra\/releases","package":"sierra.vim","4":"sierra.vim","src_id":"24010","5":"24010","creation_date":"1455509172","6":"1455509172"},{"0":"5331","vim_version":"7.3","1":"7.3","script_version":"1.4.12","2":"1.4.12","version_comment":"Initial upload","3":"Initial upload","package":"sierra.vim","4":"sierra.vim","src_id":"24006","5":"24006","creation_date":"1455348630","6":"1455348630"}]},"5330":{"script_id":"5330","0":"5330","script_name":"Hunter","1":"Hunter","script_type":"utility","2":"utility","summary":"Package fiinder for vim","3":"Package fiinder for vim","description":"Vim package finder based on Vundle. inspired by Sublime Text Package Control.","4":"Vim package finder based on Vundle. inspired by Sublime Text Package Control.","install_details":"Put in .vimrc:\r\n\r\n* Bundle 'mattn\/webapi-vim'\r\n* Bundle 'ogranada\/hunter'\r\n\r\nexecute\r\n:PluginInstall\r\n\r\n","5":"Put in .vimrc:\r\n\r\n* Bundle 'mattn\/webapi-vim'\r\n* Bundle 'ogranada\/hunter'\r\n\r\nexecute\r\n:PluginInstall\r\n\r\n","first_name":"OSCAR A","6":"OSCAR A","last_name":"Granada","7":"Granada","releases":[{"0":"5330","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"hunter.tar.gz","4":"hunter.tar.gz","src_id":"24005","5":"24005","creation_date":"1455315304","6":"1455315304"}]},"5329":{"script_id":"5329","0":"5329","script_name":"vim-latex-light","1":"vim-latex-light","script_type":"ftplugin","2":"ftplugin","summary":"LaTeX Light compiles LaTeX and shows errors and warnings in Vim","3":"LaTeX Light compiles LaTeX and shows errors and warnings in Vim","description":"LaTeX Light is a lightweight LaTeX companion for Vim that compiles your document and shows you LaTeX warnings and errors. Open up a LaTeX file and use p to issue the build command ('p' for 'PDF').\r\n\r\nThe warnings and errors are read from the logfile generated by the compiler, LaTeX Light looks for .log in the same directory.\r\n\r\nFor more info, see the GitHub page: http:\/\/rbnvrw.github.io\/vim-latex-light or the repository: https:\/\/github.com\/rbnvrw\/vim-latex-light","4":"LaTeX Light is a lightweight LaTeX companion for Vim that compiles your document and shows you LaTeX warnings and errors. Open up a LaTeX file and use p to issue the build command ('p' for 'PDF').\r\n\r\nThe warnings and errors are read from the logfile generated by the compiler, LaTeX Light looks for .log in the same directory.\r\n\r\nFor more info, see the GitHub page: http:\/\/rbnvrw.github.io\/vim-latex-light or the repository: https:\/\/github.com\/rbnvrw\/vim-latex-light","install_details":"Install using your favorite plugin manager.","5":"Install using your favorite plugin manager.","first_name":"Ruben","6":"Ruben","last_name":"Verweij","7":"Verweij","releases":[{"0":"5329","vim_version":"7.0","1":"7.0","script_version":"0.3","2":"0.3","version_comment":"Initial upload","3":"Initial upload","package":"vim-latex-light-0.3.zip","4":"vim-latex-light-0.3.zip","src_id":"24004","5":"24004","creation_date":"1455293479","6":"1455293479"}]},"5328":{"script_id":"5328","0":"5328","script_name":"lib.kom","1":"lib.kom","script_type":"utility","2":"utility","summary":"Scripting highly advanced-functions","3":"Scripting highly advanced-functions","description":"Much better display on the hub: https:\/\/github.com\/romgrk\/lib.kom\r\n\r\nScripting autoload functions for syntax highlighting and buffer\/window management. Also comes with _.vim, which is the start of a kind-of adaptation of lodash\/underscore to vimL, that I will hopefully never have to complete.\r\n\r\nExample: get objects & use them\r\nlet cur_win = win#() \" => a Window object (the current by default) (such a loss of time in this nonsense)\r\nlet alt_win = win#(\"#\") \" => the window where is displayed the alternate buffer\r\ncall alt_win.cmd('bnext')       \" safely executes \u00e2\u0080\u009cbnext\u00e2\u0080\u009d in alt_win context \r\ncall cur_win.open( buf#(9) ) \" opens buffer 9 in current window\r\n\r\nExample: exchange buffers between current window and second window\r\n let other = win#(2).buf()\r\n call win#(2).open(buf#())\r\n call win#().open(other)\r\n\r\n \" Print all &buflisted buffers, where filetype is \"vim\" and\r\n \" that have a bufnr higher than 10.\r\n echo buf#filter('&buflisted', '&ft==\"vim\"', 'v:val > 10')\r\n\r\n echo win#filter('&buflisted') \" => List of windows containing listed buffers\r\n\r\n\r\ncall win#(2).open(4)\r\n\" buffer #4 is opened in window #2\r\n\r\necho color#darken('#599eff', '0.2')\r\n\" => #477ecc\r\necho color#HexToRGB('#599eff')\r\n\" => [89, 158, 255]\r\n(if you find this useful, let me know, I might write more documentation)\r\n\r\nhi.vim - highlighting\r\n\r\nhi#fg and hi#bg ('GoupName' [, color:String]) are both getter and setters hi#( name [, group:[] | fg [,bg [,attr ] ] ] ) can get\/set or define your group without error\r\n\r\na group-hl definition may be: (name && ( 1, 2 or 4 arguments)) || (Array of (2, 3 or 4 arguments))\r\n\r\nwhere arguments are assumed to be (in order): gui-foreground-color, gui-background-color, attributes (no cterm handling)\r\n\r\nUseful trick example:\r\n\r\n=hi#fg('Function')\r\ngives you the foreground color for group Function\r\n\r\nfu! hi# (...)\r\nfu! hi#fg (name, ...)\r\nfu! hi#bg (name, ...)\r\n\" the rest:  check the source for more details\r\nfu! hi#id (name)\r\nfu! hi#attr (name, ...)\r\nfu! hi#name (id)\r\nfu! hi#create (name, ...)\r\nfu! hi#set (name, ...)\r\nfu! hi#exists (r)\r\nfu! hi#islink (name)\r\nfu! hi#isdefined (name)\r\nfu! hi#get (ref)\r\nfu! hi#group (...)\r\nfu! hi#clear (name)\r\nfu! hi#fill (group, ...)\r\nfu! hi#compose (rule, ...)\r\n\r\n\r\nundocumented:\r\n\r\n_.vim\r\ncolor.vim\r\nbuf.vim\r\nwin.vim\r\n","4":"Much better display on the hub: https:\/\/github.com\/romgrk\/lib.kom\r\n\r\nScripting autoload functions for syntax highlighting and buffer\/window management. Also comes with _.vim, which is the start of a kind-of adaptation of lodash\/underscore to vimL, that I will hopefully never have to complete.\r\n\r\nExample: get objects & use them\r\nlet cur_win = win#() \" => a Window object (the current by default) (such a loss of time in this nonsense)\r\nlet alt_win = win#(\"#\") \" => the window where is displayed the alternate buffer\r\ncall alt_win.cmd('bnext')       \" safely executes \u00e2\u0080\u009cbnext\u00e2\u0080\u009d in alt_win context \r\ncall cur_win.open( buf#(9) ) \" opens buffer 9 in current window\r\n\r\nExample: exchange buffers between current window and second window\r\n let other = win#(2).buf()\r\n call win#(2).open(buf#())\r\n call win#().open(other)\r\n\r\n \" Print all &buflisted buffers, where filetype is \"vim\" and\r\n \" that have a bufnr higher than 10.\r\n echo buf#filter('&buflisted', '&ft==\"vim\"', 'v:val > 10')\r\n\r\n echo win#filter('&buflisted') \" => List of windows containing listed buffers\r\n\r\n\r\ncall win#(2).open(4)\r\n\" buffer #4 is opened in window #2\r\n\r\necho color#darken('#599eff', '0.2')\r\n\" => #477ecc\r\necho color#HexToRGB('#599eff')\r\n\" => [89, 158, 255]\r\n(if you find this useful, let me know, I might write more documentation)\r\n\r\nhi.vim - highlighting\r\n\r\nhi#fg and hi#bg ('GoupName' [, color:String]) are both getter and setters hi#( name [, group:[] | fg [,bg [,attr ] ] ] ) can get\/set or define your group without error\r\n\r\na group-hl definition may be: (name && ( 1, 2 or 4 arguments)) || (Array of (2, 3 or 4 arguments))\r\n\r\nwhere arguments are assumed to be (in order): gui-foreground-color, gui-background-color, attributes (no cterm handling)\r\n\r\nUseful trick example:\r\n\r\n=hi#fg('Function')\r\ngives you the foreground color for group Function\r\n\r\nfu! hi# (...)\r\nfu! hi#fg (name, ...)\r\nfu! hi#bg (name, ...)\r\n\" the rest:  check the source for more details\r\nfu! hi#id (name)\r\nfu! hi#attr (name, ...)\r\nfu! hi#name (id)\r\nfu! hi#create (name, ...)\r\nfu! hi#set (name, ...)\r\nfu! hi#exists (r)\r\nfu! hi#islink (name)\r\nfu! hi#isdefined (name)\r\nfu! hi#get (ref)\r\nfu! hi#group (...)\r\nfu! hi#clear (name)\r\nfu! hi#fill (group, ...)\r\nfu! hi#compose (rule, ...)\r\n\r\n\r\nundocumented:\r\n\r\n_.vim\r\ncolor.vim\r\nbuf.vim\r\nwin.vim\r\n","install_details":"As usual (and I'm not talking about download: install from the repo with some manager: https:\/\/github.com\/romgrk\/lib.kom)\r\n(I always wonder why we still use this atrocity called vim.org)\r\n","5":"As usual (and I'm not talking about download: install from the repo with some manager: https:\/\/github.com\/romgrk\/lib.kom)\r\n(I always wonder why we still use this atrocity called vim.org)\r\n","first_name":"Rom","6":"Rom","last_name":"Grk","7":"Grk","releases":[{"0":"5328","vim_version":"7.0","1":"7.0","script_version":"1.1","2":"1.1","version_comment":"Patches, doc, examples","3":"Patches, doc, examples","package":"lib_kom.zip","4":"lib_kom.zip","src_id":"24106","5":"24106","creation_date":"1458107383","6":"1458107383"},{"0":"5328","vim_version":"7.3","1":"7.3","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"lib_kom.zip","4":"lib_kom.zip","src_id":"24003","5":"24003","creation_date":"1455278661","6":"1455278661"}]},"5327":{"script_id":"5327","0":"5327","script_name":"sky","1":"sky","script_type":"color scheme","2":"color scheme","summary":"Color scheme.","3":"Color scheme.","description":"https:\/\/github.com\/ninja\/sky","4":"https:\/\/github.com\/ninja\/sky","install_details":"https:\/\/github.com\/ninja\/sky","5":"https:\/\/github.com\/ninja\/sky","first_name":"Jamie","6":"Jamie","last_name":"Hoover","7":"Hoover","releases":[{"0":"5327","vim_version":"7.4","1":"7.4","script_version":"1.1","2":"1.1","version_comment":"Adds support for terminal colors.","3":"Adds support for terminal colors.","package":"sky-1.1.tar.gz","4":"sky-1.1.tar.gz","src_id":"24000","5":"24000","creation_date":"1455061182","6":"1455061182"},{"0":"5327","vim_version":"7.4","1":"7.4","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"sky-1.0.tar.gz","4":"sky-1.0.tar.gz","src_id":"23995","5":"23995","creation_date":"1454966761","6":"1454966761"}]},"5326":{"script_id":"5326","0":"5326","script_name":"Quickalign","1":"Quickalign","script_type":"utility","2":"utility","summary":"Marker-based alginment of small chunks of text.","3":"Marker-based alginment of small chunks of text.","description":"This vim plugin is useful for aligning small chunks of text by setting markers.\r\nThe plugin defines the following key bindings:\r\n- Set alignment marker\r\n-e     Execute alignment\r\n-c     Clean alignment buffer\r\nMultiple column alignments are supported.\r\n","4":"This vim plugin is useful for aligning small chunks of text by setting markers.\r\nThe plugin defines the following key bindings:\r\n- Set alignment marker\r\n-e     Execute alignment\r\n-c     Clean alignment buffer\r\nMultiple column alignments are supported.\r\n","install_details":"Unpack into script search path.","5":"Unpack into script search path.","first_name":"Franz","6":"Franz","last_name":"Schanovsky","7":"Schanovsky","releases":[{"0":"5326","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"vim-quick-align-V0.1.tgz","4":"vim-quick-align-V0.1.tgz","src_id":"23987","5":"23987","creation_date":"1454626591","6":"1454626591"}]},"5325":{"script_id":"5325","0":"5325","script_name":"vim-maven-syntax","1":"vim-maven-syntax","script_type":"syntax","2":"syntax","summary":"Apache Maven syntax highlighting plugin for Vim","3":"Apache Maven syntax highlighting plugin for Vim","description":"This plugin provides Apache Maven syntax highlighting on top of XML.\r\n\r\nScreenshot is available in the main repository: https:\/\/github.com\/NLKNguyen\/vim-maven-syntax\r\n\r\n\r\n# Usage\r\n\r\nManually: `:set filetype=xml.maven`\r\n\r\nAutomatically: `pom.xml` file is detected to automatically set the filetype as above.","4":"This plugin provides Apache Maven syntax highlighting on top of XML.\r\n\r\nScreenshot is available in the main repository: https:\/\/github.com\/NLKNguyen\/vim-maven-syntax\r\n\r\n\r\n# Usage\r\n\r\nManually: `:set filetype=xml.maven`\r\n\r\nAutomatically: `pom.xml` file is detected to automatically set the filetype as above.","install_details":"Copy `syntax` and `ftdetect` folders into your `~\/.vim\/` (or `vimfiles\/` on Windows)\r\n\r\nOr simply use a plugin manager like Vundle (https:\/\/github.com\/VundleVim\/Vundle.vim) (recommended for easy `:PluginUpdate`):\r\n\r\n    Plugin 'NLKNguyen\/vim-maven-syntax'\r\n","5":"Copy `syntax` and `ftdetect` folders into your `~\/.vim\/` (or `vimfiles\/` on Windows)\r\n\r\nOr simply use a plugin manager like Vundle (https:\/\/github.com\/VundleVim\/Vundle.vim) (recommended for easy `:PluginUpdate`):\r\n\r\n    Plugin 'NLKNguyen\/vim-maven-syntax'\r\n","first_name":"Nikyle","6":"Nikyle","last_name":"Nguyen","7":"Nguyen","releases":[{"0":"5325","vim_version":"7.0","1":"7.0","script_version":"0.1.0","2":"0.1.0","version_comment":"Initial upload","3":"Initial upload","package":"vim-maven-syntax.zip","4":"vim-maven-syntax.zip","src_id":"23985","5":"23985","creation_date":"1454566076","6":"1454566076"}]},"5324":{"script_id":"5324","0":"5324","script_name":"markdown-preview.vim","1":"markdown-preview.vim","script_type":"utility","2":"utility","summary":"preview markdown through browser with no external dependencies","3":"preview markdown through browser with no external dependencies","description":"Use the markdown-preview.vim plugin you can preview markdown on real-time through a browser\r\n\r\n> this plugin need your vim support py2\/py3 features\r\n> test on windows\/ubuntu14\r\n\r\nscreenshot\r\nhttps:\/\/raw.githubusercontent.com\/iamcco\/markdown-preview.vim\/master\/screenshot.gif\r\n\r\nsources \r\nhttps:\/\/github.com\/iamcco\/markdown-preview.vim\r\n\r\nUsage\r\n\r\nCommand:\r\n\r\n    MarkdownPreview\r\n    \\\" open preview window in markdown buffer\r\n\r\n    MarkdownPreviewStop\r\n    \\\" close the preview window and server\r\n\r\nwhen MarkdownPreview command can\\'t open preview window, you can use the MarkdownPreviewStop command before using MarkdownPreview command\r\nDefaul Setting:\r\n\r\n    let g:mkdp_path_to_chrome = \\\"google-chrome\\\"\r\n    \\\" path to the chrome or the command to open chrome(or other modern browsers)\r\n\r\n    let g:mkdp_auto_start = 0\r\n    \\\" set to 1, the vim will open the preview window once enter the markdown\r\n    \\\" buffer\r\n\r\n    let g:mkdp_auto_open = 0\r\n    \\\" set to 1, the vim will auto open preview window when you edit the\r\n    \\\" markdown file\r\n\r\n    let g:mkdp_auto_close = 1\r\n    \\\" set to 1, the vim will auto close current preview window when change\r\n    \\\" from markdown buffer to another buffer\r\n\r\n    let g:mkdp_refresh_slow = 0\r\n    \\\" set to 1, the vim will just refresh markdown when save the buffer or\r\n    \\\" leave from insert mode, default 0 is auto refresh markdown as you edit or\r\n    \\\" move the cursor\r\n ","4":"Use the markdown-preview.vim plugin you can preview markdown on real-time through a browser\r\n\r\n> this plugin need your vim support py2\/py3 features\r\n> test on windows\/ubuntu14\r\n\r\nscreenshot\r\nhttps:\/\/raw.githubusercontent.com\/iamcco\/markdown-preview.vim\/master\/screenshot.gif\r\n\r\nsources \r\nhttps:\/\/github.com\/iamcco\/markdown-preview.vim\r\n\r\nUsage\r\n\r\nCommand:\r\n\r\n    MarkdownPreview\r\n    \\\" open preview window in markdown buffer\r\n\r\n    MarkdownPreviewStop\r\n    \\\" close the preview window and server\r\n\r\nwhen MarkdownPreview command can\\'t open preview window, you can use the MarkdownPreviewStop command before using MarkdownPreview command\r\nDefaul Setting:\r\n\r\n    let g:mkdp_path_to_chrome = \\\"google-chrome\\\"\r\n    \\\" path to the chrome or the command to open chrome(or other modern browsers)\r\n\r\n    let g:mkdp_auto_start = 0\r\n    \\\" set to 1, the vim will open the preview window once enter the markdown\r\n    \\\" buffer\r\n\r\n    let g:mkdp_auto_open = 0\r\n    \\\" set to 1, the vim will auto open preview window when you edit the\r\n    \\\" markdown file\r\n\r\n    let g:mkdp_auto_close = 1\r\n    \\\" set to 1, the vim will auto close current preview window when change\r\n    \\\" from markdown buffer to another buffer\r\n\r\n    let g:mkdp_refresh_slow = 0\r\n    \\\" set to 1, the vim will just refresh markdown when save the buffer or\r\n    \\\" leave from insert mode, default 0 is auto refresh markdown as you edit or\r\n    \\\" move the cursor\r\n ","install_details":"1. normal install\r\n\r\nPut the plugin\/mkdp.vim file into your ~\/.vim\/plugin (or $HOME\\\\\\\\vimfiles\\\\\\\\plugin) directory. \r\nPut the doc\/mkdp.txt into your ~\/.vim\/doc (or $HOME\\\\\\\\vimfiles\\\\\\\\doc) directory. \r\nPut all the files in the autoload\/ directory into your ~\/.vim\/autoload (or $HOME\\\\\\\\vimfiles\\\\\\\\autoload) directory. \r\n\r\nRun \\\":helptags ~\/.vim\/doc\\\" (\\\":helptags $HOME\/vimfiles\/doc\\\") \r\n\r\n\r\n2. install with Vundle (recommended)\r\n\r\nput Plugin \\'iamcco\/markdown-preview.vim\\' to the .vimrc\/_vimrc file and run:PluginInstall","5":"1. normal install\r\n\r\nPut the plugin\/mkdp.vim file into your ~\/.vim\/plugin (or $HOME\\\\\\\\vimfiles\\\\\\\\plugin) directory. \r\nPut the doc\/mkdp.txt into your ~\/.vim\/doc (or $HOME\\\\\\\\vimfiles\\\\\\\\doc) directory. \r\nPut all the files in the autoload\/ directory into your ~\/.vim\/autoload (or $HOME\\\\\\\\vimfiles\\\\\\\\autoload) directory. \r\n\r\nRun \\\":helptags ~\/.vim\/doc\\\" (\\\":helptags $HOME\/vimfiles\/doc\\\") \r\n\r\n\r\n2. install with Vundle (recommended)\r\n\r\nput Plugin \\'iamcco\/markdown-preview.vim\\' to the .vimrc\/_vimrc file and run:PluginInstall","first_name":"yuuko","6":"yuuko","last_name":"aioi","7":"aioi","releases":[{"0":"5324","vim_version":"7.4","1":"7.4","script_version":"0.2.2","2":"0.2.2","version_comment":"fix bug on neovim for opening browser","3":"fix bug on neovim for opening browser","package":"markdown-preview.vim-0.2.2.zip","4":"markdown-preview.vim-0.2.2.zip","src_id":"24033","5":"24033","creation_date":"1456157371","6":"1456157371"},{"0":"5324","vim_version":"7.4","1":"7.4","script_version":"0.2.1","2":"0.2.1","version_comment":"fix the bug on *unix system \r\nhttps:\/\/github.com\/iamcco\/markdown-preview.vim\/issues","3":"fix the bug on *unix system \r\nhttps:\/\/github.com\/iamcco\/markdown-preview.vim\/issues","package":"markdown-preview.vim-0.2.1.zip","4":"markdown-preview.vim-0.2.1.zip","src_id":"23990","5":"23990","creation_date":"1454682104","6":"1454682104"},{"0":"5324","vim_version":"7.4","1":"7.4","script_version":"0.2.0","2":"0.2.0","version_comment":"Initial upload","3":"Initial upload","package":"markdown-preview.vim-0.2.0.zip","4":"markdown-preview.vim-0.2.0.zip","src_id":"23983","5":"23983","creation_date":"1454483928","6":"1454483928"}]},"5323":{"script_id":"5323","0":"5323","script_name":"vim-llvmcov","1":"vim-llvmcov","script_type":"utility","2":"utility","summary":"The llvm-cov tool shows code coverage information for C,C++,Objective-C","3":"The llvm-cov tool shows code coverage information for C,C++,Objective-C","description":"Project page: https:\/\/github.com\/alepez\/vim-llvmcov\r\n\r\nVim plugin to show code coverage with llvm cov tool.\r\n\r\nThe llvm-cov tool shows code coverage information for programs that are instrumented to emit profile data.\r\n\r\nThis plugin works with languages supported by llvm: C,C++,Objective-C.","4":"Project page: https:\/\/github.com\/alepez\/vim-llvmcov\r\n\r\nVim plugin to show code coverage with llvm cov tool.\r\n\r\nThe llvm-cov tool shows code coverage information for programs that are instrumented to emit profile data.\r\n\r\nThis plugin works with languages supported by llvm: C,C++,Objective-C.","install_details":"Needs clang compiler.","5":"Needs clang compiler.","first_name":"Alessandro","6":"Alessandro","last_name":"Pezzato","7":"Pezzato","releases":[{"0":"5323","vim_version":"7.0","1":"7.0","script_version":"0.1.0","2":"0.1.0","version_comment":"Initial upload","3":"Initial upload","package":"vim-llvmcov.zip","4":"vim-llvmcov.zip","src_id":"23974","5":"23974","creation_date":"1454273568","6":"1454273568"}]},"5322":{"script_id":"5322","0":"5322","script_name":"vim-fake","1":"vim-fake","script_type":"utility","2":"utility","summary":" A random dummy\/filler text generator","3":" A random dummy\/filler text generator","description":"Vim-fake is a Vim plugin to provide a generator of random dummy\/filler text, which is useful to generate a nonsense text like Lorem ipsum.\r\n\r\nSee https:\/\/github.com\/tkhren\/vim-fake","4":"Vim-fake is a Vim plugin to provide a generator of random dummy\/filler text, which is useful to generate a nonsense text like Lorem ipsum.\r\n\r\nSee https:\/\/github.com\/tkhren\/vim-fake","install_details":"","5":"","first_name":"tkhren","6":"tkhren","last_name":"","7":"","releases":[{"0":"5322","vim_version":"7.3","1":"7.3","script_version":"0.1.0","2":"0.1.0","version_comment":"Initial upload","3":"Initial upload","package":"vim-fake.zip","4":"vim-fake.zip","src_id":"23968","5":"23968","creation_date":"1454145480","6":"1454145480"}]},"5321":{"script_id":"5321","0":"5321","script_name":"Alduin","1":"Alduin","script_type":"color scheme","2":"color scheme","summary":"Vim Colorscheme for Terminals and GUI","3":"Vim Colorscheme for Terminals and GUI","description":"A dark low-contrast colorscheme for Terminal Vim and GUI Vim.\r\n\r\nFor Screenshots, color options, and future downloads check out the  GitHub repo:\r\nhttps:\/\/github.com\/AlessandroYorba\/Alduin","4":"A dark low-contrast colorscheme for Terminal Vim and GUI Vim.\r\n\r\nFor Screenshots, color options, and future downloads check out the  GitHub repo:\r\nhttps:\/\/github.com\/AlessandroYorba\/Alduin","install_details":"For Unix users, place alduin.vim in ~\/.vim\/colors \r\nWindows users, place alduin.vim in ~\\vimfiles\\colors\r\n\r\nor use your favorite package manager\r\n","5":"For Unix users, place alduin.vim in ~\/.vim\/colors \r\nWindows users, place alduin.vim in ~\\vimfiles\\colors\r\n\r\nor use your favorite package manager\r\n","first_name":"Alessandro","6":"Alessandro","last_name":"Yorba","7":"Yorba","releases":[{"0":"5321","vim_version":"7.0","1":"7.0","script_version":"b804874","2":"b804874","version_comment":"Enjoy!","3":"Enjoy!","package":"alduin.vim","4":"alduin.vim","src_id":"26944","5":"26944","creation_date":"1580309207","6":"1580309207"},{"0":"5321","vim_version":"7.0","1":"7.0","script_version":"b4003cf ","2":"b4003cf ","version_comment":"A malt-caramel skooma made with snowberries and dart wings. \r\n* Improved groups in Pmenu, StatusLine, Tabline\r\n* Updated terminal themes\r\n\r\nfor more info checkout: https:\/\/github.com\/AlessandroYorba\/Alduin","3":"A malt-caramel skooma made with snowberries and dart wings. \r\n* Improved groups in Pmenu, StatusLine, Tabline\r\n* Updated terminal themes\r\n\r\nfor more info checkout: https:\/\/github.com\/AlessandroYorba\/Alduin","package":"alduin.vim","4":"alduin.vim","src_id":"25694","5":"25694","creation_date":"1512603548","6":"1512603548"},{"0":"5321","vim_version":"7.0","1":"7.0","script_version":"6.0.0","2":"6.0.0","version_comment":"Latest Update","3":"Latest Update","package":"alduin.vim","4":"alduin.vim","src_id":"25491","5":"25491","creation_date":"1502316891","6":"1502316891"}]},"5320":{"script_id":"5320","0":"5320","script_name":"vim-swap","1":"vim-swap","script_type":"utility","2":"utility","summary":"Reorder delimited items.","3":"Reorder delimited items.","description":"vim-swap is an plugin to reorder delimited items. Considering the following code snippet, it is easy to swap \"arg2\" and \"arg3\" but is annoying work that swaps \"arg1\" and \"arg2\" since user have to manage a word and a delimiter separately.\r\n\r\n\tcall foo(arg1, arg2, arg3)\r\n\r\nThis plugin serves mappings to make easier to do that kind of operations. This plugin defines three mappings in default, g<, g>, gs. g< swaps the item under the cursor with the former item. Moving cursor on the \"arg2\" and pressing g<, then it swaps \"arg2\" and the former one, \"arg1\", to get:\r\n\r\n\tcall foo(arg2, arg1, arg3)\r\n\r\ng> swaps the item under the cursor with the latter item. Moving cursor on the \"arg2\" and pressing g>, then it swaps \"arg2\" and the latter one, \"arg3\", to get:\r\n\r\n\tcall foo(arg1, arg3, arg2)\r\n\r\ngs works more interactive. It starts \"swap mode\", as if there was the sub-mode of vim editor. In the mode, use h\/l to swap items, j\/k to choose item, numbers 1 ~ 9 to select nth item, u\/ to undo\/redo, and as you know  to exit \"swap mode\".\r\n\r\nLatest version: https:\/\/github.com\/machakann\/vim-swap","4":"vim-swap is an plugin to reorder delimited items. Considering the following code snippet, it is easy to swap \"arg2\" and \"arg3\" but is annoying work that swaps \"arg1\" and \"arg2\" since user have to manage a word and a delimiter separately.\r\n\r\n\tcall foo(arg1, arg2, arg3)\r\n\r\nThis plugin serves mappings to make easier to do that kind of operations. This plugin defines three mappings in default, g<, g>, gs. g< swaps the item under the cursor with the former item. Moving cursor on the \"arg2\" and pressing g<, then it swaps \"arg2\" and the former one, \"arg1\", to get:\r\n\r\n\tcall foo(arg2, arg1, arg3)\r\n\r\ng> swaps the item under the cursor with the latter item. Moving cursor on the \"arg2\" and pressing g>, then it swaps \"arg2\" and the latter one, \"arg3\", to get:\r\n\r\n\tcall foo(arg1, arg3, arg2)\r\n\r\ngs works more interactive. It starts \"swap mode\", as if there was the sub-mode of vim editor. In the mode, use h\/l to swap items, j\/k to choose item, numbers 1 ~ 9 to select nth item, u\/ to undo\/redo, and as you know  to exit \"swap mode\".\r\n\r\nLatest version: https:\/\/github.com\/machakann\/vim-swap","install_details":"Unzip and put all folders in your ~\/.vim.","5":"Unzip and put all folders in your ~\/.vim.","first_name":"Masaaki","6":"Masaaki","last_name":"Nakamura","7":"Nakamura","releases":[{"0":"5320","vim_version":"7.4","1":"7.4","script_version":"1.0.6","2":"1.0.6","version_comment":"Bug fixes","3":"Bug fixes","package":"vim-swap-1.0.6.zip","4":"vim-swap-1.0.6.zip","src_id":"25378","5":"25378","creation_date":"1499253932","6":"1499253932"},{"0":"5320","vim_version":"7.4","1":"7.4","script_version":"1.0.5","2":"1.0.5","version_comment":"Bug fixes.","3":"Bug fixes.","package":"vim-swap-1.0.5.zip","4":"vim-swap-1.0.5.zip","src_id":"24381","5":"24381","creation_date":"1469180408","6":"1469180408"},{"0":"5320","vim_version":"7.4","1":"7.4","script_version":"1.0.4","2":"1.0.4","version_comment":"Bug fixes.","3":"Bug fixes.","package":"vim-swap-1.0.4.zip","4":"vim-swap-1.0.4.zip","src_id":"24317","5":"24317","creation_date":"1465704238","6":"1465704238"},{"0":"5320","vim_version":"7.4","1":"7.4","script_version":"1.0.1","2":"1.0.1","version_comment":"Bug fixes and performance tuning.","3":"Bug fixes and performance tuning.","package":"vim-swap-1.0.1.zip","4":"vim-swap-1.0.1.zip","src_id":"23993","5":"23993","creation_date":"1454744361","6":"1454744361"},{"0":"5320","vim_version":"7.4","1":"7.4","script_version":"1.0.0","2":"1.0.0","version_comment":"Initial upload","3":"Initial upload","package":"vim-swap-1.0.0.zip","4":"vim-swap-1.0.0.zip","src_id":"23959","5":"23959","creation_date":"1453908693","6":"1453908693"}]},"5319":{"script_id":"5319","0":"5319","script_name":"hiPairs","1":"hiPairs","script_type":"utility","2":"utility","summary":"Highlights the pair surrounding the current cursor position.","3":"Highlights the pair surrounding the current cursor position.","description":"https:\/\/github.com\/Yggdroot\/hiPairs","4":"https:\/\/github.com\/Yggdroot\/hiPairs","install_details":"Just put hiPairs.vim into the plugin directory.\r\nFor Vundle user, just add Plugin 'Yggdroot\/hiPairs' to your .vimrc.","5":"Just put hiPairs.vim into the plugin directory.\r\nFor Vundle user, just add Plugin 'Yggdroot\/hiPairs' to your .vimrc.","first_name":"Yggdroot","6":"Yggdroot","last_name":"Chen","7":"Chen","releases":[{"0":"5319","vim_version":"7.3","1":"7.3","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"hiPairs.vim","4":"hiPairs.vim","src_id":"23950","5":"23950","creation_date":"1453803128","6":"1453803128"}]},"5318":{"script_id":"5318","0":"5318","script_name":"todoapp","1":"todoapp","script_type":"utility","2":"utility","summary":"Manage your todos in vim with app like experience","3":"Manage your todos in vim with app like experience","description":"Lightweight and easy to use todo management in vim.\r\n\r\nusing [unite.vim](https:\/\/github.com\/Shougo\/unite.vim) and sqlite.\r\n\r\nSqlite is used so that you can build other application on top of it, like a web\r\nservice that could be accessed from your phone.\r\n\r\n## Usage\r\n\r\n* `:Todoadd [content]` add todo item.\r\n* `:TodoInit` init todo database\r\n* `:TodoImport` import todos from a plain file\r\n* `Unite todo` show all todo that need to be done.\r\n* `Unite todo:done` show todos that have been done.\r\n\r\nActions in the unite list:\r\n\r\n* `toggle` default action, press ``\r\n* `edit` edit todo in split buffer, press `q` to save and quit\r\n* `new` create new todo through prompt\r\n* `delete`","4":"Lightweight and easy to use todo management in vim.\r\n\r\nusing [unite.vim](https:\/\/github.com\/Shougo\/unite.vim) and sqlite.\r\n\r\nSqlite is used so that you can build other application on top of it, like a web\r\nservice that could be accessed from your phone.\r\n\r\n## Usage\r\n\r\n* `:Todoadd [content]` add todo item.\r\n* `:TodoInit` init todo database\r\n* `:TodoImport` import todos from a plain file\r\n* `Unite todo` show all todo that need to be done.\r\n* `Unite todo:done` show todos that have been done.\r\n\r\nActions in the unite list:\r\n\r\n* `toggle` default action, press ``\r\n* `edit` edit todo in split buffer, press `q` to save and quit\r\n* `new` create new todo through prompt\r\n* `delete`","install_details":"Take [vundle](https:\/\/github.com\/VundleVim\/Vundle.vim) for example:\r\n\r\n    plugin 'Shougo\/unite.vim'\r\n    plugin 'chemzqm\/todoapp.vim'\r\n\r\nInstall [sqlite](https:\/\/www.sqlite.org\/) from it's website, or use brew on mac:\r\n\r\n    brew install sqlite\r\n\r\nSqlite database is available at `~\/.todo\/todo.sqlite`\r\n\r\nAfter install plugin, you need to call `:TodoInit` once to create a todo table in database","5":"Take [vundle](https:\/\/github.com\/VundleVim\/Vundle.vim) for example:\r\n\r\n    plugin 'Shougo\/unite.vim'\r\n    plugin 'chemzqm\/todoapp.vim'\r\n\r\nInstall [sqlite](https:\/\/www.sqlite.org\/) from it's website, or use brew on mac:\r\n\r\n    brew install sqlite\r\n\r\nSqlite database is available at `~\/.todo\/todo.sqlite`\r\n\r\nAfter install plugin, you need to call `:TodoInit` once to create a todo table in database","first_name":"qiming","6":"qiming","last_name":"zhao","7":"zhao","releases":[{"0":"5318","vim_version":"7.0","1":"7.0","script_version":"0.1.0","2":"0.1.0","version_comment":"Initial upload","3":"Initial upload","package":"todoapp.zip","4":"todoapp.zip","src_id":"23940","5":"23940","creation_date":"1453544967","6":"1453544967"}]},"5317":{"script_id":"5317","0":"5317","script_name":"vBox","1":"vBox","script_type":"utility","2":"utility","summary":"A simple template engine for vim","3":"A simple template engine for vim","description":"A simple vim plugin for quickly create and insert templates.\r\n\r\n# Features\r\n\r\n    - Templates specific to file types or file names.\r\n    - Customizable template variables.\r\n    - Command completion.\r\n    - Live template creation & edition.\r\n\r\n# Cons\r\n\r\n    - No templates by default, create your own.\r\n    - No auto insertion by default (Use BufNewFile for that).\r\n    - The file type matching is done according to the current &ft, not the extension.\r\n\r\nDetails and configuration in the repository > https:\/\/github.com\/KabbAmine\/vBox.vim\r\n\r\nPlease rate the plugin if you find it useful :)","4":"A simple vim plugin for quickly create and insert templates.\r\n\r\n# Features\r\n\r\n    - Templates specific to file types or file names.\r\n    - Customizable template variables.\r\n    - Command completion.\r\n    - Live template creation & edition.\r\n\r\n# Cons\r\n\r\n    - No templates by default, create your own.\r\n    - No auto insertion by default (Use BufNewFile for that).\r\n    - The file type matching is done according to the current &ft, not the extension.\r\n\r\nDetails and configuration in the repository > https:\/\/github.com\/KabbAmine\/vBox.vim\r\n\r\nPlease rate the plugin if you find it useful :)","install_details":"Copy the distributed files into Vim runtime directory which is usually ~\/.vim\/, or HOME\/vimfiles on Windows.\r\n\r\nOr use a vim plugin manager.\r\ne.g with vim-plug:\r\n\r\n    Plug 'KabbAmine\/vBox.vim'","5":"Copy the distributed files into Vim runtime directory which is usually ~\/.vim\/, or HOME\/vimfiles on Windows.\r\n\r\nOr use a vim plugin manager.\r\ne.g with vim-plug:\r\n\r\n    Plug 'KabbAmine\/vBox.vim'","first_name":"Kabbaj","6":"Kabbaj","last_name":"Amine","7":"Amine","releases":[{"0":"5317","vim_version":"7.0","1":"7.0","script_version":"0.1.0","2":"0.1.0","version_comment":"Initial upload","3":"Initial upload","package":"vBox.tar.gz","4":"vBox.tar.gz","src_id":"23939","5":"23939","creation_date":"1453472158","6":"1453472158"}]},"5316":{"script_id":"5316","0":"5316","script_name":"vim-macos","1":"vim-macos","script_type":"utility","2":"utility","summary":"Autoload functions to help vim user work with macos","3":"Autoload functions to help vim user work with macos","description":"This project is hosted at https:\/\/github.com\/chemzqm\/vim-macos\r\n\r\nIt expose three simple function to help interactive with macos\r\n\r\n### API\r\n\r\n* **macos#open(argument)** open argument(could be any path) with `open` command\r\n* **macos#ItermOpen(dir)** active iterm2 (only support version > 2.9) and open\r\n  directory in a new tab\r\n* **macos#keycodes(list...)** send keycode(s) to MacOS\r\n\r\n## Example\r\n\r\n* Make mappings for NeteaseMusic next song, previous song and pausestart\r\n\r\n``` VimL\r\nnnoremap   :call macos#keycodes('option', 'command', 'left')\r\nnnoremap   :call macos#keycodes('option', 'command', 'right')\r\nnnoremap   :call macos#keycodes('option', 'command', 'space')\r\n```\r\n\r\n*Note*, MacVim is needed for command key mapping, system global shortcut of NeteaseMusic have to be activated\r\n\r\n* A keymapping make iterm2 open directory of current file\r\n\r\n``` VimL\r\nnnoremap to :call macos#ItermOpen(expand('%:p:h'))\r\n```\r\n\r\n* A keymapping make Finder open directory of current file\r\n\r\n``` VimL\r\nnnoremap fo :call macos#open(expand('%:p:h'))\r\n```\r\n\r\n*Note*,  in MacVim only open current working directory","4":"This project is hosted at https:\/\/github.com\/chemzqm\/vim-macos\r\n\r\nIt expose three simple function to help interactive with macos\r\n\r\n### API\r\n\r\n* **macos#open(argument)** open argument(could be any path) with `open` command\r\n* **macos#ItermOpen(dir)** active iterm2 (only support version > 2.9) and open\r\n  directory in a new tab\r\n* **macos#keycodes(list...)** send keycode(s) to MacOS\r\n\r\n## Example\r\n\r\n* Make mappings for NeteaseMusic next song, previous song and pausestart\r\n\r\n``` VimL\r\nnnoremap   :call macos#keycodes('option', 'command', 'left')\r\nnnoremap   :call macos#keycodes('option', 'command', 'right')\r\nnnoremap   :call macos#keycodes('option', 'command', 'space')\r\n```\r\n\r\n*Note*, MacVim is needed for command key mapping, system global shortcut of NeteaseMusic have to be activated\r\n\r\n* A keymapping make iterm2 open directory of current file\r\n\r\n``` VimL\r\nnnoremap to :call macos#ItermOpen(expand('%:p:h'))\r\n```\r\n\r\n* A keymapping make Finder open directory of current file\r\n\r\n``` VimL\r\nnnoremap fo :call macos#open(expand('%:p:h'))\r\n```\r\n\r\n*Note*,  in MacVim only open current working directory","install_details":"\r\nInstall with your favorite plugin managers like NeoBundle\/Plugin\/Plug\r\n\r\n\tNeoBundle 'chemzqm\/macos'\r\n\tPlugin 'chemzqm\/macos'\r\n\tPlug 'chemzqm\/macos'\r\n","5":"\r\nInstall with your favorite plugin managers like NeoBundle\/Plugin\/Plug\r\n\r\n\tNeoBundle 'chemzqm\/macos'\r\n\tPlugin 'chemzqm\/macos'\r\n\tPlug 'chemzqm\/macos'\r\n","first_name":"qiming","6":"qiming","last_name":"zhao","7":"zhao","releases":[{"0":"5316","vim_version":"7.4","1":"7.4","script_version":"0.1.0","2":"0.1.0","version_comment":"Initial upload","3":"Initial upload","package":"macos.zip","4":"macos.zip","src_id":"23936","5":"23936","creation_date":"1453379709","6":"1453379709"}]},"5315":{"script_id":"5315","0":"5315","script_name":"macdown.vim","1":"macdown.vim","script_type":"utility","2":"utility","summary":"Live preview markdown in Chrome using applescript ","3":"Live preview markdown in Chrome using applescript ","description":"# Macdown.vim\r\n\r\nThis project is hosted at https:\/\/github.com\/chemzqm\/macdown.vim\r\n\r\nA simplified and flexible markdown preview for vim user on Mac.\r\nUsing applescript instead of a server to enhance the exprience of live preview.\r\n\r\nYou can get the style preview [here](https:\/\/chemzqm.me\/static\/sample.html)\r\n\r\n## Features\r\n\r\n* Works out of box, all dependencies are optional.\r\n* Preview in Chrome with range and auto reload support.\r\n* Auto close Chrome tab on buffer delete and vim exit.\r\n* Async markdown parse.\r\n* Tables, GFM enabled, code highlight and footnote enabled by default.\r\n* Misaka parser support [smartypants](http:\/\/misaka.61924.nl\/#misaka.smartypants),\r\ntoc (table of content) and unicode (including Emoji)\r\n\r\n## Install\r\n\r\nTake [vundle](https:\/\/github.com\/VundleVim\/Vundle.vim) as example:\r\n\r\n    Plugin \\'chemzqm\/macdown.vim\\'\r\n\r\nIf you need async markdown parse, just install\r\n[vimproc.vim](https: \/\/github.com\/Shougo\/vimproc.vim)\r\n\r\n    Plugin \\'Shougo\/vimproc.vim\\'\r\n\r\n## Usage\r\n\r\nTo preview current markdown file, type:\r\n\r\n    :Preview\r\n\r\nPreview with range, eg:\r\n\r\n    :1,10Preview\r\n\r\nOr visual select a range, and use:\r\n\r\n    :\\'<,\\'>Preview\r\n\r\nTo toggle auto preview for current file, type:\r\n\r\n    :PreviewAuto\r\n\r\nThe corresponding chrome tab would be activated and refreshed on CursorHold and\r\nBufWrite. A handy remap could be:\r\n\r\n    nnoremap  :PreviewAuto\r\n\r\n## Configuration\r\n\r\nBy default `macdown.vim` using [markit](https:\/\/github.com\/lepture\/markit) for\r\nmarkdown parsing, it\\'s exists inside this repository, but if you need speed and\r\nmore future, you can set global variable:\r\n\r\n    let g:macdown_marked_programme = \\'misaka\\'\r\n\r\nTo enable misaka parse, it\\'s almost 4 times faster than markit, but you need to\r\ninstall python dependencies:\r\n\r\n    pip install misaka pygments\r\n\r\n`sudo` might be required.\r\n\r\nYou can also make your own parser, it\\'s just create a excutable file inside\r\n`macdown.vim\/bin` which accept markdown content from stdin and output html to\r\nstdout.\r\n\r\n## TODO\r\n\r\n* Scrollbind for vim and Chrome\r\n","4":"# Macdown.vim\r\n\r\nThis project is hosted at https:\/\/github.com\/chemzqm\/macdown.vim\r\n\r\nA simplified and flexible markdown preview for vim user on Mac.\r\nUsing applescript instead of a server to enhance the exprience of live preview.\r\n\r\nYou can get the style preview [here](https:\/\/chemzqm.me\/static\/sample.html)\r\n\r\n## Features\r\n\r\n* Works out of box, all dependencies are optional.\r\n* Preview in Chrome with range and auto reload support.\r\n* Auto close Chrome tab on buffer delete and vim exit.\r\n* Async markdown parse.\r\n* Tables, GFM enabled, code highlight and footnote enabled by default.\r\n* Misaka parser support [smartypants](http:\/\/misaka.61924.nl\/#misaka.smartypants),\r\ntoc (table of content) and unicode (including Emoji)\r\n\r\n## Install\r\n\r\nTake [vundle](https:\/\/github.com\/VundleVim\/Vundle.vim) as example:\r\n\r\n    Plugin \\'chemzqm\/macdown.vim\\'\r\n\r\nIf you need async markdown parse, just install\r\n[vimproc.vim](https: \/\/github.com\/Shougo\/vimproc.vim)\r\n\r\n    Plugin \\'Shougo\/vimproc.vim\\'\r\n\r\n## Usage\r\n\r\nTo preview current markdown file, type:\r\n\r\n    :Preview\r\n\r\nPreview with range, eg:\r\n\r\n    :1,10Preview\r\n\r\nOr visual select a range, and use:\r\n\r\n    :\\'<,\\'>Preview\r\n\r\nTo toggle auto preview for current file, type:\r\n\r\n    :PreviewAuto\r\n\r\nThe corresponding chrome tab would be activated and refreshed on CursorHold and\r\nBufWrite. A handy remap could be:\r\n\r\n    nnoremap  :PreviewAuto\r\n\r\n## Configuration\r\n\r\nBy default `macdown.vim` using [markit](https:\/\/github.com\/lepture\/markit) for\r\nmarkdown parsing, it\\'s exists inside this repository, but if you need speed and\r\nmore future, you can set global variable:\r\n\r\n    let g:macdown_marked_programme = \\'misaka\\'\r\n\r\nTo enable misaka parse, it\\'s almost 4 times faster than markit, but you need to\r\ninstall python dependencies:\r\n\r\n    pip install misaka pygments\r\n\r\n`sudo` might be required.\r\n\r\nYou can also make your own parser, it\\'s just create a excutable file inside\r\n`macdown.vim\/bin` which accept markdown content from stdin and output html to\r\nstdout.\r\n\r\n## TODO\r\n\r\n* Scrollbind for vim and Chrome\r\n","install_details":"\tNeoBundle \\'chemzqm\/macdown.vim\\'\r\n\tPlugin \\'chemzqm\/macdown.vim\\'\r\n\tPlug \\'chemzqm\/macdown.vim\\'\r\n|vimproc| is requried to do the async markdown parse job, it would be\r\ninstalled via |vim-plug|:\r\n\r\n\tPlug \\'Shougo\/vimproc.vim\\',{\\'do\\', \\'yes\\\\|make\\'}\r\n\r\nFollow the installation guide of |vimproc| if you got problem during\r\ninstallation.\r\n\r\nIf you want to use misaka https:\/\/github.com\/FSX\/misaka for markdown parse, you have to install python dependencies by:\r\n\r\n        pip install misaka pygments","5":"\tNeoBundle \\'chemzqm\/macdown.vim\\'\r\n\tPlugin \\'chemzqm\/macdown.vim\\'\r\n\tPlug \\'chemzqm\/macdown.vim\\'\r\n|vimproc| is requried to do the async markdown parse job, it would be\r\ninstalled via |vim-plug|:\r\n\r\n\tPlug \\'Shougo\/vimproc.vim\\',{\\'do\\', \\'yes\\\\|make\\'}\r\n\r\nFollow the installation guide of |vimproc| if you got problem during\r\ninstallation.\r\n\r\nIf you want to use misaka https:\/\/github.com\/FSX\/misaka for markdown parse, you have to install python dependencies by:\r\n\r\n        pip install misaka pygments","first_name":"qiming","6":"qiming","last_name":"zhao","7":"zhao","releases":[{"0":"5315","vim_version":"7.0","1":"7.0","script_version":"0.1.0","2":"0.1.0","version_comment":"Initial upload","3":"Initial upload","package":"macdown.zip","4":"macdown.zip","src_id":"23935","5":"23935","creation_date":"1453378118","6":"1453378118"}]},"5313":{"script_id":"5313","0":"5313","script_name":"Snake","1":"Snake","script_type":"game","2":"game","summary":"Snake game in vim","3":"Snake game in vim","description":"this is the game of snake for vim. Move the snake, eat the apples, get the high score, do it again. start the game by typing \":Snake\". hjkl moves the snake, s starts a new game, q quits the game.","4":"this is the game of snake for vim. Move the snake, eat the apples, get the high score, do it again. start the game by typing \":Snake\". hjkl moves the snake, s starts a new game, q quits the game.","install_details":"place the script into .vim\/plugin\/.","5":"place the script into .vim\/plugin\/.","first_name":"Jacob","6":"Jacob","last_name":"Gelbman","7":"Gelbman","releases":[{"0":"5313","vim_version":"7.0","1":"7.0","script_version":"2.0.0","2":"2.0.0","version_comment":"slow down, multiple apples, fix positioning","3":"slow down, multiple apples, fix positioning","package":"snake.vim","4":"snake.vim","src_id":"23957","5":"23957","creation_date":"1453843094","6":"1453843094"},{"0":"5313","vim_version":"7.0","1":"7.0","script_version":"1.0.0","2":"1.0.0","version_comment":"Initial upload","3":"Initial upload","package":"snake.vim","4":"snake.vim","src_id":"23932","5":"23932","creation_date":"1453246000","6":"1453246000"}]},"5312":{"script_id":"5312","0":"5312","script_name":"VimSum","1":"VimSum","script_type":"utility","2":"utility","summary":"Simple visual mode arithmetic in Vim","3":"Simple visual mode arithmetic in Vim","description":" Github page with example use:\r\nhttps:\/\/github.com\/wgurecky\/vimSum\r\n\r\nVimSum is a collection of simple scripts that provide the ability to perform basic calculations in vim.\r\nThe scripts can be used on columns of numbers by selecting them in visual mode. The scripts also can operate on mixed number\/word paragraphs (only operating on numbers). The format of numbers in text may also be adjusted using the VisMult or VisMath script.\r\n\r\nCommon use cases:\r\n\r\n- Multiply many numbers by a constant.  Encountered when changing units.\r\n- Compute sum or mean of column in text file and immediately paste result back into text.\r\n- Perform basic arithmetic on a column of numbers.\r\n- Change format of numbers in text e.g. from scientific notation to decimal format.\r\n\r\nInspired by visSum.vim by erik falor.","4":" Github page with example use:\r\nhttps:\/\/github.com\/wgurecky\/vimSum\r\n\r\nVimSum is a collection of simple scripts that provide the ability to perform basic calculations in vim.\r\nThe scripts can be used on columns of numbers by selecting them in visual mode. The scripts also can operate on mixed number\/word paragraphs (only operating on numbers). The format of numbers in text may also be adjusted using the VisMult or VisMath script.\r\n\r\nCommon use cases:\r\n\r\n- Multiply many numbers by a constant.  Encountered when changing units.\r\n- Compute sum or mean of column in text file and immediately paste result back into text.\r\n- Perform basic arithmetic on a column of numbers.\r\n- Change format of numbers in text e.g. from scientific notation to decimal format.\r\n\r\nInspired by visSum.vim by erik falor.","install_details":"Requires vim built with +python","5":"Requires vim built with +python","first_name":"will","6":"will","last_name":"gurecky","7":"gurecky","releases":[{"0":"5312","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"VimSum.zip","4":"VimSum.zip","src_id":"23916","5":"23916","creation_date":"1452958903","6":"1452958903"}]},"5310":{"script_id":"5310","0":"5310","script_name":"vZoom","1":"vZoom","script_type":"utility","2":"utility","summary":"Quickly maximize\/unmaximize the current window","3":"Quickly maximize\/unmaximize the current window","description":"This plugin allows to maximize\/unmaximize the current window manually using a key mapping or automatically via  a command.\r\n \r\nDetails & demo here > https:\/\/github.com\/KabbAmine\/vZoom.vim\r\n\r\nPlease rate it if you find it useful :)","4":"This plugin allows to maximize\/unmaximize the current window manually using a key mapping or automatically via  a command.\r\n \r\nDetails & demo here > https:\/\/github.com\/KabbAmine\/vZoom.vim\r\n\r\nPlease rate it if you find it useful :)","install_details":"Copy the distributed files into Vim runtime directory which is usually ~\/.vim\/, or $HOME\/vimfiles on Windows.\r\n\r\nOr use a vim plugin manager.\r\ne.g with vim-plug plus lazyloading:\r\n\r\n    Plug 'KabbAmine\/vZoom.vim', {'on': '(vzoom)'}","5":"Copy the distributed files into Vim runtime directory which is usually ~\/.vim\/, or $HOME\/vimfiles on Windows.\r\n\r\nOr use a vim plugin manager.\r\ne.g with vim-plug plus lazyloading:\r\n\r\n    Plug 'KabbAmine\/vZoom.vim', {'on': '(vzoom)'}","first_name":"Kabbaj","6":"Kabbaj","last_name":"Amine","7":"Amine","releases":[{"0":"5310","vim_version":"7.0","1":"7.0","script_version":"0.3","2":"0.3","version_comment":"    - INTERNAL: More refactoring related to augroups and autocommands\r\n    - FEATURE: Add user's configuration and a 1st option: equalise_windows\r\n    - Add a doc file\r\n0.2\r\n    - INTERNAL: Small refactoring\r\n    - FEATURE : New command VZoomAutoToggle to enable\/disable auto zoom\r\n","3":"    - INTERNAL: More refactoring related to augroups and autocommands\r\n    - FEATURE: Add user's configuration and a 1st option: equalise_windows\r\n    - Add a doc file\r\n0.2\r\n    - INTERNAL: Small refactoring\r\n    - FEATURE : New command VZoomAutoToggle to enable\/disable auto zoom\r\n","package":"vZoom.tar.gz","4":"vZoom.tar.gz","src_id":"23963","5":"23963","creation_date":"1454091562","6":"1454091562"},{"0":"5310","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"vZoom.tar.gz","4":"vZoom.tar.gz","src_id":"23906","5":"23906","creation_date":"1452792324","6":"1452792324"}]},"5309":{"script_id":"5309","0":"5309","script_name":"vimdiffext","1":"vimdiffext","script_type":"ftplugin","2":"ftplugin","summary":"An easier way to vim-diff files and directories.","3":"An easier way to vim-diff files and directories.","description":"Adds some more handling for diff output.\r\n\r\nThe most useful probably for multi-file and recursive diffs which are not supported originally.\r\n\r\nTo use it, just open a patch file or do something like:\r\n$ diff -r -u folder1 folder2 | vim -R -\r\n\r\nThe added features are:\r\n\r\n1. Folds for each individual file and each diff block within.\r\nSince there are no folds originally defined for diff filetype, I added what it made sense for me.\r\n\r\n2. A command to open a side-by-side diff mode in a new tab.\r\nThe new command is DD (stands for DoDiff) and keymap for it d (\\d for me) in diff file.\r\n\r\nTo invoke it,\r\nplace the cursor on line containing the diff command line:\r\n....\r\ndiff [options ...] file1 file2\r\n....\r\nand type :DD\r\nor press \\d\r\n... a new tab with side-by-side diff mode will appear.\r\n\r\nThe files must be accessible by their paths from the current location.\r\n\r\n3. Paragraph and section motions: [[ ]] { } move to the next\/previous difference\/file.\r\n\r\n\r\nThis is the most light-weight and easy solution to compare or sync two folders (recursively) using vim.","4":"Adds some more handling for diff output.\r\n\r\nThe most useful probably for multi-file and recursive diffs which are not supported originally.\r\n\r\nTo use it, just open a patch file or do something like:\r\n$ diff -r -u folder1 folder2 | vim -R -\r\n\r\nThe added features are:\r\n\r\n1. Folds for each individual file and each diff block within.\r\nSince there are no folds originally defined for diff filetype, I added what it made sense for me.\r\n\r\n2. A command to open a side-by-side diff mode in a new tab.\r\nThe new command is DD (stands for DoDiff) and keymap for it d (\\d for me) in diff file.\r\n\r\nTo invoke it,\r\nplace the cursor on line containing the diff command line:\r\n....\r\ndiff [options ...] file1 file2\r\n....\r\nand type :DD\r\nor press \\d\r\n... a new tab with side-by-side diff mode will appear.\r\n\r\nThe files must be accessible by their paths from the current location.\r\n\r\n3. Paragraph and section motions: [[ ]] { } move to the next\/previous difference\/file.\r\n\r\n\r\nThis is the most light-weight and easy solution to compare or sync two folders (recursively) using vim.","install_details":"1. Unpack into your vim home directory (~\/.vim\/ for Unixes, _vim for Windows):\r\n\r\n    $ cd ~\/.vim ; tar zxf ~\/Downloads\/vimdiffext.tgz\r\n\r\n2. Enjoy","5":"1. Unpack into your vim home directory (~\/.vim\/ for Unixes, _vim for Windows):\r\n\r\n    $ cd ~\/.vim ; tar zxf ~\/Downloads\/vimdiffext.tgz\r\n\r\n2. Enjoy","first_name":"Yuriy","6":"Yuriy","last_name":"Ershov","7":"Ershov","releases":[{"0":"5309","vim_version":"7.0","1":"7.0","script_version":"1.0.1","2":"1.0.1","version_comment":"* Added paragraph motion to diff mode.\r\n* In vertical diff, the left and the right files are always on their correspondent sides.","3":"* Added paragraph motion to diff mode.\r\n* In vertical diff, the left and the right files are always on their correspondent sides.","package":"vimdiffext.tgz","4":"vimdiffext.tgz","src_id":"23944","5":"23944","creation_date":"1453698811","6":"1453698811"},{"0":"5309","vim_version":"7.0","1":"7.0","script_version":"1.0.0","2":"1.0.0","version_comment":"Initial upload","3":"Initial upload","package":"vimdiffext.tgz","4":"vimdiffext.tgz","src_id":"23901","5":"23901","creation_date":"1452748776","6":"1452748776"}]},"5308":{"script_id":"5308","0":"5308","script_name":"vim-keeppad","1":"vim-keeppad","script_type":"utility","2":"utility","summary":"Keep padding!","3":"Keep padding!","description":"See https:\/\/github.com\/haya14busa\/vim-keeppad","4":"See https:\/\/github.com\/haya14busa\/vim-keeppad","install_details":"","5":"","first_name":"haya14busa","6":"haya14busa","last_name":" ","7":" ","releases":[{"0":"5308","vim_version":"7.3","1":"7.3","script_version":"v0.9.0","2":"v0.9.0","version_comment":"Initial upload","3":"Initial upload","package":"vim-keeppad-0.9.0.zip","4":"vim-keeppad-0.9.0.zip","src_id":"23893","5":"23893","creation_date":"1452640821","6":"1452640821"}]},"5307":{"script_id":"5307","0":"5307","script_name":"vim-signjk-motion","1":"vim-signjk-motion","script_type":"utility","2":"utility","summary":" j\/k motion with Hit-A-Hint","3":" j\/k motion with Hit-A-Hint","description":"See https:\/\/github.com\/haya14busa\/vim-signjk-motion","4":"See https:\/\/github.com\/haya14busa\/vim-signjk-motion","install_details":"","5":"","first_name":"haya14busa","6":"haya14busa","last_name":" ","7":" ","releases":[{"0":"5307","vim_version":"7.0","1":"7.0","script_version":"v0.9.0","2":"v0.9.0","version_comment":"Initial upload","3":"Initial upload","package":"vim-signjk-motion-0.9.0.zip","4":"vim-signjk-motion-0.9.0.zip","src_id":"23892","5":"23892","creation_date":"1452632776","6":"1452632776"}]},"5306":{"script_id":"5306","0":"5306","script_name":"mycomment","1":"mycomment","script_type":"utility","2":"utility","summary":"quickly toggle comment without thinking","3":"quickly toggle comment without thinking","description":"# Mycomment\r\n\r\n_A stupid comment plugin made for people can't remember so many mappings:)_\r\n\r\nYou only need to remember one mapping for comment:  `c`\r\n\r\n## API\r\n\r\n### [count]\\cc\r\n\r\nToggle comment of `count`(default current line) lines.\r\n\r\n### \\cip\r\n\r\nToggle comment of a block. Yes, it's a motion mapping, `ip` could be any motion object.\r\n\r\n### V\\*\\*\\*\\c\r\n\r\nSelect a block and toggle comment\r\n\r\n## More productive\r\n\r\nYou can use `.` to repeat your last comment command, no need [vim-repeat](https:\/\/github.com\/tpope\/vim-repeat).\r\n\r\nIf you have [emmet-vim](https:\/\/github.com\/mattn\/emmet-vim), the plugin would use emmet comment function for comment toggle of tags in html\/xml\/xhtml files\r\n\r\n## License\r\n\r\nMIT\r\n","4":"# Mycomment\r\n\r\n_A stupid comment plugin made for people can't remember so many mappings:)_\r\n\r\nYou only need to remember one mapping for comment:  `c`\r\n\r\n## API\r\n\r\n### [count]\\cc\r\n\r\nToggle comment of `count`(default current line) lines.\r\n\r\n### \\cip\r\n\r\nToggle comment of a block. Yes, it's a motion mapping, `ip` could be any motion object.\r\n\r\n### V\\*\\*\\*\\c\r\n\r\nSelect a block and toggle comment\r\n\r\n## More productive\r\n\r\nYou can use `.` to repeat your last comment command, no need [vim-repeat](https:\/\/github.com\/tpope\/vim-repeat).\r\n\r\nIf you have [emmet-vim](https:\/\/github.com\/mattn\/emmet-vim), the plugin would use emmet comment function for comment toggle of tags in html\/xml\/xhtml files\r\n\r\n## License\r\n\r\nMIT\r\n","install_details":"Install with your favorite plugin managers like NeoBundle\/Plugin\/Plug\r\n>\r\n>\r\n\tNeoBundle 'chemzqm\/mycomment'\r\n\tPlugin 'chemzqm\/mycomment'\r\n\tPlug 'chemzqm\/mycomment'","5":"Install with your favorite plugin managers like NeoBundle\/Plugin\/Plug\r\n>\r\n>\r\n\tNeoBundle 'chemzqm\/mycomment'\r\n\tPlugin 'chemzqm\/mycomment'\r\n\tPlug 'chemzqm\/mycomment'","first_name":"qiming","6":"qiming","last_name":"zhao","7":"zhao","releases":[{"0":"5306","vim_version":"7.0","1":"7.0","script_version":"0.1.0","2":"0.1.0","version_comment":"Initial upload","3":"Initial upload","package":"mycomment.zip","4":"mycomment.zip","src_id":"23886","5":"23886","creation_date":"1452421157","6":"1452421157"}]},"5305":{"script_id":"5305","0":"5305","script_name":"unite-gitlog","1":"unite-gitlog","script_type":"utility","2":"utility","summary":"A unite source for git log","3":"A unite source for git log","description":"This project is hosted at github: https:\/\/github.com\/chemzqm\/unite-git-log\r\n\r\nunite-gitlog let you works with gitlog combined with the power of unite.\r\nStart unite-gitlog with command like: >\r\n\r\n\t:Unite gitlog\r\n\r\nNote: command need shell to work, may not works on windows, never tested\r\n\r\n## PREREQUIREMENT\t\r\n\r\nThis plugin requires |unite|, |vimproc| and |easygit| to work.  If you're\r\nusing vundle, you can install them by add:\r\n\r\nIf you use fugitive you can use tag 0.1.0 at github and skip install of easygit","4":"This project is hosted at github: https:\/\/github.com\/chemzqm\/unite-git-log\r\n\r\nunite-gitlog let you works with gitlog combined with the power of unite.\r\nStart unite-gitlog with command like: >\r\n\r\n\t:Unite gitlog\r\n\r\nNote: command need shell to work, may not works on windows, never tested\r\n\r\n## PREREQUIREMENT\t\r\n\r\nThis plugin requires |unite|, |vimproc| and |easygit| to work.  If you're\r\nusing vundle, you can install them by add:\r\n\r\nIf you use fugitive you can use tag 0.1.0 at github and skip install of easygit","install_details":"This plugin requires |unite|, |vimproc| and |easygit| to work.  If you're\r\nusing vundle, you can install them by add:\r\n>\r\n\tPlugin 'Shougo\/unite.vim'\r\n\tPlugin 'Shougo\/vimproc'\r\n\tPlugin 'chemzqm\/easygit'\r\n        Plugin 'chemzqm\/unite-git-log'","5":"This plugin requires |unite|, |vimproc| and |easygit| to work.  If you're\r\nusing vundle, you can install them by add:\r\n>\r\n\tPlugin 'Shougo\/unite.vim'\r\n\tPlugin 'Shougo\/vimproc'\r\n\tPlugin 'chemzqm\/easygit'\r\n        Plugin 'chemzqm\/unite-git-log'","first_name":"qiming","6":"qiming","last_name":"zhao","7":"zhao","releases":[{"0":"5305","vim_version":"7.0","1":"7.0","script_version":"0.2.0","2":"0.2.0","version_comment":"Initial upload","3":"Initial upload","package":"unite-gitlog.zip","4":"unite-gitlog.zip","src_id":"23882","5":"23882","creation_date":"1452259884","6":"1452259884"}]},"5304":{"script_id":"5304","0":"5304","script_name":"easygit","1":"easygit","script_type":"utility","2":"utility","summary":"A git wrapper focus on simplily and usability","3":"A git wrapper focus on simplily and usability","description":"Easygit  is hosted at github: https:\/\/github.com\/chemzqm\/vim-easygit\r\n\r\nIt's git wrapper plugin made to replace [fugitive](https:\/\/github.com\/tpope\/vim-fugitive),\r\nit can be used together with fugitive as commands are disabled by default.\r\n\r\nEasygit tried to introduce cleaner code and behaviour more friendly to user.\r\n\r\n## NOTICE\r\n\r\nSome command use command line utilities, they possibly not works on windows.\r\n\r\n## PHILOSOPHY\r\n\r\nEasygit tris hard to works well 80% of daily usage git commands while avoid\r\noverhead complexity.\r\n\r\n\t* All commands work on the git repository of current file, not current\r\n\tCWD!!  This could be a life saving if you switch the file of different\r\n\trepo a lot, to make the command behaviour reasonable, you can set\r\n\t|g:easygit_auto_lcd| to 1.\r\n\r\n\t* Commands would always available, just set |g:easygit_enable_command|\r\n\tto 1\r\n\r\n\t* No useless messages any more, no press any key to continue\r\n\r\n\t* No wait, dispatch remote commands to shell if  |vim-dispatch| or\r\n\t|vim-iterm-start| available\r\n\t\r\n\t* Expose autoload functions, could be used anywhere.\r\n\t\r\n\t* Well designed default options, works out of box.\r\n\r\n\t* Friendly to other plugins, commands are disabled by default to avoid\r\n\tconflict, |buftype| are set to nofile and |bufhidden| are set to\r\n\tdelete for the temporary buffers.\r\n\r\n\t* Enhanced gitlog support, implemented in a separate plugin\r\n\thttps:\/\/github.com\/chemzqm\/unite-git-log, which make uses the power of\r\n\t|unite.vim|\r\n\r\n## COMMANDS\r\n\r\nCommands are disabled by default to make it works with fugitive by default, , you have to add\r\n\r\n    let g:easygit_enable_command = 1\r\n\r\nto your `.vimrc`, no further action required.\r\n\r\n* *Gcd*             make vim cd to git root directory.\r\n* *Glcd*            make vim lcd to git root directory.\r\n* *Gblame*          Git blame current file, you can use `p` to preview commit and `d`\r\nto diff with current file.\r\n* *GcommitCurrent*  Git commit current file with message as command args.\r\n* *GdiffThis*       Side by side diff of current file with head or any ref.\r\n* *Gcommit*         Git commit with command line argument.\r\n* *Gedit*           Edit git reference from git show.\r\n* *Gdiff*           Git diff with command line argument.\r\n* *Gremove*         Git remove with command line argument, remove current file\r\nwhen arguments empty.\r\n* *Grename*         Rename current by git mv, file in buffer list would react the changes.\r\n* *Gmove*           Git mv with command line argument.\r\n* *Gcheckout*       Git checkout with command line argument.\r\n* *Gpush*           Git push with arguments, dispatch when possible.\r\n* *Gpull*           Git pull with arguments, dispatch when possible.\r\n* *Gfetch*          Git fetch with arguments, dispatch when possible.\r\n* *Gadd*            Git add with arguments.\r\n* *Gstatus*         Show git status in a temporary buffer.\r\n* *Ggrep*           Git grep repo of current file, and show result in quickfix\r\n* *Gmerge*          Git merge with branch complete\r\n\r\nThose commands have reasonable complete setting, use `` to complete\r\ncommands.\r\n\r\nSee more information at doc\/easygit.txt\r\n\r\n## Feedback\r\n\r\nFeel free to let me know if you have any problem with this script at https:\/\/github.com\/chemzqm\/vim-easygit\/issues","4":"Easygit  is hosted at github: https:\/\/github.com\/chemzqm\/vim-easygit\r\n\r\nIt's git wrapper plugin made to replace [fugitive](https:\/\/github.com\/tpope\/vim-fugitive),\r\nit can be used together with fugitive as commands are disabled by default.\r\n\r\nEasygit tried to introduce cleaner code and behaviour more friendly to user.\r\n\r\n## NOTICE\r\n\r\nSome command use command line utilities, they possibly not works on windows.\r\n\r\n## PHILOSOPHY\r\n\r\nEasygit tris hard to works well 80% of daily usage git commands while avoid\r\noverhead complexity.\r\n\r\n\t* All commands work on the git repository of current file, not current\r\n\tCWD!!  This could be a life saving if you switch the file of different\r\n\trepo a lot, to make the command behaviour reasonable, you can set\r\n\t|g:easygit_auto_lcd| to 1.\r\n\r\n\t* Commands would always available, just set |g:easygit_enable_command|\r\n\tto 1\r\n\r\n\t* No useless messages any more, no press any key to continue\r\n\r\n\t* No wait, dispatch remote commands to shell if  |vim-dispatch| or\r\n\t|vim-iterm-start| available\r\n\t\r\n\t* Expose autoload functions, could be used anywhere.\r\n\t\r\n\t* Well designed default options, works out of box.\r\n\r\n\t* Friendly to other plugins, commands are disabled by default to avoid\r\n\tconflict, |buftype| are set to nofile and |bufhidden| are set to\r\n\tdelete for the temporary buffers.\r\n\r\n\t* Enhanced gitlog support, implemented in a separate plugin\r\n\thttps:\/\/github.com\/chemzqm\/unite-git-log, which make uses the power of\r\n\t|unite.vim|\r\n\r\n## COMMANDS\r\n\r\nCommands are disabled by default to make it works with fugitive by default, , you have to add\r\n\r\n    let g:easygit_enable_command = 1\r\n\r\nto your `.vimrc`, no further action required.\r\n\r\n* *Gcd*             make vim cd to git root directory.\r\n* *Glcd*            make vim lcd to git root directory.\r\n* *Gblame*          Git blame current file, you can use `p` to preview commit and `d`\r\nto diff with current file.\r\n* *GcommitCurrent*  Git commit current file with message as command args.\r\n* *GdiffThis*       Side by side diff of current file with head or any ref.\r\n* *Gcommit*         Git commit with command line argument.\r\n* *Gedit*           Edit git reference from git show.\r\n* *Gdiff*           Git diff with command line argument.\r\n* *Gremove*         Git remove with command line argument, remove current file\r\nwhen arguments empty.\r\n* *Grename*         Rename current by git mv, file in buffer list would react the changes.\r\n* *Gmove*           Git mv with command line argument.\r\n* *Gcheckout*       Git checkout with command line argument.\r\n* *Gpush*           Git push with arguments, dispatch when possible.\r\n* *Gpull*           Git pull with arguments, dispatch when possible.\r\n* *Gfetch*          Git fetch with arguments, dispatch when possible.\r\n* *Gadd*            Git add with arguments.\r\n* *Gstatus*         Show git status in a temporary buffer.\r\n* *Ggrep*           Git grep repo of current file, and show result in quickfix\r\n* *Gmerge*          Git merge with branch complete\r\n\r\nThose commands have reasonable complete setting, use `` to complete\r\ncommands.\r\n\r\nSee more information at doc\/easygit.txt\r\n\r\n## Feedback\r\n\r\nFeel free to let me know if you have any problem with this script at https:\/\/github.com\/chemzqm\/vim-easygit\/issues","install_details":"Install with your favorite plugin managers like NeoBundle\/Plugin\/Plug is prefered\r\n\r\n\tNeoBundle \\\\\\'chemzqm\/easygit\\\\\\'\r\n\tPlugin \\\\\\'chemzqm\/easygit\\\\\\'\r\n\tPlug \\\\\\'chemzqm\/easygit\\\\\\'","5":"Install with your favorite plugin managers like NeoBundle\/Plugin\/Plug is prefered\r\n\r\n\tNeoBundle \\\\\\'chemzqm\/easygit\\\\\\'\r\n\tPlugin \\\\\\'chemzqm\/easygit\\\\\\'\r\n\tPlug \\\\\\'chemzqm\/easygit\\\\\\'","first_name":"qiming","6":"qiming","last_name":"zhao","7":"zhao","releases":[{"0":"5304","vim_version":"7.0","1":"7.0","script_version":"0.3.0","2":"0.3.0","version_comment":"Initial upload","3":"Initial upload","package":"easygit.zip","4":"easygit.zip","src_id":"23881","5":"23881","creation_date":"1452257237","6":"1452257237"}]},"5303":{"script_id":"5303","0":"5303","script_name":"vim-NotableFt","1":"vim-NotableFt","script_type":"utility","2":"utility","summary":"Changes 'f' and 't' to only match notable characters","3":"Changes 'f' and 't' to only match notable characters","description":"For the most up to date version see this github page:\r\n\r\nhttps:\/\/github.com\/svermeulen\/vim-NotableFt\r\n\r\nThis plugin changes the behaviour of the `f`, `F`, `t`, `T`, `;` and `,` commands to only match on characters that are considered 'notable'. This includes:\r\n- The 'humps' of camel case words\r\n- The beginning and end of words\r\n- Any non-word characters like `. , : ( !`\r\n\r\nNote that these rules only apply when the given search character is lower case.  This is because while this behaviour is what you want almost all the time, sometimes you still want to be able to search for characters that are not 'notable'.  You can do this using upper case search.\r\n\r\nFor example, given this line:\r\n\r\n`this is a test line`\r\n\r\nWith your cursor at the beginning, if you search `fi`, your cursor will move to the word 'is' (^ represents cursor)\r\n\r\n`this ^s a test line`\r\n\r\nWhereas, if you search `fI` instead, your cursor will move to:\r\n\r\n`th^s is a test line`\r\n\r\nThis plugin also adds the following behaviour:\r\n- Multiline - Can search across multiple lines or continue searching across multiple lines using `;` and `,` keys\r\n- Highlighting - Highlights all matching characters on current line, previous matching line, and next matching line\r\n- Allows repeating `t` and `T` commands using `;` or `,` commands\r\n\r\nIt's also worth noting that it only adds the new position to the jumplist if you've changed lines\r\n\r\n###Search Direction###\r\n\r\nBy default, NotableFt will preserve Vim's behaviour of searching left-to-right with `;` after using `f`, and searching right-to-left with `;` when using `t`.  However, it also includes an alternative approach, which uses fixed directions for the `;` and `,` keys.  So if that's something you want to use instead, you can enable it by including the following in your .vimrc:\r\n\r\n    let g:NotableFtUseFixedDirection = 1\r\n\r\nIn other words, when this option is enabled, the `;` key will always go left-to-right, and the `,` key will always go right-to-left.\r\n\r\n###Key Customization###\r\n\r\nIf you have remapped any of the `f`\/`F`\/`t`\/`T`\/`;`\/`,` keys you can still use the plugin without changing it, by including the following in your .vimrc:\r\n\r\n`let g:NotableFtUseDefaults = 0`\r\n\r\nWith this set, NotableFT will not remap anything.  You can then remap whatever keys you want to the following `NotableFt` mappings:\r\n\r\n    NotableFtRepeatSearchForward\r\n    NotableFtRepeatSearchBackward\r\n    NotableFtSearchFForward\r\n    NotableFtSearchFBackward\r\n    NotableFtSearchTForward\r\n    NotableFtSearchTBackward\r\n\r\nSee the file `NotableFt.vim` for an example of how to map to these.\r\n\r\n","4":"For the most up to date version see this github page:\r\n\r\nhttps:\/\/github.com\/svermeulen\/vim-NotableFt\r\n\r\nThis plugin changes the behaviour of the `f`, `F`, `t`, `T`, `;` and `,` commands to only match on characters that are considered 'notable'. This includes:\r\n- The 'humps' of camel case words\r\n- The beginning and end of words\r\n- Any non-word characters like `. , : ( !`\r\n\r\nNote that these rules only apply when the given search character is lower case.  This is because while this behaviour is what you want almost all the time, sometimes you still want to be able to search for characters that are not 'notable'.  You can do this using upper case search.\r\n\r\nFor example, given this line:\r\n\r\n`this is a test line`\r\n\r\nWith your cursor at the beginning, if you search `fi`, your cursor will move to the word 'is' (^ represents cursor)\r\n\r\n`this ^s a test line`\r\n\r\nWhereas, if you search `fI` instead, your cursor will move to:\r\n\r\n`th^s is a test line`\r\n\r\nThis plugin also adds the following behaviour:\r\n- Multiline - Can search across multiple lines or continue searching across multiple lines using `;` and `,` keys\r\n- Highlighting - Highlights all matching characters on current line, previous matching line, and next matching line\r\n- Allows repeating `t` and `T` commands using `;` or `,` commands\r\n\r\nIt's also worth noting that it only adds the new position to the jumplist if you've changed lines\r\n\r\n###Search Direction###\r\n\r\nBy default, NotableFt will preserve Vim's behaviour of searching left-to-right with `;` after using `f`, and searching right-to-left with `;` when using `t`.  However, it also includes an alternative approach, which uses fixed directions for the `;` and `,` keys.  So if that's something you want to use instead, you can enable it by including the following in your .vimrc:\r\n\r\n    let g:NotableFtUseFixedDirection = 1\r\n\r\nIn other words, when this option is enabled, the `;` key will always go left-to-right, and the `,` key will always go right-to-left.\r\n\r\n###Key Customization###\r\n\r\nIf you have remapped any of the `f`\/`F`\/`t`\/`T`\/`;`\/`,` keys you can still use the plugin without changing it, by including the following in your .vimrc:\r\n\r\n`let g:NotableFtUseDefaults = 0`\r\n\r\nWith this set, NotableFT will not remap anything.  You can then remap whatever keys you want to the following `NotableFt` mappings:\r\n\r\n    NotableFtRepeatSearchForward\r\n    NotableFtRepeatSearchBackward\r\n    NotableFtSearchFForward\r\n    NotableFtSearchFBackward\r\n    NotableFtSearchTForward\r\n    NotableFtSearchTBackward\r\n\r\nSee the file `NotableFt.vim` for an example of how to map to these.\r\n\r\n","install_details":"","5":"","first_name":"Steve","6":"Steve","last_name":"Vermeulen","7":"Vermeulen","releases":[{"0":"5303","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"vim-NotableFt-1.0.zip","4":"vim-NotableFt-1.0.zip","src_id":"23878","5":"23878","creation_date":"1452205924","6":"1452205924"}]},"5302":{"script_id":"5302","0":"5302","script_name":"oldfilesearch.vim","1":"oldfilesearch.vim","script_type":"utility","2":"utility","summary":"search the :oldfiles list and edit one file","3":"search the :oldfiles list and edit one file","description":"Add :OldFileSearch command for searching the :oldfiles list\r\nand editing one file.\r\n\r\nExamples\r\n\r\n\" Select old files that contain vimrc in their name:\r\n\r\n:OldFileSearch vimrc\r\n\r\n\" Select oldfiles that contain both \"ftpl\" and \"python.vim\" in their\r\n\" full path.  This should match ~\/.vim\/ftplugin\/python.vim if present\r\n\" in :oldfiles.\r\n\r\n:OldFileSearch ftpl python.vim\r\n","4":"Add :OldFileSearch command for searching the :oldfiles list\r\nand editing one file.\r\n\r\nExamples\r\n\r\n\" Select old files that contain vimrc in their name:\r\n\r\n:OldFileSearch vimrc\r\n\r\n\" Select oldfiles that contain both \"ftpl\" and \"python.vim\" in their\r\n\" full path.  This should match ~\/.vim\/ftplugin\/python.vim if present\r\n\" in :oldfiles.\r\n\r\n:OldFileSearch ftpl python.vim\r\n","install_details":"Expand the archive in the ~\/.vim directory \r\n\r\ntar xzf oldfilesearch-1.0.tar.gz -C ~\/.vim\/ \r\n\r\nOr if you use pathogen.vim add the oldfilesearch.vim repository\r\nto your bundles: \r\n\r\ncd ~\/.vim\/bundle \r\ngit clone https:\/\/github.com\/pavoljuhas\/oldfilesearch.vim \r\n","5":"Expand the archive in the ~\/.vim directory \r\n\r\ntar xzf oldfilesearch-1.0.tar.gz -C ~\/.vim\/ \r\n\r\nOr if you use pathogen.vim add the oldfilesearch.vim repository\r\nto your bundles: \r\n\r\ncd ~\/.vim\/bundle \r\ngit clone https:\/\/github.com\/pavoljuhas\/oldfilesearch.vim \r\n","first_name":"Pavol","6":"Pavol","last_name":"Juhas","7":"Juhas","releases":[{"0":"5302","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"oldfilesearch-1.0.tar.gz","4":"oldfilesearch-1.0.tar.gz","src_id":"23872","5":"23872","creation_date":"1452010046","6":"1452010046"}]},"5301":{"script_id":"5301","0":"5301","script_name":"Base2Tone","1":"Base2Tone","script_type":"color scheme","2":"color scheme","summary":"Base2Tone themes use only 2 hues, this leads to a more calm color scheme","3":"Base2Tone themes use only 2 hues, this leads to a more calm color scheme","description":"This is one of six colorschemes that are based on DuoTone themes by Simurai for Atom, http:\/\/simurai.com\/projects\/2016\/01\/01\/duotone-themes\/ converted with the help of Base16-builder. \r\n\r\nDuoTone themes use only 2 hues, this leads to a more calm color scheme, but still lets you find the stuff you're looking for.   \r\n\r\nOne can find the demopage for these colorschemes at: \r\nhttp:\/\/base2t.one\/\r\n\r\nDownloads at the GitHub repo: \r\nhttps:\/\/github.com\/atelierbram\/Base2Tone-vim\r\n\r\nScreenshots: \r\nhttp:\/\/base2t.one\/assets\/img\/png\/Base2Tone-Morning-light-vim_940x640.png\r\nhttp:\/\/base2t.one\/assets\/img\/png\/Base2Tone-Evening-dark-vim_940x640.png","4":"This is one of six colorschemes that are based on DuoTone themes by Simurai for Atom, http:\/\/simurai.com\/projects\/2016\/01\/01\/duotone-themes\/ converted with the help of Base16-builder. \r\n\r\nDuoTone themes use only 2 hues, this leads to a more calm color scheme, but still lets you find the stuff you're looking for.   \r\n\r\nOne can find the demopage for these colorschemes at: \r\nhttp:\/\/base2t.one\/\r\n\r\nDownloads at the GitHub repo: \r\nhttps:\/\/github.com\/atelierbram\/Base2Tone-vim\r\n\r\nScreenshots: \r\nhttp:\/\/base2t.one\/assets\/img\/png\/Base2Tone-Morning-light-vim_940x640.png\r\nhttp:\/\/base2t.one\/assets\/img\/png\/Base2Tone-Evening-dark-vim_940x640.png","install_details":"Install in ~\/.vim\/colors, or ~\\vimfiles\\colors on Windows. \r\n\r\nor \r\n\r\nPathogen installation (recommended) \r\n\r\n1.  Download and install Tim Pope's Pathogen: https:\/\/github.com\/tpope\/vim-pathogen \r\n2. download or clone this repo on Github: https:\/\/github.com\/atelierbram\/Base2Tone-vim \r\n3.  Next, move or clone the `Base2Tone-vim` directory so that it is \r\na subdirectory of the `.vim\/bundle` directory. \r\n\r\n$ cd ~\/.vim\/bundle \r\n$ git clone https:\/\/github.com\/atelierbram\/Base2Tone-vim.git \r\n\r\nTry it out with \r\nsyntax enable\r\nset background=dark\r\n\" Base2Tone Dark\r\ncolorscheme Base2Tone_EveningDark\r\n\" or any of the other schemes:\r\n\" colorscheme Base2Tone_MorningDark\r\n\" colorscheme Base2Tone_SeaDark\r\n\" colorscheme Base2Tone_SpaceDark\r\n\" colorscheme Base2Tone_EarthDark\r\n\" colorscheme Base2Tone_ForestDark\r\n\" colorscheme Base2Tone_DesertDark\r\n\" colorscheme Base2Tone_LakeDark\r\n\" colorscheme Base2Tone_MeadowDark\r\n\" colorscheme Base2Tone_DrawbridgeDark\r\n\" colorscheme Base2Tone_PoolDark\r\n\" colorscheme Base2Tone_HeathDark\r\n\" colorscheme Base2Tone_CaveDark\r\n\r\n\" Base2Tone Light\r\n\" set background=light\r\n\" colorscheme Base2Tone_EveningLight\r\n\" colorscheme Base2Tone_MorningLight\r\n\" colorscheme Base2Tone_SeaLight\r\n\" colorscheme Base2Tone_SpaceLight\r\n\" colorscheme Base2Tone_EarthLight\r\n\" colorscheme Base2Tone_ForestLight\r\n\" colorscheme Base2Tone_DesertLight\r\n\" colorscheme Base2Tone_LakeLight\r\n\" colorscheme Base2Tone_MeadowLight\r\n\" colorscheme Base2Tone_DrawbridgeLight\r\n\" colorscheme Base2Tone_PoolLight\r\n\" colorscheme Base2Tone_HeathLight\r\n\" colorscheme Base2Tone_CaveLight\r\n\r\nIf you want to make it the default, add that command to your vimrc or gvimrc.","5":"Install in ~\/.vim\/colors, or ~\\vimfiles\\colors on Windows. \r\n\r\nor \r\n\r\nPathogen installation (recommended) \r\n\r\n1.  Download and install Tim Pope's Pathogen: https:\/\/github.com\/tpope\/vim-pathogen \r\n2. download or clone this repo on Github: https:\/\/github.com\/atelierbram\/Base2Tone-vim \r\n3.  Next, move or clone the `Base2Tone-vim` directory so that it is \r\na subdirectory of the `.vim\/bundle` directory. \r\n\r\n$ cd ~\/.vim\/bundle \r\n$ git clone https:\/\/github.com\/atelierbram\/Base2Tone-vim.git \r\n\r\nTry it out with \r\nsyntax enable\r\nset background=dark\r\n\" Base2Tone Dark\r\ncolorscheme Base2Tone_EveningDark\r\n\" or any of the other schemes:\r\n\" colorscheme Base2Tone_MorningDark\r\n\" colorscheme Base2Tone_SeaDark\r\n\" colorscheme Base2Tone_SpaceDark\r\n\" colorscheme Base2Tone_EarthDark\r\n\" colorscheme Base2Tone_ForestDark\r\n\" colorscheme Base2Tone_DesertDark\r\n\" colorscheme Base2Tone_LakeDark\r\n\" colorscheme Base2Tone_MeadowDark\r\n\" colorscheme Base2Tone_DrawbridgeDark\r\n\" colorscheme Base2Tone_PoolDark\r\n\" colorscheme Base2Tone_HeathDark\r\n\" colorscheme Base2Tone_CaveDark\r\n\r\n\" Base2Tone Light\r\n\" set background=light\r\n\" colorscheme Base2Tone_EveningLight\r\n\" colorscheme Base2Tone_MorningLight\r\n\" colorscheme Base2Tone_SeaLight\r\n\" colorscheme Base2Tone_SpaceLight\r\n\" colorscheme Base2Tone_EarthLight\r\n\" colorscheme Base2Tone_ForestLight\r\n\" colorscheme Base2Tone_DesertLight\r\n\" colorscheme Base2Tone_LakeLight\r\n\" colorscheme Base2Tone_MeadowLight\r\n\" colorscheme Base2Tone_DrawbridgeLight\r\n\" colorscheme Base2Tone_PoolLight\r\n\" colorscheme Base2Tone_HeathLight\r\n\" colorscheme Base2Tone_CaveLight\r\n\r\nIf you want to make it the default, add that command to your vimrc or gvimrc.","first_name":"Bram","6":"Bram","last_name":"de Haan","7":"de Haan","releases":[{"0":"5301","vim_version":"7.0","1":"7.0","script_version":"1.6","2":"1.6","version_comment":"Changed comment on top to point to the repository on Github - some added highlighting for PHP Ruby e.o. , cleaned up some deprecated outcommented code","3":"Changed comment on top to point to the repository on Github - some added highlighting for PHP Ruby e.o. , cleaned up some deprecated outcommented code","package":"Base2Tone_EveningDark.vim","4":"Base2Tone_EveningDark.vim","src_id":"25475","5":"25475","creation_date":"1501761564","6":"1501761564"},{"0":"5301","vim_version":"7.0","1":"7.0","script_version":"1.5","2":"1.5","version_comment":"renaming","3":"renaming","package":"Base2Tone-Evening-dark.vim","4":"Base2Tone-Evening-dark.vim","src_id":"24412","5":"24412","creation_date":"1469798553","6":"1469798553"},{"0":"5301","vim_version":"7.0","1":"7.0","script_version":"1.4","2":"1.4","version_comment":"better contrast","3":"better contrast","package":"duotone-dark.vim","4":"duotone-dark.vim","src_id":"24011","5":"24011","creation_date":"1455530747","6":"1455530747"}]},"5300":{"script_id":"5300","0":"5300","script_name":"Ranger.vim","1":"Ranger.vim","script_type":"utility","2":"utility","summary":"Ranger for vim.","3":"Ranger for vim.","description":"(latest version at https:\/\/github.com\/rafaqz\/ranger.vim)\r\n\r\n\r\nRanger is a scriptable terminal file manager with vim like commands that displays files as you browse (even images).\r\n\r\nhttp:\/\/ranger.nongnu.org\/\r\n\r\nTo browse and open file(s) with ranger:\r\n\r\nrr\r\n\r\nOpen files(s) with ranger in tabs, splits and vertical splits. Each file selected gets a new tab\/split.\r\n\r\nrt\r\nrs\r\nrv\r\n\r\nUse ranger as an operator, to add\/edit a file path under the cursor:\r\n\r\nr[movement]\r\n\r\nThis example will replace the text inside () with whatever file path you select in ranger. If it's already a valid path ranger will open there:\r\n\r\nri( \r\n\r\nranger.vim wont work in gvim, but if you're using ranger, you probably don't use gvim anyway...","4":"(latest version at https:\/\/github.com\/rafaqz\/ranger.vim)\r\n\r\n\r\nRanger is a scriptable terminal file manager with vim like commands that displays files as you browse (even images).\r\n\r\nhttp:\/\/ranger.nongnu.org\/\r\n\r\nTo browse and open file(s) with ranger:\r\n\r\nrr\r\n\r\nOpen files(s) with ranger in tabs, splits and vertical splits. Each file selected gets a new tab\/split.\r\n\r\nrt\r\nrs\r\nrv\r\n\r\nUse ranger as an operator, to add\/edit a file path under the cursor:\r\n\r\nr[movement]\r\n\r\nThis example will replace the text inside () with whatever file path you select in ranger. If it's already a valid path ranger will open there:\r\n\r\nri( \r\n\r\nranger.vim wont work in gvim, but if you're using ranger, you probably don't use gvim anyway...","install_details":"","5":"","first_name":"rafaqz","6":"rafaqz","last_name":"rafaqz","7":"rafaqz","releases":[{"0":"5300","vim_version":"7.3","1":"7.3","script_version":"1.0","2":"1.0","version_comment":"Bugfixes","3":"Bugfixes","package":"ranger.vim.tar.gz","4":"ranger.vim.tar.gz","src_id":"23894","5":"23894","creation_date":"1452653581","6":"1452653581"}]},"5299":{"script_id":"5299","0":"5299","script_name":"Citation.vim","1":"Citation.vim","script_type":"utility","2":"utility","summary":"Insert citations from zotero or bibtex files.","3":"Insert citations from zotero or bibtex files.","description":"A citation source for unite.vim\r\n\r\n(latest versions are at https:\/\/github.com\/rafaqz\/citation.vim)\r\n\r\nCitation.vim Imports zotero databases or exported bibtex files, \r\nand does almost whatever you want with their fields using Unite.vim.\r\n","4":"A citation source for unite.vim\r\n\r\n(latest versions are at https:\/\/github.com\/rafaqz\/citation.vim)\r\n\r\nCitation.vim Imports zotero databases or exported bibtex files, \r\nand does almost whatever you want with their fields using Unite.vim.\r\n","install_details":"Install unite.vim (https:\/\/github.com\/Shougo\/unite.vim)\r\nInstall this plugin in vim however you like to do that.\r\n\r\nCheck the readme or github for up to date installation","5":"Install unite.vim (https:\/\/github.com\/Shougo\/unite.vim)\r\nInstall this plugin in vim however you like to do that.\r\n\r\nCheck the readme or github for up to date installation","first_name":"rafaqz","6":"rafaqz","last_name":"rafaqz","7":"rafaqz","releases":[{"0":"5299","vim_version":"7.3","1":"7.3","script_version":"0.4","2":"0.4","version_comment":"-","3":"-","package":"citation.vim.tar.gz","4":"citation.vim.tar.gz","src_id":"24988","5":"24988","creation_date":"1487725038","6":"1487725038"},{"0":"5299","vim_version":"7.3","1":"7.3","script_version":"0.3","2":"0.3","version_comment":"-","3":"-","package":"citation.vim.tar.gz","4":"citation.vim.tar.gz","src_id":"24987","5":"24987","creation_date":"1487720039","6":"1487720039"}]},"5298":{"script_id":"5298","0":"5298","script_name":"vim-love-docs","1":"vim-love-docs","script_type":"syntax","2":"syntax","summary":"Highlighting and help file for the LOVE framework","3":"Highlighting and help file for the LOVE framework","description":"Syntax highlighting for LOVE (http:\/\/love2d.org) commands. \r\nYou can auto-generate it yourself from this repo: https:\/\/github.com\/davisdude\/vim-love-docs or download the latest release here, or at https:\/\/github.com\/davisdude\/vim-love-docs\/releases\/","4":"Syntax highlighting for LOVE (http:\/\/love2d.org) commands. \r\nYou can auto-generate it yourself from this repo: https:\/\/github.com\/davisdude\/vim-love-docs or download the latest release here, or at https:\/\/github.com\/davisdude\/vim-love-docs\/releases\/","install_details":"Unpack the zip and place the files in their corresponding folders, based on the structure of the zip","5":"Unpack the zip and place the files in their corresponding folders, based on the structure of the zip","first_name":"Davis","6":"Davis","last_name":"Claiborne","7":"Claiborne","releases":[{"0":"5298","vim_version":"7.0","1":"7.0","script_version":"0.7.0","2":"0.7.0","version_comment":"0.7 with plugin\/love.vim","3":"0.7 with plugin\/love.vim","package":"vim-love-docs.tar.gz","4":"vim-love-docs.tar.gz","src_id":"28574","5":"28574","creation_date":"1699125880","6":"1699125880"},{"0":"5298","vim_version":"7.0","1":"7.0","script_version":"0.7.0","2":"0.7.0","version_comment":"Made love and lua types jumpable. To jump to lua types, install the luarefvim plugin.","3":"Made love and lua types jumpable. To jump to lua types, install the luarefvim plugin.","package":"vim-love-docs.tar.gz","4":"vim-love-docs.tar.gz","src_id":"27271","5":"27271","creation_date":"1596842388","6":"1596842388"},{"0":"5298","vim_version":"7.0","1":"7.0","script_version":"0.6.1","2":"0.6.1","version_comment":"Fixed issue with love.conf not being highlighted properly with the syntax `love.conf = function() ...`","3":"Fixed issue with love.conf not being highlighted properly with the syntax `love.conf = function() ...`","package":"vim-love-docs.zip","4":"vim-love-docs.zip","src_id":"25641","5":"25641","creation_date":"1510379353","6":"1510379353"},{"0":"5298","vim_version":"7.0","1":"7.0","script_version":"0.6.0","2":"0.6.0","version_comment":"Major overhaul of doc generation","3":"Major overhaul of doc generation","package":"vim-love-docs.zip","4":"vim-love-docs.zip","src_id":"25640","5":"25640","creation_date":"1510377650","6":"1510377650"},{"0":"5298","vim_version":"7.0","1":"7.0","script_version":"0.5.3","2":"0.5.3","version_comment":"Changed line wrapping from 79 (for whatever reason) to 80\r\nFixed URL in the about section (love-about)\r\nChanged License to MIT","3":"Changed line wrapping from 79 (for whatever reason) to 80\r\nFixed URL in the about section (love-about)\r\nChanged License to MIT","package":"vim-love-docs.zip","4":"vim-love-docs.zip","src_id":"25449","5":"25449","creation_date":"1501124179","6":"1501124179"},{"0":"5298","vim_version":"7.0","1":"7.0","script_version":"0.5.2","2":"0.5.2","version_comment":"Keep love commands from being highlighted in comments, added tag *love2d*","3":"Keep love commands from being highlighted in comments, added tag *love2d*","package":"vim-love-docs.zip","4":"vim-love-docs.zip","src_id":"25054","5":"25054","creation_date":"1490792853","6":"1490792853"},{"0":"5298","vim_version":"7.0","1":"7.0","script_version":"0.5.1","2":"0.5.1","version_comment":"Fixed highlighting to work with plugins such as vim-lua","3":"Fixed highlighting to work with plugins such as vim-lua","package":"vim-love-docs.zip","4":"vim-love-docs.zip","src_id":"25049","5":"25049","creation_date":"1490637500","6":"1490637500"},{"0":"5298","vim_version":"7.0","1":"7.0","script_version":"0.5.0","2":"0.5.0","version_comment":"Changed formatting; fixed highlighting error","3":"Changed formatting; fixed highlighting error","package":"vim-love-docs.zip","4":"vim-love-docs.zip","src_id":"24775","5":"24775","creation_date":"1480604132","6":"1480604132"},{"0":"5298","vim_version":"7.0","1":"7.0","script_version":"0.4.1","2":"0.4.1","version_comment":"Updated formatting for help file, improved string matching","3":"Updated formatting for help file, improved string matching","package":"vim-love-docs.zip","4":"vim-love-docs.zip","src_id":"24158","5":"24158","creation_date":"1459906248","6":"1459906248"},{"0":"5298","vim_version":"7.0","1":"7.0","script_version":"0.4.0","2":"0.4.0","version_comment":"Added help file","3":"Added help file","package":"master[1].zip","4":"master[1].zip","src_id":"24079","5":"24079","creation_date":"1457493194","6":"1457493194"},{"0":"5298","vim_version":"7.0","1":"7.0","script_version":"0.3.0","2":"0.3.0","version_comment":"Updated to LOVE 0.10.1","3":"Updated to LOVE 0.10.1","package":"lua.vim","4":"lua.vim","src_id":"24034","5":"24034","creation_date":"1456170332","6":"1456170332"},{"0":"5298","vim_version":"7.0","1":"7.0","script_version":"0.2.0","2":"0.2.0","version_comment":"Added highlighting for love.conf","3":"Added highlighting for love.conf","package":"lua.vim","4":"lua.vim","src_id":"23941","5":"23941","creation_date":"1453564092","6":"1453564092"},{"0":"5298","vim_version":"7.0","1":"7.0","script_version":"0.1.1","2":"0.1.1","version_comment":"Improved highlighting","3":"Improved highlighting","package":"lua.vim","4":"lua.vim","src_id":"23874","5":"23874","creation_date":"1452039173","6":"1452039173"},{"0":"5298","vim_version":"7.0","1":"7.0","script_version":"0.1.0","2":"0.1.0","version_comment":"Improved speed and highlighting","3":"Improved speed and highlighting","package":"lua.vim","4":"lua.vim","src_id":"23873","5":"23873","creation_date":"1452032086","6":"1452032086"},{"0":"5298","vim_version":"7.0","1":"7.0","script_version":"0.0.1","2":"0.0.1","version_comment":"Initial upload","3":"Initial upload","package":"lua.vim","4":"lua.vim","src_id":"23861","5":"23861","creation_date":"1451829476","6":"1451829476"}]},"5297":{"script_id":"5297","0":"5297","script_name":"iterm-start","1":"iterm-start","script_type":"utility","2":"utility","summary":"Dispatch a task for iTerm2 in MacVim, used for async command line task","3":"Dispatch a task for iTerm2 in MacVim, used for async command line task","description":"This project is hosted at https:\/\/github.com\/chemzqm\/vim-iterm2-start\r\n\r\nIt works like dispatch, but works for the lasted iTerm2 > 2.9\r\n\r\nPrerequirement:\r\n\r\n* MacVim 7.3+\r\n* iTerm2 > 2.9 currently in beta test\r\n* fish shell (otherwise you will need change the code)\r\n* Knowledge of command line tools\r\n\r\n## Command\r\n\r\n* `[!]ItermStart [options] {command}`\r\n\r\n    Start task in current session of iTerm2, when prefix with `!`, not foucs the iTerm window\r\n\r\n    * -dir=...     run command in given directory\r\n    * -title=...   set lable for iTerm2\r\n    * -no-wait      disable the default prompt of `press enter to continue` on command error\r\n\r\n* `[!]ItermStartTab [options] {command}`\r\n\r\n    Start task in a new tab session of iTerm2, options is the same as `ItermStart` command","4":"This project is hosted at https:\/\/github.com\/chemzqm\/vim-iterm2-start\r\n\r\nIt works like dispatch, but works for the lasted iTerm2 > 2.9\r\n\r\nPrerequirement:\r\n\r\n* MacVim 7.3+\r\n* iTerm2 > 2.9 currently in beta test\r\n* fish shell (otherwise you will need change the code)\r\n* Knowledge of command line tools\r\n\r\n## Command\r\n\r\n* `[!]ItermStart [options] {command}`\r\n\r\n    Start task in current session of iTerm2, when prefix with `!`, not foucs the iTerm window\r\n\r\n    * -dir=...     run command in given directory\r\n    * -title=...   set lable for iTerm2\r\n    * -no-wait      disable the default prompt of `press enter to continue` on command error\r\n\r\n* `[!]ItermStartTab [options] {command}`\r\n\r\n    Start task in a new tab session of iTerm2, options is the same as `ItermStart` command","install_details":"Install with your favorite plugin managers like NeoBundle\/Plugin\/Plug\r\n\r\n\tNeoBundle 'chemzqm\/vim-iterm2-start'\r\n\tPlugin 'chemzqm\/vim-iterm2-start'\r\n\tPlug 'chemzqm\/vim-iterm2-start'","5":"Install with your favorite plugin managers like NeoBundle\/Plugin\/Plug\r\n\r\n\tNeoBundle 'chemzqm\/vim-iterm2-start'\r\n\tPlugin 'chemzqm\/vim-iterm2-start'\r\n\tPlug 'chemzqm\/vim-iterm2-start'","first_name":"qiming","6":"qiming","last_name":"zhao","7":"zhao","releases":[{"0":"5297","vim_version":"7.0","1":"7.0","script_version":"0.2.0","2":"0.2.0","version_comment":"add notification for success command using terminal-notifier or growlnotify","3":"add notification for success command using terminal-notifier or growlnotify","package":"iterm-start.zip","4":"iterm-start.zip","src_id":"23880","5":"23880","creation_date":"1452256544","6":"1452256544"},{"0":"5297","vim_version":"7.0","1":"7.0","script_version":"0.1.0","2":"0.1.0","version_comment":"Initial upload","3":"Initial upload","package":"iterm-start.zip","4":"iterm-start.zip","src_id":"23858","5":"23858","creation_date":"1451787771","6":"1451787771"}]},"5296":{"script_id":"5296","0":"5296","script_name":"vim-run","1":"vim-run","script_type":"utility","2":"utility","summary":"Run command in vim with current buffer and see the result side-by-side","3":"Run command in vim with current buffer and see the result side-by-side","description":"The project is hosted at github: https:\/\/github.com\/chemzqm\/vim-run\r\n\r\n## Usage\r\n\r\nConfig the command by filetype:\r\n\r\n``` vim\r\nlet g:vim_run_command_map = {\r\n  \\\\\\'javascript\\': \\'node\\',\r\n  \\\\\\'php\\': \\'php\\',\r\n  \\\\\\'python\\': \\'python\\',\r\n  \\\\}\r\n```\r\n\r\nRun command with:\r\n\r\n``` vim\r\n:Run\r\n```\r\n\r\nOr you can specify the command after `Run`:\r\n\r\n``` vim\r\n:Run yourcommand\r\n```\r\n\r\n`yourcommand` will be used in the following `Run` and `Autorun` if they called with empty command argument\r\n\r\nRun command with range:\r\n\r\n``` vim\r\n:1,10Run\r\n```\r\n\r\nRun command with visual select:\r\n\r\n``` vim\r\n:\\'<,\\'>RunRange\r\n```\r\n\r\nToggle command autorun on save of current file:\r\n\r\n``` vim\r\n:AutoRun\r\n```\r\n","4":"The project is hosted at github: https:\/\/github.com\/chemzqm\/vim-run\r\n\r\n## Usage\r\n\r\nConfig the command by filetype:\r\n\r\n``` vim\r\nlet g:vim_run_command_map = {\r\n  \\\\\\'javascript\\': \\'node\\',\r\n  \\\\\\'php\\': \\'php\\',\r\n  \\\\\\'python\\': \\'python\\',\r\n  \\\\}\r\n```\r\n\r\nRun command with:\r\n\r\n``` vim\r\n:Run\r\n```\r\n\r\nOr you can specify the command after `Run`:\r\n\r\n``` vim\r\n:Run yourcommand\r\n```\r\n\r\n`yourcommand` will be used in the following `Run` and `Autorun` if they called with empty command argument\r\n\r\nRun command with range:\r\n\r\n``` vim\r\n:1,10Run\r\n```\r\n\r\nRun command with visual select:\r\n\r\n``` vim\r\n:\\'<,\\'>RunRange\r\n```\r\n\r\nToggle command autorun on save of current file:\r\n\r\n``` vim\r\n:AutoRun\r\n```\r\n","install_details":"Install with your favorite plugin managers like NeoBundle\/Plugin\/Plug\r\n>\r\n\tNeoBundle \\'chemzqm\/vim-run\\'\r\n\tPlugin \\'chemzqm\/vim-run\\'\r\n\tPlug \\'chemzqm\/vim-run\\'","5":"Install with your favorite plugin managers like NeoBundle\/Plugin\/Plug\r\n>\r\n\tNeoBundle \\'chemzqm\/vim-run\\'\r\n\tPlugin \\'chemzqm\/vim-run\\'\r\n\tPlug \\'chemzqm\/vim-run\\'","first_name":"qiming","6":"qiming","last_name":"zhao","7":"zhao","releases":[{"0":"5296","vim_version":"7.0","1":"7.0","script_version":"0.1.0","2":"0.1.0","version_comment":"Initial upload","3":"Initial upload","package":"vim-run.zip","4":"vim-run.zip","src_id":"23857","5":"23857","creation_date":"1451771457","6":"1451771457"}]},"5295":{"script_id":"5295","0":"5295","script_name":"csscomplete.vim","1":"csscomplete.vim","script_type":"ftplugin","2":"ftplugin","summary":"CSS omni complete function","3":"CSS omni complete function","description":"Update the bult-in CSS complete function to latest CSS standard.\r\n\r\nGitHub repo: https:\/\/github.com\/othree\/csscomplete.vim","4":"Update the bult-in CSS complete function to latest CSS standard.\r\n\r\nGitHub repo: https:\/\/github.com\/othree\/csscomplete.vim","install_details":"Suggest use Vundle like package manager to install.\r\nAnd assign complete function for css filetype\r\n\r\nautocmd FileType css set omnifunc=csscomplete#CompleteCSS noci","5":"Suggest use Vundle like package manager to install.\r\nAnd assign complete function for css filetype\r\n\r\nautocmd FileType css set omnifunc=csscomplete#CompleteCSS noci","first_name":"wei ko","6":"wei ko","last_name":"kao","7":"kao","releases":[{"0":"5295","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Fix at rule pattern","3":"Fix at rule pattern","package":"csscomplete.vim-0.1.vmb","4":"csscomplete.vim-0.1.vmb","src_id":"23851","5":"23851","creation_date":"1451549804","6":"1451549804"}]},"5294":{"script_id":"5294","0":"5294","script_name":"lightline","1":"lightline","script_type":"utility","2":"utility","summary":"A light and configurable statusline\/tabline for Vim","3":"A light and configurable statusline\/tabline for Vim","description":"NOTE: I don't upload code to vim.org anymore. Please clone from https:\/\/github.com\/itchyny\/lightline.vim.\r\n\r\n\r\nlightline.vim\r\n\r\nA light and configurable statusline\/tabline for Vim\r\n\r\nhttps:\/\/github.com\/itchyny\/lightline.vim\r\n","4":"NOTE: I don't upload code to vim.org anymore. Please clone from https:\/\/github.com\/itchyny\/lightline.vim.\r\n\r\n\r\nlightline.vim\r\n\r\nA light and configurable statusline\/tabline for Vim\r\n\r\nhttps:\/\/github.com\/itchyny\/lightline.vim\r\n","install_details":"","5":"","first_name":"itchyny","6":"itchyny","last_name":"\u3000","7":"　","releases":[{"0":"5294","vim_version":"7.3","1":"7.3","script_version":"0.1","2":"0.1","version_comment":"code refactoring \r\nperformance improvement \r\nadd component_function_visible_condition ","3":"code refactoring \r\nperformance improvement \r\nadd component_function_visible_condition ","package":"lightline-0.1.zip","4":"lightline-0.1.zip","src_id":"24517","5":"24517","creation_date":"1473576368","6":"1473576368"},{"0":"5294","vim_version":"7.3","1":"7.3","script_version":"0.0","2":"0.0","version_comment":"Initial upload","3":"Initial upload","package":"lightline.zip","4":"lightline.zip","src_id":"23847","5":"23847","creation_date":"1451526119","6":"1451526119"}]},"5293":{"script_id":"5293","0":"5293","script_name":"vim-operator-flashy","1":"vim-operator-flashy","script_type":"utility","2":"utility","summary":"Highlight yanked area","3":"Highlight yanked area","description":"See https:\/\/github.com\/haya14busa\/vim-operator-flashy","4":"See https:\/\/github.com\/haya14busa\/vim-operator-flashy","install_details":"","5":"","first_name":"haya14busa","6":"haya14busa","last_name":" ","7":" ","releases":[{"0":"5293","vim_version":"7.0","1":"7.0","script_version":"v0.9.0","2":"v0.9.0","version_comment":"Initial upload","3":"Initial upload","package":"vim-operator-flashy-0.9.0.zip","4":"vim-operator-flashy-0.9.0.zip","src_id":"23845","5":"23845","creation_date":"1451498079","6":"1451498079"}]},"5292":{"script_id":"5292","0":"5292","script_name":"vim-gtest","1":"vim-gtest","script_type":"utility","2":"utility","summary":"Vim plugin to quickly select and asyncronously run GoogleTest","3":"Vim plugin to quickly select and asyncronously run GoogleTest","description":"Google Test is a unit testing library for the C++ programming language. With this plugin you can:\r\n\r\n - jump between tests in the open buffer\r\n - launch test under the cursor\r\n - select a test case, with autocompletion\r\n - select a test name, with autocompletion\r\n - launch selected tests\r\n - highlight failing tests in the quickfix\r\n - fuzzy search and select tests with ctrlp\r\n - jump between test and implementation\r\n - toggle DISABLED_ in source code\r\n\r\nProject page: https:\/\/github.com\/alepez\/vim-gtest","4":"Google Test is a unit testing library for the C++ programming language. With this plugin you can:\r\n\r\n - jump between tests in the open buffer\r\n - launch test under the cursor\r\n - select a test case, with autocompletion\r\n - select a test name, with autocompletion\r\n - launch selected tests\r\n - highlight failing tests in the quickfix\r\n - fuzzy search and select tests with ctrlp\r\n - jump between test and implementation\r\n - toggle DISABLED_ in source code\r\n\r\nProject page: https:\/\/github.com\/alepez\/vim-gtest","install_details":"Extract in ~\/.vim (~\\vimfiles on Windows) or with Vundle `Plugin 'alepez\/vim-gtest'`","5":"Extract in ~\/.vim (~\\vimfiles on Windows) or with Vundle `Plugin 'alepez\/vim-gtest'`","first_name":"Alessandro","6":"Alessandro","last_name":"Pezzato","7":"Pezzato","releases":[{"0":"5292","vim_version":"7.0","1":"7.0","script_version":"1.3.1","2":"1.3.1","version_comment":"Bugfixes\r\nSource quick DISABLED_ test\r\nJump between test and implementation","3":"Bugfixes\r\nSource quick DISABLED_ test\r\nJump between test and implementation","package":"vim-gtest.zip","4":"vim-gtest.zip","src_id":"23918","5":"23918","creation_date":"1453001821","6":"1453001821"},{"0":"5292","vim_version":"7.0","1":"7.0","script_version":"1.1.0","2":"1.1.0","version_comment":"Initial upload","3":"Initial upload","package":"vim-gtest.zip","4":"vim-gtest.zip","src_id":"23842","5":"23842","creation_date":"1451436245","6":"1451436245"}]},"5291":{"script_id":"5291","0":"5291","script_name":"vim-uncommenter","1":"vim-uncommenter","script_type":"utility","2":"utility","summary":"Automatically deletes all comments in a programming source file.","3":"Automatically deletes all comments in a programming source file.","description":"UNMAINTAINED\r\n\r\nIn most programming language files opened in vim, to delete all of the lines that are comments, simply hit the keys `dc` and the comments will all disappear!\r\n\r\n------------------------------------------\r\n\r\nBefore:\r\n------------------------------------------\r\n# here is a comment\r\ndef Hello (name) # here is wierdly placed comment\r\n    puts \"\\n-------------\"\r\n    puts \"Hello, #{name}.\" # even a comment here will be removed\r\n    puts '--------------'\r\nend\r\n\r\nputs '######' # this one too, however the `#` inside the single quotes will be fine!\r\n\r\n# and here is another comment\r\n[1, 2, 3, 4, 5].each do |i| \r\n    puts \"hello\" # and another wierd one\r\nend\r\n\r\n# and here is the last comment\r\nHello(\"# Benjamin #\") # this one too\r\n\r\nAfter:\r\n------------------------------------------\r\ndef Hello (name)\r\n    puts \"\\n-------------\"\r\n    puts \"Hello, #{name}.\"\r\n    puts '--------------'\r\nend\r\n\r\nputs '######'\r\n\r\n[1, 2, 3, 4, 5].each do |i| \r\n    puts \"hello\"\r\nend\r\n\r\nHello(\"# Benjamin #\")\r\n\r\nCurrent programming languages that vim-uncommenter works with:\r\n------------------------------------------\r\n+ Ruby\r\n+ PHP\r\n+ Python\r\n+ Perl\r\n+ C\r\n+ C++\r\n+ C#\r\n+ Rust\r\n+ SASS\/SCSS\r\n+ D\r\n+ Go\r\n+ Java\r\n+ Javascript\r\n+ ActionScript\r\n+ Scala\r\n+ Pascal\r\n+ Swift\r\n+ R\r\n+ Vimscript\r\n+ Shell\r\n+ Makefile\r\n+ Cobra\r\n+ Seed7\r\n+ Powershell\r\n+ Erlang\r\n+ Text\r\n+ VBScript\r\n+ Small Basic\r\n+ AutoIt\r\n+ Lisp\r\n+ Scheme\r\n+ Rebol\r\n+ Haskell\r\n+ SQL\r\n+ Ada\r\n+ AppleScript\r\n+ Eiffel\r\n+ Lua\r\n+ VHDL","4":"UNMAINTAINED\r\n\r\nIn most programming language files opened in vim, to delete all of the lines that are comments, simply hit the keys `dc` and the comments will all disappear!\r\n\r\n------------------------------------------\r\n\r\nBefore:\r\n------------------------------------------\r\n# here is a comment\r\ndef Hello (name) # here is wierdly placed comment\r\n    puts \"\\n-------------\"\r\n    puts \"Hello, #{name}.\" # even a comment here will be removed\r\n    puts '--------------'\r\nend\r\n\r\nputs '######' # this one too, however the `#` inside the single quotes will be fine!\r\n\r\n# and here is another comment\r\n[1, 2, 3, 4, 5].each do |i| \r\n    puts \"hello\" # and another wierd one\r\nend\r\n\r\n# and here is the last comment\r\nHello(\"# Benjamin #\") # this one too\r\n\r\nAfter:\r\n------------------------------------------\r\ndef Hello (name)\r\n    puts \"\\n-------------\"\r\n    puts \"Hello, #{name}.\"\r\n    puts '--------------'\r\nend\r\n\r\nputs '######'\r\n\r\n[1, 2, 3, 4, 5].each do |i| \r\n    puts \"hello\"\r\nend\r\n\r\nHello(\"# Benjamin #\")\r\n\r\nCurrent programming languages that vim-uncommenter works with:\r\n------------------------------------------\r\n+ Ruby\r\n+ PHP\r\n+ Python\r\n+ Perl\r\n+ C\r\n+ C++\r\n+ C#\r\n+ Rust\r\n+ SASS\/SCSS\r\n+ D\r\n+ Go\r\n+ Java\r\n+ Javascript\r\n+ ActionScript\r\n+ Scala\r\n+ Pascal\r\n+ Swift\r\n+ R\r\n+ Vimscript\r\n+ Shell\r\n+ Makefile\r\n+ Cobra\r\n+ Seed7\r\n+ Powershell\r\n+ Erlang\r\n+ Text\r\n+ VBScript\r\n+ Small Basic\r\n+ AutoIt\r\n+ Lisp\r\n+ Scheme\r\n+ Rebol\r\n+ Haskell\r\n+ SQL\r\n+ Ada\r\n+ AppleScript\r\n+ Eiffel\r\n+ Lua\r\n+ VHDL","install_details":"","5":"","first_name":"Benjamin","6":"Benjamin","last_name":"Radovsky","7":"Radovsky","releases":[{"0":"5291","vim_version":"7.0","1":"7.0","script_version":"0.5","2":"0.5","version_comment":"Finished adding delete block comments functionality for most of the programming languages in the current list of languages that `vim-uncommenter` works with.","3":"Finished adding delete block comments functionality for most of the programming languages in the current list of languages that `vim-uncommenter` works with.","package":"vim-uncommenter-0.5.tar.gz","4":"vim-uncommenter-0.5.tar.gz","src_id":"23877","5":"23877","creation_date":"1452166566","6":"1452166566"}]},"5290":{"script_id":"5290","0":"5290","script_name":"partialnumber.vim","1":"partialnumber.vim","script_type":"utility","2":"utility","summary":"yet another line number option","3":"yet another line number option","description":"This plugin shows the line number partially for a specified range with an optional highlight group in the sign column.\r\n\r\nFor details and demo samples, please visit the following git repository: https:\/\/github.com\/rickhowe\/partialnumber.vim","4":"This plugin shows the line number partially for a specified range with an optional highlight group in the sign column.\r\n\r\nFor details and demo samples, please visit the following git repository: https:\/\/github.com\/rickhowe\/partialnumber.vim","install_details":"Install 'rickhowe\/partialnumber.vim' by using your plugin manager. Or manually unzip and copy all folders in your ~\/.vim or ~\/vimfiles.","5":"Install 'rickhowe\/partialnumber.vim' by using your plugin manager. Or manually unzip and copy all folders in your ~\/.vim or ~\/vimfiles.","first_name":"Rick","6":"Rick","last_name":"Howe","7":"Howe","releases":[{"0":"5290","vim_version":"8.0","1":"8.0","script_version":"2.1","2":"2.1","version_comment":"Changed to display a line number as the one placed digit or upper 2 digits.","3":"Changed to display a line number as the one placed digit or upper 2 digits.","package":"partialnumber2.1.zip","4":"partialnumber2.1.zip","src_id":"28260","5":"28260","creation_date":"1668000853","6":"1668000853"},{"0":"5290","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"partialnumber.vim","4":"partialnumber.vim","src_id":"23811","5":"23811","creation_date":"1450616509","6":"1450616509"}]},"5289":{"script_id":"5289","0":"5289","script_name":"tgf-vim","1":"tgf-vim","script_type":"utility","2":"utility","summary":"This is a PureFun-Tiger Language syntax and indent script.","3":"This is a PureFun-Tiger Language syntax and indent script.","description":"This is a PureFun-Tiger Language syntax and indent script.\r\n\r\nThe code is hosted at Github: https:\/\/github.com\/YuKill\/tgf-vim\r\n\r\nIt works with *.tgf files.","4":"This is a PureFun-Tiger Language syntax and indent script.\r\n\r\nThe code is hosted at Github: https:\/\/github.com\/YuKill\/tgf-vim\r\n\r\nIt works with *.tgf files.","install_details":"Execute the makefile.\r\n\r\nPlace at your .vimrc:\r\nau BufRead,BufNewFile *.tgf set filetype=tgf","5":"Execute the makefile.\r\n\r\nPlace at your .vimrc:\r\nau BufRead,BufNewFile *.tgf set filetype=tgf","first_name":"Yukio","6":"Yukio","last_name":"Siraichi","7":"Siraichi","releases":[{"0":"5289","vim_version":"5.7","1":"5.7","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"tgf-vim.tar.gz","4":"tgf-vim.tar.gz","src_id":"23805","5":"23805","creation_date":"1450534632","6":"1450534632"}]},"5288":{"script_id":"5288","0":"5288","script_name":"vim-rubyformat","1":"vim-rubyformat","script_type":"utility","2":"utility","summary":"Automatically reformats\/beautifies ruby source code","3":"Automatically reformats\/beautifies ruby source code","description":"UNMAINTAINED\r\n\r\nvim-rubyformat is a simple vim plugin, that automatically reformats\/beautifies ruby code, either when a ruby file is saved or when ff is pressed whilst in normal mode.\r\n\r\nStep 1. In any .rb (ruby) file, when save is called, the RubyFormat() function should automatically be called. It's as simple as that.\r\nStep 2 (Optional). Press ff in normal mode to call the RubyFormat() function.\r\n\r\nSettings:\r\nFor other keybindings, simply bind `:call RubyFormat()` to your chosen keybinding in your vimrc file. Example: `nnoremap fm :call RubyFormat()`\r\n\r\n`let g:remove_extra_lines = 2` is the current default, which deletes any extra blank lines more than 2 in a row. Place in vimrc to change the value.\r\n\r\nTo disable autoformatting on file save, place `let g:rubyformat_on_save = 0` in your vimrc file.","4":"UNMAINTAINED\r\n\r\nvim-rubyformat is a simple vim plugin, that automatically reformats\/beautifies ruby code, either when a ruby file is saved or when ff is pressed whilst in normal mode.\r\n\r\nStep 1. In any .rb (ruby) file, when save is called, the RubyFormat() function should automatically be called. It's as simple as that.\r\nStep 2 (Optional). Press ff in normal mode to call the RubyFormat() function.\r\n\r\nSettings:\r\nFor other keybindings, simply bind `:call RubyFormat()` to your chosen keybinding in your vimrc file. Example: `nnoremap fm :call RubyFormat()`\r\n\r\n`let g:remove_extra_lines = 2` is the current default, which deletes any extra blank lines more than 2 in a row. Place in vimrc to change the value.\r\n\r\nTo disable autoformatting on file save, place `let g:rubyformat_on_save = 0` in your vimrc file.","install_details":"","5":"","first_name":"Benjamin","6":"Benjamin","last_name":"Radovsky","7":"Radovsky","releases":[{"0":"5288","vim_version":"7.0","1":"7.0","script_version":"0.4.0","2":"0.4.0","version_comment":"Fixed small regular expression bug causing `=` sign to be pushed over with the symbol `||=`.","3":"Fixed small regular expression bug causing `=` sign to be pushed over with the symbol `||=`.","package":"vim-rubyformat-0.4.0.tar.gz","4":"vim-rubyformat-0.4.0.tar.gz","src_id":"23904","5":"23904","creation_date":"1452772417","6":"1452772417"},{"0":"5288","vim_version":"7.0","1":"7.0","script_version":"0.3.3","2":"0.3.3","version_comment":"Rebuilt some regular expression statements to fix auto formatting spacing issues, mainly inside of quotes such as \", ' and now even working  with ` too.","3":"Rebuilt some regular expression statements to fix auto formatting spacing issues, mainly inside of quotes such as \", ' and now even working  with ` too.","package":"vim-rubyformat-0.3.3.tar.gz","4":"vim-rubyformat-0.3.3.tar.gz","src_id":"23854","5":"23854","creation_date":"1451665765","6":"1451665765"},{"0":"5288","vim_version":"7.0","1":"7.0","script_version":"0.2.2","2":"0.2.2","version_comment":"Fixed a regular expression bug.","3":"Fixed a regular expression bug.","package":"vim-rubyformat-0.2.2.tar.gz","4":"vim-rubyformat-0.2.2.tar.gz","src_id":"23802","5":"23802","creation_date":"1450504447","6":"1450504447"}]},"5287":{"script_id":"5287","0":"5287","script_name":"Esper programming language syntax","1":"Esper programming language syntax","script_type":"syntax","2":"syntax","summary":"Basic syntax highlighting","3":"Basic syntax highlighting","description":"Provides only very basic syntax highlighting for EPL, but already has advanced features like schema name, table name highlighting.\r\n\r\nCode folding isn't supported right now, but will be supported soon.\r\n\r\nScreenshots: http:\/\/imgur.com\/mer3QDB\r\n\r\nFollow all the changes, also to contribute or report bugs: https:\/\/github.com\/itegulov\/vim-epl-syntax","4":"Provides only very basic syntax highlighting for EPL, but already has advanced features like schema name, table name highlighting.\r\n\r\nCode folding isn't supported right now, but will be supported soon.\r\n\r\nScreenshots: http:\/\/imgur.com\/mer3QDB\r\n\r\nFollow all the changes, also to contribute or report bugs: https:\/\/github.com\/itegulov\/vim-epl-syntax","install_details":"1) Just copy this file in your ~\/.vim\/syntax\r\n2) For Pathogen\/Vundle users: git clone https:\/\/github.com\/itegulov\/vim-epl-syntax ~\/.vim\/bundle","5":"1) Just copy this file in your ~\/.vim\/syntax\r\n2) For Pathogen\/Vundle users: git clone https:\/\/github.com\/itegulov\/vim-epl-syntax ~\/.vim\/bundle","first_name":"Daniyar","6":"Daniyar","last_name":"Itegulov","7":"Itegulov","releases":[{"0":"5287","vim_version":"7.3","1":"7.3","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"epl.vim","4":"epl.vim","src_id":"23791","5":"23791","creation_date":"1450283059","6":"1450283059"}]},"5286":{"script_id":"5286","0":"5286","script_name":"vim-unite-cscope","1":"vim-unite-cscope","script_type":"utility","2":"utility","summary":"Use cscope within vim","3":"Use cscope within vim","description":"Find this on github: https:\/\/www.github.com\/amitab\/vim-unite-cscope\r\n\r\nUniting cscope with vim. Instead of going into the csope UI, you just need to enter the search term and it will populate the vim-unite interface with the results.\r\nThis is a package similar to my other package (https:\/\/www.github.com\/amitab\/atom-cscope)\r\n\r\nPS: I just learnt vim scripting recently and there may be mistakes\/better way of doing things. \r\nIf you find any problems, please let me know.\r\n\r\n1.  Find this C symbol:                         ✓\r\n2.  Find this global definition:                ✓\r\n3.  Find functions called by this function:     ✓\r\n4.  Find functions calling this function:       ✓\r\n5.  Find this text string:                      ✓\r\n6.  Change this text string:                    ✗\r\n7.  Find this egrep pattern:                    ✓\r\n8.  Find this file:                             ✓\r\n9.  Find files #including this file:            ✓\r\n10. Find assignments to this symbol:            ✓","4":"Find this on github: https:\/\/www.github.com\/amitab\/vim-unite-cscope\r\n\r\nUniting cscope with vim. Instead of going into the csope UI, you just need to enter the search term and it will populate the vim-unite interface with the results.\r\nThis is a package similar to my other package (https:\/\/www.github.com\/amitab\/atom-cscope)\r\n\r\nPS: I just learnt vim scripting recently and there may be mistakes\/better way of doing things. \r\nIf you find any problems, please let me know.\r\n\r\n1.  Find this C symbol:                         ✓\r\n2.  Find this global definition:                ✓\r\n3.  Find functions called by this function:     ✓\r\n4.  Find functions calling this function:       ✓\r\n5.  Find this text string:                      ✓\r\n6.  Change this text string:                    ✗\r\n7.  Find this egrep pattern:                    ✓\r\n8.  Find this file:                             ✓\r\n9.  Find files #including this file:            ✓\r\n10. Find assignments to this symbol:            ✓","install_details":"This package depends on:\r\n* vim-unite (https:\/\/github.com\/Shougo\/unite.vim)\r\n* vim-proc (https:\/\/github.com\/Shougo\/vimproc.vim)\r\n\r\nAfter you've installed the dependencies, you can install this package \r\nwith your favioure package manager.\r\n\r\nExample:\r\n\r\n1. With Vundle - \r\nPlugin 'amitab\/vim-unite-cscope'\r\n\r\n2. With Pathogen\r\ncd ~\/.vim\/bundle\r\ngit clone https:\/\/github.com\/amitab\/vim-unite-cscope\r\n\r\n3. With Neobundle\r\nNeoBundle 'amitab\/vim-unite-cscope'\r\n\r\nTo generate cscope.out manually, in your project directory run:\r\n\r\nfind . -name \"*.c\" -o -name \"*.cpp\" -o -name \"*.h\" -o -name \"*.hpp\" > cscope.files\r\ncscope -q -R -b -i cscope.files\r\n\r\nAnd then the package will be able to use the cscope.out file to generate results.","5":"This package depends on:\r\n* vim-unite (https:\/\/github.com\/Shougo\/unite.vim)\r\n* vim-proc (https:\/\/github.com\/Shougo\/vimproc.vim)\r\n\r\nAfter you've installed the dependencies, you can install this package \r\nwith your favioure package manager.\r\n\r\nExample:\r\n\r\n1. With Vundle - \r\nPlugin 'amitab\/vim-unite-cscope'\r\n\r\n2. With Pathogen\r\ncd ~\/.vim\/bundle\r\ngit clone https:\/\/github.com\/amitab\/vim-unite-cscope\r\n\r\n3. With Neobundle\r\nNeoBundle 'amitab\/vim-unite-cscope'\r\n\r\nTo generate cscope.out manually, in your project directory run:\r\n\r\nfind . -name \"*.c\" -o -name \"*.cpp\" -o -name \"*.h\" -o -name \"*.hpp\" > cscope.files\r\ncscope -q -R -b -i cscope.files\r\n\r\nAnd then the package will be able to use the cscope.out file to generate results.","first_name":"Amitabh","6":"Amitabh","last_name":"Das","7":"Das","releases":[{"0":"5286","vim_version":"7.0","1":"7.0","script_version":"0.2.0","2":"0.2.0","version_comment":"1. Removed dynamic search due to lag\r\n2. Use vimproc for improved speed","3":"1. Removed dynamic search due to lag\r\n2. Use vimproc for improved speed","package":"vim-unite-cscope.tar.gz","4":"vim-unite-cscope.tar.gz","src_id":"23792","5":"23792","creation_date":"1450288470","6":"1450288470"},{"0":"5286","vim_version":"7.0","1":"7.0","script_version":"0.1.0","2":"0.1.0","version_comment":"Initial upload","3":"Initial upload","package":"vim-unite-cscope.tar.gz","4":"vim-unite-cscope.tar.gz","src_id":"23790","5":"23790","creation_date":"1450256669","6":"1450256669"}]},"5285":{"script_id":"5285","0":"5285","script_name":"vim-babel","1":"vim-babel","script_type":"utility","2":"utility","summary":"Wrapper around babel.js (ES2015, React, ...)","3":"Wrapper around babel.js (ES2015, React, ...)","description":"Babel shows how the current file or a snippet of Javascript will be transformed by babel-cli.\r\n\r\n  https:\/\/github.com\/jbgutierrez\/vim-babel\r\n","4":"Babel shows how the current file or a snippet of Javascript will be transformed by babel-cli.\r\n\r\n  https:\/\/github.com\/jbgutierrez\/vim-babel\r\n","install_details":"Copy the contents of each directory in the respective directories inside\r\n`~\/.vim`.\r\n\r\nYou need to install webapi-vim also:\r\n\r\n  http:\/\/www.vim.org\/scripts\/script.php?script_id=4019\r\n\r\nIf you want to use latest one:\r\n\r\n  https:\/\/github.com\/mattn\/webapi-vim\r\n","5":"Copy the contents of each directory in the respective directories inside\r\n`~\/.vim`.\r\n\r\nYou need to install webapi-vim also:\r\n\r\n  http:\/\/www.vim.org\/scripts\/script.php?script_id=4019\r\n\r\nIf you want to use latest one:\r\n\r\n  https:\/\/github.com\/mattn\/webapi-vim\r\n","first_name":"Javier","6":"Javier","last_name":"Blanco","7":"Blanco","releases":[{"0":"5285","vim_version":"7.4","1":"7.4","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"source-tree.tar.bz2","4":"source-tree.tar.bz2","src_id":"23788","5":"23788","creation_date":"1450084998","6":"1450084998"}]},"5284":{"script_id":"5284","0":"5284","script_name":"vim-dtsm","1":"vim-dtsm","script_type":"utility","2":"utility","summary":"Commands for TypeScript dtsm","3":"Commands for TypeScript dtsm","description":"This is a Vim plugin for dtsm command, which is dependency management tool for TypeScript .d.ts files.\r\n","4":"This is a Vim plugin for dtsm command, which is dependency management tool for TypeScript .d.ts files.\r\n","install_details":"Requirements\r\n\r\ndtsm command (npm install -g dtsm)\r\nShougo\/unite.vim\r\nIf you use NeoBundle, write the following into your .vimrc:\r\n\r\nNeoBundle 'Shougo\/unite.vim'\r\nNeoBundle 'Quramy\/vim-dtsm'\r\nAnd execute :NeoBundleInstall command in your Vim, you can get unite.vim and vim-dtsm.","5":"Requirements\r\n\r\ndtsm command (npm install -g dtsm)\r\nShougo\/unite.vim\r\nIf you use NeoBundle, write the following into your .vimrc:\r\n\r\nNeoBundle 'Shougo\/unite.vim'\r\nNeoBundle 'Quramy\/vim-dtsm'\r\nAnd execute :NeoBundleInstall command in your Vim, you can get unite.vim and vim-dtsm.","first_name":"Yosuke","6":"Yosuke","last_name":"Kurami","7":"Kurami","releases":[{"0":"5284","vim_version":"7.0","1":"7.0","script_version":"1.0.0","2":"1.0.0","version_comment":"Initial upload","3":"Initial upload","package":"vim-dtsm-1.0.0.zip","4":"vim-dtsm-1.0.0.zip","src_id":"23787","5":"23787","creation_date":"1450081343","6":"1450081343"}]},"5283":{"script_id":"5283","0":"5283","script_name":"ESI VPS FEA-Solver Syntax Highlighting","1":"ESI VPS FEA-Solver Syntax Highlighting","script_type":"syntax","2":"syntax","summary":"Syntax Highlighting for ESI VPS (Pam-Crash) FEA-Solver","3":"Syntax Highlighting for ESI VPS (Pam-Crash) FEA-Solver","description":"Features:\r\n   * VPS 2022 Syntax Highlighting\r\n   * Supports light and dark background\r\n   * Macros for Card Templates (type :help pam for a complete list)\r\n   * Interactive hints for fixed format in Status Bar\r\n   * Omni-Completion for Parameters (look for \"(menu)\" in Status Bar, then press Tab in a command mode ;-)\r\n   * Tags Support for Entity IDs (press F12 to create\/update the tagfile, then look for \"(tag)\" in Status Bar)\r\n   * Omni-Completion for Entity Selection (when tagfile exists (F12))\r\n   * Expression-based Folding (activate with :se fdm=expr)\r\n   * Development tracked in https:\/\/github.com\/jazzman007\/pamcrash_vim_syntax","4":"Features:\r\n   * VPS 2022 Syntax Highlighting\r\n   * Supports light and dark background\r\n   * Macros for Card Templates (type :help pam for a complete list)\r\n   * Interactive hints for fixed format in Status Bar\r\n   * Omni-Completion for Parameters (look for \"(menu)\" in Status Bar, then press Tab in a command mode ;-)\r\n   * Tags Support for Entity IDs (press F12 to create\/update the tagfile, then look for \"(tag)\" in Status Bar)\r\n   * Omni-Completion for Entity Selection (when tagfile exists (F12))\r\n   * Expression-based Folding (activate with :se fdm=expr)\r\n   * Development tracked in https:\/\/github.com\/jazzman007\/pamcrash_vim_syntax","install_details":"Just untar in ~\/.vim and enjoy!","5":"Just untar in ~\/.vim and enjoy!","first_name":"Roman","6":"Roman","last_name":"Firt","7":"Firt","releases":[{"0":"5283","vim_version":"8.1","1":"8.1","script_version":"12.0","2":"12.0","version_comment":"VPS 2022 Syntax Implemented\r\nRelease dedicated to Bram (1961-2023)","3":"VPS 2022 Syntax Implemented\r\nRelease dedicated to Bram (1961-2023)","package":"pamcrash_vim_syntax_120.tar.bz2","4":"pamcrash_vim_syntax_120.tar.bz2","src_id":"28583","5":"28583","creation_date":"1703253984","6":"1703253984"},{"0":"5283","vim_version":"8.1","1":"8.1","script_version":"11.0","2":"11.0","version_comment":"VPS 2021 Syntax Implemented","3":"VPS 2021 Syntax Implemented","package":"pamcrash_vim_syntax_110.tgz","4":"pamcrash_vim_syntax_110.tgz","src_id":"27865","5":"27865","creation_date":"1640306250","6":"1640306250"},{"0":"5283","vim_version":"8.1","1":"8.1","script_version":"10.1","2":"10.1","version_comment":"2020.5 new Modular Material Syntax implemented (experimental, feedback appreciated)\r\nMinor Bugfixes","3":"2020.5 new Modular Material Syntax implemented (experimental, feedback appreciated)\r\nMinor Bugfixes","package":"pamcrash_vim_syntax_101.tgz","4":"pamcrash_vim_syntax_101.tgz","src_id":"27570","5":"27570","creation_date":"1618207559","6":"1618207559"},{"0":"5283","vim_version":"8.1","1":"8.1","script_version":"10.0","2":"10.0","version_comment":"VPS 2020 Syntax Implemented\r\nMoved from syntax-based to expression-based folding - MASSIVE speedup!!!, finally usable on big decks - activate by typing :se fdm=expr or put it in your .vimrc\r\nReleased under WTFPL","3":"VPS 2020 Syntax Implemented\r\nMoved from syntax-based to expression-based folding - MASSIVE speedup!!!, finally usable on big decks - activate by typing :se fdm=expr or put it in your .vimrc\r\nReleased under WTFPL","package":"pamcrash_vim_syntax_100.tgz","4":"pamcrash_vim_syntax_100.tgz","src_id":"27484","5":"27484","creation_date":"1613541918","6":"1613541918"},{"0":"5283","vim_version":"7.2","1":"7.2","script_version":"9.0","2":"9.0","version_comment":"VPS 2019 Syntax Implemented ","3":"VPS 2019 Syntax Implemented ","package":"pamcrash_vim_syntax_90.tgz","4":"pamcrash_vim_syntax_90.tgz","src_id":"27469","5":"27469","creation_date":"1612423743","6":"1612423743"},{"0":"5283","vim_version":"7.2","1":"7.2","script_version":"8.0","2":"8.0","version_comment":"VPS 2018 Syntax Implemented ","3":"VPS 2018 Syntax Implemented ","package":"pamcrash_vim_syntax_80.tgz","4":"pamcrash_vim_syntax_80.tgz","src_id":"27444","5":"27444","creation_date":"1610926596","6":"1610926596"},{"0":"5283","vim_version":"7.2","1":"7.2","script_version":"7.3","2":"7.3","version_comment":"tiny PREFILTER TYPE bugfix","3":"tiny PREFILTER TYPE bugfix","package":"pamcrash_vim_syntax_73.tgz","4":"pamcrash_vim_syntax_73.tgz","src_id":"25756","5":"25756","creation_date":"1515575835","6":"1515575835"},{"0":"5283","vim_version":"7.2","1":"7.2","script_version":"7.2","2":"7.2","version_comment":"minor PICIMP Syntax Bugfix","3":"minor PICIMP Syntax Bugfix","package":"pamcrash_vim_syntax_72.tgz","4":"pamcrash_vim_syntax_72.tgz","src_id":"25672","5":"25672","creation_date":"1511940292","6":"1511940292"},{"0":"5283","vim_version":"7.2","1":"7.2","script_version":"7.1","2":"7.1","version_comment":"VPS 2017 Syntax Implemented\r\nSolver Defaults in Omni-Completion showed (where documented)\r\nSeveral minor Improvements and Bugfixes","3":"VPS 2017 Syntax Implemented\r\nSolver Defaults in Omni-Completion showed (where documented)\r\nSeveral minor Improvements and Bugfixes","package":"pamcrash_vim_syntax_71.tgz","4":"pamcrash_vim_syntax_71.tgz","src_id":"25536","5":"25536","creation_date":"1503938253","6":"1503938253"},{"0":"5283","vim_version":"7.2","1":"7.2","script_version":"6.0","2":"6.0","version_comment":"VPS 2016 Syntax Implemented\r\nSeveral minor Improvements and Bugfixes","3":"VPS 2016 Syntax Implemented\r\nSeveral minor Improvements and Bugfixes","package":"pamcrash_syntax_60.tgz","4":"pamcrash_syntax_60.tgz","src_id":"24975","5":"24975","creation_date":"1487255314","6":"1487255314"},{"0":"5283","vim_version":"7.2","1":"7.2","script_version":"5.0","2":"5.0","version_comment":"VPS 2015 Syntax Implemented\r\nSeveral minor Improvements and Bugfixes","3":"VPS 2015 Syntax Implemented\r\nSeveral minor Improvements and Bugfixes","package":"pamcrash_syntax_50.tgz","4":"pamcrash_syntax_50.tgz","src_id":"24068","5":"24068","creation_date":"1457201821","6":"1457201821"},{"0":"5283","vim_version":"7.2","1":"7.2","script_version":"4.1","2":"4.1","version_comment":"Initial upload","3":"Initial upload","package":"pamcrash_syntax_41.tgz","4":"pamcrash_syntax_41.tgz","src_id":"23785","5":"23785","creation_date":"1449989471","6":"1449989471"}]},"5282":{"script_id":"5282","0":"5282","script_name":"vim-do","1":"vim-do","script_type":"utility","2":"utility","summary":"Run shell commands asynchronously and show the output in Vim when they finish","3":"Run shell commands asynchronously and show the output in Vim when they finish","description":"For the full README visit the GitHub repo: https:\/\/github.com\/joonty\/vim-do.\r\n\r\n== Description\r\n\r\nThe aim of this plugin is to provide a quick and simple way of running shell commands in the background, and displaying the results (output, exit status, etc) in a Vim buffer as the process is running. That means you can run several commands, carry on working in Vim, and swap between the processes at will or just keep them running hidden in the background.\r\n\r\nIt works nicely for both short- and long-running processes, and the great thing is that you don't have to swap between a terminal and Vim to run commands or see their output.\r\n\r\n== Features\r\n\r\nAfter installing (see below) you're given the :Do vim command, which allows you to run any shell command:\r\n\r\n    :Do echo \"hi\"\r\n    :Do rake\r\n    :Do find \/\r\n\r\nOops, that last command is gonna take a while...\r\n\r\nBut don't worry, it's asynchronous! A new buffer will pop up while it's running and show the output. If you close it, it will keep running until the command finishes naturally. You can run as many commands at the same time as your computer can handle.\r\n\r\nFor more information, continue reading on the GitHub README: https:\/\/github.com\/joonty\/vim-do.\r\n","4":"For the full README visit the GitHub repo: https:\/\/github.com\/joonty\/vim-do.\r\n\r\n== Description\r\n\r\nThe aim of this plugin is to provide a quick and simple way of running shell commands in the background, and displaying the results (output, exit status, etc) in a Vim buffer as the process is running. That means you can run several commands, carry on working in Vim, and swap between the processes at will or just keep them running hidden in the background.\r\n\r\nIt works nicely for both short- and long-running processes, and the great thing is that you don't have to swap between a terminal and Vim to run commands or see their output.\r\n\r\n== Features\r\n\r\nAfter installing (see below) you're given the :Do vim command, which allows you to run any shell command:\r\n\r\n    :Do echo \"hi\"\r\n    :Do rake\r\n    :Do find \/\r\n\r\nOops, that last command is gonna take a while...\r\n\r\nBut don't worry, it's asynchronous! A new buffer will pop up while it's running and show the output. If you close it, it will keep running until the command finishes naturally. You can run as many commands at the same time as your computer can handle.\r\n\r\nFor more information, continue reading on the GitHub README: https:\/\/github.com\/joonty\/vim-do.\r\n","install_details":"Requires Vim compiled with Python 2.4+ support\r\n\r\n== Classic\r\n\r\nClone or download a tarball of the plugin and move its content in your ~\/.vim\/ directory.\r\n\r\nYour ~\/.vim\/plugin\/ directory should now contain the file \"do.vim\", and your autoload should contain the file \"do.vim\" and a directory called \"python\".\r\n\r\n== Using git and Pathogen\r\n\r\nClone this repository in your ~\/.vim\/bundle directory\r\n\r\n== Using vundle\r\n\r\nAdd this to your ~\/.vimrc file:\r\n\r\n    Bundle 'joonty\/vim-do.git'\r\n\r\nThen, from the command line, run:\r\n\r\n    vim +BundleInstall +qall","5":"Requires Vim compiled with Python 2.4+ support\r\n\r\n== Classic\r\n\r\nClone or download a tarball of the plugin and move its content in your ~\/.vim\/ directory.\r\n\r\nYour ~\/.vim\/plugin\/ directory should now contain the file \"do.vim\", and your autoload should contain the file \"do.vim\" and a directory called \"python\".\r\n\r\n== Using git and Pathogen\r\n\r\nClone this repository in your ~\/.vim\/bundle directory\r\n\r\n== Using vundle\r\n\r\nAdd this to your ~\/.vimrc file:\r\n\r\n    Bundle 'joonty\/vim-do.git'\r\n\r\nThen, from the command line, run:\r\n\r\n    vim +BundleInstall +qall","first_name":"Jon","6":"Jon","last_name":"Cairns","7":"Cairns","releases":[{"0":"5282","vim_version":"7.0","1":"7.0","script_version":"0.1.0","2":"0.1.0","version_comment":"Initial upload","3":"Initial upload","package":"vim-do-0.1.0.tar.gz","4":"vim-do-0.1.0.tar.gz","src_id":"23783","5":"23783","creation_date":"1449766352","6":"1449766352"}]},"5281":{"script_id":"5281","0":"5281","script_name":"Tabstuff","1":"Tabstuff","script_type":"utility","2":"utility","summary":"Tabstuff is a plugin to sulplies various tabrelated stuff","3":"Tabstuff is a plugin to sulplies various tabrelated stuff","description":"Tabstuff puts in toolbar buttons and a tab menu, that lets you do things like: open a file in a new tab create a new file in a new tab open all buffers  in separate tabs; this will only work up to tabpagemax tabs the rest will be opened in widows in the last tab.\r\n\r\nThere is also functions to move tabs, change tabs close the current tab: NB: this will not close the buffer, to do that use Buffers->delete.\r\n\r\nIf you want to increase the maximum number of tabs then set tabpagemax to your desired value I have; set tabpagemax=50 in my .gvimrc file .\r\n\r\nIf you wish to open the help in a new tab or helpgrep then there are two buttons for this.\r\n\r\nFollow the tool tips for more details.","4":"Tabstuff puts in toolbar buttons and a tab menu, that lets you do things like: open a file in a new tab create a new file in a new tab open all buffers  in separate tabs; this will only work up to tabpagemax tabs the rest will be opened in widows in the last tab.\r\n\r\nThere is also functions to move tabs, change tabs close the current tab: NB: this will not close the buffer, to do that use Buffers->delete.\r\n\r\nIf you want to increase the maximum number of tabs then set tabpagemax to your desired value I have; set tabpagemax=50 in my .gvimrc file .\r\n\r\nIf you wish to open the help in a new tab or helpgrep then there are two buttons for this.\r\n\r\nFollow the tool tips for more details.","install_details":"Tabstuff Installation (Linux):\r\n1. Download tabstuff--.tar.bz2 and extract it\r\n2. Put everything which in tabstuff- folder to ~\/.vim, or put videm to ~\/.vim\/bundle if you use pathogen \r\n3. or use vundle https:\/\/github.com\/VundleVim\/Vundle.vim and add tabstuff as\r\n\r\nPlugin 'grizzlysmit\/tabstuff.vim'\r\n\r\nInstallation(Windows):\r\n1. Download tabstuff--.tar.bz2 and extract it\r\n2. Put everything which in tabstuff- folder to $VIM\\vimfiles (for example of mine: C:\\Program Files\\Vim\\vimfiles) or put tabstuff folder into $VIM\\vimfiles\\bundle if you use pathogen\r\n3. or use vundle https:\/\/github.com\/VundleVim\/Vundle.vim and add tabstuff as\r\n\r\nPlugin 'grizzlysmit\/tabstuff.vim'\r\n\r\noptionally you can use the tabstuff-.zip archive","5":"Tabstuff Installation (Linux):\r\n1. Download tabstuff--.tar.bz2 and extract it\r\n2. Put everything which in tabstuff- folder to ~\/.vim, or put videm to ~\/.vim\/bundle if you use pathogen \r\n3. or use vundle https:\/\/github.com\/VundleVim\/Vundle.vim and add tabstuff as\r\n\r\nPlugin 'grizzlysmit\/tabstuff.vim'\r\n\r\nInstallation(Windows):\r\n1. Download tabstuff--.tar.bz2 and extract it\r\n2. Put everything which in tabstuff- folder to $VIM\\vimfiles (for example of mine: C:\\Program Files\\Vim\\vimfiles) or put tabstuff folder into $VIM\\vimfiles\\bundle if you use pathogen\r\n3. or use vundle https:\/\/github.com\/VundleVim\/Vundle.vim and add tabstuff as\r\n\r\nPlugin 'grizzlysmit\/tabstuff.vim'\r\n\r\noptionally you can use the tabstuff-.zip archive","first_name":"Francis Grizzly","6":"Francis Grizzly","last_name":"Smit","7":"Smit","releases":[{"0":"5281","vim_version":"7.0","1":"7.0","script_version":"1.3.1-zip","2":"1.3.1-zip","version_comment":"fixed a small error introduced when I fixed the last error, this is the zip version ","3":"fixed a small error introduced when I fixed the last error, this is the zip version ","package":"tabstuff.vim.zip","4":"tabstuff.vim.zip","src_id":"27603","5":"27603","creation_date":"1621018498","6":"1621018498"},{"0":"5281","vim_version":"7.0","1":"7.0","script_version":"1.3.1-tar","2":"1.3.1-tar","version_comment":"fixed a error introduced while fixing the last error, looks good now :)","3":"fixed a error introduced while fixing the last error, looks good now :)","package":"tabstuff.vim.tar.gz","4":"tabstuff.vim.tar.gz","src_id":"27602","5":"27602","creation_date":"1621018404","6":"1621018404"},{"0":"5281","vim_version":"7.0","1":"7.0","script_version":"1.3","2":"1.3","version_comment":"no longer causes errors when you use the terminal version of vim, as it no longer loads menus etc in that case","3":"no longer causes errors when you use the terminal version of vim, as it no longer loads menus etc in that case","package":"tabstuff.vim.tar.gz","4":"tabstuff.vim.tar.gz","src_id":"27598","5":"27598","creation_date":"1620943709","6":"1620943709"}]},"5280":{"script_id":"5280","0":"5280","script_name":"snpsMan2VimSyntax","1":"snpsMan2VimSyntax","script_type":"syntax","2":"syntax","summary":"Perl script to parse Synopsys man pages to create a vim syntax file","3":"Perl script to parse Synopsys man pages to create a vim syntax file","description":"If you are editing Tcl scripts for use with Synopsys tools, you will appreciate proper syntax highlighting for the command names as well as the command options. However, rather than providing a pre-compiled syntax file that will not match your installation of the Synopsys tools, this script can be used to generate them.\r\n\r\nThe script is freely available on GitHub; see more info here:\r\nhttps:\/\/github.com\/rolleric\/snpsMan2VimSyntax","4":"If you are editing Tcl scripts for use with Synopsys tools, you will appreciate proper syntax highlighting for the command names as well as the command options. However, rather than providing a pre-compiled syntax file that will not match your installation of the Synopsys tools, this script can be used to generate them.\r\n\r\nThe script is freely available on GitHub; see more info here:\r\nhttps:\/\/github.com\/rolleric\/snpsMan2VimSyntax","install_details":"","5":"","first_name":"Eric","6":"Eric","last_name":"Roller","7":"Roller","releases":[{"0":"5280","vim_version":"7.0","1":"7.0","script_version":"1.6.1","2":"1.6.1","version_comment":"Initial upload","3":"Initial upload","package":"snpsMan2VimSyntax.tar.gz","4":"snpsMan2VimSyntax.tar.gz","src_id":"23773","5":"23773","creation_date":"1449084480","6":"1449084480"}]},"5279":{"script_id":"5279","0":"5279","script_name":"vim-stata","1":"vim-stata","script_type":"ftplugin","2":"ftplugin","summary":"Vim Plugin for Running Selected Do-File Lines in Stata","3":"Vim Plugin for Running Selected Do-File Lines in Stata","description":"Vim is known as a highly configurable text editor built to enable efficient text editing, and Stata is one of the most popular statistical packages with a huge user-community. This plugin (beta) is developed to make connections between Vim and Stata and supports Mac OS X and Linux. With our plugin, you could easily send selected do file lines from Vim to have them run in Stata. To the best of our knowledge, this is probably the first plugin to link Vim and Stata under Unix-like platforms. (For Windows users, please refer to the information in the last section). Please feel free to let us know if you have any comments or suggestions.\r\n\r\n(Authors: Zizhong Yan (corresponding author), Isaac M. E. Dodd, and C Wang)\r\n\r\nGithub webpage\r\nhttps:\/\/github.com\/zizhongyan\/vim-stata \r\n\r\nPlatforms\r\nWindows, MacOS, and Linux.\r\n\r\nUpdates\r\n1, Linux Support: This update adds support for Linux systems to run Do file lines. Edits to the plugin were made by Isaac M. E. Dodd. (Last edited on 01 Apr 2019 by I Dodd)\r\n2, Syntax highlighting: This update enables the Stata syntax highlighting in Vim. An updated and enhanced Stata syntax file has been included (based on Jeffrey Pitblado's Stata syntax file). (Thanks for William Buchanan's suggestion.) (Last edited on 29 Feb 2016 by Z Yan and C Wang )\r\n\r\nBackground information\r\n\r\n1, This plugin is motivated by the article \"Some notes on text editors for Stata users\"(http:\/\/fmwww.bc.edu\/repec\/bocode\/t\/textEditors.html#vim).\r\n\r\nThis plugin basically creates a temporary do-file, which is then sent to the Stata to execute. The Stata13+ has introduced the AppleScript commands (i.e. DoCommand and DoCommandAsync) which allows script commands to directly enter the Stata without creating any temporary file. However, we did not consider this option for two reasons:\r\n\r\ni) AppleScript commands will go through all selected commands anyways even if the Stata has already reported an error message. This behaves quite differently from the Stata in-built do-file editor and could probably cause mistakes.\r\n\r\nii) AppleScript commands sometimes do not work properly based on our own experience and tests, though we have not figured out the reason so far. Therefore we believe that creating a temporary do-file would be safer and more reliable and it behaves exactly the same as what the in-built do-file editor does. The temp file is harmless since it has just been temporarily saved in a cache folders in the OS X.\r\n\r\n2, For Windows users, please follow the instructions in the webpage above.\r\n\r\n3, This plugin has been tested on Mac OS X Yosemite and El Capitan and supports Stata 12-14SE\/MP\/IC. (It should also work well with Stata 11, but has not been formally tested)","4":"Vim is known as a highly configurable text editor built to enable efficient text editing, and Stata is one of the most popular statistical packages with a huge user-community. This plugin (beta) is developed to make connections between Vim and Stata and supports Mac OS X and Linux. With our plugin, you could easily send selected do file lines from Vim to have them run in Stata. To the best of our knowledge, this is probably the first plugin to link Vim and Stata under Unix-like platforms. (For Windows users, please refer to the information in the last section). Please feel free to let us know if you have any comments or suggestions.\r\n\r\n(Authors: Zizhong Yan (corresponding author), Isaac M. E. Dodd, and C Wang)\r\n\r\nGithub webpage\r\nhttps:\/\/github.com\/zizhongyan\/vim-stata \r\n\r\nPlatforms\r\nWindows, MacOS, and Linux.\r\n\r\nUpdates\r\n1, Linux Support: This update adds support for Linux systems to run Do file lines. Edits to the plugin were made by Isaac M. E. Dodd. (Last edited on 01 Apr 2019 by I Dodd)\r\n2, Syntax highlighting: This update enables the Stata syntax highlighting in Vim. An updated and enhanced Stata syntax file has been included (based on Jeffrey Pitblado's Stata syntax file). (Thanks for William Buchanan's suggestion.) (Last edited on 29 Feb 2016 by Z Yan and C Wang )\r\n\r\nBackground information\r\n\r\n1, This plugin is motivated by the article \"Some notes on text editors for Stata users\"(http:\/\/fmwww.bc.edu\/repec\/bocode\/t\/textEditors.html#vim).\r\n\r\nThis plugin basically creates a temporary do-file, which is then sent to the Stata to execute. The Stata13+ has introduced the AppleScript commands (i.e. DoCommand and DoCommandAsync) which allows script commands to directly enter the Stata without creating any temporary file. However, we did not consider this option for two reasons:\r\n\r\ni) AppleScript commands will go through all selected commands anyways even if the Stata has already reported an error message. This behaves quite differently from the Stata in-built do-file editor and could probably cause mistakes.\r\n\r\nii) AppleScript commands sometimes do not work properly based on our own experience and tests, though we have not figured out the reason so far. Therefore we believe that creating a temporary do-file would be safer and more reliable and it behaves exactly the same as what the in-built do-file editor does. The temp file is harmless since it has just been temporarily saved in a cache folders in the OS X.\r\n\r\n2, For Windows users, please follow the instructions in the webpage above.\r\n\r\n3, This plugin has been tested on Mac OS X Yosemite and El Capitan and supports Stata 12-14SE\/MP\/IC. (It should also work well with Stata 11, but has not been formally tested)","install_details":"Please also refer to the Github webpage: https:\/\/github.com\/zizhongyan\/vim-stata \r\n\r\n\r\n1, Installation Options\r\n1.1. Manual Installation: Put vim-stata.vim (the plugin file) directly into your Vim directory. In Windows or MacOS this is either vimfiles\/plugin or vim81\/plugin. In Linux, this is .vim\r\n\r\n1.2. Package\/Plugin Managers: Or use the plugins Vim-Plug, Vundle, or pathogen.vim to install it from the git repository.\r\n\r\n2, To ensure that the do-files open in Stata by default and hence are executed directly, we need to make the following two changes.\r\nEnsure the do-files are opened in Stata by default. If it is not, please right click on any do-file and set the OS to always open the do-file in Stata by the following:\r\n\r\n2.1. On Windows: choose 'Open With', select Stata, and choose 'Always open'\r\n\r\n2.2. On MacOS: under Finder > Open With > Select Stata from Applications folder > check \"Always Open With\" > Open. Also, uncheck the \"Edit do-files opened from the Finder in Do-file Editor\" in Preference>General Preference>Windows>Do-file Editor>Advanced (Stata 13\/14), or Preferences > Do-file Editor > Advanced (Stata 12).\r\n\r\n2.3. On Linux KDE: choose 'Open With', Select Other Application, then choose Stata and check \"Remember application association\"\r\n\r\n3, Settings Configuration (Required for Linux Users)\r\nFor linux distributions, the following additional settings configuration in your .vimrc file is needed:\r\n\r\nRequired Setup Steps\r\nFor Linux users, you have to let the plugin know where your Stata binary lives (which should a binary located in a directory that is in your $PATH variable). To determine where your Stata binary is, open a terminal and enter which stata. Then, copy the path it prints out into the variable below. In your .vimrc file, paste the path into 1 of the following two variable definitions:\r\n\r\n\" Path to Stata - Set either one of these but not both. Paste in the path with the executable filename\r\n\"\tExample: On Linux, \/usr\/local\/stata15\/xstata for Stata 15\r\n\" -- Option (1): Path to the Stata binary (including the executable name)\r\nlet g:vimforstata_pathbin = \"\/usr\/local\/stata15\/xstata\"\r\nOr:\r\n\r\n\" -- Option (2): Path to a shell script with code that runs Stata\r\nlet g:vimforstata_pathbin_sh = \"~\/Scripts\/stata.sh\"\r\nA standard installation of Stata on Linux comes with different executable options (stata, xstata, stata-sm, stata-se, stata-mp, etc.). Usually for a Linux installation, \/stata is the console version and \/xstata is the GUI version. Enter in the one that's appropriate to your installation and license.\r\n\r\nThe shell script variable option allows you to specify a .sh file that launches Stata when called (plus any other automating functions you want to put in the script, such as to save a copy of the lines you run in the do file somewhere else). Just make sure that your shell script takes arguments and passes it to the executable you specify appropriately. For the bang you can use the launcher available for your Linux distribution's desktop environment (e.g., gvfs-open for Gnome users, xdg-open for other desktop environments, or gtk-launch as a last result).\r\n\r\nHere is a basic example using gtk-launch in a file located at ~\/Scripts\/stata.sh as in the above sample variable for a stata15 binary located in the usr\/local $PATH directory:\r\n\r\n#!\/usr\/bin\/env gtk-launch\r\n\/usr\/local\/stata15\/xstata $@\r\n\r\n4, Hotkey binding (optional)\r\nThe hotkey for executing selected codes is set to be F9.\r\n\r\nPlease note that you could customise your hotkey by simply adding a sentence to your .vimrc or vimrc, for example:\r\n\r\n\" Select Do file lines (with v or V) and run them with Ctrl+Shift+X\r\n:vmap  :call RunDoLines()\r\nThen the hotkey would be changed to Ctrl+Shift+X\r\n\r\n5, Column Line (optional)\r\nThe Stata do file editor puts a helpful line at the 80th column to let the user know when the lines they're coding are getting too long. By default this is turned on for any .do file. Feel free to turn this OFF with the following setting:\r\n\r\n\" Turn off the 80th column line\r\nlet g:vimforstata_set_column == 0\r\n5, Restart the Vim and hit F9 or the customised hotkey to run the selected codes.","5":"Please also refer to the Github webpage: https:\/\/github.com\/zizhongyan\/vim-stata \r\n\r\n\r\n1, Installation Options\r\n1.1. Manual Installation: Put vim-stata.vim (the plugin file) directly into your Vim directory. In Windows or MacOS this is either vimfiles\/plugin or vim81\/plugin. In Linux, this is .vim\r\n\r\n1.2. Package\/Plugin Managers: Or use the plugins Vim-Plug, Vundle, or pathogen.vim to install it from the git repository.\r\n\r\n2, To ensure that the do-files open in Stata by default and hence are executed directly, we need to make the following two changes.\r\nEnsure the do-files are opened in Stata by default. If it is not, please right click on any do-file and set the OS to always open the do-file in Stata by the following:\r\n\r\n2.1. On Windows: choose 'Open With', select Stata, and choose 'Always open'\r\n\r\n2.2. On MacOS: under Finder > Open With > Select Stata from Applications folder > check \"Always Open With\" > Open. Also, uncheck the \"Edit do-files opened from the Finder in Do-file Editor\" in Preference>General Preference>Windows>Do-file Editor>Advanced (Stata 13\/14), or Preferences > Do-file Editor > Advanced (Stata 12).\r\n\r\n2.3. On Linux KDE: choose 'Open With', Select Other Application, then choose Stata and check \"Remember application association\"\r\n\r\n3, Settings Configuration (Required for Linux Users)\r\nFor linux distributions, the following additional settings configuration in your .vimrc file is needed:\r\n\r\nRequired Setup Steps\r\nFor Linux users, you have to let the plugin know where your Stata binary lives (which should a binary located in a directory that is in your $PATH variable). To determine where your Stata binary is, open a terminal and enter which stata. Then, copy the path it prints out into the variable below. In your .vimrc file, paste the path into 1 of the following two variable definitions:\r\n\r\n\" Path to Stata - Set either one of these but not both. Paste in the path with the executable filename\r\n\"\tExample: On Linux, \/usr\/local\/stata15\/xstata for Stata 15\r\n\" -- Option (1): Path to the Stata binary (including the executable name)\r\nlet g:vimforstata_pathbin = \"\/usr\/local\/stata15\/xstata\"\r\nOr:\r\n\r\n\" -- Option (2): Path to a shell script with code that runs Stata\r\nlet g:vimforstata_pathbin_sh = \"~\/Scripts\/stata.sh\"\r\nA standard installation of Stata on Linux comes with different executable options (stata, xstata, stata-sm, stata-se, stata-mp, etc.). Usually for a Linux installation, \/stata is the console version and \/xstata is the GUI version. Enter in the one that's appropriate to your installation and license.\r\n\r\nThe shell script variable option allows you to specify a .sh file that launches Stata when called (plus any other automating functions you want to put in the script, such as to save a copy of the lines you run in the do file somewhere else). Just make sure that your shell script takes arguments and passes it to the executable you specify appropriately. For the bang you can use the launcher available for your Linux distribution's desktop environment (e.g., gvfs-open for Gnome users, xdg-open for other desktop environments, or gtk-launch as a last result).\r\n\r\nHere is a basic example using gtk-launch in a file located at ~\/Scripts\/stata.sh as in the above sample variable for a stata15 binary located in the usr\/local $PATH directory:\r\n\r\n#!\/usr\/bin\/env gtk-launch\r\n\/usr\/local\/stata15\/xstata $@\r\n\r\n4, Hotkey binding (optional)\r\nThe hotkey for executing selected codes is set to be F9.\r\n\r\nPlease note that you could customise your hotkey by simply adding a sentence to your .vimrc or vimrc, for example:\r\n\r\n\" Select Do file lines (with v or V) and run them with Ctrl+Shift+X\r\n:vmap  :call RunDoLines()\r\nThen the hotkey would be changed to Ctrl+Shift+X\r\n\r\n5, Column Line (optional)\r\nThe Stata do file editor puts a helpful line at the 80th column to let the user know when the lines they're coding are getting too long. By default this is turned on for any .do file. Feel free to turn this OFF with the following setting:\r\n\r\n\" Turn off the 80th column line\r\nlet g:vimforstata_set_column == 0\r\n5, Restart the Vim and hit F9 or the customised hotkey to run the selected codes.","first_name":"Zizhong","6":"Zizhong","last_name":"Yan","7":"Yan","releases":[{"0":"5279","vim_version":"7.4","1":"7.4","script_version":"1.1.0","2":"1.1.0","version_comment":"This pull request, written in VimScript, adds support for Linux distributions with installations of Stata to the vim-stata plugin to run do file lines.\r\nThe pull request also updates README.md to reflect the settings changes to the code for Linux users to properly configure the plugin to work with either their Stata binary executable or a shell script.","3":"This pull request, written in VimScript, adds support for Linux distributions with installations of Stata to the vim-stata plugin to run do file lines.\r\nThe pull request also updates README.md to reflect the settings changes to the code for Linux users to properly configure the plugin to work with either their Stata binary executable or a shell script.","package":"vim-stata.vim","4":"vim-stata.vim","src_id":"26450","5":"26450","creation_date":"1554548195","6":"1554548195"},{"0":"5279","vim_version":"7.4","1":"7.4","script_version":"1.0.2","2":"1.0.2","version_comment":"Initial upload","3":"Initial upload","package":"vim-stata.vim","4":"vim-stata.vim","src_id":"23772","5":"23772","creation_date":"1449080372","6":"1449080372"}]},"5278":{"script_id":"5278","0":"5278","script_name":"vim-uci","1":"vim-uci","script_type":"ftplugin","2":"ftplugin","summary":"Syntax, ftdetect and ftplugin for OpenWRT's UCI format","3":"Syntax, ftdetect and ftplugin for OpenWRT's UCI format","description":"https:\/\/github.com\/cmcaine\/vim-uci\r\n\r\nTiny, simple ftdetect, ftplugin and syntax scripts for OpenWRT's Unified Configuration Interface files.\r\n\r\nDon't have vim on your router? I don't either, but this works great with sshfs.\r\n\r\n# Bonus features\r\n\r\nftplugin\/uci.vim sets commentstring correctly, so tpope's [vim-commentary](https:\/\/github.com\/tpope\/vim-commentary) works as intended!\r\n\r\n# License\r\n\r\nCopyright Colin Caine. GPL v3.","4":"https:\/\/github.com\/cmcaine\/vim-uci\r\n\r\nTiny, simple ftdetect, ftplugin and syntax scripts for OpenWRT's Unified Configuration Interface files.\r\n\r\nDon't have vim on your router? I don't either, but this works great with sshfs.\r\n\r\n# Bonus features\r\n\r\nftplugin\/uci.vim sets commentstring correctly, so tpope's [vim-commentary](https:\/\/github.com\/tpope\/vim-commentary) works as intended!\r\n\r\n# License\r\n\r\nCopyright Colin Caine. GPL v3.","install_details":"If you don't have a preferred installation method, I recommend installing\r\n[pathogen.vim](https:\/\/github.com\/tpope\/vim-pathogen), and then simply copy and\r\npaste:\r\n\r\n    cd ~\/.vim\/bundle\r\n    git clone git:\/\/github.com\/cmcaine\/vim-uci.git\r\n\r\nVundle, etc. will probably work fine too.","5":"If you don't have a preferred installation method, I recommend installing\r\n[pathogen.vim](https:\/\/github.com\/tpope\/vim-pathogen), and then simply copy and\r\npaste:\r\n\r\n    cd ~\/.vim\/bundle\r\n    git clone git:\/\/github.com\/cmcaine\/vim-uci.git\r\n\r\nVundle, etc. will probably work fine too.","first_name":"Colin","6":"Colin","last_name":"Caine","7":"Caine","releases":[{"0":"5278","vim_version":"7.0","1":"7.0","script_version":"1","2":"1","version_comment":"Initial upload","3":"Initial upload","package":"vim-uci.zip","4":"vim-uci.zip","src_id":"23771","5":"23771","creation_date":"1449012349","6":"1449012349"}]},"5277":{"script_id":"5277","0":"5277","script_name":"vim-cloud-buffer","1":"vim-cloud-buffer","script_type":"utility","2":"utility","summary":"Save your buffers remotely ","3":"Save your buffers remotely ","description":"CloudBuffer is a plugin developed to store and retrieve buffers in a MongoDB Simple Http Rest endpoint.\r\n\r\nhttps:\/\/github.com\/jbgutierrez\/vim-cloud-buffer","4":"CloudBuffer is a plugin developed to store and retrieve buffers in a MongoDB Simple Http Rest endpoint.\r\n\r\nhttps:\/\/github.com\/jbgutierrez\/vim-cloud-buffer","install_details":"Copy the contents of each directory in the respective directories inside ~\/.vim. (~\\vimfiles on Windows) ","5":"Copy the contents of each directory in the respective directories inside ~\/.vim. (~\\vimfiles on Windows) ","first_name":"Javier","6":"Javier","last_name":"Blanco","7":"Blanco","releases":[{"0":"5277","vim_version":"7.3","1":"7.3","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"vim-cloud-buffer.tgz","4":"vim-cloud-buffer.tgz","src_id":"23767","5":"23767","creation_date":"1448918971","6":"1448918971"}]},"5276":{"script_id":"5276","0":"5276","script_name":"optcmd","1":"optcmd","script_type":"utility","2":"utility","summary":"plugin provides dialog for choicing command and process it by prefix option","3":"plugin provides dialog for choicing command and process it by prefix option","description":"Optcmd is simple plugin, that allow you to call confirm() function for your own list of commands (btw, you can have as many lists as you need). After choosing command it will be processed depend on current prefix parameter.\r\n\r\nYou can also find it on https:\/\/github.com\/sergio-ivanuzzo\/optcmd","4":"Optcmd is simple plugin, that allow you to call confirm() function for your own list of commands (btw, you can have as many lists as you need). After choosing command it will be processed depend on current prefix parameter.\r\n\r\nYou can also find it on https:\/\/github.com\/sergio-ivanuzzo\/optcmd","install_details":"Install it using Vundle. Just add next lines to your .vimrc :\r\nPlugin 'sergio-ivanuzzo\/optcmd' \r\nthen run \r\nvim +PluginInstall +qall","5":"Install it using Vundle. Just add next lines to your .vimrc :\r\nPlugin 'sergio-ivanuzzo\/optcmd' \r\nthen run \r\nvim +PluginInstall +qall","first_name":"Sergio","6":"Sergio","last_name":"Ivanuzzo","7":"Ivanuzzo","releases":[{"0":"5276","vim_version":"7.0","1":"7.0","script_version":"1.0.2","2":"1.0.2","version_comment":"optimized prefixes","3":"optimized prefixes","package":"optcmd_1.0.2.tar.gz","4":"optcmd_1.0.2.tar.gz","src_id":"23766","5":"23766","creation_date":"1448793932","6":"1448793932"},{"0":"5276","vim_version":"7.0","1":"7.0","script_version":"1.0.1","2":"1.0.1","version_comment":"fixed bug, when script works if choice more than commands length and not works, if ESC pressed.","3":"fixed bug, when script works if choice more than commands length and not works, if ESC pressed.","package":"optcmd_1.0.1.tar.gz","4":"optcmd_1.0.1.tar.gz","src_id":"23764","5":"23764","creation_date":"1448725747","6":"1448725747"},{"0":"5276","vim_version":"7.0","1":"7.0","script_version":"1.0.0","2":"1.0.0","version_comment":"Initial upload","3":"Initial upload","package":"optcmd.tar.gz","4":"optcmd.tar.gz","src_id":"23763","5":"23763","creation_date":"1448707553","6":"1448707553"}]},"5275":{"script_id":"5275","0":"5275","script_name":"Delphi","1":"Delphi","script_type":"ftplugin","2":"ftplugin","summary":"Executes your python code as you write it","3":"Executes your python code as you write it","description":"https:\/\/github.com\/thethirduniverse\/delphi","4":"https:\/\/github.com\/thethirduniverse\/delphi","install_details":"","5":"","first_name":"Guanqing","6":"Guanqing","last_name":"Yan","7":"Yan","releases":[{"0":"5275","vim_version":"7.4","1":"7.4","script_version":"1","2":"1","version_comment":"Initial upload","3":"Initial upload","package":"delphi.tar.gz","4":"delphi.tar.gz","src_id":"23762","5":"23762","creation_date":"1448647560","6":"1448647560"}]},"5272":{"script_id":"5272","0":"5272","script_name":"Buffer Hint","1":"Buffer Hint","script_type":"utility","2":"utility","summary":"A handy buffer switcher","3":"A handy buffer switcher","description":"With this plugin, you can browse all buffers in a popup side window. In addition, this plugin provides a \"hint key\" for each buffer, just like what Vimperator\/Vimium\/VimFx does. Therefore, you can switch among buffers quickly with a single key stroke in the best case.\r\n\r\nProject Home Page: https:\/\/github.com\/bsdelf\/bufferhint","4":"With this plugin, you can browse all buffers in a popup side window. In addition, this plugin provides a \"hint key\" for each buffer, just like what Vimperator\/Vimium\/VimFx does. Therefore, you can switch among buffers quickly with a single key stroke in the best case.\r\n\r\nProject Home Page: https:\/\/github.com\/bsdelf\/bufferhint","install_details":"Install:\r\ncp bufferhint.vim ~\/.vim\/plugin\/\r\n\r\nConfigure:\r\nnnoremap - :call bufferhint#Popup()\r\nnnoremap \\ :call bufferhint#LoadPrevious()\r\n\r\nUse Case:\r\n1.\"vim 1.txt 2.txt 3.txt\"\r\n2.type \"-\" to popup buffer hints\r\n3.type \"a\"\/\"b\"\/\"c\" to switch to 1.txt\/2.txt\/3.txt correspondingly\r\n\r\nLatest recently used mode:\r\n4.type \"-\" to popup buffer hints\r\n5.type SPACE to switch to LRU mode","5":"Install:\r\ncp bufferhint.vim ~\/.vim\/plugin\/\r\n\r\nConfigure:\r\nnnoremap - :call bufferhint#Popup()\r\nnnoremap \\ :call bufferhint#LoadPrevious()\r\n\r\nUse Case:\r\n1.\"vim 1.txt 2.txt 3.txt\"\r\n2.type \"-\" to popup buffer hints\r\n3.type \"a\"\/\"b\"\/\"c\" to switch to 1.txt\/2.txt\/3.txt correspondingly\r\n\r\nLatest recently used mode:\r\n4.type \"-\" to popup buffer hints\r\n5.type SPACE to switch to LRU mode","first_name":"Yanhui","6":"Yanhui","last_name":"Shen","7":"Shen","releases":[{"0":"5272","vim_version":"7.0","1":"7.0","script_version":"1.1.1","2":"1.1.1","version_comment":"Fix LoadPrevious, thanks to Jianping Liu.","3":"Fix LoadPrevious, thanks to Jianping Liu.","package":"bufferhint.vim","4":"bufferhint.vim","src_id":"24670","5":"24670","creation_date":"1477458456","6":"1477458456"},{"0":"5272","vim_version":"7.0","1":"7.0","script_version":"1.1.0","2":"1.1.0","version_comment":"New Features:\r\nKeep window layout while deleting buffer (let g:bufferhint_KeepWindow = 1, default is 0)\r\n\r\nOther Enhancements:\r\nhttps:\/\/github.com\/bsdelf\/bufferhint\/pull\/1","3":"New Features:\r\nKeep window layout while deleting buffer (let g:bufferhint_KeepWindow = 1, default is 0)\r\n\r\nOther Enhancements:\r\nhttps:\/\/github.com\/bsdelf\/bufferhint\/pull\/1","package":"bufferhint.vim","4":"bufferhint.vim","src_id":"24146","5":"24146","creation_date":"1459265501","6":"1459265501"},{"0":"5272","vim_version":"7.0","1":"7.0","script_version":"1.0.1","2":"1.0.1","version_comment":"fix a bug in bufferhint#Popup()","3":"fix a bug in bufferhint#Popup()","package":"bufferhint.vim","4":"bufferhint.vim","src_id":"23776","5":"23776","creation_date":"1449398950","6":"1449398950"},{"0":"5272","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"bufferhint.vim","4":"bufferhint.vim","src_id":"23759","5":"23759","creation_date":"1448519242","6":"1448519242"}]},"5271":{"script_id":"5271","0":"5271","script_name":"EasyClipRing.vim","1":"EasyClipRing.vim","script_type":"utility","2":"utility","summary":"Autocomplete style vim pop-up menu for your registers.","3":"Autocomplete style vim pop-up menu for your registers.","description":"EasyClipRing.vim v1.2.1\r\nAutocomplete style vim pop-up menu for your registers. See screenshot in the Usage section.\r\n\r\nThis plugin requires vim-easyclip which requires vim-repeat\r\n\r\nSee README.md on https:\/\/github.com\/davidosomething\/EasyClipRing.vim","4":"EasyClipRing.vim v1.2.1\r\nAutocomplete style vim pop-up menu for your registers. See screenshot in the Usage section.\r\n\r\nThis plugin requires vim-easyclip which requires vim-repeat\r\n\r\nSee README.md on https:\/\/github.com\/davidosomething\/EasyClipRing.vim","install_details":"Installation\r\n\r\nYou can just drop this plugin into your .vim\/ dir. Make sure vim-repeat and vim-easyclip are also installed.\r\n\r\nI recommend using vim-plug in general:\r\n\r\ncall plug#begin()\r\n\r\nPlug 'tpope\/vim-repeat'\r\n      \\| Plug 'svermeulen\/vim-easyclip'\r\n      \\| Plug 'davidosomething\/EasyClipRing.vim'\r\n\r\ncall plug#end()\r\nNote the dependency scaffold there \u00e2\u0080\u0093 vim-easyclip integrates with vim-repeat, and EasyClipRing.vim uses vim-easyclip.\r\n\r\nUsage\r\n\r\nDefine a custom mapping like so:\r\n\r\nimap    gcr  (EasyClipRing)\r\n\r\nor for \r\n\r\nimap       (EasyClipRing)\r\nUse it in in insert mode to trigger the pop-up menu\r\n","5":"Installation\r\n\r\nYou can just drop this plugin into your .vim\/ dir. Make sure vim-repeat and vim-easyclip are also installed.\r\n\r\nI recommend using vim-plug in general:\r\n\r\ncall plug#begin()\r\n\r\nPlug 'tpope\/vim-repeat'\r\n      \\| Plug 'svermeulen\/vim-easyclip'\r\n      \\| Plug 'davidosomething\/EasyClipRing.vim'\r\n\r\ncall plug#end()\r\nNote the dependency scaffold there \u00e2\u0080\u0093 vim-easyclip integrates with vim-repeat, and EasyClipRing.vim uses vim-easyclip.\r\n\r\nUsage\r\n\r\nDefine a custom mapping like so:\r\n\r\nimap    gcr  (EasyClipRing)\r\n\r\nor for \r\n\r\nimap       (EasyClipRing)\r\nUse it in in insert mode to trigger the pop-up menu\r\n","first_name":"David","6":"David","last_name":"O'Trakoun","7":"O'Trakoun","releases":[{"0":"5271","vim_version":"7.4","1":"7.4","script_version":"1.2.1","2":"1.2.1","version_comment":"Initial upload","3":"Initial upload","package":"EasyClipRing.zip","4":"EasyClipRing.zip","src_id":"23742","5":"23742","creation_date":"1447977354","6":"1447977354"}]},"5270":{"script_id":"5270","0":"5270","script_name":"todo-vim","1":"todo-vim","script_type":"utility","2":"utility","summary":"todo-vim is plugin for manage your todo notes","3":"todo-vim is plugin for manage your todo notes","description":"todo-vim is plugin for manage your todo notes. He will help you to navigate and manage your todo labels in code. Plugin support next type of labels: todo, fixme, note. Label examples:\r\n\r\nTODO: Simple todo example\r\nTODO: todo with tag priority and custom tag @p :8 @custom :custom\r\nNOTE: Simple note example with tag @tag\r\n\r\nFEATURES\r\n\r\n  - Display todo labels in separate navigation window\r\n  - Sort labels by type, line, priority.\r\n  - Quick jump to label\r\n  - Autojumping when choosing\r\n  - Tags support\r\n\r\nMore info: https:\/\/github.com\/Dimercel\/todo-vim\r\n\r\n","4":"todo-vim is plugin for manage your todo notes. He will help you to navigate and manage your todo labels in code. Plugin support next type of labels: todo, fixme, note. Label examples:\r\n\r\nTODO: Simple todo example\r\nTODO: todo with tag priority and custom tag @p :8 @custom :custom\r\nNOTE: Simple note example with tag @tag\r\n\r\nFEATURES\r\n\r\n  - Display todo labels in separate navigation window\r\n  - Sort labels by type, line, priority.\r\n  - Quick jump to label\r\n  - Autojumping when choosing\r\n  - Tags support\r\n\r\nMore info: https:\/\/github.com\/Dimercel\/todo-vim\r\n\r\n","install_details":"Install the distributed files into your Vim script directory which is usually\r\n~\/.vim\/. You should consider to use one of the famous package managers for Vim\r\nlike vundle or neobundle to install the plugin.\r\n\r\nAfter installation you can run todo-vim with the :TODOOpen or :TODOToggle\r\ncommands.","5":"Install the distributed files into your Vim script directory which is usually\r\n~\/.vim\/. You should consider to use one of the famous package managers for Vim\r\nlike vundle or neobundle to install the plugin.\r\n\r\nAfter installation you can run todo-vim with the :TODOOpen or :TODOToggle\r\ncommands.","first_name":"Dimercel","6":"Dimercel","last_name":"Ito","7":"Ito","releases":[{"0":"5270","vim_version":"7.0","1":"7.0","script_version":"0.3.1","2":"0.3.1","version_comment":"Fixed serious bug with the label search process. Thanks to @progrunner17 for the bug report!","3":"Fixed serious bug with the label search process. Thanks to @progrunner17 for the bug report!","package":"todo-vim-0.3.1.zip","4":"todo-vim-0.3.1.zip","src_id":"27110","5":"27110","creation_date":"1586377488","6":"1586377488"},{"0":"5270","vim_version":"7.0","1":"7.0","script_version":"0.3","2":"0.3","version_comment":"Fixed bugs","3":"Fixed bugs","package":"todo-vim-0.3.tar.gz","4":"todo-vim-0.3.tar.gz","src_id":"26353","5":"26353","creation_date":"1547756350","6":"1547756350"},{"0":"5270","vim_version":"7.0","1":"7.0","script_version":"0.2.0","2":"0.2.0","version_comment":"Initial upload","3":"Initial upload","package":"todo-vim-0.2.0.tar.gz","4":"todo-vim-0.2.0.tar.gz","src_id":"23741","5":"23741","creation_date":"1447924418","6":"1447924418"}]},"5269":{"script_id":"5269","0":"5269","script_name":"Nette","1":"Nette","script_type":"utility","2":"utility","summary":"Plugin for Nette Framework; syntax, indent","3":"Plugin for Nette Framework; syntax, indent","description":"GitHub: https:\/\/github.com\/fpob\/nette.vim\r\n\r\nVim plugin for Nette Framework (https:\/\/github.com\/nette\/nette).\r\n\r\nFeatures\r\n--------\r\n\r\n* Syntax highlight and indentation for NEON (https:\/\/github.com\/nette\/neon)\r\n* Syntax highlight for Latte (https:\/\/github.com\/nette\/latte)\r\n* Indentation check in NEON files - command `NetteNeonCheck`. Calls every time when file is saved.","4":"GitHub: https:\/\/github.com\/fpob\/nette.vim\r\n\r\nVim plugin for Nette Framework (https:\/\/github.com\/nette\/nette).\r\n\r\nFeatures\r\n--------\r\n\r\n* Syntax highlight and indentation for NEON (https:\/\/github.com\/nette\/neon)\r\n* Syntax highlight for Latte (https:\/\/github.com\/nette\/latte)\r\n* Indentation check in NEON files - command `NetteNeonCheck`. Calls every time when file is saved.","install_details":"Use pathogen (https:\/\/github.com\/tpope\/vim-pathogen)!\r\n\r\ncd ~\/.vim\/bundle\r\ngit clone https:\/\/github.com\/fpob\/nette.vim.git","5":"Use pathogen (https:\/\/github.com\/tpope\/vim-pathogen)!\r\n\r\ncd ~\/.vim\/bundle\r\ngit clone https:\/\/github.com\/fpob\/nette.vim.git","first_name":"Filip","6":"Filip","last_name":"Pobo\u0159il","7":"Pobořil","releases":[{"0":"5269","vim_version":"7.0","1":"7.0","script_version":"0.1.2","2":"0.1.2","version_comment":"* neon: dash in neonStructure\r\n* removed snipptes\r\n* latte: syntax highlight improvements","3":"* neon: dash in neonStructure\r\n* removed snipptes\r\n* latte: syntax highlight improvements","package":"nette.tar","4":"nette.tar","src_id":"24201","5":"24201","creation_date":"1461588380","6":"1461588380"},{"0":"5269","vim_version":"7.0","1":"7.0","script_version":"0.1.1","2":"0.1.1","version_comment":"* Fixed php snippets\r\n* Fixed indent\r\n* Fixed highlighting numbers in neon files","3":"* Fixed php snippets\r\n* Fixed indent\r\n* Fixed highlighting numbers in neon files","package":"nette.tar","4":"nette.tar","src_id":"23738","5":"23738","creation_date":"1447719468","6":"1447719468"},{"0":"5269","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"nette.tar","4":"nette.tar","src_id":"23735","5":"23735","creation_date":"1447545493","6":"1447545493"}]},"5268":{"script_id":"5268","0":"5268","script_name":"fountainflow.vim","1":"fountainflow.vim","script_type":"utility","2":"utility","summary":"Convert Fountain screenplay files to HTML and LibreOffice","3":"Convert Fountain screenplay files to HTML and LibreOffice","description":"The command :FountainFlow (or :FF) converts properly configured Fountain screenplay files into HTML compatible with LibreOffice.\r\n\r\nAfter conversion, tap  and the HTML becomes a fully formatted screenplay in LibreOffice.\r\n\r\nFinish by loading page styles from an included template, which will start proper page numbering on page 2 of the script, while skipping over a title page and optional synopsis.\r\n\r\nFully configurable. Builds list from title page info, which can be arranged through a template.\r\n\r\nExample output, Big Fish regenerated from sample Fountain file:\r\nhttps:\/\/drive.google.com\/file\/d\/0B1MbU4xaq48DRWxPeW92bm5XV2M\/view?usp=sharing\r\n\r\nAll Fountain syntax supported, with just one limitation on dual dialogue (one line of dialogue per character). See http:\/\/fountain.io\/syntax\r\n\r\n=============================================================\r\n\r\nThere is much I need to tell you that's not in the included documentation, yet.\r\n\r\nHow title page data works in Fountain Flow\r\nhttp:\/\/vimwriter.blogspot.com\/2015\/11\/how-title-page-data-works-in-fountain.html\r\n\r\nPage numbering with Fountain Flow\r\nhttp:\/\/vimwriter.blogspot.com\/2015\/11\/page-numbering-with-fountain-flow.html\r\n\r\n=============================================================","4":"The command :FountainFlow (or :FF) converts properly configured Fountain screenplay files into HTML compatible with LibreOffice.\r\n\r\nAfter conversion, tap  and the HTML becomes a fully formatted screenplay in LibreOffice.\r\n\r\nFinish by loading page styles from an included template, which will start proper page numbering on page 2 of the script, while skipping over a title page and optional synopsis.\r\n\r\nFully configurable. Builds list from title page info, which can be arranged through a template.\r\n\r\nExample output, Big Fish regenerated from sample Fountain file:\r\nhttps:\/\/drive.google.com\/file\/d\/0B1MbU4xaq48DRWxPeW92bm5XV2M\/view?usp=sharing\r\n\r\nAll Fountain syntax supported, with just one limitation on dual dialogue (one line of dialogue per character). See http:\/\/fountain.io\/syntax\r\n\r\n=============================================================\r\n\r\nThere is much I need to tell you that's not in the included documentation, yet.\r\n\r\nHow title page data works in Fountain Flow\r\nhttp:\/\/vimwriter.blogspot.com\/2015\/11\/how-title-page-data-works-in-fountain.html\r\n\r\nPage numbering with Fountain Flow\r\nhttp:\/\/vimwriter.blogspot.com\/2015\/11\/page-numbering-with-fountain-flow.html\r\n\r\n=============================================================","install_details":"After unzipping the file, drop the plugin and the help file into their respective folders (plugin and doc).\r\n\r\nFolders containing templates can be put anywhere, as long as the settings are adjusted to reflect their location.\r\n\r\nThe script relies entirely on Vimscript and regex, so there should not be any issues with different platforms and configurations.","5":"After unzipping the file, drop the plugin and the help file into their respective folders (plugin and doc).\r\n\r\nFolders containing templates can be put anywhere, as long as the settings are adjusted to reflect their location.\r\n\r\nThe script relies entirely on Vimscript and regex, so there should not be any issues with different platforms and configurations.","first_name":"Saeger","6":"Saeger","last_name":"Ryman","7":"Ryman","releases":[{"0":"5268","vim_version":"7.4","1":"7.4","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"vimflow.tar.gz","4":"vimflow.tar.gz","src_id":"23729","5":"23729","creation_date":"1447240955","6":"1447240955"}]},"5267":{"script_id":"5267","0":"5267","script_name":"simple_playground.vim","1":"simple_playground.vim","script_type":"utility","2":"utility","summary":"make vim be language playgrounds","3":"make vim be language playgrounds","description":"Simple Playground is a vim plugin that insert the script's output in the current file in comment format after you write\/save the file. It works in case one script line produce one output line. ****loop print is not working now\r\n\r\nAim to reduce time of learning new script or programming language.*\r\n","4":"Simple Playground is a vim plugin that insert the script's output in the current file in comment format after you write\/save the file. It works in case one script line produce one output line. ****loop print is not working now\r\n\r\nAim to reduce time of learning new script or programming language.*\r\n","install_details":"Install\r\ncopy simply_playground.vim to ~\/.vim\/plugin\r\nand then\r\n\r\ndefine patterns in a function by calling `BuildPlayground(execute_command, comment_pattern, print_pattern)` in `~\/.vimrc`\r\n\r\nmore details\r\nhttps:\/\/github.com\/jingz\/simple_playground","5":"Install\r\ncopy simply_playground.vim to ~\/.vim\/plugin\r\nand then\r\n\r\ndefine patterns in a function by calling `BuildPlayground(execute_command, comment_pattern, print_pattern)` in `~\/.vimrc`\r\n\r\nmore details\r\nhttps:\/\/github.com\/jingz\/simple_playground","first_name":"Sarunyoo","6":"Sarunyoo","last_name":"Chobpanich","7":"Chobpanich","releases":[{"0":"5267","vim_version":"7.0","1":"7.0","script_version":"0.1.0","2":"0.1.0","version_comment":"Initial upload","3":"Initial upload","package":"simple_playground.tar.gz","4":"simple_playground.tar.gz","src_id":"23727","5":"23727","creation_date":"1447213545","6":"1447213545"}]},"5266":{"script_id":"5266","0":"5266","script_name":"vim-maildrop","1":"vim-maildrop","script_type":"syntax","2":"syntax","summary":"Syntax highlighting for Courier maildrop filters","3":"Syntax highlighting for Courier maildrop filters","description":"Adds basic syntax highlighting for the courier maildrop filter language. A filetype plugin to auto-enable syntax highlighting is also included.\r\n\r\nGrammar based on the official reference doc: http:\/\/www.courier-mta.org\/maildropfilter.html\r\n\r\nGithub project: https:\/\/github.com\/sirtaj\/vim-maildrop\r\n\r\nPlease report any issues, suggestions or patches via the github project.\r\nNote that the version here on vim.org may lag a bit behind the dev version on github.","4":"Adds basic syntax highlighting for the courier maildrop filter language. A filetype plugin to auto-enable syntax highlighting is also included.\r\n\r\nGrammar based on the official reference doc: http:\/\/www.courier-mta.org\/maildropfilter.html\r\n\r\nGithub project: https:\/\/github.com\/sirtaj\/vim-maildrop\r\n\r\nPlease report any issues, suggestions or patches via the github project.\r\nNote that the version here on vim.org may lag a bit behind the dev version on github.","install_details":"Archive is compatible with direct extraction to .vim, and tools such as pathogen and vundle.","5":"Archive is compatible with direct extraction to .vim, and tools such as pathogen and vundle.","first_name":"Sirtaj","6":"Sirtaj","last_name":"Singh Kang","7":"Singh Kang","releases":[{"0":"5266","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"vim-maildrop-1.0.tar.gz","4":"vim-maildrop-1.0.tar.gz","src_id":"23726","5":"23726","creation_date":"1447151858","6":"1447151858"}]},"5265":{"script_id":"5265","0":"5265","script_name":"wimproved.vim","1":"wimproved.vim","script_type":"utility","2":"utility","summary":"Better fullscreen and more on Windows.","3":"Better fullscreen and more on Windows.","description":"An effort to create a better editing experience for Vim on Windows.\r\nSupports full-screen while taking care to fix visual glitches seen in\r\nother plugins.\r\n\r\nSee https:\/\/github.com\/kkoenig\/wimproved.vim#readme","4":"An effort to create a better editing experience for Vim on Windows.\r\nSupports full-screen while taking care to fix visual glitches seen in\r\nother plugins.\r\n\r\nSee https:\/\/github.com\/kkoenig\/wimproved.vim#readme","install_details":"Extract in ~\/.vim (~\\vimfiles on Windows).\r\n\r\nSee https:\/\/github.com\/kkoenig\/wimproved.vim#readme","5":"Extract in ~\/.vim (~\\vimfiles on Windows).\r\n\r\nSee https:\/\/github.com\/kkoenig\/wimproved.vim#readme","first_name":"Killian","6":"Killian","last_name":"Koenig","7":"Koenig","releases":[{"0":"5265","vim_version":"7.0","1":"7.0","script_version":"0.2.0","2":"0.2.0","version_comment":"- Fixed numerous visual glitches\r\n- Added 64-bit support\r\n- Include native dlls in release\r\n- Automated regression tests with CI","3":"- Fixed numerous visual glitches\r\n- Added 64-bit support\r\n- Include native dlls in release\r\n- Automated regression tests with CI","package":"wimproved.vim-0.2.0.tar","4":"wimproved.vim-0.2.0.tar","src_id":"23736","5":"23736","creation_date":"1447559622","6":"1447559622"},{"0":"5265","vim_version":"7.0","1":"7.0","script_version":"0.1.0","2":"0.1.0","version_comment":"Initial upload","3":"Initial upload","package":"wimproved.vim-0.1.0.tar.gz","4":"wimproved.vim-0.1.0.tar.gz","src_id":"23711","5":"23711","creation_date":"1446753930","6":"1446753930"}]},"5264":{"script_id":"5264","0":"5264","script_name":"vim-abbrev-matcher","1":"vim-abbrev-matcher","script_type":"utility","2":"utility","summary":"Abbreviation matcher plugin to be used with CtrlP and Unite","3":"Abbreviation matcher plugin to be used with CtrlP and Unite","description":"Unlike \"traditional\" fuzzy search it matches by beginnings of words. For example, \"fb\" matches \"foo_bar\" but not \"if_bar\". Words considered are groups of alphabetic characters, groups of digits and \"CamelCase\" words. All other symbols, including underscore (_) and dash (-) are word separators.\r\n\r\nThis allows faster narrowing of search results to a needed candidate, with less typing.\r\n\r\nMore detailed README and recent version: https:\/\/github.com\/sergei-dyshel\/vim-abbrev-matcher","4":"Unlike \"traditional\" fuzzy search it matches by beginnings of words. For example, \"fb\" matches \"foo_bar\" but not \"if_bar\". Words considered are groups of alphabetic characters, groups of digits and \"CamelCase\" words. All other symbols, including underscore (_) and dash (-) are word separators.\r\n\r\nThis allows faster narrowing of search results to a needed candidate, with less typing.\r\n\r\nMore detailed README and recent version: https:\/\/github.com\/sergei-dyshel\/vim-abbrev-matcher","install_details":"Just unzip into \"~\/.vim\" or any other directory in \"runtimepath\".","5":"Just unzip into \"~\/.vim\" or any other directory in \"runtimepath\".","first_name":"Sergei","6":"Sergei","last_name":"Dyshel","7":"Dyshel","releases":[{"0":"5264","vim_version":"7.3","1":"7.3","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"vim-abbrev-matcher.zip","4":"vim-abbrev-matcher.zip","src_id":"23705","5":"23705","creation_date":"1446408565","6":"1446408565"}]},"5263":{"script_id":"5263","0":"5263","script_name":"Never Optimal Wiki","1":"Never Optimal Wiki","script_type":"utility","2":"utility","summary":"a minimalistic pure vim personal wiki","3":"a minimalistic pure vim personal wiki","description":"Git repository: https:\/\/github.com\/Dalker\/vim-now\r\nNote: a proper help file has been included since version 0.5. Reach it with ':help now'\r\n\r\nRationale:  after having tried several wiki vim plugins and several personal wiki workflows, the author realized that:\r\n                 a) full 'wiki' plugins tend to have too many features and impose too many conventions on the user\r\n                 b) no personal note-taking workflow is ever optimal (\"never optimal\")\r\n                 c) to actually get something written or done, you have to do it NOW (on a Never Optimal Wiki)\r\n\r\nFeatures: \r\n - From anywhere within vim: ( means ) - all global keymaps can be easily overridden (see configuration at bottom of page)\r\n    nn  updates and enters root Never Optimal Wiki index\r\n    ni   updates and enters current dir's Never Optimal Wiki index\r\n    nr  creates new random note (in a predefined 'in' dir)\r\n\r\n -  Within a NOW buffer: ( means )\r\n    gf        open dir or file under cursor, adding suffix if needed (vim standard)\r\n    Ctrl-O go back to previous location (vim standard)\r\n    cf  create file or dir under cursor,  adding suffix if needed\r\n    gf  open under cursor with external program, which must be properly declared (see configuration at bottom of page)\r\n                the defaults are 'firefox' for urls and 'mimeopen' for anything else, which should work well in a Linux environment\r\n         overhauled gf: decides whether to act as gf, gf or cf (can be turned off to recover default  functionality)\r\n     -          go up to either dir's index.now file or to a netrw view of current directory\r\n    n    interactively (re)name a (random note) file in place\r\n    c    interactively classify (move) a file somewhere else, keeping the same name\r\n    s    copy current file to shadow dir, prepending date to name (to keep a historical log of notes)\r\n\r\n - Minimal syntax highliting:\r\n   .\/...    link to another file\r\n   =...=  emphasized text (meant for 'titles')\r\n   *...*   emphasized text (meant for everything else)\r\n\r\nPossible usage:\r\n   - dump anything from the mind into a random note ( with nr from anywhere on vim)\r\n   - occasionally 'process' notes by naming them and placing them somewhere on the directory tree (with n and c)\r\n   - shadow some notes, notably personal writing, to keep a historical log - usually right after naming them (with s)\r\n\r\nPossible directory tree (besides in\/ and shadow\/ or equivalent):\r\n   - a 'circulating' dir with subdirs to help temporary notes blend together into something\r\n   - a 'lifehack' dir to contain long-term lifehacking tips\r\n   - a 'quotes' dir to contain notes which carry book quotes, based on post-its glued while reading one\r\n   - etc...\r\n\r\n  This could result in the a dir structure similar to the following:\r\n  now\/---- in\/ ---- random01.now\r\n       |        |-- random02.now\r\n       |        |-- (...)\r\n       |        \\-- random15.now\r\n       |-- shadow\/ -- (...)\r\n       |-- circulating\/ ---- thinking_about_A\/ -- (...)  \r\n       |                 |-- (...)\r\n       |                 \\-- thinking_about_Z\/ -- (...)\r\n       |-- lifehack\/\r\n       |-- quotes\/ \r\n       \\-- (...)\r\n","4":"Git repository: https:\/\/github.com\/Dalker\/vim-now\r\nNote: a proper help file has been included since version 0.5. Reach it with ':help now'\r\n\r\nRationale:  after having tried several wiki vim plugins and several personal wiki workflows, the author realized that:\r\n                 a) full 'wiki' plugins tend to have too many features and impose too many conventions on the user\r\n                 b) no personal note-taking workflow is ever optimal (\"never optimal\")\r\n                 c) to actually get something written or done, you have to do it NOW (on a Never Optimal Wiki)\r\n\r\nFeatures: \r\n - From anywhere within vim: ( means ) - all global keymaps can be easily overridden (see configuration at bottom of page)\r\n    nn  updates and enters root Never Optimal Wiki index\r\n    ni   updates and enters current dir's Never Optimal Wiki index\r\n    nr  creates new random note (in a predefined 'in' dir)\r\n\r\n -  Within a NOW buffer: ( means )\r\n    gf        open dir or file under cursor, adding suffix if needed (vim standard)\r\n    Ctrl-O go back to previous location (vim standard)\r\n    cf  create file or dir under cursor,  adding suffix if needed\r\n    gf  open under cursor with external program, which must be properly declared (see configuration at bottom of page)\r\n                the defaults are 'firefox' for urls and 'mimeopen' for anything else, which should work well in a Linux environment\r\n         overhauled gf: decides whether to act as gf, gf or cf (can be turned off to recover default  functionality)\r\n     -          go up to either dir's index.now file or to a netrw view of current directory\r\n    n    interactively (re)name a (random note) file in place\r\n    c    interactively classify (move) a file somewhere else, keeping the same name\r\n    s    copy current file to shadow dir, prepending date to name (to keep a historical log of notes)\r\n\r\n - Minimal syntax highliting:\r\n   .\/...    link to another file\r\n   =...=  emphasized text (meant for 'titles')\r\n   *...*   emphasized text (meant for everything else)\r\n\r\nPossible usage:\r\n   - dump anything from the mind into a random note ( with nr from anywhere on vim)\r\n   - occasionally 'process' notes by naming them and placing them somewhere on the directory tree (with n and c)\r\n   - shadow some notes, notably personal writing, to keep a historical log - usually right after naming them (with s)\r\n\r\nPossible directory tree (besides in\/ and shadow\/ or equivalent):\r\n   - a 'circulating' dir with subdirs to help temporary notes blend together into something\r\n   - a 'lifehack' dir to contain long-term lifehacking tips\r\n   - a 'quotes' dir to contain notes which carry book quotes, based on post-its glued while reading one\r\n   - etc...\r\n\r\n  This could result in the a dir structure similar to the following:\r\n  now\/---- in\/ ---- random01.now\r\n       |        |-- random02.now\r\n       |        |-- (...)\r\n       |        \\-- random15.now\r\n       |-- shadow\/ -- (...)\r\n       |-- circulating\/ ---- thinking_about_A\/ -- (...)  \r\n       |                 |-- (...)\r\n       |                 \\-- thinking_about_Z\/ -- (...)\r\n       |-- lifehack\/\r\n       |-- quotes\/ \r\n       \\-- (...)\r\n","install_details":"It is recommended to decompress the tarball as a pathogen vimscript #2332 'bundle' directory or similar, e.g.:\r\n> cd ~\/.vim\/bundle\r\n> tar xfz \/tmp\/vim-now.tgz\r\n\r\nConfiguration:\r\n -  User is expected to have  and  already setup (in .vimrc)\r\n -  Several paths, etc... may be optionally customized in .vimrc, as explained at the top of plugin\/now.vim file\r\n    Most probably the single option that will need to be set by the user is the root dir of the never optimal wiki:\r\n    > let g:NOW_rootdir = $HOME .  '\/location\/of\/rootdir\/'","5":"It is recommended to decompress the tarball as a pathogen vimscript #2332 'bundle' directory or similar, e.g.:\r\n> cd ~\/.vim\/bundle\r\n> tar xfz \/tmp\/vim-now.tgz\r\n\r\nConfiguration:\r\n -  User is expected to have  and  already setup (in .vimrc)\r\n -  Several paths, etc... may be optionally customized in .vimrc, as explained at the top of plugin\/now.vim file\r\n    Most probably the single option that will need to be set by the user is the root dir of the never optimal wiki:\r\n    > let g:NOW_rootdir = $HOME .  '\/location\/of\/rootdir\/'","first_name":"Dalker","6":"Dalker","last_name":".","7":".","releases":[{"0":"5263","vim_version":"7.0","1":"7.0","script_version":"0.7","2":"0.7","version_comment":"- added keybindings\/functions for title level increasing and decreasing\r\n (default: t and T)\r\n- several minor bug fixes\r\n- minor improvements to documentation","3":"- added keybindings\/functions for title level increasing and decreasing\r\n (default: t and T)\r\n- several minor bug fixes\r\n- minor improvements to documentation","package":"vim-now.tgz","4":"vim-now.tgz","src_id":"25493","5":"25493","creation_date":"1502349909","6":"1502349909"},{"0":"5263","vim_version":"7.0","1":"7.0","script_version":"6.0","2":"6.0","version_comment":"Overhauled  key while in now buffer. Word under cursor is now first verified to be a directory to enter, then an URL to browse, then having a configured suffix to open externally, then to exist with some vim-recognized suffix to open internally and finally, if all else fails, to create adding a now suffix.","3":"Overhauled  key while in now buffer. Word under cursor is now first verified to be a directory to enter, then an URL to browse, then having a configured suffix to open externally, then to exist with some vim-recognized suffix to open internally and finally, if all else fails, to create adding a now suffix.","package":"vim-now.tgz","4":"vim-now.tgz","src_id":"24591","5":"24591","creation_date":"1475871423","6":"1475871423"},{"0":"5263","vim_version":"7.0","1":"7.0","script_version":"0.5.1","2":"0.5.1","version_comment":"bug fix:  debugged auto-closing of shadow buffer upon creation","3":"bug fix:  debugged auto-closing of shadow buffer upon creation","package":"vim-now.tgz","4":"vim-now.tgz","src_id":"23929","5":"23929","creation_date":"1453150723","6":"1453150723"},{"0":"5263","vim_version":"7.0","1":"7.0","script_version":"0.5","2":"0.5","version_comment":"- First version with full documentation included (:help now)","3":"- First version with full documentation included (:help now)","package":"vim-now.tgz","4":"vim-now.tgz","src_id":"23911","5":"23911","creation_date":"1452896877","6":"1452896877"},{"0":"5263","vim_version":"7.0","1":"7.0","script_version":"0.4.1","2":"0.4.1","version_comment":"bug fixes: - got rid of little bug introduced in 0.4 when moving up from file in dir without index.now file\r\n                  - the new autoload\/ dir had been ommitted from the tgz, rendering realease 0.4 useless... :-(","3":"bug fixes: - got rid of little bug introduced in 0.4 when moving up from file in dir without index.now file\r\n                  - the new autoload\/ dir had been ommitted from the tgz, rendering realease 0.4 useless... :-(","package":"vim-now.tgz","4":"vim-now.tgz","src_id":"23778","5":"23778","creation_date":"1449402906","6":"1449402906"},{"0":"5263","vim_version":"7.0","1":"7.0","script_version":"0.4","2":"0.4","version_comment":"- user can now make index in local dir (default keymap: nk)\r\n- navigation with - now moves up to next index if available, updating it with list of new files if necessary\r\n- folding implemented, based on 'titles' and 'subtitles'\r\n","3":"- user can now make index in local dir (default keymap: nk)\r\n- navigation with - now moves up to next index if available, updating it with list of new files if necessary\r\n- folding implemented, based on 'titles' and 'subtitles'\r\n","package":"vim-now.tgz","4":"vim-now.tgz","src_id":"23721","5":"23721","creation_date":"1447016962","6":"1447016962"},{"0":"5263","vim_version":"7.0","1":"7.0","script_version":"0.3.1","2":"0.3.1","version_comment":"- correct bug introduced in 0.3: vim's isdirectory() doesn't understand ~, so substitute by full $HOME path when necessary","3":"- correct bug introduced in 0.3: vim's isdirectory() doesn't understand ~, so substitute by full $HOME path when necessary","package":"vim-now.tgz","4":"vim-now.tgz","src_id":"23717","5":"23717","creation_date":"1446916027","6":"1446916027"},{"0":"5263","vim_version":"7.0","1":"7.0","script_version":"0.3","2":"0.3","version_comment":"- make random note and shadow necessarily subdirs of root path; this limits freedom of choice a bit, but ensures that changing a single configuration variable - the root dir - gives access to a different 'instance' of the Never Optimal Wiki\r\n- when going to index or random note, create dir if it doesn't exist yet (fundamental for new users and when setting up different root dir)","3":"- make random note and shadow necessarily subdirs of root path; this limits freedom of choice a bit, but ensures that changing a single configuration variable - the root dir - gives access to a different 'instance' of the Never Optimal Wiki\r\n- when going to index or random note, create dir if it doesn't exist yet (fundamental for new users and when setting up different root dir)","package":"vim-now.tgz","4":"vim-now.tgz","src_id":"23716","5":"23716","creation_date":"1446903257","6":"1446903257"},{"0":"5263","vim_version":"7.0","1":"7.0","script_version":"0.2","2":"0.2","version_comment":"- naming and moving notes now based on vim builtin rename(), much safer than calling external commands\r\n- classify() can now create dir on the fly if necessary (asking for confirmation first)\r\n- global options now handled in a new way that facilitates user configuration","3":"- naming and moving notes now based on vim builtin rename(), much safer than calling external commands\r\n- classify() can now create dir on the fly if necessary (asking for confirmation first)\r\n- global options now handled in a new way that facilitates user configuration","package":"vim-now.tgz","4":"vim-now.tgz","src_id":"23715","5":"23715","creation_date":"1446897181","6":"1446897181"},{"0":"5263","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"working version - but be careful with lack of safeguards when renaming \/ moving notes (it should work when used as intended)","3":"working version - but be careful with lack of safeguards when renaming \/ moving notes (it should work when used as intended)","package":"vim-now.tgz","4":"vim-now.tgz","src_id":"23712","5":"23712","creation_date":"1446798437","6":"1446798437"}]},"5262":{"script_id":"5262","0":"5262","script_name":"ttodo","1":"ttodo","script_type":"utility","2":"utility","summary":"Edit, view, sort, and filter todo.txt files","3":"Edit, view, sort, and filter todo.txt files","description":"This plugin provides the |:Ttodo| command that allow easy filtering and viewing \r\nof todo.txt files (see http:\/\/todotxt.com) via |tlib#input#List()|. The plugin \r\nsupports:\r\n\r\n    - search across multiple todo.txt files\r\n    - filter tasks with specific tags, lists etc.\r\n    - subtasks (outlines of complex tasks)\r\n    - hide tasks until a threshold date\r\n    - recurring tasks.\r\n\r\nExamples: >\r\n\r\n    \" Show all tasks; default map (|g:ttodo_nmap|): 1\r\n    :Ttodo\r\n\r\n    \" Show important tasks; default map (|g:ttodo_nmap_important|): !\r\n    :Ttodo!\r\n\r\n    \" Show tasks that are due in the next two weeks\r\n    :Ttodo --due=2w\r\n\r\n    \" Show tasks with priorities A to C\r\n    :Ttodo --pri=A-C\r\n\r\n    \" Show tasks matching @Test\r\n    :Ttodo @Test\r\n\r\n    \" By default, |:Ttodo| scans the todo.txt files in |g:ttodo#dirs|. Users \r\n    \" can also scan loaded buffers.\r\n    \" Show tasks in the current buffer\r\n    :Ttodo --bufname=%\r\n\r\n    \" Command-line options can be collected in preference sets (see \r\n    \" |g:ttodo#prefs|)\r\n    :Ttodo --pref=work\r\n\r\nIn order to use this plugin as a ftplugin, users might also want to set \r\n|g:ttodo_enable_ftdetect| to 1 in their |vimrc| file.\r\n\r\nIf filetype is ttodo, the following default keymaps are enabled:\r\n\r\n     ................. Add a new task;\r\n                           if |g:ttodo#ftplugin#add_at_eof| is true, add the \r\n                           task at the end of file\r\n     ............... Add a new task; copy any list and tags from the \r\n                           current task;\r\n                           if |g:ttodo#ftplugin#add_at_eof| is true, add the \r\n                           task at the end of file\r\n     ............... Add a new subtask\r\n    tx ...... Mark \"done\"\r\n    td ...... Mark due in N days\r\n    tw ...... Mark due in N weeks\r\n    tm ...... Mark due in N months\r\n    ty ...... Set priority\r\n    ta ...... Archive completed items\r\n    tb ...... View, filter items in the current buffer\r\n    tn ...... Add a note (the filename uses the first @list tag)\r\n    ti ...... Add a hopefully unique ID (an Adler32 hash)\r\n\r\nIf filetype is ttodo, the following commands are supported:\r\n\r\n    |:Ttodoarchive| ...... Archive completed tasks in the current buffer\r\n    |:Ttodobuffer| ....... Show tasks in the current buffer only\r\n    |:Ttodonote| ......... Add a new note to the task at the cursor\r\n    |:Ttodosort| ......... Sort the tasks in the current buffer\r\n\r\nAs a ftplugin, ttodo supports the following syntax\/extensions to todo.txt (see \r\nalso https:\/\/github.com\/ginatrapani\/todo.txt-cli\/wiki\/The-Todo.txt-Format):\r\n\r\n    (A) DATE TASK .... A priority as upper case letter (at the beginning of the \r\n                       line)\r\n    DATE TASK ........ A pending task\r\n    x DATE DATE TASK . A completed task (with completion date)\r\n    indented tasks ... A indented task is a subtask of the parent task; unless \r\n                       `has_subtasks` is true, |:Ttodo| will only show tasks \r\n                       with no open subtasks; this is similar to how the \r\n                       outline addon handles subtasks (see also \r\n                       https:\/\/github.com\/samuelsnyder\/outline-todo.txt)\r\n\r\nA TASK may contain the following tags:\r\n\r\n    @list ............ a \"list\" tag\r\n    +keyword ......... a \"keyword\" tag\r\n    h:1 .............. hidden task\r\n    due:YYYY-MM-DD ... due dates\r\n    rec:+Nx .......... When marking a task a \"done\", add a new task with a due \r\n                       date in N d(ays), w(eeks), m(onths), y(ears); with the \r\n                       leading '+' use the original due date; else use the \r\n                       completion date; this is similar to how the Simpletask \r\n                       Android app handles `rec` tags\r\n    t:YYYY-MM-DD ..... Hide the tasks until the given date\r\n    t:-Nd ............ Hide the tasks until N days before the due date\r\n\r\nOther ftplugin for todo.txt files, which can be used in conjunction with the \r\nttodo plugin (if you don't want to use it's |ftplugin|), include:\r\n\r\n    - https:\/\/github.com\/freitass\/todo.txt-vim\r\n        - todo-txt.vim : Vim plugin for Todo.txt \r\n          https:\/\/github.com\/dbeniamine\/todo.txt-vim or\r\n          http:\/\/www.vim.org\/scripts\/script.php?script_id=5134\r\n    - https:\/\/github.com\/mivok\/vimtodo or\r\n      http:\/\/www.vim.org\/scripts\/script.php?script_id=3264\r\n    - https:\/\/github.com\/davidoc\/todo.txt-vim\r\n        - My fork: https:\/\/github.com\/tomtom\/todo.txt-vim-1\r\n    - https:\/\/github.com\/dsiroky\/vim-todotxt\r\n    - ...\r\n\r\nRelated work:\r\n    - https:\/\/github.com\/elentok\/todo.vim\r\n","4":"This plugin provides the |:Ttodo| command that allow easy filtering and viewing \r\nof todo.txt files (see http:\/\/todotxt.com) via |tlib#input#List()|. The plugin \r\nsupports:\r\n\r\n    - search across multiple todo.txt files\r\n    - filter tasks with specific tags, lists etc.\r\n    - subtasks (outlines of complex tasks)\r\n    - hide tasks until a threshold date\r\n    - recurring tasks.\r\n\r\nExamples: >\r\n\r\n    \" Show all tasks; default map (|g:ttodo_nmap|): 1\r\n    :Ttodo\r\n\r\n    \" Show important tasks; default map (|g:ttodo_nmap_important|): !\r\n    :Ttodo!\r\n\r\n    \" Show tasks that are due in the next two weeks\r\n    :Ttodo --due=2w\r\n\r\n    \" Show tasks with priorities A to C\r\n    :Ttodo --pri=A-C\r\n\r\n    \" Show tasks matching @Test\r\n    :Ttodo @Test\r\n\r\n    \" By default, |:Ttodo| scans the todo.txt files in |g:ttodo#dirs|. Users \r\n    \" can also scan loaded buffers.\r\n    \" Show tasks in the current buffer\r\n    :Ttodo --bufname=%\r\n\r\n    \" Command-line options can be collected in preference sets (see \r\n    \" |g:ttodo#prefs|)\r\n    :Ttodo --pref=work\r\n\r\nIn order to use this plugin as a ftplugin, users might also want to set \r\n|g:ttodo_enable_ftdetect| to 1 in their |vimrc| file.\r\n\r\nIf filetype is ttodo, the following default keymaps are enabled:\r\n\r\n     ................. Add a new task;\r\n                           if |g:ttodo#ftplugin#add_at_eof| is true, add the \r\n                           task at the end of file\r\n     ............... Add a new task; copy any list and tags from the \r\n                           current task;\r\n                           if |g:ttodo#ftplugin#add_at_eof| is true, add the \r\n                           task at the end of file\r\n     ............... Add a new subtask\r\n    tx ...... Mark \"done\"\r\n    td ...... Mark due in N days\r\n    tw ...... Mark due in N weeks\r\n    tm ...... Mark due in N months\r\n    ty ...... Set priority\r\n    ta ...... Archive completed items\r\n    tb ...... View, filter items in the current buffer\r\n    tn ...... Add a note (the filename uses the first @list tag)\r\n    ti ...... Add a hopefully unique ID (an Adler32 hash)\r\n\r\nIf filetype is ttodo, the following commands are supported:\r\n\r\n    |:Ttodoarchive| ...... Archive completed tasks in the current buffer\r\n    |:Ttodobuffer| ....... Show tasks in the current buffer only\r\n    |:Ttodonote| ......... Add a new note to the task at the cursor\r\n    |:Ttodosort| ......... Sort the tasks in the current buffer\r\n\r\nAs a ftplugin, ttodo supports the following syntax\/extensions to todo.txt (see \r\nalso https:\/\/github.com\/ginatrapani\/todo.txt-cli\/wiki\/The-Todo.txt-Format):\r\n\r\n    (A) DATE TASK .... A priority as upper case letter (at the beginning of the \r\n                       line)\r\n    DATE TASK ........ A pending task\r\n    x DATE DATE TASK . A completed task (with completion date)\r\n    indented tasks ... A indented task is a subtask of the parent task; unless \r\n                       `has_subtasks` is true, |:Ttodo| will only show tasks \r\n                       with no open subtasks; this is similar to how the \r\n                       outline addon handles subtasks (see also \r\n                       https:\/\/github.com\/samuelsnyder\/outline-todo.txt)\r\n\r\nA TASK may contain the following tags:\r\n\r\n    @list ............ a \"list\" tag\r\n    +keyword ......... a \"keyword\" tag\r\n    h:1 .............. hidden task\r\n    due:YYYY-MM-DD ... due dates\r\n    rec:+Nx .......... When marking a task a \"done\", add a new task with a due \r\n                       date in N d(ays), w(eeks), m(onths), y(ears); with the \r\n                       leading '+' use the original due date; else use the \r\n                       completion date; this is similar to how the Simpletask \r\n                       Android app handles `rec` tags\r\n    t:YYYY-MM-DD ..... Hide the tasks until the given date\r\n    t:-Nd ............ Hide the tasks until N days before the due date\r\n\r\nOther ftplugin for todo.txt files, which can be used in conjunction with the \r\nttodo plugin (if you don't want to use it's |ftplugin|), include:\r\n\r\n    - https:\/\/github.com\/freitass\/todo.txt-vim\r\n        - todo-txt.vim : Vim plugin for Todo.txt \r\n          https:\/\/github.com\/dbeniamine\/todo.txt-vim or\r\n          http:\/\/www.vim.org\/scripts\/script.php?script_id=5134\r\n    - https:\/\/github.com\/mivok\/vimtodo or\r\n      http:\/\/www.vim.org\/scripts\/script.php?script_id=3264\r\n    - https:\/\/github.com\/davidoc\/todo.txt-vim\r\n        - My fork: https:\/\/github.com\/tomtom\/todo.txt-vim-1\r\n    - https:\/\/github.com\/dsiroky\/vim-todotxt\r\n    - ...\r\n\r\nRelated work:\r\n    - https:\/\/github.com\/elentok\/todo.vim\r\n","install_details":"To install the vimball, edit the vba file and type: >\r\n\r\n    :so %\r\n\r\nSee :help vimball for details.\r\n\r\nTo install from github, please use\r\n    1. git + a plugin loader like enable_vim, pathogen, vim-unbundle etc.\r\n    2. a plugin manager like VAM, Vundle, NeoBundle, vim-plug etc.\r\n\r\nThe tlib_vim plugin is required:\r\nhttps:\/\/github.com\/tomtom\/tlib_vim\r\n\r\nOptional enhancement:\r\n- https:\/\/github.com\/tomtom\/autolinker_vim for hyperlinking\r\n\r\nAlso available via git: http:\/\/github.com\/tomtom\/ttodo_vim\r\n\r\n\r\nSetup~\r\n\r\nPlease set |g:ttodo#dirs| in |vimrc| before using |:Ttodo|.\r\n","5":"To install the vimball, edit the vba file and type: >\r\n\r\n    :so %\r\n\r\nSee :help vimball for details.\r\n\r\nTo install from github, please use\r\n    1. git + a plugin loader like enable_vim, pathogen, vim-unbundle etc.\r\n    2. a plugin manager like VAM, Vundle, NeoBundle, vim-plug etc.\r\n\r\nThe tlib_vim plugin is required:\r\nhttps:\/\/github.com\/tomtom\/tlib_vim\r\n\r\nOptional enhancement:\r\n- https:\/\/github.com\/tomtom\/autolinker_vim for hyperlinking\r\n\r\nAlso available via git: http:\/\/github.com\/tomtom\/ttodo_vim\r\n\r\n\r\nSetup~\r\n\r\nPlease set |g:ttodo#dirs| in |vimrc| before using |:Ttodo|.\r\n","first_name":"Tom","6":"Tom","last_name":"Link","7":"Link","releases":[{"0":"5262","vim_version":"7.0","1":"7.0","script_version":"1.01","2":"1.01","version_comment":"- s\/@inbox\/@Inbox\/\n- Allow for `due:today` shortcut\n- list view: FIX invocation of some commands on multiple items\n- g:ttodo#ftplugin#edit_note defaults to ''\n- syntax: don't accidentally highlight tags, keywords etc. within words\n- FIX #1: If g:ttodo#force_filetype evaluates to true, use `set ft=ttodo` instead of `setf ttodo`\n- FIX #2: Remove leading whitespace when archiving a sub-task\n- FIX #3: Use ttodo#IsValidDue(due) to validate the value of the `due` command-line flag\n- FIX handling of --[no-]undated\n- Support for rec:Nb business days\n- g:ttodo#ftplugin#note_prefix defaults to 'root:\/\/'\n- syntax\/ttodo.vim: TtodoTag: Highlight only known tags\n- ttodo#SetCreateDate(): Marking a recurring task as done updates the created date\n- require tlib >= 1.22\n-  also copies notes\n- FIX #4: docs for maps\n- Misc improvments\n- g:ttodo#file_pattern can be a list\n- --files command-line option actually works; more checks if a file exists\n- Support for @next lists\n- Command & map to open todo files in the current working directory\n- ttodo#ftplugin#MarkDone(): Don't inherit the @next list for recurrent items\n- s:GetFiles(): use map(); etc.\n- ftdetect: Also check for upper case TODO.TXT pattern\n- FIX parsing of tags & lists; FIX linter warnings\n- g:ttodo#ftplugin#new_subtask_copy_pri defaults to 0\n- misc improvements\n- Use tcomment#type#Define() instead of tcomment#DefineType() for tcomment >= 4.00\n- Make the done filename configurable\n- Misc improvements to \"mark done\" & \"archive\"\n- Support for file-local options\nSHA256 checksum: 6fcd0ebac1f0a01222ef9b836fd39843921f03a5eab4d93e3c30ec4ad1c4edf1","3":"- s\/@inbox\/@Inbox\/\n- Allow for `due:today` shortcut\n- list view: FIX invocation of some commands on multiple items\n- g:ttodo#ftplugin#edit_note defaults to ''\n- syntax: don't accidentally highlight tags, keywords etc. within words\n- FIX #1: If g:ttodo#force_filetype evaluates to true, use `set ft=ttodo` instead of `setf ttodo`\n- FIX #2: Remove leading whitespace when archiving a sub-task\n- FIX #3: Use ttodo#IsValidDue(due) to validate the value of the `due` command-line flag\n- FIX handling of --[no-]undated\n- Support for rec:Nb business days\n- g:ttodo#ftplugin#note_prefix defaults to 'root:\/\/'\n- syntax\/ttodo.vim: TtodoTag: Highlight only known tags\n- ttodo#SetCreateDate(): Marking a recurring task as done updates the created date\n- require tlib >= 1.22\n-  also copies notes\n- FIX #4: docs for maps\n- Misc improvments\n- g:ttodo#file_pattern can be a list\n- --files command-line option actually works; more checks if a file exists\n- Support for @next lists\n- Command & map to open todo files in the current working directory\n- ttodo#ftplugin#MarkDone(): Don't inherit the @next list for recurrent items\n- s:GetFiles(): use map(); etc.\n- ftdetect: Also check for upper case TODO.TXT pattern\n- FIX parsing of tags & lists; FIX linter warnings\n- g:ttodo#ftplugin#new_subtask_copy_pri defaults to 0\n- misc improvements\n- Use tcomment#type#Define() instead of tcomment#DefineType() for tcomment >= 4.00\n- Make the done filename configurable\n- Misc improvements to \"mark done\" & \"archive\"\n- Support for file-local options\nSHA256 checksum: 6fcd0ebac1f0a01222ef9b836fd39843921f03a5eab4d93e3c30ec4ad1c4edf1","package":"ttodo.zip","4":"ttodo.zip","src_id":"28105","5":"28105","creation_date":"1658504100","6":"1658504100"},{"0":"5262","vim_version":"7.0","1":"7.0","script_version":"1.00","2":"1.00","version_comment":"- g:ttodo#ftplugin#add_at_eof defaults to 1\n- NEW map t*\n- g:ttodo_enable_ftdetect defaults to 1\n- Completion for lists and tags\n- Require tlib 1.18\n- Command-line completion for Ttodonew\n- :Ttodonew respects --pref argument\n- ftplugin: lb fo=cql\n- Cache each parsed tasks not tasks per file\n- Highlight overdue due dates\n- Task dependencies, --pending command-line option\n- dep:IDs is a comma-separated list\n- Sort moves overdue items to the top\n- NEW ttodo#ftplugin#AddDep(), map: tD\n- Fix has_lists\/tags command-line flag\n- s\/tlib#type#DefSchema\/tlib#type#Define\/; require tlib >= 1.19\n- ttodo#ftplugin#Archive(): Don't archive tasks with pending sub\/tasks\n- ttodo#ftplugin#Agent: Allow for \"once\" expressions as arguments\n- g:ttodo#rewrite_gsub: FIX regexp\n- NEW g:ttodo#ftplugin#rec_copy: copy recurring tasks when marking them as \"done\"\n- ttodo#ftplugin#MarkDone(): Make sure to inc due date once\n- NEW :Ttodogrep\n- ttodo#NewTask: FIX handling of inboxfile arg\n- Simplify g:ttodo#prefs\n- g:ttodo#new_task: pri = C\n- NEW ignore_lists, ignore_tags, ignore_pri arguments\n- g:ttodo#prefs: important.due = 1w\n- g:ttodo#sort_defaults.pri = I\n- s:FilterTasks: FIX handling of undated\n- NEW ttodo#InputNumber()\n- ttodo#ftplugin#MarkDue: Accept count == -1\n- NEW Ttodoinbox\n- TtodoHidden syntax\n- ttodo#ftplugin#MarkDone(): temporarily disallow for outlines with rec: tags; g:ttodo#ftplugin#rec_copy appends new task at the eof\nMD5 checksum: a7a364b97ca3e05540974d05a42a797e","3":"- g:ttodo#ftplugin#add_at_eof defaults to 1\n- NEW map t*\n- g:ttodo_enable_ftdetect defaults to 1\n- Completion for lists and tags\n- Require tlib 1.18\n- Command-line completion for Ttodonew\n- :Ttodonew respects --pref argument\n- ftplugin: lb fo=cql\n- Cache each parsed tasks not tasks per file\n- Highlight overdue due dates\n- Task dependencies, --pending command-line option\n- dep:IDs is a comma-separated list\n- Sort moves overdue items to the top\n- NEW ttodo#ftplugin#AddDep(), map: tD\n- Fix has_lists\/tags command-line flag\n- s\/tlib#type#DefSchema\/tlib#type#Define\/; require tlib >= 1.19\n- ttodo#ftplugin#Archive(): Don't archive tasks with pending sub\/tasks\n- ttodo#ftplugin#Agent: Allow for \"once\" expressions as arguments\n- g:ttodo#rewrite_gsub: FIX regexp\n- NEW g:ttodo#ftplugin#rec_copy: copy recurring tasks when marking them as \"done\"\n- ttodo#ftplugin#MarkDone(): Make sure to inc due date once\n- NEW :Ttodogrep\n- ttodo#NewTask: FIX handling of inboxfile arg\n- Simplify g:ttodo#prefs\n- g:ttodo#new_task: pri = C\n- NEW ignore_lists, ignore_tags, ignore_pri arguments\n- g:ttodo#prefs: important.due = 1w\n- g:ttodo#sort_defaults.pri = I\n- s:FilterTasks: FIX handling of undated\n- NEW ttodo#InputNumber()\n- ttodo#ftplugin#MarkDue: Accept count == -1\n- NEW Ttodoinbox\n- TtodoHidden syntax\n- ttodo#ftplugin#MarkDone(): temporarily disallow for outlines with rec: tags; g:ttodo#ftplugin#rec_copy appends new task at the eof\nMD5 checksum: a7a364b97ca3e05540974d05a42a797e","package":"ttodo.vba","4":"ttodo.vba","src_id":"23956","5":"23956","creation_date":"1453828056","6":"1453828056"},{"0":"5262","vim_version":"7.0","1":"7.0","script_version":"0.03","2":"0.03","version_comment":"- ttodo#Show: copy(s:list_env)\n- NEW :Ttodosort command\n- Support for indented subtasks similar to the outline add-on; misc enhancements\n- Support for tcomment\n- Fix handling of subtasks;  map for inserting subtasks; g:ttodo#viewer is a list\n- NEW --encoding command-line option\n- NEW --bufnr, --bufname command-line options\n- Remove dependency on vikitasks plugin\n- Use autocmd BufNewFile,BufRead done.txt\n- Use , t1 for setting the priority\n- ttodo#GetFileTasks: Use tlib#eval#Extend(copy(parent.task), task)\n- g:ttodo#viewer is a string; removed last traces of vikitasks\n- Configure \"hidden\" tasks via g:ttodo#task_hide_rx\n- NEW :Ttodotask; use y for SetPriority; misc enhancements\n- Properly support file-specific args; improved support for subtasks; misc enh.s\n- NEW g:ttodo#filesargs: A dictionary of {filename regexp: {additional args}}\n- NEW --has_lists=, --has_tags= command-line options\n- g:ttodo#sort: s\/idx\/lnum\/\n- s\/Ttodotask\/Ttodonew\/\n- Misc improvements to ftplugin\n- s:GetFiles(): FIX type error\n- s:FilterTasks(): Don't use g:ttodo#default_pri\n- FIX Ttodosort\n- Stop when sorting task outlines\n- Warn if subtask has a due date after the parent's task due date\n- ttodo#ftplugin#New(): FIX indentation\nMD5 checksum: f3cbe1572df17ba026f84166d3857a4b","3":"- ttodo#Show: copy(s:list_env)\n- NEW :Ttodosort command\n- Support for indented subtasks similar to the outline add-on; misc enhancements\n- Support for tcomment\n- Fix handling of subtasks;  map for inserting subtasks; g:ttodo#viewer is a list\n- NEW --encoding command-line option\n- NEW --bufnr, --bufname command-line options\n- Remove dependency on vikitasks plugin\n- Use autocmd BufNewFile,BufRead done.txt\n- Use , t1 for setting the priority\n- ttodo#GetFileTasks: Use tlib#eval#Extend(copy(parent.task), task)\n- g:ttodo#viewer is a string; removed last traces of vikitasks\n- Configure \"hidden\" tasks via g:ttodo#task_hide_rx\n- NEW :Ttodotask; use y for SetPriority; misc enhancements\n- Properly support file-specific args; improved support for subtasks; misc enh.s\n- NEW g:ttodo#filesargs: A dictionary of {filename regexp: {additional args}}\n- NEW --has_lists=, --has_tags= command-line options\n- g:ttodo#sort: s\/idx\/lnum\/\n- s\/Ttodotask\/Ttodonew\/\n- Misc improvements to ftplugin\n- s:GetFiles(): FIX type error\n- s:FilterTasks(): Don't use g:ttodo#default_pri\n- FIX Ttodosort\n- Stop when sorting task outlines\n- Warn if subtask has a due date after the parent's task due date\n- ttodo#ftplugin#New(): FIX indentation\nMD5 checksum: f3cbe1572df17ba026f84166d3857a4b","package":"ttodo.vba","4":"ttodo.vba","src_id":"23756","5":"23756","creation_date":"1448349827","6":"1448349827"},{"0":"5262","vim_version":"7.0","1":"7.0","script_version":"0.02","2":"0.02","version_comment":"- :Ttodo -A, -R, -i, -x command line options; require tlib >= 1.16\n- ttodo#CComplete(): use tlib#arg#Complete; misc\n- NEW --sort command-line option; vikitask integration for manipulating todo.txt files; misc enh\n- NEW own ftplugin; misc improvements\n- Require vikitasks >= 1.02\n- Use tlib#file#Globpath()\n- various improvements\n- s\/TLibTrace\/Tlibtrace\/g\n- version 0.01-151109\nMD5 checksum: e6b8be03504c4a9d948ca4a38de683f3","3":"- :Ttodo -A, -R, -i, -x command line options; require tlib >= 1.16\n- ttodo#CComplete(): use tlib#arg#Complete; misc\n- NEW --sort command-line option; vikitask integration for manipulating todo.txt files; misc enh\n- NEW own ftplugin; misc improvements\n- Require vikitasks >= 1.02\n- Use tlib#file#Globpath()\n- various improvements\n- s\/TLibTrace\/Tlibtrace\/g\n- version 0.01-151109\nMD5 checksum: e6b8be03504c4a9d948ca4a38de683f3","package":"ttodo.vba","4":"ttodo.vba","src_id":"23724","5":"23724","creation_date":"1447087680","6":"1447087680"},{"0":"5262","vim_version":"7.4","1":"7.4","script_version":"0.01","2":"0.01","version_comment":"Initial upload","3":"Initial upload","package":"ttodo.vba","4":"ttodo.vba","src_id":"23688","5":"23688","creation_date":"1445883874","6":"1445883874"}]},"5261":{"script_id":"5261","0":"5261","script_name":"Exeline","1":"Exeline","script_type":"utility","2":"utility","summary":"execute commands on save","3":"execute commands on save","description":"Executes a command on `BufWritePost` events. E.g.:\r\n'!:exe [so %]' sources the file on each save.\r\n\r\nDefaults: exe, md, sass, less, jade, coffee.\r\n!::exe [expression] : executes expression.\r\n!::md [dir] : outputs file.html in dir. (default = file's dir )\r\n\r\nMore detailed overview:\r\nhttps:\/\/github.com\/romgrk\/vim-exeline","4":"Executes a command on `BufWritePost` events. E.g.:\r\n'!:exe [so %]' sources the file on each save.\r\n\r\nDefaults: exe, md, sass, less, jade, coffee.\r\n!::exe [expression] : executes expression.\r\n!::md [dir] : outputs file.html in dir. (default = file's dir )\r\n\r\nMore detailed overview:\r\nhttps:\/\/github.com\/romgrk\/vim-exeline","install_details":"","5":"","first_name":"Rom","6":"Rom","last_name":"Grk","7":"Grk","releases":[{"0":"5261","vim_version":"7.0","1":"7.0","script_version":"1.1","2":"1.1","version_comment":"alternate command extension","3":"alternate command extension","package":"exeline.zip","4":"exeline.zip","src_id":"23693","5":"23693","creation_date":"1446217017","6":"1446217017"},{"0":"5261","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"vim-exeline.zip","4":"vim-exeline.zip","src_id":"23680","5":"23680","creation_date":"1445453899","6":"1445453899"}]},"5260":{"script_id":"5260","0":"5260","script_name":"visualMarks","1":"visualMarks","script_type":"utility","2":"utility","summary":"Save and restore visually selected areas","3":"Save and restore visually selected areas","description":"Everything's on the GitHub: https:\/\/github.com\/iago-lito\/vim-visualMarks","4":"Everything's on the GitHub: https:\/\/github.com\/iago-lito\/vim-visualMarks","install_details":"Built for Pathogen: just untar the ball in your bundle directory :)","5":"Built for Pathogen: just untar the ball in your bundle directory :)","first_name":"Iago","6":"Iago","last_name":"Bonnici","7":"Bonnici","releases":[{"0":"5260","vim_version":"7.4","1":"7.4","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"visualMarks-0.1.tar.gz","4":"visualMarks-0.1.tar.gz","src_id":"23679","5":"23679","creation_date":"1445189511","6":"1445189511"}]},"5259":{"script_id":"5259","0":"5259","script_name":"pp.vim","1":"pp.vim","script_type":"utility","2":"utility","summary":"Pretty-printer for vimscript expressions -- colors -- pretty colors.","3":"Pretty-printer for vimscript expressions -- colors -- pretty colors.","description":"A pretty-printer object inspector for vimscript.\r\n\r\nUse command 'Pp' to inspect objects and values, as you would use ':echo' or ':call'.\r\nOr use 'pp.dump(obj [, depth])' &\/|| 'pp#print(...)'.\r\n\r\n(Images and colors \u00e2\u0080\u0094pretty colors!\u00e2\u0080\u0094 over there ⟶ https:\/\/github.com\/romgrk\/pp.vim )\r\n","4":"A pretty-printer object inspector for vimscript.\r\n\r\nUse command 'Pp' to inspect objects and values, as you would use ':echo' or ':call'.\r\nOr use 'pp.dump(obj [, depth])' &\/|| 'pp#print(...)'.\r\n\r\n(Images and colors \u00e2\u0080\u0094pretty colors!\u00e2\u0080\u0094 over there ⟶ https:\/\/github.com\/romgrk\/pp.vim )\r\n","install_details":"Use github repo.\r\nThis will not be updated. Frequently.","5":"Use github repo.\r\nThis will not be updated. Frequently.","first_name":"Rom","6":"Rom","last_name":"Grk","7":"Grk","releases":[{"0":"5259","vim_version":"7.0","1":"7.0","script_version":"0.77","2":"0.77","version_comment":"Initial upload","3":"Initial upload","package":"pp.vim","4":"pp.vim","src_id":"23676","5":"23676","creation_date":"1445001205","6":"1445001205"}]},"5258":{"script_id":"5258","0":"5258","script_name":"vim-gradle","1":"vim-gradle","script_type":"ftplugin","2":"ftplugin","summary":"The purpose of this project is to maintain missing Gradle capabilities in Vim.","3":"The purpose of this project is to maintain missing Gradle capabilities in Vim.","description":"The purpose of this project is to maintain missing Gradle capabilities in Vim. Particularly:\r\n\r\n* File extension recognition\r\n* Syntax highlighting\r\n* Folding\r\n* Ctags support for Tagbar plugin\r\n\r\nAdditionally, some missing Groovy features are provided as well:\r\n\r\n* Folding for Groovy files\r\n* Groovy Ctags support for Tagbar plugin\r\n\r\nThe home page of the project and Mercurial repository:\r\n\r\nhttps:\/\/bitbucket.org\/sw-samuraj\/vim-gradle","4":"The purpose of this project is to maintain missing Gradle capabilities in Vim. Particularly:\r\n\r\n* File extension recognition\r\n* Syntax highlighting\r\n* Folding\r\n* Ctags support for Tagbar plugin\r\n\r\nAdditionally, some missing Groovy features are provided as well:\r\n\r\n* Folding for Groovy files\r\n* Groovy Ctags support for Tagbar plugin\r\n\r\nThe home page of the project and Mercurial repository:\r\n\r\nhttps:\/\/bitbucket.org\/sw-samuraj\/vim-gradle","install_details":"If you are using Pathogen plugin, then the installation is simple and straightforward:\r\n\r\ncd ~\/.vim\/bundle\r\nhg clone https:\/\/bitbucket.org\/sw-samuraj\/vim-gradle\r\n\r\nIf you prefer the traditional Vim layout, then you just copy the archive content to your $VIM_HOME.\r\n\r\nAnd finally, if you clone the repository, then you can use Gradle for plugin installation and uninstallation (see the home page).","5":"If you are using Pathogen plugin, then the installation is simple and straightforward:\r\n\r\ncd ~\/.vim\/bundle\r\nhg clone https:\/\/bitbucket.org\/sw-samuraj\/vim-gradle\r\n\r\nIf you prefer the traditional Vim layout, then you just copy the archive content to your $VIM_HOME.\r\n\r\nAnd finally, if you clone the repository, then you can use Gradle for plugin installation and uninstallation (see the home page).","first_name":"V\u00c3\u00adt","6":"V\u00c3\u00adt","last_name":"Kota\u010dka","7":"Kotačka","releases":[{"0":"5258","vim_version":"7.4","1":"7.4","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"vim-gradle-0.1.zip","4":"vim-gradle-0.1.zip","src_id":"23671","5":"23671","creation_date":"1444855345","6":"1444855345"}]},"5257":{"script_id":"5257","0":"5257","script_name":"groovyindent-unix","1":"groovyindent-unix","script_type":"indent","2":"indent","summary":"groovy indent script","3":"groovy indent script","description":"Re-upload of vimscript #2961 with UNIX line endings.","4":"Re-upload of vimscript #2961 with UNIX line endings.","install_details":"just place this script into VIM\/indent\/","5":"just place this script into VIM\/indent\/","first_name":"Chaoren","6":"Chaoren","last_name":"Lin","7":"Lin","releases":[{"0":"5257","vim_version":"6.0","1":"6.0","script_version":"0.11","2":"0.11","version_comment":"https:\/\/github.com\/vim-scripts\/groovyindent-unix\/pull\/1","3":"https:\/\/github.com\/vim-scripts\/groovyindent-unix\/pull\/1","package":"groovy.vim","4":"groovy.vim","src_id":"24095","5":"24095","creation_date":"1457861506","6":"1457861506"},{"0":"5257","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"groovy.vim","4":"groovy.vim","src_id":"23668","5":"23668","creation_date":"1444695225","6":"1444695225"}]},"5256":{"script_id":"5256","0":"5256","script_name":"markdown-preview.vim","1":"markdown-preview.vim","script_type":"ftplugin","2":"ftplugin","summary":"yet another markdown preview plugin","3":"yet another markdown preview plugin","description":"FOR MORE INFO: please visit https:\/\/github.com\/MikeCoder\/markdown-preview.vim\r\n\r\nWhy you need this\r\n\r\n    It's easy to install with vundle or bundle\r\n    No complex config steps\r\n    Code Hightlight\r\n    Easy to custom your own css style\r\n    TODO: Code custom style hightlight\r\n\r\n\r\nUsage\r\n\r\n    edit your markdown doc normally\r\n    when you want to preview it in html you just use :MarkdownPreview defult to show your doc in your browser\r\n    if you want to change your style. you just use :MarkdownPreview GitHub in github style markdown view\r\n    you can also use map m :MarkdownPreview GitHub to have more fun\r\n\r\nCustom\r\n\r\nthis theme is in the css folder, if you want to change it to your favorite theme. follow the steps:\r\n\r\n    go into your .vim folder\r\n    find MarkDownRes folder and you will find default.css and GitHub.css here\r\n    add your custom css file here, such as exmaple.css\r\n    use vim open your markdown doc and :MarkdownPreview example\r\n    and you will see your doc preview in your browser with example.css\r\n\r\nAdvanced Usage\r\n\r\n    use :MarkdownPreviewWithCustomCodeStyle css-style code-style instead\r\n    you can use custom css style and code hightlight style\r\n    the following code styles are you can use:\r\n        github\r\n        solarized_dark\r\n        solarized_light\r\n        default\r\n        color-brewer\r\n        railscasts\r\n        tomorrow\r\n        zenburn\r\n        mono\r\n        monokai_sublime\r\n    these code css files are in your ~\/.vim\/MarkDownRes\/code-styles folder\r\n    for example, you use :MarkdownPreviewWithCustomCodeStyleCodeStyle Github zenburn, when edit the TEST.md","4":"FOR MORE INFO: please visit https:\/\/github.com\/MikeCoder\/markdown-preview.vim\r\n\r\nWhy you need this\r\n\r\n    It's easy to install with vundle or bundle\r\n    No complex config steps\r\n    Code Hightlight\r\n    Easy to custom your own css style\r\n    TODO: Code custom style hightlight\r\n\r\n\r\nUsage\r\n\r\n    edit your markdown doc normally\r\n    when you want to preview it in html you just use :MarkdownPreview defult to show your doc in your browser\r\n    if you want to change your style. you just use :MarkdownPreview GitHub in github style markdown view\r\n    you can also use map m :MarkdownPreview GitHub to have more fun\r\n\r\nCustom\r\n\r\nthis theme is in the css folder, if you want to change it to your favorite theme. follow the steps:\r\n\r\n    go into your .vim folder\r\n    find MarkDownRes folder and you will find default.css and GitHub.css here\r\n    add your custom css file here, such as exmaple.css\r\n    use vim open your markdown doc and :MarkdownPreview example\r\n    and you will see your doc preview in your browser with example.css\r\n\r\nAdvanced Usage\r\n\r\n    use :MarkdownPreviewWithCustomCodeStyle css-style code-style instead\r\n    you can use custom css style and code hightlight style\r\n    the following code styles are you can use:\r\n        github\r\n        solarized_dark\r\n        solarized_light\r\n        default\r\n        color-brewer\r\n        railscasts\r\n        tomorrow\r\n        zenburn\r\n        mono\r\n        monokai_sublime\r\n    these code css files are in your ~\/.vim\/MarkDownRes\/code-styles folder\r\n    for example, you use :MarkdownPreviewWithCustomCodeStyleCodeStyle Github zenburn, when edit the TEST.md","install_details":"Recommand Bundle or Vundle\r\nVundle\r\n\r\n    you can see how to install vundle here\r\n    after you install your vundle, make sure your plugins folder is ~\/.vim\/bundle\r\n    then you can write this plugin url into your .vimrc file, like Plugin 'MikeCoder\/markdown-preview.vim'\r\n    then use PluginInstall to install the plugin\r\n\r\nRecommand:k-vim\r\n\r\n    add Bundle 'MikeCoder\/markdown-preview.vim' to your vimrc.bundle file\r\n    and exec BundleInstall to install the plugin\r\n\r\nUsual Install\r\n\r\n    this is not a good choice, make sure every step is right\r\n    use cd ~\/.vim into your vim folder\r\n    download this tar package and unpack it in your .vim folder\r\n    use mv markdown-preview.vim\/* . && rm -rf markdown-preview.vim\r\n    use cp resources MarkDownRes to copy the resources\r\n    then you can open your vim and type MarkdownPreview Github to check whether it is ok","5":"Recommand Bundle or Vundle\r\nVundle\r\n\r\n    you can see how to install vundle here\r\n    after you install your vundle, make sure your plugins folder is ~\/.vim\/bundle\r\n    then you can write this plugin url into your .vimrc file, like Plugin 'MikeCoder\/markdown-preview.vim'\r\n    then use PluginInstall to install the plugin\r\n\r\nRecommand:k-vim\r\n\r\n    add Bundle 'MikeCoder\/markdown-preview.vim' to your vimrc.bundle file\r\n    and exec BundleInstall to install the plugin\r\n\r\nUsual Install\r\n\r\n    this is not a good choice, make sure every step is right\r\n    use cd ~\/.vim into your vim folder\r\n    download this tar package and unpack it in your .vim folder\r\n    use mv markdown-preview.vim\/* . && rm -rf markdown-preview.vim\r\n    use cp resources MarkDownRes to copy the resources\r\n    then you can open your vim and type MarkdownPreview Github to check whether it is ok","first_name":"Dongxin","6":"Dongxin","last_name":"Tang","7":"Tang","releases":[{"0":"5256","vim_version":"7.2","1":"7.2","script_version":"2.1.1","2":"2.1.1","version_comment":"fix bugs on windows","3":"fix bugs on windows","package":"markdown-preview.vim.tar.gz","4":"markdown-preview.vim.tar.gz","src_id":"24036","5":"24036","creation_date":"1456288212","6":"1456288212"},{"0":"5256","vim_version":"7.2","1":"7.2","script_version":"1.1.0","2":"1.1.0","version_comment":"add code style custom","3":"add code style custom","package":"markdown-preview.vim.zip","4":"markdown-preview.vim.zip","src_id":"23706","5":"23706","creation_date":"1446466186","6":"1446466186"},{"0":"5256","vim_version":"7.2","1":"7.2","script_version":"1.0.2","2":"1.0.2","version_comment":"fix bugs when your vim not support python\r\n\r\nyou can see more info by visiting:https:\/\/github.com\/MikeCoder\/markdown-preview.vim","3":"fix bugs when your vim not support python\r\n\r\nyou can see more info by visiting:https:\/\/github.com\/MikeCoder\/markdown-preview.vim","package":"markdown-preview.vim.tar.gz","4":"markdown-preview.vim.tar.gz","src_id":"23670","5":"23670","creation_date":"1444713557","6":"1444713557"}]},"5255":{"script_id":"5255","0":"5255","script_name":"Tabtastic","1":"Tabtastic","script_type":"utility","2":"utility","summary":"Helps make multiple tabs in Vim quick and easy","3":"Helps make multiple tabs in Vim quick and easy","description":"This plugin was built as a tool to help create multiple tabs in Vim.\r\n\r\nTabtastic only has one command which is the :Tabtastic command. You can remap this command to use your leader key if you would like.\r\n\r\nIf you are interested in contributing to the plugin, please submit a pull request on Github.\r\n\r\n","4":"This plugin was built as a tool to help create multiple tabs in Vim.\r\n\r\nTabtastic only has one command which is the :Tabtastic command. You can remap this command to use your leader key if you would like.\r\n\r\nIf you are interested in contributing to the plugin, please submit a pull request on Github.\r\n\r\n","install_details":"Use either Vundle, or Pathogen to install this plugin please","5":"Use either Vundle, or Pathogen to install this plugin please","first_name":"matt","6":"matt","last_name":"michnal","7":"michnal","releases":[{"0":"5255","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Changed the Script and AutoInstall references to reflect new plugin created at vim.org","3":"Changed the Script and AutoInstall references to reflect new plugin created at vim.org","package":"vim-tabtastic.zip","4":"vim-tabtastic.zip","src_id":"23649","5":"23649","creation_date":"1444190375","6":"1444190375"}]},"5254":{"script_id":"5254","0":"5254","script_name":"Typer","1":"Typer","script_type":"game","2":"game","summary":"This is VIM typing file plugin to simulate work","3":"This is VIM typing file plugin to simulate work","description":"TYPER\r\n\r\n  This is VIM typing file plugin to simulate work\r\n\r\n  When you're tired but your boss is watching you, or when you want to \r\n  show your friends what is your best - just use this\r\n\r\n  Select a file, press random keys and file will be typed for you \r\n\r\nUSAGE\r\n\r\nTo type file into new tab just execute:\r\n\r\n  :Typer filename\r\n\r\nTo set speed per press use this command:\r\n\r\n  :let g:typer_speed    = 4\r\n\t\r\nTo set screen alignment speed use this command:\r\n\r\n  :let g:typer_zz_count = 16\r\n\r\nTo exit just press Ctrl+C\r\n","4":"TYPER\r\n\r\n  This is VIM typing file plugin to simulate work\r\n\r\n  When you're tired but your boss is watching you, or when you want to \r\n  show your friends what is your best - just use this\r\n\r\n  Select a file, press random keys and file will be typed for you \r\n\r\nUSAGE\r\n\r\nTo type file into new tab just execute:\r\n\r\n  :Typer filename\r\n\r\nTo set speed per press use this command:\r\n\r\n  :let g:typer_speed    = 4\r\n\t\r\nTo set screen alignment speed use this command:\r\n\r\n  :let g:typer_zz_count = 16\r\n\r\nTo exit just press Ctrl+C\r\n","install_details":"","5":"","first_name":"Mikhail","6":"Mikhail","last_name":"Brown","7":"Brown","releases":[{"0":"5254","vim_version":"5.7","1":"5.7","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"typer.vim","4":"typer.vim","src_id":"23639","5":"23639","creation_date":"1443818555","6":"1443818555"}]},"5253":{"script_id":"5253","0":"5253","script_name":"autolinker","1":"autolinker","script_type":"utility","2":"utility","summary":"Automatic links for any filetype (e.g. for a markdown\/latex based wiki)","3":"Automatic links for any filetype (e.g. for a markdown\/latex based wiki)","description":"Features:\r\n\r\n    - Call |:Autolinkbuffer| to enable autolinker for the current buffer \r\n      or check the definitions of |g:autolinker_filetypes| and \r\n      |g:autolinker_patterns|.\r\n    - Jump to files in the current directory and highlight potential hyperlinks\r\n    - Jump to files in 'path'\r\n    - Jump to tags\r\n    - Invoke URLs\r\n    - Use a fallback command (e.g. create inexistent files)\r\n\r\nThe default map is `gz` in normal and visual mode (see |g:autolinker#nmap| and \r\n|g:autolinker#xmap|). In insert mode, is is  if the key is yet unmapped \r\n(see |g:autolinker#imap|).\r\n\r\nDifferences to |gf|:\r\n\r\n    - Customizable & extensible\r\n    - Supports several methods\r\n    - Highlight some potential hyperlinks\r\n    - When there are multiple potential matches, users can select the right \r\n      file from a list\r\n","4":"Features:\r\n\r\n    - Call |:Autolinkbuffer| to enable autolinker for the current buffer \r\n      or check the definitions of |g:autolinker_filetypes| and \r\n      |g:autolinker_patterns|.\r\n    - Jump to files in the current directory and highlight potential hyperlinks\r\n    - Jump to files in 'path'\r\n    - Jump to tags\r\n    - Invoke URLs\r\n    - Use a fallback command (e.g. create inexistent files)\r\n\r\nThe default map is `gz` in normal and visual mode (see |g:autolinker#nmap| and \r\n|g:autolinker#xmap|). In insert mode, is is  if the key is yet unmapped \r\n(see |g:autolinker#imap|).\r\n\r\nDifferences to |gf|:\r\n\r\n    - Customizable & extensible\r\n    - Supports several methods\r\n    - Highlight some potential hyperlinks\r\n    - When there are multiple potential matches, users can select the right \r\n      file from a list\r\n","install_details":"To install the vimball, edit the vba file and type: >\r\n\r\n    :so %\r\n\r\nSee :help vimball for details.\r\n\r\nTo install from github, please use a plugin manager like enable_vim, pathogen, \r\nVAM, Vundle, NeoBundle, vim-plug, vim-unbundle etc.\r\n\r\nThis script requires tlib (vimscript #1863) to be installed -- see \r\nhttps:\/\/github.com\/tomtom\/tlib_vim.\r\n\r\nAlso available on https:\/\/github.com\/tomtom\/autolinker_vim\r\n","5":"To install the vimball, edit the vba file and type: >\r\n\r\n    :so %\r\n\r\nSee :help vimball for details.\r\n\r\nTo install from github, please use a plugin manager like enable_vim, pathogen, \r\nVAM, Vundle, NeoBundle, vim-plug, vim-unbundle etc.\r\n\r\nThis script requires tlib (vimscript #1863) to be installed -- see \r\nhttps:\/\/github.com\/tomtom\/tlib_vim.\r\n\r\nAlso available on https:\/\/github.com\/tomtom\/autolinker_vim\r\n","first_name":"Tom","6":"Tom","last_name":"Link","7":"Link","releases":[{"0":"5253","vim_version":"7.0","1":"7.0","script_version":"0.03","2":"0.03","version_comment":"- s:EditEdit(): try|catch\n- prototype.Jump_tag: Ignore E73\n- FIX #1: s\/autogroup!\/autocmd!\/ Don't delete the AutoLinker autocmd group; don't set b:undo_ftplugin\n- Require tlib >= 1.21\n- FIX enable autolinker on FileType autocommand\n- FIX interplay of g:autolinker#layout and g:autolinker#edit_* (relevant to the a maps (g:autolinker#map_options)\n- misc improvements & fixes\n- Handle mailto:; etc.\n- Support mailto: URLs, use queries ?q=SEARCHTEXT, ?lnum=N\n- prototype.SplitFilename(): Don't display message on #q=... and similar (just assume the probably right thing)\n- g:autolinker#url_rx\n- Improve maps\n- s:Jump(): FIX handling of w: variables\n- FIX #2: Support for hyperlink markup\n- viki: Support for intervikis, extended wiki links [[LINK]] or [[LINK][TEXT]]\n- ft_viki#ExpandCFile(): Improved suffix detection\n- Support for functions in g:autolinker#cfile_gsub\n- viki: Append suffix only if a link doesn't already include it\n- viki: Try harder to find the file\n- autolinker#Balloon(): FIX s\/self\/autolinker\/\n- Use tlib#file#Filereadable() (tlib >= 1.24)\n- autolinker#EnableBuffer(): Make sure not to init a buffer twice\n- Simplify g:autolinker#hyperlinks_markup_rx\n- Check the current buffer too in case the plugin gets loaded after startup\nSHA256 checksum: 9c516effdfd7c6c373b4861443d17fc044a7914d4ae2d3feb0bc0fba537f78d9","3":"- s:EditEdit(): try|catch\n- prototype.Jump_tag: Ignore E73\n- FIX #1: s\/autogroup!\/autocmd!\/ Don't delete the AutoLinker autocmd group; don't set b:undo_ftplugin\n- Require tlib >= 1.21\n- FIX enable autolinker on FileType autocommand\n- FIX interplay of g:autolinker#layout and g:autolinker#edit_* (relevant to the a maps (g:autolinker#map_options)\n- misc improvements & fixes\n- Handle mailto:; etc.\n- Support mailto: URLs, use queries ?q=SEARCHTEXT, ?lnum=N\n- prototype.SplitFilename(): Don't display message on #q=... and similar (just assume the probably right thing)\n- g:autolinker#url_rx\n- Improve maps\n- s:Jump(): FIX handling of w: variables\n- FIX #2: Support for hyperlink markup\n- viki: Support for intervikis, extended wiki links [[LINK]] or [[LINK][TEXT]]\n- ft_viki#ExpandCFile(): Improved suffix detection\n- Support for functions in g:autolinker#cfile_gsub\n- viki: Append suffix only if a link doesn't already include it\n- viki: Try harder to find the file\n- autolinker#Balloon(): FIX s\/self\/autolinker\/\n- Use tlib#file#Filereadable() (tlib >= 1.24)\n- autolinker#EnableBuffer(): Make sure not to init a buffer twice\n- Simplify g:autolinker#hyperlinks_markup_rx\n- Check the current buffer too in case the plugin gets loaded after startup\nSHA256 checksum: 9c516effdfd7c6c373b4861443d17fc044a7914d4ae2d3feb0bc0fba537f78d9","package":"autolinker.zip","4":"autolinker.zip","src_id":"25117","5":"25117","creation_date":"1493710801","6":"1493710801"},{"0":"5253","vim_version":"7.0","1":"7.0","script_version":"0.02","2":"0.02","version_comment":"- ]gz, [gz maps to jump between potential links (only words and Internet hyperlinks)\n- Make ]gz, [gz maps configurable\n- g:autolinker#cfile_gsub: \"stop\" option\n- autolinker#EditInPath(): Insert cfile\n- Moved g:autolinker#system_rx related code to tlib\n- typo\n- Require tlib >= 1.15\n- Support for markdown link maps\n- Support for sub-filetypes (MAJOR.MINOR)\n- Support for internal references\n- Misc enhancements\n- FIX g:autolinker#cfile_stop_characters\n- typo\n- NEW :Alfind command\n- NEW fileurl support; improved handling of directories etc.\n- s\/TLibTrace\/Tlibtrace\/g\n- g:autolinker#cfile_rstrip_rx replaces g:autolinker#cfile_stop_characters\n- s:EditEdit: Ensure the directory exists\n- :Aledit completion expands cfile_gsub etc.\n- Alfind -> Algrep; NEW Alfind: Select file\n- NEW autolinker#Balloon()\n- Handle file:\/\/ urls in CleanCFile()\n- Support jumping to line numbers (filename#LNUM) or occurrences of strings (filename#q=RX)\n- Enable for ttodo filetype by default\n- Fix highlighting\n- g:autolinker#url_rx: include \"+\"\n- g:autolinker_filetypes: Remove help\n- g:autolinker#url_rx: Include \"=\"\n- Simplify prototype.CfileGsubRx()\n- autolinker#EnableBuffer: FIX handle buffers with empty filetypes\n- Re-enable :Aledit command\n- autolinker#CompleteFilename. Include names from g:autolinker#cfile_gsub\n- autolinker#CompleteFilename: Optimize completion of directories\n- autolinker#CompleteFilename(): sort cfile_gsub names before results from glob()\n- autolinker#CompleteFilename: Escape blanks\nMD5 checksum: fcef3b288da74153a143e2d0272fe30e","3":"- ]gz, [gz maps to jump between potential links (only words and Internet hyperlinks)\n- Make ]gz, [gz maps configurable\n- g:autolinker#cfile_gsub: \"stop\" option\n- autolinker#EditInPath(): Insert cfile\n- Moved g:autolinker#system_rx related code to tlib\n- typo\n- Require tlib >= 1.15\n- Support for markdown link maps\n- Support for sub-filetypes (MAJOR.MINOR)\n- Support for internal references\n- Misc enhancements\n- FIX g:autolinker#cfile_stop_characters\n- typo\n- NEW :Alfind command\n- NEW fileurl support; improved handling of directories etc.\n- s\/TLibTrace\/Tlibtrace\/g\n- g:autolinker#cfile_rstrip_rx replaces g:autolinker#cfile_stop_characters\n- s:EditEdit: Ensure the directory exists\n- :Aledit completion expands cfile_gsub etc.\n- Alfind -> Algrep; NEW Alfind: Select file\n- NEW autolinker#Balloon()\n- Handle file:\/\/ urls in CleanCFile()\n- Support jumping to line numbers (filename#LNUM) or occurrences of strings (filename#q=RX)\n- Enable for ttodo filetype by default\n- Fix highlighting\n- g:autolinker#url_rx: include \"+\"\n- g:autolinker_filetypes: Remove help\n- g:autolinker#url_rx: Include \"=\"\n- Simplify prototype.CfileGsubRx()\n- autolinker#EnableBuffer: FIX handle buffers with empty filetypes\n- Re-enable :Aledit command\n- autolinker#CompleteFilename. Include names from g:autolinker#cfile_gsub\n- autolinker#CompleteFilename: Optimize completion of directories\n- autolinker#CompleteFilename(): sort cfile_gsub names before results from glob()\n- autolinker#CompleteFilename: Escape blanks\nMD5 checksum: fcef3b288da74153a143e2d0272fe30e","package":"autolinker.vba","4":"autolinker.vba","src_id":"23955","5":"23955","creation_date":"1453828005","6":"1453828005"},{"0":"5253","vim_version":"7.4","1":"7.4","script_version":"0.01","2":"0.01","version_comment":"Initial upload","3":"Initial upload","package":"autolinker.vba","4":"autolinker.vba","src_id":"23638","5":"23638","creation_date":"1443787906","6":"1443787906"}]},"5252":{"script_id":"5252","0":"5252","script_name":"vimagit","1":"vimagit","script_type":"utility","2":"utility","summary":"Ease your git workflow within vim.","3":"Ease your git workflow within vim.","description":"See complete description and source on github: https:\/\/github.com\/jreybert\/vimagit\r\n\r\nJoin the chat at https:\/\/gitter.im\/jreybert\/vimagit\r\n\r\nEase your git workflow within vim.\r\n\r\nFrom a very single vim buffer, you can perform main git operations in few key press. To name a few:\r\n* Visualize all diffs in your git repository.\r\n* Stage file, hunks or even just parts of a hunk using a single key press.\r\n* Write or amend your commit message and commit in the same buffer.\r\n\r\nTake a look at TL;DR to start using it immediately.\r\n\r\nThis workflow is 100% inspired from magnificent emacs Magit plugin.\r\n\r\n## Outstanding features\r\n\r\n* [x] Preview all your git changes in one unique buffer, folded at hunk level.\r\n* [x] Interactively stage\/unstage\/discard changes with one key press.\r\n* [x] Stage\/unstage at file\/hunk\/line level.\r\n* [x] Write the commit message in the same buffer.\r\n* [x] From a hunk in magit buffer, jump to the file at the diff position.\r\n* [x] 100% VimL plugin, no external dependency (except git of course).\r\n* [x] Enhanced by external plugins: vim-gitgutter vim-airline\r\n* [x] Stable. All features are tested in continuous integration.\r\n\r\nMore to come:\r\n* [ ] Add a push function, taking care if needed about the remote repository and branch #24 .\r\n* [ ] Handle commit fixup! and squash!, with a smart git log popup #23 .\r\n* [ ] Handle stash: add, pop, apply, drop #26 .\r\n* [ ] Stage multiple hunks or file by visually selecting them #83 .\r\n* [ ] Go through history, cherry-pick changes.\r\n* [ ] Make vimagit more efficient for huge repositories, with a lot of diffs.\r\n* [ ] Something is missing? Open an issue!\r\n\r\n> Why should I use vimagit, there are already plethora git plugins for vim?\r\n\r\n* fugitive is a very complete plugin, with a lot of functions. I use it for years, and it is a fundamental tool in my workflow. But visualize your changes and staged them in broad number of files is really a pain.\r\n* vim-gitgutter is very well integrated into vim, but without the ability to commit stages, it stays an informational plugin.\r\n\r\n## TL;DR\r\n\r\nThis is the minimal required set of command you must know to start playing with vimagit. See [Mappings](#mappings) for a complete description.\r\n\r\nTo simply test vimagit, modify\/add\/delete\/rename some files in a git repository and open vim.\r\n\r\n- `:Magit`  \r\n  Open magit buffer with :Magit command.\r\n- ``  \r\n  Jump to next hunk with ``, or move the cursor as you like. The cursor is on a hunk.\r\n- `S`  \r\n  While the cursor is on an unstaged hunk, press `S` in Normal mode: the hunk is now staged, and appears in \"Staged changes\" section (you can also unstage a hunk from \"Staged section\" with `S`).\r\n- `CC`  \r\n  Once you have stage all the required changes, press `CC`.\r\n  - Section \"Commit message\" is shown.\r\n  - Type your commit message in this section.\r\n  - To commit, go back in Normal mode, and press `CC` (or `:w` if you prefer).\r\n  \r\nYou just created your first commit with vimagit!","4":"See complete description and source on github: https:\/\/github.com\/jreybert\/vimagit\r\n\r\nJoin the chat at https:\/\/gitter.im\/jreybert\/vimagit\r\n\r\nEase your git workflow within vim.\r\n\r\nFrom a very single vim buffer, you can perform main git operations in few key press. To name a few:\r\n* Visualize all diffs in your git repository.\r\n* Stage file, hunks or even just parts of a hunk using a single key press.\r\n* Write or amend your commit message and commit in the same buffer.\r\n\r\nTake a look at TL;DR to start using it immediately.\r\n\r\nThis workflow is 100% inspired from magnificent emacs Magit plugin.\r\n\r\n## Outstanding features\r\n\r\n* [x] Preview all your git changes in one unique buffer, folded at hunk level.\r\n* [x] Interactively stage\/unstage\/discard changes with one key press.\r\n* [x] Stage\/unstage at file\/hunk\/line level.\r\n* [x] Write the commit message in the same buffer.\r\n* [x] From a hunk in magit buffer, jump to the file at the diff position.\r\n* [x] 100% VimL plugin, no external dependency (except git of course).\r\n* [x] Enhanced by external plugins: vim-gitgutter vim-airline\r\n* [x] Stable. All features are tested in continuous integration.\r\n\r\nMore to come:\r\n* [ ] Add a push function, taking care if needed about the remote repository and branch #24 .\r\n* [ ] Handle commit fixup! and squash!, with a smart git log popup #23 .\r\n* [ ] Handle stash: add, pop, apply, drop #26 .\r\n* [ ] Stage multiple hunks or file by visually selecting them #83 .\r\n* [ ] Go through history, cherry-pick changes.\r\n* [ ] Make vimagit more efficient for huge repositories, with a lot of diffs.\r\n* [ ] Something is missing? Open an issue!\r\n\r\n> Why should I use vimagit, there are already plethora git plugins for vim?\r\n\r\n* fugitive is a very complete plugin, with a lot of functions. I use it for years, and it is a fundamental tool in my workflow. But visualize your changes and staged them in broad number of files is really a pain.\r\n* vim-gitgutter is very well integrated into vim, but without the ability to commit stages, it stays an informational plugin.\r\n\r\n## TL;DR\r\n\r\nThis is the minimal required set of command you must know to start playing with vimagit. See [Mappings](#mappings) for a complete description.\r\n\r\nTo simply test vimagit, modify\/add\/delete\/rename some files in a git repository and open vim.\r\n\r\n- `:Magit`  \r\n  Open magit buffer with :Magit command.\r\n- ``  \r\n  Jump to next hunk with ``, or move the cursor as you like. The cursor is on a hunk.\r\n- `S`  \r\n  While the cursor is on an unstaged hunk, press `S` in Normal mode: the hunk is now staged, and appears in \"Staged changes\" section (you can also unstage a hunk from \"Staged section\" with `S`).\r\n- `CC`  \r\n  Once you have stage all the required changes, press `CC`.\r\n  - Section \"Commit message\" is shown.\r\n  - Type your commit message in this section.\r\n  - To commit, go back in Normal mode, and press `CC` (or `:w` if you prefer).\r\n  \r\nYou just created your first commit with vimagit!","install_details":"The plugin hierarchy tree respects the vim plugin standard. It is compatible with pathogen (and most probably vundle).\r\n\r\nTo install:\r\n\r\ncd ~\/.vim\/bundle\r\ngit clone https:\/\/github.com\/jreybert\/vimagit\r\n","5":"The plugin hierarchy tree respects the vim plugin standard. It is compatible with pathogen (and most probably vundle).\r\n\r\nTo install:\r\n\r\ncd ~\/.vim\/bundle\r\ngit clone https:\/\/github.com\/jreybert\/vimagit\r\n","first_name":"Jerome","6":"Jerome","last_name":"Reybert","7":"Reybert","releases":[{"0":"5252","vim_version":"7.0","1":"7.0","script_version":"1.7.3","2":"1.7.3","version_comment":"Release 1.7.3\r\n=============\r\n\r\nThis release adds some minor improvements, and fixes a lot of bugs. Most of\r\nthese has been in master branch since a long time.\r\n\r\nNew features\r\n------------\r\n\r\n* Add option to auto-close magit buffer\/window on clean state #132\r\n* Jump to source is now line precise #152 #153\r\n  Using the 'E' (for edit) mapping, cursor will now jump to the exact line\r\n  instead of the beginning of the hunk.\r\n* Smarter cursor position when staging\/refreshing.\r\n  When refreshing, the cirsor stays in the same position. When (un)staging,\r\n  cursor move to the hunk close to the current one.\r\n* Add vimagit support to vim-airline\r\n\r\nBug fixes\r\n---------\r\n\r\n* Fix freeze while refresh fix #170 #36\r\n* Fix character escape issues #156 #168\r\n  These are two old issues, which have been reproduced thanks to the issue\r\n  #168. Big up to @akrejczinger for the docker image.\r\n* Discarding untracked file results in an error in some cases fix #165\r\n* Ungraceful behaviour when opening magit outside of a git repo fix #162\r\n* Freshly created repository fails to open in vimagit fix #169\r\n* Handle commit set at the end of magit_default_sections #149\r\n","3":"Release 1.7.3\r\n=============\r\n\r\nThis release adds some minor improvements, and fixes a lot of bugs. Most of\r\nthese has been in master branch since a long time.\r\n\r\nNew features\r\n------------\r\n\r\n* Add option to auto-close magit buffer\/window on clean state #132\r\n* Jump to source is now line precise #152 #153\r\n  Using the 'E' (for edit) mapping, cursor will now jump to the exact line\r\n  instead of the beginning of the hunk.\r\n* Smarter cursor position when staging\/refreshing.\r\n  When refreshing, the cirsor stays in the same position. When (un)staging,\r\n  cursor move to the hunk close to the current one.\r\n* Add vimagit support to vim-airline\r\n\r\nBug fixes\r\n---------\r\n\r\n* Fix freeze while refresh fix #170 #36\r\n* Fix character escape issues #156 #168\r\n  These are two old issues, which have been reproduced thanks to the issue\r\n  #168. Big up to @akrejczinger for the docker image.\r\n* Discarding untracked file results in an error in some cases fix #165\r\n* Ungraceful behaviour when opening magit outside of a git repo fix #162\r\n* Freshly created repository fails to open in vimagit fix #169\r\n* Handle commit set at the end of magit_default_sections #149\r\n","package":"vimagit-1.7.3.tar.gz","4":"vimagit-1.7.3.tar.gz","src_id":"26290","5":"26290","creation_date":"1543530464","6":"1543530464"},{"0":"5252","vim_version":"7.0","1":"7.0","script_version":"1.7.2","2":"1.7.2","version_comment":"This is a *not so minor* vimagit update at the end.\r\n\r\nIt adds a nice feature, setting the cursor position on magit buffer opening at a smart position: if you are editing a file, and your cursor is in the middle of a modification, magit will open with he cursor on this hunk.\r\n\r\nUser will also notice that standard mappings (`L` or `E` to cite a few) are no longer broken in commit mode. This may a be a first step to introduce default mappings without `Shift` (see #101)\r\n\r\nIt also fixes some minor bugs (meaning these bugs were not break anything).\r\n\r\nI also want to advertise that the next major release of vimagit will see 3 new important features. Interested users are encouraged to discuss the best way to design these new features on https:\/\/gitter.im\/jreybert\/vimagit and on opened issues:\r\n* git push: push from magit buffer with ``. magit will detect the default push branch; if there is not default, or if the user used another mapping, magit will provide a way to select remote branch to push #24 \r\n* git checkout: checkout a branch with ``. Like for push, a UI must be designed to select the branch, with completion of course #141 \r\n* git stash: stage what you want (files, hunks, lines, exactly the same way as for a commit), and stash them #142 \r\n\r\nNew features\r\n-----------------\r\n\r\n* Open magit buffer with a smart cursor position. When opening magit buffer, cursor is set to current file file hunk, if any #125 \r\n* Disable most of the mappings in commit mode (i.e. when user is editing). For example, user can now use 'L' or 'E' when editing its commit message #101 #106\r\n* Magit now shows more information on top: it shows the current remote upstream branch and remote push branch. This is a first step to the git push feature!\r\n* Add VimagitLeaveCommit User autocmd. WithVimagitEnterCommit and VimagitLeaveCommit, you can now set the textwidth when you are editing your commit message (see VimagitLeaveCommit section in vimagit help) #140 \r\n* You can now use Enter to fold\/unfold a file #71\r\n\r\nBug fixes\r\n------------\r\n\r\n* Fix 'quit' behavior to something consistent: if opened with Magit (i.e. splitting the window) 'q' close the magit buffer; if opened with MagitOnly (i.e. using the current buffer), 'q' switch to the previous buffer. If magit is the last opened window, and it does not have an alternate buffer, it quits vim #137 \r\n* Fix jump to \"file already open\" abort #128\r\n* Fix warning when magit is closed with bdelete #130\r\n* Fix .gitmessage template commit duplicate on refresh #135\r\n\r\nContributors\r\n----------------\r\n\r\nUsers who have contributed to this release:\r\n* @argshook ","3":"This is a *not so minor* vimagit update at the end.\r\n\r\nIt adds a nice feature, setting the cursor position on magit buffer opening at a smart position: if you are editing a file, and your cursor is in the middle of a modification, magit will open with he cursor on this hunk.\r\n\r\nUser will also notice that standard mappings (`L` or `E` to cite a few) are no longer broken in commit mode. This may a be a first step to introduce default mappings without `Shift` (see #101)\r\n\r\nIt also fixes some minor bugs (meaning these bugs were not break anything).\r\n\r\nI also want to advertise that the next major release of vimagit will see 3 new important features. Interested users are encouraged to discuss the best way to design these new features on https:\/\/gitter.im\/jreybert\/vimagit and on opened issues:\r\n* git push: push from magit buffer with ``. magit will detect the default push branch; if there is not default, or if the user used another mapping, magit will provide a way to select remote branch to push #24 \r\n* git checkout: checkout a branch with ``. Like for push, a UI must be designed to select the branch, with completion of course #141 \r\n* git stash: stage what you want (files, hunks, lines, exactly the same way as for a commit), and stash them #142 \r\n\r\nNew features\r\n-----------------\r\n\r\n* Open magit buffer with a smart cursor position. When opening magit buffer, cursor is set to current file file hunk, if any #125 \r\n* Disable most of the mappings in commit mode (i.e. when user is editing). For example, user can now use 'L' or 'E' when editing its commit message #101 #106\r\n* Magit now shows more information on top: it shows the current remote upstream branch and remote push branch. This is a first step to the git push feature!\r\n* Add VimagitLeaveCommit User autocmd. WithVimagitEnterCommit and VimagitLeaveCommit, you can now set the textwidth when you are editing your commit message (see VimagitLeaveCommit section in vimagit help) #140 \r\n* You can now use Enter to fold\/unfold a file #71\r\n\r\nBug fixes\r\n------------\r\n\r\n* Fix 'quit' behavior to something consistent: if opened with Magit (i.e. splitting the window) 'q' close the magit buffer; if opened with MagitOnly (i.e. using the current buffer), 'q' switch to the previous buffer. If magit is the last opened window, and it does not have an alternate buffer, it quits vim #137 \r\n* Fix jump to \"file already open\" abort #128\r\n* Fix warning when magit is closed with bdelete #130\r\n* Fix .gitmessage template commit duplicate on refresh #135\r\n\r\nContributors\r\n----------------\r\n\r\nUsers who have contributed to this release:\r\n* @argshook ","package":"vimagit-1.7.2.tar.gz","4":"vimagit-1.7.2.tar.gz","src_id":"25495","5":"25495","creation_date":"1502370396","6":"1502370396"},{"0":"5252","vim_version":"7.0","1":"7.0","script_version":"1.7.1","2":"1.7.1","version_comment":"Some bugs have been reported right after the release 1.7.0\r\n\r\nFixes\r\n====\r\n\r\n* when info section is last section, commit title like \"vim: \" can be intertpreted as a modeline #120 \r\n* vimagit opens in location list #119 \r\n","3":"Some bugs have been reported right after the release 1.7.0\r\n\r\nFixes\r\n====\r\n\r\n* when info section is last section, commit title like \"vim: \" can be intertpreted as a modeline #120 \r\n* vimagit opens in location list #119 \r\n","package":"vimagit-1.7.1.tar.gz","4":"vimagit-1.7.1.tar.gz","src_id":"25002","5":"25002","creation_date":"1488224219","6":"1488224219"},{"0":"5252","vim_version":"7.0","1":"7.0","script_version":"1.7.0","2":"1.7.0","version_comment":"Release 1.7.0\r\n===========\r\n\r\nWith the new cursor behavior, commit a serie of hunk has never been so delightful! Stage one hunk and have a natural look to the next hunk in one move. \r\n\r\nAlso, think to enable vimagit support in vim-airline with `let g:airline#extensions#vimagit#enabled = 1`\r\n\r\nMajor features\r\n------------------\r\n\r\n* Smart cursor position when staging #96 #115 \r\n* Check user's commit message length #86 #116 \r\n* New mappings `` `` to jump to hunks #101\r\n* Jump through closed files too #99  \r\n* Enlarge or shrink hunks #97\r\n* Commit message with standard write commands :w :x :wq ZZ #91 \r\n* Add support for Vim-Signify #93 \r\n\r\nMinor features\r\n-------------------\r\n\r\n* Change inline help toggling mapping from 'h' to '?' #80\r\n* Add magit#show_version() and g:magit_version #69\r\n* Remove ugly 'End commit message' from vimagit buffer #84\r\n* Add `` to buffer mappings #85 \r\n* Fix inline help bug with commit section #110\r\n\r\nBug fixes\r\n------------\r\n\r\n* Handle empty commit (without staged file) and empty commit message #79\r\n* Escape vimagit path to solve space issue #89\r\n* Support commit.verbose=yes #98 \r\n* Escape dirs while chdir #89\r\n* Avoid breaking tab-local directory settings #95 \r\n* Handle old vim ~ 7.4-0 fnameescape behavior on Windows #108 \r\n* Fix E871 error when staging #117 \r\n* Show custom mapping in inline help  #103 \r\n\r\nContributors\r\n---------------\r\n\r\nThanks to @hkupty @scps950707 @Alok @aschrab @thirtythreeforty @olshevskiy87 @poohzrn","3":"Release 1.7.0\r\n===========\r\n\r\nWith the new cursor behavior, commit a serie of hunk has never been so delightful! Stage one hunk and have a natural look to the next hunk in one move. \r\n\r\nAlso, think to enable vimagit support in vim-airline with `let g:airline#extensions#vimagit#enabled = 1`\r\n\r\nMajor features\r\n------------------\r\n\r\n* Smart cursor position when staging #96 #115 \r\n* Check user's commit message length #86 #116 \r\n* New mappings `` `` to jump to hunks #101\r\n* Jump through closed files too #99  \r\n* Enlarge or shrink hunks #97\r\n* Commit message with standard write commands :w :x :wq ZZ #91 \r\n* Add support for Vim-Signify #93 \r\n\r\nMinor features\r\n-------------------\r\n\r\n* Change inline help toggling mapping from 'h' to '?' #80\r\n* Add magit#show_version() and g:magit_version #69\r\n* Remove ugly 'End commit message' from vimagit buffer #84\r\n* Add `` to buffer mappings #85 \r\n* Fix inline help bug with commit section #110\r\n\r\nBug fixes\r\n------------\r\n\r\n* Handle empty commit (without staged file) and empty commit message #79\r\n* Escape vimagit path to solve space issue #89\r\n* Support commit.verbose=yes #98 \r\n* Escape dirs while chdir #89\r\n* Avoid breaking tab-local directory settings #95 \r\n* Handle old vim ~ 7.4-0 fnameescape behavior on Windows #108 \r\n* Fix E871 error when staging #117 \r\n* Show custom mapping in inline help  #103 \r\n\r\nContributors\r\n---------------\r\n\r\nThanks to @hkupty @scps950707 @Alok @aschrab @thirtythreeforty @olshevskiy87 @poohzrn","package":"vimagit-1.7.0.tar.gz","4":"vimagit-1.7.0.tar.gz","src_id":"24991","5":"24991","creation_date":"1487890604","6":"1487890604"},{"0":"5252","vim_version":"7.0","1":"7.0","script_version":"1.6.0","2":"1.6.0","version_comment":"Release 1.6.0\r\n=============\r\n\r\nNew feature *jump* is really awesome, you must try it!\r\n\r\nFeatures\r\n--------\r\n\r\n* From a hunk in the magit buffer, press *E* and *jump* the corresponding file\r\n  at the diff position. If this file is already opened in a window, cursor move\r\n  to this window.\r\n* Add events at key points in magit buffer. User can plug commands to these\r\n  events. This new feature brings the two next features:\r\n  * If vim-gitgutter is installed, auto update its signs when git status is\r\n    updated.\r\n  * You can find in help a tip to enter in commit mode in insert mode.\r\n* User can set its own git exec binary with g:magit_git_cmd variable.\r\n\r\nFixes\r\n-----\r\n\r\n* Commit message is preserved when the magit buffer is refreshed (fix #57)\r\n* It is now possible to unstage by selection (fix #32)\r\n* When opening a magit session, if a magit buffer for this git repository is\r\n  already open, jump to this buffer.\r\n* Inline help shows mapped key instead of default (fix #72)\r\n* Fix peculiar folding behavior when magit buffer is refreshing.\r\n","3":"Release 1.6.0\r\n=============\r\n\r\nNew feature *jump* is really awesome, you must try it!\r\n\r\nFeatures\r\n--------\r\n\r\n* From a hunk in the magit buffer, press *E* and *jump* the corresponding file\r\n  at the diff position. If this file is already opened in a window, cursor move\r\n  to this window.\r\n* Add events at key points in magit buffer. User can plug commands to these\r\n  events. This new feature brings the two next features:\r\n  * If vim-gitgutter is installed, auto update its signs when git status is\r\n    updated.\r\n  * You can find in help a tip to enter in commit mode in insert mode.\r\n* User can set its own git exec binary with g:magit_git_cmd variable.\r\n\r\nFixes\r\n-----\r\n\r\n* Commit message is preserved when the magit buffer is refreshed (fix #57)\r\n* It is now possible to unstage by selection (fix #32)\r\n* When opening a magit session, if a magit buffer for this git repository is\r\n  already open, jump to this buffer.\r\n* Inline help shows mapped key instead of default (fix #72)\r\n* Fix peculiar folding behavior when magit buffer is refreshing.\r\n","package":"vimagit-1.6.0.tgz","4":"vimagit-1.6.0.tgz","src_id":"24103","5":"24103","creation_date":"1458075239","6":"1458075239"},{"0":"5252","vim_version":"7.0","1":"7.0","script_version":"1.5.2","2":"1.5.2","version_comment":"Release 1.5.2\r\n=============\r\n\r\nAlmost a major release, with some cool new feature. But the release 1.6 will be reaaally cool!\r\n\r\nFeatures\r\n--------\r\n\r\n* add command CU (commit undo) to close commit section (fix #55)\r\n* add g:magit_discard_untracked_do_delete option (fix #66)\r\n  when set, discard an untracked file will actually delete this file\r\n* support 'typechanged' git status type\r\n\r\nFixes\r\n-----\r\n\r\n* clear undo history after each update_buffer() call (refs #64)\r\n  undo in magit buffer did the user believe that it may undoes some vimagit\r\n  actions: it is not! magit buffer undo history is wiped at each refresh;\r\n  which means undo still works while the user is typing its commit message\r\n  for example.\r\n* binary file detection is done with git diff (fix #60, #61)\r\n  it fixes false positive binary file detection, binary file detection on\r\n  Windows, and may eventually speed up the refresh process :)\r\n* output an understandable message when user tries ot discard an untracked file (fix #58)\r\n* remove unwanted --No lines in buffer-- in status line when opening magit buffer (fix #56)\r\n* use 'diff -p' instead of 'diff --patch' (fix #52)\r\n* better handling of some command line error code and improve some error messages\r\n* set local foldnestmax (fix #62)\r\n","3":"Release 1.5.2\r\n=============\r\n\r\nAlmost a major release, with some cool new feature. But the release 1.6 will be reaaally cool!\r\n\r\nFeatures\r\n--------\r\n\r\n* add command CU (commit undo) to close commit section (fix #55)\r\n* add g:magit_discard_untracked_do_delete option (fix #66)\r\n  when set, discard an untracked file will actually delete this file\r\n* support 'typechanged' git status type\r\n\r\nFixes\r\n-----\r\n\r\n* clear undo history after each update_buffer() call (refs #64)\r\n  undo in magit buffer did the user believe that it may undoes some vimagit\r\n  actions: it is not! magit buffer undo history is wiped at each refresh;\r\n  which means undo still works while the user is typing its commit message\r\n  for example.\r\n* binary file detection is done with git diff (fix #60, #61)\r\n  it fixes false positive binary file detection, binary file detection on\r\n  Windows, and may eventually speed up the refresh process :)\r\n* output an understandable message when user tries ot discard an untracked file (fix #58)\r\n* remove unwanted --No lines in buffer-- in status line when opening magit buffer (fix #56)\r\n* use 'diff -p' instead of 'diff --patch' (fix #52)\r\n* better handling of some command line error code and improve some error messages\r\n* set local foldnestmax (fix #62)\r\n","package":"vimagit-1.5.2.tgz","4":"vimagit-1.5.2.tgz","src_id":"24007","5":"24007","creation_date":"1455398537","6":"1455398537"},{"0":"5252","vim_version":"7.0","1":"7.0","script_version":"1.5.1","2":"1.5.1","version_comment":"Fixes\r\n\r\n* fix next\/prev jump folding\r\n* fix modified\/untracked content in submodule (fix #49)\r\n","3":"Fixes\r\n\r\n* fix next\/prev jump folding\r\n* fix modified\/untracked content in submodule (fix #49)\r\n","package":"vimagit-1.5.1.tgz","4":"vimagit-1.5.1.tgz","src_id":"23770","5":"23770","creation_date":"1448967905","6":"1448967905"},{"0":"5252","vim_version":"7.0","1":"7.0","script_version":"1.5.0","2":"1.5.0","version_comment":"Features\r\n\r\n* vimagit is now able to handle multiple git repositories (fix #44,#34,#29).\r\n* add mappings N and P to jump to next and previous hunk (fix #25).\r\n* reorder magit display: display modified files first.\r\n* disable inline help by default (fix #46). It is always possible to switch\r\ninline help display with 'h', or with g:magit_show_help\r\n* rework magit buffer color syntax.\r\n* display commit mode in Info section.\r\n* rename magit buffer, now named after git repository path, e.g.\r\nmagit:\/\/\/path\/to\/git\/repo\/\r\n* add MagitOnly command. It can be used to craft a bash alias like:\r\nalias magit='vim -c MagitOnly'\r\n\r\nFixes\r\n\r\n* safe and smart handling of quit command (fix #41,#43).\r\n* close vimagit window if there is another window.\r\n* switch to alternate buffer if any.\r\n* close vim if magit buffer the only buffer.\r\n* disable ':w' mapping, which was not safe. This feature will be re inserted\r\nwith a safer method later.\r\n","3":"Features\r\n\r\n* vimagit is now able to handle multiple git repositories (fix #44,#34,#29).\r\n* add mappings N and P to jump to next and previous hunk (fix #25).\r\n* reorder magit display: display modified files first.\r\n* disable inline help by default (fix #46). It is always possible to switch\r\ninline help display with 'h', or with g:magit_show_help\r\n* rework magit buffer color syntax.\r\n* display commit mode in Info section.\r\n* rename magit buffer, now named after git repository path, e.g.\r\nmagit:\/\/\/path\/to\/git\/repo\/\r\n* add MagitOnly command. It can be used to craft a bash alias like:\r\nalias magit='vim -c MagitOnly'\r\n\r\nFixes\r\n\r\n* safe and smart handling of quit command (fix #41,#43).\r\n* close vimagit window if there is another window.\r\n* switch to alternate buffer if any.\r\n* close vim if magit buffer the only buffer.\r\n* disable ':w' mapping, which was not safe. This feature will be re inserted\r\nwith a safer method later.\r\n","package":"vimagit-1.5.0.tgz","4":"vimagit-1.5.0.tgz","src_id":"23768","5":"23768","creation_date":"1448927347","6":"1448927347"},{"0":"5252","vim_version":"7.0","1":"7.0","script_version":"1.4.2","2":"1.4.2","version_comment":"Some bug fixes and performance improvements.\r\n\r\nEnhancements:\r\n\r\n* smarter way to handle magit buffer:\r\n     - improve some internal mechanisms, which should improve performances for huge repositories\r\n     - by default, do not show untracked\/deleted\/added\/renamed files diffs (ref #28)\r\n       see g:magit_default_show_all_files new behavior\r\n* add g:magit_default_sections to let user choose which sections are displayed (fix #37) user can now choose which sections to display, and in which order\r\n\r\nBug fixes:\r\n\r\n* magit buffer become empty after switching to other window and back (#35)\r\n* remove warning when opening magit buffer\r\n* check that magit buffer exists before removing it (refs #39)","3":"Some bug fixes and performance improvements.\r\n\r\nEnhancements:\r\n\r\n* smarter way to handle magit buffer:\r\n     - improve some internal mechanisms, which should improve performances for huge repositories\r\n     - by default, do not show untracked\/deleted\/added\/renamed files diffs (ref #28)\r\n       see g:magit_default_show_all_files new behavior\r\n* add g:magit_default_sections to let user choose which sections are displayed (fix #37) user can now choose which sections to display, and in which order\r\n\r\nBug fixes:\r\n\r\n* magit buffer become empty after switching to other window and back (#35)\r\n* remove warning when opening magit buffer\r\n* check that magit buffer exists before removing it (refs #39)","package":"vimagit-1.4.2.tar.gz","4":"vimagit-1.4.2.tar.gz","src_id":"23728","5":"23728","creation_date":"1447230088","6":"1447230088"},{"0":"5252","vim_version":"7.0","1":"7.0","script_version":"1.4.1","2":"1.4.1","version_comment":"# Fixes\r\n\r\n* fix add binary file (fixes #27)\r\n* fix some display problem (Unstaged changes may not be highlighted)\r\n* fix reset and discard for binary files\r\n\r\n# Features\r\n\r\n* git works in a clean environment, without any configuration","3":"# Fixes\r\n\r\n* fix add binary file (fixes #27)\r\n* fix some display problem (Unstaged changes may not be highlighted)\r\n* fix reset and discard for binary files\r\n\r\n# Features\r\n\r\n* git works in a clean environment, without any configuration","package":"vimagit-1.4.1.tar.gz","4":"vimagit-1.4.1.tar.gz","src_id":"23695","5":"23695","creation_date":"1446339306","6":"1446339306"},{"0":"5252","vim_version":"7.0","1":"7.0","script_version":"1.4","2":"1.4","version_comment":"This is a major step for vimagit. It should now contain all primary command needed for staging. Then, this release should be the real 1.0 version.\r\n\r\n# Features\r\n\r\n* Stage parts of hunk (fixes #8 and #19)\r\n  * select some with v, then stage your selection with S\r\n  * stage a single line with L\r\n  * mark lines (can be non contiguous) with M, then stage marked lines in the hunk with S\r\n* Stage single files in new directories (fixes #10)\r\n* New options (fixes #18)\r\n  * g:magit_default_show_all_files to define if file diffs are shown or not at magit buffer opening.\r\n  * If magit buffer contains more than g:magit_warning_max_lines (default 10000) lines to display, user is asked if he wants to display all these lines. \r\n  * g:magit_default_fold_level to define foldlevel of magit buffer.\r\n  * These options can be overriden with new magit#show_magit() parameters (allowing user to define its own mappings\/commands)\r\n* File display is now sorted.\r\n* Show submodule diffs (fixes #12)\r\n\r\n# Fixes\r\n\r\n* No bugs have been reported since release 1.3.","3":"This is a major step for vimagit. It should now contain all primary command needed for staging. Then, this release should be the real 1.0 version.\r\n\r\n# Features\r\n\r\n* Stage parts of hunk (fixes #8 and #19)\r\n  * select some with v, then stage your selection with S\r\n  * stage a single line with L\r\n  * mark lines (can be non contiguous) with M, then stage marked lines in the hunk with S\r\n* Stage single files in new directories (fixes #10)\r\n* New options (fixes #18)\r\n  * g:magit_default_show_all_files to define if file diffs are shown or not at magit buffer opening.\r\n  * If magit buffer contains more than g:magit_warning_max_lines (default 10000) lines to display, user is asked if he wants to display all these lines. \r\n  * g:magit_default_fold_level to define foldlevel of magit buffer.\r\n  * These options can be overriden with new magit#show_magit() parameters (allowing user to define its own mappings\/commands)\r\n* File display is now sorted.\r\n* Show submodule diffs (fixes #12)\r\n\r\n# Fixes\r\n\r\n* No bugs have been reported since release 1.3.","package":"vimagit-1.4.tar.gz","4":"vimagit-1.4.tar.gz","src_id":"23684","5":"23684","creation_date":"1445781385","6":"1445781385"},{"0":"5252","vim_version":"7.0","1":"7.0","script_version":"1.3","2":"1.3","version_comment":"Features\r\n\r\n- hide file diffs: to hide\/unhide diffs for a file, move the cursor to the filename and press (Enter). It allows vimagit to be fast when there is a lot of diffs in a repository.\r\n- zo, zO, zc, zC mappings on a filename hide\/unhide file diffs.\r\n- modify hunk before staging: in the Magit buffer, it is possible to modify a hunk before staging it. Only \\'+\\' lines can be modified. No lines can be deleted or added for the moment. (fixes #9).\r\n- handle new empty files and new symlink (fix #11).\r\n- handle binary files (fix #13).\r\n- stage\/unstage\/ignore\/discard a file with cursor on the filename.\r\n- add global mapping M to open magit buffer (it can be overwritten with g:magit_show_magit_mapping).\r\n- remove \\'C\\' default mapping.\r\n\r\nFixes\r\n\r\n- fix staging issue: sometimes, staging a hunk was failing.\r\n- handle filenames with spaces.","3":"Features\r\n\r\n- hide file diffs: to hide\/unhide diffs for a file, move the cursor to the filename and press (Enter). It allows vimagit to be fast when there is a lot of diffs in a repository.\r\n- zo, zO, zc, zC mappings on a filename hide\/unhide file diffs.\r\n- modify hunk before staging: in the Magit buffer, it is possible to modify a hunk before staging it. Only \\'+\\' lines can be modified. No lines can be deleted or added for the moment. (fixes #9).\r\n- handle new empty files and new symlink (fix #11).\r\n- handle binary files (fix #13).\r\n- stage\/unstage\/ignore\/discard a file with cursor on the filename.\r\n- add global mapping M to open magit buffer (it can be overwritten with g:magit_show_magit_mapping).\r\n- remove \\'C\\' default mapping.\r\n\r\nFixes\r\n\r\n- fix staging issue: sometimes, staging a hunk was failing.\r\n- handle filenames with spaces.","package":"vimagit-1.3.tar.gz","4":"vimagit-1.3.tar.gz","src_id":"23673","5":"23673","creation_date":"1444904120","6":"1444904120"},{"0":"5252","vim_version":"7.0","1":"7.0","script_version":"1.2","2":"1.2","version_comment":"Fixes:\r\n- read COMMIT_EDITMSG only if exists (commit command failed for fresh new git directory)\r\n- fix issue of some rare hunk staging (because of some whitespaces)\r\n\r\nFeatures:\r\n- stage\/unstage\/ignore on file header now works\r\n- add info section (fix #6)","3":"Fixes:\r\n- read COMMIT_EDITMSG only if exists (commit command failed for fresh new git directory)\r\n- fix issue of some rare hunk staging (because of some whitespaces)\r\n\r\nFeatures:\r\n- stage\/unstage\/ignore on file header now works\r\n- add info section (fix #6)","package":"vimagit.tgz","4":"vimagit.tgz","src_id":"23656","5":"23656","creation_date":"1444307227","6":"1444307227"},{"0":"5252","vim_version":"7.0","1":"7.0","script_version":"1.1","2":"1.1","version_comment":"Fixes:\r\n- add wrappers to system and systemlist, when vim doesn't support system with List (available since vim v7.4.248)\r\n- fix git diff failing when cwd is not in top dir (it ends with an empty Magit buffer)\r\n- ensure to not use external diff if any\r\n- Check commentChar from git config\r\n\r\nNew mappings:\r\n- default discard mapping is now DDD, to avoid mistype\r\n- map :w to commit\r\n- close Magit buffer with q\r\n\r\nInternal:\r\n- put some first tests in regression, with travis","3":"Fixes:\r\n- add wrappers to system and systemlist, when vim doesn't support system with List (available since vim v7.4.248)\r\n- fix git diff failing when cwd is not in top dir (it ends with an empty Magit buffer)\r\n- ensure to not use external diff if any\r\n- Check commentChar from git config\r\n\r\nNew mappings:\r\n- default discard mapping is now DDD, to avoid mistype\r\n- map :w to commit\r\n- close Magit buffer with q\r\n\r\nInternal:\r\n- put some first tests in regression, with travis","package":"vimagit.tgz","4":"vimagit.tgz","src_id":"23651","5":"23651","creation_date":"1444199264","6":"1444199264"},{"0":"5252","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"vimagit.tgz","4":"vimagit.tgz","src_id":"23631","5":"23631","creation_date":"1443652729","6":"1443652729"}]},"5251":{"script_id":"5251","0":"5251","script_name":"robcolors","1":"robcolors","script_type":"color scheme","2":"color scheme","summary":"Color scheme by Robert Nowtniak","3":"Color scheme by Robert Nowtniak","description":"Color script from http:\/\/robert.nowotniak.com\/pl\/other\/vim\/ by Robert Nowotniak. Proably abandoware. Created in 2004-10-21","4":"Color script from http:\/\/robert.nowotniak.com\/pl\/other\/vim\/ by Robert Nowotniak. Proably abandoware. Created in 2004-10-21","install_details":"paste robcolors.vim this $VIMRUNTIME\/colors","5":"paste robcolors.vim this $VIMRUNTIME\/colors","first_name":"xxx","6":"xxx","last_name":"xxx","7":"xxx","releases":[{"0":"5251","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"robcolors.vim","4":"robcolors.vim","src_id":"23627","5":"23627","creation_date":"1443542652","6":"1443542652"}]},"5250":{"script_id":"5250","0":"5250","script_name":"vim-json-line-format","1":"vim-json-line-format","script_type":"utility","2":"utility","summary":"format json line","3":"format json line","description":"格式化json文本行(format json text line)\r\n================\r\n\r\n         _ ____   ___  _   _     _     ___ _   _ _____    _____ ___  ____  __  __    _  _____\r\n        | \/ ___| \/ _ \\| \\ | |   | |   |_ _| \\ | | ____|  |  ___\/ _ \\|  _ \\|  \\\/  |  \/ \\|_   _|\r\n     _  | \\___ \\| | | |  \\| |___| |    | ||  \\| |  _| ___| |_ | | | | |_) | |\\\/| | \/ _ \\ | |\r\n    | |_| |___) | |_| | |\\  |___| |___ | || |\\  | |__|___|  _|| |_| |  _ <| |  | |\/ ___ \\| |\r\n     \\___\/|____\/ \\___\/|_| \\_|   |_____|___|_| \\_|_____|  |_|   \\___\/|_| \\_\\_|  |_\/_\/   \\_\\_|\r\n\r\n\r\nif你用vim打开某文本内容为每行一个json的文本文件，内容如下：\r\n\r\nIf you open a text by VIM which contents are json lines text, such as:\r\n\r\n    {\"question\": \"\\u53d1\\u5458\\u5de5\\u7684\\u4e1c\\u897f\", \"choices\": [\"\\u6781\\u6b63\", \"\\u504f\\u6b63\", \"\\u4e2d\\u6027\", \"\\u504f\\u8d1f\", \"\\u6781\\u8d1f\", \"\\u975e\\u8bc4\\u4ef7\"]}\r\n    {\"question\": \"\\u6613\\u8fc5\\u8fd9\\u6837\\u6ca1\\u6cd5\\u6bd4\", \"choices\": [\"\\u6781\\u6b63\", \"\\u504f\\u6b63\", \"\\u4e2d\\u6027\", \"\\u504f\\u8d1f\", \"\\u6781\\u8d1f\", \"\\u975e\\u8bc4\\u4ef7\"]}\r\n    {\"question\": \"\\u5f88\\u591a\\u4e1c\\u897f\\u5df2\\u7ecf\\u6bd4\", \"choices\": [\"\\u6781\\u6b63\", \"\\u504f\\u6b63\", \"\\u4e2d\\u6027\", \"\\u504f\\u8d1f\", \"\\u6781\\u8d1f\", \"\\u975e\\u8bc4\\u4ef7\"]}\r\n\r\n由于编码和没有换行的问题不便于查看，或许说根本他妈的就没法看！那么！请立刻检查系好您的安全带，因为这个插件可以让你fly！\r\n\r\nThese json lines are inconvenient for human to read it, because of formating and encoding. Using this plugin, you can these lines easily!\r\n\r\n![](pic.gif)\r\n\r\n###安装(Install)\r\n\r\n\r\n1. 可以直接将`plugin\/json_line_format.vim`复制到你的`.vim\/plugin`下就ok\r\n(First Way: Copy `plugin\/json_line_format.vim` to your `.vim\/plugin`)\r\n\r\n2. 如果是使用Vundle，那么在你的`.vimrc`中的plugin管理中添加\r\n\r\n`Plugin 'axiaoxin\/vim-json-line-format'`\r\n\r\n然后在VIM中`:PluginInstall`你懂的哟\r\n\r\n(Second way: if you use Vundle, add `Plugin 'axiaoxin\/vim-json-line-format'` in your `.vimrc`, then use `:PluginInstall` to install this plugin)\r\n\r\n###用法(Usage)\r\n\r\n打开文件，以`normal`方式在需要查看的行上按`jp`快捷键即可在底部打印它格式化后的样子，使用`jw`快捷键直接将其修改为格式化后的json\r\n\r\nOpen a file in `Normal mode`, move your cursor on the json line, use `jp` to show formated json by print it, use `jw` could change the text to formatted json.\r\n\r\n非正确json格式无法格式化\r\n\r\nerror json can not format!\r\n\r\nlink: \r\n","4":"格式化json文本行(format json text line)\r\n================\r\n\r\n         _ ____   ___  _   _     _     ___ _   _ _____    _____ ___  ____  __  __    _  _____\r\n        | \/ ___| \/ _ \\| \\ | |   | |   |_ _| \\ | | ____|  |  ___\/ _ \\|  _ \\|  \\\/  |  \/ \\|_   _|\r\n     _  | \\___ \\| | | |  \\| |___| |    | ||  \\| |  _| ___| |_ | | | | |_) | |\\\/| | \/ _ \\ | |\r\n    | |_| |___) | |_| | |\\  |___| |___ | || |\\  | |__|___|  _|| |_| |  _ <| |  | |\/ ___ \\| |\r\n     \\___\/|____\/ \\___\/|_| \\_|   |_____|___|_| \\_|_____|  |_|   \\___\/|_| \\_\\_|  |_\/_\/   \\_\\_|\r\n\r\n\r\nif你用vim打开某文本内容为每行一个json的文本文件，内容如下：\r\n\r\nIf you open a text by VIM which contents are json lines text, such as:\r\n\r\n    {\"question\": \"\\u53d1\\u5458\\u5de5\\u7684\\u4e1c\\u897f\", \"choices\": [\"\\u6781\\u6b63\", \"\\u504f\\u6b63\", \"\\u4e2d\\u6027\", \"\\u504f\\u8d1f\", \"\\u6781\\u8d1f\", \"\\u975e\\u8bc4\\u4ef7\"]}\r\n    {\"question\": \"\\u6613\\u8fc5\\u8fd9\\u6837\\u6ca1\\u6cd5\\u6bd4\", \"choices\": [\"\\u6781\\u6b63\", \"\\u504f\\u6b63\", \"\\u4e2d\\u6027\", \"\\u504f\\u8d1f\", \"\\u6781\\u8d1f\", \"\\u975e\\u8bc4\\u4ef7\"]}\r\n    {\"question\": \"\\u5f88\\u591a\\u4e1c\\u897f\\u5df2\\u7ecf\\u6bd4\", \"choices\": [\"\\u6781\\u6b63\", \"\\u504f\\u6b63\", \"\\u4e2d\\u6027\", \"\\u504f\\u8d1f\", \"\\u6781\\u8d1f\", \"\\u975e\\u8bc4\\u4ef7\"]}\r\n\r\n由于编码和没有换行的问题不便于查看，或许说根本他妈的就没法看！那么！请立刻检查系好您的安全带，因为这个插件可以让你fly！\r\n\r\nThese json lines are inconvenient for human to read it, because of formating and encoding. Using this plugin, you can these lines easily!\r\n\r\n![](pic.gif)\r\n\r\n###安装(Install)\r\n\r\n\r\n1. 可以直接将`plugin\/json_line_format.vim`复制到你的`.vim\/plugin`下就ok\r\n(First Way: Copy `plugin\/json_line_format.vim` to your `.vim\/plugin`)\r\n\r\n2. 如果是使用Vundle，那么在你的`.vimrc`中的plugin管理中添加\r\n\r\n`Plugin 'axiaoxin\/vim-json-line-format'`\r\n\r\n然后在VIM中`:PluginInstall`你懂的哟\r\n\r\n(Second way: if you use Vundle, add `Plugin 'axiaoxin\/vim-json-line-format'` in your `.vimrc`, then use `:PluginInstall` to install this plugin)\r\n\r\n###用法(Usage)\r\n\r\n打开文件，以`normal`方式在需要查看的行上按`jp`快捷键即可在底部打印它格式化后的样子，使用`jw`快捷键直接将其修改为格式化后的json\r\n\r\nOpen a file in `Normal mode`, move your cursor on the json line, use `jp` to show formated json by print it, use `jw` could change the text to formatted json.\r\n\r\n非正确json格式无法格式化\r\n\r\nerror json can not format!\r\n\r\nlink: \r\n","install_details":"可以直接将plugin\/json_line_format.vim复制到你的.vim\/plugin下就ok\r\n\r\n如果是使用Vundle，那么在你的.vimrc中的plugin管理中添加\r\n\r\nPlugin 'axiaoxin\/vim-json-line-format'\r\n\r\n然后在VIM中:PluginInstall你懂的哟","5":"可以直接将plugin\/json_line_format.vim复制到你的.vim\/plugin下就ok\r\n\r\n如果是使用Vundle，那么在你的.vimrc中的plugin管理中添加\r\n\r\nPlugin 'axiaoxin\/vim-json-line-format'\r\n\r\n然后在VIM中:PluginInstall你懂的哟","first_name":"xiaoxin","6":"xiaoxin","last_name":"a","7":"a","releases":[{"0":"5250","vim_version":"7.0","1":"7.0","script_version":"0.1.1","2":"0.1.1","version_comment":"update readme in English","3":"update readme in English","package":"vim-json-line-format.zip","4":"vim-json-line-format.zip","src_id":"23622","5":"23622","creation_date":"1443417540","6":"1443417540"},{"0":"5250","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"vim-json-line-format.zip","4":"vim-json-line-format.zip","src_id":"23616","5":"23616","creation_date":"1443155728","6":"1443155728"}]},"5249":{"script_id":"5249","0":"5249","script_name":"togglenumber","1":"togglenumber","script_type":"utility","2":"utility","summary":"easy toggle between different numbering modes in vim","3":"easy toggle between different numbering modes in vim","description":"Easy toggle between different number modes in vim: nonumber, absolute and relative number, with just one key sequence to rule it all. Most other plugins don\\'t provide a seamless way to do all 3 modes at once.\r\n\r\nCycle through the modes by invoking the key sequence n repeatedly.\r\n\r\nSource: https:\/\/github.com\/tkhoa2711\/vim-togglenumber\r\n","4":"Easy toggle between different number modes in vim: nonumber, absolute and relative number, with just one key sequence to rule it all. Most other plugins don\\'t provide a seamless way to do all 3 modes at once.\r\n\r\nCycle through the modes by invoking the key sequence n repeatedly.\r\n\r\nSource: https:\/\/github.com\/tkhoa2711\/vim-togglenumber\r\n","install_details":"If you use pathogen, clone the repo as below:\r\n\r\ngit clone https:\/\/github.com\/tkhoa2711\/vim-togglenumber.git ~\/.vim\/bundle\/vim-togglenumber\r\n\r\nAfter having you help tags regenerated, you can view the reference manual with :help togglenumber.","5":"If you use pathogen, clone the repo as below:\r\n\r\ngit clone https:\/\/github.com\/tkhoa2711\/vim-togglenumber.git ~\/.vim\/bundle\/vim-togglenumber\r\n\r\nAfter having you help tags regenerated, you can view the reference manual with :help togglenumber.","first_name":"Khoa","6":"Khoa","last_name":"Le","7":"Le","releases":[{"0":"5249","vim_version":"7.3","1":"7.3","script_version":"1.2","2":"1.2","version_comment":"the default numbering mode is nonumber, as by vim's default","3":"the default numbering mode is nonumber, as by vim's default","package":"vim-togglenumber.zip","4":"vim-togglenumber.zip","src_id":"23869","5":"23869","creation_date":"1451921821","6":"1451921821"},{"0":"5249","vim_version":"7.3","1":"7.3","script_version":"1.1","2":"1.1","version_comment":"Make it compatible with vim version >= 7.4","3":"Make it compatible with vim version >= 7.4","package":"vim-togglenumber.zip","4":"vim-togglenumber.zip","src_id":"23708","5":"23708","creation_date":"1446480958","6":"1446480958"},{"0":"5249","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"vim-togglenumber.zip","4":"vim-togglenumber.zip","src_id":"23615","5":"23615","creation_date":"1443139386","6":"1443139386"}]},"5248":{"script_id":"5248","0":"5248","script_name":"logo","1":"logo","script_type":"syntax","2":"syntax","summary":"horrible language, teoretical for learn programming language.","3":"horrible language, teoretical for learn programming language.","description":"If you notice that missing some atom syntax, please edit\/add it.\r\n\r\ngithub: https:\/\/github.com\/kompowiec2\/logo.vim","4":"If you notice that missing some atom syntax, please edit\/add it.\r\n\r\ngithub: https:\/\/github.com\/kompowiec2\/logo.vim","install_details":"add file from vim74\/syntax\r\n\r\nif you run:\r\nset syntax=logo.vim","5":"add file from vim74\/syntax\r\n\r\nif you run:\r\nset syntax=logo.vim","first_name":"xxx","6":"xxx","last_name":"xxx","7":"xxx","releases":[{"0":"5248","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"logo.vim","4":"logo.vim","src_id":"23614","5":"23614","creation_date":"1443115327","6":"1443115327"}]},"5247":{"script_id":"5247","0":"5247","script_name":"quickBuf","1":"quickBuf","script_type":"utility","2":"utility","summary":"Simple and quick buffer explorer","3":"Simple and quick buffer explorer","description":"See latest version on github: https:\/\/github.com\/viaa\/VimPlugins\r\n\r\n\" Documentation\r\n    \" Name: quickBuf.vim\r\n    \" Version: 2.1.2.1\r\n    \" Description: Simple and quick buffer explorer\r\n    \" Author: Alexandre Viau (alexandreviau@gmail.com)\r\n    \" Thanks to: Xaizek\r\n    \" Installation: Copy the plugin to the vim plugin directory.\r\n\r\n\" Usage:\r\n    \" Press b to show the buffer list in the current window\r\n    \" Press B to show the buffer list in a new tab\r\n    \" Press  or 'o' once on the buffer list to open a buffer\r\n    \" Press  or dd once on the buffer list to delete a buffer\r\n    \" Press 't' once on the buffer list to view buffer in a tab\r\n    \" Press ctrl-o after selecting a buffer to return to the buffer list\r\n\" Todo:\r\n\"   s0 When they are more than 1 match for a buffer, delete all\r\n\r\n\" History:\r\n    \" 1.0 Initial release\r\n    \" 1.1 Switched b for B\r\n    \" 1.2 I changed the fixed path c:\/temp\/buffers.txt to $tmp\/buffers.txt\r\n    \" 1.2.1 I put the buffers.txt path to a variable\r\n    \" 1.2.2 I added 'dd' to delete the buffer under the current line and fixed error messages delete some buffers\r\n    \" 1.2.3 I changed the mappings b to open the buffer list in the current buffer, B to open the buffer list in a new tab\r\n    \" 2.0 Many changes from Xaizek (thanks!). He remove the usage of the paste register, added unix line endings and changed the commands so the buffers are managed by their numbers, which is better than name, so now it works with buffers like [Scratch]\r\n    \" 2.1 I added commands to delete the empty lines and the current buffer and remove some commands from being registered to the jump list (thanks to Xaizek for this tip). I replaced also 0w by 0^ in the commands to get the numbers if they start at the beginning of the line.\r\n    \" 2.1.1 Xaizek: There were also issues with temporary file as $TMP is not always defined and header wasn't updated to mention  and fixed the t mapping.\r\n    \" 2.1.2 Added a mapping to 'o' to open the current buffer under the cursor\r\n    \" 2.1.2.1 I updated the version number in the file","4":"See latest version on github: https:\/\/github.com\/viaa\/VimPlugins\r\n\r\n\" Documentation\r\n    \" Name: quickBuf.vim\r\n    \" Version: 2.1.2.1\r\n    \" Description: Simple and quick buffer explorer\r\n    \" Author: Alexandre Viau (alexandreviau@gmail.com)\r\n    \" Thanks to: Xaizek\r\n    \" Installation: Copy the plugin to the vim plugin directory.\r\n\r\n\" Usage:\r\n    \" Press b to show the buffer list in the current window\r\n    \" Press B to show the buffer list in a new tab\r\n    \" Press  or 'o' once on the buffer list to open a buffer\r\n    \" Press  or dd once on the buffer list to delete a buffer\r\n    \" Press 't' once on the buffer list to view buffer in a tab\r\n    \" Press ctrl-o after selecting a buffer to return to the buffer list\r\n\" Todo:\r\n\"   s0 When they are more than 1 match for a buffer, delete all\r\n\r\n\" History:\r\n    \" 1.0 Initial release\r\n    \" 1.1 Switched b for B\r\n    \" 1.2 I changed the fixed path c:\/temp\/buffers.txt to $tmp\/buffers.txt\r\n    \" 1.2.1 I put the buffers.txt path to a variable\r\n    \" 1.2.2 I added 'dd' to delete the buffer under the current line and fixed error messages delete some buffers\r\n    \" 1.2.3 I changed the mappings b to open the buffer list in the current buffer, B to open the buffer list in a new tab\r\n    \" 2.0 Many changes from Xaizek (thanks!). He remove the usage of the paste register, added unix line endings and changed the commands so the buffers are managed by their numbers, which is better than name, so now it works with buffers like [Scratch]\r\n    \" 2.1 I added commands to delete the empty lines and the current buffer and remove some commands from being registered to the jump list (thanks to Xaizek for this tip). I replaced also 0w by 0^ in the commands to get the numbers if they start at the beginning of the line.\r\n    \" 2.1.1 Xaizek: There were also issues with temporary file as $TMP is not always defined and header wasn't updated to mention  and fixed the t mapping.\r\n    \" 2.1.2 Added a mapping to 'o' to open the current buffer under the cursor\r\n    \" 2.1.2.1 I updated the version number in the file","install_details":"Copy the plugin to the vim plugin directory.","5":"Copy the plugin to the vim plugin directory.","first_name":"Alexandre","6":"Alexandre","last_name":"Viau","7":"Viau","releases":[{"0":"5247","vim_version":"7.0","1":"7.0","script_version":"2.1.2.1","2":"2.1.2.1","version_comment":"\" 2.1.2.1 I updated the version number in the file\r\n","3":"\" 2.1.2.1 I updated the version number in the file\r\n","package":"quickBuf.vim","4":"quickBuf.vim","src_id":"23626","5":"23626","creation_date":"1443528700","6":"1443528700"},{"0":"5247","vim_version":"7.0","1":"7.0","script_version":"2.1.2","2":"2.1.2","version_comment":"    \" 2.1.1 Xaizek: There were also issues with temporary file as $TMP is not always defined and header wasn't updated to mention  and fixed the t mapping.\r\n    \" 2.1.2 Added a mapping to 'o' to open the current buffer under the cursor\r\n\r\n","3":"    \" 2.1.1 Xaizek: There were also issues with temporary file as $TMP is not always defined and header wasn't updated to mention  and fixed the t mapping.\r\n    \" 2.1.2 Added a mapping to 'o' to open the current buffer under the cursor\r\n\r\n","package":"quickBuf.vim","4":"quickBuf.vim","src_id":"23625","5":"23625","creation_date":"1443528600","6":"1443528600"},{"0":"5247","vim_version":"7.0","1":"7.0","script_version":"2.1","2":"2.1","version_comment":"    \" 2.0 Many changes from Xaizek (thanks!). He remove the usage of the paste register, added unix line endings and changed the commands so the buffers are managed by their numbers, which is better than name, so now it works with buffers like [Scratch]\r\n    \" 2.1 I added commands to delete the empty lines and the current buffer and remove some commands from being registered to the jump list (thanks to Xaizek for this tip). I replaced also 0w by 0^ in the commands to get the numbers if they start at the beginning of the line.\r\n ","3":"    \" 2.0 Many changes from Xaizek (thanks!). He remove the usage of the paste register, added unix line endings and changed the commands so the buffers are managed by their numbers, which is better than name, so now it works with buffers like [Scratch]\r\n    \" 2.1 I added commands to delete the empty lines and the current buffer and remove some commands from being registered to the jump list (thanks to Xaizek for this tip). I replaced also 0w by 0^ in the commands to get the numbers if they start at the beginning of the line.\r\n ","package":"quickBuf.vim","4":"quickBuf.vim","src_id":"23624","5":"23624","creation_date":"1443462820","6":"1443462820"},{"0":"5247","vim_version":"7.0","1":"7.0","script_version":"1.2.3","2":"1.2.3","version_comment":"I changed the mappings b to open the buffer list in the current buffer, B to open the buffer list in a new tab\r\n","3":"I changed the mappings b to open the buffer list in the current buffer, B to open the buffer list in a new tab\r\n","package":"quickBuf.vim","4":"quickBuf.vim","src_id":"23618","5":"23618","creation_date":"1443348241","6":"1443348241"},{"0":"5247","vim_version":"7.0","1":"7.0","script_version":"1.2.2","2":"1.2.2","version_comment":"I added 'dd' to delete the buffer under the current line","3":"I added 'dd' to delete the buffer under the current line","package":"quickBuf.vim","4":"quickBuf.vim","src_id":"23617","5":"23617","creation_date":"1443311971","6":"1443311971"},{"0":"5247","vim_version":"7.0","1":"7.0","script_version":"1.2.1","2":"1.2.1","version_comment":"\" Documentation\r\n    \" Name: quickBuf.vim\r\n    \" Version: 1.2.1\r\n    \" Description: Simple and quick buffer explorer\r\n    \" Author: Alexandre Viau (alexandreviau@gmail.com)\r\n    \" Installation: Copy the plugin to the vim plugin directory.\r\n    \r\n\" Usage:\r\n    \" Press b to show the buffer list in a new tab\r\n    \" Press B to show the buffer list in a split window\r\n    \" Press  once on the buffer list to open a buffer\r\n    \" Press  once on the buffer list to delete a buffer\r\n    \" Press ctrl-o after selecting a buffer to return to the buffer list\r\n\" Todo:\r\n\"   s0 When they are more than 1 match for a buffer, delete all\r\n\r\n\" History:\r\n    \" 1.0 Initial release\r\n    \" 1.1 Switched b for B\r\n    \" 1.2 I changed the fixed path c:\/temp\/buffers.txt to $tmp\/buffers.txt\r\n    \" 1.2.1 I put the buffers.txt path to a variable","3":"\" Documentation\r\n    \" Name: quickBuf.vim\r\n    \" Version: 1.2.1\r\n    \" Description: Simple and quick buffer explorer\r\n    \" Author: Alexandre Viau (alexandreviau@gmail.com)\r\n    \" Installation: Copy the plugin to the vim plugin directory.\r\n    \r\n\" Usage:\r\n    \" Press b to show the buffer list in a new tab\r\n    \" Press B to show the buffer list in a split window\r\n    \" Press  once on the buffer list to open a buffer\r\n    \" Press  once on the buffer list to delete a buffer\r\n    \" Press ctrl-o after selecting a buffer to return to the buffer list\r\n\" Todo:\r\n\"   s0 When they are more than 1 match for a buffer, delete all\r\n\r\n\" History:\r\n    \" 1.0 Initial release\r\n    \" 1.1 Switched b for B\r\n    \" 1.2 I changed the fixed path c:\/temp\/buffers.txt to $tmp\/buffers.txt\r\n    \" 1.2.1 I put the buffers.txt path to a variable","package":"quickBuf.vim","4":"quickBuf.vim","src_id":"23600","5":"23600","creation_date":"1442416314","6":"1442416314"},{"0":"5247","vim_version":"7.0","1":"7.0","script_version":"1.2","2":"1.2","version_comment":"\" Documentation\r\n    \" Name: quickBuf.vim\r\n    \" Version: 1.2\r\n    \" Description: Simple and quick buffer explorer\r\n    \" Author: Alexandre Viau (alexandreviau@gmail.com)\r\n    \" Installation: Copy the plugin to the vim plugin directory.\r\n    \r\n\" Usage:\r\n    \" Press b to show the buffer list in a new tab\r\n    \" Press B to show the buffer list in a split window\r\n    \" Press  once on the buffer list to open a buffer\r\n    \" Press  once on the buffer list to delete a buffer\r\n    \" Press ctrl-o after selecting a buffer to return to the buffer list\r\n\" Todo:\r\n\"   s0 When they are more than 1 match for a buffer, delete all\r\n\r\n\" History:\r\n    \" 1.0 Initial release\r\n    \" 1.1 Switched b for B\r\n    \" 1.2 I changed the fixed path c:\/temp\/buffers.txt to $tmp\/buffers.txt","3":"\" Documentation\r\n    \" Name: quickBuf.vim\r\n    \" Version: 1.2\r\n    \" Description: Simple and quick buffer explorer\r\n    \" Author: Alexandre Viau (alexandreviau@gmail.com)\r\n    \" Installation: Copy the plugin to the vim plugin directory.\r\n    \r\n\" Usage:\r\n    \" Press b to show the buffer list in a new tab\r\n    \" Press B to show the buffer list in a split window\r\n    \" Press  once on the buffer list to open a buffer\r\n    \" Press  once on the buffer list to delete a buffer\r\n    \" Press ctrl-o after selecting a buffer to return to the buffer list\r\n\" Todo:\r\n\"   s0 When they are more than 1 match for a buffer, delete all\r\n\r\n\" History:\r\n    \" 1.0 Initial release\r\n    \" 1.1 Switched b for B\r\n    \" 1.2 I changed the fixed path c:\/temp\/buffers.txt to $tmp\/buffers.txt","package":"quickBuf.vim","4":"quickBuf.vim","src_id":"23599","5":"23599","creation_date":"1442416173","6":"1442416173"},{"0":"5247","vim_version":"7.0","1":"7.0","script_version":"1.1","2":"1.1","version_comment":"\" Documentation\r\n    \" Name: quickBuf.vim\r\n    \" Version: 1.1\r\n    \" Description: Simple and quick buffer explorer\r\n    \" Author: Alexandre Viau (alexandreviau@gmail.com)\r\n    \" Installation: Copy the plugin to the vim plugin directory.\r\n    \r\n\" Usage:\r\n    \" Press b to show the buffer list in a new tab\r\n    \" Press B to show the buffer list in a split window\r\n    \" Press  once on the buffer list to open a buffer\r\n    \" Press  once on the buffer list to delete a buffer\r\n    \" Press ctrl-o after selecting a buffer to return to the buffer list\r\n\r\n\" History:\r\n    \" 1.0 Initial release\r\n    \" 1.1 Switched b for B\r\n","3":"\" Documentation\r\n    \" Name: quickBuf.vim\r\n    \" Version: 1.1\r\n    \" Description: Simple and quick buffer explorer\r\n    \" Author: Alexandre Viau (alexandreviau@gmail.com)\r\n    \" Installation: Copy the plugin to the vim plugin directory.\r\n    \r\n\" Usage:\r\n    \" Press b to show the buffer list in a new tab\r\n    \" Press B to show the buffer list in a split window\r\n    \" Press  once on the buffer list to open a buffer\r\n    \" Press  once on the buffer list to delete a buffer\r\n    \" Press ctrl-o after selecting a buffer to return to the buffer list\r\n\r\n\" History:\r\n    \" 1.0 Initial release\r\n    \" 1.1 Switched b for B\r\n","package":"quickBuf.vim","4":"quickBuf.vim","src_id":"23594","5":"23594","creation_date":"1442241510","6":"1442241510"},{"0":"5247","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"quickBuf.vim","4":"quickBuf.vim","src_id":"23593","5":"23593","creation_date":"1442179062","6":"1442179062"}]},"5246":{"script_id":"5246","0":"5246","script_name":"ansible-vim","1":"ansible-vim","script_type":"syntax","2":"syntax","summary":"Syntax highlighting Ansible's common filetypes","3":"Syntax highlighting Ansible's common filetypes","description":"Official repo here: https:\/\/github.com\/pearofducks\/ansible-vim\r\n\r\nThis is a vim syntax plugin for Ansible 2.0, it supports YAML playbooks, Jinja2 templates, and dotini-based 'hosts' files.\r\n\r\nYAML playbooks are detected if:\r\n- they are in the group_vars or host_vars folder\r\n- they are in the tasks or roles folder and have either a .yml or .yaml suffix\r\n- they are named playbook.y(a)ml or site.y(a)ml\r\nJinja2 templates are detected if they have a .j2 suffix\r\nFiles named hosts will be treated as Ansible hosts files\r\n\r\nThis plugin should be quite reliable, as it sources the original formats and simply modifies the highlights as appropriate. This also enables a focus on simplicity and configurability instead of patching bad syntax detection.","4":"Official repo here: https:\/\/github.com\/pearofducks\/ansible-vim\r\n\r\nThis is a vim syntax plugin for Ansible 2.0, it supports YAML playbooks, Jinja2 templates, and dotini-based 'hosts' files.\r\n\r\nYAML playbooks are detected if:\r\n- they are in the group_vars or host_vars folder\r\n- they are in the tasks or roles folder and have either a .yml or .yaml suffix\r\n- they are named playbook.y(a)ml or site.y(a)ml\r\nJinja2 templates are detected if they have a .j2 suffix\r\nFiles named hosts will be treated as Ansible hosts files\r\n\r\nThis plugin should be quite reliable, as it sources the original formats and simply modifies the highlights as appropriate. This also enables a focus on simplicity and configurability instead of patching bad syntax detection.","install_details":"Expand the archive then:\r\n\r\ncp -r ftdetect ftplugin syntax  ~\/.vim\/","5":"Expand the archive then:\r\n\r\ncp -r ftdetect ftplugin syntax  ~\/.vim\/","first_name":"Dave","6":"Dave","last_name":"Honneffer","7":"Honneffer","releases":[{"0":"5246","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"- \"hosts\" files are now highlighted with our own rules, rather than use dosini rules. This allows for much better treatment of variables and Ansible's special categories (e.g. [foo:vars])","3":"- \"hosts\" files are now highlighted with our own rules, rather than use dosini rules. This allows for much better treatment of variables and Ansible's special categories (e.g. [foo:vars])","package":"ansible-vim-1.0.zip","4":"ansible-vim-1.0.zip","src_id":"23720","5":"23720","creation_date":"1446974090","6":"1446974090"},{"0":"5246","vim_version":"7.0","1":"7.0","script_version":"0.9","2":"0.9","version_comment":"Significantly improved indentation from 0.8","3":"Significantly improved indentation from 0.8","package":"ansible-vim-0.9.zip","4":"ansible-vim-0.9.zip","src_id":"23604","5":"23604","creation_date":"1442609211","6":"1442609211"},{"0":"5246","vim_version":"7.0","1":"7.0","script_version":"0.8","2":"0.8","version_comment":"Initial upload","3":"Initial upload","package":"ansible-vim-0.8.zip","4":"ansible-vim-0.8.zip","src_id":"23592","5":"23592","creation_date":"1442170799","6":"1442170799"}]},"5245":{"script_id":"5245","0":"5245","script_name":"8ch.vim","1":"8ch.vim","script_type":"syntax","2":"syntax","summary":"8chan markdown formatting","3":"8chan markdown formatting","description":"infinity Chan http:\/\/www.8ch.net\/ formatting syntax.\r\n\r\nTODO:\r\n- strikethrough and underline does not work (create stack or something)\r\n\r\nGithub: https:\/\/github.com\/kompowiec2\/8ch.vim","4":"infinity Chan http:\/\/www.8ch.net\/ formatting syntax.\r\n\r\nTODO:\r\n- strikethrough and underline does not work (create stack or something)\r\n\r\nGithub: https:\/\/github.com\/kompowiec2\/8ch.vim","install_details":"Paste file \"8chan.vim\" from \/vim74\/syntax\r\n\r\nrun:\r\n\r\nset syntax=8chan.vim","5":"Paste file \"8chan.vim\" from \/vim74\/syntax\r\n\r\nrun:\r\n\r\nset syntax=8chan.vim","first_name":"xxx","6":"xxx","last_name":"xxx","7":"xxx","releases":[{"0":"5245","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"8chan.vim","4":"8chan.vim","src_id":"23591","5":"23591","creation_date":"1442135698","6":"1442135698"}]},"5244":{"script_id":"5244","0":"5244","script_name":"vim-follow-my-lead","1":"vim-follow-my-lead","script_type":"utility","2":"utility","summary":"Shows all your  mappings in a readable table including the descriptions","3":"Shows all your  mappings in a readable table including the descriptions","description":"For details visit:\r\n\r\nhttps:\/\/github.com\/ktonga\/vim-follow-my-lead\r\n\r\nFeatures:\r\n\r\n* List  mappings defined by the user and the plugins\r\n* By default only mappings defined in .vimrc are listed. It honours $MYVIMRC variable\r\n* Mappings from all scripts sourced by Vim can be listed if specified by configuration (see Options)\r\n* If the line previous to the mapping is a comment it will be used as the description\r\n* If no comment is available the rhs of the mapping is used as description\r\n* Mappings are shown in a table, grouped by source, with the following columns\r\n    * Mode: which mode the mapping applies to\r\n    * LHS: left hand side of the mapping (without )\r\n    * Description: The mapping comment if present. The rhs otherwise","4":"For details visit:\r\n\r\nhttps:\/\/github.com\/ktonga\/vim-follow-my-lead\r\n\r\nFeatures:\r\n\r\n* List  mappings defined by the user and the plugins\r\n* By default only mappings defined in .vimrc are listed. It honours $MYVIMRC variable\r\n* Mappings from all scripts sourced by Vim can be listed if specified by configuration (see Options)\r\n* If the line previous to the mapping is a comment it will be used as the description\r\n* If no comment is available the rhs of the mapping is used as description\r\n* Mappings are shown in a table, grouped by source, with the following columns\r\n    * Mode: which mode the mapping applies to\r\n    * LHS: left hand side of the mapping (without )\r\n    * Description: The mapping comment if present. The rhs otherwise","install_details":"Copy plugin\/follow-my-lead.vim to ~\/.vim\/plugin\r\n\r\nOr add a GitHub repository entry if you are using a Plugin Manager such as Vundle:\r\n\r\n    Plugin 'ktonga\/vim-follow-my-lead'\r\n\r\n","5":"Copy plugin\/follow-my-lead.vim to ~\/.vim\/plugin\r\n\r\nOr add a GitHub repository entry if you are using a Plugin Manager such as Vundle:\r\n\r\n    Plugin 'ktonga\/vim-follow-my-lead'\r\n\r\n","first_name":"Gaston","6":"Gaston","last_name":"Tonietti","7":"Tonietti","releases":[{"0":"5244","vim_version":"7.0","1":"7.0","script_version":"0.3","2":"0.3","version_comment":"Community Contributions\r\n----------------------------------\r\n\r\n- Support for no mappings defined in vimrc\r\n- Support for non-English locales\r\n- Create a plug mapping for FML\r\n- Format longer mappings correctly\r\n- Fix for descriptions before noremap mappings\r\n- Better buffer reuse\/management","3":"Community Contributions\r\n----------------------------------\r\n\r\n- Support for no mappings defined in vimrc\r\n- Support for non-English locales\r\n- Create a plug mapping for FML\r\n- Format longer mappings correctly\r\n- Fix for descriptions before noremap mappings\r\n- Better buffer reuse\/management","package":"vim-follow-my-lead-v0.3.tar.gz","4":"vim-follow-my-lead-v0.3.tar.gz","src_id":"23786","5":"23786","creation_date":"1450048928","6":"1450048928"},{"0":"5244","vim_version":"7.0","1":"7.0","script_version":"0.2","2":"0.2","version_comment":"Improvements and bug fixing: \r\n\r\n- Support different descriptions for same mapping on different modes \r\n- Fix FML loading mappings in active buffer instead of in split window \r\n- Reuse window\/buffer to show FML output","3":"Improvements and bug fixing: \r\n\r\n- Support different descriptions for same mapping on different modes \r\n- Fix FML loading mappings in active buffer instead of in split window \r\n- Reuse window\/buffer to show FML output","package":"vim-follow-my-lead-v0.2.tar.gz","4":"vim-follow-my-lead-v0.2.tar.gz","src_id":"23734","5":"23734","creation_date":"1447510710","6":"1447510710"},{"0":"5244","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"vim-follow-my-lead.tar.gz","4":"vim-follow-my-lead.tar.gz","src_id":"23582","5":"23582","creation_date":"1441844597","6":"1441844597"}]},"5243":{"script_id":"5243","0":"5243","script_name":"vim-sipindex","1":"vim-sipindex","script_type":"ftplugin","2":"ftplugin","summary":"shows index of a sipp xml file","3":"shows index of a sipp xml file","description":"this is a mirror of https:\/\/github.com\/esoytekin\/vim-sipindex\r\n\r\nshows index of a sipp file.\r\nKeyboard shortcuts\r\n\r\n    Enter -- goto sip message\r\n    R -- manuanlly refresh sip_index\r\n    D -- delete sip message\r\n    C -- comment sip message\r\n    U -- undo changes\r\n","4":"this is a mirror of https:\/\/github.com\/esoytekin\/vim-sipindex\r\n\r\nshows index of a sipp file.\r\nKeyboard shortcuts\r\n\r\n    Enter -- goto sip message\r\n    R -- manuanlly refresh sip_index\r\n    D -- delete sip message\r\n    C -- comment sip message\r\n    U -- undo changes\r\n","install_details":"if you are using pathongen just put all files under the ~\/home\/.vim\/bundle folder.","5":"if you are using pathongen just put all files under the ~\/home\/.vim\/bundle folder.","first_name":"emrah","6":"emrah","last_name":"soytekin","7":"soytekin","releases":[{"0":"5243","vim_version":"7.0","1":"7.0","script_version":"1.1","2":"1.1","version_comment":"several bugfixes, now doesnt require python, autoload function is added. opens automaticaly whenever a sipp file is opened.","3":"several bugfixes, now doesnt require python, autoload function is added. opens automaticaly whenever a sipp file is opened.","package":"vim-sipindex.zip","4":"vim-sipindex.zip","src_id":"23623","5":"23623","creation_date":"1443429299","6":"1443429299"},{"0":"5243","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"vim-sipindex.zip","4":"vim-sipindex.zip","src_id":"23577","5":"23577","creation_date":"1441561302","6":"1441561302"}]},"5242":{"script_id":"5242","0":"5242","script_name":"easy-navigate.vim","1":"easy-navigate.vim","script_type":"utility","2":"utility","summary":"Commonly used navigation keymaps for Vim","3":"Commonly used navigation keymaps for Vim","description":"Commonly used (and community widely accepted) navigation keymaps for Vim\r\n\r\nStoring them in a separate plugin like this to keep .vimrc clean\r\n\r\nSee https:\/\/github.com\/NLKNguyen\/easy-navigate.vim for keymaps\r\n","4":"Commonly used (and community widely accepted) navigation keymaps for Vim\r\n\r\nStoring them in a separate plugin like this to keep .vimrc clean\r\n\r\nSee https:\/\/github.com\/NLKNguyen\/easy-navigate.vim for keymaps\r\n","install_details":"Using Vundle plugin manager\r\n      Plugin 'NLKNguyen\/easy-navigate.vim'\r\n\r\nOr manually copy easy-navigate.vim to ~\/.vim\/plugin\/","5":"Using Vundle plugin manager\r\n      Plugin 'NLKNguyen\/easy-navigate.vim'\r\n\r\nOr manually copy easy-navigate.vim to ~\/.vim\/plugin\/","first_name":"Nikyle","6":"Nikyle","last_name":"Nguyen","7":"Nguyen","releases":[{"0":"5242","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"easy-navigate.vim.tar.gz","4":"easy-navigate.vim.tar.gz","src_id":"23575","5":"23575","creation_date":"1441481174","6":"1441481174"}]},"5241":{"script_id":"5241","0":"5241","script_name":"log4j highlighter","1":"log4j highlighter","script_type":"syntax","2":"syntax","summary":"Syntax highlighter for log4j log files","3":"Syntax highlighter for log4j log files","description":"    1. Create ~\/.vim\/syntax folder if not already present\r\n    2. Create ~\/.vim\/ftdetect folder if not already present\r\n    3. Copy log4j_syntax_highlighter.vim to ~\/.vim\/syntax\r\n    4. Copy log4j_syntax_detect.vim to ~\/.vim\/ftdetect\r\n    5. Rename any log file to filename.mylogs\r\n    6. Open the log file in vim, it should automatically open with log4jhighlighter as syntax.","4":"    1. Create ~\/.vim\/syntax folder if not already present\r\n    2. Create ~\/.vim\/ftdetect folder if not already present\r\n    3. Copy log4j_syntax_highlighter.vim to ~\/.vim\/syntax\r\n    4. Copy log4j_syntax_detect.vim to ~\/.vim\/ftdetect\r\n    5. Rename any log file to filename.mylogs\r\n    6. Open the log file in vim, it should automatically open with log4jhighlighter as syntax.","install_details":"https:\/\/github.com\/codelibra\/log4jhighlighter\/tree\/master","5":"https:\/\/github.com\/codelibra\/log4jhighlighter\/tree\/master","first_name":"shivendra","6":"shivendra","last_name":"panicker","7":"panicker","releases":[{"0":"5241","vim_version":"7.0","1":"7.0","script_version":"1","2":"1","version_comment":"Initial upload","3":"Initial upload","package":"log4j_syntax_highlighter.vim","4":"log4j_syntax_highlighter.vim","src_id":"23574","5":"23574","creation_date":"1441437989","6":"1441437989"}]},"5240":{"script_id":"5240","0":"5240","script_name":"true-monochrome","1":"true-monochrome","script_type":"color scheme","2":"color scheme","summary":"This is a true black\/grey\/white theme for vim.","3":"This is a true black\/grey\/white theme for vim.","description":"This is a true black\/grey\/white theme for vim. I would say it is as close as I have seen to what the original vi editors looked like (think elvis).","4":"This is a true black\/grey\/white theme for vim. I would say it is as close as I have seen to what the original vi editors looked like (think elvis).","install_details":"Run:\r\n  mkdir -p ~\/.vim\/colors\/\r\n  wget -N https:\/\/raw.githubusercontent.com\/ryanpcmcquen\/true-monochrome_vim\/master\/colors\/true-monochrome.vim -P ~\/.vim\/colors\/\r\n\r\nAdd to .vimrc:\r\n  colorscheme true-monochrome","5":"Run:\r\n  mkdir -p ~\/.vim\/colors\/\r\n  wget -N https:\/\/raw.githubusercontent.com\/ryanpcmcquen\/true-monochrome_vim\/master\/colors\/true-monochrome.vim -P ~\/.vim\/colors\/\r\n\r\nAdd to .vimrc:\r\n  colorscheme true-monochrome","first_name":"Ryan","6":"Ryan","last_name":"McQuen","7":"McQuen","releases":[{"0":"5240","vim_version":"6.0","1":"6.0","script_version":"0.1.5","2":"0.1.5","version_comment":"GUI and CLI colors are now the same.","3":"GUI and CLI colors are now the same.","package":"true-monochrome.vim","4":"true-monochrome.vim","src_id":"23568","5":"23568","creation_date":"1441078513","6":"1441078513"}]},"5239":{"script_id":"5239","0":"5239","script_name":"Replace operator","1":"Replace operator","script_type":"utility","2":"utility","summary":"R (replace) operator","3":"R (replace) operator","description":"Github: https:\/\/github.com\/romgrk\/replace.vim\r\n\r\nReplace operator is an additionnal operator, like 'c', 'd' or 'p'. \r\nIt operates on a range of text, and accepts a register as input. \r\nBasically, it replaces the text in {motion} or {Visual} with the content of register [x], or 'clipboard' if none provided.\r\n\r\nThe deleted text is sent to black hole register by default. \r\nYou can set the default register by setting:\r\n\r\n    let g:replace_register = '_'\r\n\r\nWhen g:replace_register is set to '|', the text is exchanged between \r\nthe two register. \r\n","4":"Github: https:\/\/github.com\/romgrk\/replace.vim\r\n\r\nReplace operator is an additionnal operator, like 'c', 'd' or 'p'. \r\nIt operates on a range of text, and accepts a register as input. \r\nBasically, it replaces the text in {motion} or {Visual} with the content of register [x], or 'clipboard' if none provided.\r\n\r\nThe deleted text is sent to black hole register by default. \r\nYou can set the default register by setting:\r\n\r\n    let g:replace_register = '_'\r\n\r\nWhen g:replace_register is set to '|', the text is exchanged between \r\nthe two register. \r\n","install_details":"cd ~\/.vim\/bundle  && git clone https:\/\/github.com\/romgrk\/replace.vim\r\n\r\nBundle 'romgrk\/replace.vim'\r\n\r\nNeoBundle 'romgrk\/replace.vim'\r\n","5":"cd ~\/.vim\/bundle  && git clone https:\/\/github.com\/romgrk\/replace.vim\r\n\r\nBundle 'romgrk\/replace.vim'\r\n\r\nNeoBundle 'romgrk\/replace.vim'\r\n","first_name":"Rom","6":"Rom","last_name":"Grk","7":"Grk","releases":[{"0":"5239","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"replace.vim.zip","4":"replace.vim.zip","src_id":"23559","5":"23559","creation_date":"1440796113","6":"1440796113"}]},"5238":{"script_id":"5238","0":"5238","script_name":"CBOT.vim","1":"CBOT.vim","script_type":"syntax","2":"syntax","summary":"CBOT fictional programming language from Vim","3":"CBOT fictional programming language from Vim","description":"Syntax highlighting fictional programming language CBOT for vim\r\n\r\nColobot: http:\/\/colobot.info\/","4":"Syntax highlighting fictional programming language CBOT for vim\r\n\r\nColobot: http:\/\/colobot.info\/","install_details":"copying \"CBOT.vim\" file form root directory vim SYNTAX\r\n\r\nAfther run some CBOT script active syntax from:\r\n\r\n:set syntax=cbot.vim\r\n\r\nif you want auto detect syntax, run filetype.vim and add line:\r\n\r\nau BufNewFile,BufRead *.cbot setf cbot\r\n\r\nGithub: https:\/\/github.com\/kompowiec2\/CBOT.vim","5":"copying \"CBOT.vim\" file form root directory vim SYNTAX\r\n\r\nAfther run some CBOT script active syntax from:\r\n\r\n:set syntax=cbot.vim\r\n\r\nif you want auto detect syntax, run filetype.vim and add line:\r\n\r\nau BufNewFile,BufRead *.cbot setf cbot\r\n\r\nGithub: https:\/\/github.com\/kompowiec2\/CBOT.vim","first_name":"","6":"","last_name":"","7":"","releases":[{"0":"5238","vim_version":"7.0","1":"7.0","script_version":"1.0a","2":"1.0a","version_comment":"typo","3":"typo","package":"cbot.vim","4":"cbot.vim","src_id":"23563","5":"23563","creation_date":"1440861689","6":"1440861689"},{"0":"5238","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"cbot.vim","4":"cbot.vim","src_id":"23558","5":"23558","creation_date":"1440763960","6":"1440763960"}]},"5237":{"script_id":"5237","0":"5237","script_name":"coco","1":"coco","script_type":"utility","2":"utility","summary":"vim code commentator","3":"vim code commentator","description":"vim-coco\r\nvim code commentator;\r\n\r\nusage\r\nsee doc\/coco.txt;","4":"vim-coco\r\nvim code commentator;\r\n\r\nusage\r\nsee doc\/coco.txt;","install_details":"https:\/\/github.com\/cykerway\/vim-coco\r\n\r\ninstall\r\ninstall assumes vim 8.0 or later;\r\n\r\nwith git\r\nmkdir -p ~\/.vim\/pack\/foo\/start\r\ncd ~\/.vim\/pack\/foo\/start\r\ngit clone https:\/\/github.com\/cykerway\/vim-coco.git\r\nwithout git\r\nmkdir -p ~\/.vim\/pack\/foo\/start\/vim-coco\r\ncp doc plugin ~\/.vim\/pack\/foo\/start\/vim-coco\/","5":"https:\/\/github.com\/cykerway\/vim-coco\r\n\r\ninstall\r\ninstall assumes vim 8.0 or later;\r\n\r\nwith git\r\nmkdir -p ~\/.vim\/pack\/foo\/start\r\ncd ~\/.vim\/pack\/foo\/start\r\ngit clone https:\/\/github.com\/cykerway\/vim-coco.git\r\nwithout git\r\nmkdir -p ~\/.vim\/pack\/foo\/start\/vim-coco\r\ncp doc plugin ~\/.vim\/pack\/foo\/start\/vim-coco\/","first_name":"Cyker","6":"Cyker","last_name":"Way","7":"Way","releases":[{"0":"5237","vim_version":"8.0","1":"8.0","script_version":"1.2.0","2":"1.2.0","version_comment":".","3":".","package":"vim-coco.tar.gz","4":"vim-coco.tar.gz","src_id":"28133","5":"28133","creation_date":"1661133693","6":"1661133693"},{"0":"5237","vim_version":"8.0","1":"8.0","script_version":"1.1.1","2":"1.1.1","version_comment":".","3":".","package":"vim-coco.tar.gz","4":"vim-coco.tar.gz","src_id":"28130","5":"28130","creation_date":"1660983650","6":"1660983650"},{"0":"5237","vim_version":"8.0","1":"8.0","script_version":"1.0.0","2":"1.0.0","version_comment":".","3":".","package":"coco.tar.gz","4":"coco.tar.gz","src_id":"26350","5":"26350","creation_date":"1547603666","6":"1547603666"}]},"5236":{"script_id":"5236","0":"5236","script_name":"proteinFasta.vim","1":"proteinFasta.vim","script_type":"syntax","2":"syntax","summary":"Syntax file for protein-based FASTA files","3":"Syntax file for protein-based FASTA files","description":"This is a syntax coloring file for FASTA files of protein sequences, as are commonly used in proteomics.  It highlights the protein name, description, and residues in separate colors.  Invalid characters are flagged as errors.","4":"This is a syntax coloring file for FASTA files of protein sequences, as are commonly used in proteomics.  It highlights the protein name, description, and residues in separate colors.  Invalid characters are flagged as errors.","install_details":"Store in your ~\/.vim\/syntax folder (on Windows: vimfiles\\syntax)\r\nUpdate .vimrc (or _vimrc on Windows) to have\r\n:autocmd BufNewFile,BufRead *.fasta set filetype=proteinFasta","5":"Store in your ~\/.vim\/syntax folder (on Windows: vimfiles\\syntax)\r\nUpdate .vimrc (or _vimrc on Windows) to have\r\n:autocmd BufNewFile,BufRead *.fasta set filetype=proteinFasta","first_name":"Matthew","6":"Matthew","last_name":"Monroe","7":"Monroe","releases":[{"0":"5236","vim_version":"5.7","1":"5.7","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"proteinFasta.vim","4":"proteinFasta.vim","src_id":"23537","5":"23537","creation_date":"1440176982","6":"1440176982"}]},"5235":{"script_id":"5235","0":"5235","script_name":"Vizardry","1":"Vizardry","script_type":"utility","2":"utility","summary":"A vim plugin manager for lazy people","3":"A vim plugin manager for lazy people","description":"# Vizardry\r\n\r\n                ________________ _______ _______ ______  _______\r\n        |\\     \/\\__   __\/ ___   (  ___  (  ____ (  __  \\(  ____ |\\     \/|\r\n        | )   ( |  ) (  \\\/   )  | (   ) | (    )| (  \\  | (    )( \\   \/ )\r\n        | |   | |  | |      \/   | (___) | (____)| |   ) | (____)|\\ (_) \/\r\n        ( (   ) )  | |     \/   \/|  ___  |     __| |   | |     __) \\   \/\r\n         \\ \\_\/ \/   | |    \/   \/ | (   ) | (\\ (  | |   ) | (\\ (     ) (\r\n          \\   \/ ___) (___\/   (_\/| )   ( | ) \\ \\_| (__\/  | ) \\ \\__  | |\r\n           \\_\/  \\_______(_______|\/     \\|\/   \\__(______\/|\/   \\__\/  \\_\/\r\n\r\n                    A vim plugin manager for lazy people\r\n\r\n## Table of contents\r\n\r\n1. [Release notes](#release-notes)\r\n2. [Introduction](#introduction)\r\n    1. [Why This Fork ?](#why-this-fork)\r\n    2. [Requirements](#requirements)\r\n    3. [Installation](#installation)\r\n    4. [License](#license)\r\n3. [Submodules](#how-to-use-vizardry-with-submodules)\r\n4. [Commands](#commands)\r\n    1. [Scry](#scry)\r\n        1. [Number of results](#number-of-results)\r\n        2. [Queries](#queries)\r\n        3. [Search Options](#search-options)\r\n    2. [Invoke](#invoke)\r\n        1. [Display readme on Invoke](#display-readme-on-invoke)\r\n    3. [Banish](#banish)\r\n    4. [Unbanish](#unbanish)\r\n    5. [Vanish](#vanish)\r\n    6. [Evolve](#evolve)\r\n        1. [Display readme on evolve](#display-readme-on-evolve)\r\n        2. [Evolve from vim.org](#evolve-from-vim.org)\r\n    7. [Vizardry](#vizardry-cmd)\r\n    8. [Grimoire](#grimoire)\r\n5. [Magic](#magic)\r\n    1. [Configuration](#magic-configuration)\r\n    2. [Commands](#magic-commands)\r\n        1. [:Magic](#magic-cmd)\r\n        2. [:Magicedit](#magicedit)\r\n        3. [:Magicsplit](#magicsplit)\r\n        4. [:Magicvsplit](#magicvsplit)\r\n        5. [:MagicCommit](#magiccommit)\r\n6. [Get involved](#get-involved)\r\n\r\n## Release notes\r\n\r\nCurrent Version: 2.0\r\n\r\n*   v2.0 comes with several improvements:\r\n    * Grimoires abstraction to install bundles from any provider (Grimoires\r\n    currently available: github, bitbuckets, gitlab), see [Grimoire](#grimoire).\r\n    * Re enabling of `:Magic` family commands with support for submodule\r\n    mode, see [Magic](#magic)).\r\n    * A major refactor including, several minor bug fix, and removing\r\n    dependencies to external commands (`sed`, `grep` etc.).\r\n    * A new documentation for developers to help Vizardry enthusiasts improve\r\n    it.\r\n\r\n    **Important informations**: Helps and Readme are not read from stdin anymore\r\n    but from temporary file thus the Reader syntax have changed see:\r\n    [here](#display-readme-on-invoke).\r\n*   v1.4 provides several bug fix and the capability of seeing help files from\r\n Invoke and Evolve prompt.\r\n*   v1.3 allow to Invoke directly from Scry, to do so, I had to modify the input\r\n  method (using `:input()`, instead of `:getchar()`), for the user the result\r\n  is that it is now necessary to hit 'enter' after answering a prompt from\r\n  Vizardry\r\n* Since v1.1, `VizardrySortScryResults` is replaced by `VizardrySearchOptions`\r\n\r\n## Introduction\r\n\r\nRemember back in the dark ages of 2013? When you had to search for vim plugins like a wild animal, using your browser?\r\n\r\nIn 2014, you can just type \":Invoke <keyword>\" and Vizardry will automatically search github for the plugin you want and install it for you.\r\n\r\nIn 2015 you can even upgrade plugins from any git repo or vim.org using [:Evolve](#evolve).\r\n\r\nAs each year seems to come with a new improvement, in 2016 you are not\r\nlimited to github anymore it is possible to install plugins from bitbucket,\r\ngitlab or virtually any others, see [Grimoire](#grimoire).\r\n\r\n\r\n### Why this fork ?\r\n\r\nThis plugin is a fork from [Ardagnir original Vizardry\r\nplugin](https:\/\/github.com\/ardagnir\/Vizardry) which adds several pretty cool\r\nfeatures including:\r\n\r\n* `Grimoire` abstraction to install bundle from any providers.\r\n+ `Vanish` command to actually remove a plugin.\r\n+ `Evolve` command to upgrade one or every plugins see [Evolve](#evolve).\r\n+ Complete submodule handling for people having their vim config in a git repo\r\n(see [submodules](#how-to-use-vizardry-with-submodules)).\r\n+ Dislay README.md file inside vim while using `:Invoke`.\r\n+ Navigate through search results with `:Invoke`\r\n+ Set the length of `Scry` results list.\r\n+ Go directly from `Scry`  to `Invoke`\r\n+ Search script written by specific user with `:Scry` and `:Invoke`\r\n+ Automatically call `:Helptags` every time a plugin is Invoked.\r\n+ ...\r\n\r\n\r\n### Requirements\r\n\r\n+ Vizardry requires [pathogen](https:\/\/github.com\/tpope\/vim-pathogen). But you\r\n  already have pathogen installed, don't you?\r\n\r\n+ It also needs git, curl, and basic \\*nix commands.\r\n\r\n+ You will probably have issues if you use a Windows OS.\r\n\r\n### Installation\r\n\r\nUse pathogen.\r\n\r\n    cd ~\/.vim\/bundle\r\n    git clone https:\/\/github.com\/dbeniamine\/vizardry\r\n\r\n### License\r\n\r\nVizardry: A vim plugin manager for lazy people\r\nCopyright (C) 2015,2016 David Beniamine. All rights reserved.\r\nCopyright (C) 2013, James Kolb. All rights reserved.\r\n\r\nThis program is free software: you can redistribute it and\/or modify\r\nit under the terms of the GNU Affero General Public License as\r\npublished by the Free Software Foundation, either version 3 of the\r\nLicense, or (at your option) any later version.\r\n\r\nThis program is distributed in the hope that it will be useful,\r\nbut WITHOUT ANY WARRANTY; without even the implied warranty of\r\nMERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the\r\nGNU Affero General Public License for more details.\r\n\r\nYou should have received a copy of the GNU Affero General Public License\r\nalong with this program.  If not, see .\r\n\r\n\r\n## How to use Vizardry with submodules ?\r\n\r\nSet the following variables in your vimrc:\r\n\r\n    let g:VizardryGitMethod=\"submodule add\"\r\n    let g:VizardryGitBaseDir=\"\/path\/to\/your\/git\/repo\"\r\n\r\nThe second variable **must be** the root of the repo containing your vim\r\nfiles.\r\n\r\nOptionally you can set the vim commit messages (the name of the modified\r\nplugin will always be happened in the end of the message, the proposed values\r\nare the defaults):\r\n\r\n    let g:VizardryCommitMsgs={'Invoke': \"[Vizardry] Invoked vim submodule:\",\r\n          \\'Banish': \"[Vizardry] Banished vim submodule:\",\r\n          \\'Vanish': \"[Vizardry] Vanished vim submodule:\",\r\n          \\'Evolve': \"[Vizardry] Evolved vim submodule:\",\r\n          \\}\r\n\r\nEach time you `:Invoke`, `:Bannish` or `:Vanish` a module, the submodule will be correctly\r\nupdated and a minimal commit will be created.\r\n\r\n### Note:\r\n\r\n+ Commits created by Vizardry are not automatically pushed.\r\n+ The `.gitmodule` is included in each commit, do not use `:Invoke`, `:Bannish`\r\nor `:Vanish` if it contains some bad modifications.\r\n\r\n\r\n## Commands\r\n\r\n### Scry\r\n\r\n`:Scry []`\r\n\r\n+ If no  is given, list all invoked and banished plugins.\r\n+ If a  is specified (see below), search for a script matching\r\n in title or readme and list N first results.  After the search, ̀`Scry`\r\nwill prompt you to `Invoke` a script, hit `q` to exit, or a number to `Invoke`\r\nthe corresponding script.\r\n\r\n#### Number of results\r\n\r\nThe number of results displayed can be configured by adding the following to\r\nyour vimrc:\r\n\r\n    let g:VizardryNbScryResults = 25\r\n\r\nDefault is 10.\r\n\r\n#### Queries\r\n\r\nA `` can be:\r\n\r\n+ One or several keywords\r\n+ A query matching the github [search\r\napi](https:\/\/developer.github.com\/v3\/search\/#search-repositories)\r\n+ A mix of keywords and github search fields\r\n\r\nAdditionally, Vizardry adds the following parameters that can be used alone or\r\nin combination with a query\r\n    + `-u ` (search every repositories of  matching 'vim')\r\n    + `-q ` to search on a different grimoire\r\n\r\n#### Search options\r\n\r\nIt is possible to set some github search option in your vimrc, default\r\noptions are show forked repositories and sort by pertinence. These options\r\ncan be overwritten. For instance adding the following to your vimrc will\r\nmake vizardry show results sorted by number of stars hidding forked\r\nrepositries.\r\n\r\n    let g:VizardrySortOptions=\"fork:false+sort:stars\"\r\n\r\nAny combination of github option can be used, a `+` must appear between\r\neach options. For the sort option, available parameters are `stars`,\r\n`forks`, `updated`, by default, it show the best match.\r\n\r\n### Invoke\r\n\r\n`:Invoke [|N]`\r\n\r\n+   If no arguments is specified, reload your plugins.\r\n+   If the argument is a number, ask to install the plugin with that\r\n    number from the last `:Scry` or Invoke.\r\n+   If the argument is a ``, search github for a plugin matching\r\n`` (see above)  and ask for install, the sort criteria for search\r\nresults can be configured (see above).\r\n\r\nSuppose you're in the middle of vimming and you have a sudden need to surround\r\nrandom words in \"scare quotes\". You can't remember who made the surround\r\nplugin, or whether it's called surround.vim, vim-surround or\r\nvim-surround-plugin. Most importantly, you're lazy.\r\n\r\n\r\nJust type:\r\n\r\n    :Invoke surround\r\n\r\nVizardry will pop up a prompt saying:\r\n\r\n    Result 1\/20: tpope\/vim-surround\r\n    (surround.vim: quoting\/parenthesizing made simple)\r\n\r\n    Clone as \"surround\"? (Yes\/Rename\/Displayreadme\/displayHelp\/Next\/Previous\/Abort)\r\n\r\nPress Y and you can immediately start surrounding things.  You can also take a\r\nlook at the README.md directly in vim by hitting `d` or at the help using `h`,\r\nGo to the next or previous script with `n` and `p` or abort `a`. It's that\r\neasy.\r\n\r\nEven plugins with vague or silly names can be found with Vizardry. Imagine\r\nyou're running multiple instances of vim and need a package to sync registers.\r\n\r\nType:\r\n\r\n    :Invoke sync registers\r\n\r\nVizardry will prompt you with:\r\n\r\n    Result 1\/3: ardagnir\/united-front\r\n    (Automatically syncs registers between vim instances)\r\n\r\n    Clone as \"syncregisters\"? (Yes\/Rename\/DisplayMore\/Next\/Previous\/Abort)\r\n\r\nJust as easy.\r\n\r\n#### Display readme on Invoke\r\n\r\nTo view the readme, an other instance of vim is called, the command line can\r\nbe configured:\r\n\r\n    let g:VizardryReadmeReader='view -c \"set ft=markdown\"'\r\n\r\nThe help file reader is also configurable, there is the default:\r\n\r\n    let g:VizardryHelpReader='view -c \"set ft=help\"'\r\n\r\n**Note:** since v2.0, the `-` in the end of the reader line is not required\r\nanymore, please update your configuration accordingly.\r\n\r\nFinally if readme or help is missing, Vizardry will try to search for the\r\nother one, if you dont like this behavior, you can prevent it:\r\n\r\n    let g:VizardryReadmeHelpFallback = 0\r\n\r\n### Banish\r\n\r\n`:Banish `\r\n\r\nBanish a plugin, this only forbid pathogen to load it and does not remove\r\nthe files. You need to restart vim to see the effects.\r\n\r\n### UnBanish\r\n\r\n`:Unbanish `\r\n\r\nReverse a banish.\r\n\r\n### Vanish\r\n\r\n`:Vanish `\r\n\r\nRemove definitively a plugin's files.\r\n\r\n### Evolve\r\n\r\n`:Evolve  [ []]`\r\n\r\nUpgrade the plugin matching <keyword> using remote branche\r\n<branch> if specified. If no <keyword> is given, upgrade\r\nall possible plugins.\r\n\r\nGit plugins are upgraded by doing `git pull origin branch`. Where  `branch` the\r\none specified in argument if any or the current branch of the local repository.\r\nIf `branch` is different from the current branch, Vizardry will first create\r\nor checkout a local branch with the same name as the remote branch requested.\r\n\r\n####\u00c2\u00a0Display Readme On Evolve\r\n\r\nSometimes it can be a good idea to take a quick look at a plugin's README,\r\nhelp or git log when updating, to do so, add the following to your vimrc:\r\n\r\n    let g:VizardryViewReadmeOnEvolve=1\r\n\r\n`:Evolve` will then ask you to display readme help or log each time a plugin is\r\nupgraded.\r\n\r\n#### Evolve from vim.org\r\n\r\n**Evolving directly from vim.org is deprecated.**\r\nTo install plugin found at vim.org from github use:\r\n\r\n    :Invoke -u vim-scripts \r\n\r\nWere <plugin-name> is the actual name of the plugin at vim.org\r\n\r\nYou can also search a plugin by vim.org id:\r\n\r\n    :Invoke -u vim-scripts in:readme script_id=\r\n\r\n### Vizardry<\/a>\r\n\r\n    :Vizardry\r\n\r\nShow a basic usage and Vizardry version.\r\n\r\n### Grimoire\r\n\r\n    :Grimoire [provider]\r\n\r\nList Grimoires or select the `Grimoire` from which you want to `Scry` and\r\n`Invoke` bundles. A grimoire is a website from which you can search for\r\nbundles such as github or bitbucket.\r\n\r\nIt is also possible to set the default grimoire in your vimrc\r\n\r\n    let g:VizardryDefaultGrimoire='github'\r\n\r\nFor Bitbucket and gitlab, an instance url can be supplied, here are the\r\ndefaults:\r\n\r\n    let g:VizardryGitlabInstanceUrl='gitlab.com'\r\n    let g:VizardryBitbucketInstanceUrl='bitbucket.org'\r\n\r\n**Note:**\r\n\r\n*   Bitbucket does not allow to do any filters while searching for public\r\nrepository, thus every github parameters (such as `fork:true`) but `user:name`\r\nand `language:lang` are ignored, when using Bitbucket grimoire. For the same\r\nreason, Bitbuckets queries does not respect `g:VizardryNbScryResults`.\r\n*   Gitlab API is even worse, neither `user` nor ̀`language` or any other github\r\nsearch options works.\r\n\r\n# Magic\r\n\r\nVizardry Magic is a simple way to handle plugin specific configurations files,\r\nthese files will be Banished, Unbanished and Vanished with the bundle they\r\nbelong to.\r\n\r\n## Magic Configuration\r\n\r\nBy default, these files are stored in `bunde\/vizardry\/plugin\/magic`, this path\r\nensure that removing Vizardry will remove the magic files. As it is not always\r\na good idea to keep modified files in a subdirectory of an existing bundle,\r\nthis pas can be modified (and must be modified for submodule mode\r\n[Submodules](#how-to-use-vizardry-with-submodules)). A good idea can be to\r\nkeep them in `~\/.vim\/plugin\/magic`:\r\n\r\n    let g:VizardryMagicDir='~\/.vim\/plugin\/magic'\r\n\r\n\r\n## Magic Commands\r\n\r\n### :Magic<\/a>\r\n\r\n    :Magic  \r\n\r\n\r\nAdds <command> to <bundle> magic file and execute it.\r\n\r\n### :Magicedit\r\n\r\n    :Magicedit \r\n\r\nEdits magic file for <bundle>.\r\n\r\n### :Magicsplit\r\n\r\n    :Magicsplit \r\n\r\nEdits magic file for <bundle>, spliting the current window.\r\n\r\n### :Magicvsplit\r\n\r\n    :Magicvsplit \r\n\r\nEdits magic file for <bundle>, vspliting the current window.\r\n\r\n### :MagicCommit\r\n\r\n    :MagicCommit \r\n\r\nFor submodule (see [Submodules](#how-to-use-vizardry-with-submodules)) mode\r\nonly: Commit the changes to the given magic file.\r\n\r\nDoes nothing in clone mode\r\n\r\n# Get involved\r\n\r\n## Spread the word\r\n\r\nIf you like Vizardry and you are also a vimscript developper, an easy way to\r\nspread the word is to add a Vizardry install section to your plugins README\r\nfor instance:\r\n\r\nIf you have installed [Vizardry](https:\/\/github.com\/dbeniamine\/vizardry) just\r\nrun the following from vim:\r\n\r\n    :Invoke -u  \r\n\r\n## Write Grimoires\r\n\r\nCurrently only github and bitbucket are available, but it is very easy to add a\r\nnew Grimoire, see [issue#3](https:\/\/github.com\/dbeniamine\/vizardry\/issues\/3)\r\nand `:help Vizardry-Dev-grimoires`.\r\n\r\n## Develop inside Vizardry\r\n\r\nIf you like Vizardry and want to help, you can look add `vizardry\/todo.txt`\r\nsee what I improvement I'm planning to add to Vizardry.\r\nIf you are going to modify Vizardry code, please take a look at |Vizardry-Dev|\r\nbefore writing any code.\r\nFeel free to open pull requests when you are done :).\r\n\r\n\r\nMore at https:\/\/github.com\/dbeniamine\/vizardry\r\n","4":"# Vizardry\r\n\r\n                ________________ _______ _______ ______  _______\r\n        |\\     \/\\__   __\/ ___   (  ___  (  ____ (  __  \\(  ____ |\\     \/|\r\n        | )   ( |  ) (  \\\/   )  | (   ) | (    )| (  \\  | (    )( \\   \/ )\r\n        | |   | |  | |      \/   | (___) | (____)| |   ) | (____)|\\ (_) \/\r\n        ( (   ) )  | |     \/   \/|  ___  |     __| |   | |     __) \\   \/\r\n         \\ \\_\/ \/   | |    \/   \/ | (   ) | (\\ (  | |   ) | (\\ (     ) (\r\n          \\   \/ ___) (___\/   (_\/| )   ( | ) \\ \\_| (__\/  | ) \\ \\__  | |\r\n           \\_\/  \\_______(_______|\/     \\|\/   \\__(______\/|\/   \\__\/  \\_\/\r\n\r\n                    A vim plugin manager for lazy people\r\n\r\n## Table of contents\r\n\r\n1. [Release notes](#release-notes)\r\n2. [Introduction](#introduction)\r\n    1. [Why This Fork ?](#why-this-fork)\r\n    2. [Requirements](#requirements)\r\n    3. [Installation](#installation)\r\n    4. [License](#license)\r\n3. [Submodules](#how-to-use-vizardry-with-submodules)\r\n4. [Commands](#commands)\r\n    1. [Scry](#scry)\r\n        1. [Number of results](#number-of-results)\r\n        2. [Queries](#queries)\r\n        3. [Search Options](#search-options)\r\n    2. [Invoke](#invoke)\r\n        1. [Display readme on Invoke](#display-readme-on-invoke)\r\n    3. [Banish](#banish)\r\n    4. [Unbanish](#unbanish)\r\n    5. [Vanish](#vanish)\r\n    6. [Evolve](#evolve)\r\n        1. [Display readme on evolve](#display-readme-on-evolve)\r\n        2. [Evolve from vim.org](#evolve-from-vim.org)\r\n    7. [Vizardry](#vizardry-cmd)\r\n    8. [Grimoire](#grimoire)\r\n5. [Magic](#magic)\r\n    1. [Configuration](#magic-configuration)\r\n    2. [Commands](#magic-commands)\r\n        1. [:Magic](#magic-cmd)\r\n        2. [:Magicedit](#magicedit)\r\n        3. [:Magicsplit](#magicsplit)\r\n        4. [:Magicvsplit](#magicvsplit)\r\n        5. [:MagicCommit](#magiccommit)\r\n6. [Get involved](#get-involved)\r\n\r\n## Release notes\r\n\r\nCurrent Version: 2.0\r\n\r\n*   v2.0 comes with several improvements:\r\n    * Grimoires abstraction to install bundles from any provider (Grimoires\r\n    currently available: github, bitbuckets, gitlab), see [Grimoire](#grimoire).\r\n    * Re enabling of `:Magic` family commands with support for submodule\r\n    mode, see [Magic](#magic)).\r\n    * A major refactor including, several minor bug fix, and removing\r\n    dependencies to external commands (`sed`, `grep` etc.).\r\n    * A new documentation for developers to help Vizardry enthusiasts improve\r\n    it.\r\n\r\n    **Important informations**: Helps and Readme are not read from stdin anymore\r\n    but from temporary file thus the Reader syntax have changed see:\r\n    [here](#display-readme-on-invoke).\r\n*   v1.4 provides several bug fix and the capability of seeing help files from\r\n Invoke and Evolve prompt.\r\n*   v1.3 allow to Invoke directly from Scry, to do so, I had to modify the input\r\n  method (using `:input()`, instead of `:getchar()`), for the user the result\r\n  is that it is now necessary to hit 'enter' after answering a prompt from\r\n  Vizardry\r\n* Since v1.1, `VizardrySortScryResults` is replaced by `VizardrySearchOptions`\r\n\r\n## Introduction\r\n\r\nRemember back in the dark ages of 2013? When you had to search for vim plugins like a wild animal, using your browser?\r\n\r\nIn 2014, you can just type \":Invoke <keyword>\" and Vizardry will automatically search github for the plugin you want and install it for you.\r\n\r\nIn 2015 you can even upgrade plugins from any git repo or vim.org using [:Evolve](#evolve).\r\n\r\nAs each year seems to come with a new improvement, in 2016 you are not\r\nlimited to github anymore it is possible to install plugins from bitbucket,\r\ngitlab or virtually any others, see [Grimoire](#grimoire).\r\n\r\n\r\n### Why this fork ?\r\n\r\nThis plugin is a fork from [Ardagnir original Vizardry\r\nplugin](https:\/\/github.com\/ardagnir\/Vizardry) which adds several pretty cool\r\nfeatures including:\r\n\r\n* `Grimoire` abstraction to install bundle from any providers.\r\n+ `Vanish` command to actually remove a plugin.\r\n+ `Evolve` command to upgrade one or every plugins see [Evolve](#evolve).\r\n+ Complete submodule handling for people having their vim config in a git repo\r\n(see [submodules](#how-to-use-vizardry-with-submodules)).\r\n+ Dislay README.md file inside vim while using `:Invoke`.\r\n+ Navigate through search results with `:Invoke`\r\n+ Set the length of `Scry` results list.\r\n+ Go directly from `Scry`  to `Invoke`\r\n+ Search script written by specific user with `:Scry` and `:Invoke`\r\n+ Automatically call `:Helptags` every time a plugin is Invoked.\r\n+ ...\r\n\r\n\r\n### Requirements\r\n\r\n+ Vizardry requires [pathogen](https:\/\/github.com\/tpope\/vim-pathogen). But you\r\n  already have pathogen installed, don't you?\r\n\r\n+ It also needs git, curl, and basic \\*nix commands.\r\n\r\n+ You will probably have issues if you use a Windows OS.\r\n\r\n### Installation\r\n\r\nUse pathogen.\r\n\r\n    cd ~\/.vim\/bundle\r\n    git clone https:\/\/github.com\/dbeniamine\/vizardry\r\n\r\n### License\r\n\r\nVizardry: A vim plugin manager for lazy people\r\nCopyright (C) 2015,2016 David Beniamine. All rights reserved.\r\nCopyright (C) 2013, James Kolb. All rights reserved.\r\n\r\nThis program is free software: you can redistribute it and\/or modify\r\nit under the terms of the GNU Affero General Public License as\r\npublished by the Free Software Foundation, either version 3 of the\r\nLicense, or (at your option) any later version.\r\n\r\nThis program is distributed in the hope that it will be useful,\r\nbut WITHOUT ANY WARRANTY; without even the implied warranty of\r\nMERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the\r\nGNU Affero General Public License for more details.\r\n\r\nYou should have received a copy of the GNU Affero General Public License\r\nalong with this program.  If not, see .\r\n\r\n\r\n## How to use Vizardry with submodules ?\r\n\r\nSet the following variables in your vimrc:\r\n\r\n    let g:VizardryGitMethod=\"submodule add\"\r\n    let g:VizardryGitBaseDir=\"\/path\/to\/your\/git\/repo\"\r\n\r\nThe second variable **must be** the root of the repo containing your vim\r\nfiles.\r\n\r\nOptionally you can set the vim commit messages (the name of the modified\r\nplugin will always be happened in the end of the message, the proposed values\r\nare the defaults):\r\n\r\n    let g:VizardryCommitMsgs={'Invoke': \"[Vizardry] Invoked vim submodule:\",\r\n          \\'Banish': \"[Vizardry] Banished vim submodule:\",\r\n          \\'Vanish': \"[Vizardry] Vanished vim submodule:\",\r\n          \\'Evolve': \"[Vizardry] Evolved vim submodule:\",\r\n          \\}\r\n\r\nEach time you `:Invoke`, `:Bannish` or `:Vanish` a module, the submodule will be correctly\r\nupdated and a minimal commit will be created.\r\n\r\n### Note:\r\n\r\n+ Commits created by Vizardry are not automatically pushed.\r\n+ The `.gitmodule` is included in each commit, do not use `:Invoke`, `:Bannish`\r\nor `:Vanish` if it contains some bad modifications.\r\n\r\n\r\n## Commands\r\n\r\n### Scry\r\n\r\n`:Scry []`\r\n\r\n+ If no  is given, list all invoked and banished plugins.\r\n+ If a  is specified (see below), search for a script matching\r\n in title or readme and list N first results.  After the search, ̀`Scry`\r\nwill prompt you to `Invoke` a script, hit `q` to exit, or a number to `Invoke`\r\nthe corresponding script.\r\n\r\n#### Number of results\r\n\r\nThe number of results displayed can be configured by adding the following to\r\nyour vimrc:\r\n\r\n    let g:VizardryNbScryResults = 25\r\n\r\nDefault is 10.\r\n\r\n#### Queries\r\n\r\nA `` can be:\r\n\r\n+ One or several keywords\r\n+ A query matching the github [search\r\napi](https:\/\/developer.github.com\/v3\/search\/#search-repositories)\r\n+ A mix of keywords and github search fields\r\n\r\nAdditionally, Vizardry adds the following parameters that can be used alone or\r\nin combination with a query\r\n    + `-u ` (search every repositories of  matching 'vim')\r\n    + `-q ` to search on a different grimoire\r\n\r\n#### Search options\r\n\r\nIt is possible to set some github search option in your vimrc, default\r\noptions are show forked repositories and sort by pertinence. These options\r\ncan be overwritten. For instance adding the following to your vimrc will\r\nmake vizardry show results sorted by number of stars hidding forked\r\nrepositries.\r\n\r\n    let g:VizardrySortOptions=\"fork:false+sort:stars\"\r\n\r\nAny combination of github option can be used, a `+` must appear between\r\neach options. For the sort option, available parameters are `stars`,\r\n`forks`, `updated`, by default, it show the best match.\r\n\r\n### Invoke\r\n\r\n`:Invoke [|N]`\r\n\r\n+   If no arguments is specified, reload your plugins.\r\n+   If the argument is a number, ask to install the plugin with that\r\n    number from the last `:Scry` or Invoke.\r\n+   If the argument is a ``, search github for a plugin matching\r\n`` (see above)  and ask for install, the sort criteria for search\r\nresults can be configured (see above).\r\n\r\nSuppose you're in the middle of vimming and you have a sudden need to surround\r\nrandom words in \"scare quotes\". You can't remember who made the surround\r\nplugin, or whether it's called surround.vim, vim-surround or\r\nvim-surround-plugin. Most importantly, you're lazy.\r\n\r\n\r\nJust type:\r\n\r\n    :Invoke surround\r\n\r\nVizardry will pop up a prompt saying:\r\n\r\n    Result 1\/20: tpope\/vim-surround\r\n    (surround.vim: quoting\/parenthesizing made simple)\r\n\r\n    Clone as \"surround\"? (Yes\/Rename\/Displayreadme\/displayHelp\/Next\/Previous\/Abort)\r\n\r\nPress Y and you can immediately start surrounding things.  You can also take a\r\nlook at the README.md directly in vim by hitting `d` or at the help using `h`,\r\nGo to the next or previous script with `n` and `p` or abort `a`. It's that\r\neasy.\r\n\r\nEven plugins with vague or silly names can be found with Vizardry. Imagine\r\nyou're running multiple instances of vim and need a package to sync registers.\r\n\r\nType:\r\n\r\n    :Invoke sync registers\r\n\r\nVizardry will prompt you with:\r\n\r\n    Result 1\/3: ardagnir\/united-front\r\n    (Automatically syncs registers between vim instances)\r\n\r\n    Clone as \"syncregisters\"? (Yes\/Rename\/DisplayMore\/Next\/Previous\/Abort)\r\n\r\nJust as easy.\r\n\r\n#### Display readme on Invoke\r\n\r\nTo view the readme, an other instance of vim is called, the command line can\r\nbe configured:\r\n\r\n    let g:VizardryReadmeReader='view -c \"set ft=markdown\"'\r\n\r\nThe help file reader is also configurable, there is the default:\r\n\r\n    let g:VizardryHelpReader='view -c \"set ft=help\"'\r\n\r\n**Note:** since v2.0, the `-` in the end of the reader line is not required\r\nanymore, please update your configuration accordingly.\r\n\r\nFinally if readme or help is missing, Vizardry will try to search for the\r\nother one, if you dont like this behavior, you can prevent it:\r\n\r\n    let g:VizardryReadmeHelpFallback = 0\r\n\r\n### Banish\r\n\r\n`:Banish `\r\n\r\nBanish a plugin, this only forbid pathogen to load it and does not remove\r\nthe files. You need to restart vim to see the effects.\r\n\r\n### UnBanish\r\n\r\n`:Unbanish `\r\n\r\nReverse a banish.\r\n\r\n### Vanish\r\n\r\n`:Vanish `\r\n\r\nRemove definitively a plugin's files.\r\n\r\n### Evolve\r\n\r\n`:Evolve  [ []]`\r\n\r\nUpgrade the plugin matching <keyword> using remote branche\r\n<branch> if specified. If no <keyword> is given, upgrade\r\nall possible plugins.\r\n\r\nGit plugins are upgraded by doing `git pull origin branch`. Where  `branch` the\r\none specified in argument if any or the current branch of the local repository.\r\nIf `branch` is different from the current branch, Vizardry will first create\r\nor checkout a local branch with the same name as the remote branch requested.\r\n\r\n####\u00c2\u00a0Display Readme On Evolve\r\n\r\nSometimes it can be a good idea to take a quick look at a plugin's README,\r\nhelp or git log when updating, to do so, add the following to your vimrc:\r\n\r\n    let g:VizardryViewReadmeOnEvolve=1\r\n\r\n`:Evolve` will then ask you to display readme help or log each time a plugin is\r\nupgraded.\r\n\r\n#### Evolve from vim.org\r\n\r\n**Evolving directly from vim.org is deprecated.**\r\nTo install plugin found at vim.org from github use:\r\n\r\n    :Invoke -u vim-scripts \r\n\r\nWere <plugin-name> is the actual name of the plugin at vim.org\r\n\r\nYou can also search a plugin by vim.org id:\r\n\r\n    :Invoke -u vim-scripts in:readme script_id=\r\n\r\n### Vizardry<\/a>\r\n\r\n    :Vizardry\r\n\r\nShow a basic usage and Vizardry version.\r\n\r\n### Grimoire\r\n\r\n    :Grimoire [provider]\r\n\r\nList Grimoires or select the `Grimoire` from which you want to `Scry` and\r\n`Invoke` bundles. A grimoire is a website from which you can search for\r\nbundles such as github or bitbucket.\r\n\r\nIt is also possible to set the default grimoire in your vimrc\r\n\r\n    let g:VizardryDefaultGrimoire='github'\r\n\r\nFor Bitbucket and gitlab, an instance url can be supplied, here are the\r\ndefaults:\r\n\r\n    let g:VizardryGitlabInstanceUrl='gitlab.com'\r\n    let g:VizardryBitbucketInstanceUrl='bitbucket.org'\r\n\r\n**Note:**\r\n\r\n*   Bitbucket does not allow to do any filters while searching for public\r\nrepository, thus every github parameters (such as `fork:true`) but `user:name`\r\nand `language:lang` are ignored, when using Bitbucket grimoire. For the same\r\nreason, Bitbuckets queries does not respect `g:VizardryNbScryResults`.\r\n*   Gitlab API is even worse, neither `user` nor ̀`language` or any other github\r\nsearch options works.\r\n\r\n# Magic\r\n\r\nVizardry Magic is a simple way to handle plugin specific configurations files,\r\nthese files will be Banished, Unbanished and Vanished with the bundle they\r\nbelong to.\r\n\r\n## Magic Configuration\r\n\r\nBy default, these files are stored in `bunde\/vizardry\/plugin\/magic`, this path\r\nensure that removing Vizardry will remove the magic files. As it is not always\r\na good idea to keep modified files in a subdirectory of an existing bundle,\r\nthis pas can be modified (and must be modified for submodule mode\r\n[Submodules](#how-to-use-vizardry-with-submodules)). A good idea can be to\r\nkeep them in `~\/.vim\/plugin\/magic`:\r\n\r\n    let g:VizardryMagicDir='~\/.vim\/plugin\/magic'\r\n\r\n\r\n## Magic Commands\r\n\r\n### :Magic<\/a>\r\n\r\n    :Magic  \r\n\r\n\r\nAdds <command> to <bundle> magic file and execute it.\r\n\r\n### :Magicedit\r\n\r\n    :Magicedit \r\n\r\nEdits magic file for <bundle>.\r\n\r\n### :Magicsplit\r\n\r\n    :Magicsplit \r\n\r\nEdits magic file for <bundle>, spliting the current window.\r\n\r\n### :Magicvsplit\r\n\r\n    :Magicvsplit \r\n\r\nEdits magic file for <bundle>, vspliting the current window.\r\n\r\n### :MagicCommit\r\n\r\n    :MagicCommit \r\n\r\nFor submodule (see [Submodules](#how-to-use-vizardry-with-submodules)) mode\r\nonly: Commit the changes to the given magic file.\r\n\r\nDoes nothing in clone mode\r\n\r\n# Get involved\r\n\r\n## Spread the word\r\n\r\nIf you like Vizardry and you are also a vimscript developper, an easy way to\r\nspread the word is to add a Vizardry install section to your plugins README\r\nfor instance:\r\n\r\nIf you have installed [Vizardry](https:\/\/github.com\/dbeniamine\/vizardry) just\r\nrun the following from vim:\r\n\r\n    :Invoke -u  \r\n\r\n## Write Grimoires\r\n\r\nCurrently only github and bitbucket are available, but it is very easy to add a\r\nnew Grimoire, see [issue#3](https:\/\/github.com\/dbeniamine\/vizardry\/issues\/3)\r\nand `:help Vizardry-Dev-grimoires`.\r\n\r\n## Develop inside Vizardry\r\n\r\nIf you like Vizardry and want to help, you can look add `vizardry\/todo.txt`\r\nsee what I improvement I'm planning to add to Vizardry.\r\nIf you are going to modify Vizardry code, please take a look at |Vizardry-Dev|\r\nbefore writing any code.\r\nFeel free to open pull requests when you are done :).\r\n\r\n\r\nMore at https:\/\/github.com\/dbeniamine\/vizardry\r\n","install_details":"# Requirements\r\n\r\n+ Vizardry requires [pathogen](https:\/\/github.com\/tpope\/vim-pathogen). But you\r\n  already have pathogen installed, don't you?\r\n\r\n+ It also needs git, curl, and basic \\*nix commands.\r\n\r\n+ You will probably have issues if you use a Windows OS.\r\n\r\n# Installation\r\n\r\nUse pathogen.\r\n\r\n    cd ~\/.vim\/bundle\r\n    git clone https:\/\/github.com\/dbeniamine\/vizardry\r\n\r\n","5":"# Requirements\r\n\r\n+ Vizardry requires [pathogen](https:\/\/github.com\/tpope\/vim-pathogen). But you\r\n  already have pathogen installed, don't you?\r\n\r\n+ It also needs git, curl, and basic \\*nix commands.\r\n\r\n+ You will probably have issues if you use a Windows OS.\r\n\r\n# Installation\r\n\r\nUse pathogen.\r\n\r\n    cd ~\/.vim\/bundle\r\n    git clone https:\/\/github.com\/dbeniamine\/vizardry\r\n\r\n","first_name":"David","6":"David","last_name":"Beniamine","7":"Beniamine","releases":[{"0":"5235","vim_version":"7.0","1":"7.0","script_version":"2.0.1","2":"2.0.1","version_comment":"v2.0 comes with several improvements:\r\n\r\n+ Grimoires abstraction to install bundles from any provider (Grimoires currently available: github, bitbuckets, gitlab).\r\n+ Re enabling of :Magic family commands with support for submodule mode).\r\n+ A major refactor including, several minor bug fix, and removing dependencies to external commands (sed, grep etc.).\r\n+ A new documentation for developers to help Vizardry enthusiasts improve it.\r\n","3":"v2.0 comes with several improvements:\r\n\r\n+ Grimoires abstraction to install bundles from any provider (Grimoires currently available: github, bitbuckets, gitlab).\r\n+ Re enabling of :Magic family commands with support for submodule mode).\r\n+ A major refactor including, several minor bug fix, and removing dependencies to external commands (sed, grep etc.).\r\n+ A new documentation for developers to help Vizardry enthusiasts improve it.\r\n","package":"vizardry.tgz","4":"vizardry.tgz","src_id":"24155","5":"24155","creation_date":"1459677762","6":"1459677762"},{"0":"5235","vim_version":"7.0","1":"7.0","script_version":"1.4.1","2":"1.4.1","version_comment":"+ ADD: init and update git submodules while Invoking and Evolving to allow dependencies in git modules\r\n+ FIX: Better cleanup on Vanish","3":"+ ADD: init and update git submodules while Invoking and Evolving to allow dependencies in git modules\r\n+ FIX: Better cleanup on Vanish","package":"vizardry.tgz","4":"vizardry.tgz","src_id":"24047","5":"24047","creation_date":"1456497591","6":"1456497591"},{"0":"5235","vim_version":"7.0","1":"7.0","script_version":"1.4","2":"1.4","version_comment":"+ ADD: Display Help file on Invoke and Evolve\r\n+ CHG: Show Help (resp Readme) if Readme (resp Help) not available\r\n+ ADD: Vizardry command for basic help and version\r\n+ ADD: Debug mode\r\n+ CHG: Look for keyword 'vim' instead of language 'vimL' to find other language plugins\r\n+ FIX: put url between quotes for zsh see https:\/\/github.com\/dbeniamine\/vizardry\/issues\/2\r\n+ FIX: Incoherent numbers between Invoke and Scry","3":"+ ADD: Display Help file on Invoke and Evolve\r\n+ CHG: Show Help (resp Readme) if Readme (resp Help) not available\r\n+ ADD: Vizardry command for basic help and version\r\n+ ADD: Debug mode\r\n+ CHG: Look for keyword 'vim' instead of language 'vimL' to find other language plugins\r\n+ FIX: put url between quotes for zsh see https:\/\/github.com\/dbeniamine\/vizardry\/issues\/2\r\n+ FIX: Incoherent numbers between Invoke and Scry","package":"vizardry.tgz","4":"vizardry.tgz","src_id":"23765","5":"23765","creation_date":"1448730135","6":"1448730135"},{"0":"5235","vim_version":"7.0","1":"7.0","script_version":"1.3.2","2":"1.3.2","version_comment":"+ CHG:  Huge documentation cleaning\r\n+ FIX:  Show a warning message when no results are found for a query\r\n+ CHG:  Show deprecated message when trying to evolve a path as a vim.org script\r\n+ Fix:  Evolve completion\r\n","3":"+ CHG:  Huge documentation cleaning\r\n+ FIX:  Show a warning message when no results are found for a query\r\n+ CHG:  Show deprecated message when trying to evolve a path as a vim.org script\r\n+ Fix:  Evolve completion\r\n","package":"vizardry.tgz","4":"vizardry.tgz","src_id":"23610","5":"23610","creation_date":"1442853141","6":"1442853141"},{"0":"5235","vim_version":"7.0","1":"7.0","script_version":"1.3.1","2":"1.3.1","version_comment":"+ Show Git log on evolve\r\n+ Several small interface fix","3":"+ Show Git log on evolve\r\n+ Several small interface fix","package":"vizardry.tgz","4":"vizardry.tgz","src_id":"23609","5":"23609","creation_date":"1442824392","6":"1442824392"},{"0":"5235","vim_version":"7.0","1":"7.0","script_version":"1.3","2":"1.3","version_comment":"ADD: After a call to Scry, Vizardry now prompt you to Invoke a plugin\r\nCHG: Dialog method updated, see release notes for side effects\r\nADD: it is now possible to view a plugin's README after upgrading it with\r\n    :Evolve. Todo do so, add the following to your vimrc:\r\n        let g:VizardryViewReadmeOnEvolve=1\r\n    `:Evolve` will then prompt you to show readme after each plugin upgrade\r\nFix error when Invoking result 0 from Scry\r\n","3":"ADD: After a call to Scry, Vizardry now prompt you to Invoke a plugin\r\nCHG: Dialog method updated, see release notes for side effects\r\nADD: it is now possible to view a plugin's README after upgrading it with\r\n    :Evolve. Todo do so, add the following to your vimrc:\r\n        let g:VizardryViewReadmeOnEvolve=1\r\n    `:Evolve` will then prompt you to show readme after each plugin upgrade\r\nFix error when Invoking result 0 from Scry\r\n","package":"vizardry.tgz","4":"vizardry.tgz","src_id":"23552","5":"23552","creation_date":"1440596885","6":"1440596885"},{"0":"5235","vim_version":"7.0","1":"7.0","script_version":"1.2.1","2":"1.2.1","version_comment":"FIX: Invoke error when using git clone (see https:\/\/github.com\/dbeniamine\/vizardry\/issues\/1)\r\nFIX: Banish bug: \"function ListBanished not found\"\r\n","3":"FIX: Invoke error when using git clone (see https:\/\/github.com\/dbeniamine\/vizardry\/issues\/1)\r\nFIX: Banish bug: \"function ListBanished not found\"\r\n","package":"vizardry.tgz","4":"vizardry.tgz","src_id":"23542","5":"23542","creation_date":"1440317815","6":"1440317815"},{"0":"5235","vim_version":"7.0","1":"7.0","script_version":"1.2","2":"1.2","version_comment":"+ Use autoload to speedup vim startup time\r\n+ Cleaner interface\r\n+ Several small bug fix","3":"+ Use autoload to speedup vim startup time\r\n+ Cleaner interface\r\n+ Several small bug fix","package":"vizardry.tgz","4":"vizardry.tgz","src_id":"23538","5":"23538","creation_date":"1440257605","6":"1440257605"},{"0":"5235","vim_version":"7.0","1":"7.0","script_version":"1.1","2":"1.1","version_comment":"More flexible search option","3":"More flexible search option","package":"vizardry.tgz","4":"vizardry.tgz","src_id":"23533","5":"23533","creation_date":"1440087290","6":"1440087290"},{"0":"5235","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"vizardry.tgz","4":"vizardry.tgz","src_id":"23532","5":"23532","creation_date":"1440083556","6":"1440083556"}]},"5234":{"script_id":"5234","0":"5234","script_name":"lazyList","1":"lazyList","script_type":"utility","2":"utility","summary":"A quick way to create lists in Vim","3":"A quick way to create lists in Vim","description":"LazyList is a vim plugin who gives you possibility to create ordered and non ordered lists very quickly, and this by adding indices to the beginning of each line in the current selection.\r\n\r\nCheck this gif:\r\nhttps:\/\/github.com\/KabbAmine\/lazyList.vim\/raw\/master\/.img\/main.gif\r\n\r\nWith non numerical indices, the plugin can even act smartly:\r\nhttps:\/\/github.com\/KabbAmine\/lazyList.vim\/raw\/master\/.img\/todo.gif\r\n\r\nAs a bonus, the selection algorithm of the plugin can be used as a motion command:\r\nhttps:\/\/github.com\/KabbAmine\/lazyList.vim\/raw\/master\/.img\/motion.gif\r\n\r\nIf this plugin is useful (Or useless) for you, please rate it.\r\n\r\nUSAGE\r\n=====\r\nThe plugin provides one unique command: LazyList, which can be used to add\/remove indices to\/from a selection in NORMAL or VISUAL mode (This command can take 0 or 1 argument(s): The index).\r\n\r\nThe index can be:\r\n\r\n    - A character or a string (e.g +, '* ','- ', 'Chapter X. '...)\r\n    - A special pattern understandable by the plugin:\r\n        %number%: Produces indices starting from number (e.g %1%, %33%...)\r\n    - Both of them (e.g 'Chapter 1, part %1% - '...)\r\n\r\nYou will find all informations in the official repository:\r\nhttps:\/\/github.com\/KabbAmine\/lazyList.vim","4":"LazyList is a vim plugin who gives you possibility to create ordered and non ordered lists very quickly, and this by adding indices to the beginning of each line in the current selection.\r\n\r\nCheck this gif:\r\nhttps:\/\/github.com\/KabbAmine\/lazyList.vim\/raw\/master\/.img\/main.gif\r\n\r\nWith non numerical indices, the plugin can even act smartly:\r\nhttps:\/\/github.com\/KabbAmine\/lazyList.vim\/raw\/master\/.img\/todo.gif\r\n\r\nAs a bonus, the selection algorithm of the plugin can be used as a motion command:\r\nhttps:\/\/github.com\/KabbAmine\/lazyList.vim\/raw\/master\/.img\/motion.gif\r\n\r\nIf this plugin is useful (Or useless) for you, please rate it.\r\n\r\nUSAGE\r\n=====\r\nThe plugin provides one unique command: LazyList, which can be used to add\/remove indices to\/from a selection in NORMAL or VISUAL mode (This command can take 0 or 1 argument(s): The index).\r\n\r\nThe index can be:\r\n\r\n    - A character or a string (e.g +, '* ','- ', 'Chapter X. '...)\r\n    - A special pattern understandable by the plugin:\r\n        %number%: Produces indices starting from number (e.g %1%, %33%...)\r\n    - Both of them (e.g 'Chapter 1, part %1% - '...)\r\n\r\nYou will find all informations in the official repository:\r\nhttps:\/\/github.com\/KabbAmine\/lazyList.vim","install_details":"Manual installation\r\n~~~~~~~~~~~~~~~\r\nInstall the distributed files into Vim runtime directory which is usually `~\/.vim\/`, or `$HOME\/vimfiles` on Windows.\r\n\r\nUsing Pathogen\r\n~~~~~~~~~~~~~\r\nSimply extract the file into `bundle` directory.\r\n\r\nUsing a plugin manager\r\n~~~~~~~~~~~~~~~~~~~\r\nJust add the the following line in your vimrc:\r\n    Plug 'KabbAmine\/lazyList.vim'\r\nThen install the plugin using the adequate command.\r\n(The keyword 'Plug' & the installation command depends of your vim plugin manager)","5":"Manual installation\r\n~~~~~~~~~~~~~~~\r\nInstall the distributed files into Vim runtime directory which is usually `~\/.vim\/`, or `$HOME\/vimfiles` on Windows.\r\n\r\nUsing Pathogen\r\n~~~~~~~~~~~~~\r\nSimply extract the file into `bundle` directory.\r\n\r\nUsing a plugin manager\r\n~~~~~~~~~~~~~~~~~~~\r\nJust add the the following line in your vimrc:\r\n    Plug 'KabbAmine\/lazyList.vim'\r\nThen install the plugin using the adequate command.\r\n(The keyword 'Plug' & the installation command depends of your vim plugin manager)","first_name":"Kabbaj","6":"Kabbaj","last_name":"Amine","7":"Amine","releases":[{"0":"5234","vim_version":"7.0","1":"7.0","script_version":"v0.6","2":"v0.6","version_comment":"* Refactor to make future implementations & integration into other plugin(s) easier\r\n* Add test cases using Vader\r\n### Features\r\n* Add possibility to use selection algorithm as a motion command\r\n### Fixes\r\n* Allow usage of numerical indices greater than 9","3":"* Refactor to make future implementations & integration into other plugin(s) easier\r\n* Add test cases using Vader\r\n### Features\r\n* Add possibility to use selection algorithm as a motion command\r\n### Fixes\r\n* Allow usage of numerical indices greater than 9","package":"lazyList.tar.gz","4":"lazyList.tar.gz","src_id":"23612","5":"23612","creation_date":"1442954295","6":"1442954295"},{"0":"5234","vim_version":"7.0","1":"7.0","script_version":"v0.3","2":"v0.3","version_comment":"Fixes:\r\n- Select one line in VISUAL mode works as expected.\r\n- Don't remove characters from line(s) without indices anymore.","3":"Fixes:\r\n- Select one line in VISUAL mode works as expected.\r\n- Don't remove characters from line(s) without indices anymore.","package":"lazyList.tar.gz","4":"lazyList.tar.gz","src_id":"23536","5":"23536","creation_date":"1440169074","6":"1440169074"},{"0":"5234","vim_version":"7.0","1":"7.0","script_version":"v0.1","2":"v0.1","version_comment":"Initial upload","3":"Initial upload","package":"lazyList.tar.gz","4":"lazyList.tar.gz","src_id":"23528","5":"23528","creation_date":"1440075873","6":"1440075873"}]},"5233":{"script_id":"5233","0":"5233","script_name":"pypi.vim","1":"pypi.vim","script_type":"utility","2":"utility","summary":"Simple plugin for checking the latest version of the Python package in Vim.","3":"Simple plugin for checking the latest version of the Python package in Vim.","description":"## pypi.vim\r\n\r\nSimple plugin for checking the latest version of the Python package in Vim.\r\nhttps:\/\/github.com\/7kfpun\/pypi.vim\r\n\r\n## Requirements\r\n\r\n- [webapi-vim][]\r\n\r\n## Usage\r\n\r\n    :Pypi   \/\/ Check for the latest version of the package\r\n    :Pypi     \/\/ Check for the latest version of multiple packages\r\n    :'<,'>Pypi  \/\/ Update selected packages with the latest version\r\n\r\n## Install\r\n\r\n*  [Pathogen](https:\/\/github.com\/tpope\/vim-pathogen)\r\n    * `git clone https:\/\/github.com\/7kfpun\/pypi.vim.git ~\/.vim\/bundle\/pypi.vim`\r\n    * `git clone https:\/\/github.com\/mattn\/webapi-vim.git ~\/.vim\/bundle\/webapi-vim`\r\n*  [vim-plug](https:\/\/github.com\/junegunn\/vim-plug)\r\n    * `Plug 'mattn\/webapi-vim'`\r\n    * `Plug '7kfpun\/pypi.vim'`\r\n*  [NeoBundle](https:\/\/github.com\/Shougo\/neobundle.vim)\r\n    * `NeoBundle 'mattn\/webapi-vim'`\r\n    * `NeoBundle '7kfpun\/pypi.vim'`\r\n*  [Vundle](https:\/\/github.com\/gmarik\/vundle)\r\n    * `Plugin 'mattn\/webapi-vim'`\r\n    * `Plugin '7kfpun\/pypi.vim'`\r\n\r\n## Settings\r\n\r\n    \/\/ Default settings\r\n    let g:pypi_print_results = 1\r\n    let g:pypi_replace_latest_version = 1\r\n    let g:pypi_replace_type = '=='  \/\/ or '>=' or '<'\r\n    let g:pypi_replace_with_comment = 0\r\n\r\n[webapi-vim]: https:\/\/github.com\/mattn\/webapi-vim","4":"## pypi.vim\r\n\r\nSimple plugin for checking the latest version of the Python package in Vim.\r\nhttps:\/\/github.com\/7kfpun\/pypi.vim\r\n\r\n## Requirements\r\n\r\n- [webapi-vim][]\r\n\r\n## Usage\r\n\r\n    :Pypi   \/\/ Check for the latest version of the package\r\n    :Pypi     \/\/ Check for the latest version of multiple packages\r\n    :'<,'>Pypi  \/\/ Update selected packages with the latest version\r\n\r\n## Install\r\n\r\n*  [Pathogen](https:\/\/github.com\/tpope\/vim-pathogen)\r\n    * `git clone https:\/\/github.com\/7kfpun\/pypi.vim.git ~\/.vim\/bundle\/pypi.vim`\r\n    * `git clone https:\/\/github.com\/mattn\/webapi-vim.git ~\/.vim\/bundle\/webapi-vim`\r\n*  [vim-plug](https:\/\/github.com\/junegunn\/vim-plug)\r\n    * `Plug 'mattn\/webapi-vim'`\r\n    * `Plug '7kfpun\/pypi.vim'`\r\n*  [NeoBundle](https:\/\/github.com\/Shougo\/neobundle.vim)\r\n    * `NeoBundle 'mattn\/webapi-vim'`\r\n    * `NeoBundle '7kfpun\/pypi.vim'`\r\n*  [Vundle](https:\/\/github.com\/gmarik\/vundle)\r\n    * `Plugin 'mattn\/webapi-vim'`\r\n    * `Plugin '7kfpun\/pypi.vim'`\r\n\r\n## Settings\r\n\r\n    \/\/ Default settings\r\n    let g:pypi_print_results = 1\r\n    let g:pypi_replace_latest_version = 1\r\n    let g:pypi_replace_type = '=='  \/\/ or '>=' or '<'\r\n    let g:pypi_replace_with_comment = 0\r\n\r\n[webapi-vim]: https:\/\/github.com\/mattn\/webapi-vim","install_details":"","5":"","first_name":"kf","6":"kf","last_name":"_","7":"_","releases":[{"0":"5233","vim_version":"7.0","1":"7.0","script_version":"0.0.2","2":"0.0.2","version_comment":"Update default settings","3":"Update default settings","package":"pypi-0.0.2.zip","4":"pypi-0.0.2.zip","src_id":"23531","5":"23531","creation_date":"1440083030","6":"1440083030"},{"0":"5233","vim_version":"7.0","1":"7.0","script_version":"0.0.1","2":"0.0.1","version_comment":"Initial upload","3":"Initial upload","package":"pypi-0.0.1.zip","4":"pypi-0.0.1.zip","src_id":"23527","5":"23527","creation_date":"1440066228","6":"1440066228"}]},"5232":{"script_id":"5232","0":"5232","script_name":"vital-power-assert","1":"vital-power-assert","script_type":"utility","2":"utility","summary":"Power Assert in Vim script","3":"Power Assert in Vim script","description":"\r\nSee: https:\/\/github.com\/haya14busa\/vital-power-assert","4":"\r\nSee: https:\/\/github.com\/haya14busa\/vital-power-assert","install_details":"","5":"","first_name":"haya14busa","6":"haya14busa","last_name":" ","7":" ","releases":[{"0":"5232","vim_version":"7.3","1":"7.3","script_version":"v0.9.0","2":"v0.9.0","version_comment":"Initial upload","3":"Initial upload","package":"vital-power-assert-0.9.0.zip","4":"vital-power-assert-0.9.0.zip","src_id":"23524","5":"23524","creation_date":"1439997664","6":"1439997664"}]},"5231":{"script_id":"5231","0":"5231","script_name":"vim-zimwiki-syntax","1":"vim-zimwiki-syntax","script_type":"syntax","2":"syntax","summary":"Syntax highlight and file type detection for Zim","3":"Syntax highlight and file type detection for Zim","description":"This plugin adds support to handle notes created by the Zim (http:\/\/zim-wiki.org) editor. It covers syntax and file type detection.\r\n\r\nhttps:\/\/github.com\/joanrivera\/vim-zimwiki-syntax","4":"This plugin adds support to handle notes created by the Zim (http:\/\/zim-wiki.org) editor. It covers syntax and file type detection.\r\n\r\nhttps:\/\/github.com\/joanrivera\/vim-zimwiki-syntax","install_details":"Option 1: Manual installation\r\n\r\n1. Move ftdetect\/zimwiki.vim to your ~\/.vim\/ftdetect directory.\r\n2. Move syntax\/zimwiki.vim to your ~\/.vim\/syntax directory.\r\n\r\n\r\nOption 2: Vundle installation\r\n\r\n1. Open your ~\/.vimrc file and add the following line:  Plugin \\'joanrivera\/vim-zimwiki-syntax\\'\r\n2. Run :PluginInstall","5":"Option 1: Manual installation\r\n\r\n1. Move ftdetect\/zimwiki.vim to your ~\/.vim\/ftdetect directory.\r\n2. Move syntax\/zimwiki.vim to your ~\/.vim\/syntax directory.\r\n\r\n\r\nOption 2: Vundle installation\r\n\r\n1. Open your ~\/.vimrc file and add the following line:  Plugin \\'joanrivera\/vim-zimwiki-syntax\\'\r\n2. Run :PluginInstall","first_name":"Joan","6":"Joan","last_name":"Rivera","7":"Rivera","releases":[{"0":"5231","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"vim-zimwiki-syntax.tar.gz","4":"vim-zimwiki-syntax.tar.gz","src_id":"23519","5":"23519","creation_date":"1439799130","6":"1439799130"}]},"5230":{"script_id":"5230","0":"5230","script_name":"vim-es6","1":"vim-es6","script_type":"syntax","2":"syntax","summary":"List of JavaScript ES6 snippets and syntax highlighting for vim.","3":"List of JavaScript ES6 snippets and syntax highlighting for vim.","description":"vim es6\r\n\r\n> Write JavaScript ES6 easily with vim.\r\n\r\nScreenshot: https:\/\/raw.githubusercontent.com\/isRuslan\/vim-es6\/master\/sample.gif\r\n\r\nInstall:\r\n\r\n> You need SnipMate installed: https:\/\/github.com\/garbas\/vim-snipmate.\r\n\r\n    To install using Vundle https:\/\/github.com\/gmarik\/vundle:\r\n\r\n\t\" add this line to your .vimrc file\r\n\tPlugin 'isRuslan\/vim-es6'\r\n\r\n    To install using pathogen.vim:\r\n\r\n\tcd ~\/.vim\/bundle\r\n\tgit clone https:\/\/github.com\/isRuslan\/vim-es6.git\r\n\r\n    To manual install download  zip file https:\/\/github.com\/isRuslan\/vim-es6\/releases:\r\n\r\n\tcd ~\/.vim\r\n\tunzip vim-es6.zip\r\n\r\n\r\n    To checkout the source from repository:\r\n\r\n\tcd ~\/.vim\/bundle\r\n\tgit clone https:\/\/github.com\/isRuslan\/vim-es6.git\r\n\r\nSnippets list:\r\n\r\n| gfn→     | `function* name (arg) { yield arg; }` |\r\n| =>→      | `(arg) => { ... },`                               |\r\n| class→  | `class name { constructor () { ...} }` |\r\n| forof→   | `for (let value of arr) { ... }`              |\r\n| im→      | `import lib from 'Library'`                 |","4":"vim es6\r\n\r\n> Write JavaScript ES6 easily with vim.\r\n\r\nScreenshot: https:\/\/raw.githubusercontent.com\/isRuslan\/vim-es6\/master\/sample.gif\r\n\r\nInstall:\r\n\r\n> You need SnipMate installed: https:\/\/github.com\/garbas\/vim-snipmate.\r\n\r\n    To install using Vundle https:\/\/github.com\/gmarik\/vundle:\r\n\r\n\t\" add this line to your .vimrc file\r\n\tPlugin 'isRuslan\/vim-es6'\r\n\r\n    To install using pathogen.vim:\r\n\r\n\tcd ~\/.vim\/bundle\r\n\tgit clone https:\/\/github.com\/isRuslan\/vim-es6.git\r\n\r\n    To manual install download  zip file https:\/\/github.com\/isRuslan\/vim-es6\/releases:\r\n\r\n\tcd ~\/.vim\r\n\tunzip vim-es6.zip\r\n\r\n\r\n    To checkout the source from repository:\r\n\r\n\tcd ~\/.vim\/bundle\r\n\tgit clone https:\/\/github.com\/isRuslan\/vim-es6.git\r\n\r\nSnippets list:\r\n\r\n| gfn→     | `function* name (arg) { yield arg; }` |\r\n| =>→      | `(arg) => { ... },`                               |\r\n| class→  | `class name { constructor () { ...} }` |\r\n| forof→   | `for (let value of arr) { ... }`              |\r\n| im→      | `import lib from 'Library'`                 |","install_details":"","5":"","first_name":"Ruslan","6":"Ruslan","last_name":"Ismagilov","7":"Ismagilov","releases":[{"0":"5230","vim_version":"7.0","1":"7.0","script_version":"2.1","2":"2.1","version_comment":"New improvements to snippets code and to syntax highlighting.","3":"New improvements to snippets code and to syntax highlighting.","package":"vim-es6-2.1.zip","4":"vim-es6-2.1.zip","src_id":"23685","5":"23685","creation_date":"1445790381","6":"1445790381"},{"0":"5230","vim_version":"7.0","1":"7.0","script_version":"2.0","2":"2.0","version_comment":"Initial upload","3":"Initial upload","package":"vim-es6-2.0.zip","4":"vim-es6-2.0.zip","src_id":"23513","5":"23513","creation_date":"1439477718","6":"1439477718"}]},"5229":{"script_id":"5229","0":"5229","script_name":"glsl","1":"glsl","script_type":"syntax","2":"syntax","summary":"Functionality for editing OpenGL Shading Language (GLSL) in Vim","3":"Functionality for editing OpenGL Shading Language (GLSL) in Vim","description":"This package will, in time, provide a complete suite of functionality for editing OpenGL Shading Language (GLSL) code in Vim.\r\n\r\nProvided functionality includes:\r\n- syntax highlighting\r\n- automatic indentation\r\n- file type plug-in, setting options such as formatoptions and foldmethod, among others.\r\n\r\nMore features will follow, such as (but not necessarily limited to) code completion.\r\n\r\nI've tested this using Vim 7.4. It should work on some earlier versions, though.\r\n\r\nFor complete documentation, type \":help glsl\" in Vim after installing the plug-in.\r\n\r\nThe project is hosted at https:\/\/github.com\/brobeson\/glslVim. If you discover a bug, or want to request a feature, please create an issue at https:\/\/github.com\/brobeson\/glslVim\/issues.","4":"This package will, in time, provide a complete suite of functionality for editing OpenGL Shading Language (GLSL) code in Vim.\r\n\r\nProvided functionality includes:\r\n- syntax highlighting\r\n- automatic indentation\r\n- file type plug-in, setting options such as formatoptions and foldmethod, among others.\r\n\r\nMore features will follow, such as (but not necessarily limited to) code completion.\r\n\r\nI've tested this using Vim 7.4. It should work on some earlier versions, though.\r\n\r\nFor complete documentation, type \":help glsl\" in Vim after installing the plug-in.\r\n\r\nThe project is hosted at https:\/\/github.com\/brobeson\/glslVim. If you discover a bug, or want to request a feature, please create an issue at https:\/\/github.com\/brobeson\/glslVim\/issues.","install_details":"1) Download the vimball.\r\n2) Open the vimball in Vim.\r\n3) Type the command \":so %\".\r\n4) Exit Vim.","5":"1) Download the vimball.\r\n2) Open the vimball in Vim.\r\n3) Type the command \":so %\".\r\n4) Exit Vim.","first_name":"Brendan","6":"Brendan","last_name":"","7":"","releases":[{"0":"5229","vim_version":"7.4","1":"7.4","script_version":"0.3","2":"0.3","version_comment":"Add ftplugin with functionality similar to C.","3":"Add ftplugin with functionality similar to C.","package":"glsl.vmb","4":"glsl.vmb","src_id":"23510","5":"23510","creation_date":"1439010951","6":"1439010951"},{"0":"5229","vim_version":"7.4","1":"7.4","script_version":"0.2","2":"0.2","version_comment":"Add automatic indentation when editing GLSL code.","3":"Add automatic indentation when editing GLSL code.","package":"glsl.vmb","4":"glsl.vmb","src_id":"23509","5":"23509","creation_date":"1438978571","6":"1438978571"},{"0":"5229","vim_version":"7.4","1":"7.4","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"glsl.vmb","4":"glsl.vmb","src_id":"23508","5":"23508","creation_date":"1438976150","6":"1438976150"}]},"5228":{"script_id":"5228","0":"5228","script_name":"copy-cut-paste.vim","1":"copy-cut-paste.vim","script_type":"utility","2":"utility","summary":"Naturally copy, cut, and paste between Vim terminal buffer and system clipboard","3":"Naturally copy, cut, and paste between Vim terminal buffer and system clipboard","description":"Note: If `set clipboard=unnamed` works for you, then there is no need for this.\r\n\r\nKeymaps for easy copying, cutting, and pasting between Vim terminal buffer and system clipboard\r\n\r\nSee https:\/\/github.com\/NLKNguyen\/copy-cut-paste.vim","4":"Note: If `set clipboard=unnamed` works for you, then there is no need for this.\r\n\r\nKeymaps for easy copying, cutting, and pasting between Vim terminal buffer and system clipboard\r\n\r\nSee https:\/\/github.com\/NLKNguyen\/copy-cut-paste.vim","install_details":"Install with Vundle plugin manager\r\n\r\n    Plugin 'NLKNguyen\/copy-cut-paste.vim'\r\n\r\nOr manually: copy `copy-cut-paste.vim` file to your `~\/.vim\/plugin\/` directory","5":"Install with Vundle plugin manager\r\n\r\n    Plugin 'NLKNguyen\/copy-cut-paste.vim'\r\n\r\nOr manually: copy `copy-cut-paste.vim` file to your `~\/.vim\/plugin\/` directory","first_name":"Nikyle","6":"Nikyle","last_name":"Nguyen","7":"Nguyen","releases":[{"0":"5228","vim_version":"7.0","1":"7.0","script_version":"0.1.0","2":"0.1.0","version_comment":"Initial upload","3":"Initial upload","package":"copy-cut-paste.vim.tar.gz","4":"copy-cut-paste.vim.tar.gz","src_id":"23507","5":"23507","creation_date":"1438969817","6":"1438969817"}]},"5227":{"script_id":"5227","0":"5227","script_name":"finance.vim","1":"finance.vim","script_type":"utility","2":"utility","summary":"Simple plugin for checking your stock in Vim (Yahoo Finance).","3":"Simple plugin for checking your stock in Vim (Yahoo Finance).","description":"# finance.vim\r\n\r\nSimple plugin for checking your stock in Vim (Yahoo Finance).\r\nhttps:\/\/github.com\/7kfpun\/finance.vim\r\n\r\n# Requirements\r\n\r\n- [webapi-vim][]\r\n\r\n# Usage\r\n\r\n    let g:finance_watchlist = ['0005.HK', 'GOOG']\r\n    let g:finance_format' = '{symbol}: {LastTradePriceOnly} ({Change})'\r\n    let g:finance_separator' = \"\\n\"\r\n\r\n    :Finance\r\n\r\n    :Finance 0005.HK\r\n    :Finance 0005.HK GOOG\r\n\r\n# QuoteProperty\r\n\r\n    AfterHoursChangeRealtime\r\n    AnnualizedGain\r\n    Ask\r\n    AskRealtime\r\n    AverageDailyVolume\r\n    Bid\r\n    BidRealtime\r\n    BookValue\r\n    Change\r\n    ChangeFromFiftydayMovingAverage\r\n    ChangeFromTwoHundreddayMovingAverage\r\n    ChangeFromYearHigh\r\n    ChangeFromYearLow\r\n    ChangePercentRealtime\r\n    ChangeRealtime\r\n    Change_PercentChange\r\n    ChangeinPercent\r\n    Commission\r\n    Currency\r\n    DaysHigh\r\n    DaysLow\r\n    DaysRange\r\n    DaysRangeRealtime\r\n    DaysValueChange\r\n    DaysValueChangeRealtime\r\n    DividendPayDate\r\n    DividendShare\r\n    DividendYield\r\n    EBITDA\r\n    EPSEstimateCurrentYear\r\n    EPSEstimateNextQuarter\r\n    EPSEstimateNextYear\r\n    EarningsShare\r\n    ErrorIndicationreturnedforsymbolchangedinvalid\r\n    ExDividendDate\r\n    FiftydayMovingAverage\r\n    HighLimit\r\n    HoldingsGain\r\n    HoldingsGainPercent\r\n    HoldingsGainPercentRealtime\r\n    HoldingsGainRealtime\r\n    HoldingsValue\r\n    HoldingsValueRealtime\r\n    LastTradeDate\r\n    LastTradePriceOnly\r\n    LastTradeRealtimeWithTime\r\n    LastTradeTime\r\n    LastTradeWithTime\r\n    LowLimit\r\n    MarketCapRealtime\r\n    MarketCapitalization\r\n    MoreInfo\r\n    Name\r\n    Notes\r\n    OneyrTargetPrice\r\n    Open\r\n    OrderBookRealtime\r\n    PEGRatio\r\n    PERatio\r\n    PERatioRealtime\r\n    PercebtChangeFromYearHigh\r\n    PercentChange\r\n    PercentChangeFromFiftydayMovingAverage\r\n    PercentChangeFromTwoHundreddayMovingAverage\r\n    PercentChangeFromYearLow\r\n    PreviousClose\r\n    PriceBook\r\n    PriceEPSEstimateCurrentYear\r\n    PriceEPSEstimateNextYear\r\n    PricePaid\r\n    PriceSales\r\n    SharesOwned\r\n    ShortRatio\r\n    StockExchange\r\n    Symbol\r\n    TickerTrend\r\n    TradeDate\r\n    TwoHundreddayMovingAverage\r\n    Volume\r\n    YearHigh\r\n    YearLow\r\n    YearRange\r\n    symbol\r\n\r\n[webapi-vim]: https:\/\/github.com\/mattn\/webapi-vim","4":"# finance.vim\r\n\r\nSimple plugin for checking your stock in Vim (Yahoo Finance).\r\nhttps:\/\/github.com\/7kfpun\/finance.vim\r\n\r\n# Requirements\r\n\r\n- [webapi-vim][]\r\n\r\n# Usage\r\n\r\n    let g:finance_watchlist = ['0005.HK', 'GOOG']\r\n    let g:finance_format' = '{symbol}: {LastTradePriceOnly} ({Change})'\r\n    let g:finance_separator' = \"\\n\"\r\n\r\n    :Finance\r\n\r\n    :Finance 0005.HK\r\n    :Finance 0005.HK GOOG\r\n\r\n# QuoteProperty\r\n\r\n    AfterHoursChangeRealtime\r\n    AnnualizedGain\r\n    Ask\r\n    AskRealtime\r\n    AverageDailyVolume\r\n    Bid\r\n    BidRealtime\r\n    BookValue\r\n    Change\r\n    ChangeFromFiftydayMovingAverage\r\n    ChangeFromTwoHundreddayMovingAverage\r\n    ChangeFromYearHigh\r\n    ChangeFromYearLow\r\n    ChangePercentRealtime\r\n    ChangeRealtime\r\n    Change_PercentChange\r\n    ChangeinPercent\r\n    Commission\r\n    Currency\r\n    DaysHigh\r\n    DaysLow\r\n    DaysRange\r\n    DaysRangeRealtime\r\n    DaysValueChange\r\n    DaysValueChangeRealtime\r\n    DividendPayDate\r\n    DividendShare\r\n    DividendYield\r\n    EBITDA\r\n    EPSEstimateCurrentYear\r\n    EPSEstimateNextQuarter\r\n    EPSEstimateNextYear\r\n    EarningsShare\r\n    ErrorIndicationreturnedforsymbolchangedinvalid\r\n    ExDividendDate\r\n    FiftydayMovingAverage\r\n    HighLimit\r\n    HoldingsGain\r\n    HoldingsGainPercent\r\n    HoldingsGainPercentRealtime\r\n    HoldingsGainRealtime\r\n    HoldingsValue\r\n    HoldingsValueRealtime\r\n    LastTradeDate\r\n    LastTradePriceOnly\r\n    LastTradeRealtimeWithTime\r\n    LastTradeTime\r\n    LastTradeWithTime\r\n    LowLimit\r\n    MarketCapRealtime\r\n    MarketCapitalization\r\n    MoreInfo\r\n    Name\r\n    Notes\r\n    OneyrTargetPrice\r\n    Open\r\n    OrderBookRealtime\r\n    PEGRatio\r\n    PERatio\r\n    PERatioRealtime\r\n    PercebtChangeFromYearHigh\r\n    PercentChange\r\n    PercentChangeFromFiftydayMovingAverage\r\n    PercentChangeFromTwoHundreddayMovingAverage\r\n    PercentChangeFromYearLow\r\n    PreviousClose\r\n    PriceBook\r\n    PriceEPSEstimateCurrentYear\r\n    PriceEPSEstimateNextYear\r\n    PricePaid\r\n    PriceSales\r\n    SharesOwned\r\n    ShortRatio\r\n    StockExchange\r\n    Symbol\r\n    TickerTrend\r\n    TradeDate\r\n    TwoHundreddayMovingAverage\r\n    Volume\r\n    YearHigh\r\n    YearLow\r\n    YearRange\r\n    symbol\r\n\r\n[webapi-vim]: https:\/\/github.com\/mattn\/webapi-vim","install_details":"","5":"","first_name":"kf","6":"kf","last_name":"kf","7":"kf","releases":[{"0":"5227","vim_version":"7.0","1":"7.0","script_version":"0.0.1","2":"0.0.1","version_comment":"Initial upload","3":"Initial upload","package":"finance-0.0.1.zip","4":"finance-0.0.1.zip","src_id":"23504","5":"23504","creation_date":"1438781074","6":"1438781074"}]},"5226":{"script_id":"5226","0":"5226","script_name":"quick-scope","1":"quick-scope","script_type":"utility","2":"utility","summary":"Highlights the optimal characters to target for the \"f\" key and family","3":"Highlights the optimal characters to target for the \"f\" key and family","description":"GitHub: https:\/\/github.com\/unblevable\/quick-scope\r\n\r\nThis plugin highlights the optimal characters to target for the f, F, t and T motions for easier and faster left-right movement in Vim.\r\n\r\nIf you don't routinely use these keys you should! See ':help f' and ':help ;' to get started and https:\/\/github.com\/unblevable\/quick-scope#moving-across-a-line for a detailed look at why these keys\r\nare so useful.\r\n\r\nIn practice, this plugin should help you get to any word on a line in two or three keystrokes with built-in Vim commands.","4":"GitHub: https:\/\/github.com\/unblevable\/quick-scope\r\n\r\nThis plugin highlights the optimal characters to target for the f, F, t and T motions for easier and faster left-right movement in Vim.\r\n\r\nIf you don't routinely use these keys you should! See ':help f' and ':help ;' to get started and https:\/\/github.com\/unblevable\/quick-scope#moving-across-a-line for a detailed look at why these keys\r\nare so useful.\r\n\r\nIn practice, this plugin should help you get to any word on a line in two or three keystrokes with built-in Vim commands.","install_details":"I recommend using your favorite plugin manager (Plug, Vundle, NeoBundle, Pathogen, etc.).","5":"I recommend using your favorite plugin manager (Plug, Vundle, NeoBundle, Pathogen, etc.).","first_name":"Brian","6":"Brian","last_name":"Le","7":"Le","releases":[{"0":"5226","vim_version":"7.0","1":"7.0","script_version":"1.1.1","2":"1.1.1","version_comment":"Fixed\r\n- Works after sourcing .vimrc\r\n- Works after changing colorscheme\r\n","3":"Fixed\r\n- Works after sourcing .vimrc\r\n- Works after changing colorscheme\r\n","package":"quick-scope-1.1.1.zip","4":"quick-scope-1.1.1.zip","src_id":"23630","5":"23630","creation_date":"1443650394","6":"1443650394"},{"0":"5226","vim_version":"7.0","1":"7.0","script_version":"1.1.0","2":"1.1.0","version_comment":"Added option to trigger highlight on key press (g:qs_highlight_on_keys).","3":"Added option to trigger highlight on key press (g:qs_highlight_on_keys).","package":"quick-scope-1.1.0.zip","4":"quick-scope-1.1.0.zip","src_id":"23534","5":"23534","creation_date":"1440093826","6":"1440093826"},{"0":"5226","vim_version":"7.0","1":"7.0","script_version":"1.0.1","2":"1.0.1","version_comment":"Initial upload","3":"Initial upload","package":"quick-scope-1.0.1.zip","4":"quick-scope-1.0.1.zip","src_id":"23500","5":"23500","creation_date":"1438660552","6":"1438660552"}]},"5225":{"script_id":"5225","0":"5225","script_name":"pipe-mysql.vim","1":"pipe-mysql.vim","script_type":"utility","2":"utility","summary":"MySQL Client for Vim (easy-to-use \/ hassle-free configuration)","3":"MySQL Client for Vim (easy-to-use \/ hassle-free configuration)","description":"MySQL client for Vim \r\nEasy-to-use \/ hassle-free configuration\r\n\r\nSee https:\/\/github.com\/NLKNguyen\/pipe-mysql.vim for keymaps and more details \r\n\r\n**Features**\r\n\r\n* Work with MySQL database at local (with respect to Vim) or at remote machine (via SSH)\r\n* No need to have MySQL installed at local if you plan to execute MySQL statements at remote machine\r\n* Edit MySQL script locally, execute at remote machine, and get result back in Vim's Preview window at local\r\n* Execute a whole MySQL script file, a single line, or a block of MySQL statements\r\n* Set SSH remote and MySQL access on the fly; or use preset for frequently used login info\r\n* Each buffer has independent login info to database\r\n* Easily switch database on the fly\r\n* Include common queries to operate on the target where the cursor is at","4":"MySQL client for Vim \r\nEasy-to-use \/ hassle-free configuration\r\n\r\nSee https:\/\/github.com\/NLKNguyen\/pipe-mysql.vim for keymaps and more details \r\n\r\n**Features**\r\n\r\n* Work with MySQL database at local (with respect to Vim) or at remote machine (via SSH)\r\n* No need to have MySQL installed at local if you plan to execute MySQL statements at remote machine\r\n* Edit MySQL script locally, execute at remote machine, and get result back in Vim's Preview window at local\r\n* Execute a whole MySQL script file, a single line, or a block of MySQL statements\r\n* Set SSH remote and MySQL access on the fly; or use preset for frequently used login info\r\n* Each buffer has independent login info to database\r\n* Easily switch database on the fly\r\n* Include common queries to operate on the target where the cursor is at","install_details":"Install with Vundle plugin manager for easy update (:PluginUpdate)\r\n\r\n    Plugin 'NLKNguyen\/pipe.vim' \"required\r\n    Plugin 'NLKNguyen\/pipe-mysql.vim'\r\n\r\nOr manually: extract the tarball file and copy pipe.vim and pipe-mysql.vim into ~\/.vim\/plugin\/\r\n\r\nSee https:\/\/github.com\/NLKNguyen\/pipe-mysql.vim for optional settings","5":"Install with Vundle plugin manager for easy update (:PluginUpdate)\r\n\r\n    Plugin 'NLKNguyen\/pipe.vim' \"required\r\n    Plugin 'NLKNguyen\/pipe-mysql.vim'\r\n\r\nOr manually: extract the tarball file and copy pipe.vim and pipe-mysql.vim into ~\/.vim\/plugin\/\r\n\r\nSee https:\/\/github.com\/NLKNguyen\/pipe-mysql.vim for optional settings","first_name":"Nikyle","6":"Nikyle","last_name":"Nguyen","7":"Nguyen","releases":[{"0":"5225","vim_version":"7.0","1":"7.0","script_version":"0.1.0","2":"0.1.0","version_comment":"Initial upload","3":"Initial upload","package":"pipe-mysql.tar.gz","4":"pipe-mysql.tar.gz","src_id":"23495","5":"23495","creation_date":"1438292392","6":"1438292392"}]},"5224":{"script_id":"5224","0":"5224","script_name":"progress.vim","1":"progress.vim","script_type":"syntax","2":"syntax","summary":"Update - taking over as maintainer","3":"Update - taking over as maintainer","description":"This includes Progress 4GL\/ABL syntax up to version 11.5.1.\r\n\r\nThe previous maintainer does not currently use progress and has handed over the duties to me.\r\nIf this is not the right way to do this, please contact me and I'll do what ever is needed.\r\n\r\nThanks.\r\n","4":"This includes Progress 4GL\/ABL syntax up to version 11.5.1.\r\n\r\nThe previous maintainer does not currently use progress and has handed over the duties to me.\r\nIf this is not the right way to do this, please contact me and I'll do what ever is needed.\r\n\r\nThanks.\r\n","install_details":"needs to me in the runtime\/syntax folder replacing version 13 of this script.\r\n","5":"needs to me in the runtime\/syntax folder replacing version 13 of this script.\r\n","first_name":"Chris","6":"Chris","last_name":"Ruprecht","7":"Ruprecht","releases":[{"0":"5224","vim_version":"7.0","1":"7.0","script_version":"14","2":"14","version_comment":"Initial upload","3":"Initial upload","package":"progress.vim","4":"progress.vim","src_id":"23480","5":"23480","creation_date":"1437779955","6":"1437779955"}]},"5223":{"script_id":"5223","0":"5223","script_name":"vim3diff","1":"vim3diff","script_type":"utility","2":"utility","summary":"3 way diff","3":"3 way diff","description":"Already known DirDiff plugin (Http:\/\/www.vim.org\/scripts\/script.php?script_id=102) that compares only two directoris...\r\n\r\nThis is improved version of script found at http:\/\/www.cnblogs.com\/absolute8511\/archive\/2012\/02\/07\/2342038.html and has functionality similar to DirDiff, but works for 3 or even more directories.\r\n\r\nUsage: .\/vim3diff.py   \r\n","4":"Already known DirDiff plugin (Http:\/\/www.vim.org\/scripts\/script.php?script_id=102) that compares only two directoris...\r\n\r\nThis is improved version of script found at http:\/\/www.cnblogs.com\/absolute8511\/archive\/2012\/02\/07\/2342038.html and has functionality similar to DirDiff, but works for 3 or even more directories.\r\n\r\nUsage: .\/vim3diff.py   \r\n","install_details":"Unpack .zip file. Put .py file in directory where it can be found by $PATH. Put .vim file in ~\/.vim\/plugins.","5":"Unpack .zip file. Put .py file in directory where it can be found by $PATH. Put .vim file in ~\/.vim\/plugins.","first_name":"Kirill","6":"Kirill","last_name":"Frolov","7":"Frolov","releases":[{"0":"5223","vim_version":"7.0","1":"7.0","script_version":"1.01","2":"1.01","version_comment":"fixed bug","3":"fixed bug","package":"vim3diff.zip","4":"vim3diff.zip","src_id":"23485","5":"23485","creation_date":"1437992474","6":"1437992474"}]},"5222":{"script_id":"5222","0":"5222","script_name":"vim-js-pretty-template","1":"vim-js-pretty-template","script_type":"ftplugin","2":"ftplugin","summary":"highlights JavaScript's Template Strings in other FileType syntax rule","3":"highlights JavaScript's Template Strings in other FileType syntax rule","description":"A Vim plgin to highlight JavaScript's Template Strings contents in other FileType syntax rule which you want.\r\n\r\nPlease see https:\/\/github.com\/Quramy\/vim-js-pretty-template ","4":"A Vim plgin to highlight JavaScript's Template Strings contents in other FileType syntax rule which you want.\r\n\r\nPlease see https:\/\/github.com\/Quramy\/vim-js-pretty-template ","install_details":"### Vundle\r\n\r\nPlace this in your .vimrc:\r\n\r\n```\r\nPlugin 'Quramy\/vim-js-pretty-template'\r\n```\r\n\r\nthen run the following in Vim:\r\n\r\n```\r\n:source %\r\n:PluginInstall\r\n```\r\n\r\n### NeoBundle\r\n\r\n```\r\nNeoBundle 'Quramy\/vim-js-pretty-template'\r\n```\r\n\r\nthen run the following in Vim:\r\n\r\n```\r\n:source %\r\n:NeoBundleInstall\r\n```\r\n\r\n### Pathogen\r\n\r\nRun the following in a terminal:\r\n\r\n```\r\ncd ~\/.vim\/bundle\r\ngit clone https:\/\/github.com\/Quramy\/vim-js-pretty-template\r\n```","5":"### Vundle\r\n\r\nPlace this in your .vimrc:\r\n\r\n```\r\nPlugin 'Quramy\/vim-js-pretty-template'\r\n```\r\n\r\nthen run the following in Vim:\r\n\r\n```\r\n:source %\r\n:PluginInstall\r\n```\r\n\r\n### NeoBundle\r\n\r\n```\r\nNeoBundle 'Quramy\/vim-js-pretty-template'\r\n```\r\n\r\nthen run the following in Vim:\r\n\r\n```\r\n:source %\r\n:NeoBundleInstall\r\n```\r\n\r\n### Pathogen\r\n\r\nRun the following in a terminal:\r\n\r\n```\r\ncd ~\/.vim\/bundle\r\ngit clone https:\/\/github.com\/Quramy\/vim-js-pretty-template\r\n```","first_name":"Yosuke","6":"Yosuke","last_name":"Kurami","7":"Kurami","releases":[{"0":"5222","vim_version":"7.0","1":"7.0","script_version":"0.1.0","2":"0.1.0","version_comment":"Initial upload","3":"Initial upload","package":"vim-js-pretty-template-0.1.0.zip","4":"vim-js-pretty-template-0.1.0.zip","src_id":"23472","5":"23472","creation_date":"1436803516","6":"1436803516"}]},"5221":{"script_id":"5221","0":"5221","script_name":"ctrlp-locate","1":"ctrlp-locate","script_type":"utility","2":"utility","summary":"locate and open it via ctrlp.vim!","3":"locate and open it via ctrlp.vim!","description":"execute 'locate' command and open files via ctrlp.vim (https:\/\/github.com\/ctrlpvim\/ctrlp.vim).\ninspired by unite-locate (https:\/\/github.com\/ujihisa\/unite-locate)\n\nhttps:\/\/github.com\/ompugao\/ctrlp-locate\n\nDependency: locate command, es command, or mdfind command\n","4":"execute 'locate' command and open files via ctrlp.vim (https:\/\/github.com\/ctrlpvim\/ctrlp.vim).\ninspired by unite-locate (https:\/\/github.com\/ujihisa\/unite-locate)\n\nhttps:\/\/github.com\/ompugao\/ctrlp-locate\n\nDependency: locate command, es command, or mdfind command\n","install_details":"install https:\/\/github.com\/ctrlpvim\/ctrlp.vim first\n","5":"install https:\/\/github.com\/ctrlpvim\/ctrlp.vim first\n","first_name":"Shohei","6":"Shohei","last_name":"Fujii","7":"Fujii","releases":[{"0":"5221","vim_version":"7.3","1":"7.3","script_version":"0.7","2":"0.7","version_comment":"use matcher, no need to press ","3":"use matcher, no need to press ","package":"ctrlp-locate-0.7.zip","4":"ctrlp-locate-0.7.zip","src_id":"23590","5":"23590","creation_date":"1442133255","6":"1442133255"},{"0":"5221","vim_version":"7.3","1":"7.3","script_version":"0.6","2":"0.6","version_comment":"set g:ctrlp_key_loop to 0 automatically","3":"set g:ctrlp_key_loop to 0 automatically","package":"ctrlp-locate-0.6.zip","4":"ctrlp-locate-0.6.zip","src_id":"23589","5":"23589","creation_date":"1442111943","6":"1442111943"},{"0":"5221","vim_version":"7.3","1":"7.3","script_version":"0.5","2":"0.5","version_comment":"add g:ctrlp_locate_command_definition, use vital modules","3":"add g:ctrlp_locate_command_definition, use vital modules","package":"ctrlp-locate-0.5.zip","4":"ctrlp-locate-0.5.zip","src_id":"23562","5":"23562","creation_date":"1440859983","6":"1440859983"},{"0":"5221","vim_version":"7.0","1":"7.0","script_version":"0.4","2":"0.4","version_comment":"bugfix","3":"bugfix","package":"ctrlp-locate-0.4.vmb","4":"ctrlp-locate-0.4.vmb","src_id":"23470","5":"23470","creation_date":"1436784974","6":"1436784974"},{"0":"5221","vim_version":"7.0","1":"7.0","script_version":"0.3","2":"0.3","version_comment":"work on mac\/windows","3":"work on mac\/windows","package":"ctrlp-locate-0.3.vmb","4":"ctrlp-locate-0.3.vmb","src_id":"23467","5":"23467","creation_date":"1436711088","6":"1436711088"},{"0":"5221","vim_version":"7.0","1":"7.0","script_version":"0.2","2":"0.2","version_comment":"tiny updates","3":"tiny updates","package":"ctrlp-locate-0.2.vmb","4":"ctrlp-locate-0.2.vmb","src_id":"23466","5":"23466","creation_date":"1436708423","6":"1436708423"},{"0":"5221","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"ctrlp-locate-0.1.vmb","4":"ctrlp-locate-0.1.vmb","src_id":"23465","5":"23465","creation_date":"1436703844","6":"1436703844"}]},"5220":{"script_id":"5220","0":"5220","script_name":"Ferret","1":"Ferret","script_type":"utility","2":"utility","summary":"Enhanced multi-file search for Vim","3":"Enhanced multi-file search for Vim","description":"Ferret improves Vim's multi-file search in four ways:\r\n\r\n1. Powerful multi-file search ~\r\n\r\nFerret provides an |:Ack| command for searching across multiple files using\r\nripgrep (https:\/\/github.com\/BurntSushi\/ripgrep), The Silver Searcher\r\n(https:\/\/github.com\/ggreer\/the_silver_searcher), or Ack\r\n(http:\/\/beyondgrep.com\/). Support for passing options through to the\r\nunderlying search command exists, along with the ability to use full regular\r\nexpression syntax without doing special escaping. On modern versions of Vim\r\n(version 8 or higher, or Neovim), searches are performed asynchronously\r\n(without blocking the UI).\r\n\r\nShortcut mappings are provided to start an |:Ack| search (a) or to\r\nsearch for the word currently under the cursor (s).\r\n\r\nResults are normally displayed in the |quickfix| window, but Ferret also\r\nprovides a |:Lack| command that behaves like |:Ack| but uses the |location-list|\r\ninstead, and a l mapping as a shortcut to |:Lack|.\r\n\r\n|:Back| and |:Black| are analogous to |:Ack| and |:Lack|, but scoped to search\r\nwithin currently open buffers only.\r\n\r\n2. Streamlined multi-file replace ~\r\n\r\nThe companion to |:Ack| is |:Acks| (mnemonic: \"Ack substitute\", accessible via\r\nshortcut r), which allows you to run a multi-file replace across all\r\nthe files placed in the |quickfix| window by a previous invocation of |:Ack| (or\r\n|:Back|).\r\n\r\n3. Quickfix listing enhancements ~\r\n\r\nThe |quickfix| listing itself is enhanced with settings to improve its\r\nusability, and natural mappings that allow quick removal of items from the\r\nlist (for example, you can reduce clutter in the listing by removing lines\r\nthat you don't intend to make changes to).\r\n\r\nAdditionally, Vim's |:cn|, |:cp|, |:cnf| and |:cpf| commands are tweaked to make it\r\neasier to immediately identify matches by centering them within the viewport.\r\n\r\n4. Easy operations on files in the quickfix listing ~\r\n\r\nFinally, Ferret provides a |:Qargs| command that puts the files currently in\r\nthe |quickfix| listing into the |:args| list, where they can be operated on in\r\nbulk via the |:argdo| command. This is what's used under the covers on older\r\nversions of Vim by |:Acks| to do its work (on newer versions the built-in\r\n|:cfdo| is used instead).","4":"Ferret improves Vim's multi-file search in four ways:\r\n\r\n1. Powerful multi-file search ~\r\n\r\nFerret provides an |:Ack| command for searching across multiple files using\r\nripgrep (https:\/\/github.com\/BurntSushi\/ripgrep), The Silver Searcher\r\n(https:\/\/github.com\/ggreer\/the_silver_searcher), or Ack\r\n(http:\/\/beyondgrep.com\/). Support for passing options through to the\r\nunderlying search command exists, along with the ability to use full regular\r\nexpression syntax without doing special escaping. On modern versions of Vim\r\n(version 8 or higher, or Neovim), searches are performed asynchronously\r\n(without blocking the UI).\r\n\r\nShortcut mappings are provided to start an |:Ack| search (a) or to\r\nsearch for the word currently under the cursor (s).\r\n\r\nResults are normally displayed in the |quickfix| window, but Ferret also\r\nprovides a |:Lack| command that behaves like |:Ack| but uses the |location-list|\r\ninstead, and a l mapping as a shortcut to |:Lack|.\r\n\r\n|:Back| and |:Black| are analogous to |:Ack| and |:Lack|, but scoped to search\r\nwithin currently open buffers only.\r\n\r\n2. Streamlined multi-file replace ~\r\n\r\nThe companion to |:Ack| is |:Acks| (mnemonic: \"Ack substitute\", accessible via\r\nshortcut r), which allows you to run a multi-file replace across all\r\nthe files placed in the |quickfix| window by a previous invocation of |:Ack| (or\r\n|:Back|).\r\n\r\n3. Quickfix listing enhancements ~\r\n\r\nThe |quickfix| listing itself is enhanced with settings to improve its\r\nusability, and natural mappings that allow quick removal of items from the\r\nlist (for example, you can reduce clutter in the listing by removing lines\r\nthat you don't intend to make changes to).\r\n\r\nAdditionally, Vim's |:cn|, |:cp|, |:cnf| and |:cpf| commands are tweaked to make it\r\neasier to immediately identify matches by centering them within the viewport.\r\n\r\n4. Easy operations on files in the quickfix listing ~\r\n\r\nFinally, Ferret provides a |:Qargs| command that puts the files currently in\r\nthe |quickfix| listing into the |:args| list, where they can be operated on in\r\nbulk via the |:argdo| command. This is what's used under the covers on older\r\nversions of Vim by |:Acks| to do its work (on newer versions the built-in\r\n|:cfdo| is used instead).","install_details":"","5":"","first_name":"Greg","6":"Greg","last_name":"Hurrell","7":"Hurrell","releases":[{"0":"5220","vim_version":"7.0","1":"7.0","script_version":"5.1","2":"5.1","version_comment":"- Add |g:FerretAckWordWord| setting, to pass `-w` to the underlying search tool when |(FerretAckWord)| is pressed (https:\/\/github.com\/wincent\/ferret\/issues\/66).\r\n- Use `:normal!` instead of |:normal| to avoid running custom mappings (patch from Yoni Weill, https:\/\/github.com\/wincent\/ferret\/pull\/67).\r\n- Append a trailing slash when autocompleting a directory name (https:\/\/github.com\/wincent\/ferret\/issues\/69).\r\n- Fixed failure to detect pre-existing mapping to |(FerretLack)|.\r\n- Worked around breakage caused by `rg` v13.0.0 (https:\/\/github.com\/wincent\/ferret\/issues\/78).\r\n","3":"- Add |g:FerretAckWordWord| setting, to pass `-w` to the underlying search tool when |(FerretAckWord)| is pressed (https:\/\/github.com\/wincent\/ferret\/issues\/66).\r\n- Use `:normal!` instead of |:normal| to avoid running custom mappings (patch from Yoni Weill, https:\/\/github.com\/wincent\/ferret\/pull\/67).\r\n- Append a trailing slash when autocompleting a directory name (https:\/\/github.com\/wincent\/ferret\/issues\/69).\r\n- Fixed failure to detect pre-existing mapping to |(FerretLack)|.\r\n- Worked around breakage caused by `rg` v13.0.0 (https:\/\/github.com\/wincent\/ferret\/issues\/78).\r\n","package":"ferret-5.1.zip","4":"ferret-5.1.zip","src_id":"27651","5":"27651","creation_date":"1625886252","6":"1625886252"},{"0":"5220","vim_version":"7.0","1":"7.0","script_version":"5.0","2":"5.0","version_comment":"- The |(FerretAcks)| mapping now uses |\/\\v| \"very magic\" mode by default. This default can be changed using the |g:FerretVeryMagic| option.\r\n- |:Acks| now preferentially uses |:cdo| (rather than |:cfdo|) to make replacements, which means that it no longer operates on a per-file level and instead targets individual entries within the |quickfix| window. This is relevant if you've used Ferrets mappings to delete entries from the window. The old behavior can be restored with the |g:FerretAcksCommand| option.\r\n- Ferret now has a |:Lacks| command, an analog to |:Acks| which applies to the |location-list|.\r\n- Likewise, Ferret now has a |:Largs| command, analogous to |:Qargs|, which applies to the |location-list| instead of the |quickfix| window.\r\n- The Ferret bindings that are set-up in the |quickfix| window when |g:FerretQFMap| is enabled now also apply to the |location-list|.\r\n","3":"- The |(FerretAcks)| mapping now uses |\/\\v| \"very magic\" mode by default. This default can be changed using the |g:FerretVeryMagic| option.\r\n- |:Acks| now preferentially uses |:cdo| (rather than |:cfdo|) to make replacements, which means that it no longer operates on a per-file level and instead targets individual entries within the |quickfix| window. This is relevant if you've used Ferrets mappings to delete entries from the window. The old behavior can be restored with the |g:FerretAcksCommand| option.\r\n- Ferret now has a |:Lacks| command, an analog to |:Acks| which applies to the |location-list|.\r\n- Likewise, Ferret now has a |:Largs| command, analogous to |:Qargs|, which applies to the |location-list| instead of the |quickfix| window.\r\n- The Ferret bindings that are set-up in the |quickfix| window when |g:FerretQFMap| is enabled now also apply to the |location-list|.\r\n","package":"ferret-5.0.zip","4":"ferret-5.0.zip","src_id":"26527","5":"26527","creation_date":"1559979394","6":"1559979394"},{"0":"5220","vim_version":"7.0","1":"7.0","script_version":"4.1","2":"4.1","version_comment":"- Added |:Quack| command, analogous to |:Ack| but scoped to the files currently listed in the |quickfix| window.\r\n- Fixed option autocompletion.","3":"- Added |:Quack| command, analogous to |:Ack| but scoped to the files currently listed in the |quickfix| window.\r\n- Fixed option autocompletion.","package":"ferret-4.1.zip","4":"ferret-4.1.zip","src_id":"26367","5":"26367","creation_date":"1549004329","6":"1549004329"},{"0":"5220","vim_version":"7.0","1":"7.0","script_version":"4.0.2","2":"4.0.2","version_comment":"- Restore compatibility with versions of `rg` prior to v0.8 (https:\/\/github.com\/wincent\/ferret\/issues\/59).\r\n","3":"- Restore compatibility with versions of `rg` prior to v0.8 (https:\/\/github.com\/wincent\/ferret\/issues\/59).\r\n","package":"ferret-4.0.2.zip","4":"ferret-4.0.2.zip","src_id":"26337","5":"26337","creation_date":"1547232115","6":"1547232115"},{"0":"5220","vim_version":"7.0","1":"7.0","script_version":"4.0.1","2":"4.0.1","version_comment":"- Make |:Acks| behavior the same irrespective of the |'gdefault'| setting.","3":"- Make |:Acks| behavior the same irrespective of the |'gdefault'| setting.","package":"ferret-4.0.1.zip","4":"ferret-4.0.1.zip","src_id":"26332","5":"26332","creation_date":"1546968773","6":"1546968773"},{"0":"5220","vim_version":"7.0","1":"7.0","script_version":"4.0","2":"4.0","version_comment":"- Try to avoid \"press ENTER to continue\" prompts.\r\n- Put search term in |w:quickfix_title| for use in statuslines\r\n  (https:\/\/github.com\/wincent\/ferret\/pull\/57).\r\n- Add |g:FerretExecutableArguments| and |ferret#get_default_arguments()|\r\n  (https:\/\/github.com\/wincent\/ferret\/pull\/46).","3":"- Try to avoid \"press ENTER to continue\" prompts.\r\n- Put search term in |w:quickfix_title| for use in statuslines\r\n  (https:\/\/github.com\/wincent\/ferret\/pull\/57).\r\n- Add |g:FerretExecutableArguments| and |ferret#get_default_arguments()|\r\n  (https:\/\/github.com\/wincent\/ferret\/pull\/46).","package":"ferret-4.0.zip","4":"ferret-4.0.zip","src_id":"26308","5":"26308","creation_date":"1545801831","6":"1545801831"},{"0":"5220","vim_version":"7.0","1":"7.0","script_version":"3.0.2","2":"3.0.2","version_comment":"- Fix broken |:Back| and |:Black| commands\r\n  (https:\/\/github.com\/wincent\/ferret\/issues\/48).","3":"- Fix broken |:Back| and |:Black| commands\r\n  (https:\/\/github.com\/wincent\/ferret\/issues\/48).","package":"ferret-3.0.2.zip","4":"ferret-3.0.2.zip","src_id":"25621","5":"25621","creation_date":"1508983768","6":"1508983768"},{"0":"5220","vim_version":"7.0","1":"7.0","script_version":"3.0.1","2":"3.0.1","version_comment":"- Fix failure to handle search patterns containing multiple escaped spaces\r\n  (https:\/\/github.com\/wincent\/ferret\/issues\/49).","3":"- Fix failure to handle search patterns containing multiple escaped spaces\r\n  (https:\/\/github.com\/wincent\/ferret\/issues\/49).","package":"ferret-3.0.1.zip","4":"ferret-3.0.1.zip","src_id":"25528","5":"25528","creation_date":"1503621010","6":"1503621010"},{"0":"5220","vim_version":"7.0","1":"7.0","script_version":"3.0","2":"3.0","version_comment":"- Improve handling of backslash escapes (https:\/\/github.com\/wincent\/ferret\/issues\/41).\r\n- Add |g:FerretAutojump|.\r\n- Drop support for vim-dispatch.\r\n","3":"- Improve handling of backslash escapes (https:\/\/github.com\/wincent\/ferret\/issues\/41).\r\n- Add |g:FerretAutojump|.\r\n- Drop support for vim-dispatch.\r\n","package":"ferret-3.0.zip","4":"ferret-3.0.zip","src_id":"25307","5":"25307","creation_date":"1497367799","6":"1497367799"},{"0":"5220","vim_version":"7.0","1":"7.0","script_version":"2.0","2":"2.0","version_comment":"- Add support for Neovim, along with |g:FerretNvim| setting.\r\n","3":"- Add support for Neovim, along with |g:FerretNvim| setting.\r\n","package":"ferret-2.0.zip","4":"ferret-2.0.zip","src_id":"25283","5":"25283","creation_date":"1496761213","6":"1496761213"},{"0":"5220","vim_version":"7.0","1":"7.0","script_version":"1.5","2":"1.5","version_comment":"- Improvements to the handling of very large result sets (due to wide lines or many results).\r\n- Added |g:FerretLazyInit|.\r\n- Added missing documentation for |g:FerretJob|.\r\n- Added |g:FerretMaxResults|.\r\n- Added feature-detection for `rg` and `ag`, allowing Ferret to gracefully work with older versions of those tools that do not support all desired command-line switches.","3":"- Improvements to the handling of very large result sets (due to wide lines or many results).\r\n- Added |g:FerretLazyInit|.\r\n- Added missing documentation for |g:FerretJob|.\r\n- Added |g:FerretMaxResults|.\r\n- Added feature-detection for `rg` and `ag`, allowing Ferret to gracefully work with older versions of those tools that do not support all desired command-line switches.","package":"ferret-1.5.zip","4":"ferret-1.5.zip","src_id":"25136","5":"25136","creation_date":"1493947823","6":"1493947823"},{"0":"5220","vim_version":"7.0","1":"7.0","script_version":"1.4","2":"1.4","version_comment":"- Drop broken support for `grep`, printing a prompt to install `rg`, `ag`, or\r\n  `ack`\/`ack-grep` instead.\r\n- If an `ack` executable is not found, search for `ack-grep`, which is the\r\n  name used on Debian-derived distros.","3":"- Drop broken support for `grep`, printing a prompt to install `rg`, `ag`, or\r\n  `ack`\/`ack-grep` instead.\r\n- If an `ack` executable is not found, search for `ack-grep`, which is the\r\n  name used on Debian-derived distros.","package":"ferret-1.4.zip","4":"ferret-1.4.zip","src_id":"24915","5":"24915","creation_date":"1485069918","6":"1485069918"},{"0":"5220","vim_version":"7.0","1":"7.0","script_version":"1.3","2":"1.3","version_comment":"- Reset |'errorformat'| before each search (fixes issue #31).\r\n- Added |:Back| and |:Black| commands, analogous to |:Ack| and |:Lack| but scoped to search within currently open buffers only.\r\n- Change |:Acks| to use |:cfdo| when available rather than |:Qargs| and |:argdo|, to avoid polluting the |arglist|.\r\n- Remove superfluous |QuickFixCmdPost| autocommands, resolving clash with Neomake plug-in (patch from Tom Dooner, #36).\r\n- Add support for searching with ripgrep (`rg`).","3":"- Reset |'errorformat'| before each search (fixes issue #31).\r\n- Added |:Back| and |:Black| commands, analogous to |:Ack| and |:Lack| but scoped to search within currently open buffers only.\r\n- Change |:Acks| to use |:cfdo| when available rather than |:Qargs| and |:argdo|, to avoid polluting the |arglist|.\r\n- Remove superfluous |QuickFixCmdPost| autocommands, resolving clash with Neomake plug-in (patch from Tom Dooner, #36).\r\n- Add support for searching with ripgrep (`rg`).","package":"ferret-1.3.zip","4":"ferret-1.3.zip","src_id":"24881","5":"24881","creation_date":"1483877473","6":"1483877473"},{"0":"5220","vim_version":"7.4","1":"7.4","script_version":"1.2a","2":"1.2a","version_comment":"- Add optional support for running searches asynchronously using Vim's |+job| feature (enabled by default in sufficiently recent versions of Vim); see |g:FerretJob|, |:FerretCancelAsync| and |:FerretPullAsync|.\r\n","3":"- Add optional support for running searches asynchronously using Vim's |+job| feature (enabled by default in sufficiently recent versions of Vim); see |g:FerretJob|, |:FerretCancelAsync| and |:FerretPullAsync|.\r\n","package":"ferret-1.2a.zip","4":"ferret-1.2a.zip","src_id":"24250","5":"24250","creation_date":"1463412588","6":"1463412588"},{"0":"5220","vim_version":"7.0","1":"7.0","script_version":"1.1.1","2":"1.1.1","version_comment":"- Fix another edge case when searching for patterns containing \"#\", only manifesting under dispatch.vim.\r\n","3":"- Fix another edge case when searching for patterns containing \"#\", only manifesting under dispatch.vim.\r\n","package":"ferret-1.1.1.zip","4":"ferret-1.1.1.zip","src_id":"24077","5":"24077","creation_date":"1457391743","6":"1457391743"},{"0":"5220","vim_version":"7.0","1":"7.0","script_version":"1.1","2":"1.1","version_comment":"- Fix edge case when searching for strings of the form \"\".\r\n- Fix edge case when searching for patterns containing \"#\" and \"%\".\r\n- Provide completion for `ag` and `ack` options when using |:Ack| and |:Lack|.\r\n- Fix display of error messages under dispatch.vim.","3":"- Fix edge case when searching for strings of the form \"\".\r\n- Fix edge case when searching for patterns containing \"#\" and \"%\".\r\n- Provide completion for `ag` and `ack` options when using |:Ack| and |:Lack|.\r\n- Fix display of error messages under dispatch.vim.","package":"ferret-1.1.zip","4":"ferret-1.1.zip","src_id":"24075","5":"24075","creation_date":"1457311422","6":"1457311422"},{"0":"5220","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"- Fix broken |:Qargs| command (patch from Daniel Silva).\r\n- Add |g:FerretQFHandler| and |g:FerretLLHandler| options (patch from Daniel\r\n  Silva).\r\n- Make || mappings accessible even |g:FerretMap| is set to 0.\r\n- Fix failure to report filename when using `ack` and explicitly scoping\r\n  search to a single file (patch from Daniel Silva).\r\n- When using `ag`, report multiple matches per line instead of just the first\r\n  (patch from Daniel Silva).\r\n- Improve content and display of error messages.","3":"- Fix broken |:Qargs| command (patch from Daniel Silva).\r\n- Add |g:FerretQFHandler| and |g:FerretLLHandler| options (patch from Daniel\r\n  Silva).\r\n- Make || mappings accessible even |g:FerretMap| is set to 0.\r\n- Fix failure to report filename when using `ack` and explicitly scoping\r\n  search to a single file (patch from Daniel Silva).\r\n- When using `ag`, report multiple matches per line instead of just the first\r\n  (patch from Daniel Silva).\r\n- Improve content and display of error messages.","package":"ferret-1.0.zip","4":"ferret-1.0.zip","src_id":"23833","5":"23833","creation_date":"1451330611","6":"1451330611"},{"0":"5220","vim_version":"7.0","1":"7.0","script_version":"0.3","2":"0.3","version_comment":"- Added highlighting of search pattern and related |g:FerretHlsearch| option\r\n  (patch from Nelo-Thara Wallus).\r\n- Add better error reporting for failed or incorrect searches.\r\n","3":"- Added highlighting of search pattern and related |g:FerretHlsearch| option\r\n  (patch from Nelo-Thara Wallus).\r\n- Add better error reporting for failed or incorrect searches.\r\n","package":"ferret-0.3.zip","4":"ferret-0.3.zip","src_id":"23479","5":"23479","creation_date":"1437778084","6":"1437778084"},{"0":"5220","vim_version":"7.0","1":"7.0","script_version":"0.2","2":"0.2","version_comment":"- Added |FerretDidWrite| and |FerretWillWrite| autocommands (patch from Joe\r\n  Lencioni).\r\n- Add |(FerretAcks)| mapping (patch from Nelo-Thara Wallus).","3":"- Added |FerretDidWrite| and |FerretWillWrite| autocommands (patch from Joe\r\n  Lencioni).\r\n- Add |(FerretAcks)| mapping (patch from Nelo-Thara Wallus).","package":"ferret-0.2.zip","4":"ferret-0.2.zip","src_id":"23474","5":"23474","creation_date":"1437057424","6":"1437057424"},{"0":"5220","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"ferret-0.1.zip","4":"ferret-0.1.zip","src_id":"23462","5":"23462","creation_date":"1436394458","6":"1436394458"}]},"5219":{"script_id":"5219","0":"5219","script_name":"airline-colornum","1":"airline-colornum","script_type":"utility","2":"utility","summary":"Cursor line number color = Airline mode color","3":"Cursor line number color = Airline mode color","description":"Sets the cursor line number to the same color as the current mode in the statusline set by the Vim Airline plugin.\r\n\r\nMore details and documentation at the Github repository:\r\nhttps:\/\/github.com\/ntpeters\/vim-airline-colornum","4":"Sets the cursor line number to the same color as the current mode in the statusline set by the Vim Airline plugin.\r\n\r\nMore details and documentation at the Github repository:\r\nhttps:\/\/github.com\/ntpeters\/vim-airline-colornum","install_details":"There are a few ways you can go about installing this plugin:\r\n\r\n1.  If you have Vundle you can simply add:  Bundle 'ntpeters\/vim-airline-colornum'  to your .vimrc file then run: :BundleInstall \r\n\r\n2.  If you are using Pathogen, you can just run the following command:  git clone git:\/\/github.com\/ntpeters\/vim-airline-colornum.git ~\/.vim\/bundle\/vim-airline-colornum\r\n \r\n3.  While this plugin can also be installed by copying its contents into your ~\/.vim\/ directory, I would highly recommend using one of the above methods as they make managing your Vim plugins painless.","5":"There are a few ways you can go about installing this plugin:\r\n\r\n1.  If you have Vundle you can simply add:  Bundle 'ntpeters\/vim-airline-colornum'  to your .vimrc file then run: :BundleInstall \r\n\r\n2.  If you are using Pathogen, you can just run the following command:  git clone git:\/\/github.com\/ntpeters\/vim-airline-colornum.git ~\/.vim\/bundle\/vim-airline-colornum\r\n \r\n3.  While this plugin can also be installed by copying its contents into your ~\/.vim\/ directory, I would highly recommend using one of the above methods as they make managing your Vim plugins painless.","first_name":"Nate","6":"Nate","last_name":"Peterson","7":"Peterson","releases":[{"0":"5219","vim_version":"7.4","1":"7.4","script_version":"1.1","2":"1.1","version_comment":"Fixes several bugs.","3":"Fixes several bugs.","package":"airline-colornum.tar.gz","4":"airline-colornum.tar.gz","src_id":"23468","5":"23468","creation_date":"1436728341","6":"1436728341"},{"0":"5219","vim_version":"7.2","1":"7.2","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"airline-colornum.tar.gz","4":"airline-colornum.tar.gz","src_id":"23458","5":"23458","creation_date":"1436366327","6":"1436366327"}]},"5218":{"script_id":"5218","0":"5218","script_name":"vim-gurl","1":"vim-gurl","script_type":"utility","2":"utility","summary":"Grabs link to Github \/ Gitlab remote repository for current file & line range","3":"Grabs link to Github \/ Gitlab remote repository for current file & line range","description":"GURL - Git URL\r\n\r\nThis utility allows you to generate a link to the repository of the current file and line (or line range) under your cursor.\r\n","4":"GURL - Git URL\r\n\r\nThis utility allows you to generate a link to the repository of the current file and line (or line range) under your cursor.\r\n","install_details":"https:\/\/github.com\/vitapluvia\/vim-gurl","5":"https:\/\/github.com\/vitapluvia\/vim-gurl","first_name":"vita","6":"vita","last_name":"pluvia","7":"pluvia","releases":[{"0":"5218","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"vim-gurl.tar","4":"vim-gurl.tar","src_id":"23452","5":"23452","creation_date":"1436339833","6":"1436339833"}]},"5217":{"script_id":"5217","0":"5217","script_name":"vim-clipper","1":"vim-clipper","script_type":"utility","2":"utility","summary":"Clipper integration for Vim","3":"Clipper integration for Vim","description":"*clipper.txt* Clipper plug-in for Vim                       *clipper* *vim-clipper*\r\n\r\nCONTENTS                                                     *clipper-contents*\r\n\r\n 1. Intro           |clipper-intro|\r\n 2. Installation    |clipper-installation|\r\n 3. Commands        |clipper-commands|\r\n 4. Options         |clipper-options|\r\n 5. Functions       |clipper-functions|\r\n 6. Mappings        |clipper-mappings|\r\n 7. Website         |clipper-website|\r\n 8. License         |clipper-license|\r\n 9. Authors         |clipper-authors|\r\n10. History         |clipper-history|\r\n\r\n\r\nINTRO                                                           *clipper-intro*\r\n\r\n    \"clipper (noun)\r\n    an instrument for cutting or trimming small pieces off things.\"\r\n\r\n                                                             *clipper-features*\r\nvim-clipper provides integration between Vim and Clipper\r\n(https:\/\/github.com\/wincent\/clipper), which is an OS X \"launch agent\" that\r\nruns in the background providing a service that exposes the local clipboard to\r\ntmux sessions and other processes running both locally and remotely.\r\n\r\nSpecifically, vim-clipper provides a |:Clip| command, to send the last-yanked\r\ntext to Clipper, it sets up a y mapping that calls |:Clip|.\r\nAdditionally, if the |TextYankPost| |autocommand| is available, it will send\r\nthe last-yanked text to Clipper automatically.\r\n\r\n\r\nINSTALLATION                                             *clipper-installation*\r\n\r\nTo install vim-clipper, use your plug-in management system of choice.\r\n\r\nIf you don't have a \"plug-in management system of choice\", I recommend\r\nPathogen (https:\/\/github.com\/tpope\/vim-pathogen) due to its simplicity and\r\nrobustness. Assuming that you have Pathogen installed and configured, and that\r\nyou want to install vim-clipper into `~\/.vim\/bundle`, you can do so with: >\r\n\r\n  git clone https:\/\/github.com\/wincent\/vim-clipper.git ~\/.vim\/bundle\/vim-clipper\r\n\r\nAlternatively, if you use a Git submodule for each Vim plug-in, you could do\r\nthe following after `cd`-ing into the top-level of your Git superproject: >\r\n\r\n  git submodule add https:\/\/github.com\/wincent\/vim-clipper.git ~\/vim\/bundle\/vim-clipper\r\n  git submodule init\r\n\r\nTo generate help tags under Pathogen, you can do so from inside Vim with: >\r\n\r\n  :call pathogen#helptags()\r\n\r\n\r\nCOMMANDS                                                     *clipper-commands*\r\n\r\n                                                                        *:Clip*\r\n:Clip       Sends the last-yanked text to Clipper.\r\n\r\n\r\nOPTIONS                                                       *clipper-options*\r\n\r\n                                                             *g:ClipperAddress*\r\n  |g:ClipperAddress|                                string (default: localhost)\r\n\r\n  Specifies the address at which to connect to the Clipper daemon. To override\r\n  from the default of \"localhost\", set it in your |.vimrc|. The main reason\r\n  you would want to do this is to make Clipper connect to a UNIX domain\r\n  socket: >\r\n\r\n    let g:ClipperAddress=~\/.clipper.sock\r\n<\r\n  Note that if you want to connect using a UNIX domain socket, you must also\r\n  set |g:ClipperPort| to 0.\r\n\r\n  If |g:ClipperAddress| and |g:ClipperPort| provide insufficient\r\n  configurability (for example, because you are using a version of `nc` that\r\n  doesn't support UNIX sockets and want to use an alternative like\r\n  `socat - UNIX-CLIENT:$SOCKET`), then you can use |clipper#set_invocation()|\r\n  to provide an entirely custom string.\r\n\r\n                                                                *g:ClipperPort*\r\n  |g:ClipperPort|                                        number (default: 8377)\r\n\r\n  Specifies the port on which to connect to the Clipper daemon. To override\r\n  from the default of port 8377, set it in your |.vimrc|: >\r\n\r\n    let g:ClipperPort=31337\r\n<\r\n  To connect via a UNIX domain socket, set the port number to 0, and provide\r\n  the path to the socket using the |g:ClipperAddress| option.\r\n\r\n  If |g:ClipperAddress| and |g:ClipperPort| provide insufficient\r\n  configurability (for example, because you are using a version of `nc` that\r\n  doesn't support UNIX sockets and want to use an alternative like\r\n  `socat - UNIX-CLIENT:$SOCKET`), then you can use |clipper#set_invocation()|\r\n  to provide an entirely custom string.\r\n\r\n                                                                *g:ClipperAuto*\r\n  |g:ClipperAuto|                                          boolean (default: 1)\r\n\r\n  Controls whether to use the |TextYankPost| autocommand to route yanked text\r\n  to Clipper automatically. To prevent this, set to 0 in your |.vimrc|: >\r\n\r\n    let g:ClipperAuto=0\r\n<\r\n                                                                 *g:ClipperMap*\r\n  |g:ClipperMap|                                           boolean (default: 1)\r\n\r\n  Controls whether to set up the |(ClipperClip)| mapping. To prevent any\r\n  mapping from being configured, set to 0 in your |.vimrc|: >\r\n\r\n    let g:ClipperMap=0\r\n<\r\n                                                              *g:ClipperLoaded*\r\n  |g:Clipper|                                                  any (no default)\r\n\r\n  To prevent vim-clipper from being loaded, set |g:ClipperLoaded| to any value\r\n  in your |.vimrc|. For example: >\r\n\r\n    let g:ClipperLoaded=1\r\n\r\n\r\nFUNCTIONS                                                   *clipper-functions*\r\n\r\n\r\n  |clipper#set_invocation()|                         *clipper#set_invocation()*\r\n\r\n  Provide a completely custom string to invoke an arbitrary executable with\r\n  arguments. This overrides the automatic invocation that would usually be\r\n  created using `nc` and the values of |g:ClipperAddress| and |g:ClipperPort|.\r\n  This may be necessary in environments where you want to use a UNIX domain\r\n  socket but the local version of `nc` does not support the `-U` switch. For\r\n  example: >\r\n\r\n    call clipper#set_invocation('socat - UNIX-CLIENT:\/path\/to\/socket')\r\n<\r\n  Note: This is a function and not a setting for security reasons; only the\r\n  first call to |clipper#set_invocation()| will have any effect. In this way,\r\n  you can place the call near the start of your |vimrc| without having to\r\n  worry that a malicious plug-in will later overwrite it with something\r\n  nefarious (important because whatever is passed to this function will be\r\n  blindly executed with the |system()| function).\r\n\r\n  As such, even if you don't want to use this feature, it is a good\r\n  idea to lock it down by calling `clipper#set_invocation('')` in your\r\n  |vimrc|.\r\n\r\n\r\nMAPPINGS                                                     *clipper-mappings*\r\n\r\n                                                            *ClipperClip*\r\n                                                          *(ClipperClip)*\r\nvim-clipper maps y to |(ClipperClip)|, which sends the last-yanked\r\ntext to Clipper. To use an alternative mapping instead, create a different one\r\nin your |.vimrc| instead using |:nmap|: >\r\n\r\n  \" Instead of y, use x.\r\n  nmap x (ClipperClip)\r\n\r\nNote that vim-clipper will not try to set up its y mapping if any of\r\nthe following are true:\r\n\r\n- A mapping for y already exists.\r\n- An alternative mapping for |(ClipperClip)| has already been set up from\r\n  a |.vimrc|.\r\n- The mapping has been suppressed by setting |g:ClipperMap| to 1 in your\r\n  |.vimrc|.\r\n\r\n\r\nWEBSITE                                                       *clipper-website*\r\n\r\nThe official vim-clipper source code repo is at:\r\n\r\n  http:\/\/git.wincent.com\/vim-clipper.git\r\n\r\nA mirror exists at:\r\n\r\n  https:\/\/github.com\/wincent\/vim-clipper\r\n\r\nOfficial releases are listed at:\r\n\r\n  http:\/\/www.vim.org\/scripts\/script.php?script_id=5217\r\n\r\n\r\nLICENSE                                                       *clipper-license*\r\n\r\nCopyright 2015-present Greg Hurrell. All rights reserved.\r\n\r\nRedistribution and use in source and binary forms, with or without\r\nmodification, are permitted provided that the following conditions are met:\r\n\r\n1. Redistributions of source code must retain the above copyright notice,\r\n   this list of conditions and the following disclaimer.\r\n2. Redistributions in binary form must reproduce the above copyright notice,\r\n   this list of conditions and the following disclaimer in the documentation\r\n   and\/or other materials provided with the distribution.\r\n\r\nTHIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS \"AS IS\"\r\nAND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE\r\nIMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE\r\nARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDERS OR CONTRIBUTORS BE\r\nLIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR\r\nCONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF\r\nSUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS\r\nINTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN\r\nCONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE)\r\nARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE\r\nPOSSIBILITY OF SUCH DAMAGE.\r\n\r\n\r\nAUTHORS                                                       *clipper-authors*\r\n\r\nvim-clipper is written and maintained by Greg Hurrell .\r\n","4":"*clipper.txt* Clipper plug-in for Vim                       *clipper* *vim-clipper*\r\n\r\nCONTENTS                                                     *clipper-contents*\r\n\r\n 1. Intro           |clipper-intro|\r\n 2. Installation    |clipper-installation|\r\n 3. Commands        |clipper-commands|\r\n 4. Options         |clipper-options|\r\n 5. Functions       |clipper-functions|\r\n 6. Mappings        |clipper-mappings|\r\n 7. Website         |clipper-website|\r\n 8. License         |clipper-license|\r\n 9. Authors         |clipper-authors|\r\n10. History         |clipper-history|\r\n\r\n\r\nINTRO                                                           *clipper-intro*\r\n\r\n    \"clipper (noun)\r\n    an instrument for cutting or trimming small pieces off things.\"\r\n\r\n                                                             *clipper-features*\r\nvim-clipper provides integration between Vim and Clipper\r\n(https:\/\/github.com\/wincent\/clipper), which is an OS X \"launch agent\" that\r\nruns in the background providing a service that exposes the local clipboard to\r\ntmux sessions and other processes running both locally and remotely.\r\n\r\nSpecifically, vim-clipper provides a |:Clip| command, to send the last-yanked\r\ntext to Clipper, it sets up a y mapping that calls |:Clip|.\r\nAdditionally, if the |TextYankPost| |autocommand| is available, it will send\r\nthe last-yanked text to Clipper automatically.\r\n\r\n\r\nINSTALLATION                                             *clipper-installation*\r\n\r\nTo install vim-clipper, use your plug-in management system of choice.\r\n\r\nIf you don't have a \"plug-in management system of choice\", I recommend\r\nPathogen (https:\/\/github.com\/tpope\/vim-pathogen) due to its simplicity and\r\nrobustness. Assuming that you have Pathogen installed and configured, and that\r\nyou want to install vim-clipper into `~\/.vim\/bundle`, you can do so with: >\r\n\r\n  git clone https:\/\/github.com\/wincent\/vim-clipper.git ~\/.vim\/bundle\/vim-clipper\r\n\r\nAlternatively, if you use a Git submodule for each Vim plug-in, you could do\r\nthe following after `cd`-ing into the top-level of your Git superproject: >\r\n\r\n  git submodule add https:\/\/github.com\/wincent\/vim-clipper.git ~\/vim\/bundle\/vim-clipper\r\n  git submodule init\r\n\r\nTo generate help tags under Pathogen, you can do so from inside Vim with: >\r\n\r\n  :call pathogen#helptags()\r\n\r\n\r\nCOMMANDS                                                     *clipper-commands*\r\n\r\n                                                                        *:Clip*\r\n:Clip       Sends the last-yanked text to Clipper.\r\n\r\n\r\nOPTIONS                                                       *clipper-options*\r\n\r\n                                                             *g:ClipperAddress*\r\n  |g:ClipperAddress|                                string (default: localhost)\r\n\r\n  Specifies the address at which to connect to the Clipper daemon. To override\r\n  from the default of \"localhost\", set it in your |.vimrc|. The main reason\r\n  you would want to do this is to make Clipper connect to a UNIX domain\r\n  socket: >\r\n\r\n    let g:ClipperAddress=~\/.clipper.sock\r\n<\r\n  Note that if you want to connect using a UNIX domain socket, you must also\r\n  set |g:ClipperPort| to 0.\r\n\r\n  If |g:ClipperAddress| and |g:ClipperPort| provide insufficient\r\n  configurability (for example, because you are using a version of `nc` that\r\n  doesn't support UNIX sockets and want to use an alternative like\r\n  `socat - UNIX-CLIENT:$SOCKET`), then you can use |clipper#set_invocation()|\r\n  to provide an entirely custom string.\r\n\r\n                                                                *g:ClipperPort*\r\n  |g:ClipperPort|                                        number (default: 8377)\r\n\r\n  Specifies the port on which to connect to the Clipper daemon. To override\r\n  from the default of port 8377, set it in your |.vimrc|: >\r\n\r\n    let g:ClipperPort=31337\r\n<\r\n  To connect via a UNIX domain socket, set the port number to 0, and provide\r\n  the path to the socket using the |g:ClipperAddress| option.\r\n\r\n  If |g:ClipperAddress| and |g:ClipperPort| provide insufficient\r\n  configurability (for example, because you are using a version of `nc` that\r\n  doesn't support UNIX sockets and want to use an alternative like\r\n  `socat - UNIX-CLIENT:$SOCKET`), then you can use |clipper#set_invocation()|\r\n  to provide an entirely custom string.\r\n\r\n                                                                *g:ClipperAuto*\r\n  |g:ClipperAuto|                                          boolean (default: 1)\r\n\r\n  Controls whether to use the |TextYankPost| autocommand to route yanked text\r\n  to Clipper automatically. To prevent this, set to 0 in your |.vimrc|: >\r\n\r\n    let g:ClipperAuto=0\r\n<\r\n                                                                 *g:ClipperMap*\r\n  |g:ClipperMap|                                           boolean (default: 1)\r\n\r\n  Controls whether to set up the |(ClipperClip)| mapping. To prevent any\r\n  mapping from being configured, set to 0 in your |.vimrc|: >\r\n\r\n    let g:ClipperMap=0\r\n<\r\n                                                              *g:ClipperLoaded*\r\n  |g:Clipper|                                                  any (no default)\r\n\r\n  To prevent vim-clipper from being loaded, set |g:ClipperLoaded| to any value\r\n  in your |.vimrc|. For example: >\r\n\r\n    let g:ClipperLoaded=1\r\n\r\n\r\nFUNCTIONS                                                   *clipper-functions*\r\n\r\n\r\n  |clipper#set_invocation()|                         *clipper#set_invocation()*\r\n\r\n  Provide a completely custom string to invoke an arbitrary executable with\r\n  arguments. This overrides the automatic invocation that would usually be\r\n  created using `nc` and the values of |g:ClipperAddress| and |g:ClipperPort|.\r\n  This may be necessary in environments where you want to use a UNIX domain\r\n  socket but the local version of `nc` does not support the `-U` switch. For\r\n  example: >\r\n\r\n    call clipper#set_invocation('socat - UNIX-CLIENT:\/path\/to\/socket')\r\n<\r\n  Note: This is a function and not a setting for security reasons; only the\r\n  first call to |clipper#set_invocation()| will have any effect. In this way,\r\n  you can place the call near the start of your |vimrc| without having to\r\n  worry that a malicious plug-in will later overwrite it with something\r\n  nefarious (important because whatever is passed to this function will be\r\n  blindly executed with the |system()| function).\r\n\r\n  As such, even if you don't want to use this feature, it is a good\r\n  idea to lock it down by calling `clipper#set_invocation('')` in your\r\n  |vimrc|.\r\n\r\n\r\nMAPPINGS                                                     *clipper-mappings*\r\n\r\n                                                            *ClipperClip*\r\n                                                          *(ClipperClip)*\r\nvim-clipper maps y to |(ClipperClip)|, which sends the last-yanked\r\ntext to Clipper. To use an alternative mapping instead, create a different one\r\nin your |.vimrc| instead using |:nmap|: >\r\n\r\n  \" Instead of y, use x.\r\n  nmap x (ClipperClip)\r\n\r\nNote that vim-clipper will not try to set up its y mapping if any of\r\nthe following are true:\r\n\r\n- A mapping for y already exists.\r\n- An alternative mapping for |(ClipperClip)| has already been set up from\r\n  a |.vimrc|.\r\n- The mapping has been suppressed by setting |g:ClipperMap| to 1 in your\r\n  |.vimrc|.\r\n\r\n\r\nWEBSITE                                                       *clipper-website*\r\n\r\nThe official vim-clipper source code repo is at:\r\n\r\n  http:\/\/git.wincent.com\/vim-clipper.git\r\n\r\nA mirror exists at:\r\n\r\n  https:\/\/github.com\/wincent\/vim-clipper\r\n\r\nOfficial releases are listed at:\r\n\r\n  http:\/\/www.vim.org\/scripts\/script.php?script_id=5217\r\n\r\n\r\nLICENSE                                                       *clipper-license*\r\n\r\nCopyright 2015-present Greg Hurrell. All rights reserved.\r\n\r\nRedistribution and use in source and binary forms, with or without\r\nmodification, are permitted provided that the following conditions are met:\r\n\r\n1. Redistributions of source code must retain the above copyright notice,\r\n   this list of conditions and the following disclaimer.\r\n2. Redistributions in binary form must reproduce the above copyright notice,\r\n   this list of conditions and the following disclaimer in the documentation\r\n   and\/or other materials provided with the distribution.\r\n\r\nTHIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS \"AS IS\"\r\nAND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE\r\nIMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE\r\nARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDERS OR CONTRIBUTORS BE\r\nLIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR\r\nCONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF\r\nSUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS\r\nINTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN\r\nCONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE)\r\nARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE\r\nPOSSIBILITY OF SUCH DAMAGE.\r\n\r\n\r\nAUTHORS                                                       *clipper-authors*\r\n\r\nvim-clipper is written and maintained by Greg Hurrell .\r\n","install_details":"","5":"","first_name":"Greg","6":"Greg","last_name":"Hurrell","7":"Hurrell","releases":[{"0":"5217","vim_version":"7.0","1":"7.0","script_version":"2.2","2":"2.2","version_comment":"- Attempt to autodetect when host platform's `nc` executable requires the `-N` switch (https:\/\/github.com\/wincent\/vim-clipper\/pull\/3).\r\n- Make autodetection work case-insensitively (patch from J Eduardo, https:\/\/github.com\/wincent\/vim-clipper\/pull\/5).\r\n","3":"- Attempt to autodetect when host platform's `nc` executable requires the `-N` switch (https:\/\/github.com\/wincent\/vim-clipper\/pull\/3).\r\n- Make autodetection work case-insensitively (patch from J Eduardo, https:\/\/github.com\/wincent\/vim-clipper\/pull\/5).\r\n","package":"vim-clipper-2.2.zip","4":"vim-clipper-2.2.zip","src_id":"27397","5":"27397","creation_date":"1607472071","6":"1607472071"},{"0":"5217","vim_version":"7.0","1":"7.0","script_version":"2.1","2":"2.1","version_comment":"- Add ability to customize invocation with |clipper#set_invocation()|.","3":"- Add ability to customize invocation with |clipper#set_invocation()|.","package":"vim-clipper-2.1.zip","4":"vim-clipper-2.1.zip","src_id":"26412","5":"26412","creation_date":"1551904843","6":"1551904843"},{"0":"5217","vim_version":"7.0","1":"7.0","script_version":"2.0","2":"2.0","version_comment":"- Add ability to automatically send yanked text to Clipper using the\r\n  |TextYankPost| autocommand, and the corresponding |g:ClipperAuto| setting to\r\n  provide an opt-out mechanism.","3":"- Add ability to automatically send yanked text to Clipper using the\r\n  |TextYankPost| autocommand, and the corresponding |g:ClipperAuto| setting to\r\n  provide an opt-out mechanism.","package":"vim-clipper-2.0.zip","4":"vim-clipper-2.0.zip","src_id":"25529","5":"25529","creation_date":"1503708648","6":"1503708648"},{"0":"5217","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"- Rename |ClipperClip| to |(ClipperClip)|.\r\n- Add |g:ClipperAddress| and support for connecting to the Clipper daemon via\r\n  a UNIX domain socket.","3":"- Rename |ClipperClip| to |(ClipperClip)|.\r\n- Add |g:ClipperAddress| and support for connecting to the Clipper daemon via\r\n  a UNIX domain socket.","package":"vim-clipper-1.0.zip","4":"vim-clipper-1.0.zip","src_id":"24304","5":"24304","creation_date":"1465003998","6":"1465003998"},{"0":"5217","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"vim-clipper-0.1.zip","4":"vim-clipper-0.1.zip","src_id":"23450","5":"23450","creation_date":"1436243032","6":"1436243032"}]},"5216":{"script_id":"5216","0":"5216","script_name":"Terminus","1":"Terminus","script_type":"utility","2":"utility","summary":"Enhanced terminal integration for Vim","3":"Enhanced terminal integration for Vim","description":"Terminus enhances Vim's integration with the terminal in four ways,\r\nparticularly when using tmux (https:\/\/tmux.github.io\/) and iTerm\r\n(https:\/\/www.iterm2.com\/), closing the gap between terminal and GUI Vim:\r\n\r\n1. Cursor shape change in insert mode ~\r\n\r\nIn insert mode, the cursor shape changes to a thin vertical bar. On leaving\r\ninset mode, it reverts to the standard \"block\" shape.\r\n\r\n2. Improved mouse support ~\r\n\r\nActivates 'mouse' support in all modes and additionally tries to activate\r\n|sgr-mouse| support, which allows the mouse to work \"even in columns beyond\r\n223\".\r\n\r\n3. Focus reporting ~\r\n\r\nAllows Vim to receive |FocusGained| and |FocusLost| events, even in the\r\nterminal and inside tmux. This is in turn used to fire the |:checktime|\r\ncommand, which, in conjunction with the 'autoread', allows Vim to\r\nautomatically pick up changes made by other processes when switching to and\r\nfrom Vim.\r\n\r\n4. \"Bracketed Paste\" mode ~\r\n\r\nSets up \"Bracketed Paste\" mode, which means you can forget about manually\r\nsetting the 'paste' option and simply go ahead and paste in any mode.","4":"Terminus enhances Vim's integration with the terminal in four ways,\r\nparticularly when using tmux (https:\/\/tmux.github.io\/) and iTerm\r\n(https:\/\/www.iterm2.com\/), closing the gap between terminal and GUI Vim:\r\n\r\n1. Cursor shape change in insert mode ~\r\n\r\nIn insert mode, the cursor shape changes to a thin vertical bar. On leaving\r\ninset mode, it reverts to the standard \"block\" shape.\r\n\r\n2. Improved mouse support ~\r\n\r\nActivates 'mouse' support in all modes and additionally tries to activate\r\n|sgr-mouse| support, which allows the mouse to work \"even in columns beyond\r\n223\".\r\n\r\n3. Focus reporting ~\r\n\r\nAllows Vim to receive |FocusGained| and |FocusLost| events, even in the\r\nterminal and inside tmux. This is in turn used to fire the |:checktime|\r\ncommand, which, in conjunction with the 'autoread', allows Vim to\r\nautomatically pick up changes made by other processes when switching to and\r\nfrom Vim.\r\n\r\n4. \"Bracketed Paste\" mode ~\r\n\r\nSets up \"Bracketed Paste\" mode, which means you can forget about manually\r\nsetting the 'paste' option and simply go ahead and paste in any mode.","install_details":"","5":"","first_name":"Greg","6":"Greg","last_name":"Hurrell","7":"Hurrell","releases":[{"0":"5216","vim_version":"7.0","1":"7.0","script_version":"1.3","2":"1.3","version_comment":"- Add support for Neovim.","3":"- Add support for Neovim.","package":"terminus-1.3.zip","4":"terminus-1.3.zip","src_id":"25284","5":"25284","creation_date":"1496763303","6":"1496763303"},{"0":"5216","vim_version":"7.0","1":"7.0","script_version":"1.2","2":"1.2","version_comment":"- Reduce delay on leaving insert mode to 10ms.\r\n- Work-around lag for focus\/blur events caused by creation and destruction of\r\n  tmux splits.\r\n- Tweak insert mode mappings to work correctly when omni completion is\r\n  active (https:\/\/github.com\/wincent\/terminus\/pull\/18).","3":"- Reduce delay on leaving insert mode to 10ms.\r\n- Work-around lag for focus\/blur events caused by creation and destruction of\r\n  tmux splits.\r\n- Tweak insert mode mappings to work correctly when omni completion is\r\n  active (https:\/\/github.com\/wincent\/terminus\/pull\/18).","package":"terminus-1.2.zip","4":"terminus-1.2.zip","src_id":"25043","5":"25043","creation_date":"1490107373","6":"1490107373"},{"0":"5216","vim_version":"7.0","1":"7.0","script_version":"1.1","2":"1.1","version_comment":"- Use non-deprecated escape sequences when running on sufficiently recent\r\n  versions of iTerm.\r\n","3":"- Use non-deprecated escape sequences when running on sufficiently recent\r\n  versions of iTerm.\r\n","package":"terminus-1.2.zip","4":"terminus-1.2.zip","src_id":"24376","5":"24376","creation_date":"1468461293","6":"1468461293"},{"0":"5216","vim_version":"7.0","1":"7.0","script_version":"1.0.1","2":"1.0.1","version_comment":"- Correctly guard against Terminus being loaded multiple times.","3":"- Correctly guard against Terminus being loaded multiple times.","package":"terminus-1.0.1.zip","4":"terminus-1.0.1.zip","src_id":"23966","5":"23966","creation_date":"1454118247","6":"1454118247"},{"0":"5216","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"- Silence unwanted \"No matching autocommands\" output on gaining\/losing focus\r\n  in normal mode.","3":"- Silence unwanted \"No matching autocommands\" output on gaining\/losing focus\r\n  in normal mode.","package":"terminus-1.0.zip","4":"terminus-1.0.zip","src_id":"23832","5":"23832","creation_date":"1451330522","6":"1451330522"},{"0":"5216","vim_version":"7.0","1":"7.0","script_version":"0.4","2":"0.4","version_comment":"- Enabled support for KDE Konsole (patch from Jan Christoph Ebersbach).\r\n- Added |g:TerminusReplaceCursorShape| and made cursor shape substition work\r\n  with VTE terminals such as gnome-terminal (patch from Jan Christoph\r\n  Ebersbach).\r\n- Fixed bug where file modelines were being inappropriately evaluated when on\r\n  |FocusGained| and |FocusLost| events.\r\n- Added guard for \"Unknown option: t_SR\" for older versions of Vim (patch from\r\n  Joe Lencioni).\r\n- Added support for \"tmux\" `TERM` type.","3":"- Enabled support for KDE Konsole (patch from Jan Christoph Ebersbach).\r\n- Added |g:TerminusReplaceCursorShape| and made cursor shape substition work\r\n  with VTE terminals such as gnome-terminal (patch from Jan Christoph\r\n  Ebersbach).\r\n- Fixed bug where file modelines were being inappropriately evaluated when on\r\n  |FocusGained| and |FocusLost| events.\r\n- Added guard for \"Unknown option: t_SR\" for older versions of Vim (patch from\r\n  Joe Lencioni).\r\n- Added support for \"tmux\" `TERM` type.","package":"terminus-0.4.zip","4":"terminus-0.4.zip","src_id":"23674","5":"23674","creation_date":"1444921333","6":"1444921333"},{"0":"5216","vim_version":"7.0","1":"7.0","script_version":"0.2","2":"0.2","version_comment":"- Added |g:TerminusInsertCursorShape| and |g:TerminusNormalCursorShape|\r\n  settings for selecting among \"bar\", \"block\" and \"underline\" cursor shapes.\r\n","3":"- Added |g:TerminusInsertCursorShape| and |g:TerminusNormalCursorShape|\r\n  settings for selecting among \"bar\", \"block\" and \"underline\" cursor shapes.\r\n","package":"terminus-0.2.zip","4":"terminus-0.2.zip","src_id":"23478","5":"23478","creation_date":"1437764799","6":"1437764799"},{"0":"5216","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"terminus-0.1.zip","4":"terminus-0.1.zip","src_id":"23447","5":"23447","creation_date":"1436165777","6":"1436165777"}]},"5215":{"script_id":"5215","0":"5215","script_name":"Loupe","1":"Loupe","script_type":"utility","2":"utility","summary":"Enhanced in-file search for Vim","3":"Enhanced in-file search for Vim","description":"Loupe enhances Vim's |search-commands| in four ways:\r\n\r\n1. Makes the currently selected match easier to see ~\r\n\r\nWhen searching using |\/|, |?|, |star|, |#|, |n|, |N| or similar, it can be hard to see\r\nthe \"current\" match from among all the matches that 'hlsearch' highlights.\r\nLoupe makes the currently selected match easier to see by:\r\n\r\n- Applying a different |:highlight| group (by default, |hl-IncSearch|) to the\r\n  match under the cursor.\r\n- Keeping the matching line centered within the window when jumping between\r\n  matches with |n| and |N|.\r\n\r\n2. Applies sane pattern syntax by default ~\r\n\r\nLoupe makes \"very magic\" (|\/\\v|) syntax apply by default when searching. This\r\nis true even if you initiate a search via a novel means, such as from a visual\r\nselection or with a complicated |:range| prefix.\r\n\r\nThis means that you can use a pattern syntax closer to the familiar regular\r\nexpression syntax from languages such as Perl, Ruby, JavaScript (indeed, most\r\nother modern languages that support regular expressions).\r\n\r\n3. Provides a shortcut to remove search highlighting ~\r\n\r\nLoupe maps n to quickly remove all 'hlsearch' highlighting (although\r\nyou can provide an alternative mapping of your choosing or suppress the\r\nfeature entirely).\r\n\r\n4. Sensible defaults for search-related features ~\r\n\r\nLoupe provides reasonable defaults for most search-related Vim settings to\r\nprovide a good \"out of the box\" experience. For more details, or to see how to\r\noverride Loupe's settings, see |loupe-overrides|.","4":"Loupe enhances Vim's |search-commands| in four ways:\r\n\r\n1. Makes the currently selected match easier to see ~\r\n\r\nWhen searching using |\/|, |?|, |star|, |#|, |n|, |N| or similar, it can be hard to see\r\nthe \"current\" match from among all the matches that 'hlsearch' highlights.\r\nLoupe makes the currently selected match easier to see by:\r\n\r\n- Applying a different |:highlight| group (by default, |hl-IncSearch|) to the\r\n  match under the cursor.\r\n- Keeping the matching line centered within the window when jumping between\r\n  matches with |n| and |N|.\r\n\r\n2. Applies sane pattern syntax by default ~\r\n\r\nLoupe makes \"very magic\" (|\/\\v|) syntax apply by default when searching. This\r\nis true even if you initiate a search via a novel means, such as from a visual\r\nselection or with a complicated |:range| prefix.\r\n\r\nThis means that you can use a pattern syntax closer to the familiar regular\r\nexpression syntax from languages such as Perl, Ruby, JavaScript (indeed, most\r\nother modern languages that support regular expressions).\r\n\r\n3. Provides a shortcut to remove search highlighting ~\r\n\r\nLoupe maps n to quickly remove all 'hlsearch' highlighting (although\r\nyou can provide an alternative mapping of your choosing or suppress the\r\nfeature entirely).\r\n\r\n4. Sensible defaults for search-related features ~\r\n\r\nLoupe provides reasonable defaults for most search-related Vim settings to\r\nprovide a good \"out of the box\" experience. For more details, or to see how to\r\noverride Loupe's settings, see |loupe-overrides|.","install_details":"","5":"","first_name":"Greg","6":"Greg","last_name":"Hurrell","7":"Hurrell","releases":[{"0":"5215","vim_version":"7.0","1":"7.0","script_version":"1.2.2","2":"1.2.2","version_comment":"- Fix error-handling to work regardless of |'iskeyword'| setting (https:\/\/github.com\/wincent\/loupe\/pull\/14).\r\n\r\n","3":"- Fix error-handling to work regardless of |'iskeyword'| setting (https:\/\/github.com\/wincent\/loupe\/pull\/14).\r\n\r\n","package":"loupe-1.2.2.zip","4":"loupe-1.2.2.zip","src_id":"26174","5":"26174","creation_date":"1533662520","6":"1533662520"},{"0":"5215","vim_version":"7.0","1":"7.0","script_version":"1.2.1","2":"1.2.1","version_comment":"- Match default Vim behavior of opening folds when jumping to a match.","3":"- Match default Vim behavior of opening folds when jumping to a match.","package":"loupe-1.2.1.zip","4":"loupe-1.2.1.zip","src_id":"24375","5":"24375","creation_date":"1468460916","6":"1468460916"},{"0":"5215","vim_version":"7.0","1":"7.0","script_version":"1.2","2":"1.2","version_comment":"- Suppress unwanted cursor movement after |(LoupeClearHighlight)| and\r\n  when using |:nohighlight|.\r\n- Expose |loupe#hlmatch()| (previously was a private function) for users who\r\n  wish to do low-level intergration with other plug-ins.\r\n- Provide || mappings for |star|, |#|, |n|, |N|, |gstar|, |g#| (see\r\n  |(LoupeStar)|, |(LoupeOctothorpe)|, |(Loupen)|,\r\n  |(LoupeN)|, |(LoupeGStar)|, |(LoupeGOctothorpe)|).","3":"- Suppress unwanted cursor movement after |(LoupeClearHighlight)| and\r\n  when using |:nohighlight|.\r\n- Expose |loupe#hlmatch()| (previously was a private function) for users who\r\n  wish to do low-level intergration with other plug-ins.\r\n- Provide || mappings for |star|, |#|, |n|, |N|, |gstar|, |g#| (see\r\n  |(LoupeStar)|, |(LoupeOctothorpe)|, |(Loupen)|,\r\n  |(LoupeN)|, |(LoupeGStar)|, |(LoupeGOctothorpe)|).","package":"loupe-1.2.zip","4":"loupe-1.2.zip","src_id":"24348","5":"24348","creation_date":"1467037386","6":"1467037386"},{"0":"5215","vim_version":"7.0","1":"7.0","script_version":"1.1","2":"1.1","version_comment":"- Make compatible with older versions of Vim that do not have |v:hlsearch|.\r\n- Add support for special delimiters with |:substitute| command.","3":"- Make compatible with older versions of Vim that do not have |v:hlsearch|.\r\n- Add support for special delimiters with |:substitute| command.","package":"loupe-1.1.zip","4":"loupe-1.1.zip","src_id":"24332","5":"24332","creation_date":"1466041366","6":"1466041366"},{"0":"5215","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"- Renamed the |LoupeClearHighlight| mapping to\r\n  |(LoupeClearHighlight)|.","3":"- Renamed the |LoupeClearHighlight| mapping to\r\n  |(LoupeClearHighlight)|.","package":"loupe-1.0.zip","4":"loupe-1.0.zip","src_id":"23831","5":"23831","creation_date":"1451330374","6":"1451330374"},{"0":"5215","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"loupe-0.1.zip","4":"loupe-0.1.zip","src_id":"23446","5":"23446","creation_date":"1436135426","6":"1436135426"}]},"5214":{"script_id":"5214","0":"5214","script_name":"vim-qlist","1":"vim-qlist","script_type":"utility","2":"utility","summary":"Persist the results of :ilist and related commands via the quickfix list.","3":"Persist the results of :ilist and related commands via the quickfix list.","description":"Vim-qlist is an updated, more powerful, version of the function discussed in this \/r\/vim thread:\r\n\r\n    http:\/\/www.reddit.com\/r\/vim\/comments\/1rzvsm\/do_any_of_you_redirect_results_of_i_to_the\/\r\n\r\nThe purpose of this script is to make the results of \"include-search\" and \"definition-search\" easier to navigate and more persistant by using the quickfix list instead of the default list-like interface.\r\n\r\nDevelopment currently happens on GitHub: https:\/\/github.com\/romainl\/vim-qlist. Feel free to submit issues and feature requests.","4":"Vim-qlist is an updated, more powerful, version of the function discussed in this \/r\/vim thread:\r\n\r\n    http:\/\/www.reddit.com\/r\/vim\/comments\/1rzvsm\/do_any_of_you_redirect_results_of_i_to_the\/\r\n\r\nThe purpose of this script is to make the results of \"include-search\" and \"definition-search\" easier to navigate and more persistant by using the quickfix list instead of the default list-like interface.\r\n\r\nDevelopment currently happens on GitHub: https:\/\/github.com\/romainl\/vim-qlist. Feel free to submit issues and feature requests.","install_details":"Use your favorite plugin manager or dump the files in this repository in their standard location:\r\n\r\non Unix-like systems...\r\n\r\n    ~\/.vim\/doc\/qlist.txt\r\n    ~\/.vim\/plugin\/qlist.vim\r\n\r\non Windows...\r\n\r\n    %userprofile%\\vimfiles\\doc\\qlist.txt\r\n    %userprofile%\\vimfiles\\plugin\\qlist.vim\r\n\r\nDon't forget to execute the following command to make the documentation\r\nglobally available:\r\n\r\non Unix-like systems...\r\n\r\n    :helptags ~\/.vim\/doc\r\n\r\non Windows...\r\n\r\n    :helptags %userprofile%\\vimfiles\\doc","5":"Use your favorite plugin manager or dump the files in this repository in their standard location:\r\n\r\non Unix-like systems...\r\n\r\n    ~\/.vim\/doc\/qlist.txt\r\n    ~\/.vim\/plugin\/qlist.vim\r\n\r\non Windows...\r\n\r\n    %userprofile%\\vimfiles\\doc\\qlist.txt\r\n    %userprofile%\\vimfiles\\plugin\\qlist.vim\r\n\r\nDon't forget to execute the following command to make the documentation\r\nglobally available:\r\n\r\non Unix-like systems...\r\n\r\n    :helptags ~\/.vim\/doc\r\n\r\non Windows...\r\n\r\n    :helptags %userprofile%\\vimfiles\\doc","first_name":"Romain","6":"Romain","last_name":"Lafourcade","7":"Lafourcade","releases":[{"0":"5214","vim_version":"7.0","1":"7.0","script_version":"0.0.3","2":"0.0.3","version_comment":"Added \"bang\" support: :Ilist! and :dlist!.","3":"Added \"bang\" support: :Ilist! and :dlist!.","package":"vim-qlist-0.0.3.zip","4":"vim-qlist-0.0.3.zip","src_id":"23678","5":"23678","creation_date":"1445176822","6":"1445176822"},{"0":"5214","vim_version":"7.0","1":"7.0","script_version":"0.0.2","2":"0.0.2","version_comment":"* fixed visual selection handling\r\n* updated the documentation","3":"* fixed visual selection handling\r\n* updated the documentation","package":"vim-qlist-0.0.2.zip","4":"vim-qlist-0.0.2.zip","src_id":"23550","5":"23550","creation_date":"1440532188","6":"1440532188"},{"0":"5214","vim_version":"7.0","1":"7.0","script_version":"0.0.1","2":"0.0.1","version_comment":"Initial upload","3":"Initial upload","package":"vim-qlist.zip","4":"vim-qlist.zip","src_id":"23442","5":"23442","creation_date":"1436045965","6":"1436045965"}]},"5213":{"script_id":"5213","0":"5213","script_name":"vim-AHKcomplete","1":"vim-AHKcomplete","script_type":"ftplugin","2":"ftplugin","summary":"Omnicomplete for autohotkey script.","3":"Omnicomplete for autohotkey script.","description":"I've never found a good omni-completing plugin for AutoHotkey script. So I write this plugin to help me developing AHK script. This project is on GitHub: https:\/\/github.com\/huleiak47\/vim-AHKcomplete, enjoy it.\r\n\r\nThis plugin need +python feature.","4":"I've never found a good omni-completing plugin for AutoHotkey script. So I write this plugin to help me developing AHK script. This project is on GitHub: https:\/\/github.com\/huleiak47\/vim-AHKcomplete, enjoy it.\r\n\r\nThis plugin need +python feature.","install_details":"unzip this package into your vimfiles directory. Add `autocmd FileType autohotkey setl omnifunc=ahkcomplete#Complete` to .vimrc file to enable this plugin. If you want the preview of AHK commands, you should add `set completeopt+=preview` to .vimrc file. Use  to get completion.","5":"unzip this package into your vimfiles directory. Add `autocmd FileType autohotkey setl omnifunc=ahkcomplete#Complete` to .vimrc file to enable this plugin. If you want the preview of AHK commands, you should add `set completeopt+=preview` to .vimrc file. Use  to get completion.","first_name":"Hu","6":"Hu","last_name":"Lei","7":"Lei","releases":[{"0":"5213","vim_version":"7.4","1":"7.4","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"vim-AHKcomplete.zip","4":"vim-AHKcomplete.zip","src_id":"23440","5":"23440","creation_date":"1436019579","6":"1436019579"}]},"5212":{"script_id":"5212","0":"5212","script_name":"vim-on-write","1":"vim-on-write","script_type":"utility","2":"utility","summary":"Easily register commands executed when the current buffer or a given files match","3":"Easily register commands executed when the current buffer or a given files match","description":"Usage\r\n\r\n:OnWrite < command >\r\n\r\nRegister a command executed when the current buffer is saved.\r\nOnly one command can be registered for a buffer.\r\n\r\nExample:\r\n\r\nThe following command copy the current file on the server when the buffer is written.\r\n:OnWrite scp % server:\/tmp\/\r\n\r\n:OnWriteGlob < glob > < command >\r\n\r\nRegister a command executed when a file matching the glob is saved.\r\nOnly one command can be registered for a glob, but a single file can\r\nmatch multiple glob.\r\n\r\nExample:\r\n\r\nThe following command copy the *.py files when are saved.\r\n:OnWriteGlob *.py scp % server:\/tmp\/\r\n\r\n:CancelOnWrite [< glob >]\r\n\r\nRemove the command triggered for the current buffer or a glob.\r\n\r\nhttps:\/\/github.com\/andreax79\/vim-on-write","4":"Usage\r\n\r\n:OnWrite < command >\r\n\r\nRegister a command executed when the current buffer is saved.\r\nOnly one command can be registered for a buffer.\r\n\r\nExample:\r\n\r\nThe following command copy the current file on the server when the buffer is written.\r\n:OnWrite scp % server:\/tmp\/\r\n\r\n:OnWriteGlob < glob > < command >\r\n\r\nRegister a command executed when a file matching the glob is saved.\r\nOnly one command can be registered for a glob, but a single file can\r\nmatch multiple glob.\r\n\r\nExample:\r\n\r\nThe following command copy the *.py files when are saved.\r\n:OnWriteGlob *.py scp % server:\/tmp\/\r\n\r\n:CancelOnWrite [< glob >]\r\n\r\nRemove the command triggered for the current buffer or a glob.\r\n\r\nhttps:\/\/github.com\/andreax79\/vim-on-write","install_details":"This plugin follows the standard runtime path structure and it can be installed with a variety of plugin managers:\r\n\r\nVundle\r\n\r\nAdd this line to your ~\/.vimrc (or $HOME\\vimfiles.vimrc on Windows) configuration file:\r\nBundle 'andreax79\/vim-on-write'\r\n\r\nPathogen\r\n\r\nGo in your Vim bundle directory ~\/.vim\/bundle ($HOME\\vimfiles\\bundle on Windows) and execute the following command:\r\ngit clone https:\/\/github.com\/andreax79\/vim-on-write\r\n\r\nManual\r\n\r\nCopy all of the files into your ~\/.vim ($HOME\\vimfiles on Windows) directory","5":"This plugin follows the standard runtime path structure and it can be installed with a variety of plugin managers:\r\n\r\nVundle\r\n\r\nAdd this line to your ~\/.vimrc (or $HOME\\vimfiles.vimrc on Windows) configuration file:\r\nBundle 'andreax79\/vim-on-write'\r\n\r\nPathogen\r\n\r\nGo in your Vim bundle directory ~\/.vim\/bundle ($HOME\\vimfiles\\bundle on Windows) and execute the following command:\r\ngit clone https:\/\/github.com\/andreax79\/vim-on-write\r\n\r\nManual\r\n\r\nCopy all of the files into your ~\/.vim ($HOME\\vimfiles on Windows) directory","first_name":"Andrea","6":"Andrea","last_name":"Bonomi","7":"Bonomi","releases":[{"0":"5212","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"vim-on-write-1.0.tgz","4":"vim-on-write-1.0.tgz","src_id":"23438","5":"23438","creation_date":"1435929064","6":"1435929064"}]},"5211":{"script_id":"5211","0":"5211","script_name":"vim-qf","1":"vim-qf","script_type":"utility","2":"utility","summary":"Tame the quickfix window.","3":"Tame the quickfix window.","description":"vim-qf\u00e2\u0080\u0093short for vim-quickfix\u00e2\u0080\u0093is a small collection of settings, commands and mappings put together to make working with the location\/quickfix list\/window smoother.\r\n\r\nFEATURES\r\n\r\n    - disable soft-wrapping in the location\/quickfix window\r\n    - disable relative numbers in the location\/quickfix window\r\n    - quickfix buffers are hidden from :ls and buffer navigation\r\n    - optional Ack.vim-inspired mappings\r\n    - optional mappings for :cnext, :cprevious, :lnext, :lprevious that wrap around the beginning and end of the list\r\n    - optional mapping for jumping to and from the location\/quickfix window,\r\n    - filter and restore the current list\r\n    - perform commands on each line in the curent list\r\n    - perform commands on each file in the curent list\r\n    - open the location\/quickfix window automatically after :make, :grep, :lvimgrep and friends if there are valid locations\/errors\r\n    - quit Vim if the last window is a location\/quickfix window\r\n    - close location window automatically when quitting parent window\r\n    - jump to next group of entries belonging to same file (\"file grouping\")\r\n    - save and load named lists\r\n\r\nDevelopment currently happens on GitHub: https:\/\/github.com\/romainl\/vim-qf. Feel free to submit issues and feature requests.","4":"vim-qf\u00e2\u0080\u0093short for vim-quickfix\u00e2\u0080\u0093is a small collection of settings, commands and mappings put together to make working with the location\/quickfix list\/window smoother.\r\n\r\nFEATURES\r\n\r\n    - disable soft-wrapping in the location\/quickfix window\r\n    - disable relative numbers in the location\/quickfix window\r\n    - quickfix buffers are hidden from :ls and buffer navigation\r\n    - optional Ack.vim-inspired mappings\r\n    - optional mappings for :cnext, :cprevious, :lnext, :lprevious that wrap around the beginning and end of the list\r\n    - optional mapping for jumping to and from the location\/quickfix window,\r\n    - filter and restore the current list\r\n    - perform commands on each line in the curent list\r\n    - perform commands on each file in the curent list\r\n    - open the location\/quickfix window automatically after :make, :grep, :lvimgrep and friends if there are valid locations\/errors\r\n    - quit Vim if the last window is a location\/quickfix window\r\n    - close location window automatically when quitting parent window\r\n    - jump to next group of entries belonging to same file (\"file grouping\")\r\n    - save and load named lists\r\n\r\nDevelopment currently happens on GitHub: https:\/\/github.com\/romainl\/vim-qf. Feel free to submit issues and feature requests.","install_details":"Use your favorite plugin manager or dump the files below in their standard location:\r\n\r\n    # Unix-like systems\r\n    ~\/.vim\/after\/ftplugin\/qf.vim\r\n    ~\/.vim\/autoload\/qf.vim\r\n    ~\/.vim\/doc\/qf.txt\r\n    ~\/.vim\/plugin\/qf.vim\r\n\r\n    # Windows\r\n    %userprofile%\\vimfiles\\after\\ftplugin\\qf.vim\r\n    %userprofile%\\vimfiles\\autoload\\qf.vim\r\n    %userprofile%\\vimfiles\\doc\\qf.txt\r\n    %userprofile%\\vimfiles\\plugin\\qf.vim\r\n\r\nIf you go with the manual method, don't forget to execute the following command to make the documentation globally available:\r\n\r\n    :helptags ~\/.vim\/doc\r\n\r\non Unix-like systems, or:\r\n\r\n    :helptags %userprofile%\\vimfiles\\doc\r\n\r\non Windows.","5":"Use your favorite plugin manager or dump the files below in their standard location:\r\n\r\n    # Unix-like systems\r\n    ~\/.vim\/after\/ftplugin\/qf.vim\r\n    ~\/.vim\/autoload\/qf.vim\r\n    ~\/.vim\/doc\/qf.txt\r\n    ~\/.vim\/plugin\/qf.vim\r\n\r\n    # Windows\r\n    %userprofile%\\vimfiles\\after\\ftplugin\\qf.vim\r\n    %userprofile%\\vimfiles\\autoload\\qf.vim\r\n    %userprofile%\\vimfiles\\doc\\qf.txt\r\n    %userprofile%\\vimfiles\\plugin\\qf.vim\r\n\r\nIf you go with the manual method, don't forget to execute the following command to make the documentation globally available:\r\n\r\n    :helptags ~\/.vim\/doc\r\n\r\non Unix-like systems, or:\r\n\r\n    :helptags %userprofile%\\vimfiles\\doc\r\n\r\non Windows.","first_name":"Romain","6":"Romain","last_name":"Lafourcade","7":"Lafourcade","releases":[{"0":"5211","vim_version":"7.4","1":"7.4","script_version":"0.2.0","2":"0.2.0","version_comment":"Many new features:\r\n\r\n- Open the qf\/loc window at the bottom or the top of the screen.\r\n- Automatic opening of the qf\/loc window can be disabled.\r\n- Automatic resizing of the qf\/loc window can be enabled.\r\n- Max size of the qf\/loc window can be defined.\r\n- Automatic quitting can be disabled.\r\n- `:Keep` and `:Reject` can work on bufname or text or both or neither, in which case they work on the word under the cursor.\r\n- Views are saved for better comfort while toggling windows.\r\n- \"Stay\" variants of the toggle mappings.\r\n\r\nPotentially breaking changes:\r\n\r\n`` mappings have new more readable names. Efforts have been made to maintain backward compatibility but new mappings will follow the new naming scheme so it may be a good idea to change your custom mappings now. Following is a table showing the new names:\r\n\r\nOld name ---> New name\r\n--------------------|----------------------\r\n`QfCprevious` ---> `qf_qf_previous`\r\n`QfCnext` ---> `qf_qf_next`\r\n`QfLprevious` ---> `qf_loc_previous`\r\n`QfLnext` ---> `qf_loc_next`\r\n`QfSwitch` ---> `qf_qf_switch`\r\n`QfCtoggle` ---> `qf_qf_toggle`\r\n`QfLtoggle` ---> `qf_loc_toggle`","3":"Many new features:\r\n\r\n- Open the qf\/loc window at the bottom or the top of the screen.\r\n- Automatic opening of the qf\/loc window can be disabled.\r\n- Automatic resizing of the qf\/loc window can be enabled.\r\n- Max size of the qf\/loc window can be defined.\r\n- Automatic quitting can be disabled.\r\n- `:Keep` and `:Reject` can work on bufname or text or both or neither, in which case they work on the word under the cursor.\r\n- Views are saved for better comfort while toggling windows.\r\n- \"Stay\" variants of the toggle mappings.\r\n\r\nPotentially breaking changes:\r\n\r\n`` mappings have new more readable names. Efforts have been made to maintain backward compatibility but new mappings will follow the new naming scheme so it may be a good idea to change your custom mappings now. Following is a table showing the new names:\r\n\r\nOld name ---> New name\r\n--------------------|----------------------\r\n`QfCprevious` ---> `qf_qf_previous`\r\n`QfCnext` ---> `qf_qf_next`\r\n`QfLprevious` ---> `qf_loc_previous`\r\n`QfLnext` ---> `qf_loc_next`\r\n`QfSwitch` ---> `qf_qf_switch`\r\n`QfCtoggle` ---> `qf_qf_toggle`\r\n`QfLtoggle` ---> `qf_loc_toggle`","package":"vim-qf.zip","4":"vim-qf.zip","src_id":"25586","5":"25586","creation_date":"1506180338","6":"1506180338"},{"0":"5211","vim_version":"7.4","1":"7.4","script_version":"0.1.0","2":"0.1.0","version_comment":"Added \"preview\" command: p","3":"Added \"preview\" command: p","package":"vim-qf.zip","4":"vim-qf.zip","src_id":"24668","5":"24668","creation_date":"1477236155","6":"1477236155"},{"0":"5211","vim_version":"7.3","1":"7.3","script_version":"0.0.9","2":"0.0.9","version_comment":"Added two \"global\" commands for toggling the quickfix\/location windows:\r\n\r\n    - :QfCToggle\r\n    - :QfLToggle","3":"Added two \"global\" commands for toggling the quickfix\/location windows:\r\n\r\n    - :QfCToggle\r\n    - :QfLToggle","package":"vim-qf.zip","4":"vim-qf.zip","src_id":"24518","5":"24518","creation_date":"1473610552","6":"1473610552"},{"0":"5211","vim_version":"7.3","1":"7.3","script_version":"0.0.8","2":"0.0.8","version_comment":"- Added list management feature.\r\n- Fixed QFCnext and friends.\r\n- Updated the documentation.","3":"- Added list management feature.\r\n- Fixed QFCnext and friends.\r\n- Updated the documentation.","package":"vim-qf.zip","4":"vim-qf.zip","src_id":"24461","5":"24461","creation_date":"1471786344","6":"1471786344"},{"0":"5211","vim_version":"7.3","1":"7.3","script_version":"0.0.7","2":"0.0.7","version_comment":"New features:\r\n\r\n    - :Keep\r\n    - :Reject\r\n    - { and } to jump to next file grouping\r\n\r\nDeprecation warning: :Filter is on its way out.","3":"New features:\r\n\r\n    - :Keep\r\n    - :Reject\r\n    - { and } to jump to next file grouping\r\n\r\nDeprecation warning: :Filter is on its way out.","package":"vim-qf.zip","4":"vim-qf.zip","src_id":"24157","5":"24157","creation_date":"1459883407","6":"1459883407"},{"0":"5211","vim_version":"7.0","1":"7.0","script_version":"v0.0.4","2":"v0.0.4","version_comment":"Massive refactoring of the filter\/restore mechanism.","3":"Massive refactoring of the filter\/restore mechanism.","package":"vim-qf-0.0.4.zip","4":"vim-qf-0.0.4.zip","src_id":"23499","5":"23499","creation_date":"1438540149","6":"1438540149"},{"0":"5211","vim_version":"7.0","1":"7.0","script_version":"0.0.3","2":"0.0.3","version_comment":"* better statusline handling\r\n* sample configuration in the documentation","3":"* better statusline handling\r\n* sample configuration in the documentation","package":"vim-qf.zip","4":"vim-qf.zip","src_id":"23439","5":"23439","creation_date":"1436012690","6":"1436012690"},{"0":"5211","vim_version":"7.0","1":"7.0","script_version":"0.0.2","2":"0.0.2","version_comment":"Fixed empty zip. Sorry for the inconvenience :-(","3":"Fixed empty zip. Sorry for the inconvenience :-(","package":"vim-qf.zip","4":"vim-qf.zip","src_id":"23437","5":"23437","creation_date":"1435866795","6":"1435866795"},{"0":"5211","vim_version":"7.0","1":"7.0","script_version":"0.0.2","2":"0.0.2","version_comment":"Tame the quickfix list\/window.","3":"Tame the quickfix list\/window.","package":"vim-qf.zip","4":"vim-qf.zip","src_id":"23436","5":"23436","creation_date":"1435792897","6":"1435792897"},{"0":"5211","vim_version":"7.0","1":"7.0","script_version":"0.0.2","2":"0.0.2","version_comment":"Initial upload","3":"Initial upload","package":"vim-qf.zip","4":"vim-qf.zip","src_id":"23435","5":"23435","creation_date":"1435792734","6":"1435792734"}]},"5210":{"script_id":"5210","0":"5210","script_name":"autoSolarize","1":"autoSolarize","script_type":"utility","2":"utility","summary":"Automatically switches between light and dark background for solarized","3":"Automatically switches between light and dark background for solarized","description":"#Auto Solarized\r\n\r\nThis will change your vim colour scheme to either solarized dark or light\r\ndepending on the time of day.\r\n\r\n    { 07:00 < time < 17:00 } = light\r\n\r\n    { 07:00 > time > 17:00 } = dark\r\n\r\nPull requests welcome!\r\n\r\n## Dependencies\r\n\r\nThis relies on [Solarized VIM](http:\/\/ethanschoonover.com\/solarized\/vim-colors-solarized)\r\n\r\n## Installation\r\n\r\n[Vundle](https:\/\/github.com\/gmarik\/Vundle.vim) is probably your best bet and\r\nwhat is recommended.\r\n\r\n## Usage\r\n\r\nAdd to your .vimrc to map leader sc to update your colours.\r\n\r\n    noremap sc :call AutoSetSolarized()\r\n    autocmd VimEnter * call AutoSetSolarized()\r\n\r\n## Tested on\r\n\r\n- Auto Solarized was developed on and tested with Vim 7.3 on OSX, Linux","4":"#Auto Solarized\r\n\r\nThis will change your vim colour scheme to either solarized dark or light\r\ndepending on the time of day.\r\n\r\n    { 07:00 < time < 17:00 } = light\r\n\r\n    { 07:00 > time > 17:00 } = dark\r\n\r\nPull requests welcome!\r\n\r\n## Dependencies\r\n\r\nThis relies on [Solarized VIM](http:\/\/ethanschoonover.com\/solarized\/vim-colors-solarized)\r\n\r\n## Installation\r\n\r\n[Vundle](https:\/\/github.com\/gmarik\/Vundle.vim) is probably your best bet and\r\nwhat is recommended.\r\n\r\n## Usage\r\n\r\nAdd to your .vimrc to map leader sc to update your colours.\r\n\r\n    noremap sc :call AutoSetSolarized()\r\n    autocmd VimEnter * call AutoSetSolarized()\r\n\r\n## Tested on\r\n\r\n- Auto Solarized was developed on and tested with Vim 7.3 on OSX, Linux","install_details":"","5":"","first_name":"Josh","6":"Josh","last_name":"Teeter","7":"Teeter","releases":[{"0":"5210","vim_version":"7.3","1":"7.3","script_version":"0.0.6","2":"0.0.6","version_comment":"Initial upload","3":"Initial upload","package":"autoSolarize-0.0.6.tar.gz","4":"autoSolarize-0.0.6.tar.gz","src_id":"23433","5":"23433","creation_date":"1435773180","6":"1435773180"}]},"5209":{"script_id":"5209","0":"5209","script_name":"confirm_quit.vim","1":"confirm_quit.vim","script_type":"utility","2":"utility","summary":"Ask for confirmation before quitting Vim","3":"Ask for confirmation before quitting Vim","description":"- Homepage: http:\/\/code.arp242.net\/confirm_quit.vim\r\n\r\n-----------------------\r\n\r\nAsk for confirmation before quitting Vim.\r\n\r\nI originally wrote this as an answer on vi Stack Exchange:\r\nhttp:\/\/vi.stackexchange.com\/a\/3712\/51\r\n\r\nThe idea is based on the \"ConfirmQuit\" script:\r\nhttp:\/\/www.vim.org\/scripts\/script.php?script_id=1072\r\n","4":"- Homepage: http:\/\/code.arp242.net\/confirm_quit.vim\r\n\r\n-----------------------\r\n\r\nAsk for confirmation before quitting Vim.\r\n\r\nI originally wrote this as an answer on vi Stack Exchange:\r\nhttp:\/\/vi.stackexchange.com\/a\/3712\/51\r\n\r\nThe idea is based on the \"ConfirmQuit\" script:\r\nhttp:\/\/www.vim.org\/scripts\/script.php?script_id=1072\r\n","install_details":"","5":"","first_name":"Martin","6":"Martin","last_name":"Tournoij","7":"Tournoij","releases":[{"0":"5209","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Download from homepage","3":"Download from homepage","package":"download-from-homepage.tar.gz","4":"download-from-homepage.tar.gz","src_id":"24688","5":"24688","creation_date":"1477882698","6":"1477882698"}]},"5208":{"script_id":"5208","0":"5208","script_name":"complete_email.vim","1":"complete_email.vim","script_type":"utility","2":"utility","summary":"Allow completion of email addresses","3":"Allow completion of email addresses","description":"- Homepage: http:\/\/code.arp242.net\/complete_email.vim\r\n\r\n----------------------------------------------------------------------\r\n\r\nAllow completion of email addresses so you can use Vim as a basic \"address book\".\r\n\r\nThis is useful when you use Vim to compose emails in a program such as mutt. I have the following settings in my muttrc:\r\n\r\n\tset edit_headers = yes          # Edit the headers of your outgoing messages\r\n\tset autoedit = yes              # Go directly to editor after pressing m\r\n\r\nAfter pressing m I immediately go to Vim, and can fill out the headers myself:\r\n\r\n\tFrom: Martin Tournoij \r\n\tTo: \r\n\tCc: \r\n\tBcc: \r\n\tSubject: \r\n\tReply-To: \r\n\r\nI can then use this plugin to quickly fill in the To:, Cc:, etc. fields.\r\n\r\n\r\nBasic usage\r\n-----------------------\r\n- Use  to complete.\r\n- Use :AddEmailAddress to add a new email address.\r\n- Email addresses are stored in ~\/.mutt\/address by default. You can configure this by setting g:complete_email_file.\r\n\r\n\r\nFile format\r\n---------------------\r\nThere are 3 fields in the address file. name, email address, and extra info. The extra info is shown preview window. These fields are separated by the 0x1e character. Type x1e to insert it.\r\n\r\n\r\nOther scripts\r\n--------------------\r\n- mail.tgz: http:\/\/www.vim.org\/scripts\/script.php?script_id=99 - calls external utility (abook).\r\n","4":"- Homepage: http:\/\/code.arp242.net\/complete_email.vim\r\n\r\n----------------------------------------------------------------------\r\n\r\nAllow completion of email addresses so you can use Vim as a basic \"address book\".\r\n\r\nThis is useful when you use Vim to compose emails in a program such as mutt. I have the following settings in my muttrc:\r\n\r\n\tset edit_headers = yes          # Edit the headers of your outgoing messages\r\n\tset autoedit = yes              # Go directly to editor after pressing m\r\n\r\nAfter pressing m I immediately go to Vim, and can fill out the headers myself:\r\n\r\n\tFrom: Martin Tournoij \r\n\tTo: \r\n\tCc: \r\n\tBcc: \r\n\tSubject: \r\n\tReply-To: \r\n\r\nI can then use this plugin to quickly fill in the To:, Cc:, etc. fields.\r\n\r\n\r\nBasic usage\r\n-----------------------\r\n- Use  to complete.\r\n- Use :AddEmailAddress to add a new email address.\r\n- Email addresses are stored in ~\/.mutt\/address by default. You can configure this by setting g:complete_email_file.\r\n\r\n\r\nFile format\r\n---------------------\r\nThere are 3 fields in the address file. name, email address, and extra info. The extra info is shown preview window. These fields are separated by the 0x1e character. Type x1e to insert it.\r\n\r\n\r\nOther scripts\r\n--------------------\r\n- mail.tgz: http:\/\/www.vim.org\/scripts\/script.php?script_id=99 - calls external utility (abook).\r\n","install_details":"","5":"","first_name":"Martin","6":"Martin","last_name":"Tournoij","7":"Tournoij","releases":[{"0":"5208","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Download from homepage","3":"Download from homepage","package":"download-from-homepage.tar.gz","4":"download-from-homepage.tar.gz","src_id":"24689","5":"24689","creation_date":"1477882725","6":"1477882725"}]},"5207":{"script_id":"5207","0":"5207","script_name":"undofile_warn.vim","1":"undofile_warn.vim","script_type":"utility","2":"utility","summary":"Warn when using the undofile.","3":"Warn when using the undofile.","description":"Homepage: http:\/\/arp242.net\/code\/undofile_warn.vim\r\n\r\n-----------------------------------------\r\n\r\nIntroduction\r\n============\r\nThe 'undofile' is a great feature, and I use it a lot. However, one annoyance\r\nis that it's very easy to accidentally undo changes that I did the last time I\r\nopened the file; which may be 2 minutes ago, an hour ago, last week, or a\r\nyear ago.\r\nSo what would happen is that sometimes I would accidentally undo changes from\r\nages ago.\r\n\r\nThis plugin fixes that by showing a warning.\r\n\r\nI originally posted this as an answer on vi StackExchange, which also has some\r\nother solutions to the same problem:\r\nhttp:\/\/vi.stackexchange.com\/q\/2115\/51\r\n\r\n\r\nMappings\r\n========\r\nThis plugin overwrites the `u` and `CTRL-R` mappings:\r\n\r\n    nmap u     (undofile-warn-undo)\r\n    nmap  (undofile-warn-redo)\r\n\r\nYou can prevent this by setting `g:undofile_warn_no_map` to 1.\r\n\r\nOptions\r\n=======\r\ng:undofile_warn_mode (Boolean, default: 1)\r\n\r\n0 Show a warning for a second but don't actually change behaviour.\r\n1 Show a warning and do nothing on the first u press, confirm with pressing u again.\r\n2 Ask for explicit confirmation","4":"Homepage: http:\/\/arp242.net\/code\/undofile_warn.vim\r\n\r\n-----------------------------------------\r\n\r\nIntroduction\r\n============\r\nThe 'undofile' is a great feature, and I use it a lot. However, one annoyance\r\nis that it's very easy to accidentally undo changes that I did the last time I\r\nopened the file; which may be 2 minutes ago, an hour ago, last week, or a\r\nyear ago.\r\nSo what would happen is that sometimes I would accidentally undo changes from\r\nages ago.\r\n\r\nThis plugin fixes that by showing a warning.\r\n\r\nI originally posted this as an answer on vi StackExchange, which also has some\r\nother solutions to the same problem:\r\nhttp:\/\/vi.stackexchange.com\/q\/2115\/51\r\n\r\n\r\nMappings\r\n========\r\nThis plugin overwrites the `u` and `CTRL-R` mappings:\r\n\r\n    nmap u     (undofile-warn-undo)\r\n    nmap  (undofile-warn-redo)\r\n\r\nYou can prevent this by setting `g:undofile_warn_no_map` to 1.\r\n\r\nOptions\r\n=======\r\ng:undofile_warn_mode (Boolean, default: 1)\r\n\r\n0 Show a warning for a second but don't actually change behaviour.\r\n1 Show a warning and do nothing on the first u press, confirm with pressing u again.\r\n2 Ask for explicit confirmation","install_details":"","5":"","first_name":"Martin","6":"Martin","last_name":"Tournoij","7":"Tournoij","releases":[{"0":"5207","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Download from homepage.","3":"Download from homepage.","package":"download-from-homepage.tar.gz","4":"download-from-homepage.tar.gz","src_id":"24681","5":"24681","creation_date":"1477798447","6":"1477798447"}]},"5206":{"script_id":"5206","0":"5206","script_name":"auto_autoread.vim","1":"auto_autoread.vim","script_type":"utility","2":"utility","summary":"Automatically read files when they've changed. Does what 'autoread' promises.","3":"Automatically read files when they've changed. Does what 'autoread' promises.","description":"- Homepage: (http:\/\/www.vim.org\/scripts\/script.php?script_id=5206\r\n\r\n-----------------------------------------------------------------------------\r\n\r\nAutomatically read files when they've changed, This does what 'autoread' promises to do but doesn't do. This plugin requires `+python` or `+python3`.\r\n\r\nThe `'autoread'` setting _only_ checks if the file is changed when certain events happen (buffer is entered, focus changed, etc.). If you're not triggering those events, the buffer won't be updated. To be more precise, this is when:\r\n\r\n    - `:checktime` is used;\r\n    - a buffer is entered;\r\n    - `:diffupdate` is used;\r\n    - `:e` is issued for a file that already has a buffer;\r\n    - executing an external command with `!`;\r\n    - returning to the foreground (^Z, fg, only if the shell has job control).\r\n\r\nAnd for gVim, this is also done when:\r\n\r\n    - closing the \"right-click\" menu (either by selecting something, or just\r\n      by closing it);\r\n    - focus is changed (this is what you already noticed);\r\n    - closing the file browsers dialog that pops up if you use \"file -> open\",\r\n      \"file -> save as\" from the menu (as well as some other places).\r\n\r\nAs you can see, this set is very limited. If you're running Vim in another window while you're doing something else somewhere else, the buffer never gets updated.\r\n\r\nThere are some other scripts\/tips which promise to fix this, but all of those that I tried simply extend the list of events with `CursorMoved`, `CursorHold`, etc.\r\n\r\nThis plugin will periodically check if the file on the disk has changed with `:checktime`, It will do this even if you're not interacting with Vim at all.\r\n\r\n\r\n","4":"- Homepage: (http:\/\/www.vim.org\/scripts\/script.php?script_id=5206\r\n\r\n-----------------------------------------------------------------------------\r\n\r\nAutomatically read files when they've changed, This does what 'autoread' promises to do but doesn't do. This plugin requires `+python` or `+python3`.\r\n\r\nThe `'autoread'` setting _only_ checks if the file is changed when certain events happen (buffer is entered, focus changed, etc.). If you're not triggering those events, the buffer won't be updated. To be more precise, this is when:\r\n\r\n    - `:checktime` is used;\r\n    - a buffer is entered;\r\n    - `:diffupdate` is used;\r\n    - `:e` is issued for a file that already has a buffer;\r\n    - executing an external command with `!`;\r\n    - returning to the foreground (^Z, fg, only if the shell has job control).\r\n\r\nAnd for gVim, this is also done when:\r\n\r\n    - closing the \"right-click\" menu (either by selecting something, or just\r\n      by closing it);\r\n    - focus is changed (this is what you already noticed);\r\n    - closing the file browsers dialog that pops up if you use \"file -> open\",\r\n      \"file -> save as\" from the menu (as well as some other places).\r\n\r\nAs you can see, this set is very limited. If you're running Vim in another window while you're doing something else somewhere else, the buffer never gets updated.\r\n\r\nThere are some other scripts\/tips which promise to fix this, but all of those that I tried simply extend the list of events with `CursorMoved`, `CursorHold`, etc.\r\n\r\nThis plugin will periodically check if the file on the disk has changed with `:checktime`, It will do this even if you're not interacting with Vim at all.\r\n\r\n\r\n","install_details":"","5":"","first_name":"Martin","6":"Martin","last_name":"Tournoij","7":"Tournoij","releases":[{"0":"5206","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Download from homepage.","3":"Download from homepage.","package":"download-from-homepage.tar.gz","4":"download-from-homepage.tar.gz","src_id":"24682","5":"24682","creation_date":"1477798500","6":"1477798500"}]},"5205":{"script_id":"5205","0":"5205","script_name":"ShaderHighLight","1":"ShaderHighLight","script_type":"syntax","2":"syntax","summary":"常用的shader文件语法高亮","3":"常用的shader文件语法高亮","description":"功能描述:\r\n1.整合了目前常用的shader文件格式的语法高亮\r\n2.支持格式：glsl，hlsl，cg，shaderlab（unity的shader格式）\r\n3.这个插件是对一些已有的vim高亮插件进行整合，这些插件有 \r\nhttps:\/\/github.com\/tikhomirov\/vim-glsl \r\nhttps:\/\/github.com\/beyondmarc\/hlsl.vim \r\nhttps:\/\/github.com\/vim-scripts\/cg.vim\r\n插件git地址:\r\nhttp:\/\/git.oschina.net\/qiuchangjie\/ShaderHighLight","4":"功能描述:\r\n1.整合了目前常用的shader文件格式的语法高亮\r\n2.支持格式：glsl，hlsl，cg，shaderlab（unity的shader格式）\r\n3.这个插件是对一些已有的vim高亮插件进行整合，这些插件有 \r\nhttps:\/\/github.com\/tikhomirov\/vim-glsl \r\nhttps:\/\/github.com\/beyondmarc\/hlsl.vim \r\nhttps:\/\/github.com\/vim-scripts\/cg.vim\r\n插件git地址:\r\nhttp:\/\/git.oschina.net\/qiuchangjie\/ShaderHighLight","install_details":"解压ShaderHighLight.zip文件，分别把plugin和syntax中的文件拷贝到vim相应的目录中","5":"解压ShaderHighLight.zip文件，分别把plugin和syntax中的文件拷贝到vim相应的目录中","first_name":"ChangJie","6":"ChangJie","last_name":"Qiu","7":"Qiu","releases":[{"0":"5205","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"ShaderHighLight.zip","4":"ShaderHighLight.zip","src_id":"23416","5":"23416","creation_date":"1435429551","6":"1435429551"}]},"5204":{"script_id":"5204","0":"5204","script_name":"mirror.vim","1":"mirror.vim","script_type":"utility","2":"utility","summary":"Efficient way to edit remote files on multiple environments","3":"Efficient way to edit remote files on multiple environments","description":"GitHub: https:\/\/github.com\/zenbro\/mirror.vim\r\nLive demo: https:\/\/asciinema.org\/a\/22407\r\n\r\nIf some of your projects have multiple environments (e.g. development, staging, production - with nearly the same directory and files structure), then there is a situations when you need to connect to one of this environments via ssh and remotely edit project-related files. Usually you will do something like this:\r\n\r\nssh user@host\r\ncd path\/to\/you\/project\r\nvim \/some\/file\r\nand so on...\r\n\r\nThis plugin was created to simplify this process by maintaining special configuration file and adding different commands for quickly doing remote actions for each environment of project you working with.","4":"GitHub: https:\/\/github.com\/zenbro\/mirror.vim\r\nLive demo: https:\/\/asciinema.org\/a\/22407\r\n\r\nIf some of your projects have multiple environments (e.g. development, staging, production - with nearly the same directory and files structure), then there is a situations when you need to connect to one of this environments via ssh and remotely edit project-related files. Usually you will do something like this:\r\n\r\nssh user@host\r\ncd path\/to\/you\/project\r\nvim \/some\/file\r\nand so on...\r\n\r\nThis plugin was created to simplify this process by maintaining special configuration file and adding different commands for quickly doing remote actions for each environment of project you working with.","install_details":"Extract the zip file to ~\/.vim. To use the help, see :help add-local-help. To regenerate helptags run :helptags ~\/.vim\/doc.\r\n\r\nAdd this lines to .vimrc (probably they already there):\r\nset nocompatible  \" disable backward compatibility with Vi\r\nfiletype plugin on  \" plugins are enabled\r\n\r\nFor more details, see :help mirror ","5":"Extract the zip file to ~\/.vim. To use the help, see :help add-local-help. To regenerate helptags run :helptags ~\/.vim\/doc.\r\n\r\nAdd this lines to .vimrc (probably they already there):\r\nset nocompatible  \" disable backward compatibility with Vi\r\nfiletype plugin on  \" plugins are enabled\r\n\r\nFor more details, see :help mirror ","first_name":"Alexander","6":"Alexander","last_name":"Capybarov","7":"Capybarov","releases":[{"0":"5204","vim_version":"7.3","1":"7.3","script_version":"1.3.0","2":"1.3.0","version_comment":"* Wildcard support in mirrors config\r\n* Add :MirrorConfigReload command","3":"* Wildcard support in mirrors config\r\n* Add :MirrorConfigReload command","package":"mirror.zip","4":"mirror.zip","src_id":"24254","5":"24254","creation_date":"1463558473","6":"1463558473"},{"0":"5204","vim_version":"7.3","1":"7.3","script_version":"1.2.0","2":"1.2.0","version_comment":"* Add support for nvim job control for MirrorPush and MirrorPull command","3":"* Add support for nvim job control for MirrorPush and MirrorPull command","package":"mirror.zip","4":"mirror.zip","src_id":"24216","5":"24216","creation_date":"1462005209","6":"1462005209"},{"0":"5204","vim_version":"7.3","1":"7.3","script_version":"1.1.1","2":"1.1.1","version_comment":"* Add support for nvim-terminal for MirrorSSH\r\n* Improve regexp for remote path parsing\r\n* Fix diff behavior for multiple splits","3":"* Add support for nvim-terminal for MirrorSSH\r\n* Improve regexp for remote path parsing\r\n* Fix diff behavior for multiple splits","package":"mirror.zip","4":"mirror.zip","src_id":"23569","5":"23569","creation_date":"1441085644","6":"1441085644"},{"0":"5204","vim_version":"7.3","1":"7.3","script_version":"1.1.0","2":"1.1.0","version_comment":"* Auto change directory after establishing SSH connection","3":"* Auto change directory after establishing SSH connection","package":"mirror.zip","4":"mirror.zip","src_id":"23451","5":"23451","creation_date":"1436337224","6":"1436337224"},{"0":"5204","vim_version":"7.3","1":"7.3","script_version":"1.0.2","2":"1.0.2","version_comment":"* Use silent mode for netrw\r\n* Improve environments autocomplete\r\n* Perform project discovery for each buffer after saving config\r\n* Quick way to close configuration file - q\r\n* Fix typos in readme and documentation","3":"* Use silent mode for netrw\r\n* Improve environments autocomplete\r\n* Perform project discovery for each buffer after saving config\r\n* Quick way to close configuration file - q\r\n* Fix typos in readme and documentation","package":"mirror.zip","4":"mirror.zip","src_id":"23415","5":"23415","creation_date":"1435423075","6":"1435423075"},{"0":"5204","vim_version":"7.3","1":"7.3","script_version":"1.0.1","2":"1.0.1","version_comment":"* Fix project discovery algorithm","3":"* Fix project discovery algorithm","package":"mirror.zip","4":"mirror.zip","src_id":"23414","5":"23414","creation_date":"1435212347","6":"1435212347"},{"0":"5204","vim_version":"7.3","1":"7.3","script_version":"1.0.0","2":"1.0.0","version_comment":"Initial upload","3":"Initial upload","package":"mirror.zip","4":"mirror.zip","src_id":"23413","5":"23413","creation_date":"1435177537","6":"1435177537"}]},"5203":{"script_id":"5203","0":"5203","script_name":"asynccompl","1":"asynccompl","script_type":"utility","2":"utility","summary":"A simple asynchronous complete plugin","3":"A simple asynchronous complete plugin","description":"A simple asynchronous complete plugin, it will run simply and silently in background :)\r\n\r\nDepends:\r\n - vim 7.3.196 or later\r\n - +python feature\r\n - +clientserver feature (optional)\r\n\r\n * asynccompl only supports ASCII completion of the current buffer currently\r\n\r\nOptions:\r\n * g:asynccompl_autostart_filetype  default: ['all']\r\n    asynccompl will autostart in these filetype, and the 'all' means always start\r\n\r\n * g:asynccompl_autostop_filetype   default: []\r\n    asynccompl will stop in these filetype\r\n\r\nSuggestions:\r\n - If you wish always start asynccompl, just not need to configure.\r\n\r\n - If you wish just start asynccompl in c, cpp filetype, just add the follow to your .vimrc\r\n    let g:asynccompl_autostart_filetype = ['c', 'cpp']\r\n\r\n - If you wish just stop asynccompl in c, cpp filetype, just add the follow to your .vimrc\r\n    let g:asynccompl_autostop_filetype = ['c', 'cpp']","4":"A simple asynchronous complete plugin, it will run simply and silently in background :)\r\n\r\nDepends:\r\n - vim 7.3.196 or later\r\n - +python feature\r\n - +clientserver feature (optional)\r\n\r\n * asynccompl only supports ASCII completion of the current buffer currently\r\n\r\nOptions:\r\n * g:asynccompl_autostart_filetype  default: ['all']\r\n    asynccompl will autostart in these filetype, and the 'all' means always start\r\n\r\n * g:asynccompl_autostop_filetype   default: []\r\n    asynccompl will stop in these filetype\r\n\r\nSuggestions:\r\n - If you wish always start asynccompl, just not need to configure.\r\n\r\n - If you wish just start asynccompl in c, cpp filetype, just add the follow to your .vimrc\r\n    let g:asynccompl_autostart_filetype = ['c', 'cpp']\r\n\r\n - If you wish just stop asynccompl in c, cpp filetype, just add the follow to your .vimrc\r\n    let g:asynccompl_autostop_filetype = ['c', 'cpp']","install_details":"extract and put all folders and files of asynccompl folder into ~\/.vim\r\n","5":"extract and put all folders and files of asynccompl folder into ~\/.vim\r\n","first_name":"fanhe","6":"fanhe","last_name":" ","7":" ","releases":[{"0":"5203","vim_version":"7.3","1":"7.3","script_version":"0.110","2":"0.110","version_comment":"o Fix :bd and reopen issue","3":"o Fix :bd and reopen issue","package":"asynccompl-0.110-build20151101.tar.bz2","4":"asynccompl-0.110-build20151101.tar.bz2","src_id":"23696","5":"23696","creation_date":"1446354092","6":"1446354092"},{"0":"5203","vim_version":"7.3","1":"7.3","script_version":"0.100","2":"0.100","version_comment":"Initial upload","3":"Initial upload","package":"asynccompl-0.100-build20150621.tar.bz2","4":"asynccompl-0.100-build20150621.tar.bz2","src_id":"23407","5":"23407","creation_date":"1434861738","6":"1434861738"}]},"5202":{"script_id":"5202","0":"5202","script_name":"supersearch","1":"supersearch","script_type":"ftplugin","2":"ftplugin","summary":"source view plugin","3":"source view plugin","description":"The \"Super Search\" plugin is a source code browser plugin for Vim and provides an overview of the structure of the programming language files and allows you to efficiently browse through source code files for different programming languages.  You can visit the supersearch plugin home page for more information:\r\n  https:\/\/github.com\/hellotomcat\/supersearch\r\n这个项目是用来加速vim开发效率的\r\n1.由于历史原因我们的项目目录中有许多无关的目录包含着无关的代码，导致生成的tags文件往往没有实际用途\r\n2.当我们需要查看谁调用谁的问题时，要用:grep命令来搜索整个项目目录，相当不方便\r\n现在好了：\r\n有了supersearch插件，只要配置好与自己有关和目录，生成tags的事再也不用担心了（会自动生成tags文件），还能根据配置的目录进行全文搜索\r\n\r\n跳转继续使用传统的ctrl+] 全文搜索目前定义为,s 在命令模式中,s直接搜索当前单词 在视图模式中先选择要搜索的文本，再按,s\r\n","4":"The \"Super Search\" plugin is a source code browser plugin for Vim and provides an overview of the structure of the programming language files and allows you to efficiently browse through source code files for different programming languages.  You can visit the supersearch plugin home page for more information:\r\n  https:\/\/github.com\/hellotomcat\/supersearch\r\n这个项目是用来加速vim开发效率的\r\n1.由于历史原因我们的项目目录中有许多无关的目录包含着无关的代码，导致生成的tags文件往往没有实际用途\r\n2.当我们需要查看谁调用谁的问题时，要用:grep命令来搜索整个项目目录，相当不方便\r\n现在好了：\r\n有了supersearch插件，只要配置好与自己有关和目录，生成tags的事再也不用担心了（会自动生成tags文件），还能根据配置的目录进行全文搜索\r\n\r\n跳转继续使用传统的ctrl+] 全文搜索目前定义为,s 在命令模式中,s直接搜索当前单词 在视图模式中先选择要搜索的文本，再按,s\r\n","install_details":"1.Download the supersearch.zip file and unzip the files to the $HOME\/.vim\/plugin\/ The directory structure should be preserved: $HOME\/.vim\/plugin\/supersearch.vim\r\n2.Create a profile in the top-level directory of the project (\"project.conf\")\r\n3.finished\r\n\r\n直接把这个supersearch.vim放到.vim\/plugin\/目录中就可以了\r\n\r\nExample\r\nProject directory structure:\r\n\r\nsrc\r\n    --http\r\n    --core\r\n    --event\r\n    --mail\r\n    --misc\r\n    --os\r\n\r\nThe configuration file (project.conf):\r\n\r\n\/http\r\n\/core\r\n\/event\r\n\/mail\r\n\/misc\r\n\/os\r\n\r\n最后： 在插件文件的尾部定义了搜索快捷键，你可以自己修改为你喜欢的\r\n","5":"1.Download the supersearch.zip file and unzip the files to the $HOME\/.vim\/plugin\/ The directory structure should be preserved: $HOME\/.vim\/plugin\/supersearch.vim\r\n2.Create a profile in the top-level directory of the project (\"project.conf\")\r\n3.finished\r\n\r\n直接把这个supersearch.vim放到.vim\/plugin\/目录中就可以了\r\n\r\nExample\r\nProject directory structure:\r\n\r\nsrc\r\n    --http\r\n    --core\r\n    --event\r\n    --mail\r\n    --misc\r\n    --os\r\n\r\nThe configuration file (project.conf):\r\n\r\n\/http\r\n\/core\r\n\/event\r\n\/mail\r\n\/misc\r\n\/os\r\n\r\n最后： 在插件文件的尾部定义了搜索快捷键，你可以自己修改为你喜欢的\r\n","first_name":"tian","6":"tian","last_name":"guangyu","7":"guangyu","releases":[{"0":"5202","vim_version":"7.0","1":"7.0","script_version":"1.6","2":"1.6","version_comment":"1.修改检测tags方式.\r\n2.默认在未配置格式化方式时，调用gg=G来格式化当前文件.","3":"1.修改检测tags方式.\r\n2.默认在未配置格式化方式时，调用gg=G来格式化当前文件.","package":"supersearch.zip","4":"supersearch.zip","src_id":"24508","5":"24508","creation_date":"1473232787","6":"1473232787"},{"0":"5202","vim_version":"7.0","1":"7.0","script_version":"1.2","2":"1.2","version_comment":"1.修复当前目录只有一个文件时搜索后无法跳转问题\r\n2.修复生成tags文件错乱问题\r\n3.搜索时过滤掉.swp文件","3":"1.修复当前目录只有一个文件时搜索后无法跳转问题\r\n2.修复生成tags文件错乱问题\r\n3.搜索时过滤掉.swp文件","package":"supersearch.zip","4":"supersearch.zip","src_id":"23401","5":"23401","creation_date":"1434617028","6":"1434617028"},{"0":"5202","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"supersearch.zip","4":"supersearch.zip","src_id":"23398","5":"23398","creation_date":"1434530031","6":"1434530031"}]},"5201":{"script_id":"5201","0":"5201","script_name":"scilab.vim","1":"scilab.vim","script_type":"syntax","2":"syntax","summary":"Scilab syntax highlighting (Linux)","3":"Scilab syntax highlighting (Linux)","description":"Scilab syntax highlighting file with 3981 keywords in five categories (3877 from Scilab 5.5.2 and 104 from Scilab 5.5.1).\r\nUpdated to Scilab 5.5.2 with the toolboxes: FACT, GUI Builder, IPT3, JSON, NaN, Quapro and dependencies.\r\nUnix compatible, tested on Mint 19.1.","4":"Scilab syntax highlighting file with 3981 keywords in five categories (3877 from Scilab 5.5.2 and 104 from Scilab 5.5.1).\r\nUpdated to Scilab 5.5.2 with the toolboxes: FACT, GUI Builder, IPT3, JSON, NaN, Quapro and dependencies.\r\nUnix compatible, tested on Mint 19.1.","install_details":"","5":"","first_name":"A.","6":"A.","last_name":"Astonfe","7":"Astonfe","releases":[{"0":"5201","vim_version":"7.0","1":"7.0","script_version":"2.3","2":"2.3","version_comment":"colorscheme default","3":"colorscheme default","package":"scilab.vim","4":"scilab.vim","src_id":"26448","5":"26448","creation_date":"1554408742","6":"1554408742"}]},"5200":{"script_id":"5200","0":"5200","script_name":"vim-js-arrow-function","1":"vim-js-arrow-function","script_type":"ftplugin","2":"ftplugin","summary":"changes a JavaScript anonymous function to an arrow function expression (ES2015)","3":"changes a JavaScript anonymous function to an arrow function expression (ES2015)","description":"This plugin converts JavaScript anonymous functions to arrow function expressions (introduced in ES 2015).\r\n\r\nPlace the cursor anywhere inside the function, even on the \"function\" keyword, and run the JsAnonFnToArrowFn command.\r\n\r\nThis command is mapped to af unless that is already mapped to something else.","4":"This plugin converts JavaScript anonymous functions to arrow function expressions (introduced in ES 2015).\r\n\r\nPlace the cursor anywhere inside the function, even on the \"function\" keyword, and run the JsAnonFnToArrowFn command.\r\n\r\nThis command is mapped to af unless that is already mapped to something else.","install_details":"The easiest way to install this is to use Pathogen and \"git clone\" this repository into the .vim\/bundle directory.\r\nAlternatively, you can copy ftplugin\/javascript.vim to your ~\/.vim\/ftplugin directory, but be sure you are not overwriting an existing file.","5":"The easiest way to install this is to use Pathogen and \"git clone\" this repository into the .vim\/bundle directory.\r\nAlternatively, you can copy ftplugin\/javascript.vim to your ~\/.vim\/ftplugin directory, but be sure you are not overwriting an existing file.","first_name":"Mark","6":"Mark","last_name":"Volkmann","7":"Volkmann","releases":[{"0":"5200","vim_version":"7.0","1":"7.0","script_version":"1.2","2":"1.2","version_comment":"This version avoids remapping a key if it is already mapped.","3":"This version avoids remapping a key if it is already mapped.","package":"vim-js-arrow-function.zip","4":"vim-js-arrow-function.zip","src_id":"23402","5":"23402","creation_date":"1434662203","6":"1434662203"},{"0":"5200","vim_version":"7.0","1":"7.0","script_version":"1.1","2":"1.1","version_comment":"This version adds the ability to remove the \"return\" keyword and braces for anonymous functions that immediately return a value.\r\nThis:\r\nfunction (n) { return n * 2; }\r\nis changed to this:\r\nn => n * 2","3":"This version adds the ability to remove the \"return\" keyword and braces for anonymous functions that immediately return a value.\r\nThis:\r\nfunction (n) { return n * 2; }\r\nis changed to this:\r\nn => n * 2","package":"vim-js-arrow-function.zip","4":"vim-js-arrow-function.zip","src_id":"23390","5":"23390","creation_date":"1434398244","6":"1434398244"},{"0":"5200","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"vim-js-arrow-function.zip","4":"vim-js-arrow-function.zip","src_id":"23388","5":"23388","creation_date":"1434331170","6":"1434331170"}]},"5199":{"script_id":"5199","0":"5199","script_name":"flagship.vim","1":"flagship.vim","script_type":"utility","2":"utility","summary":"Configurable and extensible tab line and status line","3":"Configurable and extensible tab line and status line","description":"Flagship provides a Vim status line and tab line that are both easily\r\ncustomizable by the user and extensible by other plugins.\r\n\r\n## Extension\r\n\r\nAdding a flag from a plugin is a simple matter of calling `Hoist()` with a\r\nscope and function name from a `User Flags` autocommand.  Here's an example\r\nfrom [fugitive.vim](https:\/\/github.com\/tpope\/vim-fugitive):\r\n\r\n    autocmd User Flags call Hoist(\"buffer\", \"fugitive#statusline\")\r\n\r\nYou can also do this in your vimrc, for example if a plugin provides a\r\nstatusline flag function but does not natively integrate with Flagship.  If\r\nthe function isn't defined (e.g., you temporarily disable or permanently\r\nremove the plugin), it will be skipped.  Here's a couple of mine:\r\n\r\n    autocmd User Flags call Hoist(\"window\", \"SyntasticStatuslineFlag\")\r\n    autocmd User Flags call Hoist(\"global\", \"%{&ignorecase ? '[IC]' : ''}\")\r\n\r\n## Customization\r\n\r\nThe extension API is great for adding flags, but what if you want to change\r\nthe core content?  For the status line, Vim already provides a perfectly\r\nadequate `'statusline'` option, and Flagship will use it in constructing its\r\nown.  Customizing your status line is exactly the same with and without\r\nFlagship.\r\n\r\nThe tab line is another story.  The usual technique (see\r\n`:help setting-tabline`) involves creating a function that cycles through each\r\ntab and assembles a giant format string.  Furthermore, while you can use the\r\nsame status line \"%\" items, they're expanded in the context of the active\r\nwindow only, rendering most of them worthless for any tab but the current.\r\nRather than embrace this abomination, Flagship hides it, instead exposing\r\na `g:tablabel` option which can be assigned to customize the format of a\r\nsingle tab.  Additionally, you can set `g:tabprefix` to define content to be\r\ninserted before the first tab (assuming you disabled the GUI tab line as\r\ninstructed above).\r\n\r\nThe default tab label is nearly impossible to precisely reconstruct, and I\r\nnever really found it useful, so I've taken it a different direction.  Here's\r\nhow it would look if you set `g:tablabel` yourself, using a few of the many\r\nhelpers available:\r\n\r\n    let g:tablabel =\r\n          \\ \"%N%{flagship#tabmodified()} %{flagship#tabcwds('shorten',',')}\"\r\n\r\nHere's a breakdown of what's included:\r\n\r\n* The tab number, so you never have to hesitate on `gt` invocation.\r\n* One `+` per modified window.  Vim's default shows the status of the tab's\r\n  current window only, which can be misleading.\r\n* A compact representation of the working directories of each window.  For\r\n  determining what project a tab is on, I find this far more useful than the\r\n  filename.\r\n\r\nAdditionally, I've chosen to prefix the tab line with the Vim GUI server name\r\n(see `:help v:servername`) if available, or the current host name if SSHed.\r\nThis only takes a few characters, and I find it to be greatly helpful in\r\nreducing confusion when running multiple instances of Vim.  (Assign\r\n`g:tabprefix` if you don't like it.)","4":"Flagship provides a Vim status line and tab line that are both easily\r\ncustomizable by the user and extensible by other plugins.\r\n\r\n## Extension\r\n\r\nAdding a flag from a plugin is a simple matter of calling `Hoist()` with a\r\nscope and function name from a `User Flags` autocommand.  Here's an example\r\nfrom [fugitive.vim](https:\/\/github.com\/tpope\/vim-fugitive):\r\n\r\n    autocmd User Flags call Hoist(\"buffer\", \"fugitive#statusline\")\r\n\r\nYou can also do this in your vimrc, for example if a plugin provides a\r\nstatusline flag function but does not natively integrate with Flagship.  If\r\nthe function isn't defined (e.g., you temporarily disable or permanently\r\nremove the plugin), it will be skipped.  Here's a couple of mine:\r\n\r\n    autocmd User Flags call Hoist(\"window\", \"SyntasticStatuslineFlag\")\r\n    autocmd User Flags call Hoist(\"global\", \"%{&ignorecase ? '[IC]' : ''}\")\r\n\r\n## Customization\r\n\r\nThe extension API is great for adding flags, but what if you want to change\r\nthe core content?  For the status line, Vim already provides a perfectly\r\nadequate `'statusline'` option, and Flagship will use it in constructing its\r\nown.  Customizing your status line is exactly the same with and without\r\nFlagship.\r\n\r\nThe tab line is another story.  The usual technique (see\r\n`:help setting-tabline`) involves creating a function that cycles through each\r\ntab and assembles a giant format string.  Furthermore, while you can use the\r\nsame status line \"%\" items, they're expanded in the context of the active\r\nwindow only, rendering most of them worthless for any tab but the current.\r\nRather than embrace this abomination, Flagship hides it, instead exposing\r\na `g:tablabel` option which can be assigned to customize the format of a\r\nsingle tab.  Additionally, you can set `g:tabprefix` to define content to be\r\ninserted before the first tab (assuming you disabled the GUI tab line as\r\ninstructed above).\r\n\r\nThe default tab label is nearly impossible to precisely reconstruct, and I\r\nnever really found it useful, so I've taken it a different direction.  Here's\r\nhow it would look if you set `g:tablabel` yourself, using a few of the many\r\nhelpers available:\r\n\r\n    let g:tablabel =\r\n          \\ \"%N%{flagship#tabmodified()} %{flagship#tabcwds('shorten',',')}\"\r\n\r\nHere's a breakdown of what's included:\r\n\r\n* The tab number, so you never have to hesitate on `gt` invocation.\r\n* One `+` per modified window.  Vim's default shows the status of the tab's\r\n  current window only, which can be misleading.\r\n* A compact representation of the working directories of each window.  For\r\n  determining what project a tab is on, I find this far more useful than the\r\n  filename.\r\n\r\nAdditionally, I've chosen to prefix the tab line with the Vim GUI server name\r\n(see `:help v:servername`) if available, or the current host name if SSHed.\r\nThis only takes a few characters, and I find it to be greatly helpful in\r\nreducing confusion when running multiple instances of Vim.  (Assign\r\n`g:tabprefix` if you don't like it.)","install_details":"Extract in ~\/.vim (~\\vimfiles on Windows).\r\n\r\nWhile not strictly required, I highly recommend the following options:\r\n\r\n    set laststatus=2\r\n    set showtabline=2\r\n    set guioptions-=e\r\n\r\nThe first two force the status line and tab line to always display, and the\r\nthird disables the GUI tab line in favor of the plain text version, enabling\r\nglobal flags and the tab prefix explained below.","5":"Extract in ~\/.vim (~\\vimfiles on Windows).\r\n\r\nWhile not strictly required, I highly recommend the following options:\r\n\r\n    set laststatus=2\r\n    set showtabline=2\r\n    set guioptions-=e\r\n\r\nThe first two force the status line and tab line to always display, and the\r\nthird disables the GUI tab line in favor of the plain text version, enabling\r\nglobal flags and the tab prefix explained below.","first_name":"Tim","6":"Tim","last_name":"Pope","7":"Pope","releases":[{"0":"5199","vim_version":"7.0","1":"7.0","script_version":"1.1","2":"1.1","version_comment":"Fix duplicate flag filtering.\r\nDon't override showtabline if explicitly set.","3":"Fix duplicate flag filtering.\r\nDon't override showtabline if explicitly set.","package":"flagship.zip","4":"flagship.zip","src_id":"23516","5":"23516","creation_date":"1439666554","6":"1439666554"},{"0":"5199","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"flagship.zip","4":"flagship.zip","src_id":"23387","5":"23387","creation_date":"1434326293","6":"1434326293"}]},"5198":{"script_id":"5198","0":"5198","script_name":"vim-aertre","1":"vim-aertre","script_type":"utility","2":"utility","summary":"Adds aertre","3":"Adds aertre","description":"Adds aertre support to VIM","4":"Adds aertre support to VIM","install_details":"","5":"","first_name":"Soroso","6":"Soroso","last_name":"J M","7":"J M","releases":[{"0":"5198","vim_version":"7.4","1":"7.4","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"phpfmt.vim","4":"phpfmt.vim","src_id":"23365","5":"23365","creation_date":"1433709293","6":"1433709293"}]},"5197":{"script_id":"5197","0":"5197","script_name":"Dokumentary","1":"Dokumentary","script_type":"utility","2":"utility","summary":"Improve what K does.","3":"Improve what K does.","description":"GitHub: https:\/\/github.com\/gastonsimone\/vim-dokumentary\r\n\r\nDokumentary improves what the K command does in Vim by customizing its behaviour, depending on the type of file you are editing.\r\n\r\nVim's standard K command for normal mode let's us easily run a program to lookup the keyword under the cursor. The program to run can be customized with the keywordprg (kp) option, whose default option is man.\r\n\r\nThis presents two problems:\r\n\r\n1. The man command is the right choice only if you are writing a shell script or C code.\r\n2. Vim only runs that command and waits for it to finish to continue using Vim, which sometimes is not the ideal, because you would like to see that documentation at the same time you are editing your file.\r\n\r\nDokumentary solves these two issues by doing the following:\r\n\r\n1. It creates buffer-specific mappings for K and Visual-K, depending on the type of file you are editing. See the supported file types below.\r\n2. It loads the retireved documentation in a vim window, so you can see the documentation together with your file and use all the Vim power to search and copy from it.\r\n3. The default command is not man, but a system-specific dictionary. So if you are just reading plain text, K will show the definition of the word under the cursor.","4":"GitHub: https:\/\/github.com\/gastonsimone\/vim-dokumentary\r\n\r\nDokumentary improves what the K command does in Vim by customizing its behaviour, depending on the type of file you are editing.\r\n\r\nVim's standard K command for normal mode let's us easily run a program to lookup the keyword under the cursor. The program to run can be customized with the keywordprg (kp) option, whose default option is man.\r\n\r\nThis presents two problems:\r\n\r\n1. The man command is the right choice only if you are writing a shell script or C code.\r\n2. Vim only runs that command and waits for it to finish to continue using Vim, which sometimes is not the ideal, because you would like to see that documentation at the same time you are editing your file.\r\n\r\nDokumentary solves these two issues by doing the following:\r\n\r\n1. It creates buffer-specific mappings for K and Visual-K, depending on the type of file you are editing. See the supported file types below.\r\n2. It loads the retireved documentation in a vim window, so you can see the documentation together with your file and use all the Vim power to search and copy from it.\r\n3. The default command is not man, but a system-specific dictionary. So if you are just reading plain text, K will show the definition of the word under the cursor.","install_details":"Vimball:\r\n\r\n1. Download the zip file from this page.\r\n2. Unzip it.\r\n3. vim dokumentary.vmb\r\n4. :so %\r\n5. :q\r\n\r\nPathogen:\r\n\r\ncd ~\/.vim\/bundle\r\ngit clone git:\/\/github.com\/gastonsimone\/vim-dokumentary.git\r\n\r\nOnce help tags have been generated, you can view the manual with :help dokumentary.\r\n\r\nVundle:\r\n\r\nJust add this line\r\n\r\nPlugin 'gastonsimone\/vim-dokumentary'\r\n\r\nto your .vimrc file, reload it and do the Vundle magic by running :PluginInstall.","5":"Vimball:\r\n\r\n1. Download the zip file from this page.\r\n2. Unzip it.\r\n3. vim dokumentary.vmb\r\n4. :so %\r\n5. :q\r\n\r\nPathogen:\r\n\r\ncd ~\/.vim\/bundle\r\ngit clone git:\/\/github.com\/gastonsimone\/vim-dokumentary.git\r\n\r\nOnce help tags have been generated, you can view the manual with :help dokumentary.\r\n\r\nVundle:\r\n\r\nJust add this line\r\n\r\nPlugin 'gastonsimone\/vim-dokumentary'\r\n\r\nto your .vimrc file, reload it and do the Vundle magic by running :PluginInstall.","first_name":"Gast\u00c3\u00b3n","6":"Gast\u00c3\u00b3n","last_name":"Simone","7":"Simone","releases":[{"0":"5197","vim_version":"7.0","1":"7.0","script_version":"1.2","2":"1.2","version_comment":"Improved customization capabilities. See :help dokumentary-config","3":"Improved customization capabilities. See :help dokumentary-config","package":"dokumentary.zip","4":"dokumentary.zip","src_id":"23408","5":"23408","creation_date":"1434914937","6":"1434914937"},{"0":"5197","vim_version":"7.0","1":"7.0","script_version":"1.1","2":"1.1","version_comment":"Added 'g:dokumentary_open' variable to be able to customize where to\r\nlocate the documentation window. Now by default the window is located on\r\nthe right.\r\n\r\nAdded the corresponding documentation.\r\n\r\nThanks wimstefan (https:\/\/github.com\/wimstefan) for the suggestion!","3":"Added 'g:dokumentary_open' variable to be able to customize where to\r\nlocate the documentation window. Now by default the window is located on\r\nthe right.\r\n\r\nAdded the corresponding documentation.\r\n\r\nThanks wimstefan (https:\/\/github.com\/wimstefan) for the suggestion!","package":"dokumentary.zip","4":"dokumentary.zip","src_id":"23366","5":"23366","creation_date":"1433709608","6":"1433709608"},{"0":"5197","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"dokumentary.zip","4":"dokumentary.zip","src_id":"23359","5":"23359","creation_date":"1433624936","6":"1433624936"}]},"5195":{"script_id":"5195","0":"5195","script_name":"Indent Detector","1":"Indent Detector","script_type":"utility","2":"utility","summary":"detect indent automatically","3":"detect indent automatically","description":"features[这里有中文说明](https:\/\/github.com\/luochen1990\/indent-detector.vim\/blob\/master\/README_cn.md)\r\n\r\n--------\r\n\r\n- detect mixed indent(indent with both spaces and tabs) and echo warnning on `bufEnter` and `bufWrite` automatically.\r\n- switch setting about indenting to fit the current indenting style automatically.\r\n- detecting time is limited, so you don't need to worry about opening huge files.\r\n\r\nnote\r\n----\r\n\r\n- the options decided by this plugin are `expandtab` `smarttab` `tabstop` `shiftwidth` `softtabstop`, and is setted via `setlocal`.\r\n- your own setting about indenting is also used as default when the indenting style is not decided. (when you create an empty file or enter a file which occurs no leading spaces or tabs)\r\n- this plugin will do nothing when you open an readonly file (`:echo &readonly` to check that), so that you can open help files without warnning.\r\n\r\n\r\nGo to [github](https:\/\/github.com\/luochen1990\/indent-detector.vim) for more details.","4":"features[这里有中文说明](https:\/\/github.com\/luochen1990\/indent-detector.vim\/blob\/master\/README_cn.md)\r\n\r\n--------\r\n\r\n- detect mixed indent(indent with both spaces and tabs) and echo warnning on `bufEnter` and `bufWrite` automatically.\r\n- switch setting about indenting to fit the current indenting style automatically.\r\n- detecting time is limited, so you don't need to worry about opening huge files.\r\n\r\nnote\r\n----\r\n\r\n- the options decided by this plugin are `expandtab` `smarttab` `tabstop` `shiftwidth` `softtabstop`, and is setted via `setlocal`.\r\n- your own setting about indenting is also used as default when the indenting style is not decided. (when you create an empty file or enter a file which occurs no leading spaces or tabs)\r\n- this plugin will do nothing when you open an readonly file (`:echo &readonly` to check that), so that you can open help files without warnning.\r\n\r\n\r\nGo to [github](https:\/\/github.com\/luochen1990\/indent-detector.vim) for more details.","install_details":"### via Vundle:\r\n\r\n```vim\r\nBundle 'luochen1990\/indent-detector.vim'\r\n```\r\n\r\n### manually\r\n\r\nput `indentdetector.vim` to directory `~\/.vim\/plugin` or `vimfiles\/plugin`\r\n\r\n>\tremenber to restart your vim after installation\r\n\r\n","5":"### via Vundle:\r\n\r\n```vim\r\nBundle 'luochen1990\/indent-detector.vim'\r\n```\r\n\r\n### manually\r\n\r\nput `indentdetector.vim` to directory `~\/.vim\/plugin` or `vimfiles\/plugin`\r\n\r\n>\tremenber to restart your vim after installation\r\n\r\n","first_name":"luo","6":"luo","last_name":"chen","7":"chen","releases":[{"0":"5195","vim_version":"7.3","1":"7.3","script_version":"0.0.2","2":"0.0.2","version_comment":"fillup: README_cn.md\r\nfix: still set options when 'too many spaces here.'\r\nfix: echom instead of echo to show warnning.\r\nnew: check on bufreadpost.","3":"fillup: README_cn.md\r\nfix: still set options when 'too many spaces here.'\r\nfix: echom instead of echo to show warnning.\r\nnew: check on bufreadpost.","package":"indentdetector.vim","4":"indentdetector.vim","src_id":"23355","5":"23355","creation_date":"1433491033","6":"1433491033"},{"0":"5195","vim_version":"7.3","1":"7.3","script_version":"0.0.1","2":"0.0.1","version_comment":"Initial upload","3":"Initial upload","package":"indentdetector.vim","4":"indentdetector.vim","src_id":"23354","5":"23354","creation_date":"1433482070","6":"1433482070"}]},"5194":{"script_id":"5194","0":"5194","script_name":"cpp_doxygen","1":"cpp_doxygen","script_type":"ftplugin","2":"ftplugin","summary":"Add Doxygen templates and fold Doxygen comments.","3":"Add Doxygen templates and fold Doxygen comments.","description":"This plugin lets you add a Doxygen comment template with a couple of key strokes. Just position your cursor on the first line of a file, namespace, class, struct, or function; then press d. The plugin will deduce what is being commented and insert a Doxygen comment above it, ready for you to fill in. The plugin can deduce template parameters, function parameters, and return types.\r\n\r\nThe plugin also provides a function you can use to generate fold text for a Javadoc or Qt style Doxygen comment. If you call this function from your own fold text function, Doxygen comments fold up to to the brief description inside comment tokens:\r\n    \/** This a brief description. *\/\r\nor\r\n    \/*! This is a brief description. *\/\r\n\r\nFor complete details, install the plugin and run :help cpp_doxygen.\r\n\r\nFor feature requests or bugs, please create an issue at https:\/\/github.com\/brobeson\/Tools\/.\r\n\r\nI've tested this with Vim 7.4 on Linux (Kubuntu 15.04). Other platforms and versions of Vim should work.","4":"This plugin lets you add a Doxygen comment template with a couple of key strokes. Just position your cursor on the first line of a file, namespace, class, struct, or function; then press d. The plugin will deduce what is being commented and insert a Doxygen comment above it, ready for you to fill in. The plugin can deduce template parameters, function parameters, and return types.\r\n\r\nThe plugin also provides a function you can use to generate fold text for a Javadoc or Qt style Doxygen comment. If you call this function from your own fold text function, Doxygen comments fold up to to the brief description inside comment tokens:\r\n    \/** This a brief description. *\/\r\nor\r\n    \/*! This is a brief description. *\/\r\n\r\nFor complete details, install the plugin and run :help cpp_doxygen.\r\n\r\nFor feature requests or bugs, please create an issue at https:\/\/github.com\/brobeson\/Tools\/.\r\n\r\nI've tested this with Vim 7.4 on Linux (Kubuntu 15.04). Other platforms and versions of Vim should work.","install_details":"Download the vimball and open it in Vim. Then run\r\n:source %\r\n:q","5":"Download the vimball and open it in Vim. Then run\r\n:source %\r\n:q","first_name":"Brendan","6":"Brendan","last_name":"","7":"","releases":[{"0":"5194","vim_version":"7.4","1":"7.4","script_version":"1.2","2":"1.2","version_comment":"With version 1.1, old configuration variable names were reintroduced. If you have a configuration variable 'g:cpp_doxygen_block_style', it should be changed to 'g:cpp_doxygen_style'. The possible values are the same.","3":"With version 1.1, old configuration variable names were reintroduced. If you have a configuration variable 'g:cpp_doxygen_block_style', it should be changed to 'g:cpp_doxygen_style'. The possible values are the same.","package":"cpp_doxygen.vmb","4":"cpp_doxygen.vmb","src_id":"23371","5":"23371","creation_date":"1433861792","6":"1433861792"},{"0":"5194","vim_version":"7.4","1":"7.4","script_version":"1.1","2":"1.1","version_comment":"I fixed a bug related to documenting function parameters. If a default value was specified in C++ function declaration, the Vim function to generate the documentation would get the parameter name wrong.","3":"I fixed a bug related to documenting function parameters. If a default value was specified in C++ function declaration, the Vim function to generate the documentation would get the parameter name wrong.","package":"cpp_doxygen.vmb","4":"cpp_doxygen.vmb","src_id":"23370","5":"23370","creation_date":"1433825247","6":"1433825247"},{"0":"5194","vim_version":"7.4","1":"7.4","script_version":"1","2":"1","version_comment":"Initial upload","3":"Initial upload","package":"cpp_doxygen.vmb","4":"cpp_doxygen.vmb","src_id":"23352","5":"23352","creation_date":"1433449655","6":"1433449655"}]},"5193":{"script_id":"5193","0":"5193","script_name":"zftool.vim","1":"zftool.vim","script_type":"utility","2":"utility","summary":"PHP plugin for running ZFTool commands","3":"PHP plugin for running ZFTool commands","description":"ZFTool is an utility module for maintaining modular Zend Framework 2\r\napplications. It runs from the command line and can be installed as ZF2 module\r\nor as PHAR\r\n\r\nThis plugin gives you access to ZFTool features without leaving your favourite\r\neditor.\r\n\r\nRequirements:\r\n\r\n- Vim running inside tmux session\r\n- Installed plugin: 'benmills\/vimux'\r\n- Command zf.php available from command line\r\n\r\nCheck requirements for zf.php at official repository:\r\n\r\nhttps:\/\/github.com\/zendframework\/ZFTool\r\n\r\nUsage:\r\n\r\nCurrently you have access to ZFTool features from command line:\r\n\r\n:ZFnewProject    - Project creation\r\n:ZFnewModule     - Module creation\r\n:ZFnewController - Controller creation\r\n:ZFnewAction     - Action creation\r\n:ZFrepeat        - Repeat last ZF command run\r\n\r\nEvery time you run a command values are cached in order to make next command\r\nquickier to run\r\n\r\nGrab the latest dev version from github: https:\/\/github.com\/dsaenztagarro\/zftool.vim","4":"ZFTool is an utility module for maintaining modular Zend Framework 2\r\napplications. It runs from the command line and can be installed as ZF2 module\r\nor as PHAR\r\n\r\nThis plugin gives you access to ZFTool features without leaving your favourite\r\neditor.\r\n\r\nRequirements:\r\n\r\n- Vim running inside tmux session\r\n- Installed plugin: 'benmills\/vimux'\r\n- Command zf.php available from command line\r\n\r\nCheck requirements for zf.php at official repository:\r\n\r\nhttps:\/\/github.com\/zendframework\/ZFTool\r\n\r\nUsage:\r\n\r\nCurrently you have access to ZFTool features from command line:\r\n\r\n:ZFnewProject    - Project creation\r\n:ZFnewModule     - Module creation\r\n:ZFnewController - Controller creation\r\n:ZFnewAction     - Action creation\r\n:ZFrepeat        - Repeat last ZF command run\r\n\r\nEvery time you run a command values are cached in order to make next command\r\nquickier to run\r\n\r\nGrab the latest dev version from github: https:\/\/github.com\/dsaenztagarro\/zftool.vim","install_details":"Extract the zip file to ~\/.vim (or vimfiles on Windows).","5":"Extract the zip file to ~\/.vim (or vimfiles on Windows).","first_name":"David","6":"David","last_name":"Saenz Tagarro","7":"Saenz Tagarro","releases":[{"0":"5193","vim_version":"7.0","1":"7.0","script_version":"0.1.0","2":"0.1.0","version_comment":"Initial upload","3":"Initial upload","package":"zftool.zip","4":"zftool.zip","src_id":"23351","5":"23351","creation_date":"1433448600","6":"1433448600"}]},"5192":{"script_id":"5192","0":"5192","script_name":"cpp_cppcheck.vim","1":"cpp_cppcheck.vim","script_type":"ftplugin","2":"ftplugin","summary":"Run Cppcheck on the current window.","3":"Run Cppcheck on the current window.","description":"This plugin will let you run Cppcheck on the C++ code in the current window. Errors from Cppcheck are presented in the quickfix window so you can edit - check - edit. Just use the command :Cppcheck. After installing the plugin, use :help cpp_cppcheck in Vim for details, including how to set command line options for Cppcheck.\r\n\r\nIf you encounter any problems, or have feature requests, please create an issue at https:\/\/github.com\/brobeson\/Tools\/\r\n\r\nI've tested this with Vim 7.4 on Linux (Kubuntu 15.04). Other platforms and versions of Vim should work, but I can't be sure.","4":"This plugin will let you run Cppcheck on the C++ code in the current window. Errors from Cppcheck are presented in the quickfix window so you can edit - check - edit. Just use the command :Cppcheck. After installing the plugin, use :help cpp_cppcheck in Vim for details, including how to set command line options for Cppcheck.\r\n\r\nIf you encounter any problems, or have feature requests, please create an issue at https:\/\/github.com\/brobeson\/Tools\/\r\n\r\nI've tested this with Vim 7.4 on Linux (Kubuntu 15.04). Other platforms and versions of Vim should work, but I can't be sure.","install_details":"You need Cppcheck installed, and available through your PATH environment variable. See http:\/\/cppcheck.sourceforge.net to get Cppcheck.\r\nDownload the vimball, open it in Vim, and source it all:\r\nvim cpp_cppcheck.vmb\r\n:source %\r\n:q\r\n","5":"You need Cppcheck installed, and available through your PATH environment variable. See http:\/\/cppcheck.sourceforge.net to get Cppcheck.\r\nDownload the vimball, open it in Vim, and source it all:\r\nvim cpp_cppcheck.vmb\r\n:source %\r\n:q\r\n","first_name":"Brendan","6":"Brendan","last_name":"","7":"","releases":[{"0":"5192","vim_version":"7.4","1":"7.4","script_version":"1","2":"1","version_comment":"Initial upload","3":"Initial upload","package":"cpp_cppcheck.vmb","4":"cpp_cppcheck.vmb","src_id":"23346","5":"23346","creation_date":"1433268119","6":"1433268119"}]},"5191":{"script_id":"5191","0":"5191","script_name":"scilab.vim","1":"scilab.vim","script_type":"syntax","2":"syntax","summary":"Scilab syntax highlighting (Windows)","3":"Scilab syntax highlighting (Windows)","description":"Scilab syntax highlighting file with 3790 keywords in five categories.\r\nUpdated to Scilab 5.5.1 with the toolboxes: GUI Builder, IPT3, JSON, NaN, Quapro and dependencies.\r\nWindows compatible, tested on Win 7.","4":"Scilab syntax highlighting file with 3790 keywords in five categories.\r\nUpdated to Scilab 5.5.1 with the toolboxes: GUI Builder, IPT3, JSON, NaN, Quapro and dependencies.\r\nWindows compatible, tested on Win 7.","install_details":"","5":"","first_name":"A.","6":"A.","last_name":"Astonfe","7":"Astonfe","releases":[{"0":"5191","vim_version":"7.0","1":"7.0","script_version":"1.5","2":"1.5","version_comment":"Some changes about colors.","3":"Some changes about colors.","package":"scilab.vim","4":"scilab.vim","src_id":"24058","5":"24058","creation_date":"1456925543","6":"1456925543"}]},"5190":{"script_id":"5190","0":"5190","script_name":"vim-tag-comment","1":"vim-tag-comment","script_type":"utility","2":"utility","summary":"property comments HTML\/XML tags","3":"property comments HTML\/XML tags","description":"This plugin provides commands that \"properly\" comment and uncomment XML and HTML tags.\r\nAll the plugins I have seen for this would take the following:\r\n\r\n\r\n  baz<\/bar>\r\n<\/foo>\r\n\r\nand comment it like this:\r\n\r\n\r\n  \r\n\r\n\r\nThis is ugly and excessive!\r\nI believe the proper way to do this is:\r\n\r\n\r\n\r\nSee the README file for more detail.","4":"This plugin provides commands that \"properly\" comment and uncomment XML and HTML tags.\r\nAll the plugins I have seen for this would take the following:\r\n\r\n\r\n  baz<\/bar>\r\n<\/foo>\r\n\r\nand comment it like this:\r\n\r\n\r\n  \r\n\r\n\r\nThis is ugly and excessive!\r\nI believe the proper way to do this is:\r\n\r\n\r\n\r\nSee the README file for more detail.","install_details":"Install with Pathogen or copy plugin\/tag-comment.vim to .vim\/plugins.","5":"Install with Pathogen or copy plugin\/tag-comment.vim to .vim\/plugins.","first_name":"Mark","6":"Mark","last_name":"Volkmann","7":"Volkmann","releases":[{"0":"5190","vim_version":"7.0","1":"7.0","script_version":"1.2","2":"1.2","version_comment":"This version avoids remapping keys if they are already mapped.","3":"This version avoids remapping keys if they are already mapped.","package":"vim-tag-comment.zip","4":"vim-tag-comment.zip","src_id":"23403","5":"23403","creation_date":"1434662252","6":"1434662252"},{"0":"5190","vim_version":"7.0","1":"7.0","script_version":"1.1","2":"1.1","version_comment":"added comments to comment tags that are not closed or closed in the shorthand way\r\nrenamed the commands\r\nadded default key mappings\r\nadded test.html for trying it out","3":"added comments to comment tags that are not closed or closed in the shorthand way\r\nrenamed the commands\r\nadded default key mappings\r\nadded test.html for trying it out","package":"tag-comment.zip","4":"tag-comment.zip","src_id":"23353","5":"23353","creation_date":"1433467858","6":"1433467858"},{"0":"5190","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"xml-comment.zip","4":"xml-comment.zip","src_id":"23341","5":"23341","creation_date":"1433119273","6":"1433119273"}]},"5189":{"script_id":"5189","0":"5189","script_name":"ctrlsf.vim","1":"ctrlsf.vim","script_type":"utility","2":"utility","summary":"an ack\/ag powered global code search and view tool","3":"an ack\/ag powered global code search and view tool","description":"An ack\/ag powered code search and view tool, like ack.vim or `:vimgrep` but together with more context, and let you edit in-place with powerful edit mode.\r\n\r\nProject repository: https:\/\/github.com\/dyng\/ctrlsf.vim\r\n\r\n(Please view above github link for comprehensive demo.)\r\n\r\nFeatures:\r\n\r\n* Search and display result in a user friendly view with customizable context.\r\n* Edit mode which is incredible useful when you are doing refactoring. (Inspired by vim-ags)\r\n* Preview mode for fast exploring.\r\n* Various options for more detailed search, view and edit.","4":"An ack\/ag powered code search and view tool, like ack.vim or `:vimgrep` but together with more context, and let you edit in-place with powerful edit mode.\r\n\r\nProject repository: https:\/\/github.com\/dyng\/ctrlsf.vim\r\n\r\n(Please view above github link for comprehensive demo.)\r\n\r\nFeatures:\r\n\r\n* Search and display result in a user friendly view with customizable context.\r\n* Edit mode which is incredible useful when you are doing refactoring. (Inspired by vim-ags)\r\n* Preview mode for fast exploring.\r\n* Various options for more detailed search, view and edit.","install_details":"1. Good old way:\r\n\r\nExtract the archive to ~\/.vim on Linux\/MacOSX or $HOME\\vimfiles on Windows.\r\nRun :helptags  ~\/.vim\/doc or :helptags $HOME\\vimfiles\\doc\r\n\r\n2. Modern way:\r\n\r\nUse package manager like pathogen, vundle or neobundle.\r\n\r\nTake vundle for example:\r\n\r\n    Bundle 'dyng\/ctrlsf.vim'","5":"1. Good old way:\r\n\r\nExtract the archive to ~\/.vim on Linux\/MacOSX or $HOME\\vimfiles on Windows.\r\nRun :helptags  ~\/.vim\/doc or :helptags $HOME\\vimfiles\\doc\r\n\r\n2. Modern way:\r\n\r\nUse package manager like pathogen, vundle or neobundle.\r\n\r\nTake vundle for example:\r\n\r\n    Bundle 'dyng\/ctrlsf.vim'","first_name":"Ye","6":"Ye","last_name":"Ding","7":"Ding","releases":[{"0":"5189","vim_version":"7.3","1":"7.3","script_version":"1.40","2":"1.40","version_comment":"Change Log:\r\nFeature:\r\n- Add '-filematch' option that a user can specify pattern against name of files should be searched.\r\n\r\nBugfix:\r\n- Fix bug with Ack2 in searching explicitly specified single file.\r\n- Fix bug of '~', '$HOME' being passed not expanded.\r\n- Fix bug that space is not escaped in completion function.","3":"Change Log:\r\nFeature:\r\n- Add '-filematch' option that a user can specify pattern against name of files should be searched.\r\n\r\nBugfix:\r\n- Fix bug with Ack2 in searching explicitly specified single file.\r\n- Fix bug of '~', '$HOME' being passed not expanded.\r\n- Fix bug that space is not escaped in completion function.","package":"ctrlsf.tar.gz","4":"ctrlsf.tar.gz","src_id":"23743","5":"23743","creation_date":"1447998953","6":"1447998953"},{"0":"5189","vim_version":"7.3","1":"7.3","script_version":"1.30","2":"1.30","version_comment":"Change Log:\r\n- Add feature of populating quickfix with search result\r\n- Improve format of error message\r\n- Fix issue with Ag's bug\r\n- Fix issue that '\\b' is not well supported\r\n- Fix missing of syntax highlighting","3":"Change Log:\r\n- Add feature of populating quickfix with search result\r\n- Improve format of error message\r\n- Fix issue with Ag's bug\r\n- Fix issue that '\\b' is not well supported\r\n- Fix missing of syntax highlighting","package":"ctrlsf.tar.gz","4":"ctrlsf.tar.gz","src_id":"23607","5":"23607","creation_date":"1442638106","6":"1442638106"},{"0":"5189","vim_version":"7.3","1":"7.3","script_version":"1.20","2":"1.20","version_comment":"Changelog:\r\n\r\n* Add key mapping for manually opening file in a split window.\r\n* Come to consume '--nogroup' format result.\r\n* Fix bug in saving dos-format files.\r\n* Debug mode improvement.\r\n* Multiple key binding.","3":"Changelog:\r\n\r\n* Add key mapping for manually opening file in a split window.\r\n* Come to consume '--nogroup' format result.\r\n* Fix bug in saving dos-format files.\r\n* Debug mode improvement.\r\n* Multiple key binding.","package":"ctrlsf.tar.gz","4":"ctrlsf.tar.gz","src_id":"23606","5":"23606","creation_date":"1442638056","6":"1442638056"},{"0":"5189","vim_version":"7.3","1":"7.3","script_version":"1.10","2":"1.10","version_comment":"Changelog:\r\nFeature:\r\n* Wrap around in navigation of matches\r\n* Open file in place if 'hidden' is set\r\n* Change success message after saving\r\n\r\nBugfix:\r\n* Improve compatibility with NERDTree\r\n* Fix document","3":"Changelog:\r\nFeature:\r\n* Wrap around in navigation of matches\r\n* Open file in place if 'hidden' is set\r\n* Change success message after saving\r\n\r\nBugfix:\r\n* Improve compatibility with NERDTree\r\n* Fix document","package":"ctrlsf.tar.gz","4":"ctrlsf.tar.gz","src_id":"23420","5":"23420","creation_date":"1435504957","6":"1435504957"},{"0":"5189","vim_version":"7.3","1":"7.3","script_version":"1.00","2":"1.00","version_comment":"Initial upload","3":"Initial upload","package":"ctrlsf.tar.gz","4":"ctrlsf.tar.gz","src_id":"23337","5":"23337","creation_date":"1433055930","6":"1433055930"}]},"5188":{"script_id":"5188","0":"5188","script_name":"vim-web2py","1":"vim-web2py","script_type":"utility","2":"utility","summary":"A plugin to browse web2py files","3":"A plugin to browse web2py files","description":"vim-web2py is a lightweight web2py plugin for vim.\r\n\r\nYou can:\r\n\r\n * Switch between the current controller and its views and vice versa with :SWITCH (or :SW)\r\n\r\n * See the models and the controllers in the current project and:\r\n    * Open a controller with \"c\" \r\n    * Open a view with \"v\" \r\n    * Open a model with \"o\" \r\n\r\nThe controllers and their views are merged in order to have a denser interface.","4":"vim-web2py is a lightweight web2py plugin for vim.\r\n\r\nYou can:\r\n\r\n * Switch between the current controller and its views and vice versa with :SWITCH (or :SW)\r\n\r\n * See the models and the controllers in the current project and:\r\n    * Open a controller with \"c\" \r\n    * Open a view with \"v\" \r\n    * Open a model with \"o\" \r\n\r\nThe controllers and their views are merged in order to have a denser interface.","install_details":"","5":"","first_name":"Hector","6":"Hector","last_name":"Davensburg","7":"Davensburg","releases":[{"0":"5188","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"vim-web2py.zip","4":"vim-web2py.zip","src_id":"23335","5":"23335","creation_date":"1433023211","6":"1433023211"}]},"5187":{"script_id":"5187","0":"5187","script_name":"ftcompl","1":"ftcompl","script_type":"utility","2":"utility","summary":"Command line completion for :set filetype","3":"Command line completion for :set filetype","description":"https:\/\/github.com\/manicmaniac\/ftcompl\r\n\r\nftcompl supports selecting filetype.\r\n\r\nInstead of \":set filetype\", you can use \":SetFileType\"\r\n\r\n\t:SetFileType vim\r\n\r\nYou can use short hands in this way.\r\n\r\n\t:sftvim  => :SetFileType vim\r\n\t:setfvim => :SetFileType vim","4":"https:\/\/github.com\/manicmaniac\/ftcompl\r\n\r\nftcompl supports selecting filetype.\r\n\r\nInstead of \":set filetype\", you can use \":SetFileType\"\r\n\r\n\t:SetFileType vim\r\n\r\nYou can use short hands in this way.\r\n\r\n\t:sftvim  => :SetFileType vim\r\n\t:setfvim => :SetFileType vim","install_details":"if you already use plugin package manager (e.g. Vundle.vim, neobundle.vim),\r\njust go along with them.\r\n\r\n\t:Bundle 'manicmaniac\/ftcompl'\r\n\r\nYou can install with the classical way. see |add-global-plugin|.","5":"if you already use plugin package manager (e.g. Vundle.vim, neobundle.vim),\r\njust go along with them.\r\n\r\n\t:Bundle 'manicmaniac\/ftcompl'\r\n\r\nYou can install with the classical way. see |add-global-plugin|.","first_name":"Ryosuke","6":"Ryosuke","last_name":"Ito","7":"Ito","releases":[{"0":"5187","vim_version":"7.4","1":"7.4","script_version":"0.1.0","2":"0.1.0","version_comment":"Initial upload","3":"Initial upload","package":"ftcompl-0.1.0.tar.gz","4":"ftcompl-0.1.0.tar.gz","src_id":"23329","5":"23329","creation_date":"1432957343","6":"1432957343"}]},"5186":{"script_id":"5186","0":"5186","script_name":"betterga","1":"betterga","script_type":"utility","2":"utility","summary":"Yet another :ascii command","3":"Yet another :ascii command","description":"https:\/\/github.com\/manicmaniac\/betterga\r\n\r\nbetterga can get more information than ga (:ascii).\r\nbetterga depends on vim(>= 7.3) compiled with python (>= 2.6 or >= 3.2) interface.\r\n","4":"https:\/\/github.com\/manicmaniac\/betterga\r\n\r\nbetterga can get more information than ga (:ascii).\r\nbetterga depends on vim(>= 7.3) compiled with python (>= 2.6 or >= 3.2) interface.\r\n","install_details":"if you already use plugin package manager (e.g. Vundle.vim, neobundle.vim),\r\njust go along with them.\r\n\r\n\t:Bundle 'manicmaniac\/betterga'\r\n\r\nYou can install with the classical way. see |add-global-plugin|.\r\n","5":"if you already use plugin package manager (e.g. Vundle.vim, neobundle.vim),\r\njust go along with them.\r\n\r\n\t:Bundle 'manicmaniac\/betterga'\r\n\r\nYou can install with the classical way. see |add-global-plugin|.\r\n","first_name":"Ryosuke","6":"Ryosuke","last_name":"Ito","7":"Ito","releases":[{"0":"5186","vim_version":"7.3","1":"7.3","script_version":"0.3.2","2":"0.3.2","version_comment":"- fix not to override user-defined template variable","3":"- fix not to override user-defined template variable","package":"betterga-0.3.2.tar.gz","4":"betterga-0.3.2.tar.gz","src_id":"24889","5":"24889","creation_date":"1484151526","6":"1484151526"},{"0":"5186","vim_version":"7.3","1":"7.3","script_version":"0.3.0","2":"0.3.0","version_comment":"0.3.0\r\n- end support for Python2.4, 2.5, 3.0, 3.1\r\n- less pollution on global namespace\r\n- some bugfixes","3":"0.3.0\r\n- end support for Python2.4, 2.5, 3.0, 3.1\r\n- less pollution on global namespace\r\n- some bugfixes","package":"betterga-0.3.0.tar.gz","4":"betterga-0.3.0.tar.gz","src_id":"23494","5":"23494","creation_date":"1438270538","6":"1438270538"},{"0":"5186","vim_version":"7.4","1":"7.4","script_version":"0.2.0","2":"0.2.0","version_comment":"0.2.0\r\n- Fully support for python3","3":"0.2.0\r\n- Fully support for python3","package":"betterga-0.2.0.tar.gz","4":"betterga-0.2.0.tar.gz","src_id":"23432","5":"23432","creation_date":"1435766495","6":"1435766495"},{"0":"5186","vim_version":"7.4","1":"7.4","script_version":"0.1.0","2":"0.1.0","version_comment":"Initial upload","3":"Initial upload","package":"betterga-0.1.0.tar.gz","4":"betterga-0.1.0.tar.gz","src_id":"23328","5":"23328","creation_date":"1432957114","6":"1432957114"}]},"5185":{"script_id":"5185","0":"5185","script_name":"Pretty Printing C like syntax","1":"Pretty Printing C like syntax","script_type":"utility","2":"utility","summary":"Format files with C-like syntax","3":"Format files with C-like syntax","description":"Press LEADER-f to re-format the current file.\r\n\r\nHint: If nothing else is specified, the Leader key is '\\\\' I think.\r\n\r\nATTENTION: Mark 'f' is used, old contents are discarded.","4":"Press LEADER-f to re-format the current file.\r\n\r\nHint: If nothing else is specified, the Leader key is '\\\\' I think.\r\n\r\nATTENTION: Mark 'f' is used, old contents are discarded.","install_details":"Copy-Paste the sources to your .vimrc or a filetype plugin.","5":"Copy-Paste the sources to your .vimrc or a filetype plugin.","first_name":"Paul","6":"Paul","last_name":"Schaefer","7":"Schaefer","releases":[{"0":"5185","vim_version":"7.4","1":"7.4","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"prettyprinter.vim","4":"prettyprinter.vim","src_id":"23326","5":"23326","creation_date":"1432918407","6":"1432918407"}]},"5184":{"script_id":"5184","0":"5184","script_name":"contextcomplete","1":"contextcomplete","script_type":"utility","2":"utility","summary":"Plugin which decides which type of insert completion to use based on context","3":"Plugin which decides which type of insert completion to use based on context","description":"INTRODUCTION\r\n\r\ncontextcomplete is a plugin that decides what kind of |ins-completion| to use\r\nbased on the text that is before the cursor.  This is triggered by the key\r\nspecified in \"g:contextcomplete_trigger\".  This key is also mapped\r\nto cycle through all the possible options until the completion menu is\r\nexited.  Regexes are used to determine which type of completion is used, which\r\ncan be configured using the \"g:contextcomplete_detect_regexes\" dictionary.\r\nA table of possible keys for this dictionary and the related completion type\r\ncan be found at \"g:contextcomplete_detect_regexes\".\r\n\r\nCUSTOMIZATION\r\n\r\ncontextcomplete can be customized to use user defined regexes to detect what\r\nkind of completion to use.  The first completion type specified in\r\n\"g:contextcomplete_key_order\" whose associated regex matches is the\r\ncompletion type that is used.  If \"g:contextcomplete_detect_regexes\".ignore is\r\nspecified, it will always override any of the other completion types and make\r\n\"g:contextcomplete_trigger\" behave as it normally would in insert mode.  The\r\nsame happens if none of the specified regexes match.  A table for the possible\r\nkeys in \"g:contextcomplete_detect_regexes\" is available below.\r\n\r\n  Dictionary Key            Related Keystroke       Default Value\r\n  lines                              i_CTRL-X_CTRL-L     None\r\n  keywords                      i_CTRL-X_CTRL-N    '\\v\\w{-1,}$'\r\n  dictionary                      i_CTRL-X_CTRL-K    None\r\n  thesaurus                      i_CTRL-X_CTRL-T     None\r\n  keywords-included      i_CTRL-X_CTRL-I       None\r\n  tags                               i_CTRL-X_CTRL-]      None\r\n  file-names                    i_CTRL-X_CTRL-F     '\\v\\\/(\\w|\\-){-}$'\r\n  macros                         i_CTRL-X_CTRL-D     None\r\n  cmdline                         i_CTRL-X_CTRL-V     None\r\n  user                               i_CTRL-X_CTRL-U     None\r\n  omnicomplete              i_CTRL-X_CTRL-O     '\\v\\.\\w{-}$'\r\n  spelling                         i_CTRL-X_s                  None\r\n  complete-keywords     i_CTRL-N                      None\r\n  ignore                           None                              '\\v^\\s*$'\r\n\r\nYou can find help for what kind of completion each related keystroke does by\r\nlooking it up in vim's help.  For omnicomplete, you would do:\r\n  :help i_CTRL-X_CTRL-O\r\n\r\n\r\nThe default configuration of this dictionary will use keyword completion\r\nbefore a word, file name completion before a forward slash, and omnicompletion\r\nbefore a dot.\r\n\r\nExample of a configuration for detection regexes:\r\n  let g:contextcomplete_detect_regexes = {\r\n      \\ 'keywords': '\\v<\\w+>$', 'ignore': '\\v^\\s*$'\r\n  \\ }\r\n\r\n\r\nYou can specify which completion types have precedence over each other using\r\nthis list.  By default, the order is: file-names, omnicomplete, keywords.\r\nIf any of the possible completion types are left out, their corresponding\r\ncompletion types in \"g:contextcomplete_detect_regexes\" will be ignored.\r\nIgnore will always takes precedence over any completion types in this list.\r\n\r\nExample:\r\n  let g:contextcomplete_key_order = [\r\n    \\ 'lines', 'keywords', 'dictionary', 'thesaurus', 'keywords-included',\r\n    \\ 'tags', 'file-names', 'macros', 'cmdline', 'user', 'omnicomplete',\r\n    \\ 'spelling', 'complete-keywords'\r\n  \\ ]\r\n\r\n\r\nYou can also specify which key is used to trigger contextcomplete.  This key\r\nis also temporarily mapped to cycle throught all the completion options until\r\nthe completion menu is exited. The default value for this option is '\\'.\r\nYou must use a literal string to specify this key, which can be done by\r\nenclosing the value in single quotes.  If you do use a special key like\r\nTab>, you must escape it like in the example below.\r\n\r\nExample:\r\n  let g:contextcomplete_trigger = '\\'\r\n\r\n\r\nISSUES\/DEVELOPMENT\r\n\r\nIssues can be reported at the github issue tracker or they can be sent to my\r\nemail at .  The github issue tracker is at\r\nhttps:\/\/github.com\/4Evergreen4\/vim-contextcomplete\/issues.  You can also get\r\nthe development versions of contextcomplete at https:\/\/github.com\/4Evergreen4\/vim-contextcomplete\/\r\n\r\nCREDITS\r\n\r\nThank you to bairu for helping me write and debug this plugin.\r\n","4":"INTRODUCTION\r\n\r\ncontextcomplete is a plugin that decides what kind of |ins-completion| to use\r\nbased on the text that is before the cursor.  This is triggered by the key\r\nspecified in \"g:contextcomplete_trigger\".  This key is also mapped\r\nto cycle through all the possible options until the completion menu is\r\nexited.  Regexes are used to determine which type of completion is used, which\r\ncan be configured using the \"g:contextcomplete_detect_regexes\" dictionary.\r\nA table of possible keys for this dictionary and the related completion type\r\ncan be found at \"g:contextcomplete_detect_regexes\".\r\n\r\nCUSTOMIZATION\r\n\r\ncontextcomplete can be customized to use user defined regexes to detect what\r\nkind of completion to use.  The first completion type specified in\r\n\"g:contextcomplete_key_order\" whose associated regex matches is the\r\ncompletion type that is used.  If \"g:contextcomplete_detect_regexes\".ignore is\r\nspecified, it will always override any of the other completion types and make\r\n\"g:contextcomplete_trigger\" behave as it normally would in insert mode.  The\r\nsame happens if none of the specified regexes match.  A table for the possible\r\nkeys in \"g:contextcomplete_detect_regexes\" is available below.\r\n\r\n  Dictionary Key            Related Keystroke       Default Value\r\n  lines                              i_CTRL-X_CTRL-L     None\r\n  keywords                      i_CTRL-X_CTRL-N    '\\v\\w{-1,}$'\r\n  dictionary                      i_CTRL-X_CTRL-K    None\r\n  thesaurus                      i_CTRL-X_CTRL-T     None\r\n  keywords-included      i_CTRL-X_CTRL-I       None\r\n  tags                               i_CTRL-X_CTRL-]      None\r\n  file-names                    i_CTRL-X_CTRL-F     '\\v\\\/(\\w|\\-){-}$'\r\n  macros                         i_CTRL-X_CTRL-D     None\r\n  cmdline                         i_CTRL-X_CTRL-V     None\r\n  user                               i_CTRL-X_CTRL-U     None\r\n  omnicomplete              i_CTRL-X_CTRL-O     '\\v\\.\\w{-}$'\r\n  spelling                         i_CTRL-X_s                  None\r\n  complete-keywords     i_CTRL-N                      None\r\n  ignore                           None                              '\\v^\\s*$'\r\n\r\nYou can find help for what kind of completion each related keystroke does by\r\nlooking it up in vim's help.  For omnicomplete, you would do:\r\n  :help i_CTRL-X_CTRL-O\r\n\r\n\r\nThe default configuration of this dictionary will use keyword completion\r\nbefore a word, file name completion before a forward slash, and omnicompletion\r\nbefore a dot.\r\n\r\nExample of a configuration for detection regexes:\r\n  let g:contextcomplete_detect_regexes = {\r\n      \\ 'keywords': '\\v<\\w+>$', 'ignore': '\\v^\\s*$'\r\n  \\ }\r\n\r\n\r\nYou can specify which completion types have precedence over each other using\r\nthis list.  By default, the order is: file-names, omnicomplete, keywords.\r\nIf any of the possible completion types are left out, their corresponding\r\ncompletion types in \"g:contextcomplete_detect_regexes\" will be ignored.\r\nIgnore will always takes precedence over any completion types in this list.\r\n\r\nExample:\r\n  let g:contextcomplete_key_order = [\r\n    \\ 'lines', 'keywords', 'dictionary', 'thesaurus', 'keywords-included',\r\n    \\ 'tags', 'file-names', 'macros', 'cmdline', 'user', 'omnicomplete',\r\n    \\ 'spelling', 'complete-keywords'\r\n  \\ ]\r\n\r\n\r\nYou can also specify which key is used to trigger contextcomplete.  This key\r\nis also temporarily mapped to cycle throught all the completion options until\r\nthe completion menu is exited. The default value for this option is '\\'.\r\nYou must use a literal string to specify this key, which can be done by\r\nenclosing the value in single quotes.  If you do use a special key like\r\nTab>, you must escape it like in the example below.\r\n\r\nExample:\r\n  let g:contextcomplete_trigger = '\\'\r\n\r\n\r\nISSUES\/DEVELOPMENT\r\n\r\nIssues can be reported at the github issue tracker or they can be sent to my\r\nemail at .  The github issue tracker is at\r\nhttps:\/\/github.com\/4Evergreen4\/vim-contextcomplete\/issues.  You can also get\r\nthe development versions of contextcomplete at https:\/\/github.com\/4Evergreen4\/vim-contextcomplete\/\r\n\r\nCREDITS\r\n\r\nThank you to bairu for helping me write and debug this plugin.\r\n","install_details":"Extract to ~\/.vim, or ~\\vimfiles (Windows).  You will need to regenerate helptags for documentation.  (fill in the install path below)\r\n\r\n:helptags ~\/.vim\/doc ","5":"Extract to ~\/.vim, or ~\\vimfiles (Windows).  You will need to regenerate helptags for documentation.  (fill in the install path below)\r\n\r\n:helptags ~\/.vim\/doc ","first_name":"Evergreen","6":"Evergreen","last_name":"Tree","7":"Tree","releases":[{"0":"5184","vim_version":"7.0","1":"7.0","script_version":"1.2.1","2":"1.2.1","version_comment":"Changed default options to include completion for file names, and improved the regexes for the already included completion types.","3":"Changed default options to include completion for file names, and improved the regexes for the already included completion types.","package":"contextcomplete.zip","4":"contextcomplete.zip","src_id":"23334","5":"23334","creation_date":"1433021876","6":"1433021876"},{"0":"5184","vim_version":"7.0","1":"7.0","script_version":"1.1.1","2":"1.1.1","version_comment":"Patch:  Previous version had many errors, this patch fixes them.  Use this instead of 0.1.0","3":"Patch:  Previous version had many errors, this patch fixes them.  Use this instead of 0.1.0","package":"contextcomplete.zip","4":"contextcomplete.zip","src_id":"23321","5":"23321","creation_date":"1432855714","6":"1432855714"},{"0":"5184","vim_version":"7.0","1":"7.0","script_version":"1.1.0","2":"1.1.0","version_comment":"Added option to customize which type of insert completion gets precedence over each other\r\n","3":"Added option to customize which type of insert completion gets precedence over each other\r\n","package":"contextcomplete.zip","4":"contextcomplete.zip","src_id":"23320","5":"23320","creation_date":"1432853890","6":"1432853890"},{"0":"5184","vim_version":"7.0","1":"7.0","script_version":"1.0.0","2":"1.0.0","version_comment":"Initial upload","3":"Initial upload","package":"contextcomplete.zip","4":"contextcomplete.zip","src_id":"23318","5":"23318","creation_date":"1432845511","6":"1432845511"}]},"5183":{"script_id":"5183","0":"5183","script_name":"vim-gitignore","1":"vim-gitignore","script_type":"utility","2":"utility","summary":"Another gitignore plugin for Vim","3":"Another gitignore plugin for Vim","description":"This plugin is host on github(https:\/\/github.com\/gisphm\/vim-gitignore).\r\nIt provides syntax highlighting and code snippets from github's gitignore.\r\nIt is forked from gitiginore.vim(http:\/\/www.vim.org\/scripts\/script.php?script_id=4568).\r\nThe difference is that this plugin's snippets support more snippet engines.\r\n\r\n1. Requirements\r\nFor using code snippets you should install snipMate, neosnippet, or ultisnips first.\r\n\r\n2. Snippets Usage\r\n\r\nvim-gitignore contains a set of snippets. To use snippets, just open your .gitignore file, type in proper snippet name (for example, Python, or Vim) and press  key or other key defined in your vimrc, which will expand snippets.\r\n\r\n3. Alternative Option\r\n\r\nYou can alse follow gitignore.io to generate .gitignore file in your project.\r\n\r\n4. Snippets List\r\n\r\nactionscript,ada,agda,android,appceleratortitanium,appcode,archives,\r\narchlinuxpackages,autotools,bancha,basercms,bower,bricxcc,c,c++,cakephp,\r\ncfwheels,chefcookbook,clojure,cloud9,cmake,codeigniter,codekit,commonlisp,\r\ncompass,composer,concrete5,coq,cvs,dart,darteditor,delphi,django,dotsettings,\r\ndreamweaver,drupal,eagle,eclipse,elasticbeanstalk,elisp,elixir,emacs,ensime,\r\nepiserver,erlang,espresso,expressionengine,fancy,finale,flexbuilder,forcedotcom,\r\nfreepascal,fuelphp,gcov,go,gradle,grails,gwt,haskell,intellij,java,jboss,jekyll,\r\njetbrains,joe,joomla,justcode,jython,kate,kdevelop4,kohana,komodoedit,laravel,\r\nlatex,lazarus,leiningen,lemonstand,lilypond,linux,lithium,magento,matlab,maven,\r\nmercurial,meteor,modelsim,monodevelop,nanoc,netbeans,node,notepadpp,objective-c,\r\nocaml,opa,opencart,openfoam,oracleforms,osx,perl,ph7cms,phpstorm,playframework,\r\nplone,prestashop,processing,pycharm,python,qooxdoo,qt,quartus2,r,rails,redcar,\r\nrhodesrhomobile,ros,ruby,rubymine,rubymotion,sass,sbt,scala,scrivener,sdcc,\r\nseamgen,senchatouch,silverstripe,sketchup,stella,sublimetext,sugarcrm,svn,\r\nsymfony,symfony2,symphonycms,tags,target3001,tarmainstallmate,tasm,tex,textmate,\r\ntextpattern,turbogears2,typo3,unity,vagrant,vim,virtualenv,visualstudio,vvvv,\r\nwaf,wakanda,webmethods,webstorm,windows,wordpress,xamarinstudio,xcode,xilinxise,\r\nyeoman,yii,zendframework\r\n\r\nIf you find that the snippets are not keeping up with the gitignore repo, you can manually execute the script rebuild-snippets to rebuild snippets.","4":"This plugin is host on github(https:\/\/github.com\/gisphm\/vim-gitignore).\r\nIt provides syntax highlighting and code snippets from github's gitignore.\r\nIt is forked from gitiginore.vim(http:\/\/www.vim.org\/scripts\/script.php?script_id=4568).\r\nThe difference is that this plugin's snippets support more snippet engines.\r\n\r\n1. Requirements\r\nFor using code snippets you should install snipMate, neosnippet, or ultisnips first.\r\n\r\n2. Snippets Usage\r\n\r\nvim-gitignore contains a set of snippets. To use snippets, just open your .gitignore file, type in proper snippet name (for example, Python, or Vim) and press  key or other key defined in your vimrc, which will expand snippets.\r\n\r\n3. Alternative Option\r\n\r\nYou can alse follow gitignore.io to generate .gitignore file in your project.\r\n\r\n4. Snippets List\r\n\r\nactionscript,ada,agda,android,appceleratortitanium,appcode,archives,\r\narchlinuxpackages,autotools,bancha,basercms,bower,bricxcc,c,c++,cakephp,\r\ncfwheels,chefcookbook,clojure,cloud9,cmake,codeigniter,codekit,commonlisp,\r\ncompass,composer,concrete5,coq,cvs,dart,darteditor,delphi,django,dotsettings,\r\ndreamweaver,drupal,eagle,eclipse,elasticbeanstalk,elisp,elixir,emacs,ensime,\r\nepiserver,erlang,espresso,expressionengine,fancy,finale,flexbuilder,forcedotcom,\r\nfreepascal,fuelphp,gcov,go,gradle,grails,gwt,haskell,intellij,java,jboss,jekyll,\r\njetbrains,joe,joomla,justcode,jython,kate,kdevelop4,kohana,komodoedit,laravel,\r\nlatex,lazarus,leiningen,lemonstand,lilypond,linux,lithium,magento,matlab,maven,\r\nmercurial,meteor,modelsim,monodevelop,nanoc,netbeans,node,notepadpp,objective-c,\r\nocaml,opa,opencart,openfoam,oracleforms,osx,perl,ph7cms,phpstorm,playframework,\r\nplone,prestashop,processing,pycharm,python,qooxdoo,qt,quartus2,r,rails,redcar,\r\nrhodesrhomobile,ros,ruby,rubymine,rubymotion,sass,sbt,scala,scrivener,sdcc,\r\nseamgen,senchatouch,silverstripe,sketchup,stella,sublimetext,sugarcrm,svn,\r\nsymfony,symfony2,symphonycms,tags,target3001,tarmainstallmate,tasm,tex,textmate,\r\ntextpattern,turbogears2,typo3,unity,vagrant,vim,virtualenv,visualstudio,vvvv,\r\nwaf,wakanda,webmethods,webstorm,windows,wordpress,xamarinstudio,xcode,xilinxise,\r\nyeoman,yii,zendframework\r\n\r\nIf you find that the snippets are not keeping up with the gitignore repo, you can manually execute the script rebuild-snippets to rebuild snippets.","install_details":"1. Using vundle, or neobundle, or other options.\r\n\r\n(1) vundle\r\n     Plugin 'gisphm\/vim-gitignore'\r\n(2) neobundle\r\n     NeoBundle 'gisphm\/vim-gitignore'\r\n\r\n2. Standard Vim way (http:\/\/vimdoc.sourceforge.net\/htmldoc\/usr_05.html#add-plugin)","5":"1. Using vundle, or neobundle, or other options.\r\n\r\n(1) vundle\r\n     Plugin 'gisphm\/vim-gitignore'\r\n(2) neobundle\r\n     NeoBundle 'gisphm\/vim-gitignore'\r\n\r\n2. Standard Vim way (http:\/\/vimdoc.sourceforge.net\/htmldoc\/usr_05.html#add-plugin)","first_name":"Huanming","6":"Huanming","last_name":"Peng","7":"Peng","releases":[{"0":"5183","vim_version":"7.0","1":"7.0","script_version":"1.1.0","2":"1.1.0","version_comment":"fix indent error when expand snippets","3":"fix indent error when expand snippets","package":"vim-gitignore-1.1.0.tar.gz","4":"vim-gitignore-1.1.0.tar.gz","src_id":"23323","5":"23323","creation_date":"1432887967","6":"1432887967"},{"0":"5183","vim_version":"7.0","1":"7.0","script_version":"1.0.0","2":"1.0.0","version_comment":"Initial upload","3":"Initial upload","package":"vim-gitignore-1.0.0.tar.gz","4":"vim-gitignore-1.0.0.tar.gz","src_id":"23316","5":"23316","creation_date":"1432740104","6":"1432740104"}]},"5182":{"script_id":"5182","0":"5182","script_name":"Vim REST Console (VRC)","1":"Vim REST Console (VRC)","script_type":"utility","2":"utility","summary":"A REST console for Vim","3":"A REST console for Vim","description":"This plug-in is to help send requests to and display responses from RESTful\r\nservices in Vim. It's useful for working with REST services that use JSON to\r\nexchange information between server and client such as ElasticSearch.\r\n\r\nVRC can be used as a cURL client  for simple needs such as getting a\r\nHTTP page response or posting to a form.\r\n\r\nRequirements:\r\n  * cURL\r\n  * Vim 7.4 (might work with the older versions)\r\n\r\nFeatures:\r\n\r\n* Execute REST request and display the response on a separate display buffer.\r\n* Make changing\/adjusting request body easy.\r\n* Can have multiple REST request blocks per VRC buffer.\r\n* Can have multiple VRC buffers where they all share the same output buffer or\r\n  each can have its own output buffer.\r\n* Particularly useful for working with REST services that require the request\r\n  body to be sent in JSON such as ElasticSearch.\r\n* Syntax highlighting.\r\n* Supported verbs: GET, POST, PUT, HEAD, PATCH, OPTIONS, and TRACE.\r\n\r\nFor more information\r\n\r\nhttp:\/\/github.com\/diepm\/vim-rest-console","4":"This plug-in is to help send requests to and display responses from RESTful\r\nservices in Vim. It's useful for working with REST services that use JSON to\r\nexchange information between server and client such as ElasticSearch.\r\n\r\nVRC can be used as a cURL client  for simple needs such as getting a\r\nHTTP page response or posting to a form.\r\n\r\nRequirements:\r\n  * cURL\r\n  * Vim 7.4 (might work with the older versions)\r\n\r\nFeatures:\r\n\r\n* Execute REST request and display the response on a separate display buffer.\r\n* Make changing\/adjusting request body easy.\r\n* Can have multiple REST request blocks per VRC buffer.\r\n* Can have multiple VRC buffers where they all share the same output buffer or\r\n  each can have its own output buffer.\r\n* Particularly useful for working with REST services that require the request\r\n  body to be sent in JSON such as ElasticSearch.\r\n* Syntax highlighting.\r\n* Supported verbs: GET, POST, PUT, HEAD, PATCH, OPTIONS, and TRACE.\r\n\r\nFor more information\r\n\r\nhttp:\/\/github.com\/diepm\/vim-rest-console","install_details":"","5":"","first_name":"diepm","6":"diepm","last_name":" ","7":" ","releases":[{"0":"5182","vim_version":"7.4","1":"7.4","script_version":"3.0.2","2":"3.0.2","version_comment":"* Fix shell escape BC with Vim 7.4.\r\n* Add CHANGELOG.\r\n* Update docs.","3":"* Fix shell escape BC with Vim 7.4.\r\n* Add CHANGELOG.\r\n* Update docs.","package":"vim-rest-console-3.0.2.tgz","4":"vim-rest-console-3.0.2.tgz","src_id":"25310","5":"25310","creation_date":"1497411410","6":"1497411410"},{"0":"5182","vim_version":"7.4","1":"7.4","script_version":"3.0.1","2":"3.0.1","version_comment":"* Fix bug `-k` auto included.\r\n* Fix response content syntax-highlighting\/formatting detection.","3":"* Fix bug `-k` auto included.\r\n* Fix response content syntax-highlighting\/formatting detection.","package":"vim-rest-console-3.0.1.tgz","4":"vim-rest-console-3.0.1.tgz","src_id":"25298","5":"25298","creation_date":"1497056365","6":"1497056365"},{"0":"5182","vim_version":"7.4","1":"7.4","script_version":"3.0.0","2":"3.0.0","version_comment":"+ Support raw cUrl options.\r\n+ Support in-line data for _bulk request of Elasticsearch.\r\n+ Deprecate some VRC options in favor of cUrl options.","3":"+ Support raw cUrl options.\r\n+ Support in-line data for _bulk request of Elasticsearch.\r\n+ Deprecate some VRC options in favor of cUrl options.","package":"vim-rest-console-3.0.0.tgz","4":"vim-rest-console-3.0.0.tgz","src_id":"25258","5":"25258","creation_date":"1495783445","6":"1495783445"},{"0":"5182","vim_version":"7.4","1":"7.4","script_version":"2.6.0","2":"2.6.0","version_comment":"+ Support global variable declaration\r\n+ Support consecutive request verbs\r\n+ Add option vrc_response_default_content_type\r\n+ Bug fix: https:\/\/github.com\/diepm\/vim-rest-console\/issues\/42","3":"+ Support global variable declaration\r\n+ Support consecutive request verbs\r\n+ Add option vrc_response_default_content_type\r\n+ Bug fix: https:\/\/github.com\/diepm\/vim-rest-console\/issues\/42","package":"vim-rest-console-2.6.0.tgz","4":"vim-rest-console-2.6.0.tgz","src_id":"24937","5":"24937","creation_date":"1485845429","6":"1485845429"},{"0":"5182","vim_version":"7.4","1":"7.4","script_version":"2.5.0","2":"2.5.0","version_comment":"+ Set commentstring so that lines can be commented by commenters.\r\n+ Fix Content-Type to default to application\/json.\r\n+ Add option vrc_show_command to include cUrl command with output.","3":"+ Set commentstring so that lines can be commented by commenters.\r\n+ Fix Content-Type to default to application\/json.\r\n+ Add option vrc_show_command to include cUrl command with output.","package":"vim-rest-console-2.5.0.tgz","4":"vim-rest-console-2.5.0.tgz","src_id":"24231","5":"24231","creation_date":"1462493958","6":"1462493958"},{"0":"5182","vim_version":"7.4","1":"7.4","script_version":"2.4.0","2":"2.4.0","version_comment":"* Support POST empty body.\r\n* Option to horizontal-split output buffer.\r\n* Option to transform \\uXXXX instances to corresponding symbols.","3":"* Support POST empty body.\r\n* Option to horizontal-split output buffer.\r\n* Option to transform \\uXXXX instances to corresponding symbols.","package":"vim-rest-console-2.4.0.tgz","4":"vim-rest-console-2.4.0.tgz","src_id":"24169","5":"24169","creation_date":"1460432087","6":"1460432087"},{"0":"5182","vim_version":"7.4","1":"7.4","script_version":"2.3.0","2":"2.3.0","version_comment":"* GET request can have request body.\r\n* Request body can be specified line by line.","3":"* GET request can have request body.\r\n* Request body can be specified line by line.","package":"vim-rest-console-2.3.0.tgz","4":"vim-rest-console-2.3.0.tgz","src_id":"24131","5":"24131","creation_date":"1458798269","6":"1458798269"},{"0":"5182","vim_version":"7.4","1":"7.4","script_version":"2.2.0","2":"2.2.0","version_comment":"Add support for PATCH, OPTIONS, and TRACE.","3":"Add support for PATCH, OPTIONS, and TRACE.","package":"vim-rest-console-2.2.0.tgz","4":"vim-rest-console-2.2.0.tgz","src_id":"23996","5":"23996","creation_date":"1454982092","6":"1454982092"},{"0":"5182","vim_version":"7.4","1":"7.4","script_version":"2.1.1","2":"2.1.1","version_comment":"Incompatibility fix","3":"Incompatibility fix","package":"vim-rest-console-2.1.1.tgz","4":"vim-rest-console-2.1.1.tgz","src_id":"23971","5":"23971","creation_date":"1454189206","6":"1454189206"},{"0":"5182","vim_version":"7.4","1":"7.4","script_version":"2.1.0","2":"2.1.0","version_comment":"* Add global section for default host and headers.\r\n* Add options for connection and max timeout.","3":"* Add global section for default host and headers.\r\n* Add options for connection and max timeout.","package":"vim-rest-console-2.1.0.tgz","4":"vim-rest-console-2.1.0.tgz","src_id":"23949","5":"23949","creation_date":"1453772688","6":"1453772688"},{"0":"5182","vim_version":"7.4","1":"7.4","script_version":"2.0.0","2":"2.0.0","version_comment":"* Support POST data from external files.\r\n* Proper use of cURL commands for HTTP verbs.\r\n* Request body is sent based on HTTP verbs.\r\n  - GET, HEAD, DELETE: as GET params.\r\n  - POST, PUT: as POST params.\r\n* Remove awkward syntaxes.\r\n  - Option `vrc_nl_sep_post_data_patterns` removed.\r\n  - GET params can be specified in request body.","3":"* Support POST data from external files.\r\n* Proper use of cURL commands for HTTP verbs.\r\n* Request body is sent based on HTTP verbs.\r\n  - GET, HEAD, DELETE: as GET params.\r\n  - POST, PUT: as POST params.\r\n* Remove awkward syntaxes.\r\n  - Option `vrc_nl_sep_post_data_patterns` removed.\r\n  - GET params can be specified in request body.","package":"vim-rest-console.tar.gz","4":"vim-rest-console.tar.gz","src_id":"23758","5":"23758","creation_date":"1448359206","6":"1448359206"},{"0":"5182","vim_version":"7.4","1":"7.4","script_version":"1.3.0","2":"1.3.0","version_comment":"* Add option to follow redirects.\r\n* Add auto-formatting response.\r\n* Add option to include\/exclude response headers.\r\n* Add some tips for output syntax highlighting.","3":"* Add option to follow redirects.\r\n* Add auto-formatting response.\r\n* Add option to include\/exclude response headers.\r\n* Add some tips for output syntax highlighting.","package":"vim-rest-console-v1.3.0.tgz","4":"vim-rest-console-v1.3.0.tgz","src_id":"23349","5":"23349","creation_date":"1433378976","6":"1433378976"},{"0":"5182","vim_version":"7.4","1":"7.4","script_version":"1.2.0","2":"1.2.0","version_comment":"* Can enable\/disable the default mapping.\r\n* Add support for cookie jars.","3":"* Can enable\/disable the default mapping.\r\n* Add support for cookie jars.","package":"vim-rest-console-1.2.0.tgz","4":"vim-rest-console-1.2.0.tgz","src_id":"23333","5":"23333","creation_date":"1433017894","6":"1433017894"},{"0":"5182","vim_version":"7.4","1":"7.4","script_version":"1.1.0","2":"1.1.0","version_comment":"Add the capability to set headers in block requests","3":"Add the capability to set headers in block requests","package":"vim-rest-console-1.1.0.tgz","4":"vim-rest-console-1.1.0.tgz","src_id":"23327","5":"23327","creation_date":"1432952478","6":"1432952478"},{"0":"5182","vim_version":"7.4","1":"7.4","script_version":"1.0.1","2":"1.0.1","version_comment":"Add 'vrc_header_content_type' option to set the request header's Content-Type. It defaults to 'application\/json'.","3":"Add 'vrc_header_content_type' option to set the request header's Content-Type. It defaults to 'application\/json'.","package":"vim-rest-console-1.0.1.tgz","4":"vim-rest-console-1.0.1.tgz","src_id":"23317","5":"23317","creation_date":"1432791759","6":"1432791759"},{"0":"5182","vim_version":"7.4","1":"7.4","script_version":"1.0.0","2":"1.0.0","version_comment":"Initial upload","3":"Initial upload","package":"vim-rest-console.tgz","4":"vim-rest-console.tgz","src_id":"23315","5":"23315","creation_date":"1432714010","6":"1432714010"}]},"5181":{"script_id":"5181","0":"5181","script_name":"vim-javacomplete2","1":"vim-javacomplete2","script_type":"utility","2":"utility","summary":"Updated javacomplete plugin for vim.","3":"Updated javacomplete plugin for vim.","description":"see: https:\/\/github.com\/artur-shaik\/vim-javacomplete2","4":"see: https:\/\/github.com\/artur-shaik\/vim-javacomplete2","install_details":"see: https:\/\/github.com\/artur-shaik\/vim-javacomplete2","5":"see: https:\/\/github.com\/artur-shaik\/vim-javacomplete2","first_name":"Artur","6":"Artur","last_name":"Shaikhullin","7":"Shaikhullin","releases":[{"0":"5181","vim_version":"7.4","1":"7.4","script_version":"v2.3.5","2":"v2.3.5","version_comment":"Information on release: https:\/\/github.com\/artur-shaik\/vim-javacomplete2\/releases\/tag\/v2.3.5","3":"Information on release: https:\/\/github.com\/artur-shaik\/vim-javacomplete2\/releases\/tag\/v2.3.5","package":"vim-javacomplete2-2.3.5.tar.gz","4":"vim-javacomplete2-2.3.5.tar.gz","src_id":"24102","5":"24102","creation_date":"1458025702","6":"1458025702"},{"0":"5181","vim_version":"7.4","1":"7.4","script_version":"v2.3.4","2":"v2.3.4","version_comment":"Use maven, gradle, or Eclipse's classpath file to generate classpath;\r\nComplete methods declaration on @Override;\r\nHuge bug fix release, thanks to contributers.","3":"Use maven, gradle, or Eclipse's classpath file to generate classpath;\r\nComplete methods declaration on @Override;\r\nHuge bug fix release, thanks to contributers.","package":"vim-javacomplete2-2.3.4.tar.gz","4":"vim-javacomplete2-2.3.4.tar.gz","src_id":"23799","5":"23799","creation_date":"1450456672","6":"1450456672"},{"0":"5181","vim_version":"7.4","1":"7.4","script_version":"v2.3.3","2":"v2.3.3","version_comment":"Jsp support fixed.","3":"Jsp support fixed.","package":"vim-javacomplete2-2.3.3.zip","4":"vim-javacomplete2-2.3.3.zip","src_id":"23655","5":"23655","creation_date":"1444301064","6":"1444301064"},{"0":"5181","vim_version":"7.4","1":"7.4","script_version":"v2.3.2","2":"v2.3.2","version_comment":"Nested classes.","3":"Nested classes.","package":"vim-javacomplete2-2.3.2.tar.gz","4":"vim-javacomplete2-2.3.2.tar.gz","src_id":"23601","5":"23601","creation_date":"1442579946","6":"1442579946"},{"0":"5181","vim_version":"7.4","1":"7.4","script_version":"v2.3.1","2":"v2.3.1","version_comment":"Better experience with imports.","3":"Better experience with imports.","package":"vim-javacomplete2-2.3.1.tar.gz","4":"vim-javacomplete2-2.3.1.tar.gz","src_id":"23581","5":"23581","creation_date":"1441645010","6":"1441645010"},{"0":"5181","vim_version":"7.4","1":"7.4","script_version":"v2.3","2":"v2.3","version_comment":"Annotation completions.","3":"Annotation completions.","package":"vim-javacomplete2-2.3.tar.gz","4":"vim-javacomplete2-2.3.tar.gz","src_id":"23489","5":"23489","creation_date":"1438154473","6":"1438154473"},{"0":"5181","vim_version":"7.4","1":"7.4","script_version":"2.2","2":"2.2","version_comment":"Lambdas completion","3":"Lambdas completion","package":"vim-javacomplete2-2.2.tar.gz","4":"vim-javacomplete2-2.2.tar.gz","src_id":"23457","5":"23457","creation_date":"1436351620","6":"1436351620"},{"0":"5181","vim_version":"7.0","1":"7.0","script_version":"v2.1","2":"v2.1","version_comment":"Generics support. Bug fixes.","3":"Generics support. Bug fixes.","package":"vim-javacomplete-v2.1.tar.gz","4":"vim-javacomplete-v2.1.tar.gz","src_id":"23381","5":"23381","creation_date":"1434112759","6":"1434112759"},{"0":"5181","vim_version":"7.0","1":"7.0","script_version":"2.0","2":"2.0","version_comment":"Initial upload","3":"Initial upload","package":"vim-javacomplete2.tar.gz","4":"vim-javacomplete2.tar.gz","src_id":"23312","5":"23312","creation_date":"1432626483","6":"1432626483"}]},"5180":{"script_id":"5180","0":"5180","script_name":"Hardy","1":"Hardy","script_type":"ftplugin","2":"ftplugin","summary":"Arduino IDE intregation for vim","3":"Arduino IDE intregation for vim","description":"vim-hardy provides support for Arduino in vim.  It covers syntax, compilation,\r\nand verification for Arduino code.  I decided to call this plugin \"vim-hardy\"\r\nbecause \"Arduino\" means \"hardy friend\" in italian. Note that I did not\r\nwrite the arduino syntax file, it was created by Johannes Hoff, and is available here:\r\nvimscript#2654\r\n\r\nArduino IDE version 1.5.0 and up is required for the compilation and uploading\r\nof Arduino code.  By default, vim-hardy looks for it in your PATH, but you can\r\nspecify an installation directory with \"g:hardy_arduino_path`\"\r\n\r\nTo verify an Arduino file, run \":ArduinoVerify\".  To compile and upload it, use\r\n\":ArduinoUpload\".  For information on any options and other features, see\r\n\"doc\/hardy.txt\".\r\n\r\nFor development versions and bug reports, see the Github repository:\r\nhttps:\/\/github.com\/4Evergreen4\/vim-hardy\r\n\r\nAny feedback can be sent to evergreenubuntu[AT]gmail[DOT]com\r\n","4":"vim-hardy provides support for Arduino in vim.  It covers syntax, compilation,\r\nand verification for Arduino code.  I decided to call this plugin \"vim-hardy\"\r\nbecause \"Arduino\" means \"hardy friend\" in italian. Note that I did not\r\nwrite the arduino syntax file, it was created by Johannes Hoff, and is available here:\r\nvimscript#2654\r\n\r\nArduino IDE version 1.5.0 and up is required for the compilation and uploading\r\nof Arduino code.  By default, vim-hardy looks for it in your PATH, but you can\r\nspecify an installation directory with \"g:hardy_arduino_path`\"\r\n\r\nTo verify an Arduino file, run \":ArduinoVerify\".  To compile and upload it, use\r\n\":ArduinoUpload\".  For information on any options and other features, see\r\n\"doc\/hardy.txt\".\r\n\r\nFor development versions and bug reports, see the Github repository:\r\nhttps:\/\/github.com\/4Evergreen4\/vim-hardy\r\n\r\nAny feedback can be sent to evergreenubuntu[AT]gmail[DOT]com\r\n","install_details":"Extract to ~\/.vim, or ~\\vimfiles (Windows).  You will need to regenerate helptags for documentation.  (fill in the install path below)\r\n\r\n:helptags ~\/.vim\/doc\r\n ","5":"Extract to ~\/.vim, or ~\\vimfiles (Windows).  You will need to regenerate helptags for documentation.  (fill in the install path below)\r\n\r\n:helptags ~\/.vim\/doc\r\n ","first_name":"Evergreen","6":"Evergreen","last_name":"Tree","7":"Tree","releases":[{"0":"5180","vim_version":"7.0","1":"7.0","script_version":"1.0.0","2":"1.0.0","version_comment":"Initial upload","3":"Initial upload","package":"hardy.zip","4":"hardy.zip","src_id":"23307","5":"23307","creation_date":"1432412876","6":"1432412876"}]},"5179":{"script_id":"5179","0":"5179","script_name":"Scrawl","1":"Scrawl","script_type":"utility","2":"utility","summary":"Utility plugin which provides a customizable scratch buffer","3":"Utility plugin which provides a customizable scratch buffer","description":"Scrawl is a customizable scratch buffer for writing temporary notes, and for\r\ntesting small code pieces. Changes in it will be discarded when vim is quit.\r\nThis was heavily inspired by vimscript#664. I made this because it wasn't\r\ncustomizable enough.\r\n\r\nUse \":ScrawlSplit\" to open scrawl in a new split.  You can then use\r\n\":ScrawlClose\" to close that split from anywhere in the tab.  If you want to\r\nopen scrawl in the current buffer, use \":ScrawlOpen\".  Then when you run\r\n\":ScrawlClose\" in that current tab, it will return to editing the previous file.\r\nYou can only have one scrawl buffer open in each tab.\r\n\r\nSee \"doc\/scrawl.txt\" for options and other documentation.\r\n\r\nFor development versions and bug reports, see the Github repository:\r\nhttps:\/\/github.com\/4Evergreen4\/vim-scrawl\r\n\r\nAny other feedback can be sent to evergreenubuntu[AT]gmail[DOT]com\r\n","4":"Scrawl is a customizable scratch buffer for writing temporary notes, and for\r\ntesting small code pieces. Changes in it will be discarded when vim is quit.\r\nThis was heavily inspired by vimscript#664. I made this because it wasn't\r\ncustomizable enough.\r\n\r\nUse \":ScrawlSplit\" to open scrawl in a new split.  You can then use\r\n\":ScrawlClose\" to close that split from anywhere in the tab.  If you want to\r\nopen scrawl in the current buffer, use \":ScrawlOpen\".  Then when you run\r\n\":ScrawlClose\" in that current tab, it will return to editing the previous file.\r\nYou can only have one scrawl buffer open in each tab.\r\n\r\nSee \"doc\/scrawl.txt\" for options and other documentation.\r\n\r\nFor development versions and bug reports, see the Github repository:\r\nhttps:\/\/github.com\/4Evergreen4\/vim-scrawl\r\n\r\nAny other feedback can be sent to evergreenubuntu[AT]gmail[DOT]com\r\n","install_details":"Extract to ~\/.vim, or ~\\vimfiles (Windows).  You will need to regenerate helptags for documentation.  (fill in the install path below)\r\n\r\n:helptags ~\/.vim\/doc","5":"Extract to ~\/.vim, or ~\\vimfiles (Windows).  You will need to regenerate helptags for documentation.  (fill in the install path below)\r\n\r\n:helptags ~\/.vim\/doc","first_name":"Evergreen","6":"Evergreen","last_name":"Tree","7":"Tree","releases":[{"0":"5179","vim_version":"7.0","1":"7.0","script_version":"1.0.0","2":"1.0.0","version_comment":"Initial upload","3":"Initial upload","package":"scrawl.zip","4":"scrawl.zip","src_id":"23306","5":"23306","creation_date":"1432412365","6":"1432412365"}]},"5178":{"script_id":"5178","0":"5178","script_name":"vim-sandwich","1":"vim-sandwich","script_type":"utility","2":"utility","summary":"The set of operator and textobject plugins to edit sandwiched textobjects.","3":"The set of operator and textobject plugins to edit sandwiched textobjects.","description":"sandwich.vim is the set of operator and textobject plugins to add\/delete\/replace surroundings of a sandwiched textobject, like (foo), \"bar\".\r\n\r\n* add\r\n    Press sa{motion\/textobject}{addition}. For example, a key sequence saiw( makes foo to (foo).\r\n\r\n* delete\r\n    Press sdb or sd{deletion}. For example, key sequences sdb or sd( makes (foo) to foo. sdb searchs a set of surrounding automatically.\r\n\r\n* replace\r\n    Press srb{addition} or sr{deletion}{addition}. For example, key sequences srb\" or sr(\" makes (foo) to \"foo\".\r\n\r\nLatest version: https:\/\/github.com\/machakann\/vim-sandwich","4":"sandwich.vim is the set of operator and textobject plugins to add\/delete\/replace surroundings of a sandwiched textobject, like (foo), \"bar\".\r\n\r\n* add\r\n    Press sa{motion\/textobject}{addition}. For example, a key sequence saiw( makes foo to (foo).\r\n\r\n* delete\r\n    Press sdb or sd{deletion}. For example, key sequences sdb or sd( makes (foo) to foo. sdb searchs a set of surrounding automatically.\r\n\r\n* replace\r\n    Press srb{addition} or sr{deletion}{addition}. For example, key sequences srb\" or sr(\" makes (foo) to \"foo\".\r\n\r\nLatest version: https:\/\/github.com\/machakann\/vim-sandwich","install_details":"Unzip and just put all folders in your ~\/.vim.","5":"Unzip and just put all folders in your ~\/.vim.","first_name":"Masaaki","6":"Masaaki","last_name":"Nakamura","7":"Nakamura","releases":[{"0":"5178","vim_version":"7.4","1":"7.4","script_version":"1.3.0","2":"1.3.0","version_comment":"* Bug fixes.\r\n* Add functional inputs. (https:\/\/github.com\/machakann\/vim-sandwich\/wiki\/Magic-characters)","3":"* Bug fixes.\r\n* Add functional inputs. (https:\/\/github.com\/machakann\/vim-sandwich\/wiki\/Magic-characters)","package":"vim-sandwich-1.3.0.zip","4":"vim-sandwich-1.3.0.zip","src_id":"24472","5":"24472","creation_date":"1472269864","6":"1472269864"},{"0":"5178","vim_version":"7.4","1":"7.4","script_version":"1.2.2","2":"1.2.2","version_comment":"* Bug fixes.\r\n* Improve 'skip_break' option for textobj-sandwich.","3":"* Bug fixes.\r\n* Improve 'skip_break' option for textobj-sandwich.","package":"vim-sandwich-1.2.2.zip","4":"vim-sandwich-1.2.2.zip","src_id":"23686","5":"23686","creation_date":"1445875755","6":"1445875755"},{"0":"5178","vim_version":"7.4","1":"7.4","script_version":"1.2.1","2":"1.2.1","version_comment":"Bug fixes.","3":"Bug fixes.","package":"vim-sandwich-1.2.1.zip","4":"vim-sandwich-1.2.1.zip","src_id":"23659","5":"23659","creation_date":"1444389545","6":"1444389545"},{"0":"5178","vim_version":"7.4","1":"7.4","script_version":"1.2.0","2":"1.2.0","version_comment":"* Bug fixes.\r\n* Add 'skip_regex_head' and 'skip_regex_tail' option.\r\n* Add 'inner_syntax' option.\r\n* Update default recipes to fix inconveniences in several filetypes.","3":"* Bug fixes.\r\n* Add 'skip_regex_head' and 'skip_regex_tail' option.\r\n* Add 'inner_syntax' option.\r\n* Update default recipes to fix inconveniences in several filetypes.","package":"vim-sandwich-1.2.0.zip","4":"vim-sandwich-1.2.0.zip","src_id":"23557","5":"23557","creation_date":"1440760373","6":"1440760373"},{"0":"5178","vim_version":"7.4","1":"7.4","script_version":"1.1.1","2":"1.1.1","version_comment":"Bug fixes.","3":"Bug fixes.","package":"vim-sandwich-1.1.1.zip","4":"vim-sandwich-1.1.1.zip","src_id":"23496","5":"23496","creation_date":"1438367623","6":"1438367623"},{"0":"5178","vim_version":"7.4","1":"7.4","script_version":"1.1.0","2":"1.1.0","version_comment":"* Bug fixes.\r\n* Add 'autoindent' option\r\n* Add 'indentkeys' option","3":"* Bug fixes.\r\n* Add 'autoindent' option\r\n* Add 'indentkeys' option","package":"vim-sandwich-1.1.0.zip","4":"vim-sandwich-1.1.0.zip","src_id":"23475","5":"23475","creation_date":"1437644678","6":"1437644678"},{"0":"5178","vim_version":"7.4","1":"7.4","script_version":"1.0.0","2":"1.0.0","version_comment":"Initial upload","3":"Initial upload","package":"vim-sandwich-1.0.0.zip","4":"vim-sandwich-1.0.0.zip","src_id":"23305","5":"23305","creation_date":"1432376490","6":"1432376490"}]},"5177":{"script_id":"5177","0":"5177","script_name":"PaperColor.vim","1":"PaperColor.vim","script_type":"color scheme","2":"color scheme","summary":"Light & Dark Vim color scheme inspired by Google's Material Design","3":"Light & Dark Vim color scheme inspired by Google's Material Design","description":"Light and Dark color scheme for terminal and graphic Vim awesome editor.\r\n\r\nSupport GUI-color and identical 256-color.\r\nAlso gracefully down to 16-color terminal, which will use terminal native colors.\r\nIn 8-color and 4-color, it might lack the necessary variation of colors to express PaperColor, but seriously let me know if you still use these kinds of terminals.\r\n\r\nThere are many configurable options such as color overriding.\r\n\r\nMore info \/ screenshots: https:\/\/github.com\/NLKNguyen\/papercolor-theme\r\n\r\nInspired by Google's Material Design\r\n\r\nImprove code readability; great for presentation\r\n\r\nCurrently designed for these languages:\r\n\r\n+ Haskell, Erlang, Elixir, Clojure, Elm, Purescript, F#\r\n+ C, C++, Golang, Rust, Java, JavaScript, Python, Ruby, Pascal, PHP, Perl, LUA\r\n+ DTrace, SystemTap, SQL\/MySQL, Octave\/MATLAB, R, Lex\/Flex & Yacc\/Bison, ASN.1, Assembly (MIPS, GAS, NASM), Bash\/Shell script, Sed, Awk, Vim script, + Powershell script\r\n+ Dockerfile, Makefile, CMake, NGINX, Cucumber, YAML, JSON, HTML, XML, Markdown, reStructuredText, PlantUML, Dosini, Mail, Git commit message\r\n+ Ada, COBOL, Fortran, ALGOL, (what's your other favorite dinosaur?)\r\n\r\n\r\nOther file types can still display well as long as your Vim is set up to recognize the language syntax even though that may not be the optimal experience. So, if the language you are working on isn't listed here, feel free to make a design request.\r\n\r\nPlugin support: vimdiff, netrw, NERDTree, tagbar, tabline, vim-airline, vim-indent-guides, vim-startify, AGit\r\n\r\n---\r\n\r\nGo to the project Github page for up-to-date information as well as the list of syntax-highlighting plugins that this color scheme targets. https:\/\/github.com\/NLKNguyen\/papercolor-theme\r\n","4":"Light and Dark color scheme for terminal and graphic Vim awesome editor.\r\n\r\nSupport GUI-color and identical 256-color.\r\nAlso gracefully down to 16-color terminal, which will use terminal native colors.\r\nIn 8-color and 4-color, it might lack the necessary variation of colors to express PaperColor, but seriously let me know if you still use these kinds of terminals.\r\n\r\nThere are many configurable options such as color overriding.\r\n\r\nMore info \/ screenshots: https:\/\/github.com\/NLKNguyen\/papercolor-theme\r\n\r\nInspired by Google's Material Design\r\n\r\nImprove code readability; great for presentation\r\n\r\nCurrently designed for these languages:\r\n\r\n+ Haskell, Erlang, Elixir, Clojure, Elm, Purescript, F#\r\n+ C, C++, Golang, Rust, Java, JavaScript, Python, Ruby, Pascal, PHP, Perl, LUA\r\n+ DTrace, SystemTap, SQL\/MySQL, Octave\/MATLAB, R, Lex\/Flex & Yacc\/Bison, ASN.1, Assembly (MIPS, GAS, NASM), Bash\/Shell script, Sed, Awk, Vim script, + Powershell script\r\n+ Dockerfile, Makefile, CMake, NGINX, Cucumber, YAML, JSON, HTML, XML, Markdown, reStructuredText, PlantUML, Dosini, Mail, Git commit message\r\n+ Ada, COBOL, Fortran, ALGOL, (what's your other favorite dinosaur?)\r\n\r\n\r\nOther file types can still display well as long as your Vim is set up to recognize the language syntax even though that may not be the optimal experience. So, if the language you are working on isn't listed here, feel free to make a design request.\r\n\r\nPlugin support: vimdiff, netrw, NERDTree, tagbar, tabline, vim-airline, vim-indent-guides, vim-startify, AGit\r\n\r\n---\r\n\r\nGo to the project Github page for up-to-date information as well as the list of syntax-highlighting plugins that this color scheme targets. https:\/\/github.com\/NLKNguyen\/papercolor-theme\r\n","install_details":"Step 1:\r\nInstall with Vundle plugin manager for easy update (:PluginUpdate)\r\n\r\n    Plugin 'NLKNguyen\/papercolor-theme'\r\n\r\nOr manually copy PaperColor.vim file to your ~\/.vim\/colors\/ directory\r\n\r\n\r\nStep 2:\r\nPut this in your ~\/.vimrc\r\n\r\n    \"set background=dark    \" Light theme is used by default\r\n    set t_Co=256\r\n    colorscheme PaperColor","5":"Step 1:\r\nInstall with Vundle plugin manager for easy update (:PluginUpdate)\r\n\r\n    Plugin 'NLKNguyen\/papercolor-theme'\r\n\r\nOr manually copy PaperColor.vim file to your ~\/.vim\/colors\/ directory\r\n\r\n\r\nStep 2:\r\nPut this in your ~\/.vimrc\r\n\r\n    \"set background=dark    \" Light theme is used by default\r\n    set t_Co=256\r\n    colorscheme PaperColor","first_name":"Nikyle","6":"Nikyle","last_name":"Nguyen","7":"Nguyen","releases":[{"0":"5177","vim_version":"7.0","1":"7.0","script_version":"0.9.3","2":"0.9.3","version_comment":"Design for many more languages: F#, PureScript, Elm, Rust, PowerShell, AWK, ASN.1, ALGOL 68, and Modern Fortran!\r\n\r\n","3":"Design for many more languages: F#, PureScript, Elm, Rust, PowerShell, AWK, ASN.1, ALGOL 68, and Modern Fortran!\r\n\r\n","package":"PaperColor.zip","4":"PaperColor.zip","src_id":"26041","5":"26041","creation_date":"1528716925","6":"1528716925"},{"0":"5177","vim_version":"7.0","1":"7.0","script_version":"0.9.2","2":"0.9.2","version_comment":"Provide option to override any color. See design guideline: https:\/\/github.com\/NLKNguyen\/papercolor-theme\/blob\/master\/DESIGN.md","3":"Provide option to override any color. See design guideline: https:\/\/github.com\/NLKNguyen\/papercolor-theme\/blob\/master\/DESIGN.md","package":"PaperColor.zip","4":"PaperColor.zip","src_id":"25598","5":"25598","creation_date":"1506916102","6":"1506916102"},{"0":"5177","vim_version":"7.0","1":"7.0","script_version":"0.9.1","2":"0.9.1","version_comment":"Major speed improvement (10X faster loading time)\r\n\r\nImprove support for Git \/ Diff related such as Git commit message or AGit plugin\r\n\r\nAdd some dinosaur languages support: Ada, COBOL.\r\n\r\nImprove systematic user config options for languages and themes (it's plural for a reason -- wait for version 1.0 :) )","3":"Major speed improvement (10X faster loading time)\r\n\r\nImprove support for Git \/ Diff related such as Git commit message or AGit plugin\r\n\r\nAdd some dinosaur languages support: Ada, COBOL.\r\n\r\nImprove systematic user config options for languages and themes (it's plural for a reason -- wait for version 1.0 :) )","package":"PaperColor.zip","4":"PaperColor.zip","src_id":"25544","5":"25544","creation_date":"1504154572","6":"1504154572"},{"0":"5177","vim_version":"7.0","1":"7.0","script_version":"0.8","2":"0.8","version_comment":"Improve language support: Elixir, C\/C++, Python\r\nProvide systematic user-config options that are flexible for future implementations\r\nFix general issues","3":"Improve language support: Elixir, C\/C++, Python\r\nProvide systematic user-config options that are flexible for future implementations\r\nFix general issues","package":"papercolor-theme-0.8.tar.gz","4":"papercolor-theme-0.8.tar.gz","src_id":"25026","5":"25026","creation_date":"1489202037","6":"1489202037"},{"0":"5177","vim_version":"7.0","1":"7.0","script_version":"0.6.0","2":"0.6.0","version_comment":"Add language support for Erlang, Elixir, and Cucumber; \r\nImprove JavaScript, VimL","3":"Add language support for Erlang, Elixir, and Cucumber; \r\nImprove JavaScript, VimL","package":"PaperColor.zip","4":"PaperColor.zip","src_id":"23967","5":"23967","creation_date":"1454118780","6":"1454118780"},{"0":"5177","vim_version":"7.0","1":"7.0","script_version":"0.5.0","2":"0.5.0","version_comment":"Now designed for more than 30 languages and support more plugins","3":"Now designed for more than 30 languages and support more plugins","package":"PaperColor.zip","4":"PaperColor.zip","src_id":"23835","5":"23835","creation_date":"1451333948","6":"1451333948"},{"0":"5177","vim_version":"7.0","1":"7.0","script_version":"0.1.1","2":"0.1.1","version_comment":"Add support for vim-airline and vimdiff; \r\nImprove Ruby, Python, HTML, and JavaScript syntax colors","3":"Add support for vim-airline and vimdiff; \r\nImprove Ruby, Python, HTML, and JavaScript syntax colors","package":"PaperColor.zip","4":"PaperColor.zip","src_id":"23342","5":"23342","creation_date":"1433128090","6":"1433128090"},{"0":"5177","vim_version":"7.0","1":"7.0","script_version":"0.1.0","2":"0.1.0","version_comment":"Initial Upload","3":"Initial Upload","package":"PaperColor.vim","4":"PaperColor.vim","src_id":"23303","5":"23303","creation_date":"1432261958","6":"1432261958"}]},"5176":{"script_id":"5176","0":"5176","script_name":"dotenv.vim","1":"dotenv.vim","script_type":"utility","2":"utility","summary":"Basic support for .env and Procfile","3":"Basic support for .env and Procfile","description":"## Interactive Usage\r\n\r\nUse `:Dotenv {file}` or `:Dotenv {dir}` to load a `.env` file and set the corresponding environment variables in Vim.  Use `:verbose Dotenv` to see what variables are actually being set.\r\n\r\n## Projections\r\n\r\nWith projectionist.vim (vimscript #4989) and dispatch.vim (vimscript #4504) installed, you'll get a default `:Start` of `foreman start` for projects with a `Procfile`, and a default `:Dispatch` of `foreman check` for the `Procfile` itself.\r\n\r\n## Dispatch\r\n\r\nIf you call `:Dispatch foreman run whatever` or `:Dispatch dotenv whatever`, the compiler will be correctly selected for the `whatever` command.\r\n\r\n## API\r\n\r\nWhile the above are all marginally helpful, this is the use case that inspired the plugin.  Other plugins can call `DotenvGet('VAR')` to get the value of `$VAR` globally or from the current buffer's `.env`.  Here's a wrapper to optionally use `DotenvGet()` if it's available.\r\n\r\n    function! s:env(var) abort\r\n      return exists('*DotenvGet') ? DotenvGet(a:var) : eval('$'.a:var)\r\n    endfunction\r\n\r\n    let db_url = s:env('DATABASE_URL')\r\n\r\nThere's also `DotenvExpand()`, a drop-in replacement for `expand()`.\r\n\r\n    function! s:expand(expr) abort\r\n      return exists('*DotenvExpand') ? DotenvExpand(a:expr) : expand(a:expr)\r\n    endfunction","4":"## Interactive Usage\r\n\r\nUse `:Dotenv {file}` or `:Dotenv {dir}` to load a `.env` file and set the corresponding environment variables in Vim.  Use `:verbose Dotenv` to see what variables are actually being set.\r\n\r\n## Projections\r\n\r\nWith projectionist.vim (vimscript #4989) and dispatch.vim (vimscript #4504) installed, you'll get a default `:Start` of `foreman start` for projects with a `Procfile`, and a default `:Dispatch` of `foreman check` for the `Procfile` itself.\r\n\r\n## Dispatch\r\n\r\nIf you call `:Dispatch foreman run whatever` or `:Dispatch dotenv whatever`, the compiler will be correctly selected for the `whatever` command.\r\n\r\n## API\r\n\r\nWhile the above are all marginally helpful, this is the use case that inspired the plugin.  Other plugins can call `DotenvGet('VAR')` to get the value of `$VAR` globally or from the current buffer's `.env`.  Here's a wrapper to optionally use `DotenvGet()` if it's available.\r\n\r\n    function! s:env(var) abort\r\n      return exists('*DotenvGet') ? DotenvGet(a:var) : eval('$'.a:var)\r\n    endfunction\r\n\r\n    let db_url = s:env('DATABASE_URL')\r\n\r\nThere's also `DotenvExpand()`, a drop-in replacement for `expand()`.\r\n\r\n    function! s:expand(expr) abort\r\n      return exists('*DotenvExpand') ? DotenvExpand(a:expr) : expand(a:expr)\r\n    endfunction","install_details":"Extract in ~\/.vim (~\\vimfiles on Windows).","5":"Extract in ~\/.vim (~\\vimfiles on Windows).","first_name":"Tim","6":"Tim","last_name":"Pope","7":"Pope","releases":[{"0":"5176","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"dotenv.zip","4":"dotenv.zip","src_id":"23282","5":"23282","creation_date":"1431900479","6":"1431900479"}]},"5175":{"script_id":"5175","0":"5175","script_name":"git-flow-format","1":"git-flow-format","script_type":"utility","2":"utility","summary":"Formats Git Flow prefixed branch names to take less space in your status line.","3":"Formats Git Flow prefixed branch names to take less space in your status line.","description":"git-flow-format is a plugin for vim-airline, which formats a Git Flow branch name in order to shorten the prefixes and take up less space in your status line.\r\n\r\nThis is best shown with a couple of examples:\r\n\r\nfeature\/new_thing --> F:new_thing\r\nrelease\/v1.0.0 --> R:v1.0.0","4":"git-flow-format is a plugin for vim-airline, which formats a Git Flow branch name in order to shorten the prefixes and take up less space in your status line.\r\n\r\nThis is best shown with a couple of examples:\r\n\r\nfeature\/new_thing --> F:new_thing\r\nrelease\/v1.0.0 --> R:v1.0.0","install_details":"git-flow-format can be installed with Pathogen in the normal way. Just clone this repo into your bundle directory:\r\n\r\ngit clone https:\/\/github.com\/renyard\/vim-git-flow-format.git ~\/.vim\/bundle\/vim-git-flow-format\r\n\r\nYou can then configure vim-airline to use this format by adding the following line to your .vimrc:\r\n\r\nlet g:airline#extensions#branch#format = 'Git_flow_branch_format'","5":"git-flow-format can be installed with Pathogen in the normal way. Just clone this repo into your bundle directory:\r\n\r\ngit clone https:\/\/github.com\/renyard\/vim-git-flow-format.git ~\/.vim\/bundle\/vim-git-flow-format\r\n\r\nYou can then configure vim-airline to use this format by adding the following line to your .vimrc:\r\n\r\nlet g:airline#extensions#branch#format = 'Git_flow_branch_format'","first_name":"Ian","6":"Ian","last_name":"Renyard","7":"Renyard","releases":[{"0":"5175","vim_version":"7.4","1":"7.4","script_version":"0.4","2":"0.4","version_comment":"Updated the default prefixes in order to allow greater flexibility customization.","3":"Updated the default prefixes in order to allow greater flexibility customization.","package":"git-flow-format.zip","4":"git-flow-format.zip","src_id":"23292","5":"23292","creation_date":"1432036912","6":"1432036912"},{"0":"5175","vim_version":"7.4","1":"7.4","script_version":"0.3","2":"0.3","version_comment":"Optimized the loading of Git Flow config values.","3":"Optimized the loading of Git Flow config values.","package":"git-flow-format.zip","4":"git-flow-format.zip","src_id":"23289","5":"23289","creation_date":"1432035988","6":"1432035988"},{"0":"5175","vim_version":"7.0","1":"7.0","script_version":"0.2","2":"0.2","version_comment":"Returns an empty string immediately when an empty string is input.","3":"Returns an empty string immediately when an empty string is input.","package":"git-flow-format.zip","4":"git-flow-format.zip","src_id":"23283","5":"23283","creation_date":"1431903991","6":"1431903991"},{"0":"5175","vim_version":"7.4","1":"7.4","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"git-flow-format.zip","4":"git-flow-format.zip","src_id":"23280","5":"23280","creation_date":"1431893090","6":"1431893090"}]},"5174":{"script_id":"5174","0":"5174","script_name":"slashcomment.vim","1":"slashcomment.vim","script_type":"utility","2":"utility","summary":"slash comment works like eclipse.","3":"slash comment works like eclipse.","description":"This plug-in is a comment shortcut like eclipse.\r\nctrl-c to toggle comments","4":"This plug-in is a comment shortcut like eclipse.\r\nctrl-c to toggle comments","install_details":"1. Download the slashcomment.vim file to the $HOME\/.vim\/plugin or the \r\n    $HOME\/vimfiles\/plugin or the $VIM\/vimfiles\/plugin directory.\r\n\r\n2. Restart Vim. ","5":"1. Download the slashcomment.vim file to the $HOME\/.vim\/plugin or the \r\n    $HOME\/vimfiles\/plugin or the $VIM\/vimfiles\/plugin directory.\r\n\r\n2. Restart Vim. ","first_name":"Takahiro","6":"Takahiro","last_name":"Sasaki","7":"Sasaki","releases":[{"0":"5174","vim_version":"7.0","1":"7.0","script_version":"1.0.0","2":"1.0.0","version_comment":"Initial upload","3":"Initial upload","package":"slashcomment.vim","4":"slashcomment.vim","src_id":"23279","5":"23279","creation_date":"1431774738","6":"1431774738"}]},"5173":{"script_id":"5173","0":"5173","script_name":"systemrdl.vim","1":"systemrdl.vim","script_type":"syntax","2":"syntax","summary":"Syntax highlighting for SystemRDL files","3":"Syntax highlighting for SystemRDL files","description":"Basic syntax highlighting for the SytemRDL language from Accellera (http:\/\/accellera.org\/activities\/working-groups\/systemrdl).","4":"Basic syntax highlighting for the SytemRDL language from Accellera (http:\/\/accellera.org\/activities\/working-groups\/systemrdl).","install_details":"Put this file into ~\/.vim\/syntax or $VIMRUNTIME\/syntax.\r\n\r\nAdd the following to ftdetect or .vimrc:\r\n\r\nautocmd BufRead,BufNewFile *.rdl set filetype=systemrdl\r\n","5":"Put this file into ~\/.vim\/syntax or $VIMRUNTIME\/syntax.\r\n\r\nAdd the following to ftdetect or .vimrc:\r\n\r\nautocmd BufRead,BufNewFile *.rdl set filetype=systemrdl\r\n","first_name":"Manning","6":"Manning","last_name":"Aalsma","7":"Aalsma","releases":[{"0":"5173","vim_version":"7.3","1":"7.3","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"systemrdl.vim","4":"systemrdl.vim","src_id":"23275","5":"23275","creation_date":"1431645380","6":"1431645380"}]},"5172":{"script_id":"5172","0":"5172","script_name":"logsyntax.vim","1":"logsyntax.vim","script_type":"ftplugin","2":"ftplugin","summary":"A simple (web) log file syntax highlighting Vim plugin.","3":"A simple (web) log file syntax highlighting Vim plugin.","description":"A simple (web) log file syntax highlighting Vim plugin.\r\n\r\nSyntax highlights some common HTTP log formats like IIS format, NCSA, W3C extended and will probably work on some custom log formats too throught the magic of regular expressions.\r\n\r\nHighlighted are dates, HTTP verbs, URIs and IP addresses.\r\n\r\nUsage\r\n=====\r\n\r\nInstall using your favorite Vim plugin manager and sit back as it automatically starts syntax highlighting any file with the .log extension.","4":"A simple (web) log file syntax highlighting Vim plugin.\r\n\r\nSyntax highlights some common HTTP log formats like IIS format, NCSA, W3C extended and will probably work on some custom log formats too throught the magic of regular expressions.\r\n\r\nHighlighted are dates, HTTP verbs, URIs and IP addresses.\r\n\r\nUsage\r\n=====\r\n\r\nInstall using your favorite Vim plugin manager and sit back as it automatically starts syntax highlighting any file with the .log extension.","install_details":"Extract the archive to ~\/.vim on Linux\/MacOSX or $HOME\\vimfiles on Windows. ","5":"Extract the archive to ~\/.vim on Linux\/MacOSX or $HOME\\vimfiles on Windows. ","first_name":"J","6":"J","last_name":"Baute","7":"Baute","releases":[{"0":"5172","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"logsyntax.vim.zip","4":"logsyntax.vim.zip","src_id":"23274","5":"23274","creation_date":"1431614617","6":"1431614617"}]},"5171":{"script_id":"5171","0":"5171","script_name":"liblognorm.vim","1":"liblognorm.vim","script_type":"syntax","2":"syntax","summary":"Syntax definition for liblognorm rules files","3":"Syntax definition for liblognorm rules files","description":"Liblognorm (http:\/\/www.liblognorm.com\/) is a log normalization library, converting flat text to structured data according to provided rules.\r\nThis script adds syntax highlighting for rule files.\r\n","4":"Liblognorm (http:\/\/www.liblognorm.com\/) is a log normalization library, converting flat text to structured data according to provided rules.\r\nThis script adds syntax highlighting for rule files.\r\n","install_details":"","5":"","first_name":"Stanislaw","6":"Stanislaw","last_name":"Klekot","7":"Klekot","releases":[{"0":"5171","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"liblognorm.vim","4":"liblognorm.vim","src_id":"23273","5":"23273","creation_date":"1431612974","6":"1431612974"}]},"5170":{"script_id":"5170","0":"5170","script_name":"oasisprj.vim","1":"oasisprj.vim","script_type":"syntax","2":"syntax","summary":"syntax highlighting for _oasis files","3":"syntax highlighting for _oasis files","description":"Simple syntax highlighting for the OASIS build tool for Ocaml (http:\/\/oasis.forge.ocamlcore.org\/)","4":"Simple syntax highlighting for the OASIS build tool for Ocaml (http:\/\/oasis.forge.ocamlcore.org\/)","install_details":"Copy this file to ~\/.vim\/syntax or $VIMRUNTIME\/syntax \r\nAdd \"au BufNewFile,BufRead _oasis    setf oasisprj\" to your ftdetect script.","5":"Copy this file to ~\/.vim\/syntax or $VIMRUNTIME\/syntax \r\nAdd \"au BufNewFile,BufRead _oasis    setf oasisprj\" to your ftdetect script.","first_name":"Juan","6":"Juan","last_name":"Chanco","7":"Chanco","releases":[{"0":"5170","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"oasisprj.vim","4":"oasisprj.vim","src_id":"23272","5":"23272","creation_date":"1431569482","6":"1431569482"}]},"5169":{"script_id":"5169","0":"5169","script_name":"erlang_spec.vim","1":"erlang_spec.vim","script_type":"utility","2":"utility","summary":"Generate specifications for your Erlang functions","3":"Generate specifications for your Erlang functions","description":"When you are inside the function, call `:ErlangSpec` and this script will\r\nproduce specification for it. It won't fill in the argument types for you,\r\nthough.","4":"When you are inside the function, call `:ErlangSpec` and this script will\r\nproduce specification for it. It won't fill in the argument types for you,\r\nthough.","install_details":"Add a mapping to your ~\/.vimrc (change the key to suit your taste):\r\n\r\n    nnoremap s :ErlangSpec\r\n\r\nMore: https:\/\/github.com\/akalyaev\/vim-erlang-spec","5":"Add a mapping to your ~\/.vimrc (change the key to suit your taste):\r\n\r\n    nnoremap s :ErlangSpec\r\n\r\nMore: https:\/\/github.com\/akalyaev\/vim-erlang-spec","first_name":"Anton","6":"Anton","last_name":"Kaliaev","7":"Kaliaev","releases":[{"0":"5169","vim_version":"7.0","1":"7.0","script_version":"0.2.1","2":"0.2.1","version_comment":"Initial upload","3":"Initial upload","package":"erlang_spec.vim","4":"erlang_spec.vim","src_id":"23264","5":"23264","creation_date":"1430942638","6":"1430942638"}]},"5168":{"script_id":"5168","0":"5168","script_name":"vim-radioss","1":"vim-radioss","script_type":"ftplugin","2":"ftplugin","summary":"VIM filetype plugin for Radioss","3":"VIM filetype plugin for Radioss","description":"VIM filetype plugin for Radioss FE solver. \r\n\r\nMain plugin features: \r\n- syntax highlighting \r\n- node\/element table folding \r\n- keyword library \r\n- function commands \r\n- many others useful features ","4":"VIM filetype plugin for Radioss FE solver. \r\n\r\nMain plugin features: \r\n- syntax highlighting \r\n- node\/element table folding \r\n- keyword library \r\n- function commands \r\n- many others useful features ","install_details":"https:\/\/github.com\/gradzikb\/vim-radioss","5":"https:\/\/github.com\/gradzikb\/vim-radioss","first_name":"Bartosz","6":"Bartosz","last_name":"Gradzik","7":"Gradzik","releases":[{"0":"5168","vim_version":"7.4","1":"7.4","script_version":"1.0.0","2":"1.0.0","version_comment":"Initial upload","3":"Initial upload","package":"vim-radioss-1.0.0.zip","4":"vim-radioss-1.0.0.zip","src_id":"23262","5":"23262","creation_date":"1430905068","6":"1430905068"}]},"5167":{"script_id":"5167","0":"5167","script_name":"greekde_utf-8.vim","1":"greekde_utf-8.vim","script_type":"utility","2":"utility","summary":"Keymap for Unicode polytonic Greek, for the German QWERTZ keyboard","3":"Keymap for Unicode polytonic Greek, for the German QWERTZ keyboard","description":"The purpose of this Keymap is to make polytonic Greek characters easy to enter on the\r\nGerman QWERTZ keyboard.  (Most importantly, this Keymap does not use keys that are\r\n'dead keys' on the German keyboard, and that are therefore hard to use for other purposes,\r\nsuch as the tilde, acute\/grave\/backquote, and caret keys.  It also avoids the awkward AltGr\r\nkey combinations.)\r\n\r\nThe file contains only a simple straightforward keymap mapping, without any further\r\n\"intelligence\" such as functions or such.  The keymap can (and should) be used without\r\nchanging the keyboard layout.\r\n\r\nFor the Greek diacritics, this keymap uses the number keys.  On the German keyboard,\r\nthe row of number keys above the letter keys is labeled as follows (where the glyph on\r\nthe left of the key is the value with shift pressed):\r\n\r\n      [!1] [\"2] [ 3] [ 4] [ 5] [&6] [\/7] [(8] [)9] [=0]\r\n\r\nThe accents and breathings are created by pressing the UNSHIFTED number key whose shifted\r\nvalue on the QWERTZ keyboard suggests the diacritic.  The full set of diacritic keys is\r\nas follows:\r\n\r\n      Key        Shift      Creates\r\n                 pressed\r\n      ! 1         No        Tonos         (modern accent)\r\n      \" 2         No        Dialytika     (diaeresis, trema)\r\n      & 6         No        Varia         (grave accent)\r\n      \/ 7         No        Oxia          (acute accent)\r\n      ( 8         No        Psili         (rough breathing)\r\n      ) 9         No        Dasia         (smooth breathing)\r\n      = 0         No        Perispomeni   (circumflex accent)\r\n      underscore  Yes       Ypogegrammeni (iota subscript)\r\n\r\nThe rules for the ORDER of keystrokes in a letter with multiple diacritics are:\r\nThe breathing precedes the letter, and everything else follows the letter.\r\nIota-subscript (Ypogegrammeni) and diaeresis (Dialytika) are always typed last.\r\n\r\nExamples:\r\n\r\n      Typing e7    i.e. [e] [\/7]           produces Epsilon with acute\r\n      Typing 9a    i.e. [)9] [a]           produces Alpha with smooth breathing\r\n      Typing 8h0_  i.e. [(8] [h] [=0] [_]  produces Eta with rough breathing, circumflex, and iota subscript.\r\n\r\nThe keymap file begins with a comment section explaining in more detail how to type the\r\naccented Greek characters.\r\n\r\n\r\n","4":"The purpose of this Keymap is to make polytonic Greek characters easy to enter on the\r\nGerman QWERTZ keyboard.  (Most importantly, this Keymap does not use keys that are\r\n'dead keys' on the German keyboard, and that are therefore hard to use for other purposes,\r\nsuch as the tilde, acute\/grave\/backquote, and caret keys.  It also avoids the awkward AltGr\r\nkey combinations.)\r\n\r\nThe file contains only a simple straightforward keymap mapping, without any further\r\n\"intelligence\" such as functions or such.  The keymap can (and should) be used without\r\nchanging the keyboard layout.\r\n\r\nFor the Greek diacritics, this keymap uses the number keys.  On the German keyboard,\r\nthe row of number keys above the letter keys is labeled as follows (where the glyph on\r\nthe left of the key is the value with shift pressed):\r\n\r\n      [!1] [\"2] [ 3] [ 4] [ 5] [&6] [\/7] [(8] [)9] [=0]\r\n\r\nThe accents and breathings are created by pressing the UNSHIFTED number key whose shifted\r\nvalue on the QWERTZ keyboard suggests the diacritic.  The full set of diacritic keys is\r\nas follows:\r\n\r\n      Key        Shift      Creates\r\n                 pressed\r\n      ! 1         No        Tonos         (modern accent)\r\n      \" 2         No        Dialytika     (diaeresis, trema)\r\n      & 6         No        Varia         (grave accent)\r\n      \/ 7         No        Oxia          (acute accent)\r\n      ( 8         No        Psili         (rough breathing)\r\n      ) 9         No        Dasia         (smooth breathing)\r\n      = 0         No        Perispomeni   (circumflex accent)\r\n      underscore  Yes       Ypogegrammeni (iota subscript)\r\n\r\nThe rules for the ORDER of keystrokes in a letter with multiple diacritics are:\r\nThe breathing precedes the letter, and everything else follows the letter.\r\nIota-subscript (Ypogegrammeni) and diaeresis (Dialytika) are always typed last.\r\n\r\nExamples:\r\n\r\n      Typing e7    i.e. [e] [\/7]           produces Epsilon with acute\r\n      Typing 9a    i.e. [)9] [a]           produces Alpha with smooth breathing\r\n      Typing 8h0_  i.e. [(8] [h] [=0] [_]  produces Eta with rough breathing, circumflex, and iota subscript.\r\n\r\nThe keymap file begins with a comment section explaining in more detail how to type the\r\naccented Greek characters.\r\n\r\n\r\n","install_details":"The keymap file should have the name greekde_utf-8.vim.\r\nCopy the file to ~\/.vim\/keymap\/ (create the subdir if it doesn't exist yet).\r\n\r\nIn your ~\/.vimrc file, add the following lines:\r\n\r\n  set keymap=greekde   \" Specifies the Keymap file\r\n  map!        \" F2 to change between Greek and normal (Keymap on\/off)\r\n  set iminsert=0       \" Start with keymap off\r\n  set imsearch=-1      \" Keymap mode synchronized in Search and in main edit window\r\n  set timeout timeoutlen=3000 ttimeoutlen=100   \" More time for typing\r\n\r\nThe F2 key is mapped to produce the command Ctrl-^ which switches keymaps.  This is\r\nbecause on the German keyboard, typing Ctrl-^ may be difficult because it is typically\r\nconfigured as a \"dead key\".\r\n\r\n","5":"The keymap file should have the name greekde_utf-8.vim.\r\nCopy the file to ~\/.vim\/keymap\/ (create the subdir if it doesn't exist yet).\r\n\r\nIn your ~\/.vimrc file, add the following lines:\r\n\r\n  set keymap=greekde   \" Specifies the Keymap file\r\n  map!        \" F2 to change between Greek and normal (Keymap on\/off)\r\n  set iminsert=0       \" Start with keymap off\r\n  set imsearch=-1      \" Keymap mode synchronized in Search and in main edit window\r\n  set timeout timeoutlen=3000 ttimeoutlen=100   \" More time for typing\r\n\r\nThe F2 key is mapped to produce the command Ctrl-^ which switches keymaps.  This is\r\nbecause on the German keyboard, typing Ctrl-^ may be difficult because it is typically\r\nconfigured as a \"dead key\".\r\n\r\n","first_name":"Menno","6":"Menno","last_name":"Rubingh","7":"Rubingh","releases":[{"0":"5167","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"greekde_utf-8.vim","4":"greekde_utf-8.vim","src_id":"23261","5":"23261","creation_date":"1430903407","6":"1430903407"}]},"5166":{"script_id":"5166","0":"5166","script_name":"foldMarker.vim","1":"foldMarker.vim","script_type":"utility","2":"utility","summary":"Creat fold marker and adjust fold level with a new command ':FoldMarker'","3":"Creat fold marker and adjust fold level with a new command ':FoldMarker'","description":"foldMarker.vim defines a new command `:FoldMarker`, which can accpet six arguments to creat fold marker and adjust fold level.\r\n\r\n*   `l`: creat a pair of fold markers under cursor `Line`\r\n*   `a`: creat a pair of fold markers `Above` fold area\r\n*   `b`: creat a pair of fold markers `Below` fold area\r\n*   `s`: creat a pair of fold markers `Surrounding` Visual area\r\n*   `c`: `Creat` fold level\r\n*   `d`: `Delete` fold level\r\n\r\nDownload the plugin from GitHub Repository:\r\n\r\nhttps:\/\/github.com\/Bozar\/foldMarker","4":"foldMarker.vim defines a new command `:FoldMarker`, which can accpet six arguments to creat fold marker and adjust fold level.\r\n\r\n*   `l`: creat a pair of fold markers under cursor `Line`\r\n*   `a`: creat a pair of fold markers `Above` fold area\r\n*   `b`: creat a pair of fold markers `Below` fold area\r\n*   `s`: creat a pair of fold markers `Surrounding` Visual area\r\n*   `c`: `Creat` fold level\r\n*   `d`: `Delete` fold level\r\n\r\nDownload the plugin from GitHub Repository:\r\n\r\nhttps:\/\/github.com\/Bozar\/foldMarker","install_details":"Copy the following two files to `~\/.vim\/`(`vimfiles\/` for Windows users) :\r\n\r\n    autoload\/moveCursor.vim\r\n    plugin\/foldMarker.vim\r\n\r\nPlease be sure the plugin will not overwrite existing files.\r\n\r\nRestart Vim.","5":"Copy the following two files to `~\/.vim\/`(`vimfiles\/` for Windows users) :\r\n\r\n    autoload\/moveCursor.vim\r\n    plugin\/foldMarker.vim\r\n\r\nPlease be sure the plugin will not overwrite existing files.\r\n\r\nRestart Vim.","first_name":"Tommy","6":"Tommy","last_name":"Chen","7":"Chen","releases":[{"0":"5166","vim_version":"7.4","1":"7.4","script_version":"1.1.0","2":"1.1.0","version_comment":"*   1.1.0\r\n    +   Fix: Change search pattern for script variable `s:FoldEnd`, so that the plugin can recognize fold markers such as `[[[`\r\n    +   Add: Add 8 new arguments, L\/A\/B\/S\/C\/r\/R\/h\r\n    +   Add: Add a global variable `g:MoveFold_FoldMarker` to move new fold marker\r\n    +   Add: Let `:FoldMarker` accpet more ranges besides `'<` and `'>`, such as `:1,5FoldMarker`\r\n","3":"*   1.1.0\r\n    +   Fix: Change search pattern for script variable `s:FoldEnd`, so that the plugin can recognize fold markers such as `[[[`\r\n    +   Add: Add 8 new arguments, L\/A\/B\/S\/C\/r\/R\/h\r\n    +   Add: Add a global variable `g:MoveFold_FoldMarker` to move new fold marker\r\n    +   Add: Let `:FoldMarker` accpet more ranges besides `'<` and `'>`, such as `:1,5FoldMarker`\r\n","package":"foldMarker.tar.gz","4":"foldMarker.tar.gz","src_id":"23278","5":"23278","creation_date":"1431749663","6":"1431749663"},{"0":"5166","vim_version":"7.0","1":"7.0","script_version":"1.0.0","2":"1.0.0","version_comment":"Initial upload","3":"Initial upload","package":"foldMarker.tar.gz","4":"foldMarker.tar.gz","src_id":"23252","5":"23252","creation_date":"1430492677","6":"1430492677"}]},"5165":{"script_id":"5165","0":"5165","script_name":"MapToSideEffects","1":"MapToSideEffects","script_type":"utility","2":"utility","summary":"Create mappings to function side effects","3":"Create mappings to function side effects","description":"This plugin helps to fool Vim into mapping key sequences in Normal,\r\nVisual\/Select, and Operator-pending modes to function side effects.\r\n\r\n## User interface (API)\r\n\r\nThis plugins supports 4 *kinds* of *actions*:\r\n\r\n* `Idempotent` -- actions that take no arguments and cannot be\r\n  meaningfully repeated more than once,\r\n* `Repeatable` -- actions that take no arguments but can be\r\n  meaningfully repeated a number of times,\r\n* `WithCount`  -- actions that take a `count`-type argument,\r\n* `WithCount1` -- actions that take a `count1`-type argument.\r\n\r\n*Action* here means a *VimL* function called for its side effects.\r\n\r\n### Registering actions and creating mappings\r\n\r\nThe following functions create mappings of a key sequence of the form\r\n`()` to the side effects of the given action in requested\r\nmodes.\r\n\r\n* `mapToSideEffects#SetUpIdempotent(action[, options])`\r\n  -- set up a mapping of a key sequence of the form `()` to\r\n  the side effects of a user provided `Idempotent` action, return the\r\n  generated ID number,\r\n\r\n* `mapToSideEffects#SetUpRepeatable(action[, options])`\r\n  -- set up a mapping of a key sequence of the form `()` to\r\n  the side effects of a user provided `Repeatable` action, return the\r\n  generated ID number,\r\n\r\n* `mapToSideEffects#SetUpWithCount(action[, options])`\r\n  -- set up a mapping of a key sequence of the form `()` to\r\n  the side effects of a user provided `WithCount` action, return the\r\n  generated ID number,\r\n\r\n* `mapToSideEffects#SetUpWithCount1(action[, options])`\r\n  -- set up a mapping of a key sequence of the form `()` to\r\n  the side effects of a user provided `WithCount1` action, return the\r\n  generated ID number,\r\n\r\nThe optional `options` argument of these functions must be a\r\ndictionary which can contain two keys: `'modes'` and `'name'`.\r\n\r\nThe `modes` option, if provided, has to be a string containing only\r\nletters `n`, `v`, `x`, `s`, `o`.  If it is omitted, it is assumed to be\r\n`'nvo'`.\r\n\r\nThe `name` option, if provided, has to be a string matching the regex\r\n`'^[-_.:[:alnum:]]\\{1,45}$'` and not beginning with `MapToSideEffects-`\r\nin any character case, and the user must ensure that the key sequence\r\n`()` has not yet been used as a mapping source.  If the\r\n`name` option is omitted, the `name` is taken to be\r\n`'MapToSideEffects-'`, where `` is the generated numerical ID.\r\n\r\nName collisions may be avoided as follows, for example:\r\n\r\n(a) start names with \"`-`\" in plugins and with a dash \"`-`\"\r\n  in user scripts, or\r\n\r\n(b) do not provide custom names, use automatic names of the form\r\n  \"`MapToSideEffects-`.\"\r\n\r\n### Unregistering actions and removing mappings\r\n\r\nThe following functions unregister one or several previously registered\r\nactions and clear the corresponding mappings.\r\n\r\n* `mapToSideEffects#ClearOne(id)`\r\n  -- remove the mapping and the data associated with the given ID number,\r\n\r\n* `mapToSideEffects#ClearOneByName(name)`\r\n  -- remove the mapping and the data associated with the given name,\r\n\r\n* `mapToSideEffects#ClearMultiple(ids)`\r\n  -- remove the mappings and the data associated with the given ID\r\n  numbers,\r\n\r\n* `mapToSideEffects#ClearMultipleByNames(names)`\r\n  -- remove the mappings and the data associated with the given names,\r\n\r\nThe following function removes all the plugin's data and clears the\r\ncorresponding mappings.\r\n\r\n* `mapToSideEffects#Reset()`\r\n  -- remove all mappings and all data.\r\n\r\n## Usage\r\n\r\nSuppose one wishes to use the key sequence `ekf` in *Normal*,\r\n*Visual*, and *Operator-pending* modes to perform the motion to the\r\nnearest \"end of a keyword,\" as defined by the pattern `'\\>'` in *Vim*, in\r\nthe forward direction and taking into account the `[count]` prefix.\r\nUsing this plugin, this can be achieved as follows, for example.\r\n\r\n1. Define a function `s:ToEndOfKeywordForward` with desired side effects\r\n  that takes a positive integer argument `count1`:\r\n\r\n      function s:ToEndOfKeywordForward(count1)\r\n        let l:count1 = a:count1\r\n        while l:count1 > 0\r\n          call search('\\>', 'W')\r\n          let l:count1 -= 1\r\n        endwhile\r\n      endfunction\r\n\r\n\r\n2. Creates a mapping of `(-GoToEndOfKeywordForward)` to the side\r\n  effects of `s:ToEndOfKeywordForward` function in *Normal*, *Visual*,\r\n  and *Operator-pending* modes:\r\n\r\n      call mapToSideEffects#SetUpWithCount1(\r\n            \\   function('s:ToEndOfKeywordForward'),\r\n            \\   {'name' : '-GoToEndOfKeywordForward', 'modes' : 'nxo'} )\r\n\r\n\r\n3. Create desired custom mappings to `(-GoToEndOfKeywordForward)`:\r\n\r\n      nmap ekf (-GoToEndOfKeywordForward)\r\n      xmap ekf (-GoToEndOfKeywordForward)\r\n      omap ekf (-GoToEndOfKeywordForward)\r\n\r\n\r\nGitHub page: https:\/\/github.com\/alexeymuranov\/vim-MapToSideEffects","4":"This plugin helps to fool Vim into mapping key sequences in Normal,\r\nVisual\/Select, and Operator-pending modes to function side effects.\r\n\r\n## User interface (API)\r\n\r\nThis plugins supports 4 *kinds* of *actions*:\r\n\r\n* `Idempotent` -- actions that take no arguments and cannot be\r\n  meaningfully repeated more than once,\r\n* `Repeatable` -- actions that take no arguments but can be\r\n  meaningfully repeated a number of times,\r\n* `WithCount`  -- actions that take a `count`-type argument,\r\n* `WithCount1` -- actions that take a `count1`-type argument.\r\n\r\n*Action* here means a *VimL* function called for its side effects.\r\n\r\n### Registering actions and creating mappings\r\n\r\nThe following functions create mappings of a key sequence of the form\r\n`()` to the side effects of the given action in requested\r\nmodes.\r\n\r\n* `mapToSideEffects#SetUpIdempotent(action[, options])`\r\n  -- set up a mapping of a key sequence of the form `()` to\r\n  the side effects of a user provided `Idempotent` action, return the\r\n  generated ID number,\r\n\r\n* `mapToSideEffects#SetUpRepeatable(action[, options])`\r\n  -- set up a mapping of a key sequence of the form `()` to\r\n  the side effects of a user provided `Repeatable` action, return the\r\n  generated ID number,\r\n\r\n* `mapToSideEffects#SetUpWithCount(action[, options])`\r\n  -- set up a mapping of a key sequence of the form `()` to\r\n  the side effects of a user provided `WithCount` action, return the\r\n  generated ID number,\r\n\r\n* `mapToSideEffects#SetUpWithCount1(action[, options])`\r\n  -- set up a mapping of a key sequence of the form `()` to\r\n  the side effects of a user provided `WithCount1` action, return the\r\n  generated ID number,\r\n\r\nThe optional `options` argument of these functions must be a\r\ndictionary which can contain two keys: `'modes'` and `'name'`.\r\n\r\nThe `modes` option, if provided, has to be a string containing only\r\nletters `n`, `v`, `x`, `s`, `o`.  If it is omitted, it is assumed to be\r\n`'nvo'`.\r\n\r\nThe `name` option, if provided, has to be a string matching the regex\r\n`'^[-_.:[:alnum:]]\\{1,45}$'` and not beginning with `MapToSideEffects-`\r\nin any character case, and the user must ensure that the key sequence\r\n`()` has not yet been used as a mapping source.  If the\r\n`name` option is omitted, the `name` is taken to be\r\n`'MapToSideEffects-'`, where `` is the generated numerical ID.\r\n\r\nName collisions may be avoided as follows, for example:\r\n\r\n(a) start names with \"`-`\" in plugins and with a dash \"`-`\"\r\n  in user scripts, or\r\n\r\n(b) do not provide custom names, use automatic names of the form\r\n  \"`MapToSideEffects-`.\"\r\n\r\n### Unregistering actions and removing mappings\r\n\r\nThe following functions unregister one or several previously registered\r\nactions and clear the corresponding mappings.\r\n\r\n* `mapToSideEffects#ClearOne(id)`\r\n  -- remove the mapping and the data associated with the given ID number,\r\n\r\n* `mapToSideEffects#ClearOneByName(name)`\r\n  -- remove the mapping and the data associated with the given name,\r\n\r\n* `mapToSideEffects#ClearMultiple(ids)`\r\n  -- remove the mappings and the data associated with the given ID\r\n  numbers,\r\n\r\n* `mapToSideEffects#ClearMultipleByNames(names)`\r\n  -- remove the mappings and the data associated with the given names,\r\n\r\nThe following function removes all the plugin's data and clears the\r\ncorresponding mappings.\r\n\r\n* `mapToSideEffects#Reset()`\r\n  -- remove all mappings and all data.\r\n\r\n## Usage\r\n\r\nSuppose one wishes to use the key sequence `ekf` in *Normal*,\r\n*Visual*, and *Operator-pending* modes to perform the motion to the\r\nnearest \"end of a keyword,\" as defined by the pattern `'\\>'` in *Vim*, in\r\nthe forward direction and taking into account the `[count]` prefix.\r\nUsing this plugin, this can be achieved as follows, for example.\r\n\r\n1. Define a function `s:ToEndOfKeywordForward` with desired side effects\r\n  that takes a positive integer argument `count1`:\r\n\r\n      function s:ToEndOfKeywordForward(count1)\r\n        let l:count1 = a:count1\r\n        while l:count1 > 0\r\n          call search('\\>', 'W')\r\n          let l:count1 -= 1\r\n        endwhile\r\n      endfunction\r\n\r\n\r\n2. Creates a mapping of `(-GoToEndOfKeywordForward)` to the side\r\n  effects of `s:ToEndOfKeywordForward` function in *Normal*, *Visual*,\r\n  and *Operator-pending* modes:\r\n\r\n      call mapToSideEffects#SetUpWithCount1(\r\n            \\   function('s:ToEndOfKeywordForward'),\r\n            \\   {'name' : '-GoToEndOfKeywordForward', 'modes' : 'nxo'} )\r\n\r\n\r\n3. Create desired custom mappings to `(-GoToEndOfKeywordForward)`:\r\n\r\n      nmap ekf (-GoToEndOfKeywordForward)\r\n      xmap ekf (-GoToEndOfKeywordForward)\r\n      omap ekf (-GoToEndOfKeywordForward)\r\n\r\n\r\nGitHub page: https:\/\/github.com\/alexeymuranov\/vim-MapToSideEffects","install_details":"Install normally.","5":"Install normally.","first_name":"Alexey","6":"Alexey","last_name":"Muranov","7":"Muranov","releases":[{"0":"5165","vim_version":"7.4","1":"7.4","script_version":"0.1.0","2":"0.1.0","version_comment":"Fix typos in comments and README","3":"Fix typos in comments and README","package":"MapToSideEffects-0.1.0.tar.gz","4":"MapToSideEffects-0.1.0.tar.gz","src_id":"23251","5":"23251","creation_date":"1430471320","6":"1430471320"}]},"5164":{"script_id":"5164","0":"5164","script_name":"avrm48.vim","1":"avrm48.vim","script_type":"syntax","2":"syntax","summary":"AVR Mega48 Syntax script","3":"AVR Mega48 Syntax script","description":"Syntax highlighting for Atmel AVR Mega48 MCU","4":"Syntax highlighting for Atmel AVR Mega48 MCU","install_details":"copy File to folder ~\/.vim\/syntax","5":"copy File to folder ~\/.vim\/syntax","first_name":"Alfred","6":"Alfred","last_name":"Hell","7":"Hell","releases":[{"0":"5164","vim_version":"7.0","1":"7.0","script_version":"0.31","2":"0.31","version_comment":"Bugfix (UPM PCINT)","3":"Bugfix (UPM PCINT)","package":"avrm48.vim","4":"avrm48.vim","src_id":"24808","5":"24808","creation_date":"1482252623","6":"1482252623"},{"0":"5164","vim_version":"7.0","1":"7.0","script_version":"0.3","2":"0.3","version_comment":"Added Keywords XYZ(+-)","3":"Added Keywords XYZ(+-)","package":"avrm48.vim","4":"avrm48.vim","src_id":"24798","5":"24798","creation_date":"1481457103","6":"1481457103"},{"0":"5164","vim_version":"7.0","1":"7.0","script_version":"0.2","2":"0.2","version_comment":"Initial upload","3":"Initial upload","package":"avrm48.vim","4":"avrm48.vim","src_id":"23244","5":"23244","creation_date":"1430412725","6":"1430412725"}]},"5163":{"script_id":"5163","0":"5163","script_name":"mpi.vim","1":"mpi.vim","script_type":"syntax","2":"syntax","summary":"Syntax highlight, matching rules and mappings for the mpi","3":"Syntax highlight, matching rules and mappings for the mpi","description":"Now the plugin has full support of MPI 2.2 with C, C++ and Fortran bingding, Golang binding is on the way.\r\n\r\nPlease go to github for the latest version.\r\nhttps:\/\/github.com\/jiangxincode\/mpi.vim\r\n\r\nIf you have some advises, please tell me, open a issue, give me a pull request, or send me a email.\r\n\r\nHava a good time on MPI.\r\n\r\n\r\n","4":"Now the plugin has full support of MPI 2.2 with C, C++ and Fortran bingding, Golang binding is on the way.\r\n\r\nPlease go to github for the latest version.\r\nhttps:\/\/github.com\/jiangxincode\/mpi.vim\r\n\r\nIf you have some advises, please tell me, open a issue, give me a pull request, or send me a email.\r\n\r\nHava a good time on MPI.\r\n\r\n\r\n","install_details":"If you use Vundle,add the following line to your ~\/.vimrc:\r\n\r\nPlugin 'jiangxincode\/mpi.vim'\r\n\r\nThen run inside Vim:\r\n\r\n:so ~\/.vimrc\r\n:PluginInstall\r\n\r\nIf you use Pathogen, do this:\r\n\r\ncd ~\/.vim\/bundle\r\ngit clone https:\/\/github.com\/jiangxincode\/mpi.vim.git\r\n\r\nIf you are not using any package manager, download the tarball and this:\r\n\r\ntar -zxvf after.tar.gz\r\nmv after .vim\/","5":"If you use Vundle,add the following line to your ~\/.vimrc:\r\n\r\nPlugin 'jiangxincode\/mpi.vim'\r\n\r\nThen run inside Vim:\r\n\r\n:so ~\/.vimrc\r\n:PluginInstall\r\n\r\nIf you use Pathogen, do this:\r\n\r\ncd ~\/.vim\/bundle\r\ngit clone https:\/\/github.com\/jiangxincode\/mpi.vim.git\r\n\r\nIf you are not using any package manager, download the tarball and this:\r\n\r\ntar -zxvf after.tar.gz\r\nmv after .vim\/","first_name":"Jiang","6":"Jiang","last_name":"Xin","7":"Xin","releases":[{"0":"5163","vim_version":"5.7","1":"5.7","script_version":"0.10","2":"0.10","version_comment":"Initial upload","3":"Initial upload","package":"after.tar.gz","4":"after.tar.gz","src_id":"23232","5":"23232","creation_date":"1430211997","6":"1430211997"}]},"5162":{"script_id":"5162","0":"5162","script_name":"vison","1":"vison","script_type":"utility","2":"utility","summary":"Completion JSON files with JSON Schema","3":"Completion JSON files with JSON Schema","description":"Vison is a Vim plugin to help writing `*.json` file with JSON Schema(http:\/\/json-schema.org\/).\r\n\r\nVison provides the following features:\r\n\r\n* Completion keys or values in JSON files\r\n * You can use more than 40 schema files provided JSON Schema Store(http:\/\/schemastore.org\/json\/).\r\n* Manegement JSON schema files.\r\n\r\nIf you want more details, please see the Github repository.\r\nhttps:\/\/github.com\/Quramy\/vison","4":"Vison is a Vim plugin to help writing `*.json` file with JSON Schema(http:\/\/json-schema.org\/).\r\n\r\nVison provides the following features:\r\n\r\n* Completion keys or values in JSON files\r\n * You can use more than 40 schema files provided JSON Schema Store(http:\/\/schemastore.org\/json\/).\r\n* Manegement JSON schema files.\r\n\r\nIf you want more details, please see the Github repository.\r\nhttps:\/\/github.com\/Quramy\/vison","install_details":"This plugins requires:\r\n* Git command\r\n\r\nAnd installation the following plugin are recommended:\r\n* Shougo\/unite.vim(https:\/\/github.com\/Shougo\/unite.vim)\r\n\r\nIf you use NeoBundle, append the following to your .vimrc\r\n\r\n```:vim\r\nNeoBundle 'Shougo\/unite.vim'\r\nNeoBundle 'Quramy\/vison'\r\n```\r\n\r\nAnd execute :NeoBundleInstall.\r\n\r\n\r\nAfter installation, call :VisonSetup command to fetch JSON schema files from Schema Store.","5":"This plugins requires:\r\n* Git command\r\n\r\nAnd installation the following plugin are recommended:\r\n* Shougo\/unite.vim(https:\/\/github.com\/Shougo\/unite.vim)\r\n\r\nIf you use NeoBundle, append the following to your .vimrc\r\n\r\n```:vim\r\nNeoBundle 'Shougo\/unite.vim'\r\nNeoBundle 'Quramy\/vison'\r\n```\r\n\r\nAnd execute :NeoBundleInstall.\r\n\r\n\r\nAfter installation, call :VisonSetup command to fetch JSON schema files from Schema Store.","first_name":"Yosuke","6":"Yosuke","last_name":"Kurami","7":"Kurami","releases":[{"0":"5162","vim_version":"7.0","1":"7.0","script_version":"0.1.1","2":"0.1.1","version_comment":"Initial upload","3":"Initial upload","package":"vison-0.1.1.zip","4":"vison-0.1.1.zip","src_id":"23231","5":"23231","creation_date":"1430161734","6":"1430161734"}]},"5161":{"script_id":"5161","0":"5161","script_name":"yats","1":"yats","script_type":"syntax","2":"syntax","summary":"Yet Another TypeScript Syntax","3":"Yet Another TypeScript Syntax","description":"Yet Another TypeScript Syntax file for Vim, adapted from YAJS. Key differences:\r\n\r\nExuberant Highlighting. The most elaborate or byzatine syntax highlighting for TypeScript.\r\nBundled with snippets for UltiSnips!\r\nBuiltin Support for tagbar!\r\nUse 'typescript' as group name's prefix, not 'typeScript' nor 'TypeScript'. Works great with SyntaxComplete.\r\nInherit Web API and DOM keywords from YAJS\r\nSyntax fold. Fold long code block, semantically!\r\nRemove old, unused syntax definitions.\r\n\r\nGithub Source: https:\/\/github.com\/HerringtonDarkholme\/yats.vim","4":"Yet Another TypeScript Syntax file for Vim, adapted from YAJS. Key differences:\r\n\r\nExuberant Highlighting. The most elaborate or byzatine syntax highlighting for TypeScript.\r\nBundled with snippets for UltiSnips!\r\nBuiltin Support for tagbar!\r\nUse 'typescript' as group name's prefix, not 'typeScript' nor 'TypeScript'. Works great with SyntaxComplete.\r\nInherit Web API and DOM keywords from YAJS\r\nSyntax fold. Fold long code block, semantically!\r\nRemove old, unused syntax definitions.\r\n\r\nGithub Source: https:\/\/github.com\/HerringtonDarkholme\/yats.vim","install_details":"","5":"","first_name":"Herrington","6":"Herrington","last_name":"Dakrholme","7":"Dakrholme","releases":[{"0":"5161","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"yats.vim-master.zip","4":"yats.vim-master.zip","src_id":"23226","5":"23226","creation_date":"1430014583","6":"1430014583"}]},"5160":{"script_id":"5160","0":"5160","script_name":"primary.vim","1":"primary.vim","script_type":"color scheme","2":"color scheme","summary":"Inspired by Google's official colors","3":"Inspired by Google's official colors","description":"Primary is a Vim color scheme based on Google's colors. \r\n\r\nFor SCREENSHOTS (and much more), see \r\nhttps:\/\/github.com\/google\/vim-colorscheme-primary\r\n\r\nPrimary contains settings for both light and dark backgrounds. It's is fun, \r\nvery readable, and Google-inspired.\r\n\r\nThe Gui version uses the exact RGB codes from Google's logo. Primary on a\r\n256-color terminal looks very similar and even 8-color terminals are supported.\r\n\r\nDisclaimer: This is not an official Google product (experimental or otherwise),\r\nit is just code that happens to be owned by Google.","4":"Primary is a Vim color scheme based on Google's colors. \r\n\r\nFor SCREENSHOTS (and much more), see \r\nhttps:\/\/github.com\/google\/vim-colorscheme-primary\r\n\r\nPrimary contains settings for both light and dark backgrounds. It's is fun, \r\nvery readable, and Google-inspired.\r\n\r\nThe Gui version uses the exact RGB codes from Google's logo. Primary on a\r\n256-color terminal looks very similar and even 8-color terminals are supported.\r\n\r\nDisclaimer: This is not an official Google product (experimental or otherwise),\r\nit is just code that happens to be owned by Google.","install_details":"Download primary.vim and copy it into your .vim\/colors directory.\r\n\r\nTo set Primary as your default color scheme, add these lines to your .vimrc\r\nfile:\r\n  syntax enable\r\n  set t_Co=256\r\n  set background=light\r\n  colorscheme primary\r\n\r\nTo use Primary in dark mode, change the third line to  set background=dark.\r\n\r\nFor more options and details, see the documentation in the Git repo: \r\nhttps:\/\/github.com\/google\/vim-colorscheme-primary","5":"Download primary.vim and copy it into your .vim\/colors directory.\r\n\r\nTo set Primary as your default color scheme, add these lines to your .vimrc\r\nfile:\r\n  syntax enable\r\n  set t_Co=256\r\n  set background=light\r\n  colorscheme primary\r\n\r\nTo use Primary in dark mode, change the third line to  set background=dark.\r\n\r\nFor more options and details, see the documentation in the Git repo: \r\nhttps:\/\/github.com\/google\/vim-colorscheme-primary","first_name":"Lisie","6":"Lisie","last_name":"Michel","7":"Michel","releases":[{"0":"5160","vim_version":"7.0","1":"7.0","script_version":"1.2","2":"1.2","version_comment":"Updated colors to match Google's new logo.","3":"Updated colors to match Google's new logo.","package":"primary.vim","4":"primary.vim","src_id":"23583","5":"23583","creation_date":"1441903139","6":"1441903139"},{"0":"5160","vim_version":"7.0","1":"7.0","script_version":"1.1","2":"1.1","version_comment":"Bug fix: Updated black and white color values in 256-color mode so that they are independent of the terminal color settings.","3":"Bug fix: Updated black and white color values in 256-color mode so that they are independent of the terminal color settings.","package":"primary.vim","4":"primary.vim","src_id":"23270","5":"23270","creation_date":"1431384153","6":"1431384153"},{"0":"5160","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"primary.vim","4":"primary.vim","src_id":"23223","5":"23223","creation_date":"1429815399","6":"1429815399"}]},"5159":{"script_id":"5159","0":"5159","script_name":"gcov-marker","1":"gcov-marker","script_type":"utility","2":"utility","summary":"Show Gcov coverage within vim","3":"Show Gcov coverage within vim","description":"This plugin provides a simple way to load and reload gcov files for an open source file. It will highlight the covered and uncovered lines and publish the uncovered lines to the location list.\r\n\r\nIt does not show you detailed information about the coverage at the moment so you do not get detailed information like the number of hits or branches.\r\n\r\nSource is at https:\/\/github.com\/m42e\/vim-gcov-marker","4":"This plugin provides a simple way to load and reload gcov files for an open source file. It will highlight the covered and uncovered lines and publish the uncovered lines to the location list.\r\n\r\nIt does not show you detailed information about the coverage at the moment so you do not get detailed information like the number of hits or branches.\r\n\r\nSource is at https:\/\/github.com\/m42e\/vim-gcov-marker","install_details":"You can use Vundle, vim-plug or similar with \r\n\r\nPlug 'm42e\/vim-gcov-marker'\r\nor\r\nPlugin 'm42e\/vim-gcov-marker'\r\nor\r\nBundle 'm42e\/vim-gcov-marker'\r\n\r\nor download the archive and install by hand.","5":"You can use Vundle, vim-plug or similar with \r\n\r\nPlug 'm42e\/vim-gcov-marker'\r\nor\r\nPlugin 'm42e\/vim-gcov-marker'\r\nor\r\nBundle 'm42e\/vim-gcov-marker'\r\n\r\nor download the archive and install by hand.","first_name":"Matthias","6":"Matthias","last_name":"Bilger","7":"Bilger","releases":[{"0":"5159","vim_version":"7.3","1":"7.3","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"gcov-marker.tar.gz","4":"gcov-marker.tar.gz","src_id":"23206","5":"23206","creation_date":"1429706316","6":"1429706316"}]},"5158":{"script_id":"5158","0":"5158","script_name":"XMLExpander","1":"XMLExpander","script_type":"utility","2":"utility","summary":"XML Pretty Printer","3":"XML Pretty Printer","description":"Getting Started\r\n********************\r\nWith the XMLExpander extension plugin for vim you can make your XML file\r\nclear. The XMLExpander is a pretty printer for XML.\r\n\r\nWhen you have the problem that your xml files are e.g. in one line or have not\r\nclear insertions this plugin could help you. After running the XMLExpander\r\nevery opening and ending tag is in one line and have clear insertions.\r\n\r\nFirst install the plugin: |xmlexpander-install|\r\n\r\nTo run the XMLExpander do the following:\r\n- load the input XML file\r\n- execute the XMLExpander: menu Plugin->XMLExpander \r\n\r\nNow you have a pretty printed XML file (in the same VIM window!).\r\n\r\nFor further details read the vim help file doc\/xmlexpander.txt\r\nor in VIM :help xmlexpander\r\n\r\nWarning:\r\nThe XML File must be syntactical correct! The script do not check this.\r\n\r\n\r\nWhats New\r\n********************\r\nVersion 0.3\r\n- New name: xmlexpander\r\n- Redefine functions and variables (xmlexpander)\r\n- New function xmlexpander#isContentText(text) to check if a text has to be harmonized","4":"Getting Started\r\n********************\r\nWith the XMLExpander extension plugin for vim you can make your XML file\r\nclear. The XMLExpander is a pretty printer for XML.\r\n\r\nWhen you have the problem that your xml files are e.g. in one line or have not\r\nclear insertions this plugin could help you. After running the XMLExpander\r\nevery opening and ending tag is in one line and have clear insertions.\r\n\r\nFirst install the plugin: |xmlexpander-install|\r\n\r\nTo run the XMLExpander do the following:\r\n- load the input XML file\r\n- execute the XMLExpander: menu Plugin->XMLExpander \r\n\r\nNow you have a pretty printed XML file (in the same VIM window!).\r\n\r\nFor further details read the vim help file doc\/xmlexpander.txt\r\nor in VIM :help xmlexpander\r\n\r\nWarning:\r\nThe XML File must be syntactical correct! The script do not check this.\r\n\r\n\r\nWhats New\r\n********************\r\nVersion 0.3\r\n- New name: xmlexpander\r\n- Redefine functions and variables (xmlexpander)\r\n- New function xmlexpander#isContentText(text) to check if a text has to be harmonized","install_details":"VIMBALL\r\n*************\r\nDownload the vimball file xmlexpander.vmb from:\r\nhttp:\/\/www.vim.org\/\r\n\r\nInstall the vimball file with VIM\r\n1 Download the file xmlexpander.vmb\r\n2 vim path\/xmlexpander.vmb\r\n3 :so %\r\n4 :q\r\n\r\nNow you have the menu Plugin->XMLExpander \r\n\r\nHELP FILE\r\n****************\r\nTo activate the helpfile in VIM type in command mode:\r\n :helptags ~\/.vim\/doc\r\n OR (Windows)\r\n :helptags C:\\Users\\YourUsername\\vimfiles\\doc\r\n\r\nThen you can open the helpfile with ':help xmlexpander'\r\n\r\nGITHUB\r\n*************\r\nGITHUB Repository:\r\nhttps:\/\/github.com\/Data-Statiker\/VIM-XML\r\n\r\nWhen you have the files from GITHUB:\r\nCopy the files of the folders 'autoload', 'doc' and 'plugin' to your\r\nlocal vimfiles:\r\n ~\/.vim\/doc\r\n OR (Windows)\r\n C:\\Users\\YourUsername\\vimfiles\\doc","5":"VIMBALL\r\n*************\r\nDownload the vimball file xmlexpander.vmb from:\r\nhttp:\/\/www.vim.org\/\r\n\r\nInstall the vimball file with VIM\r\n1 Download the file xmlexpander.vmb\r\n2 vim path\/xmlexpander.vmb\r\n3 :so %\r\n4 :q\r\n\r\nNow you have the menu Plugin->XMLExpander \r\n\r\nHELP FILE\r\n****************\r\nTo activate the helpfile in VIM type in command mode:\r\n :helptags ~\/.vim\/doc\r\n OR (Windows)\r\n :helptags C:\\Users\\YourUsername\\vimfiles\\doc\r\n\r\nThen you can open the helpfile with ':help xmlexpander'\r\n\r\nGITHUB\r\n*************\r\nGITHUB Repository:\r\nhttps:\/\/github.com\/Data-Statiker\/VIM-XML\r\n\r\nWhen you have the files from GITHUB:\r\nCopy the files of the folders 'autoload', 'doc' and 'plugin' to your\r\nlocal vimfiles:\r\n ~\/.vim\/doc\r\n OR (Windows)\r\n C:\\Users\\YourUsername\\vimfiles\\doc","first_name":"Data","6":"Data","last_name":"Statiker","7":"Statiker","releases":[{"0":"5158","vim_version":"7.0","1":"7.0","script_version":"0.3","2":"0.3","version_comment":"Initial upload","3":"Initial upload","package":"xmlexpander.vmb","4":"xmlexpander.vmb","src_id":"23192","5":"23192","creation_date":"1429473584","6":"1429473584"}]},"5157":{"script_id":"5157","0":"5157","script_name":"Treemap","1":"Treemap","script_type":"utility","2":"utility","summary":"Create Treemaps with VIM","3":"Create Treemaps with VIM","description":"Getting Started\r\n********************\r\nWith the treemap extension plugin for vim you can create treemaps with the\r\noutput in a textfile or an imbedded SVG HTML file.\r\n(SLICE and DICE)\r\n\r\n**** NEW: Commands TmOpen and TmClear to open SVG-generated treemaps in the web browser out of VIM ***\r\n\r\nFor further details read the vim help file: \"help treemap\"\r\n\r\nSee screenshots at GITHUB:\r\n- Input File:             https:\/\/github.com\/Data-Statiker\/VIM-TREEMAP\/blob\/master\/screenshots\/inputFile.png\r\n- Treemap Output VIM:     https:\/\/github.com\/Data-Statiker\/VIM-TREEMAP\/blob\/master\/screenshots\/treemapOutputVIM.png\r\n- Treemap Output SVG:     https:\/\/github.com\/Data-Statiker\/VIM-TREEMAP\/blob\/master\/screenshots\/trremapOutputSVG.png\r\n- Treemap SVG in Browser: https:\/\/github.com\/Data-Statiker\/VIM-TREEMAP\/blob\/master\/screenshots\/treemapOpenSVG.png\r\n\r\n\r\nFirst install the plugin: |treemap-install|\r\n\r\nTo start the treemap creation:\r\n- load the inputfile\r\n- set the separator (;|,|\\t|...) in the menu Plugin->Treemap->Separator\r\n  or with the VIM Command :TmSeparator (tr)\r\n- set the output type 'VIM' or 'SVG' in the menu Plugin->Treemap->Output Type\r\n  or with the VIM Command :TmOutput\r\n- Run the treemap script in the menu Plugin->Treemap->Run    \r\n  or with the VIM Command :TmRun\r\n  OR\r\n  call the main function: call treemap#main(output,separator)\r\n  for example: - call treemap#main('VIM','\\t')\r\n               - call treemap#main(g:tmOutput,g:tmSeparator)\r\n \r\nNote:\r\nSet tho option wrap to 'nowrap'\r\n  :set nowrap!\r\nOtherwise the treemap is displayed wrong. You can set this\r\noption also after drawing the treemap!\r\n\r\nNote:                                                        \r\nThe decimal separator for the input file is in every language\r\nthe point \".\"                                                \r\nexamples:   23.1                                        \r\n               1020.23                                       \r\n\r\n\r\nUse commands |TmCreate| and |TmDraw| instead of |TmRun|.\r\n\r\nIf you get an error message you can find help for this error in the help file. Type :help ERROR-ID.\r\nexample: :help E0003\r\n\r\nWhats New\t\t\t\t\t\t\r\n*****************\r\nVersion 1.0:\r\n*       New command TmOpen (Mapping to)\r\n        This command opens a generated SVG\/HTML treemap in a \r\n        web browser\r\n*       Bugfix: Replace $lang with $LANG for compatibility with\r\n        older VIM versions\r\n*       New command TmClear to delete all generated files from TmOpen\r\n        in the $HOME\/treemaps\/ directory\r\n\r\nVersion 0.9.2.1\r\n*       Bugfix TmCreate with other separators than \"\\t\" (tab)\r\n\r\nVersion 0.9.2:\r\n*\tNew Commands TmCreate and TmDraw\r\n\tTo seperate the calculating and drawing of treemap\r\n*\tCreate folders in plugin files for a clear view\r\n\r\nVersion 0.9.1:\r\n*\tAdd corresponding VIM COMMANDS for each menu entry: |treemap-commands|\r\n*\tAdd Mappings for VIM Commands: |treemap-mappings|\r\n*\tSet the default width and height in case of Output Type 'VIM'\r\n        to 70*25","4":"Getting Started\r\n********************\r\nWith the treemap extension plugin for vim you can create treemaps with the\r\noutput in a textfile or an imbedded SVG HTML file.\r\n(SLICE and DICE)\r\n\r\n**** NEW: Commands TmOpen and TmClear to open SVG-generated treemaps in the web browser out of VIM ***\r\n\r\nFor further details read the vim help file: \"help treemap\"\r\n\r\nSee screenshots at GITHUB:\r\n- Input File:             https:\/\/github.com\/Data-Statiker\/VIM-TREEMAP\/blob\/master\/screenshots\/inputFile.png\r\n- Treemap Output VIM:     https:\/\/github.com\/Data-Statiker\/VIM-TREEMAP\/blob\/master\/screenshots\/treemapOutputVIM.png\r\n- Treemap Output SVG:     https:\/\/github.com\/Data-Statiker\/VIM-TREEMAP\/blob\/master\/screenshots\/trremapOutputSVG.png\r\n- Treemap SVG in Browser: https:\/\/github.com\/Data-Statiker\/VIM-TREEMAP\/blob\/master\/screenshots\/treemapOpenSVG.png\r\n\r\n\r\nFirst install the plugin: |treemap-install|\r\n\r\nTo start the treemap creation:\r\n- load the inputfile\r\n- set the separator (;|,|\\t|...) in the menu Plugin->Treemap->Separator\r\n  or with the VIM Command :TmSeparator (tr)\r\n- set the output type 'VIM' or 'SVG' in the menu Plugin->Treemap->Output Type\r\n  or with the VIM Command :TmOutput\r\n- Run the treemap script in the menu Plugin->Treemap->Run    \r\n  or with the VIM Command :TmRun\r\n  OR\r\n  call the main function: call treemap#main(output,separator)\r\n  for example: - call treemap#main('VIM','\\t')\r\n               - call treemap#main(g:tmOutput,g:tmSeparator)\r\n \r\nNote:\r\nSet tho option wrap to 'nowrap'\r\n  :set nowrap!\r\nOtherwise the treemap is displayed wrong. You can set this\r\noption also after drawing the treemap!\r\n\r\nNote:                                                        \r\nThe decimal separator for the input file is in every language\r\nthe point \".\"                                                \r\nexamples:   23.1                                        \r\n               1020.23                                       \r\n\r\n\r\nUse commands |TmCreate| and |TmDraw| instead of |TmRun|.\r\n\r\nIf you get an error message you can find help for this error in the help file. Type :help ERROR-ID.\r\nexample: :help E0003\r\n\r\nWhats New\t\t\t\t\t\t\r\n*****************\r\nVersion 1.0:\r\n*       New command TmOpen (Mapping to)\r\n        This command opens a generated SVG\/HTML treemap in a \r\n        web browser\r\n*       Bugfix: Replace $lang with $LANG for compatibility with\r\n        older VIM versions\r\n*       New command TmClear to delete all generated files from TmOpen\r\n        in the $HOME\/treemaps\/ directory\r\n\r\nVersion 0.9.2.1\r\n*       Bugfix TmCreate with other separators than \"\\t\" (tab)\r\n\r\nVersion 0.9.2:\r\n*\tNew Commands TmCreate and TmDraw\r\n\tTo seperate the calculating and drawing of treemap\r\n*\tCreate folders in plugin files for a clear view\r\n\r\nVersion 0.9.1:\r\n*\tAdd corresponding VIM COMMANDS for each menu entry: |treemap-commands|\r\n*\tAdd Mappings for VIM Commands: |treemap-mappings|\r\n*\tSet the default width and height in case of Output Type 'VIM'\r\n        to 70*25","install_details":"VIMBALL:\r\n******************\r\nDownload the vimball file treemap.vmb from:\r\nhttp:\/\/www.vim.org\/scripts\/script.php?script_id=5157\r\n\r\nInstall the vimball file with VIM \r\n1 Download the file treemap.vmb\r\n2 vim path\/treemap.vmb\r\n3 :so %\r\n4 :q\r\n\r\nNow you have the menu Plugin->Treemap\r\n\r\nGITHUB:\r\n*************\r\nGITHUB Repository:\r\nhttps:\/\/github.com\/Data-Statiker\/VIM-TREEMAP\r\n\r\nWhen you have the files from GITHUB:\r\nCopy the folders 'autoload', 'doc' and 'plugin' to your local vimfiles:\r\n ~\/.vim\/doc\r\n OR (Windows)\r\n C:\\Users\\YourUsername\\vimfiles\\doc\r\n\r\nHELP FILE:\r\n****************\r\nTo activate the helpfile in VIM type in command mode:\r\n :helptags ~\/.vim\/doc\r\n OR (Windows)\r\n :helptags C:\\Users\\YourUsername\\vimfiles\\doc","5":"VIMBALL:\r\n******************\r\nDownload the vimball file treemap.vmb from:\r\nhttp:\/\/www.vim.org\/scripts\/script.php?script_id=5157\r\n\r\nInstall the vimball file with VIM \r\n1 Download the file treemap.vmb\r\n2 vim path\/treemap.vmb\r\n3 :so %\r\n4 :q\r\n\r\nNow you have the menu Plugin->Treemap\r\n\r\nGITHUB:\r\n*************\r\nGITHUB Repository:\r\nhttps:\/\/github.com\/Data-Statiker\/VIM-TREEMAP\r\n\r\nWhen you have the files from GITHUB:\r\nCopy the folders 'autoload', 'doc' and 'plugin' to your local vimfiles:\r\n ~\/.vim\/doc\r\n OR (Windows)\r\n C:\\Users\\YourUsername\\vimfiles\\doc\r\n\r\nHELP FILE:\r\n****************\r\nTo activate the helpfile in VIM type in command mode:\r\n :helptags ~\/.vim\/doc\r\n OR (Windows)\r\n :helptags C:\\Users\\YourUsername\\vimfiles\\doc","first_name":"Data","6":"Data","last_name":"Statiker","7":"Statiker","releases":[{"0":"5157","vim_version":"7.2","1":"7.2","script_version":"1.0","2":"1.0","version_comment":"Version 1.0:\r\n* New command TmOpen (Mapping to)\r\n  This command opens a generated SVG\/HTML treemap in a \r\n  web browser\r\n* Bugfix: Replace $lang with $LANG for compatibility with\r\n  older VIM versions\r\n* New command TmClear to delete all generated files from TmOpen\r\n  in the $HOME\/treemaps\/ directory","3":"Version 1.0:\r\n* New command TmOpen (Mapping to)\r\n  This command opens a generated SVG\/HTML treemap in a \r\n  web browser\r\n* Bugfix: Replace $lang with $LANG for compatibility with\r\n  older VIM versions\r\n* New command TmClear to delete all generated files from TmOpen\r\n  in the $HOME\/treemaps\/ directory","package":"treemap.vmb","4":"treemap.vmb","src_id":"23271","5":"23271","creation_date":"1431465538","6":"1431465538"},{"0":"5157","vim_version":"7.4","1":"7.4","script_version":"0.9.2.1","2":"0.9.2.1","version_comment":"Bugfix TmCreate with other separators than \"\\t\" (tab)","3":"Bugfix TmCreate with other separators than \"\\t\" (tab)","package":"treemap.vmb","4":"treemap.vmb","src_id":"23256","5":"23256","creation_date":"1430670982","6":"1430670982"},{"0":"5157","vim_version":"7.4","1":"7.4","script_version":"0.9.2","2":"0.9.2","version_comment":"Version 0.9.2: \r\n- New Commands TmCreate and TmDraw \r\n  To seperate the calculating and drawing of treemap \r\n- Create folders in plugin files for a clear view \r\nVersion 0.9.1: \r\n- Add corresponding VIM COMMANDS for each menu entry: |treemap-commands| \r\n- Add Mappings for VIM Commands: |treemap-mappings| \r\n- Set the default width and height in case of Output Type 'VIM' to 70*25","3":"Version 0.9.2: \r\n- New Commands TmCreate and TmDraw \r\n  To seperate the calculating and drawing of treemap \r\n- Create folders in plugin files for a clear view \r\nVersion 0.9.1: \r\n- Add corresponding VIM COMMANDS for each menu entry: |treemap-commands| \r\n- Add Mappings for VIM Commands: |treemap-mappings| \r\n- Set the default width and height in case of Output Type 'VIM' to 70*25","package":"treemap.vmb","4":"treemap.vmb","src_id":"23248","5":"23248","creation_date":"1430433219","6":"1430433219"},{"0":"5157","vim_version":"7.0","1":"7.0","script_version":"0.9","2":"0.9","version_comment":"- Give your treemap a name \/ title\r\n- Namespace for global variables: g:tm*\r\n- BugFix: Initialize g:tmMess \/ no error occurs by starting \"print log\" anymore\r\n- Small changes in the help file","3":"- Give your treemap a name \/ title\r\n- Namespace for global variables: g:tm*\r\n- BugFix: Initialize g:tmMess \/ no error occurs by starting \"print log\" anymore\r\n- Small changes in the help file","package":"treemap.vmb","4":"treemap.vmb","src_id":"23221","5":"23221","creation_date":"1429809971","6":"1429809971"},{"0":"5157","vim_version":"7.0","1":"7.0","script_version":"0.8","2":"0.8","version_comment":"Update Version 0.8\r\n- Size of treemap ist now adjustable\r\n- More menu entries\r\n- Update VIM help file\r\n- Check if every unit has only one parent\r\n- Create a log file","3":"Update Version 0.8\r\n- Size of treemap ist now adjustable\r\n- More menu entries\r\n- Update VIM help file\r\n- Check if every unit has only one parent\r\n- Create a log file","package":"treemap.vmb","4":"treemap.vmb","src_id":"23188","5":"23188","creation_date":"1429293210","6":"1429293210"},{"0":"5157","vim_version":"7.4","1":"7.4","script_version":"0.7","2":"0.7","version_comment":"False version number 7.4 in first upload","3":"False version number 7.4 in first upload","package":"treemap.vmb","4":"treemap.vmb","src_id":"23170","5":"23170","creation_date":"1428958439","6":"1428958439"}]},"5156":{"script_id":"5156","0":"5156","script_name":"AtelierEstuary","1":"AtelierEstuary","script_type":"color scheme","2":"color scheme","summary":"Estuary is a yellow\/greenish colorscheme","3":"Estuary is a yellow\/greenish colorscheme","description":"This is one of ten colorschemes that were made with Base16 Builder. For the construction of these colorschemes, Solarized colorscheme stood as a model. Like in Solarized, the colorschemes come in a light \u00e2\u0080\u0093 and in a dark background version. It\u00e2\u0080\u0099s really just variations on the same idea, but each with it\u00e2\u0080\u0099s own color-value relations, interdependent on each other and their base (background-)color.  \r\n\r\nOne can find the demopage for these colorschemes at:\r\nhttp:\/\/atelierbram.github.io\/syntax-highlighting\/atelier-schemes\/ \r\n\r\nDownloads at the GitHub repo: \r\nhttps:\/\/github.com\/atelierbram\/vim-colors_atelier-schemes\r\n\r\nMore information on this particular colorscheme: \r\nhttp:\/\/atelierbram.github.io\/syntax-highlighting\/atelier-schemes\/estuary\r\n\r\nScreenshot dark version: \r\nhttp:\/\/atelierbram.github.io\/syntax-highlighting\/assets\/img\/estuary-dark_vim_640x425.png\r\n\r\nScreenshot light version: \r\nhttp:\/\/atelierbram.github.io\/syntax-highlighting\/assets\/img\/estuary-light_vim_640x425.png","4":"This is one of ten colorschemes that were made with Base16 Builder. For the construction of these colorschemes, Solarized colorscheme stood as a model. Like in Solarized, the colorschemes come in a light \u00e2\u0080\u0093 and in a dark background version. It\u00e2\u0080\u0099s really just variations on the same idea, but each with it\u00e2\u0080\u0099s own color-value relations, interdependent on each other and their base (background-)color.  \r\n\r\nOne can find the demopage for these colorschemes at:\r\nhttp:\/\/atelierbram.github.io\/syntax-highlighting\/atelier-schemes\/ \r\n\r\nDownloads at the GitHub repo: \r\nhttps:\/\/github.com\/atelierbram\/vim-colors_atelier-schemes\r\n\r\nMore information on this particular colorscheme: \r\nhttp:\/\/atelierbram.github.io\/syntax-highlighting\/atelier-schemes\/estuary\r\n\r\nScreenshot dark version: \r\nhttp:\/\/atelierbram.github.io\/syntax-highlighting\/assets\/img\/estuary-dark_vim_640x425.png\r\n\r\nScreenshot light version: \r\nhttp:\/\/atelierbram.github.io\/syntax-highlighting\/assets\/img\/estuary-light_vim_640x425.png","install_details":"Install in ~\/.vim\/colors, or ~\\vimfiles\\colors on Windows. \r\n\r\nor\r\n\r\nPathogen installation (recommended)\r\n\r\n1.  Download and install Tim Pope's Pathogen: https:\/\/github.com\/tpope\/vim-pathogen\r\n\r\n2. download or clone this repo on Github: https:\/\/github.com\/atelierbram\/vim-colors_atelier-schemes\r\n\r\n3.  Next, move or clone the `vim-colors_atelier-schemes` directory so that it is\r\na subdirectory of the `.vim\/bundle` directory.\r\n\r\n$ cd ~\/.vim\/bundle\r\n$ git clone https:\/\/github.com\/atelierbram\/vim-colors_atelier-schemes.git\r\n\r\nTry it out with \r\n:colorscheme base16-atelierestuary\r\n\r\nwith either light or dark background:\r\n:set bg=light \r\n:set bg=dark\r\n\r\nIf you want to make it the default, add that command to your vimrc or gvimrc. ","5":"Install in ~\/.vim\/colors, or ~\\vimfiles\\colors on Windows. \r\n\r\nor\r\n\r\nPathogen installation (recommended)\r\n\r\n1.  Download and install Tim Pope's Pathogen: https:\/\/github.com\/tpope\/vim-pathogen\r\n\r\n2. download or clone this repo on Github: https:\/\/github.com\/atelierbram\/vim-colors_atelier-schemes\r\n\r\n3.  Next, move or clone the `vim-colors_atelier-schemes` directory so that it is\r\na subdirectory of the `.vim\/bundle` directory.\r\n\r\n$ cd ~\/.vim\/bundle\r\n$ git clone https:\/\/github.com\/atelierbram\/vim-colors_atelier-schemes.git\r\n\r\nTry it out with \r\n:colorscheme base16-atelierestuary\r\n\r\nwith either light or dark background:\r\n:set bg=light \r\n:set bg=dark\r\n\r\nIf you want to make it the default, add that command to your vimrc or gvimrc. ","first_name":"Bram","6":"Bram","last_name":"de Haan","7":"de Haan","releases":[{"0":"5156","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"base16-atelierestuary.vim","4":"base16-atelierestuary.vim","src_id":"23140","5":"23140","creation_date":"1428333922","6":"1428333922"}]},"5155":{"script_id":"5155","0":"5155","script_name":"AtelierSavanna","1":"AtelierSavanna","script_type":"color scheme","2":"color scheme","summary":"Savanna is an understated greenish colorscheme with desaturated colors","3":"Savanna is an understated greenish colorscheme with desaturated colors","description":"This is one of ten colorschemes that were made with Base16 Builder. For the construction of these colorschemes, Solarized colorscheme stood as a model. Like in Solarized, the colorschemes come in a light \u00e2\u0080\u0093 and in a dark background version. It\u00e2\u0080\u0099s really just variations on the same idea, but each with it\u00e2\u0080\u0099s own color-value relations, interdependent on each other and their base (background-)color.  \r\n\r\nOne can find the demopage for these colorschemes at:\r\nhttp:\/\/atelierbram.github.io\/syntax-highlighting\/atelier-schemes\/ \r\n\r\nDownloads at the GitHub repo: \r\nhttps:\/\/github.com\/atelierbram\/vim-colors_atelier-schemes\r\n\r\nMore information on this particular colorscheme: \r\nhttp:\/\/atelierbram.github.io\/syntax-highlighting\/atelier-schemes\/savanna\r\n\r\nScreenshot dark version: \r\nhttp:\/\/atelierbram.github.io\/syntax-highlighting\/assets\/img\/savanna-dark_vim_640x425.png\r\n\r\nScreenshot light version: \r\nhttp:\/\/atelierbram.github.io\/syntax-highlighting\/assets\/img\/savanna-light_vim_640x425.png","4":"This is one of ten colorschemes that were made with Base16 Builder. For the construction of these colorschemes, Solarized colorscheme stood as a model. Like in Solarized, the colorschemes come in a light \u00e2\u0080\u0093 and in a dark background version. It\u00e2\u0080\u0099s really just variations on the same idea, but each with it\u00e2\u0080\u0099s own color-value relations, interdependent on each other and their base (background-)color.  \r\n\r\nOne can find the demopage for these colorschemes at:\r\nhttp:\/\/atelierbram.github.io\/syntax-highlighting\/atelier-schemes\/ \r\n\r\nDownloads at the GitHub repo: \r\nhttps:\/\/github.com\/atelierbram\/vim-colors_atelier-schemes\r\n\r\nMore information on this particular colorscheme: \r\nhttp:\/\/atelierbram.github.io\/syntax-highlighting\/atelier-schemes\/savanna\r\n\r\nScreenshot dark version: \r\nhttp:\/\/atelierbram.github.io\/syntax-highlighting\/assets\/img\/savanna-dark_vim_640x425.png\r\n\r\nScreenshot light version: \r\nhttp:\/\/atelierbram.github.io\/syntax-highlighting\/assets\/img\/savanna-light_vim_640x425.png","install_details":"Install in ~\/.vim\/colors, or ~\\vimfiles\\colors on Windows. \r\n\r\nor\r\n\r\nPathogen installation (recommended)\r\n\r\n1.  Download and install Tim Pope's Pathogen: https:\/\/github.com\/tpope\/vim-pathogen\r\n\r\n2. download or clone this repo on Github: https:\/\/github.com\/atelierbram\/vim-colors_atelier-schemes\r\n\r\n3.  Next, move or clone the `vim-colors_atelier-schemes` directory so that it is\r\na subdirectory of the `.vim\/bundle` directory.\r\n\r\n$ cd ~\/.vim\/bundle\r\n$ git clone https:\/\/github.com\/atelierbram\/vim-colors_atelier-schemes.git\r\n\r\nTry it out with \r\n:colorscheme base16-ateliersavanna\r\n\r\nwith either light or dark background:\r\n:set bg=light \r\n:set bg=dark\r\n\r\nIf you want to make it the default, add that command to your vimrc or gvimrc. ","5":"Install in ~\/.vim\/colors, or ~\\vimfiles\\colors on Windows. \r\n\r\nor\r\n\r\nPathogen installation (recommended)\r\n\r\n1.  Download and install Tim Pope's Pathogen: https:\/\/github.com\/tpope\/vim-pathogen\r\n\r\n2. download or clone this repo on Github: https:\/\/github.com\/atelierbram\/vim-colors_atelier-schemes\r\n\r\n3.  Next, move or clone the `vim-colors_atelier-schemes` directory so that it is\r\na subdirectory of the `.vim\/bundle` directory.\r\n\r\n$ cd ~\/.vim\/bundle\r\n$ git clone https:\/\/github.com\/atelierbram\/vim-colors_atelier-schemes.git\r\n\r\nTry it out with \r\n:colorscheme base16-ateliersavanna\r\n\r\nwith either light or dark background:\r\n:set bg=light \r\n:set bg=dark\r\n\r\nIf you want to make it the default, add that command to your vimrc or gvimrc. ","first_name":"Bram","6":"Bram","last_name":"de Haan","7":"de Haan","releases":[{"0":"5155","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"base16-ateliersavanna.vim","4":"base16-ateliersavanna.vim","src_id":"23139","5":"23139","creation_date":"1428333607","6":"1428333607"}]},"5154":{"script_id":"5154","0":"5154","script_name":"AtelierCave","1":"AtelierCave","script_type":"color scheme","2":"color scheme","summary":"Cave is a \u00e2\u0080\u009ccool-warm\u00e2\u0080\u009d colorscheme","3":"Cave is a \u00e2\u0080\u009ccool-warm\u00e2\u0080\u009d colorscheme","description":"This is one of ten colorschemes that were made with Base16 Builder. For the construction of these colorschemes, Solarized colorscheme stood as a model. Like in Solarized, the colorschemes come in a light \u00e2\u0080\u0093 and in a dark background version. It\u00e2\u0080\u0099s really just variations on the same idea, but each with it\u00e2\u0080\u0099s own color-value relations, interdependent on each other and their base (background-)color.  \r\n\r\nOne can find the demopage for these colorschemes at:\r\nhttp:\/\/atelierbram.github.io\/syntax-highlighting\/atelier-schemes\/ \r\n\r\nDownloads at the GitHub repo: \r\nhttps:\/\/github.com\/atelierbram\/vim-colors_atelier-schemes\r\n\r\nMore information on this particular colorscheme: \r\nhttp:\/\/atelierbram.github.io\/syntax-highlighting\/atelier-schemes\/cave\r\n\r\nScreenshot dark version: \r\nhttp:\/\/atelierbram.github.io\/syntax-highlighting\/assets\/img\/cave-dark_vim_640x425.png\r\n\r\nScreenshot light version: \r\nhttp:\/\/atelierbram.github.io\/syntax-highlighting\/assets\/img\/cave-light_vim_640x425.png","4":"This is one of ten colorschemes that were made with Base16 Builder. For the construction of these colorschemes, Solarized colorscheme stood as a model. Like in Solarized, the colorschemes come in a light \u00e2\u0080\u0093 and in a dark background version. It\u00e2\u0080\u0099s really just variations on the same idea, but each with it\u00e2\u0080\u0099s own color-value relations, interdependent on each other and their base (background-)color.  \r\n\r\nOne can find the demopage for these colorschemes at:\r\nhttp:\/\/atelierbram.github.io\/syntax-highlighting\/atelier-schemes\/ \r\n\r\nDownloads at the GitHub repo: \r\nhttps:\/\/github.com\/atelierbram\/vim-colors_atelier-schemes\r\n\r\nMore information on this particular colorscheme: \r\nhttp:\/\/atelierbram.github.io\/syntax-highlighting\/atelier-schemes\/cave\r\n\r\nScreenshot dark version: \r\nhttp:\/\/atelierbram.github.io\/syntax-highlighting\/assets\/img\/cave-dark_vim_640x425.png\r\n\r\nScreenshot light version: \r\nhttp:\/\/atelierbram.github.io\/syntax-highlighting\/assets\/img\/cave-light_vim_640x425.png","install_details":"Install in ~\/.vim\/colors, or ~\\vimfiles\\colors on Windows. \r\n\r\nor\r\n\r\nPathogen installation (recommended)\r\n\r\n1.  Download and install Tim Pope's Pathogen: https:\/\/github.com\/tpope\/vim-pathogen\r\n\r\n2. download or clone this repo on Github: https:\/\/github.com\/atelierbram\/vim-colors_atelier-schemes\r\n\r\n3.  Next, move or clone the `vim-colors_atelier-schemes` directory so that it is\r\na subdirectory of the `.vim\/bundle` directory.\r\n\r\n$ cd ~\/.vim\/bundle\r\n$ git clone https:\/\/github.com\/atelierbram\/vim-colors_atelier-schemes.git\r\n\r\nTry it out with \r\n:colorscheme base16-ateliercave\r\n\r\nwith either light or dark background:\r\n:set bg=light \r\n:set bg=dark\r\n\r\nIf you want to make it the default, add that command to your vimrc or gvimrc. ","5":"Install in ~\/.vim\/colors, or ~\\vimfiles\\colors on Windows. \r\n\r\nor\r\n\r\nPathogen installation (recommended)\r\n\r\n1.  Download and install Tim Pope's Pathogen: https:\/\/github.com\/tpope\/vim-pathogen\r\n\r\n2. download or clone this repo on Github: https:\/\/github.com\/atelierbram\/vim-colors_atelier-schemes\r\n\r\n3.  Next, move or clone the `vim-colors_atelier-schemes` directory so that it is\r\na subdirectory of the `.vim\/bundle` directory.\r\n\r\n$ cd ~\/.vim\/bundle\r\n$ git clone https:\/\/github.com\/atelierbram\/vim-colors_atelier-schemes.git\r\n\r\nTry it out with \r\n:colorscheme base16-ateliercave\r\n\r\nwith either light or dark background:\r\n:set bg=light \r\n:set bg=dark\r\n\r\nIf you want to make it the default, add that command to your vimrc or gvimrc. ","first_name":"Bram","6":"Bram","last_name":"de Haan","7":"de Haan","releases":[{"0":"5154","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"base16-ateliercave.vim","4":"base16-ateliercave.vim","src_id":"23138","5":"23138","creation_date":"1428333352","6":"1428333352"}]},"5153":{"script_id":"5153","0":"5153","script_name":"AtelierPlateau","1":"AtelierPlateau","script_type":"color scheme","2":"color scheme","summary":"Plateau is a warm colorscheme with desaturated colors","3":"Plateau is a warm colorscheme with desaturated colors","description":"This is one of ten colorschemes that were made with Base16 Builder. For the construction of these colorschemes, Solarized colorscheme stood as a model. Like in Solarized, the colorschemes come in a light \u00e2\u0080\u0093 and in a dark background version. It\u00e2\u0080\u0099s really just variations on the same idea, but each with it\u00e2\u0080\u0099s own color-value relations, interdependent on each other and their base (background-)color.  \r\n\r\nOne can find the demopage for these colorschemes at:\r\nhttp:\/\/atelierbram.github.io\/syntax-highlighting\/atelier-schemes\/ \r\n\r\nDownloads at the GitHub repo: \r\nhttps:\/\/github.com\/atelierbram\/vim-colors_atelier-schemes\r\n\r\nMore information on this particular colorscheme: \r\nhttp:\/\/atelierbram.github.io\/syntax-highlighting\/atelier-schemes\/plateau\r\n\r\nScreenshot dark version: \r\nhttp:\/\/atelierbram.github.io\/syntax-highlighting\/assets\/img\/plateau-dark_vim_640x425.png\r\n\r\nScreenshot light version: \r\nhttp:\/\/atelierbram.github.io\/syntax-highlighting\/assets\/img\/plateau-light_vim_640x425.png","4":"This is one of ten colorschemes that were made with Base16 Builder. For the construction of these colorschemes, Solarized colorscheme stood as a model. Like in Solarized, the colorschemes come in a light \u00e2\u0080\u0093 and in a dark background version. It\u00e2\u0080\u0099s really just variations on the same idea, but each with it\u00e2\u0080\u0099s own color-value relations, interdependent on each other and their base (background-)color.  \r\n\r\nOne can find the demopage for these colorschemes at:\r\nhttp:\/\/atelierbram.github.io\/syntax-highlighting\/atelier-schemes\/ \r\n\r\nDownloads at the GitHub repo: \r\nhttps:\/\/github.com\/atelierbram\/vim-colors_atelier-schemes\r\n\r\nMore information on this particular colorscheme: \r\nhttp:\/\/atelierbram.github.io\/syntax-highlighting\/atelier-schemes\/plateau\r\n\r\nScreenshot dark version: \r\nhttp:\/\/atelierbram.github.io\/syntax-highlighting\/assets\/img\/plateau-dark_vim_640x425.png\r\n\r\nScreenshot light version: \r\nhttp:\/\/atelierbram.github.io\/syntax-highlighting\/assets\/img\/plateau-light_vim_640x425.png","install_details":"Install in ~\/.vim\/colors, or ~\\vimfiles\\colors on Windows. \r\n\r\nor\r\n\r\nPathogen installation (recommended)\r\n\r\n1.  Download and install Tim Pope's Pathogen: https:\/\/github.com\/tpope\/vim-pathogen\r\n\r\n2. download or clone this repo on Github: https:\/\/github.com\/atelierbram\/vim-colors_atelier-schemes\r\n\r\n3.  Next, move or clone the `vim-colors_atelier-schemes` directory so that it is\r\na subdirectory of the `.vim\/bundle` directory.\r\n\r\n$ cd ~\/.vim\/bundle\r\n$ git clone https:\/\/github.com\/atelierbram\/vim-colors_atelier-schemes.git\r\n\r\nTry it out with \r\n:colorscheme base16-atelierplateau\r\n\r\nwith either light or dark background:\r\n:set bg=light \r\n:set bg=dark\r\n\r\nIf you want to make it the default, add that command to your vimrc or gvimrc. ","5":"Install in ~\/.vim\/colors, or ~\\vimfiles\\colors on Windows. \r\n\r\nor\r\n\r\nPathogen installation (recommended)\r\n\r\n1.  Download and install Tim Pope's Pathogen: https:\/\/github.com\/tpope\/vim-pathogen\r\n\r\n2. download or clone this repo on Github: https:\/\/github.com\/atelierbram\/vim-colors_atelier-schemes\r\n\r\n3.  Next, move or clone the `vim-colors_atelier-schemes` directory so that it is\r\na subdirectory of the `.vim\/bundle` directory.\r\n\r\n$ cd ~\/.vim\/bundle\r\n$ git clone https:\/\/github.com\/atelierbram\/vim-colors_atelier-schemes.git\r\n\r\nTry it out with \r\n:colorscheme base16-atelierplateau\r\n\r\nwith either light or dark background:\r\n:set bg=light \r\n:set bg=dark\r\n\r\nIf you want to make it the default, add that command to your vimrc or gvimrc. ","first_name":"Bram","6":"Bram","last_name":"de Haan","7":"de Haan","releases":[{"0":"5153","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"base16-atelierplateau.vim","4":"base16-atelierplateau.vim","src_id":"23137","5":"23137","creation_date":"1428333101","6":"1428333101"}]},"5152":{"script_id":"5152","0":"5152","script_name":"createfilenext.vim","1":"createfilenext.vim","script_type":"utility","2":"utility","summary":"Creates a new file in the directory of the current buffer.","3":"Creates a new file in the directory of the current buffer.","description":"createfilenext.vim\r\nCreates a new file in the directory of the current buffer.\r\n\r\nHome page: https:\/\/github.com\/caglartoklu\/createfilenext.vim\r\nFor documentation and a .gif animation, please visit the homepage link.\r\n\r\nThis script exposes one single command:\r\n:CreateFileNext\r\nWhen it is executed, it waits for a new file name from user, saves and opens it.","4":"createfilenext.vim\r\nCreates a new file in the directory of the current buffer.\r\n\r\nHome page: https:\/\/github.com\/caglartoklu\/createfilenext.vim\r\nFor documentation and a .gif animation, please visit the homepage link.\r\n\r\nThis script exposes one single command:\r\n:CreateFileNext\r\nWhen it is executed, it waits for a new file name from user, saves and opens it.","install_details":"For Vundle users:\r\n    Plugin 'caglartoklu\/createfilenext.vim'\r\n\r\nFor Pathogen users:\r\n    cd ~\/.vim\/bundle\r\n    git clone git:\/\/github.com\/caglartoklu\/createfilenext.vim\r\n\r\nFor all other users, simply drop the createfilenext.vim file to your plugin directory.","5":"For Vundle users:\r\n    Plugin 'caglartoklu\/createfilenext.vim'\r\n\r\nFor Pathogen users:\r\n    cd ~\/.vim\/bundle\r\n    git clone git:\/\/github.com\/caglartoklu\/createfilenext.vim\r\n\r\nFor all other users, simply drop the createfilenext.vim file to your plugin directory.","first_name":"Caglar","6":"Caglar","last_name":"Toklu","7":"Toklu","releases":[{"0":"5152","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"createfilenext.vim","4":"createfilenext.vim","src_id":"23135","5":"23135","creation_date":"1428264870","6":"1428264870"}]},"5151":{"script_id":"5151","0":"5151","script_name":"tsuquyomi","1":"tsuquyomi","script_type":"ftplugin","2":"ftplugin","summary":"Vim plugin for typescript","3":"Vim plugin for typescript","description":"Tsuquyomi is a vim plugin for TypeScript using TSServer, which is a tool for editor bundled into TypeScript.\r\n\r\nThis plugin provides the following features:\r\n+ Omni-completions\r\n+ Navigation to the location where the symbol is defined\r\n+ Navigation to the location where the symbol is referenced\r\n+ Show compile errors quickly.\r\n+ Rename the identifier\r\n+ etc..\r\n\r\nIf you want details, please see github repository or `:help tsuquyomi` after installation.\r\nhttps:\/\/github.com\/Quramy\/tsuquyomi","4":"Tsuquyomi is a vim plugin for TypeScript using TSServer, which is a tool for editor bundled into TypeScript.\r\n\r\nThis plugin provides the following features:\r\n+ Omni-completions\r\n+ Navigation to the location where the symbol is defined\r\n+ Navigation to the location where the symbol is referenced\r\n+ Show compile errors quickly.\r\n+ Rename the identifier\r\n+ etc..\r\n\r\nIf you want details, please see github repository or `:help tsuquyomi` after installation.\r\nhttps:\/\/github.com\/Quramy\/tsuquyomi","install_details":"Tsuquyomi requires the following:\r\n\r\n+ https:\/\/github.com\/Shougo\/vimproc.vim\r\n+ Node.js & TypeScript(v1.5.0 or later)\r\n\r\nFirst install Node.js and execute the following command in your prompt.\r\n$ npm -g install typescript\r\n\r\nSecond, install vimproc.\r\n(Please see https:\/\/github.com\/Shougo\/vimproc.vim#install)\r\n\r\nIf you use NeoBundle, append the following to your .vimrc and execute :NeoBundleInstall to get vimproc and tsuquyomi.\r\n\r\n```vim:.vimrc\r\nNeoBundle 'Shougo\/vimproc.vim', {\r\n\\ 'build' : {\r\n\\     'windows' : 'tools\\\\update-dll-mingw',\r\n\\     'cygwin' : 'make -f make_cygwin.mak',\r\n\\     'mac' : 'make -f make_mac.mak',\r\n\\     'linux' : 'make',\r\n\\     'unix' : 'gmake',\r\n\\    },\r\n\\ }\r\n\r\nNeoBundle 'Quramy\/tsuquyomi'\r\n```","5":"Tsuquyomi requires the following:\r\n\r\n+ https:\/\/github.com\/Shougo\/vimproc.vim\r\n+ Node.js & TypeScript(v1.5.0 or later)\r\n\r\nFirst install Node.js and execute the following command in your prompt.\r\n$ npm -g install typescript\r\n\r\nSecond, install vimproc.\r\n(Please see https:\/\/github.com\/Shougo\/vimproc.vim#install)\r\n\r\nIf you use NeoBundle, append the following to your .vimrc and execute :NeoBundleInstall to get vimproc and tsuquyomi.\r\n\r\n```vim:.vimrc\r\nNeoBundle 'Shougo\/vimproc.vim', {\r\n\\ 'build' : {\r\n\\     'windows' : 'tools\\\\update-dll-mingw',\r\n\\     'cygwin' : 'make -f make_cygwin.mak',\r\n\\     'mac' : 'make -f make_mac.mak',\r\n\\     'linux' : 'make',\r\n\\     'unix' : 'gmake',\r\n\\    },\r\n\\ }\r\n\r\nNeoBundle 'Quramy\/tsuquyomi'\r\n```","first_name":"Yosuke","6":"Yosuke","last_name":"Kurami","7":"Kurami","releases":[{"0":"5151","vim_version":"7.4","1":"7.4","script_version":"0.7.0","2":"0.7.0","version_comment":"https:\/\/github.com\/Quramy\/tsuquyomi\/releases\/tag\/v0.7.0","3":"https:\/\/github.com\/Quramy\/tsuquyomi\/releases\/tag\/v0.7.0","package":"tsuquyomi-0.7.0.zip","4":"tsuquyomi-0.7.0.zip","src_id":"25074","5":"25074","creation_date":"1492362934","6":"1492362934"},{"0":"5151","vim_version":"7.4","1":"7.4","script_version":"0.6.1","2":"0.6.1","version_comment":"https:\/\/github.com\/Quramy\/tsuquyomi\/releases\/tag\/v0.6.1","3":"https:\/\/github.com\/Quramy\/tsuquyomi\/releases\/tag\/v0.6.1","package":"tsuquyomi-0.6.1.zip","4":"tsuquyomi-0.6.1.zip","src_id":"24253","5":"24253","creation_date":"1463473204","6":"1463473204"},{"0":"5151","vim_version":"7.4","1":"7.4","script_version":"0.5.3","2":"0.5.3","version_comment":"https:\/\/github.com\/Quramy\/tsuquyomi\/releases\/tag\/v0.5.3","3":"https:\/\/github.com\/Quramy\/tsuquyomi\/releases\/tag\/v0.5.3","package":"tsuquyomi-0.5.3.zip","4":"tsuquyomi-0.5.3.zip","src_id":"24241","5":"24241","creation_date":"1462883136","6":"1462883136"},{"0":"5151","vim_version":"7.4","1":"7.4","script_version":"0.4.6","2":"0.4.6","version_comment":"https:\/\/github.com\/Quramy\/tsuquyomi\/releases\/tag\/v0.4.6","3":"https:\/\/github.com\/Quramy\/tsuquyomi\/releases\/tag\/v0.4.6","package":"tsuquyomi-0.4.6.zip","4":"tsuquyomi-0.4.6.zip","src_id":"23484","5":"23484","creation_date":"1437984876","6":"1437984876"},{"0":"5151","vim_version":"7.4","1":"7.4","script_version":"0.3.1","2":"0.3.1","version_comment":"https:\/\/github.com\/Quramy\/tsuquyomi\/releases\/tag\/v0.3.1","3":"https:\/\/github.com\/Quramy\/tsuquyomi\/releases\/tag\/v0.3.1","package":"tsuquyomi-0.3.1.zip","4":"tsuquyomi-0.3.1.zip","src_id":"23163","5":"23163","creation_date":"1428736181","6":"1428736181"},{"0":"5151","vim_version":"7.4","1":"7.4","script_version":"0.2.2","2":"0.2.2","version_comment":"* Update docs with release of TypeScript 1.5.0-alpha.\r\n* Add to check the option bexpr for non gvim.","3":"* Update docs with release of TypeScript 1.5.0-alpha.\r\n* Add to check the option bexpr for non gvim.","package":"tsuquyomi-0.2.2.zip","4":"tsuquyomi-0.2.2.zip","src_id":"23131","5":"23131","creation_date":"1428163789","6":"1428163789"}]},"5150":{"script_id":"5150","0":"5150","script_name":"vim-mediawiki-editor","1":"vim-mediawiki-editor","script_type":"utility","2":"utility","summary":"Edit MediaWiki right from Vim!","3":"Edit MediaWiki right from Vim!","description":"== Better description at https:\/\/github.com\/aquach\/vim-mediawiki-editor ==\r\n\r\n# vim-mediawiki-editor\r\n\r\nEdit MediaWiki articles from the comfort of Vim, your favorite text editor!\r\n\r\n## Installation\r\n\r\nvim-mediawiki-editor requires Vim compiled with python support and the [python `mwclient` library](https:\/\/github.com\/mwclient\/mwclient).\r\n\r\nYou likely have Python support, but you can check with `vim --version | grep +python`. MacVim comes with Python support.\r\n\r\nIf you get an error, try `pip install mwclient` to get the library.\r\n\r\nOnce you have these, use your favorite Vim plugin manager to install `aquach\/vim-mediawiki-editor`, or copy `plugin` and `doc` into your `.vim` folder.\r\n\r\nI recommend pairing this plugin with [mediawiki.vim](https:\/\/github.com\/chikamichi\/mediawiki.vim) for syntax highlighting and with [goyo.vim](https:\/\/github.com\/junegunn\/goyo.vim) for WriteRoom-esque editing.\r\n\r\n## Usage\r\n\r\nvim-mediawiki-editor offers these commands:\r\n\r\n#### :MWRead \r\n\r\nLoads the given article into the current buffer.\r\n\r\n```\r\n:MWRead Radish\r\n```\r\n\r\n#### :MWWrite [article-name]\r\n\r\nWrites the buffer back to the site. If you don't specify an article name, it defaults to the article you currently have open with `:MWRead`. After prompting you for the edit summary and major\/minor edit, it will publish your work back to the site.\r\n\r\n#### :MWDiff [article-name]\r\n\r\nDiffs the current buffer against the hosted version of the article specified on the site. If you don't specify an article name, it defaults to the article you currently have open with `:MWRead`.\r\n\r\n#### :MWBrowse [article-name]\r\n\r\nViews the article specified in your configured browser. If you don't specify an article name, it defaults to the article you currently have open with `:MWRead`.\r\n\r\n## Configuration\r\n\r\nIf you don't specify these settings, vim-mediawiki-editor will prompt you when you first run a vim-mediawiki-editor command.\r\n\r\n#### g:mediawiki_editor_url\r\n\r\nThe URL of the site you're editing. For the English wikipedia, that'd be `en.wikipedia.org`.\r\n\r\n#### g:mediawiki_editor_username\r\n\r\nYour account username.\r\n\r\n#### g:mediawiki_editor_password\r\n\r\nYour account password. I recommend putting the URL and username in your `.vimrc` and letting Vim ask for your password.\r\n\r\n## Contributing\r\n\r\nThis plugin is currently quite simple. Contributions, suggestions, and feedback are all welcomed!","4":"== Better description at https:\/\/github.com\/aquach\/vim-mediawiki-editor ==\r\n\r\n# vim-mediawiki-editor\r\n\r\nEdit MediaWiki articles from the comfort of Vim, your favorite text editor!\r\n\r\n## Installation\r\n\r\nvim-mediawiki-editor requires Vim compiled with python support and the [python `mwclient` library](https:\/\/github.com\/mwclient\/mwclient).\r\n\r\nYou likely have Python support, but you can check with `vim --version | grep +python`. MacVim comes with Python support.\r\n\r\nIf you get an error, try `pip install mwclient` to get the library.\r\n\r\nOnce you have these, use your favorite Vim plugin manager to install `aquach\/vim-mediawiki-editor`, or copy `plugin` and `doc` into your `.vim` folder.\r\n\r\nI recommend pairing this plugin with [mediawiki.vim](https:\/\/github.com\/chikamichi\/mediawiki.vim) for syntax highlighting and with [goyo.vim](https:\/\/github.com\/junegunn\/goyo.vim) for WriteRoom-esque editing.\r\n\r\n## Usage\r\n\r\nvim-mediawiki-editor offers these commands:\r\n\r\n#### :MWRead \r\n\r\nLoads the given article into the current buffer.\r\n\r\n```\r\n:MWRead Radish\r\n```\r\n\r\n#### :MWWrite [article-name]\r\n\r\nWrites the buffer back to the site. If you don't specify an article name, it defaults to the article you currently have open with `:MWRead`. After prompting you for the edit summary and major\/minor edit, it will publish your work back to the site.\r\n\r\n#### :MWDiff [article-name]\r\n\r\nDiffs the current buffer against the hosted version of the article specified on the site. If you don't specify an article name, it defaults to the article you currently have open with `:MWRead`.\r\n\r\n#### :MWBrowse [article-name]\r\n\r\nViews the article specified in your configured browser. If you don't specify an article name, it defaults to the article you currently have open with `:MWRead`.\r\n\r\n## Configuration\r\n\r\nIf you don't specify these settings, vim-mediawiki-editor will prompt you when you first run a vim-mediawiki-editor command.\r\n\r\n#### g:mediawiki_editor_url\r\n\r\nThe URL of the site you're editing. For the English wikipedia, that'd be `en.wikipedia.org`.\r\n\r\n#### g:mediawiki_editor_username\r\n\r\nYour account username.\r\n\r\n#### g:mediawiki_editor_password\r\n\r\nYour account password. I recommend putting the URL and username in your `.vimrc` and letting Vim ask for your password.\r\n\r\n## Contributing\r\n\r\nThis plugin is currently quite simple. Contributions, suggestions, and feedback are all welcomed!","install_details":"","5":"","first_name":"A","6":"A","last_name":"Quach","7":"Quach","releases":[{"0":"5150","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"vim-mediawiki-editor-1.0.tgz","4":"vim-mediawiki-editor-1.0.tgz","src_id":"23120","5":"23120","creation_date":"1427935191","6":"1427935191"}]},"5149":{"script_id":"5149","0":"5149","script_name":"underscore.vim","1":"underscore.vim","script_type":"utility","2":"utility","summary":"Vim script utility library","3":"Vim script utility library","description":"\r\nSEE: https:\/\/github.com\/haya14busa\/underscore.vim","4":"\r\nSEE: https:\/\/github.com\/haya14busa\/underscore.vim","install_details":"","5":"","first_name":"haya14busa","6":"haya14busa","last_name":" ","7":" ","releases":[{"0":"5149","vim_version":"7.3","1":"7.3","script_version":"1.0.0","2":"1.0.0","version_comment":"Initial upload","3":"Initial upload","package":"underscore.vim-1.0.0.zip","4":"underscore.vim-1.0.0.zip","src_id":"23112","5":"23112","creation_date":"1427838157","6":"1427838157"}]},"5148":{"script_id":"5148","0":"5148","script_name":"ShowSpaces","1":"ShowSpaces","script_type":"syntax","2":"syntax","summary":"Highlight indentation characters if they contain spaces, even mixed with tabs","3":"Highlight indentation characters if they contain spaces, even mixed with tabs","description":"Vim-ShowSpaces is a Vim plugin which highlights the indentation characters when\r\nspaces are used, even when spaces and tabs are mixed. It is useful to enforce\r\nthe use of tabulations in a project instead of spaces, or even worse, mixed\r\ntabulations and spaces.\r\n\r\nThe highlighting can be activated on a per filetype basis.\r\n\r\nREAD THE DOCUMENTATION (or at least the README)! The plugin does not highlight\r\nanything by default. You need to 'let g:showSpaces=1'  somewhere (preferably inside a\r\nftplugin\/ local config file).\r\n\r\nSources are available on github: https:\/\/github.com\/guiniol\/vim-showspaces.git\r\nThe project is under BSD-2 clauses license. (See file LICENSE in the archive).\r\n","4":"Vim-ShowSpaces is a Vim plugin which highlights the indentation characters when\r\nspaces are used, even when spaces and tabs are mixed. It is useful to enforce\r\nthe use of tabulations in a project instead of spaces, or even worse, mixed\r\ntabulations and spaces.\r\n\r\nThe highlighting can be activated on a per filetype basis.\r\n\r\nREAD THE DOCUMENTATION (or at least the README)! The plugin does not highlight\r\nanything by default. You need to 'let g:showSpaces=1'  somewhere (preferably inside a\r\nftplugin\/ local config file).\r\n\r\nSources are available on github: https:\/\/github.com\/guiniol\/vim-showspaces.git\r\nThe project is under BSD-2 clauses license. (See file LICENSE in the archive).\r\n","install_details":"If you don't have a preferred installation method, I recommend installing\r\npathogen.vim, and then simply copy and paste:\r\n\r\n  cd ~\/.vim\/bundle\r\n  git clone git:\/\/github.com\/guiniol\/vim-showspaces.git\r\n\r\nIf you are a Vundle user, the following will probably work, although it was not\r\ntested:\r\n\r\nAdd Bundle 'guiniol\/vim-showspaces' to your |vimrc| and then:\r\n\r\n  - either within Vim: :BundleInstall\r\n  - or in your shell: vim +BundleInstall +qall\r\n\r\nIf you use NeoBundle, do the following:\r\n\r\nAdd NeoBundle 'guiniol\/vim-showspaces.git' to your vimrc and then:\r\n\r\n  - either within Vim: :NeoBundleInstall\r\n  - or in your shell: vim +NeoBundleInstall +qall\r\n\r\nIf you feel adventurous, you can also put yourself the files in the right directories after decompressing the archive, they are not too numerous.\r\n","5":"If you don't have a preferred installation method, I recommend installing\r\npathogen.vim, and then simply copy and paste:\r\n\r\n  cd ~\/.vim\/bundle\r\n  git clone git:\/\/github.com\/guiniol\/vim-showspaces.git\r\n\r\nIf you are a Vundle user, the following will probably work, although it was not\r\ntested:\r\n\r\nAdd Bundle 'guiniol\/vim-showspaces' to your |vimrc| and then:\r\n\r\n  - either within Vim: :BundleInstall\r\n  - or in your shell: vim +BundleInstall +qall\r\n\r\nIf you use NeoBundle, do the following:\r\n\r\nAdd NeoBundle 'guiniol\/vim-showspaces.git' to your vimrc and then:\r\n\r\n  - either within Vim: :NeoBundleInstall\r\n  - or in your shell: vim +NeoBundleInstall +qall\r\n\r\nIf you feel adventurous, you can also put yourself the files in the right directories after decompressing the archive, they are not too numerous.\r\n","first_name":"Laurent","6":"Laurent","last_name":"Georget","7":"Georget","releases":[{"0":"5148","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"vim-showspaces-1.0.tar.gz","4":"vim-showspaces-1.0.tar.gz","src_id":"23105","5":"23105","creation_date":"1427727195","6":"1427727195"}]},"5146":{"script_id":"5146","0":"5146","script_name":"AtelierSulphurpool","1":"AtelierSulphurpool","script_type":"color scheme","2":"color scheme","summary":"Sulphurpool is a purplish colorscheme","3":"Sulphurpool is a purplish colorscheme","description":"This is one of five colorschemes that were made with Base16 Builder. For the construction of these colorschemes, Solarized colorscheme stood as a model. Like in Solarized, the colorschemes come in a light \u00e2\u0080\u0093 and in a dark background version. It\u00e2\u0080\u0099s really just variations on the same idea, but each with it\u00e2\u0080\u0099s own color-value relations, interdependent on each other and their base (background-)color.  \r\n\r\nOne can find the demopage for these colorschemes at:\r\nhttp:\/\/atelierbram.github.io\/syntax-highlighting\/atelier-schemes\/ \r\n\r\nDownloads at the GitHub repo: \r\nhttps:\/\/github.com\/atelierbram\/vim-colors_atelier-schemes\r\n\r\nMore information on this particular colorscheme: \r\nhttp:\/\/atelierbram.github.io\/syntax-highlighting\/atelier-schemes\/sulphurpool\r\n\r\nScreenshot dark version: \r\nhttp:\/\/atelierbram.github.io\/syntax-highlighting\/assets\/img\/sulphurpool-dark_vim_640x425.png\r\n\r\nScreenshot light version: \r\nhttp:\/\/atelierbram.github.io\/syntax-highlighting\/assets\/img\/sulphurpool-light_vim_640x425.png","4":"This is one of five colorschemes that were made with Base16 Builder. For the construction of these colorschemes, Solarized colorscheme stood as a model. Like in Solarized, the colorschemes come in a light \u00e2\u0080\u0093 and in a dark background version. It\u00e2\u0080\u0099s really just variations on the same idea, but each with it\u00e2\u0080\u0099s own color-value relations, interdependent on each other and their base (background-)color.  \r\n\r\nOne can find the demopage for these colorschemes at:\r\nhttp:\/\/atelierbram.github.io\/syntax-highlighting\/atelier-schemes\/ \r\n\r\nDownloads at the GitHub repo: \r\nhttps:\/\/github.com\/atelierbram\/vim-colors_atelier-schemes\r\n\r\nMore information on this particular colorscheme: \r\nhttp:\/\/atelierbram.github.io\/syntax-highlighting\/atelier-schemes\/sulphurpool\r\n\r\nScreenshot dark version: \r\nhttp:\/\/atelierbram.github.io\/syntax-highlighting\/assets\/img\/sulphurpool-dark_vim_640x425.png\r\n\r\nScreenshot light version: \r\nhttp:\/\/atelierbram.github.io\/syntax-highlighting\/assets\/img\/sulphurpool-light_vim_640x425.png","install_details":"Install in ~\/.vim\/colors, or ~\\vimfiles\\colors on Windows. \r\n\r\nor\r\n\r\nPathogen installation (recommended)\r\n\r\n1.  Download and install Tim Pope's Pathogen: https:\/\/github.com\/tpope\/vim-pathogen\r\n\r\n2. download or clone this repo on Github: https:\/\/github.com\/atelierbram\/vim-colors_atelier-schemes\r\n\r\n3.  Next, move or clone the `vim-colors_atelier-schemes` directory so that it is\r\na subdirectory of the `.vim\/bundle` directory.\r\n\r\n$ cd ~\/.vim\/bundle\r\n$ git clone https:\/\/github.com\/atelierbram\/vim-colors_atelier-schemes.git\r\n\r\nTry it out with \r\n:colorscheme base16-ateliersulphurpool\r\n\r\nwith either light or dark background:\r\n:set bg=light \r\n:set bg=dark\r\n\r\nIf you want to make it the default, add that command to your vimrc or gvimrc. ","5":"Install in ~\/.vim\/colors, or ~\\vimfiles\\colors on Windows. \r\n\r\nor\r\n\r\nPathogen installation (recommended)\r\n\r\n1.  Download and install Tim Pope's Pathogen: https:\/\/github.com\/tpope\/vim-pathogen\r\n\r\n2. download or clone this repo on Github: https:\/\/github.com\/atelierbram\/vim-colors_atelier-schemes\r\n\r\n3.  Next, move or clone the `vim-colors_atelier-schemes` directory so that it is\r\na subdirectory of the `.vim\/bundle` directory.\r\n\r\n$ cd ~\/.vim\/bundle\r\n$ git clone https:\/\/github.com\/atelierbram\/vim-colors_atelier-schemes.git\r\n\r\nTry it out with \r\n:colorscheme base16-ateliersulphurpool\r\n\r\nwith either light or dark background:\r\n:set bg=light \r\n:set bg=dark\r\n\r\nIf you want to make it the default, add that command to your vimrc or gvimrc. ","first_name":"Bram","6":"Bram","last_name":"de Haan","7":"de Haan","releases":[{"0":"5146","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"base16-ateliersulphurpool.vim","4":"base16-ateliersulphurpool.vim","src_id":"23101","5":"23101","creation_date":"1427564430","6":"1427564430"}]},"5145":{"script_id":"5145","0":"5145","script_name":"spss syntax highlighting file","1":"spss syntax highlighting file","script_type":"syntax","2":"syntax","summary":"syntax highlighting file based on spss version 22","3":"syntax highlighting file based on spss version 22","description":"Vim syntax file for SPSS command files (.sps).\r\n\r\nThis file highlights SPSS commands (including some common command abbreviations), subcommands, comments, and strings, based upon SPSS version 22.","4":"Vim syntax file for SPSS command files (.sps).\r\n\r\nThis file highlights SPSS commands (including some common command abbreviations), subcommands, comments, and strings, based upon SPSS version 22.","install_details":"See vim help on installing syntax files\r\n\r\nOr, add this file to the syntax files in your vim syntax directory, and add the following line to your vimrc file:\r\n\r\nau BufNewFile,BufRead *.sps set filetype=spss\r\n","5":"See vim help on installing syntax files\r\n\r\nOr, add this file to the syntax files in your vim syntax directory, and add the following line to your vimrc file:\r\n\r\nau BufNewFile,BufRead *.sps set filetype=spss\r\n","first_name":"karel","6":"karel","last_name":"asselberghs","7":"asselberghs","releases":[{"0":"5145","vim_version":"7.0","1":"7.0","script_version":"1.0.0","2":"1.0.0","version_comment":"Initial upload","3":"Initial upload","package":"spss.vim","4":"spss.vim","src_id":"23085","5":"23085","creation_date":"1427021899","6":"1427021899"}]},"5144":{"script_id":"5144","0":"5144","script_name":"gulp-vim","1":"gulp-vim","script_type":"utility","2":"utility","summary":"Simple gulp wrapper for Vim + ctrlp-vim + unite-gulp","3":"Simple gulp wrapper for Vim + ctrlp-vim + unite-gulp","description":"This plugin is a simple gulp (gulpjs.com) wrapper for vim.\r\n\r\nFeatures:\r\n    * Run gulp inside Vim.\r\n    * Run gulp in the backgound using an external terminal without losing focus.\r\n    * Run gulp using a custom shell or vim command.\r\n    * List your gulp tasks.\r\n    * Support different gulpfiles (.js, .babel.js, .coffee).\r\n    * CtrlP integration.\r\n    * Unite source.\r\n    * Works on GNU\/Linux and Windows.\r\n\r\nCheck the official repository for more details > https:\/\/github.com\/KabbAmine\/gulp-vim\r\nPlease rate this plugin if you find it useful (Or useless ;) ).\r\n\r\nP.S: Starting from version 0.8.0 the plugin uses semantic versionning 2.0.0.\r\n\r\nUsage\r\n=====\r\n\r\nGulp-vim provides 2 main commands: Gulp and GulpExt.\r\n\r\nBoth commands accept 0 or many arguments (Task name(s)), that can be completed using .\r\n\r\n:Gulp    [task(s)...]\r\n:GulpExt [task(s)...]\r\n\r\nIf no task name was provided, 'default' is used.\r\n\r\nThe difference between those 2 commands is that Gulp executes gulp inside Vim and GulpExt open an external terminal:\r\n    * The default one via exo-open in GNU\/Linux and a simple cmd in Windows.\r\n    * Or use Dispatch if its installed.\r\n    * Or use a defined user command.\r\nThen execute gulp.\r\n\r\nDon't use gulp watching tasks with the command Gulp (In case,  to stop it), use GulpExt for those tasks.\r\n\r\nUsing:\r\n:CtrlpGulp\r\nYou can execute gulp tasks with CtrlP (This command is provided only if ctrlp is installed).\r\n\r\nA Unite source is also provided:\r\n:Unite -buffer-name=gulp gulp\r\n\r\n:GulpTasks                                              => To show a list of your gulp task names (Extracted from current gulpfile.js).\r\n:GulpFile [gulpfile || path\/to\/gulpfile]     => To specify the gulpfile to use: gulpfile.coffee, gulpfile.babel.js (By default its gulpfile.js).\r\n\r\nFor the plugin configuration please refer to the included documentation file or the README > https:\/\/github.com\/KabbAmine\/gulp-vim\/blob\/master\/README.md","4":"This plugin is a simple gulp (gulpjs.com) wrapper for vim.\r\n\r\nFeatures:\r\n    * Run gulp inside Vim.\r\n    * Run gulp in the backgound using an external terminal without losing focus.\r\n    * Run gulp using a custom shell or vim command.\r\n    * List your gulp tasks.\r\n    * Support different gulpfiles (.js, .babel.js, .coffee).\r\n    * CtrlP integration.\r\n    * Unite source.\r\n    * Works on GNU\/Linux and Windows.\r\n\r\nCheck the official repository for more details > https:\/\/github.com\/KabbAmine\/gulp-vim\r\nPlease rate this plugin if you find it useful (Or useless ;) ).\r\n\r\nP.S: Starting from version 0.8.0 the plugin uses semantic versionning 2.0.0.\r\n\r\nUsage\r\n=====\r\n\r\nGulp-vim provides 2 main commands: Gulp and GulpExt.\r\n\r\nBoth commands accept 0 or many arguments (Task name(s)), that can be completed using .\r\n\r\n:Gulp    [task(s)...]\r\n:GulpExt [task(s)...]\r\n\r\nIf no task name was provided, 'default' is used.\r\n\r\nThe difference between those 2 commands is that Gulp executes gulp inside Vim and GulpExt open an external terminal:\r\n    * The default one via exo-open in GNU\/Linux and a simple cmd in Windows.\r\n    * Or use Dispatch if its installed.\r\n    * Or use a defined user command.\r\nThen execute gulp.\r\n\r\nDon't use gulp watching tasks with the command Gulp (In case,  to stop it), use GulpExt for those tasks.\r\n\r\nUsing:\r\n:CtrlpGulp\r\nYou can execute gulp tasks with CtrlP (This command is provided only if ctrlp is installed).\r\n\r\nA Unite source is also provided:\r\n:Unite -buffer-name=gulp gulp\r\n\r\n:GulpTasks                                              => To show a list of your gulp task names (Extracted from current gulpfile.js).\r\n:GulpFile [gulpfile || path\/to\/gulpfile]     => To specify the gulpfile to use: gulpfile.coffee, gulpfile.babel.js (By default its gulpfile.js).\r\n\r\nFor the plugin configuration please refer to the included documentation file or the README > https:\/\/github.com\/KabbAmine\/gulp-vim\/blob\/master\/README.md","install_details":"Manually\r\n=======\r\n\r\nInstall the distributed files into Vim runtime directory which is usually ~\/.vim\/, or $HOME\/vimfiles on Windows.\r\n\r\nUsing a plugin manager\r\n===================\r\n\r\nAnd this is the recommended way, use a vim plugin manager:\r\n\r\nVim-plug       Plug 'KabbAmine\/gulp-vim' \t             PlugInstall\r\nVundle \t          Plugin 'KabbAmine\/gulp-vim' \t          PluginInstall\r\nNeoBundle \t  NeoBundle 'KabbAmine\/gulp-vim' \t  NeoBundleInstall\r\n\r\nThis is not mandatory, but the plugin can use Tpope's Dispatch plugin (https:\/\/github.com\/tpope\/vim-dispatch) if its installed.","5":"Manually\r\n=======\r\n\r\nInstall the distributed files into Vim runtime directory which is usually ~\/.vim\/, or $HOME\/vimfiles on Windows.\r\n\r\nUsing a plugin manager\r\n===================\r\n\r\nAnd this is the recommended way, use a vim plugin manager:\r\n\r\nVim-plug       Plug 'KabbAmine\/gulp-vim' \t             PlugInstall\r\nVundle \t          Plugin 'KabbAmine\/gulp-vim' \t          PluginInstall\r\nNeoBundle \t  NeoBundle 'KabbAmine\/gulp-vim' \t  NeoBundleInstall\r\n\r\nThis is not mandatory, but the plugin can use Tpope's Dispatch plugin (https:\/\/github.com\/tpope\/vim-dispatch) if its installed.","first_name":"Kabbaj","6":"Kabbaj","last_name":"Amine","7":"Amine","releases":[{"0":"5144","vim_version":"7.0","1":"7.0","script_version":"0.8.4","2":"0.8.4","version_comment":"- More refactoring\r\n- Improve the way the plugin detects & sets the gulpfile\r\n- Simplify task names gathering for plugin(s) integration\r\n- Take in account whitespace characters before task names\r\n- Fix: Get task names only if a gulpfile is found","3":"- More refactoring\r\n- Improve the way the plugin detects & sets the gulpfile\r\n- Simplify task names gathering for plugin(s) integration\r\n- Take in account whitespace characters before task names\r\n- Fix: Get task names only if a gulpfile is found","package":"gulp-vim.tar.gz","4":"gulp-vim.tar.gz","src_id":"23839","5":"23839","creation_date":"1451395245","6":"1451395245"},{"0":"5144","vim_version":"7.0","1":"7.0","script_version":"0.8.3","2":"0.8.3","version_comment":"0.8.3\r\n    Fix: Get focus back only when vim window id is different from 0\r\n0.8.2\r\n    Refactoring\r\n    Improve custom command process, g:gv_custom_cmd can now escape double quotes if needed\r\n    Set back focus to the editor after using GulpExt (Need wmctrl & is Unix only)\r\n    Update screenshots and documentation\r\n0.8.1\r\n    Fix rvm_hack value\r\n    Add more informations in the README.","3":"0.8.3\r\n    Fix: Get focus back only when vim window id is different from 0\r\n0.8.2\r\n    Refactoring\r\n    Improve custom command process, g:gv_custom_cmd can now escape double quotes if needed\r\n    Set back focus to the editor after using GulpExt (Need wmctrl & is Unix only)\r\n    Update screenshots and documentation\r\n0.8.1\r\n    Fix rvm_hack value\r\n    Add more informations in the README.","package":"gulp-vim.tar.gz","4":"gulp-vim.tar.gz","src_id":"23823","5":"23823","creation_date":"1450893475","6":"1450893475"},{"0":"5144","vim_version":"7.0","1":"7.0","script_version":"0.8.0","2":"0.8.0","version_comment":"* Fixes bug introduced by ad764163f\r\n* Improve definitions of commands & functions.\r\n* Allows rvm hack option to work everywhere & make it unix only.\r\n# Features:\r\n* Add Unite source thanks to @dawnofthedev\r\n* Add possibility to define a custom command to use with GulpExt.","3":"* Fixes bug introduced by ad764163f\r\n* Improve definitions of commands & functions.\r\n* Allows rvm hack option to work everywhere & make it unix only.\r\n# Features:\r\n* Add Unite source thanks to @dawnofthedev\r\n* Add possibility to define a custom command to use with GulpExt.","package":"gulp-vim.tar.gz","4":"gulp-vim.tar.gz","src_id":"23789","5":"23789","creation_date":"1450176367","6":"1450176367"},{"0":"5144","vim_version":"7.0","1":"7.0","script_version":"v0.7.1","2":"v0.7.1","version_comment":"* Add a command for CtrlP integration (`:CtrlPGulp`)\r\n* Use `--gulpfile` flag\r\n","3":"* Add a command for CtrlP integration (`:CtrlPGulp`)\r\n* Use `--gulpfile` flag\r\n","package":"gulp-vim.tar.gz","4":"gulp-vim.tar.gz","src_id":"23744","5":"23744","creation_date":"1448107682","6":"1448107682"},{"0":"5144","vim_version":"7.0","1":"7.0","script_version":"v0.6.2","2":"v0.6.2","version_comment":"- Fix GulpExt command\r\n- Add Dispatch integration","3":"- Fix GulpExt command\r\n- Add Dispatch integration","package":"gulp-vim.tar.gz","4":"gulp-vim.tar.gz","src_id":"23689","5":"23689","creation_date":"1446031326","6":"1446031326"},{"0":"5144","vim_version":"7.0","1":"7.0","script_version":"v0.6","2":"v0.6","version_comment":"- Add support for coffee & babel gulpfiles\r\n- New command :GulpFile\r\n- New cutomisation variable g:gv_default_gulpfile\r\n- Show now some informations before proceeding","3":"- Add support for coffee & babel gulpfiles\r\n- New command :GulpFile\r\n- New cutomisation variable g:gv_default_gulpfile\r\n- Show now some informations before proceeding","package":"gulp-vim.tar.gz","4":"gulp-vim.tar.gz","src_id":"23681","5":"23681","creation_date":"1445533351","6":"1445533351"},{"0":"5144","vim_version":"7.0","1":"7.0","script_version":"0.5","2":"0.5","version_comment":"- Refactoring\r\n- Add doc & changelog files","3":"- Refactoring\r\n- Add doc & changelog files","package":"gulp-vim.tar.gz","4":"gulp-vim.tar.gz","src_id":"23677","5":"23677","creation_date":"1445164536","6":"1445164536"},{"0":"5144","vim_version":"7.0","1":"7.0","script_version":"0.1.1","2":"0.1.1","version_comment":"- Fix GulpExt in windows.","3":"- Fix GulpExt in windows.","package":"gulp-vim.tar.gz","4":"gulp-vim.tar.gz","src_id":"23095","5":"23095","creation_date":"1427274279","6":"1427274279"},{"0":"5144","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"gulp-vim.tar.gz","4":"gulp-vim.tar.gz","src_id":"23083","5":"23083","creation_date":"1427019289","6":"1427019289"}]},"5143":{"script_id":"5143","0":"5143","script_name":"Quicker_file","1":"Quicker_file","script_type":"utility","2":"utility","summary":"2-step search plugin for quicker open","3":"2-step search plugin for quicker open","description":"quicker_file\r\n==========\r\n\r\njump to files, even though you might not remember the full path and \/ or the full name.\r\n\r\n2-step search - If not found in current dir then it will search given dir.\r\n\r\nModified from quick_file at http:\/\/www.vim.org\/scripts\/script.php?script_id=4980\r\n\r\nNEED VIM WITH PYTHON SUPPORT!!!\r\n===============================\r\n\r\n:QF filename-fragment\r\n\r\nthe plugin will try to jump to shallowest match under current directory and its sub directories as well as `secondSearchPath` if `secondSearch` is set `True` and no result in first search. Also, it is possible to provide more details for a deeper match.\r\n\r\nlet's say we have a\/c.txt a\/b\/c.txt\r\n\r\n:QF c will jump to a\/c.txt and start editing\r\n:QF c b will jump to a\/b\/c.txt\r\n\r\nConfiguration\r\n===============================\r\nOpen `plugin\/quicker_file.vim`,\r\nif you want to enable second search(search in `secondSearchPath` if no result in first search) (default: on, only work in linux), then:\r\n\r\n\r\nsecondSearch = True\r\nsecondSearchPath='path_to_search' \/\/default is ~, you can use space to seperate paths(e.g '~ \/usr\/include \/tmp')\r\n\r\n","4":"quicker_file\r\n==========\r\n\r\njump to files, even though you might not remember the full path and \/ or the full name.\r\n\r\n2-step search - If not found in current dir then it will search given dir.\r\n\r\nModified from quick_file at http:\/\/www.vim.org\/scripts\/script.php?script_id=4980\r\n\r\nNEED VIM WITH PYTHON SUPPORT!!!\r\n===============================\r\n\r\n:QF filename-fragment\r\n\r\nthe plugin will try to jump to shallowest match under current directory and its sub directories as well as `secondSearchPath` if `secondSearch` is set `True` and no result in first search. Also, it is possible to provide more details for a deeper match.\r\n\r\nlet's say we have a\/c.txt a\/b\/c.txt\r\n\r\n:QF c will jump to a\/c.txt and start editing\r\n:QF c b will jump to a\/b\/c.txt\r\n\r\nConfiguration\r\n===============================\r\nOpen `plugin\/quicker_file.vim`,\r\nif you want to enable second search(search in `secondSearchPath` if no result in first search) (default: on, only work in linux), then:\r\n\r\n\r\nsecondSearch = True\r\nsecondSearchPath='path_to_search' \/\/default is ~, you can use space to seperate paths(e.g '~ \/usr\/include \/tmp')\r\n\r\n","install_details":"Unpack plugin\/quicker_file to `plugin` directory in .vim","5":"Unpack plugin\/quicker_file to `plugin` directory in .vim","first_name":"Vic","6":"Vic","last_name":"Luo","7":"Luo","releases":[{"0":"5143","vim_version":"7.0","1":"7.0","script_version":"1.1","2":"1.1","version_comment":"Bug fixed: first search not work","3":"Bug fixed: first search not work","package":"quicker_file.zip","4":"quicker_file.zip","src_id":"23075","5":"23075","creation_date":"1426916050","6":"1426916050"},{"0":"5143","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"quicker_file.zip","4":"quicker_file.zip","src_id":"23074","5":"23074","creation_date":"1426915318","6":"1426915318"}]},"5142":{"script_id":"5142","0":"5142","script_name":"unmaze.vim","1":"unmaze.vim","script_type":"utility","2":"utility","summary":"A vim plugin that shows the C\/C++ preprocessor conditions that need to be met fo","3":"A vim plugin that shows the C\/C++ preprocessor conditions that need to be met fo","description":"The plugin adds the function FindIfMacros which finds the preprocessor conditions that surround the currently selected line and displays them as a combined expression, to better navigate \"#ifdef-mazes\".\r\nBinds to 'M'\r\n\r\nNote: I'm not sure which the lowest vim version it would work with is.","4":"The plugin adds the function FindIfMacros which finds the preprocessor conditions that surround the currently selected line and displays them as a combined expression, to better navigate \"#ifdef-mazes\".\r\nBinds to 'M'\r\n\r\nNote: I'm not sure which the lowest vim version it would work with is.","install_details":"Just copy to ~\/.vim\/plugins\/","5":"Just copy to ~\/.vim\/plugins\/","first_name":"Alicia","6":"Alicia","last_name":"","7":"","releases":[{"0":"5142","vim_version":"7.4","1":"7.4","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"unmaze.vim","4":"unmaze.vim","src_id":"23070","5":"23070","creation_date":"1426843523","6":"1426843523"}]},"5141":{"script_id":"5141","0":"5141","script_name":"vim-uncrustify","1":"vim-uncrustify","script_type":"utility","2":"utility","summary":"Helper to call uncrustify in vim.","3":"Helper to call uncrustify in vim.","description":"Helper to call uncrustify in vim.\r\n\r\n```\r\nautocmd FileType c noremap   :call Uncrustify('c')\r\nautocmd FileType c vnoremap   :call RangeUncrustify('c')\r\nautocmd FileType cpp noremap   :call Uncrustify('cpp')\r\nautocmd FileType cpp vnoremap   :call RangeUncrustify('cpp')\r\n```\r\n\r\nSee https:\/\/github.com\/Cofyc\/vim-uncrustify for details.","4":"Helper to call uncrustify in vim.\r\n\r\n```\r\nautocmd FileType c noremap   :call Uncrustify('c')\r\nautocmd FileType c vnoremap   :call RangeUncrustify('c')\r\nautocmd FileType cpp noremap   :call Uncrustify('cpp')\r\nautocmd FileType cpp vnoremap   :call RangeUncrustify('cpp')\r\n```\r\n\r\nSee https:\/\/github.com\/Cofyc\/vim-uncrustify for details.","install_details":"### With pathogen\r\n\r\nDownload .tar.gz package, and extract it into ~\/.vim\/bundle or with `git`:\r\n\r\n```\r\ncd ~\/.vim\/bundle\r\ngit clone https:\/\/github.com\/Cofyc\/vim-uncrustify.git\r\n```\r\n\r\n### Without pathogen\r\n\r\nSimply extract package into your ~\/.vim folder.","5":"### With pathogen\r\n\r\nDownload .tar.gz package, and extract it into ~\/.vim\/bundle or with `git`:\r\n\r\n```\r\ncd ~\/.vim\/bundle\r\ngit clone https:\/\/github.com\/Cofyc\/vim-uncrustify.git\r\n```\r\n\r\n### Without pathogen\r\n\r\nSimply extract package into your ~\/.vim folder.","first_name":"Yecheng","6":"Yecheng","last_name":"Fu","7":"Fu","releases":[{"0":"5141","vim_version":"7.0","1":"7.0","script_version":"0.0.1","2":"0.0.1","version_comment":"Initial upload","3":"Initial upload","package":"vim-uncrustify-0.0.1.tar.gz","4":"vim-uncrustify-0.0.1.tar.gz","src_id":"23068","5":"23068","creation_date":"1426840618","6":"1426840618"}]},"5140":{"script_id":"5140","0":"5140","script_name":"vim-http-client","1":"vim-http-client","script_type":"utility","2":"utility","summary":"Make HTTP requests from Vim without wrestling the command line!","3":"Make HTTP requests from Vim without wrestling the command line!","description":"== Pretty description and demo at https:\/\/github.com\/aquach\/vim-http-client ==\r\n\r\nMake HTTP requests from Vim with the HTTP format you already know, rather than wrestling with curl -X POST -b cookie=$1 -F csrf_token=$2 -F \"request={\\\"user_id\\\":123}\" http:\/\/example.org! Then parse the results right in Vim, syntax highlighted the way you expect!\r\n\r\nUsage\r\n\r\nPut your cursor anywhere in a newline-delimited block of text and hit tt. vim-http-client will parse the text into a HTTP request, execute it, and display its results will appear in a split. You can also directly invoke the HTTP client with :call HTTPClientDoRequest(). The format mirrors HTTP's format:\r\n\r\n# Comments start with #.\r\n# First request.\r\n \r\n: \r\n: \r\n...\r\n: \r\n\r\n\r\n# Second request.\r\n \r\n: \r\n: \r\n...\r\n: \r\n\r\nDepending on where you put your cursor, the first or second request will execute. You can also substitute variables anywhere in the request:\r\n\r\n# Second request.\r\n# :foo = bar\r\nPOST http:\/\/httpbin.org\/post\r\n{\r\n  \"data\": \":foo\",\r\n  \"otherkey\": \"hello\"\r\n}\r\nEach variable lives in a separate commented line and always starts with a colon. Variables are substituted with simple string substitution.\r\n\r\nIf you'd like to pass form-encoded data, set your body like this:\r\n\r\n=\r\n=\r\n...\r\n=\r\nSee examples\/examples.txt for more examples.\r\n\r\nThe output appears in a new split. Based on the Content-Type header of the HTTP response, vim-http-client chooses a filetype for syntax highlighting. It currently supports XML, JSON, and HTML; all others will get ft=text.\r\n\r\nConfiguration\r\n\r\ng:http_client_bind_hotkey (default 1)\r\n\r\nControls whether or not tt will run the HTTP client. Regardless of the setting, vim-http-client will not overwrite your existing tt mapping if it exists.\r\n\r\nContributing\r\n\r\nThis plugin is currently quite simple. Contributions, suggestions, and feedback are all welcomed!","4":"== Pretty description and demo at https:\/\/github.com\/aquach\/vim-http-client ==\r\n\r\nMake HTTP requests from Vim with the HTTP format you already know, rather than wrestling with curl -X POST -b cookie=$1 -F csrf_token=$2 -F \"request={\\\"user_id\\\":123}\" http:\/\/example.org! Then parse the results right in Vim, syntax highlighted the way you expect!\r\n\r\nUsage\r\n\r\nPut your cursor anywhere in a newline-delimited block of text and hit tt. vim-http-client will parse the text into a HTTP request, execute it, and display its results will appear in a split. You can also directly invoke the HTTP client with :call HTTPClientDoRequest(). The format mirrors HTTP's format:\r\n\r\n# Comments start with #.\r\n# First request.\r\n \r\n: \r\n: \r\n...\r\n: \r\n\r\n\r\n# Second request.\r\n \r\n: \r\n: \r\n...\r\n: \r\n\r\nDepending on where you put your cursor, the first or second request will execute. You can also substitute variables anywhere in the request:\r\n\r\n# Second request.\r\n# :foo = bar\r\nPOST http:\/\/httpbin.org\/post\r\n{\r\n  \"data\": \":foo\",\r\n  \"otherkey\": \"hello\"\r\n}\r\nEach variable lives in a separate commented line and always starts with a colon. Variables are substituted with simple string substitution.\r\n\r\nIf you'd like to pass form-encoded data, set your body like this:\r\n\r\n=\r\n=\r\n...\r\n=\r\nSee examples\/examples.txt for more examples.\r\n\r\nThe output appears in a new split. Based on the Content-Type header of the HTTP response, vim-http-client chooses a filetype for syntax highlighting. It currently supports XML, JSON, and HTML; all others will get ft=text.\r\n\r\nConfiguration\r\n\r\ng:http_client_bind_hotkey (default 1)\r\n\r\nControls whether or not tt will run the HTTP client. Regardless of the setting, vim-http-client will not overwrite your existing tt mapping if it exists.\r\n\r\nContributing\r\n\r\nThis plugin is currently quite simple. Contributions, suggestions, and feedback are all welcomed!","install_details":"Installation\r\n\r\nvim-http-client requires Vim compiled with python support and the python requests library.\r\n\r\nYou likely have Python support, but you can check with vim --version | grep +python. MacVim comes with Python support.\r\n\r\nTo check if you have the requests library, try python -c 'import requests'. If you get an error, try pip install requests to get the library. Many distros ship Python support with Vim and the requests library with Python.\r\n\r\nOnce you have these, use your favorite Vim plugin manager to install aquach\/vim-http-client, or copy plugin and doc into your .vim folder.","5":"Installation\r\n\r\nvim-http-client requires Vim compiled with python support and the python requests library.\r\n\r\nYou likely have Python support, but you can check with vim --version | grep +python. MacVim comes with Python support.\r\n\r\nTo check if you have the requests library, try python -c 'import requests'. If you get an error, try pip install requests to get the library. Many distros ship Python support with Vim and the requests library with Python.\r\n\r\nOnce you have these, use your favorite Vim plugin manager to install aquach\/vim-http-client, or copy plugin and doc into your .vim folder.","first_name":"A","6":"A","last_name":"Quach","7":"Quach","releases":[{"0":"5140","vim_version":"7.0","1":"7.0","script_version":"1.1","2":"1.1","version_comment":"* Allow global variables that affect all requests in the buffer by prefixing the variable with $.\r\n* Pretty print response JSON.\r\n* Allow setting of filetype for JSON content type. Defaults to javascript.","3":"* Allow global variables that affect all requests in the buffer by prefixing the variable with $.\r\n* Pretty print response JSON.\r\n* Allow setting of filetype for JSON content type. Defaults to javascript.","package":"vim-http-client-1.1.tgz","4":"vim-http-client-1.1.tgz","src_id":"23114","5":"23114","creation_date":"1427908706","6":"1427908706"},{"0":"5140","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"vim-http-client-1.0.tgz","4":"vim-http-client-1.0.tgz","src_id":"23066","5":"23066","creation_date":"1426794308","6":"1426794308"}]},"5139":{"script_id":"5139","0":"5139","script_name":"vim-scrum-markdown","1":"vim-scrum-markdown","script_type":"utility","2":"utility","summary":"manage a scrum dashboard inside vim","3":"manage a scrum dashboard inside vim","description":" Usage\r\n -----\r\n \r\n Say you are in a *scrum\/* directory.\r\n \r\n * create a *scrum\/tasks\/* subdirectory.\r\n * create a file *scrum\/backlog.md* \r\n * Add tasks in *backlog.md* as links, you only need to type tasks names between brackets, hiting *ENTER* will automatically create the associated link and file in where you can enter the detailed user story. Hit *Shift + Enter* to return to the backlog file.\r\n \r\n\r\n * cut and paste your tasks to sprint-x.md files to plan your sprints","4":" Usage\r\n -----\r\n \r\n Say you are in a *scrum\/* directory.\r\n \r\n * create a *scrum\/tasks\/* subdirectory.\r\n * create a file *scrum\/backlog.md* \r\n * Add tasks in *backlog.md* as links, you only need to type tasks names between brackets, hiting *ENTER* will automatically create the associated link and file in where you can enter the detailed user story. Hit *Shift + Enter* to return to the backlog file.\r\n \r\n\r\n * cut and paste your tasks to sprint-x.md files to plan your sprints","install_details":"This plugin depends on plasticboy\/vim-markdown and mmai\/vim-markdown-wiki\r\n\r\nCopy vim-scrum-markdown.vim into your plugin directory","5":"This plugin depends on plasticboy\/vim-markdown and mmai\/vim-markdown-wiki\r\n\r\nCopy vim-scrum-markdown.vim into your plugin directory","first_name":"Henri","6":"Henri","last_name":"Bourcereau","7":"Bourcereau","releases":[{"0":"5139","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"vim-scrum-markdown.vim","4":"vim-scrum-markdown.vim","src_id":"23064","5":"23064","creation_date":"1426785533","6":"1426785533"}]},"5138":{"script_id":"5138","0":"5138","script_name":"vim-markdown-wiki","1":"vim-markdown-wiki","script_type":"utility","2":"utility","summary":"Links manipulation and navigation in markdown pages","3":"Links manipulation and navigation in markdown pages","description":"\"vim-markdown-wiki\" is plugin which eases the navigation between files in a personnal wiki\r\nLinks syntax follows Github Flavored Markdown ie [My displayed link](My-link.md)\r\n\r\nUsage\r\n-----\r\nLink creation : \r\n - Hit the ENTER key when the cursor is on a text between brackets : `[a title]`\r\n - The link will be created  `[a title](a-title.md)` and the corresponding file will be loaded in the buffer.\r\n\r\nNavigation : \r\n - Hit the ENTER key when the cursor is on a wiki link\r\n - The corresponding link file is loaded in the current buffer.\r\n - Hit Shift + ENTER to go back\r\n\r\n","4":"\"vim-markdown-wiki\" is plugin which eases the navigation between files in a personnal wiki\r\nLinks syntax follows Github Flavored Markdown ie [My displayed link](My-link.md)\r\n\r\nUsage\r\n-----\r\nLink creation : \r\n - Hit the ENTER key when the cursor is on a text between brackets : `[a title]`\r\n - The link will be created  `[a title](a-title.md)` and the corresponding file will be loaded in the buffer.\r\n\r\nNavigation : \r\n - Hit the ENTER key when the cursor is on a wiki link\r\n - The corresponding link file is loaded in the current buffer.\r\n - Hit Shift + ENTER to go back\r\n\r\n","install_details":"Copy the vim-markdown-wiki.vim file into the $HOME\/.vim\/plugin\/ directory","5":"Copy the vim-markdown-wiki.vim file into the $HOME\/.vim\/plugin\/ directory","first_name":"Henri","6":"Henri","last_name":"Bourcereau","7":"Bourcereau","releases":[{"0":"5138","vim_version":"7.0","1":"7.0","script_version":"1.3","2":"1.3","version_comment":"fix relative paths","3":"fix relative paths","package":"vim-markdown-wiki.vim","4":"vim-markdown-wiki.vim","src_id":"23077","5":"23077","creation_date":"1426938978","6":"1426938978"},{"0":"5138","vim_version":"7.0","1":"7.0","script_version":"1.3","2":"1.3","version_comment":"fix relative paths","3":"fix relative paths","package":"vim-markdown-wiki.vim","4":"vim-markdown-wiki.vim","src_id":"23076","5":"23076","creation_date":"1426938936","6":"1426938936"},{"0":"5138","vim_version":"7.0","1":"7.0","script_version":"1.2","2":"1.2","version_comment":"Create new linked file title\r\nReturn to the correct cursor position","3":"Create new linked file title\r\nReturn to the correct cursor position","package":"vim-markdown-wiki.vim","4":"vim-markdown-wiki.vim","src_id":"23072","5":"23072","creation_date":"1426857039","6":"1426857039"},{"0":"5138","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"vim-markdown-wiki.vim","4":"vim-markdown-wiki.vim","src_id":"23060","5":"23060","creation_date":"1426780906","6":"1426780906"}]},"5137":{"script_id":"5137","0":"5137","script_name":"vim.ergonomic","1":"vim.ergonomic","script_type":"utility","2":"utility","summary":"use vim more ergonomically","3":"use vim more ergonomically","description":"Download and view documentation for the latest version at:\r\n\r\nhttps:\/\/github.com\/cloudformdesign\/vim.ergonomic","4":"Download and view documentation for the latest version at:\r\n\r\nhttps:\/\/github.com\/cloudformdesign\/vim.ergonomic","install_details":"add the following to your .vimrc (with pathogen installed)\r\nbundle \"cloudformdesign\/vim.ergonomic\"","5":"add the following to your .vimrc (with pathogen installed)\r\nbundle \"cloudformdesign\/vim.ergonomic\"","first_name":"Garrett","6":"Garrett","last_name":"Berg","7":"Berg","releases":[{"0":"5137","vim_version":"7.3","1":"7.3","script_version":"0.0.1","2":"0.0.1","version_comment":"Initial upload","3":"Initial upload","package":"vim.ergonomic.zip","4":"vim.ergonomic.zip","src_id":"23056","5":"23056","creation_date":"1426720288","6":"1426720288"}]},"5136":{"script_id":"5136","0":"5136","script_name":"plugconf","1":"plugconf","script_type":"utility","2":"utility","summary":"A VIM plugin for managing configurations of other plugins.","3":"A VIM plugin for managing configurations of other plugins.","description":"PlugConf is a VIM plugin for managing configurations of other plugins. Plugin\r\nconfigurations are stored in separate files, and loaded only if the plugin is\r\nloaded.\r\n\r\nThis can come in handy if you, like me, often try out new plugins, but don't\r\nwant to mess up your .vimrc file, or if you just want to keep your .vimrc\r\nclean from plugin specific configuration.\r\n\r\nIt's also a nice feature, if you like to have the same set of configuration\r\nfiles across multiple platforms or environments, but still load a different\r\nset of plugins. That way, you could have the same mappings handled by\r\ndifferent plugins, only by loading them, and without having to change the\r\nconfiguration.\r\n\r\nPlugConf doesn't load your plugins, but depends on your favorite plugin\r\nmanager to handle that. The plugin should work with the most popular plugin\r\nmanagers, including:\r\n\r\n- Pathogen\r\n- vim-plug\r\n- Vundle\r\n- NeoBundle\r\n\r\nEven though PlugConf relies on a plugin manager, it knows nothing about which\r\none you use, as it only looks at the modified `runtimepath`. Because of that,\r\nit should work with any plugin manager that installs plugins in a folder\r\ncalled `bundle` in your vimfiles directory.\r\n\r\nI actually use both Pathogen and vim-plug together, and PlugConf handles both\r\nnicely.\r\n\r\nRepository at https:\/\/github.com\/niboan\/plugconf","4":"PlugConf is a VIM plugin for managing configurations of other plugins. Plugin\r\nconfigurations are stored in separate files, and loaded only if the plugin is\r\nloaded.\r\n\r\nThis can come in handy if you, like me, often try out new plugins, but don't\r\nwant to mess up your .vimrc file, or if you just want to keep your .vimrc\r\nclean from plugin specific configuration.\r\n\r\nIt's also a nice feature, if you like to have the same set of configuration\r\nfiles across multiple platforms or environments, but still load a different\r\nset of plugins. That way, you could have the same mappings handled by\r\ndifferent plugins, only by loading them, and without having to change the\r\nconfiguration.\r\n\r\nPlugConf doesn't load your plugins, but depends on your favorite plugin\r\nmanager to handle that. The plugin should work with the most popular plugin\r\nmanagers, including:\r\n\r\n- Pathogen\r\n- vim-plug\r\n- Vundle\r\n- NeoBundle\r\n\r\nEven though PlugConf relies on a plugin manager, it knows nothing about which\r\none you use, as it only looks at the modified `runtimepath`. Because of that,\r\nit should work with any plugin manager that installs plugins in a folder\r\ncalled `bundle` in your vimfiles directory.\r\n\r\nI actually use both Pathogen and vim-plug together, and PlugConf handles both\r\nnicely.\r\n\r\nRepository at https:\/\/github.com\/niboan\/plugconf","install_details":"Since this plugin is pretty useles unless you have installed other plugins with\r\nyour plugin manager, it is assumed that you know how to install it.\r\n\r\nThe repository is 'niboan\/plugconf'","5":"Since this plugin is pretty useles unless you have installed other plugins with\r\nyour plugin manager, it is assumed that you know how to install it.\r\n\r\nThe repository is 'niboan\/plugconf'","first_name":"Niels Bo","6":"Niels Bo","last_name":"Andersen","7":"Andersen","releases":[{"0":"5136","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"plugconf-1.0.zip","4":"plugconf-1.0.zip","src_id":"23044","5":"23044","creation_date":"1426549631","6":"1426549631"}]},"5135":{"script_id":"5135","0":"5135","script_name":"ColumnTags","1":"ColumnTags","script_type":"utility","2":"utility","summary":"Navigate your tags in column-view","3":"Navigate your tags in column-view","description":"# Column Tags - Follow your tags in column-view\r\n\r\n## Overview\r\n\r\nThis plugin aims to help you navigate through you code using\r\n[tags](http:\/\/ctags.sourceforge.net\/). Vim already has good support for this.\r\nHaving generated a tags file in your current working directory, if you move\r\nyour cursor over a keyword while in command mode and press `CTRL-]`, you will\r\nnavigate to the definition of the keyword within your project and pressing\r\n`CTRL-t` will take you back to where you came from.\r\n\r\nUsing this plugin, the experience is very similar, but you can take advantage\r\nof Vim's support for multiple windows and a wide screen to maintain an overview\r\nof both the part of the code you navigated from and the part of the code that\r\nhosts the definition of you keyword. The final experience is reminiscent of the\r\ncolumn-view of Mac's file manager program, Finder.\r\n\r\n![Column-view screenshot](http:\/\/cdn.osxdaily.com\/wp-content\/uploads\/2010\/02\/mac-os-x-finder-column-view.JPG)\r\n\r\nTo get started, you must create a tags file in the base folder of you project.\r\nMost developmnent environments come with *ctags* installed, so simply run:\r\n\r\n    cd \r\n    ctags -R .\r\n\r\nWhile using the plugin, you will have up to 3 windows displayed as columns.\r\n\r\nWith `CTRL-]`, you can follow the tag under the cursor in a new vertical split.\r\nIf the number of existing columns is `g:max_columns` and the rightmost column\r\nis focused, the view will be shifted to the left before doing the vertical\r\nsplit. If you follow a tag from a column that is not rightmost, the new column\r\nwill replace those that are to the right of the one that was in focus. The goal\r\nis to be able to view both the part of the code that executes a function or\r\nclass and its definition at the same time.\r\n\r\nWith `CTRL-t`, you can go back to where you were before following a tag. If the\r\ncolumn under focus is not the leftmost, this simply means focusing on the\r\ncolumn to the left. If the leftmost column was focused, the windows that got\r\nhidden by following tags and moving towards the right will start being\r\nrevealed.","4":"# Column Tags - Follow your tags in column-view\r\n\r\n## Overview\r\n\r\nThis plugin aims to help you navigate through you code using\r\n[tags](http:\/\/ctags.sourceforge.net\/). Vim already has good support for this.\r\nHaving generated a tags file in your current working directory, if you move\r\nyour cursor over a keyword while in command mode and press `CTRL-]`, you will\r\nnavigate to the definition of the keyword within your project and pressing\r\n`CTRL-t` will take you back to where you came from.\r\n\r\nUsing this plugin, the experience is very similar, but you can take advantage\r\nof Vim's support for multiple windows and a wide screen to maintain an overview\r\nof both the part of the code you navigated from and the part of the code that\r\nhosts the definition of you keyword. The final experience is reminiscent of the\r\ncolumn-view of Mac's file manager program, Finder.\r\n\r\n![Column-view screenshot](http:\/\/cdn.osxdaily.com\/wp-content\/uploads\/2010\/02\/mac-os-x-finder-column-view.JPG)\r\n\r\nTo get started, you must create a tags file in the base folder of you project.\r\nMost developmnent environments come with *ctags* installed, so simply run:\r\n\r\n    cd \r\n    ctags -R .\r\n\r\nWhile using the plugin, you will have up to 3 windows displayed as columns.\r\n\r\nWith `CTRL-]`, you can follow the tag under the cursor in a new vertical split.\r\nIf the number of existing columns is `g:max_columns` and the rightmost column\r\nis focused, the view will be shifted to the left before doing the vertical\r\nsplit. If you follow a tag from a column that is not rightmost, the new column\r\nwill replace those that are to the right of the one that was in focus. The goal\r\nis to be able to view both the part of the code that executes a function or\r\nclass and its definition at the same time.\r\n\r\nWith `CTRL-t`, you can go back to where you were before following a tag. If the\r\ncolumn under focus is not the leftmost, this simply means focusing on the\r\ncolumn to the left. If the leftmost column was focused, the windows that got\r\nhidden by following tags and moving towards the right will start being\r\nrevealed.","install_details":"## Installation\r\n\r\nJust paste the package's contents into into your .vim directory.\r\n\r\n\r\n## Installing with [Pathogen](https:\/\/github.com\/tpope\/vim-pathogen)\r\n\r\n1. `cd ~\/.vim\/bundle`\r\n2. `git clone git:\/\/github.com\/kbairak\/ColumnTags.vim.git","5":"## Installation\r\n\r\nJust paste the package's contents into into your .vim directory.\r\n\r\n\r\n## Installing with [Pathogen](https:\/\/github.com\/tpope\/vim-pathogen)\r\n\r\n1. `cd ~\/.vim\/bundle`\r\n2. `git clone git:\/\/github.com\/kbairak\/ColumnTags.vim.git","first_name":"Konstantinos","6":"Konstantinos","last_name":"Bairaktaris","7":"Bairaktaris","releases":[{"0":"5135","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"ColumnTags.vim-0.1.zip","4":"ColumnTags.vim-0.1.zip","src_id":"23038","5":"23038","creation_date":"1426449460","6":"1426449460"}]},"5134":{"script_id":"5134","0":"5134","script_name":"todo-txt.vim","1":"todo-txt.vim","script_type":"ftplugin","2":"ftplugin","summary":"Vim plugin for Todo.txt","3":"Vim plugin for Todo.txt","description":"# Todo.txt-vim\r\n\r\n        #####                                                #     #\r\n          #    ####  #####   ####     ##### #    # #####     #     # # #    #\r\n          #   #    # #    # #    #      #    #  #    #       #     # # ##  ##\r\n          #   #    # #    # #    #      #     ##     #   ### #     # # # ## #\r\n          #   #    # #    # #    #      #     ##     #        #   #  # #    #\r\n          #   #    # #    # #    # ##   #    #  #    #         # #   # #    #\r\n          #    ####  #####   ####  ##   #   #    #   #          #    # #    #\r\n\r\n                        Efficient Todo.txt management in vim\r\n\r\n## Table of Contents\r\n\r\n1. [Release notes](#release-notes)\r\n2. [Introduction](#introduction)\r\n    1. [Todo.txt rules](#todo.txt-rules)\r\n    2. [Why this Fork ?](#Why-this-fork)\r\n    3. [Installation](#installation)\r\n3. [TodoTxt Files](#todotxt-files)\r\n4. [Completion](#completion)\r\n5. [Hierarchical Sort](#hierarchical-sort)\r\n6. [Mappings](#mappings)\r\n    1. [Sort](#sort)\r\n    2. [Priorities](#priorities)\r\n    3. [Dates](#dates)\r\n    4. [Done](#done)\r\n\r\n## Release notes\r\n\r\n+   V0.8.1 Incorporates yet antoher Fretep work : highlithing for tasks due today.\r\n\r\n+   v0.8 Incorporates Fretep's work on overdue dates (PR#13 and PR#16) witch\r\nremoves python dependency, allow to control the cursor position after a sort by\r\ntodo (see (sort)[#sort] and\/or issue #15) and fixes bug when sorting a file\r\ncontaining only lines with due:date (issue #14).\r\n\r\n+   v0.7.6 Incorporates [Sietse's work](https:\/\/github.com\/sietse\/todo.txt-vim\/commit\/57d45200c8b033d31c9191ee0eb0711c801cdb1d) to make cancel and mark as done mapping repeatable using [vim-repeat](https:\/\/github.com\/tpope\/vim-repeat).\r\n+   v0.7.5 Incorporates [Fievel's work](https:\/\/github.com\/fievel\/todo.txt-vim\/commit\/0863e1434e9a89ace06c4856b6cb32ba9906e3de) to make overduedates work on python3.\r\n+   v0.7.4 includes the overduedate support from Guilherme Victal (see pull\r\n\r\n    [request #45 on freitass version](https:\/\/github.com\/freitass\/todo.txt-vim\/pull\/45)),\r\n    it highlight dates in overdue tasks as an Error. It depends on a\r\n    Python library, however, and as such will only be able to work if your version\r\n    of Vim was compiled with the `+python` option (as most common versions do).\r\n \r\n    If your Vim installation does **not** have Python support, this plugin **will work just fine** but this feature will be disabled.\r\n\r\n\r\n+   Since v0.7.3, `TodoComplete` is replaced by `todo#Complete`, you might need to update your vimrc (see [completion](#completion)).\r\n\r\n## Introduction\r\n\r\nTodo.txt-vim is a plugin to manage todo.txt files it was initially designed by\r\n[Freitass](https:\/\/github.com\/freitass\/todo.txt-vim) then forked and improved\r\nby David Beniamine.\r\n\r\n### Todo.txt rules\r\n\r\nTodo.txt is a standard human readable todo notes file defined [here](http:\/\/todotxt.com):\r\n\r\n\"The todo.txt format is a simple set of\r\n[rules](https:\/\/github.com\/ginatrapani\/todo.txt-cli\/wiki\/The-Todo.txt-Format)\r\nthat make todo.txt both human and machine-readable. The format supports\r\npriorities, creation and completion dates, projects and contexts. That's\r\nall you need to be productive. See an example Todo.txt file\":\r\n\r\n    (A) Call Mom @Phone +Family\r\n    (A) Schedule annual checkup +Health\r\n    (B) Outline chapter 5 +FamilyNovel @Computer\r\n    (C) Add cover sheets @ComputerOffice +FamilyTPSReports\r\n    Plan backyard herb garden @ComputerHome\r\n    Pick up milk @ComputerGroceryStore\r\n    Research self-publishing services +FamilyNovel @ComputerComputer\r\n    x Download Todo.txt mobile app @ComputerPhone\r\n\r\n### Why this fork ?\r\n\r\nThis plugin is a fork of [freitass\r\ntodo.txt-vim](https:\/\/github.com\/freitass\/todo.txt-vim). It add severals cool\r\nfunctionalities including:\r\n\r\n+ [Hierarchical sort](##hierarchical-sort)\r\n+ [A completion function](#completion)\r\n+ [A proper handling of due dates](#dates)\r\n+ [A Flexible file naming](#todotxt-files).\r\n+ Syntax Highlight for couples key:value.\r\n+ `x` is a toggle which allow you to unmark a task as done.\r\n+ `C` Toggle Mark a task cancelled\r\n+ If the current buffer is a done.txt file, the basic sort sorts on\r\n  completion date.\r\n+ ...\r\n\r\n### Installation\r\n\r\n#### Vizardry\r\n\r\nIf you have [Vizardry](https:\/\/github.com\/dbeniamine\/vizardry) installed,\r\nyou can run from vim:\r\n\r\n    :Invoke -u dbeniamine todo.txt-vim\r\n\r\n#### Pathogen install\r\n\r\n    git clone https:\/\/github.com\/dbeniamine\/todo.txt-vim.git ~\/.vim\/bundle\/todo.txt-vim\r\n\r\nThen from vim: `:Helptags` to update the doc\r\n\r\n#### Quick install\r\n\r\n        git clone https:\/\/github.com\/dbeniamine\/todo.txt-vim.git\r\n        cd todo.txt-vim\r\n        cp -r .\/* ~\/.vim\r\n\r\n\r\nIf you want the help installed, run `:helptags ~\/.vim\/doc` inside vim after\r\nhaving copied the files.  Then you will be able to get the commands help with:\r\n`:h todo.txt`\r\n\r\n## TodoTxt Files\r\n\r\nThis plugin provides a Flexible file naming for todo.txt, all the following\r\nnames are recognized as todo:\r\n\r\n    YYYY-MM-[Tt]odo.txt\r\n    YYYY-MM-DD[Tt]odo.txt\r\n    [Tt]odo-YYYY-MM.txt\r\n    [Tt]odo-YYYY-MM-DD.txt\r\n    [Tt]odo.txt\r\n    [Tt]oday.txt\r\n\r\nAnd obviously the same are recognize as done:\r\n\r\n    YYYY-MM-[Dd]one.txt\r\n    YYYY-MM-DD[Dd]one.txt\r\n    [Dd]one-YYYY-MM.txt\r\n    [Dd]one-YYYY-MM-DD.txt\r\n    [Dd]one.txt\r\n    [Dd]one-[Tt]oday.txt\r\n\r\nMoreover, `D` moves the task under the cursor to the done.txt\r\nfile corresponding to the current todo.txt, aka if you are editing\r\n2015-07-07-todo.txt, the done file while be 2015-07-07-done.txt. If you don't\r\nlike this behavior, you can set the default done.txt name:\r\n\r\n    let g:TodoTxtForceDoneName='done.txt'\r\n\r\n## Completion\r\n\r\nThis plugin provides a nice complete function for project and context, to use\r\nit add the following lines to your vimrc:\r\n\r\n    \" Use todo#Complete as the omni complete function for todo files\r\n    au filetype todo setlocal omnifunc=todo#Complete\r\n\r\nYou can also start automatically the completion when entering '+' or '@' by\r\nadding the next lines to your vimrc:\r\n\r\n    \" Auto complete projects\r\n    au filetype todo imap  + +\r\n\r\n    \" Auto complete contexts\r\n    au filetype todo imap  @ @\r\n\r\n\r\nThe `todo#Complete` function is designed to complete projects (starting by `+`)\r\nand context (starting by `@`). If you use it on a regular word, it will do a\r\nnormal keyword completion (on all buffers).\r\n\r\nIf you try to complete a project, it will propose all projects in all open\r\nbuffers and for each of them, it will show their context and the name of the\r\nbuffers in which they appears in the preview window. It does the same thing\r\nfor context except that it gives in the preview the list of projects existing\r\nin each existing contexts.\r\n\r\n## Hierarchical sort\r\n\r\nThis fork provides a hierarchical sorting function designed to do by project\r\nand\/or by context sorts and a priority sort.\r\n\r\n`sc` : Sort the file by context then by priority\r\n`scp` : Sort the file by context, project then by priority\r\n`sp` : Sort the file by project then by priority\r\n`spc` : Sort the file by project, context then by priority\r\n\r\nThe user can give argument for the two calls to vim sort function by changing\r\nthe following variables:\r\n\r\n    g:Todo_txt_first_level_sort_mode\r\n    g:Todo_txt_second_level_sort_mode\r\n\r\nDefaults values are:\r\n\r\n\r\n    g:Todo_txt_first_level_sort_mode=\"i\"\r\n    g:Todo_txt_second_level_sort_mode=\"i\"\r\n\r\n\r\nFor more information on the available flags see `help :sort`\r\n\r\n## Mappings\r\n\r\nBy default todo-txt.vim set all the mappings secribed in this section. To\r\nprevent this behavior, add the following line to your vimrc\r\n\r\n   let g:Todo_txt_do_not_map=1\r\n\r\n\r\n\r\n`` is \\  by default, so ̀`-s` means you type \\s\r\n\r\n### Sort\r\n\r\n+ `s` : Sort the file by priority\r\n+ `s+` : Sort the file on `+Projects`\r\n+ `s@` : Sort the file on `@Contexts`\r\n+ `sd` : Sort the file on due dates\r\n+ `sc` : Sort the file by context then by priority\r\n+ `scp` : Sort the file by context, project then by priority\r\n+ `sp` : Sort the file by project then by priority\r\n+ `spc` : Sort the file by project, context then by priority\r\n+ `-sd` : Sort the file by due-date. Entries with a due date appears\r\nsorted by at the beginning of the file, the rest of the file is not modified.\r\n\r\nWhen you sort by due dates, at the end of the sort, your cursor will be placed\r\nat the top of the file. This behavior can be set with the following global\r\nvariable :\r\n\r\n    let g:TodoTxtSortDueDateCursorPos = \"top\"\r\n\r\nPossible values are :\r\n\r\n+ `top` (default): The first line of the buffer, i.e. your most outstanding task\r\n+ `lastdue`: The last task with a due:date set\r\n+ `notoverdue`: The first task that is not overdue (requires #13)\r\n+ `bottom`: The last line of the buffer\r\n\r\n### Priorities\r\n\r\n+ `j` : Lower the priority of the current line\r\n+ `k` : Increase the priority of the current line\r\n+ `a` : Add the priority (A) to the current line\r\n+ `b` : Add the priority (B) to the current line\r\n+ `c` : Add the priority (C) to the current line\r\n\r\n### Dates\r\n\r\n+ `d` : Insert the current date\r\n+ `date`  : (Insert mode) Insert the current date\r\n+ `due:`  : (Insert mode) Insert `due:` followed by the current date\r\n+ `DUE:`  : (Insert mode) Insert `DUE:` followed by the current date\r\n\r\n### Done\r\n\r\n\r\n+ `x` : Toggle mark task as done (inserts or remove current\r\n+ date as completion date)\r\n+ `C` : Toggle mark task cancelled\r\n+ `X` : Mark all tasks as completed\r\n+ `D` : Move completed tasks to done file, see [TodoTxt\r\nFiles](#todotxt-files)\r\n\r\nMore at https:\/\/github.com\/dbeniamine\/todo.txt-vim\r\n","4":"# Todo.txt-vim\r\n\r\n        #####                                                #     #\r\n          #    ####  #####   ####     ##### #    # #####     #     # # #    #\r\n          #   #    # #    # #    #      #    #  #    #       #     # # ##  ##\r\n          #   #    # #    # #    #      #     ##     #   ### #     # # # ## #\r\n          #   #    # #    # #    #      #     ##     #        #   #  # #    #\r\n          #   #    # #    # #    # ##   #    #  #    #         # #   # #    #\r\n          #    ####  #####   ####  ##   #   #    #   #          #    # #    #\r\n\r\n                        Efficient Todo.txt management in vim\r\n\r\n## Table of Contents\r\n\r\n1. [Release notes](#release-notes)\r\n2. [Introduction](#introduction)\r\n    1. [Todo.txt rules](#todo.txt-rules)\r\n    2. [Why this Fork ?](#Why-this-fork)\r\n    3. [Installation](#installation)\r\n3. [TodoTxt Files](#todotxt-files)\r\n4. [Completion](#completion)\r\n5. [Hierarchical Sort](#hierarchical-sort)\r\n6. [Mappings](#mappings)\r\n    1. [Sort](#sort)\r\n    2. [Priorities](#priorities)\r\n    3. [Dates](#dates)\r\n    4. [Done](#done)\r\n\r\n## Release notes\r\n\r\n+   V0.8.1 Incorporates yet antoher Fretep work : highlithing for tasks due today.\r\n\r\n+   v0.8 Incorporates Fretep's work on overdue dates (PR#13 and PR#16) witch\r\nremoves python dependency, allow to control the cursor position after a sort by\r\ntodo (see (sort)[#sort] and\/or issue #15) and fixes bug when sorting a file\r\ncontaining only lines with due:date (issue #14).\r\n\r\n+   v0.7.6 Incorporates [Sietse's work](https:\/\/github.com\/sietse\/todo.txt-vim\/commit\/57d45200c8b033d31c9191ee0eb0711c801cdb1d) to make cancel and mark as done mapping repeatable using [vim-repeat](https:\/\/github.com\/tpope\/vim-repeat).\r\n+   v0.7.5 Incorporates [Fievel's work](https:\/\/github.com\/fievel\/todo.txt-vim\/commit\/0863e1434e9a89ace06c4856b6cb32ba9906e3de) to make overduedates work on python3.\r\n+   v0.7.4 includes the overduedate support from Guilherme Victal (see pull\r\n\r\n    [request #45 on freitass version](https:\/\/github.com\/freitass\/todo.txt-vim\/pull\/45)),\r\n    it highlight dates in overdue tasks as an Error. It depends on a\r\n    Python library, however, and as such will only be able to work if your version\r\n    of Vim was compiled with the `+python` option (as most common versions do).\r\n \r\n    If your Vim installation does **not** have Python support, this plugin **will work just fine** but this feature will be disabled.\r\n\r\n\r\n+   Since v0.7.3, `TodoComplete` is replaced by `todo#Complete`, you might need to update your vimrc (see [completion](#completion)).\r\n\r\n## Introduction\r\n\r\nTodo.txt-vim is a plugin to manage todo.txt files it was initially designed by\r\n[Freitass](https:\/\/github.com\/freitass\/todo.txt-vim) then forked and improved\r\nby David Beniamine.\r\n\r\n### Todo.txt rules\r\n\r\nTodo.txt is a standard human readable todo notes file defined [here](http:\/\/todotxt.com):\r\n\r\n\"The todo.txt format is a simple set of\r\n[rules](https:\/\/github.com\/ginatrapani\/todo.txt-cli\/wiki\/The-Todo.txt-Format)\r\nthat make todo.txt both human and machine-readable. The format supports\r\npriorities, creation and completion dates, projects and contexts. That's\r\nall you need to be productive. See an example Todo.txt file\":\r\n\r\n    (A) Call Mom @Phone +Family\r\n    (A) Schedule annual checkup +Health\r\n    (B) Outline chapter 5 +FamilyNovel @Computer\r\n    (C) Add cover sheets @ComputerOffice +FamilyTPSReports\r\n    Plan backyard herb garden @ComputerHome\r\n    Pick up milk @ComputerGroceryStore\r\n    Research self-publishing services +FamilyNovel @ComputerComputer\r\n    x Download Todo.txt mobile app @ComputerPhone\r\n\r\n### Why this fork ?\r\n\r\nThis plugin is a fork of [freitass\r\ntodo.txt-vim](https:\/\/github.com\/freitass\/todo.txt-vim). It add severals cool\r\nfunctionalities including:\r\n\r\n+ [Hierarchical sort](##hierarchical-sort)\r\n+ [A completion function](#completion)\r\n+ [A proper handling of due dates](#dates)\r\n+ [A Flexible file naming](#todotxt-files).\r\n+ Syntax Highlight for couples key:value.\r\n+ `x` is a toggle which allow you to unmark a task as done.\r\n+ `C` Toggle Mark a task cancelled\r\n+ If the current buffer is a done.txt file, the basic sort sorts on\r\n  completion date.\r\n+ ...\r\n\r\n### Installation\r\n\r\n#### Vizardry\r\n\r\nIf you have [Vizardry](https:\/\/github.com\/dbeniamine\/vizardry) installed,\r\nyou can run from vim:\r\n\r\n    :Invoke -u dbeniamine todo.txt-vim\r\n\r\n#### Pathogen install\r\n\r\n    git clone https:\/\/github.com\/dbeniamine\/todo.txt-vim.git ~\/.vim\/bundle\/todo.txt-vim\r\n\r\nThen from vim: `:Helptags` to update the doc\r\n\r\n#### Quick install\r\n\r\n        git clone https:\/\/github.com\/dbeniamine\/todo.txt-vim.git\r\n        cd todo.txt-vim\r\n        cp -r .\/* ~\/.vim\r\n\r\n\r\nIf you want the help installed, run `:helptags ~\/.vim\/doc` inside vim after\r\nhaving copied the files.  Then you will be able to get the commands help with:\r\n`:h todo.txt`\r\n\r\n## TodoTxt Files\r\n\r\nThis plugin provides a Flexible file naming for todo.txt, all the following\r\nnames are recognized as todo:\r\n\r\n    YYYY-MM-[Tt]odo.txt\r\n    YYYY-MM-DD[Tt]odo.txt\r\n    [Tt]odo-YYYY-MM.txt\r\n    [Tt]odo-YYYY-MM-DD.txt\r\n    [Tt]odo.txt\r\n    [Tt]oday.txt\r\n\r\nAnd obviously the same are recognize as done:\r\n\r\n    YYYY-MM-[Dd]one.txt\r\n    YYYY-MM-DD[Dd]one.txt\r\n    [Dd]one-YYYY-MM.txt\r\n    [Dd]one-YYYY-MM-DD.txt\r\n    [Dd]one.txt\r\n    [Dd]one-[Tt]oday.txt\r\n\r\nMoreover, `D` moves the task under the cursor to the done.txt\r\nfile corresponding to the current todo.txt, aka if you are editing\r\n2015-07-07-todo.txt, the done file while be 2015-07-07-done.txt. If you don't\r\nlike this behavior, you can set the default done.txt name:\r\n\r\n    let g:TodoTxtForceDoneName='done.txt'\r\n\r\n## Completion\r\n\r\nThis plugin provides a nice complete function for project and context, to use\r\nit add the following lines to your vimrc:\r\n\r\n    \" Use todo#Complete as the omni complete function for todo files\r\n    au filetype todo setlocal omnifunc=todo#Complete\r\n\r\nYou can also start automatically the completion when entering '+' or '@' by\r\nadding the next lines to your vimrc:\r\n\r\n    \" Auto complete projects\r\n    au filetype todo imap  + +\r\n\r\n    \" Auto complete contexts\r\n    au filetype todo imap  @ @\r\n\r\n\r\nThe `todo#Complete` function is designed to complete projects (starting by `+`)\r\nand context (starting by `@`). If you use it on a regular word, it will do a\r\nnormal keyword completion (on all buffers).\r\n\r\nIf you try to complete a project, it will propose all projects in all open\r\nbuffers and for each of them, it will show their context and the name of the\r\nbuffers in which they appears in the preview window. It does the same thing\r\nfor context except that it gives in the preview the list of projects existing\r\nin each existing contexts.\r\n\r\n## Hierarchical sort\r\n\r\nThis fork provides a hierarchical sorting function designed to do by project\r\nand\/or by context sorts and a priority sort.\r\n\r\n`sc` : Sort the file by context then by priority\r\n`scp` : Sort the file by context, project then by priority\r\n`sp` : Sort the file by project then by priority\r\n`spc` : Sort the file by project, context then by priority\r\n\r\nThe user can give argument for the two calls to vim sort function by changing\r\nthe following variables:\r\n\r\n    g:Todo_txt_first_level_sort_mode\r\n    g:Todo_txt_second_level_sort_mode\r\n\r\nDefaults values are:\r\n\r\n\r\n    g:Todo_txt_first_level_sort_mode=\"i\"\r\n    g:Todo_txt_second_level_sort_mode=\"i\"\r\n\r\n\r\nFor more information on the available flags see `help :sort`\r\n\r\n## Mappings\r\n\r\nBy default todo-txt.vim set all the mappings secribed in this section. To\r\nprevent this behavior, add the following line to your vimrc\r\n\r\n   let g:Todo_txt_do_not_map=1\r\n\r\n\r\n\r\n`` is \\  by default, so ̀`-s` means you type \\s\r\n\r\n### Sort\r\n\r\n+ `s` : Sort the file by priority\r\n+ `s+` : Sort the file on `+Projects`\r\n+ `s@` : Sort the file on `@Contexts`\r\n+ `sd` : Sort the file on due dates\r\n+ `sc` : Sort the file by context then by priority\r\n+ `scp` : Sort the file by context, project then by priority\r\n+ `sp` : Sort the file by project then by priority\r\n+ `spc` : Sort the file by project, context then by priority\r\n+ `-sd` : Sort the file by due-date. Entries with a due date appears\r\nsorted by at the beginning of the file, the rest of the file is not modified.\r\n\r\nWhen you sort by due dates, at the end of the sort, your cursor will be placed\r\nat the top of the file. This behavior can be set with the following global\r\nvariable :\r\n\r\n    let g:TodoTxtSortDueDateCursorPos = \"top\"\r\n\r\nPossible values are :\r\n\r\n+ `top` (default): The first line of the buffer, i.e. your most outstanding task\r\n+ `lastdue`: The last task with a due:date set\r\n+ `notoverdue`: The first task that is not overdue (requires #13)\r\n+ `bottom`: The last line of the buffer\r\n\r\n### Priorities\r\n\r\n+ `j` : Lower the priority of the current line\r\n+ `k` : Increase the priority of the current line\r\n+ `a` : Add the priority (A) to the current line\r\n+ `b` : Add the priority (B) to the current line\r\n+ `c` : Add the priority (C) to the current line\r\n\r\n### Dates\r\n\r\n+ `d` : Insert the current date\r\n+ `date`  : (Insert mode) Insert the current date\r\n+ `due:`  : (Insert mode) Insert `due:` followed by the current date\r\n+ `DUE:`  : (Insert mode) Insert `DUE:` followed by the current date\r\n\r\n### Done\r\n\r\n\r\n+ `x` : Toggle mark task as done (inserts or remove current\r\n+ date as completion date)\r\n+ `C` : Toggle mark task cancelled\r\n+ `X` : Mark all tasks as completed\r\n+ `D` : Move completed tasks to done file, see [TodoTxt\r\nFiles](#todotxt-files)\r\n\r\nMore at https:\/\/github.com\/dbeniamine\/todo.txt-vim\r\n","install_details":"# Installation\r\n\r\n## Vizardry\r\n\r\nIf you have [Vizardry](https:\/\/github.com\/dbeniamine\/vizardry) installed,\r\nyou can run from vim:\r\n\r\n    :Invoke -u dbeniamine todo.txt-vim\r\n\r\n## Pathogen install\r\n\r\n    git clone https:\/\/github.com\/dbeniamine\/todo.txt-vim.git ~\/.vim\/bundle\/todo.txt-vim\r\n\r\nThen from vim: `:Helptags` to update the doc\r\n\r\n## Quick install\r\n\r\n        git clone https:\/\/github.com\/dbeniamine\/todo.txt-vim.git\r\n        cd todo.txt-vim\r\n        cp -r .\/* ~\/.vim\r\n\r\n\r\nIf you want the help installed, run `:helptags ~\/.vim\/doc` inside vim after\r\nhaving copied the files.  Then you will be able to get the commands help with:\r\n`:h todo.txt`\r\n\r\n\r\n","5":"# Installation\r\n\r\n## Vizardry\r\n\r\nIf you have [Vizardry](https:\/\/github.com\/dbeniamine\/vizardry) installed,\r\nyou can run from vim:\r\n\r\n    :Invoke -u dbeniamine todo.txt-vim\r\n\r\n## Pathogen install\r\n\r\n    git clone https:\/\/github.com\/dbeniamine\/todo.txt-vim.git ~\/.vim\/bundle\/todo.txt-vim\r\n\r\nThen from vim: `:Helptags` to update the doc\r\n\r\n## Quick install\r\n\r\n        git clone https:\/\/github.com\/dbeniamine\/todo.txt-vim.git\r\n        cd todo.txt-vim\r\n        cp -r .\/* ~\/.vim\r\n\r\n\r\nIf you want the help installed, run `:helptags ~\/.vim\/doc` inside vim after\r\nhaving copied the files.  Then you will be able to get the commands help with:\r\n`:h todo.txt`\r\n\r\n\r\n","first_name":"David","6":"David","last_name":"Beniamine","7":"Beniamine","releases":[{"0":"5134","vim_version":"7.0","1":"7.0","script_version":"0.8.1","2":"0.8.1","version_comment":"+   V0.8.1 Incorporates yet antoher Fretep work : highlithing for tasks due today.\r\n\r\n+   v0.8 Incorporates Fretep's work on overdue dates (PR#13 and PR#16) witch\r\nremoves python dependency, allow to control the cursor position after a sort by\r\ntodo (see (sort)[#sort] and\/or issue #15) and fixes bug when sorting a file\r\ncontaining only lines with due:date (issue #14).\r\n\r\n+   v0.7.6 Incorporates [Sietse's work](https:\/\/github.com\/sietse\/todo.txt-vim\/commit\/57d45200c8b033d31c9191ee0eb0711c801cdb1d) to make cancel and mark as done mapping repeatable using [vim-repeat](https:\/\/github.com\/tpope\/vim-repeat).\r\n+   v0.7.5 Incorporates [Fievel's work](https:\/\/github.com\/fievel\/todo.txt-vim\/commit\/0863e1434e9a89ace06c4856b6cb32ba9906e3de) to make overduedates work on python3.\r\n+   v0.7.4 includes the overduedate support from Guilherme Victal (see pull\r\n\r\n    [request #45 on freitass version](https:\/\/github.com\/freitass\/todo.txt-vim\/pull\/45)),\r\n    it highlight dates in overdue tasks as an Error. It depends on a\r\n    Python library, however, and as such will only be able to work if your version\r\n    of Vim was compiled with the `+python` option (as most common versions do).\r\n \r\n    If your Vim installation does **not** have Python support, this plugin **will work just fine** but this feature will be disabled.\r\n","3":"+   V0.8.1 Incorporates yet antoher Fretep work : highlithing for tasks due today.\r\n\r\n+   v0.8 Incorporates Fretep's work on overdue dates (PR#13 and PR#16) witch\r\nremoves python dependency, allow to control the cursor position after a sort by\r\ntodo (see (sort)[#sort] and\/or issue #15) and fixes bug when sorting a file\r\ncontaining only lines with due:date (issue #14).\r\n\r\n+   v0.7.6 Incorporates [Sietse's work](https:\/\/github.com\/sietse\/todo.txt-vim\/commit\/57d45200c8b033d31c9191ee0eb0711c801cdb1d) to make cancel and mark as done mapping repeatable using [vim-repeat](https:\/\/github.com\/tpope\/vim-repeat).\r\n+   v0.7.5 Incorporates [Fievel's work](https:\/\/github.com\/fievel\/todo.txt-vim\/commit\/0863e1434e9a89ace06c4856b6cb32ba9906e3de) to make overduedates work on python3.\r\n+   v0.7.4 includes the overduedate support from Guilherme Victal (see pull\r\n\r\n    [request #45 on freitass version](https:\/\/github.com\/freitass\/todo.txt-vim\/pull\/45)),\r\n    it highlight dates in overdue tasks as an Error. It depends on a\r\n    Python library, however, and as such will only be able to work if your version\r\n    of Vim was compiled with the `+python` option (as most common versions do).\r\n \r\n    If your Vim installation does **not** have Python support, this plugin **will work just fine** but this feature will be disabled.\r\n","package":"todo.txt-vim.tgz","4":"todo.txt-vim.tgz","src_id":"25559","5":"25559","creation_date":"1505130146","6":"1505130146"},{"0":"5134","vim_version":"7.0","1":"7.0","script_version":"0.7.3.1","2":"0.7.3.1","version_comment":"+ Cancel tasks with C\r\n+ Full documentation re organisation","3":"+ Cancel tasks with C\r\n+ Full documentation re organisation","package":"todo.txt-vim.tgz","4":"todo.txt-vim.tgz","src_id":"23611","5":"23611","creation_date":"1442934236","6":"1442934236"},{"0":"5134","vim_version":"7.0","1":"7.0","script_version":"0.7.3","2":"0.7.3","version_comment":"+ Use vim autoload to speedup vim start\r\nTodoComplete is now todo#Complete, you might need to update your vimrc","3":"+ Use vim autoload to speedup vim start\r\nTodoComplete is now todo#Complete, you might need to update your vimrc","package":"todo.txt-vim.tgz","4":"todo.txt-vim.tgz","src_id":"23541","5":"23541","creation_date":"1440261891","6":"1440261891"},{"0":"5134","vim_version":"7.0","1":"7.0","script_version":"0.7.2","2":"0.7.2","version_comment":"CHG: More flexible file naming files matching one of the following are todo\r\nfiles:\r\n    YYYY-MM-[Tt]odo.txt\r\n    YYYY-MM-DD[Tt]odo.txt\r\n    [Tt]odo-YYYY-MM.txt\r\n    [Tt]odo-YYYY-MM-DD.txt\r\n    [Tt]odo.txt\r\n    [Tt]oday.txt\r\n    YYYY-MM-[Dd]one.txt\r\n    YYYY-MM-DD[Dd]one.txt\r\n    [Dd]one-YYYY-MM.txt\r\n    [Dd]one-YYYY-MM-DD.txt\r\n    [Dd]one.txt\r\n    [Dd]one-[Tt]oday.txt\r\nMoreover, remove complete tasks (D) moves the task to the\r\ndone.txt file corresponding to the current todo.txt, aka if you are editing\r\n2015-07-07-todo.txt, the done file while be 2015-07-07-done.txt.\r\nThis behaviour can be cancelled by fixing the done filename using\r\ng:TodoTxtForceDoneName\r\nFIX: Bug while completing empty file ","3":"CHG: More flexible file naming files matching one of the following are todo\r\nfiles:\r\n    YYYY-MM-[Tt]odo.txt\r\n    YYYY-MM-DD[Tt]odo.txt\r\n    [Tt]odo-YYYY-MM.txt\r\n    [Tt]odo-YYYY-MM-DD.txt\r\n    [Tt]odo.txt\r\n    [Tt]oday.txt\r\n    YYYY-MM-[Dd]one.txt\r\n    YYYY-MM-DD[Dd]one.txt\r\n    [Dd]one-YYYY-MM.txt\r\n    [Dd]one-YYYY-MM-DD.txt\r\n    [Dd]one.txt\r\n    [Dd]one-[Tt]oday.txt\r\nMoreover, remove complete tasks (D) moves the task to the\r\ndone.txt file corresponding to the current todo.txt, aka if you are editing\r\n2015-07-07-todo.txt, the done file while be 2015-07-07-done.txt.\r\nThis behaviour can be cancelled by fixing the done filename using\r\ng:TodoTxtForceDoneName\r\nFIX: Bug while completing empty file ","package":"todo.txt-vim.tar.gz","4":"todo.txt-vim.tar.gz","src_id":"23456","5":"23456","creation_date":"1436346362","6":"1436346362"},{"0":"5134","vim_version":"7.0","1":"7.0","script_version":"v0.7.1","2":"v0.7.1","version_comment":"FIX: Typo in sort function\r\nFIX: Keyword completion\r\nCHG: Sort done.txt by completion date","3":"FIX: Typo in sort function\r\nFIX: Keyword completion\r\nCHG: Sort done.txt by completion date","package":"todo.txt-vim.tar.gz","4":"todo.txt-vim.tar.gz","src_id":"23444","5":"23444","creation_date":"1436107610","6":"1436107610"},{"0":"5134","vim_version":"7.0","1":"7.0","script_version":"0.7","2":"0.7","version_comment":"Due dates sort and syntax highlights for couples key:value  ","3":"Due dates sort and syntax highlights for couples key:value  ","package":"todo.txt-vim.tar.gz","4":"todo.txt-vim.tar.gz","src_id":"23443","5":"23443","creation_date":"1436101732","6":"1436101732"},{"0":"5134","vim_version":"7.0","1":"7.0","script_version":"0.6","2":"0.6","version_comment":"Completion is now on all open buffer.","3":"Completion is now on all open buffer.","package":"todo.txt-vim.tgz","4":"todo.txt-vim.tgz","src_id":"23373","5":"23373","creation_date":"1433895343","6":"1433895343"},{"0":"5134","vim_version":"7.0","1":"7.0","script_version":"0.5","2":"0.5","version_comment":"Initial upload","3":"Initial upload","package":"todo.txt-vim.tar.gz","4":"todo.txt-vim.tar.gz","src_id":"23025","5":"23025","creation_date":"1426368129","6":"1426368129"}]},"5133":{"script_id":"5133","0":"5133","script_name":"vim-compile","1":"vim-compile","script_type":"ftplugin","2":"ftplugin","summary":"Yet another compile plugin for vim","3":"Yet another compile plugin for vim","description":"# Readme\r\n\r\n## What is this plugin ?\r\n\r\nThis plugin is a flexible helper for compiling directly from vim. Compilation\r\nand execution command are run using the first avalaible of the following\r\noptions:\r\n\r\n1. Custom function (see [custom starter](#starter) )\r\n2. [Dispatch](https:\/\/github.com\/tpope\/vim-dispatch)\r\n3. Vim shell escape (`:make` and `:!`)\r\n\r\nIt also provides an easy and unified way to set and use compilers, and\r\nnatively integrate with [vim-latex-suite](http:\/\/vim-latex.sourceforge.net\/)\r\ncompilation settings.\r\n\r\n## What is new ?\r\n\r\n+   v0.3.1 allows the user to define a cleaning command to use with the custom\r\n    builder. It also adds a few bug fix and two new mappings (clean and\r\n    compile, clean compile and execute, see [mappings](#mappings))\r\n\r\n+   Since V0.3, you can now define a custom builder for instance ̀`build.sh`\r\n    with custom build and execute command. Such a builder will be always chosen\r\n    if available, see [custom builder](#builder)\r\n\r\n+   Since v0.2.3, vim-compile will try to retrieve the latex main file for\r\n    compilation and execution.\r\n\r\n    If latex-suite is activated, it search for a `*.latexmain` file, else it\r\n    looks for a root file line, similar to the following:\r\n\r\n        %!TEX root=my_main_file.tex\r\n+   *Note* Since v0.2.2, you need to use `function()` to set a custom starter\r\n    function.\r\n+   Since v0.2 you can define a custom function to launch commands (compilation\r\n    and exectuion), see [custom starter](#starter).\r\n\r\n## Usage\r\n\r\n\r\nThis plugin provides an easy way to compile and execute any file.\r\n\r\nSome compilation and executions rules are predefined for a few filetypes, but the\r\nuser can redefine them, see [rules](#rules) for how.\r\n\r\nIf a `Makefile` exists in the working directory, `make` will be prefered over\r\nthe predefined rule. The same way, if a `build.xml` file exists, `ant` will be\r\nprefered. The user can also define a custom builder that will always be\r\nprefered to `make` and `ant`, see [custom builder](#builder)\r\n\r\nFor latex files, if [vim-latex-suite](http:\/\/vim-latex.sourceforge.net\/) is\r\npresent, the user can choose to overwrite predefined rules with vim-late-suite settings.\r\nVim-compile will always try to guess if the current file is part of a bigger\r\nlatex project either using `*.latexmain` file (see help latex-master-file) or\r\nby searching for a line ̀like `%!TEX root=my_main_file.tex` in the current\r\nfile. For these kind of project, vim should be open from the directory\r\ncontaining the main file.\r\n\r\n### Mappings\r\n\r\nSome useful Mappings are defined:\r\n\r\n+ `m` Compile\r\n\r\n+ `e` Execute\r\n\r\n+ `me` Compile and execute\r\n\r\n+ `mc` Clean\r\n\r\n+ `mcm` Clean and compile\r\n\r\n+ `mce` Clean, Compile and execute\r\n\r\n\r\nSome of the mappings are only working with Makefiles:\r\n\r\n+ `mj` Make parallel\r\n\r\n+ `mi` Make install\r\n\r\n+ `mij` Make parallel and make install parallel\r\n\r\n+ `mje` Make parallel and execute\r\n\r\n\r\n\r\n## Configuration\r\n\r\n\r\n### Rules\r\n\r\nTwo dictionaries (see :help Dictionary) can be used to modify or add\r\ncompilation and execution rules.\r\nFor instances adding the following to your vimrc will change the compilation\r\nand execution rules for pandoc files\r\n\r\n    let g:VimCompileExecutors={'pandoc' : \"firefox %:t:r.html > \/dev\/null 2>&1\",}\r\n    let g:VimCompileCompiler={'pandoc' : \"pandoc --smart --standalone --mathml --listings % > %:t:r.html\",}\r\n\r\nThe following variable gives the default execution rule if none are defined\r\nfor the filetype:\r\n\r\n    let g:VimCompileDefaultExecutor=\".\/%\"\r\n\r\nTo overwrite rules with LaTeX Suite settings, add the following to your vimrc:\r\n\r\n    let g:VimCompileUseLatexSuite=1\r\n\r\n### Starter\r\n\r\nA custom starter function (responsible for starting compilation and execution)\r\ncan be provided by setting the following variable:\r\n\r\n     let g:VimCompileCustomStarter=function(\"MyStarterFunction\")\r\n\r\nA starter functions takes two arguments:\r\n\r\n+ the first is the command to execute\r\n+ the second is a character:\r\n    + `'m'` indicate that we are doing an actual compilation\r\n    + `'e'` means that we run a custom command.\r\n\r\nFor a better understanding of starter functions, there is the default one:\r\n\r\n    \" Default command starter {{{2\r\n    \" Start a command using Dispatch if available or the shell escape\r\n    \" Arguments: cmd: the command to execute\r\n    \"            type: 'm' if we are doing a compilation, 'e' otherwise\r\n    function! VimCompileDefaultStartCmd(cmd,type)\r\n        if (a:type=='m') \" Compilation: use makeprg and :Dispatch or :make\r\n            let &makeprg=a:cmd\r\n            if exists(\"g:loaded_dispatch\")\r\n                let l:launcher=\":Dispatch\"\r\n            else\r\n                let l:launcher=\":make\"\r\n            endif\r\n        else \" Normal command\r\n            let l:cmd=a:cmd\r\n            if exists(\"g:loaded_dispatch\")\r\n                let l:launcher=\":Start\"\r\n                if (a:cmd=~'^.*&\\s*$') \" Let Dispatch handle background commands\r\n                    let l:cmd=substitute(a:cmd,'&\\s*$','','')\r\n                    let l:launcher.=\"!\"\r\n                endif\r\n            else \" Simple shell escape\r\n                let l:launcher=\":!\"\r\n            endif\r\n            let l:launcher.=\" \".l:cmd\r\n        endif\r\n        execute l:launcher\r\n    endfunction\r\n\r\n### Builder\r\n\r\nVim-compile allow you to define a custom compilation system which will always\r\nbe used if available. For instance if you have a script called `build.sh`, you\r\ncan define the following variables in your vimrc (adapt to your needs):\r\n\r\n    let g:VimCompileCustomBuilder='build.sh'\r\n    let g:VimCompileCustomBuilderCompile='.\/build.sh'\r\n\r\nYou can also define an executor command using this build system:\r\n\r\n    let g:VimCompileCustomBuilderExec='.\/build.sh view'\r\n\r\nAnd of course of command for cleanning the compilation stuff\r\n\r\n    let g:VimCompileCustomBuilderClean='.\/build.sh clean'\r\nMore infos at https:\/\/github.com\/dbeniamine\/vim-compile\r\n","4":"# Readme\r\n\r\n## What is this plugin ?\r\n\r\nThis plugin is a flexible helper for compiling directly from vim. Compilation\r\nand execution command are run using the first avalaible of the following\r\noptions:\r\n\r\n1. Custom function (see [custom starter](#starter) )\r\n2. [Dispatch](https:\/\/github.com\/tpope\/vim-dispatch)\r\n3. Vim shell escape (`:make` and `:!`)\r\n\r\nIt also provides an easy and unified way to set and use compilers, and\r\nnatively integrate with [vim-latex-suite](http:\/\/vim-latex.sourceforge.net\/)\r\ncompilation settings.\r\n\r\n## What is new ?\r\n\r\n+   v0.3.1 allows the user to define a cleaning command to use with the custom\r\n    builder. It also adds a few bug fix and two new mappings (clean and\r\n    compile, clean compile and execute, see [mappings](#mappings))\r\n\r\n+   Since V0.3, you can now define a custom builder for instance ̀`build.sh`\r\n    with custom build and execute command. Such a builder will be always chosen\r\n    if available, see [custom builder](#builder)\r\n\r\n+   Since v0.2.3, vim-compile will try to retrieve the latex main file for\r\n    compilation and execution.\r\n\r\n    If latex-suite is activated, it search for a `*.latexmain` file, else it\r\n    looks for a root file line, similar to the following:\r\n\r\n        %!TEX root=my_main_file.tex\r\n+   *Note* Since v0.2.2, you need to use `function()` to set a custom starter\r\n    function.\r\n+   Since v0.2 you can define a custom function to launch commands (compilation\r\n    and exectuion), see [custom starter](#starter).\r\n\r\n## Usage\r\n\r\n\r\nThis plugin provides an easy way to compile and execute any file.\r\n\r\nSome compilation and executions rules are predefined for a few filetypes, but the\r\nuser can redefine them, see [rules](#rules) for how.\r\n\r\nIf a `Makefile` exists in the working directory, `make` will be prefered over\r\nthe predefined rule. The same way, if a `build.xml` file exists, `ant` will be\r\nprefered. The user can also define a custom builder that will always be\r\nprefered to `make` and `ant`, see [custom builder](#builder)\r\n\r\nFor latex files, if [vim-latex-suite](http:\/\/vim-latex.sourceforge.net\/) is\r\npresent, the user can choose to overwrite predefined rules with vim-late-suite settings.\r\nVim-compile will always try to guess if the current file is part of a bigger\r\nlatex project either using `*.latexmain` file (see help latex-master-file) or\r\nby searching for a line ̀like `%!TEX root=my_main_file.tex` in the current\r\nfile. For these kind of project, vim should be open from the directory\r\ncontaining the main file.\r\n\r\n### Mappings\r\n\r\nSome useful Mappings are defined:\r\n\r\n+ `m` Compile\r\n\r\n+ `e` Execute\r\n\r\n+ `me` Compile and execute\r\n\r\n+ `mc` Clean\r\n\r\n+ `mcm` Clean and compile\r\n\r\n+ `mce` Clean, Compile and execute\r\n\r\n\r\nSome of the mappings are only working with Makefiles:\r\n\r\n+ `mj` Make parallel\r\n\r\n+ `mi` Make install\r\n\r\n+ `mij` Make parallel and make install parallel\r\n\r\n+ `mje` Make parallel and execute\r\n\r\n\r\n\r\n## Configuration\r\n\r\n\r\n### Rules\r\n\r\nTwo dictionaries (see :help Dictionary) can be used to modify or add\r\ncompilation and execution rules.\r\nFor instances adding the following to your vimrc will change the compilation\r\nand execution rules for pandoc files\r\n\r\n    let g:VimCompileExecutors={'pandoc' : \"firefox %:t:r.html > \/dev\/null 2>&1\",}\r\n    let g:VimCompileCompiler={'pandoc' : \"pandoc --smart --standalone --mathml --listings % > %:t:r.html\",}\r\n\r\nThe following variable gives the default execution rule if none are defined\r\nfor the filetype:\r\n\r\n    let g:VimCompileDefaultExecutor=\".\/%\"\r\n\r\nTo overwrite rules with LaTeX Suite settings, add the following to your vimrc:\r\n\r\n    let g:VimCompileUseLatexSuite=1\r\n\r\n### Starter\r\n\r\nA custom starter function (responsible for starting compilation and execution)\r\ncan be provided by setting the following variable:\r\n\r\n     let g:VimCompileCustomStarter=function(\"MyStarterFunction\")\r\n\r\nA starter functions takes two arguments:\r\n\r\n+ the first is the command to execute\r\n+ the second is a character:\r\n    + `'m'` indicate that we are doing an actual compilation\r\n    + `'e'` means that we run a custom command.\r\n\r\nFor a better understanding of starter functions, there is the default one:\r\n\r\n    \" Default command starter {{{2\r\n    \" Start a command using Dispatch if available or the shell escape\r\n    \" Arguments: cmd: the command to execute\r\n    \"            type: 'm' if we are doing a compilation, 'e' otherwise\r\n    function! VimCompileDefaultStartCmd(cmd,type)\r\n        if (a:type=='m') \" Compilation: use makeprg and :Dispatch or :make\r\n            let &makeprg=a:cmd\r\n            if exists(\"g:loaded_dispatch\")\r\n                let l:launcher=\":Dispatch\"\r\n            else\r\n                let l:launcher=\":make\"\r\n            endif\r\n        else \" Normal command\r\n            let l:cmd=a:cmd\r\n            if exists(\"g:loaded_dispatch\")\r\n                let l:launcher=\":Start\"\r\n                if (a:cmd=~'^.*&\\s*$') \" Let Dispatch handle background commands\r\n                    let l:cmd=substitute(a:cmd,'&\\s*$','','')\r\n                    let l:launcher.=\"!\"\r\n                endif\r\n            else \" Simple shell escape\r\n                let l:launcher=\":!\"\r\n            endif\r\n            let l:launcher.=\" \".l:cmd\r\n        endif\r\n        execute l:launcher\r\n    endfunction\r\n\r\n### Builder\r\n\r\nVim-compile allow you to define a custom compilation system which will always\r\nbe used if available. For instance if you have a script called `build.sh`, you\r\ncan define the following variables in your vimrc (adapt to your needs):\r\n\r\n    let g:VimCompileCustomBuilder='build.sh'\r\n    let g:VimCompileCustomBuilderCompile='.\/build.sh'\r\n\r\nYou can also define an executor command using this build system:\r\n\r\n    let g:VimCompileCustomBuilderExec='.\/build.sh view'\r\n\r\nAnd of course of command for cleanning the compilation stuff\r\n\r\n    let g:VimCompileCustomBuilderClean='.\/build.sh clean'\r\nMore infos at https:\/\/github.com\/dbeniamine\/vim-compile\r\n","install_details":"# Install\r\n\r\n## Vizardry\r\n\r\nIf you have [Vizardry](https:\/\/github.com\/dbeniamine\/vizardry) installed, you\r\ncan run from vim:\r\n\r\n    :Invoke -u dbeniamine vim-compile\r\n\r\n## Pathogen install\r\n\r\n    git clone https:\/\/github.com\/dbeniamine\/vim-compile.git ~\/.vim\/bundle\/vim-compile\r\n\r\n## Quick install\r\n\r\n    git clone https:\/\/github.com\/dbeniamine\/vim-compile.git\r\n    cd vim-compile\/\r\n    cp -r .\/* ~\/.vim\r\n","5":"# Install\r\n\r\n## Vizardry\r\n\r\nIf you have [Vizardry](https:\/\/github.com\/dbeniamine\/vizardry) installed, you\r\ncan run from vim:\r\n\r\n    :Invoke -u dbeniamine vim-compile\r\n\r\n## Pathogen install\r\n\r\n    git clone https:\/\/github.com\/dbeniamine\/vim-compile.git ~\/.vim\/bundle\/vim-compile\r\n\r\n## Quick install\r\n\r\n    git clone https:\/\/github.com\/dbeniamine\/vim-compile.git\r\n    cd vim-compile\/\r\n    cp -r .\/* ~\/.vim\r\n","first_name":"David","6":"David","last_name":"Beniamine","7":"Beniamine","releases":[{"0":"5133","vim_version":"7.0","1":"7.0","script_version":"0.3.2","2":"0.3.2","version_comment":"+ FIX trailing endif in compile function\r\n+ Use autoload to speedup vim startup","3":"+ FIX trailing endif in compile function\r\n+ Use autoload to speedup vim startup","package":"vim-compile.tgz","4":"vim-compile.tgz","src_id":"23540","5":"23540","creation_date":"1440260145","6":"1440260145"},{"0":"5133","vim_version":"7.0","1":"7.0","script_version":"v0.3.1.1","2":"v0.3.1.1","version_comment":"You can now define a custom builder for instance ̀build.sh with custom build execute and clean command. Such a builder will be always chosen if available, see custom builder","3":"You can now define a custom builder for instance ̀build.sh with custom build execute and clean command. Such a builder will be always chosen if available, see custom builder","package":"vim-compile.tar.gz","4":"vim-compile.tar.gz","src_id":"23428","5":"23428","creation_date":"1435682154","6":"1435682154"},{"0":"5133","vim_version":"7.0","1":"7.0","script_version":"0.2.3","2":"0.2.3","version_comment":"Since v0.2.3, vim-compile will try to retrieve the latex main file for compilation and execution.\r\nIf latex-suite is activated, it search for a *.latexmain file, else it looks for a root file line, similar to the following:\r\n%!TEX root=my_main_file.tex\r\n","3":"Since v0.2.3, vim-compile will try to retrieve the latex main file for compilation and execution.\r\nIf latex-suite is activated, it search for a *.latexmain file, else it looks for a root file line, similar to the following:\r\n%!TEX root=my_main_file.tex\r\n","package":"vim-compile.tar.gz","4":"vim-compile.tar.gz","src_id":"23360","5":"23360","creation_date":"1433625225","6":"1433625225"},{"0":"5133","vim_version":"7.0","1":"7.0","script_version":"0.2.2","2":"0.2.2","version_comment":"+ Use makeprg for compilation (Dispatch and :make)\r\n+ Use funcref for Custom Starter function instead of the ugly if\r\n+ Other code cleaning\r\n\r\nWarning: Since v0.2.2 you need to use function() to set a custom starter function !\r\n\r\n","3":"+ Use makeprg for compilation (Dispatch and :make)\r\n+ Use funcref for Custom Starter function instead of the ugly if\r\n+ Other code cleaning\r\n\r\nWarning: Since v0.2.2 you need to use function() to set a custom starter function !\r\n\r\n","package":"vim-compile.tar.gz","4":"vim-compile.tar.gz","src_id":"23299","5":"23299","creation_date":"1432146780","6":"1432146780"},{"0":"5133","vim_version":"7.0","1":"7.0","script_version":"0.2.1","2":"0.2.1","version_comment":"Removed debug echo & sleep","3":"Removed debug echo & sleep","package":"vim-compile.tar.gz","4":"vim-compile.tar.gz","src_id":"23298","5":"23298","creation_date":"1432129839","6":"1432129839"},{"0":"5133","vim_version":"7.0","1":"7.0","script_version":"0.2","2":"0.2","version_comment":"This version provides the user the ability to define a custom starter\r\nfunction. This function is responsible for starting compilation and execution\r\ncommand. See :help VimCompile-configuration\r\n","3":"This version provides the user the ability to define a custom starter\r\nfunction. This function is responsible for starting compilation and execution\r\ncommand. See :help VimCompile-configuration\r\n","package":"vim-compile.tar.gz","4":"vim-compile.tar.gz","src_id":"23297","5":"23297","creation_date":"1432129242","6":"1432129242"},{"0":"5133","vim_version":"7.0","1":"7.0","script_version":"0.1.1","2":"0.1.1","version_comment":"Small bug fix, cleaner start function + Compatibility with vimux","3":"Small bug fix, cleaner start function + Compatibility with vimux","package":"vim-compile.tar.gz","4":"vim-compile.tar.gz","src_id":"23296","5":"23296","creation_date":"1432039499","6":"1432039499"},{"0":"5133","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"vim-compile.tar.gz","4":"vim-compile.tar.gz","src_id":"23024","5":"23024","creation_date":"1426367870","6":"1426367870"}]},"5132":{"script_id":"5132","0":"5132","script_name":"vim-mail","1":"vim-mail","script_type":"ftplugin","2":"ftplugin","summary":"A plugin to ease mail redaction from vim","3":"A plugin to ease mail redaction from vim","description":"# Readme\r\n\r\n## What is this plugin ?\r\n\r\nThis plugin is a small helper for writing mail from vim, I designed it using\r\nmutt but it should work with other clients. I recommend to use it in\r\ncombination with [CheckAttach](https:\/\/github.com\/chrisbra\/CheckAttach).\r\n\r\n## Features\r\n\r\nThis plugin provides the following features\r\n\r\n### Contact completion\r\n\r\nThe contact completion is designed for\r\n[pycarddav](https:\/\/pypi.python.org\/pypi\/pyCardDAV), however it is possible to\r\nuse any external tools, see [address book\r\nconfiguration](#address-book-configuration).\r\n\r\nTo search your address book from vim:\r\n\r\n+   While writing a mail, in insert mode, type:\r\n\r\n        a\r\n\r\n    or (using omnifunc)\r\n\r\n        \r\n\r\n+   While editing any other file:\r\n\r\n    As the previous mapping are only set for mail files, you need to set the\r\n    completefunc (using omnifunc would be a bad idea):\r\n\r\n        set completefunc=vimmail#completion#CompleteAddr\r\n\r\n    Then use `` (in insert mode) to trigger contact completion.\r\n\r\nIt will search for the word under the cursor in your contact list.\r\n\r\nIf you are currently in a From,To,CC or Bcc line, only mail addresses will\r\nbe proposed, else all the match will appear. More details will appear in\r\nthe preview window including contact name, type of the entry (mail, cell,\r\nphone etc.).\r\n\r\nTo synchronise your address book, in a mail, in normal mode, type:\r\n\r\n    a\r\n\r\n### Redaction\r\n\r\n####   Cursor initial position\r\n\r\nBy default vim-mail place your cursor at the beginning of the mail (right\r\nafter the headers) adds a blank line and switch to insert mode. This\r\nbehavior can be modified through a series of flags:\r\n\r\nThe available flags are:\r\n\r\nFlag | Meaning\r\n-----|----------------------------------------------------------------------\r\n`i`  | insert mode\r\n`o`  | Add new line after cursor\r\n`O`  | Add new line before cursor\r\n`A`  | Place cursor at the end of the line\r\n`W`  | Start on second word (a.k.a first address of field \/ word of subject)\r\n`t`  | top (Right after headers)\r\n`b`  | Bottom (After last message)\r\n`F`  | From field\r\n`T`  | To field\r\n`C`  | Cc field\r\n`B`  | Bcc field\r\n`S`  | Subject field\r\n\r\n##### Examples\r\n\r\nAdding the following line to your vimrc will make you start at the end of\r\nthe subject line:\r\n\r\n    let g:VimMailStartFlags=\"SAi\"\r\n\r\nOr if you want to start at the end of the mail:\r\n\r\n    let g:VimMailStartFlags=\"boi\"\r\n\r\n#### Easy spelllang switch\r\n\r\nWhile writing mails, I often need to do switch the spell lang which can be\r\nannoying, so this plugin provide an easy way to do it. Just type:\r\n\r\n    l\r\n\r\nand the plugin will switch the spelllang using a list of allowed languages.  \r\nIf the current spellang is the last allowed, it will disable spell, hit\r\n\r\n    l\r\n\r\nonce more and you will restart with the first lang.\r\nYou can set the list of allowed langs in your vimrc:\r\n\r\n    let g:VimSpellLangs=['fr', 'en', 'sp']\r\n\r\nThe default langs are french, english.\r\n\r\nThis will work for any filetype as it can be usefull for many other kind of\r\nfiles.\r\n\r\n#### Messages folds\r\n\r\nA folding method which allows you to open are close the messages of the\r\nconversation is provided.\r\n\r\n### Quick in-mail navigation\r\n\r\nWith this plugin, you can easily navigate through the different par of the\r\nmail using the following mappings:\r\n\r\n+   Headers\r\n\r\n    Mapping          | Effect\r\n    -----------------|--------------------------\r\n    `f` | Go to the From field\r\n    `b` | Go to the Bcc field\r\n    `c` | Go to the Cc field\r\n    `s` | Go to the SUbject field\r\n    `R` | Go to the Reply-To field\r\n    `t` | Go to the Reply-To field\r\n\r\n+   Conversation\r\n\r\n    Mapping          | Effect\r\n    -----------------|----------------------------------------------\r\n    `B` | Go to the first line (after headers)\r\n    `E` | Go to the first line after the conversation\r\n    `r` | Go to the first message of the conversation\r\n    `r2`| Go to the second message of the conversation\r\n    `r3`| Go to the third message of the conversation\r\n    `r4`| Go to the fourth message of the conversation\r\n    `S` | Go to your signature\r\n\r\n\r\n### Launch mail client\r\n\r\nOne of Mutt main drawbacks is that you can't access your mailbox while\r\nwriting mails, good news everyone, with vim-mail you can open mutt in RO\r\nmode easily by typing\r\n\r\n    M\r\n\r\n### Send file from Vim\r\n\r\nWhen you are vimming at one point, you might want to send the file you are\r\nworking on. Leaving vim to send a mail from vim is so annoying, happily there\r\nis the solution just type: `m` and VimMail will pipe the file to\r\nmutt.\r\n\r\n## Mappings\r\n\r\nAll mappings can be disabled by adding the following line to your vimrc:\r\n\r\n    let g:VimMailDoNotMap=1\r\n\r\n\r\n+   On any file\r\n\r\n    Mapping          | Effect\r\n    -----------------|----------------------------------------------\r\n    `m` | Send the current buffer\r\n    `l` | Switch spelllang\r\n    `M` | Open the mail client\r\n\r\n+   On mail only\r\n\r\n    Mapping          | Effect\r\n    -----------------|----------------------------------------------\r\n    `a` | Search the word before cursor as a contact\r\n    `f` | Go to the From field\r\n    `b` | Go to the Bcc field\r\n    `c` | Go to the Cc field\r\n    `s` | Go to the SUbject field\r\n    `R` | Go to the Reply-To field\r\n    `t` | Go to the Reply-To field\r\n    `r` | Go to the first message of the conversation\r\n    `r2`| Go to the second message of the conversation\r\n    `r3`| Go to the third message of the conversation\r\n    `r4`| Go to the fourth message of the conversation\r\n    `S` | Go to your signature\r\n\r\n## CONFIGURATION\r\n\r\n### Address book configuration\r\n\r\nIt is possible to use another address book than pycard by setting the\r\nfollowing variables:\r\n\r\n    let g:VimMailContactSyncCmd=\"my_synchronisation_cmd\"\r\n    let g:VimMailContactQueryCmd=\"my_query_cmd\"\r\n\r\nThe only restriction is that the query command should give an output similar\r\nto pc_query output, aka something like:\r\n\r\n    Name: Someone\r\n    Tel (CELL): 000000000\r\n    EMAIL : someone@foo.bar\r\n    Name: Someone else\r\n    TEL: 0000000\r\n    EMAIL (Work): Someone.else@work.com\r\n    EMAIL (Perso): Someone.else@dummyprovider.com\r\n\r\nThe fields between parentheses are optional.\r\n\r\nIf you don't see the preview while using contact completion, add the following\r\nto your vimrc (see |completeopt| |preview| ):\r\n\r\n    set completeopt=preview\r\n\r\nIf you don't want this completion you can either not use the plugin or add\r\nthe following line to your vimrc:\r\n\r\n    let g:VimMailDontUseComplete=1\r\n\r\nBy default, the contact completion appends the query to the result list, you\r\ncan disable this feature:\r\n\r\n    let g:VimMailDoNotAppendQueryToResults\r\n\r\n### Spell\r\n\r\nSetting the list of possible spell langs:\r\n\r\n    let g:VimSpellLangs=['fr', 'en', 'sp']\r\n\r\n### Folds\r\n\r\nTo disable message folds, add the following line to your vimrc:\r\n\r\n    let g:VimMailDoNotFold=1\r\n\r\n### Mail Client\r\n\r\nYou can set the mail client command to your launcher script by adding to your\r\nvimrc something like:\r\n\r\n    let g:VimMailClient=\"\/path\/to\/your\/launcher\"\r\n\r\nIf you are not using mutt, or want to customize the send mail command, just\r\nadd something like that to your vimrc (this is the default command):\r\n\r\n    let g:VimMailSendCmd=\":! mutt -a %\"\r\n\r\n## License\r\n\r\nThis plugin is distributed under GPL Licence v3.0, see\r\nhttps:\/\/www.gnu.org\/licenses\/gpl.txt\r\n\r\nMore infos at https:\/\/github.com\/dbeniamine\/vim-mail\r\n","4":"# Readme\r\n\r\n## What is this plugin ?\r\n\r\nThis plugin is a small helper for writing mail from vim, I designed it using\r\nmutt but it should work with other clients. I recommend to use it in\r\ncombination with [CheckAttach](https:\/\/github.com\/chrisbra\/CheckAttach).\r\n\r\n## Features\r\n\r\nThis plugin provides the following features\r\n\r\n### Contact completion\r\n\r\nThe contact completion is designed for\r\n[pycarddav](https:\/\/pypi.python.org\/pypi\/pyCardDAV), however it is possible to\r\nuse any external tools, see [address book\r\nconfiguration](#address-book-configuration).\r\n\r\nTo search your address book from vim:\r\n\r\n+   While writing a mail, in insert mode, type:\r\n\r\n        a\r\n\r\n    or (using omnifunc)\r\n\r\n        \r\n\r\n+   While editing any other file:\r\n\r\n    As the previous mapping are only set for mail files, you need to set the\r\n    completefunc (using omnifunc would be a bad idea):\r\n\r\n        set completefunc=vimmail#completion#CompleteAddr\r\n\r\n    Then use `` (in insert mode) to trigger contact completion.\r\n\r\nIt will search for the word under the cursor in your contact list.\r\n\r\nIf you are currently in a From,To,CC or Bcc line, only mail addresses will\r\nbe proposed, else all the match will appear. More details will appear in\r\nthe preview window including contact name, type of the entry (mail, cell,\r\nphone etc.).\r\n\r\nTo synchronise your address book, in a mail, in normal mode, type:\r\n\r\n    a\r\n\r\n### Redaction\r\n\r\n####   Cursor initial position\r\n\r\nBy default vim-mail place your cursor at the beginning of the mail (right\r\nafter the headers) adds a blank line and switch to insert mode. This\r\nbehavior can be modified through a series of flags:\r\n\r\nThe available flags are:\r\n\r\nFlag | Meaning\r\n-----|----------------------------------------------------------------------\r\n`i`  | insert mode\r\n`o`  | Add new line after cursor\r\n`O`  | Add new line before cursor\r\n`A`  | Place cursor at the end of the line\r\n`W`  | Start on second word (a.k.a first address of field \/ word of subject)\r\n`t`  | top (Right after headers)\r\n`b`  | Bottom (After last message)\r\n`F`  | From field\r\n`T`  | To field\r\n`C`  | Cc field\r\n`B`  | Bcc field\r\n`S`  | Subject field\r\n\r\n##### Examples\r\n\r\nAdding the following line to your vimrc will make you start at the end of\r\nthe subject line:\r\n\r\n    let g:VimMailStartFlags=\"SAi\"\r\n\r\nOr if you want to start at the end of the mail:\r\n\r\n    let g:VimMailStartFlags=\"boi\"\r\n\r\n#### Easy spelllang switch\r\n\r\nWhile writing mails, I often need to do switch the spell lang which can be\r\nannoying, so this plugin provide an easy way to do it. Just type:\r\n\r\n    l\r\n\r\nand the plugin will switch the spelllang using a list of allowed languages.  \r\nIf the current spellang is the last allowed, it will disable spell, hit\r\n\r\n    l\r\n\r\nonce more and you will restart with the first lang.\r\nYou can set the list of allowed langs in your vimrc:\r\n\r\n    let g:VimSpellLangs=['fr', 'en', 'sp']\r\n\r\nThe default langs are french, english.\r\n\r\nThis will work for any filetype as it can be usefull for many other kind of\r\nfiles.\r\n\r\n#### Messages folds\r\n\r\nA folding method which allows you to open are close the messages of the\r\nconversation is provided.\r\n\r\n### Quick in-mail navigation\r\n\r\nWith this plugin, you can easily navigate through the different par of the\r\nmail using the following mappings:\r\n\r\n+   Headers\r\n\r\n    Mapping          | Effect\r\n    -----------------|--------------------------\r\n    `f` | Go to the From field\r\n    `b` | Go to the Bcc field\r\n    `c` | Go to the Cc field\r\n    `s` | Go to the SUbject field\r\n    `R` | Go to the Reply-To field\r\n    `t` | Go to the Reply-To field\r\n\r\n+   Conversation\r\n\r\n    Mapping          | Effect\r\n    -----------------|----------------------------------------------\r\n    `B` | Go to the first line (after headers)\r\n    `E` | Go to the first line after the conversation\r\n    `r` | Go to the first message of the conversation\r\n    `r2`| Go to the second message of the conversation\r\n    `r3`| Go to the third message of the conversation\r\n    `r4`| Go to the fourth message of the conversation\r\n    `S` | Go to your signature\r\n\r\n\r\n### Launch mail client\r\n\r\nOne of Mutt main drawbacks is that you can't access your mailbox while\r\nwriting mails, good news everyone, with vim-mail you can open mutt in RO\r\nmode easily by typing\r\n\r\n    M\r\n\r\n### Send file from Vim\r\n\r\nWhen you are vimming at one point, you might want to send the file you are\r\nworking on. Leaving vim to send a mail from vim is so annoying, happily there\r\nis the solution just type: `m` and VimMail will pipe the file to\r\nmutt.\r\n\r\n## Mappings\r\n\r\nAll mappings can be disabled by adding the following line to your vimrc:\r\n\r\n    let g:VimMailDoNotMap=1\r\n\r\n\r\n+   On any file\r\n\r\n    Mapping          | Effect\r\n    -----------------|----------------------------------------------\r\n    `m` | Send the current buffer\r\n    `l` | Switch spelllang\r\n    `M` | Open the mail client\r\n\r\n+   On mail only\r\n\r\n    Mapping          | Effect\r\n    -----------------|----------------------------------------------\r\n    `a` | Search the word before cursor as a contact\r\n    `f` | Go to the From field\r\n    `b` | Go to the Bcc field\r\n    `c` | Go to the Cc field\r\n    `s` | Go to the SUbject field\r\n    `R` | Go to the Reply-To field\r\n    `t` | Go to the Reply-To field\r\n    `r` | Go to the first message of the conversation\r\n    `r2`| Go to the second message of the conversation\r\n    `r3`| Go to the third message of the conversation\r\n    `r4`| Go to the fourth message of the conversation\r\n    `S` | Go to your signature\r\n\r\n## CONFIGURATION\r\n\r\n### Address book configuration\r\n\r\nIt is possible to use another address book than pycard by setting the\r\nfollowing variables:\r\n\r\n    let g:VimMailContactSyncCmd=\"my_synchronisation_cmd\"\r\n    let g:VimMailContactQueryCmd=\"my_query_cmd\"\r\n\r\nThe only restriction is that the query command should give an output similar\r\nto pc_query output, aka something like:\r\n\r\n    Name: Someone\r\n    Tel (CELL): 000000000\r\n    EMAIL : someone@foo.bar\r\n    Name: Someone else\r\n    TEL: 0000000\r\n    EMAIL (Work): Someone.else@work.com\r\n    EMAIL (Perso): Someone.else@dummyprovider.com\r\n\r\nThe fields between parentheses are optional.\r\n\r\nIf you don't see the preview while using contact completion, add the following\r\nto your vimrc (see |completeopt| |preview| ):\r\n\r\n    set completeopt=preview\r\n\r\nIf you don't want this completion you can either not use the plugin or add\r\nthe following line to your vimrc:\r\n\r\n    let g:VimMailDontUseComplete=1\r\n\r\nBy default, the contact completion appends the query to the result list, you\r\ncan disable this feature:\r\n\r\n    let g:VimMailDoNotAppendQueryToResults\r\n\r\n### Spell\r\n\r\nSetting the list of possible spell langs:\r\n\r\n    let g:VimSpellLangs=['fr', 'en', 'sp']\r\n\r\n### Folds\r\n\r\nTo disable message folds, add the following line to your vimrc:\r\n\r\n    let g:VimMailDoNotFold=1\r\n\r\n### Mail Client\r\n\r\nYou can set the mail client command to your launcher script by adding to your\r\nvimrc something like:\r\n\r\n    let g:VimMailClient=\"\/path\/to\/your\/launcher\"\r\n\r\nIf you are not using mutt, or want to customize the send mail command, just\r\nadd something like that to your vimrc (this is the default command):\r\n\r\n    let g:VimMailSendCmd=\":! mutt -a %\"\r\n\r\n## License\r\n\r\nThis plugin is distributed under GPL Licence v3.0, see\r\nhttps:\/\/www.gnu.org\/licenses\/gpl.txt\r\n\r\nMore infos at https:\/\/github.com\/dbeniamine\/vim-mail\r\n","install_details":"## Install\r\n\r\n### Vizardry\r\n\r\nIf you have [Vizardry](https:\/\/github.com\/dbeniamine\/vizardry) installed, you\r\ncan run from vim:\r\n\r\n    :Invoke -u dbeniamine vim-mail\r\n\r\n### Pathogen install\r\n\r\n    git clone https:\/\/github.com\/dbeniamine\/vim-mail.git ~\/.vim\/bundle\/vim-mail\r\n\r\n### Quick install\r\n\r\n    git clone https:\/\/github.com\/dbeniamine\/vim-mail.git\r\n    cd vim-mail\/\r\n    cp -r .\/* ~\/.vim\r\n","5":"## Install\r\n\r\n### Vizardry\r\n\r\nIf you have [Vizardry](https:\/\/github.com\/dbeniamine\/vizardry) installed, you\r\ncan run from vim:\r\n\r\n    :Invoke -u dbeniamine vim-mail\r\n\r\n### Pathogen install\r\n\r\n    git clone https:\/\/github.com\/dbeniamine\/vim-mail.git ~\/.vim\/bundle\/vim-mail\r\n\r\n### Quick install\r\n\r\n    git clone https:\/\/github.com\/dbeniamine\/vim-mail.git\r\n    cd vim-mail\/\r\n    cp -r .\/* ~\/.vim\r\n","first_name":"David","6":"David","last_name":"Beniamine","7":"Beniamine","releases":[{"0":"5132","vim_version":"7.0","1":"7.0","script_version":"0.2.6","2":"0.2.6","version_comment":"+ Mapping to send current buffer by mail\r\n+ Cleaner documentation\r\n+ Autoload file is now splitted into three parts:\r\n  + spelllang\r\n  + completion\r\n  + sendmail","3":"+ Mapping to send current buffer by mail\r\n+ Cleaner documentation\r\n+ Autoload file is now splitted into three parts:\r\n  + spelllang\r\n  + completion\r\n  + sendmail","package":"vim-mail.tgz","4":"vim-mail.tgz","src_id":"24344","5":"24344","creation_date":"1466623297","6":"1466623297"},{"0":"5132","vim_version":"7.0","1":"7.0","script_version":"0.2.4","2":"0.2.4","version_comment":"+ Use autoload\r\n+ Few minor fix\r\nsee github for more info","3":"+ Use autoload\r\n+ Few minor fix\r\nsee github for more info","package":"vim-mail.tgz","4":"vim-mail.tgz","src_id":"23539","5":"23539","creation_date":"1440258991","6":"1440258991"},{"0":"5132","vim_version":"7.0","1":"7.0","script_version":"0.2.3","2":"0.2.3","version_comment":"Small corrections \/ swith to omni completion for better plugin integration","3":"Small corrections \/ swith to omni completion for better plugin integration","package":"vim-mail.tar.gz","4":"vim-mail.tar.gz","src_id":"23294","5":"23294","creation_date":"1432038619","6":"1432038619"},{"0":"5132","vim_version":"7.0","1":"7.0","script_version":"0.2.2","2":"0.2.2","version_comment":"CHG: Contact query is not bounded to pc_query anymore\r\nADD: contact synchronization capacity\r\nCHG: Cleaner documentation\r\n","3":"CHG: Contact query is not bounded to pc_query anymore\r\nADD: contact synchronization capacity\r\nCHG: Cleaner documentation\r\n","package":"vim-mail.tar.gz","4":"vim-mail.tar.gz","src_id":"23042","5":"23042","creation_date":"1426526202","6":"1426526202"},{"0":"5132","vim_version":"7.0","1":"7.0","script_version":"0.2.1","2":"0.2.1","version_comment":"ADD: Fold Method to open\/close messages in conversation\r\nADD: Mapping to go at beginning\/end of conversation\r\nCHG: Cleaner doc and code\r\n","3":"ADD: Fold Method to open\/close messages in conversation\r\nADD: Mapping to go at beginning\/end of conversation\r\nCHG: Cleaner doc and code\r\n","package":"vim-mail.tar.gz","4":"vim-mail.tar.gz","src_id":"23029","5":"23029","creation_date":"1426395747","6":"1426395747"},{"0":"5132","vim_version":"7.0","1":"7.0","script_version":"0.2","2":"0.2","version_comment":"Add: Easy mail navigation feature\r\nCHG: Small code clarifications\r\nCHG: Better doc","3":"Add: Easy mail navigation feature\r\nCHG: Small code clarifications\r\nCHG: Better doc","package":"vim-mail.tar.gz","4":"vim-mail.tar.gz","src_id":"23027","5":"23027","creation_date":"1426390297","6":"1426390297"},{"0":"5132","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"vim-mail.tar.gz","4":"vim-mail.tar.gz","src_id":"23023","5":"23023","creation_date":"1426367682","6":"1426367682"}]},"5131":{"script_id":"5131","0":"5131","script_name":"VimPyServer","1":"VimPyServer","script_type":"utility","2":"utility","summary":"A Python server to remote control Vim without X-windows or vim-server","3":"A Python server to remote control Vim without X-windows or vim-server","description":"This is a plugin to control your vim editor via telnet. It starts a Python server inside Vim until you close the editor. This is an alternative to \"vim -servername\", which I could not use on a terminal only environment (it appears it requires X11).\r\n\r\nWhit VimPyServer you can:\r\n\r\n- Integrate the edition of every file on your computer (Windows explorer, Firefox, mutt, etc) on a single instance of Vim editor (cygwin based or not). No more copy-paste hell, no more vim editors open everywhere! See README.asciidoc included:\r\n--- Defaulting single Cygwin Vim instance with Windows Explorer \"Open with\u00e2\u0080\u00a6\"\r\n--- Single Vim instance for Firefox + Vimperator\r\n--- Single Vim instance for mutt (coming soon!)\r\n- Have fun messing the code of your friends in their faces!\r\n- Chat with vim - to - vim  and share snippets of code with your buddies, easier than ever!\r\n- Send commands to you current open vim editor from another terminal, even from another computer!\r\n- Remotely control your current open vim editor, integrate it on an IDE automate actions!\r\n\r\n2. Requirements\r\n\r\n- VIM 7.4 with python and python3 (check it with vim --version)\r\n- Python 2.7.8 (Should work on Python 3. Please send me a message if you test it with version 3).\r\n- netcat (nc) is needed temporarily. Will be unnecessary on future releases.\r\n\r\n3. Installation\r\n\r\n- If your are using pathogen just clone it to your ~\/.vim\/bundle:\r\n\r\n  git clone https:\/\/github.com\/degyves\/VimPyServer.git\r\n\r\n- Set your environment variables and restart your terminals:\r\n\r\n--- Under Windows: add VIMPYSERVER_HOME to your environment variables (WIN+Pause, advanced settings). The value will be the path, in Windows format, of where you have cloned VimPyServer. Also add %VIMPYSERVER_HOME%\\bin to your Windows PATH. Do not configure these variables on ~\/.bashrc.\r\n--- Under Linux\/Mac: add VIMPYSERVER_HOME to your ~\/.bashrc. The value will be the path where you have cloned VimPyServer. Also add $VIMPYSERVER_HOME\\bin to your PATH.\r\n--- Under OpenBSD: add VIMPYSERVER_HOME to your ~\/.profile. The value will be the path where you have cloned VimPyServer. Also add $VIMPYSERVER_HOME\\bin to your PATH.\r\n\r\nThat\u00e2\u0080\u0099s it! VimPyServer will own the first vim editor you use. If you open several vim editors, only the first one will be controlled by the VimPyServer. This will be changed later so any vim editor will have the ability to own (or not) its own VimPyServer.\r\n\r\n4. Examples and integration.\r\n\r\nPlease see README.asciidoc or go to https:\/\/github.com\/degyves\/VimPyServer for examples.","4":"This is a plugin to control your vim editor via telnet. It starts a Python server inside Vim until you close the editor. This is an alternative to \"vim -servername\", which I could not use on a terminal only environment (it appears it requires X11).\r\n\r\nWhit VimPyServer you can:\r\n\r\n- Integrate the edition of every file on your computer (Windows explorer, Firefox, mutt, etc) on a single instance of Vim editor (cygwin based or not). No more copy-paste hell, no more vim editors open everywhere! See README.asciidoc included:\r\n--- Defaulting single Cygwin Vim instance with Windows Explorer \"Open with\u00e2\u0080\u00a6\"\r\n--- Single Vim instance for Firefox + Vimperator\r\n--- Single Vim instance for mutt (coming soon!)\r\n- Have fun messing the code of your friends in their faces!\r\n- Chat with vim - to - vim  and share snippets of code with your buddies, easier than ever!\r\n- Send commands to you current open vim editor from another terminal, even from another computer!\r\n- Remotely control your current open vim editor, integrate it on an IDE automate actions!\r\n\r\n2. Requirements\r\n\r\n- VIM 7.4 with python and python3 (check it with vim --version)\r\n- Python 2.7.8 (Should work on Python 3. Please send me a message if you test it with version 3).\r\n- netcat (nc) is needed temporarily. Will be unnecessary on future releases.\r\n\r\n3. Installation\r\n\r\n- If your are using pathogen just clone it to your ~\/.vim\/bundle:\r\n\r\n  git clone https:\/\/github.com\/degyves\/VimPyServer.git\r\n\r\n- Set your environment variables and restart your terminals:\r\n\r\n--- Under Windows: add VIMPYSERVER_HOME to your environment variables (WIN+Pause, advanced settings). The value will be the path, in Windows format, of where you have cloned VimPyServer. Also add %VIMPYSERVER_HOME%\\bin to your Windows PATH. Do not configure these variables on ~\/.bashrc.\r\n--- Under Linux\/Mac: add VIMPYSERVER_HOME to your ~\/.bashrc. The value will be the path where you have cloned VimPyServer. Also add $VIMPYSERVER_HOME\\bin to your PATH.\r\n--- Under OpenBSD: add VIMPYSERVER_HOME to your ~\/.profile. The value will be the path where you have cloned VimPyServer. Also add $VIMPYSERVER_HOME\\bin to your PATH.\r\n\r\nThat\u00e2\u0080\u0099s it! VimPyServer will own the first vim editor you use. If you open several vim editors, only the first one will be controlled by the VimPyServer. This will be changed later so any vim editor will have the ability to own (or not) its own VimPyServer.\r\n\r\n4. Examples and integration.\r\n\r\nPlease see README.asciidoc or go to https:\/\/github.com\/degyves\/VimPyServer for examples.","install_details":"Clone the repository to ~\/.vim\/bundle and use pathogen#infect and :Helptags\r\n\r\nOr download the zip file and put the files under ~\/.vim\/","5":"Clone the repository to ~\/.vim\/bundle and use pathogen#infect and :Helptags\r\n\r\nOr download the zip file and put the files under ~\/.vim\/","first_name":"Victor Polo","6":"Victor Polo","last_name":"De Gyves Montero","7":"De Gyves Montero","releases":[{"0":"5131","vim_version":"7.4","1":"7.4","script_version":"0.3","2":"0.3","version_comment":"Added support for mutt: Please set your mutt\\'s editor to \\\"vp\\\" (under ~\/.vim\/bundle\/VimPyServer\/bin). Any write in Vim will update mutt.","3":"Added support for mutt: Please set your mutt\\'s editor to \\\"vp\\\" (under ~\/.vim\/bundle\/VimPyServer\/bin). Any write in Vim will update mutt.","package":"VimPyServer.zip","4":"VimPyServer.zip","src_id":"23096","5":"23096","creation_date":"1427293833","6":"1427293833"},{"0":"5131","vim_version":"7.4","1":"7.4","script_version":"0.2.1","2":"0.2.1","version_comment":"Added tests instructions and path fixes in bin\/vp","3":"Added tests instructions and path fixes in bin\/vp","package":"VimPyServer.zip","4":"VimPyServer.zip","src_id":"23057","5":"23057","creation_date":"1426723776","6":"1426723776"},{"0":"5131","vim_version":"7.4","1":"7.4","script_version":"0.2","2":"0.2","version_comment":"Better documentation and more examples","3":"Better documentation and more examples","package":"VimPyServer.zip","4":"VimPyServer.zip","src_id":"23055","5":"23055","creation_date":"1426715495","6":"1426715495"},{"0":"5131","vim_version":"7.4","1":"7.4","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"VimPyServer.zip","4":"VimPyServer.zip","src_id":"23019","5":"23019","creation_date":"1426305382","6":"1426305382"}]},"5130":{"script_id":"5130","0":"5130","script_name":"vim-tlv-mode","1":"vim-tlv-mode","script_type":"syntax","2":"syntax","summary":"Transaction-Level Verilog support for Vim","3":"Transaction-Level Verilog support for Vim","description":"The vim-tlv-mode plug-in adds support for Transaction-Level Verilog (TLV for short) to the Vim text editor. The plug-in is intended to provide everything needed to efficiently develop TLV code in Vim:\r\n\r\n\u00e2\u0080\u00a2 File type detection\r\n\u00e2\u0080\u00a2 Syntax highlighting (including an optional color scheme)\r\n\u00e2\u0080\u00a2 Smart indentation\r\n\u00e2\u0080\u00a2 Checking for syntax errors\r\n\r\nFor more information about the plug-in please refer to its homepage or the project page on GitHub: \r\n\r\n\u00e2\u0080\u00a2 http:\/\/peterodding.com\/code\/vim\/tlv-mode\/\r\n\u00e2\u0080\u00a2 http:\/\/github.com\/xolox\/vim-tlv-mode\r\n\r\nIf you have questions, bug reports, suggestions, etc. the author can be contacted at peter@peterodding.com. If you like this plug-in please vote for it below!","4":"The vim-tlv-mode plug-in adds support for Transaction-Level Verilog (TLV for short) to the Vim text editor. The plug-in is intended to provide everything needed to efficiently develop TLV code in Vim:\r\n\r\n\u00e2\u0080\u00a2 File type detection\r\n\u00e2\u0080\u00a2 Syntax highlighting (including an optional color scheme)\r\n\u00e2\u0080\u00a2 Smart indentation\r\n\u00e2\u0080\u00a2 Checking for syntax errors\r\n\r\nFor more information about the plug-in please refer to its homepage or the project page on GitHub: \r\n\r\n\u00e2\u0080\u00a2 http:\/\/peterodding.com\/code\/vim\/tlv-mode\/\r\n\u00e2\u0080\u00a2 http:\/\/github.com\/xolox\/vim-tlv-mode\r\n\r\nIf you have questions, bug reports, suggestions, etc. the author can be contacted at peter@peterodding.com. If you like this plug-in please vote for it below!","install_details":"Unzip the most recent ZIP archive of the vim-tlv-mode plug-in inside your Vim profile directory (usually this is ~\/.vim on UNIX and %USERPROFILE%\\vimfiles on Windows), restart Vim and execute the command \":helptags ~\/.vim\/doc\" (use \":helptags ~\\vimfiles\\doc\" instead on Windows).\r\n\r\nIf you prefer you can also use Pathogen, Vundle or a similar tool to install and update the vim-tlv-mode plug-in using a local clone of the git repository.\r\n\r\nNow try it out: Edit a *.tlv file and inspect the syntax highlighting in \\TLV code blocks! You can also play around with the smart indentation to get a feel for how it works.","5":"Unzip the most recent ZIP archive of the vim-tlv-mode plug-in inside your Vim profile directory (usually this is ~\/.vim on UNIX and %USERPROFILE%\\vimfiles on Windows), restart Vim and execute the command \":helptags ~\/.vim\/doc\" (use \":helptags ~\\vimfiles\\doc\" instead on Windows).\r\n\r\nIf you prefer you can also use Pathogen, Vundle or a similar tool to install and update the vim-tlv-mode plug-in using a local clone of the git repository.\r\n\r\nNow try it out: Edit a *.tlv file and inspect the syntax highlighting in \\TLV code blocks! You can also play around with the smart indentation to get a feel for how it works.","first_name":"Peter","6":"Peter","last_name":"Odding","7":"Odding","releases":[{"0":"5130","vim_version":"7.0","1":"7.0","script_version":"0.3","2":"0.3","version_comment":" \u00e2\u0080\u00a2 Include links to homepage and Vim Online:\n   http:\/\/github.com\/xolox\/vim-tlv-mode\/commit\/b96b93e\n\n \u00e2\u0080\u00a2 Determined license (MIT), added mention in readme, removed from to-do list:\n   http:\/\/github.com\/xolox\/vim-tlv-mode\/commit\/0bba06a\n\n \u00e2\u0080\u00a2 Initial implementation of text folding:\n   http:\/\/github.com\/xolox\/vim-tlv-mode\/commit\/8f5bec9\n\n \u00e2\u0080\u00a2 Update installation instructions, include doc\/tlv-mode.txt:\n   http:\/\/github.com\/xolox\/vim-tlv-mode\/commit\/37e1ad0\n\n \u00e2\u0080\u00a2 Integrated syntax checking works! (please see the README for details):\n   http:\/\/github.com\/xolox\/vim-tlv-mode\/commit\/fa98c51","3":" \u00e2\u0080\u00a2 Include links to homepage and Vim Online:\n   http:\/\/github.com\/xolox\/vim-tlv-mode\/commit\/b96b93e\n\n \u00e2\u0080\u00a2 Determined license (MIT), added mention in readme, removed from to-do list:\n   http:\/\/github.com\/xolox\/vim-tlv-mode\/commit\/0bba06a\n\n \u00e2\u0080\u00a2 Initial implementation of text folding:\n   http:\/\/github.com\/xolox\/vim-tlv-mode\/commit\/8f5bec9\n\n \u00e2\u0080\u00a2 Update installation instructions, include doc\/tlv-mode.txt:\n   http:\/\/github.com\/xolox\/vim-tlv-mode\/commit\/37e1ad0\n\n \u00e2\u0080\u00a2 Integrated syntax checking works! (please see the README for details):\n   http:\/\/github.com\/xolox\/vim-tlv-mode\/commit\/fa98c51","package":"tlv-mode.zip","4":"tlv-mode.zip","src_id":"23124","5":"23124","creation_date":"1428019275","6":"1428019275"},{"0":"5130","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"tlv-mode.zip","4":"tlv-mode.zip","src_id":"23017","5":"23017","creation_date":"1426238871","6":"1426238871"}]},"5129":{"script_id":"5129","0":"5129","script_name":"textobj-functioncall","1":"textobj-functioncall","script_type":"utility","2":"utility","summary":"The textobject plugin to select a region that calls function.","3":"The textobject plugin to select a region that calls function.","description":"The vim textobject plugin to treat function-call-like regions.\r\n\r\nDefault mappings are assigned to 'if' and 'af'.\r\n\r\n* 'if' and 'af', both of them select a region like 'func(argument)'.\r\n* 'if' and 'af' behave differently when a function takes another function as its argument.\r\n* 'if' selects the most inner function under the cursor.\r\n* 'af' selects the first function including the cursor position by its parenthesis. However if any candidate would be found, it falls back to 'if'.\r\n\r\nFor example the cursor is on '2' of \"func1(func2(argument))\"\r\n* 'if' selects \"func2(argument)\".\r\n* 'af' selects \"func1(func2(argument))\".\r\n\r\nThis textobject could select following similar patterns.\r\n* func(argument)\r\n* array[index]\r\n\r\nLatest version: https:\/\/github.com\/machakann\/vim-textobj-functioncall","4":"The vim textobject plugin to treat function-call-like regions.\r\n\r\nDefault mappings are assigned to 'if' and 'af'.\r\n\r\n* 'if' and 'af', both of them select a region like 'func(argument)'.\r\n* 'if' and 'af' behave differently when a function takes another function as its argument.\r\n* 'if' selects the most inner function under the cursor.\r\n* 'af' selects the first function including the cursor position by its parenthesis. However if any candidate would be found, it falls back to 'if'.\r\n\r\nFor example the cursor is on '2' of \"func1(func2(argument))\"\r\n* 'if' selects \"func2(argument)\".\r\n* 'af' selects \"func1(func2(argument))\".\r\n\r\nThis textobject could select following similar patterns.\r\n* func(argument)\r\n* array[index]\r\n\r\nLatest version: https:\/\/github.com\/machakann\/vim-textobj-functioncall","install_details":"Unzip and just put all folders in your ~\/.vim.","5":"Unzip and just put all folders in your ~\/.vim.","first_name":"Masaaki","6":"Masaaki","last_name":"Nakamura","7":"Nakamura","releases":[{"0":"5129","vim_version":"7.4","1":"7.4","script_version":"1.0.1","2":"1.0.1","version_comment":"- Add multibyte character support for julia language.","3":"- Add multibyte character support for julia language.","package":"vim-textobj-functioncall-1.0.1.zip","4":"vim-textobj-functioncall-1.0.1.zip","src_id":"24023","5":"24023","creation_date":"1455814040","6":"1455814040"},{"0":"5129","vim_version":"7.2","1":"7.2","script_version":"1.0.0","2":"1.0.0","version_comment":"Initial upload","3":"Initial upload","package":"textobj-functioncall-1.0.0.zip","4":"textobj-functioncall-1.0.0.zip","src_id":"23014","5":"23014","creation_date":"1426160826","6":"1426160826"}]},"5128":{"script_id":"5128","0":"5128","script_name":"vim-quick-radon","1":"vim-quick-radon","script_type":"ftplugin","2":"ftplugin","summary":"vim-quick-radon is a Vim plugin that applies radon to your current file.","3":"vim-quick-radon is a Vim plugin that applies radon to your current file.","description":"vim-quick-radon is a Vim plugin that applies radon to your current file.\r\nRadon is a Python tool that computes various metrics from the source code.\r\n\r\nSee also github repository  https:\/\/github.com\/tell-k\/vim-quick-radon","4":"vim-quick-radon is a Vim plugin that applies radon to your current file.\r\nRadon is a Python tool that computes various metrics from the source code.\r\n\r\nSee also github repository  https:\/\/github.com\/tell-k\/vim-quick-radon","install_details":"","5":"","first_name":"tell","6":"tell","last_name":"k","7":"k","releases":[{"0":"5128","vim_version":"7.0","1":"7.0","script_version":"0.1.1","2":"0.1.1","version_comment":"#1 Refactoring\r\nhttps:\/\/github.com\/tell-k\/vim-quick-radon\/issues\/1\r\n\r\n#2 Result buffer is displayed redundantly\r\nhttps:\/\/github.com\/tell-k\/vim-quick-radon\/issues\/2","3":"#1 Refactoring\r\nhttps:\/\/github.com\/tell-k\/vim-quick-radon\/issues\/1\r\n\r\n#2 Result buffer is displayed redundantly\r\nhttps:\/\/github.com\/tell-k\/vim-quick-radon\/issues\/2","package":"vim-quick-radon.zip","4":"vim-quick-radon.zip","src_id":"23001","5":"23001","creation_date":"1425945475","6":"1425945475"}]},"5127":{"script_id":"5127","0":"5127","script_name":"vim-ranger","1":"vim-ranger","script_type":"ftplugin","2":"ftplugin","summary":"A vim plugin which uses ranger as explorer","3":"A vim plugin which uses ranger as explorer","description":"vim-ranger\r\n==========\r\n\r\nHow to use it\r\n---------------\r\n\r\nIt just works.\r\n\r\nUser Guide\r\n----------\r\n\r\n`ranger `_ is a file manager with VI key bindings.\r\n\r\nThis plugin is similar to `nerdtree `_. \r\nIt overrides the default file browser (netrw), so if you :edit a directory a ranger will be opened. \r\nWhen you open a file in ranger, it will be opened in vim.\r\nYou could also select multiple files and open'em all at once (use ``v`` to select multiple files in ranger).\r\nBTW, don't use it with nerdtree at the same time. \r\n\r\nTips\r\n-----\r\n\r\nYou can add ``nnoremap  :tabe %:p:h`` to your .vimrc so that you could use ```` to open new files in new tab.\r\n\r\nKnown issue\r\n-----------\r\n\r\n1. (Only for vanilla vim) After opening ranger once and back to vim, you can't use arrow-up\/arrow-down to observe vim command line \":\" history doesn't work anymore (unless restart vim).\r\n   Workaground: use Ctrl+UP\/DOWN to observe history, instead of just UP\/DOWN.\r\n2. (Only for neovim) some shortcut don't work, such as \"F8\", \"\" because of neovim limitation.\r\n\r\nRequirement\r\n------------\r\n\r\nranger >= 1.5.1\r\n\r\nNotes\r\n-----\r\n\r\nThis plugin is forked from the official ranger example here:\r\nhttps:\/\/github.com\/hut\/ranger\/blob\/master\/examples\/vim_file_chooser.vim\r\n\r\nThere are 3 main differences\r\n\r\n1. Unlike the original plugin, in my plugin the files are opened in tabs instead of buffers.\r\n2. Ranger will be opened automatically when you :edit a directory. The original plugin requires to execute a vim command to open ranger.\r\n3. My plugin supports neovim.\r\n\r\nCopyright (C) 2015 Tianjiao Yin ","4":"vim-ranger\r\n==========\r\n\r\nHow to use it\r\n---------------\r\n\r\nIt just works.\r\n\r\nUser Guide\r\n----------\r\n\r\n`ranger `_ is a file manager with VI key bindings.\r\n\r\nThis plugin is similar to `nerdtree `_. \r\nIt overrides the default file browser (netrw), so if you :edit a directory a ranger will be opened. \r\nWhen you open a file in ranger, it will be opened in vim.\r\nYou could also select multiple files and open'em all at once (use ``v`` to select multiple files in ranger).\r\nBTW, don't use it with nerdtree at the same time. \r\n\r\nTips\r\n-----\r\n\r\nYou can add ``nnoremap  :tabe %:p:h`` to your .vimrc so that you could use ```` to open new files in new tab.\r\n\r\nKnown issue\r\n-----------\r\n\r\n1. (Only for vanilla vim) After opening ranger once and back to vim, you can't use arrow-up\/arrow-down to observe vim command line \":\" history doesn't work anymore (unless restart vim).\r\n   Workaground: use Ctrl+UP\/DOWN to observe history, instead of just UP\/DOWN.\r\n2. (Only for neovim) some shortcut don't work, such as \"F8\", \"\" because of neovim limitation.\r\n\r\nRequirement\r\n------------\r\n\r\nranger >= 1.5.1\r\n\r\nNotes\r\n-----\r\n\r\nThis plugin is forked from the official ranger example here:\r\nhttps:\/\/github.com\/hut\/ranger\/blob\/master\/examples\/vim_file_chooser.vim\r\n\r\nThere are 3 main differences\r\n\r\n1. Unlike the original plugin, in my plugin the files are opened in tabs instead of buffers.\r\n2. Ranger will be opened automatically when you :edit a directory. The original plugin requires to execute a vim command to open ranger.\r\n3. My plugin supports neovim.\r\n\r\nCopyright (C) 2015 Tianjiao Yin ","install_details":"move it into .vim\/plugin","5":"move it into .vim\/plugin","first_name":"Tianjiao","6":"Tianjiao","last_name":"Yin","7":"Yin","releases":[{"0":"5127","vim_version":"7.0","1":"7.0","script_version":"0.5","2":"0.5","version_comment":"refactor","3":"refactor","package":"ranger.vim","4":"ranger.vim","src_id":"24369","5":"24369","creation_date":"1468209450","6":"1468209450"},{"0":"5127","vim_version":"7.0","1":"7.0","script_version":"0.4","2":"0.4","version_comment":"add gvim support","3":"add gvim support","package":"ranger.vim","4":"ranger.vim","src_id":"23503","5":"23503","creation_date":"1438725515","6":"1438725515"},{"0":"5127","vim_version":"7.0","1":"7.0","script_version":"0.3","2":"0.3","version_comment":"close window is nothing to read","3":"close window is nothing to read","package":"ranger.vim","4":"ranger.vim","src_id":"22998","5":"22998","creation_date":"1425885721","6":"1425885721"},{"0":"5127","vim_version":"7.0","1":"7.0","script_version":"0.2","2":"0.2","version_comment":"update","3":"update","package":"ranger.vim","4":"ranger.vim","src_id":"22997","5":"22997","creation_date":"1425873887","6":"1425873887"},{"0":"5127","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"ranger.vim","4":"ranger.vim","src_id":"22996","5":"22996","creation_date":"1425871706","6":"1425871706"}]},"5126":{"script_id":"5126","0":"5126","script_name":"vim-snoopy","1":"vim-snoopy","script_type":"utility","2":"utility","summary":"snoop around the script-local things","3":"snoop around the script-local things","description":"\r\nSEE https:\/\/github.com\/haya14busa\/vim-snoopy","4":"\r\nSEE https:\/\/github.com\/haya14busa\/vim-snoopy","install_details":"","5":"","first_name":"haya14busa","6":"haya14busa","last_name":" ","7":" ","releases":[{"0":"5126","vim_version":"7.3","1":"7.3","script_version":"0.9.0","2":"0.9.0","version_comment":"Initial upload","3":"Initial upload","package":"vim-snoopy-0.9.0.zip","4":"vim-snoopy-0.9.0.zip","src_id":"22986","5":"22986","creation_date":"1425796289","6":"1425796289"}]},"5125":{"script_id":"5125","0":"5125","script_name":"love-launch","1":"love-launch","script_type":"utility","2":"utility","summary":"Run LOVE","3":"Run LOVE","description":"Use Alt-L to launch LOVE (or love2d: http:\/\/love2d.org) for your current project.\r\nSee the Gist at https:\/\/gist.github.com\/davisdude\/0f46c9c00917fc5c53bb","4":"Use Alt-L to launch LOVE (or love2d: http:\/\/love2d.org) for your current project.\r\nSee the Gist at https:\/\/gist.github.com\/davisdude\/0f46c9c00917fc5c53bb","install_details":"","5":"","first_name":"Davis","6":"Davis","last_name":"Claiborne","7":"Claiborne","releases":[{"0":"5125","vim_version":"7.0","1":"7.0","script_version":"0.3.0","2":"0.3.0","version_comment":"Lots of changes","3":"Lots of changes","package":"love-launch.zip","4":"love-launch.zip","src_id":"23314","5":"23314","creation_date":"1432674663","6":"1432674663"},{"0":"5125","vim_version":"7.0","1":"7.0","script_version":"0.2.0","2":"0.2.0","version_comment":"Added several new options, including the option to look for conf.lua to avoid ambiguity of having multiple main.lua files.","3":"Added several new options, including the option to look for conf.lua to avoid ambiguity of having multiple main.lua files.","package":"love-launch.zip","4":"love-launch.zip","src_id":"23258","5":"23258","creation_date":"1430789232","6":"1430789232"},{"0":"5125","vim_version":"7.0","1":"7.0","script_version":"0.1.2","2":"0.1.2","version_comment":"Fixed re-mapping","3":"Fixed re-mapping","package":"love-launch.zip","4":"love-launch.zip","src_id":"22995","5":"22995","creation_date":"1425852503","6":"1425852503"},{"0":"5125","vim_version":"7.0","1":"7.0","script_version":"0.1.1","2":"0.1.1","version_comment":"Added re-mapping and fixed small typo","3":"Added re-mapping and fixed small typo","package":"love-launch.zip","4":"love-launch.zip","src_id":"22994","5":"22994","creation_date":"1425851568","6":"1425851568"},{"0":"5125","vim_version":"7.0","1":"7.0","script_version":"0.1.0","2":"0.1.0","version_comment":"Initial upload","3":"Initial upload","package":"love-launch.zip","4":"love-launch.zip","src_id":"22985","5":"22985","creation_date":"1425787197","6":"1425787197"}]},"5124":{"script_id":"5124","0":"5124","script_name":"Vinfo","1":"Vinfo","script_type":"utility","2":"utility","summary":"Read Info documentation files","3":"Read Info documentation files","description":"https:\/\/github.com\/alx741\/vinfo\r\n\r\nVinfo is a Vim plugin that allows you to read Info documentation files right inside a Vim session in a Vim-help fashioned way or from a shell just the way you normally use Info.\r\n\r\n\r\nUsage\r\n=====\r\n\r\nVinfo can be used right inside a Vim session or from a shell using an alias.\r\n\r\nUse inside Vim\r\n--------------------\r\n\r\nYou can use Vinfo inside Vim with:\r\n\r\n:Vinfo doc\r\n\r\nWhere doc is the Info documentation to read.\r\n\r\nExample: Read Glibc Info documentation\r\n\r\n:Vinfo libc\r\n\r\nUse outside Vim\r\n----------------------\r\n\r\nWhen your are not inside a Vim session but in the shell prompt you can invoke Vinfo as a command by using the following shell script:\r\n\r\n    #! \/bin\/sh\r\n    vim -c \\\"Vinfo $1\\\" -c \\'only\\'\r\n\r\nSave it in \/usr\/bin\/ as a file named vinfo, give it execution permission with:\r\n\r\n$ chmod +x \/usr\/bin\/vinfo\r\n\r\nThen from your shell you can read a DOC with:\r\n\r\n$ vinfo doc\r\n","4":"https:\/\/github.com\/alx741\/vinfo\r\n\r\nVinfo is a Vim plugin that allows you to read Info documentation files right inside a Vim session in a Vim-help fashioned way or from a shell just the way you normally use Info.\r\n\r\n\r\nUsage\r\n=====\r\n\r\nVinfo can be used right inside a Vim session or from a shell using an alias.\r\n\r\nUse inside Vim\r\n--------------------\r\n\r\nYou can use Vinfo inside Vim with:\r\n\r\n:Vinfo doc\r\n\r\nWhere doc is the Info documentation to read.\r\n\r\nExample: Read Glibc Info documentation\r\n\r\n:Vinfo libc\r\n\r\nUse outside Vim\r\n----------------------\r\n\r\nWhen your are not inside a Vim session but in the shell prompt you can invoke Vinfo as a command by using the following shell script:\r\n\r\n    #! \/bin\/sh\r\n    vim -c \\\"Vinfo $1\\\" -c \\'only\\'\r\n\r\nSave it in \/usr\/bin\/ as a file named vinfo, give it execution permission with:\r\n\r\n$ chmod +x \/usr\/bin\/vinfo\r\n\r\nThen from your shell you can read a DOC with:\r\n\r\n$ vinfo doc\r\n","install_details":"https:\/\/github.com\/alx741\/vinfo\r\n\r\n* Vinfo is Pathogen\/ Vundle compatible.\r\n\r\n* Or install it manually by copying the files to the corresponding locations.\r\n","5":"https:\/\/github.com\/alx741\/vinfo\r\n\r\n* Vinfo is Pathogen\/ Vundle compatible.\r\n\r\n* Or install it manually by copying the files to the corresponding locations.\r\n","first_name":"Daniel","6":"Daniel","last_name":"Campoverde","7":"Campoverde","releases":[{"0":"5124","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"vinfo.tar.gz","4":"vinfo.tar.gz","src_id":"22975","5":"22975","creation_date":"1425340157","6":"1425340157"}]},"5123":{"script_id":"5123","0":"5123","script_name":"codeforces.vim","1":"codeforces.vim","script_type":"utility","2":"utility","summary":"Vim plugin for CodeForces","3":"Vim plugin for CodeForces","description":"Vim plugin for CodeForces\r\n\r\nWhat allows to do:\r\n\r\n* Watch standings of contests (Unofficial http:\/\/i.imgur.com\/yI5bhBs.png, Friends http:\/\/i.imgur.com\/2o730zV.png, Official http:\/\/i.imgur.com\/avSplri.png, Room http:\/\/i.imgur.com\/nRH64jB.png)\r\n* Submit source code (thanks to CountZero http:\/\/codeforces.ru\/blog\/entry\/14786)\r\n* Watch result of last user's submissions http:\/\/i.imgur.com\/hDWFJXo.png\r\n* Load text of problems \r\nhttp:\/\/i.imgur.com\/Q5M9fsd.png\r\nhttp:\/\/i.imgur.com\/NAmMBEj.png\r\n* Download last submission of user to problem (qwerty787788's solution to F http:\/\/i.imgur.com\/vqvZV7Y.png)\r\n\r\nIt is clone of github project https:\/\/github.com\/Igorjan94\/codeforces.vim","4":"Vim plugin for CodeForces\r\n\r\nWhat allows to do:\r\n\r\n* Watch standings of contests (Unofficial http:\/\/i.imgur.com\/yI5bhBs.png, Friends http:\/\/i.imgur.com\/2o730zV.png, Official http:\/\/i.imgur.com\/avSplri.png, Room http:\/\/i.imgur.com\/nRH64jB.png)\r\n* Submit source code (thanks to CountZero http:\/\/codeforces.ru\/blog\/entry\/14786)\r\n* Watch result of last user's submissions http:\/\/i.imgur.com\/hDWFJXo.png\r\n* Load text of problems \r\nhttp:\/\/i.imgur.com\/Q5M9fsd.png\r\nhttp:\/\/i.imgur.com\/NAmMBEj.png\r\n* Download last submission of user to problem (qwerty787788's solution to F http:\/\/i.imgur.com\/vqvZV7Y.png)\r\n\r\nIt is clone of github project https:\/\/github.com\/Igorjan94\/codeforces.vim","install_details":"with your favorite plugin manager, e.g. Bundle 'Igorjan94\/codeforces.vim', then :PluginInstall\r\n\r\nDependencies\r\n* Python\r\n  * requests   (all network)\r\n  * HTMLparser (loadProblem, loadSubmission, parseContest)\r\n  * flask, selenium (submit)\r\n* EasyAlign https:\/\/github.com\/junegunn\/vim-easy-align vimscript #4520 for beautiful standings","5":"with your favorite plugin manager, e.g. Bundle 'Igorjan94\/codeforces.vim', then :PluginInstall\r\n\r\nDependencies\r\n* Python\r\n  * requests   (all network)\r\n  * HTMLparser (loadProblem, loadSubmission, parseContest)\r\n  * flask, selenium (submit)\r\n* EasyAlign https:\/\/github.com\/junegunn\/vim-easy-align vimscript #4520 for beautiful standings","first_name":"Igor","6":"Igor","last_name":"Kolobov","7":"Kolobov","releases":[{"0":"5123","vim_version":"7.0","1":"7.0","script_version":"0.4","2":"0.4","version_comment":"submit via python-server","3":"submit via python-server","package":"0.4.zip","4":"0.4.zip","src_id":"24291","5":"24291","creation_date":"1464560508","6":"1464560508"},{"0":"5123","vim_version":"7.0","1":"7.0","script_version":"0.2","2":"0.2","version_comment":"fix of 'fix bug in CF'","3":"fix of 'fix bug in CF'","package":"0.2.zip","4":"0.2.zip","src_id":"23319","5":"23319","creation_date":"1432848518","6":"1432848518"},{"0":"5123","vim_version":"7.0","1":"7.0","script_version":"0.2","2":"0.2","version_comment":"* Parsing of contest\r\n* Running samples\r\n* Correct html-parsing of problem statement, submission, friends\r\n* Contest list\r\n* Standings with '?' while systests, color of points Blue if contest isn't finished\r\n* Refactoring","3":"* Parsing of contest\r\n* Running samples\r\n* Correct html-parsing of problem statement, submission, friends\r\n* Contest list\r\n* Standings with '?' while systests, color of points Blue if contest isn't finished\r\n* Refactoring","package":"0.2.zip","4":"0.2.zip","src_id":"23092","5":"23092","creation_date":"1427196836","6":"1427196836"},{"0":"5123","vim_version":"7.0","1":"7.0","script_version":"0.2","2":"0.2","version_comment":"Initial upload","3":"Initial upload","package":"codeforces.vim.tar.gz","4":"codeforces.vim.tar.gz","src_id":"22974","5":"22974","creation_date":"1425332358","6":"1425332358"}]},"5122":{"script_id":"5122","0":"5122","script_name":"RedirCommands","1":"RedirCommands","script_type":"utility","2":"utility","summary":"plugin for redirecting command output","3":"plugin for redirecting command output","description":"The Vim command redir is very powerful. It allows you to process the output of commands in whatever way you desire, but it is cumbersome to use. The RedirCommands pulgin gives you all of the power without the trouble.\r\n\r\nFunctionality\r\n\r\n:R \r\n\r\nRun command and redirect output to a split window.\r\n\r\n    :R function NERDComment\r\n    :R python print '\\n'.join([str(x**2) for x in xrange(100)])\r\n\r\n:RR  \r\n\r\nRun command and redirect output to a destination. Destination can be a\r\nregister, global variable, or file. The destination string must not contain\r\nspaces.\r\n\r\n    :RR highlight Comment @a\r\n    :RR highlight Comment =>g:hi_comment\r\n    :RR highlight Comment >hi_comment.txt\r\n\r\nOptions\r\n\r\ng:redircommands_newbuffer_command\r\n\r\nThe command used to redirect output to a split window. The default is 'R'.\r\n\r\ng:redircommands_general_command\r\n\r\nThe command used to redirect output to a specified destination. The default is 'RR'.","4":"The Vim command redir is very powerful. It allows you to process the output of commands in whatever way you desire, but it is cumbersome to use. The RedirCommands pulgin gives you all of the power without the trouble.\r\n\r\nFunctionality\r\n\r\n:R \r\n\r\nRun command and redirect output to a split window.\r\n\r\n    :R function NERDComment\r\n    :R python print '\\n'.join([str(x**2) for x in xrange(100)])\r\n\r\n:RR  \r\n\r\nRun command and redirect output to a destination. Destination can be a\r\nregister, global variable, or file. The destination string must not contain\r\nspaces.\r\n\r\n    :RR highlight Comment @a\r\n    :RR highlight Comment =>g:hi_comment\r\n    :RR highlight Comment >hi_comment.txt\r\n\r\nOptions\r\n\r\ng:redircommands_newbuffer_command\r\n\r\nThe command used to redirect output to a split window. The default is 'R'.\r\n\r\ng:redircommands_general_command\r\n\r\nThe command used to redirect output to a specified destination. The default is 'RR'.","install_details":"Extract the plugin files in your ~\/.vim (*nix) or ~\/vimfiles (Windows). You \r\nshould have 2 files: \r\n\r\n    plugin\/redircommands.vim \r\n    doc\/redircommands.txt \r\n\r\nNext, to finish installing the help file run: \r\n\r\n    :helptags ~\/.vim\/doc \r\n\r\nAlternatively, and arguably preferably, use Pathogen and checkout the \r\nvim-redircommands directory in your bundle directory. Then, run: \r\n\r\n    :Helptags","5":"Extract the plugin files in your ~\/.vim (*nix) or ~\/vimfiles (Windows). You \r\nshould have 2 files: \r\n\r\n    plugin\/redircommands.vim \r\n    doc\/redircommands.txt \r\n\r\nNext, to finish installing the help file run: \r\n\r\n    :helptags ~\/.vim\/doc \r\n\r\nAlternatively, and arguably preferably, use Pathogen and checkout the \r\nvim-redircommands directory in your bundle directory. Then, run: \r\n\r\n    :Helptags","first_name":"Scott","6":"Scott","last_name":"Updike","7":"Updike","releases":[{"0":"5122","vim_version":"7.0","1":"7.0","script_version":"1.0.0","2":"1.0.0","version_comment":"Initial upload","3":"Initial upload","package":"redircommands.tgz","4":"redircommands.tgz","src_id":"22960","5":"22960","creation_date":"1425170919","6":"1425170919"}]},"5121":{"script_id":"5121","0":"5121","script_name":"EnhancedDiff","1":"EnhancedDiff","script_type":"utility","2":"utility","summary":"A Vim plugin for creating better diffs (sometimes)","3":"A Vim plugin for creating better diffs (sometimes)","description":"This plugin allows to make use of the Patience diff algorithm for generating diffs to use with Vim. This needs the git command line tool available.\r\n\r\nYou can also customize you setup to use any other tool to generated diffs (e.g. mercurial) Read the help on how to configure the plugin accordingly.\r\n\r\nSee the screenshots at https:\/\/github.com\/chrisbra\/vim-diff-enhanced\r\n\r\nThis plugin defines the following Ex commands:\r\n\r\n:PatienceDiff - Use the Patience Diff algorithm for the next diff mode\r\n:CustomDiff  - Use <algorithm> to generate the diff. Use any of\r\n\r\n    myers\r\n    default\r\n    histogram\r\n    patience\r\n\r\nAfter changing the algorithm, you need to run :diffupdate if you are in diff mode to regenerate the diff.\r\nNote: Those 2 commands use internally git to generate the diffs. Make sure you have at least git version 1.8.2 installed.\r\n\r\n:DisableEnhancedDiff - Disable plugin (and use default Vim diff capabilities).","4":"This plugin allows to make use of the Patience diff algorithm for generating diffs to use with Vim. This needs the git command line tool available.\r\n\r\nYou can also customize you setup to use any other tool to generated diffs (e.g. mercurial) Read the help on how to configure the plugin accordingly.\r\n\r\nSee the screenshots at https:\/\/github.com\/chrisbra\/vim-diff-enhanced\r\n\r\nThis plugin defines the following Ex commands:\r\n\r\n:PatienceDiff - Use the Patience Diff algorithm for the next diff mode\r\n:CustomDiff  - Use <algorithm> to generate the diff. Use any of\r\n\r\n    myers\r\n    default\r\n    histogram\r\n    patience\r\n\r\nAfter changing the algorithm, you need to run :diffupdate if you are in diff mode to regenerate the diff.\r\nNote: Those 2 commands use internally git to generate the diffs. Make sure you have at least git version 1.8.2 installed.\r\n\r\n:DisableEnhancedDiff - Disable plugin (and use default Vim diff capabilities).","install_details":"Simply source the file and the plugin will be installed automatically\r\n:e EnhancedDiff-.vmb\r\n:so %\r\n\r\nAnd afterwards, have a look at the documentation: :h EnhancedDiff\r\n\r\nAlternatively, use the plugin manager of your choice for installation","5":"Simply source the file and the plugin will be installed automatically\r\n:e EnhancedDiff-.vmb\r\n:so %\r\n\r\nAnd afterwards, have a look at the documentation: :h EnhancedDiff\r\n\r\nAlternatively, use the plugin manager of your choice for installation","first_name":"Christian","6":"Christian","last_name":"Brabandt","7":"Brabandt","releases":[{"0":"5121","vim_version":"7.4","1":"7.4","script_version":"3","2":"3","version_comment":"- update diff, when in diffmode and |:CustomDiff| is used\n- run test correctly, when installed via plugin manager (issue\n  https:\/\/github.com\/chrisbra\/vim-diff-enhanced\/issues\/1, reported by\n  advocateddrummer thanks!)\n- fix small typo (noticed by Gary Johnson, thanks!)\n(automatically uploaded)","3":"- update diff, when in diffmode and |:CustomDiff| is used\n- run test correctly, when installed via plugin manager (issue\n  https:\/\/github.com\/chrisbra\/vim-diff-enhanced\/issues\/1, reported by\n  advocateddrummer thanks!)\n- fix small typo (noticed by Gary Johnson, thanks!)\n(automatically uploaded)","package":"EnhancedDiff-0.3.vmb","4":"EnhancedDiff-0.3.vmb","src_id":"22980","5":"22980","creation_date":"1425539703","6":"1425539703"},{"0":"5121","vim_version":"7.4","1":"7.4","script_version":"0.2","2":"0.2","version_comment":"Updated links to point to the vim.org page","3":"Updated links to point to the vim.org page","package":"EnhancedDiff.vmb","4":"EnhancedDiff.vmb","src_id":"22954","5":"22954","creation_date":"1424896906","6":"1424896906"},{"0":"5121","vim_version":"7.4","1":"7.4","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"EnhancedDiff.vmb","4":"EnhancedDiff.vmb","src_id":"22953","5":"22953","creation_date":"1424896467","6":"1424896467"}]},"5120":{"script_id":"5120","0":"5120","script_name":"SpecialLocationComplete","1":"SpecialLocationComplete","script_type":"utility","2":"utility","summary":"Insert mode completion for special custom patterns.","3":"Insert mode completion for special custom patterns.","description":"DESCRIPTION\r\nMost custom completions are about particular bases, contexts, patterns, or\r\nbuffers, and are pretty fixed about them. But sometimes a special completion\r\n(for example, only XML tag names) would be very useful, but it would be\r\noverkill to write a complete custom completion for it (even though the\r\nCompleteHelper.vim library makes this quite simple).\r\nThis plugin provides a generic, configurable framework for defining custom\r\ncompletions through simple configuration objects, allowing both global and\r\nbuffer- or window-scoped completions. So if you e.g. need completion of\r\nexpressions inside <% ... %> for a particular filetype, you can quickly define\r\nsuch, and assign it to a completion key.\r\n\r\nSOURCE\r\nInspired by\r\n    http:\/\/stackoverflow.com\/questions\/28496473\/a-particular-text-tagging-system-in-vim\r\n\r\nSEE ALSO\r\n- Check out the CompleteHelper.vim plugin page (vimscript #3914) for a full\r\n  list of insert mode completions powered by it.\r\n\r\nUSAGE\r\nIn insert mode, invoke the special completion via CTRL-X CTRL-X; you will\r\nthen be prompted for another key that selects the particular completion.\r\nYou can then search forward and backward via CTRL-N \/ CTRL-P, as usual.\r\n\r\nCTRL-X CTRL-X {key}[...]Find special matches configured for {key}[...] (see\r\n                        g:SpecialLocationCompletions).\r\n                        Further use of CTRL-X CTRL-X will copy additional text\r\n                        (what exactly is customizable, too).\r\n\r\nThe plugin ships with the following global default completions:\r\nCTRL-X CTRL-X t         Find pure tag names (without attributes and the\r\n                        surrounding <...>) in opening and closing tags.\r\nCTRL-X CTRL-X T         Find complete tags (everything inside and including\r\n                        the <...>). Further use will copy following complete\r\n                        tags (without text in between).\r\nCTRL-X CTRL-X CTRL-T    Find tag attributes (name=\"value\") in tags.\r\nCTRL-X CTRL-X it        Text between arbitrary tags (<...>text here<\/...>),\r\n                        starting with the base. If none is found, do a relaxed\r\n                        search for the base anywhere between arbitrary tags.\r\n                        Unlike the it text object, the surrounding tags need\r\n                        not match; they can be _any_ opening or closing tags!\r\nCTRL-X CTRL-X num       Find decimal numbers starting with \/ containing the\r\n                        base.\r\nCTRL-X CTRL-X hex       Find hexadecimal numbers (with or without \"0x\" prefix)\r\n                        starting with \/ containing the base.\r\nCTRL-X CTRL-X uuid      Find UUIDs (c2e9853b-4d8e-48b6-af5a-ef0e6279fa61 and\r\n                        c2e9853b4d8e48b6af5aef0e6279fa61) starting with \/\r\n                        containing the base.","4":"DESCRIPTION\r\nMost custom completions are about particular bases, contexts, patterns, or\r\nbuffers, and are pretty fixed about them. But sometimes a special completion\r\n(for example, only XML tag names) would be very useful, but it would be\r\noverkill to write a complete custom completion for it (even though the\r\nCompleteHelper.vim library makes this quite simple).\r\nThis plugin provides a generic, configurable framework for defining custom\r\ncompletions through simple configuration objects, allowing both global and\r\nbuffer- or window-scoped completions. So if you e.g. need completion of\r\nexpressions inside <% ... %> for a particular filetype, you can quickly define\r\nsuch, and assign it to a completion key.\r\n\r\nSOURCE\r\nInspired by\r\n    http:\/\/stackoverflow.com\/questions\/28496473\/a-particular-text-tagging-system-in-vim\r\n\r\nSEE ALSO\r\n- Check out the CompleteHelper.vim plugin page (vimscript #3914) for a full\r\n  list of insert mode completions powered by it.\r\n\r\nUSAGE\r\nIn insert mode, invoke the special completion via CTRL-X CTRL-X; you will\r\nthen be prompted for another key that selects the particular completion.\r\nYou can then search forward and backward via CTRL-N \/ CTRL-P, as usual.\r\n\r\nCTRL-X CTRL-X {key}[...]Find special matches configured for {key}[...] (see\r\n                        g:SpecialLocationCompletions).\r\n                        Further use of CTRL-X CTRL-X will copy additional text\r\n                        (what exactly is customizable, too).\r\n\r\nThe plugin ships with the following global default completions:\r\nCTRL-X CTRL-X t         Find pure tag names (without attributes and the\r\n                        surrounding <...>) in opening and closing tags.\r\nCTRL-X CTRL-X T         Find complete tags (everything inside and including\r\n                        the <...>). Further use will copy following complete\r\n                        tags (without text in between).\r\nCTRL-X CTRL-X CTRL-T    Find tag attributes (name=\"value\") in tags.\r\nCTRL-X CTRL-X it        Text between arbitrary tags (<...>text here<\/...>),\r\n                        starting with the base. If none is found, do a relaxed\r\n                        search for the base anywhere between arbitrary tags.\r\n                        Unlike the it text object, the surrounding tags need\r\n                        not match; they can be _any_ opening or closing tags!\r\nCTRL-X CTRL-X num       Find decimal numbers starting with \/ containing the\r\n                        base.\r\nCTRL-X CTRL-X hex       Find hexadecimal numbers (with or without \"0x\" prefix)\r\n                        starting with \/ containing the base.\r\nCTRL-X CTRL-X uuid      Find UUIDs (c2e9853b-4d8e-48b6-af5a-ef0e6279fa61 and\r\n                        c2e9853b4d8e48b6af5aef0e6279fa61) starting with \/\r\n                        containing the base.","install_details":"INSTALLATION\r\nThe code is hosted in a Git repo at\r\n    https:\/\/github.com\/inkarkat\/vim-SpecialLocationComplete\r\nYou can use your favorite plugin manager, or \"git clone\" into a directory used\r\nfor Vim packages. Releases are on the \"stable\" branch, the latest unstable\r\ndevelopment snapshot on \"master\".\r\n\r\nThis script is also packaged as a vimball. If you have the \"gunzip\"\r\ndecompressor in your PATH, simply edit the *.vmb.gz package in Vim; otherwise,\r\ndecompress the archive first, e.g. using WinZip. Inside Vim, install by\r\nsourcing the vimball or via the :UseVimball command.\r\n    vim SpecialLocationComplete*.vmb.gz\r\n    :so %\r\nTo uninstall, use the :RmVimball command.\r\n\r\nDEPENDENCIES\r\n- Requires Vim 7.0 or higher.\r\n- Requires the ingo-library.vim plugin (vimscript #4433), version 1.010 or\r\n  higher.\r\n- Requires the CompleteHelper.vim plugin (vimscript #3914), version 1.40 or\r\n  higher.\r\n\r\nCONFIGURATION\r\nFor a permanent configuration, put the following commands into your vimrc:\r\n\r\nThis completion can provide an arbitrary number of special completions; these\r\ncan be available globally, or only in particular buffers or windows. Each\r\ncompletion is defined by a configuration object under a (correspondingly\r\nscoped) Dictionary; the key is the (sequence of) character(s) that must be\r\ntyped after the i_CTRL-X_CTRL-X completion mapping. The following example\r\nshows the defaults (which are modeled after the built-in keyword completion),\r\nand explains their use:\r\n    let g:SpecialLocationCompletions = {\r\n    \\   'k': {\r\n       The key(s) (after i_CTRL-X_CTRL-X) to invoke. No key-notation\r\n        supported; i.e. use ^T (as a single char) for .\r\n    \\       'priority': 1000,\r\n               Number that influences the position of the completion in the\r\n                printed hints; lower numbers appear first.\r\n    \\       'description': 'keywords',\r\n               An (optional) explanation appended to the key in the prompt. >\r\n    \\       'complete': '.,w,b,u'\r\n               Specifies what is searched, like the 'complete' option. The\r\n                default depends on the config variable scope: visible windows\r\n                for w:, the current buffer for :b, and everything\r\n                configured in 'complete' for g:.\r\n    \\       'base': '\\k\\*\\%#',\r\n               The pattern to locate the completion base (before the cursor). >\r\n    \\       'patternTemplate': '\\<%s\\k\\+',\r\n               With the base inserted at \"%s\", yields the pattern used to\r\n                search for completions. Can also be a List of pattern\r\n                templates; these are then searched sequentially until one\r\n                pattern yields matches.\r\n    \\       'emptyBasePattern': '',\r\n               Optional alternative pattern to 'patternTemplate' that is used\r\n                when there's no base. Can also be a List; these are then\r\n                searched sequentially until one pattern yields matches.\r\n    \\       'repeatPatternTemplate': '%s\\zs\\s*\\k\\+',\r\n               When repeating the completion, yields the pattern to search\r\n                for completions. \"%s\" is replaced with the full completion,\r\n                \"%S\" is replaced with just the last added completion part.\r\n                Alternatively, common repeat patterns can also be built from\r\n                the following parts characterized by an anchor, a matching\r\n                atom, and a non-matching in between (this is the default):\r\n    \\       'repeatAnchorExpr': '\\<',\r\n    \\       'repeatPositiveExpr': '\\k',\r\n    \\       'repeatNegativeExpr': '\\%(\\k\\@!\\.\\)',\r\n               Note: You can't mix-and-match here, if you want to override\r\n                repeatNegativeExpr, you also need to specify the previous ones!\r\n    \\   }\r\n    \\}\r\nIn addition, any other a:options from CompleteHelper#FindMatches() can be\r\nspecified, too. These are passed to the CompleteHelper function.\r\n\r\nIf you want to use a different mapping, map your keys to the\r\n(SpecialLocationComplete) mapping target _before_ sourcing the script\r\n(e.g. in your vimrc):\r\n    imap  (SpecialLocationComplete)","5":"INSTALLATION\r\nThe code is hosted in a Git repo at\r\n    https:\/\/github.com\/inkarkat\/vim-SpecialLocationComplete\r\nYou can use your favorite plugin manager, or \"git clone\" into a directory used\r\nfor Vim packages. Releases are on the \"stable\" branch, the latest unstable\r\ndevelopment snapshot on \"master\".\r\n\r\nThis script is also packaged as a vimball. If you have the \"gunzip\"\r\ndecompressor in your PATH, simply edit the *.vmb.gz package in Vim; otherwise,\r\ndecompress the archive first, e.g. using WinZip. Inside Vim, install by\r\nsourcing the vimball or via the :UseVimball command.\r\n    vim SpecialLocationComplete*.vmb.gz\r\n    :so %\r\nTo uninstall, use the :RmVimball command.\r\n\r\nDEPENDENCIES\r\n- Requires Vim 7.0 or higher.\r\n- Requires the ingo-library.vim plugin (vimscript #4433), version 1.010 or\r\n  higher.\r\n- Requires the CompleteHelper.vim plugin (vimscript #3914), version 1.40 or\r\n  higher.\r\n\r\nCONFIGURATION\r\nFor a permanent configuration, put the following commands into your vimrc:\r\n\r\nThis completion can provide an arbitrary number of special completions; these\r\ncan be available globally, or only in particular buffers or windows. Each\r\ncompletion is defined by a configuration object under a (correspondingly\r\nscoped) Dictionary; the key is the (sequence of) character(s) that must be\r\ntyped after the i_CTRL-X_CTRL-X completion mapping. The following example\r\nshows the defaults (which are modeled after the built-in keyword completion),\r\nand explains their use:\r\n    let g:SpecialLocationCompletions = {\r\n    \\   'k': {\r\n       The key(s) (after i_CTRL-X_CTRL-X) to invoke. No key-notation\r\n        supported; i.e. use ^T (as a single char) for .\r\n    \\       'priority': 1000,\r\n               Number that influences the position of the completion in the\r\n                printed hints; lower numbers appear first.\r\n    \\       'description': 'keywords',\r\n               An (optional) explanation appended to the key in the prompt. >\r\n    \\       'complete': '.,w,b,u'\r\n               Specifies what is searched, like the 'complete' option. The\r\n                default depends on the config variable scope: visible windows\r\n                for w:, the current buffer for :b, and everything\r\n                configured in 'complete' for g:.\r\n    \\       'base': '\\k\\*\\%#',\r\n               The pattern to locate the completion base (before the cursor). >\r\n    \\       'patternTemplate': '\\<%s\\k\\+',\r\n               With the base inserted at \"%s\", yields the pattern used to\r\n                search for completions. Can also be a List of pattern\r\n                templates; these are then searched sequentially until one\r\n                pattern yields matches.\r\n    \\       'emptyBasePattern': '',\r\n               Optional alternative pattern to 'patternTemplate' that is used\r\n                when there's no base. Can also be a List; these are then\r\n                searched sequentially until one pattern yields matches.\r\n    \\       'repeatPatternTemplate': '%s\\zs\\s*\\k\\+',\r\n               When repeating the completion, yields the pattern to search\r\n                for completions. \"%s\" is replaced with the full completion,\r\n                \"%S\" is replaced with just the last added completion part.\r\n                Alternatively, common repeat patterns can also be built from\r\n                the following parts characterized by an anchor, a matching\r\n                atom, and a non-matching in between (this is the default):\r\n    \\       'repeatAnchorExpr': '\\<',\r\n    \\       'repeatPositiveExpr': '\\k',\r\n    \\       'repeatNegativeExpr': '\\%(\\k\\@!\\.\\)',\r\n               Note: You can't mix-and-match here, if you want to override\r\n                repeatNegativeExpr, you also need to specify the previous ones!\r\n    \\   }\r\n    \\}\r\nIn addition, any other a:options from CompleteHelper#FindMatches() can be\r\nspecified, too. These are passed to the CompleteHelper function.\r\n\r\nIf you want to use a different mapping, map your keys to the\r\n(SpecialLocationComplete) mapping target _before_ sourcing the script\r\n(e.g. in your vimrc):\r\n    imap  (SpecialLocationComplete)","first_name":"Ingo","6":"Ingo","last_name":"Karkat","7":"Karkat","releases":[{"0":"5120","vim_version":"7.0","1":"7.0","script_version":"2.00","2":"2.00","version_comment":"- FIX: CompleteHelper#Repeat#Processor() condenses a new line and the following indent to a single space; need to translate that. Otherwise, repeats using %S in the a:options.repeatPatternTemplate will not work on tab-indented or multi-line matches.\r\n- ENH: Add new  default completion of full tag attributes (e.g. ).\r\n- ENH: Support Lists of a:options.patternTemplate and a:options.emptyBasePattern; these are searched sequentially until one yields matches. This allows fallbacks, e.g. a relaxed search anywhere vs. a strict search for base at the beginning.\r\n- ENH: Add new it default completion for text between tags.\r\n- ENH: Add default completions for decimal and hexadecimal numbers, UUIDs.\r\n- ENH: Support sorting of completions via a:options.priority.","3":"- FIX: CompleteHelper#Repeat#Processor() condenses a new line and the following indent to a single space; need to translate that. Otherwise, repeats using %S in the a:options.repeatPatternTemplate will not work on tab-indented or multi-line matches.\r\n- ENH: Add new  default completion of full tag attributes (e.g. ).\r\n- ENH: Support Lists of a:options.patternTemplate and a:options.emptyBasePattern; these are searched sequentially until one yields matches. This allows fallbacks, e.g. a relaxed search anywhere vs. a strict search for base at the beginning.\r\n- ENH: Add new it default completion for text between tags.\r\n- ENH: Add default completions for decimal and hexadecimal numbers, UUIDs.\r\n- ENH: Support sorting of completions via a:options.priority.","package":"SpecialLocationComplete-2.00.vmb.gz","4":"SpecialLocationComplete-2.00.vmb.gz","src_id":"26492","5":"26492","creation_date":"1558324055","6":"1558324055"},{"0":"5120","vim_version":"7.0","1":"7.0","script_version":"1.00","2":"1.00","version_comment":"Initial upload","3":"Initial upload","package":"SpecialLocationComplete-1.00.vmb.gz","4":"SpecialLocationComplete-1.00.vmb.gz","src_id":"22946","5":"22946","creation_date":"1424796422","6":"1424796422"}]},"5119":{"script_id":"5119","0":"5119","script_name":"WholeLineColor","1":"WholeLineColor","script_type":"utility","2":"utility","summary":"plugin for changing background color of lines","3":"plugin for changing background color of lines","description":"Have you ever wanted to mark lines or groups of lines in a way that is easy to see and be be able to jump to those markings? The WholeLineColor plugin lets you do just that. Using Vim's signs feature, the background color of lines can be changed with convenient mappings. Groups of lines can be marked in visual mode with the same mappings. There are also mappings to go to the next and previous group of marked lines.\r\n\r\n\r\nFunctionality\r\n\r\nbu\r\n\r\nRemove set color from current (or selected) lines.\r\n\r\n\r\nbn\r\n\r\nSet background of current or selected lines to green.\r\n\r\n\r\nbg\r\n\r\nSet background of current or selected lines to grey.\r\n\r\n\r\nbl\r\n\r\nSet background of current or selected lines to blue.\r\n\r\n\r\nbp\r\n\r\nSet background of current or selected lines to purple.\r\n\r\n\r\nbr\r\n\r\nSet background of current or selected lines to red.\r\n\r\n\r\nbb\r\n\r\nSet background of current or selected lines to black.\r\n\r\n\r\nThe above mappings work in both normal and visual mode and take a count just\r\nlike built in commands.\r\n\r\nIf you have the vim-repeat plugin (https:\/\/github.com\/tpope\/vim-repeat) installed, you can also repeat any of the above mappings with dot, '.'.\r\n\r\n\r\nbK\r\n\r\nDelete all lines that don't have background color set (keep only lines with\r\nbackground color set).\r\n\r\n\r\nbD\r\n\r\nDelete all lines with background color set.\r\n\r\n\r\nbU\r\n\r\nRemove all set background colors.\r\n\r\n\r\n\r\n\r\nGo to next group of lines with background color set.\r\n\r\n\r\n\r\n\r\nGo to previous group of lines with background color set.\r\n\r\n\r\nOptions\r\n\r\ng:wholelinecolor_leader\r\n\r\nThe key used as the leader to the mappings. The default is .\r\n\r\n\r\ng:wholeline_sign_num\r\n\r\nStarting sign id. The default is 373700. Change this if this is conflicting\r\nwith other sign ids, e.g. sign ids coming from other plugins.\r\n\r\n\r\ng:wholelinecolor_next\r\n\r\nThe keystroke used to go to the next group of lines with background color set.\r\nThe default is .\r\n\r\n\r\ng:wholelinecolor_prev\r\n\r\nThe keystroke used to go to the previous group of lines with background color\r\nset. The default is .\r\n\r\n\r\nThese are the default highlight settings. Change them to suit your preferences.\r\n\r\n    highlight WLCBlackBackground  ctermbg=233 guibg=#121212\r\n    highlight WLCRedBackground    ctermbg=52  guibg=#882323\r\n    highlight WLCBlueBackground   ctermbg=17  guibg=#003366\r\n    highlight WLCPurpleBackground ctermbg=53  guibg=#732c7b\r\n    highlight WLCGreyBackground   ctermbg=238 guibg=#464646\r\n    highlight WLCGreenBackground  ctermbg=22  guibg=#005500","4":"Have you ever wanted to mark lines or groups of lines in a way that is easy to see and be be able to jump to those markings? The WholeLineColor plugin lets you do just that. Using Vim's signs feature, the background color of lines can be changed with convenient mappings. Groups of lines can be marked in visual mode with the same mappings. There are also mappings to go to the next and previous group of marked lines.\r\n\r\n\r\nFunctionality\r\n\r\nbu\r\n\r\nRemove set color from current (or selected) lines.\r\n\r\n\r\nbn\r\n\r\nSet background of current or selected lines to green.\r\n\r\n\r\nbg\r\n\r\nSet background of current or selected lines to grey.\r\n\r\n\r\nbl\r\n\r\nSet background of current or selected lines to blue.\r\n\r\n\r\nbp\r\n\r\nSet background of current or selected lines to purple.\r\n\r\n\r\nbr\r\n\r\nSet background of current or selected lines to red.\r\n\r\n\r\nbb\r\n\r\nSet background of current or selected lines to black.\r\n\r\n\r\nThe above mappings work in both normal and visual mode and take a count just\r\nlike built in commands.\r\n\r\nIf you have the vim-repeat plugin (https:\/\/github.com\/tpope\/vim-repeat) installed, you can also repeat any of the above mappings with dot, '.'.\r\n\r\n\r\nbK\r\n\r\nDelete all lines that don't have background color set (keep only lines with\r\nbackground color set).\r\n\r\n\r\nbD\r\n\r\nDelete all lines with background color set.\r\n\r\n\r\nbU\r\n\r\nRemove all set background colors.\r\n\r\n\r\n\r\n\r\nGo to next group of lines with background color set.\r\n\r\n\r\n\r\n\r\nGo to previous group of lines with background color set.\r\n\r\n\r\nOptions\r\n\r\ng:wholelinecolor_leader\r\n\r\nThe key used as the leader to the mappings. The default is .\r\n\r\n\r\ng:wholeline_sign_num\r\n\r\nStarting sign id. The default is 373700. Change this if this is conflicting\r\nwith other sign ids, e.g. sign ids coming from other plugins.\r\n\r\n\r\ng:wholelinecolor_next\r\n\r\nThe keystroke used to go to the next group of lines with background color set.\r\nThe default is .\r\n\r\n\r\ng:wholelinecolor_prev\r\n\r\nThe keystroke used to go to the previous group of lines with background color\r\nset. The default is .\r\n\r\n\r\nThese are the default highlight settings. Change them to suit your preferences.\r\n\r\n    highlight WLCBlackBackground  ctermbg=233 guibg=#121212\r\n    highlight WLCRedBackground    ctermbg=52  guibg=#882323\r\n    highlight WLCBlueBackground   ctermbg=17  guibg=#003366\r\n    highlight WLCPurpleBackground ctermbg=53  guibg=#732c7b\r\n    highlight WLCGreyBackground   ctermbg=238 guibg=#464646\r\n    highlight WLCGreenBackground  ctermbg=22  guibg=#005500","install_details":"Extract the plugin files in your ~\/.vim (*nix) or ~\/vimfiles (Windows). You should have 2 files:\r\n\r\n    plugin\/wholelinecolor.vim\r\n    doc\/wholelinecolor.txt\r\n\r\nNext, to finish installing the help file run:\r\n\r\n    :helptags ~\/.vim\/doc\r\n\r\nAlternatively, and arguably preferably, use Pathogen and checkout the vim-wholelinecolor directory in your bundle directory. Then, run:\r\n\r\n    :Helptags\r\n","5":"Extract the plugin files in your ~\/.vim (*nix) or ~\/vimfiles (Windows). You should have 2 files:\r\n\r\n    plugin\/wholelinecolor.vim\r\n    doc\/wholelinecolor.txt\r\n\r\nNext, to finish installing the help file run:\r\n\r\n    :helptags ~\/.vim\/doc\r\n\r\nAlternatively, and arguably preferably, use Pathogen and checkout the vim-wholelinecolor directory in your bundle directory. Then, run:\r\n\r\n    :Helptags\r\n","first_name":"Scott","6":"Scott","last_name":"Updike","7":"Updike","releases":[{"0":"5119","vim_version":"7.3","1":"7.3","script_version":"1.0.1","2":"1.0.1","version_comment":"Initial upload","3":"Initial upload","package":"wholelinecolor.tgz","4":"wholelinecolor.tgz","src_id":"22944","5":"22944","creation_date":"1424750067","6":"1424750067"}]},"5118":{"script_id":"5118","0":"5118","script_name":"AppendToClip","1":"AppendToClip","script_type":"utility","2":"utility","summary":"plugin for appending to the default register","3":"plugin for appending to the default register","description":"Have you ever wanted to yank or copy one line at a time from various parts of a file and be able to paste the accumulated results in one operation? Sure, you can do this using named registers using the uppercase letter, but it is cumbersome and unnatural.  The AppendToClip plugin lets you append to the default register (and the clipboard, and primary registers if the 'clipboard' option contains 'unnamed' or 'unnamedplus') in a natural and easy way.\r\n\r\nFunctionality\r\n\r\nyy\r\n\r\nAppend line(s) to the default register, '\"'. Also append to the clipboard,\r\n'*', and primary, '+', registers if the 'clipboard' option contains 'unnamed'\r\nand 'unnamedplus', respectively.\r\n\r\ndd\r\n\r\nDelete and append line(s) to the default register, '\"'. Also append to the\r\nclipboard, '*', and primary, '+', registers if the 'clipboard' option contains\r\n'unnamed' and 'unnamedplus', respectively.\r\n\r\nThese mappings work in both normal and visual mode and take a count just like\r\nthe built in commands 'dd' and 'yy'.\r\n\r\nIf you have the vim-repeat plugin (https:\/\/github.com\/tpope\/vim-repeat) installed, you can repeat either of the above mappings with dot, '.'.\r\n\r\nOptions\r\n\r\ng:appendtoclip_leader\r\n\r\nThe key used as the leader to the mappings. The default is .","4":"Have you ever wanted to yank or copy one line at a time from various parts of a file and be able to paste the accumulated results in one operation? Sure, you can do this using named registers using the uppercase letter, but it is cumbersome and unnatural.  The AppendToClip plugin lets you append to the default register (and the clipboard, and primary registers if the 'clipboard' option contains 'unnamed' or 'unnamedplus') in a natural and easy way.\r\n\r\nFunctionality\r\n\r\nyy\r\n\r\nAppend line(s) to the default register, '\"'. Also append to the clipboard,\r\n'*', and primary, '+', registers if the 'clipboard' option contains 'unnamed'\r\nand 'unnamedplus', respectively.\r\n\r\ndd\r\n\r\nDelete and append line(s) to the default register, '\"'. Also append to the\r\nclipboard, '*', and primary, '+', registers if the 'clipboard' option contains\r\n'unnamed' and 'unnamedplus', respectively.\r\n\r\nThese mappings work in both normal and visual mode and take a count just like\r\nthe built in commands 'dd' and 'yy'.\r\n\r\nIf you have the vim-repeat plugin (https:\/\/github.com\/tpope\/vim-repeat) installed, you can repeat either of the above mappings with dot, '.'.\r\n\r\nOptions\r\n\r\ng:appendtoclip_leader\r\n\r\nThe key used as the leader to the mappings. The default is .","install_details":"Extract the plugin files in your ~\/.vim (*nix) or ~\/vimfiles (Windows). You\r\nshould have 2 files:\r\n\r\n    plugin\/appendtoclip.vim\r\n    doc\/appendtoclip.txt\r\n\r\nNext, to finish installing the help file run:\r\n\r\n    :helptags ~\/.vim\/doc\r\n\r\nAlternatively, and arguably preferably, use Pathogen and checkout the\r\nvim-appendtoclip directory in your bundle directory. Then, run:\r\n\r\n    :Helptags","5":"Extract the plugin files in your ~\/.vim (*nix) or ~\/vimfiles (Windows). You\r\nshould have 2 files:\r\n\r\n    plugin\/appendtoclip.vim\r\n    doc\/appendtoclip.txt\r\n\r\nNext, to finish installing the help file run:\r\n\r\n    :helptags ~\/.vim\/doc\r\n\r\nAlternatively, and arguably preferably, use Pathogen and checkout the\r\nvim-appendtoclip directory in your bundle directory. Then, run:\r\n\r\n    :Helptags","first_name":"Scott","6":"Scott","last_name":"Updike","7":"Updike","releases":[{"0":"5118","vim_version":"7.3","1":"7.3","script_version":"1.0.4","2":"1.0.4","version_comment":"Initial upload","3":"Initial upload","package":"appendtoclip.tgz","4":"appendtoclip.tgz","src_id":"22943","5":"22943","creation_date":"1424748894","6":"1424748894"}]},"5117":{"script_id":"5117","0":"5117","script_name":"vim-stardict","1":"vim-stardict","script_type":"utility","2":"utility","summary":"Looking up meaning of words inside Vim using SDCV dictionary","3":"Looking up meaning of words inside Vim using SDCV dictionary","description":"**Note**: More information & screenshots available at https:\/\/github.com\/phongvcao\/vim-stardict\r\n\r\nA Vim plugin for looking up meaning of words inside Vim and Bash using StarDict Command-Line Version (SDCV) dictionary program.\r\n\r\nIn addition to opening a Vim split and populating it with the output of StarDict Command-Line Version (SDCV), vim-stardict takes advantage of Vim syntax highlighting and some basic regexes to present the words' definitions to the users in an organized and user-friendly way.\r\n\r\nThe plugin was inspired and originally a fork of chusiang\/vim-sdcv: https:\/\/github.com\/chusiang\/vim-sdcv","4":"**Note**: More information & screenshots available at https:\/\/github.com\/phongvcao\/vim-stardict\r\n\r\nA Vim plugin for looking up meaning of words inside Vim and Bash using StarDict Command-Line Version (SDCV) dictionary program.\r\n\r\nIn addition to opening a Vim split and populating it with the output of StarDict Command-Line Version (SDCV), vim-stardict takes advantage of Vim syntax highlighting and some basic regexes to present the words' definitions to the users in an organized and user-friendly way.\r\n\r\nThe plugin was inspired and originally a fork of chusiang\/vim-sdcv: https:\/\/github.com\/chusiang\/vim-sdcv","install_details":"**Note**: More information & screenshots available at https:\/\/github.com\/phongvcao\/vim-stardict\r\n\r\nBefore installing vim-stardict , the following applications need to be already installed in your computer:\r\n\r\n    * SDCV\r\n\r\nThere are several ways to install vim-stardict:\r\n\r\n    * Pathogen\r\n        * git clone https:\/\/github.com\/phongvcao\/vim-stardict.git\r\n\r\n    * NeoBundle\r\n        * NeoBundle 'phongvcao\/vim-stardict'\r\n\r\n    * Vundle\r\n        * Plugin 'phongvcao\/vim-stardict'\r\n\r\n    * Manual\r\n        Copy all of the files into your ~\/.vim directory\r\n\r\n* Usage:\r\n\r\nTo lookup the meaning of a word with no-space-in-between:\r\n\r\n:StarDict random_word_with_no_spaces\r\n\r\nTo lookup the meaning of a word with spaces-in-between, put it inside quotation marks (both double and single quotes are acceptable):\r\n\r\n:StarDict \"random word with spaces\"\r\n:StarDict 'random word with spaces'\r\n\r\nTo look up the meaning of several words (either no-spaces-in-between or spaces-in-between):\r\n\r\n:StarDict first_word second_word \"third word\" 'fourth word'\r\n:StarDict \"first word\" 'second word'\r\n\r\nTo lookup the meaning of a word under-the-cursor:\r\n\r\n:StarDictCursor\r\n\r\nYou can pass arguments of command-line sdcv to :StarDict and :StarDictCursor commands in Vim:\r\n\r\n:StarDict first_word \"second word\" -u \"my_dictionary\" --data-dir \/my\/data\/dir\r\n:StarDictCursor -u \"my_dictionary\" --data-dir \/my\/data\/dir","5":"**Note**: More information & screenshots available at https:\/\/github.com\/phongvcao\/vim-stardict\r\n\r\nBefore installing vim-stardict , the following applications need to be already installed in your computer:\r\n\r\n    * SDCV\r\n\r\nThere are several ways to install vim-stardict:\r\n\r\n    * Pathogen\r\n        * git clone https:\/\/github.com\/phongvcao\/vim-stardict.git\r\n\r\n    * NeoBundle\r\n        * NeoBundle 'phongvcao\/vim-stardict'\r\n\r\n    * Vundle\r\n        * Plugin 'phongvcao\/vim-stardict'\r\n\r\n    * Manual\r\n        Copy all of the files into your ~\/.vim directory\r\n\r\n* Usage:\r\n\r\nTo lookup the meaning of a word with no-space-in-between:\r\n\r\n:StarDict random_word_with_no_spaces\r\n\r\nTo lookup the meaning of a word with spaces-in-between, put it inside quotation marks (both double and single quotes are acceptable):\r\n\r\n:StarDict \"random word with spaces\"\r\n:StarDict 'random word with spaces'\r\n\r\nTo look up the meaning of several words (either no-spaces-in-between or spaces-in-between):\r\n\r\n:StarDict first_word second_word \"third word\" 'fourth word'\r\n:StarDict \"first word\" 'second word'\r\n\r\nTo lookup the meaning of a word under-the-cursor:\r\n\r\n:StarDictCursor\r\n\r\nYou can pass arguments of command-line sdcv to :StarDict and :StarDictCursor commands in Vim:\r\n\r\n:StarDict first_word \"second word\" -u \"my_dictionary\" --data-dir \/my\/data\/dir\r\n:StarDictCursor -u \"my_dictionary\" --data-dir \/my\/data\/dir","first_name":"Phong","6":"Phong","last_name":"Cao","7":"Cao","releases":[{"0":"5117","vim_version":"7.3","1":"7.3","script_version":"0.5.0","2":"0.5.0","version_comment":"* stardict & vstardict commands on Bash\/Zsh now accepts all arguments of command-line sdcv","3":"* stardict & vstardict commands on Bash\/Zsh now accepts all arguments of command-line sdcv","package":"vim-stardict-0.5.0.zip","4":"vim-stardict-0.5.0.zip","src_id":"23751","5":"23751","creation_date":"1448249449","6":"1448249449"},{"0":"5117","vim_version":"7.3","1":"7.3","script_version":"0.4.4","2":"0.4.4","version_comment":"* :StarDict command now accepts --data-dir & -u arguments\r\n* Fixed stardict.py Python piping issue that prevents sdcv -u from getting the definition","3":"* :StarDict command now accepts --data-dir & -u arguments\r\n* Fixed stardict.py Python piping issue that prevents sdcv -u from getting the definition","package":"vim-stardict-0.4.4.zip","4":"vim-stardict-0.4.4.zip","src_id":"23750","5":"23750","creation_date":"1448249415","6":"1448249415"},{"0":"5117","vim_version":"7.3","1":"7.3","script_version":"0.4.3","2":"0.4.3","version_comment":"* Switched back to \/usr\/bin\/python instead of \/usr\/bin\/env python","3":"* Switched back to \/usr\/bin\/python instead of \/usr\/bin\/env python","package":"vim-stardict-0.4.3.zip","4":"vim-stardict-0.4.3.zip","src_id":"23412","5":"23412","creation_date":"1435046651","6":"1435046651"},{"0":"5117","vim_version":"7.3","1":"7.3","script_version":"0.4.2","2":"0.4.2","version_comment":"* Replaced \/usr\/bin\/python with \/usr\/bin\/env python for stardict.py\r\n* Added STARDICT_PYTHON_PATH variable to let users specify the python\r\nexecutable they want to use to execute stardict.py\r\n* Added CONTRIBUTING.md","3":"* Replaced \/usr\/bin\/python with \/usr\/bin\/env python for stardict.py\r\n* Added STARDICT_PYTHON_PATH variable to let users specify the python\r\nexecutable they want to use to execute stardict.py\r\n* Added CONTRIBUTING.md","package":"vim-stardict-0.4.2.zip","4":"vim-stardict-0.4.2.zip","src_id":"23411","5":"23411","creation_date":"1435044950","6":"1435044950"},{"0":"5117","vim_version":"7.3","1":"7.3","script_version":"0.4.1","2":"0.4.1","version_comment":"* Fixed default Python 3 option\r\n* Removed syntax file sourcing\r\n* Removed g:stardict_prefer_python3 option","3":"* Fixed default Python 3 option\r\n* Removed syntax file sourcing\r\n* Removed g:stardict_prefer_python3 option","package":"vim-stardict-0.4.1.zip","4":"vim-stardict-0.4.1.zip","src_id":"23372","5":"23372","creation_date":"1433892886","6":"1433892886"},{"0":"5117","vim_version":"7.3","1":"7.3","script_version":"0.4.0","2":"0.4.0","version_comment":"* Added support for Zsh\r\n* Added custom $STARDICT_DIR variable to let users specify vim-stardict installation directory","3":"* Added support for Zsh\r\n* Added custom $STARDICT_DIR variable to let users specify vim-stardict installation directory","package":"vim-stardict-0.4.0.zip","4":"vim-stardict-0.4.0.zip","src_id":"23191","5":"23191","creation_date":"1429423292","6":"1429423292"},{"0":"5117","vim_version":"7.3","1":"7.3","script_version":"0.3.3","2":"0.3.3","version_comment":"* Fixed wrong highlighting of words' examples\r\n","3":"* Fixed wrong highlighting of words' examples\r\n","package":"vim-stardict-0.3.3.zip","4":"vim-stardict-0.3.3.zip","src_id":"23065","5":"23065","creation_date":"1426789930","6":"1426789930"},{"0":"5117","vim_version":"7.3","1":"7.3","script_version":"0.3.2","2":"0.3.2","version_comment":"* Fixed :split and :vsplit opening delay\r\n* Fixed multiple :split open at a time\r\n* Reuse last 'stardict' buffer if there is one\r\n* Hide 'vim-stardict' buffer from buffer list\r\n* Removed buffer cache of old word meaning history","3":"* Fixed :split and :vsplit opening delay\r\n* Fixed multiple :split open at a time\r\n* Reuse last 'stardict' buffer if there is one\r\n* Hide 'vim-stardict' buffer from buffer list\r\n* Removed buffer cache of old word meaning history","package":"vim-stardict-0.3.2.zip","4":"vim-stardict-0.3.2.zip","src_id":"22965","5":"22965","creation_date":"1425216808","6":"1425216808"},{"0":"5117","vim_version":"7.3","1":"7.3","script_version":"0.3.1","2":"0.3.1","version_comment":"* Restore mouse cursor after viewing definition","3":"* Restore mouse cursor after viewing definition","package":"vim-stardict-0.3.1.zip","4":"vim-stardict-0.3.1.zip","src_id":"22964","5":"22964","creation_date":"1425216775","6":"1425216775"},{"0":"5117","vim_version":"7.3","1":"7.3","script_version":"0.3.0","2":"0.3.0","version_comment":"* Added output colors customization for Vim and Bash\r\n* Fixed extra split in Vim","3":"* Added output colors customization for Vim and Bash\r\n* Fixed extra split in Vim","package":"vim-stardict-0.3.0.zip","4":"vim-stardict-0.3.0.zip","src_id":"22963","5":"22963","creation_date":"1425216746","6":"1425216746"},{"0":"5117","vim_version":"7.3","1":"7.3","script_version":"0.2.0","2":"0.2.0","version_comment":"    * Added support for Bash\r\n    * Added output redirection from Bash to Vim\r\n    * Fixed some highlight errors on Vim and Bash\r\n    * Changed highlighting color for \"Found ... items\"","3":"    * Added support for Bash\r\n    * Added output redirection from Bash to Vim\r\n    * Fixed some highlight errors on Vim and Bash\r\n    * Changed highlighting color for \"Found ... items\"","package":"vim-stardict.zip","4":"vim-stardict.zip","src_id":"22955","5":"22955","creation_date":"1424959199","6":"1424959199"},{"0":"5117","vim_version":"7.3","1":"7.3","script_version":"0.1.0","2":"0.1.0","version_comment":"Initial upload","3":"Initial upload","package":"vim-stardict.zip","4":"vim-stardict.zip","src_id":"22941","5":"22941","creation_date":"1424716001","6":"1424716001"}]},"5116":{"script_id":"5116","0":"5116","script_name":"vim-consul","1":"vim-consul","script_type":"utility","2":"utility","summary":"basic vim\/consul integration","3":"basic vim\/consul integration","description":"This plugin adds a :Consul command that runs consul, with tab completion of subcommands.","4":"This plugin adds a :Consul command that runs consul, with tab completion of subcommands.","install_details":"","5":"","first_name":"Mark","6":"Mark","last_name":"Cornick","7":"Cornick","releases":[{"0":"5116","vim_version":"7.0","1":"7.0","script_version":"1.0.0","2":"1.0.0","version_comment":"Initial upload","3":"Initial upload","package":"vim-consul.tar.gz","4":"vim-consul.tar.gz","src_id":"22932","5":"22932","creation_date":"1424548382","6":"1424548382"}]},"5115":{"script_id":"5115","0":"5115","script_name":"vim-fixprotocol","1":"vim-fixprotocol","script_type":"utility","2":"utility","summary":"parse a FIX protocol message into xml","3":"parse a FIX protocol message into xml","description":"This plugin transforms FIX protocol messages to XML, translating FieldNumbers to FieldNames.\r\n\r\nDetailed description: https:\/\/bitbucket.org\/vappolinario\/vim-fixprotocol\r\n","4":"This plugin transforms FIX protocol messages to XML, translating FieldNumbers to FieldNames.\r\n\r\nDetailed description: https:\/\/bitbucket.org\/vappolinario\/vim-fixprotocol\r\n","install_details":"1. Download the vim-fixprotocol.zip file and unzip the files to the $HOME\/.vim or the \r\n    $HOME\/vimfiles or the $VIM\/vimfiles directory. \r\n   Refer to the |add-plugin|, |add-global-plugin| and |runtimepath| Vim \r\n   help pages for more details about installing Vim plugins. \r\n2. Change to the $HOME\/.vim\/doc or $HOME\/vimfiles\/doc or $VIM\/vimfiles\/doc \r\n    directory, start Vim and run the \":helptags .\" command to process the \r\n    taglist help file. Without this step, you cannot jump to the taglist help \r\n    topics.","5":"1. Download the vim-fixprotocol.zip file and unzip the files to the $HOME\/.vim or the \r\n    $HOME\/vimfiles or the $VIM\/vimfiles directory. \r\n   Refer to the |add-plugin|, |add-global-plugin| and |runtimepath| Vim \r\n   help pages for more details about installing Vim plugins. \r\n2. Change to the $HOME\/.vim\/doc or $HOME\/vimfiles\/doc or $VIM\/vimfiles\/doc \r\n    directory, start Vim and run the \":helptags .\" command to process the \r\n    taglist help file. Without this step, you cannot jump to the taglist help \r\n    topics.","first_name":"Vitor","6":"Vitor","last_name":"Appolinario","7":"Appolinario","releases":[{"0":"5115","vim_version":"7.0","1":"7.0","script_version":"0.2","2":"0.2","version_comment":"Syntax Highlight for FIX messages\r\nTranslation of message types","3":"Syntax Highlight for FIX messages\r\nTranslation of message types","package":"vim-fixprotocol.zip","4":"vim-fixprotocol.zip","src_id":"23164","5":"23164","creation_date":"1428789063","6":"1428789063"},{"0":"5115","vim_version":"7.3","1":"7.3","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"vim-fixprotocol.7z","4":"vim-fixprotocol.7z","src_id":"22931","5":"22931","creation_date":"1424547856","6":"1424547856"}]},"5114":{"script_id":"5114","0":"5114","script_name":"vim-webdevicons","1":"vim-webdevicons","script_type":"utility","2":"utility","summary":"Adds file type glyphs\/icons to popular Vim plugins: NERDTree, vim-airline, Power","3":"Adds file type glyphs\/icons to popular Vim plugins: NERDTree, vim-airline, Power","description":"Adds file type glyphs\/icons to popular Vim plugins: NERDTree, vim-airline, Powerline, Unite, vim-startify and more\r\n\r\nNOTE: I highly recommend pulling from the repo and managing this plugin with a plugin manager instead of manually!\r\n\r\n* Overview Screenshot: https:\/\/raw.githubusercontent.com\/wiki\/ryanoasis\/vim-devicons\/screenshots\/v0.9.x\/overall-screenshot.png\r\n\r\n* More Details: https:\/\/github.com\/ryanoasis\/vim-devicons","4":"Adds file type glyphs\/icons to popular Vim plugins: NERDTree, vim-airline, Powerline, Unite, vim-startify and more\r\n\r\nNOTE: I highly recommend pulling from the repo and managing this plugin with a plugin manager instead of manually!\r\n\r\n* Overview Screenshot: https:\/\/raw.githubusercontent.com\/wiki\/ryanoasis\/vim-devicons\/screenshots\/v0.9.x\/overall-screenshot.png\r\n\r\n* More Details: https:\/\/github.com\/ryanoasis\/vim-devicons","install_details":"https:\/\/github.com\/ryanoasis\/vim-devicons#installation","5":"https:\/\/github.com\/ryanoasis\/vim-devicons#installation","first_name":"Ryan","6":"Ryan","last_name":"McIntyre","7":"McIntyre","releases":[{"0":"5114","vim_version":"7.0","1":"7.0","script_version":"v0.11.0","2":"v0.11.0","version_comment":"https:\/\/github.com\/ryanoasis\/vim-devicons\/releases\/tag\/v0.11.0","3":"https:\/\/github.com\/ryanoasis\/vim-devicons\/releases\/tag\/v0.11.0","package":"vim-devicons-v0.11.0.zip","4":"vim-devicons-v0.11.0.zip","src_id":"26392","5":"26392","creation_date":"1550401483","6":"1550401483"},{"0":"5114","vim_version":"7.0","1":"7.0","script_version":"v0.10.0","2":"v0.10.0","version_comment":"https:\/\/github.com\/ryanoasis\/vim-devicons\/releases\/tag\/v0.10.0","3":"https:\/\/github.com\/ryanoasis\/vim-devicons\/releases\/tag\/v0.10.0","package":"vim-devicons-v0.10.0.zip","4":"vim-devicons-v0.10.0.zip","src_id":"25831","5":"25831","creation_date":"1519011310","6":"1519011310"},{"0":"5114","vim_version":"7.0","1":"7.0","script_version":"v0.9.3","2":"v0.9.3","version_comment":"https:\/\/github.com\/ryanoasis\/vim-devicons\/releases\/tag\/v0.9.3","3":"https:\/\/github.com\/ryanoasis\/vim-devicons\/releases\/tag\/v0.9.3","package":"vim-devicons-v0.9.3.zip","4":"vim-devicons-v0.9.3.zip","src_id":"25614","5":"25614","creation_date":"1508622179","6":"1508622179"},{"0":"5114","vim_version":"7.0","1":"7.0","script_version":"v0.9.2","2":"v0.9.2","version_comment":"https:\/\/github.com\/ryanoasis\/vim-devicons\/releases\/tag\/v0.9.2","3":"https:\/\/github.com\/ryanoasis\/vim-devicons\/releases\/tag\/v0.9.2","package":"vim-devicons-v0.9.2.zip","4":"vim-devicons-v0.9.2.zip","src_id":"25272","5":"25272","creation_date":"1496086872","6":"1496086872"},{"0":"5114","vim_version":"7.0","1":"7.0","script_version":"v0.9.1","2":"v0.9.1","version_comment":"https:\/\/github.com\/ryanoasis\/vim-devicons\/releases\/tag\/v0.9.1","3":"https:\/\/github.com\/ryanoasis\/vim-devicons\/releases\/tag\/v0.9.1","package":"vim-devicons-v0.9.1.zip","4":"vim-devicons-v0.9.1.zip","src_id":"25163","5":"25163","creation_date":"1494248772","6":"1494248772"},{"0":"5114","vim_version":"7.0","1":"7.0","script_version":"v0.9.0","2":"v0.9.0","version_comment":"https:\/\/github.com\/ryanoasis\/vim-devicons\/releases\/tag\/v0.9.0","3":"https:\/\/github.com\/ryanoasis\/vim-devicons\/releases\/tag\/v0.9.0","package":"vim-devicons-v0.9.0.zip","4":"vim-devicons-v0.9.0.zip","src_id":"25110","5":"25110","creation_date":"1493591624","6":"1493591624"},{"0":"5114","vim_version":"7.0","1":"7.0","script_version":"v0.8.6","2":"v0.8.6","version_comment":"https:\/\/github.com\/ryanoasis\/vim-devicons\/releases\/tag\/v0.8.6","3":"https:\/\/github.com\/ryanoasis\/vim-devicons\/releases\/tag\/v0.8.6","package":"vim-devicons-v0.8.6.zip","4":"vim-devicons-v0.8.6.zip","src_id":"24997","5":"24997","creation_date":"1488034516","6":"1488034516"},{"0":"5114","vim_version":"7.0","1":"7.0","script_version":"v0.8.5","2":"v0.8.5","version_comment":"https:\/\/github.com\/ryanoasis\/vim-devicons\/releases\/tag\/v0.8.5","3":"https:\/\/github.com\/ryanoasis\/vim-devicons\/releases\/tag\/v0.8.5","package":"vim-devicons-v0.8.5.zip","4":"vim-devicons-v0.8.5.zip","src_id":"24654","5":"24654","creation_date":"1476920341","6":"1476920341"},{"0":"5114","vim_version":"7.0","1":"7.0","script_version":"v0.8.4","2":"v0.8.4","version_comment":"https:\/\/github.com\/ryanoasis\/vim-devicons\/releases\/tag\/v0.8.4","3":"https:\/\/github.com\/ryanoasis\/vim-devicons\/releases\/tag\/v0.8.4","package":"vim-devicons-v0.8.4.zip","4":"vim-devicons-v0.8.4.zip","src_id":"24396","5":"24396","creation_date":"1469407506","6":"1469407506"},{"0":"5114","vim_version":"7.0","1":"7.0","script_version":"v0.8.3","2":"v0.8.3","version_comment":"https:\/\/github.com\/ryanoasis\/vim-devicons\/releases\/tag\/v0.8.3","3":"https:\/\/github.com\/ryanoasis\/vim-devicons\/releases\/tag\/v0.8.3","package":"vim-devicons-v0.8.3.zip","4":"vim-devicons-v0.8.3.zip","src_id":"24312","5":"24312","creation_date":"1465336643","6":"1465336643"},{"0":"5114","vim_version":"7.0","1":"7.0","script_version":"v0.8.2","2":"v0.8.2","version_comment":"https:\/\/github.com\/ryanoasis\/vim-devicons\/releases\/tag\/v0.8.2","3":"https:\/\/github.com\/ryanoasis\/vim-devicons\/releases\/tag\/v0.8.2","package":"vim-devicons-v0.8.2.zip","4":"vim-devicons-v0.8.2.zip","src_id":"24182","5":"24182","creation_date":"1460908028","6":"1460908028"},{"0":"5114","vim_version":"7.0","1":"7.0","script_version":"v0.8.1","2":"v0.8.1","version_comment":"https:\/\/github.com\/ryanoasis\/vim-devicons\/releases\/tag\/v0.8.1","3":"https:\/\/github.com\/ryanoasis\/vim-devicons\/releases\/tag\/v0.8.1","package":"vim-devicons-v0.8.1.zip","4":"vim-devicons-v0.8.1.zip","src_id":"24078","5":"24078","creation_date":"1457459476","6":"1457459476"},{"0":"5114","vim_version":"7.0","1":"7.0","script_version":"v0.8.0","2":"v0.8.0","version_comment":"https:\/\/github.com\/ryanoasis\/vim-devicons\/releases\/tag\/v0.8.0","3":"https:\/\/github.com\/ryanoasis\/vim-devicons\/releases\/tag\/v0.8.0","package":"vim-devicons-v0.8.0.zip","4":"vim-devicons-v0.8.0.zip","src_id":"23999","5":"23999","creation_date":"1455037407","6":"1455037407"},{"0":"5114","vim_version":"7.0","1":"7.0","script_version":"v0.7.1","2":"v0.7.1","version_comment":"https:\/\/github.com\/ryanoasis\/vim-devicons\/releases\/tag\/v0.7.1","3":"https:\/\/github.com\/ryanoasis\/vim-devicons\/releases\/tag\/v0.7.1","package":"vim-devicons-v0.7.1.zip","4":"vim-devicons-v0.7.1.zip","src_id":"23905","5":"23905","creation_date":"1452783975","6":"1452783975"},{"0":"5114","vim_version":"7.0","1":"7.0","script_version":"v0.7.0","2":"v0.7.0","version_comment":"https:\/\/github.com\/ryanoasis\/vim-devicons\/releases\/tag\/v0.7.0","3":"https:\/\/github.com\/ryanoasis\/vim-devicons\/releases\/tag\/v0.7.0","package":"vim-devicons-v0.7.0.zip","4":"vim-devicons-v0.7.0.zip","src_id":"23800","5":"23800","creation_date":"1450482394","6":"1450482394"},{"0":"5114","vim_version":"7.0","1":"7.0","script_version":"v0.6.1","2":"v0.6.1","version_comment":"https:\/\/github.com\/ryanoasis\/vim-devicons\/releases\/tag\/v0.6.1","3":"https:\/\/github.com\/ryanoasis\/vim-devicons\/releases\/tag\/v0.6.1","package":"vim-devicons-v0.6.1.zip","4":"vim-devicons-v0.6.1.zip","src_id":"23652","5":"23652","creation_date":"1444231532","6":"1444231532"},{"0":"5114","vim_version":"7.0","1":"7.0","script_version":"v0.6.0","2":"v0.6.0","version_comment":"https:\/\/github.com\/ryanoasis\/vim-devicons\/releases\/tag\/v0.6.0","3":"https:\/\/github.com\/ryanoasis\/vim-devicons\/releases\/tag\/v0.6.0","package":"vim-devicons-v0.6.0.zip","4":"vim-devicons-v0.6.0.zip","src_id":"23595","5":"23595","creation_date":"1442269788","6":"1442269788"},{"0":"5114","vim_version":"7.0","1":"7.0","script_version":"v0.5.4","2":"v0.5.4","version_comment":"https:\/\/github.com\/ryanoasis\/vim-devicons\/releases\/tag\/v0.5.4","3":"https:\/\/github.com\/ryanoasis\/vim-devicons\/releases\/tag\/v0.5.4","package":"vim-devicons-v0.5.4.zip","4":"vim-devicons-v0.5.4.zip","src_id":"23570","5":"23570","creation_date":"1441121937","6":"1441121937"},{"0":"5114","vim_version":"7.0","1":"7.0","script_version":"v0.5.3","2":"v0.5.3","version_comment":"https:\/\/github.com\/ryanoasis\/vim-devicons\/releases\/tag\/v0.5.3","3":"https:\/\/github.com\/ryanoasis\/vim-devicons\/releases\/tag\/v0.5.3","package":"vim-devicons-v0.5.3.zip","4":"vim-devicons-v0.5.3.zip","src_id":"23530","5":"23530","creation_date":"1440076382","6":"1440076382"},{"0":"5114","vim_version":"7.0","1":"7.0","script_version":"v0.5.2","2":"v0.5.2","version_comment":"https:\/\/github.com\/ryanoasis\/vim-devicons\/releases\/tag\/v0.5.2","3":"https:\/\/github.com\/ryanoasis\/vim-devicons\/releases\/tag\/v0.5.2","package":"vim-devicons-v0.5.2.zip","4":"vim-devicons-v0.5.2.zip","src_id":"23501","5":"23501","creation_date":"1438693295","6":"1438693295"},{"0":"5114","vim_version":"7.0","1":"7.0","script_version":"v0.5.1","2":"v0.5.1","version_comment":"https:\/\/github.com\/ryanoasis\/vim-devicons\/releases\/tag\/v0.5.1","3":"https:\/\/github.com\/ryanoasis\/vim-devicons\/releases\/tag\/v0.5.1","package":"vim-devicons-v0.5.1.zip","4":"vim-devicons-v0.5.1.zip","src_id":"23486","5":"23486","creation_date":"1438002578","6":"1438002578"},{"0":"5114","vim_version":"7.0","1":"7.0","script_version":"v0.5.0","2":"v0.5.0","version_comment":"https:\/\/github.com\/ryanoasis\/vim-devicons\/releases\/tag\/v0.5.0","3":"https:\/\/github.com\/ryanoasis\/vim-devicons\/releases\/tag\/v0.5.0","package":"vim-devicons-v0.5.0.zip","4":"vim-devicons-v0.5.0.zip","src_id":"23471","5":"23471","creation_date":"1436794137","6":"1436794137"},{"0":"5114","vim_version":"7.0","1":"7.0","script_version":"v0.4.4","2":"v0.4.4","version_comment":"https:\/\/github.com\/ryanoasis\/vim-webdevicons\/releases\/tag\/v0.4.4","3":"https:\/\/github.com\/ryanoasis\/vim-webdevicons\/releases\/tag\/v0.4.4","package":"vim-webdevicons-v0.4.4.zip","4":"vim-webdevicons-v0.4.4.zip","src_id":"23448","5":"23448","creation_date":"1436186707","6":"1436186707"},{"0":"5114","vim_version":"7.0","1":"7.0","script_version":"v0.4.3","2":"v0.4.3","version_comment":"https:\/\/github.com\/ryanoasis\/vim-webdevicons\/releases\/tag\/v0.4.3","3":"https:\/\/github.com\/ryanoasis\/vim-webdevicons\/releases\/tag\/v0.4.3","package":"vim-webdevicons-v0.4.3.zip","4":"vim-webdevicons-v0.4.3.zip","src_id":"23430","5":"23430","creation_date":"1435755400","6":"1435755400"},{"0":"5114","vim_version":"7.0","1":"7.0","script_version":"v0.4.2","2":"v0.4.2","version_comment":"https:\/\/github.com\/ryanoasis\/vim-webdevicons\/releases\/tag\/v0.4.2","3":"https:\/\/github.com\/ryanoasis\/vim-webdevicons\/releases\/tag\/v0.4.2","package":"vim-webdevicons-v0.4.2.zip","4":"vim-webdevicons-v0.4.2.zip","src_id":"23409","5":"23409","creation_date":"1434983177","6":"1434983177"},{"0":"5114","vim_version":"7.0","1":"7.0","script_version":"v0.4.1","2":"v0.4.1","version_comment":"https:\/\/github.com\/ryanoasis\/vim-webdevicons\/releases\/tag\/v0.4.1","3":"https:\/\/github.com\/ryanoasis\/vim-webdevicons\/releases\/tag\/v0.4.1","package":"vim-webdevicons-v0.4.1.zip","4":"vim-webdevicons-v0.4.1.zip","src_id":"23389","5":"23389","creation_date":"1434371632","6":"1434371632"},{"0":"5114","vim_version":"7.0","1":"7.0","script_version":"v0.4.0","2":"v0.4.0","version_comment":"https:\/\/github.com\/ryanoasis\/vim-webdevicons\/releases\/tag\/v0.4.0","3":"https:\/\/github.com\/ryanoasis\/vim-webdevicons\/releases\/tag\/v0.4.0","package":"vim-webdevicons-v0.4.0.zip","4":"vim-webdevicons-v0.4.0.zip","src_id":"23369","5":"23369","creation_date":"1433768235","6":"1433768235"},{"0":"5114","vim_version":"7.0","1":"7.0","script_version":"v0.3.3","2":"v0.3.3","version_comment":"Initial upload","3":"Initial upload","package":"vim-webdevicons.zip","4":"vim-webdevicons.zip","src_id":"22928","5":"22928","creation_date":"1424475860","6":"1424475860"}]},"5113":{"script_id":"5113","0":"5113","script_name":"sonicpi.vim","1":"sonicpi.vim","script_type":"syntax","2":"syntax","summary":"Syntax highlighting and autocomplete for Sonic Pi \/ Ruby files","3":"Syntax highlighting and autocomplete for Sonic Pi \/ Ruby files","description":"Sonic Pi is a \"free sound synthesiser for live coding designed to support computing and music lessons within schools,\" a Ruby-based frontend to a SuperCollider server, and an accessible GUI to support the above (http:\/\/www.sonic-pi.net).\r\n\r\nThis vim plugin is intended as a replacement for the \"accessible GUI,\" extending Ruby's syntax highlighting to include Sonic Pi directives, supporting contextual autocompletion (for omnicomplete), and sending Sonic Pi code to the Sonic Pi server.\r\n\r\nIt becomes active when Sonic Pi is running and the Ruby filetype event occurs, unless explicitly disabled as outlined in the README.\r\n\r\nIt requires Sonic Pi 2.4 or greater, and sonic-pi-cli (https:\/\/github.com\/Widdershin\/sonic-pi-cli\/)","4":"Sonic Pi is a \"free sound synthesiser for live coding designed to support computing and music lessons within schools,\" a Ruby-based frontend to a SuperCollider server, and an accessible GUI to support the above (http:\/\/www.sonic-pi.net).\r\n\r\nThis vim plugin is intended as a replacement for the \"accessible GUI,\" extending Ruby's syntax highlighting to include Sonic Pi directives, supporting contextual autocompletion (for omnicomplete), and sending Sonic Pi code to the Sonic Pi server.\r\n\r\nIt becomes active when Sonic Pi is running and the Ruby filetype event occurs, unless explicitly disabled as outlined in the README.\r\n\r\nIt requires Sonic Pi 2.4 or greater, and sonic-pi-cli (https:\/\/github.com\/Widdershin\/sonic-pi-cli\/)","install_details":"Place contents of tarball in ~\/.vim\/bundle\/ as a pathogen install.","5":"Place contents of tarball in ~\/.vim\/bundle\/ as a pathogen install.","first_name":"","6":"","last_name":"","7":"","releases":[{"0":"5113","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"sonicpi.vim.tgz","4":"sonicpi.vim.tgz","src_id":"22926","5":"22926","creation_date":"1424315608","6":"1424315608"}]},"5112":{"script_id":"5112","0":"5112","script_name":"Perfect Dark","1":"Perfect Dark","script_type":"color scheme","2":"color scheme","summary":"Dark & cold color scheme inspired by gedit","3":"Dark & cold color scheme inspired by gedit","description":"This is a darkish scheme with various cold colors of which most are green\/blue.\r\n\r\nRecommend to install vimscript #4293 and vimscript #1640 to support STL and C++11.\r\n\r\nNote that this color scheme does not specify colors in terminal, BUT you can install https:\/\/github.com\/godlygeek\/csapprox and follow steps in https:\/\/github.com\/godlygeek\/csapprox\/blob\/master\/doc\/CSApprox.txt to get full-color support in terminal, which just works well in my gnome-terminal.\r\n\r\nNote2: I failed to make this scheme compatible with win32 vim terminal.\r\n\r\nScreenshots:\r\nIn Linux GVim: http:\/\/i1377.photobucket.com\/albums\/ah43\/lz96\/perfectdark_zpsa7099350.png\r\nIn Windows GVim: http:\/\/i1377.photobucket.com\/albums\/ah43\/lz96\/win_zps3c95ecff.jpg\r\nIn Linux terminal (vimcat): http:\/\/i1377.photobucket.com\/albums\/ah43\/lz96\/perfectDarkinterm_zps34785a7a.png","4":"This is a darkish scheme with various cold colors of which most are green\/blue.\r\n\r\nRecommend to install vimscript #4293 and vimscript #1640 to support STL and C++11.\r\n\r\nNote that this color scheme does not specify colors in terminal, BUT you can install https:\/\/github.com\/godlygeek\/csapprox and follow steps in https:\/\/github.com\/godlygeek\/csapprox\/blob\/master\/doc\/CSApprox.txt to get full-color support in terminal, which just works well in my gnome-terminal.\r\n\r\nNote2: I failed to make this scheme compatible with win32 vim terminal.\r\n\r\nScreenshots:\r\nIn Linux GVim: http:\/\/i1377.photobucket.com\/albums\/ah43\/lz96\/perfectdark_zpsa7099350.png\r\nIn Windows GVim: http:\/\/i1377.photobucket.com\/albums\/ah43\/lz96\/win_zps3c95ecff.jpg\r\nIn Linux terminal (vimcat): http:\/\/i1377.photobucket.com\/albums\/ah43\/lz96\/perfectDarkinterm_zps34785a7a.png","install_details":"Place in your ~\/.vim\/colors\/ (Xnix) or $VIMRUNTIME\\colors (Windows), then run :colorscheme PerfectDark","5":"Place in your ~\/.vim\/colors\/ (Xnix) or $VIMRUNTIME\\colors (Windows), then run :colorscheme PerfectDark","first_name":"Vic","6":"Vic","last_name":"Luo","7":"Luo","releases":[{"0":"5112","vim_version":"7.0","1":"7.0","script_version":"1.2","2":"1.2","version_comment":"Support cCustomClass of vim-cpp-enhanced-highlight","3":"Support cCustomClass of vim-cpp-enhanced-highlight","package":"PerfectDark.vim","4":"PerfectDark.vim","src_id":"23992","5":"23992","creation_date":"1454739261","6":"1454739261"},{"0":"5112","vim_version":"7.0","1":"7.0","script_version":"1.1","2":"1.1","version_comment":"Slightly increase the brightness of number to make it more readable","3":"Slightly increase the brightness of number to make it more readable","package":"PerfectDark.vim","4":"PerfectDark.vim","src_id":"23587","5":"23587","creation_date":"1442025204","6":"1442025204"},{"0":"5112","vim_version":"7.0","1":"7.0","script_version":"1.0-noterm","2":"1.0-noterm","version_comment":"This version removes cterm colors to be compatible with auto color converting plugin.\r\nONLY if 1.0 doesn't work properly in vim terminal should you use this.\r\nNOTE: I failed to make this scheme compatible with win32 vim terminal.","3":"This version removes cterm colors to be compatible with auto color converting plugin.\r\nONLY if 1.0 doesn't work properly in vim terminal should you use this.\r\nNOTE: I failed to make this scheme compatible with win32 vim terminal.","package":"PerfectDark.vim","4":"PerfectDark.vim","src_id":"22923","5":"22923","creation_date":"1424236595","6":"1424236595"},{"0":"5112","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"PerfectDark.vim","4":"PerfectDark.vim","src_id":"22921","5":"22921","creation_date":"1424184754","6":"1424184754"}]},"5111":{"script_id":"5111","0":"5111","script_name":"glsl_es_100.vim","1":"glsl_es_100.vim","script_type":"syntax","2":"syntax","summary":"Syntax file for GLSL ES 100","3":"Syntax file for GLSL ES 100","description":"Syntax file for GLSL ES 100\r\n\r\nNo extensions.\r\nAs defined in the specifications: https:\/\/www.khronos.org\/registry\/gles\/specs\/2.0\/GLSL_ES_Specification_1.0.17.pdf\r\nSwizzles are highlighted if more than one component is used.\r\nThe followind highlights groups are used:\r\n- Number\r\n- Comment\r\n- Operator\r\n- Type\r\n- Keyword\r\n- PreProc\r\n- Special\r\n- Constant\r\n- Function\r\n\r\nhttps:\/\/github.com\/zeduckmaster\/vim-glsl","4":"Syntax file for GLSL ES 100\r\n\r\nNo extensions.\r\nAs defined in the specifications: https:\/\/www.khronos.org\/registry\/gles\/specs\/2.0\/GLSL_ES_Specification_1.0.17.pdf\r\nSwizzles are highlighted if more than one component is used.\r\nThe followind highlights groups are used:\r\n- Number\r\n- Comment\r\n- Operator\r\n- Type\r\n- Keyword\r\n- PreProc\r\n- Special\r\n- Constant\r\n- Function\r\n\r\nhttps:\/\/github.com\/zeduckmaster\/vim-glsl","install_details":"Copy it in \/syntax directory.\r\nMake file associations in your vimrc.\r\n","5":"Copy it in \/syntax directory.\r\nMake file associations in your vimrc.\r\n","first_name":"david","6":"david","last_name":"cremoux","7":"cremoux","releases":[{"0":"5111","vim_version":"7.0","1":"7.0","script_version":"0.2","2":"0.2","version_comment":"added multi-line comments","3":"added multi-line comments","package":"glsl_es_100.vim","4":"glsl_es_100.vim","src_id":"22914","5":"22914","creation_date":"1423821666","6":"1423821666"}]},"5110":{"script_id":"5110","0":"5110","script_name":"pl65.vim","1":"pl65.vim","script_type":"syntax","2":"syntax","summary":"Syntax file for Noahsoft\\'s PL65 for Atari 8-bit computers","3":"Syntax file for Noahsoft\\'s PL65 for Atari 8-bit computers","description":"Simple color highlighting for Noahsoft\\'s PL65 for Atari 8-bit home computers. Created in preparation for a Retrochallenge 2015\/01 project.","4":"Simple color highlighting for Noahsoft\\'s PL65 for Atari 8-bit home computers. Created in preparation for a Retrochallenge 2015\/01 project.","install_details":"1. Pull the file pl65.vim to your ~\/.vim\/syntax directory\r\n2. Create the file ~\/.vim\/ftdetect\/pl65.vim and put the following inside:\r\n\r\nau BufRead,BufNewFile *.pl65 set filetype=pl65\r\n\r\n3. Edit Atari PL65 files using .pl65 extension","5":"1. Pull the file pl65.vim to your ~\/.vim\/syntax directory\r\n2. Create the file ~\/.vim\/ftdetect\/pl65.vim and put the following inside:\r\n\r\nau BufRead,BufNewFile *.pl65 set filetype=pl65\r\n\r\n3. Edit Atari PL65 files using .pl65 extension","first_name":"Michael","6":"Michael","last_name":"Sternberg","7":"Sternberg","releases":[{"0":"5110","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"pl65.vim","4":"pl65.vim","src_id":"22908","5":"22908","creation_date":"1423724672","6":"1423724672"}]},"5109":{"script_id":"5109","0":"5109","script_name":"delview","1":"delview","script_type":"utility","2":"utility","summary":"'delview' command to delete mkview\/loadview files","3":"'delview' command to delete mkview\/loadview files","description":"vim has the ability to save and load views with the mkview\/loadview files, which are used in some tips as such:\r\n\r\n  au BufWinLeave ?* mkview\r\n  au BufWinEnter ?* silent loadview\r\n\r\nUnfortunately there is one piece of functionality missing, the ability to delete or clear these views.  Currently you need to either use ':autoload edit ' to open the file without a view and then save that as a new view, or else you need to figure out where the vim 'views' directory is and manually delete the files with a file explorer or shell.\r\n\r\nThis script gives you the simple command to delete the views for the current buffer:\r\n\r\n  :delview","4":"vim has the ability to save and load views with the mkview\/loadview files, which are used in some tips as such:\r\n\r\n  au BufWinLeave ?* mkview\r\n  au BufWinEnter ?* silent loadview\r\n\r\nUnfortunately there is one piece of functionality missing, the ability to delete or clear these views.  Currently you need to either use ':autoload edit ' to open the file without a view and then save that as a new view, or else you need to figure out where the vim 'views' directory is and manually delete the files with a file explorer or shell.\r\n\r\nThis script gives you the simple command to delete the views for the current buffer:\r\n\r\n  :delview","install_details":"Source this script or just copy these lines into your .vimrc","5":"Source this script or just copy these lines into your .vimrc","first_name":"David","6":"David","last_name":"Madison","7":"Madison","releases":[{"0":"5109","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"delview.vim","4":"delview.vim","src_id":"22905","5":"22905","creation_date":"1423676541","6":"1423676541"}]},"5108":{"script_id":"5108","0":"5108","script_name":"vim-hackernews","1":"vim-hackernews","script_type":"utility","2":"utility","summary":"Browse Hacker News in Vim","3":"Browse Hacker News in Vim","description":"Browse Hacker News in Vim\r\n\r\nhttps:\/\/github.com\/ryanss\/vim-hackernews","4":"Browse Hacker News in Vim\r\n\r\nhttps:\/\/github.com\/ryanss\/vim-hackernews","install_details":"","5":"","first_name":"ryanss","6":"ryanss","last_name":"","7":"","releases":[{"0":"5108","vim_version":"7.3","1":"7.3","script_version":"0.2","2":"0.2","version_comment":"Adds Python 3 support, additional motions, comment thread folding, ability to display specific HackerNews lists (top, ask, show, etc) and handle all HackerNews item types properly (poll, job, etc). Dozens of other bug fixes and improvements","3":"Adds Python 3 support, additional motions, comment thread folding, ability to display specific HackerNews lists (top, ask, show, etc) and handle all HackerNews item types properly (poll, job, etc). Dozens of other bug fixes and improvements","package":"vim-hackernews-0.2.zip","4":"vim-hackernews-0.2.zip","src_id":"23228","5":"23228","creation_date":"1430051949","6":"1430051949"},{"0":"5108","vim_version":"7.3","1":"7.3","script_version":"0.1.1","2":"0.1.1","version_comment":"Fix \"job\" type items without a `domain` key in API","3":"Fix \"job\" type items without a `domain` key in API","package":"vim-hackernews-0.1.1.zip","4":"vim-hackernews-0.1.1.zip","src_id":"22889","5":"22889","creation_date":"1423352517","6":"1423352517"},{"0":"5108","vim_version":"7.3","1":"7.3","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"vim-hackernews-0.1.zip","4":"vim-hackernews-0.1.zip","src_id":"22888","5":"22888","creation_date":"1423349468","6":"1423349468"}]},"5107":{"script_id":"5107","0":"5107","script_name":"vim-conda","1":"vim-conda","script_type":"utility","2":"utility","summary":"Conda environment manager","3":"Conda environment manager","description":"For the most up-to-date version, please see:\r\n\r\nhttps:\/\/github.com\/cjrh\/vim-conda","4":"For the most up-to-date version, please see:\r\n\r\nhttps:\/\/github.com\/cjrh\/vim-conda","install_details":"Best to use Vundle as indicated on the github README.","5":"Best to use Vundle as indicated on the github README.","first_name":"Caleb","6":"Caleb","last_name":"Hattingh","7":"Hattingh","releases":[{"0":"5107","vim_version":"7.4","1":"7.4","script_version":"0.0.0","2":"0.0.0","version_comment":"Initial upload","3":"Initial upload","package":"vim-conda.vim","4":"vim-conda.vim","src_id":"22880","5":"22880","creation_date":"1423191805","6":"1423191805"}]},"5106":{"script_id":"5106","0":"5106","script_name":"Indentwise","1":"Indentwise","script_type":"utility","2":"utility","summary":"Indent-level based motion","3":"Indent-level based motion","description":"# Indentwise\r\n\r\n## Description\r\n\r\n`IndentWise` is a Vim plugin that provides for motions based on indent depths\r\nor levels in normal, visual, and operator-pending modes.\r\n\r\n### Movements by Relative Indent-Depth\r\n\r\nThe following key-mappings provide motions to go to lines of lesser, equal, or\r\ngreater indent than the line that the cursor is currently on:\r\n\r\n- `[-`  : Move to *previous* line of *lesser* indent than the current line.\r\n- `[+`  : Move to *previous* line of *greater* indent than the current line.\r\n- `[=`  : Move to *previous* line of *same* indent as the current line that\r\n          is separated from the current line by lines of different indents.\r\n- `]-`  : Move to *next* line of *lesser* indent than the current line.\r\n- `]+`  : Move to *next* line of *greater* indent than the current line.\r\n- `]=`  : Move to *next* line of *same* indent as the current line that\r\n          is separated from the current line by lines of different indents.\r\n\r\nThe above all take a `{count}`, so that, e.g., ``4[-`` will move to the\r\nprevious line that is 4 indent-depths less than the current one. An\r\n\"indent-depth\" is simply the indentation of the line, and thus any line with a\r\nsmaller amount of indentation relative to current line is considered at a\r\nlesser indent depth, and, conversely, any line with a greater indentation than\r\nthe current line is considered to be at a greater indent-depth.\r\n\r\n### Movements by Absolute Indent-Levels\r\n\r\nIn addition, you can navigate directly to a line of a particular indent-*level*\r\nusing:\r\n\r\n- `{count}[_`  : Move to *previous* line with indent-level of `{count}`.\r\n- `{count}]_`  : Move to *next* line with indent-level of `{count}`.\r\n\r\nAn \"indent-*level*\" of a line is the number of ``shiftwidth`` units that the\r\nline is indented (as opposed to the \"indent-*depth*\", which is just the\r\nindentation amount of a line).\r\n\r\n### Customization\r\n\r\nIf you are unhappy with the default key-mappings you can provide your own by\r\ndefining custom mappings in your _`.vimrc`_. For example to replicate the\r\ndefault mappings, you would define the following:\r\n\r\n    map [- (IndentWisePreviousLesserIndent)\r\n    map [= (IndentWisePreviousEqualIndent)\r\n    map [+ (IndentWisePreviousGreaterIndent)\r\n    map ]- (IndentWiseNextLesserIndent)\r\n    map ]= (IndentWiseNextEqualIndent)\r\n    map ]+ (IndentWiseNextGreaterIndent)\r\n    map [_ (IndentWisePreviousAbsoluteIndent)\r\n    map ]_ (IndentWiseNextAbsoluteIndent)\r\n\r\n## Installation\r\n\r\n### [pathogen.vim](https:\/\/github.com\/tpope\/vim-pathogen)\r\n\r\n    $ cd ~\/.vim\/bundle\r\n    $ git clone git:\/\/github.com\/jeetsukumaran\/vim-indentwise.git\r\n\r\n\r\n### [Vundle](https:\/\/github.com\/gmarik\/vundle.git)\r\n\r\n    :BundleInstall jeetsukumaran\/vim-indentwise\r\n\r\nAdd the line below into your _.vimrc_.\r\n\r\n    Bundle 'jeetsukumaran\/vim-indentwise'\r\n\r\n### Manually\r\n\r\nCopy the _`plugin\/indentwise.vim`_ file to your _`.vim\/plugin`_ directory and the\r\n_`doc\/indentwise.txt`_ file to your _`.vim\/doc`_ directory.\r\n\r\n## Acknowledgements\r\n\r\nIndentWise is based on the following:\r\n\r\n-   [\"Move to next\/previous line with the same indentation\"](http:\/\/vim.wikia.com\/wiki\/Move_to_next\/previous_line_with_same_indentation)","4":"# Indentwise\r\n\r\n## Description\r\n\r\n`IndentWise` is a Vim plugin that provides for motions based on indent depths\r\nor levels in normal, visual, and operator-pending modes.\r\n\r\n### Movements by Relative Indent-Depth\r\n\r\nThe following key-mappings provide motions to go to lines of lesser, equal, or\r\ngreater indent than the line that the cursor is currently on:\r\n\r\n- `[-`  : Move to *previous* line of *lesser* indent than the current line.\r\n- `[+`  : Move to *previous* line of *greater* indent than the current line.\r\n- `[=`  : Move to *previous* line of *same* indent as the current line that\r\n          is separated from the current line by lines of different indents.\r\n- `]-`  : Move to *next* line of *lesser* indent than the current line.\r\n- `]+`  : Move to *next* line of *greater* indent than the current line.\r\n- `]=`  : Move to *next* line of *same* indent as the current line that\r\n          is separated from the current line by lines of different indents.\r\n\r\nThe above all take a `{count}`, so that, e.g., ``4[-`` will move to the\r\nprevious line that is 4 indent-depths less than the current one. An\r\n\"indent-depth\" is simply the indentation of the line, and thus any line with a\r\nsmaller amount of indentation relative to current line is considered at a\r\nlesser indent depth, and, conversely, any line with a greater indentation than\r\nthe current line is considered to be at a greater indent-depth.\r\n\r\n### Movements by Absolute Indent-Levels\r\n\r\nIn addition, you can navigate directly to a line of a particular indent-*level*\r\nusing:\r\n\r\n- `{count}[_`  : Move to *previous* line with indent-level of `{count}`.\r\n- `{count}]_`  : Move to *next* line with indent-level of `{count}`.\r\n\r\nAn \"indent-*level*\" of a line is the number of ``shiftwidth`` units that the\r\nline is indented (as opposed to the \"indent-*depth*\", which is just the\r\nindentation amount of a line).\r\n\r\n### Customization\r\n\r\nIf you are unhappy with the default key-mappings you can provide your own by\r\ndefining custom mappings in your _`.vimrc`_. For example to replicate the\r\ndefault mappings, you would define the following:\r\n\r\n    map [- (IndentWisePreviousLesserIndent)\r\n    map [= (IndentWisePreviousEqualIndent)\r\n    map [+ (IndentWisePreviousGreaterIndent)\r\n    map ]- (IndentWiseNextLesserIndent)\r\n    map ]= (IndentWiseNextEqualIndent)\r\n    map ]+ (IndentWiseNextGreaterIndent)\r\n    map [_ (IndentWisePreviousAbsoluteIndent)\r\n    map ]_ (IndentWiseNextAbsoluteIndent)\r\n\r\n## Installation\r\n\r\n### [pathogen.vim](https:\/\/github.com\/tpope\/vim-pathogen)\r\n\r\n    $ cd ~\/.vim\/bundle\r\n    $ git clone git:\/\/github.com\/jeetsukumaran\/vim-indentwise.git\r\n\r\n\r\n### [Vundle](https:\/\/github.com\/gmarik\/vundle.git)\r\n\r\n    :BundleInstall jeetsukumaran\/vim-indentwise\r\n\r\nAdd the line below into your _.vimrc_.\r\n\r\n    Bundle 'jeetsukumaran\/vim-indentwise'\r\n\r\n### Manually\r\n\r\nCopy the _`plugin\/indentwise.vim`_ file to your _`.vim\/plugin`_ directory and the\r\n_`doc\/indentwise.txt`_ file to your _`.vim\/doc`_ directory.\r\n\r\n## Acknowledgements\r\n\r\nIndentWise is based on the following:\r\n\r\n-   [\"Move to next\/previous line with the same indentation\"](http:\/\/vim.wikia.com\/wiki\/Move_to_next\/previous_line_with_same_indentation)","install_details":"","5":"","first_name":"Jeet","6":"Jeet","last_name":"Sukumaran","7":"Sukumaran","releases":[{"0":"5106","vim_version":"7.0","1":"7.0","script_version":"1.0.0","2":"1.0.0","version_comment":"Initial upload","3":"Initial upload","package":"vim-indentwise-v1.0.0.tar.gz","4":"vim-indentwise-v1.0.0.tar.gz","src_id":"22879","5":"22879","creation_date":"1423161971","6":"1423161971"}]},"5105":{"script_id":"5105","0":"5105","script_name":"h2cppx","1":"h2cppx","script_type":"utility","2":"utility","summary":"parse the c++ header file and generate c++ implement code ","3":"parse the c++ header file and generate c++ implement code ","description":"h2cppx(vim-port): parse the c++ header file and generate c++ implement code \r\n===========================================================================\r\n**Purpose:** Parse the c++ header file and generate c++ implement code for vim plugin\r\n\r\n**Required:** python 2.x\r\n\r\n**Author:** xiaok\r\n\r\n**External module required:** cheetah yaml(python package)\r\n\r\n**Third-party(the plugin already include):** pyvisitor CppHeaderParser(modification) \r\n\r\n[Github-Link](https:\/\/github.com\/xuqix\/h2cppx.git)\r\n\r\nInstallation\r\n------------\r\nBefore start, make sure you have installed the python package \"yaml\",\r\nThen run below command:\r\n\r\n    cd ~\/.vim\/plugin\r\n    git clone 'https:\/\/github.com\/xuqix\/h2cppx.git\r\n    cd  h2cppx\r\n    git checkout vim-port\r\n\r\nor you can use bundle to install it:\r\n\r\nadd `Bundle 'xuqix\/h2cppx'` to ~\/.vimrc and install it,then:\r\n\r\n    cd ~\/.vim\/bundle\/h2cppx\r\n    git checkout vim-port\r\n\r\nNow you can start using it.\r\n\r\nAfter the installation is complete, \r\nYou can map the key in .vimrc to quickly use the command.\r\n\r\n    e.g:\r\n    nmap   :H2cppx\r\n    nmap   :H2cppxLine\r\n    nmap p :CpH2cppx\r\n    nmap p :CpH2cppxLine\r\n    nmap   :H2cppxAuto\r\n\r\nConfig\r\n------\r\nIf the plugin can't find the python path in your computer,\r\nyou need set \"g:python_path\" in the .vimrc file like this:\r\n\r\n    let g:h2cppx_python_path = '\/usr\/bin\/python'\r\n\r\nand you can specify the cppfile name extension like this:\r\n(default value is 'cpp')\r\n\r\n    let g:h2cppx_postfix = 'cxx'\r\n\r\nfive code-generate template file are provided by default,you \r\ncan config it in '.vimrc' like this(template0-4,default is template1):\r\n\r\n    let g:h2cppx_template = 'template4' \r\n\r\nif needed,you can refer to the default template and write your own template\r\nfiles,and use absolute path config it :\r\n\r\n    let g:h2cppx_template = '\/home\/xxx\/...\/xxx'\r\n\r\nFinally,you can add a configuration file `.h2cppx_conf` in your project \r\ndirectory to help plugin search for cppfile,otherwise the plugin will find\r\ncppfile in your header file directory.\r\nThe configuration file might look like:\r\n    \r\n    \/home\/test\/temp\/src\r\n    src1\r\n    src2\r\n\r\nsee the project_sample directory.\r\n\r\nUsage\r\n-----\r\nThe plugin function description:\r\n\r\n* :H2cppx  \r\n  Parse c++ header file and generate cpp file \r\n\r\n* :CpH2cppx  \r\n  Like :H2cppx,but generat code in your clipboard, no file writed,you can use \"p\" to get it.\r\n\r\n* :H2cppxLine  \r\n  Generate cpp code in the cursor line,and append to the end of the cpp file\r\n\r\n* :CpH2cppxLine  \r\n  Like :H2cppxLine,but generat code in your clipboard, no file writed,you can use \"p\" to get it.\r\n\r\n* :H2cppxAuto  (Recommendation)   \r\n  Auto Contrast header and implementation files, find\r\n  function declarations in the header file and append\r\n  the newly added to the implementation file, if the \r\n  file does not exist to achieve a new file is created!\r\n\r\nExample:\r\n-------\r\n\r\n    vim test.h\r\n    :H2cppx  \r\n    Now you can find new file \"test.cpp\" in your directory\r\n\r\n    vim test.h\r\n    :H2cppxLine\r\n    Now you can find defined in your file \"test.cpp\" from current line of cursor \r\n\r\n    vim test.h\r\n    :CpH2cppx  \r\n    Like :H2cppx, but defined in your clipboard, no file writed, just use \"p\" to get it.\r\n\r\n    vim test.h\r\n    :CpH2cppxLine  \r\n    Like :H2cppxLine, but defined in your clipboard, no file is writed.\r\n\r\n    vim test.h\r\n    :H2cppxAuto \r\n    Auto Contrast header and implementation files, find function \r\n    declarations in the header file and append the newly added to \r\n    the implementation file, if the file does not exist to achieve \r\n    a new file is created!\r\n","4":"h2cppx(vim-port): parse the c++ header file and generate c++ implement code \r\n===========================================================================\r\n**Purpose:** Parse the c++ header file and generate c++ implement code for vim plugin\r\n\r\n**Required:** python 2.x\r\n\r\n**Author:** xiaok\r\n\r\n**External module required:** cheetah yaml(python package)\r\n\r\n**Third-party(the plugin already include):** pyvisitor CppHeaderParser(modification) \r\n\r\n[Github-Link](https:\/\/github.com\/xuqix\/h2cppx.git)\r\n\r\nInstallation\r\n------------\r\nBefore start, make sure you have installed the python package \"yaml\",\r\nThen run below command:\r\n\r\n    cd ~\/.vim\/plugin\r\n    git clone 'https:\/\/github.com\/xuqix\/h2cppx.git\r\n    cd  h2cppx\r\n    git checkout vim-port\r\n\r\nor you can use bundle to install it:\r\n\r\nadd `Bundle 'xuqix\/h2cppx'` to ~\/.vimrc and install it,then:\r\n\r\n    cd ~\/.vim\/bundle\/h2cppx\r\n    git checkout vim-port\r\n\r\nNow you can start using it.\r\n\r\nAfter the installation is complete, \r\nYou can map the key in .vimrc to quickly use the command.\r\n\r\n    e.g:\r\n    nmap   :H2cppx\r\n    nmap   :H2cppxLine\r\n    nmap p :CpH2cppx\r\n    nmap p :CpH2cppxLine\r\n    nmap   :H2cppxAuto\r\n\r\nConfig\r\n------\r\nIf the plugin can't find the python path in your computer,\r\nyou need set \"g:python_path\" in the .vimrc file like this:\r\n\r\n    let g:h2cppx_python_path = '\/usr\/bin\/python'\r\n\r\nand you can specify the cppfile name extension like this:\r\n(default value is 'cpp')\r\n\r\n    let g:h2cppx_postfix = 'cxx'\r\n\r\nfive code-generate template file are provided by default,you \r\ncan config it in '.vimrc' like this(template0-4,default is template1):\r\n\r\n    let g:h2cppx_template = 'template4' \r\n\r\nif needed,you can refer to the default template and write your own template\r\nfiles,and use absolute path config it :\r\n\r\n    let g:h2cppx_template = '\/home\/xxx\/...\/xxx'\r\n\r\nFinally,you can add a configuration file `.h2cppx_conf` in your project \r\ndirectory to help plugin search for cppfile,otherwise the plugin will find\r\ncppfile in your header file directory.\r\nThe configuration file might look like:\r\n    \r\n    \/home\/test\/temp\/src\r\n    src1\r\n    src2\r\n\r\nsee the project_sample directory.\r\n\r\nUsage\r\n-----\r\nThe plugin function description:\r\n\r\n* :H2cppx  \r\n  Parse c++ header file and generate cpp file \r\n\r\n* :CpH2cppx  \r\n  Like :H2cppx,but generat code in your clipboard, no file writed,you can use \"p\" to get it.\r\n\r\n* :H2cppxLine  \r\n  Generate cpp code in the cursor line,and append to the end of the cpp file\r\n\r\n* :CpH2cppxLine  \r\n  Like :H2cppxLine,but generat code in your clipboard, no file writed,you can use \"p\" to get it.\r\n\r\n* :H2cppxAuto  (Recommendation)   \r\n  Auto Contrast header and implementation files, find\r\n  function declarations in the header file and append\r\n  the newly added to the implementation file, if the \r\n  file does not exist to achieve a new file is created!\r\n\r\nExample:\r\n-------\r\n\r\n    vim test.h\r\n    :H2cppx  \r\n    Now you can find new file \"test.cpp\" in your directory\r\n\r\n    vim test.h\r\n    :H2cppxLine\r\n    Now you can find defined in your file \"test.cpp\" from current line of cursor \r\n\r\n    vim test.h\r\n    :CpH2cppx  \r\n    Like :H2cppx, but defined in your clipboard, no file writed, just use \"p\" to get it.\r\n\r\n    vim test.h\r\n    :CpH2cppxLine  \r\n    Like :H2cppxLine, but defined in your clipboard, no file is writed.\r\n\r\n    vim test.h\r\n    :H2cppxAuto \r\n    Auto Contrast header and implementation files, find function \r\n    declarations in the header file and append the newly added to \r\n    the implementation file, if the file does not exist to achieve \r\n    a new file is created!\r\n","install_details":"see readme.md","5":"see readme.md","first_name":"xiaok","6":"xiaok","last_name":"","7":"","releases":[{"0":"5105","vim_version":"7.3","1":"7.3","script_version":"0.11","2":"0.11","version_comment":"fix : modify the directory structure to work for bundle","3":"fix : modify the directory structure to work for bundle","package":"h2cppx.tar.gz","4":"h2cppx.tar.gz","src_id":"22881","5":"22881","creation_date":"1423200929","6":"1423200929"},{"0":"5105","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"h2cppx.tar.gz","4":"h2cppx.tar.gz","src_id":"22875","5":"22875","creation_date":"1423125507","6":"1423125507"}]},"5104":{"script_id":"5104","0":"5104","script_name":"FastFold","1":"FastFold","script_type":"utility","2":"utility","summary":"Speed up Vim by updating folds only when called-for","3":"Speed up Vim by updating folds only when called-for","description":"Automatic folds (that is, folds generated by a fold method other\r\nthan `manual`), bog down VIM noticeably in insert mode and are often\r\nrecomputed too early (for example, when inserting an opening fold marker\r\nwhose closing counterpart is yet missing.)\r\n\r\nSee http:\/\/vim.wikia.com\/wiki\/Keep_folds_closed_while_inserting_text\r\nfor a discussion.\r\n\r\nWith this plug-in, the folds in the currently edited buffer are updated by an\r\nautomatic fold method only\r\n\r\n- when saving the buffer\r\n- when closing or opening folds (zo, za, zc, etc...)\r\n- when moving or operating fold-wise (zj,zk,[z,]z)\r\n- when typing `zuz` in normal mode\r\n\r\nand are kept as is otherwise (by keeping the fold method set to `manual`).\r\n\r\nEach of the above triggers can be changed by in your `.vimrc` by changing\r\nthe values\r\n\r\n  nmap zuz (FastFoldUpdate)\r\n  let g:fastfold_savehook = 1\r\n  let g:fastfold_fold_command_suffixes =  ['x','X','a','A','o','O','c','C']\r\n  let g:fastfold_fold_movement_commands = [']z', '[z', 'zj', 'zk']\r\n\r\n\r\nFastFold is developed at \r\n\r\nhttps:\/\/github.com\/Konfekt\/FastFold\r\n\r\nwhere issues can be filed.\r\n","4":"Automatic folds (that is, folds generated by a fold method other\r\nthan `manual`), bog down VIM noticeably in insert mode and are often\r\nrecomputed too early (for example, when inserting an opening fold marker\r\nwhose closing counterpart is yet missing.)\r\n\r\nSee http:\/\/vim.wikia.com\/wiki\/Keep_folds_closed_while_inserting_text\r\nfor a discussion.\r\n\r\nWith this plug-in, the folds in the currently edited buffer are updated by an\r\nautomatic fold method only\r\n\r\n- when saving the buffer\r\n- when closing or opening folds (zo, za, zc, etc...)\r\n- when moving or operating fold-wise (zj,zk,[z,]z)\r\n- when typing `zuz` in normal mode\r\n\r\nand are kept as is otherwise (by keeping the fold method set to `manual`).\r\n\r\nEach of the above triggers can be changed by in your `.vimrc` by changing\r\nthe values\r\n\r\n  nmap zuz (FastFoldUpdate)\r\n  let g:fastfold_savehook = 1\r\n  let g:fastfold_fold_command_suffixes =  ['x','X','a','A','o','O','c','C']\r\n  let g:fastfold_fold_movement_commands = [']z', '[z', 'zj', 'zk']\r\n\r\n\r\nFastFold is developed at \r\n\r\nhttps:\/\/github.com\/Konfekt\/FastFold\r\n\r\nwhere issues can be filed.\r\n","install_details":"Unzip FastFold.zip into  ~\/.vim on Linux or %USERPROFILE%\\vimfiles on Windows.","5":"Unzip FastFold.zip into  ~\/.vim on Linux or %USERPROFILE%\\vimfiles on Windows.","first_name":"Enno","6":"Enno","last_name":"Nagel","7":"Nagel","releases":[{"0":"5104","vim_version":"7.0","1":"7.0","script_version":"5.3","2":"5.3","version_comment":"make work less and document better","3":"make work less and document better","package":"FastFold.zip","4":"FastFold.zip","src_id":"27520","5":"27520","creation_date":"1614900685","6":"1614900685"},{"0":"5104","vim_version":"6.0","1":"6.0","script_version":"5.2","2":"5.2","version_comment":"permit enabling FastFold for faster foldmethods (that is, different from expression or syntax folding)","3":"permit enabling FastFold for faster foldmethods (that is, different from expression or syntax folding)","package":"FastFold.zip","4":"FastFold.zip","src_id":"25972","5":"25972","creation_date":"1525923427","6":"1525923427"},{"0":"5104","vim_version":"7.0","1":"7.0","script_version":"5.1","2":"5.1","version_comment":"fix trifles","3":"fix trifles","package":"FastFold.zip","4":"FastFold.zip","src_id":"24322","5":"24322","creation_date":"1465820919","6":"1465820919"},{"0":"5104","vim_version":"7.0","1":"7.0","script_version":"5.0","2":"5.0","version_comment":"restore folds after diff","3":"restore folds after diff","package":"FastFold.zip","4":"FastFold.zip","src_id":"24200","5":"24200","creation_date":"1461579547","6":"1461579547"},{"0":"5104","vim_version":"7.0","1":"7.0","script_version":"4.1","2":"4.1","version_comment":"add help tags, bug fixes and small improvements","3":"add help tags, bug fixes and small improvements","package":"FastFold.zip","4":"FastFold.zip","src_id":"24160","5":"24160","creation_date":"1459960682","6":"1459960682"},{"0":"5104","vim_version":"7.0","1":"7.0","script_version":"3.0","2":"3.0","version_comment":"smaller, more robust and faster ","3":"smaller, more robust and faster ","package":"FastFold.zip","4":"FastFold.zip","src_id":"23377","5":"23377","creation_date":"1433960259","6":"1433960259"},{"0":"5104","vim_version":"7.0","1":"7.0","script_version":"2.0","2":"2.0","version_comment":"Integrate movement commands. Clean up configuration options.","3":"Integrate movement commands. Clean up configuration options.","package":"FastFold.zip","4":"FastFold.zip","src_id":"23150","5":"23150","creation_date":"1428501406","6":"1428501406"},{"0":"5104","vim_version":"7.0","1":"7.0","script_version":"1.1","2":"1.1","version_comment":"Leaner code. Give priority to buffer instead of window fold settings.","3":"Leaner code. Give priority to buffer instead of window fold settings.","package":"FastFold.zip","4":"FastFold.zip","src_id":"22987","5":"22987","creation_date":"1425820389","6":"1425820389"},{"0":"5104","vim_version":"5.7","1":"5.7","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"FastFold.zip","4":"FastFold.zip","src_id":"22869","5":"22869","creation_date":"1423085742","6":"1423085742"}]},"5103":{"script_id":"5103","0":"5103","script_name":"haystack.vim","1":"haystack.vim","script_type":"utility","2":"utility","summary":"Fuzzy matching algorithm","3":"Fuzzy matching algorithm","description":"Haystack provides a fuzzy matching algorithm for use by other Vim plugins.  It's based on flx for Emacs but adapted to my own real world experience.  The algorithm gives priority to runs of consecutive letters and letters after punctuation marks.\r\n\r\nSo far, out of the box support is included with projectionist.vim (vimscript #4989), including dependent plugins like rails.vim (vimscript #1567).","4":"Haystack provides a fuzzy matching algorithm for use by other Vim plugins.  It's based on flx for Emacs but adapted to my own real world experience.  The algorithm gives priority to runs of consecutive letters and letters after punctuation marks.\r\n\r\nSo far, out of the box support is included with projectionist.vim (vimscript #4989), including dependent plugins like rails.vim (vimscript #1567).","install_details":"Extract in ~\/.vim (~\\vimfiles on Windows).","5":"Extract in ~\/.vim (~\\vimfiles on Windows).","first_name":"Tim","6":"Tim","last_name":"Pope","7":"Pope","releases":[{"0":"5103","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"haystack.zip","4":"haystack.zip","src_id":"22868","5":"22868","creation_date":"1423078579","6":"1423078579"}]},"5102":{"script_id":"5102","0":"5102","script_name":"vital-snoop.vim","1":"vital-snoop.vim","script_type":"utility","2":"utility","summary":"Snoop script-local functions","3":"Snoop script-local functions","description":"\r\nSEE: https:\/\/github.com\/haya14busa\/vital-snoop.vim","4":"\r\nSEE: https:\/\/github.com\/haya14busa\/vital-snoop.vim","install_details":"","5":"","first_name":"haya14busa","6":"haya14busa","last_name":" ","7":" ","releases":[{"0":"5102","vim_version":"7.3","1":"7.3","script_version":"0.9.1","2":"0.9.1","version_comment":"Initial upload","3":"Initial upload","package":"vital-snoop.vim-0.9.1.zip","4":"vital-snoop.vim-0.9.1.zip","src_id":"22858","5":"22858","creation_date":"1422898934","6":"1422898934"}]},"5101":{"script_id":"5101","0":"5101","script_name":"enabler","1":"enabler","script_type":"utility","2":"utility","summary":"Load plugins\/bundles as needed","3":"Load plugins\/bundles as needed","description":"The Enabler plugin loads plugins\/bundles (\u00c3\u00a0 la pathogen) on demand as requested \r\nby the user. It's main goal is to manage your 'runtimepath' as needed. It thus \r\nallows users to have tons of vim plugins\/bundles at their finger tips without \r\nslowing down startup time.\r\n\r\nPlugins\/bundles are enabled:\r\n\r\n    - on explicit demand via |:Enable|\r\n    - or implicitly when\r\n        - setting a filetype (see |:Enablefiletype|)\r\n        - editing a file matching a |regexp| (see |:Enablefilepattern|)\r\n        - calling an unknown function (see |:Enableautoload|)\r\n        - invoking a map (see |:Enablemap|)\r\n        - calling a command (see |:Enablecommand|)\r\n\r\nEnabler can also scan available plugins\/bundles and generate stub commands and \r\nmaps for you (see |:Enablegenerate|). These autoenabler definitions can be \r\nloaded via |:Autoenabler|.\r\n\r\nThe doc files of installed plugins\/bundles can be made available via \r\n|:Enablehelptags|.\r\n\r\nMost vim plugin managers try to do at least two things: manage your \r\n'runtimepath' and manage (install, update, remove) plugins. The Enabler plugin \r\nfocuses on the first task, i.e., managing the 'runtimepath' variable and \r\nenabling plugins as needed. The Enabler plugin doesn't provide a way to \r\ndownload \/ install \/ update \/ remove \/ build these plugins. Users should use \r\none of the other vim plugin managers available, shell scripts or whatever.\r\n\r\nEnabler is the successor of the tplugin plugin.\r\n","4":"The Enabler plugin loads plugins\/bundles (\u00c3\u00a0 la pathogen) on demand as requested \r\nby the user. It's main goal is to manage your 'runtimepath' as needed. It thus \r\nallows users to have tons of vim plugins\/bundles at their finger tips without \r\nslowing down startup time.\r\n\r\nPlugins\/bundles are enabled:\r\n\r\n    - on explicit demand via |:Enable|\r\n    - or implicitly when\r\n        - setting a filetype (see |:Enablefiletype|)\r\n        - editing a file matching a |regexp| (see |:Enablefilepattern|)\r\n        - calling an unknown function (see |:Enableautoload|)\r\n        - invoking a map (see |:Enablemap|)\r\n        - calling a command (see |:Enablecommand|)\r\n\r\nEnabler can also scan available plugins\/bundles and generate stub commands and \r\nmaps for you (see |:Enablegenerate|). These autoenabler definitions can be \r\nloaded via |:Autoenabler|.\r\n\r\nThe doc files of installed plugins\/bundles can be made available via \r\n|:Enablehelptags|.\r\n\r\nMost vim plugin managers try to do at least two things: manage your \r\n'runtimepath' and manage (install, update, remove) plugins. The Enabler plugin \r\nfocuses on the first task, i.e., managing the 'runtimepath' variable and \r\nenabling plugins as needed. The Enabler plugin doesn't provide a way to \r\ndownload \/ install \/ update \/ remove \/ build these plugins. Users should use \r\none of the other vim plugin managers available, shell scripts or whatever.\r\n\r\nEnabler is the successor of the tplugin plugin.\r\n","install_details":"If you want to install the vba from vim.org, open the vba file in VIM (see \r\n`:help vimball` for details) and type: >\r\n\r\n    :so %\r\n\r\nIf you want to install from git, clone http:\/\/github.com\/tomtom\/enabler_vim\/\r\nto ~\/.vim\/bundle\/enabler_vim: >\r\n\r\n    cd ~\/.vim\/bundle\r\n    git clone https:\/\/github.com\/tomtom\/enabler_vim.git\r\n\r\nIn order to make full use of the enabler plugin, you could insert something \r\nlike the the following lines at the top of the |vimrc| file:\r\n\r\n    \"\"\" If enabler is installed as bundle, add the directory of the enabler \r\n    \"\"\" bundle to 'rtp' (the value may differ from your setup):\r\n    set rtp+=$HOME\/.vim\/bundle\/enabler_vim\r\n    \"\"\" If enabler is installed in ~\/.vim replace the above line with the \r\n    \"\"\" following:\r\n    \" runtime! plugin\/enabler.vim\r\n\r\n    \"\"\" Optionally customize enabler's behaviour:\r\n    \" let g:enabler... = ...\r\n\r\n    \"\"\" Load the plugin:\r\n    runtime! plugin\/enabler.vim\r\n\r\n    \"\"\" Enable a standard set of plugins you always use:\r\n    Enable ...\r\n\r\n    \"\"\" Optionally load |autoenabler.vim| (must run :Enablegenerate first):\r\n    Autoenabler\r\n","5":"If you want to install the vba from vim.org, open the vba file in VIM (see \r\n`:help vimball` for details) and type: >\r\n\r\n    :so %\r\n\r\nIf you want to install from git, clone http:\/\/github.com\/tomtom\/enabler_vim\/\r\nto ~\/.vim\/bundle\/enabler_vim: >\r\n\r\n    cd ~\/.vim\/bundle\r\n    git clone https:\/\/github.com\/tomtom\/enabler_vim.git\r\n\r\nIn order to make full use of the enabler plugin, you could insert something \r\nlike the the following lines at the top of the |vimrc| file:\r\n\r\n    \"\"\" If enabler is installed as bundle, add the directory of the enabler \r\n    \"\"\" bundle to 'rtp' (the value may differ from your setup):\r\n    set rtp+=$HOME\/.vim\/bundle\/enabler_vim\r\n    \"\"\" If enabler is installed in ~\/.vim replace the above line with the \r\n    \"\"\" following:\r\n    \" runtime! plugin\/enabler.vim\r\n\r\n    \"\"\" Optionally customize enabler's behaviour:\r\n    \" let g:enabler... = ...\r\n\r\n    \"\"\" Load the plugin:\r\n    runtime! plugin\/enabler.vim\r\n\r\n    \"\"\" Enable a standard set of plugins you always use:\r\n    Enable ...\r\n\r\n    \"\"\" Optionally load |autoenabler.vim| (must run :Enablegenerate first):\r\n    Autoenabler\r\n","first_name":"Tom","6":"Tom","last_name":"Link","7":"Link","releases":[{"0":"5101","vim_version":"7.0","1":"7.0","script_version":"1.00","2":"1.00","version_comment":"- enabler#helptags#Generate(): Show message\n- enabler#Command(): Add extra check for \"AddUndefine()\"\n- Use case sensitive matches for filenames\n- enabler#AutoFiletype(): Call enabler#Plugin() with load_now = 1\n- NEW :Enablecommands, enabler#Commands()\n- NEW :Enableautocmd EVENT PATTERN PLUGIN[#GROUP]...\n- Support for ftbundles\/ftplugins\nMD5 checksum: a51dfad95cc0d93ce59868deef5cf9fd","3":"- enabler#helptags#Generate(): Show message\n- enabler#Command(): Add extra check for \"AddUndefine()\"\n- Use case sensitive matches for filenames\n- enabler#AutoFiletype(): Call enabler#Plugin() with load_now = 1\n- NEW :Enablecommands, enabler#Commands()\n- NEW :Enableautocmd EVENT PATTERN PLUGIN[#GROUP]...\n- Support for ftbundles\/ftplugins\nMD5 checksum: a51dfad95cc0d93ce59868deef5cf9fd","package":"enabler.vba","4":"enabler.vba","src_id":"23635","5":"23635","creation_date":"1443787336","6":"1443787336"},{"0":"5101","vim_version":"7.4","1":"7.4","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"enabler.vba","4":"enabler.vba","src_id":"22856","5":"22856","creation_date":"1422816652","6":"1422816652"}]},"5100":{"script_id":"5100","0":"5100","script_name":"vim-cursorword","1":"vim-cursorword","script_type":"utility","2":"utility","summary":"Underlines the word under the cursor","3":"Underlines the word under the cursor","description":"NOTE: I don't upload code to vim.org anymore. Please clone from https:\/\/github.com\/itchyny\/vim-cursorword.\r\n\r\n\r\nThis *cursorword* plugin underlines the word under the cursor. That's it.\r\n\r\nWhile we are coding, we always pay attention to the variable under the cursor.\r\nWhere did we define the variable? In which statement do we use the variable?\r\nSearching the variable using |star| or |#| is a simple solution to highlight all\r\nthe places the variable is used. However, it costs too much time to highlight\r\na word, move around to check the places and clear the highlight.  This plugin\r\n|cursorword| provides you the modest underlines for the variables under the\r\ncursor to let you know all the places the variable is used at a glance without\r\nstopping coding.\r\n\r\nImage: https:\/\/raw.githubusercontent.com\/wiki\/itchyny\/vim-cursorword\/image\/image.gif\r\nGitHub repository: https:\/\/github.com\/itchyny\/vim-cursorword\r\nBug Tracker: https:\/\/github.com\/itchyny\/vim-cursorword\/issues","4":"NOTE: I don't upload code to vim.org anymore. Please clone from https:\/\/github.com\/itchyny\/vim-cursorword.\r\n\r\n\r\nThis *cursorword* plugin underlines the word under the cursor. That's it.\r\n\r\nWhile we are coding, we always pay attention to the variable under the cursor.\r\nWhere did we define the variable? In which statement do we use the variable?\r\nSearching the variable using |star| or |#| is a simple solution to highlight all\r\nthe places the variable is used. However, it costs too much time to highlight\r\na word, move around to check the places and clear the highlight.  This plugin\r\n|cursorword| provides you the modest underlines for the variables under the\r\ncursor to let you know all the places the variable is used at a glance without\r\nstopping coding.\r\n\r\nImage: https:\/\/raw.githubusercontent.com\/wiki\/itchyny\/vim-cursorword\/image\/image.gif\r\nGitHub repository: https:\/\/github.com\/itchyny\/vim-cursorword\r\nBug Tracker: https:\/\/github.com\/itchyny\/vim-cursorword\/issues","install_details":"","5":"","first_name":"itchyny","6":"itchyny","last_name":"\u3000","7":"　","releases":[{"0":"5100","vim_version":"7.3","1":"7.3","script_version":"0.8","2":"0.8","version_comment":"improve word matching for insert and replace modes\r\nupdate word under the cursor matching on InsertEnter and InsertLeave events\r\nskip underlining word if the word is too long to avoid E339\r\n","3":"improve word matching for insert and replace modes\r\nupdate word under the cursor matching on InsertEnter and InsertLeave events\r\nskip underlining word if the word is too long to avoid E339\r\n","package":"cursorword.zip","4":"cursorword.zip","src_id":"25612","5":"25612","creation_date":"1508418570","6":"1508418570"},{"0":"5100","vim_version":"7.3","1":"7.3","script_version":"0.7","2":"0.7","version_comment":"fix E16 error on the old regexp engine","3":"fix E16 error on the old regexp engine","package":"cursorword.zip","4":"cursorword.zip","src_id":"25191","5":"25191","creation_date":"1494424153","6":"1494424153"},{"0":"5100","vim_version":"7.3","1":"7.3","script_version":"0.6","2":"0.6","version_comment":"- improve document\r\n- underline multi-byte alphabets like accents, umlauts and Cyrillic alphabets","3":"- improve document\r\n- underline multi-byte alphabets like accents, umlauts and Cyrillic alphabets","package":"cursorword.zip","4":"cursorword.zip","src_id":"25151","5":"25151","creation_date":"1494152998","6":"1494152998"},{"0":"5100","vim_version":"7.3","1":"7.3","script_version":"0.2","2":"0.2","version_comment":"Fix English in the document (Thank you ujihisa).\r\nCheck if Vim has started.\r\nCall cursorword#highlight on loading the autoload script.","3":"Fix English in the document (Thank you ujihisa).\r\nCheck if Vim has started.\r\nCall cursorword#highlight on loading the autoload script.","package":"vim-cursorword-0.2.zip","4":"vim-cursorword-0.2.zip","src_id":"22900","5":"22900","creation_date":"1423495231","6":"1423495231"},{"0":"5100","vim_version":"7.3","1":"7.3","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"vim-cursorword-0.1.zip","4":"vim-cursorword-0.1.zip","src_id":"22852","5":"22852","creation_date":"1422670692","6":"1422670692"}]},"5099":{"script_id":"5099","0":"5099","script_name":"vim-stay","1":"vim-stay","script_type":"utility","2":"utility","summary":"Make Vim persist editing state without fuss","3":"Make Vim persist editing state without fuss","description":"vim-stay adds automated view session creation and restoration whenever editing a buffer, across Vim sessions and window life cycles. It also alleviates Vim's tendency to lose view state when cycling through buffers (via `argdo`, `bufdo` et al.). It is smart about which buffers should be persisted and which should not, making the procedure painless and invisible.\r\n\r\nIf you have wished Vim would be smarter about keeping your editing state, vim-stay is for you.\r\n\r\nProject repository: https:\/\/github.com\/zhimsel\/vim-stay\r\n\r\nNOTE: Maintainership for vim-stay has been talken over by Zach Himsel. Links on this page have been corrected or will redirect to the new GitHub repository. Please do refer to the above mentioned repository for future developments.","4":"vim-stay adds automated view session creation and restoration whenever editing a buffer, across Vim sessions and window life cycles. It also alleviates Vim's tendency to lose view state when cycling through buffers (via `argdo`, `bufdo` et al.). It is smart about which buffers should be persisted and which should not, making the procedure painless and invisible.\r\n\r\nIf you have wished Vim would be smarter about keeping your editing state, vim-stay is for you.\r\n\r\nProject repository: https:\/\/github.com\/zhimsel\/vim-stay\r\n\r\nNOTE: Maintainership for vim-stay has been talken over by Zach Himsel. Links on this page have been corrected or will redirect to the new GitHub repository. Please do refer to the above mentioned repository for future developments.","install_details":"Download and source the most current vimball from the releases list, then run :helptags {dir} on your runtimepath\/doc directory. Or, if you use a git-based plug-in manager (like Pathogen, Vundle, NeoBundle etc.), simply add kopischke\/vim-fetch to the list of plug-ins, source that and issue your manager's install command.","5":"Download and source the most current vimball from the releases list, then run :helptags {dir} on your runtimepath\/doc directory. Or, if you use a git-based plug-in manager (like Pathogen, Vundle, NeoBundle etc.), simply add kopischke\/vim-fetch to the list of plug-ins, source that and issue your manager's install command.","first_name":"Martin","6":"Martin","last_name":"Kopischke","7":"Kopischke","releases":[{"0":"5099","vim_version":"7.0","1":"7.0","script_version":"1.3.1","2":"1.3.1","version_comment":"Bugfix to release 1.3.0","3":"Bugfix to release 1.3.0","package":"vim-stay-1.3.1.vmb","4":"vim-stay-1.3.1.vmb","src_id":"23111","5":"23111","creation_date":"1427824105","6":"1427824105"},{"0":"5099","vim_version":"7.0","1":"7.0","script_version":"1.3.0","2":"1.3.0","version_comment":"The speed-up edition. Release notes: https:\/\/github.com\/kopischke\/vim-stay\/releases\/tag\/v1.3.0","3":"The speed-up edition. Release notes: https:\/\/github.com\/kopischke\/vim-stay\/releases\/tag\/v1.3.0","package":"vim-stay-1.3.0.vmb","4":"vim-stay-1.3.0.vmb","src_id":"23110","5":"23110","creation_date":"1427822812","6":"1427822812"},{"0":"5099","vim_version":"7.0","1":"7.0","script_version":"1.2.0","2":"1.2.0","version_comment":"Release notes: https:\/\/github.com\/kopischke\/vim-stay\/releases\/tag\/v1.2.0 ","3":"Release notes: https:\/\/github.com\/kopischke\/vim-stay\/releases\/tag\/v1.2.0 ","package":"vim-stay-1.2.0.vmb","4":"vim-stay-1.2.0.vmb","src_id":"22978","5":"22978","creation_date":"1425468328","6":"1425468328"},{"0":"5099","vim_version":"7.0","1":"7.0","script_version":"1.1.1","2":"1.1.1","version_comment":"Release notes: https:\/\/github.com\/kopischke\/vim-stay\/releases\/tag\/v1.1.1","3":"Release notes: https:\/\/github.com\/kopischke\/vim-stay\/releases\/tag\/v1.1.1","package":"vim-stay-1.1.1.vmb","4":"vim-stay-1.1.1.vmb","src_id":"22883","5":"22883","creation_date":"1423229895","6":"1423229895"},{"0":"5099","vim_version":"7.0","1":"7.0","script_version":"1.1.0","2":"1.1.0","version_comment":"Release notes: https:\/\/github.com\/kopischke\/vim-stay\/releases\/tag\/v1.1.0","3":"Release notes: https:\/\/github.com\/kopischke\/vim-stay\/releases\/tag\/v1.1.0","package":"vim-stay-1.1.0.vmb","4":"vim-stay-1.1.0.vmb","src_id":"22876","5":"22876","creation_date":"1423130535","6":"1423130535"},{"0":"5099","vim_version":"7.0","1":"7.0","script_version":"1.0.1","2":"1.0.1","version_comment":"Release notes: https:\/\/github.com\/kopischke\/vim-stay\/releases\/tag\/v1.0.1","3":"Release notes: https:\/\/github.com\/kopischke\/vim-stay\/releases\/tag\/v1.0.1","package":"vim-stay-1.0.1.vmb","4":"vim-stay-1.0.1.vmb","src_id":"22866","5":"22866","creation_date":"1423068051","6":"1423068051"},{"0":"5099","vim_version":"7.0","1":"7.0","script_version":"1.0.0","2":"1.0.0","version_comment":"Initial upload","3":"Initial upload","package":"vim-stay-1.0.0.vmb","4":"vim-stay-1.0.0.vmb","src_id":"22851","5":"22851","creation_date":"1422549884","6":"1422549884"}]},"5098":{"script_id":"5098","0":"5098","script_name":"cscope_dynamic","1":"cscope_dynamic","script_type":"utility","2":"utility","summary":"quick automatic dynamic cscope updates","3":"quick automatic dynamic cscope updates","description":"A Vim plugin that enables very fast automatic cscope database updates for C\/C++\r\ncodebases. It accomplishes this by using two cscope databases; a large one, and\r\na small one. When a file is written it is moved to the small database, which\r\ncan update in a matter of seconds - often sub-second. The file is then removed\r\nfrom the large database to avoid duplicate cscope query results. Subsequent\r\nwrites to the same file only trigger a small database update. The initial move\r\nfrom the large to small database is a one time cost. This works well because\r\nyou're often only modifying a subset of files at a time.\r\n\r\nSee bitbucket[1] or github[2] for more information and current development.\r\n\r\n[1] https:\/\/bitbucket.org\/ericgarver\/cscope_dynamic\r\n[2] https:\/\/github.com\/erig0\/cscope_dynamic","4":"A Vim plugin that enables very fast automatic cscope database updates for C\/C++\r\ncodebases. It accomplishes this by using two cscope databases; a large one, and\r\na small one. When a file is written it is moved to the small database, which\r\ncan update in a matter of seconds - often sub-second. The file is then removed\r\nfrom the large database to avoid duplicate cscope query results. Subsequent\r\nwrites to the same file only trigger a small database update. The initial move\r\nfrom the large to small database is a one time cost. This works well because\r\nyou're often only modifying a subset of files at a time.\r\n\r\nSee bitbucket[1] or github[2] for more information and current development.\r\n\r\n[1] https:\/\/bitbucket.org\/ericgarver\/cscope_dynamic\r\n[2] https:\/\/github.com\/erig0\/cscope_dynamic","install_details":"","5":"","first_name":"Eric","6":"Eric","last_name":"Garver","7":"Garver","releases":[{"0":"5098","vim_version":"7.3","1":"7.3","script_version":"0.6","2":"0.6","version_comment":"Add support for g:cscopedb_src_dirs_file to specify directories to search for source files.\r\nContributed by Geesun Xu.","3":"Add support for g:cscopedb_src_dirs_file to specify directories to search for source files.\r\nContributed by Geesun Xu.","package":"cscope_dynamic-0.6.vmb.gz","4":"cscope_dynamic-0.6.vmb.gz","src_id":"24093","5":"24093","creation_date":"1457790862","6":"1457790862"},{"0":"5098","vim_version":"7.3","1":"7.3","script_version":"0.3","2":"0.3","version_comment":"Initial upload","3":"Initial upload","package":"cscope_dynamic-0.3.vmb.gz","4":"cscope_dynamic-0.3.vmb.gz","src_id":"22845","5":"22845","creation_date":"1422389654","6":"1422389654"}]},"5097":{"script_id":"5097","0":"5097","script_name":"vim-less","1":"vim-less","script_type":"syntax","2":"syntax","summary":"LESS css syntax updated to v2.3.0 - 2015","3":"LESS css syntax updated to v2.3.0 - 2015","description":"This vim bundle adds syntax highlighting, indenting and autocompletion for the dynamic stylesheet language LESS.\r\n\r\n* Update to LESS v2.3.0\r\n* vim-css-color Compatible\r\n* vim-css3-syntax Compatible\r\n* Any bundle that places css syntax into after\/syntax\/css\/*","4":"This vim bundle adds syntax highlighting, indenting and autocompletion for the dynamic stylesheet language LESS.\r\n\r\n* Update to LESS v2.3.0\r\n* vim-css-color Compatible\r\n* vim-css3-syntax Compatible\r\n* Any bundle that places css syntax into after\/syntax\/css\/*","install_details":"Installing and Using\r\n\r\nInstall pathogen into ~\/.vim\/autoload\/ and add the following line to your ~\/.vimrc:\r\n\r\ncall pathogen#infect()\r\n\r\nMake a clone of the vim-less repository:\r\n\r\n$ mkdir -p ~\/.vim\/bundle $ cd ~\/.vim\/bundle $ git clone https:\/\/github.com\/luishdez\/vim-less\r\n\r\nOR use vundle, adding this line to your ~\/.vimrc:\r\n\r\nBundle \\'luishdez\/vim-less\\'\r\n\r\nOR use git submodules:\r\n\r\n$ git submodule add https:\/\/github.com\/luishdez\/vim-less.git bundle\/vim-less $ git submodule init","5":"Installing and Using\r\n\r\nInstall pathogen into ~\/.vim\/autoload\/ and add the following line to your ~\/.vimrc:\r\n\r\ncall pathogen#infect()\r\n\r\nMake a clone of the vim-less repository:\r\n\r\n$ mkdir -p ~\/.vim\/bundle $ cd ~\/.vim\/bundle $ git clone https:\/\/github.com\/luishdez\/vim-less\r\n\r\nOR use vundle, adding this line to your ~\/.vimrc:\r\n\r\nBundle \\'luishdez\/vim-less\\'\r\n\r\nOR use git submodules:\r\n\r\n$ git submodule add https:\/\/github.com\/luishdez\/vim-less.git bundle\/vim-less $ git submodule init","first_name":"Luis","6":"Luis","last_name":"Hdez","7":"Hdez","releases":[{"0":"5097","vim_version":"7.0","1":"7.0","script_version":"1.0.0","2":"1.0.0","version_comment":"Initial upload","3":"Initial upload","package":"vim-less-1.0.0.zip","4":"vim-less-1.0.0.zip","src_id":"22842","5":"22842","creation_date":"1422387745","6":"1422387745"}]},"5096":{"script_id":"5096","0":"5096","script_name":"Space Ident Highlighter","1":"Space Ident Highlighter","script_type":"ftplugin","2":"ftplugin","summary":"Plugin to mark vertically identation made by spaces","3":"Plugin to mark vertically identation made by spaces","description":"This plugin is activated by i. It does mark vertically the indentation in code when the indentation is done by spaces.","4":"This plugin is activated by i. It does mark vertically the indentation in code when the indentation is done by spaces.","install_details":"Simply drop this file into your $HOME\/.vim\/plugin directory.\r\n","5":"Simply drop this file into your $HOME\/.vim\/plugin directory.\r\n","first_name":"Estevan","6":"Estevan","last_name":"Vedovelli","7":"Vedovelli","releases":[{"0":"5096","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"SpaceIdentHighlighter.vim","4":"SpaceIdentHighlighter.vim","src_id":"22841","5":"22841","creation_date":"1422384967","6":"1422384967"}]},"5095":{"script_id":"5095","0":"5095","script_name":"codekit.vim","1":"codekit.vim","script_type":"utility","2":"utility","summary":"CodeKit 2 support for Vim","3":"CodeKit 2 support for Vim","description":"CodeKit.vim provides support for controlling CodeKit 2 from Vim. It uses\r\nCodeKit's AppleScript interface to provide the following features:\r\n\r\n* Add the current project to CodeKit\r\n* Switch to the current file's project\r\n* Preview the current project in a browser\r\n* Pause and unpause CodeKit's watching of project files\r\n\r\nSee `:help codekit` for a list of the provided commands.\r\n\r\nGit repository and issue tracker available at: https:\/\/github.com\/noahfrederick\/vim-codekit","4":"CodeKit.vim provides support for controlling CodeKit 2 from Vim. It uses\r\nCodeKit's AppleScript interface to provide the following features:\r\n\r\n* Add the current project to CodeKit\r\n* Switch to the current file's project\r\n* Preview the current project in a browser\r\n* Pause and unpause CodeKit's watching of project files\r\n\r\nSee `:help codekit` for a list of the provided commands.\r\n\r\nGit repository and issue tracker available at: https:\/\/github.com\/noahfrederick\/vim-codekit","install_details":"","5":"","first_name":"Noah","6":"Noah","last_name":"Frederick","7":"Frederick","releases":[{"0":"5095","vim_version":"7.3","1":"7.3","script_version":"1.0.0","2":"1.0.0","version_comment":"Initial upload","3":"Initial upload","package":"codekit-1.0.0.zip","4":"codekit-1.0.0.zip","src_id":"22831","5":"22831","creation_date":"1422327562","6":"1422327562"}]},"5094":{"script_id":"5094","0":"5094","script_name":"partial","1":"partial","script_type":"utility","2":"utility","summary":"Easily extract partials from your code","3":"Easily extract partials from your code","description":"Partial plugin is a tool developed to help you break down your code into\r\npartials. Simply select some lines on Visual mode, hit x, enter the\r\ndesired partial location and the plugin will place the appropiate replacement.\r\n\r\nhttps:\/\/github.com\/jbgutierrez\/vim-partial","4":"Partial plugin is a tool developed to help you break down your code into\r\npartials. Simply select some lines on Visual mode, hit x, enter the\r\ndesired partial location and the plugin will place the appropiate replacement.\r\n\r\nhttps:\/\/github.com\/jbgutierrez\/vim-partial","install_details":"Install in ~\/.vim\/plugin (~\\vimfiles\\plugin on Windows)\r\n","5":"Install in ~\/.vim\/plugin (~\\vimfiles\\plugin on Windows)\r\n","first_name":"Javier","6":"Javier","last_name":"Blanco","7":"Blanco","releases":[{"0":"5094","vim_version":"7.0","1":"7.0","script_version":"0.1.0","2":"0.1.0","version_comment":"Initial upload","3":"Initial upload","package":"partial.tar","4":"partial.tar","src_id":"22828","5":"22828","creation_date":"1422230150","6":"1422230150"}]},"5093":{"script_id":"5093","0":"5093","script_name":"readdir","1":"readdir","script_type":"utility","2":"utility","summary":"A very minimal directory browser","3":"A very minimal directory browser","description":"A minimal directory browser in just ~100 lines of VimL. To use it, just open a directory and use Enter to change into directories or open files.\r\n\r\nScreenshot available at\r\nhttps:\/\/github.com\/ap\/vim-readdir","4":"A minimal directory browser in just ~100 lines of VimL. To use it, just open a directory and use Enter to change into directories or open files.\r\n\r\nScreenshot available at\r\nhttps:\/\/github.com\/ap\/vim-readdir","install_details":"Cloning from GitHub using a plugin manager is recommended.\r\nhttps:\/\/github.com\/ap\/vim-readdir\r\n\r\nOtherwise download and unzip in your .vim directory.","5":"Cloning from GitHub using a plugin manager is recommended.\r\nhttps:\/\/github.com\/ap\/vim-readdir\r\n\r\nOtherwise download and unzip in your .vim directory.","first_name":"Aristotle","6":"Aristotle","last_name":"Pagaltzis","7":"Pagaltzis","releases":[{"0":"5093","vim_version":"7.0","1":"7.0","script_version":"9cfe91ed57","2":"9cfe91ed57","version_comment":"Mappings to ascend one directory and to open the current file in a tab; current directory matches shown directory; support for Vim 7.0; better OS portability; fixes for various bugs","3":"Mappings to ascend one directory and to open the current file in a tab; current directory matches shown directory; support for Vim 7.0; better OS portability; fixes for various bugs","package":"readdir.zip","4":"readdir.zip","src_id":"27883","5":"27883","creation_date":"1641032951","6":"1641032951"}]},"5092":{"script_id":"5092","0":"5092","script_name":"screensaver.vim","1":"screensaver.vim","script_type":"utility","2":"utility","summary":"Screensavers for Vim","3":"Screensavers for Vim","description":"NOTE: I don't upload code to vim.org anymore. Please clone from https:\/\/github.com\/itchyny\/screensaver.vim.\r\n\r\n\r\nThis plugin provides some screensavers for Vim. \r\n\r\nThe default screensaver is the clock moving screensaver.\r\n\r\nThe repository is https:\/\/github.com\/itchyny\/screensaver.vim.","4":"NOTE: I don't upload code to vim.org anymore. Please clone from https:\/\/github.com\/itchyny\/screensaver.vim.\r\n\r\n\r\nThis plugin provides some screensavers for Vim. \r\n\r\nThe default screensaver is the clock moving screensaver.\r\n\r\nThe repository is https:\/\/github.com\/itchyny\/screensaver.vim.","install_details":"","5":"","first_name":"itchyny","6":"itchyny","last_name":"\u3000","7":"　","releases":[{"0":"5092","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"screensaver.vim-0.1.zip","4":"screensaver.vim-0.1.zip","src_id":"22819","5":"22819","creation_date":"1421799220","6":"1421799220"}]},"5091":{"script_id":"5091","0":"5091","script_name":"perline-diff.vim","1":"perline-diff.vim","script_type":"utility","2":"utility","summary":"this line, that line, then diff comes up","3":"this line, that line, then diff comes up","description":"You can see the differences between any lines displayed on the vim.\r\n\r\nIt is handy and simple. Press  on a line in some window, and press  again on another line in same or different window, then horizontally separated two tiny windows come up at the bottom of this page and shows those differences. Selected each lines are differently highlighted on their window. To return back to the original screen, just press .\r\n\r\nYou can select a block of lines by pressing  in visual mode or by using SPLDiff command with range. If prefer to see those diff windows at top and\/or in vertical, use g:PLDWLType global variable.  and  keys are configurable as well.\r\n\r\nIf diffchar.vim plugin has been installed, you can see the exact differences on both the perline diff windows.\r\n\r\nCommands\r\n:[range]SPLDiff - select lines and show those diff windows\r\n:QPLDiff - quit the perline diff windows\r\n\r\nConfigurable keymaps\r\nShowPerlineDiff (default: )\r\nQuitPerlineDiff (default: )\r\n\r\nGlobal variables\r\ng:PLDWLType - layout type of perline diff windows\r\n    1 : bottom horizontal (default)\r\n    2 : bottom vertical\r\n    3 : top horizontal\r\n    4 : top vertical\r\n\r\nUpdate 1.2\r\n* Fixed to restore the size of existing windows after closing perline diff windows.\r\n* Fixed to show the exact difference with diffchar.vim 5.3 and later.\r\n\r\nUpdate 1.1\r\n* If an original window has been in diff mode, temporary clear its diff mode while displaying perline diff windows.\r\n* If the selected lines are moved on the original window, their highlights will also follow those lines.\r\n* Adjust height of perline diff windows to show just as many selected lines as possible including diff filler lines, within the half of vim's height.","4":"You can see the differences between any lines displayed on the vim.\r\n\r\nIt is handy and simple. Press  on a line in some window, and press  again on another line in same or different window, then horizontally separated two tiny windows come up at the bottom of this page and shows those differences. Selected each lines are differently highlighted on their window. To return back to the original screen, just press .\r\n\r\nYou can select a block of lines by pressing  in visual mode or by using SPLDiff command with range. If prefer to see those diff windows at top and\/or in vertical, use g:PLDWLType global variable.  and  keys are configurable as well.\r\n\r\nIf diffchar.vim plugin has been installed, you can see the exact differences on both the perline diff windows.\r\n\r\nCommands\r\n:[range]SPLDiff - select lines and show those diff windows\r\n:QPLDiff - quit the perline diff windows\r\n\r\nConfigurable keymaps\r\nShowPerlineDiff (default: )\r\nQuitPerlineDiff (default: )\r\n\r\nGlobal variables\r\ng:PLDWLType - layout type of perline diff windows\r\n    1 : bottom horizontal (default)\r\n    2 : bottom vertical\r\n    3 : top horizontal\r\n    4 : top vertical\r\n\r\nUpdate 1.2\r\n* Fixed to restore the size of existing windows after closing perline diff windows.\r\n* Fixed to show the exact difference with diffchar.vim 5.3 and later.\r\n\r\nUpdate 1.1\r\n* If an original window has been in diff mode, temporary clear its diff mode while displaying perline diff windows.\r\n* If the selected lines are moved on the original window, their highlights will also follow those lines.\r\n* Adjust height of perline diff windows to show just as many selected lines as possible including diff filler lines, within the half of vim's height.","install_details":"","5":"","first_name":"Rick","6":"Rick","last_name":"Howe","7":"Howe","releases":[{"0":"5091","vim_version":"7.0","1":"7.0","script_version":"1.2","2":"1.2","version_comment":"Restore the size of existing windows. Show the exact difference with diffchar.vim 5.3 and later.","3":"Restore the size of existing windows. Show the exact difference with diffchar.vim 5.3 and later.","package":"perline-diff.vim","4":"perline-diff.vim","src_id":"23650","5":"23650","creation_date":"1444198114","6":"1444198114"},{"0":"5091","vim_version":"7.0","1":"7.0","script_version":"1.1","2":"1.1","version_comment":"Show as many selected and filler lines as possible. Show only the difference between selected lines by clearing diff mode on existing windows.","3":"Show as many selected and filler lines as possible. Show only the difference between selected lines by clearing diff mode on existing windows.","package":"perline-diff.vim","4":"perline-diff.vim","src_id":"22874","5":"22874","creation_date":"1423122953","6":"1423122953"},{"0":"5091","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"perline-diff.vim","4":"perline-diff.vim","src_id":"22804","5":"22804","creation_date":"1421505133","6":"1421505133"}]},"5090":{"script_id":"5090","0":"5090","script_name":"vim-lastplace","1":"vim-lastplace","script_type":"utility","2":"utility","summary":"Intelligently reopen files where you left off.","3":"Intelligently reopen files where you left off.","description":"Intelligently reopen files where you left off.\r\n\r\nBy default git, svn, and mercurial commit messages are ignored because you probably want to type a new message and not re-edit the previous one.\r\n\r\nAdvantages over the snippets that can be found around the net include:\r\n* Maximize Context\r\n    - Center the cursor vertically after restoring last edit position.\r\n    - Keep as much of the file on screen as possible when last edit position is at the end of the file.\r\n* Commit messages automatically start beginning of the file. This is important because many version control systems re-use the same file for commit message editing.\r\n* Opens folds if the last edit position is inside a fold.\r\n\r\nThis plugin is maintained on GitHub: https:\/\/github.com\/farmergreg\/vim-lastplace\r\n","4":"Intelligently reopen files where you left off.\r\n\r\nBy default git, svn, and mercurial commit messages are ignored because you probably want to type a new message and not re-edit the previous one.\r\n\r\nAdvantages over the snippets that can be found around the net include:\r\n* Maximize Context\r\n    - Center the cursor vertically after restoring last edit position.\r\n    - Keep as much of the file on screen as possible when last edit position is at the end of the file.\r\n* Commit messages automatically start beginning of the file. This is important because many version control systems re-use the same file for commit message editing.\r\n* Opens folds if the last edit position is inside a fold.\r\n\r\nThis plugin is maintained on GitHub: https:\/\/github.com\/farmergreg\/vim-lastplace\r\n","install_details":"vim 8 and newer:\r\n----------------------\r\nmkdir -p ~\/.vim\/pack\/plugins\/start\r\nrm -rf ~\/.vim\/pack\/plugins\/start\/vim-lastplace\r\ngit clone --depth=1 https:\/\/github.com\/farmergreg\/vim-lastplace.git ~\/.vim\/pack\/plugins\/start\/vim-lastplace\r\n\r\n\r\nneovim:\r\n----------\r\nmkdir -p ~\/.local\/share\/nvim\/site\/pack\/plugins\/start\r\nrm -rf ~\/.local\/share\/nvim\/site\/pack\/plugins\/start\/vim-lastplace\r\ngit clone --depth=1 https:\/\/github.com\/farmergreg\/vim-lastplace.git ~\/.local\/share\/nvim\/site\/pack\/plugins\/start\/vim-lastplace","5":"vim 8 and newer:\r\n----------------------\r\nmkdir -p ~\/.vim\/pack\/plugins\/start\r\nrm -rf ~\/.vim\/pack\/plugins\/start\/vim-lastplace\r\ngit clone --depth=1 https:\/\/github.com\/farmergreg\/vim-lastplace.git ~\/.vim\/pack\/plugins\/start\/vim-lastplace\r\n\r\n\r\nneovim:\r\n----------\r\nmkdir -p ~\/.local\/share\/nvim\/site\/pack\/plugins\/start\r\nrm -rf ~\/.local\/share\/nvim\/site\/pack\/plugins\/start\/vim-lastplace\r\ngit clone --depth=1 https:\/\/github.com\/farmergreg\/vim-lastplace.git ~\/.local\/share\/nvim\/site\/pack\/plugins\/start\/vim-lastplace","first_name":"Greg","6":"Greg","last_name":"Dietsche","7":"Dietsche","releases":[{"0":"5090","vim_version":"7.0","1":"7.0","script_version":"4.5.0","2":"4.5.0","version_comment":"Automatically jump to the location of your most recent edit when opening files.\r\nNew in this release: the xxd filetype is ignored.","3":"Automatically jump to the location of your most recent edit when opening files.\r\nNew in this release: the xxd filetype is ignored.","package":"vim-lastplace-4.5.0.tar.gz","4":"vim-lastplace-4.5.0.tar.gz","src_id":"28677","5":"28677","creation_date":"1713909951","6":"1713909951"},{"0":"5090","vim_version":"7.0","1":"7.0","script_version":"4.5.0","2":"4.5.0","version_comment":"Automatically jump to the location of your most recent edit when opening files.\r\nNew in this release: the xxd filetype is ignored.","3":"Automatically jump to the location of your most recent edit when opening files.\r\nNew in this release: the xxd filetype is ignored.","package":"vim-lastplace-4.5.0.zip","4":"vim-lastplace-4.5.0.zip","src_id":"28676","5":"28676","creation_date":"1713909926","6":"1713909926"},{"0":"5090","vim_version":"7.0","1":"7.0","script_version":"4.0.0","2":"4.0.0","version_comment":"bugfixes and improvements","3":"bugfixes and improvements","package":"vim-lastplace-4.0.0.zip","4":"vim-lastplace-4.0.0.zip","src_id":"28537","5":"28537","creation_date":"1692945947","6":"1692945947"},{"0":"5090","vim_version":"7.0","1":"7.0","script_version":"4.0.0","2":"4.0.0","version_comment":"bug fixes and improvements","3":"bug fixes and improvements","package":"vim-lastplace-4.0.0.tar.gz","4":"vim-lastplace-4.0.0.tar.gz","src_id":"28536","5":"28536","creation_date":"1692945876","6":"1692945876"},{"0":"5090","vim_version":"7.0","1":"7.0","script_version":"3.2.1","2":"3.2.1","version_comment":"Small enhancements and updated documentation","3":"Small enhancements and updated documentation","package":"vim-lastplace-3.2.1.tar.gz","4":"vim-lastplace-3.2.1.tar.gz","src_id":"26932","5":"26932","creation_date":"1579578028","6":"1579578028"},{"0":"5090","vim_version":"7.0","1":"7.0","script_version":"3.2.1","2":"3.2.1","version_comment":"Small enhancements and updated documentation","3":"Small enhancements and updated documentation","package":"vim-lastplace-3.2.1.zip","4":"vim-lastplace-3.2.1.zip","src_id":"26931","5":"26931","creation_date":"1579578010","6":"1579578010"},{"0":"5090","vim_version":"7.0","1":"7.0","script_version":"3.1.1","2":"3.1.1","version_comment":"Bug Fix Release","3":"Bug Fix Release","package":"vim-lastplace-3.1.1.tar.gz","4":"vim-lastplace-3.1.1.tar.gz","src_id":"25323","5":"25323","creation_date":"1497899056","6":"1497899056"},{"0":"5090","vim_version":"7.0","1":"7.0","script_version":"3.1.1","2":"3.1.1","version_comment":"Bug Fix Release","3":"Bug Fix Release","package":"vim-lastplace-3.1.1.zip","4":"vim-lastplace-3.1.1.zip","src_id":"25322","5":"25322","creation_date":"1497899034","6":"1497899034"},{"0":"5090","vim_version":"7.0","1":"7.0","script_version":"3.1.0","2":"3.1.0","version_comment":"You can now configure buffer types to ignore by setting\r\ng:lastplace_ignore_buftype in your vimrc. This is a comma separated list.\r\n\r\nBy default it is set to:\r\nlet g:lastplace_ignore_buftype = \"quickfix\"","3":"You can now configure buffer types to ignore by setting\r\ng:lastplace_ignore_buftype in your vimrc. This is a comma separated list.\r\n\r\nBy default it is set to:\r\nlet g:lastplace_ignore_buftype = \"quickfix\"","package":"vim-lastplace-3.1.0.tar.gz","4":"vim-lastplace-3.1.0.tar.gz","src_id":"24984","5":"24984","creation_date":"1487712810","6":"1487712810"},{"0":"5090","vim_version":"7.0","1":"7.0","script_version":"3.1.0","2":"3.1.0","version_comment":"You can now configure buffer types to ignore by setting\r\ng:lastplace_ignore_buftype in your vimrc. This is a comma separated list.\r\n\r\nBy default it is set to:\r\nlet g:lastplace_ignore_buftype = \"quickfix\"","3":"You can now configure buffer types to ignore by setting\r\ng:lastplace_ignore_buftype in your vimrc. This is a comma separated list.\r\n\r\nBy default it is set to:\r\nlet g:lastplace_ignore_buftype = \"quickfix\"","package":"vim-lastplace-3.1.0.zip","4":"vim-lastplace-3.1.0.zip","src_id":"24983","5":"24983","creation_date":"1487712786","6":"1487712786"},{"0":"5090","vim_version":"7.0","1":"7.0","script_version":"3.0.4","2":"3.0.4","version_comment":"Added a setting g:lastplace_open_folds to control behavior when the last edit position is inside a fold.","3":"Added a setting g:lastplace_open_folds to control behavior when the last edit position is inside a fold.","package":"vim-lastplace-3.0.4.tar.gz","4":"vim-lastplace-3.0.4.tar.gz","src_id":"24507","5":"24507","creation_date":"1473214713","6":"1473214713"},{"0":"5090","vim_version":"7.0","1":"7.0","script_version":"3.0.4","2":"3.0.4","version_comment":"Added a setting g:lastplace_open_folds to control behavior when the last edit position is inside a fold.","3":"Added a setting g:lastplace_open_folds to control behavior when the last edit position is inside a fold.","package":"vim-lastplace-3.0.4.zip","4":"vim-lastplace-3.0.4.zip","src_id":"24506","5":"24506","creation_date":"1473214698","6":"1473214698"},{"0":"5090","vim_version":"7.0","1":"7.0","script_version":"3.0.3","2":"3.0.3","version_comment":"Changes to support Debian packaging effort.","3":"Changes to support Debian packaging effort.","package":"vim-lastplace-3.0.3.tar.gz","4":"vim-lastplace-3.0.3.tar.gz","src_id":"24443","5":"24443","creation_date":"1471012725","6":"1471012725"},{"0":"5090","vim_version":"7.0","1":"7.0","script_version":"3.0.3","2":"3.0.3","version_comment":"Changes to support Debian packaging effort.","3":"Changes to support Debian packaging effort.","package":"vim-lastplace-3.0.3.zip","4":"vim-lastplace-3.0.3.zip","src_id":"24441","5":"24441","creation_date":"1471012194","6":"1471012194"},{"0":"5090","vim_version":"7.0","1":"7.0","script_version":"3.0.2","2":"3.0.2","version_comment":"Fix problem with files shorter than the window height.","3":"Fix problem with files shorter than the window height.","package":"vim-lastplace-3.0.2.tar.gz","4":"vim-lastplace-3.0.2.tar.gz","src_id":"24243","5":"24243","creation_date":"1463060126","6":"1463060126"},{"0":"5090","vim_version":"7.0","1":"7.0","script_version":"3.0.2","2":"3.0.2","version_comment":"Fix problem with files shorter than the window height.","3":"Fix problem with files shorter than the window height.","package":"vim-lastplace-3.0.2.zip","4":"vim-lastplace-3.0.2.zip","src_id":"24242","5":"24242","creation_date":"1463060109","6":"1463060109"},{"0":"5090","vim_version":"7.0","1":"7.0","script_version":"3.0.1","2":"3.0.1","version_comment":"Fix problems with modelines.","3":"Fix problems with modelines.","package":"vim-lastplace-3.0.1.tar.gz","4":"vim-lastplace-3.0.1.tar.gz","src_id":"23919","5":"23919","creation_date":"1453001923","6":"1453001923"},{"0":"5090","vim_version":"7.0","1":"7.0","script_version":"3.0.1","2":"3.0.1","version_comment":"A fix for files with modelines.","3":"A fix for files with modelines.","package":"vim-lastplace.zip","4":"vim-lastplace.zip","src_id":"23917","5":"23917","creation_date":"1453001785","6":"1453001785"},{"0":"5090","vim_version":"7.0","1":"7.0","script_version":"3.0.0","2":"3.0.0","version_comment":"Expands folds if the last edit was made inside an area that is hidden inside a fold.","3":"Expands folds if the last edit was made inside an area that is hidden inside a fold.","package":"vim-lastplace-3.0.0.tar.gz","4":"vim-lastplace-3.0.0.tar.gz","src_id":"23476","5":"23476","creation_date":"1437667276","6":"1437667276"},{"0":"5090","vim_version":"7.0","1":"7.0","script_version":"2.0.1","2":"2.0.1","version_comment":"Add gitrebase filetype to the ignore list.","3":"Add gitrebase filetype to the ignore list.","package":"vim-lastplace-2.0.1.tar.gz","4":"vim-lastplace-2.0.1.tar.gz","src_id":"22829","5":"22829","creation_date":"1422290927","6":"1422290927"},{"0":"5090","vim_version":"7.0","1":"7.0","script_version":"2.0.0","2":"2.0.0","version_comment":"New features: \r\n1) Center the screen when restoring the cursor position.\r\n2) When at the end of a file, keep as much of it on screen as possible.","3":"New features: \r\n1) Center the screen when restoring the cursor position.\r\n2) When at the end of a file, keep as much of it on screen as possible.","package":"vim-lastplace.tgz","4":"vim-lastplace.tgz","src_id":"22821","5":"22821","creation_date":"1421966286","6":"1421966286"},{"0":"5090","vim_version":"7.0","1":"7.0","script_version":"1.0.0","2":"1.0.0","version_comment":"Initial upload","3":"Initial upload","package":"vim-lastplace.tar.gz","4":"vim-lastplace.tar.gz","src_id":"22791","5":"22791","creation_date":"1421284351","6":"1421284351"}]},"5089":{"script_id":"5089","0":"5089","script_name":"vim-fetch","1":"vim-fetch","script_type":"utility","2":"utility","summary":"Make Vim handle line and column numbers in file names with a minimum of fuss","3":"Make Vim handle line and column numbers in file names with a minimum of fuss","description":"vim-fetch enables Vim to process line and column jump specifications in file paths as found in stack traces and similar output. When asked to open such a file, Vim with vim-fetch will jump to the specified line (and column, if given) instead of displaying an empty, new file.\r\n\r\nIf you have wished Vim would understand stack trace formats when loading files without making you jump through Quickfix hoops, vim-fetch is for you.\r\n\r\nProject repository: https:\/\/github.com\/wsdjeg\/vim-fetch\r\n\r\nNOTE: Maintainership for vim-fetch has been talken over by Wang Shidong. Links on this page have been corrected or will redirect to the new GitHub repository. Please do refer to the above mentioned repository for future developments.","4":"vim-fetch enables Vim to process line and column jump specifications in file paths as found in stack traces and similar output. When asked to open such a file, Vim with vim-fetch will jump to the specified line (and column, if given) instead of displaying an empty, new file.\r\n\r\nIf you have wished Vim would understand stack trace formats when loading files without making you jump through Quickfix hoops, vim-fetch is for you.\r\n\r\nProject repository: https:\/\/github.com\/wsdjeg\/vim-fetch\r\n\r\nNOTE: Maintainership for vim-fetch has been talken over by Wang Shidong. Links on this page have been corrected or will redirect to the new GitHub repository. Please do refer to the above mentioned repository for future developments.","install_details":"Download and source the most current vimball from the releases list, then run :helptags {dir} on your runtimepath\/doc directory. Or, if you use a git-based plug-in manager (like Pathogen, Vundle, NeoBundle etc.), simply add wsdjeg\/vim-fetch to the list of plug-ins, source that and issue your manager's install command.","5":"Download and source the most current vimball from the releases list, then run :helptags {dir} on your runtimepath\/doc directory. Or, if you use a git-based plug-in manager (like Pathogen, Vundle, NeoBundle etc.), simply add wsdjeg\/vim-fetch to the list of plug-ins, source that and issue your manager's install command.","first_name":"Martin","6":"Martin","last_name":"Kopischke","7":"Kopischke","releases":[{"0":"5089","vim_version":"7.0","1":"7.0","script_version":"3.0.0","2":"3.0.0","version_comment":"Restore full functionality for Vim 8. Release notes: https:\/\/github.com\/kopischke\/vim-fetch\/releases\/tag\/v3.0.0","3":"Restore full functionality for Vim 8. Release notes: https:\/\/github.com\/kopischke\/vim-fetch\/releases\/tag\/v3.0.0","package":"vim-fetch-3.0.0.vmb","4":"vim-fetch-3.0.0.vmb","src_id":"25865","5":"25865","creation_date":"1520292597","6":"1520292597"},{"0":"5089","vim_version":"7.0","1":"7.0","script_version":"2.0.2","2":"2.0.2","version_comment":"Release notes: https:\/\/github.com\/kopischke\/vim-fetch\/releases\/tag\/v2.0.2","3":"Release notes: https:\/\/github.com\/kopischke\/vim-fetch\/releases\/tag\/v2.0.2","package":"vim-fetch-2.0.2.vmb","4":"vim-fetch-2.0.2.vmb","src_id":"23339","5":"23339","creation_date":"1433091443","6":"1433091443"},{"0":"5089","vim_version":"7.0","1":"7.0","script_version":"2.0.1","2":"2.0.1","version_comment":"Release Notes: https:\/\/github.com\/kopischke\/vim-fetch\/releases\/tag\/v2.0.1","3":"Release Notes: https:\/\/github.com\/kopischke\/vim-fetch\/releases\/tag\/v2.0.1","package":"vim-fetch-2.0.1.vmb","4":"vim-fetch-2.0.1.vmb","src_id":"23015","5":"23015","creation_date":"1426176171","6":"1426176171"},{"0":"5089","vim_version":"7.0","1":"7.0","script_version":"2.0.0","2":"2.0.0","version_comment":"Key feature: full `gF` handling. Release notes: https:\/\/github.com\/kopischke\/vim-fetch\/releases\/tag\/v2.0.0","3":"Key feature: full `gF` handling. Release notes: https:\/\/github.com\/kopischke\/vim-fetch\/releases\/tag\/v2.0.0","package":"vim-fetch-2.0.0.vmb","4":"vim-fetch-2.0.0.vmb","src_id":"22952","5":"22952","creation_date":"1424868276","6":"1424868276"},{"0":"5089","vim_version":"7.0","1":"7.0","script_version":"1.3.0","2":"1.3.0","version_comment":"Release notes: https:\/\/github.com\/kopischke\/vim-fetch\/releases\/tag\/v1.3.0","3":"Release notes: https:\/\/github.com\/kopischke\/vim-fetch\/releases\/tag\/v1.3.0","package":"vim-fetch-1.3.0.vmb","4":"vim-fetch-1.3.0.vmb","src_id":"22850","5":"22850","creation_date":"1422531658","6":"1422531658"},{"0":"5089","vim_version":"7.0","1":"7.0","script_version":"1.2.0","2":"1.2.0","version_comment":"Release notes: https:\/\/github.com\/kopischke\/vim-fetch\/releases\/tag\/v1.2.0","3":"Release notes: https:\/\/github.com\/kopischke\/vim-fetch\/releases\/tag\/v1.2.0","package":"vim-fetch-1.2.0.vmb","4":"vim-fetch-1.2.0.vmb","src_id":"22811","5":"22811","creation_date":"1421710256","6":"1421710256"},{"0":"5089","vim_version":"7.0","1":"7.0","script_version":"1.1.0","2":"1.1.0","version_comment":"Release notes: https:\/\/github.com\/kopischke\/vim-fetch\/releases\/tag\/v1.1.0","3":"Release notes: https:\/\/github.com\/kopischke\/vim-fetch\/releases\/tag\/v1.1.0","package":"vim-fetch-1.1.0.vmb","4":"vim-fetch-1.1.0.vmb","src_id":"22790","5":"22790","creation_date":"1421258383","6":"1421258383"},{"0":"5089","vim_version":"7.0","1":"7.0","script_version":"1.0.1","2":"1.0.1","version_comment":"Release notes: https:\/\/github.com\/kopischke\/vim-fetch\/releases\/tag\/v1.0.1","3":"Release notes: https:\/\/github.com\/kopischke\/vim-fetch\/releases\/tag\/v1.0.1","package":"vim-fetch-1.0.1.vmb","4":"vim-fetch-1.0.1.vmb","src_id":"22789","5":"22789","creation_date":"1421230827","6":"1421230827"},{"0":"5089","vim_version":"7.0","1":"7.0","script_version":"1.0.0","2":"1.0.0","version_comment":"Initial upload","3":"Initial upload","package":"vim-fetch-1.0.0.vmb","4":"vim-fetch-1.0.0.vmb","src_id":"22788","5":"22788","creation_date":"1421170146","6":"1421170146"}]},"5088":{"script_id":"5088","0":"5088","script_name":"vim-pandoc-bundle","1":"vim-pandoc-bundle","script_type":"ftplugin","2":"ftplugin","summary":"pandoc markdown support for vim + utilities","3":"pandoc markdown support for vim + utilities","description":"This is a pre-packaged version of the\r\nhttp:\/\/github.com\/vim-pandoc main plugins. Those are updated\r\nversions of vimscript #3730.\r\n\r\nIt includes:\r\n\r\n* vim-pandoc http:\/\/github.com\/vim-pandoc\/vim-pandoc\r\n    + pandoc execution, through the :Pandoc command\r\n    + omni completion (for bibliographic references)\r\n    + advanced folding (normal, relative and stacked)\r\n    + text formatting setup (auto formatting modes available)\r\n    + etc.\r\n* vim-pandoc-syntax http:\/\/github.com\/vim-pandoc\/vim-pandoc-syntax\r\n    + syntax highlighting for pandoc markdown\r\n* vim-pandoc-after http:\/\/github.com\/vim-pandoc\/vim-pandoc-after\r\n    + third party plugins integration\r\n\r\n","4":"This is a pre-packaged version of the\r\nhttp:\/\/github.com\/vim-pandoc main plugins. Those are updated\r\nversions of vimscript #3730.\r\n\r\nIt includes:\r\n\r\n* vim-pandoc http:\/\/github.com\/vim-pandoc\/vim-pandoc\r\n    + pandoc execution, through the :Pandoc command\r\n    + omni completion (for bibliographic references)\r\n    + advanced folding (normal, relative and stacked)\r\n    + text formatting setup (auto formatting modes available)\r\n    + etc.\r\n* vim-pandoc-syntax http:\/\/github.com\/vim-pandoc\/vim-pandoc-syntax\r\n    + syntax highlighting for pandoc markdown\r\n* vim-pandoc-after http:\/\/github.com\/vim-pandoc\/vim-pandoc-after\r\n    + third party plugins integration\r\n\r\n","install_details":"Drop the files in your Vim `runtimepath` (usually `.vim` in \\*nix or `vimfiles`\r\nin windows).\r\n\r\n## Important\r\n\r\nThis bundle is provided for convenience for users of vim.org. It is better to\r\nuse the plugins from the github versions, since they are updated more often.\r\nConsult the links above for more info.","5":"Drop the files in your Vim `runtimepath` (usually `.vim` in \\*nix or `vimfiles`\r\nin windows).\r\n\r\n## Important\r\n\r\nThis bundle is provided for convenience for users of vim.org. It is better to\r\nuse the plugins from the github versions, since they are updated more often.\r\nConsult the links above for more info.","first_name":"Felipe","6":"Felipe","last_name":"Morales","7":"Morales","releases":[{"0":"5088","vim_version":"7.4","1":"7.4","script_version":"20150113","2":"20150113","version_comment":"Initial upload","3":"Initial upload","package":"vim-pandoc-bundle.zip","4":"vim-pandoc-bundle.zip","src_id":"22786","5":"22786","creation_date":"1421160584","6":"1421160584"}]},"5086":{"script_id":"5086","0":"5086","script_name":"DidYouMean","1":"DidYouMean","script_type":"utility","2":"utility","summary":"Ask for the right file to open","3":"Ask for the right file to open","description":"DidYouMean\r\n==========\r\n\r\nVim plugin which asks for the right file to open\r\n\r\nDemo: https:\/\/asciinema.org\/a\/15372\r\nGithub: https:\/\/github.com\/EinfachToll\/DidYouMean\r\n\r\nIf you're like me and you want to edit a specific file with Vim, say, `test.py`, you type `vim te` into the terminal, then you hit `` and `` immediately because you think your shell expands the characters to the right file name. But if there's another file starting with `te`, Vim fires up with an empty file called `te`, laughing at you. That's annoying. This simple plugin makes Vim ask for the right file to open.","4":"DidYouMean\r\n==========\r\n\r\nVim plugin which asks for the right file to open\r\n\r\nDemo: https:\/\/asciinema.org\/a\/15372\r\nGithub: https:\/\/github.com\/EinfachToll\/DidYouMean\r\n\r\nIf you're like me and you want to edit a specific file with Vim, say, `test.py`, you type `vim te` into the terminal, then you hit `` and `` immediately because you think your shell expands the characters to the right file name. But if there's another file starting with `te`, Vim fires up with an empty file called `te`, laughing at you. That's annoying. This simple plugin makes Vim ask for the right file to open.","install_details":"Just drop DidYouMean.vim into .vim\/plugin\/ or use a plugin manager like Pathogen or Vundle.","5":"Just drop DidYouMean.vim into .vim\/plugin\/ or use a plugin manager like Pathogen or Vundle.","first_name":"Daniel","6":"Daniel","last_name":"Schemala","7":"Schemala","releases":[{"0":"5086","vim_version":"7.0","1":"7.0","script_version":"1.0.2","2":"1.0.2","version_comment":"Fix: don't include the swap file","3":"Fix: don't include the swap file","package":"DidYouMean.vim","4":"DidYouMean.vim","src_id":"23218","5":"23218","creation_date":"1429793756","6":"1429793756"},{"0":"5086","vim_version":"7.0","1":"7.0","script_version":"1.0.1","2":"1.0.1","version_comment":"Catch and handle glob errors","3":"Catch and handle glob errors","package":"DidYouMean.vim","4":"DidYouMean.vim","src_id":"22859","5":"22859","creation_date":"1422967472","6":"1422967472"},{"0":"5086","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"DidYouMean.vim","4":"DidYouMean.vim","src_id":"22781","5":"22781","creation_date":"1421057304","6":"1421057304"}]},"5085":{"script_id":"5085","0":"5085","script_name":"Boston","1":"Boston","script_type":"ftplugin","2":"ftplugin","summary":"a key mapping plugin for commonly used coding shortcuts","3":"a key mapping plugin for commonly used coding shortcuts","description":"The Boston key mapping is particularly useful for day-to-day editing on code files. If you have other key mappings set up for the function keys they may not be compatible with this plugin. See below for a list of command mappings:\r\n\r\n thru : go to buffer 1-8.\r\nj: set up a file comparison environment for two Java files.\r\ns: set up a file comparison environment for two Javascript files.\r\nh: set up a file comparison environment for two HTML files.\r\nc: set up a file comparison environment for two CSS files.\r\nj: auto-format a Java file.\r\ns: auto-format a Javascript file.\r\nh: auto-format an HTML file.\r\nx: auto-format an XML file.","4":"The Boston key mapping is particularly useful for day-to-day editing on code files. If you have other key mappings set up for the function keys they may not be compatible with this plugin. See below for a list of command mappings:\r\n\r\n thru : go to buffer 1-8.\r\nj: set up a file comparison environment for two Java files.\r\ns: set up a file comparison environment for two Javascript files.\r\nh: set up a file comparison environment for two HTML files.\r\nc: set up a file comparison environment for two CSS files.\r\nj: auto-format a Java file.\r\ns: auto-format a Javascript file.\r\nh: auto-format an HTML file.\r\nx: auto-format an XML file.","install_details":"Install boston.vim to your plugin directory. This is a general plugin that is un-associated with any file type.","5":"Install boston.vim to your plugin directory. This is a general plugin that is un-associated with any file type.","first_name":"Christopher","6":"Christopher","last_name":"Reilly","7":"Reilly","releases":[{"0":"5085","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"boston.vim","4":"boston.vim","src_id":"22779","5":"22779","creation_date":"1421008884","6":"1421008884"}]},"5084":{"script_id":"5084","0":"5084","script_name":"Falmouth","1":"Falmouth","script_type":"color scheme","2":"color scheme","summary":"Falmouth is a pastel color scheme that is easy on the eyes.","3":"Falmouth is a pastel color scheme that is easy on the eyes.","description":"Falmouth is a color scheme that is easy on the eyes. It uses pastel colors for file comparisons that are minimally distracting so you can see what's really important: your text.","4":"Falmouth is a color scheme that is easy on the eyes. It uses pastel colors for file comparisons that are minimally distracting so you can see what's really important: your text.","install_details":"Install falmouth.vim to your colors directory. (eg. Vim\/vim73\/colors\/).","5":"Install falmouth.vim to your colors directory. (eg. Vim\/vim73\/colors\/).","first_name":"Christopher","6":"Christopher","last_name":"Reilly","7":"Reilly","releases":[{"0":"5084","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"falmouth.vim","4":"falmouth.vim","src_id":"22778","5":"22778","creation_date":"1421007095","6":"1421007095"}]},"5083":{"script_id":"5083","0":"5083","script_name":"yowish","1":"yowish","script_type":"color scheme","2":"color scheme","summary":"A yellowish dark colorscheme","3":"A yellowish dark colorscheme","description":"Yowish is a vim dark theme similar to outlander (https:\/\/atom.io\/themes\/outlander-syntax), with some yellow in it :) (Works well on both GUI & 256-colors terminal).\r\n\r\nDetails & screenshots here > https:\/\/github.com\/KabbAmine\/yowish.vim\r\n\r\nPlease rate it if you find it useful :)","4":"Yowish is a vim dark theme similar to outlander (https:\/\/atom.io\/themes\/outlander-syntax), with some yellow in it :) (Works well on both GUI & 256-colors terminal).\r\n\r\nDetails & screenshots here > https:\/\/github.com\/KabbAmine\/yowish.vim\r\n\r\nPlease rate it if you find it useful :)","install_details":"Manually\r\n=======\r\n\r\nCopy the distributed files into Vim runtime directory which is usually ~\/.vim\/, or $HOME\/vimfiles on Windows.\r\n\r\nAutomatically\r\n===========\r\n\r\nUse a plugin manager (Vundle, vim-plug....)","5":"Manually\r\n=======\r\n\r\nCopy the distributed files into Vim runtime directory which is usually ~\/.vim\/, or $HOME\/vimfiles on Windows.\r\n\r\nAutomatically\r\n===========\r\n\r\nUse a plugin manager (Vundle, vim-plug....)","first_name":"Kabbaj","6":"Kabbaj","last_name":"Amine","7":"Amine","releases":[{"0":"5083","vim_version":"7.0","1":"7.0","script_version":"0.7.1","2":"0.7.1","version_comment":"- Add custom colors for the plugin signjk-motion\r\n- Internal: Minor refactoring\r\n- Rename jade to pug\r\n- Add airline_error colors to airline themes","3":"- Add custom colors for the plugin signjk-motion\r\n- Internal: Minor refactoring\r\n- Rename jade to pug\r\n- Add airline_error colors to airline themes","package":"yowish.tar.gz","4":"yowish.tar.gz","src_id":"24073","5":"24073","creation_date":"1457277567","6":"1457277567"},{"0":"5083","vim_version":"7.0","1":"7.0","script_version":"0.7.0","2":"0.7.0","version_comment":"0.7.0\r\n- Add possibility to enable\/disable custom colors for plugins\r\n- Add custom colors for the plugin Unite\r\n0.6.4\r\n- Add more diff colors\r\n- Set better colors to quickfix & location list windows\r\n0.6.3\r\n- A better diff colors\r\n- Add custom colors for the plugin agit\r\n- Internal: Add links for used plugins","3":"0.7.0\r\n- Add possibility to enable\/disable custom colors for plugins\r\n- Add custom colors for the plugin Unite\r\n0.6.4\r\n- Add more diff colors\r\n- Set better colors to quickfix & location list windows\r\n0.6.3\r\n- A better diff colors\r\n- Add custom colors for the plugin agit\r\n- Internal: Add links for used plugins","package":"yowish.tar.gz","4":"yowish.tar.gz","src_id":"23989","5":"23989","creation_date":"1454681079","6":"1454681079"},{"0":"5083","vim_version":"7.0","1":"7.0","script_version":"0.6.2","2":"0.6.2","version_comment":"*** 0.6.2\r\n- Fix name of airline theme.\r\n*** 0.6.1\r\n- Update airline themes:\r\n- Add warningmsg colors\r\n- Fix insert_paste cterm colors\r\n- Add new screens to the README\r\n*** 0.6.0\r\n- Add a global variable `g:yowish` for user configuration\r\n- Add a new airline theme called *yowishU*\r\n- Small refactoring and code cleaning","3":"*** 0.6.2\r\n- Fix name of airline theme.\r\n*** 0.6.1\r\n- Update airline themes:\r\n- Add warningmsg colors\r\n- Fix insert_paste cterm colors\r\n- Add new screens to the README\r\n*** 0.6.0\r\n- Add a global variable `g:yowish` for user configuration\r\n- Add a new airline theme called *yowishU*\r\n- Small refactoring and code cleaning","package":"yowish.tar.gz","4":"yowish.tar.gz","src_id":"23887","5":"23887","creation_date":"1452504624","6":"1452504624"},{"0":"5083","vim_version":"7.0","1":"7.0","script_version":"0.5.5","2":"0.5.5","version_comment":"* Add jade support","3":"* Add jade support","package":"yowish.tar.gz","4":"yowish.tar.gz","src_id":"23745","5":"23745","creation_date":"1448107833","6":"1448107833"},{"0":"5083","vim_version":"7.0","1":"7.0","script_version":"0.5.4","2":"0.5.4","version_comment":"- Add ColorColumn group","3":"- Add ColorColumn group","package":"yowish.tar.gz","4":"yowish.tar.gz","src_id":"23690","5":"23690","creation_date":"1446031790","6":"1446031790"},{"0":"5083","vim_version":"7.0","1":"7.0","script_version":"0.5.3","2":"0.5.3","version_comment":"- Refactoring\r\n- Some changes in vimhelp colors\r\n- Better javascript & ruby support","3":"- Refactoring\r\n- Some changes in vimhelp colors\r\n- Better javascript & ruby support","package":"yowish.tar.gz","4":"yowish.tar.gz","src_id":"23675","5":"23675","creation_date":"1444990953","6":"1444990953"},{"0":"5083","vim_version":"7.0","1":"7.0","script_version":"0.5","2":"0.5","version_comment":"* Modify airline theme in NORMAL mode\r\n* Remove autoloaded files.\r\n* Refactoring\r\n* Add a CHANGELOG","3":"* Modify airline theme in NORMAL mode\r\n* Remove autoloaded files.\r\n* Refactoring\r\n* Add a CHANGELOG","package":"yowish.tar.gz","4":"yowish.tar.gz","src_id":"23640","5":"23640","creation_date":"1443958199","6":"1443958199"},{"0":"5083","vim_version":"7.0","1":"7.0","script_version":"0.4.1","2":"0.4.1","version_comment":"- Make search & incsearch (hlsearch) more visibles.\r\n- Link vimCommentString with vimComment.\r\n- Set back php variables to light red (More visible).","3":"- Make search & incsearch (hlsearch) more visibles.\r\n- Link vimCommentString with vimComment.\r\n- Set back php variables to light red (More visible).","package":"yowish.tar.gz","4":"yowish.tar.gz","src_id":"23082","5":"23082","creation_date":"1427018817","6":"1427018817"},{"0":"5083","vim_version":"7.0","1":"7.0","script_version":"0.4","2":"0.4","version_comment":"- Define colors and hi function in autoload files.\r\n- Modify php variables color.\r\n- Set a dark background for inactive windows in airline statusline.\r\n- Small refactoring.","3":"- Define colors and hi function in autoload files.\r\n- Modify php variables color.\r\n- Set a dark background for inactive windows in airline statusline.\r\n- Small refactoring.","package":"yowish.tar.gz","4":"yowish.tar.gz","src_id":"22887","5":"22887","creation_date":"1423319736","6":"1423319736"},{"0":"5083","vim_version":"7.0","1":"7.0","script_version":"0.3","2":"0.3","version_comment":"Update to v0.3:\r\n- Supports now terminals with 256 colors.\r\n- Add CtrlP custom colors.\r\n- Make cursor and visual selection more visibles.\r\n- Add specific theme for airlineplugin. ","3":"Update to v0.3:\r\n- Supports now terminals with 256 colors.\r\n- Add CtrlP custom colors.\r\n- Make cursor and visual selection more visibles.\r\n- Add specific theme for airlineplugin. ","package":"yowish.tar.gz","4":"yowish.tar.gz","src_id":"22784","5":"22784","creation_date":"1421141309","6":"1421141309"},{"0":"5083","vim_version":"7.0","1":"7.0","script_version":"0.2","2":"0.2","version_comment":"Update to v0.2:\r\n- Make general highlighting groups for better general support.\r\n- Symplify the code.\r\n- Add & change colors for better eye comfortableness.\r\n- No need anymore of Undotree custom colors.\r\n- Remove the loaded_nerdtree condition.","3":"Update to v0.2:\r\n- Make general highlighting groups for better general support.\r\n- Symplify the code.\r\n- Add & change colors for better eye comfortableness.\r\n- No need anymore of Undotree custom colors.\r\n- Remove the loaded_nerdtree condition.","package":"yowish.tar.gz","4":"yowish.tar.gz","src_id":"22777","5":"22777","creation_date":"1420984390","6":"1420984390"},{"0":"5083","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Correct typo","3":"Correct typo","package":"yowish.tar.gz","4":"yowish.tar.gz","src_id":"22774","5":"22774","creation_date":"1420902998","6":"1420902998"}]},"5082":{"script_id":"5082","0":"5082","script_name":"vital-string-interpolation","1":"vital-string-interpolation","script_type":"utility","2":"utility","summary":"String interpolation library for vim","3":"String interpolation library for vim","description":"\r\nSEE: https:\/\/github.com\/haya14busa\/vital-string-interpolation","4":"\r\nSEE: https:\/\/github.com\/haya14busa\/vital-string-interpolation","install_details":"","5":"","first_name":"haya14busa","6":"haya14busa","last_name":" ","7":" ","releases":[{"0":"5082","vim_version":"7.3","1":"7.3","script_version":"0.9.0","2":"0.9.0","version_comment":"Initial upload","3":"Initial upload","package":"vital-string-interpolation-0.9.0.zip","4":"vital-string-interpolation-0.9.0.zip","src_id":"22770","5":"22770","creation_date":"1420834784","6":"1420834784"}]},"5081":{"script_id":"5081","0":"5081","script_name":"Vim SQL Workbench","1":"Vim SQL Workbench","script_type":"utility","2":"utility","summary":"Provides sql access from vim to any DBMS","3":"Provides sql access from vim to any DBMS","description":"This is an implementation of SQL Workbench\/J (http:\/\/www.sql-workbench.net\/)\r\nin VIM. It works with any DBMS supported by SQL Workbench\/J (PostgreSQL,\r\nOracle, SQLite, MySQL, SQL Server etc.). See the complete list here: http:\/\/www.sql-workbench.net\/databases.html. \r\n\r\nYou can connect to any DBMS directly from VIM.\r\n\r\nFeatures:\r\n\r\n* database explorer (e.g.: table lists, procedures list, views list, triggers\r\n  list), extensible (you can have your own objects list)\r\n* SQL buffer with powerful intellisense autocomplete\r\n* export any sql statement as `text`, `sqlinsert`, `sqlupdate`,\r\n  `sqldeleteinsert`, `xml`, `ods`, `html`, `json`\r\n* search in object source\r\n* search in table or views data\r\n* transactions straight out from VIM\r\n* fully customizable\r\n\r\nMore details can be found here: https:\/\/github.com\/cosminadrianpopescu\/vim-sql-workbench","4":"This is an implementation of SQL Workbench\/J (http:\/\/www.sql-workbench.net\/)\r\nin VIM. It works with any DBMS supported by SQL Workbench\/J (PostgreSQL,\r\nOracle, SQLite, MySQL, SQL Server etc.). See the complete list here: http:\/\/www.sql-workbench.net\/databases.html. \r\n\r\nYou can connect to any DBMS directly from VIM.\r\n\r\nFeatures:\r\n\r\n* database explorer (e.g.: table lists, procedures list, views list, triggers\r\n  list), extensible (you can have your own objects list)\r\n* SQL buffer with powerful intellisense autocomplete\r\n* export any sql statement as `text`, `sqlinsert`, `sqlupdate`,\r\n  `sqldeleteinsert`, `xml`, `ods`, `html`, `json`\r\n* search in object source\r\n* search in table or views data\r\n* transactions straight out from VIM\r\n* fully customizable\r\n\r\nMore details can be found here: https:\/\/github.com\/cosminadrianpopescu\/vim-sql-workbench","install_details":"Install using any package manager or copying the files inside $HOME\/.vim","5":"Install using any package manager or copying the files inside $HOME\/.vim","first_name":"Cosmin","6":"Cosmin","last_name":"Popescu","7":"Popescu","releases":[{"0":"5081","vim_version":"8.2","1":"8.2","script_version":"8.2.2","2":"8.2.2","version_comment":"* better handling of the temporary files\r\n* bug fix: the settings file of `SQL Workbench\/J` would be overriden if the `sqlwbconsole` process would get killed\r\n* bug fix: when changing the profile, the autocomplete options would not change\r\n* fixed the background run\r\n* dbexplorer: now the references is based on the generated report\r\n* added support for `wb-profiles.properties` file\r\n* added support for master password\r\n* `SWSqlExecuteSelected` now supports ranges\r\n* minimum version of `SQL Workbench\/J` is now 128","3":"* better handling of the temporary files\r\n* bug fix: the settings file of `SQL Workbench\/J` would be overriden if the `sqlwbconsole` process would get killed\r\n* bug fix: when changing the profile, the autocomplete options would not change\r\n* fixed the background run\r\n* dbexplorer: now the references is based on the generated report\r\n* added support for `wb-profiles.properties` file\r\n* added support for master password\r\n* `SWSqlExecuteSelected` now supports ranges\r\n* minimum version of `SQL Workbench\/J` is now 128","package":"vim-sql-workbench.tar.gz","4":"vim-sql-workbench.tar.gz","src_id":"28127","5":"28127","creation_date":"1660926503","6":"1660926503"},{"0":"5081","vim_version":"7.4","1":"7.4","script_version":"8.2.1","2":"8.2.1","version_comment":"* Fixed the latest problem reported on github issue #25","3":"* Fixed the latest problem reported on github issue #25","package":"vim-sql-workbench.tar.gz","4":"vim-sql-workbench.tar.gz","src_id":"26225","5":"26225","creation_date":"1537334891","6":"1537334891"},{"0":"5081","vim_version":"7.4","1":"7.4","script_version":"8.2","2":"8.2","version_comment":"* added the `SWInclude` command\r\n* added an alternate delimiter when executting an sql\r\n* when doing `desc `, the columns are displayed before indexes now\r\n(issue #29)\r\n* when switching to the results buffer automatically, do a `keepalt` before\r\n(issue #36)\r\n* when doing `SWInclude` from an unconnected buffer, give a proper error\r\nmessage (issue #35)","3":"* added the `SWInclude` command\r\n* added an alternate delimiter when executting an sql\r\n* when doing `desc 
`, the columns are displayed before indexes now\r\n(issue #29)\r\n* when switching to the results buffer automatically, do a `keepalt` before\r\n(issue #36)\r\n* when doing `SWInclude` from an unconnected buffer, give a proper error\r\nmessage (issue #35)","package":"vim-sql-workbench.tar.gz","4":"vim-sql-workbench.tar.gz","src_id":"25931","5":"25931","creation_date":"1524079554","6":"1524079554"},{"0":"5081","vim_version":"7.4","1":"7.4","script_version":"8.1","2":"8.1","version_comment":"* fixed documentation issues\r\n* added the `CtrlPSW` command (will open CtrlP with the SW profiles)\r\n* added the `CtrlPClearSWCache` command (will parse profiles from scratch\r\nwhen opening CtrlP)\r\n* fixed the spaces in profiles name (CtrlP will fail if there was a space in\r\nthe profile name or in the group name)\r\n* switch back the autocomplete to `` for compatibility with\r\n`YouCompleteMe`\r\n* fixed case sensitiviness in the column names in the result set (will not\r\nfilter or hide columns because of it)\r\n* fixed quote issue in the profile names (having a single quote in a profile\r\nname would break `CtrlP` and any profiles completion)\r\n","3":"* fixed documentation issues\r\n* added the `CtrlPSW` command (will open CtrlP with the SW profiles)\r\n* added the `CtrlPClearSWCache` command (will parse profiles from scratch\r\nwhen opening CtrlP)\r\n* fixed the spaces in profiles name (CtrlP will fail if there was a space in\r\nthe profile name or in the group name)\r\n* switch back the autocomplete to `` for compatibility with\r\n`YouCompleteMe`\r\n* fixed case sensitiviness in the column names in the result set (will not\r\nfilter or hide columns because of it)\r\n* fixed quote issue in the profile names (having a single quote in a profile\r\nname would break `CtrlP` and any profiles completion)\r\n","package":"vim-sql-workbench.tar.gz","4":"vim-sql-workbench.tar.gz","src_id":"25895","5":"25895","creation_date":"1521665926","6":"1521665926"},{"0":"5081","vim_version":"7.0","1":"7.0","script_version":"8.0","2":"8.0","version_comment":"* for autocomplete, added all fields\r\n* for autocomplete, in fields insert, added the db type of the field\r\n* for autocomplete, fixed several bugs (now it's working also for subqueries)\r\n* for autocomplete, improved the caching\r\n* for autocomplete, for insert, in the fields part, once a field is inserted,\r\nthe next autocomplete will not return it.\r\n* added autocomplete for macros\r\n* for autocomplete, when a subquery is found, is returned as `subquery`,\r\ninstead of `#ALIAS#` in the completion menu\r\n* added the possibility to cache several `wbschemaexports`\r\n* added the possibility to follow all the references of a resultset (which\r\nrows is the current row referecing and which rows from other tables are\r\nreferencing the current row): see `SWSqlReferences` and `SWSqlReferencedBy`\r\n* added the possibility to fetch the references tree only until a certain\r\nlevel\r\n* for filtering and hiding columns, a new query is sent to the database now\r\n* when in an sql buffer, on an insert, if you are in the fields part, you can\r\nsee the corresponding value and when on a value in the values part, you can\r\nsee the corresponding column (see SWSqlMatch)\r\n* now, you can execute macros just like a query (so no shortcut for\r\n`SWSqlExecuteMacro`); you can do `c-` on a macro and is going\r\nto be interpreted correctly\r\n* you can now get the sql behind a macro (see `SWSqlGetMacroSql)\r\n* you can choose now to send to the server the macro `sql` query rather than\r\nthe macro (see `g:sw_prefer_sql_over_macro` option)\r\n* when autocompleting the list of columns (for example for `SWSqlFilter`), now\r\nfor identical identifiers the table part will be added in paranthesis after\r\nthe column name\r\n* now, when filtering, you can directly insert the insert sql part for the\r\ncurrent resultset (see `SWSqlFilter`)\r\n* added the `SWSqlGenerateInsert` command, which will generate an insert which\r\nwill be coppied in the clipboard\r\n* commands removed: `SWSqlExecuteMacro`, `SWSqlShowOnlyColumn`,\r\n`SWSqlForeignKey`, `SWSqlFilterColumn`, `SWSqlUnfilterColumn`,\r\n`SWSqlRemoveAllFilters`\r\n* commands added: `SWSqlReferences`, `SWSqlReferencedBy`, `SWSqlFilter`,\r\n`SWSqlUnfilter`, `SWSqlGenerateInsert`, `SWSqlGetMacroSql`,\r\n`SWSqlInsertMatch`\r\n* added `dbext` comparison","3":"* for autocomplete, added all fields\r\n* for autocomplete, in fields insert, added the db type of the field\r\n* for autocomplete, fixed several bugs (now it's working also for subqueries)\r\n* for autocomplete, improved the caching\r\n* for autocomplete, for insert, in the fields part, once a field is inserted,\r\nthe next autocomplete will not return it.\r\n* added autocomplete for macros\r\n* for autocomplete, when a subquery is found, is returned as `subquery`,\r\ninstead of `#ALIAS#` in the completion menu\r\n* added the possibility to cache several `wbschemaexports`\r\n* added the possibility to follow all the references of a resultset (which\r\nrows is the current row referecing and which rows from other tables are\r\nreferencing the current row): see `SWSqlReferences` and `SWSqlReferencedBy`\r\n* added the possibility to fetch the references tree only until a certain\r\nlevel\r\n* for filtering and hiding columns, a new query is sent to the database now\r\n* when in an sql buffer, on an insert, if you are in the fields part, you can\r\nsee the corresponding value and when on a value in the values part, you can\r\nsee the corresponding column (see SWSqlMatch)\r\n* now, you can execute macros just like a query (so no shortcut for\r\n`SWSqlExecuteMacro`); you can do `c-` on a macro and is going\r\nto be interpreted correctly\r\n* you can now get the sql behind a macro (see `SWSqlGetMacroSql)\r\n* you can choose now to send to the server the macro `sql` query rather than\r\nthe macro (see `g:sw_prefer_sql_over_macro` option)\r\n* when autocompleting the list of columns (for example for `SWSqlFilter`), now\r\nfor identical identifiers the table part will be added in paranthesis after\r\nthe column name\r\n* now, when filtering, you can directly insert the insert sql part for the\r\ncurrent resultset (see `SWSqlFilter`)\r\n* added the `SWSqlGenerateInsert` command, which will generate an insert which\r\nwill be coppied in the clipboard\r\n* commands removed: `SWSqlExecuteMacro`, `SWSqlShowOnlyColumn`,\r\n`SWSqlForeignKey`, `SWSqlFilterColumn`, `SWSqlUnfilterColumn`,\r\n`SWSqlRemoveAllFilters`\r\n* commands added: `SWSqlReferences`, `SWSqlReferencedBy`, `SWSqlFilter`,\r\n`SWSqlUnfilter`, `SWSqlGenerateInsert`, `SWSqlGetMacroSql`,\r\n`SWSqlInsertMatch`\r\n* added `dbext` comparison","package":"vim-sql-workbench.tar.gz","4":"vim-sql-workbench.tar.gz","src_id":"25655","5":"25655","creation_date":"1511369619","6":"1511369619"},{"0":"5081","vim_version":"7.0","1":"7.0","script_version":"7.1.2","2":"7.1.2","version_comment":"* updated the doc to specify the `g:sw_plugin_path` variable\r\n* fixed the `g:sw_cache` variable bug declaration","3":"* updated the doc to specify the `g:sw_plugin_path` variable\r\n* fixed the `g:sw_cache` variable bug declaration","package":"vim-sql-workbench.tar.gz","4":"vim-sql-workbench.tar.gz","src_id":"25490","5":"25490","creation_date":"1502220738","6":"1502220738"},{"0":"5081","vim_version":"7.0","1":"7.0","script_version":"7.1.1","2":"7.1.1","version_comment":"* renamed variable `g:sw_autocomplete_cache_dir` to `g:sw_cache`\r\n* fixed issue #24","3":"* renamed variable `g:sw_autocomplete_cache_dir` to `g:sw_cache`\r\n* fixed issue #24","package":"vim-sql-workbench.tar.gz","4":"vim-sql-workbench.tar.gz","src_id":"25482","5":"25482","creation_date":"1502048894","6":"1502048894"},{"0":"5081","vim_version":"7.0","1":"7.0","script_version":"7.1","2":"7.1","version_comment":"* fixed issue #23\r\n* added `exit` event for the sql buffer","3":"* fixed issue #23\r\n* added `exit` event for the sql buffer","package":"vim-sql-workbench.tar.gz","4":"vim-sql-workbench.tar.gz","src_id":"25462","5":"25462","creation_date":"1501531383","6":"1501531383"},{"0":"5081","vim_version":"7.0","1":"7.0","script_version":"7.0","2":"7.0","version_comment":"* profiles are automatically parsed\r\n* revamped autocomplete: no more commands needed (just set the report option,\r\nsee the `schema report` section from the documentation)\r\n* based tables metadata on the schema report generated by `WbSchemaReport`\r\n* added the `report` and `use-report` option to the profiles\r\n* added events in the sql buffer (`new_instance` and `profile_changed`)\r\n* added the possibility to share a buffer connection (see\r\n`SWSqlBufferShareConnection`)\r\n* added the possibility to go to the reference source in a result set (see the\r\n`SWSqlForeignKey` command)\r\n* removed the `SWSqlAutocomplete...` commands (not necessary anymore)\r\n* in the db explorer added references tree (see `Referenced by` and\r\n`References` options)\r\n* added the `` shortcut in the result set window (will\r\nrefresh the currently selected result set)","3":"* profiles are automatically parsed\r\n* revamped autocomplete: no more commands needed (just set the report option,\r\nsee the `schema report` section from the documentation)\r\n* based tables metadata on the schema report generated by `WbSchemaReport`\r\n* added the `report` and `use-report` option to the profiles\r\n* added events in the sql buffer (`new_instance` and `profile_changed`)\r\n* added the possibility to share a buffer connection (see\r\n`SWSqlBufferShareConnection`)\r\n* added the possibility to go to the reference source in a result set (see the\r\n`SWSqlForeignKey` command)\r\n* removed the `SWSqlAutocomplete...` commands (not necessary anymore)\r\n* in the db explorer added references tree (see `Referenced by` and\r\n`References` options)\r\n* added the `` shortcut in the result set window (will\r\nrefresh the currently selected result set)","package":"vim-sql-workbench.tar.gz","4":"vim-sql-workbench.tar.gz","src_id":"25455","5":"25455","creation_date":"1501182618","6":"1501182618"},{"0":"5081","vim_version":"7.4","1":"7.4","script_version":"6.3","2":"6.3","version_comment":"* now if you set the g:sw_config_dir, this is also sent to `SQL Workbench\/J` (please note that this only works now with build 121.4 and more)\r\n* better folding of the resultsets\r\n* added the possibility to refresh a resultset (see `SWSqlRefreshResultSet`)\r\n* added the possibility to delete a resultset from the resultsets window (see `SWSqlDeleteResultSet`)","3":"* now if you set the g:sw_config_dir, this is also sent to `SQL Workbench\/J` (please note that this only works now with build 121.4 and more)\r\n* better folding of the resultsets\r\n* added the possibility to refresh a resultset (see `SWSqlRefreshResultSet`)\r\n* added the possibility to delete a resultset from the resultsets window (see `SWSqlDeleteResultSet`)","package":"vim-sql-workbench.tar.gz","4":"vim-sql-workbench.tar.gz","src_id":"24815","5":"24815","creation_date":"1482515180","6":"1482515180"},{"0":"5081","vim_version":"8.0","1":"8.0","script_version":"6.2.1","2":"6.2.1","version_comment":"* minor bug fix","3":"* minor bug fix","package":"vim-sql-workbench.tar.gz","4":"vim-sql-workbench.tar.gz","src_id":"24698","5":"24698","creation_date":"1478043272","6":"1478043272"},{"0":"5081","vim_version":"8.0","1":"8.0","script_version":"6.2","2":"6.2","version_comment":"* added caching for the database explorer\r\n* added folding for the database explorer columns\r\n* added the possibility to kill the current statement\r\n* several fixed when working with channels\r\n* fixed a bug in integration with airline\r\n* merging the pull request 1","3":"* added caching for the database explorer\r\n* added folding for the database explorer columns\r\n* added the possibility to kill the current statement\r\n* several fixed when working with channels\r\n* fixed a bug in integration with airline\r\n* merging the pull request 1","package":"vim-sql-workbench.tar.gz","4":"vim-sql-workbench.tar.gz","src_id":"24697","5":"24697","creation_date":"1478027962","6":"1478027962"},{"0":"5081","vim_version":"8.0","1":"8.0","script_version":"6.1","2":"6.1","version_comment":"This version will break the compatibility with VIM 7. So, before installing\r\nthis new version, please upgrade to VIM 8.\r\n\r\nChanges:\r\n\r\n* fixed the tutorial in the documentation\r\n* added support for neovim\r\n* added events for the database explorer\r\n* added the filter data option for the database explorer objects\r\n* beffer hiding of the empty lines in resultsets with columns hidden\r\n* dropped the support for variables (you should only use `wbvardef` from SQL Workbench)\r\n* now the database explorer will not open by default the first tab (you have to specify which tab you want to open, once the database explorer is connected to a DBMS)\r\n","3":"This version will break the compatibility with VIM 7. So, before installing\r\nthis new version, please upgrade to VIM 8.\r\n\r\nChanges:\r\n\r\n* fixed the tutorial in the documentation\r\n* added support for neovim\r\n* added events for the database explorer\r\n* added the filter data option for the database explorer objects\r\n* beffer hiding of the empty lines in resultsets with columns hidden\r\n* dropped the support for variables (you should only use `wbvardef` from SQL Workbench)\r\n* now the database explorer will not open by default the first tab (you have to specify which tab you want to open, once the database explorer is connected to a DBMS)\r\n","package":"vim-sql-workbench.tar.gz","4":"vim-sql-workbench.tar.gz","src_id":"24572","5":"24572","creation_date":"1475177267","6":"1475177267"},{"0":"5081","vim_version":"7.4","1":"7.4","script_version":"6.0","2":"6.0","version_comment":"This version will break the compatibility with VIM 7. So, before installing\r\nthis new version, please upgrade to VIM 8.\r\n\r\nChanges:\r\n\r\n* vim8 required\r\n* python not needed anymore\r\n* every operation is now aynchronous\r\n* added the possibility to add a custom panel to an existing tab in the dbexplorer\r\n* fixed the search which was not working\r\n* eliminated the possibility to select columns to display in search (now you can use anyway :SWSqlShoOnlyColumns command)\r\n* logging the interaction with SQL Workbench\/J\r\n* added a timer for commands being executed using vim8 timers\r\n* now each buffer has its own connection to the DBMS (this means that each buffer has it\\'s own transaction, also)\r\n* added the possibility to disconnect a buffer from SQL Workbench\/J\r\n* integraton with CtrlP\r\n* integration with Airline\r\n* added the possibility to display the current connection in the status line\r\n* added the possibility to check all connected buffers to the DBMS (see SWSqlShowActiveConnections command)\r\n* removed the support for the sessions (it was not that usefull anyway)\r\n* improved the filtering\r\n* now each buffer has it\\'s own resultset\r\n* added the possibility to clear the resultsets for one buffer or for all at once (see SWSqlWipeoutResultsSets command)\r\n* added the possibility to open the resultset window without executing any command\r\n* added SWSqlGetSqlCount (which will return the number of rows of the current sql)\r\n* removed commands: SWDbExplorerRestore, SWSqlConnectToServer, SWSqlBufferRestore\r\n* new commands: SWSqlBufferConnect, SWSqlBufferDisconnect, SWSqlGetSqlCount, SWSqlGetObjRows, SWSqlShowActiveConnections, SWSqlShoLog, SWSqlShowLastResultset\r\n* new options: sw_log_to_file, sw_command_timer\r\n* removed options: sw_search_default_result_columns\r\n* added a default shortcut to execute a macro\r\n* added a default shortcut to get the number of rows for the current sql\r\n","3":"This version will break the compatibility with VIM 7. So, before installing\r\nthis new version, please upgrade to VIM 8.\r\n\r\nChanges:\r\n\r\n* vim8 required\r\n* python not needed anymore\r\n* every operation is now aynchronous\r\n* added the possibility to add a custom panel to an existing tab in the dbexplorer\r\n* fixed the search which was not working\r\n* eliminated the possibility to select columns to display in search (now you can use anyway :SWSqlShoOnlyColumns command)\r\n* logging the interaction with SQL Workbench\/J\r\n* added a timer for commands being executed using vim8 timers\r\n* now each buffer has its own connection to the DBMS (this means that each buffer has it\\'s own transaction, also)\r\n* added the possibility to disconnect a buffer from SQL Workbench\/J\r\n* integraton with CtrlP\r\n* integration with Airline\r\n* added the possibility to display the current connection in the status line\r\n* added the possibility to check all connected buffers to the DBMS (see SWSqlShowActiveConnections command)\r\n* removed the support for the sessions (it was not that usefull anyway)\r\n* improved the filtering\r\n* now each buffer has it\\'s own resultset\r\n* added the possibility to clear the resultsets for one buffer or for all at once (see SWSqlWipeoutResultsSets command)\r\n* added the possibility to open the resultset window without executing any command\r\n* added SWSqlGetSqlCount (which will return the number of rows of the current sql)\r\n* removed commands: SWDbExplorerRestore, SWSqlConnectToServer, SWSqlBufferRestore\r\n* new commands: SWSqlBufferConnect, SWSqlBufferDisconnect, SWSqlGetSqlCount, SWSqlGetObjRows, SWSqlShowActiveConnections, SWSqlShoLog, SWSqlShowLastResultset\r\n* new options: sw_log_to_file, sw_command_timer\r\n* removed options: sw_search_default_result_columns\r\n* added a default shortcut to execute a macro\r\n* added a default shortcut to get the number of rows for the current sql\r\n","package":"vim-sql-workbench.tar.gz","4":"vim-sql-workbench.tar.gz","src_id":"24561","5":"24561","creation_date":"1474826009","6":"1474826009"},{"0":"5081","vim_version":"7.0","1":"7.0","script_version":"5.2.2","2":"5.2.2","version_comment":"* Added the SWSqlExecuteMacro command\r\n* Changed the trigger sources command (works with `SQL Workbench\/J` build 119\r\nand up)\r\n* Updated to work with `SQL Workbench\/J` build 119\r\n* Added highlight in the resultset window for Oracle errors\r\n* Added the possibility to save the resultsets (see `SWSqlWipeoutResultsSets`\r\ncommand)","3":"* Added the SWSqlExecuteMacro command\r\n* Changed the trigger sources command (works with `SQL Workbench\/J` build 119\r\nand up)\r\n* Updated to work with `SQL Workbench\/J` build 119\r\n* Added highlight in the resultset window for Oracle errors\r\n* Added the possibility to save the resultsets (see `SWSqlWipeoutResultsSets`\r\ncommand)","package":"vim-sql-workbench.tar.gz","4":"vim-sql-workbench.tar.gz","src_id":"24345","5":"24345","creation_date":"1466689406","6":"1466689406"},{"0":"5081","vim_version":"7.0","1":"7.0","script_version":"5.2.1","2":"5.2.1","version_comment":"* better header display for resultsets\r\n* better folding\r\n* now the command which generated a resultset is displayed in the header","3":"* better header display for resultsets\r\n* better folding\r\n* now the command which generated a resultset is displayed in the header","package":"vim-sql-workbench.tar.gz","4":"vim-sql-workbench.tar.gz","src_id":"24064","5":"24064","creation_date":"1457119597","6":"1457119597"},{"0":"5081","vim_version":"7.0","1":"7.0","script_version":"5.2","2":"5.2","version_comment":"* hightlight the resultsets headers (in dbexplorer and sql window)\r\n* possibility to toggle form display in the dbexplorer (see the `SWDbExplorerToggleFormDisplay` command)\r\n* fixed some bugs in the filtering of the rows\r\n* improved the filtering and the hiding of the columns (faster now)\r\n* added the folds in the resultset window (each resulset can be folded now)","3":"* hightlight the resultsets headers (in dbexplorer and sql window)\r\n* possibility to toggle form display in the dbexplorer (see the `SWDbExplorerToggleFormDisplay` command)\r\n* fixed some bugs in the filtering of the rows\r\n* improved the filtering and the hiding of the columns (faster now)\r\n* added the folds in the resultset window (each resulset can be folded now)","package":"vim-sql-workbench.tar.gz","4":"vim-sql-workbench.tar.gz","src_id":"24061","5":"24061","creation_date":"1457038195","6":"1457038195"},{"0":"5081","vim_version":"7.0","1":"7.0","script_version":"5.1","2":"5.1","version_comment":"* possibility to autocomplete server ports\r\n* better display of results for asynchronious results\r\n* better delimiting of the resultsets\r\n* the resultsets are not displayed continous as long as the results window is\r\n  opened\r\n* added option to switch to results tab or not\r\n* added support to display resultsets one next to another (not implemented\r\n  yet)\r\n* added filtering of the resultsets (see the `SWSqlFilterColumn`,\r\n  `SWSqlUnfilterColumn` and `SWSqlRemoveAllFilters` commands)\r\n* added the possibility to hide and show columns (see the\r\n  `SWSqlShowAllColumns`, `SWSqlShowOnlyColumn`, `SWSqlShowOnlyColumns`,\r\n`SWSqlShowColumn` and `SWSqlHideColumn` commands)\r\n* better interactivity with the `SQL Workbench\/J` server","3":"* possibility to autocomplete server ports\r\n* better display of results for asynchronious results\r\n* better delimiting of the resultsets\r\n* the resultsets are not displayed continous as long as the results window is\r\n  opened\r\n* added option to switch to results tab or not\r\n* added support to display resultsets one next to another (not implemented\r\n  yet)\r\n* added filtering of the resultsets (see the `SWSqlFilterColumn`,\r\n  `SWSqlUnfilterColumn` and `SWSqlRemoveAllFilters` commands)\r\n* added the possibility to hide and show columns (see the\r\n  `SWSqlShowAllColumns`, `SWSqlShowOnlyColumn`, `SWSqlShowOnlyColumns`,\r\n`SWSqlShowColumn` and `SWSqlHideColumn` commands)\r\n* better interactivity with the `SQL Workbench\/J` server","package":"vim-sql-workbench.tar.gz","4":"vim-sql-workbench.tar.gz","src_id":"24032","5":"24032","creation_date":"1456129511","6":"1456129511"},{"0":"5081","vim_version":"7.0","1":"7.0","script_version":"5.0.1","2":"5.0.1","version_comment":"* Added a short tutorial in the documentation","3":"* Added a short tutorial in the documentation","package":"vim-sql-workbench.tar.gz","4":"vim-sql-workbench.tar.gz","src_id":"23749","5":"23749","creation_date":"1448221956","6":"1448221956"},{"0":"5081","vim_version":"7.0","1":"7.0","script_version":"5.0","2":"5.0","version_comment":"* Use the `SQL Workbench\/J` profiling instead of the profiling generated in `sqlwbserver`\r\n* Use the `SQL Workbench\/J` interactivity. This means: \r\n  * the possibility to use `$[?var]` parameters or `$[&var]` parameters (see http:\/\/www.sql-workbench.net\/manual\/using-variables.html)\r\n  * possible to have profiles without the password being saved in the profile (see http:\/\/www.sql-workbench.net\/manual\/profiles.html#profile-workbench-settings)\r\n  * possible to have profiles without the username being specified int the profile (see http:\/\/www.sql-workbench.net\/manual\/profiles.html#profile-workbench-settings)\r\n  * possible to have confirmation for data editing (see http:\/\/www.sql-workbench.net\/manual\/options.html#options-data-edit)\r\n* renamed the `sqlworkbench` to `sqlworkbench.py`\r\n* moved all `python` resources in the `resources\/py` folder\r\n* added a check to return a nice error if you try to run an sql statement from a non sql buffer\r\n* fixed the database explorer (checks before each command that a connection exists and if not opens a new one)\r\n\r\n\r\n`sqlworkbench.py` is not compatible with `SQL Workbench\/J` prior to build 118. To use build 117 and before you have to start `sqlworkbench.py` with the `-O 1` parameter ","3":"* Use the `SQL Workbench\/J` profiling instead of the profiling generated in `sqlwbserver`\r\n* Use the `SQL Workbench\/J` interactivity. This means: \r\n  * the possibility to use `$[?var]` parameters or `$[&var]` parameters (see http:\/\/www.sql-workbench.net\/manual\/using-variables.html)\r\n  * possible to have profiles without the password being saved in the profile (see http:\/\/www.sql-workbench.net\/manual\/profiles.html#profile-workbench-settings)\r\n  * possible to have profiles without the username being specified int the profile (see http:\/\/www.sql-workbench.net\/manual\/profiles.html#profile-workbench-settings)\r\n  * possible to have confirmation for data editing (see http:\/\/www.sql-workbench.net\/manual\/options.html#options-data-edit)\r\n* renamed the `sqlworkbench` to `sqlworkbench.py`\r\n* moved all `python` resources in the `resources\/py` folder\r\n* added a check to return a nice error if you try to run an sql statement from a non sql buffer\r\n* fixed the database explorer (checks before each command that a connection exists and if not opens a new one)\r\n\r\n\r\n`sqlworkbench.py` is not compatible with `SQL Workbench\/J` prior to build 118. To use build 117 and before you have to start `sqlworkbench.py` with the `-O 1` parameter ","package":"vim-sql-workbench.tar.gz","4":"vim-sql-workbench.tar.gz","src_id":"23740","5":"23740","creation_date":"1447875950","6":"1447875950"},{"0":"5081","vim_version":"7.0","1":"7.0","script_version":"4.0.2","2":"4.0.2","version_comment":"* Nicer error when executing operation in a non workbench buffer\r\n* Removed the  shortcut in the buffer results\r\n* fixed the sqlwbserver to work with h2 databases\r\n","3":"* Nicer error when executing operation in a non workbench buffer\r\n* Removed the  shortcut in the buffer results\r\n* fixed the sqlwbserver to work with h2 databases\r\n","package":"vim-sql-workbench.tar.gz","4":"vim-sql-workbench.tar.gz","src_id":"23691","5":"23691","creation_date":"1446064486","6":"1446064486"},{"0":"5081","vim_version":"7.0","1":"7.0","script_version":"4.0.1","2":"4.0.1","version_comment":"* made the change_tab function public (this means it is now possible to create commands using this function)\r\n* fixed a display results bug\r\n* fixed the utf-8 characters in the results tab\r\n* added the `package status` in the Oracle packages\r\n* added the `-l` option in the sqlwbserver (create a file with detailed debug informations about the requests to the server)","3":"* made the change_tab function public (this means it is now possible to create commands using this function)\r\n* fixed a display results bug\r\n* fixed the utf-8 characters in the results tab\r\n* added the `package status` in the Oracle packages\r\n* added the `-l` option in the sqlwbserver (create a file with detailed debug informations about the requests to the server)","package":"vim-sql-workbench.tar.gz","4":"vim-sql-workbench.tar.gz","src_id":"23620","5":"23620","creation_date":"1443381264","6":"1443381264"},{"0":"5081","vim_version":"7.0","1":"7.0","script_version":"4.0","2":"4.0","version_comment":"* made it compatible with latest SQL Workbench\/J build\r\n* now postgresql works by default (no need for another dbexplorer)\r\n* added the possibility to have dbexplorers options per DBMS type\r\n* added the possibility to have a vimscript function called by the dbexplorer\r\n* added some profiling\r\n* better display of error messages\r\n* improved the sqlwbserver (now it should quit gracefully, without errors)","3":"* made it compatible with latest SQL Workbench\/J build\r\n* now postgresql works by default (no need for another dbexplorer)\r\n* added the possibility to have dbexplorers options per DBMS type\r\n* added the possibility to have a vimscript function called by the dbexplorer\r\n* added some profiling\r\n* better display of error messages\r\n* improved the sqlwbserver (now it should quit gracefully, without errors)","package":"vim-sql-workbench.tar.gz","4":"vim-sql-workbench.tar.gz","src_id":"23535","5":"23535","creation_date":"1440100348","6":"1440100348"},{"0":"5081","vim_version":"7.0","1":"7.0","script_version":"3.3","2":"3.3","version_comment":"* Added the g:sw_switch_to_results_tab option (whether or not to switch to results tab after a command)\r\n* Improvements in the sqlwbserver python console\r\n* Improved documentation, using vim-tools (http:\/\/peterodding.com\/code\/vim\/tools)\r\n* Changed the handling of the user defined variables (move towards using WbVarDef)\r\n* Possibility to send command to the DBMS from vim command line. So, now you can have shortcuts for sql queries, like wbdisplay record\r\n* Autocomplete for the WbConnect command","3":"* Added the g:sw_switch_to_results_tab option (whether or not to switch to results tab after a command)\r\n* Improvements in the sqlwbserver python console\r\n* Improved documentation, using vim-tools (http:\/\/peterodding.com\/code\/vim\/tools)\r\n* Changed the handling of the user defined variables (move towards using WbVarDef)\r\n* Possibility to send command to the DBMS from vim command line. So, now you can have shortcuts for sql queries, like wbdisplay record\r\n* Autocomplete for the WbConnect command","package":"vim-sql-workbench.tar.gz","4":"vim-sql-workbench.tar.gz","src_id":"23518","5":"23518","creation_date":"1439668328","6":"1439668328"},{"0":"5081","vim_version":"7.0","1":"7.0","script_version":"3.2.2","2":"3.2.2","version_comment":"Small fix: fixed the variables (they were not working with standard modifiers)","3":"Small fix: fixed the variables (they were not working with standard modifiers)","package":"vim-sql-workbench.tar.gz","4":"vim-sql-workbench.tar.gz","src_id":"23511","5":"23511","creation_date":"1439023695","6":"1439023695"},{"0":"5081","vim_version":"7.0","1":"7.0","script_version":"3.2.1","2":"3.2.1","version_comment":"Just a minor release: \r\n* Fixed issue #6","3":"Just a minor release: \r\n* Fixed issue #6","package":"vim-sql-workbench.tar.gz","4":"vim-sql-workbench.tar.gz","src_id":"23502","5":"23502","creation_date":"1438714556","6":"1438714556"},{"0":"5081","vim_version":"7.0","1":"7.0","script_version":"3.2","2":"3.2","version_comment":"* Added the possibility to have multiple columns replaced in the database explorer\r\n* Updated the documentation\r\n* Added the resources\/dbexplorer-postgresql.vim database explorer for usage with PostgreSQL","3":"* Added the possibility to have multiple columns replaced in the database explorer\r\n* Updated the documentation\r\n* Added the resources\/dbexplorer-postgresql.vim database explorer for usage with PostgreSQL","package":"vim-sql-workbench.tar.gz","4":"vim-sql-workbench.tar.gz","src_id":"23224","5":"23224","creation_date":"1429819631","6":"1429819631"},{"0":"5081","vim_version":"7.0","1":"7.0","script_version":"3.1.1","2":"3.1.1","version_comment":"* fixed issue #9","3":"* fixed issue #9","package":"vim-sql-workbench.tar.gz","4":"vim-sql-workbench.tar.gz","src_id":"23200","5":"23200","creation_date":"1429511168","6":"1429511168"},{"0":"5081","vim_version":"7.0","1":"7.0","script_version":"3.1","2":"3.1","version_comment":"* Added the `SWDbExplorerReconnect` command (for reconnecting a dbexplorer timeout session, where you cannot do `wbconnect`)\r\n* Changed the autocomplete from omni function to userfunction (use `` instead of `` for intellisense autocomplete)\r\n* Fixed github #7 issue\r\n* Set the maximum number of rows to 100 for dbexplorer to the connection lever rather then to each command level\r\n* Fixed github #9 issue","3":"* Added the `SWDbExplorerReconnect` command (for reconnecting a dbexplorer timeout session, where you cannot do `wbconnect`)\r\n* Changed the autocomplete from omni function to userfunction (use `` instead of `` for intellisense autocomplete)\r\n* Fixed github #7 issue\r\n* Set the maximum number of rows to 100 for dbexplorer to the connection lever rather then to each command level\r\n* Fixed github #9 issue","package":"vim-sql-workbench.tar.gz","4":"vim-sql-workbench.tar.gz","src_id":"23181","5":"23181","creation_date":"1429214922","6":"1429214922"},{"0":"5081","vim_version":"7.0","1":"7.0","script_version":"3.0","2":"3.0","version_comment":"* Switch to using sqlwbserver for improved performance\r\n* Lots of new commands (like SWSqlAutocompleteLoad or SWSqlAutocompletePersist).\r\n* added python dependency (needed for using sqlwbserver)\r\n* Some commands became obsolete (like SWSqlOpen)\r\n* fixed issue #4\r\n\r\n","3":"* Switch to using sqlwbserver for improved performance\r\n* Lots of new commands (like SWSqlAutocompleteLoad or SWSqlAutocompletePersist).\r\n* added python dependency (needed for using sqlwbserver)\r\n* Some commands became obsolete (like SWSqlOpen)\r\n* fixed issue #4\r\n\r\n","package":"vim-sql-workbench.tar.gz","4":"vim-sql-workbench.tar.gz","src_id":"23115","5":"23115","creation_date":"1427917619","6":"1427917619"},{"0":"5081","vim_version":"7.0","1":"7.0","script_version":"2.0","2":"2.0","version_comment":"* Fixed #2 issue\r\n* Added transactions","3":"* Fixed #2 issue\r\n* Added transactions","package":"vim-sql-workbench.tar.gz","4":"vim-sql-workbench.tar.gz","src_id":"23067","5":"23067","creation_date":"1426797142","6":"1426797142"},{"0":"5081","vim_version":"7.0","1":"7.0","script_version":"1.3","2":"1.3","version_comment":"The autocomplete is now persisted on the hard drive. This means that it can be loaded automatically every time you open a buffer for a given profile.\r\n\r\nDeprecated methods:\r\n\r\n    SWSqlAutocompleteSetDefault\r\n    SWSqlAutocompleteWithDefault\r\n\r\n","3":"The autocomplete is now persisted on the hard drive. This means that it can be loaded automatically every time you open a buffer for a given profile.\r\n\r\nDeprecated methods:\r\n\r\n    SWSqlAutocompleteSetDefault\r\n    SWSqlAutocompleteWithDefault\r\n\r\n","package":"vim-sql-workbench.tar.gz","4":"vim-sql-workbench.tar.gz","src_id":"22993","5":"22993","creation_date":"1425847789","6":"1425847789"},{"0":"5081","vim_version":"7.0","1":"7.0","script_version":"1.2","2":"1.2","version_comment":"* Added variables (parameter substitution when sending sql queries to the DBMS). \r\nWhen sending a query to the DBMS, you can use named parameters. For example \"select * from table where name = :name\". You will be asked to provide the value of the name parameter","3":"* Added variables (parameter substitution when sending sql queries to the DBMS). \r\nWhen sending a query to the DBMS, you can use named parameters. For example \"select * from table where name = :name\". You will be asked to provide the value of the name parameter","package":"vim-sql-workbench.tar.gz","4":"vim-sql-workbench.tar.gz","src_id":"22984","5":"22984","creation_date":"1425763252","6":"1425763252"},{"0":"5081","vim_version":"7.0","1":"7.0","script_version":"1.1.3","2":"1.1.3","version_comment":"* Solved github issue 5 (https:\/\/github.com\/cosminadrianpopescu\/vim-sql-workbench\/issues\/5)","3":"* Solved github issue 5 (https:\/\/github.com\/cosminadrianpopescu\/vim-sql-workbench\/issues\/5)","package":"vim-sql-workbench.tar.gz","4":"vim-sql-workbench.tar.gz","src_id":"22970","5":"22970","creation_date":"1425235685","6":"1425235685"},{"0":"5081","vim_version":"7.0","1":"7.0","script_version":"1.1.2","2":"1.1.2","version_comment":"* Improved autocomplete (updated some regex patterns and fixed some small bugs)\r\n* Updated the vim help documentation\r\n* Added the g:sw_delete option","3":"* Improved autocomplete (updated some regex patterns and fixed some small bugs)\r\n* Updated the vim help documentation\r\n* Added the g:sw_delete option","package":"vim-sql-workbench.tar.gz","4":"vim-sql-workbench.tar.gz","src_id":"22959","5":"22959","creation_date":"1425150815","6":"1425150815"},{"0":"5081","vim_version":"7.0","1":"7.0","script_version":"1.1.1","2":"1.1.1","version_comment":"Fixed issue #3 (see github). For the moment please use SQL Workbench\/J build 116 and prior. There seems to be a problem with build 117, but I cannot reproduce it yet. ","3":"Fixed issue #3 (see github). For the moment please use SQL Workbench\/J build 116 and prior. There seems to be a problem with build 117, but I cannot reproduce it yet. ","package":"vim-sql-workbench.tar.gz","4":"vim-sql-workbench.tar.gz","src_id":"22863","5":"22863","creation_date":"1422993435","6":"1422993435"},{"0":"5081","vim_version":"7.0","1":"7.0","script_version":"1.1","2":"1.1","version_comment":"Added asynchronous functionality. Now you can run your commands asynchronous. \r\nFixed small bugs","3":"Added asynchronous functionality. Now you can run your commands asynchronous. \r\nFixed small bugs","package":"vim-sql-workbench.tar.gz","4":"vim-sql-workbench.tar.gz","src_id":"22807","5":"22807","creation_date":"1421614574","6":"1421614574"},{"0":"5081","vim_version":"7.0","1":"7.0","script_version":"1.0.2","2":"1.0.2","version_comment":"Fixed the issue #1 on github + fixed some autocomplete bugs","3":"Fixed the issue #1 on github + fixed some autocomplete bugs","package":"vim-sql-workbench.tar.gz","4":"vim-sql-workbench.tar.gz","src_id":"22780","5":"22780","creation_date":"1421047961","6":"1421047961"},{"0":"5081","vim_version":"7.0","1":"7.0","script_version":"1.0.1","2":"1.0.1","version_comment":"Fixed some autocomplete bugs","3":"Fixed some autocomplete bugs","package":"vim-sqlworkbench.tar.gz","4":"vim-sqlworkbench.tar.gz","src_id":"22771","5":"22771","creation_date":"1420835947","6":"1420835947"},{"0":"5081","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"vim-sqlworkbench.tar.gz","4":"vim-sqlworkbench.tar.gz","src_id":"22768","5":"22768","creation_date":"1420751852","6":"1420751852"}]},"5080":{"script_id":"5080","0":"5080","script_name":"MacDict","1":"MacDict","script_type":"utility","2":"utility","summary":"Search your system dictionary from within Vim","3":"Search your system dictionary from within Vim","description":"This is a Vim plugin to search for a word in your system dictionary.\r\n\r\nIt currently only supports OSX.\r\n\r\nYou can check it out on GitHub at https:\/\/github.com\/jonhiggs\/MacDict.vim.\r\n\r\n","4":"This is a Vim plugin to search for a word in your system dictionary.\r\n\r\nIt currently only supports OSX.\r\n\r\nYou can check it out on GitHub at https:\/\/github.com\/jonhiggs\/MacDict.vim.\r\n\r\n","install_details":"Drop it into your bundle\/ directory.","5":"Drop it into your bundle\/ directory.","first_name":"Jon","6":"Jon","last_name":"Higgs","7":"Higgs","releases":[{"0":"5080","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"MacDict.vim-0.1.tar.gz","4":"MacDict.vim-0.1.tar.gz","src_id":"22766","5":"22766","creation_date":"1420697992","6":"1420697992"}]},"5079":{"script_id":"5079","0":"5079","script_name":"Darcula Color Scheme","1":"Darcula Color Scheme","script_type":"color scheme","2":"color scheme","summary":"Dark color scheme that is easy on the eyes","3":"Dark color scheme that is easy on the eyes","description":"Accurate Darcula color scheme for the VIM editor. Works well with CoffeeScript projects. Can be used in 256 color mode.\r\n\r\nhttps:\/\/github.com\/blueshirts\/darcula","4":"Accurate Darcula color scheme for the VIM editor. Works well with CoffeeScript projects. Can be used in 256 color mode.\r\n\r\nhttps:\/\/github.com\/blueshirts\/darcula","install_details":"Copy darcula.vim into ~\/.vim\/colors\/ (Unix) or vimfiles\/colors\/ (Windows).\r\n\r\nType \"colorscheme darcula\" into your vimrc file.\r\n\r\nCoffeeScript Configuration\r\n\r\nAdd the following content to the .vim\/after\/syntax\/coffee\/coffee.vim file. This configuration is required with most VIM CoffeeScript syntax highlighters in order to properly color the '@' (this) symbol.\r\n\r\nhi clear coffeeParens\r\nhi coffeeParens NONE\r\nsyn clear coffeeParens\r\n\r\nhi clear coffeeSpecialIdent\r\nhi coffeeSpecialIdent NONE\r\nsyn clear coffeeSpecialIdent\r\n\r\nhi clear coffeeCurlies\r\nhi coffeeCoffeeCurlies NONE\r\nsyn clear coffeeCurlies\r\n\r\n\" Highlight the this symbol.\r\nsyn match coffeeThis \"\\v\\@\"\r\nhi def link coffeeThis Keyword","5":"Copy darcula.vim into ~\/.vim\/colors\/ (Unix) or vimfiles\/colors\/ (Windows).\r\n\r\nType \"colorscheme darcula\" into your vimrc file.\r\n\r\nCoffeeScript Configuration\r\n\r\nAdd the following content to the .vim\/after\/syntax\/coffee\/coffee.vim file. This configuration is required with most VIM CoffeeScript syntax highlighters in order to properly color the '@' (this) symbol.\r\n\r\nhi clear coffeeParens\r\nhi coffeeParens NONE\r\nsyn clear coffeeParens\r\n\r\nhi clear coffeeSpecialIdent\r\nhi coffeeSpecialIdent NONE\r\nsyn clear coffeeSpecialIdent\r\n\r\nhi clear coffeeCurlies\r\nhi coffeeCoffeeCurlies NONE\r\nsyn clear coffeeCurlies\r\n\r\n\" Highlight the this symbol.\r\nsyn match coffeeThis \"\\v\\@\"\r\nhi def link coffeeThis Keyword","first_name":"Blue","6":"Blue","last_name":"Shirts","7":"Shirts","releases":[{"0":"5079","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"darcula.vim","4":"darcula.vim","src_id":"22765","5":"22765","creation_date":"1420690350","6":"1420690350"}]},"5078":{"script_id":"5078","0":"5078","script_name":"permut.vim","1":"permut.vim","script_type":"utility","2":"utility","summary":"Plugin for swapping text columns separated by arbitrary character.","3":"Plugin for swapping text columns separated by arbitrary character.","description":"This permut.vim plugin allows to swap two columns of text in a selected range of lines.  The columns can be separated by any character (not present in text). By default, the column_separator is '|' character. The user can enter any kind of separator character. The more usual separator character encountered are the ',' or ';' or ':' characters.\r\n\r\nHere is the syntax of the Permut command:\r\n\r\n    :[range] Permut   [column_separator]\r\n\r\nExample 1 with default column separator:\r\n\r\n    1  ab cd | ef gh | ijk lmn | opq rst | uv wx | yz\r\n    2  ab cd | ef gh | ijk lmn | opq rst | uv wx | yz\r\n    3  ab cd | ef gh | ijk lmn | opq rst | uv wx | yz\r\n    4  ab cd | ef gh | ijk lmn | opq rst | uv wx | yz\r\n    5  ab cd | ef gh | ijk lmn | opq rst | uv wx | yz\r\n    6  ab cd | ef gh | ijk lmn | opq rst | uv wx | yz\r\n    7  ab cd | ef gh | ijk lmn | opq rst | uv wx | yz\r\n\r\n    :1,7 Permut 1 3\r\n\r\n    1  ijk lmn | ef gh | ab cd | opq rst | uv wx | yz\r\n    2  ijk lmn | ef gh | ab cd | opq rst | uv wx | yz\r\n    3  ijk lmn | ef gh | ab cd | opq rst | uv wx | yz\r\n    4  ijk lmn | ef gh | ab cd | opq rst | uv wx | yz\r\n    5  ijk lmn | ef gh | ab cd | opq rst | uv wx | yz\r\n    6  ijk lmn | ef gh | ab cd | opq rst | uv wx | yz\r\n    7  ijk lmn | ef gh | ab cd | opq rst | uv wx | yz\r\n\r\nFor more detailed documentation, see the README on GitHub:\r\nhttps:\/\/github.com\/jlemetay\/permut\r\n","4":"This permut.vim plugin allows to swap two columns of text in a selected range of lines.  The columns can be separated by any character (not present in text). By default, the column_separator is '|' character. The user can enter any kind of separator character. The more usual separator character encountered are the ',' or ';' or ':' characters.\r\n\r\nHere is the syntax of the Permut command:\r\n\r\n    :[range] Permut   [column_separator]\r\n\r\nExample 1 with default column separator:\r\n\r\n    1  ab cd | ef gh | ijk lmn | opq rst | uv wx | yz\r\n    2  ab cd | ef gh | ijk lmn | opq rst | uv wx | yz\r\n    3  ab cd | ef gh | ijk lmn | opq rst | uv wx | yz\r\n    4  ab cd | ef gh | ijk lmn | opq rst | uv wx | yz\r\n    5  ab cd | ef gh | ijk lmn | opq rst | uv wx | yz\r\n    6  ab cd | ef gh | ijk lmn | opq rst | uv wx | yz\r\n    7  ab cd | ef gh | ijk lmn | opq rst | uv wx | yz\r\n\r\n    :1,7 Permut 1 3\r\n\r\n    1  ijk lmn | ef gh | ab cd | opq rst | uv wx | yz\r\n    2  ijk lmn | ef gh | ab cd | opq rst | uv wx | yz\r\n    3  ijk lmn | ef gh | ab cd | opq rst | uv wx | yz\r\n    4  ijk lmn | ef gh | ab cd | opq rst | uv wx | yz\r\n    5  ijk lmn | ef gh | ab cd | opq rst | uv wx | yz\r\n    6  ijk lmn | ef gh | ab cd | opq rst | uv wx | yz\r\n    7  ijk lmn | ef gh | ab cd | opq rst | uv wx | yz\r\n\r\nFor more detailed documentation, see the README on GitHub:\r\nhttps:\/\/github.com\/jlemetay\/permut\r\n","install_details":"A simple way to install the permut vim plugin is to use [pathogen](https:\/\/github.com\/tpope\/vim-pathogen). Once this plugin manager is installed, you have just to run these commands:\r\n\r\n    cd ~\/.vim\/bundle\r\n    git clone git:\/\/github.com\/jlemetay\/permut.git\r\n\r\n","5":"A simple way to install the permut vim plugin is to use [pathogen](https:\/\/github.com\/tpope\/vim-pathogen). Once this plugin manager is installed, you have just to run these commands:\r\n\r\n    cd ~\/.vim\/bundle\r\n    git clone git:\/\/github.com\/jlemetay\/permut.git\r\n\r\n","first_name":"JY","6":"JY","last_name":"LM","7":"LM","releases":[{"0":"5078","vim_version":"7.0","1":"7.0","script_version":"0.2","2":"0.2","version_comment":"Take into account another additional text aligner plugin: vim-easy-align (https:\/\/github.com\/junegunn\/vim-easy-align) as suggested on site http:\/\/usevim.com\/2015\/01\/05\/permut\/","3":"Take into account another additional text aligner plugin: vim-easy-align (https:\/\/github.com\/junegunn\/vim-easy-align) as suggested on site http:\/\/usevim.com\/2015\/01\/05\/permut\/","package":"permut_0.2.tgz","4":"permut_0.2.tgz","src_id":"22809","5":"22809","creation_date":"1421684656","6":"1421684656"},{"0":"5078","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"permut-0.1.tgz","4":"permut-0.1.tgz","src_id":"22756","5":"22756","creation_date":"1420456860","6":"1420456860"}]},"5077":{"script_id":"5077","0":"5077","script_name":"vim-abaqus","1":"vim-abaqus","script_type":"ftplugin","2":"ftplugin","summary":"VIM filetype plugin for Abaqus","3":"VIM filetype plugin for Abaqus","description":"VIM filetype plugin for Abaqus FE solver.\r\n\r\nMain plugin features: \r\n- syntax highlighting \r\n- node\/element table folding \r\n- keyword completion\r\n- amplitude commands\r\n- many others useful features","4":"VIM filetype plugin for Abaqus FE solver.\r\n\r\nMain plugin features: \r\n- syntax highlighting \r\n- node\/element table folding \r\n- keyword completion\r\n- amplitude commands\r\n- many others useful features","install_details":"https:\/\/github.com\/gradzikb\/vim-abaqus","5":"https:\/\/github.com\/gradzikb\/vim-abaqus","first_name":"Bartosz","6":"Bartosz","last_name":"Gradzik","7":"Gradzik","releases":[{"0":"5077","vim_version":"7.0","1":"7.0","script_version":"1.1.0","2":"1.1.0","version_comment":"Update","3":"Update","package":"vim-abaqus-1.1.0.zip","4":"vim-abaqus-1.1.0.zip","src_id":"22853","5":"22853","creation_date":"1422697594","6":"1422697594"},{"0":"5077","vim_version":"7.4","1":"7.4","script_version":"1.0.0","2":"1.0.0","version_comment":"Initial upload","3":"Initial upload","package":"vim-abaqus-1.0.0.zip","4":"vim-abaqus-1.0.0.zip","src_id":"22749","5":"22749","creation_date":"1420191841","6":"1420191841"}]},"5076":{"script_id":"5076","0":"5076","script_name":"tex-syntax","1":"tex-syntax","script_type":"syntax","2":"syntax","summary":"Vim TeX syntax file","3":"Vim TeX syntax file","description":"# vim-tex-syntax\r\n\r\nThis is a rewrite of the default `syntax\/tex.vim` used for [TeX]\/[LaTeX],\r\nbecause I finally got fed-up with the default `syntax\/tex.vim` file. My main\r\ncomplaints were that syntax folding is painfully slow for large files and\r\ndoesn't work the way I want. Also spell checking checking missed many things I\r\nwanted checked (and erratically failed).\r\n\r\n## Features\r\n\r\n1. *Syntax folding.*\r\n   If you set `fdm=syntax`, the document will be folded like this:\r\n\r\n        +--  6 lines: \\documentclass[draft]{amsart}-------------\r\n        \\begin{document}\r\n        +-- 27 lines: \\title[Continuity theorem for Bernstein tr\r\n        +--169 lines: \\section{Introduction.}\\label{sxnIntro}---\r\n        +-- 12 lines: \\section{Continuity theorem.}\\label{sxnCT}\r\n        +--  3 lines: \\bibliographystyle{habbrv}----------------\r\n        \\end{document}\r\n\r\n     Additionally theorems, lemmas, proofs etc. are also folded, manual folds\r\n   can be added. Syntax folding is about 3 to 4 times faster than the default\r\n   syntax script shipped with Vim. This only make a difference if you edit\r\n   large files. On my system, a file with 15,000 lines (and multiple sections\r\n   \/ subsections \/ etc.) takes about 7 seconds to highlight and fold with this\r\n   script, and it takes about 27 with the Vim default syntax script. Both\r\n   scripts are snappy if folding is disabled, of course. If you plan on\r\n   editing large TeX\/LaTeX files and using syntax folding I recommend using\r\n   the [FastFold] plugin in addition to this script.\r\n\r\n\r\n2. *Spell checking.*\r\n   Most everything that should be spell checked is. Arguments of all commands\r\n   (except special commands in `g:tex_special_commands`) are spell checked,\r\n   and arguments of environments (except theorem like environments in\r\n   `g:tex_thm_envs`) are not spell checked.\r\n\r\n3. *Brace matching.*\r\n   Extra open braces in an environment will produce an error in the enclosing\r\n   `\\end{...}` statement. Extra closed braces are flagged. Braces denoting\r\n   command and script script arguments are highlighted differently.\r\n\r\n4. *Concealing Greek characters and Symbols.*\r\n   If you set `conceallevel` to `1` or `2` and are using UTF-8 encoding, then\r\n   commands like `\\alpha` or `\\nabla` will be shown as `α` or `∇`\r\n   respectively.\r\n\r\n## Configuration options.\r\n\r\n`g:tex_special_arg_commands`\r\n: Space separated list of commands with special arguments (e.g. `usepackage`).\r\n  Arguments of these commands will be colored and not spell checked.\r\n\r\n`g:tex_special_commands`\r\n: Space separated list of special commands (e.g. `large`). These will be\r\n  colored differently from other commands (but the arguments will not be\r\n  handled specially).\r\n\r\n`g:tex_section_commands`\r\n: Space separated list of sectioning commands (e.g. `chapter`).\r\n\r\n`g:tex_math_text_commands`\r\n: Space separated list of commands in math mode with text arguments (e.g.\r\n  `text`).\r\n\r\n`g:tex_thm_envs`\r\n: Space separated list of theorem like environments (e.g. `theorem`).\r\n  Arguments of these commands are spell checked (and not colored).\r\n\r\n`g:tex_math_envs`\r\n: Space separated list of environment names that start a math zone (e.g.\r\n  `equation` etc.),\r\n\r\n`g:tex_fold_envs`\r\n: Set this to a space separated list of environment names that should start a\r\n  fold.\r\n\r\n`g:tex_isk`\r\n: `iskeyword` option for [TeX]\/[LaTeX] files.\r\n\r\n## Additional syntax folds\r\n\r\nIn case the automatically created syntax folds created are not sufficient for\r\nyour purposes, you can adjust it manually in the following ways.\r\n\r\n1. The comment markers `%{{{` and `%}}}` can be used to create a fold.\r\n   The numbered versions `%{{{1`, `%}}}1` etc. are ignored.\r\n\r\n2. Section \/ subsection level folds can manually be started using\r\n   `%startsection`, `%startsubsection` or `%startsubsubsection`. (Similarly\r\n   for chapters).\r\n\r\n3. Section \/ subsection level folds can be manually closed using\r\n   using `%endsection`, `%endsubsection` or `%endsubsubsection`. (Similarly\r\n   for chapters)\r\n\r\n4. The front matter fold (that starts on the line after `\\begin{document}`)\r\n   usually ends when a section or chapter is started. If you want to end it\r\n   earlier, use the comment `%endfrontmatter`\r\n\r\n## Links\r\n\r\n* [Github page](https:\/\/github.com\/gi1242\/vim-tex-syntax)\r\n\r\n* [Gitlab page](https:\/\/gitlab.com\/gi1242\/vim-tex-syntax)\r\n\r\n* [Vim script page](http:\/\/www.vim.org\/scripts\/script.php?script_id=5076)\r\n\r\n[TeX]: http:\/\/en.wikipedia.org\/wiki\/TeX\r\n\r\n[LaTeX]: http:\/\/www.latex-project.org\r\n","4":"# vim-tex-syntax\r\n\r\nThis is a rewrite of the default `syntax\/tex.vim` used for [TeX]\/[LaTeX],\r\nbecause I finally got fed-up with the default `syntax\/tex.vim` file. My main\r\ncomplaints were that syntax folding is painfully slow for large files and\r\ndoesn't work the way I want. Also spell checking checking missed many things I\r\nwanted checked (and erratically failed).\r\n\r\n## Features\r\n\r\n1. *Syntax folding.*\r\n   If you set `fdm=syntax`, the document will be folded like this:\r\n\r\n        +--  6 lines: \\documentclass[draft]{amsart}-------------\r\n        \\begin{document}\r\n        +-- 27 lines: \\title[Continuity theorem for Bernstein tr\r\n        +--169 lines: \\section{Introduction.}\\label{sxnIntro}---\r\n        +-- 12 lines: \\section{Continuity theorem.}\\label{sxnCT}\r\n        +--  3 lines: \\bibliographystyle{habbrv}----------------\r\n        \\end{document}\r\n\r\n     Additionally theorems, lemmas, proofs etc. are also folded, manual folds\r\n   can be added. Syntax folding is about 3 to 4 times faster than the default\r\n   syntax script shipped with Vim. This only make a difference if you edit\r\n   large files. On my system, a file with 15,000 lines (and multiple sections\r\n   \/ subsections \/ etc.) takes about 7 seconds to highlight and fold with this\r\n   script, and it takes about 27 with the Vim default syntax script. Both\r\n   scripts are snappy if folding is disabled, of course. If you plan on\r\n   editing large TeX\/LaTeX files and using syntax folding I recommend using\r\n   the [FastFold] plugin in addition to this script.\r\n\r\n\r\n2. *Spell checking.*\r\n   Most everything that should be spell checked is. Arguments of all commands\r\n   (except special commands in `g:tex_special_commands`) are spell checked,\r\n   and arguments of environments (except theorem like environments in\r\n   `g:tex_thm_envs`) are not spell checked.\r\n\r\n3. *Brace matching.*\r\n   Extra open braces in an environment will produce an error in the enclosing\r\n   `\\end{...}` statement. Extra closed braces are flagged. Braces denoting\r\n   command and script script arguments are highlighted differently.\r\n\r\n4. *Concealing Greek characters and Symbols.*\r\n   If you set `conceallevel` to `1` or `2` and are using UTF-8 encoding, then\r\n   commands like `\\alpha` or `\\nabla` will be shown as `α` or `∇`\r\n   respectively.\r\n\r\n## Configuration options.\r\n\r\n`g:tex_special_arg_commands`\r\n: Space separated list of commands with special arguments (e.g. `usepackage`).\r\n  Arguments of these commands will be colored and not spell checked.\r\n\r\n`g:tex_special_commands`\r\n: Space separated list of special commands (e.g. `large`). These will be\r\n  colored differently from other commands (but the arguments will not be\r\n  handled specially).\r\n\r\n`g:tex_section_commands`\r\n: Space separated list of sectioning commands (e.g. `chapter`).\r\n\r\n`g:tex_math_text_commands`\r\n: Space separated list of commands in math mode with text arguments (e.g.\r\n  `text`).\r\n\r\n`g:tex_thm_envs`\r\n: Space separated list of theorem like environments (e.g. `theorem`).\r\n  Arguments of these commands are spell checked (and not colored).\r\n\r\n`g:tex_math_envs`\r\n: Space separated list of environment names that start a math zone (e.g.\r\n  `equation` etc.),\r\n\r\n`g:tex_fold_envs`\r\n: Set this to a space separated list of environment names that should start a\r\n  fold.\r\n\r\n`g:tex_isk`\r\n: `iskeyword` option for [TeX]\/[LaTeX] files.\r\n\r\n## Additional syntax folds\r\n\r\nIn case the automatically created syntax folds created are not sufficient for\r\nyour purposes, you can adjust it manually in the following ways.\r\n\r\n1. The comment markers `%{{{` and `%}}}` can be used to create a fold.\r\n   The numbered versions `%{{{1`, `%}}}1` etc. are ignored.\r\n\r\n2. Section \/ subsection level folds can manually be started using\r\n   `%startsection`, `%startsubsection` or `%startsubsubsection`. (Similarly\r\n   for chapters).\r\n\r\n3. Section \/ subsection level folds can be manually closed using\r\n   using `%endsection`, `%endsubsection` or `%endsubsubsection`. (Similarly\r\n   for chapters)\r\n\r\n4. The front matter fold (that starts on the line after `\\begin{document}`)\r\n   usually ends when a section or chapter is started. If you want to end it\r\n   earlier, use the comment `%endfrontmatter`\r\n\r\n## Links\r\n\r\n* [Github page](https:\/\/github.com\/gi1242\/vim-tex-syntax)\r\n\r\n* [Gitlab page](https:\/\/gitlab.com\/gi1242\/vim-tex-syntax)\r\n\r\n* [Vim script page](http:\/\/www.vim.org\/scripts\/script.php?script_id=5076)\r\n\r\n[TeX]: http:\/\/en.wikipedia.org\/wiki\/TeX\r\n\r\n[LaTeX]: http:\/\/www.latex-project.org\r\n","install_details":"Put tex.vim in ~\/.vim\/syntax\/tex.vim. Set fdm=syntax for folding.","5":"Put tex.vim in ~\/.vim\/syntax\/tex.vim. Set fdm=syntax for folding.","first_name":"gi1242","6":"gi1242","last_name":"gi1242","7":"gi1242","releases":[{"0":"5076","vim_version":"8.0","1":"8.0","script_version":"0.2","2":"0.2","version_comment":"Many bugfixes. Added conceal support","3":"Many bugfixes. Added conceal support","package":"tex-syntax.tgz","4":"tex-syntax.tgz","src_id":"26736","5":"26736","creation_date":"1567817149","6":"1567817149"},{"0":"5076","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"tex-syntax.tgz","4":"tex-syntax.tgz","src_id":"22735","5":"22735","creation_date":"1419655613","6":"1419655613"}]},"5075":{"script_id":"5075","0":"5075","script_name":"cf5-compile.vim","1":"cf5-compile.vim","script_type":"utility","2":"utility","summary":"Compile files right from vim.","3":"Compile files right from vim.","description":"Functions to compile\/link and run a single c\/cpp\/java\/..etc\r\nfile based programs. It's irreplaceable for small tests or \r\nexperiments.\r\n\r\nFor the most recent version check:\r\nhttps:\/\/github.com\/vishap\/vim_scripts\/blob\/master\/plugin\/cf5-compile.vim\r\n","4":"Functions to compile\/link and run a single c\/cpp\/java\/..etc\r\nfile based programs. It's irreplaceable for small tests or \r\nexperiments.\r\n\r\nFor the most recent version check:\r\nhttps:\/\/github.com\/vishap\/vim_scripts\/blob\/master\/plugin\/cf5-compile.vim\r\n","install_details":"\"\t\t\t\tPut this file into vim plugin directory. For linux users should\r\n\"\t\t\t\tbe  $HOME\/.vim\/plugin. \r\n\"\t\t\t\tIn your .vimrc file add \r\n\"\r\n\"\t\t\t\tmap   :call CF5Compile(1)\r\n\"\t\t\t\tmap   :call CF5Compile(0)\r\n\"\r\n\"\t\t\t\tThis will allow Ctrl-F5 to \"compile and run\" and F5 to only \r\n\"\t\t\t\t\"compile\" the file. Please, note that \"filetype\" is used to\r\n\"\t\t\t\tdefine the compiler\/interpreter used.\r\n\"\r\n\"\t\t\t\tThe value of the following variables are used while compiling\r\n\"\t\t\t\ta file:\r\n\"\t\t\t\t\tg:argv - command line arguments to pass to program.\r\n\"\t\t\t\t\tg:pyflags - flags to pass to python interpreter.\r\n\"\t\t\t\t\tg:cppflags - flags to pass to c++ compiler.\r\n\"\t\t\t\t\tg:wcppflags - flags to pass to (windows) compiler.\r\n\"\t\t\t\t\tg:lcppflags - flags to pass to (linux) compiler.\r\n\"\t\t\t\t\tg:ldflags - flags to pass to linker.\r\n\"\t\t\t\t\tg:ldlibpath - paths to add to PATH or LD_LIBRARY_PATH.\r\n\"\r\n\"\t\t\t\tI personally use this script with let-modeline.vim. The last\r\n\"\t\t\t\tallows to define some of compiler options right in the file. For \r\n\"\t\t\t\texample I have the following header in some of my cpp files:\r\n\"\t\t\t\t\/*\r\n\"\t\t\t\tVIM: let g:lcppflags=\"-std=c++11 -O2 -pthread\"\r\n\"\t\t\t\tVIM: let g:wcppflags=\"\/O2 \/EHsc \/DWIN32\"\r\n\"\t\t\t\tVIM: let g:cppflags=g:Iboost.g:Itbb\r\n\"\t\t\t\tVIM: let g:ldflags=g:Lboost.g:Ltbb.g:tbbmalloc.g:tbbmproxy\r\n\"\t\t\t\tVIM: let g:ldlibpath=g:Bboost.g:Btbb\r\n\"\t\t\t\tVIM: let g:argv=\"\"\r\n\"\t\t\t\t*\/\r\n\"\r\n\"\t\t\t\tYou might also consider using independence.vim or localvimrc.vim\r\n\"\t\t\t\tin order to configure the plugin for a particular directory.\r\n\"\r\n\"\t\t\t\tEnjoy.\r\n","5":"\"\t\t\t\tPut this file into vim plugin directory. For linux users should\r\n\"\t\t\t\tbe  $HOME\/.vim\/plugin. \r\n\"\t\t\t\tIn your .vimrc file add \r\n\"\r\n\"\t\t\t\tmap   :call CF5Compile(1)\r\n\"\t\t\t\tmap   :call CF5Compile(0)\r\n\"\r\n\"\t\t\t\tThis will allow Ctrl-F5 to \"compile and run\" and F5 to only \r\n\"\t\t\t\t\"compile\" the file. Please, note that \"filetype\" is used to\r\n\"\t\t\t\tdefine the compiler\/interpreter used.\r\n\"\r\n\"\t\t\t\tThe value of the following variables are used while compiling\r\n\"\t\t\t\ta file:\r\n\"\t\t\t\t\tg:argv - command line arguments to pass to program.\r\n\"\t\t\t\t\tg:pyflags - flags to pass to python interpreter.\r\n\"\t\t\t\t\tg:cppflags - flags to pass to c++ compiler.\r\n\"\t\t\t\t\tg:wcppflags - flags to pass to (windows) compiler.\r\n\"\t\t\t\t\tg:lcppflags - flags to pass to (linux) compiler.\r\n\"\t\t\t\t\tg:ldflags - flags to pass to linker.\r\n\"\t\t\t\t\tg:ldlibpath - paths to add to PATH or LD_LIBRARY_PATH.\r\n\"\r\n\"\t\t\t\tI personally use this script with let-modeline.vim. The last\r\n\"\t\t\t\tallows to define some of compiler options right in the file. For \r\n\"\t\t\t\texample I have the following header in some of my cpp files:\r\n\"\t\t\t\t\/*\r\n\"\t\t\t\tVIM: let g:lcppflags=\"-std=c++11 -O2 -pthread\"\r\n\"\t\t\t\tVIM: let g:wcppflags=\"\/O2 \/EHsc \/DWIN32\"\r\n\"\t\t\t\tVIM: let g:cppflags=g:Iboost.g:Itbb\r\n\"\t\t\t\tVIM: let g:ldflags=g:Lboost.g:Ltbb.g:tbbmalloc.g:tbbmproxy\r\n\"\t\t\t\tVIM: let g:ldlibpath=g:Bboost.g:Btbb\r\n\"\t\t\t\tVIM: let g:argv=\"\"\r\n\"\t\t\t\t*\/\r\n\"\r\n\"\t\t\t\tYou might also consider using independence.vim or localvimrc.vim\r\n\"\t\t\t\tin order to configure the plugin for a particular directory.\r\n\"\r\n\"\t\t\t\tEnjoy.\r\n","first_name":"Vahagn","6":"Vahagn","last_name":"Khachatryan","7":"Khachatryan","releases":[{"0":"5075","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"cf5-compile.vim","4":"cf5-compile.vim","src_id":"22732","5":"22732","creation_date":"1419424616","6":"1419424616"}]},"5074":{"script_id":"5074","0":"5074","script_name":"grimoire.vim","1":"grimoire.vim","script_type":"utility","2":"utility","summary":"Access Clojure Grimoire documentation from Vim","3":"Access Clojure Grimoire documentation from Vim","description":"Access Clojure Grimoire documentation at http:\/\/conj.io.","4":"Access Clojure Grimoire documentation at http:\/\/conj.io.","install_details":"","5":"","first_name":"jeb","6":"jeb","last_name":"beich","7":"beich","releases":[{"0":"5074","vim_version":"7.0","1":"7.0","script_version":"0.1.0","2":"0.1.0","version_comment":"Initial upload","3":"Initial upload","package":"grimoire.vim.zip","4":"grimoire.vim.zip","src_id":"22728","5":"22728","creation_date":"1419399549","6":"1419399549"}]},"5073":{"script_id":"5073","0":"5073","script_name":"EntryComplete","1":"EntryComplete","script_type":"utility","2":"utility","summary":"Insert mode completion based on lines in designated files or buffers.","3":"Insert mode completion based on lines in designated files or buffers.","description":"DESCRIPTION\r\nCheat sheets that contain a single phrase, formula, or function invocation per\r\nline can be very helpful and are used by many people. Using such as a\r\ncompletion source is difficult, though. The full line completion\r\n(i_CTRL-X_CTRL-L) considers other buffers, but cannot be restricted to a\r\nsingle one. And to trigger the completion, the base has to be written on a new\r\nline; you cannot recall a phrase from within an existing one. All of this can\r\nbe avoided by using a snippet plugin, but the syntax to define them usually is\r\nmore complex (so one cannot directly use one's cheat sheet), and the\r\nadditional features interfere with easy definition. Also, not every snippet\r\nplugin offers the popup selection aspect of insert-mode completion, so you may\r\nhave to remember the snippet name to recall it.\r\n\r\nThis plugin provides a highly configurable completion of lines found in\r\ndesignated files or buffers, triggered by a keyword in front of the cursor.\r\nWith its flexibility, you can use custom cheat sheets for a project, filetype,\r\nor particular buffer or window as well as global ones.\r\n\r\nSOURCE\r\nInspired by\r\n    http:\/\/stackoverflow.com\/questions\/27539429\/vim-snippet-phrase-dropdown-menu\r\n\r\nSEE ALSO\r\n- Check out the CompleteHelper.vim plugin page (vimscript #3914) for a full\r\n  list of insert mode completions powered by it.\r\n\r\nUSAGE\r\nIn insert mode, invoke the entry completion via CTRL-X CTRL-E\r\nYou can then search forward and backward via CTRL-N \/ CTRL-P, as usual.\r\n\r\nCTRL-X CTRL-E           Find matches for entries (i.e. entire lines) from the\r\n                        designated sources configured by\r\n                        g:EntryComplete_Sources.\r\n","4":"DESCRIPTION\r\nCheat sheets that contain a single phrase, formula, or function invocation per\r\nline can be very helpful and are used by many people. Using such as a\r\ncompletion source is difficult, though. The full line completion\r\n(i_CTRL-X_CTRL-L) considers other buffers, but cannot be restricted to a\r\nsingle one. And to trigger the completion, the base has to be written on a new\r\nline; you cannot recall a phrase from within an existing one. All of this can\r\nbe avoided by using a snippet plugin, but the syntax to define them usually is\r\nmore complex (so one cannot directly use one's cheat sheet), and the\r\nadditional features interfere with easy definition. Also, not every snippet\r\nplugin offers the popup selection aspect of insert-mode completion, so you may\r\nhave to remember the snippet name to recall it.\r\n\r\nThis plugin provides a highly configurable completion of lines found in\r\ndesignated files or buffers, triggered by a keyword in front of the cursor.\r\nWith its flexibility, you can use custom cheat sheets for a project, filetype,\r\nor particular buffer or window as well as global ones.\r\n\r\nSOURCE\r\nInspired by\r\n    http:\/\/stackoverflow.com\/questions\/27539429\/vim-snippet-phrase-dropdown-menu\r\n\r\nSEE ALSO\r\n- Check out the CompleteHelper.vim plugin page (vimscript #3914) for a full\r\n  list of insert mode completions powered by it.\r\n\r\nUSAGE\r\nIn insert mode, invoke the entry completion via CTRL-X CTRL-E\r\nYou can then search forward and backward via CTRL-N \/ CTRL-P, as usual.\r\n\r\nCTRL-X CTRL-E           Find matches for entries (i.e. entire lines) from the\r\n                        designated sources configured by\r\n                        g:EntryComplete_Sources.\r\n","install_details":"INSTALLATION\r\nThe code is hosted in a Git repo at\r\n    https:\/\/github.com\/inkarkat\/vim-EntryComplete\r\nYou can use your favorite plugin manager, or \"git clone\" into a directory used\r\nfor Vim packages. Releases are on the \"stable\" branch, the latest unstable\r\ndevelopment snapshot on \"master\".\r\n\r\nThis script is also packaged as a vimball. If you have the \"gunzip\"\r\ndecompressor in your PATH, simply edit the *.vmb.gz package in Vim; otherwise,\r\ndecompress the archive first, e.g. using WinZip. Inside Vim, install by\r\nsourcing the vimball or via the :UseVimball command.\r\n    vim EntryComplete*.vmb.gz\r\n    :so %\r\nTo uninstall, use the :RmVimball command.\r\n\r\nDEPENDENCIES\r\n- Requires Vim 7.0 or higher.\r\n- Requires the ingo-library.vim plugin (vimscript #4433), version 1.019 or\r\n  higher.\r\n- Requires the CompleteHelper.vim plugin (vimscript #3914), version 1.50 or\r\n  higher.\r\n\r\nCONFIGURATION\r\nFor a permanent configuration, put the following commands into your vimrc:\r\n\r\nThis completion uses designated files or buffers as completion sources. You\r\ncan configure window-local, buffer-local, or global Lists of sources. A Number\r\nis taken as a Vim buffer, a String specifies a filespec, a List directly\r\nspecifies matches (either as simple strings, or match objects as described\r\nunder complete-items), a Funcref is invoked without arguments and should\r\nreturn a List of filespecs \/ Numbers \/ Lists:\r\n    let g:EntryComplete_Sources = [bufnr('lines.txt'), expand('~\/.vimrc'),\r\n    \\   ['foo', 'bar', {'word': 'baz', 'menu': 'my favorite'}]\r\n    \\]\r\nFiles and buffers can consist of a header line. This must be the first line,\r\nand only contain the words from complete-items. The separators in between\r\nare then used to parse the remaining lines into completion objects. For\r\nexample:\r\n    word|abbr|menu\r\n    myxomatosis|mixi|A usually fatal viral disease of rabbits.\r\n\r\nThe default configuration checks for entries in entries\/{filetype}.txt and\r\nentries\/{filetype}\/*.txt in each 'runtimepath' directory, usually in your\r\nuser's configuration in ~\/.vim\/entries\/.\r\nYou can add additional directories to be checked via\r\ng:EntryComplete_FiletypeEntriesPath or b:EntryComplete_FiletypeEntriesPath.\r\n\r\nIf you want to use a different mapping, map your keys to the\r\n(EntryComplete) mapping target _before_ sourcing the script\r\n(e.g. in your vimrc):\r\n    imap  (EntryComplete)\r\n","5":"INSTALLATION\r\nThe code is hosted in a Git repo at\r\n    https:\/\/github.com\/inkarkat\/vim-EntryComplete\r\nYou can use your favorite plugin manager, or \"git clone\" into a directory used\r\nfor Vim packages. Releases are on the \"stable\" branch, the latest unstable\r\ndevelopment snapshot on \"master\".\r\n\r\nThis script is also packaged as a vimball. If you have the \"gunzip\"\r\ndecompressor in your PATH, simply edit the *.vmb.gz package in Vim; otherwise,\r\ndecompress the archive first, e.g. using WinZip. Inside Vim, install by\r\nsourcing the vimball or via the :UseVimball command.\r\n    vim EntryComplete*.vmb.gz\r\n    :so %\r\nTo uninstall, use the :RmVimball command.\r\n\r\nDEPENDENCIES\r\n- Requires Vim 7.0 or higher.\r\n- Requires the ingo-library.vim plugin (vimscript #4433), version 1.019 or\r\n  higher.\r\n- Requires the CompleteHelper.vim plugin (vimscript #3914), version 1.50 or\r\n  higher.\r\n\r\nCONFIGURATION\r\nFor a permanent configuration, put the following commands into your vimrc:\r\n\r\nThis completion uses designated files or buffers as completion sources. You\r\ncan configure window-local, buffer-local, or global Lists of sources. A Number\r\nis taken as a Vim buffer, a String specifies a filespec, a List directly\r\nspecifies matches (either as simple strings, or match objects as described\r\nunder complete-items), a Funcref is invoked without arguments and should\r\nreturn a List of filespecs \/ Numbers \/ Lists:\r\n    let g:EntryComplete_Sources = [bufnr('lines.txt'), expand('~\/.vimrc'),\r\n    \\   ['foo', 'bar', {'word': 'baz', 'menu': 'my favorite'}]\r\n    \\]\r\nFiles and buffers can consist of a header line. This must be the first line,\r\nand only contain the words from complete-items. The separators in between\r\nare then used to parse the remaining lines into completion objects. For\r\nexample:\r\n    word|abbr|menu\r\n    myxomatosis|mixi|A usually fatal viral disease of rabbits.\r\n\r\nThe default configuration checks for entries in entries\/{filetype}.txt and\r\nentries\/{filetype}\/*.txt in each 'runtimepath' directory, usually in your\r\nuser's configuration in ~\/.vim\/entries\/.\r\nYou can add additional directories to be checked via\r\ng:EntryComplete_FiletypeEntriesPath or b:EntryComplete_FiletypeEntriesPath.\r\n\r\nIf you want to use a different mapping, map your keys to the\r\n(EntryComplete) mapping target _before_ sourcing the script\r\n(e.g. in your vimrc):\r\n    imap  (EntryComplete)\r\n","first_name":"Ingo","6":"Ingo","last_name":"Karkat","7":"Karkat","releases":[{"0":"5073","vim_version":"7.0","1":"7.0","script_version":"1.20","2":"1.20","version_comment":"- CHG: Use *.txt file extension for default entry files. This allows to put backups in the same directory without having them picked up.\r\n- ENH: By default, also look into ...\/entries\/{filetype}\/*.txt for entries. This allows to easily use multiple entry sources for a filetype.\r\n- ENH: Support parsing of files and buffers into complete match objects via a header line.\r\n- Expose EntryComplete#Filetype#GetEntriesFilespecs(); it can be useful for customizations.","3":"- CHG: Use *.txt file extension for default entry files. This allows to put backups in the same directory without having them picked up.\r\n- ENH: By default, also look into ...\/entries\/{filetype}\/*.txt for entries. This allows to easily use multiple entry sources for a filetype.\r\n- ENH: Support parsing of files and buffers into complete match objects via a header line.\r\n- Expose EntryComplete#Filetype#GetEntriesFilespecs(); it can be useful for customizations.","package":"EntryComplete-1.20.vmb.gz","4":"EntryComplete-1.20.vmb.gz","src_id":"25996","5":"25996","creation_date":"1527458127","6":"1527458127"},{"0":"5073","vim_version":"7.0","1":"7.0","script_version":"1.10","2":"1.10","version_comment":"- ENH: Support Lists of matches \/ match objects.","3":"- ENH: Support Lists of matches \/ match objects.","package":"EntryComplete-1.10.vmb.gz","4":"EntryComplete-1.10.vmb.gz","src_id":"25019","5":"25019","creation_date":"1489073258","6":"1489073258"},{"0":"5073","vim_version":"7.0","1":"7.0","script_version":"1.00","2":"1.00","version_comment":"Initial upload","3":"Initial upload","package":"EntryComplete-1.00.vmb.gz","4":"EntryComplete-1.00.vmb.gz","src_id":"22727","5":"22727","creation_date":"1419362092","6":"1419362092"}]},"5072":{"script_id":"5072","0":"5072","script_name":"vim-nose","1":"vim-nose","script_type":"utility","2":"utility","summary":"Plugin wrapping nosetests command to be executed inside Vim","3":"Plugin wrapping nosetests command to be executed inside Vim","description":"vim-nose\r\nPlugin wrapping nosetests command line tool to execute python tests inside Vim. All in the name of productivity!\r\n\r\nFeatures\r\nThis plugin improve on Vim compiler option by adding some features specific to nose:\r\n\r\nConfigurable python virtual environment.\r\nIsolate tests to be run. Run a specific test, a test case, a test module or run all tests (requires git).\r\nMemorize last test ran. The last test will run when commands are executed in non-test modules.\r\nPopulate Vim quickfix window with failing tests and errors for easy navigation.\r\nRequirements\r\nFor this plugin to have some value, you need this requirements to be installed in your environment:\r\n\r\npython\r\nnose\r\nThese requirement are optional but improve the plugin usage:\r\n\r\ngit\r\nvim-dispatch by Tim Pope to run tests asynchronously\r\nVirtualEnv Configuration\r\nPlugin support two configuration options to help discovery of virtual environment.\r\n\r\nA configuration file (usually located at the root of your project).\r\nA git configuration (vim-nose.venv) in your git repository\r\nIf none of those configuration are set, the plugin will use either the system environment or any virtualenv already set in Vim process (terminal only).\r\n\r\nSee the plugin documentation for more details (:h nose-virtualenv).\r\n\r\nUsage\r\n:RunTest\r\n\r\nRun the current test surrounding the cursor position. Otherwise, run all tests in the scope the cursor is located in (i.e. test case or module).\r\n\r\n:RunCase\r\n\r\nRun all tests found in the test case surrounding the cursor position. If cursor is outside a test case scope, all tests for the module (buffer) are run.\r\n\r\n:RunModule\r\n\r\nRun all tests found in the current module (buffer).\r\n\r\n:RunAllTests\r\n\r\nRun all tests found in the git repository of the edited buffer.\r\n\r\nInteractive commands\r\n\r\nAll :Run... command can also be launched in interactive mode. This will run tests synchronously in an external console (if possible). This is useful for debugging your program or tests. For instance, using ipdb inside gVim or MacVim basic shell does not support coloring! This is an attempt to fix this problem.\r\n\r\nExample:\r\n\r\n:RunTest!\r\nLicense\r\nCopyright \u00c2\u00a9 Pascal Lalancette. Distributed under the same terms as Vim itself. See :help license.","4":"vim-nose\r\nPlugin wrapping nosetests command line tool to execute python tests inside Vim. All in the name of productivity!\r\n\r\nFeatures\r\nThis plugin improve on Vim compiler option by adding some features specific to nose:\r\n\r\nConfigurable python virtual environment.\r\nIsolate tests to be run. Run a specific test, a test case, a test module or run all tests (requires git).\r\nMemorize last test ran. The last test will run when commands are executed in non-test modules.\r\nPopulate Vim quickfix window with failing tests and errors for easy navigation.\r\nRequirements\r\nFor this plugin to have some value, you need this requirements to be installed in your environment:\r\n\r\npython\r\nnose\r\nThese requirement are optional but improve the plugin usage:\r\n\r\ngit\r\nvim-dispatch by Tim Pope to run tests asynchronously\r\nVirtualEnv Configuration\r\nPlugin support two configuration options to help discovery of virtual environment.\r\n\r\nA configuration file (usually located at the root of your project).\r\nA git configuration (vim-nose.venv) in your git repository\r\nIf none of those configuration are set, the plugin will use either the system environment or any virtualenv already set in Vim process (terminal only).\r\n\r\nSee the plugin documentation for more details (:h nose-virtualenv).\r\n\r\nUsage\r\n:RunTest\r\n\r\nRun the current test surrounding the cursor position. Otherwise, run all tests in the scope the cursor is located in (i.e. test case or module).\r\n\r\n:RunCase\r\n\r\nRun all tests found in the test case surrounding the cursor position. If cursor is outside a test case scope, all tests for the module (buffer) are run.\r\n\r\n:RunModule\r\n\r\nRun all tests found in the current module (buffer).\r\n\r\n:RunAllTests\r\n\r\nRun all tests found in the git repository of the edited buffer.\r\n\r\nInteractive commands\r\n\r\nAll :Run... command can also be launched in interactive mode. This will run tests synchronously in an external console (if possible). This is useful for debugging your program or tests. For instance, using ipdb inside gVim or MacVim basic shell does not support coloring! This is an attempt to fix this problem.\r\n\r\nExample:\r\n\r\n:RunTest!\r\nLicense\r\nCopyright \u00c2\u00a9 Pascal Lalancette. Distributed under the same terms as Vim itself. See :help license.","install_details":"","5":"","first_name":"Pascal","6":"Pascal","last_name":"Lalancette","7":"Lalancette","releases":[{"0":"5072","vim_version":"7.4","1":"7.4","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"vim-nose.tar.gz","4":"vim-nose.tar.gz","src_id":"22711","5":"22711","creation_date":"1418937167","6":"1418937167"}]},"5071":{"script_id":"5071","0":"5071","script_name":"Spacegray.vim","1":"Spacegray.vim","script_type":"color scheme","2":"color scheme","summary":"An elegant dark colorscheme for Vim","3":"An elegant dark colorscheme for Vim","description":"For latest updates, check out (pardon the pun) Spacegray on Github: https:\/\/sr.ht\/~ackyshake\/spacegray.vim\/\r\n\r\nSpacegray is a colorscheme for Vim loosely modeled after the spacegray theme for Xcode.\r\n\r\nNOTE: Spacegray (currently) is a 256color and up color scheme. Please use a terminal with support for 256colors or GUI Vim to fully enjoy Spacegray.vim\r\n\r\nSpacegray v1.6 and above support a \"Low Contrast\" option.\r\n\r\nHere are some screenshots:\r\n\r\nLow Contrast: https:\/\/git.sr.ht\/~ackyshake\/spacegray.vim\/blob\/HEAD\/screenshots\/low_contrast.png\r\nDark: https:\/\/git.sr.ht\/~ackyshake\/spacegray.vim\/blob\/HEAD\/screenshots\/dark.png\r\nSyntax Groups: https:\/\/git.sr.ht\/~ackyshake\/spacegray.vim\/blob\/HEAD\/screenshots\/hl_groups.png\r\nC: http:\/\/cl.ly\/Yxcd\/C-spacegray.png\r\nJavaScript: http:\/\/cl.ly\/Yx75\/JS-Spacegray.png\r\nVim: http:\/\/cl.ly\/Yxfr\/vim-spacegray.png\r\n\r\nEnjoy!","4":"For latest updates, check out (pardon the pun) Spacegray on Github: https:\/\/sr.ht\/~ackyshake\/spacegray.vim\/\r\n\r\nSpacegray is a colorscheme for Vim loosely modeled after the spacegray theme for Xcode.\r\n\r\nNOTE: Spacegray (currently) is a 256color and up color scheme. Please use a terminal with support for 256colors or GUI Vim to fully enjoy Spacegray.vim\r\n\r\nSpacegray v1.6 and above support a \"Low Contrast\" option.\r\n\r\nHere are some screenshots:\r\n\r\nLow Contrast: https:\/\/git.sr.ht\/~ackyshake\/spacegray.vim\/blob\/HEAD\/screenshots\/low_contrast.png\r\nDark: https:\/\/git.sr.ht\/~ackyshake\/spacegray.vim\/blob\/HEAD\/screenshots\/dark.png\r\nSyntax Groups: https:\/\/git.sr.ht\/~ackyshake\/spacegray.vim\/blob\/HEAD\/screenshots\/hl_groups.png\r\nC: http:\/\/cl.ly\/Yxcd\/C-spacegray.png\r\nJavaScript: http:\/\/cl.ly\/Yx75\/JS-Spacegray.png\r\nVim: http:\/\/cl.ly\/Yxfr\/vim-spacegray.png\r\n\r\nEnjoy!","install_details":"Unzip the zip file, and then move Spacegray.vim inside the colors directory into the ~\/.vim\/colors folder.\r\n\r\nIf you have Vim 8.0 or above, simply move it into the default 'packpath' like so:\r\n\r\n    mkdir -p ~\/.vim\/pack\/vendor\/start && unzip -d ~\/.vim\/pack\/vendor\/start -- Spacegray.vim-1.6.zip","5":"Unzip the zip file, and then move Spacegray.vim inside the colors directory into the ~\/.vim\/colors folder.\r\n\r\nIf you have Vim 8.0 or above, simply move it into the default 'packpath' like so:\r\n\r\n    mkdir -p ~\/.vim\/pack\/vendor\/start && unzip -d ~\/.vim\/pack\/vendor\/start -- Spacegray.vim-1.6.zip","first_name":"Akshay","6":"Akshay","last_name":"Hegde","7":"Hegde","releases":[{"0":"5071","vim_version":"7.3","1":"7.3","script_version":"1.6","2":"1.6","version_comment":"Spacegray v1.6 \r\n\r\n- Add low contrast option\r\n- Add colors for :terminal\r\n- Other miscellaneous updates to default highlight groups","3":"Spacegray v1.6 \r\n\r\n- Add low contrast option\r\n- Add colors for :terminal\r\n- Other miscellaneous updates to default highlight groups","package":"Spacegray.vim-1.6.zip","4":"Spacegray.vim-1.6.zip","src_id":"27431","5":"27431","creation_date":"1609321420","6":"1609321420"},{"0":"5071","vim_version":"7.3","1":"7.3","script_version":"1.4","2":"1.4","version_comment":"- Add colors for Question highlight group\r\n- Add gnome-terminal and Terminal.app colorschemes\r\n- Improve diff colors\r\n- Fix typo in Exception highlight group","3":"- Add colors for Question highlight group\r\n- Add gnome-terminal and Terminal.app colorschemes\r\n- Improve diff colors\r\n- Fix typo in Exception highlight group","package":"Spacegray.vim-1.4.zip","4":"Spacegray.vim-1.4.zip","src_id":"22961","5":"22961","creation_date":"1425186977","6":"1425186977"},{"0":"5071","vim_version":"7.3","1":"7.3","script_version":"1.3","2":"1.3","version_comment":"* Tweaks to Type and Identifier xterm colors to make them match with the GUI colors\r\n* Tweak Visual and Search colors\r\n* Tweak String xterm colors to make it match the GUI colors\r\n* Fix to conceal colors to make it look nice.","3":"* Tweaks to Type and Identifier xterm colors to make them match with the GUI colors\r\n* Tweak Visual and Search colors\r\n* Tweak String xterm colors to make it match the GUI colors\r\n* Fix to conceal colors to make it look nice.","package":"Spacegray.vim-1.3.zip","4":"Spacegray.vim-1.3.zip","src_id":"22746","5":"22746","creation_date":"1419991518","6":"1419991518"},{"0":"5071","vim_version":"7.3","1":"7.3","script_version":"1.2","2":"1.2","version_comment":"* Fixes Warning\/ErrorMsg colors\r\n* Match Normal GUI colors more closely.\r\n* Add highlighting for SignColumn","3":"* Fixes Warning\/ErrorMsg colors\r\n* Match Normal GUI colors more closely.\r\n* Add highlighting for SignColumn","package":"Spacegray.vim-1.2.zip","4":"Spacegray.vim-1.2.zip","src_id":"22729","5":"22729","creation_date":"1419404260","6":"1419404260"},{"0":"5071","vim_version":"7.3","1":"7.3","script_version":"1.1","2":"1.1","version_comment":"- Added iTerm2 colors (Spacegray palette)\r\n- Added Terminator config (Spacegray palette)\r\n- Modified colorcolumn to be a grayish color.\r\n- Improved colors for rails.\r\n","3":"- Added iTerm2 colors (Spacegray palette)\r\n- Added Terminator config (Spacegray palette)\r\n- Modified colorcolumn to be a grayish color.\r\n- Improved colors for rails.\r\n","package":"Spacegray.vim.zip","4":"Spacegray.vim.zip","src_id":"22708","5":"22708","creation_date":"1418864250","6":"1418864250"},{"0":"5071","vim_version":"7.3","1":"7.3","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"Spacegray.vim-1.0.zip","4":"Spacegray.vim-1.0.zip","src_id":"22700","5":"22700","creation_date":"1418605914","6":"1418605914"}]},"5070":{"script_id":"5070","0":"5070","script_name":"vim-tab","1":"vim-tab","script_type":"utility","2":"utility","summary":"plugin that maintain each tab different working directory","3":"plugin that maintain each tab different working directory","description":"maintain each tab different working directory,\r\nand switch directory automatically when switch tab,\r\nand can also do custom actions when switch tab,like\r\nauto reload tags in the new directory, and some other plugin \r\nwould also benefit from this plugin,like CommandT, grep, working in a \r\nsub directory is so mush fast and easy","4":"maintain each tab different working directory,\r\nand switch directory automatically when switch tab,\r\nand can also do custom actions when switch tab,like\r\nauto reload tags in the new directory, and some other plugin \r\nwould also benefit from this plugin,like CommandT, grep, working in a \r\nsub directory is so mush fast and easy","install_details":"unzip them to your .vim, \r\nfor detail please refer github https:\/\/github.com\/rargo\/vim-tab","5":"unzip them to your .vim, \r\nfor detail please refer github https:\/\/github.com\/rargo\/vim-tab","first_name":"rargo","6":"rargo","last_name":"ye","7":"ye","releases":[{"0":"5070","vim_version":"7.4","1":"7.4","script_version":"1.00","2":"1.00","version_comment":"Initial upload","3":"Initial upload","package":"vim-tab.zip","4":"vim-tab.zip","src_id":"22699","5":"22699","creation_date":"1418569522","6":"1418569522"}]},"5069":{"script_id":"5069","0":"5069","script_name":"Vim-Swoop","1":"Vim-Swoop","script_type":"utility","2":"utility","summary":"Grep and replace easily in multiple files being context aware !","3":"Grep and replace easily in multiple files being context aware !","description":"Vim swoop is directly inspired from helm-swoop we can find as emacs' plugin.\r\n\r\nIt allows you to find and replace occurences in many buffers being aware of the context.\r\n\r\n\r\n\r\nPlease, visit the git repo so have more info and see animation about how it works.\r\nhttps:\/\/github.com\/pelodelfuego\/vim-swoop\r\n\r\n\r\n\r\n\r\n-----  Credit  -----\r\nSpecial thanks to [ Shingo Fukuyama ]( https:\/\/github.com\/ShingoFukuyama ) for his amazing idea which has juste been ported to vim.\r\n \r\n","4":"Vim swoop is directly inspired from helm-swoop we can find as emacs' plugin.\r\n\r\nIt allows you to find and replace occurences in many buffers being aware of the context.\r\n\r\n\r\n\r\nPlease, visit the git repo so have more info and see animation about how it works.\r\nhttps:\/\/github.com\/pelodelfuego\/vim-swoop\r\n\r\n\r\n\r\n\r\n-----  Credit  -----\r\nSpecial thanks to [ Shingo Fukuyama ]( https:\/\/github.com\/ShingoFukuyama ) for his amazing idea which has juste been ported to vim.\r\n \r\n","install_details":"Vim-Swoop is a pure vimscript plugin, no other dependancies.\r\n\r\n\r\n-- Pathogen --\r\n\r\ngit clone https:\/\/github.com\/pelodelfuego\/vim-swoop ~\/.vim\/bundle\/vim-swoop\r\n\r\n\r\n","5":"Vim-Swoop is a pure vimscript plugin, no other dependancies.\r\n\r\n\r\n-- Pathogen --\r\n\r\ngit clone https:\/\/github.com\/pelodelfuego\/vim-swoop ~\/.vim\/bundle\/vim-swoop\r\n\r\n\r\n","first_name":"Cl\u00c3\u00a9ment","6":"Cl\u00c3\u00a9ment","last_name":"CREPY","7":"CREPY","releases":[{"0":"5069","vim_version":"7.0","1":"7.0","script_version":"1.1.8","2":"1.1.8","version_comment":"fix fix from old code for buffer delete","3":"fix fix from old code for buffer delete","package":"vim-swoop.zip","4":"vim-swoop.zip","src_id":"25317","5":"25317","creation_date":"1497609488","6":"1497609488"},{"0":"5069","vim_version":"7.0","1":"7.0","script_version":"1.1.7","2":"1.1.7","version_comment":"Fix: Proper handle for the swoopBuffer (and file)","3":"Fix: Proper handle for the swoopBuffer (and file)","package":"vim-swoop.zip","4":"vim-swoop.zip","src_id":"25297","5":"25297","creation_date":"1497023625","6":"1497023625"},{"0":"5069","vim_version":"7.0","1":"7.0","script_version":"1.1.6","2":"1.1.6","version_comment":"fix :x \r\nadd help in vim","3":"fix :x \r\nadd help in vim","package":"vim-swoop.zip","4":"vim-swoop.zip","src_id":"24584","5":"24584","creation_date":"1475684027","6":"1475684027"},{"0":"5069","vim_version":"7.0","1":"7.0","script_version":"1.1.5","2":"1.1.5","version_comment":"fix saving \r\nfix cpo restore \r\nupdate Readme\r\nfix form david Kotchan","3":"fix saving \r\nfix cpo restore \r\nupdate Readme\r\nfix form david Kotchan","package":"vim-swoop.zip","4":"vim-swoop.zip","src_id":"24151","5":"24151","creation_date":"1459508680","6":"1459508680"},{"0":"5069","vim_version":"7.0","1":"7.0","script_version":"1.1.3","2":"1.1.3","version_comment":"fix cpo options\r\nauto save consistent way","3":"fix cpo options\r\nauto save consistent way","package":"vim-swoop.zip","4":"vim-swoop.zip","src_id":"22927","5":"22927","creation_date":"1424453887","6":"1424453887"},{"0":"5069","vim_version":"7.0","1":"7.0","script_version":"1.1.0","2":"1.1.0","version_comment":"Add highlight on last pattern search\r\nOption for case sentitivity\r\nPossibility to type actual space for smart search\r\nRefactor","3":"Add highlight on last pattern search\r\nOption for case sentitivity\r\nPossibility to type actual space for smart search\r\nRefactor","package":"vim-swoop.zip","4":"vim-swoop.zip","src_id":"22849","5":"22849","creation_date":"1422493610","6":"1422493610"},{"0":"5069","vim_version":"7.0","1":"7.0","script_version":"1.0.5","2":"1.0.5","version_comment":"Fix Bugs\r\nEnchanced Customisation\r\nExposed Command\r\nExposed Function\r\nLazy Filetype Load\r\nSwoop Current visual Selection","3":"Fix Bugs\r\nEnchanced Customisation\r\nExposed Command\r\nExposed Function\r\nLazy Filetype Load\r\nSwoop Current visual Selection","package":"vim-swoop.tar.gz","4":"vim-swoop.tar.gz","src_id":"22810","5":"22810","creation_date":"1421702512","6":"1421702512"},{"0":"5069","vim_version":"7.0","1":"7.0","script_version":"1.0.0","2":"1.0.0","version_comment":"Bring interactivity to Swoop Mecanism. Much more intutive and faster workflow.","3":"Bring interactivity to Swoop Mecanism. Much more intutive and faster workflow.","package":"vim-swoop.zip","4":"vim-swoop.zip","src_id":"22763","5":"22763","creation_date":"1420645169","6":"1420645169"},{"0":"5069","vim_version":"7.4","1":"7.4","script_version":"0.9","2":"0.9","version_comment":"Initial upload","3":"Initial upload","package":"vim-swoop.tar.gz","4":"vim-swoop.tar.gz","src_id":"22698","5":"22698","creation_date":"1418568258","6":"1418568258"}]},"5068":{"script_id":"5068","0":"5068","script_name":"vim-terraform","1":"vim-terraform","script_type":"utility","2":"utility","summary":"basic vim\/terraform integration","3":"basic vim\/terraform integration","description":"This plugin adds a :Terraform command that runs terraform, with tab\r\ncompletion of subcommands. It also sets up *.tf and *.tfstate files\r\nto be highlighted as HML (Hashicorp's JSON variant) and JSON respectively.\r\n","4":"This plugin adds a :Terraform command that runs terraform, with tab\r\ncompletion of subcommands. It also sets up *.tf and *.tfstate files\r\nto be highlighted as HML (Hashicorp's JSON variant) and JSON respectively.\r\n","install_details":"","5":"","first_name":"Mark","6":"Mark","last_name":"Cornick","7":"Cornick","releases":[{"0":"5068","vim_version":"7.0","1":"7.0","script_version":"1.2.1","2":"1.2.1","version_comment":"Block indentation fix (thanks imkira@github)","3":"Block indentation fix (thanks imkira@github)","package":"vim-terraform-1.2.1.tar.gz","4":"vim-terraform-1.2.1.tar.gz","src_id":"22878","5":"22878","creation_date":"1423158557","6":"1423158557"},{"0":"5068","vim_version":"7.0","1":"7.0","script_version":"1.2.0","2":"1.2.0","version_comment":"Add Kevin Le's syntax highlighting","3":"Add Kevin Le's syntax highlighting","package":"vim-terraform-1.2.0.tar.gz","4":"vim-terraform-1.2.0.tar.gz","src_id":"22689","5":"22689","creation_date":"1418397715","6":"1418397715"},{"0":"5068","vim_version":"7.0","1":"7.0","script_version":"1.1.0","2":"1.1.0","version_comment":"Remove syntax highlighting; see README.md","3":"Remove syntax highlighting; see README.md","package":"vim-terraform-1.1.0.tar.gz","4":"vim-terraform-1.1.0.tar.gz","src_id":"22688","5":"22688","creation_date":"1418329098","6":"1418329098"},{"0":"5068","vim_version":"7.0","1":"7.0","script_version":"1.0.1","2":"1.0.1","version_comment":"Make this work without the JSON plugin","3":"Make this work without the JSON plugin","package":"vim-terraform-1.0.1.tar.gz","4":"vim-terraform-1.0.1.tar.gz","src_id":"22686","5":"22686","creation_date":"1418265319","6":"1418265319"},{"0":"5068","vim_version":"7.0","1":"7.0","script_version":"1.0.0","2":"1.0.0","version_comment":"Initial upload","3":"Initial upload","package":"vim-terraform-1.0.0.tar.gz","4":"vim-terraform-1.0.0.tar.gz","src_id":"22685","5":"22685","creation_date":"1418238445","6":"1418238445"}]},"5067":{"script_id":"5067","0":"5067","script_name":"vim-packer","1":"vim-packer","script_type":"utility","2":"utility","summary":"basic vim\/packer integration","3":"basic vim\/packer integration","description":"This plugin adds a `:Packer` command that runs packer, with tab\r\ncompletion of subcommands.\r\n","4":"This plugin adds a `:Packer` command that runs packer, with tab\r\ncompletion of subcommands.\r\n","install_details":"","5":"","first_name":"Mark","6":"Mark","last_name":"Cornick","7":"Cornick","releases":[{"0":"5067","vim_version":"7.0","1":"7.0","script_version":"1.0.0","2":"1.0.0","version_comment":"Initial upload","3":"Initial upload","package":"vim-packer-1.0.0.tar.gz","4":"vim-packer-1.0.0.tar.gz","src_id":"22684","5":"22684","creation_date":"1418238388","6":"1418238388"}]},"5066":{"script_id":"5066","0":"5066","script_name":"Escape Search","1":"Escape Search","script_type":"utility","2":"utility","summary":"escape special characters in your search expressions","3":"escape special characters in your search expressions","description":"Start typing a search, e.g.:\r\n\/http:\/\/www.vim.org\/\r\n\r\nBefore pressing Enter, press F7 to escape the search.:\r\n\/http:\\\/\\\/www\\.vim\\.org\\\/","4":"Start typing a search, e.g.:\r\n\/http:\/\/www.vim.org\/\r\n\r\nBefore pressing Enter, press F7 to escape the search.:\r\n\/http:\\\/\\\/www\\.vim\\.org\\\/","install_details":"Source this file, or copy the line into your .vimrc.","5":"Source this file, or copy the line into your .vimrc.","first_name":"Rolf","6":"Rolf","last_name":"Asmund","7":"Asmund","releases":[{"0":"5066","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"escape_search.vim","4":"escape_search.vim","src_id":"22682","5":"22682","creation_date":"1418205361","6":"1418205361"}]},"5065":{"script_id":"5065","0":"5065","script_name":"filestyle","1":"filestyle","script_type":"utility","2":"utility","summary":"filestyle is a Vim plugin that highlights unwanted whitespace and characters.","3":"filestyle is a Vim plugin that highlights unwanted whitespace and characters.","description":"**filestyle** automatically checks each opened file.\r\n\r\n##### Commands\r\n\r\n* `:FileStyleEnable`     - enable plugin globally\r\n* `:FileStyleDisable`    - disable plugin globally\r\n* `:FileStyleActivate`   - enable plugin for current buffer\r\n* `:FileStyleDeactivate` - disable plugin for current buffer\r\n* `:FileStyleCheck`      - check current buffer\r\n* `:FileStyleFix`        - fix style errors\r\n\r\n##### Highlighting rules\r\n\r\n1. If `'expandtab'` is set, highlight tabs (RED), if not, highlight spaces at\r\n   the beginning of a line (YELLOW).\r\n2. Highlight trailing spaces (CYAN)\r\n3. Highlight line parts that exceed `'textwidth'` (INVERT)\r\n4. Highlight control characters (BLUE)\r\n\r\n##### FileStyleFix rules\r\n\r\n1. Remove control characters\r\n2. Remove trailing spaces\r\n3. If `'expandtab'` is set, replace tabs with spaces, if not, replace spaces\r\n   at the beginning of a line with tabs\r\n\r\n##### Ignore file types\r\n\r\nBy default, **filestyle** checks all file types. To ignore a file type, for\r\nexample `text`, add the following line to your `.vimrc`:\r\n\r\n    let g:filestyle_ignore = ['text']\r\n\r\n##### Ignore patterns\r\n\r\n**filestyle** allows you to specify patterns that should be ignored. To ignore\r\na pattern, for example quoted lines starting with `>`, add the following line\r\nto your `.vimrc`:\r\n\r\n    let g:filestyle_ignore_patterns = ['^\\(> \\?\\)\\+$']\r\n\r\n##### Known issues\r\n\r\n* **filestyle** cannot detect `'textwidth'` changes. If you change `'textwidth'`,\r\n  execute `:FileStyleCheck` to ensure the new width is used for highlighting long\r\n  lines.\r\n\r\n* Error E315 is be thrown by Vim in case of `'splitbelow'` option is set\r\n  when `'help'` command is called\r\n\r\n\r\nContribution\r\n------------\r\n\r\nSource code and issues are hosted on GitHub:\r\n\r\n    https:\/\/github.com\/aserebryakov\/filestyle\r\n\r\nLicense\r\n-------\r\n\r\n[Apache License, Version 2.0](http:\/\/www.apache.org\/licenses\/LICENSE-2.0)\r\n\r\n\r\nCredits\r\n-------\r\n\r\n* Alexander Serebryakov, original author ([GitHub](https:\/\/github.com\/aserebryakov))\r\n* Markus Weimar ([GitHub](https:\/\/github.com\/Markus00000))\r\n","4":"**filestyle** automatically checks each opened file.\r\n\r\n##### Commands\r\n\r\n* `:FileStyleEnable`     - enable plugin globally\r\n* `:FileStyleDisable`    - disable plugin globally\r\n* `:FileStyleActivate`   - enable plugin for current buffer\r\n* `:FileStyleDeactivate` - disable plugin for current buffer\r\n* `:FileStyleCheck`      - check current buffer\r\n* `:FileStyleFix`        - fix style errors\r\n\r\n##### Highlighting rules\r\n\r\n1. If `'expandtab'` is set, highlight tabs (RED), if not, highlight spaces at\r\n   the beginning of a line (YELLOW).\r\n2. Highlight trailing spaces (CYAN)\r\n3. Highlight line parts that exceed `'textwidth'` (INVERT)\r\n4. Highlight control characters (BLUE)\r\n\r\n##### FileStyleFix rules\r\n\r\n1. Remove control characters\r\n2. Remove trailing spaces\r\n3. If `'expandtab'` is set, replace tabs with spaces, if not, replace spaces\r\n   at the beginning of a line with tabs\r\n\r\n##### Ignore file types\r\n\r\nBy default, **filestyle** checks all file types. To ignore a file type, for\r\nexample `text`, add the following line to your `.vimrc`:\r\n\r\n    let g:filestyle_ignore = ['text']\r\n\r\n##### Ignore patterns\r\n\r\n**filestyle** allows you to specify patterns that should be ignored. To ignore\r\na pattern, for example quoted lines starting with `>`, add the following line\r\nto your `.vimrc`:\r\n\r\n    let g:filestyle_ignore_patterns = ['^\\(> \\?\\)\\+$']\r\n\r\n##### Known issues\r\n\r\n* **filestyle** cannot detect `'textwidth'` changes. If you change `'textwidth'`,\r\n  execute `:FileStyleCheck` to ensure the new width is used for highlighting long\r\n  lines.\r\n\r\n* Error E315 is be thrown by Vim in case of `'splitbelow'` option is set\r\n  when `'help'` command is called\r\n\r\n\r\nContribution\r\n------------\r\n\r\nSource code and issues are hosted on GitHub:\r\n\r\n    https:\/\/github.com\/aserebryakov\/filestyle\r\n\r\nLicense\r\n-------\r\n\r\n[Apache License, Version 2.0](http:\/\/www.apache.org\/licenses\/LICENSE-2.0)\r\n\r\n\r\nCredits\r\n-------\r\n\r\n* Alexander Serebryakov, original author ([GitHub](https:\/\/github.com\/aserebryakov))\r\n* Markus Weimar ([GitHub](https:\/\/github.com\/Markus00000))\r\n","install_details":"    Pathogen:\r\n\r\n        $ cd ~\/.vim\/bundle\r\n        $ git clone https:\/\/github.com\/aserebryakov\/filestyle.git\r\n\r\n    NeoBundle:\r\n\r\n        NeoBundle 'aserebryakov\/filestyle'\r\n\r\n    Without plugin manager\r\n\r\n        Clone this repository and copy the content to your `~\/.vim\/` directory.","5":"    Pathogen:\r\n\r\n        $ cd ~\/.vim\/bundle\r\n        $ git clone https:\/\/github.com\/aserebryakov\/filestyle.git\r\n\r\n    NeoBundle:\r\n\r\n        NeoBundle 'aserebryakov\/filestyle'\r\n\r\n    Without plugin manager\r\n\r\n        Clone this repository and copy the content to your `~\/.vim\/` directory.","first_name":"Alexander","6":"Alexander","last_name":"Serebryakov","7":"Serebryakov","releases":[{"0":"5065","vim_version":"7.4","1":"7.4","script_version":"1.2.0","2":"1.2.0","version_comment":"* Added `FileStyleToggle` command\r\n* Fixed the error if default colorscheme is used","3":"* Added `FileStyleToggle` command\r\n* Fixed the error if default colorscheme is used","package":"filestyle-1.2.0.zip","4":"filestyle-1.2.0.zip","src_id":"25843","5":"25843","creation_date":"1519627561","6":"1519627561"},{"0":"5065","vim_version":"7.4","1":"7.4","script_version":"1.1.2","2":"1.1.2","version_comment":"* Fixed error messages when Vim is started in a narrow terminal\r\n* Fixed tag and version number in help file","3":"* Fixed error messages when Vim is started in a narrow terminal\r\n* Fixed tag and version number in help file","package":"filestyle-1.1.2.zip","4":"filestyle-1.1.2.zip","src_id":"23561","5":"23561","creation_date":"1440825691","6":"1440825691"},{"0":"5065","vim_version":"7.4","1":"7.4","script_version":"1.1.1","2":"1.1.1","version_comment":"* Fixed cursor positioning after FileStyleFix call","3":"* Fixed cursor positioning after FileStyleFix call","package":"filestyle-1.1.1.zip","4":"filestyle-1.1.1.zip","src_id":"23405","5":"23405","creation_date":"1434783653","6":"1434783653"},{"0":"5065","vim_version":"7.4","1":"7.4","script_version":"1.1.0","2":"1.1.0","version_comment":"* Added support for user-defined highlight groups\r\n* Fixed issue with tabs switching in INSERT mode","3":"* Added support for user-defined highlight groups\r\n* Fixed issue with tabs switching in INSERT mode","package":"filestyle-1.1.0.zip","4":"filestyle-1.1.0.zip","src_id":"23383","5":"23383","creation_date":"1434207156","6":"1434207156"},{"0":"5065","vim_version":"7.4","1":"7.4","script_version":"1.0.0","2":"1.0.0","version_comment":"* Implemented ignored patterns\r\n* Removed highlighting of trailing spaces in current line when in Insert mode\r\n* Improved order of highlights\r\n","3":"* Implemented ignored patterns\r\n* Removed highlighting of trailing spaces in current line when in Insert mode\r\n* Improved order of highlights\r\n","package":"filestyle-1.0.0.zip","4":"filestyle-1.0.0.zip","src_id":"23322","5":"23322","creation_date":"1432883689","6":"1432883689"},{"0":"5065","vim_version":"7.4","1":"7.4","script_version":"0.7.1","2":"0.7.1","version_comment":"* Fixed issue with highlighting after colorscheme change","3":"* Fixed issue with highlighting after colorscheme change","package":"filestyle-0.7.1.zip","4":"filestyle-0.7.1.zip","src_id":"23253","5":"23253","creation_date":"1430588615","6":"1430588615"},{"0":"5065","vim_version":"7.4","1":"7.4","script_version":"0.7.0","2":"0.7.0","version_comment":"* Implemented style errors fixing (experimental)\r\n* Commands enabling\/disabling plugin globally were added\r\n* Highlighting of the EOL fixed\r\n* Issue with plugin disabling for specific buffer fixed\r\n","3":"* Implemented style errors fixing (experimental)\r\n* Commands enabling\/disabling plugin globally were added\r\n* Highlighting of the EOL fixed\r\n* Issue with plugin disabling for specific buffer fixed\r\n","package":"filestyle-0.7.0.zip","4":"filestyle-0.7.0.zip","src_id":"22745","5":"22745","creation_date":"1419944768","6":"1419944768"},{"0":"5065","vim_version":"7.4","1":"7.4","script_version":"0.6.1","2":"0.6.1","version_comment":"Fixed compatibility with other plugins if Vundle is used","3":"Fixed compatibility with other plugins if Vundle is used","package":"filestyle-0.6.1.zip","4":"filestyle-0.6.1.zip","src_id":"22714","5":"22714","creation_date":"1419060262","6":"1419060262"},{"0":"5065","vim_version":"7.4","1":"7.4","script_version":"0.6.0","2":"0.6.0","version_comment":"* Configurable list of ignored file types\r\n* Plugin turns off in all windows with current buffer opened\r\n* Added highlighting of control characters","3":"* Configurable list of ignored file types\r\n* Plugin turns off in all windows with current buffer opened\r\n* Added highlighting of control characters","package":"filestyle-0.6.0.zip","4":"filestyle-0.6.0.zip","src_id":"22703","5":"22703","creation_date":"1418726099","6":"1418726099"},{"0":"5065","vim_version":"7.4","1":"7.4","script_version":"0.5.2","2":"0.5.2","version_comment":"Fixed the `undefined variable filestyle_active` error","3":"Fixed the `undefined variable filestyle_active` error","package":"filestyle-0.5.2.zip","4":"filestyle-0.5.2.zip","src_id":"22696","5":"22696","creation_date":"1418467620","6":"1418467620"},{"0":"5065","vim_version":"7.4","1":"7.4","script_version":"0.5.1","2":"0.5.1","version_comment":"Initial upload","3":"Initial upload","package":"filestyle-0.5.1.zip","4":"filestyle-0.5.1.zip","src_id":"22679","5":"22679","creation_date":"1418040874","6":"1418040874"}]},"5064":{"script_id":"5064","0":"5064","script_name":"FileSync","1":"FileSync","script_type":"utility","2":"utility","summary":"FileSync offers file synchronization functionality.","3":"FileSync offers file synchronization functionality.","description":"FileSync offers file synchronization functionality. Once you save a file, it can be synchronized to another folder. \r\n\r\nPlease see the latest update here: https:\/\/github.com\/cosminadrianpopescu\/filesync","4":"FileSync offers file synchronization functionality. Once you save a file, it can be synchronized to another folder. \r\n\r\nPlease see the latest update here: https:\/\/github.com\/cosminadrianpopescu\/filesync","install_details":"","5":"","first_name":"Cosmin","6":"Cosmin","last_name":"Popescu","7":"Popescu","releases":[{"0":"5064","vim_version":"7.0","1":"7.0","script_version":"1.0.1","2":"1.0.1","version_comment":"Fixed autoload functions","3":"Fixed autoload functions","package":"filesync.tar.gz","4":"filesync.tar.gz","src_id":"22772","5":"22772","creation_date":"1420837436","6":"1420837436"},{"0":"5064","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"filesync.zip","4":"filesync.zip","src_id":"22678","5":"22678","creation_date":"1418040829","6":"1418040829"}]},"5063":{"script_id":"5063","0":"5063","script_name":"Casetrate","1":"Casetrate","script_type":"utility","2":"utility","summary":"Modify the case of identifiers","3":"Modify the case of identifiers","description":"GitHub repository: https:\/\/github.com\/idanarye\/vim-casetrate\r\n\r\nCasetrate is a plugin for changing the case of identifiers. It can change the case to camelCase, PascalCase, snake_case, UPPER_CASE or Mixed_Case. In addition, in 'lisp' buffers it can change identifiers' case to lisp-case.","4":"GitHub repository: https:\/\/github.com\/idanarye\/vim-casetrate\r\n\r\nCasetrate is a plugin for changing the case of identifiers. It can change the case to camelCase, PascalCase, snake_case, UPPER_CASE or Mixed_Case. In addition, in 'lisp' buffers it can change identifiers' case to lisp-case.","install_details":"","5":"","first_name":"Idan","6":"Idan","last_name":"Arye","7":"Arye","releases":[{"0":"5063","vim_version":"7.0","1":"7.0","script_version":"1.1.0","2":"1.1.0","version_comment":" * Add repeat(https:\/\/github.com\/tpope\/vim-repeat) support.\r\n * Use force-case-sensitive comparison to support users that set `ignorecase`.\r\n * Fix double-sided off-by-one mistake in uppercase recognitions.","3":" * Add repeat(https:\/\/github.com\/tpope\/vim-repeat) support.\r\n * Use force-case-sensitive comparison to support users that set `ignorecase`.\r\n * Fix double-sided off-by-one mistake in uppercase recognitions.","package":"casetrate_v1.1.0.zip","4":"casetrate_v1.1.0.zip","src_id":"22676","5":"22676","creation_date":"1417985897","6":"1417985897"},{"0":"5063","vim_version":"7.0","1":"7.0","script_version":"1.0.0","2":"1.0.0","version_comment":"Initial upload","3":"Initial upload","package":"casetrate_v1.0.0.zip","4":"casetrate_v1.0.0.zip","src_id":"22671","5":"22671","creation_date":"1417895889","6":"1417895889"}]},"5062":{"script_id":"5062","0":"5062","script_name":"argwrap.vim","1":"argwrap.vim","script_type":"utility","2":"utility","summary":"Wrap and unwrap function arguments, lists and dictionaries in Vim","3":"Wrap and unwrap function arguments, lists and dictionaries in Vim","description":"# ArgWrap #\r\n\r\nArgWrap is an industrial strength argument wrapping and unwrapping extension for the [Vim](http:\/\/www.vim.org\/) text\r\neditor. It can be used for collapsing and expanding everything from function calls to array and dictionary definitions.\r\nAll operations are easily reversible and correctly preserve the indentation of the surrounding code.\r\n\r\n## Installation ##\r\n\r\n1.  Clone or otherwise download ArgWrap extension from the [GitHub](https:\/\/github.com\/FooSoft\/vim-argwrap) page.\r\n\r\n    If you are using [pathogen.vim](https:\/\/github.com\/tpope\/vim-pathogen) for plugin management you can clone the\r\n    repository directly to your bundle directory:\r\n\r\n    ```\r\n    $ git clone https:\/\/github.com\/FooSoft\/vim-argwrap ~\/.vim\/bundle\/vim-argwrap\r\n    ```\r\n\r\n2.  Create a keyboard binding for the `ArgWrap` command inside your `~\/.vimrc` file.\r\n\r\n    For example, to declare a normal mode mapping, add the following command:\r\n\r\n    ```\r\n    nnoremap  a :ArgWrap\r\n    ```\r\n\r\n## Configuration ##\r\n\r\nYou can customize the behavior of this extension by setting values for any of the following optional *buffer* and\r\n*global* configuration variables in your `.vimrc` file. Buffer variables (prefixed with `b:`) take precedence over\r\nglobal variables (prefixed with `g:`), making them ideal for configuring the behavior of this extension on a file by\r\nfile basis using `ftplugin` or `autocmd`. For example, the `argwrap_tail_comma` variable has two variants declared as\r\n`b:argwrap_tail_comma` and `g:argwrap_tail_comma`, for buffer and global scopes respectively.\r\n\r\n*   **argwrap_line_prefix**\r\n\r\n    Specifies a line prefix to be added and removed when working with languages that require newlines to be escaped.\r\n\r\n    *Line prefix disabled (default)*\r\n\r\n    ```\r\n    Foo(\r\n        wibble,\r\n        wobble,\r\n        wubble\r\n    )\r\n    ```\r\n\r\n    *Line prefix enabled for Vimscript (`let g:argwrap_line_prefix = '\\'`)*\r\n\r\n    ```\r\n    Foo(\r\n        \\wibble,\r\n        \\wobble,\r\n        \\wubble\r\n    \\)\r\n    ```\r\n\r\n*   **argwrap_padded_braces**\r\n\r\n    Specifies which brace types should be padded on the inside with spaces.\r\n\r\n    *Brace padding disabled (default)*\r\n\r\n    ```\r\n    [1, 2, 3]\r\n    {1, 2, 3}\r\n    ```\r\n\r\n    *Brace padding enabled for square brackets only (`let g:argwrap_padded_braces = '['`)*\r\n\r\n    ```\r\n    [ 1, 2, 3 ]\r\n    {1, 2, 3}\r\n    ```\r\n\r\n    *Padding can be specified for multiple brace types (`let g:argwrap_padded_braces = '[{'`)*\r\n\r\n*   **argwrap_tail_comma**\r\n\r\n    Specifies if the closing brace should be preceded with a comma when wrapping lines.\r\n\r\n    *Tail comma disabled (default)*\r\n\r\n    ```\r\n    Foo(\r\n        wibble,\r\n        wobble,\r\n        wubble\r\n    )\r\n    ```\r\n\r\n    *Tail comma enabled (`let g:argwrap_tail_comma = 1`)*\r\n\r\n    ```\r\n    Foo(\r\n        wibble,\r\n        wobble,\r\n        wubble,\r\n    )\r\n    ```\r\n\r\n*   **argwrap_wrap_closing_brace**\r\n\r\n    Specifies if the closing brace should be wrapped to a new line.\r\n\r\n    *Brace wrapping enabled (default)*\r\n\r\n    ```\r\n    Foo(\r\n        wibble,\r\n        wobble,\r\n        wubble\r\n    )\r\n    ```\r\n\r\n    *Brace wrapping disabled (`let g:argwrap_wrap_closing_brace = 0`)*\r\n\r\n    ```\r\n    Foo(\r\n        wibble,\r\n        wobble,\r\n        wubble)\r\n    ```\r\n\r\n## Usage ##\r\n\r\n1.  Position the cursor *inside* of the scope of the parenthesis, brackets or curly braces you wish to wrap\/unwrap (not\r\n    on top, before or after them).\r\n2.  Execute the keyboard binding you defined above to *toggle* the wrapping and unwrapping of arguments.\r\n\r\n## License ##\r\n\r\nMIT\r\n","4":"# ArgWrap #\r\n\r\nArgWrap is an industrial strength argument wrapping and unwrapping extension for the [Vim](http:\/\/www.vim.org\/) text\r\neditor. It can be used for collapsing and expanding everything from function calls to array and dictionary definitions.\r\nAll operations are easily reversible and correctly preserve the indentation of the surrounding code.\r\n\r\n## Installation ##\r\n\r\n1.  Clone or otherwise download ArgWrap extension from the [GitHub](https:\/\/github.com\/FooSoft\/vim-argwrap) page.\r\n\r\n    If you are using [pathogen.vim](https:\/\/github.com\/tpope\/vim-pathogen) for plugin management you can clone the\r\n    repository directly to your bundle directory:\r\n\r\n    ```\r\n    $ git clone https:\/\/github.com\/FooSoft\/vim-argwrap ~\/.vim\/bundle\/vim-argwrap\r\n    ```\r\n\r\n2.  Create a keyboard binding for the `ArgWrap` command inside your `~\/.vimrc` file.\r\n\r\n    For example, to declare a normal mode mapping, add the following command:\r\n\r\n    ```\r\n    nnoremap  a :ArgWrap\r\n    ```\r\n\r\n## Configuration ##\r\n\r\nYou can customize the behavior of this extension by setting values for any of the following optional *buffer* and\r\n*global* configuration variables in your `.vimrc` file. Buffer variables (prefixed with `b:`) take precedence over\r\nglobal variables (prefixed with `g:`), making them ideal for configuring the behavior of this extension on a file by\r\nfile basis using `ftplugin` or `autocmd`. For example, the `argwrap_tail_comma` variable has two variants declared as\r\n`b:argwrap_tail_comma` and `g:argwrap_tail_comma`, for buffer and global scopes respectively.\r\n\r\n*   **argwrap_line_prefix**\r\n\r\n    Specifies a line prefix to be added and removed when working with languages that require newlines to be escaped.\r\n\r\n    *Line prefix disabled (default)*\r\n\r\n    ```\r\n    Foo(\r\n        wibble,\r\n        wobble,\r\n        wubble\r\n    )\r\n    ```\r\n\r\n    *Line prefix enabled for Vimscript (`let g:argwrap_line_prefix = '\\'`)*\r\n\r\n    ```\r\n    Foo(\r\n        \\wibble,\r\n        \\wobble,\r\n        \\wubble\r\n    \\)\r\n    ```\r\n\r\n*   **argwrap_padded_braces**\r\n\r\n    Specifies which brace types should be padded on the inside with spaces.\r\n\r\n    *Brace padding disabled (default)*\r\n\r\n    ```\r\n    [1, 2, 3]\r\n    {1, 2, 3}\r\n    ```\r\n\r\n    *Brace padding enabled for square brackets only (`let g:argwrap_padded_braces = '['`)*\r\n\r\n    ```\r\n    [ 1, 2, 3 ]\r\n    {1, 2, 3}\r\n    ```\r\n\r\n    *Padding can be specified for multiple brace types (`let g:argwrap_padded_braces = '[{'`)*\r\n\r\n*   **argwrap_tail_comma**\r\n\r\n    Specifies if the closing brace should be preceded with a comma when wrapping lines.\r\n\r\n    *Tail comma disabled (default)*\r\n\r\n    ```\r\n    Foo(\r\n        wibble,\r\n        wobble,\r\n        wubble\r\n    )\r\n    ```\r\n\r\n    *Tail comma enabled (`let g:argwrap_tail_comma = 1`)*\r\n\r\n    ```\r\n    Foo(\r\n        wibble,\r\n        wobble,\r\n        wubble,\r\n    )\r\n    ```\r\n\r\n*   **argwrap_wrap_closing_brace**\r\n\r\n    Specifies if the closing brace should be wrapped to a new line.\r\n\r\n    *Brace wrapping enabled (default)*\r\n\r\n    ```\r\n    Foo(\r\n        wibble,\r\n        wobble,\r\n        wubble\r\n    )\r\n    ```\r\n\r\n    *Brace wrapping disabled (`let g:argwrap_wrap_closing_brace = 0`)*\r\n\r\n    ```\r\n    Foo(\r\n        wibble,\r\n        wobble,\r\n        wubble)\r\n    ```\r\n\r\n## Usage ##\r\n\r\n1.  Position the cursor *inside* of the scope of the parenthesis, brackets or curly braces you wish to wrap\/unwrap (not\r\n    on top, before or after them).\r\n2.  Execute the keyboard binding you defined above to *toggle* the wrapping and unwrapping of arguments.\r\n\r\n## License ##\r\n\r\nMIT\r\n","install_details":"","5":"","first_name":"Alex","6":"Alex","last_name":"Yatskov","7":"Yatskov","releases":[{"0":"5062","vim_version":"7.0","1":"7.0","script_version":"1.9","2":"1.9","version_comment":"Adding support for trail comma and line prefix","3":"Adding support for trail comma and line prefix","package":"vim-argwrap.tar.gz","4":"vim-argwrap.tar.gz","src_id":"23793","5":"23793","creation_date":"1450357950","6":"1450357950"},{"0":"5062","vim_version":"7.0","1":"7.0","script_version":"1.8","2":"1.8","version_comment":"misc fixes","3":"misc fixes","package":"vim-argwrap.tar.gz","4":"vim-argwrap.tar.gz","src_id":"23548","5":"23548","creation_date":"1440477934","6":"1440477934"},{"0":"5062","vim_version":"7.0","1":"7.0","script_version":"1.7","2":"1.7","version_comment":"Adding argwrap_wrap_closing_brace","3":"Adding argwrap_wrap_closing_brace","package":"vim-argwrap.tar.gz","4":"vim-argwrap.tar.gz","src_id":"23097","5":"23097","creation_date":"1427327386","6":"1427327386"},{"0":"5062","vim_version":"7.0","1":"7.0","script_version":"1.6","2":"1.6","version_comment":"Various improvements","3":"Various improvements","package":"vim-argwrap.tar.gz","4":"vim-argwrap.tar.gz","src_id":"23012","5":"23012","creation_date":"1426145569","6":"1426145569"},{"0":"5062","vim_version":"7.0","1":"7.0","script_version":"1.5","2":"1.5","version_comment":"Add \"ArgWrap\" command","3":"Add \"ArgWrap\" command","package":"vim-argwrap.tar.gz","4":"vim-argwrap.tar.gz","src_id":"22848","5":"22848","creation_date":"1422454814","6":"1422454814"},{"0":"5062","vim_version":"7.0","1":"7.0","script_version":"1.4","2":"1.4","version_comment":"Adding new customization options.","3":"Adding new customization options.","package":"vim-argwrap.tar.gz","4":"vim-argwrap.tar.gz","src_id":"22847","5":"22847","creation_date":"1422422124","6":"1422422124"},{"0":"5062","vim_version":"7.0","1":"7.0","script_version":"1.3","2":"1.3","version_comment":"Small fixes to script, documentation","3":"Small fixes to script, documentation","package":"vim-argwrap.tar.gz","4":"vim-argwrap.tar.gz","src_id":"22712","5":"22712","creation_date":"1418949596","6":"1418949596"},{"0":"5062","vim_version":"7.0","1":"7.0","script_version":"1.2","2":"1.2","version_comment":"Updating documentation","3":"Updating documentation","package":"vim-argwrap.tar.gz","4":"vim-argwrap.tar.gz","src_id":"22674","5":"22674","creation_date":"1417920848","6":"1417920848"}]},"5061":{"script_id":"5061","0":"5061","script_name":"yoda.vim","1":"yoda.vim","script_type":"ftplugin","2":"ftplugin","summary":"A VIM plug-in for completion using Clang.","3":"A VIM plug-in for completion using Clang.","description":"Yoda-vim is a Vim plug-in for code completion using libclang. Yoda-vim's features are:\r\n\r\n* Fast code completion for C\/C++ and Objective-C\/C++.\r\n* Load compilation options using your python configuration file influenced by YouCompleteMe.\r\n* Jump to definition or declaration under the cursor of the editing file.\r\n* Show code diagnostics in Vim's quickfix-window or you can use it via API as you want.\r\n* Automatically insert variable segments, substring of text of candidate supporting snake case and camel case, by one keystroke in completion (Like XCode behaivior).\r\n* Support code snippets if you have installed ultisnips.\r\n* Works on python2 and python3.\r\n\r\nEnjoy!\r\n\r\nGithub mirror: https:\/\/github.com\/kyuhi\/yoda.vim","4":"Yoda-vim is a Vim plug-in for code completion using libclang. Yoda-vim's features are:\r\n\r\n* Fast code completion for C\/C++ and Objective-C\/C++.\r\n* Load compilation options using your python configuration file influenced by YouCompleteMe.\r\n* Jump to definition or declaration under the cursor of the editing file.\r\n* Show code diagnostics in Vim's quickfix-window or you can use it via API as you want.\r\n* Automatically insert variable segments, substring of text of candidate supporting snake case and camel case, by one keystroke in completion (Like XCode behaivior).\r\n* Support code snippets if you have installed ultisnips.\r\n* Works on python2 and python3.\r\n\r\nEnjoy!\r\n\r\nGithub mirror: https:\/\/github.com\/kyuhi\/yoda.vim","install_details":"If you are using Vundle, put below code snippet in your .vimrc\r\nPlugin 'kyuhi\/yoda.vim'\r\n\r\nOr\r\n\r\nPut yoda.vim in your Vim runtime.","5":"If you are using Vundle, put below code snippet in your .vimrc\r\nPlugin 'kyuhi\/yoda.vim'\r\n\r\nOr\r\n\r\nPut yoda.vim in your Vim runtime.","first_name":"kaika ","6":"kaika ","last_name":"yuhi","7":"yuhi","releases":[{"0":"5061","vim_version":"7.4","1":"7.4","script_version":"0.8","2":"0.8","version_comment":"Initial upload","3":"Initial upload","package":"yoda.vim.zip","4":"yoda.vim.zip","src_id":"22654","5":"22654","creation_date":"1417150346","6":"1417150346"}]},"5060":{"script_id":"5060","0":"5060","script_name":"jspc.vim","1":"jspc.vim","script_type":"ftplugin","2":"ftplugin","summary":"JavaScript Parameter Complete","3":"JavaScript Parameter Complete","description":"JavaScript Parameter Complete(JSPC) is a complete function for function parameters. Such as event names, crypto algorithms, common locales.\r\n\r\ngit repo: https:\/\/github.com\/othree\/jspc.vim ","4":"JavaScript Parameter Complete(JSPC) is a complete function for function parameters. Such as event names, crypto algorithms, common locales.\r\n\r\ngit repo: https:\/\/github.com\/othree\/jspc.vim ","install_details":"Use Vundle or pathogen.vim is recommended. No special configure required. JSPC will wrap omnifunc.","5":"Use Vundle or pathogen.vim is recommended. No special configure required. JSPC will wrap omnifunc.","first_name":"wei ko","6":"wei ko","last_name":"kao","7":"kao","releases":[{"0":"5060","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"jspc.vim-1.0.0.vmb","4":"jspc.vim-1.0.0.vmb","src_id":"22653","5":"22653","creation_date":"1417149775","6":"1417149775"}]},"5059":{"script_id":"5059","0":"5059","script_name":"vim-asterisk","1":"vim-asterisk","script_type":"utility","2":"utility","summary":"*-improved","3":"*-improved","description":"\r\nSEE https:\/\/github.com\/haya14busa\/vim-asterisk","4":"\r\nSEE https:\/\/github.com\/haya14busa\/vim-asterisk","install_details":"","5":"","first_name":"haya14busa","6":"haya14busa","last_name":" ","7":" ","releases":[{"0":"5059","vim_version":"7.3","1":"7.3","script_version":"v1.0.0","2":"v1.0.0","version_comment":"1.0.0\t2015-04-04\r\n\t- Add keepCursor feature. |g:asterisk#keeppos|. This feature is based\r\n\t  on @pelodelfuego's work! https:\/\/github.com\/pelodelfuego\r\n\t- Add test\r\n\t- Fix minor bug and now it's stable\r\n","3":"1.0.0\t2015-04-04\r\n\t- Add keepCursor feature. |g:asterisk#keeppos|. This feature is based\r\n\t  on @pelodelfuego's work! https:\/\/github.com\/pelodelfuego\r\n\t- Add test\r\n\t- Fix minor bug and now it's stable\r\n","package":"vim-asterisk-1.0.0.zip","4":"vim-asterisk-1.0.0.zip","src_id":"23127","5":"23127","creation_date":"1428075914","6":"1428075914"},{"0":"5059","vim_version":"7.3","1":"7.3","script_version":"0.9.3","2":"0.9.3","version_comment":"0.9.3\t2014-12-10\r\n\t- Fix multybite handling for visual-star feature.\r\n\t- Fix |v| selection over multi lines.\r\n","3":"0.9.3\t2014-12-10\r\n\t- Fix multybite handling for visual-star feature.\r\n\t- Fix |v| selection over multi lines.\r\n","package":"vim-asterisk-0.9.3.zip","4":"vim-asterisk-0.9.3.zip","src_id":"22681","5":"22681","creation_date":"1418203716","6":"1418203716"},{"0":"5059","vim_version":"7.3","1":"7.3","script_version":"0.9.2","2":"0.9.2","version_comment":"0.9.2\t2014-12-01\r\n\t- Fix count handling for |#| motions with pattern including |\\<| and |\\>|.\r\n\t- Refactoring\r\n","3":"0.9.2\t2014-12-01\r\n\t- Fix count handling for |#| motions with pattern including |\\<| and |\\>|.\r\n\t- Refactoring\r\n","package":"vim-asterisk-0.9.2.zip","4":"vim-asterisk-0.9.2.zip","src_id":"22659","5":"22659","creation_date":"1417414465","6":"1417414465"},{"0":"5059","vim_version":"7.3","1":"7.3","script_version":"0.9.1","2":"0.9.1","version_comment":"0.9.1 2014-11-28\r\n- Show error with empty selected string","3":"0.9.1 2014-11-28\r\n- Show error with empty selected string","package":"vim-asterisk-0.9.1.zip","4":"vim-asterisk-0.9.1.zip","src_id":"22658","5":"22658","creation_date":"1417413975","6":"1417413975"},{"0":"5059","vim_version":"7.3","1":"7.3","script_version":"0.9.0","2":"0.9.0","version_comment":"Initial upload","3":"Initial upload","package":"vim-asterisk-0.9.0.zip","4":"vim-asterisk-0.9.0.zip","src_id":"22651","5":"22651","creation_date":"1417106171","6":"1417106171"}]},"5058":{"script_id":"5058","0":"5058","script_name":"emoji_complete","1":"emoji_complete","script_type":"utility","2":"utility","summary":"A plug-in for insert completion of emoji.","3":"A plug-in for insert completion of emoji.","description":"Information about the plug-in please refer to its project page on GitHub: \r\nhttps:\/\/github.com\/kyuhi\/vim-emoji-complete\r\n","4":"Information about the plug-in please refer to its project page on GitHub: \r\nhttps:\/\/github.com\/kyuhi\/vim-emoji-complete\r\n","install_details":"Put this plugin into your VIM runtime path.","5":"Put this plugin into your VIM runtime path.","first_name":"kaika ","6":"kaika ","last_name":"yuhi","7":"yuhi","releases":[{"0":"5058","vim_version":"7.4","1":"7.4","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"vim-emoji-complete.zip","4":"vim-emoji-complete.zip","src_id":"22650","5":"22650","creation_date":"1417055037","6":"1417055037"}]},"5057":{"script_id":"5057","0":"5057","script_name":"buftabline","1":"buftabline","script_type":"utility","2":"utility","summary":"Use the tabline to render buffer tabs","3":"Use the tabline to render buffer tabs","description":"Buftabline takes over the tabline and renders the buffer list in it instead of a tab list. It is designed with the ideal that it should Just Work: drop it into your setup and you\\'re done. There is only minimal configurable behavior.\r\n\r\nScreenshot, rationale and comparisons with other plugins available at\r\nhttps:\/\/github.com\/ap\/vim-buftabline","4":"Buftabline takes over the tabline and renders the buffer list in it instead of a tab list. It is designed with the ideal that it should Just Work: drop it into your setup and you\\'re done. There is only minimal configurable behavior.\r\n\r\nScreenshot, rationale and comparisons with other plugins available at\r\nhttps:\/\/github.com\/ap\/vim-buftabline","install_details":"Cloning from GitHub using a plugin manager is recommended.\r\nhttps:\/\/github.com\/ap\/vim-buftabline\r\n\r\nOtherwise download and unzip in your .vim directory.","5":"Cloning from GitHub using a plugin manager is recommended.\r\nhttps:\/\/github.com\/ap\/vim-buftabline\r\n\r\nOtherwise download and unzip in your .vim directory.","first_name":"Aristotle","6":"Aristotle","last_name":"Pagaltzis","7":"Pagaltzis","releases":[{"0":"5057","vim_version":"7.0","1":"7.0","script_version":"73b9ef5dcb","2":"73b9ef5dcb","version_comment":"Plug mapping for the last buffer shown; configurable number of plug mappings; better plug mapping error handling; support for highlighting modified buffers; better coexistence under actual tabpages; mouse support in NeoVim; Vim 7.0 compatibility; fixes for numerous small bugs","3":"Plug mapping for the last buffer shown; configurable number of plug mappings; better plug mapping error handling; support for highlighting modified buffers; better coexistence under actual tabpages; mouse support in NeoVim; Vim 7.0 compatibility; fixes for numerous small bugs","package":"buftabline.zip","4":"buftabline.zip","src_id":"27881","5":"27881","creation_date":"1641032886","6":"1641032886"}]},"5056":{"script_id":"5056","0":"5056","script_name":"css-color","1":"css-color","script_type":"utility","2":"utility","summary":"Preview colours in source code while editing","3":"Preview colours in source code while editing","description":"A very fast color keyword highlighter with context-sensitive support for many language syntaxes.\r\n\r\nOriginally an obsessively optimised fork of vimscript #2150 plus extra features:\r\n\r\n\u00e2\u0080\u00a2 multiple color highlights per line\r\n\u00e2\u0080\u00a2 rgb(), rgba(), hsl() support for CSS\r\n\u00e2\u0080\u00a2 support for various alternative CSS languages like Less and Sass\r\n\u00e2\u0080\u00a2 support for various non-CSS languages like VimL, Javascript, and Python\r\n\r\nScreenshot available at\r\nhttps:\/\/github.com\/ap\/vim-css-color","4":"A very fast color keyword highlighter with context-sensitive support for many language syntaxes.\r\n\r\nOriginally an obsessively optimised fork of vimscript #2150 plus extra features:\r\n\r\n\u00e2\u0080\u00a2 multiple color highlights per line\r\n\u00e2\u0080\u00a2 rgb(), rgba(), hsl() support for CSS\r\n\u00e2\u0080\u00a2 support for various alternative CSS languages like Less and Sass\r\n\u00e2\u0080\u00a2 support for various non-CSS languages like VimL, Javascript, and Python\r\n\r\nScreenshot available at\r\nhttps:\/\/github.com\/ap\/vim-css-color","install_details":"Cloning from GitHub using a plugin manager is recommended.\r\nhttps:\/\/github.com\/ap\/vim-css-color\r\n\r\nOtherwise download and unzip in your .vim directory.","5":"Cloning from GitHub using a plugin manager is recommended.\r\nhttps:\/\/github.com\/ap\/vim-css-color\r\n\r\nOtherwise download and unzip in your .vim directory.","first_name":"Aristotle","6":"Aristotle","last_name":"Pagaltzis","7":"Pagaltzis","releases":[{"0":"5056","vim_version":"7.0","1":"7.0","script_version":"8bf943681f","2":"8bf943681f","version_comment":"Drastically improved performance; additional improved performance in NeoVim; significantly improved colour fidelity in 256-colour terminals; support for RGBA colours in hex notation; highlighting for DOS\/Windows INI,Typescript,Elm,Clojure\/ClojureScript,QML,Vala,C\/C++,and Shell (sh\/ksh\/bash, zsh, csh, tcsh, fish) files as well as i3wm,kitty,nix,tmux,and generic .cfg configuration files","3":"Drastically improved performance; additional improved performance in NeoVim; significantly improved colour fidelity in 256-colour terminals; support for RGBA colours in hex notation; highlighting for DOS\/Windows INI,Typescript,Elm,Clojure\/ClojureScript,QML,Vala,C\/C++,and Shell (sh\/ksh\/bash, zsh, csh, tcsh, fish) files as well as i3wm,kitty,nix,tmux,and generic .cfg configuration files","package":"css-color.zip","4":"css-color.zip","src_id":"27882","5":"27882","creation_date":"1641032923","6":"1641032923"}]},"5055":{"script_id":"5055","0":"5055","script_name":"vim-www","1":"vim-www","script_type":"utility","2":"utility","summary":"Toolbox to open & search URLs from vim","3":"Toolbox to open & search URLs from vim","description":"Complete information at: https:\/\/github.com\/waiting-for-dev\/vim-www\r\n\r\nUsage\r\n\r\nvim-www allows launching a web browser from vim to open arbitrary URLs, defined favorites and search engine results.\r\n\r\nThe web browser to be used is detected automatically, but it can be manually set through g:www_launch_browser_command, using {{URL}}} as placeholder for the actual URL. E.g.:\r\n\r\nlet g:www_launch_browser_command = \"iceweasel {{URL}} &\"\r\n\r\nIn the same way, an alternative CLI browser can be set through g:www_launch_cli_browser_command. In order to work, vim-dispatch add-on must be installed. Its purpose is to open a web, for example, in a tmux pane, or in a virtual terminal if neovim and vim-dispatch-neovim are being used.\r\nFavorites and arbitrary URLs\r\n\r\n:Wopen opens any given URL. E.g.:\r\n\r\n:Wopen http:\/\/vim.org\r\n\r\nBut typing and remembering full URLs is annoying, so custom favorites can be defined in g:www_urls dictionary.\r\n\r\nSo, having in vimrc,\r\n\r\nlet g:www_urls = {\r\n  \\ 'vim' : 'http:\/\/www.vim.org',\r\n  \\ }\r\n\r\nfollowing command does the same than previous one:\r\n\r\n:Wopen vim\r\n\r\nAlso, in normal mode, wo launches the browser using WORD under cursor as URL. In visual mode it does the same but taking current text selection as URL.\r\n\r\n:Wcopen command and wco mappings do the same but using the CLI browser.\r\nSearch engines\r\n\r\n:Wsearch queries a search engine and opens the corresponding results page:\r\n\r\nE.g.:\r\n\r\n:Wsearch google how to learn vim\r\n\r\nPrevious command opens the resulting page of searching how to learn vim in google.\r\n\r\nFollowing search engines are provided by default:\r\n\r\n    bitbucket\r\n    devdocs\r\n    duckduckgo\r\n    google\r\n    github\r\n    stackoverflow\r\n    wikipedia\r\n\r\nMore search engines can be added through g:www_engines dictionary. Query is appended at the end of given URL. E.g.:\r\n\r\nlet g:www_engines = {\r\n  \\ 'youtube' : 'https:\/\/www.youtube.com\/results?search_query=',\r\n  \\ }\r\n\r\nIn normal mode, ws searches WORD under cursor, while the same mapping in visual mode searches current visual selection. In both cases, the user is prompted to choose which search engine should be used. If none is given, duckduckgo is used, but this behaviour can be changed setting g:www_default_search_engine variable. E.g.:\r\n\r\nlet g:www_default_search_engine = 'google'\r\n\r\n:Wcsearch command and wcs mappings do the same but using the CLI browser.\r\nShortcut search engines\r\n\r\nConvenient shortcuts for commonly used search engines can be defined in g:www_shortcut_engines dictionary. Having in vimrc:\r\n\r\nlet g:www_engines = {\r\n  \\ 'ruby' : 'http:\/\/ruby-doc.com\/search.html?q=',\r\n\\}\r\n\r\nlet g:www_shortcut_engines = {\r\n  \\ 'ruby': ['Docruby', 'dr', 'Doccliruby', 'dcr']\r\n\\}\r\n\r\nautomatically adds :Docruby \/ :Doccliruby commands, and dr \/ dcr mappings that work like :Wsearch \/ :Wcsearch and ws \/ wcs but using ruby straight away as search engine.\r\n\r\nRemember that user defined commands must begin with an uppercase letter.\r\n\r\nThis is very convenient to use as a quick way to consult API documentation.\r\nSessions\r\n\r\nArbitrary URLs and favorites can be grouped together under a name in g:www_sessions dictionary and opened at once using :Wsession command.\r\n\r\nHaving in vimrc:\r\n\r\nlet g:www_urls = {\r\n  \\ 'vim' : 'http:\/\/www.vim.org',\r\n  \\ }\r\n\r\nlet g:www_sessions = {\r\n  \\ 'dev' : ['vim', 'http:\/\/stackoverflow.com'],\r\n  \\ }\r\n\r\nRunning:\r\n\r\n:Wsession vim\r\n\r\nwould open http:\/\/www.vim.org and http:\/\/stackoverflow.com at once.\r\n\r\n:Wcsession command does the same but using the CLI browser.\r\nConfiguration and reference\r\n\r\nType :help vim-www for a complete reference and information about configuration.\r\nBugs\r\n\r\nOpen a bug in https:\/\/github.com\/waiting-for-dev\/vim-www\/issues\r\nContributing\r\n\r\n    Fork the project ( http:\/\/github.com\/waiting-for-dev\/vim-www\/fork )\r\n    Create your feature branch (git checkout -b my-new-feature)\r\n    Commit your changes (git commit -am 'Add some feature')\r\n    Push to the branch (git push origin my-new-feature)\r\n    Create new Pull Request\r\n\r\nVersion\r\n\r\nvim-www follows Semantic Versioning System 2.0. Current version is 1.0.0.\r\nLicense\r\n\r\nThe MIT Licence http:\/\/www.opensource.org\/licenses\/mit-license.php\r\n\r\nCopyright (c) 2014 Marc Busqu\u00c3\u00a9 P\u00c3\u00a9rez\r\n\r\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the \"Software\"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and\/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\r\n\r\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\r\n\r\nTHE SOFTWARE IS PROVIDED \"AS IS\", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.","4":"Complete information at: https:\/\/github.com\/waiting-for-dev\/vim-www\r\n\r\nUsage\r\n\r\nvim-www allows launching a web browser from vim to open arbitrary URLs, defined favorites and search engine results.\r\n\r\nThe web browser to be used is detected automatically, but it can be manually set through g:www_launch_browser_command, using {{URL}}} as placeholder for the actual URL. E.g.:\r\n\r\nlet g:www_launch_browser_command = \"iceweasel {{URL}} &\"\r\n\r\nIn the same way, an alternative CLI browser can be set through g:www_launch_cli_browser_command. In order to work, vim-dispatch add-on must be installed. Its purpose is to open a web, for example, in a tmux pane, or in a virtual terminal if neovim and vim-dispatch-neovim are being used.\r\nFavorites and arbitrary URLs\r\n\r\n:Wopen opens any given URL. E.g.:\r\n\r\n:Wopen http:\/\/vim.org\r\n\r\nBut typing and remembering full URLs is annoying, so custom favorites can be defined in g:www_urls dictionary.\r\n\r\nSo, having in vimrc,\r\n\r\nlet g:www_urls = {\r\n  \\ 'vim' : 'http:\/\/www.vim.org',\r\n  \\ }\r\n\r\nfollowing command does the same than previous one:\r\n\r\n:Wopen vim\r\n\r\nAlso, in normal mode, wo launches the browser using WORD under cursor as URL. In visual mode it does the same but taking current text selection as URL.\r\n\r\n:Wcopen command and wco mappings do the same but using the CLI browser.\r\nSearch engines\r\n\r\n:Wsearch queries a search engine and opens the corresponding results page:\r\n\r\nE.g.:\r\n\r\n:Wsearch google how to learn vim\r\n\r\nPrevious command opens the resulting page of searching how to learn vim in google.\r\n\r\nFollowing search engines are provided by default:\r\n\r\n    bitbucket\r\n    devdocs\r\n    duckduckgo\r\n    google\r\n    github\r\n    stackoverflow\r\n    wikipedia\r\n\r\nMore search engines can be added through g:www_engines dictionary. Query is appended at the end of given URL. E.g.:\r\n\r\nlet g:www_engines = {\r\n  \\ 'youtube' : 'https:\/\/www.youtube.com\/results?search_query=',\r\n  \\ }\r\n\r\nIn normal mode, ws searches WORD under cursor, while the same mapping in visual mode searches current visual selection. In both cases, the user is prompted to choose which search engine should be used. If none is given, duckduckgo is used, but this behaviour can be changed setting g:www_default_search_engine variable. E.g.:\r\n\r\nlet g:www_default_search_engine = 'google'\r\n\r\n:Wcsearch command and wcs mappings do the same but using the CLI browser.\r\nShortcut search engines\r\n\r\nConvenient shortcuts for commonly used search engines can be defined in g:www_shortcut_engines dictionary. Having in vimrc:\r\n\r\nlet g:www_engines = {\r\n  \\ 'ruby' : 'http:\/\/ruby-doc.com\/search.html?q=',\r\n\\}\r\n\r\nlet g:www_shortcut_engines = {\r\n  \\ 'ruby': ['Docruby', 'dr', 'Doccliruby', 'dcr']\r\n\\}\r\n\r\nautomatically adds :Docruby \/ :Doccliruby commands, and dr \/ dcr mappings that work like :Wsearch \/ :Wcsearch and ws \/ wcs but using ruby straight away as search engine.\r\n\r\nRemember that user defined commands must begin with an uppercase letter.\r\n\r\nThis is very convenient to use as a quick way to consult API documentation.\r\nSessions\r\n\r\nArbitrary URLs and favorites can be grouped together under a name in g:www_sessions dictionary and opened at once using :Wsession command.\r\n\r\nHaving in vimrc:\r\n\r\nlet g:www_urls = {\r\n  \\ 'vim' : 'http:\/\/www.vim.org',\r\n  \\ }\r\n\r\nlet g:www_sessions = {\r\n  \\ 'dev' : ['vim', 'http:\/\/stackoverflow.com'],\r\n  \\ }\r\n\r\nRunning:\r\n\r\n:Wsession vim\r\n\r\nwould open http:\/\/www.vim.org and http:\/\/stackoverflow.com at once.\r\n\r\n:Wcsession command does the same but using the CLI browser.\r\nConfiguration and reference\r\n\r\nType :help vim-www for a complete reference and information about configuration.\r\nBugs\r\n\r\nOpen a bug in https:\/\/github.com\/waiting-for-dev\/vim-www\/issues\r\nContributing\r\n\r\n    Fork the project ( http:\/\/github.com\/waiting-for-dev\/vim-www\/fork )\r\n    Create your feature branch (git checkout -b my-new-feature)\r\n    Commit your changes (git commit -am 'Add some feature')\r\n    Push to the branch (git push origin my-new-feature)\r\n    Create new Pull Request\r\n\r\nVersion\r\n\r\nvim-www follows Semantic Versioning System 2.0. Current version is 1.0.0.\r\nLicense\r\n\r\nThe MIT Licence http:\/\/www.opensource.org\/licenses\/mit-license.php\r\n\r\nCopyright (c) 2014 Marc Busqu\u00c3\u00a9 P\u00c3\u00a9rez\r\n\r\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the \"Software\"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and\/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\r\n\r\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\r\n\r\nTHE SOFTWARE IS PROVIDED \"AS IS\", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.","install_details":"","5":"","first_name":"Marc","6":"Marc","last_name":"Busqu\u00c3\u00a9 P\u00c3\u00a9rez","7":"Busqu\u00c3\u00a9 P\u00c3\u00a9rez","releases":[{"0":"5055","vim_version":"7.0","1":"7.0","script_version":"1.1.0","2":"1.1.0","version_comment":"- Adds cygwin support\r\n- Fixes URL escaping issues\r\n- Revisits and centralizes shell escape and dispatching for all handlers\r\n- Adds gitlab to the defaults","3":"- Adds cygwin support\r\n- Fixes URL escaping issues\r\n- Revisits and centralizes shell escape and dispatching for all handlers\r\n- Adds gitlab to the defaults","package":"vim-www-1.1.0.zip","4":"vim-www-1.1.0.zip","src_id":"24907","5":"24907","creation_date":"1484638696","6":"1484638696"},{"0":"5055","vim_version":"7.0","1":"7.0","script_version":"1.0.2","2":"1.0.2","version_comment":"- Fix using custom launch command with URLs with '#'","3":"- Fix using custom launch command with URLs with '#'","package":"vim-www-1.0.2.zip","4":"vim-www-1.0.2.zip","src_id":"24321","5":"24321","creation_date":"1465807560","6":"1465807560"},{"0":"5055","vim_version":"7.0","1":"7.0","script_version":"1.0.1","2":"1.0.1","version_comment":"- Fix bug opening URLs in MacOSX","3":"- Fix bug opening URLs in MacOSX","package":"vim-www-1.0.1.zip","4":"vim-www-1.0.1.zip","src_id":"24310","5":"24310","creation_date":"1465311885","6":"1465311885"},{"0":"5055","vim_version":"7.0","1":"7.0","script_version":"1.0.0","2":"1.0.0","version_comment":"* Separate ways between favorites (or arbitrary URLs) and search engines. `Wopen` opens the former, and `Wsearch` searches through any given search engine. Configuration variables also change.\r\n\r\n* Option to open URLs in a CLI browser using brother commands and mappings if `dispatch.vim` is installed.\r\n\r\n* Define shortcut commands and mappings to be able to search a given search engine more quickly.","3":"* Separate ways between favorites (or arbitrary URLs) and search engines. `Wopen` opens the former, and `Wsearch` searches through any given search engine. Configuration variables also change.\r\n\r\n* Option to open URLs in a CLI browser using brother commands and mappings if `dispatch.vim` is installed.\r\n\r\n* Define shortcut commands and mappings to be able to search a given search engine more quickly.","package":"vim-www-1.0.0.zip","4":"vim-www-1.0.0.zip","src_id":"24300","5":"24300","creation_date":"1464883572","6":"1464883572"},{"0":"5055","vim_version":"7.0","1":"7.0","script_version":"0.0.4","2":"0.0.4","version_comment":"* Prepend \"http:\/\/\" to url's without \":\/\/\"\r\n\r\nBug fixes\r\n* Fix opening search engine url's that are not a www tag","3":"* Prepend \"http:\/\/\" to url's without \":\/\/\"\r\n\r\nBug fixes\r\n* Fix opening search engine url's that are not a www tag","package":"vim-www.zip","4":"vim-www.zip","src_id":"23556","5":"23556","creation_date":"1440684668","6":"1440684668"},{"0":"5055","vim_version":"7.0","1":"7.0","script_version":"0.0.3","2":"0.0.3","version_comment":"Fix behaviour for URLS with \"#\" character in Linux","3":"Fix behaviour for URLS with \"#\" character in Linux","package":"vim-www-master.zip","4":"vim-www-master.zip","src_id":"22635","5":"22635","creation_date":"1416509743","6":"1416509743"},{"0":"5055","vim_version":"7.0","1":"7.0","script_version":"0.0.2","2":"0.0.2","version_comment":"Renames project to vim-www. It will be then more search engine friendly.","3":"Renames project to vim-www. It will be then more search engine friendly.","package":"vim-www-master.zip","4":"vim-www-master.zip","src_id":"22632","5":"22632","creation_date":"1416484253","6":"1416484253"},{"0":"5055","vim_version":"7.0","1":"7.0","script_version":"0.0.1","2":"0.0.1","version_comment":"Initial upload","3":"Initial upload","package":"www.vim-master.zip","4":"www.vim-master.zip","src_id":"22625","5":"22625","creation_date":"1416422640","6":"1416422640"}]},"5054":{"script_id":"5054","0":"5054","script_name":"atom-dark","1":"atom-dark","script_type":"color scheme","2":"color scheme","summary":"Dark theme inspired by Atom's default dark theme","3":"Dark theme inspired by Atom's default dark theme","description":"Dark theme inspired by Atom's default dark theme\r\n\r\nThe GitHub repo and most likely latest version can be found at https:\/\/github.com\/gosukiwi\/vim-atom-dark\/","4":"Dark theme inspired by Atom's default dark theme\r\n\r\nThe GitHub repo and most likely latest version can be found at https:\/\/github.com\/gosukiwi\/vim-atom-dark\/","install_details":"","5":"","first_name":"Federico","6":"Federico","last_name":"Ramirez","7":"Ramirez","releases":[{"0":"5054","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"atom-dark.vim","4":"atom-dark.vim","src_id":"22624","5":"22624","creation_date":"1416398533","6":"1416398533"}]},"5053":{"script_id":"5053","0":"5053","script_name":"rengbang","1":"rengbang","script_type":"utility","2":"utility","summary":"sequencial numbering with pattern","3":"sequencial numbering with pattern","description":"See https:\/\/github.com\/deris\/vim-rengbang","4":"See https:\/\/github.com\/deris\/vim-rengbang","install_details":"1. unzip the archived file you downloaded. \r\n\r\n2. copy files in autoload\/ and plugin\/ to your Vim runtime path.","5":"1. unzip the archived file you downloaded. \r\n\r\n2. copy files in autoload\/ and plugin\/ to your Vim runtime path.","first_name":"deris","6":"deris","last_name":" ","7":" ","releases":[{"0":"5053","vim_version":"7.3","1":"7.3","script_version":"1.0.0","2":"1.0.0","version_comment":"Initial upload","3":"Initial upload","package":"vim-rengbang-1.0.0.zip","4":"vim-rengbang-1.0.0.zip","src_id":"22618","5":"22618","creation_date":"1416154577","6":"1416154577"}]},"5052":{"script_id":"5052","0":"5052","script_name":"shot-f","1":"shot-f","script_type":"utility","2":"utility","summary":"highlights the characters where the cursor can move directly (by f,F,t,T)","3":"highlights the characters where the cursor can move directly (by f,F,t,T)","description":"See https:\/\/github.com\/deris\/vim-shot-f","4":"See https:\/\/github.com\/deris\/vim-shot-f","install_details":"1. unzip the archived file you downloaded. \r\n\r\n2. copy files in autoload\/ and plugin\/ to your Vim runtime path. \r\n\r\n3. f, F, t, T mappings are overwritten automatically. ","5":"1. unzip the archived file you downloaded. \r\n\r\n2. copy files in autoload\/ and plugin\/ to your Vim runtime path. \r\n\r\n3. f, F, t, T mappings are overwritten automatically. ","first_name":"deris","6":"deris","last_name":" ","7":" ","releases":[{"0":"5052","vim_version":"7.0","1":"7.0","script_version":"1.0.0","2":"1.0.0","version_comment":"Initial upload","3":"Initial upload","package":"vim-shot-f-1.0.0.zip","4":"vim-shot-f-1.0.0.zip","src_id":"22617","5":"22617","creation_date":"1416153099","6":"1416153099"}]},"5051":{"script_id":"5051","0":"5051","script_name":"directionalWindowResizer","1":"directionalWindowResizer","script_type":"utility","2":"utility","summary":"Adjust window size with Ctrl +jklh","3":"Adjust window size with Ctrl +jklh","description":"The idea behind this plugin is to allow users to resize windows by using the Ctrl key (or something else the user may choose) + whatever they have assigned to     &  which by default is obviously jkhl.\r\n\r\nTherefore, by default, the windows adjustment functions in directionalWindowResizer.vim are  set to  for down,  for up,  for right &  for left\r\nThese mappings are at the very top of the file, adjust them to whatever suits your needs\r\n\r\nThe behaviour of it is as follows:\r\nWhatever window is currently selected is the window that is going to be resized. \r\nCtrl j - if bottom most window selected, window size is reduced by 1\r\n          - for all other windows the bottom border is pushed downwards by 1\r\nCtrl k - if top most window selected, window size is reduced by 1\r\n           - for all other windows the top border is pushed upwards by 1\r\nCtrl l - if right most window selected, window size is reduced by 1\r\n          - for all other windows the right border is pushed to the right by 1\r\nCtrl h - if left most window selected, window size is reduced by 1\r\n           - for all other windows the left border is pushed to the left by 1\r\n\r\nIf you only have 1 window or if you only have vertically split windows Ctrl j & \r\nCtrl k will not work \u00e2\u0080\u0093 ie if you only have vertical splits why would you want to reduce all their sizes?  Similarily if you only have 1 window or you only have horizontally split windows Ctrl l & Ctrl h won't work either.","4":"The idea behind this plugin is to allow users to resize windows by using the Ctrl key (or something else the user may choose) + whatever they have assigned to     &  which by default is obviously jkhl.\r\n\r\nTherefore, by default, the windows adjustment functions in directionalWindowResizer.vim are  set to  for down,  for up,  for right &  for left\r\nThese mappings are at the very top of the file, adjust them to whatever suits your needs\r\n\r\nThe behaviour of it is as follows:\r\nWhatever window is currently selected is the window that is going to be resized. \r\nCtrl j - if bottom most window selected, window size is reduced by 1\r\n          - for all other windows the bottom border is pushed downwards by 1\r\nCtrl k - if top most window selected, window size is reduced by 1\r\n           - for all other windows the top border is pushed upwards by 1\r\nCtrl l - if right most window selected, window size is reduced by 1\r\n          - for all other windows the right border is pushed to the right by 1\r\nCtrl h - if left most window selected, window size is reduced by 1\r\n           - for all other windows the left border is pushed to the left by 1\r\n\r\nIf you only have 1 window or if you only have vertically split windows Ctrl j & \r\nCtrl k will not work \u00e2\u0080\u0093 ie if you only have vertical splits why would you want to reduce all their sizes?  Similarily if you only have 1 window or you only have horizontally split windows Ctrl l & Ctrl h won't work either.","install_details":"Just put the script in your vimfiles\/plugin folder","5":"Just put the script in your vimfiles\/plugin folder","first_name":"C","6":"C","last_name":"M","7":"M","releases":[{"0":"5051","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"directionalWindowResizer.vim","4":"directionalWindowResizer.vim","src_id":"22607","5":"22607","creation_date":"1415333920","6":"1415333920"}]},"5050":{"script_id":"5050","0":"5050","script_name":"numbers.vim","1":"numbers.vim","script_type":"utility","2":"utility","summary":"plugin for intelligently toggling line numbers.","3":"plugin for intelligently toggling line numbers.","description":"numbers.vim\r\n===========\r\nGithub: https:\/\/github.com\/b3niup\/numbers.vim\r\n\r\n\r\nnumbers.vim is a plugin for intelligently toggling line numbers.  \r\nIt is a fork of @myusuf3 plugin.\r\n\r\nThis plugin alternates between relative (`relativenumber`), absolute (`number`)  \r\nand hidden line numbering for active window depending on the mode you are in.\r\n\r\nIn `hidden` mode all event-based mode changes are turned off to keep numbers  \r\nhidden untill next `NumbersToggle` or `NumbersEnable` call.\r\n\r\nCommands are included for toggling the line numbering method and for enabling and disabling the plugin.\r\n\r\n\r\nHiding numbers in plugins and files\r\n-----------------------------------\r\n\r\nIf you would like to hide numbers in vim plugins or in files with specified filetype you can set custom g:numbers_exclude list in your .vimrc:\r\n\r\n    let g:numbers_exclude = ['nerdtree', 'html']\r\n\r\nThis example will hide numbers in NERD Tree and all html files.\r\n\r\nBy default plugin excludes following filetypes:\r\n\r\n    let g:numbers_exclude = ['minibufexpl', 'nerdtree', 'unite', 'tagbar', 'startify', 'gundo', 'vimshell', 'w3m']\r\n\r\nBe sure to include this superset in your .vimrc if you only would like to extend it.\r\n\r\n\r\nUsage\r\n-----\r\n\r\nOnce installed, no action is *required* on your part.  \r\nBut for convenience, you may want to add mappings in your `.vimrc` for some of the commands, e.g.,\r\n\r\n    nnoremap   :NumbersToggle\r\n\r\n\r\nIt is though *strongly recommended* to use following mapping:\r\n\r\n    inoremap  \r\n\r\nIt is a workaround for issue where `InsertLeave` event is not working with Ctrl+c.  \r\nAnother way to fix this is add `autocmd CursorMoved * :call NumbersReset()` in `NumbersEnable()` function   \r\naround line 104 in `plugin\/numbers.vim`, but personally I do not like idea of calling even such light function with every cursor move.","4":"numbers.vim\r\n===========\r\nGithub: https:\/\/github.com\/b3niup\/numbers.vim\r\n\r\n\r\nnumbers.vim is a plugin for intelligently toggling line numbers.  \r\nIt is a fork of @myusuf3 plugin.\r\n\r\nThis plugin alternates between relative (`relativenumber`), absolute (`number`)  \r\nand hidden line numbering for active window depending on the mode you are in.\r\n\r\nIn `hidden` mode all event-based mode changes are turned off to keep numbers  \r\nhidden untill next `NumbersToggle` or `NumbersEnable` call.\r\n\r\nCommands are included for toggling the line numbering method and for enabling and disabling the plugin.\r\n\r\n\r\nHiding numbers in plugins and files\r\n-----------------------------------\r\n\r\nIf you would like to hide numbers in vim plugins or in files with specified filetype you can set custom g:numbers_exclude list in your .vimrc:\r\n\r\n    let g:numbers_exclude = ['nerdtree', 'html']\r\n\r\nThis example will hide numbers in NERD Tree and all html files.\r\n\r\nBy default plugin excludes following filetypes:\r\n\r\n    let g:numbers_exclude = ['minibufexpl', 'nerdtree', 'unite', 'tagbar', 'startify', 'gundo', 'vimshell', 'w3m']\r\n\r\nBe sure to include this superset in your .vimrc if you only would like to extend it.\r\n\r\n\r\nUsage\r\n-----\r\n\r\nOnce installed, no action is *required* on your part.  \r\nBut for convenience, you may want to add mappings in your `.vimrc` for some of the commands, e.g.,\r\n\r\n    nnoremap   :NumbersToggle\r\n\r\n\r\nIt is though *strongly recommended* to use following mapping:\r\n\r\n    inoremap  \r\n\r\nIt is a workaround for issue where `InsertLeave` event is not working with Ctrl+c.  \r\nAnother way to fix this is add `autocmd CursorMoved * :call NumbersReset()` in `NumbersEnable()` function   \r\naround line 104 in `plugin\/numbers.vim`, but personally I do not like idea of calling even such light function with every cursor move.","install_details":"Using vundle or pathogen for installation is recommended.\r\n\r\nFor vundle users, add the following to your `.vimrc` and then run a `:BundleInstall`:\r\n\r\n    Bundle \"b3niup\/numbers.vim\"\r\n\r\nFor pathogen users, clone the repo:\r\n\r\n    git clone https:\/\/github.com\/b3niup\/numbers.vim.git ~\/.vim\/bundle\/numbers\r\n\r\nIf you really would like to install plugin manually:\r\n\r\n    Download the plugin and paste it into your plugin directory.\r\n\r\nOnce installed, no action is *required* on your part.  ","5":"Using vundle or pathogen for installation is recommended.\r\n\r\nFor vundle users, add the following to your `.vimrc` and then run a `:BundleInstall`:\r\n\r\n    Bundle \"b3niup\/numbers.vim\"\r\n\r\nFor pathogen users, clone the repo:\r\n\r\n    git clone https:\/\/github.com\/b3niup\/numbers.vim.git ~\/.vim\/bundle\/numbers\r\n\r\nIf you really would like to install plugin manually:\r\n\r\n    Download the plugin and paste it into your plugin directory.\r\n\r\nOnce installed, no action is *required* on your part.  ","first_name":"Benedykt","6":"Benedykt","last_name":"Przyby\u0142o","7":"Przybyło","releases":[{"0":"5050","vim_version":"7.3","1":"7.3","script_version":"v0.5.0","2":"v0.5.0","version_comment":"Initial upload","3":"Initial upload","package":"numbers.vim.zip","4":"numbers.vim.zip","src_id":"22605","5":"22605","creation_date":"1415210740","6":"1415210740"}]},"5049":{"script_id":"5049","0":"5049","script_name":"ab-prefix","1":"ab-prefix","script_type":"ftplugin","2":"ftplugin","summary":"Conditionally expand abbreviations on a matching prefix.","3":"Conditionally expand abbreviations on a matching prefix.","description":"# vim-ab-prefix\r\n\r\nThis plugin provides the ability to define abbreviations that expand only if a particular prefix is matched.\r\n\r\nThe main reason for writing this plugin was to make typing text into TeX easier. Many default abbreviations for TeX are provided.\r\n\r\n## Example.\r\n\r\nTyping\r\n\r\n    By Fourier inversion (th~Finv}),\r\n    $$\r\n        \\vp(x) = \\int_R2 e^{-2\\pi i x \\cdot \\xi} \\hat \\vp(\\xi) dxi.\r\n    $$\r\n\r\nproduces\r\n\r\n    By Fourier inversion (theorem~\\ref{thmFinv}),\r\n    \\begin{equation*}\r\n        \\varphi(x) = \\int_{\\R^2} e^{-2\\pi i x \\cdot \\xi} \\hat \\vp(\\xi) \\, d\\xi.\r\n    \\end{equation*}\r\n\r\nIf you also have the [tex_autoclose](http:\/\/www.vim.org\/scripts\/script.php?script_id=920) plugin installed, then you can type `\\en` to close any open environment.\r\n\r\n## Links.\r\n\r\n* [Github page](https:\/\/github.com\/gi1242\/vim-ab-prefix)","4":"# vim-ab-prefix\r\n\r\nThis plugin provides the ability to define abbreviations that expand only if a particular prefix is matched.\r\n\r\nThe main reason for writing this plugin was to make typing text into TeX easier. Many default abbreviations for TeX are provided.\r\n\r\n## Example.\r\n\r\nTyping\r\n\r\n    By Fourier inversion (th~Finv}),\r\n    $$\r\n        \\vp(x) = \\int_R2 e^{-2\\pi i x \\cdot \\xi} \\hat \\vp(\\xi) dxi.\r\n    $$\r\n\r\nproduces\r\n\r\n    By Fourier inversion (theorem~\\ref{thmFinv}),\r\n    \\begin{equation*}\r\n        \\varphi(x) = \\int_{\\R^2} e^{-2\\pi i x \\cdot \\xi} \\hat \\vp(\\xi) \\, d\\xi.\r\n    \\end{equation*}\r\n\r\nIf you also have the [tex_autoclose](http:\/\/www.vim.org\/scripts\/script.php?script_id=920) plugin installed, then you can type `\\en` to close any open environment.\r\n\r\n## Links.\r\n\r\n* [Github page](https:\/\/github.com\/gi1242\/vim-ab-prefix)","install_details":"Put the contents of plugin\/ in your ~\/.vim\/plugin directory, the contents of doc\/ in your ~\/.vim\/doc directory.\r\n\r\nIf you also want the many pre-defined TeX abbreviations, then put the contents of ftplugin\/ in your ~\/.vim\/ftplugin directory.\r\n","5":"Put the contents of plugin\/ in your ~\/.vim\/plugin directory, the contents of doc\/ in your ~\/.vim\/doc directory.\r\n\r\nIf you also want the many pre-defined TeX abbreviations, then put the contents of ftplugin\/ in your ~\/.vim\/ftplugin directory.\r\n","first_name":"gi1242","6":"gi1242","last_name":"gi1242","7":"gi1242","releases":[{"0":"5049","vim_version":"7.3","1":"7.3","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"ab-prefix.xz","4":"ab-prefix.xz","src_id":"22604","5":"22604","creation_date":"1415151464","6":"1415151464"}]},"5048":{"script_id":"5048","0":"5048","script_name":"RootIgnore","1":"RootIgnore","script_type":"utility","2":"utility","summary":"Set 'wildignore' from git repo root","3":"Set 'wildignore' from git repo root","description":"Set 'wildignore' from git repo root.\r\n\r\nSee github https:\/\/github.com\/octref\/rootignore.\r\n\r\nAdapted from gitignore  by Adam Bellaire.\r\n\r\nThis plugin is designed to complement CtrlP.\r\nThere is no easy way to:\r\n1. Restrict search results to files under current directory\r\n2. Honor .gitignore in repo root\r\nat the same time.\r\n\r\nAdam Bellaire's script honors .gitignore when Vim is opened at repo root, but not when Vim is opened in subfolders under repo root.\r\n\r\nIf this plugin is present, when you cd foo\/bar\/ and open Vim, and suppose foo\/.gitingore ignores _*, CtrlP ignores foo\/bar\/_build and all results are under foo\/bar\/.","4":"Set 'wildignore' from git repo root.\r\n\r\nSee github https:\/\/github.com\/octref\/rootignore.\r\n\r\nAdapted from gitignore  by Adam Bellaire.\r\n\r\nThis plugin is designed to complement CtrlP.\r\nThere is no easy way to:\r\n1. Restrict search results to files under current directory\r\n2. Honor .gitignore in repo root\r\nat the same time.\r\n\r\nAdam Bellaire's script honors .gitignore when Vim is opened at repo root, but not when Vim is opened in subfolders under repo root.\r\n\r\nIf this plugin is present, when you cd foo\/bar\/ and open Vim, and suppose foo\/.gitingore ignores _*, CtrlP ignores foo\/bar\/_build and all results are under foo\/bar\/.","install_details":"Vundle installation is recommended.\r\n\r\nAdd this to your .vimrc:\r\nplugin 'octref\/RootIgnore'","5":"Vundle installation is recommended.\r\n\r\nAdd this to your .vimrc:\r\nplugin 'octref\/RootIgnore'","first_name":"Pine","6":"Pine","last_name":"Wu","7":"Wu","releases":[{"0":"5048","vim_version":"7.0","1":"7.0","script_version":"0.3","2":"0.3","version_comment":"Able to use .gitignore even in non-git folder.\r\nCan use a global ~\/.gitignore.","3":"Able to use .gitignore even in non-git folder.\r\nCan use a global ~\/.gitignore.","package":"RootIgnore.tar.gz","4":"RootIgnore.tar.gz","src_id":"23506","5":"23506","creation_date":"1438963295","6":"1438963295"},{"0":"5048","vim_version":"7.0","1":"7.0","script_version":"0.2.1","2":"0.2.1","version_comment":"Add g:RootIgnoreUseHome which allows ignoring ~\/.gitignore.","3":"Add g:RootIgnoreUseHome which allows ignoring ~\/.gitignore.","package":"RootIgnore.tar.gz","4":"RootIgnore.tar.gz","src_id":"22962","5":"22962","creation_date":"1425188990","6":"1425188990"},{"0":"5048","vim_version":"7.0","1":"7.0","script_version":"0.2","2":"0.2","version_comment":"Resolve folder path in gitignore to path relative to current working dir.","3":"Resolve folder path in gitignore to path relative to current working dir.","package":"RootIgnore.tar.gz","4":"RootIgnore.tar.gz","src_id":"22882","5":"22882","creation_date":"1423204937","6":"1423204937"},{"0":"5048","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"RootIgnore.tar.gz","4":"RootIgnore.tar.gz","src_id":"22595","5":"22595","creation_date":"1414978021","6":"1414978021"}]},"5047":{"script_id":"5047","0":"5047","script_name":"VIntSearch","1":"VIntSearch","script_type":"utility","2":"utility","summary":"\"One should be able to jump between all kinds of search results\".","3":"\"One should be able to jump between all kinds of search results\".","description":"More information : https:\/\/github.com\/yssl\/VIntSearch\r\n\r\nScreenshots:\r\n\r\n- Symbol search\r\n![symbol-search](https:\/\/cloud.githubusercontent.com\/assets\/5915359\/9022502\/5c6329fe-38b2-11e5-8d36-78cbf380bb3a.png)\r\n\r\n- Text search\r\n![text-search](https:\/\/cloud.githubusercontent.com\/assets\/5915359\/9022494\/468a46e4-38b2-11e5-93f9-5830e9c351da.png)\r\n\r\n- File search\r\n![file-search](https:\/\/cloud.githubusercontent.com\/assets\/5915359\/9022503\/63e29bf6-38b2-11e5-9379-c40285ac3fd1.png)\r\n\r\n- Search stack\r\n![search-stack](https:\/\/cloud.githubusercontent.com\/assets\/5915359\/9022504\/6f103236-38b2-11e5-8e27-2506e8e88f4c.png)\r\n\r\n\r\n==============================================================================\r\n1. Introduction                                             *VIntSearch-intro*\r\n\r\n|VIntSearch| is a vim plugin providing an integrated interface across various\r\ntypes of searches. It currently supports symbol search, text search, and file search.\r\nSearch results are given in the quickfix window and a user can conviniently \r\nmove forward \/ backward through the integrated search history.\r\nVIntSearch means Vim Integrated Search.\r\n\r\n## Features\r\n\r\n- Quickfix-listed search results for all types of searches\r\n\r\n- Integrated search stack containing search history for all types of searches \r\n  (similar to vim's tag stack, but more general one)\r\n\r\n- Unified search path for all search types\r\n\r\n- Stacking not only search keywords and their position, but also search results \r\n  in the quickfix\r\n\r\n- Search keyword can be from a word under the cursor, visually selected text,\r\n  or any string you type.\r\n\r\n==============================================================================\r\n2. Getting Started                                 *VIntSearch-gettingstarted*\r\n\r\n1. You need Exuberant Ctags to fully use this plugin. If you don't have it,\r\n   please install it first: `sudo apt-get install exuberant-ctags`.\r\n\r\n2. Install this plugin.\r\n\r\n3. Open one of your source files with vim.\r\n\r\n4. Build a tag file by typing |:VIntSearchBuildSymbolDB|. The tag file will be \r\n   created in the nearest ancestor dir of the source file that contains \r\n   a repository dir such as `.git`,\r\n   or in the current working dir if the source file is not managed by any \r\n   version control system. \r\n   (You can change this behavior via `g:vintsearch_searchpathmode`)\r\n\r\n5. Note that your `set tags=...` setting should have `.\/tags;,tags;` to use \r\n   the generated tag file. \r\n   (The name of the tag file can be changed by setting |g:vintsearch_tagfilename|)\r\n\r\n6. Move the cursor to one of the functions or variables. \r\n   Typing |:VIntSearchCursor| symbol n l or |:VIntSearchCursor| text n l will \r\n   give search results in the quickfix window. \r\n   Typing |:VIntSearchPrintStack| will show the search stack.\r\n\r\n==============================================================================\r\n3. Search Types \/ Commands                            *VIntSearch-searchtypes*\r\n\r\nVIntSearch supports symbol search, text search, and file search.\r\nCurrently, available search commands for each type of search are as follows:\r\n\r\n- Symbol search\r\n\t- ctags\r\n- Text search\r\n\t- grep\r\n- File search\r\n\t- find\r\n\r\nYou can set the default commands for search types via `g:vintsearch_symbol_defaultcmd`,\r\n`g:vintsearch_text_defaultcmd`, and `g:vintsearch_file_defaultcmd`.\r\n\r\n==============================================================================\r\n4. Search Path \/ Tag Commands               *VIntSearch-searchpathtagcommands*\r\n\r\nThe search path is a directory 1) that is recursively searched by grep, \r\n2) that is the root of the entire source directory tree for which a tag file is generated,\r\nand 3) where the tag file is located.\r\nIt is determined by |g:vintsearch_searchpathmode|.\r\n\r\n*:VIntSearchPrintPath*, *:VSpath*    \r\nPrint current search path.\r\n\r\n*:VIntSearchBuildSymbolDB*, *:VSbuild*   \r\nBuild a symbol db file for the search path.\r\n\r\n==============================================================================\r\n5. Search Commands                                 *VIntSearch-searchcommands*\r\n\r\n*:VSsymbol* [keyword]  \r\nSearch symbol for [keyword] (by default using ctags).\r\n\r\n*:VStext* [keyword] [options]  \r\nSearch text for [keyword] with [options] (by default using grep, [option] is grep option).\r\n[keyword] can be double-quoted and the argument order can be changed.  \r\n\r\nFor example:\r\n```\r\n:VStext tags\r\n:VStext \"let tags\"\r\n:VStext tags -i\r\n:VStext -i tags\r\n:VStext \"let tags\" -i\r\n```\r\n(See ```man grep``` for more details about [options])\r\n\r\n*:VSfile* [keyword] [options]  \r\nSearch file for [keyword] with [options] (by default using find).\r\nCurently only works with -path options of find command.  \r\n\r\nFor example,\r\n```\r\n:VSfind *test-class.cpp\r\n```\r\n\r\n*:VScftext* [keyword] [options]  \r\nSearch text for [keyword] with [options] in the current file.\r\n\r\n--------------------\r\n*:VIntSearch* [search type] [keyword] [options]  \r\nA search command taking a search type as an argument.\r\n\r\n[search type] can be one of:\r\n- symbol\r\n- text\r\n- file\r\n- cftext\r\n\r\nFor example,\r\n`:VIntSearch text \"this is\"` is same to `:VStext \"this is\"`.\r\n\r\n*:VIntSearchCmd* [search type] [search command] [keyword] [options]  \r\nA search command taking a search type and a search command as arguments.\r\nFor example,\r\n`:VIntSearchCmd text grep \"this is\"` is same to `:VStext \"this is\"`\r\nwith `grep` as the default text search command.\r\n\r\n--------------------\r\n*:VIntSearchCursor* [search type] [vimmode] [action]  \r\nSearch for keyword under the cursor with a specified [search type].\r\n\r\n[vimmode] can be one of:  \r\n- 'n' : Use this if vim is in normal mode. Then keyword is the word under the cursor.  \r\n- 'v' : Use this if vim is in visual mode. Then keyword is the visually selected text.\r\n\r\n[action] can be one of:  \r\n- 'l' : List search result in the quickfix window and open the quickfix window.\r\n- 'j' : Jump to the first search result. The quickfix window is also updated but not opened.\r\n\r\n*:VIntSearchCursorCmd* [search type] [search command] [vimmode] [action]  \r\nSearch for keyword under the cursor with a specified [search type] and a\r\n[search command].\r\n\r\n==============================================================================\r\n6. Stack Commands                                   *VIntSearch-stackcommands*\r\n\r\nSearch stack contains your search history - search keywords you jumped to,\r\nfrom which file, and search results in the quickfix also.\r\nYou can browse your source code more easily by moving forward and backward \r\nin the search stack.\r\n\r\n*:VIntSearchPrintStack*, *:VSstack*  \r\nPrint current search stack.\r\n\r\n*:VIntSearchMoveBackward*, *:VSbwd*  \r\nMove backward in the search stack.\r\n\r\n*:VIntSearchMoveForward*, *:VSfwd*  \r\nMove forward in the search stack.\r\n\r\n*:VIntSearchClearStack*, *:VSclear*  \r\nClear the search stack.\r\n\r\n*:VScc*  \r\n*:VScnext*  \r\n*:VScprev*  \r\nReplacement of vim's |:cc|, |:cnext|, and |:cprev| commands.\r\nJumping to a new quickFix item should be done ONLY using these commands. \r\nIf not, the jump will not be reflected in VIntSearch's search stack . \r\n- If you're using any key mapings for |:cnext| or |:cprev|, you can just replace them \r\nwith |:VScnext| and |:VScprev|. \r\n- When you `Enter` or `Double-click on a quickfix item, VIntSearch will automatically \r\ncall |:VScc| instead of vim's |:cc| command.\r\n\r\nYou can disable this VIntSearch's default `Enter` behavior \r\nusing |g:vintsearch_enable_default_quickfix_enter|.\r\n\r\n|:VScc| also can be used in other plugins that override vim's |:cc| command,\r\nsuch as [QFEnter](http:\/\/www.vim.org\/scripts\/script.php?script_id=4778).\r\n(For example, you can register |:VScc| as QFEnter's \"cc\" command by adding\r\n`let g:qfenter_cc_cmd = 'VScc ##'` in your .vimrc.)\r\n","4":"More information : https:\/\/github.com\/yssl\/VIntSearch\r\n\r\nScreenshots:\r\n\r\n- Symbol search\r\n![symbol-search](https:\/\/cloud.githubusercontent.com\/assets\/5915359\/9022502\/5c6329fe-38b2-11e5-8d36-78cbf380bb3a.png)\r\n\r\n- Text search\r\n![text-search](https:\/\/cloud.githubusercontent.com\/assets\/5915359\/9022494\/468a46e4-38b2-11e5-93f9-5830e9c351da.png)\r\n\r\n- File search\r\n![file-search](https:\/\/cloud.githubusercontent.com\/assets\/5915359\/9022503\/63e29bf6-38b2-11e5-9379-c40285ac3fd1.png)\r\n\r\n- Search stack\r\n![search-stack](https:\/\/cloud.githubusercontent.com\/assets\/5915359\/9022504\/6f103236-38b2-11e5-8e27-2506e8e88f4c.png)\r\n\r\n\r\n==============================================================================\r\n1. Introduction                                             *VIntSearch-intro*\r\n\r\n|VIntSearch| is a vim plugin providing an integrated interface across various\r\ntypes of searches. It currently supports symbol search, text search, and file search.\r\nSearch results are given in the quickfix window and a user can conviniently \r\nmove forward \/ backward through the integrated search history.\r\nVIntSearch means Vim Integrated Search.\r\n\r\n## Features\r\n\r\n- Quickfix-listed search results for all types of searches\r\n\r\n- Integrated search stack containing search history for all types of searches \r\n  (similar to vim's tag stack, but more general one)\r\n\r\n- Unified search path for all search types\r\n\r\n- Stacking not only search keywords and their position, but also search results \r\n  in the quickfix\r\n\r\n- Search keyword can be from a word under the cursor, visually selected text,\r\n  or any string you type.\r\n\r\n==============================================================================\r\n2. Getting Started                                 *VIntSearch-gettingstarted*\r\n\r\n1. You need Exuberant Ctags to fully use this plugin. If you don't have it,\r\n   please install it first: `sudo apt-get install exuberant-ctags`.\r\n\r\n2. Install this plugin.\r\n\r\n3. Open one of your source files with vim.\r\n\r\n4. Build a tag file by typing |:VIntSearchBuildSymbolDB|. The tag file will be \r\n   created in the nearest ancestor dir of the source file that contains \r\n   a repository dir such as `.git`,\r\n   or in the current working dir if the source file is not managed by any \r\n   version control system. \r\n   (You can change this behavior via `g:vintsearch_searchpathmode`)\r\n\r\n5. Note that your `set tags=...` setting should have `.\/tags;,tags;` to use \r\n   the generated tag file. \r\n   (The name of the tag file can be changed by setting |g:vintsearch_tagfilename|)\r\n\r\n6. Move the cursor to one of the functions or variables. \r\n   Typing |:VIntSearchCursor| symbol n l or |:VIntSearchCursor| text n l will \r\n   give search results in the quickfix window. \r\n   Typing |:VIntSearchPrintStack| will show the search stack.\r\n\r\n==============================================================================\r\n3. Search Types \/ Commands                            *VIntSearch-searchtypes*\r\n\r\nVIntSearch supports symbol search, text search, and file search.\r\nCurrently, available search commands for each type of search are as follows:\r\n\r\n- Symbol search\r\n\t- ctags\r\n- Text search\r\n\t- grep\r\n- File search\r\n\t- find\r\n\r\nYou can set the default commands for search types via `g:vintsearch_symbol_defaultcmd`,\r\n`g:vintsearch_text_defaultcmd`, and `g:vintsearch_file_defaultcmd`.\r\n\r\n==============================================================================\r\n4. Search Path \/ Tag Commands               *VIntSearch-searchpathtagcommands*\r\n\r\nThe search path is a directory 1) that is recursively searched by grep, \r\n2) that is the root of the entire source directory tree for which a tag file is generated,\r\nand 3) where the tag file is located.\r\nIt is determined by |g:vintsearch_searchpathmode|.\r\n\r\n*:VIntSearchPrintPath*, *:VSpath*    \r\nPrint current search path.\r\n\r\n*:VIntSearchBuildSymbolDB*, *:VSbuild*   \r\nBuild a symbol db file for the search path.\r\n\r\n==============================================================================\r\n5. Search Commands                                 *VIntSearch-searchcommands*\r\n\r\n*:VSsymbol* [keyword]  \r\nSearch symbol for [keyword] (by default using ctags).\r\n\r\n*:VStext* [keyword] [options]  \r\nSearch text for [keyword] with [options] (by default using grep, [option] is grep option).\r\n[keyword] can be double-quoted and the argument order can be changed.  \r\n\r\nFor example:\r\n```\r\n:VStext tags\r\n:VStext \"let tags\"\r\n:VStext tags -i\r\n:VStext -i tags\r\n:VStext \"let tags\" -i\r\n```\r\n(See ```man grep``` for more details about [options])\r\n\r\n*:VSfile* [keyword] [options]  \r\nSearch file for [keyword] with [options] (by default using find).\r\nCurently only works with -path options of find command.  \r\n\r\nFor example,\r\n```\r\n:VSfind *test-class.cpp\r\n```\r\n\r\n*:VScftext* [keyword] [options]  \r\nSearch text for [keyword] with [options] in the current file.\r\n\r\n--------------------\r\n*:VIntSearch* [search type] [keyword] [options]  \r\nA search command taking a search type as an argument.\r\n\r\n[search type] can be one of:\r\n- symbol\r\n- text\r\n- file\r\n- cftext\r\n\r\nFor example,\r\n`:VIntSearch text \"this is\"` is same to `:VStext \"this is\"`.\r\n\r\n*:VIntSearchCmd* [search type] [search command] [keyword] [options]  \r\nA search command taking a search type and a search command as arguments.\r\nFor example,\r\n`:VIntSearchCmd text grep \"this is\"` is same to `:VStext \"this is\"`\r\nwith `grep` as the default text search command.\r\n\r\n--------------------\r\n*:VIntSearchCursor* [search type] [vimmode] [action]  \r\nSearch for keyword under the cursor with a specified [search type].\r\n\r\n[vimmode] can be one of:  \r\n- 'n' : Use this if vim is in normal mode. Then keyword is the word under the cursor.  \r\n- 'v' : Use this if vim is in visual mode. Then keyword is the visually selected text.\r\n\r\n[action] can be one of:  \r\n- 'l' : List search result in the quickfix window and open the quickfix window.\r\n- 'j' : Jump to the first search result. The quickfix window is also updated but not opened.\r\n\r\n*:VIntSearchCursorCmd* [search type] [search command] [vimmode] [action]  \r\nSearch for keyword under the cursor with a specified [search type] and a\r\n[search command].\r\n\r\n==============================================================================\r\n6. Stack Commands                                   *VIntSearch-stackcommands*\r\n\r\nSearch stack contains your search history - search keywords you jumped to,\r\nfrom which file, and search results in the quickfix also.\r\nYou can browse your source code more easily by moving forward and backward \r\nin the search stack.\r\n\r\n*:VIntSearchPrintStack*, *:VSstack*  \r\nPrint current search stack.\r\n\r\n*:VIntSearchMoveBackward*, *:VSbwd*  \r\nMove backward in the search stack.\r\n\r\n*:VIntSearchMoveForward*, *:VSfwd*  \r\nMove forward in the search stack.\r\n\r\n*:VIntSearchClearStack*, *:VSclear*  \r\nClear the search stack.\r\n\r\n*:VScc*  \r\n*:VScnext*  \r\n*:VScprev*  \r\nReplacement of vim's |:cc|, |:cnext|, and |:cprev| commands.\r\nJumping to a new quickFix item should be done ONLY using these commands. \r\nIf not, the jump will not be reflected in VIntSearch's search stack . \r\n- If you're using any key mapings for |:cnext| or |:cprev|, you can just replace them \r\nwith |:VScnext| and |:VScprev|. \r\n- When you `Enter` or `Double-click on a quickfix item, VIntSearch will automatically \r\ncall |:VScc| instead of vim's |:cc| command.\r\n\r\nYou can disable this VIntSearch's default `Enter` behavior \r\nusing |g:vintsearch_enable_default_quickfix_enter|.\r\n\r\n|:VScc| also can be used in other plugins that override vim's |:cc| command,\r\nsuch as [QFEnter](http:\/\/www.vim.org\/scripts\/script.php?script_id=4778).\r\n(For example, you can register |:VScc| as QFEnter's \"cc\" command by adding\r\n`let g:qfenter_cc_cmd = 'VScc ##'` in your .vimrc.)\r\n","install_details":"- Using plugin managers (recommended)\r\n    - [Vundle] : Add `Bundle 'yssl\/VIntSearch'` to .vimrc & `:BundleInstall`\r\n    - [NeoBundle] : Add `NeoBundle 'yssl\/VIntSearch'` to .vimrc & `:NeoBundleInstall`\r\n    - [vim-plug] : Add `Plug 'yssl\/VIntSearch'` to .vimrc & `:PlugInstall`\r\n- Using [Pathogen]\r\n    - `cd ~\/.vim\/bundle; git clone https:\/\/github.com\/yssl\/VIntSearch.git`\r\n- Manual install (not recommended)\r\n    - Download this plugin and extract it in `~\/.vim\/`\r\n\r\nThis plugin requires a version of vim with python support. You can check your vim with :echo has('python'). If your vim doesn't support python, one of the easiest solutions would be installing a more featured version of vim by:\r\nsudo apt-get install vim-nox","5":"- Using plugin managers (recommended)\r\n    - [Vundle] : Add `Bundle 'yssl\/VIntSearch'` to .vimrc & `:BundleInstall`\r\n    - [NeoBundle] : Add `NeoBundle 'yssl\/VIntSearch'` to .vimrc & `:NeoBundleInstall`\r\n    - [vim-plug] : Add `Plug 'yssl\/VIntSearch'` to .vimrc & `:PlugInstall`\r\n- Using [Pathogen]\r\n    - `cd ~\/.vim\/bundle; git clone https:\/\/github.com\/yssl\/VIntSearch.git`\r\n- Manual install (not recommended)\r\n    - Download this plugin and extract it in `~\/.vim\/`\r\n\r\nThis plugin requires a version of vim with python support. You can check your vim with :echo has('python'). If your vim doesn't support python, one of the easiest solutions would be installing a more featured version of vim by:\r\nsudo apt-get install vim-nox","first_name":"Yoonsang","6":"Yoonsang","last_name":"Lee","7":"Lee","releases":[{"0":"5047","vim_version":"7.0","1":"7.0","script_version":"1.4.2","2":"1.4.2","version_comment":"Support both Python 2 & Python 3 ","3":"Support both Python 2 & Python 3 ","package":"VIntSearch.zip","4":"VIntSearch.zip","src_id":"26434","5":"26434","creation_date":"1553413846","6":"1553413846"},{"0":"5047","vim_version":"7.0","1":"7.0","script_version":"1.4.1","2":"1.4.1","version_comment":"- Add cyclic version of cprev & cnext : VScnextc and VScprevc","3":"- Add cyclic version of cprev & cnext : VScnextc and VScprevc","package":"VIntSearch.zip","4":"VIntSearch.zip","src_id":"24359","5":"24359","creation_date":"1467759662","6":"1467759662"},{"0":"5047","vim_version":"7.0","1":"7.0","script_version":"1.4.0","2":"1.4.0","version_comment":"- Support MS Windows\r\n- Improve handling exceptional cases\r\n- Add VIntSearch#SearchCursorWithCmd()\r\n- Delete deprecated features from 1.3.0","3":"- Support MS Windows\r\n- Improve handling exceptional cases\r\n- Add VIntSearch#SearchCursorWithCmd()\r\n- Delete deprecated features from 1.3.0","package":"VIntSearch.zip","4":"VIntSearch.zip","src_id":"24207","5":"24207","creation_date":"1461805866","6":"1461805866"},{"0":"5047","vim_version":"7.0","1":"7.0","script_version":"1.3.1","2":"1.3.1","version_comment":" - Bug fix for find option used by VSfile & VSbuild","3":" - Bug fix for find option used by VSfile & VSbuild","package":"VIntSearch.zip","4":"VIntSearch.zip","src_id":"23692","5":"23692","creation_date":"1446216956","6":"1446216956"},{"0":"5047","vim_version":"7.0","1":"7.0","script_version":"1.3.0","2":"1.3.0","version_comment":"- Bug fix related to :vintsearch_search_exclude_patterns\r\n- Change names of include\/exclude pattern options \r\n- Refactor all search commands to be more extensible\r\n- Rename VIntSearchBuildTag to VIntSearchBuildSymbolDB \r\n- Following deprecated commands & options will be removed in version 1.4.0\r\n    - :VIntSearchBuildTag, :VSbtag   \r\n    - :VIntSearchCtags, :VSctags   \r\n    - :VIntSearchGrep, :VSgrep\r\n    - :VIntSearchCFGrep, :VScfgrep\r\n    - :VIntSearchFind, :VSfind   \r\n    - :VIntSearchCtagsCursor\r\n    - :VIntSearchGrepCursor\r\n    - :VIntSearchCFGrepCursor\r\n    - :VIntSearchFindCursor\r\n    - g:vintsearch_search_include_patterns\r\n    - g:vintsearch_search_exclude_patterns","3":"- Bug fix related to :vintsearch_search_exclude_patterns\r\n- Change names of include\/exclude pattern options \r\n- Refactor all search commands to be more extensible\r\n- Rename VIntSearchBuildTag to VIntSearchBuildSymbolDB \r\n- Following deprecated commands & options will be removed in version 1.4.0\r\n    - :VIntSearchBuildTag, :VSbtag   \r\n    - :VIntSearchCtags, :VSctags   \r\n    - :VIntSearchGrep, :VSgrep\r\n    - :VIntSearchCFGrep, :VScfgrep\r\n    - :VIntSearchFind, :VSfind   \r\n    - :VIntSearchCtagsCursor\r\n    - :VIntSearchGrepCursor\r\n    - :VIntSearchCFGrepCursor\r\n    - :VIntSearchFindCursor\r\n    - g:vintsearch_search_include_patterns\r\n    - g:vintsearch_search_exclude_patterns","package":"VIntSearch.zip","4":"VIntSearch.zip","src_id":"23497","5":"23497","creation_date":"1438449123","6":"1438449123"},{"0":"5047","vim_version":"7.0","1":"7.0","script_version":"1.2.2","2":"1.2.2","version_comment":"- Add hightlight option for search result (g:vintsearch_highlight_group)","3":"- Add hightlight option for search result (g:vintsearch_highlight_group)","package":"VIntSearch.zip","4":"VIntSearch.zip","src_id":"23461","5":"23461","creation_date":"1436389285","6":"1436389285"},{"0":"5047","vim_version":"7.0","1":"7.0","script_version":"1.2.1","2":"1.2.1","version_comment":"- Add file find commands. :VIntSearchFind & VintSearchFindCursor\r\n- Fix script errors","3":"- Add file find commands. :VIntSearchFind & VintSearchFindCursor\r\n- Fix script errors","package":"VIntSearch.zip","4":"VIntSearch.zip","src_id":"23378","5":"23378","creation_date":"1433969918","6":"1433969918"},{"0":"5047","vim_version":"7.0","1":"7.0","script_version":"1.2.0","2":"1.2.0","version_comment":"- Fix find option bug related to grep search.\r\n- Rename & refactor all commands and whole code. The old commands (e.g. :VIntSearchListCursorGrep) are deprecated and will be removed in 1.3.0 version.","3":"- Fix find option bug related to grep search.\r\n- Rename & refactor all commands and whole code. The old commands (e.g. :VIntSearchListCursorGrep) are deprecated and will be removed in 1.3.0 version.","package":"VIntSearch.zip","4":"VIntSearch.zip","src_id":"23361","5":"23361","creation_date":"1433635295","6":"1433635295"},{"0":"5047","vim_version":"7.0","1":"7.0","script_version":"1.1.3","2":"1.1.3","version_comment":"- Update key mapping example\r\n- Update documents for Search Path \/ Tag Commands\r\n- Add VSbtag command\r\n- Fix :helptag build error","3":"- Update key mapping example\r\n- Update documents for Search Path \/ Tag Commands\r\n- Add VSbtag command\r\n- Fix :helptag build error","package":"VIntSearch.zip","4":"VIntSearch.zip","src_id":"23350","5":"23350","creation_date":"1433429230","6":"1433429230"},{"0":"5047","vim_version":"7.0","1":"7.0","script_version":"1.1.2","2":"1.1.2","version_comment":"- Add local search commands (search in current file)\r\n- Escaping double quotation mark in search keyword\r\n- Handle vim pattern character (%, #) in search keyword\r\n- Change grep option a bit internally","3":"- Add local search commands (search in current file)\r\n- Escaping double quotation mark in search keyword\r\n- Handle vim pattern character (%, #) in search keyword\r\n- Change grep option a bit internally","package":"VIntSearch.zip","4":"VIntSearch.zip","src_id":"23311","5":"23311","creation_date":"1432595262","6":"1432595262"},{"0":"5047","vim_version":"7.0","1":"7.0","script_version":"1.1.1","2":"1.1.1","version_comment":"Fix the infinite loop bug when there is no vcs directory","3":"Fix the infinite loop bug when there is no vcs directory","package":"VIntSearch.zip","4":"VIntSearch.zip","src_id":"22906","5":"22906","creation_date":"1423688982","6":"1423688982"},{"0":"5047","vim_version":"7.0","1":"7.0","script_version":"1.1.0","2":"1.1.0","version_comment":"- Add DefaultQuickFixEnter behavior - doesn't need external plugins like QFEnter any more\r\n- New file pattern options to specify input source files for both ctags and grep commands\r\n- Exception handling: Catch E553 error of VScnext & VScprev  \r\n","3":"- Add DefaultQuickFixEnter behavior - doesn't need external plugins like QFEnter any more\r\n- New file pattern options to specify input source files for both ctags and grep commands\r\n- Exception handling: Catch E553 error of VScnext & VScprev  \r\n","package":"VIntSearch.zip","4":"VIntSearch.zip","src_id":"22855","5":"22855","creation_date":"1422706543","6":"1422706543"},{"0":"5047","vim_version":"7.0","1":"7.0","script_version":"1.0.1","2":"1.0.1","version_comment":"Change repository directories finding behavior.","3":"Change repository directories finding behavior.","package":"VIntSearch.zip","4":"VIntSearch.zip","src_id":"22827","5":"22827","creation_date":"1422223805","6":"1422223805"},{"0":"5047","vim_version":"7.0","1":"7.0","script_version":"1.0.0","2":"1.0.0","version_comment":"Initial upload","3":"Initial upload","package":"VIntSearch.zip","4":"VIntSearch.zip","src_id":"22591","5":"22591","creation_date":"1414887792","6":"1414887792"}]},"5046":{"script_id":"5046","0":"5046","script_name":"ReplaceWithSameIndentRegister","1":"ReplaceWithSameIndentRegister","script_type":"utility","2":"utility","summary":"Replace lines with the contents of a register, keeping the original indent.","3":"Replace lines with the contents of a register, keeping the original indent.","description":"DESCRIPTION\r\nReplacing existing lines with the contents of a register is a very common task\r\nduring editing. Often, one wants to adapt the indent of the pasted lines to\r\nthe current indent, e.g. when replacing a nested conditional from a yank that\r\noriginated at a different nesting level.\r\n\r\nThis plugin combines the replacement functionality of the\r\nReplaceWithRegister.vim plugin with the indent-adjustment done by the\r\nbuilt-in ]p command. With a simple mapping, you can replace line(s) with the\r\ncontents of a register while adjusting the indent to that of the first\r\nreplaced line.\r\n\r\nSEE ALSO\r\n- ReplaceWithRegister.vim (vimscript #2703) implements the general case of\r\n  replacing text including the indent (also with a {motion} mapping for\r\n  arbitrary text, not just lines).\r\n\r\nUSAGE\r\n[count][\"x]grR          Replace [count] lines with the contents of register x\r\n                        and adjust the indent to the first replaced line (like\r\n                        pasting with ]p).\r\n{Visual}[\"x]gR          Replace the selection with the contents of register x\r\n                        and adjust the indent to the first selected line.\r\n                        As the replacement is always entire lines, this only\r\n                        works with linewise selections (V).","4":"DESCRIPTION\r\nReplacing existing lines with the contents of a register is a very common task\r\nduring editing. Often, one wants to adapt the indent of the pasted lines to\r\nthe current indent, e.g. when replacing a nested conditional from a yank that\r\noriginated at a different nesting level.\r\n\r\nThis plugin combines the replacement functionality of the\r\nReplaceWithRegister.vim plugin with the indent-adjustment done by the\r\nbuilt-in ]p command. With a simple mapping, you can replace line(s) with the\r\ncontents of a register while adjusting the indent to that of the first\r\nreplaced line.\r\n\r\nSEE ALSO\r\n- ReplaceWithRegister.vim (vimscript #2703) implements the general case of\r\n  replacing text including the indent (also with a {motion} mapping for\r\n  arbitrary text, not just lines).\r\n\r\nUSAGE\r\n[count][\"x]grR          Replace [count] lines with the contents of register x\r\n                        and adjust the indent to the first replaced line (like\r\n                        pasting with ]p).\r\n{Visual}[\"x]gR          Replace the selection with the contents of register x\r\n                        and adjust the indent to the first selected line.\r\n                        As the replacement is always entire lines, this only\r\n                        works with linewise selections (V).","install_details":"INSTALLATION\r\nThe code is hosted in a Git repo at\r\n    https:\/\/github.com\/inkarkat\/vim-ReplaceWithSameIndentRegister\r\nYou can use your favorite plugin manager, or \"git clone\" into a directory used\r\nfor Vim packages. Releases are on the \"stable\" branch, the latest unstable\r\ndevelopment snapshot on \"master\".\r\n\r\nThis script is also packaged as a vimball. If you have the \"gunzip\"\r\ndecompressor in your PATH, simply edit the *.vmb.gz package in Vim; otherwise,\r\ndecompress the archive first, e.g. using WinZip. Inside Vim, install by\r\nsourcing the vimball or via the :UseVimball command.\r\n    vim ReplaceWithSameIndentRegister*.vmb.gz\r\n    :so %\r\nTo uninstall, use the :RmVimball command.\r\n\r\nDEPENDENCIES\r\n- Requires Vim 7.0 or higher.\r\n- Requires the ingo-library.vim plugin (vimscript #4433), version 1.000 or\r\n  higher.\r\n- repeat.vim (vimscript #2136) plugin (optional)\r\n  To support repetition with a register other than the default register, you\r\n  need version 1.1 or later.\r\n- visualrepeat.vim (vimscript #3848) plugin (version 2.00 or higher; optional)\r\n\r\nCONFIGURATION\r\nIf you want to use different mappings, map your keys to the\r\nReplaceWithSameIndentRegister... mapping targets _before_ sourcing the\r\nscript (e.g. in your vimrc):\r\n    nmap R  ReplaceWithSameIndentRegisterLine\r\n    xmap R  ReplaceWithSameIndentRegisterVisual","5":"INSTALLATION\r\nThe code is hosted in a Git repo at\r\n    https:\/\/github.com\/inkarkat\/vim-ReplaceWithSameIndentRegister\r\nYou can use your favorite plugin manager, or \"git clone\" into a directory used\r\nfor Vim packages. Releases are on the \"stable\" branch, the latest unstable\r\ndevelopment snapshot on \"master\".\r\n\r\nThis script is also packaged as a vimball. If you have the \"gunzip\"\r\ndecompressor in your PATH, simply edit the *.vmb.gz package in Vim; otherwise,\r\ndecompress the archive first, e.g. using WinZip. Inside Vim, install by\r\nsourcing the vimball or via the :UseVimball command.\r\n    vim ReplaceWithSameIndentRegister*.vmb.gz\r\n    :so %\r\nTo uninstall, use the :RmVimball command.\r\n\r\nDEPENDENCIES\r\n- Requires Vim 7.0 or higher.\r\n- Requires the ingo-library.vim plugin (vimscript #4433), version 1.000 or\r\n  higher.\r\n- repeat.vim (vimscript #2136) plugin (optional)\r\n  To support repetition with a register other than the default register, you\r\n  need version 1.1 or later.\r\n- visualrepeat.vim (vimscript #3848) plugin (version 2.00 or higher; optional)\r\n\r\nCONFIGURATION\r\nIf you want to use different mappings, map your keys to the\r\nReplaceWithSameIndentRegister... mapping targets _before_ sourcing the\r\nscript (e.g. in your vimrc):\r\n    nmap R  ReplaceWithSameIndentRegisterLine\r\n    xmap R  ReplaceWithSameIndentRegisterVisual","first_name":"Ingo","6":"Ingo","last_name":"Karkat","7":"Karkat","releases":[{"0":"5046","vim_version":"7.0","1":"7.0","script_version":"1.01","2":"1.01","version_comment":"- BUG: {count}grR does not repeat the count.\r\n- BUG: Starting with v_gR, repeating in normal mode with {count}., repeating again uses the original number of selected lines, not the overridden {count}.\r\n- Suppress \"--No lines in buffer--\" message when replacing the entire buffer, and combine \"Deleted N lines\" \/ \"Added M lines\" into a single message that is given when either previous or new amount of lines reaches 'report'.","3":"- BUG: {count}grR does not repeat the count.\r\n- BUG: Starting with v_gR, repeating in normal mode with {count}., repeating again uses the original number of selected lines, not the overridden {count}.\r\n- Suppress \"--No lines in buffer--\" message when replacing the entire buffer, and combine \"Deleted N lines\" \/ \"Added M lines\" into a single message that is given when either previous or new amount of lines reaches 'report'.","package":"ReplaceWithSameIndentRegister-1.01.vmb.gz","4":"ReplaceWithSameIndentRegister-1.01.vmb.gz","src_id":"26844","5":"26844","creation_date":"1574184836","6":"1574184836"},{"0":"5046","vim_version":"7.0","1":"7.0","script_version":"1.00","2":"1.00","version_comment":"Initial upload","3":"Initial upload","package":"ReplaceWithSameIndentRegister-1.00.vmb.gz","4":"ReplaceWithSameIndentRegister-1.00.vmb.gz","src_id":"22580","5":"22580","creation_date":"1414575400","6":"1414575400"}]},"5045":{"script_id":"5045","0":"5045","script_name":"miv.vim","1":"miv.vim","script_type":"ftplugin","2":"ftplugin","summary":"markdown in vim","3":"markdown in vim","description":"# miv.vim\r\n\r\nMarkdown in Vim.\r\n\r\n\r\nI Want to write a Better markdown writing plugin for vim.\r\n\r\n**Reason**\r\n\r\nThough rst with [Riv.vim](https:\/\/github.com\/Rykka\/riv.vim) is enough for writing.\r\n\r\nbut rst does not support javascript, which is a BIG disadvantage.\r\n\r\n----\r\n\r\nHaven't start working yet, So any suggestion are welcome.\r\n\r\nYou can post issues at [github](https:\/\/github.com\/Rykka\/miv.vim) or email me at rykka@foxmail.com.\r\n\r\n\r\n----\r\n\r\nI thought I should use javascript lib to finish it.\r\n\r\nThough vim does not support native javascript scripting is a BIG disadvantage.\r\n","4":"# miv.vim\r\n\r\nMarkdown in Vim.\r\n\r\n\r\nI Want to write a Better markdown writing plugin for vim.\r\n\r\n**Reason**\r\n\r\nThough rst with [Riv.vim](https:\/\/github.com\/Rykka\/riv.vim) is enough for writing.\r\n\r\nbut rst does not support javascript, which is a BIG disadvantage.\r\n\r\n----\r\n\r\nHaven't start working yet, So any suggestion are welcome.\r\n\r\nYou can post issues at [github](https:\/\/github.com\/Rykka\/miv.vim) or email me at rykka@foxmail.com.\r\n\r\n\r\n----\r\n\r\nI thought I should use javascript lib to finish it.\r\n\r\nThough vim does not support native javascript scripting is a BIG disadvantage.\r\n","install_details":"Not yet.","5":"Not yet.","first_name":"Rykka","6":"Rykka","last_name":"f","7":"f","releases":[{"0":"5045","vim_version":"7.0","1":"7.0","script_version":"0.0.1","2":"0.0.1","version_comment":"Initial upload","3":"Initial upload","package":"miv.vim-0.0.1.zip","4":"miv.vim-0.0.1.zip","src_id":"22573","5":"22573","creation_date":"1414425657","6":"1414425657"}]},"5044":{"script_id":"5044","0":"5044","script_name":"vimdir.vim","1":"vimdir.vim","script_type":"utility","2":"utility","summary":"Manage files and directories in vim","3":"Manage files and directories in vim","description":"vimdir.vim\r\n==========\r\n\r\nManage files and directories in vim\r\n\r\nInspired by vidir by Joey Hess (https:\/\/joeyh.name\/code\/moreutils\/)\r\n\r\n## Usage\r\n\r\nTo list files and folders\r\n```\r\n:Vimdir [directory]\r\n```\r\n\r\nTo list files and folders recursive\r\n```\r\n:VimdirR [directory]\r\n```\r\n\r\nIf no directory is specified Vimdir will use the current path\r\n\r\nChanges will be applyed when you save the vimdir buffer. If you want to cancel\r\njust close the buffer without saving.\r\n\r\n## Colors\r\n\r\nvimdir.vim doesn't come with highlighting support but using the https:\/\/github.com\/trapd00r\/vim-syntax-vidir-ls plugin works perfectly.\r\n\r\n## Configuration\r\n\r\nTo show hidden files and folders set this in your vimrc\r\n\r\n```\r\nlet g:vimdir_show_hidden = 1\r\n```\r\n\r\nTo force removal of files and folders set this in your vimrc\r\n(will add this to the overwrite code when its implemented)\r\n```\r\nlet g:vimdir_force = 1\r\n```\r\n\r\n## bin\/vimdir\r\n\r\nYou can use the bin\/vimdir script to execute vimdir directly from the terminal.\r\nJust place it in your path and run vimdir.\r\n\r\n## github\r\n\r\nhttps:\/\/github.com\/c0r73x\/vimdir.vim\r\n","4":"vimdir.vim\r\n==========\r\n\r\nManage files and directories in vim\r\n\r\nInspired by vidir by Joey Hess (https:\/\/joeyh.name\/code\/moreutils\/)\r\n\r\n## Usage\r\n\r\nTo list files and folders\r\n```\r\n:Vimdir [directory]\r\n```\r\n\r\nTo list files and folders recursive\r\n```\r\n:VimdirR [directory]\r\n```\r\n\r\nIf no directory is specified Vimdir will use the current path\r\n\r\nChanges will be applyed when you save the vimdir buffer. If you want to cancel\r\njust close the buffer without saving.\r\n\r\n## Colors\r\n\r\nvimdir.vim doesn't come with highlighting support but using the https:\/\/github.com\/trapd00r\/vim-syntax-vidir-ls plugin works perfectly.\r\n\r\n## Configuration\r\n\r\nTo show hidden files and folders set this in your vimrc\r\n\r\n```\r\nlet g:vimdir_show_hidden = 1\r\n```\r\n\r\nTo force removal of files and folders set this in your vimrc\r\n(will add this to the overwrite code when its implemented)\r\n```\r\nlet g:vimdir_force = 1\r\n```\r\n\r\n## bin\/vimdir\r\n\r\nYou can use the bin\/vimdir script to execute vimdir directly from the terminal.\r\nJust place it in your path and run vimdir.\r\n\r\n## github\r\n\r\nhttps:\/\/github.com\/c0r73x\/vimdir.vim\r\n","install_details":"### Vundle\r\n\r\n    Bundle 'c0r73x\/vimdir.vim'\r\n\r\n### NeoBundle\r\n\r\n    NeoBundle 'c0r73x\/vimdir.vim'\r\n\r\n### Manual\r\n\r\n    Download the plugin and paste it into your plugin directory.","5":"### Vundle\r\n\r\n    Bundle 'c0r73x\/vimdir.vim'\r\n\r\n### NeoBundle\r\n\r\n    NeoBundle 'c0r73x\/vimdir.vim'\r\n\r\n### Manual\r\n\r\n    Download the plugin and paste it into your plugin directory.","first_name":"Christian","6":"Christian","last_name":"Persson","7":"Persson","releases":[{"0":"5044","vim_version":"7.0","1":"7.0","script_version":"0.0.4","2":"0.0.4","version_comment":"Renaming lower to uppercase now works.\r\nAnd fixed problem when file- and foldernames contained space.\r\n","3":"Renaming lower to uppercase now works.\r\nAnd fixed problem when file- and foldernames contained space.\r\n","package":"vimdir.vim.zip","4":"vimdir.vim.zip","src_id":"22588","5":"22588","creation_date":"1414692644","6":"1414692644"}]},"5043":{"script_id":"5043","0":"5043","script_name":"ShowWhiteSpace","1":"ShowWhiteSpace","script_type":"ftplugin","2":"ftplugin","summary":"Display WhiteSpace","3":"Display WhiteSpace","description":"This script is influenced by a question on stackoverflow on how to display space characters in a window. By default it uses the \u00c2\u00b7 character for a space.\r\n\r\nUse the :ShowWhiteToggle command to toggle display of spaces in the current window. Alternatively you can use the normal mode mapping '\\ws'","4":"This script is influenced by a question on stackoverflow on how to display space characters in a window. By default it uses the \u00c2\u00b7 character for a space.\r\n\r\nUse the :ShowWhiteToggle command to toggle display of spaces in the current window. Alternatively you can use the normal mode mapping '\\ws'","install_details":"simply source the file and the plugin will be installed automatically\r\n:e show-whitespace-.vmb\r\n:so %\r\n\r\nAnd afterwards, have a look at the documentation: :h ShowWhitespace.txt\r\n\r\nAlternatively, use the plugin manager of your choice.","5":"simply source the file and the plugin will be installed automatically\r\n:e show-whitespace-.vmb\r\n:so %\r\n\r\nAnd afterwards, have a look at the documentation: :h ShowWhitespace.txt\r\n\r\nAlternatively, use the plugin manager of your choice.","first_name":"Christian","6":"Christian","last_name":"Brabandt","7":"Brabandt","releases":[{"0":"5043","vim_version":"7.4","1":"7.4","script_version":"2","2":"2","version_comment":"- Make sure highlighting group exists (issue https:\/\/github.com\/chrisbra\/vim-show-whitespace\/issues\/1, reported by feroxium, thanks!)\n- Link Conceal highlighting to Normal group\n- Support Vim 7.4.711 (includes a native fix for whitespace highlighting using the 'listchars' option)\n(automatically uploaded)","3":"- Make sure highlighting group exists (issue https:\/\/github.com\/chrisbra\/vim-show-whitespace\/issues\/1, reported by feroxium, thanks!)\n- Link Conceal highlighting to Normal group\n- Support Vim 7.4.711 (includes a native fix for whitespace highlighting using the 'listchars' option)\n(automatically uploaded)","package":"show-whitespace-0.2.vmb","4":"show-whitespace-0.2.vmb","src_id":"23204","5":"23204","creation_date":"1429640409","6":"1429640409"},{"0":"5043","vim_version":"7.3","1":"7.3","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"show-whitespace.vmb","4":"show-whitespace.vmb","src_id":"22569","5":"22569","creation_date":"1414354546","6":"1414354546"}]},"5042":{"script_id":"5042","0":"5042","script_name":"vim-xblogger","1":"vim-xblogger","script_type":"ftplugin","2":"ftplugin","summary":"A set of Vim-files for publishing posts to Blogger or WordPress","3":"A set of Vim-files for publishing posts to Blogger or WordPress","description":"XBlogger\r\n========\r\n\r\nThis is a set of Vim-files for publishing posts to Blogger or Wordpress in your favorite markup language.\r\n\r\nRequirements\r\n------------\r\n\r\n[b.py](http:\/\/http:\/\/pythonhosted.org\/b.py\/) - a command line tool for publishing posts.\r\n\r\nOptional Vim-plugins:\r\n\r\n* [SirVer\/ultisnips](https:\/\/github.com\/SirVer\/ultisnips) - snippets\r\n* [tpope\/vim-ragtag](https:\/\/github.com\/tpope\/vim-ragtag) - for tag closing\r\n* [aperezdc\/vim-template](https:\/\/github.com\/aperezdc\/vim-template) - templates for new files\r\n\r\nInstallation\r\n------------\r\n\r\n1. Install via Vundle: `Plugin 'xvadim\/vim-xblogger'` or just unpack the archive to `$HOME\/.vim`\r\n2. Copy the file `external\/brc.py` to the directory where you are going to prepare and keep posts\r\n3. Replace `YOU_BLOG_ID` with the real ID of your blog\r\n4. Setup `b.py` as [described in documentation](http:\/\/pythonhosted.org\/b.py\/tutorial.html)\r\n\r\nUsage\r\n-----\r\n\r\n1. Start post creation: `vim my_post.blog`\r\n2. Create post [as described in documentation](http:\/\/pythonhosted.org\/b.py\/tutorial.html#creating-the-first-post)\r\n3. For publishing the post type in the normal mode: `post`\r\n\r\nImprovements\r\n------------\r\n\r\nIf you use plugin **vim-template** copy the file `external\/.vim-template:*.blog` to the directory of your posts.\r\nThis will insert a header to new files.\r\n\r\nIf you use [higlhlight.js](https:\/\/highlightjs.org\/) and plugin **ultisnips** copy the file `snippet\/blog.snippets`\r\nto the snippets directory. This adds the snippet `code` which inserts the next fragment:\r\n\r\n```\r\n
\r\n<\/code><\/pre>\r\n```\r\n\r\nAlso it makes available all snippets for mardown-files.\r\n\r\nAlso the command `Rc file_name` available. This command inserts the given file as fragment of code.\r\n\r\ngithub: https:\/\/github.com\/xvadim\/vim-xblogger","4":"XBlogger\r\n========\r\n\r\nThis is a set of Vim-files for publishing posts to Blogger or Wordpress in your favorite markup language.\r\n\r\nRequirements\r\n------------\r\n\r\n[b.py](http:\/\/http:\/\/pythonhosted.org\/b.py\/) - a command line tool for publishing posts.\r\n\r\nOptional Vim-plugins:\r\n\r\n* [SirVer\/ultisnips](https:\/\/github.com\/SirVer\/ultisnips) - snippets\r\n* [tpope\/vim-ragtag](https:\/\/github.com\/tpope\/vim-ragtag) - for tag closing\r\n* [aperezdc\/vim-template](https:\/\/github.com\/aperezdc\/vim-template) - templates for new files\r\n\r\nInstallation\r\n------------\r\n\r\n1. Install via Vundle: `Plugin 'xvadim\/vim-xblogger'` or just unpack the archive to `$HOME\/.vim`\r\n2. Copy the file `external\/brc.py` to the directory where you are going to prepare and keep posts\r\n3. Replace `YOU_BLOG_ID` with the real ID of your blog\r\n4. Setup `b.py` as [described in documentation](http:\/\/pythonhosted.org\/b.py\/tutorial.html)\r\n\r\nUsage\r\n-----\r\n\r\n1. Start post creation: `vim my_post.blog`\r\n2. Create post [as described in documentation](http:\/\/pythonhosted.org\/b.py\/tutorial.html#creating-the-first-post)\r\n3. For publishing the post type in the normal mode: `post`\r\n\r\nImprovements\r\n------------\r\n\r\nIf you use plugin **vim-template** copy the file `external\/.vim-template:*.blog` to the directory of your posts.\r\nThis will insert a header to new files.\r\n\r\nIf you use [higlhlight.js](https:\/\/highlightjs.org\/) and plugin **ultisnips** copy the file `snippet\/blog.snippets`\r\nto the snippets directory. This adds the snippet `code` which inserts the next fragment:\r\n\r\n```\r\n
\r\n<\/code><\/pre>\r\n```\r\n\r\nAlso it makes available all snippets for mardown-files.\r\n\r\nAlso the command `Rc file_name` available. This command inserts the given file as fragment of code.\r\n\r\ngithub: https:\/\/github.com\/xvadim\/vim-xblogger","install_details":"","5":"","first_name":"Vadym","6":"Vadym","last_name":"Khokhlov","7":"Khokhlov","releases":[{"0":"5042","vim_version":"7.0","1":"7.0","script_version":"1.1","2":"1.1","version_comment":"Added support of linkchecker for links checking","3":"Added support of linkchecker for links checking","package":"vim-xblogger.zip","4":"vim-xblogger.zip","src_id":"23125","5":"23125","creation_date":"1428046550","6":"1428046550"},{"0":"5042","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"vim-xblogger.zip","4":"vim-xblogger.zip","src_id":"22561","5":"22561","creation_date":"1414185698","6":"1414185698"}]},"5041":{"script_id":"5041","0":"5041","script_name":"Sweater","1":"Sweater","script_type":"color scheme","2":"color scheme","summary":"Light color scheme for Vim.","3":"Light color scheme for Vim.","description":"For more details, screenshot and development, please visit: https:\/\/github.com\/nice\/sweater","4":"For more details, screenshot and development, please visit: https:\/\/github.com\/nice\/sweater","install_details":":colorscheme sweater","5":":colorscheme sweater","first_name":"nice","6":"nice","last_name":"guy","7":"guy","releases":[{"0":"5041","vim_version":"7.0","1":"7.0","script_version":"0.9","2":"0.9","version_comment":"Initial upload","3":"Initial upload","package":"sweater.vim","4":"sweater.vim","src_id":"22560","5":"22560","creation_date":"1414157961","6":"1414157961"}]},"5040":{"script_id":"5040","0":"5040","script_name":"verilog.vim","1":"verilog.vim","script_type":"indent","2":"indent","summary":"Automated indentation for Verilog and SystemVerilog","3":"Automated indentation for Verilog and SystemVerilog","description":"This script provides indentation rules for Verilog and SystemVerilog constructs. Indentation scripts like this sometimes require changing your coding style a bit to match the limitations of the script. This one, for example, can only look back one or two lines. You'll need to use begin and end statements for any non-sectional block that has more than one line (like \"always\" as opposed to \"task\"). I've been using and improving this script for years now, so I expect there will always be a way to organize your syntax for compatibility with this script.","4":"This script provides indentation rules for Verilog and SystemVerilog constructs. Indentation scripts like this sometimes require changing your coding style a bit to match the limitations of the script. This one, for example, can only look back one or two lines. You'll need to use begin and end statements for any non-sectional block that has more than one line (like \"always\" as opposed to \"task\"). I've been using and improving this script for years now, so I expect there will always be a way to organize your syntax for compatibility with this script.","install_details":"Put the file in ~\/.vim\/indent","5":"Put the file in ~\/.vim\/indent","first_name":"Lex","6":"Lex","last_name":"Leonard","7":"Leonard","releases":[{"0":"5040","vim_version":"7.0","1":"7.0","script_version":"1.1","2":"1.1","version_comment":"Minor improvements","3":"Minor improvements","package":"verilog.vim","4":"verilog.vim","src_id":"26436","5":"26436","creation_date":"1553665219","6":"1553665219"},{"0":"5040","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"verilog.vim","4":"verilog.vim","src_id":"22557","5":"22557","creation_date":"1414006140","6":"1414006140"}]},"5039":{"script_id":"5039","0":"5039","script_name":"vi-clone.vim","1":"vi-clone.vim","script_type":"color scheme","2":"color scheme","summary":"Elvis-like syntax highlighting.","3":"Elvis-like syntax highlighting.","description":"DEPRECATED for: https:\/\/github.com\/ryanpcmcquen\/true-monochrome_vim\r\n\r\n\r\nThis is for those who want the 'vi' look with vim's features.","4":"DEPRECATED for: https:\/\/github.com\/ryanpcmcquen\/true-monochrome_vim\r\n\r\n\r\nThis is for those who want the 'vi' look with vim's features.","install_details":"Run:\r\n  mkdir -p ~\/.vim\/colors\/\r\n  wget -N https:\/\/raw.githubusercontent.com\/ryanpcmcquen\/vim-plain\/master\/colors\/vi-clone.vim -P ~\/.vim\/colors\/\r\n\r\nAdd to .vimrc:\r\n  colorscheme vi-clone","5":"Run:\r\n  mkdir -p ~\/.vim\/colors\/\r\n  wget -N https:\/\/raw.githubusercontent.com\/ryanpcmcquen\/vim-plain\/master\/colors\/vi-clone.vim -P ~\/.vim\/colors\/\r\n\r\nAdd to .vimrc:\r\n  colorscheme vi-clone","first_name":"Ryan","6":"Ryan","last_name":"McQuen","7":"McQuen","releases":[{"0":"5039","vim_version":"6.0","1":"6.0","script_version":"0.3.3","2":"0.3.3","version_comment":"Update email.","3":"Update email.","package":"vi-clone.vim","4":"vi-clone.vim","src_id":"24879","5":"24879","creation_date":"1483833388","6":"1483833388"},{"0":"5039","vim_version":"6.0","1":"6.0","script_version":"0.3.2","2":"0.3.2","version_comment":"Spacing fixes.","3":"Spacing fixes.","package":"vi-clone.vim","4":"vi-clone.vim","src_id":"22554","5":"22554","creation_date":"1413901064","6":"1413901064"}]},"5038":{"script_id":"5038","0":"5038","script_name":"incsearch.vim","1":"incsearch.vim","script_type":"utility","2":"utility","summary":"Improved incremental searching for Vim","3":"Improved incremental searching for Vim","description":"See https:\/\/github.com\/haya14busa\/incsearch.vim","4":"See https:\/\/github.com\/haya14busa\/incsearch.vim","install_details":"","5":"","first_name":"haya14busa","6":"haya14busa","last_name":" ","7":" ","releases":[{"0":"5038","vim_version":"7.3","1":"7.3","script_version":"v2.0.1","2":"v2.0.1","version_comment":"2.0.1 2015-10-31\r\nFix can't turn off |g:incsearch#consistent_n_direction|. ref: #95\r\nFix ? pattern handling for backward search. ref: #92\r\n","3":"2.0.1 2015-10-31\r\nFix can't turn off |g:incsearch#consistent_n_direction|. ref: #95\r\nFix ? pattern handling for backward search. ref: #92\r\n","package":"incsearch.vim-2.0.1.zip","4":"incsearch.vim-2.0.1.zip","src_id":"23694","5":"23694","creation_date":"1446331836","6":"1446331836"},{"0":"5038","vim_version":"7.3","1":"7.3","script_version":"v2.0.0","2":"v2.0.0","version_comment":"### 2.0.0\t2015-07-06\r\n1. |incsearch#go()| and |incsearch-config| as a API\r\n2. Pattern converter feature |incsearch-config-converters|\r\n3. Injection of vital-over module |incsearch-config-modules|\r\n4. External extention plugins like fuzzy, easymotion, migemo...\r\n  - https:\/\/github.com\/haya14busa\/incsearch.vim\/wiki\/List-of-plugins-for-incsearch.vim\r\nhttps:\/\/github.com\/haya14busa\/incsearch.vim\/releases\/tag\/v2.0.0","3":"### 2.0.0\t2015-07-06\r\n1. |incsearch#go()| and |incsearch-config| as a API\r\n2. Pattern converter feature |incsearch-config-converters|\r\n3. Injection of vital-over module |incsearch-config-modules|\r\n4. External extention plugins like fuzzy, easymotion, migemo...\r\n  - https:\/\/github.com\/haya14busa\/incsearch.vim\/wiki\/List-of-plugins-for-incsearch.vim\r\nhttps:\/\/github.com\/haya14busa\/incsearch.vim\/releases\/tag\/v2.0.0","package":"incsearch.vim-2.0.0.zip","4":"incsearch.vim-2.0.0.zip","src_id":"23445","5":"23445","creation_date":"1436133920","6":"1436133920"},{"0":"5038","vim_version":"7.3","1":"7.3","script_version":"v1.2.1","2":"v1.2.1","version_comment":"1.2.1\t2015-06-26\r\n\t1. Add |incsearch-config-keymap| option to |incsearch-config|\r\n\t2. Some refactoring\r\n","3":"1.2.1\t2015-06-26\r\n\t1. Add |incsearch-config-keymap| option to |incsearch-config|\r\n\t2. Some refactoring\r\n","package":"incsearch.vim-1.2.1.zip","4":"incsearch.vim-1.2.1.zip","src_id":"23417","5":"23417","creation_date":"1435494461","6":"1435494461"},{"0":"5038","vim_version":"7.3","1":"7.3","script_version":"v1.2.0","2":"v1.2.0","version_comment":"1.2.0\t2015-06-06\r\n\t1. Now, fix unexpected key input with |feedkeys()| by auto-nohlsearch\r\n\t   feature (|incsearch-additional-usage|) #82\r\n\t2. Avoid Unneeded loading for mappings like |(incsearch-nohl)|\r\n\t   related with #81\r\n\t3. Fix |nowrapscan| handling #83\r\n\t4. Add |incsearch-config-prompt| option\r\n\t5. auto-nohlsearch on |CursorMoved| after |InsertLeave| related with #80\r\n\t6. Some refactoring\r\n","3":"1.2.0\t2015-06-06\r\n\t1. Now, fix unexpected key input with |feedkeys()| by auto-nohlsearch\r\n\t   feature (|incsearch-additional-usage|) #82\r\n\t2. Avoid Unneeded loading for mappings like |(incsearch-nohl)|\r\n\t   related with #81\r\n\t3. Fix |nowrapscan| handling #83\r\n\t4. Add |incsearch-config-prompt| option\r\n\t5. auto-nohlsearch on |CursorMoved| after |InsertLeave| related with #80\r\n\t6. Some refactoring\r\n","package":"incsearch.vim-1.2.0.zip","4":"incsearch.vim-1.2.0.zip","src_id":"23364","5":"23364","creation_date":"1433684906","6":"1433684906"},{"0":"5038","vim_version":"7.3","1":"7.3","script_version":"v1.1.0","2":"v1.1.0","version_comment":"1.1.0\t2015-05-03\r\n\t1. Add experimental API |incsearch-api|.\r\n\t    - Now you can pass a default pattern |incsearch-config-pattern|\r\n\t    - Use |incsearch#cli()| with |incsearch-autocmd| to extend\r\n\t      incsearch.vim's search interface\r\n\t    - vim-repeat support if needed |incsearch-config-is_expr|\r\n\t    - You can pass additional vital-over module to connect\r\n\t      |incsearch-config-modules|","3":"1.1.0\t2015-05-03\r\n\t1. Add experimental API |incsearch-api|.\r\n\t    - Now you can pass a default pattern |incsearch-config-pattern|\r\n\t    - Use |incsearch#cli()| with |incsearch-autocmd| to extend\r\n\t      incsearch.vim's search interface\r\n\t    - vim-repeat support if needed |incsearch-config-is_expr|\r\n\t    - You can pass additional vital-over module to connect\r\n\t      |incsearch-config-modules|","package":"incsearch.vim-1.1.0.zip","4":"incsearch.vim-1.1.0.zip","src_id":"23255","5":"23255","creation_date":"1430646268","6":"1430646268"},{"0":"5038","vim_version":"7.3","1":"7.3","script_version":"v1.0.3","2":"v1.0.3","version_comment":"1.0.3\t2015-05-03\r\n\t1. Fix 'hlsearch' handling #74\r\n","3":"1.0.3\t2015-05-03\r\n\t1. Fix 'hlsearch' handling #74\r\n","package":"incsearch.vim-1.0.3.zip","4":"incsearch.vim-1.0.3.zip","src_id":"23254","5":"23254","creation_date":"1430631859","6":"1430631859"},{"0":"5038","vim_version":"7.3","1":"7.3","script_version":"1.0.2","2":"1.0.2","version_comment":"1.0.2\t2015-04-16\r\n\t1. Implement experimental API (undocumented) to access vital-over\r\n\t   command line object\r\n\t2. Add LiteralInsert module to insert special character literally\r\n\t  - e.g.  now inserts literal  and search them.\r\n\t3. Add workaround pasting issue for MacVim #35\r\n\t4. Fix to redraw commandline when leaving with  #67\r\n\t5. Fix  handling for  mappings #51\r\n\t6. Fix flicker at entering incsearch's commands #73\r\n\r\n\r\n","3":"1.0.2\t2015-04-16\r\n\t1. Implement experimental API (undocumented) to access vital-over\r\n\t   command line object\r\n\t2. Add LiteralInsert module to insert special character literally\r\n\t  - e.g.  now inserts literal  and search them.\r\n\t3. Add workaround pasting issue for MacVim #35\r\n\t4. Fix to redraw commandline when leaving with  #67\r\n\t5. Fix  handling for  mappings #51\r\n\t6. Fix flicker at entering incsearch's commands #73\r\n\r\n\r\n","package":"incsearch.vim-1.0.2.zip","4":"incsearch.vim-1.0.2.zip","src_id":"23180","5":"23180","creation_date":"1429190602","6":"1429190602"},{"0":"5038","vim_version":"7.3","1":"7.3","script_version":"1.0.1","2":"1.0.1","version_comment":"1.0.1\t2015-01-04\r\n\t1. Fix keymapping escape\r\n\t2. Fix |last-pattern| with |g:incsearch#magic|\r\n","3":"1.0.1\t2015-01-04\r\n\t1. Fix keymapping escape\r\n\t2. Fix |last-pattern| with |g:incsearch#magic|\r\n","package":"incsearch.vim-1.0.1.zip","4":"incsearch.vim-1.0.1.zip","src_id":"22751","5":"22751","creation_date":"1420302245","6":"1420302245"},{"0":"5038","vim_version":"7.3","1":"7.3","script_version":"1.0.0","2":"1.0.0","version_comment":"1.0.0\t2014-12-14\r\n1. Improve compatibility with default commandline behavior\r\n    - Automatically apply mappings defined with |:cnoremap| and |:cmap|\r\n      See |g:incsearch#vim_cmdline_keymap|\r\n    - Support multi {lhs} and  mappings\r\n2. Support incremental highlighting in other windows.\r\n    - See |g:incsearch#no_inc_hlsearch|\r\n3. Add |(buffer-complete-prev)|\r\n4. Add |IncsearchExecute| event\r\n5. Implement |:digraph| feature\r\n6. Fix minor problems.\r\n","3":"1.0.0\t2014-12-14\r\n1. Improve compatibility with default commandline behavior\r\n    - Automatically apply mappings defined with |:cnoremap| and |:cmap|\r\n      See |g:incsearch#vim_cmdline_keymap|\r\n    - Support multi {lhs} and  mappings\r\n2. Support incremental highlighting in other windows.\r\n    - See |g:incsearch#no_inc_hlsearch|\r\n3. Add |(buffer-complete-prev)|\r\n4. Add |IncsearchExecute| event\r\n5. Implement |:digraph| feature\r\n6. Fix minor problems.\r\n","package":"incsearch.vim-1.0.0.zip","4":"incsearch.vim-1.0.0.zip","src_id":"22697","5":"22697","creation_date":"1418563066","6":"1418563066"},{"0":"5038","vim_version":"7.3","1":"7.3","script_version":"0.9.9","2":"0.9.9","version_comment":"1. Smart backward word feature. See: |g:incsearch#smart_backward_word| 2. Implement |g:incsearch#vim_cmdline_keymap| option which apply mappings defined with |:cmap| and |:cnoremap| to custome command line interface of incsearch.vim 3. Do not highlight annoying patterns which matches everything like `\\v`, `vim\\|`, etc.. 4. Interactive module management (e.g. |g:incsearch#emacs_like_keymap|) 6. Fix |c__| behavoir to be compatible with default one 7. Fix cancel behavior 8. Fix & improve {rhs} handling (after exit mappings, =, etc...) 9. Fix minor problems","3":"1. Smart backward word feature. See: |g:incsearch#smart_backward_word| 2. Implement |g:incsearch#vim_cmdline_keymap| option which apply mappings defined with |:cmap| and |:cnoremap| to custome command line interface of incsearch.vim 3. Do not highlight annoying patterns which matches everything like `\\v`, `vim\\|`, etc.. 4. Interactive module management (e.g. |g:incsearch#emacs_like_keymap|) 6. Fix |c__| behavoir to be compatible with default one 7. Fix cancel behavior 8. Fix & improve {rhs} handling (after exit mappings, =, etc...) 9. Fix minor problems","package":"incsearch.vim-0.9.9.zip","4":"incsearch.vim-0.9.9.zip","src_id":"22619","5":"22619","creation_date":"1416226275","6":"1416226275"},{"0":"5038","vim_version":"7.3","1":"7.3","script_version":"0.9.8","2":"0.9.8","version_comment":"0.9.8\t2014-10-25\r\n\t1. Handle |last-pattern| incrementally. See: |(incsearch-next)|\r\n\t2. Now |c_Ctrl-p| and |c_Ctrl-n| works by default and fix history\r\n\t   behavior to be compatible with default one\r\n\t3. Fix 'smartcase' flag detection to work with like |\\%V| and\r\n\t   repetitive escaped uppercase character like `\\V\\V`\r\n\r\n0.9.7\t2014-10-21\r\n\t1. Minor update. Fix  interruption, use |\\m| instead of |\\M|, doc\r\n\t   fix.\r\n","3":"0.9.8\t2014-10-25\r\n\t1. Handle |last-pattern| incrementally. See: |(incsearch-next)|\r\n\t2. Now |c_Ctrl-p| and |c_Ctrl-n| works by default and fix history\r\n\t   behavior to be compatible with default one\r\n\t3. Fix 'smartcase' flag detection to work with like |\\%V| and\r\n\t   repetitive escaped uppercase character like `\\V\\V`\r\n\r\n0.9.7\t2014-10-21\r\n\t1. Minor update. Fix  interruption, use |\\m| instead of |\\M|, doc\r\n\t   fix.\r\n","package":"incsearch.vim-0.9.8.zip","4":"incsearch.vim-0.9.8.zip","src_id":"22564","5":"22564","creation_date":"1414226195","6":"1414226195"},{"0":"5038","vim_version":"7.3","1":"7.3","script_version":"0.9.6","2":"0.9.6","version_comment":"Initial upload","3":"Initial upload","package":"incsearch.vim-0.9.6.zip","4":"incsearch.vim-0.9.6.zip","src_id":"22533","5":"22533","creation_date":"1413562045","6":"1413562045"}]},"5037":{"script_id":"5037","0":"5037","script_name":"Vim SELinux suite","1":"Vim SELinux suite","script_type":"ftplugin","2":"ftplugin","summary":"A collection of vim scripts to help you write SELinux policy modules.","3":"A collection of vim scripts to help you write SELinux policy modules.","description":"Vim SELinux suite is a collection of vim scripts to help you write SELinux policy modules.\r\nIt is composed of:\r\n - highlight syntax files for the SELinux filetypes;\r\n - a snippets file to use with the 'SnipMate' plugin (vimscript#2540). \r\n - an utility (a filetype plugin) called 'setool'.\r\n\r\nThe setool utility lists all the SELinux interfaces\/definitions\/templates found on the system (On redhat\/fedora, it is in the directory \/usr\/share\/selinux\/devel\/include, provided by the package selinux-policy-devel), ordered by type, in a sidebar window.\r\nThe listings are built at runtime when they are first required (by unfolding or using one of the provided functions), and show each interface name, parameters and summary.\r\nThis help the user to choose which interface to use. The user can jump to the interface definition by double-clicking if he wants to inspect it.\r\n\r\nThis plugin also sets the variables makeprg and errorformat, so you can use the command ':make' to build a module. If an error is detected, the cursor position will be set to the corresponding line.\r\n\r\nThe plugin exposes three functions:\r\n - SEToolToggle() to show\/hide the setool window;\r\n - SEToolSearch() to search the definition of the word under the cursor. If the word is found, the corresponding file is opened and setool is set to its position.\r\n - SEToolFind('word') to search for the given word instead of the word under the cursor.\r\n\r\nThe plugin defines some convenient keymaps for the buffers, to avoid calling the functions manually. They are written in the help menu of the setool window (press  in setool).\r\n\r\nNotes:\r\n - the setool window uses UTF8 characters as fold icons;\r\n - use the usual C to stop an operation, for instance if a cache takes to much time to build;\r\n - do not try to unfold 'corenetwork.if': it contains too many interfaces and the cache takes to much time to build. Just double-click to open the file, and use the command 'setl fdm=expr' to fold.\r\n - the setool window always starts with everything folded, even when toggled off\/on. It is the expected behavior.\r\n\r\n","4":"Vim SELinux suite is a collection of vim scripts to help you write SELinux policy modules.\r\nIt is composed of:\r\n - highlight syntax files for the SELinux filetypes;\r\n - a snippets file to use with the 'SnipMate' plugin (vimscript#2540). \r\n - an utility (a filetype plugin) called 'setool'.\r\n\r\nThe setool utility lists all the SELinux interfaces\/definitions\/templates found on the system (On redhat\/fedora, it is in the directory \/usr\/share\/selinux\/devel\/include, provided by the package selinux-policy-devel), ordered by type, in a sidebar window.\r\nThe listings are built at runtime when they are first required (by unfolding or using one of the provided functions), and show each interface name, parameters and summary.\r\nThis help the user to choose which interface to use. The user can jump to the interface definition by double-clicking if he wants to inspect it.\r\n\r\nThis plugin also sets the variables makeprg and errorformat, so you can use the command ':make' to build a module. If an error is detected, the cursor position will be set to the corresponding line.\r\n\r\nThe plugin exposes three functions:\r\n - SEToolToggle() to show\/hide the setool window;\r\n - SEToolSearch() to search the definition of the word under the cursor. If the word is found, the corresponding file is opened and setool is set to its position.\r\n - SEToolFind('word') to search for the given word instead of the word under the cursor.\r\n\r\nThe plugin defines some convenient keymaps for the buffers, to avoid calling the functions manually. They are written in the help menu of the setool window (press  in setool).\r\n\r\nNotes:\r\n - the setool window uses UTF8 characters as fold icons;\r\n - use the usual C to stop an operation, for instance if a cache takes to much time to build;\r\n - do not try to unfold 'corenetwork.if': it contains too many interfaces and the cache takes to much time to build. Just double-click to open the file, and use the command 'setl fdm=expr' to fold.\r\n - the setool window always starts with everything folded, even when toggled off\/on. It is the expected behavior.\r\n\r\n","install_details":"Unpack the archive and copy its content in your home folder .vim:\r\n   tar -xvf selinux-suite-.txz\r\n   cp -R selinux-suite\/* ~\/.vim\/\r\n","5":"Unpack the archive and copy its content in your home folder .vim:\r\n   tar -xvf selinux-suite-.txz\r\n   cp -R selinux-suite\/* ~\/.vim\/\r\n","first_name":"Yedvilun","6":"Yedvilun","last_name":"Prior","7":"Prior","releases":[{"0":"5037","vim_version":"7.0","1":"7.0","script_version":"1.0.4","2":"1.0.4","version_comment":"Initial upload","3":"Initial upload","package":"selinux-suite-1.0.4.txz","4":"selinux-suite-1.0.4.txz","src_id":"22530","5":"22530","creation_date":"1413285133","6":"1413285133"}]},"5036":{"script_id":"5036","0":"5036","script_name":"vim-chip8","1":"vim-chip8","script_type":"syntax","2":"syntax","summary":"Syntax highlighting and indentation rules for Chip8 assembly.","3":"Syntax highlighting and indentation rules for Chip8 assembly.","description":"Syntax highlighting and indentation rules for Chip8 assembly. These rules will apply to any *.8o file.\r\nFull support for the SuperChip and XO-Chip instruction sets is available, but not enabled out-of-the-box. Read below for directions.\r\n\r\nSupported keywords:\r\n  conditionals:  begin, else, end, if, then, while\r\n      constants:  buzzer, const, delay, key\r\n       functions:  bcd, jump, jump0, load, save, sprite\r\n          repeats:  again, loop\r\n    statements:  :alias`, :breakpoint, :next, :unpack, clear, return\r\n\r\nThere is also syntax highlighting for named subroutines, integer\/hex\/binary values, and comments.\r\n\r\n\r\nAuto-indentation will trigger for the following cases\r\n  * indent one shiftwidth on lines following `loop`\r\n  * indent one shiftwidth on lines following `while`\r\n  * unindent to matching `loop` when ending it with `again`\r\n  * indent one shiftwidth on lines following `if ... begin` and `else`\r\n  * unindent to matching `if ... begin` when ending it with `end`\r\n  * indent to zero for new labels\r\n  * indent one shiftwidth on lines following new labels\r\n  * indent to zero when ending a subroutine with `;`\r\n\r\n\r\nSuperChip\r\n\r\nAn expanded set of keywords are supported for the SuperChip instruction set. To enable these uncomment out the following line in syntax\/8o.vim:\r\n  \"let b:superChip = 1\r\n\r\nSupported keywords:\r\n    constants:  bighex\r\n     functions:  hires, loadflags, lores, saveflags, scroll-down, scroll-left, scroll-right\r\n  statements:  exit\r\n\r\n\r\nXO-Chip\r\n\r\nAnother set of keywords are available to support the XO-Chip instructions. These are also disabled by default but can be turned on by uncommenting out the following line in syntax\/8o.vim:\r\n  \"let b:superChip = 1\r\n\r\nSupported keywords:\r\n    constants:  long\r\n     functions:  plane, scroll-up\r\n  statements:  audio\r\n\r\n\r\nContribute!\r\n\r\nI really haven't done a whole lot of Chip8 programming so if something feels weird or is missing, please feel free to leave an issue of submit a pull request at https:\/\/github.com\/jackiekircher\/vim-chip8","4":"Syntax highlighting and indentation rules for Chip8 assembly. These rules will apply to any *.8o file.\r\nFull support for the SuperChip and XO-Chip instruction sets is available, but not enabled out-of-the-box. Read below for directions.\r\n\r\nSupported keywords:\r\n  conditionals:  begin, else, end, if, then, while\r\n      constants:  buzzer, const, delay, key\r\n       functions:  bcd, jump, jump0, load, save, sprite\r\n          repeats:  again, loop\r\n    statements:  :alias`, :breakpoint, :next, :unpack, clear, return\r\n\r\nThere is also syntax highlighting for named subroutines, integer\/hex\/binary values, and comments.\r\n\r\n\r\nAuto-indentation will trigger for the following cases\r\n  * indent one shiftwidth on lines following `loop`\r\n  * indent one shiftwidth on lines following `while`\r\n  * unindent to matching `loop` when ending it with `again`\r\n  * indent one shiftwidth on lines following `if ... begin` and `else`\r\n  * unindent to matching `if ... begin` when ending it with `end`\r\n  * indent to zero for new labels\r\n  * indent one shiftwidth on lines following new labels\r\n  * indent to zero when ending a subroutine with `;`\r\n\r\n\r\nSuperChip\r\n\r\nAn expanded set of keywords are supported for the SuperChip instruction set. To enable these uncomment out the following line in syntax\/8o.vim:\r\n  \"let b:superChip = 1\r\n\r\nSupported keywords:\r\n    constants:  bighex\r\n     functions:  hires, loadflags, lores, saveflags, scroll-down, scroll-left, scroll-right\r\n  statements:  exit\r\n\r\n\r\nXO-Chip\r\n\r\nAnother set of keywords are available to support the XO-Chip instructions. These are also disabled by default but can be turned on by uncommenting out the following line in syntax\/8o.vim:\r\n  \"let b:superChip = 1\r\n\r\nSupported keywords:\r\n    constants:  long\r\n     functions:  plane, scroll-up\r\n  statements:  audio\r\n\r\n\r\nContribute!\r\n\r\nI really haven't done a whole lot of Chip8 programming so if something feels weird or is missing, please feel free to leave an issue of submit a pull request at https:\/\/github.com\/jackiekircher\/vim-chip8","install_details":"Copy the corresponding files to your vim directory (~\/.vim\/ or ~\/vimfiles\/):\r\n\r\n  ftdetect\/8o.vim to ~\/.vim\/ftdetect\/8o.vim\r\n  syntax\/8o.vim to ~\/.vim\/syntax\/8o.vim\r\n  indent\/8o.vim to ~\/.vim\/indent\/8o.vim\r\n","5":"Copy the corresponding files to your vim directory (~\/.vim\/ or ~\/vimfiles\/):\r\n\r\n  ftdetect\/8o.vim to ~\/.vim\/ftdetect\/8o.vim\r\n  syntax\/8o.vim to ~\/.vim\/syntax\/8o.vim\r\n  indent\/8o.vim to ~\/.vim\/indent\/8o.vim\r\n","first_name":"jackie","6":"jackie","last_name":"kircher","7":"kircher","releases":[{"0":"5036","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"* add support for the XO-Chip\r\n* increase hex number length to 4 digits\r\n* add highlighting and indentation support for 'if ... begin' blocks\r\n* support nesting auto-indentation with loops and if statements\r\n* fix highlighting rules for 'scroll-down', 'scroll-left', and 'scroll-right'\r\n* include function highlighting for main chip8 functions by default\r\n* don't auto-indent labels until typing a space after ':'","3":"* add support for the XO-Chip\r\n* increase hex number length to 4 digits\r\n* add highlighting and indentation support for 'if ... begin' blocks\r\n* support nesting auto-indentation with loops and if statements\r\n* fix highlighting rules for 'scroll-down', 'scroll-left', and 'scroll-right'\r\n* include function highlighting for main chip8 functions by default\r\n* don't auto-indent labels until typing a space after ':'","package":"vim-chip8-1.0.zip","4":"vim-chip8-1.0.zip","src_id":"23634","5":"23634","creation_date":"1443667577","6":"1443667577"},{"0":"5036","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"vim-chip8-0.1.zip","4":"vim-chip8-0.1.zip","src_id":"22528","5":"22528","creation_date":"1413230036","6":"1413230036"}]},"5035":{"script_id":"5035","0":"5035","script_name":"whitespace syntax highlight","1":"whitespace syntax highlight","script_type":"syntax","2":"syntax","summary":"whitespace syntax highlight","3":"whitespace syntax highlight","description":"Whitespace might be one of the most difficult programming languages to read. Therefor a syntax highlight for Vim proves extremely useful.\r\n\r\nFor more information on the Whitespace, see\r\nhttp:\/\/compsoc.dur.ac.uk\/whitespace\/\r\nor\r\nhttp:\/\/en.wikipedia.org\/wiki\/Whitespace_(programming_language)\r\n","4":"Whitespace might be one of the most difficult programming languages to read. Therefor a syntax highlight for Vim proves extremely useful.\r\n\r\nFor more information on the Whitespace, see\r\nhttp:\/\/compsoc.dur.ac.uk\/whitespace\/\r\nor\r\nhttp:\/\/en.wikipedia.org\/wiki\/Whitespace_(programming_language)\r\n","install_details":":source ws.vim","5":":source ws.vim","first_name":"Rolf","6":"Rolf","last_name":"Asmund","7":"Asmund","releases":[{"0":"5035","vim_version":"7.0","1":"7.0","script_version":"1.1","2":"1.1","version_comment":"removed autoindet, only set tabsize locally, set sync method to fromstart","3":"removed autoindet, only set tabsize locally, set sync method to fromstart","package":"ws.vim","4":"ws.vim","src_id":"23730","5":"23730","creation_date":"1447431073","6":"1447431073"},{"0":"5035","vim_version":"7.3","1":"7.3","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"ws.vim","4":"ws.vim","src_id":"22523","5":"22523","creation_date":"1413111567","6":"1413111567"}]},"5034":{"script_id":"5034","0":"5034","script_name":"Dragon Curve","1":"Dragon Curve","script_type":"game","2":"game","summary":"Draws the Dragon Curve - purely recreational","3":"Draws the Dragon Curve - purely recreational","description":"This is a simple demonstration of how to create a fractal in less than 256 bytes of Vim script.\r\n\r\nSee also:\r\nhttp:\/\/en.wikipedia.org\/wiki\/Dragon_curve","4":"This is a simple demonstration of how to create a fractal in less than 256 bytes of Vim script.\r\n\r\nSee also:\r\nhttp:\/\/en.wikipedia.org\/wiki\/Dragon_curve","install_details":":source dragon_curve.vim.\r\nPress and hold F2.\r\nFor greatest value, create a document with many empty line, and place the cursor in the middle of the screen.\r\n","5":":source dragon_curve.vim.\r\nPress and hold F2.\r\nFor greatest value, create a document with many empty line, and place the cursor in the middle of the screen.\r\n","first_name":"Rolf","6":"Rolf","last_name":"Asmund","7":"Asmund","releases":[{"0":"5034","vim_version":"7.2","1":"7.2","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"dragon_curve.vim","4":"dragon_curve.vim","src_id":"22522","5":"22522","creation_date":"1413108469","6":"1413108469"}]},"5033":{"script_id":"5033","0":"5033","script_name":"Maven Compiler","1":"Maven Compiler","script_type":"ftplugin","2":"ftplugin","summary":"VIM compiler setup for Java with Maven","3":"VIM compiler setup for Java with Maven","description":"Maven Compiler is a plugin to simplify the building of Java applications which use the maven project management system. This includes:\r\n\r\n1. A syntax file containing highlighting rules for Maven's pom.xml files.\r\n2. A compiler file containing the compiler setup and error format setup.\r\n3. A file type detection script for pom.xml files to setup the filetype and syntax type for pom editing.\r\n\r\nGithub mirror:  https:\/\/github.com\/JalaiAmitahl\/maven-compiler.vim\r\n","4":"Maven Compiler is a plugin to simplify the building of Java applications which use the maven project management system. This includes:\r\n\r\n1. A syntax file containing highlighting rules for Maven's pom.xml files.\r\n2. A compiler file containing the compiler setup and error format setup.\r\n3. A file type detection script for pom.xml files to setup the filetype and syntax type for pom editing.\r\n\r\nGithub mirror:  https:\/\/github.com\/JalaiAmitahl\/maven-compiler.vim\r\n","install_details":"Pathogen is the recommended way to install the Maven Compiler plugin.\r\n\r\nIf you are using Pathogen:\r\n\r\ngit clone https:\/\/github.com\/JalaiAmitahl\/maven-compiler.vim ~\/.vim\/bundle\/\r\n\r\nOtherwise, extract the .tgz to a temporary directory and move the ftdetect, syntax and compiler folders into your ~\/.vim\/ folder.\r\n","5":"Pathogen is the recommended way to install the Maven Compiler plugin.\r\n\r\nIf you are using Pathogen:\r\n\r\ngit clone https:\/\/github.com\/JalaiAmitahl\/maven-compiler.vim ~\/.vim\/bundle\/\r\n\r\nOtherwise, extract the .tgz to a temporary directory and move the ftdetect, syntax and compiler folders into your ~\/.vim\/ folder.\r\n","first_name":"Dan","6":"Dan","last_name":"Taylor","7":"Taylor","releases":[{"0":"5033","vim_version":"7.0","1":"7.0","script_version":"1.1","2":"1.1","version_comment":"Fixed issues where only one error was being displayed at a time, added a quickfix plugin to strip duplicate and blank entries from the quickfix window.\r\n","3":"Fixed issues where only one error was being displayed at a time, added a quickfix plugin to strip duplicate and blank entries from the quickfix window.\r\n","package":"maven-compiler.tgz","4":"maven-compiler.tgz","src_id":"22590","5":"22590","creation_date":"1414857803","6":"1414857803"},{"0":"5033","vim_version":"7.0","1":"7.0","script_version":"1.0.1","2":"1.0.1","version_comment":"Small fixes to:\r\n\r\n1. POM syntax file now highlights the parent tag.\r\n2. Error format now ignores everything which is not explicitly requested.\r\n3. ftdetect didn't always override the xml file type.\r\n","3":"Small fixes to:\r\n\r\n1. POM syntax file now highlights the parent tag.\r\n2. Error format now ignores everything which is not explicitly requested.\r\n3. ftdetect didn't always override the xml file type.\r\n","package":"maven-compiler.tgz","4":"maven-compiler.tgz","src_id":"22520","5":"22520","creation_date":"1413074321","6":"1413074321"},{"0":"5033","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"maven-compiler.tgz","4":"maven-compiler.tgz","src_id":"22502","5":"22502","creation_date":"1412823328","6":"1412823328"}]},"5032":{"script_id":"5032","0":"5032","script_name":"ctrlp-hibuff","1":"ctrlp-hibuff","script_type":"utility","2":"utility","summary":"A better buffer explorer for CtrlP","3":"A better buffer explorer for CtrlP","description":"Features:\r\n\r\n* Everything highlighted\r\n* Buffer numbers\r\n* Easy buffer deletion\r\n* Relative buffer paths\r\n\r\nScreenshot: http:\/\/raw.github.com\/noscript\/ctrlp-hibuff\/master\/screen.png\r\n\r\nGithub: http:\/\/github.com\/noscript\/ctrlp-hibuff","4":"Features:\r\n\r\n* Everything highlighted\r\n* Buffer numbers\r\n* Easy buffer deletion\r\n* Relative buffer paths\r\n\r\nScreenshot: http:\/\/raw.github.com\/noscript\/ctrlp-hibuff\/master\/screen.png\r\n\r\nGithub: http:\/\/github.com\/noscript\/ctrlp-hibuff","install_details":"1. Install CtrlP","5":"1. Install CtrlP","first_name":"Sergey","6":"Sergey","last_name":"Vlasov","7":"Vlasov","releases":[{"0":"5032","vim_version":"7.0","1":"7.0","script_version":"0.3","2":"0.3","version_comment":"The plugin functionality is now a part of https:\/\/github.com\/ctrlpvim\/ctrlp.vim.\r\n\r\nCheck out the docs for new color mappings and key binding.","3":"The plugin functionality is now a part of https:\/\/github.com\/ctrlpvim\/ctrlp.vim.\r\n\r\nCheck out the docs for new color mappings and key binding.","package":"moved.txt","4":"moved.txt","src_id":"22612","5":"22612","creation_date":"1415873867","6":"1415873867"},{"0":"5032","vim_version":"7.0","1":"7.0","script_version":"0.2","2":"0.2","version_comment":"v0.2: added default colors\r\n","3":"v0.2: added default colors\r\n","package":"ctrlp-hibuff-0.2.zip","4":"ctrlp-hibuff-0.2.zip","src_id":"22503","5":"22503","creation_date":"1412864101","6":"1412864101"},{"0":"5032","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"ctrlp-hibuff.zip","4":"ctrlp-hibuff.zip","src_id":"22497","5":"22497","creation_date":"1412771202","6":"1412771202"}]},"5031":{"script_id":"5031","0":"5031","script_name":"lua_indent","1":"lua_indent","script_type":"indent","2":"indent","summary":"best lua indent plugin","3":"best lua indent plugin","description":"best lua indent plugin. source: https:\/\/github.com\/dantezhu\/lua_indent\r\nmodify from https:\/\/gist.github.com\/bonsaiviking\/8845871\r\n\r\nfix some bugs, like:\r\n\r\n\" create(\r\n\"     get(\r\n\"         1,\r\n\"         2\r\n\"         ),\r\n\"     val(),\r\n\"     )\r\n\"\r\n\" to\r\n\"\r\n\" create(\r\n\"     get(\r\n\"         1,\r\n\"         2\r\n\"     ),\r\n\"     val(),\r\n\" )","4":"best lua indent plugin. source: https:\/\/github.com\/dantezhu\/lua_indent\r\nmodify from https:\/\/gist.github.com\/bonsaiviking\/8845871\r\n\r\nfix some bugs, like:\r\n\r\n\" create(\r\n\"     get(\r\n\"         1,\r\n\"         2\r\n\"         ),\r\n\"     val(),\r\n\"     )\r\n\"\r\n\" to\r\n\"\r\n\" create(\r\n\"     get(\r\n\"         1,\r\n\"         2\r\n\"     ),\r\n\"     val(),\r\n\" )","install_details":"just put it in indent directory, enjoy it","5":"just put it in indent directory, enjoy it","first_name":"zhu","6":"zhu","last_name":"nianyang","7":"nianyang","releases":[{"0":"5031","vim_version":"7.0","1":"7.0","script_version":"1.0.1","2":"1.0.1","version_comment":"fix bug","3":"fix bug","package":"lua.vim","4":"lua.vim","src_id":"22493","5":"22493","creation_date":"1412590084","6":"1412590084"}]},"5030":{"script_id":"5030","0":"5030","script_name":"splunk.vim","1":"splunk.vim","script_type":"syntax","2":"syntax","summary":"Syntax file for Splunk Search Language","3":"Syntax file for Splunk Search Language","description":"If you do allot of work writing Splunk queries (http:\/\/www.splunk.com) and you live in the online docs for the Splunk Search Reference (see http:\/\/docs.splunk.com\/Documentation\/Splunk\/latest\/SearchReference\/WhatsInThisManual) this might be helpful.\r\n\r\nThis does color syntax highlighting for the Splunk 6.1.4 Search Language.  It does not detect syntax errors.  It recognizes all the Splunk Commands, all the Splunk Functions (both the EVAL and WHERE command functions and the functions for STATS, TIMECHART, CHART, ...), and most of the keywords for the Splunk Commands.\r\n\r\nThere is no error checking, currently.  If you use a function for the EVAL command in your STATS command the function name will be highlighted like normal.  (Something for improvement: in the future the script will be smartened-up to recognize this and indicate it is an error.)\r\n\r\nRelative Date\/Time Modifiers are recognized and look the same as Strings and Numbers.  The Relative Date\/Time Modifiers are recognized anywhere in the search.  That is a bug.  The relative date\/time modifiers are only valid after the following keywords: 'earliest', 'latest', 'span'\r\n\r\nThe relative date\/time modifier bug does slow down the whole thing a little.   This will be fixed in the next release.","4":"If you do allot of work writing Splunk queries (http:\/\/www.splunk.com) and you live in the online docs for the Splunk Search Reference (see http:\/\/docs.splunk.com\/Documentation\/Splunk\/latest\/SearchReference\/WhatsInThisManual) this might be helpful.\r\n\r\nThis does color syntax highlighting for the Splunk 6.1.4 Search Language.  It does not detect syntax errors.  It recognizes all the Splunk Commands, all the Splunk Functions (both the EVAL and WHERE command functions and the functions for STATS, TIMECHART, CHART, ...), and most of the keywords for the Splunk Commands.\r\n\r\nThere is no error checking, currently.  If you use a function for the EVAL command in your STATS command the function name will be highlighted like normal.  (Something for improvement: in the future the script will be smartened-up to recognize this and indicate it is an error.)\r\n\r\nRelative Date\/Time Modifiers are recognized and look the same as Strings and Numbers.  The Relative Date\/Time Modifiers are recognized anywhere in the search.  That is a bug.  The relative date\/time modifiers are only valid after the following keywords: 'earliest', 'latest', 'span'\r\n\r\nThe relative date\/time modifier bug does slow down the whole thing a little.   This will be fixed in the next release.","install_details":"untar in your vimfiles folder\r\n\r\n(weak, I know... but the best I got at the moment)","5":"untar in your vimfiles folder\r\n\r\n(weak, I know... but the best I got at the moment)","first_name":"The Happy","6":"The Happy","last_name":"Hacker","7":"Hacker","releases":[{"0":"5030","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"splunk.tar.gz","4":"splunk.tar.gz","src_id":"22491","5":"22491","creation_date":"1412562490","6":"1412562490"}]},"5029":{"script_id":"5029","0":"5029","script_name":"vim-shellutils","1":"vim-shellutils","script_type":"utility","2":"utility","summary":"Provides shell-like commands in Vim","3":"Provides shell-like commands in Vim","description":"Overview\r\n\r\nThe vim-shellutils provides shell-like commands such as 'rm', 'ls', and so on. This plugin is written in pure Vim script. This is because you can execute shell-like commands as long as you have huge Vim 7.3+. In addition, thanks to this plugin, you can execute it without exiting the Vim. If you want to make some direcotries, all you have to do is type :Mkdir dirA dirB from cmd-line.\r\n\r\nThe Github repository for the autocdls is available at: \r\n  https:\/\/github.com\/b4b4r07\/vim-shellutils\r\n\r\nUsage\r\n\r\n* Ls\r\n\r\n\t:Ls[!] [{path}]\r\n\t\r\nShow up some files in the {path} directory to cmd-line. If you want to show up all the files, including the files that begin with a dot in the {path} directory, then please put a bang. (:Ls!) If you omit the {path}, the current directory is specified as {path}.\r\n\r\n* File\r\n\r\n\t:File [{path}]\r\n\r\nDisplay {path} file information to cmd-line.If the {path} argument is omitted, set current buffer as {path}. The :File display many file information such as 'ls -l' of shell. \r\n\r\nFor example,\r\n\t\r\n\t[file] rw-r--r-- 2014-08-15 17:02:58 (5KB) shellutils.txt\r\n\r\n* Rm\r\n\r\n\t:Rm[!] [{path}]\r\n\r\n\r\nRemove the {path} file. If the {path} argument is omitted, remove the current buffer. The :Rm inquires whether you really delete the {path} file. If you don't do this, then please put a bang. (:Rm!)\r\n\r\n* Mkdir\r\n\r\n\t:Mkdir {path}\r\n\r\nCreate the {path} directory(ies), if they do not already exist. Unlike 'mkdir' of shell, The :Mkdir always set '-p' option, thus create directory(ies) when parent directory if no existing.\r\n\r\n* Touch\r\n\r\n\t:Touch {path}\r\n\r\nCreate blank files. Unlike that of the shell, do not edit its last modified time.\r\n\r\n* Cat\r\n\r\n\t:Cat {path}\r\n\r\nConcatenate FILE(s), to cmd-line.\r\n\r\n* Head\r\n\r\n\t:Head {path}\r\n\r\nPrint the first 10 lines of each FILE to cmd-line. With no FILE, read current buffer.\r\n\r\n* Tail\r\n\r\n\t:Tail {path}\r\n\r\nPrint the last 10 lines of each FILE to cmd-line. With no FILE, read current buffer.\r\n\r\n* Cp\r\n\r\n\t:Cp[!] {src}    {dest}\r\n\t:Cp[!] {src}... {directory}\r\n\r\nCopy {src} to {dest}, or multiple {src}s to {directory}. Prompt whether to overwrite existing regular destination files. If you don't do this, then please put a bang. (:Cp!)\r\n\r\n* Mv\r\n\r\n\t:Mv[!] {src}    {dest}\r\n\t:Mv[!] {src}... {directory}\r\n\r\nRename {src} to {dest}, or move {src}s to {directory}. Prompt whether to overwrite existing regular destination files. If you don't do this, then please put a bang. (:Mv!)\r\n\r\nFor more information, see also doc\/vim-shelltils.txt","4":"Overview\r\n\r\nThe vim-shellutils provides shell-like commands such as 'rm', 'ls', and so on. This plugin is written in pure Vim script. This is because you can execute shell-like commands as long as you have huge Vim 7.3+. In addition, thanks to this plugin, you can execute it without exiting the Vim. If you want to make some direcotries, all you have to do is type :Mkdir dirA dirB from cmd-line.\r\n\r\nThe Github repository for the autocdls is available at: \r\n  https:\/\/github.com\/b4b4r07\/vim-shellutils\r\n\r\nUsage\r\n\r\n* Ls\r\n\r\n\t:Ls[!] [{path}]\r\n\t\r\nShow up some files in the {path} directory to cmd-line. If you want to show up all the files, including the files that begin with a dot in the {path} directory, then please put a bang. (:Ls!) If you omit the {path}, the current directory is specified as {path}.\r\n\r\n* File\r\n\r\n\t:File [{path}]\r\n\r\nDisplay {path} file information to cmd-line.If the {path} argument is omitted, set current buffer as {path}. The :File display many file information such as 'ls -l' of shell. \r\n\r\nFor example,\r\n\t\r\n\t[file] rw-r--r-- 2014-08-15 17:02:58 (5KB) shellutils.txt\r\n\r\n* Rm\r\n\r\n\t:Rm[!] [{path}]\r\n\r\n\r\nRemove the {path} file. If the {path} argument is omitted, remove the current buffer. The :Rm inquires whether you really delete the {path} file. If you don't do this, then please put a bang. (:Rm!)\r\n\r\n* Mkdir\r\n\r\n\t:Mkdir {path}\r\n\r\nCreate the {path} directory(ies), if they do not already exist. Unlike 'mkdir' of shell, The :Mkdir always set '-p' option, thus create directory(ies) when parent directory if no existing.\r\n\r\n* Touch\r\n\r\n\t:Touch {path}\r\n\r\nCreate blank files. Unlike that of the shell, do not edit its last modified time.\r\n\r\n* Cat\r\n\r\n\t:Cat {path}\r\n\r\nConcatenate FILE(s), to cmd-line.\r\n\r\n* Head\r\n\r\n\t:Head {path}\r\n\r\nPrint the first 10 lines of each FILE to cmd-line. With no FILE, read current buffer.\r\n\r\n* Tail\r\n\r\n\t:Tail {path}\r\n\r\nPrint the last 10 lines of each FILE to cmd-line. With no FILE, read current buffer.\r\n\r\n* Cp\r\n\r\n\t:Cp[!] {src}    {dest}\r\n\t:Cp[!] {src}... {directory}\r\n\r\nCopy {src} to {dest}, or multiple {src}s to {directory}. Prompt whether to overwrite existing regular destination files. If you don't do this, then please put a bang. (:Cp!)\r\n\r\n* Mv\r\n\r\n\t:Mv[!] {src}    {dest}\r\n\t:Mv[!] {src}... {directory}\r\n\r\nRename {src} to {dest}, or move {src}s to {directory}. Prompt whether to overwrite existing regular destination files. If you don't do this, then please put a bang. (:Mv!)\r\n\r\nFor more information, see also doc\/vim-shelltils.txt","install_details":"Download zip-file and put it in your plugin directory","5":"Download zip-file and put it in your plugin directory","first_name":"b4b4r07","6":"b4b4r07","last_name":" ","7":" ","releases":[{"0":"5029","vim_version":"7.3","1":"7.3","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"vim-shellutils.zip","4":"vim-shellutils.zip","src_id":"22490","5":"22490","creation_date":"1412561832","6":"1412561832"}]},"5028":{"script_id":"5028","0":"5028","script_name":"ftcolor.vim","1":"ftcolor.vim","script_type":"utility","2":"utility","summary":"Switches colorschemes according to the file type.","3":"Switches colorschemes according to the file type.","description":"ftcolor.vim\r\nSwitches colorschemes according to the file type.\r\n\r\nHome page: https:\/\/github.com\/caglartoklu\/ftcolor.vim\r\nFor documentation and a .gif animation, please visit the homepage link. \r\n\r\nFor each defined file type, this plugin changes the color scheme according to the configuration:\r\nFor example, you can use the color scheme 'eclipse' for .java files, 'ibmedit' for .vb files, and 'molokai' for all the others.\r\n","4":"ftcolor.vim\r\nSwitches colorschemes according to the file type.\r\n\r\nHome page: https:\/\/github.com\/caglartoklu\/ftcolor.vim\r\nFor documentation and a .gif animation, please visit the homepage link. \r\n\r\nFor each defined file type, this plugin changes the color scheme according to the configuration:\r\nFor example, you can use the color scheme 'eclipse' for .java files, 'ibmedit' for .vb files, and 'molokai' for all the others.\r\n","install_details":"For Vundle users:\r\n    Bundle 'caglartoklu\/ftcolor.vim'\r\n\r\nFor Pathogen users:\r\n    cd ~\/.vim\/bundle\r\n    git clone git:\/\/github.com\/caglartoklu\/ftcolor.vim\r\n\r\nFor all other users, simply drop the ftcolor.vim file to your plugin directory.\r\n","5":"For Vundle users:\r\n    Bundle 'caglartoklu\/ftcolor.vim'\r\n\r\nFor Pathogen users:\r\n    cd ~\/.vim\/bundle\r\n    git clone git:\/\/github.com\/caglartoklu\/ftcolor.vim\r\n\r\nFor all other users, simply drop the ftcolor.vim file to your plugin directory.\r\n","first_name":"Caglar","6":"Caglar","last_name":"Toklu","7":"Toklu","releases":[{"0":"5028","vim_version":"7.0","1":"7.0","script_version":"0.0.2","2":"0.0.2","version_comment":"+ New: Run a custom command after the colorscheme is set, thanks for the pull request by: https:\/\/github.com\/aliou. \r\n+ Fix: Added support for help\/utility\/readonly buffers, so the colorscheme will be stable when such a buffer is opened, thanks for the feedback from: https:\/\/github.com\/ReneFroger","3":"+ New: Run a custom command after the colorscheme is set, thanks for the pull request by: https:\/\/github.com\/aliou. \r\n+ Fix: Added support for help\/utility\/readonly buffers, so the colorscheme will be stable when such a buffer is opened, thanks for the feedback from: https:\/\/github.com\/ReneFroger","package":"ftcolor.vim","4":"ftcolor.vim","src_id":"22628","5":"22628","creation_date":"1416432645","6":"1416432645"},{"0":"5028","vim_version":"7.0","1":"7.0","script_version":"0.0.1","2":"0.0.1","version_comment":"Initial upload","3":"Initial upload","package":"ftcolor.vim","4":"ftcolor.vim","src_id":"22489","5":"22489","creation_date":"1412529615","6":"1412529615"}]},"5027":{"script_id":"5027","0":"5027","script_name":"Open Plugin Page","1":"Open Plugin Page","script_type":"utility","2":"utility","summary":"A script for quick opening plugin page on Github","3":"A script for quick opening plugin page on Github","description":"# Open plugin page\r\n\r\nThis plugin allows you to quick open plugin page on github by pressing only two keys.\r\nIt is useful for exploring of examples of vimrc files. At this moment only \r\n**vundle**-format of plugin specification is supported.\r\n\r\n## Use\r\n\r\nPut cursor on the line with plugin name, i.e. on the line like:\r\n\r\n    Plugin 'xvadim\/open_plugin_page'\r\n\r\nand press o (in the normal mode). The Github-page of plugin will be\r\nopened in your default web-browser.\r\n\r\n## Configuration\r\n\r\nYou can change the manual-invocation mapping by adding this to your `.vimrc`:\r\n\r\n    map foo OpenPluginPage\r\n\r\nwhere `foo` is the mapping you want.\r\n\r\nYou can change the command for browser opening:\r\n\r\n    leg g:g:opp_open_command = \"open\"\r\n\r\n\r\nGithub address of plugin: https:\/\/github.com\/xvadim\/open_plugin_page","4":"# Open plugin page\r\n\r\nThis plugin allows you to quick open plugin page on github by pressing only two keys.\r\nIt is useful for exploring of examples of vimrc files. At this moment only \r\n**vundle**-format of plugin specification is supported.\r\n\r\n## Use\r\n\r\nPut cursor on the line with plugin name, i.e. on the line like:\r\n\r\n    Plugin 'xvadim\/open_plugin_page'\r\n\r\nand press o (in the normal mode). The Github-page of plugin will be\r\nopened in your default web-browser.\r\n\r\n## Configuration\r\n\r\nYou can change the manual-invocation mapping by adding this to your `.vimrc`:\r\n\r\n    map foo OpenPluginPage\r\n\r\nwhere `foo` is the mapping you want.\r\n\r\nYou can change the command for browser opening:\r\n\r\n    leg g:g:opp_open_command = \"open\"\r\n\r\n\r\nGithub address of plugin: https:\/\/github.com\/xvadim\/open_plugin_page","install_details":"## Installation\r\n\r\nCopy the contents of archive into `~\/.vim` or use **Vundle**:\r\n\r\n    Plugin 'xvadim\/open_plugin_page'","5":"## Installation\r\n\r\nCopy the contents of archive into `~\/.vim` or use **Vundle**:\r\n\r\n    Plugin 'xvadim\/open_plugin_page'","first_name":"Vadym","6":"Vadym","last_name":"Khokhlov","7":"Khokhlov","releases":[{"0":"5027","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"open_plugin_page.zip","4":"open_plugin_page.zip","src_id":"22477","5":"22477","creation_date":"1412352145","6":"1412352145"}]},"5026":{"script_id":"5026","0":"5026","script_name":"cascadia.vim","1":"cascadia.vim","script_type":"color scheme","2":"color scheme","summary":"Color scheme representing the beauty of the Cascadia Bioregion.","3":"Color scheme representing the beauty of the Cascadia Bioregion.","description":"A light theme created in honor of the Cascadia Bioregion. As with the Cascadian flag, the colors of this theme are meant to represent the beauty of the Pacific Northwest. Scheme was designed with Python and LaTeX in mind. \r\nThis scheme will not work with terminals, and requires a recent version (7.3) to utilize all features. ","4":"A light theme created in honor of the Cascadia Bioregion. As with the Cascadian flag, the colors of this theme are meant to represent the beauty of the Pacific Northwest. Scheme was designed with Python and LaTeX in mind. \r\nThis scheme will not work with terminals, and requires a recent version (7.3) to utilize all features. ","install_details":"Move file to .vim\/colors","5":"Move file to .vim\/colors","first_name":"Aaron","6":"Aaron","last_name":"Heuser","7":"Heuser","releases":[{"0":"5026","vim_version":"7.3","1":"7.3","script_version":"2.0.0","2":"2.0.0","version_comment":"Scheme will now recognize and highlight many more types within scripts. \r\nLaTeX $ signs are now properly highlighted.\r\nVisual mode highlight set to green.","3":"Scheme will now recognize and highlight many more types within scripts. \r\nLaTeX $ signs are now properly highlighted.\r\nVisual mode highlight set to green.","package":"cascadia.vim","4":"cascadia.vim","src_id":"22687","5":"22687","creation_date":"1418315937","6":"1418315937"},{"0":"5026","vim_version":"7.3","1":"7.3","script_version":"1.1.0","2":"1.1.0","version_comment":"Initial upload","3":"Initial upload","package":"cascadia.vim","4":"cascadia.vim","src_id":"22476","5":"22476","creation_date":"1412307031","6":"1412307031"}]},"5025":{"script_id":"5025","0":"5025","script_name":"vim-sjson","1":"vim-sjson","script_type":"syntax","2":"syntax","summary":"Syntax highlighting for Bitsquid JSON files.","3":"Syntax highlighting for Bitsquid JSON files.","description":"This plugin provides syntax highlighting for the simplified JSON (\"SJSON\") files used by the Stingray engine (http:\/\/stingrayengine.com\/). It is no longer actively maintained.","4":"This plugin provides syntax highlighting for the simplified JSON (\"SJSON\") files used by the Stingray engine (http:\/\/stingrayengine.com\/). It is no longer actively maintained.","install_details":"","5":"","first_name":"Josh","6":"Josh","last_name":"Petrie","7":"Petrie","releases":[{"0":"5025","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Final release.","3":"Final release.","package":"sjson.zip","4":"sjson.zip","src_id":"24063","5":"24063","creation_date":"1457114534","6":"1457114534"}]},"5024":{"script_id":"5024","0":"5024","script_name":"vim-geeknote","1":"vim-geeknote","script_type":"syntax","2":"syntax","summary":"Geeknote\/Evernote VIM Integration ","3":"Geeknote\/Evernote VIM Integration ","description":"Create\/edit\/view Evernote notebooks and notes in Vim.\r\n\r\nhttps:\/\/github.com\/neilagabriel\/vim-geeknote","4":"Create\/edit\/view Evernote notebooks and notes in Vim.\r\n\r\nhttps:\/\/github.com\/neilagabriel\/vim-geeknote","install_details":"https:\/\/github.com\/neilagabriel\/vim-geeknote","5":"https:\/\/github.com\/neilagabriel\/vim-geeknote","first_name":"Neil","6":"Neil","last_name":"Gabriel","7":"Gabriel","releases":[{"0":"5024","vim_version":"7.0","1":"7.0","script_version":"0.7","2":"0.7","version_comment":"Bugfixes and OS portability improvements.","3":"Bugfixes and OS portability improvements.","package":"vim-geeknote-master.zip","4":"vim-geeknote-master.zip","src_id":"22820","5":"22820","creation_date":"1421902628","6":"1421902628"},{"0":"5024","vim_version":"7.0","1":"7.0","script_version":"0.6","2":"0.6","version_comment":"Minor UI improvements.","3":"Minor UI improvements.","package":"vim-geeknote-master.zip","4":"vim-geeknote-master.zip","src_id":"22691","5":"22691","creation_date":"1418413833","6":"1418413833"},{"0":"5024","vim_version":"7.0","1":"7.0","script_version":"0.5","2":"0.5","version_comment":"More improvements and bugfixes.","3":"More improvements and bugfixes.","package":"vim-geeknote-master.zip","4":"vim-geeknote-master.zip","src_id":"22661","5":"22661","creation_date":"1417498049","6":"1417498049"},{"0":"5024","vim_version":"7.0","1":"7.0","script_version":"0.4","2":"0.4","version_comment":"Updates","3":"Updates","package":"vim-geeknote-master.zip","4":"vim-geeknote-master.zip","src_id":"22546","5":"22546","creation_date":"1413770838","6":"1413770838"},{"0":"5024","vim_version":"7.0","1":"7.0","script_version":"0.3","2":"0.3","version_comment":"Tag support and more bug fixes.","3":"Tag support and more bug fixes.","package":"vim-geeknote-master.zip","4":"vim-geeknote-master.zip","src_id":"22496","5":"22496","creation_date":"1412743957","6":"1412743957"},{"0":"5024","vim_version":"7.0","1":"7.0","script_version":"0.2","2":"0.2","version_comment":"Bugfixes and vim help","3":"Bugfixes and vim help","package":"vim-geeknote-master.zip","4":"vim-geeknote-master.zip","src_id":"22471","5":"22471","creation_date":"1412180890","6":"1412180890"},{"0":"5024","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"vim-geeknote-master.zip","4":"vim-geeknote-master.zip","src_id":"22468","5":"22468","creation_date":"1412110613","6":"1412110613"}]},"5023":{"script_id":"5023","0":"5023","script_name":"vim-line-jump","1":"vim-line-jump","script_type":"utility","2":"utility","summary":"easier way to jump lines in Tagbar and NERDTree","3":"easier way to jump lines in Tagbar and NERDTree","description":"When in Tagbar and NERDTree, It's not convenient jump lines using 'j','k'.\r\nLineJump is written to make it easier\r\n\r\nFirst, add following default map to your .vimrc\r\n    \"LineJump NERDTree key map\r\n    augroup LineJumpNerdTree\r\n        \"I find nerdtree's f map to something not that useful!\r\n        autocmd BufEnter NERD_tree_\\d\\+ nnoremap    f :silent! call LineJumpSelectForward()\r\n        autocmd BufEnter NERD_tree_\\d\\+ nnoremap    ; :silent! call LineJumpMoveForward()\r\n        autocmd BufEnter NERD_tree_\\d\\+ nnoremap    b :silent! call LineJumpSelectBackward()\r\n        autocmd BufEnter NERD_tree_\\d\\+ nnoremap    , :silent! call LineJumpMoveBackward()\r\n\r\n        autocmd BufEnter NERD_tree_\\d\\+ nnoremap    gh :silent! call LineJumpMoveTop()\r\n        autocmd BufEnter NERD_tree_\\d\\+ nnoremap    gm :silent! call LineJumpMoveMiddle()\r\n        autocmd BufEnter NERD_tree_\\d\\+ nnoremap    gl :silent! call LineJumpMoveBottom()\r\n    augroup END\r\n\r\n    \"LineJump TagBar key map\r\n    augroup LineJumpTagbar\r\n        autocmd BufEnter __Tagbar__ nnoremap    f :silent! call LineJumpSelectForward()\r\n        autocmd BufEnter __Tagbar__ nnoremap    ; :silent! call LineJumpMoveForward()\r\n        autocmd BufEnter __Tagbar__ nnoremap    b :silent! call LineJumpSelectBackward()\r\n        autocmd BufEnter __Tagbar__ nnoremap    , :silent! call LineJumpMoveBackward()\r\n\r\n        autocmd BufEnter __Tagbar__ nnoremap    gh :silent! call LineJumpMoveTop()\r\n        autocmd BufEnter __Tagbar__ nnoremap    gm :silent! call LineJumpMoveMiddle()\r\n        autocmd BufEnter __Tagbar__ nnoremap    gl :silent! call LineJumpMoveBottom()\r\n    augroup END\r\n\r\nIt has two map key 'f', 'b' and a group of function to jump quickly in NERDTree and Tagbar(if you like, also can be enable in other buffer)\r\n\r\nHere is how it works:\r\n    in NERDTree or Tagbar, press 'f'(forward jump) or 'b'(backward jump), the first alpha will be highlight,\r\n    previous selection often will have more than one match,  than:\r\n        When g:LineJumpSelectMethod is 0:\r\n            1. use ';' to move to next match\r\n            2. use ',' to move to previous match\r\n            3. use 'gh' to move to the first match\r\n            4. use 'gm' to move to the middle match \r\n            5. use 'gl' to move to the last match\r\n        When g:LineJumpSelectMethod is 1:\r\n            highlight characters will be shown, press the conreponding\r\n            key to jump to the line\r\n\r\nGlobal option:\r\n    g:LineJumpSelectMethod\r\n        define sub select way, default is 0\r\n        0: sub select by LineJumpSubForward(), LineJumpSubBackward()\r\n            need to map these two functions to some key\r\n        1: sub select by press number and alpha\r\n\r\n    g:LineJumpSelectInVisable = 0\r\n        only valid when g:LineJumpSelectMethod == 0, \r\n        if it is not 0, select will extend to the whole buffer,\r\n        not just lines visabled in the window\r\n\r\n    g:LineJumpMoveHighlight = 0\r\n        only valid when g:LineJumpSelectMethod == 0, \r\n        if it is not 0, when move using ';',',', the candidate lines will highlight\r\n\r\nrargo.m@gmail.com 2014.09.28\r\nDistributed under the same terms as Vim itself.","4":"When in Tagbar and NERDTree, It's not convenient jump lines using 'j','k'.\r\nLineJump is written to make it easier\r\n\r\nFirst, add following default map to your .vimrc\r\n    \"LineJump NERDTree key map\r\n    augroup LineJumpNerdTree\r\n        \"I find nerdtree's f map to something not that useful!\r\n        autocmd BufEnter NERD_tree_\\d\\+ nnoremap    f :silent! call LineJumpSelectForward()\r\n        autocmd BufEnter NERD_tree_\\d\\+ nnoremap    ; :silent! call LineJumpMoveForward()\r\n        autocmd BufEnter NERD_tree_\\d\\+ nnoremap    b :silent! call LineJumpSelectBackward()\r\n        autocmd BufEnter NERD_tree_\\d\\+ nnoremap    , :silent! call LineJumpMoveBackward()\r\n\r\n        autocmd BufEnter NERD_tree_\\d\\+ nnoremap    gh :silent! call LineJumpMoveTop()\r\n        autocmd BufEnter NERD_tree_\\d\\+ nnoremap    gm :silent! call LineJumpMoveMiddle()\r\n        autocmd BufEnter NERD_tree_\\d\\+ nnoremap    gl :silent! call LineJumpMoveBottom()\r\n    augroup END\r\n\r\n    \"LineJump TagBar key map\r\n    augroup LineJumpTagbar\r\n        autocmd BufEnter __Tagbar__ nnoremap    f :silent! call LineJumpSelectForward()\r\n        autocmd BufEnter __Tagbar__ nnoremap    ; :silent! call LineJumpMoveForward()\r\n        autocmd BufEnter __Tagbar__ nnoremap    b :silent! call LineJumpSelectBackward()\r\n        autocmd BufEnter __Tagbar__ nnoremap    , :silent! call LineJumpMoveBackward()\r\n\r\n        autocmd BufEnter __Tagbar__ nnoremap    gh :silent! call LineJumpMoveTop()\r\n        autocmd BufEnter __Tagbar__ nnoremap    gm :silent! call LineJumpMoveMiddle()\r\n        autocmd BufEnter __Tagbar__ nnoremap    gl :silent! call LineJumpMoveBottom()\r\n    augroup END\r\n\r\nIt has two map key 'f', 'b' and a group of function to jump quickly in NERDTree and Tagbar(if you like, also can be enable in other buffer)\r\n\r\nHere is how it works:\r\n    in NERDTree or Tagbar, press 'f'(forward jump) or 'b'(backward jump), the first alpha will be highlight,\r\n    previous selection often will have more than one match,  than:\r\n        When g:LineJumpSelectMethod is 0:\r\n            1. use ';' to move to next match\r\n            2. use ',' to move to previous match\r\n            3. use 'gh' to move to the first match\r\n            4. use 'gm' to move to the middle match \r\n            5. use 'gl' to move to the last match\r\n        When g:LineJumpSelectMethod is 1:\r\n            highlight characters will be shown, press the conreponding\r\n            key to jump to the line\r\n\r\nGlobal option:\r\n    g:LineJumpSelectMethod\r\n        define sub select way, default is 0\r\n        0: sub select by LineJumpSubForward(), LineJumpSubBackward()\r\n            need to map these two functions to some key\r\n        1: sub select by press number and alpha\r\n\r\n    g:LineJumpSelectInVisable = 0\r\n        only valid when g:LineJumpSelectMethod == 0, \r\n        if it is not 0, select will extend to the whole buffer,\r\n        not just lines visabled in the window\r\n\r\n    g:LineJumpMoveHighlight = 0\r\n        only valid when g:LineJumpSelectMethod == 0, \r\n        if it is not 0, when move using ';',',', the candidate lines will highlight\r\n\r\nrargo.m@gmail.com 2014.09.28\r\nDistributed under the same terms as Vim itself.","install_details":"extract the file under plugin to your vim's plugin directory\r\nmuch encourage using github(pathogen, NeoBundle ...)\r\nhttps:\/\/github.com\/rargo\/vim-line-jump","5":"extract the file under plugin to your vim's plugin directory\r\nmuch encourage using github(pathogen, NeoBundle ...)\r\nhttps:\/\/github.com\/rargo\/vim-line-jump","first_name":"rargo","6":"rargo","last_name":"ye","7":"ye","releases":[{"0":"5023","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"vim-line-jump.zip","4":"vim-line-jump.zip","src_id":"22464","5":"22464","creation_date":"1411897331","6":"1411897331"}]},"5022":{"script_id":"5022","0":"5022","script_name":"cobalt","1":"cobalt","script_type":"color scheme","2":"color scheme","summary":"A dark blue color theme that works in both GUI and 256 color terminals.","3":"A dark blue color theme that works in both GUI and 256 color terminals.","description":"This color scheme is based on ArchLinux Mousepad cobalt color scheme, and is more colorful than the original. It is not only for programming, but also for system administration. Try vimdiff command or view some \/etc\/configFile with this theme. \r\nAbout screenshot: You could have a glance at http:\/\/bytefluent.com\/vivify\/ (The top right corner at that page for importing new scheme). but Vivify shows a little different from reality.","4":"This color scheme is based on ArchLinux Mousepad cobalt color scheme, and is more colorful than the original. It is not only for programming, but also for system administration. Try vimdiff command or view some \/etc\/configFile with this theme. \r\nAbout screenshot: You could have a glance at http:\/\/bytefluent.com\/vivify\/ (The top right corner at that page for importing new scheme). but Vivify shows a little different from reality.","install_details":"1) Copy the file to ~\/.vim\/colors folder\r\n2) Use the command \":color scheme cobalt\" for temporarily changing.","5":"1) Copy the file to ~\/.vim\/colors folder\r\n2) Use the command \":color scheme cobalt\" for temporarily changing.","first_name":"James","6":"James","last_name":"G","7":"G","releases":[{"0":"5022","vim_version":"7.3","1":"7.3","script_version":"1.1","2":"1.1","version_comment":"Optimization many colors.","3":"Optimization many colors.","package":"cobalt.vim","4":"cobalt.vim","src_id":"22455","5":"22455","creation_date":"1411578220","6":"1411578220"},{"0":"5022","vim_version":"7.3","1":"7.3","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"cobalt.vim","4":"cobalt.vim","src_id":"22453","5":"22453","creation_date":"1411479818","6":"1411479818"}]},"5021":{"script_id":"5021","0":"5021","script_name":"vim-lamdify","1":"vim-lamdify","script_type":"syntax","2":"syntax","summary":"Conceals lambdas as lambda characters in various languages","3":"Conceals lambdas as lambda characters in various languages","description":"Currently works for lambdas in Python, JavaScript, Scheme, Erlang, Java 8, and C#\r\n\r\nSource and details are at:\r\nhttps:\/\/github.com\/calebsmith\/vim-lambdify","4":"Currently works for lambdas in Python, JavaScript, Scheme, Erlang, Java 8, and C#\r\n\r\nSource and details are at:\r\nhttps:\/\/github.com\/calebsmith\/vim-lambdify","install_details":"Untar and place the vim files in after\/syntax into your .vim\/after\/syntax tree, or install through vundle with:\r\n\r\nPlugin 'calebsmith\/vim-lambdify'\r\n\r\nAlternatively, download the tarball or checkout the source code repo and run make.","5":"Untar and place the vim files in after\/syntax into your .vim\/after\/syntax tree, or install through vundle with:\r\n\r\nPlugin 'calebsmith\/vim-lambdify'\r\n\r\nAlternatively, download the tarball or checkout the source code repo and run make.","first_name":"Caleb","6":"Caleb","last_name":"Smith","7":"Smith","releases":[{"0":"5021","vim_version":"7.3","1":"7.3","script_version":"v0.6","2":"v0.6","version_comment":"Adds support for C#","3":"Adds support for C#","package":"vim-lambdify.tar","4":"vim-lambdify.tar","src_id":"23505","5":"23505","creation_date":"1438952644","6":"1438952644"},{"0":"5021","vim_version":"7.4","1":"7.4","script_version":"v0.5","2":"v0.5","version_comment":"Adds support for lambdas in Java >= 8","3":"Adds support for lambdas in Java >= 8","package":"vim-lambdify.tar","4":"vim-lambdify.tar","src_id":"23078","5":"23078","creation_date":"1426970832","6":"1426970832"},{"0":"5021","vim_version":"7.3","1":"7.3","script_version":"0.4","2":"0.4","version_comment":"Adds Erlang and Ruby support. Also, now easier to add new languages","3":"Adds Erlang and Ruby support. Also, now easier to add new languages","package":"vim-lambdify.tar","4":"vim-lambdify.tar","src_id":"22519","5":"22519","creation_date":"1413071498","6":"1413071498"},{"0":"5021","vim_version":"7.3","1":"7.3","script_version":"0.3","2":"0.3","version_comment":"Fix to javascript.vim so that other highlighting is not overwritten","3":"Fix to javascript.vim so that other highlighting is not overwritten","package":"vim-lambdify.tar","4":"vim-lambdify.tar","src_id":"22454","5":"22454","creation_date":"1411562477","6":"1411562477"},{"0":"5021","vim_version":"7.3","1":"7.3","script_version":"0.2","2":"0.2","version_comment":"Fixes a bug where the plugin could crash if default syntax files aren't used.","3":"Fixes a bug where the plugin could crash if default syntax files aren't used.","package":"vim-lambdify.tar","4":"vim-lambdify.tar","src_id":"22452","5":"22452","creation_date":"1411436870","6":"1411436870"},{"0":"5021","vim_version":"7.3","1":"7.3","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"vim-lambdify.tar","4":"vim-lambdify.tar","src_id":"22449","5":"22449","creation_date":"1411348086","6":"1411348086"}]},"5020":{"script_id":"5020","0":"5020","script_name":"VIM PHP Refactoring Toolbox","1":"VIM PHP Refactoring Toolbox","script_type":"utility","2":"utility","summary":"Easily refactor your PHP Code","3":"Easily refactor your PHP Code","description":"This plugin contains multiple refactoring tools for PHP code.\r\n\r\nHere is the default mapping :\r\n\r\nnnoremap  rlv :call PhpRenameLocalVariable()\r\nnnoremap  rcv :call PhpRenameClassVariable()\r\nnnoremap  rm :call PhpRenameMethod()\r\nnnoremap  eu :call PhpExtractUse()\r\nvnoremap  ec :call PhpExtractConst()\r\nnnoremap  ep :call PhpExtractClassProperty()\r\nvnoremap  em :call PhpExtractMethod()\r\nnnoremap  np :call PhpCreateProperty()\r\nnnoremap  du :call PhpDetectUnusedUseStatements()\r\nvnoremap  == :call PhpAlignAssigns()\r\nnnoremap  sg :call PhpCreateSettersAndGetters()\r\nnnoremap  da :call PhpDocAll()\r\n\r\nYou can find more details on how to use this script here : https:\/\/github.com\/adoy\/vim-php-refactoring-toolbox","4":"This plugin contains multiple refactoring tools for PHP code.\r\n\r\nHere is the default mapping :\r\n\r\nnnoremap  rlv :call PhpRenameLocalVariable()\r\nnnoremap  rcv :call PhpRenameClassVariable()\r\nnnoremap  rm :call PhpRenameMethod()\r\nnnoremap  eu :call PhpExtractUse()\r\nvnoremap  ec :call PhpExtractConst()\r\nnnoremap  ep :call PhpExtractClassProperty()\r\nvnoremap  em :call PhpExtractMethod()\r\nnnoremap  np :call PhpCreateProperty()\r\nnnoremap  du :call PhpDetectUnusedUseStatements()\r\nvnoremap  == :call PhpAlignAssigns()\r\nnnoremap  sg :call PhpCreateSettersAndGetters()\r\nnnoremap  da :call PhpDocAll()\r\n\r\nYou can find more details on how to use this script here : https:\/\/github.com\/adoy\/vim-php-refactoring-toolbox","install_details":"Just copy the php-refactoring-toolbox.vim file in your ~\/.vim\/plugin\/ folder","5":"Just copy the php-refactoring-toolbox.vim file in your ~\/.vim\/plugin\/ folder","first_name":"Pierrick","6":"Pierrick","last_name":"Charron","7":"Charron","releases":[{"0":"5020","vim_version":"7.0","1":"7.0","script_version":"1.0.3","2":"1.0.3","version_comment":"Bug fixing.","3":"Bug fixing.","package":"php-refactoring-toolbox.vim","4":"php-refactoring-toolbox.vim","src_id":"25155","5":"25155","creation_date":"1494174343","6":"1494174343"},{"0":"5020","vim_version":"7.0","1":"7.0","script_version":"1.0.2","2":"1.0.2","version_comment":"- Fix add property in weird cases\r\n- Add more configurations (auto validate, default visibility)","3":"- Fix add property in weird cases\r\n- Add more configurations (auto validate, default visibility)","package":"php-refactoring-toolbox.vim","4":"php-refactoring-toolbox.vim","src_id":"23304","5":"23304","creation_date":"1432318552","6":"1432318552"},{"0":"5020","vim_version":"7.0","1":"7.0","script_version":"1.0.1","2":"1.0.1","version_comment":"- Fix a bug in RenameLocalVariable when $ is included in iskeyword\r\n- Add a g:vim_php_refactoring_use_default_mapping config to enable\/disable default mapping","3":"- Fix a bug in RenameLocalVariable when $ is included in iskeyword\r\n- Add a g:vim_php_refactoring_use_default_mapping config to enable\/disable default mapping","package":"php-refactoring-toolbox.vim","4":"php-refactoring-toolbox.vim","src_id":"22465","5":"22465","creation_date":"1411962219","6":"1411962219"},{"0":"5020","vim_version":"7.0","1":"7.0","script_version":"1.0.0","2":"1.0.0","version_comment":"Initial upload","3":"Initial upload","package":"php-refactoring-toolbox.vim","4":"php-refactoring-toolbox.vim","src_id":"22448","5":"22448","creation_date":"1411258534","6":"1411258534"}]},"5019":{"script_id":"5019","0":"5019","script_name":"oengsimple.vim","1":"oengsimple.vim","script_type":"utility","2":"utility","summary":"simplified keymap for Old English (Anglo Saxon)","3":"simplified keymap for Old English (Anglo Saxon)","description":"This keymap (based on vimscript #4147 by J\u00c3\u00bada Ron\u00c3\u00a9n) allows the input of basic Old English\/Anglo Saxon text using a standard keyboard. It has been simplified from the original to emphasize natural, fast entry. It is suitable for most work done by students of the language but is also capable of more complex manuscripts.\r\n\r\nFor example, to input \"\u00c3\u00a6\" type \"ae\". For \"ā\", type \"-a\".\r\n\r\nThe general scheme is the following.\r\n\r\n- macron (e.g. \"-a\" becomes \"ā\")\r\n. dot (e.g. \".c\" becomes \"ċ\")\r\n# Insular script (e.g. \"#g\" becomes \"ᵹ\")\r\n* miscellaneous special symbols (e.g. \"*w\" becomes \"ƿ\")\r\n\/ prevent a mapping (e.g. \"\/ae\" becomes \"ae\" instead of \"\u00c3\u00a6\")\r\n\r\nFor details, see the source file oengsimple.vim or the wiki page.","4":"This keymap (based on vimscript #4147 by J\u00c3\u00bada Ron\u00c3\u00a9n) allows the input of basic Old English\/Anglo Saxon text using a standard keyboard. It has been simplified from the original to emphasize natural, fast entry. It is suitable for most work done by students of the language but is also capable of more complex manuscripts.\r\n\r\nFor example, to input \"\u00c3\u00a6\" type \"ae\". For \"ā\", type \"-a\".\r\n\r\nThe general scheme is the following.\r\n\r\n- macron (e.g. \"-a\" becomes \"ā\")\r\n. dot (e.g. \".c\" becomes \"ċ\")\r\n# Insular script (e.g. \"#g\" becomes \"ᵹ\")\r\n* miscellaneous special symbols (e.g. \"*w\" becomes \"ƿ\")\r\n\/ prevent a mapping (e.g. \"\/ae\" becomes \"ae\" instead of \"\u00c3\u00a6\")\r\n\r\nFor details, see the source file oengsimple.vim or the wiki page.","install_details":"Put oengsimple.vim in ~\/.vim\/keymap\/.\r\n\r\nRun \":set keymap=oengsimple\".\r\n\r\nTo toggle the keymap while in Insert or Command-line mode, use CTRL-^.\r\n\r\nTo restore the default keymap, run \":set keymap=\".","5":"Put oengsimple.vim in ~\/.vim\/keymap\/.\r\n\r\nRun \":set keymap=oengsimple\".\r\n\r\nTo toggle the keymap while in Insert or Command-line mode, use CTRL-^.\r\n\r\nTo restore the default keymap, run \":set keymap=\".","first_name":"Jonathan","6":"Jonathan","last_name":"Blake","7":"Blake","releases":[{"0":"5019","vim_version":"7.0","1":"7.0","script_version":"2.0","2":"2.0","version_comment":"Made the mapping scheme more regular and predictable. Added more capabilities like Insular script and scribal abbreviations.","3":"Made the mapping scheme more regular and predictable. Added more capabilities like Insular script and scribal abbreviations.","package":"oengsimple.vim","4":"oengsimple.vim","src_id":"23133","5":"23133","creation_date":"1428180335","6":"1428180335"},{"0":"5019","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"oengsimple.vim","4":"oengsimple.vim","src_id":"22447","5":"22447","creation_date":"1411231667","6":"1411231667"}]},"5018":{"script_id":"5018","0":"5018","script_name":"vullScreen","1":"vullScreen","script_type":"utility","2":"utility","summary":"Full-screen mode for Vim on GNU\/Linux","3":"Full-screen mode for Vim on GNU\/Linux","description":"Vull..what?\r\n*************\r\nNothing fancy here (Except the strange name), vullScreen is a small vim plugin that allows you to toggle Vim in full-screen mode on GNU\/Linux.\r\n\r\nI'm talking about a real full-screen mode, no menu and no toolbars as shown in the following gif.\r\nhttps:\/\/raw.githubusercontent.com\/KabbAmine\/vullScreen.vim\/master\/.img\/vullScreen.gif\r\n\r\nTo get the last version or to have more informations check the github repo > https:\/\/github.com\/KabbAmine\/vullScreen.vim\r\nDon't forget to rate it if you find it useful ( Or useless ;) ). \r\n\r\nHow to use?\r\n***************\r\nWith the command:\r\n\r\n    :VullScreen\r\n\r\nOr using the key `` in both *NORMAL* and *INSERT* mode.\r\n\r\nWhy F11?\r\n************\r\nBecause its nice and common to a lot of programs, but if you want to change it to something else simply add to your `vimrc`:\r\n   \r\n    let g:vullscreen_key = ''\r\n\r\nNotes\r\n*******\r\nYou don't really need this plugin if you're using Vim on a terminal (The full-screen option is included in most graphical terminals).","4":"Vull..what?\r\n*************\r\nNothing fancy here (Except the strange name), vullScreen is a small vim plugin that allows you to toggle Vim in full-screen mode on GNU\/Linux.\r\n\r\nI'm talking about a real full-screen mode, no menu and no toolbars as shown in the following gif.\r\nhttps:\/\/raw.githubusercontent.com\/KabbAmine\/vullScreen.vim\/master\/.img\/vullScreen.gif\r\n\r\nTo get the last version or to have more informations check the github repo > https:\/\/github.com\/KabbAmine\/vullScreen.vim\r\nDon't forget to rate it if you find it useful ( Or useless ;) ). \r\n\r\nHow to use?\r\n***************\r\nWith the command:\r\n\r\n    :VullScreen\r\n\r\nOr using the key `` in both *NORMAL* and *INSERT* mode.\r\n\r\nWhy F11?\r\n************\r\nBecause its nice and common to a lot of programs, but if you want to change it to something else simply add to your `vimrc`:\r\n   \r\n    let g:vullscreen_key = ''\r\n\r\nNotes\r\n*******\r\nYou don't really need this plugin if you're using Vim on a terminal (The full-screen option is included in most graphical terminals).","install_details":"VullScreen requires wmctrl (http:\/\/tomas.styblo.name\/wmctrl\/), the program is present in the default repositories of most GNU\/Linux distributions, so install it using your preferred packet manager.\r\n\r\nThen, use your preferred method to install the plugin, I recommend using a vim plugin manager:\r\n\r\n* Vim-plug (https:\/\/github.com\/junegunn\/vim-plug)\r\n    In your vimrc: Plug 'KabbAmine\/vullScreen.vim'\r\n    :so %\r\n    :PlugInstall\r\n\r\n* Vundle (https:\/\/github.com\/gmarik\/Vundle.vim)\r\n    In your vimrc: Plugin 'KabbAmine\/vullScreen.vim'\r\n    :so %\r\n    :PluginInstall","5":"VullScreen requires wmctrl (http:\/\/tomas.styblo.name\/wmctrl\/), the program is present in the default repositories of most GNU\/Linux distributions, so install it using your preferred packet manager.\r\n\r\nThen, use your preferred method to install the plugin, I recommend using a vim plugin manager:\r\n\r\n* Vim-plug (https:\/\/github.com\/junegunn\/vim-plug)\r\n    In your vimrc: Plug 'KabbAmine\/vullScreen.vim'\r\n    :so %\r\n    :PlugInstall\r\n\r\n* Vundle (https:\/\/github.com\/gmarik\/Vundle.vim)\r\n    In your vimrc: Plugin 'KabbAmine\/vullScreen.vim'\r\n    :so %\r\n    :PluginInstall","first_name":"Kabbaj","6":"Kabbaj","last_name":"Amine","7":"Amine","releases":[{"0":"5018","vim_version":"7.0","1":"7.0","script_version":"0.6","2":"0.6","version_comment":"Simple internal refactoring","3":"Simple internal refactoring","package":"vullScreen.tar.gz","4":"vullScreen.tar.gz","src_id":"24072","5":"24072","creation_date":"1457277429","6":"1457277429"},{"0":"5018","vim_version":"7.0","1":"7.0","script_version":"0.5","2":"0.5","version_comment":"- Refactoring\r\n- Add a CHANGELOG file","3":"- Refactoring\r\n- Add a CHANGELOG file","package":"vullScreen.tar.gz","4":"vullScreen.tar.gz","src_id":"23555","5":"23555","creation_date":"1440682945","6":"1440682945"},{"0":"5018","vim_version":"7.0","1":"7.0","script_version":"0.3","2":"0.3","version_comment":"- Equalize splits after toggling vullScreen.\r\n- Code cleaning.","3":"- Equalize splits after toggling vullScreen.\r\n- Code cleaning.","package":"vullScreen.tar.gz","4":"vullScreen.tar.gz","src_id":"22474","5":"22474","creation_date":"1412248543","6":"1412248543"},{"0":"5018","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"vullScreen.tar.gz","4":"vullScreen.tar.gz","src_id":"22432","5":"22432","creation_date":"1410893939","6":"1410893939"}]},"5017":{"script_id":"5017","0":"5017","script_name":"rogue.vim","1":"rogue.vim","script_type":"game","2":"game","summary":"Porting of Rogue-clone II for Vim","3":"Porting of Rogue-clone II for Vim","description":"This Vim plugin is a game that is porting of Rogue-clone II.\r\nYou can enjoy the game on your Vim.\r\n\r\nExecute `:Rogue` to start the game.\r\n\r\nYou can get the latest version from here.\r\nhttps:\/\/github.com\/katono\/rogue.vim\r\n\r\nScreenshot:\r\nhttps:\/\/raw.github.com\/wiki\/katono\/rogue.vim\/image\/rogue_vim.png\r\n","4":"This Vim plugin is a game that is porting of Rogue-clone II.\r\nYou can enjoy the game on your Vim.\r\n\r\nExecute `:Rogue` to start the game.\r\n\r\nYou can get the latest version from here.\r\nhttps:\/\/github.com\/katono\/rogue.vim\r\n\r\nScreenshot:\r\nhttps:\/\/raw.github.com\/wiki\/katono\/rogue.vim\/image\/rogue_vim.png\r\n","install_details":"rogue.vim requires Lua-enabled Vim.\r\nCheck `:echo has('lua')` returns 1 and `:echo luaeval('_VERSION')` returns \"Lua 5.1\" or later.\r\n\r\nCopy autoload, doc, plugin, and syntax directories into your Vim runtimepath, like $HOME\/.vim or $VIM\/vimfiles.\r\nAnd execute `:helptags \/doc` to make help tags.\r\n\r\nYou can execute `:h rogue` to see this plugin's help.\r\n","5":"rogue.vim requires Lua-enabled Vim.\r\nCheck `:echo has('lua')` returns 1 and `:echo luaeval('_VERSION')` returns \"Lua 5.1\" or later.\r\n\r\nCopy autoload, doc, plugin, and syntax directories into your Vim runtimepath, like $HOME\/.vim or $VIM\/vimfiles.\r\nAnd execute `:helptags \/doc` to make help tags.\r\n\r\nYou can execute `:h rogue` to see this plugin's help.\r\n","first_name":"Noriaki","6":"Noriaki","last_name":"KATO","7":"KATO","releases":[{"0":"5017","vim_version":"7.3","1":"7.3","script_version":"1.0.2","2":"1.0.2","version_comment":"- Fixed for using Lua 5.3 without bit32 library\r\n- Auto make directory of g:rogue#directory if not exists\r\n- Fixed some bugs","3":"- Fixed for using Lua 5.3 without bit32 library\r\n- Auto make directory of g:rogue#directory if not exists\r\n- Fixed some bugs","package":"rogue.vim-1.0.2.zip","4":"rogue.vim-1.0.2.zip","src_id":"27812","5":"27812","creation_date":"1637503291","6":"1637503291"},{"0":"5017","vim_version":"7.3","1":"7.3","script_version":"1.0.1","2":"1.0.1","version_comment":"Fixed some bugs","3":"Fixed some bugs","package":"rogue.vim-1.0.1.zip","4":"rogue.vim-1.0.1.zip","src_id":"22450","5":"22450","creation_date":"1411395291","6":"1411395291"},{"0":"5017","vim_version":"7.3","1":"7.3","script_version":"1.0.0","2":"1.0.0","version_comment":"Initial upload","3":"Initial upload","package":"rogue.vim-1.0.0.zip","4":"rogue.vim-1.0.0.zip","src_id":"22425","5":"22425","creation_date":"1410703383","6":"1410703383"}]},"5016":{"script_id":"5016","0":"5016","script_name":"autocdls","1":"autocdls","script_type":"utility","2":"utility","summary":"Automatically shell-like ls after ':cd' in Vim","3":"Automatically shell-like ls after ':cd' in Vim","description":"Overview\r\n\r\nScreenshot:\r\n  http:\/\/cl.ly\/image\/1t0W0V3W3E2O\/autocdls.gif\r\n\r\nThe Github repository for the autocdls is available at:\r\n  https:\/\/github.com\/b4b4r07\/vim-autocdls\r\n\r\nUsage:\r\n  :Ls {path}\r\n    List the files and directories in {path} like a shell 'ls'.\r\n\r\n  In addition, execute ':Ls' automatically after executing ':cd'.","4":"Overview\r\n\r\nScreenshot:\r\n  http:\/\/cl.ly\/image\/1t0W0V3W3E2O\/autocdls.gif\r\n\r\nThe Github repository for the autocdls is available at:\r\n  https:\/\/github.com\/b4b4r07\/vim-autocdls\r\n\r\nUsage:\r\n  :Ls {path}\r\n    List the files and directories in {path} like a shell 'ls'.\r\n\r\n  In addition, execute ':Ls' automatically after executing ':cd'.","install_details":"Download zip-file and put it in your plugin directory","5":"Download zip-file and put it in your plugin directory","first_name":"b4b4r07","6":"b4b4r07","last_name":" ","7":" ","releases":[{"0":"5016","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"autocdls.zip","4":"autocdls.zip","src_id":"22417","5":"22417","creation_date":"1410618702","6":"1410618702"}]},"5015":{"script_id":"5015","0":"5015","script_name":"C64.vim","1":"C64.vim","script_type":"color scheme","2":"color scheme","summary":"A scheme using the 16 Commodore 64 colors","3":"A scheme using the 16 Commodore 64 colors","description":"Feeling a bit nostalgic, I created a Vim C64 color scheme using only the 16 preset colors available on the Commodore 64. These blues and pastels may look familiar to programmers who grew up in the eighties.\r\n\r\nNo bold.  No italics.  \r\n\r\nSee screenshots here: http:\/\/aaronmaupin.com\/blog\/vim-c64-color-scheme\/","4":"Feeling a bit nostalgic, I created a Vim C64 color scheme using only the 16 preset colors available on the Commodore 64. These blues and pastels may look familiar to programmers who grew up in the eighties.\r\n\r\nNo bold.  No italics.  \r\n\r\nSee screenshots here: http:\/\/aaronmaupin.com\/blog\/vim-c64-color-scheme\/","install_details":"On Linux\/Unix, place C64.vim in ~\/.vim\/colors\/\r\n\r\nOn Windows, place it in C:\/Users\/\/vimfiles\/colors\/","5":"On Linux\/Unix, place C64.vim in ~\/.vim\/colors\/\r\n\r\nOn Windows, place it in C:\/Users\/\/vimfiles\/colors\/","first_name":"Aaron","6":"Aaron","last_name":"Maupin","7":"Maupin","releases":[{"0":"5015","vim_version":"7.0","1":"7.0","script_version":"0.02","2":"0.02","version_comment":"Fixed DiffAdd legibility.","3":"Fixed DiffAdd legibility.","package":"C64.vim","4":"C64.vim","src_id":"22394","5":"22394","creation_date":"1409506977","6":"1409506977"},{"0":"5015","vim_version":"7.0","1":"7.0","script_version":"0.01","2":"0.01","version_comment":"Initial upload","3":"Initial upload","package":"C64.vim","4":"C64.vim","src_id":"22393","5":"22393","creation_date":"1409503403","6":"1409503403"}]},"5014":{"script_id":"5014","0":"5014","script_name":"vim-nerdtree_plugin_open","1":"vim-nerdtree_plugin_open","script_type":"utility","2":"utility","summary":"Open files independent from vim (NERD tree extension)","3":"Open files independent from vim (NERD tree extension)","description":"Grab the latest dev version from github: https:\/\/github.com\/aufgang001\/vim-nerdtree_plugin_open\r\n\r\nNERD tree (https:\/\/github.com\/scrooloose\/nerdtree) allows you to explore your filesystem and to open files and directories in Vim. \r\nThe NerdtreePluginOpen extends this functionality with the ability to open files with an appropriate application independent from vim (e.g. non-text files).","4":"Grab the latest dev version from github: https:\/\/github.com\/aufgang001\/vim-nerdtree_plugin_open\r\n\r\nNERD tree (https:\/\/github.com\/scrooloose\/nerdtree) allows you to explore your filesystem and to open files and directories in Vim. \r\nThe NerdtreePluginOpen extends this functionality with the ability to open files with an appropriate application independent from vim (e.g. non-text files).","install_details":"Install this plugin with your favorite plugin-manager or unzip the archive manual into your ~\/.vim directory. \r\n\r\nExtend your .vimrc file with the following command:\r\nlet g:nerdtree_plugin_open_cmd = ''\r\n\r\n\"Your command\" depends on the operating system and desktop environment. (e.g. gnome-open, kde-open, xdg-open or use your own cmd)\r\n","5":"Install this plugin with your favorite plugin-manager or unzip the archive manual into your ~\/.vim directory. \r\n\r\nExtend your .vimrc file with the following command:\r\nlet g:nerdtree_plugin_open_cmd = ''\r\n\r\n\"Your command\" depends on the operating system and desktop environment. (e.g. gnome-open, kde-open, xdg-open or use your own cmd)\r\n","first_name":"Seb","6":"Seb","last_name":"","7":"","releases":[{"0":"5014","vim_version":"7.0","1":"7.0","script_version":"1.0.0","2":"1.0.0","version_comment":"Initial upload","3":"Initial upload","package":"vim-nerdtree_plugin_open.zip","4":"vim-nerdtree_plugin_open.zip","src_id":"22390","5":"22390","creation_date":"1409478694","6":"1409478694"}]},"5013":{"script_id":"5013","0":"5013","script_name":"autotype.vim","1":"autotype.vim","script_type":"utility","2":"utility","summary":"Yes, Vim will work for you.","3":"Yes, Vim will work for you.","description":"An auto typing machine for vim.\r\n\r\nimage: https:\/\/github.com\/Rykka\/github_things\/raw\/master\/image\/autotype.gif\r\n\r\nSee details in github: https:\/\/github.com\/Rykka\/autotype.vim\r\n\r\n","4":"An auto typing machine for vim.\r\n\r\nimage: https:\/\/github.com\/Rykka\/github_things\/raw\/master\/image\/autotype.gif\r\n\r\nSee details in github: https:\/\/github.com\/Rykka\/autotype.vim\r\n\r\n","install_details":"Using Vundle or NeoBundle.\r\n\r\nBundle 'Rykka\/autotype.vim'","5":"Using Vundle or NeoBundle.\r\n\r\nBundle 'Rykka\/autotype.vim'","first_name":"Rykka","6":"Rykka","last_name":"f","7":"f","releases":[{"0":"5013","vim_version":"7.0","1":"7.0","script_version":"0.10.7","2":"0.10.7","version_comment":"0.10.7: Add Python Code Block.\r\n0.10.6: Add ``INCLUDE`` tag. Strip syntax.\r\n0.10.5: Add Local Context Support. ","3":"0.10.7: Add Python Code Block.\r\n0.10.6: Add ``INCLUDE`` tag. Strip syntax.\r\n0.10.5: Add Local Context Support. ","package":"autotype.vim-0.10.7.zip","4":"autotype.vim-0.10.7.zip","src_id":"22396","5":"22396","creation_date":"1409529646","6":"1409529646"},{"0":"5013","vim_version":"7.0","1":"7.0","script_version":"0.10.4","2":"0.10.4","version_comment":"0.10.4 : Add Comment Tags.\r\n0.10.3 : Add `INSERT`, Add Bar\/Bang support for CMDS. \r\n0.10.2 : Add speed setup with :AtpSpd\r\n","3":"0.10.4 : Add Comment Tags.\r\n0.10.3 : Add `INSERT`, Add Bar\/Bang support for CMDS. \r\n0.10.2 : Add speed setup with :AtpSpd\r\n","package":"autotype.vim-0.10.4.zip","4":"autotype.vim-0.10.4.zip","src_id":"22388","5":"22388","creation_date":"1409421713","6":"1409421713"},{"0":"5013","vim_version":"7.0","1":"7.0","script_version":"0.10.1","2":"0.10.1","version_comment":"0.10.0: Add Syn\/Cmd\/Var. \r\nNow Vim will work for you.","3":"0.10.0: Add Syn\/Cmd\/Var. \r\nNow Vim will work for you.","package":"autotype.vim-0.10.1.zip","4":"autotype.vim-0.10.1.zip","src_id":"22385","5":"22385","creation_date":"1409375749","6":"1409375749"},{"0":"5013","vim_version":"7.0","1":"7.0","script_version":"0.9","2":"0.9","version_comment":"Initial upload","3":"Initial upload","package":"autotype.vim-0.9.zip","4":"autotype.vim-0.9.zip","src_id":"22375","5":"22375","creation_date":"1409241914","6":"1409241914"}]},"5012":{"script_id":"5012","0":"5012","script_name":"Vim Markdown Preview","1":"Vim Markdown Preview","script_type":"utility","2":"utility","summary":"A Vim plugin for previewing markdown files in a browser.","3":"A Vim plugin for previewing markdown files in a browser.","description":"A Vim plugin for previewing markdown files in a browser. This plugin was designed to maintain focus on Vim but use Google Chrome to preview rendered markdown. Thus, everything is done in the background so you never have to leave vim.\r\n\r\nFor more the most updated version, more details, and a screenshot see: https:\/\/github.com\/JamshedVesuna\/vim-markdown-preview\r\n\r\nUsage\r\n\r\nWhen in a *.markdown or *.md file, vim-markdown-preview does the following on a write to the buffer:\r\n    1. If you are not previewing the current file:\r\n            Open an html rendered version of your file in Google Chrome in the background.\r\n    2. Otherwise:\r\n            Refresh your preview of the current markdown file in Google Chrome.\r\nUncomment the last line in plugin\/vim-markdown-preview.vim to map Ctrl-p to the above instead of on write.\r\n\r\nBehind The Scenes:\r\n\r\n    1. First, vim-markdown-preview renders your markdown as html and creates a temporary file vim-markdown-preview.html in \/tmp\/.\r\n    2. Next, vim-markdown-preview then either opens the html file or refreshes the Google Chrome tab.\r\n    3. Lastly, vim-markdown-preview removes the temporary file so nothing left behind.\r\n\r\nRequirements:\r\n\r\n    1. Markdown\r\n    2. xdotool\r\n    3. Google Chrome","4":"A Vim plugin for previewing markdown files in a browser. This plugin was designed to maintain focus on Vim but use Google Chrome to preview rendered markdown. Thus, everything is done in the background so you never have to leave vim.\r\n\r\nFor more the most updated version, more details, and a screenshot see: https:\/\/github.com\/JamshedVesuna\/vim-markdown-preview\r\n\r\nUsage\r\n\r\nWhen in a *.markdown or *.md file, vim-markdown-preview does the following on a write to the buffer:\r\n    1. If you are not previewing the current file:\r\n            Open an html rendered version of your file in Google Chrome in the background.\r\n    2. Otherwise:\r\n            Refresh your preview of the current markdown file in Google Chrome.\r\nUncomment the last line in plugin\/vim-markdown-preview.vim to map Ctrl-p to the above instead of on write.\r\n\r\nBehind The Scenes:\r\n\r\n    1. First, vim-markdown-preview renders your markdown as html and creates a temporary file vim-markdown-preview.html in \/tmp\/.\r\n    2. Next, vim-markdown-preview then either opens the html file or refreshes the Google Chrome tab.\r\n    3. Lastly, vim-markdown-preview removes the temporary file so nothing left behind.\r\n\r\nRequirements:\r\n\r\n    1. Markdown\r\n    2. xdotool\r\n    3. Google Chrome","install_details":"With Pathogen: Place vim-markdown-preview\/ in .vim\/bundle\/.","5":"With Pathogen: Place vim-markdown-preview\/ in .vim\/bundle\/.","first_name":"Jamshed","6":"Jamshed","last_name":"Vesuna","7":"Vesuna","releases":[{"0":"5012","vim_version":"7.0","1":"7.0","script_version":"0.2","2":"0.2","version_comment":"Added screenshot gif","3":"Added screenshot gif","package":"vim-markdown-preview.zip","4":"vim-markdown-preview.zip","src_id":"22367","5":"22367","creation_date":"1409110956","6":"1409110956"},{"0":"5012","vim_version":"7.0","1":"7.0","script_version":"7.0","2":"7.0","version_comment":"Initial upload","3":"Initial upload","package":"vim-markdown-preview.zip","4":"vim-markdown-preview.zip","src_id":"22366","5":"22366","creation_date":"1409097276","6":"1409097276"}]},"5011":{"script_id":"5011","0":"5011","script_name":"autorepeat.vim","1":"autorepeat.vim","script_type":"utility","2":"utility","summary":"Repeat the normal mode command automatically.","3":"Repeat the normal mode command automatically.","description":"*autorepeat* is a Vim plugin to repeat the normal mode command automatically.\r\n\r\nLatest version:\r\nhttps:\/\/github.com\/daisuzu\/autorepeat.vim\r\n\r\nUSAGE\r\n\r\nWrite the following setting to your vimrc.\r\n\r\n\r\n    nmap . (autorepeat)\r\n\r\n\r\nKey sequence that is entered after \".\"  is repeated automatically.\r\nRepetition continues until you enter any key.\r\n\r\nExamples:\r\n\r\n    Repeat the movement to the left.(l)\r\n\r\n        .l\r\n\r\n\r\n    Repeat scroll to the bottom.()\r\n\r\n        .\r\n\r\n\r\n    Repeat the deletion of the next word of the next match.(nwdiw)\r\n\r\n        .nwdiw","4":"*autorepeat* is a Vim plugin to repeat the normal mode command automatically.\r\n\r\nLatest version:\r\nhttps:\/\/github.com\/daisuzu\/autorepeat.vim\r\n\r\nUSAGE\r\n\r\nWrite the following setting to your vimrc.\r\n\r\n\r\n    nmap . (autorepeat)\r\n\r\n\r\nKey sequence that is entered after \".\"  is repeated automatically.\r\nRepetition continues until you enter any key.\r\n\r\nExamples:\r\n\r\n    Repeat the movement to the left.(l)\r\n\r\n        .l\r\n\r\n\r\n    Repeat scroll to the bottom.()\r\n\r\n        .\r\n\r\n\r\n    Repeat the deletion of the next word of the next match.(nwdiw)\r\n\r\n        .nwdiw","install_details":"Copy it to your plugin directory.","5":"Copy it to your plugin directory.","first_name":"Daisuke","6":"Daisuke","last_name":"Suzuki","7":"Suzuki","releases":[{"0":"5011","vim_version":"7.2","1":"7.2","script_version":"0.0.1-1","2":"0.0.1-1","version_comment":"Fix document","3":"Fix document","package":"autorepeat.vim.zip","4":"autorepeat.vim.zip","src_id":"22365","5":"22365","creation_date":"1409062856","6":"1409062856"},{"0":"5011","vim_version":"7.2","1":"7.2","script_version":"0.0.1","2":"0.0.1","version_comment":"Initial upload","3":"Initial upload","package":"autorepeat.vim.zip","4":"autorepeat.vim.zip","src_id":"22361","5":"22361","creation_date":"1408892434","6":"1408892434"}]},"5010":{"script_id":"5010","0":"5010","script_name":"json-formatter.vim","1":"json-formatter.vim","script_type":"ftplugin","2":"ftplugin","summary":"A Vim plugin for formatting saved JSON file.","3":"A Vim plugin for formatting saved JSON file.","description":"https:\/\/github.com\/XadillaX\/json-formatter.vim","4":"https:\/\/github.com\/XadillaX\/json-formatter.vim","install_details":"json-formatter.txt*      For Vim version 7.0. \r\n\r\nAuthor:\t        Kaidi Zhu                             October 10, 2015\r\nVersion:        1.1.2\r\n\r\nFor instructions on installing this file, type\r\n\t:help add-local-help |add-local-help| inside Vim.\r\n    \r\nHomepage: https:\/\/www.vim.org\/scripts\/script.php?script_id=5010\r\n\r\n\r\n==============================================================================\r\n1. Contents                                      *json_formatter* *json_formatter-contents*\r\n\r\n    1. Contents...............................: |json_formatter-contents|\r\n    2. Description............................: |json_formatter-description|\r\n    3. Installation...........................: |json_formatter-installation|\r\n    4. Configuration..........................: |json_formatter-configure|\r\n       3.1 Global Variables...................: |json_formatter-globals|\r\n       3.2 Default Keys.......................: |json_formatter-mappings|\r\n    4. Commands...............................: |json_formatter-commands|\r\n       JSONFormatter..........................: |:JSONFormatter|\r\n\r\n==============================================================================\r\n2. Description                                   *json_formatter-description*\r\n\r\nA Vim plugin for formatting JSON.\r\n\r\nJSONLint is used to first check the validity of the JSON.\r\nIf JSONLint reports error a Vim buffer is open (similar to the |quickfix|\r\nwindow) which will display the error and the line information. \r\nClicking on that line will take you to the error in the buffer\r\nwhich contains the JSON.  \r\n\r\nIf there are no errors, the selected text is replaced with the formatted\r\ntext.\r\n\r\nThe json-formatter Vim plugin calls the NodeJS jjson module to perform\r\nthe formatting.  \r\n\r\n==============================================================================\r\n3. Installation                                 *json_formatter-installation*\r\n\r\nIf using Vundle:\r\n    Add this `repo` to your Vundle configuration: \r\n        Bundle \"XadillaX\/json-formatter.vim\" \r\n\r\nNo package manager:\r\n    If you are not using a Vim package manager, simply unzip the \r\n    jjson-formatter.zip file into your .vim or vimfiles directory.  \r\n    There are 2 files:\r\n        plugin\/json-formatter.vim\r\n        doc\/json-formatter.txt\r\n\r\nNode.js\r\n    A Node.js module is required which performs the actual formatting\r\n    and syntax checking.  You must first install Node.js from here:\r\n        https:\/\/nodejs.org\/\r\n\r\n    Once installed, you must install the jjson package.  Using a \r\n    terminal or command prompt, you can run the following:\r\n        $ npm install jjson -g \r\n\r\n    To verify the package is installed correctly, from the terminal\r\n    or command prompt you can run:\r\n        jjson -h\r\n\r\n    You should get output similar to this: >\r\n        Usage: jjson [options]\r\n\r\n        Options:\r\n           -f, --file              JSON filename.\r\n           -e, --encoding          JSON file encoding.  [utf8]\r\n           -i, --indent            Number of indent for each line.  [2]\r\n           -v, --vim-plugin-mode   Whether it's in VIM plugin mode.\r\n\r\n==============================================================================\r\n3. Configuration                                 *json_formatter-configure*\r\n\r\n3.1 Global Variables                             *json_formatter-globals*\r\n\r\nYou can customize the json_formatter by setting various global variables in\r\nyour |.vimrc|. \r\n\r\nRunning the Node.js package to format the JSON can be modified using \r\nsome additional options (if necessary):  >\r\n\r\n    json_formatter_command\r\n<       Default: jjson\r\n        You can include a full path to the script if necessary using: >\r\n            let g:json_formatter_command = 'C:\\Program Files\\nodejs\\node_modules\\.bin\\jjson.cmd'\r\n    json_formatter_command_encoding\r\n<       Default: \r\n        This will pass an encoding value using the -e parameter.  >\r\n            let g:json_formatter_command_encoding = 'utf8'\r\n    json_formatter_command_indent\r\n<       Default:\r\n        This will pass an indent value using the -i parameter.  >\r\n            let g:json_formatter_command_indent = '4'\r\n\r\nThe jjson-formatter error window is displayed if there is \r\na problem with the JSON.  The following settings allow you to decide\r\nwhere this window is opened and it's size.\r\n>\r\n    json_formatter_window_use_horiz\r\n<       Default: 1\r\n        When the json_formatter window is opened, it uses a horizontal split at the\r\n        bottom of the Vim window.  It can optionally use a vertical split by\r\n        setting this option to 0.  >\r\n            let g:json_formatter_window_use_horiz = 0  \" Use vertical split\r\n    json_formatter_window_height\r\n<       Default: 8\r\n        If using a horizontal split, this option controls how high to make\r\n        the window.  >\r\n            let g:json_formatter_window_height = 8\r\n    json_formatter_window_width\r\n<       Default: 30\r\n        If using a vertical split, this option controls how wide to make the\r\n        window.  >\r\n            let g:json_formatter_window_width = 30\r\n    json_formatter_window_use_bottom\r\n<       Default: 1\r\n        If using a horizontal split, this option control whether the window is\r\n        opened at the top or bottom of the Vim window.  Setting this option to\r\n        0 forces the window to open at the top of the Vim window.  >\r\n            let g:json_formatter_window_use_bottom = 1\r\n    json_formatter_window_use_right\r\n<       Default: 1\r\n        If using a vertical split, this option control whether the window is\r\n        opened on the left or right side of the Vim window.  To force the\r\n        window to open on the left side, set this option to 0.  >\r\n            let g:json_formatter_window_use_right = 1\r\n    json_formatter_window_increment\r\n<       Default: 1\r\n        If using a vertical split the default width of the vertical window may\r\n        be too narrow to view enough of the elements.  Pressing [] will\r\n        increase the size of the window by this number of columns.  Pressing\r\n        [] again will toggle it back to the original size.  >\r\n            let g:json_formatter_window_increment = 50\r\n\r\n<\r\n3.2 Buffer Variables                             *json_formatter-buffer*\r\n\r\nYou can customize the json_formatter by setting various buffer local variables in\r\nyour buffer to allow you to format the JSON differently for each buffer.\r\nFor example, if you are working on different projects and one specifies\r\nand indent standard of 4 and the other 2, then you can define a buffer\r\nlocal variable to override the jjson command to pass the correct values\r\nto Node.js.  The let statements below differ from the globals with a \r\n\"b:\" at the start, rather than a \"g:\". >\r\n\r\n    json_formatter_command\r\n<       Default: jjson\r\n        You can include a full path to the script if necessary using: >\r\n            let b:json_formatter_command = 'C:\\Program Files\\nodejs\\node_modules\\.bin\\jjson.cmd'\r\n    json_formatter_command_encoding\r\n<       Default: \r\n        This will pass an encoding value using the -e parameter.  >\r\n            let b:json_formatter_command_encoding = 'latin1'\r\n    json_formatter_command_indent\r\n<       Default:\r\n        This will pass an indent value using the -i parameter.  >\r\n            let b:json_formatter_command_indent = '8'\r\n\r\n==============================================================================\r\n4. Commands:                                     *json_formatter-commands*\r\n\r\nJSONFormatter                                    *:JSONFormatter*\r\n     The JSONFormatter command will either format the JSON supplied\r\n     or open the |quickfix| window and show any errors reported\r\n     by the tools.  Clicking or hitting  on any of the lines\r\n     reported in the quickfix window will take you directly to \r\n     that location.\r\n\r\n         Examples: >\r\n            :JSONFormatter\r\n            :1,100JSONFormatter\r\n            :'<,'>JSONFormatter\r\n<            \r\n\r\nvim: ts=4 ft=help tw=78","5":"json-formatter.txt*      For Vim version 7.0. \r\n\r\nAuthor:\t        Kaidi Zhu                             October 10, 2015\r\nVersion:        1.1.2\r\n\r\nFor instructions on installing this file, type\r\n\t:help add-local-help |add-local-help| inside Vim.\r\n    \r\nHomepage: https:\/\/www.vim.org\/scripts\/script.php?script_id=5010\r\n\r\n\r\n==============================================================================\r\n1. Contents                                      *json_formatter* *json_formatter-contents*\r\n\r\n    1. Contents...............................: |json_formatter-contents|\r\n    2. Description............................: |json_formatter-description|\r\n    3. Installation...........................: |json_formatter-installation|\r\n    4. Configuration..........................: |json_formatter-configure|\r\n       3.1 Global Variables...................: |json_formatter-globals|\r\n       3.2 Default Keys.......................: |json_formatter-mappings|\r\n    4. Commands...............................: |json_formatter-commands|\r\n       JSONFormatter..........................: |:JSONFormatter|\r\n\r\n==============================================================================\r\n2. Description                                   *json_formatter-description*\r\n\r\nA Vim plugin for formatting JSON.\r\n\r\nJSONLint is used to first check the validity of the JSON.\r\nIf JSONLint reports error a Vim buffer is open (similar to the |quickfix|\r\nwindow) which will display the error and the line information. \r\nClicking on that line will take you to the error in the buffer\r\nwhich contains the JSON.  \r\n\r\nIf there are no errors, the selected text is replaced with the formatted\r\ntext.\r\n\r\nThe json-formatter Vim plugin calls the NodeJS jjson module to perform\r\nthe formatting.  \r\n\r\n==============================================================================\r\n3. Installation                                 *json_formatter-installation*\r\n\r\nIf using Vundle:\r\n    Add this `repo` to your Vundle configuration: \r\n        Bundle \"XadillaX\/json-formatter.vim\" \r\n\r\nNo package manager:\r\n    If you are not using a Vim package manager, simply unzip the \r\n    jjson-formatter.zip file into your .vim or vimfiles directory.  \r\n    There are 2 files:\r\n        plugin\/json-formatter.vim\r\n        doc\/json-formatter.txt\r\n\r\nNode.js\r\n    A Node.js module is required which performs the actual formatting\r\n    and syntax checking.  You must first install Node.js from here:\r\n        https:\/\/nodejs.org\/\r\n\r\n    Once installed, you must install the jjson package.  Using a \r\n    terminal or command prompt, you can run the following:\r\n        $ npm install jjson -g \r\n\r\n    To verify the package is installed correctly, from the terminal\r\n    or command prompt you can run:\r\n        jjson -h\r\n\r\n    You should get output similar to this: >\r\n        Usage: jjson [options]\r\n\r\n        Options:\r\n           -f, --file              JSON filename.\r\n           -e, --encoding          JSON file encoding.  [utf8]\r\n           -i, --indent            Number of indent for each line.  [2]\r\n           -v, --vim-plugin-mode   Whether it's in VIM plugin mode.\r\n\r\n==============================================================================\r\n3. Configuration                                 *json_formatter-configure*\r\n\r\n3.1 Global Variables                             *json_formatter-globals*\r\n\r\nYou can customize the json_formatter by setting various global variables in\r\nyour |.vimrc|. \r\n\r\nRunning the Node.js package to format the JSON can be modified using \r\nsome additional options (if necessary):  >\r\n\r\n    json_formatter_command\r\n<       Default: jjson\r\n        You can include a full path to the script if necessary using: >\r\n            let g:json_formatter_command = 'C:\\Program Files\\nodejs\\node_modules\\.bin\\jjson.cmd'\r\n    json_formatter_command_encoding\r\n<       Default: \r\n        This will pass an encoding value using the -e parameter.  >\r\n            let g:json_formatter_command_encoding = 'utf8'\r\n    json_formatter_command_indent\r\n<       Default:\r\n        This will pass an indent value using the -i parameter.  >\r\n            let g:json_formatter_command_indent = '4'\r\n\r\nThe jjson-formatter error window is displayed if there is \r\na problem with the JSON.  The following settings allow you to decide\r\nwhere this window is opened and it's size.\r\n>\r\n    json_formatter_window_use_horiz\r\n<       Default: 1\r\n        When the json_formatter window is opened, it uses a horizontal split at the\r\n        bottom of the Vim window.  It can optionally use a vertical split by\r\n        setting this option to 0.  >\r\n            let g:json_formatter_window_use_horiz = 0  \" Use vertical split\r\n    json_formatter_window_height\r\n<       Default: 8\r\n        If using a horizontal split, this option controls how high to make\r\n        the window.  >\r\n            let g:json_formatter_window_height = 8\r\n    json_formatter_window_width\r\n<       Default: 30\r\n        If using a vertical split, this option controls how wide to make the\r\n        window.  >\r\n            let g:json_formatter_window_width = 30\r\n    json_formatter_window_use_bottom\r\n<       Default: 1\r\n        If using a horizontal split, this option control whether the window is\r\n        opened at the top or bottom of the Vim window.  Setting this option to\r\n        0 forces the window to open at the top of the Vim window.  >\r\n            let g:json_formatter_window_use_bottom = 1\r\n    json_formatter_window_use_right\r\n<       Default: 1\r\n        If using a vertical split, this option control whether the window is\r\n        opened on the left or right side of the Vim window.  To force the\r\n        window to open on the left side, set this option to 0.  >\r\n            let g:json_formatter_window_use_right = 1\r\n    json_formatter_window_increment\r\n<       Default: 1\r\n        If using a vertical split the default width of the vertical window may\r\n        be too narrow to view enough of the elements.  Pressing [] will\r\n        increase the size of the window by this number of columns.  Pressing\r\n        [] again will toggle it back to the original size.  >\r\n            let g:json_formatter_window_increment = 50\r\n\r\n<\r\n3.2 Buffer Variables                             *json_formatter-buffer*\r\n\r\nYou can customize the json_formatter by setting various buffer local variables in\r\nyour buffer to allow you to format the JSON differently for each buffer.\r\nFor example, if you are working on different projects and one specifies\r\nand indent standard of 4 and the other 2, then you can define a buffer\r\nlocal variable to override the jjson command to pass the correct values\r\nto Node.js.  The let statements below differ from the globals with a \r\n\"b:\" at the start, rather than a \"g:\". >\r\n\r\n    json_formatter_command\r\n<       Default: jjson\r\n        You can include a full path to the script if necessary using: >\r\n            let b:json_formatter_command = 'C:\\Program Files\\nodejs\\node_modules\\.bin\\jjson.cmd'\r\n    json_formatter_command_encoding\r\n<       Default: \r\n        This will pass an encoding value using the -e parameter.  >\r\n            let b:json_formatter_command_encoding = 'latin1'\r\n    json_formatter_command_indent\r\n<       Default:\r\n        This will pass an indent value using the -i parameter.  >\r\n            let b:json_formatter_command_indent = '8'\r\n\r\n==============================================================================\r\n4. Commands:                                     *json_formatter-commands*\r\n\r\nJSONFormatter                                    *:JSONFormatter*\r\n     The JSONFormatter command will either format the JSON supplied\r\n     or open the |quickfix| window and show any errors reported\r\n     by the tools.  Clicking or hitting  on any of the lines\r\n     reported in the quickfix window will take you directly to \r\n     that location.\r\n\r\n         Examples: >\r\n            :JSONFormatter\r\n            :1,100JSONFormatter\r\n            :'<,'>JSONFormatter\r\n<            \r\n\r\nvim: ts=4 ft=help tw=78","first_name":"Chu","6":"Chu","last_name":"Khaidi","7":"Khaidi","releases":[{"0":"5010","vim_version":"7.0","1":"7.0","script_version":"1.1.2","2":"1.1.2","version_comment":"Support quickfix list.","3":"Support quickfix list.","package":"json-formatter.vim-1.1.2.zip","4":"json-formatter.vim-1.1.2.zip","src_id":"27964","5":"27964","creation_date":"1647345213","6":"1647345213"},{"0":"5010","vim_version":"7.0","1":"7.0","script_version":"1.0.0","2":"1.0.0","version_comment":"Initial upload","3":"Initial upload","package":"json-formatter.vim-master.zip","4":"json-formatter.vim-master.zip","src_id":"22355","5":"22355","creation_date":"1408692492","6":"1408692492"}]},"5009":{"script_id":"5009","0":"5009","script_name":"256_darkdot","1":"256_darkdot","script_type":"color scheme","2":"color scheme","summary":"DarkDot color scheme for 256 color terminals","3":"DarkDot color scheme for 256 color terminals","description":"This is a color scheme based on the DarkDot color scheme for 256 color\r\nterminals.\r\n\r\nOriginally taken from here:\r\n\r\nhttps:\/\/web.archive.org\/web\/20130313011037\/http:\/\/www.frexx.de\/xterm-256-notes\/\r\n\r\nOn Github here:\r\n\r\nhttps:\/\/github.com\/rkitover\/256_darkdot_vim\r\n\r\nFollow the above Github link for a screenshot.","4":"This is a color scheme based on the DarkDot color scheme for 256 color\r\nterminals.\r\n\r\nOriginally taken from here:\r\n\r\nhttps:\/\/web.archive.org\/web\/20130313011037\/http:\/\/www.frexx.de\/xterm-256-notes\/\r\n\r\nOn Github here:\r\n\r\nhttps:\/\/github.com\/rkitover\/256_darkdot_vim\r\n\r\nFollow the above Github link for a screenshot.","install_details":"Put the file into ~\/.vim\/colors\r\n\r\nThen in your .vimrc add the following:\r\n\r\nsyntax on\r\ncolors 256_darkdot","5":"Put the file into ~\/.vim\/colors\r\n\r\nThen in your .vimrc add the following:\r\n\r\nsyntax on\r\ncolors 256_darkdot","first_name":"Rafael","6":"Rafael","last_name":"Kitover","7":"Kitover","releases":[{"0":"5009","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"256_darkdot.vim","4":"256_darkdot.vim","src_id":"22354","5":"22354","creation_date":"1408619227","6":"1408619227"}]},"5008":{"script_id":"5008","0":"5008","script_name":"a indent","1":"a indent","script_type":"utility","2":"utility","summary":"a_indent helps you to select\/move in different code block","3":"a_indent helps you to select\/move in different code block","description":"\r\na_indent helps you to select\/move in different code block\r\n\r\ngithub : https:\/\/github.com\/caigithub\/a_indent\/wiki\r\n\r\nkeys : \r\n        am : select a code block, ( stops when meet a same indent line and last line is blank )\r\n        ai : select all the indent block, ( stops when meet a indent out line )\r\n\r\n        M : jump to the next same indent code block\r\n        < : jump to the previous same indent code block\r\n        H : jump to the previous indent out code line\r\n        L : jump to the next indent out code line\r\n\r\n============\r\nexamples\r\n\r\n  1 function a()\r\n  2     code block 1 begins                 \/\/execute vam  will select code block 1 ( line2-line8 )\r\n  3         code block 2 begins\r\n  4         code block 2 ends               \/\/execute vam will select code block 2 ( line3-line4 )\r\n  5\r\n  6         code block 3 begins             \/\/execute vam will select code block 3 ( line6-line7 )\r\n  7             code block 4 begins\/ends, code block3 ends\r\n  8     code block 1 ends\r\n  9\r\n 10     code block 5 begins here            \/\/execute vam will select code block 6 ( line10-line12 )\r\n 11     code block 5 begins here            \/\/execute vai will select code block 1 and block 6 ( line2-line12 )\r\n 12     code block 5 begins here\r\n 13 endfunction\r\n\r\n","4":"\r\na_indent helps you to select\/move in different code block\r\n\r\ngithub : https:\/\/github.com\/caigithub\/a_indent\/wiki\r\n\r\nkeys : \r\n        am : select a code block, ( stops when meet a same indent line and last line is blank )\r\n        ai : select all the indent block, ( stops when meet a indent out line )\r\n\r\n        M : jump to the next same indent code block\r\n        < : jump to the previous same indent code block\r\n        H : jump to the previous indent out code line\r\n        L : jump to the next indent out code line\r\n\r\n============\r\nexamples\r\n\r\n  1 function a()\r\n  2     code block 1 begins                 \/\/execute vam  will select code block 1 ( line2-line8 )\r\n  3         code block 2 begins\r\n  4         code block 2 ends               \/\/execute vam will select code block 2 ( line3-line4 )\r\n  5\r\n  6         code block 3 begins             \/\/execute vam will select code block 3 ( line6-line7 )\r\n  7             code block 4 begins\/ends, code block3 ends\r\n  8     code block 1 ends\r\n  9\r\n 10     code block 5 begins here            \/\/execute vam will select code block 6 ( line10-line12 )\r\n 11     code block 5 begins here            \/\/execute vai will select code block 1 and block 6 ( line2-line12 )\r\n 12     code block 5 begins here\r\n 13 endfunction\r\n\r\n","install_details":"","5":"","first_name":"colin","6":"colin","last_name":"cai","7":"cai","releases":[{"0":"5008","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"a_indent.vim","4":"a_indent.vim","src_id":"22351","5":"22351","creation_date":"1408497537","6":"1408497537"}]},"5007":{"script_id":"5007","0":"5007","script_name":"phpmanual","1":"phpmanual","script_type":"ftplugin","2":"ftplugin","summary":"PHP manual for vim, update to PHP5.5","3":"PHP manual for vim, update to PHP5.5","description":"This is php manual plugin for vim with help keyword doc.\r\n\r\nYou can do these with this plugin:\r\n\r\nin normal mode,\r\n\r\n    press SHIFT-k to view the Explanation of the keyword under the cursor\r\n    press CTRL-ALT-k to see the online manual of the keyword under the cursor\r\n\r\nin visual mode,\r\n\r\n    select content, and then press SHIFT-k to view the Explanation of the content\r\n    select content, and then press CTRL-ALT-k to see the online manual of the content","4":"This is php manual plugin for vim with help keyword doc.\r\n\r\nYou can do these with this plugin:\r\n\r\nin normal mode,\r\n\r\n    press SHIFT-k to view the Explanation of the keyword under the cursor\r\n    press CTRL-ALT-k to see the online manual of the keyword under the cursor\r\n\r\nin visual mode,\r\n\r\n    select content, and then press SHIFT-k to view the Explanation of the content\r\n    select content, and then press CTRL-ALT-k to see the online manual of the content","install_details":"","5":"","first_name":"-","6":"-","last_name":"-","7":"-","releases":[{"0":"5007","vim_version":"7.0","1":"7.0","script_version":"5.6","2":"5.6","version_comment":"PHP5.6","3":"PHP5.6","package":"vim-php-manual.zip","4":"vim-php-manual.zip","src_id":"22747","5":"22747","creation_date":"1420125518","6":"1420125518"}]},"5006":{"script_id":"5006","0":"5006","script_name":"Vim-EPUB","1":"Vim-EPUB","script_type":"ftplugin","2":"ftplugin","summary":"Plugin for EPUB ebooks' edition","3":"Plugin for EPUB ebooks' edition","description":"Github page: https:\/\/github.com\/etnadji\/vim-epub\r\n\r\nWith Vim, you can already edit an epub file with the builtin zip.vim.\r\nBut it's only a RO opening. If you want to add or remove files, you need to extract and recompress the EPUB. That's boring.\r\n\r\nWith Vim-EPUB, you can:\r\n\r\n− Add an empty page (XHTML).\r\n− Add an empty CSS stylesheet.\r\n− Add a Table of contents page.\r\n− Add medias (images, etc.).\r\n− Make your OS open the EPUB with its selected reader.\r\n− Provide a menu to easily link XHTML and CSS contents.\r\n\r\nSee https:\/\/github.com\/etnadji\/vim-epub\/wiki\/Features for a complete list.","4":"Github page: https:\/\/github.com\/etnadji\/vim-epub\r\n\r\nWith Vim, you can already edit an epub file with the builtin zip.vim.\r\nBut it's only a RO opening. If you want to add or remove files, you need to extract and recompress the EPUB. That's boring.\r\n\r\nWith Vim-EPUB, you can:\r\n\r\n− Add an empty page (XHTML).\r\n− Add an empty CSS stylesheet.\r\n− Add a Table of contents page.\r\n− Add medias (images, etc.).\r\n− Make your OS open the EPUB with its selected reader.\r\n− Provide a menu to easily link XHTML and CSS contents.\r\n\r\nSee https:\/\/github.com\/etnadji\/vim-epub\/wiki\/Features for a complete list.","install_details":"Vim-EPUB does not work under Windows, due to zip.vim limitations.\r\n\r\nYou need a Vim version compiled with python support.\r\n\r\nThe CleanFromExports command needs Pandoc: http:\/\/johnmacfarlane.net\/pandoc\/\r\n\r\nFor plugin managers:\r\n\r\nVundle\r\n---------\r\nBundle 'etnadji\/vim-epub'\r\n\r\nThen :BundleInstall\r\n\r\nVim-Plug\r\n-----------\r\nPlug 'etnadji\/vim-epub'\r\n\r\nThen :PlugUpdate\r\n\r\nPathogen\r\n------------\r\ngit clone https:\/\/github.com\/etnadji\/vim-epub ~\/.vim\/bundle\/vim-epub","5":"Vim-EPUB does not work under Windows, due to zip.vim limitations.\r\n\r\nYou need a Vim version compiled with python support.\r\n\r\nThe CleanFromExports command needs Pandoc: http:\/\/johnmacfarlane.net\/pandoc\/\r\n\r\nFor plugin managers:\r\n\r\nVundle\r\n---------\r\nBundle 'etnadji\/vim-epub'\r\n\r\nThen :BundleInstall\r\n\r\nVim-Plug\r\n-----------\r\nPlug 'etnadji\/vim-epub'\r\n\r\nThen :PlugUpdate\r\n\r\nPathogen\r\n------------\r\ngit clone https:\/\/github.com\/etnadji\/vim-epub ~\/.vim\/bundle\/vim-epub","first_name":"Etienne","6":"Etienne","last_name":"Nadji","7":"Nadji","releases":[{"0":"5006","vim_version":"7.0","1":"7.0","script_version":"0.6","2":"0.6","version_comment":"New commands: OpenMedia, FindFontDefinition.\r\ng:VimEPUB_OpenCommand option becomes g:VimEPUB_EreaderCommand\r\nFixed french documentation (by junkblocker).\r\nSMIL snippets in Extras.","3":"New commands: OpenMedia, FindFontDefinition.\r\ng:VimEPUB_OpenCommand option becomes g:VimEPUB_EreaderCommand\r\nFixed french documentation (by junkblocker).\r\nSMIL snippets in Extras.","package":"vim-epub.zip","4":"vim-epub.zip","src_id":"23782","5":"23782","creation_date":"1449579462","6":"1449579462"},{"0":"5006","vim_version":"7.0","1":"7.0","script_version":"0.5","2":"0.5","version_comment":"Commands:\r\n*CleanFromExports* Clean up epubs files typically made with Word & Calibre. Needs pydoc.\r\n*NewEPUB*  Make a new EPUB from vim buffers\r\n*ViewMetadatas* Show EPUB's metadatas (human readable)","3":"Commands:\r\n*CleanFromExports* Clean up epubs files typically made with Word & Calibre. Needs pydoc.\r\n*NewEPUB*  Make a new EPUB from vim buffers\r\n*ViewMetadatas* Show EPUB's metadatas (human readable)","package":"vim-epub.zip","4":"vim-epub.zip","src_id":"22584","5":"22584","creation_date":"1414612984","6":"1414612984"},{"0":"5006","vim_version":"7.0","1":"7.0","script_version":"0.4","2":"0.4","version_comment":"RemoveUnusedMedias, UpdateToc commands.","3":"RemoveUnusedMedias, UpdateToc commands.","package":"vim-epub.zip","4":"vim-epub.zip","src_id":"22411","5":"22411","creation_date":"1410032311","6":"1410032311"},{"0":"5006","vim_version":"7.0","1":"7.0","script_version":"0.3","2":"0.3","version_comment":"Add DiffEPUB, DiffLastEPUB, MergeFiles commands.\r\nAdd two configuration variables.","3":"Add DiffEPUB, DiffLastEPUB, MergeFiles commands.\r\nAdd two configuration variables.","package":"vim-epub.zip","4":"vim-epub.zip","src_id":"22399","5":"22399","creation_date":"1409598097","6":"1409598097"},{"0":"5006","vim_version":"7.0","1":"7.0","script_version":"0.2","2":"0.2","version_comment":"RenameFile,BackupEPUB commands.\r\nVarious improvements.","3":"RenameFile,BackupEPUB commands.\r\nVarious improvements.","package":"vim-epub.zip","4":"vim-epub.zip","src_id":"22378","5":"22378","creation_date":"1409320673","6":"1409320673"},{"0":"5006","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"vim-epub.zip","4":"vim-epub.zip","src_id":"22344","5":"22344","creation_date":"1408342679","6":"1408342679"}]},"5005":{"script_id":"5005","0":"5005","script_name":"Session-Viminfo-Management","1":"Session-Viminfo-Management","script_type":"utility","2":"utility","summary":"The plug-in improves upon Vim's built-in :mksession and :wviminfo commands.","3":"The plug-in improves upon Vim's built-in :mksession and :wviminfo commands.","description":"The plug-in improves upon Vim's built-in :mksession and :wviminfo commands. \r\nIt provide great convinience to save and load your Vim session and viminfo files automatically. \r\n\r\nTypically, you can save your Vim session and viminfo files in one command and load them efficiently. \r\nEven better, it can automatically load\/save vim session and viminfo files when entering vim and leaving vim environment. \r\nThat are very useful if you want Vim to quickly swith between different projects, automatically loading the files you were last working on in that project, and enable you to continue where you left off. \r\n\r\nTerminology and Default Values:\r\nWorkspace files: I will shortly call vim session and viminfo files as \"Workspace files\" in this manual. workspace: All prompt messages in Vim prefixed with \"workspace:\" are from this Session-Viminfo-Management plugin. \r\nDefault Values:\r\n    * Default name for workspace files is: workspace.session workspace.viminfo\r\n    * Default saving path: vim current path (Type Vim Ex command getcwd() to get it)\r\n\r\nFunctionality:\r\n* This plugin provides automation ability when launching Vim and leaving Vim.\r\n* It provides two Ex commands: Savews, Loadws.\r\n* There is one global option you can use: wsOverwrite.\r\n\r\nAutomation\r\n\r\nThis plugin provides automation ability when launching Vim and leaving Vim.\r\n\r\nWhen launching Vim, this plugin will detect current path and load default workspace files(workspace.session and workspace.viminfo) if exist. If no default workspace files found, it will check whether there are files having suffix \".session\" and \".viminfo\" in pair. If yes, it will prompt a list for user selection if there are more than one pair.\r\n\r\nExample 1:\r\nIf you're at \/home\/test, there are:\r\n\r\n    workspace.session\r\n    workspace.viminfo\r\n    test.session\r\n    test.viminfo\r\n\r\nWhen you launch vim, it will load workspace.session and workspace.viminfo with prompt message by default. As following illustration: http:\/\/brant-public.qiniudn.com\/vim01-automation_lauching.png\r\n\r\nExample 2:\r\nIf you're at \/home\/test, there are:\r\n\r\n    test01.session\r\n    test01.viminfo\r\n    test02.session\r\n    test02.viminfo\r\n\r\nWhen you launch vim, it will list all workspace files for your choice. As following:\r\n\r\n  workspace: Please input the expected workspace index you want to load:\r\n    [0] \/home\/test\/test01\r\n    [1] \/home\/test\/test02\r\n  Your input(q to exit this function of workspace plugin):\r\n\r\nThen you type a legal number in range(0,1), it will load the specific workspace files. Also you can type 'Q' or 'q' to do nothing with workspace files. If you give an exception, you will be required to input again. As following illustration: http:\/\/brant-public.qiniudn.com\/vim02-automation_lauching_dup_echo_disappear.png\r\n\r\nThere is a little compatible problem in some tty console. Please read \"Limitation and Known issues\" section in this Readme.md for more details.\r\nLeaving Vim\r\n\r\nExample 1:\r\n\r\n  : Savews my.ws\r\n  : Loadws wow.ws\r\n  : Savews new.ws\r\n  : qa\r\n\r\nResult:\r\nThis plugin will automatically save session and viminfo files to the last workspace files\r\n\r\n    new.session\r\n    new.viminfo\r\n\r\nAs following illustration: vim03-automation_leaving_new.ws.png\r\nEx Commands\r\n\r\nThis plugin provide two Ex commands: Savews, Loadws.\r\nSavews\r\n\r\nSave vim session and viminfo files when you type Ex command :Savews with proper arguments. Particularly, if option wsOverwrite is 1(This is default value), when you exit from Vim, this plugin will save session and viminfo files to your last saved\/loaded workspace files automatically.\r\n\r\nExample 1:\r\n\r\n  :Savews    \r\n\r\nResult:\r\nWill create workspace.session and workspace.viminfo in current folder, if they didnot existed beforehand.\r\nPlease see |'wsOverwrite'| for more details about overwrite behavior.\r\n\r\nExample 2:\r\n\r\n  :Savews \/home\/myproject \r\n\r\nResult:\r\nWill create:\r\n\r\n    \/home\/myproject\/workspace.session\r\n    \/home\/myproject\/workspace.viminfo Please make sure folder \/home\/myproject existed beforehand.\r\n    Please see |'wsOverwrite'| for more details about overwrite behavior.\r\n\r\nExample 3:\r\n\r\n  :Savews my.ws\r\n\r\nResult:\r\nSave to my.session and my.viminfo in current folder.\r\nPlease see |'wsOverwrite'| for more details about overwrite behavior.\r\n\r\nExample 4:\r\n\r\n  :Savews \/home\/myproject\/my.ws\r\n\r\nResult:\r\nYou will get my.session and my.viminfo in \/home\/myproject folder if \/home\/myproject existed.\r\nPlease see |'wsOverwrite'| for more details about overwrite behavior.\r\n\r\nTwo point please keep in mind when using Savews:\r\n\r\n    You must have suffix .ws, if you want to specify name for session and viminfo files, like example 3 and example 4. Otherwise, they will have default name, workspace.session and workspace.viminfo.\r\n    Please remember to use :qwa to quit Vim if you want to reopen all windows\/tabs you're editing.\r\n    The reason is that Savews command will save workspace files automatically when you exit Vim. So if you have opened many windows\/tabs, but closed them one by one, there would be only one window is openning just before you exit Vim, workspace plugin will only can remember the last window and just reopen it for you when you enter Vim next time by loading your workspace files.\r\n\r\nLoadws\r\n\r\nLoad vim session and viminfo files.\r\n\r\nExample 1:\r\n\r\n  :Lavews    \r\n\r\nResult:\r\nWill load workspace.session and workspace.viminfo in current folder, if they existed beforehand.\r\n\r\nExample 2:\r\n\r\n  :Lavews \/home\/myproject \r\n\r\nResult:\r\nWill load:\r\n\r\n    \/home\/myproject\/workspace.session\r\n    \/home\/myproject\/workspace.viminfo Please make sure workspace files existed beforehand.\r\n\r\nExample 3:\r\n\r\n  :Lavews my.ws\r\n\r\nResult:\r\nWill load my.session and my.viminfo in current folder.\r\n\r\nExample 4:\r\n\r\n  :Lavews \/home\/myproject\/my.ws\r\n\r\nResult:\r\nWill load my.session and my.viminfo in \/home\/myproject folder if existed.\r\n\r\nYou'd better not to run :Loadws in same Vim twice. Please read \"Limitation and Known issues\" section in this Readme.md for more details.\r\nOptions\r\n\r\nThere is one global option you can use: wsOverwrite.\r\nwsOverwrite\r\n\r\nValue: 0 or 1.\r\nDefault: 1.\r\n\r\nIf there are vim session and viminfo files with same name when you issue :Savews, you can overwrite them by setting this option to 1:\r\n\r\n  let g:wsOverwrite=1\r\n\r\nIf g:wsOverwrite is 0, and there are workspace.session and workspace.viminfo, when you type:\r\n\r\n  :Savews\r\n\r\nIt will said:\r\n\r\n    Workspace files existed, and wsOverwrite is 0, will not overwrite existed files.\r\n\r\nIT RECOMMENDED STRONGLY YOU KEEP IT DEFAULT AS 1. BECAUSE IF IT'S 0, WHEN YOU EXIT VIM, IT WON'T SAVE YOUR WORKSPACE FILES AUTOMATICALLY.\r\n\r\nLimitation and Known issues:\r\n* Windows is not a target of this plugin. I think you would experience some problmes if you want to use this plugin on Windows Vim.\r\n* There is compatible problem when work with autochdir option. Recommend to remove autochdir option from your ~\/.vimrc. For my experiences, if enable autochdir option in Vim, users will mess up themselves when trying to provide relative pathes of Vim session and viminfo files. It seems it can't have impact if you provide absolute path for Vim session and viminfo files.\r\n* There is a little compatible problem in some tty console. In some tty console, when launching Vim and this plugin prompt a workspace list for your choice, after you input your choice, it will echo all message one time. Anyway, the function still works.\r\n* You'd better not to run :Loadws in same Vim twice. If you once run Loadws to load your workspace files, then run Loadws to reload them again in the same Vim, it will not close all openning windows and tabs. In other words, you may see double windows have been opened for the same file.\r\n\r\nLicense:\r\nThis software is licensed under the MIT License. Copyright 2014 Brant Chen (Primary: brantchen2008@gmail.com and secondary: xkdcc@163.com).\r\n\r\nFor more details, please access: https:\/\/github.com\/xkdcc\/Session-Viminfo-Management\r\nOr :help workspaceIntro.","4":"The plug-in improves upon Vim's built-in :mksession and :wviminfo commands. \r\nIt provide great convinience to save and load your Vim session and viminfo files automatically. \r\n\r\nTypically, you can save your Vim session and viminfo files in one command and load them efficiently. \r\nEven better, it can automatically load\/save vim session and viminfo files when entering vim and leaving vim environment. \r\nThat are very useful if you want Vim to quickly swith between different projects, automatically loading the files you were last working on in that project, and enable you to continue where you left off. \r\n\r\nTerminology and Default Values:\r\nWorkspace files: I will shortly call vim session and viminfo files as \"Workspace files\" in this manual. workspace: All prompt messages in Vim prefixed with \"workspace:\" are from this Session-Viminfo-Management plugin. \r\nDefault Values:\r\n    * Default name for workspace files is: workspace.session workspace.viminfo\r\n    * Default saving path: vim current path (Type Vim Ex command getcwd() to get it)\r\n\r\nFunctionality:\r\n* This plugin provides automation ability when launching Vim and leaving Vim.\r\n* It provides two Ex commands: Savews, Loadws.\r\n* There is one global option you can use: wsOverwrite.\r\n\r\nAutomation\r\n\r\nThis plugin provides automation ability when launching Vim and leaving Vim.\r\n\r\nWhen launching Vim, this plugin will detect current path and load default workspace files(workspace.session and workspace.viminfo) if exist. If no default workspace files found, it will check whether there are files having suffix \".session\" and \".viminfo\" in pair. If yes, it will prompt a list for user selection if there are more than one pair.\r\n\r\nExample 1:\r\nIf you're at \/home\/test, there are:\r\n\r\n    workspace.session\r\n    workspace.viminfo\r\n    test.session\r\n    test.viminfo\r\n\r\nWhen you launch vim, it will load workspace.session and workspace.viminfo with prompt message by default. As following illustration: http:\/\/brant-public.qiniudn.com\/vim01-automation_lauching.png\r\n\r\nExample 2:\r\nIf you're at \/home\/test, there are:\r\n\r\n    test01.session\r\n    test01.viminfo\r\n    test02.session\r\n    test02.viminfo\r\n\r\nWhen you launch vim, it will list all workspace files for your choice. As following:\r\n\r\n  workspace: Please input the expected workspace index you want to load:\r\n    [0] \/home\/test\/test01\r\n    [1] \/home\/test\/test02\r\n  Your input(q to exit this function of workspace plugin):\r\n\r\nThen you type a legal number in range(0,1), it will load the specific workspace files. Also you can type 'Q' or 'q' to do nothing with workspace files. If you give an exception, you will be required to input again. As following illustration: http:\/\/brant-public.qiniudn.com\/vim02-automation_lauching_dup_echo_disappear.png\r\n\r\nThere is a little compatible problem in some tty console. Please read \"Limitation and Known issues\" section in this Readme.md for more details.\r\nLeaving Vim\r\n\r\nExample 1:\r\n\r\n  : Savews my.ws\r\n  : Loadws wow.ws\r\n  : Savews new.ws\r\n  : qa\r\n\r\nResult:\r\nThis plugin will automatically save session and viminfo files to the last workspace files\r\n\r\n    new.session\r\n    new.viminfo\r\n\r\nAs following illustration: vim03-automation_leaving_new.ws.png\r\nEx Commands\r\n\r\nThis plugin provide two Ex commands: Savews, Loadws.\r\nSavews\r\n\r\nSave vim session and viminfo files when you type Ex command :Savews with proper arguments. Particularly, if option wsOverwrite is 1(This is default value), when you exit from Vim, this plugin will save session and viminfo files to your last saved\/loaded workspace files automatically.\r\n\r\nExample 1:\r\n\r\n  :Savews    \r\n\r\nResult:\r\nWill create workspace.session and workspace.viminfo in current folder, if they didnot existed beforehand.\r\nPlease see |'wsOverwrite'| for more details about overwrite behavior.\r\n\r\nExample 2:\r\n\r\n  :Savews \/home\/myproject \r\n\r\nResult:\r\nWill create:\r\n\r\n    \/home\/myproject\/workspace.session\r\n    \/home\/myproject\/workspace.viminfo Please make sure folder \/home\/myproject existed beforehand.\r\n    Please see |'wsOverwrite'| for more details about overwrite behavior.\r\n\r\nExample 3:\r\n\r\n  :Savews my.ws\r\n\r\nResult:\r\nSave to my.session and my.viminfo in current folder.\r\nPlease see |'wsOverwrite'| for more details about overwrite behavior.\r\n\r\nExample 4:\r\n\r\n  :Savews \/home\/myproject\/my.ws\r\n\r\nResult:\r\nYou will get my.session and my.viminfo in \/home\/myproject folder if \/home\/myproject existed.\r\nPlease see |'wsOverwrite'| for more details about overwrite behavior.\r\n\r\nTwo point please keep in mind when using Savews:\r\n\r\n    You must have suffix .ws, if you want to specify name for session and viminfo files, like example 3 and example 4. Otherwise, they will have default name, workspace.session and workspace.viminfo.\r\n    Please remember to use :qwa to quit Vim if you want to reopen all windows\/tabs you're editing.\r\n    The reason is that Savews command will save workspace files automatically when you exit Vim. So if you have opened many windows\/tabs, but closed them one by one, there would be only one window is openning just before you exit Vim, workspace plugin will only can remember the last window and just reopen it for you when you enter Vim next time by loading your workspace files.\r\n\r\nLoadws\r\n\r\nLoad vim session and viminfo files.\r\n\r\nExample 1:\r\n\r\n  :Lavews    \r\n\r\nResult:\r\nWill load workspace.session and workspace.viminfo in current folder, if they existed beforehand.\r\n\r\nExample 2:\r\n\r\n  :Lavews \/home\/myproject \r\n\r\nResult:\r\nWill load:\r\n\r\n    \/home\/myproject\/workspace.session\r\n    \/home\/myproject\/workspace.viminfo Please make sure workspace files existed beforehand.\r\n\r\nExample 3:\r\n\r\n  :Lavews my.ws\r\n\r\nResult:\r\nWill load my.session and my.viminfo in current folder.\r\n\r\nExample 4:\r\n\r\n  :Lavews \/home\/myproject\/my.ws\r\n\r\nResult:\r\nWill load my.session and my.viminfo in \/home\/myproject folder if existed.\r\n\r\nYou'd better not to run :Loadws in same Vim twice. Please read \"Limitation and Known issues\" section in this Readme.md for more details.\r\nOptions\r\n\r\nThere is one global option you can use: wsOverwrite.\r\nwsOverwrite\r\n\r\nValue: 0 or 1.\r\nDefault: 1.\r\n\r\nIf there are vim session and viminfo files with same name when you issue :Savews, you can overwrite them by setting this option to 1:\r\n\r\n  let g:wsOverwrite=1\r\n\r\nIf g:wsOverwrite is 0, and there are workspace.session and workspace.viminfo, when you type:\r\n\r\n  :Savews\r\n\r\nIt will said:\r\n\r\n    Workspace files existed, and wsOverwrite is 0, will not overwrite existed files.\r\n\r\nIT RECOMMENDED STRONGLY YOU KEEP IT DEFAULT AS 1. BECAUSE IF IT'S 0, WHEN YOU EXIT VIM, IT WON'T SAVE YOUR WORKSPACE FILES AUTOMATICALLY.\r\n\r\nLimitation and Known issues:\r\n* Windows is not a target of this plugin. I think you would experience some problmes if you want to use this plugin on Windows Vim.\r\n* There is compatible problem when work with autochdir option. Recommend to remove autochdir option from your ~\/.vimrc. For my experiences, if enable autochdir option in Vim, users will mess up themselves when trying to provide relative pathes of Vim session and viminfo files. It seems it can't have impact if you provide absolute path for Vim session and viminfo files.\r\n* There is a little compatible problem in some tty console. In some tty console, when launching Vim and this plugin prompt a workspace list for your choice, after you input your choice, it will echo all message one time. Anyway, the function still works.\r\n* You'd better not to run :Loadws in same Vim twice. If you once run Loadws to load your workspace files, then run Loadws to reload them again in the same Vim, it will not close all openning windows and tabs. In other words, you may see double windows have been opened for the same file.\r\n\r\nLicense:\r\nThis software is licensed under the MIT License. Copyright 2014 Brant Chen (Primary: brantchen2008@gmail.com and secondary: xkdcc@163.com).\r\n\r\nFor more details, please access: https:\/\/github.com\/xkdcc\/Session-Viminfo-Management\r\nOr :help workspaceIntro.","install_details":"Download zip ball and copy files to ~\/.vim\/plugin\/session-viminfo-manage.vim and ~\/.vim\/doc\/session-viminfo-manage.txt. Or copy and paste:\r\n\r\ncd ~\/.vim\r\ngit clone https:\/\/github.com\/xkdcc\/Session-Viminfo-Management.git \r\nmv Session-Viminfo-Management\/plugin\/* ~\/.vim\/plugin\/ && mv Session-Viminfo-Management\/doc\/* ~\/.vim\/doc\/\r\nrm -fr Session-Viminfo-Management\/\r\n\r\nNormally to generate documentation, Vim expects you to run :helptags on each directory with documentation (e.g., :helptags ~\/.vim\/doc). ","5":"Download zip ball and copy files to ~\/.vim\/plugin\/session-viminfo-manage.vim and ~\/.vim\/doc\/session-viminfo-manage.txt. Or copy and paste:\r\n\r\ncd ~\/.vim\r\ngit clone https:\/\/github.com\/xkdcc\/Session-Viminfo-Management.git \r\nmv Session-Viminfo-Management\/plugin\/* ~\/.vim\/plugin\/ && mv Session-Viminfo-Management\/doc\/* ~\/.vim\/doc\/\r\nrm -fr Session-Viminfo-Management\/\r\n\r\nNormally to generate documentation, Vim expects you to run :helptags on each directory with documentation (e.g., :helptags ~\/.vim\/doc). ","first_name":"Brant","6":"Brant","last_name":"Chen","7":"Chen","releases":[{"0":"5005","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"Session-Viminfo-Management-1.0-git-042c94fbe8154a52fcfd89234ba7ca6a36f73057.zip","4":"Session-Viminfo-Management-1.0-git-042c94fbe8154a52fcfd89234ba7ca6a36f73057.zip","src_id":"22339","5":"22339","creation_date":"1408266431","6":"1408266431"}]},"5004":{"script_id":"5004","0":"5004","script_name":"vim-rubygems","1":"vim-rubygems","script_type":"utility","2":"utility","summary":"The plugin provides ability to work with rubygems.org inside Vim","3":"The plugin provides ability to work with rubygems.org inside Vim","description":"The vim-rubygems plugin provides ability to work with rubygems.org inside Vim.\r\nCurrenty the following features are provided by the plugin:\r\n- general information for selected gem (version, authors, summary, built date, downloads, description)\r\n- versions list for selected gem (version, built date)\r\n- last version for selected gem (version, built date)\r\n- append a version for a gem under cursor\r\n\r\nMore information on development page:\r\nhttps:\/\/github.com\/alexbel\/vim-rubygems","4":"The vim-rubygems plugin provides ability to work with rubygems.org inside Vim.\r\nCurrenty the following features are provided by the plugin:\r\n- general information for selected gem (version, authors, summary, built date, downloads, description)\r\n- versions list for selected gem (version, built date)\r\n- last version for selected gem (version, built date)\r\n- append a version for a gem under cursor\r\n\r\nMore information on development page:\r\nhttps:\/\/github.com\/alexbel\/vim-rubygems","install_details":"The plugin is compatible with Vundle\/Pathogen. \r\nExample for Vundle:\r\nBundle 'alexbel\/vim-rubygems'","5":"The plugin is compatible with Vundle\/Pathogen. \r\nExample for Vundle:\r\nBundle 'alexbel\/vim-rubygems'","first_name":"Alexander","6":"Alexander","last_name":"Belyaev","7":"Belyaev","releases":[{"0":"5004","vim_version":"7.3","1":"7.3","script_version":"0.0.2","2":"0.0.2","version_comment":"- Add active gems search\r\n- Add checking for outdated gems in Gemfile","3":"- Add active gems search\r\n- Add checking for outdated gems in Gemfile","package":"vim-rubygems.zip","4":"vim-rubygems.zip","src_id":"22541","5":"22541","creation_date":"1413682198","6":"1413682198"},{"0":"5004","vim_version":"7.3","1":"7.3","script_version":"0.0.1","2":"0.0.1","version_comment":"Initial upload","3":"Initial upload","package":"vim-rubygems.zip","4":"vim-rubygems.zip","src_id":"22335","5":"22335","creation_date":"1408179142","6":"1408179142"}]},"5003":{"script_id":"5003","0":"5003","script_name":"Dutyl","1":"Dutyl","script_type":"ftplugin","2":"ftplugin","summary":"Coordinate D tools to work together for you","3":"Coordinate D tools to work together for you","description":"GitHub repository: https:\/\/github.com\/idanarye\/vim-dutyl\r\n\r\nDutyl operates various Dlang tools to help you program D in Vim. Instead of having a separate plugin for each tool, Dutyl can use multiple plugins and use them together - for example, use DUB to get a list of import paths the project is using and pass that list to DCD to get autocompleting for symbols that come from libraries. Dutyl has a module(\/plugin) system that allows tools to back up each other - so for example if a project doesn\\'t use DUB, Dutyl can back up reading the import paths from a static configuration file.","4":"GitHub repository: https:\/\/github.com\/idanarye\/vim-dutyl\r\n\r\nDutyl operates various Dlang tools to help you program D in Vim. Instead of having a separate plugin for each tool, Dutyl can use multiple plugins and use them together - for example, use DUB to get a list of import paths the project is using and pass that list to DCD to get autocompleting for symbols that come from libraries. Dutyl has a module(\/plugin) system that allows tools to back up each other - so for example if a project doesn\\'t use DUB, Dutyl can back up reading the import paths from a static configuration file.","install_details":"","5":"","first_name":"Idan","6":"Idan","last_name":"Arye","7":"Arye","releases":[{"0":"5003","vim_version":"7.0","1":"7.0","script_version":"1.6.0","2":"1.6.0","version_comment":"* add signature to :DUddoc\r\n* Allow disabling format and indent with dfmt\r\n* When dub fails, still get the import path in g:dutyl_stdImportPaths\r\n* Remove dub warnings\r\n* echoerr unparsable dscanner output lines\r\n* Fix a bug with tools that use default executable\r\n* Fix sending input to vimproc#system\r\n* Allow registering complex commands for running tools\r\n","3":"* add signature to :DUddoc\r\n* Allow disabling format and indent with dfmt\r\n* When dub fails, still get the import path in g:dutyl_stdImportPaths\r\n* Remove dub warnings\r\n* echoerr unparsable dscanner output lines\r\n* Fix a bug with tools that use default executable\r\n* Fix sending input to vimproc#system\r\n* Allow registering complex commands for running tools\r\n","package":"dutyl_v1.6.0.zip","4":"dutyl_v1.6.0.zip","src_id":"24723","5":"24723","creation_date":"1478875889","6":"1478875889"},{"0":"5003","vim_version":"7.0","1":"7.0","script_version":"1.5.3","2":"1.5.3","version_comment":"Bugfixes regarding running dcd-server in Linux","3":"Bugfixes regarding running dcd-server in Linux","package":"dutyl_v1.5.3.zip","4":"dutyl_v1.5.3.zip","src_id":"23737","5":"23737","creation_date":"1447702239","6":"1447702239"},{"0":"5003","vim_version":"7.0","1":"7.0","script_version":"1.5.0","2":"1.5.0","version_comment":"Format and indent with dfmt","3":"Format and indent with dfmt","package":"dutyl_v1.5.0.zip","4":"dutyl_v1.5.0.zip","src_id":"23222","5":"23222","creation_date":"1429814714","6":"1429814714"},{"0":"5003","vim_version":"7.0","1":"7.0","script_version":"1.4.3","2":"1.4.3","version_comment":"Cache import paths queried from DUB","3":"Cache import paths queried from DUB","package":"dutyl_v1.4.3.zip","4":"dutyl_v1.4.3.zip","src_id":"22753","5":"22753","creation_date":"1420330354","6":"1420330354"},{"0":"5003","vim_version":"7.0","1":"7.0","script_version":"1.4.2","2":"1.4.2","version_comment":" * Improve UI for declarations locations with huge lists\r\n * Make configFile's importPaths use project root for resolving full paths\r\n * Add required DCD version to docs","3":" * Improve UI for declarations locations with huge lists\r\n * Make configFile's importPaths use project root for resolving full paths\r\n * Add required DCD version to docs","package":"dutyl_v1.4.2.zip","4":"dutyl_v1.4.2.zip","src_id":"22534","5":"22534","creation_date":"1413567698","6":"1413567698"},{"0":"5003","vim_version":"7.0","1":"7.0","script_version":"1.4.1","2":"1.4.1","version_comment":"Fix Issue 6 - Jumping to a buffer that's open in another window ","3":"Fix Issue 6 - Jumping to a buffer that's open in another window ","package":"dutyl_v1.4.1.zip","4":"dutyl_v1.4.1.zip","src_id":"22495","5":"22495","creation_date":"1412718449","6":"1412718449"},{"0":"5003","vim_version":"7.0","1":"7.0","script_version":"1.4.0","2":"1.4.0","version_comment":" * Support using DCD's `--search` flag.\r\n * Add the DUDCDrestartServer and DUDCDclearCache commands\r\n * Recognize the project's root and run commands there","3":" * Support using DCD's `--search` flag.\r\n * Add the DUDCDrestartServer and DUDCDclearCache commands\r\n * Recognize the project's root and run commands there","package":"dutyl_v1.4.0.zip","4":"dutyl_v1.4.0.zip","src_id":"22488","5":"22488","creation_date":"1412446918","6":"1412446918"},{"0":"5003","vim_version":"7.0","1":"7.0","script_version":"1.3.1","2":"1.3.1","version_comment":"Fixed swapfile error on Windows","3":"Fixed swapfile error on Windows","package":"dutyl_v1.3.1.zip","4":"dutyl_v1.3.1.zip","src_id":"22441","5":"22441","creation_date":"1411126176","6":"1411126176"},{"0":"5003","vim_version":"7.0","1":"7.0","script_version":"1.3.0","2":"1.3.0","version_comment":"* Add the `:DUupdateCTags` command for updating the tags file(with Dscanner)\r\n* Make `:DJump` and friends push to the tag stack\r\n* Fix an off by one mistake with byte position calculation","3":"* Add the `:DUupdateCTags` command for updating the tags file(with Dscanner)\r\n* Make `:DJump` and friends push to the tag stack\r\n* Fix an off by one mistake with byte position calculation","package":"dutyl_v1.3.0.zip","4":"dutyl_v1.3.0.zip","src_id":"22429","5":"22429","creation_date":"1410813503","6":"1410813503"},{"0":"5003","vim_version":"7.0","1":"7.0","script_version":"1.2.1","2":"1.2.1","version_comment":"Remove dependency on `uniq` ","3":"Remove dependency on `uniq` ","package":"dutyl_v1.2.1.zip","4":"dutyl_v1.2.1.zip","src_id":"22427","5":"22427","creation_date":"1410730119","6":"1410730119"},{"0":"5003","vim_version":"7.0","1":"7.0","script_version":"1.2.0","2":"1.2.0","version_comment":"* Add :DUsjump, :DUsjump and bang option to ignore context\r\n* Add syntax and style checks using Dscanner","3":"* Add :DUsjump, :DUsjump and bang option to ignore context\r\n* Add syntax and style checks using Dscanner","package":"dutyl_v1.2.0.zip","4":"dutyl_v1.2.0.zip","src_id":"22418","5":"22418","creation_date":"1410621346","6":"1410621346"},{"0":"5003","vim_version":"7.0","1":"7.0","script_version":"1.1.0","2":"1.1.0","version_comment":"* Add DUjump command for jumping to declarations\r\n* Add Dscanner as an option for finding declarations\r\n* (bugfix) Automatically glob and expand the import paths","3":"* Add DUjump command for jumping to declarations\r\n* Add Dscanner as an option for finding declarations\r\n* (bugfix) Automatically glob and expand the import paths","package":"dutyl_v1.1.0.zip","4":"dutyl_v1.1.0.zip","src_id":"22404","5":"22404","creation_date":"1409771388","6":"1409771388"},{"0":"5003","vim_version":"7.0","1":"7.0","script_version":"1.0.1","2":"1.0.1","version_comment":"- Add instructions for using with plugin managers.\r\n- Fix the command line string formatting problems.\r\n- Make dutyl#core#bytePosition always use unix file format.\r\n- Fix usage for Windows without VimProc.\r\n- Support both dub.json and package.json as the DUB file.\r\n- Change the DCD server control functions to use call instead of echo.\r\n- Use DUB's --annotate flag to prevent downloading dependencies.\r\n- Register import paths immediately when starting the DCD server.\r\n- Clean import paths from last character if it's a path separator.","3":"- Add instructions for using with plugin managers.\r\n- Fix the command line string formatting problems.\r\n- Make dutyl#core#bytePosition always use unix file format.\r\n- Fix usage for Windows without VimProc.\r\n- Support both dub.json and package.json as the DUB file.\r\n- Change the DCD server control functions to use call instead of echo.\r\n- Use DUB's --annotate flag to prevent downloading dependencies.\r\n- Register import paths immediately when starting the DCD server.\r\n- Clean import paths from last character if it's a path separator.","package":"dutyl_v1.0.1.zip","4":"dutyl_v1.0.1.zip","src_id":"22350","5":"22350","creation_date":"1408474788","6":"1408474788"},{"0":"5003","vim_version":"7.0","1":"7.0","script_version":"1.0.0","2":"1.0.0","version_comment":"* Getting the imports list from DUB or from a configuration file\r\n* Autocompletion using DCD\r\n* Finding DDoc using DCD","3":"* Getting the imports list from DUB or from a configuration file\r\n* Autocompletion using DCD\r\n* Finding DDoc using DCD","package":"dutyl_v1.0.0.zip","4":"dutyl_v1.0.0.zip","src_id":"22327","5":"22327","creation_date":"1408057145","6":"1408057145"}]},"5002":{"script_id":"5002","0":"5002","script_name":"vim-autoprefixer","1":"vim-autoprefixer","script_type":"utility","2":"utility","summary":"Adds CSS autoprefixer support to Vim.","3":"Adds CSS autoprefixer support to Vim.","description":"With vim-autoprefixer you can use the power of Autoprefixer (https:\/\/github.com\/ai\/autoprefixer) without leaving vim. Write your CSS and add vendor prefixes automatically using values from Can I Use (http:\/\/caniuse.com\/). Autoprefixer utilizes the most recent data from Can I Use to add only necessary vendor prefixes. It also removes old, unnecessary prefixes from your CSS.\r\n\r\nvim-autoprefixer plugin works in normal and visual vim mode. Select a block of CSS code in visual mode hit F7 and aply prefixes on it, in normal mode the plugin processes the entire file.\r\n\r\nNote that vim-autoprefixer interact with the user and promt for Autoprefixer options, if you don\u00e2\u0080\u0099t set any option and hit Enter vim-aytoprefixer continue with Autoprefixer default settings.","4":"With vim-autoprefixer you can use the power of Autoprefixer (https:\/\/github.com\/ai\/autoprefixer) without leaving vim. Write your CSS and add vendor prefixes automatically using values from Can I Use (http:\/\/caniuse.com\/). Autoprefixer utilizes the most recent data from Can I Use to add only necessary vendor prefixes. It also removes old, unnecessary prefixes from your CSS.\r\n\r\nvim-autoprefixer plugin works in normal and visual vim mode. Select a block of CSS code in visual mode hit F7 and aply prefixes on it, in normal mode the plugin processes the entire file.\r\n\r\nNote that vim-autoprefixer interact with the user and promt for Autoprefixer options, if you don\u00e2\u0080\u0099t set any option and hit Enter vim-aytoprefixer continue with Autoprefixer default settings.","install_details":"vim-autoprefixer requires Node.js>=0.12.0 and Postcss plugin Autoprefixer-cli installed on your system. \r\nInstall and test autoprefixer-cli to make sure it's running properly.\r\n\r\nnpm install --global postcss-cli autoprefixer\r\npostcss --use autoprefixer *.css -d build\/\r\n\r\nInstall vim-autoprefixer.\r\nYou can install the plugin manually, just extract the zip file and place the content files in your .vim subfolders.\r\n\r\nPlace in ~\/.vim\/plugin\/vim-autoprefixer.vim\r\nand in ~\/.vim\/doc\/vim-autoprefixer.txt\r\nOr you can install it with Vundle or Pathogen\r\n\r\nmore on GitHub:https:\/\/github.com\/Ioannis-Kapoulas\/vim-autoprefixer","5":"vim-autoprefixer requires Node.js>=0.12.0 and Postcss plugin Autoprefixer-cli installed on your system. \r\nInstall and test autoprefixer-cli to make sure it's running properly.\r\n\r\nnpm install --global postcss-cli autoprefixer\r\npostcss --use autoprefixer *.css -d build\/\r\n\r\nInstall vim-autoprefixer.\r\nYou can install the plugin manually, just extract the zip file and place the content files in your .vim subfolders.\r\n\r\nPlace in ~\/.vim\/plugin\/vim-autoprefixer.vim\r\nand in ~\/.vim\/doc\/vim-autoprefixer.txt\r\nOr you can install it with Vundle or Pathogen\r\n\r\nmore on GitHub:https:\/\/github.com\/Ioannis-Kapoulas\/vim-autoprefixer","first_name":"Ioannis","6":"Ioannis","last_name":"Kapoulas","7":"Kapoulas","releases":[{"0":"5002","vim_version":"7.0","1":"7.0","script_version":"2.0.0","2":"2.0.0","version_comment":"vim-autoprefixer now works with postcss-cli","3":"vim-autoprefixer now works with postcss-cli","package":"vim-autoprefixer-master.zip","4":"vim-autoprefixer-master.zip","src_id":"24101","5":"24101","creation_date":"1457897840","6":"1457897840"}]},"5001":{"script_id":"5001","0":"5001","script_name":"logstash.vim","1":"logstash.vim","script_type":"syntax","2":"syntax","summary":"logstash.vim highlights configuration files for logstash (see http:\/\/logstash.ne","3":"logstash.vim highlights configuration files for logstash (see http:\/\/logstash.ne","description":"logstash.vim highlights configuration files for logstash, a tool for managing events and logs (see http:\/\/logstash.net)\r\n\r\nThis script also includes custom filetype detection for logstash files, since they end with a generic extension. For it to take effect automatically, your configuration file must end with \".conf\" and the first line must look like \"input {\".","4":"logstash.vim highlights configuration files for logstash, a tool for managing events and logs (see http:\/\/logstash.net)\r\n\r\nThis script also includes custom filetype detection for logstash files, since they end with a generic extension. For it to take effect automatically, your configuration file must end with \".conf\" and the first line must look like \"input {\".","install_details":"Download syntax\/logstash.vim to ~\/.vim\/syntax\/ and ftdetect\/logstash.vim to ~\/.vim\/ftdetect.","5":"Download syntax\/logstash.vim to ~\/.vim\/syntax\/ and ftdetect\/logstash.vim to ~\/.vim\/ftdetect.","first_name":"Rob","6":"Rob","last_name":"O'Dwyer","7":"O'Dwyer","releases":[{"0":"5001","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"logstash.vim.zip","4":"logstash.vim.zip","src_id":"22309","5":"22309","creation_date":"1407543338","6":"1407543338"}]},"5000":{"script_id":"5000","0":"5000","script_name":"clickable.vim","1":"clickable.vim","script_type":"utility","2":"utility","summary":" make things clickable","3":" make things clickable","description":"Make things clickable, even in vim.\r\n\r\ndefault ones are urls and files , and you can define your own clickable things. \r\n\r\nfor example, with additional bundles installed(https:\/\/github.com\/Rykka\/clickable-things),\r\nclicking the 'Bundle \"xxx\/yyy\"' will jump to the '~\/.vim\/bundle\/yyy' directory directly.\r\n\r\n.. image :: http:\/\/i.imgur.com\/9T91tLb.gif\r\n\r\nSee details in github: https:\/\/github.com\/Rykka\/clickable.vim\r\n","4":"Make things clickable, even in vim.\r\n\r\ndefault ones are urls and files , and you can define your own clickable things. \r\n\r\nfor example, with additional bundles installed(https:\/\/github.com\/Rykka\/clickable-things),\r\nclicking the 'Bundle \"xxx\/yyy\"' will jump to the '~\/.vim\/bundle\/yyy' directory directly.\r\n\r\n.. image :: http:\/\/i.imgur.com\/9T91tLb.gif\r\n\r\nSee details in github: https:\/\/github.com\/Rykka\/clickable.vim\r\n","install_details":"Extract to you .vim folder (this zip does not include additional bundles)\r\n\r\nor    \r\n\r\n    Bundle \"Rykka\/clickable.vim\"\r\n    Bundle \"Rykka\/clickable-things\"\r\n    Bundle \"Rykka\/os.vim\"\r\n","5":"Extract to you .vim folder (this zip does not include additional bundles)\r\n\r\nor    \r\n\r\n    Bundle \"Rykka\/clickable.vim\"\r\n    Bundle \"Rykka\/clickable-things\"\r\n    Bundle \"Rykka\/os.vim\"\r\n","first_name":"Rykka","6":"Rykka","last_name":"f","7":"f","releases":[{"0":"5000","vim_version":"7.0","1":"7.0","script_version":"0.9.1","2":"0.9.1","version_comment":"Rewrited.\r\nNow you can define clickable items.\r\n","3":"Rewrited.\r\nNow you can define clickable items.\r\n","package":"clickable.vim-0.9.1.zip","4":"clickable.vim-0.9.1.zip","src_id":"22571","5":"22571","creation_date":"1414423084","6":"1414423084"},{"0":"5000","vim_version":"7.0","1":"7.0","script_version":"0.6.6","2":"0.6.6","version_comment":"Fix bugs! make it work more quickly~","3":"Fix bugs! make it work more quickly~","package":"clickable.vim-0.6.6.zip","4":"clickable.vim-0.6.6.zip","src_id":"22371","5":"22371","creation_date":"1409183158","6":"1409183158"},{"0":"5000","vim_version":"7.0","1":"7.0","script_version":"0.65","2":"0.65","version_comment":"bug fix and misc feature added","3":"bug fix and misc feature added","package":"clickable.vim-0.65.zip","4":"clickable.vim-0.65.zip","src_id":"22302","5":"22302","creation_date":"1407391959","6":"1407391959"},{"0":"5000","vim_version":"7.0","1":"7.0","script_version":"0.6","2":"0.6","version_comment":"feature implemented","3":"feature implemented","package":"clickable.vim-master.zip","4":"clickable.vim-master.zip","src_id":"22300","5":"22300","creation_date":"1407389376","6":"1407389376"},{"0":"5000","vim_version":"7.0","1":"7.0","script_version":"0.01","2":"0.01","version_comment":"Initial upload","3":"Initial upload","package":"clickable.vim-master.zip","4":"clickable.vim-master.zip","src_id":"22298","5":"22298","creation_date":"1407360345","6":"1407360345"}]},"4999":{"script_id":"4999","0":"4999","script_name":"InstantRst","1":"InstantRst","script_type":"utility","2":"utility","summary":"Preview rst document instantly.","3":"Preview rst document instantly.","description":"A vim plugin for preview rst document instantly.\r\n\r\ngithub: https:\/\/github.com\/Rykka\/InstantRst\r\n\r\n.. figure:: https:\/\/github.com\/Rykka\/github_things\/raw\/master\/image\/rst_quick_start.gif \r\n\r\nThis is an intro for vim usage.\r\nTo use the server, see instant-rst.py_.\r\n\r\n.. _instant-rst.py: https:\/\/github.com\/rykka\/instant-rst.py\r\n","4":"A vim plugin for preview rst document instantly.\r\n\r\ngithub: https:\/\/github.com\/Rykka\/InstantRst\r\n\r\n.. figure:: https:\/\/github.com\/Rykka\/github_things\/raw\/master\/image\/rst_quick_start.gif \r\n\r\nThis is an intro for vim usage.\r\nTo use the server, see instant-rst.py_.\r\n\r\n.. _instant-rst.py: https:\/\/github.com\/rykka\/instant-rst.py\r\n","install_details":"1. Vim with Vundle or NeoBundle:\r\n\r\n   ``NeoBundle 'Rykka\/InstantRst'``\r\n\r\n2. Python:\r\n\r\n.. code:: sh\r\n\r\n   # Got some issue on pypi\r\n   # sudo pip install instant-rst\r\n   sudo pip install https:\/\/github.com\/Rykka\/instant-rst.py\/archive\/master.zip\r\n\r\n3. Curl:\r\n\r\n.. code:: sh\r\n\r\n   sudo apt-get install curl\r\n","5":"1. Vim with Vundle or NeoBundle:\r\n\r\n   ``NeoBundle 'Rykka\/InstantRst'``\r\n\r\n2. Python:\r\n\r\n.. code:: sh\r\n\r\n   # Got some issue on pypi\r\n   # sudo pip install instant-rst\r\n   sudo pip install https:\/\/github.com\/Rykka\/instant-rst.py\/archive\/master.zip\r\n\r\n3. Curl:\r\n\r\n.. code:: sh\r\n\r\n   sudo apt-get install curl\r\n","first_name":"Rykka","6":"Rykka","last_name":"f","7":"f","releases":[{"0":"4999","vim_version":"7.0","1":"7.0","script_version":"0.97","2":"0.97","version_comment":"Using python package.\r\nAdd scroll-binding,init-view and themes.\r\nWorks like a charm!\r\n","3":"Using python package.\r\nAdd scroll-binding,init-view and themes.\r\nWorks like a charm!\r\n","package":"InstantRst-0.9.7.zip","4":"InstantRst-0.9.7.zip","src_id":"22370","5":"22370","creation_date":"1409182208","6":"1409182208"},{"0":"4999","vim_version":"7.0","1":"7.0","script_version":"0.6","2":"0.6","version_comment":"Initial upload","3":"Initial upload","package":"InstantRst-master.zip","4":"InstantRst-master.zip","src_id":"22297","5":"22297","creation_date":"1407359214","6":"1407359214"}]},"4998":{"script_id":"4998","0":"4998","script_name":"doctest.vim","1":"doctest.vim","script_type":"utility","2":"utility","summary":"  DocTest in vim","3":"  DocTest in vim","description":"Besides TDD & BDD , What about DDD (Doc Driven Dev) :)\r\n\r\nThis is a plugin for doctest vim scripts.\r\n\r\nsee https:\/\/github.com\/Rykka\/doctest.vim","4":"Besides TDD & BDD , What about DDD (Doc Driven Dev) :)\r\n\r\nThis is a plugin for doctest vim scripts.\r\n\r\nsee https:\/\/github.com\/Rykka\/doctest.vim","install_details":"extracts to your .vim folder","5":"extracts to your .vim folder","first_name":"Rykka","6":"Rykka","last_name":"f","7":"f","releases":[{"0":"4998","vim_version":"7.0","1":"7.0","script_version":"0.95","2":"0.95","version_comment":"Add timing and s:var support\r\nFix bugs","3":"Add timing and s:var support\r\nFix bugs","package":"doctest.vim-0.95.zip","4":"doctest.vim-0.95.zip","src_id":"22301","5":"22301","creation_date":"1407390362","6":"1407390362"},{"0":"4998","vim_version":"7.0","1":"7.0","script_version":"0.9","2":"0.9","version_comment":"Initial upload","3":"Initial upload","package":"doctest.vim-master.zip","4":"doctest.vim-master.zip","src_id":"22295","5":"22295","creation_date":"1407357380","6":"1407357380"}]},"4997":{"script_id":"4997","0":"4997","script_name":"SearchInRange","1":"SearchInRange","script_type":"utility","2":"utility","summary":"Limit search to range when jumping to the next search result.","3":"Limit search to range when jumping to the next search result.","description":"DESCRIPTION\r\nVim can limit the scope of searches to the remainder of the buffer with the\r\n'wrapscan' option, but it cannot limit searches to a particular range, other\r\nthan by including special regular expression atoms like \/\\%l. It's not easy\r\nto restrict a search to the current function, or next 100 lines, even though\r\nsuch is often useful to avoid getting lost in the buffer.\r\n\r\nThis plugin provides custom search motions, similar to the built-in n \/ N,\r\nwhich only move to matches of the current search pattern that fall within a\r\ncertain range that has been specified through the :SearchInRange command, or\r\nan equivalent mapping.\r\n\r\nSEE ALSO\r\n- Check out the SearchRepeat.vim plugin page (vimscript #4949) for a full\r\n  list of custom searches that integrate with it.\r\n\r\nRELATED WORKS\r\n- range-search (vimscript #1396) defines a :R command.\r\n- vis.vim (vimscript #1195) defines a :S command and \/\/ and ?? mappings. It\r\n  works by modifying the search pattern to add restrictions for lines and\r\n  columns.\r\n\r\nUSAGE\r\n:[range]SearchInRange   Search forward to the first occurrence of the current\r\n                        search pattern inside [range]. Limit search to lines\r\n                        inside [range] when jumping to the next search result.\r\n:[range]SearchInRange [\/]{pattern}[\/]\r\n                        Search for {pattern}, starting with the first occurrence\r\n                        inside [range]. Limit search to lines inside [range]\r\n                        when jumping to the next search result. Without [\/],\r\n                        only literal whole words are matched. :search-args\r\n\r\n:[range]SearchInRangeInclude [range]\r\n                        Add [range] \/ the current line to the list of ranges\r\n                        that are searched. If you pass the [range] after the\r\n                        command, it is re-evaluated on each search; i.e. you\r\n                        can for example pass marks ('a,'b), and the resulting\r\n                        lines will be reevaluated, adapting to changes in the\r\n                        buffer.\r\n\r\n:[range]SearchInRangeExclude [range]\r\n                        Remove [range] \/ the current line from the list of\r\n                        ranges that are searched. If you pass the [range]\r\n                        after the command, it is re-evaluated on each search.\r\n\r\n:SearchInRangeClear     Reset the search by clearing all ranges. You need to\r\n                        specify a new one to use this search again. This\r\n                        command is useful to e.g. search in all lines matching\r\n                        \"foo\":\r\n                            :SearchInRangeClear | global\/foo\/SearchInRangeInclude\r\n                       or with dynamic ranges: >\r\n                            :SearchInRangeClear | SearchInRangeInclude \/foo\/\r\n\r\n{Visual}n       Jump to the first occurrence of the last search\r\n                        pattern inside the current selection. Limit search to\r\n                        lines inside selection when jumping to the next search\r\n                        result.\r\n\r\nn{motion}       Use the moved-over lines as a range to limit searches\r\n                        to. Jump to first occurrence of the last search\r\n                        pattern inside the range.\r\n\r\nThe special searches all start with 'go...' (mnemonic: \"go once to special\r\nmatch\"); and come in search forward (go...) and backward (gO...) variants.\r\n\r\n[count]gor \/ gOr        Search forward \/ backward to the [count]'th occurrence\r\n                        of the last search pattern in the previously specified\r\n                        range.","4":"DESCRIPTION\r\nVim can limit the scope of searches to the remainder of the buffer with the\r\n'wrapscan' option, but it cannot limit searches to a particular range, other\r\nthan by including special regular expression atoms like \/\\%l. It's not easy\r\nto restrict a search to the current function, or next 100 lines, even though\r\nsuch is often useful to avoid getting lost in the buffer.\r\n\r\nThis plugin provides custom search motions, similar to the built-in n \/ N,\r\nwhich only move to matches of the current search pattern that fall within a\r\ncertain range that has been specified through the :SearchInRange command, or\r\nan equivalent mapping.\r\n\r\nSEE ALSO\r\n- Check out the SearchRepeat.vim plugin page (vimscript #4949) for a full\r\n  list of custom searches that integrate with it.\r\n\r\nRELATED WORKS\r\n- range-search (vimscript #1396) defines a :R command.\r\n- vis.vim (vimscript #1195) defines a :S command and \/\/ and ?? mappings. It\r\n  works by modifying the search pattern to add restrictions for lines and\r\n  columns.\r\n\r\nUSAGE\r\n:[range]SearchInRange   Search forward to the first occurrence of the current\r\n                        search pattern inside [range]. Limit search to lines\r\n                        inside [range] when jumping to the next search result.\r\n:[range]SearchInRange [\/]{pattern}[\/]\r\n                        Search for {pattern}, starting with the first occurrence\r\n                        inside [range]. Limit search to lines inside [range]\r\n                        when jumping to the next search result. Without [\/],\r\n                        only literal whole words are matched. :search-args\r\n\r\n:[range]SearchInRangeInclude [range]\r\n                        Add [range] \/ the current line to the list of ranges\r\n                        that are searched. If you pass the [range] after the\r\n                        command, it is re-evaluated on each search; i.e. you\r\n                        can for example pass marks ('a,'b), and the resulting\r\n                        lines will be reevaluated, adapting to changes in the\r\n                        buffer.\r\n\r\n:[range]SearchInRangeExclude [range]\r\n                        Remove [range] \/ the current line from the list of\r\n                        ranges that are searched. If you pass the [range]\r\n                        after the command, it is re-evaluated on each search.\r\n\r\n:SearchInRangeClear     Reset the search by clearing all ranges. You need to\r\n                        specify a new one to use this search again. This\r\n                        command is useful to e.g. search in all lines matching\r\n                        \"foo\":\r\n                            :SearchInRangeClear | global\/foo\/SearchInRangeInclude\r\n                       or with dynamic ranges: >\r\n                            :SearchInRangeClear | SearchInRangeInclude \/foo\/\r\n\r\n{Visual}n       Jump to the first occurrence of the last search\r\n                        pattern inside the current selection. Limit search to\r\n                        lines inside selection when jumping to the next search\r\n                        result.\r\n\r\nn{motion}       Use the moved-over lines as a range to limit searches\r\n                        to. Jump to first occurrence of the last search\r\n                        pattern inside the range.\r\n\r\nThe special searches all start with 'go...' (mnemonic: \"go once to special\r\nmatch\"); and come in search forward (go...) and backward (gO...) variants.\r\n\r\n[count]gor \/ gOr        Search forward \/ backward to the [count]'th occurrence\r\n                        of the last search pattern in the previously specified\r\n                        range.","install_details":"INSTALLATION\r\nThe code is hosted in a Git repo at\r\n    https:\/\/github.com\/inkarkat\/vim-SearchInRange\r\nYou can use your favorite plugin manager, or \"git clone\" into a directory used\r\nfor Vim packages. Releases are on the \"stable\" branch, the latest unstable\r\ndevelopment snapshot on \"master\".\r\n\r\nThis script is also packaged as a vimball. If you have the \"gunzip\"\r\ndecompressor in your PATH, simply edit the *.vmb.gz package in Vim; otherwise,\r\ndecompress the archive first, e.g. using WinZip. Inside Vim, install by\r\nsourcing the vimball or via the :UseVimball command.\r\n    vim SearchInRange*.vmb.gz\r\n    :so %\r\nTo uninstall, use the :RmVimball command.\r\n\r\nDEPENDENCIES\r\n- Requires Vim 7.0 or higher.\r\n- Requires the ingo-library.vim plugin (vimscript #4433), version 1.022 or\r\n  higher.\r\n- SearchRepeat.vim (vimscript #4949) plugin, version 2.00 or higher (optional)\r\n\r\nCONFIGURATION\r\nFor a permanent configuration, put the following commands into your vimrc:\r\n\r\nIf you want to use different mappings, map your keys to the\r\n(SearchInRange...) mapping targets _before_ sourcing the script\r\n(e.g. in your vimrc):\r\n    xmap n (SearchInRange)\r\n    nmap n (SearchInRangeOperator)\r\n    nmap gor (SearchInRangeNext)\r\n    nmap gOr (SearchInRangePrev)\r\n\r\nINTEGRATION\r\nIf the SearchRepeat plugin is installed, a parallel set of \"go now and for\r\nnext searches\" mappings (starting with 'gn...' instead of 'go...') is\r\ninstalled. These mappings have the same effect, but in addition re-program the\r\n'n\/N' keys to repeat this particular search (until another gn... search is\r\nused).","5":"INSTALLATION\r\nThe code is hosted in a Git repo at\r\n    https:\/\/github.com\/inkarkat\/vim-SearchInRange\r\nYou can use your favorite plugin manager, or \"git clone\" into a directory used\r\nfor Vim packages. Releases are on the \"stable\" branch, the latest unstable\r\ndevelopment snapshot on \"master\".\r\n\r\nThis script is also packaged as a vimball. If you have the \"gunzip\"\r\ndecompressor in your PATH, simply edit the *.vmb.gz package in Vim; otherwise,\r\ndecompress the archive first, e.g. using WinZip. Inside Vim, install by\r\nsourcing the vimball or via the :UseVimball command.\r\n    vim SearchInRange*.vmb.gz\r\n    :so %\r\nTo uninstall, use the :RmVimball command.\r\n\r\nDEPENDENCIES\r\n- Requires Vim 7.0 or higher.\r\n- Requires the ingo-library.vim plugin (vimscript #4433), version 1.022 or\r\n  higher.\r\n- SearchRepeat.vim (vimscript #4949) plugin, version 2.00 or higher (optional)\r\n\r\nCONFIGURATION\r\nFor a permanent configuration, put the following commands into your vimrc:\r\n\r\nIf you want to use different mappings, map your keys to the\r\n(SearchInRange...) mapping targets _before_ sourcing the script\r\n(e.g. in your vimrc):\r\n    xmap n (SearchInRange)\r\n    nmap n (SearchInRangeOperator)\r\n    nmap gor (SearchInRangeNext)\r\n    nmap gOr (SearchInRangePrev)\r\n\r\nINTEGRATION\r\nIf the SearchRepeat plugin is installed, a parallel set of \"go now and for\r\nnext searches\" mappings (starting with 'gn...' instead of 'go...') is\r\ninstalled. These mappings have the same effect, but in addition re-program the\r\n'n\/N' keys to repeat this particular search (until another gn... search is\r\nused).","first_name":"Ingo","6":"Ingo","last_name":"Karkat","7":"Karkat","releases":[{"0":"4997","vim_version":"7.0","1":"7.0","script_version":"2.00","2":"2.00","version_comment":"- Add SearchInRangeInclude, SearchInRangeExclude, SearchInRangeClear commands. These allow dynamic ranges that get re-interpreted on each search.\r\n- Implement skipping over gaps between individual ranges.\r\n- Also add {pattern} to the search history.","3":"- Add SearchInRangeInclude, SearchInRangeExclude, SearchInRangeClear commands. These allow dynamic ranges that get re-interpreted on each search.\r\n- Implement skipping over gaps between individual ranges.\r\n- Also add {pattern} to the search history.","package":"SearchInRange-2.00.vmb.gz","4":"SearchInRange-2.00.vmb.gz","src_id":"25701","5":"25701","creation_date":"1512763531","6":"1512763531"},{"0":"4997","vim_version":"7.0","1":"7.0","script_version":"1.01","2":"1.01","version_comment":"- FIX: Need to explicitly account for closed folds in the range passed to SearchInRange#SetAndSearchInRange().\r\n- FIX: When moving to start \/ end of range, must use \"c\" search flag to avoid skipping a match directly at the border.\r\n- FIX: After moving outside the range, also need to use \"c\" search flag.\r\n- FIX: Correct default mappings in documentation. *** You need to update to ingo-library (vimscript #4433) version 1.022! *** ","3":"- FIX: Need to explicitly account for closed folds in the range passed to SearchInRange#SetAndSearchInRange().\r\n- FIX: When moving to start \/ end of range, must use \"c\" search flag to avoid skipping a match directly at the border.\r\n- FIX: After moving outside the range, also need to use \"c\" search flag.\r\n- FIX: Correct default mappings in documentation. *** You need to update to ingo-library (vimscript #4433) version 1.022! *** ","package":"SearchInRange-1.01.vmb.gz","4":"SearchInRange-1.01.vmb.gz","src_id":"22461","5":"22461","creation_date":"1411723750","6":"1411723750"},{"0":"4997","vim_version":"7.0","1":"7.0","script_version":"1.00","2":"1.00","version_comment":"Initial upload","3":"Initial upload","package":"SearchInRange-1.00.vmb.gz","4":"SearchInRange-1.00.vmb.gz","src_id":"22294","5":"22294","creation_date":"1407352654","6":"1407352654"}]},"4996":{"script_id":"4996","0":"4996","script_name":"AdvancedDiffOptions","1":"AdvancedDiffOptions","script_type":"utility","2":"utility","summary":"Additional diff options and commands to manage them.","3":"Additional diff options and commands to manage them.","description":"DESCRIPTION\r\nVim provides a nice diff-mode; parameters like case- or whitespace-\r\ninsensitivity can be controlled through the 'diffopt' option. However, because\r\nthat option controls both the difference filtering itself as well as the\r\nvisual appearance within Vim, modifying that option on the fly with `:set`\r\nisn't very comfortable.\r\n\r\nThis plugin provides a set of :DiffI... commands that enable you to quickly\r\ntoggle the built-in diff filtering options, and adds advanced options for\r\nfiltering blank lines, complete change hunks, lines, ranges, or patterns of\r\ntext.\r\n\r\nHOW IT WORKS\r\nWhen there's a corresponding command-line option for the \"diff\" tool, this is\r\npassed. The filtering of lines, ranges, and patterns is implemented by\r\npreprocessing the buffers through the external \"sed\" command.\r\n\r\nRELATED WORKS\r\n- spotdiff.vim (vimscript #5509) also selectively diffs parts of two buffers\r\n  by filtering certain lines via a custom 'diffexpr', similar to how\r\n  :DiffIRange works.\r\n\r\nUSAGE\r\n:DiffOptions            List the currently active diff options.\r\n\r\n:DiffAlgorithm          Show the currently active diff algorithm (for the\r\n                        internal diff).\r\n:DiffAlgorithm {algorithm}\r\n                        Set the algorithm for the internal diff to\r\n                        {algorithm}, one of myers, minimal, patience, history;\r\n                        cp. 'diffopt'.\r\n\r\n:DiffIClear             Clear all \"ignore ...\" diff options.\r\n\r\n:DiffIWhiteSpace[!]     Ignore changes in whitespace. [!] for undo.\r\n\r\n:DiffICase[!]           Ignore changes in case. [!] for undo.\r\n\r\n:DiffIWhiteAll[!]       Ignore all white space changes. [!] for undo.\r\n\r\n:DiffIWhiteEol[!]       Ignore white space changes at end of line. [!] for\r\n                        undo.\r\n\r\n:DiffIBlankLines[!]     Ignore changes where lines are all blank. [!] for\r\n                        undo.\r\n\r\n:DiffIHunks[!] [{expr}] Ignore change hunks whose lines _all_ match {expr}.\r\n                        [!] for undo.\r\n\r\n                        The following filters go beyond the capabilities of\r\n                        the diff command itself; they work by preprocessing\r\n                        the compared files before sending them to diff.\r\n\r\n:DiffILines[!] [{expr}] Do not consider any (whole) lines that match {expr} in\r\n                        the diff (like grep). [!] for undo.\r\n\r\n:DiffIRange[!] [{range}]\r\n                        Do not consider any lines that match the lines\r\n                        specified by {range} in the diff. [!] for undo.\r\n                        Note that Vim will still highlight additional lines at\r\n                        the end of the longer buffer.\r\n\r\n:DiffIPattern[!] [{expr}]\r\n                        Do not consider any text that matches {expr} in the\r\n                        diff (globally, not just the first match). Other text\r\n                        around the matches still contributes to the diff, so\r\n                        in contrast to :DiffILines, this lets you\r\n                        selectively ignore parts of a line.\r\n                        [!] for undo, i.e. removing {expr}, or all previously\r\n                        given patterns.\r\n                        Note that if the amount of ignored lines different\r\n                        between files, other (later) lines will be mistakenly\r\n                        highlighted as changed.\r\n                        Note that Vim will still highlight the ignored changes\r\n                        (should there be another change in the line that is\r\n                        not covered by {expr}), because it determines that on\r\n                        its own.\r\n\r\nEXAMPLE\r\nFilter all diff hunks that only consist of comments in a Perl script:\r\n    :DiffIHunks ^#\r\n\r\nIgnore any differences after a line matching \"EOF\":\r\n    :DiffIRange \/^EOF$\/,$\r\n\r\nIgnore type differences of \"char const\" vs. \"char\" in a C program:\r\n    :DiffIPattern [ ]const","4":"DESCRIPTION\r\nVim provides a nice diff-mode; parameters like case- or whitespace-\r\ninsensitivity can be controlled through the 'diffopt' option. However, because\r\nthat option controls both the difference filtering itself as well as the\r\nvisual appearance within Vim, modifying that option on the fly with `:set`\r\nisn't very comfortable.\r\n\r\nThis plugin provides a set of :DiffI... commands that enable you to quickly\r\ntoggle the built-in diff filtering options, and adds advanced options for\r\nfiltering blank lines, complete change hunks, lines, ranges, or patterns of\r\ntext.\r\n\r\nHOW IT WORKS\r\nWhen there's a corresponding command-line option for the \"diff\" tool, this is\r\npassed. The filtering of lines, ranges, and patterns is implemented by\r\npreprocessing the buffers through the external \"sed\" command.\r\n\r\nRELATED WORKS\r\n- spotdiff.vim (vimscript #5509) also selectively diffs parts of two buffers\r\n  by filtering certain lines via a custom 'diffexpr', similar to how\r\n  :DiffIRange works.\r\n\r\nUSAGE\r\n:DiffOptions            List the currently active diff options.\r\n\r\n:DiffAlgorithm          Show the currently active diff algorithm (for the\r\n                        internal diff).\r\n:DiffAlgorithm {algorithm}\r\n                        Set the algorithm for the internal diff to\r\n                        {algorithm}, one of myers, minimal, patience, history;\r\n                        cp. 'diffopt'.\r\n\r\n:DiffIClear             Clear all \"ignore ...\" diff options.\r\n\r\n:DiffIWhiteSpace[!]     Ignore changes in whitespace. [!] for undo.\r\n\r\n:DiffICase[!]           Ignore changes in case. [!] for undo.\r\n\r\n:DiffIWhiteAll[!]       Ignore all white space changes. [!] for undo.\r\n\r\n:DiffIWhiteEol[!]       Ignore white space changes at end of line. [!] for\r\n                        undo.\r\n\r\n:DiffIBlankLines[!]     Ignore changes where lines are all blank. [!] for\r\n                        undo.\r\n\r\n:DiffIHunks[!] [{expr}] Ignore change hunks whose lines _all_ match {expr}.\r\n                        [!] for undo.\r\n\r\n                        The following filters go beyond the capabilities of\r\n                        the diff command itself; they work by preprocessing\r\n                        the compared files before sending them to diff.\r\n\r\n:DiffILines[!] [{expr}] Do not consider any (whole) lines that match {expr} in\r\n                        the diff (like grep). [!] for undo.\r\n\r\n:DiffIRange[!] [{range}]\r\n                        Do not consider any lines that match the lines\r\n                        specified by {range} in the diff. [!] for undo.\r\n                        Note that Vim will still highlight additional lines at\r\n                        the end of the longer buffer.\r\n\r\n:DiffIPattern[!] [{expr}]\r\n                        Do not consider any text that matches {expr} in the\r\n                        diff (globally, not just the first match). Other text\r\n                        around the matches still contributes to the diff, so\r\n                        in contrast to :DiffILines, this lets you\r\n                        selectively ignore parts of a line.\r\n                        [!] for undo, i.e. removing {expr}, or all previously\r\n                        given patterns.\r\n                        Note that if the amount of ignored lines different\r\n                        between files, other (later) lines will be mistakenly\r\n                        highlighted as changed.\r\n                        Note that Vim will still highlight the ignored changes\r\n                        (should there be another change in the line that is\r\n                        not covered by {expr}), because it determines that on\r\n                        its own.\r\n\r\nEXAMPLE\r\nFilter all diff hunks that only consist of comments in a Perl script:\r\n    :DiffIHunks ^#\r\n\r\nIgnore any differences after a line matching \"EOF\":\r\n    :DiffIRange \/^EOF$\/,$\r\n\r\nIgnore type differences of \"char const\" vs. \"char\" in a C program:\r\n    :DiffIPattern [ ]const","install_details":"INSTALLATION\r\nThe code is hosted in a Git repo at\r\n    https:\/\/github.com\/inkarkat\/vim-AdvancedDiffOptions\r\nYou can use your favorite plugin manager, or \"git clone\" into a directory used\r\nfor Vim packages. Releases are on the \"stable\" branch, the latest unstable\r\ndevelopment snapshot on \"master\".\r\n\r\nThis script is also packaged as a vimball. If you have the \"gunzip\"\r\ndecompressor in your PATH, simply edit the *.vmb.gz package in Vim; otherwise,\r\ndecompress the archive first, e.g. using WinZip. Inside Vim, install by\r\nsourcing the vimball or via the :UseVimball command.\r\n    vim AdvancedDiffOptions*.vmb.gz\r\n    :so %\r\nTo uninstall, use the :RmVimball command.\r\n\r\nDEPENDENCIES\r\n- Requires Vim 7.0 or higher.\r\n- Requires the ingo-library.vim plugin (vimscript #4433), version 1.040 or\r\n  higher.\r\n- misc.vim plugin (vimscript #4597), version 1.17 or higher (optional).\r\n- External command \"diff\" or equivalent for listing of differences.\r\n- External command \"sed\" for some advanced filters (optional).\r\n\r\nCONFIGURATION\r\nSome advanced filters require preprocessing of the compared files. The plugin\r\nnow offers several different strategies for this, each with slight differences\r\nin supported syntax. The default is using a separate instance of Vim:\r\n    let g:AdvancedDiffOptions_Strategy = AdvancedDiffOptions#External#Vim\r\nWith that, you can use the familiar syntax for ranges and regular expressions,\r\nbut the processing is the slowest.\r\nIf you have the sed tool on your system, you can use that instead:\r\n    let g:AdvancedDiffOptions_Strategy = AdvancedDiffOptions#External#Sed\r\nThis is faster, but note that the tool uses a different regular expression\r\nsyntax.\r\nThe fastest option is processing of the diff files inside the current Vim\r\ninstance; no external tool launch (other than diff itself) is required. Note\r\nthat this currently only supports a subset of numerical ranges (e.g. 23,42)\r\nand \"$\", and that regular expression are evaluated line by line and cannot\r\nreference other lines. Also, no detection of the file encoding is done.\r\n    let g:AdvancedDiffOptions_Strategy = AdvancedDiffOptions#Internal#Vim","5":"INSTALLATION\r\nThe code is hosted in a Git repo at\r\n    https:\/\/github.com\/inkarkat\/vim-AdvancedDiffOptions\r\nYou can use your favorite plugin manager, or \"git clone\" into a directory used\r\nfor Vim packages. Releases are on the \"stable\" branch, the latest unstable\r\ndevelopment snapshot on \"master\".\r\n\r\nThis script is also packaged as a vimball. If you have the \"gunzip\"\r\ndecompressor in your PATH, simply edit the *.vmb.gz package in Vim; otherwise,\r\ndecompress the archive first, e.g. using WinZip. Inside Vim, install by\r\nsourcing the vimball or via the :UseVimball command.\r\n    vim AdvancedDiffOptions*.vmb.gz\r\n    :so %\r\nTo uninstall, use the :RmVimball command.\r\n\r\nDEPENDENCIES\r\n- Requires Vim 7.0 or higher.\r\n- Requires the ingo-library.vim plugin (vimscript #4433), version 1.040 or\r\n  higher.\r\n- misc.vim plugin (vimscript #4597), version 1.17 or higher (optional).\r\n- External command \"diff\" or equivalent for listing of differences.\r\n- External command \"sed\" for some advanced filters (optional).\r\n\r\nCONFIGURATION\r\nSome advanced filters require preprocessing of the compared files. The plugin\r\nnow offers several different strategies for this, each with slight differences\r\nin supported syntax. The default is using a separate instance of Vim:\r\n    let g:AdvancedDiffOptions_Strategy = AdvancedDiffOptions#External#Vim\r\nWith that, you can use the familiar syntax for ranges and regular expressions,\r\nbut the processing is the slowest.\r\nIf you have the sed tool on your system, you can use that instead:\r\n    let g:AdvancedDiffOptions_Strategy = AdvancedDiffOptions#External#Sed\r\nThis is faster, but note that the tool uses a different regular expression\r\nsyntax.\r\nThe fastest option is processing of the diff files inside the current Vim\r\ninstance; no external tool launch (other than diff itself) is required. Note\r\nthat this currently only supports a subset of numerical ranges (e.g. 23,42)\r\nand \"$\", and that regular expression are evaluated line by line and cannot\r\nreference other lines. Also, no detection of the file encoding is done.\r\n    let g:AdvancedDiffOptions_Strategy = AdvancedDiffOptions#Internal#Vim","first_name":"Ingo","6":"Ingo","last_name":"Karkat","7":"Karkat","releases":[{"0":"4996","vim_version":"7.0","1":"7.0","script_version":"2.10","2":"2.10","version_comment":"- Add :DiffAlgorithm command to query or set the algorithm used by the internal diff.\r\n- Save original 'diffexpr'. Remove \"internal\" from 'diffopt' when setting 'diffexpr'.\r\n- Don't include \"internal\" in AdvancedDiffOptions#GetShortDiffOptions(), as it's more an implementation detail. Same for \"indent-heuristic\" (which also starts with i and is therefore picked up).\r\n- Add :DiffIWhiteAll, :DiffIWhiteEol for the new built-in 'diffopt' values added in Vim 8.1.393. Implement :DiffIBlankLines in terms of the \"iblank\" 'diffopt' value if supported. *** You need to update to ingo-library (vimscript #4433) version 1.040! ***","3":"- Add :DiffAlgorithm command to query or set the algorithm used by the internal diff.\r\n- Save original 'diffexpr'. Remove \"internal\" from 'diffopt' when setting 'diffexpr'.\r\n- Don't include \"internal\" in AdvancedDiffOptions#GetShortDiffOptions(), as it's more an implementation detail. Same for \"indent-heuristic\" (which also starts with i and is therefore picked up).\r\n- Add :DiffIWhiteAll, :DiffIWhiteEol for the new built-in 'diffopt' values added in Vim 8.1.393. Implement :DiffIBlankLines in terms of the \"iblank\" 'diffopt' value if supported. *** You need to update to ingo-library (vimscript #4433) version 1.040! ***","package":"AdvancedDiffOptions-2.10.vmb.gz","4":"AdvancedDiffOptions-2.10.vmb.gz","src_id":"27250","5":"27250","creation_date":"1595819257","6":"1595819257"},{"0":"4996","vim_version":"7.0","1":"7.0","script_version":"2.00","2":"2.00","version_comment":"- Refactor the plugin to handle different strategies to preprocess the compared files (used by some advanced filters).\r\n- Offer preprocessing through an externally launched Vim instance, and internally in the current Vim, in addition to the existing external sed tool. Change the default to external Vim, because that offers the fullest feature set, and no need to switch regular expression dialects as with sed. Thanks to Marcelo Mont\u00c3\u00ba for suggesting this and sending prototype patches for both external and internal Vim processing!\r\n","3":"- Refactor the plugin to handle different strategies to preprocess the compared files (used by some advanced filters).\r\n- Offer preprocessing through an externally launched Vim instance, and internally in the current Vim, in addition to the existing external sed tool. Change the default to external Vim, because that offers the fullest feature set, and no need to switch regular expression dialects as with sed. Thanks to Marcelo Mont\u00c3\u00ba for suggesting this and sending prototype patches for both external and internal Vim processing!\r\n","package":"AdvancedDiffOptions-2.00.vmb.gz","4":"AdvancedDiffOptions-2.00.vmb.gz","src_id":"22456","5":"22456","creation_date":"1411646442","6":"1411646442"},{"0":"4996","vim_version":"7.0","1":"7.0","script_version":"1.00","2":"1.00","version_comment":"Initial upload","3":"Initial upload","package":"AdvancedDiffOptions-1.00.vmb.gz","4":"AdvancedDiffOptions-1.00.vmb.gz","src_id":"22289","5":"22289","creation_date":"1407242905","6":"1407242905"}]},"4995":{"script_id":"4995","0":"4995","script_name":"vCoolor","1":"vCoolor","script_type":"utility","2":"utility","summary":"A Simple color selector\/picker plugin","3":"A Simple color selector\/picker plugin","description":"vCoolor is a Vim plugin that allows using a color picker\/selector directly from the editor.\r\n\r\nWhat this plugin do:\r\n* Insert hex, rgb, rgba (1 in opacity) or hsl color anywhere.\r\n* Modify hex color even if there are many colors in 1 line.\r\n* Modify a rgb color with 0-255 values or % (Only one by line).\r\n* Modify a hsl color (Only one by line).\r\n* Modify a rgba color but don't change opacity (Only one by line).\r\n\r\nWhat this plugin doesn't do:\r\n* Insert or modify hsla colors.\r\n\r\nIn GNU\/Linux it uses a simple GTK+ dialog.\r\nIn windows it uses colorpicker-windows-commandline (https:\/\/github.com\/jaxbot\/colorpicker-windows-commandline) (The binary is included in the plugin).\r\nIn MAC OS it uses a ruby script (https:\/\/github.com\/KabbAmine\/vCoolor.vim\/tree\/master\/osx\/color-picker) to trigger the system color picker.\r\nYou can even use your own color picker, refer to the documentation for that.\r\n\r\nTo get the last version or to have more informations check the github repo > https:\/\/github.com\/KabbAmine\/vCoolor.vim\r\nDon't forget to rate it if you find it useful ( Or useless ;) ).\r\n\r\nusage\r\n=====\r\n\r\nIn both NORMAL and INSERT modes, only 1 shortcut is needed: `` (I find it very convenient :D), but he may be not working on terminal.\r\n\r\nUse it:\r\n* To insert a color anywhere.\r\n* To modify the current hex, rgb, rgba or hsl color.\r\n\r\nUsing `` you can insert a rgb color anywhere (NORMAL and INSERT modes).\r\nUsing `` you can insert a hsl color anywhere (NORMAL and INSERT modes).\r\nUsing `` you can insert a rgba color anywhere (NORMAL and INSERT modes).\r\n\r\nPlease refer to the documentation for a full overview of the plugin.\r\n\r\nA short screencast of the v0.1 here > https:\/\/www.youtube.com\/watch?v=ZBJ_-Uxm55U","4":"vCoolor is a Vim plugin that allows using a color picker\/selector directly from the editor.\r\n\r\nWhat this plugin do:\r\n* Insert hex, rgb, rgba (1 in opacity) or hsl color anywhere.\r\n* Modify hex color even if there are many colors in 1 line.\r\n* Modify a rgb color with 0-255 values or % (Only one by line).\r\n* Modify a hsl color (Only one by line).\r\n* Modify a rgba color but don't change opacity (Only one by line).\r\n\r\nWhat this plugin doesn't do:\r\n* Insert or modify hsla colors.\r\n\r\nIn GNU\/Linux it uses a simple GTK+ dialog.\r\nIn windows it uses colorpicker-windows-commandline (https:\/\/github.com\/jaxbot\/colorpicker-windows-commandline) (The binary is included in the plugin).\r\nIn MAC OS it uses a ruby script (https:\/\/github.com\/KabbAmine\/vCoolor.vim\/tree\/master\/osx\/color-picker) to trigger the system color picker.\r\nYou can even use your own color picker, refer to the documentation for that.\r\n\r\nTo get the last version or to have more informations check the github repo > https:\/\/github.com\/KabbAmine\/vCoolor.vim\r\nDon't forget to rate it if you find it useful ( Or useless ;) ).\r\n\r\nusage\r\n=====\r\n\r\nIn both NORMAL and INSERT modes, only 1 shortcut is needed: `` (I find it very convenient :D), but he may be not working on terminal.\r\n\r\nUse it:\r\n* To insert a color anywhere.\r\n* To modify the current hex, rgb, rgba or hsl color.\r\n\r\nUsing `` you can insert a rgb color anywhere (NORMAL and INSERT modes).\r\nUsing `` you can insert a hsl color anywhere (NORMAL and INSERT modes).\r\nUsing `` you can insert a rgba color anywhere (NORMAL and INSERT modes).\r\n\r\nPlease refer to the documentation for a full overview of the plugin.\r\n\r\nA short screencast of the v0.1 here > https:\/\/www.youtube.com\/watch?v=ZBJ_-Uxm55U","install_details":"To use vCoolor in GNU\/Linux, you need to have Zenity or Yad (http:\/\/sourceforge.net\/projects\/yad-dialog\/).\r\n\r\nManual installation\r\n~~~~~~~~~~~~~~~ \r\nInstall the distributed files into Vim runtime directory which is usually `~\/.vim\/`, or `$HOME\/vimfiles` on Windows.\r\n\r\nUsing Pathogen\r\n~~~~~~~~~~~~~\r\nIf you're using pathogen, extract the files into `bundle` directory.\r\n\r\nUsing Vundle\r\n~~~~~~~~~~~~~\r\nJust add the following line in the Vundle part of your vimrc:\r\n    Plugin 'KabbAmine\/vCoolor.vim'\r\n\r\nThen proceed to the installation of the plugin with the following command:\r\n    :PluginInstall","5":"To use vCoolor in GNU\/Linux, you need to have Zenity or Yad (http:\/\/sourceforge.net\/projects\/yad-dialog\/).\r\n\r\nManual installation\r\n~~~~~~~~~~~~~~~ \r\nInstall the distributed files into Vim runtime directory which is usually `~\/.vim\/`, or `$HOME\/vimfiles` on Windows.\r\n\r\nUsing Pathogen\r\n~~~~~~~~~~~~~\r\nIf you're using pathogen, extract the files into `bundle` directory.\r\n\r\nUsing Vundle\r\n~~~~~~~~~~~~~\r\nJust add the following line in the Vundle part of your vimrc:\r\n    Plugin 'KabbAmine\/vCoolor.vim'\r\n\r\nThen proceed to the installation of the plugin with the following command:\r\n    :PluginInstall","first_name":"Kabbaj","6":"Kabbaj","last_name":"Amine","7":"Amine","releases":[{"0":"4995","vim_version":"7.0","1":"7.0","script_version":"1.2.4","2":"1.2.4","version_comment":"- Critical bug: Fix function name\r\n- Make picker work in both terminal and MacVim by @jaxbot\r\n1.2.3:\r\n- Redirect to black hole in MacOS\r\n- Fix osx color picker by @coinsk","3":"- Critical bug: Fix function name\r\n- Make picker work in both terminal and MacVim by @jaxbot\r\n1.2.3:\r\n- Redirect to black hole in MacOS\r\n- Fix osx color picker by @coinsk","package":"vCoolor.tar.gz","4":"vCoolor.tar.gz","src_id":"24071","5":"24071","creation_date":"1457277229","6":"1457277229"},{"0":"4995","vim_version":"7.0","1":"7.0","script_version":"1.2.1","2":"1.2.1","version_comment":"Fix : mapping bug, g:vcoolor_disable_mappings works now as expected ","3":"Fix : mapping bug, g:vcoolor_disable_mappings works now as expected ","package":"vCoolor.tar.gz","4":"vCoolor.tar.gz","src_id":"23168","5":"23168","creation_date":"1428833288","6":"1428833288"},{"0":"4995","vim_version":"7.0","1":"7.0","script_version":"1.2","2":"1.2","version_comment":"- Move most functions to an autoload files.\r\n- Fix hsl conversion issue when returning float number.\r\n- Add an option for disabling default mapping ('g:vcoolor_disable_mappings).\r\n- Update documentations.","3":"- Move most functions to an autoload files.\r\n- Fix hsl conversion issue when returning float number.\r\n- Add an option for disabling default mapping ('g:vcoolor_disable_mappings).\r\n- Update documentations.","package":"vCoolor.tar.gz","4":"vCoolor.tar.gz","src_id":"23134","5":"23134","creation_date":"1428238696","6":"1428238696"},{"0":"4995","vim_version":"7.0","1":"7.0","script_version":"1.1a","2":"1.1a","version_comment":"In INSERTION mode, don't insert # if already present.","3":"In INSERTION mode, don't insert # if already present.","package":"vCoolor.tar.gz","4":"vCoolor.tar.gz","src_id":"22886","5":"22886","creation_date":"1423319180","6":"1423319180"},{"0":"4995","vim_version":"7.0","1":"7.0","script_version":"1.1","2":"1.1","version_comment":"Add partial rgba support:\r\n- Modify rgba color without changing opacity.\r\n- Insert a rgba color with opacity 1.","3":"Add partial rgba support:\r\n- Modify rgba color without changing opacity.\r\n- Insert a rgba color with opacity 1.","package":"vCoolor.tar.gz","4":"vCoolor.tar.gz","src_id":"22553","5":"22553","creation_date":"1413887952","6":"1413887952"},{"0":"4995","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"- Fixes https:\/\/github.com\/KabbAmine\/vCoolor.vim\/issues\/16\r\n- Fixes https:\/\/github.com\/KabbAmine\/vCoolor.vim\/issues\/15\r\n\r\n- Set correct position of cursor after color insertion (INSERT mode).\r\n- Documentation updated.\r\n- Color pickers are now in one folder.\r\n- No more s, you can use global variables to change default mappings.\r\n- Unify function and command for color insertion (:VCoolIns).\r\n- Return message when using command :VCase","3":"- Fixes https:\/\/github.com\/KabbAmine\/vCoolor.vim\/issues\/16\r\n- Fixes https:\/\/github.com\/KabbAmine\/vCoolor.vim\/issues\/15\r\n\r\n- Set correct position of cursor after color insertion (INSERT mode).\r\n- Documentation updated.\r\n- Color pickers are now in one folder.\r\n- No more s, you can use global variables to change default mappings.\r\n- Unify function and command for color insertion (:VCoolIns).\r\n- Return message when using command :VCase","package":"vCoolor.tar.gz","4":"vCoolor.tar.gz","src_id":"22529","5":"22529","creation_date":"1413236452","6":"1413236452"},{"0":"4995","vim_version":"7.0","1":"7.0","script_version":"0.8a","2":"0.8a","version_comment":"VCase added, command for toggling between upper\/lower case for hex color","3":"VCase added, command for toggling between upper\/lower case for hex color","package":"vCoolor.tar.gz","4":"vCoolor.tar.gz","src_id":"22433","5":"22433","creation_date":"1410897373","6":"1410897373"},{"0":"4995","vim_version":"7.0","1":"7.0","script_version":"0.8","2":"0.8","version_comment":"v0.8:\r\n- Add possibility to set hex colors in lowercase by setting the global variable g:vcoolor_lowercase to 1.\r\n- Fix potential exception on OSX.\r\n- Doc file updated.","3":"v0.8:\r\n- Add possibility to set hex colors in lowercase by setting the global variable g:vcoolor_lowercase to 1.\r\n- Fix potential exception on OSX.\r\n- Doc file updated.","package":"vCoolor.tar.gz","4":"vCoolor.tar.gz","src_id":"22336","5":"22336","creation_date":"1408199312","6":"1408199312"},{"0":"4995","vim_version":"7.0","1":"7.0","script_version":"0.7a","2":"0.7a","version_comment":"v0.7:\r\n- Windows support.\r\n- MAC OS support.\r\n- No more VCoolor* shadowed, more responsive.\r\n\r\nv0.6:\r\n- The plugin ConvertBase is no more needed.\r\n\r\nv0.5:\r\n- Hsl support added.\r\n- Possibility to insert hsl color with  added.","3":"v0.7:\r\n- Windows support.\r\n- MAC OS support.\r\n- No more VCoolor* shadowed, more responsive.\r\n\r\nv0.6:\r\n- The plugin ConvertBase is no more needed.\r\n\r\nv0.5:\r\n- Hsl support added.\r\n- Possibility to insert hsl color with  added.","package":"vCoolor.tar.gz","4":"vCoolor.tar.gz","src_id":"22324","5":"22324","creation_date":"1408035602","6":"1408035602"},{"0":"4995","vim_version":"7.0","1":"7.0","script_version":"0.3","2":"0.3","version_comment":"- Possibility to insert rgb color with  added.\r\n- README updated.","3":"- Possibility to insert rgb color with  added.\r\n- README updated.","package":"vCoolor.tar.gz","4":"vCoolor.tar.gz","src_id":"22290","5":"22290","creation_date":"1407317187","6":"1407317187"},{"0":"4995","vim_version":"7.0","1":"7.0","script_version":"0.2","2":"0.2","version_comment":"Support of rgb(%) added.","3":"Support of rgb(%) added.","package":"vCoolor.tar.gz","4":"vCoolor.tar.gz","src_id":"22286","5":"22286","creation_date":"1407144732","6":"1407144732"},{"0":"4995","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Fix a small error","3":"Fix a small error","package":"vCoolor.tar.gz","4":"vCoolor.tar.gz","src_id":"22284","5":"22284","creation_date":"1406999759","6":"1406999759"}]},"4994":{"script_id":"4994","0":"4994","script_name":"cloudboard.vim","1":"cloudboard.vim","script_type":"utility","2":"utility","summary":"A cloud-based clipboard, copy text on a machine, paste it on another","3":"A cloud-based clipboard, copy text on a machine, paste it on another","description":"# cloudboard.vim\r\n\r\nhttps:\/\/github.com\/brookhong\/cloudboard.vim\r\n\r\n中文文档 https:\/\/brookhong.github.io\/2014\/09\/27\/cloudboard-cn.html\r\n\r\nA cloud-based clipboard, yank(copy) text into a numbered cloud register on a machine, put(paste) the text from the cloud register on another machine.\r\n\r\nIt uses GITHUB's gist as the cloud service.\r\n\r\n# Usage\r\n\r\n1. run command `:CBInit` to set up your own cloudboard.\r\n2. visual select the text that you want to copy (otherwise all the current buffer), use command `:CBYank 0` to copy it into cloud register 0.\r\nhttps:\/\/raw.githubusercontent.com\/brookhong\/brookhong.github.io\/master\/assets\/images\/cbyank.gif\r\n3. open vim on another machine, use command `:CBPut 0` to paste the text from cloud register 0.\r\nhttps:\/\/raw.githubusercontent.com\/brookhong\/brookhong.github.io\/master\/assets\/images\/cbput.gif\r\n\r\n\r\n### Cloud Register\r\n\r\nThe number starts from 0, you can use anyone you'd like, for example:\r\n\r\n    :CBYank 5\r\n    :CBPut 5\r\n\r\n\r\n`:CBList` to put the contents from all cloud registers into current buffer.\r\n\r\n#### Auto Clear of Cloud Registers\r\n\r\nWhen AutoClear is turned on for a cloud register, the content of the cloud register will be cleared automatically after its content is read by a `CBPut` action.\r\n\r\n`:CBAutoClear 2` to toggle on\/off AutoClear of cloud register 2.\r\n\r\n### Cloud Files\r\n\r\nCloud files are named files stored in a GITHUB gist.\r\n\r\n    :CBSave test.c      to save selected range into a cloud file named test.c.\r\n    :CBLoad test.c      to load a cloud file test.c into current buffer.\r\n    :CBRm test.c        to delete a cloud file test.c.\r\n    :CBListFiles        to list all cloud files in the cloudboard gist.\r\n\r\nLoading cloud files requires two requests to GITHUB, thus cloud register is faster to be used as a clipboard across machines.\r\nCloud files is better when the text is huge, especial in case of that you prefer to save them for long period.\r\n\r\n### Recommended Mappings\r\n\r\n    nnoremap p :CBPut \r\n    vnoremap y :CBYank \r\n\r\n# Installation\r\n\r\nYour VIM must have python support, check it with `:python print 'hello'`.\r\n\r\n`Bundle 'brookhong\/cloudboard.vim'`\r\n\r\nor\r\n\r\nJust unzip the zip file to your VIM file path, usually to be ~\/.vim. \r\n","4":"# cloudboard.vim\r\n\r\nhttps:\/\/github.com\/brookhong\/cloudboard.vim\r\n\r\n中文文档 https:\/\/brookhong.github.io\/2014\/09\/27\/cloudboard-cn.html\r\n\r\nA cloud-based clipboard, yank(copy) text into a numbered cloud register on a machine, put(paste) the text from the cloud register on another machine.\r\n\r\nIt uses GITHUB's gist as the cloud service.\r\n\r\n# Usage\r\n\r\n1. run command `:CBInit` to set up your own cloudboard.\r\n2. visual select the text that you want to copy (otherwise all the current buffer), use command `:CBYank 0` to copy it into cloud register 0.\r\nhttps:\/\/raw.githubusercontent.com\/brookhong\/brookhong.github.io\/master\/assets\/images\/cbyank.gif\r\n3. open vim on another machine, use command `:CBPut 0` to paste the text from cloud register 0.\r\nhttps:\/\/raw.githubusercontent.com\/brookhong\/brookhong.github.io\/master\/assets\/images\/cbput.gif\r\n\r\n\r\n### Cloud Register\r\n\r\nThe number starts from 0, you can use anyone you'd like, for example:\r\n\r\n    :CBYank 5\r\n    :CBPut 5\r\n\r\n\r\n`:CBList` to put the contents from all cloud registers into current buffer.\r\n\r\n#### Auto Clear of Cloud Registers\r\n\r\nWhen AutoClear is turned on for a cloud register, the content of the cloud register will be cleared automatically after its content is read by a `CBPut` action.\r\n\r\n`:CBAutoClear 2` to toggle on\/off AutoClear of cloud register 2.\r\n\r\n### Cloud Files\r\n\r\nCloud files are named files stored in a GITHUB gist.\r\n\r\n    :CBSave test.c      to save selected range into a cloud file named test.c.\r\n    :CBLoad test.c      to load a cloud file test.c into current buffer.\r\n    :CBRm test.c        to delete a cloud file test.c.\r\n    :CBListFiles        to list all cloud files in the cloudboard gist.\r\n\r\nLoading cloud files requires two requests to GITHUB, thus cloud register is faster to be used as a clipboard across machines.\r\nCloud files is better when the text is huge, especial in case of that you prefer to save them for long period.\r\n\r\n### Recommended Mappings\r\n\r\n    nnoremap p :CBPut \r\n    vnoremap y :CBYank \r\n\r\n# Installation\r\n\r\nYour VIM must have python support, check it with `:python print 'hello'`.\r\n\r\n`Bundle 'brookhong\/cloudboard.vim'`\r\n\r\nor\r\n\r\nJust unzip the zip file to your VIM file path, usually to be ~\/.vim. \r\n","install_details":"","5":"","first_name":"brook","6":"brook","last_name":"hong","7":"hong","releases":[{"0":"4994","vim_version":"7.3","1":"7.3","script_version":"1.0.2","2":"1.0.2","version_comment":"Because that the token attribute is deprecated in some of OAuth Authorizations API responses, the plugin will require user to input token directly instead of fetching a token through username\/password.","3":"Because that the token attribute is deprecated in some of OAuth Authorizations API responses, the plugin will require user to input token directly instead of fetching a token through username\/password.","package":"cloudboard.zip","4":"cloudboard.zip","src_id":"23242","5":"23242","creation_date":"1430408572","6":"1430408572"},{"0":"4994","vim_version":"7.3","1":"7.3","script_version":"1.0.1","2":"1.0.1","version_comment":"add commmand :CBList\r\nadd commands for cloud files\r\nadd commmand :CBAutoClear\r\n","3":"add commmand :CBList\r\nadd commands for cloud files\r\nadd commmand :CBAutoClear\r\n","package":"cloudboard.zip","4":"cloudboard.zip","src_id":"22463","5":"22463","creation_date":"1411877938","6":"1411877938"},{"0":"4994","vim_version":"7.3","1":"7.3","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"cloudboard.zip","4":"cloudboard.zip","src_id":"22273","5":"22273","creation_date":"1406635051","6":"1406635051"}]},"4993":{"script_id":"4993","0":"4993","script_name":"vim-root","1":"vim-root","script_type":"syntax","2":"syntax","summary":"Basic syntax highlighting for the ROOT Data Analysis Framework","3":"Basic syntax highlighting for the ROOT Data Analysis Framework","description":"Basic syntax highlighting for the ROOT Data Analysis Framework http:\/\/root.cern.ch\/\r\n\r\nInitially inspired by Theo Christoudias' plugin: cern_root.vim. (vimscript #2387)\r\n\r\nIn contrast to cern_root.vim, this plugin is structured to work with common Vim plugin managers. It attempts to be semantically correct, which also allows seamless integration with both the PyROOT, as well as the original C++ implementation.","4":"Basic syntax highlighting for the ROOT Data Analysis Framework http:\/\/root.cern.ch\/\r\n\r\nInitially inspired by Theo Christoudias' plugin: cern_root.vim. (vimscript #2387)\r\n\r\nIn contrast to cern_root.vim, this plugin is structured to work with common Vim plugin managers. It attempts to be semantically correct, which also allows seamless integration with both the PyROOT, as well as the original C++ implementation.","install_details":"You can use the git repository with your favourite vim package manager: \r\nhttps:\/\/github.com\/parnmatt\/vim-root\r\n\r\nor manually:\r\n\r\n$ mkdir -p vim-root ${VIMRUNTIME:-$HOME\/.vim}\/syntax\/\r\n$ tar -xzf vim-root*.tar.gz -C vim-root\r\n$ mv vim-root\/syntax\/root.vim ${VIMRUNTIME:-$HOME\/.vim}\/syntax\/\r\n$ rm -rf vim-root*","5":"You can use the git repository with your favourite vim package manager: \r\nhttps:\/\/github.com\/parnmatt\/vim-root\r\n\r\nor manually:\r\n\r\n$ mkdir -p vim-root ${VIMRUNTIME:-$HOME\/.vim}\/syntax\/\r\n$ tar -xzf vim-root*.tar.gz -C vim-root\r\n$ mv vim-root\/syntax\/root.vim ${VIMRUNTIME:-$HOME\/.vim}\/syntax\/\r\n$ rm -rf vim-root*","first_name":"Matthew","6":"Matthew","last_name":"Parnell","7":"Parnell","releases":[{"0":"4993","vim_version":"7.0","1":"7.0","script_version":"1.0.1","2":"1.0.1","version_comment":"Uploaded documentation","3":"Uploaded documentation","package":"vim-root-1.0.1.tar.gz","4":"vim-root-1.0.1.tar.gz","src_id":"24497","5":"24497","creation_date":"1473017447","6":"1473017447"},{"0":"4993","vim_version":"6.0","1":"6.0","script_version":"1.0.0","2":"1.0.0","version_comment":"Initial upload","3":"Initial upload","package":"vim-root_v1.0.0.tar.gz","4":"vim-root_v1.0.0.tar.gz","src_id":"22269","5":"22269","creation_date":"1406584538","6":"1406584538"}]},"4992":{"script_id":"4992","0":"4992","script_name":"elm.vim","1":"elm.vim","script_type":"ftplugin","2":"ftplugin","summary":"Plugin for the Elm programming language","3":"Plugin for the Elm programming language","description":"Vim plugin for the Elm programming language. \r\n\r\nIncludes syntax highlighting and integration with the Elm compiler, repl, etc.\r\n\r\nSee: https:\/\/github.com\/lambdatoast\/elm.vim","4":"Vim plugin for the Elm programming language. \r\n\r\nIncludes syntax highlighting and integration with the Elm compiler, repl, etc.\r\n\r\nSee: https:\/\/github.com\/lambdatoast\/elm.vim","install_details":"Nothing other than vim is needed for the syntax highlighting.\r\n\r\nFor the special commands and aliases (for compilation, etc), the plugin expects the following programs to be available:\r\n\r\n* elm: The Elm compiler.\r\n* elm-repl: The Elm REPL. The plugin sends it bits of code for evaluation.","5":"Nothing other than vim is needed for the syntax highlighting.\r\n\r\nFor the special commands and aliases (for compilation, etc), the plugin expects the following programs to be available:\r\n\r\n* elm: The Elm compiler.\r\n* elm-repl: The Elm REPL. The plugin sends it bits of code for evaluation.","first_name":"Alexander","6":"Alexander","last_name":"Noriega","7":"Noriega","releases":[{"0":"4992","vim_version":"7.3","1":"7.3","script_version":"0.4.1","2":"0.4.1","version_comment":"Initial upload","3":"Initial upload","package":"elm.vim.tgz","4":"elm.vim.tgz","src_id":"22268","5":"22268","creation_date":"1406555534","6":"1406555534"}]},"4991":{"script_id":"4991","0":"4991","script_name":"a_pair","1":"a_pair","script_type":"utility","2":"utility","summary":"combine {}, [], () into one text object :","3":"combine {}, [], () into one text object :","description":"the script combine {}, [], () into one text object ap\r\n\r\ngithub : https:\/\/github.com\/caigithub\/a_pair\/wiki\r\n\r\n==================\r\n1:  {\r\n2:      aaa                             \/\/ execute : dap, it will delete the {}, line1-line11\r\n3:      [\r\n4:           bbb                        \/\/ execute : vap, it will select the  [], line4-line8\r\n5:           (\r\n6:                ccc                    \/\/ execute : xap, it will cut the (), line5-line7\r\n7:            )\r\n8:            ddd\r\n9:      ]\r\n10:    ggg\r\n11:  }\r\n \r\n\r\n   ","4":"the script combine {}, [], () into one text object ap\r\n\r\ngithub : https:\/\/github.com\/caigithub\/a_pair\/wiki\r\n\r\n==================\r\n1:  {\r\n2:      aaa                             \/\/ execute : dap, it will delete the {}, line1-line11\r\n3:      [\r\n4:           bbb                        \/\/ execute : vap, it will select the  [], line4-line8\r\n5:           (\r\n6:                ccc                    \/\/ execute : xap, it will cut the (), line5-line7\r\n7:            )\r\n8:            ddd\r\n9:      ]\r\n10:    ggg\r\n11:  }\r\n \r\n\r\n   ","install_details":"","5":"","first_name":"colin","6":"colin","last_name":"cai","7":"cai","releases":[{"0":"4991","vim_version":"7.0","1":"7.0","script_version":"7.0","2":"7.0","version_comment":"Initial upload","3":"Initial upload","package":"a_pair.vim","4":"a_pair.vim","src_id":"22263","5":"22263","creation_date":"1406383307","6":"1406383307"}]},"4990":{"script_id":"4990","0":"4990","script_name":"srec.vim","1":"srec.vim","script_type":"syntax","2":"syntax","summary":"Colorizes SREC (Motorola S-Record) files","3":"Colorizes SREC (Motorola S-Record) files","description":"Just an update for version by Peter Sommerfeld (http:\/\/www.vim.org\/scripts\/script.php?script_id=873)\r\n\r\n+ Fixed syntax match for 16-Bit Addresses\r\n+ Added commonly used data fields in header (Version, Revision)\r\n+ Added count register (S5) support","4":"Just an update for version by Peter Sommerfeld (http:\/\/www.vim.org\/scripts\/script.php?script_id=873)\r\n\r\n+ Fixed syntax match for 16-Bit Addresses\r\n+ Added commonly used data fields in header (Version, Revision)\r\n+ Added count register (S5) support","install_details":"Just put it in $HOME\/.vim\/plugin","5":"Just put it in $HOME\/.vim\/plugin","first_name":"Martino","6":"Martino","last_name":"Saco","7":"Saco","releases":[{"0":"4990","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"srec.vim","4":"srec.vim","src_id":"22234","5":"22234","creation_date":"1406027383","6":"1406027383"}]},"4989":{"script_id":"4989","0":"4989","script_name":"projectionist.vim","1":"projectionist.vim","script_type":"utility","2":"utility","summary":"Granular project configuration","3":"Granular project configuration","description":"Projectionist provides granular project configuration using \"projections\".  What are projections?  Let's start with an example.\r\n\r\n## Example\r\n\r\nA while back I went and made a bunch of plugins for working with rbenv.  Here's what a couple of them look like:\r\n\r\n    ~\/.rbenv\/plugins $ tree\r\n    .\r\n    |-- rbenv-ctags\r\n    |   |-- bin\r\n    |   |   `-- rbenv-ctags\r\n    |   `-- etc\r\n    |       `-- rbenv.d\r\n    |           `-- install\r\n    |               `-- ctags.bash\r\n    `-- rbenv-sentience\r\n        `-- etc\r\n            `-- rbenv.d\r\n                `-- install\r\n                    `-- sentience.bash\r\n\r\nAs you can see, rbenv plugins have hooks in `etc\/rbenv.d\/` and commands in `bin\/` matching `rbenv-*`.  Here's a projectionist configuration for that setup:\r\n\r\n    let g:projectionist_heuristics = {\r\n          \\   \"etc\/rbenv.d\/|bin\/rbenv-*\": {\r\n          \\     \"bin\/rbenv-*\": {\r\n          \\        \"type\": \"command\",\r\n          \\        \"template\": [\"#!\/usr\/bin\/env bash\"],\r\n          \\     },\r\n          \\     \"etc\/rbenv.d\/*.bash\": {\"type\": \"hook\"}\r\n          \\   }\r\n          \\ }\r\n\r\nThe key in the outermost dictionary says to activate for any directory containing a subdirectory `etc\/rbenv.d\/` *or* files matching `bin\/rbenv-*`.  The corresponding value contains projection definitions.  Here, two projections are defined.  The first creates an `:Ecommand` navigation command and provides boilerplate to pre-populate new files with, and the second creates an `:Ehook` command.\r\n\r\n## Features\r\n\r\nSee `:help projectionist` for the authoritative documentation.  Here are some highlights.\r\n\r\n### Global and per project projection definitions\r\n\r\nIn the above example, we used the global `g:projectionist_heuristics` to declare projections based on requirements in the root directory.  If that's not flexible enough, you can use the autocommand based API, or create a `.projections.json` in the root of the project.\r\n\r\n### Navigation commands\r\n\r\nNavigation commands encapsulate editing filenames matching certain patterns.  Here are some examples for this very project:\r\n\r\n    {\r\n      \"plugin\/*.vim\": {\"type\": \"plugin\"},\r\n      \"autoload\/*.vim\": {\"type\": \"autoload\"},\r\n      \"doc\/*.txt\": {\"type\": \"doc\"},\r\n      \"README.markdown\": {\"type\": \"doc\"}\r\n    }\r\n\r\nWith these in place, you could use `:Eplugin projectionist` to edit `plugin\/projectionist.vim` and `:Edoc projectionist` to edit `doc\/projectionist.txt`.  For `README.markdown`, since there's no glob, it becomes the default destination for `:Edoc` if no argument is given.\r\n\r\nThe `E` stands for `edit`.  You also get `S`, `V`, and `T` variants that `split`, `vsplit`, and `tabedit`.\r\n\r\nTab complete is smart.  Not quite \"fuzzy finder\" smart but smart nonetheless.  (On that note, fuzzy finders are great, but I prefer the navigation command approach when there are multiple categories of similarly named files.)\r\n\r\n### Alternate files\r\n\r\nProjectionist provides `:A`, `:AS`, `:AV`, and `:AT` to jump to an \"alternate\" file, based on ye olde convention originally established in vimscript #31.  Here's an example configuration for Maven that allows you to jump between the implementation and test:\r\n\r\n    {\r\n      \"src\/main\/java\/*.java\": {\"alternate\": \"src\/test\/java\/{}.java\"},\r\n      \"src\/test\/java\/*.java\": {\"alternate\": \"src\/main\/java\/{}.java\"}\r\n    }\r\n\r\nBonus feature: `:A {filename}` edits a file relative to the root of the project.\r\n\r\n### Buffer configuration\r\n\r\nCheck out these examples for a minimal Ruby project:\r\n\r\n    {\r\n      \"*\": {\"make\": \"rake\"},\r\n      \"spec\/*_spec.rb\": {\"dispatch\": \"rspec {file}\"}\r\n    }\r\n\r\nThat second one sets the default for dispatch.vim (vimscript #4504).  Plugins can use projections for their own configuration.","4":"Projectionist provides granular project configuration using \"projections\".  What are projections?  Let's start with an example.\r\n\r\n## Example\r\n\r\nA while back I went and made a bunch of plugins for working with rbenv.  Here's what a couple of them look like:\r\n\r\n    ~\/.rbenv\/plugins $ tree\r\n    .\r\n    |-- rbenv-ctags\r\n    |   |-- bin\r\n    |   |   `-- rbenv-ctags\r\n    |   `-- etc\r\n    |       `-- rbenv.d\r\n    |           `-- install\r\n    |               `-- ctags.bash\r\n    `-- rbenv-sentience\r\n        `-- etc\r\n            `-- rbenv.d\r\n                `-- install\r\n                    `-- sentience.bash\r\n\r\nAs you can see, rbenv plugins have hooks in `etc\/rbenv.d\/` and commands in `bin\/` matching `rbenv-*`.  Here's a projectionist configuration for that setup:\r\n\r\n    let g:projectionist_heuristics = {\r\n          \\   \"etc\/rbenv.d\/|bin\/rbenv-*\": {\r\n          \\     \"bin\/rbenv-*\": {\r\n          \\        \"type\": \"command\",\r\n          \\        \"template\": [\"#!\/usr\/bin\/env bash\"],\r\n          \\     },\r\n          \\     \"etc\/rbenv.d\/*.bash\": {\"type\": \"hook\"}\r\n          \\   }\r\n          \\ }\r\n\r\nThe key in the outermost dictionary says to activate for any directory containing a subdirectory `etc\/rbenv.d\/` *or* files matching `bin\/rbenv-*`.  The corresponding value contains projection definitions.  Here, two projections are defined.  The first creates an `:Ecommand` navigation command and provides boilerplate to pre-populate new files with, and the second creates an `:Ehook` command.\r\n\r\n## Features\r\n\r\nSee `:help projectionist` for the authoritative documentation.  Here are some highlights.\r\n\r\n### Global and per project projection definitions\r\n\r\nIn the above example, we used the global `g:projectionist_heuristics` to declare projections based on requirements in the root directory.  If that's not flexible enough, you can use the autocommand based API, or create a `.projections.json` in the root of the project.\r\n\r\n### Navigation commands\r\n\r\nNavigation commands encapsulate editing filenames matching certain patterns.  Here are some examples for this very project:\r\n\r\n    {\r\n      \"plugin\/*.vim\": {\"type\": \"plugin\"},\r\n      \"autoload\/*.vim\": {\"type\": \"autoload\"},\r\n      \"doc\/*.txt\": {\"type\": \"doc\"},\r\n      \"README.markdown\": {\"type\": \"doc\"}\r\n    }\r\n\r\nWith these in place, you could use `:Eplugin projectionist` to edit `plugin\/projectionist.vim` and `:Edoc projectionist` to edit `doc\/projectionist.txt`.  For `README.markdown`, since there's no glob, it becomes the default destination for `:Edoc` if no argument is given.\r\n\r\nThe `E` stands for `edit`.  You also get `S`, `V`, and `T` variants that `split`, `vsplit`, and `tabedit`.\r\n\r\nTab complete is smart.  Not quite \"fuzzy finder\" smart but smart nonetheless.  (On that note, fuzzy finders are great, but I prefer the navigation command approach when there are multiple categories of similarly named files.)\r\n\r\n### Alternate files\r\n\r\nProjectionist provides `:A`, `:AS`, `:AV`, and `:AT` to jump to an \"alternate\" file, based on ye olde convention originally established in vimscript #31.  Here's an example configuration for Maven that allows you to jump between the implementation and test:\r\n\r\n    {\r\n      \"src\/main\/java\/*.java\": {\"alternate\": \"src\/test\/java\/{}.java\"},\r\n      \"src\/test\/java\/*.java\": {\"alternate\": \"src\/main\/java\/{}.java\"}\r\n    }\r\n\r\nBonus feature: `:A {filename}` edits a file relative to the root of the project.\r\n\r\n### Buffer configuration\r\n\r\nCheck out these examples for a minimal Ruby project:\r\n\r\n    {\r\n      \"*\": {\"make\": \"rake\"},\r\n      \"spec\/*_spec.rb\": {\"dispatch\": \"rspec {file}\"}\r\n    }\r\n\r\nThat second one sets the default for dispatch.vim (vimscript #4504).  Plugins can use projections for their own configuration.","install_details":"Extract in ~\/.vim (~\\vimfiles on Windows).\r\n\r\nhttps:\/\/github.com\/tpope\/vim-projectionist","5":"Extract in ~\/.vim (~\\vimfiles on Windows).\r\n\r\nhttps:\/\/github.com\/tpope\/vim-projectionist","first_name":"Tim","6":"Tim","last_name":"Pope","7":"Pope","releases":[{"0":"4989","vim_version":"7.0","1":"7.0","script_version":"1.3","2":"1.3","version_comment":"Fix :Pcd and :Plcd.","3":"Fix :Pcd and :Plcd.","package":"projectionist.zip","4":"projectionist.zip","src_id":"26200","5":"26200","creation_date":"1535977379","6":"1535977379"},{"0":"4989","vim_version":"7.0","1":"7.0","script_version":"1.2","2":"1.2","version_comment":"Support virtual buffers from plugins like Fugitive.\r\nMinor bug fixes.","3":"Support virtual buffers from plugins like Fugitive.\r\nMinor bug fixes.","package":"projectionist.zip","4":"projectionist.zip","src_id":"26195","5":"26195","creation_date":"1535450561","6":"1535450561"},{"0":"4989","vim_version":"7.0","1":"7.0","script_version":"1.1","2":"1.1","version_comment":"Provide \"path\" projection to append to 'path'.\r\nAdd tags file to 'tags' for each project root.\r\nProvide snakecase transformation.\r\nChange camelcase transformation from UpperCamelCase to lowerCamelCase.\r\nSupport mods like :vertical.\r\nSupport +cmd and ++opt.\r\nReplace :Cd and :Lcd with :Pcd and :Plcd.\r\nPrompt to create alternate if none exists.\r\nBug fixes.","3":"Provide \"path\" projection to append to 'path'.\r\nAdd tags file to 'tags' for each project root.\r\nProvide snakecase transformation.\r\nChange camelcase transformation from UpperCamelCase to lowerCamelCase.\r\nSupport mods like :vertical.\r\nSupport +cmd and ++opt.\r\nReplace :Cd and :Lcd with :Pcd and :Plcd.\r\nPrompt to create alternate if none exists.\r\nBug fixes.","package":"projectionist.zip","4":"projectionist.zip","src_id":"26101","5":"26101","creation_date":"1530599762","6":"1530599762"},{"0":"4989","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"projectionist.zip","4":"projectionist.zip","src_id":"22231","5":"22231","creation_date":"1405980958","6":"1405980958"}]},"4988":{"script_id":"4988","0":"4988","script_name":"SpellLangIdentifier","1":"SpellLangIdentifier","script_type":"utility","2":"utility","summary":"Automatically identify buffer's language and set the spell lang","3":"Automatically identify buffer's language and set the spell lang","description":"SpellLangIdentifier detects the language based on the buffer contents through 'mguesser' (http:\/\/www.mnogosearch.org\/guesser\/), which in turn uses \"N-Gram-Based Text Categorization\".\r\n\r\nGit repository: https:\/\/github.com\/daaugusto\/spelllangidentifier","4":"SpellLangIdentifier detects the language based on the buffer contents through 'mguesser' (http:\/\/www.mnogosearch.org\/guesser\/), which in turn uses \"N-Gram-Based Text Categorization\".\r\n\r\nGit repository: https:\/\/github.com\/daaugusto\/spelllangidentifier","install_details":"Installation\r\n------------\r\n\r\nDecompress the tarball and change to directory sli-x.y.z\/\r\nFrom there, assuming you have a standard Vim setup:\r\n\r\n\r\n   mkdir -p ~\/.vim\/plugin\r\n   cp -r SpellLangIdentifier.vim LanguageIdentifier.sh mguesser ~\/.vim\/plugin\r\n   cp vimrc.sample ~\/.vimrc.sli\r\n   cd ~\/.vim\/plugin\/mguesser && make\r\n\r\n\r\n\r\nConfiguration (~\/.vimrc)\r\n------------------------\r\n\r\nPlease, check out the sample Vim configuration file which you have just copied. If you prefer you can introduce your changes there and source it directly from your personal vimrc (usually ~\/.vimrc), by inserting the line:\r\n\r\n   source ~\/.vimrc.sli\r\n\r\nMake sure you remove or comment out any previous spell checking configuration that might conflict with the new ones.\r\n\r\n\r\nUsage\r\n-----\r\n\r\n   1. Automatically (just open a text, mail or TeX file, as illustrated in ~\/.vimrc.sli). It even works on-the-fly while you edit the file, switching the languages on a paragraph basis when working on multi-language documents (configurable).\r\n   2. Using shortcuts in normal or insert mode (F5, F6, F7 and F8; F9 to disable spell checking and on-the-fly language identification).\r\n   3. Directly: :{range}SpellLangIdentify (identify the language based on {range} lines; default is the whole buffer).\r\n\r\n\r\nNotes\r\n-----\r\n\r\nThe user can create its own reference language set (\"maps\") which will guide\/bias the language identification. An example would be to create an n-gram frequency file (a map) for words related to the medical literature or, perhaps, to some subset of the English language. Please check out mguesser's documentation for that.\r\n\r\n\r\nPrerequisites\r\n-------------\r\n\r\n   * Unix-like environment (POSIX shell, coreutils, awk, sed, grep, file, ...).\r\n\r\n   * In order to improve language detection according to the file type at hand, it is recommended (but not required) to have the following utilities installed: detex, ps2ascii, html2text.","5":"Installation\r\n------------\r\n\r\nDecompress the tarball and change to directory sli-x.y.z\/\r\nFrom there, assuming you have a standard Vim setup:\r\n\r\n\r\n   mkdir -p ~\/.vim\/plugin\r\n   cp -r SpellLangIdentifier.vim LanguageIdentifier.sh mguesser ~\/.vim\/plugin\r\n   cp vimrc.sample ~\/.vimrc.sli\r\n   cd ~\/.vim\/plugin\/mguesser && make\r\n\r\n\r\n\r\nConfiguration (~\/.vimrc)\r\n------------------------\r\n\r\nPlease, check out the sample Vim configuration file which you have just copied. If you prefer you can introduce your changes there and source it directly from your personal vimrc (usually ~\/.vimrc), by inserting the line:\r\n\r\n   source ~\/.vimrc.sli\r\n\r\nMake sure you remove or comment out any previous spell checking configuration that might conflict with the new ones.\r\n\r\n\r\nUsage\r\n-----\r\n\r\n   1. Automatically (just open a text, mail or TeX file, as illustrated in ~\/.vimrc.sli). It even works on-the-fly while you edit the file, switching the languages on a paragraph basis when working on multi-language documents (configurable).\r\n   2. Using shortcuts in normal or insert mode (F5, F6, F7 and F8; F9 to disable spell checking and on-the-fly language identification).\r\n   3. Directly: :{range}SpellLangIdentify (identify the language based on {range} lines; default is the whole buffer).\r\n\r\n\r\nNotes\r\n-----\r\n\r\nThe user can create its own reference language set (\"maps\") which will guide\/bias the language identification. An example would be to create an n-gram frequency file (a map) for words related to the medical literature or, perhaps, to some subset of the English language. Please check out mguesser's documentation for that.\r\n\r\n\r\nPrerequisites\r\n-------------\r\n\r\n   * Unix-like environment (POSIX shell, coreutils, awk, sed, grep, file, ...).\r\n\r\n   * In order to improve language detection according to the file type at hand, it is recommended (but not required) to have the following utilities installed: detex, ps2ascii, html2text.","first_name":"Douglas","6":"Douglas","last_name":"Augusto","7":"Augusto","releases":[{"0":"4988","vim_version":"7.0","1":"7.0","script_version":"1.0.1","2":"1.0.1","version_comment":"OS X compatibility changes (thanks Ingo Heimbach).","3":"OS X compatibility changes (thanks Ingo Heimbach).","package":"sli-1.0.1.tar.gz","4":"sli-1.0.1.tar.gz","src_id":"27228","5":"27228","creation_date":"1593861769","6":"1593861769"},{"0":"4988","vim_version":"7.0","1":"7.0","script_version":"1.0.0","2":"1.0.0","version_comment":"* Fixes the issue with stray characters in console-based Vim when using on-the-fly language detection.\r\n* Better error handling.\r\n* Improves the sample configuration file.\r\n\r\n","3":"* Fixes the issue with stray characters in console-based Vim when using on-the-fly language detection.\r\n* Better error handling.\r\n* Improves the sample configuration file.\r\n\r\n","package":"sli-1.0.0.tar.gz","4":"sli-1.0.0.tar.gz","src_id":"23362","5":"23362","creation_date":"1433654557","6":"1433654557"},{"0":"4988","vim_version":"7.0","1":"7.0","script_version":"0.4.1","2":"0.4.1","version_comment":"Mail file types were not being handled\/filtered properly and a note about a known issue in console-based Vim when using on-the-fly language detection.","3":"Mail file types were not being handled\/filtered properly and a note about a known issue in console-based Vim when using on-the-fly language detection.","package":"sli-0.4.1.tar.gz","4":"sli-0.4.1.tar.gz","src_id":"22380","5":"22380","creation_date":"1409328103","6":"1409328103"},{"0":"4988","vim_version":"7.0","1":"7.0","script_version":"0.4.0","2":"0.4.0","version_comment":"Improved mappings (see README and vimrc.sample), better support according to the file type, bug fixes.","3":"Improved mappings (see README and vimrc.sample), better support according to the file type, bug fixes.","package":"sli-0.4.0.tar.gz","4":"sli-0.4.0.tar.gz","src_id":"22270","5":"22270","creation_date":"1406593278","6":"1406593278"},{"0":"4988","vim_version":"7.0","1":"7.0","script_version":"0.3.0","2":"0.3.0","version_comment":"Fine-grained on-the-fly spell language identification and bug fixes.\r\n","3":"Fine-grained on-the-fly spell language identification and bug fixes.\r\n","package":"sli-0.3.0.tar.gz","4":"sli-0.3.0.tar.gz","src_id":"22259","5":"22259","creation_date":"1406268233","6":"1406268233"},{"0":"4988","vim_version":"7.0","1":"7.0","script_version":"0.2.0","2":"0.2.0","version_comment":"Improvements, bug fixes and clarifications.","3":"Improvements, bug fixes and clarifications.","package":"sli-0.2.0.tar.gz","4":"sli-0.2.0.tar.gz","src_id":"22252","5":"22252","creation_date":"1406108982","6":"1406108982"},{"0":"4988","vim_version":"7.0","1":"7.0","script_version":"0.1.0","2":"0.1.0","version_comment":"Initial upload","3":"Initial upload","package":"sli-0.1.0.tar.gz","4":"sli-0.1.0.tar.gz","src_id":"22227","5":"22227","creation_date":"1405959554","6":"1405959554"}]},"4987":{"script_id":"4987","0":"4987","script_name":"vim-simple-session","1":"vim-simple-session","script_type":"utility","2":"utility","summary":"Super simple sessions","3":"Super simple sessions","description":"Simple session is a straightforward, no hassle plugin for handling named\r\nsessions in VIM.\r\n\r\nJust type away :Session {name} for creating new sessions or switching to\r\nold sessions. :SList, :SDelete and :SQuit pretty much do what they\r\npromise. Commands that take an argument support autocompletion.\r\n\r\nSessions are automatically saved when VIM is closed or an old session is\r\nopened up.\r\n\r\nMore information at http:\/\/github.com\/manuel-colmenero\/vim-simple-session","4":"Simple session is a straightforward, no hassle plugin for handling named\r\nsessions in VIM.\r\n\r\nJust type away :Session {name} for creating new sessions or switching to\r\nold sessions. :SList, :SDelete and :SQuit pretty much do what they\r\npromise. Commands that take an argument support autocompletion.\r\n\r\nSessions are automatically saved when VIM is closed or an old session is\r\nopened up.\r\n\r\nMore information at http:\/\/github.com\/manuel-colmenero\/vim-simple-session","install_details":"Just copy the files to your ~\/.vim\/ directory, or see alternatives at\r\nhttp:\/\/github.com\/manuel-colmenero\/vim-simple-session","5":"Just copy the files to your ~\/.vim\/ directory, or see alternatives at\r\nhttp:\/\/github.com\/manuel-colmenero\/vim-simple-session","first_name":"Manuel","6":"Manuel","last_name":"Colmenero","7":"Colmenero","releases":[{"0":"4987","vim_version":"7.3","1":"7.3","script_version":"1.0.0","2":"1.0.0","version_comment":"Initial upload","3":"Initial upload","package":"vim-simple-session.zip","4":"vim-simple-session.zip","src_id":"22207","5":"22207","creation_date":"1405467031","6":"1405467031"}]},"4986":{"script_id":"4986","0":"4986","script_name":"glowshi-ft.vim","1":"glowshi-ft.vim","script_type":"utility","2":"utility","summary":"Improve movement of f\/t with glow shift.","3":"Improve movement of f\/t with glow shift.","description":"glowshi-ft.vim is a Vim plugin to improve movement of f\/t. The basic behavior is the same, but when there are multiple targets in the current line, you are able to choose and shift to candidates of position which glow.","4":"glowshi-ft.vim is a Vim plugin to improve movement of f\/t. The basic behavior is the same, but when there are multiple targets in the current line, you are able to choose and shift to candidates of position which glow.","install_details":"More at https:\/\/github.com\/saihoooooooo\/glowshi-ft.vim","5":"More at https:\/\/github.com\/saihoooooooo\/glowshi-ft.vim","first_name":"shinya","6":"shinya","last_name":"saiho","7":"saiho","releases":[{"0":"4986","vim_version":"7.0","1":"7.0","script_version":"1.0.0","2":"1.0.0","version_comment":"Initial upload","3":"Initial upload","package":"glowshi-ft.vim.zip","4":"glowshi-ft.vim.zip","src_id":"22205","5":"22205","creation_date":"1405358331","6":"1405358331"}]},"4985":{"script_id":"4985","0":"4985","script_name":"filemaker.vim","1":"filemaker.vim","script_type":"ftplugin","2":"ftplugin","summary":"FileMaker calculation syntax highlighting and snippets","3":"FileMaker calculation syntax highlighting and snippets","description":"See https:\/\/github.com\/chivalry\/filemaker.vim for the latest version, feature details and installation instructions.","4":"See https:\/\/github.com\/chivalry\/filemaker.vim for the latest version, feature details and installation instructions.","install_details":"","5":"","first_name":"Charles","6":"Charles","last_name":"Ross","7":"Ross","releases":[{"0":"4985","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"filemaker.vim.zip","4":"filemaker.vim.zip","src_id":"22201","5":"22201","creation_date":"1405285097","6":"1405285097"}]},"4984":{"script_id":"4984","0":"4984","script_name":"PHPSyntaxCheck","1":"PHPSyntaxCheck","script_type":"ftplugin","2":"ftplugin","summary":"PHP语法检查","3":"PHP语法检查","description":"PHP语法检查插件\r\n\r\n在PHP文件保存时会自动进行语法检查，有错误会提示，没有错误不提示。\r\n\r\n*语法检查使用系统的php -l -n命令；\r\n*对非PHP文件不起作用；\r\n\r\n详见：\r\nhttp:\/\/blog.quanhz.com\/archives\/393\r\n","4":"PHP语法检查插件\r\n\r\n在PHP文件保存时会自动进行语法检查，有错误会提示，没有错误不提示。\r\n\r\n*语法检查使用系统的php -l -n命令；\r\n*对非PHP文件不起作用；\r\n\r\n详见：\r\nhttp:\/\/blog.quanhz.com\/archives\/393\r\n","install_details":"配置：\r\n可配置phpbin的路径，不配置默认使用'php'\r\nlet g:PHP_SYNTAX_CHECK_BIN = '\/apps\/php\/bin\/php'\r\n\r\n安装说明：\r\n将phpcheck.vim放入vim的plugin目录。\r\n（注：plugin目录一般在~\/.vim或vim的安装目录下）","5":"配置：\r\n可配置phpbin的路径，不配置默认使用'php'\r\nlet g:PHP_SYNTAX_CHECK_BIN = '\/apps\/php\/bin\/php'\r\n\r\n安装说明：\r\n将phpcheck.vim放入vim的plugin目录。\r\n（注：plugin目录一般在~\/.vim或vim的安装目录下）","first_name":"quan","6":"quan","last_name":"hengzhuang","7":"hengzhuang","releases":[{"0":"4984","vim_version":"7.0","1":"7.0","script_version":"1.1","2":"1.1","version_comment":"1.可配置phpbin路径；2.php执行时添加参数-n；3.只对*.php有效，用autocmd控制；","3":"1.可配置phpbin路径；2.php执行时添加参数-n；3.只对*.php有效，用autocmd控制；","package":"phpcheck.vim","4":"phpcheck.vim","src_id":"22312","5":"22312","creation_date":"1407640947","6":"1407640947"},{"0":"4984","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"phpcheck.vim","4":"phpcheck.vim","src_id":"22194","5":"22194","creation_date":"1405070268","6":"1405070268"}]},"4983":{"script_id":"4983","0":"4983","script_name":"Clighter","1":"Clighter","script_type":"utility","2":"utility","summary":"Plugin to improve c-family development environment based on Clang","3":"Plugin to improve c-family development environment based on Clang","description":"Clighter(C Lighter) is a vim plugin that integrates the libclang to improve c-family\r\ndevelopment environment, and it currently provides the following features(for c-family):\r\n\r\n* Automatically do semantic highlighting\r\n* Automatically highlight all words that with the same definition\r\n* Options to customize the colors\r\n* Experimental function to do rename-refactoring\r\n\r\n2015\/01\/23\r\nThis page will not be maintained anymore, all news, update and release will be in \r\nhttps:\/\/github.com\/bbchung\/clighter ","4":"Clighter(C Lighter) is a vim plugin that integrates the libclang to improve c-family\r\ndevelopment environment, and it currently provides the following features(for c-family):\r\n\r\n* Automatically do semantic highlighting\r\n* Automatically highlight all words that with the same definition\r\n* Options to customize the colors\r\n* Experimental function to do rename-refactoring\r\n\r\n2015\/01\/23\r\nThis page will not be maintained anymore, all news, update and release will be in \r\nhttps:\/\/github.com\/bbchung\/clighter ","install_details":"Vundle is the recommended way to install clighter. \r\n\r\nIf using Vundle: \r\nadd this line in .vimrc \r\nBundle 'bbchung\/clighter'\r\n \r\nOtherwise: \r\nExtract the .gz file into your ~\/.vim, open up vim, run helptags and then checkout :help clighter.","5":"Vundle is the recommended way to install clighter. \r\n\r\nIf using Vundle: \r\nadd this line in .vimrc \r\nBundle 'bbchung\/clighter'\r\n \r\nOtherwise: \r\nExtract the .gz file into your ~\/.vim, open up vim, run helptags and then checkout :help clighter.","first_name":"BB","6":"BB","last_name":"Chung","7":"Chung","releases":[{"0":"4983","vim_version":"7.4","1":"7.4","script_version":"4.1","2":"4.1","version_comment":"* refactoring code\r\n* fix threading issue\r\n* improve performance","3":"* refactoring code\r\n* fix threading issue\r\n* improve performance","package":"clighter.tar.bz2","4":"clighter.tar.bz2","src_id":"22642","5":"22642","creation_date":"1416903661","6":"1416903661"},{"0":"4983","vim_version":"7.4","1":"7.4","script_version":"4.0","2":"4.0","version_comment":"* Hide some options to internal variable\r\n* Better handle for compile args\r\n* Performance imrpovement\r\n* Bugfix","3":"* Hide some options to internal variable\r\n* Better handle for compile args\r\n* Performance imrpovement\r\n* Bugfix","package":"clighter.tar.bz2","4":"clighter.tar.bz2","src_id":"22620","5":"22620","creation_date":"1416231719","6":"1416231719"},{"0":"4983","vim_version":"7.4","1":"7.4","script_version":"3.00","2":"3.00","version_comment":"* fix many bugs\r\n* new rename-refactoring function","3":"* fix many bugs\r\n* new rename-refactoring function","package":"clighter.tar.gz","4":"clighter.tar.gz","src_id":"22352","5":"22352","creation_date":"1408510571","6":"1408510571"},{"0":"4983","vim_version":"7.4","1":"7.4","script_version":"2.00","2":"2.00","version_comment":"1. improve architecture for parsing\r\n2. optimize code\r\n3. better multiple buffers support","3":"1. improve architecture for parsing\r\n2. optimize code\r\n3. better multiple buffers support","package":"clighter.tar.gz","4":"clighter.tar.gz","src_id":"22258","5":"22258","creation_date":"1406221054","6":"1406221054"},{"0":"4983","vim_version":"7.3","1":"7.3","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"clighter.tar.gz","4":"clighter.tar.gz","src_id":"22191","5":"22191","creation_date":"1405048049","6":"1405048049"}]},"4982":{"script_id":"4982","0":"4982","script_name":"Buddy Challenge","1":"Buddy Challenge","script_type":"game","2":"game","summary":"Teases you on things you are unsure of","3":"Teases you on things you are unsure of","description":"Why not try my customise Vim help page:\r\nhttp:\/\/www.ezrider.co.uk\/VimTagsHelp\/\r\n\r\nThere are two versions of this script because MAC vs. Windows is slightly different the keyboard mappings.  On Windows, when you press Alt-z or Alt-i  the vim editor plays brain games with you about what's under the cursor.  On MAC it's Cmd-z or Cmd-i\r\n\r\nDemo :-\r\n\r\nhttps:\/\/www.youtube.com\/watch?v=v7F3c9Ez0xg&feature=youtu.be\r\n\r\nTip:: \r\nin Windows you can make AutoHotKey (*) press Alt-i for you when you press Middle Mouse: \r\n\r\n  MButton::\r\n  Click\r\n  Sleep,200\r\n  Send,!i\r\n  return\r\n\r\njust paste these lines into an .ahk script e.g \"mybutton.ahk\" and Right-click context menu in explorer --> Run Script when you've installed AutoHotKey. Get it from www.autohotkey.com.  AutoHotKey is a very easy to use macro style programming language.  It is superb at trapping keys, mice, and joysticks. And no I don't work for AutoHotKey","4":"Why not try my customise Vim help page:\r\nhttp:\/\/www.ezrider.co.uk\/VimTagsHelp\/\r\n\r\nThere are two versions of this script because MAC vs. Windows is slightly different the keyboard mappings.  On Windows, when you press Alt-z or Alt-i  the vim editor plays brain games with you about what's under the cursor.  On MAC it's Cmd-z or Cmd-i\r\n\r\nDemo :-\r\n\r\nhttps:\/\/www.youtube.com\/watch?v=v7F3c9Ez0xg&feature=youtu.be\r\n\r\nTip:: \r\nin Windows you can make AutoHotKey (*) press Alt-i for you when you press Middle Mouse: \r\n\r\n  MButton::\r\n  Click\r\n  Sleep,200\r\n  Send,!i\r\n  return\r\n\r\njust paste these lines into an .ahk script e.g \"mybutton.ahk\" and Right-click context menu in explorer --> Run Script when you've installed AutoHotKey. Get it from www.autohotkey.com.  AutoHotKey is a very easy to use macro style programming language.  It is superb at trapping keys, mice, and joysticks. And no I don't work for AutoHotKey","install_details":"Windows \r\n  Win7 put buddyChalWIN.vim --> \\Users\\{username}\\vimfiles\\plugin  <-- n.b singular \r\n  XP put             ^^                      --> \\Program Files\\Vim\\vimfiles\\plugin\r\nMAC\r\n  drop buddyChalMAC.vim into {home}\/.vim\/plugin\r\n\r\nMake it more personal by adding the line below to your _vimrc.  In WINDOWS _vimrc is in \\Program Files (86)\\vim\\_vimfiles,(*) on MAC it`s \/Applications\/MacVim.app\/Contents\/Resources\/vim\/gvimrc: * note in Win 7 etc.. you need to be running in Administrator mode with regards to this _vimrc file.\r\n\r\n  let buddyChallenge_yourname = \"{yourname}\" (but without {})\r\n\r\ne.g: let buddyChallenge_yourname = \"Paul\" - n.b some teases will not fully work until you do this\r\n\r\nIf you don't like it just delete the script just delete it from the plugin dir.  It doesn't leave anything behind.  If you want to be really thorough you can delete the let above buddyChallenge_... line from your _vimrc but it's not gonna do any harm leaving it there because it's unlikely there's gonna be another thing in Vim that uses a variable like this.\r\n\r\nStart being teased!  Just move your cursor over what you are not sure about and press Alt-z or Alt-i on Windows, Command-z or Command-i on the MAC\r\n\r\nEnjoy!!  :D","5":"Windows \r\n  Win7 put buddyChalWIN.vim --> \\Users\\{username}\\vimfiles\\plugin  <-- n.b singular \r\n  XP put             ^^                      --> \\Program Files\\Vim\\vimfiles\\plugin\r\nMAC\r\n  drop buddyChalMAC.vim into {home}\/.vim\/plugin\r\n\r\nMake it more personal by adding the line below to your _vimrc.  In WINDOWS _vimrc is in \\Program Files (86)\\vim\\_vimfiles,(*) on MAC it`s \/Applications\/MacVim.app\/Contents\/Resources\/vim\/gvimrc: * note in Win 7 etc.. you need to be running in Administrator mode with regards to this _vimrc file.\r\n\r\n  let buddyChallenge_yourname = \"{yourname}\" (but without {})\r\n\r\ne.g: let buddyChallenge_yourname = \"Paul\" - n.b some teases will not fully work until you do this\r\n\r\nIf you don't like it just delete the script just delete it from the plugin dir.  It doesn't leave anything behind.  If you want to be really thorough you can delete the let above buddyChallenge_... line from your _vimrc but it's not gonna do any harm leaving it there because it's unlikely there's gonna be another thing in Vim that uses a variable like this.\r\n\r\nStart being teased!  Just move your cursor over what you are not sure about and press Alt-z or Alt-i on Windows, Command-z or Command-i on the MAC\r\n\r\nEnjoy!!  :D","first_name":"Paul","6":"Paul","last_name":"Contreras","7":"Contreras","releases":[{"0":"4982","vim_version":"7.0","1":"7.0","script_version":"3.0","2":"3.0","version_comment":"same as MAC but uses Alt-z and Alt-i to tease","3":"same as MAC but uses Alt-z and Alt-i to tease","package":"buddyChalWIN.vim","4":"buddyChalWIN.vim","src_id":"22567","5":"22567","creation_date":"1414246780","6":"1414246780"},{"0":"4982","vim_version":"7.0","1":"7.0","script_version":"3.0","2":"3.0","version_comment":"added a few terms, tidied up hilighting","3":"added a few terms, tidied up hilighting","package":"buddyChalMAC.vim","4":"buddyChalMAC.vim","src_id":"22566","5":"22566","creation_date":"1414246740","6":"1414246740"},{"0":"4982","vim_version":"7.0","1":"7.0","script_version":"2.9","2":"2.9","version_comment":"same as MAC but with Alt-i and Alt-z rather than Cmd key","3":"same as MAC but with Alt-i and Alt-z rather than Cmd key","package":"buddyChalWIN.vim","4":"buddyChalWIN.vim","src_id":"22532","5":"22532","creation_date":"1413421953","6":"1413421953"},{"0":"4982","vim_version":"7.0","1":"7.0","script_version":"2.9","2":"2.9","version_comment":"added new case","3":"added new case","package":"buddyChalMAC.vim","4":"buddyChalMAC.vim","src_id":"22531","5":"22531","creation_date":"1413421886","6":"1413421886"},{"0":"4982","vim_version":"7.0","1":"7.0","script_version":"2.8","2":"2.8","version_comment":"same as Mac but using Cmd-z and Cmd-i","3":"same as Mac but using Cmd-z and Cmd-i","package":"buddyChalWIN.vim","4":"buddyChalWIN.vim","src_id":"22510","5":"22510","creation_date":"1412883769","6":"1412883769"},{"0":"4982","vim_version":"7.0","1":"7.0","script_version":"2.8","2":"2.8","version_comment":"fix bug causing Undefined Variable","3":"fix bug causing Undefined Variable","package":"buddyChalMAC.vim","4":"buddyChalMAC.vim","src_id":"22508","5":"22508","creation_date":"1412883318","6":"1412883318"},{"0":"4982","vim_version":"7.0","1":"7.0","script_version":"2.7","2":"2.7","version_comment":"same as MAC but using Cmd-z and Cmd-i","3":"same as MAC but using Cmd-z and Cmd-i","package":"buddyChalWIN.vim","4":"buddyChalWIN.vim","src_id":"22507","5":"22507","creation_date":"1412881902","6":"1412881902"},{"0":"4982","vim_version":"7.0","1":"7.0","script_version":"2.7","2":"2.7","version_comment":"corrected typo","3":"corrected typo","package":"buddyChalMAC.vim","4":"buddyChalMAC.vim","src_id":"22506","5":"22506","creation_date":"1412881871","6":"1412881871"},{"0":"4982","vim_version":"7.0","1":"7.0","script_version":"2.6","2":"2.6","version_comment":"Same as MAC but with Alt-z and Alt-i","3":"Same as MAC but with Alt-z and Alt-i","package":"buddyChalWIN.vim","4":"buddyChalWIN.vim","src_id":"22505","5":"22505","creation_date":"1412867970","6":"1412867970"},{"0":"4982","vim_version":"7.0","1":"7.0","script_version":"2.6","2":"2.6","version_comment":"added cases, improved highlight","3":"added cases, improved highlight","package":"buddyChalMAC.vim","4":"buddyChalMAC.vim","src_id":"22504","5":"22504","creation_date":"1412867930","6":"1412867930"},{"0":"4982","vim_version":"7.0","1":"7.0","script_version":"2.5","2":"2.5","version_comment":"Same as MAC but using Alt-z and Alt-i","3":"Same as MAC but using Alt-z and Alt-i","package":"buddyChalWIN.vim","4":"buddyChalWIN.vim","src_id":"22500","5":"22500","creation_date":"1412806144","6":"1412806144"},{"0":"4982","vim_version":"7.0","1":"7.0","script_version":"2.5","2":"2.5","version_comment":"added some cases, tidied grammar","3":"added some cases, tidied grammar","package":"buddyChalMAC.vim","4":"buddyChalMAC.vim","src_id":"22499","5":"22499","creation_date":"1412806064","6":"1412806064"},{"0":"4982","vim_version":"7.0","1":"7.0","script_version":"2.4","2":"2.4","version_comment":"same as MAC but using Alt-i and new Alt-z instead of MAC's Cmd-i and Cmd-z","3":"same as MAC but using Alt-i and new Alt-z instead of MAC's Cmd-i and Cmd-z","package":"buddyChalWIN.vim","4":"buddyChalWIN.vim","src_id":"22487","5":"22487","creation_date":"1412421107","6":"1412421107"},{"0":"4982","vim_version":"7.0","1":"7.0","script_version":"2.4","2":"2.4","version_comment":"small correction, new hotkey","3":"small correction, new hotkey","package":"buddyChalMAC.vim","4":"buddyChalMAC.vim","src_id":"22486","5":"22486","creation_date":"1412421014","6":"1412421014"},{"0":"4982","vim_version":"7.0","1":"7.0","script_version":"2.3","2":"2.3","version_comment":"Same as MAC but with Alt-i instead of Cmd-i","3":"Same as MAC but with Alt-i instead of Cmd-i","package":"buddyChalWIN.vim","4":"buddyChalWIN.vim","src_id":"22482","5":"22482","creation_date":"1412375802","6":"1412375802"},{"0":"4982","vim_version":"7.0","1":"7.0","script_version":"2.3","2":"2.3","version_comment":"Some minor additions","3":"Some minor additions","package":"buddyChalMAC.vim","4":"buddyChalMAC.vim","src_id":"22481","5":"22481","creation_date":"1412375759","6":"1412375759"},{"0":"4982","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"MAC version","3":"MAC version","package":"buddyChalMAC.vim","4":"buddyChalMAC.vim","src_id":"22178","5":"22178","creation_date":"1404952781","6":"1404952781"},{"0":"4982","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"buddyChalWIN.vim","4":"buddyChalWIN.vim","src_id":"22176","5":"22176","creation_date":"1404923226","6":"1404923226"}]},"4981":{"script_id":"4981","0":"4981","script_name":"elevator","1":"elevator","script_type":"utility","2":"utility","summary":"Scrollbar for VIM","3":"Scrollbar for VIM","description":"Elevator is a scollbar that utilizes VIM popup feature and works across both VIM and GVIM.\r\n\r\nGitHub: https:\/\/github.com\/noscript\/elevator.vim","4":"Elevator is a scollbar that utilizes VIM popup feature and works across both VIM and GVIM.\r\n\r\nGitHub: https:\/\/github.com\/noscript\/elevator.vim","install_details":"Extract to ~\/.vim\/","5":"Extract to ~\/.vim\/","first_name":"Sergey","6":"Sergey","last_name":"Vlasov","7":"Vlasov","releases":[{"0":"4981","vim_version":"9.0","1":"9.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"elevator-0.1.zip","4":"elevator-0.1.zip","src_id":"28526","5":"28526","creation_date":"1692161550","6":"1692161550"}]},"4980":{"script_id":"4980","0":"4980","script_name":"quick-file","1":"quick-file","script_type":"ftplugin","2":"ftplugin","summary":"to quickly jump to file in current or sub directory","3":"to quickly jump to file in current or sub directory","description":"Wonder how to locate and jump to file in vim real quick?\r\nHere is a solution. (It helps me a lot)\r\n\r\nNOTE: THIS REQUIRES VIM WITH PYTHON (but don't worry, I am sure your vim supports it, unless you are using windows, then you got to install python you yourself)\r\n\r\nhttp:\/\/github.com\/zhchang\/quick_file\r\n\r\n:QF something my-folder my-sub-folder\r\n\r\nif you have wtf\/wtf-my-folder-blahblah\/wtf-my-sub-folder-blahblahblah\/this-is-something-lol.py\r\n\r\nit will locate and open this-is-something-lol.py for editing in no time.\r\n\r\nAll you need to jump to a file is to type a fragment of the filename, and optionally specify fragment of the folder that it resides in. The plugin will jump to the closest match and start editing it.(the more fragment you give, the preciser the match will be)\r\n\r\na big productivity improver.\r\n\r\nEnjoy.","4":"Wonder how to locate and jump to file in vim real quick?\r\nHere is a solution. (It helps me a lot)\r\n\r\nNOTE: THIS REQUIRES VIM WITH PYTHON (but don't worry, I am sure your vim supports it, unless you are using windows, then you got to install python you yourself)\r\n\r\nhttp:\/\/github.com\/zhchang\/quick_file\r\n\r\n:QF something my-folder my-sub-folder\r\n\r\nif you have wtf\/wtf-my-folder-blahblah\/wtf-my-sub-folder-blahblahblah\/this-is-something-lol.py\r\n\r\nit will locate and open this-is-something-lol.py for editing in no time.\r\n\r\nAll you need to jump to a file is to type a fragment of the filename, and optionally specify fragment of the folder that it resides in. The plugin will jump to the closest match and start editing it.(the more fragment you give, the preciser the match will be)\r\n\r\na big productivity improver.\r\n\r\nEnjoy.","install_details":"unizp quick_file.zip to:\r\nubuntu\/osx: ~\/.vim\r\n","5":"unizp quick_file.zip to:\r\nubuntu\/osx: ~\/.vim\r\n","first_name":"zhao","6":"zhao","last_name":"chang","7":"chang","releases":[{"0":"4980","vim_version":"7.0","1":"7.0","script_version":"0.1.4","2":"0.1.4","version_comment":"add switch to enable and disable secondary search","3":"add switch to enable and disable secondary search","package":"quick_file.zip","4":"quick_file.zip","src_id":"23098","5":"23098","creation_date":"1427349834","6":"1427349834"},{"0":"4980","vim_version":"7.0","1":"7.0","script_version":"0.1.3","2":"0.1.3","version_comment":"avoid showing \"hit enter to continue prompt\"","3":"avoid showing \"hit enter to continue prompt\"","package":"quick_file.zip","4":"quick_file.zip","src_id":"22512","5":"22512","creation_date":"1412925880","6":"1412925880"},{"0":"4980","vim_version":"7.0","1":"7.0","script_version":"0.1.2","2":"0.1.2","version_comment":"correct error from last update","3":"correct error from last update","package":"quick_file.zip","4":"quick_file.zip","src_id":"22272","5":"22272","creation_date":"1406602603","6":"1406602603"},{"0":"4980","vim_version":"7.0","1":"7.0","script_version":"0.1.1","2":"0.1.1","version_comment":"kill find process on timeout","3":"kill find process on timeout","package":"quick_file.zip","4":"quick_file.zip","src_id":"22224","5":"22224","creation_date":"1405906815","6":"1405906815"},{"0":"4980","vim_version":"7.0","1":"7.0","script_version":"0.1.0","2":"0.1.0","version_comment":"support timeout for find ","3":"support timeout for find ","package":"quick_file.zip","4":"quick_file.zip","src_id":"22219","5":"22219","creation_date":"1405837972","6":"1405837972"}]},"4979":{"script_id":"4979","0":"4979","script_name":"Improved AnsiEsc","1":"Improved AnsiEsc","script_type":"syntax","2":"syntax","summary":"Improved AnsiEsc.vim : ansi escape sequences highlighted and concealed","3":"Improved AnsiEsc.vim : ansi escape sequences highlighted and concealed","description":"This is improved version of AnsiEsc.vim (vimscript #302).\r\n\r\nChanges\r\n\r\n *  updated to latest author's version: 13e (Dec 06, 2012)\r\n *  add support for simple ANSI sequences like \"bold\" (without defining color)\r\n *  add support for 16-color 'light' escape sequences (by Andy Berdan, merged from https:\/\/github.com\/berdandy\/AnsiEsc.vim)\r\n *  disable \\swp and \\rwp maps if g:no_plugin_maps or g:no_cecutil_maps exists\r\n *  disable DrChip\/AnsiEsc menu if g:no_drchip_menu or g:no_ansiesc_menu exists\r\n\r\nSource: https:\/\/github.com\/powerman\/vim-plugin-AnsiEsc","4":"This is improved version of AnsiEsc.vim (vimscript #302).\r\n\r\nChanges\r\n\r\n *  updated to latest author's version: 13e (Dec 06, 2012)\r\n *  add support for simple ANSI sequences like \"bold\" (without defining color)\r\n *  add support for 16-color 'light' escape sequences (by Andy Berdan, merged from https:\/\/github.com\/berdandy\/AnsiEsc.vim)\r\n *  disable \\swp and \\rwp maps if g:no_plugin_maps or g:no_cecutil_maps exists\r\n *  disable DrChip\/AnsiEsc menu if g:no_drchip_menu or g:no_ansiesc_menu exists\r\n\r\nSource: https:\/\/github.com\/powerman\/vim-plugin-AnsiEsc","install_details":"Using pathogen (recommended). \r\na) Using source: \r\n    $ git clone https:\/\/github.com\/powerman\/vim-plugin-AnsiEsc.git ~\/.vim\/bundle\/AnsiEsc\/ \r\n    $ vi \r\n    :Helptags \r\nb) Using .zip archive: \r\n    $ mkdir ~\/.vim\/bundle\/AnsiEsc\/ \r\n    $ unzip AnsiEsc.zip -d ~\/.vim\/bundle\/AnsiEsc\/ \r\n    $ vi \r\n    :Helptags \r\nc) Using  .vmb vimball: \r\n    $ mkdir ~\/.vim\/bundle\/AnsiEsc\/ \r\n    $ vi AnsiEsc.vmb \r\n    :UseVimball ~\/.vim\/bundle\/AnsiEsc \r\n    :Helptags \r\n\r\nPlain install without pathogen. \r\na) Using .zip archive: \r\n    $ unzip AnsiEsc.zip -d ~\/.vim\/ \r\n    $ vi \r\n    :helptags ~\/.vim\/doc \r\nb) Using .vmb vimball: \r\n    $ vi AnsiEsc.vmb \r\n    :so % \r\n    :helptags ~\/.vim\/doc","5":"Using pathogen (recommended). \r\na) Using source: \r\n    $ git clone https:\/\/github.com\/powerman\/vim-plugin-AnsiEsc.git ~\/.vim\/bundle\/AnsiEsc\/ \r\n    $ vi \r\n    :Helptags \r\nb) Using .zip archive: \r\n    $ mkdir ~\/.vim\/bundle\/AnsiEsc\/ \r\n    $ unzip AnsiEsc.zip -d ~\/.vim\/bundle\/AnsiEsc\/ \r\n    $ vi \r\n    :Helptags \r\nc) Using  .vmb vimball: \r\n    $ mkdir ~\/.vim\/bundle\/AnsiEsc\/ \r\n    $ vi AnsiEsc.vmb \r\n    :UseVimball ~\/.vim\/bundle\/AnsiEsc \r\n    :Helptags \r\n\r\nPlain install without pathogen. \r\na) Using .zip archive: \r\n    $ unzip AnsiEsc.zip -d ~\/.vim\/ \r\n    $ vi \r\n    :helptags ~\/.vim\/doc \r\nb) Using .vmb vimball: \r\n    $ vi AnsiEsc.vmb \r\n    :so % \r\n    :helptags ~\/.vim\/doc","first_name":"Alex","6":"Alex","last_name":"Efros","7":"Efros","releases":[{"0":"4979","vim_version":"7.0","1":"7.0","script_version":"13.4","2":"13.4","version_comment":"vimball","3":"vimball","package":"AnsiEsc.vmb","4":"AnsiEsc.vmb","src_id":"26454","5":"26454","creation_date":"1554681434","6":"1554681434"},{"0":"4979","vim_version":"7.0","1":"7.0","script_version":"13.4","2":"13.4","version_comment":"- minor fixes","3":"- minor fixes","package":"AnsiEsc.zip","4":"AnsiEsc.zip","src_id":"26453","5":"26453","creation_date":"1554681407","6":"1554681407"},{"0":"4979","vim_version":"7.0","1":"7.0","script_version":"13.3","2":"13.3","version_comment":"vimball","3":"vimball","package":"AnsiEsc.vmb","4":"AnsiEsc.vmb","src_id":"24019","5":"24019","creation_date":"1455728502","6":"1455728502"},{"0":"4979","vim_version":"7.0","1":"7.0","script_version":"13.3","2":"13.3","version_comment":"- more colors support\r\n- minor fixes","3":"- more colors support\r\n- minor fixes","package":"AnsiEsc.zip","4":"AnsiEsc.zip","src_id":"24018","5":"24018","creation_date":"1455728487","6":"1455728487"},{"0":"4979","vim_version":"7.0","1":"7.0","script_version":"13.2","2":"13.2","version_comment":"vimball","3":"vimball","package":"AnsiEsc.vmb","4":"AnsiEsc.vmb","src_id":"23546","5":"23546","creation_date":"1440423907","6":"1440423907"},{"0":"4979","vim_version":"7.0","1":"7.0","script_version":"13.2","2":"13.2","version_comment":"- updated to author's version: 13i (Apr 02, 2015)\r\n- add support for simple ANSI sequences like disable bold\/italic\/etc.\r\n- minor fixes","3":"- updated to author's version: 13i (Apr 02, 2015)\r\n- add support for simple ANSI sequences like disable bold\/italic\/etc.\r\n- minor fixes","package":"AnsiEsc.zip","4":"AnsiEsc.zip","src_id":"23545","5":"23545","creation_date":"1440423881","6":"1440423881"},{"0":"4979","vim_version":"7.0","1":"7.0","script_version":"13.1","2":"13.1","version_comment":"vimball","3":"vimball","package":"AnsiEsc.vmb","4":"AnsiEsc.vmb","src_id":"22162","5":"22162","creation_date":"1404760958","6":"1404760958"},{"0":"4979","vim_version":"7.0","1":"7.0","script_version":"13.1","2":"13.1","version_comment":"Initial upload","3":"Initial upload","package":"AnsiEsc.zip","4":"AnsiEsc.zip","src_id":"22161","5":"22161","creation_date":"1404760876","6":"1404760876"}]},"4978":{"script_id":"4978","0":"4978","script_name":"fireplace.vim","1":"fireplace.vim","script_type":"utility","2":"utility","summary":"Clojure REPL support","3":"Clojure REPL support","description":"There's a REPL in fireplace, but you probably wouldn't have noticed if I hadn't told you.  Such is the way with fireplace.vim.  By the way, this plugin is for Clojure.\r\n\r\nPartial feature list:\r\n\r\n* Transparent setup and automatic connection.\r\n* Evaluate code from the buffer or arbitrary input.\r\n* Jump to namespace or function definitions.\r\n* Wrappers for source, doc, and macroexpand.\r\n* Omnicomplete.\r\n\r\nSee http:\/\/clojure-doc.org\/articles\/tutorials\/vim_fireplace.html for help getting started.","4":"There's a REPL in fireplace, but you probably wouldn't have noticed if I hadn't told you.  Such is the way with fireplace.vim.  By the way, this plugin is for Clojure.\r\n\r\nPartial feature list:\r\n\r\n* Transparent setup and automatic connection.\r\n* Evaluate code from the buffer or arbitrary input.\r\n* Jump to namespace or function definitions.\r\n* Wrappers for source, doc, and macroexpand.\r\n* Omnicomplete.\r\n\r\nSee http:\/\/clojure-doc.org\/articles\/tutorials\/vim_fireplace.html for help getting started.","install_details":"You'll need Python.  On Windows, the Vim Python interface is required.  :h if_pyth\r\n\r\nFirst, set up https:\/\/github.com\/clojure-emacs\/cider-nrepl. (If you skip this step, fireplace.vim will make do with eval, which mostly works.)\r\n\r\nExtract in ~\/.vim (~\\vimfiles on Windows).\r\n\r\nIf you prefer an SCM install:\r\n\r\n    git clone https:\/\/tpo.pe\/vim\/fireplace.git ~\/.vim\/bundle\/fireplace","5":"You'll need Python.  On Windows, the Vim Python interface is required.  :h if_pyth\r\n\r\nFirst, set up https:\/\/github.com\/clojure-emacs\/cider-nrepl. (If you skip this step, fireplace.vim will make do with eval, which mostly works.)\r\n\r\nExtract in ~\/.vim (~\\vimfiles on Windows).\r\n\r\nIf you prefer an SCM install:\r\n\r\n    git clone https:\/\/tpo.pe\/vim\/fireplace.git ~\/.vim\/bundle\/fireplace","first_name":"Tim","6":"Tim","last_name":"Pope","7":"Pope","releases":[{"0":"4978","vim_version":"8.0","1":"8.0","script_version":"2.1","2":"2.1","version_comment":"Bug fixes and minor tweaks.","3":"Bug fixes and minor tweaks.","package":"fireplace.zip","4":"fireplace.zip","src_id":"26695","5":"26695","creation_date":"1565616166","6":"1565616166"},{"0":"4978","vim_version":"8.0","1":"8.0","script_version":"2.0","2":"2.0","version_comment":"Native job\/channel support with asynchronous API.\r\nRun tests asynchronously.\r\nProvide global :CljEval and :CljsEval commands.\r\nSoftly deprecate :Piggieback in favor of :CljEval (whatever\/cljs-repl).\r\nUse ClojureScript for cljc files if REPL initialized.\r\nReplace Nashorn ClojureScript REPL default with configuration option.\r\nProvide :SpecForm and :SpecExample.\r\nReplace automatic stacktrace retrieval with :Stacktrace.\r\nExtract bulk of plugin file to autoload file.\r\nUse explicit clojure.core in all evals for improved robustness.","3":"Native job\/channel support with asynchronous API.\r\nRun tests asynchronously.\r\nProvide global :CljEval and :CljsEval commands.\r\nSoftly deprecate :Piggieback in favor of :CljEval (whatever\/cljs-repl).\r\nUse ClojureScript for cljc files if REPL initialized.\r\nReplace Nashorn ClojureScript REPL default with configuration option.\r\nProvide :SpecForm and :SpecExample.\r\nReplace automatic stacktrace retrieval with :Stacktrace.\r\nExtract bulk of plugin file to autoload file.\r\nUse explicit clojure.core in all evals for improved robustness.","package":"fireplace.zip","4":"fireplace.zip","src_id":"26685","5":"26685","creation_date":"1564622428","6":"1564622428"},{"0":"4978","vim_version":"8.0","1":"8.0","script_version":"1.2","2":"1.2","version_comment":"Support pretty printinng.\r\nProvide code formatting on gq.\r\nGreatly improve ClojureScript support.\r\nSupport latest nREPL, Piggieback, and CIDER.\r\nFully support Python 3.\r\nAssorted bug fixes and minor enhancements.","3":"Support pretty printinng.\r\nProvide code formatting on gq.\r\nGreatly improve ClojureScript support.\r\nSupport latest nREPL, Piggieback, and CIDER.\r\nFully support Python 3.\r\nAssorted bug fixes and minor enhancements.","package":"fireplace.zip","4":"fireplace.zip","src_id":"26516","5":"26516","creation_date":"1559738603","6":"1559738603"},{"0":"4978","vim_version":"7.0","1":"7.0","script_version":"1.1","2":"1.1","version_comment":"Support cider completion, including context aware completion.\r\nUpdates for latest cider-nrepl and piggieback.\r\nUse :.RunTests or 1cpr to run test under cursor.\r\nAdd CTRL-R CTRL-F and CTRL-R CTRL-P command line maps.\r\nAdd support for boot's fake class path.\r\nFix handling of CTRL-C interrupt while evaling.\r\nNumerous minor bug fixes.","3":"Support cider completion, including context aware completion.\r\nUpdates for latest cider-nrepl and piggieback.\r\nUse :.RunTests or 1cpr to run test under cursor.\r\nAdd CTRL-R CTRL-F and CTRL-R CTRL-P command line maps.\r\nAdd support for boot's fake class path.\r\nFix handling of CTRL-C interrupt while evaling.\r\nNumerous minor bug fixes.","package":"fireplace.zip","4":"fireplace.zip","src_id":"23429","5":"23429","creation_date":"1435704708","6":"1435704708"},{"0":"4978","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"fireplace.zip","4":"fireplace.zip","src_id":"22133","5":"22133","creation_date":"1404506951","6":"1404506951"}]},"4977":{"script_id":"4977","0":"4977","script_name":"textobj-delimited","1":"textobj-delimited","script_type":"utility","2":"utility","summary":"The textobject plugin to do well with each delimited part of a string.","3":"The textobject plugin to do well with each delimited part of a string.","description":"This textobject provides the keymappings to select a part of a delimited string. id, ad, iD, aD is used in default.\r\n\r\n# ... cursor\r\n------------------------------------------------\r\n key input: did\r\n\r\n '#foo_bar_baz'   ->   '_bar_baz'\r\n------------------------------------------------\r\n key input: did\r\n\r\n 'foo_#bar_baz'   ->   'foo__baz'\r\n------------------------------------------------\r\n key input: did\r\n\r\n 'foo_bar_#baz'   ->   'foo_bar_'\r\n------------------------------------------------\r\n key input: d1id\r\n\r\n '#foo_bar_baz'   ->   '_bar_baz'\r\n------------------------------------------------\r\n key input: d2id\r\n\r\n '#foo_bar_baz'   ->   'foo__baz'\r\n------------------------------------------------\r\n key input: d3id\r\n\r\n '#foo_bar_baz'   ->   'foo_bar_'\r\n------------------------------------------------\r\n key input: dad\r\n \r\n '#foo_bar_baz'   ->   'bar_baz'\r\n------------------------------------------------\r\n key input: dad\r\n\r\n 'foo_#bar_baz'   ->   'foo_baz'\r\n------------------------------------------------\r\n key input: dad\r\n\r\n 'foo_bar_#baz'   ->   'foo_bar'\r\n------------------------------------------------\r\n key input: d1ad\r\n\r\n '#foo_bar_baz'   ->   'bar_baz'\r\n------------------------------------------------\r\n key input: d2ad\r\n\r\n '#foo_bar_baz'   ->   'foo_baz'\r\n------------------------------------------------\r\n key input: d3ad\r\n\r\n '#foo_bar_baz'   ->   'foo_bar'\r\n------------------------------------------------\r\n\r\nLatest version : https:\/\/github.com\/machakann\/vim-textobj-delimited","4":"This textobject provides the keymappings to select a part of a delimited string. id, ad, iD, aD is used in default.\r\n\r\n# ... cursor\r\n------------------------------------------------\r\n key input: did\r\n\r\n '#foo_bar_baz'   ->   '_bar_baz'\r\n------------------------------------------------\r\n key input: did\r\n\r\n 'foo_#bar_baz'   ->   'foo__baz'\r\n------------------------------------------------\r\n key input: did\r\n\r\n 'foo_bar_#baz'   ->   'foo_bar_'\r\n------------------------------------------------\r\n key input: d1id\r\n\r\n '#foo_bar_baz'   ->   '_bar_baz'\r\n------------------------------------------------\r\n key input: d2id\r\n\r\n '#foo_bar_baz'   ->   'foo__baz'\r\n------------------------------------------------\r\n key input: d3id\r\n\r\n '#foo_bar_baz'   ->   'foo_bar_'\r\n------------------------------------------------\r\n key input: dad\r\n \r\n '#foo_bar_baz'   ->   'bar_baz'\r\n------------------------------------------------\r\n key input: dad\r\n\r\n 'foo_#bar_baz'   ->   'foo_baz'\r\n------------------------------------------------\r\n key input: dad\r\n\r\n 'foo_bar_#baz'   ->   'foo_bar'\r\n------------------------------------------------\r\n key input: d1ad\r\n\r\n '#foo_bar_baz'   ->   'bar_baz'\r\n------------------------------------------------\r\n key input: d2ad\r\n\r\n '#foo_bar_baz'   ->   'foo_baz'\r\n------------------------------------------------\r\n key input: d3ad\r\n\r\n '#foo_bar_baz'   ->   'foo_bar'\r\n------------------------------------------------\r\n\r\nLatest version : https:\/\/github.com\/machakann\/vim-textobj-delimited","install_details":"Unzip and just put all folders in your ~\/.vim.","5":"Unzip and just put all folders in your ~\/.vim.","first_name":"Masaaki","6":"Masaaki","last_name":"Nakamura","7":"Nakamura","releases":[{"0":"4977","vim_version":"7.4","1":"7.4","script_version":"1.1.0","2":"1.1.0","version_comment":"*   Bug fixes.\r\n*   Change the treatment for ended delimiters.\r\n*   Update documents.","3":"*   Bug fixes.\r\n*   Change the treatment for ended delimiters.\r\n*   Update documents.","package":"textobj-delimited.zip","4":"textobj-delimited.zip","src_id":"22340","5":"22340","creation_date":"1408291577","6":"1408291577"},{"0":"4977","vim_version":"7.4","1":"7.4","script_version":"1.0.2","2":"1.0.2","version_comment":"* Fix up a bug on selection option.\r\n* Fix up a bug on the charm to prevent multiple load.","3":"* Fix up a bug on selection option.\r\n* Fix up a bug on the charm to prevent multiple load.","package":"textobj-delimited.zip","4":"textobj-delimited.zip","src_id":"22253","5":"22253","creation_date":"1406116727","6":"1406116727"},{"0":"4977","vim_version":"7.4","1":"7.4","script_version":"1.0.0","2":"1.0.0","version_comment":"Initial upload","3":"Initial upload","package":"textobj-delimited.zip","4":"textobj-delimited.zip","src_id":"22132","5":"22132","creation_date":"1404489799","6":"1404489799"}]},"4976":{"script_id":"4976","0":"4976","script_name":"vim-gista","1":"vim-gista","script_type":"utility","2":"utility","summary":"An alternative gist.vim, vim plugin which manipulate gists in Vim","3":"An alternative gist.vim, vim plugin which manipulate gists in Vim","description":"vim-gista is a plugin for manipulating Gist in Vim. It provide the following features:\r\n\r\n - List gists of a particular lookup\r\n - List commits of a gist\r\n - Open a gist as a JSON file\r\n - Open a file of a gist\r\n - Post a content of the current buffer\r\n - Patch a content of the current buffer to a gist\r\n - Rename files in a gist\r\n - Remove files in a gist\r\n - Delete a gist\r\n - Star\/Unstar a gist\r\n - Folk a gist\r\n\r\nDeveloped on https:\/\/github.com\/lambdalisue\/vim-gista","4":"vim-gista is a plugin for manipulating Gist in Vim. It provide the following features:\r\n\r\n - List gists of a particular lookup\r\n - List commits of a gist\r\n - Open a gist as a JSON file\r\n - Open a file of a gist\r\n - Post a content of the current buffer\r\n - Patch a content of the current buffer to a gist\r\n - Rename files in a gist\r\n - Remove files in a gist\r\n - Delete a gist\r\n - Star\/Unstar a gist\r\n - Folk a gist\r\n\r\nDeveloped on https:\/\/github.com\/lambdalisue\/vim-gista","install_details":"\" vim-plug\r\nPlug 'lambdalisue\/vim-gista'\r\n\r\n\" neobundle.vim\r\nNeoBundle 'lambdalisue\/vim-gista'\r\n\r\n\" neobundle.vim (Lazy)\r\nNeoBundleLazy 'lambdalisue\/vim-gista', {\r\n    \\ 'on_cmd': ['Gista']\r\n    \\ 'on_func': 'gista#'\r\n    \\}\r\n\r\n\" Or install the repository into your runtimepath manually.","5":"\" vim-plug\r\nPlug 'lambdalisue\/vim-gista'\r\n\r\n\" neobundle.vim\r\nNeoBundle 'lambdalisue\/vim-gista'\r\n\r\n\" neobundle.vim (Lazy)\r\nNeoBundleLazy 'lambdalisue\/vim-gista', {\r\n    \\ 'on_cmd': ['Gista']\r\n    \\ 'on_func': 'gista#'\r\n    \\}\r\n\r\n\" Or install the repository into your runtimepath manually.","first_name":"Alisue","6":"Alisue","last_name":"Lambda","7":"Lambda","releases":[{"0":"4976","vim_version":"7.4","1":"7.4","script_version":"v2.5.0","2":"v2.5.0","version_comment":"- Support Neovim\r\n- Add --stay option to post\/patch","3":"- Support Neovim\r\n- Add --stay option to post\/patch","package":"vim-gista-v2.5.0.zip","4":"vim-gista-v2.5.0.zip","src_id":"24977","5":"24977","creation_date":"1487572105","6":"1487572105"},{"0":"4976","vim_version":"7.4","1":"7.4","script_version":"v2.3.3","2":"v2.3.3","version_comment":"- Improve documents (v2.3.1)\r\n- Refactoring codes (v2.3.1)\r\n- Support neovim (v2.3.2)\r\n- Support BufReadCmd( v2.3.2)\r\n- Support 32 bit GistID (v2.3.3)","3":"- Improve documents (v2.3.1)\r\n- Refactoring codes (v2.3.1)\r\n- Support neovim (v2.3.2)\r\n- Support BufReadCmd( v2.3.2)\r\n- Support 32 bit GistID (v2.3.3)","package":"vim-gista-v2.3.3.zip","4":"vim-gista-v2.3.3.zip","src_id":"24167","5":"24167","creation_date":"1460322166","6":"1460322166"},{"0":"4976","vim_version":"7.4","1":"7.4","script_version":"2.3.0","2":"2.3.0","version_comment":"- Get GitHub username from git config github.user\r\n- Add short options (alias)\r\n- Add GistaXXX autocmds for :Gista xxx\r\n- Fix several bugs","3":"- Get GitHub username from git config github.user\r\n- Add short options (alias)\r\n- Add GistaXXX autocmds for :Gista xxx\r\n- Fix several bugs","package":"vim-gista-2.3.0.zip","4":"vim-gista-2.3.0.zip","src_id":"23947","5":"23947","creation_date":"1453730319","6":"1453730319"},{"0":"4976","vim_version":"7.4","1":"7.4","script_version":"2.2.0","2":"2.2.0","version_comment":"- Refactoring code\r\n- Fix critical issue on +python","3":"- Refactoring code\r\n- Fix critical issue on +python","package":"vim-gista-2.2.0.zip","4":"vim-gista-2.2.0.zip","src_id":"23934","5":"23934","creation_date":"1453302300","6":"1453302300"},{"0":"4976","vim_version":"7.4","1":"7.4","script_version":"2.1.0","2":"2.1.0","version_comment":"- Use URI like bufname instead of comma separated one (Tue Jan 19 10:20:00 2016 +0900) [7275b81](https:\/\/github.com\/lambdalisue\/vim-gista\/commit\/7275b814bdb113418c630d490253115b15c0ed56)\r\n- Fix Gista logout (Tue Jan 19 20:46:28 2016 +0900) [8bac83f](https:\/\/github.com\/lambdalisue\/vim-gista\/commit\/8bac83f45c6b6c9a78c6a83b8e9ea157af5d8773)\r\n- Fix temporal authorization and improve Gista status (Tue Jan 19 20:56:38 2016 +0900) [8c32b7a](https:\/\/github.com\/lambdalisue\/vim-gista\/commit\/8c32b7ab7dae76d688daeb841d1fe12292705ad1)\r\n- Merge pull request #60 from lambdalisue\/fix\/gista_filenames (Tue Jan 19 21:44:40 2016 +0900) [6ee3036](https:\/\/github.com\/lambdalisue\/vim-gista\/commit\/6ee3036852bfb27fb2b503c0e491876713f44e99)\r\n- Bump version (Tue Jan 19 21:45:59 2016 +0900) [39cd521](https:\/\/github.com\/lambdalisue\/vim-gista\/commit\/39cd52179224923f41da17720c57270d2f002e69)\r\n- Update changelog (Tue Jan 19 21:46:47 2016 +0900) [9396538](https:\/\/github.com\/lambdalisue\/vim-gista\/commit\/9396538aa03b2d1b763a883067e5aba86f7c04d2)\r\n\r\n\r\n","3":"- Use URI like bufname instead of comma separated one (Tue Jan 19 10:20:00 2016 +0900) [7275b81](https:\/\/github.com\/lambdalisue\/vim-gista\/commit\/7275b814bdb113418c630d490253115b15c0ed56)\r\n- Fix Gista logout (Tue Jan 19 20:46:28 2016 +0900) [8bac83f](https:\/\/github.com\/lambdalisue\/vim-gista\/commit\/8bac83f45c6b6c9a78c6a83b8e9ea157af5d8773)\r\n- Fix temporal authorization and improve Gista status (Tue Jan 19 20:56:38 2016 +0900) [8c32b7a](https:\/\/github.com\/lambdalisue\/vim-gista\/commit\/8c32b7ab7dae76d688daeb841d1fe12292705ad1)\r\n- Merge pull request #60 from lambdalisue\/fix\/gista_filenames (Tue Jan 19 21:44:40 2016 +0900) [6ee3036](https:\/\/github.com\/lambdalisue\/vim-gista\/commit\/6ee3036852bfb27fb2b503c0e491876713f44e99)\r\n- Bump version (Tue Jan 19 21:45:59 2016 +0900) [39cd521](https:\/\/github.com\/lambdalisue\/vim-gista\/commit\/39cd52179224923f41da17720c57270d2f002e69)\r\n- Update changelog (Tue Jan 19 21:46:47 2016 +0900) [9396538](https:\/\/github.com\/lambdalisue\/vim-gista\/commit\/9396538aa03b2d1b763a883067e5aba86f7c04d2)\r\n\r\n\r\n","package":"vim-gista-2.1.0.zip","4":"vim-gista-2.1.0.zip","src_id":"23930","5":"23930","creation_date":"1453207831","6":"1453207831"},{"0":"4976","vim_version":"7.4","1":"7.4","script_version":"2.0.4","2":"2.0.4","version_comment":"- Fix #58: SSL certification error (Mon Jan 18 21:49:46 2016 +0900) [f18f08d](https:\/\/github.com\/lambdalisue\/vim-gista\/commit\/f18f08de9df737b7de45ac08c507a8456f7fc0f0)\r\n- Update Web.API.GitHub (Mon Jan 18 23:56:01 2016 +0900) [0ddac64](https:\/\/github.com\/lambdalisue\/vim-gista\/commit\/0ddac64f274a2a5bf53fa6a61e09c52bdfeefc4c)\r\n- Bump version (Tue Jan 19 00:02:57 2016 +0900) [d2e574a](https:\/\/github.com\/lambdalisue\/vim-gista\/commit\/d2e574a17391239af13d87719391311564f2a1cb)\r\n- Update changelog (Tue Jan 19 00:09:34 2016 +0900) [65819e3](https:\/\/github.com\/lambdalisue\/vim-gista\/commit\/65819e3e27d0fe7b33335d2e8832095018d231c0)","3":"- Fix #58: SSL certification error (Mon Jan 18 21:49:46 2016 +0900) [f18f08d](https:\/\/github.com\/lambdalisue\/vim-gista\/commit\/f18f08de9df737b7de45ac08c507a8456f7fc0f0)\r\n- Update Web.API.GitHub (Mon Jan 18 23:56:01 2016 +0900) [0ddac64](https:\/\/github.com\/lambdalisue\/vim-gista\/commit\/0ddac64f274a2a5bf53fa6a61e09c52bdfeefc4c)\r\n- Bump version (Tue Jan 19 00:02:57 2016 +0900) [d2e574a](https:\/\/github.com\/lambdalisue\/vim-gista\/commit\/d2e574a17391239af13d87719391311564f2a1cb)\r\n- Update changelog (Tue Jan 19 00:09:34 2016 +0900) [65819e3](https:\/\/github.com\/lambdalisue\/vim-gista\/commit\/65819e3e27d0fe7b33335d2e8832095018d231c0)","package":"vim-gista-2.0.4.zip","4":"vim-gista-2.0.4.zip","src_id":"23928","5":"23928","creation_date":"1453129902","6":"1453129902"},{"0":"4976","vim_version":"7.4","1":"7.4","script_version":"2.0.3","2":"2.0.3","version_comment":"\r\n    Fix syntax highlight issue (Add 'default') (Mon Jan 18 00:50:50 2016 +0900) 781dba0\r\n    Semantic fix (Mon Jan 18 00:55:54 2016 +0900) 0529b6e\r\n    Suppress 'no such autocmd' issue (Mon Jan 18 20:12:39 2016 +0900) 5f2d11b\r\n    Fix Gista post\/patch filename assign bug (Mon Jan 18 20:42:55 2016 +0900) ecb198d\r\n    Fix keepalt issue (Mon Jan 18 20:54:18 2016 +0900) bedc229\r\n    Bump version (Mon Jan 18 20:58:47 2016 +0900) f3ea722\r\n\r\n","3":"\r\n    Fix syntax highlight issue (Add 'default') (Mon Jan 18 00:50:50 2016 +0900) 781dba0\r\n    Semantic fix (Mon Jan 18 00:55:54 2016 +0900) 0529b6e\r\n    Suppress 'no such autocmd' issue (Mon Jan 18 20:12:39 2016 +0900) 5f2d11b\r\n    Fix Gista post\/patch filename assign bug (Mon Jan 18 20:42:55 2016 +0900) ecb198d\r\n    Fix keepalt issue (Mon Jan 18 20:54:18 2016 +0900) bedc229\r\n    Bump version (Mon Jan 18 20:58:47 2016 +0900) f3ea722\r\n\r\n","package":"vim-gista-2.0.3.zip","4":"vim-gista-2.0.3.zip","src_id":"23927","5":"23927","creation_date":"1453121144","6":"1453121144"},{"0":"4976","vim_version":"7.4","1":"7.4","script_version":"2.0.2","2":"2.0.2","version_comment":"Fix an username option on Gista login\r\n\r\nGista login --username={username} --> Gista login {username} (follow the document)","3":"Fix an username option on Gista login\r\n\r\nGista login --username={username} --> Gista login {username} (follow the document)","package":"vim-gista-2.0.2.zip","4":"vim-gista-2.0.2.zip","src_id":"23922","5":"23922","creation_date":"1453045429","6":"1453045429"},{"0":"4976","vim_version":"7.4","1":"7.4","script_version":"2.0.1","2":"2.0.1","version_comment":"Fix critical issues related on :write command\r\n\r\n- Fix wrong filename re-apply in ':w' or ':Gista patch'\r\n- Fix ':w' to save content changes (Close #56)\r\n\r\n","3":"Fix critical issues related on :write command\r\n\r\n- Fix wrong filename re-apply in ':w' or ':Gista patch'\r\n- Fix ':w' to save content changes (Close #56)\r\n\r\n","package":"vim-gista-2.0.1.zip","4":"vim-gista-2.0.1.zip","src_id":"23921","5":"23921","creation_date":"1453043483","6":"1453043483"},{"0":"4976","vim_version":"7.4","1":"7.4","script_version":"2.0.0","2":"2.0.0","version_comment":"Re-created and no backward compatibility exists.\r\nThe following new features are available\r\n\r\n- Support additional API (e.g. GitHub & GitHub Enterpriese)\r\n- Support multi account\r\n- Support temporal authorization\r\n- Fast fetching by multi-thread (+python\/+python3 is required)\r\n- List commits of a gist\r\n- Support Shougo\/unite.vim for listing (vim-gista-unite)\r\n- Support ctrlpvim\/ctrlp.vim for listing (vim-gista-ctrlp)","3":"Re-created and no backward compatibility exists.\r\nThe following new features are available\r\n\r\n- Support additional API (e.g. GitHub & GitHub Enterpriese)\r\n- Support multi account\r\n- Support temporal authorization\r\n- Fast fetching by multi-thread (+python\/+python3 is required)\r\n- List commits of a gist\r\n- Support Shougo\/unite.vim for listing (vim-gista-unite)\r\n- Support ctrlpvim\/ctrlp.vim for listing (vim-gista-ctrlp)","package":"vim-gista-2.0.0.zip","4":"vim-gista-2.0.0.zip","src_id":"23913","5":"23913","creation_date":"1452920991","6":"1452920991"},{"0":"4976","vim_version":"7.3","1":"7.3","script_version":"0.1.15","2":"0.1.15","version_comment":"v0.1.8\r\n\r\n6e5e499 \u00e2\u0080\u00a2 Add auto yank featrue (Sat Jul 5 17:32:11 2014 +0900)\r\na576c0a \u00e2\u0080\u00a2 Bump version (Sat Jul 5 17:35:50 2014 +0900)\r\ne057e43 \u00e2\u0080\u00a2 Add\/Change highlights in gista:list and unite (Mon Jul 7 12:44:28 2014 +0900)\r\n0757786 \u00e2\u0080\u00a2 Bump version (Mon Jul 7 12:46:57 2014 +0900)\r\nv0.1.9\r\n\r\n09b2c11 \u00e2\u0080\u00a2 Add Vim 7.3 support (Mon Jul 7 14:45:50 2014 +0900)\r\n072bb6b \u00e2\u0080\u00a2 Bump version (Mon Jul 7 14:46:37 2014 +0900)\r\nv0.1.10\r\n\r\n11d4893 \u00e2\u0080\u00a2 Support Vim 7.3 (Mon Jul 7 14:53:11 2014 +0900)\r\n738df8d \u00e2\u0080\u00a2 Merge branch 'vim703_support' (Mon Jul 7 14:54:15 2014 +0900)\r\n5d9c61c \u00e2\u0080\u00a2 Bump version (Mon Jul 7 14:55:14 2014 +0900)\r\nv0.1.11\r\n\r\n672face \u00e2\u0080\u00a2 Support 'anonymous_mode' (Mon Jul 7 15:26:53 2014 +0900)\r\na2ab173 \u00e2\u0080\u00a2 Add document and Bump version (Mon Jul 7 15:29:44 2014 +0900)\r\nv0.1.12\r\n\r\nb7b9626 \u00e2\u0080\u00a2 Fixed #28 (Mon Jul 7 17:40:17 2014 +0900)\r\n57a58c3 \u00e2\u0080\u00a2 Cancel 'rename' action for same filename (Mon Jul 7 17:41:43 2014 +0900)\r\ne16e064 \u00e2\u0080\u00a2 Bump version (Mon Jul 7 18:05:26 2014 +0900)\r\nv0.1.13\r\n\r\n023cd8c \u00e2\u0080\u00a2 Add 'disable_python_client' option (Mon Jul 7 17:36:07 2014 +0900)\r\n5d5c521 \u00e2\u0080\u00a2 Bump version (Mon Jul 7 18:09:42 2014 +0900)\r\nv0.1.14\r\n\r\n0dfa117 \u00e2\u0080\u00a2 Fixed #29 (Mon Jul 7 18:32:12 2014 +0900)\r\ned96f7f \u00e2\u0080\u00a2 Fixed #30 (Mon Jul 7 18:41:08 2014 +0900)\r\nf8dad73 \u00e2\u0080\u00a2 Merge branch 'issue30' (Mon Jul 7 18:41:26 2014 +0900)\r\n7418491 \u00e2\u0080\u00a2 Bump version (Mon Jul 7 18:41:50 2014 +0900)\r\nv0.1.15\r\n\r\n85be809 \u00e2\u0080\u00a2 Add a way to reopen a gist without using cache (Mon Jul 7 20:32:56 2014 +0900)\r\n02ddd7e \u00e2\u0080\u00a2 Bump version (Mon Jul 7 20:33:28 2014 +0900)","3":"v0.1.8\r\n\r\n6e5e499 \u00e2\u0080\u00a2 Add auto yank featrue (Sat Jul 5 17:32:11 2014 +0900)\r\na576c0a \u00e2\u0080\u00a2 Bump version (Sat Jul 5 17:35:50 2014 +0900)\r\ne057e43 \u00e2\u0080\u00a2 Add\/Change highlights in gista:list and unite (Mon Jul 7 12:44:28 2014 +0900)\r\n0757786 \u00e2\u0080\u00a2 Bump version (Mon Jul 7 12:46:57 2014 +0900)\r\nv0.1.9\r\n\r\n09b2c11 \u00e2\u0080\u00a2 Add Vim 7.3 support (Mon Jul 7 14:45:50 2014 +0900)\r\n072bb6b \u00e2\u0080\u00a2 Bump version (Mon Jul 7 14:46:37 2014 +0900)\r\nv0.1.10\r\n\r\n11d4893 \u00e2\u0080\u00a2 Support Vim 7.3 (Mon Jul 7 14:53:11 2014 +0900)\r\n738df8d \u00e2\u0080\u00a2 Merge branch 'vim703_support' (Mon Jul 7 14:54:15 2014 +0900)\r\n5d9c61c \u00e2\u0080\u00a2 Bump version (Mon Jul 7 14:55:14 2014 +0900)\r\nv0.1.11\r\n\r\n672face \u00e2\u0080\u00a2 Support 'anonymous_mode' (Mon Jul 7 15:26:53 2014 +0900)\r\na2ab173 \u00e2\u0080\u00a2 Add document and Bump version (Mon Jul 7 15:29:44 2014 +0900)\r\nv0.1.12\r\n\r\nb7b9626 \u00e2\u0080\u00a2 Fixed #28 (Mon Jul 7 17:40:17 2014 +0900)\r\n57a58c3 \u00e2\u0080\u00a2 Cancel 'rename' action for same filename (Mon Jul 7 17:41:43 2014 +0900)\r\ne16e064 \u00e2\u0080\u00a2 Bump version (Mon Jul 7 18:05:26 2014 +0900)\r\nv0.1.13\r\n\r\n023cd8c \u00e2\u0080\u00a2 Add 'disable_python_client' option (Mon Jul 7 17:36:07 2014 +0900)\r\n5d5c521 \u00e2\u0080\u00a2 Bump version (Mon Jul 7 18:09:42 2014 +0900)\r\nv0.1.14\r\n\r\n0dfa117 \u00e2\u0080\u00a2 Fixed #29 (Mon Jul 7 18:32:12 2014 +0900)\r\ned96f7f \u00e2\u0080\u00a2 Fixed #30 (Mon Jul 7 18:41:08 2014 +0900)\r\nf8dad73 \u00e2\u0080\u00a2 Merge branch 'issue30' (Mon Jul 7 18:41:26 2014 +0900)\r\n7418491 \u00e2\u0080\u00a2 Bump version (Mon Jul 7 18:41:50 2014 +0900)\r\nv0.1.15\r\n\r\n85be809 \u00e2\u0080\u00a2 Add a way to reopen a gist without using cache (Mon Jul 7 20:32:56 2014 +0900)\r\n02ddd7e \u00e2\u0080\u00a2 Bump version (Mon Jul 7 20:33:28 2014 +0900)","package":"vim-gista-0.1.15.zip","4":"vim-gista-0.1.15.zip","src_id":"22155","5":"22155","creation_date":"1404736282","6":"1404736282"},{"0":"4976","vim_version":"7.4","1":"7.4","script_version":"0.1.6","2":"0.1.6","version_comment":"Initial upload","3":"Initial upload","package":"vim-gista-0.1.6.zip","4":"vim-gista-0.1.6.zip","src_id":"22130","5":"22130","creation_date":"1404404500","6":"1404404500"}]},"4975":{"script_id":"4975","0":"4975","script_name":"unite-linephrase","1":"unite-linephrase","script_type":"utility","2":"utility","summary":"A unite source for set phrases","3":"A unite source for set phrases","description":"unite-linephrase is a Unite.vim plugin for listing, searching, manipulating set phrases. It is developed for one liner set phrases (linephrases), something like:\r\n\r\nPyPI classifier entries\r\nMarkdown styled hyperlinks, images, whatever\r\nEmail addresses\r\nThis plugin use files for generating candidates. Basically each lines in the file are translated to source candidates. Thus even Vim beginners can easily make them own sources for set phrases, it is quite good for users who are too bothered to create original sources as well :-p\r\n\r\nGitHub: https:\/\/github.com\/lambdalisue\/unite-linephrase","4":"unite-linephrase is a Unite.vim plugin for listing, searching, manipulating set phrases. It is developed for one liner set phrases (linephrases), something like:\r\n\r\nPyPI classifier entries\r\nMarkdown styled hyperlinks, images, whatever\r\nEmail addresses\r\nThis plugin use files for generating candidates. Basically each lines in the file are translated to source candidates. Thus even Vim beginners can easily make them own sources for set phrases, it is quite good for users who are too bothered to create original sources as well :-p\r\n\r\nGitHub: https:\/\/github.com\/lambdalisue\/unite-linephrase","install_details":"","5":"","first_name":"Alisue","6":"Alisue","last_name":"Lambda","7":"Lambda","releases":[{"0":"4975","vim_version":"7.4","1":"7.4","script_version":"0.1.0","2":"0.1.0","version_comment":"Initial upload","3":"Initial upload","package":"unite-linephrase-0.1.0.zip","4":"unite-linephrase-0.1.0.zip","src_id":"22129","5":"22129","creation_date":"1404404356","6":"1404404356"}]},"4974":{"script_id":"4974","0":"4974","script_name":"YAJS: Yet Another JavaScript Syntax","1":"YAJS: Yet Another JavaScript Syntax","script_type":"syntax","2":"syntax","summary":"Yet Another JavaScript Syntax file for Vim","3":"Yet Another JavaScript Syntax file for Vim","description":"Yet Another JavaScript Syntax file for Vim. Key differences:\r\n\r\n *  Use 'javascript' as group name's prefix, not 'javaScript' or 'JavaScript'. Works great with SyntaxComplete.\r\n *  Recognize Web API and DOM keywords. Keep increase.\r\n *  Works perfect with javascript-libraries-syntax.vim\r\n *  Remove old, unused syntax definitions.\r\n *  Support several ES6 new syntax, ex: arrow function =>.\r\n\r\nGitHub repo: https:\/\/github.com\/othree\/yajs.vim","4":"Yet Another JavaScript Syntax file for Vim. Key differences:\r\n\r\n *  Use 'javascript' as group name's prefix, not 'javaScript' or 'JavaScript'. Works great with SyntaxComplete.\r\n *  Recognize Web API and DOM keywords. Keep increase.\r\n *  Works perfect with javascript-libraries-syntax.vim\r\n *  Remove old, unused syntax definitions.\r\n *  Support several ES6 new syntax, ex: arrow function =>.\r\n\r\nGitHub repo: https:\/\/github.com\/othree\/yajs.vim","install_details":"","5":"","first_name":"wei ko","6":"wei ko","last_name":"kao","7":"kao","releases":[{"0":"4974","vim_version":"7.0","1":"7.0","script_version":"1.5","2":"1.5","version_comment":"1.5\r\n\r\nLots of bug fix","3":"1.5\r\n\r\nLots of bug fix","package":"yajs.vim-1.5.vmb","4":"yajs.vim-1.5.vmb","src_id":"23849","5":"23849","creation_date":"1451549037","6":"1451549037"},{"0":"4974","vim_version":"7.0","1":"7.0","script_version":"1.4","2":"1.4","version_comment":"* Better Array Comprehesion support\r\n* Better Template highlight\r\n* AngularJS JSDoc module\r\n* Fix object literal syntax\r\n* Don't break vim-jsx","3":"* Better Array Comprehesion support\r\n* Better Template highlight\r\n* AngularJS JSDoc module\r\n* Fix object literal syntax\r\n* Don't break vim-jsx","package":"yajs.vim-1.4.vmb","4":"yajs.vim-1.4.vmb","src_id":"23103","5":"23103","creation_date":"1427696968","6":"1427696968"},{"0":"4974","vim_version":"7.0","1":"7.0","script_version":"1.3.1","2":"1.3.1","version_comment":"- Add ServiceWorker\r\n- Some code refactor\r\n- Lots of bug fix\r\n  - Nesting block\r\n  - Multiline template string\r\n  - Negative integer\r\n  - Syntax not load second time\r\n  - Comment in object literal\r\n  - Reserved word not in all string type ","3":"- Add ServiceWorker\r\n- Some code refactor\r\n- Lots of bug fix\r\n  - Nesting block\r\n  - Multiline template string\r\n  - Negative integer\r\n  - Syntax not load second time\r\n  - Comment in object literal\r\n  - Reserved word not in all string type ","package":"yajs.vim-1.3.1.vmb","4":"yajs.vim-1.3.1.vmb","src_id":"22922","5":"22922","creation_date":"1424188984","6":"1424188984"},{"0":"4974","vim_version":"7.0","1":"7.0","script_version":"1.2","2":"1.2","version_comment":"- Embed JS in html\/erb\/haml\r\n- fetch\r\n- sendBeacon\r\n- Improve init perfomance","3":"- Embed JS in html\/erb\/haml\r\n- fetch\r\n- sendBeacon\r\n- Improve init perfomance","package":"yajs.vim-1.2.vmb","4":"yajs.vim-1.2.vmb","src_id":"22660","5":"22660","creation_date":"1417491966","6":"1417491966"},{"0":"4974","vim_version":"7.0","1":"7.0","script_version":"1.1","2":"1.1","version_comment":"* JSDoc 3\r\n* ECMA-402: Intl\r\n* async, await\r\n* Event name\r\n* String bugs fix\r\n* Minor bug fix","3":"* JSDoc 3\r\n* ECMA-402: Intl\r\n* async, await\r\n* Event name\r\n* String bugs fix\r\n* Minor bug fix","package":"yajs.vim-1.1.0.vmb","4":"yajs.vim-1.1.0.vmb","src_id":"22589","5":"22589","creation_date":"1414745199","6":"1414745199"},{"0":"4974","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Stable release","3":"Stable release","package":"yajs.vim-1.0.0.vba","4":"yajs.vim-1.0.0.vba","src_id":"22204","5":"22204","creation_date":"1405322248","6":"1405322248"},{"0":"4974","vim_version":"7.0","1":"7.0","script_version":"0.99","2":"0.99","version_comment":"Initial upload","3":"Initial upload","package":"yajs.vim-0.9.9.vba","4":"yajs.vim-0.9.9.vba","src_id":"22121","5":"22121","creation_date":"1404368461","6":"1404368461"}]},"4973":{"script_id":"4973","0":"4973","script_name":"erlang-motions.vim","1":"erlang-motions.vim","script_type":"ftplugin","2":"ftplugin","summary":"Motions and text objects for erlang","3":"Motions and text objects for erlang","description":"Motions\r\n\r\n    ]] go to next function declaration\r\n    [[ previous function declaration\r\n\r\n    ]m next function clause\r\n    [m previous function clause\r\n\r\n    And more: ]M, [M, ][, [] go to end of next\/previous clause\/declaration.\r\n\r\n    Each motion can be prefixed with a count.\r\n\r\nText objects\r\n\r\n    im, am inside\/around function clause\r\n\r\n    iM, aM inside\/around function declaration\r\n\r\nTo remind yourself what's an erlang function clause\/declaration:\r\nhttp:\/\/erlang.org\/doc\/reference_manual\/functions.html\r\n\r\nAll these additions are consistent with vim's default behaviour (but vim's default behaviour doesn't work on erlang).\r\n\r\nFor a screenshot and better docs, and latest version check out GitHub:\r\nhttps:\/\/github.com\/edkolev\/erlang-motions.vim","4":"Motions\r\n\r\n    ]] go to next function declaration\r\n    [[ previous function declaration\r\n\r\n    ]m next function clause\r\n    [m previous function clause\r\n\r\n    And more: ]M, [M, ][, [] go to end of next\/previous clause\/declaration.\r\n\r\n    Each motion can be prefixed with a count.\r\n\r\nText objects\r\n\r\n    im, am inside\/around function clause\r\n\r\n    iM, aM inside\/around function declaration\r\n\r\nTo remind yourself what's an erlang function clause\/declaration:\r\nhttp:\/\/erlang.org\/doc\/reference_manual\/functions.html\r\n\r\nAll these additions are consistent with vim's default behaviour (but vim's default behaviour doesn't work on erlang).\r\n\r\nFor a screenshot and better docs, and latest version check out GitHub:\r\nhttps:\/\/github.com\/edkolev\/erlang-motions.vim","install_details":"Extract in ~\/.vim (~\\vimfiles on Windows)\r\nOr even better, grab it from https:\/\/github.com\/edkolev\/erlang-motions.vim","5":"Extract in ~\/.vim (~\\vimfiles on Windows)\r\nOr even better, grab it from https:\/\/github.com\/edkolev\/erlang-motions.vim","first_name":"Evgeni","6":"Evgeni","last_name":"Kolev","7":"Kolev","releases":[{"0":"4973","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"erlang-motions.zip","4":"erlang-motions.zip","src_id":"22116","5":"22116","creation_date":"1404233328","6":"1404233328"}]},"4972":{"script_id":"4972","0":"4972","script_name":"vim-fanfou","1":"vim-fanfou","script_type":"utility","2":"utility","summary":"Fanfou client for VIM","3":"Fanfou client for VIM","description":"* Vim-Fanfou\r\nVim-Fanfou = VIM + Fanfou ( http:\/\/fanfou.com\/ ).\r\nIt allows you to post to status and view Fanfou timeline.\r\n\r\nJust like Fanfou is a Twitter clone. \r\nVim-Fanfou is a TwitVim ( https:\/\/github.com\/vim-scripts\/TwitVim ) clone.\r\n\r\n* Vim-Fanfou links\r\n - Source code:  https:\/\/github.com\/xiongjia\/vim-fanfou\r\n - Releases:     https:\/\/github.com\/xiongjia\/vim-fanfou\/releases\r\n - Vim Script:   http:\/\/www.vim.org\/scripts\/script.php?script_id=4972\r\n - Project Page: http:\/\/xiongjia.github.io\/vim-fanfou\/\r\n\r\n* Installation\r\n - Requirements:\r\n   Vim-Fanfou is based on Python 2.7(+) & VIM 7+. Please check your VIM before you install Vim-Fanfou.\r\n\r\n - Steps to install:\r\n    Copy the \"plugin\" folder to your VIM \"plugin\" folder.\r\n\r\n* Usage\r\n  ** Setup & Login\r\n   - To enable HTTP Proxy: Add below line to your .vimrc.\r\n      let g:fanfou_http_proxy = \"http:\/\/:\"\r\n\r\n   - To setup your Fanfou account: Run below command for save the Fanfou OAuth token.\r\n      :FanfouSetAccount\r\n      This command will open the Fanfou OAuth confirmation Web Page.\r\n      After you get the PIN code, please enter it to VIM.\r\n      NOTE: In default, Vim-Fanfou saves your OAuth Token to \"$HOME\/.fanfou_auth_cache\".\r\n\r\n  ** Commands\r\n   - :FanfouSetAccount\r\n     To setup your Fanfou account. Please check \"Setup & Login\" section.\r\n   - :FanfouSwitchAccount\r\n     Login to another Fanfou account.\r\n   - :FanfouHomeTimeline\r\n     View your Fanfou home timeline.\r\n   - :FanfouMentions\r\n     View @ mention messages.\r\n  -  :FanfouFavorites\r\n     View your Fanfou favorites.\r\n  - :FanfouRefresh\r\n    Update Fanfou Vim Buffer. \r\n  - :FanfouPostStatus\r\n    To post a new Status to your Fanfou.\r\n\r\n  ** Shortcut key in the Fanfou VIM buffer\r\n   -  :FanfouRefresh\r\n   - h :FanfouHomeTimeline\r\n   - m :FanfouMentions\r\n   - s :FanfouFavorites\r\n   - p :FanfouPostStatus\r\n\r\n* License\r\nVim-fanfou is distributed under the same terms as VIM itself. See :help license.\r\n\r\n* Contact\r\n    The maintainer: @Xiongjia_Le ( http:\/\/fanfou.com\/xiongjia_le )\r\n     github: https:\/\/github.com\/xiongjia\/vim-fanfou\r\n","4":"* Vim-Fanfou\r\nVim-Fanfou = VIM + Fanfou ( http:\/\/fanfou.com\/ ).\r\nIt allows you to post to status and view Fanfou timeline.\r\n\r\nJust like Fanfou is a Twitter clone. \r\nVim-Fanfou is a TwitVim ( https:\/\/github.com\/vim-scripts\/TwitVim ) clone.\r\n\r\n* Vim-Fanfou links\r\n - Source code:  https:\/\/github.com\/xiongjia\/vim-fanfou\r\n - Releases:     https:\/\/github.com\/xiongjia\/vim-fanfou\/releases\r\n - Vim Script:   http:\/\/www.vim.org\/scripts\/script.php?script_id=4972\r\n - Project Page: http:\/\/xiongjia.github.io\/vim-fanfou\/\r\n\r\n* Installation\r\n - Requirements:\r\n   Vim-Fanfou is based on Python 2.7(+) & VIM 7+. Please check your VIM before you install Vim-Fanfou.\r\n\r\n - Steps to install:\r\n    Copy the \"plugin\" folder to your VIM \"plugin\" folder.\r\n\r\n* Usage\r\n  ** Setup & Login\r\n   - To enable HTTP Proxy: Add below line to your .vimrc.\r\n      let g:fanfou_http_proxy = \"http:\/\/:\"\r\n\r\n   - To setup your Fanfou account: Run below command for save the Fanfou OAuth token.\r\n      :FanfouSetAccount\r\n      This command will open the Fanfou OAuth confirmation Web Page.\r\n      After you get the PIN code, please enter it to VIM.\r\n      NOTE: In default, Vim-Fanfou saves your OAuth Token to \"$HOME\/.fanfou_auth_cache\".\r\n\r\n  ** Commands\r\n   - :FanfouSetAccount\r\n     To setup your Fanfou account. Please check \"Setup & Login\" section.\r\n   - :FanfouSwitchAccount\r\n     Login to another Fanfou account.\r\n   - :FanfouHomeTimeline\r\n     View your Fanfou home timeline.\r\n   - :FanfouMentions\r\n     View @ mention messages.\r\n  -  :FanfouFavorites\r\n     View your Fanfou favorites.\r\n  - :FanfouRefresh\r\n    Update Fanfou Vim Buffer. \r\n  - :FanfouPostStatus\r\n    To post a new Status to your Fanfou.\r\n\r\n  ** Shortcut key in the Fanfou VIM buffer\r\n   -  :FanfouRefresh\r\n   - h :FanfouHomeTimeline\r\n   - m :FanfouMentions\r\n   - s :FanfouFavorites\r\n   - p :FanfouPostStatus\r\n\r\n* License\r\nVim-fanfou is distributed under the same terms as VIM itself. See :help license.\r\n\r\n* Contact\r\n    The maintainer: @Xiongjia_Le ( http:\/\/fanfou.com\/xiongjia_le )\r\n     github: https:\/\/github.com\/xiongjia\/vim-fanfou\r\n","install_details":"* Installation\r\n - Requirements:\r\n   Vim-Fanfou is based on Python 2.7(+) & VIM 7+. Please check your VIM before you install Vim-Fanfou.\r\n - Steps to install:\r\n    Copy the \"plugin\" folder to your VIM \"plugin\" folder.\r\n\r\n","5":"* Installation\r\n - Requirements:\r\n   Vim-Fanfou is based on Python 2.7(+) & VIM 7+. Please check your VIM before you install Vim-Fanfou.\r\n - Steps to install:\r\n    Copy the \"plugin\" folder to your VIM \"plugin\" folder.\r\n\r\n","first_name":"XiongJia","6":"XiongJia","last_name":"Le","7":"Le","releases":[{"0":"4972","vim_version":"7.0","1":"7.0","script_version":"v0.2","2":"v0.2","version_comment":"* Fix HTML String convert issue\r\n* Support Favorites&Mentions timeline\r\n*  Add more Shortcut keys\r\n*  Update Syntax for Vim Fanfou buffer\r\n*  Update README & Documentation; New Project Page: http:\/\/xiongjia.github.io\/vim-fanfou\/\r\n*  Add python unit tests\r\n","3":"* Fix HTML String convert issue\r\n* Support Favorites&Mentions timeline\r\n*  Add more Shortcut keys\r\n*  Update Syntax for Vim Fanfou buffer\r\n*  Update README & Documentation; New Project Page: http:\/\/xiongjia.github.io\/vim-fanfou\/\r\n*  Add python unit tests\r\n","package":"vim-fanfou-0.2.zip","4":"vim-fanfou-0.2.zip","src_id":"22262","5":"22262","creation_date":"1406351621","6":"1406351621"},{"0":"4972","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"vim-fanfou-0.1.zip","4":"vim-fanfou-0.1.zip","src_id":"22102","5":"22102","creation_date":"1403935202","6":"1403935202"}]},"4971":{"script_id":"4971","0":"4971","script_name":"SwapText","1":"SwapText","script_type":"utility","2":"utility","summary":"Mappings to exchange text with the previously deleted text. ","3":"Mappings to exchange text with the previously deleted text. ","description":"DESCRIPTION\r\nSwapping text areas when there's other text in between (e.g. function\r\narguments separated by other arguments) is done frequently, yet cumbersome.\r\nOne way to do this is by deleting A, selecting B, pasting over it, then going\r\nback to where A used to be and pasting the original B.\r\n\r\nThis plugin lets you exchange the current selection \/ line \/ text covered by a\r\nmotion with the previously deleted text, with a short and simple mapping. The\r\nswap can be undone as a single action.\r\n\r\nSOURCE\r\nBased on vimtip #470: Map to quickly swap\/exchange arbitrary text by Piet\r\nDelport and an enhancement by ad_scriven@postmaster.co.uk.\r\n    http:\/\/vim.wikia.com\/wiki\/Swapping_characters,_words_and_lines\r\n\r\nSEE ALSO\r\n- The LineJuggler.vim plugin (vimscript #4140) provides [E \/ ]E mappings to\r\n  swap lines \/ the selection with the same amount of visible lines located\r\n  [count] above \/ below.\r\n- The LineJugglerCommands.vim plugin (vimscript #4465) provides swapping of\r\n  ranges as an Ex :Swap command.\r\n\r\nRELATED WORKS\r\n- visswap.vim (http:\/\/www.drchip.org\/astronaut\/vim\/vbafiles\/visswap.vba.gz)\r\n  uses a visual selection, , another selection,  to swap the two.\r\n- swapstrings.vim (http:\/\/www.drchip.org\/astronaut\/vim\/#SWAPSTRINGS) can swap\r\n  all instances of two strings in a range.\r\n- swap.vim (vimscript #3250) can swap around a pivot (e.g. ==) or to WORDs to\r\n  the left \/ right with x \/ X.\r\n- exchange (https:\/\/github.com\/tommcdo\/vim-exchange) defines a cx{motion}\r\n  operator that has to be used twice to exchange the first with the second\r\n  one.\r\n\r\nUSAGE\r\nFirst, delete some text (using any normal Vim command, such as \"daw\",\r\n{Visual}x, or \"dt\"). Then, visually select some other text, and press\r\nx, or use the custom operator x{motion}. The two pieces of\r\ntext should now be swapped.\r\n\r\n{Visual}x       Swap the visual selection with the just deleted text.\r\nx{motion}       Swap the characters covered by {motion} with the just\r\n                        deleted text.\r\n[count]xx       Swap the current [count] line(s) with the just deleted\r\n                        text.\r\n[count]X        Swap the characters under the cursor until the end of\r\n                        the line and [count]-1 more lines with the just\r\n                        deleted text.","4":"DESCRIPTION\r\nSwapping text areas when there's other text in between (e.g. function\r\narguments separated by other arguments) is done frequently, yet cumbersome.\r\nOne way to do this is by deleting A, selecting B, pasting over it, then going\r\nback to where A used to be and pasting the original B.\r\n\r\nThis plugin lets you exchange the current selection \/ line \/ text covered by a\r\nmotion with the previously deleted text, with a short and simple mapping. The\r\nswap can be undone as a single action.\r\n\r\nSOURCE\r\nBased on vimtip #470: Map to quickly swap\/exchange arbitrary text by Piet\r\nDelport and an enhancement by ad_scriven@postmaster.co.uk.\r\n    http:\/\/vim.wikia.com\/wiki\/Swapping_characters,_words_and_lines\r\n\r\nSEE ALSO\r\n- The LineJuggler.vim plugin (vimscript #4140) provides [E \/ ]E mappings to\r\n  swap lines \/ the selection with the same amount of visible lines located\r\n  [count] above \/ below.\r\n- The LineJugglerCommands.vim plugin (vimscript #4465) provides swapping of\r\n  ranges as an Ex :Swap command.\r\n\r\nRELATED WORKS\r\n- visswap.vim (http:\/\/www.drchip.org\/astronaut\/vim\/vbafiles\/visswap.vba.gz)\r\n  uses a visual selection, , another selection,  to swap the two.\r\n- swapstrings.vim (http:\/\/www.drchip.org\/astronaut\/vim\/#SWAPSTRINGS) can swap\r\n  all instances of two strings in a range.\r\n- swap.vim (vimscript #3250) can swap around a pivot (e.g. ==) or to WORDs to\r\n  the left \/ right with x \/ X.\r\n- exchange (https:\/\/github.com\/tommcdo\/vim-exchange) defines a cx{motion}\r\n  operator that has to be used twice to exchange the first with the second\r\n  one.\r\n\r\nUSAGE\r\nFirst, delete some text (using any normal Vim command, such as \"daw\",\r\n{Visual}x, or \"dt\"). Then, visually select some other text, and press\r\nx, or use the custom operator x{motion}. The two pieces of\r\ntext should now be swapped.\r\n\r\n{Visual}x       Swap the visual selection with the just deleted text.\r\nx{motion}       Swap the characters covered by {motion} with the just\r\n                        deleted text.\r\n[count]xx       Swap the current [count] line(s) with the just deleted\r\n                        text.\r\n[count]X        Swap the characters under the cursor until the end of\r\n                        the line and [count]-1 more lines with the just\r\n                        deleted text.","install_details":"INSTALLATION\r\nThis script is packaged as a vimball. If you have the \"gunzip\" decompressor\r\nin your PATH, simply edit the *.vmb.gz package in Vim; otherwise, decompress\r\nthe archive first, e.g. using WinZip. Inside Vim, install by sourcing the\r\nvimball or via the :UseVimball command.\r\n    vim SwapText*.vmb.gz\r\n    :so %\r\nTo uninstall, use the :RmVimball command.\r\n\r\nDEPENDENCIES\r\n- Requires Vim 7.0 or higher.\r\n- Requires the ingo-library.vim plugin (vimscript #4433), version 1.005 or\r\n  higher.","5":"INSTALLATION\r\nThis script is packaged as a vimball. If you have the \"gunzip\" decompressor\r\nin your PATH, simply edit the *.vmb.gz package in Vim; otherwise, decompress\r\nthe archive first, e.g. using WinZip. Inside Vim, install by sourcing the\r\nvimball or via the :UseVimball command.\r\n    vim SwapText*.vmb.gz\r\n    :so %\r\nTo uninstall, use the :RmVimball command.\r\n\r\nDEPENDENCIES\r\n- Requires Vim 7.0 or higher.\r\n- Requires the ingo-library.vim plugin (vimscript #4433), version 1.005 or\r\n  higher.","first_name":"Ingo","6":"Ingo","last_name":"Karkat","7":"Karkat","releases":[{"0":"4971","vim_version":"7.0","1":"7.0","script_version":"1.02","2":"1.02","version_comment":"- \"E790: undojoin is not allowed after undo\" may also be raised in SwapText#Operator(); ignore it.\r\n- BUG: When deleting at the end of a line, and swapping with a longer text before it, the swap location is off by one. The EOL position isn't properly detected, because the virtual line length after the paste is used in the condition. Save the deleted virtual line length in deletedVirtLen, and pass that on to s:WasDeletionAtEndOfLine(). Thanks to Marcelo Mont\u00c3\u00ba for the bug report.","3":"- \"E790: undojoin is not allowed after undo\" may also be raised in SwapText#Operator(); ignore it.\r\n- BUG: When deleting at the end of a line, and swapping with a longer text before it, the swap location is off by one. The EOL position isn't properly detected, because the virtual line length after the paste is used in the condition. Save the deleted virtual line length in deletedVirtLen, and pass that on to s:WasDeletionAtEndOfLine(). Thanks to Marcelo Mont\u00c3\u00ba for the bug report.","package":"SwapText-1.02.vmb.gz","4":"SwapText-1.02.vmb.gz","src_id":"24539","5":"24539","creation_date":"1474301811","6":"1474301811"},{"0":"4971","vim_version":"7.0","1":"7.0","script_version":"1.01","2":"1.01","version_comment":"- BUG: X includes the newline unless :set selection=exclusive. Thanks to Enno Nagel for reporting this.","3":"- BUG: X includes the newline unless :set selection=exclusive. Thanks to Enno Nagel for reporting this.","package":"SwapText-1.01.vmb.gz","4":"SwapText-1.01.vmb.gz","src_id":"22235","5":"22235","creation_date":"1406030207","6":"1406030207"},{"0":"4971","vim_version":"7.0","1":"7.0","script_version":"1.00","2":"1.00","version_comment":"Initial upload","3":"Initial upload","package":"SwapText-1.00.vmb.gz","4":"SwapText-1.00.vmb.gz","src_id":"22091","5":"22091","creation_date":"1403616619","6":"1403616619"}]},"4970":{"script_id":"4970","0":"4970","script_name":"rdark-terminal2.vim","1":"rdark-terminal2.vim","script_type":"color scheme","2":"color scheme","summary":"Modified rdark-terminal color scheme to enhance visibility for Dark Pastels ","3":"Modified rdark-terminal color scheme to enhance visibility for Dark Pastels ","description":"rdark-terminal2 modifies color for CursorLine, Type, Special, ColorColumn and IncSearch to enhance visibility for Dark Pastels. It is based on rdark-terminal of Lukas Gr\u00c3\u00a4sslin (http:\/\/www.vim.org\/scripts\/script.php?script_id=3202) which ported the rdark colorscheme for 256 colors (http:\/\/www.vim.org\/scripts\/script.php?script_id=1732).\r\n","4":"rdark-terminal2 modifies color for CursorLine, Type, Special, ColorColumn and IncSearch to enhance visibility for Dark Pastels. It is based on rdark-terminal of Lukas Gr\u00c3\u00a4sslin (http:\/\/www.vim.org\/scripts\/script.php?script_id=3202) which ported the rdark colorscheme for 256 colors (http:\/\/www.vim.org\/scripts\/script.php?script_id=1732).\r\n","install_details":"Place it in the colors directory","5":"Place it in the colors directory","first_name":"Radu-Sebastian","6":"Radu-Sebastian","last_name":"Marinescu","7":"Marinescu","releases":[{"0":"4970","vim_version":"7.4","1":"7.4","script_version":"0.3","2":"0.3","version_comment":"Visual mode with syntax highlighting","3":"Visual mode with syntax highlighting","package":"rdark-terminal2.vim","4":"rdark-terminal2.vim","src_id":"22209","5":"22209","creation_date":"1405512476","6":"1405512476"},{"0":"4970","vim_version":"7.0","1":"7.0","script_version":"0.2","2":"0.2","version_comment":"different IncSearch and Search colors to enhance visibility for search and replace operations ","3":"different IncSearch and Search colors to enhance visibility for search and replace operations ","package":"rdark-terminal2.vim","4":"rdark-terminal2.vim","src_id":"22097","5":"22097","creation_date":"1403872480","6":"1403872480"},{"0":"4970","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"rdark-terminal2.vim","4":"rdark-terminal2.vim","src_id":"22090","5":"22090","creation_date":"1403610973","6":"1403610973"}]},"4969":{"script_id":"4969","0":"4969","script_name":"Fist of Vim","1":"Fist of Vim","script_type":"utility","2":"utility","summary":"Super simple and awesome gist support for vim","3":"Super simple and awesome gist support for vim","description":"Fast, simple and super awesome Gist-ing for Vim.\r\n\r\n## Dependencies\r\n- https:\/\/github.com\/defunkt\/gist.git - \"Potentially the best command line gister\"\r\n\r\nInstall and configure it by running:\r\n\r\n    [sudo] gem install gist && gist --login\r\n\r\n## Usage\r\nOnly breathing is easier than using Fist of Vim.\r\n\r\nFist of Vim defines these super simple mappings by default:\r\n\r\n1. p - Create a new Gist\r\n\r\n2. u - Update an existing Gist\r\n\r\n3. l - List your public Gists\r\n\r\nYou can use create or update a Gist with a visual selection, or in normal mode,\r\nin which case, it is motion based.\r\n\r\nFor example, in normal mode, pG will create a new Gist from the\r\ncursor to the end of file. In visual mode, you can simply select and then hit\r\np to create a new Gist. \r\n\r\nFist of Vim also sets the filetype and syntax completely automatically without\r\nyou having to set it!\r\n\r\nAs the philosopher, Staples Inc., once said, \"That was easy!\"\r\n\r\n### Custom Maps\r\nFist of Vim allows you to choose the Fist to hold the gavel with. In other\r\nwords, you can assign your own maps for these:\r\n\r\n1. fov_new           - Create a new Gist (normal mode)\r\n\r\n2. fov_update       - Update a Gist (normal mode)\r\n\r\n3. fov_visual_new    - Create a new Gist (visual mode)\r\n\r\n4. fov_visual_update - Update a Gist (visual mode)\r\n\r\n5. fov_list          - List your Gists.\r\n\r\nExample: nmap f fov_new.\r\n\r\n### Configuration\r\nFist of Vim offers these hilariously named variables so it can be configured to your exacting standards:\r\n\r\n1. g:fist_opens_browser - Open the new\/updated Gist in the browser.\r\n\r\n2. g:fist_in_private    - Create a secret Gist\r\n\r\n3. g:fist_no_maps       - Don't define any mappings automatically.\r\n\r\n4. g:fist_dispatch      - When listing Gists, do it asynchronously (requires dispatch.vim from https:\/\/github.com\/tpope\/vim-dispatch)","4":"Fast, simple and super awesome Gist-ing for Vim.\r\n\r\n## Dependencies\r\n- https:\/\/github.com\/defunkt\/gist.git - \"Potentially the best command line gister\"\r\n\r\nInstall and configure it by running:\r\n\r\n    [sudo] gem install gist && gist --login\r\n\r\n## Usage\r\nOnly breathing is easier than using Fist of Vim.\r\n\r\nFist of Vim defines these super simple mappings by default:\r\n\r\n1. p - Create a new Gist\r\n\r\n2. u - Update an existing Gist\r\n\r\n3. l - List your public Gists\r\n\r\nYou can use create or update a Gist with a visual selection, or in normal mode,\r\nin which case, it is motion based.\r\n\r\nFor example, in normal mode, pG will create a new Gist from the\r\ncursor to the end of file. In visual mode, you can simply select and then hit\r\np to create a new Gist. \r\n\r\nFist of Vim also sets the filetype and syntax completely automatically without\r\nyou having to set it!\r\n\r\nAs the philosopher, Staples Inc., once said, \"That was easy!\"\r\n\r\n### Custom Maps\r\nFist of Vim allows you to choose the Fist to hold the gavel with. In other\r\nwords, you can assign your own maps for these:\r\n\r\n1. fov_new           - Create a new Gist (normal mode)\r\n\r\n2. fov_update       - Update a Gist (normal mode)\r\n\r\n3. fov_visual_new    - Create a new Gist (visual mode)\r\n\r\n4. fov_visual_update - Update a Gist (visual mode)\r\n\r\n5. fov_list          - List your Gists.\r\n\r\nExample: nmap f fov_new.\r\n\r\n### Configuration\r\nFist of Vim offers these hilariously named variables so it can be configured to your exacting standards:\r\n\r\n1. g:fist_opens_browser - Open the new\/updated Gist in the browser.\r\n\r\n2. g:fist_in_private    - Create a secret Gist\r\n\r\n3. g:fist_no_maps       - Don't define any mappings automatically.\r\n\r\n4. g:fist_dispatch      - When listing Gists, do it asynchronously (requires dispatch.vim from https:\/\/github.com\/tpope\/vim-dispatch)","install_details":"\r\n## Install\r\nIf you use Vim 8 or better, simply copy and paste:\r\n\r\n    git clone https:\/\/git.sr.ht\/~ackyshake\/fist.vim ~\/.vim\/pack\/vendor\/start\/vim-fist\r\n\r\nOnce the helptags have been generated (:helptags ALL), see :help vim-fist for usage.","5":"\r\n## Install\r\nIf you use Vim 8 or better, simply copy and paste:\r\n\r\n    git clone https:\/\/git.sr.ht\/~ackyshake\/fist.vim ~\/.vim\/pack\/vendor\/start\/vim-fist\r\n\r\nOnce the helptags have been generated (:helptags ALL), see :help vim-fist for usage.","first_name":"Akshay","6":"Akshay","last_name":"Hegde","7":"Hegde","releases":[{"0":"4969","vim_version":"7.3","1":"7.3","script_version":"1.8","2":"1.8","version_comment":"- Now creates a secret gist by default\r\n- Fixed incorrect function name reference\r\n- Fixed an issue where creating a gist with visual mode would use the contents of the unnamed register instead of the selection.","3":"- Now creates a secret gist by default\r\n- Fixed incorrect function name reference\r\n- Fixed an issue where creating a gist with visual mode would use the contents of the unnamed register instead of the selection.","package":"vim-fist-1.8.tar.gz","4":"vim-fist-1.8.tar.gz","src_id":"27440","5":"27440","creation_date":"1609914226","6":"1609914226"},{"0":"4969","vim_version":"7.3","1":"7.3","script_version":"1.7","2":"1.7","version_comment":"* Finally fixes any gist updating issues.\r\n\r\nThis version also means that if you can simply enter `let @f = \"\"` and then use the Fist of Vim's update command and have the gist updated.","3":"* Finally fixes any gist updating issues.\r\n\r\nThis version also means that if you can simply enter `let @f = \"\"` and then use the Fist of Vim's update command and have the gist updated.","package":"vim-fist-1.7.zip","4":"vim-fist-1.7.zip","src_id":"22776","5":"22776","creation_date":"1420963079","6":"1420963079"},{"0":"4969","vim_version":"7.3","1":"7.3","script_version":"1.6","2":"1.6","version_comment":"* Better UX when listing gists\r\n* Added a g:fist_dispatch variable to optionally use async when listing gists\r\n* Fixed an issue where filename was not getting set.\r\n* Cleaned up default maps to not use `hasmapto()` to prevent errors.\r\n* Documentation updates","3":"* Better UX when listing gists\r\n* Added a g:fist_dispatch variable to optionally use async when listing gists\r\n* Fixed an issue where filename was not getting set.\r\n* Cleaned up default maps to not use `hasmapto()` to prevent errors.\r\n* Documentation updates","package":"vim-fist-1.6.zip","4":"vim-fist-1.6.zip","src_id":"22731","5":"22731","creation_date":"1419423320","6":"1419423320"},{"0":"4969","vim_version":"7.3","1":"7.3","script_version":"1.5","2":"1.5","version_comment":"Major changes:\r\n\r\nFixed an issue creating a Gist with linewise motions.\r\nFixed several issues with updating a Gist with both normal and visual modes.\r\nModified all functions to be private\r\nUpdated documentation","3":"Major changes:\r\n\r\nFixed an issue creating a Gist with linewise motions.\r\nFixed several issues with updating a Gist with both normal and visual modes.\r\nModified all functions to be private\r\nUpdated documentation","package":"vim-fist-1.5.zip","4":"vim-fist-1.5.zip","src_id":"22716","5":"22716","creation_date":"1419143119","6":"1419143119"},{"0":"4969","vim_version":"7.3","1":"7.3","script_version":"1.4","2":"1.4","version_comment":"* Add ability to list the user's gists.\r\n* Allow users to disable Fist of Vim default mappings.\r\n* Fix an issue where gists aren't created to the end of a line.","3":"* Add ability to list the user's gists.\r\n* Allow users to disable Fist of Vim default mappings.\r\n* Fix an issue where gists aren't created to the end of a line.","package":"vim-fist-1.4.zip","4":"vim-fist-1.4.zip","src_id":"22713","5":"22713","creation_date":"1418978540","6":"1418978540"},{"0":"4969","vim_version":"7.3","1":"7.3","script_version":"1.3","2":"1.3","version_comment":"Major Changes:\r\n\r\n* Added ability to define new mappings for creating\/updating gists.\r\n* Bug Fixes","3":"Major Changes:\r\n\r\n* Added ability to define new mappings for creating\/updating gists.\r\n* Bug Fixes","package":"vim-fist.zip","4":"vim-fist.zip","src_id":"22212","5":"22212","creation_date":"1405677027","6":"1405677027"},{"0":"4969","vim_version":"7.3","1":"7.3","script_version":"1.2","2":"1.2","version_comment":"Major changes:\r\n\r\n- Fixed gisting from visual mode.\r\n- Gisting from normal mode is now motion based (See :h vim-fist)\r\n- You can now update your existing gists from\r\n\r\nMinor Changes:\r\nThis plugin is now called Fist of Vim","3":"Major changes:\r\n\r\n- Fixed gisting from visual mode.\r\n- Gisting from normal mode is now motion based (See :h vim-fist)\r\n- You can now update your existing gists from\r\n\r\nMinor Changes:\r\nThis plugin is now called Fist of Vim","package":"vim-fist-1.2.zip","4":"vim-fist-1.2.zip","src_id":"22094","5":"22094","creation_date":"1403649941","6":"1403649941"},{"0":"4969","vim_version":"7.3","1":"7.3","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"vim-fist-1.0.zip","4":"vim-fist-1.0.zip","src_id":"22089","5":"22089","creation_date":"1403586311","6":"1403586311"}]},"4968":{"script_id":"4968","0":"4968","script_name":"AutoCWD.vim","1":"AutoCWD.vim","script_type":"utility","2":"utility","summary":"Automatically updates vim's CWD depending on the current file path ","3":"Automatically updates vim's CWD depending on the current file path ","description":"More information : https:\/\/github.com\/yssl\/autocwd.vim\r\n\r\n# autocwd.vim\r\n\r\nautocwd.vim automatically changes the current working directory (CWD) of vim \r\nwhen you change the current buffer (or window).\r\nYou can define patterns that may be included in a file path or buffer name,\r\n and corresponding working directories in your .vimrc. \r\n\r\nScreenshot:\r\nhttps:\/\/cloud.githubusercontent.com\/assets\/5915359\/3622432\/de3ce5c8-0e33-11e4-8a78-ff5d8bc33d92.png\r\n\r\n## Usage\r\n\r\nYou can define patterns and working directories in your .vimrc as follows:\r\n\r\n```\r\nlet g:autocwd_patternwd_pairs = [\r\n\t\\[pattern1, working_directory1],\r\n\t\\[pattern2, working_directory2],\r\n\t...\r\n\t\\]\r\n```\r\n\r\n- pattern is a substring of a file path or buffer name with Unix shell-style wildcards.  \r\nFor example, '\\*.vim' matches files with .vim extension and '*\/project1\/*' matches files \r\nthat contains '\/project1\/' in their absolute file paths.  \r\n(Please refer https:\/\/docs.python.org\/2\/library\/fnmatch.html for more information.\r\npatterns are processed by python's fnmatch function internally.)\r\n\r\n- working_directory will be the CWD when the corresponding pattern matches the c\r\nurrent file path or buffer name.  \r\nIt can be one of following types:\r\n\r\n\ttype                                 | example: working_directory | example: CWD to be changed\r\n\t---                                  | ---                        | ---\r\n\tabsolute path                        | '~\/test'                   | ~\/test\r\n\tvim's file name modifier (1)         | '%:p:h'                    | current file's directory\r\n\tspecial keyword                      | '*REPO*' (2)               | root directory of the repository containing current file\r\n\r\n\t(1) Please refer http:\/\/vimdoc.sourceforge.net\/htmldoc\/cmdline.html#filename-modifiers for more information.  \r\n\t(2) '*REPO*' is replaced with the root directory of the repository containing current file.  \r\n\t- Examples:  \r\n\t\tIf the directory structure looks like this:\r\n\t\t```\r\n\t\t+-- ~\/code \r\n\t\t|\t+-- bin\r\n\t\t|\t+-- examples\r\n\t\t|\t|\t+-- .git\r\n\t\t|\t|\t+-- ex1\r\n\t\t| \t|\t|\t+-- current file\r\n\t\t```\r\n\t- '\\*REPO\\*' : ~\/code\/examples\r\n\t- '\\*REPO\\*\/ex1' : ~\/code\/examples\/ex1\r\n\t- '\\*REPO\\*\/..' : ~\/code\r\n\r\n- If the current buffer matches one of the defined patterns, the CWD will \r\nbe changed to the corresponding working directory.\r\nOtherwise, the default working directory that have been the CWD before \r\napplying `g:autocwd_patternwd_pairs` will be restored.  \r\nYou can change the default working directory by `:cd` or other CWD-changing \r\ncommands (e.g., 'cd' of the NERDTree) when the current buffer does not \r\nmatch any of predefined patterns.\r\n\r\n- The order of patterns in `g:autocwd_patternwd_pairs` is meaningful.\r\nIf the current buffer matches both first and second patterns, the working \r\ndirectory corresponding to the first pattern will be the CWD.\r\n\r\n\r\n## Commands\r\n\r\n**:AutoCWDPrint**  \r\nPrint the buffer name or file path, matched pattern, and working directory of windows in the current tab.\r\nYou can jump to one of the listed windows by typing the index(#) of the window.\r\n\r\nThere is no activation commands for autocwd.vim. \r\nIf you install this plugin, it will starts to manage the CWD.\r\n\r\n## Motivation\r\n\r\nIt is quite useful to set the CWD for each opened file in vim.\r\nVim provides `:lcd` command for this purpose. \r\nHowever, it cannot deal with opening other files in the same window because `:lcd` is applied to a specific window, not buffer.  \r\n\r\nautocwd.vim is designed to solve this problem.\r\nMoreover, it provides more convenient way to set CWDs with Unix shell-style patterns.\r\n","4":"More information : https:\/\/github.com\/yssl\/autocwd.vim\r\n\r\n# autocwd.vim\r\n\r\nautocwd.vim automatically changes the current working directory (CWD) of vim \r\nwhen you change the current buffer (or window).\r\nYou can define patterns that may be included in a file path or buffer name,\r\n and corresponding working directories in your .vimrc. \r\n\r\nScreenshot:\r\nhttps:\/\/cloud.githubusercontent.com\/assets\/5915359\/3622432\/de3ce5c8-0e33-11e4-8a78-ff5d8bc33d92.png\r\n\r\n## Usage\r\n\r\nYou can define patterns and working directories in your .vimrc as follows:\r\n\r\n```\r\nlet g:autocwd_patternwd_pairs = [\r\n\t\\[pattern1, working_directory1],\r\n\t\\[pattern2, working_directory2],\r\n\t...\r\n\t\\]\r\n```\r\n\r\n- pattern is a substring of a file path or buffer name with Unix shell-style wildcards.  \r\nFor example, '\\*.vim' matches files with .vim extension and '*\/project1\/*' matches files \r\nthat contains '\/project1\/' in their absolute file paths.  \r\n(Please refer https:\/\/docs.python.org\/2\/library\/fnmatch.html for more information.\r\npatterns are processed by python's fnmatch function internally.)\r\n\r\n- working_directory will be the CWD when the corresponding pattern matches the c\r\nurrent file path or buffer name.  \r\nIt can be one of following types:\r\n\r\n\ttype                                 | example: working_directory | example: CWD to be changed\r\n\t---                                  | ---                        | ---\r\n\tabsolute path                        | '~\/test'                   | ~\/test\r\n\tvim's file name modifier (1)         | '%:p:h'                    | current file's directory\r\n\tspecial keyword                      | '*REPO*' (2)               | root directory of the repository containing current file\r\n\r\n\t(1) Please refer http:\/\/vimdoc.sourceforge.net\/htmldoc\/cmdline.html#filename-modifiers for more information.  \r\n\t(2) '*REPO*' is replaced with the root directory of the repository containing current file.  \r\n\t- Examples:  \r\n\t\tIf the directory structure looks like this:\r\n\t\t```\r\n\t\t+-- ~\/code \r\n\t\t|\t+-- bin\r\n\t\t|\t+-- examples\r\n\t\t|\t|\t+-- .git\r\n\t\t|\t|\t+-- ex1\r\n\t\t| \t|\t|\t+-- current file\r\n\t\t```\r\n\t- '\\*REPO\\*' : ~\/code\/examples\r\n\t- '\\*REPO\\*\/ex1' : ~\/code\/examples\/ex1\r\n\t- '\\*REPO\\*\/..' : ~\/code\r\n\r\n- If the current buffer matches one of the defined patterns, the CWD will \r\nbe changed to the corresponding working directory.\r\nOtherwise, the default working directory that have been the CWD before \r\napplying `g:autocwd_patternwd_pairs` will be restored.  \r\nYou can change the default working directory by `:cd` or other CWD-changing \r\ncommands (e.g., 'cd' of the NERDTree) when the current buffer does not \r\nmatch any of predefined patterns.\r\n\r\n- The order of patterns in `g:autocwd_patternwd_pairs` is meaningful.\r\nIf the current buffer matches both first and second patterns, the working \r\ndirectory corresponding to the first pattern will be the CWD.\r\n\r\n\r\n## Commands\r\n\r\n**:AutoCWDPrint**  \r\nPrint the buffer name or file path, matched pattern, and working directory of windows in the current tab.\r\nYou can jump to one of the listed windows by typing the index(#) of the window.\r\n\r\nThere is no activation commands for autocwd.vim. \r\nIf you install this plugin, it will starts to manage the CWD.\r\n\r\n## Motivation\r\n\r\nIt is quite useful to set the CWD for each opened file in vim.\r\nVim provides `:lcd` command for this purpose. \r\nHowever, it cannot deal with opening other files in the same window because `:lcd` is applied to a specific window, not buffer.  \r\n\r\nautocwd.vim is designed to solve this problem.\r\nMoreover, it provides more convenient way to set CWDs with Unix shell-style patterns.\r\n","install_details":"- Using plugin managers (recommended)\r\n    - [Vundle] : Add `Bundle 'yssl\/autocwd.vim'` to .vimrc & `:BundleInstall`\r\n    - [NeoBundle] : Add `NeoBundle 'yssl\/autocwd.vim'` to .vimrc & `:NeoBundleInstall`\r\n    - [vim-plug] : Add `Plug 'yssl\/autocwd.vim'` to .vimrc & `:PlugInstall`\r\n- Using [Pathogen]\r\n    - `cd ~\/.vim\/bundle; git clone https:\/\/github.com\/yssl\/autocwd.vim.git`\r\n- Manual install (not recommended)\r\n    - Download this plugin and extract it in `~\/.vim\/`\r\n\r\nThis plugin requires a version of vim with python support. You can check your vim with :echo has('python'). If your vim doesn't support python, one of the easiest solutions would be installing a more featured version of vim by:\r\nsudo apt-get install vim-nox","5":"- Using plugin managers (recommended)\r\n    - [Vundle] : Add `Bundle 'yssl\/autocwd.vim'` to .vimrc & `:BundleInstall`\r\n    - [NeoBundle] : Add `NeoBundle 'yssl\/autocwd.vim'` to .vimrc & `:NeoBundleInstall`\r\n    - [vim-plug] : Add `Plug 'yssl\/autocwd.vim'` to .vimrc & `:PlugInstall`\r\n- Using [Pathogen]\r\n    - `cd ~\/.vim\/bundle; git clone https:\/\/github.com\/yssl\/autocwd.vim.git`\r\n- Manual install (not recommended)\r\n    - Download this plugin and extract it in `~\/.vim\/`\r\n\r\nThis plugin requires a version of vim with python support. You can check your vim with :echo has('python'). If your vim doesn't support python, one of the easiest solutions would be installing a more featured version of vim by:\r\nsudo apt-get install vim-nox","first_name":"Yoonsang","6":"Yoonsang","last_name":"Lee","7":"Lee","releases":[{"0":"4968","vim_version":"7.0","1":"7.0","script_version":"1.3.2","2":"1.3.2","version_comment":"Support both Python 2 & Python 3 ","3":"Support both Python 2 & Python 3 ","package":"AutoCWD.vim.zip","4":"AutoCWD.vim.zip","src_id":"26433","5":"26433","creation_date":"1553413817","6":"1553413817"},{"0":"4968","vim_version":"7.0","1":"7.0","script_version":"1.3.1","2":"1.3.1","version_comment":"Print working directory in absolute path","3":"Print working directory in absolute path","package":"autocwd.vim.zip","4":"autocwd.vim.zip","src_id":"22817","5":"22817","creation_date":"1421790764","6":"1421790764"},{"0":"4968","vim_version":"7.0","1":"7.0","script_version":"1.3.0","2":"1.3.0","version_comment":"add window selecting prompt to AutoCMDPrint command","3":"add window selecting prompt to AutoCMDPrint command","package":"autocwd.vim.zip","4":"autocwd.vim.zip","src_id":"22737","5":"22737","creation_date":"1419719070","6":"1419719070"},{"0":"4968","vim_version":"7.0","1":"7.0","script_version":"1.2.0","2":"1.2.0","version_comment":"    - add special keyword '*REPO*' that can be used in predefined working_directory.\r\n    now you can set working directory to relative path from the repository directory.\r\n","3":"    - add special keyword '*REPO*' that can be used in predefined working_directory.\r\n    now you can set working directory to relative path from the repository directory.\r\n","package":"autocwd.vim.zip","4":"autocwd.vim.zip","src_id":"22501","5":"22501","creation_date":"1412811801","6":"1412811801"},{"0":"4968","vim_version":"7.0","1":"7.0","script_version":"1.1.0","2":"1.1.0","version_comment":"change the name to autocmd.vim","3":"change the name to autocmd.vim","package":"autocwd.zip","4":"autocwd.zip","src_id":"22303","5":"22303","creation_date":"1407422500","6":"1407422500"},{"0":"4968","vim_version":"7.0","1":"7.0","script_version":"1.0.0","2":"1.0.0","version_comment":"Initial upload","3":"Initial upload","package":"CWDPattern.zip","4":"CWDPattern.zip","src_id":"22088","5":"22088","creation_date":"1403580772","6":"1403580772"}]},"4967":{"script_id":"4967","0":"4967","script_name":"Nefertiti","1":"Nefertiti","script_type":"color scheme","2":"color scheme","summary":"Dark-background Vim Color Scheme with Dynamic Brightness Control (GUI-only) ","3":"Dark-background Vim Color Scheme with Dynamic Brightness Control (GUI-only) ","description":"A warm dark-background color scheme for Vim, featuring dynamic control of brightness-levels as needed.\r\n\r\nBrighten select (normal and syntax) colors with \":NefertitiBrighten\", or darken them with \":NefertitiDarken\". Conveniently bound to \"META-2\" and \"META-1\", respectively, but you can, of course, suppress the key mappings and\/or replace them with others of your own preference.\r\n\r\nNOTE: \r\n    (1) GUI Vim only at the present time.\r\n    (2) Previously known as \"MochaLatte\"\r\n\r\nNefertiti lives at:\r\n\r\n    https:\/\/github.com\/jeetsukumaran\/vim-nefertiti\r\n\r\nand more details as well as, e.g. screen shots, can be found there.","4":"A warm dark-background color scheme for Vim, featuring dynamic control of brightness-levels as needed.\r\n\r\nBrighten select (normal and syntax) colors with \":NefertitiBrighten\", or darken them with \":NefertitiDarken\". Conveniently bound to \"META-2\" and \"META-1\", respectively, but you can, of course, suppress the key mappings and\/or replace them with others of your own preference.\r\n\r\nNOTE: \r\n    (1) GUI Vim only at the present time.\r\n    (2) Previously known as \"MochaLatte\"\r\n\r\nNefertiti lives at:\r\n\r\n    https:\/\/github.com\/jeetsukumaran\/vim-nefertiti\r\n\r\nand more details as well as, e.g. screen shots, can be found there.","install_details":"## Pathogen\r\n\r\n    $ cd ~\/.vim\/bundle\r\n    $ git clone https:\/\/github.com\/jeetsukumaran\/vim-nefertiti\r\n\r\n## Vundle\r\n\r\n    :BundleInstall jeetsukumaran\/vim-nefertiti\r\n\r\n## Manually\r\n\r\nCopy the file \"colors\/nefertiti.vim\" to your \"~.\/vim\/colors\/\" subdirectory.","5":"## Pathogen\r\n\r\n    $ cd ~\/.vim\/bundle\r\n    $ git clone https:\/\/github.com\/jeetsukumaran\/vim-nefertiti\r\n\r\n## Vundle\r\n\r\n    :BundleInstall jeetsukumaran\/vim-nefertiti\r\n\r\n## Manually\r\n\r\nCopy the file \"colors\/nefertiti.vim\" to your \"~.\/vim\/colors\/\" subdirectory.","first_name":"Jeet","6":"Jeet","last_name":"Sukumaran","7":"Sukumaran","releases":[{"0":"4967","vim_version":"7.0","1":"7.0","script_version":"2.0.0","2":"2.0.0","version_comment":"Initial upload","3":"Initial upload","package":"vim-nefertiti-v2.0.0.tar.gz","4":"vim-nefertiti-v2.0.0.tar.gz","src_id":"22081","5":"22081","creation_date":"1403466991","6":"1403466991"}]},"4965":{"script_id":"4965","0":"4965","script_name":"arnoldc.vim","1":"arnoldc.vim","script_type":"syntax","2":"syntax","summary":"Syntax highlighting for ArnoldC language","3":"Syntax highlighting for ArnoldC language","description":"ArnoldC code is all uppercase. Syntax highlighting makes a difference particularly while you are learning. See the notes in arnoldc.vim about syntax highlighting groups and colour schemes. Otherwise you will not see very many different colours.","4":"ArnoldC code is all uppercase. Syntax highlighting makes a difference particularly while you are learning. See the notes in arnoldc.vim about syntax highlighting groups and colour schemes. Otherwise you will not see very many different colours.","install_details":"Put the arnoldc.vim file in your (main or alternate) syntax folder. Add a file association command at start up in your .vimrc (or equivalent) file.\r\n\r\nsyntax enable              \"You might already have this\r\nau BufRead,BufNewFile *.arnoldc setfiletype arnoldc","5":"Put the arnoldc.vim file in your (main or alternate) syntax folder. Add a file association command at start up in your .vimrc (or equivalent) file.\r\n\r\nsyntax enable              \"You might already have this\r\nau BufRead,BufNewFile *.arnoldc setfiletype arnoldc","first_name":"David","6":"David","last_name":"Croal","7":"Croal","releases":[{"0":"4965","vim_version":"7.0","1":"7.0","script_version":"1","2":"1","version_comment":"Initial upload","3":"Initial upload","package":"arnoldc.vim","4":"arnoldc.vim","src_id":"22071","5":"22071","creation_date":"1403361685","6":"1403361685"}]},"4963":{"script_id":"4963","0":"4963","script_name":"OCamlJump","1":"OCamlJump","script_type":"ftplugin","2":"ftplugin","summary":"Allow to jum between let and in keyword.","3":"Allow to jum between let and in keyword.","description":"OCaml is a great language but still greater can be done.\r\nEspecially, about syntax, I feel every 'delimiting' things should be made easily 'jumpables'.\r\n\r\nThis plugin add a leader j ( \\j ) shortcut allowing to jump from a 'let' to its matching 'in' or the reverse ('in' to 'let').\r\n'let' or 'in' contained in comments or string are subtly ignored.\r\n\r\n###################\r\n\r\nOcaml estas mojosa programlingvo tamen povas ankora\u00c3\u00bb esti pli bona.\r\nSpeciale, pri sintakso, mi pensas ke ĉiuj 'disigiloj' devas esti facile 'salteblaj'.\r\n\r\nTio aldonaĵo proponas klavosignon (ĉefklavo j ( \\j ) ) kiu saltagas la skribmarkon el 'let' al la kongrua 'in' kaj inverso.\r\n'let' a\u00c3\u00bb 'in' entenita en komentoj a\u00c3\u00bb signoĉenoj estas ignorataj.\r\n\r\n\r\n","4":"OCaml is a great language but still greater can be done.\r\nEspecially, about syntax, I feel every 'delimiting' things should be made easily 'jumpables'.\r\n\r\nThis plugin add a leader j ( \\j ) shortcut allowing to jump from a 'let' to its matching 'in' or the reverse ('in' to 'let').\r\n'let' or 'in' contained in comments or string are subtly ignored.\r\n\r\n###################\r\n\r\nOcaml estas mojosa programlingvo tamen povas ankora\u00c3\u00bb esti pli bona.\r\nSpeciale, pri sintakso, mi pensas ke ĉiuj 'disigiloj' devas esti facile 'salteblaj'.\r\n\r\nTio aldonaĵo proponas klavosignon (ĉefklavo j ( \\j ) ) kiu saltagas la skribmarkon el 'let' al la kongrua 'in' kaj inverso.\r\n'let' a\u00c3\u00bb 'in' entenita en komentoj a\u00c3\u00bb signoĉenoj estas ignorataj.\r\n\r\n\r\n","install_details":"Just put this ocaml.vim in your local vim ftplugin.\r\nVersion 1.0 works with Vim 7.3.\r\nVersion 1.01 works with Vim 7.4.\r\n\r\n##################\r\n\r\nNur enmetu tion ocaml.vim en vian lokan vim-an ftplugin.\r\nVersio 1.0 funkcias kun Vim 7.3.\r\nVersio 1.01 funkcias kun Vim 7.4.","5":"Just put this ocaml.vim in your local vim ftplugin.\r\nVersion 1.0 works with Vim 7.3.\r\nVersion 1.01 works with Vim 7.4.\r\n\r\n##################\r\n\r\nNur enmetu tion ocaml.vim en vian lokan vim-an ftplugin.\r\nVersio 1.0 funkcias kun Vim 7.3.\r\nVersio 1.01 funkcias kun Vim 7.4.","first_name":"Pierre ","6":"Pierre ","last_name":"Vittet","7":"Vittet","releases":[{"0":"4963","vim_version":"7.4","1":"7.4","script_version":"1.01","2":"1.01","version_comment":"This version works with Vim 7.4.\r\nTio versio funkcias kun Vim 7.4.","3":"This version works with Vim 7.4.\r\nTio versio funkcias kun Vim 7.4.","package":"ocaml.vim","4":"ocaml.vim","src_id":"22054","5":"22054","creation_date":"1403108941","6":"1403108941"},{"0":"4963","vim_version":"7.3","1":"7.3","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"ocaml.vim","4":"ocaml.vim","src_id":"22053","5":"22053","creation_date":"1403108687","6":"1403108687"}]},"4962":{"script_id":"4962","0":"4962","script_name":"FileBeagle","1":"FileBeagle","script_type":"utility","2":"utility","summary":"A VINE-spired (Vim Is Not Emacs) file system explorer","3":"A VINE-spired (Vim Is Not Emacs) file system explorer","description":"\r\nFileBeagle is a utility to display a directory listing and select a file for\r\nediting. You can change directories and, if necessary, create new files. Files\r\ncan be opened in new splits or tabs, and new directory catalogs can be spawned.\r\n\r\nAnd that is about it.\r\n\r\nFileBeagle is \"VINE-spired\": that is, inspired by the design principle of \"Vim\r\nIs Not Emacs\".\r\n\r\nVim is a text editor, *not* an operating system that can edit text. FileBeagle\r\nrespects this, and attempts to conform to this both in spirit and in practice.\r\n\r\nIf you are looking for a plugin to serve as a filesystem manager from within\r\nVim, FileBeagle is not it. FileBeagle does not support copying, deleting,\r\nmoving\/renaming, or any other filesystem operations. FileBeagle lists and opens\r\nfiles.\r\n\r\nIf you are looking for a plugin to replicate an operating system shell in Vim,\r\nFileBeagle is not it. FileBeagle does not support `grep`-ing, `find`-ing, or\r\nany of other the other functionality provided by (the *excellent*) programs in\r\nyour operating system environment dedicated to these tasks. FileBeagles lists\r\nand opens files.\r\n\r\nIf you are looking for a plugin that makes Vim resemble some bloated\r\nbells-and-whistles IDE with a billion open \"drawers\", panels, toolbars, and\r\nwindows, FileBeagle is not it. FileBeagle does not provide for fancy\r\nsplits or project drawers. FileBeagle lists and opens files.\r\n\r\n## Overview of Basic Usage\r\n\r\nType '`-`' to open the FileBeagle directory viewer on the directory of the\r\ncurrent buffer. Alternatively, you can use '`f`' to open the FileBeagle\r\ndirectory viewer on the current working directory. This latter key is mapped to\r\nthe command \"`:FileBeagle`\": if the command is used directly, it can actually\r\ntake an optional argument which specifies the path of the directory to open\r\ninstead of the current working directory.\r\n\r\nIn either case, once a directory viewer is open, you can use any of your normal\r\nnavigation keys\/commands to move to a file or directory of your choice. Once\r\nyou have selected a file or directory, you can type `` or \"`o`\" to open\r\nit for editing in the current window. Or you can type `CTRL-V` to edit it in a\r\nnew vertical split, `CTRL-S` to edit it in a new horizontal split, or `CTRL-T`\r\nto edit it in a new tab. Even better, if you make sure that line numbers are\r\nenabled, you can simply type the line number followed by '`o`' or any of the\r\nother maps to instantly open the file or directory listed at the given line\r\nnumber. So, for example, '`42o`' will open the file or directory at line 42 in\r\nthe same window, while '`42v`' (or '`42 CTRL-V`') will open it in a new\r\nvertical split, and '`42t`' (or '`42 CTRL-T`') will open it in a new tab, etc.\r\n\r\nYou can navigate to a directory by selecting it using the same key maps that\r\nyou use to select files. In addition, you can use \"`-`\" to go a parent\r\ndirectory or backspace \"``\" to go back to the previous directory.\r\n\r\nFor each independent invocation of FileBeagle, it remembers the entry which you\r\nlast selected in each directory as your enter or leave directories. Each time\r\nyou return to a directory that you have visited before, the cursor is\r\nautomatically placed at the entry which you selected the just before leaving\r\nthat directory. This means that you can quickly traverse up and down a\r\ndirectory chain by typing \"`-`\" and\/or \"``\". Use \"`-`\" to move up and\r\nup, until you get to the root, and then \"``\" to drill seamlessly back\r\ndown the same path you just traversed until you hit the file from which you\r\ncame. Once you have tried it, you will not want to traverse directories in any\r\nother way (well, except for fuzzy-querying to \"teleport\" you directly where you\r\nwant to go).\r\n\r\nThe only file management functionality provided is to create a new file ('`%`'\r\nor '`+`'). For everything else, use the operating system.\r\n\r\nAt any time, you can type \"`q`\" to close FileBeagle and restore the previous\r\nbuffer.\r\n\r\n","4":"\r\nFileBeagle is a utility to display a directory listing and select a file for\r\nediting. You can change directories and, if necessary, create new files. Files\r\ncan be opened in new splits or tabs, and new directory catalogs can be spawned.\r\n\r\nAnd that is about it.\r\n\r\nFileBeagle is \"VINE-spired\": that is, inspired by the design principle of \"Vim\r\nIs Not Emacs\".\r\n\r\nVim is a text editor, *not* an operating system that can edit text. FileBeagle\r\nrespects this, and attempts to conform to this both in spirit and in practice.\r\n\r\nIf you are looking for a plugin to serve as a filesystem manager from within\r\nVim, FileBeagle is not it. FileBeagle does not support copying, deleting,\r\nmoving\/renaming, or any other filesystem operations. FileBeagle lists and opens\r\nfiles.\r\n\r\nIf you are looking for a plugin to replicate an operating system shell in Vim,\r\nFileBeagle is not it. FileBeagle does not support `grep`-ing, `find`-ing, or\r\nany of other the other functionality provided by (the *excellent*) programs in\r\nyour operating system environment dedicated to these tasks. FileBeagles lists\r\nand opens files.\r\n\r\nIf you are looking for a plugin that makes Vim resemble some bloated\r\nbells-and-whistles IDE with a billion open \"drawers\", panels, toolbars, and\r\nwindows, FileBeagle is not it. FileBeagle does not provide for fancy\r\nsplits or project drawers. FileBeagle lists and opens files.\r\n\r\n## Overview of Basic Usage\r\n\r\nType '`-`' to open the FileBeagle directory viewer on the directory of the\r\ncurrent buffer. Alternatively, you can use '`f`' to open the FileBeagle\r\ndirectory viewer on the current working directory. This latter key is mapped to\r\nthe command \"`:FileBeagle`\": if the command is used directly, it can actually\r\ntake an optional argument which specifies the path of the directory to open\r\ninstead of the current working directory.\r\n\r\nIn either case, once a directory viewer is open, you can use any of your normal\r\nnavigation keys\/commands to move to a file or directory of your choice. Once\r\nyou have selected a file or directory, you can type `` or \"`o`\" to open\r\nit for editing in the current window. Or you can type `CTRL-V` to edit it in a\r\nnew vertical split, `CTRL-S` to edit it in a new horizontal split, or `CTRL-T`\r\nto edit it in a new tab. Even better, if you make sure that line numbers are\r\nenabled, you can simply type the line number followed by '`o`' or any of the\r\nother maps to instantly open the file or directory listed at the given line\r\nnumber. So, for example, '`42o`' will open the file or directory at line 42 in\r\nthe same window, while '`42v`' (or '`42 CTRL-V`') will open it in a new\r\nvertical split, and '`42t`' (or '`42 CTRL-T`') will open it in a new tab, etc.\r\n\r\nYou can navigate to a directory by selecting it using the same key maps that\r\nyou use to select files. In addition, you can use \"`-`\" to go a parent\r\ndirectory or backspace \"``\" to go back to the previous directory.\r\n\r\nFor each independent invocation of FileBeagle, it remembers the entry which you\r\nlast selected in each directory as your enter or leave directories. Each time\r\nyou return to a directory that you have visited before, the cursor is\r\nautomatically placed at the entry which you selected the just before leaving\r\nthat directory. This means that you can quickly traverse up and down a\r\ndirectory chain by typing \"`-`\" and\/or \"``\". Use \"`-`\" to move up and\r\nup, until you get to the root, and then \"``\" to drill seamlessly back\r\ndown the same path you just traversed until you hit the file from which you\r\ncame. Once you have tried it, you will not want to traverse directories in any\r\nother way (well, except for fuzzy-querying to \"teleport\" you directly where you\r\nwant to go).\r\n\r\nThe only file management functionality provided is to create a new file ('`%`'\r\nor '`+`'). For everything else, use the operating system.\r\n\r\nAt any time, you can type \"`q`\" to close FileBeagle and restore the previous\r\nbuffer.\r\n\r\n","install_details":"## Repository is at:\r\n\r\n    https:\/\/github.com\/jeetsukumaran\/vim-filebeagle\r\n\r\n## Pathogen\r\n\r\n    $ cd ~\/.vim\/bundle\r\n    $ git clone git:\/\/github.com\/jeetsukumaran\/vim-filebeagle\r\n    \r\n## Vundle\r\n\r\n    :BundleInstall jeetsukumaran\/vim-filebeagle\r\n\r\n## Manually\r\n\r\nUnpack the archive contents in your \"~\/.vim\/\" directory.\r\n\r\n","5":"## Repository is at:\r\n\r\n    https:\/\/github.com\/jeetsukumaran\/vim-filebeagle\r\n\r\n## Pathogen\r\n\r\n    $ cd ~\/.vim\/bundle\r\n    $ git clone git:\/\/github.com\/jeetsukumaran\/vim-filebeagle\r\n    \r\n## Vundle\r\n\r\n    :BundleInstall jeetsukumaran\/vim-filebeagle\r\n\r\n## Manually\r\n\r\nUnpack the archive contents in your \"~\/.vim\/\" directory.\r\n\r\n","first_name":"Jeet","6":"Jeet","last_name":"Sukumaran","7":"Sukumaran","releases":[{"0":"4962","vim_version":"7.0","1":"7.0","script_version":"2.0.0","2":"2.0.0","version_comment":"A complete overhaul of interface, with much more streamlined (and configurable) key mappings within FileBeagle buffer instances, as well as significant architectural changes and bug fixes. Thanks to justinmk for helping with critical feedback, reviews, and suggestions. ","3":"A complete overhaul of interface, with much more streamlined (and configurable) key mappings within FileBeagle buffer instances, as well as significant architectural changes and bug fixes. Thanks to justinmk for helping with critical feedback, reviews, and suggestions. ","package":"vim-filebeagle-v2.0.0.tar.gz","4":"vim-filebeagle-v2.0.0.tar.gz","src_id":"22813","5":"22813","creation_date":"1421723714","6":"1421723714"},{"0":"4962","vim_version":"7.0","1":"7.0","script_version":"1.0.0","2":"1.0.0","version_comment":"Initial upload","3":"Initial upload","package":"vim-filebeagle-v1.0.0.tar.gz","4":"vim-filebeagle-v1.0.0.tar.gz","src_id":"22051","5":"22051","creation_date":"1403066445","6":"1403066445"}]},"4961":{"script_id":"4961","0":"4961","script_name":"SmartColumnColor","1":"SmartColumnColor","script_type":"utility","2":"utility","summary":"vim plugin for alert when we reach a defined numbers of characters in a line","3":"vim plugin for alert when we reach a defined numbers of characters in a line","description":"This plugin alert us when we reach a defined amount of characters per line.\r\n\r\nInstead of showing a line over all the content, showing the limit, SmartColumnColors displays a bg\/fg distinctive for that character in particular.\r\n","4":"This plugin alert us when we reach a defined amount of characters per line.\r\n\r\nInstead of showing a line over all the content, showing the limit, SmartColumnColors displays a bg\/fg distinctive for that character in particular.\r\n","install_details":"if you use janus or pathogen, clone the repository under .bundle or .janus in your home directory :\r\n git clone git@github.com:gagoar\/SmartColumnColors.git\r\n\r\nre open your vim\/mvim ","5":"if you use janus or pathogen, clone the repository under .bundle or .janus in your home directory :\r\n git clone git@github.com:gagoar\/SmartColumnColors.git\r\n\r\nre open your vim\/mvim ","first_name":"German","6":"German","last_name":"Frigerio","7":"Frigerio","releases":[{"0":"4961","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"SmartColumnColors.zip","4":"SmartColumnColors.zip","src_id":"22039","5":"22039","creation_date":"1402955367","6":"1402955367"}]},"4960":{"script_id":"4960","0":"4960","script_name":"Kerbal Space Program Syntax","1":"Kerbal Space Program Syntax","script_type":"syntax","2":"syntax","summary":"Simple syntax highlighting for Kerbal Space Program saves and .craft files.","3":"Simple syntax highlighting for Kerbal Space Program saves and .craft files.","description":"Simple syntax highlighting for Kerbal Space Program saves and .craft files.\r\nSource files can be found at https:\/\/github.com\/mic47\/KSP-Syntax","4":"Simple syntax highlighting for Kerbal Space Program saves and .craft files.\r\nSource files can be found at https:\/\/github.com\/mic47\/KSP-Syntax","install_details":"Extract in the directory where is your .vim directory.","5":"Extract in the directory where is your .vim directory.","first_name":"Michal","6":"Michal","last_name":"N\u00c3\u00a1n\u00c3\u00a1si","7":"N\u00c3\u00a1n\u00c3\u00a1si","releases":[{"0":"4960","vim_version":"7.0","1":"7.0","script_version":"0.2","2":"0.2","version_comment":"Added handling of .craft files, added comment highlighting, operators and separators (,:; in lists of numbers).","3":"Added handling of .craft files, added comment highlighting, operators and separators (,:; in lists of numbers).","package":"craft.zip","4":"craft.zip","src_id":"22113","5":"22113","creation_date":"1404153956","6":"1404153956"},{"0":"4960","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"craft.zip","4":"craft.zip","src_id":"22028","5":"22028","creation_date":"1402862180","6":"1402862180"}]},"4959":{"script_id":"4959","0":"4959","script_name":"vimf90+","1":"vimf90+","script_type":"ftplugin","2":"ftplugin","summary":"  A fortran-90+ plugin for easy editing","3":"  A fortran-90+ plugin for easy editing","description":"This is a plugin for editing fortran-90+. It gives keymapping for writing f90+ codes with ease.\r\nThe latest plugin will always be available at https:\/\/github.com\/rudrab\/vimf90\r\n\r\nThis is heavily under development. Kindly update, comment, suggest and check :h vimf90+List regularly\r\nNB: Note the change in name. its now vimf90, rather then vimf90+, as github doesn't  accept + as its last letter","4":"This is a plugin for editing fortran-90+. It gives keymapping for writing f90+ codes with ease.\r\nThe latest plugin will always be available at https:\/\/github.com\/rudrab\/vimf90\r\n\r\nThis is heavily under development. Kindly update, comment, suggest and check :h vimf90+List regularly\r\nNB: Note the change in name. its now vimf90, rather then vimf90+, as github doesn't  accept + as its last letter","install_details":"Install it with a plugin manager. Checked with vundle. but PATHOGEN should also do.","5":"Install it with a plugin manager. Checked with vundle. but PATHOGEN should also do.","first_name":"Rudra","6":"Rudra","last_name":"Banerjee","7":"Banerjee","releases":[{"0":"4959","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"many more functionality added","3":"many more functionality added","package":"vimf90.tar.gz","4":"vimf90.tar.gz","src_id":"22095","5":"22095","creation_date":"1403692196","6":"1403692196"},{"0":"4959","vim_version":"7.0","1":"7.0","script_version":".5","2":".5","version_comment":"Some addition, syncing the commands etc","3":"Some addition, syncing the commands etc","package":"vimf90.tar.gz","4":"vimf90.tar.gz","src_id":"22044","5":"22044","creation_date":"1403019365","6":"1403019365"},{"0":"4959","vim_version":"7.0","1":"7.0","script_version":".1","2":".1","version_comment":"Initial upload","3":"Initial upload","package":"vimf90+.tar.gz","4":"vimf90+.tar.gz","src_id":"22027","5":"22027","creation_date":"1402823068","6":"1402823068"}]},"4958":{"script_id":"4958","0":"4958","script_name":"AdvancedSorters","1":"AdvancedSorters","script_type":"utility","2":"utility","summary":"Sorting of certain areas or by special needs.","3":"Sorting of certain areas or by special needs.","description":"DESCRIPTION\r\nThe built-in :sort command is powerful, but it still is line-based. It\r\ndoesn't take into account folded lines, nor can it sort entire blocks like\r\nfunction definitions, paragraphs, etc. But often, one needs to sort exactly\r\nsuch areas as single entities, i.e. without changing the line order within\r\nthem. A workaround in Vim is condensing each block into a single line,\r\nperforming the sorting, and then expanding again. (External, more powerful\r\nsort commands could be used, too.)\r\n\r\nThis plugin implements this workaround and encapsulates the three separate\r\nsteps in one handy command.\r\n\r\nWhile :sort has several flags for sorting on various numbers, and a\r\n\/{pattern}\/ can be specified to skip or sort on, it doesn't allow arbitrary\r\n(Vimscript) expressions.\r\n\r\nThis plugin offers extension commands that evaluate an expression per line,\r\nput that number in front of the line, do a numerical sort, and then remove the\r\ntemporary number again. Specializations handle the common sort by number of\r\ncharacters and by the line's display width.\r\n\r\nSOURCE\r\n- :SortVisible inspired by\r\n  http:\/\/stackoverflow.com\/questions\/13554191\/sorting-vim-folds\r\n- :SortRangesByRange inspired by\r\n  http:\/\/superuser.com\/questions\/752032\/how-do-i-sort-multiple-blocks-of-text-by-the-first-line-in-each-block-in-vim\r\n- :SortByExpr inspired by\r\n  http:\/\/stackoverflow.com\/questions\/11531073\/how-do-you-sort-a-range-of-lines-by-length\r\n- :SortWORDs inspired by\r\n  http:\/\/stackoverflow.com\/questions\/26739697\/sort-line-horizontally-in-vim\r\n  http:\/\/stackoverflow.com\/questions\/1327978\/sorting-words-not-lines-in-vim\r\n\r\nSEE ALSO\r\n- The LineJuggler.vim plugin (vimscript #4140) offers many quick mappings to\r\n  move around (blocks of) lines. For small data sets, manual shifting may be\r\n  quicker than coming up with a correct sort command.\r\n\r\nUSAGE\r\n:[range]SortVisible[!] [i][u][r][n][x][o] [\/{pattern}\/]\r\n                        Sort visible lines in the buffer \/ [range]. Lines\r\n                        inside closed folds are kept intact; sorting is done\r\n                        on all lines of the fold as one unit; i.e. the order\r\n                        of the other lines inside the fold does _not_ change!\r\n\r\n:[range]SortRangesByHeader[!] \/{expr}\/ [i][u][r][n][x][o] [\/{pattern}\/]\r\n                        Each match of {expr} (in the buffer \/ [range]) starts\r\n                        a new area that sorts as one unit; i.e. the order of\r\n                        the other lines inside the area does _not_ change!\r\n                        Lines before the first header are sorted individually.\r\n\r\n:[range]SortRangesByMatch[!] \/{expr}\/ [i][u][r][n][x][o] [\/{pattern}\/]\r\n                        Each (multi-line) match of {expr} (in the buffer \/\r\n                        [range]) defines an area that sorts as one unit,\r\n                        together with individual non-matching lines.\r\n\r\n:[range]SortRangesByRange[!] {range} [i][u][r][n][x][o] [\/{pattern}\/]\r\n                        Each {range} (in the buffer \/ [range]) defines an area\r\n                        that sorts as one unit.\r\n                        Note: For this command, \/{pattern}\/ must be separated\r\n                        from the {range} by a [i][u][r][n][x][o] flag or a\r\n                        space; you cannot directly concatenate them.\r\n\r\n                        Note: The text must not contain embedded \r\n                        characters (^@) for the above commands!\r\n\r\n:[range]ReorderVisible {reorder-expr}\r\n                        Reorder visible lines in the buffer \/ [range] by\r\n                        collecting into a List of Strings (multiple folded\r\n                        lines are joined with newlines) and passing it (as\r\n                        v:val) to {reorder-expr}.\r\n\r\n:[range]ReorderFolded {reorder-expr}\r\n                        Reorder folded lines in the buffer \/ [range] by\r\n                        collecting into a List of Strings (multiple folded\r\n                        lines are joined with newlines) and passing it (as\r\n                        v:val) to {reorder-expr}. Those are then re-inserted\r\n                        in between any unfolded lines, which stay as they\r\n                        were.\r\n\r\n:[range]ReorderUnfolded {reorder-expr}\r\n                        Reorder unfolded lines in the buffer \/ [range] by\r\n                        collecting into a List of Strings (subsequent unfolded\r\n                        lines are joined with newlines) and passing it (as\r\n                        v:val) to {reorder-expr}. Those are then re-inserted\r\n                        in between any closed folds, which stay as they were.\r\n\r\n:[range]ReorderByHeader \/{expr}\/ {reorder-expr}\r\n                        Each match of {expr} (in the buffer \/ [range]) starts\r\n                        a new area that is reordered as one unit (joined with\r\n                        newlines) by passing it (as v:val) to {reorder-expr}.\r\n                        Lines before the first header are reordered as another\r\n                        single unit.\r\n\r\n:[range]ReorderOnlyByMatch \/{expr}\/ {reorder-expr}\r\n                        Each (multi-line) match of {expr} (in the buffer \/\r\n                        [range]) defines an area that is reordered as one unit\r\n                        (joined with newlines) by passing it (as v:val) to\r\n                        {reorder-expr}. Those are then re-inserted in between\r\n                        any non-matching lines, which stay as they were.\r\n\r\n:[range]ReorderByMatchAndNonMatches \/{expr}\/ {reorder-expr}\r\n                        Each (multi-line) match of {expr} (in the buffer \/\r\n                        [range]) defines an area that is reordered as one unit\r\n                        (joined with newlines), together with units of\r\n                        non-matching lines, by passing it (as v:val) to\r\n                        {reorder-expr}.\r\n\r\n:[range]ReorderByMatchAndLines \/{expr}\/ {reorder-expr}\r\n                        Each (multi-line) match of {expr} (in the buffer \/\r\n                        [range]) defines an area that is reordered as one unit\r\n                        (joined with newlines), together with individual\r\n                        non-matching lines, by passing it (as v:val) to\r\n                        {reorder-expr}.\r\n\r\n:[range]ReorderOnlyByRange {range} {reorder-expr}\r\n                        Each {range} (in the buffer \/ [range]) defines an area\r\n                        that is reordered as one unit (joined with newlines),\r\n                        by passing it (as v:val) to {reorder-expr}. Those are\r\n                        then re-inserted in between any non-matching lines,\r\n                        which stay as they were.\r\n\r\n:[range]ReorderByRangeAndNonMatches {range} {reorder-expr}\r\n                        Each {range} (in the buffer \/ [range]) defines an area\r\n                        that is reordered as one unit (joined with newlines),\r\n                        together with individual non-matching lines, by\r\n                        passing it (as v:val) to {reorder-expr}.\r\n\r\n:[range]ReorderByRangeAndLines {range} {reorder-expr}\r\n                        Each {range} (in the buffer \/ [range]) defines an area\r\n                        that is reordered as one unit (joined with newlines),\r\n                        together with individual non-matching lines, by\r\n                        passing it (as v:val) to {reorder-expr}.\r\n\r\n:[range]SortByExpr[!] {expr}\r\n                        Sort lines in [range] by the {expr}, which should take\r\n                        the current line as input via v:val and return a\r\n                        number. With [!] the order is reversed.\r\n\r\n:[range]SortByExprUnique[!] {expr}\r\n                        Sort lines in [range] by the {expr}; only the first\r\n                        line that gets a certain number from {expr} is kept.\r\n                        With [!] the order is reversed.\r\n\r\n:[range]SortByCharLength[!]\r\n                        Sort lines in [range] by the number of characters.\r\n\r\n:[range]SortByWidth[!]\r\n                        Sort lines in [range] by the display width.\r\n\r\n:[range]SortEach \/{delimiter-pattern}\/[{joiner}\/]\r\n:[range]SortEach \/{delimiter-pattern}\/[{joiner}]\/ [i][u][r][n][x][o] \/{pattern}\/\r\n                        Sort individual elements delimited by\r\n                        {delimiter-pattern} (or newlines) in the current line\r\n                        \/ [range], and join them back together with the first\r\n                        matching delimiter [or {joiner}].\r\n\r\n:[range]SortWORDs[!] [i][u][r][n][x][o] [\/{pattern}\/]\r\n                        Sort individual (whitespace-delimited) WORDs in the\r\n                        current line \/ [range].\r\n\r\n:[range]UniqAny [i][r] [\/{pattern}\/]\r\n                        Remove lines in [range] that have already been\r\n                        encountered earlier (not necessarily adjacent).\r\n                        With [i] case is ignored.\r\n                        When \/{pattern}\/ is specified and there is no [r] flag\r\n                        the text matched with {pattern} is ignored.\r\n                        With [r] only the matching {pattern} is considered;\r\n                        the rest is ignored.\r\n                        If a {pattern} is used, any lines which don't have a\r\n                        match for {pattern} are kept.\r\n\r\n:[range]UniqSubsequent [i][r] [\/{pattern}\/]\r\n                        Remove second and succeeding copies of repeated\r\n                        adjacent lines in [range].\r\n                        With [i] case is ignored.\r\n                        When \/{pattern}\/ is specified and there is no [r] flag\r\n                        the text matched with {pattern} is ignored.\r\n                        With [r] only the matching {pattern} is considered;\r\n                        the rest is ignored.\r\n                        If a {pattern} is used, any lines which don't have a\r\n                        match for {pattern} are kept.\r\n\r\nEXAMPLE\r\nWe're taking any Vimscript file with multiple function definitions as an\r\nexample, and show how to sort whole functions according to function name (and\r\narguments).\r\n\r\nTo use folding, we first have to define the folds, then trigger the sorting:\r\n    :g\/^function\/,\/^endfunction\/fold\r\n    :SortVisible\r\n\r\nIf we don't care about including any lines after the \"endfunction\", we can\r\njust base the areas on the function start:\r\n    :SortRangesByHeader \/^function\/\r\nBut we'll get better results with an explicit end. One way is to define a\r\nmulti-line pattern that covers the entire function:\r\n    :SortRangesByMatch \/^function\\_.\\{-}\\nendfunction$\/\r\nAnother way spans up a range, similar to what we've done above to define the\r\nfolds:\r\n    :SortRangesByRange \/^function\/,\/^endfunction$\/","4":"DESCRIPTION\r\nThe built-in :sort command is powerful, but it still is line-based. It\r\ndoesn't take into account folded lines, nor can it sort entire blocks like\r\nfunction definitions, paragraphs, etc. But often, one needs to sort exactly\r\nsuch areas as single entities, i.e. without changing the line order within\r\nthem. A workaround in Vim is condensing each block into a single line,\r\nperforming the sorting, and then expanding again. (External, more powerful\r\nsort commands could be used, too.)\r\n\r\nThis plugin implements this workaround and encapsulates the three separate\r\nsteps in one handy command.\r\n\r\nWhile :sort has several flags for sorting on various numbers, and a\r\n\/{pattern}\/ can be specified to skip or sort on, it doesn't allow arbitrary\r\n(Vimscript) expressions.\r\n\r\nThis plugin offers extension commands that evaluate an expression per line,\r\nput that number in front of the line, do a numerical sort, and then remove the\r\ntemporary number again. Specializations handle the common sort by number of\r\ncharacters and by the line's display width.\r\n\r\nSOURCE\r\n- :SortVisible inspired by\r\n  http:\/\/stackoverflow.com\/questions\/13554191\/sorting-vim-folds\r\n- :SortRangesByRange inspired by\r\n  http:\/\/superuser.com\/questions\/752032\/how-do-i-sort-multiple-blocks-of-text-by-the-first-line-in-each-block-in-vim\r\n- :SortByExpr inspired by\r\n  http:\/\/stackoverflow.com\/questions\/11531073\/how-do-you-sort-a-range-of-lines-by-length\r\n- :SortWORDs inspired by\r\n  http:\/\/stackoverflow.com\/questions\/26739697\/sort-line-horizontally-in-vim\r\n  http:\/\/stackoverflow.com\/questions\/1327978\/sorting-words-not-lines-in-vim\r\n\r\nSEE ALSO\r\n- The LineJuggler.vim plugin (vimscript #4140) offers many quick mappings to\r\n  move around (blocks of) lines. For small data sets, manual shifting may be\r\n  quicker than coming up with a correct sort command.\r\n\r\nUSAGE\r\n:[range]SortVisible[!] [i][u][r][n][x][o] [\/{pattern}\/]\r\n                        Sort visible lines in the buffer \/ [range]. Lines\r\n                        inside closed folds are kept intact; sorting is done\r\n                        on all lines of the fold as one unit; i.e. the order\r\n                        of the other lines inside the fold does _not_ change!\r\n\r\n:[range]SortRangesByHeader[!] \/{expr}\/ [i][u][r][n][x][o] [\/{pattern}\/]\r\n                        Each match of {expr} (in the buffer \/ [range]) starts\r\n                        a new area that sorts as one unit; i.e. the order of\r\n                        the other lines inside the area does _not_ change!\r\n                        Lines before the first header are sorted individually.\r\n\r\n:[range]SortRangesByMatch[!] \/{expr}\/ [i][u][r][n][x][o] [\/{pattern}\/]\r\n                        Each (multi-line) match of {expr} (in the buffer \/\r\n                        [range]) defines an area that sorts as one unit,\r\n                        together with individual non-matching lines.\r\n\r\n:[range]SortRangesByRange[!] {range} [i][u][r][n][x][o] [\/{pattern}\/]\r\n                        Each {range} (in the buffer \/ [range]) defines an area\r\n                        that sorts as one unit.\r\n                        Note: For this command, \/{pattern}\/ must be separated\r\n                        from the {range} by a [i][u][r][n][x][o] flag or a\r\n                        space; you cannot directly concatenate them.\r\n\r\n                        Note: The text must not contain embedded \r\n                        characters (^@) for the above commands!\r\n\r\n:[range]ReorderVisible {reorder-expr}\r\n                        Reorder visible lines in the buffer \/ [range] by\r\n                        collecting into a List of Strings (multiple folded\r\n                        lines are joined with newlines) and passing it (as\r\n                        v:val) to {reorder-expr}.\r\n\r\n:[range]ReorderFolded {reorder-expr}\r\n                        Reorder folded lines in the buffer \/ [range] by\r\n                        collecting into a List of Strings (multiple folded\r\n                        lines are joined with newlines) and passing it (as\r\n                        v:val) to {reorder-expr}. Those are then re-inserted\r\n                        in between any unfolded lines, which stay as they\r\n                        were.\r\n\r\n:[range]ReorderUnfolded {reorder-expr}\r\n                        Reorder unfolded lines in the buffer \/ [range] by\r\n                        collecting into a List of Strings (subsequent unfolded\r\n                        lines are joined with newlines) and passing it (as\r\n                        v:val) to {reorder-expr}. Those are then re-inserted\r\n                        in between any closed folds, which stay as they were.\r\n\r\n:[range]ReorderByHeader \/{expr}\/ {reorder-expr}\r\n                        Each match of {expr} (in the buffer \/ [range]) starts\r\n                        a new area that is reordered as one unit (joined with\r\n                        newlines) by passing it (as v:val) to {reorder-expr}.\r\n                        Lines before the first header are reordered as another\r\n                        single unit.\r\n\r\n:[range]ReorderOnlyByMatch \/{expr}\/ {reorder-expr}\r\n                        Each (multi-line) match of {expr} (in the buffer \/\r\n                        [range]) defines an area that is reordered as one unit\r\n                        (joined with newlines) by passing it (as v:val) to\r\n                        {reorder-expr}. Those are then re-inserted in between\r\n                        any non-matching lines, which stay as they were.\r\n\r\n:[range]ReorderByMatchAndNonMatches \/{expr}\/ {reorder-expr}\r\n                        Each (multi-line) match of {expr} (in the buffer \/\r\n                        [range]) defines an area that is reordered as one unit\r\n                        (joined with newlines), together with units of\r\n                        non-matching lines, by passing it (as v:val) to\r\n                        {reorder-expr}.\r\n\r\n:[range]ReorderByMatchAndLines \/{expr}\/ {reorder-expr}\r\n                        Each (multi-line) match of {expr} (in the buffer \/\r\n                        [range]) defines an area that is reordered as one unit\r\n                        (joined with newlines), together with individual\r\n                        non-matching lines, by passing it (as v:val) to\r\n                        {reorder-expr}.\r\n\r\n:[range]ReorderOnlyByRange {range} {reorder-expr}\r\n                        Each {range} (in the buffer \/ [range]) defines an area\r\n                        that is reordered as one unit (joined with newlines),\r\n                        by passing it (as v:val) to {reorder-expr}. Those are\r\n                        then re-inserted in between any non-matching lines,\r\n                        which stay as they were.\r\n\r\n:[range]ReorderByRangeAndNonMatches {range} {reorder-expr}\r\n                        Each {range} (in the buffer \/ [range]) defines an area\r\n                        that is reordered as one unit (joined with newlines),\r\n                        together with individual non-matching lines, by\r\n                        passing it (as v:val) to {reorder-expr}.\r\n\r\n:[range]ReorderByRangeAndLines {range} {reorder-expr}\r\n                        Each {range} (in the buffer \/ [range]) defines an area\r\n                        that is reordered as one unit (joined with newlines),\r\n                        together with individual non-matching lines, by\r\n                        passing it (as v:val) to {reorder-expr}.\r\n\r\n:[range]SortByExpr[!] {expr}\r\n                        Sort lines in [range] by the {expr}, which should take\r\n                        the current line as input via v:val and return a\r\n                        number. With [!] the order is reversed.\r\n\r\n:[range]SortByExprUnique[!] {expr}\r\n                        Sort lines in [range] by the {expr}; only the first\r\n                        line that gets a certain number from {expr} is kept.\r\n                        With [!] the order is reversed.\r\n\r\n:[range]SortByCharLength[!]\r\n                        Sort lines in [range] by the number of characters.\r\n\r\n:[range]SortByWidth[!]\r\n                        Sort lines in [range] by the display width.\r\n\r\n:[range]SortEach \/{delimiter-pattern}\/[{joiner}\/]\r\n:[range]SortEach \/{delimiter-pattern}\/[{joiner}]\/ [i][u][r][n][x][o] \/{pattern}\/\r\n                        Sort individual elements delimited by\r\n                        {delimiter-pattern} (or newlines) in the current line\r\n                        \/ [range], and join them back together with the first\r\n                        matching delimiter [or {joiner}].\r\n\r\n:[range]SortWORDs[!] [i][u][r][n][x][o] [\/{pattern}\/]\r\n                        Sort individual (whitespace-delimited) WORDs in the\r\n                        current line \/ [range].\r\n\r\n:[range]UniqAny [i][r] [\/{pattern}\/]\r\n                        Remove lines in [range] that have already been\r\n                        encountered earlier (not necessarily adjacent).\r\n                        With [i] case is ignored.\r\n                        When \/{pattern}\/ is specified and there is no [r] flag\r\n                        the text matched with {pattern} is ignored.\r\n                        With [r] only the matching {pattern} is considered;\r\n                        the rest is ignored.\r\n                        If a {pattern} is used, any lines which don't have a\r\n                        match for {pattern} are kept.\r\n\r\n:[range]UniqSubsequent [i][r] [\/{pattern}\/]\r\n                        Remove second and succeeding copies of repeated\r\n                        adjacent lines in [range].\r\n                        With [i] case is ignored.\r\n                        When \/{pattern}\/ is specified and there is no [r] flag\r\n                        the text matched with {pattern} is ignored.\r\n                        With [r] only the matching {pattern} is considered;\r\n                        the rest is ignored.\r\n                        If a {pattern} is used, any lines which don't have a\r\n                        match for {pattern} are kept.\r\n\r\nEXAMPLE\r\nWe're taking any Vimscript file with multiple function definitions as an\r\nexample, and show how to sort whole functions according to function name (and\r\narguments).\r\n\r\nTo use folding, we first have to define the folds, then trigger the sorting:\r\n    :g\/^function\/,\/^endfunction\/fold\r\n    :SortVisible\r\n\r\nIf we don't care about including any lines after the \"endfunction\", we can\r\njust base the areas on the function start:\r\n    :SortRangesByHeader \/^function\/\r\nBut we'll get better results with an explicit end. One way is to define a\r\nmulti-line pattern that covers the entire function:\r\n    :SortRangesByMatch \/^function\\_.\\{-}\\nendfunction$\/\r\nAnother way spans up a range, similar to what we've done above to define the\r\nfolds:\r\n    :SortRangesByRange \/^function\/,\/^endfunction$\/","install_details":"INSTALLATION\r\nThe code is hosted in a Git repo at\r\n    https:\/\/github.com\/inkarkat\/vim-AdvancedSorters\r\nYou can use your favorite plugin manager, or \"git clone\" into a directory used\r\nfor Vim packages. Releases are on the \"stable\" branch, the latest unstable\r\ndevelopment snapshot on \"master\".\r\n\r\nThis script is also packaged as a vimball. If you have the \"gunzip\"\r\ndecompressor in your PATH, simply edit the *.vmb.gz package in Vim; otherwise,\r\ndecompress the archive first, e.g. using WinZip. Inside Vim, install by\r\nsourcing the vimball or via the :UseVimball command.\r\n    vim AdvancedSorters*.vmb.gz\r\n    :so %\r\nTo uninstall, use the :RmVimball command.\r\n\r\nDEPENDENCIES\r\n- Requires Vim 7.0 or higher.\r\n- Requires the ingo-library.vim plugin (vimscript #4433), version 1.039 or\r\n  higher.","5":"INSTALLATION\r\nThe code is hosted in a Git repo at\r\n    https:\/\/github.com\/inkarkat\/vim-AdvancedSorters\r\nYou can use your favorite plugin manager, or \"git clone\" into a directory used\r\nfor Vim packages. Releases are on the \"stable\" branch, the latest unstable\r\ndevelopment snapshot on \"master\".\r\n\r\nThis script is also packaged as a vimball. If you have the \"gunzip\"\r\ndecompressor in your PATH, simply edit the *.vmb.gz package in Vim; otherwise,\r\ndecompress the archive first, e.g. using WinZip. Inside Vim, install by\r\nsourcing the vimball or via the :UseVimball command.\r\n    vim AdvancedSorters*.vmb.gz\r\n    :so %\r\nTo uninstall, use the :RmVimball command.\r\n\r\nDEPENDENCIES\r\n- Requires Vim 7.0 or higher.\r\n- Requires the ingo-library.vim plugin (vimscript #4433), version 1.039 or\r\n  higher.","first_name":"Ingo","6":"Ingo","last_name":"Karkat","7":"Karkat","releases":[{"0":"4958","vim_version":"7.0","1":"7.0","script_version":"1.30","2":"1.30","version_comment":"- CHG: Rename :Uniq to :UniqAny and add :UniqSubsequent variant.\r\n- Add :SortEach generalization of :SortWORDs.\r\n- CHG: Rename :SortUnfolded to :SortVisible.\r\n- ENH: Add various :ReorderBy... commands that mirror the :SortVisible and :SortRangedBy... commands, but allow arbitrary reorderings via a Vimscript expression. *** You need to update to ingo-library (vimscript #4433) version 1.039! ***","3":"- CHG: Rename :Uniq to :UniqAny and add :UniqSubsequent variant.\r\n- Add :SortEach generalization of :SortWORDs.\r\n- CHG: Rename :SortUnfolded to :SortVisible.\r\n- ENH: Add various :ReorderBy... commands that mirror the :SortVisible and :SortRangedBy... commands, but allow arbitrary reorderings via a Vimscript expression. *** You need to update to ingo-library (vimscript #4433) version 1.039! ***","package":"AdvancedSorters-1.30.vmb.gz","4":"AdvancedSorters-1.30.vmb.gz","src_id":"26955","5":"26955","creation_date":"1580765757","6":"1580765757"},{"0":"4958","vim_version":"7.0","1":"7.0","script_version":"1.21","2":"1.21","version_comment":"- BUG: :SortUnfolded and :SortRangedBy... remove comment sigils (like \"#\") when 'formatoptions' contains \"j\". Temporarily reset 'formatoptions' to avoid interference of user settings. Thanks to Holger Mitschke for reporting this!","3":"- BUG: :SortUnfolded and :SortRangedBy... remove comment sigils (like \"#\") when 'formatoptions' contains \"j\". Temporarily reset 'formatoptions' to avoid interference of user settings. Thanks to Holger Mitschke for reporting this!","package":"AdvancedSorters-1.21.vmb.gz","4":"AdvancedSorters-1.21.vmb.gz","src_id":"24671","5":"24671","creation_date":"1477497438","6":"1477497438"},{"0":"4958","vim_version":"7.0","1":"7.0","script_version":"1.20","2":"1.20","version_comment":"- Add :Uniq command.\r\n- Also support [\/{pattern}\/] [i][u][r][n][x][o] :sort argument order (and mixed).\r\n- FIX: Include missing Words.vim module that prevented the :SortWORDs command introduced in the previous version 1.10 from functioning.","3":"- Add :Uniq command.\r\n- Also support [\/{pattern}\/] [i][u][r][n][x][o] :sort argument order (and mixed).\r\n- FIX: Include missing Words.vim module that prevented the :SortWORDs command introduced in the previous version 1.10 from functioning.","package":"AdvancedSorters-1.20.vmb.gz","4":"AdvancedSorters-1.20.vmb.gz","src_id":"22896","5":"22896","creation_date":"1423481303","6":"1423481303"},{"0":"4958","vim_version":"7.0","1":"7.0","script_version":"1.10","2":"1.10","version_comment":"- Add :SortWORDs command.","3":"- Add :SortWORDs command.","package":"AdvancedSorters-1.10.vmb.gz","4":"AdvancedSorters-1.10.vmb.gz","src_id":"22718","5":"22718","creation_date":"1419333543","6":"1419333543"},{"0":"4958","vim_version":"7.0","1":"7.0","script_version":"1.02","2":"1.02","version_comment":"- BUG: :.SortRangesBy... doesn't work correctly on a closed fold; need to use ingo#range#NetStart(). *** You need to update to ingo-library (vimscript #4433) version 1.022! ***","3":"- BUG: :.SortRangesBy... doesn't work correctly on a closed fold; need to use ingo#range#NetStart(). *** You need to update to ingo-library (vimscript #4433) version 1.022! ***","package":"AdvancedSorters-1.02.vmb.gz","4":"AdvancedSorters-1.02.vmb.gz","src_id":"22606","5":"22606","creation_date":"1415279560","6":"1415279560"},{"0":"4958","vim_version":"7.0","1":"7.0","script_version":"1.01","2":"1.01","version_comment":"- Make :SortRangesByRange work for Vim versions before 7.4.218 that don't have uniq(). *** You need to update to ingo-library (vimscript #4433) version 1.021! ***","3":"- Make :SortRangesByRange work for Vim versions before 7.4.218 that don't have uniq(). *** You need to update to ingo-library (vimscript #4433) version 1.021! ***","package":"AdvancedSorters-1.01.vmb.gz","4":"AdvancedSorters-1.01.vmb.gz","src_id":"22181","5":"22181","creation_date":"1404984559","6":"1404984559"},{"0":"4958","vim_version":"7.0","1":"7.0","script_version":"1.00","2":"1.00","version_comment":"Initial upload","3":"Initial upload","package":"AdvancedSorters-1.00.vmb.gz","4":"AdvancedSorters-1.00.vmb.gz","src_id":"22015","5":"22015","creation_date":"1402476477","6":"1402476477"}]},"4957":{"script_id":"4957","0":"4957","script_name":"zeavim","1":"zeavim","script_type":"utility","2":"utility","summary":"Execute the documentation browser Zeal from Vim","3":"Execute the documentation browser Zeal from Vim","description":"Zeavim allows to use the offline documentation browser Zeal(http:\/\/zealdocs.org) from Vim.\r\n\r\n# Features:\r\n    * Search for word under cursor, a motion or a visual selection.\r\n    * Search without losing focus from Vim if Zeal is already opened (Need wmctrl on UNIX).\r\n    * Possibility to specify dynamically a docset.\r\n    * Narrow search with a query.\r\n    * Allows using multiple docsets.\r\n    * Docset name completion.\r\n    * Define you own docsets using file types, extentions or regex.\r\n    * Supports docsets specific to file names (e.g gulpfile.js)\r\n    * Works on GNU\/Linux and Windows.\r\n\r\nYou'll find the last version on https:\/\/github.com\/KabbAmine\/zeavim.vim\r\nDon't forget to rate it if you find it useful ( Or useless ;) ).\r\n\r\nusage\r\n=====\r\n\r\n1. z\r\n    Search for word under cursor with the docset defined automatically.\r\n\r\n2. gz{motion}\r\n    Search for a motion with the docset defined automatically.\r\n\r\n3. z\r\n    Narrow search with a docset and a query (A default docset is provided).\r\n        - Multiple docsets can be defined, just separate them by a comma.\r\n        - The docset name can be completed using tab, see completion for that.\r\n\r\nPlease refer to the documentation(https:\/\/github.com\/KabbAmine\/zeavim.vim\/blob\/master\/doc\/zeavim.txt)  or the README file(https:\/\/github.com\/KabbAmine\/zeavim.vim\/blob\/master\/README.md) for more informations and how to configure zeavim.\r\n","4":"Zeavim allows to use the offline documentation browser Zeal(http:\/\/zealdocs.org) from Vim.\r\n\r\n# Features:\r\n    * Search for word under cursor, a motion or a visual selection.\r\n    * Search without losing focus from Vim if Zeal is already opened (Need wmctrl on UNIX).\r\n    * Possibility to specify dynamically a docset.\r\n    * Narrow search with a query.\r\n    * Allows using multiple docsets.\r\n    * Docset name completion.\r\n    * Define you own docsets using file types, extentions or regex.\r\n    * Supports docsets specific to file names (e.g gulpfile.js)\r\n    * Works on GNU\/Linux and Windows.\r\n\r\nYou'll find the last version on https:\/\/github.com\/KabbAmine\/zeavim.vim\r\nDon't forget to rate it if you find it useful ( Or useless ;) ).\r\n\r\nusage\r\n=====\r\n\r\n1. z\r\n    Search for word under cursor with the docset defined automatically.\r\n\r\n2. gz{motion}\r\n    Search for a motion with the docset defined automatically.\r\n\r\n3. z\r\n    Narrow search with a docset and a query (A default docset is provided).\r\n        - Multiple docsets can be defined, just separate them by a comma.\r\n        - The docset name can be completed using tab, see completion for that.\r\n\r\nPlease refer to the documentation(https:\/\/github.com\/KabbAmine\/zeavim.vim\/blob\/master\/doc\/zeavim.txt)  or the README file(https:\/\/github.com\/KabbAmine\/zeavim.vim\/blob\/master\/README.md) for more informations and how to configure zeavim.\r\n","install_details":"Manual installation\r\n~~~~~~~~~~~~~~~\r\nInstall the distributed files into Vim runtime directory which is usually `~\/.vim\/`, or `$HOME\/vimfiles` on Windows.\r\n\r\nUsing Pathogen\r\n~~~~~~~~~~~~~\r\nSimply extract the file into `bundle` directory.\r\n\r\nUsing Vundle\r\n~~~~~~~~~~~~~\r\nJust add the following line in the Vundle part of your vimrc\r\n    Plugin 'KabbAmine\/zeavim.vim'\r\nThen proceed to the installation of the plugin with the following command:\r\n    :PluginInstall","5":"Manual installation\r\n~~~~~~~~~~~~~~~\r\nInstall the distributed files into Vim runtime directory which is usually `~\/.vim\/`, or `$HOME\/vimfiles` on Windows.\r\n\r\nUsing Pathogen\r\n~~~~~~~~~~~~~\r\nSimply extract the file into `bundle` directory.\r\n\r\nUsing Vundle\r\n~~~~~~~~~~~~~\r\nJust add the following line in the Vundle part of your vimrc\r\n    Plugin 'KabbAmine\/zeavim.vim'\r\nThen proceed to the installation of the plugin with the following command:\r\n    :PluginInstall","first_name":"Kabbaj","6":"Kabbaj","last_name":"Amine","7":"Amine","releases":[{"0":"4957","vim_version":"7.0","1":"7.0","script_version":"2.1.0","2":"2.1.0","version_comment":"* New feature: Search for a motion using ZVMotion\r\n* Internal refactoring\r\n* Bug fix","3":"* New feature: Search for a motion using ZVMotion\r\n* Internal refactoring\r\n* Bug fix","package":"zeavim.tar.gz","4":"zeavim.tar.gz","src_id":"23897","5":"23897","creation_date":"1452674218","6":"1452674218"},{"0":"4957","vim_version":"7.0","1":"7.0","script_version":"2.0.1","2":"2.0.1","version_comment":"2.0.1\r\n    DEGRADATION: Fix the issue where default mappings were not working\r\n    Fix code example in the documentation\r\n2.0.0\r\n    Big refactoring\r\n    Update documentation and screens\r\n    Add a version badge and use now semantic versionning\r\n    Changes:\r\n        Remove ZVKeyword and ZvK command, the functionality is natively supported by ZVKeyDocset\r\n    Features:\r\n        Supports docsets for specific file names\r\n        Don't lose focus anymore on Unix if Zeal is opened (Needs wmtcrl)\r\n        Allows using regex in g:zv_file_types\r\n        Allows using multiple docsets with multiple completion for Docset","3":"2.0.1\r\n    DEGRADATION: Fix the issue where default mappings were not working\r\n    Fix code example in the documentation\r\n2.0.0\r\n    Big refactoring\r\n    Update documentation and screens\r\n    Add a version badge and use now semantic versionning\r\n    Changes:\r\n        Remove ZVKeyword and ZvK command, the functionality is natively supported by ZVKeyDocset\r\n    Features:\r\n        Supports docsets for specific file names\r\n        Don't lose focus anymore on Unix if Zeal is opened (Needs wmtcrl)\r\n        Allows using regex in g:zv_file_types\r\n        Allows using multiple docsets with multiple completion for Docset","package":"zeavim.tar.gz","4":"zeavim.tar.gz","src_id":"23824","5":"23824","creation_date":"1450893955","6":"1450893955"},{"0":"4957","vim_version":"7.0","1":"7.0","script_version":"1.4.4","2":"1.4.4","version_comment":"* Some refactoring\r\n* Update documentation\r\n* Add a CHANGELOG\r\n### Changes\r\n* Rename g:zv_added_files_type to g:zv_file_types\r\n* Rename g:zv_zeal_directory to g:zv_zeal_executable","3":"* Some refactoring\r\n* Update documentation\r\n* Add a CHANGELOG\r\n### Changes\r\n* Rename g:zv_added_files_type to g:zv_file_types\r\n* Rename g:zv_zeal_directory to g:zv_zeal_executable","package":"zeavim.tar.gz","4":"zeavim.tar.gz","src_id":"23619","5":"23619","creation_date":"1443372385","6":"1443372385"},{"0":"4957","vim_version":"7.0","1":"7.0","script_version":"1.4.2","2":"1.4.2","version_comment":"Follow zeal 0.1.0 changes:\r\n- No more --query in zeal's command.\r\n- Docsets names are now in lower case.","3":"Follow zeal 0.1.0 changes:\r\n- No more --query in zeal's command.\r\n- Docsets names are now in lower case.","package":"zeavim.tar.gz","4":"zeavim.tar.gz","src_id":"23189","5":"23189","creation_date":"1429298685","6":"1429298685"},{"0":"4957","vim_version":"7.0","1":"7.0","script_version":"1.4","2":"1.4","version_comment":"Update to v1.4:\r\n- New option added: g:docsets_dir > Specify zeal docsets directory for automatic command completion.\r\n- Add docset completion to ZvKeyDocset (\\\\z).\r\n- Shows now docset name after calling ZVKeyDocset (\\\\z).\r\n- No more simple quotes in Windows in zeal's query.\r\n- Doc updated.\r\n- Some refactoring & code cleaning.\r\n\r\n","3":"Update to v1.4:\r\n- New option added: g:docsets_dir > Specify zeal docsets directory for automatic command completion.\r\n- Add docset completion to ZvKeyDocset (\\\\z).\r\n- Shows now docset name after calling ZVKeyDocset (\\\\z).\r\n- No more simple quotes in Windows in zeal's query.\r\n- Doc updated.\r\n- Some refactoring & code cleaning.\r\n\r\n","package":"zeavim.tar.gz","4":"zeavim.tar.gz","src_id":"23081","5":"23081","creation_date":"1427018625","6":"1427018625"},{"0":"4957","vim_version":"7.0","1":"7.0","script_version":"1.3","2":"1.3","version_comment":"- Change key mapping process: g:zv_disable_mapping works now just as it should be.\r\n- Correct script variable name.","3":"- Change key mapping process: g:zv_disable_mapping works now just as it should be.\r\n- Correct script variable name.","package":"zeavim.tar.gz","4":"zeavim.tar.gz","src_id":"22930","5":"22930","creation_date":"1424498560","6":"1424498560"},{"0":"4957","vim_version":"7.0","1":"7.0","script_version":"1.2","2":"1.2","version_comment":"- Add completion when using the command Docset\r\n- You can also add docset names for the competion in g:zv_lazy_docset_list\r\n","3":"- Add completion when using the command Docset\r\n- You can also add docset names for the competion in g:zv_lazy_docset_list\r\n","package":"zeavim.tar.gz","4":"zeavim.tar.gz","src_id":"22669","5":"22669","creation_date":"1417697712","6":"1417697712"},{"0":"4957","vim_version":"7.0","1":"7.0","script_version":"1.1","2":"1.1","version_comment":"- No more latency, the plugin works instantly.\r\n- Add a way to specify manually a docset (:Docset).\r\n- Documentation updated.\r\n- Clean the code.\r\n","3":"- No more latency, the plugin works instantly.\r\n- Add a way to specify manually a docset (:Docset).\r\n- Documentation updated.\r\n- Clean the code.\r\n","package":"zeavim.tar.gz","4":"zeavim.tar.gz","src_id":"22473","5":"22473","creation_date":"1412248375","6":"1412248375"},{"0":"4957","vim_version":"7.0","1":"7.0","script_version":"1.0.3","2":"1.0.3","version_comment":"Symbolic update to 1.0.3:\r\n- Clear vim screen after calling zeavim (For tmux).\r\n- Possibility to disable default mappings added.\r\n- Commands for main functions added. ","3":"Symbolic update to 1.0.3:\r\n- Clear vim screen after calling zeavim (For tmux).\r\n- Possibility to disable default mappings added.\r\n- Commands for main functions added. ","package":"zeavim.tar.gz","4":"zeavim.tar.gz","src_id":"22358","5":"22358","creation_date":"1408798337","6":"1408798337"},{"0":"4957","vim_version":"7.0","1":"7.0","script_version":"1.0.2","2":"1.0.2","version_comment":"Put the cursor in his initial position after Zeal visual calling.","3":"Put the cursor in his initial position after Zeal visual calling.","package":"zeavim.tar.gz","4":"zeavim.tar.gz","src_id":"22281","5":"22281","creation_date":"1406833554","6":"1406833554"},{"0":"4957","vim_version":"7.0","1":"7.0","script_version":"1.0.1","2":"1.0.1","version_comment":"No changes, the 0.1 is simply for an updated doc. ","3":"No changes, the 0.1 is simply for an updated doc. ","package":"zeavim.tar.gz","4":"zeavim.tar.gz","src_id":"22017","5":"22017","creation_date":"1402482990","6":"1402482990"},{"0":"4957","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"zeavim.tar.gz","4":"zeavim.tar.gz","src_id":"22003","5":"22003","creation_date":"1402299630","6":"1402299630"}]},"4956":{"script_id":"4956","0":"4956","script_name":"vimbed","1":"vimbed","script_type":"utility","2":"utility","summary":"A plugin for embedding vim","3":"A plugin for embedding vim","description":"Vimbed is a Vim plugin for embedding Vim in other programs.\r\n\r\nRun Vim in the background using Vimbed to ease communication with external processes.\r\n\r\nProjects that use Vimbed:\r\n    Pterosaur embeds Vim in Firefox textboxes.\r\n    Chalcogen embeds Vim in the Atom editor.\r\n\r\nSee http:\/\/github.com\/ardagnir\/vimbed for more info.\r\n","4":"Vimbed is a Vim plugin for embedding Vim in other programs.\r\n\r\nRun Vim in the background using Vimbed to ease communication with external processes.\r\n\r\nProjects that use Vimbed:\r\n    Pterosaur embeds Vim in Firefox textboxes.\r\n    Chalcogen embeds Vim in the Atom editor.\r\n\r\nSee http:\/\/github.com\/ardagnir\/vimbed for more info.\r\n","install_details":"Install vimbed with your favorite plugin-manager. If you use pathogen:\r\n    cd ~\/.vim\/bundle\r\n    git clone http:\/\/github.com\/ardagnir\/vimbed","5":"Install vimbed with your favorite plugin-manager. If you use pathogen:\r\n    cd ~\/.vim\/bundle\r\n    git clone http:\/\/github.com\/ardagnir\/vimbed","first_name":"James","6":"James","last_name":"Kolb","7":"Kolb","releases":[{"0":"4956","vim_version":"7.0","1":"7.0","script_version":"0.2","2":"0.2","version_comment":"New name\/api names.","3":"New name\/api names.","package":"vimbed.tar.gz","4":"vimbed.tar.gz","src_id":"22050","5":"22050","creation_date":"1403062224","6":"1403062224"},{"0":"4956","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"shadowvim.tar.gz","4":"shadowvim.tar.gz","src_id":"22002","5":"22002","creation_date":"1402297004","6":"1402297004"}]},"4955":{"script_id":"4955","0":"4955","script_name":"Merginal","1":"Merginal","script_type":"utility","2":"utility","summary":"Fugitive extention to manage and merge Git branches","3":"Fugitive extention to manage and merge Git branches","description":"GitHub repository: https:\/\/github.com\/idanarye\/vim-merginal\r\n\r\nMerginal aims provide a nice inteface for dealing with Git branches. It offers interactive TUI for:\r\n\r\n* Viewing the list of branches\r\n* Checking out branches from that list\r\n* Creating new branches\r\n* Deleting branches\r\n* Merging branches\r\n* Solving merge conflicts\r\n* Interacting with remotes(pulling, pushing, fetching, tracking)\r\n* Diffing against other branches\r\n* Renaming branches","4":"GitHub repository: https:\/\/github.com\/idanarye\/vim-merginal\r\n\r\nMerginal aims provide a nice inteface for dealing with Git branches. It offers interactive TUI for:\r\n\r\n* Viewing the list of branches\r\n* Checking out branches from that list\r\n* Creating new branches\r\n* Deleting branches\r\n* Merging branches\r\n* Solving merge conflicts\r\n* Interacting with remotes(pulling, pushing, fetching, tracking)\r\n* Diffing against other branches\r\n* Renaming branches","install_details":"","5":"","first_name":"Idan","6":"Idan","last_name":"Arye","7":"Arye","releases":[{"0":"4955","vim_version":"7.0","1":"7.0","script_version":"2.2.3","2":"2.2.3","version_comment":"### Fixed\r\n- Remove a stray echo when generating help for the various Merginal buffers.\r\n","3":"### Fixed\r\n- Remove a stray echo when generating help for the various Merginal buffers.\r\n","package":"merginal_v2.2.3.zip","4":"merginal_v2.2.3.zip","src_id":"28241","5":"28241","creation_date":"1667089042","6":"1667089042"},{"0":"4955","vim_version":"7.3","1":"7.3","script_version":"2.2.2","2":"2.2.2","version_comment":"- Replace fugitive#repo() usage with Fugitives standalone functions.","3":"- Replace fugitive#repo() usage with Fugitives standalone functions.","package":"merginal_v2.2.2.zip","4":"merginal_v2.2.2.zip","src_id":"28198","5":"28198","creation_date":"1664958900","6":"1664958900"},{"0":"4955","vim_version":"7.3","1":"7.3","script_version":"2.2.1","2":"2.2.1","version_comment":"Fixes:\r\n- Use FugitiveShellCommand instead of repo.git_command (which is deprecated by Fugitive)\r\n- Use Git merge instead of Gmerge (which is deprecated by Fugitive)","3":"Fixes:\r\n- Use FugitiveShellCommand instead of repo.git_command (which is deprecated by Fugitive)\r\n- Use Git merge instead of Gmerge (which is deprecated by Fugitive)","package":"merginal_v2.2.1.zip","4":"merginal_v2.2.1.zip","src_id":"27819","5":"27819","creation_date":"1637989721","6":"1637989721"},{"0":"4955","vim_version":"7.3","1":"7.3","script_version":"2.2.0","2":"2.2.0","version_comment":"- Support separate Meginal buffers on multiple tabs.\r\n- Added merginal_remoteVisible variable to set remote branches to be viewed by default.\r\n- Added a hotkey 'tr' to toggle remote branches in the view.\r\n- Calling `Merginal` or `MerginalToggle` when the merginal buffer is open but not in the main mode (branch list by default, or changes if in special Git status) will:\r\n  - Jump to it, if the user is in another window.\r\n  - Change it to the main mode, if the user is in it.\r\n","3":"- Support separate Meginal buffers on multiple tabs.\r\n- Added merginal_remoteVisible variable to set remote branches to be viewed by default.\r\n- Added a hotkey 'tr' to toggle remote branches in the view.\r\n- Calling `Merginal` or `MerginalToggle` when the merginal buffer is open but not in the main mode (branch list by default, or changes if in special Git status) will:\r\n  - Jump to it, if the user is in another window.\r\n  - Change it to the main mode, if the user is in it.\r\n","package":"merginal_v2.2.0.zip","4":"merginal_v2.2.0.zip","src_id":"27395","5":"27395","creation_date":"1607321215","6":"1607321215"},{"0":"4955","vim_version":"7.3","1":"7.3","script_version":"2.1.2","2":"2.1.2","version_comment":"\r\n    Made merginal commands global, not buffer-local, because Fugutive no longer fires the signals Merginal depended on.\r\n    Changed fugitive#detect to FugitiveDetect.\r\n    Made pS push with --force-with-lease instead of just --force. Yes, this is a fix. No this is not a breaking change. If this breaks your workflow then your workflow was broken to begin with.\r\n    Made all the mappings .\r\n","3":"\r\n    Made merginal commands global, not buffer-local, because Fugutive no longer fires the signals Merginal depended on.\r\n    Changed fugitive#detect to FugitiveDetect.\r\n    Made pS push with --force-with-lease instead of just --force. Yes, this is a fix. No this is not a breaking change. If this breaks your workflow then your workflow was broken to begin with.\r\n    Made all the mappings .\r\n","package":"merginal_v2.1.2.zip","4":"merginal_v2.1.2.zip","src_id":"26948","5":"26948","creation_date":"1580358256","6":"1580358256"},{"0":"4955","vim_version":"7.3","1":"7.3","script_version":"2.1.1","2":"2.1.1","version_comment":"* Fix fileFullPath bug.\r\n* Fix order of arguments when merging.\r\n* Limit amount of commits displayed. This is considered a bugfix and not a feature because the only reason for\r\nlimiting the commit was performance.\r\n* Fix a typo in historyLog.vim.","3":"* Fix fileFullPath bug.\r\n* Fix order of arguments when merging.\r\n* Limit amount of commits displayed. This is considered a bugfix and not a feature because the only reason for\r\nlimiting the commit was performance.\r\n* Fix a typo in historyLog.vim.","package":"merginal_v2.1.1.zip","4":"merginal_v2.1.1.zip","src_id":"26734","5":"26734","creation_date":"1567803465","6":"1567803465"},{"0":"4955","vim_version":"7.3","1":"7.3","script_version":"2.1.0","2":"2.1.0","version_comment":"New features:\r\n* Add NERDTree style keymaps for opening files\r\n* Use committer date instead of author date in historyLog\r\n* Allow setting the Merginal window width\r\n* Add option to split vertically\/horizontally\r\n* Add merginal_windowSize configuration\r\n\r\nFixes:\r\n* Use exception number instead of string\r\n* Fix try catch to has_key\r\n* Add missing merge commands to mergeConflicts buffer\r\n* Pushing when there are multiple remotes\r\n* Keymaps leaking between buffers\r\n* Add -- after commands to solve branch\/path ambiguity\r\n* Fix command running for Vim8 with :terminal support","3":"New features:\r\n* Add NERDTree style keymaps for opening files\r\n* Use committer date instead of author date in historyLog\r\n* Allow setting the Merginal window width\r\n* Add option to split vertically\/horizontally\r\n* Add merginal_windowSize configuration\r\n\r\nFixes:\r\n* Use exception number instead of string\r\n* Fix try catch to has_key\r\n* Add missing merge commands to mergeConflicts buffer\r\n* Pushing when there are multiple remotes\r\n* Keymaps leaking between buffers\r\n* Add -- after commands to solve branch\/path ambiguity\r\n* Fix command running for Vim8 with :terminal support","package":"merginal_v2.1.0.zip","4":"merginal_v2.1.0.zip","src_id":"25628","5":"25628","creation_date":"1509232250","6":"1509232250"},{"0":"4955","vim_version":"7.3","1":"7.3","script_version":"2.0.2","2":"2.0.2","version_comment":"Fix refresh - prevent it from modifying other windows","3":"Fix refresh - prevent it from modifying other windows","package":"merginal_v2.0.2.zip","4":"merginal_v2.0.2.zip","src_id":"24315","5":"24315","creation_date":"1465425334","6":"1465425334"},{"0":"4955","vim_version":"7.3","1":"7.3","script_version":"2.0.1","2":"2.0.1","version_comment":"* Add the missing open-conflicted-file command from v1\r\n* Fix the way filtering works in history log","3":"* Add the missing open-conflicted-file command from v1\r\n* Fix the way filtering works in history log","package":"merginal_v2.0.1.zip","4":"merginal_v2.0.1.zip","src_id":"24218","5":"24218","creation_date":"1462053556","6":"1462053556"},{"0":"4955","vim_version":"7.3","1":"7.3","script_version":"2.0.0","2":"2.0.0","version_comment":"Merginal 2.0.0!\r\n\r\n* Huge refactor - moving to object model\r\n* Add built-in help(pressing ?)\r\n* Add filtering(pressing &)\r\n* Minor bug fixes","3":"Merginal 2.0.0!\r\n\r\n* Huge refactor - moving to object model\r\n* Add built-in help(pressing ?)\r\n* Add filtering(pressing &)\r\n* Minor bug fixes","package":"merginal_v2.0.0.zip","4":"merginal_v2.0.0.zip","src_id":"24163","5":"24163","creation_date":"1460217693","6":"1460217693"},{"0":"4955","vim_version":"7.0","1":"7.0","script_version":"1.6.0","2":"1.6.0","version_comment":"* Add mn keymap for merging with --no-ff\r\n* Add keymap and conflict-resolving mode for cherry-picking\r\n* Fix a bug where failure to do an operation would mess up the Vim windows","3":"* Add mn keymap for merging with --no-ff\r\n* Add keymap and conflict-resolving mode for cherry-picking\r\n* Fix a bug where failure to do an operation would mess up the Vim windows","package":"merginal_v1.6.0.zip","4":"merginal_v1.6.0.zip","src_id":"23613","5":"23613","creation_date":"1443031187","6":"1443031187"},{"0":"4955","vim_version":"7.0","1":"7.0","script_version":"1.5.0","2":"1.5.0","version_comment":"Add the history log buffer(`gl` from the branch list), which allows:\r\n * Viewing the commit history of a branch\r\n * Viewing information on each commit\r\n * Checking out commits\r\n * Diffing against commits\r\n\r\nOther changes:\r\n * Add `pr` keymap for `pull --rebase`\r\n * Add `q` keymap for closing the side-buffers\r\n * Minor typo fixes and output\/doc styling changes","3":"Add the history log buffer(`gl` from the branch list), which allows:\r\n * Viewing the commit history of a branch\r\n * Viewing information on each commit\r\n * Checking out commits\r\n * Diffing against commits\r\n\r\nOther changes:\r\n * Add `pr` keymap for `pull --rebase`\r\n * Add `q` keymap for closing the side-buffers\r\n * Minor typo fixes and output\/doc styling changes","package":"merginal_v1.5.0.zip","4":"merginal_v1.5.0.zip","src_id":"22916","5":"22916","creation_date":"1423940520","6":"1423940520"},{"0":"4955","vim_version":"7.0","1":"7.0","script_version":"1.4.0","2":"1.4.0","version_comment":"- Add the `rn` keymap for renaming branches\r\n- Add a buffer type for `rebase-amend`\r\n- Add `pS` command for force pushing branches","3":"- Add the `rn` keymap for renaming branches\r\n- Add a buffer type for `rebase-amend`\r\n- Add `pS` command for force pushing branches","package":"merginal_v1.4.0.zip","4":"merginal_v1.4.0.zip","src_id":"22442","5":"22442","creation_date":"1411128501","6":"1411128501"},{"0":"4955","vim_version":"7.0","1":"7.0","script_version":"1.3.0","2":"1.3.0","version_comment":"- Add the `rb` keymap to start a rebase.\r\n  - The rebase buffer supports the merge buffer\\'s keymaps(`R`, ``,\r\n    `aa`, `A`).\r\n  - The rebase buffer also support `ra` to abort the rebase, `rc` to\r\n    continue to the next patch and `rs` to skip the current patch.\r\n- Add `MerginalToggle` command to toggle the merginal buffer.\r\n- Add `MerginalClose` command to close the merginal buffer.\r\n- Support `ps`, `pl` and `pf` directly on remote branches.\r\n- Fix a bug with non-linear merges that don\\'t have merge conflicts.","3":"- Add the `rb` keymap to start a rebase.\r\n  - The rebase buffer supports the merge buffer\\'s keymaps(`R`, ``,\r\n    `aa`, `A`).\r\n  - The rebase buffer also support `ra` to abort the rebase, `rc` to\r\n    continue to the next patch and `rs` to skip the current patch.\r\n- Add `MerginalToggle` command to toggle the merginal buffer.\r\n- Add `MerginalClose` command to close the merginal buffer.\r\n- Support `ps`, `pl` and `pf` directly on remote branches.\r\n- Fix a bug with non-linear merges that don\\'t have merge conflicts.","package":"merginal_v1.3.0.zip","4":"merginal_v1.3.0.zip","src_id":"22314","5":"22314","creation_date":"1407762577","6":"1407762577"},{"0":"4955","vim_version":"7.0","1":"7.0","script_version":"1.2.0","2":"1.2.0","version_comment":" - Add the `mf` keymap to run Fugitive's `:Gmerge`\r\n - Add `merginal#branchDetails` for better parsing of the branch info\r\n - Add `ct` and `cT` for tracking remote branches\r\n - Add `ps`,`pl` and `pf` to push, pull and fetch branches\r\n - Make `dd` be able to delete remote branches\r\n - `bd` in the branch list opens the diff files buffer to diff against the\r\n   selected branch.","3":" - Add the `mf` keymap to run Fugitive's `:Gmerge`\r\n - Add `merginal#branchDetails` for better parsing of the branch info\r\n - Add `ct` and `cT` for tracking remote branches\r\n - Add `ps`,`pl` and `pf` to push, pull and fetch branches\r\n - Make `dd` be able to delete remote branches\r\n - `bd` in the branch list opens the diff files buffer to diff against the\r\n   selected branch.","package":"merginal_v1.2.0.zip","4":"merginal_v1.2.0.zip","src_id":"22164","5":"22164","creation_date":"1404769529","6":"1404769529"},{"0":"4955","vim_version":"7.0","1":"7.0","script_version":"1.1.0","2":"1.1.0","version_comment":"Made it more plugin-friendly","3":"Made it more plugin-friendly","package":"merginal_v1.1.0.zip","4":"merginal_v1.1.0.zip","src_id":"21992","5":"21992","creation_date":"1402083827","6":"1402083827"},{"0":"4955","vim_version":"7.0","1":"7.0","script_version":"1.0.0","2":"1.0.0","version_comment":"Initial upload","3":"Initial upload","package":"merginal_v1.0.0.zip","4":"merginal_v1.0.0.zip","src_id":"21985","5":"21985","creation_date":"1401900466","6":"1401900466"}]},"4954":{"script_id":"4954","0":"4954","script_name":"purpledrop","1":"purpledrop","script_type":"color scheme","2":"color scheme","summary":"dark purple backdrop nice for coding","3":"dark purple backdrop nice for coding","description":"Suffusions of mostly yellow and violet on calm deep purple backdrop.","4":"Suffusions of mostly yellow and violet on calm deep purple backdrop.","install_details":"Drop into colors subdirectory and :colo purpledrop","5":"Drop into colors subdirectory and :colo purpledrop","first_name":"Stephen","6":"Stephen","last_name":"Klump","7":"Klump","releases":[{"0":"4954","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"purpledrop.vim","4":"purpledrop.vim","src_id":"21983","5":"21983","creation_date":"1401819818","6":"1401819818"}]},"4953":{"script_id":"4953","0":"4953","script_name":"dubs-green","1":"dubs-green","script_type":"color scheme","2":"color scheme","summary":"dubs-scheme gone green","3":"dubs-scheme gone green","description":"This is an other member of the dubs scheme group.","4":"This is an other member of the dubs scheme group.","install_details":"Download to vim file to your ...\/color folder.","5":"Download to vim file to your ...\/color folder.","first_name":"Gabor","6":"Gabor","last_name":"Urban","7":"Urban","releases":[{"0":"4953","vim_version":"7.2","1":"7.2","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"dubs_green.vim","4":"dubs_green.vim","src_id":"21980","5":"21980","creation_date":"1401700219","6":"1401700219"}]},"4952":{"script_id":"4952","0":"4952","script_name":"dubs-red","1":"dubs-red","script_type":"color scheme","2":"color scheme","summary":"A reddish version of the dubs scheme","3":"A reddish version of the dubs scheme","description":"This scheme is similar to dubs-scheme with a red flavor.\r\n\r\nCredit to Alexander A. Evstyugov-Babaev for the scheme aiseered which gave me ideas to experiment in this direction.","4":"This scheme is similar to dubs-scheme with a red flavor.\r\n\r\nCredit to Alexander A. Evstyugov-Babaev for the scheme aiseered which gave me ideas to experiment in this direction.","install_details":"Download this file to your ..\/color folder.","5":"Download this file to your ..\/color folder.","first_name":"Gabor","6":"Gabor","last_name":"Urban","7":"Urban","releases":[{"0":"4952","vim_version":"7.2","1":"7.2","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"dubs_red.vim","4":"dubs_red.vim","src_id":"21979","5":"21979","creation_date":"1401699684","6":"1401699684"}]},"4951":{"script_id":"4951","0":"4951","script_name":"caniuse.vim","1":"caniuse.vim","script_type":"utility","2":"utility","summary":"Quickly search caniuse.com from vim","3":"Quickly search caniuse.com from vim","description":"This plugin allows you to perform searches on caniuse.com directly from vim.\r\n\r\nRepository and issues: https:\/\/github.com\/zoeesilcock\/vim-caniuse\r\n\r\n\r\nUsage\r\n\r\nYou can trigger a search from normal mode in which case it will pick the word under the cursor or you can trigger it from visual mode which will search for the selection.\r\n\r\nThe built in mapping is:\r\n\r\n  ciu\r\n\r\nYou can also use command mode:\r\n\r\n  :Caniuse border-radius\r\n\r\n\r\nMappings\r\n\r\nYou can disable the built in mapping by adding this to your .vimrc:\r\n\r\n  let g:caniuse_no_mappings = 1\r\n\r\nIf you want to setup your own key mappings use the following:\r\n\r\nNcaniuse          For normal mode.\r\nVcaniuse          For visual mode.\r\n\r\nFor example:\r\n\r\n  :nmap foo Ncaniuse\r\n  :vmap foo Vcaniuse\r\n\r\nNote: Using :noremap will not work with  mappings.\r\n\r\n\r\nRequirements\r\n\r\nThe plugin should work out of the box on most systems, but opening a URL in your web browser requires an external program. The plugin will do it's best to find the built in command on your system. On Linux it assumes that you have xdg-open which is installed by default on most distributions (it's part of the xdg-utils package in case you happen to not have it).\r\n\r\nIf the plugin fails to find the right command or you want to use another one you can specify the command in your .vimrc file:\r\n\r\n  let g:caniuse_browser_command = 'open'\r\n\r\nThe command you put here will be called with the URL as a parameter.","4":"This plugin allows you to perform searches on caniuse.com directly from vim.\r\n\r\nRepository and issues: https:\/\/github.com\/zoeesilcock\/vim-caniuse\r\n\r\n\r\nUsage\r\n\r\nYou can trigger a search from normal mode in which case it will pick the word under the cursor or you can trigger it from visual mode which will search for the selection.\r\n\r\nThe built in mapping is:\r\n\r\n  ciu\r\n\r\nYou can also use command mode:\r\n\r\n  :Caniuse border-radius\r\n\r\n\r\nMappings\r\n\r\nYou can disable the built in mapping by adding this to your .vimrc:\r\n\r\n  let g:caniuse_no_mappings = 1\r\n\r\nIf you want to setup your own key mappings use the following:\r\n\r\nNcaniuse          For normal mode.\r\nVcaniuse          For visual mode.\r\n\r\nFor example:\r\n\r\n  :nmap foo Ncaniuse\r\n  :vmap foo Vcaniuse\r\n\r\nNote: Using :noremap will not work with  mappings.\r\n\r\n\r\nRequirements\r\n\r\nThe plugin should work out of the box on most systems, but opening a URL in your web browser requires an external program. The plugin will do it's best to find the built in command on your system. On Linux it assumes that you have xdg-open which is installed by default on most distributions (it's part of the xdg-utils package in case you happen to not have it).\r\n\r\nIf the plugin fails to find the right command or you want to use another one you can specify the command in your .vimrc file:\r\n\r\n  let g:caniuse_browser_command = 'open'\r\n\r\nThe command you put here will be called with the URL as a parameter.","install_details":"","5":"","first_name":"Zoee","6":"Zoee","last_name":"Silcock","7":"Silcock","releases":[{"0":"4951","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"vim-caniuse.zip","4":"vim-caniuse.zip","src_id":"21975","5":"21975","creation_date":"1401644156","6":"1401644156"}]},"4950":{"script_id":"4950","0":"4950","script_name":"Lua Support 2","1":"Lua Support 2","script_type":"utility","2":"utility","summary":"Lua IDE -- Insert code snippets, run and check the code and look up help","3":"Lua IDE -- Insert code snippets, run and check the code and look up help","description":"Speed-up the development of Lua scripts:\r\n\r\n- insert code snippets: comments, statements, functions, regular expressions, ...\r\n- ... which come in an extendible template library\r\n- quickly comment the code by automatically generating function descriptions\r\n- run or compile the code from within Vim\r\n- run the syntax checker\r\n- quick access to the online reference manual\r\n- ... or read the manual inside Vim\r\n- make integration\r\n\r\nSome screen shots :  http:\/\/wolfgangmehner.github.io\/vim-plugins\/luasupport.html\r\n\r\nFor plug-in managers :  https:\/\/github.com\/WolfgangMehner\/lua-support\r\n\r\nThe help file online :  http:\/\/wolfgangmehner.github.io\/vim-plugins\/doc\/luasupport.html\r\n\r\nWhile this plug-in is conceived as a successor of the original lua-support ( https:\/\/www.vim.org\/scripts\/script.php?script_id=1763 ), backwards compatibility is not guaranteed.\r\nHowever, we hope that the better configurability through the template library and other new features make for a product which is much better suited to deal with a language like Lua.\r\n\r\n\r\nDOCUMENTATION\r\n--------------------------------------------------------\r\nThis plug-in comes with a help file (luasupport.txt). Read it with\r\n\r\n    :help luasupport\r\n\r\nGitHub\r\n--------------------------------------------------------\r\nLua-Support is on GitHub. We are happy to receive your questions, suggestions, and bug reports here:\r\n\r\n    https:\/\/github.com\/WolfgangMehner\/vim-plugins\r\n\r\n(Please help us keep track of all the issues and name your report\/request \"Lua-Support: \")","4":"Speed-up the development of Lua scripts:\r\n\r\n- insert code snippets: comments, statements, functions, regular expressions, ...\r\n- ... which come in an extendible template library\r\n- quickly comment the code by automatically generating function descriptions\r\n- run or compile the code from within Vim\r\n- run the syntax checker\r\n- quick access to the online reference manual\r\n- ... or read the manual inside Vim\r\n- make integration\r\n\r\nSome screen shots :  http:\/\/wolfgangmehner.github.io\/vim-plugins\/luasupport.html\r\n\r\nFor plug-in managers :  https:\/\/github.com\/WolfgangMehner\/lua-support\r\n\r\nThe help file online :  http:\/\/wolfgangmehner.github.io\/vim-plugins\/doc\/luasupport.html\r\n\r\nWhile this plug-in is conceived as a successor of the original lua-support ( https:\/\/www.vim.org\/scripts\/script.php?script_id=1763 ), backwards compatibility is not guaranteed.\r\nHowever, we hope that the better configurability through the template library and other new features make for a product which is much better suited to deal with a language like Lua.\r\n\r\n\r\nDOCUMENTATION\r\n--------------------------------------------------------\r\nThis plug-in comes with a help file (luasupport.txt). Read it with\r\n\r\n    :help luasupport\r\n\r\nGitHub\r\n--------------------------------------------------------\r\nLua-Support is on GitHub. We are happy to receive your questions, suggestions, and bug reports here:\r\n\r\n    https:\/\/github.com\/WolfgangMehner\/vim-plugins\r\n\r\n(Please help us keep track of all the issues and name your report\/request \"Lua-Support: <title>\")","install_details":"Copy the zip archive lua-support.zip to $HOME\/.vim\/ (Linux\/Unix) or\r\n$HOME\/vimfiles (Windows) and run:\r\n    unzip lua-support.zip\r\n\r\nRedo the helptags (Linux\/Windows):\r\n    :helptags $HOME\/.vim\/doc\/\r\n    :helptags $HOME\\vimfiles\\doc\\\r\n\r\nYou might have to set the correct executable. See lua-support\/README.md or:\r\n    :help g:Lua_Executable\r\n(the default is \"lua\")\r\n\r\nTo install the templates for Lua's C-API, please consult:\r\n    :help luasupport-usage-capi","5":"Copy the zip archive lua-support.zip to $HOME\/.vim\/ (Linux\/Unix) or\r\n$HOME\/vimfiles (Windows) and run:\r\n    unzip lua-support.zip\r\n\r\nRedo the helptags (Linux\/Windows):\r\n    :helptags $HOME\/.vim\/doc\/\r\n    :helptags $HOME\\vimfiles\\doc\\\r\n\r\nYou might have to set the correct executable. See lua-support\/README.md or:\r\n    :help g:Lua_Executable\r\n(the default is \"lua\")\r\n\r\nTo install the templates for Lua's C-API, please consult:\r\n    :help luasupport-usage-capi","first_name":"Wolfgang","6":"Wolfgang","last_name":"Mehner","7":"Mehner","releases":[{"0":"4950","vim_version":"7.3","1":"7.3","script_version":"1.0","2":"1.0","version_comment":"- The default style used by the template library is now 'Lua_52'.\r\n  You can change it in the template customization file (see below).\r\n  The jump to the online help is also set up for Lua 5.2.\r\n- Rename 'g:Lua_GlbTemplateFile' into 'g:Lua_GlobalTemplateFile'.\r\n- Rename 'g:Lua_LclTemplateFile' into 'g:Lua_LocalTemplateFile'.\r\n- Add optional custom templates 'g:Lua_CustomTemplateFile'.\r\n- Add template personalization file and setup wizard.\r\n- Add Lua's reference manual in Vim's help format.\r\n- Add maps and menu entries to jump to it conveniently.\r\n- New and improved templates, add Lua 5.3.\r\n- Add Lua C-API templates.\r\n- Fix running and compiling scripts under Windows.\r\n- Minor improvements.","3":"- The default style used by the template library is now 'Lua_52'.\r\n  You can change it in the template customization file (see below).\r\n  The jump to the online help is also set up for Lua 5.2.\r\n- Rename 'g:Lua_GlbTemplateFile' into 'g:Lua_GlobalTemplateFile'.\r\n- Rename 'g:Lua_LclTemplateFile' into 'g:Lua_LocalTemplateFile'.\r\n- Add optional custom templates 'g:Lua_CustomTemplateFile'.\r\n- Add template personalization file and setup wizard.\r\n- Add Lua's reference manual in Vim's help format.\r\n- Add maps and menu entries to jump to it conveniently.\r\n- New and improved templates, add Lua 5.3.\r\n- Add Lua C-API templates.\r\n- Fix running and compiling scripts under Windows.\r\n- Minor improvements.","package":"lua-support.zip","4":"lua-support.zip","src_id":"24447","5":"24447","creation_date":"1471288252","6":"1471288252"},{"0":"4950","vim_version":"7.0","1":"7.0","script_version":"0.9","2":"0.9","version_comment":"- Added: Inserting and removing long comments ( --[[ --]] ).\r\n- Added: Hardcopy to postscript.\r\n- Added: Direct run, run executable scripts directly, using their shebang.\r\n- Added: Make script executable\/not exec.\r\n- Added: The contents of the buffer \"Lua Output\" can be loaded into the quickfix\r\n  list even if the interpreter did not terminate with an error.\r\n- Added: Toolbox for make integration.\r\n- Changed: Better error recognition while running scripts.\r\n- Fixed: Setup of local templates in case of global installation.\r\n- New templates and codesnippets.\r\n- Minor improvements.","3":"- Added: Inserting and removing long comments ( --[[ --]] ).\r\n- Added: Hardcopy to postscript.\r\n- Added: Direct run, run executable scripts directly, using their shebang.\r\n- Added: Make script executable\/not exec.\r\n- Added: The contents of the buffer \"Lua Output\" can be loaded into the quickfix\r\n  list even if the interpreter did not terminate with an error.\r\n- Added: Toolbox for make integration.\r\n- Changed: Better error recognition while running scripts.\r\n- Fixed: Setup of local templates in case of global installation.\r\n- New templates and codesnippets.\r\n- Minor improvements.","package":"lua-support.zip","4":"lua-support.zip","src_id":"22598","5":"22598","creation_date":"1415037979","6":"1415037979"},{"0":"4950","vim_version":"7.0","1":"7.0","script_version":"0.8","2":"0.8","version_comment":"Initial upload","3":"Initial upload","package":"lua-support.zip","4":"lua-support.zip","src_id":"21963","5":"21963","creation_date":"1401440572","6":"1401440572"}]},"4949":{"script_id":"4949","0":"4949","script_name":"SearchRepeat","1":"SearchRepeat","script_type":"utility","2":"utility","summary":"Repeat the last type of search via n\/N.","3":"Repeat the last type of search via n\/N.","description":"DESCRIPTION\r\nJumping to the next \/ previous search match is such a common command in Vim\r\nthat the n \/ N keys quickly become deeply ingrained in muscle memory. So\r\nwhen one has defined a custom search (e.g. aided by the SearchSpecial.vim\r\n(vimscript #4948) plugin), one is tempted to use n \/ N to repeat those,\r\ntoo, but the keys will just continue to perform the default search. An\r\nintelligent overloading of n \/ N is also desirable because these\r\nsingle-key commands allow for quick single-stroke repeat, and there aren't\r\nmany other keys left for mapping custom searches to.\r\n\r\nThis plugin overloads the n and N commands so that custom searches (i.e.\r\nanything except the default search via \/, ?, [g]*, [g]#) can be repeated.\r\nActivation of a custom search makes that search the new type of search to be\r\nrepeated, until the search type is changed again. The default search is\r\nincluded in that via the `\/` and ? commands, too.\r\n\r\nIt can also make n always move forward and N always move backward (for\r\nboth built-in and custom searches), regardless of the current search\r\ndirection.\r\n\r\nSEE ALSO\r\n- The SearchSpecial.vim (vimscript #4948) plugin provides generic functions\r\n  for special search modes. Check out its plugin page for a full list of\r\n  custom searches powered by it.\r\n\r\nThe following custom searches integrate with this plugin:\r\n\r\n- SearchAsQuickJump.vim (vimscript #5619):\r\n  Quick search without affecting 'hlsearch', search pattern and history.\r\n- SearchInRange.vim (vimscript #4997):\r\n  Limit search to range when jumping to the next search result.\r\n\r\nRELATED WORKS\r\n- If you just want to change the n\/N direction behavior, you can use the\r\n  following (source: http:\/\/article.gmane.org\/gmane.editors.vim.devel\/37715):\r\n    noremap <expr> n 'Nn'[v:searchforward]\r\n    noremap <expr> N 'nN'[v:searchforward]\r\n\r\nUSAGE\r\nn \/ N               Repeat the last used type of search.\r\n\r\ngn                      List all registered search types, keys to\r\n                        (re-)activate, and optional related search commands\r\n                        that activate or configure that type.\r\n                        The currently active search type is highlighted.\r\n\r\nSome custom searches provide dedicated :Search... commands that also activate\r\nthe search repeat. Apart from that, you usually select and execute a custom\r\nsearch type via its gn... integration mapping.\r\nTo change the search type back to plain normal search (without changing the\r\nsearch pattern), just type '\/<Enter>'.\r\n\r\n<Leader>tgn             Toggle whether a change in the current search pattern\r\n                        resets searching with n\/N to standard search, or the\r\n                        current search type is kept.\r\n                        (g:SearchRepeat_IsResetToStandardSearch).\r\n\r\nEXAMPLE\r\nLet's define a simple custom search that positions the current search result\r\nin the middle of the window (using zz). These mappings just delegate to the\r\ndefault n command, open a fold (zv, because that's not done automatically\r\nfrom a mapping), and then append the zz command:\r\n    nnoremap <silent> <Plug>(SearchAtCenterOfWindowNext) :<C-u>execute 'normal!' v:count1 . 'nzvzz'<CR>\r\n    nnoremap <silent> <Plug>(SearchAtCenterOfWindowPrev) :<C-u>execute 'normal!' v:count1 . 'Nzvzz'<CR>\r\n\r\nThen, integrate these into SearchRepeat, using gnzz and gnzZ to activate them:\r\n    call SearchRepeat#Define(\r\n    \\   '<Plug>(SearchAtCenterOfWindowNext)', '<Plug>(SearchAtCenterOfWindowPrev)',\r\n    \\   '', 'zz', 'win-center', 'Search, position at center of window', '',\r\n    \\   2\r\n    \\)\r\n\r\nThe gn command will now show the newly added custom search in addition to\r\nthe built-in standard search:\r\nactivation      identifier      description\r\n        \/       Standard search\r\ngnzz            win-center      Search, position at center of window\r\n\r\nTo activate, search for \/something, then press gnzz. From now on, the n \/\r\nN commands will also center the match (and the gnzz search type is\r\nhighlighted in the gn list), until you reset the search type with another\r\n\/search.","4":"DESCRIPTION\r\nJumping to the next \/ previous search match is such a common command in Vim\r\nthat the n \/ N keys quickly become deeply ingrained in muscle memory. So\r\nwhen one has defined a custom search (e.g. aided by the SearchSpecial.vim\r\n(vimscript #4948) plugin), one is tempted to use n \/ N to repeat those,\r\ntoo, but the keys will just continue to perform the default search. An\r\nintelligent overloading of n \/ N is also desirable because these\r\nsingle-key commands allow for quick single-stroke repeat, and there aren't\r\nmany other keys left for mapping custom searches to.\r\n\r\nThis plugin overloads the n and N commands so that custom searches (i.e.\r\nanything except the default search via \/, ?, [g]*, [g]#) can be repeated.\r\nActivation of a custom search makes that search the new type of search to be\r\nrepeated, until the search type is changed again. The default search is\r\nincluded in that via the `\/` and ? commands, too.\r\n\r\nIt can also make n always move forward and N always move backward (for\r\nboth built-in and custom searches), regardless of the current search\r\ndirection.\r\n\r\nSEE ALSO\r\n- The SearchSpecial.vim (vimscript #4948) plugin provides generic functions\r\n  for special search modes. Check out its plugin page for a full list of\r\n  custom searches powered by it.\r\n\r\nThe following custom searches integrate with this plugin:\r\n\r\n- SearchAsQuickJump.vim (vimscript #5619):\r\n  Quick search without affecting 'hlsearch', search pattern and history.\r\n- SearchInRange.vim (vimscript #4997):\r\n  Limit search to range when jumping to the next search result.\r\n\r\nRELATED WORKS\r\n- If you just want to change the n\/N direction behavior, you can use the\r\n  following (source: http:\/\/article.gmane.org\/gmane.editors.vim.devel\/37715):\r\n    noremap <expr> n 'Nn'[v:searchforward]\r\n    noremap <expr> N 'nN'[v:searchforward]\r\n\r\nUSAGE\r\nn \/ N               Repeat the last used type of search.\r\n\r\ngn                      List all registered search types, keys to\r\n                        (re-)activate, and optional related search commands\r\n                        that activate or configure that type.\r\n                        The currently active search type is highlighted.\r\n\r\nSome custom searches provide dedicated :Search... commands that also activate\r\nthe search repeat. Apart from that, you usually select and execute a custom\r\nsearch type via its gn... integration mapping.\r\nTo change the search type back to plain normal search (without changing the\r\nsearch pattern), just type '\/<Enter>'.\r\n\r\n<Leader>tgn             Toggle whether a change in the current search pattern\r\n                        resets searching with n\/N to standard search, or the\r\n                        current search type is kept.\r\n                        (g:SearchRepeat_IsResetToStandardSearch).\r\n\r\nEXAMPLE\r\nLet's define a simple custom search that positions the current search result\r\nin the middle of the window (using zz). These mappings just delegate to the\r\ndefault n command, open a fold (zv, because that's not done automatically\r\nfrom a mapping), and then append the zz command:\r\n    nnoremap <silent> <Plug>(SearchAtCenterOfWindowNext) :<C-u>execute 'normal!' v:count1 . 'nzvzz'<CR>\r\n    nnoremap <silent> <Plug>(SearchAtCenterOfWindowPrev) :<C-u>execute 'normal!' v:count1 . 'Nzvzz'<CR>\r\n\r\nThen, integrate these into SearchRepeat, using gnzz and gnzZ to activate them:\r\n    call SearchRepeat#Define(\r\n    \\   '<Plug>(SearchAtCenterOfWindowNext)', '<Plug>(SearchAtCenterOfWindowPrev)',\r\n    \\   '', 'zz', 'win-center', 'Search, position at center of window', '',\r\n    \\   2\r\n    \\)\r\n\r\nThe gn command will now show the newly added custom search in addition to\r\nthe built-in standard search:\r\nactivation      identifier      description\r\n        \/       Standard search\r\ngnzz            win-center      Search, position at center of window\r\n\r\nTo activate, search for \/something, then press gnzz. From now on, the n \/\r\nN commands will also center the match (and the gnzz search type is\r\nhighlighted in the gn list), until you reset the search type with another\r\n\/search.","install_details":"INSTALLATION\r\nThe code is hosted in a Git repo at\r\n    https:\/\/github.com\/inkarkat\/vim-SearchRepeat\r\nYou can use your favorite plugin manager, or \"git clone\" into a directory used\r\nfor Vim packages. Releases are on the \"stable\" branch, the latest unstable\r\ndevelopment snapshot on \"master\".\r\n\r\nThis script is also packaged as a vimball. If you have the \"gunzip\"\r\ndecompressor in your PATH, simply edit the *.vmb.gz package in Vim; otherwise,\r\ndecompress the archive first, e.g. using WinZip. Inside Vim, install by\r\nsourcing the vimball or via the :UseVimball command.\r\n    vim SearchRepeat*.vmb.gz\r\n    :so %\r\nTo uninstall, use the :RmVimball command.\r\n\r\nDEPENDENCIES\r\n- Requires Vim 7.0 or higher.\r\n- Requires the ingo-library.vim plugin (vimscript #4433), version 1.025 or\r\n  higher.\r\n\r\nCONFIGURATION\r\nFor a permanent configuration, put the following commands into your vimrc:\r\n\r\nBy default, when a backwards search (e.g. ?foo?) is configured, the n\r\ncommand jumps backwards, too, so the search direction affects the behavior of\r\nn \/ N. Some prefer to have n \/ N behave consistently, regardless of\r\nthe current search direction, i.e. have n always move forward and N always\r\nmove backward. This can be achieved for both built-in and custom searches by\r\nsetting:\r\n    let g:SearchRepeat_IsAlwaysForwardWith_n = 1\r\nNote: This requires Vim 7.2 or later.\r\n\r\nWhenever the current search pattern (quote\/) changes, searches with n\/N are\r\nreset to the standard search; it is assumed that a custom search was bound to\r\na particular search pattern, and once the pattern changes the scope of the\r\ncustom search has ended. To disable that, use:\r\n    let g:SearchRepeat_IsResetToStandardSearch = 0\r\nAfter that, you have to explicitly switch back to standard search with gn\/ \/\r\ngn? (provided by SearchStandardSearch.vim).\r\n\r\nTo change the default mapping prefixes for forward \/ backward search, use:\r\n    let g:SearchRepeat_MappingPrefixNext = 'gn'\r\n    let g:SearchRepeat_MappingPrefixPrev = 'gN'\r\nThis will affect all SearchRepeat integrations done by custom searches, and by\r\ndefault also the gn list of all registered search types, and the toggling of\r\nreset to standard search mapping. To change the latter ones separately, use:\r\n    nmap <Leader>gn <Plug>(SearchRepeatHelp)\r\n    nmap <Leader>tgn <Plug>(SearchRepeatToggleResetToStandard)\r\n\r\nINTEGRATION\r\nTo set the current search type (in a custom search mapping):\r\n    :call SearchRepeat#Set(\"\\<Plug>MyCustomSearchMapping\", \"\\<Plug>MyCustomOppositeSearchMapping\", 2)\r\n\r\nTo set the current search type (in a custom search mapping) and execute the\r\n(first with 0, opposite with 1 as first argument) search mapping:\r\n    if ! SearchRepeat#Execute(0, \"\\<Plug>MyCustomSearchMapping\", \"\\<Plug>MyCustomOppositeSearchMapping\", 2)\r\n        echoerr ingo#err#Get()\r\n    endif\r\n\r\nThe third argument specifies how the mappings deal with an optional [count]\r\nthat is passed to the n \/ N commands:\r\n    0: Doesn't handle count, single invocation only. No count is prepended to\r\n       the search mapping, which is invoked only once. (But the count itself\r\n       is still available through v:count.)\r\n    1: Doesn't handle count itself, invoke search mapping multiple times.\r\n    2: Handles count itself, prepend count before search mapping.\r\n\r\nAn optional fourth argument supplies additional configuration in a dictionary;\r\nsee the SearchRepeat#Set() function for details.\r\n\r\nBut normally, you'd define the (optional) SearchRepeat integration via the\r\nsingle SearchRepeat#Define() convenience function, at the end of your custom\r\nsearch plugin:\r\n    try\r\n        call SearchRepeat#Define(...)\r\n    catch \/^Vim\\%((\\a\\+)\\)\\=:E117\/      \" catch error E117: Unknown function\r\n    endtry\r\nLook up the function definition for details on the arguments.\r\n\r\nThe repeated search type may be affected by changes to the last search pattern\r\n(quote\/; via g:SearchRepeat_IsResetToStandardSearch). Other plugins or\r\ncustomizations that change register \/ may notify SearchRepeat about this by\r\nfiring a User event:\r\n    let @\/ = \"new pattern\"\r\n    silent doautocmd User LastSearchPatternChanged\r\nThis is purely optional; the effects of that are only noticeable if the\r\ncurrent search type is indicated in the 'titlestring' or 'statusline', for\r\nexample. Even without the event, SearchRepeat will recognize and evaluate the\r\npatter change on the next navigation with n \/ N, anyway.","5":"INSTALLATION\r\nThe code is hosted in a Git repo at\r\n    https:\/\/github.com\/inkarkat\/vim-SearchRepeat\r\nYou can use your favorite plugin manager, or \"git clone\" into a directory used\r\nfor Vim packages. Releases are on the \"stable\" branch, the latest unstable\r\ndevelopment snapshot on \"master\".\r\n\r\nThis script is also packaged as a vimball. If you have the \"gunzip\"\r\ndecompressor in your PATH, simply edit the *.vmb.gz package in Vim; otherwise,\r\ndecompress the archive first, e.g. using WinZip. Inside Vim, install by\r\nsourcing the vimball or via the :UseVimball command.\r\n    vim SearchRepeat*.vmb.gz\r\n    :so %\r\nTo uninstall, use the :RmVimball command.\r\n\r\nDEPENDENCIES\r\n- Requires Vim 7.0 or higher.\r\n- Requires the ingo-library.vim plugin (vimscript #4433), version 1.025 or\r\n  higher.\r\n\r\nCONFIGURATION\r\nFor a permanent configuration, put the following commands into your vimrc:\r\n\r\nBy default, when a backwards search (e.g. ?foo?) is configured, the n\r\ncommand jumps backwards, too, so the search direction affects the behavior of\r\nn \/ N. Some prefer to have n \/ N behave consistently, regardless of\r\nthe current search direction, i.e. have n always move forward and N always\r\nmove backward. This can be achieved for both built-in and custom searches by\r\nsetting:\r\n    let g:SearchRepeat_IsAlwaysForwardWith_n = 1\r\nNote: This requires Vim 7.2 or later.\r\n\r\nWhenever the current search pattern (quote\/) changes, searches with n\/N are\r\nreset to the standard search; it is assumed that a custom search was bound to\r\na particular search pattern, and once the pattern changes the scope of the\r\ncustom search has ended. To disable that, use:\r\n    let g:SearchRepeat_IsResetToStandardSearch = 0\r\nAfter that, you have to explicitly switch back to standard search with gn\/ \/\r\ngn? (provided by SearchStandardSearch.vim).\r\n\r\nTo change the default mapping prefixes for forward \/ backward search, use:\r\n    let g:SearchRepeat_MappingPrefixNext = 'gn'\r\n    let g:SearchRepeat_MappingPrefixPrev = 'gN'\r\nThis will affect all SearchRepeat integrations done by custom searches, and by\r\ndefault also the gn list of all registered search types, and the toggling of\r\nreset to standard search mapping. To change the latter ones separately, use:\r\n    nmap <Leader>gn <Plug>(SearchRepeatHelp)\r\n    nmap <Leader>tgn <Plug>(SearchRepeatToggleResetToStandard)\r\n\r\nINTEGRATION\r\nTo set the current search type (in a custom search mapping):\r\n    :call SearchRepeat#Set(\"\\<Plug>MyCustomSearchMapping\", \"\\<Plug>MyCustomOppositeSearchMapping\", 2)\r\n\r\nTo set the current search type (in a custom search mapping) and execute the\r\n(first with 0, opposite with 1 as first argument) search mapping:\r\n    if ! SearchRepeat#Execute(0, \"\\<Plug>MyCustomSearchMapping\", \"\\<Plug>MyCustomOppositeSearchMapping\", 2)\r\n        echoerr ingo#err#Get()\r\n    endif\r\n\r\nThe third argument specifies how the mappings deal with an optional [count]\r\nthat is passed to the n \/ N commands:\r\n    0: Doesn't handle count, single invocation only. No count is prepended to\r\n       the search mapping, which is invoked only once. (But the count itself\r\n       is still available through v:count.)\r\n    1: Doesn't handle count itself, invoke search mapping multiple times.\r\n    2: Handles count itself, prepend count before search mapping.\r\n\r\nAn optional fourth argument supplies additional configuration in a dictionary;\r\nsee the SearchRepeat#Set() function for details.\r\n\r\nBut normally, you'd define the (optional) SearchRepeat integration via the\r\nsingle SearchRepeat#Define() convenience function, at the end of your custom\r\nsearch plugin:\r\n    try\r\n        call SearchRepeat#Define(...)\r\n    catch \/^Vim\\%((\\a\\+)\\)\\=:E117\/      \" catch error E117: Unknown function\r\n    endtry\r\nLook up the function definition for details on the arguments.\r\n\r\nThe repeated search type may be affected by changes to the last search pattern\r\n(quote\/; via g:SearchRepeat_IsResetToStandardSearch). Other plugins or\r\ncustomizations that change register \/ may notify SearchRepeat about this by\r\nfiring a User event:\r\n    let @\/ = \"new pattern\"\r\n    silent doautocmd User LastSearchPatternChanged\r\nThis is purely optional; the effects of that are only noticeable if the\r\ncurrent search type is indicated in the 'titlestring' or 'statusline', for\r\nexample. Even without the event, SearchRepeat will recognize and evaluate the\r\npatter change on the next navigation with n \/ N, anyway.","first_name":"Ingo","6":"Ingo","last_name":"Karkat","7":"Karkat","releases":[{"0":"4949","vim_version":"7.0","1":"7.0","script_version":"2.00","2":"2.00","version_comment":"- CHG: Split g:SearchRepeat_MappingPrefix into two g:SearchRepeat_MappingPrefixNext and g:SearchRepeat_MappingPrefixPrev. With this, custom searches only need to register a single suffix for forward \/ backward searches. This both frees up keys (which I'm running out of with my many custom searches), and enables non-alphabetic suffixes (SearchForExpr.vim is now using gn= instead of gne \/ gnE).\r\n- CHG: Simplify SearchRepeat#Define() API: Get rid of duplicate suffixes, descriptions, helptexts, related commands for next \/ prev mappings. Instead, forward \/ backward search is now handled by separate gn \/ gN mapping prefixes.\r\n- CHG: Mapping registration only stores the \"Next\" mapping, and the gn help command only lists those (to reduce clutter and duplication). The \"Prev\" mapping is now stored in s:reverseRegistrations.\r\n- Remember the contents of @\/ and reset to standard search when it changed (e.g. by * \/ g*, or plugins like my SearchAlternatives.vim).\r\n- Make this configurable via g:SearchRepeat_IsResetToStandardSearch and enable toggling via new <Leader>tgn mapping.\r\n- ENH: Omit related commands and condense activation commands column in search type list when in small-width Vim, to avoid line breaks that make the layout hard to read.\r\n- ENH: Support \"isResetToStandardSearch\" option flag that overrides the g:SearchRepeat_IsResetToStandardSearch configuration value for certain integrations.\r\n- Rename \"description\" to \"identifier\" and \"helptext\" to \"description\" in gn help and function arguments.\r\n- ENH: Other plugins and customizations can emit a User LastSearchPatternChanged event to notify SearchRepeat of changes to @\/. *** You need to update to ingo-library (vimscript #4433) version 1.025! ***","3":"- CHG: Split g:SearchRepeat_MappingPrefix into two g:SearchRepeat_MappingPrefixNext and g:SearchRepeat_MappingPrefixPrev. With this, custom searches only need to register a single suffix for forward \/ backward searches. This both frees up keys (which I'm running out of with my many custom searches), and enables non-alphabetic suffixes (SearchForExpr.vim is now using gn= instead of gne \/ gnE).\r\n- CHG: Simplify SearchRepeat#Define() API: Get rid of duplicate suffixes, descriptions, helptexts, related commands for next \/ prev mappings. Instead, forward \/ backward search is now handled by separate gn \/ gN mapping prefixes.\r\n- CHG: Mapping registration only stores the \"Next\" mapping, and the gn help command only lists those (to reduce clutter and duplication). The \"Prev\" mapping is now stored in s:reverseRegistrations.\r\n- Remember the contents of @\/ and reset to standard search when it changed (e.g. by * \/ g*, or plugins like my SearchAlternatives.vim).\r\n- Make this configurable via g:SearchRepeat_IsResetToStandardSearch and enable toggling via new <Leader>tgn mapping.\r\n- ENH: Omit related commands and condense activation commands column in search type list when in small-width Vim, to avoid line breaks that make the layout hard to read.\r\n- ENH: Support \"isResetToStandardSearch\" option flag that overrides the g:SearchRepeat_IsResetToStandardSearch configuration value for certain integrations.\r\n- Rename \"description\" to \"identifier\" and \"helptext\" to \"description\" in gn help and function arguments.\r\n- ENH: Other plugins and customizations can emit a User LastSearchPatternChanged event to notify SearchRepeat of changes to @\/. *** You need to update to ingo-library (vimscript #4433) version 1.025! ***","package":"SearchRepeat-2.00.vmb.gz","4":"SearchRepeat-2.00.vmb.gz","src_id":"25700","5":"25700","creation_date":"1512759525","6":"1512759525"},{"0":"4949","vim_version":"7.0","1":"7.0","script_version":"1.11","2":"1.11","version_comment":"- FIX: v:searchforward requires Vim 7.2; don't support the g:SearchRepeat_IsAlwaysForwardWith_n configuration in older versions.","3":"- FIX: v:searchforward requires Vim 7.2; don't support the g:SearchRepeat_IsAlwaysForwardWith_n configuration in older versions.","package":"SearchRepeat-1.11.vmb.gz","4":"SearchRepeat-1.11.vmb.gz","src_id":"24214","5":"24214","creation_date":"1461919675","6":"1461919675"},{"0":"4949","vim_version":"7.0","1":"7.0","script_version":"1.10","2":"1.10","version_comment":"- CHG: Add isOpposite flag to SearchRepeat#Execute() and remove the swapping of a:mappingNext and a:mappingPrev in the opposite mapping definition.\r\n- ENH: Add g:SearchRepeat_IsAlwaysForwardWith_n configuration to consistently always move forward \/ backward with n \/ N, regardless of whether the current search mode goes into the opposite direction.\r\n- FIX: SearchRepeat#Execute() needs to return status of SearchRepeat#Repeat() to have clients :echoerr any error.","3":"- CHG: Add isOpposite flag to SearchRepeat#Execute() and remove the swapping of a:mappingNext and a:mappingPrev in the opposite mapping definition.\r\n- ENH: Add g:SearchRepeat_IsAlwaysForwardWith_n configuration to consistently always move forward \/ backward with n \/ N, regardless of whether the current search mode goes into the opposite direction.\r\n- FIX: SearchRepeat#Execute() needs to return status of SearchRepeat#Repeat() to have clients :echoerr any error.","package":"SearchRepeat-1.10.vmb.gz","4":"SearchRepeat-1.10.vmb.gz","src_id":"21971","5":"21971","creation_date":"1401562085","6":"1401562085"},{"0":"4949","vim_version":"7.0","1":"7.0","script_version":"1.00","2":"1.00","version_comment":"Initial upload","3":"Initial upload","package":"SearchRepeat-1.00.vmb.gz","4":"SearchRepeat-1.00.vmb.gz","src_id":"21944","5":"21944","creation_date":"1401101296","6":"1401101296"}]},"4948":{"script_id":"4948","0":"4948","script_name":"SearchSpecial","1":"SearchSpecial","script_type":"utility","2":"utility","summary":"Generic functions for special search modes.","3":"Generic functions for special search modes.","description":"DESCRIPTION\r\nThe built-in search via \/, n, and N does its job. But sometimes, it\r\nwould be nice to have a custom search that is limited to a certain range, or\r\nthe first match in a line, or certain syntax groups, or a search that doesn't\r\nopen folds. This plugin offers generic functions that can be used to easily\r\nbuild such custom search mappings for special searches. A predicate function\r\ncan specify which matches are skipped, and options control the behavior with\r\nregards to folding and jumps.\r\n\r\nSEE ALSO\r\n- The SearchRepeat.vim (vimscript #4949) plugin provides an integration\r\n  facility for custom searches (such as ones implemented via\r\n  SearchSpecial.vim) that repeats the last type of used search via n\/N, and\r\n  can list all defined custom searches.\r\n\r\nThe following custom searches use this plugin:\r\n\r\n- SearchAsQuickJump.vim (vimscript #5619):\r\n  Quick search without affecting 'hlsearch', search pattern and history.\r\n\r\nUSAGE\r\nThis plugin defines several functions. The following is an overview; you'll\r\nfind the details directly in the implementation files in the .vim\/autoload\/\r\ndirectory.\r\n\r\nSearchSpecial#SearchWithout( searchPattern, isBackward, Predicate, predicateId, predicateDescription, count, ... )\r\n\r\nThe main helper function that jumps to the next match of a:searchPattern,\r\nskipping all those matches where a:Predicate returns false.\r\n\r\nEXAMPLE\r\nHere's a simple search mapping that emulates the default search (because it\r\ndoesn't pass a predicate that limits the matches, nor are there any options):\r\n    nnoremap <silent> ,n\r\n    \\   :<C-u>if SearchSpecial#SearchWithout(@\/, 0, '', 'default', '', v:count1)<Bar>\r\n    \\   if &hlsearch<Bar>set hlsearch<Bar>endif<Bar>\r\n    \\   else<Bar>echoerr ingo#err#Get()<Bar>endif<CR>\r\nThe 'hlsearch' handling cannot be done in a function; and any \"Pattern not\r\nfound\" error is raised directly from the mapping; that's the boilerplate code\r\nat the end of the mapping.","4":"DESCRIPTION\r\nThe built-in search via \/, n, and N does its job. But sometimes, it\r\nwould be nice to have a custom search that is limited to a certain range, or\r\nthe first match in a line, or certain syntax groups, or a search that doesn't\r\nopen folds. This plugin offers generic functions that can be used to easily\r\nbuild such custom search mappings for special searches. A predicate function\r\ncan specify which matches are skipped, and options control the behavior with\r\nregards to folding and jumps.\r\n\r\nSEE ALSO\r\n- The SearchRepeat.vim (vimscript #4949) plugin provides an integration\r\n  facility for custom searches (such as ones implemented via\r\n  SearchSpecial.vim) that repeats the last type of used search via n\/N, and\r\n  can list all defined custom searches.\r\n\r\nThe following custom searches use this plugin:\r\n\r\n- SearchAsQuickJump.vim (vimscript #5619):\r\n  Quick search without affecting 'hlsearch', search pattern and history.\r\n\r\nUSAGE\r\nThis plugin defines several functions. The following is an overview; you'll\r\nfind the details directly in the implementation files in the .vim\/autoload\/\r\ndirectory.\r\n\r\nSearchSpecial#SearchWithout( searchPattern, isBackward, Predicate, predicateId, predicateDescription, count, ... )\r\n\r\nThe main helper function that jumps to the next match of a:searchPattern,\r\nskipping all those matches where a:Predicate returns false.\r\n\r\nEXAMPLE\r\nHere's a simple search mapping that emulates the default search (because it\r\ndoesn't pass a predicate that limits the matches, nor are there any options):\r\n    nnoremap <silent> ,n\r\n    \\   :<C-u>if SearchSpecial#SearchWithout(@\/, 0, '', 'default', '', v:count1)<Bar>\r\n    \\   if &hlsearch<Bar>set hlsearch<Bar>endif<Bar>\r\n    \\   else<Bar>echoerr ingo#err#Get()<Bar>endif<CR>\r\nThe 'hlsearch' handling cannot be done in a function; and any \"Pattern not\r\nfound\" error is raised directly from the mapping; that's the boilerplate code\r\nat the end of the mapping.","install_details":"INSTALLATION\r\nThe code is hosted in a Git repo at\r\n    https:\/\/github.com\/inkarkat\/vim-SearchSpecial\r\nYou can use your favorite plugin manager, or \"git clone\" into a directory used\r\nfor Vim packages. Releases are on the \"stable\" branch, the latest unstable\r\ndevelopment snapshot on \"master\".\r\n\r\nThis script is also packaged as a vimball. If you have the \"gunzip\"\r\ndecompressor in your PATH, simply edit the *.vmb.gz package in Vim; otherwise,\r\ndecompress the archive first, e.g. using WinZip. Inside Vim, install by\r\nsourcing the vimball or via the :UseVimball command.\r\n    vim SearchSpecial*.vmb.gz\r\n    :so %\r\nTo uninstall, use the :RmVimball command.\r\n\r\nDEPENDENCIES\r\n- Requires Vim 7.0 or higher.\r\n- Requires the ingo-library.vim plugin (vimscript #4433), version 1.019 or\r\n  higher.","5":"INSTALLATION\r\nThe code is hosted in a Git repo at\r\n    https:\/\/github.com\/inkarkat\/vim-SearchSpecial\r\nYou can use your favorite plugin manager, or \"git clone\" into a directory used\r\nfor Vim packages. Releases are on the \"stable\" branch, the latest unstable\r\ndevelopment snapshot on \"master\".\r\n\r\nThis script is also packaged as a vimball. If you have the \"gunzip\"\r\ndecompressor in your PATH, simply edit the *.vmb.gz package in Vim; otherwise,\r\ndecompress the archive first, e.g. using WinZip. Inside Vim, install by\r\nsourcing the vimball or via the :UseVimball command.\r\n    vim SearchSpecial*.vmb.gz\r\n    :so %\r\nTo uninstall, use the :RmVimball command.\r\n\r\nDEPENDENCIES\r\n- Requires Vim 7.0 or higher.\r\n- Requires the ingo-library.vim plugin (vimscript #4433), version 1.019 or\r\n  higher.","first_name":"Ingo","6":"Ingo","last_name":"Karkat","7":"Karkat","releases":[{"0":"4948","vim_version":"7.0","1":"7.0","script_version":"1.20","2":"1.20","version_comment":"- ENH: Extract search {offset} from the last search history element and apply it after jumping if the passed a:searchPattern is also the last element in the history. This can be turned off via a:options.isAutoOffset. The implementation even handles another search (|\/\/;|), even though this is only considered for an initial search, not for subsequent searches (only the last pattern is stored in @\/, not the full search sequence).\r\n- a:options.EchoFunction and a:options.ErrorFunction now get supplied a:searchPattern which is either a String of a List of [searchPattern, searchOffset] if such is specified (via a:options.isAutoOffset).\r\n- ENH: Add a:options.searchOffset to allow clients set the search offset.","3":"- ENH: Extract search {offset} from the last search history element and apply it after jumping if the passed a:searchPattern is also the last element in the history. This can be turned off via a:options.isAutoOffset. The implementation even handles another search (|\/\/;|), even though this is only considered for an initial search, not for subsequent searches (only the last pattern is stored in @\/, not the full search sequence).\r\n- a:options.EchoFunction and a:options.ErrorFunction now get supplied a:searchPattern which is either a String of a List of [searchPattern, searchOffset] if such is specified (via a:options.isAutoOffset).\r\n- ENH: Add a:options.searchOffset to allow clients set the search offset.","package":"SearchSpecial-1.20.vmb.gz","4":"SearchSpecial-1.20.vmb.gz","src_id":"25699","5":"25699","creation_date":"1512759451","6":"1512759451"},{"0":"4948","vim_version":"7.0","1":"7.0","script_version":"1.10","2":"1.10","version_comment":"- ENH: Allow to configure the echoing of successful matches via a:options.EchoFunction.\r\n- ENH: Allow to configure the error messages when there are no matches via a:options.ErrorFunction.\r\n- ENH: Allow to return more search information via a:options.isReturnMoreInfo.\r\n- ENH: Allow to run commands before and after the first search via a:options.BeforeFirstSearchAction and a:options.AfterFirstSearchAction. Needed for SearchManyLocations.vim.\r\n- ENH: Allow to run commands after each search via a:options.AfterAnySearchAction and after the final search jump via a:options.AfterFinalSearchAction. Allow to specify a:options.additionalSearchFlags. Both required for SearchAsQuickJump.vim offset enhancement.","3":"- ENH: Allow to configure the echoing of successful matches via a:options.EchoFunction.\r\n- ENH: Allow to configure the error messages when there are no matches via a:options.ErrorFunction.\r\n- ENH: Allow to return more search information via a:options.isReturnMoreInfo.\r\n- ENH: Allow to run commands before and after the first search via a:options.BeforeFirstSearchAction and a:options.AfterFirstSearchAction. Needed for SearchManyLocations.vim.\r\n- ENH: Allow to run commands after each search via a:options.AfterAnySearchAction and after the final search jump via a:options.AfterFinalSearchAction. Allow to specify a:options.additionalSearchFlags. Both required for SearchAsQuickJump.vim offset enhancement.","package":"SearchSpecial-1.10.vmb.gz","4":"SearchSpecial-1.10.vmb.gz","src_id":"25650","5":"25650","creation_date":"1511112677","6":"1511112677"},{"0":"4948","vim_version":"7.0","1":"7.0","script_version":"1.00","2":"1.00","version_comment":"Initial upload","3":"Initial upload","package":"SearchSpecial-1.00.vmb.gz","4":"SearchSpecial-1.00.vmb.gz","src_id":"21935","5":"21935","creation_date":"1400959418","6":"1400959418"}]},"4947":{"script_id":"4947","0":"4947","script_name":"Find in Files, feature like Notepad++","1":"Find in Files, feature like Notepad++","script_type":"utility","2":"utility","summary":"\"Find in Files and Directories\" like Notepad++","3":"\"Find in Files and Directories\" like Notepad++","description":"This script has been written to mimic the Notepad++ 's 'Find in Files' feature.\r\nKeeping the simplicity in mind, this script is written to be simple.\r\nThe objective of this script is to eliminate the hassle of\r\nsearching through vimgrep to the new users and provide\r\na quick yet easy way to do this job.\r\n\r\nTested on Windows 7 64-bit (Gvim official 32-bit)\r\nTested on Linux (UBUNTU 13.10 Saucy) (Gvim from its repository)\r\n\r\n*EXAMPLES*\r\nSay you have to find something (e.g. printf) in a specified directory\r\n(e.g. C:\\CodeBlocks\\TDM-GCC-64\\x86_64-w64-mingw32\\include ) in a bunch of\r\nC header files (i.e.,    .h).\r\n\r\nSelect the item from Menu Bar -> Edit -> Find in Files.\r\nAn input box will appear, asking for term you are looking for.\r\nFill it up and press OK.\r\n\r\nThis time you will see a directory browser, navigate to the directory\r\nin which you want to perform the search operation. Press Open.\r\n\r\nNow another input box will ask you to submit the extension\r\n(e.g.  .txt, .h, .c etc), if you are willing to look into the\r\n\r\n-----------------------------------------------------------------------------------\r\n   C header files                |       give             h\r\n-----------------------------------------------------------------------------------\r\n   C files                           |       give             c\r\n-----------------------------------------------------------------------------------\r\n   C++ files                       |       give        cpp  cxx C  whichever is\r\n                                       |             most suitable to the situation.\r\n-----------------------------------------------------------------------------------\r\n   text files                        |       give             txt\r\n-----------------------------------------------------------------------------------\r\n   extension-less files         |       sorry, this plug-in currently\r\n                                        |    does not work with extension-less files.\r\n-----------------------------------------------------------------------------------\r\n   Other type of files            |       give the extension only,\r\n                                        |        but do not use any wild-card or dot.\r\n-----------------------------------------------------------------------------------\r\nNever write   .h   .txt   etc, the script will fail to work.\r\n                                            It already does the job internally.\r\nAlways write   h    txt   this way.\r\n\r\n*LIMITATIONS*\r\n1 . Currently this script cannot search the directory recursively,\r\nbut in future an option will be there.\r\n2 . Currently this script cannot search into the extension-less files.\r\n3 . vimgrep is a slow process, please be patient while searching.\r\n\r\n*INTERNAL*\r\nThe raw method of searching something within a bunch of similar file-type is\r\n:vimgrep \/the_term_u_r_looking_4\/ Directory\\*.extension\r\nLike:\r\n:vimgrep \/printf\/ C:\\CodeBlocks\\TDM-GCC-64\\x86_64-w64-mingw32\\include\\*.h\r\n\r\nThis script internally does this.\r\n","4":"This script has been written to mimic the Notepad++ 's 'Find in Files' feature.\r\nKeeping the simplicity in mind, this script is written to be simple.\r\nThe objective of this script is to eliminate the hassle of\r\nsearching through vimgrep to the new users and provide\r\na quick yet easy way to do this job.\r\n\r\nTested on Windows 7 64-bit (Gvim official 32-bit)\r\nTested on Linux (UBUNTU 13.10 Saucy) (Gvim from its repository)\r\n\r\n*EXAMPLES*\r\nSay you have to find something (e.g. printf) in a specified directory\r\n(e.g. C:\\CodeBlocks\\TDM-GCC-64\\x86_64-w64-mingw32\\include ) in a bunch of\r\nC header files (i.e.,    .h).\r\n\r\nSelect the item from Menu Bar -> Edit -> Find in Files.\r\nAn input box will appear, asking for term you are looking for.\r\nFill it up and press OK.\r\n\r\nThis time you will see a directory browser, navigate to the directory\r\nin which you want to perform the search operation. Press Open.\r\n\r\nNow another input box will ask you to submit the extension\r\n(e.g.  .txt, .h, .c etc), if you are willing to look into the\r\n\r\n-----------------------------------------------------------------------------------\r\n   C header files                |       give             h\r\n-----------------------------------------------------------------------------------\r\n   C files                           |       give             c\r\n-----------------------------------------------------------------------------------\r\n   C++ files                       |       give        cpp  cxx C  whichever is\r\n                                       |             most suitable to the situation.\r\n-----------------------------------------------------------------------------------\r\n   text files                        |       give             txt\r\n-----------------------------------------------------------------------------------\r\n   extension-less files         |       sorry, this plug-in currently\r\n                                        |    does not work with extension-less files.\r\n-----------------------------------------------------------------------------------\r\n   Other type of files            |       give the extension only,\r\n                                        |        but do not use any wild-card or dot.\r\n-----------------------------------------------------------------------------------\r\nNever write   .h   .txt   etc, the script will fail to work.\r\n                                            It already does the job internally.\r\nAlways write   h    txt   this way.\r\n\r\n*LIMITATIONS*\r\n1 . Currently this script cannot search the directory recursively,\r\nbut in future an option will be there.\r\n2 . Currently this script cannot search into the extension-less files.\r\n3 . vimgrep is a slow process, please be patient while searching.\r\n\r\n*INTERNAL*\r\nThe raw method of searching something within a bunch of similar file-type is\r\n:vimgrep \/the_term_u_r_looking_4\/ Directory\\*.extension\r\nLike:\r\n:vimgrep \/printf\/ C:\\CodeBlocks\\TDM-GCC-64\\x86_64-w64-mingw32\\include\\*.h\r\n\r\nThis script internally does this.\r\n","install_details":"Extract the zip file and copy 'Find_in_Files.txt' and 'Find_in_Files.vim' to their respective directory.\r\nE.g., on Windows 7 64-bit you can place 'Find_in_Files.vim' into \"C:\\Program Files (x86)\\Vim\\vim74\\plugin\" and 'Find_in_Files.txt' into \"C:\\Program Files (x86)\\Vim\\vim74\\doc\".\r\nThen Press Shift+:\r\nthen, :helptags $VIMRUNTIME\/doc\r\n\r\nOn linux you can put the files  'Find_in_Files.txt' and 'Find_in_Files.vim' to \r\n\/home\/your_user_account_name\/.vim\/doc and \/home\/your_user_account_name\/.vim\/plugin\r\nOpen file manager (nautilus etc.) press Ctrl+L then write ~\/.vim and hit Enter to find these directories.\r\nAfter installing, do   :helptags $HOME\/.vim\/doc\r\nRead the documentations.","5":"Extract the zip file and copy 'Find_in_Files.txt' and 'Find_in_Files.vim' to their respective directory.\r\nE.g., on Windows 7 64-bit you can place 'Find_in_Files.vim' into \"C:\\Program Files (x86)\\Vim\\vim74\\plugin\" and 'Find_in_Files.txt' into \"C:\\Program Files (x86)\\Vim\\vim74\\doc\".\r\nThen Press Shift+:\r\nthen, :helptags $VIMRUNTIME\/doc\r\n\r\nOn linux you can put the files  'Find_in_Files.txt' and 'Find_in_Files.vim' to \r\n\/home\/your_user_account_name\/.vim\/doc and \/home\/your_user_account_name\/.vim\/plugin\r\nOpen file manager (nautilus etc.) press Ctrl+L then write ~\/.vim and hit Enter to find these directories.\r\nAfter installing, do   :helptags $HOME\/.vim\/doc\r\nRead the documentations.","first_name":"Pinaki Sekhar","6":"Pinaki Sekhar","last_name":"Gupta","7":"Gupta","releases":[{"0":"4947","vim_version":"7.3","1":"7.3","script_version":"0.0.01","2":"0.0.01","version_comment":"Initial upload","3":"Initial upload","package":"Find_in_Files.zip","4":"Find_in_Files.zip","src_id":"21925","5":"21925","creation_date":"1400831319","6":"1400831319"}]},"4946":{"script_id":"4946","0":"4946","script_name":"Gtags And Man Proto (GAMP)","1":"Gtags And Man Proto (GAMP)","script_type":"utility","2":"utility","summary":"Full function completion using Linux manual and GTags (not mandatory).","3":"Full function completion using Linux manual and GTags (not mandatory).","description":"GAMP is a very lightweight system completion for libc functions and virtually any other functions.\r\n\r\nREQUIREMENTS\r\n  Mandatory:\r\n    * Linux-like OS with a shell and a manpage system\r\n    * Vim 'laststatus' must be set to 2\r\n  Optional:\r\n    * GNU Global (its use can be disabled)\r\n\r\nFEATURES\r\n  * Perfect for C, C++ and theorically support other C syntax-like languages (PHP, Java)\r\n  * 3 modes:\r\n    * Complete function prototype in completion mode\r\n    * Hint for function prototype in statusline mode\r\n    * Do all of the above when using both modes\r\n  * Take definition from all the function manpages from section 2 and 3\r\n    ( system and library (including libc) calls )\r\n  * Take definition of any function using GNU Global GTags system\r\n  * If not using Global GTags, there is no dependency\r\n  * Real-time updating and no maintenance required if using  gtags.vim  \r\n    auto-update feature\r\n\r\nUSAGE EXAMPLE\r\nIn completion mode:\r\n        printf ||                       \/* \"||\" is the cursor *\/\r\n    After pressing <Leader>gmc  becomes:\r\n        print|f| ( {+const_char_pt_format+}, {+VA_Args+} )\r\n    Use <C-j> to jump to next argument:\r\n        printf ( ||, {+VA_Args+} )\r\n        printf ( \"GAMP mark: %d\/10\"||, {+VA_Args+} )\r\n    And again:\r\n        printf ( \"GAMP mark: %d\/10\", || )\r\n        printf ( \"GAMP mark: %d\/10\", 10|| )\r\n\r\nIn statusline mode:\r\n        printf (const char *format, ...)\r\n     Is displayed on statusline.\r\n\r\nNOTES\r\n  * Functions taking function pointers as arguments are not yet fully supported","4":"GAMP is a very lightweight system completion for libc functions and virtually any other functions.\r\n\r\nREQUIREMENTS\r\n  Mandatory:\r\n    * Linux-like OS with a shell and a manpage system\r\n    * Vim 'laststatus' must be set to 2\r\n  Optional:\r\n    * GNU Global (its use can be disabled)\r\n\r\nFEATURES\r\n  * Perfect for C, C++ and theorically support other C syntax-like languages (PHP, Java)\r\n  * 3 modes:\r\n    * Complete function prototype in completion mode\r\n    * Hint for function prototype in statusline mode\r\n    * Do all of the above when using both modes\r\n  * Take definition from all the function manpages from section 2 and 3\r\n    ( system and library (including libc) calls )\r\n  * Take definition of any function using GNU Global GTags system\r\n  * If not using Global GTags, there is no dependency\r\n  * Real-time updating and no maintenance required if using  gtags.vim  \r\n    auto-update feature\r\n\r\nUSAGE EXAMPLE\r\nIn completion mode:\r\n        printf ||                       \/* \"||\" is the cursor *\/\r\n    After pressing <Leader>gmc  becomes:\r\n        print|f| ( {+const_char_pt_format+}, {+VA_Args+} )\r\n    Use <C-j> to jump to next argument:\r\n        printf ( ||, {+VA_Args+} )\r\n        printf ( \"GAMP mark: %d\/10\"||, {+VA_Args+} )\r\n    And again:\r\n        printf ( \"GAMP mark: %d\/10\", || )\r\n        printf ( \"GAMP mark: %d\/10\", 10|| )\r\n\r\nIn statusline mode:\r\n        printf (const char *format, ...)\r\n     Is displayed on statusline.\r\n\r\nNOTES\r\n  * Functions taking function pointers as arguments are not yet fully supported","install_details":"Inside the GAMP.tar archive are two files that you have to put in the appropriate location of your vim folder (for me, it's  $HOME\/.vim ).\r\nYou can do it using your graphical archive manager (like  file-roller ), or with the command-line with:\r\n    $ tar -xvf  GAMP.tar\r\nto extract the archive, and:\r\n    $ cp  doc\/gtags-and-man-proto.txt          $HOME\/.vim\/doc\r\n    $ cp  plugin\/gtags-and-man-proto.vim   $HOME\/.vim\/plugin \r\nto copy the files.","5":"Inside the GAMP.tar archive are two files that you have to put in the appropriate location of your vim folder (for me, it's  $HOME\/.vim ).\r\nYou can do it using your graphical archive manager (like  file-roller ), or with the command-line with:\r\n    $ tar -xvf  GAMP.tar\r\nto extract the archive, and:\r\n    $ cp  doc\/gtags-and-man-proto.txt          $HOME\/.vim\/doc\r\n    $ cp  plugin\/gtags-and-man-proto.vim   $HOME\/.vim\/plugin \r\nto copy the files.","first_name":"S","6":"S","last_name":"S","7":"S","releases":[{"0":"4946","vim_version":"7.0","1":"7.0","script_version":"0.5.9","2":"0.5.9","version_comment":"Bugfix: a mere typo, sorry for that.","3":"Bugfix: a mere typo, sorry for that.","package":"GAMP.tar","4":"GAMP.tar","src_id":"22101","5":"22101","creation_date":"1403897793","6":"1403897793"},{"0":"4946","vim_version":"7.0","1":"7.0","script_version":"0.5.9","2":"0.5.9","version_comment":"Bugfix: improved manual pages lookup for multi-line definition ( fwrite, etc... ) and function pointers ( __free_hook, etc... ).\r\nIf found, comments are now removed from prototypes when completing.","3":"Bugfix: improved manual pages lookup for multi-line definition ( fwrite, etc... ) and function pointers ( __free_hook, etc... ).\r\nIf found, comments are now removed from prototypes when completing.","package":"GAMP.tar","4":"GAMP.tar","src_id":"22098","5":"22098","creation_date":"1403888617","6":"1403888617"},{"0":"4946","vim_version":"7.0","1":"7.0","script_version":"0.5.5","2":"0.5.5","version_comment":"Bugfix: g:GAMP_UnloadLoadedBuffer == 1 used to be problematic when function definition was located in the same file as the currently active file.","3":"Bugfix: g:GAMP_UnloadLoadedBuffer == 1 used to be problematic when function definition was located in the same file as the currently active file.","package":"GAMP.tar","4":"GAMP.tar","src_id":"22083","5":"22083","creation_date":"1403527936","6":"1403527936"},{"0":"4946","vim_version":"7.0","1":"7.0","script_version":"0.5.1","2":"0.5.1","version_comment":"Bugfix: improved grep matching of manual pages for ambiguous cases ( puts\/fputs, etc... )","3":"Bugfix: improved grep matching of manual pages for ambiguous cases ( puts\/fputs, etc... )","package":"GAMP.tar","4":"GAMP.tar","src_id":"22077","5":"22077","creation_date":"1403440849","6":"1403440849"},{"0":"4946","vim_version":"7.0","1":"7.0","script_version":"0.5.1","2":"0.5.1","version_comment":"* <Leader>gm mapping now available in all modes.\r\n* New mapping   gmh   (Gtags and Man Hint) which shows hint of prototype function even when not in statusline mode.","3":"* <Leader>gm mapping now available in all modes.\r\n* New mapping   gmh   (Gtags and Man Hint) which shows hint of prototype function even when not in statusline mode.","package":"GAMP.tar","4":"GAMP.tar","src_id":"21921","5":"21921","creation_date":"1400801224","6":"1400801224"},{"0":"4946","vim_version":"7.0","1":"7.0","script_version":"0.5","2":"0.5","version_comment":"Initial upload","3":"Initial upload","package":"GAMP.tar","4":"GAMP.tar","src_id":"21919","5":"21919","creation_date":"1400767049","6":"1400767049"}]},"4945":{"script_id":"4945","0":"4945","script_name":"SemanticHL","1":"SemanticHL","script_type":"syntax","2":"syntax","summary":"Semantic highlighting for C\/C++ (v1.0 20140521)","3":"Semantic highlighting for C\/C++ (v1.0 20140521)","description":"Adds semantic highlighting to C\/C++ symbols\r\n\r\nDetails\r\n\r\nAssigns the color of a C\/C++ symbol using the hash of the symbol string as a key to a color table that spans the line between minimum and maximum hue. Color table customizable by editing script. Behavior of color assignment customizable by editing hash function.\r\n\r\nKnown defects\r\n\r\n- The 'define' in a '#define' preprocessor definition may be incorrectly colorized.\r\n\r\n- The semantic parsing algorithm is approximately O(n). Where 'n' is the number of non-syntax symbols in a buffer. Large files may be slow to process on your machine.\r\n\r\n- Only available in gvim.","4":"Adds semantic highlighting to C\/C++ symbols\r\n\r\nDetails\r\n\r\nAssigns the color of a C\/C++ symbol using the hash of the symbol string as a key to a color table that spans the line between minimum and maximum hue. Color table customizable by editing script. Behavior of color assignment customizable by editing hash function.\r\n\r\nKnown defects\r\n\r\n- The 'define' in a '#define' preprocessor definition may be incorrectly colorized.\r\n\r\n- The semantic parsing algorithm is approximately O(n). Where 'n' is the number of non-syntax symbols in a buffer. Large files may be slow to process on your machine.\r\n\r\n- Only available in gvim.","install_details":"Assumptions\r\n\r\nVim home directory is ~\/.vim\r\n\r\nProcedure\r\n \r\n1. Copy 'cpp_sem.vim' and 'c_sem.vim' to ~\/.vim\/syntax.\r\n2. Copy 'semantic.vim' to ~\/.vim\/ftdetect\r\n\r\nSemantic highlighting will be enabled automatically for files with c\/cpp\/h\/hpp extensions. \r\n","5":"Assumptions\r\n\r\nVim home directory is ~\/.vim\r\n\r\nProcedure\r\n \r\n1. Copy 'cpp_sem.vim' and 'c_sem.vim' to ~\/.vim\/syntax.\r\n2. Copy 'semantic.vim' to ~\/.vim\/ftdetect\r\n\r\nSemantic highlighting will be enabled automatically for files with c\/cpp\/h\/hpp extensions. \r\n","first_name":"John","6":"John","last_name":"Leimon","7":"Leimon","releases":[{"0":"4945","vim_version":"7.0","1":"7.0","script_version":"1.1","2":"1.1","version_comment":"Removed semantic highlight parsing from autocmd hooks: CursorMovedI and CursorMoved. This is to prevent noticeable UI performance degradation while editing some buffers on some systems.","3":"Removed semantic highlight parsing from autocmd hooks: CursorMovedI and CursorMoved. This is to prevent noticeable UI performance degradation while editing some buffers on some systems.","package":"semantic.zip","4":"semantic.zip","src_id":"22004","5":"22004","creation_date":"1402371545","6":"1402371545"},{"0":"4945","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Latest and greatest.","3":"Latest and greatest.","package":"semantic.zip","4":"semantic.zip","src_id":"21917","5":"21917","creation_date":"1400736786","6":"1400736786"}]},"4944":{"script_id":"4944","0":"4944","script_name":"Switch c\/c++ source and header files","1":"Switch c\/c++ source and header files","script_type":"utility","2":"utility","summary":"Switch current vim buffer between c++ header and cpp files","3":"Switch current vim buffer between c++ header and cpp files","description":"\\\" || Switch c++ h and cpp\r\n\\\" || Jia Hongyuan, 2014-03-06. Email: jhy817@qq.com\r\n\\\" ||\r\n\\\" || Descriptions:\r\n\\\" || This script is designed to quickly switch current vim buffer between c\/c++\r\n\\\" || header and cpp files. You can easily add new file extensions by changing \\\"exts\\\" variable.\r\n\\\" || The current supporting extensions include .cpp, .C, .cc.\r\n","4":"\\\" || Switch c++ h and cpp\r\n\\\" || Jia Hongyuan, 2014-03-06. Email: jhy817@qq.com\r\n\\\" ||\r\n\\\" || Descriptions:\r\n\\\" || This script is designed to quickly switch current vim buffer between c\/c++\r\n\\\" || header and cpp files. You can easily add new file extensions by changing \\\"exts\\\" variable.\r\n\\\" || The current supporting extensions include .cpp, .C, .cc.\r\n","install_details":"\\\" || Installation:\r\n\\\" || 1. Copy this .vim file into .vim\/plugin folder. You can change the logger\r\n\\\" || level, if you want to suppress the redundant output information.\r\n\\\" || 2. Set shortcut in .vimrc. e.g.  nmap ,s :call Switch_h_cpp()<CR>\r\n\r\n\" vbundle git location\r\ngit location: https:\/\/github.com\/jiahongyuan\/sourceCodeSwitcherForC_CXX.git","5":"\\\" || Installation:\r\n\\\" || 1. Copy this .vim file into .vim\/plugin folder. You can change the logger\r\n\\\" || level, if you want to suppress the redundant output information.\r\n\\\" || 2. Set shortcut in .vimrc. e.g.  nmap ,s :call Switch_h_cpp()<CR>\r\n\r\n\" vbundle git location\r\ngit location: https:\/\/github.com\/jiahongyuan\/sourceCodeSwitcherForC_CXX.git","first_name":"hongyuan","6":"hongyuan","last_name":"jia","7":"jia","releases":[{"0":"4944","vim_version":"7.0","1":"7.0","script_version":"1.2","2":"1.2","version_comment":"Improved the searching performance. \r\nIf the plugin can find a target file in a folder in where current vim buffer file locates, it will load this file directly, no need to do further search.","3":"Improved the searching performance. \r\nIf the plugin can find a target file in a folder in where current vim buffer file locates, it will load this file directly, no need to do further search.","package":"Switch_h_cpp.vim","4":"Switch_h_cpp.vim","src_id":"21986","5":"21986","creation_date":"1401918784","6":"1401918784"},{"0":"4944","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"Switch_h_cpp.vim","4":"Switch_h_cpp.vim","src_id":"21914","5":"21914","creation_date":"1400701546","6":"1400701546"}]},"4943":{"script_id":"4943","0":"4943","script_name":"vim-ralf-syntax","1":"vim-ralf-syntax","script_type":"syntax","2":"syntax","summary":"Syntax highlighting for Synopsys Register Abstraction Layer ralf files","3":"Syntax highlighting for Synopsys Register Abstraction Layer ralf files","description":"Grab the latest dev version from github: https:\/\/github.com\/amal-khailtash\/vim-ralf-syntax.git\r\n\r\n### References\r\n\r\n* [VMM Register Abstraction Layer User Guide - Mar 2014](https:\/\/solvnet.synopsys.com\/dow_retrieve\/I-2014.03\/VCS\/ral_user_guide.pdf)\r\n* [UVM Register Abstraction Layer User Guide - Mar 2014](https:\/\/solvnet.synopsys.com\/dow_retrieve\/I-2014.03\/VCS\/uvm_ralgen_ug.pdf)\r\n* [VMM Register Abstraction Layer User Guide - Jul 2011](http:\/\/vmmcentral.org\/pdfs\/ral_user_guide.pdf)\r\n* [VMM Primer - Using the Register Abstraction Layer - Mar 2008](http:\/\/vmmcentral.org\/pdfs\/using_register_abstract_layer.pdf)","4":"Grab the latest dev version from github: https:\/\/github.com\/amal-khailtash\/vim-ralf-syntax.git\r\n\r\n### References\r\n\r\n* [VMM Register Abstraction Layer User Guide - Mar 2014](https:\/\/solvnet.synopsys.com\/dow_retrieve\/I-2014.03\/VCS\/ral_user_guide.pdf)\r\n* [UVM Register Abstraction Layer User Guide - Mar 2014](https:\/\/solvnet.synopsys.com\/dow_retrieve\/I-2014.03\/VCS\/uvm_ralgen_ug.pdf)\r\n* [VMM Register Abstraction Layer User Guide - Jul 2011](http:\/\/vmmcentral.org\/pdfs\/ral_user_guide.pdf)\r\n* [VMM Primer - Using the Register Abstraction Layer - Mar 2008](http:\/\/vmmcentral.org\/pdfs\/using_register_abstract_layer.pdf)","install_details":"Syntax highlighting for Synopsys Register Abstraction Layer ralf files.\r\n\r\n## Installation\r\n\r\n_\\*Assuming **[VIM_ROOT]** is ~\/.vim (on \\*nix) or ~\/vimfiles (on Windows)_\r\n\r\nThis syntax file requires Vim 7 or higher and is made up of 2 files:\r\n\r\n    ftdetect\/ralf.vim\r\n    syntax\/ralf.vim\r\n\r\n### Classic Install\r\n\r\n* Extract the zip contents to your **[VIM_ROOT]**\r\n\r\n### Vundle Install\r\n\r\n* Add \"Bundle 'vim-ralf-syntax'\" to your vimrc\r\n\r\n### Pathogen Install\r\n\r\n1. Navigate to your **[VIM_ROOT]\/bundle** directory\r\n2. git clone https:\/\/github.com\/amal-khailtash\/vim-ralf-syntax.git\r\n","5":"Syntax highlighting for Synopsys Register Abstraction Layer ralf files.\r\n\r\n## Installation\r\n\r\n_\\*Assuming **[VIM_ROOT]** is ~\/.vim (on \\*nix) or ~\/vimfiles (on Windows)_\r\n\r\nThis syntax file requires Vim 7 or higher and is made up of 2 files:\r\n\r\n    ftdetect\/ralf.vim\r\n    syntax\/ralf.vim\r\n\r\n### Classic Install\r\n\r\n* Extract the zip contents to your **[VIM_ROOT]**\r\n\r\n### Vundle Install\r\n\r\n* Add \"Bundle 'vim-ralf-syntax'\" to your vimrc\r\n\r\n### Pathogen Install\r\n\r\n1. Navigate to your **[VIM_ROOT]\/bundle** directory\r\n2. git clone https:\/\/github.com\/amal-khailtash\/vim-ralf-syntax.git\r\n","first_name":"Amal","6":"Amal","last_name":"Khailtash","7":"Khailtash","releases":[{"0":"4943","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"vim-ralf-syntax.zip","4":"vim-ralf-syntax.zip","src_id":"21913","5":"21913","creation_date":"1400695208","6":"1400695208"}]},"4942":{"script_id":"4942","0":"4942","script_name":"vim-do-syntax","1":"vim-do-syntax","script_type":"syntax","2":"syntax","summary":"Syntax highlighting for Mentor Graphics Questa Sim do files","3":"Syntax highlighting for Mentor Graphics Questa Sim do files","description":"Grab the latest dev version from github: https:\/\/github.com\/amal-khailtash\/vim-do-syntax.git\r\n\r\n### References\r\n\r\n* [Questa SIM Command Reference Manual v10.3a](http:\/\/supportnet.mentor.com\/docs\/201404102\/docs\/pdfdocs\/questa_sim_ref.pdf)","4":"Grab the latest dev version from github: https:\/\/github.com\/amal-khailtash\/vim-do-syntax.git\r\n\r\n### References\r\n\r\n* [Questa SIM Command Reference Manual v10.3a](http:\/\/supportnet.mentor.com\/docs\/201404102\/docs\/pdfdocs\/questa_sim_ref.pdf)","install_details":"## Installation\r\n\r\n_\\*Assuming **[VIM_ROOT]** is ~\/.vim (on \\*nix) or ~\/vimfiles (on Windows)_\r\n\r\nThis syntax file requires Vim 7 or higher and is made up of 2 files:\r\n\r\n    ftdetect\/do.vim\r\n    syntax\/do.vim\r\n\r\n### Classic Install\r\n\r\n* Extract the zip contents to your **[VIM_ROOT]**\r\n\r\n### Vundle Install\r\n\r\n* Add \"Bundle 'vim-do-syntax'\" to your vimrc\r\n\r\n### Pathogen Install\r\n\r\n1. Navigate to your **[VIM_ROOT]\/bundle** directory\r\n2. git clone https:\/\/github.com\/amal-khailtash\/vim-do-syntax.git\r\n","5":"## Installation\r\n\r\n_\\*Assuming **[VIM_ROOT]** is ~\/.vim (on \\*nix) or ~\/vimfiles (on Windows)_\r\n\r\nThis syntax file requires Vim 7 or higher and is made up of 2 files:\r\n\r\n    ftdetect\/do.vim\r\n    syntax\/do.vim\r\n\r\n### Classic Install\r\n\r\n* Extract the zip contents to your **[VIM_ROOT]**\r\n\r\n### Vundle Install\r\n\r\n* Add \"Bundle 'vim-do-syntax'\" to your vimrc\r\n\r\n### Pathogen Install\r\n\r\n1. Navigate to your **[VIM_ROOT]\/bundle** directory\r\n2. git clone https:\/\/github.com\/amal-khailtash\/vim-do-syntax.git\r\n","first_name":"Amal","6":"Amal","last_name":"Khailtash","7":"Khailtash","releases":[{"0":"4942","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"vim-do-syntax.zip","4":"vim-do-syntax.zip","src_id":"21912","5":"21912","creation_date":"1400695175","6":"1400695175"}]},"4941":{"script_id":"4941","0":"4941","script_name":"Vebugger","1":"Vebugger","script_type":"utility","2":"utility","summary":"frontend for interactive shell debuggers","3":"frontend for interactive shell debuggers","description":"GitHub repository: https:\/\/github.com\/idanarye\/vim-vebugger\r\n\r\nVebugger is yet another debugger frontend plugin for Vim, created because I wasn't happy with the other debugger plugins I found. Vebugger currently supports GDB, JDB, Mdbg, PDB and RDebug.\r\n\r\nVebugger is developed under Linux. It doesn't work properly under Windows due to lack of PTY support. I have neither plans nor means to support OSX, but I will accept pull requests that add OSX support.","4":"GitHub repository: https:\/\/github.com\/idanarye\/vim-vebugger\r\n\r\nVebugger is yet another debugger frontend plugin for Vim, created because I wasn't happy with the other debugger plugins I found. Vebugger currently supports GDB, JDB, Mdbg, PDB and RDebug.\r\n\r\nVebugger is developed under Linux. It doesn't work properly under Windows due to lack of PTY support. I have neither plans nor means to support OSX, but I will accept pull requests that add OSX support.","install_details":"","5":"","first_name":"Idan","6":"Idan","last_name":"Arye","7":"Arye","releases":[{"0":"4941","vim_version":"7.3","1":"7.3","script_version":"1.2.3","2":"1.2.3","version_comment":"Fix issue #17 - prevent Vebugger from interfering with the CtrlP window.","3":"Fix issue #17 - prevent Vebugger from interfering with the CtrlP window.","package":"vebugger_v1.2.3.zip","4":"vebugger_v1.2.3.zip","src_id":"23325","5":"23325","creation_date":"1432905582","6":"1432905582"},{"0":"4941","vim_version":"7.3","1":"7.3","script_version":"1.2.2","2":"1.2.2","version_comment":"Fix Vim7.3 compatibility","3":"Fix Vim7.3 compatibility","package":"vebugger_v1.2.2.zip","4":"vebugger_v1.2.2.zip","src_id":"22830","5":"22830","creation_date":"1422322946","6":"1422322946"},{"0":"4941","vim_version":"7.0","1":"7.0","script_version":"1.2.1","2":"1.2.1","version_comment":"Fix MDbg support in Cygwin","3":"Fix MDbg support in Cygwin","package":"vebugger_v1.2.1.zip","4":"vebugger_v1.2.1.zip","src_id":"22793","5":"22793","creation_date":"1421348500","6":"1421348500"},{"0":"4941","vim_version":"7.0","1":"7.0","script_version":"1.2.0","2":"1.2.0","version_comment":"* Allow GDB to work with Dlang executables\r\n* Add support for multiple versions of debuggers\r\n* Fix for line stops in GDB","3":"* Allow GDB to work with Dlang executables\r\n* Add support for multiple versions of debuggers\r\n* Fix for line stops in GDB","package":"vebugger_v1.2.0.zip","4":"vebugger_v1.2.0.zip","src_id":"22381","5":"22381","creation_date":"1409349079","6":"1409349079"},{"0":"4941","vim_version":"7.0","1":"7.0","script_version":"1.1.0","2":"1.1.0","version_comment":"This is embarrassing... I forgot to put an important file in the zip...","3":"This is embarrassing... I forgot to put an important file in the zip...","package":"vebugger_v1.1.0.zip","4":"vebugger_v1.1.0.zip","src_id":"21984","5":"21984","creation_date":"1401900201","6":"1401900201"},{"0":"4941","vim_version":"7.0","1":"7.0","script_version":"1.1.0","2":"1.1.0","version_comment":"* Add windows support\r\n* Add Mdbg support\r\n* Allow setting paths to executables with global variables","3":"* Add windows support\r\n* Add Mdbg support\r\n* Allow setting paths to executables with global variables","package":"vebugger_v1.1.0.zip","4":"vebugger_v1.1.0.zip","src_id":"21931","5":"21931","creation_date":"1400858468","6":"1400858468"},{"0":"4941","vim_version":"7.0","1":"7.0","script_version":"1.0.0","2":"1.0.0","version_comment":"Initial upload","3":"Initial upload","package":"vebugger_v1.0.0.zip","4":"vebugger_v1.0.0.zip","src_id":"21907","5":"21907","creation_date":"1400523826","6":"1400523826"}]},"4940":{"script_id":"4940","0":"4940","script_name":"BufLine","1":"BufLine","script_type":"utility","2":"utility","summary":"This script will show your buffer list in the tabline.","3":"This script will show your buffer list in the tabline.","description":"  Note: if you are actively using tabs in VIM, this script will probably be of no use to you.\r\n\r\n  The script is pretty similar to the miniBufExpl, except it uses vim |tabline| instead of dedicated split to show your buffer list. For detailed user manual type \":h BufLine\" command after you install the srcipt.","4":"  Note: if you are actively using tabs in VIM, this script will probably be of no use to you.\r\n\r\n  The script is pretty similar to the miniBufExpl, except it uses vim |tabline| instead of dedicated split to show your buffer list. For detailed user manual type \":h BufLine\" command after you install the srcipt.","install_details":"1. Extract tarball into your $HOME\/.vim directory.\r\n2. Rebuild help tags index by issuing \":helptags $HOME\/.vim\/doc\" command.\r\n3. Read user manual and add desired settings into your $HOME\/.vimrc file.\r\n4. Restart the VIM.\r\n\r\nThe directories may differ in your VIM installation. See |.vimrc|.","5":"1. Extract tarball into your $HOME\/.vim directory.\r\n2. Rebuild help tags index by issuing \":helptags $HOME\/.vim\/doc\" command.\r\n3. Read user manual and add desired settings into your $HOME\/.vimrc file.\r\n4. Restart the VIM.\r\n\r\nThe directories may differ in your VIM installation. See |.vimrc|.","first_name":"Valentin","6":"Valentin","last_name":"Gleevoy","7":"Gleevoy","releases":[{"0":"4940","vim_version":"7.4","1":"7.4","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"bufline.tar","4":"bufline.tar","src_id":"21906","5":"21906","creation_date":"1400515535","6":"1400515535"}]},"4939":{"script_id":"4939","0":"4939","script_name":"TWstack","1":"TWstack","script_type":"utility","2":"utility","summary":"Smart commands for moving between tab pages and windows with history stacks.","3":"Smart commands for moving between tab pages and windows with history stacks.","description":"TWstack has several commands for changing tab pages and windows.\r\nThere are commands for changing to the previously active window of tab\r\npage.  There are also commands for saving window and tab pages on\r\nstacks and returning to those saved windows and tab pages, also \r\ncommands for viewing and manipulating those stacks.\r\n\r\nAll of the saved window and tab page information is done using unique\r\nidentifiers assigned to each window and tab page when they are created.\r\nChanging the order of the windows or tab pages will not affect the saved\r\ninformation.\r\n\r\nRead the help file for detailed information:\r\n:help twstack.txt","4":"TWstack has several commands for changing tab pages and windows.\r\nThere are commands for changing to the previously active window of tab\r\npage.  There are also commands for saving window and tab pages on\r\nstacks and returning to those saved windows and tab pages, also \r\ncommands for viewing and manipulating those stacks.\r\n\r\nAll of the saved window and tab page information is done using unique\r\nidentifiers assigned to each window and tab page when they are created.\r\nChanging the order of the windows or tab pages will not affect the saved\r\ninformation.\r\n\r\nRead the help file for detailed information:\r\n:help twstack.txt","install_details":"Open twstack.vmb in vim\r\nSource it with:\r\n:so %\r\nRead the help file:\r\n:help twstack.txt","5":"Open twstack.vmb in vim\r\nSource it with:\r\n:so %\r\nRead the help file:\r\n:help twstack.txt","first_name":"Steve","6":"Steve","last_name":"Jones","7":"Jones","releases":[{"0":"4939","vim_version":"7.4","1":"7.4","script_version":"1.00","2":"1.00","version_comment":"Initial upload","3":"Initial upload","package":"twstack.vmb","4":"twstack.vmb","src_id":"21903","5":"21903","creation_date":"1400449028","6":"1400449028"}]},"4938":{"script_id":"4938","0":"4938","script_name":"cmake","1":"cmake","script_type":"syntax","2":"syntax","summary":"CMake syntax update","3":"CMake syntax update","description":"Simple syntax updates for CMake (www.cmake.org) syntax highlighting in Vim, to include new names added all the way to cmake v2.8.12\r\n\r\nThis script is only an after\/syntax file and it still uses the syntax\/cmake.vim file provided by Vim. Script only adds new language keywords and names to be highlighted.\r\n\r\nSyntax changes:\r\n   - new CMake commands\r\n   - CMake-provided variables \r\n   - CMake properties\r\n   - CMake \"generator expressions\"","4":"Simple syntax updates for CMake (www.cmake.org) syntax highlighting in Vim, to include new names added all the way to cmake v2.8.12\r\n\r\nThis script is only an after\/syntax file and it still uses the syntax\/cmake.vim file provided by Vim. Script only adds new language keywords and names to be highlighted.\r\n\r\nSyntax changes:\r\n   - new CMake commands\r\n   - CMake-provided variables \r\n   - CMake properties\r\n   - CMake \"generator expressions\"","install_details":"Download the cmake.vmb file and open the file in Vim. With the file open, type the following Vim command:\r\n       :source %\r\n\r\nThe file will then be installed in your \"~\/.vim\/after\/syntax\/\" directory (Unix) or \"%UserProfile%\/vimfiles\/after\/syntax\/\" directory (Windows)\r\n\r\nIf you happen to already have another after\/syntax\/cmake.vim file (perhaps your own), you can create an after\/syntax\/cmake\/ directory to contain them both.","5":"Download the cmake.vmb file and open the file in Vim. With the file open, type the following Vim command:\r\n       :source %\r\n\r\nThe file will then be installed in your \"~\/.vim\/after\/syntax\/\" directory (Unix) or \"%UserProfile%\/vimfiles\/after\/syntax\/\" directory (Windows)\r\n\r\nIf you happen to already have another after\/syntax\/cmake.vim file (perhaps your own), you can create an after\/syntax\/cmake\/ directory to contain them both.","first_name":"Timothy","6":"Timothy","last_name":"Madden","7":"Madden","releases":[{"0":"4938","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"cmake.vmb","4":"cmake.vmb","src_id":"21886","5":"21886","creation_date":"1400178597","6":"1400178597"}]},"4937":{"script_id":"4937","0":"4937","script_name":"RubyJump","1":"RubyJump","script_type":"utility","2":"utility","summary":"Vim plugin for ruby editing. Quick jump to method, class, module defenitions.","3":"Vim plugin for ruby editing. Quick jump to method, class, module defenitions.","description":"https:\/\/github.com\/xmisao\/rubyjump.vim","4":"https:\/\/github.com\/xmisao\/rubyjump.vim","install_details":"","5":"","first_name":"x","6":"x","last_name":"misao","7":"misao","releases":[{"0":"4937","vim_version":"7.4","1":"7.4","script_version":"0.9.2","2":"0.9.2","version_comment":"- Bug fix\r\n- Improvement parsing\r\n- add g:rubyjump#enable_ripper variable\r\n- add g:rubyjump#filetypes variable","3":"- Bug fix\r\n- Improvement parsing\r\n- add g:rubyjump#enable_ripper variable\r\n- add g:rubyjump#filetypes variable","package":"rubyjump.vim-0.9.2.zip","4":"rubyjump.vim-0.9.2.zip","src_id":"21892","5":"21892","creation_date":"1400223688","6":"1400223688"},{"0":"4937","vim_version":"7.4","1":"7.4","script_version":"0.9.1","2":"0.9.1","version_comment":"Initial upload","3":"Initial upload","package":"rubyjump.vim-0.9.1.zip","4":"rubyjump.vim-0.9.1.zip","src_id":"21879","5":"21879","creation_date":"1399912434","6":"1399912434"}]},"4936":{"script_id":"4936","0":"4936","script_name":"mrtg.vim","1":"mrtg.vim","script_type":"syntax","2":"syntax","summary":"Multi Router Traffic Grapher config file","3":"Multi Router Traffic Grapher config file","description":"Syntax highlight for MRTG (Multi Router Traffic Grapher) config files\r\n\r\nPreliminary version (only keywords and some other stuff)\r\nNeeds testing, therefore feedback|suggestions|improvements are wellcome\r\n\r\n","4":"Syntax highlight for MRTG (Multi Router Traffic Grapher) config files\r\n\r\nPreliminary version (only keywords and some other stuff)\r\nNeeds testing, therefore feedback|suggestions|improvements are wellcome\r\n\r\n","install_details":"copy to $HOME\/.vim\/syntax or \/usr\/share\/vim\/vim73\/syntax","5":"copy to $HOME\/.vim\/syntax or \/usr\/share\/vim\/vim73\/syntax","first_name":"Pep B. ","6":"Pep B. ","last_name":"Alsina","7":"Alsina","releases":[{"0":"4936","vim_version":"7.0","1":"7.0","script_version":"7.3","2":"7.3","version_comment":"Initial upload","3":"Initial upload","package":"mrtg.vim","4":"mrtg.vim","src_id":"21873","5":"21873","creation_date":"1399590463","6":"1399590463"}]},"4935":{"script_id":"4935","0":"4935","script_name":"Syntax for Clustal","1":"Syntax for Clustal","script_type":"syntax","2":"syntax","summary":"Highlighting for Clustal Alignment","3":"Highlighting for Clustal Alignment","description":"Syntax highlighting clustal alignment generated by clustalw or clustalx","4":"Syntax highlighting clustal alignment generated by clustalw or clustalx","install_details":"Copy clustal.vim into your syntax folder.\r\n\r\nTo tell vim detect clustal files automatically, please put the following line into .vimrc or filetype.vim\r\n\r\nau BufNewFile,BufRead *.aln  setf clustal","5":"Copy clustal.vim into your syntax folder.\r\n\r\nTo tell vim detect clustal files automatically, please put the following line into .vimrc or filetype.vim\r\n\r\nau BufNewFile,BufRead *.aln  setf clustal","first_name":"Qinhu","6":"Qinhu","last_name":"Wang","7":"Wang","releases":[{"0":"4935","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"clustal.vim","4":"clustal.vim","src_id":"21871","5":"21871","creation_date":"1399428563","6":"1399428563"}]},"4933":{"script_id":"4933","0":"4933","script_name":"lite-dfm","1":"lite-dfm","script_type":"utility","2":"utility","summary":"A plugin to remove distractions","3":"A plugin to remove distractions","description":"A lightweight plugin to remove distractions from Vim.\r\n\r\nThis is based loosely on Distraction Free Mode in Sublime Text.\r\n\r\nA key differentiator from most other implementations of distraction free writing in Vim is that support for vsplits remains uncrippled. This comes at the expense of proper centering, though, so there\\'s a tradeoff.","4":"A lightweight plugin to remove distractions from Vim.\r\n\r\nThis is based loosely on Distraction Free Mode in Sublime Text.\r\n\r\nA key differentiator from most other implementations of distraction free writing in Vim is that support for vsplits remains uncrippled. This comes at the expense of proper centering, though, so there\\'s a tradeoff.","install_details":"","5":"","first_name":"Bilal","6":"Bilal","last_name":"Quadri","7":"Quadri","releases":[{"0":"4933","vim_version":"7.2","1":"7.2","script_version":"1.0.0","2":"1.0.0","version_comment":"Initial upload","3":"Initial upload","package":"lite-dfm.tar.gz","4":"lite-dfm.tar.gz","src_id":"21852","5":"21852","creation_date":"1399098917","6":"1399098917"}]},"4932":{"script_id":"4932","0":"4932","script_name":"diffchar.vim","1":"diffchar.vim","script_type":"utility","2":"utility","summary":"Highlight the exact differences, based on characters and words","3":"Highlight the exact differences, based on characters and words","description":"This plugin has been developed in order to make diff mode more useful. Vim highlights all the text in between the first and last different characters on a changed line. But this plugin will find the exact differences between them, character by character - so called DiffChar.\r\n\r\nFor example, in diff mode: ( [DiffText], <DiffAdd> )\r\n\r\n    (window A) The [quick brown fox jumps over the lazy] dog.\r\n    (window B) The [lazy fox jumps over the quick brown] dog.\r\n\r\nthis plugin will exactly show the changed and added units:\r\n\r\n    (window A) The [quick] <brown >fox jumps over the [lazy] dog.\r\n    (window B) The [lazy] fox jumps over the [quick] <brown >dog.\r\n\r\nFor details and demo samples, please visit the following git repository: https:\/\/github.com\/rickhowe\/diffchar.vim","4":"This plugin has been developed in order to make diff mode more useful. Vim highlights all the text in between the first and last different characters on a changed line. But this plugin will find the exact differences between them, character by character - so called DiffChar.\r\n\r\nFor example, in diff mode: ( [DiffText], <DiffAdd> )\r\n\r\n    (window A) The [quick brown fox jumps over the lazy] dog.\r\n    (window B) The [lazy fox jumps over the quick brown] dog.\r\n\r\nthis plugin will exactly show the changed and added units:\r\n\r\n    (window A) The [quick] <brown >fox jumps over the [lazy] dog.\r\n    (window B) The [lazy] fox jumps over the [quick] <brown >dog.\r\n\r\nFor details and demo samples, please visit the following git repository: https:\/\/github.com\/rickhowe\/diffchar.vim","install_details":"Install 'rickhowe\/diffchar.vim' by using your plugin manager. Or manually unzip and copy all folders in your ~\/.vim or ~\/vimfiles.","5":"Install 'rickhowe\/diffchar.vim' by using your plugin manager. Or manually unzip and copy all folders in your ~\/.vim or ~\/vimfiles.","first_name":"Rick","6":"Rick","last_name":"Howe","7":"Howe","releases":[{"0":"4932","vim_version":"8.2","1":"8.2","script_version":"9.7","2":"9.7","version_comment":"Implemented to use a new builtin diff() function to compare diff units and make it faster in vim.","3":"Implemented to use a new builtin diff() function to compare diff units and make it faster in vim.","package":"diffchar9.7.zip","4":"diffchar9.7.zip","src_id":"28608","5":"28608","creation_date":"1707887007","6":"1707887007"},{"0":"4932","vim_version":"8.2","1":"8.2","script_version":"9.61","2":"9.61","version_comment":"Changed not to incrementally check the diff lines upon scrolling or searching. Fixed not to use hl-DiffText if [{hlg}] is specified in the g:DiffColors option.","3":"Changed not to incrementally check the diff lines upon scrolling or searching. Fixed not to use hl-DiffText if [{hlg}] is specified in the g:DiffColors option.","package":"diffchar9.61.zip","4":"diffchar9.61.zip","src_id":"28516","5":"28516","creation_date":"1689516195","6":"1689516195"},{"0":"4932","vim_version":"8.0","1":"8.0","script_version":"8.91","2":"8.91","version_comment":"Updated to check a new WinClosed event to appropriately reset\/repair the highlighted diff units.","3":"Updated to check a new WinClosed event to appropriately reset\/repair the highlighted diff units.","package":"diffchar8.91.zip","4":"diffchar8.91.zip","src_id":"27830","5":"27830","creation_date":"1638911383","6":"1638911383"},{"0":"4932","vim_version":"7.0","1":"7.0","script_version":"7.6","2":"7.6","version_comment":"Improved to make DiffChar highlights draw faster.","3":"Improved to make DiffChar highlights draw faster.","package":"diffchar7.6.zip","4":"diffchar7.6.zip","src_id":"26142","5":"26142","creation_date":"1532276421","6":"1532276421"},{"0":"4932","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"diffchar.vim","4":"diffchar.vim","src_id":"21850","5":"21850","creation_date":"1399032413","6":"1399032413"}]},"4931":{"script_id":"4931","0":"4931","script_name":"vimtux","1":"vimtux","script_type":"utility","2":"utility","summary":"Send commands from Vim to Tmux.","3":"Send commands from Vim to Tmux.","description":"Installation\r\n\r\nVundle:\r\nIn your .vimrc place Plugin 'brauner\/vimtux' between call vundle#begin() and call vundle#end(). Then open vim and install with :PluginInstall.\r\n\r\nPathogen:\r\ncd ~\/.vim\/bundle\r\ngit clone https:\/\/github.com\/brauner\/vimtux.git\r\n\r\nFind the current script on Github: https:\/\/github.com\/lord-garbage\/vimtux\r\n\r\nThis is a simple Vim script to send text, commands and keys from a Vim buffer to a running tmux session. Its main objective is to stay as simple as possible following the famous KISS principle. This means it does not rely on the presence of any external files, programming languages whatsoever and it will stay that way. Forever. Period. It does exactly what it was designed for no more no less: Send text, commands and keys to any Tmux session via Vim. You will find the details below.\r\n\r\nNote: If you use version of tmux ealier than 1.3, you should use the stable branch. The version available in that branch isn't aware of panes so it will paste to pane 0 of the window.\r\n\r\n(1) vimtux provides the ability to send multiple keys to a tmux target at once.\r\n\r\n(2) The tmux target is set on buffer basis. This means that every tab in Vim can have its own tmux target. (E.g. you could have a tab in which you edit a Python script and send text and keys to a Python repl and another tab in which you edit an R script and send text and keys to an R repl.)\r\n\r\n(3) vimtux allows you to refer to panes and windows either via their dynamic identifier which is a simple number. Or via their unique identifier. For panes their unique identifier is a number prefixed with % and for windows a number prefixed with @.\r\n\r\na) Demonstrative Reference\/Dynamic Reference:\r\n\r\n\u00c2\u00b7 Panes: If you choose to refer to a pane via its dynamic identifier the target of any given send function in this script will change when you insert a new pane before the pane you used.\r\n\r\n\u00c2\u00b7 Windows (slightly more complex to explain): Assume you have set set-window-option -g automatic-rename on in your ~\/.tmux.conf. This is quite useful when you want to have an easy way of seeing what program is currently running in any given tmux window. But it is not very useful when you switch programs in a tmux window a lot but still want to be able to send commands and keys from the same window or pane to these different programs. Because refering to the window via its name given to it by the program currently running will break the connection between the window running the program and the window you are sending commands and keys from once that program is exited.\r\n\r\nb) Proper Name\/Static Reference: If you choose to refer to a pane via its unique identifier the target of any given send function in this script will stay fixed.\r\n\r\nb) Proper Name\/Static Reference: If you choose to refer to a window via its unique identifier the target of any given send function in this script will stay fixed while allowing that the program currently running in that window is setting the name for that session.\r\n\r\nTip: You can find out the unique identifier of a pane by either passing tmux list-panes -t x where x is the name of the session. Or (the easier way) you let the unique identifier of every pane be shown in your tmux status bar with the option #D; e.g.: set -g status-left '#D'. (All possible options about what to display in the statusbar can be found via man tmux or some internet searching.)\r\n\r\nI suggest using something like this in your .tmux.conf:\r\n\r\n# Status bar.\r\n\r\nset -g status-interval 2\r\n\r\nset -g status-right '[#D|#P|#T] '\r\n\r\nset -g status-left '[#{session_id}|#S]'\r\n\r\nset-option -g status-justify centre\r\n\r\n# Disable showing the default window list component and trim it to a more specific format.\r\n\r\nset-window-option -g window-status-current-format '[#F|#{window_id}|#I|#W|#{window_panes}]'\r\n\r\nset-window-option -g window-status-format '[#F|#{window_id}|#I|#W|#{window_panes}]'\r\n\r\nwhich gives you: #{session_id} := unique session ID, #S := session title, #F := window flags (Info about which windows is active etc.), #{window_id} := unique window ID, #I := window index, #W := window title, #{window_panes} := number of active panes in current window, #D := unique pane number, #P := dynamic pane number, #T := pane title, The characters [, ] and | are just used to secure visibility and do not have any further meaning.\r\n\r\nA last hint: If you fancy it you can rename panes. Just issue printf '\\033]2;%s\\033\\\\' 'hello' in any pane and observe how #T will change.\r\n\r\n(For fun: Consider including #D and #P in your statusbar for a moment in order to see how tmux changes the dynamic window number for every pane that comes after the one you just opened and how #D stays fixed.)\r\n\r\n(4) Keybindings are not set automatically for you. Instead, you can map whatever you'd like to one of the plugin-specific bindings in your .vimrc file.","4":"Installation\r\n\r\nVundle:\r\nIn your .vimrc place Plugin 'brauner\/vimtux' between call vundle#begin() and call vundle#end(). Then open vim and install with :PluginInstall.\r\n\r\nPathogen:\r\ncd ~\/.vim\/bundle\r\ngit clone https:\/\/github.com\/brauner\/vimtux.git\r\n\r\nFind the current script on Github: https:\/\/github.com\/lord-garbage\/vimtux\r\n\r\nThis is a simple Vim script to send text, commands and keys from a Vim buffer to a running tmux session. Its main objective is to stay as simple as possible following the famous KISS principle. This means it does not rely on the presence of any external files, programming languages whatsoever and it will stay that way. Forever. Period. It does exactly what it was designed for no more no less: Send text, commands and keys to any Tmux session via Vim. You will find the details below.\r\n\r\nNote: If you use version of tmux ealier than 1.3, you should use the stable branch. The version available in that branch isn't aware of panes so it will paste to pane 0 of the window.\r\n\r\n(1) vimtux provides the ability to send multiple keys to a tmux target at once.\r\n\r\n(2) The tmux target is set on buffer basis. This means that every tab in Vim can have its own tmux target. (E.g. you could have a tab in which you edit a Python script and send text and keys to a Python repl and another tab in which you edit an R script and send text and keys to an R repl.)\r\n\r\n(3) vimtux allows you to refer to panes and windows either via their dynamic identifier which is a simple number. Or via their unique identifier. For panes their unique identifier is a number prefixed with % and for windows a number prefixed with @.\r\n\r\na) Demonstrative Reference\/Dynamic Reference:\r\n\r\n\u00c2\u00b7 Panes: If you choose to refer to a pane via its dynamic identifier the target of any given send function in this script will change when you insert a new pane before the pane you used.\r\n\r\n\u00c2\u00b7 Windows (slightly more complex to explain): Assume you have set set-window-option -g automatic-rename on in your ~\/.tmux.conf. This is quite useful when you want to have an easy way of seeing what program is currently running in any given tmux window. But it is not very useful when you switch programs in a tmux window a lot but still want to be able to send commands and keys from the same window or pane to these different programs. Because refering to the window via its name given to it by the program currently running will break the connection between the window running the program and the window you are sending commands and keys from once that program is exited.\r\n\r\nb) Proper Name\/Static Reference: If you choose to refer to a pane via its unique identifier the target of any given send function in this script will stay fixed.\r\n\r\nb) Proper Name\/Static Reference: If you choose to refer to a window via its unique identifier the target of any given send function in this script will stay fixed while allowing that the program currently running in that window is setting the name for that session.\r\n\r\nTip: You can find out the unique identifier of a pane by either passing tmux list-panes -t x where x is the name of the session. Or (the easier way) you let the unique identifier of every pane be shown in your tmux status bar with the option #D; e.g.: set -g status-left '#D'. (All possible options about what to display in the statusbar can be found via man tmux or some internet searching.)\r\n\r\nI suggest using something like this in your .tmux.conf:\r\n\r\n# Status bar.\r\n\r\nset -g status-interval 2\r\n\r\nset -g status-right '[#D|#P|#T] '\r\n\r\nset -g status-left '[#{session_id}|#S]'\r\n\r\nset-option -g status-justify centre\r\n\r\n# Disable showing the default window list component and trim it to a more specific format.\r\n\r\nset-window-option -g window-status-current-format '[#F|#{window_id}|#I|#W|#{window_panes}]'\r\n\r\nset-window-option -g window-status-format '[#F|#{window_id}|#I|#W|#{window_panes}]'\r\n\r\nwhich gives you: #{session_id} := unique session ID, #S := session title, #F := window flags (Info about which windows is active etc.), #{window_id} := unique window ID, #I := window index, #W := window title, #{window_panes} := number of active panes in current window, #D := unique pane number, #P := dynamic pane number, #T := pane title, The characters [, ] and | are just used to secure visibility and do not have any further meaning.\r\n\r\nA last hint: If you fancy it you can rename panes. Just issue printf '\\033]2;%s\\033\\\\' 'hello' in any pane and observe how #T will change.\r\n\r\n(For fun: Consider including #D and #P in your statusbar for a moment in order to see how tmux changes the dynamic window number for every pane that comes after the one you just opened and how #D stays fixed.)\r\n\r\n(4) Keybindings are not set automatically for you. Instead, you can map whatever you'd like to one of the plugin-specific bindings in your .vimrc file.","install_details":"Installation\r\n\r\nVundle:\r\nIn your .vimrc place Plugin 'brauner\/vimtux' between call vundle#begin() and call vundle#end(). Then open vim and install with :PluginInstall.\r\n\r\nPathogen:\r\ncd ~\/.vim\/bundle\r\ngit clone https:\/\/github.com\/brauner\/vimtux.git","5":"Installation\r\n\r\nVundle:\r\nIn your .vimrc place Plugin 'brauner\/vimtux' between call vundle#begin() and call vundle#end(). Then open vim and install with :PluginInstall.\r\n\r\nPathogen:\r\ncd ~\/.vim\/bundle\r\ngit clone https:\/\/github.com\/brauner\/vimtux.git","first_name":"Christian","6":"Christian","last_name":"Brauner","7":"Brauner","releases":[{"0":"4931","vim_version":"7.0","1":"7.0","script_version":"1.6","2":"1.6","version_comment":"Adapt for Vundle and Pathogen","3":"Adapt for Vundle and Pathogen","package":"vimtux.vim","4":"vimtux.vim","src_id":"23379","5":"23379","creation_date":"1434029047","6":"1434029047"},{"0":"4931","vim_version":"7.0","1":"7.0","script_version":"1.5","2":"1.5","version_comment":"renaming, cleaning code","3":"renaming, cleaning code","package":"vimtux.vim","4":"vimtux.vim","src_id":"22407","5":"22407","creation_date":"1409826047","6":"1409826047"}]},"4930":{"script_id":"4930","0":"4930","script_name":"EightHeader","1":"EightHeader","script_type":"utility","2":"utility","summary":"Easily create custom headlines, foldtext, toc, etc.","3":"Easily create custom headlines, foldtext, toc, etc.","description":"https:\/\/github.com\/BimbaLaszlo\/vim-eightheader\r\n\r\nTo use EightHeader just move the cursor to the line which you want to modify (hereinafter line), then call it:\r\n\r\nEightHeader( {length}, {align}, {oneline}, {decor}, {marker}, {str} )\r\n\r\n{length}   Length of the header.\r\n{align}    Alignment of text.\r\n{oneline}  If false, then underline the {line} with {decor}.\r\n{decor}    Decorator text to fill with.\r\n{marker}   Extra content after decotRightEnd.\r\n{str}      Replace the content of {line} with this.\r\n\r\nAn example with {oneline} set to true (1) (s:str means the original line, see EightHeaderVars for details):\r\n\r\ncall EightHeader( 78, 'center', 1, ['l ', 'decor', ' r'], ' m', '\\=\" \".s:str.\" \"' )\r\n\r\nl decordecordecordecordeco TEXT IN THE LINE cordecordecordecordecord r m\r\n\r\nIf you don't like the default 'foldtext' you can customize it by setting to\r\nEightHeaderFolds().\r\n\r\nFor example the closed folds looks like this by default:\r\n\r\n+-- 45 lines: Fold level one\r\n+--- 67 lines: Fold level two\r\n\r\nIf you would like to change it to this kind:\r\n\r\nFold level one................45 lines\r\n  Fold level two..............67 lines\r\n\r\n... then you can use this function:\r\n\r\nlet &foldtext = \"EightHeaderFolds( '\\\\=s:fullwidth-2', 'left', [ repeat( '  ', v:foldlevel - 1 ), '.', '' ], '\\\\= s:foldlines . \\\" lines\\\"', '' )\"\r\n\r\nAn alternative usage for example formating a vimhelp table of contents:\r\n\r\nOptions;options\r\nDefault mappings;maps\r\n  Launch nuclear strike;apocalypse\r\n\r\n... to this:\r\n\r\nOptions........................................................|options|\r\nDefault mappings..................................................|maps|\r\n  Launch nuclear strike.....................................|apocalypse|\r\n\r\nVisually select the lines, than:\r\n\r\ncall EightHeader( 78, \"left\", 1, \".\", \"\\\\='|'.matchstr(s:str, ';\\\\@<=.*').'|'\", \"\\\\=matchstr(s:str, '.*;\\\\@=')\" )","4":"https:\/\/github.com\/BimbaLaszlo\/vim-eightheader\r\n\r\nTo use EightHeader just move the cursor to the line which you want to modify (hereinafter line), then call it:\r\n\r\nEightHeader( {length}, {align}, {oneline}, {decor}, {marker}, {str} )\r\n\r\n{length}   Length of the header.\r\n{align}    Alignment of text.\r\n{oneline}  If false, then underline the {line} with {decor}.\r\n{decor}    Decorator text to fill with.\r\n{marker}   Extra content after decotRightEnd.\r\n{str}      Replace the content of {line} with this.\r\n\r\nAn example with {oneline} set to true (1) (s:str means the original line, see EightHeaderVars for details):\r\n\r\ncall EightHeader( 78, 'center', 1, ['l ', 'decor', ' r'], ' m', '\\=\" \".s:str.\" \"' )\r\n\r\nl decordecordecordecordeco TEXT IN THE LINE cordecordecordecordecord r m\r\n\r\nIf you don't like the default 'foldtext' you can customize it by setting to\r\nEightHeaderFolds().\r\n\r\nFor example the closed folds looks like this by default:\r\n\r\n+-- 45 lines: Fold level one\r\n+--- 67 lines: Fold level two\r\n\r\nIf you would like to change it to this kind:\r\n\r\nFold level one................45 lines\r\n  Fold level two..............67 lines\r\n\r\n... then you can use this function:\r\n\r\nlet &foldtext = \"EightHeaderFolds( '\\\\=s:fullwidth-2', 'left', [ repeat( '  ', v:foldlevel - 1 ), '.', '' ], '\\\\= s:foldlines . \\\" lines\\\"', '' )\"\r\n\r\nAn alternative usage for example formating a vimhelp table of contents:\r\n\r\nOptions;options\r\nDefault mappings;maps\r\n  Launch nuclear strike;apocalypse\r\n\r\n... to this:\r\n\r\nOptions........................................................|options|\r\nDefault mappings..................................................|maps|\r\n  Launch nuclear strike.....................................|apocalypse|\r\n\r\nVisually select the lines, than:\r\n\r\ncall EightHeader( 78, \"left\", 1, \".\", \"\\\\='|'.matchstr(s:str, ';\\\\@<=.*').'|'\", \"\\\\=matchstr(s:str, '.*;\\\\@=')\" )","install_details":"Open in vim then run \r\n:so % \r\n\r\n... or use Vundle:\r\n\r\nAdd these lines to your .vimrc after 'call vundle#rc()' to install from the official repository (https:\/\/github.com\/BimbaLaszlo\/vim-eightheader):\r\n\r\nPlugin 'bimbalaszlo\/vim-eightheader'\r\n\r\nOpen vim again, then call ':PluginInstall'\r\n\r\nPlease rate if you using it!","5":"Open in vim then run \r\n:so % \r\n\r\n... or use Vundle:\r\n\r\nAdd these lines to your .vimrc after 'call vundle#rc()' to install from the official repository (https:\/\/github.com\/BimbaLaszlo\/vim-eightheader):\r\n\r\nPlugin 'bimbalaszlo\/vim-eightheader'\r\n\r\nOpen vim again, then call ':PluginInstall'\r\n\r\nPlease rate if you using it!","first_name":"Laszlo","6":"Laszlo","last_name":"Bimba","7":"Bimba","releases":[{"0":"4930","vim_version":"7.4","1":"7.4","script_version":"1.0","2":"1.0","version_comment":"clarified documentation","3":"clarified documentation","package":"eightheader.vmb","4":"eightheader.vmb","src_id":"23313","5":"23313","creation_date":"1432665657","6":"1432665657"},{"0":"4930","vim_version":"7.4","1":"7.4","script_version":"1.0","2":"1.0","version_comment":"Moved to github.","3":"Moved to github.","package":"eightheader.vmb","4":"eightheader.vmb","src_id":"21891","5":"21891","creation_date":"1400221027","6":"1400221027"},{"0":"4930","vim_version":"7.4","1":"7.4","script_version":"1.0","2":"1.0","version_comment":"\"Please rate\" advertisement.","3":"\"Please rate\" advertisement.","package":"eightheader.vmb","4":"eightheader.vmb","src_id":"21887","5":"21887","creation_date":"1400180072","6":"1400180072"},{"0":"4930","vim_version":"7.4","1":"7.4","script_version":"1.0","2":"1.0","version_comment":"Help about comment handling.","3":"Help about comment handling.","package":"eightheader.vmb","4":"eightheader.vmb","src_id":"21846","5":"21846","creation_date":"1398873241","6":"1398873241"},{"0":"4930","vim_version":"7.4","1":"7.4","script_version":"1.0","2":"1.0","version_comment":"Previous vimballs was broken, sorry.\r\nAdded more help.","3":"Previous vimballs was broken, sorry.\r\nAdded more help.","package":"eightheader.vmb","4":"eightheader.vmb","src_id":"21845","5":"21845","creation_date":"1398859630","6":"1398859630"}]},"4929":{"script_id":"4929","0":"4929","script_name":"unite-spell-suggest","1":"unite-spell-suggest","script_type":"utility","2":"utility","summary":"A spelling suggestion source for unite.vim","3":"A spelling suggestion source for unite.vim","description":"A unite.vim (vimscript #3396) source that displays Vim\u00e2\u0080\u0099s spelling suggestions for a word, updating live as the word under the cursor changes, and offering convenient replacement functionality to allow it to stand in stead of Vim\u00e2\u0080\u0099s z=.\r\n\r\nIf you have wished there was a slicker, less obtrusive interface than Vim\u00e2\u0080\u0099s modal full-screen one to spelling suggestions and corrections, unite-spell-suggest is for you.\r\n\r\nForked from original work by MURAOKA Yusuke and maintained by Martin Kopischke at https:\/\/github.com\/kopischke\/unite-spell-suggest.","4":"A unite.vim (vimscript #3396) source that displays Vim\u00e2\u0080\u0099s spelling suggestions for a word, updating live as the word under the cursor changes, and offering convenient replacement functionality to allow it to stand in stead of Vim\u00e2\u0080\u0099s z=.\r\n\r\nIf you have wished there was a slicker, less obtrusive interface than Vim\u00e2\u0080\u0099s modal full-screen one to spelling suggestions and corrections, unite-spell-suggest is for you.\r\n\r\nForked from original work by MURAOKA Yusuke and maintained by Martin Kopischke at https:\/\/github.com\/kopischke\/unite-spell-suggest.","install_details":"Either via classic Vimball install, or by using a git-based plugin manager and adding 'kopischke\/unite-spell-suggest'.","5":"Either via classic Vimball install, or by using a git-based plugin manager and adding 'kopischke\/unite-spell-suggest'.","first_name":"Martin","6":"Martin","last_name":"Kopischke","7":"Kopischke","releases":[{"0":"4929","vim_version":"7.0","1":"7.0","script_version":"1.1.2","2":"1.1.2","version_comment":"Bug fixes to replace actions behavior. GitHub release: https:\/\/github.com\/kopischke\/unite-spell-suggest\/releases\/tag\/v1.1.2","3":"Bug fixes to replace actions behavior. GitHub release: https:\/\/github.com\/kopischke\/unite-spell-suggest\/releases\/tag\/v1.1.2","package":"unite-spell-suggest.vmb","4":"unite-spell-suggest.vmb","src_id":"22434","5":"22434","creation_date":"1410949063","6":"1410949063"},{"0":"4929","vim_version":"7.0","1":"7.0","script_version":"1.1.1","2":"1.1.1","version_comment":"Fixes to target word selection. GitHub release with details: https:\/\/github.com\/kopischke\/unite-spell-suggest\/releases\/tag\/v1.1.1","3":"Fixes to target word selection. GitHub release with details: https:\/\/github.com\/kopischke\/unite-spell-suggest\/releases\/tag\/v1.1.1","package":"unite-spell-suggest.vmb","4":"unite-spell-suggest.vmb","src_id":"22414","5":"22414","creation_date":"1410430507","6":"1410430507"},{"0":"4929","vim_version":"7.0","1":"7.0","script_version":"1.1.0","2":"1.1.0","version_comment":"Seamless Vim spell checking integration:\r\n\r\n* the replacement actions have been rewritten to use Vim\u00e2\u0080\u0099s own spell checking functions; besides fixing all inconsistencies and bugs in the replacement behavior, this ensures you can use :spellrepall after a correction initiated by unite-spell-suggest.\r\n\r\n* replacement actions will now also work when using -no-split and startofline is set (which is the Vim default).\r\n\r\nGitHub release: https:\/\/github.com\/kopischke\/unite-spell-suggest\/releases\/tag\/v1.1.0","3":"Seamless Vim spell checking integration:\r\n\r\n* the replacement actions have been rewritten to use Vim\u00e2\u0080\u0099s own spell checking functions; besides fixing all inconsistencies and bugs in the replacement behavior, this ensures you can use :spellrepall after a correction initiated by unite-spell-suggest.\r\n\r\n* replacement actions will now also work when using -no-split and startofline is set (which is the Vim default).\r\n\r\nGitHub release: https:\/\/github.com\/kopischke\/unite-spell-suggest\/releases\/tag\/v1.1.0","package":"unite-spell-suggest.vmb","4":"unite-spell-suggest.vmb","src_id":"22368","5":"22368","creation_date":"1409146173","6":"1409146173"},{"0":"4929","vim_version":"7.0","1":"7.0","script_version":"1.0.4","2":"1.0.4","version_comment":"Fixes issue #4 ('replace_all' does not work when 'gedit' is set). Thanks to @petobens for the PR. \r\n\r\nAlso, from this release on, the Readme and License files are not included into the Vimball anymore, as their generic title is likely to cause collisions.","3":"Fixes issue #4 ('replace_all' does not work when 'gedit' is set). Thanks to @petobens for the PR. \r\n\r\nAlso, from this release on, the Readme and License files are not included into the Vimball anymore, as their generic title is likely to cause collisions.","package":"unite-spell-suggest.vmb","4":"unite-spell-suggest.vmb","src_id":"21882","5":"21882","creation_date":"1400070316","6":"1400070316"},{"0":"4929","vim_version":"7.0","1":"7.0","script_version":"1.0.3","2":"1.0.3","version_comment":"Avoid live updating on buffers that are not spelling suggestions targets and when the Unite spelling suggestion interface overlays the text buffer (i.e. '-no-split').","3":"Avoid live updating on buffers that are not spelling suggestions targets and when the Unite spelling suggestion interface overlays the text buffer (i.e. '-no-split').","package":"unite-spell-suggest.vba","4":"unite-spell-suggest.vba","src_id":"21833","5":"21833","creation_date":"1398449774","6":"1398449774"},{"0":"4929","vim_version":"7.0","1":"7.0","script_version":"1.0.2","2":"1.0.2","version_comment":"Fix duplicate help tag (no functional changes).","3":"Fix duplicate help tag (no functional changes).","package":"unite-spell-suggest.vba","4":"unite-spell-suggest.vba","src_id":"21815","5":"21815","creation_date":"1398265776","6":"1398265776"},{"0":"4929","vim_version":"7.0","1":"7.0","script_version":"1.0.1","2":"1.0.1","version_comment":"Initial upload","3":"Initial upload","package":"unite-spell-suggest.vba","4":"unite-spell-suggest.vba","src_id":"21814","5":"21814","creation_date":"1398265044","6":"1398265044"}]},"4928":{"script_id":"4928","0":"4928","script_name":"clang_pro.vim","1":"clang_pro.vim","script_type":"utility","2":"utility","summary":"auto complete c\/c++\/java ,using global make a proj to find define and reference","3":"auto complete c\/c++\/java ,using global make a proj to find define and reference","description":"This plugin use clang and  javacomplete to auto complete c\/c++\/java codes ,and use gnu global(work better than cscope for c++ and can work  for java and php) make a project to find define and callers. \r\n\r\nAll of the codes in one file . So it is small but powerful.Everyone know vim script can read this plugin and change it for yourself. That is vim's power ,do it yourself. I use it work well for ubuntu and old winxp machine, it may work well on macos X too.\r\n\r\nAny one fix bug or use it on mac os give me a email at xieyong88881@163.com  ,i will happy.\r\n\r\nFor get the all utilities of the plugin,make install clang(apt-get install clang) and gnu global(from src .\/configure make install). on Windows you must find clang.exe\/global.exe for your environment.\r\nMake  a file  name is clang_pro  at the root of your c\/c++\/java project.(all source file in it's dir or child dir)\r\nAs default key bindings,when you open a source file(.h .c .cpp .cc .cxx .java)\r\npush ',' and 'd' keys on the word for define.\r\npush ',' and 'r' for references.\r\npush ',' and 'h' for h\/c,cpp switch.\r\npush ',' and 's' for save sessions.\r\npush ',' and 'l' for load sessions.\r\npush ',' and 'e' for error info.(use clang compile for one file find err)\r\npush ',' and 'm' for will build the project using makeprg.(c\/c++ for makefile ,java for ant)\r\nWhen add . :: -> complete menu will pop up for you. You can also use key ctrl-x-o make the complete menu pop up manully.\r\nFor new version,add a smart tab complete，can work as ctrl-x-o，select for complete menu,and finish a smart code template for c\/c++\/java ,you can close it by using let g:clang_auto_tab=0\r\ntry code template,such as write 'mai' and press tab,you can change place with tab again.\r\n\r\nclang_pro file will work well for keys ,d ,r ,h ,s ,l functions with nothing in it,but for c\/c++\/java auto complete,it may need compile info lines in clang_pro file, like: \r\n\"for c\/cpp project,notice for cpp need add  stdlib path\r\nset makeprg=cd\\ ~\/pro;make \r\nlet g:clang_options = ' -std=c++11 -I \/usr\/include\/c++\/4.8\/  -I \/usr\/include\/x86_64-linux-gnu\/c++\/4.8\/   -I  ~\/test\/cpp\/include'\r\n\"for windows env\r\n\"let g:clang_options = ' -std=c++11 -fms-extensions -fms-compatibility -I \"C:\\Program Files\\Microsoft Visual Studio 10.0\\VC\\include\" '\r\n\"or for java project\r\n\"set makeprg=ant\\ -find\r\n\"set efm=%A\\ %#[javac]\\ %f:%l:\\ %m,%-Z\\ %#[javac]\\ %p^,%-C%.%#\r\n\"let g:java_classpath='.:\/skyics\/ics\/out\/host\/common\/obj\/JAVA_LIBRARIES\/layoutlib_intermediates\/classes'\r\nWith right settings in clang_pro file for your project.  the \",m\" \",e\"key binding.and auto complete when meeting . -> :: will work well.\r\n\r\nThis plugin only use clang not libclang.so,it give method to use project file auto make a pch file for speed, most of time it quick enough (first time a little delay,but follow times is quick).\r\nIf it is slow for your project, you can  write line in your .vimrc or in clang_pro file at root of your project .\r\nlet g:clang_auto = 0  \"only when you need ,ctrl-x-o to complete it.\r\nother lines can add:\r\nlet g:clang_auto_map=0  \"close default keys bindings\r\nlet g:clang_exe= 'clang'  \"you can use other clang name\r\nlet g:clang_project = 'clang_pro'   \"you can change the project file.\r\nTo other configure, make them in clang_pro file may better.like:\r\nlet g:clang_options = ' -std=c++11 -fms-extensions -fms-compatibility -I \"C:\\Program Files\\Microsoft Visual Studio 10.0\\VC\\include\" '   (notice this is in windows os using a clang version compiled by vc++)\r\nlet g:clang_use_pch=\"#include <vector>\\n#include <list>\"\r\n\r\nWhen the script start ,it will find the clang_pro file and make it work,so can write any vim settings in it .\r\n If you want a project which can quickly find define and callers .\r\nGNU GLOBAL will make a GTAGS in the root of project, you can use the abilities of it.\r\n You can use let g:clang_options to make clang work right, most of time ,include -I and macro define -D is needed.\r\nAnd if the c\/c++ header file is large for compile,you can use  g:clang_use_pch add pch file for clang, use \\n to split these headers. \r\nthe quickfix windows will not pop at  auto complete.\r\nIt is better to make the function of getting err info alone,the quickfix windows will not pop at  auto complete.","4":"This plugin use clang and  javacomplete to auto complete c\/c++\/java codes ,and use gnu global(work better than cscope for c++ and can work  for java and php) make a project to find define and callers. \r\n\r\nAll of the codes in one file . So it is small but powerful.Everyone know vim script can read this plugin and change it for yourself. That is vim's power ,do it yourself. I use it work well for ubuntu and old winxp machine, it may work well on macos X too.\r\n\r\nAny one fix bug or use it on mac os give me a email at xieyong88881@163.com  ,i will happy.\r\n\r\nFor get the all utilities of the plugin,make install clang(apt-get install clang) and gnu global(from src .\/configure make install). on Windows you must find clang.exe\/global.exe for your environment.\r\nMake  a file  name is clang_pro  at the root of your c\/c++\/java project.(all source file in it's dir or child dir)\r\nAs default key bindings,when you open a source file(.h .c .cpp .cc .cxx .java)\r\npush ',' and 'd' keys on the word for define.\r\npush ',' and 'r' for references.\r\npush ',' and 'h' for h\/c,cpp switch.\r\npush ',' and 's' for save sessions.\r\npush ',' and 'l' for load sessions.\r\npush ',' and 'e' for error info.(use clang compile for one file find err)\r\npush ',' and 'm' for will build the project using makeprg.(c\/c++ for makefile ,java for ant)\r\nWhen add . :: -> complete menu will pop up for you. You can also use key ctrl-x-o make the complete menu pop up manully.\r\nFor new version,add a smart tab complete，can work as ctrl-x-o，select for complete menu,and finish a smart code template for c\/c++\/java ,you can close it by using let g:clang_auto_tab=0\r\ntry code template,such as write 'mai' and press tab,you can change place with tab again.\r\n\r\nclang_pro file will work well for keys ,d ,r ,h ,s ,l functions with nothing in it,but for c\/c++\/java auto complete,it may need compile info lines in clang_pro file, like: \r\n\"for c\/cpp project,notice for cpp need add  stdlib path\r\nset makeprg=cd\\ ~\/pro;make \r\nlet g:clang_options = ' -std=c++11 -I \/usr\/include\/c++\/4.8\/  -I \/usr\/include\/x86_64-linux-gnu\/c++\/4.8\/   -I  ~\/test\/cpp\/include'\r\n\"for windows env\r\n\"let g:clang_options = ' -std=c++11 -fms-extensions -fms-compatibility -I \"C:\\Program Files\\Microsoft Visual Studio 10.0\\VC\\include\" '\r\n\"or for java project\r\n\"set makeprg=ant\\ -find\r\n\"set efm=%A\\ %#[javac]\\ %f:%l:\\ %m,%-Z\\ %#[javac]\\ %p^,%-C%.%#\r\n\"let g:java_classpath='.:\/skyics\/ics\/out\/host\/common\/obj\/JAVA_LIBRARIES\/layoutlib_intermediates\/classes'\r\nWith right settings in clang_pro file for your project.  the \",m\" \",e\"key binding.and auto complete when meeting . -> :: will work well.\r\n\r\nThis plugin only use clang not libclang.so,it give method to use project file auto make a pch file for speed, most of time it quick enough (first time a little delay,but follow times is quick).\r\nIf it is slow for your project, you can  write line in your .vimrc or in clang_pro file at root of your project .\r\nlet g:clang_auto = 0  \"only when you need ,ctrl-x-o to complete it.\r\nother lines can add:\r\nlet g:clang_auto_map=0  \"close default keys bindings\r\nlet g:clang_exe= 'clang'  \"you can use other clang name\r\nlet g:clang_project = 'clang_pro'   \"you can change the project file.\r\nTo other configure, make them in clang_pro file may better.like:\r\nlet g:clang_options = ' -std=c++11 -fms-extensions -fms-compatibility -I \"C:\\Program Files\\Microsoft Visual Studio 10.0\\VC\\include\" '   (notice this is in windows os using a clang version compiled by vc++)\r\nlet g:clang_use_pch=\"#include <vector>\\n#include <list>\"\r\n\r\nWhen the script start ,it will find the clang_pro file and make it work,so can write any vim settings in it .\r\n If you want a project which can quickly find define and callers .\r\nGNU GLOBAL will make a GTAGS in the root of project, you can use the abilities of it.\r\n You can use let g:clang_options to make clang work right, most of time ,include -I and macro define -D is needed.\r\nAnd if the c\/c++ header file is large for compile,you can use  g:clang_use_pch add pch file for clang, use \\n to split these headers. \r\nthe quickfix windows will not pop at  auto complete.\r\nIt is better to make the function of getting err info alone,the quickfix windows will not pop at  auto complete.","install_details":"just put clang_pro.vim in your ~\/.vim\/plugin \r\ninstall clang and GNU GLOBAL,(apt-get install clang and for new version in global source from http:\/\/gnu.april.org\/software\/global\/ using configure\/make install\r\ninstall javacomplete from http:\/\/www.vim.org\/scripts\/script.php?script_id=1785  \r\n\r\nmake a file named clang_pro at the root of your c\/c++\/java project. the content can be like\r\nwhen using a c\/cpp pro using autotools for makefile,the sample content can be:\r\n\r\nset makeprg=export\\ PATH=$PATH:\/opt\/buildroot-gcc342\/bin;cd\\ ~\/wifidog;make \r\nlet g:clang_options = '-I .\/include -I ..\/include'\r\n\"notice must use \"\\\" before when there are  ' ' in commands\r\n\r\nwhen using a java pro using ant for make,the sample content can be:\r\n\r\nset efm=%A\\ %#[javac]\\ %f:%l:\\ %m,%-Z\\ %#[javac]\\ %p^,%-C%.%#\r\nset makeprg=ant\r\nlet g:java_classpath='.:\/skyics\/ics\/out\/host\/common\/obj\/JAVA_LIBRARIES\/layoutlib_intermediates\/classes'\r\n\r\nWhen the script start ,it will find the clang_pro file and make it work,so can write any vim settings in it .\r\nAs default ,GNU GLOBAL will make a GTAGS in the root of project, you can\r\nuse the abilility of it which can quickly find define and callers. You can use let g:clang_options to make clang work well, most of time ,include and macro define is needed.\r\n\r\n If you do not want a project using gtags,write:  let g:clang_use_global = 0.\r\n\r\nAnd if the head file is large,you can use  g:clang_use_pch add pch file for clang, use \\n to split these headers.  for example:  let g:clang_use_pch=\"#include <vector>\\n#include <list>\"","5":"just put clang_pro.vim in your ~\/.vim\/plugin \r\ninstall clang and GNU GLOBAL,(apt-get install clang and for new version in global source from http:\/\/gnu.april.org\/software\/global\/ using configure\/make install\r\ninstall javacomplete from http:\/\/www.vim.org\/scripts\/script.php?script_id=1785  \r\n\r\nmake a file named clang_pro at the root of your c\/c++\/java project. the content can be like\r\nwhen using a c\/cpp pro using autotools for makefile,the sample content can be:\r\n\r\nset makeprg=export\\ PATH=$PATH:\/opt\/buildroot-gcc342\/bin;cd\\ ~\/wifidog;make \r\nlet g:clang_options = '-I .\/include -I ..\/include'\r\n\"notice must use \"\\\" before when there are  ' ' in commands\r\n\r\nwhen using a java pro using ant for make,the sample content can be:\r\n\r\nset efm=%A\\ %#[javac]\\ %f:%l:\\ %m,%-Z\\ %#[javac]\\ %p^,%-C%.%#\r\nset makeprg=ant\r\nlet g:java_classpath='.:\/skyics\/ics\/out\/host\/common\/obj\/JAVA_LIBRARIES\/layoutlib_intermediates\/classes'\r\n\r\nWhen the script start ,it will find the clang_pro file and make it work,so can write any vim settings in it .\r\nAs default ,GNU GLOBAL will make a GTAGS in the root of project, you can\r\nuse the abilility of it which can quickly find define and callers. You can use let g:clang_options to make clang work well, most of time ,include and macro define is needed.\r\n\r\n If you do not want a project using gtags,write:  let g:clang_use_global = 0.\r\n\r\nAnd if the head file is large,you can use  g:clang_use_pch add pch file for clang, use \\n to split these headers.  for example:  let g:clang_use_pch=\"#include <vector>\\n#include <list>\"","first_name":"yong","6":"yong","last_name":"xie","7":"xie","releases":[{"0":"4928","vim_version":"7.0","1":"7.0","script_version":"4.2","2":"4.2","version_comment":"using completeopt=menuone,longest for complete menu","3":"using completeopt=menuone,longest for complete menu","package":"clang_pro.vim","4":"clang_pro.vim","src_id":"23003","5":"23003","creation_date":"1425977952","6":"1425977952"},{"0":"4928","vim_version":"7.0","1":"7.0","script_version":"4.1.1","2":"4.1.1","version_comment":"add some c template code","3":"add some c template code","package":"clang_pro.vim","4":"clang_pro.vim","src_id":"22769","5":"22769","creation_date":"1420767023","6":"1420767023"},{"0":"4928","vim_version":"7.0","1":"7.0","script_version":"4.1","2":"4.1","version_comment":"make first complete quick","3":"make first complete quick","package":"clang_pro.vim","4":"clang_pro.vim","src_id":"22511","5":"22511","creation_date":"1412903876","6":"1412903876"},{"0":"4928","vim_version":"7.0","1":"7.0","script_version":"4.0","2":"4.0","version_comment":"add a smart tab complete，can work as ctrl-x-o，select for complete menu,and finish a smart code template for c\/c++\/java ,you can close it by using let g:clang_auto_tab=0","3":"add a smart tab complete，can work as ctrl-x-o，select for complete menu,and finish a smart code template for c\/c++\/java ,you can close it by using let g:clang_auto_tab=0","package":"clang_pro.vim","4":"clang_pro.vim","src_id":"22446","5":"22446","creation_date":"1411181296","6":"1411181296"},{"0":"4928","vim_version":"7.0","1":"7.0","script_version":"3.10","2":"3.10","version_comment":"make -std=c++11 as default cpp flag,remove complete word which start with '_'","3":"make -std=c++11 as default cpp flag,remove complete word which start with '_'","package":"clang_pro.vim","4":"clang_pro.vim","src_id":"22428","5":"22428","creation_date":"1410762364","6":"1410762364"},{"0":"4928","vim_version":"7.0","1":"7.0","script_version":"3.9","2":"3.9","version_comment":"add code from gtags.vim,so not need gtags.vim anymore.","3":"add code from gtags.vim,so not need gtags.vim anymore.","package":"clang_pro.vim","4":"clang_pro.vim","src_id":"22410","5":"22410","creation_date":"1409913563","6":"1409913563"},{"0":"4928","vim_version":"7.0","1":"7.0","script_version":"3.8.1","2":"3.8.1","version_comment":"add ',e' work for java","3":"add ',e' work for java","package":"clang_pro.vim","4":"clang_pro.vim","src_id":"22392","5":"22392","creation_date":"1409492511","6":"1409492511"},{"0":"4928","vim_version":"7.0","1":"7.0","script_version":"3.8","2":"3.8","version_comment":"add key binding \",e\" for error info,now only work for cpp","3":"add key binding \",e\" for error info,now only work for cpp","package":"clang_pro.vim","4":"clang_pro.vim","src_id":"22374","5":"22374","creation_date":"1409233555","6":"1409233555"},{"0":"4928","vim_version":"7.0","1":"7.0","script_version":"3.7","2":"3.7","version_comment":"fix c++ head\/source file switch can't use .cc file bug.","3":"fix c++ head\/source file switch can't use .cc file bug.","package":"clang_pro.vim","4":"clang_pro.vim","src_id":"22347","5":"22347","creation_date":"1408435523","6":"1408435523"},{"0":"4928","vim_version":"7.0","1":"7.0","script_version":"3.6","2":"3.6","version_comment":"remove '#' make clang complete more clear","3":"remove '#' make clang complete more clear","package":"clang_pro.vim","4":"clang_pro.vim","src_id":"22329","5":"22329","creation_date":"1408089918","6":"1408089918"},{"0":"4928","vim_version":"7.0","1":"7.0","script_version":"3.5","2":"3.5","version_comment":"only bug fix","3":"only bug fix","package":"clang_pro.vim","4":"clang_pro.vim","src_id":"22171","5":"22171","creation_date":"1404867262","6":"1404867262"},{"0":"4928","vim_version":"7.0","1":"7.0","script_version":"3.4","2":"3.4","version_comment":"add default key ,m for :make<CR>","3":"add default key ,m for :make<CR>","package":"clang_pro.vim","4":"clang_pro.vim","src_id":"22023","5":"22023","creation_date":"1402627408","6":"1402627408"},{"0":"4928","vim_version":"7.0","1":"7.0","script_version":"3.3","2":"3.3","version_comment":"add default keys \r\n,s for saveSession. \r\n,l for loadSession when in clang_pro subdir","3":"add default keys \r\n,s for saveSession. \r\n,l for loadSession when in clang_pro subdir","package":"clang_pro.vim","4":"clang_pro.vim","src_id":"21989","5":"21989","creation_date":"1402038334","6":"1402038334"},{"0":"4928","vim_version":"7.0","1":"7.0","script_version":"3.2","2":"3.2","version_comment":"add default key map\r\nnmap ,d for find define\r\nnmap ,r for find reference\r\nnmap ,h for switch h\/c,cpp\r\n","3":"add default key map\r\nnmap ,d for find define\r\nnmap ,r for find reference\r\nnmap ,h for switch h\/c,cpp\r\n","package":"clang_pro.vim","4":"clang_pro.vim","src_id":"21982","5":"21982","creation_date":"1401780949","6":"1401780949"},{"0":"4928","vim_version":"7.0","1":"7.0","script_version":"3.1","2":"3.1","version_comment":"add cscope compatible,can use  command :cs find ...., add command :HCppSwitch   for goto h file and c\/cpp file","3":"add cscope compatible,can use  command :cs find ...., add command :HCppSwitch   for goto h file and c\/cpp file","package":"clang_pro.vim","4":"clang_pro.vim","src_id":"21961","5":"21961","creation_date":"1401340569","6":"1401340569"},{"0":"4928","vim_version":"7.0","1":"7.0","script_version":"3.0","2":"3.0","version_comment":"add auto java complete ","3":"add auto java complete ","package":"clang_pro.vim","4":"clang_pro.vim","src_id":"21947","5":"21947","creation_date":"1401154404","6":"1401154404"},{"0":"4928","vim_version":"7.0","1":"7.0","script_version":"2.1","2":"2.1","version_comment":"make start vim when using clang_pro build gtags pro quickly.","3":"make start vim when using clang_pro build gtags pro quickly.","package":"clang_pro.vim","4":"clang_pro.vim","src_id":"21939","5":"21939","creation_date":"1401066858","6":"1401066858"},{"0":"4928","vim_version":"7.0","1":"7.0","script_version":"2.0.1","2":"2.0.1","version_comment":"when has clang_pro file,make let g:clang_use_global = 1 as default,you can put line:\r\n let g:clang_use_global = 0 \r\nin your clang_pro file to close gnu global auto create gtags file for your project.  ","3":"when has clang_pro file,make let g:clang_use_global = 1 as default,you can put line:\r\n let g:clang_use_global = 0 \r\nin your clang_pro file to close gnu global auto create gtags file for your project.  ","package":"clang_pro.vim","4":"clang_pro.vim","src_id":"21918","5":"21918","creation_date":"1400747977","6":"1400747977"},{"0":"4928","vim_version":"7.0","1":"7.0","script_version":"2.0","2":"2.0","version_comment":"add function for session. When has clang_pro file, you can use :ClangSetSesion and :clangGetSession command save and load session at any c\/c++ file in project.","3":"add function for session. When has clang_pro file, you can use :ClangSetSesion and :clangGetSession command save and load session at any c\/c++ file in project.","package":"clang_pro.vim","4":"clang_pro.vim","src_id":"21863","5":"21863","creation_date":"1399191872","6":"1399191872"},{"0":"4928","vim_version":"7.0","1":"7.0","script_version":"1.2","2":"1.2","version_comment":"fix bug for when  no clang_pro file complete work err.","3":"fix bug for when  no clang_pro file complete work err.","package":"clang_pro.vim","4":"clang_pro.vim","src_id":"21824","5":"21824","creation_date":"1398411025","6":"1398411025"},{"0":"4928","vim_version":"7.0","1":"7.0","script_version":"1.1","2":"1.1","version_comment":"some bug fix, make -I relative path can work and windows make gtags project err fixed.  ","3":"some bug fix, make -I relative path can work and windows make gtags project err fixed.  ","package":"clang_pro.vim","4":"clang_pro.vim","src_id":"21812","5":"21812","creation_date":"1398242380","6":"1398242380"},{"0":"4928","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"clang_pro.vim","4":"clang_pro.vim","src_id":"21797","5":"21797","creation_date":"1398066824","6":"1398066824"}]},"4927":{"script_id":"4927","0":"4927","script_name":"Autosave","1":"Autosave","script_type":"utility","2":"utility","summary":"Auto save new empty buffer to backup folder.","3":"Auto save new empty buffer to backup folder.","description":"When Vim cashes, you can recover file contents from swap file, the auto backup files can save your life, too.\r\n\r\nBut if you accidentally confirmed to quit an unnamed buffer, there's no regret pill.\r\n\r\nSo this is the very simple plugin to automatically save empty buffer to backup path, you don't need to save new buffer mannually every time.","4":"When Vim cashes, you can recover file contents from swap file, the auto backup files can save your life, too.\r\n\r\nBut if you accidentally confirmed to quit an unnamed buffer, there's no regret pill.\r\n\r\nSo this is the very simple plugin to automatically save empty buffer to backup path, you don't need to save new buffer mannually every time.","install_details":"Copy to plugin directory.","5":"Copy to plugin directory.","first_name":"calon","6":"calon","last_name":"xu","7":"xu","releases":[{"0":"4927","vim_version":"7.0","1":"7.0","script_version":"2.0","2":"2.0","version_comment":"Rewrite in VimL.\r\n\r\nAdd option for auto save and manually quick save.\r\n\r\nBug fix(special buffer).","3":"Rewrite in VimL.\r\n\r\nAdd option for auto save and manually quick save.\r\n\r\nBug fix(special buffer).","package":"quicksave.vim","4":"quicksave.vim","src_id":"22515","5":"22515","creation_date":"1413009952","6":"1413009952"},{"0":"4927","vim_version":"7.0","1":"7.0","script_version":"1.2","2":"1.2","version_comment":"Bug fix","3":"Bug fix","package":"autosave.vim","4":"autosave.vim","src_id":"21807","5":"21807","creation_date":"1398171770","6":"1398171770"},{"0":"4927","vim_version":"7.0","1":"7.0","script_version":"1.1","2":"1.1","version_comment":"Bug fix.","3":"Bug fix.","package":"autosave.vim","4":"autosave.vim","src_id":"21796","5":"21796","creation_date":"1398055311","6":"1398055311"},{"0":"4927","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"autosave.vim","4":"autosave.vim","src_id":"21793","5":"21793","creation_date":"1397979740","6":"1397979740"}]},"4926":{"script_id":"4926","0":"4926","script_name":"vim-clang","1":"vim-clang","script_type":"utility","2":"utility","summary":"Yet another C\/C++ code completion plugin based on Clang","3":"Yet another C\/C++ code completion plugin based on Clang","description":"Installation\r\n-------------\r\n* Require executable `clang` installed.\r\n* Put the file `plugin\/clang.vim` into `~\/.vim\/plugin` is OK.\r\n* [pathogen.vim][4] `cd ~\/.vim\/bundle; git clone https:\/\/github.com\/justmao945\/vim-clang.git` is recommended.\r\n\r\n\r\nWhy\r\n---------------\r\nI was a user of clang\\_compelete and it's really a good job, but someday I found that\r\nI must write another plugin to overcome some _drawbacks_ of it...\r\n\r\nvim-clang VS [Rip-Rip\/clang_complete][1]\r\n---------------\r\n\r\n1. User options can be set for different file types in vim-clang.\r\n    \r\n        let g:clang_c_options = '-std=gnu11'\r\n        let g:clang_cpp_options = '-std=c++11 -stdlib=libc++'\r\n\r\n2. vim-clang is faster than clang_complete(not use libclang).\r\nvim-clang does not support libclang now, and I don't think it's a good idea to use cindex.py(python binding for clang) directly.\r\nIf you use clang_complete with libclang and open many C\/C++ source files, you'll find that VIM eats up **hundreds** of MB RAM...\r\n    * vim-clang caches output of clang and reuses if the completion point is not changed and without errors.\r\n    * vim-clang only runs clang once to get completions and diagnostics.\r\n\r\n3. vim-clang is more friendly than clang_complete.\r\n    * vim-clang uses the preview window to show prototypes for C\/C++ sources.\r\n      Generally, C++ source has many overload functions and most of completions are very complex,\r\n      which is not good to put this into OmniComplete popup menu.\r\n    * vim-clang uses a split window to show the caret diagnostics from clang.\r\n      clang_complete uses quickfix window to show diagnostics without caret, but that's not the best choice...\r\n      Because the caret diagnostics of clang including many useful infomation.\r\n\r\n4. vim-clang supports relative include path in .clang configuration file.\r\n    \r\n        proj\/\r\n        |-- .clang\r\n        |-- include\/\r\n            |-- main.h\r\n        |-- src\/\r\n            |-- main.c\r\n        |-- test\/\r\n            |-- main_test.c\r\n        \r\n        $ cat .clang\r\n        -I.\r\n\r\n5. Better PCH support. vim-clang will find stdafx.h.pch automatically.\r\n\r\nvim-clang VS [Valloric\/YouCompleteMe][5]\r\n--------------------\r\n[YouCompleteMe][5] is more powerful than vim-clang, that has a well designed client-server\r\narchitecture to deal the memory problem in clang_complete.\r\n\r\n\r\nAsynchronized mode [new]\r\n--------------------\r\n* Now vim-clang supports to call clang executable asynchronously that it won't block\r\nvim during the completion. This is very useful if your project is large and the machine\r\nis not very powerful to parse them in tens of milliseconds. In synchronized mode you'll\r\nfind that's too 'slow' to wait the completion...\r\n\r\n* This mode is implemented by starting another vim process to notify the finish of the\r\n   completion, so `+clientserver` option is required to compile the vim(generally added).\r\n\r\n* Please note that if you start vim from a terminal, and work as the non-GUI mode, such\r\n  as execute 'vim' to spawn the edit, default it does not act as a server. Instead, you\r\n  can start Gvim to work as a server or you must add '--servername XXX' to force to start\r\n  a vim server. More to see ':h clientserver'.\r\n\r\n* Job control is used to run clang when in neovim, which is really very nice! Thank you \r\n  [syswow][6].\r\n\r\n\r\n\r\nInclude file path completion ?\r\n--------------------\r\nPlease use with [neocomplete][7], they can work well together.\r\n```viml\r\n\" disable auto completion for vim-clang\r\nlet g:clang_auto = 0\r\n\" default 'longest' can not work with neocomplete\r\nlet g:clang_c_completeopt = 'menuone,preview'\r\nlet g:clang_cpp_completeopt = 'menuone,preview'\r\n\r\n\" use neocomplete\r\n\" input patterns\r\nif !exists('g:neocomplete#force_omni_input_patterns')\r\n  let g:neocomplete#force_omni_input_patterns = {}\r\nendif\r\n\r\n\" for c and c++\r\nlet g:neocomplete#force_omni_input_patterns.c =\r\n      \\ '[^.[:digit:] *\\t]\\%(\\.\\|->\\)\\w*'\r\nlet g:neocomplete#force_omni_input_patterns.cpp =\r\n      \\ '[^.[:digit:] *\\t]\\%(\\.\\|->\\)\\w*\\|\\h\\w*::\\w*'\r\n```\r\n\r\n\r\nOptions and Commands\r\n--------------------\r\n`:h clang.txt`\r\n\r\nOS requirement\r\n--------------------\r\nNow only tested on Linux (Ubuntu\/Debian) and Mac OSX\r\n\r\n\r\n[1]: https:\/\/github.com\/Rip-Rip\/clang_complete\r\n[2]: http:\/\/www.ishani.org\r\n[3]: http:\/\/www.ishani.org\/web\/articles\/code\/clang-win32\/\r\n[4]: https:\/\/github.com\/tpope\/vim-pathogen\r\n[5]: https:\/\/github.com\/Valloric\/YouCompleteMe\r\n[6]: https:\/\/github.com\/syswow\r\n[7]: https:\/\/github.com\/Shougo\/neocomplete","4":"Installation\r\n-------------\r\n* Require executable `clang` installed.\r\n* Put the file `plugin\/clang.vim` into `~\/.vim\/plugin` is OK.\r\n* [pathogen.vim][4] `cd ~\/.vim\/bundle; git clone https:\/\/github.com\/justmao945\/vim-clang.git` is recommended.\r\n\r\n\r\nWhy\r\n---------------\r\nI was a user of clang\\_compelete and it's really a good job, but someday I found that\r\nI must write another plugin to overcome some _drawbacks_ of it...\r\n\r\nvim-clang VS [Rip-Rip\/clang_complete][1]\r\n---------------\r\n\r\n1. User options can be set for different file types in vim-clang.\r\n    \r\n        let g:clang_c_options = '-std=gnu11'\r\n        let g:clang_cpp_options = '-std=c++11 -stdlib=libc++'\r\n\r\n2. vim-clang is faster than clang_complete(not use libclang).\r\nvim-clang does not support libclang now, and I don't think it's a good idea to use cindex.py(python binding for clang) directly.\r\nIf you use clang_complete with libclang and open many C\/C++ source files, you'll find that VIM eats up **hundreds** of MB RAM...\r\n    * vim-clang caches output of clang and reuses if the completion point is not changed and without errors.\r\n    * vim-clang only runs clang once to get completions and diagnostics.\r\n\r\n3. vim-clang is more friendly than clang_complete.\r\n    * vim-clang uses the preview window to show prototypes for C\/C++ sources.\r\n      Generally, C++ source has many overload functions and most of completions are very complex,\r\n      which is not good to put this into OmniComplete popup menu.\r\n    * vim-clang uses a split window to show the caret diagnostics from clang.\r\n      clang_complete uses quickfix window to show diagnostics without caret, but that's not the best choice...\r\n      Because the caret diagnostics of clang including many useful infomation.\r\n\r\n4. vim-clang supports relative include path in .clang configuration file.\r\n    \r\n        proj\/\r\n        |-- .clang\r\n        |-- include\/\r\n            |-- main.h\r\n        |-- src\/\r\n            |-- main.c\r\n        |-- test\/\r\n            |-- main_test.c\r\n        \r\n        $ cat .clang\r\n        -I.\r\n\r\n5. Better PCH support. vim-clang will find stdafx.h.pch automatically.\r\n\r\nvim-clang VS [Valloric\/YouCompleteMe][5]\r\n--------------------\r\n[YouCompleteMe][5] is more powerful than vim-clang, that has a well designed client-server\r\narchitecture to deal the memory problem in clang_complete.\r\n\r\n\r\nAsynchronized mode [new]\r\n--------------------\r\n* Now vim-clang supports to call clang executable asynchronously that it won't block\r\nvim during the completion. This is very useful if your project is large and the machine\r\nis not very powerful to parse them in tens of milliseconds. In synchronized mode you'll\r\nfind that's too 'slow' to wait the completion...\r\n\r\n* This mode is implemented by starting another vim process to notify the finish of the\r\n   completion, so `+clientserver` option is required to compile the vim(generally added).\r\n\r\n* Please note that if you start vim from a terminal, and work as the non-GUI mode, such\r\n  as execute 'vim' to spawn the edit, default it does not act as a server. Instead, you\r\n  can start Gvim to work as a server or you must add '--servername XXX' to force to start\r\n  a vim server. More to see ':h clientserver'.\r\n\r\n* Job control is used to run clang when in neovim, which is really very nice! Thank you \r\n  [syswow][6].\r\n\r\n\r\n\r\nInclude file path completion ?\r\n--------------------\r\nPlease use with [neocomplete][7], they can work well together.\r\n```viml\r\n\" disable auto completion for vim-clang\r\nlet g:clang_auto = 0\r\n\" default 'longest' can not work with neocomplete\r\nlet g:clang_c_completeopt = 'menuone,preview'\r\nlet g:clang_cpp_completeopt = 'menuone,preview'\r\n\r\n\" use neocomplete\r\n\" input patterns\r\nif !exists('g:neocomplete#force_omni_input_patterns')\r\n  let g:neocomplete#force_omni_input_patterns = {}\r\nendif\r\n\r\n\" for c and c++\r\nlet g:neocomplete#force_omni_input_patterns.c =\r\n      \\ '[^.[:digit:] *\\t]\\%(\\.\\|->\\)\\w*'\r\nlet g:neocomplete#force_omni_input_patterns.cpp =\r\n      \\ '[^.[:digit:] *\\t]\\%(\\.\\|->\\)\\w*\\|\\h\\w*::\\w*'\r\n```\r\n\r\n\r\nOptions and Commands\r\n--------------------\r\n`:h clang.txt`\r\n\r\nOS requirement\r\n--------------------\r\nNow only tested on Linux (Ubuntu\/Debian) and Mac OSX\r\n\r\n\r\n[1]: https:\/\/github.com\/Rip-Rip\/clang_complete\r\n[2]: http:\/\/www.ishani.org\r\n[3]: http:\/\/www.ishani.org\/web\/articles\/code\/clang-win32\/\r\n[4]: https:\/\/github.com\/tpope\/vim-pathogen\r\n[5]: https:\/\/github.com\/Valloric\/YouCompleteMe\r\n[6]: https:\/\/github.com\/syswow\r\n[7]: https:\/\/github.com\/Shougo\/neocomplete","install_details":"Require executable `clang` installed.\r\n\r\nPut the file plugin\/clang.vim into ~\/.vim\/plugin is OK.\r\n\r\npathogen.vim: `cd ~\/.vim\/bundle; git clone https:\/\/github.com\/justmao945\/vim-clang.git` is recommended.","5":"Require executable `clang` installed.\r\n\r\nPut the file plugin\/clang.vim into ~\/.vim\/plugin is OK.\r\n\r\npathogen.vim: `cd ~\/.vim\/bundle; git clone https:\/\/github.com\/justmao945\/vim-clang.git` is recommended.","first_name":"Jianjun","6":"Jianjun","last_name":"Mao","7":"Mao","releases":[{"0":"4926","vim_version":"7.4","1":"7.4","script_version":"0.5","2":"0.5","version_comment":"support CMake compile_commands.json [@c0r73x]\r\nsupport for MinGW in Windows [@maxint]\r\n","3":"support CMake compile_commands.json [@c0r73x]\r\nsupport for MinGW in Windows [@maxint]\r\n","package":"vim-clang-0.5.tar.gz","4":"vim-clang-0.5.tar.gz","src_id":"23579","5":"23579","creation_date":"1441637267","6":"1441637267"},{"0":"4926","vim_version":"7.4","1":"7.4","script_version":"0.4.1","2":"0.4.1","version_comment":"* Windows support [mattn]\r\n* bug fix","3":"* Windows support [mattn]\r\n* bug fix","package":"vim-clang-0.4.1.tar.gz","4":"vim-clang-0.4.1.tar.gz","src_id":"23331","5":"23331","creation_date":"1432986416","6":"1432986416"},{"0":"4926","vim_version":"7.4","1":"7.4","script_version":"0.4.0","2":"0.4.0","version_comment":"* improve job control for neovim [syswow]\r\n* support auto-close diagnostics window when leave\r\n* support syntax check when save source file\r\n* support neocomplete for header files completion\r\n* support clang-format\r\n","3":"* improve job control for neovim [syswow]\r\n* support auto-close diagnostics window when leave\r\n* support syntax check when save source file\r\n* support neocomplete for header files completion\r\n* support clang-format\r\n","package":"vim-clang-0.4.0.tar.gz","4":"vim-clang-0.4.0.tar.gz","src_id":"23268","5":"23268","creation_date":"1431153086","6":"1431153086"},{"0":"4926","vim_version":"7.4","1":"7.4","script_version":"0.3.0","2":"0.3.0","version_comment":"* support job control for neovim [@syswow]\r\n* no need to write source file to disk before completion [@mlen]\r\n* fix init plugin when create new file\r\n* bug fix","3":"* support job control for neovim [@syswow]\r\n* no need to write source file to disk before completion [@mlen]\r\n* fix init plugin when create new file\r\n* bug fix","package":"vim-clang-0.3.0.tar.gz","4":"vim-clang-0.3.0.tar.gz","src_id":"23239","5":"23239","creation_date":"1430398196","6":"1430398196"},{"0":"4926","vim_version":"7.4","1":"7.4","script_version":"0.2.8","2":"0.2.8","version_comment":"* bug fix on var set and restore\r\n* refactor DiagnosticsWindowClose","3":"* bug fix on var set and restore\r\n* refactor DiagnosticsWindowClose","package":"vim-clang-0.2.8.tar.gz","4":"vim-clang-0.2.8.tar.gz","src_id":"23053","5":"23053","creation_date":"1426691102","6":"1426691102"},{"0":"4926","vim_version":"7.3","1":"7.3","script_version":"0.2.7","2":"0.2.7","version_comment":"fix restore global vars when call ClangComplete","3":"fix restore global vars when call ClangComplete","package":"vim-clang-0.2.7.tar.gz","4":"vim-clang-0.2.7.tar.gz","src_id":"22918","5":"22918","creation_date":"1424080166","6":"1424080166"},{"0":"4926","vim_version":"7.3","1":"7.3","script_version":"0.2.6","2":"0.2.6","version_comment":"* import include path from &path  [thawk]\r\n* do not initialize plugin for non readable files [jreybert]\r\n* fix \"can't remove clang warning #16\" issue [jreybert]\r\n* add an option to load vim-clang only if .clang file is found [jreybert]","3":"* import include path from &path  [thawk]\r\n* do not initialize plugin for non readable files [jreybert]\r\n* fix \"can't remove clang warning #16\" issue [jreybert]\r\n* add an option to load vim-clang only if .clang file is found [jreybert]","package":"vim-clang-0.2.6.tar.gz","4":"vim-clang-0.2.6.tar.gz","src_id":"22680","5":"22680","creation_date":"1418092414","6":"1418092414"},{"0":"4926","vim_version":"7.0","1":"7.0","script_version":"0.2.5","2":"0.2.5","version_comment":"update doc","3":"update doc","package":"vim-clang-0.2.5.tar.gz","4":"vim-clang-0.2.5.tar.gz","src_id":"22391","5":"22391","creation_date":"1409486979","6":"1409486979"},{"0":"4926","vim_version":"7.0","1":"7.0","script_version":"0.2.4","2":"0.2.4","version_comment":"* fix ClangGenPCHFromFile\r\n* fix ClangCompleteInit","3":"* fix ClangGenPCHFromFile\r\n* fix ClangCompleteInit","package":"vim-clang.tar.gz","4":"vim-clang.tar.gz","src_id":"21819","5":"21819","creation_date":"1398357196","6":"1398357196"},{"0":"4926","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"vim-clang.tar.gz","4":"vim-clang.tar.gz","src_id":"21787","5":"21787","creation_date":"1397737766","6":"1397737766"}]},"4925":{"script_id":"4925","0":"4925","script_name":"snare","1":"snare","script_type":"utility","2":"utility","summary":"Snippets Again, with Regular Expressions","3":"Snippets Again, with Regular Expressions","description":"This plugin expands code snippets for which the trigger is a regular\r\nexpression; submatches can be reused in the expansion. Along with command\r\nsubstitution, regular expressions allow the user to define flexible snippets.\r\n\r\nA few examples:\r\n\r\n- In HTML, expand \"<mytag\" to\r\n    <mytag>$$<\/mytag>\r\n(with $$ marking the next position of the cursor), no matter what\r\n\"mytag\" is.\r\n\r\n- In Ruby, expand \"do\" to\r\n    do\r\n      $$\r\n    end\r\nand \"do a b c\" to\r\n    do |a, b, c|\r\n      $$\r\n    end\r\nwith a single pattern.\r\n\r\n- In JavaScript, expand \"var a b c\" to\r\n    var a = $$,\r\n        b = $$,\r\n        c = $$;\r\n\r\n- Etc.\r\n\r\nThe plugin follows a minimalist design, trying to be a simple yet powerful\r\ntool, using Vim's native resources (vim script, search patterns), and avoiding\r\nfancy features.","4":"This plugin expands code snippets for which the trigger is a regular\r\nexpression; submatches can be reused in the expansion. Along with command\r\nsubstitution, regular expressions allow the user to define flexible snippets.\r\n\r\nA few examples:\r\n\r\n- In HTML, expand \"<mytag\" to\r\n    <mytag>$$<\/mytag>\r\n(with $$ marking the next position of the cursor), no matter what\r\n\"mytag\" is.\r\n\r\n- In Ruby, expand \"do\" to\r\n    do\r\n      $$\r\n    end\r\nand \"do a b c\" to\r\n    do |a, b, c|\r\n      $$\r\n    end\r\nwith a single pattern.\r\n\r\n- In JavaScript, expand \"var a b c\" to\r\n    var a = $$,\r\n        b = $$,\r\n        c = $$;\r\n\r\n- Etc.\r\n\r\nThe plugin follows a minimalist design, trying to be a simple yet powerful\r\ntool, using Vim's native resources (vim script, search patterns), and avoiding\r\nfancy features.","install_details":"See the \"Quick start\" section of the help file.","5":"See the \"Quick start\" section of the help file.","first_name":"Paul","6":"Paul","last_name":"Isambert","7":"Isambert","releases":[{"0":"4925","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"snare.zip","4":"snare.zip","src_id":"21786","5":"21786","creation_date":"1397730846","6":"1397730846"}]},"4924":{"script_id":"4924","0":"4924","script_name":"FormatToWidth","1":"FormatToWidth","script_type":"utility","2":"utility","summary":"Apply the gq command to the selected \/ count width.","3":"Apply the gq command to the selected \/ count width.","description":"DESCRIPTION\r\nVim can reformat lines with the gq command, according to 'textwidth' and\r\n'formatoptions', which is very handy. But sometimes you want to format to a\r\ndifferent width, or just a single block in a vertical column layout. That\r\nrequires a temporary :setlocal tw=N, and copying the block elsewhere to\r\nreformat it, which is cumbersome.\r\n\r\nThis plugin provides a visual mode <Leader>gq command that reformats only the\r\nselection; how exactly depends on the selection mode. The new width is\r\ndetermined by a passed [count], or the width of the selection's first line.\r\nWith this, you can easily reformat lines to a certain width, or a blockwise\r\nselection while leaving the text to the left and right alone.\r\n\r\nSOURCE\r\nInspired by\r\n    http:\/\/stackoverflow.com\/questions\/22922274\/how-does-one-rewrap-text-in-a-column-in-vim\r\n\r\nUSAGE\r\n{Visual}<Leader>gq      Linewise selection: Format the selected text to the\r\n                        width of the first selected line \/ to [count]\r\n                        characters.\r\n                        Blockwise selection: Format the selected text to the\r\n                        width of the block \/ to [count] characters, and\r\n                        change the selected text in-place. If the reformatted\r\n                        text consists of less lines, the remainder of the\r\n                        block will consist of spaces. If it's more lines,\r\n                        these will be inserted as additional lines,\r\n                        left-aligned with spaces to the start column of the\r\n                        block.\r\n                        Characterwise selection: Format the selected text to\r\n                        the width of the first selected line \/ to [count]\r\n                        characters, and align all following lines to the start\r\n                        column of the selection.\r\n\r\nEXAMPLE LINEWISE\r\nTo re-wrap the following text:\r\n    The quick brown fox jumps over the lazy dog.\r\nto a 'textwidth' of 20, you select the entire line, then reformat to the\r\nspecified width: V20<Leader>gq\r\n    The quick brown fox\r\n    jumps over the lazy\r\n    dog.\r\n\r\nEXAMPLE BLOCKWISE\r\nYou have a multi-column layout like this:\r\n    Intro | The quick brown fox       -\r\n          | jumps over the lazy dog.  - (he's very lazy)\r\nLet's reformat the middle column to use all the available space.\r\nYou select the entire column as a block, e.g. with f|l<C-V>t-j, then reformat\r\nthe selection with <Leader>gq:\r\n    Intro | The quick brown fox jumps -\r\n          | over the lazy dog.        - (he's very lazy)\r\nOkay, but now you want it wider: gv40<Leader>gq reformats to a 40-char column:\r\n    Intro | The quick brown fox jumps over the lazy -\r\n          | dog.                                    - (he's very lazy)","4":"DESCRIPTION\r\nVim can reformat lines with the gq command, according to 'textwidth' and\r\n'formatoptions', which is very handy. But sometimes you want to format to a\r\ndifferent width, or just a single block in a vertical column layout. That\r\nrequires a temporary :setlocal tw=N, and copying the block elsewhere to\r\nreformat it, which is cumbersome.\r\n\r\nThis plugin provides a visual mode <Leader>gq command that reformats only the\r\nselection; how exactly depends on the selection mode. The new width is\r\ndetermined by a passed [count], or the width of the selection's first line.\r\nWith this, you can easily reformat lines to a certain width, or a blockwise\r\nselection while leaving the text to the left and right alone.\r\n\r\nSOURCE\r\nInspired by\r\n    http:\/\/stackoverflow.com\/questions\/22922274\/how-does-one-rewrap-text-in-a-column-in-vim\r\n\r\nUSAGE\r\n{Visual}<Leader>gq      Linewise selection: Format the selected text to the\r\n                        width of the first selected line \/ to [count]\r\n                        characters.\r\n                        Blockwise selection: Format the selected text to the\r\n                        width of the block \/ to [count] characters, and\r\n                        change the selected text in-place. If the reformatted\r\n                        text consists of less lines, the remainder of the\r\n                        block will consist of spaces. If it's more lines,\r\n                        these will be inserted as additional lines,\r\n                        left-aligned with spaces to the start column of the\r\n                        block.\r\n                        Characterwise selection: Format the selected text to\r\n                        the width of the first selected line \/ to [count]\r\n                        characters, and align all following lines to the start\r\n                        column of the selection.\r\n\r\nEXAMPLE LINEWISE\r\nTo re-wrap the following text:\r\n    The quick brown fox jumps over the lazy dog.\r\nto a 'textwidth' of 20, you select the entire line, then reformat to the\r\nspecified width: V20<Leader>gq\r\n    The quick brown fox\r\n    jumps over the lazy\r\n    dog.\r\n\r\nEXAMPLE BLOCKWISE\r\nYou have a multi-column layout like this:\r\n    Intro | The quick brown fox       -\r\n          | jumps over the lazy dog.  - (he's very lazy)\r\nLet's reformat the middle column to use all the available space.\r\nYou select the entire column as a block, e.g. with f|l<C-V>t-j, then reformat\r\nthe selection with <Leader>gq:\r\n    Intro | The quick brown fox jumps -\r\n          | over the lazy dog.        - (he's very lazy)\r\nOkay, but now you want it wider: gv40<Leader>gq reformats to a 40-char column:\r\n    Intro | The quick brown fox jumps over the lazy -\r\n          | dog.                                    - (he's very lazy)","install_details":"INSTALLATION\r\nThis script is packaged as a vimball. If you have the \"gunzip\" decompressor\r\nin your PATH, simply edit the *.vmb.gz package in Vim; otherwise, decompress\r\nthe archive first, e.g. using WinZip. Inside Vim, install by sourcing the\r\nvimball or via the :UseVimball command.\r\n    vim FormatToWidth*.vmb.gz\r\n    :so %\r\nTo uninstall, use the :RmVimball command.\r\n\r\nDEPENDENCIES\r\n- Requires Vim 7.0 or higher.\r\n- Requires the ingo-library.vim plugin (vimscript #4433), version 1.018 or\r\n  higher.\r\n\r\nCONFIGURATION\r\nFor a permanent configuration, put the following commands into your vimrc:\r\n\r\nIf you want to use a different mapping, map your keys to the\r\n<Plug>(FormatToWidth) mapping target _before_ sourcing the script\r\n(e.g. in your vimrc):\r\n    xmap <Leader>gq <Plug>(FormatToWidth)","5":"INSTALLATION\r\nThis script is packaged as a vimball. If you have the \"gunzip\" decompressor\r\nin your PATH, simply edit the *.vmb.gz package in Vim; otherwise, decompress\r\nthe archive first, e.g. using WinZip. Inside Vim, install by sourcing the\r\nvimball or via the :UseVimball command.\r\n    vim FormatToWidth*.vmb.gz\r\n    :so %\r\nTo uninstall, use the :RmVimball command.\r\n\r\nDEPENDENCIES\r\n- Requires Vim 7.0 or higher.\r\n- Requires the ingo-library.vim plugin (vimscript #4433), version 1.018 or\r\n  higher.\r\n\r\nCONFIGURATION\r\nFor a permanent configuration, put the following commands into your vimrc:\r\n\r\nIf you want to use a different mapping, map your keys to the\r\n<Plug>(FormatToWidth) mapping target _before_ sourcing the script\r\n(e.g. in your vimrc):\r\n    xmap <Leader>gq <Plug>(FormatToWidth)","first_name":"Ingo","6":"Ingo","last_name":"Karkat","7":"Karkat","releases":[{"0":"4924","vim_version":"7.0","1":"7.0","script_version":"1.00","2":"1.00","version_comment":"Initial upload","3":"Initial upload","package":"FormatToWidth-1.00.vmb.gz","4":"FormatToWidth-1.00.vmb.gz","src_id":"21773","5":"21773","creation_date":"1397487169","6":"1397487169"}]},"4923":{"script_id":"4923","0":"4923","script_name":"autoswap.vim","1":"autoswap.vim","script_type":"utility","2":"utility","summary":"Switch to open editor window instead of asking what to do with swapfile","3":"Switch to open editor window instead of asking what to do with swapfile","description":"Dealing with swap files is annoying. Most of the time you have to deal with a swap file because you either have the same file open in another window or it is a swap file left there by a previous crash.\r\n\r\nThis plugin does for you what you would do in these cases:\r\n\r\n1. Is file already open in another Vim session in some other window?\r\n2. If so, swap to the window where we are editing that file.\r\n3. Otherwise, if swapfile is older than file itself, just get rid of it.\r\n4. Otherwise, open file read-only so we can have a look at it and may save it.\r\n\r\nHomepage: http:\/\/svario.it\/vim-autoswap\r\nReport issues: http:\/\/svario.it\/vim-autoswap\/issues\r\n\r\n--\r\n\r\nDamian Conway presented this plugin at OSCON 2013 in his talk \"More instantly better Vim\" (http:\/\/programming.oreilly.com\/2013\/10\/more-instantly-better-vim.html).\r\n\r\nThis version has been modified to work also on Linux systems. Both Vim and GVim are supported.\r\n\r\nThe original version of this plugin (only for Mac OX) is available at http:\/\/is.gd\/IBV2013, together with other plugins presented in the same talk. \r\n\r\n","4":"Dealing with swap files is annoying. Most of the time you have to deal with a swap file because you either have the same file open in another window or it is a swap file left there by a previous crash.\r\n\r\nThis plugin does for you what you would do in these cases:\r\n\r\n1. Is file already open in another Vim session in some other window?\r\n2. If so, swap to the window where we are editing that file.\r\n3. Otherwise, if swapfile is older than file itself, just get rid of it.\r\n4. Otherwise, open file read-only so we can have a look at it and may save it.\r\n\r\nHomepage: http:\/\/svario.it\/vim-autoswap\r\nReport issues: http:\/\/svario.it\/vim-autoswap\/issues\r\n\r\n--\r\n\r\nDamian Conway presented this plugin at OSCON 2013 in his talk \"More instantly better Vim\" (http:\/\/programming.oreilly.com\/2013\/10\/more-instantly-better-vim.html).\r\n\r\nThis version has been modified to work also on Linux systems. Both Vim and GVim are supported.\r\n\r\nThe original version of this plugin (only for Mac OX) is available at http:\/\/is.gd\/IBV2013, together with other plugins presented in the same talk. \r\n\r\n","install_details":"Copy the `autoswap.vim` file in your `~\/.vim\/plugin` directory.\r\n\r\nOr use Pathogen and just clone the git repository:\r\n\r\n    $ cd ~\/.vim\/bundle\r\n    $ git clone https:\/\/github.com\/gioele\/vim-autoswap.git\r\n\r\nLinux users: you must install `wmctrl` to be able to automatically switch to the Vim window with the open file. `wmctrl` is already packaged for most distributions.","5":"Copy the `autoswap.vim` file in your `~\/.vim\/plugin` directory.\r\n\r\nOr use Pathogen and just clone the git repository:\r\n\r\n    $ cd ~\/.vim\/bundle\r\n    $ git clone https:\/\/github.com\/gioele\/vim-autoswap.git\r\n\r\nLinux users: you must install `wmctrl` to be able to automatically switch to the Vim window with the open file. `wmctrl` is already packaged for most distributions.","first_name":"Gioele","6":"Gioele","last_name":"Barabucci","7":"Barabucci","releases":[{"0":"4923","vim_version":"7.0","1":"7.0","script_version":"0.3","2":"0.3","version_comment":"Fixed the display of delayed messages.","3":"Fixed the display of delayed messages.","package":"vim-autoswap-0.3.tar.gz","4":"vim-autoswap-0.3.tar.gz","src_id":"21832","5":"21832","creation_date":"1398445798","6":"1398445798"},{"0":"4923","vim_version":"7.0","1":"7.0","script_version":"0.2","2":"0.2","version_comment":"Removed debug logging","3":"Removed debug logging","package":"vim-autoswap-0.2.tar.gz","4":"vim-autoswap-0.2.tar.gz","src_id":"21770","5":"21770","creation_date":"1397484684","6":"1397484684"},{"0":"4923","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"vim-autoswap-0.1.tar.gz","4":"vim-autoswap-0.1.tar.gz","src_id":"21769","5":"21769","creation_date":"1397474786","6":"1397474786"}]},"4922":{"script_id":"4922","0":"4922","script_name":"FindOccurrence","1":"FindOccurrence","script_type":"utility","2":"utility","summary":"Extended mappings for :isearch, :ilist and :ijump.","3":"Extended mappings for :isearch, :ilist and :ijump.","description":"DESCRIPTION\r\nThis plugin adds the following features to the default Vim mappings for\r\n:isearch, :ilist and :ijump:\r\n- ]I et al. not only list the occurrences, but ask for the occurrence number\r\n  to jump to.\r\n- ]I et al. also work in visual mode, searching for the selection instead of\r\n  the word under cursor.\r\n- New ]n ]N ]<C-N> <C-W>n <C-W><C-N> mappings that operate on the\r\n  last search pattern.\r\n- New ]\/ <C-W>\/ mappings that query and then operate on a pattern.\r\n\r\nSOURCE\r\nBased on the Vim Tip \"Search visually\":\r\n    http:\/\/vim.wikia.com\/wiki\/Search_visually\r\n\r\nUSAGE\r\nList occurrences of \\<word\\> under cursor \/ word under cursor (g[I) \/ visual\r\nselection:\r\nWith any [count], also includes 'comment'ed lines.\r\n[count][I               List all occurrences in the file. (Like :ilist)\r\n[count]]I               List occurrences from the cursor position to end of\r\n                        file.\r\n[count][CTRL-I          Jump to the [count]'th occurrence in the file. (Like\r\n                        :ijump)\r\n[count]]CTRL-I          Jump to the [count]'th occurrence starting from the\r\n                        cursor position.\r\n\r\nList occurrences of last search pattern quote\/:\r\nWith any [count], also includes 'comment'ed lines.\r\n[count][n               List [count]'th occurrence in the file. (Like\r\n                        :isearch)\r\n[count]]n               List [count]'th occurrence from the cursor position.\r\n[count][N               List all occurrences in the file. (Like :ilist)\r\n[count]]N               List occurrences from the cursor position to end of\r\n                        file.\r\n[count][CTRL-N          Jump to the [count]'th occurrence in the file. (Like\r\n                        :ijump)\r\n[count]]CTRL-N          Jump to the [count]'th occurrence starting from the\r\n                        cursor position.\r\n\r\nList occurrences of queried pattern:\r\nWith any [count], also includes 'comment'ed lines.\r\n[count][\/               Without [count]: Query, then list all occurrences in\r\n                        the file (like :ilist).\r\n                        With [count]: Query, then jump to [count]'th\r\n                        occurrence; if it doesn't exist, list all occurrences.\r\n[count]]\/               Without [count]: Query, then list occurrences from the\r\n                        cursor position to end of file.\r\n                        With [count]: Query, then jump to [count]'th\r\n                        occurrence from the cursor position; if it doesn't\r\n                        exist, list occurrences from the cursor position to\r\n                        end of file.\r\n                        These eclipse [\/ and ]\/ motions, but you can still use\r\n                        [* and ]*.\r\n[count]CTRL-W_\/         Query, then jump to the [count]'th occurrence in a\r\n                        split window.\r\n\r\n[count][?               Without [count]: List all occurrences of the\r\n                        previously queried pattern in the file (like\r\n                        :ilist).\r\n                        With [count]: Jump to [count]'th previously queried\r\n                        occurrence; if it doesn't exist, list all occurrences.\r\n[count]]?               Without [count]: List occurrences of the previously\r\n                        queried pattern from the cursor position to end of\r\n                        file.\r\n                        With [count]: Jump to [count]'th previously queried\r\n                        occurrence from the cursor position; if it doesn't\r\n                        exist, list occurrences from the cursor position to\r\n                        end of file.\r\n[count]CTRL-W_?         Jump to the [count]'th previously queried occurrence\r\n                        in a split window.\r\n\r\nNOTES\r\n- The [ and <C-W> mappings start at the beginning of the file, the ] mappings\r\n  at the line after the cursor. Both are directed forward, so it's easy to\r\n  jump to the next match, but to go to a previous match, you have to find out\r\n  about the match number and use that.\r\n- Without a [count], commented lines are ignored. If you want to show the list\r\n  that includes commented lines, use a high count (e.g. 999) that is unlikely\r\n  to produce a direct match.\r\n- x just echoes the occurrence, X prints a list of the occurrences and asks\r\n  for the occurrence number to jump to, <C-X> directly jumps to the\r\n  occurrence, <C-W>x and <C-W><C-X> split the window and jump to the\r\n  occurrence.\r\n- i I <Tab> <C-W>i <C-W><Tab> for word under cursor.\r\n- d D <C-D> <C-W>d <C-W><C-D> for macro definition under cursor.\r\n- n N <C-N> <C-W>n <C-W><C-N> for last search pattern.\r\n- \/ <C-W>\/                    for queried pattern.\r\n\r\nUSE CASES\r\n- List all occurrences excluding \/ including comments:\r\n  [X \/ 999[X\r\n- Move through all matches excluding \/ including comments:\r\n  [CTRL-X, ]CTRL-X, ]CTRL-X, ... \/ 1[CTRL-X, 1]CTRL-X, 1]CTRL-X, ...\r\n- Move through every n'th match excluding \/ including comments:\r\n  [CTRL-X, ]Xn, ]Xn, ... \/ 1[CTRL-X, n]CTRL-X, n]CTRL-X, ...","4":"DESCRIPTION\r\nThis plugin adds the following features to the default Vim mappings for\r\n:isearch, :ilist and :ijump:\r\n- ]I et al. not only list the occurrences, but ask for the occurrence number\r\n  to jump to.\r\n- ]I et al. also work in visual mode, searching for the selection instead of\r\n  the word under cursor.\r\n- New ]n ]N ]<C-N> <C-W>n <C-W><C-N> mappings that operate on the\r\n  last search pattern.\r\n- New ]\/ <C-W>\/ mappings that query and then operate on a pattern.\r\n\r\nSOURCE\r\nBased on the Vim Tip \"Search visually\":\r\n    http:\/\/vim.wikia.com\/wiki\/Search_visually\r\n\r\nUSAGE\r\nList occurrences of \\<word\\> under cursor \/ word under cursor (g[I) \/ visual\r\nselection:\r\nWith any [count], also includes 'comment'ed lines.\r\n[count][I               List all occurrences in the file. (Like :ilist)\r\n[count]]I               List occurrences from the cursor position to end of\r\n                        file.\r\n[count][CTRL-I          Jump to the [count]'th occurrence in the file. (Like\r\n                        :ijump)\r\n[count]]CTRL-I          Jump to the [count]'th occurrence starting from the\r\n                        cursor position.\r\n\r\nList occurrences of last search pattern quote\/:\r\nWith any [count], also includes 'comment'ed lines.\r\n[count][n               List [count]'th occurrence in the file. (Like\r\n                        :isearch)\r\n[count]]n               List [count]'th occurrence from the cursor position.\r\n[count][N               List all occurrences in the file. (Like :ilist)\r\n[count]]N               List occurrences from the cursor position to end of\r\n                        file.\r\n[count][CTRL-N          Jump to the [count]'th occurrence in the file. (Like\r\n                        :ijump)\r\n[count]]CTRL-N          Jump to the [count]'th occurrence starting from the\r\n                        cursor position.\r\n\r\nList occurrences of queried pattern:\r\nWith any [count], also includes 'comment'ed lines.\r\n[count][\/               Without [count]: Query, then list all occurrences in\r\n                        the file (like :ilist).\r\n                        With [count]: Query, then jump to [count]'th\r\n                        occurrence; if it doesn't exist, list all occurrences.\r\n[count]]\/               Without [count]: Query, then list occurrences from the\r\n                        cursor position to end of file.\r\n                        With [count]: Query, then jump to [count]'th\r\n                        occurrence from the cursor position; if it doesn't\r\n                        exist, list occurrences from the cursor position to\r\n                        end of file.\r\n                        These eclipse [\/ and ]\/ motions, but you can still use\r\n                        [* and ]*.\r\n[count]CTRL-W_\/         Query, then jump to the [count]'th occurrence in a\r\n                        split window.\r\n\r\n[count][?               Without [count]: List all occurrences of the\r\n                        previously queried pattern in the file (like\r\n                        :ilist).\r\n                        With [count]: Jump to [count]'th previously queried\r\n                        occurrence; if it doesn't exist, list all occurrences.\r\n[count]]?               Without [count]: List occurrences of the previously\r\n                        queried pattern from the cursor position to end of\r\n                        file.\r\n                        With [count]: Jump to [count]'th previously queried\r\n                        occurrence from the cursor position; if it doesn't\r\n                        exist, list occurrences from the cursor position to\r\n                        end of file.\r\n[count]CTRL-W_?         Jump to the [count]'th previously queried occurrence\r\n                        in a split window.\r\n\r\nNOTES\r\n- The [ and <C-W> mappings start at the beginning of the file, the ] mappings\r\n  at the line after the cursor. Both are directed forward, so it's easy to\r\n  jump to the next match, but to go to a previous match, you have to find out\r\n  about the match number and use that.\r\n- Without a [count], commented lines are ignored. If you want to show the list\r\n  that includes commented lines, use a high count (e.g. 999) that is unlikely\r\n  to produce a direct match.\r\n- x just echoes the occurrence, X prints a list of the occurrences and asks\r\n  for the occurrence number to jump to, <C-X> directly jumps to the\r\n  occurrence, <C-W>x and <C-W><C-X> split the window and jump to the\r\n  occurrence.\r\n- i I <Tab> <C-W>i <C-W><Tab> for word under cursor.\r\n- d D <C-D> <C-W>d <C-W><C-D> for macro definition under cursor.\r\n- n N <C-N> <C-W>n <C-W><C-N> for last search pattern.\r\n- \/ <C-W>\/                    for queried pattern.\r\n\r\nUSE CASES\r\n- List all occurrences excluding \/ including comments:\r\n  [X \/ 999[X\r\n- Move through all matches excluding \/ including comments:\r\n  [CTRL-X, ]CTRL-X, ]CTRL-X, ... \/ 1[CTRL-X, 1]CTRL-X, 1]CTRL-X, ...\r\n- Move through every n'th match excluding \/ including comments:\r\n  [CTRL-X, ]Xn, ]Xn, ... \/ 1[CTRL-X, n]CTRL-X, n]CTRL-X, ...","install_details":"INSTALLATION\r\nThis script is packaged as a vimball. If you have the \"gunzip\" decompressor\r\nin your PATH, simply edit the *.vmb.gz package in Vim; otherwise, decompress\r\nthe archive first, e.g. using WinZip. Inside Vim, install by sourcing the\r\nvimball or via the :UseVimball command.\r\n    vim FindOccurrence*.vmb.gz\r\n    :so %\r\nTo uninstall, use the :RmVimball command.\r\n\r\nDEPENDENCIES\r\n- Requires Vim 7.0 or higher.\r\n- Requires the ingo-library.vim plugin (vimscript #4433), version 1.007 or\r\n  higher.","5":"INSTALLATION\r\nThis script is packaged as a vimball. If you have the \"gunzip\" decompressor\r\nin your PATH, simply edit the *.vmb.gz package in Vim; otherwise, decompress\r\nthe archive first, e.g. using WinZip. Inside Vim, install by sourcing the\r\nvimball or via the :UseVimball command.\r\n    vim FindOccurrence*.vmb.gz\r\n    :so %\r\nTo uninstall, use the :RmVimball command.\r\n\r\nDEPENDENCIES\r\n- Requires Vim 7.0 or higher.\r\n- Requires the ingo-library.vim plugin (vimscript #4433), version 1.007 or\r\n  higher.","first_name":"Ingo","6":"Ingo","last_name":"Karkat","7":"Karkat","releases":[{"0":"4922","vim_version":"7.0","1":"7.0","script_version":"1.01","2":"1.01","version_comment":"- ENH: Add g[I and g[<Tab> mappings that search for the word (not the \\<word\\>) under the cursor, like * and g*.","3":"- ENH: Add g[I and g[<Tab> mappings that search for the word (not the \\<word\\>) under the cursor, like * and g*.","package":"FindOccurrence-1.01.vmb.gz","4":"FindOccurrence-1.01.vmb.gz","src_id":"21927","5":"21927","creation_date":"1400842586","6":"1400842586"},{"0":"4922","vim_version":"7.0","1":"7.0","script_version":"1.00","2":"1.00","version_comment":"Initial upload","3":"Initial upload","package":"FindOccurrence-1.00.vmb.gz","4":"FindOccurrence-1.00.vmb.gz","src_id":"21758","5":"21758","creation_date":"1397117490","6":"1397117490"}]},"4921":{"script_id":"4921","0":"4921","script_name":"Simple TODO","1":"Simple TODO","script_type":"syntax","2":"syntax","summary":"A simple plugin that can use VIM as TODO","3":"A simple plugin that can use VIM as TODO","description":"Once installed, create a todo.txt file, then you can create todo list\r\n\r\n[ ] this is a todo\r\n[.] this is a low priority todo\r\n[x] this is a finished todo\r\n\r\n!this is a highlight line\r\nTODO: this is a pink todo\r\n@@: this is pink todo","4":"Once installed, create a todo.txt file, then you can create todo list\r\n\r\n[ ] this is a todo\r\n[.] this is a low priority todo\r\n[x] this is a finished todo\r\n\r\n!this is a highlight line\r\nTODO: this is a pink todo\r\n@@: this is pink todo","install_details":"put under your .vim folder.","5":"put under your .vim folder.","first_name":"Frank","6":"Frank","last_name":"Ren","7":"Ren","releases":[{"0":"4921","vim_version":"7.0","1":"7.0","script_version":"0.02","2":"0.02","version_comment":"Updated to support terminal vim better.\r\n\r\nThanks Yu-Jie Lin(https:\/\/github.com\/livibetter) for making this change.","3":"Updated to support terminal vim better.\r\n\r\nThanks Yu-Jie Lin(https:\/\/github.com\/livibetter) for making this change.","package":"texttodo.zip","4":"texttodo.zip","src_id":"21761","5":"21761","creation_date":"1397284356","6":"1397284356"},{"0":"4921","vim_version":"7.0","1":"7.0","script_version":"0.01","2":"0.01","version_comment":"Initial upload","3":"Initial upload","package":"todotxt.tar.gz","4":"todotxt.tar.gz","src_id":"21757","5":"21757","creation_date":"1397093186","6":"1397093186"}]},"4920":{"script_id":"4920","0":"4920","script_name":"Spiffy Foldtext","1":"Spiffy Foldtext","script_type":"utility","2":"utility","summary":"easy foldtext via a format string, with added features","3":"easy foldtext via a format string, with added features","description":"A customizable foldtext function that properly takes into account the actual\r\nwidth of the displayable area of your windows. You are thus able to\r\nright-justify a portion of it, usually meta-data like line count and fold\r\nlevel.\r\n\r\nAt the center of the plugin is a special format string. By customizing its\r\nvalue, you can create your own custom foldtext in a single line in your vimrc.\r\n\r\nThis plugin is meant to be drop-in-able without the need to make any\r\nadjustments--with nice default settings that increase the clarity of your\r\npartially folded windows. There are no functions mapped or in need of mapping.\r\n\r\nThe official repository for this plugin is located on bitbucket, at\r\nhttps:\/\/bitbucket.org\/atimholt\/spiffy_foldtext , but a skeleton git repository\r\n(containing just numbered releases) is kept on github, at\r\nhttps:\/\/github.com\/atimholt\/spiffy_foldtext for the sake of plugin managers\r\nthat don't support Mercurial, like Vundle.\r\n\r\n                               The Format String\r\n\r\nThe format string is customizable by setting the \"SpiffyFoldtext_format\"\r\nvariable, prepended with \"g:\" for global scope, \"b:\" for buffer-local scope,\r\nor \"w:\" for window-local scope--each scope overriding those listed before it.\r\nThe format string contains control triggers and literal text describing how\r\nyour folded lines will render. For example, here's the default (more or less):\r\n\r\n        if has('multi_byte')\r\n            let g:SpiffyFoldtext_format = \"%c{═}  %<%f{═}╡ %4n lines ╞═%l{╤═}\"\r\n        else\r\n            let g:SpiffyFoldtext_format = \"%c{=}  %<%f{=}| %4n lines |=%l{\/=}\"\r\n        endif\r\n\r\nOr, more simply (I'll take the ascii-only version for the sake of\r\nexplanation):\r\n\r\n        let g:SpiffyFoldtext_format = \"%c{=}  %<%f{=}| %4n lines |=%l{\/=}\"\r\n\r\nThe plugin parses this string upon first run, then 'compiles' it to your\r\nfoldtext each time vim needs to determine what to display on a line that\r\nrepresents a folded region. In a display area 70 characters wide, the above\r\nexample would make this sample text:\r\n\r\n    Some text with a foldmarker {{{                                       \r\n        Some indented text        with a wide whitespace region {{{       \r\n                                                                          \r\n        }}}                                                               \r\n    }}}                                                                   \r\n\r\nfold to look like this:\r\n\r\n    Some text with a foldmarker {{{                                       \r\n    === Some indented text ====== with a wide whitespace |    3 lines |=\/=\r\n    }}}                                                                   \r\n\r\nor this:\r\n\r\n    Some text with a foldmarker {{{  ======================|    5 lines |=\r\n\r\n\r\nHere's a sampling of what some of the example translates to. See the plugin's\r\nhelp (:help spiffy_foldtext) for more information on the rest:\r\n\r\n   \"%c{=}\"\r\n\r\nThis trigger places the text of the fold region's first line into your\r\nfoldtext. As given here, its indentation and wider whitespace regions will be\r\nfilled with the '=' character. See :help spiffy_foldtext-%c.\r\n\r\n   \"  \"\r\n\r\nThis inserts two literal spaces.\r\n\r\n   \"%<\"\r\n\r\nThis represents the split between what will be left-aligned in your foldtext\r\nand what will be right aligned. The leftward angle bracket is meant as a\r\nmnemonic to indicate that, should all the contents of the foldtext be too wide\r\nfor the display area, the content to the right of this trigger will overwrite\r\npart of the content to the left. See :help spiffy_foldtext-%<.\r\n\r\n   \"%f{=}\"\r\n\r\nIf the content of the foldtext doesn't fill up the entire display region, the\r\nfoldtext will be filled with '='s at this point, to the amount needed to\r\nright-align the right-align section. See :help spiffy_foldtext-%f{}.\r\n\r\n  etc.\r\n","4":"A customizable foldtext function that properly takes into account the actual\r\nwidth of the displayable area of your windows. You are thus able to\r\nright-justify a portion of it, usually meta-data like line count and fold\r\nlevel.\r\n\r\nAt the center of the plugin is a special format string. By customizing its\r\nvalue, you can create your own custom foldtext in a single line in your vimrc.\r\n\r\nThis plugin is meant to be drop-in-able without the need to make any\r\nadjustments--with nice default settings that increase the clarity of your\r\npartially folded windows. There are no functions mapped or in need of mapping.\r\n\r\nThe official repository for this plugin is located on bitbucket, at\r\nhttps:\/\/bitbucket.org\/atimholt\/spiffy_foldtext , but a skeleton git repository\r\n(containing just numbered releases) is kept on github, at\r\nhttps:\/\/github.com\/atimholt\/spiffy_foldtext for the sake of plugin managers\r\nthat don't support Mercurial, like Vundle.\r\n\r\n                               The Format String\r\n\r\nThe format string is customizable by setting the \"SpiffyFoldtext_format\"\r\nvariable, prepended with \"g:\" for global scope, \"b:\" for buffer-local scope,\r\nor \"w:\" for window-local scope--each scope overriding those listed before it.\r\nThe format string contains control triggers and literal text describing how\r\nyour folded lines will render. For example, here's the default (more or less):\r\n\r\n        if has('multi_byte')\r\n            let g:SpiffyFoldtext_format = \"%c{═}  %<%f{═}╡ %4n lines ╞═%l{╤═}\"\r\n        else\r\n            let g:SpiffyFoldtext_format = \"%c{=}  %<%f{=}| %4n lines |=%l{\/=}\"\r\n        endif\r\n\r\nOr, more simply (I'll take the ascii-only version for the sake of\r\nexplanation):\r\n\r\n        let g:SpiffyFoldtext_format = \"%c{=}  %<%f{=}| %4n lines |=%l{\/=}\"\r\n\r\nThe plugin parses this string upon first run, then 'compiles' it to your\r\nfoldtext each time vim needs to determine what to display on a line that\r\nrepresents a folded region. In a display area 70 characters wide, the above\r\nexample would make this sample text:\r\n\r\n    Some text with a foldmarker {{{                                       \r\n        Some indented text        with a wide whitespace region {{{       \r\n                                                                          \r\n        }}}                                                               \r\n    }}}                                                                   \r\n\r\nfold to look like this:\r\n\r\n    Some text with a foldmarker {{{                                       \r\n    === Some indented text ====== with a wide whitespace |    3 lines |=\/=\r\n    }}}                                                                   \r\n\r\nor this:\r\n\r\n    Some text with a foldmarker {{{  ======================|    5 lines |=\r\n\r\n\r\nHere's a sampling of what some of the example translates to. See the plugin's\r\nhelp (:help spiffy_foldtext) for more information on the rest:\r\n\r\n   \"%c{=}\"\r\n\r\nThis trigger places the text of the fold region's first line into your\r\nfoldtext. As given here, its indentation and wider whitespace regions will be\r\nfilled with the '=' character. See :help spiffy_foldtext-%c.\r\n\r\n   \"  \"\r\n\r\nThis inserts two literal spaces.\r\n\r\n   \"%<\"\r\n\r\nThis represents the split between what will be left-aligned in your foldtext\r\nand what will be right aligned. The leftward angle bracket is meant as a\r\nmnemonic to indicate that, should all the contents of the foldtext be too wide\r\nfor the display area, the content to the right of this trigger will overwrite\r\npart of the content to the left. See :help spiffy_foldtext-%<.\r\n\r\n   \"%f{=}\"\r\n\r\nIf the content of the foldtext doesn't fill up the entire display region, the\r\nfoldtext will be filled with '='s at this point, to the amount needed to\r\nright-align the right-align section. See :help spiffy_foldtext-%f{}.\r\n\r\n  etc.\r\n","install_details":"There are a few supported ways to install this plugin:\r\n\r\n                                   Old style:\r\n\r\nIf you just don't care, simply copy the files into your run time and run the\r\ncommand:\r\n\r\n    :helptags $VIMRUNTIME\/doc\r\n\r\nPutting whatever directory the docs for the plugin ended up in.\r\n\r\nThis is *not* recommended. It's not even the *easiest* way nowadays. Try one of\r\nthe methods below.\r\n\r\n\r\n                                   Pathogen:\r\n\r\nUnzip the files into your bundle folder. Or do the following:\r\n\r\nNavigate to your bundle directory. By default, this will be something like\r\n\u00e2\u0080\u009c~\/.vim\/bundle\u00e2\u0080\u009d.\r\n\r\nThen run the command:\r\n\r\n    hg clone https:\/\/bitbucket.org\/atimholt\/spiffy_foldtext\r\n\r\n\r\n                                    Vundle:\r\n\r\nInsert the following line into your vimrc, under the conditions described by the\r\nVundle documentation:\r\n\r\n    Bundle 'atimholt\/spiffy_foldtext'\r\n\r\n\r\n                                   NeoBundle:\r\n\r\nInsert the following line into your vimrc, under the conditions described by the\r\nNeoBundle documentation:\r\n\r\n    NeoBundle 'atimholt\/spiffy_foldtext'\r\n\r\nOr, if you want a slightly better guarantee that you really have the latest\r\nversion:\r\n\r\n    NeoBundle 'bb:atimholt\/spiffy_foldtext', {'type': 'hg'}\r\n\r\nThis still puts you in the default branch, which is kept stable.\r\n\r\n                             Other Plugin managers:\r\n\r\nOther plugin managers are likely easily adapted to installing this plugin, using\r\ninstructions similar to one of the above. See your plugin manager's\r\ndocumentation.\r\n","5":"There are a few supported ways to install this plugin:\r\n\r\n                                   Old style:\r\n\r\nIf you just don't care, simply copy the files into your run time and run the\r\ncommand:\r\n\r\n    :helptags $VIMRUNTIME\/doc\r\n\r\nPutting whatever directory the docs for the plugin ended up in.\r\n\r\nThis is *not* recommended. It's not even the *easiest* way nowadays. Try one of\r\nthe methods below.\r\n\r\n\r\n                                   Pathogen:\r\n\r\nUnzip the files into your bundle folder. Or do the following:\r\n\r\nNavigate to your bundle directory. By default, this will be something like\r\n\u00e2\u0080\u009c~\/.vim\/bundle\u00e2\u0080\u009d.\r\n\r\nThen run the command:\r\n\r\n    hg clone https:\/\/bitbucket.org\/atimholt\/spiffy_foldtext\r\n\r\n\r\n                                    Vundle:\r\n\r\nInsert the following line into your vimrc, under the conditions described by the\r\nVundle documentation:\r\n\r\n    Bundle 'atimholt\/spiffy_foldtext'\r\n\r\n\r\n                                   NeoBundle:\r\n\r\nInsert the following line into your vimrc, under the conditions described by the\r\nNeoBundle documentation:\r\n\r\n    NeoBundle 'atimholt\/spiffy_foldtext'\r\n\r\nOr, if you want a slightly better guarantee that you really have the latest\r\nversion:\r\n\r\n    NeoBundle 'bb:atimholt\/spiffy_foldtext', {'type': 'hg'}\r\n\r\nThis still puts you in the default branch, which is kept stable.\r\n\r\n                             Other Plugin managers:\r\n\r\nOther plugin managers are likely easily adapted to installing this plugin, using\r\ninstructions similar to one of the above. See your plugin manager's\r\ndocumentation.\r\n","first_name":"Tim","6":"Tim","last_name":"Holt","7":"Holt","releases":[{"0":"4920","vim_version":"7.0","1":"7.0","script_version":"1.1","2":"1.1","version_comment":"changelog (1.1):\r\n  - Added window local fold-text, to override global fold text or buffer local\r\n    foldtext when present.\r\n  - Added buffer local fold-text, to override global fold text when present.\r\n  - Unit tests for stability and changeability (not really a feature)\r\n  - Added %[some number]fl trigger, inserting fold level\r\n","3":"changelog (1.1):\r\n  - Added window local fold-text, to override global fold text or buffer local\r\n    foldtext when present.\r\n  - Added buffer local fold-text, to override global fold text when present.\r\n  - Unit tests for stability and changeability (not really a feature)\r\n  - Added %[some number]fl trigger, inserting fold level\r\n","package":"spiffy_foldtext_1_1.7z","4":"spiffy_foldtext_1_1.7z","src_id":"21960","5":"21960","creation_date":"1401319533","6":"1401319533"},{"0":"4920","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"spiffy_foldtext_1_0.tar.gz","4":"spiffy_foldtext_1_0.tar.gz","src_id":"21756","5":"21756","creation_date":"1397079775","6":"1397079775"}]},"4919":{"script_id":"4919","0":"4919","script_name":"Tabv","1":"Tabv","script_type":"utility","2":"utility","summary":"Easily open relevant groupings of files as a tab in Vim","3":"Easily open relevant groupings of files as a tab in Vim","description":"I use it along with The NERD tree and CtrlP.Vim in order to easily call up files from within a project and make working in Vim more like working in an IDE.\r\n\r\nThe main command is :Tabv. It takes one argument, which is the \"root\" or \"stem\" of the set of files you want to open. It attempts to guess the type of project you are working on and open the files accordingly.\r\n\r\nFor more information, visit the GitHub repo https:\/\/github.com\/Kazark\/vim-tabv","4":"I use it along with The NERD tree and CtrlP.Vim in order to easily call up files from within a project and make working in Vim more like working in an IDE.\r\n\r\nThe main command is :Tabv. It takes one argument, which is the \"root\" or \"stem\" of the set of files you want to open. It attempts to guess the type of project you are working on and open the files accordingly.\r\n\r\nFor more information, visit the GitHub repo https:\/\/github.com\/Kazark\/vim-tabv","install_details":"Suggested method: use Pathogen.\r\n\r\ngit clone https:\/\/github.com\/Kazark\/vim-tabv.git ~\/.vim\/bundle\/tabv","5":"Suggested method: use Pathogen.\r\n\r\ngit clone https:\/\/github.com\/Kazark\/vim-tabv.git ~\/.vim\/bundle\/tabv","first_name":"Kazark","6":"Kazark","last_name":"(elided)","7":"(elided)","releases":[{"0":"4919","vim_version":"7.0","1":"7.0","script_version":"0.1.0","2":"0.1.0","version_comment":"Added C# support and :Tvword command to open tab grouping based on the word under the cursor","3":"Added C# support and :Tvword command to open tab grouping based on the word under the cursor","package":"tabv0.1.0.zip","4":"tabv0.1.0.zip","src_id":"21831","5":"21831","creation_date":"1398442246","6":"1398442246"},{"0":"4919","vim_version":"7.0","1":"7.0","script_version":"0.0.2","2":"0.0.2","version_comment":"\r\n\r\nHad used a three-parameter version of expand without realizing this was introduced in 7.4. Not worth breaking backwards compatibility for that, so changed it to split(expand(..., which is more readable anyway.\r\n\r\nAlso fixed a bug in the C++ <> implementation\r\n","3":"\r\n\r\nHad used a three-parameter version of expand without realizing this was introduced in 7.4. Not worth breaking backwards compatibility for that, so changed it to split(expand(..., which is more readable anyway.\r\n\r\nAlso fixed a bug in the C++ <> implementation\r\n","package":"tabv.zip","4":"tabv.zip","src_id":"21759","5":"21759","creation_date":"1397222756","6":"1397222756"},{"0":"4919","vim_version":"7.0","1":"7.0","script_version":"0.0.1","2":"0.0.1","version_comment":"Initial upload","3":"Initial upload","package":"tabv.zip","4":"tabv.zip","src_id":"21755","5":"21755","creation_date":"1397076332","6":"1397076332"}]},"4918":{"script_id":"4918","0":"4918","script_name":"otaku","1":"otaku","script_type":"color scheme","2":"color scheme","summary":"Inspired by Lucky Star","3":"Inspired by Lucky Star","description":"Blue\/purple kawaii for fun, GUI only. Redefines some window decorations just to cause trouble. Will most likely murder your eyes if you stare at it all night long. Yay!\r\n\r\nInitial prerelease party version covers the basics. No special support yet for various syntax\/scripts.\r\n\r\nhttp:\/\/elfhero.com\/otaku\/","4":"Blue\/purple kawaii for fun, GUI only. Redefines some window decorations just to cause trouble. Will most likely murder your eyes if you stare at it all night long. Yay!\r\n\r\nInitial prerelease party version covers the basics. No special support yet for various syntax\/scripts.\r\n\r\nhttp:\/\/elfhero.com\/otaku\/","install_details":"Typical colorscheme: just pop the file into the colors directory and type :colo otaku\r\n\r\nvimscript #2682 recommended for terminal use. It becomes really purple.","5":"Typical colorscheme: just pop the file into the colors directory and type :colo otaku\r\n\r\nvimscript #2682 recommended for terminal use. It becomes really purple.","first_name":"carson","6":"carson","last_name":"fire","7":"fire","releases":[{"0":"4918","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"otaku.vim","4":"otaku.vim","src_id":"21754","5":"21754","creation_date":"1397071862","6":"1397071862"}]},"4917":{"script_id":"4917","0":"4917","script_name":"vim-lldb","1":"vim-lldb","script_type":"utility","2":"utility","summary":"lldb debugger integration for vim","3":"lldb debugger integration for vim","description":"This plugin provides lldb debbugging integration including\r\n\r\n* breakpoints\r\n* watchpoints\r\n* threads view\r\n* locals view\r\n* and more ...\r\n\r\nArbitrary valid lldb commands can be invoked as well.\r\n\r\nThe plugin is hosted at : https:\/\/github.com\/gilligan\/vim-lldb","4":"This plugin provides lldb debbugging integration including\r\n\r\n* breakpoints\r\n* watchpoints\r\n* threads view\r\n* locals view\r\n* and more ...\r\n\r\nArbitrary valid lldb commands can be invoked as well.\r\n\r\nThe plugin is hosted at : https:\/\/github.com\/gilligan\/vim-lldb","install_details":"Installation is easiest using a package manager such as vundle: \r\n\r\nBundle \\\"gilligan\/vim-lldb\\\"\r\n","5":"Installation is easiest using a package manager such as vundle: \r\n\r\nBundle \\\"gilligan\/vim-lldb\\\"\r\n","first_name":"Tobias","6":"Tobias","last_name":"Pflug","7":"Pflug","releases":[{"0":"4917","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"vim-lldb.tar.gz","4":"vim-lldb.tar.gz","src_id":"21753","5":"21753","creation_date":"1397062998","6":"1397062998"}]},"4916":{"script_id":"4916","0":"4916","script_name":"vim-onoff","1":"vim-onoff","script_type":"utility","2":"utility","summary":"Turn Vim options on. Off.","3":"Turn Vim options on. Off.","description":"Vim has a lot of different boolean options \u00e2\u0080\u0094 cursorline, number, list, spell, etc. Toggle them gracefully.\r\n\r\nMuch of onoff.vim was extracted from my vimrc. Plugin provides an API to switch boolean options in Vim. After each turn option value shown at bottom of the window.\r\n\r\nMore documentation can be found on GitHub page\r\n\r\nhttps:\/\/github.com\/vitalk\/vim-onoff\r\n\r\nCopyright (c) by Vital Kudzelka.\r\n\r\nDistributed under the same terms as Vim itself. See :help license.","4":"Vim has a lot of different boolean options \u00e2\u0080\u0094 cursorline, number, list, spell, etc. Toggle them gracefully.\r\n\r\nMuch of onoff.vim was extracted from my vimrc. Plugin provides an API to switch boolean options in Vim. After each turn option value shown at bottom of the window.\r\n\r\nMore documentation can be found on GitHub page\r\n\r\nhttps:\/\/github.com\/vitalk\/vim-onoff\r\n\r\nCopyright (c) by Vital Kudzelka.\r\n\r\nDistributed under the same terms as Vim itself. See :help license.","install_details":"via pathogen.vim:\r\ncd ~\/.vim\/bundle\r\ngit clone git:\/\/github.com\/vitalk\/vim-onoff.git\r\nvia Vundle:\r\n\" Gracefully toggle boolean options in Vim\r\nBundle 'vitalk\/vim-onoff'","5":"via pathogen.vim:\r\ncd ~\/.vim\/bundle\r\ngit clone git:\/\/github.com\/vitalk\/vim-onoff.git\r\nvia Vundle:\r\n\" Gracefully toggle boolean options in Vim\r\nBundle 'vitalk\/vim-onoff'","first_name":"Vital","6":"Vital","last_name":"Kudzelka","7":"Kudzelka","releases":[{"0":"4916","vim_version":"7.0","1":"7.0","script_version":"0.2.2","2":"0.2.2","version_comment":"Update Vundle installation instruction.","3":"Update Vundle installation instruction.","package":"vim-onoff-0.2.2.zip","4":"vim-onoff-0.2.2.zip","src_id":"21902","5":"21902","creation_date":"1400408895","6":"1400408895"},{"0":"4916","vim_version":"7.0","1":"7.0","script_version":"0.2.0","2":"0.2.0","version_comment":"Add :Onoff command.","3":"Add :Onoff command.","package":"vim-onoff-0.2.0.zip","4":"vim-onoff-0.2.0.zip","src_id":"21798","5":"21798","creation_date":"1398067968","6":"1398067968"},{"0":"4916","vim_version":"7.0","1":"7.0","script_version":"0.1.1","2":"0.1.1","version_comment":"Initial upload","3":"Initial upload","package":"vim-onoff-0.1.1.zip","4":"vim-onoff-0.1.1.zip","src_id":"21750","5":"21750","creation_date":"1396986802","6":"1396986802"}]},"4915":{"script_id":"4915","0":"4915","script_name":"heroku.vim","1":"heroku.vim","script_type":"utility","2":"utility","summary":"Heroku toolbelt wrapper","3":"Heroku toolbelt wrapper","description":"A Vim plugin for interacting with Heroku.  Yes really.  Provided is an :Hk command that wraps the Heroku toolbelt, along with some pretty wicked tab complete.  Plus it adds a command wrapper for each Heroku remote in your Git config, so :Staging console is only a few keystrokes away.\r\n\r\nhttps:\/\/github.com\/tpope\/vim-heroku","4":"A Vim plugin for interacting with Heroku.  Yes really.  Provided is an :Hk command that wraps the Heroku toolbelt, along with some pretty wicked tab complete.  Plus it adds a command wrapper for each Heroku remote in your Git config, so :Staging console is only a few keystrokes away.\r\n\r\nhttps:\/\/github.com\/tpope\/vim-heroku","install_details":"Extract in ~\/.vim (~\\vimfiles on Windows).","5":"Extract in ~\/.vim (~\\vimfiles on Windows).","first_name":"Tim","6":"Tim","last_name":"Pope","7":"Pope","releases":[{"0":"4915","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"heroku.zip","4":"heroku.zip","src_id":"21749","5":"21749","creation_date":"1396979834","6":"1396979834"}]},"4914":{"script_id":"4914","0":"4914","script_name":"repeatable-motions.vim","1":"repeatable-motions.vim","script_type":"utility","2":"utility","summary":"Make most motions repeatable","3":"Make most motions repeatable","description":"While the motions f\/F and t\/T can be repeated with , and ; the default key mapping is not\r\nonly unintuitive it also requires the user to remember in what direction s\/he moved with the previous f\/t motion.\r\n\r\nThis nuisance brought me to rethink the idea of repeatable motions and resulted\r\nin this plugin.\r\n\r\nrepeatable-motions.vim makes most default motions repeatable in an easy and\r\nintuitive way. Perform a motion once (such as f) and repeat it simply with\r\n<C-h> to the left and <C-l> to the right. The direction is always what you'd expect, no more remembering if you used f or F.\r\n\r\nAdditionally repeatable-motions.vim distinguishes between vertical and horizontal\r\nmotions. So [M can be repeated with <C-j> and <C-k> while still remembering your\r\nprevious horizontal movement.\r\n\r\nMotions that are being repeated behave like normal motions, support counts and can be used in\r\noperation-pending as well as visual-mode.\r\n\r\nEverything works out of the box and making your own motion\r\nrepeatable is as easy as calling AddRepeatableMotion(\"<Up>\", \"<Down>\", 1).\r\nBuffer-, expression- and custom mappings are all handled without further ado.","4":"While the motions f\/F and t\/T can be repeated with , and ; the default key mapping is not\r\nonly unintuitive it also requires the user to remember in what direction s\/he moved with the previous f\/t motion.\r\n\r\nThis nuisance brought me to rethink the idea of repeatable motions and resulted\r\nin this plugin.\r\n\r\nrepeatable-motions.vim makes most default motions repeatable in an easy and\r\nintuitive way. Perform a motion once (such as f) and repeat it simply with\r\n<C-h> to the left and <C-l> to the right. The direction is always what you'd expect, no more remembering if you used f or F.\r\n\r\nAdditionally repeatable-motions.vim distinguishes between vertical and horizontal\r\nmotions. So [M can be repeated with <C-j> and <C-k> while still remembering your\r\nprevious horizontal movement.\r\n\r\nMotions that are being repeated behave like normal motions, support counts and can be used in\r\noperation-pending as well as visual-mode.\r\n\r\nEverything works out of the box and making your own motion\r\nrepeatable is as easy as calling AddRepeatableMotion(\"<Up>\", \"<Down>\", 1).\r\nBuffer-, expression- and custom mappings are all handled without further ado.","install_details":"Extract into ~\/.vim\r\nRun :helptags ~\/.vim\/doc in vim\r\n\r\nOr use a plugin manager (Vundle, Pathogen, vim-addon-manager)\r\n\r\nIf you want to change the default key mappings to repeat motions see :help repeatable-motions-mapping.","5":"Extract into ~\/.vim\r\nRun :helptags ~\/.vim\/doc in vim\r\n\r\nOr use a plugin manager (Vundle, Pathogen, vim-addon-manager)\r\n\r\nIf you want to change the default key mappings to repeat motions see :help repeatable-motions-mapping.","first_name":"Mohammed","6":"Mohammed","last_name":"Chelouti","7":"Chelouti","releases":[{"0":"4914","vim_version":"7.0","1":"7.0","script_version":"1.2","2":"1.2","version_comment":"Bugfixes:\r\n- Rectify inaccurate information in help and clear up some ambiguities.\r\n- Fix [' and ]' (and any custom motion containing a single quote) throwing\r\n  an error.\r\n\r\nFeatures:\r\n- Added <Plug>ReverseMostRecentMotion to perform most recent motion in\r\n  the oppposite direction.\r\n","3":"Bugfixes:\r\n- Rectify inaccurate information in help and clear up some ambiguities.\r\n- Fix [' and ]' (and any custom motion containing a single quote) throwing\r\n  an error.\r\n\r\nFeatures:\r\n- Added <Plug>ReverseMostRecentMotion to perform most recent motion in\r\n  the oppposite direction.\r\n","package":"repeatable-motions.zip","4":"repeatable-motions.zip","src_id":"25409","5":"25409","creation_date":"1500067690","6":"1500067690"},{"0":"4914","vim_version":"7.0","1":"7.0","script_version":"1.1.1","2":"1.1.1","version_comment":"Features:\r\n- Added 'g:repeatable_motions_default_mappings' to disable all default\r\n  mappings.\r\nBugfixes:\r\n- Renamed GetPreviouslyPreformedMotion() to |GetPreviouslyPerformedMotion()|.\r\n","3":"Features:\r\n- Added 'g:repeatable_motions_default_mappings' to disable all default\r\n  mappings.\r\nBugfixes:\r\n- Renamed GetPreviouslyPreformedMotion() to |GetPreviouslyPerformedMotion()|.\r\n","package":"repeatable-motions.zip","4":"repeatable-motions.zip","src_id":"22264","5":"22264","creation_date":"1406408776","6":"1406408776"},{"0":"4914","vim_version":"7.0","1":"7.0","script_version":"1.1","2":"1.1","version_comment":"Bugfixes:\r\n- RemoveRepeatableMotion() can now remove motions containing <Leader>.\r\n- Mappings with special keys (e.g. <Down> or <C-w>) are handled correctly.\r\n- Workaround for t\/T now doesn't get stuck on first occurrence unless\r\n  'cpoptions' contains ';'.\r\n\r\nFeatures:\r\n- Added functionality to repeat most recent motion in the same direction.\r\n","3":"Bugfixes:\r\n- RemoveRepeatableMotion() can now remove motions containing <Leader>.\r\n- Mappings with special keys (e.g. <Down> or <C-w>) are handled correctly.\r\n- Workaround for t\/T now doesn't get stuck on first occurrence unless\r\n  'cpoptions' contains ';'.\r\n\r\nFeatures:\r\n- Added functionality to repeat most recent motion in the same direction.\r\n","package":"repeatable-motions.zip","4":"repeatable-motions.zip","src_id":"21875","5":"21875","creation_date":"1399655918","6":"1399655918"},{"0":"4914","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"repeatable-motions.zip","4":"repeatable-motions.zip","src_id":"21746","5":"21746","creation_date":"1396905749","6":"1396905749"}]},"4913":{"script_id":"4913","0":"4913","script_name":"ttfzoom","1":"ttfzoom","script_type":"utility","2":"utility","summary":"For gvim, provide font zooming with Ctrl-MouseWheel like others","3":"For gvim, provide font zooming with Ctrl-MouseWheel like others","description":"*Requires python*.\r\n\r\nAfter installation, Ctrl-WheelUp increase the font size, Ctrl-WheelDown decrease the font size. This is almost like the standard interface for all things GUI because it's implemented by a LOT of them: chrome, firefox, editors, pdf readers and what have you.","4":"*Requires python*.\r\n\r\nAfter installation, Ctrl-WheelUp increase the font size, Ctrl-WheelDown decrease the font size. This is almost like the standard interface for all things GUI because it's implemented by a LOT of them: chrome, firefox, editors, pdf readers and what have you.","install_details":"Drop the file into ~\/.vim\/plugin","5":"Drop the file into ~\/.vim\/plugin","first_name":"Wenzhi","6":"Wenzhi","last_name":"Liang","7":"Liang","releases":[{"0":"4913","vim_version":"7.0","1":"7.0","script_version":"0.2","2":"0.2","version_comment":"Clean up. No functional difference - I don't think it needs any. :)","3":"Clean up. No functional difference - I don't think it needs any. :)","package":"ttfzoom.vim","4":"ttfzoom.vim","src_id":"21743","5":"21743","creation_date":"1396866043","6":"1396866043"},{"0":"4913","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"ttfzoom.vim","4":"ttfzoom.vim","src_id":"21737","5":"21737","creation_date":"1396711349","6":"1396711349"}]},"4912":{"script_id":"4912","0":"4912","script_name":"AlphaComplete","1":"AlphaComplete","script_type":"utility","2":"utility","summary":"Insert mode completion based on any sequence of alphabetic characters.","3":"Insert mode completion based on any sequence of alphabetic characters.","description":"DESCRIPTION\r\nThe built-in insert mode completion i_CTRL-N searches for keywords. When you\r\nwant to complete from fragments of variables (e.g. \"frobnicator\" from\r\n\"m_frobnicator\"), it won't work. Same when you have a keyword prefix before\r\nyour completion base (e.g. \"_fro\" won't find \"frobnicator\").\r\nThis plugin offers completion of sequences of alphabetic characters ([A-Za-z],\r\n\/\\a), and therefore can complete from text fragments or when there are\r\nnon-alphabetic keyword characters in front of the completion base.\r\n\r\nSEE ALSO\r\n- Check out the CompleteHelper.vim plugin page (vimscript #3914) for a full\r\n  list of insert mode completions powered by it.\r\n\r\nUSAGE\r\nIn insert mode, invoke the alphabetic completion via CTRL-X a\r\nYou can then search forward and backward via CTRL-N \/ CTRL-P, as usual.\r\n\r\nCTRL-X a                Find matches for whole fragments of alphabetic\r\n                        characters.\r\n                        Further use of CTRL-X a will copy the text including\r\n                        the next alphabetic fragments following the previous\r\n                        expansion in other contexts.","4":"DESCRIPTION\r\nThe built-in insert mode completion i_CTRL-N searches for keywords. When you\r\nwant to complete from fragments of variables (e.g. \"frobnicator\" from\r\n\"m_frobnicator\"), it won't work. Same when you have a keyword prefix before\r\nyour completion base (e.g. \"_fro\" won't find \"frobnicator\").\r\nThis plugin offers completion of sequences of alphabetic characters ([A-Za-z],\r\n\/\\a), and therefore can complete from text fragments or when there are\r\nnon-alphabetic keyword characters in front of the completion base.\r\n\r\nSEE ALSO\r\n- Check out the CompleteHelper.vim plugin page (vimscript #3914) for a full\r\n  list of insert mode completions powered by it.\r\n\r\nUSAGE\r\nIn insert mode, invoke the alphabetic completion via CTRL-X a\r\nYou can then search forward and backward via CTRL-N \/ CTRL-P, as usual.\r\n\r\nCTRL-X a                Find matches for whole fragments of alphabetic\r\n                        characters.\r\n                        Further use of CTRL-X a will copy the text including\r\n                        the next alphabetic fragments following the previous\r\n                        expansion in other contexts.","install_details":"INSTALLATION\r\nThis script is packaged as a vimball. If you have the \"gunzip\" decompressor\r\nin your PATH, simply edit the *.vmb.gz package in Vim; otherwise, decompress\r\nthe archive first, e.g. using WinZip. Inside Vim, install by sourcing the\r\nvimball or via the :UseVimball command.\r\n    vim AlphaComplete*.vmb.gz\r\n    :so %\r\nTo uninstall, use the :RmVimball command.\r\n\r\nDEPENDENCIES\r\n- Requires Vim 7.0 or higher.\r\n- Requires the CompleteHelper.vim plugin (vimscript #3914).\r\n\r\nCONFIGURATION\r\nFor a permanent configuration, put the following commands into your vimrc:\r\n\r\nAnaloguous to the 'complete' option, you can specify which buffers will be\r\nscanned for completion candidates. Currently, '.' (current buffer), 'w'\r\n(buffers from other windows), and 'b' (other listed buffers) are supported.\r\n    let g:AlphaComplete_complete = '.,w,b'\r\nThe global setting can be overridden for a particular buffer\r\n(b:AlphaComplete_complete).\r\n\r\nIf you want to use a different mapping, map your keys to the\r\n<Plug>(AlphaComplete) mapping target _before_ sourcing the script (e.g.\r\nin your vimrc):\r\n    imap <C-x>a <Plug>(AlphaComplete)","5":"INSTALLATION\r\nThis script is packaged as a vimball. If you have the \"gunzip\" decompressor\r\nin your PATH, simply edit the *.vmb.gz package in Vim; otherwise, decompress\r\nthe archive first, e.g. using WinZip. Inside Vim, install by sourcing the\r\nvimball or via the :UseVimball command.\r\n    vim AlphaComplete*.vmb.gz\r\n    :so %\r\nTo uninstall, use the :RmVimball command.\r\n\r\nDEPENDENCIES\r\n- Requires Vim 7.0 or higher.\r\n- Requires the CompleteHelper.vim plugin (vimscript #3914).\r\n\r\nCONFIGURATION\r\nFor a permanent configuration, put the following commands into your vimrc:\r\n\r\nAnaloguous to the 'complete' option, you can specify which buffers will be\r\nscanned for completion candidates. Currently, '.' (current buffer), 'w'\r\n(buffers from other windows), and 'b' (other listed buffers) are supported.\r\n    let g:AlphaComplete_complete = '.,w,b'\r\nThe global setting can be overridden for a particular buffer\r\n(b:AlphaComplete_complete).\r\n\r\nIf you want to use a different mapping, map your keys to the\r\n<Plug>(AlphaComplete) mapping target _before_ sourcing the script (e.g.\r\nin your vimrc):\r\n    imap <C-x>a <Plug>(AlphaComplete)","first_name":"Ingo","6":"Ingo","last_name":"Karkat","7":"Karkat","releases":[{"0":"4912","vim_version":"7.0","1":"7.0","script_version":"1.00","2":"1.00","version_comment":"Initial upload","3":"Initial upload","package":"AlphaComplete-1.00.vmb.gz","4":"AlphaComplete-1.00.vmb.gz","src_id":"21734","5":"21734","creation_date":"1396637932","6":"1396637932"}]},"4911":{"script_id":"4911","0":"4911","script_name":"LineComplete","1":"LineComplete","script_type":"utility","2":"utility","summary":"Insert mode completion of entire lines based on looser matching.","3":"Insert mode completion of entire lines based on looser matching.","description":"DESCRIPTION\r\nThe built-in i_CTRL-X_CTRL-L line completion allows to quickly grab entire\r\nlines, but you have to know and type the first characters as a completion\r\nbase. That's bad if the start is difficult to type (e.g. because of comment\r\nprefixes) or the key differentiating word only comes late in the line. On the\r\nother hand, any indent is ignored, so you cannot reduce the number of matches\r\neven if you know that the indent of the desired line is the same as the\r\ncurrent one.\r\n\r\nThis plugin offers an alternative full-line completion that considers any\r\nexisting indent, and lifts the restriction that matches must _start_ with the\r\ncompletion base. Instead, the WORDs of the base can appear anywhere in the\r\nline, with fallbacks allowing other WORDs in between or even the WORDs\r\nappearing anywhere inside the line.\r\n\r\nSEE ALSO\r\n- Check out the CompleteHelper.vim plugin page (vimscript #3914) for a full\r\n  list of insert mode completions powered by it.\r\n\r\nUSAGE\r\nIn insert mode, invoke the line completion via CTRL-X l\r\nYou can then search forward and backward via CTRL-N \/ CTRL-P, as usual.\r\n\r\nCTRL-X l                Find matches for whole lines that have the same indent\r\n                        as the current line (only if any exists!) and match\r\n                        the text before the cursor (not necessarily at the\r\n                        start), falling back to a match of all WORDs before\r\n                        the cursor (possibly with other text in between each,\r\n                        but still in the given order), first as\r\n                        space-separated WORDs, finally accepting matches\r\n                        anywhere.\r\n\r\n                        In contrast, the built-in i_CTRL-X_CTRL-L always\r\n                        ignores the indent. This completion is stricter if\r\n                        indent is given (it must match exactly), but otherwise\r\n                        much more loose, because the completion base need not\r\n                        specify the start of the line.\r\n                        If you don't want the indent restriction, use\r\n                        i_CTRL-U before typing the completion base to clear\r\n                        any indent.\r\n\r\n                        Further use of CTRL-X l will copy the line after the\r\n                        one that has been completed.","4":"DESCRIPTION\r\nThe built-in i_CTRL-X_CTRL-L line completion allows to quickly grab entire\r\nlines, but you have to know and type the first characters as a completion\r\nbase. That's bad if the start is difficult to type (e.g. because of comment\r\nprefixes) or the key differentiating word only comes late in the line. On the\r\nother hand, any indent is ignored, so you cannot reduce the number of matches\r\neven if you know that the indent of the desired line is the same as the\r\ncurrent one.\r\n\r\nThis plugin offers an alternative full-line completion that considers any\r\nexisting indent, and lifts the restriction that matches must _start_ with the\r\ncompletion base. Instead, the WORDs of the base can appear anywhere in the\r\nline, with fallbacks allowing other WORDs in between or even the WORDs\r\nappearing anywhere inside the line.\r\n\r\nSEE ALSO\r\n- Check out the CompleteHelper.vim plugin page (vimscript #3914) for a full\r\n  list of insert mode completions powered by it.\r\n\r\nUSAGE\r\nIn insert mode, invoke the line completion via CTRL-X l\r\nYou can then search forward and backward via CTRL-N \/ CTRL-P, as usual.\r\n\r\nCTRL-X l                Find matches for whole lines that have the same indent\r\n                        as the current line (only if any exists!) and match\r\n                        the text before the cursor (not necessarily at the\r\n                        start), falling back to a match of all WORDs before\r\n                        the cursor (possibly with other text in between each,\r\n                        but still in the given order), first as\r\n                        space-separated WORDs, finally accepting matches\r\n                        anywhere.\r\n\r\n                        In contrast, the built-in i_CTRL-X_CTRL-L always\r\n                        ignores the indent. This completion is stricter if\r\n                        indent is given (it must match exactly), but otherwise\r\n                        much more loose, because the completion base need not\r\n                        specify the start of the line.\r\n                        If you don't want the indent restriction, use\r\n                        i_CTRL-U before typing the completion base to clear\r\n                        any indent.\r\n\r\n                        Further use of CTRL-X l will copy the line after the\r\n                        one that has been completed.","install_details":"INSTALLATION\r\nThis script is packaged as a vimball. If you have the \"gunzip\" decompressor\r\nin your PATH, simply edit the *.vmb.gz package in Vim; otherwise, decompress\r\nthe archive first, e.g. using WinZip. Inside Vim, install by sourcing the\r\nvimball or via the :UseVimball command.\r\n    vim LineComplete*.vmb.gz\r\n    :so %\r\nTo uninstall, use the :RmVimball command.\r\n\r\nDEPENDENCIES\r\n- Requires Vim 7.0 or higher.\r\n- Requires the CompleteHelper.vim plugin (vimscript #3914).\r\n\r\nCONFIGURATION\r\nFor a permanent configuration, put the following commands into your vimrc:\r\n\r\nAnaloguous to the 'complete' option, you can specify which buffers will be\r\nscanned for completion candidates. Currently, '.' (current buffer), 'w'\r\n(buffers from other windows), and 'b' (other listed buffers) are supported.\r\n    let g:LineComplete_complete = '.,w,b'\r\nThe global setting can be overridden for a particular buffer\r\n(b:LineComplete_complete).\r\n\r\nIf you want to use a different mapping, map your keys to the\r\n<Plug>(LineComplete) mapping target _before_ sourcing the script\r\n(e.g. in your vimrc):\r\n    imap <C-x>l <Plug>(LineComplete)","5":"INSTALLATION\r\nThis script is packaged as a vimball. If you have the \"gunzip\" decompressor\r\nin your PATH, simply edit the *.vmb.gz package in Vim; otherwise, decompress\r\nthe archive first, e.g. using WinZip. Inside Vim, install by sourcing the\r\nvimball or via the :UseVimball command.\r\n    vim LineComplete*.vmb.gz\r\n    :so %\r\nTo uninstall, use the :RmVimball command.\r\n\r\nDEPENDENCIES\r\n- Requires Vim 7.0 or higher.\r\n- Requires the CompleteHelper.vim plugin (vimscript #3914).\r\n\r\nCONFIGURATION\r\nFor a permanent configuration, put the following commands into your vimrc:\r\n\r\nAnaloguous to the 'complete' option, you can specify which buffers will be\r\nscanned for completion candidates. Currently, '.' (current buffer), 'w'\r\n(buffers from other windows), and 'b' (other listed buffers) are supported.\r\n    let g:LineComplete_complete = '.,w,b'\r\nThe global setting can be overridden for a particular buffer\r\n(b:LineComplete_complete).\r\n\r\nIf you want to use a different mapping, map your keys to the\r\n<Plug>(LineComplete) mapping target _before_ sourcing the script\r\n(e.g. in your vimrc):\r\n    imap <C-x>l <Plug>(LineComplete)","first_name":"Ingo","6":"Ingo","last_name":"Karkat","7":"Karkat","releases":[{"0":"4911","vim_version":"7.0","1":"7.0","script_version":"1.00","2":"1.00","version_comment":"Initial upload","3":"Initial upload","package":"LineComplete-1.00.vmb.gz","4":"LineComplete-1.00.vmb.gz","src_id":"21733","5":"21733","creation_date":"1396621068","6":"1396621068"}]},"4910":{"script_id":"4910","0":"4910","script_name":"nc.vim","1":"nc.vim","script_type":"syntax","2":"syntax","summary":"Syntax highlighting for NC (G-Code) files","3":"Syntax highlighting for NC (G-Code) files","description":"A simple set of syntax highlighting rules for G-Code files for CNC controls.","4":"A simple set of syntax highlighting rules for G-Code files for CNC controls.","install_details":"","5":"","first_name":"Dave","6":"Dave","last_name":"Eno","7":"Eno","releases":[{"0":"4910","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"nc.vim","4":"nc.vim","src_id":"21729","5":"21729","creation_date":"1396550716","6":"1396550716"}]},"4909":{"script_id":"4909","0":"4909","script_name":"vim-sails","1":"vim-sails","script_type":"utility","2":"utility","summary":"Vim navigation plugin for Sails framework. Heavily inspired by vim-rails.","3":"Vim navigation plugin for Sails framework. Heavily inspired by vim-rails.","description":"# sails.vim\r\nhttps:\/\/github.com\/rsludge\/vim-sails\r\n\r\nVim navigation plugin for [Sails](https:\/\/github.com\/balderdashy\/sails) framework. Heavily inspired by [vim-rails](https:\/\/github.com\/tpope\/vim-rails).\r\n\r\n## Installation\r\n\r\nPlugin can be installed with Vundle or NeoBundle.\r\n\r\n## Usage\r\n\r\nWhile editing Sails project you can use :Econtroller or :Emodel commands to navigate project file structure.\r\n`:Econtroller`, `:Emodel`, `:Eview`, `:Epolicy`, `:Econfig` commands are allowed. Also variants with `S`, `V`, `T` are available for splits and tabedit.\r\n","4":"# sails.vim\r\nhttps:\/\/github.com\/rsludge\/vim-sails\r\n\r\nVim navigation plugin for [Sails](https:\/\/github.com\/balderdashy\/sails) framework. Heavily inspired by [vim-rails](https:\/\/github.com\/tpope\/vim-rails).\r\n\r\n## Installation\r\n\r\nPlugin can be installed with Vundle or NeoBundle.\r\n\r\n## Usage\r\n\r\nWhile editing Sails project you can use :Econtroller or :Emodel commands to navigate project file structure.\r\n`:Econtroller`, `:Emodel`, `:Eview`, `:Epolicy`, `:Econfig` commands are allowed. Also variants with `S`, `V`, `T` are available for splits and tabedit.\r\n","install_details":"","5":"","first_name":"Oleg","6":"Oleg","last_name":"Potapov","7":"Potapov","releases":[{"0":"4909","vim_version":"7.0","1":"7.0","script_version":"0.1.1","2":"0.1.1","version_comment":"- added :Sgenerate command","3":"- added :Sgenerate command","package":"vim-sails-0.1.1.tar.gz","4":"vim-sails-0.1.1.tar.gz","src_id":"21780","5":"21780","creation_date":"1397637177","6":"1397637177"},{"0":"4909","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"vim-sails.tar.gz","4":"vim-sails.tar.gz","src_id":"21720","5":"21720","creation_date":"1396510689","6":"1396510689"}]},"4908":{"script_id":"4908","0":"4908","script_name":"visualHtml","1":"visualHtml","script_type":"ftplugin","2":"ftplugin","summary":"script to preview in live html, php and css edition","3":"script to preview in live html, php and css edition","description":"Plugin to preview in live php, html and css edition.\r\nYou'll need CLCBrowser, witch have been developed specially for this plugin, to get the best results.\r\nSee the documentation in the package for more informations","4":"Plugin to preview in live php, html and css edition.\r\nYou'll need CLCBrowser, witch have been developed specially for this plugin, to get the best results.\r\nSee the documentation in the package for more informations","install_details":"Copy paste all files in you ~\/.vimrc in the corresponding sub directories, or install it as a pathogen bundle.\r\nYou can also follow the git repository : https:\/\/github.com\/hl037\/vim-visualHtml\r\ngit clone git@github.com:hl037\/vim-visualHtml.git\r\nYou'll need CLCBrowser to get the best results. you can download its sources here : https:\/\/gitorious.org\/clcbrowser\/clcbrowser more informations about will come soon","5":"Copy paste all files in you ~\/.vimrc in the corresponding sub directories, or install it as a pathogen bundle.\r\nYou can also follow the git repository : https:\/\/github.com\/hl037\/vim-visualHtml\r\ngit clone git@github.com:hl037\/vim-visualHtml.git\r\nYou'll need CLCBrowser to get the best results. you can download its sources here : https:\/\/gitorious.org\/clcbrowser\/clcbrowser more informations about will come soon","first_name":"L\u00c3\u00a9o Flaventin","6":"L\u00c3\u00a9o Flaventin","last_name":"Hauchecorne","7":"Hauchecorne","releases":[{"0":"4908","vim_version":"7.0","1":"7.0","script_version":"1.2.1","2":"1.2.1","version_comment":"+ settings bug fixed","3":"+ settings bug fixed","package":"visualHtml_v1.2.1.tar.gz","4":"visualHtml_v1.2.1.tar.gz","src_id":"21728","5":"21728","creation_date":"1396540866","6":"1396540866"},{"0":"4908","vim_version":"7.0","1":"7.0","script_version":"1.2","2":"1.2","version_comment":"+ file type blacklist (not to launch the browser for .md files for example)","3":"+ file type blacklist (not to launch the browser for .md files for example)","package":"visualHtml_v1.2.tar.gz","4":"visualHtml_v1.2.tar.gz","src_id":"21723","5":"21723","creation_date":"1396536159","6":"1396536159"},{"0":"4908","vim_version":"7.0","1":"7.0","script_version":"1.1","2":"1.1","version_comment":"+ autolauch and auto quit browsers\r\n+ allow change exec path\r\n+ documentation of custom browser support\r\n+ change name of clcb windows title and tabs","3":"+ autolauch and auto quit browsers\r\n+ allow change exec path\r\n+ documentation of custom browser support\r\n+ change name of clcb windows title and tabs","package":"visualHtml_v1.1.tar.gz","4":"visualHtml_v1.1.tar.gz","src_id":"21721","5":"21721","creation_date":"1396529237","6":"1396529237"},{"0":"4908","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"visualHtml.tar.gz","4":"visualHtml.tar.gz","src_id":"21716","5":"21716","creation_date":"1396481926","6":"1396481926"}]},"4907":{"script_id":"4907","0":"4907","script_name":"angular.vim","1":"angular.vim","script_type":"ftplugin","2":"ftplugin","summary":"Some niceties for the AngularJS framework","3":"Some niceties for the AngularJS framework","description":"Features\r\n\r\nSwitch to test file and vice versa\r\n\r\n:A\r\n\r\nA, the \"alternate\" file, has been mapped to take you from your code to the corresponding test file, or from your test file to the corresponding implementation file. For example, if you're in app\/js\/rock-socks.js, and you hammer :A, you will be taken to test\/spec\/rock-socks.js, if such a file exists. Some other common directory structure conventions in the angular community, such as app\/src and test\/unit, are also supported. Feel free to file a pull request if your reasonable convention doesn't work.\r\n\r\nJump to definition of service\/directive\/controller\/etc\r\n\r\ngf\r\n\r\n\"Go to file\" has been slightly overriden to take you to the definition of the file under your cursor. If you're reading some code like this...\r\n\r\nif (true) {\r\n  AwesomeService.changeStateBecauseMutationIsAwesome();\r\n}\r\n...and your cursor is on AwesomeService, and you hammer gf, if there is a file called awesome-service.js somewhere in a subdirectory of your path, you will be taken there. The default behavior of gf can also be quite useful in the context of an angular app, since html fragments are specified as file paths in views (with ng-include src=\"full\/path.html), directives (with templateUrl: 'src\/myapp\/modules\/main\/views\/\/prompt-list.html', so an attempt has been made to allow this to work as well. If all that is missing from a template path is the \"app\" directory (which is a common value for \"cwd\" in Gruntfile.js, the plugin will add this for you as well. If either of these two things don't work for your use case, file a ticket, figure out why and file a pull request, or use ctags.\r\n\r\nRun the current spec\r\n\r\nIf you're writing jasmine unit tests for your angular app, they look like this:\r\n\r\nit('should work', function() {\r\n  var actualThing = 'cow';\r\n  expect(actualThing).toEqual('cow');\r\n});\r\n\r\nNow, if you take that \"it\" prefix, and replace it with \"iit\", instead of running your entire suite, it will run JUST THAT ONE SPEC. There are probably bad reasons to want to do this, like if your build is broken and you only want to fix your code, but it can be pretty handy to focus in on just one spec at a time (and one spec generally runs way fast).\r\n\r\nSo, if you're anywhere inside a spec:\r\n\r\n:AngularRunSpec\r\n\r\nor the \"run spec\" mapping:\r\n\r\n<leader>rs\r\n\r\nwill toggle the spec between \"it\" and \"iit.\" This works especially well if you have a karma watch going. See the screencast at http:\/\/notkeepingitreal.com (soon come).","4":"Features\r\n\r\nSwitch to test file and vice versa\r\n\r\n:A\r\n\r\nA, the \"alternate\" file, has been mapped to take you from your code to the corresponding test file, or from your test file to the corresponding implementation file. For example, if you're in app\/js\/rock-socks.js, and you hammer :A, you will be taken to test\/spec\/rock-socks.js, if such a file exists. Some other common directory structure conventions in the angular community, such as app\/src and test\/unit, are also supported. Feel free to file a pull request if your reasonable convention doesn't work.\r\n\r\nJump to definition of service\/directive\/controller\/etc\r\n\r\ngf\r\n\r\n\"Go to file\" has been slightly overriden to take you to the definition of the file under your cursor. If you're reading some code like this...\r\n\r\nif (true) {\r\n  AwesomeService.changeStateBecauseMutationIsAwesome();\r\n}\r\n...and your cursor is on AwesomeService, and you hammer gf, if there is a file called awesome-service.js somewhere in a subdirectory of your path, you will be taken there. The default behavior of gf can also be quite useful in the context of an angular app, since html fragments are specified as file paths in views (with ng-include src=\"full\/path.html), directives (with templateUrl: 'src\/myapp\/modules\/main\/views\/\/prompt-list.html', so an attempt has been made to allow this to work as well. If all that is missing from a template path is the \"app\" directory (which is a common value for \"cwd\" in Gruntfile.js, the plugin will add this for you as well. If either of these two things don't work for your use case, file a ticket, figure out why and file a pull request, or use ctags.\r\n\r\nRun the current spec\r\n\r\nIf you're writing jasmine unit tests for your angular app, they look like this:\r\n\r\nit('should work', function() {\r\n  var actualThing = 'cow';\r\n  expect(actualThing).toEqual('cow');\r\n});\r\n\r\nNow, if you take that \"it\" prefix, and replace it with \"iit\", instead of running your entire suite, it will run JUST THAT ONE SPEC. There are probably bad reasons to want to do this, like if your build is broken and you only want to fix your code, but it can be pretty handy to focus in on just one spec at a time (and one spec generally runs way fast).\r\n\r\nSo, if you're anywhere inside a spec:\r\n\r\n:AngularRunSpec\r\n\r\nor the \"run spec\" mapping:\r\n\r\n<leader>rs\r\n\r\nwill toggle the spec between \"it\" and \"iit.\" This works especially well if you have a karma watch going. See the screencast at http:\/\/notkeepingitreal.com (soon come).","install_details":"Extract in ~\/.vim or ~\\vimfiles.\r\n\r\nGrab the very latest from http:\/\/github.com\/burnettk\/vim-angular","5":"Extract in ~\/.vim or ~\\vimfiles.\r\n\r\nGrab the very latest from http:\/\/github.com\/burnettk\/vim-angular","first_name":"Kevin","6":"Kevin","last_name":"Burnett","7":"Burnett","releases":[{"0":"4907","vim_version":"7.0","1":"7.0","script_version":"2.0.0","2":"2.0.0","version_comment":"Supports jasmine 2 conventions.","3":"Supports jasmine 2 conventions.","package":"angular.zip","4":"angular.zip","src_id":"23208","5":"23208","creation_date":"1429733869","6":"1429733869"},{"0":"4907","vim_version":"7.0","1":"7.0","script_version":"1.0.1","2":"1.0.1","version_comment":"lots of refactors, tests","3":"lots of refactors, tests","package":"angular.zip","4":"angular.zip","src_id":"21742","5":"21742","creation_date":"1396834352","6":"1396834352"},{"0":"4907","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"angular.zip","4":"angular.zip","src_id":"21710","5":"21710","creation_date":"1396406234","6":"1396406234"}]},"4906":{"script_id":"4906","0":"4906","script_name":"Peggi","1":"Peggi","script_type":"utility","2":"utility","summary":"A Parsing framework for Parsing Expression Grammar","3":"A Parsing framework for Parsing Expression Grammar","description":"Peggi is a parsing framework. On it's own, it's of not much use, but it can serve you when you write a Vim script that has to struggle with data too complicated to parse with regular expressions alone.\r\n\r\nIt's home is here: https:\/\/github.com\/EinfachToll\/peggi\/\r\n\r\n\r\nBasic Usage\r\n---------------------\r\n\r\n1. In your Vim script, first specify the formal grammar of your data as Parsing Expression Grammar (PEG)\r\n2. Then start Peggi: `let result = peggi#peggi#parse(grammar, data, start-nonterminal)`\r\n\r\nSee the Readme for details.\r\n\r\n\r\n\r\nExample\r\n---------------\r\n\r\nAs an example, let's look at a script that uses Peggi for processing arithmetic expressions:\r\n\r\nlet s:grammar = '\r\n            \\ Expression = ( Term , \/\\s*[+-]\/.strip() , Expression ).g:compute()  |  Term\r\n            \\ Term = ( Factor , \/\\s*[*\\\/]\/.strip() , Term ).g:compute()  |  Factor\r\n            \\ Factor = ( \/\\s*(\/ , Expression , \/\\s*)\/ ).take(\"1\")  |  \/\\s*[-0-9.]\\+\/.str2float()\r\n            \\ '\r\n\r\nfunction! g:compute(list)\r\n    if a:list[1] == '*'\r\n        return a:list[0] * a:list[2]\r\n    elseif a:list[1] == '\/'\r\n        return a:list[0] \/ a:list[2]\r\n    elseif a:list[1] == '+'\r\n        return a:list[0] + a:list[2]\r\n    elseif a:list[1] == '-'\r\n        return a:list[0] - a:list[2]\r\n    endif\r\nendfunction\r\n\r\nlet s:example = '-10 * (2* 2)\/(0.6 +2)'\r\n\r\necho peggi#peggi#parse(s:grammar, s:example, 'Expression')\r\n\r\n\r\nThe output is -15.384615","4":"Peggi is a parsing framework. On it's own, it's of not much use, but it can serve you when you write a Vim script that has to struggle with data too complicated to parse with regular expressions alone.\r\n\r\nIt's home is here: https:\/\/github.com\/EinfachToll\/peggi\/\r\n\r\n\r\nBasic Usage\r\n---------------------\r\n\r\n1. In your Vim script, first specify the formal grammar of your data as Parsing Expression Grammar (PEG)\r\n2. Then start Peggi: `let result = peggi#peggi#parse(grammar, data, start-nonterminal)`\r\n\r\nSee the Readme for details.\r\n\r\n\r\n\r\nExample\r\n---------------\r\n\r\nAs an example, let's look at a script that uses Peggi for processing arithmetic expressions:\r\n\r\nlet s:grammar = '\r\n            \\ Expression = ( Term , \/\\s*[+-]\/.strip() , Expression ).g:compute()  |  Term\r\n            \\ Term = ( Factor , \/\\s*[*\\\/]\/.strip() , Term ).g:compute()  |  Factor\r\n            \\ Factor = ( \/\\s*(\/ , Expression , \/\\s*)\/ ).take(\"1\")  |  \/\\s*[-0-9.]\\+\/.str2float()\r\n            \\ '\r\n\r\nfunction! g:compute(list)\r\n    if a:list[1] == '*'\r\n        return a:list[0] * a:list[2]\r\n    elseif a:list[1] == '\/'\r\n        return a:list[0] \/ a:list[2]\r\n    elseif a:list[1] == '+'\r\n        return a:list[0] + a:list[2]\r\n    elseif a:list[1] == '-'\r\n        return a:list[0] - a:list[2]\r\n    endif\r\nendfunction\r\n\r\nlet s:example = '-10 * (2* 2)\/(0.6 +2)'\r\n\r\necho peggi#peggi#parse(s:grammar, s:example, 'Expression')\r\n\r\n\r\nThe output is -15.384615","install_details":"Use one of the many plugin managers for Vim, or install it manually by putting the folder `peggi\/` into any `autoload\/` directory in your runtimepath.","5":"Use one of the many plugin managers for Vim, or install it manually by putting the folder `peggi\/` into any `autoload\/` directory in your runtimepath.","first_name":"Daniel","6":"Daniel","last_name":"Schemala","7":"Schemala","releases":[{"0":"4906","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"peggi.tar.gz","4":"peggi.tar.gz","src_id":"21705","5":"21705","creation_date":"1396354523","6":"1396354523"}]},"4905":{"script_id":"4905","0":"4905","script_name":"apprentice.vim","1":"apprentice.vim","script_type":"color scheme","2":"color scheme","summary":"A dark low-contrast colorscheme.","3":"A dark low-contrast colorscheme.","description":"Apprentice is a low-contrast colorscheme based on the awesome Sorcerer by Jeet Sukumaran.\r\n\r\nIt is essentially a streamlined version of the original with a reduced number of colors entirely taken from the default xterm palette to ensure a similar look in 256 colors-ready terminal emulators and GUI Vim.\r\n\r\nFor screenshots, visit Apprentice\u00e2\u0080\u0099s home page:\r\n\r\nhttp:\/\/romainl.github.io\/Apprentice\/\r\n\r\nFor issues and pull requests, visit Apprentice's GitHub page:\r\n\r\nhttps:\/\/github.com\/romainl\/Apprentice","4":"Apprentice is a low-contrast colorscheme based on the awesome Sorcerer by Jeet Sukumaran.\r\n\r\nIt is essentially a streamlined version of the original with a reduced number of colors entirely taken from the default xterm palette to ensure a similar look in 256 colors-ready terminal emulators and GUI Vim.\r\n\r\nFor screenshots, visit Apprentice\u00e2\u0080\u0099s home page:\r\n\r\nhttp:\/\/romainl.github.io\/Apprentice\/\r\n\r\nFor issues and pull requests, visit Apprentice's GitHub page:\r\n\r\nhttps:\/\/github.com\/romainl\/Apprentice","install_details":"On UNIX-like systems:\r\n\r\n$HOME\/.vim\/colors\/apprentice.vim\r\n\r\nOn Windows:\r\n\r\n$HOME\\vimfiles\\colors\\apprentice.vim\r\n","5":"On UNIX-like systems:\r\n\r\n$HOME\/.vim\/colors\/apprentice.vim\r\n\r\nOn Windows:\r\n\r\n$HOME\\vimfiles\\colors\\apprentice.vim\r\n","first_name":"Romain","6":"Romain","last_name":"Lafourcade","7":"Lafourcade","releases":[{"0":"4905","vim_version":"8.0","1":"8.0","script_version":"2.0","2":"2.0","version_comment":"So it has been six years since the last official release. Apprentice hasn't lost its spirit but a lot happened in the meantime, in Vim and in Apprentice itself.\r\n\r\nThis is the changelog for v2.0.\r\n\r\nDropped:\r\n\r\n- Explicit support for Neovim,\r\n- explicit support for status line plugins,\r\n- italic text because of spotty support across terminal emulators and poor feature detection in Vim,\r\n- brittle logic,\r\n- iTerm-specific hack.\r\n\r\nAdded:\r\n\r\n- Support for :help :terminal,\r\n- definition of g:terminal_ansi_colors,\r\n- support for :help terminal-debugger.\r\n\r\nFixed:\r\n\r\n- Casing issues,\r\n- faulty logic,\r\n- priority of several highlight groups,\r\n- inconsistencies between 256c and GUI,\r\n- cursor color in GUI,\r\n- brighter comments,\r\n- diff highlight groups.\r\n\r\nLow-level changes:\r\n\r\n- Switch to a template-based workflow (see README.md).","3":"So it has been six years since the last official release. Apprentice hasn't lost its spirit but a lot happened in the meantime, in Vim and in Apprentice itself.\r\n\r\nThis is the changelog for v2.0.\r\n\r\nDropped:\r\n\r\n- Explicit support for Neovim,\r\n- explicit support for status line plugins,\r\n- italic text because of spotty support across terminal emulators and poor feature detection in Vim,\r\n- brittle logic,\r\n- iTerm-specific hack.\r\n\r\nAdded:\r\n\r\n- Support for :help :terminal,\r\n- definition of g:terminal_ansi_colors,\r\n- support for :help terminal-debugger.\r\n\r\nFixed:\r\n\r\n- Casing issues,\r\n- faulty logic,\r\n- priority of several highlight groups,\r\n- inconsistencies between 256c and GUI,\r\n- cursor color in GUI,\r\n- brighter comments,\r\n- diff highlight groups.\r\n\r\nLow-level changes:\r\n\r\n- Switch to a template-based workflow (see README.md).","package":"vim-apprentice-2.0.zip","4":"vim-apprentice-2.0.zip","src_id":"27995","5":"27995","creation_date":"1649788233","6":"1649788233"},{"0":"4905","vim_version":"7.0","1":"7.0","script_version":"1.9","2":"1.9","version_comment":"Fixed priority issue between `Error` and `Diff...` on one side and `Visual` on the other side.","3":"Fixed priority issue between `Error` and `Diff...` on one side and `Visual` on the other side.","package":"Apprentice-1.9.zip","4":"Apprentice-1.9.zip","src_id":"23973","5":"23973","creation_date":"1454267917","6":"1454267917"},{"0":"4905","vim_version":"7.0","1":"7.0","script_version":"v1.8","2":"v1.8","version_comment":"* Better support for the Windows console.\r\n* Support for neovim's terminal thanks to metalelf0 (https:\/\/github.com\/metalelf0).\r\n* Minor tweaks","3":"* Better support for the Windows console.\r\n* Support for neovim's terminal thanks to metalelf0 (https:\/\/github.com\/metalelf0).\r\n* Minor tweaks","package":"Apprentice.1.8.zip","4":"Apprentice.1.8.zip","src_id":"23498","5":"23498","creation_date":"1438531216","6":"1438531216"},{"0":"4905","vim_version":"7.0","1":"7.0","script_version":"1.7","2":"1.7","version_comment":"Fixed MatchParen.","3":"Fixed MatchParen.","package":"apprentice-1.7.zip","4":"apprentice-1.7.zip","src_id":"23269","5":"23269","creation_date":"1431161719","6":"1431161719"},{"0":"4905","vim_version":"7.0","1":"7.0","script_version":"1.6","2":"1.6","version_comment":"This release fixes many errors in the 8\/16 version.","3":"This release fixes many errors in the 8\/16 version.","package":"Apprentice-1.6.zip","4":"Apprentice-1.6.zip","src_id":"22744","5":"22744","creation_date":"1419862622","6":"1419862622"},{"0":"4905","vim_version":"7.0","1":"7.0","script_version":"1.5","2":"1.5","version_comment":"* The tabline, statusline and vertical split are now visually consistent: \"black on ocre\" for \"active\", \"ocre on black\" for \"inactive\".\r\n* Following up on issue #1 (https:\/\/github.com\/romainl\/Apprentice\/issues\/1), folds are darker than they used to be.\r\n\r\nEnjoy.","3":"* The tabline, statusline and vertical split are now visually consistent: \"black on ocre\" for \"active\", \"ocre on black\" for \"inactive\".\r\n* Following up on issue #1 (https:\/\/github.com\/romainl\/Apprentice\/issues\/1), folds are darker than they used to be.\r\n\r\nEnjoy.","package":"Apprentice-1.5.zip","4":"Apprentice-1.5.zip","src_id":"22525","5":"22525","creation_date":"1413143940","6":"1413143940"},{"0":"4905","vim_version":"7.0","1":"7.0","script_version":"1.4","2":"1.4","version_comment":"* Completely reworked to work better in 8\/16 colors terminal.","3":"* Completely reworked to work better in 8\/16 colors terminal.","package":"apprentice-1.4.zip","4":"apprentice-1.4.zip","src_id":"22311","5":"22311","creation_date":"1407587615","6":"1407587615"},{"0":"4905","vim_version":"7.0","1":"7.0","script_version":"1.3","2":"1.3","version_comment":"* The 8 colors part no longer defines a \"Normal\" background color.\r\n* See the Github page for color swatches to customize your 8 colors terminal.","3":"* The 8 colors part no longer defines a \"Normal\" background color.\r\n* See the Github page for color swatches to customize your 8 colors terminal.","package":"apprentice-1.3.zip","4":"apprentice-1.3.zip","src_id":"22254","5":"22254","creation_date":"1406116826","6":"1406116826"},{"0":"4905","vim_version":"7.0","1":"7.0","script_version":"1.2","2":"1.2","version_comment":"* Added installation instructions to README.\r\n* Changed images in README to remove screnshot dir.\r\n* Cleaned up the cterm colors for non-256 terminals.\r\n* Changed htmlLink for more visibility.\r\n* Fixed TabLineFill.","3":"* Added installation instructions to README.\r\n* Changed images in README to remove screnshot dir.\r\n* Cleaned up the cterm colors for non-256 terminals.\r\n* Changed htmlLink for more visibility.\r\n* Fixed TabLineFill.","package":"apprentice-1.2.zip","4":"apprentice-1.2.zip","src_id":"21792","5":"21792","creation_date":"1397945648","6":"1397945648"},{"0":"4905","vim_version":"7.0","1":"7.0","script_version":"1.1","2":"1.1","version_comment":"Fixes an Error vs CursorLine conflict.\r\nAdds rules for Fugitive\u00e2\u0080\u0099s diffAdded and diffRemoved.","3":"Fixes an Error vs CursorLine conflict.\r\nAdds rules for Fugitive\u00e2\u0080\u0099s diffAdded and diffRemoved.","package":"apprentice.zip","4":"apprentice.zip","src_id":"21722","5":"21722","creation_date":"1396532891","6":"1396532891"},{"0":"4905","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"apprentice.zip","4":"apprentice.zip","src_id":"21697","5":"21697","creation_date":"1396280305","6":"1396280305"}]},"4904":{"script_id":"4904","0":"4904","script_name":"avahi-syntax","1":"avahi-syntax","script_type":"color scheme","2":"color scheme","summary":"VIM syntax highlighting for Avahi","3":"VIM syntax highlighting for Avahi","description":"VIM syntax highlighting for Avahi packages\r\n- avahi-client\r\n- avahi-common\r\n- avahi-glib\r\n- avahi-gobject\r\n- avahi-qt\r\n- avahi-ui\r\n\r\nABSOLUTELY NO WARRANTY WHATSOEVER and COMPLETELY FREE to do whatever you want with it!!!\r\nDid it for my own use and now sharing it...","4":"VIM syntax highlighting for Avahi packages\r\n- avahi-client\r\n- avahi-common\r\n- avahi-glib\r\n- avahi-gobject\r\n- avahi-qt\r\n- avahi-ui\r\n\r\nABSOLUTELY NO WARRANTY WHATSOEVER and COMPLETELY FREE to do whatever you want with it!!!\r\nDid it for my own use and now sharing it...","install_details":"Copy into ~\/.vim\/syntax\/","5":"Copy into ~\/.vim\/syntax\/","first_name":"kiran","6":"kiran","last_name":"sb","7":"sb","releases":[{"0":"4904","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"avahi.vim","4":"avahi.vim","src_id":"21674","5":"21674","creation_date":"1395840040","6":"1395840040"}]},"4903":{"script_id":"4903","0":"4903","script_name":"github-issues.vim","1":"github-issues.vim","script_type":"utility","2":"utility","summary":"Github Issues integration with Vim","3":"Github Issues integration with Vim","description":"Allows you to browse issues for the current repository with :Gissues, and populates the omnifunc auto complete in gitcommit filetypes. Detailed information, examples, and animated GIFs over on Github: \r\n\r\nhttps:\/\/github.com\/jaxbot\/github-issues.vim\r\n\r\nShould be drop-in in most cases. Requires Python","4":"Allows you to browse issues for the current repository with :Gissues, and populates the omnifunc auto complete in gitcommit filetypes. Detailed information, examples, and animated GIFs over on Github: \r\n\r\nhttps:\/\/github.com\/jaxbot\/github-issues.vim\r\n\r\nShould be drop-in in most cases. Requires Python","install_details":"","5":"","first_name":"Jonathan","6":"Jonathan","last_name":"Warner","7":"Warner","releases":[{"0":"4903","vim_version":"7.3","1":"7.3","script_version":"2.0","2":"2.0","version_comment":"Initial upload","3":"Initial upload","package":"githubissues.vim","4":"githubissues.vim","src_id":"21664","5":"21664","creation_date":"1395704607","6":"1395704607"}]},"4902":{"script_id":"4902","0":"4902","script_name":"VimCompletesMe","1":"VimCompletesMe","script_type":"utility","2":"utility","summary":"Simple tab completion for Vim","3":"Simple tab completion for Vim","description":"A super simple, super minimal, super light-weight tab-completion plugin for Vim.\r\n\r\nWithout configuration, the Tab key will:\r\n\r\n    Use Vim's local keyword completion (Ctrl-X_Ctrl-N).\r\n    Complete a file path (Ctrl-X_Ctrl-F)\r\n    Offer omni-completion after typing a period. (Ctrl-X_Ctrl-O)\r\n\r\nWith a b:vcm_tab_complete variable, the Tab key will complete using:\r\n\r\n    Dictionary words (Ctrl-X_Ctrl-K)\r\n    User-defined completion (Ctrl-X_Ctrl-U)\r\n    Tags (Ctrl-X_Ctrl-])\r\n    Vim command line (Ctrl-X_Ctrl-V)\r\n\r\nYou can set the b:vcm_tab_complete variable interactively, or in an autocommand:\r\n\r\nautocmd FileType text,markdown let b:vcm_tab_complete = 'dict'\r\n\r\nStriving for minimalism, this plugin weighs under 80 lines of code.\r\n\r\nNote: You can always get the latest version on github: hhttps:\/\/git.sr.ht\/~ackyshake\/VimCompletesMe.vim","4":"A super simple, super minimal, super light-weight tab-completion plugin for Vim.\r\n\r\nWithout configuration, the Tab key will:\r\n\r\n    Use Vim's local keyword completion (Ctrl-X_Ctrl-N).\r\n    Complete a file path (Ctrl-X_Ctrl-F)\r\n    Offer omni-completion after typing a period. (Ctrl-X_Ctrl-O)\r\n\r\nWith a b:vcm_tab_complete variable, the Tab key will complete using:\r\n\r\n    Dictionary words (Ctrl-X_Ctrl-K)\r\n    User-defined completion (Ctrl-X_Ctrl-U)\r\n    Tags (Ctrl-X_Ctrl-])\r\n    Vim command line (Ctrl-X_Ctrl-V)\r\n\r\nYou can set the b:vcm_tab_complete variable interactively, or in an autocommand:\r\n\r\nautocmd FileType text,markdown let b:vcm_tab_complete = 'dict'\r\n\r\nStriving for minimalism, this plugin weighs under 80 lines of code.\r\n\r\nNote: You can always get the latest version on github: hhttps:\/\/git.sr.ht\/~ackyshake\/VimCompletesMe.vim","install_details":"","5":"","first_name":"Akshay","6":"Akshay","last_name":"Hegde","7":"Hegde","releases":[{"0":"4902","vim_version":"7.3","1":"7.3","script_version":"1.5.2","2":"1.5.2","version_comment":"- Avoid clobbering completeopt's 'noselect'\r\n- Ensure fallback completion uses the same direction as the normal completion","3":"- Avoid clobbering completeopt's 'noselect'\r\n- Ensure fallback completion uses the same direction as the normal completion","package":"VimCompletesMe-1.5.2.zip","4":"VimCompletesMe-1.5.2.zip","src_id":"27432","5":"27432","creation_date":"1609322946","6":"1609322946"},{"0":"4902","vim_version":"7.3","1":"7.3","script_version":"1.5.1","2":"1.5.1","version_comment":"This is a hotfix release over VimCompletesMe v1.5 which fixes a function naming issue.","3":"This is a hotfix release over VimCompletesMe v1.5 which fixes a function naming issue.","package":"VimCompletesMe-1.5.1.zip","4":"VimCompletesMe-1.5.1.zip","src_id":"25881","5":"25881","creation_date":"1521005905","6":"1521005905"},{"0":"4902","vim_version":"7.3","1":"7.3","script_version":"1.5","2":"1.5","version_comment":"- VCM is now more consistent when using \"p\" for the g:vcm_direction\r\n- g:vcm_direction is now \"n\" as the default\r\n- Introduce vcm_omni_pattern variable to set patterns to look for, for smart invocations of i_Ctrl-x_Ctrl-o\r\n- Introduce vcm_s_tab_mapping option to allow user to set their own action commands for Shift Tab key press\r\n- General fixes and improvements\r\n\r\nSee :help VimCompletesMe for full details.","3":"- VCM is now more consistent when using \"p\" for the g:vcm_direction\r\n- g:vcm_direction is now \"n\" as the default\r\n- Introduce vcm_omni_pattern variable to set patterns to look for, for smart invocations of i_Ctrl-x_Ctrl-o\r\n- Introduce vcm_s_tab_mapping option to allow user to set their own action commands for Shift Tab key press\r\n- General fixes and improvements\r\n\r\nSee :help VimCompletesMe for full details.","package":"VimCompletesMe-1.5.zip","4":"VimCompletesMe-1.5.zip","src_id":"25876","5":"25876","creation_date":"1520835445","6":"1520835445"},{"0":"4902","vim_version":"7.3","1":"7.3","script_version":"1.3","2":"1.3","version_comment":"- General improvements to completion behavior\r\n- Minor bugfixes","3":"- General improvements to completion behavior\r\n- Minor bugfixes","package":"VimCompletesMe-1.3.tar.gz","4":"VimCompletesMe-1.3.tar.gz","src_id":"24188","5":"24188","creation_date":"1461299328","6":"1461299328"},{"0":"4902","vim_version":"7.3","1":"7.3","script_version":"1.2.1","2":"1.2.1","version_comment":"This is a hotfix release that fixes Vim 7.3 compatibility.","3":"This is a hotfix release that fixes Vim 7.3 compatibility.","package":"VimCompletesMe-1.2.1.zip","4":"VimCompletesMe-1.2.1.zip","src_id":"23194","5":"23194","creation_date":"1429476520","6":"1429476520"},{"0":"4902","vim_version":"7.4","1":"7.4","script_version":"1.2","2":"1.2","version_comment":"* Fix an issue with remapping default keybindings\r\n* Documentation updates","3":"* Fix an issue with remapping default keybindings\r\n* Documentation updates","package":"VimCompletesMe-1.2.zip","4":"VimCompletesMe-1.2.zip","src_id":"23190","5":"23190","creation_date":"1429326659","6":"1429326659"},{"0":"4902","vim_version":"7.3","1":"7.3","script_version":"1.1","2":"1.1","version_comment":"- Add an option to disable default maps\r\n- Fix an issue where fallback completion would enter a letter below the cursor\r\n- Documentation fixes","3":"- Add an option to disable default maps\r\n- Fix an issue where fallback completion would enter a letter below the cursor\r\n- Documentation fixes","package":"VimCompletesMe-1.1.zip","4":"VimCompletesMe-1.1.zip","src_id":"22894","5":"22894","creation_date":"1423474872","6":"1423474872"},{"0":"4902","vim_version":"7.3","1":"7.3","script_version":"1.0","2":"1.0","version_comment":"* Provide a way to fallback to keyword completion if completion with b:vcm_tab_complete variable fails\r\n* Simplified a lot of the code\r\n* Fix a minor helptag reference","3":"* Provide a way to fallback to keyword completion if completion with b:vcm_tab_complete variable fails\r\n* Simplified a lot of the code\r\n* Fix a minor helptag reference","package":"VimCompletesMe-1.0.zip","4":"VimCompletesMe-1.0.zip","src_id":"22740","5":"22740","creation_date":"1419751171","6":"1419751171"},{"0":"4902","vim_version":"7.3","1":"7.3","script_version":"0.3","2":"0.3","version_comment":"VimCompletesMe v0.3\r\n\r\n- Allows user to set 'b:vcm_tab_complete' to \"omni\" to allow omnicompletion without typing a period.","3":"VimCompletesMe v0.3\r\n\r\n- Allows user to set 'b:vcm_tab_complete' to \"omni\" to allow omnicompletion without typing a period.","package":"VimCompletesMe.zip","4":"VimCompletesMe.zip","src_id":"21767","5":"21767","creation_date":"1397429539","6":"1397429539"},{"0":"4902","vim_version":"7.3","1":"7.3","script_version":"0.2","2":"0.2","version_comment":"VimCompletesMe v0.2\r\n\r\n- Minor changes in README\r\n- Added FAQ section in the docs\r\n- Fix plugin name on vim.org","3":"VimCompletesMe v0.2\r\n\r\n- Minor changes in README\r\n- Added FAQ section in the docs\r\n- Fix plugin name on vim.org","package":"VimCompletesMe.zip","4":"VimCompletesMe.zip","src_id":"21698","5":"21698","creation_date":"1396292103","6":"1396292103"},{"0":"4902","vim_version":"7.3","1":"7.3","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"VimComplesMe.zip","4":"VimComplesMe.zip","src_id":"21654","5":"21654","creation_date":"1395619904","6":"1395619904"}]},"4901":{"script_id":"4901","0":"4901","script_name":"vim-lsdyna","1":"vim-lsdyna","script_type":"ftplugin","2":"ftplugin","summary":"VIM filetype plugin for Ls-Dyna","3":"VIM filetype plugin for Ls-Dyna","description":"VIM filetype plugin for Ls-Dyna FE solver.\r\n\r\nMain plugin features:\r\n- syntax highlighting\r\n- node\/element table folding\r\n- keyword library\r\n- curve commands\r\n- many others useful features\r\n\r\n","4":"VIM filetype plugin for Ls-Dyna FE solver.\r\n\r\nMain plugin features:\r\n- syntax highlighting\r\n- node\/element table folding\r\n- keyword library\r\n- curve commands\r\n- many others useful features\r\n\r\n","install_details":"https:\/\/github.com\/gradzikb\/vim-lsdyna","5":"https:\/\/github.com\/gradzikb\/vim-lsdyna","first_name":"Bartosz","6":"Bartosz","last_name":"Gradzik","7":"Gradzik","releases":[{"0":"4901","vim_version":"7.4","1":"7.4","script_version":"1.1.0","2":"1.1.0","version_comment":"Update","3":"Update","package":"vim-lsdyna-1.1.0.zip","4":"vim-lsdyna-1.1.0.zip","src_id":"22854","5":"22854","creation_date":"1422697764","6":"1422697764"},{"0":"4901","vim_version":"7.4","1":"7.4","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"vim-lsdyna-1.0.zip","4":"vim-lsdyna-1.0.zip","src_id":"21649","5":"21649","creation_date":"1395426845","6":"1395426845"}]},"4900":{"script_id":"4900","0":"4900","script_name":"Arrow Key Repurpose","1":"Arrow Key Repurpose","script_type":"utility","2":"utility","summary":"A plugin for repurposing the arrow keys mostly for shifting lines of text around","3":"A plugin for repurposing the arrow keys mostly for shifting lines of text around","description":"A plugin-ification of  the older version of vimtip #1066, with a couple modifications and added documentation.\r\n\r\nMany consider it a best practice not to use the keyboard\u00e2\u0080\u0099s arrow keys for movement. New users are usually encouraged to use hjkl instead. vimtip #1066 recommends re-mapping the arrow keys\u00e2\u0080\u0099 functionality rather than letting them go to waste.\r\n\r\nThis is a plugin implementation of that tip\u00e2\u0080\u0094in short, the arrow keys now shift lines around by manipulating indentation and blank lines\u00e2\u0080\u0094with modifications from around the web and personal additions, along with documentation.","4":"A plugin-ification of  the older version of vimtip #1066, with a couple modifications and added documentation.\r\n\r\nMany consider it a best practice not to use the keyboard\u00e2\u0080\u0099s arrow keys for movement. New users are usually encouraged to use hjkl instead. vimtip #1066 recommends re-mapping the arrow keys\u00e2\u0080\u0099 functionality rather than letting them go to waste.\r\n\r\nThis is a plugin implementation of that tip\u00e2\u0080\u0094in short, the arrow keys now shift lines around by manipulating indentation and blank lines\u00e2\u0080\u0094with modifications from around the web and personal additions, along with documentation.","install_details":"There are currently two recommended ways to install this plugin, though other\r\nplugin managers are likely easily adapted:\r\n\r\nPathogen:\r\n\r\nNavigate to your bundle directory. By default, this will be something like\r\n\u00e2\u0080\u009c~\/.vim\/bundle\u00e2\u0080\u009d.\r\n\r\nThen decompress the downloaded file into its own folder, or run the command:\r\n\r\n    \u00e2\u0080\u009chg clone https:\/\/bitbucket.org\/atimholt\/arrowkeyrepurpose\u00e2\u0080\u009d\r\n\r\n(minus the quotes)\r\n\r\nNeoBundle:\r\n\r\nAdd this line to your vimrc (minus the quotes), under the conditions described\r\nby the NeoBundle documentation:\r\n\r\n    \u00e2\u0080\u009cNeoBundle 'bb:atimholt\/ArrowKeyRepurpose', {'type': 'hg'}\u00e2\u0080\u009d\r\n","5":"There are currently two recommended ways to install this plugin, though other\r\nplugin managers are likely easily adapted:\r\n\r\nPathogen:\r\n\r\nNavigate to your bundle directory. By default, this will be something like\r\n\u00e2\u0080\u009c~\/.vim\/bundle\u00e2\u0080\u009d.\r\n\r\nThen decompress the downloaded file into its own folder, or run the command:\r\n\r\n    \u00e2\u0080\u009chg clone https:\/\/bitbucket.org\/atimholt\/arrowkeyrepurpose\u00e2\u0080\u009d\r\n\r\n(minus the quotes)\r\n\r\nNeoBundle:\r\n\r\nAdd this line to your vimrc (minus the quotes), under the conditions described\r\nby the NeoBundle documentation:\r\n\r\n    \u00e2\u0080\u009cNeoBundle 'bb:atimholt\/ArrowKeyRepurpose', {'type': 'hg'}\u00e2\u0080\u009d\r\n","first_name":"Tim","6":"Tim","last_name":"Holt","7":"Holt","releases":[{"0":"4900","vim_version":"7.0","1":"7.0","script_version":"1.0release","2":"1.0release","version_comment":"Fixed bugs & works properly with visual selections & folded text. Added user settings. Sorry about the version number confusion.","3":"Fixed bugs & works properly with visual selections & folded text. Added user settings. Sorry about the version number confusion.","package":"arrowkeyrepurpose_1.0.tar.gz","4":"arrowkeyrepurpose_1.0.tar.gz","src_id":"21788","5":"21788","creation_date":"1397773445","6":"1397773445"},{"0":"4900","vim_version":"7.0","1":"7.0","script_version":"1.0.0","2":"1.0.0","version_comment":"Initial upload","3":"Initial upload","package":"arrowkeyrepurpose.1.0.0.tar.gz","4":"arrowkeyrepurpose.1.0.0.tar.gz","src_id":"21641","5":"21641","creation_date":"1395256394","6":"1395256394"}]},"4899":{"script_id":"4899","0":"4899","script_name":"cra.vim","1":"cra.vim","script_type":"utility","2":"utility","summary":"yearly timesheet","3":"yearly timesheet","description":"yearly timesheet for Vim\r\n\r\n    realtime counter for holiday (while there is a shift of one month on paychecks)\r\n    get rid of Libreoffice (or worse Excel) to do this\r\n","4":"yearly timesheet for Vim\r\n\r\n    realtime counter for holiday (while there is a shift of one month on paychecks)\r\n    get rid of Libreoffice (or worse Excel) to do this\r\n","install_details":"cf https:\/\/github.com\/YannMoisan\/cra.vim","5":"cf https:\/\/github.com\/YannMoisan\/cra.vim","first_name":"yann","6":"yann","last_name":"moisan","7":"moisan","releases":[{"0":"4899","vim_version":"7.0","1":"7.0","script_version":"0.2","2":"0.2","version_comment":"Fix buggy archive","3":"Fix buggy archive","package":"cra.vim.tar.gz","4":"cra.vim.tar.gz","src_id":"21644","5":"21644","creation_date":"1395337723","6":"1395337723"}]},"4898":{"script_id":"4898","0":"4898","script_name":"VIDE","1":"VIDE","script_type":"utility","2":"utility","summary":"Simple IDE interface for vim","3":"Simple IDE interface for vim","description":"Vim as an IDE provides an out of the box IDE like experience using existing vim plugins.\r\n\r\nIt is intended to allow vim users to get up and running quickly with a minimal set of plugins and configuration options.\r\n\r\nYou can find more information at https:\/\/github.com\/hutchinson\/vide\/releases\/tag\/1.2.1\r\n\r\nCurrently vide provides:\r\n\r\n- File browsing via NERDTree (4.2.0)\r\n- Buffer browsing using MiniBufExplorer (6.5.2)\r\n- Function\/Class outline viewer using Tagbar (2.6.1)\r\n- Buffer management using bufkill\r\n- SuperTab! (2.0)\r\n- delimitMate (2.6)\r\n- A customised .vimrc file which integrates these plugins and other vim features to provide a basic integrated development environment.\r\n\r\nRequirements\r\n- vim 7+ (known to work on version 7.3)\r\n- Exuberant CTags available here: http:\/\/ctags.sourceforge.net","4":"Vim as an IDE provides an out of the box IDE like experience using existing vim plugins.\r\n\r\nIt is intended to allow vim users to get up and running quickly with a minimal set of plugins and configuration options.\r\n\r\nYou can find more information at https:\/\/github.com\/hutchinson\/vide\/releases\/tag\/1.2.1\r\n\r\nCurrently vide provides:\r\n\r\n- File browsing via NERDTree (4.2.0)\r\n- Buffer browsing using MiniBufExplorer (6.5.2)\r\n- Function\/Class outline viewer using Tagbar (2.6.1)\r\n- Buffer management using bufkill\r\n- SuperTab! (2.0)\r\n- delimitMate (2.6)\r\n- A customised .vimrc file which integrates these plugins and other vim features to provide a basic integrated development environment.\r\n\r\nRequirements\r\n- vim 7+ (known to work on version 7.3)\r\n- Exuberant CTags available here: http:\/\/ctags.sourceforge.net","install_details":"Installation\r\n[WARNING]: The vide installer will attempt to back-up your existing .vimrc file and .vim folder. They will be backed up to ~\/.vimrc~vide_backup and ~\/.vim~vide_backup respectively.\r\nHowever you should make backup copies yourself if you have made significant modifications.\r\nThe installer comes with no warranty and no liability is accepted for loss of data, use at your own risk.\r\n\r\ngit clone https:\/\/github.com\/hutchinson\/vide.git vide\r\ncd vide\r\n.\/install","5":"Installation\r\n[WARNING]: The vide installer will attempt to back-up your existing .vimrc file and .vim folder. They will be backed up to ~\/.vimrc~vide_backup and ~\/.vim~vide_backup respectively.\r\nHowever you should make backup copies yourself if you have made significant modifications.\r\nThe installer comes with no warranty and no liability is accepted for loss of data, use at your own risk.\r\n\r\ngit clone https:\/\/github.com\/hutchinson\/vide.git vide\r\ncd vide\r\n.\/install","first_name":"Dan","6":"Dan","last_name":"Hutchinson","7":"Hutchinson","releases":[{"0":"4898","vim_version":"7.3","1":"7.3","script_version":"1.3.0","2":"1.3.0","version_comment":"This release adds the airline plugin to the installer script.","3":"This release adds the airline plugin to the installer script.","package":"vide-1.3.0.zip","4":"vide-1.3.0.zip","src_id":"22775","5":"22775","creation_date":"1420904650","6":"1420904650"},{"0":"4898","vim_version":"7.0","1":"7.0","script_version":"1.2.1","2":"1.2.1","version_comment":"Fix default language specifier for spell checking.","3":"Fix default language specifier for spell checking.","package":"vide-1.2.1.tar.gz","4":"vide-1.2.1.tar.gz","src_id":"21666","5":"21666","creation_date":"1395753605","6":"1395753605"},{"0":"4898","vim_version":"7.0","1":"7.0","script_version":"1.2.0","2":"1.2.0","version_comment":"Adds SuperTab and delimitMate + spell checking is enabled by default.","3":"Adds SuperTab and delimitMate + spell checking is enabled by default.","package":"vide-1.2.0.tar","4":"vide-1.2.0.tar","src_id":"21661","5":"21661","creation_date":"1395697388","6":"1395697388"},{"0":"4898","vim_version":"7.0","1":"7.0","script_version":"1.1.0","2":"1.1.0","version_comment":"Adds bufkill","3":"Adds bufkill","package":"vide-1.1.0.tar","4":"vide-1.1.0.tar","src_id":"21643","5":"21643","creation_date":"1395261078","6":"1395261078"},{"0":"4898","vim_version":"7.0","1":"7.0","script_version":"1.0.0","2":"1.0.0","version_comment":"Initial upload","3":"Initial upload","package":"vide-1.0.0.tar","4":"vide-1.0.0.tar","src_id":"21636","5":"21636","creation_date":"1395174029","6":"1395174029"}]},"4897":{"script_id":"4897","0":"4897","script_name":"cloneSimilar","1":"cloneSimilar","script_type":"utility","2":"utility","summary":"Create a duplicate clone of the current buffer with a similar name.","3":"Create a duplicate clone of the current buffer with a similar name.","description":"DESCRIPTION\r\nThis plugin combines the buffer cloning functionality of clone.vim\r\n(vimscript #4896) with the selection of similar files provided by\r\nEditSimilar.vim (vimscript #2544) to provide :CloneSubstitute,\r\n:ClonePlus etc. command variants of the original :CloneAs command.\r\n\r\nUSAGE\r\n:ClonePlus,  :CloneMinus,  :CloneSubstitute,  :CloneRoot\r\n:SClonePlus, :SCloneMinus, :SCloneSubstitute, :SCloneRoot\r\n                        Duplicate and edit the current buffer to a file with a\r\n                        similar name, using the substitutions and iterations\r\n                        provided by the EditSimilar.vim plugin.","4":"DESCRIPTION\r\nThis plugin combines the buffer cloning functionality of clone.vim\r\n(vimscript #4896) with the selection of similar files provided by\r\nEditSimilar.vim (vimscript #2544) to provide :CloneSubstitute,\r\n:ClonePlus etc. command variants of the original :CloneAs command.\r\n\r\nUSAGE\r\n:ClonePlus,  :CloneMinus,  :CloneSubstitute,  :CloneRoot\r\n:SClonePlus, :SCloneMinus, :SCloneSubstitute, :SCloneRoot\r\n                        Duplicate and edit the current buffer to a file with a\r\n                        similar name, using the substitutions and iterations\r\n                        provided by the EditSimilar.vim plugin.","install_details":"INSTALLATION\r\nThis script is packaged as a vimball. If you have the \"gunzip\" decompressor\r\nin your PATH, simply edit the *.vmb.gz package in Vim; otherwise, decompress\r\nthe archive first, e.g. using WinZip. Inside Vim, install by sourcing the\r\nvimball or via the :UseVimball command.\r\n    vim cloneSimilar*.vmb.gz\r\n    :so %\r\nTo uninstall, use the :RmVimball command.\r\n\r\nDEPENDENCIES\r\n- Requires Vim 7.0 or higher.\r\n- Requires the clone.vim plugin (vimscript #4896), version 1.00 or\r\n  higher.\r\n- Requires the EditSimilar.vim plugin (vimscript #2544), version 2.10 or\r\n  higher.","5":"INSTALLATION\r\nThis script is packaged as a vimball. If you have the \"gunzip\" decompressor\r\nin your PATH, simply edit the *.vmb.gz package in Vim; otherwise, decompress\r\nthe archive first, e.g. using WinZip. Inside Vim, install by sourcing the\r\nvimball or via the :UseVimball command.\r\n    vim cloneSimilar*.vmb.gz\r\n    :so %\r\nTo uninstall, use the :RmVimball command.\r\n\r\nDEPENDENCIES\r\n- Requires Vim 7.0 or higher.\r\n- Requires the clone.vim plugin (vimscript #4896), version 1.00 or\r\n  higher.\r\n- Requires the EditSimilar.vim plugin (vimscript #2544), version 2.10 or\r\n  higher.","first_name":"Ingo","6":"Ingo","last_name":"Karkat","7":"Karkat","releases":[{"0":"4897","vim_version":"7.0","1":"7.0","script_version":"1.00","2":"1.00","version_comment":"Initial upload","3":"Initial upload","package":"cloneSimilar-1.00.vmb.gz","4":"cloneSimilar-1.00.vmb.gz","src_id":"21634","5":"21634","creation_date":"1395152053","6":"1395152053"}]},"4896":{"script_id":"4896","0":"4896","script_name":"clone","1":"clone","script_type":"utility","2":"utility","summary":"Create a duplicate clone of the current buffer.","3":"Create a duplicate clone of the current buffer.","description":"DESCRIPTION\r\nOften, it is efficient to base a new file (e.g. unit test, meeting minutes) on\r\nan existing one, and just apply the changes instead of re-creating the entire\r\nfile. In Vim, one can create a duplicate copy of the current buffer via\r\n:write {newfile} or :saveas {newfile}. But the former doesn't\r\nautomatically open the cloned file, whereas with the latter, you're losing the\r\nbuffer containing the original file. Also, the identical clone is immediately\r\npersisted, which may confuse automated build tools (or yourself, should you\r\nget interrupted and forget to make the actual modifications). Transferring the\r\nbuffer contents via :yank is also cumbersome and clobbers a register.\r\n\r\nThis plugin offers a :CloneAs command that duplicates the current buffer (or\r\nonly parts of it) without persisting the clone right away (only on :w), and\r\nkeeping the original buffer loaded and unmodified inside Vim (with\r\n:SCloneAs, it'll even be kept displayed in a window).\r\n\r\nOftentimes, duplication in source code is a code smell. Please use this plugin\r\nresponsibly ;-)\r\n\r\nSEE ALSO\r\nThe cloneSimilar.vim plugin (vimscript #4897) adds additional command\r\nvariants powered by the EditSimilar.vim (vimscript #2544) plugin.\r\n\r\nUSAGE\r\n:[range]CloneAs {file}  Duplicate and edit the current buffer \/ specified\r\n                        lines with a new name, keep the existing one.\r\n:[range]SCloneAs {file} Duplicate and split the current buffer \/ specified\r\n                        lines with a new name, keep the existing one.\r\n\r\n                        The original cursor position \/ window view will be\r\n                        kept, as well as the 'fileformat', 'fileencoding' and\r\n                        'filetype' settings of the original buffer.","4":"DESCRIPTION\r\nOften, it is efficient to base a new file (e.g. unit test, meeting minutes) on\r\nan existing one, and just apply the changes instead of re-creating the entire\r\nfile. In Vim, one can create a duplicate copy of the current buffer via\r\n:write {newfile} or :saveas {newfile}. But the former doesn't\r\nautomatically open the cloned file, whereas with the latter, you're losing the\r\nbuffer containing the original file. Also, the identical clone is immediately\r\npersisted, which may confuse automated build tools (or yourself, should you\r\nget interrupted and forget to make the actual modifications). Transferring the\r\nbuffer contents via :yank is also cumbersome and clobbers a register.\r\n\r\nThis plugin offers a :CloneAs command that duplicates the current buffer (or\r\nonly parts of it) without persisting the clone right away (only on :w), and\r\nkeeping the original buffer loaded and unmodified inside Vim (with\r\n:SCloneAs, it'll even be kept displayed in a window).\r\n\r\nOftentimes, duplication in source code is a code smell. Please use this plugin\r\nresponsibly ;-)\r\n\r\nSEE ALSO\r\nThe cloneSimilar.vim plugin (vimscript #4897) adds additional command\r\nvariants powered by the EditSimilar.vim (vimscript #2544) plugin.\r\n\r\nUSAGE\r\n:[range]CloneAs {file}  Duplicate and edit the current buffer \/ specified\r\n                        lines with a new name, keep the existing one.\r\n:[range]SCloneAs {file} Duplicate and split the current buffer \/ specified\r\n                        lines with a new name, keep the existing one.\r\n\r\n                        The original cursor position \/ window view will be\r\n                        kept, as well as the 'fileformat', 'fileencoding' and\r\n                        'filetype' settings of the original buffer.","install_details":"INSTALLATION\r\nThis script is packaged as a vimball. If you have the \"gunzip\" decompressor\r\nin your PATH, simply edit the *.vmb.gz package in Vim; otherwise, decompress\r\nthe archive first, e.g. using WinZip. Inside Vim, install by sourcing the\r\nvimball or via the :UseVimball command.\r\n    vim clone*.vmb.gz\r\n    :so %\r\nTo uninstall, use the :RmVimball command.\r\n\r\nDEPENDENCIES\r\n- Requires Vim 7.0 or higher.\r\n- Requires the ingo-library.vim plugin (vimscript #4433), version 1.019 or\r\n  higher.\r\n\r\nCONFIGURATION\r\nFor a permanent configuration, put the following commands into your vimrc:\r\n\r\nThe :SCloneAs command uses the default 'splitbelow' behavior; you can\r\ninfluence this via:\r\n    let g:clone_splitmode = 'belowright'","5":"INSTALLATION\r\nThis script is packaged as a vimball. If you have the \"gunzip\" decompressor\r\nin your PATH, simply edit the *.vmb.gz package in Vim; otherwise, decompress\r\nthe archive first, e.g. using WinZip. Inside Vim, install by sourcing the\r\nvimball or via the :UseVimball command.\r\n    vim clone*.vmb.gz\r\n    :so %\r\nTo uninstall, use the :RmVimball command.\r\n\r\nDEPENDENCIES\r\n- Requires Vim 7.0 or higher.\r\n- Requires the ingo-library.vim plugin (vimscript #4433), version 1.019 or\r\n  higher.\r\n\r\nCONFIGURATION\r\nFor a permanent configuration, put the following commands into your vimrc:\r\n\r\nThe :SCloneAs command uses the default 'splitbelow' behavior; you can\r\ninfluence this via:\r\n    let g:clone_splitmode = 'belowright'","first_name":"Ingo","6":"Ingo","last_name":"Karkat","7":"Karkat","releases":[{"0":"4896","vim_version":"7.0","1":"7.0","script_version":"1.02","2":"1.02","version_comment":"- Avoid setting 'filetype' when it already has the value of the original buffer, because even that triggers FileType autocmds, and may result in disturbing duplicate messages.\r\n- Also handle unreadable files (and directories). *** You need to update to ingo-library (vimscript #4433) version 1.019! ***","3":"- Avoid setting 'filetype' when it already has the value of the original buffer, because even that triggers FileType autocmds, and may result in disturbing duplicate messages.\r\n- Also handle unreadable files (and directories). *** You need to update to ingo-library (vimscript #4433) version 1.019! ***","package":"clone-1.02.vmb.gz","4":"clone-1.02.vmb.gz","src_id":"22063","5":"22063","creation_date":"1403204822","6":"1403204822"},{"0":"4896","vim_version":"7.0","1":"7.0","script_version":"1.01","2":"1.01","version_comment":"- Allow cloning into unloaded buffer.\r\n- Suppress BufNewFile event, and instead emit the more appropriate BufRead event for the clone buffer.","3":"- Allow cloning into unloaded buffer.\r\n- Suppress BufNewFile event, and instead emit the more appropriate BufRead event for the clone buffer.","package":"clone-1.01.vmb.gz","4":"clone-1.01.vmb.gz","src_id":"21827","5":"21827","creation_date":"1398434228","6":"1398434228"},{"0":"4896","vim_version":"7.0","1":"7.0","script_version":"1.00","2":"1.00","version_comment":"Initial upload","3":"Initial upload","package":"clone-1.00.vmb.gz","4":"clone-1.00.vmb.gz","src_id":"21633","5":"21633","creation_date":"1395151812","6":"1395151812"}]},"4895":{"script_id":"4895","0":"4895","script_name":"Pterosaur","1":"Pterosaur","script_type":"utility","2":"utility","summary":"Makes firefox text-inputs use vim.","3":"Makes firefox text-inputs use vim.","description":"Pterosaur lets you edit Firefox textfields using your actual Vim, vimrc, and vim plugins. (Not in a seperate window. Type vim keys directly into the textfield)\r\n\r\nSee https:\/\/github.com\/ardagnir\/pterosaur for more information.","4":"Pterosaur lets you edit Firefox textfields using your actual Vim, vimrc, and vim plugins. (Not in a seperate window. Type vim keys directly into the textfield)\r\n\r\nSee https:\/\/github.com\/ardagnir\/pterosaur for more information.","install_details":"See https:\/\/github.com\/ardagnir\/pterosaur","5":"See https:\/\/github.com\/ardagnir\/pterosaur","first_name":"James","6":"James","last_name":"Kolb","7":"Kolb","releases":[{"0":"4895","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Tons of changes since 0.6. Do not use the old versions.\r\nMade into a firefox plugin. No longer requires pentadactyl.","3":"Tons of changes since 0.6. Do not use the old versions.\r\nMade into a firefox plugin. No longer requires pentadactyl.","package":"pterosaur.xpi","4":"pterosaur.xpi","src_id":"22910","5":"22910","creation_date":"1423805792","6":"1423805792"},{"0":"4895","vim_version":"7.0","1":"7.0","script_version":"0.6","2":"0.6","version_comment":"- Increased stability and compatability.\r\n\r\n- Better undo support.\r\n\r\n- Modelines for select, visual, and replace modes.\r\n\r\n- Better cleanup of created vim processes and files.\r\n\r\n- Added debug mode\r\n\r\n- Other assorted bugfixes\r\n\r\n- Better undo support.\r\n\r\n- Modelines for select, visual, and replace modes.\r\n\r\n- Better cleanup of created vim processes and files.\r\n\r\n- Added debug mode\r\n\r\n- Other assorted bugfixes","3":"- Increased stability and compatability.\r\n\r\n- Better undo support.\r\n\r\n- Modelines for select, visual, and replace modes.\r\n\r\n- Better cleanup of created vim processes and files.\r\n\r\n- Added debug mode\r\n\r\n- Other assorted bugfixes\r\n\r\n- Better undo support.\r\n\r\n- Modelines for select, visual, and replace modes.\r\n\r\n- Better cleanup of created vim processes and files.\r\n\r\n- Added debug mode\r\n\r\n- Other assorted bugfixes","package":"pterosaur.tar.gz","4":"pterosaur.tar.gz","src_id":"21904","5":"21904","creation_date":"1400466028","6":"1400466028"},{"0":"4895","vim_version":"7.0","1":"7.0","script_version":"0.5","2":"0.5","version_comment":"Lots of bugfixes.","3":"Lots of bugfixes.","package":"pterosaur.tar.gz","4":"pterosaur.tar.gz","src_id":"21838","5":"21838","creation_date":"1398722487","6":"1398722487"},{"0":"4895","vim_version":"7.0","1":"7.0","script_version":"0.4","2":"0.4","version_comment":"Added better commandline support and error display. Added escape key fixes. Fixed some other small bugs.\r\n\r\nThis version requires eventloop.vim.\r\n","3":"Added better commandline support and error display. Added escape key fixes. Fixed some other small bugs.\r\n\r\nThis version requires eventloop.vim.\r\n","package":"pterosaur.tar.gz","4":"pterosaur.tar.gz","src_id":"21806","5":"21806","creation_date":"1398127596","6":"1398127596"},{"0":"4895","vim_version":"7.0","1":"7.0","script_version":"0.2","2":"0.2","version_comment":"Added mouse support and bugfixes.","3":"Added mouse support and bugfixes.","package":"pterosaur.tar.gz","4":"pterosaur.tar.gz","src_id":"21662","5":"21662","creation_date":"1395699897","6":"1395699897"},{"0":"4895","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"pterosaur.tar.gz","4":"pterosaur.tar.gz","src_id":"21631","5":"21631","creation_date":"1395109693","6":"1395109693"}]},"4894":{"script_id":"4894","0":"4894","script_name":"Markology","1":"Markology","script_type":"utility","2":"utility","summary":"Mark Visualization, Navigation and Management","3":"Mark Visualization, Navigation and Management","description":"\r\nMarkology provides for the visualization, navigation, and management of Vim's\r\n(marks).  Visualization is through use of Vim's 'sign' feature, and so use of\r\nthis plugin requires that Vim be compiled with the 'sign' option.\r\n\r\nMarkology displays marks associated with the current line in the sign column or\r\ngutter of the window displaying the buffer (with the entire line highlighted\r\nin a different color, if so desired).  You can easily add ('\\m+'), delete\r\n('\\m-'), or toggle ('\\m,') marks associated with the current line.  You can\r\neasily jump through the sequence of all the local marks in the buffer, either\r\nspatially ('\\m]' and '\\m[') or lexicographically ('\\m}' and '\\m{').  You can\r\nalso easily display all current marks in the location list window ('\\m?') or\r\nthe quickfix window ('\\m~').\r\n\r\nDetailed usage description given in the help file, which can be viewed on-line\r\nhere:\r\n\r\n    http:\/\/github.com\/jeetsukumaran\/vim-markology\/blob\/master\/doc\/markology.txt\r\n\r\nSource code repository can be found here:\r\n\r\n    http:\/\/github.com\/jeetsukumaran\/vim-markology\r\n\r\nMarkology is a Frankenstein-ian beast that seamlessly amalgamates and\r\nstreamlines (the best) parts of:\r\n\r\n    1.  ShowMarks\r\n\r\n            ShowMarks - Visually show the location of marks\r\n            Version 2.2 (2004-08-06)\r\n            http:\/\/www.vim.org\/scripts\/script.php?script_id=152\r\n            By Anthony Kruize <trandor@labyrinth.net.au>\r\n            Michael Geddes <michaelrgeddes@optushome.com.au>\r\n\r\n    2.  The patch for the above, as given here:\r\n\r\n            http:\/\/easwy.com\/blog\/archives\/advanced-vim-skills-advanced-move-method\/\r\n\r\n        which fixes the issue of global marks showing up in files in which they\r\n        were *not* declared.\r\n\r\n    3. Mark_Tools\r\n\r\n            mark_tools : Toggle and navigate marks\r\n            Sergey Khorev <sergey.khorev@gmail.com>\r\n\r\n            http:\/\/www.vim.org\/scripts\/script.php?script_id=2929\r\n            https:\/\/bitbucket.org\/khorser\/vim-mark-tools\r\n            https:\/\/github.com\/khorser\/vim-mark-tools\r\n\r\nLike \"ShowMarks\", Markology provides visual representation of |marks| local to a\r\nbuffer by placing a |sign| in the leftmost column of the buffer indicating the\r\nlabel of the mark and its location.\r\n\r\nMarkology is activated by the |CursorHold| |autocommand| which is triggered\r\nevery |updatetime| milliseconds.  This is set to 4000(4 seconds) by default.\r\nIf this is too slow, setting it to a lower value will make it more responsive.\r\n\r\nLike \"Mark_Tools\", Markology provides commands and keymaps for navigating\r\nbetween |marks| and listing\/viewing  |marks| .\r\n\r\nNote: This plugin requires Vim 6.x compiled with the |+signs| feature.\r\n","4":"\r\nMarkology provides for the visualization, navigation, and management of Vim's\r\n(marks).  Visualization is through use of Vim's 'sign' feature, and so use of\r\nthis plugin requires that Vim be compiled with the 'sign' option.\r\n\r\nMarkology displays marks associated with the current line in the sign column or\r\ngutter of the window displaying the buffer (with the entire line highlighted\r\nin a different color, if so desired).  You can easily add ('\\m+'), delete\r\n('\\m-'), or toggle ('\\m,') marks associated with the current line.  You can\r\neasily jump through the sequence of all the local marks in the buffer, either\r\nspatially ('\\m]' and '\\m[') or lexicographically ('\\m}' and '\\m{').  You can\r\nalso easily display all current marks in the location list window ('\\m?') or\r\nthe quickfix window ('\\m~').\r\n\r\nDetailed usage description given in the help file, which can be viewed on-line\r\nhere:\r\n\r\n    http:\/\/github.com\/jeetsukumaran\/vim-markology\/blob\/master\/doc\/markology.txt\r\n\r\nSource code repository can be found here:\r\n\r\n    http:\/\/github.com\/jeetsukumaran\/vim-markology\r\n\r\nMarkology is a Frankenstein-ian beast that seamlessly amalgamates and\r\nstreamlines (the best) parts of:\r\n\r\n    1.  ShowMarks\r\n\r\n            ShowMarks - Visually show the location of marks\r\n            Version 2.2 (2004-08-06)\r\n            http:\/\/www.vim.org\/scripts\/script.php?script_id=152\r\n            By Anthony Kruize <trandor@labyrinth.net.au>\r\n            Michael Geddes <michaelrgeddes@optushome.com.au>\r\n\r\n    2.  The patch for the above, as given here:\r\n\r\n            http:\/\/easwy.com\/blog\/archives\/advanced-vim-skills-advanced-move-method\/\r\n\r\n        which fixes the issue of global marks showing up in files in which they\r\n        were *not* declared.\r\n\r\n    3. Mark_Tools\r\n\r\n            mark_tools : Toggle and navigate marks\r\n            Sergey Khorev <sergey.khorev@gmail.com>\r\n\r\n            http:\/\/www.vim.org\/scripts\/script.php?script_id=2929\r\n            https:\/\/bitbucket.org\/khorser\/vim-mark-tools\r\n            https:\/\/github.com\/khorser\/vim-mark-tools\r\n\r\nLike \"ShowMarks\", Markology provides visual representation of |marks| local to a\r\nbuffer by placing a |sign| in the leftmost column of the buffer indicating the\r\nlabel of the mark and its location.\r\n\r\nMarkology is activated by the |CursorHold| |autocommand| which is triggered\r\nevery |updatetime| milliseconds.  This is set to 4000(4 seconds) by default.\r\nIf this is too slow, setting it to a lower value will make it more responsive.\r\n\r\nLike \"Mark_Tools\", Markology provides commands and keymaps for navigating\r\nbetween |marks| and listing\/viewing  |marks| .\r\n\r\nNote: This plugin requires Vim 6.x compiled with the |+signs| feature.\r\n","install_details":"Recommended: using a package manager like Pathogen (http:\/\/www.vim.org\/scripts\/script.php?script_id=2332):\r\n\r\n  $ cd ~\/.vim\/bundle\r\n  $ git clone http:\/\/github.com\/jeetsukumaran\/vim-markology\r\n\r\nOtherwise, download and extract the archive below to '~\/.vim' (or '~\\vimfiles'  on Windows).","5":"Recommended: using a package manager like Pathogen (http:\/\/www.vim.org\/scripts\/script.php?script_id=2332):\r\n\r\n  $ cd ~\/.vim\/bundle\r\n  $ git clone http:\/\/github.com\/jeetsukumaran\/vim-markology\r\n\r\nOtherwise, download and extract the archive below to '~\/.vim' (or '~\\vimfiles'  on Windows).","first_name":"Jeet","6":"Jeet","last_name":"Sukumaran","7":"Sukumaran","releases":[{"0":"4894","vim_version":"7.0","1":"7.0","script_version":"2.0.0","2":"2.0.0","version_comment":"- Complete split and reorganization of code into separate `autoload\/` and `plugin\/` modules\r\n- Default key maps now use direct `m` trigger instead of `<Leader>m` (fully-configurable, from no mapping at all, to old `<Leader>m` style maps, to new and sleek `m` maps)\r\n- Easily toggle highlighting of marked lines\r\n- Remove old signs for marks that are doubled up (Benjamin Thomas)\r\n- Use noremap instead of map to avoid space mapping issues\r\n- Added option to disable default key-mapping entirely (Jonathan Geddes)\r\n- Correctly show marks on first line\r\n- Correctly behavior to avoid complaints due to Vim patch 7.4.275","3":"- Complete split and reorganization of code into separate `autoload\/` and `plugin\/` modules\r\n- Default key maps now use direct `m` trigger instead of `<Leader>m` (fully-configurable, from no mapping at all, to old `<Leader>m` style maps, to new and sleek `m` maps)\r\n- Easily toggle highlighting of marked lines\r\n- Remove old signs for marks that are doubled up (Benjamin Thomas)\r\n- Use noremap instead of map to avoid space mapping issues\r\n- Added option to disable default key-mapping entirely (Jonathan Geddes)\r\n- Correctly show marks on first line\r\n- Correctly behavior to avoid complaints due to Vim patch 7.4.275","package":"vim-markology-v2.0.0.tar.gz","4":"vim-markology-v2.0.0.tar.gz","src_id":"21910","5":"21910","creation_date":"1400642870","6":"1400642870"},{"0":"4894","vim_version":"7.0","1":"7.0","script_version":"1.0.0","2":"1.0.0","version_comment":"Initial upload","3":"Initial upload","package":"vim-markology-1.0.0.tar.gz","4":"vim-markology-1.0.0.tar.gz","src_id":"21628","5":"21628","creation_date":"1395073856","6":"1395073856"}]},"4893":{"script_id":"4893","0":"4893","script_name":"vim-bookmarks","1":"vim-bookmarks","script_type":"utility","2":"utility","summary":"bookmark and annotate lines of code","3":"bookmark and annotate lines of code","description":"This vim plugin allows toggling bookmarks per line. A quickfix window gives access to all bookmarks. Annotations can be added as well. These are special bookmarks with a comment attached. They are useful for preparing code reviews. All bookmarks will be restored on the next startup.\r\n\r\nScreenshot:\r\nhttps:\/\/raw.githubusercontent.com\/MattesGroeger\/vim-bookmarks\/master\/preview.gif\r\n\r\nFeatures:\r\n* Toggle bookmarks per line ⚑\r\n* Add annotations per line ☰\r\n* Navigate all bookmarks with quickfix window\r\n* Bookmarks will be restored on next startup\r\n* Bookmarks per working directory (optional)\r\n* Fully customisable (signs, sign column, highlights, mappings)\r\n* Integrates with Unite's quickfix source if installed\r\n* Works independently from vim marks\r\n\r\nMore details on GitHub:\r\nhttps:\/\/github.com\/MattesGroeger\/vim-bookmarks","4":"This vim plugin allows toggling bookmarks per line. A quickfix window gives access to all bookmarks. Annotations can be added as well. These are special bookmarks with a comment attached. They are useful for preparing code reviews. All bookmarks will be restored on the next startup.\r\n\r\nScreenshot:\r\nhttps:\/\/raw.githubusercontent.com\/MattesGroeger\/vim-bookmarks\/master\/preview.gif\r\n\r\nFeatures:\r\n* Toggle bookmarks per line ⚑\r\n* Add annotations per line ☰\r\n* Navigate all bookmarks with quickfix window\r\n* Bookmarks will be restored on next startup\r\n* Bookmarks per working directory (optional)\r\n* Fully customisable (signs, sign column, highlights, mappings)\r\n* Integrates with Unite's quickfix source if installed\r\n* Works independently from vim marks\r\n\r\nMore details on GitHub:\r\nhttps:\/\/github.com\/MattesGroeger\/vim-bookmarks","install_details":"Use your favorite plugin manager:\r\n\r\nPathogen\r\ngit clone https:\/\/github.com\/MattesGroeger\/vim-bookmarks.git ~\/.vim\/bundle\/vim-bookmarks\r\n\r\nVundle\r\n1. Add Plugin 'MattesGroeger\/vim-bookmarks' to .vimrc\r\n2. Run :PluginInstall\r\n\r\nNeoBundle\r\n1. Add NeoBundle 'MattesGroeger\/vim-bookmarks' to .vimrc\r\n2. Run :NeoBundleInstall\r\n\r\nvim-plug\r\n1. Add Plug 'MattesGroeger\/vim-bookmarks' to .vimrc\r\n2. Run :PlugInstall","5":"Use your favorite plugin manager:\r\n\r\nPathogen\r\ngit clone https:\/\/github.com\/MattesGroeger\/vim-bookmarks.git ~\/.vim\/bundle\/vim-bookmarks\r\n\r\nVundle\r\n1. Add Plugin 'MattesGroeger\/vim-bookmarks' to .vimrc\r\n2. Run :PluginInstall\r\n\r\nNeoBundle\r\n1. Add NeoBundle 'MattesGroeger\/vim-bookmarks' to .vimrc\r\n2. Run :NeoBundleInstall\r\n\r\nvim-plug\r\n1. Add Plug 'MattesGroeger\/vim-bookmarks' to .vimrc\r\n2. Run :PlugInstall","first_name":"Mattes","6":"Mattes","last_name":"Dev","7":"Dev","releases":[{"0":"4893","vim_version":"7.0","1":"7.0","script_version":"1.3.0","2":"1.3.0","version_comment":" * [feature] Store bookmarks per project #54\r\n * [enhancement] Integration with Unite, if installed #56","3":" * [feature] Store bookmarks per project #54\r\n * [enhancement] Integration with Unite, if installed #56","package":"vim-bookmarks-1.3.0.zip","4":"vim-bookmarks-1.3.0.zip","src_id":"22395","5":"22395","creation_date":"1409511317","6":"1409511317"},{"0":"4893","vim_version":"7.0","1":"7.0","script_version":"1.2.0","2":"1.2.0","version_comment":" * [feature] Automatically close bookmarks' quickfix split. #45\r\n * [enhancement] Shortcut `ma` should be a toggle #51\r\n * [enhancement] Consistently named Commands #49\r\n * [enhancement] Silent loading and saving of bookmarks (for extensions) #46\r\n * [enhancement] Better positioning of \"show all bookmarks\" window #41\r\n * [bugfix] Single quotation mark in annotation causes loss of saved bookmarks #53\r\n * [bugfix] Unprinted signs at file loading #40","3":" * [feature] Automatically close bookmarks' quickfix split. #45\r\n * [enhancement] Shortcut `ma` should be a toggle #51\r\n * [enhancement] Consistently named Commands #49\r\n * [enhancement] Silent loading and saving of bookmarks (for extensions) #46\r\n * [enhancement] Better positioning of \"show all bookmarks\" window #41\r\n * [bugfix] Single quotation mark in annotation causes loss of saved bookmarks #53\r\n * [bugfix] Unprinted signs at file loading #40","package":"vim-bookmarks-1.2.0.zip","4":"vim-bookmarks-1.2.0.zip","src_id":"22260","5":"22260","creation_date":"1406290836","6":"1406290836"},{"0":"4893","vim_version":"7.0","1":"7.0","script_version":"1.1.0","2":"1.1.0","version_comment":" * [enhancement] Center bookmarks when jumping to them #37\r\n * [bugfix] Should not show error on invalid buffers #39","3":" * [enhancement] Center bookmarks when jumping to them #37\r\n * [bugfix] Should not show error on invalid buffers #39","package":"vim-bookmarks-1.1.0.zip","4":"vim-bookmarks-1.1.0.zip","src_id":"21857","5":"21857","creation_date":"1399187590","6":"1399187590"},{"0":"4893","vim_version":"7.0","1":"7.0","script_version":"1.0.0","2":"1.0.0","version_comment":" * [feature] Allow saving\/loading bookmarks from\/to file #31\r\n * [feature] Support text annotations #29\r\n * [feature] Delete bookmarks in all buffers #24\r\n * [feature] Persist bookmarks automatically #5\r\n * [enhancement] Sort files in quickfix list alphabetically #26\r\n * [enhancement] Don't jump to first bookmark when opening quickfix window #18\r\n * [bugfix] Adding bookmark in new\/unsaved buffer fails #30\r\n * [bugfix] Bookmarks on empty lines show up wrong in quickfix window #25","3":" * [feature] Allow saving\/loading bookmarks from\/to file #31\r\n * [feature] Support text annotations #29\r\n * [feature] Delete bookmarks in all buffers #24\r\n * [feature] Persist bookmarks automatically #5\r\n * [enhancement] Sort files in quickfix list alphabetically #26\r\n * [enhancement] Don't jump to first bookmark when opening quickfix window #18\r\n * [bugfix] Adding bookmark in new\/unsaved buffer fails #30\r\n * [bugfix] Bookmarks on empty lines show up wrong in quickfix window #25","package":"vim-bookmarks-1.0.0.zip","4":"vim-bookmarks-1.0.0.zip","src_id":"21739","5":"21739","creation_date":"1396717675","6":"1396717675"},{"0":"4893","vim_version":"7.0","1":"7.0","script_version":"0.2.0","2":"0.2.0","version_comment":" * [feature] Jump to first non-blank character in line\r\n * [enhancement] Load sub-script(s) only if bookmarks are used\r\n * [enhancement] Improve load times\r\n * [bug] Allow editing files without breaking bookmark jumps\r\n * [bug] Line preview in quickfix window doesn't work for closed\/previous buffer","3":" * [feature] Jump to first non-blank character in line\r\n * [enhancement] Load sub-script(s) only if bookmarks are used\r\n * [enhancement] Improve load times\r\n * [bug] Allow editing files without breaking bookmark jumps\r\n * [bug] Line preview in quickfix window doesn't work for closed\/previous buffer","package":"vim-bookmarks-0.2.0.zip","4":"vim-bookmarks-0.2.0.zip","src_id":"21653","5":"21653","creation_date":"1395593044","6":"1395593044"},{"0":"4893","vim_version":"7.0","1":"7.0","script_version":"0.1.0","2":"0.1.0","version_comment":"Initial upload","3":"Initial upload","package":"vim-bookmarks-0.1.0.zip","4":"vim-bookmarks-0.1.0.zip","src_id":"21625","5":"21625","creation_date":"1395005660","6":"1395005660"}]},"4892":{"script_id":"4892","0":"4892","script_name":"vim-less","1":"vim-less","script_type":"syntax","2":"syntax","summary":"Less syntax highlighting","3":"Less syntax highlighting","description":"Tim Pope vim-haml fork to highlight Less syntax correctly.\r\n\r\nFor the syntax files to work correctly you need to install the latest CSS runtime files from Jules Wang repository https:\/\/github.com\/JulesWang\/css.vim\r\n\r\nUpdated version on https:\/\/github.com\/genoma\/vim-less","4":"Tim Pope vim-haml fork to highlight Less syntax correctly.\r\n\r\nFor the syntax files to work correctly you need to install the latest CSS runtime files from Jules Wang repository https:\/\/github.com\/JulesWang\/css.vim\r\n\r\nUpdated version on https:\/\/github.com\/genoma\/vim-less","install_details":"Using Vundle, add this to your .vimrc file:\r\nBundle 'genoma\/vim-less'\r\n\r\nUsing Pathogen clone this repository in '~\/.vim\/bundle':\r\n$ cd ~\/.vim\/bundle $ git clone https:\/\/github.com\/genoma\/vim-less.git","5":"Using Vundle, add this to your .vimrc file:\r\nBundle 'genoma\/vim-less'\r\n\r\nUsing Pathogen clone this repository in '~\/.vim\/bundle':\r\n$ cd ~\/.vim\/bundle $ git clone https:\/\/github.com\/genoma\/vim-less.git","first_name":"Alessandro","6":"Alessandro","last_name":"Vioni","7":"Vioni","releases":[{"0":"4892","vim_version":"7.4","1":"7.4","script_version":"2.11","2":"2.11","version_comment":"Changed license from MIT to Vim license.","3":"Changed license from MIT to Vim license.","package":"vim-less.zip","4":"vim-less.zip","src_id":"22641","5":"22641","creation_date":"1416866606","6":"1416866606"},{"0":"4892","vim_version":"7.4","1":"7.4","script_version":"2.0","2":"2.0","version_comment":"Cleaned up code and commented.\r\n\r\nFor the syntax files to work correctly you need to install the latest CSS runtime files from Jules Wang repository: https:\/\/github.com\/JulesWang\/css.vim","3":"Cleaned up code and commented.\r\n\r\nFor the syntax files to work correctly you need to install the latest CSS runtime files from Jules Wang repository: https:\/\/github.com\/JulesWang\/css.vim","package":"vim-less.zip","4":"vim-less.zip","src_id":"22579","5":"22579","creation_date":"1414569300","6":"1414569300"},{"0":"4892","vim_version":"7.4","1":"7.4","script_version":"1.55","2":"1.55","version_comment":"Fixed Less function highlighting","3":"Fixed Less function highlighting","package":"vim-less.zip","4":"vim-less.zip","src_id":"22316","5":"22316","creation_date":"1407838234","6":"1407838234"},{"0":"4892","vim_version":"7.4","1":"7.4","script_version":"1.50","2":"1.50","version_comment":"Cleaned code and fixes","3":"Cleaned code and fixes","package":"vim-less.zip","4":"vim-less.zip","src_id":"22157","5":"22157","creation_date":"1404748862","6":"1404748862"},{"0":"4892","vim_version":"7.4","1":"7.4","script_version":"1.42","2":"1.42","version_comment":"More fixes:\r\n  - @media queries are correctly highlighted\r\n  - added lessTagName and lessDeprecated","3":"More fixes:\r\n  - @media queries are correctly highlighted\r\n  - added lessTagName and lessDeprecated","package":"vim-less.zip","4":"vim-less.zip","src_id":"22154","5":"22154","creation_date":"1404734279","6":"1404734279"},{"0":"4892","vim_version":"7.4","1":"7.4","script_version":"1.4","2":"1.4","version_comment":"Version 1.4 remove a couple of highlight errors with a temporary fix (removed cssDeprecated).\r\n\r\nReport errors or contribute https:\/\/github.com\/genoma\/vim-less\r\n","3":"Version 1.4 remove a couple of highlight errors with a temporary fix (removed cssDeprecated).\r\n\r\nReport errors or contribute https:\/\/github.com\/genoma\/vim-less\r\n","package":"vim-less.zip","4":"vim-less.zip","src_id":"22153","5":"22153","creation_date":"1404728976","6":"1404728976"},{"0":"4892","vim_version":"7.4","1":"7.4","script_version":"1.35","2":"1.35","version_comment":"Bunch of bugfixes, now ampersand and classes, id's should be highlighted coorectly.","3":"Bunch of bugfixes, now ampersand and classes, id's should be highlighted coorectly.","package":"vim-less.zip","4":"vim-less.zip","src_id":"22152","5":"22152","creation_date":"1404725919","6":"1404725919"},{"0":"4892","vim_version":"7.4","1":"7.4","script_version":"1.33","2":"1.33","version_comment":"Updated README.md","3":"Updated README.md","package":"vim-less.zip","4":"vim-less.zip","src_id":"22150","5":"22150","creation_date":"1404721432","6":"1404721432"},{"0":"4892","vim_version":"7.4","1":"7.4","script_version":"1.32","2":"1.32","version_comment":"More fixes","3":"More fixes","package":"vim-less.zip","4":"vim-less.zip","src_id":"22128","5":"22128","creation_date":"1404403121","6":"1404403121"},{"0":"4892","vim_version":"7.4","1":"7.4","script_version":"1.31","2":"1.31","version_comment":"Small highlighting fixes","3":"Small highlighting fixes","package":"vim-less.zip","4":"vim-less.zip","src_id":"22126","5":"22126","creation_date":"1404399233","6":"1404399233"},{"0":"4892","vim_version":"7.0","1":"7.0","script_version":"1.2","2":"1.2","version_comment":"Small fixes","3":"Small fixes","package":"vim-less.zip","4":"vim-less.zip","src_id":"22117","5":"22117","creation_date":"1404299736","6":"1404299736"},{"0":"4892","vim_version":"7.0","1":"7.0","script_version":"1.1","2":"1.1","version_comment":"Cleaned code and fixed a bunch of glaring errors.","3":"Cleaned code and fixed a bunch of glaring errors.","package":"vim-less.zip","4":"vim-less.zip","src_id":"21638","5":"21638","creation_date":"1395178081","6":"1395178081"},{"0":"4892","vim_version":"7.3","1":"7.3","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"vim-less.zip","4":"vim-less.zip","src_id":"21624","5":"21624","creation_date":"1395002481","6":"1395002481"}]},"4891":{"script_id":"4891","0":"4891","script_name":"nomad","1":"nomad","script_type":"utility","2":"utility","summary":"Keep your environment variables in sync with tmux","3":"Keep your environment variables in sync with tmux","description":"Using Vim in a remote tmux session is very convenient, because you can detach the running session and resume it later without leaving Vim. This is great in situations where you login with ssh into your development machine at work or your server to continue coding after you changed your location. But suddenly, when you try to access a git+ssh remote (maybe through tpope's excellent fugitive plugin) or access the quotestar or quoteplus registers, things won't work as expected because with a new ssh connection some of your environment variables changed and Vim doesn't know about it. Fortunately tmux knows about these changes and this is where the nomad plugin kicks in. It queries tmux for the new values and updates your environment in Vim.","4":"Using Vim in a remote tmux session is very convenient, because you can detach the running session and resume it later without leaving Vim. This is great in situations where you login with ssh into your development machine at work or your server to continue coding after you changed your location. But suddenly, when you try to access a git+ssh remote (maybe through tpope's excellent fugitive plugin) or access the quotestar or quoteplus registers, things won't work as expected because with a new ssh connection some of your environment variables changed and Vim doesn't know about it. Fortunately tmux knows about these changes and this is where the nomad plugin kicks in. It queries tmux for the new values and updates your environment in Vim.","install_details":"If you don't have a preferred installation method, I recommend installing pathogen.vim, and then simply copy and paste:\r\n\r\ncd ~\/.vim\/bundle git clone git:\/\/github.com\/buztard\/vim-nomad.git\r\n\r\nOr for Vundle users:\r\n\r\nAdd Bundle 'buztard\/vim-nomad' to your ~\/.vimrc and then:\r\n\r\n    either within Vim: :BundleInstall\r\n    or in your shell: vim +BundleInstall +qall\r\n","5":"If you don't have a preferred installation method, I recommend installing pathogen.vim, and then simply copy and paste:\r\n\r\ncd ~\/.vim\/bundle git clone git:\/\/github.com\/buztard\/vim-nomad.git\r\n\r\nOr for Vundle users:\r\n\r\nAdd Bundle 'buztard\/vim-nomad' to your ~\/.vimrc and then:\r\n\r\n    either within Vim: :BundleInstall\r\n    or in your shell: vim +BundleInstall +qall\r\n","first_name":"Bastian","6":"Bastian","last_name":"Winkler","7":"Winkler","releases":[{"0":"4891","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"vim-nomad.tar.gz","4":"vim-nomad.tar.gz","src_id":"21623","5":"21623","creation_date":"1394991192","6":"1394991192"}]},"4890":{"script_id":"4890","0":"4890","script_name":"quickfix-reflector.vim","1":"quickfix-reflector.vim","script_type":"utility","2":"utility","summary":"Change code right in the quickfix window","3":"Change code right in the quickfix window","description":"Usage\r\n=====\r\n\r\nIn the quickfix window, simply edit any entry you like. Once you save the quickfix buffer, your changes will be made in the actual file an entry points to.\r\n\r\nYou can also delete lines in the quickfix window. This way, you can first review the quickfix list, remove all entries you don't care to change, and then use `%s\/foo\/bar` (or anything else) on the rest.\r\n\r\n\r\nDetails\r\n=======\r\n\r\n* Works in location list windows, too\r\n* The quickfix buffer is now `modifiable`\r\n* The usual write commands can be used (`:w`, `:x` etc.), but they won't save the buffer to a file. Instead they will trigger replacement for any changes you made.\r\n* If you specifically want to save the quickfix buffer to a file, you can still do that the same way as before `:write my_qf_list`\r\n* Adding and removing lines in the quickfix buffer breaks each line's link to Vim's internal quickfix entry. After making such changes, you need to write the quickfix buffer. This will rewrite Vim's internal quickfix list. Otherwise, pressing `<Enter>` may jump to the wrong entry.\r\n\r\n\r\nLimits to text replacement\r\n==========================\r\n\r\nWhenever a replacement fails, you get an '[ERROR]' in the corresponding quickfix entry.\r\n\r\nReplacement only works if the text that was modified actually exists in the corresponding text file and line number. So it may fail if the file was modified since the quickfix list was built.\r\n\r\nIf the quickfix entry contains only part of a line, replacement should work as long as there is a substring of that line with at least three characters.\r\n\r\nExample: The quickfix entry `Missing ; at: xyz` can be used to replace in a line `a = xyz`. However, it cannot be used in a line `xyz = 1+xyz` because it is not clear which xyz would need to be replaced\r\n\r\n\r\nLinks\r\n=====\r\n\r\nhttps:\/\/github.com\/stefandtw\/quickfix-reflector.vim","4":"Usage\r\n=====\r\n\r\nIn the quickfix window, simply edit any entry you like. Once you save the quickfix buffer, your changes will be made in the actual file an entry points to.\r\n\r\nYou can also delete lines in the quickfix window. This way, you can first review the quickfix list, remove all entries you don't care to change, and then use `%s\/foo\/bar` (or anything else) on the rest.\r\n\r\n\r\nDetails\r\n=======\r\n\r\n* Works in location list windows, too\r\n* The quickfix buffer is now `modifiable`\r\n* The usual write commands can be used (`:w`, `:x` etc.), but they won't save the buffer to a file. Instead they will trigger replacement for any changes you made.\r\n* If you specifically want to save the quickfix buffer to a file, you can still do that the same way as before `:write my_qf_list`\r\n* Adding and removing lines in the quickfix buffer breaks each line's link to Vim's internal quickfix entry. After making such changes, you need to write the quickfix buffer. This will rewrite Vim's internal quickfix list. Otherwise, pressing `<Enter>` may jump to the wrong entry.\r\n\r\n\r\nLimits to text replacement\r\n==========================\r\n\r\nWhenever a replacement fails, you get an '[ERROR]' in the corresponding quickfix entry.\r\n\r\nReplacement only works if the text that was modified actually exists in the corresponding text file and line number. So it may fail if the file was modified since the quickfix list was built.\r\n\r\nIf the quickfix entry contains only part of a line, replacement should work as long as there is a substring of that line with at least three characters.\r\n\r\nExample: The quickfix entry `Missing ; at: xyz` can be used to replace in a line `a = xyz`. However, it cannot be used in a line `xyz = 1+xyz` because it is not clear which xyz would need to be replaced\r\n\r\n\r\nLinks\r\n=====\r\n\r\nhttps:\/\/github.com\/stefandtw\/quickfix-reflector.vim","install_details":"Copy the contents of the plugin and doc directories into the corresponding directories of your Vim runtime.\r\nAlternatively, use Vundle, Pathogen etc. to make the installation easier.","5":"Copy the contents of the plugin and doc directories into the corresponding directories of your Vim runtime.\r\nAlternatively, use Vundle, Pathogen etc. to make the installation easier.","first_name":"Stefan","6":"Stefan","last_name":"Dotterweich","7":"Dotterweich","releases":[{"0":"4890","vim_version":"7.4","1":"7.4","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"quickfix-reflector.zip","4":"quickfix-reflector.zip","src_id":"21620","5":"21620","creation_date":"1394977156","6":"1394977156"}]},"4889":{"script_id":"4889","0":"4889","script_name":"likelycomplete","1":"likelycomplete","script_type":"utility","2":"utility","summary":"Collect & rank words for completion","3":"Collect & rank words for completion","description":"Once enabled for a filetype (see |g:likelycomplete_filetypes|), this \r\nplugin observes any buffer of that filetype. It collects the words, \r\nranks them based on the probability of their occurrences (sort of) and \r\ncompiles a dictionary file that is fed to 'complete'. Any words that are \r\nfrequently used in files of enabled filetypes, are offered in the \r\ncompletion list (see |i_CTRL-P|). The plugin also supports Insert mode \r\ncompletion (see 'completefunc') that optionally takes into account the cursor's \r\ncontext.\r\n\r\nThe word list on disk is updated when leaving vim. It could take a few \r\nediting sessions to get at a usable word list.\r\n\r\nFeatues:\r\n\r\n    - Generate word lists for use in 'complete' (see also |ins-completion| and \r\n      |i_CTRL-P|)\r\n    - Set a 'completefunc' (incorporate results from the original \r\n      'completefunc' and optionally from 'omnifunc') -- see \r\n      |g:likelycomplete#set_completefunc|\r\n\r\nAdditional featues for use as 'completefunc':\r\n\r\n    - Auto-completion -- see |g:likelycomplete#auto_complete|\r\n    - Fuzzy completion -- see |g:likelycomplete#use_fuzzy_matches|\r\n    - Part of word completion -- see |g:likelycomplete#match_beginning|\r\n    - Context based sorting (not available for |i_CTRL-P|) -- see \r\n      |g:likelycomplete#assess_context|\r\n    - If finding the right completion via VIM's own popup menu is too \r\n      cumbersome, press <C-S-Space> -- see |g:likelycomplete#select_imap|\r\n\r\nBy default only completion via |i_CTRL-P| is enabled (and only for those \r\nfiletypes listed in |g:likelycomplete_filetypes|). Most of the above options \r\ncan be enabled by setting |g:likelycomplete#experimental| to 1.\r\n","4":"Once enabled for a filetype (see |g:likelycomplete_filetypes|), this \r\nplugin observes any buffer of that filetype. It collects the words, \r\nranks them based on the probability of their occurrences (sort of) and \r\ncompiles a dictionary file that is fed to 'complete'. Any words that are \r\nfrequently used in files of enabled filetypes, are offered in the \r\ncompletion list (see |i_CTRL-P|). The plugin also supports Insert mode \r\ncompletion (see 'completefunc') that optionally takes into account the cursor's \r\ncontext.\r\n\r\nThe word list on disk is updated when leaving vim. It could take a few \r\nediting sessions to get at a usable word list.\r\n\r\nFeatues:\r\n\r\n    - Generate word lists for use in 'complete' (see also |ins-completion| and \r\n      |i_CTRL-P|)\r\n    - Set a 'completefunc' (incorporate results from the original \r\n      'completefunc' and optionally from 'omnifunc') -- see \r\n      |g:likelycomplete#set_completefunc|\r\n\r\nAdditional featues for use as 'completefunc':\r\n\r\n    - Auto-completion -- see |g:likelycomplete#auto_complete|\r\n    - Fuzzy completion -- see |g:likelycomplete#use_fuzzy_matches|\r\n    - Part of word completion -- see |g:likelycomplete#match_beginning|\r\n    - Context based sorting (not available for |i_CTRL-P|) -- see \r\n      |g:likelycomplete#assess_context|\r\n    - If finding the right completion via VIM's own popup menu is too \r\n      cumbersome, press <C-S-Space> -- see |g:likelycomplete#select_imap|\r\n\r\nBy default only completion via |i_CTRL-P| is enabled (and only for those \r\nfiletypes listed in |g:likelycomplete_filetypes|). Most of the above options \r\ncan be enabled by setting |g:likelycomplete#experimental| to 1.\r\n","install_details":"In order to install the vba, open the vba file in VIM and type: >\r\n\r\n    :so %\r\n\r\nSee :help vimball for details.\r\n\r\nThis script requires tlib (vimscript #1863) to be installed.\r\n\r\nAlso available via git: http:\/\/github.com\/tomtom\/likelycomplete_vim\/\r\n\r\n\r\nPost-Install~\r\n\r\nUsers have to set |g:likelycomplete_filetypes| in |vimrc| in order to enable \r\nLikelyComplete for certain filetypes.\r\n","5":"In order to install the vba, open the vba file in VIM and type: >\r\n\r\n    :so %\r\n\r\nSee :help vimball for details.\r\n\r\nThis script requires tlib (vimscript #1863) to be installed.\r\n\r\nAlso available via git: http:\/\/github.com\/tomtom\/likelycomplete_vim\/\r\n\r\n\r\nPost-Install~\r\n\r\nUsers have to set |g:likelycomplete_filetypes| in |vimrc| in order to enable \r\nLikelyComplete for certain filetypes.\r\n","first_name":"Tom","6":"Tom","last_name":"Link","7":"Link","releases":[{"0":"4889","vim_version":"7.0","1":"7.0","script_version":"0.04","2":"0.04","version_comment":"- GetWordsSortedByRelevance(): Minor change to weighting len(base)\/len(word)\n- GetCompletions: Filter list ASAP in order to reduce runtime of tlib#list#Uniq(); fix s:Readlines: return copy of lines\nMD5 checksum: 8e0bd638cd179e37c391ab1802752ed4","3":"- GetWordsSortedByRelevance(): Minor change to weighting len(base)\/len(word)\n- GetCompletions: Filter list ASAP in order to reduce runtime of tlib#list#Uniq(); fix s:Readlines: return copy of lines\nMD5 checksum: 8e0bd638cd179e37c391ab1802752ed4","package":"likelycomplete.vba","4":"likelycomplete.vba","src_id":"21678","5":"21678","creation_date":"1395949188","6":"1395949188"},{"0":"4889","vim_version":"7.0","1":"7.0","script_version":"0.03","2":"0.03","version_comment":"- g:likelycomplete#prgname: Prefer vim if available\n- likelycomplete#AsyncUpdateWordList(), s:UpdateWordList(): Escape special characters only on exec\n- g:likelycomplete#base_context, g:likelycomplete#max_context\n- Always insert base when called via <c-x><c-u>; remove dbg\/log comments\n- Call UpdateWordList() on BufDelete, not BufUnload\n- Debugging, s:Run()\n- g:likelycomplete#sources: Define source & order; g:likelycomplete#dictionaries: define dictionaries\n- g:likelycomplete_per_window: per-window filetypes (not yet functional)\n- Don't update word list when using w:likelycomplete_filetype\n- Make sure not to update wordlist if sources don't include 'likelycomplete'\n- FIX variable scope\n- SetupComplete(): Add dictionaries to &complete and &dictionary\n- Use \"_\" if filetype is empty; actually test likelycomplete#SetupFiletype()\n- Renamed 'dict' to 'dictionaries'; support for including 'dictionary'\n- g:likelycomplete#sources: Remove \"?files\"\nMD5 checksum: c633c39845d8e2869ea26fb4cbe9561a","3":"- g:likelycomplete#prgname: Prefer vim if available\n- likelycomplete#AsyncUpdateWordList(), s:UpdateWordList(): Escape special characters only on exec\n- g:likelycomplete#base_context, g:likelycomplete#max_context\n- Always insert base when called via <c-x><c-u>; remove dbg\/log comments\n- Call UpdateWordList() on BufDelete, not BufUnload\n- Debugging, s:Run()\n- g:likelycomplete#sources: Define source & order; g:likelycomplete#dictionaries: define dictionaries\n- g:likelycomplete_per_window: per-window filetypes (not yet functional)\n- Don't update word list when using w:likelycomplete_filetype\n- Make sure not to update wordlist if sources don't include 'likelycomplete'\n- FIX variable scope\n- SetupComplete(): Add dictionaries to &complete and &dictionary\n- Use \"_\" if filetype is empty; actually test likelycomplete#SetupFiletype()\n- Renamed 'dict' to 'dictionaries'; support for including 'dictionary'\n- g:likelycomplete#sources: Remove \"?files\"\nMD5 checksum: c633c39845d8e2869ea26fb4cbe9561a","package":"likelycomplete.vba","4":"likelycomplete.vba","src_id":"21675","5":"21675","creation_date":"1395840369","6":"1395840369"},{"0":"4889","vim_version":"7.0","1":"7.0","script_version":"0.02","2":"0.02","version_comment":"- g:likelycomplete#options_javascript; allow customization of  cms_rx\n- use_words: Add the current buffer's words to the list of possible completions\n- s:GetCompletions(): return unique words\n- likelycomplete#ListPicker_tlib(): Temporarily set noshowmode\n- g:likelycomplete#use_fuzzy_matches defaults to 0\n- g:likelycomplete#use_fuzzy_matches defaults to 1 (again); slightly improved ranking for fuzzy patterns\n- UpdateWordListNow: increased base value for AssessContext to 10; FIX comparison\n- Make sure not to call AutoComplete twice\n- Cache intermediate results in s:GetSortedCompletions()\nMD5 checksum: 1f31791acf08a1f9266203c071c59f2a","3":"- g:likelycomplete#options_javascript; allow customization of  cms_rx\n- use_words: Add the current buffer's words to the list of possible completions\n- s:GetCompletions(): return unique words\n- likelycomplete#ListPicker_tlib(): Temporarily set noshowmode\n- g:likelycomplete#use_fuzzy_matches defaults to 0\n- g:likelycomplete#use_fuzzy_matches defaults to 1 (again); slightly improved ranking for fuzzy patterns\n- UpdateWordListNow: increased base value for AssessContext to 10; FIX comparison\n- Make sure not to call AutoComplete twice\n- Cache intermediate results in s:GetSortedCompletions()\nMD5 checksum: 1f31791acf08a1f9266203c071c59f2a","package":"likelycomplete.vba","4":"likelycomplete.vba","src_id":"21622","5":"21622","creation_date":"1394989819","6":"1394989819"},{"0":"4889","vim_version":"7.4","1":"7.4","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"likelycomplete.vba","4":"likelycomplete.vba","src_id":"21615","5":"21615","creation_date":"1394797138","6":"1394797138"}]},"4888":{"script_id":"4888","0":"4888","script_name":"svnj.vim","1":"svnj.vim","script_type":"utility","2":"utility","summary":"vim svn plugin (subversion svn ) and browser","3":"vim svn plugin (subversion svn ) and browser","description":"VIM (VIM 7 and up) plugin for subversion (svn)\r\n\r\nSupport for svn add,commit, view logs, diff, checkout and browsing the repository, working copy, bookmarks plus more\r\n\r\nkeywords: svn vim subversion SVN\r\n\r\nRepo :    https:\/\/github.com\/juneedahamed\/svnj.vim\r\n\r\nscreenshots  :  \r\n              http:\/\/i.imgur.com\/GplIbo2.png\r\n              http:\/\/i.imgur.com\/Vl9pmoI.png\r\n              http:\/\/i.imgur.com\/I69Mny2.png\r\n              http:\/\/i.imgur.com\/oY6E2kP.png\r\n              http:\/\/i.imgur.com\/QskUigu.png\r\n              http:\/\/i.imgur.com\/GTBhjVT.png\r\n\r\nSupported operations\r\n     svn add, commit, log, status, diff, blame, list, info, co\r\n\r\nFeatures\r\n1. SVNAdd [<file>|<dir>|%]\r\n    Add and Commit File(s)\/Directories to svn repo. SVNAdd is supported as a command and also as an\r\n    operation from SVNStatus and SVNBrowse output. Available options are to just add or add and commit \r\n\r\n2. SVNCommit[!] [<file>|<dir>|%]\r\n     Performs svn commit. A new buffer will be opened to accept comments. The buffer will list\r\n     the files which are candidates for commit. Files\/Directories can also be updated in this buffer. \r\n     A commit can be forced with no comments with a bang. SVNCommit is supported as a command and \r\n     also as an operation from the SVNStatus|SVNBrowseWorkingCopy|SVNBrowseBuffer output window. \r\n\r\n3. SVNBlame [<file>|<dir>|%]\r\n     Vertically splits the blame info for the file in bufffer. Scrollbinds to the file.\r\n\r\n4. SVNStatus [ <dir> | . [q] [u]]\r\n     Get the output of svn status. With the listed files in the split buffer which states the filename\r\n     and status, the following are few of the operations supported\r\n       - Open file under cursor or all \r\n       - SVN info, SVN Diff \r\n       - SVN Commit selected\/marked files, opens a commit log for accepting comments (svn ci)\r\n       - SVN Add selected\/marked files as new repo elements (svn add)\r\n\r\n5. SVNLog [<file> | <dir> | . | % [,nooflogs]]\r\n     Lists the log for the current file in buffer.  The output displays the revision, author, comments \r\n     and the revision when the branch was created. With the revisions listed can diff the required \r\n     revisions with the file in buffer. Also provides mechanism to diff the file across branches\/trunk. \r\n     A menu will be displayed to list revisions from available branches and trunk. This requires that\r\n     g:svnj_branch_url and g:svnj_trunk_url be defined. \r\n\r\n     - Diff revision(s) from current working copy or across branches\/trunk\r\n     - List Affected\/Modified files for the revision (most useful with dirs)\r\n     - SVN Diff :HEAD | :PREV  with selected revision (most useful with dirs)\r\n     - Open marked revisons or revison under cursor as new file - newbuffer or vspilt\r\n     - View SVN Info and Log of revision\r\n\r\n6. SVNDiff\r\n   Immediate diff the file in buffer with the previous revision. If there are more than one file in \r\n   buffer Ctrl-n\/Ctrl-p will close the current diff and move to the next\/prev file in buffer.\r\n\r\n7. SVNBrowse\r\n   Browse the svn repository, working copy files, buffer files, favorites, bookmarks\r\n\r\n     - SVNBrowse\r\n         This command brings up a menu of available options for browsing.\r\n     - SVNBrowseRepo [<dir>|\/]\r\n         This command lists files\/directories from the repository. The current directory should be \r\n         a working copy for the plugin to pick up the svn path.\r\n     - SVNBrowseWorkingCopy [<dir>]\r\n         This command lists files\/directories from the current directory. \r\n     - SVNBrowseMyList\r\n         This command lists files\/directories specified using g:svnj_browse_mylist see \r\n         :help g:svnj_browse_mylist \r\n     - SVNBrowseBookMarks\r\n           While browsing the repo\/working copy you can bookmarks the dir\/files \r\n           All of the book marked files will be listed as output. \r\n           These bookmarked files\/dirs are available only for the current vim session unless caching \r\n           is enabled, Once vim is closed all bookmarks are lost if caching is not enabled.\r\n     -SVNBrowseBuffer\r\n           List the files from Buffer\r\n\r\n     Cache for browsing:\r\n         The caching feature is off by default, On enabling the caching the listing of files for \r\n     SVNBrowseRepo and SVNBrowseWorkingCopy will be faster. There are many levels at which the caching\r\n     can be enabled see help:g:svnj_cache_dir\r\n\r\n    Some of the operations supported are\r\n      - Recursive\/Non-recursive listing of files from directory\r\n      - Open file(s) in new buffer or vertical split\r\n      - Navigate up\/down the directory, Jump to Respository Root\/Working Root\/Home where applicable\r\n      - SVN info, SVN Log\r\n      - Bookmark the dir\/file. To persist the bookmarks across sessions see :help g:svnj_browse_bookmarks_cache\r\n      - SVN Checkout (svn co)\r\n          Hint : Use Bookmarks or MyList feature to store the repo root so that can be browsed \r\n                 when need to checkout.  \r\n      - SVN Copy (Paste) the selected urls to new dir location, (svn cp)\r\n          The paste on repo requires a commit so a buffer will be opened to enter comments for the commit\r\n      - SVN Add, SVN Commit\r\n\r\n 8. SVNCommits [ <dir> | . | [,nooflogs]]\r\n      Get the list of files checked in across project revision. This command lists the output of svn log \r\n      of the project directory.  \r\n\r\n9. SVNClearCache\r\n     The cache\/persistency is not enabled by default. please see :help SVNClearCache for more info.\r\n\r\n10. SVNInfo [<file> | <dir> | % | . ]\r\n     Will display svn info.\r\n\r\nRecomended settings at .vimrc\r\n\r\nlet g:svnj_custom_statusbar_ops_hide = 1\r\n    Supported operations are listed on the status line of the svnj_window. With growing support for\r\n    many commands, recomend to hide it. You can still have a quick glance of supported operations by\r\n    pressing ?\r\n\r\nlet g:svnj_browse_cache_all = 1\r\n    This enables caching, Listing of files will be faster, On MAC\/Unix the default location is $HOME\/.cache.\r\n    A new directory svnj will be created in the specified directory.\r\n\r\n    For windows this option must be specified along with the cache dir\r\n    let g:svnj_cache_dir=\"C:\/Users\/user1\"\r\n\r\nlet g:svnj_branch_url = [\"svn:\/\/127.0.0.1\/Path\/until\/branches\/\", \"svn:\/\/127.0.0.1\/Path\/until\/tags\/\"]\r\n    This settings when available will provide menu's to navigate available branches and tags for SVNLog\r\n\r\nlet g:svnj_trunk_url = \"svn:\/\/127.0.0.1\/Path\/until\/trunk\";\r\n    This settings when available will provide menu's to navigate trunk files for SVNLog\r\n\r\nGlobal Options  :help svnj-options and :help svnj-customize\r\n\r\n +  g:svnj_max_logs, g:svnj_max_open_files, g:svnj_max_diff,\r\n    g:svnj_window_max_size, g:svnj_warn_branch_log, g:svnj_browse_max_files_cnt,\r\n    g:svnj_browse_repo_max_files, g:svnj_sticky_on_start, g:svnj_send_soc_command\r\n\r\n + g:svnj_browse_cache_all, g:svnj_browse_bookmarks_cache, g:svnj_browse_repo_cache,\r\n   g:svnj_browse_workingcopy_cache, g:svnj_browse_cache_max_cnt\r\n\r\n + g:svnj_signs, g:svnj_ignore_files, \r\n\r\n + g:svnj_browse_mylist\r\n\r\n + g:svnj_branch_url, g:svnj_trunk_url\r\n\r\n + g:svnj_custom_fuzzy_match_hl, g:svnj_custom_menu_color, g:svnj_custom_error_color,\r\n   g:svnj_custom_prompt_color, g:svnj_custom_statusbar_hl, g:svnj_custom_statusbar_title\r\n   g:svnj_custom_statusbar_title, g:svnj_custom_statusbar_ops_hl, \r\n   g:svnj_custom_statusbar_sel_hl, g:svnj_custom_statusbar_ops_hide,\r\n   g:svnj_custom_sticky_hl, g:svnj_custom_commit_files_hl, g:svnj_custom_commit_header_hl\r\n\r\n\r\nBasic Usage:\r\n    Run from vim command line\r\n    :SVNBrowse  ,   :SVNBrowseWorkingCopy ,  :SVNBrowseRepo, :SVNBrowseBookMarks , :SVNBrowseMyList\r\n    :SVNBlame\r\n    :SVNDiff\r\n    :SVNLog\r\n    :SVNStatus\r\n    :SVNCommits\r\n    :SVNInfo\r\n    :SVNClearCache\r\n    :help svn\r\n","4":"VIM (VIM 7 and up) plugin for subversion (svn)\r\n\r\nSupport for svn add,commit, view logs, diff, checkout and browsing the repository, working copy, bookmarks plus more\r\n\r\nkeywords: svn vim subversion SVN\r\n\r\nRepo :    https:\/\/github.com\/juneedahamed\/svnj.vim\r\n\r\nscreenshots  :  \r\n              http:\/\/i.imgur.com\/GplIbo2.png\r\n              http:\/\/i.imgur.com\/Vl9pmoI.png\r\n              http:\/\/i.imgur.com\/I69Mny2.png\r\n              http:\/\/i.imgur.com\/oY6E2kP.png\r\n              http:\/\/i.imgur.com\/QskUigu.png\r\n              http:\/\/i.imgur.com\/GTBhjVT.png\r\n\r\nSupported operations\r\n     svn add, commit, log, status, diff, blame, list, info, co\r\n\r\nFeatures\r\n1. SVNAdd [<file>|<dir>|%]\r\n    Add and Commit File(s)\/Directories to svn repo. SVNAdd is supported as a command and also as an\r\n    operation from SVNStatus and SVNBrowse output. Available options are to just add or add and commit \r\n\r\n2. SVNCommit[!] [<file>|<dir>|%]\r\n     Performs svn commit. A new buffer will be opened to accept comments. The buffer will list\r\n     the files which are candidates for commit. Files\/Directories can also be updated in this buffer. \r\n     A commit can be forced with no comments with a bang. SVNCommit is supported as a command and \r\n     also as an operation from the SVNStatus|SVNBrowseWorkingCopy|SVNBrowseBuffer output window. \r\n\r\n3. SVNBlame [<file>|<dir>|%]\r\n     Vertically splits the blame info for the file in bufffer. Scrollbinds to the file.\r\n\r\n4. SVNStatus [ <dir> | . [q] [u]]\r\n     Get the output of svn status. With the listed files in the split buffer which states the filename\r\n     and status, the following are few of the operations supported\r\n       - Open file under cursor or all \r\n       - SVN info, SVN Diff \r\n       - SVN Commit selected\/marked files, opens a commit log for accepting comments (svn ci)\r\n       - SVN Add selected\/marked files as new repo elements (svn add)\r\n\r\n5. SVNLog [<file> | <dir> | . | % [,nooflogs]]\r\n     Lists the log for the current file in buffer.  The output displays the revision, author, comments \r\n     and the revision when the branch was created. With the revisions listed can diff the required \r\n     revisions with the file in buffer. Also provides mechanism to diff the file across branches\/trunk. \r\n     A menu will be displayed to list revisions from available branches and trunk. This requires that\r\n     g:svnj_branch_url and g:svnj_trunk_url be defined. \r\n\r\n     - Diff revision(s) from current working copy or across branches\/trunk\r\n     - List Affected\/Modified files for the revision (most useful with dirs)\r\n     - SVN Diff :HEAD | :PREV  with selected revision (most useful with dirs)\r\n     - Open marked revisons or revison under cursor as new file - newbuffer or vspilt\r\n     - View SVN Info and Log of revision\r\n\r\n6. SVNDiff\r\n   Immediate diff the file in buffer with the previous revision. If there are more than one file in \r\n   buffer Ctrl-n\/Ctrl-p will close the current diff and move to the next\/prev file in buffer.\r\n\r\n7. SVNBrowse\r\n   Browse the svn repository, working copy files, buffer files, favorites, bookmarks\r\n\r\n     - SVNBrowse\r\n         This command brings up a menu of available options for browsing.\r\n     - SVNBrowseRepo [<dir>|\/]\r\n         This command lists files\/directories from the repository. The current directory should be \r\n         a working copy for the plugin to pick up the svn path.\r\n     - SVNBrowseWorkingCopy [<dir>]\r\n         This command lists files\/directories from the current directory. \r\n     - SVNBrowseMyList\r\n         This command lists files\/directories specified using g:svnj_browse_mylist see \r\n         :help g:svnj_browse_mylist \r\n     - SVNBrowseBookMarks\r\n           While browsing the repo\/working copy you can bookmarks the dir\/files \r\n           All of the book marked files will be listed as output. \r\n           These bookmarked files\/dirs are available only for the current vim session unless caching \r\n           is enabled, Once vim is closed all bookmarks are lost if caching is not enabled.\r\n     -SVNBrowseBuffer\r\n           List the files from Buffer\r\n\r\n     Cache for browsing:\r\n         The caching feature is off by default, On enabling the caching the listing of files for \r\n     SVNBrowseRepo and SVNBrowseWorkingCopy will be faster. There are many levels at which the caching\r\n     can be enabled see help:g:svnj_cache_dir\r\n\r\n    Some of the operations supported are\r\n      - Recursive\/Non-recursive listing of files from directory\r\n      - Open file(s) in new buffer or vertical split\r\n      - Navigate up\/down the directory, Jump to Respository Root\/Working Root\/Home where applicable\r\n      - SVN info, SVN Log\r\n      - Bookmark the dir\/file. To persist the bookmarks across sessions see :help g:svnj_browse_bookmarks_cache\r\n      - SVN Checkout (svn co)\r\n          Hint : Use Bookmarks or MyList feature to store the repo root so that can be browsed \r\n                 when need to checkout.  \r\n      - SVN Copy (Paste) the selected urls to new dir location, (svn cp)\r\n          The paste on repo requires a commit so a buffer will be opened to enter comments for the commit\r\n      - SVN Add, SVN Commit\r\n\r\n 8. SVNCommits [ <dir> | . | [,nooflogs]]\r\n      Get the list of files checked in across project revision. This command lists the output of svn log \r\n      of the project directory.  \r\n\r\n9. SVNClearCache\r\n     The cache\/persistency is not enabled by default. please see :help SVNClearCache for more info.\r\n\r\n10. SVNInfo [<file> | <dir> | % | . ]\r\n     Will display svn info.\r\n\r\nRecomended settings at .vimrc\r\n\r\nlet g:svnj_custom_statusbar_ops_hide = 1\r\n    Supported operations are listed on the status line of the svnj_window. With growing support for\r\n    many commands, recomend to hide it. You can still have a quick glance of supported operations by\r\n    pressing ?\r\n\r\nlet g:svnj_browse_cache_all = 1\r\n    This enables caching, Listing of files will be faster, On MAC\/Unix the default location is $HOME\/.cache.\r\n    A new directory svnj will be created in the specified directory.\r\n\r\n    For windows this option must be specified along with the cache dir\r\n    let g:svnj_cache_dir=\"C:\/Users\/user1\"\r\n\r\nlet g:svnj_branch_url = [\"svn:\/\/127.0.0.1\/Path\/until\/branches\/\", \"svn:\/\/127.0.0.1\/Path\/until\/tags\/\"]\r\n    This settings when available will provide menu's to navigate available branches and tags for SVNLog\r\n\r\nlet g:svnj_trunk_url = \"svn:\/\/127.0.0.1\/Path\/until\/trunk\";\r\n    This settings when available will provide menu's to navigate trunk files for SVNLog\r\n\r\nGlobal Options  :help svnj-options and :help svnj-customize\r\n\r\n +  g:svnj_max_logs, g:svnj_max_open_files, g:svnj_max_diff,\r\n    g:svnj_window_max_size, g:svnj_warn_branch_log, g:svnj_browse_max_files_cnt,\r\n    g:svnj_browse_repo_max_files, g:svnj_sticky_on_start, g:svnj_send_soc_command\r\n\r\n + g:svnj_browse_cache_all, g:svnj_browse_bookmarks_cache, g:svnj_browse_repo_cache,\r\n   g:svnj_browse_workingcopy_cache, g:svnj_browse_cache_max_cnt\r\n\r\n + g:svnj_signs, g:svnj_ignore_files, \r\n\r\n + g:svnj_browse_mylist\r\n\r\n + g:svnj_branch_url, g:svnj_trunk_url\r\n\r\n + g:svnj_custom_fuzzy_match_hl, g:svnj_custom_menu_color, g:svnj_custom_error_color,\r\n   g:svnj_custom_prompt_color, g:svnj_custom_statusbar_hl, g:svnj_custom_statusbar_title\r\n   g:svnj_custom_statusbar_title, g:svnj_custom_statusbar_ops_hl, \r\n   g:svnj_custom_statusbar_sel_hl, g:svnj_custom_statusbar_ops_hide,\r\n   g:svnj_custom_sticky_hl, g:svnj_custom_commit_files_hl, g:svnj_custom_commit_header_hl\r\n\r\n\r\nBasic Usage:\r\n    Run from vim command line\r\n    :SVNBrowse  ,   :SVNBrowseWorkingCopy ,  :SVNBrowseRepo, :SVNBrowseBookMarks , :SVNBrowseMyList\r\n    :SVNBlame\r\n    :SVNDiff\r\n    :SVNLog\r\n    :SVNStatus\r\n    :SVNCommits\r\n    :SVNInfo\r\n    :SVNClearCache\r\n    :help svn\r\n","install_details":"Options 1: (Pathogen Users)\r\n    cd ~\/.vim\/bundle\r\n    unzip svnj.vim.1.0.zip\r\n\r\nOption 2:\r\n    Download to some folder\r\n\r\n    unzip svnj.vim.1.0.zip\r\n    cp -r svnj.vim\/plugin\/*  ~\/.vim\/plugin    \r\n    cp -r svnj.vim\/autoload\/* ~\/.vim\/autoload \r\n    cp -r svnj.vim\/doc\/*  ~\/.vim\/doc\r\n\r\n    Run at vim's command :helptags doc","5":"Options 1: (Pathogen Users)\r\n    cd ~\/.vim\/bundle\r\n    unzip svnj.vim.1.0.zip\r\n\r\nOption 2:\r\n    Download to some folder\r\n\r\n    unzip svnj.vim.1.0.zip\r\n    cp -r svnj.vim\/plugin\/*  ~\/.vim\/plugin    \r\n    cp -r svnj.vim\/autoload\/* ~\/.vim\/autoload \r\n    cp -r svnj.vim\/doc\/*  ~\/.vim\/doc\r\n\r\n    Run at vim's command :helptags doc","first_name":"juneed","6":"juneed","last_name":"ahamed","7":"ahamed","releases":[{"0":"4888","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"+ Added Ctrl Up Arrow and Ctrl Down Arrow in diff window to diff with old, new \r\n      revisions of the file\r\n\r\n + Added ! option for SVNDiff\r\n + Added authentication support, please refer to :help svnj-authentication\r\n\r\n + Now the cursor remembers the last selection in SVNLog\r\n    Example SVNLog <dir>\r\n    outputs is svn log of <dir>, then use Ctrl-a to see affected files. In the affected files\r\n    window to go back press Ctrl-u, The window displays the last window with the\r\n    last visted log\r\n\r\n + Now the cursor is placed on the directory when navigating upwards during browse ops\r\n + Bug fixes\r\n     Now remembers the previous window and the cursor is place in the correct\r\n     window when the svnj window is closed\r\n\r\n +Changed setting g:svnj_custom_statusbar_ops_hide = 1 as default\r\n +Changed settings g:svnj_max_logs = 50 as default\r\n","3":"+ Added Ctrl Up Arrow and Ctrl Down Arrow in diff window to diff with old, new \r\n      revisions of the file\r\n\r\n + Added ! option for SVNDiff\r\n + Added authentication support, please refer to :help svnj-authentication\r\n\r\n + Now the cursor remembers the last selection in SVNLog\r\n    Example SVNLog <dir>\r\n    outputs is svn log of <dir>, then use Ctrl-a to see affected files. In the affected files\r\n    window to go back press Ctrl-u, The window displays the last window with the\r\n    last visted log\r\n\r\n + Now the cursor is placed on the directory when navigating upwards during browse ops\r\n + Bug fixes\r\n     Now remembers the previous window and the cursor is place in the correct\r\n     window when the svnj window is closed\r\n\r\n +Changed setting g:svnj_custom_statusbar_ops_hide = 1 as default\r\n +Changed settings g:svnj_max_logs = 50 as default\r\n","package":"svnj.vim.1.0.zip","4":"svnj.vim.1.0.zip","src_id":"22885","5":"22885","creation_date":"1423287430","6":"1423287430"},{"0":"4888","vim_version":"7.0","1":"7.0","script_version":"0.9","2":"0.9","version_comment":" NEW,\r\n  SVNAdd (svn add), SVNCommit (svn ci) , Checkout (svn co), Copy (svn copy) and\r\n  stop-on-copy for svn log, SVNBrowseBuffer\r\n\r\n+ SVNAdd\r\n  As a command SVNAdd or operation from SVNStatus, SVNBrowse. Provides option to add and commit\r\n  or just add the elements to repository.\r\n\r\n+ SVNCommit \r\n   Can execute :SVNCommit , will commit file in buffer or files\/dirs passed as\r\n   arguments\r\n   + Added commit as operation for SVN Status and SVNBrowse\r\n     select the required files from SVNStatus | SVNBrowseWorkingCopy | SVNBrowseBuffer\r\n     output and press Ctrl-z, this will bring up the commit log\r\n\r\n+ SVNBrowseBuffer\r\n\r\n+ SVN Log \r\n   1. Now shows the --stop-on-copy revision on the status bar as \"S@\"revision_num\r\n        This will be the revision number when the working copy was created.\r\n        Those who prefer not want to see this info can opt to not\r\n        send this command by setting g:svnj_send_soc_command to 0\r\n   2. Added Ctrl-h : Brings up svn diff passing :HEAD to selected revision \r\n   3. Added Ctrl-p : Brings up svn diff passing :PREV to selected revision \r\n\r\n   Now simplifies the operation of finding all changes to current directory\r\n\r\n   At vim execute :SVNLog . \r\n   The title now shows the s@ revision\r\n   Go to the said revision and press Ctrl-h\r\n\r\n+ SVN Status has following new ops\r\n   + Select All\r\n   + Commit selected\r\n   + Add selected files to repo\r\n\r\n+ SVNBrowse commands has following new ops\r\n   + Add (svn add)\r\n   + Commit  (svn ci)\r\n   + Copy (svn cp)\r\n   + Checkout (svn co)\r\n\r\n+ Added operation to checkout to browse operation (should be a respository browse)\r\n   Hint : Use bookmarks, mylist feature to store the repository root and then\r\n   check out from there\r\n\r\n+ SVNInfo now takes arguments\r\n\r\n+ Added options g:svnj_send_soc_command, g:svnj_custom_commit_files_hl,\r\n  g:svnj_custom_commit_header_hl\r\n       \r\n+ Now providing browser to select file when doing a file diff in SVNLog\r\n  across branches\/trunk when svnj fails to create a proper svn url.\r\n  Now not using svn list -r command to hunt down the file. ","3":" NEW,\r\n  SVNAdd (svn add), SVNCommit (svn ci) , Checkout (svn co), Copy (svn copy) and\r\n  stop-on-copy for svn log, SVNBrowseBuffer\r\n\r\n+ SVNAdd\r\n  As a command SVNAdd or operation from SVNStatus, SVNBrowse. Provides option to add and commit\r\n  or just add the elements to repository.\r\n\r\n+ SVNCommit \r\n   Can execute :SVNCommit , will commit file in buffer or files\/dirs passed as\r\n   arguments\r\n   + Added commit as operation for SVN Status and SVNBrowse\r\n     select the required files from SVNStatus | SVNBrowseWorkingCopy | SVNBrowseBuffer\r\n     output and press Ctrl-z, this will bring up the commit log\r\n\r\n+ SVNBrowseBuffer\r\n\r\n+ SVN Log \r\n   1. Now shows the --stop-on-copy revision on the status bar as \"S@\"revision_num\r\n        This will be the revision number when the working copy was created.\r\n        Those who prefer not want to see this info can opt to not\r\n        send this command by setting g:svnj_send_soc_command to 0\r\n   2. Added Ctrl-h : Brings up svn diff passing :HEAD to selected revision \r\n   3. Added Ctrl-p : Brings up svn diff passing :PREV to selected revision \r\n\r\n   Now simplifies the operation of finding all changes to current directory\r\n\r\n   At vim execute :SVNLog . \r\n   The title now shows the s@ revision\r\n   Go to the said revision and press Ctrl-h\r\n\r\n+ SVN Status has following new ops\r\n   + Select All\r\n   + Commit selected\r\n   + Add selected files to repo\r\n\r\n+ SVNBrowse commands has following new ops\r\n   + Add (svn add)\r\n   + Commit  (svn ci)\r\n   + Copy (svn cp)\r\n   + Checkout (svn co)\r\n\r\n+ Added operation to checkout to browse operation (should be a respository browse)\r\n   Hint : Use bookmarks, mylist feature to store the repository root and then\r\n   check out from there\r\n\r\n+ SVNInfo now takes arguments\r\n\r\n+ Added options g:svnj_send_soc_command, g:svnj_custom_commit_files_hl,\r\n  g:svnj_custom_commit_header_hl\r\n       \r\n+ Now providing browser to select file when doing a file diff in SVNLog\r\n  across branches\/trunk when svnj fails to create a proper svn url.\r\n  Now not using svn list -r command to hunt down the file. ","package":"svnj.vim.0.9.zip","4":"svnj.vim.0.9.zip","src_id":"22266","5":"22266","creation_date":"1406452605","6":"1406452605"},{"0":"4888","vim_version":"7.0","1":"7.0","script_version":"0.8","2":"0.8","version_comment":"+ NEW Highlights:   \r\n     Sticky (Ctrl-s), Browsing(Ctrl-h), Diffed files(Ctrl-q)\r\n     Bookmark files listed in SVNStatus window\r\n     Browsing recursive up, Vertical split\r\n     Number of logs to display as argument where applicable\r\n     SVNBlame binds\r\n     Fuzzzy speed improvements\r\n     Quick glance operation using \"?\"\r\n     New options g:svnj_sticky_on_start, g:svnj_window_max_size\r\n                 g:svnj_custom_sticky_hl, g:svnj_warn_branch_log\r\n\r\n+ STICKY, Now can have the svnj window remain on after file selections. Useful \r\n  for doing multiple operations on different files\/directories.\r\n\r\n  Ctrl-s toggles the STICKY behavior. This operation is available for all \r\n  SVNJ commands which brings up the svnj window.\r\n\r\n  If you like the sticky behavior and would like to start as default on use\r\n  the option g:svnj_sticky_on_start as 1 default is 0. At .vimrc\r\n   let g:svnj_sticky_on_start = 1\r\n\r\n+ Added Ctrl-q to the files diffed from SVNJWindow. Press Ctrl-q on the diffed\r\n  file. If the sticky is enabled on svnj window, the control\/cursor will land back\r\n  on the svnj window.  Very helpfull when need to diff\/compare a few versions for\r\n  a given file. See an example usage above as |How to use sticky and Ctrl-q|\r\n\r\n+ Speed up fuzzy search\r\n\r\n+ Added Ctrl-h to browsing, Takes to repository root if the current directory is \r\n  a revisioned else to Working copy root if working copy. If at working copy\r\n  the first Ctrl-h jumps to Working copy root and again the second Ctrl-h jumps\r\n  to $HOME. Save a few keystorkes\r\n\r\n+ Now can bookmark status output, the file\/dir will can be bookmarked to open and\r\n  operate on later\r\n\r\n+ SVNLog, SVNCommits takes in an optional numeric values as the number of logs to \r\n  display, When not provided will use the default or the value specified \r\n  in g:svnj_max_logs\r\n\r\n+ Browsing recursive, If navigating downwards was recursive so will be the upward\r\n  navigation and vice versa\r\n\r\n+ Added Ctrl-v to open as vertical split\r\n\r\n+ SVNBlame now scrollbinds to file.  When the cursor in the blame buffer is moved\r\n  the file on the right buffer will be in sync with the blame file\r\n\r\n+ Added g:svnj_window_max_size to handle the size of svnj window\r\n\r\n+ Added F5 to redraw buffer\r\n\r\n+ Added \"?\" as help display supported operations. Now can disable the\r\n  operations using \r\n   let g:svnj_custom_statusbar_ops_hide = 1\r\n  and then use ? to bring out the supported operations for a quick glance\r\n\r\n+ Added Ctrl-i for log output to display info and log (Useful if the comments are \r\n  long)\r\n\r\nFIXED\r\n+ Bookmark sign is shown while browsing bookmarks list, now its easier to unbook\r\n+ Fixed filename\/dirs with spaces\/special chars.","3":"+ NEW Highlights:   \r\n     Sticky (Ctrl-s), Browsing(Ctrl-h), Diffed files(Ctrl-q)\r\n     Bookmark files listed in SVNStatus window\r\n     Browsing recursive up, Vertical split\r\n     Number of logs to display as argument where applicable\r\n     SVNBlame binds\r\n     Fuzzzy speed improvements\r\n     Quick glance operation using \"?\"\r\n     New options g:svnj_sticky_on_start, g:svnj_window_max_size\r\n                 g:svnj_custom_sticky_hl, g:svnj_warn_branch_log\r\n\r\n+ STICKY, Now can have the svnj window remain on after file selections. Useful \r\n  for doing multiple operations on different files\/directories.\r\n\r\n  Ctrl-s toggles the STICKY behavior. This operation is available for all \r\n  SVNJ commands which brings up the svnj window.\r\n\r\n  If you like the sticky behavior and would like to start as default on use\r\n  the option g:svnj_sticky_on_start as 1 default is 0. At .vimrc\r\n   let g:svnj_sticky_on_start = 1\r\n\r\n+ Added Ctrl-q to the files diffed from SVNJWindow. Press Ctrl-q on the diffed\r\n  file. If the sticky is enabled on svnj window, the control\/cursor will land back\r\n  on the svnj window.  Very helpfull when need to diff\/compare a few versions for\r\n  a given file. See an example usage above as |How to use sticky and Ctrl-q|\r\n\r\n+ Speed up fuzzy search\r\n\r\n+ Added Ctrl-h to browsing, Takes to repository root if the current directory is \r\n  a revisioned else to Working copy root if working copy. If at working copy\r\n  the first Ctrl-h jumps to Working copy root and again the second Ctrl-h jumps\r\n  to $HOME. Save a few keystorkes\r\n\r\n+ Now can bookmark status output, the file\/dir will can be bookmarked to open and\r\n  operate on later\r\n\r\n+ SVNLog, SVNCommits takes in an optional numeric values as the number of logs to \r\n  display, When not provided will use the default or the value specified \r\n  in g:svnj_max_logs\r\n\r\n+ Browsing recursive, If navigating downwards was recursive so will be the upward\r\n  navigation and vice versa\r\n\r\n+ Added Ctrl-v to open as vertical split\r\n\r\n+ SVNBlame now scrollbinds to file.  When the cursor in the blame buffer is moved\r\n  the file on the right buffer will be in sync with the blame file\r\n\r\n+ Added g:svnj_window_max_size to handle the size of svnj window\r\n\r\n+ Added F5 to redraw buffer\r\n\r\n+ Added \"?\" as help display supported operations. Now can disable the\r\n  operations using \r\n   let g:svnj_custom_statusbar_ops_hide = 1\r\n  and then use ? to bring out the supported operations for a quick glance\r\n\r\n+ Added Ctrl-i for log output to display info and log (Useful if the comments are \r\n  long)\r\n\r\nFIXED\r\n+ Bookmark sign is shown while browsing bookmarks list, now its easier to unbook\r\n+ Fixed filename\/dirs with spaces\/special chars.","package":"svnj.vim.0.8.zip","4":"svnj.vim.0.8.zip","src_id":"21899","5":"21899","creation_date":"1400293063","6":"1400293063"},{"0":"4888","vim_version":"7.0","1":"7.0","script_version":"0.5","2":"0.5","version_comment":" FIXED:\r\n  + statusline getting disappeared in few scenarios   \r\n \r\nENAHANCEMENTS:\r\n  + Added BrowseWorkingCopyRec\r\n     - This command recusrively lists file, avoids a few key strokes\r\n  + BrowseWorkingCopy[Rec] command now works for local files\/directories also,\r\n     The svn commands like show logs will report error if the selected entry is not\r\n     an svn entity, Other operations like open should work\r\n  + Supported Ctrl-Enter for BrowseMenu on Repo and Workingcopy , saves again few keystorkes\r\n  + OpenAll [Ctrl-o ] operation in case of Browse, Status and Commits will honor the filter,\r\n    Files shown only on the buffer will be candidates to be opened\r\n  + Added Ctrl-i for browsed and stats file, this lists the svn info of file\/dir\r\n  + Enhanced file fetcher, limits the depth\/number of files fetched\r\n  + status line shows number for files selected\/marked\r\n  + Added more customization options\r\n     g:svnj_custom_statusbar_ops_hl, g:svnj_custom_statusbar_ops_hide,\r\n     g:svnj_custom_statusbar_sel_hl","3":" FIXED:\r\n  + statusline getting disappeared in few scenarios   \r\n \r\nENAHANCEMENTS:\r\n  + Added BrowseWorkingCopyRec\r\n     - This command recusrively lists file, avoids a few key strokes\r\n  + BrowseWorkingCopy[Rec] command now works for local files\/directories also,\r\n     The svn commands like show logs will report error if the selected entry is not\r\n     an svn entity, Other operations like open should work\r\n  + Supported Ctrl-Enter for BrowseMenu on Repo and Workingcopy , saves again few keystorkes\r\n  + OpenAll [Ctrl-o ] operation in case of Browse, Status and Commits will honor the filter,\r\n    Files shown only on the buffer will be candidates to be opened\r\n  + Added Ctrl-i for browsed and stats file, this lists the svn info of file\/dir\r\n  + Enhanced file fetcher, limits the depth\/number of files fetched\r\n  + status line shows number for files selected\/marked\r\n  + Added more customization options\r\n     g:svnj_custom_statusbar_ops_hl, g:svnj_custom_statusbar_ops_hide,\r\n     g:svnj_custom_statusbar_sel_hl","package":"svnj.vim.0.5.zip","4":"svnj.vim.0.5.zip","src_id":"21791","5":"21791","creation_date":"1397880523","6":"1397880523"},{"0":"4888","vim_version":"7.0","1":"7.0","script_version":"0.4","2":"0.4","version_comment":"  + Added support to browse the entire svn using |SVNBrowse| command\r\n  + Added support to browse the working directory using |SVNBrowseWorkingCopy| command\r\n  + Added support for permanent bookmarks see g:svnj_browse_mylist\r\n  + Added support for multiple branches at g:svnj_branch_url \r\n        - Hint svn tag  \r\n  + Added support to navigate entire SVN without any configuration\r\n     NOTE: Using configuration options like g:svnj_browse_mylist and g:svnj_branch_url\r\n           will help navigate faster.  Again g:svnj_branch_url supports coma seperated \r\n           directories\r\n  + Added sign(s) for file\/logs selection\r\n  + Added support for customization \r\n     use    :help svnj-customize\r\n  + Added following Key Mapping \r\n        |Ctrl-t|  : Go to start\r\n        |Ctrl-u|  : Go up\r\n  + Added more files to ignore list\r\n  - Removed |SVNList|, |SVNListRec| in favor of SVNBrowse and SVNBrowseWorkingCopy and\r\n    more\r\n\r\n   Known Issue.\r\n   1. Marking\/Selecting the file\/directory using Ctrl-Space highlights the line\r\n      Later navigating away from the path say going up the directory and recusrive list\r\n      of contents donot highlights the line though remembers the marked file and open\/diffs\r\n      the file. (Will Fix later)\r\n","3":"  + Added support to browse the entire svn using |SVNBrowse| command\r\n  + Added support to browse the working directory using |SVNBrowseWorkingCopy| command\r\n  + Added support for permanent bookmarks see g:svnj_browse_mylist\r\n  + Added support for multiple branches at g:svnj_branch_url \r\n        - Hint svn tag  \r\n  + Added support to navigate entire SVN without any configuration\r\n     NOTE: Using configuration options like g:svnj_browse_mylist and g:svnj_branch_url\r\n           will help navigate faster.  Again g:svnj_branch_url supports coma seperated \r\n           directories\r\n  + Added sign(s) for file\/logs selection\r\n  + Added support for customization \r\n     use    :help svnj-customize\r\n  + Added following Key Mapping \r\n        |Ctrl-t|  : Go to start\r\n        |Ctrl-u|  : Go up\r\n  + Added more files to ignore list\r\n  - Removed |SVNList|, |SVNListRec| in favor of SVNBrowse and SVNBrowseWorkingCopy and\r\n    more\r\n\r\n   Known Issue.\r\n   1. Marking\/Selecting the file\/directory using Ctrl-Space highlights the line\r\n      Later navigating away from the path say going up the directory and recusrive list\r\n      of contents donot highlights the line though remembers the marked file and open\/diffs\r\n      the file. (Will Fix later)\r\n","package":"svnj.vim.0.4.zip","4":"svnj.vim.0.4.zip","src_id":"21763","5":"21763","creation_date":"1397348362","6":"1397348362"},{"0":"4888","vim_version":"7.0","1":"7.0","script_version":"0.3","2":"0.3","version_comment":"+ Added Fuzzy search at filter \r\n    NOTE:  Needs vim with python for fuzzy search\r\n\r\n+ Added SVNList, SVNListRec\r\n\r\n+ Stream lined operations\r\n+ Added option to open files without splits\r\n+ Bug fixes","3":"+ Added Fuzzy search at filter \r\n    NOTE:  Needs vim with python for fuzzy search\r\n\r\n+ Added SVNList, SVNListRec\r\n\r\n+ Stream lined operations\r\n+ Added option to open files without splits\r\n+ Bug fixes","package":"svnj.vim.0.3.zip","4":"svnj.vim.0.3.zip","src_id":"21669","5":"21669","creation_date":"1395817424","6":"1395817424"},{"0":"4888","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"svnj.vim.zip","4":"svnj.vim.zip","src_id":"21606","5":"21606","creation_date":"1394687061","6":"1394687061"}]},"4887":{"script_id":"4887","0":"4887","script_name":"REPL plugin","1":"REPL plugin","script_type":"utility","2":"utility","summary":"A plugin for handling a REPL interpreter in a scratch window","3":"A plugin for handling a REPL interpreter in a scratch window","description":"This plugin allows the user to open a scratch window with some external REPL interpreter (either a shell or some interpreter for any programming language). You should map a key (see the beginning of the file) to the ReplCmd() command which sends the current line to the interpreter (input is in your edited buffer, output is in the scratch buffer).\r\n\r\nSee video: http:\/\/cjoint.com\/14ma\/DCmkCJGRZH7.htm\r\n\r\nThe plugin uses FIFO special files and won't work under Windows. On the other hand, it will run either in terminal mode or in graphical mode (no server callback). It doesn't need embbeded script languages like python either.\r\n\r\nFor working, just type:\r\n\r\n  :call ReplNew()\r\n  then :call ReplCmd() on each line to be executed (this should be mapped to some shortcut key)\r\n  :call ReplClose()\r\n\r\nDeleting the scratch buffer or the working buffer should close everything also.","4":"This plugin allows the user to open a scratch window with some external REPL interpreter (either a shell or some interpreter for any programming language). You should map a key (see the beginning of the file) to the ReplCmd() command which sends the current line to the interpreter (input is in your edited buffer, output is in the scratch buffer).\r\n\r\nSee video: http:\/\/cjoint.com\/14ma\/DCmkCJGRZH7.htm\r\n\r\nThe plugin uses FIFO special files and won't work under Windows. On the other hand, it will run either in terminal mode or in graphical mode (no server callback). It doesn't need embbeded script languages like python either.\r\n\r\nFor working, just type:\r\n\r\n  :call ReplNew()\r\n  then :call ReplCmd() on each line to be executed (this should be mapped to some shortcut key)\r\n  :call ReplClose()\r\n\r\nDeleting the scratch buffer or the working buffer should close everything also.","install_details":"By default, the script should open a shell \/bin\/sh\r\nBut the script has been tried with other interpreters.\r\nJust edit your ~\/.vimrc file and define the following global variables:\r\n\r\nThe interpreter to be launched:\r\n  let g:repl_cmd = '\/bin\/sh'\r\n\r\nThe command to be sent to the interpreter to make it close by itself:\r\n  let g:repl_stop = 'exit'\r\n\r\nThe command to be sent to the interpreter after each command of the session (for parsing purposes); it should echo some arbitrary string. Single quote should be used rather than double quotes (but if double quotes are absolutely needed, protecting them with a backslash should probably work). What is printed by the interpreter doesn not need to be of a string type from the point of view of the interpreter; it could be a number or whatever as long as the output is an known sequence of characters.\r\n  let g:repl_send = 'echo REPL-VIM-INTERNAL-KEY'\r\n\r\nThe exact string to be caught from the previous command:\r\n  let g:repl_detect = 'REPL-VIM-INTERNAL-KEY'\r\n\r\nSome settings for using with various interpreters can be found there: https:\/\/gist.github.com\/baruchel\/9546517","5":"By default, the script should open a shell \/bin\/sh\r\nBut the script has been tried with other interpreters.\r\nJust edit your ~\/.vimrc file and define the following global variables:\r\n\r\nThe interpreter to be launched:\r\n  let g:repl_cmd = '\/bin\/sh'\r\n\r\nThe command to be sent to the interpreter to make it close by itself:\r\n  let g:repl_stop = 'exit'\r\n\r\nThe command to be sent to the interpreter after each command of the session (for parsing purposes); it should echo some arbitrary string. Single quote should be used rather than double quotes (but if double quotes are absolutely needed, protecting them with a backslash should probably work). What is printed by the interpreter doesn not need to be of a string type from the point of view of the interpreter; it could be a number or whatever as long as the output is an known sequence of characters.\r\n  let g:repl_send = 'echo REPL-VIM-INTERNAL-KEY'\r\n\r\nThe exact string to be caught from the previous command:\r\n  let g:repl_detect = 'REPL-VIM-INTERNAL-KEY'\r\n\r\nSome settings for using with various interpreters can be found there: https:\/\/gist.github.com\/baruchel\/9546517","first_name":"Thomas","6":"Thomas","last_name":"Baruchel","7":"Baruchel","releases":[{"0":"4887","vim_version":"7.0","1":"7.0","script_version":"1.4","2":"1.4","version_comment":"Release version.","3":"Release version.","package":"repl.vim","4":"repl.vim","src_id":"21605","5":"21605","creation_date":"1394620064","6":"1394620064"},{"0":"4887","vim_version":"7.0","1":"7.0","script_version":"1.3","2":"1.3","version_comment":"Fixed indentation issues in the REPL windows.","3":"Fixed indentation issues in the REPL windows.","package":"repl.vim","4":"repl.vim","src_id":"21604","5":"21604","creation_date":"1394614247","6":"1394614247"},{"0":"4887","vim_version":"7.0","1":"7.0","script_version":"1.2","2":"1.2","version_comment":"Fixed the bug concerning the subprocess remaining alive.","3":"Fixed the bug concerning the subprocess remaining alive.","package":"repl.vim","4":"repl.vim","src_id":"21602","5":"21602","creation_date":"1394584904","6":"1394584904"},{"0":"4887","vim_version":"7.0","1":"7.0","script_version":"1.1","2":"1.1","version_comment":"Added some support for highlighting the line while executed and restoring cursor position.","3":"Added some support for highlighting the line while executed and restoring cursor position.","package":"repl.vim","4":"repl.vim","src_id":"21601","5":"21601","creation_date":"1394580135","6":"1394580135"},{"0":"4887","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"repl.vim","4":"repl.vim","src_id":"21600","5":"21600","creation_date":"1394574227","6":"1394574227"}]},"4886":{"script_id":"4886","0":"4886","script_name":"ConsultADict.vim","1":"ConsultADict.vim","script_type":"utility","2":"utility","summary":"ConsultADict is plugin that provides easy way to consult a dictionary","3":"ConsultADict is plugin that provides easy way to consult a dictionary","description":"Consult A Dictionary is plugin that provides easy (IMHO) way to consult\r\ndictionaries (for example for translate words). It provides the following\r\nfuncionality:\r\n    * Search for words or phrases in dictionaries and displaying\r\n      dictionary entries in a separate window\r\n    * Use of Ex commands and hence shell-commands (for example \r\n      \"r!\/usr\/bin\/sdcv -n $$$_words\") for displaying dictionary entries.\r\n    * Search in dictionaries for:\r\n        - given word or phrase (:ConsultADict <words>);\r\n        - the word under the cursor (:ConsultADict or :ConsultADictToggle);\r\n        - the current selection in visual mode (:ConsultADict or :ConsultADictToggle)\r\n    * Search history (for current script run time)\r\n\r\nFor more information see :help ConsultADict\r\n","4":"Consult A Dictionary is plugin that provides easy (IMHO) way to consult\r\ndictionaries (for example for translate words). It provides the following\r\nfuncionality:\r\n    * Search for words or phrases in dictionaries and displaying\r\n      dictionary entries in a separate window\r\n    * Use of Ex commands and hence shell-commands (for example \r\n      \"r!\/usr\/bin\/sdcv -n $$$_words\") for displaying dictionary entries.\r\n    * Search in dictionaries for:\r\n        - given word or phrase (:ConsultADict <words>);\r\n        - the word under the cursor (:ConsultADict or :ConsultADictToggle);\r\n        - the current selection in visual mode (:ConsultADict or :ConsultADictToggle)\r\n    * Search history (for current script run time)\r\n\r\nFor more information see :help ConsultADict\r\n","install_details":"Extract the zip archive into your runtime dicrectory (for example ~\/.vim or\r\n~\/vimfiles for Windows). The archive contains the following two files:\r\n    plugin\/ConsultADict.vim,\r\n    doc\/ConsultADict.txt.\r\n\r\nNext, to finish installing the help file run:\r\n    :helptags <your_runtime_directory>\/doc\r\n\r\nIt needs to add at least one command to list of the commands for displaying\r\ndictionary entries before start using plugin.  Variable ConsultADict_cmd is\r\nused to define that list (you can set it in your vimrc file).\r\n\r\nEx commands and hence shell-commands (r!<shell_command>) are used for\r\ndisplaying dictionary entries.\r\nAs an example, let's use sdcv (simple, cross-platform text-base utility for\r\nwork with dictionaries) to define command for displaying dictionary entries:\r\n\r\n    :let ConsultADict_cmd = [\"r!\/usr\/bin\/sdcv -n $$$_words\"]\r\n\r\n$$$_words will be replaced with word or phrase to look it up in dictionaries.\r\n\r\nFor more information see :help ConsultADict_cmd and :help ConsultADictScripts\r\n","5":"Extract the zip archive into your runtime dicrectory (for example ~\/.vim or\r\n~\/vimfiles for Windows). The archive contains the following two files:\r\n    plugin\/ConsultADict.vim,\r\n    doc\/ConsultADict.txt.\r\n\r\nNext, to finish installing the help file run:\r\n    :helptags <your_runtime_directory>\/doc\r\n\r\nIt needs to add at least one command to list of the commands for displaying\r\ndictionary entries before start using plugin.  Variable ConsultADict_cmd is\r\nused to define that list (you can set it in your vimrc file).\r\n\r\nEx commands and hence shell-commands (r!<shell_command>) are used for\r\ndisplaying dictionary entries.\r\nAs an example, let's use sdcv (simple, cross-platform text-base utility for\r\nwork with dictionaries) to define command for displaying dictionary entries:\r\n\r\n    :let ConsultADict_cmd = [\"r!\/usr\/bin\/sdcv -n $$$_words\"]\r\n\r\n$$$_words will be replaced with word or phrase to look it up in dictionaries.\r\n\r\nFor more information see :help ConsultADict_cmd and :help ConsultADictScripts\r\n","first_name":"Dmitry","6":"Dmitry","last_name":"Ivanov","7":"Ivanov","releases":[{"0":"4886","vim_version":"7.0","1":"7.0","script_version":"0.9","2":"0.9","version_comment":"Bugfix: now plugin really displays dictionary entry in separate window","3":"Bugfix: now plugin really displays dictionary entry in separate window","package":"consultadict.zip","4":"consultadict.zip","src_id":"21618","5":"21618","creation_date":"1394912053","6":"1394912053"},{"0":"4886","vim_version":"7.0","1":"7.0","script_version":"0.801","2":"0.801","version_comment":"An unfortunate misprint was correted in documetation (ConsultADict.txt, Section 2 - Instalation)","3":"An unfortunate misprint was correted in documetation (ConsultADict.txt, Section 2 - Instalation)","package":"consultadict.zip","4":"consultadict.zip","src_id":"21590","5":"21590","creation_date":"1394462168","6":"1394462168"}]},"4885":{"script_id":"4885","0":"4885","script_name":"FilePathConvert","1":"FilePathConvert","script_type":"utility","2":"utility","summary":"Convert filespec between absolute, relative, and URL formats.","3":"Convert filespec between absolute, relative, and URL formats.","description":"DESCRIPTION\r\nThis plugin converts a file path and name that is inserted into the buffer\r\nbetween absolute and relative paths. This is especially useful after pasting\r\nin or completing (i_CTRL-X_CTRL-F) filespecs.\r\n\r\nRELATED WORKS\r\n- html_FileCompletion.vim (vimscript #4070) is insert mode completion of\r\n  URL-escaped file links relative to a document root and base URL.\r\n\r\nUSAGE\r\n<Leader>sf              Convert the file whose name is under or after the\r\n                        cursor to a more local one:\r\n                        URL -> [ UNC -> ] absolute -> relative (-> absolute)\r\n{Visual}<Leader>sf      Convert the selected file name.\r\n\r\n<Leader>sF              Convert the file whose name is under or after the\r\n                        cursor to a more global one:\r\n                        relative -> absolute  -> [ UNC -> ] URL (-> UNC \/ abs)\r\n{Visual}<Leader>sF      Convert the selected file name.\r\n\r\n                        A relative file path (..\/foo) is converted to an\r\n                        absolute one (\/home\/user\/dir\/foo).\r\n                        An absolute file path (\/home\/user\/dir\/foo) is\r\n                        converted to a relative one (..\/foo).\r\n                        On Windows, an absolute filespec starts with a drive\r\n                        letter (C:\\foo).\r\n                        A URL starts with a protocol like file:\/\/; the actual\r\n                        protocol is ignored here. Or it is a Windows file\r\n                        share in UNC notation (\\\\host\\share\\foo).\r\n                        Unless a mapping of URL prefix to mount point exists\r\n                        (see g:FilePathConvert_UrlMappings), this can only\r\n                        be mapped to a generic share in UNC notation.\r\n\r\nEXAMPLE\r\nHere's a simple illustration:\r\n    :cd C:\\Windows\\Temp\r\n    :edit test.txt\r\nThe text\r\n    C:\\Windows\\System32\\drivers\\etc\\hosts\r\nis turned into:\r\n    ..\\System32\\drivers\\etc\\hosts\r\nand\r\n    Cookies\\index.dat\r\nis turned into:\r\n    C:\\Windows\\Temp\\Cookies\\index.dat","4":"DESCRIPTION\r\nThis plugin converts a file path and name that is inserted into the buffer\r\nbetween absolute and relative paths. This is especially useful after pasting\r\nin or completing (i_CTRL-X_CTRL-F) filespecs.\r\n\r\nRELATED WORKS\r\n- html_FileCompletion.vim (vimscript #4070) is insert mode completion of\r\n  URL-escaped file links relative to a document root and base URL.\r\n\r\nUSAGE\r\n<Leader>sf              Convert the file whose name is under or after the\r\n                        cursor to a more local one:\r\n                        URL -> [ UNC -> ] absolute -> relative (-> absolute)\r\n{Visual}<Leader>sf      Convert the selected file name.\r\n\r\n<Leader>sF              Convert the file whose name is under or after the\r\n                        cursor to a more global one:\r\n                        relative -> absolute  -> [ UNC -> ] URL (-> UNC \/ abs)\r\n{Visual}<Leader>sF      Convert the selected file name.\r\n\r\n                        A relative file path (..\/foo) is converted to an\r\n                        absolute one (\/home\/user\/dir\/foo).\r\n                        An absolute file path (\/home\/user\/dir\/foo) is\r\n                        converted to a relative one (..\/foo).\r\n                        On Windows, an absolute filespec starts with a drive\r\n                        letter (C:\\foo).\r\n                        A URL starts with a protocol like file:\/\/; the actual\r\n                        protocol is ignored here. Or it is a Windows file\r\n                        share in UNC notation (\\\\host\\share\\foo).\r\n                        Unless a mapping of URL prefix to mount point exists\r\n                        (see g:FilePathConvert_UrlMappings), this can only\r\n                        be mapped to a generic share in UNC notation.\r\n\r\nEXAMPLE\r\nHere's a simple illustration:\r\n    :cd C:\\Windows\\Temp\r\n    :edit test.txt\r\nThe text\r\n    C:\\Windows\\System32\\drivers\\etc\\hosts\r\nis turned into:\r\n    ..\\System32\\drivers\\etc\\hosts\r\nand\r\n    Cookies\\index.dat\r\nis turned into:\r\n    C:\\Windows\\Temp\\Cookies\\index.dat","install_details":"INSTALLATION\r\nThis script is packaged as a vimball. If you have the \"gunzip\" decompressor\r\nin your PATH, simply edit the *.vmb.gz package in Vim; otherwise, decompress\r\nthe archive first, e.g. using WinZip. Inside Vim, install by sourcing the\r\nvimball or via the :UseVimball command.\r\n    vim FilePathConvert*.vmb.gz\r\n    :so %\r\nTo uninstall, use the :RmVimball command.\r\n\r\nDEPENDENCIES\r\n- Requires Vim 7.0 or higher.\r\n- Requires the ingo-library.vim plugin (vimscript #4433), version 1.019 or\r\n  higher.\r\n- Requires the TextTransform plugin (vimscript #4005), version 1.22 or higher.\r\n\r\nCONFIGURATION\r\nFor a permanent configuration, put the following commands into your vimrc:\r\n\r\nTo be able to convert custom URLs, non-file:\/\/ protocols, and UNC paths to a\r\nlocal file system path, you need to specify the mapping of the base URL to\r\nmount point(s; you can configure a list of filespecs to cater for symbolic\r\nlinks etc.):\r\n    let g:FilePathConvert_UrlMappings = {\r\n    \\   '\/\/win\/share': 'D:\/data',\r\n    \\   'file:\/\/\/\/\/lin\/www\/htdocs': '\/var\/srv\/htdocs',\r\n    \\   'http:\/\/lin\/': '\/var\/srv\/htdocs',\r\n    \\   'file:\/\/\/\/\/srv\/user': ['\/var\/srv\/user', '\/home\/user']\r\n    \\}\r\nAs the filespecs are system-specific, you probably want to define them for the\r\ncurrent host; the hostname() function can help to write a conditional in\r\ncase you're using a .vimrc shared across multiple systems.\r\nYou can override the global mapping with a buffer-local one, too.\r\n\r\nIf you just want to add a single mapping for the current buffer, you can do\r\nthat by defining both b:baseurl and b:basedir variables.\r\n\r\nIf you want to use different mappings, map your keys to the\r\n<Plug>TextTFilePathConvert#... mapping targets _before_ sourcing the script\r\n(e.g. in your vimrc):\r\n    nmap <Leader>sf <Plug>TextTFilePathConvert#FilePathConvertLine\r\n    xmap <Leader>sf <Plug>TextTFilePathConvert#FilePathConvertVisual","5":"INSTALLATION\r\nThis script is packaged as a vimball. If you have the \"gunzip\" decompressor\r\nin your PATH, simply edit the *.vmb.gz package in Vim; otherwise, decompress\r\nthe archive first, e.g. using WinZip. Inside Vim, install by sourcing the\r\nvimball or via the :UseVimball command.\r\n    vim FilePathConvert*.vmb.gz\r\n    :so %\r\nTo uninstall, use the :RmVimball command.\r\n\r\nDEPENDENCIES\r\n- Requires Vim 7.0 or higher.\r\n- Requires the ingo-library.vim plugin (vimscript #4433), version 1.019 or\r\n  higher.\r\n- Requires the TextTransform plugin (vimscript #4005), version 1.22 or higher.\r\n\r\nCONFIGURATION\r\nFor a permanent configuration, put the following commands into your vimrc:\r\n\r\nTo be able to convert custom URLs, non-file:\/\/ protocols, and UNC paths to a\r\nlocal file system path, you need to specify the mapping of the base URL to\r\nmount point(s; you can configure a list of filespecs to cater for symbolic\r\nlinks etc.):\r\n    let g:FilePathConvert_UrlMappings = {\r\n    \\   '\/\/win\/share': 'D:\/data',\r\n    \\   'file:\/\/\/\/\/lin\/www\/htdocs': '\/var\/srv\/htdocs',\r\n    \\   'http:\/\/lin\/': '\/var\/srv\/htdocs',\r\n    \\   'file:\/\/\/\/\/srv\/user': ['\/var\/srv\/user', '\/home\/user']\r\n    \\}\r\nAs the filespecs are system-specific, you probably want to define them for the\r\ncurrent host; the hostname() function can help to write a conditional in\r\ncase you're using a .vimrc shared across multiple systems.\r\nYou can override the global mapping with a buffer-local one, too.\r\n\r\nIf you just want to add a single mapping for the current buffer, you can do\r\nthat by defining both b:baseurl and b:basedir variables.\r\n\r\nIf you want to use different mappings, map your keys to the\r\n<Plug>TextTFilePathConvert#... mapping targets _before_ sourcing the script\r\n(e.g. in your vimrc):\r\n    nmap <Leader>sf <Plug>TextTFilePathConvert#FilePathConvertLine\r\n    xmap <Leader>sf <Plug>TextTFilePathConvert#FilePathConvertVisual","first_name":"Ingo","6":"Ingo","last_name":"Karkat","7":"Karkat","releases":[{"0":"4885","vim_version":"7.0","1":"7.0","script_version":"2.00","2":"2.00","version_comment":"- Add <Leader>sF variant that converts into more global filespecs to support file:\/\/ URLs.\r\n- Handle conversion to \/ from UNC and URL paths via URL mappings configuation g:FilePathConvert_UrlMappings. *** You need to update to ingo-library (vimscript #4433) version 1.019! ***","3":"- Add <Leader>sF variant that converts into more global filespecs to support file:\/\/ URLs.\r\n- Handle conversion to \/ from UNC and URL paths via URL mappings configuation g:FilePathConvert_UrlMappings. *** You need to update to ingo-library (vimscript #4433) version 1.019! ***","package":"FilePathConvert-2.00.vmb.gz","4":"FilePathConvert-2.00.vmb.gz","src_id":"21969","5":"21969","creation_date":"1401561867","6":"1401561867"},{"0":"4885","vim_version":"7.0","1":"7.0","script_version":"1.00","2":"1.00","version_comment":"Initial upload","3":"Initial upload","package":"FilePathConvert-1.00.vmb.gz","4":"FilePathConvert-1.00.vmb.gz","src_id":"21575","5":"21575","creation_date":"1394116086","6":"1394116086"}]},"4884":{"script_id":"4884","0":"4884","script_name":"ctrlp-py-matcher","1":"ctrlp-py-matcher","script_type":"utility","2":"utility","summary":"Fast matcher for CtrlP plugin written in python.","3":"Fast matcher for CtrlP plugin written in python.","description":"*pymatcher* is a replacement for standard fuzzy matcher provided with CtrlP\r\nbecause of its performance issues on huge projects. Tested on 350k files.\r\nSome queries causes |CtrlP|'s standard matcher freezes up to 15 seconds. This\r\nmatcher provides ~700ms performance on the same hardware with same queries.\r\nPull requests to improve above performance are much appreciated.\r\n\r\nOfficial repository:\r\nhttps:\/\/github.com\/FelikZ\/ctrlp-py-matcher","4":"*pymatcher* is a replacement for standard fuzzy matcher provided with CtrlP\r\nbecause of its performance issues on huge projects. Tested on 350k files.\r\nSome queries causes |CtrlP|'s standard matcher freezes up to 15 seconds. This\r\nmatcher provides ~700ms performance on the same hardware with same queries.\r\nPull requests to improve above performance are much appreciated.\r\n\r\nOfficial repository:\r\nhttps:\/\/github.com\/FelikZ\/ctrlp-py-matcher","install_details":"","5":"","first_name":"Oleksii","6":"Oleksii","last_name":"Shevchenko","7":"Shevchenko","releases":[{"0":"4884","vim_version":"7.0","1":"7.0","script_version":"v1.1.0","2":"v1.1.0","version_comment":"- Improved performance\r\n- Fixed uppercase issue (see #29)\r\n- Added licence","3":"- Improved performance\r\n- Fixed uppercase issue (see #29)\r\n- Added licence","package":"ctrlp-py-matcher-1.1.0.zip","4":"ctrlp-py-matcher-1.1.0.zip","src_id":"24341","5":"24341","creation_date":"1466592206","6":"1466592206"},{"0":"4884","vim_version":"7.0","1":"7.0","script_version":"1.0d","2":"1.0d","version_comment":"Bugfixes & stability improvements","3":"Bugfixes & stability improvements","package":"ctrlp-py-matcher-1.0d.zip","4":"ctrlp-py-matcher-1.0d.zip","src_id":"23229","5":"23229","creation_date":"1430080002","6":"1430080002"},{"0":"4884","vim_version":"7.4","1":"7.4","script_version":"1.0c","2":"1.0c","version_comment":" - Added python3 compatibility\r\n - Improved better memory usage via #8 ( use heapq to find n best results )\r\n","3":" - Added python3 compatibility\r\n - Improved better memory usage via #8 ( use heapq to find n best results )\r\n","package":"ctrlp-py-matcher-1.0c.zip","4":"ctrlp-py-matcher-1.0c.zip","src_id":"22440","5":"22440","creation_date":"1411117976","6":"1411117976"},{"0":"4884","vim_version":"7.4","1":"7.4","script_version":"1.0b","2":"1.0b","version_comment":"- Added support for <c-d> and <c-f> modes\r\n- Improved matching algorithm for all modes","3":"- Added support for <c-d> and <c-f> modes\r\n- Improved matching algorithm for all modes","package":"ctrlp-py-matcher-1.0b.zip","4":"ctrlp-py-matcher-1.0b.zip","src_id":"21883","5":"21883","creation_date":"1400101401","6":"1400101401"},{"0":"4884","vim_version":"7.3","1":"7.3","script_version":"0.9b","2":"0.9b","version_comment":"Initial upload","3":"Initial upload","package":"ctrlp-py-matcher-0.9b.zip","4":"ctrlp-py-matcher-0.9b.zip","src_id":"21571","5":"21571","creation_date":"1393977463","6":"1393977463"}]},"4883":{"script_id":"4883","0":"4883","script_name":"pipe2eval","1":"pipe2eval","script_type":"utility","2":"utility","summary":"simple REPL inside vim","3":"simple REPL inside vim","description":"simple REPL inside vim\r\n\r\ndemo coffeescript:\r\n\r\nhttps:\/\/github.com\/zweifisch\/pipe2eval\/raw\/master\/demos\/coffee.gif\r\n\r\ndemo mysql:\r\n\r\nhttps:\/\/github.com\/zweifisch\/pipe2eval\/raw\/master\/demos\/mysql.gif\r\n\r\nusage\r\n\r\npress V<space> to evaluate current line, vip<space> to evaluate a paragraph\r\n\r\nto specify a diffrent filetype use the Pipe2 command :Pipe2 redis, :Pipe2 mongo ...\r\n\r\nevaluate an empty line will clear the context\r\n\r\nmore info: https:\/\/github.com\/zweifisch\/pipe2eval","4":"simple REPL inside vim\r\n\r\ndemo coffeescript:\r\n\r\nhttps:\/\/github.com\/zweifisch\/pipe2eval\/raw\/master\/demos\/coffee.gif\r\n\r\ndemo mysql:\r\n\r\nhttps:\/\/github.com\/zweifisch\/pipe2eval\/raw\/master\/demos\/mysql.gif\r\n\r\nusage\r\n\r\npress V<space> to evaluate current line, vip<space> to evaluate a paragraph\r\n\r\nto specify a diffrent filetype use the Pipe2 command :Pipe2 redis, :Pipe2 mongo ...\r\n\r\nevaluate an empty line will clear the context\r\n\r\nmore info: https:\/\/github.com\/zweifisch\/pipe2eval","install_details":"Extract to ~\/.vim\r\n\r\nthe latest version can be installed via vundle\r\n\r\nBundle \"zweifisch\/pipe2eval\"\r\n\r\ntempfiles are put to \/dev\/shm\/ by default, export PIP2EVAL_TMP_FILE_PATH to override.\r\n\r\nOn Mac OS X, \/dev\/ is highly locked down permissions wise. If you're on OS X it's recommended to use another folder, such as \/tmp\/shms or similar (you'll have to create it). To this by adding export PIP2EVAL_TMP_FILE_PATH=\/tmp\/shms to your Bash\/ZSH RC file.\r\n","5":"Extract to ~\/.vim\r\n\r\nthe latest version can be installed via vundle\r\n\r\nBundle \"zweifisch\/pipe2eval\"\r\n\r\ntempfiles are put to \/dev\/shm\/ by default, export PIP2EVAL_TMP_FILE_PATH to override.\r\n\r\nOn Mac OS X, \/dev\/ is highly locked down permissions wise. If you're on OS X it's recommended to use another folder, such as \/tmp\/shms or similar (you'll have to create it). To this by adding export PIP2EVAL_TMP_FILE_PATH=\/tmp\/shms to your Bash\/ZSH RC file.\r\n","first_name":"Feng","6":"Feng","last_name":"Zhou","7":"Zhou","releases":[{"0":"4883","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"pip2eval.zip","4":"pip2eval.zip","src_id":"21569","5":"21569","creation_date":"1393910764","6":"1393910764"}]},"4882":{"script_id":"4882","0":"4882","script_name":"wipeout","1":"wipeout","script_type":"utility","2":"utility","summary":"Destroy all buffers that are not open in any tabs or windows.","3":"Destroy all buffers that are not open in any tabs or windows.","description":"Destroy all buffers that are not open in any tabs or windows.\r\n\r\nUsage\r\n\r\n    :Wipeout","4":"Destroy all buffers that are not open in any tabs or windows.\r\n\r\nUsage\r\n\r\n    :Wipeout","install_details":"","5":"","first_name":"Artem","6":"Artem","last_name":"Nezvigin","7":"Nezvigin","releases":[{"0":"4882","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"wipeout.vim","4":"wipeout.vim","src_id":"21566","5":"21566","creation_date":"1393805144","6":"1393805144"}]},"4881":{"script_id":"4881","0":"4881","script_name":"patternjump","1":"patternjump","script_type":"utility","2":"utility","summary":"Move cursor as you like.","3":"Move cursor as you like.","description":"Patternjump give you a effective way to move cursor in various modes. The rules to move cursor can be easily optimized by using regular expression. Those rules defined by regular expression are called patterns in this introduction. Numbers of patterns can be registered and cursor would be moved to the closest candidate in them. This plugin serves two keymappings.  One searches candidates for forward direction, and the other searches them for backward direction.\r\n\r\nSuppose that your cursor is on the first character of a line like this:\r\n\r\n    let foo = \"bar\"\r\n\r\nIf you define a pattern \"bar\", of course, it matches with \"bar\". Thus using the keymapping which searches candidates in forward direction, cursor will move on a word \"bar\". Here I should say there are two types of patterns, head-patterns and tail-patterns. All the patterns should belong to either head or tail patterns, you can choose which when you register a new pattern. If \"bar\" belongs to head-patterns, cursor will move on 'b' of \"bar\". And if \"bar\" belongs to tail-patterns, cursor will move on 'r' of \"bar\".\r\n\r\n    head-pattern :\r\n        let foo = \"#bar\"                         '#' represents cursor position\r\n\r\n    tail-pattern :\r\n        let foo = \"bar#\"                         '#' represents cursor position\r\n\r\nI guess you have found that the pattern \"bar\" seems like not useful. So \"bar\" is not included in default patterns. Alternatively, a pattern '\\<\\h\\k\\+\\>' is included in default patterns. This pattern matches with a independent word determined by the option 'iskeyword' in a source code.  Therefore cursor will stop at \"let\", \"foo\", \"bar\". I think they are the very what we want to correct when we review a source code in many cases.\r\n\r\nLatest version : https:\/\/github.com\/machakann\/vim-patternjump","4":"Patternjump give you a effective way to move cursor in various modes. The rules to move cursor can be easily optimized by using regular expression. Those rules defined by regular expression are called patterns in this introduction. Numbers of patterns can be registered and cursor would be moved to the closest candidate in them. This plugin serves two keymappings.  One searches candidates for forward direction, and the other searches them for backward direction.\r\n\r\nSuppose that your cursor is on the first character of a line like this:\r\n\r\n    let foo = \"bar\"\r\n\r\nIf you define a pattern \"bar\", of course, it matches with \"bar\". Thus using the keymapping which searches candidates in forward direction, cursor will move on a word \"bar\". Here I should say there are two types of patterns, head-patterns and tail-patterns. All the patterns should belong to either head or tail patterns, you can choose which when you register a new pattern. If \"bar\" belongs to head-patterns, cursor will move on 'b' of \"bar\". And if \"bar\" belongs to tail-patterns, cursor will move on 'r' of \"bar\".\r\n\r\n    head-pattern :\r\n        let foo = \"#bar\"                         '#' represents cursor position\r\n\r\n    tail-pattern :\r\n        let foo = \"bar#\"                         '#' represents cursor position\r\n\r\nI guess you have found that the pattern \"bar\" seems like not useful. So \"bar\" is not included in default patterns. Alternatively, a pattern '\\<\\h\\k\\+\\>' is included in default patterns. This pattern matches with a independent word determined by the option 'iskeyword' in a source code.  Therefore cursor will stop at \"let\", \"foo\", \"bar\". I think they are the very what we want to correct when we review a source code in many cases.\r\n\r\nLatest version : https:\/\/github.com\/machakann\/vim-patternjump","install_details":"Unzip and just put all folders in your ~\/.vim.","5":"Unzip and just put all folders in your ~\/.vim.","first_name":"Masaaki","6":"Masaaki","last_name":"Nakamura","7":"Nakamura","releases":[{"0":"4881","vim_version":"7.4","1":"7.4","script_version":"2.1.1","2":"2.1.1","version_comment":"Bug fixes.","3":"Bug fixes.","package":"patternjump-2.1.1.zip","4":"patternjump-2.1.1.zip","src_id":"23657","5":"23657","creation_date":"1444375160","6":"1444375160"},{"0":"4881","vim_version":"7.4","1":"7.4","script_version":"2.1.0","2":"2.1.0","version_comment":" Implement new search engine.\r\n    * obsolete 'wrap_line' option\r\n    * obsolete 'move_afap' option\r\n    * obsolete 'swap_head_tail' option\r\n    * obsolete 'cache_name' option\r\n    * add 'timeout' option","3":" Implement new search engine.\r\n    * obsolete 'wrap_line' option\r\n    * obsolete 'move_afap' option\r\n    * obsolete 'swap_head_tail' option\r\n    * obsolete 'cache_name' option\r\n    * add 'timeout' option","package":"patternjump-2.1.0.zip","4":"patternjump-2.1.0.zip","src_id":"22956","5":"22956","creation_date":"1425042921","6":"1425042921"},{"0":"4881","vim_version":"7.0","1":"7.0","script_version":"2.0.1","2":"2.0.1","version_comment":"Fix a bug on backward searching.","3":"Fix a bug on backward searching.","package":"patternjump-2.0.1.zip","4":"patternjump-2.0.1.zip","src_id":"22070","5":"22070","creation_date":"1403322553","6":"1403322553"},{"0":"4881","vim_version":"7.0","1":"7.0","script_version":"2.0.0","2":"2.0.0","version_comment":"* Bug fixes.\r\n* New feature : now patternjump can move cursor to vicinal lines.","3":"* Bug fixes.\r\n* New feature : now patternjump can move cursor to vicinal lines.","package":"patternjump-2.0.0.zip","4":"patternjump-2.0.0.zip","src_id":"21740","5":"21740","creation_date":"1396778028","6":"1396778028"},{"0":"4881","vim_version":"7.0","1":"7.0","script_version":"1.0.3","2":"1.0.3","version_comment":"Fix the bug with 'set encoding=utf-8' environments.","3":"Fix the bug with 'set encoding=utf-8' environments.","package":"patternjump-1.0.3.zip","4":"patternjump-1.0.3.zip","src_id":"21670","5":"21670","creation_date":"1395832019","6":"1395832019"},{"0":"4881","vim_version":"7.0","1":"7.0","script_version":"1.0.2","2":"1.0.2","version_comment":"Bug fixes.","3":"Bug fixes.","package":"patternjump-1.0.2.zip","4":"patternjump-1.0.2.zip","src_id":"21591","5":"21591","creation_date":"1394463488","6":"1394463488"},{"0":"4881","vim_version":"7.0","1":"7.0","script_version":"1.0.1","2":"1.0.1","version_comment":"Bug fixes.","3":"Bug fixes.","package":"patternjump-1.0.1.zip","4":"patternjump-1.0.1.zip","src_id":"21580","5":"21580","creation_date":"1394294969","6":"1394294969"},{"0":"4881","vim_version":"7.0","1":"7.0","script_version":"1.0.0","2":"1.0.0","version_comment":"Initial upload","3":"Initial upload","package":"patternjump-1.0.0.zip","4":"patternjump-1.0.0.zip","src_id":"21565","5":"21565","creation_date":"1393775974","6":"1393775974"}]},"4880":{"script_id":"4880","0":"4880","script_name":"columnmove","1":"columnmove","script_type":"utility","2":"utility","summary":"Bring cursor vertically in similar ways as line-wise commands.","3":"Bring cursor vertically in similar ways as line-wise commands.","description":"columnmove serves you several keymappings specialized for moving cursor in vertical direction.\r\n\r\n*** columnmove-f and its variants ***\r\ncolumnmove-f and its variants are the commands for bringing cursor to the position assigned by a character in the same column. This group has six keymappings, that is, \"columnmove-f\", \"columnmove-t\", \"columnmove-F\", \"columnmove-T\", \"columnmove-;\", \"columnmove-,\".  Each of them are the imitations of \"f\", \"t\", \"F\", \"T\", \";\", \",\" command, but work in vertical direction, not in line-wise.\r\n\r\n*** columnmove-w and its variants ***\r\ncolumnmove-w and its variants are the commands for moving cursor in word-wise. This group has four keymappings, that is, \"columnmove-w\", \"columnmove-b\", \"columnmove-e\", \"columnmove-ge\". Each of them are the imitations of \"w\", \"b\", \"e\", \"ge\", but work in vertical direction. These commands regard the column which cursor is on as a line and search for the head or tail of word to move.\r\n\r\nLatest version : https:\/\/github.com\/machakann\/vim-columnmove\r\n","4":"columnmove serves you several keymappings specialized for moving cursor in vertical direction.\r\n\r\n*** columnmove-f and its variants ***\r\ncolumnmove-f and its variants are the commands for bringing cursor to the position assigned by a character in the same column. This group has six keymappings, that is, \"columnmove-f\", \"columnmove-t\", \"columnmove-F\", \"columnmove-T\", \"columnmove-;\", \"columnmove-,\".  Each of them are the imitations of \"f\", \"t\", \"F\", \"T\", \";\", \",\" command, but work in vertical direction, not in line-wise.\r\n\r\n*** columnmove-w and its variants ***\r\ncolumnmove-w and its variants are the commands for moving cursor in word-wise. This group has four keymappings, that is, \"columnmove-w\", \"columnmove-b\", \"columnmove-e\", \"columnmove-ge\". Each of them are the imitations of \"w\", \"b\", \"e\", \"ge\", but work in vertical direction. These commands regard the column which cursor is on as a line and search for the head or tail of word to move.\r\n\r\nLatest version : https:\/\/github.com\/machakann\/vim-columnmove\r\n","install_details":"Unzip and just put all folders in your ~\/.vim.","5":"Unzip and just put all folders in your ~\/.vim.","first_name":"Masaaki","6":"Masaaki","last_name":"Nakamura","7":"Nakamura","releases":[{"0":"4880","vim_version":"7.4","1":"7.4","script_version":"1.2.0","2":"1.2.0","version_comment":"- Obsolete g:columnmove_expand_range.\r\n- Obsolete g:columnmove_auto_scroll.\r\n- Define highlight group 'ColumnmoveCandidate'.\r\n- Change the order of arguments of columnmove#[ftFT]().\r\n- Change the order of arguments of columnmove#utility#map().","3":"- Obsolete g:columnmove_expand_range.\r\n- Obsolete g:columnmove_auto_scroll.\r\n- Define highlight group 'ColumnmoveCandidate'.\r\n- Change the order of arguments of columnmove#[ftFT]().\r\n- Change the order of arguments of columnmove#utility#map().","package":"vim-columnmove-1.2.0.zip","4":"vim-columnmove-1.2.0.zip","src_id":"24125","5":"24125","creation_date":"1458452037","6":"1458452037"},{"0":"4880","vim_version":"7.4","1":"7.4","script_version":"1.1.2","2":"1.1.2","version_comment":"* Bug fixes.\r\n* Add utility function to define keymappings. (columnmove#utility#map())","3":"* Bug fixes.\r\n* Add utility function to define keymappings. (columnmove#utility#map())","package":"columnmove-1.1.2.zip","4":"columnmove-1.1.2.zip","src_id":"23658","5":"23658","creation_date":"1444375698","6":"1444375698"},{"0":"4880","vim_version":"7.4","1":"7.4","script_version":"1.1.1","2":"1.1.1","version_comment":"* Bug fixes.","3":"* Bug fixes.","package":"columnmove-1.1.1.zip","4":"columnmove-1.1.1.zip","src_id":"22426","5":"22426","creation_date":"1410703927","6":"1410703927"},{"0":"4880","vim_version":"7.4","1":"7.4","script_version":"1.1.0","2":"1.1.0","version_comment":"*   Bug fixes.\r\n*   Add new keymappings (columnmove-W, B, E, gE).\r\n*   Now columnmove-f, t, F, T can be repeated by dot command.\r\n*   Abolish 'raw' option.","3":"*   Bug fixes.\r\n*   Add new keymappings (columnmove-W, B, E, gE).\r\n*   Now columnmove-f, t, F, T can be repeated by dot command.\r\n*   Abolish 'raw' option.","package":"columnmove-1.1.0.zip","4":"columnmove-1.1.0.zip","src_id":"22341","5":"22341","creation_date":"1408291926","6":"1408291926"},{"0":"4880","vim_version":"7.0","1":"7.0","script_version":"1.0.2","2":"1.0.2","version_comment":"Bug fixes.","3":"Bug fixes.","package":"columnmove-1.0.2.zip","4":"columnmove-1.0.2.zip","src_id":"21592","5":"21592","creation_date":"1394463528","6":"1394463528"},{"0":"4880","vim_version":"7.0","1":"7.0","script_version":"1.0.1","2":"1.0.1","version_comment":"Bug fixes.","3":"Bug fixes.","package":"columnmove-1.0.1.zip","4":"columnmove-1.0.1.zip","src_id":"21581","5":"21581","creation_date":"1394295040","6":"1394295040"},{"0":"4880","vim_version":"7.0","1":"7.0","script_version":"1.0.0","2":"1.0.0","version_comment":"Initial upload","3":"Initial upload","package":"columnmove-1.0.0.zip","4":"columnmove-1.0.0.zip","src_id":"21564","5":"21564","creation_date":"1393775044","6":"1393775044"}]},"4879":{"script_id":"4879","0":"4879","script_name":"vim-autoflake","1":"vim-autoflake","script_type":"ftplugin","2":"ftplugin","summary":"vim-autoflake is a Vim plugin that applies autoflake to your current file. ","3":"vim-autoflake is a Vim plugin that applies autoflake to your current file. ","description":"vim-autoflake is a Vim plugin that applies autoflake to your current file. \r\n\r\nautoflake remove unused imports and unused variables as reported by pyflakes.\r\n\r\nsee also https:\/\/github.com\/tell-k\/vim-autoflake\r\n\r\ndocumentation https:\/\/vim-autoflake.readthedocs.org\/en\/latest\/","4":"vim-autoflake is a Vim plugin that applies autoflake to your current file. \r\n\r\nautoflake remove unused imports and unused variables as reported by pyflakes.\r\n\r\nsee also https:\/\/github.com\/tell-k\/vim-autoflake\r\n\r\ndocumentation https:\/\/vim-autoflake.readthedocs.org\/en\/latest\/","install_details":"simply put the contents of this repository in your ~\/.vim\/bundle directory.","5":"simply put the contents of this repository in your ~\/.vim\/bundle directory.","first_name":"tell","6":"tell","last_name":"k","7":"k","releases":[{"0":"4879","vim_version":"7.0","1":"7.0","script_version":"1.0.1","2":"1.0.1","version_comment":"#1 No need to file scope variables.\r\nhttps:\/\/github.com\/tell-k\/vim-autoflake\/issues\/1","3":"#1 No need to file scope variables.\r\nhttps:\/\/github.com\/tell-k\/vim-autoflake\/issues\/1","package":"vim-autoflake.zip","4":"vim-autoflake.zip","src_id":"22444","5":"22444","creation_date":"1411145118","6":"1411145118"},{"0":"4879","vim_version":"7.0","1":"7.0","script_version":"1.0.0","2":"1.0.0","version_comment":"Initial upload","3":"Initial upload","package":"vim-autoflake.zip","4":"vim-autoflake.zip","src_id":"21562","5":"21562","creation_date":"1393771045","6":"1393771045"}]},"4878":{"script_id":"4878","0":"4878","script_name":"Abridge","1":"Abridge","script_type":"utility","2":"utility","summary":"Vim code snippets creation made easy","3":"Vim code snippets creation made easy","description":"Easily create custom snippets automatically expanded when recognized, or use the default ones provided. No need to hit <TAB> or some other key combinations.\r\n\r\nSee GitHub for most recent version : https:\/\/github.com\/justindomingue\/Abridge\r\nAnimated screenshot : https:\/\/github.com\/justindomingue\/Abridge\/blob\/master\/screenshot.gif\r\n\r\n= Example Workflow\r\n\r\nIn a c or c++ file,\r\n\r\n      for<space>i = 0,,i < 10,,++i,,\r\n\r\nwill become\r\n\r\n      for(i = 0; i < 10; ++i) {\r\n      \r\n       }\r\n\r\nOnce you hit <space>, vim recognized `for` and expands the snippet as defined in abridge.vim (easily modified). \",,\" selects the next placeholder (you could change it to <TAB> if you wanted, see below).\r\n\r\n= Usage\r\n\r\nAbridge comes with some default snippets. The goal is not to be exahaustive, but rather to define commonly use snippets.\r\n\r\nYou can define your own very easily. Add the command in your .vimrc :\r\n\r\ncall Abridge(\"to\", \"from\", \"filetype\")\r\n        from : abbreviation (contains <1> - see note below)\r\n          to : expanded expression\r\n    filetype : file type on which to apply the abbreviation ('*' for all file types)\r\nThis command will create an abbreviation for to which will expand to from in file with type filetype.\r\n\r\nNote from must contain <1>. This is where the cursor will be positioned after the expansion.\r\n\r\nFor example,\r\n\r\ncall Abridge(\"for\",\"for(<1>; <2>; <3>) {<CR><4><CR>}\", \"c,cpp\")\r\nwill expand for<non-keyword character> to\r\n\r\nfor(<1>; <2>; <3>) {\r\n  <4>\r\n}\r\nNote <non-keyword character> helps vim recognize the abbreviation : <ESC>, <CR>, <space>\r\n\r\n- Mapping\r\n\r\n,, : go to next <\\d> and substitute (if not match is found, insert \",,\")\r\n\r\n-- Disable Mapping\r\n\r\nTo overwrite the mapping keys, set g:abridge_map_keys to your preferred keys. For example,\r\n\r\nlet g:abridge_map_keys = \"<tab>\"\r\n\r\n-- Disable Default Snippets\r\n\r\nAdd let abridge_default_abb = 0 to your vimrc.","4":"Easily create custom snippets automatically expanded when recognized, or use the default ones provided. No need to hit <TAB> or some other key combinations.\r\n\r\nSee GitHub for most recent version : https:\/\/github.com\/justindomingue\/Abridge\r\nAnimated screenshot : https:\/\/github.com\/justindomingue\/Abridge\/blob\/master\/screenshot.gif\r\n\r\n= Example Workflow\r\n\r\nIn a c or c++ file,\r\n\r\n      for<space>i = 0,,i < 10,,++i,,\r\n\r\nwill become\r\n\r\n      for(i = 0; i < 10; ++i) {\r\n      \r\n       }\r\n\r\nOnce you hit <space>, vim recognized `for` and expands the snippet as defined in abridge.vim (easily modified). \",,\" selects the next placeholder (you could change it to <TAB> if you wanted, see below).\r\n\r\n= Usage\r\n\r\nAbridge comes with some default snippets. The goal is not to be exahaustive, but rather to define commonly use snippets.\r\n\r\nYou can define your own very easily. Add the command in your .vimrc :\r\n\r\ncall Abridge(\"to\", \"from\", \"filetype\")\r\n        from : abbreviation (contains <1> - see note below)\r\n          to : expanded expression\r\n    filetype : file type on which to apply the abbreviation ('*' for all file types)\r\nThis command will create an abbreviation for to which will expand to from in file with type filetype.\r\n\r\nNote from must contain <1>. This is where the cursor will be positioned after the expansion.\r\n\r\nFor example,\r\n\r\ncall Abridge(\"for\",\"for(<1>; <2>; <3>) {<CR><4><CR>}\", \"c,cpp\")\r\nwill expand for<non-keyword character> to\r\n\r\nfor(<1>; <2>; <3>) {\r\n  <4>\r\n}\r\nNote <non-keyword character> helps vim recognize the abbreviation : <ESC>, <CR>, <space>\r\n\r\n- Mapping\r\n\r\n,, : go to next <\\d> and substitute (if not match is found, insert \",,\")\r\n\r\n-- Disable Mapping\r\n\r\nTo overwrite the mapping keys, set g:abridge_map_keys to your preferred keys. For example,\r\n\r\nlet g:abridge_map_keys = \"<tab>\"\r\n\r\n-- Disable Default Snippets\r\n\r\nAdd let abridge_default_abb = 0 to your vimrc.","install_details":"Either copy plugin\/abridge.vim to ~\/.vim\/plugin\/ or use pathogen :\r\n\r\n    cd ~\/.vim\/bundle\/\r\n    git clone https:\/\/github.com\/justindomingue\/Abridge.git","5":"Either copy plugin\/abridge.vim to ~\/.vim\/plugin\/ or use pathogen :\r\n\r\n    cd ~\/.vim\/bundle\/\r\n    git clone https:\/\/github.com\/justindomingue\/Abridge.git","first_name":"Justin","6":"Justin","last_name":"Domingue","7":"Domingue","releases":[{"0":"4878","vim_version":"7.0","1":"7.0","script_version":"0.4","2":"0.4","version_comment":"Added SelectNextIfSage() which selects next only if match found","3":"Added SelectNextIfSage() which selects next only if match found","package":"abridge.vim","4":"abridge.vim","src_id":"21555","5":"21555","creation_date":"1393700561","6":"1393700561"},{"0":"4878","vim_version":"7.0","1":"7.0","script_version":"0.3","2":"0.3","version_comment":"Fixed a bug","3":"Fixed a bug","package":"abridge.vim","4":"abridge.vim","src_id":"21554","5":"21554","creation_date":"1393696728","6":"1393696728"},{"0":"4878","vim_version":"7.0","1":"7.0","script_version":"0.2","2":"0.2","version_comment":"Initial upload","3":"Initial upload","package":"abridge.vim","4":"abridge.vim","src_id":"21548","5":"21548","creation_date":"1393636646","6":"1393636646"}]},"4877":{"script_id":"4877","0":"4877","script_name":"magnum.vim","1":"magnum.vim","script_type":"utility","2":"utility","summary":"Pure Vim script big integer library","3":"Pure Vim script big integer library","description":"Magnum is a big integer library for Vim plugins written entirely in Vim script. Currently it provides just a small set of predicates, arithmetic, and conversion operations. It also includes a simple random number generator.\r\n\r\nComplete documentation is included and can be accessed via \":h magnum\".\r\n\r\nAdditional materials (usage examples, test suite, references) are available at the plugin home on GitHub.\r\nhttps:\/\/github.com\/glts\/vim-magnum\r\n","4":"Magnum is a big integer library for Vim plugins written entirely in Vim script. Currently it provides just a small set of predicates, arithmetic, and conversion operations. It also includes a simple random number generator.\r\n\r\nComplete documentation is included and can be accessed via \":h magnum\".\r\n\r\nAdditional materials (usage examples, test suite, references) are available at the plugin home on GitHub.\r\nhttps:\/\/github.com\/glts\/vim-magnum\r\n","install_details":"Unzip the archive in your ~\/.vim directory. (On Windows, replace \"~\/.vim\" with \"%HOME%\\vimfiles\".)\r\n\r\nIf you use a plugin management system use the installation procedure appropriate to your setup.\r\n\r\nFor example, with pathogen.vim the installation goes simply:\r\n\r\ngit clone https:\/\/github.com\/glts\/vim-magnum.git ~\/.vim\/bundle\/magnum\r\n","5":"Unzip the archive in your ~\/.vim directory. (On Windows, replace \"~\/.vim\" with \"%HOME%\\vimfiles\".)\r\n\r\nIf you use a plugin management system use the installation procedure appropriate to your setup.\r\n\r\nFor example, with pathogen.vim the installation goes simply:\r\n\r\ngit clone https:\/\/github.com\/glts\/vim-magnum.git ~\/.vim\/bundle\/magnum\r\n","first_name":"David","6":"David","last_name":"B\u00c3\u00bcrgin","7":"B\u00c3\u00bcrgin","releases":[{"0":"4877","vim_version":"7.3","1":"7.3","script_version":"2.1.1","2":"2.1.1","version_comment":"Updated contact info (no changes)","3":"Updated contact info (no changes)","package":"magnum-2.1.1.zip","4":"magnum-2.1.1.zip","src_id":"26824","5":"26824","creation_date":"1573604797","6":"1573604797"},{"0":"4877","vim_version":"7.3","1":"7.3","script_version":"2.1.0","2":"2.1.0","version_comment":"Changed magnum#random#NextInt to accept arbitrary range\r\nAdded support for +num64 feature\r\n","3":"Changed magnum#random#NextInt to accept arbitrary range\r\nAdded support for +num64 feature\r\n","package":"magnum-2.1.0.zip","4":"magnum-2.1.0.zip","src_id":"24364","5":"24364","creation_date":"1468137750","6":"1468137750"},{"0":"4877","vim_version":"7.3","1":"7.3","script_version":"2.0.0","2":"2.0.0","version_comment":"Removed dependency on Maktaba\r\nChanged exception values to start with \"magnum:\" (breaking change)","3":"Removed dependency on Maktaba\r\nChanged exception values to start with \"magnum:\" (breaking change)","package":"magnum-2.0.0.zip","4":"magnum-2.0.0.zip","src_id":"24340","5":"24340","creation_date":"1466535074","6":"1466535074"},{"0":"4877","vim_version":"7.3","1":"7.3","script_version":"1.1.0","2":"1.1.0","version_comment":"Added random number generator\r\n","3":"Added random number generator\r\n","package":"magnum-1.1.0.zip","4":"magnum-1.1.0.zip","src_id":"22479","5":"22479","creation_date":"1412360904","6":"1412360904"},{"0":"4877","vim_version":"7.3","1":"7.3","script_version":"1.0.2","2":"1.0.2","version_comment":"Improved uncaught exception messages","3":"Improved uncaught exception messages","package":"magnum-1.0.2.zip","4":"magnum-1.0.2.zip","src_id":"22214","5":"22214","creation_date":"1405762765","6":"1405762765"},{"0":"4877","vim_version":"7.3","1":"7.3","script_version":"1.0.1","2":"1.0.1","version_comment":"Removed undocumented exception in Integer.Pow\r\nImproved performance of Integer.Pow\r\n","3":"Removed undocumented exception in Integer.Pow\r\nImproved performance of Integer.Pow\r\n","package":"magnum-1.0.1.zip","4":"magnum-1.0.1.zip","src_id":"22026","5":"22026","creation_date":"1402762564","6":"1402762564"},{"0":"4877","vim_version":"7.3","1":"7.3","script_version":"1.0.0","2":"1.0.0","version_comment":"Initial upload","3":"Initial upload","package":"magnum-1.0.0.zip","4":"magnum-1.0.0.zip","src_id":"21547","5":"21547","creation_date":"1393615578","6":"1393615578"}]},"4876":{"script_id":"4876","0":"4876","script_name":"TWcmd.vim","1":"TWcmd.vim","script_type":"utility","2":"utility","summary":"wincmd-style tab \/ window moving commands.","3":"wincmd-style tab \/ window moving commands.","description":"More information : https:\/\/github.com\/yssl\/twcmd.vim\r\n\r\n# twcmd.vim \r\n\r\ntwcmd.vim is a set of useful commands for moving & managing tabs and windows in vim.\r\n\r\n- Move a tab \/ window\r\nhttps:\/\/cloud.githubusercontent.com\/assets\/5915359\/3844245\/89017712-1e47-11e4-9f19-089d56a035d8.gif\r\n\r\n- Stack visited windows and recover them when closing\r\nhttps:\/\/cloud.githubusercontent.com\/assets\/5915359\/3351949\/c7c4c2d6-fa27-11e3-816a-f448657a5dba.gif\r\n\r\n## Usage\r\nIn vim normal mode, type the following command and press `<Enter>`.  \r\n**:TWcmd {cmd} {arg}**  \r\n- {cmd} : sub-commands for tabs or windows\r\n- {arg} : vim's `:wincmd`-style single character arguments \r\n\r\nFor example,\r\n```\r\n:TWcmd tcm l    |\" go to the right tab\r\n:TWcmd tmv l    |\" move the current tab right\r\n:TWcmd wmv h    |\" move the current window left\r\n:TWcmd tcm q    |\" close current tab\r\n```\r\n\r\n## Commands\r\n\r\n{cmd}   | description \r\n---     | ---\r\ntcm     | tab commands\r\ntmv     | tab moving commands\r\nwcm     | window commands\r\nwmv     | window moving commands\r\nwmvt    | window moving commands between tabs\r\ntwh     | tab-window history commands\r\n\r\n\r\nFor more information, please visit https:\/\/github.com\/yssl\/twcmd.vim.","4":"More information : https:\/\/github.com\/yssl\/twcmd.vim\r\n\r\n# twcmd.vim \r\n\r\ntwcmd.vim is a set of useful commands for moving & managing tabs and windows in vim.\r\n\r\n- Move a tab \/ window\r\nhttps:\/\/cloud.githubusercontent.com\/assets\/5915359\/3844245\/89017712-1e47-11e4-9f19-089d56a035d8.gif\r\n\r\n- Stack visited windows and recover them when closing\r\nhttps:\/\/cloud.githubusercontent.com\/assets\/5915359\/3351949\/c7c4c2d6-fa27-11e3-816a-f448657a5dba.gif\r\n\r\n## Usage\r\nIn vim normal mode, type the following command and press `<Enter>`.  \r\n**:TWcmd {cmd} {arg}**  \r\n- {cmd} : sub-commands for tabs or windows\r\n- {arg} : vim's `:wincmd`-style single character arguments \r\n\r\nFor example,\r\n```\r\n:TWcmd tcm l    |\" go to the right tab\r\n:TWcmd tmv l    |\" move the current tab right\r\n:TWcmd wmv h    |\" move the current window left\r\n:TWcmd tcm q    |\" close current tab\r\n```\r\n\r\n## Commands\r\n\r\n{cmd}   | description \r\n---     | ---\r\ntcm     | tab commands\r\ntmv     | tab moving commands\r\nwcm     | window commands\r\nwmv     | window moving commands\r\nwmvt    | window moving commands between tabs\r\ntwh     | tab-window history commands\r\n\r\n\r\nFor more information, please visit https:\/\/github.com\/yssl\/twcmd.vim.","install_details":"- Using plugin managers (recommended)\r\n    - [Vundle] : Add `Bundle 'yssl\/twcmd.vim'` to .vimrc & `:BundleInstall`\r\n    - [NeoBundle] : Add `NeoBundle 'yssl\/twcmd.vim'` to .vimrc & `:NeoBundleInstall`\r\n    - [vim-plug] : Add `Plug 'yssl\/twcmd.vim'` to .vimrc & `:PlugInstall`\r\n- Using [Pathogen]\r\n    - `cd ~\/.vim\/bundle; git clone https:\/\/github.com\/yssl\/twcmd.vim.git`\r\n- Manual install (not recommended)\r\n    - Download this plugin and extract it in `~\/.vim\/`","5":"- Using plugin managers (recommended)\r\n    - [Vundle] : Add `Bundle 'yssl\/twcmd.vim'` to .vimrc & `:BundleInstall`\r\n    - [NeoBundle] : Add `NeoBundle 'yssl\/twcmd.vim'` to .vimrc & `:NeoBundleInstall`\r\n    - [vim-plug] : Add `Plug 'yssl\/twcmd.vim'` to .vimrc & `:PlugInstall`\r\n- Using [Pathogen]\r\n    - `cd ~\/.vim\/bundle; git clone https:\/\/github.com\/yssl\/twcmd.vim.git`\r\n- Manual install (not recommended)\r\n    - Download this plugin and extract it in `~\/.vim\/`","first_name":"Yoonsang","6":"Yoonsang","last_name":"Lee","7":"Lee","releases":[{"0":"4876","vim_version":"7.0","1":"7.0","script_version":"1.3.1","2":"1.3.1","version_comment":"- Fix a bug when setting g:twcmd_focus_after_closing to 'none'","3":"- Fix a bug when setting g:twcmd_focus_after_closing to 'none'","package":"TWcmd.vim.zip","4":"TWcmd.vim.zip","src_id":"27322","5":"27322","creation_date":"1602076280","6":"1602076280"},{"0":"4876","vim_version":"7.0","1":"7.0","script_version":"1.3.0","2":"1.3.0","version_comment":"- g:twcmd_restore_prevfocus has been changed to g:twcmd_focus_after_closing  which can be one of the string values, 'prev_win_curr_tab', 'prev_win_tab',or 'none'.\r\n- change default focusing behavior to 'jump to the lastest window of the current tab'  when a window is closed. ('prev_win_curr_tab')","3":"- g:twcmd_restore_prevfocus has been changed to g:twcmd_focus_after_closing  which can be one of the string values, 'prev_win_curr_tab', 'prev_win_tab',or 'none'.\r\n- change default focusing behavior to 'jump to the lastest window of the current tab'  when a window is closed. ('prev_win_curr_tab')","package":"twcmd.vim.zip","4":"twcmd.vim.zip","src_id":"22739","5":"22739","creation_date":"1419748967","6":"1419748967"},{"0":"4876","vim_version":"7.0","1":"7.0","script_version":"1.2.0","2":"1.2.0","version_comment":"- change the name to twcmd.vim","3":"- change the name to twcmd.vim","package":"twcmd.zip","4":"twcmd.zip","src_id":"22304","5":"22304","creation_date":"1407425505","6":"1407425505"},{"0":"4876","vim_version":"7.0","1":"7.0","script_version":"1.1.0","2":"1.1.0","version_comment":"- add tab-window history stack feature\r\n- update screencast\r\n- update documents","3":"- add tab-window history stack feature\r\n- update screencast\r\n- update documents","package":"TWCommand.zip","4":"TWCommand.zip","src_id":"22079","5":"22079","creation_date":"1403458588","6":"1403458588"},{"0":"4876","vim_version":"7.0","1":"7.0","script_version":"1.0.0","2":"1.0.0","version_comment":"Initial upload","3":"Initial upload","package":"TWCommand.zip","4":"TWCommand.zip","src_id":"21545","5":"21545","creation_date":"1393579670","6":"1393579670"}]},"4875":{"script_id":"4875","0":"4875","script_name":"industry.vim","1":"industry.vim","script_type":"color scheme","2":"color scheme","summary":"Standard industrial color scheme for Vim","3":"Standard industrial color scheme for Vim","description":"I would like to suggest adding an industrial color scheme to the next Vim release.\r\nI used to work and program for machines in industrial environment. The main difference between industrial environment and desktop environment is the immediate risk for human lives.\r\nTherefore, colors are highly important and very meaningful in industry. \r\nJust take for example the traffic lights: imagine the green as blue or the red as brown... that could certainly cause an accident, since we all associate colors with meanings (as I briefly described in the header of the source file). \r\nFrom my personal experience, designing an HMI (Human-Machine-Interface) with non-standard colors, reduces productivity, risks human lives, and makes the workers tired quicker.\r\nI assume that the standard industrial color scheme might be helpful also in the desktop environment.\r\nI would like to offer this color scheme to Vim maintainer, Bram.\r\nIs there any objection? ","4":"I would like to suggest adding an industrial color scheme to the next Vim release.\r\nI used to work and program for machines in industrial environment. The main difference between industrial environment and desktop environment is the immediate risk for human lives.\r\nTherefore, colors are highly important and very meaningful in industry. \r\nJust take for example the traffic lights: imagine the green as blue or the red as brown... that could certainly cause an accident, since we all associate colors with meanings (as I briefly described in the header of the source file). \r\nFrom my personal experience, designing an HMI (Human-Machine-Interface) with non-standard colors, reduces productivity, risks human lives, and makes the workers tired quicker.\r\nI assume that the standard industrial color scheme might be helpful also in the desktop environment.\r\nI would like to offer this color scheme to Vim maintainer, Bram.\r\nIs there any objection? ","install_details":"1. Create your user runtime directory (you would normally use the first\r\n   item of the 'runtimepath' option) and sub-directory. Example for Linux: \r\n\t\r\n\tmkdir ~\/.vim\r\n\tmkdir ~\/.vim\/colors\r\n\r\n2. Unzip and copy the file to the sub-directory that you've created. Example for Linux:\r\n\r\n\tcp industry.vim ~\/.vim\/colors\r\n\r\n3. Restart Vim (if Vim is running). And select the color scheme:\r\n\r\n        :colo industry\r\n\r\ndone.","5":"1. Create your user runtime directory (you would normally use the first\r\n   item of the 'runtimepath' option) and sub-directory. Example for Linux: \r\n\t\r\n\tmkdir ~\/.vim\r\n\tmkdir ~\/.vim\/colors\r\n\r\n2. Unzip and copy the file to the sub-directory that you've created. Example for Linux:\r\n\r\n\tcp industry.vim ~\/.vim\/colors\r\n\r\n3. Restart Vim (if Vim is running). And select the color scheme:\r\n\r\n        :colo industry\r\n\r\ndone.","first_name":"Shian","6":"Shian","last_name":"Lee","7":"Lee","releases":[{"0":"4875","vim_version":"7.0","1":"7.0","script_version":"1.01","2":"1.01","version_comment":"- cursor coloring removed (always use the default cursor).\r\n- setting Normal for both cterm and GUI (regular white on black).","3":"- cursor coloring removed (always use the default cursor).\r\n- setting Normal for both cterm and GUI (regular white on black).","package":"industry.zip","4":"industry.zip","src_id":"21576","5":"21576","creation_date":"1394120130","6":"1394120130"}]},"4874":{"script_id":"4874","0":"4874","script_name":"LeaderF","1":"LeaderF","script_type":"utility","2":"utility","summary":"Quickly locate files, buffers, mrus, tags, ... in large project.","3":"Quickly locate files, buffers, mrus, tags, ... in large project.","description":"LeaderF\r\n\r\nThis plugin is mainly used for locating files, buffers, mrus, tags in large project.\r\n\r\nWritten in Python.\r\nSupport fuzzy and regex searching.\r\nManage buffers and mrus.\r\nOpen multiple files at once.\r\nExtensible.\r\n\r\nScreenshots\r\nhttps:\/\/github.com\/Yggdroot\/Images\/blob\/master\/leaderf\/leaderf_1.gif\r\nhttps:\/\/github.com\/Yggdroot\/Images\/blob\/master\/leaderf\/leaderf_2.gif\r\n\r\nRequirements\r\n\r\nvim7.3 or higher. Only support vim7.4.330 or higher after v1.01.\r\nvim compiled with Python support, you can check by using echo has('python') or echo has('python3') to see if the result is 1; Make sure that your python2 version is Python 2.7 or higher and python3 version is Python 3.1 or higher.\r\nInstallation\r\n\r\nTo install this plugin just put the plugin files in your ~\/.vim (Linux) or ~\/vimfiles (Windows).\r\nFor Vundle user, just add Plugin 'Yggdroot\/LeaderF' to your .vimrc.\r\n\r\nUsage\r\n\r\n:LeaderfFile or :LeaderfFile [directory] or ,f\r\nLaunch LeaderF to search files.\r\n\r\n:LeaderfBuffer or ,b\r\nLaunch LeaderF to search buffers.\r\n\r\n:LeaderfMru\r\nLaunch LeaderF to search Mru.\r\n\r\n:LeaderfMruCwd\r\nLaunch LeaderF to search Mru in current working directory.\r\n\r\n:LeaderfTag\r\nLaunch LeaderF to navigate tags.\r\n\r\n:LeaderfBufTag\r\nLaunch LeaderF to navigate tags in current buffer.\r\n\r\n:LeaderfBufTagAll\r\nLaunch LeaderF to navigate tags in all opening buffers.\r\n\r\nOnce LeaderF is launched:\r\n\r\n<C-C> : quit from LeaderF.\r\n<C-R> : switch between fuzzy search mode and regex mode.\r\n<C-F> : switch between full path search mode and name only search mode.\r\n<ESC> : switch to normal mode.\r\n<C-V>, <S-Insert> : paste from clipboard.\r\n<C-U> : clear the prompt.\r\n<C-J>, <Down>, <C-K>, <Up> : navigate the result list.\r\n<2-LeftMouse> or <CR> : open the file under cursor or selected(when multiple files are selected).\r\n<C-X> : open in horizontal split window.\r\n<C-]> : open in vertical split window.\r\n<C-T> : open in new tabpage.\r\n<F5> : refresh the cache.\r\n<C-LeftMouse> or <C-S> : select multiple files.\r\n<S-LeftMouse> : select consecutive multiple files.\r\n<C-A> : select all files.\r\n<C-L> : clear all selections.\r\n<BS> : delete the preceding character in the prompt.\r\n<Del> : delete the current character in the prompt.\r\n<Home>: move the cursor to the begin of the prompt.\r\n<End> : move the cursor to the end of the prompt.\r\n<Left>: move the cursor one character to the left.\r\n<Right> : move the cursor one character to the right.\r\n\r\nGithub:\r\n    https:\/\/github.com\/Yggdroot\/LeaderF","4":"LeaderF\r\n\r\nThis plugin is mainly used for locating files, buffers, mrus, tags in large project.\r\n\r\nWritten in Python.\r\nSupport fuzzy and regex searching.\r\nManage buffers and mrus.\r\nOpen multiple files at once.\r\nExtensible.\r\n\r\nScreenshots\r\nhttps:\/\/github.com\/Yggdroot\/Images\/blob\/master\/leaderf\/leaderf_1.gif\r\nhttps:\/\/github.com\/Yggdroot\/Images\/blob\/master\/leaderf\/leaderf_2.gif\r\n\r\nRequirements\r\n\r\nvim7.3 or higher. Only support vim7.4.330 or higher after v1.01.\r\nvim compiled with Python support, you can check by using echo has('python') or echo has('python3') to see if the result is 1; Make sure that your python2 version is Python 2.7 or higher and python3 version is Python 3.1 or higher.\r\nInstallation\r\n\r\nTo install this plugin just put the plugin files in your ~\/.vim (Linux) or ~\/vimfiles (Windows).\r\nFor Vundle user, just add Plugin 'Yggdroot\/LeaderF' to your .vimrc.\r\n\r\nUsage\r\n\r\n:LeaderfFile or :LeaderfFile [directory] or ,f\r\nLaunch LeaderF to search files.\r\n\r\n:LeaderfBuffer or ,b\r\nLaunch LeaderF to search buffers.\r\n\r\n:LeaderfMru\r\nLaunch LeaderF to search Mru.\r\n\r\n:LeaderfMruCwd\r\nLaunch LeaderF to search Mru in current working directory.\r\n\r\n:LeaderfTag\r\nLaunch LeaderF to navigate tags.\r\n\r\n:LeaderfBufTag\r\nLaunch LeaderF to navigate tags in current buffer.\r\n\r\n:LeaderfBufTagAll\r\nLaunch LeaderF to navigate tags in all opening buffers.\r\n\r\nOnce LeaderF is launched:\r\n\r\n<C-C> : quit from LeaderF.\r\n<C-R> : switch between fuzzy search mode and regex mode.\r\n<C-F> : switch between full path search mode and name only search mode.\r\n<ESC> : switch to normal mode.\r\n<C-V>, <S-Insert> : paste from clipboard.\r\n<C-U> : clear the prompt.\r\n<C-J>, <Down>, <C-K>, <Up> : navigate the result list.\r\n<2-LeftMouse> or <CR> : open the file under cursor or selected(when multiple files are selected).\r\n<C-X> : open in horizontal split window.\r\n<C-]> : open in vertical split window.\r\n<C-T> : open in new tabpage.\r\n<F5> : refresh the cache.\r\n<C-LeftMouse> or <C-S> : select multiple files.\r\n<S-LeftMouse> : select consecutive multiple files.\r\n<C-A> : select all files.\r\n<C-L> : clear all selections.\r\n<BS> : delete the preceding character in the prompt.\r\n<Del> : delete the current character in the prompt.\r\n<Home>: move the cursor to the begin of the prompt.\r\n<End> : move the cursor to the end of the prompt.\r\n<Left>: move the cursor one character to the left.\r\n<Right> : move the cursor one character to the right.\r\n\r\nGithub:\r\n    https:\/\/github.com\/Yggdroot\/LeaderF","install_details":"To install this plugin just put the plugin files in your ~\/.vim (Linux) or ~\/vimfiles (Windows).\r\nFor Vundle user, just add Plugin 'Yggdroot\/LeaderF' to your .vimrc.","5":"To install this plugin just put the plugin files in your ~\/.vim (Linux) or ~\/vimfiles (Windows).\r\nFor Vundle user, just add Plugin 'Yggdroot\/LeaderF' to your .vimrc.","first_name":"Yggdroot","6":"Yggdroot","last_name":"Chen","7":"Chen","releases":[{"0":"4874","vim_version":"8.0","1":"8.0","script_version":"1.20","2":"1.20","version_comment":"Feature #191: add support for GNU Global(Leaderf gtags)\r\nFor more details: Leaderf gtags -h","3":"Feature #191: add support for GNU Global(Leaderf gtags)\r\nFor more details: Leaderf gtags -h","package":"LeaderF-master.zip","4":"LeaderF-master.zip","src_id":"26502","5":"26502","creation_date":"1558994169","6":"1558994169"},{"0":"4874","vim_version":"7.4","1":"7.4","script_version":"1.19","2":"1.19","version_comment":"Feature #57: Add support for rg(Leaderf rg)\r\nFor more details: Leaderf rg -h\r\nFeature #130: Add Changelog file.\r\nFeature #208: Add support for input file list.\r\nAdd --file option for Leaderf file.\r\nFeature #213: Add support for input history.\r\nUse <UP> and <Down> to loop the input history.\r\nAdd one-dark colorscheme.\r\nAdd --nowrap option for LeaderF.","3":"Feature #57: Add support for rg(Leaderf rg)\r\nFor more details: Leaderf rg -h\r\nFeature #130: Add Changelog file.\r\nFeature #208: Add support for input file list.\r\nAdd --file option for Leaderf file.\r\nFeature #213: Add support for input history.\r\nUse <UP> and <Down> to loop the input history.\r\nAdd one-dark colorscheme.\r\nAdd --nowrap option for LeaderF.","package":"LeaderF-master.zip","4":"LeaderF-master.zip","src_id":"26310","5":"26310","creation_date":"1546085246","6":"1546085246"},{"0":"4874","vim_version":"7.4","1":"7.4","script_version":"1.11","2":"1.11","version_comment":"0. Add async support\r\n1. Better fuzzy match algorithm.\r\n2. Faster speed.\r\n3. Better tool to find the tags.","3":"0. Add async support\r\n1. Better fuzzy match algorithm.\r\n2. Faster speed.\r\n3. Better tool to find the tags.","package":"LeaderF-1.11.zip","4":"LeaderF-1.11.zip","src_id":"25381","5":"25381","creation_date":"1499393446","6":"1499393446"},{"0":"4874","vim_version":"7.4","1":"7.4","script_version":"1.0.4","2":"1.0.4","version_comment":"7.4.330 or higher","3":"7.4.330 or higher","package":"LeaderF.zip","4":"LeaderF.zip","src_id":"25046","5":"25046","creation_date":"1490453925","6":"1490453925"},{"0":"4874","vim_version":"7.0","1":"7.0","script_version":"1.0.3","2":"1.0.3","version_comment":"fix a bug","3":"fix a bug","package":"LeaderF.zip","4":"LeaderF.zip","src_id":"21686","5":"21686","creation_date":"1395975502","6":"1395975502"}]},"4873":{"script_id":"4873","0":"4873","script_name":"gnuplot syntax highlighting","1":"gnuplot syntax highlighting","script_type":"syntax","2":"syntax","summary":"syntax highlighting for gnuplot","3":"syntax highlighting for gnuplot","description":"Highlighting for all gnuplot commands, keywords, built-in variables, etc. as of 2014-02-24.","4":"Highlighting for all gnuplot commands, keywords, built-in variables, etc. as of 2014-02-24.","install_details":"Place script in ~\/.vim\/syntax\r\n\r\nSee \r\n  :help mysyntaxfile \r\n  :help new-filetype","5":"Place script in ~\/.vim\/syntax\r\n\r\nSee \r\n  :help mysyntaxfile \r\n  :help new-filetype","first_name":"Andrew","6":"Andrew","last_name":"Rasmussen","7":"Rasmussen","releases":[{"0":"4873","vim_version":"5.7","1":"5.7","script_version":"1.11","2":"1.11","version_comment":"added 'variable' keyword","3":"added 'variable' keyword","package":"gnuplot.vim","4":"gnuplot.vim","src_id":"21536","5":"21536","creation_date":"1393413644","6":"1393413644"},{"0":"4873","vim_version":"5.7","1":"5.7","script_version":"1.1","2":"1.1","version_comment":"Updated credits, uncommented version-dependent code.","3":"Updated credits, uncommented version-dependent code.","package":"gnuplot.vim","4":"gnuplot.vim","src_id":"21531","5":"21531","creation_date":"1393272056","6":"1393272056"},{"0":"4873","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"gnuplot.vim","4":"gnuplot.vim","src_id":"21530","5":"21530","creation_date":"1393271427","6":"1393271427"}]},"4872":{"script_id":"4872","0":"4872","script_name":"a","1":"a","script_type":"syntax","2":"syntax","summary":" ","3":" ","description":" ","4":" ","install_details":"","5":"","first_name":".","6":".","last_name":".","7":".","releases":[{"0":"4872","vim_version":"7.0","1":"7.0","script_version":"1.7","2":"1.7","version_comment":"Check value of `g:decfile_disable_folding`. Previously, folding was disabled whenever `g:decfile_disable_folding` was set, irrespective of its value. Now folding is only disabled when the variable evaluates to non-zero. Folding can be re-enabled with `let g:decfile_disable_folding = 0`, without needing to unset the variable.","3":"Check value of `g:decfile_disable_folding`. Previously, folding was disabled whenever `g:decfile_disable_folding` was set, irrespective of its value. Now folding is only disabled when the variable evaluates to non-zero. Folding can be re-enabled with `let g:decfile_disable_folding = 0`, without needing to unset the variable.","package":"vim-decfile-1.7.tar.gz","4":"vim-decfile-1.7.tar.gz","src_id":"23761","5":"23761","creation_date":"1448625583","6":"1448625583"}]},"4871":{"script_id":"4871","0":"4871","script_name":"Licenses","1":"Licenses","script_type":"utility","2":"utility","summary":"Provides commands to add licenses at the top of the buffer","3":"Provides commands to add licenses at the top of the buffer","description":"This plugin provides commands to insert licenses at the top of the buffer.\r\nIf the license is already at the top of the buffer, nothing is added.\r\nThis plugin works for the most popular programming languages, including\r\nC, Java, Objective-C, C++, C#, PHP, Python, JavaScript, Ruby, Perl, Asm and Haskell.\r\nThe HTML and CSS languages are also supported.\r\nIt may work for other languages.\r\n\r\nThere are currently more than 10 licenses, and you can add your own.\r\nTo do so, copy the license text in ~\/.vim\/licenses\/licenseFile.txt.\r\nThen add a command for this license:\r\n\r\n    command! License call InsertLicense('licenseFile')\r\n\r\nIf your license file contains a <year> tag, it will be automatically\r\nreplaced by the current year.\r\n\r\nThe <name of copyright holder> tag will be automatically replaced by the\r\ncontent of the g:licenses_copyright_holders_name variable (if not empty), so that\r\nthe copyright holder's name will be automatically added to the license.\r\nThus, you may want to add such a line to you .vimrc:\r\n\r\nlet g:licenses_copyright_holders_name = 'Last Name, First Name <my@email.com>'\r\n\r\nAnd the <name of author> tag will be replaced by the content of the\r\ng:licenses_authors_name variable (if not empty).\r\n\r\nThis way you can autocomplete the license template with, for example, the company\r\nyou work for as the copyright holder, and you as the author. Or you can set\r\nyourself as the copyright holder, and thus your name will be next to the year.\r\n\r\nIf you do not want this plugin to create all these commands, you may\r\nrestrict to the licenses you want by using the g:licenses_default_commands\r\noption. For instance, to have this plugin add only a command for the GNU GPL,\r\nMit and Foobar licenses, use this:\r\n\r\nlet g:licenses_default_commands = ['gpl', 'mit', 'foobar']\r\n\r\nCommands:\r\n:Affero\r\n    Add the GNU Affero license to the buffer.\r\n\r\n:Apache\r\n    Add the Apache License 2.0 to the buffer.\r\n\r\n:Bsd2\r\n    Add the BSD 2-Clause \"New\" or \"Revised\" license to the buffer.\r\n\r\n:Bsd3\r\n    Add the BSD 3-Clause \"Simplified\" or \"FreeBSD\" license to the buffer.\r\n\r\n:Epl\r\n    Add the Eclipse Public License to the buffer.\r\n\r\n:Gfdl\r\n    Add the GNU Free Documentation License (FDL) to the buffer.\r\n\r\n:Gpl\r\n    Add the GNU General Public License (GPL) version 3.0 to the buffer.\r\n\r\n:Gplv2\r\n    Add the GNU General Public License (GPL) version 2.0 to the buffer.\r\n\r\n:Lgpl\r\n    Add the GNU \"Lesser\" General Public License (LGPL) license to the buffer.\r\n\r\n:Mit\r\n    Add the MIT license to the buffer.\r\n\r\n:Mpl\r\n    Add the Mozilla Public License 2.0 to the buffer.\r\n\r\n:Unlicense\r\n    Add the Unlicense to the buffer.\r\n\r\n:Wtfpl\r\n    Add the Do What The Fuck You Want To Public License (WTFPL) to the buffer.\r\n\r\n:Zlib\r\n    Add the Zlib License to the buffer.\r\n\r\nSettings:\r\n\r\nThe g:licenses_copyright_holders_name option\r\n\r\nThe name of the copyright holder to automatically insert in the buffer in the license.\r\n\r\nThe g:licenses_authors_name option\r\n\r\nThe author name to automatically insert in the buffer in the license.\r\n\r\nThe g:licenses_default_commands option\r\n\r\nChoose what commands to create for the listed licenses.\r\n\r\nGit repository:\r\n\r\nhttps:\/\/github.com\/antoyo\/vim-licenses","4":"This plugin provides commands to insert licenses at the top of the buffer.\r\nIf the license is already at the top of the buffer, nothing is added.\r\nThis plugin works for the most popular programming languages, including\r\nC, Java, Objective-C, C++, C#, PHP, Python, JavaScript, Ruby, Perl, Asm and Haskell.\r\nThe HTML and CSS languages are also supported.\r\nIt may work for other languages.\r\n\r\nThere are currently more than 10 licenses, and you can add your own.\r\nTo do so, copy the license text in ~\/.vim\/licenses\/licenseFile.txt.\r\nThen add a command for this license:\r\n\r\n    command! License call InsertLicense('licenseFile')\r\n\r\nIf your license file contains a <year> tag, it will be automatically\r\nreplaced by the current year.\r\n\r\nThe <name of copyright holder> tag will be automatically replaced by the\r\ncontent of the g:licenses_copyright_holders_name variable (if not empty), so that\r\nthe copyright holder's name will be automatically added to the license.\r\nThus, you may want to add such a line to you .vimrc:\r\n\r\nlet g:licenses_copyright_holders_name = 'Last Name, First Name <my@email.com>'\r\n\r\nAnd the <name of author> tag will be replaced by the content of the\r\ng:licenses_authors_name variable (if not empty).\r\n\r\nThis way you can autocomplete the license template with, for example, the company\r\nyou work for as the copyright holder, and you as the author. Or you can set\r\nyourself as the copyright holder, and thus your name will be next to the year.\r\n\r\nIf you do not want this plugin to create all these commands, you may\r\nrestrict to the licenses you want by using the g:licenses_default_commands\r\noption. For instance, to have this plugin add only a command for the GNU GPL,\r\nMit and Foobar licenses, use this:\r\n\r\nlet g:licenses_default_commands = ['gpl', 'mit', 'foobar']\r\n\r\nCommands:\r\n:Affero\r\n    Add the GNU Affero license to the buffer.\r\n\r\n:Apache\r\n    Add the Apache License 2.0 to the buffer.\r\n\r\n:Bsd2\r\n    Add the BSD 2-Clause \"New\" or \"Revised\" license to the buffer.\r\n\r\n:Bsd3\r\n    Add the BSD 3-Clause \"Simplified\" or \"FreeBSD\" license to the buffer.\r\n\r\n:Epl\r\n    Add the Eclipse Public License to the buffer.\r\n\r\n:Gfdl\r\n    Add the GNU Free Documentation License (FDL) to the buffer.\r\n\r\n:Gpl\r\n    Add the GNU General Public License (GPL) version 3.0 to the buffer.\r\n\r\n:Gplv2\r\n    Add the GNU General Public License (GPL) version 2.0 to the buffer.\r\n\r\n:Lgpl\r\n    Add the GNU \"Lesser\" General Public License (LGPL) license to the buffer.\r\n\r\n:Mit\r\n    Add the MIT license to the buffer.\r\n\r\n:Mpl\r\n    Add the Mozilla Public License 2.0 to the buffer.\r\n\r\n:Unlicense\r\n    Add the Unlicense to the buffer.\r\n\r\n:Wtfpl\r\n    Add the Do What The Fuck You Want To Public License (WTFPL) to the buffer.\r\n\r\n:Zlib\r\n    Add the Zlib License to the buffer.\r\n\r\nSettings:\r\n\r\nThe g:licenses_copyright_holders_name option\r\n\r\nThe name of the copyright holder to automatically insert in the buffer in the license.\r\n\r\nThe g:licenses_authors_name option\r\n\r\nThe author name to automatically insert in the buffer in the license.\r\n\r\nThe g:licenses_default_commands option\r\n\r\nChoose what commands to create for the listed licenses.\r\n\r\nGit repository:\r\n\r\nhttps:\/\/github.com\/antoyo\/vim-licenses","install_details":"1. Download the licenses.zip file and unzip the files to the $HOME\/.vim directory. After this step,\r\n    you should have the following files and directories (the directory structure should be preserved):\r\n\r\n    doc\/licenses.txt                         - documentation (help) file\r\n    licenses\/                                     - licenses directory\r\n    plugin\/licenses.vim                  - main licenses plugin file\r\n    test\/test_insert_license.vim    - The plugin unit tests\r\n    LICENSE                                   - The licenses plugin license\r\n\r\n2. Change to the $HOME\/.vim\/doc directory, start Vim and run the \":helptags .\" command\r\n     to process the licenses help file. Without this step, you cannot jump to the licenses help topics.\r\n3. Restart Vim.\r\n4. You can now use one of the commands above to add a license to the buffer. You can\r\n     use the \":help licenses\" command to get more information about using the licenses plugin.","5":"1. Download the licenses.zip file and unzip the files to the $HOME\/.vim directory. After this step,\r\n    you should have the following files and directories (the directory structure should be preserved):\r\n\r\n    doc\/licenses.txt                         - documentation (help) file\r\n    licenses\/                                     - licenses directory\r\n    plugin\/licenses.vim                  - main licenses plugin file\r\n    test\/test_insert_license.vim    - The plugin unit tests\r\n    LICENSE                                   - The licenses plugin license\r\n\r\n2. Change to the $HOME\/.vim\/doc directory, start Vim and run the \":helptags .\" command\r\n     to process the licenses help file. Without this step, you cannot jump to the licenses help topics.\r\n3. Restart Vim.\r\n4. You can now use one of the commands above to add a license to the buffer. You can\r\n     use the \":help licenses\" command to get more information about using the licenses plugin.","first_name":"Antoni","6":"Antoni","last_name":"Boucher","7":"Boucher","releases":[{"0":"4871","vim_version":"7.0","1":"7.0","script_version":"0.5","2":"0.5","version_comment":"This version breaks backward compatibility!\r\nPlease update your configuration according to the documentation.\r\n\r\nAdded new licenses.\r\nRemoved trailing spaces in the inserted licenses.\r\nFixed bug to avoid overriding the alternate buffer.\r\nAdded copyright holder variable (breaks backward compatibility).","3":"This version breaks backward compatibility!\r\nPlease update your configuration according to the documentation.\r\n\r\nAdded new licenses.\r\nRemoved trailing spaces in the inserted licenses.\r\nFixed bug to avoid overriding the alternate buffer.\r\nAdded copyright holder variable (breaks backward compatibility).","package":"licenses.zip","4":"licenses.zip","src_id":"24533","5":"24533","creation_date":"1474130201","6":"1474130201"},{"0":"4871","vim_version":"7.0","1":"7.0","script_version":"0.4","2":"0.4","version_comment":"Added new licenses.\r\nAdded an option to specify the default license commands to create.","3":"Added new licenses.\r\nAdded an option to specify the default license commands to create.","package":"licenses.zip","4":"licenses.zip","src_id":"22115","5":"22115","creation_date":"1404228934","6":"1404228934"},{"0":"4871","vim_version":"7.0","1":"7.0","script_version":"0.3","2":"0.3","version_comment":"Added many new licenses.\r\nCreated better comments option parser to support more languages.\r\nAdded an option to set the author's name instead of having to manually change the license text files.\r\nThe error shown when no <year> tag was in the license text is now hidden.\r\nAdded unit tests.","3":"Added many new licenses.\r\nCreated better comments option parser to support more languages.\r\nAdded an option to set the author's name instead of having to manually change the license text files.\r\nThe error shown when no <year> tag was in the license text is now hidden.\r\nAdded unit tests.","package":"licenses.zip","4":"licenses.zip","src_id":"21908","5":"21908","creation_date":"1400531876","6":"1400531876"},{"0":"4871","vim_version":"7.0","1":"7.0","script_version":"0.2","2":"0.2","version_comment":"Added support for Windows.","3":"Added support for Windows.","package":"licenses.zip","4":"licenses.zip","src_id":"21532","5":"21532","creation_date":"1393284377","6":"1393284377"},{"0":"4871","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"licenses.zip","4":"licenses.zip","src_id":"21524","5":"21524","creation_date":"1393114580","6":"1393114580"}]},"4870":{"script_id":"4870","0":"4870","script_name":"ExtractLinks","1":"ExtractLinks","script_type":"utility","2":"utility","summary":"Replace inline links with unique references and a link table.","3":"Replace inline links with unique references and a link table.","description":"DESCRIPTION\r\nIn forums, emails, documentation, or other plain-text files, one often embeds\r\nreferences directly in the text. But many URLs are quite long, and this often\r\nbreaks the formatting and natural flow of the text. It would be better to\r\nplace those below the main text, in a neat reference section. But doing that\r\nmanually is tedious and error-prone.\r\n\r\nThis plugin leverages the :SubstituteAndYankUnique command of the\r\nExtractMatches.vim plugin (vimscript #4795) to extract the (configurable)\r\nURLs found in the buffer and replace them with unique inline anchors.\r\nAdditionally, an (again configurable) table of anchor and extracted URL is\r\nplaced into a register, for easy pasting. The complete link extraction and\r\nreferencing is therefore reduced to a short and painless\r\n    :ExtractMatches | $put\r\n\r\nIn addition to a general global default, the plugin ships with predefined\r\npattern and replacement definitions for:\r\n- Markdown\r\n[text](URL)\r\n- HTML\r\n[text] or [<a href=\"...\">link<\/a>\"]\r\n\r\nSOURCE\r\nInspired by\r\nhttp:\/\/superuser.com\/questions\/717946\/links-to-references-in-mutt-or-vim\r\n\r\nUSAGE\r\n:[range]ExtractLinks [x]\r\n                        Extract all links in [range] \/ the buffer with a\r\n                        (filetype-specific, by default \"[N]\") unique\r\n                        reference, and generate a corresponding link table\r\n                        that associates the references with the respective\r\n                        original links (default: \"[N] {link}\"). This is placed\r\n                        into register [x] \/ the default register, so it can be\r\n                            :$put\r\n                       into the buffer (probably at the end, as a legend).\r\n\r\nEXAMPLE\r\n    This text references http:\/\/www.vim.org\/ and http:\/\/w3.org\/.\r\n    :ExtractLinks\r\n    This text references [1] and [2].\r\n    :put\r\n    [1] http:\/\/www.vim.org\/\r\n    [2] http:\/\/w3.org\/","4":"DESCRIPTION\r\nIn forums, emails, documentation, or other plain-text files, one often embeds\r\nreferences directly in the text. But many URLs are quite long, and this often\r\nbreaks the formatting and natural flow of the text. It would be better to\r\nplace those below the main text, in a neat reference section. But doing that\r\nmanually is tedious and error-prone.\r\n\r\nThis plugin leverages the :SubstituteAndYankUnique command of the\r\nExtractMatches.vim plugin (vimscript #4795) to extract the (configurable)\r\nURLs found in the buffer and replace them with unique inline anchors.\r\nAdditionally, an (again configurable) table of anchor and extracted URL is\r\nplaced into a register, for easy pasting. The complete link extraction and\r\nreferencing is therefore reduced to a short and painless\r\n    :ExtractMatches | $put\r\n\r\nIn addition to a general global default, the plugin ships with predefined\r\npattern and replacement definitions for:\r\n- Markdown\r\n[text](URL)\r\n- HTML\r\n[text] or [<a href=\"...\">link<\/a>\"]\r\n\r\nSOURCE\r\nInspired by\r\nhttp:\/\/superuser.com\/questions\/717946\/links-to-references-in-mutt-or-vim\r\n\r\nUSAGE\r\n:[range]ExtractLinks [x]\r\n                        Extract all links in [range] \/ the buffer with a\r\n                        (filetype-specific, by default \"[N]\") unique\r\n                        reference, and generate a corresponding link table\r\n                        that associates the references with the respective\r\n                        original links (default: \"[N] {link}\"). This is placed\r\n                        into register [x] \/ the default register, so it can be\r\n                            :$put\r\n                       into the buffer (probably at the end, as a legend).\r\n\r\nEXAMPLE\r\n    This text references http:\/\/www.vim.org\/ and http:\/\/w3.org\/.\r\n    :ExtractLinks\r\n    This text references [1] and [2].\r\n    :put\r\n    [1] http:\/\/www.vim.org\/\r\n    [2] http:\/\/w3.org\/","install_details":"INSTALLATION\r\nThis script is packaged as a vimball. If you have the \"gunzip\" decompressor\r\nin your PATH, simply edit the *.vmb.gz package in Vim; otherwise, decompress\r\nthe archive first, e.g. using WinZip. Inside Vim, install by sourcing the\r\nvimball or via the :UseVimball command.\r\n    vim ExtractLinks*.vmb.gz\r\n    :so %\r\nTo uninstall, use the :RmVimball command.\r\n\r\nDEPENDENCIES\r\n- Requires Vim 7.0 or higher.\r\n- Requires the ingo-library.vim plugin (vimscript #4433), version 1.015 or\r\n  higher.\r\n- Requires the ExtractMatches.vim plugin (vimscript #4795), version 1.20 or\r\n  higher.\r\n\r\nCONFIGURATION\r\nFor a permanent configuration, put the following commands into your vimrc:\r\n\r\nA Dictionary (to avoid multiple identical entries) containing regular\r\nexpressions (as keys, the values are irrelevant) to capture links in the\r\nbuffer:\r\n    let g:ExtractLinks_Expressions = {'\\<link: \\S\\+\\>', 1}\r\n\r\nThe replacement of the matched link inside the buffer:\r\n    let g:ExtractLinks_ReplacementInline = '[\\#]'\r\n\r\nThe replacement of the matched link for the link table:\r\n    let g:ExtractLinks_ReplacementExtraction = '[\\#] &\\n'","5":"INSTALLATION\r\nThis script is packaged as a vimball. If you have the \"gunzip\" decompressor\r\nin your PATH, simply edit the *.vmb.gz package in Vim; otherwise, decompress\r\nthe archive first, e.g. using WinZip. Inside Vim, install by sourcing the\r\nvimball or via the :UseVimball command.\r\n    vim ExtractLinks*.vmb.gz\r\n    :so %\r\nTo uninstall, use the :RmVimball command.\r\n\r\nDEPENDENCIES\r\n- Requires Vim 7.0 or higher.\r\n- Requires the ingo-library.vim plugin (vimscript #4433), version 1.015 or\r\n  higher.\r\n- Requires the ExtractMatches.vim plugin (vimscript #4795), version 1.20 or\r\n  higher.\r\n\r\nCONFIGURATION\r\nFor a permanent configuration, put the following commands into your vimrc:\r\n\r\nA Dictionary (to avoid multiple identical entries) containing regular\r\nexpressions (as keys, the values are irrelevant) to capture links in the\r\nbuffer:\r\n    let g:ExtractLinks_Expressions = {'\\<link: \\S\\+\\>', 1}\r\n\r\nThe replacement of the matched link inside the buffer:\r\n    let g:ExtractLinks_ReplacementInline = '[\\#]'\r\n\r\nThe replacement of the matched link for the link table:\r\n    let g:ExtractLinks_ReplacementExtraction = '[\\#] &\\n'","first_name":"Ingo","6":"Ingo","last_name":"Karkat","7":"Karkat","releases":[{"0":"4870","vim_version":"7.0","1":"7.0","script_version":"1.00","2":"1.00","version_comment":"Initial upload","3":"Initial upload","package":"ExtractLinks-1.00.vmb.gz","4":"ExtractLinks-1.00.vmb.gz","src_id":"21513","5":"21513","creation_date":"1392914304","6":"1392914304"}]},"4869":{"script_id":"4869","0":"4869","script_name":"searchmatch","1":"searchmatch","script_type":"utility","2":"utility","summary":"Easy search highlight pinning in Vim with :match","3":"Easy search highlight pinning in Vim with :match","description":"So if you're a frequent user of Vim's hlsearch feature, you may find yourself wishing that you could highlight multiple searches. Well Vim has support for this in its :match command, but doesn't make that particularly easy to use.\r\n\r\nThis plugin aims to put the full power of Vim's :match feature at the user's fingertips in the easiest way possible: as an extension of the existing search feature that you know and love.\r\n\r\nYou just search for something, and then pin that search with one of the SearchMatchN commands or key mappings.\r\n\r\nhttps:\/\/github.com\/jcorbin\/vim-searchmatch","4":"So if you're a frequent user of Vim's hlsearch feature, you may find yourself wishing that you could highlight multiple searches. Well Vim has support for this in its :match command, but doesn't make that particularly easy to use.\r\n\r\nThis plugin aims to put the full power of Vim's :match feature at the user's fingertips in the easiest way possible: as an extension of the existing search feature that you know and love.\r\n\r\nYou just search for something, and then pin that search with one of the SearchMatchN commands or key mappings.\r\n\r\nhttps:\/\/github.com\/jcorbin\/vim-searchmatch","install_details":"Clone with pathogen or copy the plugin file into your runtime (see README for details).","5":"Clone with pathogen or copy the plugin file into your runtime (see README for details).","first_name":"Joshua","6":"Joshua","last_name":"Corbin","7":"Corbin","releases":[{"0":"4869","vim_version":"7.0","1":"7.0","script_version":"0.9.1","2":"0.9.1","version_comment":"Changed default mapping; minor improvements.","3":"Changed default mapping; minor improvements.","package":"vim-searchmatch-0.9.1.tar.gz","4":"vim-searchmatch-0.9.1.tar.gz","src_id":"21499","5":"21499","creation_date":"1392670921","6":"1392670921"},{"0":"4869","vim_version":"7.0","1":"7.0","script_version":"0.9.0","2":"0.9.0","version_comment":"Initial upload","3":"Initial upload","package":"vim-searchmatch-0.9.0.tar.gz","4":"vim-searchmatch-0.9.0.tar.gz","src_id":"21498","5":"21498","creation_date":"1392658541","6":"1392658541"}]},"4868":{"script_id":"4868","0":"4868","script_name":"wildfire.vim","1":"wildfire.vim","script_type":"utility","2":"utility","summary":"Smart selection of the closest text object","3":"Smart selection of the closest text object","description":"\r\n+] Intro\r\n\r\nWith Wildfire you can quickly select the closest text object among a group of candidates.\r\n By default candidates are \"i'\", 'i\"', \"i)\", \"i]\", \"i}\", \"ip\" and \"it\".\r\n\r\n+] Usage\r\n\r\nPress <ENTER> in normal mode to select the closest text object. Keep pressing <ENTER> \r\nfor selecting the next closest text object. To go the other way round, that is, to select the previously \r\nselected text object, press <BS>.\r\n\r\nTo speed things up, if you want to select the nth closest text object you can press a number followed \r\nby <ENTER> (e.g. pressing 2<ENTER> will select the second closest text object).\r\n\r\nMore at https:\/\/github.com\/gcmt\/wildfire.vim","4":"\r\n+] Intro\r\n\r\nWith Wildfire you can quickly select the closest text object among a group of candidates.\r\n By default candidates are \"i'\", 'i\"', \"i)\", \"i]\", \"i}\", \"ip\" and \"it\".\r\n\r\n+] Usage\r\n\r\nPress <ENTER> in normal mode to select the closest text object. Keep pressing <ENTER> \r\nfor selecting the next closest text object. To go the other way round, that is, to select the previously \r\nselected text object, press <BS>.\r\n\r\nTo speed things up, if you want to select the nth closest text object you can press a number followed \r\nby <ENTER> (e.g. pressing 2<ENTER> will select the second closest text object).\r\n\r\nMore at https:\/\/github.com\/gcmt\/wildfire.vim","install_details":"\r\nInstall with Pathogen, Vundle or your favorite plugin manager.","5":"\r\nInstall with Pathogen, Vundle or your favorite plugin manager.","first_name":"geck","6":"geck","last_name":" ","7":" ","releases":[{"0":"4868","vim_version":"7.0","1":"7.0","script_version":"1.1.4","2":"1.1.4","version_comment":"- Bug fixes","3":"- Bug fixes","package":"wildfire.zip","4":"wildfire.zip","src_id":"22170","5":"22170","creation_date":"1404841217","6":"1404841217"}]},"4867":{"script_id":"4867","0":"4867","script_name":"fuckpep8","1":"fuckpep8","script_type":"indent","2":"indent","summary":"Make life feasible in the presense of crazy space-hippies.","3":"Make life feasible in the presense of crazy space-hippies.","description":"This plugin is intended to make life feasible for those of us who are right in the head, and use the proper tools (tabs) for indentation. It uses the awesome detectindent plugin (http:\/\/www.vim.org\/scripts\/script.php?script\\_id=1171) to detect how many spaces the poor misguided souls that originally wrote a given Python file use, replace them with tabs, and switch it back before saving.\r\n\r\nThe most up-to-date version will be here: https:\/\/github.com\/zardus\/fuckpep8","4":"This plugin is intended to make life feasible for those of us who are right in the head, and use the proper tools (tabs) for indentation. It uses the awesome detectindent plugin (http:\/\/www.vim.org\/scripts\/script.php?script\\_id=1171) to detect how many spaces the poor misguided souls that originally wrote a given Python file use, replace them with tabs, and switch it back before saving.\r\n\r\nThe most up-to-date version will be here: https:\/\/github.com\/zardus\/fuckpep8","install_details":"First, install detectindent and configure some reasonable defaults.\r\n\r\nThen, install fuckpep8.\r\n\r\nThat's it!","5":"First, install detectindent and configure some reasonable defaults.\r\n\r\nThen, install fuckpep8.\r\n\r\nThat's it!","first_name":"Yan","6":"Yan","last_name":"Shoshitaishvili","7":"Shoshitaishvili","releases":[{"0":"4867","vim_version":"7.0","1":"7.0","script_version":"1.2","2":"1.2","version_comment":"Fixed undo behavior to hide the retabbing.","3":"Fixed undo behavior to hide the retabbing.","package":"fuckpep8.tar.gz","4":"fuckpep8.tar.gz","src_id":"21500","5":"21500","creation_date":"1392684959","6":"1392684959"},{"0":"4867","vim_version":"7.0","1":"7.0","script_version":"1.1","2":"1.1","version_comment":"now a filetype plugin","3":"now a filetype plugin","package":"fuckpep8.tar.gz","4":"fuckpep8.tar.gz","src_id":"21491","5":"21491","creation_date":"1392598606","6":"1392598606"},{"0":"4867","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"fuckpep8.tar.gz","4":"fuckpep8.tar.gz","src_id":"21490","5":"21490","creation_date":"1392596043","6":"1392596043"}]},"4866":{"script_id":"4866","0":"4866","script_name":"prop.vim","1":"prop.vim","script_type":"color scheme","2":"color scheme","summary":"Android system properties highlight","3":"Android system properties highlight","description":"Highlights Android system properties files (those obtained by adb shell getprop > system.prop)","4":"Highlights Android system properties files (those obtained by adb shell getprop > system.prop)","install_details":"","5":"","first_name":"Douglas","6":"Douglas","last_name":"Drumond","7":"Drumond","releases":[{"0":"4866","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"prop.vim","4":"prop.vim","src_id":"21489","5":"21489","creation_date":"1392516831","6":"1392516831"}]},"4865":{"script_id":"4865","0":"4865","script_name":"writable_search.vim","1":"writable_search.vim","script_type":"utility","2":"utility","summary":"Perform a grep and edit the results directly","3":"Perform a grep and edit the results directly","description":"Github project: https:\/\/github.com\/AndrewRadev\/writable_search.vim\r\n\r\nThe plugin exposes the command `:WritableSearch`, which takes a search query and performs a grep (or ack, or a different search command -- see below), with that query. For example:\r\n\r\n    :WritableSearch function_call\\(\r\n\r\nThe results are opened in a new tab (by default), and are very similar to what you would get from performing the search on the command-line. The difference is that you can now edit this buffer and, upon writing, the original files will be updated with the changes. This gives you a very simple and straightforward search-and-replace process.\r\n\r\nIf you change the filenames in the header blocks, those files will be renamed (with some manual confirmation that you can turn off if you're feeling adventurous). For example, if the header says:\r\n\r\n    foo\/bar.txt:12-34\r\n\r\nand you change that to:\r\n\r\n    foo\/renamed.txt:12-34\r\n\r\nThen the file \"foo\/bar.txt\" will be renamed to \"foo\/renamed.txt\". If this is not possible, you'll get an error.\r\n\r\nIf you change the line numbers displayed in the headers, the virtual \"window\" that this search result is pointing to will reposition itself to those line numbers. For example, if the header says:\r\n\r\n    foo\/bar.txt:12-34\r\n\r\nand you change that to:\r\n\r\n    foo\/bar.txt:10-22\r\n\r\nThen the lines displayed will now be the ones from 10 to 22.\r\n\r\nThe plugin uses \"egrep\" by default, but can also use \"ack\", and it can piggyback on the \"ack.vim\" plugin. For more control, it can also take an existing buffer with some search results and turn them into the writable search buffer. Take a look at the documentation to learn more.\r\n","4":"Github project: https:\/\/github.com\/AndrewRadev\/writable_search.vim\r\n\r\nThe plugin exposes the command `:WritableSearch`, which takes a search query and performs a grep (or ack, or a different search command -- see below), with that query. For example:\r\n\r\n    :WritableSearch function_call\\(\r\n\r\nThe results are opened in a new tab (by default), and are very similar to what you would get from performing the search on the command-line. The difference is that you can now edit this buffer and, upon writing, the original files will be updated with the changes. This gives you a very simple and straightforward search-and-replace process.\r\n\r\nIf you change the filenames in the header blocks, those files will be renamed (with some manual confirmation that you can turn off if you're feeling adventurous). For example, if the header says:\r\n\r\n    foo\/bar.txt:12-34\r\n\r\nand you change that to:\r\n\r\n    foo\/renamed.txt:12-34\r\n\r\nThen the file \"foo\/bar.txt\" will be renamed to \"foo\/renamed.txt\". If this is not possible, you'll get an error.\r\n\r\nIf you change the line numbers displayed in the headers, the virtual \"window\" that this search result is pointing to will reposition itself to those line numbers. For example, if the header says:\r\n\r\n    foo\/bar.txt:12-34\r\n\r\nand you change that to:\r\n\r\n    foo\/bar.txt:10-22\r\n\r\nThen the lines displayed will now be the ones from 10 to 22.\r\n\r\nThe plugin uses \"egrep\" by default, but can also use \"ack\", and it can piggyback on the \"ack.vim\" plugin. For more control, it can also take an existing buffer with some search results and turn them into the writable search buffer. Take a look at the documentation to learn more.\r\n","install_details":"There are several ways to install the plugin. The recommended one is by using Tim Pope's pathogen (http:\/\/www.vim.org\/scripts\/script.php?script_id=2332). In that case, you can clone the plugin's git repository like so:\r\n\r\n    git clone git:\/\/github.com\/AndrewRadev\/writable_search.vim.git ~\/.vim\/bundle\/writable_search\r\n\r\nIf your vim configuration is under git version control, you could also set up the repository as a submodule, which would allow you to update more easily. The command is (provided you're in ~\/.vim):\r\n\r\n    git submodule add git:\/\/github.com\/AndrewRadev\/writable_search.vim.git bundle\/writable_search\r\n\r\nAnother way is to simply copy all the essential directories inside the ~\/.vim directory: autoload, doc, ftplugin, plugin, syntax.","5":"There are several ways to install the plugin. The recommended one is by using Tim Pope's pathogen (http:\/\/www.vim.org\/scripts\/script.php?script_id=2332). In that case, you can clone the plugin's git repository like so:\r\n\r\n    git clone git:\/\/github.com\/AndrewRadev\/writable_search.vim.git ~\/.vim\/bundle\/writable_search\r\n\r\nIf your vim configuration is under git version control, you could also set up the repository as a submodule, which would allow you to update more easily. The command is (provided you're in ~\/.vim):\r\n\r\n    git submodule add git:\/\/github.com\/AndrewRadev\/writable_search.vim.git bundle\/writable_search\r\n\r\nAnother way is to simply copy all the essential directories inside the ~\/.vim directory: autoload, doc, ftplugin, plugin, syntax.","first_name":"Andrew","6":"Andrew","last_name":"Radev","7":"Radev","releases":[{"0":"4865","vim_version":"7.0","1":"7.0","script_version":"0.2.0","2":"0.2.0","version_comment":"Configurable backends, like: ack, git-grep, egrep. Possible to, for example, set up \"ack\" as default, but use \"git-grep\" if we're in a git repository.","3":"Configurable backends, like: ack, git-grep, egrep. Possible to, for example, set up \"ack\" as default, but use \"git-grep\" if we're in a git repository.","package":"writable_search.zip","4":"writable_search.zip","src_id":"22839","5":"22839","creation_date":"1422354152","6":"1422354152"},{"0":"4865","vim_version":"7.0","1":"7.0","script_version":"0.1.0","2":"0.1.0","version_comment":"Initial upload","3":"Initial upload","package":"writable_search.zip","4":"writable_search.zip","src_id":"21487","5":"21487","creation_date":"1392483055","6":"1392483055"}]},"4864":{"script_id":"4864","0":"4864","script_name":"c.vim","1":"c.vim","script_type":"syntax","2":"syntax","summary":"Highlight more syntax items of C program","3":"Highlight more syntax items of C program","description":"This script contains two vim files: \"c.vim\" and \"workpath.vim\".\r\n\"workpath.vim\" is used to set the current work path, which contains\r\nsource code you want to edit and relative tags file. It works together with\r\nthe other syntax script \"c.vim\". \"c.vim\" searches the tags file to identify\r\ndifferent syntax items, such as macros, typedefs, structs, enums, etc. So, if\r\nyou want to use the \"c.vim\" to highlight your C programs, you need to assign\r\nthe work path which contains the tags file of your C programs.","4":"This script contains two vim files: \"c.vim\" and \"workpath.vim\".\r\n\"workpath.vim\" is used to set the current work path, which contains\r\nsource code you want to edit and relative tags file. It works together with\r\nthe other syntax script \"c.vim\". \"c.vim\" searches the tags file to identify\r\ndifferent syntax items, such as macros, typedefs, structs, enums, etc. So, if\r\nyou want to use the \"c.vim\" to highlight your C programs, you need to assign\r\nthe work path which contains the tags file of your C programs.","install_details":"1. Download the c.zip file and unzip the files to the $VIM\/vimfiles directory.\r\n   After this step, you should have the following three files (the directory\r\n   structure should be preserved):\r\n\r\n\tafter\/syntax\/c.vim  - syntax script for C language\r\n\tplugin\/workpath.vim - set tags file path for \"c.vim\"\r\n\tdoc\/workpath.txt    - documentation (help) file\r\n\r\n2. Change to the $VIM\/vimfiles\/doc directory, and run the \":helptags .\"\r\n   command to process the workpath help file. Without this step, you can not\r\n   jump to the workpath help topics.\r\n3. Restart Vim.","5":"1. Download the c.zip file and unzip the files to the $VIM\/vimfiles directory.\r\n   After this step, you should have the following three files (the directory\r\n   structure should be preserved):\r\n\r\n\tafter\/syntax\/c.vim  - syntax script for C language\r\n\tplugin\/workpath.vim - set tags file path for \"c.vim\"\r\n\tdoc\/workpath.txt    - documentation (help) file\r\n\r\n2. Change to the $VIM\/vimfiles\/doc directory, and run the \":helptags .\"\r\n   command to process the workpath help file. Without this step, you can not\r\n   jump to the workpath help topics.\r\n3. Restart Vim.","first_name":"Liu","6":"Liu","last_name":"Zemin","7":"Zemin","releases":[{"0":"4864","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"c.zip","4":"c.zip","src_id":"21485","5":"21485","creation_date":"1392450086","6":"1392450086"}]},"4863":{"script_id":"4863","0":"4863","script_name":"jdaddy.vim","1":"jdaddy.vim","script_type":"utility","2":"utility","summary":"JSON manipulation and pretty printing","3":"JSON manipulation and pretty printing","description":"Check out these *must have* mappings for working with JSON in Vim:\r\n\r\n* `aj` provides a text object for the outermost JSON object, array, string, number, or keyword.\r\n* `gqaj` \"pretty prints\" (wraps\/indents\/sorts keys\/otherwise cleans up) the JSON construct under the cursor.\r\n* `gwaj` takes the JSON object on the clipboard and extends it into the JSON object under the cursor.\r\n\r\nThere are also `ij` variants that target innermost rather than outermost JSON construct.\r\n\r\nhttps:\/\/github.com\/tpope\/vim-jdaddy","4":"Check out these *must have* mappings for working with JSON in Vim:\r\n\r\n* `aj` provides a text object for the outermost JSON object, array, string, number, or keyword.\r\n* `gqaj` \"pretty prints\" (wraps\/indents\/sorts keys\/otherwise cleans up) the JSON construct under the cursor.\r\n* `gwaj` takes the JSON object on the clipboard and extends it into the JSON object under the cursor.\r\n\r\nThere are also `ij` variants that target innermost rather than outermost JSON construct.\r\n\r\nhttps:\/\/github.com\/tpope\/vim-jdaddy","install_details":"Extract in ~\/.vim (~\\vimfiles on Windows).","5":"Extract in ~\/.vim (~\\vimfiles on Windows).","first_name":"Tim","6":"Tim","last_name":"Pope","7":"Pope","releases":[{"0":"4863","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"jdaddy.zip","4":"jdaddy.zip","src_id":"21481","5":"21481","creation_date":"1392322992","6":"1392322992"}]},"4862":{"script_id":"4862","0":"4862","script_name":"hybris ImpEx","1":"hybris ImpEx","script_type":"syntax","2":"syntax","summary":"Providing syntax highlight for hybris ImpEx file","3":"Providing syntax highlight for hybris ImpEx file","description":"For ImpEx syntax, please refer to the following link\r\n\r\nhttps:\/\/wiki.hybris.com\/display\/release5\/ImpEx+Syntax","4":"For ImpEx syntax, please refer to the following link\r\n\r\nhttps:\/\/wiki.hybris.com\/display\/release5\/ImpEx+Syntax","install_details":"1. Put the file in your ~\/.vim\/syntax directory. \r\n2. Modify your .vimrc file and add:\r\n\r\nau BufRead,BufNewFile *.impex set filetype=impex","5":"1. Put the file in your ~\/.vim\/syntax directory. \r\n2. Modify your .vimrc file and add:\r\n\r\nau BufRead,BufNewFile *.impex set filetype=impex","first_name":"Nevin","6":"Nevin","last_name":"Ng","7":"Ng","releases":[{"0":"4862","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"impex.vim","4":"impex.vim","src_id":"21470","5":"21470","creation_date":"1392191532","6":"1392191532"}]},"4861":{"script_id":"4861","0":"4861","script_name":"sql.snippets","1":"sql.snippets","script_type":"utility","2":"utility","summary":"T-SQL snippets","3":"T-SQL snippets","description":"Some snippets for T-SQL. For use with the snipmate plugin in Vim.","4":"Some snippets for T-SQL. For use with the snipmate plugin in Vim.","install_details":"Put the file in ~YourSnipmatePath~\/snippets","5":"Put the file in ~YourSnipmatePath~\/snippets","first_name":"Mike","6":"Mike","last_name":"Z","7":"Z","releases":[{"0":"4861","vim_version":"7.4","1":"7.4","script_version":"0.91","2":"0.91","version_comment":"a few snips for remembering syntax. copy data from source to dest.","3":"a few snips for remembering syntax. copy data from source to dest.","package":"sql.snippets","4":"sql.snippets","src_id":"21614","5":"21614","creation_date":"1394747674","6":"1394747674"},{"0":"4861","vim_version":"7.3","1":"7.3","script_version":"0.9","2":"0.9","version_comment":"if\/else, try\/catch","3":"if\/else, try\/catch","package":"sql.snippets","4":"sql.snippets","src_id":"21543","5":"21543","creation_date":"1393542353","6":"1393542353"},{"0":"4861","vim_version":"7.3","1":"7.3","script_version":"0.8","2":"0.8","version_comment":"A few pagination queries. Exists check","3":"A few pagination queries. Exists check","package":"sql.snippets","4":"sql.snippets","src_id":"21509","5":"21509","creation_date":"1392828096","6":"1392828096"},{"0":"4861","vim_version":"7.3","1":"7.3","script_version":"0.71","2":"0.71","version_comment":"junction table snippet","3":"junction table snippet","package":"sql.snippets","4":"sql.snippets","src_id":"21501","5":"21501","creation_date":"1392686672","6":"1392686672"},{"0":"4861","vim_version":"7.3","1":"7.3","script_version":"0.6","2":"0.6","version_comment":"snippets for insert, update, delete, and CTEs.","3":"snippets for insert, update, delete, and CTEs.","package":"sql.snippets","4":"sql.snippets","src_id":"21484","5":"21484","creation_date":"1392414179","6":"1392414179"},{"0":"4861","vim_version":"7.3","1":"7.3","script_version":"0.5","2":"0.5","version_comment":"Snippets added for loops, cursors, and joins.","3":"Snippets added for loops, cursors, and joins.","package":"sql.snippets","4":"sql.snippets","src_id":"21476","5":"21476","creation_date":"1392241631","6":"1392241631"},{"0":"4861","vim_version":"7.3","1":"7.3","script_version":"0.4","2":"0.4","version_comment":"snippets added for unique keys and check constraints.","3":"snippets added for unique keys and check constraints.","package":"sql.snippets","4":"sql.snippets","src_id":"21466","5":"21466","creation_date":"1392128388","6":"1392128388"},{"0":"4861","vim_version":"7.3","1":"7.3","script_version":"0.3","2":"0.3","version_comment":"more snippets","3":"more snippets","package":"sql.snippets","4":"sql.snippets","src_id":"21462","5":"21462","creation_date":"1392092070","6":"1392092070"},{"0":"4861","vim_version":"7.3","1":"7.3","script_version":"0.2","2":"0.2","version_comment":"More snippets added","3":"More snippets added","package":"sql.snippets","4":"sql.snippets","src_id":"21460","5":"21460","creation_date":"1392077789","6":"1392077789"},{"0":"4861","vim_version":"7.3","1":"7.3","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"sql.snippets","4":"sql.snippets","src_id":"21458","5":"21458","creation_date":"1392070569","6":"1392070569"}]},"4860":{"script_id":"4860","0":"4860","script_name":"VimMahewinHub","1":"VimMahewinHub","script_type":"indent","2":"indent","summary":"Interface for hub command.","3":"Interface for hub command.","description":"Provides an interface to hub for a github integration.","4":"Provides an interface to hub for a github integration.","install_details":"Decompress archive: tar -zxvf vim-mahewin-hub.tar.gz,  in your .vim ","5":"Decompress archive: tar -zxvf vim-mahewin-hub.tar.gz,  in your .vim ","first_name":"Natal","6":"Natal","last_name":"Ng\u00c3\u00a9tal","7":"Ng\u00c3\u00a9tal","releases":[{"0":"4860","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"vim-mahewin-hub.tar.gz","4":"vim-mahewin-hub.tar.gz","src_id":"21457","5":"21457","creation_date":"1391989109","6":"1391989109"}]},"4859":{"script_id":"4859","0":"4859","script_name":"better-whitespace","1":"better-whitespace","script_type":"utility","2":"utility","summary":"A better whitespace highlighter for Vim","3":"A better whitespace highlighter for Vim","description":"This plugin causes all trailing whitespace characters (spaces and tabs) to be highlighted.\r\nWhitespace for the current line will not be highlighted while in insert mode. \r\nIt is possible to disable current line highlighting while in other modes as well.\r\nA helper function ':StripWhitespace' is also provided to make whitespace cleaning painless.\r\n\r\nCheck out a screenshot: http:\/\/i.imgur.com\/St7yHth.png\r\nMore are screenshots available at the Github repository below.\r\n\r\nSee further documentation at its Github repository:\r\nhttps:\/\/github.com\/ntpeters\/vim-better-whitespace","4":"This plugin causes all trailing whitespace characters (spaces and tabs) to be highlighted.\r\nWhitespace for the current line will not be highlighted while in insert mode. \r\nIt is possible to disable current line highlighting while in other modes as well.\r\nA helper function ':StripWhitespace' is also provided to make whitespace cleaning painless.\r\n\r\nCheck out a screenshot: http:\/\/i.imgur.com\/St7yHth.png\r\nMore are screenshots available at the Github repository below.\r\n\r\nSee further documentation at its Github repository:\r\nhttps:\/\/github.com\/ntpeters\/vim-better-whitespace","install_details":"There are a few ways you can go about installing this plugin:\r\n\r\n1.  If you have Vundle you can simply add: Bundle 'ntpeters\/vim-better-whitespace' to your .vimrc file then run: \":BundleInstall\"\r\n\r\n2.  If you are using Pathogen, you can just run the following command: \"git clone git:\/\/github.com\/ntpeters\/vim-better-whitespace.git ~\/.vim\/bundle\/\"\r\n\r\n3.  While this plugin can also be installed by copying its contents into your \"~\/.vim\/\" directory, I would highly recommend using one of the above methods as they make managing your Vim plugins painless.","5":"There are a few ways you can go about installing this plugin:\r\n\r\n1.  If you have Vundle you can simply add: Bundle 'ntpeters\/vim-better-whitespace' to your .vimrc file then run: \":BundleInstall\"\r\n\r\n2.  If you are using Pathogen, you can just run the following command: \"git clone git:\/\/github.com\/ntpeters\/vim-better-whitespace.git ~\/.vim\/bundle\/\"\r\n\r\n3.  While this plugin can also be installed by copying its contents into your \"~\/.vim\/\" directory, I would highly recommend using one of the above methods as they make managing your Vim plugins painless.","first_name":"Nate","6":"Nate","last_name":"Peterson","7":"Peterson","releases":[{"0":"4859","vim_version":"7.2","1":"7.2","script_version":"1.2","2":"1.2","version_comment":"Features:\r\n- Support all unicode whitespace characters\r\n- Per buffer enable\/disable\r\n- Verbose output option\r\n\r\nFixes:\r\n- Do not clear all matches. Only clear this match group.\r\n- Enable\/disable across all windows\r\n- Blacklist file types 'diff', 'gitcomment', 'unite', 'qf', 'help', 'markdown' by default\r\n- Reset highlight group after color scheme changes\r\n- Remove redundant autocommand events\r\n","3":"Features:\r\n- Support all unicode whitespace characters\r\n- Per buffer enable\/disable\r\n- Verbose output option\r\n\r\nFixes:\r\n- Do not clear all matches. Only clear this match group.\r\n- Enable\/disable across all windows\r\n- Blacklist file types 'diff', 'gitcomment', 'unite', 'qf', 'help', 'markdown' by default\r\n- Reset highlight group after color scheme changes\r\n- Remove redundant autocommand events\r\n","package":"better-whitespace.tar.gz","4":"better-whitespace.tar.gz","src_id":"24897","5":"24897","creation_date":"1484515652","6":"1484515652"},{"0":"4859","vim_version":"7.2","1":"7.2","script_version":"1.1.0","2":"1.1.0","version_comment":"Add ability to blacklist certain file types.","3":"Add ability to blacklist certain file types.","package":"better-whitespace.tar.gz","4":"better-whitespace.tar.gz","src_id":"22074","5":"22074","creation_date":"1403393282","6":"1403393282"},{"0":"4859","vim_version":"7.2","1":"7.2","script_version":"1.0.2","2":"1.0.2","version_comment":"Minor update to ensure loading of autocommands on initial script load.","3":"Minor update to ensure loading of autocommands on initial script load.","package":"better-whitespace.tar.gz","4":"better-whitespace.tar.gz","src_id":"21475","5":"21475","creation_date":"1392234801","6":"1392234801"},{"0":"4859","vim_version":"7.2","1":"7.2","script_version":"1.0.1","2":"1.0.1","version_comment":"Readme and documentation updates","3":"Readme and documentation updates","package":"better-whitespace.tar.gz","4":"better-whitespace.tar.gz","src_id":"21459","5":"21459","creation_date":"1392076638","6":"1392076638"},{"0":"4859","vim_version":"7.2","1":"7.2","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"better-whitespace.tar.gz","4":"better-whitespace.tar.gz","src_id":"21455","5":"21455","creation_date":"1391975279","6":"1391975279"}]},"4858":{"script_id":"4858","0":"4858","script_name":"stdtabs","1":"stdtabs","script_type":"indent","2":"indent","summary":"Indentation for some languages according to their most used style guidelines.","3":"Indentation for some languages according to their most used style guidelines.","description":"Find documentation at:\r\nhttps:\/\/github.com\/sdanielf\/vim-stdtabs\/","4":"Find documentation at:\r\nhttps:\/\/github.com\/sdanielf\/vim-stdtabs\/","install_details":"","5":"","first_name":"Daniel","6":"Daniel","last_name":"Francis","7":"Francis","releases":[{"0":"4858","vim_version":"7.0","1":"7.0","script_version":"0.2","2":"0.2","version_comment":"https:\/\/github.com\/sdanielf\/vim-stdtabs\/releases\/tag\/v0.2","3":"https:\/\/github.com\/sdanielf\/vim-stdtabs\/releases\/tag\/v0.2","package":"vim-stdtabs.tar.gz","4":"vim-stdtabs.tar.gz","src_id":"21454","5":"21454","creation_date":"1391973306","6":"1391973306"}]},"4857":{"script_id":"4857","0":"4857","script_name":"APL character picker","1":"APL character picker","script_type":"utility","2":"utility","summary":"A pop-up menu for inserting APL characters","3":"A pop-up menu for inserting APL characters","description":"The scripts maps the \u00c2\u00b2 key (which can be changed according to the needs) to a pop-up console menu displaying all glyphs in the Unicode range 2336-237a for quickly inserting them.","4":"The scripts maps the \u00c2\u00b2 key (which can be changed according to the needs) to a pop-up console menu displaying all glyphs in the Unicode range 2336-237a for quickly inserting them.","install_details":"Add\r\n  set wildmenu\r\nin your ~\/.vimrc file","5":"Add\r\n  set wildmenu\r\nin your ~\/.vimrc file","first_name":"Thomas","6":"Thomas","last_name":"Baruchel","7":"Baruchel","releases":[{"0":"4857","vim_version":"7.0","1":"7.0","script_version":"1.1","2":"1.1","version_comment":"Added the \"set wildmenu\" in the plugin in order to make sure the plugin will work.","3":"Added the \"set wildmenu\" in the plugin in order to make sure the plugin will work.","package":"apl.vim","4":"apl.vim","src_id":"21488","5":"21488","creation_date":"1392491553","6":"1392491553"},{"0":"4857","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"apl.vim","4":"apl.vim","src_id":"21452","5":"21452","creation_date":"1391967344","6":"1391967344"}]},"4856":{"script_id":"4856","0":"4856","script_name":"CRDispatcher","1":"CRDispatcher","script_type":"utility","2":"utility","summary":"dispatch CR in the command line","3":"dispatch CR in the command line","description":"# CRDispatcher Vim Plugin\r\nThis is a utility plugin which is used in my other Vim plugins.  It let\r\nregieter callback functions which transform the command line after hitting\r\nenter: for example EnchantedVim is using it to add `\\v` to patterns.\r\n\r\nIt also has a nice hack to make `c_CTRL-f` work nicely: it will transform\r\nthe line when entering the command line.  The `crdispatcher#CRDsiaptcher` dict\r\nwhich is passed to callbacks has `ctrl_f` entry which is `1` in this case.\r\nThis is useful if a callback should only be used with `<cr>` or `ctrl-f`.\r\n\r\nThe plugins that depend on it are:\r\n* [System](https:\/\/github.com\/coot\/System)\r\n* [CommandAlias](https:\/\/www.github.com\/coot\/cmdalias_vim)\r\n* [EnchantedVim](https:\/\/github.com\/coot\/EnchantedVim)\r\n\r\n## Callbacks\r\nEvery callback function axcepts one argument: the crdispatcher#CRDispatcher\r\ndictionary, and it can modify the cmdline value.\r\n\r\n## Note\r\nYou can use the expression register with Vim 7.3.686 or later.  With an earlier version\r\nyou will not be able to use it.\r\n\r\n## Code\r\nThis plugin is a simple example of OO programing in VimL.\r\n\r\n* Copyright: \u00c2\u00a9 Marcin Szamotulski, 2014\r\n* License: vim-license, see `:help license`\r\n","4":"# CRDispatcher Vim Plugin\r\nThis is a utility plugin which is used in my other Vim plugins.  It let\r\nregieter callback functions which transform the command line after hitting\r\nenter: for example EnchantedVim is using it to add `\\v` to patterns.\r\n\r\nIt also has a nice hack to make `c_CTRL-f` work nicely: it will transform\r\nthe line when entering the command line.  The `crdispatcher#CRDsiaptcher` dict\r\nwhich is passed to callbacks has `ctrl_f` entry which is `1` in this case.\r\nThis is useful if a callback should only be used with `<cr>` or `ctrl-f`.\r\n\r\nThe plugins that depend on it are:\r\n* [System](https:\/\/github.com\/coot\/System)\r\n* [CommandAlias](https:\/\/www.github.com\/coot\/cmdalias_vim)\r\n* [EnchantedVim](https:\/\/github.com\/coot\/EnchantedVim)\r\n\r\n## Callbacks\r\nEvery callback function axcepts one argument: the crdispatcher#CRDispatcher\r\ndictionary, and it can modify the cmdline value.\r\n\r\n## Note\r\nYou can use the expression register with Vim 7.3.686 or later.  With an earlier version\r\nyou will not be able to use it.\r\n\r\n## Code\r\nThis plugin is a simple example of OO programing in VimL.\r\n\r\n* Copyright: \u00c2\u00a9 Marcin Szamotulski, 2014\r\n* License: vim-license, see `:help license`\r\n","install_details":"Open the vimball file in vim and source it with  :so%","5":"Open the vimball file in vim and source it with  :so%","first_name":"Marcin","6":"Marcin","last_name":"Szamotulski","7":"Szamotulski","releases":[{"0":"4856","vim_version":"7.0","1":"7.0","script_version":"2","2":"2","version_comment":"New better version which includes parsers for command line.","3":"New better version which includes parsers for command line.","package":"crdispatcher.vmb","4":"crdispatcher.vmb","src_id":"21550","5":"21550","creation_date":"1393664685","6":"1393664685"},{"0":"4856","vim_version":"7.3","1":"7.3","script_version":"1","2":"1","version_comment":"Initial upload","3":"Initial upload","package":"crdispatcher.vba","4":"crdispatcher.vba","src_id":"21435","5":"21435","creation_date":"1391720788","6":"1391720788"}]},"4853":{"script_id":"4853","0":"4853","script_name":"scd.vim","1":"scd.vim","script_type":"utility","2":"utility","summary":"smart change of directory in Vim","3":"smart change of directory in Vim","description":"Add commands :Scd and :Slcd for changing to any directory with a few keystrokes.  Record the Vim-visited directories in the scd directory index.  This plugin is an interface to the scd shell script that provides the same functionality in a terminal.\r\n\r\nFor details see\r\nhttps:\/\/github.com\/pavoljuhas\/scd.vim","4":"Add commands :Scd and :Slcd for changing to any directory with a few keystrokes.  Record the Vim-visited directories in the scd directory index.  This plugin is an interface to the scd shell script that provides the same functionality in a terminal.\r\n\r\nFor details see\r\nhttps:\/\/github.com\/pavoljuhas\/scd.vim","install_details":"Linux, Mac OS X or other Unix-like system only.\r\n\r\n(1) Make sure zsh (Z shell) is available or install it with \"sudo apt-get install zsh\".\r\n\r\n(2) Expand the archive in the ~\/.vim directory\r\n\r\ntar xzf scd-1.3.tar.gz -C ~\/.vim\/\r\n\r\nOr if you use pathogen.vim, add scd.vim repository to your bundles:\r\n\r\ncd ~\/.vim\/bundle\r\ngit clone https:\/\/github.com\/pavoljuhas\/scd.vim\r\n\r\n(3) Optional - for best results activate scd also in system shell as described at\r\nhttps:\/\/github.com\/pavoljuhas\/scd.vim\/blob\/master\/scd_tools\/README.md#installation.","5":"Linux, Mac OS X or other Unix-like system only.\r\n\r\n(1) Make sure zsh (Z shell) is available or install it with \"sudo apt-get install zsh\".\r\n\r\n(2) Expand the archive in the ~\/.vim directory\r\n\r\ntar xzf scd-1.3.tar.gz -C ~\/.vim\/\r\n\r\nOr if you use pathogen.vim, add scd.vim repository to your bundles:\r\n\r\ncd ~\/.vim\/bundle\r\ngit clone https:\/\/github.com\/pavoljuhas\/scd.vim\r\n\r\n(3) Optional - for best results activate scd also in system shell as described at\r\nhttps:\/\/github.com\/pavoljuhas\/scd.vim\/blob\/master\/scd_tools\/README.md#installation.","first_name":"Pavol","6":"Pavol","last_name":"Juhas","7":"Juhas","releases":[{"0":"4853","vim_version":"7.0","1":"7.0","script_version":"1.3","2":"1.3","version_comment":"- Check for a directory change also in insert mode.\r\n- Improve operation of :Scd --unalias.\r\n- Remove non-existent paths when trimming the index.\r\n- Add tip on using directory aliases in Vim paths.","3":"- Check for a directory change also in insert mode.\r\n- Improve operation of :Scd --unalias.\r\n- Remove non-existent paths when trimming the index.\r\n- Add tip on using directory aliases in Vim paths.","package":"scd-1.3.tar.gz","4":"scd-1.3.tar.gz","src_id":"23182","5":"23182","creation_date":"1429216886","6":"1429216886"},{"0":"4853","vim_version":"7.0","1":"7.0","script_version":"1.2","2":"1.2","version_comment":"* reorder files for standard plugin installation and for pathogen support.\r\n* add end-of-path matching with $.\r\n* Add option -A,--all for all matches.\r\n* Compress index duplicates to an equivalent timestamp.\r\n* Simplify directory matching.\r\n","3":"* reorder files for standard plugin installation and for pathogen support.\r\n* add end-of-path matching with $.\r\n* Add option -A,--all for all matches.\r\n* Compress index duplicates to an equivalent timestamp.\r\n* Simplify directory matching.\r\n","package":"scd-1.2.tar.gz","4":"scd-1.2.tar.gz","src_id":"22398","5":"22398","creation_date":"1409595121","6":"1409595121"},{"0":"4853","vim_version":"7.0","1":"7.0","script_version":"1.1","2":"1.1","version_comment":"avoid duplicate entries after 'cd .', improve documentation and code clarity.","3":"avoid duplicate entries after 'cd .', improve documentation and code clarity.","package":"scd-1.1.tar.gz","4":"scd-1.1.tar.gz","src_id":"21629","5":"21629","creation_date":"1395090913","6":"1395090913"},{"0":"4853","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"scd-1.0.tar.gz","4":"scd-1.0.tar.gz","src_id":"21424","5":"21424","creation_date":"1391488602","6":"1391488602"}]},"4852":{"script_id":"4852","0":"4852","script_name":"vawa.vim","1":"vawa.vim","script_type":"utility","2":"utility","summary":"A plugin that will highlight all occurances of the php variable under the cursor","3":"A plugin that will highlight all occurances of the php variable under the cursor","description":"For detailed description please visit https:\/\/bitbucket.org\/sras\/vawa.","4":"For detailed description please visit https:\/\/bitbucket.org\/sras\/vawa.","install_details":"If you are using pathogen, just clone the  mercurial repo at https:\/\/bitbucket.org\/sras\/vawa into your bundles directory.\r\n\r\nIf you are not using pathogen, then just place the vawa.vim file in the plugins directory.","5":"If you are using pathogen, just clone the  mercurial repo at https:\/\/bitbucket.org\/sras\/vawa into your bundles directory.\r\n\r\nIf you are not using pathogen, then just place the vawa.vim file in the plugins directory.","first_name":"Sandeep","6":"Sandeep","last_name":"CR","7":"CR","releases":[{"0":"4852","vim_version":"7.2","1":"7.2","script_version":"1.00","2":"1.00","version_comment":"Initial upload","3":"Initial upload","package":"vawa.vim","4":"vawa.vim","src_id":"21421","5":"21421","creation_date":"1391418126","6":"1391418126"}]},"4851":{"script_id":"4851","0":"4851","script_name":"grin.vim","1":"grin.vim","script_type":"utility","2":"utility","summary":"  Vim plugin for 'grin', the Python port of 'ack'","3":"  Vim plugin for 'grin', the Python port of 'ack'","description":"This plugin is a front for grin, the python version of Ack. Grin can be used as a replacement for grep, it will allow you to run grin from vim, get the results in a split window and open them right in the editor.","4":"This plugin is a front for grin, the python version of Ack. Grin can be used as a replacement for grep, it will allow you to run grin from vim, get the results in a split window and open them right in the editor.","install_details":" Grin\r\n\r\nInstall grin at OS level, user levle or even on a virtualenv:\r\n\r\nGlobal install\r\n\r\n$ sudo pip install grin\r\n\r\nUser install:\r\n\r\n$ pip install --user grin\r\n\r\nIn a Virtualenv: \r\n\r\n$ mkvirtualenv grin\r\n$ workon grin\r\n$ pip install grin\r\n\r\nYou can specify a custom grin name and path in your .vimrc like so:\r\n\r\nlet g:grinprg=\"<custom-grin-path> --emacs\"\r\n\r\nThe Plugin\r\n\r\nIf you don't have a preferred installation method, I recommend installing pathogen.vim, and then simply copy and paste:\r\n\r\n$ cd ~\/.vim\/bundle\r\n$ git clone git:\/\/github.com\/santiycr\/grin.vim.git\r\n\r\nOnce help tags have been generated, you can view the manual with :help fugitive.","5":" Grin\r\n\r\nInstall grin at OS level, user levle or even on a virtualenv:\r\n\r\nGlobal install\r\n\r\n$ sudo pip install grin\r\n\r\nUser install:\r\n\r\n$ pip install --user grin\r\n\r\nIn a Virtualenv: \r\n\r\n$ mkvirtualenv grin\r\n$ workon grin\r\n$ pip install grin\r\n\r\nYou can specify a custom grin name and path in your .vimrc like so:\r\n\r\nlet g:grinprg=\"<custom-grin-path> --emacs\"\r\n\r\nThe Plugin\r\n\r\nIf you don't have a preferred installation method, I recommend installing pathogen.vim, and then simply copy and paste:\r\n\r\n$ cd ~\/.vim\/bundle\r\n$ git clone git:\/\/github.com\/santiycr\/grin.vim.git\r\n\r\nOnce help tags have been generated, you can view the manual with :help fugitive.","first_name":"Santiago","6":"Santiago","last_name":"Suarez Ordo\u00c3\u00b1ez","7":"Suarez Ordo\u00c3\u00b1ez","releases":[{"0":"4851","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"grin.vim.tar.gz","4":"grin.vim.tar.gz","src_id":"21420","5":"21420","creation_date":"1391389268","6":"1391389268"}]},"4850":{"script_id":"4850","0":"4850","script_name":"vim-colors-pencil","1":"vim-colors-pencil","script_type":"color scheme","2":"color scheme","summary":"A light (and dark) color scheme inspired by iA Writer","3":"A light (and dark) color scheme inspired by iA Writer","description":"The pencil color scheme takes its inspiration from iA Writer, an elegant word processor available on the iOS and OSX platforms.\r\n\r\nThis Vim color scheme features:\r\n\r\n* Subtle indicators of changes in the gutter for Signify, git-gutter, etc.\r\n* Use for both code and prose, though it\u00e2\u0080\u0099s definitely geared towards the latter\r\n* Light and dark variants\r\n* iTerm color scheme available, for use in terminal-based Vim\r\n\r\nScreen shot (and latest version) at https:\/\/github.com\/reedes\/vim-colors-pencil\r\n\r\nUse just like any other colorscheme:\r\n\r\n:colorscheme pencil\r\n\r\nIt has both dark and light variants:\r\n\r\n:set background=dark\r\n:set background=light\r\n\r\nDifferences with iA Writer: most notably, the \u00e2\u0080\u0098#\u00e2\u0080\u0099 heading text is shaded blue. This compensates for the lack of a visual cue found in iA Writer where the heading indicators are inside the left margin. Here we use color instead.\r\n\r\nA corresponding iTerm color scheme to enable use of this color scheme with terminal-based Vim can be found at https:\/\/github.com\/mattly\/iterm-colors-pencil\r\n\r\nInteract with the color scheme at the http:\/\/vimcolors.com website.","4":"The pencil color scheme takes its inspiration from iA Writer, an elegant word processor available on the iOS and OSX platforms.\r\n\r\nThis Vim color scheme features:\r\n\r\n* Subtle indicators of changes in the gutter for Signify, git-gutter, etc.\r\n* Use for both code and prose, though it\u00e2\u0080\u0099s definitely geared towards the latter\r\n* Light and dark variants\r\n* iTerm color scheme available, for use in terminal-based Vim\r\n\r\nScreen shot (and latest version) at https:\/\/github.com\/reedes\/vim-colors-pencil\r\n\r\nUse just like any other colorscheme:\r\n\r\n:colorscheme pencil\r\n\r\nIt has both dark and light variants:\r\n\r\n:set background=dark\r\n:set background=light\r\n\r\nDifferences with iA Writer: most notably, the \u00e2\u0080\u0098#\u00e2\u0080\u0099 heading text is shaded blue. This compensates for the lack of a visual cue found in iA Writer where the heading indicators are inside the left margin. Here we use color instead.\r\n\r\nA corresponding iTerm color scheme to enable use of this color scheme with terminal-based Vim can be found at https:\/\/github.com\/mattly\/iterm-colors-pencil\r\n\r\nInteract with the color scheme at the http:\/\/vimcolors.com website.","install_details":"Install using Pathogen, Vundle, Neobundle, or your favorite Vim package manager.\r\n\r\nOr simply copy the colorscheme file to your ~\/.vim\/colors directory.\r\n","5":"Install using Pathogen, Vundle, Neobundle, or your favorite Vim package manager.\r\n\r\nOr simply copy the colorscheme file to your ~\/.vim\/colors directory.\r\n","first_name":"Reed","6":"Reed","last_name":"Esau","7":"Esau","releases":[{"0":"4850","vim_version":"7.0","1":"7.0","script_version":"0.6","2":"0.6","version_comment":"Darker blue for directory group; support for plasticboy\/vim-markdown; option for neutral (normal color) headings in markdown","3":"Darker blue for directory group; support for plasticboy\/vim-markdown; option for neutral (normal color) headings in markdown","package":"vim-colors-pencil-0.6.zip","4":"vim-colors-pencil-0.6.zip","src_id":"21597","5":"21597","creation_date":"1394517414","6":"1394517414"},{"0":"4850","vim_version":"7.0","1":"7.0","script_version":"0.5","2":"0.5","version_comment":"Mute MatchParen from intense pink to bg_subtle; brighter red for dark bg, lighten Visual for Dark, to contrast with Search.","3":"Mute MatchParen from intense pink to bg_subtle; brighter red for dark bg, lighten Visual for Dark, to contrast with Search.","package":"vim-colors-pencil-0.5.zip","4":"vim-colors-pencil-0.5.zip","src_id":"21539","5":"21539","creation_date":"1393467575","6":"1393467575"},{"0":"4850","vim_version":"7.0","1":"7.0","script_version":"0.4","2":"0.4","version_comment":"Initial upload","3":"Initial upload","package":"vim-colors-pencil-0.4.zip","4":"vim-colors-pencil-0.4.zip","src_id":"21419","5":"21419","creation_date":"1391371819","6":"1391371819"}]},"4849":{"script_id":"4849","0":"4849","script_name":"Enchanted Vim","1":"Enchanted Vim","script_type":"utility","2":"utility","summary":"persistent very magic option","3":"persistent very magic option","description":"# Enchanted Vim\r\n\r\nThis is a vim script which makes searches with `\\v` (very magic) persistent.\r\nYou can turn it off temporarily with \r\n```viml\r\n  let g:VeryMagic = 0 (default is 1)\r\n```\r\nor if you are already in the command line you can type `\\m` or `\\M` (see :help\r\n`\\m`).  There are also: very magic `substitute`, `global` and `vimgrep`\r\n(`lvimgrep`), which you have to turn on if you want to use them:\r\n```viml\r\n  let g:VeryMagicSubstitute = 1  \" (default is 0)\r\n  let g:VeryMagicGlobal = 1  \" (default is 0)\r\n  let g:VeryMagicVimGrep = 1  \" (default is 0)\r\n  let g:VeryMagicSearchArg = 1  \" (default is 0, :edit +\/{pattern}))\r\n  let g:VeryMagicFunction = 1  \" (default is 0, :fun \/{pattern})\r\n  let g:VeryMagicHelpgrep = 1  \" (default is 0)\r\n  let g:VeryMagicRange = 1  \" (default is 0, search patterns in command ranges)\r\n  let g:VeryMagicEscapeBackslashesInSearchArg = 1  \" (default is 0, :edit +\/{pattern}))\r\n  let g:SortEditArgs = 1  \" (default is 0, see below)\r\n```\r\n\r\nThe `g:VeryMagicSearchArg` turns on the support for very magic `:edit +\/pat\r\nfile` for various commands which accepts this syntax, i.e. `edit`, `view`,\r\n`visual`, `ex`, `split`, `vsplit`, `new`, `vnew`, `sview`, `find`, `sfind`.\r\nFurthermore with `g:VeryMagicEscapeBackslashesInSearchArg` the backslashes in\r\nthe `+\/` argument will be escaped (yes vim requires that and probably not only\r\nI forget about this) if there is at least one unescaped backslash (this\r\nprevents from double escaping when resuing the command from command history).\r\nYou still need to escape backslashes when you run `vim +\/\\\\vpat` from the\r\ncommand line, e.g. `vim +\"\/\\\\vpattern\" file.vim`.\r\n\r\nIf you set `g:SortEditArgs = 1` the arguments for `:edit` like commands will\r\nbe reordered.  This allows to use `:edit file.txt +\/pattern` which will be\r\nreordered into `:edit +\/pattern file.txt`.\r\n\r\nIf you use `incsearch` setting, you probably want to use `g:VeryMagic = 0` and\r\nset two mappings:\r\n```viml\r\nnm \/ \/\\v\r\nnm ? ?\\v\r\n```\r\notherwise `incsearch` will not work for patterns which contains non\r\nalphanumeric characters.\r\n\r\n## How it works\r\nIt simply injects `\\v` at the beginning of your pattern *after you press enter*\r\nor after c_CTRL-f.\r\n\r\nNote: if you are using one of the two other of my plugins which are defining\r\nmaps to <CR> in the command line, you need to update them to the latest\r\nversion so that they will all work:\r\n* [System](https:\/\/github.com\/coot\/System)\r\n* [CommandAlias](https:\/\/github.com\/coot\/cmdalias_vim)\r\n\r\n# Requirements\r\nYou have to also install\r\n[CRDispatcher](https:\/\/www.github\/coot\/CRDispatcher) plugin.\r\n","4":"# Enchanted Vim\r\n\r\nThis is a vim script which makes searches with `\\v` (very magic) persistent.\r\nYou can turn it off temporarily with \r\n```viml\r\n  let g:VeryMagic = 0 (default is 1)\r\n```\r\nor if you are already in the command line you can type `\\m` or `\\M` (see :help\r\n`\\m`).  There are also: very magic `substitute`, `global` and `vimgrep`\r\n(`lvimgrep`), which you have to turn on if you want to use them:\r\n```viml\r\n  let g:VeryMagicSubstitute = 1  \" (default is 0)\r\n  let g:VeryMagicGlobal = 1  \" (default is 0)\r\n  let g:VeryMagicVimGrep = 1  \" (default is 0)\r\n  let g:VeryMagicSearchArg = 1  \" (default is 0, :edit +\/{pattern}))\r\n  let g:VeryMagicFunction = 1  \" (default is 0, :fun \/{pattern})\r\n  let g:VeryMagicHelpgrep = 1  \" (default is 0)\r\n  let g:VeryMagicRange = 1  \" (default is 0, search patterns in command ranges)\r\n  let g:VeryMagicEscapeBackslashesInSearchArg = 1  \" (default is 0, :edit +\/{pattern}))\r\n  let g:SortEditArgs = 1  \" (default is 0, see below)\r\n```\r\n\r\nThe `g:VeryMagicSearchArg` turns on the support for very magic `:edit +\/pat\r\nfile` for various commands which accepts this syntax, i.e. `edit`, `view`,\r\n`visual`, `ex`, `split`, `vsplit`, `new`, `vnew`, `sview`, `find`, `sfind`.\r\nFurthermore with `g:VeryMagicEscapeBackslashesInSearchArg` the backslashes in\r\nthe `+\/` argument will be escaped (yes vim requires that and probably not only\r\nI forget about this) if there is at least one unescaped backslash (this\r\nprevents from double escaping when resuing the command from command history).\r\nYou still need to escape backslashes when you run `vim +\/\\\\vpat` from the\r\ncommand line, e.g. `vim +\"\/\\\\vpattern\" file.vim`.\r\n\r\nIf you set `g:SortEditArgs = 1` the arguments for `:edit` like commands will\r\nbe reordered.  This allows to use `:edit file.txt +\/pattern` which will be\r\nreordered into `:edit +\/pattern file.txt`.\r\n\r\nIf you use `incsearch` setting, you probably want to use `g:VeryMagic = 0` and\r\nset two mappings:\r\n```viml\r\nnm \/ \/\\v\r\nnm ? ?\\v\r\n```\r\notherwise `incsearch` will not work for patterns which contains non\r\nalphanumeric characters.\r\n\r\n## How it works\r\nIt simply injects `\\v` at the beginning of your pattern *after you press enter*\r\nor after c_CTRL-f.\r\n\r\nNote: if you are using one of the two other of my plugins which are defining\r\nmaps to <CR> in the command line, you need to update them to the latest\r\nversion so that they will all work:\r\n* [System](https:\/\/github.com\/coot\/System)\r\n* [CommandAlias](https:\/\/github.com\/coot\/cmdalias_vim)\r\n\r\n# Requirements\r\nYou have to also install\r\n[CRDispatcher](https:\/\/www.github\/coot\/CRDispatcher) plugin.\r\n","install_details":"First install http:\/\/www.vim.org\/scripts\/script.php?script_id=4856 and then drop the file in .vim\/plugins\/ or _vim\/plugins directory.","5":"First install http:\/\/www.vim.org\/scripts\/script.php?script_id=4856 and then drop the file in .vim\/plugins\/ or _vim\/plugins directory.","first_name":"Marcin","6":"Marcin","last_name":"Szamotulski","7":"Szamotulski","releases":[{"0":"4849","vim_version":"7.3","1":"7.3","script_version":"4","2":"4","version_comment":"New version, which includes new options and deals with some corner cases.  Don't forget to update also http:\/\/www.vim.org\/scripts\/script.php?script_id=4856 .","3":"New version, which includes new options and deals with some corner cases.  Don't forget to update also http:\/\/www.vim.org\/scripts\/script.php?script_id=4856 .","package":"enchanted.vim","4":"enchanted.vim","src_id":"21551","5":"21551","creation_date":"1393664839","6":"1393664839"},{"0":"4849","vim_version":"7.3","1":"7.3","script_version":"3","2":"3","version_comment":"New versions with a few fixes.","3":"New versions with a few fixes.","package":"enchanted.vim","4":"enchanted.vim","src_id":"21444","5":"21444","creation_date":"1391847605","6":"1391847605"},{"0":"4849","vim_version":"7.3","1":"7.3","script_version":"2","2":"2","version_comment":"New version.  Also install: http:\/\/www.vim.org\/scripts\/script.php?script_id=4856 .","3":"New version.  Also install: http:\/\/www.vim.org\/scripts\/script.php?script_id=4856 .","package":"enchanted.vim","4":"enchanted.vim","src_id":"21440","5":"21440","creation_date":"1391766585","6":"1391766585"},{"0":"4849","vim_version":"7.3","1":"7.3","script_version":"1","2":"1","version_comment":"Initial upload","3":"Initial upload","package":"enchanted.vim","4":"enchanted.vim","src_id":"21416","5":"21416","creation_date":"1391347152","6":"1391347152"}]},"4848":{"script_id":"4848","0":"4848","script_name":"blockit","1":"blockit","script_type":"utility","2":"utility","summary":"a vim plugin to wrap lines in a block","3":"a vim plugin to wrap lines in a block","description":"=====================================================\r\nProject hosted at Github: https:\/\/github.com\/sk1418\/blockit\r\nscreenshot and demo animation can be found at the link above.\r\n=====================================================\r\n\r\nIntroduction\r\n\r\nWhen we are coding or editing text in vim, sometimes we want to wrap some lines of text (or in visual selections) in a block, which built by ascii chars. blockit is the vim plugin, to make this work easily to be done. One can \"draw\" block in different style. Please read next section for detailed features.\r\n\r\nFeatures\r\n\r\n - horizontal\/vertical char of the block border could be defined separately\r\n - margin between text and block border can be customized\r\n - block width can be dynamic (auto fit text width) or fixed\r\n - supports 4 in-block text alignment (No align., left-align., right align. center align.)\r\n - supports line-wise and block-wise visual selection text blocking (via key-mapping)\r\n - provide command to block line range\r\n\r\nConfiguration\r\n\r\nThere are 5 variables could be customized to configurate block style: (more detailed information please check the plugin doc.)\r\n\r\nvarialbe\tvalues\tdefault\r\ng:blockit_H_char\tstring: horizontal border char(s)\t'-'\r\ng:blockit_V_char\tstring: vertical border char(s)\t'|'\r\ng:blockit_margin\tint: margin between text and border\t1\r\n*g:blockit_fixed_length\tint: if you want the block has fixed width, value >=5\t0\r\ng:blockit_align\tstring: one of 'c','l','r','n'\t'n' (no alignment)\r\n* for the fixed length, please read the plugin docs for details.\r\n\r\nUsage\r\n\r\nIt is easy to use the blockit plugin. There are two commands and one mapping ready to use.  \r\n\r\n[range]:Block: This command will block the line range, with the settings in \"Configuration\" section.\r\n\r\n:BlockitVersion will print the current version info of installed blockit\r\n\r\n\r\n\r\nMapping\r\n\r\nMapping is only available in line-wise or block-wise visual selection mode.\r\n\r\nDefault:\r\n\r\n<leader>bi\r\n\r\nThis mapping will block the visual selected text.\r\n\r\nYou can of course customize the mapping in this way:\r\n\r\nvmap (Your_Mapping) <Plug>BlockitVisual","4":"=====================================================\r\nProject hosted at Github: https:\/\/github.com\/sk1418\/blockit\r\nscreenshot and demo animation can be found at the link above.\r\n=====================================================\r\n\r\nIntroduction\r\n\r\nWhen we are coding or editing text in vim, sometimes we want to wrap some lines of text (or in visual selections) in a block, which built by ascii chars. blockit is the vim plugin, to make this work easily to be done. One can \"draw\" block in different style. Please read next section for detailed features.\r\n\r\nFeatures\r\n\r\n - horizontal\/vertical char of the block border could be defined separately\r\n - margin between text and block border can be customized\r\n - block width can be dynamic (auto fit text width) or fixed\r\n - supports 4 in-block text alignment (No align., left-align., right align. center align.)\r\n - supports line-wise and block-wise visual selection text blocking (via key-mapping)\r\n - provide command to block line range\r\n\r\nConfiguration\r\n\r\nThere are 5 variables could be customized to configurate block style: (more detailed information please check the plugin doc.)\r\n\r\nvarialbe\tvalues\tdefault\r\ng:blockit_H_char\tstring: horizontal border char(s)\t'-'\r\ng:blockit_V_char\tstring: vertical border char(s)\t'|'\r\ng:blockit_margin\tint: margin between text and border\t1\r\n*g:blockit_fixed_length\tint: if you want the block has fixed width, value >=5\t0\r\ng:blockit_align\tstring: one of 'c','l','r','n'\t'n' (no alignment)\r\n* for the fixed length, please read the plugin docs for details.\r\n\r\nUsage\r\n\r\nIt is easy to use the blockit plugin. There are two commands and one mapping ready to use.  \r\n\r\n[range]:Block: This command will block the line range, with the settings in \"Configuration\" section.\r\n\r\n:BlockitVersion will print the current version info of installed blockit\r\n\r\n\r\n\r\nMapping\r\n\r\nMapping is only available in line-wise or block-wise visual selection mode.\r\n\r\nDefault:\r\n\r\n<leader>bi\r\n\r\nThis mapping will block the visual selected text.\r\n\r\nYou can of course customize the mapping in this way:\r\n\r\nvmap (Your_Mapping) <Plug>BlockitVisual","install_details":"extract the archive into ~\/.vim\r\nor use plugin management like Vundle: add\r\nBundle 'sk1418\/blockit'","5":"extract the archive into ~\/.vim\r\nor use plugin management like Vundle: add\r\nBundle 'sk1418\/blockit'","first_name":"Kent","6":"Kent","last_name":"Yuan","7":"Yuan","releases":[{"0":"4848","vim_version":"7.3","1":"7.3","script_version":"1.0.0","2":"1.0.0","version_comment":"Initial upload","3":"Initial upload","package":"blockit.tar.gz","4":"blockit.tar.gz","src_id":"21407","5":"21407","creation_date":"1391093515","6":"1391093515"}]},"4847":{"script_id":"4847","0":"4847","script_name":"phpspec.vim","1":"phpspec.vim","script_type":"utility","2":"utility","summary":"phpspec compiler","3":"phpspec compiler","description":"Just a PhpSpec compiler for VIM\r\n\r\nUsage\r\n--------\r\n\r\n```\r\n:compiler phpspec\r\n:make\r\n```\r\n\r\nIf you want a deeper integration with PhpSpec, like shortcuts, take a look at Herzult's plugin (https:\/\/github.com\/Herzult\/phpspec-vim). Feel free to use them together :).","4":"Just a PhpSpec compiler for VIM\r\n\r\nUsage\r\n--------\r\n\r\n```\r\n:compiler phpspec\r\n:make\r\n```\r\n\r\nIf you want a deeper integration with PhpSpec, like shortcuts, take a look at Herzult's plugin (https:\/\/github.com\/Herzult\/phpspec-vim). Feel free to use them together :).","install_details":"As usual, you can install it with your prefered VIM plugin manager (like Pathogen, Vundle or NeoBundle). If you want to install it by yourself, just copy the compiler folder to your ~\/.vim folder.","5":"As usual, you can install it with your prefered VIM plugin manager (like Pathogen, Vundle or NeoBundle). If you want to install it by yourself, just copy the compiler folder to your ~\/.vim folder.","first_name":"Renan","6":"Renan","last_name":"Martins","7":"Martins","releases":[{"0":"4847","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"phpspec.vim-1.0.0.tar.gz","4":"phpspec.vim-1.0.0.tar.gz","src_id":"21397","5":"21397","creation_date":"1390997210","6":"1390997210"}]},"4846":{"script_id":"4846","0":"4846","script_name":"TWMC: Tab\/Win Move Commands","1":"TWMC: Tab\/Win Move Commands","script_type":"utility","2":"utility","summary":"Tab\/Win Move Commands for vim.","3":"Tab\/Win Move Commands for vim.","description":"This plugin is deprecated.\r\nIt is merged to TWCommand plugin (http:\/\/www.vim.org\/scripts\/script.php?script_id=4876), and not will be updated any more.\r\nPlease use TWCommand instead of this plugin.\r\n\r\n-----------------------------------------------------------------------------------------\r\nFor more information, please see https:\/\/github.com\/yssl\/TWMC.\r\n\r\n# TWMC: Tab\/Win Move Commands\r\n\r\nTWMC is a set of useful commands for moving a tab, window or a cursor between vim's tabs \/ windows.\r\nIt provides additional useful commands such as maxmizing a window.  \r\n\r\nTWMC is composed of three commands:\r\n- Winmove : Move the current window between windows.\r\n- Tabcmd : `:wincmd`-style tab management command including moving commands for a cursor between tabs.\r\n- WincmdEx : Extension of the original `:wincmd`.\r\n\r\nEach command has several sub-commands called by `:wincmd`-style single character arguments.\r\n\r\n## Winmove\r\n\r\nIn vim normal mode, you can just type `:Winmove {arg}` (similar to `:wincmd {arg}`).  \r\nList of available `{arg}` is:\r\n\r\n{arg} | Winmove\r\n---   | ---\r\nh     | Move current window to left.\r\nl     | Move current window to right.\r\nj     | Move current window to down.\r\nk     | Move current window to up.\r\np     | Move current window to location of previously focused window.\r\n\r\nand all other arguments used in `:wincmd` that move a cursor such as w, W, t, b.\r\n\r\n## Tabcmd\r\n\r\nIn normal mode, just type `:Tabcmd {arg}`.\r\n\r\n{arg} | Tabcmd\r\n---   | ---\r\nh     | Go to the left tab page.\r\nl     | Go to the right tab page.\r\nW     | Go to the left tab page. Wraps around from the first to the last one.\r\nw     | Go to the right tab page. Wraps around from the last to the first one.\r\nt     | Go to the first tab page.\r\nb     | Go to the last tab page.\r\np     | Go to the previous tab page.\r\nq     | Close current tab page and move focus to previously focused one.\r\nn     | Open a new tab page with an empty window, after the current tab page.\r\no     | Close all other tab pages.\r\n\r\n## WincmdEx\r\n\r\nThis command overrides the original `:wincmd` command.  \r\nIn normal mode, just type `:WincmdEx {arg}`.\r\n\r\n{arg} | WincmdEx\r\n---   | ---\r\nq     | Quit current window and move cursor to previously focused one.\r\nm     | Toggle maximizing current window.\r\n\r\nand all other arguments used in `:wincmd`.\r\n","4":"This plugin is deprecated.\r\nIt is merged to TWCommand plugin (http:\/\/www.vim.org\/scripts\/script.php?script_id=4876), and not will be updated any more.\r\nPlease use TWCommand instead of this plugin.\r\n\r\n-----------------------------------------------------------------------------------------\r\nFor more information, please see https:\/\/github.com\/yssl\/TWMC.\r\n\r\n# TWMC: Tab\/Win Move Commands\r\n\r\nTWMC is a set of useful commands for moving a tab, window or a cursor between vim's tabs \/ windows.\r\nIt provides additional useful commands such as maxmizing a window.  \r\n\r\nTWMC is composed of three commands:\r\n- Winmove : Move the current window between windows.\r\n- Tabcmd : `:wincmd`-style tab management command including moving commands for a cursor between tabs.\r\n- WincmdEx : Extension of the original `:wincmd`.\r\n\r\nEach command has several sub-commands called by `:wincmd`-style single character arguments.\r\n\r\n## Winmove\r\n\r\nIn vim normal mode, you can just type `:Winmove {arg}` (similar to `:wincmd {arg}`).  \r\nList of available `{arg}` is:\r\n\r\n{arg} | Winmove\r\n---   | ---\r\nh     | Move current window to left.\r\nl     | Move current window to right.\r\nj     | Move current window to down.\r\nk     | Move current window to up.\r\np     | Move current window to location of previously focused window.\r\n\r\nand all other arguments used in `:wincmd` that move a cursor such as w, W, t, b.\r\n\r\n## Tabcmd\r\n\r\nIn normal mode, just type `:Tabcmd {arg}`.\r\n\r\n{arg} | Tabcmd\r\n---   | ---\r\nh     | Go to the left tab page.\r\nl     | Go to the right tab page.\r\nW     | Go to the left tab page. Wraps around from the first to the last one.\r\nw     | Go to the right tab page. Wraps around from the last to the first one.\r\nt     | Go to the first tab page.\r\nb     | Go to the last tab page.\r\np     | Go to the previous tab page.\r\nq     | Close current tab page and move focus to previously focused one.\r\nn     | Open a new tab page with an empty window, after the current tab page.\r\no     | Close all other tab pages.\r\n\r\n## WincmdEx\r\n\r\nThis command overrides the original `:wincmd` command.  \r\nIn normal mode, just type `:WincmdEx {arg}`.\r\n\r\n{arg} | WincmdEx\r\n---   | ---\r\nq     | Quit current window and move cursor to previously focused one.\r\nm     | Toggle maximizing current window.\r\n\r\nand all other arguments used in `:wincmd`.\r\n","install_details":"","5":"","first_name":"Yoonsang","6":"Yoonsang","last_name":"Lee","7":"Lee","releases":[{"0":"4846","vim_version":"7.0","1":"7.0","script_version":"2.0.0","2":"2.0.0","version_comment":"add Winmove Command","3":"add Winmove Command","package":"TWMC.zip","4":"TWMC.zip","src_id":"21412","5":"21412","creation_date":"1391243236","6":"1391243236"},{"0":"4846","vim_version":"7.0","1":"7.0","script_version":"1.1.0","2":"1.1.0","version_comment":"- rename the plugin to 'TWMC'.\r\n- add 'toggle maximizing window' command.","3":"- rename the plugin to 'TWMC'.\r\n- add 'toggle maximizing window' command.","package":"TWMC.zip","4":"TWMC.zip","src_id":"21411","5":"21411","creation_date":"1391239126","6":"1391239126"},{"0":"4846","vim_version":"7.0","1":"7.0","script_version":"1.0.0","2":"1.0.0","version_comment":"Initial upload","3":"Initial upload","package":"Tabcmd.zip","4":"Tabcmd.zip","src_id":"21395","5":"21395","creation_date":"1390957153","6":"1390957153"}]},"4845":{"script_id":"4845","0":"4845","script_name":"Html Template","1":"Html Template","script_type":"ftplugin","2":"ftplugin","summary":"This plugin paste a base frame in your new html- or php-file.","3":"This plugin paste a base frame in your new html- or php-file.","description":"This plugin enables you to work faster.\r\nIt paste a base frame if you edit a new file with the ending .php, .html or .htm. \r\nAn African proverb:\r\n\"If many little people do in many small places a lot of small things, they can change the face of the world.\"\r\n\r\nTry out:\r\n1. Start vim.\r\n2. Run :e test.html\r\n\r\nIf you have the right settings, the code have been added.","4":"This plugin enables you to work faster.\r\nIt paste a base frame if you edit a new file with the ending .php, .html or .htm. \r\nAn African proverb:\r\n\"If many little people do in many small places a lot of small things, they can change the face of the world.\"\r\n\r\nTry out:\r\n1. Start vim.\r\n2. Run :e test.html\r\n\r\nIf you have the right settings, the code have been added.","install_details":"1. Download the plugin in your \/ftplugin - Directory.\r\n2. Paste this code in your vimrc:\r\n\"htmlheader plugin\r\nautocmd BufNewFile *.html,*.htm,*.php source ~\/.vim\/ftplugin\/htmltemplate.vim\r\n3. Maybe you must change the directory in the vimrc.","5":"1. Download the plugin in your \/ftplugin - Directory.\r\n2. Paste this code in your vimrc:\r\n\"htmlheader plugin\r\nautocmd BufNewFile *.html,*.htm,*.php source ~\/.vim\/ftplugin\/htmltemplate.vim\r\n3. Maybe you must change the directory in the vimrc.","first_name":"Linus","6":"Linus","last_name":"Clau\u00c3\u009fnitzer","7":"Clau\u00c3\u009fnitzer","releases":[{"0":"4845","vim_version":"7.0","1":"7.0","script_version":"1.1","2":"1.1","version_comment":"Added indent ","3":"Added indent ","package":"htmltemplate.vim","4":"htmltemplate.vim","src_id":"23022","5":"23022","creation_date":"1426324869","6":"1426324869"},{"0":"4845","vim_version":"7.3","1":"7.3","script_version":"1","2":"1","version_comment":"Initial upload","3":"Initial upload","package":"htmltemplate.vim","4":"htmltemplate.vim","src_id":"21378","5":"21378","creation_date":"1390730441","6":"1390730441"}]},"4844":{"script_id":"4844","0":"4844","script_name":" poshcomplete-vim","1":" poshcomplete-vim","script_type":"ftplugin","2":"ftplugin","summary":"Omni Completion for PowerShell","3":"Omni Completion for PowerShell","description":"This is omnifunc for PowerShell.\r\n\r\nUsage:\r\n    1. call poshcomplete#StartServer()\r\n    2. foobar<C-X><C-O>\r\n\r\n\r\nLATEST VERSION\r\n    https:\/\/github.com\/cd01\/poshcomplete-vim","4":"This is omnifunc for PowerShell.\r\n\r\nUsage:\r\n    1. call poshcomplete#StartServer()\r\n    2. foobar<C-X><C-O>\r\n\r\n\r\nLATEST VERSION\r\n    https:\/\/github.com\/cd01\/poshcomplete-vim","install_details":"1. netsh http add urlacl url=http:\/\/+:1234\/ user=Everyone\r\n2. Download poshcomplete-vim-xx.xx.zip from this page\r\n3. Extract poshcomplete-vim.zip to ~\\vimfiles\\bundle\\poshcomplete-vim\r\n4. Run ~\\vimfiles\\bundle\\poshcomplete-vim\\server\\PoshComplete\\bin\\Release\\PoshComplete.exe and Turn off Security Warning\r\n5. Add ~\\vimfiles\\bundle\\poshcomplete-vim to runtimepath\r\n\r\nRequirement:\r\n  * webapi-vim https:\/\/github.com\/mattn\/webapi-vim\r\n  * vimproc https:\/\/github.com\/Shougo\/vimproc \r\n\r\n","5":"1. netsh http add urlacl url=http:\/\/+:1234\/ user=Everyone\r\n2. Download poshcomplete-vim-xx.xx.zip from this page\r\n3. Extract poshcomplete-vim.zip to ~\\vimfiles\\bundle\\poshcomplete-vim\r\n4. Run ~\\vimfiles\\bundle\\poshcomplete-vim\\server\\PoshComplete\\bin\\Release\\PoshComplete.exe and Turn off Security Warning\r\n5. Add ~\\vimfiles\\bundle\\poshcomplete-vim to runtimepath\r\n\r\nRequirement:\r\n  * webapi-vim https:\/\/github.com\/mattn\/webapi-vim\r\n  * vimproc https:\/\/github.com\/Shougo\/vimproc \r\n\r\n","first_name":"cd01","6":"cd01","last_name":" ","7":" ","releases":[{"0":"4844","vim_version":"7.3","1":"7.3","script_version":"0.1.1","2":"0.1.1","version_comment":"Fix a bug","3":"Fix a bug","package":"poshcomplete-vim-0.1.1.zip","4":"poshcomplete-vim-0.1.1.zip","src_id":"22345","5":"22345","creation_date":"1408357756","6":"1408357756"},{"0":"4844","vim_version":"7.3","1":"7.3","script_version":"0.1.0","2":"0.1.0","version_comment":"New completion method","3":"New completion method","package":"poshcomplete-vim-0.1.0.zip","4":"poshcomplete-vim-0.1.0.zip","src_id":"22328","5":"22328","creation_date":"1408075574","6":"1408075574"}]},"4843":{"script_id":"4843","0":"4843","script_name":"CopySel","1":"CopySel","script_type":"utility","2":"utility","summary":"Extract arbitrary selections to workfile ","3":"Extract arbitrary selections to workfile ","description":"The idea for wirting this script came up as I have to maintain an old but very huge and undocumented program in which some messages was produced depending on its number by simple do a 'CALL FEHLER(nnn);' where nnn was a number.\r\n\r\nUnfortunately this calls weren't in order and coded somewhere between approx 12000 lines of code, and it was necessary to have the numbers unique of course but some weren't, and there were approx 400 numbers used.\r\n\r\nSo I thaught about how I could get just the numbers and nothing else to examine them, and this made the script CopySel, which does I needed.\r\n\r\nThere are 2 versions I supply:\r\nThe comfortable version uses my VDLGBX.DLL (vimscript #755).\r\nThe 'nude' version simple uses your last search and is stuck to th q-register.\r\n\r\nHow to use:\r\n1) do a locate using the pattern you want to extract (if necessary use \\zs and \\ze to limit the selection to an interesting part of your pattern)\r\n2) :call CopySel(1) [using VDLGBX] or CopySel(0)\r\n3) press @q f\u00c3\u00bcr copying, n for jumping to next selection \r\n\r\n","4":"The idea for wirting this script came up as I have to maintain an old but very huge and undocumented program in which some messages was produced depending on its number by simple do a 'CALL FEHLER(nnn);' where nnn was a number.\r\n\r\nUnfortunately this calls weren't in order and coded somewhere between approx 12000 lines of code, and it was necessary to have the numbers unique of course but some weren't, and there were approx 400 numbers used.\r\n\r\nSo I thaught about how I could get just the numbers and nothing else to examine them, and this made the script CopySel, which does I needed.\r\n\r\nThere are 2 versions I supply:\r\nThe comfortable version uses my VDLGBX.DLL (vimscript #755).\r\nThe 'nude' version simple uses your last search and is stuck to th q-register.\r\n\r\nHow to use:\r\n1) do a locate using the pattern you want to extract (if necessary use \\zs and \\ze to limit the selection to an interesting part of your pattern)\r\n2) :call CopySel(1) [using VDLGBX] or CopySel(0)\r\n3) press @q f\u00c3\u00bcr copying, n for jumping to next selection \r\n\r\n","install_details":"Simple copy the version you want in your plugin-folder.\r\n","5":"Simple copy the version you want in your plugin-folder.\r\n","first_name":"Michael","6":"Michael","last_name":"Fitz","7":"Fitz","releases":[{"0":"4843","vim_version":"6.0","1":"6.0","script_version":"1.2","2":"1.2","version_comment":"Missing assignment when using without VDLGBX\r\nSome minor improvements and bugfixes","3":"Missing assignment when using without VDLGBX\r\nSome minor improvements and bugfixes","package":"CopySel.VIM","4":"CopySel.VIM","src_id":"21537","5":"21537","creation_date":"1393429810","6":"1393429810"},{"0":"4843","vim_version":"6.0","1":"6.0","script_version":"1.1","2":"1.1","version_comment":"Only one version with\/without VDLGBX (see script for details)\r\nSome minor improvements and bugs fixed","3":"Only one version with\/without VDLGBX (see script for details)\r\nSome minor improvements and bugs fixed","package":"CopySel.VIM","4":"CopySel.VIM","src_id":"21398","5":"21398","creation_date":"1391018255","6":"1391018255"},{"0":"4843","vim_version":"6.0","1":"6.0","script_version":"1.001","2":"1.001","version_comment":"Some error I've detected just now","3":"Some error I've detected just now","package":"CopySel.zip","4":"CopySel.zip","src_id":"21375","5":"21375","creation_date":"1390655853","6":"1390655853"}]},"4842":{"script_id":"4842","0":"4842","script_name":"InsertFromAround","1":"InsertFromAround","script_type":"utility","2":"utility","summary":"Insert mode mappings to fetch text or indent from surrounding lines.","3":"Insert mode mappings to fetch text or indent from surrounding lines.","description":"DESCRIPTION\r\nWith the proper indent settings, Vim will mostly supply the correct amount of\r\nindent when creating new lines. But sometimes, one needs a special amount of\r\nindent, and it is cumbersome to manually create that by repeatedly pressing\r\n<Tab>, <Space>, and <BS>.\r\n\r\nThis plugin defines insert mode mappings that indent a new line exactly at the\r\ncurrent cursor position, or insert the indent used in adjacent lines, or align\r\nthe text to the right of the cursor to text fragments in surrounding lines.\r\n\r\nTo duplicate the text of adjacent lines, Vim has the i_CTRL-E \/ i_CTRL-Y\r\ncommands. But these only work character for character (which makes it slow to\r\ncopy longer fragments), and fail when empty \/ shorter lines surround the\r\ncurrent line.\r\n\r\nThis plugin supercharges these commands, making them look beyond the immediate\r\nlines. With a separate mapping, the scope of completion can be toggled between\r\nsingle characters and whole words, speeding up larger text grabs while still\r\nallowing the fine-grained completion.\r\n\r\nSOURCE\r\n- The i_CTRL-E \/ i_CTRL-Y mappings are based on\r\n    http:\/\/www.ibm.com\/developerworks\/linux\/library\/l-vim-script-1\/index.html\r\n\r\nRELATED WORKS\r\n- The prev_indent plugin (vimscript #4575) provides an insert mode mapping and\r\n  :PrevIndent to move the current line to the previous indentation level.\r\n\r\nUSAGE\r\nCTRL-Enter              Insert newline and indent the new line to the current\r\n                        cursor column. This takes into account indent-\r\n                        expressions and insertion of the comment leader.\r\n\r\nCTRL-E \/ CTRL-Y         Insert the character from unfolded lines below \/ above\r\n                        the cursor; if the adjacent line is not that long,\r\n                        mook beyond. The command beeps and suspends insert\r\n                        once if the current target line has been exhausted.\r\n\r\nCTRL-G CTRL-E \/ CTRL-G CTRL-Y\r\n                        Insert an entire word from unfolded lines below \/\r\n                        above the cursor and toggle the behavior of i_CTRL-E\r\n                        \/ i_CTRL-Y to continue inserting words. The behavior\r\n                        reverts itself when inserting in another line or by\r\n                        using this mapping a second time.\r\n\r\nCTRL-G CTRL-U           Replace the text before the cursor with the indent\r\n                        from the next nearby unfolded line that has at least\r\n                        as much indent as the current cursor position. If the\r\n                        indent before and after the current line differs, the\r\n                        smaller amount is inserted; repeat the mapping to get\r\n                        the larger amount.\r\n                        (Mnemonic: Undo the effect of i_CTRL-U.)\r\n\r\nCTRL-G CTRL-B           Remove whitespace before the cursor so that the\r\n                        current cursor position aligns with the start of\r\n                        preceding non-whitespace text in the previous unfolded\r\n                        line.\r\n\r\nCTRL-G CTRL-A           Insert whitespace so that the text after the cursor\r\n                        aligns with the start of following non-whitespace text\r\n                        (and the end of the text) in the previous unfolded\r\n                        line.\r\n\r\nCTRL-G CTRL-V           Insert whitespace so that the text after the cursor\r\n                        aligns with the closest match of the (non-whitespace)\r\n                        character after the cursor found after the cursor\r\n                        column in adjacent unfolded lines.\r\n\r\nCTRL-G V{char}          Insert whitespace so that the text after the cursor\r\n                        aligns the next match of {char} in the current line\r\n                        with the closest match of {char} found after that\r\n                        column in adjacent unfolded lines.\r\n                        Note: This won't work correctly when there are <Tab>\r\n                        characters between the cursor and the next match of\r\n                        {char}.\r\n\r\nEXAMPLE\r\nInsert newline and indent to cursor column:\r\nfoo|ar\r\n    v CTRL-Enter\r\nfoo\r\n    bar\r\n\r\nInsert the character, character, then word, word from above:\r\nA very long example provides context.\r\nShort one.\r\n    I'm here|\r\n            v CTRL-Y\r\n    I'm heree|\r\n            v CTRL-Y\r\n    I'm hereex|\r\n            v CTRL-G CTRL-Y\r\n    I'm hereexample|\r\n            v CTRL-Y\r\n    I'm hereexample provides|\r\n\r\nInsert the additional indent from next nearby lines:\r\n    FOO            BAR        BAZ\r\n           HI\r\n|ere\r\nv CTRL-G CTRL-U\r\n    |ere\r\n    v CTRL-G CTRL-U\r\n           |ere\r\n\r\nAlign with the start of preceding text fragments:\r\n    FOO            BAR        BAZ\r\n|ere\r\nv CTRL-G CTRL-A\r\n    |ere\r\n    v CTRL-G CTRL-A\r\n                   |ere\r\n                   v CTRL-G CTRL-A\r\n                              |ere\r\n                              v CTRL-G CTRL-B\r\n                   |ere\r\n\r\nAlign \"Nothing\" with the closest match of the character \"N\" found nearby:\r\n    NOO            BAR        NAZ\r\n           NI\r\n|othing\r\nv CTRL-G CTRL-U\r\n    |othing\r\n    v CTRL-G CTRL-U\r\n           |othing\r\n           v CTRL-G CTRL-U\r\n                              |othing\r\n\r\nAlign on = with the closest match found nearby:\r\n    class=\"bar\" alt=\"ni\"\r\n|ummary=\"foo\"\r\nv CTRL-G V =\r\n  |ummary=\"foo\"\r\n    v CTRL-G CTRL-U\r\n            |ummary=\"foo\"","4":"DESCRIPTION\r\nWith the proper indent settings, Vim will mostly supply the correct amount of\r\nindent when creating new lines. But sometimes, one needs a special amount of\r\nindent, and it is cumbersome to manually create that by repeatedly pressing\r\n<Tab>, <Space>, and <BS>.\r\n\r\nThis plugin defines insert mode mappings that indent a new line exactly at the\r\ncurrent cursor position, or insert the indent used in adjacent lines, or align\r\nthe text to the right of the cursor to text fragments in surrounding lines.\r\n\r\nTo duplicate the text of adjacent lines, Vim has the i_CTRL-E \/ i_CTRL-Y\r\ncommands. But these only work character for character (which makes it slow to\r\ncopy longer fragments), and fail when empty \/ shorter lines surround the\r\ncurrent line.\r\n\r\nThis plugin supercharges these commands, making them look beyond the immediate\r\nlines. With a separate mapping, the scope of completion can be toggled between\r\nsingle characters and whole words, speeding up larger text grabs while still\r\nallowing the fine-grained completion.\r\n\r\nSOURCE\r\n- The i_CTRL-E \/ i_CTRL-Y mappings are based on\r\n    http:\/\/www.ibm.com\/developerworks\/linux\/library\/l-vim-script-1\/index.html\r\n\r\nRELATED WORKS\r\n- The prev_indent plugin (vimscript #4575) provides an insert mode mapping and\r\n  :PrevIndent to move the current line to the previous indentation level.\r\n\r\nUSAGE\r\nCTRL-Enter              Insert newline and indent the new line to the current\r\n                        cursor column. This takes into account indent-\r\n                        expressions and insertion of the comment leader.\r\n\r\nCTRL-E \/ CTRL-Y         Insert the character from unfolded lines below \/ above\r\n                        the cursor; if the adjacent line is not that long,\r\n                        mook beyond. The command beeps and suspends insert\r\n                        once if the current target line has been exhausted.\r\n\r\nCTRL-G CTRL-E \/ CTRL-G CTRL-Y\r\n                        Insert an entire word from unfolded lines below \/\r\n                        above the cursor and toggle the behavior of i_CTRL-E\r\n                        \/ i_CTRL-Y to continue inserting words. The behavior\r\n                        reverts itself when inserting in another line or by\r\n                        using this mapping a second time.\r\n\r\nCTRL-G CTRL-U           Replace the text before the cursor with the indent\r\n                        from the next nearby unfolded line that has at least\r\n                        as much indent as the current cursor position. If the\r\n                        indent before and after the current line differs, the\r\n                        smaller amount is inserted; repeat the mapping to get\r\n                        the larger amount.\r\n                        (Mnemonic: Undo the effect of i_CTRL-U.)\r\n\r\nCTRL-G CTRL-B           Remove whitespace before the cursor so that the\r\n                        current cursor position aligns with the start of\r\n                        preceding non-whitespace text in the previous unfolded\r\n                        line.\r\n\r\nCTRL-G CTRL-A           Insert whitespace so that the text after the cursor\r\n                        aligns with the start of following non-whitespace text\r\n                        (and the end of the text) in the previous unfolded\r\n                        line.\r\n\r\nCTRL-G CTRL-V           Insert whitespace so that the text after the cursor\r\n                        aligns with the closest match of the (non-whitespace)\r\n                        character after the cursor found after the cursor\r\n                        column in adjacent unfolded lines.\r\n\r\nCTRL-G V{char}          Insert whitespace so that the text after the cursor\r\n                        aligns the next match of {char} in the current line\r\n                        with the closest match of {char} found after that\r\n                        column in adjacent unfolded lines.\r\n                        Note: This won't work correctly when there are <Tab>\r\n                        characters between the cursor and the next match of\r\n                        {char}.\r\n\r\nEXAMPLE\r\nInsert newline and indent to cursor column:\r\nfoo|ar\r\n    v CTRL-Enter\r\nfoo\r\n    bar\r\n\r\nInsert the character, character, then word, word from above:\r\nA very long example provides context.\r\nShort one.\r\n    I'm here|\r\n            v CTRL-Y\r\n    I'm heree|\r\n            v CTRL-Y\r\n    I'm hereex|\r\n            v CTRL-G CTRL-Y\r\n    I'm hereexample|\r\n            v CTRL-Y\r\n    I'm hereexample provides|\r\n\r\nInsert the additional indent from next nearby lines:\r\n    FOO            BAR        BAZ\r\n           HI\r\n|ere\r\nv CTRL-G CTRL-U\r\n    |ere\r\n    v CTRL-G CTRL-U\r\n           |ere\r\n\r\nAlign with the start of preceding text fragments:\r\n    FOO            BAR        BAZ\r\n|ere\r\nv CTRL-G CTRL-A\r\n    |ere\r\n    v CTRL-G CTRL-A\r\n                   |ere\r\n                   v CTRL-G CTRL-A\r\n                              |ere\r\n                              v CTRL-G CTRL-B\r\n                   |ere\r\n\r\nAlign \"Nothing\" with the closest match of the character \"N\" found nearby:\r\n    NOO            BAR        NAZ\r\n           NI\r\n|othing\r\nv CTRL-G CTRL-U\r\n    |othing\r\n    v CTRL-G CTRL-U\r\n           |othing\r\n           v CTRL-G CTRL-U\r\n                              |othing\r\n\r\nAlign on = with the closest match found nearby:\r\n    class=\"bar\" alt=\"ni\"\r\n|ummary=\"foo\"\r\nv CTRL-G V =\r\n  |ummary=\"foo\"\r\n    v CTRL-G CTRL-U\r\n            |ummary=\"foo\"","install_details":"INSTALLATION\r\nThe code is hosted in a Git repo at\r\n    https:\/\/github.com\/inkarkat\/vim-InsertFromAround\r\nYou can use your favorite plugin manager, or \"git clone\" into a directory used\r\nfor Vim packages. Releases are on the \"stable\" branch, the latest unstable\r\ndevelopment snapshot on \"master\".\r\n\r\nThis script is also packaged as a vimball. If you have the \"gunzip\"\r\ndecompressor in your PATH, simply edit the *.vmb.gz package in Vim; otherwise,\r\ndecompress the archive first, e.g. using WinZip. Inside Vim, install by\r\nsourcing the vimball or via the :UseVimball command.\r\n    vim InsertFromAround*.vmb.gz\r\n    :so %\r\nTo uninstall, use the :RmVimball command.\r\n\r\nDEPENDENCIES\r\n- Requires Vim 7.0 or higher.\r\n- Requires the ingo-library.vim plugin (vimscript #4433), version 1.030 or\r\n  higher.\r\n\r\nCONFIGURATION\r\nFor a permanent configuration, put the following commands into your vimrc:\r\n\r\nIf you want to use different mappings, map your keys to the\r\n<Plug>(InsertFrom...) mapping targets _before_ sourcing the script\r\n(e.g. in your vimrc):\r\n    imap <C-CR> <Plug>(InsertFromEnterAndIndent)\r\n    imap <C-e> <Plug>(InsertFromTextBelow)\r\n    imap <C-y> <Plug>(InsertFromTextAbove)\r\n    imap <C-g><C-e> <Plug>(InsertFromTextBelowToggle)\r\n    imap <C-g><C-y> <Plug>(InsertFromTextAboveToggle)\r\n    imap <C-g><C-u> <Plug>(InsertFromIndent)\r\n    imap <C-g><C-b> <Plug>(InsertFromAlignToPrevious)\r\n    imap <C-g><C-a> <Plug>(InsertFromAlignToNext)","5":"INSTALLATION\r\nThe code is hosted in a Git repo at\r\n    https:\/\/github.com\/inkarkat\/vim-InsertFromAround\r\nYou can use your favorite plugin manager, or \"git clone\" into a directory used\r\nfor Vim packages. Releases are on the \"stable\" branch, the latest unstable\r\ndevelopment snapshot on \"master\".\r\n\r\nThis script is also packaged as a vimball. If you have the \"gunzip\"\r\ndecompressor in your PATH, simply edit the *.vmb.gz package in Vim; otherwise,\r\ndecompress the archive first, e.g. using WinZip. Inside Vim, install by\r\nsourcing the vimball or via the :UseVimball command.\r\n    vim InsertFromAround*.vmb.gz\r\n    :so %\r\nTo uninstall, use the :RmVimball command.\r\n\r\nDEPENDENCIES\r\n- Requires Vim 7.0 or higher.\r\n- Requires the ingo-library.vim plugin (vimscript #4433), version 1.030 or\r\n  higher.\r\n\r\nCONFIGURATION\r\nFor a permanent configuration, put the following commands into your vimrc:\r\n\r\nIf you want to use different mappings, map your keys to the\r\n<Plug>(InsertFrom...) mapping targets _before_ sourcing the script\r\n(e.g. in your vimrc):\r\n    imap <C-CR> <Plug>(InsertFromEnterAndIndent)\r\n    imap <C-e> <Plug>(InsertFromTextBelow)\r\n    imap <C-y> <Plug>(InsertFromTextAbove)\r\n    imap <C-g><C-e> <Plug>(InsertFromTextBelowToggle)\r\n    imap <C-g><C-y> <Plug>(InsertFromTextAboveToggle)\r\n    imap <C-g><C-u> <Plug>(InsertFromIndent)\r\n    imap <C-g><C-b> <Plug>(InsertFromAlignToPrevious)\r\n    imap <C-g><C-a> <Plug>(InsertFromAlignToNext)","first_name":"Ingo","6":"Ingo","last_name":"Karkat","7":"Karkat","releases":[{"0":"4842","vim_version":"7.0","1":"7.0","script_version":"1.11","2":"1.11","version_comment":"- Make <C-CR> handle comment prefixes, not just indent.\r\n- CHG: Rename i_CTRL-G_CTRL-D \/ i_CTRL-G_CTRL-T default mappings to i_CTRL-G_CTRL-B (\"before\") \/ i_CTRL-G_CTRL-A (\"after\"). I need the original mappings to toggle i_CTRL-D \/ i_CTRL-T in my IndentCommentPrefix.vim plugin for toggling similar to i_CTRL-G_CTRL-E here. To restore the original mappings, put this into your .vimrc: >\r\n    imap <C-g><C-d> <Plug>(InsertFromAlignToPrevious)\r\n    imap <C-g><C-t> <Plug>(InsertFromAlignToNext)\r\n*** You need to update to ingo-library (vimscript #4433) version 1.030! ***","3":"- Make <C-CR> handle comment prefixes, not just indent.\r\n- CHG: Rename i_CTRL-G_CTRL-D \/ i_CTRL-G_CTRL-T default mappings to i_CTRL-G_CTRL-B (\"before\") \/ i_CTRL-G_CTRL-A (\"after\"). I need the original mappings to toggle i_CTRL-D \/ i_CTRL-T in my IndentCommentPrefix.vim plugin for toggling similar to i_CTRL-G_CTRL-E here. To restore the original mappings, put this into your .vimrc: >\r\n    imap <C-g><C-d> <Plug>(InsertFromAlignToPrevious)\r\n    imap <C-g><C-t> <Plug>(InsertFromAlignToNext)\r\n*** You need to update to ingo-library (vimscript #4433) version 1.030! ***","package":"InsertFromAround-1.11.vmb.gz","4":"InsertFromAround-1.11.vmb.gz","src_id":"26263","5":"26263","creation_date":"1541384102","6":"1541384102"},{"0":"4842","vim_version":"7.0","1":"7.0","script_version":"1.10","2":"1.10","version_comment":"- ENH: The i_CTRL-G_CTRL-D \/ i_CTRL-G_CTRL-T mappings also align to non-whitespace text in preceding lines when the line immediately above is shorter than the cursor column.\r\n- Add CTRL-G CTRL-V mapping that aligns to the current character found in adjacent lines.\r\n- Add CTRL-G V{char} mapping that aligns to the queried character.","3":"- ENH: The i_CTRL-G_CTRL-D \/ i_CTRL-G_CTRL-T mappings also align to non-whitespace text in preceding lines when the line immediately above is shorter than the cursor column.\r\n- Add CTRL-G CTRL-V mapping that aligns to the current character found in adjacent lines.\r\n- Add CTRL-G V{char} mapping that aligns to the queried character.","package":"InsertFromAround-1.10.vmb.gz","4":"InsertFromAround-1.10.vmb.gz","src_id":"21725","5":"21725","creation_date":"1396537569","6":"1396537569"},{"0":"4842","vim_version":"7.0","1":"7.0","script_version":"1.00","2":"1.00","version_comment":"Initial upload","3":"Initial upload","package":"InsertFromAround-1.00.vmb.gz","4":"InsertFromAround-1.00.vmb.gz","src_id":"21364","5":"21364","creation_date":"1390493659","6":"1390493659"}]},"4841":{"script_id":"4841","0":"4841","script_name":"JumpToVerticalOccurrence","1":"JumpToVerticalOccurrence","script_type":"utility","2":"utility","summary":"Like f{char}, but searching the same screen column, not line.","3":"Like f{char}, but searching the same screen column, not line.","description":"DESCRIPTION\r\nThe f \/ F commands allow you to quickly go to next \/ previous occurrences\r\nof a character in the same line (with plugins also across lines), but are\r\nlimited to horizontal movement. But vertical movement, restricted to the same\r\nscreen column the cursor is in, across lines would often be helpful, too.\r\n\r\nThis plugin provides a |]V|{char} mapping that works just like f, but\r\nvertically. The ]v mapping is similar, but uses the character under the\r\ncursor instead of querying for it (which is a more common use case when moving\r\nvertically).\r\nThe ]| mapping is helpful for jumping out of indented blocks, or to filled-out\r\ncolumns, as it moves to the next non-whitespace in the current column.\r\nIn long sorted lists, one often wants to go to the first \/ last instance of\r\nthe current character (e.g. to move from \"[A]ddress\" to \"Aardvark\" or the last\r\n\"Azure\" before the entries with \"B\" begin). The ]! mapping does that.\r\n\r\nSOURCE\r\nThe ]| mapping was inspired by\r\n    http:\/\/stackoverflow.com\/questions\/20882722\/move-to-the-next-row-which-has-non-white-space-character-in-the-same-column-in-v\r\n\r\nSEE ALSO\r\n- The JumpToLastOccurrence.vim plugin (vimscript #3386) still moves\r\n  horizontally in the same line, but counts the characters in reverse,\r\n  starting from the last one.\r\n- The JumpToVerticalBlock.vim plugin (vimscript #5657) has motions that\r\n  operate like W and E, but vertically.\r\n- Check out the CountJump.vim plugin page (vimscript #3130) for a full list\r\n  of motions and text objects powered by it.\r\n\r\nRELATED WORKS\r\n- columnmove (vimscript #4880) defines f\/t\/;\/, commands as well as w\/e\/b\/ge\r\n  commands that work vertically, either skipping or opening closed folds.\r\n- columnMove (vimscript #5402) moves to the end \/ start of vertical blocks of\r\n  non-whitespace.\r\n\r\nUSAGE\r\n]v                  To [count]'th occurrence of the character under the cursor\r\n                    in the same screen column of following lines.\r\n[v                  To [count]'th occurrence of the character under the cursor\r\n                    in the same screen column of previous lines.\r\n\r\n]V{char}            To [count]'th occurrence of {char} in the same screen\r\n                    column of following lines. Like f, but vertically.\r\n[V{char}            To [count]'th occurrence of {char} in the same screen\r\n                    column of previous lines. Like F, but vertically.\r\n                    You can quickly repeat the same motion via the ]v \/ [v\r\n                    mappings (like ; \/ , for f).\r\n\r\n]|                  To [count]'th next line that has non-whitespace in the\r\n                    same column as the current one.\r\n[|                  To [count]'th previous line that has non-whitespace in the\r\n                    same column as the current one.\r\n\r\n]!                  To the last continuous occurrence of the character under\r\n                    the cursor in the same screen column. With any [count],\r\n                    skips over whitespace and shorter lines.\r\n[!                  To the first continuous occurrence of the character under\r\n                    the cursor in the same screen column. With any [count],\r\n                    skips over whitespace and shorter lines.\r\n                    Mnemonic: The ! looks like a column, with the dot marking\r\n                    the jump target.","4":"DESCRIPTION\r\nThe f \/ F commands allow you to quickly go to next \/ previous occurrences\r\nof a character in the same line (with plugins also across lines), but are\r\nlimited to horizontal movement. But vertical movement, restricted to the same\r\nscreen column the cursor is in, across lines would often be helpful, too.\r\n\r\nThis plugin provides a |]V|{char} mapping that works just like f, but\r\nvertically. The ]v mapping is similar, but uses the character under the\r\ncursor instead of querying for it (which is a more common use case when moving\r\nvertically).\r\nThe ]| mapping is helpful for jumping out of indented blocks, or to filled-out\r\ncolumns, as it moves to the next non-whitespace in the current column.\r\nIn long sorted lists, one often wants to go to the first \/ last instance of\r\nthe current character (e.g. to move from \"[A]ddress\" to \"Aardvark\" or the last\r\n\"Azure\" before the entries with \"B\" begin). The ]! mapping does that.\r\n\r\nSOURCE\r\nThe ]| mapping was inspired by\r\n    http:\/\/stackoverflow.com\/questions\/20882722\/move-to-the-next-row-which-has-non-white-space-character-in-the-same-column-in-v\r\n\r\nSEE ALSO\r\n- The JumpToLastOccurrence.vim plugin (vimscript #3386) still moves\r\n  horizontally in the same line, but counts the characters in reverse,\r\n  starting from the last one.\r\n- The JumpToVerticalBlock.vim plugin (vimscript #5657) has motions that\r\n  operate like W and E, but vertically.\r\n- Check out the CountJump.vim plugin page (vimscript #3130) for a full list\r\n  of motions and text objects powered by it.\r\n\r\nRELATED WORKS\r\n- columnmove (vimscript #4880) defines f\/t\/;\/, commands as well as w\/e\/b\/ge\r\n  commands that work vertically, either skipping or opening closed folds.\r\n- columnMove (vimscript #5402) moves to the end \/ start of vertical blocks of\r\n  non-whitespace.\r\n\r\nUSAGE\r\n]v                  To [count]'th occurrence of the character under the cursor\r\n                    in the same screen column of following lines.\r\n[v                  To [count]'th occurrence of the character under the cursor\r\n                    in the same screen column of previous lines.\r\n\r\n]V{char}            To [count]'th occurrence of {char} in the same screen\r\n                    column of following lines. Like f, but vertically.\r\n[V{char}            To [count]'th occurrence of {char} in the same screen\r\n                    column of previous lines. Like F, but vertically.\r\n                    You can quickly repeat the same motion via the ]v \/ [v\r\n                    mappings (like ; \/ , for f).\r\n\r\n]|                  To [count]'th next line that has non-whitespace in the\r\n                    same column as the current one.\r\n[|                  To [count]'th previous line that has non-whitespace in the\r\n                    same column as the current one.\r\n\r\n]!                  To the last continuous occurrence of the character under\r\n                    the cursor in the same screen column. With any [count],\r\n                    skips over whitespace and shorter lines.\r\n[!                  To the first continuous occurrence of the character under\r\n                    the cursor in the same screen column. With any [count],\r\n                    skips over whitespace and shorter lines.\r\n                    Mnemonic: The ! looks like a column, with the dot marking\r\n                    the jump target.","install_details":"INSTALLATION\r\nThe code is hosted in a Git repo at\r\n    https:\/\/github.com\/inkarkat\/vim-JumpToVerticalOccurrence\r\nYou can use your favorite plugin manager, or \"git clone\" into a directory used\r\nfor Vim packages. Releases are on the \"stable\" branch, the latest unstable\r\ndevelopment snapshot on \"master\".\r\n\r\nThis script is also packaged as a vimball. If you have the \"gunzip\"\r\ndecompressor in your PATH, simply edit the *.vmb.gz package in Vim; otherwise,\r\ndecompress the archive first, e.g. using WinZip. Inside Vim, install by\r\nsourcing the vimball or via the :UseVimball command.\r\n    vim JumpToVerticalOccurrence*.vmb.gz\r\n    :so %\r\nTo uninstall, use the :RmVimball command.\r\n\r\nDEPENDENCIES\r\n- Requires Vim 7.0 or higher.\r\n- Requires the CountJump plugin (vimscript #3130), version 1.60 or higher.\r\n- Requires the ingo-library.vim plugin (vimscript #4433), version 1.034 or\r\n  higher.\r\n- repeat.vim (vimscript #2136) plugin (optional)\r\n\r\nCONFIGURATION\r\nFor a permanent configuration, put the following commands into your vimrc:\r\n\r\nTo change the default motion mappings, use:\r\n    let g:JumpToVerticalOccurrence_CharUnderCursorMapping = 'v'\r\n    let g:JumpToVerticalOccurrence_QueriedMapping = 'V'\r\n    let g:JumpToVerticalOccurrence_NonWhitespaceMapping = '<Bar>'\r\n    let g:JumpToVerticalOccurrence_LastSameCharMapping = '!'\r\nTo also change the [ \/ ] prefix to something else, follow the instructions for\r\nCountJump-remap-motions.","5":"INSTALLATION\r\nThe code is hosted in a Git repo at\r\n    https:\/\/github.com\/inkarkat\/vim-JumpToVerticalOccurrence\r\nYou can use your favorite plugin manager, or \"git clone\" into a directory used\r\nfor Vim packages. Releases are on the \"stable\" branch, the latest unstable\r\ndevelopment snapshot on \"master\".\r\n\r\nThis script is also packaged as a vimball. If you have the \"gunzip\"\r\ndecompressor in your PATH, simply edit the *.vmb.gz package in Vim; otherwise,\r\ndecompress the archive first, e.g. using WinZip. Inside Vim, install by\r\nsourcing the vimball or via the :UseVimball command.\r\n    vim JumpToVerticalOccurrence*.vmb.gz\r\n    :so %\r\nTo uninstall, use the :RmVimball command.\r\n\r\nDEPENDENCIES\r\n- Requires Vim 7.0 or higher.\r\n- Requires the CountJump plugin (vimscript #3130), version 1.60 or higher.\r\n- Requires the ingo-library.vim plugin (vimscript #4433), version 1.034 or\r\n  higher.\r\n- repeat.vim (vimscript #2136) plugin (optional)\r\n\r\nCONFIGURATION\r\nFor a permanent configuration, put the following commands into your vimrc:\r\n\r\nTo change the default motion mappings, use:\r\n    let g:JumpToVerticalOccurrence_CharUnderCursorMapping = 'v'\r\n    let g:JumpToVerticalOccurrence_QueriedMapping = 'V'\r\n    let g:JumpToVerticalOccurrence_NonWhitespaceMapping = '<Bar>'\r\n    let g:JumpToVerticalOccurrence_LastSameCharMapping = '!'\r\nTo also change the [ \/ ] prefix to something else, follow the instructions for\r\nCountJump-remap-motions.","first_name":"Ingo","6":"Ingo","last_name":"Karkat","7":"Karkat","releases":[{"0":"4841","vim_version":"7.0","1":"7.0","script_version":"1.01","2":"1.01","version_comment":"- BUG: ]! on a single occurrence of a character in that column mistakenly jumps to end of buffer.\r\n- BUG: <count>]! may jump too far and land on whitespace instead of the last line that contains the current character at the current column. *** You need to update to ingo-library (vimscript #4433) version 1.034! ***","3":"- BUG: ]! on a single occurrence of a character in that column mistakenly jumps to end of buffer.\r\n- BUG: <count>]! may jump too far and land on whitespace instead of the last line that contains the current character at the current column. *** You need to update to ingo-library (vimscript #4433) version 1.034! ***","package":"JumpToVerticalOccurrence-1.01.vmb.gz","4":"JumpToVerticalOccurrence-1.01.vmb.gz","src_id":"25827","5":"25827","creation_date":"1518596239","6":"1518596239"},{"0":"4841","vim_version":"7.0","1":"7.0","script_version":"1.00","2":"1.00","version_comment":"Initial upload","3":"Initial upload","package":"JumpToVerticalOccurrence-1.00.vmb.gz","4":"JumpToVerticalOccurrence-1.00.vmb.gz","src_id":"21357","5":"21357","creation_date":"1390396095","6":"1390396095"}]},"4840":{"script_id":"4840","0":"4840","script_name":"rename","1":"rename","script_type":"utility","2":"utility","summary":"Rename a buffer within Vim and on the disk. Supports relative path.","3":"Rename a buffer within Vim and on the disk. Supports relative path.","description":"Rename a buffer within Vim and on the disk. Supports relative path.\r\nhttps:\/\/github.com\/artnez\/vim-rename","4":"Rename a buffer within Vim and on the disk. Supports relative path.\r\nhttps:\/\/github.com\/artnez\/vim-rename","install_details":"","5":"","first_name":"Artem","6":"Artem","last_name":"Nezvigin","7":"Nezvigin","releases":[{"0":"4840","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"rename.vim","4":"rename.vim","src_id":"21355","5":"21355","creation_date":"1390378313","6":"1390378313"}]},"4839":{"script_id":"4839","0":"4839","script_name":"writepath","1":"writepath","script_type":"utility","2":"utility","summary":"Open a buffer for writing without having to create the parent directories.","3":"Open a buffer for writing without having to create the parent directories.","description":"Open a buffer for writing without having to create the parent directories leading up to the filename.\r\nhttps:\/\/github.com\/artnez\/vim-writepath","4":"Open a buffer for writing without having to create the parent directories leading up to the filename.\r\nhttps:\/\/github.com\/artnez\/vim-writepath","install_details":"","5":"","first_name":"Artem","6":"Artem","last_name":"Nezvigin","7":"Nezvigin","releases":[{"0":"4839","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"writepath.vim","4":"writepath.vim","src_id":"21354","5":"21354","creation_date":"1390377721","6":"1390377721"}]},"4838":{"script_id":"4838","0":"4838","script_name":"counterpoint.vim","1":"counterpoint.vim","script_type":"utility","2":"utility","summary":"Easily navigate file counterparts.","3":"Easily navigate file counterparts.","description":"Use Counterpoint to easily cycle between file counterparts (.h, .cpp, .osx.mm, win.cpp, and so on) via the :CounterpointNext and :CounterpointPrevious commands.\r\n\r\nCounterpoint works by taking the current file, determining the root file name, and switching between files with the same root but different extensions. This allows Counterpoint to operate on multi-level file extensions instead of just the traditional .h and .cpp pairs, and allows it to cycle in a natural way without any configuration beyond mapping at least one of the command commands in your .vimrc, perhaps like so:\r\n\r\nnnoremap <leader>a :CounterpointNext\r\n\r\nFor feature requests, bugs, better documentation and the latest version, check out the GitHub page:\r\n\r\nhttps:\/\/github.com\/jpetrie\/vim-counterpoint\r\n\r\n","4":"Use Counterpoint to easily cycle between file counterparts (.h, .cpp, .osx.mm, win.cpp, and so on) via the :CounterpointNext and :CounterpointPrevious commands.\r\n\r\nCounterpoint works by taking the current file, determining the root file name, and switching between files with the same root but different extensions. This allows Counterpoint to operate on multi-level file extensions instead of just the traditional .h and .cpp pairs, and allows it to cycle in a natural way without any configuration beyond mapping at least one of the command commands in your .vimrc, perhaps like so:\r\n\r\nnnoremap <leader>a :CounterpointNext\r\n\r\nFor feature requests, bugs, better documentation and the latest version, check out the GitHub page:\r\n\r\nhttps:\/\/github.com\/jpetrie\/vim-counterpoint\r\n\r\n","install_details":"Use your favorite plugin manager (Pathogen, Vundle, et cetera) or extract directly into ~\/.vim.","5":"Use your favorite plugin manager (Pathogen, Vundle, et cetera) or extract directly into ~\/.vim.","first_name":"Josh","6":"Josh","last_name":"Petrie","7":"Petrie","releases":[{"0":"4838","vim_version":"7.0","1":"7.0","script_version":"1.6","2":"1.6","version_comment":"Official 1.6 release.","3":"Official 1.6 release.","package":"counterpoint.zip","4":"counterpoint.zip","src_id":"24062","5":"24062","creation_date":"1457113804","6":"1457113804"},{"0":"4838","vim_version":"7.0","1":"7.0","script_version":"1.5","2":"1.5","version_comment":"Official 1.5 release.","3":"Official 1.5 release.","package":"counterpoint.zip","4":"counterpoint.zip","src_id":"23942","5":"23942","creation_date":"1453572166","6":"1453572166"},{"0":"4838","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Official 1.0 release.","3":"Official 1.0 release.","package":"counterpoint.zip","4":"counterpoint.zip","src_id":"22764","5":"22764","creation_date":"1420687280","6":"1420687280"},{"0":"4838","vim_version":"7.0","1":"7.0","script_version":"0.3","2":"0.3","version_comment":"Adds support for excluding files from the counterpart set.","3":"Adds support for excluding files from the counterpart set.","package":"counterpoint.zip","4":"counterpoint.zip","src_id":"21687","5":"21687","creation_date":"1396031344","6":"1396031344"},{"0":"4838","vim_version":"7.0","1":"7.0","script_version":"0.2","2":"0.2","version_comment":"Adds support for user search paths, allowing Counterpoint to cycle between counterparts located outside the current file's directory (useful if source and headers are in sibling directories).","3":"Adds support for user search paths, allowing Counterpoint to cycle between counterparts located outside the current file's directory (useful if source and headers are in sibling directories).","package":"counterpoint.zip","4":"counterpoint.zip","src_id":"21360","5":"21360","creation_date":"1390453882","6":"1390453882"},{"0":"4838","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"counterpoint.zip","4":"counterpoint.zip","src_id":"21351","5":"21351","creation_date":"1390277379","6":"1390277379"}]},"4837":{"script_id":"4837","0":"4837","script_name":"vim-bemhtml","1":"vim-bemhtml","script_type":"syntax","2":"syntax","summary":"Syntax for bemhtml template language","3":"Syntax for bemhtml template language","description":"Syntax highlighting for bemhtml template engine.","4":"Syntax highlighting for bemhtml template engine.","install_details":"Requires https:\/\/github.com\/pangloss\/vim-javascript installed.","5":"Requires https:\/\/github.com\/pangloss\/vim-javascript installed.","first_name":"Sergej","6":"Sergej","last_name":"Tatrincev","7":"Tatrincev","releases":[{"0":"4837","vim_version":"7.3","1":"7.3","script_version":"0.1.0","2":"0.1.0","version_comment":"Initial upload","3":"Initial upload","package":"vim-bemhtml.zip","4":"vim-bemhtml.zip","src_id":"21348","5":"21348","creation_date":"1390210935","6":"1390210935"}]},"4836":{"script_id":"4836","0":"4836","script_name":"NERDTree Fetch","1":"NERDTree Fetch","script_type":"utility","2":"utility","summary":"NERDTree plugin to pull a file from the internet in the current node","3":"NERDTree plugin to pull a file from the internet in the current node","description":"This is a simple plugin for NERDTree to allow a file to be pulled from the internet using wget or curl.\r\n\r\nGithub: https:\/\/github.com\/markgandolfo\/nerdtree-fetch.vim\r\n\r\nTo use place the cursor over the directory you wish to pull the file into, and open the file menu in NERDTree using (m), then press (f) . You will get an input asking you to enter the url of the file. Fill in the the url and press enter.","4":"This is a simple plugin for NERDTree to allow a file to be pulled from the internet using wget or curl.\r\n\r\nGithub: https:\/\/github.com\/markgandolfo\/nerdtree-fetch.vim\r\n\r\nTo use place the cursor over the directory you wish to pull the file into, and open the file menu in NERDTree using (m), then press (f) . You will get an input asking you to enter the url of the file. Fill in the the url and press enter.","install_details":"To install the plugin just copy autoload, plugin, doc directories into your .vim directory.\r\n\r\nVundle\r\n\r\nTo Install using Vundle add the following to your vimrc file after the NerdTree Bundle.\r\n\r\nBundle 'markgandolfo\/nerdtree-fetch.vim'\r\nPathogen\r\n\r\nTo install via Pathogen run the following commands\r\n\r\ncd ~\/.vim\/bundle\r\ngit clone git@github.com:markgandolfo\/nerdtree-fetch.vim.git\r\n","5":"To install the plugin just copy autoload, plugin, doc directories into your .vim directory.\r\n\r\nVundle\r\n\r\nTo Install using Vundle add the following to your vimrc file after the NerdTree Bundle.\r\n\r\nBundle 'markgandolfo\/nerdtree-fetch.vim'\r\nPathogen\r\n\r\nTo install via Pathogen run the following commands\r\n\r\ncd ~\/.vim\/bundle\r\ngit clone git@github.com:markgandolfo\/nerdtree-fetch.vim.git\r\n","first_name":"Mark","6":"Mark","last_name":"Gandolfo","7":"Gandolfo","releases":[{"0":"4836","vim_version":"7.0","1":"7.0","script_version":"1.3","2":"1.3","version_comment":"* Changed name to nerdtree-fetch from nerdtree-wget. \r\n* I know use curl if wget is unavailable","3":"* Changed name to nerdtree-fetch from nerdtree-wget. \r\n* I know use curl if wget is unavailable","package":"nerdtree-fetch.vim-1.3.tar.gz","4":"nerdtree-fetch.vim-1.3.tar.gz","src_id":"22363","5":"22363","creation_date":"1409003942","6":"1409003942"},{"0":"4836","vim_version":"7.0","1":"7.0","script_version":"1.2","2":"1.2","version_comment":"Moved plugin to after\/plugin to ensure it's loaded after nerdtree","3":"Moved plugin to after\/plugin to ensure it's loaded after nerdtree","package":"nerdtree-wget.tgz","4":"nerdtree-wget.tgz","src_id":"21369","5":"21369","creation_date":"1390628263","6":"1390628263"},{"0":"4836","vim_version":"7.0","1":"7.0","script_version":"1.1","2":"1.1","version_comment":"Fixed current path upload with wget. ","3":"Fixed current path upload with wget. ","package":"nerdtree-wget.vim.tgz","4":"nerdtree-wget.vim.tgz","src_id":"21363","5":"21363","creation_date":"1390483397","6":"1390483397"},{"0":"4836","vim_version":"7.0","1":"7.0","script_version":"1","2":"1","version_comment":"Initial upload","3":"Initial upload","package":"nerdtree-wget.tgz","4":"nerdtree-wget.tgz","src_id":"21346","5":"21346","creation_date":"1390134487","6":"1390134487"}]},"4835":{"script_id":"4835","0":"4835","script_name":"microViche","1":"microViche","script_type":"utility","2":"utility","summary":"pan and zoom through the archive!","3":"pan and zoom through the archive!","description":"microViche (microfiche + Vi) lets you pan and zoom through text archives and\r\n... has great mouse support,\r\n... automatic mapping,\r\n... a youtube demo (https:\/\/www.youtube.com\/watch?v=9YNiPUTGO28),\r\n... and a github site (https:\/\/github.com\/q335r49\/microviche)!","4":"microViche (microfiche + Vi) lets you pan and zoom through text archives and\r\n... has great mouse support,\r\n... automatic mapping,\r\n... a youtube demo (https:\/\/www.youtube.com\/watch?v=9YNiPUTGO28),\r\n... and a github site (https:\/\/github.com\/q335r49\/microviche)!","install_details":":source nav.vim\r\nPress f10 to evoke a file prompt: you can start off with a pattern (eg, *.txt) or a single file.","5":":source nav.vim\r\nPress f10 to evoke a file prompt: you can start off with a pattern (eg, *.txt) or a single file.","first_name":"Liang","6":"Liang","last_name":"Li","7":"Li","releases":[{"0":"4835","vim_version":"7.4","1":"7.4","script_version":"1.8.4.2","2":"1.8.4.2","version_comment":"Some new map navigation commands, disable autocommands during panning for greater compatibility with other plugins, simpify help and warnings, minor bugs and optimizations","3":"Some new map navigation commands, disable autocommands during panning for greater compatibility with other plugins, simpify help and warnings, minor bugs and optimizations","package":"nav.vim","4":"nav.vim","src_id":"21962","5":"21962","creation_date":"1401385053","6":"1401385053"},{"0":"4835","vim_version":"7.4","1":"7.4","script_version":"1.8.4.1","2":"1.8.4.1","version_comment":"Minor bug fixes and usability improvements","3":"Minor bug fixes and usability improvements","package":"nav.vim","4":"nav.vim","src_id":"21877","5":"21877","creation_date":"1399768796","6":"1399768796"},{"0":"4835","vim_version":"7.4","1":"7.4","script_version":"1.8.4","2":"1.8.4","version_comment":"Settings apply immediately, new simpler mapping algorithm, settings UI changes, long delayed settings streamlining","3":"Settings apply immediately, new simpler mapping algorithm, settings UI changes, long delayed settings streamlining","package":"nav.vim","4":"nav.vim","src_id":"21839","5":"21839","creation_date":"1398725533","6":"1398725533"},{"0":"4835","vim_version":"7.4","1":"7.4","script_version":"1.8.3","2":"1.8.3","version_comment":"New mapping algorithm allows for partial remapping, automatic remap on show map, simpler keyboard panning scheme","3":"New mapping algorithm allows for partial remapping, automatic remap on show map, simpler keyboard panning scheme","package":"nav.vim","4":"nav.vim","src_id":"21801","5":"21801","creation_date":"1398085034","6":"1398085034"},{"0":"4835","vim_version":"7.4","1":"7.4","script_version":"1.8.2","2":"1.8.2","version_comment":"Map drawing optimizations, custom label markers, bug fixes","3":"Map drawing optimizations, custom label markers, bug fixes","package":"nav.vim","4":"nav.vim","src_id":"21748","5":"21748","creation_date":"1396964634","6":"1396964634"},{"0":"4835","vim_version":"7.4","1":"7.4","script_version":"1.8.1.1","2":"1.8.1.1","version_comment":"Map shows negative space! Handle map conflicts better! + lots of usability and bug fixes","3":"Map shows negative space! Handle map conflicts better! + lots of usability and bug fixes","package":"nav.vim","4":"nav.vim","src_id":"21731","5":"21731","creation_date":"1396567833","6":"1396567833"},{"0":"4835","vim_version":"7.4","1":"7.4","script_version":"1.8.0","2":"1.8.0","version_comment":"*ALL MAP DATA WILL BE LOST ON UPDATE* Long overdue map overhaul: Manual mapping removed, there are no longer explicit map cells, but a zoom level determines how the map is drawn. Also, name change, optimizations, simplifications.","3":"*ALL MAP DATA WILL BE LOST ON UPDATE* Long overdue map overhaul: Manual mapping removed, there are no longer explicit map cells, but a zoom level determines how the map is drawn. Also, name change, optimizations, simplifications.","package":"nav.vim","4":"nav.vim","src_id":"21696","5":"21696","creation_date":"1396276336","6":"1396276336"},{"0":"4835","vim_version":"7.0","1":"7.0","script_version":"1.7.6","2":"1.7.6","version_comment":"The jagged bottom of the abyss (ie, long, uneven splits) has been tamed, hopefully","3":"The jagged bottom of the abyss (ie, long, uneven splits) has been tamed, hopefully","package":"nav.vim","4":"nav.vim","src_id":"21658","5":"21658","creation_date":"1395669541","6":"1395669541"},{"0":"4835","vim_version":"7.0","1":"7.0","script_version":"1.7.5.1","2":"1.7.5.1","version_comment":"Scroll wheel works, bug fixes","3":"Scroll wheel works, bug fixes","package":"nav.vim","4":"nav.vim","src_id":"21640","5":"21640","creation_date":"1395241143","6":"1395241143"},{"0":"4835","vim_version":"7.0","1":"7.0","script_version":"1.7.5","2":"1.7.5","version_comment":"Automapping -- Lines of the form txb:[lnum][: Label] will automatically generate a map label on [hotkey][R]eformat (in addition to redrawing and realigning). Automatic labels will never overwrite user set labels.","3":"Automapping -- Lines of the form txb:[lnum][: Label] will automatically generate a map label on [hotkey][R]eformat (in addition to redrawing and realigning). Automatic labels will never overwrite user set labels.","package":"nav.vim","4":"nav.vim","src_id":"21630","5":"21630","creation_date":"1395099568","6":"1395099568"},{"0":"4835","vim_version":"7.0","1":"7.0","script_version":"1.7.4","2":"1.7.4","version_comment":"Working directory! (Plane is now unaffected by directory changes and can be loaded from anywhere.) + minor fixes and improvements","3":"Working directory! (Plane is now unaffected by directory changes and can be loaded from anywhere.) + minor fixes and improvements","package":"nav.vim","4":"nav.vim","src_id":"21613","5":"21613","creation_date":"1394739168","6":"1394739168"}]},"4834":{"script_id":"4834","0":"4834","script_name":"vimcaps","1":"vimcaps","script_type":"utility","2":"utility","summary":"Toggle off capslock when back to normal mode.","3":"Toggle off capslock when back to normal mode.","description":"vimcaps\r\nNever be bothered by caps lock.\r\n\r\nAs is known, capslock is almost useless in vim\\'s normal mode. If it happens that the capslock is locked, you know what the fuck is going to happen:\r\n\r\n+ You want to move up, but came out a man;\r\n+ You wanna move down, but line joins;\r\n+ You try to undo those joins, but it undo itself;\r\n+ ...\r\n\r\nSo, lots of vimmers disabled the capslock or map it to another key. Yes, that is a beautiful solution. I don\\'t like capslock too. But someday, I notice that the capslock is still useful, ---if you have to use an on screen keyboard (e.g., with a touch screen) Then I decide to do a simple thing instead of remap the keyboard: Toggle off the capslock when back to normal mode, ---that is what this plugin do.\r\n\r\nvimcaps now support Windows and Linux (actually xWindow, we need Xlib), TTYs are still not supported. BSD hasn't been tested, suggestions are welcomed. Since I don't have a mac, there won't be any mac support until someone send a pull request. :)\r\n\r\nLinux support may have some bug (Although according to my test, only with such a strange way can vimcaps work. I'm using ubuntu 13.10 and a logitech small keyboard and onboard BTW). What we need to know is that, xWindow have a shift lock modifier. I don't know if such a lock exists on a physical keyboard or not, but Xlib functions can't change onboard's shift lock. So this shift lock is still a problem.\r\n\r\nUsage:\r\nAfter install, this plugin will automatically handle the capslock for you: vimcaps register autocmd for toggle off the capslock when InsertLeave, BufferWinEnter and FocusGained. Note that FocusGained may don't work if you are under a terminal.\r\n\r\nStarting from 0.0.3, vimcaps provide a function vimcaps#statusline() in order to display the keyboard locks status on the statusline. You'll need to add it to your statusline settings to enable it.\r\n\r\nset stl=...%{vimcaps#statusline(N)}...\r\n\r\nMore information can be obtained from the source, or check out:\r\nhttps:\/\/github.com\/suxpert\/vimcaps","4":"vimcaps\r\nNever be bothered by caps lock.\r\n\r\nAs is known, capslock is almost useless in vim\\'s normal mode. If it happens that the capslock is locked, you know what the fuck is going to happen:\r\n\r\n+ You want to move up, but came out a man;\r\n+ You wanna move down, but line joins;\r\n+ You try to undo those joins, but it undo itself;\r\n+ ...\r\n\r\nSo, lots of vimmers disabled the capslock or map it to another key. Yes, that is a beautiful solution. I don\\'t like capslock too. But someday, I notice that the capslock is still useful, ---if you have to use an on screen keyboard (e.g., with a touch screen) Then I decide to do a simple thing instead of remap the keyboard: Toggle off the capslock when back to normal mode, ---that is what this plugin do.\r\n\r\nvimcaps now support Windows and Linux (actually xWindow, we need Xlib), TTYs are still not supported. BSD hasn't been tested, suggestions are welcomed. Since I don't have a mac, there won't be any mac support until someone send a pull request. :)\r\n\r\nLinux support may have some bug (Although according to my test, only with such a strange way can vimcaps work. I'm using ubuntu 13.10 and a logitech small keyboard and onboard BTW). What we need to know is that, xWindow have a shift lock modifier. I don't know if such a lock exists on a physical keyboard or not, but Xlib functions can't change onboard's shift lock. So this shift lock is still a problem.\r\n\r\nUsage:\r\nAfter install, this plugin will automatically handle the capslock for you: vimcaps register autocmd for toggle off the capslock when InsertLeave, BufferWinEnter and FocusGained. Note that FocusGained may don't work if you are under a terminal.\r\n\r\nStarting from 0.0.3, vimcaps provide a function vimcaps#statusline() in order to display the keyboard locks status on the statusline. You'll need to add it to your statusline settings to enable it.\r\n\r\nset stl=...%{vimcaps#statusline(N)}...\r\n\r\nMore information can be obtained from the source, or check out:\r\nhttps:\/\/github.com\/suxpert\/vimcaps","install_details":"If you download the package from vim.org, unzip the package to your vimfiles folder.\r\n\r\nFor Linux user, you need to compile the library manually, or let vimcaps compile it automatically. make, gcc, Xlib must be installed first.\r\n\r\nFor vundle and vim-addons-manager user, please visit:\r\nhttps:\/\/github.com\/suxpert\/vimcaps\r\n","5":"If you download the package from vim.org, unzip the package to your vimfiles folder.\r\n\r\nFor Linux user, you need to compile the library manually, or let vimcaps compile it automatically. make, gcc, Xlib must be installed first.\r\n\r\nFor vundle and vim-addons-manager user, please visit:\r\nhttps:\/\/github.com\/suxpert\/vimcaps\r\n","first_name":"LiTuX","6":"LiTuX","last_name":"S.","7":"S.","releases":[{"0":"4834","vim_version":"7.0","1":"7.0","script_version":"0.1.1","2":"0.1.1","version_comment":"Add option to disable the autocmd (use the statusline function only, for example);\r\nRestructured, move most code into autoload\/vimcaps.vim","3":"Add option to disable the autocmd (use the statusline function only, for example);\r\nRestructured, move most code into autoload\/vimcaps.vim","package":"vimcaps-0.1.1.zip","4":"vimcaps-0.1.1.zip","src_id":"21521","5":"21521","creation_date":"1393059989","6":"1393059989"},{"0":"4834","vim_version":"7.0","1":"7.0","script_version":"0.1.0","2":"0.1.0","version_comment":"vimcaps now support xWindow, hence version became 0.1.0. :)","3":"vimcaps now support xWindow, hence version became 0.1.0. :)","package":"vimcaps-0.1.0.zip","4":"vimcaps-0.1.0.zip","src_id":"21486","5":"21486","creation_date":"1392471402","6":"1392471402"},{"0":"4834","vim_version":"7.0","1":"7.0","script_version":"0.0.3","2":"0.0.3","version_comment":"Add \"vimcaps#statusline()\" function for displaying the keyboard lock status in statusline.\r\n","3":"Add \"vimcaps#statusline()\" function for displaying the keyboard lock status in statusline.\r\n","package":"vimcaps-0.0.3.zip","4":"vimcaps-0.0.3.zip","src_id":"21371","5":"21371","creation_date":"1390650304","6":"1390650304"},{"0":"4834","vim_version":"7.0","1":"7.0","script_version":"0.0.2","2":"0.0.2","version_comment":"Optimize functions, add some high level function for numlock and scrollock, add vimcaps#dance() function for fun. Let's dance! :)","3":"Optimize functions, add some high level function for numlock and scrollock, add vimcaps#dance() function for fun. Let's dance! :)","package":"vimcaps-0.0.2.zip","4":"vimcaps-0.0.2.zip","src_id":"21349","5":"21349","creation_date":"1390211007","6":"1390211007"},{"0":"4834","vim_version":"7.0","1":"7.0","script_version":"0.0.1","2":"0.0.1","version_comment":"Initial upload","3":"Initial upload","package":"vimcaps-0.0.1.zip","4":"vimcaps-0.0.1.zip","src_id":"21328","5":"21328","creation_date":"1389882009","6":"1389882009"}]},"4833":{"script_id":"4833","0":"4833","script_name":"vim-clojure-highlight","1":"vim-clojure-highlight","script_type":"utility","2":"utility","summary":"  Extend builtin syntax highlighting to referred and aliased vars in Clojure buf","3":"  Extend builtin syntax highlighting to referred and aliased vars in Clojure buf","description":"# Home Page\r\n\r\nhttps:\/\/github.com\/guns\/vim-clojure-highlight\r\n\r\n# Introduction\r\n\r\nExtend builtin syntax highlighting to referred and aliased vars in Clojure\r\nbuffers.\r\n\r\nThis is essentially a re-implementation of the dynamic highlighting feature\r\nfrom Meikel Brandmeyer's VimClojure project.\r\n\r\n# Requires:\r\n\r\n* [fireplace.vim](https:\/\/github.com\/tpope\/vim-fireplace)\r\n\r\nIf you'd like this ported to another REPL plugin, please create an issue! This\r\ncan be done quite easily.\r\n\r\n# Installation\r\n\r\nInstall as a normal Vim plugin. If you are unfamiliar with this process,\r\nplease refer to [Pathogen](https:\/\/github.com\/tpope\/vim-pathogen).\r\n\r\n# Usage\r\n\r\n`vim-clojure-highlight` installs a hook that executes the relevant `syntax`\r\nstatements when a `*.clj` file is loaded.\r\n\r\nThis will fail silently if fireplace is unable to connect to an nREPL server.\r\n\r\nReload your buffer with `:e` to update syntax matches.\r\n\r\nReference highlighting can be toggled with the following command:\r\n\r\n    :ToggleClojureHighlightReferences\r\n\r\nand can be disabled by default:\r\n\r\n    let g:clojure_highlight_references = 0\r\n","4":"# Home Page\r\n\r\nhttps:\/\/github.com\/guns\/vim-clojure-highlight\r\n\r\n# Introduction\r\n\r\nExtend builtin syntax highlighting to referred and aliased vars in Clojure\r\nbuffers.\r\n\r\nThis is essentially a re-implementation of the dynamic highlighting feature\r\nfrom Meikel Brandmeyer's VimClojure project.\r\n\r\n# Requires:\r\n\r\n* [fireplace.vim](https:\/\/github.com\/tpope\/vim-fireplace)\r\n\r\nIf you'd like this ported to another REPL plugin, please create an issue! This\r\ncan be done quite easily.\r\n\r\n# Installation\r\n\r\nInstall as a normal Vim plugin. If you are unfamiliar with this process,\r\nplease refer to [Pathogen](https:\/\/github.com\/tpope\/vim-pathogen).\r\n\r\n# Usage\r\n\r\n`vim-clojure-highlight` installs a hook that executes the relevant `syntax`\r\nstatements when a `*.clj` file is loaded.\r\n\r\nThis will fail silently if fireplace is unable to connect to an nREPL server.\r\n\r\nReload your buffer with `:e` to update syntax matches.\r\n\r\nReference highlighting can be toggled with the following command:\r\n\r\n    :ToggleClojureHighlightReferences\r\n\r\nand can be disabled by default:\r\n\r\n    let g:clojure_highlight_references = 0\r\n","install_details":"","5":"","first_name":"Sung","6":"Sung","last_name":"Pae","7":"Pae","releases":[{"0":"4833","vim_version":"7.3","1":"7.3","script_version":"1","2":"1","version_comment":"Initial upload","3":"Initial upload","package":"vim-clojure-highlight.tar.gz","4":"vim-clojure-highlight.tar.gz","src_id":"21321","5":"21321","creation_date":"1389718294","6":"1389718294"}]},"4832":{"script_id":"4832","0":"4832","script_name":"vader.vim","1":"vader.vim","script_type":"utility","2":"utility","summary":"A simple Vimscript test framework","3":"A simple Vimscript test framework","description":"Vader.vim is a very simple and intuitive Vimscript test framework.\r\n\r\nSee the following page for more information:\r\n  https:\/\/github.com\/junegunn\/vader.vim","4":"Vader.vim is a very simple and intuitive Vimscript test framework.\r\n\r\nSee the following page for more information:\r\n  https:\/\/github.com\/junegunn\/vader.vim","install_details":"Extract in ~\/.vim or use your favorite plugin manager (junegunn\/vader.vim)","5":"Extract in ~\/.vim or use your favorite plugin manager (junegunn\/vader.vim)","first_name":"Junegunn","6":"Junegunn","last_name":"Choi","7":"Choi","releases":[{"0":"4832","vim_version":"7.3","1":"7.3","script_version":"0.3.0","2":"0.3.0","version_comment":"Bug fixes and improvements","3":"Bug fixes and improvements","package":"vader.vim.zip","4":"vader.vim.zip","src_id":"21809","5":"21809","creation_date":"1398221360","6":"1398221360"},{"0":"4832","vim_version":"7.3","1":"7.3","script_version":"0.2.0","2":"0.2.0","version_comment":"Added `Include: <VADER FILENAME>` macro","3":"Added `Include: <VADER FILENAME>` macro","package":"vader.vim.zip","4":"vader.vim.zip","src_id":"21345","5":"21345","creation_date":"1390104441","6":"1390104441"},{"0":"4832","vim_version":"7.3","1":"7.3","script_version":"0.1.0","2":"0.1.0","version_comment":"Initial upload","3":"Initial upload","package":"vader.vim.zip","4":"vader.vim.zip","src_id":"21320","5":"21320","creation_date":"1389717125","6":"1389717125"}]},"4831":{"script_id":"4831","0":"4831","script_name":"vim-airline-todo","1":"vim-airline-todo","script_type":"ftplugin","2":"ftplugin","summary":"TODO list plugin","3":"TODO list plugin","description":"see https:\/\/github.com\/Zuckonit\/vim-airline-todo","4":"see https:\/\/github.com\/Zuckonit\/vim-airline-todo","install_details":"Decompression the downloaded file","5":"Decompression the downloaded file","first_name":"Mocker","6":"Mocker","last_name":"Yang","7":"Yang","releases":[{"0":"4831","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"vim-airline-todo.zip","4":"vim-airline-todo.zip","src_id":"21318","5":"21318","creation_date":"1389689096","6":"1389689096"}]},"4830":{"script_id":"4830","0":"4830","script_name":"excel.vim","1":"excel.vim","script_type":"utility","2":"utility","summary":"A simple vim plugin for displaying texts of an excel file. ","3":"A simple vim plugin for displaying texts of an excel file. ","description":"For more information please have a look at https:\/\/github.com\/yakiang\/excel.vim","4":"For more information please have a look at https:\/\/github.com\/yakiang\/excel.vim","install_details":"","5":"","first_name":"yakiang","6":"yakiang","last_name":"zhong","7":"zhong","releases":[{"0":"4830","vim_version":"7.0","1":"7.0","script_version":"0.2.0","2":"0.2.0","version_comment":"Added support for newlines in columns and spaces in sheet names. @ Ryan ","3":"Added support for newlines in columns and spaces in sheet names. @ Ryan ","package":"excel.vim.zip","4":"excel.vim.zip","src_id":"22498","5":"22498","creation_date":"1412785726","6":"1412785726"},{"0":"4830","vim_version":"7.0","1":"7.0","script_version":"0.1.0","2":"0.1.0","version_comment":"Initial upload","3":"Initial upload","package":"excel.tar.gz","4":"excel.tar.gz","src_id":"21317","5":"21317","creation_date":"1389678700","6":"1389678700"}]},"4829":{"script_id":"4829","0":"4829","script_name":"cs class split","1":"cs class split","script_type":"utility","2":"utility","summary":"cs class split","3":"cs class split","description":"cs class split","4":"cs class split","install_details":"","5":"","first_name":"hkia","6":"hkia","last_name":"ipc","7":"ipc","releases":[{"0":"4829","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"CSFold.vim","4":"CSFold.vim","src_id":"21312","5":"21312","creation_date":"1389579874","6":"1389579874"}]},"4828":{"script_id":"4828","0":"4828","script_name":"vim-plug","1":"vim-plug","script_type":"utility","2":"utility","summary":"Minimalist Vim Plugin Manager","3":"Minimalist Vim Plugin Manager","description":"vim-plug is a minimalist Vim plugin manager with the fast parallel installer.\r\n\r\nProject home:\r\n  https:\/\/github.com\/junegunn\/vim-plug\r\n\r\nUsage:\r\n  Open your .vimrc and write down the list of plugins between plug#begin() and plug#end()\r\n\r\n        call plug#begin('~\/.vim\/plugged')\r\n\r\n        Plug 'junegunn\/seoul256.vim'\r\n        Plug 'junegunn\/vim-easy-align'\r\n        Plug 'scrooloose\/nerdtree', { 'on':  'NERDTreeToggle' }\r\n        Plug 'tpope\/vim-fireplace', { 'for': 'clojure' }\r\n        \" ...\r\n\r\n        call plug#end()\r\n\r\n  Reload it and :PlugInstall to install the plugins, :PlugUpdate to update them.\r\n  :PlugClean will remove unused plugins, and :PlugUpgrade will update vim-plug itself.\r\n\r\n  Parallel installation only works if your Vim is compiled with Ruby or Python support.\r\n","4":"vim-plug is a minimalist Vim plugin manager with the fast parallel installer.\r\n\r\nProject home:\r\n  https:\/\/github.com\/junegunn\/vim-plug\r\n\r\nUsage:\r\n  Open your .vimrc and write down the list of plugins between plug#begin() and plug#end()\r\n\r\n        call plug#begin('~\/.vim\/plugged')\r\n\r\n        Plug 'junegunn\/seoul256.vim'\r\n        Plug 'junegunn\/vim-easy-align'\r\n        Plug 'scrooloose\/nerdtree', { 'on':  'NERDTreeToggle' }\r\n        Plug 'tpope\/vim-fireplace', { 'for': 'clojure' }\r\n        \" ...\r\n\r\n        call plug#end()\r\n\r\n  Reload it and :PlugInstall to install the plugins, :PlugUpdate to update them.\r\n  :PlugClean will remove unused plugins, and :PlugUpgrade will update vim-plug itself.\r\n\r\n  Parallel installation only works if your Vim is compiled with Ruby or Python support.\r\n","install_details":"Download plug.vim and put it in ~\/.vim\/autoload\/","5":"Download plug.vim and put it in ~\/.vim\/autoload\/","first_name":"Junegunn","6":"Junegunn","last_name":"Choi","7":"Choi","releases":[{"0":"4828","vim_version":"7.0","1":"7.0","script_version":"0.8.0","2":"0.8.0","version_comment":"New features:\r\n  - Added `commit` option for fine-grained version control\r\n  - Fixed issues with parallel installer on Windows and enabled it by default\r\n\r\nImprovements:\r\n  - Changed `PlugSnapshot` to create Vim script using the new commit hash support\r\n  - `PlugDiff` shows pending updates for plugins locked on `commit` or `tag`\r\n  - Enhanced output format of post-update hooks\r\n\r\nIssues resolved:\r\n  - Fixed Ruby installer to unshallowed tagged plugin on update (#350)\r\n  - Fixed output format of Neovim installer (#340)\r\n  - Remapped `q` in plug window to `bd` (#336)\r\n  - Fixed freeze in Python installer (#318)\r\n  - Case-sensitive validation of `on` arguments (#314)\r\n  - Fixed post-update hook not to run on error\r\n  - Fixed `for` option to load syntax files (#272)\r\n  - Fixed UnicodeDecodeError from Python installer (#262)\r\n  - `set nomodifiable` on commit preview window (#255)","3":"New features:\r\n  - Added `commit` option for fine-grained version control\r\n  - Fixed issues with parallel installer on Windows and enabled it by default\r\n\r\nImprovements:\r\n  - Changed `PlugSnapshot` to create Vim script using the new commit hash support\r\n  - `PlugDiff` shows pending updates for plugins locked on `commit` or `tag`\r\n  - Enhanced output format of post-update hooks\r\n\r\nIssues resolved:\r\n  - Fixed Ruby installer to unshallowed tagged plugin on update (#350)\r\n  - Fixed output format of Neovim installer (#340)\r\n  - Remapped `q` in plug window to `bd` (#336)\r\n  - Fixed freeze in Python installer (#318)\r\n  - Case-sensitive validation of `on` arguments (#314)\r\n  - Fixed post-update hook not to run on error\r\n  - Fixed `for` option to load syntax files (#272)\r\n  - Fixed UnicodeDecodeError from Python installer (#262)\r\n  - `set nomodifiable` on commit preview window (#255)","package":"plug.vim","4":"plug.vim","src_id":"23826","5":"23826","creation_date":"1450958331","6":"1450958331"},{"0":"4828","vim_version":"7.0","1":"7.0","script_version":"0.7.2","2":"0.7.2","version_comment":"- Parallel installer for Python 2.6+ and 3.0+\r\n- Added support for Neovim Python\r\n- Shallow clone by default\r\n- PlugUpgrade using git\r\n- Trigger User autocmd when plugin is loaded on-demand\r\n- Do not add `git::@` to URI if git 2.3.0 or above is found\r\n- Bug fixes and improvements","3":"- Parallel installer for Python 2.6+ and 3.0+\r\n- Added support for Neovim Python\r\n- Shallow clone by default\r\n- PlugUpgrade using git\r\n- Trigger User autocmd when plugin is loaded on-demand\r\n- Do not add `git::@` to URI if git 2.3.0 or above is found\r\n- Bug fixes and improvements","package":"plug.vim","4":"plug.vim","src_id":"23330","5":"23330","creation_date":"1432958583","6":"1432958583"},{"0":"4828","vim_version":"7.0","1":"7.0","script_version":"0.6.2","2":"0.6.2","version_comment":"- Fixed issues with NeoVim (#118, #127)\r\n- Fixed to remove any existing ODL triggers (#130, #132)\r\n- Fixed to check for full match of command name when setting ODL triggers (#135)\r\n- Minor improvements and fixes (#123, #131, #135)","3":"- Fixed issues with NeoVim (#118, #127)\r\n- Fixed to remove any existing ODL triggers (#130, #132)\r\n- Fixed to check for full match of command name when setting ODL triggers (#135)\r\n- Minor improvements and fixes (#123, #131, #135)","package":"plug.vim","4":"plug.vim","src_id":"22690","5":"22690","creation_date":"1418400663","6":"1418400663"},{"0":"4828","vim_version":"7.0","1":"7.0","script_version":"0.6.1","2":"0.6.1","version_comment":"0.6.1:\r\n- Fixed PlugUpgrade on Neovim (#111)\r\n- Changed not to suppress messages from ftplugin when loaded on-demand (#112)\r\n- PlugInstall or PlugUpdate will now install frozen plugins as well (#113)\r\n- Fixed not to yield empty path elements in &rtp (#114)\r\n\r\n0.6.0:\r\n- Asynchronous parallel installer for Neovim\r\n- Added PlugSnapshot command\r\n- Fixed PlugClean not to remove unmanaged plugins inside g:plug_home","3":"0.6.1:\r\n- Fixed PlugUpgrade on Neovim (#111)\r\n- Changed not to suppress messages from ftplugin when loaded on-demand (#112)\r\n- PlugInstall or PlugUpdate will now install frozen plugins as well (#113)\r\n- Fixed not to yield empty path elements in &rtp (#114)\r\n\r\n0.6.0:\r\n- Asynchronous parallel installer for Neovim\r\n- Added PlugSnapshot command\r\n- Fixed PlugClean not to remove unmanaged plugins inside g:plug_home","package":"plug.vim","4":"plug.vim","src_id":"22572","5":"22572","creation_date":"1414424686","6":"1414424686"},{"0":"4828","vim_version":"7.0","1":"7.0","script_version":"0.5.7","2":"0.5.7","version_comment":"Minor bug fixes and improvements\r\n\r\n- Resolve symlinks in path to plug.vim (#67)\r\n- `syntax enable` instead of `syntax on`\r\n- Refactor PlugUpgrade (#72)\r\n- Remove plugin directory on failure during installation (#75)\r\n- Add `U` keybinding for updating plugins (#79)\r\n- Use blackhole register when deleting lines\r\n- Expand argument to plug#begin (#82)\r\n- Suppress error messages from `which` command\r\n- Improve &runtimepath mgmt (#85, #88)\r\n- Enable syntax only during startup","3":"Minor bug fixes and improvements\r\n\r\n- Resolve symlinks in path to plug.vim (#67)\r\n- `syntax enable` instead of `syntax on`\r\n- Refactor PlugUpgrade (#72)\r\n- Remove plugin directory on failure during installation (#75)\r\n- Add `U` keybinding for updating plugins (#79)\r\n- Use blackhole register when deleting lines\r\n- Expand argument to plug#begin (#82)\r\n- Suppress error messages from `which` command\r\n- Improve &runtimepath mgmt (#85, #88)\r\n- Enable syntax only during startup","package":"plug.vim","4":"plug.vim","src_id":"22458","5":"22458","creation_date":"1411663236","6":"1411663236"},{"0":"4828","vim_version":"7.0","1":"7.0","script_version":"0.5.6","2":"0.5.6","version_comment":"- Added `g:plug_window` (#57)\r\n- Changed URL for `PlugUpgrade` (#58)\r\n- Added `g:plug_url_format` (#62)\r\n- Fixed PlugDiff with git config `pull.rebase=true` (#64)\r\n- Fixed commit review of `PlugDiff` when directory changed on BufEnter\/BufLeave (#65)\r\n- Changed not to print message after PlugUpdate when there was no update (#66)","3":"- Added `g:plug_window` (#57)\r\n- Changed URL for `PlugUpgrade` (#58)\r\n- Added `g:plug_url_format` (#62)\r\n- Fixed PlugDiff with git config `pull.rebase=true` (#64)\r\n- Fixed commit review of `PlugDiff` when directory changed on BufEnter\/BufLeave (#65)\r\n- Changed not to print message after PlugUpdate when there was no update (#66)","package":"plug.vim","4":"plug.vim","src_id":"22406","5":"22406","creation_date":"1409814696","6":"1409814696"},{"0":"4828","vim_version":"7.0","1":"7.0","script_version":"0.5.5","2":"0.5.5","version_comment":"0.5.2:\r\n- Added `PlugInstall!` and `PlugUpdate!` for forced-run of post-update hooks\r\n\r\n0.5.3:\r\n- Added `-bar` option to the commands so that they can be written one line\r\n  with BARs. e.g. `PlugClean! | PlugInstall`\r\n- Fixed `PlugUpgrade` so that a restart (or reload of .vimrc) is not required\r\n  even when a very old version of vim-plug is upgraded\r\n- Removed redundant code for creating of `g:plug_home` directory\r\n\r\n0.5.4:\r\n- Added plug#helptags()\r\n- Added plug#load(name...)\r\n- Updated `:PlugStatus` to show which plugins are not yet loaded\r\n    - You load them with `L` key (visual range allowed)\r\n- Updated `:PlugDiff` to allow reverting the update with `X` key\r\n\r\n0.5.5:\r\n- Use `git::` prefix to avoid password prompt on git 1.7 (#56)\r\n- Allow Plug command even when git executable is not found (#52)","3":"0.5.2:\r\n- Added `PlugInstall!` and `PlugUpdate!` for forced-run of post-update hooks\r\n\r\n0.5.3:\r\n- Added `-bar` option to the commands so that they can be written one line\r\n  with BARs. e.g. `PlugClean! | PlugInstall`\r\n- Fixed `PlugUpgrade` so that a restart (or reload of .vimrc) is not required\r\n  even when a very old version of vim-plug is upgraded\r\n- Removed redundant code for creating of `g:plug_home` directory\r\n\r\n0.5.4:\r\n- Added plug#helptags()\r\n- Added plug#load(name...)\r\n- Updated `:PlugStatus` to show which plugins are not yet loaded\r\n    - You load them with `L` key (visual range allowed)\r\n- Updated `:PlugDiff` to allow reverting the update with `X` key\r\n\r\n0.5.5:\r\n- Use `git::` prefix to avoid password prompt on git 1.7 (#56)\r\n- Allow Plug command even when git executable is not found (#52)","package":"plug.vim","4":"plug.vim","src_id":"22338","5":"22338","creation_date":"1408210805","6":"1408210805"},{"0":"4828","vim_version":"7.0","1":"7.0","script_version":"0.5.1","2":"0.5.1","version_comment":"- Bug fixes and performance optimization.\r\n- Removed support for Plugfile\r\n","3":"- Bug fixes and performance optimization.\r\n- Removed support for Plugfile\r\n","package":"plug.vim","4":"plug.vim","src_id":"22280","5":"22280","creation_date":"1406819553","6":"1406819553"},{"0":"4828","vim_version":"7.0","1":"7.0","script_version":"0.4.0","2":"0.4.0","version_comment":"- Added support for locally-managed plugins\r\n    - Plug expression should start with either `\/`, `~`, or `$`\r\n- Added `frozen` option for not updating\/installing unless explicitly specifed\r\n- Errors during help tag generation will be ignored\r\n- Automatic retrial on timeout\r\n- Added `R` keybinding for retrying failed update\/installation\r\n- Workaround for screen freeze problem on GUI MacVim","3":"- Added support for locally-managed plugins\r\n    - Plug expression should start with either `\/`, `~`, or `$`\r\n- Added `frozen` option for not updating\/installing unless explicitly specifed\r\n- Errors during help tag generation will be ignored\r\n- Automatic retrial on timeout\r\n- Added `R` keybinding for retrying failed update\/installation\r\n- Workaround for screen freeze problem on GUI MacVim","package":"plug.vim","4":"plug.vim","src_id":"22251","5":"22251","creation_date":"1406088696","6":"1406088696"},{"0":"4828","vim_version":"7.0","1":"7.0","script_version":"0.3.5","2":"0.3.5","version_comment":"- Implemented <Plug>-based on-demand loading\r\n- Fixed `after` directory and `Plugfile` on Windows\r\n- Removed extraneous FileType events on filetype-based on-demand loading","3":"- Implemented <Plug>-based on-demand loading\r\n- Fixed `after` directory and `Plugfile` on Windows\r\n- Removed extraneous FileType events on filetype-based on-demand loading","package":"plug.vim","4":"plug.vim","src_id":"22175","5":"22175","creation_date":"1404921192","6":"1404921192"},{"0":"4828","vim_version":"7.0","1":"7.0","script_version":"0.3.4","2":"0.3.4","version_comment":"Bug fixes and improvements","3":"Bug fixes and improvements","package":"plug.vim","4":"plug.vim","src_id":"22092","5":"22092","creation_date":"1403618926","6":"1403618926"},{"0":"4828","vim_version":"7.0","1":"7.0","script_version":"0.3.3","2":"0.3.3","version_comment":"Bug fix in FT-based ODL","3":"Bug fix in FT-based ODL","package":"plug.vim","4":"plug.vim","src_id":"22076","5":"22076","creation_date":"1403416996","6":"1403416996"},{"0":"4828","vim_version":"7.0","1":"7.0","script_version":"0.3.2","2":"0.3.2","version_comment":"0.3.2\r\n- Clear #filetypeplugin for filetype-based ODL (#24)\r\n- Allow updating subset of plugins\r\n- Allow -range in on-demand loading commands\r\n- Allow trailing comment after Plug declaration (#23)\r\n","3":"0.3.2\r\n- Clear #filetypeplugin for filetype-based ODL (#24)\r\n- Allow updating subset of plugins\r\n- Allow -range in on-demand loading commands\r\n- Allow trailing comment after Plug declaration (#23)\r\n","package":"plug.vim","4":"plug.vim","src_id":"22072","5":"22072","creation_date":"1403379931","6":"1403379931"},{"0":"4828","vim_version":"7.0","1":"7.0","script_version":"0.3.1","2":"0.3.1","version_comment":"- Initialize git submodule\r\n- Filetype-based on-demand loading","3":"- Initialize git submodule\r\n- Filetype-based on-demand loading","package":"plug.vim","4":"plug.vim","src_id":"22043","5":"22043","creation_date":"1403017979","6":"1403017979"},{"0":"4828","vim_version":"7.0","1":"7.0","script_version":"0.3.0","2":"0.3.0","version_comment":"Bug fixes and improvements","3":"Bug fixes and improvements","package":"plug.vim","4":"plug.vim","src_id":"21810","5":"21810","creation_date":"1398221489","6":"1398221489"},{"0":"4828","vim_version":"7.0","1":"7.0","script_version":"0.2.0","2":"0.2.0","version_comment":"Added support for on-demand loading of plugins","3":"Added support for on-demand loading of plugins","package":"plug.vim","4":"plug.vim","src_id":"21469","5":"21469","creation_date":"1392174267","6":"1392174267"},{"0":"4828","vim_version":"7.3","1":"7.3","script_version":"0.1.0","2":"0.1.0","version_comment":"Initial upload","3":"Initial upload","package":"plug.vim","4":"plug.vim","src_id":"21310","5":"21310","creation_date":"1389544282","6":"1389544282"}]},"4827":{"script_id":"4827","0":"4827","script_name":"vim-gitgutter","1":"vim-gitgutter","script_type":"utility","2":"utility","summary":"Shows a git diff summary in the sign column and stages\/reverts individual hunks.","3":"Shows a git diff summary in the sign column and stages\/reverts individual hunks.","description":"Please see https:\/\/github.com\/airblade\/vim-gitgutter\/.","4":"Please see https:\/\/github.com\/airblade\/vim-gitgutter\/.","install_details":"Install in the usual way.","5":"Install in the usual way.","first_name":"Andrew","6":"Andrew","last_name":"Stewart","7":"Stewart","releases":[{"0":"4827","vim_version":"7.0","1":"7.0","script_version":"a4347c5","2":"a4347c5","version_comment":"Many speed improvements and bug fixes.","3":"Many speed improvements and bug fixes.","package":"vim-gitgutter.tgz","4":"vim-gitgutter.tgz","src_id":"21771","5":"21771","creation_date":"1397485090","6":"1397485090"},{"0":"4827","vim_version":"7.0","1":"7.0","script_version":"a6ac0d8","2":"a6ac0d8","version_comment":"Initial upload","3":"Initial upload","package":"vim-gitgutter.tar.gz","4":"vim-gitgutter.tar.gz","src_id":"21301","5":"21301","creation_date":"1389345445","6":"1389345445"}]},"4826":{"script_id":"4826","0":"4826","script_name":"arnaudmix2 Color Scheme","1":"arnaudmix2 Color Scheme","script_type":"color scheme","2":"color scheme","summary":"A dark color scheme vim and gvim.","3":"A dark color scheme vim and gvim.","description":"A dark color scheme for vim and gvim.\r\n\r\nScreenshot : http:\/\/i42.tinypic.com\/16is5zt.png\r\n\r\nhttps:\/\/github.com\/arnaudmix2\/arnaudmix2-color-scheme\r\n","4":"A dark color scheme for vim and gvim.\r\n\r\nScreenshot : http:\/\/i42.tinypic.com\/16is5zt.png\r\n\r\nhttps:\/\/github.com\/arnaudmix2\/arnaudmix2-color-scheme\r\n","install_details":"Place in your ~\/.vim\/colors and type :colorscheme arnaudmix2.\r\n","5":"Place in your ~\/.vim\/colors and type :colorscheme arnaudmix2.\r\n","first_name":"Arnaud","6":"Arnaud","last_name":"Ronsse","7":"Ronsse","releases":[{"0":"4826","vim_version":"7.0","1":"7.0","script_version":"1.0.0","2":"1.0.0","version_comment":"Initial upload","3":"Initial upload","package":"arnaudmix2.vim","4":"arnaudmix2.vim","src_id":"21299","5":"21299","creation_date":"1389285133","6":"1389285133"}]},"4825":{"script_id":"4825","0":"4825","script_name":"Elda","1":"Elda","script_type":"color scheme","2":"color scheme","summary":"Dark 256-color scheme","3":"Dark 256-color scheme","description":"This colorscheme uses 256 colors in terminal mode and is similar to colorscheme luinnar.vim in gui mode.\r\n\r\nSnapshots:\r\nterminal mode: https:\/\/github.com\/lxmzhv\/vim\/blob\/master\/screenshots\/vim_elda_term.png\r\ngui mode: https:\/\/github.com\/lxmzhv\/vim\/blob\/master\/screenshots\/vim_elda_gui.png\r\n\r\nSuggestions are welcome here: https:\/\/github.com\/lxmzhv\/vim\/tree\/master\/colors","4":"This colorscheme uses 256 colors in terminal mode and is similar to colorscheme luinnar.vim in gui mode.\r\n\r\nSnapshots:\r\nterminal mode: https:\/\/github.com\/lxmzhv\/vim\/blob\/master\/screenshots\/vim_elda_term.png\r\ngui mode: https:\/\/github.com\/lxmzhv\/vim\/blob\/master\/screenshots\/vim_elda_gui.png\r\n\r\nSuggestions are welcome here: https:\/\/github.com\/lxmzhv\/vim\/tree\/master\/colors","install_details":"As usual copy the file elda.vim into your ~\/.vim\/colors\/ and then perform the command \":colors elda\" from within vim (and add this command to ~\/.vimrc if you like the scheme!).","5":"As usual copy the file elda.vim into your ~\/.vim\/colors\/ and then perform the command \":colors elda\" from within vim (and add this command to ~\/.vimrc if you like the scheme!).","first_name":"Luinnar","6":"Luinnar","last_name":".","7":".","releases":[{"0":"4825","vim_version":"7.0","1":"7.0","script_version":"1.0.2","2":"1.0.2","version_comment":"minor fix","3":"minor fix","package":"elda.vim","4":"elda.vim","src_id":"21297","5":"21297","creation_date":"1389260699","6":"1389260699"},{"0":"4825","vim_version":"7.0","1":"7.0","script_version":"1.0.1","2":"1.0.1","version_comment":"better name for the scheme!","3":"better name for the scheme!","package":"elda.vim","4":"elda.vim","src_id":"21296","5":"21296","creation_date":"1389260601","6":"1389260601"}]},"4824":{"script_id":"4824","0":"4824","script_name":"vim-pencil","1":"vim-pencil","script_type":"utility","2":"utility","summary":"Rethinking Vim as a tool for writers","3":"Rethinking Vim as a tool for writers","description":"The pencil plugin aspires to make Vim as powerful a tool for writers as it is for coders by focusing narrowly on the handful of tweaks needed to smooth the path to writing prose.\r\n\r\nFeatures of the pencil plugin:\r\n\r\n* For editing files in text, markdown, textile, and other prose-oriented file types\r\n* Agnostic on soft line wrap versus hard line breaks, supporting both\r\n* Auto-detects wrap mode via modeline and sampling\r\n* Adjusts navigation key mappings to suit the wrap mode\r\n* Creates undo points on common punctuation\r\n* When using hard line breaks, enables autoformat while inserting text\r\n* Buffer-scoped configuration (leaves your global settings alone)\r\n\r\nThe latest version of this plugin, including configuration details and a brief animated demo, can be found at: https:\/\/github.com\/reedes\/vim-pencil","4":"The pencil plugin aspires to make Vim as powerful a tool for writers as it is for coders by focusing narrowly on the handful of tweaks needed to smooth the path to writing prose.\r\n\r\nFeatures of the pencil plugin:\r\n\r\n* For editing files in text, markdown, textile, and other prose-oriented file types\r\n* Agnostic on soft line wrap versus hard line breaks, supporting both\r\n* Auto-detects wrap mode via modeline and sampling\r\n* Adjusts navigation key mappings to suit the wrap mode\r\n* Creates undo points on common punctuation\r\n* When using hard line breaks, enables autoformat while inserting text\r\n* Buffer-scoped configuration (leaves your global settings alone)\r\n\r\nThe latest version of this plugin, including configuration details and a brief animated demo, can be found at: https:\/\/github.com\/reedes\/vim-pencil","install_details":"Best installed using Pathogen, Vundle, Neobundle, or your favorite Vim package manager. ","5":"Best installed using Pathogen, Vundle, Neobundle, or your favorite Vim package manager. ","first_name":"Reed","6":"Reed","last_name":"Esau","7":"Esau","releases":[{"0":"4824","vim_version":"7.3","1":"7.3","script_version":"0.2","2":"0.2","version_comment":"Added line sampling for wrap mode detection; bug fixes ","3":"Added line sampling for wrap mode detection; bug fixes ","package":"vim-pencil-0.2.zip","4":"vim-pencil-0.2.zip","src_id":"21324","5":"21324","creation_date":"1389803485","6":"1389803485"},{"0":"4824","vim_version":"7.3","1":"7.3","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"vim-pencil-0.1.zip","4":"vim-pencil-0.1.zip","src_id":"21293","5":"21293","creation_date":"1389236166","6":"1389236166"}]},"4822":{"script_id":"4822","0":"4822","script_name":"RadicalGoodSpeed.vim","1":"RadicalGoodSpeed.vim","script_type":"color scheme","2":"color scheme","summary":"Dark colorscheme,  for web front end.","3":"Dark colorscheme,  for web front end.","description":"RadicalGoodSpeed is a dark color scheme for Vim. \r\nrecommended transparency is `:set transparency = 14`\r\n\r\nこそこそ設定してきたカラースキームです。\r\n良ければお使いください。\r\n\r\nhttps:\/\/github.com\/svjunic\/RadicalGoodSpeed.vim","4":"RadicalGoodSpeed is a dark color scheme for Vim. \r\nrecommended transparency is `:set transparency = 14`\r\n\r\nこそこそ設定してきたカラースキームです。\r\n良ければお使いください。\r\n\r\nhttps:\/\/github.com\/svjunic\/RadicalGoodSpeed.vim","install_details":"First put the RadicalGoodSpeed.vim file in your ~\/.vim\/colors\/ folder  \r\nThen add the following command to your ~\/.vimrc (without quotes) : 'colorscheme radicalgoodspeed' \r\n\r\n-----\r\nNeoBundle 'gh:svjunic\/RadicalGoodSpeed.vim.git'","5":"First put the RadicalGoodSpeed.vim file in your ~\/.vim\/colors\/ folder  \r\nThen add the following command to your ~\/.vimrc (without quotes) : 'colorscheme radicalgoodspeed' \r\n\r\n-----\r\nNeoBundle 'gh:svjunic\/RadicalGoodSpeed.vim.git'","first_name":"Jun","6":"Jun","last_name":"Fujimura","7":"Fujimura","releases":[{"0":"4822","vim_version":"8.0","1":"8.0","script_version":"1.4.0","2":"1.4.0","version_comment":"Color adjustment","3":"Color adjustment","package":"RadicalGoodSpeed.vim.zip","4":"RadicalGoodSpeed.vim.zip","src_id":"26293","5":"26293","creation_date":"1544006722","6":"1544006722"},{"0":"4822","vim_version":"7.3","1":"7.3","script_version":"1.3","2":"1.3","version_comment":"Adjustment of color.","3":"Adjustment of color.","package":"radicalgoodspeed.vim","4":"radicalgoodspeed.vim","src_id":"22029","5":"22029","creation_date":"1402915661","6":"1402915661"},{"0":"4822","vim_version":"7.3","1":"7.3","script_version":"1.1","2":"1.1","version_comment":"update TabLine settings.","3":"update TabLine settings.","package":"radicalgoodspeed.vim","4":"radicalgoodspeed.vim","src_id":"21294","5":"21294","creation_date":"1389242571","6":"1389242571"},{"0":"4822","vim_version":"7.3","1":"7.3","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"radicalgoodspeed.vim","4":"radicalgoodspeed.vim","src_id":"21288","5":"21288","creation_date":"1389164195","6":"1389164195"}]},"4821":{"script_id":"4821","0":"4821","script_name":"potion-support","1":"potion-support","script_type":"utility","2":"utility","summary":"potion-support","3":"potion-support","description":"potion-support functionality for the potion programming language","4":"potion-support functionality for the potion programming language","install_details":"","5":"","first_name":"Dolfly","6":"Dolfly","last_name":".","7":".","releases":[{"0":"4821","vim_version":"7.0","1":"7.0","script_version":"0.0.0.1","2":"0.0.0.1","version_comment":"Initial upload","3":"Initial upload","package":"potion-support.tar.gz","4":"potion-support.tar.gz","src_id":"21287","5":"21287","creation_date":"1389151496","6":"1389151496"}]},"4820":{"script_id":"4820","0":"4820","script_name":"Iceberg","1":"Iceberg","script_type":"color scheme","2":"color scheme","summary":"A dark blue color scheme with calm color palette","3":"A dark blue color scheme with calm color palette","description":"Iceberg is a dark blue color scheme for Vim.\r\nIt brings a cool-headed perspective for your happy coding :)\r\n\r\nFeatures:\r\n- Eye-friendly dark coloration, designed for GUI version\r\n- Support 256-colors terminal\r\n- Support airline theme\r\n- Support lightline colorscheme\r\n\r\nOfficial site: https:\/\/cocopon.github.io\/iceberg.vim\/\r\nGitHub repository: https:\/\/github.com\/cocopon\/iceberg.vim","4":"Iceberg is a dark blue color scheme for Vim.\r\nIt brings a cool-headed perspective for your happy coding :)\r\n\r\nFeatures:\r\n- Eye-friendly dark coloration, designed for GUI version\r\n- Support 256-colors terminal\r\n- Support airline theme\r\n- Support lightline colorscheme\r\n\r\nOfficial site: https:\/\/cocopon.github.io\/iceberg.vim\/\r\nGitHub repository: https:\/\/github.com\/cocopon\/iceberg.vim","install_details":"1. Copy colors\/iceberg.vim to ~\/.vim\/colors (or <YOUR_VIM>\\vimfiles\\colors on Windows)\r\n2. Execute :colorscheme iceberg","5":"1. Copy colors\/iceberg.vim to ~\/.vim\/colors (or <YOUR_VIM>\\vimfiles\\colors on Windows)\r\n2. Execute :colorscheme iceberg","first_name":"Hiroki","6":"Hiroki","last_name":"Kokubun","7":"Kokubun","releases":[{"0":"4820","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Added plugin supports: CtrlP, EasyMotion, Syntastic, vim-plug, etc.\r\nImprove filetype supports: css, javascript, sass, graphql, etc.\r\nAdded new highlight supports: StatusLineTerm, StatusLineTermNC.\r\nAdded Neovim terminal colors support.\r\nImprove stability of airline\/lightline support.","3":"Added plugin supports: CtrlP, EasyMotion, Syntastic, vim-plug, etc.\r\nImprove filetype supports: css, javascript, sass, graphql, etc.\r\nAdded new highlight supports: StatusLineTerm, StatusLineTermNC.\r\nAdded Neovim terminal colors support.\r\nImprove stability of airline\/lightline support.","package":"iceberg.zip","4":"iceberg.zip","src_id":"25718","5":"25718","creation_date":"1513595106","6":"1513595106"},{"0":"4820","vim_version":"7.3","1":"7.3","script_version":"0.6","2":"0.6","version_comment":"Added airline support.\r\nAdded lightline support.\r\nAdded rules for new highlight group: `EndOfBuffer`.\r\nImproved colors for javascript, markdown, etc.\r\nMinor color updates.","3":"Added airline support.\r\nAdded lightline support.\r\nAdded rules for new highlight group: `EndOfBuffer`.\r\nImproved colors for javascript, markdown, etc.\r\nMinor color updates.","package":"iceberg.zip","4":"iceberg.zip","src_id":"24801","5":"24801","creation_date":"1481698342","6":"1481698342"},{"0":"4820","vim_version":"7.3","1":"7.3","script_version":"0.5","2":"0.5","version_comment":"Improved visibility of diff with cursorline.\r\nUpdated color for swift.\r\nMinor color updates.","3":"Improved visibility of diff with cursorline.\r\nUpdated color for swift.\r\nMinor color updates.","package":"iceberg.zip","4":"iceberg.zip","src_id":"24270","5":"24270","creation_date":"1464162289","6":"1464162289"},{"0":"4820","vim_version":"7.3","1":"7.3","script_version":"0.4","2":"0.4","version_comment":"Updated color for html.","3":"Updated color for html.","package":"iceberg.zip","4":"iceberg.zip","src_id":"21612","5":"21612","creation_date":"1394724944","6":"1394724944"},{"0":"4820","vim_version":"7.3","1":"7.3","script_version":"0.3","2":"0.3","version_comment":"Added rules for diff.\r\nAdded links for help.\r\nMinor color updates.","3":"Added rules for diff.\r\nAdded links for help.\r\nMinor color updates.","package":"iceberg.zip","4":"iceberg.zip","src_id":"21406","5":"21406","creation_date":"1391083859","6":"1391083859"},{"0":"4820","vim_version":"7.3","1":"7.3","script_version":"0.2","2":"0.2","version_comment":"Initial upload","3":"Initial upload","package":"iceberg.zip","4":"iceberg.zip","src_id":"21282","5":"21282","creation_date":"1389022497","6":"1389022497"}]},"4819":{"script_id":"4819","0":"4819","script_name":"select & search","1":"select & search","script_type":"utility","2":"utility","summary":"select text in v mode, then press n to search next one (N for prev one)","3":"select text in v mode, then press n to search next one (N for prev one)","description":"More details in Github: http:\/\/github.com\/luochen1990\/select-and-search\r\n\r\nAny problem, create a new issue here: http:\/\/github.com\/luochen1990\/select-and-search\/issues ","4":"More details in Github: http:\/\/github.com\/luochen1990\/select-and-search\r\n\r\nAny problem, create a new issue here: http:\/\/github.com\/luochen1990\/select-and-search\/issues ","install_details":"go to Github http:\/\/github.com\/luochen1990\/select-and-search for more details","5":"go to Github http:\/\/github.com\/luochen1990\/select-and-search for more details","first_name":"luo","6":"luo","last_name":"chen","7":"chen","releases":[{"0":"4819","vim_version":"7.3","1":"7.3","script_version":"1.1","2":"1.1","version_comment":"select_and_search_active = 2 or 3 added.","3":"select_and_search_active = 2 or 3 added.","package":"select_and_search.vim","4":"select_and_search.vim","src_id":"22149","5":"22149","creation_date":"1404718691","6":"1404718691"},{"0":"4819","vim_version":"7.3","1":"7.3","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"select_and_search.vim","4":"select_and_search.vim","src_id":"21280","5":"21280","creation_date":"1388983381","6":"1388983381"}]},"4818":{"script_id":"4818","0":"4818","script_name":"vizardry","1":"vizardry","script_type":"utility","2":"utility","summary":"A pathogen-based plugin manager for lazy people","3":"A pathogen-based plugin manager for lazy people","description":"Vizardry allows you to quickly search for and install vim plugins.\r\n\r\nAfter installing vizardry, type \":Invoke <keyword>\" and vizardry will search github for vim plugins matching that keyword and ask you if you want to install one. You can start using the installed plugin immediately.\r\n\r\nYou can remove plugins with \":Banish <keyword>\"\r\n\r\nFind out more and get the latest version at https:\/\/github.com\/ardagnir\/vizardry","4":"Vizardry allows you to quickly search for and install vim plugins.\r\n\r\nAfter installing vizardry, type \":Invoke <keyword>\" and vizardry will search github for vim plugins matching that keyword and ask you if you want to install one. You can start using the installed plugin immediately.\r\n\r\nYou can remove plugins with \":Banish <keyword>\"\r\n\r\nFind out more and get the latest version at https:\/\/github.com\/ardagnir\/vizardry","install_details":"Vizardry requires pathogen and curl. It does NOT support Microsoft Windows.\r\n\r\nTo install:\r\n    cd ~\/.vim\/bundle\r\n    git clone https:\/\/github.com\/ardagnir\/vizardry","5":"Vizardry requires pathogen and curl. It does NOT support Microsoft Windows.\r\n\r\nTo install:\r\n    cd ~\/.vim\/bundle\r\n    git clone https:\/\/github.com\/ardagnir\/vizardry","first_name":"James","6":"James","last_name":"Kolb","7":"Kolb","releases":[{"0":"4818","vim_version":"7.0","1":"7.0","script_version":"0.2","2":"0.2","version_comment":"Added \"magic\" and support for git submodules.","3":"Added \"magic\" and support for git submodules.","package":"vizardry.tar","4":"vizardry.tar","src_id":"21352","5":"21352","creation_date":"1390279187","6":"1390279187"},{"0":"4818","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"vizardry.tar","4":"vizardry.tar","src_id":"21274","5":"21274","creation_date":"1388857076","6":"1388857076"}]},"4817":{"script_id":"4817","0":"4817","script_name":"increment-activator","1":"increment-activator","script_type":"utility","2":"utility","summary":"Enhanced to allow increment the list that you have defined","3":"Enhanced to allow increment the list that you have defined","description":"*increment-activator* is a powerful increment plugin.\r\n\r\nThe behavior is like <C-a>, <C-x> increment or decrement number by the default Vim\r\n\r\nIt has been enhanced to allow increment the list that you have defined.\r\n\r\nThe list will be generated in candidates patterns automatically.\r\n\r\nPattern of candidates:\r\n- no changes (that you have defined)\r\n- lower\r\n- UPPER\r\n- Capitalize\r\n\r\nScreen shots:\r\n- https:\/\/raw.githubusercontent.com\/nishigori\/increment-activator\/master\/snapshot.gif\r\n\r\nLatest version:\r\nhttps:\/\/github.com\/nishigori\/increment-activator\r\n\r\nDocument:\r\nhttps:\/\/raw.github.com\/nishigori\/increment-activator\/master\/doc\/vim-increment-activator.txt","4":"*increment-activator* is a powerful increment plugin.\r\n\r\nThe behavior is like <C-a>, <C-x> increment or decrement number by the default Vim\r\n\r\nIt has been enhanced to allow increment the list that you have defined.\r\n\r\nThe list will be generated in candidates patterns automatically.\r\n\r\nPattern of candidates:\r\n- no changes (that you have defined)\r\n- lower\r\n- UPPER\r\n- Capitalize\r\n\r\nScreen shots:\r\n- https:\/\/raw.githubusercontent.com\/nishigori\/increment-activator\/master\/snapshot.gif\r\n\r\nLatest version:\r\nhttps:\/\/github.com\/nishigori\/increment-activator\r\n\r\nDocument:\r\nhttps:\/\/raw.github.com\/nishigori\/increment-activator\/master\/doc\/vim-increment-activator.txt","install_details":"Please see more section of *increment-activator-installation* in the Document","5":"Please see more section of *increment-activator-installation* in the Document","first_name":"Takuya","6":"Takuya","last_name":"Nishigori","7":"Nishigori","releases":[{"0":"4817","vim_version":"7.2","1":"7.2","script_version":"0.1.0","2":"0.1.0","version_comment":"- Change variable name from 'increment_activator#config' to 'increment_activator_filetype_candidates'                   \r\n- [GH-6] Fix increment not expect multiple line               \r\n","3":"- Change variable name from 'increment_activator#config' to 'increment_activator_filetype_candidates'                   \r\n- [GH-6] Fix increment not expect multiple line               \r\n","package":"increment-activator-0.1.0.zip","4":"increment-activator-0.1.0.zip","src_id":"22107","5":"22107","creation_date":"1404039966","6":"1404039966"},{"0":"4817","vim_version":"7.2","1":"7.2","script_version":"0.0.2","2":"0.0.2","version_comment":"- Support insert-mode\r\n- Fix E154 'duplicate tag 'increment-activator'","3":"- Support insert-mode\r\n- Fix E154 'duplicate tag 'increment-activator'","package":"increment-activator-0.0.2.zip","4":"increment-activator-0.0.2.zip","src_id":"21316","5":"21316","creation_date":"1389656418","6":"1389656418"},{"0":"4817","vim_version":"7.2","1":"7.2","script_version":"0.0.1","2":"0.0.1","version_comment":"Initial upload","3":"Initial upload","package":"increment-activator-0.0.1.zip","4":"increment-activator-0.0.1.zip","src_id":"21271","5":"21271","creation_date":"1388834776","6":"1388834776"}]},"4816":{"script_id":"4816","0":"4816","script_name":"publish_helper","1":"publish_helper","script_type":"utility","2":"utility","summary":"vim code highlights in pandoc documents (HTML and TeX)","3":"vim code highlights in pandoc documents (HTML and TeX)","description":"Description:\r\n  two commands for publishing highlighted code in HTML or TeX\r\n  (optionally from pandoc as highlighting engine from filter vimhl.hs)\r\n\r\n  github: http:\/\/github.com\/lyokha\/vim-publish-helper\r\n\r\nUsage:\r\n  The commands may be used from within vim. Additionally they can act as\r\n  the highlighting engine from pandoc having been inserted inside filter\r\n  vimhl.hs shipped with this distribution.\r\n\r\n  Command :MakeHtmlCodeHighlight to create a new buffer in a new window with\r\n  HTML code correctly highlighted accordingly to the current color scheme or\r\n  scheme declared in variable g:PhColorscheme. The command uses TOhtml\r\n  internally with temporarily set value g:html_use_css = 0\r\n\r\n  Command :MakeTexCodeHighlight to create a new buffer in a new window with\r\n  TeX code correctly highlighted accordingly to the current color scheme or\r\n  scheme declared in variable g:PhColorscheme. The command accepts optional\r\n  argument which defines that lines will be enumerated. If the argument is\r\n  missing then no line enumeration will be generated, if it is negative then\r\n  lines will be enumerated from the number of the first line in the original\r\n  buffer, otherwise lines will be enumerated from the value of the argument.\r\n\r\n  The both commands can act as the highlighting engine in filter vimhl.hs\r\n  shipped with this distribution. This program is supposed to be used like\r\n\r\n  pandoc -f html -t latex -F vimhl.hs -o document.tex document.html\r\n\r\n  It is possible to compile vimhl.hs:\r\n\r\n  ghc --make vimhl\r\n\r\n  Move vimhl.hs (or compiled program vimhl) somewhere in your $PATH.\r\n\r\n  When converting formats with pandoc ensure that original file has\r\n  additional parameter hl=\"vim\" inside tag <pre> (as an example for HTML):\r\n  only in this case pandoc will choose vimhl.hs as highlighting filter.\r\n\r\n  There are two other commands :GetFgColorUnderCursor and\r\n  :GetBgColorUnderCursor. They are included as they may help in debugging\r\n  and finding foreground or background colors under cursor. Normally i use\r\n  them in maps like following:\r\n\r\n  nmap <silent> ,vc :GetFgColorUnderCursor<CR>\r\n  nmap <silent> ,vb :GetBgColorUnderCursor<CR>\r\n\r\nThanks to:\r\n  Christian Brabandt for plugin Colorizer and Xterm2rgb translation functions","4":"Description:\r\n  two commands for publishing highlighted code in HTML or TeX\r\n  (optionally from pandoc as highlighting engine from filter vimhl.hs)\r\n\r\n  github: http:\/\/github.com\/lyokha\/vim-publish-helper\r\n\r\nUsage:\r\n  The commands may be used from within vim. Additionally they can act as\r\n  the highlighting engine from pandoc having been inserted inside filter\r\n  vimhl.hs shipped with this distribution.\r\n\r\n  Command :MakeHtmlCodeHighlight to create a new buffer in a new window with\r\n  HTML code correctly highlighted accordingly to the current color scheme or\r\n  scheme declared in variable g:PhColorscheme. The command uses TOhtml\r\n  internally with temporarily set value g:html_use_css = 0\r\n\r\n  Command :MakeTexCodeHighlight to create a new buffer in a new window with\r\n  TeX code correctly highlighted accordingly to the current color scheme or\r\n  scheme declared in variable g:PhColorscheme. The command accepts optional\r\n  argument which defines that lines will be enumerated. If the argument is\r\n  missing then no line enumeration will be generated, if it is negative then\r\n  lines will be enumerated from the number of the first line in the original\r\n  buffer, otherwise lines will be enumerated from the value of the argument.\r\n\r\n  The both commands can act as the highlighting engine in filter vimhl.hs\r\n  shipped with this distribution. This program is supposed to be used like\r\n\r\n  pandoc -f html -t latex -F vimhl.hs -o document.tex document.html\r\n\r\n  It is possible to compile vimhl.hs:\r\n\r\n  ghc --make vimhl\r\n\r\n  Move vimhl.hs (or compiled program vimhl) somewhere in your $PATH.\r\n\r\n  When converting formats with pandoc ensure that original file has\r\n  additional parameter hl=\"vim\" inside tag <pre> (as an example for HTML):\r\n  only in this case pandoc will choose vimhl.hs as highlighting filter.\r\n\r\n  There are two other commands :GetFgColorUnderCursor and\r\n  :GetBgColorUnderCursor. They are included as they may help in debugging\r\n  and finding foreground or background colors under cursor. Normally i use\r\n  them in maps like following:\r\n\r\n  nmap <silent> ,vc :GetFgColorUnderCursor<CR>\r\n  nmap <silent> ,vb :GetBgColorUnderCursor<CR>\r\n\r\nThanks to:\r\n  Christian Brabandt for plugin Colorizer and Xterm2rgb translation functions","install_details":"Prerequisites for using as a pandoc filter: pandoc version 1.12 or greater, haskell\r\n\r\n1. Extract the tarball in your $HOME\/.vim directory\r\n2. Move vimhl.hs into a directory listed in the $PATH and make it executable.\r\n    Or better compile vimhl.hs:\r\n        ghc --make vimhl\r\n    and move vimhl into a directory listed in the $PATH.\r\n3. :helptags ~\/.vim\/doc\/","5":"Prerequisites for using as a pandoc filter: pandoc version 1.12 or greater, haskell\r\n\r\n1. Extract the tarball in your $HOME\/.vim directory\r\n2. Move vimhl.hs into a directory listed in the $PATH and make it executable.\r\n    Or better compile vimhl.hs:\r\n        ghc --make vimhl\r\n    and move vimhl into a directory listed in the $PATH.\r\n3. :helptags ~\/.vim\/doc\/","first_name":"Alexey","6":"Alexey","last_name":"Radkov","7":"Radkov","releases":[{"0":"4816","vim_version":"7.3","1":"7.3","script_version":"0.14","2":"0.14","version_comment":"Vim startup optimization: all functions were moved to autoload\/ directory","3":"Vim startup optimization: all functions were moved to autoload\/ directory","package":"vim-publish-helper-0.14.tgz","4":"vim-publish-helper-0.14.tgz","src_id":"28462","5":"28462","creation_date":"1683761862","6":"1683761862"},{"0":"4816","vim_version":"7.3","1":"7.3","script_version":"0.13.1","2":"0.13.1","version_comment":"- vimhl: dropped dependency on packages regex-compat and cond.\r\n- vimhl_latex_tmpl.sh: fixes after running Shellcheck.","3":"- vimhl: dropped dependency on packages regex-compat and cond.\r\n- vimhl_latex_tmpl.sh: fixes after running Shellcheck.","package":"vim-publish-helper-0.13.1.tgz","4":"vim-publish-helper-0.13.1.tgz","src_id":"28340","5":"28340","creation_date":"1673036818","6":"1673036818"},{"0":"4816","vim_version":"7.3","1":"7.3","script_version":"0.13","2":"0.13","version_comment":"- Added an option for rendering highlights built by the treesitter in Neovim.\r\n- Fixes and improvements in rendering of HTML tables for the line-number columns.\r\n- Use environment variable VIMHL_BACKEND to choose between vim flavors in vimhl.","3":"- Added an option for rendering highlights built by the treesitter in Neovim.\r\n- Fixes and improvements in rendering of HTML tables for the line-number columns.\r\n- Use environment variable VIMHL_BACKEND to choose between vim flavors in vimhl.","package":"vim-publish-helper-0.13.tgz","4":"vim-publish-helper-0.13.tgz","src_id":"28330","5":"28330","creation_date":"1672015044","6":"1672015044"},{"0":"4816","vim_version":"7.3","1":"7.3","script_version":"0.12.7","2":"0.12.7","version_comment":"updated after Pandoc 2.8 and the String-to-Text migration","3":"updated after Pandoc 2.8 and the String-to-Text migration","package":"vim-publish-helper-0.12.7.tgz","4":"vim-publish-helper-0.12.7.tgz","src_id":"27226","5":"27226","creation_date":"1593834172","6":"1593834172"},{"0":"4816","vim_version":"7.3","1":"7.3","script_version":"0.12.5","2":"0.12.5","version_comment":"miscellaneous improvement in vimhl.hs","3":"miscellaneous improvement in vimhl.hs","package":"vim-publish-helper-0.12.5.tgz","4":"vim-publish-helper-0.12.5.tgz","src_id":"26283","5":"26283","creation_date":"1542772754","6":"1542772754"},{"0":"4816","vim_version":"7.3","1":"7.3","script_version":"0.12.4","2":"0.12.4","version_comment":"better handling of Ctrl-C interrupts and vim failures in vimhl.hs","3":"better handling of Ctrl-C interrupts and vim failures in vimhl.hs","package":"vim-publish-helper-0.12.4.tgz","4":"vim-publish-helper-0.12.4.tgz","src_id":"26280","5":"26280","creation_date":"1542685162","6":"1542685162"},{"0":"4816","vim_version":"7.3","1":"7.3","script_version":"0.12.3","2":"0.12.3","version_comment":"fixes and improvements in vimhl.hs and vimhl_latex_tmpl.sh, compatibility with pandoc 2.0","3":"fixes and improvements in vimhl.hs and vimhl_latex_tmpl.sh, compatibility with pandoc 2.0","package":"vim-publish-helper-0.12.3.tgz","4":"vim-publish-helper-0.12.3.tgz","src_id":"26274","5":"26274","creation_date":"1542348013","6":"1542348013"},{"0":"4816","vim_version":"7.3","1":"7.3","script_version":"0.12.2","2":"0.12.2","version_comment":"files structure reorganized, misc enhancements, filter vimhl can now be installed with cabal","3":"files structure reorganized, misc enhancements, filter vimhl can now be installed with cabal","package":"vim-publish-helper-0.12.2.tgz","4":"vim-publish-helper-0.12.2.tgz","src_id":"24565","5":"24565","creation_date":"1474982307","6":"1474982307"},{"0":"4816","vim_version":"7.3","1":"7.3","script_version":"0.12.1","2":"0.12.1","version_comment":"fixed broken in version 0.12 tex \/ pdf output","3":"fixed broken in version 0.12 tex \/ pdf output","package":"vim-publish-helper-0.12.1.tgz","4":"vim-publish-helper-0.12.1.tgz","src_id":"22884","5":"22884","creation_date":"1423252471","6":"1423252471"},{"0":"4816","vim_version":"7.3","1":"7.3","script_version":"0.12","2":"0.12","version_comment":"    - added an option for line numbering as an HTML table effective in\r\n      the internal HTML syntax highlighting engine only: set variable\r\n      g:PhLinenrAsTblColumn and enjoy it (see updated docs)\r\n    - several improvements in script vimhl_latex_tmpl.sh\r\n    - minor refactoring of vimhl.hs","3":"    - added an option for line numbering as an HTML table effective in\r\n      the internal HTML syntax highlighting engine only: set variable\r\n      g:PhLinenrAsTblColumn and enjoy it (see updated docs)\r\n    - several improvements in script vimhl_latex_tmpl.sh\r\n    - minor refactoring of vimhl.hs","package":"vim-publish-helper-0.12.tgz","4":"vim-publish-helper-0.12.tgz","src_id":"22785","5":"22785","creation_date":"1421148189","6":"1421148189"},{"0":"4816","vim_version":"7.0","1":"7.0","script_version":"0.11","2":"0.11","version_comment":"    - added support for rich text elements: text background color, bold,\r\n      italic and underline typefaces and turned it on by default\r\n    - speed improvements, now commands may run about 30% faster","3":"    - added support for rich text elements: text background color, bold,\r\n      italic and underline typefaces and turned it on by default\r\n    - speed improvements, now commands may run about 30% faster","package":"vim-publish-helper-0.11.tgz","4":"vim-publish-helper-0.11.tgz","src_id":"21946","5":"21946","creation_date":"1401120760","6":"1401120760"},{"0":"4816","vim_version":"7.0","1":"7.0","script_version":"0.10","2":"0.10","version_comment":"    - added support for highlighting various shells outputs\r\n    - added an example with images on github","3":"    - added support for highlighting various shells outputs\r\n    - added an example with images on github","package":"vim-publish-helper-0.10.tgz","4":"vim-publish-helper-0.10.tgz","src_id":"21635","5":"21635","creation_date":"1395154172","6":"1395154172"},{"0":"4816","vim_version":"7.0","1":"7.0","script_version":"0.9","2":"0.9","version_comment":"    - further improvements in TOhtml rendering engine (completed in 0.8.x series)\r\n    - added new variable g:PhTexBlockStyle to customize code blocks visual\r\n      parameters in TeX documents\r\n    - added an auxiliary script vimhl_latex_tmpl.sh for making pandoc\r\n      templates for TeX compatible with vimhl (see updated docs)","3":"    - further improvements in TOhtml rendering engine (completed in 0.8.x series)\r\n    - added new variable g:PhTexBlockStyle to customize code blocks visual\r\n      parameters in TeX documents\r\n    - added an auxiliary script vimhl_latex_tmpl.sh for making pandoc\r\n      templates for TeX compatible with vimhl (see updated docs)","package":"vim-publish-helper-0.9.tgz","4":"vim-publish-helper-0.9.tgz","src_id":"21617","5":"21617","creation_date":"1394883042","6":"1394883042"},{"0":"4816","vim_version":"7.0","1":"7.0","script_version":"0.8.3","2":"0.8.3","version_comment":"    - properly restore global variables related to TOhtml\r\n    - minor (mostly stylistic) imrovements in vimhl.hs","3":"    - properly restore global variables related to TOhtml\r\n    - minor (mostly stylistic) imrovements in vimhl.hs","package":"vim-publish-helper-0.8.3.tgz","4":"vim-publish-helper-0.8.3.tgz","src_id":"21517","5":"21517","creation_date":"1392980956","6":"1392980956"},{"0":"4816","vim_version":"7.0","1":"7.0","script_version":"0.8.2","2":"0.8.2","version_comment":"fixed trim algorithm in TOhtml engine; minor fixes and improvements","3":"fixed trim algorithm in TOhtml engine; minor fixes and improvements","package":"vim-publish-helper-0.8.2.tgz","4":"vim-publish-helper-0.8.2.tgz","src_id":"21482","5":"21482","creation_date":"1392382113","6":"1392382113"},{"0":"4816","vim_version":"7.0","1":"7.0","script_version":"0.8.1","2":"0.8.1","version_comment":"fixed possible error messages about not found patterns when using Tohtml engine","3":"fixed possible error messages about not found patterns when using Tohtml engine","package":"vim-publish-helper-0.8.1.tgz","4":"vim-publish-helper-0.8.1.tgz","src_id":"21467","5":"21467","creation_date":"1392143680","6":"1392143680"},{"0":"4816","vim_version":"7.0","1":"7.0","script_version":"0.8","2":"0.8","version_comment":"    - both HTML rendering engines do not use tag <tt> any longer\r\n    - improved TOhtml rendering engine: full support of line numbering,\r\n      regular spaces instead HTML non-breaking spaces\r\n    - docs updated","3":"    - both HTML rendering engines do not use tag <tt> any longer\r\n    - improved TOhtml rendering engine: full support of line numbering,\r\n      regular spaces instead HTML non-breaking spaces\r\n    - docs updated","package":"vim-publish-helper-0.8.tgz","4":"vim-publish-helper-0.8.tgz","src_id":"21464","5":"21464","creation_date":"1392118226","6":"1392118226"},{"0":"4816","vim_version":"7.0","1":"7.0","script_version":"0.7","2":"0.7","version_comment":"    - customizing attributes of HTML tag <pre> using variable g:PhHtmlPreAttrs\r\n    - select between conditions in .vimrc or .vimrc.pandoc using variables\r\n      defined in a new attribute vars (see docs)","3":"    - customizing attributes of HTML tag <pre> using variable g:PhHtmlPreAttrs\r\n    - select between conditions in .vimrc or .vimrc.pandoc using variables\r\n      defined in a new attribute vars (see docs)","package":"vim-publish-helper-0.7.tgz","4":"vim-publish-helper-0.7.tgz","src_id":"21445","5":"21445","creation_date":"1391866176","6":"1391866176"},{"0":"4816","vim_version":"7.0","1":"7.0","script_version":"0.6","2":"0.6","version_comment":"    - all elements that do not have syntax names are highlighted by Normal\r\n      highlighting group\r\n    - HTML may now be rendered using internal plugin's highlighting engine,\r\n      this is controlled by a new variable g:PhHtmlEngine; with the new engine\r\n      line numbering of code blocks gets available\r\n    - added new variable g:PhTrimBlocks to control how blank lines around the\r\n      code will be managed","3":"    - all elements that do not have syntax names are highlighted by Normal\r\n      highlighting group\r\n    - HTML may now be rendered using internal plugin's highlighting engine,\r\n      this is controlled by a new variable g:PhHtmlEngine; with the new engine\r\n      line numbering of code blocks gets available\r\n    - added new variable g:PhTrimBlocks to control how blank lines around the\r\n      code will be managed","package":"vim-publish-helper-0.6.tgz","4":"vim-publish-helper-0.6.tgz","src_id":"21291","5":"21291","creation_date":"1389203895","6":"1389203895"},{"0":"4816","vim_version":"7.0","1":"7.0","script_version":"0.5","2":"0.5","version_comment":"    - added new variable g:PhCtrlTrans that deals with correct representation\r\n      of control characters in MakeTexCodeHighlight","3":"    - added new variable g:PhCtrlTrans that deals with correct representation\r\n      of control characters in MakeTexCodeHighlight","package":"vim-publish-helper-0.5.tgz","4":"vim-publish-helper-0.5.tgz","src_id":"21284","5":"21284","creation_date":"1389110378","6":"1389110378"},{"0":"4816","vim_version":"7.0","1":"7.0","script_version":"0.4","2":"0.4","version_comment":"    - fixed white-instead-black foreground issue\r\n    - added example of how to use Shaded and Highlighting environments in docs\r\n    - other small fixes","3":"    - fixed white-instead-black foreground issue\r\n    - added example of how to use Shaded and Highlighting environments in docs\r\n    - other small fixes","package":"vim-publish-helper-0.4.tgz","4":"vim-publish-helper-0.4.tgz","src_id":"21275","5":"21275","creation_date":"1388872934","6":"1388872934"},{"0":"4816","vim_version":"7.0","1":"7.0","script_version":"0.3","2":"0.3","version_comment":"    - vimhl.hs: added possibility to load a dedicated file $HOME\/.vimrc.pandoc\r\n      instead normal $HOME\/.vimrc when running pandoc: this may extremely\r\n      speed up pandoc; see docs for details\r\n    - vimhl.hs: added another option to choose color scheme when running\r\n      pandoc: attribute colorscheme; however using file $HOME\/.vimrc.pandoc is\r\n      more preferable","3":"    - vimhl.hs: added possibility to load a dedicated file $HOME\/.vimrc.pandoc\r\n      instead normal $HOME\/.vimrc when running pandoc: this may extremely\r\n      speed up pandoc; see docs for details\r\n    - vimhl.hs: added another option to choose color scheme when running\r\n      pandoc: attribute colorscheme; however using file $HOME\/.vimrc.pandoc is\r\n      more preferable","package":"vim-publish-helper-0.3.tgz","4":"vim-publish-helper-0.3.tgz","src_id":"21273","5":"21273","creation_date":"1388850968","6":"1388850968"},{"0":"4816","vim_version":"7.0","1":"7.0","script_version":"0.2","2":"0.2","version_comment":"    - dropped perl dependency in vimhl.hs\r\n    - vimhl.hs is no longer executable script (make it executable or compile)\r\n    - docs added","3":"    - dropped perl dependency in vimhl.hs\r\n    - vimhl.hs is no longer executable script (make it executable or compile)\r\n    - docs added","package":"vim-publish-helper-0.2.tgz","4":"vim-publish-helper-0.2.tgz","src_id":"21269","5":"21269","creation_date":"1388691059","6":"1388691059"},{"0":"4816","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"publish_helper-0.1.tgz","4":"publish_helper-0.1.tgz","src_id":"21268","5":"21268","creation_date":"1388607210","6":"1388607210"}]},"4815":{"script_id":"4815","0":"4815","script_name":"choowsewin.vim","1":"choowsewin.vim","script_type":"utility","2":"utility","summary":"land to window you choose like tmux's 'display-pane'.","3":"land to window you choose like tmux's 'display-pane'.","description":"GitHub : https:\/\/github.com\/t9md\/vim-choosewin\r\n\r\n# Land to window you choose~\r\n\r\nAiming to mimic tmux's `display-pane` feature, which enables you to choose\r\nwindow interactively.\r\n\r\nThis plugin should be useful especially when you are working on high\r\nresolution wide display.\r\nSince with wide display, you are likely to open multiple window and\r\nmoving around window is a little bit tiresome.\r\n\r\nThis plugin make window excursion simplify.\r\n\r\n\t1. display window label on statusbar\r\n\t2. read input from you.\r\n\t3. you can land to window you choose","4":"GitHub : https:\/\/github.com\/t9md\/vim-choosewin\r\n\r\n# Land to window you choose~\r\n\r\nAiming to mimic tmux's `display-pane` feature, which enables you to choose\r\nwindow interactively.\r\n\r\nThis plugin should be useful especially when you are working on high\r\nresolution wide display.\r\nSince with wide display, you are likely to open multiple window and\r\nmoving around window is a little bit tiresome.\r\n\r\nThis plugin make window excursion simplify.\r\n\r\n\t1. display window label on statusbar\r\n\t2. read input from you.\r\n\t3. you can land to window you choose","install_details":"","5":"","first_name":"t9","6":"t9","last_name":"md","7":"md","releases":[{"0":"4815","vim_version":"7.0","1":"7.0","script_version":"v1.5","2":"v1.5","version_comment":"2015-01-20: v1.5\r\n\t- verup again because of document mistake.\r\n2015-01-20: v1.4\r\n\t- verup\r\n2015-01-08:\r\n\t- [new] land to previous window suggested by @collinpeters\r\n\t- [enhance] remove swap virtual keymap, now its incorporate into\r\n\t  keymap within choosewin.\r\n\t- [new] create 'ChooseWinSwap' command, you don't necessarily need\r\n\t  this command since you can choose 'swap' within standard 'Choosewin'\r\n\t  command, simply sintax sugar.\r\n\t- [improve] now overlay consider offset of |windowcol()|.\r\n2014-09-05:\r\n\t- [new] introduce <Plug>(choosewin-swap-again) feature.\r\n2014-09-02:\r\n\t- [new] introduce <Plug>(choosewin-swap) feature.\r\n2014-01-15:\r\n\t- [new] add 'noop' option for api-only call\r\n\t- [new] add hook feature for filter_window before label_show()\r\n\t- [new] g:choosewin_active auto set variable intended within\r\n\t  &statuline plugin(such as disabling trailing space warning).\r\n2014-01-12:\r\n\t- [improve] disble cursorline while overlay\r\n\t- [new-feature] now support 'small' font for overlay and configurable\r\n\t  size you prefer. by default 'auto' mode determine font size based on\r\n\t  winheight(0).","3":"2015-01-20: v1.5\r\n\t- verup again because of document mistake.\r\n2015-01-20: v1.4\r\n\t- verup\r\n2015-01-08:\r\n\t- [new] land to previous window suggested by @collinpeters\r\n\t- [enhance] remove swap virtual keymap, now its incorporate into\r\n\t  keymap within choosewin.\r\n\t- [new] create 'ChooseWinSwap' command, you don't necessarily need\r\n\t  this command since you can choose 'swap' within standard 'Choosewin'\r\n\t  command, simply sintax sugar.\r\n\t- [improve] now overlay consider offset of |windowcol()|.\r\n2014-09-05:\r\n\t- [new] introduce <Plug>(choosewin-swap-again) feature.\r\n2014-09-02:\r\n\t- [new] introduce <Plug>(choosewin-swap) feature.\r\n2014-01-15:\r\n\t- [new] add 'noop' option for api-only call\r\n\t- [new] add hook feature for filter_window before label_show()\r\n\t- [new] g:choosewin_active auto set variable intended within\r\n\t  &statuline plugin(such as disabling trailing space warning).\r\n2014-01-12:\r\n\t- [improve] disble cursorline while overlay\r\n\t- [new-feature] now support 'small' font for overlay and configurable\r\n\t  size you prefer. by default 'auto' mode determine font size based on\r\n\t  winheight(0).","package":"vim-choosewin-1.5.zip","4":"vim-choosewin-1.5.zip","src_id":"22816","5":"22816","creation_date":"1421737884","6":"1421737884"},{"0":"4815","vim_version":"7.3","1":"7.3","script_version":"v1.3","2":"v1.3","version_comment":"2014-01-11: v1.3\r\n\t- [verup] v1.3\r\n\t- [improve] provide '<NOP>\" special action to disable default keymap.\r\n\t- [improve] greatly improve overlay rendering with new pattern\r\n\t  compilation x2 faster now.\r\n2014-01-10:\r\n\t- [improve] disable trailing white space highlight internally.\r\n\t- [improve] performance and effectiveness improve by avoiding\r\n\t  unnecessary append blankline.\r\n\t- [improve] treat first_path() case as consistent manner.\r\n\t- [improve] eliminate invalid window at initial phrase","3":"2014-01-11: v1.3\r\n\t- [verup] v1.3\r\n\t- [improve] provide '<NOP>\" special action to disable default keymap.\r\n\t- [improve] greatly improve overlay rendering with new pattern\r\n\t  compilation x2 faster now.\r\n2014-01-10:\r\n\t- [improve] disable trailing white space highlight internally.\r\n\t- [improve] performance and effectiveness improve by avoiding\r\n\t  unnecessary append blankline.\r\n\t- [improve] treat first_path() case as consistent manner.\r\n\t- [improve] eliminate invalid window at initial phrase","package":"vim-choosewin-1.3.zip","4":"vim-choosewin-1.3.zip","src_id":"21306","5":"21306","creation_date":"1389417192","6":"1389417192"},{"0":"4815","vim_version":"7.3","1":"7.3","script_version":"v1.2","2":"v1.2","version_comment":"2014-01-09: v1.2\r\n\t- verup\r\n2014-01-09: v1.1\r\n\t- [improve] now undo history cleared when undolist is empty.\r\n\t- [improve] recover poslist properly in overlay mode\r\n\t- [bugfix] for buffer buftype=nowrite,nofile, buffer was not recovered\r\n\t  since &modified flag is ignored.","3":"2014-01-09: v1.2\r\n\t- verup\r\n2014-01-09: v1.1\r\n\t- [improve] now undo history cleared when undolist is empty.\r\n\t- [improve] recover poslist properly in overlay mode\r\n\t- [bugfix] for buffer buftype=nowrite,nofile, buffer was not recovered\r\n\t  since &modified flag is ignored.","package":"vim-choosewin-1.2.zip","4":"vim-choosewin-1.2.zip","src_id":"21298","5":"21298","creation_date":"1389270997","6":"1389270997"},{"0":"4815","vim_version":"7.3","1":"7.3","script_version":"v1.0","2":"v1.0","version_comment":"now stabilized new window overlay feature which completely emulate tmux's display-pain by using matchadd().\r\nsee https:\/\/github.com\/t9md\/vim-choosewin for gif animation.\r\n\r\n2014-01-08: v1.0\r\n\t- [improve] Add multibyte workaround.\r\n\t- [improve] now overlay not break since &conceallevel = 0 temporarily\r\n\t- [bugfix] validate valid winnum and number of label\r\n\t- [improve] disable fold, wrap, list adviced by manga-osyo.\r\n\t- [improve] separate keymap variable\r\n\t- [bugfix] properly clear label on tabswitch\r\n\t- [refactor] and stabilize\r\n2014-01-06:\r\n\t- [bugfix] Number of tab exceed length of |g:choosewin_tablabel| cause\r\n\t  error.\r\n\t- [bugfix] Experimental overlay caption break redo history.\r\n\t  now, keep undolist with |:rundo|, |:rundo|.\r\n2014-01-03:\r\n\t- [improve] cleanup highlight management.\r\n\t- [new] add experimental overlay window caption.\r\n2013-12-31:\r\n\t- [bugfixed] Number of tab exceed length of |g:choosewin_tablabel|\r\n\t  cause error.\r\n\t- [new-feature] last four char for |g:choosewin_tablabel|is used for\r\n\t  special tab excursion.\r\n\t- [bugfix] choosing tab and <Esc> don't revert original tab.\r\n2013-12-29:\r\n\t- now blinking cursor word at land so that easy to spot cursor.\r\n\t- [api-change] add auto-choose optional args for choowsewin#start()\r\n\t  suggested by hrsh7th","3":"now stabilized new window overlay feature which completely emulate tmux's display-pain by using matchadd().\r\nsee https:\/\/github.com\/t9md\/vim-choosewin for gif animation.\r\n\r\n2014-01-08: v1.0\r\n\t- [improve] Add multibyte workaround.\r\n\t- [improve] now overlay not break since &conceallevel = 0 temporarily\r\n\t- [bugfix] validate valid winnum and number of label\r\n\t- [improve] disable fold, wrap, list adviced by manga-osyo.\r\n\t- [improve] separate keymap variable\r\n\t- [bugfix] properly clear label on tabswitch\r\n\t- [refactor] and stabilize\r\n2014-01-06:\r\n\t- [bugfix] Number of tab exceed length of |g:choosewin_tablabel| cause\r\n\t  error.\r\n\t- [bugfix] Experimental overlay caption break redo history.\r\n\t  now, keep undolist with |:rundo|, |:rundo|.\r\n2014-01-03:\r\n\t- [improve] cleanup highlight management.\r\n\t- [new] add experimental overlay window caption.\r\n2013-12-31:\r\n\t- [bugfixed] Number of tab exceed length of |g:choosewin_tablabel|\r\n\t  cause error.\r\n\t- [new-feature] last four char for |g:choosewin_tablabel|is used for\r\n\t  special tab excursion.\r\n\t- [bugfix] choosing tab and <Esc> don't revert original tab.\r\n2013-12-29:\r\n\t- now blinking cursor word at land so that easy to spot cursor.\r\n\t- [api-change] add auto-choose optional args for choowsewin#start()\r\n\t  suggested by hrsh7th","package":"vim-choosewin-1.0.zip","4":"vim-choosewin-1.0.zip","src_id":"21290","5":"21290","creation_date":"1389188466","6":"1389188466"},{"0":"4815","vim_version":"7.3","1":"7.3","script_version":"0.8","2":"0.8","version_comment":"Now you can choose tab!\r\nYou can check animated GIF on\r\nhttps:\/\/github.com\/t9md\/vim-choosewin","3":"Now you can choose tab!\r\nYou can check animated GIF on\r\nhttps:\/\/github.com\/t9md\/vim-choosewin","package":"vim-choosewin-0.8.zip","4":"vim-choosewin-0.8.zip","src_id":"21255","5":"21255","creation_date":"1388329561","6":"1388329561"},{"0":"4815","vim_version":"7.3","1":"7.3","script_version":"0.6","2":"0.6","version_comment":"Initial upload","3":"Initial upload","package":"vim-choosewin-0.6.zip","4":"vim-choosewin-0.6.zip","src_id":"21250","5":"21250","creation_date":"1388227017","6":"1388227017"}]},"4814":{"script_id":"4814","0":"4814","script_name":"vim-howdoi","1":"vim-howdoi","script_type":"utility","2":"utility","summary":"Howdoi VIM Plugin","3":"Howdoi VIM Plugin","description":"A Vim frontend for howdoi, the awesome command line tool that lets you ask what you need and grabs the snippet of code from SO.\r\n\r\nPlease use the GitHub project for bug reports and feature suggestions:\r\nhttps:\/\/github.com\/laurentgoudet\/vim-howdoi\r\n\r\nFeatures:\r\n- Type your query and enter <CTRL-H> to get the code!\r\n- You can also use the plugin's menu entry under GUI\r\n- Overwrite the default mapping with map <WhatYouWant> <Plug>Howdoi\r\n\r\nRequirements:\r\n- Install howdoi if you haven't: pip install howdoi\r\n- You must also have vim compiled with +python support. You can check that using the command: vim --version | grep +python. Vim package in Ubuntu and it's derivatives comes with +python support.\r\n\r\nUsage\r\n- Write what your are looking for\r\n- Press <CTRL-H> to get the code!\r\n\r\nTroubleshooting\r\n- You'll maybe need LXML2 apt-get install python-lxml if howdoi compilation fails.\r\n\r\nLicense\r\n- This plugin is released under the WTFPLv2 License.","4":"A Vim frontend for howdoi, the awesome command line tool that lets you ask what you need and grabs the snippet of code from SO.\r\n\r\nPlease use the GitHub project for bug reports and feature suggestions:\r\nhttps:\/\/github.com\/laurentgoudet\/vim-howdoi\r\n\r\nFeatures:\r\n- Type your query and enter <CTRL-H> to get the code!\r\n- You can also use the plugin's menu entry under GUI\r\n- Overwrite the default mapping with map <WhatYouWant> <Plug>Howdoi\r\n\r\nRequirements:\r\n- Install howdoi if you haven't: pip install howdoi\r\n- You must also have vim compiled with +python support. You can check that using the command: vim --version | grep +python. Vim package in Ubuntu and it's derivatives comes with +python support.\r\n\r\nUsage\r\n- Write what your are looking for\r\n- Press <CTRL-H> to get the code!\r\n\r\nTroubleshooting\r\n- You'll maybe need LXML2 apt-get install python-lxml if howdoi compilation fails.\r\n\r\nLicense\r\n- This plugin is released under the WTFPLv2 License.","install_details":"","5":"","first_name":"Laurent","6":"Laurent","last_name":"Goudet","7":"Goudet","releases":[{"0":"4814","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"vim-howdoi-1.0.tar.gz","4":"vim-howdoi-1.0.tar.gz","src_id":"21244","5":"21244","creation_date":"1388125599","6":"1388125599"}]},"4813":{"script_id":"4813","0":"4813","script_name":"candyVirus.vim","1":"candyVirus.vim","script_type":"color scheme","2":"color scheme","summary":"An elegant dark 256 colors colorscheme for cterm","3":"An elegant dark 256 colors colorscheme for cterm","description":"CandyVirus is a 256 colors elegant colorscheme wrote for vim term. It has been mainly test over C, C++ and Shell Script files, but should also work fine as long as you have good syntax files.\r\nThe colorscheme has 2 versions, a light one and a dark one. One can switch from one to the other by using the CandyLight, CandyDark, and CadySwitch commands. (Dark by default)\r\n\r\nGithub: https:\/\/github.com\/ercolanelli-leo\/candyVirus.git","4":"CandyVirus is a 256 colors elegant colorscheme wrote for vim term. It has been mainly test over C, C++ and Shell Script files, but should also work fine as long as you have good syntax files.\r\nThe colorscheme has 2 versions, a light one and a dark one. One can switch from one to the other by using the CandyLight, CandyDark, and CadySwitch commands. (Dark by default)\r\n\r\nGithub: https:\/\/github.com\/ercolanelli-leo\/candyVirus.git","install_details":"First put the candyVirus.vim file in your ~\/.vim\/colors\/ folder\r\nThen add the following command to your ~\/.vimrc (without quotes) : 'colorscheme candyVirus'\r\nThe default mode is the dark one. To access the light one, add (without quotes) 'CandyLight'.\r\nYou may need to also add to your '~\/.vimrc' (still without quotes): 'set t_Co=256' to enable the 256 color display.","5":"First put the candyVirus.vim file in your ~\/.vim\/colors\/ folder\r\nThen add the following command to your ~\/.vimrc (without quotes) : 'colorscheme candyVirus'\r\nThe default mode is the dark one. To access the light one, add (without quotes) 'CandyLight'.\r\nYou may need to also add to your '~\/.vimrc' (still without quotes): 'set t_Co=256' to enable the 256 color display.","first_name":"Leo","6":"Leo","last_name":"Ercolanelli","7":"Ercolanelli","releases":[{"0":"4813","vim_version":"7.0","1":"7.0","script_version":"2.0","2":"2.0","version_comment":"The light version of the colorscheme is now completed.","3":"The light version of the colorscheme is now completed.","package":"candyVirus.vim","4":"candyVirus.vim","src_id":"21764","5":"21764","creation_date":"1397391486","6":"1397391486"},{"0":"4813","vim_version":"7.0","1":"7.0","script_version":"1.1","2":"1.1","version_comment":"Fixed the wrong color display on search.","3":"Fixed the wrong color display on search.","package":"candyVirus.vim","4":"candyVirus.vim","src_id":"21516","5":"21516","creation_date":"1392943610","6":"1392943610"},{"0":"4813","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"candyVirus.vim","4":"candyVirus.vim","src_id":"21242","5":"21242","creation_date":"1388079567","6":"1388079567"}]},"4812":{"script_id":"4812","0":"4812","script_name":"vim-sexp","1":"vim-sexp","script_type":"utility","2":"utility","summary":"Precision Editing for S-expressions","3":"Precision Editing for S-expressions","description":"Vim-sexp brings the Vim philosophy of precision editing to S-expressions.\r\n\r\nPlease see the home page at https:\/\/github.com\/guns\/vim-sexp for more details.","4":"Vim-sexp brings the Vim philosophy of precision editing to S-expressions.\r\n\r\nPlease see the home page at https:\/\/github.com\/guns\/vim-sexp for more details.","install_details":"","5":"","first_name":"Sung","6":"Sung","last_name":"Pae","7":"Pae","releases":[{"0":"4812","vim_version":"7.3","1":"7.3","script_version":"1","2":"1","version_comment":"Initial upload","3":"Initial upload","package":"vim-sexp.tar.gz","4":"vim-sexp.tar.gz","src_id":"21240","5":"21240","creation_date":"1388066776","6":"1388066776"}]},"4811":{"script_id":"4811","0":"4811","script_name":"vim-textobj-quote","1":"vim-textobj-quote","script_type":"utility","2":"utility","summary":"Extending Vim to better support typographic (curly) quote characters","3":"Extending Vim to better support typographic (curly) quote characters","description":"NOTE (02 Feb 2014) I've rewrote and renamed this project to \"vim-textobj-quote\" to emphasize its use as a text object. The former \"vim-quotable\" is deprecated but still available on github. -Reed\r\n\r\nWhile Vim is renown for its text manipulation capabilities, it nevertheless retains a bias towards ASCII that stretches back to its vi roots on Unix. This can limit the appeal of this powerful editor for those who prefer typographic characters like \u00e2\u0080\u009ccurly quotes\u00e2\u0080\u009d over \"straight quotes\" in the prose or documentation they write.\r\n\r\nFeatures of this plugin:\r\n\r\n* Automatic entry of \u00e2\u0080\u0098typographic quotes\u00e2\u0080\u0099 from the 'straight quote' keys\r\n* Motion support for typographic quote pairs\r\n* Matchit % matching for typographic quote pairs\r\n* User can define alternative typographic quote pairs\r\n* Replace quotes in existing text, including entire buffer\r\n\r\nThe latest version of plugin, including configuration details and a brief animated demo, can be found at: https:\/\/github.com\/reedes\/vim-textobj-quote","4":"NOTE (02 Feb 2014) I've rewrote and renamed this project to \"vim-textobj-quote\" to emphasize its use as a text object. The former \"vim-quotable\" is deprecated but still available on github. -Reed\r\n\r\nWhile Vim is renown for its text manipulation capabilities, it nevertheless retains a bias towards ASCII that stretches back to its vi roots on Unix. This can limit the appeal of this powerful editor for those who prefer typographic characters like \u00e2\u0080\u009ccurly quotes\u00e2\u0080\u009d over \"straight quotes\" in the prose or documentation they write.\r\n\r\nFeatures of this plugin:\r\n\r\n* Automatic entry of \u00e2\u0080\u0098typographic quotes\u00e2\u0080\u0099 from the 'straight quote' keys\r\n* Motion support for typographic quote pairs\r\n* Matchit % matching for typographic quote pairs\r\n* User can define alternative typographic quote pairs\r\n* Replace quotes in existing text, including entire buffer\r\n\r\nThe latest version of plugin, including configuration details and a brief animated demo, can be found at: https:\/\/github.com\/reedes\/vim-textobj-quote","install_details":"Install using Pathogen, Vundle, Neobundle, or your favorite Vim package manager.\r\n\r\nTo support typographic characters as text objects, the following dependency should be installed. (Strongly recommended.)\r\n\r\nvim-textobject-user - a Vim plugin to create your own text objects without pain","5":"Install using Pathogen, Vundle, Neobundle, or your favorite Vim package manager.\r\n\r\nTo support typographic characters as text objects, the following dependency should be installed. (Strongly recommended.)\r\n\r\nvim-textobject-user - a Vim plugin to create your own text objects without pain","first_name":"Reed","6":"Reed","last_name":"Esau","7":"Esau","releases":[{"0":"4811","vim_version":"7.3","1":"7.3","script_version":"0.7","2":"0.7","version_comment":"Command naming now more consistent.","3":"Command naming now more consistent.","package":"vim-textobj-quote-0.7.zip","4":"vim-textobj-quote-0.7.zip","src_id":"21447","5":"21447","creation_date":"1391901188","6":"1391901188"},{"0":"4811","vim_version":"7.3","1":"7.3","script_version":"0.6","2":"0.6","version_comment":"Rewrite that implements previous character detection with regex.","3":"Rewrite that implements previous character detection with regex.","package":"vim-textobj-quote-0.6.zip","4":"vim-textobj-quote-0.6.zip","src_id":"21446","5":"21446","creation_date":"1391887960","6":"1391887960"},{"0":"4811","vim_version":"7.3","1":"7.3","script_version":"0.5","2":"0.5","version_comment":"Add bulk replace feature. See README for details.","3":"Add bulk replace feature. See README for details.","package":"vim-quotable-0.5.zip","4":"vim-quotable-0.5.zip","src_id":"21344","5":"21344","creation_date":"1390080830","6":"1390080830"},{"0":"4811","vim_version":"7.3","1":"7.3","script_version":"0.4","2":"0.4","version_comment":"Performance optimizations for educate mode; removed advanced educate mode due to incompatibilities with autoformat.","3":"Performance optimizations for educate mode; removed advanced educate mode due to incompatibilities with autoformat.","package":"vim-quotable-0.4.zip","4":"vim-quotable-0.4.zip","src_id":"21323","5":"21323","creation_date":"1389761521","6":"1389761521"},{"0":"4811","vim_version":"7.3","1":"7.3","script_version":"0.3","2":"0.3","version_comment":"Fixed problem with educating quotes not working with :set virtualedit=all","3":"Fixed problem with educating quotes not working with :set virtualedit=all","package":"vim-quotable-0.3.zip","4":"vim-quotable-0.3.zip","src_id":"21286","5":"21286","creation_date":"1389116953","6":"1389116953"},{"0":"4811","vim_version":"7.3","1":"7.3","script_version":"0.2","2":"0.2","version_comment":"Bugfixes and new advanced mode for educating quotes that provides additional context.","3":"Bugfixes and new advanced mode for educating quotes that provides additional context.","package":"vim-quotable.zip","4":"vim-quotable.zip","src_id":"21256","5":"21256","creation_date":"1388361843","6":"1388361843"},{"0":"4811","vim_version":"7.3","1":"7.3","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"vim-quotable.zip","4":"vim-quotable.zip","src_id":"21239","5":"21239","creation_date":"1388039982","6":"1388039982"}]},"4810":{"script_id":"4810","0":"4810","script_name":"LEF_DEF_syntax","1":"LEF_DEF_syntax","script_type":"syntax","2":"syntax","summary":"Design\/Library Exchange Formats syntax files","3":"Design\/Library Exchange Formats syntax files","description":"This files are Design\/Library Exchange Formats (DEF\/LEF) syntax files.","4":"This files are Design\/Library Exchange Formats (DEF\/LEF) syntax files.","install_details":"How to install DEF (Design Exchange Format) and LEF (Library Exchange Format) syntax files.\r\n\r\nDownload and unzip LEF_DEF_syntax_for_VIM.rar file\r\n\r\nFor UNIX:\r\n 1. Copy syntax\/* to \/home\/<username>\/.vim\/syntax\/\r\n 2. Copy ftdetect\/* to \/home\/<username>\/.vim\/ftdetect\/\r\n 3. Add to your .vimrc file following lines:\r\n    autocmd FileType lef so ~\/.vim\/syntax\/lef.vim\r\n    autocmd FileType def so ~\/.vim\/syntax\/def.vim\r\n\r\nFor Windows:\r\n 1. Copy syntax\/* to C:\\Program Files (x86)\\Vim\\vimfiles\\syntax\\\r\n 2. Copy ftdetect\/* to C:\\Program Files (x86)\\Vim\\vimfiles\\ftdetect\\","5":"How to install DEF (Design Exchange Format) and LEF (Library Exchange Format) syntax files.\r\n\r\nDownload and unzip LEF_DEF_syntax_for_VIM.rar file\r\n\r\nFor UNIX:\r\n 1. Copy syntax\/* to \/home\/<username>\/.vim\/syntax\/\r\n 2. Copy ftdetect\/* to \/home\/<username>\/.vim\/ftdetect\/\r\n 3. Add to your .vimrc file following lines:\r\n    autocmd FileType lef so ~\/.vim\/syntax\/lef.vim\r\n    autocmd FileType def so ~\/.vim\/syntax\/def.vim\r\n\r\nFor Windows:\r\n 1. Copy syntax\/* to C:\\Program Files (x86)\\Vim\\vimfiles\\syntax\\\r\n 2. Copy ftdetect\/* to C:\\Program Files (x86)\\Vim\\vimfiles\\ftdetect\\","first_name":"Levon","6":"Levon","last_name":"Ohanyan","7":"Ohanyan","releases":[{"0":"4810","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"LEF_DEF_syntax_for_VIM.rar","4":"LEF_DEF_syntax_for_VIM.rar","src_id":"21234","5":"21234","creation_date":"1387904403","6":"1387904403"}]},"4809":{"script_id":"4809","0":"4809","script_name":"vim-sneak","1":"vim-sneak","script_type":"utility","2":"utility","summary":"motion improved","3":"motion improved","description":"Sneak is a Vim plugin that enables you to move to any location specified by two characters. It works across multiple lines; with operators (including repeat .); and in visual mode. Move to the next or previous match via ; or ,. Move to the nth match by prefixing ; or , with a [count].\r\n\r\nThe plugin chooses sane defaults, which are easily changed via <Plug> mappings. See :help sneak for options and details.\r\n\r\nLatest version and full details are here: \r\n\r\nhttps:\/\/github.com\/justinmk\/vim-sneak\r\n\r\n","4":"Sneak is a Vim plugin that enables you to move to any location specified by two characters. It works across multiple lines; with operators (including repeat .); and in visual mode. Move to the next or previous match via ; or ,. Move to the nth match by prefixing ; or , with a [count].\r\n\r\nThe plugin chooses sane defaults, which are easily changed via <Plug> mappings. See :help sneak for options and details.\r\n\r\nLatest version and full details are here: \r\n\r\nhttps:\/\/github.com\/justinmk\/vim-sneak\r\n\r\n","install_details":"","5":"","first_name":"Justin","6":"Justin","last_name":"Keyes","7":"Keyes","releases":[{"0":"4809","vim_version":"7.2","1":"7.2","script_version":"1.7.3","2":"1.7.3","version_comment":"**New features:**\r\n- support for mbyte\/lang keymaps\r\n- new option to disable \"clever-s\": `g:sneak#s_next`\r\n- \"clever-s\" (g:sneak#s_next) is now disabled by default\r\n\r\n**New features for *streak-mode*:**\r\n- intuitive, reliable support for operators\r\n- intuitive, reliable support for dot-repeat (requires repeat.vim)\r\n- handle ctrl-c like <esc>\r\n- allow S\/Z\/f\/F\/t\/T in target labels\r\n- put 's' at the start of target_labels\r\n- provide sneak#is_sneaking() function to allow flexible mappings, for example:\r\n      nmap <expr> s sneak#is_sneaking() ? '<Plug>SneakNext' : 's'\r\n- provide <Plug>(SneakStreak*) in visual-mode and operator-pending mode\r\n\r\n**Bug fixes:**\r\n- handle operator-pending on ; , and [count]\r\n- indentLine compatibility \/ don't highlight concealed characters in other windows\r\n- fixed inclusive (f), exclusive (t) behavior\r\n- fixed <Plug>(SneakStreak) mapping\r\n- handle very long wrapped lines\r\n- don't highlight same buffer in other windows\r\n- more robust dot-repeat after streak-mode operation\r\n","3":"**New features:**\r\n- support for mbyte\/lang keymaps\r\n- new option to disable \"clever-s\": `g:sneak#s_next`\r\n- \"clever-s\" (g:sneak#s_next) is now disabled by default\r\n\r\n**New features for *streak-mode*:**\r\n- intuitive, reliable support for operators\r\n- intuitive, reliable support for dot-repeat (requires repeat.vim)\r\n- handle ctrl-c like <esc>\r\n- allow S\/Z\/f\/F\/t\/T in target labels\r\n- put 's' at the start of target_labels\r\n- provide sneak#is_sneaking() function to allow flexible mappings, for example:\r\n      nmap <expr> s sneak#is_sneaking() ? '<Plug>SneakNext' : 's'\r\n- provide <Plug>(SneakStreak*) in visual-mode and operator-pending mode\r\n\r\n**Bug fixes:**\r\n- handle operator-pending on ; , and [count]\r\n- indentLine compatibility \/ don't highlight concealed characters in other windows\r\n- fixed inclusive (f), exclusive (t) behavior\r\n- fixed <Plug>(SneakStreak) mapping\r\n- handle very long wrapped lines\r\n- don't highlight same buffer in other windows\r\n- more robust dot-repeat after streak-mode operation\r\n","package":"vim-sneak-1.7.3.zip","4":"vim-sneak-1.7.3.zip","src_id":"21703","5":"21703","creation_date":"1396330528","6":"1396330528"},{"0":"4809","vim_version":"7.2","1":"7.2","script_version":"1.3","2":"1.3","version_comment":"Initial upload","3":"Initial upload","package":"vim-sneak-1.3.zip","4":"vim-sneak-1.3.zip","src_id":"21233","5":"21233","creation_date":"1387871325","6":"1387871325"}]},"4808":{"script_id":"4808","0":"4808","script_name":"auto-pairs-gentle","1":"auto-pairs-gentle","script_type":"utility","2":"utility","summary":"Gentle version of Auto Pairs plugin: Insert or delete brackets, parens in pair","3":"Gentle version of Auto Pairs plugin: Insert or delete brackets, parens in pair","description":"This plugin is a fork of AutoPairs. ( vimscript #3599 )\r\n\r\nAutoPairs is surely great plugin, but, to me, it behaves too aggressively: if\r\nyour cursor is on \")\" char, and you type \")\", cursor ALWAYS jumps over the \")\"\r\ninstead of inserting new char.\r\n\r\n(And, in \"fly mode\", AutoPairs is even much more \"aggressive\"... \r\nSo if you like \"fly mode\" of AutoPairs, then you definitely don't need for\r\nauto-pairs-gentle plugin)\r\n\r\nPersonally I want the plugin to meddle with it as little as possible. Ideal behavior for\r\nme is that plugin should jump only over those chars, pairs for whose were\r\ninserted automatically: sometimes, and not so rarely, I really need to insert\r\nsome brace before another brace, and aggressive jumping over all pair chars\r\nannoyed me so much that I had to completely get rid of AutoPairs until I found\r\nthe way to improve it.\r\n\r\nFirst of all, I must say that I have written a patch for existing AutoPairs\r\nplugin that just adds new option, and default behavior was not changed at all.\r\nI have sent pull-request to the author\r\n( https:\/\/github.com\/jiangmiao\/auto-pairs\/pull\/71 ) , but he answered that my\r\nsolution \"is not current plugin way\", and disagreed to merge.\r\n\r\nI believe that highly configurable tools are generally good, and so, it worth\r\nto add a new option to an existing tool instead of make a fork, but now, to\r\nmake a fork is the only way I'm left with.\r\n\r\n\r\nSo, here's an explanation of the behavior of new plugin AutoPairsGentle.\r\n\r\nConsider an example (\"|\" char indicates cursor position):\r\n\r\nI have an existing expression (that I typed some time ago, not just now):\r\n\r\n                  (a * b|)\r\n\r\nI type:\r\n\r\n                   * (\r\n\r\nResult:\r\n\r\n                  (a * b * (|))\r\n\r\nI type:\r\n\r\n                  c + d\r\n\r\nResult:\r\n\r\n                  (a * b * (c + d|))\r\n\r\nI type:\r\n\r\n                  )\r\n\r\nResult:\r\n\r\n                  (a * b * (c + d)|)\r\n\r\nNote that cursor just jumped over the \")\" since it was inserted automatically.\r\nBut if I type \")\" again, new char \")\" will be inserted, instead of jumping\r\nover the last \")\"! Because last parens was not typed just now.\r\nBut if you type several nested parens, of course cursor will jump over all of them.\r\nAnd not more.\r\n\r\nThe same is for any other pair character.\r\n\r\nThis is how actually modern IDEs editors work (I have checked Eclipse and\r\nNetBeans), and this algorithm is really useful.\r\n\r\nIf you don't like this behavior, you surely don't need this plugin.\r\n\r\nHow does it work: actually, applied solution is very simple: plugin remembers\r\nhow many pairs were inserted, and jumps only over this count of pair chars. When\r\nuser leaves insert mode, pairs count is reset.\r\n\r\n\r\n\r\nNOTE 1: default behavior of AutoPairsGentle is the same as original AutoPairs,\r\nso, to make the algorithm above work, you should define an option in your\r\nvimrc:\r\n\r\nlet g:AutoPairsUseInsertedCount = 1\r\n\r\nNOTE 2: this option is not compatible with \"fly mode\" ( g:AutoPairsFlyMode ),\r\nbut I believe that if you like fly mode, then you definitely do not need for\r\nAutoPairsGentle, because \"fly mode\" is much more \"aggressive\" than default\r\nbehavior.\r\n\r\n","4":"This plugin is a fork of AutoPairs. ( vimscript #3599 )\r\n\r\nAutoPairs is surely great plugin, but, to me, it behaves too aggressively: if\r\nyour cursor is on \")\" char, and you type \")\", cursor ALWAYS jumps over the \")\"\r\ninstead of inserting new char.\r\n\r\n(And, in \"fly mode\", AutoPairs is even much more \"aggressive\"... \r\nSo if you like \"fly mode\" of AutoPairs, then you definitely don't need for\r\nauto-pairs-gentle plugin)\r\n\r\nPersonally I want the plugin to meddle with it as little as possible. Ideal behavior for\r\nme is that plugin should jump only over those chars, pairs for whose were\r\ninserted automatically: sometimes, and not so rarely, I really need to insert\r\nsome brace before another brace, and aggressive jumping over all pair chars\r\nannoyed me so much that I had to completely get rid of AutoPairs until I found\r\nthe way to improve it.\r\n\r\nFirst of all, I must say that I have written a patch for existing AutoPairs\r\nplugin that just adds new option, and default behavior was not changed at all.\r\nI have sent pull-request to the author\r\n( https:\/\/github.com\/jiangmiao\/auto-pairs\/pull\/71 ) , but he answered that my\r\nsolution \"is not current plugin way\", and disagreed to merge.\r\n\r\nI believe that highly configurable tools are generally good, and so, it worth\r\nto add a new option to an existing tool instead of make a fork, but now, to\r\nmake a fork is the only way I'm left with.\r\n\r\n\r\nSo, here's an explanation of the behavior of new plugin AutoPairsGentle.\r\n\r\nConsider an example (\"|\" char indicates cursor position):\r\n\r\nI have an existing expression (that I typed some time ago, not just now):\r\n\r\n                  (a * b|)\r\n\r\nI type:\r\n\r\n                   * (\r\n\r\nResult:\r\n\r\n                  (a * b * (|))\r\n\r\nI type:\r\n\r\n                  c + d\r\n\r\nResult:\r\n\r\n                  (a * b * (c + d|))\r\n\r\nI type:\r\n\r\n                  )\r\n\r\nResult:\r\n\r\n                  (a * b * (c + d)|)\r\n\r\nNote that cursor just jumped over the \")\" since it was inserted automatically.\r\nBut if I type \")\" again, new char \")\" will be inserted, instead of jumping\r\nover the last \")\"! Because last parens was not typed just now.\r\nBut if you type several nested parens, of course cursor will jump over all of them.\r\nAnd not more.\r\n\r\nThe same is for any other pair character.\r\n\r\nThis is how actually modern IDEs editors work (I have checked Eclipse and\r\nNetBeans), and this algorithm is really useful.\r\n\r\nIf you don't like this behavior, you surely don't need this plugin.\r\n\r\nHow does it work: actually, applied solution is very simple: plugin remembers\r\nhow many pairs were inserted, and jumps only over this count of pair chars. When\r\nuser leaves insert mode, pairs count is reset.\r\n\r\n\r\n\r\nNOTE 1: default behavior of AutoPairsGentle is the same as original AutoPairs,\r\nso, to make the algorithm above work, you should define an option in your\r\nvimrc:\r\n\r\nlet g:AutoPairsUseInsertedCount = 1\r\n\r\nNOTE 2: this option is not compatible with \"fly mode\" ( g:AutoPairsFlyMode ),\r\nbut I believe that if you like fly mode, then you definitely do not need for\r\nAutoPairsGentle, because \"fly mode\" is much more \"aggressive\" than default\r\nbehavior.\r\n\r\n","install_details":"Install it as usual, and don't forget to set in your vimrc:\r\n\r\nlet g:AutoPairsUseInsertedCount = 1\r\n\r\nto make it gentle.","5":"Install it as usual, and don't forget to set in your vimrc:\r\n\r\nlet g:AutoPairsUseInsertedCount = 1\r\n\r\nto make it gentle.","first_name":"Dmitry","6":"Dmitry","last_name":"Frank","7":"Frank","releases":[{"0":"4808","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"auto-pairs-gentle.zip","4":"auto-pairs-gentle.zip","src_id":"21230","5":"21230","creation_date":"1387797200","6":"1387797200"}]},"4807":{"script_id":"4807","0":"4807","script_name":"Accurev diff tool","1":"Accurev diff tool","script_type":"utility","2":"utility","summary":"Tool to view the changes that you make in accurev workspace","3":"Tool to view the changes that you make in accurev workspace","description":"Tool to view the changes between your version and backed version or basis version.\r\nThere are four commands.\r\nAd      - View the difference between modified file and last kept file\r\nAdbs  - View the difference between modified file and last updated version\r\nAdbk  - View the difference between modified file and backed file in backed stream\r\nAdc    - Exit the diff view","4":"Tool to view the changes between your version and backed version or basis version.\r\nThere are four commands.\r\nAd      - View the difference between modified file and last kept file\r\nAdbs  - View the difference between modified file and last updated version\r\nAdbk  - View the difference between modified file and backed file in backed stream\r\nAdc    - Exit the diff view","install_details":"Copy this script to .vim\/plugin on linux.","5":"Copy this script to .vim\/plugin on linux.","first_name":"paul","6":"paul","last_name":"pan","7":"pan","releases":[{"0":"4807","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"accurevdiff.vim","4":"accurevdiff.vim","src_id":"21219","5":"21219","creation_date":"1387521076","6":"1387521076"}]},"4806":{"script_id":"4806","0":"4806","script_name":"vim-systemverilog","1":"vim-systemverilog","script_type":"ftplugin","2":"ftplugin","summary":"system verilog indent, syntax, and ftdetect","3":"system verilog indent, syntax, and ftdetect","description":"This script detects system verilog files, does indents, and syntax highlighting.\r\n\r\n\r\nThis is the \\\\\\\\\\\\\\\"bug fix\\\\\\\\\\\\\\\" version of \\\\\\\\\\\\\\\"verilog_systemverilog.vim\\\\\\\\\\\\\\\" vimscript #1586 created by Amit Sethi.\r\n\r\nWith this fixed version, the key \\\\\\\\\\\\\\\"%\\\\\\\\\\\\\\\" (matchit.vim) works for Verilog\/SystemVerilog files, which doesn\\\\\\\\\\\\\\'t work for the original version.\r\n\r\n\r\n\r\nNew features and changes since branch\r\n\r\nAdded folding expression:\r\nCurrently folds functions, tasks\r\n\r\nAdded matchit words for matchit.vim\r\n\r\ngithub: https:\/\/github.com\/cazador481\/vim-systemverilog","4":"This script detects system verilog files, does indents, and syntax highlighting.\r\n\r\n\r\nThis is the \\\\\\\\\\\\\\\"bug fix\\\\\\\\\\\\\\\" version of \\\\\\\\\\\\\\\"verilog_systemverilog.vim\\\\\\\\\\\\\\\" vimscript #1586 created by Amit Sethi.\r\n\r\nWith this fixed version, the key \\\\\\\\\\\\\\\"%\\\\\\\\\\\\\\\" (matchit.vim) works for Verilog\/SystemVerilog files, which doesn\\\\\\\\\\\\\\'t work for the original version.\r\n\r\n\r\n\r\nNew features and changes since branch\r\n\r\nAdded folding expression:\r\nCurrently folds functions, tasks\r\n\r\nAdded matchit words for matchit.vim\r\n\r\ngithub: https:\/\/github.com\/cazador481\/vim-systemverilog","install_details":"","5":"","first_name":"Edward","6":"Edward","last_name":"Ash","7":"Ash","releases":[{"0":"4806","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"systemverilog.tar.gz","4":"systemverilog.tar.gz","src_id":"21218","5":"21218","creation_date":"1387490466","6":"1387490466"}]},"4805":{"script_id":"4805","0":"4805","script_name":"MultiWordComplete","1":"MultiWordComplete","script_type":"utility","2":"utility","summary":"Insert mode completion that completes a sequence of words based on anchors.","3":"Insert mode completion that completes a sequence of words based on anchors.","description":"DESCRIPTION\r\nThe built-in insert mode completion completes single words, and one can copy\r\nthe words following the previous expansion one-by-one. (But that is cumbersome\r\nand doesn't scale when there are many alternatives.)\r\nThis plugin offers completion of sequences of words, i.e. everything separated\r\nby whitespace, non-keyword characters or the start \/ end of line, based on the\r\ntyped first letter of each word. With this, one can quickly complete entire\r\nphrases; for example, \"imc\" completes to \"insert mode completion\", and \"\/ulb\"\r\ncompletes to \"\/usr\/local\/bin\".\r\n\r\nSEE ALSO\r\n- CamelCaseComplete.vim (vimscript #3915) provides a similar completion, but\r\n  the anchor characters must be the start fragments of CamelCaseWords or\r\n  underscore_words.\r\n- Check out the CompleteHelper.vim plugin page (vimscript #3914) for a full\r\n  list of insert mode completions powered by it.\r\n\r\nUSAGE\r\nIn insert mode, type all initial letters of the requested phrase, and invoke\r\nthe multi-word completion via CTRL-X w.\r\nYou can then search forward and backward via CTRL-N \/ CTRL-P, as usual.\r\n\r\nCTRL-X w                Find matches for multiple words which begin with the\r\n                        typed letters in front of the cursor. The 'ignorecase'\r\n                        and 'smartcase' settings apply. If no matches were\r\n                        found that way, a case-insensitive search is tried as\r\n                        a fallback. (So, unless you care about a minimum\r\n                        number of matches and search speed, you can be sloppy\r\n                        with the case of the typed letters.)\r\n                        The sequence of words can span multiple lines;\r\n                        newlines are removed in the completion results.\r\n\r\n                        Non-alphabetic keyword characters (e.g. numbers, \"_\"\r\n                        in the default 'iskeyword' setting) can be inserted\r\n                        into the completion base to force inclusion of these,\r\n                        e.g. both \"mf\" and \"mf_b\" complete to \"my foo_bar\",\r\n                        but the latter excludes \"my foobar\" and \"my foo_quux\".\r\n                        An alphabetic anchor following a non-alphabetic anchor\r\n                        must match immediately after the non-alphabetic\r\n                        letter, not in the next word. Thus, mentally parse the\r\n                        base \"mf_b\" as \"m\", \"f\", \"_b\".\r\n                        In addition, non-alphabetic keyword characters match\r\n                        at a start of a word, too. For example, \"f2s\" matches\r\n                        both \"foobar 2000 system\" (\"2\" matching like an\r\n                        alphabetic character) and \"foo2sam\" (\"2\" matching\r\n                        according to the special rule for non-alphabetic\r\n                        characters).","4":"DESCRIPTION\r\nThe built-in insert mode completion completes single words, and one can copy\r\nthe words following the previous expansion one-by-one. (But that is cumbersome\r\nand doesn't scale when there are many alternatives.)\r\nThis plugin offers completion of sequences of words, i.e. everything separated\r\nby whitespace, non-keyword characters or the start \/ end of line, based on the\r\ntyped first letter of each word. With this, one can quickly complete entire\r\nphrases; for example, \"imc\" completes to \"insert mode completion\", and \"\/ulb\"\r\ncompletes to \"\/usr\/local\/bin\".\r\n\r\nSEE ALSO\r\n- CamelCaseComplete.vim (vimscript #3915) provides a similar completion, but\r\n  the anchor characters must be the start fragments of CamelCaseWords or\r\n  underscore_words.\r\n- Check out the CompleteHelper.vim plugin page (vimscript #3914) for a full\r\n  list of insert mode completions powered by it.\r\n\r\nUSAGE\r\nIn insert mode, type all initial letters of the requested phrase, and invoke\r\nthe multi-word completion via CTRL-X w.\r\nYou can then search forward and backward via CTRL-N \/ CTRL-P, as usual.\r\n\r\nCTRL-X w                Find matches for multiple words which begin with the\r\n                        typed letters in front of the cursor. The 'ignorecase'\r\n                        and 'smartcase' settings apply. If no matches were\r\n                        found that way, a case-insensitive search is tried as\r\n                        a fallback. (So, unless you care about a minimum\r\n                        number of matches and search speed, you can be sloppy\r\n                        with the case of the typed letters.)\r\n                        The sequence of words can span multiple lines;\r\n                        newlines are removed in the completion results.\r\n\r\n                        Non-alphabetic keyword characters (e.g. numbers, \"_\"\r\n                        in the default 'iskeyword' setting) can be inserted\r\n                        into the completion base to force inclusion of these,\r\n                        e.g. both \"mf\" and \"mf_b\" complete to \"my foo_bar\",\r\n                        but the latter excludes \"my foobar\" and \"my foo_quux\".\r\n                        An alphabetic anchor following a non-alphabetic anchor\r\n                        must match immediately after the non-alphabetic\r\n                        letter, not in the next word. Thus, mentally parse the\r\n                        base \"mf_b\" as \"m\", \"f\", \"_b\".\r\n                        In addition, non-alphabetic keyword characters match\r\n                        at a start of a word, too. For example, \"f2s\" matches\r\n                        both \"foobar 2000 system\" (\"2\" matching like an\r\n                        alphabetic character) and \"foo2sam\" (\"2\" matching\r\n                        according to the special rule for non-alphabetic\r\n                        characters).","install_details":"INSTALLATION\r\nThe code is hosted in a Git repo at\r\n    https:\/\/github.com\/inkarkat\/vim-MultiWordComplete\r\nYou can use your favorite plugin manager, or \"git clone\" into a directory used\r\nfor Vim packages. Releases are on the \"stable\" branch, the latest unstable\r\ndevelopment snapshot on \"master\".\r\n\r\nThis script is also packaged as a vimball. If you have the \"gunzip\"\r\ndecompressor in your PATH, simply edit the *.vmb.gz package in Vim; otherwise,\r\ndecompress the archive first, e.g. using WinZip. Inside Vim, install by\r\nsourcing the vimball or via the :UseVimball command.\r\n    vim MultiWordComplete*.vmb.gz\r\n    :so %\r\nTo uninstall, use the :RmVimball command.\r\n\r\nDEPENDENCIES\r\n- Requires Vim 7.0 or higher.\r\n- Requires the ingo-library.vim plugin (vimscript #4433), version 1.010 or\r\n  higher.\r\n- Requires the CompleteHelper.vim plugin (vimscript #3914), version 1.40 or\r\n  higher.\r\n\r\nCONFIGURATION\r\nFor a permanent configuration, put the following commands into your vimrc:\r\n\r\nBy default, the 'complete' option controls which buffers will be scanned for\r\ncompletion candidates. You can override that either for the entire plugin, or\r\nonly for particular buffers; see CompleteHelper_complete for supported\r\nvalues.\r\n    let g:MultiWordComplete_complete = '.,w,b,u'\r\n\r\nTo disable the removal of the (mostly useless) completion base when aborting\r\nwith <Esc> while there are no matches:\r\n    let g:MultiWordComplete_FindStartMark = ''\r\n\r\nIf you want to use a different mapping, map your keys to the\r\n<Plug>(MultiWordComplete) mapping target _before_ sourcing the script (e.g.\r\nin your vimrc):\r\n    imap <C-x>w <Plug>(MultiWordComplete)<Plug>(MultiWordPostComplete)","5":"INSTALLATION\r\nThe code is hosted in a Git repo at\r\n    https:\/\/github.com\/inkarkat\/vim-MultiWordComplete\r\nYou can use your favorite plugin manager, or \"git clone\" into a directory used\r\nfor Vim packages. Releases are on the \"stable\" branch, the latest unstable\r\ndevelopment snapshot on \"master\".\r\n\r\nThis script is also packaged as a vimball. If you have the \"gunzip\"\r\ndecompressor in your PATH, simply edit the *.vmb.gz package in Vim; otherwise,\r\ndecompress the archive first, e.g. using WinZip. Inside Vim, install by\r\nsourcing the vimball or via the :UseVimball command.\r\n    vim MultiWordComplete*.vmb.gz\r\n    :so %\r\nTo uninstall, use the :RmVimball command.\r\n\r\nDEPENDENCIES\r\n- Requires Vim 7.0 or higher.\r\n- Requires the ingo-library.vim plugin (vimscript #4433), version 1.010 or\r\n  higher.\r\n- Requires the CompleteHelper.vim plugin (vimscript #3914), version 1.40 or\r\n  higher.\r\n\r\nCONFIGURATION\r\nFor a permanent configuration, put the following commands into your vimrc:\r\n\r\nBy default, the 'complete' option controls which buffers will be scanned for\r\ncompletion candidates. You can override that either for the entire plugin, or\r\nonly for particular buffers; see CompleteHelper_complete for supported\r\nvalues.\r\n    let g:MultiWordComplete_complete = '.,w,b,u'\r\n\r\nTo disable the removal of the (mostly useless) completion base when aborting\r\nwith <Esc> while there are no matches:\r\n    let g:MultiWordComplete_FindStartMark = ''\r\n\r\nIf you want to use a different mapping, map your keys to the\r\n<Plug>(MultiWordComplete) mapping target _before_ sourcing the script (e.g.\r\nin your vimrc):\r\n    imap <C-x>w <Plug>(MultiWordComplete)<Plug>(MultiWordPostComplete)","first_name":"Ingo","6":"Ingo","last_name":"Karkat","7":"Karkat","releases":[{"0":"4805","vim_version":"7.0","1":"7.0","script_version":"1.01","2":"1.01","version_comment":"- Make repeat across lines work.\r\n- FIX: Avoid \"E121: Undefined variable: s:isNoMatches\" when triggering the completion for the first time without a valid base.\r\n- Remove default g:MultiWordComplete_complete configuration and default to 'complete' option value instead.\r\n- Remove superfluous duplicate :imap for default mapping. *** You need to update to CompleteHelper.vim (vimscript #3914) version 1.40! ***","3":"- Make repeat across lines work.\r\n- FIX: Avoid \"E121: Undefined variable: s:isNoMatches\" when triggering the completion for the first time without a valid base.\r\n- Remove default g:MultiWordComplete_complete configuration and default to 'complete' option value instead.\r\n- Remove superfluous duplicate :imap for default mapping. *** You need to update to CompleteHelper.vim (vimscript #3914) version 1.40! ***","package":"MultiWordComplete-1.01.vmb.gz","4":"MultiWordComplete-1.01.vmb.gz","src_id":"26422","5":"26422","creation_date":"1552877629","6":"1552877629"},{"0":"4805","vim_version":"7.0","1":"7.0","script_version":"1.00","2":"1.00","version_comment":"Initial upload","3":"Initial upload","package":"MultiWordComplete-1.00.vmb.gz","4":"MultiWordComplete-1.00.vmb.gz","src_id":"21217","5":"21217","creation_date":"1387451423","6":"1387451423"}]},"4804":{"script_id":"4804","0":"4804","script_name":"InnerFragmentComplete","1":"InnerFragmentComplete","script_type":"utility","2":"utility","summary":"Insert mode completion based on fragments inside words.","3":"Insert mode completion based on fragments inside words.","description":"DESCRIPTION\r\nThe built-in insert mode completion i_CTRL-N searches for entire keywords.\r\nOften, variable names share many identical fragments, but if you want to\r\ncomplete from fragments inside of variables (e.g. \"KeyValue\" from\r\n\"SpecialKeyValue\"), it won't work, because the usual completions only offer\r\nwhole keyword matches.\r\n\r\nSEE ALSO\r\n- The anchoring to individual fragment characters is re-used from\r\n  CamelCaseComplete (vimscript #3915), but applied here only to fragments\r\n  inside CamelCaseWords or underscore_words, not whole words.\r\n- BidiComplete (vimscript #4658) can complete inner (or leftmost) fragments\r\n  when there's already a completion base after the cursor.\r\n- Check out the CompleteHelper.vim plugin page (vimscript #3914) for a full\r\n  list of insert mode completions powered by it.\r\n\r\nUSAGE\r\nIn insert mode, invoke the inner fragment completion via CTRL-X i\r\nYou can then search forward and backward via CTRL-N \/ CTRL-P, as usual.\r\n\r\nCTRL-X i                Find matches for inner fragments. It first searches\r\n                        inside CamelCaseWords and underscore_words, either for\r\n                        matches of the keyword characters before the cursor at\r\n                        the inner fragment start, or for fragments whose\r\n                        individual words begin with the typed letters in front\r\n                        of the cursor. (The latter requires the optional\r\n                        CamelCaseComplete.vim plugin, and then works like\r\n                        with the strict i_CTRL-X_CTRL-C completion.)\r\n                        The completion base starts with the first uppercase\r\n                        character before the cursor (so \"myCust\" would find\r\n                        fragments starting with \"Cust\", e.g. in\r\n                        \"SpecialCustomer\"), or the keywords (excluding the\r\n                        underscore character, to be able to trigger completion\r\n                        inside an underscore_word) before the cursor. If the\r\n                        first keyword character is lowercase, the inner\r\n                        CamelCase matches will be converted to start\r\n                        lowercase, too.\r\n                        If there is a fragment before the completion base\r\n                        (e.g. \"My\" in \"MyCust\", or \"end_\" in \"end_foo\") the\r\n                        completion not only offers matching inner fragments,\r\n                        but also the complete word match, in order to complete\r\n                        prefixed new words with existing full words.\r\n                        For CamelCaseWord fragments, matches at the start of a\r\n                        CamelCaseWord are also valid, as long as it's not the\r\n                        entire CamelCaseWord that is matched (e.g. \"CC\"\r\n                        matches \"CamelCase\" in \"CamelCaseWord\").\r\n\r\n                        If that doesn't find any matches, a fallback search\r\n                        will pick up base matches anywhere inside a word (e.g.\r\n                        \"comp\" will match \"compress\" inside \"decompress\").\r\n\r\nEXAMPLE\r\nThe text contains \"CamelCaseWords\". To write \"PascalCaseWords\", start either\r\nwith \"PascalCaseW\" (unique text match), \"PascalC\" (several text matches), or\r\n\"PascalCW\" (unique fragment match).\r\n\r\nThe text contains \"ConfigurationItem\". To write \"SystemConfigurationItem\",\r\nstart with \"SystemCo\" (full text match) or \"SystemCI\" (full fragment match).","4":"DESCRIPTION\r\nThe built-in insert mode completion i_CTRL-N searches for entire keywords.\r\nOften, variable names share many identical fragments, but if you want to\r\ncomplete from fragments inside of variables (e.g. \"KeyValue\" from\r\n\"SpecialKeyValue\"), it won't work, because the usual completions only offer\r\nwhole keyword matches.\r\n\r\nSEE ALSO\r\n- The anchoring to individual fragment characters is re-used from\r\n  CamelCaseComplete (vimscript #3915), but applied here only to fragments\r\n  inside CamelCaseWords or underscore_words, not whole words.\r\n- BidiComplete (vimscript #4658) can complete inner (or leftmost) fragments\r\n  when there's already a completion base after the cursor.\r\n- Check out the CompleteHelper.vim plugin page (vimscript #3914) for a full\r\n  list of insert mode completions powered by it.\r\n\r\nUSAGE\r\nIn insert mode, invoke the inner fragment completion via CTRL-X i\r\nYou can then search forward and backward via CTRL-N \/ CTRL-P, as usual.\r\n\r\nCTRL-X i                Find matches for inner fragments. It first searches\r\n                        inside CamelCaseWords and underscore_words, either for\r\n                        matches of the keyword characters before the cursor at\r\n                        the inner fragment start, or for fragments whose\r\n                        individual words begin with the typed letters in front\r\n                        of the cursor. (The latter requires the optional\r\n                        CamelCaseComplete.vim plugin, and then works like\r\n                        with the strict i_CTRL-X_CTRL-C completion.)\r\n                        The completion base starts with the first uppercase\r\n                        character before the cursor (so \"myCust\" would find\r\n                        fragments starting with \"Cust\", e.g. in\r\n                        \"SpecialCustomer\"), or the keywords (excluding the\r\n                        underscore character, to be able to trigger completion\r\n                        inside an underscore_word) before the cursor. If the\r\n                        first keyword character is lowercase, the inner\r\n                        CamelCase matches will be converted to start\r\n                        lowercase, too.\r\n                        If there is a fragment before the completion base\r\n                        (e.g. \"My\" in \"MyCust\", or \"end_\" in \"end_foo\") the\r\n                        completion not only offers matching inner fragments,\r\n                        but also the complete word match, in order to complete\r\n                        prefixed new words with existing full words.\r\n                        For CamelCaseWord fragments, matches at the start of a\r\n                        CamelCaseWord are also valid, as long as it's not the\r\n                        entire CamelCaseWord that is matched (e.g. \"CC\"\r\n                        matches \"CamelCase\" in \"CamelCaseWord\").\r\n\r\n                        If that doesn't find any matches, a fallback search\r\n                        will pick up base matches anywhere inside a word (e.g.\r\n                        \"comp\" will match \"compress\" inside \"decompress\").\r\n\r\nEXAMPLE\r\nThe text contains \"CamelCaseWords\". To write \"PascalCaseWords\", start either\r\nwith \"PascalCaseW\" (unique text match), \"PascalC\" (several text matches), or\r\n\"PascalCW\" (unique fragment match).\r\n\r\nThe text contains \"ConfigurationItem\". To write \"SystemConfigurationItem\",\r\nstart with \"SystemCo\" (full text match) or \"SystemCI\" (full fragment match).","install_details":"INSTALLATION\r\nThis script is packaged as a vimball. If you have the \"gunzip\" decompressor\r\nin your PATH, simply edit the *.vmb.gz package in Vim; otherwise, decompress\r\nthe archive first, e.g. using WinZip. Inside Vim, install by sourcing the\r\nvimball or via the :UseVimball command.\r\n    vim InnerFragmentComplete*.vmb.gz\r\n    :so %\r\nTo uninstall, use the :RmVimball command.\r\n\r\nDEPENDENCIES\r\n- Requires Vim 7.0 or higher.\r\n- Requires the CompleteHelper.vim (vimscript #3914) plugin, version 1.32 or\r\n  higher.\r\n- CamelCaseComplete.vim (vimscript #3915) plugin, version 1.01 or higher\r\n  (optional).\r\n\r\nCONFIGURATION\r\nFor a permanent configuration, put the following commands into your vimrc:\r\n\r\nAnaloguous to the 'complete' option, you can specify which buffers will be\r\nscanned for completion candidates. Currently, '.' (current buffer), 'w'\r\n(buffers from other windows), and 'b' (other listed buffers) are supported.\r\n    let g:InnerFragmentComplete_complete = '.,w,b'\r\nThe global setting can be overridden for a particular buffer\r\n(b:InnerFragmentComplete_complete).\r\n\r\nIf you want to use a different mapping, map your keys to the\r\n<Plug>(InnerFragmentComplete) mapping target _before_ sourcing the script\r\n(e.g. in your vimrc):\r\n    imap <C-x>i  <Plug>(InnerFragmentComplete)","5":"INSTALLATION\r\nThis script is packaged as a vimball. If you have the \"gunzip\" decompressor\r\nin your PATH, simply edit the *.vmb.gz package in Vim; otherwise, decompress\r\nthe archive first, e.g. using WinZip. Inside Vim, install by sourcing the\r\nvimball or via the :UseVimball command.\r\n    vim InnerFragmentComplete*.vmb.gz\r\n    :so %\r\nTo uninstall, use the :RmVimball command.\r\n\r\nDEPENDENCIES\r\n- Requires Vim 7.0 or higher.\r\n- Requires the CompleteHelper.vim (vimscript #3914) plugin, version 1.32 or\r\n  higher.\r\n- CamelCaseComplete.vim (vimscript #3915) plugin, version 1.01 or higher\r\n  (optional).\r\n\r\nCONFIGURATION\r\nFor a permanent configuration, put the following commands into your vimrc:\r\n\r\nAnaloguous to the 'complete' option, you can specify which buffers will be\r\nscanned for completion candidates. Currently, '.' (current buffer), 'w'\r\n(buffers from other windows), and 'b' (other listed buffers) are supported.\r\n    let g:InnerFragmentComplete_complete = '.,w,b'\r\nThe global setting can be overridden for a particular buffer\r\n(b:InnerFragmentComplete_complete).\r\n\r\nIf you want to use a different mapping, map your keys to the\r\n<Plug>(InnerFragmentComplete) mapping target _before_ sourcing the script\r\n(e.g. in your vimrc):\r\n    imap <C-x>i  <Plug>(InnerFragmentComplete)","first_name":"Ingo","6":"Ingo","last_name":"Karkat","7":"Karkat","releases":[{"0":"4804","vim_version":"7.0","1":"7.0","script_version":"1.10","2":"1.10","version_comment":"- ENH: When the completion base is prefixed by a fragment (e.g. \"my\" in \"myFoo\"), also offer full keyword \/ CamelCaseWord matches, not just inner fragments, as the default completion \/ CamelCaseComplete would not use that base, yet it is helpful when completing \"myFooBar\" from \"FooBar\".\r\n- ENH: Also match from the start of a CamelCaseWord without a base prefix. But then, there must be additional (unmatched) fragments after the match to avoid overlap with the CamelCaseComplete completion.","3":"- ENH: When the completion base is prefixed by a fragment (e.g. \"my\" in \"myFoo\"), also offer full keyword \/ CamelCaseWord matches, not just inner fragments, as the default completion \/ CamelCaseComplete would not use that base, yet it is helpful when completing \"myFooBar\" from \"FooBar\".\r\n- ENH: Also match from the start of a CamelCaseWord without a base prefix. But then, there must be additional (unmatched) fragments after the match to avoid overlap with the CamelCaseComplete completion.","package":"InnerFragmentComplete-1.10.vmb.gz","4":"InnerFragmentComplete-1.10.vmb.gz","src_id":"21732","5":"21732","creation_date":"1396620960","6":"1396620960"},{"0":"4804","vim_version":"7.0","1":"7.0","script_version":"1.00","2":"1.00","version_comment":"Initial upload","3":"Initial upload","package":"InnerFragmentComplete-1.00.vmb.gz","4":"InnerFragmentComplete-1.00.vmb.gz","src_id":"21214","5":"21214","creation_date":"1387439262","6":"1387439262"}]},"4803":{"script_id":"4803","0":"4803","script_name":"ft-cmake","1":"ft-cmake","script_type":"ftplugin","2":"ftplugin","summary":"dict and snippet for cmake files (e.g. CMakeLists.txt)","3":"dict and snippet for cmake files (e.g. CMakeLists.txt)","description":"dict and snippet for cmake files (e.g. CMakeLists.txt)\n\n* http:\/\/github.com\/ujihisa\/ft-cmake\n","4":"dict and snippet for cmake files (e.g. CMakeLists.txt)\n\n* http:\/\/github.com\/ujihisa\/ft-cmake\n","install_details":"NeoBundle 'ujihisa\/ft-cmake'\n","5":"NeoBundle 'ujihisa\/ft-cmake'\n","first_name":"ujihisa","6":"ujihisa","last_name":".","7":".","releases":[{"0":"4803","vim_version":"7.3","1":"7.3","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"ft-cmake-1.0.tgz","4":"ft-cmake-1.0.tgz","src_id":"21212","5":"21212","creation_date":"1387437932","6":"1387437932"}]},"4802":{"script_id":"4802","0":"4802","script_name":"vim-javacompleteex","1":"vim-javacompleteex","script_type":"ftplugin","2":"ftplugin","summary":"better java omni-completion.","3":"better java omni-completion.","description":"see: https:\/\/github.com\/richox\/vim-javacompleteex","4":"see: https:\/\/github.com\/richox\/vim-javacompleteex","install_details":"see: https:\/\/github.com\/richox\/vim-javacompleteex","5":"see: https:\/\/github.com\/richox\/vim-javacompleteex","first_name":"Zhang","6":"Zhang","last_name":"Li","7":"Li","releases":[{"0":"4802","vim_version":"7.0","1":"7.0","script_version":"20131218","2":"20131218","version_comment":"Initial upload","3":"Initial upload","package":"vim-javacompleteex-20131218.zip","4":"vim-javacompleteex-20131218.zip","src_id":"21207","5":"21207","creation_date":"1387361358","6":"1387361358"}]},"4801":{"script_id":"4801","0":"4801","script_name":"vim-skuld","1":"vim-skuld","script_type":"utility","2":"utility","summary":"A pomodoro timer that runs inside Vim.","3":"A pomodoro timer that runs inside Vim.","description":"Introduction\r\n============\r\n\r\nSkuld is a [pomodoro timer][1] that runs inside Vim. It can help you track\r\nyour tasks in an simple (or stupid) way.\r\n\r\n![Skuld Screenshot](https:\/\/raw.github.com\/l04m33\/img\/master\/vim-skuld-screenshot.png)\r\n\r\nPlease send pull requests to https:\/\/github.com\/l04m33\/vim-skuld\r\n\r\n[1]: http:\/\/en.wikipedia.org\/wiki\/Pomodoro_technique\r\n\r\nDependencies\r\n============\r\n\r\nSkuld depends on `+python` or `+python3`, as well as `+clientserver`.\r\nNothing else is needed.\r\n\r\nInstallation\r\n============\r\n\r\n[Vundle][2] is recommended.\r\n\r\n[2]: https:\/\/github.com\/gmarik\/vundle\r\n\r\nUsage\r\n=====\r\n\r\nAfter a successful installation, these commands are available:\r\n\r\n- `SkuldStartTimer <task_id>`   : Start the pomodoro timer\r\n- `SkuldStopTimer`              : Stop the pomodoro timer\r\n- `SkuldStartTask <task_id>`    : Switch current task. The timer will be started if it's stopped\r\n- `SkuldSwitchTask <task_id>`   : Switch current task\r\n- `SkuldGetState`               : Display current timer state\r\n- `SkuldBufOpen`                : Open the buffer containing the task list (`[Skuld Tasks]`)\r\n- `SkuldTaskUpdate`             : Update the internal task list according to `[Skuld Tasks]` buffer\r\n\r\n`SkuldBufOpen` is mapped to `<leader>sb` by default. You can open a scratch\r\nbuffer called `[Skuld Tasks]` using this command, and then write down your\r\ntasks in that buffer, **one task per line**. Whenever you leave insert mode,\r\nor leave the `[Skuld Tasks]` buffer, your tasks will be set automatically.\r\nEach task will be assigned an ID. The IDs start from **zero**.\r\n\r\nOnce the tasks are set, you can press `<cr>` on a task to start the timer.\r\nYou don't need to keep the `[Skuld Tasks]` buffer open while the timer is\r\nrunning.\r\n\r\nWhen the pomodoro timer times out, there will be a Vim message signifying\r\nthe change of timer state. You can start working or have a break\r\naccordingly. Skuld will append a pomodoro completion symbol, which defaults\r\nto `*`, after the current task, when a working period ends.\r\n\r\nIf you invoked `SkuldStopTimer` during a working period, a squash symbol,\r\nwhich defaults to `x`, will be appended instead.\r\n\r\nYou can edit `[Skuld Tasks]` buffer while the timer is running. Edited\r\ntasks will be synchronized automatically once you leave insert mode or\r\nleave the buffer.\r\n\r\nMappings\r\n========\r\n\r\n```VimL\r\n    nnoremap <leader>sb :SkuldBufOpen<cr>\r\n    nnoremap <leader>ss :SkuldGetState<cr>\r\n```\r\n\r\nSettings\r\n========\r\n\r\nThese variables can be set in you `.vimrc` to override the defaults:\r\n\r\n```VimL\r\n    \" Pomodoro completion symbol\r\n    let g:skuld_progress_symbol = '*'\r\n\r\n    \" Pomodoro squashed symbol\r\n    let g:skuld_squash_symbol = 'x'\r\n\r\n    \" Pomodoro working period (in minutes)\r\n    let g:skuld_work_period = 25\r\n\r\n    \" Pomodoro resting period (in minutes)\r\n    let g:skuld_rest_period = 5\r\n\r\n    \" Pomodoro long resting period (in minutes)\r\n    let g:skuld_long_rest_period = 15\r\n\r\n    \" Max working streak before long resting\r\n    let g:skuld_max_work_streak = 4\r\n\r\n    \" Notification command\r\n    let g:skuld_notify_cmd = 'notify-send'\r\n\r\n    \" Mapping for opening the task buffer\r\n    let g:skuld_buffer_map = '<leader>sb'\r\n\r\n    \" Mapping for displaying the current state\r\n    let g:skuld_state_map = '<leader>ss'\r\n\r\n    \" Default line width for the task buffer\r\n    let g:skuld_line_width = 29\r\n```\r\n\r\nLicense\r\n=======\r\n\r\nThis Vim plugin is licensed under the terms of [the MIT license][3].\r\n\r\n[3]: http:\/\/l04m33.mit-license.org\/\r\n\r\n","4":"Introduction\r\n============\r\n\r\nSkuld is a [pomodoro timer][1] that runs inside Vim. It can help you track\r\nyour tasks in an simple (or stupid) way.\r\n\r\n![Skuld Screenshot](https:\/\/raw.github.com\/l04m33\/img\/master\/vim-skuld-screenshot.png)\r\n\r\nPlease send pull requests to https:\/\/github.com\/l04m33\/vim-skuld\r\n\r\n[1]: http:\/\/en.wikipedia.org\/wiki\/Pomodoro_technique\r\n\r\nDependencies\r\n============\r\n\r\nSkuld depends on `+python` or `+python3`, as well as `+clientserver`.\r\nNothing else is needed.\r\n\r\nInstallation\r\n============\r\n\r\n[Vundle][2] is recommended.\r\n\r\n[2]: https:\/\/github.com\/gmarik\/vundle\r\n\r\nUsage\r\n=====\r\n\r\nAfter a successful installation, these commands are available:\r\n\r\n- `SkuldStartTimer <task_id>`   : Start the pomodoro timer\r\n- `SkuldStopTimer`              : Stop the pomodoro timer\r\n- `SkuldStartTask <task_id>`    : Switch current task. The timer will be started if it's stopped\r\n- `SkuldSwitchTask <task_id>`   : Switch current task\r\n- `SkuldGetState`               : Display current timer state\r\n- `SkuldBufOpen`                : Open the buffer containing the task list (`[Skuld Tasks]`)\r\n- `SkuldTaskUpdate`             : Update the internal task list according to `[Skuld Tasks]` buffer\r\n\r\n`SkuldBufOpen` is mapped to `<leader>sb` by default. You can open a scratch\r\nbuffer called `[Skuld Tasks]` using this command, and then write down your\r\ntasks in that buffer, **one task per line**. Whenever you leave insert mode,\r\nor leave the `[Skuld Tasks]` buffer, your tasks will be set automatically.\r\nEach task will be assigned an ID. The IDs start from **zero**.\r\n\r\nOnce the tasks are set, you can press `<cr>` on a task to start the timer.\r\nYou don't need to keep the `[Skuld Tasks]` buffer open while the timer is\r\nrunning.\r\n\r\nWhen the pomodoro timer times out, there will be a Vim message signifying\r\nthe change of timer state. You can start working or have a break\r\naccordingly. Skuld will append a pomodoro completion symbol, which defaults\r\nto `*`, after the current task, when a working period ends.\r\n\r\nIf you invoked `SkuldStopTimer` during a working period, a squash symbol,\r\nwhich defaults to `x`, will be appended instead.\r\n\r\nYou can edit `[Skuld Tasks]` buffer while the timer is running. Edited\r\ntasks will be synchronized automatically once you leave insert mode or\r\nleave the buffer.\r\n\r\nMappings\r\n========\r\n\r\n```VimL\r\n    nnoremap <leader>sb :SkuldBufOpen<cr>\r\n    nnoremap <leader>ss :SkuldGetState<cr>\r\n```\r\n\r\nSettings\r\n========\r\n\r\nThese variables can be set in you `.vimrc` to override the defaults:\r\n\r\n```VimL\r\n    \" Pomodoro completion symbol\r\n    let g:skuld_progress_symbol = '*'\r\n\r\n    \" Pomodoro squashed symbol\r\n    let g:skuld_squash_symbol = 'x'\r\n\r\n    \" Pomodoro working period (in minutes)\r\n    let g:skuld_work_period = 25\r\n\r\n    \" Pomodoro resting period (in minutes)\r\n    let g:skuld_rest_period = 5\r\n\r\n    \" Pomodoro long resting period (in minutes)\r\n    let g:skuld_long_rest_period = 15\r\n\r\n    \" Max working streak before long resting\r\n    let g:skuld_max_work_streak = 4\r\n\r\n    \" Notification command\r\n    let g:skuld_notify_cmd = 'notify-send'\r\n\r\n    \" Mapping for opening the task buffer\r\n    let g:skuld_buffer_map = '<leader>sb'\r\n\r\n    \" Mapping for displaying the current state\r\n    let g:skuld_state_map = '<leader>ss'\r\n\r\n    \" Default line width for the task buffer\r\n    let g:skuld_line_width = 29\r\n```\r\n\r\nLicense\r\n=======\r\n\r\nThis Vim plugin is licensed under the terms of [the MIT license][3].\r\n\r\n[3]: http:\/\/l04m33.mit-license.org\/\r\n\r\n","install_details":"","5":"","first_name":"Kay","6":"Kay","last_name":"Z.","7":"Z.","releases":[{"0":"4801","vim_version":"7.0","1":"7.0","script_version":"0.2.3","2":"0.2.3","version_comment":"- The default key mappings can now be overridden by setting global variables.\r\n- The default line width for the task buffer is now adjustable (see README.markdown).","3":"- The default key mappings can now be overridden by setting global variables.\r\n- The default line width for the task buffer is now adjustable (see README.markdown).","package":"vim-skuld-0.2.3.tar.bz2","4":"vim-skuld-0.2.3.tar.bz2","src_id":"21260","5":"21260","creation_date":"1388416647","6":"1388416647"},{"0":"4801","vim_version":"7.0","1":"7.0","script_version":"0.2.2","2":"0.2.2","version_comment":"- Use the 'gutter' area to show current task.\r\n- Add convenient mapping for switching tasks.","3":"- Use the 'gutter' area to show current task.\r\n- Add convenient mapping for switching tasks.","package":"vim-skuld-0.2.2.tar.bz2","4":"vim-skuld-0.2.2.tar.bz2","src_id":"21227","5":"21227","creation_date":"1387782214","6":"1387782214"},{"0":"4801","vim_version":"7.0","1":"7.0","script_version":"0.2.1","2":"0.2.1","version_comment":"- Fix task highlighting\r\n- Add screenshot","3":"- Fix task highlighting\r\n- Add screenshot","package":"vim-skuld-0.2.1.tar.bz2","4":"vim-skuld-0.2.1.tar.bz2","src_id":"21211","5":"21211","creation_date":"1387387309","6":"1387387309"},{"0":"4801","vim_version":"7.0","1":"7.0","script_version":"0.2.0","2":"0.2.0","version_comment":"- Use a closure to prevent name leaks.\r\n- Add installation instruction in README.","3":"- Use a closure to prevent name leaks.\r\n- Add installation instruction in README.","package":"vim-skuld-0.2.0.tar.bz2","4":"vim-skuld-0.2.0.tar.bz2","src_id":"21210","5":"21210","creation_date":"1387365050","6":"1387365050"},{"0":"4801","vim_version":"7.0","1":"7.0","script_version":"0.1.0","2":"0.1.0","version_comment":"Initial upload","3":"Initial upload","package":"vim-skuld-0.1.0.tar.bz2","4":"vim-skuld-0.1.0.tar.bz2","src_id":"21205","5":"21205","creation_date":"1387280685","6":"1387280685"}]},"4800":{"script_id":"4800","0":"4800","script_name":"Investigate.vim","1":"Investigate.vim","script_type":"utility","2":"utility","summary":"A plugin for viewing documentation","3":"A plugin for viewing documentation","description":"# investigate.vim\r\n\r\nThe plugin is on Github https:\/\/github.com\/Keithbsmiley\/investigate.vim\/\r\n\r\nA plugin for looking documentation on the word under the cursor.\r\nYou can choose to open it in a browser, with\r\n[Dash](http:\/\/kapeli.com\/dash) on OS X, or with an arbitary\r\nshell command.\r\n\r\n## Example\r\n\r\n![Web](http:\/\/keithbsmiley.github.io\/investigate.vim\/img\/web.gif)\r\n\r\n## Setup\r\n\r\nExample mapping:\r\n\r\n```\r\nnnoremap K :call investigate#Investigate()<cr>\r\n```\r\n\r\nWith this mapping, using capital K when your cursor is on a specific\r\nword will open its documentation. The [help\r\nfile](https:\/\/github.com\/Keithbsmiley\/investigate.vim\/blob\/master\/doc\/investigate.txt)\r\nhas tons of documentation on configuration. Here are some of the\r\nbasic options.\r\n\r\n## Configuration\r\n\r\n### Dash\r\n\r\nIf you want to open everything in Dash you need to set:\r\n\r\n```\r\nlet g:investigate_use_dash=1\r\n```\r\n\r\nThis value is ignored unless you're on OS X. If you want to use Dash\r\nconditionally based off the current filetype you can set something like:\r\n\r\n```\r\nlet g:investigate_use_dash_for_ruby=1\r\n```\r\n\r\nIf you want to use something else, like a URL for a single type you'd\r\nwant to use this which will override the global Dash setting:\r\n\r\n```\r\nlet g:investigate_use_url_for_ruby=1\r\n```\r\n\r\nIf you use a different keyword in Dash for a given language you can\r\nset it by using:\r\n\r\n```\r\nlet g:investigate_dash_for_ruby=\"rails\"\r\n```\r\n\r\nThis would set all Ruby files to open in the Rails documentation.\r\n\r\n\r\n### URLs\r\n\r\nIf you don't like the website I chose as the default for a filetype you\r\ncan redefine it with:\r\n\r\n```\r\nlet g:investigate_url_for_ruby=\"http:\/\/ruby-doc.com\/search.html?q=^s\"\r\n```\r\n\r\nWhere `^s` will be replaced with the word under the cursor for Ruby\r\nfiles.\r\n\r\n\r\n### Custom Commands\r\n\r\nYou can also open documentation with arbitrary shell commands. See\r\n`investigate-writing-commands` in the documentation for more info.\r\n\r\n\r\n### Project specific settings\r\n\r\nYou can setup project specific settings with an `.invrc` file from the\r\ndirectory you launch Vim in. For example for a Rails project you may\r\nwant to set Ruby files to open Rails documentation for that single\r\nproject but not other Ruby gem based projects you're working on. To do\r\nthat the file would look something like this:\r\n\r\n```\r\n[syntax]\r\nruby=rails\r\n```\r\n\r\nThis will set a syntax variable:\r\n\r\n```\r\nlet g:investigate_syntax_for_ruby=rails\r\n```\r\n\r\nWhich entirely changes Ruby files to open in the Rails documentation.\r\nSee `investigate-conf-file` for more information.\r\n\r\n\r\n## Installation\r\n\r\n### With [Vundle](https:\/\/github.com\/gmarik\/vundle)\r\n\r\nAdd:\r\n\r\n```\r\nBundle 'Keithbsmiley\/investigate.vim'\r\n```\r\n\r\nTo your `.vimrc` and run `BundleInstall` from within vim or `vim +BundleInstall +qall` from the command line\r\n\r\n### With [Pathogen](https:\/\/github.com\/tpope\/vim-pathogen)\r\n\r\n```\r\ncd ~\/.vim\/bundle\r\ngit clone https:\/\/github.com\/Keithbsmiley\/investigate.vim.git\r\n```\r\n\r\nTo generate the helptags afterwards run `:Helptags`\r\n\r\n## Development\r\n\r\nIf you find any bugs, want any languages added, or want any default\r\nlanguage settings changed, please submit an\r\n[issue](https:\/\/github.com\/Keithbsmiley\/investigate.vim\/issues\/new).\r\n","4":"# investigate.vim\r\n\r\nThe plugin is on Github https:\/\/github.com\/Keithbsmiley\/investigate.vim\/\r\n\r\nA plugin for looking documentation on the word under the cursor.\r\nYou can choose to open it in a browser, with\r\n[Dash](http:\/\/kapeli.com\/dash) on OS X, or with an arbitary\r\nshell command.\r\n\r\n## Example\r\n\r\n![Web](http:\/\/keithbsmiley.github.io\/investigate.vim\/img\/web.gif)\r\n\r\n## Setup\r\n\r\nExample mapping:\r\n\r\n```\r\nnnoremap K :call investigate#Investigate()<cr>\r\n```\r\n\r\nWith this mapping, using capital K when your cursor is on a specific\r\nword will open its documentation. The [help\r\nfile](https:\/\/github.com\/Keithbsmiley\/investigate.vim\/blob\/master\/doc\/investigate.txt)\r\nhas tons of documentation on configuration. Here are some of the\r\nbasic options.\r\n\r\n## Configuration\r\n\r\n### Dash\r\n\r\nIf you want to open everything in Dash you need to set:\r\n\r\n```\r\nlet g:investigate_use_dash=1\r\n```\r\n\r\nThis value is ignored unless you're on OS X. If you want to use Dash\r\nconditionally based off the current filetype you can set something like:\r\n\r\n```\r\nlet g:investigate_use_dash_for_ruby=1\r\n```\r\n\r\nIf you want to use something else, like a URL for a single type you'd\r\nwant to use this which will override the global Dash setting:\r\n\r\n```\r\nlet g:investigate_use_url_for_ruby=1\r\n```\r\n\r\nIf you use a different keyword in Dash for a given language you can\r\nset it by using:\r\n\r\n```\r\nlet g:investigate_dash_for_ruby=\"rails\"\r\n```\r\n\r\nThis would set all Ruby files to open in the Rails documentation.\r\n\r\n\r\n### URLs\r\n\r\nIf you don't like the website I chose as the default for a filetype you\r\ncan redefine it with:\r\n\r\n```\r\nlet g:investigate_url_for_ruby=\"http:\/\/ruby-doc.com\/search.html?q=^s\"\r\n```\r\n\r\nWhere `^s` will be replaced with the word under the cursor for Ruby\r\nfiles.\r\n\r\n\r\n### Custom Commands\r\n\r\nYou can also open documentation with arbitrary shell commands. See\r\n`investigate-writing-commands` in the documentation for more info.\r\n\r\n\r\n### Project specific settings\r\n\r\nYou can setup project specific settings with an `.invrc` file from the\r\ndirectory you launch Vim in. For example for a Rails project you may\r\nwant to set Ruby files to open Rails documentation for that single\r\nproject but not other Ruby gem based projects you're working on. To do\r\nthat the file would look something like this:\r\n\r\n```\r\n[syntax]\r\nruby=rails\r\n```\r\n\r\nThis will set a syntax variable:\r\n\r\n```\r\nlet g:investigate_syntax_for_ruby=rails\r\n```\r\n\r\nWhich entirely changes Ruby files to open in the Rails documentation.\r\nSee `investigate-conf-file` for more information.\r\n\r\n\r\n## Installation\r\n\r\n### With [Vundle](https:\/\/github.com\/gmarik\/vundle)\r\n\r\nAdd:\r\n\r\n```\r\nBundle 'Keithbsmiley\/investigate.vim'\r\n```\r\n\r\nTo your `.vimrc` and run `BundleInstall` from within vim or `vim +BundleInstall +qall` from the command line\r\n\r\n### With [Pathogen](https:\/\/github.com\/tpope\/vim-pathogen)\r\n\r\n```\r\ncd ~\/.vim\/bundle\r\ngit clone https:\/\/github.com\/Keithbsmiley\/investigate.vim.git\r\n```\r\n\r\nTo generate the helptags afterwards run `:Helptags`\r\n\r\n## Development\r\n\r\nIf you find any bugs, want any languages added, or want any default\r\nlanguage settings changed, please submit an\r\n[issue](https:\/\/github.com\/Keithbsmiley\/investigate.vim\/issues\/new).\r\n","install_details":"","5":"","first_name":"Keith","6":"Keith","last_name":"Smiley","7":"Smiley","releases":[{"0":"4800","vim_version":"7.0","1":"7.0","script_version":"1.0.0","2":"1.0.0","version_comment":"Initial upload","3":"Initial upload","package":"investigate.vim.tar.gz","4":"investigate.vim.tar.gz","src_id":"21201","5":"21201","creation_date":"1387218069","6":"1387218069"}]},"4799":{"script_id":"4799","0":"4799","script_name":"Include Fixer for C\/C++","1":"Include Fixer for C\/C++","script_type":"utility","2":"utility","summary":"Categorizes and Alphabetizes C\/C++ #include directives","3":"Categorizes and Alphabetizes C\/C++ #include directives","description":"Include Fixer organizes C and C++ #include header files to be in specific\r\ncategories, as well as organizing alphabetically. Default categories are\r\nprovided, as well as the option to customize categories\r\n\r\nUsage:\r\nOnce installed, use the following command to organize include files:\r\n    :FixIncludes\r\n\r\nThe command will search for lines containing #include directives, and organize\r\nthem into different categories and alphabetically within those categories.\r\nNote: this includes whether the include is written as \"file.h\" or <file.h>.\r\nAll includes starting with \" will precede those starting with <\r\n\r\nThe plugin comes with a number of default categories. Each category is\r\nseparated from the others with a blank line. The default categories are\r\narranged in the following order:\r\n        module\r\n        local\r\n        boost\r\n        qt\r\n        c std library\r\n        c++ std library","4":"Include Fixer organizes C and C++ #include header files to be in specific\r\ncategories, as well as organizing alphabetically. Default categories are\r\nprovided, as well as the option to customize categories\r\n\r\nUsage:\r\nOnce installed, use the following command to organize include files:\r\n    :FixIncludes\r\n\r\nThe command will search for lines containing #include directives, and organize\r\nthem into different categories and alphabetically within those categories.\r\nNote: this includes whether the include is written as \"file.h\" or <file.h>.\r\nAll includes starting with \" will precede those starting with <\r\n\r\nThe plugin comes with a number of default categories. Each category is\r\nseparated from the others with a blank line. The default categories are\r\narranged in the following order:\r\n        module\r\n        local\r\n        boost\r\n        qt\r\n        c std library\r\n        c++ std library","install_details":"Note: I recommend using Tim Pope's pathogen plugin to install this plugin. See\r\nhttps:\/\/github.com\/tpope\/vim-pathogen. If you've installed pathogen properly\r\nyou can install Include Fixer with the following commands:\r\n\r\n        $ cd ~\/.vim\/bundle\r\n        $ git clone https:\/\/github.com\/DeonPoncini\/includefixer.git\r\n\r\nIf you aren't using pathogen, you can use the following steps to install:\r\n1.  Checkout the git repository above\r\n2.  Move `includefixer.vim` to your `plugins` directory\r\n3.  Move this help file into the `doc` directory","5":"Note: I recommend using Tim Pope's pathogen plugin to install this plugin. See\r\nhttps:\/\/github.com\/tpope\/vim-pathogen. If you've installed pathogen properly\r\nyou can install Include Fixer with the following commands:\r\n\r\n        $ cd ~\/.vim\/bundle\r\n        $ git clone https:\/\/github.com\/DeonPoncini\/includefixer.git\r\n\r\nIf you aren't using pathogen, you can use the following steps to install:\r\n1.  Checkout the git repository above\r\n2.  Move `includefixer.vim` to your `plugins` directory\r\n3.  Move this help file into the `doc` directory","first_name":"Deon","6":"Deon","last_name":"Poncini","7":"Poncini","releases":[{"0":"4799","vim_version":"7.3","1":"7.3","script_version":"0.1","2":"0.1","version_comment":"Fix small bug with not removing enough blank lines","3":"Fix small bug with not removing enough blank lines","package":"includefixer.tar.gz","4":"includefixer.tar.gz","src_id":"21198","5":"21198","creation_date":"1387071850","6":"1387071850"}]},"4798":{"script_id":"4798","0":"4798","script_name":"swamplight","1":"swamplight","script_type":"color scheme","2":"color scheme","summary":"light color scheme, GUI and 256","3":"light color scheme, GUI and 256","description":"This is a light vim color scheme, made from scratch.\r\nThe UI elements are complete - I didn't skip stuff (I hope) like some other themes do.\r\nHas GUI color as well as 256 color support, although the background of the 256 color\r\nvariant couldn't match the intended color too well.\r\n\r\nWorks better if the font is not a single pixel bitmap. I think this is the fault of it\r\nbeing a light color scheme.\r\n\r\nKeep in mind I am not a programmer, so the syntax color choice might be off or something,\r\nalthough seeing how bad most of the other color schemes are...\r\n\r\nBest to check the screenshots below.\r\n\r\n###### Screenshots ######\r\n\r\nrandom ruby with Consolas font:\r\nhttp:\/\/i.imgur.com\/gjyvkKs.png\r\n\r\ndiff with DejaVu Sans Mono:\r\nhttp:\/\/i.imgur.com\/vM6kSD0.png\r\n\r\nTerminus font:\r\nhttp:\/\/i.imgur.com\/lOcg3hY.png\r\n\r\nAnd the 256 color variant with VGA font:\r\nhttp:\/\/i.imgur.com\/AzhjP2T.png\r\n\r\nAny comments for improving this can be made at \"2drealm@gmail.com\"\r\nIf you find something wrong please write, even something very short.","4":"This is a light vim color scheme, made from scratch.\r\nThe UI elements are complete - I didn't skip stuff (I hope) like some other themes do.\r\nHas GUI color as well as 256 color support, although the background of the 256 color\r\nvariant couldn't match the intended color too well.\r\n\r\nWorks better if the font is not a single pixel bitmap. I think this is the fault of it\r\nbeing a light color scheme.\r\n\r\nKeep in mind I am not a programmer, so the syntax color choice might be off or something,\r\nalthough seeing how bad most of the other color schemes are...\r\n\r\nBest to check the screenshots below.\r\n\r\n###### Screenshots ######\r\n\r\nrandom ruby with Consolas font:\r\nhttp:\/\/i.imgur.com\/gjyvkKs.png\r\n\r\ndiff with DejaVu Sans Mono:\r\nhttp:\/\/i.imgur.com\/vM6kSD0.png\r\n\r\nTerminus font:\r\nhttp:\/\/i.imgur.com\/lOcg3hY.png\r\n\r\nAnd the 256 color variant with VGA font:\r\nhttp:\/\/i.imgur.com\/AzhjP2T.png\r\n\r\nAny comments for improving this can be made at \"2drealm@gmail.com\"\r\nIf you find something wrong please write, even something very short.","install_details":"You know how it goes, put the file in \"~\/.vim\/colors\" or whatever.","5":"You know how it goes, put the file in \"~\/.vim\/colors\" or whatever.","first_name":"Borislav","6":"Borislav","last_name":"Velichkov","7":"Velichkov","releases":[{"0":"4798","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"swamplight.vim","4":"swamplight.vim","src_id":"21192","5":"21192","creation_date":"1387035137","6":"1387035137"}]},"4797":{"script_id":"4797","0":"4797","script_name":"CtrlP-SmartTabs","1":"CtrlP-SmartTabs","script_type":"utility","2":"utility","summary":"Vim CtrlP plugin to switch between opened tabs","3":"Vim CtrlP plugin to switch between opened tabs","description":"With the vim plugin CtrlP you can easily open a file or a buffer.\r\nThis is a ctrlp.vim extension that allow you to switch between different opened tabs.\r\n\r\nGithub repository: https:\/\/github.com\/DavidEGx\/ctrlp-smarttabs","4":"With the vim plugin CtrlP you can easily open a file or a buffer.\r\nThis is a ctrlp.vim extension that allow you to switch between different opened tabs.\r\n\r\nGithub repository: https:\/\/github.com\/DavidEGx\/ctrlp-smarttabs","install_details":"See https:\/\/github.com\/DavidEGx\/ctrlp-smarttabs","5":"See https:\/\/github.com\/DavidEGx\/ctrlp-smarttabs","first_name":"David","6":"David","last_name":"Escribano Garcia","7":"Escribano Garcia","releases":[{"0":"4797","vim_version":"7.0","1":"7.0","script_version":"0.7","2":"0.7","version_comment":"* Use a better title for quickfix buffers.\r\n* Allow to hide quickfix buffers.","3":"* Use a better title for quickfix buffers.\r\n* Allow to hide quickfix buffers.","package":"ctrlp-smarttabs.zip","4":"ctrlp-smarttabs.zip","src_id":"25189","5":"25189","creation_date":"1494417415","6":"1494417415"},{"0":"4797","vim_version":"7.0","1":"7.0","script_version":"0.6","2":"0.6","version_comment":"Add configuration options:\r\n* Highlight selected file in tabline is optional (g:ctrlp_smarttabs_modify_tabline).\r\n* Control the order in which files are displayed (g:ctrlp_smarttabs_reverse)","3":"Add configuration options:\r\n* Highlight selected file in tabline is optional (g:ctrlp_smarttabs_modify_tabline).\r\n* Control the order in which files are displayed (g:ctrlp_smarttabs_reverse)","package":"ctrlp-smarttabs.zip","4":"ctrlp-smarttabs.zip","src_id":"22715","5":"22715","creation_date":"1419081516","6":"1419081516"},{"0":"4797","vim_version":"7.0","1":"7.0","script_version":"0.5","2":"0.5","version_comment":"Initialize smarttabs as a ctrlp plugin correctly","3":"Initialize smarttabs as a ctrlp plugin correctly","package":"ctrlp-smarttabs.zip","4":"ctrlp-smarttabs.zip","src_id":"22702","5":"22702","creation_date":"1418726001","6":"1418726001"},{"0":"4797","vim_version":"7.0","1":"7.0","script_version":"0.4","2":"0.4","version_comment":"Highlighted selected tab","3":"Highlighted selected tab","package":"ctrlp-smarttabs.zip","4":"ctrlp-smarttabs.zip","src_id":"21277","5":"21277","creation_date":"1388961852","6":"1388961852"},{"0":"4797","vim_version":"7.0","1":"7.0","script_version":"0.3","2":"0.3","version_comment":"Added tab number to tab list","3":"Added tab number to tab list","package":"ctrlp-smarttabs.zip","4":"ctrlp-smarttabs.zip","src_id":"21262","5":"21262","creation_date":"1388444331","6":"1388444331"},{"0":"4797","vim_version":"7.0","1":"7.0","script_version":"0.2","2":"0.2","version_comment":"Now the plugin will switch to the appropriate window inside the appropriate tab.","3":"Now the plugin will switch to the appropriate window inside the appropriate tab.","package":"ctrlp-smarttabs.zip","4":"ctrlp-smarttabs.zip","src_id":"21200","5":"21200","creation_date":"1387202082","6":"1387202082"},{"0":"4797","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"ctrlp-smarttabs.zip","4":"ctrlp-smarttabs.zip","src_id":"21191","5":"21191","creation_date":"1387022682","6":"1387022682"}]},"4796":{"script_id":"4796","0":"4796","script_name":"vim-nfo","1":"vim-nfo","script_type":"ftplugin","2":"ftplugin","summary":"ftplugin for .nfo files","3":"ftplugin for .nfo files","description":"http:\/\/github.com\/smilekzs\/vim-nfo","4":"http:\/\/github.com\/smilekzs\/vim-nfo","install_details":"use vundle\/pathogen","5":"use vundle\/pathogen","first_name":"smilekzs","6":"smilekzs","last_name":"-","7":"-","releases":[{"0":"4796","vim_version":"7.0","1":"7.0","script_version":"0.1.0","2":"0.1.0","version_comment":"Initial upload","3":"Initial upload","package":"vim-nfo.zip","4":"vim-nfo.zip","src_id":"21190","5":"21190","creation_date":"1387003829","6":"1387003829"}]},"4795":{"script_id":"4795","0":"4795","script_name":"ExtractMatches","1":"ExtractMatches","script_type":"utility","2":"utility","summary":"Yank matches from range into a register.","3":"Yank matches from range into a register.","description":"DESCRIPTION\r\nThis plugin provides a toolbox of commands to copy all (or only unique first)\r\nsearch matches \/ matches of a passed pattern \/ entire lines matching, to a\r\nregister, or directly :put them into the buffer. The commands are easier to\r\nremember and quicker to type than the various idioms for that, and they are\r\nrobust, i.e. also support patterns spanning multiples lines.\r\n\r\nSOURCE\r\nImplementation inspired by\r\n    http:\/\/vim.wikia.com\/wiki\/Copy_the_search_results_into_clipboard\r\nUse case inspired from a post by Luc Hermitte at\r\n    http:\/\/www.reddit.com\/r\/vim\/comments\/ef9zh\/any_better_way_to_yank_all_lines_matching_pattern\/\r\n\r\nALTERNATIVES\r\nOne can employ a sub-replace-expression to capture the matches, as described\r\nin\r\n    http:\/\/stackoverflow.com\/questions\/9079561\/how-to-extract-regex-matches-using-vim\r\nThe idea is to use the side effect of add() in the expression, and force an\r\nempty return value from it through the inverse range of [1:0]. To avoid text\r\nmodification, we make the pattern match nothing by appending \/\\zs; with\r\nthis, \\0 will be empty, so we have to capture the match as \\1:\r\n    let t=[] | %s\/\\(fo*)\\zs\/\\=add(t, submatch(1))[1:0]\/g\r\nSince this has the side effect of setting 'modified', anyway, we can\r\nalternatively have add() return the last added element [-1]; this saves us\r\nfrom the zero-width match and capture:\r\n    let t=[] | %s\/fo*\/\\=add(t, submatch(0))[-1]\/g\r\n\r\nSEE ALSO\r\n- The PatternsOnText.vim plugin (vimscript #4602) provides commands that\r\n  print, substitute, or delete certain duplicates or matches directly in the\r\n  buffer.\r\n\r\nRELATED WORKS\r\n- The yankitute plugin (vimscript #4719) provides a similar\r\n  :[range]Yankitute[register]\/{pattern}\/[string]\/[flags]\/[join] command.\r\n- yankmatches\r\n  (https:\/\/github.com\/thoughtstream\/Damian-Conway-s-Vim-Setup\/blob\/master\/plugin\/yankmatches.vim)\r\n  can yank \/ delete entire lines with \/ without matches, similar to\r\n  :GrepToReg.\r\n\r\nUSAGE\r\nAll commands default to the entire buffer if the [range] is omitted.\r\n\r\n:[range]GrepToReg[!] \/{pattern}\/[x]\r\n:[range]GrepToReg[!] [{pattern}]\r\n                        Yank all lines in [range] that match {pattern} (or the\r\n                        last search pattern if omitted), with !: do not match,\r\n                        into register [x] (or the unnamed register).\r\n\r\n:[range]GrepRangeToReg[!] \/{pattern}\/ {range} [x]\r\n:[range]GrepRangeToReg[!] {range} [x]\r\n                        Yank all lines in [range] that match {pattern} (or the\r\n                        last search pattern if omitted), with !: do not match,\r\n                        and all lines in {range} around it, into register [x]\r\n                        (or the unnamed register).\r\n                        With this, you can emulate grep's context line control\r\n                        -A -B -C \/ --after-context --before-context --context\r\n                        (but without the \"--\" group separator).\r\n\r\n:[range]YankMatches[!] \/{pattern}\/[x]\r\n:[range]YankMatches[!] [{pattern}]\r\n                        Yank text matching {pattern} (or the last search\r\n                        pattern if omitted) in [range] into register [x] (or\r\n                        the unnamed register). Each match is put on a new\r\n                        line. This works like \"grep -o\". With [!]: Yank only\r\n                        the first match in each line.\r\n:[range]YankMatches[!] \/{pattern}\/{replacement}\/[x]\r\n                        Grab text matching {pattern} (or the last search\r\n                        pattern if omitted) in [range], and put {replacement}\r\n                        into register [x] (or the unnamed register). You can\r\n                        refer to the match via s\/\\& and submatches (s\/\\1).\r\n                        The matches are simply concatenated without a newline\r\n                        character here. Append \\n at {replacement} to have\r\n                        one. When {replacement} is \"&...\", ... is assumed to\r\n                        be a (literal) separator and is removed from the last\r\n                        element; if you don't want that, use \\0 instead of &.\r\n                        With [!]: Yank only the first match in each line.\r\n\r\n:[range]YankUniqueMatches[!] \/{pattern}\/[x]\r\n:[range]YankUniqueMatches[!] [{pattern}]\r\n                        Yank text matching {pattern} (or the last search\r\n                        pattern if omitted) in [range] into register [x] (or\r\n                        the unnamed register), but only once. Each match is\r\n                        put on a new line. With [!]: Yank only the first match\r\n                        in each line.\r\n:[range]YankUniqueMatches[!] \/{pattern}\/{replacement}\/[x]\r\n\r\n:[range]PrintMatches[!] \/{pattern}\/\r\n:[range]PrintMatches[!] [{pattern}]\r\n                        Print text matching {pattern} (or the last search\r\n                        pattern if omitted) in [range]. Each match is printed\r\n                        on a new line. This works like \"grep -o\". With [!]:\r\n                        Print only the first match in each line.\r\n:[range]PrintMatches[!] \/{pattern}\/{replacement}\/\r\n                        Like :YankMatches, but print the replacement instead\r\n                        of yanking.\r\n:[range]PrintUniqueMatches[!] \/{pattern}\/\r\n:[range]PrintUniqueMatches[!] [{pattern}]\r\n:[range]PrintUniqueMatches[!] \/{pattern}\/{replacement}\/\r\n                        Like :YankUniqueMatches, but print instead of\r\n                        yanking.\r\n\r\n:[range]SubstituteAndYank \/{pattern}\/{replacement}\/[flags]\/{yank-replacement}\/[x]\r\n                        Replace all matches of {pattern} in the current line \/\r\n                        [range] with {replacement}, like with :substitute\r\n                        (using [flags] as :s_flags), and put the\r\n                        {yank-replacement} (simply concatenated without a\r\n                        newline) into register [x] (or the unnamed register).\r\n                        Supports the same replacements as :YankMatches;\r\n                        additionally,  \\# is replaced with a (1-based) count\r\n                        of the current yank and in a sub-replace-expression,\r\n                        v:key stands for the 0-based index.\r\n\r\n:[range]SubstituteAndYankUnique \/{pattern}\/{replacement}\/[flags]\/{yank-replacement}\/[x]\r\n                        Like :SubstituteAndYank, but only add unique matches\r\n                        to the register. For non-unique matches, \\# and v:key\r\n                        refer to the corresponding existing match in the\r\n                        register.\r\n\r\n:[line]PutMatches[!] \/{pattern}\/\r\n:[line]PutMatches[!] [{pattern}]\r\n:[line]PutMatches[!] \/{pattern}\/{replacement}\/\r\n                        Put text matching {pattern} (or the last search pattern\r\n                        if omitted) after [line] (default current line). Each\r\n                        match is put on a new line (except when {replacement}\r\n                        is specified; see :YankMatches). This works like\r\n                        \"grep -o\".\r\n                        With [!]: Put only the first match in each line.\r\n                        Cp. :YankMatches.\r\n\r\n:[line]PutUniqueMatches[!] \/{pattern}\/\r\n:[line]PutUniqueMatches[!] [{pattern}]\r\n:[line]PutUniqueMatches[!] \/{pattern}\/{replacement}\/\r\n                        Put text matching {pattern} (or the last search pattern\r\n                        if omitted) after [line] (default current line). Each\r\n                        match is once put on a new line.\r\n                        With [!]: Put only the first match in each line.\r\n                        Cp. :YankUniqueMatches.","4":"DESCRIPTION\r\nThis plugin provides a toolbox of commands to copy all (or only unique first)\r\nsearch matches \/ matches of a passed pattern \/ entire lines matching, to a\r\nregister, or directly :put them into the buffer. The commands are easier to\r\nremember and quicker to type than the various idioms for that, and they are\r\nrobust, i.e. also support patterns spanning multiples lines.\r\n\r\nSOURCE\r\nImplementation inspired by\r\n    http:\/\/vim.wikia.com\/wiki\/Copy_the_search_results_into_clipboard\r\nUse case inspired from a post by Luc Hermitte at\r\n    http:\/\/www.reddit.com\/r\/vim\/comments\/ef9zh\/any_better_way_to_yank_all_lines_matching_pattern\/\r\n\r\nALTERNATIVES\r\nOne can employ a sub-replace-expression to capture the matches, as described\r\nin\r\n    http:\/\/stackoverflow.com\/questions\/9079561\/how-to-extract-regex-matches-using-vim\r\nThe idea is to use the side effect of add() in the expression, and force an\r\nempty return value from it through the inverse range of [1:0]. To avoid text\r\nmodification, we make the pattern match nothing by appending \/\\zs; with\r\nthis, \\0 will be empty, so we have to capture the match as \\1:\r\n    let t=[] | %s\/\\(fo*)\\zs\/\\=add(t, submatch(1))[1:0]\/g\r\nSince this has the side effect of setting 'modified', anyway, we can\r\nalternatively have add() return the last added element [-1]; this saves us\r\nfrom the zero-width match and capture:\r\n    let t=[] | %s\/fo*\/\\=add(t, submatch(0))[-1]\/g\r\n\r\nSEE ALSO\r\n- The PatternsOnText.vim plugin (vimscript #4602) provides commands that\r\n  print, substitute, or delete certain duplicates or matches directly in the\r\n  buffer.\r\n\r\nRELATED WORKS\r\n- The yankitute plugin (vimscript #4719) provides a similar\r\n  :[range]Yankitute[register]\/{pattern}\/[string]\/[flags]\/[join] command.\r\n- yankmatches\r\n  (https:\/\/github.com\/thoughtstream\/Damian-Conway-s-Vim-Setup\/blob\/master\/plugin\/yankmatches.vim)\r\n  can yank \/ delete entire lines with \/ without matches, similar to\r\n  :GrepToReg.\r\n\r\nUSAGE\r\nAll commands default to the entire buffer if the [range] is omitted.\r\n\r\n:[range]GrepToReg[!] \/{pattern}\/[x]\r\n:[range]GrepToReg[!] [{pattern}]\r\n                        Yank all lines in [range] that match {pattern} (or the\r\n                        last search pattern if omitted), with !: do not match,\r\n                        into register [x] (or the unnamed register).\r\n\r\n:[range]GrepRangeToReg[!] \/{pattern}\/ {range} [x]\r\n:[range]GrepRangeToReg[!] {range} [x]\r\n                        Yank all lines in [range] that match {pattern} (or the\r\n                        last search pattern if omitted), with !: do not match,\r\n                        and all lines in {range} around it, into register [x]\r\n                        (or the unnamed register).\r\n                        With this, you can emulate grep's context line control\r\n                        -A -B -C \/ --after-context --before-context --context\r\n                        (but without the \"--\" group separator).\r\n\r\n:[range]YankMatches[!] \/{pattern}\/[x]\r\n:[range]YankMatches[!] [{pattern}]\r\n                        Yank text matching {pattern} (or the last search\r\n                        pattern if omitted) in [range] into register [x] (or\r\n                        the unnamed register). Each match is put on a new\r\n                        line. This works like \"grep -o\". With [!]: Yank only\r\n                        the first match in each line.\r\n:[range]YankMatches[!] \/{pattern}\/{replacement}\/[x]\r\n                        Grab text matching {pattern} (or the last search\r\n                        pattern if omitted) in [range], and put {replacement}\r\n                        into register [x] (or the unnamed register). You can\r\n                        refer to the match via s\/\\& and submatches (s\/\\1).\r\n                        The matches are simply concatenated without a newline\r\n                        character here. Append \\n at {replacement} to have\r\n                        one. When {replacement} is \"&...\", ... is assumed to\r\n                        be a (literal) separator and is removed from the last\r\n                        element; if you don't want that, use \\0 instead of &.\r\n                        With [!]: Yank only the first match in each line.\r\n\r\n:[range]YankUniqueMatches[!] \/{pattern}\/[x]\r\n:[range]YankUniqueMatches[!] [{pattern}]\r\n                        Yank text matching {pattern} (or the last search\r\n                        pattern if omitted) in [range] into register [x] (or\r\n                        the unnamed register), but only once. Each match is\r\n                        put on a new line. With [!]: Yank only the first match\r\n                        in each line.\r\n:[range]YankUniqueMatches[!] \/{pattern}\/{replacement}\/[x]\r\n\r\n:[range]PrintMatches[!] \/{pattern}\/\r\n:[range]PrintMatches[!] [{pattern}]\r\n                        Print text matching {pattern} (or the last search\r\n                        pattern if omitted) in [range]. Each match is printed\r\n                        on a new line. This works like \"grep -o\". With [!]:\r\n                        Print only the first match in each line.\r\n:[range]PrintMatches[!] \/{pattern}\/{replacement}\/\r\n                        Like :YankMatches, but print the replacement instead\r\n                        of yanking.\r\n:[range]PrintUniqueMatches[!] \/{pattern}\/\r\n:[range]PrintUniqueMatches[!] [{pattern}]\r\n:[range]PrintUniqueMatches[!] \/{pattern}\/{replacement}\/\r\n                        Like :YankUniqueMatches, but print instead of\r\n                        yanking.\r\n\r\n:[range]SubstituteAndYank \/{pattern}\/{replacement}\/[flags]\/{yank-replacement}\/[x]\r\n                        Replace all matches of {pattern} in the current line \/\r\n                        [range] with {replacement}, like with :substitute\r\n                        (using [flags] as :s_flags), and put the\r\n                        {yank-replacement} (simply concatenated without a\r\n                        newline) into register [x] (or the unnamed register).\r\n                        Supports the same replacements as :YankMatches;\r\n                        additionally,  \\# is replaced with a (1-based) count\r\n                        of the current yank and in a sub-replace-expression,\r\n                        v:key stands for the 0-based index.\r\n\r\n:[range]SubstituteAndYankUnique \/{pattern}\/{replacement}\/[flags]\/{yank-replacement}\/[x]\r\n                        Like :SubstituteAndYank, but only add unique matches\r\n                        to the register. For non-unique matches, \\# and v:key\r\n                        refer to the corresponding existing match in the\r\n                        register.\r\n\r\n:[line]PutMatches[!] \/{pattern}\/\r\n:[line]PutMatches[!] [{pattern}]\r\n:[line]PutMatches[!] \/{pattern}\/{replacement}\/\r\n                        Put text matching {pattern} (or the last search pattern\r\n                        if omitted) after [line] (default current line). Each\r\n                        match is put on a new line (except when {replacement}\r\n                        is specified; see :YankMatches). This works like\r\n                        \"grep -o\".\r\n                        With [!]: Put only the first match in each line.\r\n                        Cp. :YankMatches.\r\n\r\n:[line]PutUniqueMatches[!] \/{pattern}\/\r\n:[line]PutUniqueMatches[!] [{pattern}]\r\n:[line]PutUniqueMatches[!] \/{pattern}\/{replacement}\/\r\n                        Put text matching {pattern} (or the last search pattern\r\n                        if omitted) after [line] (default current line). Each\r\n                        match is once put on a new line.\r\n                        With [!]: Put only the first match in each line.\r\n                        Cp. :YankUniqueMatches.","install_details":"INSTALLATION\r\nThe code is hosted in a Git repo at\r\n    https:\/\/github.com\/inkarkat\/vim-ExtractMatches\r\nYou can use your favorite plugin manager, or \"git clone\" into a directory used\r\nfor Vim packages. Releases are on the \"stable\" branch, the latest unstable\r\ndevelopment snapshot on \"master\".\r\n\r\nThis script is also packaged as a vimball. If you have the \"gunzip\"\r\ndecompressor in your PATH, simply edit the *.vmb.gz package in Vim; otherwise,\r\ndecompress the archive first, e.g. using WinZip. Inside Vim, install by\r\nsourcing the vimball or via the :UseVimball command.\r\n    vim ExtractMatches*.vmb.gz\r\n    :so %\r\nTo uninstall, use the :RmVimball command.\r\n\r\nDEPENDENCIES\r\n- Requires Vim 7.0 or higher.\r\n- Requires the ingo-library.vim plugin (vimscript #4433), version 1.035 or\r\n  higher.","5":"INSTALLATION\r\nThe code is hosted in a Git repo at\r\n    https:\/\/github.com\/inkarkat\/vim-ExtractMatches\r\nYou can use your favorite plugin manager, or \"git clone\" into a directory used\r\nfor Vim packages. Releases are on the \"stable\" branch, the latest unstable\r\ndevelopment snapshot on \"master\".\r\n\r\nThis script is also packaged as a vimball. If you have the \"gunzip\"\r\ndecompressor in your PATH, simply edit the *.vmb.gz package in Vim; otherwise,\r\ndecompress the archive first, e.g. using WinZip. Inside Vim, install by\r\nsourcing the vimball or via the :UseVimball command.\r\n    vim ExtractMatches*.vmb.gz\r\n    :so %\r\nTo uninstall, use the :RmVimball command.\r\n\r\nDEPENDENCIES\r\n- Requires Vim 7.0 or higher.\r\n- Requires the ingo-library.vim plugin (vimscript #4433), version 1.035 or\r\n  higher.","first_name":"Ingo","6":"Ingo","last_name":"Karkat","7":"Karkat","releases":[{"0":"4795","vim_version":"7.0","1":"7.0","script_version":"1.42","2":"1.42","version_comment":"- BUG: :Grep[Range]ToReg and :{Print,Yank}[Unique]Matches do not consider all lines when executed on a closed fold.\r\n- Adapt: :Put[Unique]Matches need to check <count> == -1 instead of <line2> to support current line as well as a lnum of 0 (since Vim 8.1.1241).","3":"- BUG: :Grep[Range]ToReg and :{Print,Yank}[Unique]Matches do not consider all lines when executed on a closed fold.\r\n- Adapt: :Put[Unique]Matches need to check <count> == -1 instead of <line2> to support current line as well as a lnum of 0 (since Vim 8.1.1241).","package":"ExtractMatches-1.42.vmb.gz","4":"ExtractMatches-1.42.vmb.gz","src_id":"27018","5":"27018","creation_date":"1582259700","6":"1582259700"},{"0":"4795","vim_version":"7.0","1":"7.0","script_version":"1.41","2":"1.41","version_comment":"- Move PatternsOnText#ReplaceSpecial(), and PatternsOnText#DefaultReplacer() to ingo-library.\r\n- Does not require the |PatternsOnText.vim| plugin (vimscript #4602), version 2.00 or higher for the :SubstituteAndYank[Unique] commands any longer. *** You need to update to ingo-library (vimscript #4433) version 1.035! ***","3":"- Move PatternsOnText#ReplaceSpecial(), and PatternsOnText#DefaultReplacer() to ingo-library.\r\n- Does not require the |PatternsOnText.vim| plugin (vimscript #4602), version 2.00 or higher for the :SubstituteAndYank[Unique] commands any longer. *** You need to update to ingo-library (vimscript #4433) version 1.035! ***","package":"ExtractMatches-1.41.vmb.gz","4":"ExtractMatches-1.41.vmb.gz","src_id":"26260","5":"26260","creation_date":"1541369879","6":"1541369879"},{"0":"4795","vim_version":"7.0","1":"7.0","script_version":"1.40","2":"1.40","version_comment":"- ENH: Add :GrepRangeToReg command.\r\n- :YankMatches does not handle magicness modifier atoms (\\v, \\M, etc.) before \/ after \\zs \/ \\ze. They get cut away, and then the remaining pattern does not match any longer, and a custom {replacement} is not applied. Normalize the magicness in the pattern. Additionally, also keep a case-sensitivity atom (\\c, \\C). Reported by bjornmelgaard on Stack Overflow. *** You need to update to ingo-library (vimscript #4433) version 1.029! ***","3":"- ENH: Add :GrepRangeToReg command.\r\n- :YankMatches does not handle magicness modifier atoms (\\v, \\M, etc.) before \/ after \\zs \/ \\ze. They get cut away, and then the remaining pattern does not match any longer, and a custom {replacement} is not applied. Normalize the magicness in the pattern. Additionally, also keep a case-sensitivity atom (\\c, \\C). Reported by bjornmelgaard on Stack Overflow. *** You need to update to ingo-library (vimscript #4433) version 1.029! ***","package":"ExtractMatches-1.40.vmb.gz","4":"ExtractMatches-1.40.vmb.gz","src_id":"24919","5":"24919","creation_date":"1485258192","6":"1485258192"},{"0":"4795","vim_version":"7.0","1":"7.0","script_version":"1.32","2":"1.32","version_comment":"- In PatternsOnText.vim version 2.0, PatternsOnText#Selected#ReplaceSpecial() has been moved to PatternsOnText#DefaultReplacer().","3":"- In PatternsOnText.vim version 2.0, PatternsOnText#Selected#ReplaceSpecial() has been moved to PatternsOnText#DefaultReplacer().","package":"ExtractMatches-1.32.vmb.gz","4":"ExtractMatches-1.32.vmb.gz","src_id":"24787","5":"24787","creation_date":"1481114131","6":"1481114131"},{"0":"4795","vim_version":"7.0","1":"7.0","script_version":"1.31","2":"1.31","version_comment":"- BUG: :GrepToReg runs into endless loop when the last line of the buffer belongs to the range and is matching.\r\n- Refactoring: Use ingo#cmdargs#pattern#ParseUnescaped(). *** You need to update to ingo-library (vimscript #4433) version 1.020! ***","3":"- BUG: :GrepToReg runs into endless loop when the last line of the buffer belongs to the range and is matching.\r\n- Refactoring: Use ingo#cmdargs#pattern#ParseUnescaped(). *** You need to update to ingo-library (vimscript #4433) version 1.020! ***","package":"ExtractMatches-1.31.vmb.gz","4":"ExtractMatches-1.31.vmb.gz","src_id":"22672","5":"22672","creation_date":"1417901896","6":"1417901896"},{"0":"4795","vim_version":"7.0","1":"7.0","script_version":"1.30","2":"1.30","version_comment":"- CHG: Rename :Yank[Unique]MatchesToReg to :Yank[Unique]Matches; the \"register\" part is implied by the yank.\r\n- CHG: Change default range of :SubstituteAndYank[Unique] to current line instead of buffer, to be consistent with :substitute and the :Substitute... commands defined by PatternsOnText.vim.\r\n- Add :Print[Unique]Matches variant of :Yank[Unique]Matches.\r\n- FIX: Inline pasting (with replacements) doesn't use the specified line and doesn't create a new empty line.\r\n- FIX: Typo in variable name prevented elimination of \\ze.\r\n- FIX: Remove escaping of a:replacement to apply the DWIM trailing separator removal also to \\\\, \\n, \\t etc.\r\n- Handle \\r, \\n, \\t, \\b in replacement, too.","3":"- CHG: Rename :Yank[Unique]MatchesToReg to :Yank[Unique]Matches; the \"register\" part is implied by the yank.\r\n- CHG: Change default range of :SubstituteAndYank[Unique] to current line instead of buffer, to be consistent with :substitute and the :Substitute... commands defined by PatternsOnText.vim.\r\n- Add :Print[Unique]Matches variant of :Yank[Unique]Matches.\r\n- FIX: Inline pasting (with replacements) doesn't use the specified line and doesn't create a new empty line.\r\n- FIX: Typo in variable name prevented elimination of \\ze.\r\n- FIX: Remove escaping of a:replacement to apply the DWIM trailing separator removal also to \\\\, \\n, \\t etc.\r\n- Handle \\r, \\n, \\t, \\b in replacement, too.","package":"ExtractMatches-1.30.vmb.gz","4":"ExtractMatches-1.30.vmb.gz","src_id":"21608","5":"21608","creation_date":"1394703796","6":"1394703796"},{"0":"4795","vim_version":"7.0","1":"7.0","script_version":"1.20","2":"1.20","version_comment":"- Add :SubstituteAndYank and :SubstituteAndYankUnique commands.\r\n- All commands now properly abort on errors.","3":"- Add :SubstituteAndYank and :SubstituteAndYankUnique commands.\r\n- All commands now properly abort on errors.","package":"ExtractMatches-1.20.vmb.gz","4":"ExtractMatches-1.20.vmb.gz","src_id":"21512","5":"21512","creation_date":"1392914229","6":"1392914229"},{"0":"4795","vim_version":"7.0","1":"7.0","script_version":"1.10","2":"1.10","version_comment":"- DWIM: When {replacement} is \"&...\", assume ... is a (literal) separator and remove it from the last element.\r\n- Add heuristic that drops \\zs, \\ze, and all location-aware atoms (like \\%v) for the separate substitution for {replacement}, to allow it to match. Beforehand, either nothing or the entire match have been wrongly returned as the result.","3":"- DWIM: When {replacement} is \"&...\", assume ... is a (literal) separator and remove it from the last element.\r\n- Add heuristic that drops \\zs, \\ze, and all location-aware atoms (like \\%v) for the separate substitution for {replacement}, to allow it to match. Beforehand, either nothing or the entire match have been wrongly returned as the result.","package":"ExtractMatches-1.10.vmb.gz","4":"ExtractMatches-1.10.vmb.gz","src_id":"21503","5":"21503","creation_date":"1392725837","6":"1392725837"},{"0":"4795","vim_version":"7.0","1":"7.0","script_version":"1.00","2":"1.00","version_comment":"Initial upload","3":"Initial upload","package":"ExtractMatches-1.00.vmb.gz","4":"ExtractMatches-1.00.vmb.gz","src_id":"21184","5":"21184","creation_date":"1386750241","6":"1386750241"}]},"4794":{"script_id":"4794","0":"4794","script_name":"AddCppClass_Plus","1":"AddCppClass_Plus","script_type":"ftplugin","2":"ftplugin","summary":"this plugin is to help you add a c++ class conveniently","3":"this plugin is to help you add a c++ class conveniently","description":"It's update form http:\/\/www.vim.org\/scripts\/script.php?script_id=2986\r\n, I fix some bug, add filename using underlined + lowercase letters  and header info\r\n\r\nIf you want header info.\r\nvimrc:\r\nlet g:DoxygenToolkit_authorName=\"Your name\"\r\nlet g:DoxygenToolkit_authorEmail=\"Your email\"\r\n\r\ncommand: \r\n:AddCppClass","4":"It's update form http:\/\/www.vim.org\/scripts\/script.php?script_id=2986\r\n, I fix some bug, add filename using underlined + lowercase letters  and header info\r\n\r\nIf you want header info.\r\nvimrc:\r\nlet g:DoxygenToolkit_authorName=\"Your name\"\r\nlet g:DoxygenToolkit_authorEmail=\"Your email\"\r\n\r\ncommand: \r\n:AddCppClass","install_details":"save to ~\/.vim\/plugin or ~\/vimfiles\/plugin","5":"save to ~\/.vim\/plugin or ~\/vimfiles\/plugin","first_name":"Angluca","6":"Angluca","last_name":"Ac","7":"Ac","releases":[{"0":"4794","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"AddCppClass_Plus.vim","4":"AddCppClass_Plus.vim","src_id":"21183","5":"21183","creation_date":"1386731747","6":"1386731747"}]},"4793":{"script_id":"4793","0":"4793","script_name":"easydir.vim","1":"easydir.vim","script_type":"utility","2":"utility","summary":"An easy way to create directories and files at the same time!","3":"An easy way to create directories and files at the same time!","description":"Using *easydir* is quite easy. Functionality remains the same for editing and\r\nsaving files, but now you can prepend nonexistent directories to the desired\r\nfile name to create them both.\r\n\r\nEXAMPLES\r\n\r\n:e new_directory\/new_file.txt        Edits a file called |new_file.txt|\r\n                                                      which is nested inside |new_directory|\r\n\r\n:sp new_directory\/new_file2.txt    Split a new window assign the file\r\n                                                      as |new_file2.txt| and\r\n                                                      create the directory |new_directory|\r\n\r\n:n new_dir\/another_dir\/file.txt       You can even nest multiple directories!\r\n\r\nThat's it! So *easy!*","4":"Using *easydir* is quite easy. Functionality remains the same for editing and\r\nsaving files, but now you can prepend nonexistent directories to the desired\r\nfile name to create them both.\r\n\r\nEXAMPLES\r\n\r\n:e new_directory\/new_file.txt        Edits a file called |new_file.txt|\r\n                                                      which is nested inside |new_directory|\r\n\r\n:sp new_directory\/new_file2.txt    Split a new window assign the file\r\n                                                      as |new_file2.txt| and\r\n                                                      create the directory |new_directory|\r\n\r\n:n new_dir\/another_dir\/file.txt       You can even nest multiple directories!\r\n\r\nThat's it! So *easy!*","install_details":"","5":"","first_name":"Doug","6":"Doug","last_name":"Yun","7":"Yun","releases":[{"0":"4793","vim_version":"7.0","1":"7.0","script_version":"1.2","2":"1.2","version_comment":"* Generalize check for protocols in path - https:\/\/github.com\/duggiefresh\/vim-easydir\/pull\/10\r\n","3":"* Generalize check for protocols in path - https:\/\/github.com\/duggiefresh\/vim-easydir\/pull\/10\r\n","package":"vim-easydir-1.2.zip","4":"vim-easydir-1.2.zip","src_id":"27002","5":"27002","creation_date":"1581991542","6":"1581991542"},{"0":"4793","vim_version":"7.0","1":"7.0","script_version":"1.1","2":"1.1","version_comment":"Version 1.1\r\n=========\r\n\r\n* Supports netrw's network protocols by @rr-\r\n* README update by @knowledgejunkie\r\n*Add \/doc\/tags to .gitignore by @lencioni","3":"Version 1.1\r\n=========\r\n\r\n* Supports netrw's network protocols by @rr-\r\n* README update by @knowledgejunkie\r\n*Add \/doc\/tags to .gitignore by @lencioni","package":"vim-easydir-1.1.zip","4":"vim-easydir-1.1.zip","src_id":"25531","5":"25531","creation_date":"1503781071","6":"1503781071"},{"0":"4793","vim_version":"7.0","1":"7.0","script_version":"1.0.1","2":"1.0.1","version_comment":"Minor corrections and bug fix for README and docs.\r\n\r\n* Use HTTPS for Pathogen installation within README. - Brett Chalupa\r\n* Remove duplicate tags from docs - Mark Wu","3":"Minor corrections and bug fix for README and docs.\r\n\r\n* Use HTTPS for Pathogen installation within README. - Brett Chalupa\r\n* Remove duplicate tags from docs - Mark Wu","package":"vim-easydir-1.0.1.zip","4":"vim-easydir-1.0.1.zip","src_id":"21265","5":"21265","creation_date":"1388523212","6":"1388523212"},{"0":"4793","vim_version":"7.0","1":"7.0","script_version":"1.0.0","2":"1.0.0","version_comment":"Initial upload","3":"Initial upload","package":"easydir.vim","4":"easydir.vim","src_id":"21179","5":"21179","creation_date":"1386560837","6":"1386560837"}]},"4792":{"script_id":"4792","0":"4792","script_name":"netgrep","1":"netgrep","script_type":"utility","2":"utility","summary":"vim plugin for grepping and finding on a remote server","3":"vim plugin for grepping and finding on a remote server","description":"Adds functions for Grepping and Finding files that are on a remote server. The files can then be edited using Netrw (which is built into most vim installs).\r\n\r\nThe canonical repository is on github at https:\/\/github.com\/sirbrillig\/netgrep\r\n","4":"Adds functions for Grepping and Finding files that are on a remote server. The files can then be edited using Netrw (which is built into most vim installs).\r\n\r\nThe canonical repository is on github at https:\/\/github.com\/sirbrillig\/netgrep\r\n","install_details":"If you're using Pathogen and have git installed, it's very simple; just clone the project into your ~\/.vim\/bundle\/ directory:\r\n\r\ncd ~\/.vim\/bundle\/ && git clone https:\/\/github.com\/sirbrillig\/netgrep","5":"If you're using Pathogen and have git installed, it's very simple; just clone the project into your ~\/.vim\/bundle\/ directory:\r\n\r\ncd ~\/.vim\/bundle\/ && git clone https:\/\/github.com\/sirbrillig\/netgrep","first_name":"Payton","6":"Payton","last_name":"Swick","7":"Swick","releases":[{"0":"4792","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"netgrep-1.0.zip","4":"netgrep-1.0.zip","src_id":"21178","5":"21178","creation_date":"1386548099","6":"1386548099"}]},"4791":{"script_id":"4791","0":"4791","script_name":"SwissCalc","1":"SwissCalc","script_type":"utility","2":"utility","summary":"A powerful interactive calculator for geeks","3":"A powerful interactive calculator for geeks","description":"SwissCalc is a powerful interactive calculator for programmer whilst inside Vim. SwissCalc wants to achieve two goals:\r\n\r\nconvenient\r\npowerful\r\n\r\nSwissCalc preserve as mush Vim functionality as possible. You can edit, move, edit, yank expressions for SwissCalc by Vim. It\\'s quite easy to open SwissCalc and edit expressions in Vim. SwissCalc has been tailored to act as a Read Eval Print Loop (REPL) and provides some convenient variables such as last evaluated result, pi, e and functions such as vars(), funcs(), help().\r\n\r\nSwissCalc supports three data types: integer, float, string(yes, I am serious). SwissCalc also provides many operations such as bitwise operation, exponention, factorial. SwissCalc is supplied many built-in functions, too. You can all many math functions such as log(), sqrt(), sin(), asin(), many string functions to manipulate string, for example base64 encoding\/decoding, md5\/sha digest, regular expression, url encoding\/decoding, time operattion. If you find that SwissCalc is missing functions that you would like to use, you can define your own functions easily by Python.\r\n\r\nSee more in https:\/\/github.com\/lightxue\/SwissCalc\r\n","4":"SwissCalc is a powerful interactive calculator for programmer whilst inside Vim. SwissCalc wants to achieve two goals:\r\n\r\nconvenient\r\npowerful\r\n\r\nSwissCalc preserve as mush Vim functionality as possible. You can edit, move, edit, yank expressions for SwissCalc by Vim. It\\'s quite easy to open SwissCalc and edit expressions in Vim. SwissCalc has been tailored to act as a Read Eval Print Loop (REPL) and provides some convenient variables such as last evaluated result, pi, e and functions such as vars(), funcs(), help().\r\n\r\nSwissCalc supports three data types: integer, float, string(yes, I am serious). SwissCalc also provides many operations such as bitwise operation, exponention, factorial. SwissCalc is supplied many built-in functions, too. You can all many math functions such as log(), sqrt(), sin(), asin(), many string functions to manipulate string, for example base64 encoding\/decoding, md5\/sha digest, regular expression, url encoding\/decoding, time operattion. If you find that SwissCalc is missing functions that you would like to use, you can define your own functions easily by Python.\r\n\r\nSee more in https:\/\/github.com\/lightxue\/SwissCalc\r\n","install_details":"","5":"","first_name":"Light","6":"Light","last_name":"Xue","7":"Xue","releases":[{"0":"4791","vim_version":"7.3","1":"7.3","script_version":"1.0.0","2":"1.0.0","version_comment":"Initial upload","3":"Initial upload","package":"SwissCalc.tar.bz2","4":"SwissCalc.tar.bz2","src_id":"21170","5":"21170","creation_date":"1386432348","6":"1386432348"}]},"4790":{"script_id":"4790","0":"4790","script_name":"gsl.vim","1":"gsl.vim","script_type":"syntax","2":"syntax","summary":"Resaltador de sintaxis para GNU SL","3":"Resaltador de sintaxis para GNU SL","description":"Resaltador de sintaxis para GNU SL.\r\nLa p\u00c3\u00a1gina oficial de GNU SL es: http:\/\/bit.ly\/gnusl\r\nLa p\u00c3\u00a1gina oficial de SL es http:\/\/www.cnc.una.py\/sl","4":"Resaltador de sintaxis para GNU SL.\r\nLa p\u00c3\u00a1gina oficial de GNU SL es: http:\/\/bit.ly\/gnusl\r\nLa p\u00c3\u00a1gina oficial de SL es http:\/\/www.cnc.una.py\/sl","install_details":"0. Descargar el script\r\n1. Crear el directorio $HOME\/.vim\/syntax\/, copiar aqu\u00c3\u00ad el script\r\n2. Crear el directorio $HOME\/.vim\/ftdetect\/, dentro del mismo crear un archivo gsl.vim con la siguiente linea: au BufRead,BufNewFile *.sl set filetype=gsl","5":"0. Descargar el script\r\n1. Crear el directorio $HOME\/.vim\/syntax\/, copiar aqu\u00c3\u00ad el script\r\n2. Crear el directorio $HOME\/.vim\/ftdetect\/, dentro del mismo crear un archivo gsl.vim con la siguiente linea: au BufRead,BufNewFile *.sl set filetype=gsl","first_name":"Eliseo","6":"Eliseo","last_name":"Ocampos","7":"Ocampos","releases":[{"0":"4790","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"gsl.vim","4":"gsl.vim","src_id":"21167","5":"21167","creation_date":"1386389477","6":"1386389477"}]},"4789":{"script_id":"4789","0":"4789","script_name":"Vim-CtrlSpace","1":"Vim-CtrlSpace","script_type":"utility","2":"utility","summary":"Vim Workspace Controller","3":"Vim Workspace Controller","description":"Vim-CtrlSpace is a great plugin that helps you to get more power from Vim while working with buffers, tabs, windows, and so on. It is meant to organize your Vim screen space and your workspace effectively. To accomplish that Vim-CtrlSpace introduces a concept of separated buffer lists per tab and provides a lot of power around that (buffer and file management, multiple workspaces stored on disk, fuzzy search, tab management, and more).\r\n\r\nIts name follows the convention of naming similar plugins after their default mappings (like Command-T or CtrlP). Obviously, the plugin mapping is by default Ctrl + Space.\r\n\r\nProject page: https:\/\/github.com\/szw\/vim-ctrlspace\r\nProject demo: https:\/\/www.youtube.com\/watch?v=09l92uwKupI","4":"Vim-CtrlSpace is a great plugin that helps you to get more power from Vim while working with buffers, tabs, windows, and so on. It is meant to organize your Vim screen space and your workspace effectively. To accomplish that Vim-CtrlSpace introduces a concept of separated buffer lists per tab and provides a lot of power around that (buffer and file management, multiple workspaces stored on disk, fuzzy search, tab management, and more).\r\n\r\nIts name follows the convention of naming similar plugins after their default mappings (like Command-T or CtrlP). Obviously, the plugin mapping is by default Ctrl + Space.\r\n\r\nProject page: https:\/\/github.com\/szw\/vim-ctrlspace\r\nProject demo: https:\/\/www.youtube.com\/watch?v=09l92uwKupI","install_details":"The plugin installation is really simple. You can use Vundle or Pathogen, or just clone the repository to your .vim directory. In case of Vundle, add:\r\n\r\nBundle \"szw\/vim-ctrlspace\" \r\n\r\nto you .vimrc.\r\n\r\nIf you want to increase fuzzy search speed, make sure you have decent Ruby bindings in your Vim enabled (compiled in). The plugin will try to use your Ruby if available by default.","5":"The plugin installation is really simple. You can use Vundle or Pathogen, or just clone the repository to your .vim directory. In case of Vundle, add:\r\n\r\nBundle \"szw\/vim-ctrlspace\" \r\n\r\nto you .vimrc.\r\n\r\nIf you want to increase fuzzy search speed, make sure you have decent Ruby bindings in your Vim enabled (compiled in). The plugin will try to use your Ruby if available by default.","first_name":"Szymon","6":"Szymon","last_name":"Wrozynski","7":"Wrozynski","releases":[{"0":"4789","vim_version":"7.3","1":"7.3","script_version":"4.0.0","2":"4.0.0","version_comment":"Next major release: https:\/\/www.youtube.com\/watch?v=U1hbGJm3J0g","3":"Next major release: https:\/\/www.youtube.com\/watch?v=U1hbGJm3J0g","package":"vim-ctrlspace.zip","4":"vim-ctrlspace.zip","src_id":"21876","5":"21876","creation_date":"1399714091","6":"1399714091"},{"0":"4789","vim_version":"7.3","1":"7.3","script_version":"3.2.4","2":"3.2.4","version_comment":"More movements in the list. Project root detection without depending on CWD. API extended with some workspace commands. Polished README file.","3":"More movements in the list. Project root detection without depending on CWD. API extended with some workspace commands. Polished README file.","package":"vim-ctrlspace.zip","4":"vim-ctrlspace.zip","src_id":"21187","5":"21187","creation_date":"1386810833","6":"1386810833"},{"0":"4789","vim_version":"7.3","1":"7.3","script_version":"3.2.2","2":"3.2.2","version_comment":"Improved fuzzy search smoothness. Added a Vim quit action. Several improvements.","3":"Improved fuzzy search smoothness. Added a Vim quit action. Several improvements.","package":"vim-ctrlspace.zip","4":"vim-ctrlspace.zip","src_id":"21175","5":"21175","creation_date":"1386528544","6":"1386528544"},{"0":"4789","vim_version":"7.3","1":"7.3","script_version":"3.1.9","2":"3.1.9","version_comment":"Initial upload","3":"Initial upload","package":"vim-ctrlspace.zip","4":"vim-ctrlspace.zip","src_id":"21164","5":"21164","creation_date":"1386269172","6":"1386269172"}]},"4788":{"script_id":"4788","0":"4788","script_name":"Vim-Kompleter","1":"Vim-Kompleter","script_type":"utility","2":"utility","summary":"A smart, fast, simple, and reliable keyword completion replacement for Vim","3":"A smart, fast, simple, and reliable keyword completion replacement for Vim","description":"A smart, fast, simple, and reliable keyword completion replacement for Vim.\r\n\r\nIt differs from the standard keyword completion by extensive usage of distance and frequency algorithms in order to perform keyword matching. Those algorithms are inspired by TextMate's keyword completion experiences.\r\n\r\nIt is written with K to emphasize its new approach to keyword completion.\r\n\r\nMore details you will find on the project page: https:\/\/github.com\/szw\/vim-kompleter","4":"A smart, fast, simple, and reliable keyword completion replacement for Vim.\r\n\r\nIt differs from the standard keyword completion by extensive usage of distance and frequency algorithms in order to perform keyword matching. Those algorithms are inspired by TextMate's keyword completion experiences.\r\n\r\nIt is written with K to emphasize its new approach to keyword completion.\r\n\r\nMore details you will find on the project page: https:\/\/github.com\/szw\/vim-kompleter","install_details":"In case of Pathogen, just clone the repo to your bundles directory:\r\n\r\ngit clone https:\/\/github.com\/szw\/vim-kompleter.git\r\n\r\nIf you prefer Vundle, add the following snippet to your .vimrc file and perform :BundleInstall:\r\n\r\nBundle \"szw\/vim-kompleter\"\r\n\r\nIn both cases you should restart Vim.","5":"In case of Pathogen, just clone the repo to your bundles directory:\r\n\r\ngit clone https:\/\/github.com\/szw\/vim-kompleter.git\r\n\r\nIf you prefer Vundle, add the following snippet to your .vimrc file and perform :BundleInstall:\r\n\r\nBundle \"szw\/vim-kompleter\"\r\n\r\nIn both cases you should restart Vim.","first_name":"Szymon","6":"Szymon","last_name":"Wrozynski","7":"Wrozynski","releases":[{"0":"4788","vim_version":"7.3","1":"7.3","script_version":"0.1.8","2":"0.1.8","version_comment":"Initial upload","3":"Initial upload","package":"vim-kompleter.zip","4":"vim-kompleter.zip","src_id":"21162","5":"21162","creation_date":"1386266328","6":"1386266328"}]},"4787":{"script_id":"4787","0":"4787","script_name":"vim-svngutter","1":"vim-svngutter","script_type":"utility","2":"utility","summary":"A plugin to put SVN diff info into the gutter ","3":"A plugin to put SVN diff info into the gutter ","description":"Removed in favour of Signify http:\/\/www.vim.org\/scripts\/script.php?script_id=4487","4":"Removed in favour of Signify http:\/\/www.vim.org\/scripts\/script.php?script_id=4487","install_details":"Removed in favour of Signify http:\/\/www.vim.org\/scripts\/script.php?script_id=4487","5":"Removed in favour of Signify http:\/\/www.vim.org\/scripts\/script.php?script_id=4487","first_name":"Andy","6":"Andy","last_name":"Betteridge","7":"Betteridge","releases":[{"0":"4787","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"First version","3":"First version","package":"vim-svngutter-0.1.zip","4":"vim-svngutter-0.1.zip","src_id":"21158","5":"21158","creation_date":"1386242218","6":"1386242218"}]},"4786":{"script_id":"4786","0":"4786","script_name":"update-time","1":"update-time","script_type":"utility","2":"utility","summary":"Automatic update Last Change time as you like!","3":"Automatic update Last Change time as you like!","description":"# vim-update-time\r\n\r\nAutomatic update Last Change time as you like!\r\n\r\n[New version](https:\/\/github.com\/QianChenglong\/vim-update-time)\r\n\r\n## Command\r\n\r\n- Toggle update time\r\n\r\n        :UpdateTimeToggle\r\n\r\n## Custome\r\n\r\n- Time stamp for search line to update\r\n\r\n        let g:update_time_time_stamp_leader = 'Last Change: '\r\n\r\n- Time format\r\n\r\n        let g:update_time_time_format = '%Y-%m-%d %H:%M:%S %Z'\r\n\r\n- Begin line number to search\r\n\r\n        let g:update_time_begin_line = 0\r\n\r\n- End line number to search\r\n\r\n        let g:update_time_end_line = 10\r\n\r\n- Default enable when save\r\n\r\n        let g:update_time_enable = 1\r\n","4":"# vim-update-time\r\n\r\nAutomatic update Last Change time as you like!\r\n\r\n[New version](https:\/\/github.com\/QianChenglong\/vim-update-time)\r\n\r\n## Command\r\n\r\n- Toggle update time\r\n\r\n        :UpdateTimeToggle\r\n\r\n## Custome\r\n\r\n- Time stamp for search line to update\r\n\r\n        let g:update_time_time_stamp_leader = 'Last Change: '\r\n\r\n- Time format\r\n\r\n        let g:update_time_time_format = '%Y-%m-%d %H:%M:%S %Z'\r\n\r\n- Begin line number to search\r\n\r\n        let g:update_time_begin_line = 0\r\n\r\n- End line number to search\r\n\r\n        let g:update_time_end_line = 10\r\n\r\n- Default enable when save\r\n\r\n        let g:update_time_enable = 1\r\n","install_details":"","5":"","first_name":"Qian","6":"Qian","last_name":"Chenglong","7":"Chenglong","releases":[{"0":"4786","vim_version":"7.0","1":"7.0","script_version":"0.1.1","2":"0.1.1","version_comment":"Update last change time When a file really modified","3":"Update last change time When a file really modified","package":"vim-update-time-0.1.1.zip","4":"vim-update-time-0.1.1.zip","src_id":"21153","5":"21153","creation_date":"1386217374","6":"1386217374"},{"0":"4786","vim_version":"7.0","1":"7.0","script_version":"0.1.0","2":"0.1.0","version_comment":"Initial upload","3":"Initial upload","package":"vim-update-time.tar.zip","4":"vim-update-time.tar.zip","src_id":"21151","5":"21151","creation_date":"1386166476","6":"1386166476"}]},"4785":{"script_id":"4785","0":"4785","script_name":"goyo.vim","1":"goyo.vim","script_type":"utility","2":"utility","summary":"Distraction-free writing in Vim","3":"Distraction-free writing in Vim","description":"goyo.vim (고요)\r\n===============\r\n\r\nDistraction-free writing in Vim.\r\n\r\nProject Home: https:\/\/github.com\/junegunn\/goyo.vim\r\nScreenshot: https:\/\/raw.github.com\/junegunn\/i\/master\/goyo.png\r\n\r\nUsage\r\n-----\r\n\r\n:Goyo [width]\r\n\r\nConfiguration\r\n-------------\r\n\r\n- g:goyo_width (default: 80)\r\n- g:goyo_margin_top (default: 4)\r\n- g:goyo_margin_bottom (default: 4)","4":"goyo.vim (고요)\r\n===============\r\n\r\nDistraction-free writing in Vim.\r\n\r\nProject Home: https:\/\/github.com\/junegunn\/goyo.vim\r\nScreenshot: https:\/\/raw.github.com\/junegunn\/i\/master\/goyo.png\r\n\r\nUsage\r\n-----\r\n\r\n:Goyo [width]\r\n\r\nConfiguration\r\n-------------\r\n\r\n- g:goyo_width (default: 80)\r\n- g:goyo_margin_top (default: 4)\r\n- g:goyo_margin_bottom (default: 4)","install_details":"Extract in ~\/.vim or use a plugin manager to install the latest version from junegunn\/goyo.vim","5":"Extract in ~\/.vim or use a plugin manager to install the latest version from junegunn\/goyo.vim","first_name":"Junegunn","6":"Junegunn","last_name":"Choi","7":"Choi","releases":[{"0":"4785","vim_version":"7.0","1":"7.0","script_version":"1.5.3","2":"1.5.3","version_comment":"Fixed rendering issue on urxvt","3":"Fixed rendering issue on urxvt","package":"goyo.zip","4":"goyo.zip","src_id":"21822","5":"21822","creation_date":"1398407336","6":"1398407336"},{"0":"4785","vim_version":"7.0","1":"7.0","script_version":"1.5.2","2":"1.5.2","version_comment":"Bug fixes.","3":"Bug fixes.","package":"goyo.zip","4":"goyo.zip","src_id":"21808","5":"21808","creation_date":"1398221111","6":"1398221111"},{"0":"4785","vim_version":"7.0","1":"7.0","script_version":"1.5.1","2":"1.5.1","version_comment":"Bug fixes","3":"Bug fixes","package":"goyo.zip","4":"goyo.zip","src_id":"21266","5":"21266","creation_date":"1388585942","6":"1388585942"},{"0":"4785","vim_version":"7.0","1":"7.0","script_version":"1.5","2":"1.5","version_comment":"Vim 7.0 compatibility","3":"Vim 7.0 compatibility","package":"goyo.zip","4":"goyo.zip","src_id":"21206","5":"21206","creation_date":"1387296927","6":"1387296927"},{"0":"4785","vim_version":"7.3","1":"7.3","script_version":"1.4","2":"1.4","version_comment":"- Added g:goyo_callbacks\r\n- Bug fixes","3":"- Added g:goyo_callbacks\r\n- Bug fixes","package":"goyo.zip","4":"goyo.zip","src_id":"21148","5":"21148","creation_date":"1386129967","6":"1386129967"},{"0":"4785","vim_version":"7.3","1":"7.3","script_version":"1.3","2":"1.3","version_comment":"- Fixed relativenumber issue when g:goyo_linenr is set\r\n- Changed to disable ruler as well","3":"- Fixed relativenumber issue when g:goyo_linenr is set\r\n- Changed to disable ruler as well","package":"goyo.zip","4":"goyo.zip","src_id":"21145","5":"21145","creation_date":"1386027047","6":"1386027047"},{"0":"4785","vim_version":"7.3","1":"7.3","script_version":"1.2","2":"1.2","version_comment":"- Fixed issues with vim-airline \/ vim-powerline \/ powerline\r\n- Added g:goyo_linenr option","3":"- Fixed issues with vim-airline \/ vim-powerline \/ powerline\r\n- Added g:goyo_linenr option","package":"goyo.zip","4":"goyo.zip","src_id":"21142","5":"21142","creation_date":"1385996213","6":"1385996213"},{"0":"4785","vim_version":"7.3","1":"7.3","script_version":"1.1","2":"1.1","version_comment":"Hide tilde(~)s on color schemes without background","3":"Hide tilde(~)s on color schemes without background","package":"goyo.zip","4":"goyo.zip","src_id":"21138","5":"21138","creation_date":"1385946775","6":"1385946775"},{"0":"4785","vim_version":"7.3","1":"7.3","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"goyo.zip","4":"goyo.zip","src_id":"21136","5":"21136","creation_date":"1385921159","6":"1385921159"}]},"4783":{"script_id":"4783","0":"4783","script_name":"npm.vim","1":"npm.vim","script_type":"utility","2":"utility","summary":"Run NPM commands in Vim.","3":"Run NPM commands in Vim.","description":"npm.vim makes it easy to run npm commands from Vim. It doesn't have any interesting features like errorlist integration yet.\r\n\r\nGlobal Commands:\r\n\r\n    :Npm <command> [options..]\r\n\r\nCalls `npm <command> [options]`. Commands can be tab-completed.\r\n\r\nGlobal Settings:\r\n\r\n    g:npm_background = 0\r\n\r\nIf set to non-zero, runs all commands in background (so you lose their output).\r\n\r\n    g:npm_custom_commands = []\r\n\r\nIf some NPM commands aren't being picked up, add them to this list.\r\n\r\nLicense:\r\n\r\nnpm.vim is released under the MIT license. See the comments at the head of npm.vim for the full license text, or the \"COPYING\" file you should have received with your copy of this software.","4":"npm.vim makes it easy to run npm commands from Vim. It doesn't have any interesting features like errorlist integration yet.\r\n\r\nGlobal Commands:\r\n\r\n    :Npm <command> [options..]\r\n\r\nCalls `npm <command> [options]`. Commands can be tab-completed.\r\n\r\nGlobal Settings:\r\n\r\n    g:npm_background = 0\r\n\r\nIf set to non-zero, runs all commands in background (so you lose their output).\r\n\r\n    g:npm_custom_commands = []\r\n\r\nIf some NPM commands aren't being picked up, add them to this list.\r\n\r\nLicense:\r\n\r\nnpm.vim is released under the MIT license. See the comments at the head of npm.vim for the full license text, or the \"COPYING\" file you should have received with your copy of this software.","install_details":"Download npm.vim.zip from http:\/\/www.vim.org\/scripts\/script.php?script_id=4783\r\n\r\nUnzip the zipfile. Copy plugin\/npm.vim to your .vim\/plugin\/ directory and doc\/npm.txt to your .vim\/doc\/ directory. Run `:helptags ~\/.vim\/doc` to build the docs as with other scripts.","5":"Download npm.vim.zip from http:\/\/www.vim.org\/scripts\/script.php?script_id=4783\r\n\r\nUnzip the zipfile. Copy plugin\/npm.vim to your .vim\/plugin\/ directory and doc\/npm.txt to your .vim\/doc\/ directory. Run `:helptags ~\/.vim\/doc` to build the docs as with other scripts.","first_name":"Thomas","6":"Thomas","last_name":"Allen","7":"Allen","releases":[{"0":"4783","vim_version":"7.0","1":"7.0","script_version":"0.1.3","2":"0.1.3","version_comment":"Fix bad global function definition, remove GitHub link.","3":"Fix bad global function definition, remove GitHub link.","package":"npm.vim.zip","4":"npm.vim.zip","src_id":"23393","5":"23393","creation_date":"1434471793","6":"1434471793"},{"0":"4783","vim_version":"7.0","1":"7.0","script_version":"0.1.2","2":"0.1.2","version_comment":"Fix silly settings bug.","3":"Fix silly settings bug.","package":"npm.vim.zip","4":"npm.vim.zip","src_id":"21129","5":"21129","creation_date":"1385779946","6":"1385779946"},{"0":"4783","vim_version":"7.0","1":"7.0","script_version":"0.1.1","2":"0.1.1","version_comment":"Cleanup and bugfixes.","3":"Cleanup and bugfixes.","package":"npm.vim.zip","4":"npm.vim.zip","src_id":"21119","5":"21119","creation_date":"1385532854","6":"1385532854"}]},"4782":{"script_id":"4782","0":"4782","script_name":"v2ex","1":"v2ex","script_type":"utility","2":"utility","summary":"v2ex for vim.","3":"v2ex for vim.","description":"v2ex for vim.\r\n\r\nrequires vim +python.\r\n\r\nusage:\r\n\r\n    :V2ex\r\n    :V2EX\r\n    :V2Ex\r\n    :V2eX\r\n","4":"v2ex for vim.\r\n\r\nrequires vim +python.\r\n\r\nusage:\r\n\r\n    :V2ex\r\n    :V2EX\r\n    :V2Ex\r\n    :V2eX\r\n","install_details":"download and cp v2ex.vim to .vim\/plugin\/","5":"download and cp v2ex.vim to .vim\/plugin\/","first_name":" ","6":" ","last_name":" solos","7":" solos","releases":[{"0":"4782","vim_version":"7.3","1":"7.3","script_version":"0.0.2","2":"0.0.2","version_comment":"use urllib2 if requests not installed.","3":"use urllib2 if requests not installed.","package":"v2ex.vim","4":"v2ex.vim","src_id":"21546","5":"21546","creation_date":"1393598137","6":"1393598137"},{"0":"4782","vim_version":"7.2","1":"7.2","script_version":"0.0.1","2":"0.0.1","version_comment":"Initial upload","3":"Initial upload","package":"v2ex.vim","4":"v2ex.vim","src_id":"21115","5":"21115","creation_date":"1385462733","6":"1385462733"}]},"4781":{"script_id":"4781","0":"4781","script_name":"RPN","1":"RPN","script_type":"utility","2":"utility","summary":"Vim RPN calculator","3":"Vim RPN calculator","description":"Examples:\r\n\r\necho Rpn#Eval( '2 3 +' )\r\nOr\r\necho Rpn#Eval( 2, 3, '+' )\r\n\r\nSuggested command:\r\ncom! -nargs=+ Rpn echo Rpn#Eval( <f-args> )\r\n\r\nThen, Rpn 2 3 + echoes the result.\r\n\r\nOperators:\r\n+\r\n-\r\n*\r\n\/\r\n%\r\n^\r\n\r\nCommands:\r\nd: duplicate last entry\r\nr: reverse last two entries\r\nv: square root the last entry\r\n\r\nSpecial:\r\nans: Replaces with the answer from the last entry\r\n","4":"Examples:\r\n\r\necho Rpn#Eval( '2 3 +' )\r\nOr\r\necho Rpn#Eval( 2, 3, '+' )\r\n\r\nSuggested command:\r\ncom! -nargs=+ Rpn echo Rpn#Eval( <f-args> )\r\n\r\nThen, Rpn 2 3 + echoes the result.\r\n\r\nOperators:\r\n+\r\n-\r\n*\r\n\/\r\n%\r\n^\r\n\r\nCommands:\r\nd: duplicate last entry\r\nr: reverse last two entries\r\nv: square root the last entry\r\n\r\nSpecial:\r\nans: Replaces with the answer from the last entry\r\n","install_details":"Put it in your autoload directory.","5":"Put it in your autoload directory.","first_name":"Salman","6":"Salman","last_name":"Halim","7":"Halim","releases":[{"0":"4781","vim_version":"7.0","1":"7.0","script_version":"1.5","2":"1.5","version_comment":"New commands:\r\n\r\nc: clear the stack\r\nf: print the entire stack\r\np: display the last entry on the stack (done by default at the end, anyway)\r\nk: set precision (number of decimal places)\r\nK: push the precision onto the stack\r\n!: replace the item with its negative value\r\nZ: replace the item with the number of characters it takes up (number of digits plus decimal point and negative sign)\r\nz: push the size of the current stack\r\nx: remove the entry (pop and destroy)\r\n\r\nNew special:\r\n\r\ntax: Equivalent to multiplying by g:Rpn_taxRate. For example, if you set g:Rpn_taxRate to 1.5, then executing 'Rpn 3 tax' is the same as 'Rpn 3 1.5 *' -- I use it for sales tax calculations\r\n","3":"New commands:\r\n\r\nc: clear the stack\r\nf: print the entire stack\r\np: display the last entry on the stack (done by default at the end, anyway)\r\nk: set precision (number of decimal places)\r\nK: push the precision onto the stack\r\n!: replace the item with its negative value\r\nZ: replace the item with the number of characters it takes up (number of digits plus decimal point and negative sign)\r\nz: push the size of the current stack\r\nx: remove the entry (pop and destroy)\r\n\r\nNew special:\r\n\r\ntax: Equivalent to multiplying by g:Rpn_taxRate. For example, if you set g:Rpn_taxRate to 1.5, then executing 'Rpn 3 tax' is the same as 'Rpn 3 1.5 *' -- I use it for sales tax calculations\r\n","package":"rpn.zip","4":"rpn.zip","src_id":"26351","5":"26351","creation_date":"1547613050","6":"1547613050"},{"0":"4781","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Left out a needed file *blush*","3":"Left out a needed file *blush*","package":"rpn.vmb","4":"rpn.vmb","src_id":"21104","5":"21104","creation_date":"1385408778","6":"1385408778"},{"0":"4781","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"rpn.vim","4":"rpn.vim","src_id":"21103","5":"21103","creation_date":"1385407540","6":"1385407540"}]},"4780":{"script_id":"4780","0":"4780","script_name":"bashizzle.vim","1":"bashizzle.vim","script_type":"utility","2":"utility","summary":"deadsimple snippet\/templating using bash","3":"deadsimple snippet\/templating using bash","description":"This plugin enables bash templates \/ filtering, aka the macgyver-style of using snippets.\r\nShellintegration is already possible using '!' and '.!' and such, but I wanted a faster \/ more templated way of doing things.\r\n\r\nSEE VIDEODEMO HERE: http:\/\/playterm.org\/r\/bashizzle-and-vim-1385374364\r\n\r\nFEATURES\r\n=========\r\n\r\n* full bashification of vim, if you are better at bashscripting compared to vimscript: this is for you\r\n* write a filename '\/etc\/motd'..and press CTRL-B, it'll just include that file in the current document\r\n* write 'snippet' and it will list the contents of ~\/.vim\/snippet   (snippet.vim compatible)\r\n* single-word-executables: write 'date' in vim..press CTRL-B, then it turns into 'Mon Nov 25 10:47:40 CET 2013' (it just ran '\/usr\/bin\/date' :)\r\n* UPDATE: filters! you can now postprocess your snippets or current vimdocument with easy bashscripts (extension .filter)\r\n* UPDATE: $CLASSNAME and $FILE are now passed to snippets\r\n* UPDATE: configurationfile ~\/.bashizzle for global search\/replace on every included snippet \r\n\r\nEXAMPLE\r\n========\r\nEnough featureboasting, show me something!\r\nOk, bashizzle can easily turn something like this: http:\/\/pastie.org\/8509238\r\ninto this: http:\/\/pastie.org\/8509252\r\nand optionally filter it with this: http:\/\/pastie.org\/8509293\r\n\r\ngiven that you properly configured your global search\/replace keywords in ~\/.bashizzle\r\n\r\nMake sure you watch the screencat above","4":"This plugin enables bash templates \/ filtering, aka the macgyver-style of using snippets.\r\nShellintegration is already possible using '!' and '.!' and such, but I wanted a faster \/ more templated way of doing things.\r\n\r\nSEE VIDEODEMO HERE: http:\/\/playterm.org\/r\/bashizzle-and-vim-1385374364\r\n\r\nFEATURES\r\n=========\r\n\r\n* full bashification of vim, if you are better at bashscripting compared to vimscript: this is for you\r\n* write a filename '\/etc\/motd'..and press CTRL-B, it'll just include that file in the current document\r\n* write 'snippet' and it will list the contents of ~\/.vim\/snippet   (snippet.vim compatible)\r\n* single-word-executables: write 'date' in vim..press CTRL-B, then it turns into 'Mon Nov 25 10:47:40 CET 2013' (it just ran '\/usr\/bin\/date' :)\r\n* UPDATE: filters! you can now postprocess your snippets or current vimdocument with easy bashscripts (extension .filter)\r\n* UPDATE: $CLASSNAME and $FILE are now passed to snippets\r\n* UPDATE: configurationfile ~\/.bashizzle for global search\/replace on every included snippet \r\n\r\nEXAMPLE\r\n========\r\nEnough featureboasting, show me something!\r\nOk, bashizzle can easily turn something like this: http:\/\/pastie.org\/8509238\r\ninto this: http:\/\/pastie.org\/8509252\r\nand optionally filter it with this: http:\/\/pastie.org\/8509293\r\n\r\ngiven that you properly configured your global search\/replace keywords in ~\/.bashizzle\r\n\r\nMake sure you watch the screencat above","install_details":"tested on only textmode..just unzip it in your homefolder:\r\n\r\ncd ~\r\nunzip bashizzle.zip\r\n  inflating: .vim\/bashizzle          \r\n  inflating: .vim\/plugin\/bashizzle.vim  \r\n  inflating: .vim\/snippets\/companyx.filter  \r\n  inflating: .vim\/snippets\/php\/class \r\nthats it","5":"tested on only textmode..just unzip it in your homefolder:\r\n\r\ncd ~\r\nunzip bashizzle.zip\r\n  inflating: .vim\/bashizzle          \r\n  inflating: .vim\/plugin\/bashizzle.vim  \r\n  inflating: .vim\/snippets\/companyx.filter  \r\n  inflating: .vim\/snippets\/php\/class \r\nthats it","first_name":"Leon","6":"Leon","last_name":"van Kammen","7":"van Kammen","releases":[{"0":"4780","vim_version":"7.0","1":"7.0","script_version":"0.66","2":"0.66","version_comment":"* bugfix: indentation fix\r\n* bugfix: remove filterline after filtering","3":"* bugfix: indentation fix\r\n* bugfix: remove filterline after filtering","package":"bashizzle.zip","4":"bashizzle.zip","src_id":"21116","5":"21116","creation_date":"1385473731","6":"1385473731"},{"0":"4780","vim_version":"7.0","1":"7.0","script_version":"0.6","2":"0.6","version_comment":"* added configurationfile\r\n* added filters (.filter files)\r\n* added example snippet + filter","3":"* added configurationfile\r\n* added filters (.filter files)\r\n* added example snippet + filter","package":"bashizzle.zip","4":"bashizzle.zip","src_id":"21114","5":"21114","creation_date":"1385456907","6":"1385456907"},{"0":"4780","vim_version":"7.0","1":"7.0","script_version":"0.5","2":"0.5","version_comment":"Initial upload","3":"Initial upload","package":"bashizzle.zip","4":"bashizzle.zip","src_id":"21102","5":"21102","creation_date":"1385373233","6":"1385373233"}]},"4779":{"script_id":"4779","0":"4779","script_name":"vim-slamhound","1":"vim-slamhound","script_type":"ftplugin","2":"ftplugin","summary":"Slamhound integration for vim.","3":"Slamhound integration for vim.","description":"Slamhound integration for vim.\r\n\r\nFirst install:\r\n\r\n        slamhound:      https:\/\/github.com\/technomancy\/slamhound\r\n        fireplace.vim:  https:\/\/github.com\/tpope\/vim-fireplace\r\n\r\nIf you are running Vim 7.3.802 or earlier, then you will also need to install\r\nthe Clojure runtime files:\r\n\r\n        https:\/\/github.com\/guns\/vim-clojure-static\r\n\r\nThen from a Clojure buffer run:\r\n\r\n        :Slamhound\r\n\r\nNo mappings are supplied, but a useful mapping may be:\r\n\r\n        nnoremap <LocalLeader>sh :Slamhound<CR>\r\n\r\nA function, slamhound#reconstruct(file, textwidth), is available for more\r\ngranular control.\r\n","4":"Slamhound integration for vim.\r\n\r\nFirst install:\r\n\r\n        slamhound:      https:\/\/github.com\/technomancy\/slamhound\r\n        fireplace.vim:  https:\/\/github.com\/tpope\/vim-fireplace\r\n\r\nIf you are running Vim 7.3.802 or earlier, then you will also need to install\r\nthe Clojure runtime files:\r\n\r\n        https:\/\/github.com\/guns\/vim-clojure-static\r\n\r\nThen from a Clojure buffer run:\r\n\r\n        :Slamhound\r\n\r\nNo mappings are supplied, but a useful mapping may be:\r\n\r\n        nnoremap <LocalLeader>sh :Slamhound<CR>\r\n\r\nA function, slamhound#reconstruct(file, textwidth), is available for more\r\ngranular control.\r\n","install_details":"","5":"","first_name":"Sung","6":"Sung","last_name":"Pae","7":"Pae","releases":[{"0":"4779","vim_version":"7.3","1":"7.3","script_version":"1","2":"1","version_comment":"Initial upload","3":"Initial upload","package":"vim-slamhound.tar.gz","4":"vim-slamhound.tar.gz","src_id":"21098","5":"21098","creation_date":"1385311811","6":"1385311811"}]},"4778":{"script_id":"4778","0":"4778","script_name":"QFEnter","1":"QFEnter","script_type":"utility","2":"utility","summary":"Open a Quickfix item in a window you choose","3":"Open a Quickfix item in a window you choose","description":"More information : https:\/\/github.com\/yssl\/QFEnter\r\n\r\nA normal mode example : https:\/\/f.cloud.github.com\/assets\/5915359\/1632228\/bb76dc72-5774-11e3-83d1-2933b95d5b81.gif\r\nA visual mode example : https:\/\/f.cloud.github.com\/assets\/5915359\/2006385\/61c6f720-8717-11e3-806b-d0f276af3ef9.gif\r\n\r\n# QFEnter\r\n\r\nQFEnter allows you to open a Quickfix item in a window you choose.\r\nYou can choose the window by giving it a focus just before jumping to Quickfix window.\r\nYou can also open multiple items at once by including them in the visual block.\r\n\r\n## Usage\r\n\r\nIn Quickfix window,\r\n\r\n<Enter>, <2-LeftMouse>  \r\nNormal mode : Open an item under cursor in a previously focused window.  \r\nVisual mode : Open items in visual block in a previously focused window. As a result, the last item appears in the window. \r\n\r\n<Leader><Enter>  \r\nNormal mode : Open an item under cursor in a new vertical split from a previously focused window.  \r\nVisual mode : Open items in visual block in a sequence of new vertical splits from a previously focused window.\r\n\r\n<Leader><Space>  \r\nNormal mode : Open an item under cursor in a new horizontal split from a previously focused window.  \r\nVisual mode : Open items in visual block in a sequence of new horizontal splits from a previously focused window.\r\n\r\n<Leader><Tab>  \r\nNormal mode : Open an item under cursor in a new tab.  \r\nVisual mode : Open items in visual block in a sequence of new tabs.  \r\nQuickfix window is automatically opened in the new tab to help you open other Quickfix items.\r\n\r\nYou can change the key mappings in your .vimrc. The default setting is, \r\n```\r\nlet g:qfenter_keymap = {}\r\nlet g:qfenter_keymap.open = ['<CR>', '<2-LeftMouse>']\r\nlet g:qfenter_keymap.vopen = ['<Leader><CR>']\r\nlet g:qfenter_keymap.hopen = ['<Leader><Space>']\r\nlet g:qfenter_keymap.topen = ['<Leader><Tab>']\r\n```\r\n\r\nIf you're a [CtrlP] user, for instance, you might like these for familiarity:\r\n```\r\nlet g:qfenter_keymap = {}\r\nlet g:qfenter_keymap.vopen = ['<C-v>']\r\nlet g:qfenter_keymap.hopen = ['<C-CR>', '<C-s>', '<C-x>']\r\nlet g:qfenter_keymap.topen = ['<C-t>']\r\n```\r\n\r\n## Motivation\r\n\r\nDefault opening methods for QuickFix items are quite inconvenient,\r\n\r\n- You cannot select a window in which a file is opened when you press `<Enter>` in Quickfix.  \r\n\r\n  > Hitting the <Enter> key or double-clicking the mouse on a line has the same effect. The\r\nfile containing the error is opened in the window above the quickfix window.  \r\n`:help quickfix` \r\n\r\n  It is inconsistent with other Quickfix commands like `:cnext` and `:cprev` which open a file in a previously focused window.\r\n\r\n- You also cannot specify the window when you use `Ctrl-W <Enter>`, \r\nbecause Vim always create a new horizontal split window above Quickfix window and open a file in it.\r\nThere is even no command for 'open in new vertical split window'.\r\n\r\nThey are confusing and bother me every time, so I wrote a simple plugin to make up for these weak points.\r\nIt's name comes from the most basic way to open a file from Quickfix window - the `<Enter>` key.","4":"More information : https:\/\/github.com\/yssl\/QFEnter\r\n\r\nA normal mode example : https:\/\/f.cloud.github.com\/assets\/5915359\/1632228\/bb76dc72-5774-11e3-83d1-2933b95d5b81.gif\r\nA visual mode example : https:\/\/f.cloud.github.com\/assets\/5915359\/2006385\/61c6f720-8717-11e3-806b-d0f276af3ef9.gif\r\n\r\n# QFEnter\r\n\r\nQFEnter allows you to open a Quickfix item in a window you choose.\r\nYou can choose the window by giving it a focus just before jumping to Quickfix window.\r\nYou can also open multiple items at once by including them in the visual block.\r\n\r\n## Usage\r\n\r\nIn Quickfix window,\r\n\r\n<Enter>, <2-LeftMouse>  \r\nNormal mode : Open an item under cursor in a previously focused window.  \r\nVisual mode : Open items in visual block in a previously focused window. As a result, the last item appears in the window. \r\n\r\n<Leader><Enter>  \r\nNormal mode : Open an item under cursor in a new vertical split from a previously focused window.  \r\nVisual mode : Open items in visual block in a sequence of new vertical splits from a previously focused window.\r\n\r\n<Leader><Space>  \r\nNormal mode : Open an item under cursor in a new horizontal split from a previously focused window.  \r\nVisual mode : Open items in visual block in a sequence of new horizontal splits from a previously focused window.\r\n\r\n<Leader><Tab>  \r\nNormal mode : Open an item under cursor in a new tab.  \r\nVisual mode : Open items in visual block in a sequence of new tabs.  \r\nQuickfix window is automatically opened in the new tab to help you open other Quickfix items.\r\n\r\nYou can change the key mappings in your .vimrc. The default setting is, \r\n```\r\nlet g:qfenter_keymap = {}\r\nlet g:qfenter_keymap.open = ['<CR>', '<2-LeftMouse>']\r\nlet g:qfenter_keymap.vopen = ['<Leader><CR>']\r\nlet g:qfenter_keymap.hopen = ['<Leader><Space>']\r\nlet g:qfenter_keymap.topen = ['<Leader><Tab>']\r\n```\r\n\r\nIf you're a [CtrlP] user, for instance, you might like these for familiarity:\r\n```\r\nlet g:qfenter_keymap = {}\r\nlet g:qfenter_keymap.vopen = ['<C-v>']\r\nlet g:qfenter_keymap.hopen = ['<C-CR>', '<C-s>', '<C-x>']\r\nlet g:qfenter_keymap.topen = ['<C-t>']\r\n```\r\n\r\n## Motivation\r\n\r\nDefault opening methods for QuickFix items are quite inconvenient,\r\n\r\n- You cannot select a window in which a file is opened when you press `<Enter>` in Quickfix.  \r\n\r\n  > Hitting the <Enter> key or double-clicking the mouse on a line has the same effect. The\r\nfile containing the error is opened in the window above the quickfix window.  \r\n`:help quickfix` \r\n\r\n  It is inconsistent with other Quickfix commands like `:cnext` and `:cprev` which open a file in a previously focused window.\r\n\r\n- You also cannot specify the window when you use `Ctrl-W <Enter>`, \r\nbecause Vim always create a new horizontal split window above Quickfix window and open a file in it.\r\nThere is even no command for 'open in new vertical split window'.\r\n\r\nThey are confusing and bother me every time, so I wrote a simple plugin to make up for these weak points.\r\nIt's name comes from the most basic way to open a file from Quickfix window - the `<Enter>` key.","install_details":"- Using plugin managers (recommended)\r\n    - [Vundle] : Add `Bundle 'yssl\/QFEnter'` to .vimrc & `:BundleInstall`\r\n    - [NeoBundle] : Add `NeoBundle 'yssl\/QFEnter'` to .vimrc & `:NeoBundleInstall`\r\n    - [vim-plug] : Add `Plug 'yssl\/QFEnter'` to .vimrc & `:PlugInstall`\r\n- Using [Pathogen]\r\n    - `cd ~\/.vim\/bundle; git clone https:\/\/github.com\/yssl\/QFEnter.git`\r\n- Manual install (not recommended)\r\n    - Download this plugin and extract it in `~\/.vim\/`","5":"- Using plugin managers (recommended)\r\n    - [Vundle] : Add `Bundle 'yssl\/QFEnter'` to .vimrc & `:BundleInstall`\r\n    - [NeoBundle] : Add `NeoBundle 'yssl\/QFEnter'` to .vimrc & `:NeoBundleInstall`\r\n    - [vim-plug] : Add `Plug 'yssl\/QFEnter'` to .vimrc & `:PlugInstall`\r\n- Using [Pathogen]\r\n    - `cd ~\/.vim\/bundle; git clone https:\/\/github.com\/yssl\/QFEnter.git`\r\n- Manual install (not recommended)\r\n    - Download this plugin and extract it in `~\/.vim\/`","first_name":"Yoonsang","6":"Yoonsang","last_name":"Lee","7":"Lee","releases":[{"0":"4778","vim_version":"7.0","1":"7.0","script_version":"2.4.3","2":"2.4.3","version_comment":"Add a new option g:qfenter_autoclose and deprecate g:qfenter_enable_autoquickfix. Thanks for the suggestion auto-close quickfix, minhduc0711!","3":"Add a new option g:qfenter_autoclose and deprecate g:qfenter_enable_autoquickfix. Thanks for the suggestion auto-close quickfix, minhduc0711!","package":"QFEnter.zip","4":"QFEnter.zip","src_id":"28217","5":"28217","creation_date":"1665907820","6":"1665907820"},{"0":"4778","vim_version":"7.0","1":"7.0","script_version":"2.4.2","2":"2.4.2","version_comment":"- Change the default value of g:qfenter_excluded_action to 'next'\r\n- Fix the behavior in the case of undefined g:qfenter_excluded_action and g:qfenter_prevtabwin_policy\r\n- Add option to use next window when excluded. Thanks for the PR, mmrwoods!\r\n- Fix g:qfenter_prevtabwin_policy behavior when switchbuf=usetab or useopen is used\r\n  and fix a bug with 'open' cmds. Thanks for the suggestions, Konfekt!\r\n- Fix prevtabwin_policy tag name in doc. Thanks for the PR, tssm!","3":"- Change the default value of g:qfenter_excluded_action to 'next'\r\n- Fix the behavior in the case of undefined g:qfenter_excluded_action and g:qfenter_prevtabwin_policy\r\n- Add option to use next window when excluded. Thanks for the PR, mmrwoods!\r\n- Fix g:qfenter_prevtabwin_policy behavior when switchbuf=usetab or useopen is used\r\n  and fix a bug with 'open' cmds. Thanks for the suggestions, Konfekt!\r\n- Fix prevtabwin_policy tag name in doc. Thanks for the PR, tssm!","package":"QFEnter.zip","4":"QFEnter.zip","src_id":"28216","5":"28216","creation_date":"1665839129","6":"1665839129"},{"0":"4778","vim_version":"7.0","1":"7.0","script_version":"2.4.1","2":"2.4.1","version_comment":"2.4.1\r\n    Add an option for the policy to determine the previous window \/ tab' - g:qfenter_custom_map_list. Thanks for the suggestions, Konfekt and mckellyln!\r\n\r\n2.4.0\r\n    Remove the deprecated commands from 2.3.0: g:qfenter_*_map, g:qfenter_keep_quickfixfocus\r\n    Support custom functions to specify target window through g:qfenter_custom_map_list. Thanks to p0deje!\r\n    Add an option to prevent quickfix items from opening in windows of certain filetypes. Thanks to lsaint!","3":"2.4.1\r\n    Add an option for the policy to determine the previous window \/ tab' - g:qfenter_custom_map_list. Thanks for the suggestions, Konfekt and mckellyln!\r\n\r\n2.4.0\r\n    Remove the deprecated commands from 2.3.0: g:qfenter_*_map, g:qfenter_keep_quickfixfocus\r\n    Support custom functions to specify target window through g:qfenter_custom_map_list. Thanks to p0deje!\r\n    Add an option to prevent quickfix items from opening in windows of certain filetypes. Thanks to lsaint!","package":"QFEnter.zip","4":"QFEnter.zip","src_id":"27321","5":"27321","creation_date":"1602076228","6":"1602076228"},{"0":"4778","vim_version":"7.0","1":"7.0","script_version":"2.3.1","2":"2.3.1","version_comment":"    - Bug fix for deprecated variable(g:qfenter_keep_quickfixfocus) checking.\r\n    - Update documents for customization.","3":"    - Bug fix for deprecated variable(g:qfenter_keep_quickfixfocus) checking.\r\n    - Update documents for customization.","package":"QFEnter.zip","4":"QFEnter.zip","src_id":"25009","5":"25009","creation_date":"1488576895","6":"1488576895"},{"0":"4778","vim_version":"7.0","1":"7.0","script_version":"2.3.0","2":"2.3.0","version_comment":"- Key mapping setup has totally changed for more flexible customizing.","3":"- Key mapping setup has totally changed for more flexible customizing.","package":"QFEnter.zip","4":"QFEnter.zip","src_id":"25003","5":"25003","creation_date":"1488250452","6":"1488250452"},{"0":"4778","vim_version":"7.0","1":"7.0","script_version":"2.2.2","2":"2.2.2","version_comment":"- Avoid messages when mappings are executed.\r\n- E553 of cn & cp commands\r\n- Modelines, clean up vimdoc formatting and edit text\r\n- Support location list","3":"- Avoid messages when mappings are executed.\r\n- E553 of cn & cp commands\r\n- Modelines, clean up vimdoc formatting and edit text\r\n- Support location list","package":"QFEnter.zip","4":"QFEnter.zip","src_id":"23310","5":"23310","creation_date":"1432593852","6":"1432593852"},{"0":"4778","vim_version":"7.0","1":"7.0","script_version":"2.2.1","2":"2.2.1","version_comment":"- now QFEnter supports vim's 'switchbuf' option.\r\n  if you change 'switchbuf' option, QFEnter adapts its behavior to the changed option.\r\n- thanks to sergey-vlasov!\r\n- update document for 'switchbuf' option.","3":"- now QFEnter supports vim's 'switchbuf' option.\r\n  if you change 'switchbuf' option, QFEnter adapts its behavior to the changed option.\r\n- thanks to sergey-vlasov!\r\n- update document for 'switchbuf' option.","package":"QFEnter.zip","4":"QFEnter.zip","src_id":"21626","5":"21626","creation_date":"1395020757","6":"1395020757"},{"0":"4778","vim_version":"7.0","1":"7.0","script_version":"2.1.0","2":"2.1.0","version_comment":"\t- subdivide g:qfenter_keep_quickfixfocus option for each command. \r\n\t  e.g. g:qfenter_keep_quickfixfocus.open, g:qfenter_keep_quickfixfocus.cnext,\r\n\t  g:qfenter_keep_quickfixfocus.cprev\r\n\t- bug fix : not updated window for already opened file when g:qfenter_keep_quickfixfocus==1\r\n\t- thanks for mMontu!\r\n","3":"\t- subdivide g:qfenter_keep_quickfixfocus option for each command. \r\n\t  e.g. g:qfenter_keep_quickfixfocus.open, g:qfenter_keep_quickfixfocus.cnext,\r\n\t  g:qfenter_keep_quickfixfocus.cprev\r\n\t- bug fix : not updated window for already opened file when g:qfenter_keep_quickfixfocus==1\r\n\t- thanks for mMontu!\r\n","package":"QFEnter.zip","4":"QFEnter.zip","src_id":"21391","5":"21391","creation_date":"1390874118","6":"1390874118"},{"0":"4778","vim_version":"7.0","1":"7.0","script_version":"2.0.0","2":"2.0.0","version_comment":"- visual mode support to open multiple Quickfix items at once\r\n- add option to keep focus in Quicifix window after opening items  (g:qfenter_keep_quickfixfocus)\r\n- support :cnext and :cprev command to open items","3":"- visual mode support to open multiple Quickfix items at once\r\n- add option to keep focus in Quicifix window after opening items  (g:qfenter_keep_quickfixfocus)\r\n- support :cnext and :cprev command to open items","package":"QFEnter.zip","4":"QFEnter.zip","src_id":"21387","5":"21387","creation_date":"1390802688","6":"1390802688"},{"0":"4778","vim_version":"7.0","1":"7.0","script_version":"1.3.0","2":"1.3.0","version_comment":"improve features\r\n  - improve auto quickfix open when 'open in new tab'\r\n    - restore view(cursor position, scroll..) of quickfix window to auto-opened quickfix window\r\n    - restore size of quickfix window to auto-opened quickfix window\r\n    - now you don't need to provide g:qfenter_copen_modifier option. QFEnter now smartly determine whether the new quickfix window is botright or topleft, vertical or horizontal.\r\n  - change g:qfenter_ttopen_map option name to g:qfenter_topen_map (backward compatibility maintained)\r\n  - remove '<Tab><Tab>' from default mapping\r\n","3":"improve features\r\n  - improve auto quickfix open when 'open in new tab'\r\n    - restore view(cursor position, scroll..) of quickfix window to auto-opened quickfix window\r\n    - restore size of quickfix window to auto-opened quickfix window\r\n    - now you don't need to provide g:qfenter_copen_modifier option. QFEnter now smartly determine whether the new quickfix window is botright or topleft, vertical or horizontal.\r\n  - change g:qfenter_ttopen_map option name to g:qfenter_topen_map (backward compatibility maintained)\r\n  - remove '<Tab><Tab>' from default mapping\r\n","package":"QFEnter-1.3.0.zip","4":"QFEnter-1.3.0.zip","src_id":"21181","5":"21181","creation_date":"1386629553","6":"1386629553"},{"0":"4778","vim_version":"7.0","1":"7.0","script_version":"1.2.0","2":"1.2.0","version_comment":"    - now, Quickfix window is automatically opened after \"open in a new tab\"\r\n    - add options about Quickfix auto opening\r\n    - add one more default mapping for \"open in a new tab\"\r\n    - code refactoring\r\n","3":"    - now, Quickfix window is automatically opened after \"open in a new tab\"\r\n    - add options about Quickfix auto opening\r\n    - add one more default mapping for \"open in a new tab\"\r\n    - code refactoring\r\n","package":"QFEnter-1.2.0.zip","4":"QFEnter-1.2.0.zip","src_id":"21173","5":"21173","creation_date":"1386480558","6":"1386480558"},{"0":"4778","vim_version":"7.0","1":"7.0","script_version":"1.1.1","2":"1.1.1","version_comment":"    - change default mapping for \"open a file in a new tab\"","3":"    - change default mapping for \"open a file in a new tab\"","package":"QFEnter-1.1.1.zip","4":"QFEnter-1.1.1.zip","src_id":"21165","5":"21165","creation_date":"1386295137","6":"1386295137"},{"0":"4778","vim_version":"7.0","1":"7.0","script_version":"1.1.0","2":"1.1.0","version_comment":"- add new feature\r\n     : open a file under cursor in new tab window.\r\n     : register custom \"cc\" command with g:qfenter_cc_cmd\r\n","3":"- add new feature\r\n     : open a file under cursor in new tab window.\r\n     : register custom \"cc\" command with g:qfenter_cc_cmd\r\n","package":"QFEnter.zip","4":"QFEnter.zip","src_id":"21163","5":"21163","creation_date":"1386267397","6":"1386267397"},{"0":"4778","vim_version":"7.0","1":"7.0","script_version":"1.0.0","2":"1.0.0","version_comment":"Initial upload","3":"Initial upload","package":"QFEnter.zip","4":"QFEnter.zip","src_id":"21096","5":"21096","creation_date":"1385226966","6":"1385226966"}]},"4777":{"script_id":"4777","0":"4777","script_name":"repeatableMapping","1":"repeatableMapping","script_type":"utility","2":"utility","summary":"Set up mappings that can be repeated via repeat.vim.","3":"Set up mappings that can be repeated via repeat.vim.","description":"DESCRIPTION\r\nThis plugin simplifies the application of the repeat.vim and visualrepeat.vim\r\nrepeat functionality to existing mappings. As with repeat.vim, all\r\nembellishments are optional; if the corresponding plugin isn't available, the\r\ncall will be ignored and the original mappings persist unchanged (though\r\nwithout any repeat functionality).\r\n\r\nRETROFIT MAPPING REPETITION\r\nSome plugins provide out-of-the-box support for repeat.vim, many do not.\r\nSome mappings have been developed in an ad-hoc fashion, e.g. as custom\r\nfiletype-specific workflow shortcuts, and therefore do not have the\r\ncanonical remapping layer of <Plug> mappings (which repeat.vim requires).\r\n\r\nThis plugin allows to retrofit repeatability to mappings from plugins that\r\ndo not directly use repeat.vim. It also offers a succinct way for custom\r\nmappings to acquire repeatability, and spares them the definition of\r\n<Plug>-mappings and adding the repeat#set() boilerplate code themselves.\r\n\r\nVISUAL MODE REPETITION\r\nrepeat.vim only supports normal mode repetition, as this is the only\r\nrepetition that is built into Vim. However, one can define repetition in\r\nvisual mode:\r\n    xnoremap . :normal .<CR>\r\nor with pass-through of [count]:\r\n    xnoremap . :execute 'normal' (v:count ? v:count : '') . '.'<CR>\r\n(Or better a more fancy version that only applies the repeat command over\r\nentire lines in linewise visual mode, keeps the current cursor position in\r\ncharacterwise visual mode, and does nothing (sensible) in blockwise visual\r\nmode. The visualrepeat.vim plugin provides this.)\r\n\r\nThe <Plug>(ReenterVisualMode) mapping allows to apply repeat.vim repetition to\r\nvisual mode commands; just prepend it in the call to repeat#set():\r\n    vnoremap <silent> <Plug>MyMapping ...:silent! call repeat#set(\"\\<Plug>(ReenterVisualMode)\\<Plug>MyMapping\")<CR>\r\n\r\nIf a previously used visual mode mapping is repeated from an active visual\r\nselection, that selection is the affected area for the repetition. The\r\nrecorded repeat count is passed to the mapping.\r\n\r\nIf repetition is invoked in normal mode, the repetition works on a new\r\nselection, depending on the last visual mode:\r\n- For linewise selections, the repetition selects the current line.\r\n- For characterwise selections, a new selection starting at the cursor\r\n  position, with the same size as the last visual selection is used. 1v\r\nA [count] is passed to the mapping and overrides the recorded one.\r\n\r\nIf a non-visual mode mapping is repeated from an active visual selection, it\r\nwon't (can't) apply to the visual selection, but to whatever that mapping\r\ntypically applies. So, you can only repeat previous visual mode mappings on\r\na visual selection! The only way around this is to cross-link both mapping\r\ntypes, and to use a more intelligent version of the repeat definition in\r\nvisual mode. This is described next:\r\n\r\nCROSS-REPEAT\r\nThrough the visualrepeat.vim plugin, it is possible to make normal mode and\r\nvisual mode mappings repeat each other, with the normal mode mapping repeated\r\nover the visual selection, and the visual mode mapping repeated over a new\r\nselection, such as:\r\n- For previous linewise selections, the repetition applies to the same amount\r\n  of lines, unless a different [count] is given. In that case, it selects\r\n  [count] lines starting at the cursor position.\r\n- Else, a new selection starting at the cursor position, with the same size as\r\n  the last visual selection (times [count], if given and different) is used.\r\n  1v\r\nThe mapping itself is always repeated with the recorded [count], not a new\r\ngiven one. For cross-repeat of a visual mode mapping in normal mode, a new\r\ndifferent [count] only affects the range it applies to!\r\n\r\nFor cross-repeat, use the repeatableMapping#makeCrossRepeatable() function,\r\nfor single normal mode and visual mode mappings, and\r\nrepeatableMapping#makeMultipleCrossRepeatable() for multiple normal mode and\r\na single visual mode mapping.\r\nFor existing <Plug>-mappings, there's the\r\nrepeatableMapping#makeMultiplePlugMappingCrossRepeatable() function.\r\n\r\nIf the repeat needs to go to a different <Plug>-mapping (for example when you\r\nhave a mapping that queries the user, and you want to avoid the query on\r\nrepeat through a non-interactive mapping variant that recalls the saved\r\noriginal query's value), use the\r\nrepeatableMapping#makePlugMappingWithDifferentRepeatCrossRepeatable()\r\nfunction. With this variant of repeatableMapping#makeCrossRepeatable(), you\r\ncan specify separate repeat <Plug>-mappings:\r\n    silent! call repeatableMapping#makePlugMappingWithDifferentRepeatCrossRepeatable(\r\n    \\   'nnoremap', '<Plug>(FooRange)',           '<Plug>(FooRangeRepeat)',\r\n    \\   'xnoremap', '<Plug>(FooSelection)',       '<Plug>(FooSelectionRepeat)'\r\n    \\)\r\n    silent! call repeatableMapping#makePlugMappingWithDifferentRepeatCrossRepeatable(\r\n    \\   'nnoremap', '<Plug>(FooRangeRepeat)',     '<Plug>(FooRangeRepeat)',\r\n    \\   'xnoremap', '<Plug>(FooSelectionRepeat)', '<Plug>(FooSelectionRepeat)'\r\n    \\)\r\n\r\nUSAGE\r\nRETROFIT MAPPING REPETITION\r\nFirst define your mapping in the usual way:\r\n    nnoremap <silent> <Leader>v :version<CR>\r\nThen make the mapping repeatable; this will redefine the original mapping\r\nand insert the call to repeat#set() at the end.\r\n    silent! call repeatableMapping#makeRepeatable('nnoremap', '<Leader>v', 'ShowVersion')\r\n\r\nThe processing requires the following information:\r\n- The original mapping command (for the map-mode, whether :noremap or not,\r\n  any optional map-arguments like \"<buffer>\"; \"<silent>\" is added\r\n  automatically to avoid showing the repeat invocation).\r\n- The mapping's {lhs} (i.e. keys that invoke the mapping).\r\n- A unique name for the intermediate <Plug>-mapping that needs to be created\r\n  so that repeat.vim can invoke it.\r\n- Optional: The default count that will be prefixed to the mapping if no\r\n  explicit numeric argument was given; i.e. the second optional argument of\r\n  repeat#set(). If your mapping doesn't accept a numeric argument and you\r\n  never want to receive one, pass a value of -1.\r\nNote that the wrapped Ex command in the mapping must support command\r\nsequencing with | (i.e. custom commands must be defined with :command-bar),\r\nas the repeat insertion will be appended with <Bar>. If that is not the case,\r\nwrap the command in :execute.\r\n\r\nIf you already have a <Plug> mapping:\r\n    vnoremap <silent> <Plug>ShowVersion :<C-U>version<CR>\r\n    vmap <Leader>v <Plug>ShowVersion\r\nYou can redefine the <Plug> mapping directly, and just have the call to\r\nrepeat#set() appended:\r\n    silent! call repeatableMapping#makePlugMappingRepeatable('vnoremap', '<Plug>ShowVersion')\r\nThis is especially useful to retrofit existing visual mode mappings with the\r\nability to be repeatable, in conjunction with the visual mode repetition\r\ndescribed above.\r\n\r\nVISUAL MODE REPETITION\r\nFirst define your normal and visual mode mappings:\r\n    nnoremap <buffer> <LocalLeader>qq :s\/^\/> \/<CR>\r\n    vnoremap <buffer> <LocalLeader>q  :s\/^\/> \/<CR>\r\n\r\nYou could now make both mappings repeatable via two separate calls to\r\nrepeatableMapping#makeRepeatable(), as described in the above section, but\r\nwith that, the mappings won't repeat each other. Therefore, it is recommended\r\nto use repeatableMapping#makeCrossRepeatable(), so that the normal mode\r\nmapping can be repeated over a visual selection and vice versa:\r\n    silent! call repeatableMapping#makeCrossRepeatable(\r\n    \\   'nnoremap <buffer>', '<LocalLeader>qq', 'QuoteLine',\r\n    \\   'vnoremap <buffer>', '<LocalLeader>q',  'QuoteSelection'\r\n    \\)\r\n\r\nAgain, if you already have <Plug> mappings (and need them for a configurable\r\nplugin), you can use the alternative function:\r\n    silent! call repeatableMapping#makePlugMappingCrossRepeatable(\r\n    \\   'nnoremap <buffer>', '<Plug>QuoteLine',\r\n    \\   'vnoremap <buffer>', '<Plug>QuoteSelection'\r\n    \\)\r\nNote that you need to do this _after_ any\r\n    if ! hasmapto('<Plug>QuoteLine', 'n') ...\r\ndefault mapping tests; because the <Plug>-mapping is contained in the\r\nretrofitted mapping, the test would otherwise always be false, and the default\r\nmappings would be missing!","4":"DESCRIPTION\r\nThis plugin simplifies the application of the repeat.vim and visualrepeat.vim\r\nrepeat functionality to existing mappings. As with repeat.vim, all\r\nembellishments are optional; if the corresponding plugin isn't available, the\r\ncall will be ignored and the original mappings persist unchanged (though\r\nwithout any repeat functionality).\r\n\r\nRETROFIT MAPPING REPETITION\r\nSome plugins provide out-of-the-box support for repeat.vim, many do not.\r\nSome mappings have been developed in an ad-hoc fashion, e.g. as custom\r\nfiletype-specific workflow shortcuts, and therefore do not have the\r\ncanonical remapping layer of <Plug> mappings (which repeat.vim requires).\r\n\r\nThis plugin allows to retrofit repeatability to mappings from plugins that\r\ndo not directly use repeat.vim. It also offers a succinct way for custom\r\nmappings to acquire repeatability, and spares them the definition of\r\n<Plug>-mappings and adding the repeat#set() boilerplate code themselves.\r\n\r\nVISUAL MODE REPETITION\r\nrepeat.vim only supports normal mode repetition, as this is the only\r\nrepetition that is built into Vim. However, one can define repetition in\r\nvisual mode:\r\n    xnoremap . :normal .<CR>\r\nor with pass-through of [count]:\r\n    xnoremap . :execute 'normal' (v:count ? v:count : '') . '.'<CR>\r\n(Or better a more fancy version that only applies the repeat command over\r\nentire lines in linewise visual mode, keeps the current cursor position in\r\ncharacterwise visual mode, and does nothing (sensible) in blockwise visual\r\nmode. The visualrepeat.vim plugin provides this.)\r\n\r\nThe <Plug>(ReenterVisualMode) mapping allows to apply repeat.vim repetition to\r\nvisual mode commands; just prepend it in the call to repeat#set():\r\n    vnoremap <silent> <Plug>MyMapping ...:silent! call repeat#set(\"\\<Plug>(ReenterVisualMode)\\<Plug>MyMapping\")<CR>\r\n\r\nIf a previously used visual mode mapping is repeated from an active visual\r\nselection, that selection is the affected area for the repetition. The\r\nrecorded repeat count is passed to the mapping.\r\n\r\nIf repetition is invoked in normal mode, the repetition works on a new\r\nselection, depending on the last visual mode:\r\n- For linewise selections, the repetition selects the current line.\r\n- For characterwise selections, a new selection starting at the cursor\r\n  position, with the same size as the last visual selection is used. 1v\r\nA [count] is passed to the mapping and overrides the recorded one.\r\n\r\nIf a non-visual mode mapping is repeated from an active visual selection, it\r\nwon't (can't) apply to the visual selection, but to whatever that mapping\r\ntypically applies. So, you can only repeat previous visual mode mappings on\r\na visual selection! The only way around this is to cross-link both mapping\r\ntypes, and to use a more intelligent version of the repeat definition in\r\nvisual mode. This is described next:\r\n\r\nCROSS-REPEAT\r\nThrough the visualrepeat.vim plugin, it is possible to make normal mode and\r\nvisual mode mappings repeat each other, with the normal mode mapping repeated\r\nover the visual selection, and the visual mode mapping repeated over a new\r\nselection, such as:\r\n- For previous linewise selections, the repetition applies to the same amount\r\n  of lines, unless a different [count] is given. In that case, it selects\r\n  [count] lines starting at the cursor position.\r\n- Else, a new selection starting at the cursor position, with the same size as\r\n  the last visual selection (times [count], if given and different) is used.\r\n  1v\r\nThe mapping itself is always repeated with the recorded [count], not a new\r\ngiven one. For cross-repeat of a visual mode mapping in normal mode, a new\r\ndifferent [count] only affects the range it applies to!\r\n\r\nFor cross-repeat, use the repeatableMapping#makeCrossRepeatable() function,\r\nfor single normal mode and visual mode mappings, and\r\nrepeatableMapping#makeMultipleCrossRepeatable() for multiple normal mode and\r\na single visual mode mapping.\r\nFor existing <Plug>-mappings, there's the\r\nrepeatableMapping#makeMultiplePlugMappingCrossRepeatable() function.\r\n\r\nIf the repeat needs to go to a different <Plug>-mapping (for example when you\r\nhave a mapping that queries the user, and you want to avoid the query on\r\nrepeat through a non-interactive mapping variant that recalls the saved\r\noriginal query's value), use the\r\nrepeatableMapping#makePlugMappingWithDifferentRepeatCrossRepeatable()\r\nfunction. With this variant of repeatableMapping#makeCrossRepeatable(), you\r\ncan specify separate repeat <Plug>-mappings:\r\n    silent! call repeatableMapping#makePlugMappingWithDifferentRepeatCrossRepeatable(\r\n    \\   'nnoremap', '<Plug>(FooRange)',           '<Plug>(FooRangeRepeat)',\r\n    \\   'xnoremap', '<Plug>(FooSelection)',       '<Plug>(FooSelectionRepeat)'\r\n    \\)\r\n    silent! call repeatableMapping#makePlugMappingWithDifferentRepeatCrossRepeatable(\r\n    \\   'nnoremap', '<Plug>(FooRangeRepeat)',     '<Plug>(FooRangeRepeat)',\r\n    \\   'xnoremap', '<Plug>(FooSelectionRepeat)', '<Plug>(FooSelectionRepeat)'\r\n    \\)\r\n\r\nUSAGE\r\nRETROFIT MAPPING REPETITION\r\nFirst define your mapping in the usual way:\r\n    nnoremap <silent> <Leader>v :version<CR>\r\nThen make the mapping repeatable; this will redefine the original mapping\r\nand insert the call to repeat#set() at the end.\r\n    silent! call repeatableMapping#makeRepeatable('nnoremap', '<Leader>v', 'ShowVersion')\r\n\r\nThe processing requires the following information:\r\n- The original mapping command (for the map-mode, whether :noremap or not,\r\n  any optional map-arguments like \"<buffer>\"; \"<silent>\" is added\r\n  automatically to avoid showing the repeat invocation).\r\n- The mapping's {lhs} (i.e. keys that invoke the mapping).\r\n- A unique name for the intermediate <Plug>-mapping that needs to be created\r\n  so that repeat.vim can invoke it.\r\n- Optional: The default count that will be prefixed to the mapping if no\r\n  explicit numeric argument was given; i.e. the second optional argument of\r\n  repeat#set(). If your mapping doesn't accept a numeric argument and you\r\n  never want to receive one, pass a value of -1.\r\nNote that the wrapped Ex command in the mapping must support command\r\nsequencing with | (i.e. custom commands must be defined with :command-bar),\r\nas the repeat insertion will be appended with <Bar>. If that is not the case,\r\nwrap the command in :execute.\r\n\r\nIf you already have a <Plug> mapping:\r\n    vnoremap <silent> <Plug>ShowVersion :<C-U>version<CR>\r\n    vmap <Leader>v <Plug>ShowVersion\r\nYou can redefine the <Plug> mapping directly, and just have the call to\r\nrepeat#set() appended:\r\n    silent! call repeatableMapping#makePlugMappingRepeatable('vnoremap', '<Plug>ShowVersion')\r\nThis is especially useful to retrofit existing visual mode mappings with the\r\nability to be repeatable, in conjunction with the visual mode repetition\r\ndescribed above.\r\n\r\nVISUAL MODE REPETITION\r\nFirst define your normal and visual mode mappings:\r\n    nnoremap <buffer> <LocalLeader>qq :s\/^\/> \/<CR>\r\n    vnoremap <buffer> <LocalLeader>q  :s\/^\/> \/<CR>\r\n\r\nYou could now make both mappings repeatable via two separate calls to\r\nrepeatableMapping#makeRepeatable(), as described in the above section, but\r\nwith that, the mappings won't repeat each other. Therefore, it is recommended\r\nto use repeatableMapping#makeCrossRepeatable(), so that the normal mode\r\nmapping can be repeated over a visual selection and vice versa:\r\n    silent! call repeatableMapping#makeCrossRepeatable(\r\n    \\   'nnoremap <buffer>', '<LocalLeader>qq', 'QuoteLine',\r\n    \\   'vnoremap <buffer>', '<LocalLeader>q',  'QuoteSelection'\r\n    \\)\r\n\r\nAgain, if you already have <Plug> mappings (and need them for a configurable\r\nplugin), you can use the alternative function:\r\n    silent! call repeatableMapping#makePlugMappingCrossRepeatable(\r\n    \\   'nnoremap <buffer>', '<Plug>QuoteLine',\r\n    \\   'vnoremap <buffer>', '<Plug>QuoteSelection'\r\n    \\)\r\nNote that you need to do this _after_ any\r\n    if ! hasmapto('<Plug>QuoteLine', 'n') ...\r\ndefault mapping tests; because the <Plug>-mapping is contained in the\r\nretrofitted mapping, the test would otherwise always be false, and the default\r\nmappings would be missing!","install_details":"INSTALLATION\r\nThe code is hosted in a Git repo at\r\n    https:\/\/github.com\/inkarkat\/vim-repeatableMapping\r\nYou can use your favorite plugin manager, or \"git clone\" into a directory used\r\nfor Vim packages. Releases are on the \"stable\" branch, the latest unstable\r\ndevelopment snapshot on \"master\".\r\n\r\nThis script is also packaged as a vimball. If you have the \"gunzip\"\r\ndecompressor in your PATH, simply edit the *.vmb.gz package in Vim; otherwise,\r\ndecompress the archive first, e.g. using WinZip. Inside Vim, install by\r\nsourcing the vimball or via the :UseVimball command.\r\n    vim repeatableMapping*.vmb.gz\r\n    :so %\r\nTo uninstall, use the :RmVimball command.\r\n\r\nDEPENDENCIES\r\n- Requires Vim 7.0 or higher.\r\n- repeat.vim (vimscript #2136) plugin (optional, but without it this plugin\r\n  doesn't provide any functionality).\r\n- visualrepeat.vim (vimscript #3848 plugin) (version 2.00 or higher; optional,\r\n  but recommended for cross-repeat functionality).","5":"INSTALLATION\r\nThe code is hosted in a Git repo at\r\n    https:\/\/github.com\/inkarkat\/vim-repeatableMapping\r\nYou can use your favorite plugin manager, or \"git clone\" into a directory used\r\nfor Vim packages. Releases are on the \"stable\" branch, the latest unstable\r\ndevelopment snapshot on \"master\".\r\n\r\nThis script is also packaged as a vimball. If you have the \"gunzip\"\r\ndecompressor in your PATH, simply edit the *.vmb.gz package in Vim; otherwise,\r\ndecompress the archive first, e.g. using WinZip. Inside Vim, install by\r\nsourcing the vimball or via the :UseVimball command.\r\n    vim repeatableMapping*.vmb.gz\r\n    :so %\r\nTo uninstall, use the :RmVimball command.\r\n\r\nDEPENDENCIES\r\n- Requires Vim 7.0 or higher.\r\n- repeat.vim (vimscript #2136) plugin (optional, but without it this plugin\r\n  doesn't provide any functionality).\r\n- visualrepeat.vim (vimscript #3848 plugin) (version 2.00 or higher; optional,\r\n  but recommended for cross-repeat functionality).","first_name":"Ingo","6":"Ingo","last_name":"Karkat","7":"Karkat","releases":[{"0":"4777","vim_version":"7.0","1":"7.0","script_version":"2.20","2":"2.20","version_comment":"- ENH: All functions now support a second optional a:isRepeatRegister argument (to skip specifying a a:defaultCount, pass an empty String as the first optional argument) that if set invokes repeat#setreg() before the original {rhs} and also tweaks the repeat mappings that recreate a visual selection (which clobber count and also register) to save and restore the repeated register for the repeat as well.","3":"- ENH: All functions now support a second optional a:isRepeatRegister argument (to skip specifying a a:defaultCount, pass an empty String as the first optional argument) that if set invokes repeat#setreg() before the original {rhs} and also tweaks the repeat mappings that recreate a visual selection (which clobber count and also register) to save and restore the repeated register for the repeat as well.","package":"repeatableMapping-2.20.vmb.gz","4":"repeatableMapping-2.20.vmb.gz","src_id":"27098","5":"27098","creation_date":"1585969630","6":"1585969630"},{"0":"4777","vim_version":"7.0","1":"7.0","script_version":"2.11","2":"2.11","version_comment":"- Documentation: Mention that a <silent> map-argument does not need to be passed; I was confused about this myself.\r\n- FIX: The ingo-library may not be loaded yet (as repeatable mappings are usually defined early in plugin scripts); try loading it before testing for its existence.\r\n- Escaping (duplicated from ingo#compat#maparg()) didn't consider <; in fact, it needs to escape stand-alone < and escaped \\<, but not proper key notations like <C-CR>.","3":"- Documentation: Mention that a <silent> map-argument does not need to be passed; I was confused about this myself.\r\n- FIX: The ingo-library may not be loaded yet (as repeatable mappings are usually defined early in plugin scripts); try loading it before testing for its existence.\r\n- Escaping (duplicated from ingo#compat#maparg()) didn't consider <; in fact, it needs to escape stand-alone < and escaped \\<, but not proper key notations like <C-CR>.","package":"repeatableMapping-2.11.vmb.gz","4":"repeatableMapping-2.11.vmb.gz","src_id":"26658","5":"26658","creation_date":"1564086820","6":"1564086820"},{"0":"4777","vim_version":"7.0","1":"7.0","script_version":"2.10","2":"2.10","version_comment":"- ENH: Allow to pass Funcref as a:defaultCount; the value will then be determined via a dynamic lookup. This is necessary for mappings that clobber v:count (e.g. due to use of :normal). They can now save the original count and pass it on to the repeat part via the Funcref, which is more elegant than a global variable.","3":"- ENH: Allow to pass Funcref as a:defaultCount; the value will then be determined via a dynamic lookup. This is necessary for mappings that clobber v:count (e.g. due to use of :normal). They can now save the original count and pass it on to the repeat part via the Funcref, which is more elegant than a global variable.","package":"repeatableMapping-2.10.vmb.gz","4":"repeatableMapping-2.10.vmb.gz","src_id":"22990","5":"22990","creation_date":"1425845238","6":"1425845238"},{"0":"4777","vim_version":"7.0","1":"7.0","script_version":"2.01","2":"2.01","version_comment":"- BUG: Typo in repeatableMapping#makePlugMappingCrossRepeatable() causes \"E116: Invalid arguments for function call\", which unfortunately usually is suppressed by the :silent! invocation.","3":"- BUG: Typo in repeatableMapping#makePlugMappingCrossRepeatable() causes \"E116: Invalid arguments for function call\", which unfortunately usually is suppressed by the :silent! invocation.","package":"repeatableMapping-2.01.vmb.gz","4":"repeatableMapping-2.01.vmb.gz","src_id":"22630","5":"22630","creation_date":"1416469079","6":"1416469079"},{"0":"4777","vim_version":"7.0","1":"7.0","script_version":"2.00","2":"2.00","version_comment":"Initial upload","3":"Initial upload","package":"repeatableMapping-2.00.vmb.gz","4":"repeatableMapping-2.00.vmb.gz","src_id":"21094","5":"21094","creation_date":"1385133981","6":"1385133981"}]},"4776":{"script_id":"4776","0":"4776","script_name":"Projx","1":"Projx","script_type":"utility","2":"utility","summary":"Light weight project explorer","3":"Light weight project explorer","description":" projx is a simple to install, light weight project explorer plugin. It opens a project navigation panel on  the right\/left side of the vim screen. When enter is pressed on a file name the file is opened in a new tab or jumps to an existing tab that already has the file\r\n                                                                                       \r\n It supports project wide grep that will show all the instances in the quickfix window. \r\n                                                                                       \r\n When enabled, it automatically creates and updates tag file for the list of files in the project.\r\n\r\n Works well with cppnav plugin\r\n http:\/\/www.vim.org\/scripts\/script.php?script_id=4763\r\n\r\nSCREEN SHOTS:\r\n  http:\/\/vim.wikia.com\/wiki\/Projx_Vim_Plugin\r\n                                                                                       \r\nUSAGE:\r\n To use this plugin, simply place a .projx file in the root of working directory with all the file names (with relative path) in the project (one per line)\r\n                                                                                       \r\n :Projx [<project file>] to open or close the project navigation panel. Optionally specify the project file name to this command.\r\n                                                                                       \r\n :Pgrep <regx> to search for a string across all the files in the project. Results are listed in the quickfix window. Preview\/jump to the location using p or <enter> keys.\r\n                                                                                       \r\n :Ptags to update the tag file. This plugin automatically updates the tag file on init (if any of the file is newer than the tag file)\r\n                                                                                       \r\n :Pfilter <wildcard expression> to see only the specific files on the navigation panel\r\n                                                                                       \r\nOPTIONS:\r\n Set the following variables in .vimrc\/_vimrc file to control some of the options. \r\n                                                                                       \r\n let g:projx_file_def = <default project file name>           \" .projx is used by default\r\n let g:projx_right_win = <1\/0>                                            \" use right\/left navigation panel\r\n let g:projx_win_size = xxx                                                 \" set the navigation panel width to xxx\r\n let g:projx_ctag_path = <ctag executable name\/path> \" omit this to disable tab file creation","4":" projx is a simple to install, light weight project explorer plugin. It opens a project navigation panel on  the right\/left side of the vim screen. When enter is pressed on a file name the file is opened in a new tab or jumps to an existing tab that already has the file\r\n                                                                                       \r\n It supports project wide grep that will show all the instances in the quickfix window. \r\n                                                                                       \r\n When enabled, it automatically creates and updates tag file for the list of files in the project.\r\n\r\n Works well with cppnav plugin\r\n http:\/\/www.vim.org\/scripts\/script.php?script_id=4763\r\n\r\nSCREEN SHOTS:\r\n  http:\/\/vim.wikia.com\/wiki\/Projx_Vim_Plugin\r\n                                                                                       \r\nUSAGE:\r\n To use this plugin, simply place a .projx file in the root of working directory with all the file names (with relative path) in the project (one per line)\r\n                                                                                       \r\n :Projx [<project file>] to open or close the project navigation panel. Optionally specify the project file name to this command.\r\n                                                                                       \r\n :Pgrep <regx> to search for a string across all the files in the project. Results are listed in the quickfix window. Preview\/jump to the location using p or <enter> keys.\r\n                                                                                       \r\n :Ptags to update the tag file. This plugin automatically updates the tag file on init (if any of the file is newer than the tag file)\r\n                                                                                       \r\n :Pfilter <wildcard expression> to see only the specific files on the navigation panel\r\n                                                                                       \r\nOPTIONS:\r\n Set the following variables in .vimrc\/_vimrc file to control some of the options. \r\n                                                                                       \r\n let g:projx_file_def = <default project file name>           \" .projx is used by default\r\n let g:projx_right_win = <1\/0>                                            \" use right\/left navigation panel\r\n let g:projx_win_size = xxx                                                 \" set the navigation panel width to xxx\r\n let g:projx_ctag_path = <ctag executable name\/path> \" omit this to disable tab file creation","install_details":"Linux\/Unix\/Cygwin : Copy the projx.vim to ~\/.vim\/plugin\/\r\nWindows : Copy the projx.vim to %HOME%\\vimfiles\\plugin\\\r\n\r\nSome useful shortcuts to add to .vimrc\/_vimrc\r\n  nmap <silent> <F3> :Pgrep expand(\"<cword>\")<CR>  \"search word under cursor\r\n  nmap <silent> <F7> :Projx<CR>  \" Open\/Close project panel\r\n  nmap <silent> <Tab>     <C-W><C-W> \" Tab to jump between windows","5":"Linux\/Unix\/Cygwin : Copy the projx.vim to ~\/.vim\/plugin\/\r\nWindows : Copy the projx.vim to %HOME%\\vimfiles\\plugin\\\r\n\r\nSome useful shortcuts to add to .vimrc\/_vimrc\r\n  nmap <silent> <F3> :Pgrep expand(\"<cword>\")<CR>  \"search word under cursor\r\n  nmap <silent> <F7> :Projx<CR>  \" Open\/Close project panel\r\n  nmap <silent> <Tab>     <C-W><C-W> \" Tab to jump between windows","first_name":"Sureshkumar","6":"Sureshkumar","last_name":"Manimuthu","7":"Manimuthu","releases":[{"0":"4776","vim_version":"7.0","1":"7.0","script_version":"1.1","2":"1.1","version_comment":"Auto resize the navigation panel when vim is resized.","3":"Auto resize the navigation panel when vim is resized.","package":"projx.vim","4":"projx.vim","src_id":"21100","5":"21100","creation_date":"1385352938","6":"1385352938"},{"0":"4776","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial Upload","3":"Initial Upload","package":"projx.vim","4":"projx.vim","src_id":"21086","5":"21086","creation_date":"1385040423","6":"1385040423"}]},"4775":{"script_id":"4775","0":"4775","script_name":"tex-breqn.vim","1":"tex-breqn.vim","script_type":"syntax","2":"syntax","summary":"LaTeX breqn package syntax highlighting support","3":"LaTeX breqn package syntax highlighting support","description":"LaTeX breqn package syntax highlighting support.\r\n\r\nFeature: use math rules to highlight dmath environment.\r\n\r\ngit repo: https:\/\/github.com\/xuhdev\/tex-breqn.vim","4":"LaTeX breqn package syntax highlighting support.\r\n\r\nFeature: use math rules to highlight dmath environment.\r\n\r\ngit repo: https:\/\/github.com\/xuhdev\/tex-breqn.vim","install_details":"Unzip this archive into ~\/.vim","5":"Unzip this archive into ~\/.vim","first_name":"Hong","6":"Hong","last_name":"Xu","7":"Xu","releases":[{"0":"4775","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"tex-breqn-0.1.zip","4":"tex-breqn-0.1.zip","src_id":"21078","5":"21078","creation_date":"1384989853","6":"1384989853"}]},"4774":{"script_id":"4774","0":"4774","script_name":"p4checkout","1":"p4checkout","script_type":"utility","2":"utility","summary":"Automatically check out RO files from Perforce on edit","3":"Automatically check out RO files from Perforce on edit","description":"p4checkout is a simple plugin which uses perforce to check out all read-only files on edit with support for multiple simultaneous client workspaces. It uses the p4 command-line utilities, which must be installed and available in the PATH.","4":"p4checkout is a simple plugin which uses perforce to check out all read-only files on edit with support for multiple simultaneous client workspaces. It uses the p4 command-line utilities, which must be installed and available in the PATH.","install_details":"See installation instructions at https:\/\/github.com\/aslater\/p4checkout","5":"See installation instructions at https:\/\/github.com\/aslater\/p4checkout","first_name":"Adam","6":"Adam","last_name":"Slater","7":"Slater","releases":[{"0":"4774","vim_version":"7.0","1":"7.0","script_version":"1.01","2":"1.01","version_comment":"Removed some debug prints","3":"Removed some debug prints","package":"p4checkout.zip","4":"p4checkout.zip","src_id":"21077","5":"21077","creation_date":"1384975872","6":"1384975872"},{"0":"4774","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"p4checkout.zip","4":"p4checkout.zip","src_id":"21076","5":"21076","creation_date":"1384964623","6":"1384964623"}]},"4773":{"script_id":"4773","0":"4773","script_name":"grishin-color-scheme","1":"grishin-color-scheme","script_type":"color scheme","2":"color scheme","summary":"A koehler-similar scheme","3":"A koehler-similar scheme","description":"I like original koehler scheme. However, it offers little help in catching magic numbers in the code (see Steve McConnell's advice regarding \"no magic numbers\" in his \"Code Complete 2\"); this modified scheme will help in catching all of them. String literals and bools are marked in purple, number constants in red.\r\n\r\nYou can preview it here:\r\nwww.pyramidheadgroup.ca\/~ygrishin\/public\/grishin-vim-color-scheme.png","4":"I like original koehler scheme. However, it offers little help in catching magic numbers in the code (see Steve McConnell's advice regarding \"no magic numbers\" in his \"Code Complete 2\"); this modified scheme will help in catching all of them. String literals and bools are marked in purple, number constants in red.\r\n\r\nYou can preview it here:\r\nwww.pyramidheadgroup.ca\/~ygrishin\/public\/grishin-vim-color-scheme.png","install_details":"Place the grishin.vim into your Vim colors directory (next to koehler.vim)\r\nFor example, on Debian it is\r\n\/usr\/share\/vim\/vim73\/colors\/grishin.vim","5":"Place the grishin.vim into your Vim colors directory (next to koehler.vim)\r\nFor example, on Debian it is\r\n\/usr\/share\/vim\/vim73\/colors\/grishin.vim","first_name":"Yuriy","6":"Yuriy","last_name":"Grishin","7":"Grishin","releases":[{"0":"4773","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"grishin.vim","4":"grishin.vim","src_id":"21058","5":"21058","creation_date":"1384827958","6":"1384827958"}]},"4772":{"script_id":"4772","0":"4772","script_name":"marslo.vim","1":"marslo.vim","script_type":"color scheme","2":"color scheme","summary":"A dark-background color scheme made by Marslo","3":"A dark-background color scheme made by Marslo","description":"The color made by myself. Including 16 color and 256 color.\r\n这是我自己做的vim配色。包括了16色和256色两种\r\n\r\nThe screenshot: https:\/\/github.com\/Marslo\/marslo.vim#screenshot\r\n无图无真相： https:\/\/github.com\/Marslo\/marslo.vim#screenshot\r\n\r\nThe github repo for my color scheme: https:\/\/github.com\/Marslo\/marslo.vim\r\n详情查看此配色在github上的repo： https:\/\/github.com\/Marslo\/marslo.vim\r\n\r\n-----\r\nUsage:\r\n使用方法:\r\n- Copy the following settings to .vimrc in linux (~\/.vimrc) or _vimrc in windows (C:\\Program Files (x86)\\Vim\\_vimrc)\r\n  将如下配置拷贝粘贴至 Linux下的.vimrc(~\/.vimrc) 或者 windows下的_vimrc(C:\\Program Files (x86)\\Vim\\_vimrc)\r\n\r\n    if has('gui_running') || 'xterm-256color' == $TERM\r\n        colorscheme marslo\r\n        let psc_style='cool'\r\n    else\r\n        colorscheme marslo16\r\n    endif\r\n\r\n\r\n- For Linux, just add the following setting into .bashrc(~\/.bashrc). Make sure 256 colors can be supported in Linux Terminal.\r\n  如果是Linux用户，还需要将如下配置粘贴复制至 .bashrc(~\/.bashrc) 以保证Linux下的终端可以支持256色(不写也行，只是不好看)\r\n\r\n    if [ -e \/usr\/share\/terminfo\/x\/xterm-256color ];\r\n    then\r\n        export TERM='xterm-256color'\r\n    # Ubuntu\r\n    elif [ -e \/lib\/terminfo\/x\/xterm-256color ];\r\n    then\r\n        export TERM='xterm-256color'\r\n    else\r\n        export TERM='xterm-color'\r\n    fi\r\n\r\n\r\nAnything wrong, just leave message at: https:\/\/github.com\/Marslo\/marslo.vim\/issues\r\n任何问题，请到此配色的github的repo处留言: https:\/\/github.com\/Marslo\/marslo.vim\/issues","4":"The color made by myself. Including 16 color and 256 color.\r\n这是我自己做的vim配色。包括了16色和256色两种\r\n\r\nThe screenshot: https:\/\/github.com\/Marslo\/marslo.vim#screenshot\r\n无图无真相： https:\/\/github.com\/Marslo\/marslo.vim#screenshot\r\n\r\nThe github repo for my color scheme: https:\/\/github.com\/Marslo\/marslo.vim\r\n详情查看此配色在github上的repo： https:\/\/github.com\/Marslo\/marslo.vim\r\n\r\n-----\r\nUsage:\r\n使用方法:\r\n- Copy the following settings to .vimrc in linux (~\/.vimrc) or _vimrc in windows (C:\\Program Files (x86)\\Vim\\_vimrc)\r\n  将如下配置拷贝粘贴至 Linux下的.vimrc(~\/.vimrc) 或者 windows下的_vimrc(C:\\Program Files (x86)\\Vim\\_vimrc)\r\n\r\n    if has('gui_running') || 'xterm-256color' == $TERM\r\n        colorscheme marslo\r\n        let psc_style='cool'\r\n    else\r\n        colorscheme marslo16\r\n    endif\r\n\r\n\r\n- For Linux, just add the following setting into .bashrc(~\/.bashrc). Make sure 256 colors can be supported in Linux Terminal.\r\n  如果是Linux用户，还需要将如下配置粘贴复制至 .bashrc(~\/.bashrc) 以保证Linux下的终端可以支持256色(不写也行，只是不好看)\r\n\r\n    if [ -e \/usr\/share\/terminfo\/x\/xterm-256color ];\r\n    then\r\n        export TERM='xterm-256color'\r\n    # Ubuntu\r\n    elif [ -e \/lib\/terminfo\/x\/xterm-256color ];\r\n    then\r\n        export TERM='xterm-256color'\r\n    else\r\n        export TERM='xterm-color'\r\n    fi\r\n\r\n\r\nAnything wrong, just leave message at: https:\/\/github.com\/Marslo\/marslo.vim\/issues\r\n任何问题，请到此配色的github的repo处留言: https:\/\/github.com\/Marslo\/marslo.vim\/issues","install_details":"1. Install by manually:\r\n   手动安装:\r\n- For Windows: Download and copy two files (marslo16.vim && marslo.vim) to \"colors\" folder (C:\\Program Files (x86)\\Vim\\vimfiles\\colors, for example)\r\n  Windows用户: 下载且拷贝两个文件(marslo16.vim && marslo.vim) 到 \"colors\" 目录中 (C:\\Program Files (x86)\\Vim\\vimfiles\\colors 【64位操作系统】)\r\n\r\n- For Linux: Download and copy two files (marslo.vim && marslo16.vim) to ~\/.vim\/colors\r\n  Linux用户: 下载且拷贝两个文件 (marslo.vim && marslo16.vim) 到 ~\/.vim\/colors\r\n\r\n2. Install by Vundle:\r\n   通过Vundle安装:\r\n\r\n- Add the following setting into .vimrc(linux [~\/.vimrc]) or _vimrc(windows [C:\\Program Files (x86)\\Vim\\_vimrc])\r\n  将如下配置拷贝至 Linux用户的.vimrc([~\/.vimrc) 或 Windows用户的_vimrc(C:\\Program Files (x86)\\Vim\\_vimrc)\r\n\r\n    Bundle 'Marslo\/marslo.vim'\r\n\r\n- Execute the command in vim\/gvim:\r\n  在 vim\/gvim 下执行如下命令即可自动安装成功:\r\n\r\n    :BundleInstall\r\n","5":"1. Install by manually:\r\n   手动安装:\r\n- For Windows: Download and copy two files (marslo16.vim && marslo.vim) to \"colors\" folder (C:\\Program Files (x86)\\Vim\\vimfiles\\colors, for example)\r\n  Windows用户: 下载且拷贝两个文件(marslo16.vim && marslo.vim) 到 \"colors\" 目录中 (C:\\Program Files (x86)\\Vim\\vimfiles\\colors 【64位操作系统】)\r\n\r\n- For Linux: Download and copy two files (marslo.vim && marslo16.vim) to ~\/.vim\/colors\r\n  Linux用户: 下载且拷贝两个文件 (marslo.vim && marslo16.vim) 到 ~\/.vim\/colors\r\n\r\n2. Install by Vundle:\r\n   通过Vundle安装:\r\n\r\n- Add the following setting into .vimrc(linux [~\/.vimrc]) or _vimrc(windows [C:\\Program Files (x86)\\Vim\\_vimrc])\r\n  将如下配置拷贝至 Linux用户的.vimrc([~\/.vimrc) 或 Windows用户的_vimrc(C:\\Program Files (x86)\\Vim\\_vimrc)\r\n\r\n    Bundle 'Marslo\/marslo.vim'\r\n\r\n- Execute the command in vim\/gvim:\r\n  在 vim\/gvim 下执行如下命令即可自动安装成功:\r\n\r\n    :BundleInstall\r\n","first_name":"Marslo","6":"Marslo","last_name":"Jiao","7":"Jiao","releases":[{"0":"4772","vim_version":"7.3","1":"7.3","script_version":"0.1.10","2":"0.1.10","version_comment":"Change marslo256.vim to marslo.vim. Add diff colors for both GUI and Term","3":"Change marslo256.vim to marslo.vim. Add diff colors for both GUI and Term","package":"marslo.vim","4":"marslo.vim","src_id":"23544","5":"23544","creation_date":"1440327479","6":"1440327479"},{"0":"4772","vim_version":"7.3","1":"7.3","script_version":"0.1.10","2":"0.1.10","version_comment":"Add diff colors for both GUI and Term","3":"Add diff colors for both GUI and Term","package":"marslo16.vim","4":"marslo16.vim","src_id":"23543","5":"23543","creation_date":"1440327448","6":"1440327448"},{"0":"4772","vim_version":"7.3","1":"7.3","script_version":"0.1.9","2":"0.1.9","version_comment":"Remove the Redundancy comments, and add couple of colors","3":"Remove the Redundancy comments, and add couple of colors","package":"marslo256.vim","4":"marslo256.vim","src_id":"21693","5":"21693","creation_date":"1396236295","6":"1396236295"},{"0":"4772","vim_version":"7.3","1":"7.3","script_version":"0.1.9","2":"0.1.9","version_comment":"Remove the Redundancy comments, and add couple of colors","3":"Remove the Redundancy comments, and add couple of colors","package":"marslo16.vim","4":"marslo16.vim","src_id":"21692","5":"21692","creation_date":"1396236249","6":"1396236249"},{"0":"4772","vim_version":"7.3","1":"7.3","script_version":"1.8.1","2":"1.8.1","version_comment":"Upload the separate version(256 and 16).","3":"Upload the separate version(256 and 16).","package":"marslo256.vim","4":"marslo256.vim","src_id":"21258","5":"21258","creation_date":"1388385928","6":"1388385928"},{"0":"4772","vim_version":"7.3","1":"7.3","script_version":"1.8.1","2":"1.8.1","version_comment":"Upload the separate version(256 and 16).","3":"Upload the separate version(256 and 16).","package":"marslo16.vim","4":"marslo16.vim","src_id":"21257","5":"21257","creation_date":"1388385901","6":"1388385901"},{"0":"4772","vim_version":"7.3","1":"7.3","script_version":"1.8","2":"1.8","version_comment":"Initial upload","3":"Initial upload","package":"colors.zip","4":"colors.zip","src_id":"21055","5":"21055","creation_date":"1384786901","6":"1384786901"}]},"4771":{"script_id":"4771","0":"4771","script_name":"maven3.1.1 errorformat","1":"maven3.1.1 errorformat","script_type":"utility","2":"utility","summary":"errorformat for maven-compiler-plugin(2.5.1), maven-javadoc-plugin(2.10.1)","3":"errorformat for maven-compiler-plugin(2.5.1), maven-javadoc-plugin(2.10.1)","description":"errorformat for maven-compiler-plugin(2.5.1), maven-javadoc-plugin(2.10.1)","4":"errorformat for maven-compiler-plugin(2.5.1), maven-javadoc-plugin(2.10.1)","install_details":"put it under path $HOME\/.vim\/compiler\/\r\n","5":"put it under path $HOME\/.vim\/compiler\/\r\n","first_name":"quangang","6":"quangang","last_name":"sheng","7":"sheng","releases":[{"0":"4771","vim_version":"7.0","1":"7.0","script_version":"1.3.1","2":"1.3.1","version_comment":"fix cjk message type","3":"fix cjk message type","package":"maven.vim","4":"maven.vim","src_id":"23069","5":"23069","creation_date":"1426841189","6":"1426841189"},{"0":"4771","vim_version":"7.0","1":"7.0","script_version":"1.3","2":"1.3","version_comment":"This is for maven-3.1.1 with default version of maven-compiler-plugin(:2.5.1), maven-javadoc-plugin(2.10.1)","3":"This is for maven-3.1.1 with default version of maven-compiler-plugin(:2.5.1), maven-javadoc-plugin(2.10.1)","package":"maven.vim","4":"maven.vim","src_id":"23004","5":"23004","creation_date":"1425983354","6":"1425983354"},{"0":"4771","vim_version":"7.3","1":"7.3","script_version":"1.2","2":"1.2","version_comment":"bug fix","3":"bug fix","package":"maven.vim","4":"maven.vim","src_id":"21069","5":"21069","creation_date":"1384935606","6":"1384935606"},{"0":"4771","vim_version":"7.3","1":"7.3","script_version":"1.1","2":"1.1","version_comment":"fix some bug","3":"fix some bug","package":"maven.vim","4":"maven.vim","src_id":"21057","5":"21057","creation_date":"1384827865","6":"1384827865"},{"0":"4771","vim_version":"7.3","1":"7.3","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"maven.vim","4":"maven.vim","src_id":"21053","5":"21053","creation_date":"1384746330","6":"1384746330"}]},"4770":{"script_id":"4770","0":"4770","script_name":"noerrmsg.vim","1":"noerrmsg.vim","script_type":"utility","2":"utility","summary":"Hides the ErrorMsg while in insert mode","3":"Hides the ErrorMsg while in insert mode","description":"This plugin addresses the issue on autocompletion plugins, like YouCompleteMe. From its FAQ:\r\n\r\n    I get annoying messages in Vim's status area when I type\r\n\r\n    If you're referring to the User defined completion <bla bla> back at original and similar, then sadly there's no fix for those. Vim will emit them no matter how hard I try to silence them.\r\n\r\n    You'll have to learn to ignore them. It's a shitty \"solution\", I know.\r\n\r\nWith this plugin those messages in the status area are hidden.","4":"This plugin addresses the issue on autocompletion plugins, like YouCompleteMe. From its FAQ:\r\n\r\n    I get annoying messages in Vim's status area when I type\r\n\r\n    If you're referring to the User defined completion <bla bla> back at original and similar, then sadly there's no fix for those. Vim will emit them no matter how hard I try to silence them.\r\n\r\n    You'll have to learn to ignore them. It's a shitty \"solution\", I know.\r\n\r\nWith this plugin those messages in the status area are hidden.","install_details":"Put noerrmsg.vim in your global plugin directory, e.g. ~\/vim\/plugin","5":"Put noerrmsg.vim in your global plugin directory, e.g. ~\/vim\/plugin","first_name":"Hector","6":"Hector","last_name":"Arciga","7":"Arciga","releases":[{"0":"4770","vim_version":"7.0","1":"7.0","script_version":"1","2":"1","version_comment":"Initial upload","3":"Initial upload","package":"noerrmsg.vim","4":"noerrmsg.vim","src_id":"21044","5":"21044","creation_date":"1384493969","6":"1384493969"}]},"4769":{"script_id":"4769","0":"4769","script_name":"airlineish","1":"airlineish","script_type":"color scheme","2":"color scheme","summary":"Custom theme for vim-airline (works perfect with dark background \/ UI)","3":"Custom theme for vim-airline (works perfect with dark background \/ UI)","description":"Theme for vim-airline: https:\/\/github.com\/bling\/vim-airline\r\n\r\nPreview: https:\/\/raw.github.com\/paranoida\/vim-airlineish\/master\/preview.gif\r\n\r\nIt's also available on github: https:\/\/github.com\/paranoida\/vim-airlineish","4":"Theme for vim-airline: https:\/\/github.com\/bling\/vim-airline\r\n\r\nPreview: https:\/\/raw.github.com\/paranoida\/vim-airlineish\/master\/preview.gif\r\n\r\nIt's also available on github: https:\/\/github.com\/paranoida\/vim-airlineish","install_details":"(Make sure that you have vim-airline installed)\r\n\r\n1. Clone repository:\r\n\r\ncd ~\/.vim\/bundle\r\ngit clone https:\/\/github.com\/paranoida\/vim-airlineish.git\r\n\r\n2. Add `let g:airline_theme = 'airlineish'` to your vimrc.\r\n","5":"(Make sure that you have vim-airline installed)\r\n\r\n1. Clone repository:\r\n\r\ncd ~\/.vim\/bundle\r\ngit clone https:\/\/github.com\/paranoida\/vim-airlineish.git\r\n\r\n2. Add `let g:airline_theme = 'airlineish'` to your vimrc.\r\n","first_name":"Rafal","6":"Rafal","last_name":"Bromirski","7":"Bromirski","releases":[{"0":"4769","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"airlineish.vim","4":"airlineish.vim","src_id":"21037","5":"21037","creation_date":"1384337641","6":"1384337641"}]},"4768":{"script_id":"4768","0":"4768","script_name":"natbib.vim","1":"natbib.vim","script_type":"syntax","2":"syntax","summary":"Syntax support for the LaTeX package natbib","3":"Syntax support for the LaTeX package natbib","description":"This extension enables the syntax highlighting for the Latex natbib package\r\n\r\nImage: http:\/\/i.imgur.com\/kCCnOFU.png\r\n\r\nKeyword latex, natbib","4":"This extension enables the syntax highlighting for the Latex natbib package\r\n\r\nImage: http:\/\/i.imgur.com\/kCCnOFU.png\r\n\r\nKeyword latex, natbib","install_details":"Move the file to the global after-directory in your runtimepath, e.g. ~\/.vim\/after\/syntax\/tex\/natbib.vim","5":"Move the file to the global after-directory in your runtimepath, e.g. ~\/.vim\/after\/syntax\/tex\/natbib.vim","first_name":"Hector","6":"Hector","last_name":"Arciga","7":"Arciga","releases":[{"0":"4768","vim_version":"7.0","1":"7.0","script_version":"2","2":"2","version_comment":"Added support for conceal syntax","3":"Added support for conceal syntax","package":"natbib.vim","4":"natbib.vim","src_id":"21049","5":"21049","creation_date":"1384623490","6":"1384623490"},{"0":"4768","vim_version":"7.0","1":"7.0","script_version":"1","2":"1","version_comment":"Initial upload","3":"Initial upload","package":"natbib.vim","4":"natbib.vim","src_id":"21034","5":"21034","creation_date":"1384295636","6":"1384295636"}]},"4767":{"script_id":"4767","0":"4767","script_name":"tabwins.vim","1":"tabwins.vim","script_type":"utility","2":"utility","summary":"1 command for custom window structures that persist","3":"1 command for custom window structures that persist","description":"\"I'm very impressed with it. It gets my highest accolade: the coveted 'Why The\r\nHell Isn't This Functionality Built-In To Vim' award.\"\r\n- Damian Conway\r\n\r\n\r\nThe Developer:\r\n\r\n   o Avoids hit-or-miss, time-consuming, manual, repetitious runs of :split\/:vsplit\r\n\r\n   o Avoids detours thinking about how to produce an intended window structure\r\n\r\n   o Avoids losing current configurations due to mid-session reloads of backed-up Vim sessions that have preferred window structures\r\n\r\n   o Avoids loss of focus from these discontinuities\r\n\r\n\r\n\r\nSEE the reworked and graphically-enhanced tabwins.vim documentation at\r\n  \r\n      https:\/\/github.com\/cesheridan\/tabwins","4":"\"I'm very impressed with it. It gets my highest accolade: the coveted 'Why The\r\nHell Isn't This Functionality Built-In To Vim' award.\"\r\n- Damian Conway\r\n\r\n\r\nThe Developer:\r\n\r\n   o Avoids hit-or-miss, time-consuming, manual, repetitious runs of :split\/:vsplit\r\n\r\n   o Avoids detours thinking about how to produce an intended window structure\r\n\r\n   o Avoids losing current configurations due to mid-session reloads of backed-up Vim sessions that have preferred window structures\r\n\r\n   o Avoids loss of focus from these discontinuities\r\n\r\n\r\n\r\nSEE the reworked and graphically-enhanced tabwins.vim documentation at\r\n  \r\n      https:\/\/github.com\/cesheridan\/tabwins","install_details":"  tabwins.vim tabwins\/ dir is structured for deployment in a \r\n  pathogen-managed bundle directory, e.g. ~\/.vim\/bundle\/\r\n\r\n  If pathogen is not installed, copy the the files in the tabwins \r\n  subdirs to the same subdirs in ~\/.vim.\r\n\r\n  Enable :h tabwins in a pathogen environment with\r\n    :Helptags\r\n  and in a non-pathogen environment with\r\n    :helptags\r\n\r\n\r\n","5":"  tabwins.vim tabwins\/ dir is structured for deployment in a \r\n  pathogen-managed bundle directory, e.g. ~\/.vim\/bundle\/\r\n\r\n  If pathogen is not installed, copy the the files in the tabwins \r\n  subdirs to the same subdirs in ~\/.vim.\r\n\r\n  Enable :h tabwins in a pathogen environment with\r\n    :Helptags\r\n  and in a non-pathogen environment with\r\n    :helptags\r\n\r\n\r\n","first_name":"Charles","6":"Charles","last_name":"Sheridan","7":"Sheridan","releases":[{"0":"4767","vim_version":"7.0","1":"7.0","script_version":"3.1.0","2":"3.1.0","version_comment":"1. For fill_specs that are files, put line #1 at window top.\r\n2. tabwins.txt: correct Fill_tab() key 'dir_cmd_name'     to 'explore_cmd_name'\r\n3. tabwins.txt: correct 'tabwins_dir_reader_name_default' to 'tabwins_explore_cmd_name_default'\r\n4. tabwins.txt: various improvements.","3":"1. For fill_specs that are files, put line #1 at window top.\r\n2. tabwins.txt: correct Fill_tab() key 'dir_cmd_name'     to 'explore_cmd_name'\r\n3. tabwins.txt: correct 'tabwins_dir_reader_name_default' to 'tabwins_explore_cmd_name_default'\r\n4. tabwins.txt: various improvements.","package":"tabwins.v3.1.0.tgz","4":"tabwins.v3.1.0.tgz","src_id":"21176","5":"21176","creation_date":"1386540151","6":"1386540151"},{"0":"4767","vim_version":"7.0","1":"7.0","script_version":"3.0.0","2":"3.0.0","version_comment":"0. No behavioral changes to command logic.\r\n1. Tab option 'line_number_at_window_top' \r\n   renamed => 'line_number_at_netrw_window_top'\r\n\r\n2. Add configurable build of command aliases :T, :V, :H, and :TF \r\n   for :Tabwins* commands.  An alias is NOT BUILT IF an existing\r\n   command has the same name.  See \"\"Configuration\"\/*TabwinsConfiguration*\r\n   in tabwins.txt.\r\n\r\n3. All defaults to Fill_tab() are now user-configurable global vars.\r\n\r\n4. Most functions converted to vimscript ':s' scope -- the \r\n   Explore_*() functions and Fill_tab() are the exceptions.\r\n\r\n5. Demo tabs are now :Tabwins* commands rather than functions.\r\n6. Remove the :Ot* abbreviated commands for the demo tabs.\r\n7. tabwins.txt: Add example builder command, & various improvements.\r\n8. Comments in code cleaned up.\r\n","3":"0. No behavioral changes to command logic.\r\n1. Tab option 'line_number_at_window_top' \r\n   renamed => 'line_number_at_netrw_window_top'\r\n\r\n2. Add configurable build of command aliases :T, :V, :H, and :TF \r\n   for :Tabwins* commands.  An alias is NOT BUILT IF an existing\r\n   command has the same name.  See \"\"Configuration\"\/*TabwinsConfiguration*\r\n   in tabwins.txt.\r\n\r\n3. All defaults to Fill_tab() are now user-configurable global vars.\r\n\r\n4. Most functions converted to vimscript ':s' scope -- the \r\n   Explore_*() functions and Fill_tab() are the exceptions.\r\n\r\n5. Demo tabs are now :Tabwins* commands rather than functions.\r\n6. Remove the :Ot* abbreviated commands for the demo tabs.\r\n7. tabwins.txt: Add example builder command, & various improvements.\r\n8. Comments in code cleaned up.\r\n","package":"tabwins.v3.0.0.tgz","4":"tabwins.v3.0.0.tgz","src_id":"21146","5":"21146","creation_date":"1386032265","6":"1386032265"},{"0":"4767","vim_version":"7.0","1":"7.0","script_version":"2.2.0","2":"2.2.0","version_comment":"- CLI commands support tab_option args\r\n        ALL tabwins.vim capability is now available directly to\r\n        the Vim command line.  A developer should not have to call\r\n        functions in tabwins.vim to create a tabwins command.\r\n\r\n- Configurable reloadability of tabwins.vim.\r\n\r\n- Add :TabwinsFindTabwins and include it in the 'Tabwins' menu.\r\n\r\n- Function Fill_tab() arg 'fill_content' renamed => 'fill_specs'\r\n\r\n- Rework documentation.\r\n","3":"- CLI commands support tab_option args\r\n        ALL tabwins.vim capability is now available directly to\r\n        the Vim command line.  A developer should not have to call\r\n        functions in tabwins.vim to create a tabwins command.\r\n\r\n- Configurable reloadability of tabwins.vim.\r\n\r\n- Add :TabwinsFindTabwins and include it in the 'Tabwins' menu.\r\n\r\n- Function Fill_tab() arg 'fill_content' renamed => 'fill_specs'\r\n\r\n- Rework documentation.\r\n","package":"tabwins.v2.2.0.tgz","4":"tabwins.v2.2.0.tgz","src_id":"21099","5":"21099","creation_date":"1385324475","6":"1385324475"},{"0":"4767","vim_version":"7.0","1":"7.0","script_version":"2.1.0","2":"2.1.0","version_comment":"Enable command-line spec of window content.","3":"Enable command-line spec of window content.","package":"tabwins.v2.1.0.tgz","4":"tabwins.v2.1.0.tgz","src_id":"21052","5":"21052","creation_date":"1384729341","6":"1384729341"},{"0":"4767","vim_version":"7.0","1":"7.0","script_version":"2.0.0","2":"2.0.0","version_comment":"1) As previewed in v1.8.0, the predefined asymmetric :{VH}{I\u00e2\u0080\u00a6} commands are removed, replaced with calls to :TabwinsVertical, :TabwinsHorizontal, and :Tabwins.  All the Create_tab_{vh}*() commands are removed, as the :Tabwins* commands can create the same tabs, with arbitrary dimensions.\r\n\r\n2) Addition of :Tabwins, establishing a plugin default to :TabwinsVertical\r\n\r\n3) Lots of updates to comments, reflecting 1) & 2)","3":"1) As previewed in v1.8.0, the predefined asymmetric :{VH}{I\u00e2\u0080\u00a6} commands are removed, replaced with calls to :TabwinsVertical, :TabwinsHorizontal, and :Tabwins.  All the Create_tab_{vh}*() commands are removed, as the :Tabwins* commands can create the same tabs, with arbitrary dimensions.\r\n\r\n2) Addition of :Tabwins, establishing a plugin default to :TabwinsVertical\r\n\r\n3) Lots of updates to comments, reflecting 1) & 2)","package":"tabwins-master.v2.0.0.tgz","4":"tabwins-master.v2.0.0.tgz","src_id":"21040","5":"21040","creation_date":"1384369474","6":"1384369474"},{"0":"4767","vim_version":"7.0","1":"7.0","script_version":"1.8.0","2":"1.8.0","version_comment":"New commands :TabwinsVertical and :TabwinsHorizontal to create arbitrarily-dimensioned symmetric AND asymmetric tabs.  In v.1.7.0, each asymmetric command required creation of a dedicated function, which is no longer the case.  \r\n\r\nMost of the predefined asymmetric commands in v.1.7.0 will be removed in a later release.","3":"New commands :TabwinsVertical and :TabwinsHorizontal to create arbitrarily-dimensioned symmetric AND asymmetric tabs.  In v.1.7.0, each asymmetric command required creation of a dedicated function, which is no longer the case.  \r\n\r\nMost of the predefined asymmetric commands in v.1.7.0 will be removed in a later release.","package":"tabwins-master.tgz","4":"tabwins-master.tgz","src_id":"21036","5":"21036","creation_date":"1384320294","6":"1384320294"},{"0":"4767","vim_version":"7.0","1":"7.0","script_version":"1.7.0","2":"1.7.0","version_comment":"Initial upload","3":"Initial upload","package":"tabwins-master.zip","4":"tabwins-master.zip","src_id":"21029","5":"21029","creation_date":"1384206502","6":"1384206502"}]},"4766":{"script_id":"4766","0":"4766","script_name":"sovim","1":"sovim","script_type":"ftplugin","2":"ftplugin","summary":"Goes up on directory structures and autosources Vimscript file.","3":"Goes up on directory structures and autosources Vimscript file.","description":"Major application: automatically source per-project Vim configuration from anywhere inside the source tree.\r\n\r\nSource and docs\r\n\r\nhttps:\/\/github.com\/cirosantilli\/sovim","4":"Major application: automatically source per-project Vim configuration from anywhere inside the source tree.\r\n\r\nSource and docs\r\n\r\nhttps:\/\/github.com\/cirosantilli\/sovim","install_details":"If you are using Vundle (and you should) add this to your ~\/.vimrc:\r\n\r\nBundle 'cirosantilli\/sovim'\r\n\r\nand then use the Vim command:\r\n\r\n:BundleInstall","5":"If you are using Vundle (and you should) add this to your ~\/.vimrc:\r\n\r\nBundle 'cirosantilli\/sovim'\r\n\r\nand then use the Vim command:\r\n\r\n:BundleInstall","first_name":"Ciro","6":"Ciro","last_name":"Santilli","7":"Santilli","releases":[{"0":"4766","vim_version":"7.0","1":"7.0","script_version":"0.0.0","2":"0.0.0","version_comment":"Initial upload","3":"Initial upload","package":"sovim.zip","4":"sovim.zip","src_id":"21022","5":"21022","creation_date":"1384067096","6":"1384067096"}]},"4765":{"script_id":"4765","0":"4765","script_name":"axiom.vim","1":"axiom.vim","script_type":"syntax","2":"syntax","summary":"Syntax files for Axiom computer algebra system files","3":"Syntax files for Axiom computer algebra system files","description":"The files contained in the compressed archive provide syntax highlighting for Axiom CAS input files.\r\n\r\nPamphlet files are also supported: you can thus have latex syntax highlight in latex text and Axiom syntax highlight in Axiom code inserted inside a \"chunk\" environment.\r\n\r\nFor another syntax file for axiom, see also\r\nhttp:\/\/axiom-wiki.newsynthesis.org\/AxiomInVim","4":"The files contained in the compressed archive provide syntax highlighting for Axiom CAS input files.\r\n\r\nPamphlet files are also supported: you can thus have latex syntax highlight in latex text and Axiom syntax highlight in Axiom code inserted inside a \"chunk\" environment.\r\n\r\nFor another syntax file for axiom, see also\r\nhttp:\/\/axiom-wiki.newsynthesis.org\/AxiomInVim","install_details":"The files should be copied in your ~\/.vim\/syntax directory; then add to your\r\n~\/.vimrc file the line  \r\n\r\nau BufNewFile,BufRead *.input *.spad  exe \"source ~\/.vim\/syntax\/axiom.vim\"\r\n\r\nFor pamphlet files, add\r\n\r\nau BufRead,BufNewFile *.pamphlet   setfiletype tex\r\nau BufRead,BufNewFile *.pamphlet   exe \"source ~\/.vim\/syntax\/pamphlet.vim\"\r\n\r\nto your ~\/.vimrc file.\r\n\r\nPlease read also the axiom\/README file","5":"The files should be copied in your ~\/.vim\/syntax directory; then add to your\r\n~\/.vimrc file the line  \r\n\r\nau BufNewFile,BufRead *.input *.spad  exe \"source ~\/.vim\/syntax\/axiom.vim\"\r\n\r\nFor pamphlet files, add\r\n\r\nau BufRead,BufNewFile *.pamphlet   setfiletype tex\r\nau BufRead,BufNewFile *.pamphlet   exe \"source ~\/.vim\/syntax\/pamphlet.vim\"\r\n\r\nto your ~\/.vimrc file.\r\n\r\nPlease read also the axiom\/README file","first_name":"Fabio","6":"Fabio","last_name":"Stumbo","7":"Stumbo","releases":[{"0":"4765","vim_version":"7.0","1":"7.0","script_version":"2.0.0","2":"2.0.0","version_comment":"Added a script to extract keywords from pamphlet files","3":"Added a script to extract keywords from pamphlet files","package":"axiom.vim.tgz","4":"axiom.vim.tgz","src_id":"21075","5":"21075","creation_date":"1384949439","6":"1384949439"},{"0":"4765","vim_version":"7.0","1":"7.0","script_version":"2.0","2":"2.0","version_comment":"Colours are defined in term of standard classes to respect user's colour schemes","3":"Colours are defined in term of standard classes to respect user's colour schemes","package":"axiom.vim.tgz","4":"axiom.vim.tgz","src_id":"21067","5":"21067","creation_date":"1384898224","6":"1384898224"},{"0":"4765","vim_version":"7.0","1":"7.0","script_version":"1.2","2":"1.2","version_comment":"Added syntax for system commands\r\nAdded instructions for better customization","3":"Added syntax for system commands\r\nAdded instructions for better customization","package":"axiom.vim.tgz","4":"axiom.vim.tgz","src_id":"21030","5":"21030","creation_date":"1384258680","6":"1384258680"},{"0":"4765","vim_version":"7.0","1":"7.0","script_version":"1.1","2":"1.1","version_comment":"Made some cleanup","3":"Made some cleanup","package":"axiom.vim.tgz","4":"axiom.vim.tgz","src_id":"21025","5":"21025","creation_date":"1384168429","6":"1384168429"},{"0":"4765","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"axiom.vim.tgz","4":"axiom.vim.tgz","src_id":"21021","5":"21021","creation_date":"1384017821","6":"1384017821"}]},"4764":{"script_id":"4764","0":"4764","script_name":"NERV-ous","1":"NERV-ous","script_type":"color scheme","2":"color scheme","summary":"Evangelion-inspired dark colorscheme","3":"Evangelion-inspired dark colorscheme","description":"An Evangelion-inspired dark colorscheme.\r\nOnly supports GUI for now.\r\n\r\nPreview: http:\/\/cmant.deviantart.com\/art\/NERV-ous-Vim-Colorscheme-412479243","4":"An Evangelion-inspired dark colorscheme.\r\nOnly supports GUI for now.\r\n\r\nPreview: http:\/\/cmant.deviantart.com\/art\/NERV-ous-Vim-Colorscheme-412479243","install_details":"Put nerv-ous.vim in your Vim config directory (e.g. \"~\/.vim\/colors\" or \"<your vim directory>\\vimfiles\\colors\").\r\nUse \":colo nerv-ous\" to set it as the current colorscheme.","5":"Put nerv-ous.vim in your Vim config directory (e.g. \"~\/.vim\/colors\" or \"<your vim directory>\\vimfiles\\colors\").\r\nUse \":colo nerv-ous\" to set it as the current colorscheme.","first_name":"Mattia","6":"Mattia","last_name":"Ferrari","7":"Ferrari","releases":[{"0":"4764","vim_version":"7.0","1":"7.0","script_version":"0.3","2":"0.3","version_comment":"Color tweaks.","3":"Color tweaks.","package":"nerv-ous.vim","4":"nerv-ous.vim","src_id":"21168","5":"21168","creation_date":"1386418137","6":"1386418137"},{"0":"4764","vim_version":"7.0","1":"7.0","script_version":"0.2","2":"0.2","version_comment":"More highlight groups.","3":"More highlight groups.","package":"nerv-ous.vim","4":"nerv-ous.vim","src_id":"21035","5":"21035","creation_date":"1384302500","6":"1384302500"},{"0":"4764","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"nerv-ous.vim","4":"nerv-ous.vim","src_id":"21020","5":"21020","creation_date":"1384003652","6":"1384003652"}]},"4763":{"script_id":"4763","0":"4763","script_name":"cppnav","1":"cppnav","script_type":"utility","2":"utility","summary":"C\/C++ File navigation - using omnicppcomplete","3":"C\/C++ File navigation - using omnicppcomplete","description":"The \"cppnav\" is a source code navigation plugin for c++ and c files. It uses omnicppcomplete  plugin and ctag tool.\r\n\r\nFEATURES:\r\n - Accurate navigation\r\n - Jumping to member function and member variable of class\/struct\r\n - Nested jumping : ctrl-] from a jumped location goes to the next instance. ctrl-t brings back to the original locaiton\r\n - Jumping to files in #include directive\r\n - Prototype preview of functions, macros and variables with single key press\r\n - Function prototype preview while typing the functionName(\r\n - Tab based navigation\r\n      If the identifier is declared in a file in other tab then it jumps\r\n      to the tab instead of opening it in the current window.\r\n                                                                                  \r\n   let g:cppnav_tab = 'never'\r\n  \tDisable tab navigation feature\r\n\r\n   let g:cppnav_tab = 'always'\r\n  \tAlways use tab navigation. Open a new tab if the file is not already opened\r\n\r\n   let g:cppnav_tab = 'only'\r\n  \tUse tab navigation only if the file is already open in another tab or the  current file is not saved.\r\n                                                                                  \r\n USAGE:\r\n  create the 'tags' file using ctag with following options\r\n  \t--fields=+iaS --extra=+fq\r\n                                                                                  \r\n  ctrl-]  = Jump to declaration\r\n  ctrl-t  = Jump back from declaration\r\n  <space> = Quick prototype preview (editor bottom)\r\n  _       = Preview the declaration file (preview window)\r\n  -       = Jump to the declaration file (preview window)\r\n\r\n\r\nCheck out the Projx plugin for automatic tag creation and project file management\r\n   http:\/\/www.vim.org\/scripts\/script.php?script_id=4776","4":"The \"cppnav\" is a source code navigation plugin for c++ and c files. It uses omnicppcomplete  plugin and ctag tool.\r\n\r\nFEATURES:\r\n - Accurate navigation\r\n - Jumping to member function and member variable of class\/struct\r\n - Nested jumping : ctrl-] from a jumped location goes to the next instance. ctrl-t brings back to the original locaiton\r\n - Jumping to files in #include directive\r\n - Prototype preview of functions, macros and variables with single key press\r\n - Function prototype preview while typing the functionName(\r\n - Tab based navigation\r\n      If the identifier is declared in a file in other tab then it jumps\r\n      to the tab instead of opening it in the current window.\r\n                                                                                  \r\n   let g:cppnav_tab = 'never'\r\n  \tDisable tab navigation feature\r\n\r\n   let g:cppnav_tab = 'always'\r\n  \tAlways use tab navigation. Open a new tab if the file is not already opened\r\n\r\n   let g:cppnav_tab = 'only'\r\n  \tUse tab navigation only if the file is already open in another tab or the  current file is not saved.\r\n                                                                                  \r\n USAGE:\r\n  create the 'tags' file using ctag with following options\r\n  \t--fields=+iaS --extra=+fq\r\n                                                                                  \r\n  ctrl-]  = Jump to declaration\r\n  ctrl-t  = Jump back from declaration\r\n  <space> = Quick prototype preview (editor bottom)\r\n  _       = Preview the declaration file (preview window)\r\n  -       = Jump to the declaration file (preview window)\r\n\r\n\r\nCheck out the Projx plugin for automatic tag creation and project file management\r\n   http:\/\/www.vim.org\/scripts\/script.php?script_id=4776","install_details":"Install omnicppcomplete plugin from\r\n       http:\/\/www.vim.org\/scripts\/script.php?script_id=1520\r\n\r\nLinux\/Unix\/Cygwin : copy the cppnav.vim to ~\/.vim\/plugin\/ directory\r\nWindows : copy the cppnav.vim to %HOME%\\vimfiles\\plugin\\ directory","5":"Install omnicppcomplete plugin from\r\n       http:\/\/www.vim.org\/scripts\/script.php?script_id=1520\r\n\r\nLinux\/Unix\/Cygwin : copy the cppnav.vim to ~\/.vim\/plugin\/ directory\r\nWindows : copy the cppnav.vim to %HOME%\\vimfiles\\plugin\\ directory","first_name":"Sureshkumar","6":"Sureshkumar","last_name":"Manimuthu","7":"Manimuthu","releases":[{"0":"4763","vim_version":"7.0","1":"7.0","script_version":"1.3","2":"1.3","version_comment":"Nested jump : If ctrl-] pressed again from the jumped location, it jumps to the next instance","3":"Nested jump : If ctrl-] pressed again from the jumped location, it jumps to the next instance","package":"cppnav.vim","4":"cppnav.vim","src_id":"21128","5":"21128","creation_date":"1385774664","6":"1385774664"},{"0":"4763","vim_version":"7.0","1":"7.0","script_version":"1.2","2":"1.2","version_comment":"- Function prototype preview while typing functionName(\r\n- Fixed : Prototype preview on the same file that is modified having issue","3":"- Function prototype preview while typing functionName(\r\n- Fixed : Prototype preview on the same file that is modified having issue","package":"cppnav.vim","4":"cppnav.vim","src_id":"21109","5":"21109","creation_date":"1385425917","6":"1385425917"},{"0":"4763","vim_version":"7.0","1":"7.0","script_version":"1.1","2":"1.1","version_comment":"Tab based navigation support added.\r\nUse g:cppnav_tab variable to control the behavior","3":"Tab based navigation support added.\r\nUse g:cppnav_tab variable to control the behavior","package":"cppnav.vim","4":"cppnav.vim","src_id":"21080","5":"21080","creation_date":"1385009655","6":"1385009655"},{"0":"4763","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"cppnav.vim","4":"cppnav.vim","src_id":"21016","5":"21016","creation_date":"1383910102","6":"1383910102"}]},"4762":{"script_id":"4762","0":"4762","script_name":"vim-sunflower","1":"vim-sunflower","script_type":"utility","2":"utility","summary":"Switch colorscheme depending on whether it is day or night.","3":"Switch colorscheme depending on whether it is day or night.","description":"For details and most up-to-date sources, see https:\/\/github.com\/kayaalpg\/vim-sunflower","4":"For details and most up-to-date sources, see https:\/\/github.com\/kayaalpg\/vim-sunflower","install_details":"","5":"","first_name":"G\u00c3\u00b6ktu\u011f","6":"G\u00c3\u00b6ktuğ","last_name":"Kayaalp","7":"Kayaalp","releases":[{"0":"4762","vim_version":"7.0","1":"7.0","script_version":"0.1.1","2":"0.1.1","version_comment":"Initial upload","3":"Initial upload","package":"vim-sunflower-0.1.1.tar.gz","4":"vim-sunflower-0.1.1.tar.gz","src_id":"21012","5":"21012","creation_date":"1383829984","6":"1383829984"}]},"4761":{"script_id":"4761","0":"4761","script_name":"HowMuch","1":"HowMuch","script_type":"utility","2":"utility","summary":"A Vim calculator for visual selections","3":"A Vim calculator for visual selections","description":"Project Home: https:\/\/github.com\/sk1418\/HowMuch\r\n\r\n\r\n##Introduction\r\n`HowMuch` is a Vim plugin to calculate visual selected mathematical formulars (vim or bc expressions). It will add the result(or replace the selected expressions) in the current edit text. For details check next section: Features \r\n\r\n##Features\r\n\r\n- Supports all visual selection modes (char-\/line-\/block-wise)\r\n- Supports two output formats: \r\n    >> - append result with\/out `=` after the expression \r\n    >>- replace the selected expressions with result\r\n- Supports sum total result in line-(`V`) and block-wise (`Ctrl-V`)selection\r\n- You can create custom mapping to invoke `HowMuch`\r\n- *Evaluation \"Engines\"* (The expression evaluator)\r\n     >>- `HowMuch` supports `GNU bc`, `python` and `native vim` expressions evaluation engines,\r\n     >>- You can choose which engine should be used to evaluate current visual section.\r\n     >>- You can define the order of the engines, and let `HowMuch` do evaluation automatically. E.g. if `bc` fails, try `vim` again.\r\n     >>- You can add your own engines or modify the built-in engines. read documentation for details.\r\n\r\n**!Please read plugin documentation (HowMuch-config section) for options, mappings**\r\n\r\n##Examples & Screencasts\r\n\r\nDemo animation (gif) could be found at Project Home page(https:\/\/github.com\/sk1418\/HowMuch). The gif files were packed in the release archive as well.\r\n","4":"Project Home: https:\/\/github.com\/sk1418\/HowMuch\r\n\r\n\r\n##Introduction\r\n`HowMuch` is a Vim plugin to calculate visual selected mathematical formulars (vim or bc expressions). It will add the result(or replace the selected expressions) in the current edit text. For details check next section: Features \r\n\r\n##Features\r\n\r\n- Supports all visual selection modes (char-\/line-\/block-wise)\r\n- Supports two output formats: \r\n    >> - append result with\/out `=` after the expression \r\n    >>- replace the selected expressions with result\r\n- Supports sum total result in line-(`V`) and block-wise (`Ctrl-V`)selection\r\n- You can create custom mapping to invoke `HowMuch`\r\n- *Evaluation \"Engines\"* (The expression evaluator)\r\n     >>- `HowMuch` supports `GNU bc`, `python` and `native vim` expressions evaluation engines,\r\n     >>- You can choose which engine should be used to evaluate current visual section.\r\n     >>- You can define the order of the engines, and let `HowMuch` do evaluation automatically. E.g. if `bc` fails, try `vim` again.\r\n     >>- You can add your own engines or modify the built-in engines. read documentation for details.\r\n\r\n**!Please read plugin documentation (HowMuch-config section) for options, mappings**\r\n\r\n##Examples & Screencasts\r\n\r\nDemo animation (gif) could be found at Project Home page(https:\/\/github.com\/sk1418\/HowMuch). The gif files were packed in the release archive as well.\r\n","install_details":"extract the archive into ~\/.vim","5":"extract the archive into ~\/.vim","first_name":"Kent","6":"Kent","last_name":"Yuan","7":"Yuan","releases":[{"0":"4761","vim_version":"7.3","1":"7.3","script_version":"1.0.0","2":"1.0.0","version_comment":"Initial upload","3":"Initial upload","package":"HowMuch.tar.gz","4":"HowMuch.tar.gz","src_id":"21010","5":"21010","creation_date":"1383745720","6":"1383745720"}]},"4760":{"script_id":"4760","0":"4760","script_name":"vim-gnote","1":"vim-gnote","script_type":"utility","2":"utility","summary":"keep your note in your gmail special box","3":"keep your note in your gmail special box","description":"use you gmail as your note place. When you use this plugin, your can send the current text to your gmail, within the default inbox named \"gnote\",\r\nthe subject of your note will be your filename without suffix by default, so same filename(without suffix) will be in same dialogue. Just have a try, you'll see the effect.\r\n(any updates, please star at my github: https:\/\/github.com\/Zuckonit\/vim-gnote )","4":"use you gmail as your note place. When you use this plugin, your can send the current text to your gmail, within the default inbox named \"gnote\",\r\nthe subject of your note will be your filename without suffix by default, so same filename(without suffix) will be in same dialogue. Just have a try, you'll see the effect.\r\n(any updates, please star at my github: https:\/\/github.com\/Zuckonit\/vim-gnote )","install_details":"https:\/\/github.com\/Zuckonit\/vim-gnote","5":"https:\/\/github.com\/Zuckonit\/vim-gnote","first_name":"Mocker","6":"Mocker","last_name":"Yang","7":"Yang","releases":[{"0":"4760","vim_version":"7.0","1":"7.0","script_version":"0.02","2":"0.02","version_comment":"not only gmail, other mail (can use imap) supported. please update your configuration, just take a look at README.md or doc\/gnote.txt","3":"not only gmail, other mail (can use imap) supported. please update your configuration, just take a look at README.md or doc\/gnote.txt","package":"vim-gnote.zip","4":"vim-gnote.zip","src_id":"21008","5":"21008","creation_date":"1383705528","6":"1383705528"},{"0":"4760","vim_version":"7.0","1":"7.0","script_version":"0.01","2":"0.01","version_comment":"Initial upload","3":"Initial upload","package":"vim-gnote.zip","4":"vim-gnote.zip","src_id":"21007","5":"21007","creation_date":"1383642991","6":"1383642991"}]},"4759":{"script_id":"4759","0":"4759","script_name":"minimal_gdb","1":"minimal_gdb","script_type":"utility","2":"utility","summary":"lightweight vim->gdb broker. set and auto export breakpoints to gdb","3":"lightweight vim->gdb broker. set and auto export breakpoints to gdb","description":"Minimal gdb is a lightweight vim->gdb broker, that only allows you to set breakpoints in vim and automatically export them to gdb.\r\n\r\n\r\nOFFICIAL GITHUB: https:\/\/github.com\/mechatroner\/minimal_gdb\r\n\r\n\r\nYou can't use the Minimal gdb for debugging inside vim windows, you have to start a separate gdb session, but all the breakpoints you've set will be magicaly (via .gdbinit actually) active in the debugger.\r\nThe main difference from other similiar gdb vim plugins, is that Minimal gdb uses the .gdbinit file for breakpoint export and doesn't allow in-window fully integrated debugging in vim. If some new breakpoints are set in vim after gdb startup, one has to run \"syncbp\" command in gdb or restart the debugger in order to import them.\r\nThe \"syncbp\" command will be added to gdb on the plugin first run via .gdbinit magic.\r\n\r\nA typical use case looks like this:\r\n    1. set some breakpoints in vim, they will be highlighted in the 'sign' column\r\n    2. run gdb, which will automatically export the breakpoints from step 1.\r\n    3. set some more breakpoints\r\n    4. export them in gdb by using the new gdb \"synbp\" command, or by restarting the debugger (the former is easier).\r\n\r\nINSTALLATION:\r\n    Copy the files to your .vim folder or use Vundle.\r\n    The script will configure everything when you set a first breakpoint\r\n\r\nCOMMANDS:\r\n    In vim:\r\n    MinGDBToggleBP or <leader>b - toggles a breakpoint.\r\n    MinGDBDeleteAll - delete all breakpoints\r\n    MinGDBRefreshFile - refresh breakpoints positions in a vim file. Use this in case something went wrong.\r\n\r\n    In gdb:\r\n    synbp - export new breakpoints from vim, which were set after gdb session has started.\r\n\r\n\r\nREQUIREMENTS:\r\n    gdb \r\n    python 2.7 \r\n    vim compiled with python and signs features.\r\n\r\n\r\nTested with vim and gvim in linux and freebsd","4":"Minimal gdb is a lightweight vim->gdb broker, that only allows you to set breakpoints in vim and automatically export them to gdb.\r\n\r\n\r\nOFFICIAL GITHUB: https:\/\/github.com\/mechatroner\/minimal_gdb\r\n\r\n\r\nYou can't use the Minimal gdb for debugging inside vim windows, you have to start a separate gdb session, but all the breakpoints you've set will be magicaly (via .gdbinit actually) active in the debugger.\r\nThe main difference from other similiar gdb vim plugins, is that Minimal gdb uses the .gdbinit file for breakpoint export and doesn't allow in-window fully integrated debugging in vim. If some new breakpoints are set in vim after gdb startup, one has to run \"syncbp\" command in gdb or restart the debugger in order to import them.\r\nThe \"syncbp\" command will be added to gdb on the plugin first run via .gdbinit magic.\r\n\r\nA typical use case looks like this:\r\n    1. set some breakpoints in vim, they will be highlighted in the 'sign' column\r\n    2. run gdb, which will automatically export the breakpoints from step 1.\r\n    3. set some more breakpoints\r\n    4. export them in gdb by using the new gdb \"synbp\" command, or by restarting the debugger (the former is easier).\r\n\r\nINSTALLATION:\r\n    Copy the files to your .vim folder or use Vundle.\r\n    The script will configure everything when you set a first breakpoint\r\n\r\nCOMMANDS:\r\n    In vim:\r\n    MinGDBToggleBP or <leader>b - toggles a breakpoint.\r\n    MinGDBDeleteAll - delete all breakpoints\r\n    MinGDBRefreshFile - refresh breakpoints positions in a vim file. Use this in case something went wrong.\r\n\r\n    In gdb:\r\n    synbp - export new breakpoints from vim, which were set after gdb session has started.\r\n\r\n\r\nREQUIREMENTS:\r\n    gdb \r\n    python 2.7 \r\n    vim compiled with python and signs features.\r\n\r\n\r\nTested with vim and gvim in linux and freebsd","install_details":"add mechatroner\/minimal_gdb to your Vundle or manualy copy the files from the archive.","5":"add mechatroner\/minimal_gdb to your Vundle or manualy copy the files from the archive.","first_name":"Dmitry","6":"Dmitry","last_name":"Ignatovich","7":"Ignatovich","releases":[{"0":"4759","vim_version":"7.3","1":"7.3","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"minimal_gdb.tar.gz","4":"minimal_gdb.tar.gz","src_id":"21005","5":"21005","creation_date":"1383607774","6":"1383607774"}]},"4758":{"script_id":"4758","0":"4758","script_name":"Cosco","1":"Cosco","script_type":"utility","2":"utility","summary":"Colon and semicolon insertion bliss","3":"Colon and semicolon insertion bliss","description":"What Cosco does:\r\n\r\nAppends, substitutes or removes a comma or a semi-colon to the end of your line, based on its context.\r\n\r\nIt:\r\n\r\nTakes into consideration previous and next lines endings, as well line indentations.\r\nIgnores blank lines.\r\nWill maintain your cursor's original position.\r\nThe best way to describe it is with examples -- take a look at the official page on GitHub to see examples.\r\n\r\nFor examples, installation and usage, see the documentation at:\r\n\r\nOFFICIAL GITHUB: https:\/\/github.com\/lfilho\/cosco.vim","4":"What Cosco does:\r\n\r\nAppends, substitutes or removes a comma or a semi-colon to the end of your line, based on its context.\r\n\r\nIt:\r\n\r\nTakes into consideration previous and next lines endings, as well line indentations.\r\nIgnores blank lines.\r\nWill maintain your cursor's original position.\r\nThe best way to describe it is with examples -- take a look at the official page on GitHub to see examples.\r\n\r\nFor examples, installation and usage, see the documentation at:\r\n\r\nOFFICIAL GITHUB: https:\/\/github.com\/lfilho\/cosco.vim","install_details":"1- Add lfilho\/cosco.vim to your Vundle, NeoBundle, pathogen, or manually copy the files... You know the deal.\r\n2- Run your Vundle\/NeoBundle\/pathogen process of updating \/ installing new bundles... \r\n3- Use it (see https:\/\/github.com\/lfilho\/cosco.vim for more details)\r\n4- Profit!","5":"1- Add lfilho\/cosco.vim to your Vundle, NeoBundle, pathogen, or manually copy the files... You know the deal.\r\n2- Run your Vundle\/NeoBundle\/pathogen process of updating \/ installing new bundles... \r\n3- Use it (see https:\/\/github.com\/lfilho\/cosco.vim for more details)\r\n4- Profit!","first_name":"Luiz","6":"Luiz","last_name":"Filho","7":"Filho","releases":[{"0":"4758","vim_version":"7.0","1":"7.0","script_version":"0.10.0","2":"0.10.0","version_comment":"- Support for whitelisting and blacklisting files based on filetypes\r\n- Support for ignoring comment lines\r\n- Bug fix for next lines starting with {","3":"- Support for whitelisting and blacklisting files based on filetypes\r\n- Support for ignoring comment lines\r\n- Bug fix for next lines starting with {","package":"cosco.vim-0.10.0.zip","4":"cosco.vim-0.10.0.zip","src_id":"25435","5":"25435","creation_date":"1500801023","6":"1500801023"},{"0":"4758","vim_version":"7.0","1":"7.0","script_version":"0.9.0","2":"0.9.0","version_comment":"Add <Plug> mappings; Add vim-repeat support (and dependency)","3":"Add <Plug> mappings; Add vim-repeat support (and dependency)","package":"cosco.vim-v0.9.0.zip","4":"cosco.vim-v0.9.0.zip","src_id":"24409","5":"24409","creation_date":"1469725664","6":"1469725664"},{"0":"4758","vim_version":"7.0","1":"7.0","script_version":"0.8.5","2":"0.8.5","version_comment":"Initial upload","3":"Initial upload","package":"cosco.vim-v0.8.5.zip","4":"cosco.vim-v0.8.5.zip","src_id":"21002","5":"21002","creation_date":"1383479738","6":"1383479738"}]},"4757":{"script_id":"4757","0":"4757","script_name":"SlateDark","1":"SlateDark","script_type":"color scheme","2":"color scheme","summary":"Dark vim color scheme inspired by Slate.","3":"Dark vim color scheme inspired by Slate.","description":"This is a fork from the Slate color scheme Ralph Amissah. The main difference in the white background in some types.","4":"This is a fork from the Slate color scheme Ralph Amissah. The main difference in the white background in some types.","install_details":"","5":"","first_name":"Rudra","6":"Rudra","last_name":"Banerjee","7":"Banerjee","releases":[{"0":"4757","vim_version":"7.0","1":"7.0","script_version":"0.01","2":"0.01","version_comment":"initial upload","3":"initial upload","package":"SlateDark.vim","4":"SlateDark.vim","src_id":"21001","5":"21001","creation_date":"1383477071","6":"1383477071"}]},"4756":{"script_id":"4756","0":"4756","script_name":"vim-airline-tomato","1":"vim-airline-tomato","script_type":"utility","2":"utility","summary":"Pomodoro Technique ","3":"Pomodoro Technique ","description":"This is vim-airline extension to display Pomodoro Technique\r\n(get the latest version on https:\/\/github.com\/Zuckonit\/vim-airline-tomato )\r\nRequired\r\nAirline: This is a extension of airline (like powerline, but more fast and KISS)\r\npowerline-font: if you use chinese font, you may need install powerline font\r\nConfiguration\r\n` If you want to change the working time:\r\n\r\nlet g:tomato#interval = 60 * 60\r\n< If you wat to change rest time:\r\n\r\nlet g:tomato#rest_time = 20 * 60\r\n< If you wat to change language(english or chinese):\r\n\r\nlet g:tomato#lang = 'chinese'\r\nIf you wat to change working text:\r\n\r\nlet g:tomato#remind = \":(\"\r\nIf you wat to change rest text:\r\n\r\nlet g:tomato#remind = \":)\"\r\n","4":"This is vim-airline extension to display Pomodoro Technique\r\n(get the latest version on https:\/\/github.com\/Zuckonit\/vim-airline-tomato )\r\nRequired\r\nAirline: This is a extension of airline (like powerline, but more fast and KISS)\r\npowerline-font: if you use chinese font, you may need install powerline font\r\nConfiguration\r\n` If you want to change the working time:\r\n\r\nlet g:tomato#interval = 60 * 60\r\n< If you wat to change rest time:\r\n\r\nlet g:tomato#rest_time = 20 * 60\r\n< If you wat to change language(english or chinese):\r\n\r\nlet g:tomato#lang = 'chinese'\r\nIf you wat to change working text:\r\n\r\nlet g:tomato#remind = \":(\"\r\nIf you wat to change rest text:\r\n\r\nlet g:tomato#remind = \":)\"\r\n","install_details":"https:\/\/github.com\/Zuckonit\/vim-airline-tomato","5":"https:\/\/github.com\/Zuckonit\/vim-airline-tomato","first_name":"Mocker","6":"Mocker","last_name":"Yang","7":"Yang","releases":[{"0":"4756","vim_version":"7.2","1":"7.2","script_version":"0.02","2":"0.02","version_comment":"urgent bugfix, please use version 0.02\r\nPlease see the latest version on my github","3":"urgent bugfix, please use version 0.02\r\nPlease see the latest version on my github","package":"vim-airline-tomato.zip","4":"vim-airline-tomato.zip","src_id":"20991","5":"20991","creation_date":"1383272308","6":"1383272308"}]},"4755":{"script_id":"4755","0":"4755","script_name":"launchassociated.vim","1":"launchassociated.vim","script_type":"utility","2":"utility","summary":"Launches current file with the associated program.","3":"Launches current file with the associated program.","description":"launchassociated.vim\r\nLaunches current file with the associated program.\r\n\r\nFor example, if you are editing an HTML file, and type the command LaunchAssociated, your default browser will open it.\r\n\r\nIt can be used on any file type, such as .xml, .html, .java or even .png, anything that is associated with a program.\r\n\r\nhttps:\/\/github.com\/caglartoklu\/launchassociated.vim\r\n\r\nThe development is on Github.\r\nFor documentation, please visit the homepage link.\r\nFunctionality changes will still be reflected to Vim.org page.","4":"launchassociated.vim\r\nLaunches current file with the associated program.\r\n\r\nFor example, if you are editing an HTML file, and type the command LaunchAssociated, your default browser will open it.\r\n\r\nIt can be used on any file type, such as .xml, .html, .java or even .png, anything that is associated with a program.\r\n\r\nhttps:\/\/github.com\/caglartoklu\/launchassociated.vim\r\n\r\nThe development is on Github.\r\nFor documentation, please visit the homepage link.\r\nFunctionality changes will still be reflected to Vim.org page.","install_details":"For Vundle users:\r\n    Plugin 'caglartoklu\/launchassociated.vim'\r\n\r\nFor Pathogen users:\r\n    cd ~\/.vim\/bundle\r\n    git clone git:\/\/github.com\/caglartoklu\/launchassociated.vim\r\n\r\nFor all other users, simply drop the launchassociated.vim file to your plugin directory.","5":"For Vundle users:\r\n    Plugin 'caglartoklu\/launchassociated.vim'\r\n\r\nFor Pathogen users:\r\n    cd ~\/.vim\/bundle\r\n    git clone git:\/\/github.com\/caglartoklu\/launchassociated.vim\r\n\r\nFor all other users, simply drop the launchassociated.vim file to your plugin directory.","first_name":"Caglar","6":"Caglar","last_name":"Toklu","7":"Toklu","releases":[{"0":"4755","vim_version":"7.0","1":"7.0","script_version":"0.0.2","2":"0.0.2","version_comment":"Added SelectInFileManager command (currently, Windows only).\r\nThis command will open the file manager and the buffer will be selected by default.","3":"Added SelectInFileManager command (currently, Windows only).\r\nThis command will open the file manager and the buffer will be selected by default.","package":"launchassociated.vim","4":"launchassociated.vim","src_id":"23203","5":"23203","creation_date":"1429635854","6":"1429635854"},{"0":"4755","vim_version":"7.0","1":"7.0","script_version":"0.0.1","2":"0.0.1","version_comment":"Initial upload","3":"Initial upload","package":"launchassociated.vim","4":"launchassociated.vim","src_id":"20972","5":"20972","creation_date":"1382973707","6":"1382973707"}]},"4754":{"script_id":"4754","0":"4754","script_name":"mlessnau_block_shift","1":"mlessnau_block_shift","script_type":"utility","2":"utility","summary":"Line-wise up\/down shift of selected blocks","3":"Line-wise up\/down shift of selected blocks","description":"The plugin implements 2 functions: BlockShiftUp() and BlockShiftDown(). When selecting blocks of text in visual mode, these functions will shift the block one up, or down. The textmanip plugin offers equal functionality but did not behave the way I would've expect it.","4":"The plugin implements 2 functions: BlockShiftUp() and BlockShiftDown(). When selecting blocks of text in visual mode, these functions will shift the block one up, or down. The textmanip plugin offers equal functionality but did not behave the way I would've expect it.","install_details":"Copy the file into you plugins directory (i.e. ~\/.vim\/plugins). Now you need to define the keyboard mappings in your .vimrc file:\r\n\r\nvmap <C-k> :call BlockShiftUp()<CR>\r\nvmap <C-j> :call BlockShiftDown()<CR>\r\n\r\nSo, when you're in visual mode and selected a block of text, you now can shift it up\/down by pressing [Ctrl]+[k] and [Ctrl]+[j].","5":"Copy the file into you plugins directory (i.e. ~\/.vim\/plugins). Now you need to define the keyboard mappings in your .vimrc file:\r\n\r\nvmap <C-k> :call BlockShiftUp()<CR>\r\nvmap <C-j> :call BlockShiftDown()<CR>\r\n\r\nSo, when you're in visual mode and selected a block of text, you now can shift it up\/down by pressing [Ctrl]+[k] and [Ctrl]+[j].","first_name":"Michael","6":"Michael","last_name":"Le\u00c3\u009fnau","7":"Le\u00c3\u009fnau","releases":[{"0":"4754","vim_version":"7.3","1":"7.3","script_version":"0.0.1","2":"0.0.1","version_comment":"Initial upload","3":"Initial upload","package":"mlessnau_block_shift.vim","4":"mlessnau_block_shift.vim","src_id":"20968","5":"20968","creation_date":"1382881178","6":"1382881178"}]},"4753":{"script_id":"4753","0":"4753","script_name":"OpenURL","1":"OpenURL","script_type":"utility","2":"utility","summary":"Opens links found on the current line; can also send emails (with mailto:\/\/)","3":"Opens links found on the current line; can also send emails (with mailto:\/\/)","description":"Type :OpenURL to start the utility.\r\nIt will then search the current line for links, if only one link is found then this link is opened.\r\nIf several links are found; OpenURL will display a prompt like this one:\r\n\r\n1: http:\/\/www.vim.org\r\n2: www.youtube.com\r\n3: mailto:\/\/jonasmo441@gmail.com\r\n?> \r\n\r\nYou then answer accordingly with a number.\r\n\r\nThe following kinds of urls are allowed:\r\nprotocol:\/\/domain.ext\r\nprotocol:\/\/www.domain.ext\r\nprotocol:\/\/www.subdomain.domain.ext\r\nwww.domain.ext\r\nuser@domain.ext\r\n\r\nIf an email address is found; mailto:\/\/ will be the assumed protocol.\r\nIf a www.___.___ link is found; http:\/\/ will be the assumed protocol.\r\n                            \r\nThese protocols are used\/found by OpenURL:\r\nhttp(s):\/\/\r\nftp(s):\/\/\r\nmailto:\/\/\r\n\r\nYou can send any bugs or feature requests to my email address.\r\n\r\nOpenURL.vim  Copyright (C) 2013  Jonas M\u00c3\u00b8ller <jonasmo441@gmail.com>\r\n    This program comes with ABSOLUTELY NO WARRANTY\r\n    This is free software, and you are welcome to redistribute it\r\n    under certain conditions; go to http:\/\/www.gnu.org\/copyleft\/gpl.html for details","4":"Type :OpenURL to start the utility.\r\nIt will then search the current line for links, if only one link is found then this link is opened.\r\nIf several links are found; OpenURL will display a prompt like this one:\r\n\r\n1: http:\/\/www.vim.org\r\n2: www.youtube.com\r\n3: mailto:\/\/jonasmo441@gmail.com\r\n?> \r\n\r\nYou then answer accordingly with a number.\r\n\r\nThe following kinds of urls are allowed:\r\nprotocol:\/\/domain.ext\r\nprotocol:\/\/www.domain.ext\r\nprotocol:\/\/www.subdomain.domain.ext\r\nwww.domain.ext\r\nuser@domain.ext\r\n\r\nIf an email address is found; mailto:\/\/ will be the assumed protocol.\r\nIf a www.___.___ link is found; http:\/\/ will be the assumed protocol.\r\n                            \r\nThese protocols are used\/found by OpenURL:\r\nhttp(s):\/\/\r\nftp(s):\/\/\r\nmailto:\/\/\r\n\r\nYou can send any bugs or feature requests to my email address.\r\n\r\nOpenURL.vim  Copyright (C) 2013  Jonas M\u00c3\u00b8ller <jonasmo441@gmail.com>\r\n    This program comes with ABSOLUTELY NO WARRANTY\r\n    This is free software, and you are welcome to redistribute it\r\n    under certain conditions; go to http:\/\/www.gnu.org\/copyleft\/gpl.html for details","install_details":"Linux\/Mac\/BSD: \r\n        Put the \"OpenURL.vim\" file inside ~\/.vim\/plugin\/ and restart vim \r\n\r\nWindows: \r\n        Put the \"OpenURL.vim\" file inside C:\\Program Files (x86)\\Vim\\vim74\\plugin (requires admin rights) and restart vim.","5":"Linux\/Mac\/BSD: \r\n        Put the \"OpenURL.vim\" file inside ~\/.vim\/plugin\/ and restart vim \r\n\r\nWindows: \r\n        Put the \"OpenURL.vim\" file inside C:\\Program Files (x86)\\Vim\\vim74\\plugin (requires admin rights) and restart vim.","first_name":"Jonas","6":"Jonas","last_name":"M\u00c3\u00b8ller","7":"M\u00c3\u00b8ller","releases":[{"0":"4753","vim_version":"7.0","1":"7.0","script_version":"1.1","2":"1.1","version_comment":"Fixed problem with dashes \"-\" in URLS","3":"Fixed problem with dashes \"-\" in URLS","package":"OpenURL.vim","4":"OpenURL.vim","src_id":"20989","5":"20989","creation_date":"1383252690","6":"1383252690"},{"0":"4753","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"OpenURL.vim","4":"OpenURL.vim","src_id":"20964","5":"20964","creation_date":"1382801161","6":"1382801161"}]},"4752":{"script_id":"4752","0":"4752","script_name":"macvim-transparency","1":"macvim-transparency","script_type":"utility","2":"utility","summary":"change macvim transparency easily","3":"change macvim transparency easily","description":"simple transparency change helper.\r\nsee help\r\nand github for animation GIF.\r\n\r\nhttps:\/\/github.com\/t9md\/vim-macvim-transparency","4":"simple transparency change helper.\r\nsee help\r\nand github for animation GIF.\r\n\r\nhttps:\/\/github.com\/t9md\/vim-macvim-transparency","install_details":"","5":"","first_name":"t9","6":"t9","last_name":"md","7":"md","releases":[{"0":"4752","vim_version":"7.3","1":"7.3","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"vim-macvim-transparency-1.0.zip","4":"vim-macvim-transparency-1.0.zip","src_id":"20963","5":"20963","creation_date":"1382799031","6":"1382799031"}]},"4751":{"script_id":"4751","0":"4751","script_name":"ruby-xmpfilter","1":"ruby-xmpfilter","script_type":"utility","2":"utility","summary":"xmpfilter.txt Helper for ruby's xmpfilter or seeing_is_believing ","3":"xmpfilter.txt Helper for ruby's xmpfilter or seeing_is_believing ","description":"Github\r\nhttps:\/\/github.com\/t9md\/vim-ruby-xmpfilter\r\n\r\nvim-ruby-xmpfilter provide keymap that helps you use 'xmpfilter' or\r\n'seeing_is_believing' from Vim.\r\n\r\n * insert\/delete annotation mark \" # =>\".\r\n * virtual keymap for marking and executing 'xmpfilter' or 'seeing_is_believing'\r\n   against current bufffer.\r\n\r\nxmpfilter is provided as part of rcodetools.\r\n http:\/\/rubygems.org\/gems\/rcodetools\r\n\r\nseeing_is_believing\r\n https:\/\/github.com\/JoshCheek\/seeing_is_believing\r\n\r\nInsert \" # =>\" into end of line or delete \" # =>\" if it already exist.\r\n\r\n  normal <Plug>(xmpfilter-mark)\r\n  visual <Plug>(xmpfilter-mark)\r\n  insert <Plug>(xmpfilter-mark)\r\n\r\n  normal <Plug>(seeing_is_believing-mark)\r\n  visual <Plug>(seeing_is_believing-mark)\r\n  insert <Plug>(seeing_is_believing-mark)\r\n\r\nInsert evaluated result at the mark.\r\n\r\n  normal <Plug>(xmpfilter-run)\r\n  visual <Plug>(xmpfilter-run)\r\n  insert <Plug>(xmpfilter-run)\r\n\r\n  normal <Plug>(seeing_is_believing-run_-x)\r\n  visual <Plug>(seeing_is_believing-run_-x)\r\n  insert <Plug>(seeing_is_believing-run_-x)\r\n\r\nInsert evaluated result with mark.\r\nOnly for \"seeing_is_believing\"\r\n\r\n  normal <Plug>(seeing_is_believing-run)\r\n  visual <Plug>(seeing_is_believing-run)\r\n  insert <Plug>(seeing_is_believing-run)\r\n\r\nClean all marks in the buffer\r\nOnly for \"seeing_is_believing\"\r\n\r\n  normal <Plug>(seeing_is_believing-clean)\r\n  visual <Plug>(seeing_is_believing-clean)\r\n  insert <Plug>(seeing_is_believing-clean)\r\n","4":"Github\r\nhttps:\/\/github.com\/t9md\/vim-ruby-xmpfilter\r\n\r\nvim-ruby-xmpfilter provide keymap that helps you use 'xmpfilter' or\r\n'seeing_is_believing' from Vim.\r\n\r\n * insert\/delete annotation mark \" # =>\".\r\n * virtual keymap for marking and executing 'xmpfilter' or 'seeing_is_believing'\r\n   against current bufffer.\r\n\r\nxmpfilter is provided as part of rcodetools.\r\n http:\/\/rubygems.org\/gems\/rcodetools\r\n\r\nseeing_is_believing\r\n https:\/\/github.com\/JoshCheek\/seeing_is_believing\r\n\r\nInsert \" # =>\" into end of line or delete \" # =>\" if it already exist.\r\n\r\n  normal <Plug>(xmpfilter-mark)\r\n  visual <Plug>(xmpfilter-mark)\r\n  insert <Plug>(xmpfilter-mark)\r\n\r\n  normal <Plug>(seeing_is_believing-mark)\r\n  visual <Plug>(seeing_is_believing-mark)\r\n  insert <Plug>(seeing_is_believing-mark)\r\n\r\nInsert evaluated result at the mark.\r\n\r\n  normal <Plug>(xmpfilter-run)\r\n  visual <Plug>(xmpfilter-run)\r\n  insert <Plug>(xmpfilter-run)\r\n\r\n  normal <Plug>(seeing_is_believing-run_-x)\r\n  visual <Plug>(seeing_is_believing-run_-x)\r\n  insert <Plug>(seeing_is_believing-run_-x)\r\n\r\nInsert evaluated result with mark.\r\nOnly for \"seeing_is_believing\"\r\n\r\n  normal <Plug>(seeing_is_believing-run)\r\n  visual <Plug>(seeing_is_believing-run)\r\n  insert <Plug>(seeing_is_believing-run)\r\n\r\nClean all marks in the buffer\r\nOnly for \"seeing_is_believing\"\r\n\r\n  normal <Plug>(seeing_is_believing-clean)\r\n  visual <Plug>(seeing_is_believing-clean)\r\n  insert <Plug>(seeing_is_believing-clean)\r\n","install_details":"","5":"","first_name":"t9","6":"t9","last_name":"md","7":"md","releases":[{"0":"4751","vim_version":"7.0","1":"7.0","script_version":"1.1","2":"1.1","version_comment":"Initial upload","3":"Initial upload","package":"vim-ruby-xmpfilter-1.1.zip","4":"vim-ruby-xmpfilter-1.1.zip","src_id":"20962","5":"20962","creation_date":"1382796889","6":"1382796889"}]},"4750":{"script_id":"4750","0":"4750","script_name":"human.vim","1":"human.vim","script_type":"ftplugin","2":"ftplugin","summary":"Vim plugin to enhance the writing of human readable formats, such as Markdown.","3":"Vim plugin to enhance the writing of human readable formats, such as Markdown.","description":"Vim plugin to enhance the writing of human readable formats, such as Markdown.\r\n\r\nThis plugins sets auto paragraph formatting and convenient writing options to formats known to be read by humans, such as Markdown or Git commit message.\r\n\r\nIf you have any comments, fixes or requests, feel free to contact me or send me a patch.\r\nThe development also takes place at https:\/\/github.com\/vivien\/vim-human","4":"Vim plugin to enhance the writing of human readable formats, such as Markdown.\r\n\r\nThis plugins sets auto paragraph formatting and convenient writing options to formats known to be read by humans, such as Markdown or Git commit message.\r\n\r\nIf you have any comments, fixes or requests, feel free to contact me or send me a patch.\r\nThe development also takes place at https:\/\/github.com\/vivien\/vim-human","install_details":"Just copy the linuxsty.vim file in your ~\/.vim\/plugin directory.","5":"Just copy the linuxsty.vim file in your ~\/.vim\/plugin directory.","first_name":"Vivien","6":"Vivien","last_name":"Didelot","7":"Didelot","releases":[{"0":"4750","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"human.vim","4":"human.vim","src_id":"20958","5":"20958","creation_date":"1382744700","6":"1382744700"}]},"4749":{"script_id":"4749","0":"4749","script_name":"vim-gains-nrepl","1":"vim-gains-nrepl","script_type":"utility","2":"utility","summary":"Simple vim plugin for dealing with nrepl","3":"Simple vim plugin for dealing with nrepl","description":"This has been intended to be a simple way to talk to nrepl from Vim. I've almost succeed - the only excess here is nREPL sessions support, but it is important - it enables ClojureScript support.\r\nThe project lives here https:\/\/github.com\/shashurup\/vim-gains-nrepl","4":"This has been intended to be a simple way to talk to nrepl from Vim. I've almost succeed - the only excess here is nREPL sessions support, but it is important - it enables ClojureScript support.\r\nThe project lives here https:\/\/github.com\/shashurup\/vim-gains-nrepl","install_details":"You need Vim => 7.4 with Python support to use this plugin. ","5":"You need Vim => 7.4 with Python support to use this plugin. ","first_name":"Georgy","6":"Georgy","last_name":"Kibardin","7":"Kibardin","releases":[{"0":"4749","vim_version":"7.4","1":"7.4","script_version":"0.3","2":"0.3","version_comment":"Ability to send repl output to a buffer. Minor bugfixes.","3":"Ability to send repl output to a buffer. Minor bugfixes.","package":"vim-gains-nrepl-0.3.zip","4":"vim-gains-nrepl-0.3.zip","src_id":"23629","5":"23629","creation_date":"1443619842","6":"1443619842"},{"0":"4749","vim_version":"7.3","1":"7.3","script_version":"0.2","2":"0.2","version_comment":"Initial upload","3":"Initial upload","package":"vim-gains-nrepl-0.2.zip","4":"vim-gains-nrepl-0.2.zip","src_id":"20930","5":"20930","creation_date":"1382112398","6":"1382112398"}]},"4748":{"script_id":"4748","0":"4748","script_name":"JavaScript Context Coloring","1":"JavaScript Context Coloring","script_type":"ftplugin","2":"ftplugin","summary":"JavaScript plugin to highlight scope regions","3":"JavaScript plugin to highlight scope regions","description":"This is a plugin for the Vim text editor to highlight JavaScript code \r\naccording to its scope. This was inspired by an idea by Douglas Crockford\r\nin his presentation (http:\/\/www.youtube.com\/watch?v=dkZFtimgAcM) at YUIConf 2012.\r\n(See from around the 16 minute mark onwards.) \r\n\r\nThe GitHub repo will always have latest version:\r\n\r\nhttps:\/\/github.com\/bigfish\/vim-js-context-coloring\r\n","4":"This is a plugin for the Vim text editor to highlight JavaScript code \r\naccording to its scope. This was inspired by an idea by Douglas Crockford\r\nin his presentation (http:\/\/www.youtube.com\/watch?v=dkZFtimgAcM) at YUIConf 2012.\r\n(See from around the 16 minute mark onwards.) \r\n\r\nThe GitHub repo will always have latest version:\r\n\r\nhttps:\/\/github.com\/bigfish\/vim-js-context-coloring\r\n","install_details":"Node.js is currently required for the script to work.\r\n\r\nRecommended Installation Method: Use Pathogen.\r\n\r\n0. install Pathogen (https:\/\/github.com\/tpope\/vim-pathogen)\r\n\r\n1. Copy the package, or clone the repo from GitHub into your 'bundle' directory:\r\n\r\n    git clone git@github.com:bigfish\/vim-js-context-coloring.git\r\n\r\n2. install node deps (in repo dir):\r\n    \r\n    npm install\r\n\r\n3. Install docs (in Vim):\r\n\r\n    :Helptags\r\n\r\n\r\nOr you can copy the after\/ftplugin\/javascript.vim file into your VIMHOME, as well as the bin\/ directory.\r\n","5":"Node.js is currently required for the script to work.\r\n\r\nRecommended Installation Method: Use Pathogen.\r\n\r\n0. install Pathogen (https:\/\/github.com\/tpope\/vim-pathogen)\r\n\r\n1. Copy the package, or clone the repo from GitHub into your 'bundle' directory:\r\n\r\n    git clone git@github.com:bigfish\/vim-js-context-coloring.git\r\n\r\n2. install node deps (in repo dir):\r\n    \r\n    npm install\r\n\r\n3. Install docs (in Vim):\r\n\r\n    :Helptags\r\n\r\n\r\nOr you can copy the after\/ftplugin\/javascript.vim file into your VIMHOME, as well as the bin\/ directory.\r\n","first_name":"David","6":"David","last_name":"Wilhelm","7":"Wilhelm","releases":[{"0":"4748","vim_version":"7.0","1":"7.0","script_version":"0.0.8","2":"0.0.8","version_comment":"support ES6, JSX.","3":"support ES6, JSX.","package":"vim-js-context-coloring-0.0.8.zip","4":"vim-js-context-coloring-0.0.8.zip","src_id":"23521","5":"23521","creation_date":"1439901983","6":"1439901983"},{"0":"4748","vim_version":"7.2","1":"7.2","script_version":"0.0.6","2":"0.0.6","version_comment":"support gVim and MacVim. \r\nsupport extended color notation.\r\nturn on 'colorize comments' by default.","3":"support gVim and MacVim. \r\nsupport extended color notation.\r\nturn on 'colorize comments' by default.","package":"vim-js-context-coloring-0-0-6.zip","4":"vim-js-context-coloring-0-0-6.zip","src_id":"21423","5":"21423","creation_date":"1391457703","6":"1391457703"},{"0":"4748","vim_version":"7.3","1":"7.3","script_version":"0.0.5","2":"0.0.5","version_comment":"- make default colors 16 color safe\r\n- add instructions to get 256 color support working in terminal\r\n- ensure disabling works.","3":"- make default colors 16 color safe\r\n- add instructions to get 256 color support working in terminal\r\n- ensure disabling works.","package":"vim-js-context-coloring-master.zip","4":"vim-js-context-coloring-master.zip","src_id":"21281","5":"21281","creation_date":"1388986133","6":"1388986133"},{"0":"4748","vim_version":"7.3","1":"7.3","script_version":"0.0.4","2":"0.0.4","version_comment":"Added support for 7.3, though 7.4 is recommended. \r\n\r\nFixed range overrun by one character at end of function expressions (via update to node lib eslevels)\r\n\r\nUpdate instructions: run 'npm install --update' to update the eslevels dependency.","3":"Added support for 7.3, though 7.4 is recommended. \r\n\r\nFixed range overrun by one character at end of function expressions (via update to node lib eslevels)\r\n\r\nUpdate instructions: run 'npm install --update' to update the eslevels dependency.","package":"vim-js-context-coloring-0-0-4.zip","4":"vim-js-context-coloring-0-0-4.zip","src_id":"20993","5":"20993","creation_date":"1383354502","6":"1383354502"},{"0":"4748","vim_version":"7.0","1":"7.0","script_version":"0.0.3","2":"0.0.3","version_comment":"made more tolerant of parser errors .. will revert to default syntax highlighting if it cannot parse the code. ","3":"made more tolerant of parser errors .. will revert to default syntax highlighting if it cannot parse the code. ","package":"vim-js-context-coloring-0-0-3.zip","4":"vim-js-context-coloring-0-0-3.zip","src_id":"20974","5":"20974","creation_date":"1383020685","6":"1383020685"},{"0":"4748","vim_version":"7.0","1":"7.0","script_version":"0.0.2","2":"0.0.2","version_comment":"added comment color config options","3":"added comment color config options","package":"vim-js-context-coloring-master.zip","4":"vim-js-context-coloring-master.zip","src_id":"20936","5":"20936","creation_date":"1382190277","6":"1382190277"},{"0":"4748","vim_version":"7.0","1":"7.0","script_version":"0.0.1","2":"0.0.1","version_comment":"Initial upload","3":"Initial upload","package":"vim-js-context-coloring-master.zip","4":"vim-js-context-coloring-master.zip","src_id":"20927","5":"20927","creation_date":"1382057434","6":"1382057434"}]},"4747":{"script_id":"4747","0":"4747","script_name":"felipec","1":"felipec","script_type":"color scheme","2":"color scheme","summary":"FelipeC's colorscheme","3":"FelipeC's colorscheme","description":"My own personal colorscheme I've been tuning for several years.","4":"My own personal colorscheme I've been tuning for several years.","install_details":"","5":"","first_name":"Felipe","6":"Felipe","last_name":"Contreras","7":"Contreras","releases":[{"0":"4747","vim_version":"7.0","1":"7.0","script_version":"3.0","2":"3.0","version_comment":"Colors adjusted to reduce contrast similar to other popular colorschemes.","3":"Colors adjusted to reduce contrast similar to other popular colorschemes.","package":"felipec.vim","4":"felipec.vim","src_id":"27886","5":"27886","creation_date":"1641311348","6":"1641311348"},{"0":"4747","vim_version":"7.0","1":"7.0","script_version":"2.0","2":"2.0","version_comment":"Complete revamp using a template and a generator.","3":"Complete revamp using a template and a generator.","package":"felipec.vim","4":"felipec.vim","src_id":"27343","5":"27343","creation_date":"1603271252","6":"1603271252"},{"0":"4747","vim_version":"7.4","1":"7.4","script_version":"1.1","2":"1.1","version_comment":"Update color format.","3":"Update color format.","package":"felipec.vim","4":"felipec.vim","src_id":"24234","5":"24234","creation_date":"1462502639","6":"1462502639"},{"0":"4747","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"felipec.vim","4":"felipec.vim","src_id":"20918","5":"20918","creation_date":"1381649237","6":"1381649237"}]},"4746":{"script_id":"4746","0":"4746","script_name":"tocterm2","1":"tocterm2","script_type":"utility","2":"utility","summary":"This script converts the guifg\/guibg parameters of a colorscheme to cterm.","3":"This script converts the guifg\/guibg parameters of a colorscheme to cterm.","description":"This script converts the guifg\/guibg parameters of a colorscheme the\r\nequivalent cterm ones for 256-color terminals.\r\n\r\nIt's a rewrite from Shawn Biddle's script that uses PHP:\r\nhttp:\/\/shawnbiddle.com\/toCterm","4":"This script converts the guifg\/guibg parameters of a colorscheme the\r\nequivalent cterm ones for 256-color terminals.\r\n\r\nIt's a rewrite from Shawn Biddle's script that uses PHP:\r\nhttp:\/\/shawnbiddle.com\/toCterm","install_details":"Simply run :source <path_to_this_script>.vim","5":"Simply run :source <path_to_this_script>.vim","first_name":"Felipe","6":"Felipe","last_name":"Contreras","7":"Contreras","releases":[{"0":"4746","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"tocterm.vim","4":"tocterm.vim","src_id":"20917","5":"20917","creation_date":"1381646296","6":"1381646296"}]},"4745":{"script_id":"4745","0":"4745","script_name":"unkiwii color scheme","1":"unkiwii color scheme","script_type":"color scheme","2":"color scheme","summary":"a dark high contrast theme","3":"a dark high contrast theme","description":"Preview: (in C language) https:\/\/dl.dropboxusercontent.com\/u\/2283327\/unkiwii.png\r\n\r\nHere you can have the last version always: https:\/\/github.com\/unkiwii\/dotfiles\/unkiwii.vim","4":"Preview: (in C language) https:\/\/dl.dropboxusercontent.com\/u\/2283327\/unkiwii.png\r\n\r\nHere you can have the last version always: https:\/\/github.com\/unkiwii\/dotfiles\/unkiwii.vim","install_details":"Copy the file to $VIMRUNTIME\/colors folder","5":"Copy the file to $VIMRUNTIME\/colors folder","first_name":"Lucas Gabriel","6":"Lucas Gabriel","last_name":"S\u00c3\u00a1nchez","7":"S\u00c3\u00a1nchez","releases":[{"0":"4745","vim_version":"7.0","1":"7.0","script_version":"0.4","2":"0.4","version_comment":"Add a function to set colors to both gui a cterm","3":"Add a function to set colors to both gui a cterm","package":"unkiwii.vim","4":"unkiwii.vim","src_id":"21241","5":"21241","creation_date":"1388076343","6":"1388076343"},{"0":"4745","vim_version":"7.3","1":"7.3","script_version":"0.3","2":"0.3","version_comment":"fix some colors for the gui, add tabs configuration, remove html groups, change normal and folds configuration.","3":"fix some colors for the gui, add tabs configuration, remove html groups, change normal and folds configuration.","package":"unkiwii.vim","4":"unkiwii.vim","src_id":"20955","5":"20955","creation_date":"1382723701","6":"1382723701"}]},"4744":{"script_id":"4744","0":"4744","script_name":"unbundle.vim","1":"unbundle.vim","script_type":"utility","2":"utility","summary":"A filetype lazy, disjoint folder Vim script loader!","3":"A filetype lazy, disjoint folder Vim script loader!","description":"Unbundle activates Vim scripts from isolated directories by adding them to\r\nVim's runtimepath and building missing helptags for documentation therein.\r\n\r\nIt's like vimscript #2332 but with filetype-specific bundles and less code.\r\n\r\nSee https:\/\/github.com\/sunaku\/vim-unbundle#readme for more information.","4":"Unbundle activates Vim scripts from isolated directories by adding them to\r\nVim's runtimepath and building missing helptags for documentation therein.\r\n\r\nIt's like vimscript #2332 but with filetype-specific bundles and less code.\r\n\r\nSee https:\/\/github.com\/sunaku\/vim-unbundle#readme for more information.","install_details":"See https:\/\/github.com\/sunaku\/vim-unbundle#installation for instructions.","5":"See https:\/\/github.com\/sunaku\/vim-unbundle#installation for instructions.","first_name":"Suraj","6":"Suraj","last_name":"Kurapati","7":"Kurapati","releases":[{"0":"4744","vim_version":"7.0","1":"7.0","script_version":"1.1.0","2":"1.1.0","version_comment":"2015-04-09 make bundle\/ and ftbundle\/ locations configurable\r\n2015-04-14 allow this plugin to be loaded during vim startup\r\n2015-04-22 allow configuring bundles before they are loaded\r\n2015-05-15 avoid unnecessary work if there are no new bundles\r\n2015-05-16 allow this plugin to be stored as a bundle\/ itself\r\n2015-06-01 only Unftbundle on the very first FileType trigger","3":"2015-04-09 make bundle\/ and ftbundle\/ locations configurable\r\n2015-04-14 allow this plugin to be loaded during vim startup\r\n2015-04-22 allow configuring bundles before they are loaded\r\n2015-05-15 avoid unnecessary work if there are no new bundles\r\n2015-05-16 allow this plugin to be stored as a bundle\/ itself\r\n2015-06-01 only Unftbundle on the very first FileType trigger","package":"vim-unbundle.zip","4":"vim-unbundle.zip","src_id":"23376","5":"23376","creation_date":"1433958196","6":"1433958196"},{"0":"4744","vim_version":"7.0","1":"7.0","script_version":"1.0.0","2":"1.0.0","version_comment":"Initial upload","3":"Initial upload","package":"vim-unbundle.zip","4":"vim-unbundle.zip","src_id":"20900","5":"20900","creation_date":"1381257742","6":"1381257742"}]},"4743":{"script_id":"4743","0":"4743","script_name":"systemverilog.vim","1":"systemverilog.vim","script_type":"indent","2":"indent","summary":"Indent & syntax script for Verilog and SystemVerilog","3":"Indent & syntax script for Verilog and SystemVerilog","description":"Latest version 1.12 - download from GitHub\r\n\r\nThis script is maintained on github at:\r\nhttps:\/\/github.com\/nachumk\/systemverilog.vim","4":"Latest version 1.12 - download from GitHub\r\n\r\nThis script is maintained on github at:\r\nhttps:\/\/github.com\/nachumk\/systemverilog.vim","install_details":"VIM 8 Install:\r\n\r\nInstall by cloning repository:\r\n\r\ngit clone git:\/\/github.com\/nachumk\/systemverilog.vim ~\/.vim\/pack\/systemverilog.vim\r\n\r\nVIM 7 Install:\r\n\r\nVIM 7 doesn't have a native package management system. Using pathogen is recommended.\r\n\r\nPathogen Install (will enable VIM 8's directory structure of 'pack' instead of 'bundle' in VIM 7 - make sure Pathogen is updated as well)\r\n\r\nhttps:\/\/github.com\/tpope\/vim-pathogen\r\n\r\nInstall by cloning repository:\r\n\r\ngit clone git:\/\/github.com\/nachumk\/systemverilog.vim ~\/.vim\/pack\/systemverilog.vim\r\n\r\nMy .vimrc:\r\n\r\n\"Enable matchit\r\nruntime macros\/matchit.vim\r\nif v:version < 800\r\n    \"Start pathogen\r\n    execute pathogen#infect()\r\nendif\r\n\"Turn on syntax highlighting\r\nsyntax on\r\n\"Enable filetype detection\r\nfiletype plugin indent on\r\n\"Enable folding based on indent (on 8.0 and greater versions)\r\nif v:version >= 800\r\n    set foldmethod=indent\r\n    set foldnestmax=10\r\n    set nofoldenable\r\n    set foldlevelstart=10\r\nendif","5":"VIM 8 Install:\r\n\r\nInstall by cloning repository:\r\n\r\ngit clone git:\/\/github.com\/nachumk\/systemverilog.vim ~\/.vim\/pack\/systemverilog.vim\r\n\r\nVIM 7 Install:\r\n\r\nVIM 7 doesn't have a native package management system. Using pathogen is recommended.\r\n\r\nPathogen Install (will enable VIM 8's directory structure of 'pack' instead of 'bundle' in VIM 7 - make sure Pathogen is updated as well)\r\n\r\nhttps:\/\/github.com\/tpope\/vim-pathogen\r\n\r\nInstall by cloning repository:\r\n\r\ngit clone git:\/\/github.com\/nachumk\/systemverilog.vim ~\/.vim\/pack\/systemverilog.vim\r\n\r\nMy .vimrc:\r\n\r\n\"Enable matchit\r\nruntime macros\/matchit.vim\r\nif v:version < 800\r\n    \"Start pathogen\r\n    execute pathogen#infect()\r\nendif\r\n\"Turn on syntax highlighting\r\nsyntax on\r\n\"Enable filetype detection\r\nfiletype plugin indent on\r\n\"Enable folding based on indent (on 8.0 and greater versions)\r\nif v:version >= 800\r\n    set foldmethod=indent\r\n    set foldnestmax=10\r\n    set nofoldenable\r\n    set foldlevelstart=10\r\nendif","first_name":"Nachum","6":"Nachum","last_name":"Kanovsky","7":"Kanovsky","releases":[{"0":"4743","vim_version":"7.0","1":"7.0","script_version":"1.12","2":"1.12","version_comment":"Update to VIM 8\\\\\\'s package management system (also compatible with the latest Pathogen if using VIM 7)","3":"Update to VIM 8\\\\\\'s package management system (also compatible with the latest Pathogen if using VIM 7)","package":"systemverilog.vim-1.12.tar.gz","4":"systemverilog.vim-1.12.tar.gz","src_id":"27684","5":"27684","creation_date":"1627604650","6":"1627604650"},{"0":"4743","vim_version":"7.0","1":"7.0","script_version":"1.11.3","2":"1.11.3","version_comment":"Fix matchit with `ifdef and else fixes","3":"Fix matchit with `ifdef and else fixes","package":"systemverilog.vim-1.11.3.tar.gz","4":"systemverilog.vim-1.11.3.tar.gz","src_id":"27683","5":"27683","creation_date":"1627552742","6":"1627552742"},{"0":"4743","vim_version":"7.0","1":"7.0","script_version":"1.11.2","2":"1.11.2","version_comment":"Improve string conversion to handle escaped quotes.","3":"Improve string conversion to handle escaped quotes.","package":"systemverilog.vim-1.11.2.tar.gz","4":"systemverilog.vim-1.11.2.tar.gz","src_id":"27682","5":"27682","creation_date":"1627546484","6":"1627546484"},{"0":"4743","vim_version":"7.0","1":"7.0","script_version":"1.11.1","2":"1.11.1","version_comment":"Fix greedy string conversion.","3":"Fix greedy string conversion.","package":"systemverilog.vim-1.11.1.tar.gz","4":"systemverilog.vim-1.11.1.tar.gz","src_id":"27681","5":"27681","creation_date":"1627544619","6":"1627544619"},{"0":"4743","vim_version":"7.0","1":"7.0","script_version":"1.11","2":"1.11","version_comment":"Add missing keywords, and improve overall indenting","3":"Add missing keywords, and improve overall indenting","package":"systemverilog.vim-1.11.tar.gz","4":"systemverilog.vim-1.11.tar.gz","src_id":"27680","5":"27680","creation_date":"1627537961","6":"1627537961"},{"0":"4743","vim_version":"7.0","1":"7.0","script_version":"1.9","2":"1.9","version_comment":"Latest from GitHub","3":"Latest from GitHub","package":"systemverilog.vim-master.zip","4":"systemverilog.vim-master.zip","src_id":"27599","5":"27599","creation_date":"1620947919","6":"1620947919"},{"0":"4743","vim_version":"7.0","1":"7.0","script_version":"1.9","2":"1.9","version_comment":"Fix indent for SVA properties.\r\nImprove syntax support.","3":"Fix indent for SVA properties.\r\nImprove syntax support.","package":"systemverilog.vim-master.zip","4":"systemverilog.vim-master.zip","src_id":"26848","5":"26848","creation_date":"1574396041","6":"1574396041"},{"0":"4743","vim_version":"7.0","1":"7.0","script_version":"1.7","2":"1.7","version_comment":"Comments handled properly - see GitHub for details.","3":"Comments handled properly - see GitHub for details.","package":"systemverilog.1.7.zip","4":"systemverilog.1.7.zip","src_id":"25905","5":"25905","creation_date":"1522253657","6":"1522253657"},{"0":"4743","vim_version":"7.2","1":"7.2","script_version":"1.5","2":"1.5","version_comment":"Fix matchit support - thank you Felipe Gon\u00c3\u00a7alves Assis\r\nFix number highlighting","3":"Fix matchit support - thank you Felipe Gon\u00c3\u00a7alves Assis\r\nFix number highlighting","package":"systemverilog.vim-1.5.tar.gz","4":"systemverilog.vim-1.5.tar.gz","src_id":"25029","5":"25029","creation_date":"1489294351","6":"1489294351"},{"0":"4743","vim_version":"7.0","1":"7.0","script_version":"1.3","2":"1.3","version_comment":"Ignores keywords in single line strings. Eg: If a string contained the word 'end' it would mis-indent.","3":"Ignores keywords in single line strings. Eg: If a string contained the word 'end' it would mis-indent.","package":"systemverilog.1.3.tar.gz","4":"systemverilog.1.3.tar.gz","src_id":"21399","5":"21399","creation_date":"1391022259","6":"1391022259"},{"0":"4743","vim_version":"7.0","1":"7.0","script_version":"1.2","2":"1.2","version_comment":"Added in 'z' and 'x' for number highlighting.\r\nAdded in missing operators for highlighting - Thanks to Eugene Mikhantiev.","3":"Added in 'z' and 'x' for number highlighting.\r\nAdded in missing operators for highlighting - Thanks to Eugene Mikhantiev.","package":"systemverilog.1.2.tar.gz","4":"systemverilog.1.2.tar.gz","src_id":"21396","5":"21396","creation_date":"1390980201","6":"1390980201"},{"0":"4743","vim_version":"7.0","1":"7.0","script_version":"1.1","2":"1.1","version_comment":"Improved case statement highlighting.\r\neg: label1, label2, label3: ...\r\nwill now highlight properly.","3":"Improved case statement highlighting.\r\neg: label1, label2, label3: ...\r\nwill now highlight properly.","package":"systemverilog.1.1.tar.gz","4":"systemverilog.1.1.tar.gz","src_id":"21340","5":"21340","creation_date":"1389997512","6":"1389997512"},{"0":"4743","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Fixed incorrect highlighting of numbers and times.","3":"Fixed incorrect highlighting of numbers and times.","package":"systemverilog.1.0.tar.gz","4":"systemverilog.1.0.tar.gz","src_id":"21039","5":"21039","creation_date":"1384366794","6":"1384366794"},{"0":"4743","vim_version":"7.0","1":"7.0","script_version":"0.9","2":"0.9","version_comment":"Fixed syntax highlighting for case and possibly other keywords messed up by the existence of svIdentifier.","3":"Fixed syntax highlighting for case and possibly other keywords messed up by the existence of svIdentifier.","package":"systemverilog.0.9.tar.gz","4":"systemverilog.0.9.tar.gz","src_id":"21031","5":"21031","creation_date":"1384284831","6":"1384284831"},{"0":"4743","vim_version":"7.0","1":"7.0","script_version":"0.8","2":"0.8","version_comment":"Fixed assume property indent.","3":"Fixed assume property indent.","package":"systemverilog.0.8.tar.gz","4":"systemverilog.0.8.tar.gz","src_id":"20957","5":"20957","creation_date":"1382742848","6":"1382742848"},{"0":"4743","vim_version":"7.0","1":"7.0","script_version":"0.7","2":"0.7","version_comment":"Fixed issue with assert and cover property statements causing indent.","3":"Fixed issue with assert and cover property statements causing indent.","package":"systemverilog.0.7.tar.gz","4":"systemverilog.0.7.tar.gz","src_id":"20956","5":"20956","creation_date":"1382727798","6":"1382727798"},{"0":"4743","vim_version":"7.0","1":"7.0","script_version":"0.6","2":"0.6","version_comment":"Added a bunch of additional keywords to syntax script. Supports property, sequence, covergroup, etc...","3":"Added a bunch of additional keywords to syntax script. Supports property, sequence, covergroup, etc...","package":"systemverilog.0.6.tar.gz","4":"systemverilog.0.6.tar.gz","src_id":"20952","5":"20952","creation_date":"1382677749","6":"1382677749"},{"0":"4743","vim_version":"7.0","1":"7.0","script_version":"0.5","2":"0.5","version_comment":"Added in syntax highlighting\r\nIndent with ( as well\r\nAdded in headers","3":"Added in syntax highlighting\r\nIndent with ( as well\r\nAdded in headers","package":"systemverilog.0.5.tar.gz","4":"systemverilog.0.5.tar.gz","src_id":"20949","5":"20949","creation_date":"1382590817","6":"1382590817"},{"0":"4743","vim_version":"7.0","1":"7.0","script_version":"0.4","2":"0.4","version_comment":"oops, forgot to uncomment finish lines in load checks","3":"oops, forgot to uncomment finish lines in load checks","package":"systemverilog.0.4.tar.gz","4":"systemverilog.0.4.tar.gz","src_id":"20896","5":"20896","creation_date":"1381127948","6":"1381127948"},{"0":"4743","vim_version":"7.0","1":"7.0","script_version":"0.3","2":"0.3","version_comment":"Added in { and }.","3":"Added in { and }.","package":"systemverilog.0.3.tar.gz","4":"systemverilog.0.3.tar.gz","src_id":"20895","5":"20895","creation_date":"1381127415","6":"1381127415"},{"0":"4743","vim_version":"7.3","1":"7.3","script_version":"0.2","2":"0.2","version_comment":"Added support for pure functions.","3":"Added support for pure functions.","package":"systemverilog.0.2.tar.gz","4":"systemverilog.0.2.tar.gz","src_id":"20894","5":"20894","creation_date":"1381124266","6":"1381124266"},{"0":"4743","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"systemverilog.tar.gz","4":"systemverilog.tar.gz","src_id":"20892","5":"20892","creation_date":"1381115580","6":"1381115580"}]},"4742":{"script_id":"4742","0":"4742","script_name":"columcille.vim","1":"columcille.vim","script_type":"utility","2":"utility","summary":"split window management","3":"split window management","description":"This plugin provides commands for setting the number of open top-level vertical windows or horizontal split windows (in a vertical split window or just in the main window).","4":"This plugin provides commands for setting the number of open top-level vertical windows or horizontal split windows (in a vertical split window or just in the main window).","install_details":"I recommend installation via Vundle: https:\/\/github.com\/gmarik\/vundle\r\n\r\nWith Vundle installed, add a Bundle for \"fifthposition\/columcille\", start Vim, and run Vundle\u00e2\u0080\u0099s bundle install command (as explained in its README).","5":"I recommend installation via Vundle: https:\/\/github.com\/gmarik\/vundle\r\n\r\nWith Vundle installed, add a Bundle for \"fifthposition\/columcille\", start Vim, and run Vundle\u00e2\u0080\u0099s bundle install command (as explained in its README).","first_name":"Ben","6":"Ben","last_name":"Klein","7":"Klein","releases":[{"0":"4742","vim_version":"7.0","1":"7.0","script_version":"0.0.1","2":"0.0.1","version_comment":"Initial upload","3":"Initial upload","package":"columcille.zip","4":"columcille.zip","src_id":"20883","5":"20883","creation_date":"1380921227","6":"1380921227"}]},"4741":{"script_id":"4741","0":"4741","script_name":"TextFormComplete","1":"TextFormComplete","script_type":"utility","2":"utility","summary":"Convert textual options into completion candidates.","3":"Convert textual options into completion candidates.","description":"DESCRIPTION\r\nThis plugin can transform textual options (in the form FOO|BAR, as they are\r\noften found in templates or snippets) into a printed list or insert-mode\r\ncompletion, which offer all alternatives (\"FOO\" and \"BAR\" in this example),\r\nand allow to choose one and replace the full options block with it.\r\n\r\nUSAGE\r\nq|                      List all individual alternatives in the text form\r\n                        close to the cursor and allow the user to choose one,\r\n                        which then replaces the full options block.\r\n{Visual}q|              List all individual alternatives in the selected text\r\n{Select}CTRL-X |        form and allow the user to choose one, which then\r\n                        replaces the selection.\r\n[count]q|               Replace the full options block \/ selection with the\r\n{Visual}[count]q|       [count]'th alternative from it.\r\n\r\nCTRL-X |                Convert the text form before the cursor into the\r\n                        individual alternatives and offer them for completion.\r\n\r\nSYNTAX\r\nThe text forms can be in simple and extended syntax. The simple syntax is just\r\na list of word characters (without whitespace!), delimited by | characters:\r\n    FOO|BAZ|QUUX\r\nYou can include [], (), + and |, too, but you have to escape with a backslash.\r\n\r\nThe extended syntax is bracketed by [...], and its alternatives can contain\r\nwhitespace and any other characters.\r\n    [FOO+BAR|My BAZ|The QUUX!]\r\nAdditionally, you can append an optional explanation to each alternative. This\r\nwill only be shown in the completion menu, but is not inserted into the\r\nbuffer. The explanation must be enclosed in (...) and comes after the\r\nalternative text, separated by a <Space>:\r\n    [FOO (default)|BAZ (softer)|QUUX (the special choice)]\r\n\r\nAnother form element is a slider where the active element # can be positioned\r\nanywhere on the linear measure ----- between the [...] stops.\r\n    [---#------]\r\nYou can choose among all possible positions (indicated with their percentage\r\nranges), and after that quickly adjust with CTRL-A \/ CTRL-X.","4":"DESCRIPTION\r\nThis plugin can transform textual options (in the form FOO|BAR, as they are\r\noften found in templates or snippets) into a printed list or insert-mode\r\ncompletion, which offer all alternatives (\"FOO\" and \"BAR\" in this example),\r\nand allow to choose one and replace the full options block with it.\r\n\r\nUSAGE\r\nq|                      List all individual alternatives in the text form\r\n                        close to the cursor and allow the user to choose one,\r\n                        which then replaces the full options block.\r\n{Visual}q|              List all individual alternatives in the selected text\r\n{Select}CTRL-X |        form and allow the user to choose one, which then\r\n                        replaces the selection.\r\n[count]q|               Replace the full options block \/ selection with the\r\n{Visual}[count]q|       [count]'th alternative from it.\r\n\r\nCTRL-X |                Convert the text form before the cursor into the\r\n                        individual alternatives and offer them for completion.\r\n\r\nSYNTAX\r\nThe text forms can be in simple and extended syntax. The simple syntax is just\r\na list of word characters (without whitespace!), delimited by | characters:\r\n    FOO|BAZ|QUUX\r\nYou can include [], (), + and |, too, but you have to escape with a backslash.\r\n\r\nThe extended syntax is bracketed by [...], and its alternatives can contain\r\nwhitespace and any other characters.\r\n    [FOO+BAR|My BAZ|The QUUX!]\r\nAdditionally, you can append an optional explanation to each alternative. This\r\nwill only be shown in the completion menu, but is not inserted into the\r\nbuffer. The explanation must be enclosed in (...) and comes after the\r\nalternative text, separated by a <Space>:\r\n    [FOO (default)|BAZ (softer)|QUUX (the special choice)]\r\n\r\nAnother form element is a slider where the active element # can be positioned\r\nanywhere on the linear measure ----- between the [...] stops.\r\n    [---#------]\r\nYou can choose among all possible positions (indicated with their percentage\r\nranges), and after that quickly adjust with CTRL-A \/ CTRL-X.","install_details":"INSTALLATION\r\nThis script is packaged as a vimball. If you have the \"gunzip\" decompressor\r\nin your PATH, simply edit the *.vmb.gz package in Vim; otherwise, decompress\r\nthe archive first, e.g. using WinZip. Inside Vim, install by sourcing the\r\nvimball or via the :UseVimball command.\r\n    vim TextFormComplete*.vmb.gz\r\n    :so %\r\nTo uninstall, use the :RmVimball command.\r\n\r\nDEPENDENCIES\r\n- Requires Vim 7.0 or higher.\r\n- Requires the ingo-library.vim plugin (vimscript #4433), version 1.010 or\r\n  higher.\r\n- SwapIt (vimscript #2294) plugin (optional)\r\n- repeat.vim (vimscript #2136) plugin (optional)\r\n- visualrepeat.vim (vimscript #3848) plugin (optional)\r\n\r\nCONFIGURATION\r\nFor a permanent configuration, put the following commands into your vimrc:\r\n\r\nWhen there's only a single option, the plugin allows to deselect that value.\r\nThis expression configures what the deselected value is (in i_CTRL-X_Bar,\r\nthis must not be empty to be included in the completion list). By default, a\r\nstring of \"---\" with the same length as the sole option is offered. You can\r\nchange this to e.g. a single dash via:\r\n    let g:TextFormComplete_DeselectionExpr = '\"-\"'\r\n\r\nIf you want to use different mappings, map your keys to the\r\n<Plug>(TextFormComplete) mapping targets _before_ sourcing the script (e.g.\r\nin your vimrc):\r\n    imap <C-x><Bar> <Plug>(TextFormComplete)\r\n    smap <C-x><Bar> <Plug>(TextFormComplete)\r\n    nmap q<Bar> <Plug>(TextFormComplete)\r\n    xmap q<Bar> <Plug>(TextFormComplete)\r\n\r\nINTEGRATION\r\nWhen the SwapIt plugin is installed, the completed alternatives are defined as\r\na :SwapList, so you can change your initial completed choice and move\r\nthrough all alternatives just by pressing CTRL-A \/ CTRL-X on them. (With a\r\nvisual selection, this even works for alternatives containing whitespace!)","5":"INSTALLATION\r\nThis script is packaged as a vimball. If you have the \"gunzip\" decompressor\r\nin your PATH, simply edit the *.vmb.gz package in Vim; otherwise, decompress\r\nthe archive first, e.g. using WinZip. Inside Vim, install by sourcing the\r\nvimball or via the :UseVimball command.\r\n    vim TextFormComplete*.vmb.gz\r\n    :so %\r\nTo uninstall, use the :RmVimball command.\r\n\r\nDEPENDENCIES\r\n- Requires Vim 7.0 or higher.\r\n- Requires the ingo-library.vim plugin (vimscript #4433), version 1.010 or\r\n  higher.\r\n- SwapIt (vimscript #2294) plugin (optional)\r\n- repeat.vim (vimscript #2136) plugin (optional)\r\n- visualrepeat.vim (vimscript #3848) plugin (optional)\r\n\r\nCONFIGURATION\r\nFor a permanent configuration, put the following commands into your vimrc:\r\n\r\nWhen there's only a single option, the plugin allows to deselect that value.\r\nThis expression configures what the deselected value is (in i_CTRL-X_Bar,\r\nthis must not be empty to be included in the completion list). By default, a\r\nstring of \"---\" with the same length as the sole option is offered. You can\r\nchange this to e.g. a single dash via:\r\n    let g:TextFormComplete_DeselectionExpr = '\"-\"'\r\n\r\nIf you want to use different mappings, map your keys to the\r\n<Plug>(TextFormComplete) mapping targets _before_ sourcing the script (e.g.\r\nin your vimrc):\r\n    imap <C-x><Bar> <Plug>(TextFormComplete)\r\n    smap <C-x><Bar> <Plug>(TextFormComplete)\r\n    nmap q<Bar> <Plug>(TextFormComplete)\r\n    xmap q<Bar> <Plug>(TextFormComplete)\r\n\r\nINTEGRATION\r\nWhen the SwapIt plugin is installed, the completed alternatives are defined as\r\na :SwapList, so you can change your initial completed choice and move\r\nthrough all alternatives just by pressing CTRL-A \/ CTRL-X on them. (With a\r\nvisual selection, this even works for alternatives containing whitespace!)","first_name":"Ingo","6":"Ingo","last_name":"Karkat","7":"Karkat","releases":[{"0":"4741","vim_version":"7.0","1":"7.0","script_version":"1.10","2":"1.10","version_comment":"- ENH: Add support for sliders [---#-----].\r\n- Set change marks when replacing the text form with a match from normal mode.","3":"- ENH: Add support for sliders [---#-----].\r\n- Set change marks when replacing the text form with a match from normal mode.","package":"TextFormComplete-1.10.vmb.gz","4":"TextFormComplete-1.10.vmb.gz","src_id":"21325","5":"21325","creation_date":"1389817687","6":"1389817687"},{"0":"4741","vim_version":"7.0","1":"7.0","script_version":"1.00","2":"1.00","version_comment":"Initial upload","3":"Initial upload","package":"TextFormComplete-1.00.vmb.gz","4":"TextFormComplete-1.00.vmb.gz","src_id":"20882","5":"20882","creation_date":"1380913476","6":"1380913476"}]},"4740":{"script_id":"4740","0":"4740","script_name":"vim-toplevel","1":"vim-toplevel","script_type":"utility","2":"utility","summary":"Quickly change to a root directory.","3":"Quickly change to a root directory.","description":"For an always updated description see:\r\n\r\nhttps:\/\/github.com\/mhinz\/vim-toplevel\r\n\r\nThanks!","4":"For an always updated description see:\r\n\r\nhttps:\/\/github.com\/mhinz\/vim-toplevel\r\n\r\nThanks!","install_details":"If you have no preferred installation method, I suggest using tpope's pathogen. Afterwards installing vim-toplevel is as easy as pie:\r\n\r\n$ git clone https:\/\/github.com\/mhinz\/vim-toplevel ~\/.vim\/bundle\/vim-toplevel\r\n\r\nIt works without any configuration, but you might want to look into the documentation for further customization:\r\n\r\n:Helptags  \" rebuilding tags files\r\n:h toplevel","5":"If you have no preferred installation method, I suggest using tpope's pathogen. Afterwards installing vim-toplevel is as easy as pie:\r\n\r\n$ git clone https:\/\/github.com\/mhinz\/vim-toplevel ~\/.vim\/bundle\/vim-toplevel\r\n\r\nIt works without any configuration, but you might want to look into the documentation for further customization:\r\n\r\n:Helptags  \" rebuilding tags files\r\n:h toplevel","first_name":"Marco","6":"Marco","last_name":"Hinz","7":"Hinz","releases":[{"0":"4740","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"vim-toplevel-1.0.tar.gz","4":"vim-toplevel-1.0.tar.gz","src_id":"20881","5":"20881","creation_date":"1380892307","6":"1380892307"}]},"4739":{"script_id":"4739","0":"4739","script_name":"extline","1":"extline","script_type":"utility","2":"utility","summary":"Plugin for extending lines (e.g., underlined titles)","3":"Plugin for extending lines (e.g., underlined titles)","description":"When writing titles in a plain text document, a common convention is to use\r\nrepeated punctuation characters to draw lines under (and sometimes over) the\r\ntitle text.  This plugin helps maintain those title lines more easily, and\r\nit provides support for standalone horizontal lines as well.\r\n\r\nTitles are marked up in a manner compatible with reStructuredText[1], and the\r\nvarious heading levels are chosen to coincide with the Sphinx[2] project's\r\nconventions as follows::\r\n\r\n    ##############\r\n    Part (level 9)\r\n    ##############\r\n\r\n    *****************\r\n    Chapter (level 0)\r\n    *****************\r\n\r\n    Section (level 1)\r\n    =================\r\n\r\n    Subsection (level 2)\r\n    --------------------\r\n\r\n    Subsubsection (level 3)\r\n    ^^^^^^^^^^^^^^^^^^^^^^^\r\n\r\n    Paragraph (level 4)\r\n    \"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\r\n\r\n    Level-5 heading\r\n    '''''''''''''''\r\n\r\nExtline provides methods for adding these lines, adjusting them to fit as the\r\nsection names changes, and for converting one level to another.\r\n\r\n[1]: http:\/\/docutils.sourceforge.net\/rst.html\r\n[2]: http:\/\/sphinx-doc.org\/\r\n\r\nSee documentation in doc\/extline.txt for installation, customization, and\r\nusage instructions.\r\n\r\nDeveloped by Michael Henry (vim at drmikehenry.com).\r\n\r\nDistributed under Vim's license.\r\n\r\nGit repository:   https:\/\/github.com\/drmikehenry\/vim-extline\r\n","4":"When writing titles in a plain text document, a common convention is to use\r\nrepeated punctuation characters to draw lines under (and sometimes over) the\r\ntitle text.  This plugin helps maintain those title lines more easily, and\r\nit provides support for standalone horizontal lines as well.\r\n\r\nTitles are marked up in a manner compatible with reStructuredText[1], and the\r\nvarious heading levels are chosen to coincide with the Sphinx[2] project's\r\nconventions as follows::\r\n\r\n    ##############\r\n    Part (level 9)\r\n    ##############\r\n\r\n    *****************\r\n    Chapter (level 0)\r\n    *****************\r\n\r\n    Section (level 1)\r\n    =================\r\n\r\n    Subsection (level 2)\r\n    --------------------\r\n\r\n    Subsubsection (level 3)\r\n    ^^^^^^^^^^^^^^^^^^^^^^^\r\n\r\n    Paragraph (level 4)\r\n    \"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\r\n\r\n    Level-5 heading\r\n    '''''''''''''''\r\n\r\nExtline provides methods for adding these lines, adjusting them to fit as the\r\nsection names changes, and for converting one level to another.\r\n\r\n[1]: http:\/\/docutils.sourceforge.net\/rst.html\r\n[2]: http:\/\/sphinx-doc.org\/\r\n\r\nSee documentation in doc\/extline.txt for installation, customization, and\r\nusage instructions.\r\n\r\nDeveloped by Michael Henry (vim at drmikehenry.com).\r\n\r\nDistributed under Vim's license.\r\n\r\nGit repository:   https:\/\/github.com\/drmikehenry\/vim-extline\r\n","install_details":"","5":"","first_name":"Michael","6":"Michael","last_name":"Henry","7":"Henry","releases":[{"0":"4739","vim_version":"7.0","1":"7.0","script_version":"0.2.1","2":"0.2.1","version_comment":"- Fix line length for titles with multi-byte characters.  The previously used\r\n  `len(title)` returned the size in bytes rather than logical characters,\r\n  causing overly long line lengths for multi-byte characters.\r\n\r\n- Allow multi-byte characters for \"horizontal line update\".\r\n","3":"- Fix line length for titles with multi-byte characters.  The previously used\r\n  `len(title)` returned the size in bytes rather than logical characters,\r\n  causing overly long line lengths for multi-byte characters.\r\n\r\n- Allow multi-byte characters for \"horizontal line update\".\r\n","package":"extline-0.2.1.zip","4":"extline-0.2.1.zip","src_id":"28456","5":"28456","creation_date":"1683430872","6":"1683430872"},{"0":"4739","vim_version":"7.0","1":"7.0","script_version":"0.2.0","2":"0.2.0","version_comment":"Initial upload","3":"Initial upload","package":"extline-0.2.0.zip","4":"extline-0.2.0.zip","src_id":"20879","5":"20879","creation_date":"1380824144","6":"1380824144"}]},"4738":{"script_id":"4738","0":"4738","script_name":"vim-isort","1":"vim-isort","script_type":"utility","2":"utility","summary":"sort python imports using the isort lib","3":"sort python imports using the isort lib","description":"Plugin to sort python imports using the isort lib.\r\n\r\nUsage:\r\nJust call the :Isort command, and it will reorder the imports of the current python file.\r\nYou can also configure isort options, check them on the isort docs.\r\n\r\nOfficial repo:\r\nhttps:\/\/github.com\/fisadev\/vim-isort","4":"Plugin to sort python imports using the isort lib.\r\n\r\nUsage:\r\nJust call the :Isort command, and it will reorder the imports of the current python file.\r\nYou can also configure isort options, check them on the isort docs.\r\n\r\nOfficial repo:\r\nhttps:\/\/github.com\/fisadev\/vim-isort","install_details":"Recommended installation method is to use a plugin manager, like Vundle or Pathogen (pointing to the oficial repo). But you could manually extract the files from this plugin in your .vim folder. \r\nYou will need a vim compiled with python support, and this dependency installed on your system:\r\n\r\nsudo pip install isort","5":"Recommended installation method is to use a plugin manager, like Vundle or Pathogen (pointing to the oficial repo). But you could manually extract the files from this plugin in your .vim folder. \r\nYou will need a vim compiled with python support, and this dependency installed on your system:\r\n\r\nsudo pip install isort","first_name":"Juan Pedro","6":"Juan Pedro","last_name":"Fisanotti","7":"Fisanotti","releases":[{"0":"4738","vim_version":"7.0","1":"7.0","script_version":"87dc4","2":"87dc4","version_comment":"-  Fixed problem with empty lines being added at the end of the file","3":"-  Fixed problem with empty lines being added at the end of the file","package":"vim-isort.tar.gz","4":"vim-isort.tar.gz","src_id":"24402","5":"24402","creation_date":"1469508301","6":"1469508301"},{"0":"4738","vim_version":"7.0","1":"7.0","script_version":"27a890","2":"27a890","version_comment":"- Doc change\r\n- Fixed crash when no isort module installed (now it just warns the user)","3":"- Doc change\r\n- Fixed crash when no isort module installed (now it just warns the user)","package":"vim-isort.tar.gz","4":"vim-isort.tar.gz","src_id":"23719","5":"23719","creation_date":"1446947705","6":"1446947705"},{"0":"4738","vim_version":"7.0","1":"7.0","script_version":"561c6c","2":"561c6c","version_comment":"Small fix to add compatibility with older versions of vim's python interpreter.","3":"Small fix to add compatibility with older versions of vim's python interpreter.","package":"vim-isort.tar.gz","4":"vim-isort.tar.gz","src_id":"22840","5":"22840","creation_date":"1422377459","6":"1422377459"},{"0":"4738","vim_version":"7.0","1":"7.0","script_version":"f9fe7c","2":"f9fe7c","version_comment":"- Removed python files, they are now dependencies\r\n- Fixed issue with empty lines at the end of files\r\n- Added python3 compatibility, for people with vim compiled with +python3 and without +python","3":"- Removed python files, they are now dependencies\r\n- Fixed issue with empty lines at the end of files\r\n- Added python3 compatibility, for people with vim compiled with +python3 and without +python","package":"vim-isort.tar.gz","4":"vim-isort.tar.gz","src_id":"21409","5":"21409","creation_date":"1391146044","6":"1391146044"},{"0":"4738","vim_version":"7.0","1":"7.0","script_version":"de4e83","2":"de4e83","version_comment":"added visual mode sorting, configurable mappings, and removed the pip dependencies","3":"added visual mode sorting, configurable mappings, and removed the pip dependencies","package":"vim-isort.tar.gz","4":"vim-isort.tar.gz","src_id":"21068","5":"21068","creation_date":"1384905889","6":"1384905889"},{"0":"4738","vim_version":"7.0","1":"7.0","script_version":"cc07c9","2":"cc07c9","version_comment":"Initial upload","3":"Initial upload","package":"vim-isort.tar.gz","4":"vim-isort.tar.gz","src_id":"20872","5":"20872","creation_date":"1380758518","6":"1380758518"}]},"4737":{"script_id":"4737","0":"4737","script_name":"ctrlp-cmdpalette","1":"ctrlp-cmdpalette","script_type":"utility","2":"utility","summary":"ctrlp extension to search and execute vim commands","3":"ctrlp extension to search and execute vim commands","description":"This is an extension for the awesome vim CtrlP plugin.\r\n\r\nThis extension adds a new CtrlP command, the :CtrlPCmdPalette, which allows you to find and run vim commands (internal or custom).\r\n\r\nOficial repo:\r\nhttps:\/\/github.com\/fisadev\/vim-ctrlp-cmdpalette","4":"This is an extension for the awesome vim CtrlP plugin.\r\n\r\nThis extension adds a new CtrlP command, the :CtrlPCmdPalette, which allows you to find and run vim commands (internal or custom).\r\n\r\nOficial repo:\r\nhttps:\/\/github.com\/fisadev\/vim-ctrlp-cmdpalette","install_details":"Recommended installation method is to use a plugin manager, like Vundle or Pathogen (pointing to the oficial repo). But you could manually install CtrlP and then extract the files from this plugin in your .vim folder.\r\nYou will need a vim compiled with python support.","5":"Recommended installation method is to use a plugin manager, like Vundle or Pathogen (pointing to the oficial repo). But you could manually install CtrlP and then extract the files from this plugin in your .vim folder.\r\nYou will need a vim compiled with python support.","first_name":"Juan Pedro","6":"Juan Pedro","last_name":"Fisanotti","7":"Fisanotti","releases":[{"0":"4737","vim_version":"7.0","1":"7.0","script_version":"a2ec83","2":"a2ec83","version_comment":"Initial upload","3":"Initial upload","package":"ctrlp-cmdpalette.tar.gz","4":"ctrlp-cmdpalette.tar.gz","src_id":"20871","5":"20871","creation_date":"1380758084","6":"1380758084"}]},"4736":{"script_id":"4736","0":"4736","script_name":"navigate-softtab","1":"navigate-softtab","script_type":"utility","2":"utility","summary":"simulates tab cursor movement over leading space in normal mode","3":"simulates tab cursor movement over leading space in normal mode","description":"Makes Vim navigate leading spaces like tabs.\r\nThis is only active if softtabstop is set:\r\nset softtabstop=4   \" Sets the number of columns for a TAB\r\nSupports BS and Space in normal mode.\r\nsource @ https:\/\/github.com\/lampert\/vim\r\n\r\n","4":"Makes Vim navigate leading spaces like tabs.\r\nThis is only active if softtabstop is set:\r\nset softtabstop=4   \" Sets the number of columns for a TAB\r\nSupports BS and Space in normal mode.\r\nsource @ https:\/\/github.com\/lampert\/vim\r\n\r\n","install_details":"Put the .vim file to ~\/.vim\/plugin","5":"Put the .vim file to ~\/.vim\/plugin","first_name":"Paul","6":"Paul","last_name":"Lampert","7":"Lampert","releases":[{"0":"4736","vim_version":"7.0","1":"7.0","script_version":"1.2","2":"1.2","version_comment":"Fix line wrap bug","3":"Fix line wrap bug","package":"navigate-softtab.vim","4":"navigate-softtab.vim","src_id":"20941","5":"20941","creation_date":"1382384851","6":"1382384851"},{"0":"4736","vim_version":"7.0","1":"7.0","script_version":"1.1","2":"1.1","version_comment":"stopped mapping x and X since '.' breaks","3":"stopped mapping x and X since '.' breaks","package":"navigate-softtab.vim","4":"navigate-softtab.vim","src_id":"20902","5":"20902","creation_date":"1381352162","6":"1381352162"},{"0":"4736","vim_version":"7.0","1":"7.0","script_version":"1","2":"1","version_comment":"Initial upload","3":"Initial upload","package":"navigate-softtab.vim","4":"navigate-softtab.vim","src_id":"20868","5":"20868","creation_date":"1380744637","6":"1380744637"}]},"4735":{"script_id":"4735","0":"4735","script_name":"accordion","1":"accordion","script_type":"utility","2":"utility","summary":"A window manager for people who love vsplits","3":"A window manager for people who love vsplits","description":"Accordion lets you specify a maximum number of vsplits. Extra splits are collapsed to be 1 column wide so that the ones in the current viewport are more readable. When you are on the edge of the viewport and switch windows to one of the collapsed windows, the viewport slides over.\r\n\r\nThere's also a diff mode that sets the viewport to be two windows wide and diffs the two visible windows against each other.\r\n\r\nPlease refer to the github repo for example gifs, issues, and more frequent updates: https:\/\/github.com\/mattboehm\/vim-accordion\/","4":"Accordion lets you specify a maximum number of vsplits. Extra splits are collapsed to be 1 column wide so that the ones in the current viewport are more readable. When you are on the edge of the viewport and switch windows to one of the collapsed windows, the viewport slides over.\r\n\r\nThere's also a diff mode that sets the viewport to be two windows wide and diffs the two visible windows against each other.\r\n\r\nPlease refer to the github repo for example gifs, issues, and more frequent updates: https:\/\/github.com\/mattboehm\/vim-accordion\/","install_details":"Unzip into your ~\/.vim or use Pathogen\/Vundle\/etc. \r\n\r\nDon't forget to run :helptags to load the documentation.","5":"Unzip into your ~\/.vim or use Pathogen\/Vundle\/etc. \r\n\r\nDon't forget to run :helptags to load the documentation.","first_name":"Matthew","6":"Matthew","last_name":"Boehm","7":"Boehm","releases":[{"0":"4735","vim_version":"7.0","1":"7.0","script_version":"0.3.0","2":"0.3.0","version_comment":"Initial upload","3":"Initial upload","package":"vim-accordion-master.zip","4":"vim-accordion-master.zip","src_id":"20865","5":"20865","creation_date":"1380651226","6":"1380651226"}]},"4734":{"script_id":"4734","0":"4734","script_name":"united-front","1":"united-front","script_type":"utility","2":"utility","summary":"Autoshare yank registers across vim instances.","3":"Autoshare yank registers across vim instances.","description":"This plugin will automatically share the registers of any and\/or all vim instances.\r\n\r\n\"Buffer separately, but yank together!\"\r\n -- Leon Robotsky\r\n\r\nAll vim instances that you want to share registers need to be started in server mode.\r\nGVim does this automatically, but terminal vim must be told to do this.\r\n\r\n    vim --servername whateveryouwant\r\n\r\nIf you alias the vim command to always use a server, everything will be automatic and you can spend more time editing with your awesome new shared registers.\r\n\r\n    alias vim=\"vim --servername robotsky\"\r\n\r\nSee http:\/\/github.com\/ardagnir\/united-front for most up-to-date version.\r\n","4":"This plugin will automatically share the registers of any and\/or all vim instances.\r\n\r\n\"Buffer separately, but yank together!\"\r\n -- Leon Robotsky\r\n\r\nAll vim instances that you want to share registers need to be started in server mode.\r\nGVim does this automatically, but terminal vim must be told to do this.\r\n\r\n    vim --servername whateveryouwant\r\n\r\nIf you alias the vim command to always use a server, everything will be automatic and you can spend more time editing with your awesome new shared registers.\r\n\r\n    alias vim=\"vim --servername robotsky\"\r\n\r\nSee http:\/\/github.com\/ardagnir\/united-front for most up-to-date version.\r\n","install_details":"Use pathogen.\r\n\r\n    cd ~\/.vim\/bundle\r\n    git clone https:\/\/github.com\/ardagnir\/united-front","5":"Use pathogen.\r\n\r\n    cd ~\/.vim\/bundle\r\n    git clone https:\/\/github.com\/ardagnir\/united-front","first_name":"James","6":"James","last_name":"Kolb","7":"Kolb","releases":[{"0":"4734","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"united-front.tar","4":"united-front.tar","src_id":"20863","5":"20863","creation_date":"1380470952","6":"1380470952"}]},"4733":{"script_id":"4733","0":"4733","script_name":"Sol","1":"Sol","script_type":"color scheme","2":"color scheme","summary":"Simple colorscheme created for fun and day usage","3":"Simple colorscheme created for fun and day usage","description":"This is simple colorscheme that was created for coding during day (and night) ! \r\n\r\nthe git repo is here: https:\/\/github.com\/Pychimp\/vim-sol \r\n\r\nConsole colorscheme is uploaded here, you can get the Gvim version colorscheme from the above mentioned git repo","4":"This is simple colorscheme that was created for coding during day (and night) ! \r\n\r\nthe git repo is here: https:\/\/github.com\/Pychimp\/vim-sol \r\n\r\nConsole colorscheme is uploaded here, you can get the Gvim version colorscheme from the above mentioned git repo","install_details":"Download and move to ~\/.vim\/colors\/ (or its equivalent in Windows)\r\n\r\nFor Pathogen (or Bundle) users: \r\n\r\nclone the repo into your bundle folder in your .vim directory","5":"Download and move to ~\/.vim\/colors\/ (or its equivalent in Windows)\r\n\r\nFor Pathogen (or Bundle) users: \r\n\r\nclone the repo into your bundle folder in your .vim directory","first_name":"Pratheek","6":"Pratheek","last_name":"","7":"","releases":[{"0":"4733","vim_version":"7.3","1":"7.3","script_version":"0.0.1","2":"0.0.1","version_comment":"Initial upload","3":"Initial upload","package":"sol-term.vim","4":"sol-term.vim","src_id":"20860","5":"20860","creation_date":"1380365713","6":"1380365713"}]},"4732":{"script_id":"4732","0":"4732","script_name":"Integrake","1":"Integrake","script_type":"utility","2":"utility","summary":"Abuse Rake to do project chores around Vim","3":"Abuse Rake to do project chores around Vim","description":"GitHub repository: https:\/\/github.com\/idanarye\/vim-integrake\r\n\r\nBuild systems were originally created to script the build process, but they can do much more - they are actually a great way to organize and run all the project-specific, development-related scripts. You can keep all the scripts for running the project, running unit-tests, cleaning, deploying etc. as different tasks(or targets) in a single build file, and easily run specific tasks from the command-line.\r\n\r\nIntegrake takes this one step farther - it uses Vim's ruby interface and the Rake API to load Rakefiles and run Rake tasks inside the Vim environment. Integrake tasks, are written in Ruby - which means power, elegance and access to any gem you want - and executed in the environment of the current Vim instance - which means you can interact with the buffers, change settings, modify global Vim variables and execute the commands of your Vim plugins.\r\n\r\nIntegrake also assists in creation and editing those Integrake tasks, and allows you to easily copy project-type-general Integrake file that you made in advance.\r\n\r\nFor example - you might always want a :run task that runs your project with specific input(that you often change) and see if it behaves like you want.\r\n\r\n    If the project is a command line application - you will simply want execute it in a shell. Nothing fancy here.\r\n    If it's a web service, you want to send an HTTP request to it and display the result. Since Integrake is written with Ruby, you can use Ruby's default HTTP library - install an alternative, easier-to-use library using RubyGems - to easily send that request.\r\n    Some languages and frameworks are painful to run from the command line, but have a Vim plugin that helps running their projects. Since Integrake runs in the environment of the current Vim instance, you can use those plugins from inside the :run task.\r\n\r\nSince you always use the same task name - :run - you can have a global key mapping that runs your project in the appropriate way, no matter which type of project it is. And since the task is defined in a file in the project's directory, you can easily change the run arguments to test different things in your project, without having to remap the key.","4":"GitHub repository: https:\/\/github.com\/idanarye\/vim-integrake\r\n\r\nBuild systems were originally created to script the build process, but they can do much more - they are actually a great way to organize and run all the project-specific, development-related scripts. You can keep all the scripts for running the project, running unit-tests, cleaning, deploying etc. as different tasks(or targets) in a single build file, and easily run specific tasks from the command-line.\r\n\r\nIntegrake takes this one step farther - it uses Vim's ruby interface and the Rake API to load Rakefiles and run Rake tasks inside the Vim environment. Integrake tasks, are written in Ruby - which means power, elegance and access to any gem you want - and executed in the environment of the current Vim instance - which means you can interact with the buffers, change settings, modify global Vim variables and execute the commands of your Vim plugins.\r\n\r\nIntegrake also assists in creation and editing those Integrake tasks, and allows you to easily copy project-type-general Integrake file that you made in advance.\r\n\r\nFor example - you might always want a :run task that runs your project with specific input(that you often change) and see if it behaves like you want.\r\n\r\n    If the project is a command line application - you will simply want execute it in a shell. Nothing fancy here.\r\n    If it's a web service, you want to send an HTTP request to it and display the result. Since Integrake is written with Ruby, you can use Ruby's default HTTP library - install an alternative, easier-to-use library using RubyGems - to easily send that request.\r\n    Some languages and frameworks are painful to run from the command line, but have a Vim plugin that helps running their projects. Since Integrake runs in the environment of the current Vim instance, you can use those plugins from inside the :run task.\r\n\r\nSince you always use the same task name - :run - you can have a global key mapping that runs your project in the appropriate way, no matter which type of project it is. And since the task is defined in a file in the project's directory, you can easily change the run arguments to test different things in your project, without having to remap the key.","install_details":"Requirements:\r\n\r\n * Ruby installed on your computer(Tested with Ruby 1.9 and 2.0)\r\n * Vim compiled with ruby support(check with \":echo has('ruby')\" from Vim)\r\n * Rake gem installed(install with \"gem install rake\" from the command line)\r\n\r\n\r\nSee \":help integrake-configuration\" for configuration details.","5":"Requirements:\r\n\r\n * Ruby installed on your computer(Tested with Ruby 1.9 and 2.0)\r\n * Vim compiled with ruby support(check with \":echo has('ruby')\" from Vim)\r\n * Rake gem installed(install with \"gem install rake\" from the command line)\r\n\r\n\r\nSee \":help integrake-configuration\" for configuration details.","first_name":"Idan","6":"Idan","last_name":"Arye","7":"Arye","releases":[{"0":"4732","vim_version":"7.0","1":"7.0","script_version":"1.3.0","2":"1.3.0","version_comment":"- Automatically add a task for querying the chosen option of Integrake.option\r\n- Allow passing the option to Integrake.option as an argument\r\n- Add a new prepared autocompletion - :list\r\n- Add input_list - an improved version of Vim's inputlist()\r\n- Fix a bug that prevented invoking IR from regular & block visual mode","3":"- Automatically add a task for querying the chosen option of Integrake.option\r\n- Allow passing the option to Integrake.option as an argument\r\n- Add a new prepared autocompletion - :list\r\n- Add input_list - an improved version of Vim's inputlist()\r\n- Fix a bug that prevented invoking IR from regular & block visual mode","package":"integrake_v1.3.0.zip","4":"integrake_v1.3.0.zip","src_id":"23603","5":"23603","creation_date":"1442607173","6":"1442607173"},{"0":"4732","vim_version":"7.0","1":"7.0","script_version":"1.2.0","2":"1.2.0","version_comment":" - Add a mechanism for passing data from prerequisites to caller tasks.\r\n - Add option-choosing tasks.\r\n - Add window preparation tasks.\r\n - Add autocompletion with the complete method for `Rake::Task`.\r\n - Isolate the integrake file from the rest of the Vim ruby environment.\r\n - Add `to_vim` for Hash.","3":" - Add a mechanism for passing data from prerequisites to caller tasks.\r\n - Add option-choosing tasks.\r\n - Add window preparation tasks.\r\n - Add autocompletion with the complete method for `Rake::Task`.\r\n - Isolate the integrake file from the rest of the Vim ruby environment.\r\n - Add `to_vim` for Hash.","package":"integrake_v1.2.0.zip","4":"integrake_v1.2.0.zip","src_id":"22610","5":"22610","creation_date":"1415576468","6":"1415576468"},{"0":"4732","vim_version":"7.0","1":"7.0","script_version":"1.1.1","2":"1.1.1","version_comment":"Fix a bug where do_in_window crash when there are no results","3":"Fix a bug where do_in_window crash when there are no results","package":"integrake_v1.1.1.zip","4":"integrake_v1.1.1.zip","src_id":"22315","5":"22315","creation_date":"1407795448","6":"1407795448"},{"0":"4732","vim_version":"7.0","1":"7.0","script_version":"1.1.0","2":"1.1.0","version_comment":"Add functions for operating in Vim windows:\r\n - `find_window_numbers` and `find_window_number` for finding window\r\n   numbers.\r\n - `do_in_windows` and `do_in_windows` for running code in certain\r\n   windows.\r\n\r\nAlso fix a bug where you can\\'t run commands with `!`","3":"Add functions for operating in Vim windows:\r\n - `find_window_numbers` and `find_window_number` for finding window\r\n   numbers.\r\n - `do_in_windows` and `do_in_windows` for running code in certain\r\n   windows.\r\n\r\nAlso fix a bug where you can\\'t run commands with `!`","package":"integrake_v1.1.0.zip","4":"integrake_v1.1.0.zip","src_id":"22305","5":"22305","creation_date":"1407426304","6":"1407426304"},{"0":"4732","vim_version":"7.0","1":"7.0","script_version":"1.0.1","2":"1.0.1","version_comment":" Removed a duplicate `IR` tag from the doc. Just because it causes an error on pathogen's `:Helptags`...","3":" Removed a duplicate `IR` tag from the doc. Just because it causes an error on pathogen's `:Helptags`...","package":"integrake.zip","4":"integrake.zip","src_id":"21018","5":"21018","creation_date":"1383946569","6":"1383946569"},{"0":"4732","vim_version":"7.3","1":"7.3","script_version":"1.0.0","2":"1.0.0","version_comment":"Initial upload","3":"Initial upload","package":"integrake.zip","4":"integrake.zip","src_id":"20859","5":"20859","creation_date":"1380312335","6":"1380312335"}]},"4731":{"script_id":"4731","0":"4731","script_name":"cmake.vim","1":"cmake.vim","script_type":"utility","2":"utility","summary":"Incorporates CMake support to Vim.","3":"Incorporates CMake support to Vim.","description":"cmake.vim 0.4.1 is a Vim plugin that allows you to use CMake within Vim for your projects. This is alpha-grade software and may turn your CMake project into a cat-overrun Telnet session.\r\n\r\nIf lost, run :help cmake for a bit of guidance.\r\n\r\n# Requirements\r\nAt the time of writing, cmake.vim has been tested with Vim 7.3+ in nocp mode and CMake 2.8.\r\n\r\n# Getting Started\r\nAfter you installed the plugin, just cd into the directory where the top-level CMakeLists.txt can be found and run:\r\n\r\n\" Create a new binary directory for your clean project.\r\n:CMakeCreateProject <build-dir-name>\r\n\r\n\" Build all of the targets.\r\n:CMakeBuild\r\n\r\nWith that, you created (or re-configured in a vanilla-setup) a new binary directory and built the project.\r\n\r\n# Commands\r\ncmake.vim defines a few methods for generic interaction with CMake. Check out :help cmake-methods for more information.\r\n\r\n# Options\r\nIn order for CMake to operate, it has to know where the build directory is located. This is done automatically by the plugin but it does need help in the event that you happen to build your CMake project in a sub-directory. Check out :help cmake-options for more information.\r\n\r\n# Integrations\r\nSee :help cmake-integrations for tips on integrations cmake.vim with other plug-ins like Syntastic or YouCompleteMe. Long story short, it's freaking awesome but could use some work. With this version, the integrations are now target-specific, allowing for fine-grained integration for every single file.","4":"cmake.vim 0.4.1 is a Vim plugin that allows you to use CMake within Vim for your projects. This is alpha-grade software and may turn your CMake project into a cat-overrun Telnet session.\r\n\r\nIf lost, run :help cmake for a bit of guidance.\r\n\r\n# Requirements\r\nAt the time of writing, cmake.vim has been tested with Vim 7.3+ in nocp mode and CMake 2.8.\r\n\r\n# Getting Started\r\nAfter you installed the plugin, just cd into the directory where the top-level CMakeLists.txt can be found and run:\r\n\r\n\" Create a new binary directory for your clean project.\r\n:CMakeCreateProject <build-dir-name>\r\n\r\n\" Build all of the targets.\r\n:CMakeBuild\r\n\r\nWith that, you created (or re-configured in a vanilla-setup) a new binary directory and built the project.\r\n\r\n# Commands\r\ncmake.vim defines a few methods for generic interaction with CMake. Check out :help cmake-methods for more information.\r\n\r\n# Options\r\nIn order for CMake to operate, it has to know where the build directory is located. This is done automatically by the plugin but it does need help in the event that you happen to build your CMake project in a sub-directory. Check out :help cmake-options for more information.\r\n\r\n# Integrations\r\nSee :help cmake-integrations for tips on integrations cmake.vim with other plug-ins like Syntastic or YouCompleteMe. Long story short, it's freaking awesome but could use some work. With this version, the integrations are now target-specific, allowing for fine-grained integration for every single file.","install_details":"# Installing\r\n\r\nI recommending using Vundle to install plugins. The line necessary to add this plugin is as follows:\r\n\r\nBundle 'jalcine\/cmake.vim`","5":"# Installing\r\n\r\nI recommending using Vundle to install plugins. The line necessary to add this plugin is as follows:\r\n\r\nBundle 'jalcine\/cmake.vim`","first_name":"Jacky","6":"Jacky","last_name":"Alcin\u00c3\u00a9","7":"Alcin\u00c3\u00a9","releases":[{"0":"4731","vim_version":"7.0","1":"7.0","script_version":"0.5.4","2":"0.5.4","version_comment":"better checking for targets within individual buffers.","3":"better checking for targets within individual buffers.","package":"vim-cmake-0.5.4.tar.gz","4":"vim-cmake-0.5.4.tar.gz","src_id":"23063","5":"23063","creation_date":"1426784072","6":"1426784072"},{"0":"4731","vim_version":"7.0","1":"7.0","script_version":"0.5.3","2":"0.5.3","version_comment":"patches to improve buffer detection.","3":"patches to improve buffer detection.","package":"vim-cmake-0.5.3.tar.gz","4":"vim-cmake-0.5.3.tar.gz","src_id":"23062","5":"23062","creation_date":"1426784038","6":"1426784038"},{"0":"4731","vim_version":"7.4","1":"7.4","script_version":"0.5.2","2":"0.5.2","version_comment":"This release includes the following:\r\n\r\n  * Improved support for Syntastic.\r\n  * Better file discovery support for Ninja builds.\r\n  * Stabilized test suite on local machines.\r\n  * Choosing all-global commands instead of buffer specific commands.\r\n  * Support of out-of-source builds in conjunction to the classic in-source builds.","3":"This release includes the following:\r\n\r\n  * Improved support for Syntastic.\r\n  * Better file discovery support for Ninja builds.\r\n  * Stabilized test suite on local machines.\r\n  * Choosing all-global commands instead of buffer specific commands.\r\n  * Support of out-of-source builds in conjunction to the classic in-source builds.","package":"cmake.vim-0.5.2.tar.gz","4":"cmake.vim-0.5.2.tar.gz","src_id":"23006","5":"23006","creation_date":"1425990821","6":"1425990821"},{"0":"4731","vim_version":"7.0","1":"7.0","script_version":"0.5.1","2":"0.5.1","version_comment":"Add information about similar projects to cmake.vim and provided newer Ruby gems for testing.","3":"Add information about similar projects to cmake.vim and provided newer Ruby gems for testing.","package":"cmake-0.5.1.tar.gz","4":"cmake-0.5.1.tar.gz","src_id":"22803","5":"22803","creation_date":"1421412317","6":"1421412317"},{"0":"4731","vim_version":"7.0","1":"7.0","script_version":"0.4.5","2":"0.4.5","version_comment":"updated - includes bugfix for ft detection and better testing.","3":"updated - includes bugfix for ft detection and better testing.","package":"v0.4.5.tar.gz","4":"v0.4.5.tar.gz","src_id":"22537","5":"22537","creation_date":"1413592588","6":"1413592588"},{"0":"4731","vim_version":"7.0","1":"7.0","script_version":"0.4.4","2":"0.4.4","version_comment":"(backported) Add more support for YCM.","3":"(backported) Add more support for YCM.","package":"v0.4.4.tar.gz","4":"v0.4.4.tar.gz","src_id":"22536","5":"22536","creation_date":"1413592552","6":"1413592552"},{"0":"4731","vim_version":"7.0","1":"7.0","script_version":"0.4.3","2":"0.4.3","version_comment":"Purely test changes to make them a bit faster.","3":"Purely test changes to make them a bit faster.","package":"v0.4.3.tar.gz","4":"v0.4.3.tar.gz","src_id":"22337","5":"22337","creation_date":"1408203864","6":"1408203864"},{"0":"4731","vim_version":"7.3","1":"7.3","script_version":"0.4.2","2":"0.4.2","version_comment":"Includes a test suite and allows for better control.","3":"Includes a test suite and allows for better control.","package":"v0.4.2.tar.gz","4":"v0.4.2.tar.gz","src_id":"22210","5":"22210","creation_date":"1405557698","6":"1405557698"},{"0":"4731","vim_version":"7.3","1":"7.3","script_version":"0.1.9-1","2":"0.1.9-1","version_comment":"Improved support for Vimux with absolute file path resolution.","3":"Improved support for Vimux with absolute file path resolution.","package":"v0.1.9-1.tar.gz","4":"v0.1.9-1.tar.gz","src_id":"20855","5":"20855","creation_date":"1380242677","6":"1380242677"},{"0":"4731","vim_version":"7.3","1":"7.3","script_version":"0.1.9","2":"0.1.9","version_comment":"Initial upload","3":"Initial upload","package":"v0.1.9.tar.gz","4":"v0.1.9.tar.gz","src_id":"20853","5":"20853","creation_date":"1380224756","6":"1380224756"}]},"4730":{"script_id":"4730","0":"4730","script_name":"pastek.vim","1":"pastek.vim","script_type":"syntax","2":"syntax","summary":"Syntax for Pastek files","3":"Syntax for Pastek files","description":"Pastek is a lightweight Markdown-like markup language. This script adds syntax support to Vim for *.pastek files.\r\n\r\nhttps:\/\/github.com\/pastek-project\/pastek\r\n\r\nNote: in 2014, Pastek was rewritten by its author and its syntax changed. This file is for the 2013 syntax.","4":"Pastek is a lightweight Markdown-like markup language. This script adds syntax support to Vim for *.pastek files.\r\n\r\nhttps:\/\/github.com\/pastek-project\/pastek\r\n\r\nNote: in 2014, Pastek was rewritten by its author and its syntax changed. This file is for the 2013 syntax.","install_details":"Drop the script in ~\/.vim\/syntax, and add the following line in your vimrc:\r\n\r\nau BufNewFile,BufRead *.pastek set ft=pastek","5":"Drop the script in ~\/.vim\/syntax, and add the following line in your vimrc:\r\n\r\nau BufNewFile,BufRead *.pastek set ft=pastek","first_name":"Baptiste","6":"Baptiste","last_name":"Fontaine","7":"Fontaine","releases":[{"0":"4730","vim_version":"7.0","1":"7.0","script_version":"0.2.0","2":"0.2.0","version_comment":"This is for Pastek\u00e2\u0080\u0099s 2014 syntax. If you use its 2013 syntax, download the script version 0.1.0 instead.","3":"This is for Pastek\u00e2\u0080\u0099s 2014 syntax. If you use its 2013 syntax, download the script version 0.1.0 instead.","package":"pastek.vim","4":"pastek.vim","src_id":"21494","5":"21494","creation_date":"1392626079","6":"1392626079"},{"0":"4730","vim_version":"7.0","1":"7.0","script_version":"0.1.0","2":"0.1.0","version_comment":"Initial upload","3":"Initial upload","package":"pastek.vim","4":"pastek.vim","src_id":"20850","5":"20850","creation_date":"1380181807","6":"1380181807"}]},"4729":{"script_id":"4729","0":"4729","script_name":"VerticalHelp","1":"VerticalHelp","script_type":"utility","2":"utility","summary":"Launch help in vertical window for wide-screen displays","3":"Launch help in vertical window for wide-screen displays","description":"This is a very simple script to display help in an appropriately sized vertical window.\r\n\r\nWith a wide-screen monitor, vim's help is best displayed in a vertical window; but the command 'vertical help' opens a help window taking up half of the display. In my case, it opens a 250 column window to display an 80 column file.  The width of the vertical window is the buffer's textwidth, typically specified in the file's modeline.  \r\n\r\nUSAGE:\r\n:H  <topic>    \" Opens a help window vertically on the right\r\n\r\nIf a help topic was opened horizontally using :h, then the command :H will move and resize the window. \r\nIf a help window already exists that is vertical and sized appropriately, then :H will toggle between the help window and the previous window without having to <C-W>p.\r\n\r\n:H allows for command-line completion, just as :h does.\r\n\r\nOPTIONS:\r\ng:vertical_help_left -- Define this to display the window on the left instead of the right.\r\n\r\nNOTES:\r\nI especially like to use this to display custom cheatsheets, which I format as vim help files.  I put the cheatsheets under vimfiles\/bundle\/cheatsheets\/doc.  Then I call, for example, \r\n:H git-cheatsheet, to pull up my notes. By basing the window width on textwidth, the cheatsheets are not limited to 80 columns.\r\n","4":"This is a very simple script to display help in an appropriately sized vertical window.\r\n\r\nWith a wide-screen monitor, vim's help is best displayed in a vertical window; but the command 'vertical help' opens a help window taking up half of the display. In my case, it opens a 250 column window to display an 80 column file.  The width of the vertical window is the buffer's textwidth, typically specified in the file's modeline.  \r\n\r\nUSAGE:\r\n:H  <topic>    \" Opens a help window vertically on the right\r\n\r\nIf a help topic was opened horizontally using :h, then the command :H will move and resize the window. \r\nIf a help window already exists that is vertical and sized appropriately, then :H will toggle between the help window and the previous window without having to <C-W>p.\r\n\r\n:H allows for command-line completion, just as :h does.\r\n\r\nOPTIONS:\r\ng:vertical_help_left -- Define this to display the window on the left instead of the right.\r\n\r\nNOTES:\r\nI especially like to use this to display custom cheatsheets, which I format as vim help files.  I put the cheatsheets under vimfiles\/bundle\/cheatsheets\/doc.  Then I call, for example, \r\n:H git-cheatsheet, to pull up my notes. By basing the window width on textwidth, the cheatsheets are not limited to 80 columns.\r\n","install_details":"Put the .vim file to ~\/.vim\/plugin","5":"Put the .vim file to ~\/.vim\/plugin","first_name":"Mel","6":"Mel","last_name":"Davis","7":"Davis","releases":[{"0":"4729","vim_version":"7.0","1":"7.0","script_version":"1.02","2":"1.02","version_comment":"Sets help window to textwidth, instead of defaulting to 80 columns.","3":"Sets help window to textwidth, instead of defaulting to 80 columns.","package":"VerticalHelp.vim","4":"VerticalHelp.vim","src_id":"20939","5":"20939","creation_date":"1382305394","6":"1382305394"},{"0":"4729","vim_version":"7.0","1":"7.0","script_version":"1.01","2":"1.01","version_comment":"Corrected check for windows size and corrected a normal command.","3":"Corrected check for windows size and corrected a normal command.","package":"VerticalHelp.vim","4":"VerticalHelp.vim","src_id":"20849","5":"20849","creation_date":"1380142609","6":"1380142609"}]},"4728":{"script_id":"4728","0":"4728","script_name":"Tags Updater","1":"Tags Updater","script_type":"utility","2":"utility","summary":"Simple tags automatic updater","3":"Simple tags automatic updater","description":"This script is a very simple utility to help you to update tags automatically.\r\nIt will update the tags after saving a file.\r\n\r\nDEPENDING:\r\n  * ctags\r\n  * sed\r\n  * grep\r\n\r\nUSAGE:\r\n  $ ctags -R\r\n  $ vim <file> # now tags will update automatically\r\n\r\nOPTIONS:\r\n  g:tags_updater_update_exist     integer (default 0)\r\n      If not 0, Tags Updater only updates tags of file which the file is\r\n      already in tags file\r\n\r\n  g:tags_updater_ctags_program    string (default 'ctags')\r\n      The ctags program.\r\n\r\nLIMITATION:\r\n  If g:tags_updater_update_exist is 0, the file under directory of tags will\r\n  be updated. For example, case 1 will not be updated and case 2 will be.\r\n\r\n  case 1:\r\n      dir\r\n      |-- a\r\n      |   `-- tags\r\n      `-- file\r\n\r\n  case 2:\r\n      dir\r\n      |-- a\r\n      |   `-- file\r\n      `-- tags","4":"This script is a very simple utility to help you to update tags automatically.\r\nIt will update the tags after saving a file.\r\n\r\nDEPENDING:\r\n  * ctags\r\n  * sed\r\n  * grep\r\n\r\nUSAGE:\r\n  $ ctags -R\r\n  $ vim <file> # now tags will update automatically\r\n\r\nOPTIONS:\r\n  g:tags_updater_update_exist     integer (default 0)\r\n      If not 0, Tags Updater only updates tags of file which the file is\r\n      already in tags file\r\n\r\n  g:tags_updater_ctags_program    string (default 'ctags')\r\n      The ctags program.\r\n\r\nLIMITATION:\r\n  If g:tags_updater_update_exist is 0, the file under directory of tags will\r\n  be updated. For example, case 1 will not be updated and case 2 will be.\r\n\r\n  case 1:\r\n      dir\r\n      |-- a\r\n      |   `-- tags\r\n      `-- file\r\n\r\n  case 2:\r\n      dir\r\n      |-- a\r\n      |   `-- file\r\n      `-- tags","install_details":"Put the .vim file to ~\/.vim\/plugin or corresponding directory on Windows.\r\nNOTE: If you are on Windows, grep and sed programs are needed in your PATH. Download them from http:\/\/gnuwin32.sourceforge.net\/ and and to you PATH environment variable.","5":"Put the .vim file to ~\/.vim\/plugin or corresponding directory on Windows.\r\nNOTE: If you are on Windows, grep and sed programs are needed in your PATH. Download them from http:\/\/gnuwin32.sourceforge.net\/ and and to you PATH environment variable.","first_name":"fanhe","6":"fanhe","last_name":" ","7":" ","releases":[{"0":"4728","vim_version":"7.2","1":"7.2","script_version":"1.2","2":"1.2","version_comment":" - Supported Windows (need grep and sed).","3":" - Supported Windows (need grep and sed).","package":"tags_updater.vim","4":"tags_updater.vim","src_id":"20861","5":"20861","creation_date":"1380371264","6":"1380371264"},{"0":"4728","vim_version":"7.2","1":"7.2","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"tags_updater.vim","4":"tags_updater.vim","src_id":"20845","5":"20845","creation_date":"1380124107","6":"1380124107"}]},"4727":{"script_id":"4727","0":"4727","script_name":"stringliteral","1":"stringliteral","script_type":"ftplugin","2":"ftplugin","summary":"C++ multi-line string literals from common text","3":"C++ multi-line string literals from common text","description":"This script convert multiline text in a C++ file to a multi-line\r\nstring literal, escaping the quote and tab characters. It also does\r\nthe reverse conversion, un-escaping some characters. It's not too\r\ncomplete for now, but it will be someday if needs come.\r\n\r\nThis script requires Python.\r\n\r\nYou can find a source-repository for this script here:\r\n\r\nhttps:\/\/bitbucket.org\/dsign\/stringliteral.vim\r\n\r\nFeel free to use Bitbucket's ticket system or to write-me an email to a.viamontes.esquivel @\"google's popular email service\"  with comments or suggestions. \r\n\r\n","4":"This script convert multiline text in a C++ file to a multi-line\r\nstring literal, escaping the quote and tab characters. It also does\r\nthe reverse conversion, un-escaping some characters. It's not too\r\ncomplete for now, but it will be someday if needs come.\r\n\r\nThis script requires Python.\r\n\r\nYou can find a source-repository for this script here:\r\n\r\nhttps:\/\/bitbucket.org\/dsign\/stringliteral.vim\r\n\r\nFeel free to use Bitbucket's ticket system or to write-me an email to a.viamontes.esquivel @\"google's popular email service\"  with comments or suggestions. \r\n\r\n","install_details":"Copy the stringliteral.vim file to some place in your Vim's runtime under the directory ftplugin\/cpp,\r\nand the .txt file to doc\/. Note that you will need filetype plugin on for this to work.  Redo the help \r\ntags file with :helptags <youruntimepath>","5":"Copy the stringliteral.vim file to some place in your Vim's runtime under the directory ftplugin\/cpp,\r\nand the .txt file to doc\/. Note that you will need filetype plugin on for this to work.  Redo the help \r\ntags file with :helptags <youruntimepath>","first_name":"Alcides","6":"Alcides","last_name":"Viamontes","7":"Viamontes","releases":[{"0":"4727","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"stringliteral-0.1.tar.gz","4":"stringliteral-0.1.tar.gz","src_id":"20841","5":"20841","creation_date":"1380049497","6":"1380049497"}]},"4726":{"script_id":"4726","0":"4726","script_name":"Extended-FT","1":"Extended-FT","script_type":"utility","2":"utility","summary":"Extended functionality for 'f' and 't' commands","3":"Extended functionality for 'f' and 't' commands","description":"This plugin adds the following behaviour to the default behaviour of the `f`, `F`, `t`, and `T` commands:\r\n- Multiline - Can search across multiple lines or continue searching across multiple lines using `;` and `,` keys\r\n- Smart Case - When the search character is lower case it matches both lower and upper case, and when the character is uppercase it matches only upper case.\r\n- Allow repeating `t` and `T` commands using `;` or `,` commands (which doesn't really work properly in default Vim)\r\n\r\nIt's also worth noting that it only adds the new position to the jumplist if you've changed lines.\r\n\r\nFor more information please visit the github page at: https:\/\/github.com\/svermeulen\/vim-extended-ft\r\n\r\nCustomization\r\n-----------------------------\r\nIf you have remapped any of the `f`\/`F`\/`t`\/`T`\/`;`\/`,` keys you can still use the plugin without changing it, by including the following in your .vimrc:\r\n\r\n`let g:ExtendedFTUseDefaults = 0`\r\n\r\nAnd then remapping the desired keys to the `<plug>` mappings in your .vimrc (see the bottom of the file vim-extended-ft.vim for an example).\r\n\r\nTo disable smartcase matching, and either force case-sensitive or case-insensitive, use this option in your .vimrc:\r\n\r\n`let g:ExtendedFT_caseOption = `\r\n\r\nPossible values:\r\n\r\n* '\\c' - Forces `ignorecase`\r\n* '\\C' - Forces `noignorecase`","4":"This plugin adds the following behaviour to the default behaviour of the `f`, `F`, `t`, and `T` commands:\r\n- Multiline - Can search across multiple lines or continue searching across multiple lines using `;` and `,` keys\r\n- Smart Case - When the search character is lower case it matches both lower and upper case, and when the character is uppercase it matches only upper case.\r\n- Allow repeating `t` and `T` commands using `;` or `,` commands (which doesn't really work properly in default Vim)\r\n\r\nIt's also worth noting that it only adds the new position to the jumplist if you've changed lines.\r\n\r\nFor more information please visit the github page at: https:\/\/github.com\/svermeulen\/vim-extended-ft\r\n\r\nCustomization\r\n-----------------------------\r\nIf you have remapped any of the `f`\/`F`\/`t`\/`T`\/`;`\/`,` keys you can still use the plugin without changing it, by including the following in your .vimrc:\r\n\r\n`let g:ExtendedFTUseDefaults = 0`\r\n\r\nAnd then remapping the desired keys to the `<plug>` mappings in your .vimrc (see the bottom of the file vim-extended-ft.vim for an example).\r\n\r\nTo disable smartcase matching, and either force case-sensitive or case-insensitive, use this option in your .vimrc:\r\n\r\n`let g:ExtendedFT_caseOption = `\r\n\r\nPossible values:\r\n\r\n* '\\c' - Forces `ignorecase`\r\n* '\\C' - Forces `noignorecase`","install_details":"I recommend loading your plugins with vundle or pathogen or neobundle","5":"I recommend loading your plugins with vundle or pathogen or neobundle","first_name":"Steve","6":"Steve","last_name":"Vermeulen","7":"Vermeulen","releases":[{"0":"4726","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":".","3":".","package":"vim-extended-ft.zip","4":"vim-extended-ft.zip","src_id":"20826","5":"20826","creation_date":"1379858800","6":"1379858800"}]},"4725":{"script_id":"4725","0":"4725","script_name":"vim-emoji","1":"vim-emoji","script_type":"utility","2":"utility","summary":"Emoji in Vim","3":"Emoji in Vim","description":"https:\/\/github.com\/junegunn\/vim-emoji\r\n\r\nEmoji in Vim. Emojis are only available on terminal Vim on Mac.\r\n\r\n\r\nList of functions:\r\n\r\n- emoji#available()\r\n- emoji#for(name[, default = '', pad = 1])\r\n  - Refer to http:\/\/www.emoji-cheat-sheet.com\r\n  - Returns an empty string if not available\r\n- emoji#list()\r\n\r\nExample - Using Emojis as GitGutter symbols:\r\n\r\nsilent! if emoji#available()\r\n  let g:gitgutter_sign_added = emoji#for('small_blue_diamond')\r\n  let g:gitgutter_sign_modified = emoji#for('small_orange_diamond')\r\n  let g:gitgutter_sign_removed = emoji#for('small_red_triangle')\r\n  let g:gitgutter_sign_modified_removed = emoji#for('collision')\r\nendif","4":"https:\/\/github.com\/junegunn\/vim-emoji\r\n\r\nEmoji in Vim. Emojis are only available on terminal Vim on Mac.\r\n\r\n\r\nList of functions:\r\n\r\n- emoji#available()\r\n- emoji#for(name[, default = '', pad = 1])\r\n  - Refer to http:\/\/www.emoji-cheat-sheet.com\r\n  - Returns an empty string if not available\r\n- emoji#list()\r\n\r\nExample - Using Emojis as GitGutter symbols:\r\n\r\nsilent! if emoji#available()\r\n  let g:gitgutter_sign_added = emoji#for('small_blue_diamond')\r\n  let g:gitgutter_sign_modified = emoji#for('small_orange_diamond')\r\n  let g:gitgutter_sign_removed = emoji#for('small_red_triangle')\r\n  let g:gitgutter_sign_modified_removed = emoji#for('collision')\r\nendif","install_details":"Extract in ~\/.vim or use your favorite plugin manager","5":"Extract in ~\/.vim or use your favorite plugin manager","first_name":"Junegunn","6":"Junegunn","last_name":"Choi","7":"Choi","releases":[{"0":"4725","vim_version":"7.3","1":"7.3","script_version":"0.2.0","2":"0.2.0","version_comment":"Reduce load time by around 10%","3":"Reduce load time by around 10%","package":"vim-emoji.zip","4":"vim-emoji.zip","src_id":"20828","5":"20828","creation_date":"1379867184","6":"1379867184"}]},"4724":{"script_id":"4724","0":"4724","script_name":"Ultimate Test Utility","1":"Ultimate Test Utility","script_type":"utility","2":"utility","summary":"A straightforward, fully documented unit testing utility.","3":"A straightforward, fully documented unit testing utility.","description":"Vim Ultimate Test Utility\r\n=========================\r\n\r\nIntroduction                      \r\n------------\r\n\r\nUltimate-Test-Utility is the only tool you\\'ll need for creating and running\r\nunit tests in Vim. Unit testing has been notoriously hard for Vim-script and\r\nthe plugins that do exist often require languages, are difficult to\r\nsetup\/configure\/use, have bugs, or have incomplete documentation.\r\n\r\nUltimate-Test-Utility is maintained solely by Kevin Biskar and is constantly\r\nexpanding it\\'s features. If you have any concerns, feature requests, or have\r\nfound any undocumented bugs, please notify him (me).\r\n\r\nThis is also available on github at https:\/\/github.com\/biskark\/vim-ultimate-test-utility\r\n\r\nFeatures and Requirements          \r\n-------------------------\r\n\r\n- Ultimate-Test-Utility is written solely in vimscript so compilation\r\n  requirements are minimal.\r\n\r\n    - However, Ultimate-Test-Utility must be run in a Vim 7.0 or higher and\r\n      some functions may require read\/write access to files you may be using.\r\n      Of course, use those functions with care, though the instances in which\r\n      these precautions are necessary should be obvious; Ultimate-Test-Utility \r\n      does NOT want to harm your work, it\\'s here to help.\r\n\r\n    - Also, Ultimate-Test-Utility has included some example functions that\r\n      may not work correctly on your OS. This should not be an issue when\r\n      using this plugin to write your own vimscript code, only when trying the\r\n      demos. In the future, these examples may be updated to be compatible with\r\n      as many OSes and setups as possible.\r\n\r\n- Ultimate-Test-Utility provides several levels of reporting so your reports\r\n  are as detailed or minimal as you\\'d like.\r\n\r\n- Ultimate-Test-Utility allows for easy installation through Pathogen, Vundle,\r\n  or other compatible plugin managers. If you\\'re reading this, it\\'s likely\r\n  installed correctly already, but if not consult the README.md file.\r\n\r\n- Ultimate-Test-Utility is, like most vim plugins, open-source! Please feel\r\n  free to distribute, contribute, modify or spread the word.\r\n\r\n\r\n\r\nUsage                              \r\n-----\r\n\r\nUltimate-Test-Utility has a straightforward API, and is not unlike the Perl\r\ntesting suite. However, Vim\\'s lack of out-of-box OOP and our decision to\r\nmaximize compatibility (we don\\'t use other languages or CLI testing\r\nsoftware) means that Ultimate-Test-Utility does have a mild\r\nlearning-curve, but should be easy to pick for both testing veterans and\r\nfirst-timers alike.\r\n\r\n- The first section, Ultimate-Test-Utility-Quick-Start, provides a quick\r\noverview of how to use this plugin.\r\n\r\n- The second section, Ultimate-Test-Utility-Basic-Examples, shows the most\r\ncommon usage and should be enough to get you started on working on your own\r\nprojects.\r\n\r\n- The third section, Ultimate-Test-Utility-Basic-Examples, explores more\r\ncomplex usage cases and explains the interface to some of the less intuitive\r\nfunctions.\r\n\r\nThe more complex examples are available in examples.vim.\r\n\r\n\r\nQuick Start Guide                 \r\n-----------------\r\n\r\nUltimate-Test-Utility breaks down tests into two categories. Individual\r\nAssertion tests (referred to as sub-tests) which check for one specific thing,\r\nand groupings of related sub-tests (collectively referred to as a test).\r\nIt\\'s often natural to have sub-tests in a full test address different aspects\r\nand edge cases of a particular function or key mapping. Thus a plugin with 4\r\nfunctions and 1 keymapping may have 5 total \\\"tests\\\", with each \\\"test\\\"\r\nconsisting of up to dozens of \\\"sub-tests.\\\"\r\n\r\nThe basic workflow is simple.\r\n\r\n1. You MUST call UltiTestStart to tell vim that you are going into\r\n   \\\"test-mode\\\".\r\n\r\n2. You then call as many UltiAssert... sub-tests as you need.\r\n\r\n3. You then call UltiTestStop to tell vim that a particular test is over.\r\n\r\n4. You may then call UltiTestReport which will give a report of varying\r\n   detail about the success and failure of your sub-tests. Additionally, this\r\n   will report the overall success of the entire test. The degree of detail\r\n   reported is dependent on the value of g:ulti\\\\_test\\\\_verbose. See\r\n   Ultimate-Test-Utility-Config for more details.\r\n\r\n5. If you wish to execute more tests (ie. more groupds of sub-tests), you\r\n   should call UltiTestReset.\r\n\r\n6. Repeat steps 1-6 as needed.\r\n\r\n7. You may then call UltiTestFinalSummary to give a simple summary of all\r\n   the \\\"tests\\\" you have run (since you either loaded the plugin or called\r\n   UltiTestResetAll, see next step for details).\r\n\r\n8. If you wish to run another suite of \\\"tests\\\", say for a different plugin or\r\n   file, call UltiTestResetAll.\r\n\r\n9. Repeat steps 1-8 as needed.\r\n\r\nThe next section shows how to setup and run one full \\\"test\\\" on an example\r\nfunction.\r\n\r\nBasic Examples                    \r\n--------------\r\n\r\nSpecial Note: It\\'s good practice to write your tests before you write the code\r\nyou\\'re testing, but for the purpose of this tutorial, we\\'ll ignore that.\r\n\r\nExample Multiply function, takes two arguments and returns the quotient.\r\n\r\n```vim\r\nfunction! Multiply(numerator, denominator)\r\n    return a:numerator * a:denominator\r\nendfunction\r\n```\r\n\r\nExample test function that examines some basic-use cases and possible edge\r\ncases. Comments have been sprinkled in to explain a little of the API.\r\n    \r\n```vim\r\nfunction! MultiplyTestOne()\r\n    call UltiTestStart()\r\n\r\n    call UltiAssertTrue(\\'\\', Multiply(2, 2) == 4, \\'true\\')\r\n\r\n    call UltiAssertTrue(\\\"Testing 1 times 1 isn\\'t 6\\\",\r\n                \\\\ Multiply(1, 1) == 6,\r\n                \\\\ \\'false\\')\r\n\r\n    \\\" We\\'re deliberately making an incorrect test here to see what happens\r\n    call UltiAssertTrue(\\\"Testing 5 times -2 isn\\'t -10\\\",\r\n                \\\\ Multiply(5, -2) == -10,\r\n                \\\\ \\'false\\')\r\n\r\n    call UltiAssertEquals(\\'Testing Multiply(2.0, 3) == Multiply(3.0, 2)\\',\r\n                \\\\ Multiply(2.0, 3),\r\n                \\\\ Multiply(3.0, 2),\r\n                \\\\ \\'true\\')\r\n\r\n    call UltiTestStop()\r\n    call UltiTestReport()\r\nendfunction\r\n\r\n\\\" Now to run the test\r\ncall MultiplyTestOne()\r\n```\r\n\r\nThis should give something like the following as output:\r\n\r\n```vim\r\n    Sub-test 3: Failed, Testing 5 times -2 isn\\'t -10\r\n    Test 1 Results:\r\n        Expected: Not specified, Passed: 3, Failed: 1, Skipped: 0\r\n```\r\n\r\nYay, it works, let\\'s review what we did.\r\n\r\nThe calls to UltiTestStart, UltiTestStop, and UltiTestReport were covered in\r\nthe previous section and are straightforward. However, we then called the\r\nactual sub-tests themselves.\r\n\r\nEach sub-test available starts with \\'UltiAssert\\'.\r\nEach UltiAssert function has a slightly different argument signature but there\r\nare some similarities in usage.\r\n\r\n1. The first argument is a string describing the purpose of the test. Notice\r\n   this message was displayed when sub-test 3 failed. Descriptive messages\r\n   make pin-pointing problems quick, but you may provide an empty string like\r\n   we did for the first sub-test.\r\n\r\n2. Next are the arguments unique to the assertion test being run.\r\n\r\n3. The last argument is optional, and can only be the string \\'skip\\' to\r\n   indicate that you don\\'t want to run the test at this time. Notice that we\r\n   did not use this feature in any of the tests we just ran.\r\n\r\n4. The argument before \\'skip\\' (aka the last argument if you don\\'t\r\n   provide \\'skip\\'), must be either \\'true\\' or \\'false\\', indicating if\r\n   the Assertion is expected to be true or false.\r\n\r\nEssentially, each simple UltiAssert... looks like this...\r\n\r\n```vim\r\n    call UltiAssertSimple(description, ..., expected_outcome)  \\\" or\r\n    call UltiAssertSimple(description, ..., expected_outcome, \\'skip\\')\r\n```\r\n\r\nwhere the \\'...\\' is unique to whatever test you\\'re using.\r\n\r\nNote: there is no test called UltiAssertSimple or UltiAssert.... These are\r\nplace holder names.\r\n\r\nNotice that in MultiplyTestOne we used UltiAssertTrue, which took one unique\r\nargument (the result of the Multiply function call) and UltiAssertEquals which\r\ntook two unique arguments (the results of two Multiply function calls). As you\r\nmay have guessed, UltiAssertTrue simply evaluates the truthiness of its one\r\nunique argument, and UltiAssertEquals compares its two unique arguments to\r\neachother.  Most sub-tests can be written with either one of these. The\r\npresence of both of them, and the more specific assertions explained in the\r\nnext section, is merely a convenience. You should use whichever sub-tests feel\r\nthe most natural.\r\n\r\nNext Steps:\r\nYay, it works ... but it could be better. Ignoring that our function is\r\ntrivial, we deliberately made a mistake, and the usefulness of these tests is\r\nquestionable, we can still improve our test function.\r\n\r\n1. If we run our test again, it now says we\\'re on Test 2 even though this\r\n   is the same test we just ran.\r\n\r\n2. \\'Test 1\\' isn\\'t a horribly informative name in the first place.\r\n\r\n3. Though moot in this case, how do we know we tested everything we\r\n   intended? Though careful coding can eliminate this problem, in tests with\r\n   many sub-tests, especially in more complicated plugins, we may want an\r\n   extra level of confidence.\r\n\r\nIt turns out we can fix all of these problems with minimal effort.\r\n\r\n```vim\r\nfunction! MultiplyTestTwo()\r\n    call UltiTestReset()\r\n    call UltiTestStart(\\'Testing the Multiply Function\\', 4)\r\n\r\n    call UltiAssertTrue(\\'\\', Multiply(2, 2) == 4, \\'true\\')\r\n\r\n    call UltiAssertTrue(\\\"Testing 1 times 1 isn\\'t 6\\\",\r\n                \\\\ Multiply(1, 1) == 6,\r\n                \\\\ \\'false\\')\r\n\r\n    \\\" We\\'re deliberately making an incorrect test here to see what happens\r\n    call UltiAssertTrue(\\\"Testing 5 times -2 isn\\'t -10\\\",\r\n                \\\\ Multiply(5, -2) == -10,\r\n                \\\\ \\'false\\')\r\n\r\n    call UltiAssertEquals(\\'Testing Multiply(2.0, 3) == Multiply(3.0, 2)\\',\r\n                \\\\ Multiply(2.0, 3),\r\n                \\\\ Multiply(3.0, 2),\r\n                \\\\ \\'true\\',\r\n                \\\\ \\'skip\\')\r\n\r\n    call UltiTestStop()\r\n    call UltiTestReport()\r\nendfunction\r\n\r\n\\\" Now to run the test\r\ncall MultiplyTestOne()\r\n```\r\n\r\nThis should give something like the following as output:\r\n\r\n```vim\r\nSub-test 3: Failed, Testing 5 times -2 isn\\'t -10\r\nTest 1 \\'Testing the Multiply Function\\' Results:\r\n    Expected: 4, Passed: 2, Failed: 1, Skipped: 1\r\n```\r\n\r\nTwo quick points, and we can move on to more advanced usage.\r\n\r\n1. The call to UltiTestReset tells vim to reset our sub-test counters so\r\n   that we could have been placed at the end of the function instead of the\r\n   beginning. However, as we\\'ll see, this call should usually be made outside\r\n   of any one test, and rather after or before running a suite of tests.\r\n\r\n2. The call to UltiTestStart can take two optional arguments in any order.\r\n   It can take a string that should describe how the sub-tests are related,\r\n   and an integer that tells the test how many sub-tests to expect.\r\n\r\n3. The last sub-test has the \\'skip\\' argument added, just to show how to use\r\n   it. Note that adding \\'skip\\' only prevents the result from being factored in\r\n   the testing facility, it won\\'t prevent any errors in the other arguments\r\n   from causing problems.\r\n\r\n\r\nExtended Examples                \r\n-----------------\r\n\r\nLet\\'s broaden our look at this plugin be testing some more complicated\r\nplugins\/functions and integrating several tests into one suite. Assume all\r\nreferences to MultiplyTest() refer to the MultiplyTestTwo() function from the\r\nprevious section.\r\n\r\nSpecial Note: It\\'s good practice to write your tests before you write the code\r\nyou\\'re testing, but for the purpose of this tutorial, we\\'ll ignore that.\r\n\r\nFirst let\\'s write two more functions and add a keymapping for one of them.\r\n\r\nThe first is a slightly trickier function that echos the quotient of two\r\nnumbers rather than merely returns them. Also, divide by zero exceptions may\r\nbe thrown and we\\'ll show how to deal with that.\r\n\r\n```vim\r\nfunction! Divide(numerator, denominator)\r\n    if a:denominator == 0\r\n        throw \\\"Divide by zero\\\"\r\n    endif\r\n    echo (a:numerator \/ a:denominator)\r\nendfunction\r\n```\r\n\r\nThe next is a vim function that inserts the word \\\"Hello\\\" into the current\r\nbuffer. For convenience, we\\'ll also add a helper function that adds a\r\nkeymapping for this function.\r\n\r\n```vim\r\nfunction! InsertHello()\r\n    execute \\'normal! iHello\\'\r\nendfunction\r\n\r\nfunction! NewMapping()\r\n    nnoremap <silent> <leader>S :call InsertHello()<cr>\r\nendfunction\r\n```\r\n\r\n\r\nOk, now let\\'s write those tests.\r\n\r\n```vim\r\nfunction! TestDivide()\r\n    call UltiTestStart(\\\"Divide Tests\\\", 5)\r\n    \r\n    \\\" Output tests\r\n    call UltiAssertInOutput(\\'6 \/ 2 == 3\\', \\'Divide\\', [6, 2], \\'3\\', \\'true\\')\r\n    call UltiAssertInOutput(\\\"1 \/ 3 == 0 (\\'Testing Int Division\\')\\\",\r\n                \\\\ \\'Divide\\', [1, 3], \\'6\\', \\'false\\')\r\n\r\n    \\\" Exception tests\r\n    call UltiAssertException(\\\"Throws divide by zero error\\\",\r\n                \\\\ \\'Divide by zero\\', \\'Divide\\', [4, 0], \\'true\\')\r\n    call UltiAssertException(\\\"Doesn\\'t throw divide by zero error\\\",\r\n                \\\\ \\'Divide by zero\\', \\'Divide\\', [4, 2], \\'false\\')\r\n    \\\" For variety, use a variable for the function name\r\n    let l:fx = \\'Divide\\'\r\n    call UltiAssertException(\\\"Complains about arguments\\\",\r\n                \\\\ \\'Not enough arguments\\', l:fx, [], \\'true\\')\r\n\r\n    call UltiTestStop()\r\n    call UltiTestReport()\r\nendfunction\r\n```\r\n\r\nNotes:\r\nUltiAssertInOuput and UltiAssertException both have more complicated\r\ninterfaces but share similarities with the previous UltiAssert functions\r\nand with each other.\r\n\r\n1. Like the others, the first argument is a descriptive name, and the last\r\n   two arguments are the expection (either \\\"true\\\" or \\\"false\\\") and an\r\n   optional \\\"skip\\\" string to indicate the test is skipped.\r\n2. The second argument is a variable or raw string with the name of the\r\n   function to be tested. The name should NOT have parentheses or any\r\n   arguments.\r\n3. The third argument is a List of all arguments you would like to be\r\n   passed to the function you\\'re testing. If no arguments are to be passed,\r\n   you must provide an empty list \\'[]\\'.\r\n4. The fourth argument is a string or regex specific to the UltiAssert test\r\n   you\\'re using. For UltiAsserException, it should be the exception you\r\n   expect to be thrown. For UltiAssertInOutput it should be the string\r\n   you expect to be in the output.\r\n\r\nIn summary, each simple UltiAssert... looks like this...\r\n\r\n```vim\r\ncall UltiAssertSimple(desc, ..., expected_outcome)  \\\" or\r\ncall UltiAssertSimple(desc, ..., expected_outcome, \\'skip\\')\r\n```\r\nwhere the \\'...\\' is unique to whatever test you\\'re using.\r\n\r\nEach complex UltiAssert... looks like this.\r\n\r\n```vim\r\ncall UltiAssertComplex(desc, fx, arguments, string, expected_outcome)  \\\" or\r\ncall UltiAssertComplex(desc, fx, arguments, string, expected_outcome, \\'skip\\')\r\n```\r\n\r\nNote: there is no test called UltiAssertSimple or UltiAssert... or\r\nUltiAssertComplex. These are place holder names only.\r\n\r\n\r\nThis next test is a bit of a cheat in that it tests the InsertHello() function\r\nvia the keymapping where these tests should probably be separate. Also, the\r\nuse of the mapleader variable can be troublesome because the mapping is always\r\nwhatever the value of the leader key at the time it was set. If this doesn\\'t\r\nmake sense to you, just know to be careful if you use it.\r\n\r\n```vim\r\nfunction! TestInsertHello()\r\n    call UltiTestStart(\\'Testing Command Mapping and Text Insertion\\', 3)\r\n\r\n    if exists(\\'mapleader\\')\r\n        let leader = mapleader\r\n    else\r\n        let leader = \\'\\\\\\'\r\n    endif\r\n\r\n    \\\" Make the new mapping\r\n    call NewMapping()\r\n\r\n    let l:fx = \\'Hello\\'\r\n    call UltiAssertInBuffer(\\'Testing for \\\"Hello\\\" absence before execute\\',\r\n                \\\\ \\'Hello\\', \\'false\\')\r\n\r\n    execute \\'normal! \\' . leader . \\'S\\'\r\n    call UltiAssertInBuffer(\\'Testing for \\\"Hello\\\" absence after normal!\\',\r\n                \\\\ \\'Hello\\', \\'false\\')\r\n\r\n    execute \\'normal \\' . leader . \\'S\\'\r\n    call UltiAssertInBuffer(\\'Testing for \\\"Hello World\\\" presence after normal\\',\r\n                \\\\ \\'Hello\\', \\'true\\')\r\n    \r\n    \\\" Clean up the text that was just inserted. Not necessary for the\r\n    \\\" test though.\r\n    execute \\\"s\/Hello\/\/\\\"\r\n\r\n    call UltiTestStop()\r\n    call UltiTestReport()\r\nendfunction\r\n```\r\n\r\nNotes\r\n1. We specified there should be 3 sub-tests run and given the test a\r\n   description.\r\n\r\n2. We have not called UltiTestReset yet.\r\n\r\n3. Now that we\\'re executing more complicated functions, we need\r\n   to be careful that we\\'re not polluting the current buffer with side-effects\r\n   from our testing. In particular beware of testing UltiAssertInBuffer\r\n   sub-tests in the buffer where you wrote the test. See if you can figure out\r\n   why.\r\n\r\n4. UltiAssertInBuffer has an almost identical interface to UltiAssertTrue.\r\n\r\n\r\nFinally, let\\'s organize these two tests into a full suite with the\r\nMultiplyTest from before. Take out the call to UltiTestReset in the\r\nMultiplyTest.\r\n\r\n```vim\r\nfunction! AllTests()\r\n    call UltiTestReset()         \\\" Clears residual junk\r\n\r\n    call MultiplyTest()\r\n    call TestDivide()\r\n    call TestInsertHello()\r\n\r\n    call UltiTestFinalSummary()  \\\" Brief summary of all three tests\r\n    call UltiTestResetAll()      \\\" Clears everything\r\nendfunction\r\n```\r\n\r\nNow to call the whole thing...\r\n\r\n```vim\r\ncall AllTests()\r\n```\r\n\r\nRemember that because our TestInsertHello() tests for the presence and absence\r\nof the string \\'Hello\\' in the buffer it\\'s executed in, it\\'s best to run these\r\ntests in an empty buffer. So it\\'s probably best to source these functions,\r\nswitch to a new buffer, and then call AllTests().\r\n\r\nYou can change the output by setting one of these three values before you call\r\nthe function.\r\n\r\n```vim\r\nlet g:ulti_test_verbose = 0    \\\" or\r\nlet g:ulti_test_verbose = 1    \\\" or\r\nlet g:ulti_test_verbose = 2\r\n```\r\n\r\nAssuming you left it at 1, you should get ...\r\n\r\n```vim\r\nSub-test 3: Failed, Testing 5 times -2 isn\\'t -10\r\nTest 1 Results:\r\n    Expected: 4, Passed: 3, Failed: 1, Skipped: 0\r\n\r\nTest 2 \\'Divide Test\\' Results\r\n    Expected: 5, Passed: 5, Failed: 0, Skipped: 0\r\n\r\nTest 3 \\'Testing Command Mapping and Text Insertion\\' Results\r\n    Expected: 3, Passed: 3, Failed: 0, Skipped: 0\r\n\r\n1 test(s) failed.\r\n```\r\n","4":"Vim Ultimate Test Utility\r\n=========================\r\n\r\nIntroduction                      \r\n------------\r\n\r\nUltimate-Test-Utility is the only tool you\\'ll need for creating and running\r\nunit tests in Vim. Unit testing has been notoriously hard for Vim-script and\r\nthe plugins that do exist often require languages, are difficult to\r\nsetup\/configure\/use, have bugs, or have incomplete documentation.\r\n\r\nUltimate-Test-Utility is maintained solely by Kevin Biskar and is constantly\r\nexpanding it\\'s features. If you have any concerns, feature requests, or have\r\nfound any undocumented bugs, please notify him (me).\r\n\r\nThis is also available on github at https:\/\/github.com\/biskark\/vim-ultimate-test-utility\r\n\r\nFeatures and Requirements          \r\n-------------------------\r\n\r\n- Ultimate-Test-Utility is written solely in vimscript so compilation\r\n  requirements are minimal.\r\n\r\n    - However, Ultimate-Test-Utility must be run in a Vim 7.0 or higher and\r\n      some functions may require read\/write access to files you may be using.\r\n      Of course, use those functions with care, though the instances in which\r\n      these precautions are necessary should be obvious; Ultimate-Test-Utility \r\n      does NOT want to harm your work, it\\'s here to help.\r\n\r\n    - Also, Ultimate-Test-Utility has included some example functions that\r\n      may not work correctly on your OS. This should not be an issue when\r\n      using this plugin to write your own vimscript code, only when trying the\r\n      demos. In the future, these examples may be updated to be compatible with\r\n      as many OSes and setups as possible.\r\n\r\n- Ultimate-Test-Utility provides several levels of reporting so your reports\r\n  are as detailed or minimal as you\\'d like.\r\n\r\n- Ultimate-Test-Utility allows for easy installation through Pathogen, Vundle,\r\n  or other compatible plugin managers. If you\\'re reading this, it\\'s likely\r\n  installed correctly already, but if not consult the README.md file.\r\n\r\n- Ultimate-Test-Utility is, like most vim plugins, open-source! Please feel\r\n  free to distribute, contribute, modify or spread the word.\r\n\r\n\r\n\r\nUsage                              \r\n-----\r\n\r\nUltimate-Test-Utility has a straightforward API, and is not unlike the Perl\r\ntesting suite. However, Vim\\'s lack of out-of-box OOP and our decision to\r\nmaximize compatibility (we don\\'t use other languages or CLI testing\r\nsoftware) means that Ultimate-Test-Utility does have a mild\r\nlearning-curve, but should be easy to pick for both testing veterans and\r\nfirst-timers alike.\r\n\r\n- The first section, Ultimate-Test-Utility-Quick-Start, provides a quick\r\noverview of how to use this plugin.\r\n\r\n- The second section, Ultimate-Test-Utility-Basic-Examples, shows the most\r\ncommon usage and should be enough to get you started on working on your own\r\nprojects.\r\n\r\n- The third section, Ultimate-Test-Utility-Basic-Examples, explores more\r\ncomplex usage cases and explains the interface to some of the less intuitive\r\nfunctions.\r\n\r\nThe more complex examples are available in examples.vim.\r\n\r\n\r\nQuick Start Guide                 \r\n-----------------\r\n\r\nUltimate-Test-Utility breaks down tests into two categories. Individual\r\nAssertion tests (referred to as sub-tests) which check for one specific thing,\r\nand groupings of related sub-tests (collectively referred to as a test).\r\nIt\\'s often natural to have sub-tests in a full test address different aspects\r\nand edge cases of a particular function or key mapping. Thus a plugin with 4\r\nfunctions and 1 keymapping may have 5 total \\\"tests\\\", with each \\\"test\\\"\r\nconsisting of up to dozens of \\\"sub-tests.\\\"\r\n\r\nThe basic workflow is simple.\r\n\r\n1. You MUST call UltiTestStart to tell vim that you are going into\r\n   \\\"test-mode\\\".\r\n\r\n2. You then call as many UltiAssert... sub-tests as you need.\r\n\r\n3. You then call UltiTestStop to tell vim that a particular test is over.\r\n\r\n4. You may then call UltiTestReport which will give a report of varying\r\n   detail about the success and failure of your sub-tests. Additionally, this\r\n   will report the overall success of the entire test. The degree of detail\r\n   reported is dependent on the value of g:ulti\\\\_test\\\\_verbose. See\r\n   Ultimate-Test-Utility-Config for more details.\r\n\r\n5. If you wish to execute more tests (ie. more groupds of sub-tests), you\r\n   should call UltiTestReset.\r\n\r\n6. Repeat steps 1-6 as needed.\r\n\r\n7. You may then call UltiTestFinalSummary to give a simple summary of all\r\n   the \\\"tests\\\" you have run (since you either loaded the plugin or called\r\n   UltiTestResetAll, see next step for details).\r\n\r\n8. If you wish to run another suite of \\\"tests\\\", say for a different plugin or\r\n   file, call UltiTestResetAll.\r\n\r\n9. Repeat steps 1-8 as needed.\r\n\r\nThe next section shows how to setup and run one full \\\"test\\\" on an example\r\nfunction.\r\n\r\nBasic Examples                    \r\n--------------\r\n\r\nSpecial Note: It\\'s good practice to write your tests before you write the code\r\nyou\\'re testing, but for the purpose of this tutorial, we\\'ll ignore that.\r\n\r\nExample Multiply function, takes two arguments and returns the quotient.\r\n\r\n```vim\r\nfunction! Multiply(numerator, denominator)\r\n    return a:numerator * a:denominator\r\nendfunction\r\n```\r\n\r\nExample test function that examines some basic-use cases and possible edge\r\ncases. Comments have been sprinkled in to explain a little of the API.\r\n    \r\n```vim\r\nfunction! MultiplyTestOne()\r\n    call UltiTestStart()\r\n\r\n    call UltiAssertTrue(\\'\\', Multiply(2, 2) == 4, \\'true\\')\r\n\r\n    call UltiAssertTrue(\\\"Testing 1 times 1 isn\\'t 6\\\",\r\n                \\\\ Multiply(1, 1) == 6,\r\n                \\\\ \\'false\\')\r\n\r\n    \\\" We\\'re deliberately making an incorrect test here to see what happens\r\n    call UltiAssertTrue(\\\"Testing 5 times -2 isn\\'t -10\\\",\r\n                \\\\ Multiply(5, -2) == -10,\r\n                \\\\ \\'false\\')\r\n\r\n    call UltiAssertEquals(\\'Testing Multiply(2.0, 3) == Multiply(3.0, 2)\\',\r\n                \\\\ Multiply(2.0, 3),\r\n                \\\\ Multiply(3.0, 2),\r\n                \\\\ \\'true\\')\r\n\r\n    call UltiTestStop()\r\n    call UltiTestReport()\r\nendfunction\r\n\r\n\\\" Now to run the test\r\ncall MultiplyTestOne()\r\n```\r\n\r\nThis should give something like the following as output:\r\n\r\n```vim\r\n    Sub-test 3: Failed, Testing 5 times -2 isn\\'t -10\r\n    Test 1 Results:\r\n        Expected: Not specified, Passed: 3, Failed: 1, Skipped: 0\r\n```\r\n\r\nYay, it works, let\\'s review what we did.\r\n\r\nThe calls to UltiTestStart, UltiTestStop, and UltiTestReport were covered in\r\nthe previous section and are straightforward. However, we then called the\r\nactual sub-tests themselves.\r\n\r\nEach sub-test available starts with \\'UltiAssert\\'.\r\nEach UltiAssert function has a slightly different argument signature but there\r\nare some similarities in usage.\r\n\r\n1. The first argument is a string describing the purpose of the test. Notice\r\n   this message was displayed when sub-test 3 failed. Descriptive messages\r\n   make pin-pointing problems quick, but you may provide an empty string like\r\n   we did for the first sub-test.\r\n\r\n2. Next are the arguments unique to the assertion test being run.\r\n\r\n3. The last argument is optional, and can only be the string \\'skip\\' to\r\n   indicate that you don\\'t want to run the test at this time. Notice that we\r\n   did not use this feature in any of the tests we just ran.\r\n\r\n4. The argument before \\'skip\\' (aka the last argument if you don\\'t\r\n   provide \\'skip\\'), must be either \\'true\\' or \\'false\\', indicating if\r\n   the Assertion is expected to be true or false.\r\n\r\nEssentially, each simple UltiAssert... looks like this...\r\n\r\n```vim\r\n    call UltiAssertSimple(description, ..., expected_outcome)  \\\" or\r\n    call UltiAssertSimple(description, ..., expected_outcome, \\'skip\\')\r\n```\r\n\r\nwhere the \\'...\\' is unique to whatever test you\\'re using.\r\n\r\nNote: there is no test called UltiAssertSimple or UltiAssert.... These are\r\nplace holder names.\r\n\r\nNotice that in MultiplyTestOne we used UltiAssertTrue, which took one unique\r\nargument (the result of the Multiply function call) and UltiAssertEquals which\r\ntook two unique arguments (the results of two Multiply function calls). As you\r\nmay have guessed, UltiAssertTrue simply evaluates the truthiness of its one\r\nunique argument, and UltiAssertEquals compares its two unique arguments to\r\neachother.  Most sub-tests can be written with either one of these. The\r\npresence of both of them, and the more specific assertions explained in the\r\nnext section, is merely a convenience. You should use whichever sub-tests feel\r\nthe most natural.\r\n\r\nNext Steps:\r\nYay, it works ... but it could be better. Ignoring that our function is\r\ntrivial, we deliberately made a mistake, and the usefulness of these tests is\r\nquestionable, we can still improve our test function.\r\n\r\n1. If we run our test again, it now says we\\'re on Test 2 even though this\r\n   is the same test we just ran.\r\n\r\n2. \\'Test 1\\' isn\\'t a horribly informative name in the first place.\r\n\r\n3. Though moot in this case, how do we know we tested everything we\r\n   intended? Though careful coding can eliminate this problem, in tests with\r\n   many sub-tests, especially in more complicated plugins, we may want an\r\n   extra level of confidence.\r\n\r\nIt turns out we can fix all of these problems with minimal effort.\r\n\r\n```vim\r\nfunction! MultiplyTestTwo()\r\n    call UltiTestReset()\r\n    call UltiTestStart(\\'Testing the Multiply Function\\', 4)\r\n\r\n    call UltiAssertTrue(\\'\\', Multiply(2, 2) == 4, \\'true\\')\r\n\r\n    call UltiAssertTrue(\\\"Testing 1 times 1 isn\\'t 6\\\",\r\n                \\\\ Multiply(1, 1) == 6,\r\n                \\\\ \\'false\\')\r\n\r\n    \\\" We\\'re deliberately making an incorrect test here to see what happens\r\n    call UltiAssertTrue(\\\"Testing 5 times -2 isn\\'t -10\\\",\r\n                \\\\ Multiply(5, -2) == -10,\r\n                \\\\ \\'false\\')\r\n\r\n    call UltiAssertEquals(\\'Testing Multiply(2.0, 3) == Multiply(3.0, 2)\\',\r\n                \\\\ Multiply(2.0, 3),\r\n                \\\\ Multiply(3.0, 2),\r\n                \\\\ \\'true\\',\r\n                \\\\ \\'skip\\')\r\n\r\n    call UltiTestStop()\r\n    call UltiTestReport()\r\nendfunction\r\n\r\n\\\" Now to run the test\r\ncall MultiplyTestOne()\r\n```\r\n\r\nThis should give something like the following as output:\r\n\r\n```vim\r\nSub-test 3: Failed, Testing 5 times -2 isn\\'t -10\r\nTest 1 \\'Testing the Multiply Function\\' Results:\r\n    Expected: 4, Passed: 2, Failed: 1, Skipped: 1\r\n```\r\n\r\nTwo quick points, and we can move on to more advanced usage.\r\n\r\n1. The call to UltiTestReset tells vim to reset our sub-test counters so\r\n   that we could have been placed at the end of the function instead of the\r\n   beginning. However, as we\\'ll see, this call should usually be made outside\r\n   of any one test, and rather after or before running a suite of tests.\r\n\r\n2. The call to UltiTestStart can take two optional arguments in any order.\r\n   It can take a string that should describe how the sub-tests are related,\r\n   and an integer that tells the test how many sub-tests to expect.\r\n\r\n3. The last sub-test has the \\'skip\\' argument added, just to show how to use\r\n   it. Note that adding \\'skip\\' only prevents the result from being factored in\r\n   the testing facility, it won\\'t prevent any errors in the other arguments\r\n   from causing problems.\r\n\r\n\r\nExtended Examples                \r\n-----------------\r\n\r\nLet\\'s broaden our look at this plugin be testing some more complicated\r\nplugins\/functions and integrating several tests into one suite. Assume all\r\nreferences to MultiplyTest() refer to the MultiplyTestTwo() function from the\r\nprevious section.\r\n\r\nSpecial Note: It\\'s good practice to write your tests before you write the code\r\nyou\\'re testing, but for the purpose of this tutorial, we\\'ll ignore that.\r\n\r\nFirst let\\'s write two more functions and add a keymapping for one of them.\r\n\r\nThe first is a slightly trickier function that echos the quotient of two\r\nnumbers rather than merely returns them. Also, divide by zero exceptions may\r\nbe thrown and we\\'ll show how to deal with that.\r\n\r\n```vim\r\nfunction! Divide(numerator, denominator)\r\n    if a:denominator == 0\r\n        throw \\\"Divide by zero\\\"\r\n    endif\r\n    echo (a:numerator \/ a:denominator)\r\nendfunction\r\n```\r\n\r\nThe next is a vim function that inserts the word \\\"Hello\\\" into the current\r\nbuffer. For convenience, we\\'ll also add a helper function that adds a\r\nkeymapping for this function.\r\n\r\n```vim\r\nfunction! InsertHello()\r\n    execute \\'normal! iHello\\'\r\nendfunction\r\n\r\nfunction! NewMapping()\r\n    nnoremap <silent> <leader>S :call InsertHello()<cr>\r\nendfunction\r\n```\r\n\r\n\r\nOk, now let\\'s write those tests.\r\n\r\n```vim\r\nfunction! TestDivide()\r\n    call UltiTestStart(\\\"Divide Tests\\\", 5)\r\n    \r\n    \\\" Output tests\r\n    call UltiAssertInOutput(\\'6 \/ 2 == 3\\', \\'Divide\\', [6, 2], \\'3\\', \\'true\\')\r\n    call UltiAssertInOutput(\\\"1 \/ 3 == 0 (\\'Testing Int Division\\')\\\",\r\n                \\\\ \\'Divide\\', [1, 3], \\'6\\', \\'false\\')\r\n\r\n    \\\" Exception tests\r\n    call UltiAssertException(\\\"Throws divide by zero error\\\",\r\n                \\\\ \\'Divide by zero\\', \\'Divide\\', [4, 0], \\'true\\')\r\n    call UltiAssertException(\\\"Doesn\\'t throw divide by zero error\\\",\r\n                \\\\ \\'Divide by zero\\', \\'Divide\\', [4, 2], \\'false\\')\r\n    \\\" For variety, use a variable for the function name\r\n    let l:fx = \\'Divide\\'\r\n    call UltiAssertException(\\\"Complains about arguments\\\",\r\n                \\\\ \\'Not enough arguments\\', l:fx, [], \\'true\\')\r\n\r\n    call UltiTestStop()\r\n    call UltiTestReport()\r\nendfunction\r\n```\r\n\r\nNotes:\r\nUltiAssertInOuput and UltiAssertException both have more complicated\r\ninterfaces but share similarities with the previous UltiAssert functions\r\nand with each other.\r\n\r\n1. Like the others, the first argument is a descriptive name, and the last\r\n   two arguments are the expection (either \\\"true\\\" or \\\"false\\\") and an\r\n   optional \\\"skip\\\" string to indicate the test is skipped.\r\n2. The second argument is a variable or raw string with the name of the\r\n   function to be tested. The name should NOT have parentheses or any\r\n   arguments.\r\n3. The third argument is a List of all arguments you would like to be\r\n   passed to the function you\\'re testing. If no arguments are to be passed,\r\n   you must provide an empty list \\'[]\\'.\r\n4. The fourth argument is a string or regex specific to the UltiAssert test\r\n   you\\'re using. For UltiAsserException, it should be the exception you\r\n   expect to be thrown. For UltiAssertInOutput it should be the string\r\n   you expect to be in the output.\r\n\r\nIn summary, each simple UltiAssert... looks like this...\r\n\r\n```vim\r\ncall UltiAssertSimple(desc, ..., expected_outcome)  \\\" or\r\ncall UltiAssertSimple(desc, ..., expected_outcome, \\'skip\\')\r\n```\r\nwhere the \\'...\\' is unique to whatever test you\\'re using.\r\n\r\nEach complex UltiAssert... looks like this.\r\n\r\n```vim\r\ncall UltiAssertComplex(desc, fx, arguments, string, expected_outcome)  \\\" or\r\ncall UltiAssertComplex(desc, fx, arguments, string, expected_outcome, \\'skip\\')\r\n```\r\n\r\nNote: there is no test called UltiAssertSimple or UltiAssert... or\r\nUltiAssertComplex. These are place holder names only.\r\n\r\n\r\nThis next test is a bit of a cheat in that it tests the InsertHello() function\r\nvia the keymapping where these tests should probably be separate. Also, the\r\nuse of the mapleader variable can be troublesome because the mapping is always\r\nwhatever the value of the leader key at the time it was set. If this doesn\\'t\r\nmake sense to you, just know to be careful if you use it.\r\n\r\n```vim\r\nfunction! TestInsertHello()\r\n    call UltiTestStart(\\'Testing Command Mapping and Text Insertion\\', 3)\r\n\r\n    if exists(\\'mapleader\\')\r\n        let leader = mapleader\r\n    else\r\n        let leader = \\'\\\\\\'\r\n    endif\r\n\r\n    \\\" Make the new mapping\r\n    call NewMapping()\r\n\r\n    let l:fx = \\'Hello\\'\r\n    call UltiAssertInBuffer(\\'Testing for \\\"Hello\\\" absence before execute\\',\r\n                \\\\ \\'Hello\\', \\'false\\')\r\n\r\n    execute \\'normal! \\' . leader . \\'S\\'\r\n    call UltiAssertInBuffer(\\'Testing for \\\"Hello\\\" absence after normal!\\',\r\n                \\\\ \\'Hello\\', \\'false\\')\r\n\r\n    execute \\'normal \\' . leader . \\'S\\'\r\n    call UltiAssertInBuffer(\\'Testing for \\\"Hello World\\\" presence after normal\\',\r\n                \\\\ \\'Hello\\', \\'true\\')\r\n    \r\n    \\\" Clean up the text that was just inserted. Not necessary for the\r\n    \\\" test though.\r\n    execute \\\"s\/Hello\/\/\\\"\r\n\r\n    call UltiTestStop()\r\n    call UltiTestReport()\r\nendfunction\r\n```\r\n\r\nNotes\r\n1. We specified there should be 3 sub-tests run and given the test a\r\n   description.\r\n\r\n2. We have not called UltiTestReset yet.\r\n\r\n3. Now that we\\'re executing more complicated functions, we need\r\n   to be careful that we\\'re not polluting the current buffer with side-effects\r\n   from our testing. In particular beware of testing UltiAssertInBuffer\r\n   sub-tests in the buffer where you wrote the test. See if you can figure out\r\n   why.\r\n\r\n4. UltiAssertInBuffer has an almost identical interface to UltiAssertTrue.\r\n\r\n\r\nFinally, let\\'s organize these two tests into a full suite with the\r\nMultiplyTest from before. Take out the call to UltiTestReset in the\r\nMultiplyTest.\r\n\r\n```vim\r\nfunction! AllTests()\r\n    call UltiTestReset()         \\\" Clears residual junk\r\n\r\n    call MultiplyTest()\r\n    call TestDivide()\r\n    call TestInsertHello()\r\n\r\n    call UltiTestFinalSummary()  \\\" Brief summary of all three tests\r\n    call UltiTestResetAll()      \\\" Clears everything\r\nendfunction\r\n```\r\n\r\nNow to call the whole thing...\r\n\r\n```vim\r\ncall AllTests()\r\n```\r\n\r\nRemember that because our TestInsertHello() tests for the presence and absence\r\nof the string \\'Hello\\' in the buffer it\\'s executed in, it\\'s best to run these\r\ntests in an empty buffer. So it\\'s probably best to source these functions,\r\nswitch to a new buffer, and then call AllTests().\r\n\r\nYou can change the output by setting one of these three values before you call\r\nthe function.\r\n\r\n```vim\r\nlet g:ulti_test_verbose = 0    \\\" or\r\nlet g:ulti_test_verbose = 1    \\\" or\r\nlet g:ulti_test_verbose = 2\r\n```\r\n\r\nAssuming you left it at 1, you should get ...\r\n\r\n```vim\r\nSub-test 3: Failed, Testing 5 times -2 isn\\'t -10\r\nTest 1 Results:\r\n    Expected: 4, Passed: 3, Failed: 1, Skipped: 0\r\n\r\nTest 2 \\'Divide Test\\' Results\r\n    Expected: 5, Passed: 5, Failed: 0, Skipped: 0\r\n\r\nTest 3 \\'Testing Command Mapping and Text Insertion\\' Results\r\n    Expected: 3, Passed: 3, Failed: 0, Skipped: 0\r\n\r\n1 test(s) failed.\r\n```\r\n","install_details":"Installation is quite simple and does not require any other plugins or languages\r\nto be installed.\r\n\r\n### Pathogen\r\n\r\n```bash\r\ncd ~\/.vim\/bundle\r\ngit clone https:\/\/github.com\/biskark\/vim-ultimate-colorscheme-utility.git\r\n```\r\nThat's enough to get the latest stable release, but if you'd like to keep up-to-date with the latest developments, continue with...\r\n\r\ncd ~\/.vim\/bundle\/vim-ultimate-test-utility\/\r\ngit checkout latest\r\n\r\n\r\n### From archive\r\n1. download archive\r\n2. unzip archive into .vim","5":"Installation is quite simple and does not require any other plugins or languages\r\nto be installed.\r\n\r\n### Pathogen\r\n\r\n```bash\r\ncd ~\/.vim\/bundle\r\ngit clone https:\/\/github.com\/biskark\/vim-ultimate-colorscheme-utility.git\r\n```\r\nThat's enough to get the latest stable release, but if you'd like to keep up-to-date with the latest developments, continue with...\r\n\r\ncd ~\/.vim\/bundle\/vim-ultimate-test-utility\/\r\ngit checkout latest\r\n\r\n\r\n### From archive\r\n1. download archive\r\n2. unzip archive into .vim","first_name":"Kevin","6":"Kevin","last_name":"Biskar","7":"Biskar","releases":[{"0":"4724","vim_version":"7.0","1":"7.0","script_version":"0.0.0","2":"0.0.0","version_comment":"Initial upload","3":"Initial upload","package":"vim-ultimate-test-utility-v0.0.0.tar","4":"vim-ultimate-test-utility-v0.0.0.tar","src_id":"20812","5":"20812","creation_date":"1379380715","6":"1379380715"}]},"4723":{"script_id":"4723","0":"4723","script_name":"fontdetect","1":"fontdetect","script_type":"utility","2":"utility","summary":"Detect installed fonts","3":"Detect installed fonts","description":"fontdetect helps Vim detect which fonts are installed on the system.\r\nIt works around limitations in Vim's getfontname() function.\r\n\r\nFor example (using GTK2 GUI)::\r\n\r\n    if fontdetect#hasFontFamily(\"DejaVu Sans Mono\")\r\n        let &guifont = \"DejaVu Sans Mono 14\"\r\n    endif\r\n\r\nAt present, the following platforms are supported:\r\n\r\n- Linux (using GTK2 GUI)\r\n- Windows\r\n- Mac OS X\r\n\r\nSee documentation in doc\/fontdetect.txt for installation instructions.\r\n\r\nDeveloped by Michael Henry (vim at drmikehenry.com).\r\n\r\nDistributed under Vim's license.\r\n\r\nGit repository:   https:\/\/github.com\/drmikehenry\/vim-fontdetect\r\n","4":"fontdetect helps Vim detect which fonts are installed on the system.\r\nIt works around limitations in Vim's getfontname() function.\r\n\r\nFor example (using GTK2 GUI)::\r\n\r\n    if fontdetect#hasFontFamily(\"DejaVu Sans Mono\")\r\n        let &guifont = \"DejaVu Sans Mono 14\"\r\n    endif\r\n\r\nAt present, the following platforms are supported:\r\n\r\n- Linux (using GTK2 GUI)\r\n- Windows\r\n- Mac OS X\r\n\r\nSee documentation in doc\/fontdetect.txt for installation instructions.\r\n\r\nDeveloped by Michael Henry (vim at drmikehenry.com).\r\n\r\nDistributed under Vim's license.\r\n\r\nGit repository:   https:\/\/github.com\/drmikehenry\/vim-fontdetect\r\n","install_details":"","5":"","first_name":"Michael","6":"Michael","last_name":"Henry","7":"Henry","releases":[{"0":"4723","vim_version":"7.0","1":"7.0","script_version":"0.3.0","2":"0.3.0","version_comment":"Support for Python 3 in addition to Python 2 on OS X (thanks to Mike Haig).","3":"Support for Python 3 in addition to Python 2 on OS X (thanks to Mike Haig).","package":"fontdetect-0.3.0.zip","4":"fontdetect-0.3.0.zip","src_id":"26253","5":"26253","creation_date":"1540700763","6":"1540700763"},{"0":"4723","vim_version":"7.0","1":"7.0","script_version":"0.2.2","2":"0.2.2","version_comment":"Documentation reorganization.","3":"Documentation reorganization.","package":"fontdetect-0.2.2.zip","4":"fontdetect-0.2.2.zip","src_id":"20877","5":"20877","creation_date":"1380818229","6":"1380818229"},{"0":"4723","vim_version":"7.0","1":"7.0","script_version":"0.2.1","2":"0.2.1","version_comment":"Restore cpoptions correctly.","3":"Restore cpoptions correctly.","package":"vim-fontdetect-0.2.1.zip","4":"vim-fontdetect-0.2.1.zip","src_id":"20831","5":"20831","creation_date":"1379931055","6":"1379931055"},{"0":"4723","vim_version":"7.0","1":"7.0","script_version":"0.2.0","2":"0.2.0","version_comment":"Initial upload","3":"Initial upload","package":"vim-fontdetect-0.2.0.zip","4":"vim-fontdetect-0.2.0.zip","src_id":"20810","5":"20810","creation_date":"1379376931","6":"1379376931"}]},"4722":{"script_id":"4722","0":"4722","script_name":"DuplicateWrite","1":"DuplicateWrite","script_type":"utility","2":"utility","summary":" Cascade the writing of a file to another location.","3":" Cascade the writing of a file to another location.","description":"DESCRIPTION\r\nThough you should use scripts for automated deployment and version control for\r\nmerges, sometimes, you need to quickly duplicate a file to another file system\r\nlocation whenever it is changed.\r\nThis plugin defines a :DuplicateWrite command that sets up additional\r\n:write targets. From then on, whenever you save that buffer, the write is\r\ncascaded to the additional files. Thus, when editing a script in your project\r\ndirectory, you can have it immediately (on only on demand, with [!]) copied to\r\nthe install directory that is in the PATH. Or, with the help of the netrw\r\nplugin, you can even automatically upload a locally edited HTML page to the\r\nremote web server.\r\n\r\nHOW IT WORKS\r\nThe plugin hooks into the BufWritePost event to issue additional :write\r\ncommands.\r\n\r\nRELATED WORKS\r\n- The FileSync plugin (vimscript #5064) can automatically sync files or\r\n  directory trees on write, using a Vim command like !cp, netrw plugin, or\r\n  custom function.\r\n- The mirror.vim plugin (vimscript #5204) needs a mirror configuration, and\r\n  then provides custom commands to open, diff, push, etc. mirrored files.\r\n\r\nUSAGE\r\n:DuplicateWrite[!] [++opt] [+cmd] [-cmd] {file}|{dirspec} [...]\r\n                        Create a cascaded write of the current buffer to the\r\n                        specified {file}, or to a file with the same filename\r\n                        located in {dirspec}. From now on, whenever the buffer\r\n                        is |:w|ritten, it will also be persisted to the passed\r\n                        location. (Until you :bdelete it.)\r\n                        With [!], duplication only happens with forced\r\n                        :write!, not with :write. This is useful if the\r\n                        duplication target is on a slow networked filesystem\r\n                        or if a file write triggers other costly actions\r\n                        (like a service restart after a config update).\r\n                        [++opt] is passed to :write. An optional [+cmd] is\r\n                        executed before the write; likewise, [-cmd] is\r\n                        executed after the write; the degenerate [-] will\r\n                        :undo any changes to the buffer done by [+cmd].\r\n                        In the {cmd}s, spaces and also special characters\r\n                        (cmdline-special) like % and <cword> must be\r\n                        escaped. The plugin supports a special <tfile>\r\n                        identifer that gets replaced with the duplicated\r\n                        target file.\r\n\r\n                        You can issue the command multiple times (with\r\n                        different {file} targets) for a buffer to add cascades\r\n                        to several concurrent locations.\r\n\r\n:DuplicateWriteOff      Turn off all cascaded writes for the current buffer.\r\n\r\n:DuplicateWriteList     List the cascaded write target(s) for the current\r\n                        buffer.\r\n\r\n:DuplicateWriteListAll  List the cascaded write target(s) for all open\r\n                        buffers that have any. The buffers are listed with\r\n                        their number followed by the name; the targets are\r\n                        listed in the following, indented lines, for example:\r\n                        4  \"DuplicateWrite.txt\" ->\r\n                                \"C:\\temp\\DuplicateWrite.txt\"\r\n                                \"X:\\backup.txt\"","4":"DESCRIPTION\r\nThough you should use scripts for automated deployment and version control for\r\nmerges, sometimes, you need to quickly duplicate a file to another file system\r\nlocation whenever it is changed.\r\nThis plugin defines a :DuplicateWrite command that sets up additional\r\n:write targets. From then on, whenever you save that buffer, the write is\r\ncascaded to the additional files. Thus, when editing a script in your project\r\ndirectory, you can have it immediately (on only on demand, with [!]) copied to\r\nthe install directory that is in the PATH. Or, with the help of the netrw\r\nplugin, you can even automatically upload a locally edited HTML page to the\r\nremote web server.\r\n\r\nHOW IT WORKS\r\nThe plugin hooks into the BufWritePost event to issue additional :write\r\ncommands.\r\n\r\nRELATED WORKS\r\n- The FileSync plugin (vimscript #5064) can automatically sync files or\r\n  directory trees on write, using a Vim command like !cp, netrw plugin, or\r\n  custom function.\r\n- The mirror.vim plugin (vimscript #5204) needs a mirror configuration, and\r\n  then provides custom commands to open, diff, push, etc. mirrored files.\r\n\r\nUSAGE\r\n:DuplicateWrite[!] [++opt] [+cmd] [-cmd] {file}|{dirspec} [...]\r\n                        Create a cascaded write of the current buffer to the\r\n                        specified {file}, or to a file with the same filename\r\n                        located in {dirspec}. From now on, whenever the buffer\r\n                        is |:w|ritten, it will also be persisted to the passed\r\n                        location. (Until you :bdelete it.)\r\n                        With [!], duplication only happens with forced\r\n                        :write!, not with :write. This is useful if the\r\n                        duplication target is on a slow networked filesystem\r\n                        or if a file write triggers other costly actions\r\n                        (like a service restart after a config update).\r\n                        [++opt] is passed to :write. An optional [+cmd] is\r\n                        executed before the write; likewise, [-cmd] is\r\n                        executed after the write; the degenerate [-] will\r\n                        :undo any changes to the buffer done by [+cmd].\r\n                        In the {cmd}s, spaces and also special characters\r\n                        (cmdline-special) like % and <cword> must be\r\n                        escaped. The plugin supports a special <tfile>\r\n                        identifer that gets replaced with the duplicated\r\n                        target file.\r\n\r\n                        You can issue the command multiple times (with\r\n                        different {file} targets) for a buffer to add cascades\r\n                        to several concurrent locations.\r\n\r\n:DuplicateWriteOff      Turn off all cascaded writes for the current buffer.\r\n\r\n:DuplicateWriteList     List the cascaded write target(s) for the current\r\n                        buffer.\r\n\r\n:DuplicateWriteListAll  List the cascaded write target(s) for all open\r\n                        buffers that have any. The buffers are listed with\r\n                        their number followed by the name; the targets are\r\n                        listed in the following, indented lines, for example:\r\n                        4  \"DuplicateWrite.txt\" ->\r\n                                \"C:\\temp\\DuplicateWrite.txt\"\r\n                                \"X:\\backup.txt\"","install_details":"INSTALLATION\r\nThe code is hosted in a Git repo at\r\n    https:\/\/github.com\/inkarkat\/vim-DuplicateWrite\r\nYou can use your favorite plugin manager, or \"git clone\" into a directory used\r\nfor Vim packages. Releases are on the \"stable\" branch, the latest unstable\r\ndevelopment snapshot on \"master\".\r\n\r\nThis script is also packaged as a vimball. If you have the \"gunzip\"\r\ndecompressor in your PATH, simply edit the *.vmb.gz package in Vim; otherwise,\r\ndecompress the archive first, e.g. using WinZip. Inside Vim, install by\r\nsourcing the vimball or via the :UseVimball command.\r\n    vim DuplicateWrite*.vmb.gz\r\n    :so %\r\nTo uninstall, use the :RmVimball command.\r\n\r\nDEPENDENCIES\r\n- Requires Vim 7.0 or higher.\r\n- Requires the ingo-library.vim plugin (vimscript #4433), version 1.025 or\r\n  higher.\r\n\r\nCONFIGURATION\r\nFor a permanent configuration, put the following commands into your vimrc:\r\n\r\nTo avoid giving an argument to :DuplicateWrite, you can define a List of\r\n{source-glob}, {argument-object} pairs: The part of the buffer's filespec that\r\nmatches {source-glob} will then be replaced by {argument-object}.pathspec to\r\nyield the target:\r\n    let g:DuplicateWrite_DefaultMirrors = [\r\n    \\   ['D:\\project\\foo', {'pathspec': 'X:\\foo'}],\r\n    \\   ['**\\src\\**', {\r\n    \\                   'pathspec': 'E:\\deploy',\r\n    \\                   'bang': 0,\r\n    \\                   'opt': '++ff=dos',\r\n    \\                   'preCmd': '%s\/Copyright: \\zsXXXX\/Acme Corp\/e,\r\n    \\                   'postCmd': 'UNDO'\r\n    \\                 }]\r\n    \\]\r\nThis would for example duplicate a file D:\\project\\foo\\bin\\zap.cmd to\r\nX:\\foo\\bin\\zap.cmd and any file anywhere inside a src\/ directory directly to\r\nE:\\deploy when you execute :DuplicateWrite. A buffer-local configuration\r\noverrides the global one. All matching {source-glob} are processed, so if you\r\nneed to duplicate to multiple locations, define several same {source-glob}s.\r\n\r\nThe duplicate writes themselves also trigger |autocmd|s; we need this nesting\r\nto let plugins like netrw interfere and handle special (remote) filesystem\r\nlocations. However, other plugins may also be triggered, and that may be\r\nundesirable (for example, you don't want to trigger syntax checking on the\r\nduplicates, or add them to a MRU list in Vim). Because of this, the plugin\r\nignores certain events (via 'eventignore') during its execution:\r\n    let g:DuplicateWrite_EventIgnore = 'BufWritePre,BufWritePost'\r\n\r\nEspecially when using default mirrors, the target directory for the duplicated\r\nwrite may not exist yet. The following variable defines the plugin's behavior\r\nin that case; either \"no\", \"yes\", or \"ask\":\r\n    let g:DuplicateWrite_CreateNonExistingTargetDirectory = 'ask'\r\n\r\nRemote target directories (e.g. netrw URLs like scp:\/\/path\/to\/file) cannot\r\nbe checked for existence; in order to be able to write to them (and skip the\r\nuseless target directory check), certain dirspecs (also local ones) can be\r\nexempted. Any dirspec that matches the regular expression not checked:\r\n    let g:DuplicateWrite_TargetDirectoryCheckIgnorePattern = '^\\a\\+:\/\/'\r\n\r\nINTEGRATION\r\nThe filespecs of the cascaded write targets are stored in the buffer-local\r\nList variable b:DuplicateWrite. You can use its existence \/ number of elements\r\nto determine whether \/ how many duplications are configured, and use this e.g.\r\nin a custom 'statusline'. To programatically add duplicate writes, use the\r\nDuplicateWrite#Add() function.","5":"INSTALLATION\r\nThe code is hosted in a Git repo at\r\n    https:\/\/github.com\/inkarkat\/vim-DuplicateWrite\r\nYou can use your favorite plugin manager, or \"git clone\" into a directory used\r\nfor Vim packages. Releases are on the \"stable\" branch, the latest unstable\r\ndevelopment snapshot on \"master\".\r\n\r\nThis script is also packaged as a vimball. If you have the \"gunzip\"\r\ndecompressor in your PATH, simply edit the *.vmb.gz package in Vim; otherwise,\r\ndecompress the archive first, e.g. using WinZip. Inside Vim, install by\r\nsourcing the vimball or via the :UseVimball command.\r\n    vim DuplicateWrite*.vmb.gz\r\n    :so %\r\nTo uninstall, use the :RmVimball command.\r\n\r\nDEPENDENCIES\r\n- Requires Vim 7.0 or higher.\r\n- Requires the ingo-library.vim plugin (vimscript #4433), version 1.025 or\r\n  higher.\r\n\r\nCONFIGURATION\r\nFor a permanent configuration, put the following commands into your vimrc:\r\n\r\nTo avoid giving an argument to :DuplicateWrite, you can define a List of\r\n{source-glob}, {argument-object} pairs: The part of the buffer's filespec that\r\nmatches {source-glob} will then be replaced by {argument-object}.pathspec to\r\nyield the target:\r\n    let g:DuplicateWrite_DefaultMirrors = [\r\n    \\   ['D:\\project\\foo', {'pathspec': 'X:\\foo'}],\r\n    \\   ['**\\src\\**', {\r\n    \\                   'pathspec': 'E:\\deploy',\r\n    \\                   'bang': 0,\r\n    \\                   'opt': '++ff=dos',\r\n    \\                   'preCmd': '%s\/Copyright: \\zsXXXX\/Acme Corp\/e,\r\n    \\                   'postCmd': 'UNDO'\r\n    \\                 }]\r\n    \\]\r\nThis would for example duplicate a file D:\\project\\foo\\bin\\zap.cmd to\r\nX:\\foo\\bin\\zap.cmd and any file anywhere inside a src\/ directory directly to\r\nE:\\deploy when you execute :DuplicateWrite. A buffer-local configuration\r\noverrides the global one. All matching {source-glob} are processed, so if you\r\nneed to duplicate to multiple locations, define several same {source-glob}s.\r\n\r\nThe duplicate writes themselves also trigger |autocmd|s; we need this nesting\r\nto let plugins like netrw interfere and handle special (remote) filesystem\r\nlocations. However, other plugins may also be triggered, and that may be\r\nundesirable (for example, you don't want to trigger syntax checking on the\r\nduplicates, or add them to a MRU list in Vim). Because of this, the plugin\r\nignores certain events (via 'eventignore') during its execution:\r\n    let g:DuplicateWrite_EventIgnore = 'BufWritePre,BufWritePost'\r\n\r\nEspecially when using default mirrors, the target directory for the duplicated\r\nwrite may not exist yet. The following variable defines the plugin's behavior\r\nin that case; either \"no\", \"yes\", or \"ask\":\r\n    let g:DuplicateWrite_CreateNonExistingTargetDirectory = 'ask'\r\n\r\nRemote target directories (e.g. netrw URLs like scp:\/\/path\/to\/file) cannot\r\nbe checked for existence; in order to be able to write to them (and skip the\r\nuseless target directory check), certain dirspecs (also local ones) can be\r\nexempted. Any dirspec that matches the regular expression not checked:\r\n    let g:DuplicateWrite_TargetDirectoryCheckIgnorePattern = '^\\a\\+:\/\/'\r\n\r\nINTEGRATION\r\nThe filespecs of the cascaded write targets are stored in the buffer-local\r\nList variable b:DuplicateWrite. You can use its existence \/ number of elements\r\nto determine whether \/ how many duplications are configured, and use this e.g.\r\nin a custom 'statusline'. To programatically add duplicate writes, use the\r\nDuplicateWrite#Add() function.","first_name":"Ingo","6":"Ingo","last_name":"Karkat","7":"Karkat","releases":[{"0":"4722","vim_version":"7.0","1":"7.0","script_version":"2.01","2":"2.01","version_comment":"- The target directory check interferes with remote (netrw) targets. Add g:DuplicateWrite_TargetDirectoryCheckIgnorePattern configuration that skips URIs by default.\r\n- BUG: A netrw target (e.g. scp:\/\/hostname\/path) causes the autocmds to get lost.\r\n- FIX: Cleanup of autocmds may not apply after :bdelete.","3":"- The target directory check interferes with remote (netrw) targets. Add g:DuplicateWrite_TargetDirectoryCheckIgnorePattern configuration that skips URIs by default.\r\n- BUG: A netrw target (e.g. scp:\/\/hostname\/path) causes the autocmds to get lost.\r\n- FIX: Cleanup of autocmds may not apply after :bdelete.","package":"DuplicateWrite-2.01.vmb.gz","4":"DuplicateWrite-2.01.vmb.gz","src_id":"26090","5":"26090","creation_date":"1530335463","6":"1530335463"},{"0":"4722","vim_version":"7.0","1":"7.0","script_version":"2.00","2":"2.00","version_comment":"- ENH: Support passing [++opt] [+cmd] [-cmd] before filespecs, and allow multiple filespec arguments to :DuplicateWrite.\r\n- ENH: Add default mirror configuration in g:DuplicateWrite_DefaultMirrors.\r\n- Use nested autocmds, but allow to suppress certain events via g:DuplicateWrite_EventIgnore.\r\n- ENH: Check for existence of target directory, and react according to g:DuplicateWrite_CreateNonExistingTargetDirectory.\r\n- ENH: Support duplicate write only with :write when using :DuplicateWrite! during definition. *** You need to update to ingo-library (vimscript #4433) version 1.025! ***","3":"- ENH: Support passing [++opt] [+cmd] [-cmd] before filespecs, and allow multiple filespec arguments to :DuplicateWrite.\r\n- ENH: Add default mirror configuration in g:DuplicateWrite_DefaultMirrors.\r\n- Use nested autocmds, but allow to suppress certain events via g:DuplicateWrite_EventIgnore.\r\n- ENH: Check for existence of target directory, and react according to g:DuplicateWrite_CreateNonExistingTargetDirectory.\r\n- ENH: Support duplicate write only with :write when using :DuplicateWrite! during definition. *** You need to update to ingo-library (vimscript #4433) version 1.025! ***","package":"DuplicateWrite-2.00.vmb.gz","4":"DuplicateWrite-2.00.vmb.gz","src_id":"24467","5":"24467","creation_date":"1472030267","6":"1472030267"},{"0":"4722","vim_version":"7.0","1":"7.0","script_version":"1.01","2":"1.01","version_comment":"- FIX: Use full absolute path and normalize to be immune against changes in CWD.\r\n- *** You need to update to ingo-library (vimscript #4433) version 1.013! ***","3":"- FIX: Use full absolute path and normalize to be immune against changes in CWD.\r\n- *** You need to update to ingo-library (vimscript #4433) version 1.013! ***","package":"DuplicateWrite-1.01.vmb.gz","4":"DuplicateWrite-1.01.vmb.gz","src_id":"20800","5":"20800","creation_date":"1379102729","6":"1379102729"},{"0":"4722","vim_version":"7.0","1":"7.0","script_version":"1.00","2":"1.00","version_comment":"Initial upload","3":"Initial upload","package":"DuplicateWrite-1.00.vmb.gz","4":"DuplicateWrite-1.00.vmb.gz","src_id":"20798","5":"20798","creation_date":"1379099145","6":"1379099145"}]},"4721":{"script_id":"4721","0":"4721","script_name":"vim-polyglot","1":"vim-polyglot","script_type":"syntax","2":"syntax","summary":"A collection of language packs for Vim.","3":"A collection of language packs for Vim.","description":"\r\nA solid yet lightweight language pack for Vim.\r\n\r\nPlease visit source repository for installation instructions and releases in .zip format.\r\nI'll try to post here updates only for major releases, though.\r\n\r\nhttps:\/\/github.com\/sheerun\/vim-polyglot","4":"\r\nA solid yet lightweight language pack for Vim.\r\n\r\nPlease visit source repository for installation instructions and releases in .zip format.\r\nI'll try to post here updates only for major releases, though.\r\n\r\nhttps:\/\/github.com\/sheerun\/vim-polyglot","install_details":"\r\n1. Install pathogen, Vundle or NeoBundle package manager.\r\n2. Use this repository as submodule or package.\r\n\r\nOptionally download one of the releases and unpack it directly under ~\/.vim directory.","5":"\r\n1. Install pathogen, Vundle or NeoBundle package manager.\r\n2. Use this repository as submodule or package.\r\n\r\nOptionally download one of the releases and unpack it directly under ~\/.vim directory.","first_name":"Adam","6":"Adam","last_name":"Stankiewicz","7":"Stankiewicz","releases":[{"0":"4721","vim_version":"7.0","1":"7.0","script_version":"v1.8.0","2":"v1.8.0","version_comment":"New languages, upgrades, fixes.","3":"New languages, upgrades, fixes.","package":"vim-polyglot.zip","4":"vim-polyglot.zip","src_id":"21774","5":"21774","creation_date":"1397521249","6":"1397521249"},{"0":"4721","vim_version":"7.0","1":"7.0","script_version":"v1.5.3","2":"v1.5.3","version_comment":"Major update","3":"Major update","package":"vim-polyglot.zip","4":"vim-polyglot.zip","src_id":"21596","5":"21596","creation_date":"1394495125","6":"1394495125"},{"0":"4721","vim_version":"7.0","1":"7.0","script_version":"v1.4.0","2":"v1.4.0","version_comment":"- add support for dockerfile, rust, typescript, perl\r\n- tested automatically and reviewed visually\r\n- language packs updated","3":"- add support for dockerfile, rust, typescript, perl\r\n- tested automatically and reviewed visually\r\n- language packs updated","package":"vim-polyglot.zip","4":"vim-polyglot.zip","src_id":"20852","5":"20852","creation_date":"1380194655","6":"1380194655"},{"0":"4721","vim_version":"7.0","1":"7.0","script_version":"v1.3.1","2":"v1.3.1","version_comment":"- fix latex, switching to LaTeX-Box-Team\/LaTeX-Box\r\n- fix erlang, switching to oscarh\/vimerl\r\n- properly detect rspec syntax (switch to own fork of rspec,vim)\r\n- remove bundler package, as it provides only compiler, not syntax","3":"- fix latex, switching to LaTeX-Box-Team\/LaTeX-Box\r\n- fix erlang, switching to oscarh\/vimerl\r\n- properly detect rspec syntax (switch to own fork of rspec,vim)\r\n- remove bundler package, as it provides only compiler, not syntax","package":"vim-polyglot.zip","4":"vim-polyglot.zip","src_id":"20811","5":"20811","creation_date":"1379379196","6":"1379379196"}]},"4720":{"script_id":"4720","0":"4720","script_name":"vim-django-i18n","1":"vim-django-i18n","script_type":"ftplugin","2":"ftplugin","summary":"transform text to django i18n format","3":"transform text to django i18n format","description":"django i18n","4":"django i18n","install_details":"download to .vim\/plugins","5":"download to .vim\/plugins","first_name":"hello","6":"hello","last_name":"world","7":"world","releases":[{"0":"4720","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"vim-django-i18n-master.zip","4":"vim-django-i18n-master.zip","src_id":"20794","5":"20794","creation_date":"1379041628","6":"1379041628"}]},"4719":{"script_id":"4719","0":"4719","script_name":"Yankitute","1":"Yankitute","script_type":"utility","2":"utility","summary":"Regex powered yank+substitute","3":"Regex powered yank+substitute","description":"GitHub repository: https:\/\/github.com\/idanarye\/vim-yankitute\r\n\r\nYankitute combines the yank and substitute Vim commands into one. Like substitute, it searches for a pattern in the buffer and transforms all matches using a format string supplied by the user. But instead of replacing the text in the buffer with the transformed matches, it acts like yank and copies the transformed matches into a register.","4":"GitHub repository: https:\/\/github.com\/idanarye\/vim-yankitute\r\n\r\nYankitute combines the yank and substitute Vim commands into one. Like substitute, it searches for a pattern in the buffer and transforms all matches using a format string supplied by the user. But instead of replacing the text in the buffer with the transformed matches, it acts like yank and copies the transformed matches into a register.","install_details":"","5":"","first_name":"Idan","6":"Idan","last_name":"Arye","7":"Arye","releases":[{"0":"4719","vim_version":"7.3","1":"7.3","script_version":"1.1.0","2":"1.1.0","version_comment":"Use :substitute behind the scenes:\r\n - more :s_flags can be handled\r\n - respects gdefault\r\n - pattern can use \\zs and \\ze\r\n - replacement can use sub-replacement aka \\=\r\n - provide error detection","3":"Use :substitute behind the scenes:\r\n - more :s_flags can be handled\r\n - respects gdefault\r\n - pattern can use \\zs and \\ze\r\n - replacement can use sub-replacement aka \\=\r\n - provide error detection","package":"yankitute_v1.1.0.zip","4":"yankitute_v1.1.0.zip","src_id":"23441","5":"23441","creation_date":"1436038625","6":"1436038625"},{"0":"4719","vim_version":"7.0","1":"7.0","script_version":"1.0.0","2":"1.0.0","version_comment":"Initial upload","3":"Initial upload","package":"yankitute_v1.0.0.zip","4":"yankitute_v1.0.0.zip","src_id":"20791","5":"20791","creation_date":"1378939861","6":"1378939861"}]},"4718":{"script_id":"4718","0":"4718","script_name":"SuperSub","1":"SuperSub","script_type":"utility","2":"utility","summary":"Enhanced Substitute Command","3":"Enhanced Substitute Command","description":"SuperSub is an enhanced substitute command that can both replace multiple words in one line as well as multiple words in multiple lines.\r\n\r\nHere are some examples:\r\nMy first name is Phil, my last name is Miller\r\n\r\nSure you could probably feed a simple regex into the standard substitute command for this one but you'll get the point\r\n\r\nIssuing :S\/Phil\/John\/Miller\/Smith will change it to\r\nMy first name is John, my last name is Smith\r\n\r\nOk, so that's not very exciting so check out this. Let's say you have this piece of PHP code:\r\n$contacts[1] = \"Phil\"\r\n\r\nSimple right? Now you want five of them.\r\n\r\nSo you copy it five times:\r\n$contacts[1] = \"Phil\"\r\n$contacts[1] = \"Phil\" \r\n$contacts[1] = \"Phil\"\r\n$contacts[1] = \"Phil\" \r\n$contacts[1] = \"Phil\"\r\n\r\nThen you select all but the first row and issue this command:\r\n:S\/1\/;2;3;4;5\/Phil\/;Jessica;Joel;Kaitlyn;PorkChop\r\n\r\nAnd out comes this:\r\n$contacts[1] = \"Phil\"\r\n$contacts[2] = \"Jessica\" \r\n$contacts[3] = \"Joel\"\r\n$contacts[4] = \"Phil\" \r\n$contacts[5] = \"PorkChop\"","4":"SuperSub is an enhanced substitute command that can both replace multiple words in one line as well as multiple words in multiple lines.\r\n\r\nHere are some examples:\r\nMy first name is Phil, my last name is Miller\r\n\r\nSure you could probably feed a simple regex into the standard substitute command for this one but you'll get the point\r\n\r\nIssuing :S\/Phil\/John\/Miller\/Smith will change it to\r\nMy first name is John, my last name is Smith\r\n\r\nOk, so that's not very exciting so check out this. Let's say you have this piece of PHP code:\r\n$contacts[1] = \"Phil\"\r\n\r\nSimple right? Now you want five of them.\r\n\r\nSo you copy it five times:\r\n$contacts[1] = \"Phil\"\r\n$contacts[1] = \"Phil\" \r\n$contacts[1] = \"Phil\"\r\n$contacts[1] = \"Phil\" \r\n$contacts[1] = \"Phil\"\r\n\r\nThen you select all but the first row and issue this command:\r\n:S\/1\/;2;3;4;5\/Phil\/;Jessica;Joel;Kaitlyn;PorkChop\r\n\r\nAnd out comes this:\r\n$contacts[1] = \"Phil\"\r\n$contacts[2] = \"Jessica\" \r\n$contacts[3] = \"Joel\"\r\n$contacts[4] = \"Phil\" \r\n$contacts[5] = \"PorkChop\"","install_details":"Just drop supersub.vim in your plugin directory.","5":"Just drop supersub.vim in your plugin directory.","first_name":"Phil","6":"Phil","last_name":"Miller","7":"Miller","releases":[{"0":"4718","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"supersub.vim","4":"supersub.vim","src_id":"20782","5":"20782","creation_date":"1378868401","6":"1378868401"}]},"4717":{"script_id":"4717","0":"4717","script_name":"svnim","1":"svnim","script_type":"utility","2":"utility","summary":"svn plugin","3":"svn plugin","description":"SVN IMproved plugin\r\n\r\nhttps:\/\/github.com\/4lb0\/svnim\r\n\r\nDependency:\r\n\r\n* svn\r\n\r\nCommands:\r\n\r\n* <leader>ss : svn status. When the status windows is open you can press *x* to choosewherever file you want to commit and then *c* in order to commit Screenshot: http:\/\/imgur.com\/30W16nt.\r\n* <leader>sd : svn diff. You can also get the diff of version 123 by pressing *123sd*.\r\n* <leader>su : svn update.\r\n* <leader>sl : svn log. By default will show last 10 commits, you can press *20sl* to get last 20 commits.","4":"SVN IMproved plugin\r\n\r\nhttps:\/\/github.com\/4lb0\/svnim\r\n\r\nDependency:\r\n\r\n* svn\r\n\r\nCommands:\r\n\r\n* <leader>ss : svn status. When the status windows is open you can press *x* to choosewherever file you want to commit and then *c* in order to commit Screenshot: http:\/\/imgur.com\/30W16nt.\r\n* <leader>sd : svn diff. You can also get the diff of version 123 by pressing *123sd*.\r\n* <leader>su : svn update.\r\n* <leader>sl : svn log. By default will show last 10 commits, you can press *20sl* to get last 20 commits.","install_details":"Extract the svnim folder into ~\/.vim\/plugin","5":"Extract the svnim folder into ~\/.vim\/plugin","first_name":"Rodrigo","6":"Rodrigo","last_name":"Arce","7":"Arce","releases":[{"0":"4717","vim_version":"7.0","1":"7.0","script_version":"0.0.2","2":"0.0.2","version_comment":"Fix <SID> bug ","3":"Fix <SID> bug ","package":"svnim-0.0.2.zip","4":"svnim-0.0.2.zip","src_id":"20783","5":"20783","creation_date":"1378868553","6":"1378868553"}]},"4716":{"script_id":"4716","0":"4716","script_name":"files.vim","1":"files.vim","script_type":"utility","2":"utility","summary":"List files for partial search using 'ls' command","3":"List files for partial search using 'ls' command","description":"Why another plugin?\r\n------------------\r\nI wanted open a file with by just typing a file name, even with a partial name of a file.\r\nI found several plugins out there to find a file with a partial name.\r\n\r\n    1) FuzzyFinder, http:\/\/www.vim.org\/scripts\/script.php?script_id=1984\r\n    2) CtrlP, http:\/\/www.vim.org\/scripts\/script.php?script_id=3736\r\n    3) Command-T. http:\/\/www.vim.org\/scripts\/script.php?script_id=3025\r\n\r\nI tried all of them, and was not satisfactory.\r\n\r\nAll of the above tried to mimic other editors behavior, TextMate, and they are heavy(sometimes makes me wait to load files and expressions)\r\n\r\nWhat I wanted was to see the files, and find what I want to open it. It is just simple combination of list and open, nothing else.\r\nFuthermore, mimicing other IDE's command it not a vim's way in my opinion.\r\n\r\nThat's why I developed this plugin. It does;\r\n  1. List all files(3 directory level deep)\r\n  2. Let you find a file in a separate vim window\r\n  3. Let you open a file in current or split window\r\n\r\nHow it works\r\n------------\r\n  1. open a window and run result of run `ls` command (Sorry, window users)\r\n  2. find your file name, `\/`, then type <Enter> to open it\r\n\r\n  To change the base directory of file list, run the vim command, :cd\r\n\r\n  i.e. `:cd ~\/myproject`.\r\n\r\n  After :cd <path> command, your files listed by files.vim plugin will be based on the directory path.\r\n\r\n\r\ncreated by\r\nAllen Kim\r\n \r\nscript type\r\nutility\r\n \r\ndescription\r\nHow it works \r\n\r\nWhen initialized, set related files \r\nIn vim window, when n is pressed \r\n\r\n1. Get the current file name \r\n2. Get the related files \r\n3. Open a window with related files and let you to choose which file to open \r\n   1) <Enter> to open in a current window \r\n   2) \"o\" to open in a horizontally splitted window \r\n   3) \"v\" to open in a vertically split window \r\n\r\nFor Rails developers, there is pre-defined mapping like the following. You may want to change this. If so, you can re-define this in your .vimrc \r\n    let g:nextFilesMap[\"Ruby On Rails\"] = { \r\n      \\ \"Ruby On Rails\" : { \r\n        \\ \"Controller\" : { \"expression\" : \"app\/controllers\/(.*)_controller.rb$\", \"transform\" : \"pluralize\" }, \r\n        \\ \"Funtional Test\" : { \"expression\" : \"test\/functional\/(.*)_controller_test.rb$\", \"transform\" : \"pluralize\" }, \r\n        \\ \"View\" : { \"expression\" : \"app\/views\/(.*)\/\", \"transform\" : \"pluralize\" }, \r\n        \\ \"Model\" : { \"expression\" : \"app\/models\/(.*).rb$\", \"transform\" : \"singularize\" }, \r\n        \\ \"Unit Test\" : { \"expression\" : \"test\/unit\/(.*)_test.rb$\", \"transform\" : \"singularize\" } \r\n      \\ } \r\n    \\ } \r\n\r\nFor screenshot and source code, visit https:\/\/github.com\/bighostkim\/files.vim, \r\nand if you want to make this better, please log an issue or fork this repository.","4":"Why another plugin?\r\n------------------\r\nI wanted open a file with by just typing a file name, even with a partial name of a file.\r\nI found several plugins out there to find a file with a partial name.\r\n\r\n    1) FuzzyFinder, http:\/\/www.vim.org\/scripts\/script.php?script_id=1984\r\n    2) CtrlP, http:\/\/www.vim.org\/scripts\/script.php?script_id=3736\r\n    3) Command-T. http:\/\/www.vim.org\/scripts\/script.php?script_id=3025\r\n\r\nI tried all of them, and was not satisfactory.\r\n\r\nAll of the above tried to mimic other editors behavior, TextMate, and they are heavy(sometimes makes me wait to load files and expressions)\r\n\r\nWhat I wanted was to see the files, and find what I want to open it. It is just simple combination of list and open, nothing else.\r\nFuthermore, mimicing other IDE's command it not a vim's way in my opinion.\r\n\r\nThat's why I developed this plugin. It does;\r\n  1. List all files(3 directory level deep)\r\n  2. Let you find a file in a separate vim window\r\n  3. Let you open a file in current or split window\r\n\r\nHow it works\r\n------------\r\n  1. open a window and run result of run `ls` command (Sorry, window users)\r\n  2. find your file name, `\/`, then type <Enter> to open it\r\n\r\n  To change the base directory of file list, run the vim command, :cd\r\n\r\n  i.e. `:cd ~\/myproject`.\r\n\r\n  After :cd <path> command, your files listed by files.vim plugin will be based on the directory path.\r\n\r\n\r\ncreated by\r\nAllen Kim\r\n \r\nscript type\r\nutility\r\n \r\ndescription\r\nHow it works \r\n\r\nWhen initialized, set related files \r\nIn vim window, when n is pressed \r\n\r\n1. Get the current file name \r\n2. Get the related files \r\n3. Open a window with related files and let you to choose which file to open \r\n   1) <Enter> to open in a current window \r\n   2) \"o\" to open in a horizontally splitted window \r\n   3) \"v\" to open in a vertically split window \r\n\r\nFor Rails developers, there is pre-defined mapping like the following. You may want to change this. If so, you can re-define this in your .vimrc \r\n    let g:nextFilesMap[\"Ruby On Rails\"] = { \r\n      \\ \"Ruby On Rails\" : { \r\n        \\ \"Controller\" : { \"expression\" : \"app\/controllers\/(.*)_controller.rb$\", \"transform\" : \"pluralize\" }, \r\n        \\ \"Funtional Test\" : { \"expression\" : \"test\/functional\/(.*)_controller_test.rb$\", \"transform\" : \"pluralize\" }, \r\n        \\ \"View\" : { \"expression\" : \"app\/views\/(.*)\/\", \"transform\" : \"pluralize\" }, \r\n        \\ \"Model\" : { \"expression\" : \"app\/models\/(.*).rb$\", \"transform\" : \"singularize\" }, \r\n        \\ \"Unit Test\" : { \"expression\" : \"test\/unit\/(.*)_test.rb$\", \"transform\" : \"singularize\" } \r\n      \\ } \r\n    \\ } \r\n\r\nFor screenshot and source code, visit https:\/\/github.com\/bighostkim\/files.vim, \r\nand if you want to make this better, please log an issue or fork this repository.","install_details":"Installation\r\n------------\r\n  1. Download files.vim into your ~\/.vim\/plugin directory\r\n  2. in ~\/.vimrc, add a key map to call Files() function, I prefer \\f, but you can choose any you want.\r\n    nmap <Leader>f <ESC>:call Files()<CR>\r\n","5":"Installation\r\n------------\r\n  1. Download files.vim into your ~\/.vim\/plugin directory\r\n  2. in ~\/.vimrc, add a key map to call Files() function, I prefer \\f, but you can choose any you want.\r\n    nmap <Leader>f <ESC>:call Files()<CR>\r\n","first_name":"Allen","6":"Allen","last_name":"Kim","7":"Kim","releases":[{"0":"4716","vim_version":"7.0","1":"7.0","script_version":"0.2","2":"0.2","version_comment":"Added help line on the top","3":"Added help line on the top","package":"files.vim","4":"files.vim","src_id":"20776","5":"20776","creation_date":"1378760016","6":"1378760016"},{"0":"4716","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"files.vim","4":"files.vim","src_id":"20775","5":"20775","creation_date":"1378755471","6":"1378755471"}]},"4715":{"script_id":"4715","0":"4715","script_name":"Hardcore Mode","1":"Hardcore Mode","script_type":"utility","2":"utility","summary":"A mode that helps get rid of the habit of using evil cursor keys, mouse, and GUI","3":"A mode that helps get rid of the habit of using evil cursor keys, mouse, and GUI","description":"Agetian's Vim Hardcore Mode (C) 2013 by Michael Kamensky, all rights reserved.\r\nThis script is distributed under Vim license.\r\n==============================================================================\r\n\r\nThis simple script is aimed to help aspiring Vim users become adept at using the\r\nproper Vim motion keys when moving around, selecting text, and performing\r\nvarious operations.\r\n\r\nVim is a modern tool and, as any other modern tool, allows the user to use the\r\ntraditional input and movement methods, such as e.g. the cursor keys and the\r\nmouse, despite their terrible inefficiency compared to the methods that Vim was\r\noriginally meant to be used with. In addition to that, the GUI version of Vim\r\n(gVim) features the menu bar and the toolbar which seem to help the beginning\r\nuser but in reality only slow him\/her down and take away the precious window\r\nspace that can be used to actually display the edited text.\r\n\r\nThis hardcore mode is meant to help the Vim users get a better feel for the\r\nproper Vim movement and input commands and get rid of the bad habit of using the\r\n\"evil\", slow methods of moving around. It does so by temporarily disabling the\r\nmost common unwanted movement methods (the cursor keys, the mouse,\r\nPgUp\/PgDn\/etc.), as well as the most common unwanted GUI features (the menu bar\r\nand the toolbar), thus making it more difficult (rather, temporarily impossible)\r\nfor the end user to actually use them. In normal mode, the plugin will give\r\nhints as to what keys can be used instead of the \"evil\" keys. In insert,\r\ncommand, and visual modes, sadly, the hints did not work correctly for some\r\nreason, so currently the keys will simply not do anything there. With time,\r\nhopefully, you will learn to overcome your desire to use the evil keys and the\r\nevil mouse in Vim (because they simply don't do the thing you want) and learn to\r\nuse the proper keys instead.\r\n\r\nThe hardcore mode is easy to enable (<Leader>hm by default, mnemonic for\r\n\"Hardcore Mode\") and easy to disable if the user gets tired of it or gets lost\r\nand confused (use the same key sequence, <Leader>hm by default).\r\n\r\nWARNING: By default, the hardcore mode disables the cursor keys and PgUp\/PgDn\/\r\nEnd\/Home\/Insert\/Delete keys in the command (ex) mode! This may be confusing at\r\nfirst because it seems to make scrolling through the command history more\r\ndifficult (many users prefer to use the Up key to choose the previous commands).\r\nDo try to use the main keyboard keys to navigate the command line history (C-p\r\nshows the previous entry, C-n shows the next entry, C-f opens the history window\r\nwhere you can edit the command line and execute it). If you find it difficult\r\nand you're sure you want the old command line functionality back while in\r\nHardcore mode, you can use <Leader>hc (by default) to toggle whether the command\r\nmode is hardcore or not.\r\n\r\nThe plugin will remember the user's current mouse and GUI settings and restore\r\nthem when the hardcore mode is disabled. As such, if you normally have the mouse\r\nand the menu bar\/toolbar disabled, disabling the hardcore mode will not enable\r\nthose features automatically for you.\r\n\r\nEnabling\/disabling the mode\r\n===========================\r\nUnless you customized the mappings in hardcore.vim, use:\r\n<Leader>hm to toggle the hardcore mode\r\n<Leader>hc to toggle whether the command (ex) mode is hardcore or not\r\nThe default leader key in Vim is the backslash key (\\).\r\n\r\nCaution\r\n=======\r\nIf you are a beginner in Vim, please make sure of the following before trying to\r\nuse this script: \r\n1) Make sure you at least complete the 'vimtutor' tutorial that ships with Vim\r\nto familiarize yourself with the proper motion commands.\r\n2) Make sure you use the \"real Vim\" - that is, ensure you're not using the\r\nso-called \"easy mode\" which is actually more evil than both the cursor keys and\r\nthe mouse combined. If you can only use Vim in \"easy mode\", please familiarize\r\nyourself with the way Vim is really meant to be used before trying the hardcore\r\nmode!\r\n3) If worst comes to worst, remember that <Leader>hm (by default, backslash\r\nquickly followed by h and m) in Normal mode will disable Hardcore Mode if it's\r\nalready enabled. If that fails for you for whatever reason and you can't get out\r\nof hardcore mode, restart Vim and it'll be back to normal.\r\n\r\nThe hardcore mode may feel frustrating for you or confuse you in case you're\r\nonly starting to use Vim and are not familiar with modal editing and vi movement\r\nkeys yet. You've been warned. ;)\r\n\r\nKnown issues\r\n============\r\n\r\nEnabling and disabling hardcore mode multiple times in gVim progressively makes\r\nthe gVim window smaller by one line. This is easily fixed by remaximizing gVim\r\nwindow or resizing it back to the desired size. This issue occurs because of the\r\nway gVim handles the menu bar and the toolbar when they are toggled on and off,\r\nI'm not sure if it's possible to resolve it programmatically from the plugin.\r\n\r\n==============================================================================\r\nIf you still feel brave enough to try out hardcore mode, gl hf!\r\n","4":"Agetian's Vim Hardcore Mode (C) 2013 by Michael Kamensky, all rights reserved.\r\nThis script is distributed under Vim license.\r\n==============================================================================\r\n\r\nThis simple script is aimed to help aspiring Vim users become adept at using the\r\nproper Vim motion keys when moving around, selecting text, and performing\r\nvarious operations.\r\n\r\nVim is a modern tool and, as any other modern tool, allows the user to use the\r\ntraditional input and movement methods, such as e.g. the cursor keys and the\r\nmouse, despite their terrible inefficiency compared to the methods that Vim was\r\noriginally meant to be used with. In addition to that, the GUI version of Vim\r\n(gVim) features the menu bar and the toolbar which seem to help the beginning\r\nuser but in reality only slow him\/her down and take away the precious window\r\nspace that can be used to actually display the edited text.\r\n\r\nThis hardcore mode is meant to help the Vim users get a better feel for the\r\nproper Vim movement and input commands and get rid of the bad habit of using the\r\n\"evil\", slow methods of moving around. It does so by temporarily disabling the\r\nmost common unwanted movement methods (the cursor keys, the mouse,\r\nPgUp\/PgDn\/etc.), as well as the most common unwanted GUI features (the menu bar\r\nand the toolbar), thus making it more difficult (rather, temporarily impossible)\r\nfor the end user to actually use them. In normal mode, the plugin will give\r\nhints as to what keys can be used instead of the \"evil\" keys. In insert,\r\ncommand, and visual modes, sadly, the hints did not work correctly for some\r\nreason, so currently the keys will simply not do anything there. With time,\r\nhopefully, you will learn to overcome your desire to use the evil keys and the\r\nevil mouse in Vim (because they simply don't do the thing you want) and learn to\r\nuse the proper keys instead.\r\n\r\nThe hardcore mode is easy to enable (<Leader>hm by default, mnemonic for\r\n\"Hardcore Mode\") and easy to disable if the user gets tired of it or gets lost\r\nand confused (use the same key sequence, <Leader>hm by default).\r\n\r\nWARNING: By default, the hardcore mode disables the cursor keys and PgUp\/PgDn\/\r\nEnd\/Home\/Insert\/Delete keys in the command (ex) mode! This may be confusing at\r\nfirst because it seems to make scrolling through the command history more\r\ndifficult (many users prefer to use the Up key to choose the previous commands).\r\nDo try to use the main keyboard keys to navigate the command line history (C-p\r\nshows the previous entry, C-n shows the next entry, C-f opens the history window\r\nwhere you can edit the command line and execute it). If you find it difficult\r\nand you're sure you want the old command line functionality back while in\r\nHardcore mode, you can use <Leader>hc (by default) to toggle whether the command\r\nmode is hardcore or not.\r\n\r\nThe plugin will remember the user's current mouse and GUI settings and restore\r\nthem when the hardcore mode is disabled. As such, if you normally have the mouse\r\nand the menu bar\/toolbar disabled, disabling the hardcore mode will not enable\r\nthose features automatically for you.\r\n\r\nEnabling\/disabling the mode\r\n===========================\r\nUnless you customized the mappings in hardcore.vim, use:\r\n<Leader>hm to toggle the hardcore mode\r\n<Leader>hc to toggle whether the command (ex) mode is hardcore or not\r\nThe default leader key in Vim is the backslash key (\\).\r\n\r\nCaution\r\n=======\r\nIf you are a beginner in Vim, please make sure of the following before trying to\r\nuse this script: \r\n1) Make sure you at least complete the 'vimtutor' tutorial that ships with Vim\r\nto familiarize yourself with the proper motion commands.\r\n2) Make sure you use the \"real Vim\" - that is, ensure you're not using the\r\nso-called \"easy mode\" which is actually more evil than both the cursor keys and\r\nthe mouse combined. If you can only use Vim in \"easy mode\", please familiarize\r\nyourself with the way Vim is really meant to be used before trying the hardcore\r\nmode!\r\n3) If worst comes to worst, remember that <Leader>hm (by default, backslash\r\nquickly followed by h and m) in Normal mode will disable Hardcore Mode if it's\r\nalready enabled. If that fails for you for whatever reason and you can't get out\r\nof hardcore mode, restart Vim and it'll be back to normal.\r\n\r\nThe hardcore mode may feel frustrating for you or confuse you in case you're\r\nonly starting to use Vim and are not familiar with modal editing and vi movement\r\nkeys yet. You've been warned. ;)\r\n\r\nKnown issues\r\n============\r\n\r\nEnabling and disabling hardcore mode multiple times in gVim progressively makes\r\nthe gVim window smaller by one line. This is easily fixed by remaximizing gVim\r\nwindow or resizing it back to the desired size. This issue occurs because of the\r\nway gVim handles the menu bar and the toolbar when they are toggled on and off,\r\nI'm not sure if it's possible to resolve it programmatically from the plugin.\r\n\r\n==============================================================================\r\nIf you still feel brave enough to try out hardcore mode, gl hf!\r\n","install_details":"Variant 1. Drop hardcore.vim into your \"plugin\" folder in the ~\/.vim directory.\r\n\t   It'll be loaded automatically the next time you start Vim.\r\nVariant 2. Manually open the script (:e hardcore.vim) and source it (:so %).\r\n\t   It'll be loaded immediately but will not be auto-loaded the next time\r\n\t   you start Vim.\r\n\r\nIMPORTANT: If you are using any custom plugins that rely on mappings for cursor\r\nkeys, Insert\/Delete\/Home\/End\/PgUp\/PgDn keys, or the mouse, this plugin may mess\r\nwith these plugins and disrupt their operation! \r\n\r\n","5":"Variant 1. Drop hardcore.vim into your \"plugin\" folder in the ~\/.vim directory.\r\n\t   It'll be loaded automatically the next time you start Vim.\r\nVariant 2. Manually open the script (:e hardcore.vim) and source it (:so %).\r\n\t   It'll be loaded immediately but will not be auto-loaded the next time\r\n\t   you start Vim.\r\n\r\nIMPORTANT: If you are using any custom plugins that rely on mappings for cursor\r\nkeys, Insert\/Delete\/Home\/End\/PgUp\/PgDn keys, or the mouse, this plugin may mess\r\nwith these plugins and disrupt their operation! \r\n\r\n","first_name":"Michael","6":"Michael","last_name":"Kamensky","7":"Kamensky","releases":[{"0":"4715","vim_version":"7.0","1":"7.0","script_version":"1.2","2":"1.2","version_comment":"- Changed the way Hardcore Mode is enabled\/disabled. Instead of using two different command sequences the Hardcore Mode is now toggled with <Leader>hm, mnemonic for Hardcore Mode.","3":"- Changed the way Hardcore Mode is enabled\/disabled. Instead of using two different command sequences the Hardcore Mode is now toggled with <Leader>hm, mnemonic for Hardcore Mode.","package":"hardcore_1.2.zip","4":"hardcore_1.2.zip","src_id":"20771","5":"20771","creation_date":"1378737955","6":"1378737955"},{"0":"4715","vim_version":"7.0","1":"7.0","script_version":"1.1","2":"1.1","version_comment":"- Hardcore mode now disables cursor keys and PgUp\/PgDn\/etc. keys in Command (ex) mode by default (yes, do try to use C-n\/C-p\/C-f instead to navigate through the command history and edit\/reexecute commands).\r\n- Hardcore Command (ex) mode can be toggled using the <Leader>hc combination while in Normal mode.\r\n- Readme updated to account for the new changes and to outline the known issues and their solutions.","3":"- Hardcore mode now disables cursor keys and PgUp\/PgDn\/etc. keys in Command (ex) mode by default (yes, do try to use C-n\/C-p\/C-f instead to navigate through the command history and edit\/reexecute commands).\r\n- Hardcore Command (ex) mode can be toggled using the <Leader>hc combination while in Normal mode.\r\n- Readme updated to account for the new changes and to outline the known issues and their solutions.","package":"hardcore_1.1.zip","4":"hardcore_1.1.zip","src_id":"20768","5":"20768","creation_date":"1378704873","6":"1378704873"},{"0":"4715","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"hardcore_1.0.zip","4":"hardcore_1.0.zip","src_id":"20767","5":"20767","creation_date":"1378649059","6":"1378649059"}]},"4714":{"script_id":"4714","0":"4714","script_name":"KillBrackets","1":"KillBrackets","script_type":"utility","2":"utility","summary":"Removes matching brackets\/parens. Very handy in LISP\/Scheme","3":"Removes matching brackets\/parens. Very handy in LISP\/Scheme","description":"This script adds a feature I've often missed when hacking away at some code in Vim.\r\n\r\nI recommend adding a keybinding, such as \"<Leader>) :Killbracks\"\r\nTo use it, just place the cursor on top of either a closing or opening bracket while in normal mode (vim will highlight the other one) and either type \":Killbracks\" or use the keybinding you just added.\r\n\r\nProblems (IMPORTANT FOR LISP):\r\nThere are problems associated with parens and bracks inside of quotes messing with \"the order of things.\" Killbrackets is set up to ignore everything within \"double quotes\"  and 'single quotes' but if you're programming in a language that uses 'single quotes' for something completely different (like in LISP) you might be in trouble, if you had something like '(LIST OF STUFF) in your program.\r\nTo fix this, you go into the \"KillBrackets.vim\" file and search for \"QUOTES SETTINGS\" then uncomment the behaviour you want, and comment the behaviour you don't want (explained a bit further in the source)\r\nNote that if you are \"(inside quotes)\" or '(inside quotes)', KillBrackets will do it's magic perfectly if the parens inside of the quotes are correctly matched. But if you are outside of the quotes (\"wasd)wasd\") KillBrackets will ignore everything within the quotes and only kill the matching bracket on the outside, and you'll end up with \"wasd)wasd\".","4":"This script adds a feature I've often missed when hacking away at some code in Vim.\r\n\r\nI recommend adding a keybinding, such as \"<Leader>) :Killbracks\"\r\nTo use it, just place the cursor on top of either a closing or opening bracket while in normal mode (vim will highlight the other one) and either type \":Killbracks\" or use the keybinding you just added.\r\n\r\nProblems (IMPORTANT FOR LISP):\r\nThere are problems associated with parens and bracks inside of quotes messing with \"the order of things.\" Killbrackets is set up to ignore everything within \"double quotes\"  and 'single quotes' but if you're programming in a language that uses 'single quotes' for something completely different (like in LISP) you might be in trouble, if you had something like '(LIST OF STUFF) in your program.\r\nTo fix this, you go into the \"KillBrackets.vim\" file and search for \"QUOTES SETTINGS\" then uncomment the behaviour you want, and comment the behaviour you don't want (explained a bit further in the source)\r\nNote that if you are \"(inside quotes)\" or '(inside quotes)', KillBrackets will do it's magic perfectly if the parens inside of the quotes are correctly matched. But if you are outside of the quotes (\"wasd)wasd\") KillBrackets will ignore everything within the quotes and only kill the matching bracket on the outside, and you'll end up with \"wasd)wasd\".","install_details":"Linux\/Mac\/BSD:\r\n        Put the \"KillBrackets.vim\" file inside ~\/.vim\/plugin\/ and restart vim\r\n\r\nWindows:\r\n        Put the \"KillBrackets.vim\" file inside C:\\Program Files (x86)\\Vim\\vim74\\plugin (requires admin rights) and restart vim.","5":"Linux\/Mac\/BSD:\r\n        Put the \"KillBrackets.vim\" file inside ~\/.vim\/plugin\/ and restart vim\r\n\r\nWindows:\r\n        Put the \"KillBrackets.vim\" file inside C:\\Program Files (x86)\\Vim\\vim74\\plugin (requires admin rights) and restart vim.","first_name":"Jonas","6":"Jonas","last_name":"M\u00c3\u00b8ller","7":"M\u00c3\u00b8ller","releases":[{"0":"4714","vim_version":"7.0","1":"7.0","script_version":"1.0.1","2":"1.0.1","version_comment":"Added license (MIT)","3":"Added license (MIT)","package":"KillBrackets.vim","4":"KillBrackets.vim","src_id":"20765","5":"20765","creation_date":"1378579001","6":"1378579001"},{"0":"4714","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"KillBrackets.vim","4":"KillBrackets.vim","src_id":"20760","5":"20760","creation_date":"1378472751","6":"1378472751"}]},"4713":{"script_id":"4713","0":"4713","script_name":"reco","1":"reco","script_type":"utility","2":"utility","summary":"backup and recovery solution for Vim","3":"backup and recovery solution for Vim","description":"Plugin was completely re-written in python. Below you have video presentation of\r\nplugin showing difference in Vim recovery with and without Reco plugin.\r\n\r\nIn youtube set video quality 720p\r\nSometimes first 10s of video is in lower resolution even with 720p quality, but rest of video is fine so don't give up\r\nhttp:\/\/www.youtube.com\/watch?v=NrJ87pENIX4\r\n\r\nSee reco docs for more details\r\n\r\nGithub: \r\nhttps:\/\/github.com\/mir-mal\/reco","4":"Plugin was completely re-written in python. Below you have video presentation of\r\nplugin showing difference in Vim recovery with and without Reco plugin.\r\n\r\nIn youtube set video quality 720p\r\nSometimes first 10s of video is in lower resolution even with 720p quality, but rest of video is fine so don't give up\r\nhttp:\/\/www.youtube.com\/watch?v=NrJ87pENIX4\r\n\r\nSee reco docs for more details\r\n\r\nGithub: \r\nhttps:\/\/github.com\/mir-mal\/reco","install_details":"You can source Reco directly from .vimrc as you can see in video\r\nOr use any plugin manager i.e pathogen\r\nOnly setting you probably would like to change is backup_dir\r\nSet in .vimrc\r\npy reco.backup_dir=<your new dir> #default is your home folder\r\nor you  can change path in reco.vim ","5":"You can source Reco directly from .vimrc as you can see in video\r\nOr use any plugin manager i.e pathogen\r\nOnly setting you probably would like to change is backup_dir\r\nSet in .vimrc\r\npy reco.backup_dir=<your new dir> #default is your home folder\r\nor you  can change path in reco.vim ","first_name":"Mirek","6":"Mirek","last_name":"Malinowski","7":"Malinowski","releases":[{"0":"4713","vim_version":"7.3","1":"7.3","script_version":"2.1","2":"2.1","version_comment":"unnamed buffer fix: when unnamed buffer is saved, current buffer is equal saved buffer","3":"unnamed buffer fix: when unnamed buffer is saved, current buffer is equal saved buffer","package":"reco2.1.zip","4":"reco2.1.zip","src_id":"20840","5":"20840","creation_date":"1380027607","6":"1380027607"},{"0":"4713","vim_version":"7.3","1":"7.3","script_version":"2.0","2":"2.0","version_comment":"re-written in python, test_cases added","3":"re-written in python, test_cases added","package":"reco.tar.gz","4":"reco.tar.gz","src_id":"20816","5":"20816","creation_date":"1379479032","6":"1379479032"}]},"4712":{"script_id":"4712","0":"4712","script_name":"FindYamlKey","1":"FindYamlKey","script_type":"utility","2":"utility","summary":"Search for nested keys in a YAML document","3":"Search for nested keys in a YAML document","description":"Find an always current version on Github: https:\/\/github.com\/munen\/find_yaml_key\r\n\r\nUSAGE~\r\n\r\n:FindYamlKey {pattern}\r\n\r\n    Search recursively in the current buffer for yaml keys.\r\n    For example\r\n\r\n    :FindYamlKey foo.bar.baz\r\n\r\n    Will place the cursor under the |baz| key in this YAML document:\r\n\r\n    maunz:\r\n      braunz: \"mew\"\r\n    foo:\r\n      bar:\r\n        baz: \"hello world\"","4":"Find an always current version on Github: https:\/\/github.com\/munen\/find_yaml_key\r\n\r\nUSAGE~\r\n\r\n:FindYamlKey {pattern}\r\n\r\n    Search recursively in the current buffer for yaml keys.\r\n    For example\r\n\r\n    :FindYamlKey foo.bar.baz\r\n\r\n    Will place the cursor under the |baz| key in this YAML document:\r\n\r\n    maunz:\r\n      braunz: \"mew\"\r\n    foo:\r\n      bar:\r\n        baz: \"hello world\"","install_details":"Requires ruby support.","5":"Requires ruby support.","first_name":"Munen Alain M.","6":"Munen Alain M.","last_name":"","7":"","releases":[{"0":"4712","vim_version":"7.3","1":"7.3","script_version":"0.1.0","2":"0.1.0","version_comment":"Initial upload","3":"Initial upload","package":"find_yaml_key.zip","4":"find_yaml_key.zip","src_id":"20740","5":"20740","creation_date":"1377982177","6":"1377982177"}]},"4710":{"script_id":"4710","0":"4710","script_name":"tweetvim-advanced-filter","1":"tweetvim-advanced-filter","script_type":"utility","2":"utility","summary":"A high-configurable timeline filter for TweetVim.","3":"A high-configurable timeline filter for TweetVim.","description":"TweetVim has a simple NG word filter as default filter. This plugin adds a high-configuable filter to TweetVim.\r\n\r\nAll you have to do is to define a dictionary-function, g:tweetvim_advanced_filter.executor. The function must have one argument and the argument is a dictionary of tweet information. And it must return 1 or 0 which represents if the tweet should be filtered or not.\r\n\r\nTweetVim\r\nhttp:\/\/www.vim.org\/scripts\/script.php?script_id=4532\r\n\r\nGithub repository of this plugin is below. Please check to get more information. \r\nhttps:\/\/github.com\/rhysd\/tweetvim-advanced-filter","4":"TweetVim has a simple NG word filter as default filter. This plugin adds a high-configuable filter to TweetVim.\r\n\r\nAll you have to do is to define a dictionary-function, g:tweetvim_advanced_filter.executor. The function must have one argument and the argument is a dictionary of tweet information. And it must return 1 or 0 which represents if the tweet should be filtered or not.\r\n\r\nTweetVim\r\nhttp:\/\/www.vim.org\/scripts\/script.php?script_id=4532\r\n\r\nGithub repository of this plugin is below. Please check to get more information. \r\nhttps:\/\/github.com\/rhysd\/tweetvim-advanced-filter","install_details":"0. install TweetVim in advance.\r\n\r\n1. unzip the archived file you downloaded. \r\n\r\n2. copy files in autoload\/ and plugin\/ to your Vim runtime path. \r\n\r\n3. define function! g:tweetvim_advanced_filter.executor(tweet).","5":"0. install TweetVim in advance.\r\n\r\n1. unzip the archived file you downloaded. \r\n\r\n2. copy files in autoload\/ and plugin\/ to your Vim runtime path. \r\n\r\n3. define function! g:tweetvim_advanced_filter.executor(tweet).","first_name":"Linda","6":"Linda","last_name":"Rhysd","7":"Rhysd","releases":[{"0":"4710","vim_version":"7.2","1":"7.2","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"tweetvim-advanced-filter.zip","4":"tweetvim-advanced-filter.zip","src_id":"20718","5":"20718","creation_date":"1377531147","6":"1377531147"}]},"4709":{"script_id":"4709","0":"4709","script_name":"unite-n3337","1":"unite-n3337","script_type":"utility","2":"utility","summary":"A vim plugin for unite.vim to look in N3337 quickly.","3":"A vim plugin for unite.vim to look in N3337 quickly.","description":"unite-n3337 is a Vim plugin for |unite.vim| to look in highlighted N3337\r\nquickly.  N3337 is Working Draft, Standard for C++, which is the nearest draft\r\nto ISO\/IEC 14882:2011.\r\n\r\nGithub repository of this plugin is below. Please check to get more information. \r\nhttps:\/\/github.com\/rhysd\/unite-n3337","4":"unite-n3337 is a Vim plugin for |unite.vim| to look in highlighted N3337\r\nquickly.  N3337 is Working Draft, Standard for C++, which is the nearest draft\r\nto ISO\/IEC 14882:2011.\r\n\r\nGithub repository of this plugin is below. Please check to get more information. \r\nhttps:\/\/github.com\/rhysd\/unite-n3337","install_details":"0. get n3337.pdf from http:\/\/www.open-std.org\/jtc1\/sc22\/wg21\/docs\/papers\/2012\/ and install unite.vim in advance and pdftotext command.\r\n\r\n1. unzip the archived file you downloaded. \r\n\r\n2. copy files in autoload\/ and doc\/ to your Vim runtime path. \r\n\r\n3. :Unite n3337","5":"0. get n3337.pdf from http:\/\/www.open-std.org\/jtc1\/sc22\/wg21\/docs\/papers\/2012\/ and install unite.vim in advance and pdftotext command.\r\n\r\n1. unzip the archived file you downloaded. \r\n\r\n2. copy files in autoload\/ and doc\/ to your Vim runtime path. \r\n\r\n3. :Unite n3337","first_name":"Linda","6":"Linda","last_name":"Rhysd","7":"Rhysd","releases":[{"0":"4709","vim_version":"7.2","1":"7.2","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"unite-n3337.zip","4":"unite-n3337.zip","src_id":"20717","5":"20717","creation_date":"1377530687","6":"1377530687"}]},"4708":{"script_id":"4708","0":"4708","script_name":"open-pdf.vim","1":"open-pdf.vim","script_type":"utility","2":"utility","summary":"Convert pdf file to plain text, cache it and open it quickly in vim using pdftot","3":"Convert pdf file to plain text, cache it and open it quickly in vim using pdftot","description":"*open-pdf.vim* is plugin to open pdf files in vim. This plugin enables to\r\naccess pdf files and yank in the files quickly. Conversion from pdf to txt\r\ntakes seconds, however, the conversion only occurs at first time because this\r\nplugin cache txt files. If you use |unite.vim|, you can access the cache files\r\nusing unite interface.\r\n\r\nGithub repository of this plugin is below. Please check to get more information.\r\nhttps:\/\/github.com\/rhysd\/open-pdf.vim","4":"*open-pdf.vim* is plugin to open pdf files in vim. This plugin enables to\r\naccess pdf files and yank in the files quickly. Conversion from pdf to txt\r\ntakes seconds, however, the conversion only occurs at first time because this\r\nplugin cache txt files. If you use |unite.vim|, you can access the cache files\r\nusing unite interface.\r\n\r\nGithub repository of this plugin is below. Please check to get more information.\r\nhttps:\/\/github.com\/rhysd\/open-pdf.vim","install_details":"0. texttopdf command is required. This is a part of poppler package.\r\n\r\n1. unzip the archived file you downloaded. \r\n\r\n2. copy files in autoload\/ and plugin\/ and doc\/ to your Vim runtime path. \r\n\r\n3. open pdf file with :Pdf command\r\n","5":"0. texttopdf command is required. This is a part of poppler package.\r\n\r\n1. unzip the archived file you downloaded. \r\n\r\n2. copy files in autoload\/ and plugin\/ and doc\/ to your Vim runtime path. \r\n\r\n3. open pdf file with :Pdf command\r\n","first_name":"Linda","6":"Linda","last_name":"Rhysd","7":"Rhysd","releases":[{"0":"4708","vim_version":"7.3","1":"7.3","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"open-pdf.vim.zip","4":"open-pdf.vim.zip","src_id":"20716","5":"20716","creation_date":"1377530174","6":"1377530174"}]},"4707":{"script_id":"4707","0":"4707","script_name":"clever-f.vim","1":"clever-f.vim","script_type":"utility","2":"utility","summary":"Extended f\/F\/t\/T mappings for more convenience.","3":"Extended f\/F\/t\/T mappings for more convenience.","description":"clever-f.vim extends f, F, t and T mappings for more convenience.  Instead of ;, f is available to repeat after you type f{char} or F{char}.  F after f{char} and F{char} is also available to undo a jump. t{char} and T{char} are ditto. This extension makes a repeat easier and makes you forget the existence of ;. You can use ; for other key mapping.\r\nIn addition, you can customize a behavior of the mappings.\r\n\r\nGithub repository of this plugin is here\r\nhttps:\/\/github.com\/rhysd\/clever-f.vim\r\n\r\nPlease see README.md, doc\/clever_f.txt and this repository for more information.\r\n\r\n","4":"clever-f.vim extends f, F, t and T mappings for more convenience.  Instead of ;, f is available to repeat after you type f{char} or F{char}.  F after f{char} and F{char} is also available to undo a jump. t{char} and T{char} are ditto. This extension makes a repeat easier and makes you forget the existence of ;. You can use ; for other key mapping.\r\nIn addition, you can customize a behavior of the mappings.\r\n\r\nGithub repository of this plugin is here\r\nhttps:\/\/github.com\/rhysd\/clever-f.vim\r\n\r\nPlease see README.md, doc\/clever_f.txt and this repository for more information.\r\n\r\n","install_details":"1. unzip the archived file you downloaded. \r\n\r\n2. copy files in autoload\/ and plugin\/ to your Vim runtime path. \r\n\r\n3. f, F, t, T mappings are overwritten automatically.\r\n","5":"1. unzip the archived file you downloaded. \r\n\r\n2. copy files in autoload\/ and plugin\/ to your Vim runtime path. \r\n\r\n3. f, F, t, T mappings are overwritten automatically.\r\n","first_name":"Linda","6":"Linda","last_name":"Rhysd","7":"Rhysd","releases":[{"0":"4707","vim_version":"7.0","1":"7.0","script_version":"1.7","2":"1.7","version_comment":"- Add new feature 'highlight timeout' which removes highlights after specified timeout automatically\r\n- Do not repeat the previous character while f mapping is used while macro\r\n- Small refactorings\/improvements","3":"- Add new feature 'highlight timeout' which removes highlights after specified timeout automatically\r\n- Do not repeat the previous character while f mapping is used while macro\r\n- Small refactorings\/improvements","package":"clever-f-1.7.zip","4":"clever-f-1.7.zip","src_id":"27590","5":"27590","creation_date":"1620170167","6":"1620170167"},{"0":"4707","vim_version":"7.0","1":"7.0","script_version":"1.6","2":"1.6","version_comment":"- Adding new features\r\n- Fixes for newer Vim","3":"- Adding new features\r\n- Fixes for newer Vim","package":"clever-f-1.6.zip","4":"clever-f-1.6.zip","src_id":"27309","5":"27309","creation_date":"1599361271","6":"1599361271"},{"0":"4707","vim_version":"7.0","1":"7.0","script_version":"1.4","2":"1.4","version_comment":"New features: \r\n  - highlight characters \r\n  - do not move cursor on input \r\n  - timeout \r\n  - repeat last input \r\n\r\n...and various bug fixes","3":"New features: \r\n  - highlight characters \r\n  - do not move cursor on input \r\n  - timeout \r\n  - repeat last input \r\n\r\n...and various bug fixes","package":"clever-f-1.4.zip","4":"clever-f-1.4.zip","src_id":"22293","5":"22293","creation_date":"1407347116","6":"1407347116"},{"0":"4707","vim_version":"7.3","1":"7.3","script_version":"1.3","2":"1.3","version_comment":"- added new feature\r\n  - smart case\r\n  - you can set a character which matches any signs\r\n\r\n- some refactorings\r\n\r\n- some bug fixes","3":"- added new feature\r\n  - smart case\r\n  - you can set a character which matches any signs\r\n\r\n- some refactorings\r\n\r\n- some bug fixes","package":"clever-f-1.3.vim.zip","4":"clever-f-1.3.vim.zip","src_id":"20829","5":"20829","creation_date":"1379903034","6":"1379903034"},{"0":"4707","vim_version":"7.3","1":"7.3","script_version":"1.2","2":"1.2","version_comment":"## add features for customization\r\n- make a search ignore case\r\n- migemo support for Japanese environment\r\n- fix mappings' directions of search\r\n- show prompt\r\n\r\n## make more stable\r\n\r\n## some bug fixes and more tests","3":"## add features for customization\r\n- make a search ignore case\r\n- migemo support for Japanese environment\r\n- fix mappings' directions of search\r\n- show prompt\r\n\r\n## make more stable\r\n\r\n## some bug fixes and more tests","package":"clever-f.vim.zip","4":"clever-f.vim.zip","src_id":"20746","5":"20746","creation_date":"1378214752","6":"1378214752"},{"0":"4707","vim_version":"7.3","1":"7.3","script_version":"1.1","2":"1.1","version_comment":"Initial upload","3":"Initial upload","package":"clever-f.vim.zip","4":"clever-f.vim.zip","src_id":"20715","5":"20715","creation_date":"1377529321","6":"1377529321"}]},"4706":{"script_id":"4706","0":"4706","script_name":"excess-lines","1":"excess-lines","script_type":"utility","2":"utility","summary":"Highlight surplus characters of long lines","3":"Highlight surplus characters of long lines","description":"Work with several matchadd() matches at once.  The default highlights long lines.\r\nFor more, see:\r\nhttps:\/\/github.com\/dirkwallenstein\/vim-excess-lines","4":"Work with several matchadd() matches at once.  The default highlights long lines.\r\nFor more, see:\r\nhttps:\/\/github.com\/dirkwallenstein\/vim-excess-lines","install_details":"Please use Vundle or pathogen.","5":"Please use Vundle or pathogen.","first_name":"Dirk","6":"Dirk","last_name":"Wallenstein","7":"Wallenstein","releases":[{"0":"4706","vim_version":"7.3","1":"7.3","script_version":"1.0.0","2":"1.0.0","version_comment":"Initial upload","3":"Initial upload","package":"vim-excess-lines-1.0.0.tar.gz","4":"vim-excess-lines-1.0.0.tar.gz","src_id":"20711","5":"20711","creation_date":"1377446504","6":"1377446504"}]},"4705":{"script_id":"4705","0":"4705","script_name":"AtelierDune","1":"AtelierDune","script_type":"color scheme","2":"color scheme","summary":"Part of a set of colorschemes that come with a light and dark background ","3":"Part of a set of colorschemes that come with a light and dark background ","description":"This is one of five colorschemes that were made with Base16 Builder. For the construction of these colorschemes, Solarized colorscheme stood as a model. Like in Solarized, the colorschemes come in a light \u00e2\u0080\u0093 and in a dark background version. It\u00e2\u0080\u0099s really just variations on the same idea, but each with it\u00e2\u0080\u0099s own color-value relations, interdependent on each other and their base (background-)color.  \r\n\r\nOne can find the demopage for these colorschemes at:\r\nhttp:\/\/atelierbram.github.io\/syntax-highlighting\/atelier-schemes\/ \r\n\r\nDownloads at the GitHub repo: \r\nhttps:\/\/github.com\/atelierbram\/vim-colors_atelier-schemes\r\n\r\nMore information on this particular colorscheme: \r\nhttp:\/\/atelierbram.github.io\/syntax-highlighting\/atelier-schemes\/dune\r\n\r\nScreenshot dark version: \r\nhttp:\/\/atelierbram.github.io\/syntax-highlighting\/assets\/img\/dune-dark_vim_640x425.png\r\n\r\nScreenshot light version: \r\nhttp:\/\/atelierbram.github.io\/syntax-highlighting\/assets\/img\/dune-light_vim_640x425.png\r\n\r\nChanges:\r\nhttp:\/\/atelierbram.github.io\/syntax-highlighting\/atelier-schemes\/demo\/changes-03-2015.html#dune","4":"This is one of five colorschemes that were made with Base16 Builder. For the construction of these colorschemes, Solarized colorscheme stood as a model. Like in Solarized, the colorschemes come in a light \u00e2\u0080\u0093 and in a dark background version. It\u00e2\u0080\u0099s really just variations on the same idea, but each with it\u00e2\u0080\u0099s own color-value relations, interdependent on each other and their base (background-)color.  \r\n\r\nOne can find the demopage for these colorschemes at:\r\nhttp:\/\/atelierbram.github.io\/syntax-highlighting\/atelier-schemes\/ \r\n\r\nDownloads at the GitHub repo: \r\nhttps:\/\/github.com\/atelierbram\/vim-colors_atelier-schemes\r\n\r\nMore information on this particular colorscheme: \r\nhttp:\/\/atelierbram.github.io\/syntax-highlighting\/atelier-schemes\/dune\r\n\r\nScreenshot dark version: \r\nhttp:\/\/atelierbram.github.io\/syntax-highlighting\/assets\/img\/dune-dark_vim_640x425.png\r\n\r\nScreenshot light version: \r\nhttp:\/\/atelierbram.github.io\/syntax-highlighting\/assets\/img\/dune-light_vim_640x425.png\r\n\r\nChanges:\r\nhttp:\/\/atelierbram.github.io\/syntax-highlighting\/atelier-schemes\/demo\/changes-03-2015.html#dune","install_details":"Install in ~\/.vim\/colors, or ~\\vimfiles\\colors on Windows. \r\n\r\nor\r\n\r\nPathogen installation (recommended)\r\n\r\n1.  Download and install Tim Pope's Pathogen: https:\/\/github.com\/tpope\/vim-pathogen\r\n\r\n2. download or clone this repo on Github: https:\/\/github.com\/atelierbram\/vim-colors_atelier-schemes\r\n\r\n3.  Next, move or clone the `vim-colors_atelier-schemes` directory so that it is\r\na subdirectory of the `.vim\/bundle` directory.\r\n\r\n$ cd ~\/.vim\/bundle\r\n$ git clone https:\/\/github.com\/atelierbram\/vim-colors_atelier-schemes.git\r\n\r\nTry it out with \r\n:colorscheme base16-atelierdune\r\n\r\nwith either light or dark background:\r\n:set bg=light \r\n:set bg=dark\r\n\r\nIf you want to make it the default, add that command to your vimrc or gvimrc. ","5":"Install in ~\/.vim\/colors, or ~\\vimfiles\\colors on Windows. \r\n\r\nor\r\n\r\nPathogen installation (recommended)\r\n\r\n1.  Download and install Tim Pope's Pathogen: https:\/\/github.com\/tpope\/vim-pathogen\r\n\r\n2. download or clone this repo on Github: https:\/\/github.com\/atelierbram\/vim-colors_atelier-schemes\r\n\r\n3.  Next, move or clone the `vim-colors_atelier-schemes` directory so that it is\r\na subdirectory of the `.vim\/bundle` directory.\r\n\r\n$ cd ~\/.vim\/bundle\r\n$ git clone https:\/\/github.com\/atelierbram\/vim-colors_atelier-schemes.git\r\n\r\nTry it out with \r\n:colorscheme base16-atelierdune\r\n\r\nwith either light or dark background:\r\n:set bg=light \r\n:set bg=dark\r\n\r\nIf you want to make it the default, add that command to your vimrc or gvimrc. ","first_name":"Bram","6":"Bram","last_name":"de Haan","7":"de Haan","releases":[{"0":"4705","vim_version":"7.0","1":"7.0","script_version":"1.1","2":"1.1","version_comment":"Changed value for yellow (slightly darker): base0A changed from #cfb017 to #ae9513","3":"Changed value for yellow (slightly darker): base0A changed from #cfb017 to #ae9513","package":"base16-atelierdune.vim","4":"base16-atelierdune.vim","src_id":"23100","5":"23100","creation_date":"1427560975","6":"1427560975"}]},"4704":{"script_id":"4704","0":"4704","script_name":"vim-vsnumber","1":"vim-vsnumber","script_type":"utility","2":"utility","summary":"vim script to make the number sort in selection area","3":"vim script to make the number sort in selection area","description":"vim plugin to make value of number sort in select text,\r\nrargo.m@gmail.com\r\n\r\nUsage: use ctrl-v V v to select text,and call vsnumber to make it's value change\r\n\r\nfor example:\r\norigin text:\r\n\t\t=1--1--3=====9=\r\n\t\t=5--4--6=====9=\r\n\r\nselect text using ctrl-v( '|' repersents select position):\r\n\t\t=|1--1--3|=====9=\r\n\t\t=|5--4--6|=====9=\r\n\r\nif call :'<,'>VsNumber 9 1\r\nthe result is:\r\n\t\t=9--10--11=====9=\r\n\t\t=12--13--14=====9=\r\n\t\tthat is the number in select text became sort start from 9, increase by 1\r\n\r\nif call :'<,'>VsNumber . -1  (\".\" mean's change uppon on current value)\r\nthe result is:\r\n\t\t=0--0--2=====9=\r\n\t\t=4--3--5=====9=\r\n\t\tthat is each number in select text sub by 1\r\n\r\nIt's useful when you has the following text, and you want to correct the suqenuce\r\n\t1. line1\r\n\t2. line2\r\n\t7. line3\r\n\t6. line4\r\nto:\r\n\t1. line1\r\n\t2. line2\r\n\t3. line3\r\n\t4. line4\r\n\r\nalso, useful when you want to make a large suqenuce numbers like below:\r\n\tenum const_logic {\r\n\t\tint value0 = 0,\r\n\t\tint value1 = 1,\r\n\t\tint value2 = 2,\r\n\t\tint value3 = 3,\r\n\t\tint value4 = 4,\r\n\t\tint value5 = 5,\r\n\t\tint value6 = 6,\r\n\t\tint value7 = 7,\r\n\t\tint value8 = 8,\r\n\t\tint value9 = 9,\r\n\t\t...\r\n\t};\r\n\r\n","4":"vim plugin to make value of number sort in select text,\r\nrargo.m@gmail.com\r\n\r\nUsage: use ctrl-v V v to select text,and call vsnumber to make it's value change\r\n\r\nfor example:\r\norigin text:\r\n\t\t=1--1--3=====9=\r\n\t\t=5--4--6=====9=\r\n\r\nselect text using ctrl-v( '|' repersents select position):\r\n\t\t=|1--1--3|=====9=\r\n\t\t=|5--4--6|=====9=\r\n\r\nif call :'<,'>VsNumber 9 1\r\nthe result is:\r\n\t\t=9--10--11=====9=\r\n\t\t=12--13--14=====9=\r\n\t\tthat is the number in select text became sort start from 9, increase by 1\r\n\r\nif call :'<,'>VsNumber . -1  (\".\" mean's change uppon on current value)\r\nthe result is:\r\n\t\t=0--0--2=====9=\r\n\t\t=4--3--5=====9=\r\n\t\tthat is each number in select text sub by 1\r\n\r\nIt's useful when you has the following text, and you want to correct the suqenuce\r\n\t1. line1\r\n\t2. line2\r\n\t7. line3\r\n\t6. line4\r\nto:\r\n\t1. line1\r\n\t2. line2\r\n\t3. line3\r\n\t4. line4\r\n\r\nalso, useful when you want to make a large suqenuce numbers like below:\r\n\tenum const_logic {\r\n\t\tint value0 = 0,\r\n\t\tint value1 = 1,\r\n\t\tint value2 = 2,\r\n\t\tint value3 = 3,\r\n\t\tint value4 = 4,\r\n\t\tint value5 = 5,\r\n\t\tint value6 = 6,\r\n\t\tint value7 = 7,\r\n\t\tint value8 = 8,\r\n\t\tint value9 = 9,\r\n\t\t...\r\n\t};\r\n\r\n","install_details":"unzip the file in plugin to your ~\/.vim\/plugin\/","5":"unzip the file in plugin to your ~\/.vim\/plugin\/","first_name":"rargo","6":"rargo","last_name":"ye","7":"ye","releases":[{"0":"4704","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"vim-vsnumber.tar.gz","4":"vim-vsnumber.tar.gz","src_id":"20705","5":"20705","creation_date":"1377336746","6":"1377336746"}]},"4703":{"script_id":"4703","0":"4703","script_name":"surfer.vim","1":"surfer.vim","script_type":"utility","2":"utility","summary":"Code navigation built upon Ctags","3":"Code navigation built upon Ctags","description":"\r\nSurfer provides nice user interface for code navigation built on top of Ctags.\r\n\r\nGo to https:\/\/github.com\/gcmt\/surfer.vim for a quick introduction to Surfer.","4":"\r\nSurfer provides nice user interface for code navigation built on top of Ctags.\r\n\r\nGo to https:\/\/github.com\/gcmt\/surfer.vim for a quick introduction to Surfer.","install_details":"\r\nRequirements: \r\n\r\n  * Vim 7.3+ compiled with support for python 2.x \r\n  * Exuberant Ctags\r\n\r\nQuick installation:\r\n\r\n  1. Install Exuberant Ctags\r\n\r\n  2. Install Surfer with Vundle or Pathogen \r\n\r\n  3. [For non-Windows users] Go to the plugin root directory and execute .\/install.sh\r\n      to complete the installation.\r\n\r\n  4. Map the :Surf command and enjoy!","5":"\r\nRequirements: \r\n\r\n  * Vim 7.3+ compiled with support for python 2.x \r\n  * Exuberant Ctags\r\n\r\nQuick installation:\r\n\r\n  1. Install Exuberant Ctags\r\n\r\n  2. Install Surfer with Vundle or Pathogen \r\n\r\n  3. [For non-Windows users] Go to the plugin root directory and execute .\/install.sh\r\n      to complete the installation.\r\n\r\n  4. Map the :Surf command and enjoy!","first_name":"geck","6":"geck","last_name":" ","7":" ","releases":[{"0":"4703","vim_version":"7.3","1":"7.3","script_version":"2.1.2","2":"2.1.2","version_comment":"* Added notification system for letting the user know when the search component has been updated and needs to be recompiled. \r\n* Fixed all unicode related issues. \r\n* Various bug fixes.","3":"* Added notification system for letting the user know when the search component has been updated and needs to be recompiled. \r\n* Fixed all unicode related issues. \r\n* Various bug fixes.","package":"surfer-2.1.2.zip","4":"surfer-2.1.2.zip","src_id":"21382","5":"21382","creation_date":"1390742366","6":"1390742366"}]},"4702":{"script_id":"4702","0":"4702","script_name":"tex-fold","1":"tex-fold","script_type":"ftplugin","2":"ftplugin","summary":"Easy TeX folding","3":"Easy TeX folding","description":"A light-weight alternative to vim-latexsuite's folding. It uses a simple foldexpr to capture \\sections, \\subsections and blocks defined with \\begin and \\end. However, you are not limited to the foldexpr method and can still define manual markers, e.g.\r\n\r\n%{{{ Packages\r\n\\usepackage{hyperref}\r\n%}}}","4":"A light-weight alternative to vim-latexsuite's folding. It uses a simple foldexpr to capture \\sections, \\subsections and blocks defined with \\begin and \\end. However, you are not limited to the foldexpr method and can still define manual markers, e.g.\r\n\r\n%{{{ Packages\r\n\\usepackage{hyperref}\r\n%}}}","install_details":"Use either Pathogen, Vundle or NeoBundle, e.g. add\r\n\r\n    Bundle 'matze\/vim-tex.fold'\r\n\r\nto your .vimrc or install manually using the standard Vim way. For more information have a look at\r\n\r\n    http:\/\/vimdoc.sourceforge.net\/htmldoc\/usr_05.html#add-plugin","5":"Use either Pathogen, Vundle or NeoBundle, e.g. add\r\n\r\n    Bundle 'matze\/vim-tex.fold'\r\n\r\nto your .vimrc or install manually using the standard Vim way. For more information have a look at\r\n\r\n    http:\/\/vimdoc.sourceforge.net\/htmldoc\/usr_05.html#add-plugin","first_name":"Matthias","6":"Matthias","last_name":"Vogelgesang","7":"Vogelgesang","releases":[{"0":"4702","vim_version":"7.0","1":"7.0","script_version":"1.3","2":"1.3","version_comment":"* Add g:tex_fold_additional_envs. Thanks @fwang2.","3":"* Add g:tex_fold_additional_envs. Thanks @fwang2.","package":"vim-tex-fold-1.3.tar.gz","4":"vim-tex-fold-1.3.tar.gz","src_id":"22397","5":"22397","creation_date":"1409573565","6":"1409573565"},{"0":"4702","vim_version":"7.0","1":"7.0","script_version":"1.2","2":"1.2","version_comment":"* Fixes incompatibility issue with Vim 7.4\r\n* Fold figure, tabular and align environments. Thanks @DanielAndreasen.\r\n","3":"* Fixes incompatibility issue with Vim 7.4\r\n* Fold figure, tabular and align environments. Thanks @DanielAndreasen.\r\n","package":"vim-tex-fold-1.2.tar.gz","4":"vim-tex-fold-1.2.tar.gz","src_id":"22112","5":"22112","creation_date":"1404148436","6":"1404148436"},{"0":"4702","vim_version":"7.0","1":"7.0","script_version":"1.1","2":"1.1","version_comment":"* Fixes incompatibility issue with NERDcommenter.","3":"* Fixes incompatibility issue with NERDcommenter.","package":"vim-tex-fold-1.1.tar.gz","4":"vim-tex-fold-1.1.tar.gz","src_id":"21811","5":"21811","creation_date":"1398238007","6":"1398238007"},{"0":"4702","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"vim-tex-fold-1.0.tar.gz","4":"vim-tex-fold-1.0.tar.gz","src_id":"20698","5":"20698","creation_date":"1377162968","6":"1377162968"}]},"4701":{"script_id":"4701","0":"4701","script_name":"mlp.vim","1":"mlp.vim","script_type":"color scheme","2":"color scheme","summary":"My Little Pony-Inspired Color Scheme","3":"My Little Pony-Inspired Color Scheme","description":"Tried to use colors from actual character models, but there were some difficult decisions for visibility. Looking for feedback and for someone to improve on the theme to make it more eye-friendly.","4":"Tried to use colors from actual character models, but there were some difficult decisions for visibility. Looking for feedback and for someone to improve on the theme to make it more eye-friendly.","install_details":"copy into the colors folder","5":"copy into the colors folder","first_name":"Alex","6":"Alex","last_name":"P","7":"P","releases":[{"0":"4701","vim_version":"7.2","1":"7.2","script_version":"7.2","2":"7.2","version_comment":"Initial upload","3":"Initial upload","package":"mlp.vim","4":"mlp.vim","src_id":"20682","5":"20682","creation_date":"1376932120","6":"1376932120"}]},"4700":{"script_id":"4700","0":"4700","script_name":"libxml2","1":"libxml2","script_type":"syntax","2":"syntax","summary":"syntax for libxml2","3":"syntax for libxml2","description":"I wrote a simple program to parse libxml2.devhelp and generate this syntax file","4":"I wrote a simple program to parse libxml2.devhelp and generate this syntax file","install_details":"","5":"","first_name":"wiky","6":"wiky","last_name":"L","7":"L","releases":[{"0":"4700","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"libxml2.vim","4":"libxml2.vim","src_id":"20676","5":"20676","creation_date":"1376892542","6":"1376892542"}]},"4699":{"script_id":"4699","0":"4699","script_name":"webkitgtk","1":"webkitgtk","script_type":"syntax","2":"syntax","summary":"syntax for webkitgtk-3.0","3":"syntax for webkitgtk-3.0","description":"I wrote a simple program to parse webkitgtk.devhelp2 and generate this syntax file.","4":"I wrote a simple program to parse webkitgtk.devhelp2 and generate this syntax file.","install_details":"","5":"","first_name":"wiky","6":"wiky","last_name":"L","7":"L","releases":[{"0":"4699","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"webkitgtk.vim","4":"webkitgtk.vim","src_id":"20675","5":"20675","creation_date":"1376892410","6":"1376892410"}]},"4698":{"script_id":"4698","0":"4698","script_name":"nextfile.vim","1":"nextfile.vim","script_type":"utility","2":"utility","summary":"Vim plugin to open related files by key(i.e. \\n or any)","3":"Vim plugin to open related files by key(i.e. \\n or any)","description":"How it works\r\n\r\nWhen initialized, set related files\r\nIn vim window, when n is pressed\r\n\r\n1. Get the current file name\r\n2. Get the related files\r\n3. Open a window with related files and let you to choose which file to open\r\n   1) <Enter> to open in a current window\r\n   2) \"o\" to open in a horizontally splitted window\r\n   3) \"v\" to open in a vertically split window\r\n\r\nFor Rails developers, there is pre-defined mapping like the following. You may want to change this. If so, you can re-define this in your .vimrc\r\n    let g:nextFilesMap[\"Ruby On Rails\"] = {\r\n      \\ \"Ruby On Rails\" : {\r\n        \\ \"Controller\" : { \"expression\" : \"app\/controllers\/(.*)_controller.rb$\", \"transform\" : \"pluralize\" },\r\n        \\ \"Funtional Test\" : { \"expression\" : \"test\/functional\/(.*)_controller_test.rb$\", \"transform\" : \"pluralize\" },\r\n        \\ \"View\" : { \"expression\" : \"app\/views\/(.*)\/\", \"transform\" : \"pluralize\" },\r\n        \\ \"Model\" : { \"expression\" : \"app\/models\/(.*).rb$\", \"transform\" : \"singularize\" },\r\n        \\ \"Unit Test\" : { \"expression\" : \"test\/unit\/(.*)_test.rb$\", \"transform\" : \"singularize\" }\r\n      \\ }\r\n    \\ }\r\n\r\nFor screenshot and source code, visit https:\/\/github.com\/bighostkim\/nextfile.vim,\r\n and if you want to make this better, please log an issue or fork this repository.\r\n\r\nIf you like this, you may like files.vim also,  https:\/\/github.com\/bighostkim\/files.vim.\r\n","4":"How it works\r\n\r\nWhen initialized, set related files\r\nIn vim window, when n is pressed\r\n\r\n1. Get the current file name\r\n2. Get the related files\r\n3. Open a window with related files and let you to choose which file to open\r\n   1) <Enter> to open in a current window\r\n   2) \"o\" to open in a horizontally splitted window\r\n   3) \"v\" to open in a vertically split window\r\n\r\nFor Rails developers, there is pre-defined mapping like the following. You may want to change this. If so, you can re-define this in your .vimrc\r\n    let g:nextFilesMap[\"Ruby On Rails\"] = {\r\n      \\ \"Ruby On Rails\" : {\r\n        \\ \"Controller\" : { \"expression\" : \"app\/controllers\/(.*)_controller.rb$\", \"transform\" : \"pluralize\" },\r\n        \\ \"Funtional Test\" : { \"expression\" : \"test\/functional\/(.*)_controller_test.rb$\", \"transform\" : \"pluralize\" },\r\n        \\ \"View\" : { \"expression\" : \"app\/views\/(.*)\/\", \"transform\" : \"pluralize\" },\r\n        \\ \"Model\" : { \"expression\" : \"app\/models\/(.*).rb$\", \"transform\" : \"singularize\" },\r\n        \\ \"Unit Test\" : { \"expression\" : \"test\/unit\/(.*)_test.rb$\", \"transform\" : \"singularize\" }\r\n      \\ }\r\n    \\ }\r\n\r\nFor screenshot and source code, visit https:\/\/github.com\/bighostkim\/nextfile.vim,\r\n and if you want to make this better, please log an issue or fork this repository.\r\n\r\nIf you like this, you may like files.vim also,  https:\/\/github.com\/bighostkim\/files.vim.\r\n","install_details":"Install it with Vundle\r\n   \r\n    Bundle 'bighostkim\/nextfile.vim'\r\n\r\nOr, download the following files into ~\/.vim\/plugin directory. Two .txt files, singular_expressions.txt and plural_expressoins.txt, are used to convert file names into singular and plural word in English.\r\n\r\n. nextfile.vim\r\n. singular_expressions.txt\r\n. plural_expressions.txt\r\n\r\nTo your ~\/.vimrc, add a keyboard map to call NextFile() function\r\n\r\n    nmap <Leader>n <ESC>:call NextFile()<CR>","5":"Install it with Vundle\r\n   \r\n    Bundle 'bighostkim\/nextfile.vim'\r\n\r\nOr, download the following files into ~\/.vim\/plugin directory. Two .txt files, singular_expressions.txt and plural_expressoins.txt, are used to convert file names into singular and plural word in English.\r\n\r\n. nextfile.vim\r\n. singular_expressions.txt\r\n. plural_expressions.txt\r\n\r\nTo your ~\/.vimrc, add a keyboard map to call NextFile() function\r\n\r\n    nmap <Leader>n <ESC>:call NextFile()<CR>","first_name":"Allen","6":"Allen","last_name":"Kim","7":"Kim","releases":[{"0":"4698","vim_version":"7.0","1":"7.0","script_version":"0.4","2":"0.4","version_comment":"Open\/Close directory by <Enter>","3":"Open\/Close directory by <Enter>","package":"nextfile.vim.zip","4":"nextfile.vim.zip","src_id":"20813","5":"20813","creation_date":"1379393432","6":"1379393432"},{"0":"4698","vim_version":"7.0","1":"7.0","script_version":"0.3","2":"0.3","version_comment":"help line one the top, most related file on the next line with cursor","3":"help line one the top, most related file on the next line with cursor","package":"nextfile.vim.zip","4":"nextfile.vim.zip","src_id":"20774","5":"20774","creation_date":"1378753443","6":"1378753443"},{"0":"4698","vim_version":"7.0","1":"7.0","script_version":"0.2","2":"0.2","version_comment":"changed file switching to file browser so that we can open by split or vsplit","3":"changed file switching to file browser so that we can open by split or vsplit","package":"nextfile.vim.zip","4":"nextfile.vim.zip","src_id":"20756","5":"20756","creation_date":"1378423902","6":"1378423902"},{"0":"4698","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"nextfile.vim","4":"nextfile.vim","src_id":"20673","5":"20673","creation_date":"1376860859","6":"1376860859"}]},"4697":{"script_id":"4697","0":"4697","script_name":"perl-nextmethod","1":"perl-nextmethod","script_type":"utility","2":"utility","summary":"]m, ]M, [m, [M next\/previous perl method motions","3":"]m, ]M, [m, [M next\/previous perl method motions","description":"This plugin adds the ]m, ]M, [m, [M motions for perl scripts. \r\n\r\nVim already supports these motions but they are available only for certain languages.\r\n\r\n]m - jump to the next perl subroutine start\r\n]M - jump to the next perl subroutine end\r\n[m - jump to previous perl subroutine start\r\n[M - jump to previous perl subroutine end\r\n\r\nCAVEATS:\r\n1. Does not preserve the jump list nor the ` mark (previous position)\r\n2. There is small issue when using it with operators (e.g. yank copies the subroutine but leaves the last brace off)\r\n3. Visual selection operator is unsupported\r\n\r\nGuthub repository:\r\nhttps:\/\/github.com\/catalinciurea\/perl-nextmethod","4":"This plugin adds the ]m, ]M, [m, [M motions for perl scripts. \r\n\r\nVim already supports these motions but they are available only for certain languages.\r\n\r\n]m - jump to the next perl subroutine start\r\n]M - jump to the next perl subroutine end\r\n[m - jump to previous perl subroutine start\r\n[M - jump to previous perl subroutine end\r\n\r\nCAVEATS:\r\n1. Does not preserve the jump list nor the ` mark (previous position)\r\n2. There is small issue when using it with operators (e.g. yank copies the subroutine but leaves the last brace off)\r\n3. Visual selection operator is unsupported\r\n\r\nGuthub repository:\r\nhttps:\/\/github.com\/catalinciurea\/perl-nextmethod","install_details":"1. Untar the archive into your ~\/.vim directory\r\n2. :helptags ~\/.vim\/doc","5":"1. Untar the archive into your ~\/.vim directory\r\n2. :helptags ~\/.vim\/doc","first_name":"Catalin","6":"Catalin","last_name":"Ciurea","7":"Ciurea","releases":[{"0":"4697","vim_version":"7.0","1":"7.0","script_version":"0.01","2":"0.01","version_comment":"Initial upload","3":"Initial upload","package":"perl-nextmethod.tar.gz","4":"perl-nextmethod.tar.gz","src_id":"20671","5":"20671","creation_date":"1376823648","6":"1376823648"}]},"4696":{"script_id":"4696","0":"4696","script_name":"liquidfold.vim","1":"liquidfold.vim","script_type":"syntax","2":"syntax","summary":"liquidfold.vim provides Vim syntax folding for Liquid templates. It supports any","3":"liquidfold.vim provides Vim syntax folding for Liquid templates. It supports any","description":"# liquidfold.vim\r\n\r\nliquidfold.vim provides Vim syntax folding for Liquid templates (http:\/\/liquidmarkup.org\/). It supports any tags that have an associated end tag, including:\r\n\r\n    {% comment %} {% endcomment %}\r\n    {% raw %} {% endraw %}\r\n    {% if %} {% endif %}\r\n    {% case %} {% endcase %}\r\n    {% for %} {% endfor %}\r\n    {% tablerow %} {% endtablerow %}\r\n    {% block %} {% endblock %}\r\n\r\n\r\n## Installation\r\n\r\nUse pathogen.vim (https:\/\/github.com\/tpope\/vim-pathogen), and unpack liquidfold.vim into your ~\/.vim\/bundle directory.\r\n\r\n\r\n## Customization\r\n\r\nBy default, all foldable tags will be folded. To specify a subset of these tags for folding, set g:liquidfold_words in your vimrc.\r\n\r\n    let g:liquidfold_words = \"block,if\"\r\n\r\n\r\n## Source\r\n\r\nliquidfold.vim is maintained at:\r\n\r\nhttps:\/\/bitbucket.org\/bbakersmith\/liquidfold.vim\r\n\r\nhttps:\/\/github.com\/bbakersmith\/liquidfold.vim\r\n\r\n\r\n## License\r\n\r\nThe MIT License (MIT)\r\n\r\nCopyright (c) 2013 Ben Baker-Smith\r\n\r\nPermission is hereby granted, free of charge, to any person obtaining a copy\r\nof this software and associated documentation files (the \\\"Software\\\"), to deal\r\nin the Software without restriction, including without limitation the rights\r\nto use, copy, modify, merge, publish, distribute, sublicense, and\/or sell\r\ncopies of the Software, and to permit persons to whom the Software is\r\nfurnished to do so, subject to the following conditions:\r\n\r\nThe above copyright notice and this permission notice shall be included in\r\nall copies or substantial portions of the Software.\r\n\r\nTHE SOFTWARE IS PROVIDED \\\"AS IS\\\", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR\r\nIMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,\r\nFITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE\r\nAUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER\r\nLIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,\r\nOUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN\r\nTHE SOFTWARE.","4":"# liquidfold.vim\r\n\r\nliquidfold.vim provides Vim syntax folding for Liquid templates (http:\/\/liquidmarkup.org\/). It supports any tags that have an associated end tag, including:\r\n\r\n    {% comment %} {% endcomment %}\r\n    {% raw %} {% endraw %}\r\n    {% if %} {% endif %}\r\n    {% case %} {% endcase %}\r\n    {% for %} {% endfor %}\r\n    {% tablerow %} {% endtablerow %}\r\n    {% block %} {% endblock %}\r\n\r\n\r\n## Installation\r\n\r\nUse pathogen.vim (https:\/\/github.com\/tpope\/vim-pathogen), and unpack liquidfold.vim into your ~\/.vim\/bundle directory.\r\n\r\n\r\n## Customization\r\n\r\nBy default, all foldable tags will be folded. To specify a subset of these tags for folding, set g:liquidfold_words in your vimrc.\r\n\r\n    let g:liquidfold_words = \"block,if\"\r\n\r\n\r\n## Source\r\n\r\nliquidfold.vim is maintained at:\r\n\r\nhttps:\/\/bitbucket.org\/bbakersmith\/liquidfold.vim\r\n\r\nhttps:\/\/github.com\/bbakersmith\/liquidfold.vim\r\n\r\n\r\n## License\r\n\r\nThe MIT License (MIT)\r\n\r\nCopyright (c) 2013 Ben Baker-Smith\r\n\r\nPermission is hereby granted, free of charge, to any person obtaining a copy\r\nof this software and associated documentation files (the \\\"Software\\\"), to deal\r\nin the Software without restriction, including without limitation the rights\r\nto use, copy, modify, merge, publish, distribute, sublicense, and\/or sell\r\ncopies of the Software, and to permit persons to whom the Software is\r\nfurnished to do so, subject to the following conditions:\r\n\r\nThe above copyright notice and this permission notice shall be included in\r\nall copies or substantial portions of the Software.\r\n\r\nTHE SOFTWARE IS PROVIDED \\\"AS IS\\\", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR\r\nIMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,\r\nFITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE\r\nAUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER\r\nLIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,\r\nOUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN\r\nTHE SOFTWARE.","install_details":"","5":"","first_name":"Ben","6":"Ben","last_name":"Baker-Smith","7":"Baker-Smith","releases":[{"0":"4696","vim_version":"7.0","1":"7.0","script_version":"1.2","2":"1.2","version_comment":"Refactor to utilize ftdetect and autoload for lazy loading","3":"Refactor to utilize ftdetect and autoload for lazy loading","package":"liquidfold.vim.tar.gz","4":"liquidfold.vim.tar.gz","src_id":"20709","5":"20709","creation_date":"1377392690","6":"1377392690"},{"0":"4696","vim_version":"7.0","1":"7.0","script_version":"1.1","2":"1.1","version_comment":"Exclude single line statements from folding","3":"Exclude single line statements from folding","package":"liquidfold.vim.1.1.tar.gz","4":"liquidfold.vim.1.1.tar.gz","src_id":"20690","5":"20690","creation_date":"1376956256","6":"1376956256"},{"0":"4696","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"liquidfold.vim.tar.gz","4":"liquidfold.vim.tar.gz","src_id":"20669","5":"20669","creation_date":"1376776757","6":"1376776757"}]},"4695":{"script_id":"4695","0":"4695","script_name":"0x7A69_dark.vim","1":"0x7A69_dark.vim","script_type":"color scheme","2":"color scheme","summary":"0x7A69","3":"0x7A69","description":"Dark theme.","4":"Dark theme.","install_details":"Put 0x7A69_dark.vim in [vimfolder]\/colors","5":"Put 0x7A69_dark.vim in [vimfolder]\/colors","first_name":"John","6":"John","last_name":"Do","7":"Do","releases":[{"0":"4695","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"0x7A69_dark.vim","4":"0x7A69_dark.vim","src_id":"20665","5":"20665","creation_date":"1376698819","6":"1376698819"}]},"4694":{"script_id":"4694","0":"4694","script_name":"WSearch","1":"WSearch","script_type":"utility","2":"utility","summary":"Web Search Plugin","3":"Web Search Plugin","description":"Git: https:\/\/github.com\/countoren\/WSearch\r\n\r\nCommands:\r\n\r\nPressing tab when intreducing tag name will autocomplete.\r\nWhen using search commands search pattern will be copied to clipboard\r\nSite must start with http:\/\/ or https:\/\/ in order to be open in the browser else a file will be open.\r\nVim Feture Reminder - Functions can be autocomplete you can :wse and then tab in order to get :WSearch.\r\nWSearchInit - Start new WSearch repository(folder) in the current (PWD) folder\r\n\r\nWSearchSaveTagAndSite [Tag] [Site] - Save tag and a site .WSearch folder must exists (WSearchInit) . Saving on the same tag will replace the old value. Url can have {WSearch} in it , this will be replaced when searching. Example:\r\n\r\n:WSearchSaveTagAndSite google https:\/\/www.google.com\/search?q={WSearch}\r\nWSearchShow [Tag] - Shows a url ralted for this Tag\r\n\r\nWSearchRemoveTag [Tag] - Removes the specified Tag\r\n\r\nSearchCommands:\r\n\r\nWSearch [SearchContent] - Will get the latesturl (last saved or WSearchATag ) and will reaplce the {WSearch} with SearchContent\r\n\r\nWSearchATag [Tag] - The same as WSearch except getting the url related to Tag Example:\r\n\r\n:WSearchATag google\r\nWSearchATag [Tag] [SearchConectent] - the same as WSearch with SearchContent except getting the url related to Tag Example:\r\n\r\n:WSearchATag google hello WSearch","4":"Git: https:\/\/github.com\/countoren\/WSearch\r\n\r\nCommands:\r\n\r\nPressing tab when intreducing tag name will autocomplete.\r\nWhen using search commands search pattern will be copied to clipboard\r\nSite must start with http:\/\/ or https:\/\/ in order to be open in the browser else a file will be open.\r\nVim Feture Reminder - Functions can be autocomplete you can :wse and then tab in order to get :WSearch.\r\nWSearchInit - Start new WSearch repository(folder) in the current (PWD) folder\r\n\r\nWSearchSaveTagAndSite [Tag] [Site] - Save tag and a site .WSearch folder must exists (WSearchInit) . Saving on the same tag will replace the old value. Url can have {WSearch} in it , this will be replaced when searching. Example:\r\n\r\n:WSearchSaveTagAndSite google https:\/\/www.google.com\/search?q={WSearch}\r\nWSearchShow [Tag] - Shows a url ralted for this Tag\r\n\r\nWSearchRemoveTag [Tag] - Removes the specified Tag\r\n\r\nSearchCommands:\r\n\r\nWSearch [SearchContent] - Will get the latesturl (last saved or WSearchATag ) and will reaplce the {WSearch} with SearchContent\r\n\r\nWSearchATag [Tag] - The same as WSearch except getting the url related to Tag Example:\r\n\r\n:WSearchATag google\r\nWSearchATag [Tag] [SearchConectent] - the same as WSearch with SearchContent except getting the url related to Tag Example:\r\n\r\n:WSearchATag google hello WSearch","install_details":"Installation:\r\n\r\nusing pathogen.vim : download folder into your bundle folder.\r\n\r\nelse: You can allways source autoload\/WSearch.vim In your vimrc append to file source [PATHTHEPLUGIN]\/WSearch\/autoload\/WSearch.vim Or from the command line :source [PATHTHEPLUGIN]\/WSearch\/autoload\/WSearch.vim","5":"Installation:\r\n\r\nusing pathogen.vim : download folder into your bundle folder.\r\n\r\nelse: You can allways source autoload\/WSearch.vim In your vimrc append to file source [PATHTHEPLUGIN]\/WSearch\/autoload\/WSearch.vim Or from the command line :source [PATHTHEPLUGIN]\/WSearch\/autoload\/WSearch.vim","first_name":"Oren","6":"Oren","last_name":"Rozen","7":"Rozen","releases":[{"0":"4694","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"WSearch1.0.zip","4":"WSearch1.0.zip","src_id":"20661","5":"20661","creation_date":"1376618737","6":"1376618737"}]},"4693":{"script_id":"4693","0":"4693","script_name":"fixkey","1":"fixkey","script_type":"utility","2":"utility","summary":"Use non-ASCII keys in console Vim","3":"Use non-ASCII keys in console Vim","description":"Fixkey helps Vim use the non-ASCII keys of a terminal emulator, permitting\r\nmapping of several classes of characters, including:\r\n\r\n- Alt-lowercase letters (<M-a> - <M-z>).\r\n- Alt-uppercase letters (<M-A> - <M-Z>), except <M-O> due to keycode\r\n  ambiguity).\r\n- Function keys with no modifiers or combinations of shift, control, and alt:\r\n  <F1> - <F12>, <S-F1> - <S-F12>, ..., <M-C-S-F1> - <M-C-S-F12>.\r\n  *Note* not all combination of terminal and environment send all of these.\r\n- Arrow keys with no modifiers or combinations of shift, control, and alt:\r\n  <Up>, <Down>, <Left>, <Right>, <S-Up>, <S-Down>, <S-Left>, <S-Right>, ..., \r\n  <M-C-S-Up>, <M-C-S-Down>, <M-C-S-Left>, <M-C-S-Right>.\r\n- Home and End keys with no modifiers or combinations of shift, control, and\r\n  alt: <Home>, <End>, <S-Home>, <S-End>, ..., <M-C-S-Home>, <M-C-S-End>.\r\n- <S-Enter> (few terminals).\r\n- <M-Enter> (not all terminals).\r\n\r\nNow, console Vim users can map keys like Gvim users, e.g.::\r\n\r\n  \" Map Alt-q to re-wrap a paragraph.\r\n  :nnoremap <M-q> gqap\r\n\r\nSee documentation in doc\/fixkey.txt for installation instructions and\r\nterminal setup.\r\n\r\nDeveloped by Michael Henry (vim at drmikehenry.com).\r\n\r\nDistributed under Vim's license.\r\n\r\nGit repository:   https:\/\/github.com\/drmikehenry\/vim-fixkey\r\n","4":"Fixkey helps Vim use the non-ASCII keys of a terminal emulator, permitting\r\nmapping of several classes of characters, including:\r\n\r\n- Alt-lowercase letters (<M-a> - <M-z>).\r\n- Alt-uppercase letters (<M-A> - <M-Z>), except <M-O> due to keycode\r\n  ambiguity).\r\n- Function keys with no modifiers or combinations of shift, control, and alt:\r\n  <F1> - <F12>, <S-F1> - <S-F12>, ..., <M-C-S-F1> - <M-C-S-F12>.\r\n  *Note* not all combination of terminal and environment send all of these.\r\n- Arrow keys with no modifiers or combinations of shift, control, and alt:\r\n  <Up>, <Down>, <Left>, <Right>, <S-Up>, <S-Down>, <S-Left>, <S-Right>, ..., \r\n  <M-C-S-Up>, <M-C-S-Down>, <M-C-S-Left>, <M-C-S-Right>.\r\n- Home and End keys with no modifiers or combinations of shift, control, and\r\n  alt: <Home>, <End>, <S-Home>, <S-End>, ..., <M-C-S-Home>, <M-C-S-End>.\r\n- <S-Enter> (few terminals).\r\n- <M-Enter> (not all terminals).\r\n\r\nNow, console Vim users can map keys like Gvim users, e.g.::\r\n\r\n  \" Map Alt-q to re-wrap a paragraph.\r\n  :nnoremap <M-q> gqap\r\n\r\nSee documentation in doc\/fixkey.txt for installation instructions and\r\nterminal setup.\r\n\r\nDeveloped by Michael Henry (vim at drmikehenry.com).\r\n\r\nDistributed under Vim's license.\r\n\r\nGit repository:   https:\/\/github.com\/drmikehenry\/vim-fixkey\r\n","install_details":"","5":"","first_name":"Michael","6":"Michael","last_name":"Henry","7":"Henry","releases":[{"0":"4693","vim_version":"7.0","1":"7.0","script_version":"0.3.15","2":"0.3.15","version_comment":"- Fix regression in version 0.3.14 for terminals that lack |TermResponse|.\r\n  Now, in addition to |TermResponse|, Fixkey watches for the |VimEnter|\r\n  autocmd to ensure Fixkey setup will always be invoked.  Notably tmux, PuTTY,\r\n  and Linux console do not trigger |TermResponse| autocmd events.\r\n","3":"- Fix regression in version 0.3.14 for terminals that lack |TermResponse|.\r\n  Now, in addition to |TermResponse|, Fixkey watches for the |VimEnter|\r\n  autocmd to ensure Fixkey setup will always be invoked.  Notably tmux, PuTTY,\r\n  and Linux console do not trigger |TermResponse| autocmd events.\r\n","package":"fixkey-0.3.15.zip","4":"fixkey-0.3.15.zip","src_id":"28435","5":"28435","creation_date":"1682810343","6":"1682810343"},{"0":"4693","vim_version":"7.0","1":"7.0","script_version":"0.3.14","2":"0.3.14","version_comment":"- Add `g:Fixkey_useTimestamps` to produce system calls visible to `strace` for\r\n  timing measurements.\r\n\r\n- Change `g:Fixkey_setupDelay` to be measured from reception of the\r\n  |TermResponse| autocmd instead of the start of Fixkey initialization.  This\r\n  removes some variability in startup times and makes the choice of delay\r\n  value easier.  The default delay is now 400 ms.  The previous default of 10\r\n  ms was guesswork based on user feedback showing that delaying even 0 ms was\r\n  sufficient; however, measurements provided by `g:Fixkey_useTimestamps` show\r\n  that the delays actually provided by Vim's timer mechanism were\r\n  substantially longer than what was requested, because timers may be\r\n  postponed while Vim is busy with various startup tasks.  Waiting until\r\n  |TermResponse| ensures that Vim has actually received the initial terminal\r\n  response.  Additional delay is needed to ensure Vim receives and processes\r\n  any responses to Vim's subsequent terminal queries.\r\n\r\n  This additional delay works around problems with newer Vim and\r\n  gnome-terminal.  The sequence `ESC P` is found in gnome-terminal's response\r\n  to some Vim query.  If Fixkey setup occurs before this response is received,\r\n  Vim misinterprets the `ESC P` as a keypress (Alt+P), corrupting the\r\n  processing of the response and causing the user's first keypress to be\r\n  swallowed.\r\n","3":"- Add `g:Fixkey_useTimestamps` to produce system calls visible to `strace` for\r\n  timing measurements.\r\n\r\n- Change `g:Fixkey_setupDelay` to be measured from reception of the\r\n  |TermResponse| autocmd instead of the start of Fixkey initialization.  This\r\n  removes some variability in startup times and makes the choice of delay\r\n  value easier.  The default delay is now 400 ms.  The previous default of 10\r\n  ms was guesswork based on user feedback showing that delaying even 0 ms was\r\n  sufficient; however, measurements provided by `g:Fixkey_useTimestamps` show\r\n  that the delays actually provided by Vim's timer mechanism were\r\n  substantially longer than what was requested, because timers may be\r\n  postponed while Vim is busy with various startup tasks.  Waiting until\r\n  |TermResponse| ensures that Vim has actually received the initial terminal\r\n  response.  Additional delay is needed to ensure Vim receives and processes\r\n  any responses to Vim's subsequent terminal queries.\r\n\r\n  This additional delay works around problems with newer Vim and\r\n  gnome-terminal.  The sequence `ESC P` is found in gnome-terminal's response\r\n  to some Vim query.  If Fixkey setup occurs before this response is received,\r\n  Vim misinterprets the `ESC P` as a keypress (Alt+P), corrupting the\r\n  processing of the response and causing the user's first keypress to be\r\n  swallowed.\r\n","package":"fixkey-0.3.14.zip","4":"fixkey-0.3.14.zip","src_id":"28398","5":"28398","creation_date":"1680383348","6":"1680383348"},{"0":"4693","vim_version":"7.0","1":"7.0","script_version":"0.3.13","2":"0.3.13","version_comment":"- Add support for Alt-shifted-numbers (<M-)>, <M-!>, ..., <M-(>).\r\n\r\n- Document that <M-M> doesn't work with PuTTY for some reason.\r\n\r\n- Avoid overriding a non-empty 'ttymouse' setting for tmux (thanks to Kevin MacMartin).\r\n\r\n- Allow setting g:Fixkey_termType in vimrc to override Fixkey's terminal detection algorithm.\r\n","3":"- Add support for Alt-shifted-numbers (<M-)>, <M-!>, ..., <M-(>).\r\n\r\n- Document that <M-M> doesn't work with PuTTY for some reason.\r\n\r\n- Avoid overriding a non-empty 'ttymouse' setting for tmux (thanks to Kevin MacMartin).\r\n\r\n- Allow setting g:Fixkey_termType in vimrc to override Fixkey's terminal detection algorithm.\r\n","package":"fixkey-0.3.13.zip","4":"fixkey-0.3.13.zip","src_id":"27489","5":"27489","creation_date":"1613719403","6":"1613719403"},{"0":"4693","vim_version":"7.0","1":"7.0","script_version":"0.3.12","2":"0.3.12","version_comment":"- Extend detection of TERM=linux to include TERM=linux-16color and similar (thanks to Andy Weidenbaum).\r\n","3":"- Extend detection of TERM=linux to include TERM=linux-16color and similar (thanks to Andy Weidenbaum).\r\n","package":"fixkey-0.3.12.zip","4":"fixkey-0.3.12.zip","src_id":"27488","5":"27488","creation_date":"1613719364","6":"1613719364"},{"0":"4693","vim_version":"7.0","1":"7.0","script_version":"0.3.11","2":"0.3.11","version_comment":"- Delay Fixkey setup at startup to avoid interfering with Vim's terminal\r\n  negotiations.  This works around issues with newer Xterm versions (see\r\n  https:\/\/github.com\/drmikehenry\/vim-fixkey\/issues\/11).  Startup delay is\r\n  controlled via |g:Fixkey_setupDelay|.\r\n\r\n- Silently skip Fixkey setup when running with Neovim.  Fixkey's features\r\n  are not required on Neovim, as that editor already supports mapping\r\n  Alt-keys natively.  As a convenience to users that share configuration\r\n  files between Vim and Neovim, Fixkey skips its initialization when Neovim\r\n  is detected.\r\n","3":"- Delay Fixkey setup at startup to avoid interfering with Vim's terminal\r\n  negotiations.  This works around issues with newer Xterm versions (see\r\n  https:\/\/github.com\/drmikehenry\/vim-fixkey\/issues\/11).  Startup delay is\r\n  controlled via |g:Fixkey_setupDelay|.\r\n\r\n- Silently skip Fixkey setup when running with Neovim.  Fixkey's features\r\n  are not required on Neovim, as that editor already supports mapping\r\n  Alt-keys natively.  As a convenience to users that share configuration\r\n  files between Vim and Neovim, Fixkey skips its initialization when Neovim\r\n  is detected.\r\n","package":"fixkey-0.3.11.zip","4":"fixkey-0.3.11.zip","src_id":"26710","5":"26710","creation_date":"1566764660","6":"1566764660"},{"0":"4693","vim_version":"7.0","1":"7.0","script_version":"0.3.10","2":"0.3.10","version_comment":"Support Alt-numbers (<M-0> - <M-9>), thanks to Ralf Vogler.","3":"Support Alt-numbers (<M-0> - <M-9>), thanks to Ralf Vogler.","package":"fixkey-0.3.10.zip","4":"fixkey-0.3.10.zip","src_id":"26430","5":"26430","creation_date":"1553378453","6":"1553378453"},{"0":"4693","vim_version":"7.0","1":"7.0","script_version":"0.3.9","2":"0.3.9","version_comment":"Clarify documentation about the need to configure Konsole.  This is a documentation-only change.\r\n","3":"Clarify documentation about the need to configure Konsole.  This is a documentation-only change.\r\n","package":"fixkey-0.3.9.zip","4":"fixkey-0.3.9.zip","src_id":"26149","5":"26149","creation_date":"1532638725","6":"1532638725"},{"0":"4693","vim_version":"7.0","1":"7.0","script_version":"0.3.8","2":"0.3.8","version_comment":"Work around TERM=tmux issue with mis-detected mouse settings that interfere with proper operation of <Home> and <End> keys.","3":"Work around TERM=tmux issue with mis-detected mouse settings that interfere with proper operation of <Home> and <End> keys.","package":"fixkey-0.3.8.zip","4":"fixkey-0.3.8.zip","src_id":"24582","5":"24582","creation_date":"1475629613","6":"1475629613"},{"0":"4693","vim_version":"7.0","1":"7.0","script_version":"0.3.7","2":"0.3.7","version_comment":"Fixup function keys and navigation keys (home\/end\/arrows\/etc.)\r\nfor xterm, konsole, and gnome-terminal.  This corrects a problem\r\nwith stock Fedora Linux vim, because Fedora patches Vim and\r\nexchanges the definitions for <F1> through <F4> with <xF1>\r\nthrough <xF4>.\r\n","3":"Fixup function keys and navigation keys (home\/end\/arrows\/etc.)\r\nfor xterm, konsole, and gnome-terminal.  This corrects a problem\r\nwith stock Fedora Linux vim, because Fedora patches Vim and\r\nexchanges the definitions for <F1> through <F4> with <xF1>\r\nthrough <xF4>.\r\n","package":"fixkey-0.3.7.zip","4":"fixkey-0.3.7.zip","src_id":"24094","5":"24094","creation_date":"1457827668","6":"1457827668"},{"0":"4693","vim_version":"7.0","1":"7.0","script_version":"0.3.6","2":"0.3.6","version_comment":"Support TERM=tmux.  Starting with version 2.1, tmux allows TERM to be \"tmux\" instead of just \"screen\".","3":"Support TERM=tmux.  Starting with version 2.1, tmux allows TERM to be \"tmux\" instead of just \"screen\".","package":"fixkey-0.3.6.zip","4":"fixkey-0.3.6.zip","src_id":"23682","5":"23682","creation_date":"1445560655","6":"1445560655"},{"0":"4693","vim_version":"7.0","1":"7.0","script_version":"0.3.5","2":"0.3.5","version_comment":"Add support for \\\"TERM=screen-it\\\" and similar (thanks to Kevin MacMartin) (updated for minor typo in documentation).","3":"Add support for \\\"TERM=screen-it\\\" and similar (thanks to Kevin MacMartin) (updated for minor typo in documentation).","package":"fixkey-0.3.5.zip","4":"fixkey-0.3.5.zip","src_id":"22267","5":"22267","creation_date":"1406463351","6":"1406463351"},{"0":"4693","vim_version":"7.0","1":"7.0","script_version":"0.3.3","2":"0.3.3","version_comment":"Add support for overlooked PuTTY-SCO keys <F1> to <F12>.","3":"Add support for overlooked PuTTY-SCO keys <F1> to <F12>.","package":"fixkey-0.3.3.zip","4":"fixkey-0.3.3.zip","src_id":"21900","5":"21900","creation_date":"1400360955","6":"1400360955"},{"0":"4693","vim_version":"7.0","1":"7.0","script_version":"0.3.2","2":"0.3.2","version_comment":"Documentation reorganization.","3":"Documentation reorganization.","package":"fixkey-0.3.2.zip","4":"fixkey-0.3.2.zip","src_id":"20876","5":"20876","creation_date":"1380817711","6":"1380817711"},{"0":"4693","vim_version":"7.0","1":"7.0","script_version":"0.3.1","2":"0.3.1","version_comment":"Restore cpoptions correctly.","3":"Restore cpoptions correctly.","package":"vim-fixkey-0.3.1.zip","4":"vim-fixkey-0.3.1.zip","src_id":"20830","5":"20830","creation_date":"1379930227","6":"1379930227"},{"0":"4693","vim_version":"7.0","1":"7.0","script_version":"0.3.0","2":"0.3.0","version_comment":"Add support for more modifier keys.  Now all combinations of Shift, Control, and Meta work with function keys, arrows, and home\/end (on supported terminals).","3":"Add support for more modifier keys.  Now all combinations of Shift, Control, and Meta work with function keys, arrows, and home\/end (on supported terminals).","package":"vim-fixkey-0.3.0.zip","4":"vim-fixkey-0.3.0.zip","src_id":"20710","5":"20710","creation_date":"1377434370","6":"1377434370"},{"0":"4693","vim_version":"7.0","1":"7.0","script_version":"0.2.3","2":"0.2.3","version_comment":"Add support for -bce and -s subvariants of screen (e.g., TERM=screen-256color-bce-s will now work).","3":"Add support for -bce and -s subvariants of screen (e.g., TERM=screen-256color-bce-s will now work).","package":"vim-fixkey-0.2.3.zip","4":"vim-fixkey-0.2.3.zip","src_id":"20691","5":"20691","creation_date":"1376956991","6":"1376956991"},{"0":"4693","vim_version":"7.0","1":"7.0","script_version":"0.2.2","2":"0.2.2","version_comment":"Add support for <M-Enter>, <S-Enter> for some terminals","3":"Add support for <M-Enter>, <S-Enter> for some terminals","package":"vim-fixkey-0.2.2.zip","4":"vim-fixkey-0.2.2.zip","src_id":"20672","5":"20672","creation_date":"1376832725","6":"1376832725"},{"0":"4693","vim_version":"7.0","1":"7.0","script_version":"0.2.1","2":"0.2.1","version_comment":"Initial upload","3":"Initial upload","package":"vim-fixkey-0.2.1.zip","4":"vim-fixkey-0.2.1.zip","src_id":"20651","5":"20651","creation_date":"1376525946","6":"1376525946"}]},"4692":{"script_id":"4692","0":"4692","script_name":"desertink.vim","1":"desertink.vim","script_type":"color scheme","2":"color scheme","summary":"Colorscheme based on desert","3":"Colorscheme based on desert","description":"This is a version of the default desert colorscheme with a darker background and more colorful foreground colors.\r\n\r\nIt also adds highlighting for folds, diffs, line numbers, signcolumn, completion menus, and cursor line\/column.\r\n\r\nThe colors are automatically converted for 88\/256 color terminals, adapted from http:\/\/www.vim.org\/scripts\/script.php?script_id=1243\r\n\r\nYou can find the latest version at https:\/\/github.com\/toupeira\/desertink.vim and see a screenshot at http:\/\/i.imgur.com\/DZ35F.png","4":"This is a version of the default desert colorscheme with a darker background and more colorful foreground colors.\r\n\r\nIt also adds highlighting for folds, diffs, line numbers, signcolumn, completion menus, and cursor line\/column.\r\n\r\nThe colors are automatically converted for 88\/256 color terminals, adapted from http:\/\/www.vim.org\/scripts\/script.php?script_id=1243\r\n\r\nYou can find the latest version at https:\/\/github.com\/toupeira\/desertink.vim and see a screenshot at http:\/\/i.imgur.com\/DZ35F.png","install_details":"1. Add the plugin to your bundles\r\n2. Load the colorscheme with \"colorscheme desertink\"","5":"1. Add the plugin to your bundles\r\n2. Load the colorscheme with \"colorscheme desertink\"","first_name":"Markus","6":"Markus","last_name":"Koller","7":"Koller","releases":[{"0":"4692","vim_version":"7.0","1":"7.0","script_version":"1.2","2":"1.2","version_comment":"Initial upload","3":"Initial upload","package":"desertink-1.2.tar.gz","4":"desertink-1.2.tar.gz","src_id":"20644","5":"20644","creation_date":"1376471464","6":"1376471464"}]},"4691":{"script_id":"4691","0":"4691","script_name":"movealong.vim","1":"movealong.vim","script_type":"utility","2":"utility","summary":"Context-aware motion commands","3":"Context-aware motion commands","description":"This plugin gives you commands to repeat a motion until either a specific word or syntax group is encountered, or an arbitrary expression returns true. It also skips over blank lines, punctuation and other syntax noise.\r\n\r\nSee https:\/\/github.com\/toupeira\/vim-movealong for the latest version and more information.","4":"This plugin gives you commands to repeat a motion until either a specific word or syntax group is encountered, or an arbitrary expression returns true. It also skips over blank lines, punctuation and other syntax noise.\r\n\r\nSee https:\/\/github.com\/toupeira\/vim-movealong for the latest version and more information.","install_details":"1. Add the plugin to your bundles\r\n2. Enable the default keymaps with \"let g:movealong_default_keys = 1\" in your .vimrc\r\n3. Override the default keys with \"g:movealong_default_maps\"","5":"1. Add the plugin to your bundles\r\n2. Enable the default keymaps with \"let g:movealong_default_keys = 1\" in your .vimrc\r\n3. Override the default keys with \"g:movealong_default_maps\"","first_name":"Markus","6":"Markus","last_name":"Koller","7":"Koller","releases":[{"0":"4691","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"movealong-1.0.tar.gz","4":"movealong-1.0.tar.gz","src_id":"20643","5":"20643","creation_date":"1376471384","6":"1376471384"}]},"4690":{"script_id":"4690","0":"4690","script_name":"oops_trace.vim","1":"oops_trace.vim","script_type":"patch","2":"patch","summary":"oops_trace.vim - Use tag-style lookups on Linux kernel oops backtraces.","3":"oops_trace.vim - Use tag-style lookups on Linux kernel oops backtraces.","description":"This script lets you use tag-style lookups (i.e. C-] ) on Linux kernel oops\r\nstack traces.  For this to work, you need the following:\r\n1) The log file with the stack trace needs to be recognized as having\r\n   filetype=messages, which is hopefully the default.  If not, run \r\n'set filetype=messages'.\r\n2) You need to have built your kernel with debug symbols\r\n   (CONFIG_DEBUG_INFO=y).\r\n3) Vim needs to have its PWD in your Linux build directory, or you need to\r\n   set up the g:oops_path global variable to your build directory.  i.e.:\r\n   let g:oops_path='\/home\/myuser\/linux-kernel'","4":"This script lets you use tag-style lookups (i.e. C-] ) on Linux kernel oops\r\nstack traces.  For this to work, you need the following:\r\n1) The log file with the stack trace needs to be recognized as having\r\n   filetype=messages, which is hopefully the default.  If not, run \r\n'set filetype=messages'.\r\n2) You need to have built your kernel with debug symbols\r\n   (CONFIG_DEBUG_INFO=y).\r\n3) Vim needs to have its PWD in your Linux build directory, or you need to\r\n   set up the g:oops_path global variable to your build directory.  i.e.:\r\n   let g:oops_path='\/home\/myuser\/linux-kernel'","install_details":"Just copy to your ~\/.vim\/plugin directory.","5":"Just copy to your ~\/.vim\/plugin directory.","first_name":"Ross","6":"Ross","last_name":"Zwisler","7":"Zwisler","releases":[{"0":"4690","vim_version":"7.0","1":"7.0","script_version":"1.4","2":"1.4","version_comment":"Some bug fixes and additional debug.","3":"Some bug fixes and additional debug.","package":"oops_trace.vim","4":"oops_trace.vim","src_id":"27443","5":"27443","creation_date":"1610520656","6":"1610520656"},{"0":"4690","vim_version":"7.0","1":"7.0","script_version":"1.3","2":"1.3","version_comment":"Fixed a few bugs and added a bit more debug for when things go wrong.","3":"Fixed a few bugs and added a bit more debug for when things go wrong.","package":"oops_trace.vim","4":"oops_trace.vim","src_id":"26352","5":"26352","creation_date":"1547693957","6":"1547693957"},{"0":"4690","vim_version":"7.0","1":"7.0","script_version":"1.2","2":"1.2","version_comment":"Trying again to fix issues with cloned function lookups.","3":"Trying again to fix issues with cloned function lookups.","package":"oops_trace.vim","4":"oops_trace.vim","src_id":"21066","5":"21066","creation_date":"1384890846","6":"1384890846"},{"0":"4690","vim_version":"7.0","1":"7.0","script_version":"1.1","2":"1.1","version_comment":"Fixed a regexp to deal with kernel functions that have been cloned by GCC.","3":"Fixed a regexp to deal with kernel functions that have been cloned by GCC.","package":"oops_trace.vim","4":"oops_trace.vim","src_id":"21017","5":"21017","creation_date":"1383934357","6":"1383934357"},{"0":"4690","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"oops_trace.vim","4":"oops_trace.vim","src_id":"20639","5":"20639","creation_date":"1376408133","6":"1376408133"}]},"4689":{"script_id":"4689","0":"4689","script_name":"vim-kitchen","1":"vim-kitchen","script_type":"utility","2":"utility","summary":"initial version","3":"initial version","description":"This plugin adds a :Kitchen command that runs test-kitchen, with tab completion of subcommands. It is intended to be used with test-kitchen 1.x.\r\n","4":"This plugin adds a :Kitchen command that runs test-kitchen, with tab completion of subcommands. It is intended to be used with test-kitchen 1.x.\r\n","install_details":"","5":"","first_name":"Mark","6":"Mark","last_name":"Cornick","7":"Cornick","releases":[{"0":"4689","vim_version":"7.0","1":"7.0","script_version":"1.0.0","2":"1.0.0","version_comment":"Initial upload","3":"Initial upload","package":"vim-kitchen-1.0.0.tar.gz","4":"vim-kitchen-1.0.0.tar.gz","src_id":"20634","5":"20634","creation_date":"1376325903","6":"1376325903"}]},"4688":{"script_id":"4688","0":"4688","script_name":"simple_highlighting","1":"simple_highlighting","script_type":"utility","2":"utility","summary":"Easily highlight multiple words in all buffers and search through them","3":"Easily highlight multiple words in all buffers and search through them","description":"==============================================================================\r\nSection 1: Description                               *simple_highlighting*\r\n\r\nScript is designed to be easy and quick to use and satisfy the following\r\nfunctionality:\r\n1. Highlight multiple different words in multiple different highlight styles.\r\n2. Keep the highlights between buffers.\r\n3. Change search pattern to a highlighted style\r\n\r\n==============================================================================\r\nSection 2: Brief example of usage:\r\n  * Place your cursor on a word and use \"\\h\" to highlight it with default slot.\r\n  * Type \"\\h\" over another word to add it to the default slot\r\n  * Run \"\\h\" on a word already in the default highlight slot to remove it\r\n  * \":Hd 3\" will change the default slot to slot 3\r\n  * 5\\h will highlight the word under the cursor in 5's highlight slot.\r\n  * Change buffer or open new window and highlights will remain the same\r\n  * \":Hc 2\"  will clear all the of slots 2's highlights.\r\n  * \":Hs\"     to changes the search pattern to all the current highlighted word\r\n  * \":Hc\"     will clear all highlights.\r\n  * \":Ha 1 \\<aa\" will add the regular expression \"\\<aa\" to highlight slot 1\r\n  * \":Hw highlights.so\" will save all the curent highlight settings\r\n\r\n==============================================================================\r\nSection 3: Detailed description of use:\r\n\r\n\r\nKEYBINDING\r\n\r\n<leader> default is \\\r\n\r\n[<number>] <Leader> h   -> to highlight the whole word under the cursor,\r\nhighlighted colour is determined by the preceding number, if no number\r\nis given 0 is used\r\n\r\nnumbers can be between 0 to 7 default is 0. More highlight numbers\/slots\r\ncan be added and there representative colour's changed at the start of\r\nthe script.\r\n\r\nIf the a word (or pattern) is added to a slot that already cointains it\r\nthe pattern will be removed.\r\n\r\n\r\nCHANGING \/ REMOVING SLOTS\r\n\r\nIf the word\/pattern you are trying to highlight already exits in a slot\r\nit will be removed from the previous slot. If the previous slot is the\r\nsame as the one new one (you are trying to add it to the same slot twice)\r\nit will simply remove the word\/pattern.\r\n\r\n\r\nCOMMANDS\r\n\r\n*Hc* *HighlightClear*\r\n\t:Hc [0 2 ...]\r\nClears the highlighted patterns in slot numbers listed or all if no\r\nnumber(s) are passed. If you just which to remove one word from the slot\r\nplease see changing \/ removing slots above\r\n\r\n*Hs* *HighlightSearch*\r\n\t:Hs [0 2 ...]\r\nChanges the search pattern to the highlighted slot numbers listed or\r\nall if no number(s) passed\r\n\r\n*Ha* *HighlightAddMultiple*\r\n\t:Ha <slot_number> <pattern> [additional patterns ...]\r\nAdds the pattern and any additional patterns (space separated) to the\r\nhighlight slot specified in <slot_number>. The patterns support regular\r\nexpressions. To include a space use \\ as escape character (eg \"\\ \")\r\n\r\n*Hw* *HighlightWrite*\r\n\t:Hw <file_location> [0 2 ...]\r\nCreate a vim source file at <file_location> containing the settings for\r\nthe slot number(s) passed (or all slots if no numbers are passed)\r\n \r\nTo load the file created from HighlightWrite simple source it using\r\n\t:source <file_location>\r\n\r\n\r\n==============================================================================\r\nSection 4: Wrap up\r\n\r\nISSUES:\r\n\r\nCurrently there are no known bugs.\r\n\r\n\r\nALTERNATIVES:\r\n<http:\/\/vim.wikia.com\/wiki\/Highlight_multiple_words> is a very good\r\nalternative to this script. This script is designed to be simple and\r\neasy to use\r\n\r\n<http:\/\/www.vim.org\/scripts\/script.php?script_id=2666 > is a much more\r\ncompressive and complex script then this one.\r\n \r\n```","4":"==============================================================================\r\nSection 1: Description                               *simple_highlighting*\r\n\r\nScript is designed to be easy and quick to use and satisfy the following\r\nfunctionality:\r\n1. Highlight multiple different words in multiple different highlight styles.\r\n2. Keep the highlights between buffers.\r\n3. Change search pattern to a highlighted style\r\n\r\n==============================================================================\r\nSection 2: Brief example of usage:\r\n  * Place your cursor on a word and use \"\\h\" to highlight it with default slot.\r\n  * Type \"\\h\" over another word to add it to the default slot\r\n  * Run \"\\h\" on a word already in the default highlight slot to remove it\r\n  * \":Hd 3\" will change the default slot to slot 3\r\n  * 5\\h will highlight the word under the cursor in 5's highlight slot.\r\n  * Change buffer or open new window and highlights will remain the same\r\n  * \":Hc 2\"  will clear all the of slots 2's highlights.\r\n  * \":Hs\"     to changes the search pattern to all the current highlighted word\r\n  * \":Hc\"     will clear all highlights.\r\n  * \":Ha 1 \\<aa\" will add the regular expression \"\\<aa\" to highlight slot 1\r\n  * \":Hw highlights.so\" will save all the curent highlight settings\r\n\r\n==============================================================================\r\nSection 3: Detailed description of use:\r\n\r\n\r\nKEYBINDING\r\n\r\n<leader> default is \\\r\n\r\n[<number>] <Leader> h   -> to highlight the whole word under the cursor,\r\nhighlighted colour is determined by the preceding number, if no number\r\nis given 0 is used\r\n\r\nnumbers can be between 0 to 7 default is 0. More highlight numbers\/slots\r\ncan be added and there representative colour's changed at the start of\r\nthe script.\r\n\r\nIf the a word (or pattern) is added to a slot that already cointains it\r\nthe pattern will be removed.\r\n\r\n\r\nCHANGING \/ REMOVING SLOTS\r\n\r\nIf the word\/pattern you are trying to highlight already exits in a slot\r\nit will be removed from the previous slot. If the previous slot is the\r\nsame as the one new one (you are trying to add it to the same slot twice)\r\nit will simply remove the word\/pattern.\r\n\r\n\r\nCOMMANDS\r\n\r\n*Hc* *HighlightClear*\r\n\t:Hc [0 2 ...]\r\nClears the highlighted patterns in slot numbers listed or all if no\r\nnumber(s) are passed. If you just which to remove one word from the slot\r\nplease see changing \/ removing slots above\r\n\r\n*Hs* *HighlightSearch*\r\n\t:Hs [0 2 ...]\r\nChanges the search pattern to the highlighted slot numbers listed or\r\nall if no number(s) passed\r\n\r\n*Ha* *HighlightAddMultiple*\r\n\t:Ha <slot_number> <pattern> [additional patterns ...]\r\nAdds the pattern and any additional patterns (space separated) to the\r\nhighlight slot specified in <slot_number>. The patterns support regular\r\nexpressions. To include a space use \\ as escape character (eg \"\\ \")\r\n\r\n*Hw* *HighlightWrite*\r\n\t:Hw <file_location> [0 2 ...]\r\nCreate a vim source file at <file_location> containing the settings for\r\nthe slot number(s) passed (or all slots if no numbers are passed)\r\n \r\nTo load the file created from HighlightWrite simple source it using\r\n\t:source <file_location>\r\n\r\n\r\n==============================================================================\r\nSection 4: Wrap up\r\n\r\nISSUES:\r\n\r\nCurrently there are no known bugs.\r\n\r\n\r\nALTERNATIVES:\r\n<http:\/\/vim.wikia.com\/wiki\/Highlight_multiple_words> is a very good\r\nalternative to this script. This script is designed to be simple and\r\neasy to use\r\n\r\n<http:\/\/www.vim.org\/scripts\/script.php?script_id=2666 > is a much more\r\ncompressive and complex script then this one.\r\n \r\n```","install_details":"The script just needs to be source at compile time. You can do that by coping it or sourcing it from your .vimrc file.\r\n\r\nOr you can use a package manager to install it from https:\/\/github.com\/pevhall\/simple_highlighting.\r\nminpac:\r\n   call minpac#add('pevhall\/simple_highlighting')  \r\nPlug:\r\n   Plug 'pevhall\/simple_highlighting'\r\n\r\n","5":"The script just needs to be source at compile time. You can do that by coping it or sourcing it from your .vimrc file.\r\n\r\nOr you can use a package manager to install it from https:\/\/github.com\/pevhall\/simple_highlighting.\r\nminpac:\r\n   call minpac#add('pevhall\/simple_highlighting')  \r\nPlug:\r\n   Plug 'pevhall\/simple_highlighting'\r\n\r\n","first_name":"Pev","6":"Pev","last_name":"Hall","7":"Hall","releases":[{"0":"4688","vim_version":"7.2","1":"7.2","script_version":"2.1","2":"2.1","version_comment":"Fixed issue #4:\r\n\r\nWhen highlighting on a visual selection the script does not current escape the magic characters.\r\n\r\nThis causes undesirable behavior. For instance it you tried to match \"...a\" with a visual selection match you are going to end up with everything that has three characters before an a highlighted.","3":"Fixed issue #4:\r\n\r\nWhen highlighting on a visual selection the script does not current escape the magic characters.\r\n\r\nThis causes undesirable behavior. For instance it you tried to match \"...a\" with a visual selection match you are going to end up with everything that has three characters before an a highlighted.","package":"simple_highlighting.vim","4":"simple_highlighting.vim","src_id":"27562","5":"27562","creation_date":"1617558316","6":"1617558316"},{"0":"4688","vim_version":"7.2","1":"7.2","script_version":"2.0","2":"2.0","version_comment":"New version number needed since the API has changed with slot 0 being removed.\r\n\r\nAdded conferable default slot. To do this I needed to remove slot 0. So now the slots start at 1 and 0 means the default slot. The default slot can be changed by using the \\\":Hd\\\" command \\\":Hd 2\\\" will change the default highlight slot to 2.\r\n\r\nFixed an issue with Hw where it was writing to many arguments for Ha due to vim error E740. It now breaks these long commands into multiple files if as needed.","3":"New version number needed since the API has changed with slot 0 being removed.\r\n\r\nAdded conferable default slot. To do this I needed to remove slot 0. So now the slots start at 1 and 0 means the default slot. The default slot can be changed by using the \\\":Hd\\\" command \\\":Hd 2\\\" will change the default highlight slot to 2.\r\n\r\nFixed an issue with Hw where it was writing to many arguments for Ha due to vim error E740. It now breaks these long commands into multiple files if as needed.","package":"simple_highlighting.vim","4":"simple_highlighting.vim","src_id":"27238","5":"27238","creation_date":"1595156273","6":"1595156273"},{"0":"4688","vim_version":"7.2","1":"7.2","script_version":"1.2.1","2":"1.2.1","version_comment":"* minor fix: stopped the cursor from moving a character when highlighting the word underneath it.\r\n* moved version into the file and out of the file name","3":"* minor fix: stopped the cursor from moving a character when highlighting the word underneath it.\r\n* moved version into the file and out of the file name","package":"simpleHighlighting.vimrc","4":"simpleHighlighting.vimrc","src_id":"23481","5":"23481","creation_date":"1437782670","6":"1437782670"},{"0":"4688","vim_version":"7.2","1":"7.2","script_version":"1.2.0","2":"1.2.0","version_comment":"Added Hw (Highlight Write) function use to create a vim source file for storing (and potential modifying) highlight settings","3":"Added Hw (Highlight Write) function use to create a vim source file for storing (and potential modifying) highlight settings","package":"simpleHighlightingV1.2.vimrc","4":"simpleHighlightingV1.2.vimrc","src_id":"22757","5":"22757","creation_date":"1420457542","6":"1420457542"},{"0":"4688","vim_version":"7.2","1":"7.2","script_version":"1.1.0","2":"1.1.0","version_comment":"Fixed issue when using commands with multiple numbers eg\r\n    :Hs 0 2\r\n\r\nTwo major improvements:\r\n   * If you highlight a word (or pattern) in a highlight slot where the word\/pattern already exists. It now removes the highlight (so you don't have to clear all the highlights in the slot). If it exits in a different slot it will remove it from the old slot before putting it in the new.\r\n\r\n   * Added new command \"Ha\" (Highlight add) so it is much easier to add highlights that use regular expressions. See description for more information","3":"Fixed issue when using commands with multiple numbers eg\r\n    :Hs 0 2\r\n\r\nTwo major improvements:\r\n   * If you highlight a word (or pattern) in a highlight slot where the word\/pattern already exists. It now removes the highlight (so you don't have to clear all the highlights in the slot). If it exits in a different slot it will remove it from the old slot before putting it in the new.\r\n\r\n   * Added new command \"Ha\" (Highlight add) so it is much easier to add highlights that use regular expressions. See description for more information","package":"simpleHighlightingV1.1.vimrc","4":"simpleHighlightingV1.1.vimrc","src_id":"22373","5":"22373","creation_date":"1409231275","6":"1409231275"},{"0":"4688","vim_version":"7.2","1":"7.2","script_version":"1.0.0","2":"1.0.0","version_comment":"Major fix: Removed conflicts when multiple windows are editing same buffer.","3":"Major fix: Removed conflicts when multiple windows are editing same buffer.","package":"simple_highlighting.vimrc","4":"simple_highlighting.vimrc","src_id":"21204","5":"21204","creation_date":"1387269093","6":"1387269093"},{"0":"4688","vim_version":"7.2","1":"7.2","script_version":"0.9.1","2":"0.9.1","version_comment":"Missed some dependent functions in previous commit.","3":"Missed some dependent functions in previous commit.","package":"simple_highlighting","4":"simple_highlighting","src_id":"20631","5":"20631","creation_date":"1376227001","6":"1376227001"}]},"4687":{"script_id":"4687","0":"4687","script_name":"move","1":"move","script_type":"utility","2":"utility","summary":"Move lines and selected text up and down","3":"Move lines and selected text up and down","description":"move is a Vim plugin that moves lines and selections in a visual manner using key maps in normal and visual mode.\r\n\r\nRead more about the plugin at \r\n\r\n   http:\/\/bloerg.net\/2013\/08\/10\/shift-lines-and-selections-faster-with-vim-move.html\r\n\r\nor watch a short demo screen cast for a first impression\r\n\r\n    http:\/\/i.imgur.com\/gIw2CCD.gif\r\n\r\nSource code and some more details are available at\r\n\r\n    https:\/\/github.com\/matze\/vim-move","4":"move is a Vim plugin that moves lines and selections in a visual manner using key maps in normal and visual mode.\r\n\r\nRead more about the plugin at \r\n\r\n   http:\/\/bloerg.net\/2013\/08\/10\/shift-lines-and-selections-faster-with-vim-move.html\r\n\r\nor watch a short demo screen cast for a first impression\r\n\r\n    http:\/\/i.imgur.com\/gIw2CCD.gif\r\n\r\nSource code and some more details are available at\r\n\r\n    https:\/\/github.com\/matze\/vim-move","install_details":"Use either Pathogen, Vundle or NeoBundle, e.g. add \r\n\r\n    Bundle 'matze\/vim-move'\r\n\r\nto your .vimrc or install manually using the standard Vim way. For more information have a look at\r\n\r\n    http:\/\/vimdoc.sourceforge.net\/htmldoc\/usr_05.html#add-plugin\r\n","5":"Use either Pathogen, Vundle or NeoBundle, e.g. add \r\n\r\n    Bundle 'matze\/vim-move'\r\n\r\nto your .vimrc or install manually using the standard Vim way. For more information have a look at\r\n\r\n    http:\/\/vimdoc.sourceforge.net\/htmldoc\/usr_05.html#add-plugin\r\n","first_name":"Matthias","6":"Matthias","last_name":"Vogelgesang","7":"Vogelgesang","releases":[{"0":"4687","vim_version":"7.0","1":"7.0","script_version":"1.4","2":"1.4","version_comment":"* New functionality for moving horizontally\r\n* Add g:move_past_end_of_line to control the move to the right.","3":"* New functionality for moving horizontally\r\n* Add g:move_past_end_of_line to control the move to the right.","package":"vim-move-1.4.tar.gz","4":"vim-move-1.4.tar.gz","src_id":"26186","5":"26186","creation_date":"1534721629","6":"1534721629"},{"0":"4687","vim_version":"7.0","1":"7.0","script_version":"1.3","2":"1.3","version_comment":"* Add g:move_auto_indent option to en-\/disable auto indentation\r\n* Do not modify readonly buffers\r\n* Silence :move commands to avoid first-time errors on read-only files.","3":"* Add g:move_auto_indent option to en-\/disable auto indentation\r\n* Do not modify readonly buffers\r\n* Silence :move commands to avoid first-time errors on read-only files.","package":"vim-move-1.3.tar.gz","4":"vim-move-1.3.tar.gz","src_id":"21632","5":"21632","creation_date":"1395139353","6":"1395139353"},{"0":"4687","vim_version":"7.0","1":"7.0","script_version":"1.2","2":"1.2","version_comment":"* Add key modifier for bindings (@vitalk)\r\n* Use <A-j> and <A-k> in normal and visual mode (@vitalk)\r\n* Add <Plug>Move{Block,Line}HalfPage{Up,Down} to move text in larger increments.","3":"* Add key modifier for bindings (@vitalk)\r\n* Use <A-j> and <A-k> in normal and visual mode (@vitalk)\r\n* Add <Plug>Move{Block,Line}HalfPage{Up,Down} to move text in larger increments.","package":"vim-move-1.2.tar.gz","4":"vim-move-1.2.tar.gz","src_id":"20642","5":"20642","creation_date":"1376461415","6":"1376461415"},{"0":"4687","vim_version":"7.0","1":"7.0","script_version":"1.1","2":"1.1","version_comment":"Minor bug fixes.","3":"Minor bug fixes.","package":"vim-move-1.1.tar.gz","4":"vim-move-1.1.tar.gz","src_id":"20625","5":"20625","creation_date":"1376164060","6":"1376164060"},{"0":"4687","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"vim-move-1.0.tar.gz","4":"vim-move-1.0.tar.gz","src_id":"20623","5":"20623","creation_date":"1376152594","6":"1376152594"}]},"4686":{"script_id":"4686","0":"4686","script_name":"Crunch","1":"Crunch","script_type":"utility","2":"utility","summary":"An easier way to perform calculations inside Vim","3":"An easier way to perform calculations inside Vim","description":"Crunch\r\n======\r\n\r\nAn easier way to perform calculations inside Vim\r\n\r\nGitHub\r\n------\r\nThe most up to date version of this plugin can be found here:\r\nhttps:\/\/github.com\/arecarn\/crunch\r\n\r\n\r\n\r\nOverview\r\n--------\r\n\r\nCrunch makes calculations in Vim more accessible and loosens Vim's math syntax. Most of Crunch's looser syntax is accomplished by extensive search and replace. Crunch also forces floating point to be used.\r\n\r\nRequirements: Vim compiled with +float feature.\r\n\r\nCrunch allows you to just type in mathematical expressions without having to worry about the syntax as much.\r\n\r\nUsage\r\n-----\r\n\r\n:Crunch <args>\r\n\r\nWhere is some mathematical expression to be evaluated. The result is then available to be pasted from the default register.\r\n\r\n:Crunch\r\n\r\nCrunch then gives you the following prompt in the command line: Calc >> for you to enter you mathematical expression. The result is then available to be pasted from the default register.\r\n\r\n:CrunchLine, :'<'>CrunchLine, or <leader>cl\r\n\r\nCrunch Uses the current line or the visually selected lines as the expression(s) and adds the result to the end of the line(s). When the expression(s) changes using :CrunchLine again will reevaluate the line(s)\r\n\r\n:CrunchBlock, or <leader>cb\r\n\r\nCrunch Uses the current paragraph (block of text starting and ending with an empty line) as the expressions and adds the result to the end of the lines. When a expressions in a paragraph changes using :CrunchBlock again will reevaluate them\r\n\r\nDemos\r\n-----\r\n\r\nSee the Github page for Animated Gif Demos\r\nhttps:\/\/github.com\/arecarn\/crunch\r\n\r\nMake Crunch Better\r\n\r\nI'm pretty new to Vim Script so any tips are appreciated. Think you can make Crunch better? Fork it on GitHub and send a pull request. If you find bugs, want new functionality contact me by making an issue on GitHub and I'll see what I can do.\r\n\r\nCredits\r\n-------\r\n\r\nSources inspiration and credits for this plugin\r\n\r\nhttp:\/\/patorjk.com\/ ASCII font courtesy of Patrick Gillespie\r\n\r\nhttps:\/\/github.com\/gregsexton\/VimCalc Greg Sexton Wrote Vimcalc\r\n\r\nhttp:\/\/vimrc-dissection.blogspot.com\/2011\/01\/vim-inline-calculator-revisited.html Ihar Filipau wrote most of the tagging code as well as VIM incline calculator\r\n\r\nhttps:\/\/github.com\/hrsh7th\/vim-neco-calc hrsh7th wrote Neco-calc, and inspired the int to float conversion method\r\n","4":"Crunch\r\n======\r\n\r\nAn easier way to perform calculations inside Vim\r\n\r\nGitHub\r\n------\r\nThe most up to date version of this plugin can be found here:\r\nhttps:\/\/github.com\/arecarn\/crunch\r\n\r\n\r\n\r\nOverview\r\n--------\r\n\r\nCrunch makes calculations in Vim more accessible and loosens Vim's math syntax. Most of Crunch's looser syntax is accomplished by extensive search and replace. Crunch also forces floating point to be used.\r\n\r\nRequirements: Vim compiled with +float feature.\r\n\r\nCrunch allows you to just type in mathematical expressions without having to worry about the syntax as much.\r\n\r\nUsage\r\n-----\r\n\r\n:Crunch <args>\r\n\r\nWhere is some mathematical expression to be evaluated. The result is then available to be pasted from the default register.\r\n\r\n:Crunch\r\n\r\nCrunch then gives you the following prompt in the command line: Calc >> for you to enter you mathematical expression. The result is then available to be pasted from the default register.\r\n\r\n:CrunchLine, :'<'>CrunchLine, or <leader>cl\r\n\r\nCrunch Uses the current line or the visually selected lines as the expression(s) and adds the result to the end of the line(s). When the expression(s) changes using :CrunchLine again will reevaluate the line(s)\r\n\r\n:CrunchBlock, or <leader>cb\r\n\r\nCrunch Uses the current paragraph (block of text starting and ending with an empty line) as the expressions and adds the result to the end of the lines. When a expressions in a paragraph changes using :CrunchBlock again will reevaluate them\r\n\r\nDemos\r\n-----\r\n\r\nSee the Github page for Animated Gif Demos\r\nhttps:\/\/github.com\/arecarn\/crunch\r\n\r\nMake Crunch Better\r\n\r\nI'm pretty new to Vim Script so any tips are appreciated. Think you can make Crunch better? Fork it on GitHub and send a pull request. If you find bugs, want new functionality contact me by making an issue on GitHub and I'll see what I can do.\r\n\r\nCredits\r\n-------\r\n\r\nSources inspiration and credits for this plugin\r\n\r\nhttp:\/\/patorjk.com\/ ASCII font courtesy of Patrick Gillespie\r\n\r\nhttps:\/\/github.com\/gregsexton\/VimCalc Greg Sexton Wrote Vimcalc\r\n\r\nhttp:\/\/vimrc-dissection.blogspot.com\/2011\/01\/vim-inline-calculator-revisited.html Ihar Filipau wrote most of the tagging code as well as VIM incline calculator\r\n\r\nhttps:\/\/github.com\/hrsh7th\/vim-neco-calc hrsh7th wrote Neco-calc, and inspired the int to float conversion method\r\n","install_details":"If you don't have an preferred method, I recommend one of the following plugin managers.\r\n\r\nNeobundle\r\nVundle\r\npathogen\r\nVAM\r\n","5":"If you don't have an preferred method, I recommend one of the following plugin managers.\r\n\r\nNeobundle\r\nVundle\r\npathogen\r\nVAM\r\n","first_name":"Ryan","6":"Ryan","last_name":"Carney","7":"Carney","releases":[{"0":"4686","vim_version":"7.3","1":"7.3","script_version":"2.0","2":"2.0","version_comment":"- The # has been removed from variable declaration\/usage \r\n- evaluate math enclosed in comments.\r\n- :CrunchBlock command evaluates blocks at a time\r\n- various other large and small fixes","3":"- The # has been removed from variable declaration\/usage \r\n- evaluate math enclosed in comments.\r\n- :CrunchBlock command evaluates blocks at a time\r\n- various other large and small fixes","package":"crunch.zip","4":"crunch.zip","src_id":"21047","5":"21047","creation_date":"1384557845","6":"1384557845"},{"0":"4686","vim_version":"7.3","1":"7.3","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"crunch.zip","4":"crunch.zip","src_id":"20614","5":"20614","creation_date":"1375978808","6":"1375978808"}]},"4685":{"script_id":"4685","0":"4685","script_name":"logpad-plus-duration","1":"logpad-plus-duration","script_type":"utility","2":"utility","summary":"Emulate Windows Notepad logging feature, and log duration of each entry","3":"Emulate Windows Notepad logging feature, and log duration of each entry","description":"Credits\r\n----------\r\n\r\nThis plugin is a fork of logpad plugin by Sven Knurr <der_tuxman@arcor.de> available at: http:\/\/vim.sourceforge.net\/scripts\/script.php?script_id=2775\r\n\r\nBackground\r\n----------------\r\n\r\nIt is suggested to keep a daily log to stay focused on productivity. Life Hacker did [an article](http:\/\/lifehacker.com\/5582372\/use-a-daily-log-to-keep-yourself-focused-on-productivity) on it. I looked for plugin to have similar feature in Vim and that landed me on Logpad plugin. \r\n\r\nWouldn't it be nice if besides logging, we can also see how much time was spent on the latest activity? This is exactly what this plugin attempts to do. If you enable it, it will calculate the time elapsed and insert it in the file.\r\n\r\nWith this plugin you get all the features of Logpad plugin plus log duration feature.\r\n\r\nHow to use it\r\n------------------\r\n\r\nCreate a new file, write .LOG as the first line and save it. Every time you reopen the file, a new line with the current timestamp is added, so you can easily maintain a chronologic log of your tasks.\r\n\r\nOptions\r\n-----------\r\n\r\nBy default, this plugin works the same way as the original Notepad. You can modify certain aspects of it by setting the following variables:\r\n\r\nlet LogpadEnabled = 1\r\n\r\n    enables\/disables logpad\r\n    available values : [0, 1]\r\n    default value: 1\r\n\r\nlet LogpadInsert = 0\r\n\r\n    automatically enables insert mode when a new log entry is created\r\n    available values : [0, 1]\r\n    default value: 0\r\n\r\nlet LogpadLineBreak = 0\r\n\r\n    adds an empty line before a new log entry\r\n    available values : [0, 1]\r\n    default value: 0 (Windows Notepad behavior)\r\n\r\nlet LogpadIgnoreNotes = 0\r\n\r\n    allows adding notes before the first log entry\r\n    available values : [0, 1]\r\n    default value: 0\r\n\r\nlet LogpadIgnoreReadOnly = 0\r\n\r\n    allows logpad to ignore a file's read-only flag\r\n    available values : [0, 1]\r\n    default value: 0\r\n\r\nlet LogpadLogDuration = 1\r\n\r\n    adds the time elapsed since last timestamp under the new timestamp\r\n    available values : [0 ,1]\r\n    default value: 0\r\n\r\nExample (without LogpadLogDuration)\r\n----------------------------------------------------\r\n\r\n.LOG\r\nSun Jul 14 17:38:44 2013\r\nFirst entry of the day\r\nSun Jul 14 17:46:11 2013\r\nReplied to customer emails.\r\nSun Jul 14 18:41:43 2013\r\nSkype session with remote team.\r\n\r\nExample (with LogpadLogDuration)\r\n------------------------------------------------\r\n\r\nIf LogpadLogDuration is set then time elapsed since last event will also be added.\r\n\r\n.LOG\r\nSun Jul 14 17:38:44 2013\r\nFirst entry of the day\r\nSun Jul 14 17:46:11 2013\r\nTime elapsed: 7 min 27 sec\r\nReplied to customer emails.\r\nSun Jul 14 18:41:43 2013\r\nTime elapsed: 55 min 32 sec \r\nSkype session with remote team.\r\n\r\nNow you can see that your Skype session took 55 min. Your replied to emails within 7 min. Without this feature, you will have to do mental maths to calculate the time it took you to do a work.\r\n\r\nSource Code\r\n------------------\r\n\r\nhttps:\/\/github.com\/talha131\/logpad-plus-duration\r\n\r\nBug Reports\/Feature Requests\r\n------------------------------------------\r\n\r\nhttps:\/\/github.com\/talha131\/logpad-plus-duration\/issues","4":"Credits\r\n----------\r\n\r\nThis plugin is a fork of logpad plugin by Sven Knurr <der_tuxman@arcor.de> available at: http:\/\/vim.sourceforge.net\/scripts\/script.php?script_id=2775\r\n\r\nBackground\r\n----------------\r\n\r\nIt is suggested to keep a daily log to stay focused on productivity. Life Hacker did [an article](http:\/\/lifehacker.com\/5582372\/use-a-daily-log-to-keep-yourself-focused-on-productivity) on it. I looked for plugin to have similar feature in Vim and that landed me on Logpad plugin. \r\n\r\nWouldn't it be nice if besides logging, we can also see how much time was spent on the latest activity? This is exactly what this plugin attempts to do. If you enable it, it will calculate the time elapsed and insert it in the file.\r\n\r\nWith this plugin you get all the features of Logpad plugin plus log duration feature.\r\n\r\nHow to use it\r\n------------------\r\n\r\nCreate a new file, write .LOG as the first line and save it. Every time you reopen the file, a new line with the current timestamp is added, so you can easily maintain a chronologic log of your tasks.\r\n\r\nOptions\r\n-----------\r\n\r\nBy default, this plugin works the same way as the original Notepad. You can modify certain aspects of it by setting the following variables:\r\n\r\nlet LogpadEnabled = 1\r\n\r\n    enables\/disables logpad\r\n    available values : [0, 1]\r\n    default value: 1\r\n\r\nlet LogpadInsert = 0\r\n\r\n    automatically enables insert mode when a new log entry is created\r\n    available values : [0, 1]\r\n    default value: 0\r\n\r\nlet LogpadLineBreak = 0\r\n\r\n    adds an empty line before a new log entry\r\n    available values : [0, 1]\r\n    default value: 0 (Windows Notepad behavior)\r\n\r\nlet LogpadIgnoreNotes = 0\r\n\r\n    allows adding notes before the first log entry\r\n    available values : [0, 1]\r\n    default value: 0\r\n\r\nlet LogpadIgnoreReadOnly = 0\r\n\r\n    allows logpad to ignore a file's read-only flag\r\n    available values : [0, 1]\r\n    default value: 0\r\n\r\nlet LogpadLogDuration = 1\r\n\r\n    adds the time elapsed since last timestamp under the new timestamp\r\n    available values : [0 ,1]\r\n    default value: 0\r\n\r\nExample (without LogpadLogDuration)\r\n----------------------------------------------------\r\n\r\n.LOG\r\nSun Jul 14 17:38:44 2013\r\nFirst entry of the day\r\nSun Jul 14 17:46:11 2013\r\nReplied to customer emails.\r\nSun Jul 14 18:41:43 2013\r\nSkype session with remote team.\r\n\r\nExample (with LogpadLogDuration)\r\n------------------------------------------------\r\n\r\nIf LogpadLogDuration is set then time elapsed since last event will also be added.\r\n\r\n.LOG\r\nSun Jul 14 17:38:44 2013\r\nFirst entry of the day\r\nSun Jul 14 17:46:11 2013\r\nTime elapsed: 7 min 27 sec\r\nReplied to customer emails.\r\nSun Jul 14 18:41:43 2013\r\nTime elapsed: 55 min 32 sec \r\nSkype session with remote team.\r\n\r\nNow you can see that your Skype session took 55 min. Your replied to emails within 7 min. Without this feature, you will have to do mental maths to calculate the time it took you to do a work.\r\n\r\nSource Code\r\n------------------\r\n\r\nhttps:\/\/github.com\/talha131\/logpad-plus-duration\r\n\r\nBug Reports\/Feature Requests\r\n------------------------------------------\r\n\r\nhttps:\/\/github.com\/talha131\/logpad-plus-duration\/issues","install_details":"Download the logpad.vim file. Put it into your plugins directory.","5":"Download the logpad.vim file. Put it into your plugins directory.","first_name":"Talha","6":"Talha","last_name":"Mansoor","7":"Mansoor","releases":[{"0":"4685","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"logpad.vim","4":"logpad.vim","src_id":"20613","5":"20613","creation_date":"1375954799","6":"1375954799"}]},"4684":{"script_id":"4684","0":"4684","script_name":"EasyClip","1":"EasyClip","script_type":"utility","2":"utility","summary":"Simplified clipboard functionality for Vim","3":"Simplified clipboard functionality for Vim","description":"EasyClip is a collection of clipboard related functionality with the goal of making using vim simpler without losing any of its power.  Major changes include: \r\n\r\n    - Remapping all delete operations to the black hole register and introducing a new operator (cut) to be used instead\r\n    - Adding a substitute operator\r\n    - Improvements to paste\r\n    - Improvements to yank, including support for navigating history\r\n    - Ability to share clipboard between different concurrent vim instances\r\n    - Persistent saving of yank history to file\r\n\r\nFor more information please visit the github page at: https:\/\/github.com\/svermeulen\/vim-easyclip","4":"EasyClip is a collection of clipboard related functionality with the goal of making using vim simpler without losing any of its power.  Major changes include: \r\n\r\n    - Remapping all delete operations to the black hole register and introducing a new operator (cut) to be used instead\r\n    - Adding a substitute operator\r\n    - Improvements to paste\r\n    - Improvements to yank, including support for navigating history\r\n    - Ability to share clipboard between different concurrent vim instances\r\n    - Persistent saving of yank history to file\r\n\r\nFor more information please visit the github page at: https:\/\/github.com\/svermeulen\/vim-easyclip","install_details":"I recommend loading your plugins with neobundle or vundle or pathogen.\r\n\r\nThis plugin also requires that you have Tim Pope\\\\\\'s repeat.vim plugin installed.","5":"I recommend loading your plugins with neobundle or vundle or pathogen.\r\n\r\nThis plugin also requires that you have Tim Pope\\\\\\'s repeat.vim plugin installed.","first_name":"Steve","6":"Steve","last_name":"Vermeulen","7":"Vermeulen","releases":[{"0":"4684","vim_version":"7.0","1":"7.0","script_version":"2.4","2":"2.4","version_comment":"Added interactive paste by executing command :PasteI\r\nAdded :Paste and :PasteBefore commands, and also the corresponding methods EasyClip#PasteIndex and EasyClip#PasteIndexBefore\r\nBug fixes to visual mode paste\r\nAdded plug mapping to toggle paste between format\/unformatted","3":"Added interactive paste by executing command :PasteI\r\nAdded :Paste and :PasteBefore commands, and also the corresponding methods EasyClip#PasteIndex and EasyClip#PasteIndexBefore\r\nBug fixes to visual mode paste\r\nAdded plug mapping to toggle paste between format\/unformatted","package":"vim-easyclip-2.4.zip","4":"vim-easyclip-2.4.zip","src_id":"26317","5":"26317","creation_date":"1546663398","6":"1546663398"},{"0":"4684","vim_version":"7.0","1":"7.0","script_version":"2.2","2":"2.2","version_comment":"    Bug fixes\r\n    Removed the 'system sync' option since using unnamed register is sufficient for this\r\n    Added support for persistent\/shared yanks","3":"    Bug fixes\r\n    Removed the 'system sync' option since using unnamed register is sufficient for this\r\n    Added support for persistent\/shared yanks","package":"vim-easyclip-2.2.zip","4":"vim-easyclip-2.2.zip","src_id":"22844","5":"22844","creation_date":"1422388488","6":"1422388488"},{"0":"4684","vim_version":"7.0","1":"7.0","script_version":"2.1","2":"2.1","version_comment":"Many fixes, added yankring-style swap, better defaults.","3":"Many fixes, added yankring-style swap, better defaults.","package":"vim-easy-clip-2.1.zip","4":"vim-easy-clip-2.1.zip","src_id":"21189","5":"21189","creation_date":"1386914022","6":"1386914022"},{"0":"4684","vim_version":"7.0","1":"7.0","script_version":"1.2","2":"1.2","version_comment":"Bug fixes \/ tweaks","3":"Bug fixes \/ tweaks","package":"vim-easyclip.zip","4":"vim-easyclip.zip","src_id":"20825","5":"20825","creation_date":"1379858695","6":"1379858695"},{"0":"4684","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"vim-easyclip-master.zip","4":"vim-easyclip-master.zip","src_id":"20611","5":"20611","creation_date":"1375914398","6":"1375914398"}]},"4683":{"script_id":"4683","0":"4683","script_name":"playroom","1":"playroom","script_type":"color scheme","2":"color scheme","summary":"A light colorscheme based on the FlatUI palette","3":"A light colorscheme based on the FlatUI palette","description":"A light colorscheme based on the FlatUI palette (http:\/\/flatuicolors.com\/)\r\n\r\nWhite BG, low contrast normal text, brightly colored accents.","4":"A light colorscheme based on the FlatUI palette (http:\/\/flatuicolors.com\/)\r\n\r\nWhite BG, low contrast normal text, brightly colored accents.","install_details":"Put playroom.vim in [vimfolder]\/colors","5":"Put playroom.vim in [vimfolder]\/colors","first_name":"Tommy","6":"Tommy","last_name":"Heffernan","7":"Heffernan","releases":[{"0":"4683","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"playroom.vim","4":"playroom.vim","src_id":"20609","5":"20609","creation_date":"1375808908","6":"1375808908"}]},"4682":{"script_id":"4682","0":"4682","script_name":"jshint2.vim","1":"jshint2.vim","script_type":"utility","2":"utility","summary":"Lightweight, customizable and functional Vim plugin for JSHint integration.","3":"Lightweight, customizable and functional Vim plugin for JSHint integration.","description":"See https:\/\/github.com\/Shutnik\/jshint2.vim\r\n\r\nFeatures:\r\n* Linting whole file or selected lines without saving to disk.\r\n* Using project-specific (locally installed) version of JSHint and JSHint configuration files if available.\r\n* Setting lint flags from command line with autocompletion.\r\n* Optionally opening list of linting errors with useful shortcuts.\r\n* Optionally validating files after reading or saving.\r\n* Working on Linux, Windows (with JSHint 2.1.5 and newer) and OS X.","4":"See https:\/\/github.com\/Shutnik\/jshint2.vim\r\n\r\nFeatures:\r\n* Linting whole file or selected lines without saving to disk.\r\n* Using project-specific (locally installed) version of JSHint and JSHint configuration files if available.\r\n* Setting lint flags from command line with autocompletion.\r\n* Optionally opening list of linting errors with useful shortcuts.\r\n* Optionally validating files after reading or saving.\r\n* Working on Linux, Windows (with JSHint 2.1.5 and newer) and OS X.","install_details":"See https:\/\/github.com\/Shutnik\/jshint2.vim#installation","5":"See https:\/\/github.com\/Shutnik\/jshint2.vim#installation","first_name":"Nikolay","6":"Nikolay","last_name":"Frantsev","7":"Frantsev","releases":[{"0":"4682","vim_version":"7.0","1":"7.0","script_version":"0.5","2":"0.5","version_comment":"New upstream release","3":"New upstream release","package":"jshint2.vim-0.5.zip","4":"jshint2.vim-0.5.zip","src_id":"22177","5":"22177","creation_date":"1404937783","6":"1404937783"}]},"4681":{"script_id":"4681","0":"4681","script_name":"Pretty Args","1":"Pretty Args","script_type":"utility","2":"utility","summary":"Pretty print for :args command","3":"Pretty print for :args command","description":"This plugin provides an :Arg command which can nicely print the output of :args.  Read more in the included doc file.\r\n\r\nThe main reason for this plugin is to remove a common directory when you work on a project which files are deep under some common project directory and you use autodir vim option.  In this case :args command shows very long filenames and the arg list becomes to readable.  You can use:\r\nArgs :p:s?^\/path\/to\/project\/directory\/??\r\nor even\r\nArgs :p:s?^\/path\/to\/project\/directory\/??:S\r\nto shorten the path.  If you work on a Django project and you use args and friends this command will be very useful.\r\n\r\nIf you rate this plugin, especially down rate and you have a reason for that, please send me an email mszamot [AT] gmail [DOT] com . Otherwise, why to rate at all ...?\r\n\r\nYou can also get the plugin from https:\/\/github.com\/coot\/vim_args","4":"This plugin provides an :Arg command which can nicely print the output of :args.  Read more in the included doc file.\r\n\r\nThe main reason for this plugin is to remove a common directory when you work on a project which files are deep under some common project directory and you use autodir vim option.  In this case :args command shows very long filenames and the arg list becomes to readable.  You can use:\r\nArgs :p:s?^\/path\/to\/project\/directory\/??\r\nor even\r\nArgs :p:s?^\/path\/to\/project\/directory\/??:S\r\nto shorten the path.  If you work on a Django project and you use args and friends this command will be very useful.\r\n\r\nIf you rate this plugin, especially down rate and you have a reason for that, please send me an email mszamot [AT] gmail [DOT] com . Otherwise, why to rate at all ...?\r\n\r\nYou can also get the plugin from https:\/\/github.com\/coot\/vim_args","install_details":"Unzip the file ant put the files inside your ~\/.vim directory.","5":"Unzip the file ant put the files inside your ~\/.vim directory.","first_name":"Marcin","6":"Marcin","last_name":"Szamotulski","7":"Szamotulski","releases":[{"0":"4681","vim_version":"7.3","1":"7.3","script_version":"3","2":"3","version_comment":"New updated version. Vim patch included.","3":"New updated version. Vim patch included.","package":"pretty_args.zip","4":"pretty_args.zip","src_id":"21368","5":"21368","creation_date":"1390611304","6":"1390611304"},{"0":"4681","vim_version":"7.0","1":"7.0","script_version":"2","2":"2","version_comment":"Documentation updated with a nice example.","3":"Documentation updated with a nice example.","package":"pretty_args.zip","4":"pretty_args.zip","src_id":"20633","5":"20633","creation_date":"1376297699","6":"1376297699"},{"0":"4681","vim_version":"7.3","1":"7.3","script_version":"1","2":"1","version_comment":"Initial upload","3":"Initial upload","package":"pretty_args.zip","4":"pretty_args.zip","src_id":"20599","5":"20599","creation_date":"1375639357","6":"1375639357"}]},"4680":{"script_id":"4680","0":"4680","script_name":"Visual Studio","1":"Visual Studio","script_type":"color scheme","2":"color scheme","summary":"A color scheme that tries to imitate Visual Studio 2010.","3":"A color scheme that tries to imitate Visual Studio 2010.","description":"This color scheme was derived from vimscript #3328\r\nIt tries to be closer to the look of Visual Studios syntax highlighting and font.\r\nYou should use it in the GUI version of vim (gvim).\r\n\r\nThe archive includes the font Consolas from http:\/\/github.com\/eugeneching\/consolas-powerline-vim\r\n\r\nScreenshot:\r\n\r\nhttp:\/\/img545.imageshack.us\/img545\/5940\/v7o4.png\r\n","4":"This color scheme was derived from vimscript #3328\r\nIt tries to be closer to the look of Visual Studios syntax highlighting and font.\r\nYou should use it in the GUI version of vim (gvim).\r\n\r\nThe archive includes the font Consolas from http:\/\/github.com\/eugeneching\/consolas-powerline-vim\r\n\r\nScreenshot:\r\n\r\nhttp:\/\/img545.imageshack.us\/img545\/5940\/v7o4.png\r\n","install_details":"Instructions for Unix-like OSes:\r\n\r\nExtract archive:\r\n\r\n        tar -xf visualstudio.tar.gz\r\n\r\nCopy fonts:\r\n\r\n        cp visualstudio\/fonts\/*.ttf ~\/.fonts\/\r\n\r\nCopy color scheme:\r\n\r\n        cp visualstudio\/visualstudio.vim ~\/.vim\/colors\/\r\n\r\nActivate in gvim with:\r\n\r\n        :colorscheme visualstudio\r\n","5":"Instructions for Unix-like OSes:\r\n\r\nExtract archive:\r\n\r\n        tar -xf visualstudio.tar.gz\r\n\r\nCopy fonts:\r\n\r\n        cp visualstudio\/fonts\/*.ttf ~\/.fonts\/\r\n\r\nCopy color scheme:\r\n\r\n        cp visualstudio\/visualstudio.vim ~\/.vim\/colors\/\r\n\r\nActivate in gvim with:\r\n\r\n        :colorscheme visualstudio\r\n","first_name":"Kali","6":"Kali","last_name":"Kali","7":"Kali","releases":[{"0":"4680","vim_version":"7.0","1":"7.0","script_version":"1.1","2":"1.1","version_comment":"Changed visualstudio.vim to display the right name of this color scheme. Version 1.0 showed up as \"blueshift\".","3":"Changed visualstudio.vim to display the right name of this color scheme. Version 1.0 showed up as \"blueshift\".","package":"visualstudio.tar.gz","4":"visualstudio.tar.gz","src_id":"20598","5":"20598","creation_date":"1375605233","6":"1375605233"},{"0":"4680","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"visualstudio.tar.gz","4":"visualstudio.tar.gz","src_id":"20593","5":"20593","creation_date":"1375455563","6":"1375455563"}]},"4679":{"script_id":"4679","0":"4679","script_name":"Vim-Ultimate-Colorscheme-Utility","1":"Vim-Ultimate-Colorscheme-Utility","script_type":"utility","2":"utility","summary":"Utility for managing multiple favorite colorschemes and fonts.","3":"Utility for managing multiple favorite colorschemes and fonts.","description":"Use the http:\/\/github.com\/biskark\/vim-ultimate-colorscheme-utility page for more current releases.\r\nIf you have and questions, comments, or new feature ideas, you can contact me at biskark@gmail.com\r\n\r\nNew Features\r\n===========\r\nMenu Integration\r\n\r\nUltimate Colorscheme Utility is now working on better integration into GVim. There is now a 'Favorites' menu that enables all the functionality of the plugin at the push of a button.\r\nExcluded Filetypes\r\n\r\nNow you can specify which filetypes Ultimate Colorscheme Utility can ignore for even more customizability.\r\n\r\nFeatures\r\n========\r\nUltimate Colorscheme Utility offers several features for customizing your colorscheme preferences.\r\n- Allows for easy browsing of all installed colorschemes,\r\n  see the awesome archive at https:\/\/github.com\/flazz\/vim-colorschemes for a ton of colorschemes.\r\n- Allows saving favorite colorschemes for all vim, or for specific filetypes.\r\n- Enables automatic switching of colorschemes when switching fietype buffers so that a favorite scheme is always on.\r\n- NEW: Allows for the saving of favorite fonts when using GVim.\r\n\r\nQuick Usage\r\n===========\r\nNote: This is not a complete list and all mappings are customizable, view the helptags for more information.\r\n\r\n<leader><leader>a    \" Adds the current colorscheme to favorites\r\n<leader><leader>A    \" Removes the current colorscheme from favorites\r\n<leader><leader>f     \" Goes to next colorscheme in favorites\r\n<leader><leader>F    \" Goes to previous colorscheme in favorites\r\n<leader><leader>g    \" Goes to next colorscheme in global favorites\r\n<leader><leader>G    \" Goes to previous colorscheme in global favorites\r\n<leader><leader>n    \" Goes to next colorscheme in all colors\r\n<leader><leader>N    \" Goes to previous colorscheme in all colors\r\n\r\n<leader><leader>t     \" Adds the current font to favorites\r\n<leader><leader>T    \" Removes the current font from favorites\r\n<leader><leader>e    \" Goes to the next font in filetype specific favorites\r\n<leader><leader>E    \" Goes to the previous font in filetype specific favorites\r\n<leader><leader>r     \" Goes to the next font in global favorites\r\n<leader><leader>R   \" Goes to the previous font in global favorites\r\n\r\n<leader><leader>q    \" Views all favorites","4":"Use the http:\/\/github.com\/biskark\/vim-ultimate-colorscheme-utility page for more current releases.\r\nIf you have and questions, comments, or new feature ideas, you can contact me at biskark@gmail.com\r\n\r\nNew Features\r\n===========\r\nMenu Integration\r\n\r\nUltimate Colorscheme Utility is now working on better integration into GVim. There is now a 'Favorites' menu that enables all the functionality of the plugin at the push of a button.\r\nExcluded Filetypes\r\n\r\nNow you can specify which filetypes Ultimate Colorscheme Utility can ignore for even more customizability.\r\n\r\nFeatures\r\n========\r\nUltimate Colorscheme Utility offers several features for customizing your colorscheme preferences.\r\n- Allows for easy browsing of all installed colorschemes,\r\n  see the awesome archive at https:\/\/github.com\/flazz\/vim-colorschemes for a ton of colorschemes.\r\n- Allows saving favorite colorschemes for all vim, or for specific filetypes.\r\n- Enables automatic switching of colorschemes when switching fietype buffers so that a favorite scheme is always on.\r\n- NEW: Allows for the saving of favorite fonts when using GVim.\r\n\r\nQuick Usage\r\n===========\r\nNote: This is not a complete list and all mappings are customizable, view the helptags for more information.\r\n\r\n<leader><leader>a    \" Adds the current colorscheme to favorites\r\n<leader><leader>A    \" Removes the current colorscheme from favorites\r\n<leader><leader>f     \" Goes to next colorscheme in favorites\r\n<leader><leader>F    \" Goes to previous colorscheme in favorites\r\n<leader><leader>g    \" Goes to next colorscheme in global favorites\r\n<leader><leader>G    \" Goes to previous colorscheme in global favorites\r\n<leader><leader>n    \" Goes to next colorscheme in all colors\r\n<leader><leader>N    \" Goes to previous colorscheme in all colors\r\n\r\n<leader><leader>t     \" Adds the current font to favorites\r\n<leader><leader>T    \" Removes the current font from favorites\r\n<leader><leader>e    \" Goes to the next font in filetype specific favorites\r\n<leader><leader>E    \" Goes to the previous font in filetype specific favorites\r\n<leader><leader>r     \" Goes to the next font in global favorites\r\n<leader><leader>R   \" Goes to the previous font in global favorites\r\n\r\n<leader><leader>q    \" Views all favorites","install_details":"Installation\r\n========\r\n\r\n### via Pathogen, the preferred method\r\n\r\ncd ~\/.vim\/bundle\r\ngit clone https:\/\/github.com\/biskark\/vim-ultimate-colorscheme-utility.git\r\nIn vim type ':pathogen#helptags' # Adds documentation\r\n\r\n### via archive, the bad method\r\n1. download archive\r\n2. unzip archive\r\n3. copy all files into $HOME\/.vim for mac or linux, or $HOME\/vimfiles for windows\r\n4. In vim, type ':helptags $HOME\/.vim\/doc' or ':helptags $HOME\/vimfiles\/doc'\r\n\r\n### via Vundle, the unknown method\r\n1. I don't use Vundle, but I assume it's similar to Pathogen","5":"Installation\r\n========\r\n\r\n### via Pathogen, the preferred method\r\n\r\ncd ~\/.vim\/bundle\r\ngit clone https:\/\/github.com\/biskark\/vim-ultimate-colorscheme-utility.git\r\nIn vim type ':pathogen#helptags' # Adds documentation\r\n\r\n### via archive, the bad method\r\n1. download archive\r\n2. unzip archive\r\n3. copy all files into $HOME\/.vim for mac or linux, or $HOME\/vimfiles for windows\r\n4. In vim, type ':helptags $HOME\/.vim\/doc' or ':helptags $HOME\/vimfiles\/doc'\r\n\r\n### via Vundle, the unknown method\r\n1. I don't use Vundle, but I assume it's similar to Pathogen","first_name":"Kevin","6":"Kevin","last_name":"Biskar","7":"Biskar","releases":[{"0":"4679","vim_version":"7.0","1":"7.0","script_version":"0.2.2","2":"0.2.2","version_comment":"New GVim Menu Integration and customizable list of excluded filetypes.","3":"New GVim Menu Integration and customizable list of excluded filetypes.","package":"vim-ultimate-colorscheme-utility-v0.2.2.tar","4":"vim-ultimate-colorscheme-utility-v0.2.2.tar","src_id":"20757","5":"20757","creation_date":"1378434111","6":"1378434111"},{"0":"4679","vim_version":"7.0","1":"7.0","script_version":"0.2.0a","2":"0.2.0a","version_comment":"Minor Bugfixes","3":"Minor Bugfixes","package":"vim-ultimate-colorscheme-utility-v0.2.0a.tar","4":"vim-ultimate-colorscheme-utility-v0.2.0a.tar","src_id":"20749","5":"20749","creation_date":"1378285046","6":"1378285046"},{"0":"4679","vim_version":"7.0","1":"7.0","script_version":"0.2.0","2":"0.2.0","version_comment":"New Feature!\r\n\r\nNow allows for the saving of favorite fonts.\r\nNote this only works when using GVim.","3":"New Feature!\r\n\r\nNow allows for the saving of favorite fonts.\r\nNote this only works when using GVim.","package":"vim-ultimate-colorscheme-utility-v0.2.0.tar","4":"vim-ultimate-colorscheme-utility-v0.2.0.tar","src_id":"20748","5":"20748","creation_date":"1378248607","6":"1378248607"},{"0":"4679","vim_version":"7.0","1":"7.0","script_version":"0.1.3","2":"0.1.3","version_comment":"Fixed an issue where changing colorschemes did not always display the new name when g:ulti_color_verbose was set to 1.","3":"Fixed an issue where changing colorschemes did not always display the new name when g:ulti_color_verbose was set to 1.","package":"vim-ultimate-colorscheme-utility-v0.1.3.tar","4":"vim-ultimate-colorscheme-utility-v0.1.3.tar","src_id":"20689","5":"20689","creation_date":"1376951240","6":"1376951240"},{"0":"4679","vim_version":"7.0","1":"7.0","script_version":"0.1.2","2":"0.1.2","version_comment":"Minor Bug Fix - Typo corrected that prevented manual saving and loading of favorites.","3":"Minor Bug Fix - Typo corrected that prevented manual saving and loading of favorites.","package":"vim-ultimate-colorscheme-utility-v0.1.2.tar","4":"vim-ultimate-colorscheme-utility-v0.1.2.tar","src_id":"20686","5":"20686","creation_date":"1376941838","6":"1376941838"},{"0":"4679","vim_version":"7.0","1":"7.0","script_version":"0.1.1","2":"0.1.1","version_comment":"Added explicit browsing of global favorites, documentation update and minor bug fixes.","3":"Added explicit browsing of global favorites, documentation update and minor bug fixes.","package":"vim-ultimate-colorscheme-utility-v0.1.1.zip","4":"vim-ultimate-colorscheme-utility-v0.1.1.zip","src_id":"20610","5":"20610","creation_date":"1375893838","6":"1375893838"},{"0":"4679","vim_version":"7.0","1":"7.0","script_version":"0.1.0","2":"0.1.0","version_comment":"Initial upload","3":"Initial upload","package":"vim-ultimate-colorscheme-utility.tar","4":"vim-ultimate-colorscheme-utility.tar","src_id":"20586","5":"20586","creation_date":"1375392800","6":"1375392800"}]},"4678":{"script_id":"4678","0":"4678","script_name":"neat.vim","1":"neat.vim","script_type":"utility","2":"utility","summary":"A simple VIM plugin to help you pretty print your data.","3":"A simple VIM plugin to help you pretty print your data.","description":"See https:\/\/bitbucket.org\/sareyko\/neat.vim or https:\/\/github.com\/sareyko\/neat.vim for details.","4":"See https:\/\/bitbucket.org\/sareyko\/neat.vim or https:\/\/github.com\/sareyko\/neat.vim for details.","install_details":"","5":"","first_name":"Sebastian","6":"Sebastian","last_name":"Sareyko","7":"Sareyko","releases":[{"0":"4678","vim_version":"7.4","1":"7.4","script_version":"1.1","2":"1.1","version_comment":"See https:\/\/bitbucket.org\/sareyko\/neat.vim\/overview for details and changelog.","3":"See https:\/\/bitbucket.org\/sareyko\/neat.vim\/overview for details and changelog.","package":"neat.vim-1.1.tar.gz","4":"neat.vim-1.1.tar.gz","src_id":"22078","5":"22078","creation_date":"1403446113","6":"1403446113"},{"0":"4678","vim_version":"7.3","1":"7.3","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"neat.vim-1.0.tar.gz","4":"neat.vim-1.0.tar.gz","src_id":"20585","5":"20585","creation_date":"1375387984","6":"1375387984"}]},"4677":{"script_id":"4677","0":"4677","script_name":"unstack","1":"unstack","script_type":"utility","2":"utility","summary":"Open files from stack traces in vsplits","3":"Open files from stack traces in vsplits","description":"Parse stack traces or quickfix entries and open the result in vim splits!\r\n\r\nGo from this: http:\/\/i.imgur.com\/DgXSAkq.png\r\nTo this: http:\/\/i.imgur.com\/Q31wohX.png\r\n\r\nFollow the development at https:\/\/github.com\/mattboehm\/unstack\r\n\r\nMuch more information on the github page and in the documentation.","4":"Parse stack traces or quickfix entries and open the result in vim splits!\r\n\r\nGo from this: http:\/\/i.imgur.com\/DgXSAkq.png\r\nTo this: http:\/\/i.imgur.com\/Q31wohX.png\r\n\r\nFollow the development at https:\/\/github.com\/mattboehm\/unstack\r\n\r\nMuch more information on the github page and in the documentation.","install_details":"Unzip into your ~\/.vim or use Pathogen\/Vundle\/etc.\r\n\r\nDon't forget to run :helptags to load the documentation.","5":"Unzip into your ~\/.vim or use Pathogen\/Vundle\/etc.\r\n\r\nDon't forget to run :helptags to load the documentation.","first_name":"Matthew","6":"Matthew","last_name":"Boehm","7":"Boehm","releases":[{"0":"4677","vim_version":"7.0","1":"7.0","script_version":"0.3.4","2":"0.3.4","version_comment":"Add portrait mode, option to populate qflist","3":"Add portrait mode, option to populate qflist","package":"vim-unstack-master.zip","4":"vim-unstack-master.zip","src_id":"20866","5":"20866","creation_date":"1380654882","6":"1380654882"},{"0":"4677","vim_version":"7.0","1":"7.0","script_version":"0.3.0","2":"0.3.0","version_comment":"Initial upload","3":"Initial upload","package":"unstack.zip","4":"unstack.zip","src_id":"20583","5":"20583","creation_date":"1375333989","6":"1375333989"}]},"4676":{"script_id":"4676","0":"4676","script_name":"better-header","1":"better-header","script_type":"utility","2":"utility","summary":"add file header automatically and intelligently","3":"add file header automatically and intelligently","description":"https:\/\/github.com\/xiaket\/better-header#introduction","4":"https:\/\/github.com\/xiaket\/better-header#introduction","install_details":"cd ~\/.vim\/bundle\r\ngit clone https:\/\/github.com\/xiaket\/better-header.git","5":"cd ~\/.vim\/bundle\r\ngit clone https:\/\/github.com\/xiaket\/better-header.git","first_name":"Xia","6":"Xia","last_name":"Kai","7":"Kai","releases":[{"0":"4676","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"better-header.vim","4":"better-header.vim","src_id":"20582","5":"20582","creation_date":"1375328049","6":"1375328049"}]},"4675":{"script_id":"4675","0":"4675","script_name":"Vertigo","1":"Vertigo","script_type":"utility","2":"utility","summary":"A better way to move vertically.","3":"A better way to move vertically.","description":"Vertigo.vim is a Vim plugin is based on a simple idea: that moving up and down using relative line numbers (e.g., 3j, 15k) is a very simple and precise way of moving around vertically, and shouldn't require your hands to leave home row.\r\n\r\nTo show how Vertigo works, let's look an example: say you want to go to some line that you can see (with relativenumber) is 14 lines down.\r\n\r\nWith this plugin, you'd press <Space>j to activate \"jump mode.\" Vim then waits for two home-row keypresses representing a two-digit number, mapping asdfghjkl; to 1234567890. You then press af for 14, and just like that, you're 14 lines down. Easy! For one-digit numbers, just hit shift. (<Space>jF goes four lines down)\r\n\r\nSee the GitHub page for more details and installation instructions:\r\nhttps:\/\/github.com\/prendradjaja\/vim-vertigo","4":"Vertigo.vim is a Vim plugin is based on a simple idea: that moving up and down using relative line numbers (e.g., 3j, 15k) is a very simple and precise way of moving around vertically, and shouldn't require your hands to leave home row.\r\n\r\nTo show how Vertigo works, let's look an example: say you want to go to some line that you can see (with relativenumber) is 14 lines down.\r\n\r\nWith this plugin, you'd press <Space>j to activate \"jump mode.\" Vim then waits for two home-row keypresses representing a two-digit number, mapping asdfghjkl; to 1234567890. You then press af for 14, and just like that, you're 14 lines down. Easy! For one-digit numbers, just hit shift. (<Space>jF goes four lines down)\r\n\r\nSee the GitHub page for more details and installation instructions:\r\nhttps:\/\/github.com\/prendradjaja\/vim-vertigo","install_details":"","5":"","first_name":"Pandu","6":"Pandu","last_name":"Rendradjaja","7":"Rendradjaja","releases":[{"0":"4675","vim_version":"7.2","1":"7.2","script_version":"1.0.0","2":"1.0.0","version_comment":"Initial upload","3":"Initial upload","package":"vertigo.zip","4":"vertigo.zip","src_id":"20576","5":"20576","creation_date":"1375154826","6":"1375154826"}]},"4674":{"script_id":"4674","0":"4674","script_name":"node","1":"node","script_type":"utility","2":"utility","summary":"Tools to make Vim superb for developing with Node.js. Like Rails.vim for Node.","3":"Tools to make Vim superb for developing with Node.js. Like Rails.vim for Node.","description":"Tools to make Vim superb for developing with Node.js.\r\nIt's the Node equivalent of Rails.vim (vimscript #1567) and Rake.vim (vimscript #3669).\r\n\r\nThis is just the first release to get the nodes rolling. If you've collected great helpers and shortcuts that help you work with Node, please share them via email (andri@dot.ee), Twitter (https:\/\/twitter.com\/theml) GitHub issues (https:\/\/github.com\/moll\/vim-node\/issues) so we could incorporate them here, too! Thanks!\r\n\r\nTour:\r\n- Use gf on paths or requires to open the same file Node.js would.\r\n- Use gf on require(\".\") to open .\/index.js\r\n- Use gf on require(\".\/dir\") to open .\/dir\/index.js\r\n- Use gf on require(\".\/foo\") to open foo.js.\r\n- Use gf on require(\".\/package\") and have it open package.json.\r\n- Use gf on require(\"module\") to open the module's main file (parsed for you from package.json).\r\n- Use gf on require(\"module\/lib\/utils\") and open files inside the module.\r\n- Automatically sets the filetype to JavaScript for files with Node's shebang (#!).\r\n- Use [I etc. to look for a keyword in required files (Sets Vim's &include).\r\n- Use :Nedit to quickly edit any module, file in a module or your project file.\r\n- Use :Nopen to quickly edit any module and lcd to its directory.\r\n- Node.vim itself is tested with a thorough automated integration test suite! No cowboy coding here!\r\n\r\nExpect more to come soon and feel free to let me know what you're after!\r\n\r\nPS. Node.vim is absolutely intended to work on Windows, but not yet tested there at all. If you could help, try it out and report issues, I'd be grateful!\r\n\r\nLatest development version and more info with full README at https:\/\/github.com\/moll\/vim-node.","4":"Tools to make Vim superb for developing with Node.js.\r\nIt's the Node equivalent of Rails.vim (vimscript #1567) and Rake.vim (vimscript #3669).\r\n\r\nThis is just the first release to get the nodes rolling. If you've collected great helpers and shortcuts that help you work with Node, please share them via email (andri@dot.ee), Twitter (https:\/\/twitter.com\/theml) GitHub issues (https:\/\/github.com\/moll\/vim-node\/issues) so we could incorporate them here, too! Thanks!\r\n\r\nTour:\r\n- Use gf on paths or requires to open the same file Node.js would.\r\n- Use gf on require(\".\") to open .\/index.js\r\n- Use gf on require(\".\/dir\") to open .\/dir\/index.js\r\n- Use gf on require(\".\/foo\") to open foo.js.\r\n- Use gf on require(\".\/package\") and have it open package.json.\r\n- Use gf on require(\"module\") to open the module's main file (parsed for you from package.json).\r\n- Use gf on require(\"module\/lib\/utils\") and open files inside the module.\r\n- Automatically sets the filetype to JavaScript for files with Node's shebang (#!).\r\n- Use [I etc. to look for a keyword in required files (Sets Vim's &include).\r\n- Use :Nedit to quickly edit any module, file in a module or your project file.\r\n- Use :Nopen to quickly edit any module and lcd to its directory.\r\n- Node.vim itself is tested with a thorough automated integration test suite! No cowboy coding here!\r\n\r\nExpect more to come soon and feel free to let me know what you're after!\r\n\r\nPS. Node.vim is absolutely intended to work on Windows, but not yet tested there at all. If you could help, try it out and report issues, I'd be grateful!\r\n\r\nLatest development version and more info with full README at https:\/\/github.com\/moll\/vim-node.","install_details":"","5":"","first_name":"Andri","6":"Andri","last_name":"M\u00c3\u00b6ll","7":"M\u00c3\u00b6ll","releases":[{"0":"4674","vim_version":"7.0","1":"7.0","script_version":"0.8.1","2":"0.8.1","version_comment":"- Updates the URL from which Node.vim downloads Node core module source files.  \r\n  Uses <http:\/\/rawgit.com> which used to be named <http:\/\/rawgithub.com>.  \r\n  Because of Vim Netrw's inability to handle HTTPS, it does so over HTTP. Sorry.","3":"- Updates the URL from which Node.vim downloads Node core module source files.  \r\n  Uses <http:\/\/rawgit.com> which used to be named <http:\/\/rawgithub.com>.  \r\n  Because of Vim Netrw's inability to handle HTTPS, it does so over HTTP. Sorry.","package":"node-0.8.1.zip","4":"node-0.8.1.zip","src_id":"21777","5":"21777","creation_date":"1397584540","6":"1397584540"},{"0":"4674","vim_version":"7.0","1":"7.0","script_version":"0.8.0","2":"0.8.0","version_comment":"- Adds `node` as a core module so you could use `:Nedit node` to open the file Node uses to bootstrap its core.","3":"- Adds `node` as a core module so you could use `:Nedit node` to open the file Node uses to bootstrap its core.","package":"node-0.8.0.zip","4":"node-0.8.0.zip","src_id":"20762","5":"20762","creation_date":"1378499426","6":"1378499426"},{"0":"4674","vim_version":"7.0","1":"7.0","script_version":"0.7.0","2":"0.7.0","version_comment":"- Adds support for opening core Node.js modules, such as `http`, `util`, etc. with `gf` or `:Nedit`.\r\n  They're shown straight from Node's online repository without you having to download everything.","3":"- Adds support for opening core Node.js modules, such as `http`, `util`, etc. with `gf` or `:Nedit`.\r\n  They're shown straight from Node's online repository without you having to download everything.","package":"node-0.7.0.zip","4":"node-0.7.0.zip","src_id":"20723","5":"20723","creation_date":"1377687247","6":"1377687247"},{"0":"4674","vim_version":"7.0","1":"7.0","script_version":"0.6.0","2":"0.6.0","version_comment":"- Adds `:Nedit` command for editing modules or files relative to the Node project root.\r\n  For example: `:Nedit any-module\/lib` or `:Nedit .\/package`.\r\n- Adds `:Nopen` command which behaves like `:Nedit`, but also `lcd`s to the module's directory.\r\n- Makes `<Plug>NodeGotoFile` available for your mapping in any Node project file, but maps it to `gf` automatically only on JavaScript files.\r\n- Maps `gf` also for JSON files for easy jumping to modules.\r\n- Makes `:Nedit` and `:Nopen` available immediately when starting Vim in a directory of a Node project.","3":"- Adds `:Nedit` command for editing modules or files relative to the Node project root.\r\n  For example: `:Nedit any-module\/lib` or `:Nedit .\/package`.\r\n- Adds `:Nopen` command which behaves like `:Nedit`, but also `lcd`s to the module's directory.\r\n- Makes `<Plug>NodeGotoFile` available for your mapping in any Node project file, but maps it to `gf` automatically only on JavaScript files.\r\n- Maps `gf` also for JSON files for easy jumping to modules.\r\n- Makes `:Nedit` and `:Nopen` available immediately when starting Vim in a directory of a Node project.","package":"node-0.6.0.zip","4":"node-0.6.0.zip","src_id":"20704","5":"20704","creation_date":"1377285737","6":"1377285737"},{"0":"4674","vim_version":"7.0","1":"7.0","script_version":"0.5.1","2":"0.5.1","version_comment":"- Adds `Node` autocommand.  \r\n  Use it with `autocmd User Node` to customize settings for files in Node projects.\r\n- Adds `<Plug>NodeVSplitGotoFile` for those who want `<C-w>f` to split vertically.","3":"- Adds `Node` autocommand.  \r\n  Use it with `autocmd User Node` to customize settings for files in Node projects.\r\n- Adds `<Plug>NodeVSplitGotoFile` for those who want `<C-w>f` to split vertically.","package":"node-0.5.1.zip","4":"node-0.5.1.zip","src_id":"20612","5":"20612","creation_date":"1375917283","6":"1375917283"},{"0":"4674","vim_version":"7.0","1":"7.0","script_version":"0.5.0","2":"0.5.0","version_comment":"- Adds `&include` pattern so Vim can recognize included\/required files, e.g. for looking up keywords with `[I`.\r\n- Cleans `&path` from `\/usr\/include` for JavaScript files.\r\n- Adds a new superb `gf` handler to handle all relative and module paths, incl. support for `require(\".\")` to open `.\/index.js`. This is spot on how Node.js finds your requires.\r\n- Adds `<Plug>NodeGotoFile` should you want to remap Node.vim's file opener.\r\n- Opens files before directories should both, e.g. `.\/foo.js` and `.\/foo`, exist. This matches Node.js's behavior.\r\n- Adds a full automated integration test suite to Node.vim which is freaking amazing!","3":"- Adds `&include` pattern so Vim can recognize included\/required files, e.g. for looking up keywords with `[I`.\r\n- Cleans `&path` from `\/usr\/include` for JavaScript files.\r\n- Adds a new superb `gf` handler to handle all relative and module paths, incl. support for `require(\".\")` to open `.\/index.js`. This is spot on how Node.js finds your requires.\r\n- Adds `<Plug>NodeGotoFile` should you want to remap Node.vim's file opener.\r\n- Opens files before directories should both, e.g. `.\/foo.js` and `.\/foo`, exist. This matches Node.js's behavior.\r\n- Adds a full automated integration test suite to Node.vim which is freaking amazing!","package":"node-0.5.0.zip","4":"node-0.5.0.zip","src_id":"20601","5":"20601","creation_date":"1375661872","6":"1375661872"},{"0":"4674","vim_version":"7.0","1":"7.0","script_version":"0.2.0","2":"0.2.0","version_comment":"- Adds full support for navigating to module files by using `gf` on `require(\"any-module\")`.\r\n- Adds `.json` to `&suffixesadd` so you could use `gf` on `require(\".\/package\")` to open package.json.","3":"- Adds full support for navigating to module files by using `gf` on `require(\"any-module\")`.\r\n- Adds `.json` to `&suffixesadd` so you could use `gf` on `require(\".\/package\")` to open package.json.","package":"node-0.2.0.zip","4":"node-0.2.0.zip","src_id":"20573","5":"20573","creation_date":"1375027412","6":"1375027412"},{"0":"4674","vim_version":"7.0","1":"7.0","script_version":"0.1.1","2":"0.1.1","version_comment":"- Removes an innocent but forgotten debugging line.","3":"- Removes an innocent but forgotten debugging line.","package":"node-0.1.1.zip","4":"node-0.1.1.zip","src_id":"20572","5":"20572","creation_date":"1375013854","6":"1375013854"},{"0":"4674","vim_version":"7.0","1":"7.0","script_version":"0.1.0","2":"0.1.0","version_comment":"Initial upload","3":"Initial upload","package":"node-0.1.0.zip","4":"node-0.1.0.zip","src_id":"20571","5":"20571","creation_date":"1375011989","6":"1375011989"}]},"4673":{"script_id":"4673","0":"4673","script_name":"ctrlp-tjump","1":"ctrlp-tjump","script_type":"utility","2":"utility","summary":"CtrlP extension for fuzzy-search in tag matches (tjump\/tselect replacement)","3":"CtrlP extension for fuzzy-search in tag matches (tjump\/tselect replacement)","description":"CtrlP extension for fuzzy-searching in tag matches. May be used instead of :tjump or :tselect for IDE-like Goto declaration functionality, which jumps to the declaration in case of one match, and shows quick-search window in case of multiple matches.\r\n\r\nTwo vim commands are created by this plugin:\r\n\r\n* `CtrlPtjump` - go to declaration of the identifier under cursor\r\n* `CtrlPtjumpVisual` - go to declaration of the visual selected text\r\n\r\nhttps:\/\/github.com\/ivalkeen\/vim-ctrlp-tjump\r\n\r\nPrerequisites:\r\n1. CtrlP should be installed\r\n2. Tags should already work with :tag, :tselect and :tjump commands.\r\n\r\nInstallation:\r\n1. Use your favorite method (I prefer Vundle)\r\n2. (Optional) Create mappings:\r\nnnoremap <c-]> :CtrlPtjump<cr>\r\nvnoremap <c-]> :CtrlPtjumpVisual<cr>\r\n\r\n\r\nUsage:\r\n1. Move cursor to the Class\/Method usage in your code\r\n2. Press c-] (if you have created mapping) or just execute :CtrlPtjump in the command line (or `:CtrlPtjumpVisual` in visual mode) in the command line.\r\n\r\nScreenshot: https:\/\/github-camo.global.ssl.fastly.net\/41125e06c9b55368d39d59c50ff136b5b6867a87\/687474703a2f2f692e696d6775722e636f6d2f3155724d4f70642e706e67","4":"CtrlP extension for fuzzy-searching in tag matches. May be used instead of :tjump or :tselect for IDE-like Goto declaration functionality, which jumps to the declaration in case of one match, and shows quick-search window in case of multiple matches.\r\n\r\nTwo vim commands are created by this plugin:\r\n\r\n* `CtrlPtjump` - go to declaration of the identifier under cursor\r\n* `CtrlPtjumpVisual` - go to declaration of the visual selected text\r\n\r\nhttps:\/\/github.com\/ivalkeen\/vim-ctrlp-tjump\r\n\r\nPrerequisites:\r\n1. CtrlP should be installed\r\n2. Tags should already work with :tag, :tselect and :tjump commands.\r\n\r\nInstallation:\r\n1. Use your favorite method (I prefer Vundle)\r\n2. (Optional) Create mappings:\r\nnnoremap <c-]> :CtrlPtjump<cr>\r\nvnoremap <c-]> :CtrlPtjumpVisual<cr>\r\n\r\n\r\nUsage:\r\n1. Move cursor to the Class\/Method usage in your code\r\n2. Press c-] (if you have created mapping) or just execute :CtrlPtjump in the command line (or `:CtrlPtjumpVisual` in visual mode) in the command line.\r\n\r\nScreenshot: https:\/\/github-camo.global.ssl.fastly.net\/41125e06c9b55368d39d59c50ff136b5b6867a87\/687474703a2f2f692e696d6775722e636f6d2f3155724d4f70642e706e67","install_details":"Unzip into your .vim directory or use Pathogen\/Vundle","5":"Unzip into your .vim directory or use Pathogen\/Vundle","first_name":"Ivan","6":"Ivan","last_name":"Tkalin","7":"Tkalin","releases":[{"0":"4673","vim_version":"7.4","1":"7.4","script_version":"0.2.0","2":"0.2.0","version_comment":"Support all CtrlP file open modes (current window, new tab, vertical split, horizontal split)","3":"Support all CtrlP file open modes (current window, new tab, vertical split, horizontal split)","package":"vim-ctrlp-tjump-0.2.0.zip","4":"vim-ctrlp-tjump-0.2.0.zip","src_id":"22136","5":"22136","creation_date":"1404649016","6":"1404649016"},{"0":"4673","vim_version":"7.0","1":"7.0","script_version":"0.1.0","2":"0.1.0","version_comment":"Added CtrlPtjumpVisual command to go to declaration of the selected text. Bugfixes.","3":"Added CtrlPtjumpVisual command to go to declaration of the selected text. Bugfixes.","package":"vim-ctrlp-tjump-0.1.0.tar.gz","4":"vim-ctrlp-tjump-0.1.0.tar.gz","src_id":"20734","5":"20734","creation_date":"1377881326","6":"1377881326"},{"0":"4673","vim_version":"7.0","1":"7.0","script_version":"0.0.1","2":"0.0.1","version_comment":"Initial upload","3":"Initial upload","package":"vim-ctrlp-tjump-0.0.1.tar.gz","4":"vim-ctrlp-tjump-0.0.1.tar.gz","src_id":"20569","5":"20569","creation_date":"1374870328","6":"1374870328"}]},"4672":{"script_id":"4672","0":"4672","script_name":"nerdtree-execute","1":"nerdtree-execute","script_type":"utility","2":"utility","summary":"Execute OS file\/dir handler from NERDTree","3":"Execute OS file\/dir handler from NERDTree","description":"Plugin for NERDTree that provides an execute menu item, that executes system default application for file or directory.\r\n\r\nhttps:\/\/github.com\/ivalkeen\/nerdtree-execute\r\n\r\nCurrently works only on Linux and Windows (experimental)\r\n\r\nUsage:\r\nWhen navigating in NERDTree, select file or directory, press 'm' key, and NERDTree menu will appear. Press 'x' then to execute system default application for selected file\/directory, using this plugin. You can open your favourite image editor for images, pdf reader for pdfs etc.","4":"Plugin for NERDTree that provides an execute menu item, that executes system default application for file or directory.\r\n\r\nhttps:\/\/github.com\/ivalkeen\/nerdtree-execute\r\n\r\nCurrently works only on Linux and Windows (experimental)\r\n\r\nUsage:\r\nWhen navigating in NERDTree, select file or directory, press 'm' key, and NERDTree menu will appear. Press 'x' then to execute system default application for selected file\/directory, using this plugin. You can open your favourite image editor for images, pdf reader for pdfs etc.","install_details":"Unzip into your .vim directory or use Pathogen\/Vundle","5":"Unzip into your .vim directory or use Pathogen\/Vundle","first_name":"Ivan","6":"Ivan","last_name":"Tkalin","7":"Tkalin","releases":[{"0":"4672","vim_version":"7.2","1":"7.2","script_version":"0.0.2","2":"0.0.2","version_comment":"Add OS X support\r\nFix KDE support","3":"Add OS X support\r\nFix KDE support","package":"nerdtree-execute-0.0.2.zip","4":"nerdtree-execute-0.0.2.zip","src_id":"23309","5":"23309","creation_date":"1432581958","6":"1432581958"},{"0":"4672","vim_version":"7.0","1":"7.0","script_version":"0.0.1","2":"0.0.1","version_comment":"Initial upload","3":"Initial upload","package":"nerdtree-execute-0.0.1.tar.gz","4":"nerdtree-execute-0.0.1.tar.gz","src_id":"20568","5":"20568","creation_date":"1374869675","6":"1374869675"}]},"4671":{"script_id":"4671","0":"4671","script_name":"locate.vim","1":"locate.vim","script_type":"utility","2":"utility","summary":"lvimgrep search enhanced","3":"lvimgrep search enhanced","description":"https:\/\/github.com\/mtth\/locate.vim","4":"https:\/\/github.com\/mtth\/locate.vim","install_details":"","5":"","first_name":"Matthieu","6":"Matthieu","last_name":"Monsch","7":"Monsch","releases":[{"0":"4671","vim_version":"7.0","1":"7.0","script_version":"1.3.0","2":"1.3.0","version_comment":"* Optional search flags\r\n* Chainable patterns\r\n* g:locate_mappings option","3":"* Optional search flags\r\n* Chainable patterns\r\n* g:locate_mappings option","package":"locate.tar.gz","4":"locate.tar.gz","src_id":"20638","5":"20638","creation_date":"1376401429","6":"1376401429"},{"0":"4671","vim_version":"7.0","1":"7.0","script_version":"1.2.0","2":"1.2.0","version_comment":"Added g:locate_jump_to, g:locate_refresh, and g:locate_sort options.","3":"Added g:locate_jump_to, g:locate_refresh, and g:locate_sort options.","package":"locate.tar.gz","4":"locate.tar.gz","src_id":"20618","5":"20618","creation_date":"1376082867","6":"1376082867"},{"0":"4671","vim_version":"7.0","1":"7.0","script_version":"1.1.0","2":"1.1.0","version_comment":"Additions:\r\n  * Automatic location list closing\r\n  * |:Lpurge|, |:Lrefresh| commands\r\n  * Multiple windows per buffer supported\r\n  * Multiple tabs supported","3":"Additions:\r\n  * Automatic location list closing\r\n  * |:Lpurge|, |:Lrefresh| commands\r\n  * Multiple windows per buffer supported\r\n  * Multiple tabs supported","package":"locate.tar.gz","4":"locate.tar.gz","src_id":"20574","5":"20574","creation_date":"1375064302","6":"1375064302"},{"0":"4671","vim_version":"7.0","1":"7.0","script_version":"1.0.0","2":"1.0.0","version_comment":"Initial upload","3":"Initial upload","package":"locate.tar.gz","4":"locate.tar.gz","src_id":"20567","5":"20567","creation_date":"1374868211","6":"1374868211"}]},"4670":{"script_id":"4670","0":"4670","script_name":"android.vim","1":"android.vim","script_type":"utility","2":"utility","summary":"Initial release","3":"Initial release","description":"** ALPHA release **\r\n\r\nThis is my attempt at a more clean, efficient and powerful means of building Android applications in Vim. Check the README for more information.","4":"** ALPHA release **\r\n\r\nThis is my attempt at a more clean, efficient and powerful means of building Android applications in Vim. Check the README for more information.","install_details":"I recommend using Vundle (https:\/\/github.com\/gmarik\/vundle) to install plugins.\r\n\r\nOtherwise just extract this into your $VIM directory.","5":"I recommend using Vundle (https:\/\/github.com\/gmarik\/vundle) to install plugins.\r\n\r\nOtherwise just extract this into your $VIM directory.","first_name":"Jacky","6":"Jacky","last_name":"Alcin\u00c3\u00a9","7":"Alcin\u00c3\u00a9","releases":[{"0":"4670","vim_version":"7.2","1":"7.2","script_version":"0.2.0-1","2":"0.2.0-1","version_comment":"Initial upload","3":"Initial upload","package":"android.vim-0.2.0-1.tar.gz","4":"android.vim-0.2.0-1.tar.gz","src_id":"20566","5":"20566","creation_date":"1374829692","6":"1374829692"}]},"4669":{"script_id":"4669","0":"4669","script_name":"bluecloud","1":"bluecloud","script_type":"color scheme","2":"color scheme","summary":"A blue\/gray theme with a colorful palette.","3":"A blue\/gray theme with a colorful palette.","description":"A color scheme dark enough, and colorful enough. For GVim the theme\r\nis blueish (bluecloud). Due to limitations with the default 256-palette, under\r\nxterm the theme is grayish (shadow of a bluecloud?).","4":"A color scheme dark enough, and colorful enough. For GVim the theme\r\nis blueish (bluecloud). Due to limitations with the default 256-palette, under\r\nxterm the theme is grayish (shadow of a bluecloud?).","install_details":"Place `bluecloud.vim` in your `~\/.vim\/colors` folder. While running Vim, you\r\ncan use this theme via the ex command \":colo bluecloud\".","5":"Place `bluecloud.vim` in your `~\/.vim\/colors` folder. While running Vim, you\r\ncan use this theme via the ex command \":colo bluecloud\".","first_name":"Edwin","6":"Edwin","last_name":"Pujols","7":"Pujols","releases":[{"0":"4669","vim_version":"7.0","1":"7.0","script_version":"1.4","2":"1.4","version_comment":"Added xterm \"equivalent\" color palette. (Call it shadow-of-bluecloud.)","3":"Added xterm \"equivalent\" color palette. (Call it shadow-of-bluecloud.)","package":"bluecloud.vim","4":"bluecloud.vim","src_id":"20834","5":"20834","creation_date":"1379989034","6":"1379989034"},{"0":"4669","vim_version":"7.0","1":"7.0","script_version":"1.2","2":"1.2","version_comment":"Revamped palette. (Into special consideration, TeX\/LaTeX, diff mode, Python and NERDtree.)","3":"Revamped palette. (Into special consideration, TeX\/LaTeX, diff mode, Python and NERDtree.)","package":"bluecloud.vim","4":"bluecloud.vim","src_id":"20833","5":"20833","creation_date":"1379972985","6":"1379972985"},{"0":"4669","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"bluecloud.vim","4":"bluecloud.vim","src_id":"20564","5":"20564","creation_date":"1374699162","6":"1374699162"}]},"4668":{"script_id":"4668","0":"4668","script_name":"TurboMark","1":"TurboMark","script_type":"utility","2":"utility","summary":"Mark and find lines in your open buffers on steroids","3":"Mark and find lines in your open buffers on steroids","description":"This plugin intends to replace the functionality of the m and ' keys that Vim\r\nprovides in normal mode. By using this plugin, you don't need to memorize a\r\nregister for each line you mark, you just mark it with m. Marked lines go into\r\na list which is displayed by using the ' mapping. Upon pressing ', the quickfix\r\nwindow opens, populated with the already marked lines and the editor is\r\nautomatically entered into search mode. This way, you can immediately type part\r\nof the line you've previously marked, hit double-enter (the first is to exit\r\nsearch-mode) and you're exactly where you want to be.","4":"This plugin intends to replace the functionality of the m and ' keys that Vim\r\nprovides in normal mode. By using this plugin, you don't need to memorize a\r\nregister for each line you mark, you just mark it with m. Marked lines go into\r\na list which is displayed by using the ' mapping. Upon pressing ', the quickfix\r\nwindow opens, populated with the already marked lines and the editor is\r\nautomatically entered into search mode. This way, you can immediately type part\r\nof the line you've previously marked, hit double-enter (the first is to exit\r\nsearch-mode) and you're exactly where you want to be.","install_details":"Just paste the package's contents into into your .vim directory.\r\n\r\nInstalling with Pathogen:\r\n\r\n    cd ~\/.vim\/bundle\r\n    git clone git:\/\/github.com\/kbairak\/TurboMark.git\r\n","5":"Just paste the package's contents into into your .vim directory.\r\n\r\nInstalling with Pathogen:\r\n\r\n    cd ~\/.vim\/bundle\r\n    git clone git:\/\/github.com\/kbairak\/TurboMark.git\r\n","first_name":"Konstantinos","6":"Konstantinos","last_name":"Bairaktaris","7":"Bairaktaris","releases":[{"0":"4668","vim_version":"7.0","1":"7.0","script_version":"0.2","2":"0.2","version_comment":"Major changes\r\n\r\n- exit quickfix window when navigating to a mark\r\n- save and reload marks from text file in home folder","3":"Major changes\r\n\r\n- exit quickfix window when navigating to a mark\r\n- save and reload marks from text file in home folder","package":"TurboMark-0.2.zip","4":"TurboMark-0.2.zip","src_id":"21956","5":"21956","creation_date":"1401265340","6":"1401265340"},{"0":"4668","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"TurboMark.tar.gz","4":"TurboMark.tar.gz","src_id":"20561","5":"20561","creation_date":"1374663748","6":"1374663748"}]},"4667":{"script_id":"4667","0":"4667","script_name":"monokai","1":"monokai","script_type":"color scheme","2":"color scheme","summary":"Monokai colorscheme, originally ported to vim by Damien Gombault","3":"Monokai colorscheme, originally ported to vim by Damien Gombault","description":"Monokai colorscheme, originally ported to vim by Damien Gombault.\r\n\r\nThe original files lives here: http:\/\/desintegr.googlecode.com\/svn\/config\/vim\/colors\/monokai.vim, although it hasn't been updated since 2009.\r\n\r\nThe repos on Github (https:\/\/github.com\/lsdr\/monokai) and on vim.org serves only to allow monokai.vim to be found and installed using modern plugin managers for vim.","4":"Monokai colorscheme, originally ported to vim by Damien Gombault.\r\n\r\nThe original files lives here: http:\/\/desintegr.googlecode.com\/svn\/config\/vim\/colors\/monokai.vim, although it hasn't been updated since 2009.\r\n\r\nThe repos on Github (https:\/\/github.com\/lsdr\/monokai) and on vim.org serves only to allow monokai.vim to be found and installed using modern plugin managers for vim.","install_details":"Download and copy the monokai.vim colorscheme file directly into your .vim\/colors folder.\r\n\r\nYou can fetch it over the net, if you prefer:\r\n\r\n   $ cd ~\/.vim\r\n   $ curl -G https:\/\/raw.githubusercontent.com\/lsdr\/monokai\/master\/colors\/monokai.vim -o monokai.vim\r\n\r\nVia Vundle (vimscript #3458):\r\n\r\n   Bundle 'lsdr\/monokai'","5":"Download and copy the monokai.vim colorscheme file directly into your .vim\/colors folder.\r\n\r\nYou can fetch it over the net, if you prefer:\r\n\r\n   $ cd ~\/.vim\r\n   $ curl -G https:\/\/raw.githubusercontent.com\/lsdr\/monokai\/master\/colors\/monokai.vim -o monokai.vim\r\n\r\nVia Vundle (vimscript #3458):\r\n\r\n   Bundle 'lsdr\/monokai'","first_name":"Luiz","6":"Luiz","last_name":"Rocha","7":"Rocha","releases":[{"0":"4667","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"monokai.vim","4":"monokai.vim","src_id":"20558","5":"20558","creation_date":"1374544527","6":"1374544527"}]},"4666":{"script_id":"4666","0":"4666","script_name":"vim-berks","1":"vim-berks","script_type":"utility","2":"utility","summary":"basic vim\/berks integration","3":"basic vim\/berks integration","description":"This plugin adds a :Berks command that runs berkshelf, with tab completion of subcommands. It also sets up Berksfiles to be highlighted as Ruby.","4":"This plugin adds a :Berks command that runs berkshelf, with tab completion of subcommands. It also sets up Berksfiles to be highlighted as Ruby.","install_details":"","5":"","first_name":"Mark","6":"Mark","last_name":"Cornick","7":"Cornick","releases":[{"0":"4666","vim_version":"7.0","1":"7.0","script_version":"1.0.1","2":"1.0.1","version_comment":"Fix stupid search\/replace induced error in plugin","3":"Fix stupid search\/replace induced error in plugin","package":"vim-berks-1.0.1.tar.gz","4":"vim-berks-1.0.1.tar.gz","src_id":"20557","5":"20557","creation_date":"1374528891","6":"1374528891"}]},"4665":{"script_id":"4665","0":"4665","script_name":"ctrlp-ssh","1":"ctrlp-ssh","script_type":"utility","2":"utility","summary":"Open new SSH connections via ctrlp.vim interface","3":"Open new SSH connections via ctrlp.vim interface","description":"ctrlp-ssh\r\n============\r\n\r\nSYNOPSIS\r\n----------\r\nYou can do SSH to a server via ctrlp.vim interface using this plugin.\r\nNote that this plugin is a ctrlp.vim extension and it requires a runner (only *tmux* is currently supported).\r\n\r\nscreenshot: http:\/\/i.imgur.com\/PvIvax0.png\r\n\r\n\r\nPREMISE\r\n----------\r\nFirst, I believe you're a user of a great Vim plugin ctrlp.vim.\r\nOtherwise, you need to install it before start installing this plugin.\r\nSecond, this plugin requires tmux to open a new SSH window (currently).\r\n\r\n\r\nCONFIGURATION\r\n----------\r\nIt's useful to define a mapping like this:\r\n\r\n    nnoremap <Leader>fs :CtrlPSSH<Cr>\r\n\r\n\r\nLINK\r\n--------------\r\n\r\n* ctrlpvim\/ctrlp.vim: https:\/\/github.com\/ctrlpvim\/ctrlp.vim\r\n* tacahiroy\/ctrlp-ssh: https:\/\/github.com\/tacahiroy\/ctrlp-ssh\r\n\r\nLICENSE\r\n-------\r\n\r\nCopyright (c) 2013-2015 Takahiro Yoshihara. Distributed under the Modified BSD License.\r\n","4":"ctrlp-ssh\r\n============\r\n\r\nSYNOPSIS\r\n----------\r\nYou can do SSH to a server via ctrlp.vim interface using this plugin.\r\nNote that this plugin is a ctrlp.vim extension and it requires a runner (only *tmux* is currently supported).\r\n\r\nscreenshot: http:\/\/i.imgur.com\/PvIvax0.png\r\n\r\n\r\nPREMISE\r\n----------\r\nFirst, I believe you're a user of a great Vim plugin ctrlp.vim.\r\nOtherwise, you need to install it before start installing this plugin.\r\nSecond, this plugin requires tmux to open a new SSH window (currently).\r\n\r\n\r\nCONFIGURATION\r\n----------\r\nIt's useful to define a mapping like this:\r\n\r\n    nnoremap <Leader>fs :CtrlPSSH<Cr>\r\n\r\n\r\nLINK\r\n--------------\r\n\r\n* ctrlpvim\/ctrlp.vim: https:\/\/github.com\/ctrlpvim\/ctrlp.vim\r\n* tacahiroy\/ctrlp-ssh: https:\/\/github.com\/tacahiroy\/ctrlp-ssh\r\n\r\nLICENSE\r\n-------\r\n\r\nCopyright (c) 2013-2015 Takahiro Yoshihara. Distributed under the Modified BSD License.\r\n","install_details":"If you use Vundle (https:\/\/github.com\/gmarik\/vundle.git) you can install this plugin using following Vim command:\r\n\r\n    :PluginInstall tacahiroy\/ctrlp-ssh\r\n\r\nIn addition, don't forget put a line `Plugin 'tacahiroy\/ctrlp-ssh'` into your .vimrc.\r\n\r\nIf you use pathogen.vim (https:\/\/github.com\/tpope\/vim-pathogen), you can do install this plugin with these commands:\r\n\r\n    cd ~\/.vim\/bundle\r\n    git clone git:\/\/github.com\/tacahiroy\/ctrlp-ssh.git\r\n\r\nYou don't use either plugin management systems, copy autoload and plugin directory to your .vim directory.","5":"If you use Vundle (https:\/\/github.com\/gmarik\/vundle.git) you can install this plugin using following Vim command:\r\n\r\n    :PluginInstall tacahiroy\/ctrlp-ssh\r\n\r\nIn addition, don't forget put a line `Plugin 'tacahiroy\/ctrlp-ssh'` into your .vimrc.\r\n\r\nIf you use pathogen.vim (https:\/\/github.com\/tpope\/vim-pathogen), you can do install this plugin with these commands:\r\n\r\n    cd ~\/.vim\/bundle\r\n    git clone git:\/\/github.com\/tacahiroy\/ctrlp-ssh.git\r\n\r\nYou don't use either plugin management systems, copy autoload and plugin directory to your .vim directory.","first_name":"Takahiro","6":"Takahiro","last_name":"Yoshihara","7":"Yoshihara","releases":[{"0":"4665","vim_version":"7.0","1":"7.0","script_version":"0.1.1","2":"0.1.1","version_comment":"Fix a stupid error: No such autoload function - ctrlp#ssh#runner#tmux","3":"Fix a stupid error: No such autoload function - ctrlp#ssh#runner#tmux","package":"ctrlp-ssh-0.1.1.zip","4":"ctrlp-ssh-0.1.1.zip","src_id":"22792","5":"22792","creation_date":"1421334321","6":"1421334321"},{"0":"4665","vim_version":"7.0","1":"7.0","script_version":"0.1.0","2":"0.1.0","version_comment":"New feature: keep ctrlp window to open SSH connection one after another.","3":"New feature: keep ctrlp window to open SSH connection one after another.","package":"ctrlp-ssh-0.1.0.zip","4":"ctrlp-ssh-0.1.0.zip","src_id":"20915","5":"20915","creation_date":"1381591259","6":"1381591259"},{"0":"4665","vim_version":"7.0","1":"7.0","script_version":"0.0.1","2":"0.0.1","version_comment":"Initial upload","3":"Initial upload","package":"ctrlp-ssh.zip","4":"ctrlp-ssh.zip","src_id":"20555","5":"20555","creation_date":"1374507199","6":"1374507199"}]},"4664":{"script_id":"4664","0":"4664","script_name":"bbye","1":"bbye","script_type":"utility","2":"utility","summary":"Delete buffers & close files without closing or messing up windows. Like Bclose.","3":"Delete buffers & close files without closing or messing up windows. Like Bclose.","description":"Bbye (Buffer Bye) allows you to do delete buffers (close files) without closing your windows or messing up your layout.\r\n\r\nVim by default closes all windows that have the buffer (file) open when you do :bdelete. If you've just got your splits and columns perfectly tuned, having them messed up equals a punch in the face and that's no way to tango.\r\n\r\nBbye gives you a :Bdelete command that behaves like a well designed citizen:\r\n- Closes and removes the buffer.\r\n- Shows another file in that window.\r\n- Shows an empty file if you've got no other files open.\r\n- Does not leave useless `[no file]` buffers if you decide to edit another file in that window.\r\n- Works even if a file's open in multiple windows.\r\n- Works a-okay with various buffer explorers and tabbars.\r\n\r\nLatest development version and more info with full README at https:\/\/github.com\/moll\/vim-bbye.","4":"Bbye (Buffer Bye) allows you to do delete buffers (close files) without closing your windows or messing up your layout.\r\n\r\nVim by default closes all windows that have the buffer (file) open when you do :bdelete. If you've just got your splits and columns perfectly tuned, having them messed up equals a punch in the face and that's no way to tango.\r\n\r\nBbye gives you a :Bdelete command that behaves like a well designed citizen:\r\n- Closes and removes the buffer.\r\n- Shows another file in that window.\r\n- Shows an empty file if you've got no other files open.\r\n- Does not leave useless `[no file]` buffers if you decide to edit another file in that window.\r\n- Works even if a file's open in multiple windows.\r\n- Works a-okay with various buffer explorers and tabbars.\r\n\r\nLatest development version and more info with full README at https:\/\/github.com\/moll\/vim-bbye.","install_details":"","5":"","first_name":"Andri","6":"Andri","last_name":"M\u00c3\u00b6ll","7":"M\u00c3\u00b6ll","releases":[{"0":"4664","vim_version":"7.0","1":"7.0","script_version":"1.0.1","2":"1.0.1","version_comment":"- Fix `:Bdelete`ing via buffer number. Finally, perfect!","3":"- Fix `:Bdelete`ing via buffer number. Finally, perfect!","package":"vim-bbye-1.0.1.zip","4":"vim-bbye-1.0.1.zip","src_id":"20560","5":"20560","creation_date":"1374596192","6":"1374596192"},{"0":"4664","vim_version":"7.0","1":"7.0","script_version":"1.0.0","2":"1.0.0","version_comment":"- Hides the empty buffer from buffer explorers and tabbars.\r\n- Handles `:Bdelete!`ing buffers which are set to auto-delete via `&bufhidden`.\r\n- Wipes empty buffers after hiding to reduce the amount of unlisted buffers after using Bbye for a while.\r\n- Handles buffer explorers and tabbars better that remove or add windows mid-flight.\r\n- Improves an edge-case where the empty buffer might get listed and show up in buffer explorers.\r\n- Perfect for v1.0.0.","3":"- Hides the empty buffer from buffer explorers and tabbars.\r\n- Handles `:Bdelete!`ing buffers which are set to auto-delete via `&bufhidden`.\r\n- Wipes empty buffers after hiding to reduce the amount of unlisted buffers after using Bbye for a while.\r\n- Handles buffer explorers and tabbars better that remove or add windows mid-flight.\r\n- Improves an edge-case where the empty buffer might get listed and show up in buffer explorers.\r\n- Perfect for v1.0.0.","package":"vim-bbye-1.0.0.zip","4":"vim-bbye-1.0.0.zip","src_id":"20559","5":"20559","creation_date":"1374584032","6":"1374584032"},{"0":"4664","vim_version":"7.0","1":"7.0","script_version":"0.9.1","2":"0.9.1","version_comment":"- Removed an innocent but forgotten debugging line. Now even more perfect.","3":"- Removed an innocent but forgotten debugging line. Now even more perfect.","package":"vim-bbye-0.9.1.zip","4":"vim-bbye-0.9.1.zip","src_id":"20553","5":"20553","creation_date":"1374398410","6":"1374398410"},{"0":"4664","vim_version":"7.0","1":"7.0","script_version":"0.9.0","2":"0.9.0","version_comment":"Initial upload","3":"Initial upload","package":"vim-bbye-0.9.0.zip","4":"vim-bbye-0.9.0.zip","src_id":"20552","5":"20552","creation_date":"1374364686","6":"1374364686"}]},"4663":{"script_id":"4663","0":"4663","script_name":"terra.vim","1":"terra.vim","script_type":"syntax","2":"syntax","summary":"Unofficial syntax highlighting for Terra (terralang.org)","3":"Unofficial syntax highlighting for Terra (terralang.org)","description":"Based entirely on lua.vim as bundled with my vim 7.3; a big hack, too, but I'm not a Vimscripter.\r\n\r\nhttp:\/\/terralang.org\/","4":"Based entirely on lua.vim as bundled with my vim 7.3; a big hack, too, but I'm not a Vimscripter.\r\n\r\nhttp:\/\/terralang.org\/","install_details":"ft=terra will engage.","5":"ft=terra will engage.","first_name":"Yuki","6":"Yuki","last_name":"Izumi","7":"Izumi","releases":[{"0":"4663","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"terra.vim","4":"terra.vim","src_id":"20551","5":"20551","creation_date":"1374322451","6":"1374322451"}]},"4662":{"script_id":"4662","0":"4662","script_name":"sprunge.vim","1":"sprunge.vim","script_type":"utility","2":"utility","summary":"A pastebin vim plugin for http:\/\/sprunge.us\/","3":"A pastebin vim plugin for http:\/\/sprunge.us\/","description":"There are several pastebin sites avalaible on the Internet, and there exist even a plugin for Gist: https:\/\/github.com\/mattn\/gist-vim. So why yet another pastebin plugin?, well, tell me 1 site who allow you fetch the content sanetely?, most of them ask you to open a browser and click here and there to get the juice.\r\n\r\nhttp:\/\/sprunge.us\/ doesn't not!, if you're confident in a terminal, try this:\r\n\r\n  $ ls | curl -F 'sprunge=<-' http:\/\/sprunge.us\r\n\r\nCurius for your output?, try now this:\r\n\r\n  $ curl <url-sprunge-generated>\r\n\r\nCool!?, eh?, now, wouldn't it be even more cool if you could paste directly from vim?\r\n\r\n2. Usage\r\n\r\n    :Sprunge\r\n\r\nAfter pressing <Enter>, you'll get a url with the content of your file. You\r\ncan also invoke this in visual mode to sprunge only the visual selection.\r\n\r\nAlternatively you may also use the '<Leader>s' mapping, you can override this\r\nmapping by setting 'g:sprunge_map' in your .vimrc","4":"There are several pastebin sites avalaible on the Internet, and there exist even a plugin for Gist: https:\/\/github.com\/mattn\/gist-vim. So why yet another pastebin plugin?, well, tell me 1 site who allow you fetch the content sanetely?, most of them ask you to open a browser and click here and there to get the juice.\r\n\r\nhttp:\/\/sprunge.us\/ doesn't not!, if you're confident in a terminal, try this:\r\n\r\n  $ ls | curl -F 'sprunge=<-' http:\/\/sprunge.us\r\n\r\nCurius for your output?, try now this:\r\n\r\n  $ curl <url-sprunge-generated>\r\n\r\nCool!?, eh?, now, wouldn't it be even more cool if you could paste directly from vim?\r\n\r\n2. Usage\r\n\r\n    :Sprunge\r\n\r\nAfter pressing <Enter>, you'll get a url with the content of your file. You\r\ncan also invoke this in visual mode to sprunge only the visual selection.\r\n\r\nAlternatively you may also use the '<Leader>s' mapping, you can override this\r\nmapping by setting 'g:sprunge_map' in your .vimrc","install_details":"The recommended way to get sprunge.vim is by combining github and vundle:\r\n\r\n     https:\/\/github.com\/chilicuil\/sprunge.vim\r\n\r\nVundle (recommended):\r\n=================\r\n\r\nAdd to your $HOME\/.vimrc file:\r\n\r\n    Bundle 'chilicuil\/sprunge.vim'\r\n\r\nRun inside of vim:\r\n\r\n    :BundleInstall\r\n\r\nPathogen:\r\n=======\r\n\r\n    $ git clone https:\/\/github.com\/chilicuil\/sprunge.vim.git ~\/.vim\/bundle\/sprunge.vim\r\n\r\nManual:\r\n=====\r\n\r\nDownload the zip file attached and extract the files in $HOME\/.vim\r\n\r\n    mv sprunge.vim*.zip $HOME\/.vim\r\n    cd $HOME\/.vim && unzip sprunge.vim*.zip\r\n\r\nUpdate the help tags:\r\n\r\n    :helpt ~\/.vim\/doc\/\r\n\r\nVote the plugin if you like it =)","5":"The recommended way to get sprunge.vim is by combining github and vundle:\r\n\r\n     https:\/\/github.com\/chilicuil\/sprunge.vim\r\n\r\nVundle (recommended):\r\n=================\r\n\r\nAdd to your $HOME\/.vimrc file:\r\n\r\n    Bundle 'chilicuil\/sprunge.vim'\r\n\r\nRun inside of vim:\r\n\r\n    :BundleInstall\r\n\r\nPathogen:\r\n=======\r\n\r\n    $ git clone https:\/\/github.com\/chilicuil\/sprunge.vim.git ~\/.vim\/bundle\/sprunge.vim\r\n\r\nManual:\r\n=====\r\n\r\nDownload the zip file attached and extract the files in $HOME\/.vim\r\n\r\n    mv sprunge.vim*.zip $HOME\/.vim\r\n    cd $HOME\/.vim && unzip sprunge.vim*.zip\r\n\r\nUpdate the help tags:\r\n\r\n    :helpt ~\/.vim\/doc\/\r\n\r\nVote the plugin if you like it =)","first_name":"chili","6":"chili","last_name":"cuil","7":"cuil","releases":[{"0":"4662","vim_version":"7.0","1":"7.0","script_version":"0.0.6","2":"0.0.6","version_comment":"* Add option g:sprunge_tabs2spaces to replace tabs with spaces\r\n      before aligning to left, WARNING: slow\r\n* Add option to align to the left before pasting, enabled by\r\n      g:sprunge_flush_left\r\n* Add new provider http:\/\/ix.io\r\n* Add notion of multiple providers, enabled by g:sprunge_providers","3":"* Add option g:sprunge_tabs2spaces to replace tabs with spaces\r\n      before aligning to left, WARNING: slow\r\n* Add option to align to the left before pasting, enabled by\r\n      g:sprunge_flush_left\r\n* Add new provider http:\/\/ix.io\r\n* Add notion of multiple providers, enabled by g:sprunge_providers","package":"sprunge.vim.zip","4":"sprunge.vim.zip","src_id":"25103","5":"25103","creation_date":"1493527407","6":"1493527407"}]},"4661":{"script_id":"4661","0":"4661","script_name":"vim-airline","1":"vim-airline","script_type":"utility","2":"utility","summary":"lean & mean statusline that's light as air","3":"lean & mean statusline that's light as air","description":"A fast and lightweight statusline for Vim that's easily configurable, extendable, and integrates with powerline font symbols.  It automatically integrates with a variety of 3rd party plugins and provides many themes out of the box.\r\n\r\nThe latest version can be found at https:\/\/github.com\/vim-airline\/vim-airline","4":"A fast and lightweight statusline for Vim that's easily configurable, extendable, and integrates with powerline font symbols.  It automatically integrates with a variety of 3rd party plugins and provides many themes out of the box.\r\n\r\nThe latest version can be found at https:\/\/github.com\/vim-airline\/vim-airline","install_details":"Extract the contents of the zip files into your vim runtime path.\r\n\r\nThe preferred installation method is to use Pathogen, Vundle, NeoBundle, or some other similar plugin manager.","5":"Extract the contents of the zip files into your vim runtime path.\r\n\r\nThe preferred installation method is to use Pathogen, Vundle, NeoBundle, or some other similar plugin manager.","first_name":"Bailey","6":"Bailey","last_name":"Ling","7":"Ling","releases":[{"0":"4661","vim_version":"7.2","1":"7.2","script_version":"0.11","2":"0.11","version_comment":"  - New features\r\n    - Extensions:\r\n      - [Coc](https:\/\/github.com\/neoclide\/coc.nvim) support\r\n      - [Defx](https:\/\/github.com\/Shougo\/defx.nvim) support\r\n      - [gina](https:\/\/github.com\/lambdalisue\/gina.vim) support\r\n      - [vim-bookmark](https:\/\/github.com\/MattesGroeger\/vim-bookmarks) support\r\n      - [vista.vim](https:\/\/github.com\/liuchengxu\/vista.vim) support\r\n      - [tabws](https:\/\/github.com\/s1341\/vim-tabws) support for the tabline\r\n  - Improvements\r\n    - The statusline can be configured to be shown on top (in the tabline)\r\n      Set the `g:airline_statusline_ontop` to enable this experimental feature.\r\n    - If `buffer_idx_mode=2`, up to 89 mappings will be exposed to access more\r\n      buffers directly (issue [#1823](https:\/\/github.com\/vim-airline\/vim-airline\/issues\/1823))\r\n    - Allow to use `random` as special theme name, which will switch to a random\r\n      airline theme (at least if a random number can be generated :()\r\n    - The branch extensions now also displays whether the repository is in a clean state\r\n      (will append a ! or ⚡if the repository is considered dirty).\r\n    - The whitespace extensions will also check for conflict markers\r\n    - `:AirlineRefresh` command now takes an additional `!` attribute, that **skips**\r\n      recreating the highlighting groups (which might have a serious performance\r\n      impact if done very often, as might be the case when the configuration variable\r\n      `airline_skip_empty_sections` is active).\r\n    - airline can now also detect multiple cursor mode (issue [#1933](https:\/\/github.com\/vim-airline\/vim-airline\/issues\/1933))\r\n    - expose hunks output using the function `airline#extensions#hunks#get_raw_hunks()` to the outside [#1877](https:\/\/github.com\/vim-airline\/vim-airline\/pull\/1877)\r\n    - expose wordcount affected filetype list to the public using the `airline#extensions#wordcount#filetypes` variable [#1887](https:\/\/github.com\/vim-airline\/vim-airline\/pull\/1887)\r\n    - for the `:AirlineExtension` command, indicate whether the extension has been loaded from an external source [#1890](https:\/\/github.com\/vim-airline\/vim-airline\/issues\/1890)\r\n    - correctly load custom wordcount formatters [#1896](https:\/\/github.com\/vim-airline\/vim-airline\/issues\/1896)\r\n    - add a new short_path formatter for the tabline [#1898](https:\/\/github.com\/vim-airline\/vim-airline\/pull\/1898)\r\n    - several improvements to the branch, denite and tabline extension, as well as the async code for Vim and Neovim\r\n    - the term extension supports [neoterm](https:\/\/github.com\/kassio\/neoterm) vim plugin","3":"  - New features\r\n    - Extensions:\r\n      - [Coc](https:\/\/github.com\/neoclide\/coc.nvim) support\r\n      - [Defx](https:\/\/github.com\/Shougo\/defx.nvim) support\r\n      - [gina](https:\/\/github.com\/lambdalisue\/gina.vim) support\r\n      - [vim-bookmark](https:\/\/github.com\/MattesGroeger\/vim-bookmarks) support\r\n      - [vista.vim](https:\/\/github.com\/liuchengxu\/vista.vim) support\r\n      - [tabws](https:\/\/github.com\/s1341\/vim-tabws) support for the tabline\r\n  - Improvements\r\n    - The statusline can be configured to be shown on top (in the tabline)\r\n      Set the `g:airline_statusline_ontop` to enable this experimental feature.\r\n    - If `buffer_idx_mode=2`, up to 89 mappings will be exposed to access more\r\n      buffers directly (issue [#1823](https:\/\/github.com\/vim-airline\/vim-airline\/issues\/1823))\r\n    - Allow to use `random` as special theme name, which will switch to a random\r\n      airline theme (at least if a random number can be generated :()\r\n    - The branch extensions now also displays whether the repository is in a clean state\r\n      (will append a ! or ⚡if the repository is considered dirty).\r\n    - The whitespace extensions will also check for conflict markers\r\n    - `:AirlineRefresh` command now takes an additional `!` attribute, that **skips**\r\n      recreating the highlighting groups (which might have a serious performance\r\n      impact if done very often, as might be the case when the configuration variable\r\n      `airline_skip_empty_sections` is active).\r\n    - airline can now also detect multiple cursor mode (issue [#1933](https:\/\/github.com\/vim-airline\/vim-airline\/issues\/1933))\r\n    - expose hunks output using the function `airline#extensions#hunks#get_raw_hunks()` to the outside [#1877](https:\/\/github.com\/vim-airline\/vim-airline\/pull\/1877)\r\n    - expose wordcount affected filetype list to the public using the `airline#extensions#wordcount#filetypes` variable [#1887](https:\/\/github.com\/vim-airline\/vim-airline\/pull\/1887)\r\n    - for the `:AirlineExtension` command, indicate whether the extension has been loaded from an external source [#1890](https:\/\/github.com\/vim-airline\/vim-airline\/issues\/1890)\r\n    - correctly load custom wordcount formatters [#1896](https:\/\/github.com\/vim-airline\/vim-airline\/issues\/1896)\r\n    - add a new short_path formatter for the tabline [#1898](https:\/\/github.com\/vim-airline\/vim-airline\/pull\/1898)\r\n    - several improvements to the branch, denite and tabline extension, as well as the async code for Vim and Neovim\r\n    - the term extension supports [neoterm](https:\/\/github.com\/kassio\/neoterm) vim plugin","package":"vim-airline-0.11.zip","4":"vim-airline-0.11.zip","src_id":"26817","5":"26817","creation_date":"1573422685","6":"1573422685"},{"0":"4661","vim_version":"7.2","1":"7.2","script_version":"0.10","2":"0.10","version_comment":"- New features\r\n  - Extensions:\r\n    - [LanguageClient](https:\/\/github.com\/autozimu\/LanguageClient-neovim)\r\n    - [vim-gutentags](https:\/\/github.com\/ludovicchabant\/vim-gutentags)\r\n    - [vim-localsearch](https:\/\/github.com\/mox-mox\/vim-localsearch)\r\n    - [xtabline](https:\/\/github.com\/mg979\/vim-xtabline)\r\n    - [vim-grepper](https:\/\/github.com\/mhinz\/vim-grepper)\r\n  - Add custom AirlineModeChanged autocommand, allowing to call user defined commands\r\n    whenever airline displays a different mode\r\n  - New :AirlineExtensions command, to show which extensions have been loaded\r\n  - Detect several new modes (e.g. completion, virtual replace, etc)\r\n- Improvements\r\n  - Various performance improvements, should Vim keep responsive, even when\r\n    many highlighting groups need to be re-created\r\n  - Rework tabline extension\r\n  - Refactor [vim-ctrlspace](https:\/\/github.com\/szw\/vim-ctrlspace) extension\r\n  - Refactor the wordcount extension\r\n  - Reworked the po extension\r\n  - Allow to disable line numbers for the [Ale Extension](https:\/\/github.com\/w0rp\/ale)\r\n  - [fugitive](https:\/\/github.com\/tpope\/vim-fugitive) plugin has been refactored\r\n    causing adjustments for vim-airline, also uses Fugitives new API calls\r\n  - some improvements to Vims terminal mode\r\n  - Allow to use alternative seperators for inactive windows (#1236)\r\n  - Statusline can be set to inactive, whenever Vim loses focus (using FocusLost autocommand)","3":"- New features\r\n  - Extensions:\r\n    - [LanguageClient](https:\/\/github.com\/autozimu\/LanguageClient-neovim)\r\n    - [vim-gutentags](https:\/\/github.com\/ludovicchabant\/vim-gutentags)\r\n    - [vim-localsearch](https:\/\/github.com\/mox-mox\/vim-localsearch)\r\n    - [xtabline](https:\/\/github.com\/mg979\/vim-xtabline)\r\n    - [vim-grepper](https:\/\/github.com\/mhinz\/vim-grepper)\r\n  - Add custom AirlineModeChanged autocommand, allowing to call user defined commands\r\n    whenever airline displays a different mode\r\n  - New :AirlineExtensions command, to show which extensions have been loaded\r\n  - Detect several new modes (e.g. completion, virtual replace, etc)\r\n- Improvements\r\n  - Various performance improvements, should Vim keep responsive, even when\r\n    many highlighting groups need to be re-created\r\n  - Rework tabline extension\r\n  - Refactor [vim-ctrlspace](https:\/\/github.com\/szw\/vim-ctrlspace) extension\r\n  - Refactor the wordcount extension\r\n  - Reworked the po extension\r\n  - Allow to disable line numbers for the [Ale Extension](https:\/\/github.com\/w0rp\/ale)\r\n  - [fugitive](https:\/\/github.com\/tpope\/vim-fugitive) plugin has been refactored\r\n    causing adjustments for vim-airline, also uses Fugitives new API calls\r\n  - some improvements to Vims terminal mode\r\n  - Allow to use alternative seperators for inactive windows (#1236)\r\n  - Statusline can be set to inactive, whenever Vim loses focus (using FocusLost autocommand)","package":"vim-airline-0.10.zip","4":"vim-airline-0.10.zip","src_id":"26301","5":"26301","creation_date":"1544934240","6":"1544934240"},{"0":"4661","vim_version":"7.2","1":"7.2","script_version":"0.9","2":"0.9","version_comment":"- Changes\r\n  - Look of default Airline Symbols has been improved [#1397](https:\/\/github.com\/vim-airline\/vim-airline\/issues\/1397)\r\n  - Airline does now set `laststatus=2` if needed\r\n  - Syntastic extension now displays warnings and errors separately\r\n  - Updates on Resize and SessionLoad events\r\n  - Add `maxlinenr` symbol to `airline_section_z`\r\n  - Add quickfix title to inactive windows\r\n- Improvements\r\n  - Many performance improvements (using caching and async feature when possible)\r\n  - Cache changes to highlighting groups if `g:airline_highlighting_cache = 1` is set\r\n  - Allow to skip empty sections by setting `g:airline_skip_empty_sections` variable\r\n  - Make use of improved Vim Script API, if available (e.g. getwininfo())\r\n  - Support for Vims terminal feature (very experimental since it hasn't been stabilized yet)\r\n  - More configuration for the tabline extension (with clickable buffers for Neovim)\r\n  - Works better on smaller window sizes\r\n  - Make airline aware of git worktrees\r\n  - Improvements to the fugitive extension [#1603](https:\/\/github.com\/vim-airline\/vim-airline\/issues\/1603)\r\n  - Allows for configurable fileformat output if `g:airline#parts#ffenc#skip_expected_string` is set\r\n  - Improvements to the documentation\r\n- New features\r\n  - Full async support for Vim 8 and Neovim\r\n  - Extensions:\r\n    - [vim-bufmru](https:\/\/github.com\/mildred\/vim-bufmru)\r\n    - [xkb-switch](https:\/\/github.com\/ierton\/xkb-switch)\r\n    - [input-source-switcher](https:\/\/github.com\/vovkasm\/input-source-switcher)\r\n    - [vimagit](https:\/\/github.com\/jreybert\/vimagit)\r\n    - [denite](https:\/\/github.com\/Shougo\/denite.nvim)\r\n    - [dein](https:\/\/github.com\/Shougo\/dein.vim)\r\n    - [vimtex](https:\/\/github.com\/lervag\/vimtex)\r\n    - [minpac](https:\/\/github.com\/k-takata\/minpac\/)\r\n    - [vim-cursormode](https:\/\/github.com\/vheon\/vim-cursormode)\r\n    - [Neomake](https:\/\/github.com\/neomake\/neomake)\r\n    - [Ale](https:\/\/github.com\/w0rp\/ale)\r\n    - [vim-obsession](https:\/\/github.com\/tpope\/vim-obsession)\r\n    - spell (can also display Spell language)\r\n    - keymap\r\n  - Formatters:\r\n    - Formatters for JavaScript [#1617](https:\/\/github.com\/vim-airline\/vim-airline\/issues\/1617)\r\n    - Tabline: Allow for custom formatter for `tab_nr_type` [#1418](https:\/\/github.com\/vim-airline\/vim-airline\/issues\/1418)\r\n    - Customizable wordcount formatter [#1584](https:\/\/github.com\/vim-airline\/vim-airline\/issues\/1584)\r\n  - Add User autocommand for Theme changing [#1226](https:\/\/github.com\/vim-airline\/vim-airline\/issues\/1226)\r\n  - Shows mercurial mq status if hg mq extension is enabled","3":"- Changes\r\n  - Look of default Airline Symbols has been improved [#1397](https:\/\/github.com\/vim-airline\/vim-airline\/issues\/1397)\r\n  - Airline does now set `laststatus=2` if needed\r\n  - Syntastic extension now displays warnings and errors separately\r\n  - Updates on Resize and SessionLoad events\r\n  - Add `maxlinenr` symbol to `airline_section_z`\r\n  - Add quickfix title to inactive windows\r\n- Improvements\r\n  - Many performance improvements (using caching and async feature when possible)\r\n  - Cache changes to highlighting groups if `g:airline_highlighting_cache = 1` is set\r\n  - Allow to skip empty sections by setting `g:airline_skip_empty_sections` variable\r\n  - Make use of improved Vim Script API, if available (e.g. getwininfo())\r\n  - Support for Vims terminal feature (very experimental since it hasn't been stabilized yet)\r\n  - More configuration for the tabline extension (with clickable buffers for Neovim)\r\n  - Works better on smaller window sizes\r\n  - Make airline aware of git worktrees\r\n  - Improvements to the fugitive extension [#1603](https:\/\/github.com\/vim-airline\/vim-airline\/issues\/1603)\r\n  - Allows for configurable fileformat output if `g:airline#parts#ffenc#skip_expected_string` is set\r\n  - Improvements to the documentation\r\n- New features\r\n  - Full async support for Vim 8 and Neovim\r\n  - Extensions:\r\n    - [vim-bufmru](https:\/\/github.com\/mildred\/vim-bufmru)\r\n    - [xkb-switch](https:\/\/github.com\/ierton\/xkb-switch)\r\n    - [input-source-switcher](https:\/\/github.com\/vovkasm\/input-source-switcher)\r\n    - [vimagit](https:\/\/github.com\/jreybert\/vimagit)\r\n    - [denite](https:\/\/github.com\/Shougo\/denite.nvim)\r\n    - [dein](https:\/\/github.com\/Shougo\/dein.vim)\r\n    - [vimtex](https:\/\/github.com\/lervag\/vimtex)\r\n    - [minpac](https:\/\/github.com\/k-takata\/minpac\/)\r\n    - [vim-cursormode](https:\/\/github.com\/vheon\/vim-cursormode)\r\n    - [Neomake](https:\/\/github.com\/neomake\/neomake)\r\n    - [Ale](https:\/\/github.com\/w0rp\/ale)\r\n    - [vim-obsession](https:\/\/github.com\/tpope\/vim-obsession)\r\n    - spell (can also display Spell language)\r\n    - keymap\r\n  - Formatters:\r\n    - Formatters for JavaScript [#1617](https:\/\/github.com\/vim-airline\/vim-airline\/issues\/1617)\r\n    - Tabline: Allow for custom formatter for `tab_nr_type` [#1418](https:\/\/github.com\/vim-airline\/vim-airline\/issues\/1418)\r\n    - Customizable wordcount formatter [#1584](https:\/\/github.com\/vim-airline\/vim-airline\/issues\/1584)\r\n  - Add User autocommand for Theme changing [#1226](https:\/\/github.com\/vim-airline\/vim-airline\/issues\/1226)\r\n  - Shows mercurial mq status if hg mq extension is enabled","package":"vim-airline-0.9.zip","4":"vim-airline-0.9.zip","src_id":"25767","5":"25767","creation_date":"1516040607","6":"1516040607"},{"0":"4661","vim_version":"7.2","1":"7.2","script_version":"0.8","2":"0.8","version_comment":"- Changes\r\n  - Airline converted to an organization and moved to new [repository](https:\/\/github.com\/vim-airline\/vim-airline)\r\n  - Themes have been split into an separate repository [vim-airline-themes](https:\/\/github.com\/vim-airline\/vim-airline-themes)\r\n- Improvements\r\n  - Extensions\r\n    - branch: support Git and Mercurial simultaneously, untracked files\r\n    - whitespace: new mixed-indent rule\r\n  - Windows support\r\n  - Many bug fixes\r\n  - Support for Neovim\r\n- New features\r\n  - Many new themes\r\n  - Extensions\/integration\r\n    - [taboo](https:\/\/github.com\/gcmt\/taboo.vim)\r\n    - [vim-ctrlspace](https:\/\/github.com\/szw\/vim-ctrlspace)\r\n    - [quickfixsigns](https:\/\/github.com\/tomtom\/quickfixsigns_vim)\r\n    - [YouCompleteMe](https:\/\/github.com\/Valloric\/YouCompleteMe)\r\n    - [po.vim](http:\/\/www.vim.org\/scripts\/script.php?script_id=695)\r\n    - [unicode.vim](https:\/\/github.com\/chrisbra\/unicode.vim)\r\n    - wordcount\r\n    - crypt indicator\r\n    - byte order mark indicator\r\n  - Tabline's tab mode can display splits simultaneously","3":"- Changes\r\n  - Airline converted to an organization and moved to new [repository](https:\/\/github.com\/vim-airline\/vim-airline)\r\n  - Themes have been split into an separate repository [vim-airline-themes](https:\/\/github.com\/vim-airline\/vim-airline-themes)\r\n- Improvements\r\n  - Extensions\r\n    - branch: support Git and Mercurial simultaneously, untracked files\r\n    - whitespace: new mixed-indent rule\r\n  - Windows support\r\n  - Many bug fixes\r\n  - Support for Neovim\r\n- New features\r\n  - Many new themes\r\n  - Extensions\/integration\r\n    - [taboo](https:\/\/github.com\/gcmt\/taboo.vim)\r\n    - [vim-ctrlspace](https:\/\/github.com\/szw\/vim-ctrlspace)\r\n    - [quickfixsigns](https:\/\/github.com\/tomtom\/quickfixsigns_vim)\r\n    - [YouCompleteMe](https:\/\/github.com\/Valloric\/YouCompleteMe)\r\n    - [po.vim](http:\/\/www.vim.org\/scripts\/script.php?script_id=695)\r\n    - [unicode.vim](https:\/\/github.com\/chrisbra\/unicode.vim)\r\n    - wordcount\r\n    - crypt indicator\r\n    - byte order mark indicator\r\n  - Tabline's tab mode can display splits simultaneously","package":"vim-airline-0.8.zip","4":"vim-airline-0.8.zip","src_id":"24086","5":"24086","creation_date":"1457619244","6":"1457619244"},{"0":"4661","vim_version":"7.2","1":"7.2","script_version":"0.7","2":"0.7","version_comment":"* New features\r\n  ** tabline\r\n    *** new highlight for unmodified inactive\r\n    *** can enable bindings for predictable number-based tab numbers\r\n    *** unique_tail and unique_tail_improved formatters\r\n  ** whitespace extension: can handle some common mixed indent rules\r\n  ** extensions: capslock, netrw, nrrwrgn, promptline, quickfix, tmuxline, windowswap\r\n  ** themes: durant, hybrid, kalisi, kolor, raven, silver\r\n* Improvements\r\n  ** countless refinements and bug fixes","3":"* New features\r\n  ** tabline\r\n    *** new highlight for unmodified inactive\r\n    *** can enable bindings for predictable number-based tab numbers\r\n    *** unique_tail and unique_tail_improved formatters\r\n  ** whitespace extension: can handle some common mixed indent rules\r\n  ** extensions: capslock, netrw, nrrwrgn, promptline, quickfix, tmuxline, windowswap\r\n  ** themes: durant, hybrid, kalisi, kolor, raven, silver\r\n* Improvements\r\n  ** countless refinements and bug fixes","package":"vim-airline-0.7.zip","4":"vim-airline-0.7.zip","src_id":"22726","5":"22726","creation_date":"1419348351","6":"1419348351"},{"0":"4661","vim_version":"7.2","1":"7.2","script_version":"0.6","2":"0.6","version_comment":"* New features\r\n * accents support; allowing multiple colors\/styles in the same section\r\n * extensions: eclim\r\n * themes: understated, monochrome, murmur, sol, lucius\r\n* Improvements\r\n * solarized theme; support for 8 color terminals\r\n * tabline resizes dynamically based on number of open buffers\r\n * miscellaneous bug fixes","3":"* New features\r\n * accents support; allowing multiple colors\/styles in the same section\r\n * extensions: eclim\r\n * themes: understated, monochrome, murmur, sol, lucius\r\n* Improvements\r\n * solarized theme; support for 8 color terminals\r\n * tabline resizes dynamically based on number of open buffers\r\n * miscellaneous bug fixes","package":"vim-airline-0.6.zip","4":"vim-airline-0.6.zip","src_id":"20904","5":"20904","creation_date":"1381428102","6":"1381428102"},{"0":"4661","vim_version":"7.2","1":"7.2","script_version":"0.5","2":"0.5","version_comment":"* New features\r\n  * smart tabline extension which displays all buffers when only one tab is visible\r\n  * automatic section truncation when the window resizes\r\n  * support for a declarative style of configuration, allowing parts to contain metadata such as minimum window width or conditional visibility\r\n  * themes: zenburn, serene\r\n* Other\r\n  * a sizable chunk of vim-airline is now running through a unit testing suite, automated via Travis CI","3":"* New features\r\n  * smart tabline extension which displays all buffers when only one tab is visible\r\n  * automatic section truncation when the window resizes\r\n  * support for a declarative style of configuration, allowing parts to contain metadata such as minimum window width or conditional visibility\r\n  * themes: zenburn, serene\r\n* Other\r\n  * a sizable chunk of vim-airline is now running through a unit testing suite, automated via Travis CI","package":"vim-airline-0.5.zip","4":"vim-airline-0.5.zip","src_id":"20779","5":"20779","creation_date":"1378845708","6":"1378845708"},{"0":"4661","vim_version":"7.2","1":"7.2","script_version":"0.4","2":"0.4","version_comment":"* New features\r\n  * integration with csv.vim and vim-virtualenv\r\n  * hunks extension for vim-gitgutter and vim-signify\r\n  * automatic theme switching with matching colorschemes\r\n  * commands: AirlineToggle\r\n  * themes: base16 (all variants)\r\n* Improvements\r\n  * integration with undotree, tagbar, and unite\r\n* Other\r\n  * refactored core and exposed statusline builder and pipeline\r\n  * all extension related g:airline_ variables have been deprecated in favor of g:airline#extensions# variables\r\n  * extensions found in the runtimepath outside of the default distribution will be automatically loaded","3":"* New features\r\n  * integration with csv.vim and vim-virtualenv\r\n  * hunks extension for vim-gitgutter and vim-signify\r\n  * automatic theme switching with matching colorschemes\r\n  * commands: AirlineToggle\r\n  * themes: base16 (all variants)\r\n* Improvements\r\n  * integration with undotree, tagbar, and unite\r\n* Other\r\n  * refactored core and exposed statusline builder and pipeline\r\n  * all extension related g:airline_ variables have been deprecated in favor of g:airline#extensions# variables\r\n  * extensions found in the runtimepath outside of the default distribution will be automatically loaded","package":"vim-airline-0.4.zip","4":"vim-airline-0.4.zip","src_id":"20719","5":"20719","creation_date":"1377536703","6":"1377536703"},{"0":"4661","vim_version":"7.2","1":"7.2","script_version":"0.3","2":"0.3","version_comment":"* New features\r\n  * first-class integration with tagbar\r\n  * white space detection for trailing spaces and mixed indentation\r\n  * introduced warning section for syntastic and white space detection\r\n  * improved ctrlp integration: colors are automatically selected based on the current airline theme\r\n  * new themes: molokai, bubblegum, jellybeans, tomorrow\r\n* Bug fixes\r\n  * improved handling of eventignore used by other plugins\r\n* Other\r\n  * code cleaned up for clearer separation between core functionality and extensions\r\n  * introduced color extraction from highlight groups, allowing themes to be generated off of the active colorscheme (e.g. jellybeans and tomorrow)\r\n  * License changed to MIT","3":"* New features\r\n  * first-class integration with tagbar\r\n  * white space detection for trailing spaces and mixed indentation\r\n  * introduced warning section for syntastic and white space detection\r\n  * improved ctrlp integration: colors are automatically selected based on the current airline theme\r\n  * new themes: molokai, bubblegum, jellybeans, tomorrow\r\n* Bug fixes\r\n  * improved handling of eventignore used by other plugins\r\n* Other\r\n  * code cleaned up for clearer separation between core functionality and extensions\r\n  * introduced color extraction from highlight groups, allowing themes to be generated off of the active colorscheme (e.g. jellybeans and tomorrow)\r\n  * License changed to MIT","package":"vim-airline-0.3.zip","4":"vim-airline-0.3.zip","src_id":"20635","5":"20635","creation_date":"1376345307","6":"1376345307"},{"0":"4661","vim_version":"7.2","1":"7.2","script_version":"0.2","2":"0.2","version_comment":"* New features\r\n  * iminsert detection\r\n  * integration with vimshell, vimfiler, commandt, lawrencium\r\n  * enhanced bufferline theming\r\n  * support for ctrlp theming\r\n  * support for custom window excludes\r\n* New themes\r\n  * luna and wombat\r\n* Bug fixes\r\n  * refresh branch name after switching with a shell command","3":"* New features\r\n  * iminsert detection\r\n  * integration with vimshell, vimfiler, commandt, lawrencium\r\n  * enhanced bufferline theming\r\n  * support for ctrlp theming\r\n  * support for custom window excludes\r\n* New themes\r\n  * luna and wombat\r\n* Bug fixes\r\n  * refresh branch name after switching with a shell command","package":"vim-airline-0.2.zip","4":"vim-airline-0.2.zip","src_id":"20570","5":"20570","creation_date":"1374964824","6":"1374964824"},{"0":"4661","vim_version":"7.2","1":"7.2","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"vim-airline-0.1.zip","4":"vim-airline-0.1.zip","src_id":"20535","5":"20535","creation_date":"1374020076","6":"1374020076"}]},"4660":{"script_id":"4660","0":"4660","script_name":"plum.vim","1":"plum.vim","script_type":"color scheme","2":"color scheme","summary":"Light and dark colorscheme","3":"Light and dark colorscheme","description":"\r\nLight and dark colorscheme with ambient light detection (OS X)\r\n","4":"\r\nLight and dark colorscheme with ambient light detection (OS X)\r\n","install_details":"\r\nInstall with your favorite plugin manager.\r\n\r\nIf you're running OS X and want to use ambient light detection you need to move to the\r\nplugin root directory and run\r\n\r\n    $ .\/install.sh\r\n","5":"\r\nInstall with your favorite plugin manager.\r\n\r\nIf you're running OS X and want to use ambient light detection you need to move to the\r\nplugin root directory and run\r\n\r\n    $ .\/install.sh\r\n","first_name":"geck","6":"geck","last_name":" ","7":" ","releases":[{"0":"4660","vim_version":"7.0","1":"7.0","script_version":"0.3","2":"0.3","version_comment":"Various fixes","3":"Various fixes","package":"plum-0.3.zip","4":"plum-0.3.zip","src_id":"21245","5":"21245","creation_date":"1388163860","6":"1388163860"}]},"4659":{"script_id":"4659","0":"4659","script_name":"buildmenu","1":"buildmenu","script_type":"utility","2":"utility","summary":"Plugin for managing a list of build targets (so far only with Waf)","3":"Plugin for managing a list of build targets (so far only with Waf)","description":"Grab the latest dev version from github: https:\/\/github.com\/andsten\/buildmenu.\r\n\r\nIf you use the build-tool Waf (http:\/\/code.google.com\/p\/waf), this plugin will\r\nassist you by providing a comfortable sidebar menu which lists major Waf\r\ncommands and all existing build-targets of your current project. You can\r\nselect one or more targets from the list for building.\r\n\r\nSee https:\/\/github.com\/andsten\/buildmenu\/wiki for a screenshot.\r\n\r\n\r\nMappings in the sidebar menu:\r\n\r\n<Space>\r\nselect or unselect a build-target from the list. the target\r\nis highlighted in a different color to visualize your choice\r\n\r\n<Return>\r\nstart building your selected build-target(s) with Waf. The\r\nresulting build command would usually look like this:\r\n   .\/waf --targets=common,unittest1,unitest2\r\n\r\n'R'\r\nrefresh build target list (plugin will run cmd \"waf list\" again)\r\n\r\nYou need to set a key-mapping in your .vimrc file to open\/close the sidebar\r\nmenu (install this plugin and see its help file for details).\r\n\r\n\r\nThis script is still quite young and far from being feature complete.\r\nPlanned features for future versions:\r\n\r\n * test seriously on windows platform (so far only tested on linux)\r\n * user can add own args to the waf command-line for building\r\n * quick-help in the style of NERDTree (when pressing '?')\r\n * support of other build systems like SCons and GNU Make (if feasible)\r\n * multiselect targets via visual mode\r\n * press 'U' to unselect all\r\n","4":"Grab the latest dev version from github: https:\/\/github.com\/andsten\/buildmenu.\r\n\r\nIf you use the build-tool Waf (http:\/\/code.google.com\/p\/waf), this plugin will\r\nassist you by providing a comfortable sidebar menu which lists major Waf\r\ncommands and all existing build-targets of your current project. You can\r\nselect one or more targets from the list for building.\r\n\r\nSee https:\/\/github.com\/andsten\/buildmenu\/wiki for a screenshot.\r\n\r\n\r\nMappings in the sidebar menu:\r\n\r\n<Space>\r\nselect or unselect a build-target from the list. the target\r\nis highlighted in a different color to visualize your choice\r\n\r\n<Return>\r\nstart building your selected build-target(s) with Waf. The\r\nresulting build command would usually look like this:\r\n   .\/waf --targets=common,unittest1,unitest2\r\n\r\n'R'\r\nrefresh build target list (plugin will run cmd \"waf list\" again)\r\n\r\nYou need to set a key-mapping in your .vimrc file to open\/close the sidebar\r\nmenu (install this plugin and see its help file for details).\r\n\r\n\r\nThis script is still quite young and far from being feature complete.\r\nPlanned features for future versions:\r\n\r\n * test seriously on windows platform (so far only tested on linux)\r\n * user can add own args to the waf command-line for building\r\n * quick-help in the style of NERDTree (when pressing '?')\r\n * support of other build systems like SCons and GNU Make (if feasible)\r\n * multiselect targets via visual mode\r\n * press 'U' to unselect all\r\n","install_details":"* unzip the archive into your ~\/.vim directory. That should put buildmenu.vim\r\n  in ~\/.vim\/plugin and buildmenu.txt in ~\/.vim\/doc.\r\n* start vim and run \":helptags ~\/.vim\/doc\"\r\n* enter \":help buildmenu\" to view the help page of this plugin\r\n","5":"* unzip the archive into your ~\/.vim directory. That should put buildmenu.vim\r\n  in ~\/.vim\/plugin and buildmenu.txt in ~\/.vim\/doc.\r\n* start vim and run \":helptags ~\/.vim\/doc\"\r\n* enter \":help buildmenu\" to view the help page of this plugin\r\n","first_name":"Andrej","6":"Andrej","last_name":"Stender","7":"Stender","releases":[{"0":"4659","vim_version":"7.3","1":"7.3","script_version":"0.2","2":"0.2","version_comment":"- menu offers major Waf commands (\u00e2\u0080\u0093help, clean, distclean, configure, build, \u00e2\u0080\u00a6)\r\n- status-line shows Waf version\r\n- lot of bugfixes, code refactoring\r\n","3":"- menu offers major Waf commands (\u00e2\u0080\u0093help, clean, distclean, configure, build, \u00e2\u0080\u00a6)\r\n- status-line shows Waf version\r\n- lot of bugfixes, code refactoring\r\n","package":"buildmenu.zip","4":"buildmenu.zip","src_id":"20624","5":"20624","creation_date":"1376153637","6":"1376153637"},{"0":"4659","vim_version":"7.3","1":"7.3","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"buildmenu.zip","4":"buildmenu.zip","src_id":"20522","5":"20522","creation_date":"1373842086","6":"1373842086"}]},"4658":{"script_id":"4658","0":"4658","script_name":"BidiComplete","1":"BidiComplete","script_type":"utility","2":"utility","summary":"Insert mode completion that considers text before AND AFTER the cursor.","3":"Insert mode completion that considers text before AND AFTER the cursor.","description":"DESCRIPTION\r\nThe built-in insert mode completion i_CTRL-N searches for words that start\r\nwith the keyword in front of the cursor. Any text after the cursor is ignored.\r\nSo when you want to replace \"MyFunnyVariable\" with \"MySpecialVariable\", you\r\nhave to delete everything after \"My\", then start completion, which now also\r\noffers \"MySpecialFunction\", \"MySpecialWhatever\", in which you're not\r\ninterested in. If you only removed the \"Funny\" part, the list of\r\n(inapplicable) completions would be the same, and you would finally end up\r\nwith \"MySpecialVariableVariable\", requiring additional edits.\r\n\r\nThis plugin offers a custom completion mapping that considers the text after\r\nthe cursor; if there is no keyword immediately after the cursor, it behaves\r\nlike the built-in completion. It even works when there is only text after, but\r\nnot before the cursor, so completion on \"|Variable\" yields\r\n\"MySpecialVariable\", \"MyFunnyVariable\", etc. The base for completion is\r\nderived from the string of keyword characters before and after the cursor, so\r\nset your 'iskeyword' option accordingly.\r\n\r\nSOURCE\r\nOriginal idea by Laszlo Kozma in his paper \"Reverse autocomplete\"\r\n    http:\/\/www.lkozma.net\/autocomplete.html\r\n\r\nSEE ALSO\r\n- Check out the CompleteHelper.vim plugin page (vimscript #3914) for a full\r\n  list of insert mode completions powered by it.\r\n\r\nUSAGE\r\nIn insert mode, invoke the bidirectional completion via CTRL-X CTRL-B.\r\nYou can then search forward and backward via CTRL-N \/ CTRL-P, as usual.\r\n\r\nCTRL-X CTRL-B           Find matches for words that start with the (optional)\r\n                        keyword in front of the cursor and end with the\r\n                        (mandatory) keyword (or non-keyword non-whitespace,\r\n                        either optionally separated by whitespace) after the\r\n                        cursor.\r\n\r\nEXAMPLE\r\n(the \"|\" denotes the cursor)\r\n\r\nThe B|Complete\r\n    will complete to \"BidiComplete\"\r\nThe |Complete\r\n    will offer all words ending with \"Complete\"\r\nThe d|.\r\n    will complete to \"dog\" if that word ends somewhere with a period (the\r\n    completion base after the cursor is mandatory, and non-keyword characters\r\n    are taken, too)\r\nMy | lady\r\n    will complete to \"fair\" from \"fair lady\". There's no leading base, as\r\n    whitespace before the cursor is ignored, but for the mandatory trailing\r\n    base, \" lady\" is taken.","4":"DESCRIPTION\r\nThe built-in insert mode completion i_CTRL-N searches for words that start\r\nwith the keyword in front of the cursor. Any text after the cursor is ignored.\r\nSo when you want to replace \"MyFunnyVariable\" with \"MySpecialVariable\", you\r\nhave to delete everything after \"My\", then start completion, which now also\r\noffers \"MySpecialFunction\", \"MySpecialWhatever\", in which you're not\r\ninterested in. If you only removed the \"Funny\" part, the list of\r\n(inapplicable) completions would be the same, and you would finally end up\r\nwith \"MySpecialVariableVariable\", requiring additional edits.\r\n\r\nThis plugin offers a custom completion mapping that considers the text after\r\nthe cursor; if there is no keyword immediately after the cursor, it behaves\r\nlike the built-in completion. It even works when there is only text after, but\r\nnot before the cursor, so completion on \"|Variable\" yields\r\n\"MySpecialVariable\", \"MyFunnyVariable\", etc. The base for completion is\r\nderived from the string of keyword characters before and after the cursor, so\r\nset your 'iskeyword' option accordingly.\r\n\r\nSOURCE\r\nOriginal idea by Laszlo Kozma in his paper \"Reverse autocomplete\"\r\n    http:\/\/www.lkozma.net\/autocomplete.html\r\n\r\nSEE ALSO\r\n- Check out the CompleteHelper.vim plugin page (vimscript #3914) for a full\r\n  list of insert mode completions powered by it.\r\n\r\nUSAGE\r\nIn insert mode, invoke the bidirectional completion via CTRL-X CTRL-B.\r\nYou can then search forward and backward via CTRL-N \/ CTRL-P, as usual.\r\n\r\nCTRL-X CTRL-B           Find matches for words that start with the (optional)\r\n                        keyword in front of the cursor and end with the\r\n                        (mandatory) keyword (or non-keyword non-whitespace,\r\n                        either optionally separated by whitespace) after the\r\n                        cursor.\r\n\r\nEXAMPLE\r\n(the \"|\" denotes the cursor)\r\n\r\nThe B|Complete\r\n    will complete to \"BidiComplete\"\r\nThe |Complete\r\n    will offer all words ending with \"Complete\"\r\nThe d|.\r\n    will complete to \"dog\" if that word ends somewhere with a period (the\r\n    completion base after the cursor is mandatory, and non-keyword characters\r\n    are taken, too)\r\nMy | lady\r\n    will complete to \"fair\" from \"fair lady\". There's no leading base, as\r\n    whitespace before the cursor is ignored, but for the mandatory trailing\r\n    base, \" lady\" is taken.","install_details":"INSTALLATION\r\nThis script is packaged as a vimball. If you have the \"gunzip\" decompressor\r\nin your PATH, simply edit the *.vmb.gz package in Vim; otherwise, decompress\r\nthe archive first, e.g. using WinZip. Inside Vim, install by sourcing the\r\nvimball or via the :UseVimball command.\r\n    vim BidiComplete*.vmb.gz\r\n    :so %\r\nTo uninstall, use the :RmVimball command.\r\n\r\nDEPENDENCIES\r\n- Requires Vim 7.0 or higher.\r\n- Requires the CompleteHelper.vim plugin (vimscript #3914).\r\n- Requires the ingo-library.vim plugin (vimscript #4433), version 1.010 or\r\n  higher.\r\n\r\nCONFIGURATION\r\nFor a permanent configuration, put the following commands into your vimrc:\r\n\r\nAnaloguous to the 'complete' option, you can specify which buffers will be\r\nscanned for completion candidates. Currently, '.' (current buffer), 'w'\r\n(buffers from other windows), and 'b' (other listed buffers) are supported.\r\n    let g:BidiComplete_complete = '.,w,b'\r\nThe global setting can be overridden for a particular buffer\r\n(b:BidiComplete_complete).\r\n\r\nIf you want to use a different mapping, map your keys to the\r\n<Plug>(BidiComplete) mapping target _before_ sourcing the script (e.g.\r\nin your vimrc):\r\n    imap <C-x><C-b> <Plug>(BidiComplete)","5":"INSTALLATION\r\nThis script is packaged as a vimball. If you have the \"gunzip\" decompressor\r\nin your PATH, simply edit the *.vmb.gz package in Vim; otherwise, decompress\r\nthe archive first, e.g. using WinZip. Inside Vim, install by sourcing the\r\nvimball or via the :UseVimball command.\r\n    vim BidiComplete*.vmb.gz\r\n    :so %\r\nTo uninstall, use the :RmVimball command.\r\n\r\nDEPENDENCIES\r\n- Requires Vim 7.0 or higher.\r\n- Requires the CompleteHelper.vim plugin (vimscript #3914).\r\n- Requires the ingo-library.vim plugin (vimscript #4433), version 1.010 or\r\n  higher.\r\n\r\nCONFIGURATION\r\nFor a permanent configuration, put the following commands into your vimrc:\r\n\r\nAnaloguous to the 'complete' option, you can specify which buffers will be\r\nscanned for completion candidates. Currently, '.' (current buffer), 'w'\r\n(buffers from other windows), and 'b' (other listed buffers) are supported.\r\n    let g:BidiComplete_complete = '.,w,b'\r\nThe global setting can be overridden for a particular buffer\r\n(b:BidiComplete_complete).\r\n\r\nIf you want to use a different mapping, map your keys to the\r\n<Plug>(BidiComplete) mapping target _before_ sourcing the script (e.g.\r\nin your vimrc):\r\n    imap <C-x><C-b> <Plug>(BidiComplete)","first_name":"Ingo","6":"Ingo","last_name":"Karkat","7":"Karkat","releases":[{"0":"4658","vim_version":"7.0","1":"7.0","script_version":"1.01","2":"1.01","version_comment":"Tweak base algorithm: Enforce base after cursor (without it, the completion would be just like the default one), also take non-keyword non-whitespace characters there, optionally separated by whitespace. This makes the completion useful in more places.","3":"Tweak base algorithm: Enforce base after cursor (without it, the completion would be just like the default one), also take non-keyword non-whitespace characters there, optionally separated by whitespace. This makes the completion useful in more places.","package":"BidiComplete-1.01.vmb.gz","4":"BidiComplete-1.01.vmb.gz","src_id":"20526","5":"20526","creation_date":"1373891158","6":"1373891158"},{"0":"4658","vim_version":"7.0","1":"7.0","script_version":"1.00","2":"1.00","version_comment":"Initial upload","3":"Initial upload","package":"BidiComplete-1.00.vmb.gz","4":"BidiComplete-1.00.vmb.gz","src_id":"20516","5":"20516","creation_date":"1373817365","6":"1373817365"}]},"4657":{"script_id":"4657","0":"4657","script_name":"wabisabi","1":"wabisabi","script_type":"color scheme","2":"color scheme","summary":"wabisabi.vim is a colorscheme of Gvim","3":"wabisabi.vim is a colorscheme of Gvim","description":"This plugin is a colorscheme of gvim.\r\n\r\nLatest version: \r\nhttps:\/\/github.com\/boolfool\/wabisabi.vim","4":"This plugin is a colorscheme of gvim.\r\n\r\nLatest version: \r\nhttps:\/\/github.com\/boolfool\/wabisabi.vim","install_details":"","5":"","first_name":"bool","6":"bool","last_name":"fool","7":"fool","releases":[{"0":"4657","vim_version":"7.3","1":"7.3","script_version":"0.0.0","2":"0.0.0","version_comment":"Initial upload","3":"Initial upload","package":"wabisabi.vim.zip","4":"wabisabi.vim.zip","src_id":"20511","5":"20511","creation_date":"1373779636","6":"1373779636"}]},"4656":{"script_id":"4656","0":"4656","script_name":"vim-addon-errorformats","1":"vim-addon-errorformats","script_type":"utility","2":"utility","summary":"error formats for Vim","3":"error formats for Vim","description":"Advanced features such as \\\\\\\"run in background\\\\\\\" require errorformats, too. Vim only has :compiler, which also sets makeprg etc, which is not what you want in some cases.\r\n\r\nThis plugin provides errorformats only for various compilers etc.\r\n\r\nBest is that you can combine multiple errorformats, such as ruby (rumake build system) & target language (ocaml)","4":"Advanced features such as \\\\\\\"run in background\\\\\\\" require errorformats, too. Vim only has :compiler, which also sets makeprg etc, which is not what you want in some cases.\r\n\r\nThis plugin provides errorformats only for various compilers etc.\r\n\r\nBest is that you can combine multiple errorformats, such as ruby (rumake build system) & target language (ocaml)","install_details":"Get from github, use VAM. If you have trouble contact me (eg on irc or per mail)","5":"Get from github, use VAM. If you have trouble contact me (eg on irc or per mail)","first_name":"Marc","6":"Marc","last_name":"Weber","7":"Weber","releases":[{"0":"4656","vim_version":"7.0","1":"7.0","script_version":"0.0","2":"0.0","version_comment":"Initial upload","3":"Initial upload","package":"dummy.txt","4":"dummy.txt","src_id":"20508","5":"20508","creation_date":"1373644946","6":"1373644946"}]},"4655":{"script_id":"4655","0":"4655","script_name":"hsftp","1":"hsftp","script_type":"utility","2":"utility","summary":"Upload and download files through sftp","3":"Upload and download files through sftp","description":"Check https:\/\/github.com\/hesselbom\/vim-hsftp for instructions","4":"Check https:\/\/github.com\/hesselbom\/vim-hsftp for instructions","install_details":"","5":"","first_name":"Viktor","6":"Viktor","last_name":"Hesselbom","7":"Hesselbom","releases":[{"0":"4655","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"hsftp.vim","4":"hsftp.vim","src_id":"20506","5":"20506","creation_date":"1373526497","6":"1373526497"}]},"4654":{"script_id":"4654","0":"4654","script_name":"AutoAdapt","1":"AutoAdapt","script_type":"utility","2":"utility","summary":"Automatically adapt timestamps, copyright notices, etc.","3":"Automatically adapt timestamps, copyright notices, etc.","description":"DESCRIPTION\r\nThis plugin automatically adapts information like \"last modified\" timestamps\r\nand copyright notices, or applies any other substitution before each file\r\nsave. Where and what is replaced can be configured globally and for each\r\nindividual buffer.\r\n\r\nThe plugin ships with configuration defaults which handle the most common\r\ncopyright notices, e.g.:\r\n    Copyright: (C) 2011-2019 Ingo Karkat\r\nand modification timestamps such as\r\n    Last Change: Sat 23 Mar 2019 21:39:31 C\r\n    Modified: 2019 Mar 23\r\n\r\nSOURCE\r\n- The regular expression for updating copyright notices is derived from\r\n    http:\/\/vim.wikia.com\/wiki\/Automatically_Update_Copyright_Notice_in_Files\r\n\r\nRELATED WORKS\r\n- autodate.vim (vimscript #291) is an old plugin that can insert and update a\r\n  time stamp (between a prefix and postfix) in a certain format.\r\n- ferallastchange.vim (vimscript #680) is an old plugin that searches for a\r\n  prefix and then updates the timestamp in a certain format.\r\n- timstamp.vim (vimscript #371) takes pattern and replacement parts like this\r\n  plugin (the replacement part also supports some custom tokens e.g. for\r\n  hostname), and is functionally very close.\r\n- timestamp.vim (vimscript #923) is based on timstamp.vim. It allows only one\r\n  pattern and feeds the replacement part to strftime(), making it less\r\n  general.\r\n- header.vim (vimscript #1142) insert or updates a header at the top, in a\r\n  rather primitive way, and limited to shell, Python, Perl, and Vim scripts.\r\n- lastmod.vim (vimscript #3578) is a short and simple plugin for replacing one\r\n  pattern with a timestamp in the first N lines.\r\n- better-header.vim (vimscript #4676) can insert and update a header for\r\n  Python and shell scripts, and requires Python itself.\r\n- update-time (vimscript #4786) searches the first and last lines for a single\r\n  prefix and then automatically updates a following timestamp.\r\n\r\nUSAGE\r\nThe adaptation happens before every buffer save (BufWritePre event), e.g.\r\nwith the :write command. No action required. You can configure\r\n(g:AutoAdapt_Rules) and disable this, though:\r\n\r\n:NoAutoAdapt            Turn off automatic adapting for the current buffer.\r\n\r\n:AutoAdapt[!]           Turn on automatic adapting for the current buffer,\r\n                        after having it turned off via|:NoAutoAdapt|, or to\r\n                        enable adapting for a buffer when the automatic\r\n                        adapting has been configured to exclude the current\r\n                        buffer via g:AutoAdapt_FilePattern, or (with [!]) to\r\n                        override a configured Predicate which disables\r\n                        adaptation for the buffer.\r\n\r\n:Adapt[!]               Trigger manual adaptation of the current buffer (when\r\n                        automatic adaption has been turned off via\r\n                        :NoAutoAdapt). With [!] also overrides a configured\r\n                        Predicate which disables adaptation for the buffer.","4":"DESCRIPTION\r\nThis plugin automatically adapts information like \"last modified\" timestamps\r\nand copyright notices, or applies any other substitution before each file\r\nsave. Where and what is replaced can be configured globally and for each\r\nindividual buffer.\r\n\r\nThe plugin ships with configuration defaults which handle the most common\r\ncopyright notices, e.g.:\r\n    Copyright: (C) 2011-2019 Ingo Karkat\r\nand modification timestamps such as\r\n    Last Change: Sat 23 Mar 2019 21:39:31 C\r\n    Modified: 2019 Mar 23\r\n\r\nSOURCE\r\n- The regular expression for updating copyright notices is derived from\r\n    http:\/\/vim.wikia.com\/wiki\/Automatically_Update_Copyright_Notice_in_Files\r\n\r\nRELATED WORKS\r\n- autodate.vim (vimscript #291) is an old plugin that can insert and update a\r\n  time stamp (between a prefix and postfix) in a certain format.\r\n- ferallastchange.vim (vimscript #680) is an old plugin that searches for a\r\n  prefix and then updates the timestamp in a certain format.\r\n- timstamp.vim (vimscript #371) takes pattern and replacement parts like this\r\n  plugin (the replacement part also supports some custom tokens e.g. for\r\n  hostname), and is functionally very close.\r\n- timestamp.vim (vimscript #923) is based on timstamp.vim. It allows only one\r\n  pattern and feeds the replacement part to strftime(), making it less\r\n  general.\r\n- header.vim (vimscript #1142) insert or updates a header at the top, in a\r\n  rather primitive way, and limited to shell, Python, Perl, and Vim scripts.\r\n- lastmod.vim (vimscript #3578) is a short and simple plugin for replacing one\r\n  pattern with a timestamp in the first N lines.\r\n- better-header.vim (vimscript #4676) can insert and update a header for\r\n  Python and shell scripts, and requires Python itself.\r\n- update-time (vimscript #4786) searches the first and last lines for a single\r\n  prefix and then automatically updates a following timestamp.\r\n\r\nUSAGE\r\nThe adaptation happens before every buffer save (BufWritePre event), e.g.\r\nwith the :write command. No action required. You can configure\r\n(g:AutoAdapt_Rules) and disable this, though:\r\n\r\n:NoAutoAdapt            Turn off automatic adapting for the current buffer.\r\n\r\n:AutoAdapt[!]           Turn on automatic adapting for the current buffer,\r\n                        after having it turned off via|:NoAutoAdapt|, or to\r\n                        enable adapting for a buffer when the automatic\r\n                        adapting has been configured to exclude the current\r\n                        buffer via g:AutoAdapt_FilePattern, or (with [!]) to\r\n                        override a configured Predicate which disables\r\n                        adaptation for the buffer.\r\n\r\n:Adapt[!]               Trigger manual adaptation of the current buffer (when\r\n                        automatic adaption has been turned off via\r\n                        :NoAutoAdapt). With [!] also overrides a configured\r\n                        Predicate which disables adaptation for the buffer.","install_details":"INSTALLATION\r\nThe code is hosted in a Git repo at\r\n    https:\/\/github.com\/inkarkat\/vim-AutoAdapt\r\nYou can use your favorite plugin manager, or \"git clone\" into a directory used\r\nfor Vim packages. Releases are on the \"stable\" branch, the latest unstable\r\ndevelopment snapshot on \"master\".\r\n\r\nThis script is also packaged as a vimball. If you have the \"gunzip\"\r\ndecompressor in your PATH, simply edit the *.vmb.gz package in Vim; otherwise,\r\ndecompress the archive first, e.g. using WinZip. Inside Vim, install by\r\nsourcing the vimball or via the :UseVimball command.\r\n    vim AutoAdapt*.vmb.gz\r\n    :so %\r\nTo uninstall, use the :RmVimball command.\r\n\r\nDEPENDENCIES\r\n- Requires Vim 7.0 or higher.\r\n- Requires the ingo-library.vim plugin (vimscript #4433), version 1.025 or\r\n  higher.\r\n\r\nCONFIGURATION\r\nFor a permanent configuration, put the following commands into your vimrc:\r\n\r\nIf you want to apply the adaptation only to certain files, you can specify\r\nautocmd-patterns instead of the default \"*\". This must be set before the\r\nplugin is sourced:\r\n    let g:AutoAdapt_FilePattern = '*.h,*.c,*.cpp'\r\nAlternatively, if you want to opt-in for certain files only instead of opting\r\nout via :NoAutoAdapt, completely disable the automatic adaptation through\r\n    let g:AutoAdapt_FilePattern = ''\r\nand use :AutoAdapt, e.g. in combination with a local vimrc plugin.\r\n\r\nThe number of lines at the start of the buffer when the rules are applied by\r\ndefault:\r\n    let g:AutoAdapt_FirstLines = 25\r\n\r\nThe number of lines at the end of the buffer when the rules are applied by\r\ndefault:\r\n    let g:AutoAdapt_LastLines = 10\r\nThe reasoning for a larger \"first lines\" value is that there may be more\r\nboilerplate code at the file's header. (Also for this reason, the 'modelines'\r\nvalue is not used by default.)\r\nYou can override both values for particular buffers \/ filetypes with the\r\nbuffer-scoped variable.\r\n\r\nThe plugin uses a list of rules to adapt the buffer contents on each save. You\r\ncan add your own rules, or completely replace the default rules. Rules can\r\nalso be overridden for individual buffers with a buffer-local variable. The\r\nrules consist of a List of Rule objects:\r\n    let g:AutoAdapt_Rules = [\r\n    \\   {\r\n    \\       'name': 'Copyright notice',\r\n    \\       'pattern': '\\c\\<Copyright:\\?\\d\\{4}\\>',\r\n    \\       'replacement': strftime('%Y'),\r\n    \\       'range': 'modelines'\r\n    \\   },\r\n    \\   { ... }\r\n    \\]\r\n\r\nname                    An optional, human-readable description of the rule.\r\npattern                 The regular-expression as used in a :substitute\r\n                        command (with the separator character \/, or\r\n                        substitutionSeparator).\r\npatternexpr             A Funcref (that takes the entire current rule object)\r\n                        or a String that is |eval()|ed to yield the pattern.\r\n                        Updates the pattern attribute on each run. You can use\r\n                        this to e.g. get the current date (via strftime(),\r\n                        to avoid a match of the current date with \/@!) into\r\n                        the pattern. The Funcref can throw \"AutoAdaptSkip\" to\r\n                        skip the application of this rule.\r\nreplacement             The replacement; you can use text or\r\n                        sub-replace-special.\r\nrange                   The (optional) range to which parts of the buffer the\r\n                        rule will be applied. It defaults to the empty string\r\n                        \"\", which uses the g:AutoAdapt_FirstLines and\r\n                        g:AutoAdapt_LastLines variables. Alternatives are:\r\n                        \"modelines\", which considers the 'modelines' number of\r\n                        lines at both the start and end of the buffer.\r\n                        You can also use \"%\" for the entire buffer, or use\r\n                        numbered ranges \"11,42\".\r\nsubstitutionSeparator   The separator in the :substitute. Change from the\r\n                        default \"\/\" to another non-alphanumeric single-byte\r\n                        character when the default is cumbersome. E146\r\n\r\nTo skip the automatic adaptation for certain files, in addition to\r\ng:AutoAdapt_FilePattern and :NoAutoAdapt, you can also configure a Funcref\r\n(if that is more convenient) that is passed the current file's filespec, and\r\nshould return a Boolean value whether it should be adapted. For example, if\r\nyou have the writebackupVersionControl.vim plugin (vimscript #1829)\r\ninstalled, you can skip adapting backups via:\r\n    let g:AutoAdapt_Predicate = function('writebackupVersionControl#IsOriginalFile')\r\n\r\nINTEGRATION\r\nAfter each write, the plugin sets the variable b:AutoAdapt to the number of\r\nrules that have been applied. If no rule was applied, the variable is removed.\r\nThe :NoAutoAdapt sets the variable to 0 to indicate that the plugin is\r\ndisabled for that buffer.\r\n\r\nIf you want to indicate (e.g. in your 'statusline') whether automatic adapting\r\ntook place or whether you've manually overridden the automation, you can use\r\nthe AutoAdapt#Info#Status() function, which returns:\r\n    \"adapted\"   when adaptation took place\r\n    \"noadapt\"   when automatic adaptation is enabled, but was turned off via\r\n                :NoAutoAdapt for this buffer\r\n    \"adapt\"     when automatic adaptation is disabled, but was turned on via\r\n                :AutoAdapt for this buffer\r\n    \"\"          in all other situations","5":"INSTALLATION\r\nThe code is hosted in a Git repo at\r\n    https:\/\/github.com\/inkarkat\/vim-AutoAdapt\r\nYou can use your favorite plugin manager, or \"git clone\" into a directory used\r\nfor Vim packages. Releases are on the \"stable\" branch, the latest unstable\r\ndevelopment snapshot on \"master\".\r\n\r\nThis script is also packaged as a vimball. If you have the \"gunzip\"\r\ndecompressor in your PATH, simply edit the *.vmb.gz package in Vim; otherwise,\r\ndecompress the archive first, e.g. using WinZip. Inside Vim, install by\r\nsourcing the vimball or via the :UseVimball command.\r\n    vim AutoAdapt*.vmb.gz\r\n    :so %\r\nTo uninstall, use the :RmVimball command.\r\n\r\nDEPENDENCIES\r\n- Requires Vim 7.0 or higher.\r\n- Requires the ingo-library.vim plugin (vimscript #4433), version 1.025 or\r\n  higher.\r\n\r\nCONFIGURATION\r\nFor a permanent configuration, put the following commands into your vimrc:\r\n\r\nIf you want to apply the adaptation only to certain files, you can specify\r\nautocmd-patterns instead of the default \"*\". This must be set before the\r\nplugin is sourced:\r\n    let g:AutoAdapt_FilePattern = '*.h,*.c,*.cpp'\r\nAlternatively, if you want to opt-in for certain files only instead of opting\r\nout via :NoAutoAdapt, completely disable the automatic adaptation through\r\n    let g:AutoAdapt_FilePattern = ''\r\nand use :AutoAdapt, e.g. in combination with a local vimrc plugin.\r\n\r\nThe number of lines at the start of the buffer when the rules are applied by\r\ndefault:\r\n    let g:AutoAdapt_FirstLines = 25\r\n\r\nThe number of lines at the end of the buffer when the rules are applied by\r\ndefault:\r\n    let g:AutoAdapt_LastLines = 10\r\nThe reasoning for a larger \"first lines\" value is that there may be more\r\nboilerplate code at the file's header. (Also for this reason, the 'modelines'\r\nvalue is not used by default.)\r\nYou can override both values for particular buffers \/ filetypes with the\r\nbuffer-scoped variable.\r\n\r\nThe plugin uses a list of rules to adapt the buffer contents on each save. You\r\ncan add your own rules, or completely replace the default rules. Rules can\r\nalso be overridden for individual buffers with a buffer-local variable. The\r\nrules consist of a List of Rule objects:\r\n    let g:AutoAdapt_Rules = [\r\n    \\   {\r\n    \\       'name': 'Copyright notice',\r\n    \\       'pattern': '\\c\\<Copyright:\\?\\d\\{4}\\>',\r\n    \\       'replacement': strftime('%Y'),\r\n    \\       'range': 'modelines'\r\n    \\   },\r\n    \\   { ... }\r\n    \\]\r\n\r\nname                    An optional, human-readable description of the rule.\r\npattern                 The regular-expression as used in a :substitute\r\n                        command (with the separator character \/, or\r\n                        substitutionSeparator).\r\npatternexpr             A Funcref (that takes the entire current rule object)\r\n                        or a String that is |eval()|ed to yield the pattern.\r\n                        Updates the pattern attribute on each run. You can use\r\n                        this to e.g. get the current date (via strftime(),\r\n                        to avoid a match of the current date with \/@!) into\r\n                        the pattern. The Funcref can throw \"AutoAdaptSkip\" to\r\n                        skip the application of this rule.\r\nreplacement             The replacement; you can use text or\r\n                        sub-replace-special.\r\nrange                   The (optional) range to which parts of the buffer the\r\n                        rule will be applied. It defaults to the empty string\r\n                        \"\", which uses the g:AutoAdapt_FirstLines and\r\n                        g:AutoAdapt_LastLines variables. Alternatives are:\r\n                        \"modelines\", which considers the 'modelines' number of\r\n                        lines at both the start and end of the buffer.\r\n                        You can also use \"%\" for the entire buffer, or use\r\n                        numbered ranges \"11,42\".\r\nsubstitutionSeparator   The separator in the :substitute. Change from the\r\n                        default \"\/\" to another non-alphanumeric single-byte\r\n                        character when the default is cumbersome. E146\r\n\r\nTo skip the automatic adaptation for certain files, in addition to\r\ng:AutoAdapt_FilePattern and :NoAutoAdapt, you can also configure a Funcref\r\n(if that is more convenient) that is passed the current file's filespec, and\r\nshould return a Boolean value whether it should be adapted. For example, if\r\nyou have the writebackupVersionControl.vim plugin (vimscript #1829)\r\ninstalled, you can skip adapting backups via:\r\n    let g:AutoAdapt_Predicate = function('writebackupVersionControl#IsOriginalFile')\r\n\r\nINTEGRATION\r\nAfter each write, the plugin sets the variable b:AutoAdapt to the number of\r\nrules that have been applied. If no rule was applied, the variable is removed.\r\nThe :NoAutoAdapt sets the variable to 0 to indicate that the plugin is\r\ndisabled for that buffer.\r\n\r\nIf you want to indicate (e.g. in your 'statusline') whether automatic adapting\r\ntook place or whether you've manually overridden the automation, you can use\r\nthe AutoAdapt#Info#Status() function, which returns:\r\n    \"adapted\"   when adaptation took place\r\n    \"noadapt\"   when automatic adaptation is enabled, but was turned off via\r\n                :NoAutoAdapt for this buffer\r\n    \"adapt\"     when automatic adaptation is disabled, but was turned on via\r\n                :AutoAdapt for this buffer\r\n    \"\"          in all other situations","first_name":"Ingo","6":"Ingo","last_name":"Karkat","7":"Karkat","releases":[{"0":"4654","vim_version":"7.0","1":"7.0","script_version":"1.11","2":"1.11","version_comment":"- Expose default s:lastChangePattern as g:AutoAdapt_LastChangePattern. Useful to adapt only this part when keeping the default rules.\r\n- Tweak g:AutoAdapt_LastChangePattern to also capture \/[lL]ast updated\\?\/ and \/Updated\/, and make the following : optional.\r\n- Old version compatibility: Prevent \"No matching autocommands\" messages in Vim 7.0\/1\/2. *** You need to update to ingo-library (vimscript #4433) version 1.025! ***","3":"- Expose default s:lastChangePattern as g:AutoAdapt_LastChangePattern. Useful to adapt only this part when keeping the default rules.\r\n- Tweak g:AutoAdapt_LastChangePattern to also capture \/[lL]ast updated\\?\/ and \/Updated\/, and make the following : optional.\r\n- Old version compatibility: Prevent \"No matching autocommands\" messages in Vim 7.0\/1\/2. *** You need to update to ingo-library (vimscript #4433) version 1.025! ***","package":"AutoAdapt-1.11.vmb.gz","4":"AutoAdapt-1.11.vmb.gz","src_id":"26432","5":"26432","creation_date":"1553405962","6":"1553405962"},{"0":"4654","vim_version":"7.0","1":"7.0","script_version":"1.10","2":"1.10","version_comment":"- ENH: Allow to disable \/ limit automatic adaptation via g:AutoAdapt_FilePattern configuration.\r\n- ENH: Add :AutoAdapt command to opt-in to automatic adaptation when it's either not enabled for the current buffer, or was turned off via :NoAutoAdapt.\r\n- ENH: Add AutoAdapt#Info#Status() function for use in a custom 'statusline'.\r\n- ENH: Allow to skip adaptation with g:AutoAdapt_Predicate.\r\n- ENH: Implement :Adapt command to manually trigger the adaptation (or override a configured predicate disallowing it).\r\n- Adapt to changed ingo#actions#EvaluateOrFunc() interface. *** You need to update to ingo-library (vimscript #4433) version 1.015! ***","3":"- ENH: Allow to disable \/ limit automatic adaptation via g:AutoAdapt_FilePattern configuration.\r\n- ENH: Add :AutoAdapt command to opt-in to automatic adaptation when it's either not enabled for the current buffer, or was turned off via :NoAutoAdapt.\r\n- ENH: Add AutoAdapt#Info#Status() function for use in a custom 'statusline'.\r\n- ENH: Allow to skip adaptation with g:AutoAdapt_Predicate.\r\n- ENH: Implement :Adapt command to manually trigger the adaptation (or override a configured predicate disallowing it).\r\n- Adapt to changed ingo#actions#EvaluateOrFunc() interface. *** You need to update to ingo-library (vimscript #4433) version 1.015! ***","package":"AutoAdapt-1.10.vmb.gz","4":"AutoAdapt-1.10.vmb.gz","src_id":"21327","5":"21327","creation_date":"1389818373","6":"1389818373"},{"0":"4654","vim_version":"7.0","1":"7.0","script_version":"1.00","2":"1.00","version_comment":"Initial upload","3":"Initial upload","package":"AutoAdapt-1.00.vmb.gz","4":"AutoAdapt-1.00.vmb.gz","src_id":"20501","5":"20501","creation_date":"1373360942","6":"1373360942"}]},"4653":{"script_id":"4653","0":"4653","script_name":"presenting.vim","1":"presenting.vim","script_type":"utility","2":"utility","summary":"A simple tool for presenting slides in vim based on text files.","3":"A simple tool for presenting slides in vim based on text files.","description":"https:\/\/github.com\/sotte\/presenting.vim","4":"https:\/\/github.com\/sotte\/presenting.vim","install_details":"","5":"","first_name":"stefan","6":"stefan","last_name":"otte","7":"otte","releases":[{"0":"4653","vim_version":"7.0","1":"7.0","script_version":"0.1.0","2":"0.1.0","version_comment":"Initial upload","3":"Initial upload","package":"presenting.vim.zip","4":"presenting.vim.zip","src_id":"20498","5":"20498","creation_date":"1373231343","6":"1373231343"}]},"4652":{"script_id":"4652","0":"4652","script_name":"NPM","1":"NPM","script_type":"utility","2":"utility","summary":"Using Node Package Manager in Vim","3":"Using Node Package Manager in Vim","description":"Working and using Node Package Manager in Vim editor. \r\n\r\nNPM.vim is a Vim plugin to manage and work with Node Package Manager (NPM) easily.","4":"Working and using Node Package Manager in Vim editor. \r\n\r\nNPM.vim is a Vim plugin to manage and work with Node Package Manager (NPM) easily.","install_details":"","5":"","first_name":"Afshin","6":"Afshin","last_name":"Mehrabani","7":"Mehrabani","releases":[{"0":"4652","vim_version":"7.0","1":"7.0","script_version":"0.1.0","2":"0.1.0","version_comment":"Initial upload","3":"Initial upload","package":"npm.vim.zip","4":"npm.vim.zip","src_id":"20497","5":"20497","creation_date":"1373200164","6":"1373200164"}]},"4651":{"script_id":"4651","0":"4651","script_name":"cottidie.vim","1":"cottidie.vim","script_type":"utility","2":"utility","summary":"Your quotidian Vim tip in 78 characters","3":"Your quotidian Vim tip in 78 characters","description":"This plugin brings friendly, syntax-highlighted Vim tips to your messages area. At 78 characters these have enough substance to inspire but not enough to distract. Try it out:\r\n\r\n:CottidieTip\r\n\r\nThe location of the tips file is configurable, so this plugin may also serve you as a \"daily tip\" engine which draws from your own notes. (Not actually daily though, it doesn't include any timing mechanism.)\r\n\r\nThe target audience is intermediate level. Contributions are welcome!\r\n","4":"This plugin brings friendly, syntax-highlighted Vim tips to your messages area. At 78 characters these have enough substance to inspire but not enough to distract. Try it out:\r\n\r\n:CottidieTip\r\n\r\nThe location of the tips file is configurable, so this plugin may also serve you as a \"daily tip\" engine which draws from your own notes. (Not actually daily though, it doesn't include any timing mechanism.)\r\n\r\nThe target audience is intermediate level. Contributions are welcome!\r\n","install_details":"Unzip the archive in your ~\/.vim directory. (On Windows, replace \"~\/.vim\" with \"$HOME\\vimfiles\".)\r\n\r\nThis plugin is also hosted on Github at https:\/\/github.com\/glts\/vim-cottidie\r\nWith pathogen.vim the installation is as simple as:\r\n\r\ncd ~\/.vim\/bundle\r\ngit clone https:\/\/github.com\/glts\/vim-cottidie.git cottidie\r\n","5":"Unzip the archive in your ~\/.vim directory. (On Windows, replace \"~\/.vim\" with \"$HOME\\vimfiles\".)\r\n\r\nThis plugin is also hosted on Github at https:\/\/github.com\/glts\/vim-cottidie\r\nWith pathogen.vim the installation is as simple as:\r\n\r\ncd ~\/.vim\/bundle\r\ngit clone https:\/\/github.com\/glts\/vim-cottidie.git cottidie\r\n","first_name":"David","6":"David","last_name":"B\u00c3\u00bcrgin","7":"B\u00c3\u00bcrgin","releases":[{"0":"4651","vim_version":"7.3","1":"7.3","script_version":"1.1.0","2":"1.1.0","version_comment":"Fixed minor issue with split window\r\nAdded more tips\r\n","3":"Fixed minor issue with split window\r\nAdded more tips\r\n","package":"cottidie.zip","4":"cottidie.zip","src_id":"20806","5":"20806","creation_date":"1379267876","6":"1379267876"},{"0":"4651","vim_version":"7.3","1":"7.3","script_version":"1.0.0","2":"1.0.0","version_comment":"Initial upload","3":"Initial upload","package":"cottidie.zip","4":"cottidie.zip","src_id":"20496","5":"20496","creation_date":"1373184134","6":"1373184134"}]},"4650":{"script_id":"4650","0":"4650","script_name":"conflictslides","1":"conflictslides","script_type":"utility","2":"utility","summary":"Exchange or assemble conflict content","3":"Exchange or assemble conflict content","description":"Lock to a range of lines delineated by conflict markers and skip through or assemble different content for that section.\r\nFor more, see github and the accompanying blog post:\r\nhttps:\/\/github.com\/dirkwallenstein\/vim-conflict-slides\r\nhttp:\/\/vertuxeltes.blogspot.de\/2013\/07\/conflict-resolution-with-vim-conflict.html","4":"Lock to a range of lines delineated by conflict markers and skip through or assemble different content for that section.\r\nFor more, see github and the accompanying blog post:\r\nhttps:\/\/github.com\/dirkwallenstein\/vim-conflict-slides\r\nhttp:\/\/vertuxeltes.blogspot.de\/2013\/07\/conflict-resolution-with-vim-conflict.html","install_details":"Please use Vundle or pathogen.","5":"Please use Vundle or pathogen.","first_name":"Dirk","6":"Dirk","last_name":"Wallenstein","7":"Wallenstein","releases":[{"0":"4650","vim_version":"7.3","1":"7.3","script_version":"1.0.0","2":"1.0.0","version_comment":"Initial upload","3":"Initial upload","package":"conflictslides-1.0.0.tar.gz","4":"conflictslides-1.0.0.tar.gz","src_id":"20492","5":"20492","creation_date":"1373132335","6":"1373132335"}]},"4649":{"script_id":"4649","0":"4649","script_name":"proguard.vim","1":"proguard.vim","script_type":"syntax","2":"syntax","summary":"Syntax highlighting for ProGuard configuration files","3":"Syntax highlighting for ProGuard configuration files","description":"Syntax highlighting for ProGuard configuration files","4":"Syntax highlighting for ProGuard configuration files","install_details":"","5":"","first_name":"David","6":"David","last_name":"Reiss","7":"Reiss","releases":[{"0":"4649","vim_version":"7.0","1":"7.0","script_version":"2","2":"2","version_comment":"Add some more directives.","3":"Add some more directives.","package":"proguard.vim","4":"proguard.vim","src_id":"23713","5":"23713","creation_date":"1446835274","6":"1446835274"},{"0":"4649","vim_version":"7.0","1":"7.0","script_version":"1","2":"1","version_comment":"Initial upload","3":"Initial upload","package":"proguard.vim","4":"proguard.vim","src_id":"20489","5":"20489","creation_date":"1373079276","6":"1373079276"}]},"4648":{"script_id":"4648","0":"4648","script_name":"yet-another-vim-buffer-list","1":"yet-another-vim-buffer-list","script_type":"utility","2":"utility","summary":"https:\/\/github.com\/jebberjeb\/yet-another-buffer-list","3":"https:\/\/github.com\/jebberjeb\/yet-another-buffer-list","description":"https:\/\/github.com\/jebberjeb\/yet-another-buffer-list","4":"https:\/\/github.com\/jebberjeb\/yet-another-buffer-list","install_details":"https:\/\/github.com\/jebberjeb\/yet-another-buffer-list","5":"https:\/\/github.com\/jebberjeb\/yet-another-buffer-list","first_name":"jeb","6":"jeb","last_name":"beich","7":"beich","releases":[{"0":"4648","vim_version":"7.3","1":"7.3","script_version":"0.2.0","2":"0.2.0","version_comment":"*added buffer deletion\r\n*buffer list not modifiable","3":"*added buffer deletion\r\n*buffer list not modifiable","package":"buflist.vim","4":"buflist.vim","src_id":"20628","5":"20628","creation_date":"1376194509","6":"1376194509"},{"0":"4648","vim_version":"7.3","1":"7.3","script_version":"0.1.0","2":"0.1.0","version_comment":"Initial upload","3":"Initial upload","package":"buflist.vim","4":"buflist.vim","src_id":"20484","5":"20484","creation_date":"1373048349","6":"1373048349"}]},"4647":{"script_id":"4647","0":"4647","script_name":"ecostation","1":"ecostation","script_type":"color scheme","2":"color scheme","summary":"Smooth natural colors on dark background. Put some jungle in your Vim.","3":"Smooth natural colors on dark background. Put some jungle in your Vim.","description":"This color scheme is for those who likes dark (but not black) background. \r\nThe colors are nice and natural and will not make your eyes burn.\r\nPut some jungle in your code with these green-red-orange gradations.\r\n\r\nThe color scheme is suitable for using on 16 color terminals.\r\n\r\nInitial inspiration for two primary colors came from divxstation.com.\r\n\r\nScreenshot: http:\/\/radiolybitel.ru\/yul\/ecostation_screen.png","4":"This color scheme is for those who likes dark (but not black) background. \r\nThe colors are nice and natural and will not make your eyes burn.\r\nPut some jungle in your code with these green-red-orange gradations.\r\n\r\nThe color scheme is suitable for using on 16 color terminals.\r\n\r\nInitial inspiration for two primary colors came from divxstation.com.\r\n\r\nScreenshot: http:\/\/radiolybitel.ru\/yul\/ecostation_screen.png","install_details":"1. Copy the file in your colors folder (i.e. ~\/.vim\/colors)\r\n2. Select the colorscheme via \":colorscheme ecostation\" or put this line in your .vimrc","5":"1. Copy the file in your colors folder (i.e. ~\/.vim\/colors)\r\n2. Select the colorscheme via \":colorscheme ecostation\" or put this line in your .vimrc","first_name":"Yulya","6":"Yulya","last_name":"Shtyryakova","7":"Shtyryakova","releases":[{"0":"4647","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"ecostation.vim","4":"ecostation.vim","src_id":"20482","5":"20482","creation_date":"1373032934","6":"1373032934"}]},"4646":{"script_id":"4646","0":"4646","script_name":"sexy_scroller.vim","1":"sexy_scroller.vim","script_type":"utility","2":"utility","summary":"Smooth animation of the cursor and the page whenever they move, with easing.","3":"Smooth animation of the cursor and the page whenever they move, with easing.","description":"sexy_scroller.vim - Smooth animation of the cursor and the page whenever they move, with easing.\r\nBy joeytwiddle, inspired by Terry Ma's smooth_scroll.vim, one of many Ctrl-U\/Ctrl-D scrollers.\r\nNot to be confused with daylilyfield\/sexyscroll.vim which lacks easing.\r\nI have not yet seen any other smooth-scrolling scripts that provide easing, operate on general movements, or use winrestview instead of keymappings\/cursorhold.\r\n\r\nUsually when you scroll the buffer or motion to a different part of the\r\ndocument, Vim will jump there immediately.  But with SexyScroller, Vim will\r\nscroll to the new position smoothly.  As well as looking pretty, this\r\nprovides you with visual feedback about the distance you have travelled.\r\n\r\n# Options\r\n\r\nInstead of specifying the scrolling *speed*, SexyScroller asks you to\r\nspecify how *slow* you want scrolling to be.  You can store these options in\r\nyour .vimrc once you are happy with them.\r\n\r\nSet the time it takes (in milliseconds) for the buffer to scroll one line or\r\ncolumn.\r\n\r\n    :let g:SexyScroller_ScrollTime = 10\r\n\r\nSet the time it takes for the cursor to travel one line.\r\nProbably only visible if you have `:set cursorline`.  Set it to 0 to never\r\nanimate the cursor.\r\n\r\n    :let g:SexyScroller_CursorTime = 5\r\n\r\n(I like to pretend the cursor is \"lighter\" than the buffer.)\r\n\r\nSet the maximum amount of time that longer scrolls can take:\r\n\r\n    :let g:SexyScroller_MaxTime = 500\r\n\r\nChoose the easing style (how scrolling accelerates and decelerates):\r\n\r\n    :let g:SexyScroller_EasingStyle = 2\r\n\r\nwhere\r\n\r\n  - 1 = start fast, finish slowly            (like 2 but less so)\r\n  - 2 = start very fast, finish very slowly  (recommended, default)\r\n  - 3 = start slowly, get faster, end slowly (sexy)\r\n  - 4 = start very slowly, end very slowly   (like 3 but more so)\r\n  - ? = constant speed                       (dull)\r\n\r\nInterrupts the animation if you press a key.  Resumes the animation if they\r\nkey you pressed causes further scrolling, otherwise just jumps directly to\r\nthe destination.  Resuming animation looks best with EasingStyle 1.\r\n\r\n    :let g:SexyScroller_DetectPendingKeys = 1   \/   0\r\n\r\nThis command is provided to enable\/disable the scrolling:\r\n\r\n    :SexyScrollerToggle\r\n\r\nFor eye candy, try MaxTime=1200, EasingStyle=3 and increase ScrollTime as\r\nwell.  This can help to visualise the distance travelled when moving through\r\na document.\r\n\r\nPower users may prefer to lower MaxTime to 400, and set EasingStyle 1 or 0.\r\nThis will make Vim feel more like normal (more responsive).\r\n\r\n\r\n\r\nWorks pretty well in the general case, without having to configure custom mappings, but there are a few known issues which are documented in the script itself.\r\n\r\nThe most noticeable is that if you have 'hlsearch' enabled, scrolling does not occur until *after* you leave search mode!  Although it works fine on n and N.\r\n\r\nOlder versions of the script may be found at https:\/\/github.com\/joeytwiddle\/sexy_scroller.vim","4":"sexy_scroller.vim - Smooth animation of the cursor and the page whenever they move, with easing.\r\nBy joeytwiddle, inspired by Terry Ma's smooth_scroll.vim, one of many Ctrl-U\/Ctrl-D scrollers.\r\nNot to be confused with daylilyfield\/sexyscroll.vim which lacks easing.\r\nI have not yet seen any other smooth-scrolling scripts that provide easing, operate on general movements, or use winrestview instead of keymappings\/cursorhold.\r\n\r\nUsually when you scroll the buffer or motion to a different part of the\r\ndocument, Vim will jump there immediately.  But with SexyScroller, Vim will\r\nscroll to the new position smoothly.  As well as looking pretty, this\r\nprovides you with visual feedback about the distance you have travelled.\r\n\r\n# Options\r\n\r\nInstead of specifying the scrolling *speed*, SexyScroller asks you to\r\nspecify how *slow* you want scrolling to be.  You can store these options in\r\nyour .vimrc once you are happy with them.\r\n\r\nSet the time it takes (in milliseconds) for the buffer to scroll one line or\r\ncolumn.\r\n\r\n    :let g:SexyScroller_ScrollTime = 10\r\n\r\nSet the time it takes for the cursor to travel one line.\r\nProbably only visible if you have `:set cursorline`.  Set it to 0 to never\r\nanimate the cursor.\r\n\r\n    :let g:SexyScroller_CursorTime = 5\r\n\r\n(I like to pretend the cursor is \"lighter\" than the buffer.)\r\n\r\nSet the maximum amount of time that longer scrolls can take:\r\n\r\n    :let g:SexyScroller_MaxTime = 500\r\n\r\nChoose the easing style (how scrolling accelerates and decelerates):\r\n\r\n    :let g:SexyScroller_EasingStyle = 2\r\n\r\nwhere\r\n\r\n  - 1 = start fast, finish slowly            (like 2 but less so)\r\n  - 2 = start very fast, finish very slowly  (recommended, default)\r\n  - 3 = start slowly, get faster, end slowly (sexy)\r\n  - 4 = start very slowly, end very slowly   (like 3 but more so)\r\n  - ? = constant speed                       (dull)\r\n\r\nInterrupts the animation if you press a key.  Resumes the animation if they\r\nkey you pressed causes further scrolling, otherwise just jumps directly to\r\nthe destination.  Resuming animation looks best with EasingStyle 1.\r\n\r\n    :let g:SexyScroller_DetectPendingKeys = 1   \/   0\r\n\r\nThis command is provided to enable\/disable the scrolling:\r\n\r\n    :SexyScrollerToggle\r\n\r\nFor eye candy, try MaxTime=1200, EasingStyle=3 and increase ScrollTime as\r\nwell.  This can help to visualise the distance travelled when moving through\r\na document.\r\n\r\nPower users may prefer to lower MaxTime to 400, and set EasingStyle 1 or 0.\r\nThis will make Vim feel more like normal (more responsive).\r\n\r\n\r\n\r\nWorks pretty well in the general case, without having to configure custom mappings, but there are a few known issues which are documented in the script itself.\r\n\r\nThe most noticeable is that if you have 'hlsearch' enabled, scrolling does not occur until *after* you leave search mode!  Although it works fine on n and N.\r\n\r\nOlder versions of the script may be found at https:\/\/github.com\/joeytwiddle\/sexy_scroller.vim","install_details":"Drop the script in your ~\/.vim\/plugin folder","5":"Drop the script in your ~\/.vim\/plugin folder","first_name":"joey","6":"joey","last_name":"twiddle","7":"twiddle","releases":[{"0":"4646","vim_version":"7.0","1":"7.0","script_version":"20130714","2":"20130714","version_comment":"sqrt(cos) is a better easing function, added CursorMovedI event, to catch PageUp\/Down","3":"sqrt(cos) is a better easing function, added CursorMovedI event, to catch PageUp\/Down","package":"sexy_scroller.vim","4":"sexy_scroller.vim","src_id":"20512","5":"20512","creation_date":"1373810495","6":"1373810495"},{"0":"4646","vim_version":"7.0","1":"7.0","script_version":"20130703","2":"20130703","version_comment":"Initial upload","3":"Initial upload","package":"sexy_scroller.vim","4":"sexy_scroller.vim","src_id":"20475","5":"20475","creation_date":"1372813122","6":"1372813122"}]},"4645":{"script_id":"4645","0":"4645","script_name":"vroom-syntax.vim","1":"vroom-syntax.vim","script_type":"syntax","2":"syntax","summary":"Syntax for  Vroom-pm","3":"Syntax for  Vroom-pm","description":"Syntax for Vroom\r\n================\r\n\r\n[Vroom][1] is a Vim slide show system. It use a custom filetype vroom.\r\nThis repository is Vim syntax for vroom file.\r\n\r\n[1]:https:\/\/github.com\/ingydotnet\/vroom-pm\r\n\r\nRepo\r\n--------\r\n\r\n* [Github]:https:\/\/github.com\/othree\/vroom-syntax.vim\r\n\r\nLicense\r\n-------\r\n\r\nCopyright (C) 2013 Kao, Wei-Ko\r\n\r\nPermission is hereby granted, free of charge, to any person obtaining\r\na copy of this software and associated documentation files (the \"Software\"),\r\nto deal in the Software without restriction, including without limitation\r\nthe rights to use, copy, modify, merge, publish, distribute, sublicense,\r\nand\/or sell copies of the Software, and to permit persons to whom the \r\nSoftware is furnished to do so, subject to the following conditions:\r\n\r\nThe above copyright notice and this permission notice shall be included\r\nin all copies or substantial portions of the Software.\r\n\r\nTHE SOFTWARE IS PROVIDED \"AS IS\", WITHOUT WARRANTY OF ANY KIND,\r\nEXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES\r\nOF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT.\r\nIN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM,\r\nDAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT,\r\nTORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE\r\nOR THE USE OR OTHER DEALINGS IN THE SOFTWARE.","4":"Syntax for Vroom\r\n================\r\n\r\n[Vroom][1] is a Vim slide show system. It use a custom filetype vroom.\r\nThis repository is Vim syntax for vroom file.\r\n\r\n[1]:https:\/\/github.com\/ingydotnet\/vroom-pm\r\n\r\nRepo\r\n--------\r\n\r\n* [Github]:https:\/\/github.com\/othree\/vroom-syntax.vim\r\n\r\nLicense\r\n-------\r\n\r\nCopyright (C) 2013 Kao, Wei-Ko\r\n\r\nPermission is hereby granted, free of charge, to any person obtaining\r\na copy of this software and associated documentation files (the \"Software\"),\r\nto deal in the Software without restriction, including without limitation\r\nthe rights to use, copy, modify, merge, publish, distribute, sublicense,\r\nand\/or sell copies of the Software, and to permit persons to whom the \r\nSoftware is furnished to do so, subject to the following conditions:\r\n\r\nThe above copyright notice and this permission notice shall be included\r\nin all copies or substantial portions of the Software.\r\n\r\nTHE SOFTWARE IS PROVIDED \"AS IS\", WITHOUT WARRANTY OF ANY KIND,\r\nEXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES\r\nOF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT.\r\nIN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM,\r\nDAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT,\r\nTORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE\r\nOR THE USE OR OTHER DEALINGS IN THE SOFTWARE.","install_details":"Use *Vundle* or *pathogen.vim*\r\nOr you can just copy the file to `~\/.vim\/syntax\/`\r\n\r\nThen add the following line in your vimrc\r\n\r\n    au BufRead,BufNewFile *.vroom set ft=vroom\r\n\r\n[Vundle]:https:\/\/github.com\/gmarik\/vundle\r\n[pathogen.vim]:https:\/\/github.com\/tpope\/vim-pathogen","5":"Use *Vundle* or *pathogen.vim*\r\nOr you can just copy the file to `~\/.vim\/syntax\/`\r\n\r\nThen add the following line in your vimrc\r\n\r\n    au BufRead,BufNewFile *.vroom set ft=vroom\r\n\r\n[Vundle]:https:\/\/github.com\/gmarik\/vundle\r\n[pathogen.vim]:https:\/\/github.com\/tpope\/vim-pathogen","first_name":"wei ko","6":"wei ko","last_name":"kao","7":"kao","releases":[{"0":"4645","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"vroom.vim","4":"vroom.vim","src_id":"20470","5":"20470","creation_date":"1372756957","6":"1372756957"}]},"4644":{"script_id":"4644","0":"4644","script_name":"git_shade.vim","1":"git_shade.vim","script_type":"utility","2":"utility","summary":"Colors lines in different intensities according to their age in git's history","3":"Colors lines in different intensities according to their age in git's history","description":"Colours lines in different intensities according to their age in git's history\r\nAlso displays commit info for the current line in the cmdline.\r\n\r\nRun `:GitShade` to shade the file, and again to turn it off.\r\n\r\nNaturally this only works in Vim's GUI mode.\r\nIf you never have GUI mode available, you may want to try the\r\nGitGutter plugin instead: https:\/\/github.com\/airblade\/vim-gitgutter\r\n\r\nSome possible options (see the plugin file for more):\r\n\r\n    let g:GitShade_ColorGradient = \"black_to_blue\"\r\n    let g:GitShade_ColorWhat = \"bg\"\r\n\r\n    let g:GitShade_ColorGradient = \"green_to_white\"\r\n    let g:GitShade_ColorWhat = \"fg\"\r\n\r\nIn the screenshots below, the brighter blue background indicates a more recent addition.\r\n\r\nWith `let g:GitShade_Linear = 0` the recent additions stand out clearly:\r\n\r\nhttp:\/\/neuralyte.org\/~joey\/git_shade\/git_shade\/git_shade_non_linear.png\r\n\r\nWith `let g:GitShade_Linear = 1` we can see the relative ages of all lines in the file:\r\n\r\nhttp:\/\/neuralyte.org\/~joey\/git_shade\/git_shade\/git_shade_linear.png","4":"Colours lines in different intensities according to their age in git's history\r\nAlso displays commit info for the current line in the cmdline.\r\n\r\nRun `:GitShade` to shade the file, and again to turn it off.\r\n\r\nNaturally this only works in Vim's GUI mode.\r\nIf you never have GUI mode available, you may want to try the\r\nGitGutter plugin instead: https:\/\/github.com\/airblade\/vim-gitgutter\r\n\r\nSome possible options (see the plugin file for more):\r\n\r\n    let g:GitShade_ColorGradient = \"black_to_blue\"\r\n    let g:GitShade_ColorWhat = \"bg\"\r\n\r\n    let g:GitShade_ColorGradient = \"green_to_white\"\r\n    let g:GitShade_ColorWhat = \"fg\"\r\n\r\nIn the screenshots below, the brighter blue background indicates a more recent addition.\r\n\r\nWith `let g:GitShade_Linear = 0` the recent additions stand out clearly:\r\n\r\nhttp:\/\/neuralyte.org\/~joey\/git_shade\/git_shade\/git_shade_non_linear.png\r\n\r\nWith `let g:GitShade_Linear = 1` we can see the relative ages of all lines in the file:\r\n\r\nhttp:\/\/neuralyte.org\/~joey\/git_shade\/git_shade\/git_shade_linear.png","install_details":"Drop the file in ~\/.vim\/plugin\/","5":"Drop the file in ~\/.vim\/plugin\/","first_name":"joey","6":"joey","last_name":"twiddle","7":"twiddle","releases":[{"0":"4644","vim_version":"6.0","1":"6.0","script_version":"20130627","2":"20130627","version_comment":"Initial upload","3":"Initial upload","package":"git_shade.vim","4":"git_shade.vim","src_id":"20463","5":"20463","creation_date":"1372621949","6":"1372621949"}]},"4643":{"script_id":"4643","0":"4643","script_name":"mlessnau_dark","1":"mlessnau_dark","script_type":"color scheme","2":"color scheme","summary":"dark 256 color scheme inspired by railscasts","3":"dark 256 color scheme inspired by railscasts","description":"This 256 color scheme is inspired by the color scheme used by railscasts.\r\n\r\nIt does work in 256-color terminals (export TERM=screen-256color) but results may differ when using it in gvim.\r\n\r\nIt is optimized for vimdiff, ruby, javascript, php, c\/c++, sh and HTML. It has some tweaks for NERD_tree as well.\r\n\r\nEnjoy :)","4":"This 256 color scheme is inspired by the color scheme used by railscasts.\r\n\r\nIt does work in 256-color terminals (export TERM=screen-256color) but results may differ when using it in gvim.\r\n\r\nIt is optimized for vimdiff, ruby, javascript, php, c\/c++, sh and HTML. It has some tweaks for NERD_tree as well.\r\n\r\nEnjoy :)","install_details":"1. Copy the file in your colors folder (i.e. ~\/.vim\/colors)\r\n2. Select the colorscheme via \":colorscheme mlessnau_dark\" or setup your .vimrc accordingly\r\n\r\nYou'll probably need to restart running Vim instances in order to be able to use of the color scheme.\r\n","5":"1. Copy the file in your colors folder (i.e. ~\/.vim\/colors)\r\n2. Select the colorscheme via \":colorscheme mlessnau_dark\" or setup your .vimrc accordingly\r\n\r\nYou'll probably need to restart running Vim instances in order to be able to use of the color scheme.\r\n","first_name":"Michael","6":"Michael","last_name":"Le\u00c3\u009fnau","7":"Le\u00c3\u009fnau","releases":[{"0":"4643","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"mlessnau_dark.vim","4":"mlessnau_dark.vim","src_id":"20462","5":"20462","creation_date":"1372619459","6":"1372619459"}]},"4642":{"script_id":"4642","0":"4642","script_name":"mlessnau_bisectional_movement","1":"mlessnau_bisectional_movement","script_type":"utility","2":"utility","summary":"Allows horizontal movement in a bisectional fashion (command mode only)","3":"Allows horizontal movement in a bisectional fashion (command mode only)","description":"This plugin introduces a command mode mappings (does not work in visual mode yet):\r\n\r\n1. <Tab> (move right)\r\n2. <Shift>+<Tab> (move left)\r\n\r\nDepending on whether you are moving to the left or right, by doing it in a bisectional fashion, you're skipping half the content to the start or end of the line.\r\n\r\nThe feature is quite simplistic but saves a lot of time when you need to access content in the middle the current line over and over.","4":"This plugin introduces a command mode mappings (does not work in visual mode yet):\r\n\r\n1. <Tab> (move right)\r\n2. <Shift>+<Tab> (move left)\r\n\r\nDepending on whether you are moving to the left or right, by doing it in a bisectional fashion, you're skipping half the content to the start or end of the line.\r\n\r\nThe feature is quite simplistic but saves a lot of time when you need to access content in the middle the current line over and over.","install_details":"1. Copy the file in your plugin folder (i.e. ~\/.vim\/plugin)\r\n2. Done\r\n\r\nYou'll need to restart running Vim instances in order to be able to use of the plugin.\r\n","5":"1. Copy the file in your plugin folder (i.e. ~\/.vim\/plugin)\r\n2. Done\r\n\r\nYou'll need to restart running Vim instances in order to be able to use of the plugin.\r\n","first_name":"Michael","6":"Michael","last_name":"Le\u00c3\u009fnau","7":"Le\u00c3\u009fnau","releases":[{"0":"4642","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"mlessnau_bisectional_movement.vim","4":"mlessnau_bisectional_movement.vim","src_id":"20461","5":"20461","creation_date":"1372618762","6":"1372618762"}]},"4641":{"script_id":"4641","0":"4641","script_name":"mlessnau_case","1":"mlessnau_case","script_type":"utility","2":"utility","summary":"\"in-case\" selection, deletion and substitution for underscore, camel, mixed case","3":"\"in-case\" selection, deletion and substitution for underscore, camel, mixed case","description":"This plugin introduces 3 new Vim commands:\r\n\r\n1. vic (select in-case)\r\n2. dic (delete in-case) -- this mapping is disabled as of version 0.2 (you can define your own if you need to)\r\n3. cic (change\/substitute in-case)\r\n\r\nSupported identifier cases are \"camel case\" (coolCat, CoolCat), \"snake case\" (good_dog, GOOD_DOG) and a mix of both (_coolDog, Good_Cat).\r\n\r\nBy using the above commands you can quickly select, delete or change segments of cased identifiers depending on which segment the cursor is pointing at. For example ([x] denotes the cursor position, or selection):\r\n\r\nviw: Fo[o]Bar -> [Foo]Bar (-> visual mode)\r\nciw: foo_[B]arBaz -> foo_[]Baz (-> insert mode)\r\n\r\nin order to use in-case deletion you may map the call to DeleteInCase() accordingly.","4":"This plugin introduces 3 new Vim commands:\r\n\r\n1. vic (select in-case)\r\n2. dic (delete in-case) -- this mapping is disabled as of version 0.2 (you can define your own if you need to)\r\n3. cic (change\/substitute in-case)\r\n\r\nSupported identifier cases are \"camel case\" (coolCat, CoolCat), \"snake case\" (good_dog, GOOD_DOG) and a mix of both (_coolDog, Good_Cat).\r\n\r\nBy using the above commands you can quickly select, delete or change segments of cased identifiers depending on which segment the cursor is pointing at. For example ([x] denotes the cursor position, or selection):\r\n\r\nviw: Fo[o]Bar -> [Foo]Bar (-> visual mode)\r\nciw: foo_[B]arBaz -> foo_[]Baz (-> insert mode)\r\n\r\nin order to use in-case deletion you may map the call to DeleteInCase() accordingly.","install_details":"1. Copy the file in your plugin folder (i.e. ~\/.vim\/plugin)\r\n2. Done\r\n\r\nYou'll need to restart running Vim instances in order to be able to use of the plugin.\r\n","5":"1. Copy the file in your plugin folder (i.e. ~\/.vim\/plugin)\r\n2. Done\r\n\r\nYou'll need to restart running Vim instances in order to be able to use of the plugin.\r\n","first_name":"Michael","6":"Michael","last_name":"Le\u00c3\u009fnau","7":"Le\u00c3\u009fnau","releases":[{"0":"4641","vim_version":"7.0","1":"7.0","script_version":"0.2","2":"0.2","version_comment":"Disables shortcut \"dic\" for in-case deletion as it appeared to conflict with \"dd\"","3":"Disables shortcut \"dic\" for in-case deletion as it appeared to conflict with \"dd\"","package":"mlessnau_case.vim","4":"mlessnau_case.vim","src_id":"20507","5":"20507","creation_date":"1373531475","6":"1373531475"},{"0":"4641","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"mlessnau_case.vim","4":"mlessnau_case.vim","src_id":"20460","5":"20460","creation_date":"1372617864","6":"1372617864"}]},"4640":{"script_id":"4640","0":"4640","script_name":"accelerated-smooth-scroll","1":"accelerated-smooth-scroll","script_type":"utility","2":"utility","summary":"Scrolling in Vim with smooth animation and acceleration behavior","3":"Scrolling in Vim with smooth animation and acceleration behavior","description":"Vim plugin for accelerated smooth scroll.\r\n\r\nThe *accelerated-smooth-scroll* plugin makes scrolling with a smooth animation in Vim.\r\nMoreover, the scroll speed will be accelerated, if you consecutively scroll.\r\n\r\n`<C-D>\/<C-U>` and `<C-F>\/<C-B>` keys are replaced by default.\r\n\r\nIntroduction Movie:\r\n - http:\/\/www.youtube.com\/watch?v=mGMgAiS8Xtg\r\n\r\nRepository:\r\n- https:\/\/github.com\/yonchu\/accelerated-smooth-scroll ","4":"Vim plugin for accelerated smooth scroll.\r\n\r\nThe *accelerated-smooth-scroll* plugin makes scrolling with a smooth animation in Vim.\r\nMoreover, the scroll speed will be accelerated, if you consecutively scroll.\r\n\r\n`<C-D>\/<C-U>` and `<C-F>\/<C-B>` keys are replaced by default.\r\n\r\nIntroduction Movie:\r\n - http:\/\/www.youtube.com\/watch?v=mGMgAiS8Xtg\r\n\r\nRepository:\r\n- https:\/\/github.com\/yonchu\/accelerated-smooth-scroll ","install_details":"See README.md.","5":"See README.md.","first_name":"Yonchu","6":"Yonchu","last_name":" ","7":" ","releases":[{"0":"4640","vim_version":"7.0","1":"7.0","script_version":"1.1.0","2":"1.1.0","version_comment":"- Disable (and restore after scroll) relative line numbers to improve performance\r\n- Add ac_smooth_scroll_disable_relativenumber option (default: 1)\r\n- Bugfix\r\n  - Rename functions not to use global function like g:hogehoge\r\n  - Use setlocal instead of set to save and restore settings\r\n","3":"- Disable (and restore after scroll) relative line numbers to improve performance\r\n- Add ac_smooth_scroll_disable_relativenumber option (default: 1)\r\n- Bugfix\r\n  - Rename functions not to use global function like g:hogehoge\r\n  - Use setlocal instead of set to save and restore settings\r\n","package":"accelerated-smooth-scroll.zip","4":"accelerated-smooth-scroll.zip","src_id":"22413","5":"22413","creation_date":"1410429287","6":"1410429287"},{"0":"4640","vim_version":"7.0","1":"7.0","script_version":"1.0.1","2":"1.0.1","version_comment":"Fix executing doautocmd for old version of Vim","3":"Fix executing doautocmd for old version of Vim","package":"accelerated-smooth-scroll.zip","4":"accelerated-smooth-scroll.zip","src_id":"20458","5":"20458","creation_date":"1372588127","6":"1372588127"},{"0":"4640","vim_version":"7.0","1":"7.0","script_version":"1.0.0","2":"1.0.0","version_comment":"Initial upload","3":"Initial upload","package":"accelerated-smooth-scroll.zip","4":"accelerated-smooth-scroll.zip","src_id":"20456","5":"20456","creation_date":"1372582581","6":"1372582581"}]},"4639":{"script_id":"4639","0":"4639","script_name":"vim-wakatime","1":"vim-wakatime","script_type":"utility","2":"utility","summary":"Fully automatic time tracking for Vim","3":"Fully automatic time tracking for Vim","description":"Fully automatic time tracking for Vim.\r\n\r\nOpen-source on GitHub: https:\/\/github.com\/wakatime\/vim-wakatime","4":"Fully automatic time tracking for Vim.\r\n\r\nOpen-source on GitHub: https:\/\/github.com\/wakatime\/vim-wakatime","install_details":"https:\/\/wakatime.com\/help\/plugins\/vim","5":"https:\/\/wakatime.com\/help\/plugins\/vim","first_name":"Alan","6":"Alan","last_name":"Hamlett","7":"Hamlett","releases":[{"0":"4639","vim_version":"7.0","1":"7.0","script_version":"1.2.3","2":"1.2.3","version_comment":"Use Vundle for the most recent version.","3":"Use Vundle for the most recent version.","package":"vim-wakatime.zip","4":"vim-wakatime.zip","src_id":"21026","5":"21026","creation_date":"1384185553","6":"1384185553"}]},"4638":{"script_id":"4638","0":"4638","script_name":"newnoise.vim","1":"newnoise.vim","script_type":"color scheme","2":"color scheme","summary":"Black and red, low contrast scheme","3":"Black and red, low contrast scheme","description":"This is a very low contrast, mono color scheme. It's especially well suited for highlighting the structure of your code. But you could use it as your main colorscheme as well.\r\nhttp:\/\/i.imgur.com\/Boe7eGD.png","4":"This is a very low contrast, mono color scheme. It's especially well suited for highlighting the structure of your code. But you could use it as your main colorscheme as well.\r\nhttp:\/\/i.imgur.com\/Boe7eGD.png","install_details":"","5":"","first_name":"Olivier","6":"Olivier","last_name":"Bellemans","7":"Bellemans","releases":[{"0":"4638","vim_version":"7.0","1":"7.0","script_version":"1.1","2":"1.1","version_comment":"Display issue for JavaScript files fixed","3":"Display issue for JavaScript files fixed","package":"newnoise.vim","4":"newnoise.vim","src_id":"20450","5":"20450","creation_date":"1372328540","6":"1372328540"},{"0":"4638","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"newnoise.vim","4":"newnoise.vim","src_id":"20446","5":"20446","creation_date":"1372261974","6":"1372261974"}]},"4637":{"script_id":"4637","0":"4637","script_name":"symfind","1":"symfind","script_type":"utility","2":"utility","summary":"find symbol or file in your project","3":"find symbol or file in your project","description":"Symfind is designed for easy locating files and symbols. It's similar to such tools as ctags\/cscope\/global\/vim+fuzzyfind, but optimized for large-scale project. \r\n\r\nKey features of Symfind:\r\n- natural search pattern, like in google\r\n- small repository\r\n- simple, stable and reliable\r\n- value search for macro or variable\r\n- vim integration\r\n\r\nThe project is host on google:  https:\/\/code.google.com\/p\/symfind\/\r\nPlease read __README__.txt in the release package for detail.\r\n","4":"Symfind is designed for easy locating files and symbols. It's similar to such tools as ctags\/cscope\/global\/vim+fuzzyfind, but optimized for large-scale project. \r\n\r\nKey features of Symfind:\r\n- natural search pattern, like in google\r\n- small repository\r\n- simple, stable and reliable\r\n- value search for macro or variable\r\n- vim integration\r\n\r\nThe project is host on google:  https:\/\/code.google.com\/p\/symfind\/\r\nPlease read __README__.txt in the release package for detail.\r\n","install_details":"The installation is just to copy files to your folder.\r\n\r\nOn Linux, modify path in script install_linux.sh and run it. \r\n\r\nOn MS Windows, you need install Perl. Modify install_windows.bat for your path and run it. \r\n","5":"The installation is just to copy files to your folder.\r\n\r\nOn Linux, modify path in script install_linux.sh and run it. \r\n\r\nOn MS Windows, you need install Perl. Modify install_windows.bat for your path and run it. \r\n","first_name":"Jian","6":"Jian","last_name":"Liang","7":"Liang","releases":[{"0":"4637","vim_version":"7.0","1":"7.0","script_version":"2.1","2":"2.1","version_comment":"- performance enhancement (rewrite symfind using C++);\r\n- g-grep command; \r\n- shell command in symfind;","3":"- performance enhancement (rewrite symfind using C++);\r\n- g-grep command; \r\n- shell command in symfind;","package":"symfind-2.1.tgz","4":"symfind-2.1.tgz","src_id":"20805","5":"20805","creation_date":"1379177940","6":"1379177940"},{"0":"4637","vim_version":"7.0","1":"7.0","script_version":"2.0.1","2":"2.0.1","version_comment":"important bugfix.","3":"important bugfix.","package":"symfind-2.0.1.tgz","4":"symfind-2.0.1.tgz","src_id":"20466","5":"20466","creation_date":"1372673764","6":"1372673764"},{"0":"4637","vim_version":"7.0","1":"7.0","script_version":"2.0","2":"2.0","version_comment":"Initial upload","3":"Initial upload","package":"symfind-2.0.tgz","4":"symfind-2.0.tgz","src_id":"20443","5":"20443","creation_date":"1372241113","6":"1372241113"}]},"4636":{"script_id":"4636","0":"4636","script_name":"TempKeyword","1":"TempKeyword","script_type":"utility","2":"utility","summary":"Highlight keyword temporarily.","3":"Highlight keyword temporarily.","description":"[Default Usage]\r\n\r\nAssume <leader> is default value, use \\0 ~ \\9 to add keywords to group 0 ~ 9.\r\n\\c0 ~ \\c9 can clear corresponding groups.\r\n\\ca can clear all groups.\r\n\r\n[Customization]\r\n\r\nSet TempKeywordCmdPrefix to change prefix command.\r\nUse DeclareTempKeyword to add more groups with customized color.\r\n\r\n[GIT]\r\nhttps:\/\/github.com\/BlueCatMe\/TempKeyword","4":"[Default Usage]\r\n\r\nAssume <leader> is default value, use \\0 ~ \\9 to add keywords to group 0 ~ 9.\r\n\\c0 ~ \\c9 can clear corresponding groups.\r\n\\ca can clear all groups.\r\n\r\n[Customization]\r\n\r\nSet TempKeywordCmdPrefix to change prefix command.\r\nUse DeclareTempKeyword to add more groups with customized color.\r\n\r\n[GIT]\r\nhttps:\/\/github.com\/BlueCatMe\/TempKeyword","install_details":"Put it in vim plugin folder.","5":"Put it in vim plugin folder.","first_name":"BlueCat","6":"BlueCat","last_name":"Chen","7":"Chen","releases":[{"0":"4636","vim_version":"6.0","1":"6.0","script_version":"1.1","2":"1.1","version_comment":"Initial upload","3":"Initial upload","package":"tempkeyword.vim","4":"tempkeyword.vim","src_id":"20440","5":"20440","creation_date":"1372236172","6":"1372236172"}]},"4635":{"script_id":"4635","0":"4635","script_name":"vim-github-dashboard","1":"vim-github-dashboard","script_type":"utility","2":"utility","summary":"Browse GitHub events in Vim","3":"Browse GitHub events in Vim","description":"This plugin allows you to browse GitHub events (user dashboard, user\/repo activity) in Vim.\r\n\r\nProject Home:\r\n  https:\/\/github.com\/junegunn\/vim-github-dashboard\r\n\r\nRequirements:\r\n  - Ruby support\r\n  - json_pure or json gem\r\n\r\nCommands (with authentication):\r\n  - :GHDashboard\r\n  - :GHDashboard USER\r\n  - :GHActivity\r\n  - :GHActivity USER\r\n  - :GHActivity USER\/REPO\r\n\r\nCommands (without authentication):\r\n  - :GHDashboard! USER\r\n  - :GHActivity! USER\r\n  - :GHActivity! USER\/REPO\r\n\r\nNavigation:\r\n  Use Tab and Shift-Tab to navigate back and forth through the links.\r\n  Press Enter key or double-click on a link to open it in the browser.\r\n  Press R to refresh the tab.\r\n  Press q to close the tab.","4":"This plugin allows you to browse GitHub events (user dashboard, user\/repo activity) in Vim.\r\n\r\nProject Home:\r\n  https:\/\/github.com\/junegunn\/vim-github-dashboard\r\n\r\nRequirements:\r\n  - Ruby support\r\n  - json_pure or json gem\r\n\r\nCommands (with authentication):\r\n  - :GHDashboard\r\n  - :GHDashboard USER\r\n  - :GHActivity\r\n  - :GHActivity USER\r\n  - :GHActivity USER\/REPO\r\n\r\nCommands (without authentication):\r\n  - :GHDashboard! USER\r\n  - :GHActivity! USER\r\n  - :GHActivity! USER\/REPO\r\n\r\nNavigation:\r\n  Use Tab and Shift-Tab to navigate back and forth through the links.\r\n  Press Enter key or double-click on a link to open it in the browser.\r\n  Press R to refresh the tab.\r\n  Press q to close the tab.","install_details":"Extract in ~\/.vim, or use Pathogen or Vundle.\r\n\r\nWith Vundle:\r\n  Add the following line to your .vimrc,\r\n    Bundle 'junegunn\/vim-github-dashboard'\r\n  then execute, :BundleInstall command.\r\n\r\nWith Pathogen:\r\n    cd ~\/.vim\/bundle\r\n    git clone git@github.com:junegunn\/vim-github-dashboard.git","5":"Extract in ~\/.vim, or use Pathogen or Vundle.\r\n\r\nWith Vundle:\r\n  Add the following line to your .vimrc,\r\n    Bundle 'junegunn\/vim-github-dashboard'\r\n  then execute, :BundleInstall command.\r\n\r\nWith Pathogen:\r\n    cd ~\/.vim\/bundle\r\n    git clone git@github.com:junegunn\/vim-github-dashboard.git","first_name":"Junegunn","6":"Junegunn","last_name":"Choi","7":"Choi","releases":[{"0":"4635","vim_version":"7.3","1":"7.3","script_version":"1.3","2":"1.3","version_comment":"- Added g:github_dashboard['position'] option\r\n- Added g:github_dashboard['emoji_map'] option\r\n- Emoji on tab line\r\n","3":"- Added g:github_dashboard['position'] option\r\n- Added g:github_dashboard['emoji_map'] option\r\n- Emoji on tab line\r\n","package":"vim-github-dashboard.zip","4":"vim-github-dashboard.zip","src_id":"20480","5":"20480","creation_date":"1372949804","6":"1372949804"},{"0":"4635","vim_version":"7.3","1":"7.3","script_version":"1.2","2":"1.2","version_comment":"- Print emoji in comments as well\r\n- Fix gist URL\r\n","3":"- Print emoji in comments as well\r\n- Fix gist URL\r\n","package":"vim-github-dashboard.zip","4":"vim-github-dashboard.zip","src_id":"20467","5":"20467","creation_date":"1372693382","6":"1372693382"},{"0":"4635","vim_version":"7.3","1":"7.3","script_version":"1.1","2":"1.1","version_comment":"- Shows repository activity as well (USER\/REPO)\r\n- R key to refresh dashboard\r\n- Double-click on links","3":"- Shows repository activity as well (USER\/REPO)\r\n- R key to refresh dashboard\r\n- Double-click on links","package":"vim-github-dashboard.zip","4":"vim-github-dashboard.zip","src_id":"20451","5":"20451","creation_date":"1372351069","6":"1372351069"},{"0":"4635","vim_version":"7.3","1":"7.3","script_version":"1.0.1","2":"1.0.1","version_comment":"Bug fixes","3":"Bug fixes","package":"vim-github-dashboard.zip","4":"vim-github-dashboard.zip","src_id":"20437","5":"20437","creation_date":"1372215017","6":"1372215017"},{"0":"4635","vim_version":"7.3","1":"7.3","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"vim-github-dashboard.zip","4":"vim-github-dashboard.zip","src_id":"20435","5":"20435","creation_date":"1372186392","6":"1372186392"}]},"4634":{"script_id":"4634","0":"4634","script_name":"NumUtils","1":"NumUtils","script_type":"utility","2":"utility","summary":"calculator with regex support","3":"calculator with regex support","description":"https:\/\/github.com\/BimbaLaszlo\/vim-numutils\r\n\r\nDid you ever want to manipulate a lot of data in text files? Add an offset\r\nto the axes in G-code, calculate the finances, or just renumber the\r\nchapters in the table of contents? With this plugin you can do the\r\ncalculations with regular expression support!\r\n\r\nPlease feel free to send me a mail if you have a good idea, or found a\r\nbug. If you think the plugin does something else that you want, send me\r\nthe lines to manipulate, the task that the plugin should do and the\r\ncommand that you used for, and i try to find and fix the bug.\r\n\r\nEXAMPLES\r\n\r\nNumUtilsAdd, NumUtilsSub, NumUtilsMul, NumUtilsDiv\r\n\r\nWith the built-in commands you can do the basic stuff: addition,\r\nsubtraction, multiplication and division. By default the commands\r\nwill be called on the line where the cursor stays, but you can use\r\n:range, :global, or linewise-visual to give a range as you do\r\nwhen you using :subtitute for example.\r\n\r\nA basic usage is for example add 10 to every number prefixed by X on this\r\nline:\r\n\r\n    X123 Y456 Z789 X100\r\n\r\nTo do it, call this:\r\n\r\n:NumUtilsAdd 10, 'X'\r\n\r\n... and you will get this:\r\n\r\n    X133 Y456 Z789 X110\r\n\r\nAnother example (add 2 to the number after star_ and to the number after\r\nanother number):\r\n\r\n    .star_10 {\r\n        background: url(stars.png) no-repeat 0 0;\r\n    }\r\n\r\n:NumUtilsAdd 2, 'star_!NUM!', ':NUM: !NUM!;$'\r\n\r\n    .star_12 {\r\n        background: url(stars.png) no-repeat 0 2;\r\n    }\r\n\r\nThere is another useful feature (add first and second submatch to value of\r\n!NUM!):\r\n\r\n    100|20|3\r\n\r\n:NumUtilsAdd [1,2], '\\(:NUM:\\)|\\(:NUM:\\)|!NUM!'\r\n\r\n    100|20|123","4":"https:\/\/github.com\/BimbaLaszlo\/vim-numutils\r\n\r\nDid you ever want to manipulate a lot of data in text files? Add an offset\r\nto the axes in G-code, calculate the finances, or just renumber the\r\nchapters in the table of contents? With this plugin you can do the\r\ncalculations with regular expression support!\r\n\r\nPlease feel free to send me a mail if you have a good idea, or found a\r\nbug. If you think the plugin does something else that you want, send me\r\nthe lines to manipulate, the task that the plugin should do and the\r\ncommand that you used for, and i try to find and fix the bug.\r\n\r\nEXAMPLES\r\n\r\nNumUtilsAdd, NumUtilsSub, NumUtilsMul, NumUtilsDiv\r\n\r\nWith the built-in commands you can do the basic stuff: addition,\r\nsubtraction, multiplication and division. By default the commands\r\nwill be called on the line where the cursor stays, but you can use\r\n:range, :global, or linewise-visual to give a range as you do\r\nwhen you using :subtitute for example.\r\n\r\nA basic usage is for example add 10 to every number prefixed by X on this\r\nline:\r\n\r\n    X123 Y456 Z789 X100\r\n\r\nTo do it, call this:\r\n\r\n:NumUtilsAdd 10, 'X'\r\n\r\n... and you will get this:\r\n\r\n    X133 Y456 Z789 X110\r\n\r\nAnother example (add 2 to the number after star_ and to the number after\r\nanother number):\r\n\r\n    .star_10 {\r\n        background: url(stars.png) no-repeat 0 0;\r\n    }\r\n\r\n:NumUtilsAdd 2, 'star_!NUM!', ':NUM: !NUM!;$'\r\n\r\n    .star_12 {\r\n        background: url(stars.png) no-repeat 0 2;\r\n    }\r\n\r\nThere is another useful feature (add first and second submatch to value of\r\n!NUM!):\r\n\r\n    100|20|3\r\n\r\n:NumUtilsAdd [1,2], '\\(:NUM:\\)|\\(:NUM:\\)|!NUM!'\r\n\r\n    100|20|123","install_details":"Open in vim then run\r\n:so %\r\n\r\n... or use Vundle:\r\n\r\nAdd these lines to your .vimrc after 'call vundle#rc()':\r\n\r\nPlugin 'bimbalaszlo\/vim-numutils'\r\n\r\nOpen vim again, then call ':PluginInstall'\r\n\r\nPlease rate if you using it!","5":"Open in vim then run\r\n:so %\r\n\r\n... or use Vundle:\r\n\r\nAdd these lines to your .vimrc after 'call vundle#rc()':\r\n\r\nPlugin 'bimbalaszlo\/vim-numutils'\r\n\r\nOpen vim again, then call ':PluginInstall'\r\n\r\nPlease rate if you using it!","first_name":"Laszlo","6":"Laszlo","last_name":"Bimba","7":"Bimba","releases":[{"0":"4634","vim_version":"7.3","1":"7.3","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"NumUtils.vmb","4":"NumUtils.vmb","src_id":"20428","5":"20428","creation_date":"1372167521","6":"1372167521"}]},"4633":{"script_id":"4633","0":"4633","script_name":"robo","1":"robo","script_type":"utility","2":"utility","summary":"A vim plugin for Android development.","3":"A vim plugin for Android development.","description":"Robo helps Android development by doing little things like:\r\n\r\nInserting missing imports,\r\nJumping to the manifest file,\r\nJumping to an activity from a list of available activities,\r\nAdding activities (both the .java file and the entry in the manifest),\r\nStarting an emulator.\r\n\r\nDocumentation\r\n-------------------\r\nIn vim :h robo\r\nor at https:\/\/bitbucket.org\/ercax\/robo .","4":"Robo helps Android development by doing little things like:\r\n\r\nInserting missing imports,\r\nJumping to the manifest file,\r\nJumping to an activity from a list of available activities,\r\nAdding activities (both the .java file and the entry in the manifest),\r\nStarting an emulator.\r\n\r\nDocumentation\r\n-------------------\r\nIn vim :h robo\r\nor at https:\/\/bitbucket.org\/ercax\/robo .","install_details":"Messy way: Unzip the robo.zip into your .vim folder.\r\nNice way: Use Pathogen a something similar plugin manager for Vim","5":"Messy way: Unzip the robo.zip into your .vim folder.\r\nNice way: Use Pathogen a something similar plugin manager for Vim","first_name":"Ercan","6":"Ercan","last_name":"Erden","7":"Erden","releases":[{"0":"4633","vim_version":"7.3","1":"7.3","script_version":"1","2":"1","version_comment":"Initial upload","3":"Initial upload","package":"robo.zip","4":"robo.zip","src_id":"20427","5":"20427","creation_date":"1372136242","6":"1372136242"}]},"4632":{"script_id":"4632","0":"4632","script_name":"tjs.vim","1":"tjs.vim","script_type":"syntax","2":"syntax","summary":"syntax file for kirikiri2 tjs script","3":"syntax file for kirikiri2 tjs script","description":"http:\/\/github.com\/Aixile\/tjs.vim\r\n\r\n吉里吉里２　tjsスクリプトのsyntax fileです。","4":"http:\/\/github.com\/Aixile\/tjs.vim\r\n\r\n吉里吉里２　tjsスクリプトのsyntax fileです。","install_details":"このファイルをsyntaxフォルダーにコビーした後、\"au BufNewFile,BufRead *.tjs set filetype=tjs\"をvimrcに追加してください。","5":"このファイルをsyntaxフォルダーにコビーした後、\"au BufNewFile,BufRead *.tjs set filetype=tjs\"をvimrcに追加してください。","first_name":"Amane","6":"Amane","last_name":"Nagatsuki","7":"Nagatsuki","releases":[{"0":"4632","vim_version":"7.0","1":"7.0","script_version":"1.0.1","2":"1.0.1","version_comment":"Fix Oct\/Bin Floats","3":"Fix Oct\/Bin Floats","package":"tjs.vim","4":"tjs.vim","src_id":"20413","5":"20413","creation_date":"1372056320","6":"1372056320"}]},"4631":{"script_id":"4631","0":"4631","script_name":"vim-github-comment","1":"vim-github-comment","script_type":"utility","2":"utility","summary":"Comment on GitHub straight from within Vim.","3":"Comment on GitHub straight from within Vim.","description":"You can find the repository on GitHub: https:\/\/github.com\/mmozuras\/vim-github-comment","4":"You can find the repository on GitHub: https:\/\/github.com\/mmozuras\/vim-github-comment","install_details":"Add the following into your ~\/.vimrc\r\n\r\n  let g:github_user = 'mmozuras'","5":"Add the following into your ~\/.vimrc\r\n\r\n  let g:github_user = 'mmozuras'","first_name":"Mindaugas","6":"Mindaugas","last_name":"Moz\u016bras","7":"Mozūras","releases":[{"0":"4631","vim_version":"7.0","1":"7.0","script_version":"0.0.4","2":"0.0.4","version_comment":"Support for github.user section in .gitconfig","3":"Support for github.user section in .gitconfig","package":"vim-github-comment.zip","4":"vim-github-comment.zip","src_id":"22857","5":"22857","creation_date":"1422817709","6":"1422817709"},{"0":"4631","vim_version":"7.0","1":"7.0","script_version":"0.0.3","2":"0.0.3","version_comment":"Support for GitHub two-factor authentication","3":"Support for GitHub two-factor authentication","package":"vim-github-comment.zip","4":"vim-github-comment.zip","src_id":"22451","5":"22451","creation_date":"1411414103","6":"1411414103"},{"0":"4631","vim_version":"7.0","1":"7.0","script_version":"0.0.2","2":"0.0.2","version_comment":"Comments now go inline and there's an optional ability to open browser after comment.","3":"Comments now go inline and there's an optional ability to open browser after comment.","package":"vim-github-comment.zip","4":"vim-github-comment.zip","src_id":"20415","5":"20415","creation_date":"1372061134","6":"1372061134"},{"0":"4631","vim_version":"7.0","1":"7.0","script_version":"0.0.1","2":"0.0.1","version_comment":"Initial upload","3":"Initial upload","package":"vim-github-comment.zip","4":"vim-github-comment.zip","src_id":"20409","5":"20409","creation_date":"1372000618","6":"1372000618"}]},"4630":{"script_id":"4630","0":"4630","script_name":"vim-addon-errorformats","1":"vim-addon-errorformats","script_type":"utility","2":"utility","summary":"error-formats only","3":"error-formats only","description":"Vim has the :compiler command built in. However sometimes you only want one or more error formats setup. That's what this plugin is about: It allows you to\r\n\r\n:Errorformat ocaml-simple ruby\r\nwhich will set 'errorformat' to ocmal-simple then amend ruby error format description.\r\n\r\nThis is useful if you build an ocaml project using the rake build system which is implemented in ruby","4":"Vim has the :compiler command built in. However sometimes you only want one or more error formats setup. That's what this plugin is about: It allows you to\r\n\r\n:Errorformat ocaml-simple ruby\r\nwhich will set 'errorformat' to ocmal-simple then amend ruby error format description.\r\n\r\nThis is useful if you build an ocaml project using the rake build system which is implemented in ruby","install_details":"","5":"","first_name":"Marc","6":"Marc","last_name":"Weber","7":"Weber","releases":[{"0":"4630","vim_version":"7.0","1":"7.0","script_version":"0.0","2":"0.0","version_comment":"Initial upload","3":"Initial upload","package":"install-info.txt","4":"install-info.txt","src_id":"20408","5":"20408","creation_date":"1371993014","6":"1371993014"}]},"4629":{"script_id":"4629","0":"4629","script_name":"LGS","1":"LGS","script_type":"utility","2":"utility","summary":"Laravel 4 Generators interface.","3":"Laravel 4 Generators interface.","description":"Adds integration with Laravel 4 Generator bundle through LG command allowing user to generate various entities w\/o leaving VIM. Convinient navigation through generated\/updated files included. This is a very early release, please file bugs if you find any.\r\n\r\nGitHub repo: https:\/\/github.com\/naquad\/lgs.vim\r\n\r\nLGS.vim provides one single command for invoking generators: LG\r\n\r\nExamples:\r\n\r\n\\\\\\\" Generates NewModel\r\nLG model NewModel\r\n\r\n\\\\\\\" Generates controller Controller\r\nLG controller MyController\r\n\r\n\\\\\\\" Will insert form for model Model into current buffer at cursor position\r\nLG form NewModel\r\n\r\n\\\\\\\" You can also specify options for generators\r\n\r\nLG form --method=create --html=ul ModelName\r\n\r\n\\\\\\\" Syntax with = is supported too\r\nLG controller --path=\/path\/to\/template ControllerName\r\n\r\nSee documentation for more details.","4":"Adds integration with Laravel 4 Generator bundle through LG command allowing user to generate various entities w\/o leaving VIM. Convinient navigation through generated\/updated files included. This is a very early release, please file bugs if you find any.\r\n\r\nGitHub repo: https:\/\/github.com\/naquad\/lgs.vim\r\n\r\nLGS.vim provides one single command for invoking generators: LG\r\n\r\nExamples:\r\n\r\n\\\\\\\" Generates NewModel\r\nLG model NewModel\r\n\r\n\\\\\\\" Generates controller Controller\r\nLG controller MyController\r\n\r\n\\\\\\\" Will insert form for model Model into current buffer at cursor position\r\nLG form NewModel\r\n\r\n\\\\\\\" You can also specify options for generators\r\n\r\nLG form --method=create --html=ul ModelName\r\n\r\n\\\\\\\" Syntax with = is supported too\r\nLG controller --path=\/path\/to\/template ControllerName\r\n\r\nSee documentation for more details.","install_details":"","5":"","first_name":"daniel","6":"daniel","last_name":"fort","7":"fort","releases":[{"0":"4629","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"lgs.zip","4":"lgs.zip","src_id":"20402","5":"20402","creation_date":"1371940638","6":"1371940638"}]},"4628":{"script_id":"4628","0":"4628","script_name":"bats.vim","1":"bats.vim","script_type":"syntax","2":"syntax","summary":"Syntax highlighting for Bats - Bash Automated Testing System","3":"Syntax highlighting for Bats - Bash Automated Testing System","description":"Extends the built in shell highlighting (sh.vim) for Bats - Bash Automated Testing System.\r\n\r\nPlease see project page for more information or to report issues: \r\nhttps:\/\/github.com\/rosstimson\/bats.vim\r\n\r\nFor more information on Bats please see:\r\nhttps:\/\/github.com\/sstephenson\/bats","4":"Extends the built in shell highlighting (sh.vim) for Bats - Bash Automated Testing System.\r\n\r\nPlease see project page for more information or to report issues: \r\nhttps:\/\/github.com\/rosstimson\/bats.vim\r\n\r\nFor more information on Bats please see:\r\nhttps:\/\/github.com\/sstephenson\/bats","install_details":"Extract into ~\/.vim or use Pathogen \/ Vundle (recommended).","5":"Extract into ~\/.vim or use Pathogen \/ Vundle (recommended).","first_name":"Ross","6":"Ross","last_name":"Timson","7":"Timson","releases":[{"0":"4628","vim_version":"7.0","1":"7.0","script_version":"0.1.0","2":"0.1.0","version_comment":"Initial upload","3":"Initial upload","package":"bats.tar.gz","4":"bats.tar.gz","src_id":"20400","5":"20400","creation_date":"1371922140","6":"1371922140"}]},"4627":{"script_id":"4627","0":"4627","script_name":"auto tags gen","1":"auto tags gen","script_type":"utility","2":"utility","summary":"Plugin for creating tags automatically (C\/C++)","3":"Plugin for creating tags automatically (C\/C++)","description":"Get the latest version from GitHub: https:\/\/github.com\/Pinaki82\/auto-tags-gen.git\r\n\r\nPlugin for creating tags with ctags in the current working directory of the currently opened buffer (file), automatically, when you save your file.\r\n\r\nThis plugin works with C\/C++ files only.\r\n\r\nWorks in the current working directory. It can include sub-directories as well. You can generate tags files automatically for easy access through Omni completion, and facilitate the plugins those that depend on a tags file.\r\n\r\nYou can even create tags file in any directory without saving a file.\r\n\r\nFor example: code_complete.vim (by Mingbai),\r\n             echofunc.vim (by Mingbai), plugins relies on a\r\n             tags file in the working directory\r\n             and the include directories added to vim's search list.\r\n\r\nAll of this is specified within a simple text file based plugin script (auto_tags_gen.vim) with a few global variables and a shared library (auto_tag_gen.dll and libauto_tag_gen.so on Linux).\r\n\r\nWritten For Vim version 7.4. May work with older versions as well as the future releases also.\r\n\r\n    Tested with Vim 32-bit on Windows XP\/7 32-bit, Windows 7 64-bit (vim 32-bit),\r\n    may work with Vim 64-bit on Windows 64-bit.\r\n    Now it works on Linux. Tested in ubuntu 13.04 (Gvim from its repository).\r\n\r\n\r\n\r\nYou must set 'nocompatible' in your _vimrc file to use this plugin. You can stop the plugin from being loaded by setting the\r\n\r\n\"loaded_auto_tag_generator\" variable:\r\n\r\n\t:let loaded_auto_tag_generator = 0\r\n\r\nin your 'vimrc' file.\r\n\r\nVersion 0.00.07-win32 can load option no. at vimstartup.\r\nYou can do this by putting option no. 0\/1\/2\/3\/4 like:\r\n\r\n :let g:startuptrigger = 1\r\n \r\nin your vimrc file.\r\n\r\nYou can also put these lines for your convenience:\r\n\r\n\r\nfiletype on\r\nfiletype plugin on\r\nset number\r\nset laststatus=2\r\n:set timeout timeoutlen=4500 \"   ttimeoutlen=100 \"  default settings -1 not harmed under comment\r\nset history=100 \" tons of command-line history. Can be used with up-down arrow key\r\n","4":"Get the latest version from GitHub: https:\/\/github.com\/Pinaki82\/auto-tags-gen.git\r\n\r\nPlugin for creating tags with ctags in the current working directory of the currently opened buffer (file), automatically, when you save your file.\r\n\r\nThis plugin works with C\/C++ files only.\r\n\r\nWorks in the current working directory. It can include sub-directories as well. You can generate tags files automatically for easy access through Omni completion, and facilitate the plugins those that depend on a tags file.\r\n\r\nYou can even create tags file in any directory without saving a file.\r\n\r\nFor example: code_complete.vim (by Mingbai),\r\n             echofunc.vim (by Mingbai), plugins relies on a\r\n             tags file in the working directory\r\n             and the include directories added to vim's search list.\r\n\r\nAll of this is specified within a simple text file based plugin script (auto_tags_gen.vim) with a few global variables and a shared library (auto_tag_gen.dll and libauto_tag_gen.so on Linux).\r\n\r\nWritten For Vim version 7.4. May work with older versions as well as the future releases also.\r\n\r\n    Tested with Vim 32-bit on Windows XP\/7 32-bit, Windows 7 64-bit (vim 32-bit),\r\n    may work with Vim 64-bit on Windows 64-bit.\r\n    Now it works on Linux. Tested in ubuntu 13.04 (Gvim from its repository).\r\n\r\n\r\n\r\nYou must set 'nocompatible' in your _vimrc file to use this plugin. You can stop the plugin from being loaded by setting the\r\n\r\n\"loaded_auto_tag_generator\" variable:\r\n\r\n\t:let loaded_auto_tag_generator = 0\r\n\r\nin your 'vimrc' file.\r\n\r\nVersion 0.00.07-win32 can load option no. at vimstartup.\r\nYou can do this by putting option no. 0\/1\/2\/3\/4 like:\r\n\r\n :let g:startuptrigger = 1\r\n \r\nin your vimrc file.\r\n\r\nYou can also put these lines for your convenience:\r\n\r\n\r\nfiletype on\r\nfiletype plugin on\r\nset number\r\nset laststatus=2\r\n:set timeout timeoutlen=4500 \"   ttimeoutlen=100 \"  default settings -1 not harmed under comment\r\nset history=100 \" tons of command-line history. Can be used with up-down arrow key\r\n","install_details":"Installation:\r\nDownload Exuberant ctags from\r\n http:\/\/ctags.sourceforge.net.\r\nPut ctags.exe into C:\\WINDOWS\\system32 (for Windows XP only)\r\n\r\nor, create a folder for ctags and finally add this folder to path, by r-clicking at My Computer -> Properties -> Advanced -> Environment Variables -> System Variables -> Path. (XP)\r\n\r\nor,\r\nr-clicking at Computer -> Advanced System Settings\r\n-> System Properties\r\n-> Advanced tab -> Environment Variables\r\n-> System Variables -> Path. (Win7)\r\n\r\nor,\r\n\r\nr-clicking at \"This PC\" -> Advanced System Settings\r\n-> System Properties\r\n-> Advanced tab -> Environment Variables\r\n-> System Variables -> Path. (Win10)\r\n\r\nUbuntu users should download ctags from the repository.\r\n\r\nDownload the code in a ZIP achieve from the main branch and extract the file \"auto-tags-gen-main.zip\" to any location\r\nof your preference. This contains source code for the shared library and the\r\nmakefiles for different targets and compilers.\r\n\r\nAt this time, it supports 3 compilers on Windows:- MinGW, tiny C, Visual Studio.\r\nThis project relies on bakefile (http:\/\/www.bakefile.org). The project also includes bakefile scripts. If you want to create your own makefile then you can also use it but it is not required to build the project, since it already contains the required makefiles. The makefiles have been created using bakefile.\r\n\r\nExtract \"auto_tag_gen.zip\" and put the fiiles in their respective\r\nlocations, e.g. 'auto_tags_gen.txt' to \"%userprofile%\\vimefiles\\doc\", 'auto_tag_gen.dll' and 'auto_tags_gen.vim' to \"%userprofile%\\vimefiles\\plugin\"\r\n\r\nor,\r\n\r\nIn Ubuntu Linux, extract and enter the directory from the terminal where the Makefile is contained, type 'make'. Now copy the file 'auto_tags_gen_linux.vim' into \"~\/.vim\/plugin\" and 'libauto_tag_gen.so' into repective plugin directory.\r\n\r\nFire up gVim and at the Vim command-line do (windows):\r\n\r\n:helptags $VIMRUNTIME\/doc\r\n\r\nthen,\r\n\r\n:h auto_tags_gen\r\n\r\nor, in Ubuntu Linux,\r\n\r\n:helptags $HOME\/.vim\/doc\r\n\r\nRead the documentation carefully.\r\n\r\nNOTE:: (Improvement):: From Version 0.0.06, this plugin no more kills any other\r\nconsole window on Microsoft Windows Operating Systems. It kills only the previously running ctags.exe processes just to ensure you have the latest updated tags.\r\nYou can now run any other command-line jobs such as compilation etc.\r\nThe cmd.exe won't be terminated. Nothing will be harmed.\r\n\r\nCAUTION:: On Windows, older version of this plugin (prior to Version 0.0.06)\r\nused to kill all the running 'cmd.exe' at the background to prevent parallel ctags processes targeting the same 'tags'. This had some obvious advantages but a precaution is necessary. Means if you want to do other tasks which depend on the command-line via 'cmd.exe' such as compilation etc., then do not use any older version before 0.0.06, as it would interrupt your task by killing it midway. Older versions do not work with the console version of Vim, and you should not try to integrate any older version with the console version of Vim as it would kill Vim itself by killing the 'cmd.exe'. Only use GVim. Better use version 0.0.06 when you already have the option to upgrade.\r\n\r\nOn Linux, you don't have to worry about it even with the older versions.\r\n\r\n\r\nGitHub repository of this plugin contains the latest codebase.\r\n\r\n","5":"Installation:\r\nDownload Exuberant ctags from\r\n http:\/\/ctags.sourceforge.net.\r\nPut ctags.exe into C:\\WINDOWS\\system32 (for Windows XP only)\r\n\r\nor, create a folder for ctags and finally add this folder to path, by r-clicking at My Computer -> Properties -> Advanced -> Environment Variables -> System Variables -> Path. (XP)\r\n\r\nor,\r\nr-clicking at Computer -> Advanced System Settings\r\n-> System Properties\r\n-> Advanced tab -> Environment Variables\r\n-> System Variables -> Path. (Win7)\r\n\r\nor,\r\n\r\nr-clicking at \"This PC\" -> Advanced System Settings\r\n-> System Properties\r\n-> Advanced tab -> Environment Variables\r\n-> System Variables -> Path. (Win10)\r\n\r\nUbuntu users should download ctags from the repository.\r\n\r\nDownload the code in a ZIP achieve from the main branch and extract the file \"auto-tags-gen-main.zip\" to any location\r\nof your preference. This contains source code for the shared library and the\r\nmakefiles for different targets and compilers.\r\n\r\nAt this time, it supports 3 compilers on Windows:- MinGW, tiny C, Visual Studio.\r\nThis project relies on bakefile (http:\/\/www.bakefile.org). The project also includes bakefile scripts. If you want to create your own makefile then you can also use it but it is not required to build the project, since it already contains the required makefiles. The makefiles have been created using bakefile.\r\n\r\nExtract \"auto_tag_gen.zip\" and put the fiiles in their respective\r\nlocations, e.g. 'auto_tags_gen.txt' to \"%userprofile%\\vimefiles\\doc\", 'auto_tag_gen.dll' and 'auto_tags_gen.vim' to \"%userprofile%\\vimefiles\\plugin\"\r\n\r\nor,\r\n\r\nIn Ubuntu Linux, extract and enter the directory from the terminal where the Makefile is contained, type 'make'. Now copy the file 'auto_tags_gen_linux.vim' into \"~\/.vim\/plugin\" and 'libauto_tag_gen.so' into repective plugin directory.\r\n\r\nFire up gVim and at the Vim command-line do (windows):\r\n\r\n:helptags $VIMRUNTIME\/doc\r\n\r\nthen,\r\n\r\n:h auto_tags_gen\r\n\r\nor, in Ubuntu Linux,\r\n\r\n:helptags $HOME\/.vim\/doc\r\n\r\nRead the documentation carefully.\r\n\r\nNOTE:: (Improvement):: From Version 0.0.06, this plugin no more kills any other\r\nconsole window on Microsoft Windows Operating Systems. It kills only the previously running ctags.exe processes just to ensure you have the latest updated tags.\r\nYou can now run any other command-line jobs such as compilation etc.\r\nThe cmd.exe won't be terminated. Nothing will be harmed.\r\n\r\nCAUTION:: On Windows, older version of this plugin (prior to Version 0.0.06)\r\nused to kill all the running 'cmd.exe' at the background to prevent parallel ctags processes targeting the same 'tags'. This had some obvious advantages but a precaution is necessary. Means if you want to do other tasks which depend on the command-line via 'cmd.exe' such as compilation etc., then do not use any older version before 0.0.06, as it would interrupt your task by killing it midway. Older versions do not work with the console version of Vim, and you should not try to integrate any older version with the console version of Vim as it would kill Vim itself by killing the 'cmd.exe'. Only use GVim. Better use version 0.0.06 when you already have the option to upgrade.\r\n\r\nOn Linux, you don't have to worry about it even with the older versions.\r\n\r\n\r\nGitHub repository of this plugin contains the latest codebase.\r\n\r\n","first_name":"Pinaki Sekhar","6":"Pinaki Sekhar","last_name":"Gupta","7":"Gupta","releases":[{"0":"4627","vim_version":"7.3","1":"7.3","script_version":"0.00.08","2":"0.00.08","version_comment":"This version no more contains different script version for different OS.\r\nInstead os-specific features are merged into one vim script.","3":"This version no more contains different script version for different OS.\r\nInstead os-specific features are merged into one vim script.","package":"auto_tag_gen_v0.00.08win32.7z","4":"auto_tag_gen_v0.00.08win32.7z","src_id":"24020","5":"24020","creation_date":"1455785553","6":"1455785553"},{"0":"4627","vim_version":"7.3","1":"7.3","script_version":"0.00.07","2":"0.00.07","version_comment":"This version can load user specified option number at vim startup.\r\nImproved C++ specific ctags commands.\r\nUser can do this by putting option no. 0\/1\/2\/3\/4 like:\r\nlet g:startuptrigger = 1\r\nin vimrc.","3":"This version can load user specified option number at vim startup.\r\nImproved C++ specific ctags commands.\r\nUser can do this by putting option no. 0\/1\/2\/3\/4 like:\r\nlet g:startuptrigger = 1\r\nin vimrc.","package":"auto_tag_gen_v0.00.07win32.7z","4":"auto_tag_gen_v0.00.07win32.7z","src_id":"24013","5":"24013","creation_date":"1455564908","6":"1455564908"},{"0":"4627","vim_version":"7.3","1":"7.3","script_version":"0.00.06","2":"0.00.06","version_comment":"In this version while saving file (Windows OS), only ctags.exe is\r\nterminated, other command-line Windows are not affected.","3":"In this version while saving file (Windows OS), only ctags.exe is\r\nterminated, other command-line Windows are not affected.","package":"auto_tag_gen_v0.00.06win32.zip","4":"auto_tag_gen_v0.00.06win32.zip","src_id":"23830","5":"23830","creation_date":"1451324914","6":"1451324914"},{"0":"4627","vim_version":"7.3","1":"7.3","script_version":"0.00.05","2":"0.00.05","version_comment":"Support for Arduino *.ino and *.pde files included.","3":"Support for Arduino *.ino and *.pde files included.","package":"auto_tag_gen_v0.00.05win32.zip","4":"auto_tag_gen_v0.00.05win32.zip","src_id":"23492","5":"23492","creation_date":"1438156979","6":"1438156979"},{"0":"4627","vim_version":"7.3","1":"7.3","script_version":"0.00.04","2":"0.00.04","version_comment":"This version supports Linux operating system (Makefile included). On Windows it does not starts multiple ctags process, just creates one process and when you re-save your file, it kills previous process and starts a new process. So no longer you have to wait just to finish the earlier process, it tackles everything automatically.","3":"This version supports Linux operating system (Makefile included). On Windows it does not starts multiple ctags process, just creates one process and when you re-save your file, it kills previous process and starts a new process. So no longer you have to wait just to finish the earlier process, it tackles everything automatically.","package":"auto_tag_gen_v0.00.04win32.7z","4":"auto_tag_gen_v0.00.04win32.7z","src_id":"21443","5":"21443","creation_date":"1391791336","6":"1391791336"},{"0":"4627","vim_version":"7.0","1":"7.0","script_version":"0.00.03","2":"0.00.03","version_comment":"Better compatibility with Vim 7.4.\r\nMinor bug-fix in the plug-in section.","3":"Better compatibility with Vim 7.4.\r\nMinor bug-fix in the plug-in section.","package":"auto_tag_gen_v0.00.03win32.7z","4":"auto_tag_gen_v0.00.03win32.7z","src_id":"20780","5":"20780","creation_date":"1378866070","6":"1378866070"},{"0":"4627","vim_version":"7.3","1":"7.3","script_version":"0.00.02","2":"0.00.02","version_comment":"Documentations updated.\r\nPlug-in optimized.","3":"Documentations updated.\r\nPlug-in optimized.","package":"auto_tag_gen_v0.00.02win32.7z","4":"auto_tag_gen_v0.00.02win32.7z","src_id":"20416","5":"20416","creation_date":"1372063358","6":"1372063358"}]},"4626":{"script_id":"4626","0":"4626","script_name":"tex.vim","1":"tex.vim","script_type":"syntax","2":"syntax","summary":"Every symbol defined by the unicode-math package","3":"Every symbol defined by the unicode-math package","description":"A tex.vim syntax file for Vim with a mapping of all commands defined by the unicode-math package to the symbols they stand for to be used in editing LaTeX source code.\r\n\r\nSome further details you can find here (about the syntax-file): \r\nhttp:\/\/chbrauner.blogspot.de\/2013\/06\/vims-conceal-feature-and-syntax-file.html\r\nand here (about the conceal-feature and latex):\r\nhttp:\/\/b4winckler.wordpress.com\/2010\/08\/07\/using-the-conceal-vim-feature-with-latex\/","4":"A tex.vim syntax file for Vim with a mapping of all commands defined by the unicode-math package to the symbols they stand for to be used in editing LaTeX source code.\r\n\r\nSome further details you can find here (about the syntax-file): \r\nhttp:\/\/chbrauner.blogspot.de\/2013\/06\/vims-conceal-feature-and-syntax-file.html\r\nand here (about the conceal-feature and latex):\r\nhttp:\/\/b4winckler.wordpress.com\/2010\/08\/07\/using-the-conceal-vim-feature-with-latex\/","install_details":"The archive contains two files which give you two mutually exclusive options:\r\nEither\r\n(a) tex.vim: This file should be put in your local \/home\/username\/.vim\/after\/syntax\/ folder (only focusing on Linux here) additionally to the standard tex.vim file shipped with Vim.\r\nor\r\n(b) tex.vim~: This file should be renamed to tex.vim and replace the standard tex.vim file shipped with Vim.","5":"The archive contains two files which give you two mutually exclusive options:\r\nEither\r\n(a) tex.vim: This file should be put in your local \/home\/username\/.vim\/after\/syntax\/ folder (only focusing on Linux here) additionally to the standard tex.vim file shipped with Vim.\r\nor\r\n(b) tex.vim~: This file should be renamed to tex.vim and replace the standard tex.vim file shipped with Vim.","first_name":"Christian","6":"Christian","last_name":"Brauner","7":"Brauner","releases":[{"0":"4626","vim_version":"7.0","1":"7.0","script_version":"2","2":"2","version_comment":"symbols adapted to version July 2014 of unicode-math","3":"symbols adapted to version July 2014 of unicode-math","package":"tex.vim","4":"tex.vim","src_id":"22730","5":"22730","creation_date":"1419423284","6":"1419423284"},{"0":"4626","vim_version":"7.3","1":"7.3","script_version":"1","2":"1","version_comment":"The archive contains two files which give you two mutually exclusive options:\r\nEither\r\n(a) tex.vim: This file should be put in your local \/home\/username\/.vim\/after\/syntax\/ folder (only focusing on Linux here) additionally to the standard tex.vim file shipped with Vim.\r\nor\r\n(b)tex.vim~: This file should be renamed to tex.vim and replace the standard tex.vim file shipped with Vim.","3":"The archive contains two files which give you two mutually exclusive options:\r\nEither\r\n(a) tex.vim: This file should be put in your local \/home\/username\/.vim\/after\/syntax\/ folder (only focusing on Linux here) additionally to the standard tex.vim file shipped with Vim.\r\nor\r\n(b)tex.vim~: This file should be renamed to tex.vim and replace the standard tex.vim file shipped with Vim.","package":"vim.tar","4":"vim.tar","src_id":"20404","5":"20404","creation_date":"1371945583","6":"1371945583"},{"0":"4626","vim_version":"7.0","1":"7.0","script_version":"1","2":"1","version_comment":"Initial upload","3":"Initial upload","package":"tex.vim","4":"tex.vim","src_id":"20387","5":"20387","creation_date":"1371850799","6":"1371850799"}]},"4624":{"script_id":"4624","0":"4624","script_name":"cisco.vim","1":"cisco.vim","script_type":"syntax","2":"syntax","summary":"Script to highlight cisco configuration files","3":"Script to highlight cisco configuration files","description":"This script will highlight some of the more common cisco configuration elements such as IP addresses and masks, router and configuration prompts, interface names, and a few other useful highlighting elements.  It also has syntax highlighting intended for use in Conqueterm, for those who might use that vim script to open a terminal in their vim buffer and apply syntax highlighting to it allowing them to highlight live router and switch login sessions.  There is highlighting to catch some common error conditions found in the output of \"show interface\" on most platforms, as well as interface up and down status.  It is far from complete, and more sections will be added in the future.","4":"This script will highlight some of the more common cisco configuration elements such as IP addresses and masks, router and configuration prompts, interface names, and a few other useful highlighting elements.  It also has syntax highlighting intended for use in Conqueterm, for those who might use that vim script to open a terminal in their vim buffer and apply syntax highlighting to it allowing them to highlight live router and switch login sessions.  There is highlighting to catch some common error conditions found in the output of \"show interface\" on most platforms, as well as interface up and down status.  It is far from complete, and more sections will be added in the future.","install_details":"Put it in the syntax folder of your .vim directory.","5":"Put it in the syntax folder of your .vim directory.","first_name":"John","6":"John","last_name":"Biederstedt","7":"Biederstedt","releases":[{"0":"4624","vim_version":"7.0","1":"7.0","script_version":".627","2":".627","version_comment":"Updated.","3":"Updated.","package":"cisco.vim","4":"cisco.vim","src_id":"24956","5":"24956","creation_date":"1486692327","6":"1486692327"},{"0":"4624","vim_version":"7.0","1":"7.0","script_version":".622","2":".622","version_comment":"Fix to switchport error highlighting, misc","3":"Fix to switchport error highlighting, misc","package":"cisco.vim","4":"cisco.vim","src_id":"20504","5":"20504","creation_date":"1373375007","6":"1373375007"}]},"4622":{"script_id":"4622","0":"4622","script_name":"muzzl.vim","1":"muzzl.vim","script_type":"color scheme","2":"color scheme","summary":"Tango colors with a torte scheme","3":"Tango colors with a torte scheme","description":"There are many color schemes for Vim that take their palette from the Tango Desktop Project.  What makes this one interesting is that it matches the colors to syntax in a way that mimics the torte theme that comes prepackaged with Vim.  If you've spent as much time staring at torte as I have you will welcome the familiarity of the colors coupled with the reduced eye strain of slightly lowered contrast.\r\n\r\nIt also adds a couple of definitions for console colors so if your terminal is using the Tango theme then you should hardly be able to tell gvim and vim apart...  Though I think this gvim cyan is better than the Tango theme that came packaged with my Terminal.  The Tango Desktop Project does not define a cyan so we have to improvise if we need one.\r\n\r\nNot only did I do the tweaking for this but I spent the last week or so staring at code in it and I'm not sure I'll ever need another color scheme.","4":"There are many color schemes for Vim that take their palette from the Tango Desktop Project.  What makes this one interesting is that it matches the colors to syntax in a way that mimics the torte theme that comes prepackaged with Vim.  If you've spent as much time staring at torte as I have you will welcome the familiarity of the colors coupled with the reduced eye strain of slightly lowered contrast.\r\n\r\nIt also adds a couple of definitions for console colors so if your terminal is using the Tango theme then you should hardly be able to tell gvim and vim apart...  Though I think this gvim cyan is better than the Tango theme that came packaged with my Terminal.  The Tango Desktop Project does not define a cyan so we have to improvise if we need one.\r\n\r\nNot only did I do the tweaking for this but I spent the last week or so staring at code in it and I'm not sure I'll ever need another color scheme.","install_details":"","5":"","first_name":"Joel","6":"Joel","last_name":"Muzzerall","7":"Muzzerall","releases":[{"0":"4622","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"muzzl.vim","4":"muzzl.vim","src_id":"20371","5":"20371","creation_date":"1371602810","6":"1371602810"}]},"4621":{"script_id":"4621","0":"4621","script_name":"wir_black","1":"wir_black","script_type":"color scheme","2":"color scheme","summary":"heavily modified ir_black theme for 255 terminals","3":"heavily modified ir_black theme for 255 terminals","description":"Heavily modified ir_black theme.\r\n\r\nCurrently only supports 255 color terminals, if you have one, you might have to add \"set t_Co=256\" to your .vimrc.\r\n\r\ngvim is not supported, original ir_black will be used for it.\r\n\r\nscreenshot: http:\/\/postimg.org\/image\/6jswxzy3l\/","4":"Heavily modified ir_black theme.\r\n\r\nCurrently only supports 255 color terminals, if you have one, you might have to add \"set t_Co=256\" to your .vimrc.\r\n\r\ngvim is not supported, original ir_black will be used for it.\r\n\r\nscreenshot: http:\/\/postimg.org\/image\/6jswxzy3l\/","install_details":"","5":"","first_name":"piotr","6":"piotr","last_name":"podusowski","7":"podusowski","releases":[{"0":"4621","vim_version":"6.0","1":"6.0","script_version":"1","2":"1","version_comment":"Initial upload","3":"Initial upload","package":"wir_black.vim","4":"wir_black.vim","src_id":"20370","5":"20370","creation_date":"1371589177","6":"1371589177"}]},"4620":{"script_id":"4620","0":"4620","script_name":"Luna","1":"Luna","script_type":"color scheme","2":"color scheme","summary":"Simple colorscheme created for fun and night usage","3":"Simple colorscheme created for fun and night usage","description":"This is simple colorscheme that was created for coding during night ! \r\n\r\nthe git repo is here: https:\/\/github.com\/Pychimp\/vim-luna \r\n\r\nGvim colorscheme is uploaded here, you can get the Console colorscheme from the above mentioned git repo","4":"This is simple colorscheme that was created for coding during night ! \r\n\r\nthe git repo is here: https:\/\/github.com\/Pychimp\/vim-luna \r\n\r\nGvim colorscheme is uploaded here, you can get the Console colorscheme from the above mentioned git repo","install_details":"Download and move to ~\/.vim\/colors\/ (or its equivalent in Windows)\r\n\r\nFor Pathogen (or Bundle) users: \r\n\r\nclone the repo into your bundle folder in your .vim directory","5":"Download and move to ~\/.vim\/colors\/ (or its equivalent in Windows)\r\n\r\nFor Pathogen (or Bundle) users: \r\n\r\nclone the repo into your bundle folder in your .vim directory","first_name":"Pratheek","6":"Pratheek","last_name":"","7":"","releases":[{"0":"4620","vim_version":"7.3","1":"7.3","script_version":"0.0.2","2":"0.0.2","version_comment":"Initial upload","3":"Initial upload","package":"luna.vim","4":"luna.vim","src_id":"20359","5":"20359","creation_date":"1371291927","6":"1371291927"}]},"4619":{"script_id":"4619","0":"4619","script_name":"K.vim","1":"K.vim","script_type":"utility","2":"utility","summary":"let you quickly run external command, and show the result in a scratch window.","3":"let you quickly run external command, and show the result in a scratch window.","description":"[Documentation](https:\/\/brookhong.github.io\/2014\/10\/22\/kvim.html)\r\n\r\n[文档](https:\/\/brookhong.github.io\/2014\/09\/28\/kvim-cn.html)\r\n\r\n[screencast](https:\/\/brookhong.github.io\/assets\/images\/k.gif)\r\n","4":"[Documentation](https:\/\/brookhong.github.io\/2014\/10\/22\/kvim.html)\r\n\r\n[文档](https:\/\/brookhong.github.io\/2014\/09\/28\/kvim-cn.html)\r\n\r\n[screencast](https:\/\/brookhong.github.io\/assets\/images\/k.gif)\r\n","install_details":"Just unzip the zip file to your VIM file path, usually to be ~\/.vim. \r\n\r\nor \r\n\r\nBundle 'brookhong\/k.vim'","5":"Just unzip the zip file to your VIM file path, usually to be ~\/.vim. \r\n\r\nor \r\n\r\nBundle 'brookhong\/k.vim'","first_name":"brook","6":"brook","last_name":"hong","7":"hong","releases":[{"0":"4619","vim_version":"7.2","1":"7.2","script_version":"0.3","2":"0.3","version_comment":":Ft <tab> to set filetype\r\nFor C\/Cpp\/Java: <leader>rc to compile, <leader>rx to run","3":":Ft <tab> to set filetype\r\nFor C\/Cpp\/Java: <leader>rc to compile, <leader>rx to run","package":"k.zip","4":"k.zip","src_id":"22556","5":"22556","creation_date":"1413989644","6":"1413989644"},{"0":"4619","vim_version":"7.2","1":"7.2","script_version":"0.2","2":"0.2","version_comment":"K.vim now evolves to be a plugin to let you quickly run external command, and show the result\r\nin a scratch window.\r\n\r\n1. press `<leader><leader>` to show explanation of word with call to an external\r\ncommand `kv`, https:\/\/github.com\/brookhong\/kv\r\n\r\n1. press `<space><leader>` to close the scratch window\r\n\r\n1. press `<leader>r` to run all scripts in a buffer\r\n\r\n1. press `<enter>` to run curren line.\r\n","3":"K.vim now evolves to be a plugin to let you quickly run external command, and show the result\r\nin a scratch window.\r\n\r\n1. press `<leader><leader>` to show explanation of word with call to an external\r\ncommand `kv`, https:\/\/github.com\/brookhong\/kv\r\n\r\n1. press `<space><leader>` to close the scratch window\r\n\r\n1. press `<leader>r` to run all scripts in a buffer\r\n\r\n1. press `<enter>` to run curren line.\r\n","package":"k.zip","4":"k.zip","src_id":"21813","5":"21813","creation_date":"1398262992","6":"1398262992"},{"0":"4619","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"k.zip","4":"k.zip","src_id":"20354","5":"20354","creation_date":"1371142305","6":"1371142305"}]},"4618":{"script_id":"4618","0":"4618","script_name":"kink.vim","1":"kink.vim","script_type":"ftplugin","2":"ftplugin","summary":"Vim Plugin for Kink Programming Language","3":"Vim Plugin for Kink Programming Language","description":"https:\/\/bitbucket.org\/kink\/kink.vim\r\n\r\nFiletype, syntax and indent plugins for the Kink Programming Language (https:\/\/bitbucket.org\/kink\/kink).","4":"https:\/\/bitbucket.org\/kink\/kink.vim\r\n\r\nFiletype, syntax and indent plugins for the Kink Programming Language (https:\/\/bitbucket.org\/kink\/kink).","install_details":"Open the file with Vim and execute \":source %\".","5":"Open the file with Vim and execute \":source %\".","first_name":"Taku","6":"Taku","last_name":"Miyakawa","7":"Miyakawa","releases":[{"0":"4618","vim_version":"7.0","1":"7.0","script_version":"1.0.11","2":"1.0.11","version_comment":"better handling for comments and strings","3":"better handling for comments and strings","package":"kink.vim-1.0.11.vba","4":"kink.vim-1.0.11.vba","src_id":"25073","5":"25073","creation_date":"1491985501","6":"1491985501"},{"0":"4618","vim_version":"7.0","1":"7.0","script_version":"1.0.10","2":"1.0.10","version_comment":"* fix indentation issues around backslashes.\r\n* improve syntax highlighting for identifiers.","3":"* fix indentation issues around backslashes.\r\n* improve syntax highlighting for identifiers.","package":"kink.vim-1.0.10.vba","4":"kink.vim-1.0.10.vba","src_id":"25068","5":"25068","creation_date":"1491753041","6":"1491753041"},{"0":"4618","vim_version":"7.0","1":"7.0","script_version":"1.0.9","2":"1.0.9","version_comment":"more robust indentation and syntax highlights.","3":"more robust indentation and syntax highlights.","package":"kink.vim-1.0.9.vba","4":"kink.vim-1.0.9.vba","src_id":"24949","5":"24949","creation_date":"1486288536","6":"1486288536"},{"0":"4618","vim_version":"7.0","1":"7.0","script_version":"1.0.7","2":"1.0.7","version_comment":"fixes a bug of in-string indentation","3":"fixes a bug of in-string indentation","package":"kink.vim-1.0.7.vba","4":"kink.vim-1.0.7.vba","src_id":"22558","5":"22558","creation_date":"1414033861","6":"1414033861"},{"0":"4618","vim_version":"7.0","1":"7.0","script_version":"1.0.6","2":"1.0.6","version_comment":"supports lisp style indenting","3":"supports lisp style indenting","package":"kink.vim-1.0.6.vba","4":"kink.vim-1.0.6.vba","src_id":"22538","5":"22538","creation_date":"1413604337","6":"1413604337"},{"0":"4618","vim_version":"7.0","1":"7.0","script_version":"1.0.4","2":"1.0.4","version_comment":"1. abolishes regex literals\r\n2. supports (*...*) and [*...*]","3":"1. abolishes regex literals\r\n2. supports (*...*) and [*...*]","package":"kink.vim-1.0.4.vba","4":"kink.vim-1.0.4.vba","src_id":"22521","5":"22521","creation_date":"1413100899","6":"1413100899"},{"0":"4618","vim_version":"7.0","1":"7.0","script_version":"1.0.3","2":"1.0.3","version_comment":"Syntax change: \"_xxx\" is now a noun.","3":"Syntax change: \"_xxx\" is now a noun.","package":"kink.vim-1.0.3.vba","4":"kink.vim-1.0.3.vba","src_id":"20887","5":"20887","creation_date":"1381039733","6":"1381039733"},{"0":"4618","vim_version":"7.0","1":"7.0","script_version":"1.0.2","2":"1.0.2","version_comment":"Minor refactoring.","3":"Minor refactoring.","package":"kink.vim-1.0.2.vba","4":"kink.vim-1.0.2.vba","src_id":"20352","5":"20352","creation_date":"1371131094","6":"1371131094"},{"0":"4618","vim_version":"7.0","1":"7.0","script_version":"1.0.1","2":"1.0.1","version_comment":"Uses \"setlocal filtetype=...\" instead of \"setfiletype ...\"\r\n\r\nThe latter has no effect when installed under bundle\/.","3":"Uses \"setlocal filtetype=...\" instead of \"setfiletype ...\"\r\n\r\nThe latter has no effect when installed under bundle\/.","package":"kink.vim-1.0.1.vba","4":"kink.vim-1.0.1.vba","src_id":"20351","5":"20351","creation_date":"1371130711","6":"1371130711"},{"0":"4618","vim_version":"7.0","1":"7.0","script_version":"1.0.0","2":"1.0.0","version_comment":"Initial upload","3":"Initial upload","package":"kink.vim-1.0.0.vba","4":"kink.vim-1.0.0.vba","src_id":"20339","5":"20339","creation_date":"1370993837","6":"1370993837"}]},"4617":{"script_id":"4617","0":"4617","script_name":"vim-cpp-enhanced-highlight","1":"vim-cpp-enhanced-highlight","script_type":"syntax","2":"syntax","summary":"Improved C++ syntax highlight","3":"Improved C++ syntax highlight","description":"This file contains additional syntax highlighting that I use for my C++11\r\ndevelopment in Vim. Compared to the standard syntax highlighting for C++ it\r\nadds highlighting of (user defined) functions and the containers and types\r\nin the standard library \/ boost.\r\n\r\nDevelopment is done at: http:\/\/github.com\/octol\/vim-cpp-enhanced-highlight\r\n\r\nBased on:\r\n---------\r\n\r\n- http:\/\/stackoverflow.com\/questions\/736701\/class-function-names-highlighting-in-vim\r\n- Scripts: vimscript #4293, vimscript #2224, vimscript #1640, vimscript #3064\r\n\r\n","4":"This file contains additional syntax highlighting that I use for my C++11\r\ndevelopment in Vim. Compared to the standard syntax highlighting for C++ it\r\nadds highlighting of (user defined) functions and the containers and types\r\nin the standard library \/ boost.\r\n\r\nDevelopment is done at: http:\/\/github.com\/octol\/vim-cpp-enhanced-highlight\r\n\r\nBased on:\r\n---------\r\n\r\n- http:\/\/stackoverflow.com\/questions\/736701\/class-function-names-highlighting-in-vim\r\n- Scripts: vimscript #4293, vimscript #2224, vimscript #1640, vimscript #3064\r\n\r\n","install_details":"Either copy the cpp.vim file to ~\/.vim\/after\/syntax\/cpp.vim\r\nor install using Vundle by adding\r\n\r\n    Bundle 'octol\/vim-cpp-enhanced-highlight'\r\n\r\nto your .vimrc file.\r\n","5":"Either copy the cpp.vim file to ~\/.vim\/after\/syntax\/cpp.vim\r\nor install using Vundle by adding\r\n\r\n    Bundle 'octol\/vim-cpp-enhanced-highlight'\r\n\r\nto your .vimrc file.\r\n","first_name":"Jon","6":"Jon","last_name":"Haggblad","7":"Haggblad","releases":[{"0":"4617","vim_version":"7.0","1":"7.0","script_version":"0.3","2":"0.3","version_comment":"C++14 and misc updates.","3":"C++14 and misc updates.","package":"vim-cpp-enhanced-highlight-0.3.tar.gz","4":"vim-cpp-enhanced-highlight-0.3.tar.gz","src_id":"21805","5":"21805","creation_date":"1398109072","6":"1398109072"},{"0":"4617","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"vim-cpp-enhanced-highlight-0.1.tar.gz","4":"vim-cpp-enhanced-highlight-0.1.tar.gz","src_id":"20330","5":"20330","creation_date":"1370813212","6":"1370813212"}]},"4616":{"script_id":"4616","0":"4616","script_name":"shootingstar","1":"shootingstar","script_type":"utility","2":"utility","summary":"Like the magic * but start matching at the cursor position","3":"Like the magic * but start matching at the cursor position","description":"* Given your cursor (|) is here: shoo|ting start\r\n*  Pressing \\* will search for the term ting if it's part of the word \\<shooting\\>\r\n*  In vim search syntax this is equivalent to: \/\\<shoo\\zsting\\>\r\n\r\nSupported keybindings\r\n* <Leader>* and <Leader># for searching forward\/backward for the exact word\r\n* <Leader>g* and <Leader>g# for searching forward\/backward without stopping at word boundaries\r\n\r\nWhy would I need that? Peronsally, I'm using the * often when I want to refactor code, e.g. change the name of a variable or function. Often I just want to change a certain part of the name and it would come very handy if the search would be able to place the cursor right there. I'm too lazy to pull up the original search term and edit it, so I end up typing the whole name during the change. This little plugin solves exactly the described issue by introducting just one extra keystroke infront of the magic *.\r\n\r\n\r\nLicense\r\n\r\nCopyright \u00c2\u00a9 Jan Christoph Ebersbach. Distributed under the same terms as Vim itself. See :help license","4":"* Given your cursor (|) is here: shoo|ting start\r\n*  Pressing \\* will search for the term ting if it's part of the word \\<shooting\\>\r\n*  In vim search syntax this is equivalent to: \/\\<shoo\\zsting\\>\r\n\r\nSupported keybindings\r\n* <Leader>* and <Leader># for searching forward\/backward for the exact word\r\n* <Leader>g* and <Leader>g# for searching forward\/backward without stopping at word boundaries\r\n\r\nWhy would I need that? Peronsally, I'm using the * often when I want to refactor code, e.g. change the name of a variable or function. Often I just want to change a certain part of the name and it would come very handy if the search would be able to place the cursor right there. I'm too lazy to pull up the original search term and edit it, so I end up typing the whole name during the change. This little plugin solves exactly the described issue by introducting just one extra keystroke infront of the magic *.\r\n\r\n\r\nLicense\r\n\r\nCopyright \u00c2\u00a9 Jan Christoph Ebersbach. Distributed under the same terms as Vim itself. See :help license","install_details":"I recommend installing pathogen.vim, and than execute the following commands:\r\n\r\ncd ~\/.vim\/bundle\r\ngit clone git:\/\/github.com\/jceb\/vim-shootingstar.git\r\n\r\nOr download the source directly from github: https:\/\/github.com\/jceb\/vim-shootingstar","5":"I recommend installing pathogen.vim, and than execute the following commands:\r\n\r\ncd ~\/.vim\/bundle\r\ngit clone git:\/\/github.com\/jceb\/vim-shootingstar.git\r\n\r\nOr download the source directly from github: https:\/\/github.com\/jceb\/vim-shootingstar","first_name":"Jan Christoph","6":"Jan Christoph","last_name":"Ebersbach","7":"Ebersbach","releases":[{"0":"4616","vim_version":"7.0","1":"7.0","script_version":"0.2","2":"0.2","version_comment":"* replace backslash by <Leader>\r\n* add g*\/g# keybindings","3":"* replace backslash by <Leader>\r\n* add g*\/g# keybindings","package":"shootingstar.vim","4":"shootingstar.vim","src_id":"20459","5":"20459","creation_date":"1372600996","6":"1372600996"},{"0":"4616","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"shootingstar.vim","4":"shootingstar.vim","src_id":"20328","5":"20328","creation_date":"1370805100","6":"1370805100"}]},"4615":{"script_id":"4615","0":"4615","script_name":"thumbnail.vim","1":"thumbnail.vim","script_type":"utility","2":"utility","summary":"A thumbnail-style buffer selector for Vim","3":"A thumbnail-style buffer selector for Vim","description":"NOTE: I don't upload code to vim.org anymore. Please clone from https:\/\/github.com\/itchyny\/thumbnail.vim.\r\n\r\nThis plugin is a thumbnail-style buffer selector for Vim.\r\n\r\nThe basic concept is graphical vim. We should not stay still at old-style\r\nstage. The user interface is largely influenced by the new tab of\r\nGoogle Chrome. This plugin is also inspired by Launchpad of Mac and unite.vim.\r\n\r\nThe repository is https:\/\/github.com\/itchyny\/thumbnail.vim.","4":"NOTE: I don't upload code to vim.org anymore. Please clone from https:\/\/github.com\/itchyny\/thumbnail.vim.\r\n\r\nThis plugin is a thumbnail-style buffer selector for Vim.\r\n\r\nThe basic concept is graphical vim. We should not stay still at old-style\r\nstage. The user interface is largely influenced by the new tab of\r\nGoogle Chrome. This plugin is also inspired by Launchpad of Mac and unite.vim.\r\n\r\nThe repository is https:\/\/github.com\/itchyny\/thumbnail.vim.","install_details":"See README.md.","5":"See README.md.","first_name":"itchyny","6":"itchyny","last_name":"\u3000","7":"　","releases":[{"0":"4615","vim_version":"7.2","1":"7.2","script_version":"0.8","2":"0.8","version_comment":"- Refactoring\r\n- Fix s:gen_color\r\n","3":"- Refactoring\r\n- Fix s:gen_color\r\n","package":"thumbnail.vim-0.8.zip","4":"thumbnail.vim-0.8.zip","src_id":"24500","5":"24500","creation_date":"1473120563","6":"1473120563"},{"0":"4615","vim_version":"7.2","1":"7.2","script_version":"0.7","2":"0.7","version_comment":"Clear colorcolumn\r\nReplace ==\/!~ with ==#\/!~#\r\nUse abort argument for :function\r\nSet norelativenumber\r\nUse nowait for <ESC>\r\nFix for buffers containing [|, [\\, [^\r\n","3":"Clear colorcolumn\r\nReplace ==\/!~ with ==#\/!~#\r\nUse abort argument for :function\r\nSet norelativenumber\r\nUse nowait for <ESC>\r\nFix for buffers containing [|, [\\, [^\r\n","package":"thumbnail.vim-0.7.zip","4":"thumbnail.vim-0.7.zip","src_id":"23031","5":"23031","creation_date":"1426407241","6":"1426407241"},{"0":"4615","vim_version":"7.2","1":"7.2","script_version":"0.6","2":"0.6","version_comment":"Save cpo and restore\r\nImprove g:loaded_thumbnail check\r\nFix the LICENSE file\r\nImprove the syntax file","3":"Save cpo and restore\r\nImprove g:loaded_thumbnail check\r\nFix the LICENSE file\r\nImprove the syntax file","package":"thumbnail.zip","4":"thumbnail.zip","src_id":"22805","5":"22805","creation_date":"1421531252","6":"1421531252"},{"0":"4615","vim_version":"7.2","1":"7.2","script_version":"0.5","2":"0.5","version_comment":"Improve the syntax\r\nRemove noautocmd\r\nImprove the buffer's name\r\nImprove buffer initialization\r\nUpdate colors on ColorScheme event\r\nFix for mouse wheel\r\n<Plug>(thumbnail)","3":"Improve the syntax\r\nRemove noautocmd\r\nImprove the buffer's name\r\nImprove buffer initialization\r\nUpdate colors on ColorScheme event\r\nFix for mouse wheel\r\n<Plug>(thumbnail)","package":"thumbnail.zip","4":"thumbnail.zip","src_id":"21711","5":"21711","creation_date":"1396445028","6":"1396445028"},{"0":"4615","vim_version":"7.2","1":"7.2","script_version":"0.4","2":"0.4","version_comment":"Check existence of &concealcursor.\r\nMove core codes to autoload\/thumbnail.vim.","3":"Check existence of &concealcursor.\r\nMove core codes to autoload\/thumbnail.vim.","package":"thumbnail.zip","4":"thumbnail.zip","src_id":"20819","5":"20819","creation_date":"1379494264","6":"1379494264"},{"0":"4615","vim_version":"7.0","1":"7.0","script_version":"0.3","2":"0.3","version_comment":"Filtering for [No Name] buffers\r\nImprove argument completion\r\nImprove option completion\r\nImprove behavior of vnew\r\nImprove option parser and add '-here!'\r\nChange behavior of nmap I","3":"Filtering for [No Name] buffers\r\nImprove argument completion\r\nImprove option completion\r\nImprove behavior of vnew\r\nImprove option parser and add '-here!'\r\nChange behavior of nmap I","package":"thumbnail.zip","4":"thumbnail.zip","src_id":"20588","5":"20588","creation_date":"1375424900","6":"1375424900"},{"0":"4615","vim_version":"7.0","1":"7.0","script_version":"0.2","2":"0.2","version_comment":"Fix -here option","3":"Fix -here option","package":"thumbnail.zip","4":"thumbnail.zip","src_id":"20357","5":"20357","creation_date":"1371161643","6":"1371161643"},{"0":"4615","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"thumbnail.zip","4":"thumbnail.zip","src_id":"20326","5":"20326","creation_date":"1370743161","6":"1370743161"}]},"4614":{"script_id":"4614","0":"4614","script_name":"vim-autopep8","1":"vim-autopep8","script_type":"ftplugin","2":"ftplugin","summary":"vim-autopep8 is a Vim plugin that runs the currently open file through autopep8.","3":"vim-autopep8 is a Vim plugin that runs the currently open file through autopep8.","description":"vim-autopep8 is a Vim plugin that applies autopep8 to your current file. \r\n\r\nautopep8 automatically formats Python code to conform to the PEP 8 style guide.\r\n\r\nsee also https:\/\/github.com\/tell-k\/vim-autopep8\r\n\r\ndocumentaion https:\/\/vim-autopep8.readthedocs.org\/en\/latest\/","4":"vim-autopep8 is a Vim plugin that applies autopep8 to your current file. \r\n\r\nautopep8 automatically formats Python code to conform to the PEP 8 style guide.\r\n\r\nsee also https:\/\/github.com\/tell-k\/vim-autopep8\r\n\r\ndocumentaion https:\/\/vim-autopep8.readthedocs.org\/en\/latest\/","install_details":"simply put the contents of this repository in your ~\/.vim\/bundle directory.","5":"simply put the contents of this repository in your ~\/.vim\/bundle directory.","first_name":"tell","6":"tell","last_name":"k","7":"k","releases":[{"0":"4614","vim_version":"7.0","1":"7.0","script_version":"1.2.0","2":"1.2.0","version_comment":"* Add new option \"autopep8_on_save\". (https:\/\/github.com\/tell-k\/vim-autopep8\/pull\/35) Thanks to @ahakanbaba\r\n","3":"* Add new option \"autopep8_on_save\". (https:\/\/github.com\/tell-k\/vim-autopep8\/pull\/35) Thanks to @ahakanbaba\r\n","package":"vim-autopep8.zip","4":"vim-autopep8.zip","src_id":"26026","5":"26026","creation_date":"1528047060","6":"1528047060"},{"0":"4614","vim_version":"7.0","1":"7.0","script_version":"1.1.1","2":"1.1.1","version_comment":"fixed auto go to first line.\r\nhttps:\/\/github.com\/tell-k\/vim-autopep8\/pull\/33","3":"fixed auto go to first line.\r\nhttps:\/\/github.com\/tell-k\/vim-autopep8\/pull\/33","package":"vim-autopep8.zip","4":"vim-autopep8.zip","src_id":"25606","5":"25606","creation_date":"1507741478","6":"1507741478"},{"0":"4614","vim_version":"7.0","1":"7.0","script_version":"1.1.0","2":"1.1.0","version_comment":"- Support more aggresive options\r\n- Support show diff in vertical split\r\n- Support range selection\r\n- Remove default <F8> key mapping.","3":"- Support more aggresive options\r\n- Support show diff in vertical split\r\n- Support range selection\r\n- Remove default <F8> key mapping.","package":"vim-autopep8.zip","4":"vim-autopep8.zip","src_id":"25000","5":"25000","creation_date":"1488079059","6":"1488079059"},{"0":"4614","vim_version":"7.0","1":"7.0","script_version":"1.0.7","2":"1.0.7","version_comment":"#15 :Autopep8 broken\r\nhttps:\/\/github.com\/tell-k\/vim-autopep8\/pull\/15\r\n\r\n#13 redraw under disable_show_diff mode\r\nhttps:\/\/github.com\/tell-k\/vim-autopep8\/pull\/13","3":"#15 :Autopep8 broken\r\nhttps:\/\/github.com\/tell-k\/vim-autopep8\/pull\/15\r\n\r\n#13 redraw under disable_show_diff mode\r\nhttps:\/\/github.com\/tell-k\/vim-autopep8\/pull\/13","package":"vim-autopep8.zip","4":"vim-autopep8.zip","src_id":"22443","5":"22443","creation_date":"1411143515","6":"1411143515"},{"0":"4614","vim_version":"7.0","1":"7.0","script_version":"1.0.6","2":"1.0.6","version_comment":"No need to file scope variables. \r\n* https:\/\/github.com\/tell-k\/vim-autopep8\/issues\/11\r\n\r\nAdd ability to pass commandline args\r\n* https:\/\/github.com\/tell-k\/vim-autopep8\/pull\/10\r\n\r\nfixe type \r\n* https:\/\/github.com\/tell-k\/vim-autopep8\/pull\/9\r\n","3":"No need to file scope variables. \r\n* https:\/\/github.com\/tell-k\/vim-autopep8\/issues\/11\r\n\r\nAdd ability to pass commandline args\r\n* https:\/\/github.com\/tell-k\/vim-autopep8\/pull\/10\r\n\r\nfixe type \r\n* https:\/\/github.com\/tell-k\/vim-autopep8\/pull\/9\r\n","package":"vim-autopep8.zip","4":"vim-autopep8.zip","src_id":"21924","5":"21924","creation_date":"1400823377","6":"1400823377"},{"0":"4614","vim_version":"7.0","1":"7.0","script_version":"1.0.5","2":"1.0.5","version_comment":"add \"autopep8_indent_size\" option\r\nhttps:\/\/github.com\/tell-k\/vim-autopep8\/issues\/8","3":"add \"autopep8_indent_size\" option\r\nhttps:\/\/github.com\/tell-k\/vim-autopep8\/issues\/8","package":"vim-autopep8.zip","4":"vim-autopep8.zip","src_id":"21884","5":"21884","creation_date":"1400125572","6":"1400125572"},{"0":"4614","vim_version":"7.0","1":"7.0","script_version":"1.0.4","2":"1.0.4","version_comment":"* Changed to green the color of the \"fixes comment\" \r\n* Function \":Autopep8\" becomes callable.","3":"* Changed to green the color of the \"fixes comment\" \r\n* Function \":Autopep8\" becomes callable.","package":"vim-autopep8.zip","4":"vim-autopep8.zip","src_id":"21563","5":"21563","creation_date":"1393771127","6":"1393771127"},{"0":"4614","vim_version":"7.0","1":"7.0","script_version":"1.0.3","2":"1.0.3","version_comment":"fixed bug & typo.\r\n* https:\/\/github.com\/tell-k\/vim-autopep8\/issues\/5 when filename or filepath contain whitespace, cause error.\r\n* https:\/\/github.com\/tell-k\/vim-autopep8\/issues\/7 typo. 'aggresive' => 'aggressive'.","3":"fixed bug & typo.\r\n* https:\/\/github.com\/tell-k\/vim-autopep8\/issues\/5 when filename or filepath contain whitespace, cause error.\r\n* https:\/\/github.com\/tell-k\/vim-autopep8\/issues\/7 typo. 'aggresive' => 'aggressive'.","package":"vim-autopep8.zip","4":"vim-autopep8.zip","src_id":"21259","5":"21259","creation_date":"1388412336","6":"1388412336"},{"0":"4614","vim_version":"7.0","1":"7.0","script_version":"1.0.2","2":"1.0.2","version_comment":"fixed typo. https:\/\/github.com\/tell-k\/vim-autopep8\/pull\/4","3":"fixed typo. https:\/\/github.com\/tell-k\/vim-autopep8\/pull\/4","package":"vim-autopep8.zip","4":"vim-autopep8.zip","src_id":"20954","5":"20954","creation_date":"1382714971","6":"1382714971"},{"0":"4614","vim_version":"7.0","1":"7.0","script_version":"1.0.1","2":"1.0.1","version_comment":"* add \"autopep8_disable_show_diff\" option. default is 0.\r\n* add help document. available \"help autopep8\".\r\n","3":"* add \"autopep8_disable_show_diff\" option. default is 0.\r\n* add help document. available \"help autopep8\".\r\n","package":"vim-autopep8.zip","4":"vim-autopep8.zip","src_id":"20808","5":"20808","creation_date":"1379342372","6":"1379342372"},{"0":"4614","vim_version":"7.0","1":"7.0","script_version":"1.0.0","2":"1.0.0","version_comment":"Initial upload","3":"Initial upload","package":"python_autopep8.vim","4":"python_autopep8.vim","src_id":"20314","5":"20314","creation_date":"1370623140","6":"1370623140"}]},"4613":{"script_id":"4613","0":"4613","script_name":"vim-origami","1":"vim-origami","script_type":"utility","2":"utility","summary":"A script to align, insert and delete foldmarkers conveniently","3":"A script to align, insert and delete foldmarkers conveniently","description":"#vim-origami\r\n\r\nPlugin to satisfy all your folding needs  \r\n * Justify all the open-fold markers  \r\n * Create new open\/close foldmarkers conveniently  \r\n\r\nThe latest version will be available on Github https:\/\/github.com\/kshenoy\/vim-origami\r\n\r\n##Screenshots\r\nhttp:\/\/imgur.com\/a\/n8It6#0\r\n\r\n\r\n##Usage\r\nSo, once that's done, out of the box, the followings mappings are defined by default:  \r\n\r\n  <leader>zax  Align all folds of level 'x'  \r\n  <leader>zox  Insert a start foldmarker of level 'x' at the end of line  \r\n  <leader>zcx  Insert an end  foldmarker of level 'x' at the end of line  \r\n  <leader>zOx  Insert a start foldmarker of level 'x' enclosed in comments at the end of line  \r\n  <leader>zCx  Insert an end  foldmarker of level 'x' enclosed in comments at the end of line  \r\n  <leader>zd   Delete a foldmarker present on the line  \r\n\r\n  <leader>zaa  Align all the folds\r\n  <leader>zoo  Insert an unnumbered open foldmarker\r\n  <leader>zcc  Insert an unnumbered close foldmarker\r\n  <leader>zOO  Insert a commented unnumbered open foldmarker\r\n  <leader>zCC  Insert a commented unnumbered close foldmarker\r\n\r\nwhere 'x' is a number from 0-9. 0 refers to unnumbered folds","4":"#vim-origami\r\n\r\nPlugin to satisfy all your folding needs  \r\n * Justify all the open-fold markers  \r\n * Create new open\/close foldmarkers conveniently  \r\n\r\nThe latest version will be available on Github https:\/\/github.com\/kshenoy\/vim-origami\r\n\r\n##Screenshots\r\nhttp:\/\/imgur.com\/a\/n8It6#0\r\n\r\n\r\n##Usage\r\nSo, once that's done, out of the box, the followings mappings are defined by default:  \r\n\r\n  <leader>zax  Align all folds of level 'x'  \r\n  <leader>zox  Insert a start foldmarker of level 'x' at the end of line  \r\n  <leader>zcx  Insert an end  foldmarker of level 'x' at the end of line  \r\n  <leader>zOx  Insert a start foldmarker of level 'x' enclosed in comments at the end of line  \r\n  <leader>zCx  Insert an end  foldmarker of level 'x' enclosed in comments at the end of line  \r\n  <leader>zd   Delete a foldmarker present on the line  \r\n\r\n  <leader>zaa  Align all the folds\r\n  <leader>zoo  Insert an unnumbered open foldmarker\r\n  <leader>zcc  Insert an unnumbered close foldmarker\r\n  <leader>zOO  Insert a commented unnumbered open foldmarker\r\n  <leader>zCC  Insert a commented unnumbered close foldmarker\r\n\r\nwhere 'x' is a number from 0-9. 0 refers to unnumbered folds","install_details":"For those of you -\r\n* Pathogen: Unzip contents of the zip file to .vim\/bundle folder\r\n* Vundle\/NeoBundle: Add 'Bundle \"kshenoy\/vim-origami\" ' to .vimrc\r\n\r\nI highly recommend using a plugin manager to do the dirty work for you. \r\nIf you still insist on not using one, unzip the contents of the vim-origami folder to your .vim folder.","5":"For those of you -\r\n* Pathogen: Unzip contents of the zip file to .vim\/bundle folder\r\n* Vundle\/NeoBundle: Add 'Bundle \"kshenoy\/vim-origami\" ' to .vimrc\r\n\r\nI highly recommend using a plugin manager to do the dirty work for you. \r\nIf you still insist on not using one, unzip the contents of the vim-origami folder to your .vim folder.","first_name":"Kartik","6":"Kartik","last_name":"Shenoy","7":"Shenoy","releases":[{"0":"4613","vim_version":"7.0","1":"7.0","script_version":"1.6","2":"1.6","version_comment":"Bugfixes galore","3":"Bugfixes galore","package":"vim-origami.zip","4":"vim-origami.zip","src_id":"21238","5":"21238","creation_date":"1388020820","6":"1388020820"}]},"4612":{"script_id":"4612","0":"4612","script_name":"aPen","1":"aPen","script_type":"color scheme","2":"color scheme","summary":"like the Brackets","3":"like the Brackets","description":"Light background color scheme.\r\n\r\nPreview:\r\nhttp:\/\/pic4.zhimg.com\/a5e45393e8d5284395cf9795590fefbf_b.jpg","4":"Light background color scheme.\r\n\r\nPreview:\r\nhttp:\/\/pic4.zhimg.com\/a5e45393e8d5284395cf9795590fefbf_b.jpg","install_details":"Copy it to \"colors\" dir.","5":"Copy it to \"colors\" dir.","first_name":"Pengkai","6":"Pengkai","last_name":"Wang","7":"Wang","releases":[{"0":"4612","vim_version":"7.0","1":"7.0","script_version":"1.0.1","2":"1.0.1","version_comment":"Converting file format for Unix.","3":"Converting file format for Unix.","package":"apen.vim","4":"apen.vim","src_id":"23368","5":"23368","creation_date":"1433729402","6":"1433729402"},{"0":"4612","vim_version":"7.3","1":"7.3","script_version":"1.0","2":"1.0","version_comment":"add more color of syntax, it looks better.","3":"add more color of syntax, it looks better.","package":"apen.vim","4":"apen.vim","src_id":"22114","5":"22114","creation_date":"1404193563","6":"1404193563"},{"0":"4612","vim_version":"7.0","1":"7.0","script_version":"beta","2":"beta","version_comment":"Initial upload","3":"Initial upload","package":"apen.vim","4":"apen.vim","src_id":"20290","5":"20290","creation_date":"1370398709","6":"1370398709"}]},"4611":{"script_id":"4611","0":"4611","script_name":"racoon.vim","1":"racoon.vim","script_type":"syntax","2":"syntax","summary":"racoon config syntax","3":"racoon config syntax","description":"Syntax file for racoon.conf, the racoon (IPSec) configuration file. This syntax description has a small amount of context-sensitivity; it's more than a list of keywords, but far short of a strict parser.\r\n\r\nhttp:\/\/netbsd.gw.com\/cgi-bin\/man-cgi?racoon.conf","4":"Syntax file for racoon.conf, the racoon (IPSec) configuration file. This syntax description has a small amount of context-sensitivity; it's more than a list of keywords, but far short of a strict parser.\r\n\r\nhttp:\/\/netbsd.gw.com\/cgi-bin\/man-cgi?racoon.conf","install_details":"","5":"","first_name":"Peter","6":"Peter","last_name":"Sagerson","7":"Sagerson","releases":[{"0":"4611","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"racoon.vim","4":"racoon.vim","src_id":"20288","5":"20288","creation_date":"1370388276","6":"1370388276"}]},"4610":{"script_id":"4610","0":"4610","script_name":"vim-c-cr","1":"vim-c-cr","script_type":"ftplugin","2":"ftplugin","summary":"Finish braces, brackets and parentheses with ctrl+enter in gvim","3":"Finish braces, brackets and parentheses with ctrl+enter in gvim","description":"Full plugin located at: https:\/\/github.com\/jtmkrueger\/vim-c-cr\r\n\r\nvim-c-cr\r\nA very simple and small (eighteen lines of vimscript) plugin that maps ctrl+enter (<c-cr>) in insert mode to finish braces ({}), brackets ([]) and parentheses (()) for you and puts your cursor tabbed over on a blank line between them.\r\n\r\nSo,\r\n\r\n{<c-cr>\r\nor\r\n[<c-cr>\r\nor\r\n(<c-cr>\r\nwill give you\r\n\r\n{\r\n  <your cursor here>\r\n}\r\nor\r\n[\r\n  <your cursor here>\r\n]\r\nor\r\n(\r\n  <your cursor here>\r\n)\r\n\r\nDISCLAIMER\r\n\r\nThis only works with gvim!","4":"Full plugin located at: https:\/\/github.com\/jtmkrueger\/vim-c-cr\r\n\r\nvim-c-cr\r\nA very simple and small (eighteen lines of vimscript) plugin that maps ctrl+enter (<c-cr>) in insert mode to finish braces ({}), brackets ([]) and parentheses (()) for you and puts your cursor tabbed over on a blank line between them.\r\n\r\nSo,\r\n\r\n{<c-cr>\r\nor\r\n[<c-cr>\r\nor\r\n(<c-cr>\r\nwill give you\r\n\r\n{\r\n  <your cursor here>\r\n}\r\nor\r\n[\r\n  <your cursor here>\r\n]\r\nor\r\n(\r\n  <your cursor here>\r\n)\r\n\r\nDISCLAIMER\r\n\r\nThis only works with gvim!","install_details":"Compatible with pathogen and vundle, here's the github repo where you can find the whole plugin: https:\/\/github.com\/jtmkrueger\/vim-c-cr.\r\n\r\nOnly the 1 file is here.","5":"Compatible with pathogen and vundle, here's the github repo where you can find the whole plugin: https:\/\/github.com\/jtmkrueger\/vim-c-cr.\r\n\r\nOnly the 1 file is here.","first_name":"John","6":"John","last_name":"Krueger","7":"Krueger","releases":[{"0":"4610","vim_version":"7.0","1":"7.0","script_version":"1","2":"1","version_comment":"Initial upload","3":"Initial upload","package":"ccr.vim","4":"ccr.vim","src_id":"20282","5":"20282","creation_date":"1370358465","6":"1370358465"}]},"4609":{"script_id":"4609","0":"4609","script_name":"Psearch","1":"Psearch","script_type":"patch","2":"patch","summary":"Vim plugin for parallel searching the pattern string","3":"Vim plugin for parallel searching the pattern string","description":"Vim global plugin Psearch for parallel searching the pattern string in your current file.\r\n\r\nThere are two functions to find the pattern string. The second one support regular expression.\r\n\r\nPsearch(arg1, arg2) is a function which can find your designated pattern string parallel and locate the cursor at the position of the next or the previous pattern string.\r\n@param arg1\tpattern string\r\n@param arg2\tfind direction \r\n\t\t\t'D' means find the next one\r\n\t\t\t'F' means find the previous one\r\n\r\nPRsearch(arg1, arg2) is a function which can find your designated regular expression parallel and locate the cursor at the position of the next or the previous string which matches the regular expression. \r\n@param arg1\tregular expression\r\n@param arg2\tfind direction \r\n\t\t\t'D' means find the next one\r\n\t\t\t'F' means find the previous one","4":"Vim global plugin Psearch for parallel searching the pattern string in your current file.\r\n\r\nThere are two functions to find the pattern string. The second one support regular expression.\r\n\r\nPsearch(arg1, arg2) is a function which can find your designated pattern string parallel and locate the cursor at the position of the next or the previous pattern string.\r\n@param arg1\tpattern string\r\n@param arg2\tfind direction \r\n\t\t\t'D' means find the next one\r\n\t\t\t'F' means find the previous one\r\n\r\nPRsearch(arg1, arg2) is a function which can find your designated regular expression parallel and locate the cursor at the position of the next or the previous string which matches the regular expression. \r\n@param arg1\tregular expression\r\n@param arg2\tfind direction \r\n\t\t\t'D' means find the next one\r\n\t\t\t'F' means find the previous one","install_details":"To use the plugin, \r\n1.You need to install python pprocess-0.5 fisrt. Decompress the pprocess-0.5.tar.gz and enter the directory. Use \"python setup.py install\" to install it.\r\n2.Load and install the plugin, input \":source <path>\/Psearch.vim\" in the VIM command line.\r\n3.How to call the functions:\r\nIn the VIM command line\r\n:call Psearch(arg1, arg2)\r\n:call PRsearch(arg1, arg2)","5":"To use the plugin, \r\n1.You need to install python pprocess-0.5 fisrt. Decompress the pprocess-0.5.tar.gz and enter the directory. Use \"python setup.py install\" to install it.\r\n2.Load and install the plugin, input \":source <path>\/Psearch.vim\" in the VIM command line.\r\n3.How to call the functions:\r\nIn the VIM command line\r\n:call Psearch(arg1, arg2)\r\n:call PRsearch(arg1, arg2)","first_name":"Jingwen","6":"Jingwen","last_name":"Deng","7":"Deng","releases":[{"0":"4609","vim_version":"7.0","1":"7.0","script_version":"Psearch","2":"Psearch","version_comment":"Initial upload","3":"Initial upload","package":"Psearch.zip","4":"Psearch.zip","src_id":"20281","5":"20281","creation_date":"1370354631","6":"1370354631"}]},"4608":{"script_id":"4608","0":"4608","script_name":"darknight256.vim","1":"darknight256.vim","script_type":"color scheme","2":"color scheme","summary":"Just another dark color scheme","3":"Just another dark color scheme","description":"Screenshot:\r\nhttp:\/\/i.imgur.com\/jH2J3af.png","4":"Screenshot:\r\nhttp:\/\/i.imgur.com\/jH2J3af.png","install_details":"","5":"","first_name":"Alexander","6":"Alexander","last_name":"Haeussler","7":"Haeussler","releases":[{"0":"4608","vim_version":"7.0","1":"7.0","script_version":"0.3","2":"0.3","version_comment":"- color definitons for SASS, CSS and JS\r\n- various color changes\r\n- formatting corrections","3":"- color definitons for SASS, CSS and JS\r\n- various color changes\r\n- formatting corrections","package":"darknight256.vim","4":"darknight256.vim","src_id":"22285","5":"22285","creation_date":"1407074641","6":"1407074641"},{"0":"4608","vim_version":"7.0","1":"7.0","script_version":"0.2","2":"0.2","version_comment":"- Better colors for messages, statusline and wildmenu\r\n- Code cleanup\r\n- License information added: Public Domain","3":"- Better colors for messages, statusline and wildmenu\r\n- Code cleanup\r\n- License information added: Public Domain","package":"darknight256.vim","4":"darknight256.vim","src_id":"20304","5":"20304","creation_date":"1370473545","6":"1370473545"},{"0":"4608","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"darknight256.vim","4":"darknight256.vim","src_id":"20279","5":"20279","creation_date":"1370324577","6":"1370324577"}]},"4607":{"script_id":"4607","0":"4607","script_name":"autoscroll.vim","1":"autoscroll.vim","script_type":"utility","2":"utility","summary":"Automatically scrolls the window slowly so you can read a file hands-free","3":"Automatically scrolls the window slowly so you can read a file hands-free","description":"Execute :ScrollDown or :ScrollUp to start auto movement of the cursor.\r\nPress <Space> or <Escape> to stop it.\r\n\r\nChange the scrolling speed with:\r\n\r\n    :let g:AutoScrollSpeed = 400\r\n","4":"Execute :ScrollDown or :ScrollUp to start auto movement of the cursor.\r\nPress <Space> or <Escape> to stop it.\r\n\r\nChange the scrolling speed with:\r\n\r\n    :let g:AutoScrollSpeed = 400\r\n","install_details":"Drop in ~\/.vim\/plugin\/ folder.","5":"Drop in ~\/.vim\/plugin\/ folder.","first_name":"joey","6":"joey","last_name":"twiddle","7":"twiddle","releases":[{"0":"4607","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"autoscroll.vim","4":"autoscroll.vim","src_id":"20257","5":"20257","creation_date":"1370088918","6":"1370088918"}]},"4606":{"script_id":"4606","0":"4606","script_name":"move_until_char_changes.vim","1":"move_until_char_changes.vim","script_type":"utility","2":"utility","summary":"Moves up or down the file until a different character appears under the cursor","3":"Moves up or down the file until a different character appears under the cursor","description":"\" Keep moving in given direction until we reach a new character under the\r\n\" cursor.  (Like Ctrl-Arrow in Excel.)  Bound to Ctrl-Shift-Up\/Down for Vim.","4":"\" Keep moving in given direction until we reach a new character under the\r\n\" cursor.  (Like Ctrl-Arrow in Excel.)  Bound to Ctrl-Shift-Up\/Down for Vim.","install_details":"Drop in ~\/.vim\/plugin\/ folder","5":"Drop in ~\/.vim\/plugin\/ folder","first_name":"joey","6":"joey","last_name":"twiddle","7":"twiddle","releases":[{"0":"4606","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"move_until_char_changes.vim","4":"move_until_char_changes.vim","src_id":"20256","5":"20256","creation_date":"1370088491","6":"1370088491"}]},"4605":{"script_id":"4605","0":"4605","script_name":"seoul256.vim","1":"seoul256.vim","script_type":"color scheme","2":"color scheme","summary":"A low-contrast Vim color scheme based on Seoul Colors","3":"A low-contrast Vim color scheme based on Seoul Colors","description":"seoul256.vim is a low-contrast Vim color scheme based on Seoul Colors.\r\nWorks on 256-color terminal or on GVim.\r\n\r\nProject page:\r\n  https:\/\/github.com\/junegunn\/seoul256.vim\r\n\r\nScreenshot:\r\n  https:\/\/raw.github.com\/junegunn\/i\/master\/seoul256.png\r\n  https:\/\/raw.github.com\/junegunn\/i\/master\/seoul256-light.png\r\n\r\nSeoul Colors:\r\n  http:\/\/www.seoul.go.kr\/v2012\/seoul\/symbol\/color.html\r\n\r\nChanging background brightness:\r\n    \" Dark version:\r\n    \"   Range:   233 (darkest) ~ 239 (lightest)\r\n    let g:seoul256_background = 237\r\n    colo seoul256\r\n\r\n    \" Light version\r\n    \"   Range:   252 (darkest) ~ 256 (lightest)\r\n    let g:seoul256_background = 253\r\n    colo seoul256\r\n","4":"seoul256.vim is a low-contrast Vim color scheme based on Seoul Colors.\r\nWorks on 256-color terminal or on GVim.\r\n\r\nProject page:\r\n  https:\/\/github.com\/junegunn\/seoul256.vim\r\n\r\nScreenshot:\r\n  https:\/\/raw.github.com\/junegunn\/i\/master\/seoul256.png\r\n  https:\/\/raw.github.com\/junegunn\/i\/master\/seoul256-light.png\r\n\r\nSeoul Colors:\r\n  http:\/\/www.seoul.go.kr\/v2012\/seoul\/symbol\/color.html\r\n\r\nChanging background brightness:\r\n    \" Dark version:\r\n    \"   Range:   233 (darkest) ~ 239 (lightest)\r\n    let g:seoul256_background = 237\r\n    colo seoul256\r\n\r\n    \" Light version\r\n    \"   Range:   252 (darkest) ~ 256 (lightest)\r\n    let g:seoul256_background = 253\r\n    colo seoul256\r\n","install_details":"Download and put it in your ~\/.vim\/colors directory, or use Pathogen or Vundle (Bundle 'junegunn\/seoul256.vim')\r\n","5":"Download and put it in your ~\/.vim\/colors directory, or use Pathogen or Vundle (Bundle 'junegunn\/seoul256.vim')\r\n","first_name":"Junegunn","6":"Junegunn","last_name":"Choi","7":"Choi","releases":[{"0":"4605","vim_version":"7.0","1":"7.0","script_version":"1.3.0","2":"1.3.0","version_comment":"- Added support for switching versions with `set background`\r\n- Improved colors","3":"- Added support for switching versions with `set background`\r\n- Improved colors","package":"seoul256.vim","4":"seoul256.vim","src_id":"21307","5":"21307","creation_date":"1389431232","6":"1389431232"},{"0":"4605","vim_version":"7.3","1":"7.3","script_version":"1.2.12","2":"1.2.12","version_comment":"Allow background color of 233","3":"Allow background color of 233","package":"seoul256.vim","4":"seoul256.vim","src_id":"20885","5":"20885","creation_date":"1380983415","6":"1380983415"},{"0":"4605","vim_version":"7.3","1":"7.3","script_version":"1.2.11","2":"1.2.11","version_comment":"Changed colors for extra whitespaces. Added colors for vim-indent-guides plugin.","3":"Changed colors for extra whitespaces. Added colors for vim-indent-guides plugin.","package":"seoul256.vim","4":"seoul256.vim","src_id":"20617","5":"20617","creation_date":"1376021297","6":"1376021297"},{"0":"4605","vim_version":"7.3","1":"7.3","script_version":"1.2.11","2":"1.2.11","version_comment":"Changed colors for strings, identifiers, and directories. Added colors for vim-indent-guides plugin.","3":"Changed colors for strings, identifiers, and directories. Added colors for vim-indent-guides plugin.","package":"seoul256-light.vim","4":"seoul256-light.vim","src_id":"20616","5":"20616","creation_date":"1376021276","6":"1376021276"},{"0":"4605","vim_version":"7.3","1":"7.3","script_version":"1.2.10","2":"1.2.10","version_comment":"- Changed SpecialKey color for listchars\r\n- Corrected background value (dark)","3":"- Changed SpecialKey color for listchars\r\n- Corrected background value (dark)","package":"seoul256.vim","4":"seoul256.vim","src_id":"20581","5":"20581","creation_date":"1375286016","6":"1375286016"},{"0":"4605","vim_version":"7.3","1":"7.3","script_version":"1.2.10","2":"1.2.10","version_comment":"- Changed SpecialKey color for listchars","3":"- Changed SpecialKey color for listchars","package":"seoul256-light.vim","4":"seoul256-light.vim","src_id":"20580","5":"20580","creation_date":"1375285965","6":"1375285965"},{"0":"4605","vim_version":"7.3","1":"7.3","script_version":"1.2.8","2":"1.2.8","version_comment":"Improve readability","3":"Improve readability","package":"seoul256.vim","4":"seoul256.vim","src_id":"20455","5":"20455","creation_date":"1372566589","6":"1372566589"},{"0":"4605","vim_version":"7.3","1":"7.3","script_version":"1.2.8","2":"1.2.8","version_comment":"Improve readability","3":"Improve readability","package":"seoul256-light.vim","4":"seoul256-light.vim","src_id":"20454","5":"20454","creation_date":"1372566557","6":"1372566557"},{"0":"4605","vim_version":"7.3","1":"7.3","script_version":"1.2.6","2":"1.2.6","version_comment":"Light color scheme","3":"Light color scheme","package":"seoul256-light.vim","4":"seoul256-light.vim","src_id":"20334","5":"20334","creation_date":"1370928770","6":"1370928770"},{"0":"4605","vim_version":"7.3","1":"7.3","script_version":"1.2.5","2":"1.2.5","version_comment":"Dark color scheme","3":"Dark color scheme","package":"seoul256.vim","4":"seoul256.vim","src_id":"20299","5":"20299","creation_date":"1370450454","6":"1370450454"}]},"4604":{"script_id":"4604","0":"4604","script_name":"Balsa-vim","1":"Balsa-vim","script_type":"syntax","2":"syntax","summary":"Balsa syntax and indent descriptions.","3":"Balsa syntax and indent descriptions.","description":"This plugin contains indent and syntax plugins for Balsa.\r\nBalsa is an asynchronous circuit synthesis system and hardware description language.\r\nTo get more information, visit http:\/\/apt.cs.manchester.ac.uk\/projects\/tools\/balsa\/\r\n\r\nFor more detail see also project page https:\/\/github.com\/qeexee\/balsa-vim","4":"This plugin contains indent and syntax plugins for Balsa.\r\nBalsa is an asynchronous circuit synthesis system and hardware description language.\r\nTo get more information, visit http:\/\/apt.cs.manchester.ac.uk\/projects\/tools\/balsa\/\r\n\r\nFor more detail see also project page https:\/\/github.com\/qeexee\/balsa-vim","install_details":"","5":"","first_name":"Shin'ya","6":"Shin'ya","last_name":"Ueoka","7":"Ueoka","releases":[{"0":"4604","vim_version":"7.0","1":"7.0","script_version":"1.0.1","2":"1.0.1","version_comment":"Removed trash.","3":"Removed trash.","package":"balsa-vim.tar.gz","4":"balsa-vim.tar.gz","src_id":"20240","5":"20240","creation_date":"1369990122","6":"1369990122"}]},"4603":{"script_id":"4603","0":"4603","script_name":"Emacs Org-protocol","1":"Emacs Org-protocol","script_type":"utility","2":"utility","summary":"Emacs Org-mode protocol","3":"Emacs Org-mode protocol","description":"launch your Emacs Client from vim, and capture a file or store link with org mode.\r\n\r\nOrg mode is for keeping notes, maintaining TODO lists, planning projects, and authoring documents with a fast and effective plain-text system.\r\n\r\nhttp:\/\/orgmode.org\/\r\n\r\nkey map:\r\n\r\n<A-n> : capture a file\r\n\r\n<A-l> : store a link\r\n","4":"launch your Emacs Client from vim, and capture a file or store link with org mode.\r\n\r\nOrg mode is for keeping notes, maintaining TODO lists, planning projects, and authoring documents with a fast and effective plain-text system.\r\n\r\nhttp:\/\/orgmode.org\/\r\n\r\nkey map:\r\n\r\n<A-n> : capture a file\r\n\r\n<A-l> : store a link\r\n","install_details":"drop it into your plugin folder.","5":"drop it into your plugin folder.","first_name":"Huxi","6":"Huxi","last_name":"Fun","7":"Fun","releases":[{"0":"4603","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"org-protocol.vim","4":"org-protocol.vim","src_id":"20230","5":"20230","creation_date":"1369883975","6":"1369883975"}]},"4602":{"script_id":"4602","0":"4602","script_name":"PatternsOnText","1":"PatternsOnText","script_type":"utility","2":"utility","summary":"Advanced commands to apply regular expressions.","3":"Advanced commands to apply regular expressions.","description":"DESCRIPTION\r\nThis plugin provides a toolbox of commands to delete, substitute, or\r\nde-duplicate text based on a passed regular expression (or the last used\r\nsearch pattern), something which would otherwise require multiple steps, a\r\ncomplex sub-replace-expression or a macro. One way or the other, all\r\ncommands here are extensions of the :substitute command. Use them whenever\r\nthe general built-in doesn't suffice.\r\n\r\nSOURCE\r\n:DeleteExcept\r\n    http:\/\/stackoverflow.com\/questions\/6249172\/vim-delete-anything-other-than-pattern\r\n:SubstituteInSearch inspired by\r\n    http:\/\/stackoverflow.com\/questions\/13763880\/in-vim-how-can-i-search-and-replace-every-other-match\r\n:DeleteDuplicateLinesOf inspired by\r\n    http:\/\/stackoverflow.com\/questions\/14236226\/hanging-only-to-the-first-instance-of-the-line-and-deleting-all-further-copies\r\n:DeleteDuplicateLinesIgnoring inspired by\r\n    http:\/\/stackoverflow.com\/questions\/1896793\/remove-duplicate-line-in-vim\r\n:DeleteAllDuplicateLinesIgnoring inspired by\r\n    http:\/\/stackoverflow.com\/questions\/22193596\/in-vim-how-to-remove-all-lines-that-are-duplicate-somewhere\r\n:SubstituteNotInSearch inspired by\r\n    http:\/\/stackoverflow.com\/questions\/26569959\/ignore-keywords-in-quotes-in-vim-regex-substitute\r\n:DeleteUniqueLinesIgnoring inspired by\r\n    http:\/\/stackoverflow.com\/questions\/26981192\/how-do-i-remove-non-duplicate-lines-in-vim\r\n:SubstituteChoices inspired by\r\n    http:\/\/vi.stackexchange.com\/questions\/9700\/mutliple-choice-substitute\r\n\r\nSEE ALSO\r\n- The ExtractMatches.vim plugin (vimscript #4795) provides commands to yank\r\n  matches into a register, optionally only unique matches without duplicates.\r\n- The EditSimilar.vim plugin (vimscript #2544) uses the same\r\n  {wildcard}={string} replacement pairs of :SubstituteWildcard, but for\r\n  editing a similar file, e.g. via :EditSubstitute.\r\n- The ingo#syntaxitem#IsOnSyntax() function provided by ingo-library.vim can\r\n  be used with :SubstituteIf as a predicate that checks for the syntax of\r\n  the current match. For example, a predicate that detects comments can be\r\n  defined as:\r\n    function! Comment()\r\n        return ingo#syntaxitem#IsOnSyntax(getpos('.'), '^Comment$')\r\n    endfunction\r\n\r\nRELATED WORKS\r\n- The :SubstituteSelected command can be emulated with built-ins via\r\n    :call feedkeys('yyyq') | %s\/{pattern}\/{string}\/gc\r\n (Source: http:\/\/stackoverflow.com\/a\/25840884\/813602)\r\n- substitute_unless_string.vim\r\n  (https:\/\/github.com\/LucHermitte\/lh-misc\/blob\/master\/plugin\/substitute_unless_string.vim)\r\n  implements a :SubstituteIf with a fixed predicate (that checks the current\r\n  syntax).\r\n\r\nUSAGE\r\n:[range]SubstituteExcept\/{pattern}\/{string}\/[flags] [count]\r\n                        Replace text in the current line \/ [range] that does\r\n                        not match {pattern} \/ the last used search pattern\r\n                        with {string}; \"g\" is implicit. Empty lines (without\r\n                        any whitespace) are kept empty.\r\n                        In {string}, & refers to the text that does not match,\r\n                        whereas \\1 etc. refer to the previous match of a\r\n                        sub-expression in {pattern}.\r\n:[range]SubstituteExcept [flags] [count]\r\n                        Repeat the last substitution with the last used search\r\n                        pattern, last used replacement string, and last used\r\n                        :s_flags; \"g\" is implicit.\r\n\r\n:[range]DeleteExcept [{pattern}]\r\n:[range]DeleteExcept \/{pattern}\/[flags]\r\n                        Delete all text in the current line \/ [range] except\r\n                        for the text matching {pattern} \/ the last used search\r\n                        pattern. For [flags], see :s_flags; \"g\" is implicit.\r\n\r\n:[range]SubstituteSelected\/{pattern}\/{string}\/[flags] {answers}\r\n                        Replace matches of {pattern} in the current line \/\r\n                        [range] with {string}, determining whether a\r\n                        particular match should be replaced on the sequence of\r\n                        \"y\" or \"n\" (a count can be prefixed, e.g. \"3y4n2y\") or\r\n                        numeric positions \"2,5\", or ranges \"3-5\" in {answers}.\r\n                        If no numeric positions follow, the last \"y\" \/ \"n\"\r\n                        sequence repeats for further matches. For example with\r\n                        \"ynn\", the first match is replaced, the second and\r\n                        third are not, the fourth is again replaced, ...\r\n                        Handles & and \\0, \\1 .. \\9 in {string}, also \\=\r\n                        sub-replace-expression and \\r, \\n, \\t, \\b.\r\n:[range]SubstituteSelected [flags] [answers]\r\n                        Repeat the last substitution with the last used search\r\n                        pattern, last used replacement string, last used\r\n                        :s_flags, and last used answers.\r\n\r\n:[range]SubstituteSubsequent\/{pattern}\/{string}\/[flags]\r\n                        Replace all matches of {pattern} on or after the\r\n                        current cursor position (and in all entire following\r\n                        lines) in [range] with {string}.\r\n                        For a \"blockwise to end\" replacement that is\r\n                        restricted to positions on and after the current\r\n                        column in all lines, pass the special flag [b].\r\n:[range]SubstituteSubsequent\/{pattern}\/{string}\/[flags] {answers}\r\n                        Replace all matches of {pattern} on or after the\r\n                        current cursor position in [range] with {string},\r\n                        determining whether a particular match should be\r\n                        replaced on the sequence of \"y\" or \"n\" (a count can be\r\n                        prefixed, e.g. \"3y4n2y\") or numeric positions \"2,5\",\r\n                        or ranges \"3-5\" in {answers}, as with\r\n                        :SubstituteSelected.\r\n:[range]SubstituteSubsequent [flags] [answers]\r\n                        Repeat the last substitution with the last used search\r\n                        pattern, last used replacement string, last used\r\n                        :s_flags, and last used answers.\r\n\r\n:SubstituteUnderCursor\/{pattern}\/{string}\/[flags]\r\n                        Replace a match of {pattern} if the cursor is\r\n                        (somewhere) on the match. Stuff excluded by \/\\zs and\r\n                        \/\\ze still counts a match.\r\n:SubstituteUnderCursor [flags]\r\n                        Repeat the last substitution with the last used search\r\n                        pattern, last used replacement string, and last used\r\n                        :s_flags.\r\n\r\n:[range]SubstituteInSearch\/{pattern}\/{string}\/[flags] [count]\r\n                        Within the current search pattern matches, replace all\r\n                        matches of {pattern} with {string}. Shortcut for\r\n                        :%s\/\/\\=substitute(submatch(0), \"foo\", \"bar\", \"g\")\/gc\r\n                       ~ is replaced with the {string} of the previous\r\n                        :Substitute[Not]InSearch.\r\n                        Handles \\= sub-replace-expression in {string}, which\r\n                        can't be used recursively in the above built-in\r\n                        :%s\/\/\\=...\r\n                       [flags] and [count] apply to the outer matching of the\r\n                        last search pattern. The [e] from :s_flags also\r\n                        suppresses the error message when {pattern} never\r\n                        matches.\r\n                        To replace only the first occurrence of {pattern},\r\n                        pass the special flag [f].\r\n                        For a case-insensitive substitution, prepend '\\c' to\r\n                        {pattern}.\r\n                        Does not modify the last search pattern quote\/.\r\n:[range]SubstituteInSearch\/{search}\/{pattern}\/{string}\/[flags] [count]\r\n                        Like above, but additionally specifies the {search}\r\n                        pattern instead of using quote\/ (which again isn't\r\n                        modified).\r\n:[range]SubstituteInSearch [flags] [count]\r\n                        Repeat last :SubstituteInSearch with same search\r\n                        {pattern} and substitute {string}, but without the\r\n                        same flags or given {search} pattern.\r\n\r\n:[range]SubstituteNotInSearch\/{pattern}\/{string}\/[flags] [count]\r\n                        Outside the current search pattern matches, replace\r\n                        all matches of {pattern} with {string}. Combination of\r\n                        :SubstituteExcept and :SubstituteInSearch.\r\n                        ~ is replaced with the {string} of the previous\r\n                        :Substitute[Not]InSearch.\r\n                        [flags] and [count] apply to the outer matching of the\r\n                        last search pattern. The [e] from :s_flags also\r\n                        suppresses the error message when {pattern} never\r\n                        matches.\r\n                        To replace only the first occurrence of {pattern},\r\n                        pass the special flag [f].\r\n                        For a case-insensitive substitution, prepend '\\c' to\r\n                        {pattern}.\r\n                        Does not modify the last search pattern quote\/.\r\n:[range]SubstituteNotInSearch\/{search}\/{pattern}\/{string}\/[flags] [count]\r\n                        Like above, but additionally specifies the {search}\r\n                        pattern instead of using quote\/ (which again isn't\r\n                        modified).\r\n:[range]SubstituteNotInSearch [flags] [count]\r\n                        Repeat last :SubstituteNotInSearch with same search\r\n                        {pattern} and substitute {string}, but without the\r\n                        same flags or given {search} pattern.\r\n\r\n:[range]SubstituteIf\/{pattern}\/{string}\/[flags] {predicate}\r\n:[range]SubstituteUnless\/{pattern}\/{string}\/[flags] {predicate}\r\n                        Replace matches of {pattern} in the current line \/\r\n                        [range] with {string} if the expression {predicate}\r\n                        returns a true (:SubstituteIf) \/ false\r\n                        (:SubstituteUnless) value.\r\n\r\n                        Inside {predicate}, you can reference a context object\r\n                        via v:val. It provides the following information:\r\n                            matchCount: number of current match of {pattern}\r\n                            replacementCount: number of actual replacements\r\n                                              done so far, i.e. where\r\n                                              {predicate} was true\r\n                        It also contains pre-initialized variables for use by\r\n                        {predicate}. These get cleared by each :SubstituteIf\r\n                        \/ :SubstituteUnless invocation:\r\n                            n: number \/ flag (0 \/ false)\r\n                            m: number \/ flag (1 \/ true)\r\n                            l: empty List []\r\n                            d: empty Dictionary {}\r\n                            s: empty String \"\"\r\n:[range]SubstituteIf [flags] [predicate]\r\n:[range]SubstituteUnless [flags] [predicate]\r\n                        Repeat the last substitution with the last used search\r\n                        pattern, last used replacement string, last used\r\n                        :s_flags, and last used predicate.\r\n\r\n:[range]SubstituteChoices \/{pattern}\/{string1}\/{string2}\/[...\/] [flags] [count]\r\n                        Replace a match of {pattern} with one of {string1},\r\n                        {string2}, ..., with each replacement queried from the\r\n                        user.\r\n:[range]SubstituteChoices [flags] [count]\r\n                        Repeat the last substitution with the last used search\r\n                        pattern, last used replacement choices, last used\r\n                        :s_flags and count.\r\n\r\n:[range]SubstituteMultiple \/{pattern}\/{string}\/ [...] [flags] [count]\r\n                        Change any of the {pattern} given to the corresponding\r\n                        {string}. As this is done in a single :substitute,\r\n                        this can have different (better) semantics than\r\n                        sequential :s\/new\/old\/ | s\/older\/newer\/ commands. For\r\n                        example, you can swap texts with this.\r\n                        Note: You cannot use capturing groups \/\\( here!\r\n                        Handles & and \\= sub-replace-expression in {string}.\r\n:[range]SubstituteMultiple [flags] [count]\r\n                        Repeat the last substitution with the last used search\r\n                        patterns, last used replacement strings, last used\r\n                        :s_flags and count.\r\n\r\n:[range]SubstituteWildcard {wildcard}={string} [...] [flags] [count]\r\n                        Change (first in the line, with \"g\" flag all) matches\r\n                        of wildcard to {string}. Modeled after the Korn\r\n                        shell's \"cd {old} {new}\" command.\r\n                        Handles & and \\= sub-replace-expression in {string}.\r\n                        Whitespace in the substitution pairs must be escaped;\r\n                        for a literal backslash search \/ replace, use \\\\:\r\n                            C:\\\\=my\\ drive\r\n:[range]SubstituteWildcard [flags] [count]\r\n                        Repeat the last substitution with the last used search\r\n                        pattern, last used wildcard replacements, last used\r\n                        :s_flags and count.\r\n\r\n:[range]SubstituteMultipleExpr \/{pattern-expr}\/{replacement-expr}\/ [flags] [count]\r\n                        Evaluate {pattern-expr}, either as a List of patterns,\r\n                        or else as String, which is then split into lines of\r\n                        patterns. Change any of these patterns to the\r\n                        corresponding (i.e. with the same index, using the\r\n                        last available if there are fewer replacements\r\n                        available) List element of {replacement-expr}.\r\n                        Note: You cannot use capturing groups \/\\( here!\r\n                        Each replacement handles & and \\=.\r\n:[range]SubstituteMultipleExpr [flags] [count]\r\n                        Repeat the last substitution with the last used search\r\n                        and replacement expressions, last used :s_flags and\r\n                        count.\r\n\r\n:[range]SubstituteTransactional \/{pattern}\/{string}\/\r\n                                [flags][t\/{test-expr}\/][u\/{update-predicate}\/]\r\n                        First record every match of {pattern} without changing\r\n                        anything.\r\n                        The optional {test-expr} is invoked at each match\r\n                        (v:val contains a context Dict Substitute-v:val that\r\n                        can be used to store additional information. It also\r\n                        has the matchCount information (but not\r\n                        replacementCount)). You can skip that match by\r\n                        throwing \"skip\".\r\n                        The optional {update-predicate} is invoked once at the\r\n                        end (and passed that context object as v:val again,\r\n                        now also with matchNum information); it has to return\r\n                        1 or 0; in the latter case, no replacements are done\r\n                        (the transaction is aborted). In case of 1 (commit),\r\n                        all recorded positions (in reverse order from last to\r\n                        first) are replaced with {string}, which handles & and\r\n                        also \\=; with the latter sub-replace-expression, the\r\n                        cursor is positioned on the match, and can use the\r\n                        context via v:val, which contains the following\r\n                        additional information:\r\n                            matchNum:   total number of matches\r\n                            matchCount: number of current match of {pattern};\r\n                                        decreases from matchNum to 1\r\n                            matches:    List of all recorded matches, index\r\n                                        with matchCount to obtain the current\r\n                                        one\r\n                            matchText:  matched text (as you cannot use\r\n                                        submatch(0) any longer\r\n                            startPos:   [line, col] of the start of the match\r\n                            endPos:     [line, col] of the end of the match\r\n:[range]SubstituteTransactional [flags][t\/{test-expr}\/][u\/{update-predicate}\/]\r\n                        Repeat the last substitution with the last used search\r\n                        pattern, last used replacement, last used :s_flags\r\n                        and {test-expr} \/ {update-predicate} (unless\r\n                        specified).\r\n\r\n:[range]SubstituteTransactionalExpr \/{pattern-expr}\/{replacement-expr}\/\r\n                                [flags][t\/{test-expr}\/][u\/{update-predicate}\/]\r\n                        Evaluate {pattern-expr}, either as a List of patterns,\r\n                        or else as String, which is then split into lines of\r\n                        patterns. First record (the optional {test-expr}, and\r\n                        a later sub-replace-expression have an additional\r\n                        patternIndex that shows which pattern matched) and\r\n                        then at the end change any of these patterns given to\r\n                        the corresponding (i.e. with the same index, using the\r\n                        last available if there are fewer replacements\r\n                        available) List element of {replacement-expr}, like\r\n                        :SubstituteTransactional.\r\n                        Note: You cannot use capturing groups \/\\( here!\r\n:[range]SubstituteTransactionalExpr [flags][t\/{test-expr}\/][u\/{update-predicate}\/]\r\n                        Repeat the last substitution with the last used search\r\n                        and replacement expressions, last used :s_flags and\r\n                        {test-expr} \/ {update-predicate} (unless specified).\r\n\r\n:[range]SubstituteTransactionalExprEach \/{pattern-expr}\/{replacement-expr}\/\r\n                                [flags][t\/{test-expr}\/][u\/{update-predicate}\/]\r\n                        Evaluate {pattern-expr}, either as a List of patterns,\r\n                        or else as String, which is then split into lines of\r\n                        patterns. First record (the optional {test-expr}, and\r\n                        a later sub-replace-expression have an additional\r\n                        patternIndex that shows which pattern matched) and\r\n                        then at the end change any of these patterns given to\r\n                        the corresponding (i.e. with the same index, using the\r\n                        last available if there are fewer replacements\r\n                        available) List element of {replacement-expr}, like\r\n                        :SubstituteTransactional.\r\n                        In contrast to :SubstituteTransactionalExpr, each\r\n                        pattern is searched separately, not as alternative\r\n                        regexp branches (where the first branch matches, and\r\n                        other potential matches are eclipsed). As the\r\n                        replacements are only done at the very end, this means\r\n                        that _any_ pattern match is recorded and later\r\n                        replaced, not just the first alternative! (And you can\r\n                        use capturing groups here.)\r\n:[range]SubstituteTransactionalExprEach [flags][t\/{test-expr}\/][u\/{update-predicate}\/]\r\n                        Repeat the last substitution with the last used search\r\n                        and replacement expressions, last used :s_flags and\r\n                        {test-expr} \/ {update-predicate} (unless specified).\r\n\r\n:[range]SubstituteRotate \/{pattern}[\/{shift-value}]\/[+-]N\/[flags]\r\n:[range]SubstituteRotate \/{pattern}[\/\\={shift-value-expr}]\/[+-]N\/[flags]\r\n                        [t\/{test-expr}\/][u\/{update-predicate}\/]\r\n                        Replace every match of {pattern} with the preceding\r\n                        (+N) \/ following (-N) one. A given {shift-value} is\r\n                        used for the first \/ last match(es) (which are then\r\n                        put into the default register), and a\r\n                        {shift-value-expr} can refer to the context via v:val;\r\n                        else, matches will rotate, and the [+N] first are\r\n                        taken from behind \/ the [-N] last are taken from the\r\n                        front.\r\n                        For {test-expr} and {update-predicate} see\r\n                        :SubstituteTransactional.\r\n:[range]SubstituteRotate [flags][t\/{test-expr}\/][u\/{update-predicate}\/]\r\n                        Repeat the last substitution with the last used search\r\n                        pattern, last used {shift-value} \/ [+-]N, last used\r\n                        :s_flags and {test-expr} \/ {update-predicate}\r\n                        (unless specified).\r\n\r\n:[range]SubstituteRotateMemoized[!] \/{pattern}[\/{shift-value}]\/[+-]N\/[flags]\r\n:[range]SubstituteRotateMemoized[!] \/{pattern}[\/\\={shift-value-expr}]\/[+-]N\/[flags]\r\n                        [t\/{test-expr}\/][u\/{update-predicate}\/]\r\n:[range]SubstituteRotateMemoized[!] [flags][t\/{test-expr}\/][u\/{update-predicate}\/]\r\n                        Replace every match of {pattern} with the preceding\r\n                        (+N) \/ following (-N) one, and do the same replacement\r\n                        for further identical matches (instead of taking a\r\n                        possibly different neighbor there). Everything else\r\n                        works like :SubstituteRotate. Useful to make space\r\n                        in a list of matches in a consistent way. This\r\n                        persists across invocations (so you can apply the same\r\n                        rotation on multiple ranges \/ buffers); use ! to clear\r\n                        any stored associations and reset the context object.\r\n\r\n:[range]SubstituteExecute\/{pattern}\/[flags] {expr}\r\n                        Replace matches of {pattern} in the current line \/\r\n                        [range] with whatever {expr} |:return|s.\r\n                        This is like :sub-replace-expression, but you can\r\n                        use commands like :let, and have to explicitly\r\n                        :return the replacement value.\r\n                        Inside {expr}, you can reference a context object, as\r\n                        with :SubstituteIf. Cp. Substitute-v:val\r\n:[range]SubstituteExecute [flags] [expr]\r\n                        Repeat the last substitution with the last used search\r\n                        pattern, last used :s_flags, and last used\r\n                        expression.\r\n\r\n:[range]SubstituteTranslate[!] \/{pattern}\/\\={expr}\/[flags]\r\n                        Put each unique match of {pattern} through {expr} ...\r\n                        Inside {expr}, you can reference a context object, as\r\n                        with :SubstituteIf. Cp. Substitute-v:val; here,\r\n                        the information is:\r\n                            matchCount: number of non-memoized match of\r\n                                        {pattern}\r\n                            replacementCount: number of actual replacements\r\n                                              (memoized and new) done so far\r\n:[range]SubstituteTranslate[!] \/{pattern}\/{func}\/[flags]\r\n                        Invoke {func} (a context object, as with\r\n                        :SubstituteIf, cp. Substitute-v:val is the only\r\n                        argument; the match can be inspected via submatch())\r\n                        for each unique match ...\r\n:[range]SubstituteTranslate[!] \/{pattern}\/{item1}\/{item2}[\/...]\/[flags]\r\n                        Replace each unique match of {pattern} with the\r\n                        {item1}, ... (from left to right; if these are new\r\n                        {itemA} or there are additional appended {item3},\r\n                        those are added to the original ones, unless ! is\r\n                        given) ...\r\n                        ... and memoize the association, so that further\r\n                        identical matches will automatically use the same\r\n                        value (without invoking {expr} \/ {func} \/ popping\r\n                        {item1}). This persists across invocations (so you can\r\n                        apply the same translation on multiple ranges \/\r\n                        buffers); use ! to clear any stored associations and\r\n                        reset the context object.\r\n                        By returning a List, {expr} \/ {func} can indicate the\r\n                        the current match should be skipped (this decision\r\n                        isn't memoized), just like if there are no {item1}\r\n                        available any longer.\r\n:[range]SubstituteTranslate[!] [flags] [count]\r\n                        Repeat the last substitution with the last used search\r\n                        pattern, last used {expr} \/ {func} \/ {item1}..., last\r\n                        used :s_flags and count.\r\n:[line]PutTranslations [{template-expr}]\r\n                        Put all translations from :SubstituteTranslate after\r\n                        [line] (default current line), according to\r\n                        {template-expr}, which can refer to each original\r\n                        match as v:val.match, the associated replacement as\r\n                        v:val.replacement, and the (original) number of\r\n                        translation (which also determines the output order)\r\n                        as v:val.count. The default template associates the\r\n                        replacement with the original match:\r\n                            repl1: match1\r\n                            repl2: match2\r\n:YankTranslations [x] [{template-expr}]\r\n                        Yank all translations from :SubstituteTranslate\r\n                        [into register x], according to {template-expr} (see\r\n                        above). The default template creates :substitute\r\n                        commands that undo the translation:\r\n                            :'[,']substitute\/repl1\/match1\/g\r\n\r\n:[range]PrintDuplicateLinesOf[!] [{pattern}]\r\n:[range]PrintDuplicateLinesOf[!] \/{pattern}\/\r\n                        Print all occurrences of lines matching (with [!]: not\r\n                        matching) {pattern} (or the current line, if omitted).\r\n                        All matching lines are added to the jumplist, so you\r\n                        can use CTRL-O to revisit the locations.\r\n\r\n:[range]DeleteDuplicateLinesOf[!] [{pattern}]\r\n:[range]DeleteDuplicateLinesOf[!] \/{pattern}\/\r\n                        Delete all subsequent occurrences of lines matching\r\n                        (with [!]: not matching) {pattern} (or the current\r\n                        line, if omitted).\r\n\r\n:[range]PrintDuplicateLinesIgnoring[!] [{pattern}]\r\n:[range]PrintDuplicateLinesIgnoring[!] \/{pattern}\/\r\n                        Print all occurrences of a line whose text (ignoring\r\n                        any text matched (with [!]: not matched) by {pattern})\r\n                        appears multiple times. To ignore empty lines, use a\r\n                        {pattern} of ^$ (strict) or ^\\s*$ (lenient).\r\n                        All matching lines are added to the jumplist, so you\r\n                        can use CTRL-O to revisit the locations.\r\n\r\n:[range]DeleteDuplicateLinesIgnoring[!] [{pattern}]\r\n:[range]DeleteDuplicateLinesIgnoring[!] \/{pattern}\/\r\n                        Delete all subsequent occurrences of a line (ignoring\r\n                        any text matched (with [!]: not matched) by\r\n                        {pattern}).\r\n\r\n:[range]DeleteAllDuplicateLinesIgnoring[!] [{pattern}]\r\n:[range]DeleteAllDuplicateLinesIgnoring[!] \/{pattern}\/\r\n                        Delete all (including the very first) occurrences of a\r\n                        duplicate line (ignoring any text matched (with [!]:\r\n                        not matched) by {pattern}).\r\n\r\n:[range]PrintUniqueLinesOf[!] [\/]{pattern}[\/]\r\n                        Print all unique occurrences of lines matching (with\r\n                        [!]: not matching) {pattern}. All matching lines are\r\n                        added to the jumplist, so you can use CTRL-O to\r\n                        revisit the locations.\r\n\r\n:[range]DeleteUniqueLinesOf[!] [\/]{pattern}[\/]\r\n                        Delete all unique occurrences of lines matching (with\r\n                        [!]: not matching) {pattern}. Only duplicate lines are\r\n                        kept.\r\n\r\n:[range]PrintUniqueLinesIgnoring[!] [{pattern}]\r\n:[range]PrintUniqueLinesIgnoring[!] \/{pattern}\/\r\n                        Print all lines whose text (ignoring any text matched\r\n                        (with [!]: not matched) by {pattern}) appears only\r\n                        once in the buffer \/ [range].\r\n                        All matching lines are added to the jumplist, so you\r\n                        can use CTRL-O to revisit the locations.\r\n\r\n:[range]DeleteUniqueLinesIgnoring[!] [{pattern}]\r\n:[range]DeleteUniqueLinesIgnoring[!] \/{pattern}\/\r\n                        Delete all unique occurrences of a line (ignoring\r\n                        any text matched (with [!]: not matched) by\r\n                        {pattern}). Only duplicate lines are kept.\r\n\r\n                        For the following commands, the [!] suppresses the\r\n                        error when there are no duplicates.\r\n\r\n:[range]PrintUniques[!] [{pattern}]\r\n:[range]PrintUniques[!] \/{pattern}\/\r\n                        Print all matches of {pattern} (if omitted: the last\r\n                        search pattern) that appear only once in the current\r\n                        line \/ [range].\r\n                        To print all unique matches of {pattern} within a\r\n                        single line, processing a [range] or the entire\r\n                        buffer, use:\r\n                        :global\/^\/PrintUniques! [{pattern}]\r\n                        :global\/^\/PrintUniques! \/{pattern}\/\r\n                       The [!] suppresses the error when there are no\r\n                        uniques in a particular line.\r\n\r\n:[range]DeleteUniques[!] [{pattern}]\r\n:[range]DeleteUniques[!] \/{pattern}\/\r\n                        Delete all unique matches of {pattern} (or the last\r\n                        search pattern, if omitted). Only duplicate matches\r\n                        are kept.\r\n\r\n:[range]PrintDuplicates[!] [{pattern}]\r\n:[range]PrintDuplicates[!] \/{pattern}\/\r\n                        Print all matches of {pattern} (if omitted: the last\r\n                        search pattern) that appear multiple times in the\r\n                        current line \/ [range].\r\n                        To print all duplicate matches of {pattern} within a\r\n                        single line, processing a [range] or the entire\r\n                        buffer, use:\r\n                        :global\/^\/PrintDuplicates! [{pattern}]\r\n                        :global\/^\/PrintDuplicates! \/{pattern}\/\r\n                       The [!] suppresses the error when there are no\r\n                        duplicates in a particular line.\r\n\r\n:[range]DeleteDuplicates[!] [{pattern}]\r\n:[range]DeleteDuplicates[!] \/{pattern}\/\r\n                        Delete all subsequent matches of {pattern} (or the\r\n                        last search pattern, if omitted) except the first.\r\n                        To delete all non-unique matches, use\r\n                        :DeleteAllDuplicates instead.\r\n\r\n:[range]DeleteAllDuplicates[!] [{pattern}]\r\n:[range]DeleteAllDuplicates[!] \/{pattern}\/\r\n                        Delete all non-unique matches of {pattern} (or the last\r\n                        search pattern, if omitted). To keep the first match,\r\n                        use :DeleteDuplicates instead.\r\n\r\n:[range]DeleteRanges[!] {range} [range] [...] [x]\r\n:[range]YankRanges[!] {range} [range] [...] [x]\r\n                        Within the entire buffer \/ passed [range], delete \/\r\n                        yank all lines that fall within {range} (with [!]: do\r\n                        not fall within) into register [x] (or the unnamed\r\n                        register). When multiple [range]s are given, each line\r\n                        is yanked only once (in ascending order).\r\n\r\n:[range]PrintRanges[!] {range} [range] [...]\r\n                        Within the entire buffer \/ passed [range], print all\r\n                        lines that fall within {range} (with [!]: do not fall\r\n                        within).\r\n                        Each start of a block is added to the jumplist, so\r\n                        you can use CTRL-O to revisit the locations.\r\n\r\n:[range]RangeDo[!] {range} [range] [...] {command}\r\n                        Within the entire buffer \/ passed [range], execute the\r\n                        Ex command {cmd} on each line that falls within\r\n                        {range} (with [!]: does not fall within). When\r\n                        multiple [range]s are given, each line is processed\r\n                        only once (in ascending order).\r\n                        Note: {command} must be separated by whitespace from\r\n                        the preceding ranges!\r\n                        Works like\r\n                            :global\/apples\/,\/peaches\/ {cmd}\r\n                       but:\r\n                        - processes each line only once when the ranges are\r\n                          overlapping\r\n                        - supports multiple ranges (which are joined) and\r\n                          inversion with [!]\r\n\r\n:[range]Renumber [N][\/{pattern}\/[{fmt}\/]][flags][[*]offset]\r\n                        Search for decimal numbers \/ {pattern} with [flags],\r\n                        and replace each (according to :s_flags with\r\n                        1, 2, ... \/ [N], [N] + [offset], ...\r\n                        (or [N] * [offset])\r\n                        formatted as {fmt} (cp. printf()).\r\n:[range]Renumber &      Continue renumbering with the last used number, same\r\n                        {pattern}, {fmt}, [flags] and [offset]. Useful with\r\n                        :global to cover only certain lines. Use\r\n                        :0Renumber ... to prime the required values, e.g.:\r\n                            :0Renumber 100 g 10 | global\/^#\/.Renumber &","4":"DESCRIPTION\r\nThis plugin provides a toolbox of commands to delete, substitute, or\r\nde-duplicate text based on a passed regular expression (or the last used\r\nsearch pattern), something which would otherwise require multiple steps, a\r\ncomplex sub-replace-expression or a macro. One way or the other, all\r\ncommands here are extensions of the :substitute command. Use them whenever\r\nthe general built-in doesn't suffice.\r\n\r\nSOURCE\r\n:DeleteExcept\r\n    http:\/\/stackoverflow.com\/questions\/6249172\/vim-delete-anything-other-than-pattern\r\n:SubstituteInSearch inspired by\r\n    http:\/\/stackoverflow.com\/questions\/13763880\/in-vim-how-can-i-search-and-replace-every-other-match\r\n:DeleteDuplicateLinesOf inspired by\r\n    http:\/\/stackoverflow.com\/questions\/14236226\/hanging-only-to-the-first-instance-of-the-line-and-deleting-all-further-copies\r\n:DeleteDuplicateLinesIgnoring inspired by\r\n    http:\/\/stackoverflow.com\/questions\/1896793\/remove-duplicate-line-in-vim\r\n:DeleteAllDuplicateLinesIgnoring inspired by\r\n    http:\/\/stackoverflow.com\/questions\/22193596\/in-vim-how-to-remove-all-lines-that-are-duplicate-somewhere\r\n:SubstituteNotInSearch inspired by\r\n    http:\/\/stackoverflow.com\/questions\/26569959\/ignore-keywords-in-quotes-in-vim-regex-substitute\r\n:DeleteUniqueLinesIgnoring inspired by\r\n    http:\/\/stackoverflow.com\/questions\/26981192\/how-do-i-remove-non-duplicate-lines-in-vim\r\n:SubstituteChoices inspired by\r\n    http:\/\/vi.stackexchange.com\/questions\/9700\/mutliple-choice-substitute\r\n\r\nSEE ALSO\r\n- The ExtractMatches.vim plugin (vimscript #4795) provides commands to yank\r\n  matches into a register, optionally only unique matches without duplicates.\r\n- The EditSimilar.vim plugin (vimscript #2544) uses the same\r\n  {wildcard}={string} replacement pairs of :SubstituteWildcard, but for\r\n  editing a similar file, e.g. via :EditSubstitute.\r\n- The ingo#syntaxitem#IsOnSyntax() function provided by ingo-library.vim can\r\n  be used with :SubstituteIf as a predicate that checks for the syntax of\r\n  the current match. For example, a predicate that detects comments can be\r\n  defined as:\r\n    function! Comment()\r\n        return ingo#syntaxitem#IsOnSyntax(getpos('.'), '^Comment$')\r\n    endfunction\r\n\r\nRELATED WORKS\r\n- The :SubstituteSelected command can be emulated with built-ins via\r\n    :call feedkeys('yyyq') | %s\/{pattern}\/{string}\/gc\r\n (Source: http:\/\/stackoverflow.com\/a\/25840884\/813602)\r\n- substitute_unless_string.vim\r\n  (https:\/\/github.com\/LucHermitte\/lh-misc\/blob\/master\/plugin\/substitute_unless_string.vim)\r\n  implements a :SubstituteIf with a fixed predicate (that checks the current\r\n  syntax).\r\n\r\nUSAGE\r\n:[range]SubstituteExcept\/{pattern}\/{string}\/[flags] [count]\r\n                        Replace text in the current line \/ [range] that does\r\n                        not match {pattern} \/ the last used search pattern\r\n                        with {string}; \"g\" is implicit. Empty lines (without\r\n                        any whitespace) are kept empty.\r\n                        In {string}, & refers to the text that does not match,\r\n                        whereas \\1 etc. refer to the previous match of a\r\n                        sub-expression in {pattern}.\r\n:[range]SubstituteExcept [flags] [count]\r\n                        Repeat the last substitution with the last used search\r\n                        pattern, last used replacement string, and last used\r\n                        :s_flags; \"g\" is implicit.\r\n\r\n:[range]DeleteExcept [{pattern}]\r\n:[range]DeleteExcept \/{pattern}\/[flags]\r\n                        Delete all text in the current line \/ [range] except\r\n                        for the text matching {pattern} \/ the last used search\r\n                        pattern. For [flags], see :s_flags; \"g\" is implicit.\r\n\r\n:[range]SubstituteSelected\/{pattern}\/{string}\/[flags] {answers}\r\n                        Replace matches of {pattern} in the current line \/\r\n                        [range] with {string}, determining whether a\r\n                        particular match should be replaced on the sequence of\r\n                        \"y\" or \"n\" (a count can be prefixed, e.g. \"3y4n2y\") or\r\n                        numeric positions \"2,5\", or ranges \"3-5\" in {answers}.\r\n                        If no numeric positions follow, the last \"y\" \/ \"n\"\r\n                        sequence repeats for further matches. For example with\r\n                        \"ynn\", the first match is replaced, the second and\r\n                        third are not, the fourth is again replaced, ...\r\n                        Handles & and \\0, \\1 .. \\9 in {string}, also \\=\r\n                        sub-replace-expression and \\r, \\n, \\t, \\b.\r\n:[range]SubstituteSelected [flags] [answers]\r\n                        Repeat the last substitution with the last used search\r\n                        pattern, last used replacement string, last used\r\n                        :s_flags, and last used answers.\r\n\r\n:[range]SubstituteSubsequent\/{pattern}\/{string}\/[flags]\r\n                        Replace all matches of {pattern} on or after the\r\n                        current cursor position (and in all entire following\r\n                        lines) in [range] with {string}.\r\n                        For a \"blockwise to end\" replacement that is\r\n                        restricted to positions on and after the current\r\n                        column in all lines, pass the special flag [b].\r\n:[range]SubstituteSubsequent\/{pattern}\/{string}\/[flags] {answers}\r\n                        Replace all matches of {pattern} on or after the\r\n                        current cursor position in [range] with {string},\r\n                        determining whether a particular match should be\r\n                        replaced on the sequence of \"y\" or \"n\" (a count can be\r\n                        prefixed, e.g. \"3y4n2y\") or numeric positions \"2,5\",\r\n                        or ranges \"3-5\" in {answers}, as with\r\n                        :SubstituteSelected.\r\n:[range]SubstituteSubsequent [flags] [answers]\r\n                        Repeat the last substitution with the last used search\r\n                        pattern, last used replacement string, last used\r\n                        :s_flags, and last used answers.\r\n\r\n:SubstituteUnderCursor\/{pattern}\/{string}\/[flags]\r\n                        Replace a match of {pattern} if the cursor is\r\n                        (somewhere) on the match. Stuff excluded by \/\\zs and\r\n                        \/\\ze still counts a match.\r\n:SubstituteUnderCursor [flags]\r\n                        Repeat the last substitution with the last used search\r\n                        pattern, last used replacement string, and last used\r\n                        :s_flags.\r\n\r\n:[range]SubstituteInSearch\/{pattern}\/{string}\/[flags] [count]\r\n                        Within the current search pattern matches, replace all\r\n                        matches of {pattern} with {string}. Shortcut for\r\n                        :%s\/\/\\=substitute(submatch(0), \"foo\", \"bar\", \"g\")\/gc\r\n                       ~ is replaced with the {string} of the previous\r\n                        :Substitute[Not]InSearch.\r\n                        Handles \\= sub-replace-expression in {string}, which\r\n                        can't be used recursively in the above built-in\r\n                        :%s\/\/\\=...\r\n                       [flags] and [count] apply to the outer matching of the\r\n                        last search pattern. The [e] from :s_flags also\r\n                        suppresses the error message when {pattern} never\r\n                        matches.\r\n                        To replace only the first occurrence of {pattern},\r\n                        pass the special flag [f].\r\n                        For a case-insensitive substitution, prepend '\\c' to\r\n                        {pattern}.\r\n                        Does not modify the last search pattern quote\/.\r\n:[range]SubstituteInSearch\/{search}\/{pattern}\/{string}\/[flags] [count]\r\n                        Like above, but additionally specifies the {search}\r\n                        pattern instead of using quote\/ (which again isn't\r\n                        modified).\r\n:[range]SubstituteInSearch [flags] [count]\r\n                        Repeat last :SubstituteInSearch with same search\r\n                        {pattern} and substitute {string}, but without the\r\n                        same flags or given {search} pattern.\r\n\r\n:[range]SubstituteNotInSearch\/{pattern}\/{string}\/[flags] [count]\r\n                        Outside the current search pattern matches, replace\r\n                        all matches of {pattern} with {string}. Combination of\r\n                        :SubstituteExcept and :SubstituteInSearch.\r\n                        ~ is replaced with the {string} of the previous\r\n                        :Substitute[Not]InSearch.\r\n                        [flags] and [count] apply to the outer matching of the\r\n                        last search pattern. The [e] from :s_flags also\r\n                        suppresses the error message when {pattern} never\r\n                        matches.\r\n                        To replace only the first occurrence of {pattern},\r\n                        pass the special flag [f].\r\n                        For a case-insensitive substitution, prepend '\\c' to\r\n                        {pattern}.\r\n                        Does not modify the last search pattern quote\/.\r\n:[range]SubstituteNotInSearch\/{search}\/{pattern}\/{string}\/[flags] [count]\r\n                        Like above, but additionally specifies the {search}\r\n                        pattern instead of using quote\/ (which again isn't\r\n                        modified).\r\n:[range]SubstituteNotInSearch [flags] [count]\r\n                        Repeat last :SubstituteNotInSearch with same search\r\n                        {pattern} and substitute {string}, but without the\r\n                        same flags or given {search} pattern.\r\n\r\n:[range]SubstituteIf\/{pattern}\/{string}\/[flags] {predicate}\r\n:[range]SubstituteUnless\/{pattern}\/{string}\/[flags] {predicate}\r\n                        Replace matches of {pattern} in the current line \/\r\n                        [range] with {string} if the expression {predicate}\r\n                        returns a true (:SubstituteIf) \/ false\r\n                        (:SubstituteUnless) value.\r\n\r\n                        Inside {predicate}, you can reference a context object\r\n                        via v:val. It provides the following information:\r\n                            matchCount: number of current match of {pattern}\r\n                            replacementCount: number of actual replacements\r\n                                              done so far, i.e. where\r\n                                              {predicate} was true\r\n                        It also contains pre-initialized variables for use by\r\n                        {predicate}. These get cleared by each :SubstituteIf\r\n                        \/ :SubstituteUnless invocation:\r\n                            n: number \/ flag (0 \/ false)\r\n                            m: number \/ flag (1 \/ true)\r\n                            l: empty List []\r\n                            d: empty Dictionary {}\r\n                            s: empty String \"\"\r\n:[range]SubstituteIf [flags] [predicate]\r\n:[range]SubstituteUnless [flags] [predicate]\r\n                        Repeat the last substitution with the last used search\r\n                        pattern, last used replacement string, last used\r\n                        :s_flags, and last used predicate.\r\n\r\n:[range]SubstituteChoices \/{pattern}\/{string1}\/{string2}\/[...\/] [flags] [count]\r\n                        Replace a match of {pattern} with one of {string1},\r\n                        {string2}, ..., with each replacement queried from the\r\n                        user.\r\n:[range]SubstituteChoices [flags] [count]\r\n                        Repeat the last substitution with the last used search\r\n                        pattern, last used replacement choices, last used\r\n                        :s_flags and count.\r\n\r\n:[range]SubstituteMultiple \/{pattern}\/{string}\/ [...] [flags] [count]\r\n                        Change any of the {pattern} given to the corresponding\r\n                        {string}. As this is done in a single :substitute,\r\n                        this can have different (better) semantics than\r\n                        sequential :s\/new\/old\/ | s\/older\/newer\/ commands. For\r\n                        example, you can swap texts with this.\r\n                        Note: You cannot use capturing groups \/\\( here!\r\n                        Handles & and \\= sub-replace-expression in {string}.\r\n:[range]SubstituteMultiple [flags] [count]\r\n                        Repeat the last substitution with the last used search\r\n                        patterns, last used replacement strings, last used\r\n                        :s_flags and count.\r\n\r\n:[range]SubstituteWildcard {wildcard}={string} [...] [flags] [count]\r\n                        Change (first in the line, with \"g\" flag all) matches\r\n                        of wildcard to {string}. Modeled after the Korn\r\n                        shell's \"cd {old} {new}\" command.\r\n                        Handles & and \\= sub-replace-expression in {string}.\r\n                        Whitespace in the substitution pairs must be escaped;\r\n                        for a literal backslash search \/ replace, use \\\\:\r\n                            C:\\\\=my\\ drive\r\n:[range]SubstituteWildcard [flags] [count]\r\n                        Repeat the last substitution with the last used search\r\n                        pattern, last used wildcard replacements, last used\r\n                        :s_flags and count.\r\n\r\n:[range]SubstituteMultipleExpr \/{pattern-expr}\/{replacement-expr}\/ [flags] [count]\r\n                        Evaluate {pattern-expr}, either as a List of patterns,\r\n                        or else as String, which is then split into lines of\r\n                        patterns. Change any of these patterns to the\r\n                        corresponding (i.e. with the same index, using the\r\n                        last available if there are fewer replacements\r\n                        available) List element of {replacement-expr}.\r\n                        Note: You cannot use capturing groups \/\\( here!\r\n                        Each replacement handles & and \\=.\r\n:[range]SubstituteMultipleExpr [flags] [count]\r\n                        Repeat the last substitution with the last used search\r\n                        and replacement expressions, last used :s_flags and\r\n                        count.\r\n\r\n:[range]SubstituteTransactional \/{pattern}\/{string}\/\r\n                                [flags][t\/{test-expr}\/][u\/{update-predicate}\/]\r\n                        First record every match of {pattern} without changing\r\n                        anything.\r\n                        The optional {test-expr} is invoked at each match\r\n                        (v:val contains a context Dict Substitute-v:val that\r\n                        can be used to store additional information. It also\r\n                        has the matchCount information (but not\r\n                        replacementCount)). You can skip that match by\r\n                        throwing \"skip\".\r\n                        The optional {update-predicate} is invoked once at the\r\n                        end (and passed that context object as v:val again,\r\n                        now also with matchNum information); it has to return\r\n                        1 or 0; in the latter case, no replacements are done\r\n                        (the transaction is aborted). In case of 1 (commit),\r\n                        all recorded positions (in reverse order from last to\r\n                        first) are replaced with {string}, which handles & and\r\n                        also \\=; with the latter sub-replace-expression, the\r\n                        cursor is positioned on the match, and can use the\r\n                        context via v:val, which contains the following\r\n                        additional information:\r\n                            matchNum:   total number of matches\r\n                            matchCount: number of current match of {pattern};\r\n                                        decreases from matchNum to 1\r\n                            matches:    List of all recorded matches, index\r\n                                        with matchCount to obtain the current\r\n                                        one\r\n                            matchText:  matched text (as you cannot use\r\n                                        submatch(0) any longer\r\n                            startPos:   [line, col] of the start of the match\r\n                            endPos:     [line, col] of the end of the match\r\n:[range]SubstituteTransactional [flags][t\/{test-expr}\/][u\/{update-predicate}\/]\r\n                        Repeat the last substitution with the last used search\r\n                        pattern, last used replacement, last used :s_flags\r\n                        and {test-expr} \/ {update-predicate} (unless\r\n                        specified).\r\n\r\n:[range]SubstituteTransactionalExpr \/{pattern-expr}\/{replacement-expr}\/\r\n                                [flags][t\/{test-expr}\/][u\/{update-predicate}\/]\r\n                        Evaluate {pattern-expr}, either as a List of patterns,\r\n                        or else as String, which is then split into lines of\r\n                        patterns. First record (the optional {test-expr}, and\r\n                        a later sub-replace-expression have an additional\r\n                        patternIndex that shows which pattern matched) and\r\n                        then at the end change any of these patterns given to\r\n                        the corresponding (i.e. with the same index, using the\r\n                        last available if there are fewer replacements\r\n                        available) List element of {replacement-expr}, like\r\n                        :SubstituteTransactional.\r\n                        Note: You cannot use capturing groups \/\\( here!\r\n:[range]SubstituteTransactionalExpr [flags][t\/{test-expr}\/][u\/{update-predicate}\/]\r\n                        Repeat the last substitution with the last used search\r\n                        and replacement expressions, last used :s_flags and\r\n                        {test-expr} \/ {update-predicate} (unless specified).\r\n\r\n:[range]SubstituteTransactionalExprEach \/{pattern-expr}\/{replacement-expr}\/\r\n                                [flags][t\/{test-expr}\/][u\/{update-predicate}\/]\r\n                        Evaluate {pattern-expr}, either as a List of patterns,\r\n                        or else as String, which is then split into lines of\r\n                        patterns. First record (the optional {test-expr}, and\r\n                        a later sub-replace-expression have an additional\r\n                        patternIndex that shows which pattern matched) and\r\n                        then at the end change any of these patterns given to\r\n                        the corresponding (i.e. with the same index, using the\r\n                        last available if there are fewer replacements\r\n                        available) List element of {replacement-expr}, like\r\n                        :SubstituteTransactional.\r\n                        In contrast to :SubstituteTransactionalExpr, each\r\n                        pattern is searched separately, not as alternative\r\n                        regexp branches (where the first branch matches, and\r\n                        other potential matches are eclipsed). As the\r\n                        replacements are only done at the very end, this means\r\n                        that _any_ pattern match is recorded and later\r\n                        replaced, not just the first alternative! (And you can\r\n                        use capturing groups here.)\r\n:[range]SubstituteTransactionalExprEach [flags][t\/{test-expr}\/][u\/{update-predicate}\/]\r\n                        Repeat the last substitution with the last used search\r\n                        and replacement expressions, last used :s_flags and\r\n                        {test-expr} \/ {update-predicate} (unless specified).\r\n\r\n:[range]SubstituteRotate \/{pattern}[\/{shift-value}]\/[+-]N\/[flags]\r\n:[range]SubstituteRotate \/{pattern}[\/\\={shift-value-expr}]\/[+-]N\/[flags]\r\n                        [t\/{test-expr}\/][u\/{update-predicate}\/]\r\n                        Replace every match of {pattern} with the preceding\r\n                        (+N) \/ following (-N) one. A given {shift-value} is\r\n                        used for the first \/ last match(es) (which are then\r\n                        put into the default register), and a\r\n                        {shift-value-expr} can refer to the context via v:val;\r\n                        else, matches will rotate, and the [+N] first are\r\n                        taken from behind \/ the [-N] last are taken from the\r\n                        front.\r\n                        For {test-expr} and {update-predicate} see\r\n                        :SubstituteTransactional.\r\n:[range]SubstituteRotate [flags][t\/{test-expr}\/][u\/{update-predicate}\/]\r\n                        Repeat the last substitution with the last used search\r\n                        pattern, last used {shift-value} \/ [+-]N, last used\r\n                        :s_flags and {test-expr} \/ {update-predicate}\r\n                        (unless specified).\r\n\r\n:[range]SubstituteRotateMemoized[!] \/{pattern}[\/{shift-value}]\/[+-]N\/[flags]\r\n:[range]SubstituteRotateMemoized[!] \/{pattern}[\/\\={shift-value-expr}]\/[+-]N\/[flags]\r\n                        [t\/{test-expr}\/][u\/{update-predicate}\/]\r\n:[range]SubstituteRotateMemoized[!] [flags][t\/{test-expr}\/][u\/{update-predicate}\/]\r\n                        Replace every match of {pattern} with the preceding\r\n                        (+N) \/ following (-N) one, and do the same replacement\r\n                        for further identical matches (instead of taking a\r\n                        possibly different neighbor there). Everything else\r\n                        works like :SubstituteRotate. Useful to make space\r\n                        in a list of matches in a consistent way. This\r\n                        persists across invocations (so you can apply the same\r\n                        rotation on multiple ranges \/ buffers); use ! to clear\r\n                        any stored associations and reset the context object.\r\n\r\n:[range]SubstituteExecute\/{pattern}\/[flags] {expr}\r\n                        Replace matches of {pattern} in the current line \/\r\n                        [range] with whatever {expr} |:return|s.\r\n                        This is like :sub-replace-expression, but you can\r\n                        use commands like :let, and have to explicitly\r\n                        :return the replacement value.\r\n                        Inside {expr}, you can reference a context object, as\r\n                        with :SubstituteIf. Cp. Substitute-v:val\r\n:[range]SubstituteExecute [flags] [expr]\r\n                        Repeat the last substitution with the last used search\r\n                        pattern, last used :s_flags, and last used\r\n                        expression.\r\n\r\n:[range]SubstituteTranslate[!] \/{pattern}\/\\={expr}\/[flags]\r\n                        Put each unique match of {pattern} through {expr} ...\r\n                        Inside {expr}, you can reference a context object, as\r\n                        with :SubstituteIf. Cp. Substitute-v:val; here,\r\n                        the information is:\r\n                            matchCount: number of non-memoized match of\r\n                                        {pattern}\r\n                            replacementCount: number of actual replacements\r\n                                              (memoized and new) done so far\r\n:[range]SubstituteTranslate[!] \/{pattern}\/{func}\/[flags]\r\n                        Invoke {func} (a context object, as with\r\n                        :SubstituteIf, cp. Substitute-v:val is the only\r\n                        argument; the match can be inspected via submatch())\r\n                        for each unique match ...\r\n:[range]SubstituteTranslate[!] \/{pattern}\/{item1}\/{item2}[\/...]\/[flags]\r\n                        Replace each unique match of {pattern} with the\r\n                        {item1}, ... (from left to right; if these are new\r\n                        {itemA} or there are additional appended {item3},\r\n                        those are added to the original ones, unless ! is\r\n                        given) ...\r\n                        ... and memoize the association, so that further\r\n                        identical matches will automatically use the same\r\n                        value (without invoking {expr} \/ {func} \/ popping\r\n                        {item1}). This persists across invocations (so you can\r\n                        apply the same translation on multiple ranges \/\r\n                        buffers); use ! to clear any stored associations and\r\n                        reset the context object.\r\n                        By returning a List, {expr} \/ {func} can indicate the\r\n                        the current match should be skipped (this decision\r\n                        isn't memoized), just like if there are no {item1}\r\n                        available any longer.\r\n:[range]SubstituteTranslate[!] [flags] [count]\r\n                        Repeat the last substitution with the last used search\r\n                        pattern, last used {expr} \/ {func} \/ {item1}..., last\r\n                        used :s_flags and count.\r\n:[line]PutTranslations [{template-expr}]\r\n                        Put all translations from :SubstituteTranslate after\r\n                        [line] (default current line), according to\r\n                        {template-expr}, which can refer to each original\r\n                        match as v:val.match, the associated replacement as\r\n                        v:val.replacement, and the (original) number of\r\n                        translation (which also determines the output order)\r\n                        as v:val.count. The default template associates the\r\n                        replacement with the original match:\r\n                            repl1: match1\r\n                            repl2: match2\r\n:YankTranslations [x] [{template-expr}]\r\n                        Yank all translations from :SubstituteTranslate\r\n                        [into register x], according to {template-expr} (see\r\n                        above). The default template creates :substitute\r\n                        commands that undo the translation:\r\n                            :'[,']substitute\/repl1\/match1\/g\r\n\r\n:[range]PrintDuplicateLinesOf[!] [{pattern}]\r\n:[range]PrintDuplicateLinesOf[!] \/{pattern}\/\r\n                        Print all occurrences of lines matching (with [!]: not\r\n                        matching) {pattern} (or the current line, if omitted).\r\n                        All matching lines are added to the jumplist, so you\r\n                        can use CTRL-O to revisit the locations.\r\n\r\n:[range]DeleteDuplicateLinesOf[!] [{pattern}]\r\n:[range]DeleteDuplicateLinesOf[!] \/{pattern}\/\r\n                        Delete all subsequent occurrences of lines matching\r\n                        (with [!]: not matching) {pattern} (or the current\r\n                        line, if omitted).\r\n\r\n:[range]PrintDuplicateLinesIgnoring[!] [{pattern}]\r\n:[range]PrintDuplicateLinesIgnoring[!] \/{pattern}\/\r\n                        Print all occurrences of a line whose text (ignoring\r\n                        any text matched (with [!]: not matched) by {pattern})\r\n                        appears multiple times. To ignore empty lines, use a\r\n                        {pattern} of ^$ (strict) or ^\\s*$ (lenient).\r\n                        All matching lines are added to the jumplist, so you\r\n                        can use CTRL-O to revisit the locations.\r\n\r\n:[range]DeleteDuplicateLinesIgnoring[!] [{pattern}]\r\n:[range]DeleteDuplicateLinesIgnoring[!] \/{pattern}\/\r\n                        Delete all subsequent occurrences of a line (ignoring\r\n                        any text matched (with [!]: not matched) by\r\n                        {pattern}).\r\n\r\n:[range]DeleteAllDuplicateLinesIgnoring[!] [{pattern}]\r\n:[range]DeleteAllDuplicateLinesIgnoring[!] \/{pattern}\/\r\n                        Delete all (including the very first) occurrences of a\r\n                        duplicate line (ignoring any text matched (with [!]:\r\n                        not matched) by {pattern}).\r\n\r\n:[range]PrintUniqueLinesOf[!] [\/]{pattern}[\/]\r\n                        Print all unique occurrences of lines matching (with\r\n                        [!]: not matching) {pattern}. All matching lines are\r\n                        added to the jumplist, so you can use CTRL-O to\r\n                        revisit the locations.\r\n\r\n:[range]DeleteUniqueLinesOf[!] [\/]{pattern}[\/]\r\n                        Delete all unique occurrences of lines matching (with\r\n                        [!]: not matching) {pattern}. Only duplicate lines are\r\n                        kept.\r\n\r\n:[range]PrintUniqueLinesIgnoring[!] [{pattern}]\r\n:[range]PrintUniqueLinesIgnoring[!] \/{pattern}\/\r\n                        Print all lines whose text (ignoring any text matched\r\n                        (with [!]: not matched) by {pattern}) appears only\r\n                        once in the buffer \/ [range].\r\n                        All matching lines are added to the jumplist, so you\r\n                        can use CTRL-O to revisit the locations.\r\n\r\n:[range]DeleteUniqueLinesIgnoring[!] [{pattern}]\r\n:[range]DeleteUniqueLinesIgnoring[!] \/{pattern}\/\r\n                        Delete all unique occurrences of a line (ignoring\r\n                        any text matched (with [!]: not matched) by\r\n                        {pattern}). Only duplicate lines are kept.\r\n\r\n                        For the following commands, the [!] suppresses the\r\n                        error when there are no duplicates.\r\n\r\n:[range]PrintUniques[!] [{pattern}]\r\n:[range]PrintUniques[!] \/{pattern}\/\r\n                        Print all matches of {pattern} (if omitted: the last\r\n                        search pattern) that appear only once in the current\r\n                        line \/ [range].\r\n                        To print all unique matches of {pattern} within a\r\n                        single line, processing a [range] or the entire\r\n                        buffer, use:\r\n                        :global\/^\/PrintUniques! [{pattern}]\r\n                        :global\/^\/PrintUniques! \/{pattern}\/\r\n                       The [!] suppresses the error when there are no\r\n                        uniques in a particular line.\r\n\r\n:[range]DeleteUniques[!] [{pattern}]\r\n:[range]DeleteUniques[!] \/{pattern}\/\r\n                        Delete all unique matches of {pattern} (or the last\r\n                        search pattern, if omitted). Only duplicate matches\r\n                        are kept.\r\n\r\n:[range]PrintDuplicates[!] [{pattern}]\r\n:[range]PrintDuplicates[!] \/{pattern}\/\r\n                        Print all matches of {pattern} (if omitted: the last\r\n                        search pattern) that appear multiple times in the\r\n                        current line \/ [range].\r\n                        To print all duplicate matches of {pattern} within a\r\n                        single line, processing a [range] or the entire\r\n                        buffer, use:\r\n                        :global\/^\/PrintDuplicates! [{pattern}]\r\n                        :global\/^\/PrintDuplicates! \/{pattern}\/\r\n                       The [!] suppresses the error when there are no\r\n                        duplicates in a particular line.\r\n\r\n:[range]DeleteDuplicates[!] [{pattern}]\r\n:[range]DeleteDuplicates[!] \/{pattern}\/\r\n                        Delete all subsequent matches of {pattern} (or the\r\n                        last search pattern, if omitted) except the first.\r\n                        To delete all non-unique matches, use\r\n                        :DeleteAllDuplicates instead.\r\n\r\n:[range]DeleteAllDuplicates[!] [{pattern}]\r\n:[range]DeleteAllDuplicates[!] \/{pattern}\/\r\n                        Delete all non-unique matches of {pattern} (or the last\r\n                        search pattern, if omitted). To keep the first match,\r\n                        use :DeleteDuplicates instead.\r\n\r\n:[range]DeleteRanges[!] {range} [range] [...] [x]\r\n:[range]YankRanges[!] {range} [range] [...] [x]\r\n                        Within the entire buffer \/ passed [range], delete \/\r\n                        yank all lines that fall within {range} (with [!]: do\r\n                        not fall within) into register [x] (or the unnamed\r\n                        register). When multiple [range]s are given, each line\r\n                        is yanked only once (in ascending order).\r\n\r\n:[range]PrintRanges[!] {range} [range] [...]\r\n                        Within the entire buffer \/ passed [range], print all\r\n                        lines that fall within {range} (with [!]: do not fall\r\n                        within).\r\n                        Each start of a block is added to the jumplist, so\r\n                        you can use CTRL-O to revisit the locations.\r\n\r\n:[range]RangeDo[!] {range} [range] [...] {command}\r\n                        Within the entire buffer \/ passed [range], execute the\r\n                        Ex command {cmd} on each line that falls within\r\n                        {range} (with [!]: does not fall within). When\r\n                        multiple [range]s are given, each line is processed\r\n                        only once (in ascending order).\r\n                        Note: {command} must be separated by whitespace from\r\n                        the preceding ranges!\r\n                        Works like\r\n                            :global\/apples\/,\/peaches\/ {cmd}\r\n                       but:\r\n                        - processes each line only once when the ranges are\r\n                          overlapping\r\n                        - supports multiple ranges (which are joined) and\r\n                          inversion with [!]\r\n\r\n:[range]Renumber [N][\/{pattern}\/[{fmt}\/]][flags][[*]offset]\r\n                        Search for decimal numbers \/ {pattern} with [flags],\r\n                        and replace each (according to :s_flags with\r\n                        1, 2, ... \/ [N], [N] + [offset], ...\r\n                        (or [N] * [offset])\r\n                        formatted as {fmt} (cp. printf()).\r\n:[range]Renumber &      Continue renumbering with the last used number, same\r\n                        {pattern}, {fmt}, [flags] and [offset]. Useful with\r\n                        :global to cover only certain lines. Use\r\n                        :0Renumber ... to prime the required values, e.g.:\r\n                            :0Renumber 100 g 10 | global\/^#\/.Renumber &","install_details":"INSTALLATION\r\nThe code is hosted in a Git repo at\r\n    https:\/\/github.com\/inkarkat\/vim-PatternsOnText\r\nYou can use your favorite plugin manager, or \"git clone\" into a directory used\r\nfor Vim packages. Releases are on the \"stable\" branch, the latest unstable\r\ndevelopment snapshot on \"master\".\r\n\r\nThis script is also packaged as a vimball. If you have the \"gunzip\"\r\ndecompressor in your PATH, simply edit the *.vmb.gz package in Vim; otherwise,\r\ndecompress the archive first, e.g. using WinZip. Inside Vim, install by\r\nsourcing the vimball or via the :UseVimball command.\r\n    vim PatternsOnText*.vmb.gz\r\n    :so %\r\nTo uninstall, use the :RmVimball command.\r\n\r\nDEPENDENCIES\r\n- Requires Vim 7.0 or higher.\r\n- Requires the ingo-library.vim plugin (vimscript #4433), version 1.043 or\r\n  higher.","5":"INSTALLATION\r\nThe code is hosted in a Git repo at\r\n    https:\/\/github.com\/inkarkat\/vim-PatternsOnText\r\nYou can use your favorite plugin manager, or \"git clone\" into a directory used\r\nfor Vim packages. Releases are on the \"stable\" branch, the latest unstable\r\ndevelopment snapshot on \"master\".\r\n\r\nThis script is also packaged as a vimball. If you have the \"gunzip\"\r\ndecompressor in your PATH, simply edit the *.vmb.gz package in Vim; otherwise,\r\ndecompress the archive first, e.g. using WinZip. Inside Vim, install by\r\nsourcing the vimball or via the :UseVimball command.\r\n    vim PatternsOnText*.vmb.gz\r\n    :so %\r\nTo uninstall, use the :RmVimball command.\r\n\r\nDEPENDENCIES\r\n- Requires Vim 7.0 or higher.\r\n- Requires the ingo-library.vim plugin (vimscript #4433), version 1.043 or\r\n  higher.","first_name":"Ingo","6":"Ingo","last_name":"Karkat","7":"Karkat","releases":[{"0":"4602","vim_version":"7.0","1":"7.0","script_version":"2.20","2":"2.20","version_comment":"- Adapt: :PutTranslations and :Renumber need to check <count> == -1 instead of <line2> to support current line as well as a lnum of 0 (since Vim 8.1.1241).\r\n- ENH: :SubstituteTransactional* additionally support arbitrary access of matched texts via v:val.matches context.\r\n- ENH: Add :SubstituteRotate[Memoized] for the special case of using :SubstituteTransactional for rotating or shifting matches; i.e. replacing with preceding or following matches to make space for something new. Comes as both a stateless variant and :SubstituteRotateMemoized that keeps the mappings from old match to new, similar to what :SubstituteTranslate does.\r\n- ENH: Add :SubstituteUnderCursor for applying {pattern} only at the cursor position.\r\n- All commands support prepended command modifiers (like :keeppatterns). *** You need to update to ingo-library (vimscript #4433) version 1.043! ***","3":"- Adapt: :PutTranslations and :Renumber need to check <count> == -1 instead of <line2> to support current line as well as a lnum of 0 (since Vim 8.1.1241).\r\n- ENH: :SubstituteTransactional* additionally support arbitrary access of matched texts via v:val.matches context.\r\n- ENH: Add :SubstituteRotate[Memoized] for the special case of using :SubstituteTransactional for rotating or shifting matches; i.e. replacing with preceding or following matches to make space for something new. Comes as both a stateless variant and :SubstituteRotateMemoized that keeps the mappings from old match to new, similar to what :SubstituteTranslate does.\r\n- ENH: Add :SubstituteUnderCursor for applying {pattern} only at the cursor position.\r\n- All commands support prepended command modifiers (like :keeppatterns). *** You need to update to ingo-library (vimscript #4433) version 1.043! ***","package":"PatternsOnText-2.20.vmb.gz","4":"PatternsOnText-2.20.vmb.gz","src_id":"28076","5":"28076","creation_date":"1655132287","6":"1655132287"},{"0":"4602","vim_version":"7.0","1":"7.0","script_version":"2.11","2":"2.11","version_comment":"- Extract PatternsOnText#Translate#Translate() API function to allow easier creation of custom translation commands without having to reassemble (and then re-parse) the entire command arguments.\r\n- Add :PutTranslations and :YankTranslations companion commands of :SubstituteTranslate.\r\n- ENH: Also support \\= |sub-replace-expression| for :SubstituteMultiple and :SubstituteWildcard.\r\n- ENH: Add :SubstituteMultipleExpr variant of :SubstituteMultiple.\r\n- ENH: Add :SubstituteTransactional[Expr[Each]] commands.","3":"- Extract PatternsOnText#Translate#Translate() API function to allow easier creation of custom translation commands without having to reassemble (and then re-parse) the entire command arguments.\r\n- Add :PutTranslations and :YankTranslations companion commands of :SubstituteTranslate.\r\n- ENH: Also support \\= |sub-replace-expression| for :SubstituteMultiple and :SubstituteWildcard.\r\n- ENH: Add :SubstituteMultipleExpr variant of :SubstituteMultiple.\r\n- ENH: Add :SubstituteTransactional[Expr[Each]] commands.","package":"PatternsOnText-2.11.vmb.gz","4":"PatternsOnText-2.11.vmb.gz","src_id":"26440","5":"26440","creation_date":"1553836994","6":"1553836994"},{"0":"4602","vim_version":"7.0","1":"7.0","script_version":"2.10","2":"2.10","version_comment":"- Add :Renumber command.\r\n- Add :DeleteAllDuplicates command, a variant of :DeleteDuplicates and inverse of :DeleteUniques.\r\n- Minor: Do proper escaping of pattern separators when adding to the search history.\r\n- CHG: Allow inversion of :...LinesOf and :...LinesIgnoring {pattern} via ! (instead of suppressing error message with !) Affects :PrintDuplicateLinesOf, :DeleteDuplicateLinesOf, :PrintDuplicateLinesIgnoring, :DeleteDuplicateLinesIgnoring, :DeleteAllDuplicateLinesIgnoring, :PrintUniqueLinesOf, :DeleteUniqueLinesOf, :PrintUniqueLinesIgnoring, :DeleteUniqueLinesIgnoring\r\n- :SubstituteChoices: FIX: Forgot to update current line number; current line is re-printed on each occurrence.\r\n- :SubstituteChoices: Only rely on 'cursorline' highlighting if the line isn't actually folded.\r\n- :SubstituteChoices: ENH: Include count of match replacements in current line in query.\r\n- :SubstituteChoices: Correctly handle multi-digit entry, leading zeros with \/c flag.\r\n- FIX: Many :Substitute... commands did not yet check for read-only or unmodifiable buffer and instead printed an ugly multi-line error.\r\n- :SubstituteChoices: Also offer \"no\" and \"last as ...\" choices if the |:s_c| flag is given, to offer feature parity with built-in :substitute.\r\n- Add :SubstituteTranslate command.\r\n- CHG: Escaping of whitespace and backslashes in :SubstituteMultiple is not necessary any longer (but now the full \/{pattern}\/{string}\/ needs to be given; you cannot omit e.g. the trailing \/). This parsing better matches the user expectation. :SubstituteWildcard still requires escaping, though. *** You need to update to ingo-library (vimscript #4433) version 1.035! ***","3":"- Add :Renumber command.\r\n- Add :DeleteAllDuplicates command, a variant of :DeleteDuplicates and inverse of :DeleteUniques.\r\n- Minor: Do proper escaping of pattern separators when adding to the search history.\r\n- CHG: Allow inversion of :...LinesOf and :...LinesIgnoring {pattern} via ! (instead of suppressing error message with !) Affects :PrintDuplicateLinesOf, :DeleteDuplicateLinesOf, :PrintDuplicateLinesIgnoring, :DeleteDuplicateLinesIgnoring, :DeleteAllDuplicateLinesIgnoring, :PrintUniqueLinesOf, :DeleteUniqueLinesOf, :PrintUniqueLinesIgnoring, :DeleteUniqueLinesIgnoring\r\n- :SubstituteChoices: FIX: Forgot to update current line number; current line is re-printed on each occurrence.\r\n- :SubstituteChoices: Only rely on 'cursorline' highlighting if the line isn't actually folded.\r\n- :SubstituteChoices: ENH: Include count of match replacements in current line in query.\r\n- :SubstituteChoices: Correctly handle multi-digit entry, leading zeros with \/c flag.\r\n- FIX: Many :Substitute... commands did not yet check for read-only or unmodifiable buffer and instead printed an ugly multi-line error.\r\n- :SubstituteChoices: Also offer \"no\" and \"last as ...\" choices if the |:s_c| flag is given, to offer feature parity with built-in :substitute.\r\n- Add :SubstituteTranslate command.\r\n- CHG: Escaping of whitespace and backslashes in :SubstituteMultiple is not necessary any longer (but now the full \/{pattern}\/{string}\/ needs to be given; you cannot omit e.g. the trailing \/). This parsing better matches the user expectation. :SubstituteWildcard still requires escaping, though. *** You need to update to ingo-library (vimscript #4433) version 1.035! ***","package":"PatternsOnText-2.10.vmb.gz","4":"PatternsOnText-2.10.vmb.gz","src_id":"26247","5":"26247","creation_date":"1539986913","6":"1539986913"},{"0":"4602","vim_version":"7.0","1":"7.0","script_version":"2.01","2":"2.01","version_comment":"- Add :SubstituteUnless variant of :SubstituteIf.\r\n- Move PatternsOnText#DefaultReplacementOnPredicate(), PatternsOnText#ReplaceSpecial(), and PatternsOnText#DefaultReplacer() to ingo-library. *** You need to update to ingo-library (vimscript #4433) version 1.032! ***","3":"- Add :SubstituteUnless variant of :SubstituteIf.\r\n- Move PatternsOnText#DefaultReplacementOnPredicate(), PatternsOnText#ReplaceSpecial(), and PatternsOnText#DefaultReplacer() to ingo-library. *** You need to update to ingo-library (vimscript #4433) version 1.032! ***","package":"PatternsOnText-2.01.vmb.gz","4":"PatternsOnText-2.01.vmb.gz","src_id":"25510","5":"25510","creation_date":"1502791827","6":"1502791827"},{"0":"4602","vim_version":"7.0","1":"7.0","script_version":"2.00","2":"2.00","version_comment":"- Add :SubstituteChoices command.\r\n- Add :SubstituteIf command.\r\n- Add :SubstituteExecute command.\r\n- ENH: Support recall of previous pairs \/ substitutions in :SubstituteWildcard \/ :SubstituteMultiple.\r\n- FIX: Minor: With :SubstituteSelected, Cursor jumps to first line if no substitution at all (\"nnnnn\"). Initialize l:lastNum to current line. *** You need to update to ingo-library (vimscript #4433) version 1.027! ***","3":"- Add :SubstituteChoices command.\r\n- Add :SubstituteIf command.\r\n- Add :SubstituteExecute command.\r\n- ENH: Support recall of previous pairs \/ substitutions in :SubstituteWildcard \/ :SubstituteMultiple.\r\n- FIX: Minor: With :SubstituteSelected, Cursor jumps to first line if no substitution at all (\"nnnnn\"). Initialize l:lastNum to current line. *** You need to update to ingo-library (vimscript #4433) version 1.027! ***","package":"PatternsOnText-2.00.vmb.gz","4":"PatternsOnText-2.00.vmb.gz","src_id":"24576","5":"24576","creation_date":"1475235158","6":"1475235158"},{"0":"4602","vim_version":"7.0","1":"7.0","script_version":"1.51","2":"1.51","version_comment":"- Don't set the buffer 'modified' for :PrintDuplicates and :PrintUniques.\r\n- Improve reporting of readonly buffers for :SubstituteExcept, :DeleteExcept, :SubstituteSelected, and :SubstituteSubsequent.\r\n- FIX: Misplaced :continue in s:Collect() safety check; must :return out of factored out function.","3":"- Don't set the buffer 'modified' for :PrintDuplicates and :PrintUniques.\r\n- Improve reporting of readonly buffers for :SubstituteExcept, :DeleteExcept, :SubstituteSelected, and :SubstituteSubsequent.\r\n- FIX: Misplaced :continue in s:Collect() safety check; must :return out of factored out function.","package":"PatternsOnText-1.51.vmb.gz","4":"PatternsOnText-1.51.vmb.gz","src_id":"22721","5":"22721","creation_date":"1419333718","6":"1419333718"},{"0":"4602","vim_version":"7.0","1":"7.0","script_version":"1.50","2":"1.50","version_comment":"- ENH: Add :PrintUniqueLinesOf, :DeleteUniqueLinesOf, :PrintUniqueLinesIgnoring, :DeleteUniqueLinesIgnoring, :PrintUniques, :DeleteUniques commands that are the opposite of the corresponding :...Duplicate... commands.","3":"- ENH: Add :PrintUniqueLinesOf, :DeleteUniqueLinesOf, :PrintUniqueLinesIgnoring, :DeleteUniqueLinesIgnoring, :PrintUniques, :DeleteUniques commands that are the opposite of the corresponding :...Duplicate... commands.","package":"PatternsOnText-1.50.vmb.gz","4":"PatternsOnText-1.50.vmb.gz","src_id":"22631","5":"22631","creation_date":"1416469117","6":"1416469117"},{"0":"4602","vim_version":"7.0","1":"7.0","script_version":"1.40","2":"1.40","version_comment":"- FIX: :SubstituteSubsequent can give \"E488: Trailing characters\". Previous search pattern must be properly escaped in case the separators are different.\r\n- Add :SubstituteNotInSearch, a combination of :SubstituteExcept and :SubstituteInSearch.","3":"- FIX: :SubstituteSubsequent can give \"E488: Trailing characters\". Previous search pattern must be properly escaped in case the separators are different.\r\n- Add :SubstituteNotInSearch, a combination of :SubstituteExcept and :SubstituteInSearch.","package":"PatternsOnText-1.40.vmb.gz","4":"PatternsOnText-1.40.vmb.gz","src_id":"22578","5":"22578","creation_date":"1414488289","6":"1414488289"},{"0":"4602","vim_version":"7.0","1":"7.0","script_version":"1.36","2":"1.36","version_comment":"- BUG: :.DeleteRange et al. don't work correctly on a closed fold; need to use ingo#range#NetStart().\r\n- BUG: :.DeleteDuplicateLines... et al. don't work correctly on a closed fold; need to use ingo#range#NetStart().\r\n- BUG: :SubstituteSubsequent doesn't work correctly on a closed fold; need to use ingo#range#NetStart().\r\n- Make the deletions work with closed folds (i.e. only delete the duplicate lines \/ lines in range itself, not the entire folds) by temporarily disabling folding.\r\n- Correctly report :PrintDuplicates on folded lines.\r\n- Refactoring: Use ingo#cmdargs#pattern#ParseUnescaped().\r\n- Factor out ingo#range#lines#Get() into ingo-library. *** You need to update to ingo-library (vimscript #4433) version 1.022! ***","3":"- BUG: :.DeleteRange et al. don't work correctly on a closed fold; need to use ingo#range#NetStart().\r\n- BUG: :.DeleteDuplicateLines... et al. don't work correctly on a closed fold; need to use ingo#range#NetStart().\r\n- BUG: :SubstituteSubsequent doesn't work correctly on a closed fold; need to use ingo#range#NetStart().\r\n- Make the deletions work with closed folds (i.e. only delete the duplicate lines \/ lines in range itself, not the entire folds) by temporarily disabling folding.\r\n- Correctly report :PrintDuplicates on folded lines.\r\n- Refactoring: Use ingo#cmdargs#pattern#ParseUnescaped().\r\n- Factor out ingo#range#lines#Get() into ingo-library. *** You need to update to ingo-library (vimscript #4433) version 1.022! ***","package":"PatternsOnText-1.36.vmb.gz","4":"PatternsOnText-1.36.vmb.gz","src_id":"22568","5":"22568","creation_date":"1414354109","6":"1414354109"},{"0":"4602","vim_version":"7.0","1":"7.0","script_version":"1.35","2":"1.35","version_comment":"- ENH: Allow to pass multiple ranges to the :*Ranges commands.\r\n- FIX: The *Ranges commands only handled \/{pattern}\/,... ranges, not line numbers or marks. Only use :global for patterns; for everything else, there's only a single range, so we can just prepend it to :call directly.\r\n- Don't clobber the search history with the :*Ranges commands (through using :global).\r\n- Add :RangeDo command.\r\n- ENH: Also support passing the search pattern inline with :SubstituteInSearch\/{search}\/{pattern}\/{string}\/[flags] instead of using the last search pattern.","3":"- ENH: Allow to pass multiple ranges to the :*Ranges commands.\r\n- FIX: The *Ranges commands only handled \/{pattern}\/,... ranges, not line numbers or marks. Only use :global for patterns; for everything else, there's only a single range, so we can just prepend it to :call directly.\r\n- Don't clobber the search history with the :*Ranges commands (through using :global).\r\n- Add :RangeDo command.\r\n- ENH: Also support passing the search pattern inline with :SubstituteInSearch\/{search}\/{pattern}\/{string}\/[flags] instead of using the last search pattern.","package":"PatternsOnText-1.35.vmb.gz","4":"PatternsOnText-1.35.vmb.gz","src_id":"21825","5":"21825","creation_date":"1398434096","6":"1398434096"},{"0":"4602","vim_version":"7.0","1":"7.0","script_version":"1.30","2":"1.30","version_comment":"- Add :DeleteAllDuplicateLinesIgnoring command.\r\n- CHG: The :[Print|Delete]DuplicateLines[ Of|Ignoring] commands do not automatically ignore empty lines any more. Use a {pattern} like ^$ to ignore them explicitly.\r\n- FIX: Wrong use of ingo#escape#Unescape().\r\n- ENH: Enable use of \\= sub-replace-expression in :SubstituteInSearch through emulation, as the command implementation itself uses \\=, Vim doesn't allow recursive use inside it. This has been inspired by http:\/\/stackoverflow.com\/questions\/21588649\/increment-numbers-between-delimiters-in-vim\r\n- Add :DeleteRanges, :YankRanges, :PrintRanges commands.\r\n- Handle \\r, \\n, \\t, \\b in {string}, too. *** You need to update to ingo-library (vimscript #4433) version 1.017! ***","3":"- Add :DeleteAllDuplicateLinesIgnoring command.\r\n- CHG: The :[Print|Delete]DuplicateLines[ Of|Ignoring] commands do not automatically ignore empty lines any more. Use a {pattern} like ^$ to ignore them explicitly.\r\n- FIX: Wrong use of ingo#escape#Unescape().\r\n- ENH: Enable use of \\= sub-replace-expression in :SubstituteInSearch through emulation, as the command implementation itself uses \\=, Vim doesn't allow recursive use inside it. This has been inspired by http:\/\/stackoverflow.com\/questions\/21588649\/increment-numbers-between-delimiters-in-vim\r\n- Add :DeleteRanges, :YankRanges, :PrintRanges commands.\r\n- Handle \\r, \\n, \\t, \\b in {string}, too. *** You need to update to ingo-library (vimscript #4433) version 1.017! ***","package":"PatternsOnText-1.30.vmb.gz","4":"PatternsOnText-1.30.vmb.gz","src_id":"21609","5":"21609","creation_date":"1394703861","6":"1394703861"},{"0":"4602","vim_version":"7.0","1":"7.0","script_version":"1.20","2":"1.20","version_comment":"- ENH: Add :SubstituteWildcard {wildcard}={string} and :SubstituteMultiple \/{pattern}\/{string}\/ commands. *** You need to update to ingo-library (vimscript #4433) version 1.016! ***","3":"- ENH: Add :SubstituteWildcard {wildcard}={string} and :SubstituteMultiple \/{pattern}\/{string}\/ commands. *** You need to update to ingo-library (vimscript #4433) version 1.016! ***","package":"PatternsOnText-1.20.vmb.gz","4":"PatternsOnText-1.20.vmb.gz","src_id":"21502","5":"21502","creation_date":"1392725711","6":"1392725711"},{"0":"4602","vim_version":"7.0","1":"7.0","script_version":"1.12","2":"1.12","version_comment":"- FIX: Use of \\v and \\V magicness atoms in the pattern for :DeleteExcept and :SubstituteExcept cause errors like \"E54: Unmatched (\" and \"E486: Pattern not found\". Revert to the default 'magic' mode after each pattern insertion to the workhorse regular expression.\r\n- FIX: Abort :DeleteExcept \/ :SubstituteExcept commands when the pattern contains the set start \/ end match patterns \\zs \/ \\ze, as these interfere with the internal implemenation.\r\n- Minor: Make substitute() and matchlist() robust against 'ignorecase'.","3":"- FIX: Use of \\v and \\V magicness atoms in the pattern for :DeleteExcept and :SubstituteExcept cause errors like \"E54: Unmatched (\" and \"E486: Pattern not found\". Revert to the default 'magic' mode after each pattern insertion to the workhorse regular expression.\r\n- FIX: Abort :DeleteExcept \/ :SubstituteExcept commands when the pattern contains the set start \/ end match patterns \\zs \/ \\ze, as these interfere with the internal implemenation.\r\n- Minor: Make substitute() and matchlist() robust against 'ignorecase'.","package":"PatternsOnText-1.12.vmb.gz","4":"PatternsOnText-1.12.vmb.gz","src_id":"21083","5":"21083","creation_date":"1385039886","6":"1385039886"},{"0":"4602","vim_version":"7.0","1":"7.0","script_version":"1.11","2":"1.11","version_comment":"- FIX: Remove -bar from all commands to correctly handle patterns like foo\\|bar without escaping as foo\\\\|bar.\r\n- :SubstituteSelected now positions the cursor on the line where the last selected replacement happened, to behave like :substitute.","3":"- FIX: Remove -bar from all commands to correctly handle patterns like foo\\|bar without escaping as foo\\\\|bar.\r\n- :SubstituteSelected now positions the cursor on the line where the last selected replacement happened, to behave like :substitute.","package":"PatternsOnText-1.11.vmb.gz","4":"PatternsOnText-1.11.vmb.gz","src_id":"20347","5":"20347","creation_date":"1371110333","6":"1371110333"},{"0":"4602","vim_version":"7.0","1":"7.0","script_version":"1.10","2":"1.10","version_comment":"- ENH: :SubstituteSelected handles count before \"y\" and \"n\" answers, numeric positions \"2,5\", and ranges \"3-5\".\r\n- Also recall previous answers in a bare :SubstituteSelected command.\r\n- The commands that take a {pattern}, i.e. :SubstituteExcept, :DeleteExcept, :SubstituteSelected now consistently set that as the last search pattern.\r\n- Refactoring: Move functions from ingo\/cmdargs.vim to ingo\/cmdargs\/pattern.vim and ingo\/cmdargs\/substitute.vim. *** You need to update to ingo-library (vimscript #4433) version 1.007! ***","3":"- ENH: :SubstituteSelected handles count before \"y\" and \"n\" answers, numeric positions \"2,5\", and ranges \"3-5\".\r\n- Also recall previous answers in a bare :SubstituteSelected command.\r\n- The commands that take a {pattern}, i.e. :SubstituteExcept, :DeleteExcept, :SubstituteSelected now consistently set that as the last search pattern.\r\n- Refactoring: Move functions from ingo\/cmdargs.vim to ingo\/cmdargs\/pattern.vim and ingo\/cmdargs\/substitute.vim. *** You need to update to ingo-library (vimscript #4433) version 1.007! ***","package":"PatternsOnText-1.10.vmb.gz","4":"PatternsOnText-1.10.vmb.gz","src_id":"20307","5":"20307","creation_date":"1370508866","6":"1370508866"},{"0":"4602","vim_version":"7.0","1":"7.0","script_version":"1.01","2":"1.01","version_comment":"Implement abort on error for :SubstituteExcept, :DeleteExcept, :SubstituteSelected, and :SubstituteInSearch, too.","3":"Implement abort on error for :SubstituteExcept, :DeleteExcept, :SubstituteSelected, and :SubstituteInSearch, too.","package":"PatternsOnText-1.01.vmb.gz","4":"PatternsOnText-1.01.vmb.gz","src_id":"20236","5":"20236","creation_date":"1369942984","6":"1369942984"},{"0":"4602","vim_version":"7.0","1":"7.0","script_version":"1.00","2":"1.00","version_comment":"Initial upload","3":"Initial upload","package":"PatternsOnText-1.00.vmb.gz","4":"PatternsOnText-1.00.vmb.gz","src_id":"20228","5":"20228","creation_date":"1369824982","6":"1369824982"}]},"4601":{"script_id":"4601","0":"4601","script_name":"grails-conque","1":"grails-conque","script_type":"utility","2":"utility","summary":"Run grails shell and unit\/integration tests inside vim","3":"Run grails shell and unit\/integration tests inside vim","description":"This script is still in early stages and updates often - I recommend cloning the github repo and submitting issues\/code there if you find problems or think of good features.\r\n\r\nGithub repo: https:\/\/github.com\/hoffoo\/vim-grails-console\r\n\r\nSimple plugin that uses ConqueTerm to run tests, interact with the shell, and use the grails console inside vim. Requires ConqueTerm http:\/\/www.vim.org\/scripts\/script.php?script_id=2771\r\n\r\nYou can either run the entire test file or the test function under your cursor.\r\n\r\n\" Start the grails shell\r\n:StartGrailsConque\r\n\r\n\" Run the current file as a Grails test\r\n:GrailsRunTestFile\r\n\r\n\" Run the Test under the cursor\r\n:GrailsRunCurrentTest\r\n\r\n\" You can also run a test by name\r\n:GrailsRunTest TestName\r\n\r\n\" Rerun the last test\r\n:GrailsReRun\r\n\" Settings:\r\n\r\n\" NOTE: all the keymappings apply only to the _grails_ buffer so not to conflict\r\n\" with the rest of your setup\r\n\r\n\" set this to open the shell buffer across the bottom in a split\r\nlet g:GrailsShellStartSplit = 1\r\n\r\n\" remap an insert mode key to switch back to previous buffer\r\nlet g:GrailsShellReturnKey = \"<C-w><C-w>\"\r\n\r\n\" if this is set insert mode backspace will be remapped to <C-w> to delete \r\n\" whole word backwards\r\nlet g:GrailsShellRemapBS = 1\r\n\r\n\" command that will be passed the tests url when running :GrailsTestsBrowser\r\nlet g:GrailsTestsBrowser = \"chromium --app=file:\/\/\"\r\n\r\n\" You can override the path to the grails executable using:\r\n\" default is grails\r\nlet g:GrailsShellExecutable = \"\/opt\/grails\/bin\/grails\"\r\n\r\n\r\n\" Recommended Conque settings\r\nlet g:ConqueTerm_ReadUnfocused = 1 \" run while not the selected window\r\nlet g:ConqueTerm_CloseOnEnd = 1 \" quit grails when done\r\nYou can open a browser frame to show the html output of your tests:\r\n\r\n\" this is the executable that will be ran when opening the test result pages\r\n\" open in chromium\/google-chrome frame with no tabs\r\nlet g:GrailsTestsBrowser = 'chromium --app=file:\/\/' \r\nlet g:GrailsTestsBrowser = 'firefox ' \" NOTE: notice the space\r\n\r\n\" open with regular tab\r\nlet g:GrailsTestsBrowser = '\/usr\/bin\/google-chrome ' \r\n\r\n\" and then to open the browser with\r\n:GrailsTestsBrowser\r\n\r\n=== Console ===\r\nProvided you have the grails-console plugin you can run scripts directly to the grails app from vim. To do this either copy, or link the RunConsole.groovy file to the scripts directory within your grails project.\r\n\r\n:GrailsRunConsole <filename>.groovy \" send the file to groovy console\r\n\r\n\" Note that by default :GrailsReRun will only rerun tests - to enable\r\n\" rerun of console set the option \r\n\r\nlet g:GrailsReRunConsole = 1\r\n\r\nThe default behaviour is to enter insert mode after switching back to the grails buffer so Conque will update. This way it does not override the g:ConqueTerm_InsertOnEnter. You can disable this with g:GrailsShellInsertOnEnter.\r\n\r\nTODO:\r\n- Search upwards if we are in a sub directory of a grails project\r\n- Regex upwards to find the test function name, rather than passing it with the cursor\r\n\r\nResources: http:\/\/www.objectpartners.com\/2012\/02\/28\/using-vim-as-your-grails-ide-part-2\/","4":"This script is still in early stages and updates often - I recommend cloning the github repo and submitting issues\/code there if you find problems or think of good features.\r\n\r\nGithub repo: https:\/\/github.com\/hoffoo\/vim-grails-console\r\n\r\nSimple plugin that uses ConqueTerm to run tests, interact with the shell, and use the grails console inside vim. Requires ConqueTerm http:\/\/www.vim.org\/scripts\/script.php?script_id=2771\r\n\r\nYou can either run the entire test file or the test function under your cursor.\r\n\r\n\" Start the grails shell\r\n:StartGrailsConque\r\n\r\n\" Run the current file as a Grails test\r\n:GrailsRunTestFile\r\n\r\n\" Run the Test under the cursor\r\n:GrailsRunCurrentTest\r\n\r\n\" You can also run a test by name\r\n:GrailsRunTest TestName\r\n\r\n\" Rerun the last test\r\n:GrailsReRun\r\n\" Settings:\r\n\r\n\" NOTE: all the keymappings apply only to the _grails_ buffer so not to conflict\r\n\" with the rest of your setup\r\n\r\n\" set this to open the shell buffer across the bottom in a split\r\nlet g:GrailsShellStartSplit = 1\r\n\r\n\" remap an insert mode key to switch back to previous buffer\r\nlet g:GrailsShellReturnKey = \"<C-w><C-w>\"\r\n\r\n\" if this is set insert mode backspace will be remapped to <C-w> to delete \r\n\" whole word backwards\r\nlet g:GrailsShellRemapBS = 1\r\n\r\n\" command that will be passed the tests url when running :GrailsTestsBrowser\r\nlet g:GrailsTestsBrowser = \"chromium --app=file:\/\/\"\r\n\r\n\" You can override the path to the grails executable using:\r\n\" default is grails\r\nlet g:GrailsShellExecutable = \"\/opt\/grails\/bin\/grails\"\r\n\r\n\r\n\" Recommended Conque settings\r\nlet g:ConqueTerm_ReadUnfocused = 1 \" run while not the selected window\r\nlet g:ConqueTerm_CloseOnEnd = 1 \" quit grails when done\r\nYou can open a browser frame to show the html output of your tests:\r\n\r\n\" this is the executable that will be ran when opening the test result pages\r\n\" open in chromium\/google-chrome frame with no tabs\r\nlet g:GrailsTestsBrowser = 'chromium --app=file:\/\/' \r\nlet g:GrailsTestsBrowser = 'firefox ' \" NOTE: notice the space\r\n\r\n\" open with regular tab\r\nlet g:GrailsTestsBrowser = '\/usr\/bin\/google-chrome ' \r\n\r\n\" and then to open the browser with\r\n:GrailsTestsBrowser\r\n\r\n=== Console ===\r\nProvided you have the grails-console plugin you can run scripts directly to the grails app from vim. To do this either copy, or link the RunConsole.groovy file to the scripts directory within your grails project.\r\n\r\n:GrailsRunConsole <filename>.groovy \" send the file to groovy console\r\n\r\n\" Note that by default :GrailsReRun will only rerun tests - to enable\r\n\" rerun of console set the option \r\n\r\nlet g:GrailsReRunConsole = 1\r\n\r\nThe default behaviour is to enter insert mode after switching back to the grails buffer so Conque will update. This way it does not override the g:ConqueTerm_InsertOnEnter. You can disable this with g:GrailsShellInsertOnEnter.\r\n\r\nTODO:\r\n- Search upwards if we are in a sub directory of a grails project\r\n- Regex upwards to find the test function name, rather than passing it with the cursor\r\n\r\nResources: http:\/\/www.objectpartners.com\/2012\/02\/28\/using-vim-as-your-grails-ide-part-2\/","install_details":"Install ConqueTerm: http:\/\/www.vim.org\/scripts\/script.php?script_id=2771","5":"Install ConqueTerm: http:\/\/www.vim.org\/scripts\/script.php?script_id=2771","first_name":"Marin","6":"Marin","last_name":"Staykov","7":"Staykov","releases":[{"0":"4601","vim_version":"7.0","1":"7.0","script_version":"0.4","2":"0.4","version_comment":"Add support for VAM","3":"Add support for VAM","package":"grails-conque.tgz","4":"grails-conque.tgz","src_id":"20353","5":"20353","creation_date":"1371140391","6":"1371140391"},{"0":"4601","vim_version":"7.0","1":"7.0","script_version":"0.3","2":"0.3","version_comment":"fixed startup annoyances","3":"fixed startup annoyances","package":"grails-conque.tgz","4":"grails-conque.tgz","src_id":"20284","5":"20284","creation_date":"1370365180","6":"1370365180"},{"0":"4601","vim_version":"7.0","1":"7.0","script_version":"0.3","2":"0.3","version_comment":"Grails Console Integration and minor refactoring","3":"Grails Console Integration and minor refactoring","package":"grails-conque.tgz","4":"grails-conque.tgz","src_id":"20272","5":"20272","creation_date":"1370241056","6":"1370241056"},{"0":"4601","vim_version":"7.0","1":"7.0","script_version":"0.2","2":"0.2","version_comment":"more sensible browser config\r\noption to remap <BS>\r\noption to remap key to return from the shell buffer to prev buffer\r\ngeneral cleanup","3":"more sensible browser config\r\noption to remap <BS>\r\noption to remap key to return from the shell buffer to prev buffer\r\ngeneral cleanup","package":"grails-conque.tgz","4":"grails-conque.tgz","src_id":"20269","5":"20269","creation_date":"1370204612","6":"1370204612"},{"0":"4601","vim_version":"7.0","1":"7.0","script_version":"0.2","2":"0.2","version_comment":"ReRun unit tests, Open test results in browser, option to always open in :botright split ","3":"ReRun unit tests, Open test results in browser, option to always open in :botright split ","package":"grails-conque.tgz","4":"grails-conque.tgz","src_id":"20267","5":"20267","creation_date":"1370194982","6":"1370194982"},{"0":"4601","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"grails-conque.tgz","4":"grails-conque.tgz","src_id":"20226","5":"20226","creation_date":"1369792825","6":"1369792825"}]},"4600":{"script_id":"4600","0":"4600","script_name":"Sprunge Paste Upload","1":"Sprunge Paste Upload","script_type":"utility","2":"utility","summary":"Loading your code quickly on Sprunge","3":"Loading your code quickly on Sprunge","description":"Load and share your code fastly with friends wasn't never so simple.","4":"Load and share your code fastly with friends wasn't never so simple.","install_details":"","5":"","first_name":"Ciro","6":"Ciro","last_name":"Somma","7":"Somma","releases":[{"0":"4600","vim_version":"5.7","1":"5.7","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"sprunge.vim","4":"sprunge.vim","src_id":"20224","5":"20224","creation_date":"1369681683","6":"1369681683"}]},"4599":{"script_id":"4599","0":"4599","script_name":"videm","1":"videm","script_type":"utility","2":"utility","summary":"Vim's IDE Mode","3":"Vim's IDE Mode","description":"Videm (Vim's IDE Mode) is a C\/C++ IDE  based on vim (will become a common IDE framework in future, I think).\r\nIt named VimLite in past before I make it to a framework.\r\nVidem is compatible with VimLite about configuration.\r\nBut all commands which in VimLite are renamed in videm, please run ':h videm.txt' for more information after installation.\r\n\r\nVidem mainly consists of the following modules:\r\n1.Project Manager:\r\n    The project management module is compatible with CodeLite 2.10. It will auto generates makefile for you.\r\n2.Code Completion:\r\n    An enhanced OmniCpp and a VIMCCC plugin.\r\n        OmniCpp - Support the following completion: namespace, structure, class member, using, using namespace, class template, stl, etc.\r\n        VIMCCC - An Omni cpp code completion plugin which based on libclang.\r\n        OmniCxx(Experimental) - A new simple code complete engine for C\/C++, currently only support C and simple C++ without template.\r\n3. Symbol Database:\r\n    Cscope and gnu global.\r\n4.Debugger Integration:\r\n    Gdb integration, by pyclewn. \r\n\r\nPlease read videm.txt help file for more information.\r\nAnd you also can reference the VimLite project http:\/\/www.vim.org\/scripts\/script.php?script_id=3647","4":"Videm (Vim's IDE Mode) is a C\/C++ IDE  based on vim (will become a common IDE framework in future, I think).\r\nIt named VimLite in past before I make it to a framework.\r\nVidem is compatible with VimLite about configuration.\r\nBut all commands which in VimLite are renamed in videm, please run ':h videm.txt' for more information after installation.\r\n\r\nVidem mainly consists of the following modules:\r\n1.Project Manager:\r\n    The project management module is compatible with CodeLite 2.10. It will auto generates makefile for you.\r\n2.Code Completion:\r\n    An enhanced OmniCpp and a VIMCCC plugin.\r\n        OmniCpp - Support the following completion: namespace, structure, class member, using, using namespace, class template, stl, etc.\r\n        VIMCCC - An Omni cpp code completion plugin which based on libclang.\r\n        OmniCxx(Experimental) - A new simple code complete engine for C\/C++, currently only support C and simple C++ without template.\r\n3. Symbol Database:\r\n    Cscope and gnu global.\r\n4.Debugger Integration:\r\n    Gdb integration, by pyclewn. \r\n\r\nPlease read videm.txt help file for more information.\r\nAnd you also can reference the VimLite project http:\/\/www.vim.org\/scripts\/script.php?script_id=3647","install_details":"Prerequisites:\r\n\r\nMake sure your vim's version is 7.3.196 or later and compile with this features: \r\n    +python\r\n    +netbeans_intg (required by debugger)\r\n\r\nVidem depends following software: \r\n    python\r\n    python-lxml (optional)\r\n    make\r\n    cscope\r\n    global\r\n    gcc\r\n    gdb\r\n    libclang (version 3.0, required by VIMCCC)\r\n\r\nOn ubuntu (10.04), just run: \r\n    sudo apt-get install python python-lxml build-essential gdb cscope global\r\n\r\nOn Windows, just installs python 2.x (2.6 or later) and pywin32(for pyclewn) from http:\/\/sourceforge.net\/projects\/pywin32\/files\/pywin32\/\r\n\r\nAnd make sure you have these settings in your vimrc file: \r\n    set nocp\r\n    filetype plugin on\r\n    syntax on\r\n\r\nVidem Installation (Linux):\r\n1. Download videm-<version>-<build>.tar.bz2 and extract it\r\n2. Put everything which in videm folder to ~\/.vim, or put videm to ~\/.vim\/bundle if you use pathogen\r\n\r\nAfter above steps, you can open videm workspace. Just run\r\n:VidemOpen <workspace-name>.vlworkspace\r\n\r\n3. If you wish use VIMCCC, please install libclang 3.0\r\n4. If you wish use OmniCpp or OmniCxx, please install videm-tools\r\n\r\nVidem-tools Installation(Linux):\r\n1. Download videm-tools-<version>.tar.bz2 and extract it\r\n2. Open videm workspace\r\n3. Run 'Release' Batch Build (press '.' and select the menu)\r\n4. After step 3, videm generates a videm folder in the root of videm-tools-{version} folder, just run \"cp -r videm\/* ~\/.vim\/_videm\" or \"cp -r videm\/* ~\/.vim\/bundle\/videm\/_videm\" if you use pathogen\r\n\r\nInstallation(Windows):\r\n1. Download videm-<version>-<build>.tar.bz2 and extract it\r\n2. Put everything which in videm folder to $VIM\\vimfiles (for example of mine: C:\\Program Files\\Vim\\vimfiles) or put videm folder to $VIM\\vimfiles\\bundle if you use pathogen\r\n3. Download win32bin-<version>.zip and extract it and put all files(exes and dlls) into $VIM\\vimfiles\\_videm\\bin or $VIM\\vimfiles\\bundle\\videm\\_videm\\bin if you use pathogen, and add this folder to the environment variable PATH\r\n4. Install MinGW 4.x. You can download MinGW-4.4.1.7z in http:\/\/code.google.com\/p\/vimlite\/downloads\/detail?name=MinGW-4.4.1.7z\r\n5. Add bin folder path (mine is D:\\MinGW-4.4.1\\bin) of MinGW to the environment variable PATH\r\n6. Download videm-tools-<version>-win32.zip and extract it and put all folder (bin and lib) into $VIM\\vimfiles\\_videm\\bin or $VIM\\vimfiles\\bundle\\videm\\_videm\\bin if you use pathogen\r\n7. (Optional) If you wish use code completion engine based on libclang, install libclang 3.0\r\n\r\nMigrate From Old Version:\r\nSince videm-1100, the folder placement is changed, so you need do some migration.\r\n1. Just move ~\/.videm\/* to ~\/.vim\/_videm\/ or ~\/.vim\/bundle\/_videm\/ if you use pathogen. On Windows just move $VIM\\videm\\* to $VIM\\vimfiles\\_videm\\* or $VIM\/vimfiles\\bundle\\_videm\\ if you use pathogen.\r\n2. Install the latest videm\r\n\r\nOthers:\r\n\r\nNOTE: Macros for OmniCpp need update for glibc 4.7. Add the followings to 'Macros:' of Videm->'OmniCpp Tags Settings...' - 2013-12-11\r\n\/\/ glibc 4.7\r\n#define _GLIBCXX_NOEXCEPT\r\n#define noexcept\r\n\r\nDonate:\r\n    If you like Videm and want to help me to develop, you can give me some coins :-).\r\n    My bitcoin wallet: 1E8iBxZWPh8vqEoGGMDZVBJV2gVF4hySny","5":"Prerequisites:\r\n\r\nMake sure your vim's version is 7.3.196 or later and compile with this features: \r\n    +python\r\n    +netbeans_intg (required by debugger)\r\n\r\nVidem depends following software: \r\n    python\r\n    python-lxml (optional)\r\n    make\r\n    cscope\r\n    global\r\n    gcc\r\n    gdb\r\n    libclang (version 3.0, required by VIMCCC)\r\n\r\nOn ubuntu (10.04), just run: \r\n    sudo apt-get install python python-lxml build-essential gdb cscope global\r\n\r\nOn Windows, just installs python 2.x (2.6 or later) and pywin32(for pyclewn) from http:\/\/sourceforge.net\/projects\/pywin32\/files\/pywin32\/\r\n\r\nAnd make sure you have these settings in your vimrc file: \r\n    set nocp\r\n    filetype plugin on\r\n    syntax on\r\n\r\nVidem Installation (Linux):\r\n1. Download videm-<version>-<build>.tar.bz2 and extract it\r\n2. Put everything which in videm folder to ~\/.vim, or put videm to ~\/.vim\/bundle if you use pathogen\r\n\r\nAfter above steps, you can open videm workspace. Just run\r\n:VidemOpen <workspace-name>.vlworkspace\r\n\r\n3. If you wish use VIMCCC, please install libclang 3.0\r\n4. If you wish use OmniCpp or OmniCxx, please install videm-tools\r\n\r\nVidem-tools Installation(Linux):\r\n1. Download videm-tools-<version>.tar.bz2 and extract it\r\n2. Open videm workspace\r\n3. Run 'Release' Batch Build (press '.' and select the menu)\r\n4. After step 3, videm generates a videm folder in the root of videm-tools-{version} folder, just run \"cp -r videm\/* ~\/.vim\/_videm\" or \"cp -r videm\/* ~\/.vim\/bundle\/videm\/_videm\" if you use pathogen\r\n\r\nInstallation(Windows):\r\n1. Download videm-<version>-<build>.tar.bz2 and extract it\r\n2. Put everything which in videm folder to $VIM\\vimfiles (for example of mine: C:\\Program Files\\Vim\\vimfiles) or put videm folder to $VIM\\vimfiles\\bundle if you use pathogen\r\n3. Download win32bin-<version>.zip and extract it and put all files(exes and dlls) into $VIM\\vimfiles\\_videm\\bin or $VIM\\vimfiles\\bundle\\videm\\_videm\\bin if you use pathogen, and add this folder to the environment variable PATH\r\n4. Install MinGW 4.x. You can download MinGW-4.4.1.7z in http:\/\/code.google.com\/p\/vimlite\/downloads\/detail?name=MinGW-4.4.1.7z\r\n5. Add bin folder path (mine is D:\\MinGW-4.4.1\\bin) of MinGW to the environment variable PATH\r\n6. Download videm-tools-<version>-win32.zip and extract it and put all folder (bin and lib) into $VIM\\vimfiles\\_videm\\bin or $VIM\\vimfiles\\bundle\\videm\\_videm\\bin if you use pathogen\r\n7. (Optional) If you wish use code completion engine based on libclang, install libclang 3.0\r\n\r\nMigrate From Old Version:\r\nSince videm-1100, the folder placement is changed, so you need do some migration.\r\n1. Just move ~\/.videm\/* to ~\/.vim\/_videm\/ or ~\/.vim\/bundle\/_videm\/ if you use pathogen. On Windows just move $VIM\\videm\\* to $VIM\\vimfiles\\_videm\\* or $VIM\/vimfiles\\bundle\\_videm\\ if you use pathogen.\r\n2. Install the latest videm\r\n\r\nOthers:\r\n\r\nNOTE: Macros for OmniCpp need update for glibc 4.7. Add the followings to 'Macros:' of Videm->'OmniCpp Tags Settings...' - 2013-12-11\r\n\/\/ glibc 4.7\r\n#define _GLIBCXX_NOEXCEPT\r\n#define noexcept\r\n\r\nDonate:\r\n    If you like Videm and want to help me to develop, you can give me some coins :-).\r\n    My bitcoin wallet: 1E8iBxZWPh8vqEoGGMDZVBJV2gVF4hySny","first_name":"fanhe","6":"fanhe","last_name":" ","7":" ","releases":[{"0":"4599","vim_version":"7.3","1":"7.3","script_version":"1.102","2":"1.102","version_comment":"- Fixed a located file issue on old version vim","3":"- Fixed a located file issue on old version vim","package":"videm-1102-build20140213.tar.bz2","4":"videm-1102-build20140213.tar.bz2","src_id":"21478","5":"21478","creation_date":"1392306834","6":"1392306834"},{"0":"4599","vim_version":"7.3","1":"7.3","script_version":"1.101","2":"1.101","version_comment":"- Fixed some open file issues","3":"- Fixed some open file issues","package":"videm-1101-build20140211.tar.bz2","4":"videm-1101-build20140211.tar.bz2","src_id":"21463","5":"21463","creation_date":"1392117797","6":"1392117797"},{"0":"4599","vim_version":"7.3","1":"7.3","script_version":"1.100","2":"1.100","version_comment":"- Added a new experimental code complete engine called omnicxx\r\n- Added VPlugInfo command to show the plugin info\r\n- Fixed a gtags updating issue on Windows\r\n- Added asynchronous code complete framework for vimccc and omnicxx\r\n\r\nNOTE1: This version change many things, please read above \"Migrate From Old Version\"\r\nNOTE2: This version require vim 7.3.196 or later because the \"InsertCharPre\" autocmd","3":"- Added a new experimental code complete engine called omnicxx\r\n- Added VPlugInfo command to show the plugin info\r\n- Fixed a gtags updating issue on Windows\r\n- Added asynchronous code complete framework for vimccc and omnicxx\r\n\r\nNOTE1: This version change many things, please read above \"Migrate From Old Version\"\r\nNOTE2: This version require vim 7.3.196 or later because the \"InsertCharPre\" autocmd","package":"videm-1100-build20140127.tar.bz2","4":"videm-1100-build20140127.tar.bz2","src_id":"21383","5":"21383","creation_date":"1390755480","6":"1390755480"},{"0":"4599","vim_version":"7.3","1":"7.3","script_version":"1.015","2":"1.015","version_comment":"- Fixed some error in help file videm.txt\r\n- Fixed a omnicpp decode issue\r\n- Fixed a environment variables setting issue\r\n- Fixed a command running issue in vim which run without X","3":"- Fixed some error in help file videm.txt\r\n- Fixed a omnicpp decode issue\r\n- Fixed a environment variables setting issue\r\n- Fixed a command running issue in vim which run without X","package":"videm-1015-build20131211.tar.bz2","4":"videm-1015-build20131211.tar.bz2","src_id":"21185","5":"21185","creation_date":"1386769004","6":"1386769004"},{"0":"4599","vim_version":"7.3","1":"7.3","script_version":"1.014","2":"1.014","version_comment":"- Added limited supporting of special working path of workspace, eg contains Chinese\r\n\r\nNOTE: The debugger do not support special working path currently.","3":"- Added limited supporting of special working path of workspace, eg contains Chinese\r\n\r\nNOTE: The debugger do not support special working path currently.","package":"videm-1014-build20131208.tar.bz2","4":"videm-1014-build20131208.tar.bz2","src_id":"21174","5":"21174","creation_date":"1386492046","6":"1386492046"},{"0":"4599","vim_version":"7.3","1":"7.3","script_version":"1.013","2":"1.013","version_comment":"- Fiexd a issue that cannot create new file on Windows\r\n- Added some sanity check for adding files and virtual directories\r\n- Fiexd a issue that displaying CWD in adding files dialog","3":"- Fiexd a issue that cannot create new file on Windows\r\n- Added some sanity check for adding files and virtual directories\r\n- Fiexd a issue that displaying CWD in adding files dialog","package":"videm-1013-build20131124.tar.bz2","4":"videm-1013-build20131124.tar.bz2","src_id":"21097","5":"21097","creation_date":"1385269829","6":"1385269829"},{"0":"4599","vim_version":"7.3","1":"7.3","script_version":"1.012","2":"1.012","version_comment":"- Fixed gtags updating issue on Windows\r\n- Ignore invalid project file when adding an existing project","3":"- Fixed gtags updating issue on Windows\r\n- Ignore invalid project file when adding an existing project","package":"videm-1012-Build20131030.tar.bz2","4":"videm-1012-Build20131030.tar.bz2","src_id":"20981","5":"20981","creation_date":"1383141177","6":"1383141177"},{"0":"4599","vim_version":"7.3","1":"7.3","script_version":"1.011","2":"1.011","version_comment":"- Fixed a symbol database init issue\r\n- Improved \"Workspace Settings\"\r\n- Added \"g:videm_user_options\" global variable for set user options quickly\r\n- Update help file videm.txt about new options\r\n- Fixed some other issues","3":"- Fixed a symbol database init issue\r\n- Improved \"Workspace Settings\"\r\n- Added \"g:videm_user_options\" global variable for set user options quickly\r\n- Update help file videm.txt about new options\r\n- Fixed some other issues","package":"videm-1011-Build20131022.tar.bz2","4":"videm-1011-Build20131022.tar.bz2","src_id":"20944","5":"20944","creation_date":"1382451369","6":"1382451369"},{"0":"4599","vim_version":"7.3","1":"7.3","script_version":"1.1.0","2":"1.1.0","version_comment":"- videm-tools for windows 32bit","3":"- videm-tools for windows 32bit","package":"videm-tools-1.1.0-win32.zip","4":"videm-tools-1.1.0-win32.zip","src_id":"20911","5":"20911","creation_date":"1381496947","6":"1381496947"},{"0":"4599","vim_version":"7.3","1":"7.3","script_version":"1.0.0","2":"1.0.0","version_comment":"- Required programs for windows 32bit.","3":"- Required programs for windows 32bit.","package":"win32bin-1.0.0.zip","4":"win32bin-1.0.0.zip","src_id":"20910","5":"20910","creation_date":"1381496716","6":"1381496716"},{"0":"4599","vim_version":"7.3","1":"7.3","script_version":"1.010","2":"1.010","version_comment":"- Supported session, added option '.videm.wsp.AutoSession': 0\r\n- Added option '.videm.symdb.Quickfix': 1\r\n- Added commands VSymbolDatabaseInit and VSymbolDatabaseUpdate\r\n- Added option '.videm.wsp.EnablePopUpMenu': 1\r\n- Added Cut\/Paste nodes operations of workspace, press <F1> in workspace buffer for more information\r\n- Supported store file node under project node\r\n- Added separating settings of code complete engine for per config of project\r\n- Added VSearchSymbol* serial commands","3":"- Supported session, added option '.videm.wsp.AutoSession': 0\r\n- Added option '.videm.symdb.Quickfix': 1\r\n- Added commands VSymbolDatabaseInit and VSymbolDatabaseUpdate\r\n- Added option '.videm.wsp.EnablePopUpMenu': 1\r\n- Added Cut\/Paste nodes operations of workspace, press <F1> in workspace buffer for more information\r\n- Supported store file node under project node\r\n- Added separating settings of code complete engine for per config of project\r\n- Added VSearchSymbol* serial commands","package":"videm-1010-Build20131011.tar.bz2","4":"videm-1010-Build20131011.tar.bz2","src_id":"20909","5":"20909","creation_date":"1381496083","6":"1381496083"},{"0":"4599","vim_version":"7.3","1":"7.3","script_version":"1.004","2":"1.004","version_comment":"- Changed VLWDbg* commands to VDbg*\r\n- Improved OmniCpp tags database performance.\r\n- Fixed a workspace buffer refresh issue after add a new project.","3":"- Changed VLWDbg* commands to VDbg*\r\n- Improved OmniCpp tags database performance.\r\n- Fixed a workspace buffer refresh issue after add a new project.","package":"videm-1004.tar.xz","4":"videm-1004.tar.xz","src_id":"20331","5":"20331","creation_date":"1370840217","6":"1370840217"},{"0":"4599","vim_version":"7.3","1":"7.3","script_version":"1.003","2":"1.003","version_comment":" - Fixed a VIMCCC auto code completing issue.\r\n - Fixed some other bugs.\r\n - Updated help file.","3":" - Fixed a VIMCCC auto code completing issue.\r\n - Fixed some other bugs.\r\n - Updated help file.","package":"videm-1003.tar.xz","4":"videm-1003.tar.xz","src_id":"20266","5":"20266","creation_date":"1370182464","6":"1370182464"},{"0":"4599","vim_version":"7.3","1":"7.3","script_version":"1.002","2":"1.002","version_comment":" - Updated videm.txt help file.\r\n - Fixed a vimccc issue about finding libclang.so.","3":" - Updated videm.txt help file.\r\n - Fixed a vimccc issue about finding libclang.so.","package":"videm-1002.tar.xz","4":"videm-1002.tar.xz","src_id":"20229","5":"20229","creation_date":"1369836336","6":"1369836336"},{"0":"4599","vim_version":"7.3","1":"7.3","script_version":"1.001","2":"1.001","version_comment":"First Release","3":"First Release","package":"videm-1001.tar.gz","4":"videm-1001.tar.gz","src_id":"20222","5":"20222","creation_date":"1369665916","6":"1369665916"},{"0":"4599","vim_version":"7.3","1":"7.3","script_version":"1.001","2":"1.001","version_comment":"Initial upload","3":"Initial upload","package":"videm-tools-1.1.0.tar.bz2","4":"videm-tools-1.1.0.tar.bz2","src_id":"20221","5":"20221","creation_date":"1369665697","6":"1369665697"}]},"4598":{"script_id":"4598","0":"4598","script_name":"rainbow_csv.vim","1":"rainbow_csv.vim","script_type":"syntax","2":"syntax","summary":"Highlight columns in csv\/tsv files and run SELECT queries in SQL-like language","3":"Highlight columns in csv\/tsv files and run SELECT queries in SQL-like language","description":"Rainbow CSV has 2 main features:\r\n\r\n* Highlights csv columns in different rainbow colors.\r\n* Provides SELECT and UPDATE queries in RBQL: SQL-like transprogramming query language.\r\n\r\nDemonstration gif:\r\nhttps:\/\/i.imgur.com\/Tnk9KZv.gif\r\n\r\nThere are 2 ways to enable csv columns highlighting:\r\n* CSV autodetection based on file content. File extension doesn't have to be .csv or .tsv\r\n* Manual CSV delimiter selection with :RainbowDelim command (So you can use rainbow_csv for non-table files, e.g. to highlight function arguments in different colors)\r\n\r\nTo run an RBQL query either press F5 or enter the query in vim command line e.g. :Select a1, a2\r\n\r\nMore info can be found here: https:\/\/github.com\/mechatroner\/rainbow_csv","4":"Rainbow CSV has 2 main features:\r\n\r\n* Highlights csv columns in different rainbow colors.\r\n* Provides SELECT and UPDATE queries in RBQL: SQL-like transprogramming query language.\r\n\r\nDemonstration gif:\r\nhttps:\/\/i.imgur.com\/Tnk9KZv.gif\r\n\r\nThere are 2 ways to enable csv columns highlighting:\r\n* CSV autodetection based on file content. File extension doesn't have to be .csv or .tsv\r\n* Manual CSV delimiter selection with :RainbowDelim command (So you can use rainbow_csv for non-table files, e.g. to highlight function arguments in different colors)\r\n\r\nTo run an RBQL query either press F5 or enter the query in vim command line e.g. :Select a1, a2\r\n\r\nMore info can be found here: https:\/\/github.com\/mechatroner\/rainbow_csv","install_details":"https:\/\/github.com\/mechatroner\/rainbow_csv","5":"https:\/\/github.com\/mechatroner\/rainbow_csv","first_name":"Dmitry","6":"Dmitry","last_name":"Ignatovich","7":"Ignatovich","releases":[{"0":"4598","vim_version":"7.3","1":"7.3","script_version":"4.3.0","2":"4.3.0","version_comment":"* Redesigned syntax logic: added support for conventional Vim filetypes\r\n* Support newlines in CSV fields\r\n* Support multicharacter separators\r\n* Updated RBQL\r\n* Bug fixes and usability improvements","3":"* Redesigned syntax logic: added support for conventional Vim filetypes\r\n* Support newlines in CSV fields\r\n* Support multicharacter separators\r\n* Updated RBQL\r\n* Bug fixes and usability improvements","package":"rainbow_csv-master.zip","4":"rainbow_csv-master.zip","src_id":"26822","5":"26822","creation_date":"1573554144","6":"1573554144"},{"0":"4598","vim_version":"7.3","1":"7.3","script_version":"4.0","2":"4.0","version_comment":"Usability improvements","3":"Usability improvements","package":"rainbow_csv-master.zip","4":"rainbow_csv-master.zip","src_id":"26027","5":"26027","creation_date":"1528123317","6":"1528123317"},{"0":"4598","vim_version":"7.3","1":"7.3","script_version":"3.0","2":"3.0","version_comment":"Correct handling of quoted commas; Built-in SQL-like RBQL query language which supports SELECT, TOP, WHERE, ORDER BY, UPDATE, JOIN and other keywords; ","3":"Correct handling of quoted commas; Built-in SQL-like RBQL query language which supports SELECT, TOP, WHERE, ORDER BY, UPDATE, JOIN and other keywords; ","package":"rainbow_csv-master.zip","4":"rainbow_csv-master.zip","src_id":"25629","5":"25629","creation_date":"1509325942","6":"1509325942"},{"0":"4598","vim_version":"7.0","1":"7.0","script_version":"2.0","2":"2.0","version_comment":"Persistent settings for files. Added 'header' feature. See github page for more info.","3":"Persistent settings for files. Added 'header' feature. See github page for more info.","package":"rainbow_csv-master.zip","4":"rainbow_csv-master.zip","src_id":"24083","5":"24083","creation_date":"1457582415","6":"1457582415"},{"0":"4598","vim_version":"7.3","1":"7.3","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"rainbow_csv.zip","4":"rainbow_csv.zip","src_id":"20204","5":"20204","creation_date":"1369480952","6":"1369480952"}]},"4597":{"script_id":"4597","0":"4597","script_name":"vim-misc","1":"vim-misc","script_type":"utility","2":"utility","summary":"Miscellaneous auto-load Vim scripts","3":"Miscellaneous auto-load Vim scripts","description":"This plug-in contains Vim scripts that are used by most of the Vim plug-ins I've written yet don't really belong with any single one of the plug-ins. Basically it's an extended standard library of Vim script functions that I wrote during the development of my Vim profile and plug-ins.\r\n\r\nIn the past these scripts were bundled with each plug-in, however that turned out to be a maintenance nightmare for me. That's why the miscellaneous scripts are now a proper plug-in with their own page on Vim Online.\r\n\r\nFor more information about the miscellaneous scripts please refer to the homepage or the project page on GitHub:\r\n\r\n\u00c2\u00a0\u00e2\u0080\u00a2 http:\/\/peterodding.com\/code\/vim\/misc\/ \r\n\u00c2\u00a0\u00e2\u0080\u00a2 http:\/\/github.com\/xolox\/vim-misc\r\n\r\nIf you have questions, bug reports, suggestions, etc. the author can be contacted at peter@peterodding.com. If you like this plug-in please vote for it below!\r\n\r\nThe following plug-ins of mine depend on the installation of the miscellaneous scripts as a separate plug-in:\r\n\r\n\u00c2\u00a0\u00e2\u0080\u00a2 vim-colorscheme-switcher (vimscript #4586)\r\n\u00c2\u00a0\u00e2\u0080\u00a2 vim-easytags (vimscript #3114)\r\n\u00c2\u00a0\u00e2\u0080\u00a2 vim-lua-ftplugin (vimscript #3625)\r\n\u00c2\u00a0\u00e2\u0080\u00a2 vim-lua-inspect (vimscript #3169)\r\n\u00c2\u00a0\u00e2\u0080\u00a2 vim-notes (vimscript #3375)\r\n\u00c2\u00a0\u00e2\u0080\u00a2 vim-reload (vimscript #3148)\r\n\u00c2\u00a0\u00e2\u0080\u00a2 vim-session (vimscript #3150)\r\n\u00c2\u00a0\u00e2\u0080\u00a2 vim-shell (vimscript #3123)","4":"This plug-in contains Vim scripts that are used by most of the Vim plug-ins I've written yet don't really belong with any single one of the plug-ins. Basically it's an extended standard library of Vim script functions that I wrote during the development of my Vim profile and plug-ins.\r\n\r\nIn the past these scripts were bundled with each plug-in, however that turned out to be a maintenance nightmare for me. That's why the miscellaneous scripts are now a proper plug-in with their own page on Vim Online.\r\n\r\nFor more information about the miscellaneous scripts please refer to the homepage or the project page on GitHub:\r\n\r\n\u00c2\u00a0\u00e2\u0080\u00a2 http:\/\/peterodding.com\/code\/vim\/misc\/ \r\n\u00c2\u00a0\u00e2\u0080\u00a2 http:\/\/github.com\/xolox\/vim-misc\r\n\r\nIf you have questions, bug reports, suggestions, etc. the author can be contacted at peter@peterodding.com. If you like this plug-in please vote for it below!\r\n\r\nThe following plug-ins of mine depend on the installation of the miscellaneous scripts as a separate plug-in:\r\n\r\n\u00c2\u00a0\u00e2\u0080\u00a2 vim-colorscheme-switcher (vimscript #4586)\r\n\u00c2\u00a0\u00e2\u0080\u00a2 vim-easytags (vimscript #3114)\r\n\u00c2\u00a0\u00e2\u0080\u00a2 vim-lua-ftplugin (vimscript #3625)\r\n\u00c2\u00a0\u00e2\u0080\u00a2 vim-lua-inspect (vimscript #3169)\r\n\u00c2\u00a0\u00e2\u0080\u00a2 vim-notes (vimscript #3375)\r\n\u00c2\u00a0\u00e2\u0080\u00a2 vim-reload (vimscript #3148)\r\n\u00c2\u00a0\u00e2\u0080\u00a2 vim-session (vimscript #3150)\r\n\u00c2\u00a0\u00e2\u0080\u00a2 vim-shell (vimscript #3123)","install_details":"Unzip the most recent ZIP archive file (see below) inside your Vim profile directory (usually this is \"~\/.vim\" on UNIX and \"%USERPROFILE%\\vimfiles\" on Windows), restart Vim and execute the command \":helptags ~\/.vim\/doc\" (use \":helptags ~\\vimfiles\\doc\" instead on Windows).","5":"Unzip the most recent ZIP archive file (see below) inside your Vim profile directory (usually this is \"~\/.vim\" on UNIX and \"%USERPROFILE%\\vimfiles\" on Windows), restart Vim and execute the command \":helptags ~\/.vim\/doc\" (use \":helptags ~\\vimfiles\\doc\" instead on Windows).","first_name":"Peter","6":"Peter","last_name":"Odding","7":"Odding","releases":[{"0":"4597","vim_version":"7.0","1":"7.0","script_version":"1.17.6","2":"1.17.6","version_comment":" \u00e2\u0080\u00a2 Try to fix issue #17 (async command execution on Windows without DLL):\n   http:\/\/github.com\/xolox\/vim-misc\/commit\/3e6b8fb","3":" \u00e2\u0080\u00a2 Try to fix issue #17 (async command execution on Windows without DLL):\n   http:\/\/github.com\/xolox\/vim-misc\/commit\/3e6b8fb","package":"misc.zip","4":"misc.zip","src_id":"23300","5":"23300","creation_date":"1432234475","6":"1432234475"},{"0":"4597","vim_version":"7.0","1":"7.0","script_version":"1.17.5","2":"1.17.5","version_comment":" \u00e2\u0080\u00a2 Fix issue 18 (Installation link loops):\n   http:\/\/github.com\/xolox\/vim-misc\/commit\/8076e72","3":" \u00e2\u0080\u00a2 Fix issue 18 (Installation link loops):\n   http:\/\/github.com\/xolox\/vim-misc\/commit\/8076e72","package":"misc.zip","4":"misc.zip","src_id":"23233","5":"23233","creation_date":"1430240274","6":"1430240274"},{"0":"4597","vim_version":"7.0","1":"7.0","script_version":"1.17.4","2":"1.17.4","version_comment":" \u00e2\u0080\u00a2 Bug fix: Don't mistake 'D' for 'd' when &ignorecase is set:\n   http:\/\/github.com\/xolox\/vim-misc\/commit\/14ddee7","3":" \u00e2\u0080\u00a2 Bug fix: Don't mistake 'D' for 'd' when &ignorecase is set:\n   http:\/\/github.com\/xolox\/vim-misc\/commit\/14ddee7","package":"misc.zip","4":"misc.zip","src_id":"23119","5":"23119","creation_date":"1427924402","6":"1427924402"},{"0":"4597","vim_version":"7.0","1":"7.0","script_version":"1.17.3","2":"1.17.3","version_comment":" \u00e2\u0080\u00a2 Make xolox#misc#option#eval_tags() respect 'd' in &cpoptions:\n   http:\/\/github.com\/xolox\/vim-misc\/commit\/3e2619e","3":" \u00e2\u0080\u00a2 Make xolox#misc#option#eval_tags() respect 'd' in &cpoptions:\n   http:\/\/github.com\/xolox\/vim-misc\/commit\/3e2619e","package":"misc.zip","4":"misc.zip","src_id":"23118","5":"23118","creation_date":"1427923973","6":"1427923973"},{"0":"4597","vim_version":"7.0","1":"7.0","script_version":"1.17.2","2":"1.17.2","version_comment":" \u00e2\u0080\u00a2 Merge pull request 16: Change highlight group of xolox#misc#msg#info():\n   http:\/\/github.com\/xolox\/vim-misc\/commit\/9b38b8f","3":" \u00e2\u0080\u00a2 Merge pull request 16: Change highlight group of xolox#misc#msg#info():\n   http:\/\/github.com\/xolox\/vim-misc\/commit\/9b38b8f","package":"misc.zip","4":"misc.zip","src_id":"23033","5":"23033","creation_date":"1426414280","6":"1426414280"},{"0":"4597","vim_version":"7.0","1":"7.0","script_version":"1.17.1","2":"1.17.1","version_comment":" \u00e2\u0080\u00a2 Try to silence errors during startup caused by :redraw:\n   http:\/\/github.com\/xolox\/vim-misc\/commit\/038faed","3":" \u00e2\u0080\u00a2 Try to silence errors during startup caused by :redraw:\n   http:\/\/github.com\/xolox\/vim-misc\/commit\/038faed","package":"misc.zip","4":"misc.zip","src_id":"22614","5":"22614","creation_date":"1415917161","6":"1415917161"},{"0":"4597","vim_version":"7.0","1":"7.0","script_version":"1.17","2":"1.17","version_comment":" \u00e2\u0080\u00a2 Added open handler for cygwin:\n   http:\/\/github.com\/xolox\/vim-misc\/commit\/80ccd89\n\n \u00e2\u0080\u00a2 Merge pull request #15: Added open handler for cygwin:\n   http:\/\/github.com\/xolox\/vim-misc\/commit\/15fd181","3":" \u00e2\u0080\u00a2 Added open handler for cygwin:\n   http:\/\/github.com\/xolox\/vim-misc\/commit\/80ccd89\n\n \u00e2\u0080\u00a2 Merge pull request #15: Added open handler for cygwin:\n   http:\/\/github.com\/xolox\/vim-misc\/commit\/15fd181","package":"misc.zip","4":"misc.zip","src_id":"22576","5":"22576","creation_date":"1414458456","6":"1414458456"},{"0":"4597","vim_version":"7.0","1":"7.0","script_version":"1.16.1","2":"1.16.1","version_comment":" \u00e2\u0080\u00a2 Add generic string unescaping function:\n   http:\/\/github.com\/xolox\/vim-misc\/commit\/640bc14\n\n \u00e2\u0080\u00a2 Generates error when easytags is not installed:\n   http:\/\/github.com\/xolox\/vim-misc\/commit\/3ae8dc0\n\n \u00e2\u0080\u00a2 Merge pull request #14 (references to xolox#easytags in xolox#misc#async):\n   http:\/\/github.com\/xolox\/vim-misc\/commit\/77b23c8","3":" \u00e2\u0080\u00a2 Add generic string unescaping function:\n   http:\/\/github.com\/xolox\/vim-misc\/commit\/640bc14\n\n \u00e2\u0080\u00a2 Generates error when easytags is not installed:\n   http:\/\/github.com\/xolox\/vim-misc\/commit\/3ae8dc0\n\n \u00e2\u0080\u00a2 Merge pull request #14 (references to xolox#easytags in xolox#misc#async):\n   http:\/\/github.com\/xolox\/vim-misc\/commit\/77b23c8","package":"misc.zip","4":"misc.zip","src_id":"22436","5":"22436","creation_date":"1410986408","6":"1410986408"},{"0":"4597","vim_version":"7.0","1":"7.0","script_version":"1.15.1","2":"1.15.1","version_comment":" \u00e2\u0080\u00a2 `xolox#misc#os#is_mac` might be slow: call it only when required:\n   http:\/\/github.com\/xolox\/vim-misc\/commit\/03caf46","3":" \u00e2\u0080\u00a2 `xolox#misc#os#is_mac` might be slow: call it only when required:\n   http:\/\/github.com\/xolox\/vim-misc\/commit\/03caf46","package":"misc.zip","4":"misc.zip","src_id":"22420","5":"22420","creation_date":"1410684688","6":"1410684688"},{"0":"4597","vim_version":"7.0","1":"7.0","script_version":"1.15","2":"1.15","version_comment":" \u00e2\u0080\u00a2 Make xolox#misc#complete#keywords() respect &ignorecase:\n   http:\/\/github.com\/xolox\/vim-misc\/commit\/e5b41ce\n\n \u00e2\u0080\u00a2 Resumable timers for accurate timing of short running operations:\n   http:\/\/github.com\/xolox\/vim-misc\/commit\/6ce98ee","3":" \u00e2\u0080\u00a2 Make xolox#misc#complete#keywords() respect &ignorecase:\n   http:\/\/github.com\/xolox\/vim-misc\/commit\/e5b41ce\n\n \u00e2\u0080\u00a2 Resumable timers for accurate timing of short running operations:\n   http:\/\/github.com\/xolox\/vim-misc\/commit\/6ce98ee","package":"misc.zip","4":"misc.zip","src_id":"22215","5":"22215","creation_date":"1405768283","6":"1405768283"},{"0":"4597","vim_version":"7.0","1":"7.0","script_version":"1.14.1","2":"1.14.1","version_comment":" \u00e2\u0080\u00a2 Merge pull request #12: Correctly handle Windows paths without drive letter:\n   http:\/\/github.com\/xolox\/vim-misc\/commit\/f6acb27","3":" \u00e2\u0080\u00a2 Merge pull request #12: Correctly handle Windows paths without drive letter:\n   http:\/\/github.com\/xolox\/vim-misc\/commit\/f6acb27","package":"misc.zip","4":"misc.zip","src_id":"22158","5":"22158","creation_date":"1404752520","6":"1404752520"},{"0":"4597","vim_version":"7.0","1":"7.0","script_version":"1.14","2":"1.14","version_comment":" \u00e2\u0080\u00a2 Silence xolox#misc#async#periodic_callback() when request queue is empty:\n   http:\/\/github.com\/xolox\/vim-misc\/commit\/0a70769\n\n \u00e2\u0080\u00a2 Make it clear how long it takes for asynchronous callbacks to reply:\n   http:\/\/github.com\/xolox\/vim-misc\/commit\/92172c6\n\n \u00e2\u0080\u00a2 New xolox#misc#path#starts_with() function:\n   http:\/\/github.com\/xolox\/vim-misc\/commit\/e3f28a7","3":" \u00e2\u0080\u00a2 Silence xolox#misc#async#periodic_callback() when request queue is empty:\n   http:\/\/github.com\/xolox\/vim-misc\/commit\/0a70769\n\n \u00e2\u0080\u00a2 Make it clear how long it takes for asynchronous callbacks to reply:\n   http:\/\/github.com\/xolox\/vim-misc\/commit\/92172c6\n\n \u00e2\u0080\u00a2 New xolox#misc#path#starts_with() function:\n   http:\/\/github.com\/xolox\/vim-misc\/commit\/e3f28a7","package":"misc.zip","4":"misc.zip","src_id":"22137","5":"22137","creation_date":"1404664234","6":"1404664234"},{"0":"4597","vim_version":"7.0","1":"7.0","script_version":"1.13.1","2":"1.13.1","version_comment":" \u00e2\u0080\u00a2 Bug fix: Don't raise exception if \/usr\/bin\/stat doesn't work:\n   http:\/\/github.com\/xolox\/vim-misc\/commit\/9d1f006","3":" \u00e2\u0080\u00a2 Bug fix: Don't raise exception if \/usr\/bin\/stat doesn't work:\n   http:\/\/github.com\/xolox\/vim-misc\/commit\/9d1f006","package":"misc.zip","4":"misc.zip","src_id":"22111","5":"22111","creation_date":"1404081717","6":"1404081717"},{"0":"4597","vim_version":"7.0","1":"7.0","script_version":"1.13","2":"1.13","version_comment":" \u00e2\u0080\u00a2 Support for 'atomic' file updates (preserving owner, group and mode):\n   http:\/\/github.com\/xolox\/vim-misc\/commit\/8dde3d1","3":" \u00e2\u0080\u00a2 Support for 'atomic' file updates (preserving owner, group and mode):\n   http:\/\/github.com\/xolox\/vim-misc\/commit\/8dde3d1","package":"misc.zip","4":"misc.zip","src_id":"22110","5":"22110","creation_date":"1404080407","6":"1404080407"},{"0":"4597","vim_version":"7.0","1":"7.0","script_version":"1.12","2":"1.12","version_comment":" \u00e2\u0080\u00a2 Support for querying\/setting UNIX file permissions:\n   http:\/\/github.com\/xolox\/vim-misc\/commit\/fc75b64","3":" \u00e2\u0080\u00a2 Support for querying\/setting UNIX file permissions:\n   http:\/\/github.com\/xolox\/vim-misc\/commit\/fc75b64","package":"misc.zip","4":"misc.zip","src_id":"22109","5":"22109","creation_date":"1404077650","6":"1404077650"},{"0":"4597","vim_version":"7.0","1":"7.0","script_version":"1.11","2":"1.11","version_comment":" \u00e2\u0080\u00a2 Expose formatting of elapsed time as xolox#misc#timer#convert():\n   http:\/\/github.com\/xolox\/vim-misc\/commit\/e6b3037\n\n \u00e2\u0080\u00a2 Implement generalized rate limiting of CursorHold events:\n   http:\/\/github.com\/xolox\/vim-misc\/commit\/ec5942f\n\n \u00e2\u0080\u00a2 Functions to persist\/recall Vim values from\/to files:\n   http:\/\/github.com\/xolox\/vim-misc\/commit\/8176763\n\n \u00e2\u0080\u00a2 Generalized asynchronous Vim script evaluation (for vim-easytags):\n   http:\/\/github.com\/xolox\/vim-misc\/commit\/81fdec8","3":" \u00e2\u0080\u00a2 Expose formatting of elapsed time as xolox#misc#timer#convert():\n   http:\/\/github.com\/xolox\/vim-misc\/commit\/e6b3037\n\n \u00e2\u0080\u00a2 Implement generalized rate limiting of CursorHold events:\n   http:\/\/github.com\/xolox\/vim-misc\/commit\/ec5942f\n\n \u00e2\u0080\u00a2 Functions to persist\/recall Vim values from\/to files:\n   http:\/\/github.com\/xolox\/vim-misc\/commit\/8176763\n\n \u00e2\u0080\u00a2 Generalized asynchronous Vim script evaluation (for vim-easytags):\n   http:\/\/github.com\/xolox\/vim-misc\/commit\/81fdec8","package":"misc.zip","4":"misc.zip","src_id":"22075","5":"22075","creation_date":"1403398545","6":"1403398545"},{"0":"4597","vim_version":"7.0","1":"7.0","script_version":"1.8.5","2":"1.8.5","version_comment":" \u00e2\u0080\u00a2 Avoid the costly shelling out to uname when on Windows (contributed by Ingo Karkat):\n   http:\/\/github.com\/xolox\/vim-misc\/commit\/fe6a548\n   http:\/\/github.com\/xolox\/vim-misc\/commit\/8551f2b","3":" \u00e2\u0080\u00a2 Avoid the costly shelling out to uname when on Windows (contributed by Ingo Karkat):\n   http:\/\/github.com\/xolox\/vim-misc\/commit\/fe6a548\n   http:\/\/github.com\/xolox\/vim-misc\/commit\/8551f2b","package":"misc.zip","4":"misc.zip","src_id":"20548","5":"20548","creation_date":"1374309758","6":"1374309758"},{"0":"4597","vim_version":"7.0","1":"7.0","script_version":"1.8.4","2":"1.8.4","version_comment":" \u00e2\u0080\u00a2 Don't error out when vim-shell is not installed:\n   http:\/\/github.com\/xolox\/vim-misc\/commit\/6fe6e26","3":" \u00e2\u0080\u00a2 Don't error out when vim-shell is not installed:\n   http:\/\/github.com\/xolox\/vim-misc\/commit\/6fe6e26","package":"misc.zip","4":"misc.zip","src_id":"20441","5":"20441","creation_date":"1372236986","6":"1372236986"},{"0":"4597","vim_version":"7.0","1":"7.0","script_version":"1.8.3","2":"1.8.3","version_comment":" \u00e2\u0080\u00a2 Bug fix for xolox#misc#path#tempdir() (E739 was not being caught):\n   http:\/\/github.com\/xolox\/vim-misc\/commit\/473381c\n\n \u00e2\u0080\u00a2 Make external command execution work properly without vim-shell!\n   http:\/\/github.com\/xolox\/vim-misc\/commit\/d780f0a","3":" \u00e2\u0080\u00a2 Bug fix for xolox#misc#path#tempdir() (E739 was not being caught):\n   http:\/\/github.com\/xolox\/vim-misc\/commit\/473381c\n\n \u00e2\u0080\u00a2 Make external command execution work properly without vim-shell!\n   http:\/\/github.com\/xolox\/vim-misc\/commit\/d780f0a","package":"misc.zip","4":"misc.zip","src_id":"20436","5":"20436","creation_date":"1372198417","6":"1372198417"},{"0":"4597","vim_version":"7.0","1":"7.0","script_version":"1.8.1","2":"1.8.1","version_comment":" \u00e2\u0080\u00a2 xolox#misc#os#exec(): Improve error reporting about temporary files:\n   http:\/\/github.com\/xolox\/vim-misc\/commit\/3d246a6","3":" \u00e2\u0080\u00a2 xolox#misc#os#exec(): Improve error reporting about temporary files:\n   http:\/\/github.com\/xolox\/vim-misc\/commit\/3d246a6","package":"misc.zip","4":"misc.zip","src_id":"20421","5":"20421","creation_date":"1372111979","6":"1372111979"},{"0":"4597","vim_version":"7.0","1":"7.0","script_version":"1.8","2":"1.8","version_comment":" \u00e2\u0080\u00a2 Updates required by vim-notes 0.22:\n   http:\/\/github.com\/xolox\/vim-misc\/commit\/19803c1\n   http:\/\/github.com\/xolox\/vim-misc\/commit\/78a6ee0","3":" \u00e2\u0080\u00a2 Updates required by vim-notes 0.22:\n   http:\/\/github.com\/xolox\/vim-misc\/commit\/19803c1\n   http:\/\/github.com\/xolox\/vim-misc\/commit\/78a6ee0","package":"misc.zip","4":"misc.zip","src_id":"20411","5":"20411","creation_date":"1372022114","6":"1372022114"},{"0":"4597","vim_version":"7.0","1":"7.0","script_version":"1.7","2":"1.7","version_comment":" \u00e2\u0080\u00a2 Version string parsing and comparison functions:\n   http:\/\/github.com\/xolox\/vim-misc\/commit\/c0e7620","3":" \u00e2\u0080\u00a2 Version string parsing and comparison functions:\n   http:\/\/github.com\/xolox\/vim-misc\/commit\/c0e7620","package":"misc.zip","4":"misc.zip","src_id":"20389","5":"20389","creation_date":"1371859794","6":"1371859794"},{"0":"4597","vim_version":"7.0","1":"7.0","script_version":"1.6.3","2":"1.6.3","version_comment":" \u00e2\u0080\u00a2 Bug fix for xolox#misc#open#url() on Mac OS X (xolox\/vim-shell#18):\n   http:\/\/github.com\/xolox\/vim-misc\/commit\/732cc21","3":" \u00e2\u0080\u00a2 Bug fix for xolox#misc#open#url() on Mac OS X (xolox\/vim-shell#18):\n   http:\/\/github.com\/xolox\/vim-misc\/commit\/732cc21","package":"misc.zip","4":"misc.zip","src_id":"20375","5":"20375","creation_date":"1371675266","6":"1371675266"},{"0":"4597","vim_version":"7.0","1":"7.0","script_version":"1.6.2","2":"1.6.2","version_comment":" \u00e2\u0080\u00a2 open.vim: Bug fix for error handling code (the \"not implemented\" message):\n   http:\/\/github.com\/xolox\/vim-misc\/commit\/cf92d5a\n\n \u00e2\u0080\u00a2 xolox#misc#open#file(): Improve documentation & variable names:\n   http:\/\/github.com\/xolox\/vim-misc\/commit\/3d51983\n\n \u00e2\u0080\u00a2 xolox#misc#open#file(): Instrument with xolox#misc#msg#debug() calls:\n   http:\/\/github.com\/xolox\/vim-misc\/commit\/b9391f4\n\n \u00e2\u0080\u00a2 Properly detect Mac OS X using xolox#misc#os#is_mac():\n   http:\/\/github.com\/xolox\/vim-misc\/commit\/aea5599","3":" \u00e2\u0080\u00a2 open.vim: Bug fix for error handling code (the \"not implemented\" message):\n   http:\/\/github.com\/xolox\/vim-misc\/commit\/cf92d5a\n\n \u00e2\u0080\u00a2 xolox#misc#open#file(): Improve documentation & variable names:\n   http:\/\/github.com\/xolox\/vim-misc\/commit\/3d51983\n\n \u00e2\u0080\u00a2 xolox#misc#open#file(): Instrument with xolox#misc#msg#debug() calls:\n   http:\/\/github.com\/xolox\/vim-misc\/commit\/b9391f4\n\n \u00e2\u0080\u00a2 Properly detect Mac OS X using xolox#misc#os#is_mac():\n   http:\/\/github.com\/xolox\/vim-misc\/commit\/aea5599","package":"misc.zip","4":"misc.zip","src_id":"20374","5":"20374","creation_date":"1371668848","6":"1371668848"},{"0":"4597","vim_version":"7.0","1":"7.0","script_version":"1.6","2":"1.6","version_comment":" \u00e2\u0080\u00a2 Finally started writing automated tests:\n   http:\/\/github.com\/xolox\/vim-misc\/commit\/1aed880\n\n \u00e2\u0080\u00a2 Bug fix based on tests: Don't add duplicate directory separators in xolox#misc#option#eval_tags():\n   http:\/\/github.com\/xolox\/vim-misc\/commit\/8a2773d\n\n \u00e2\u0080\u00a2 Bug fix based on tests: Don't generate errors on empty paths in xolox#misc#path#join():\n   http:\/\/github.com\/xolox\/vim-misc\/commit\/7c7d70f\n\n \u00e2\u0080\u00a2 Move xolox#misc#timer#format_timespan() -> xolox#misc#format#timestamp():\n   http:\/\/github.com\/xolox\/vim-misc\/commit\/1e4f278\n\n \u00e2\u0080\u00a2 Reliable detection of xolox#misc#timer#start() return values:\n   http:\/\/github.com\/xolox\/vim-misc\/commit\/abac1c8\n\n \u00e2\u0080\u00a2 Add string coercion to xolox#misc#msg#info() & similar functions:\n   http:\/\/github.com\/xolox\/vim-misc\/commit\/2a8eaa7\n\n \u00e2\u0080\u00a2 Add xolox#misc#format#pluralize() function:\n   http:\/\/github.com\/xolox\/vim-misc\/commit\/d250b06\n\n \u00e2\u0080\u00a2 Extract testing framework from test suite:\n   http:\/\/github.com\/xolox\/vim-misc\/commit\/ac6fc93\n\n \u00e2\u0080\u00a2 Add xolox#misc#str#ucfirst() function:\n   http:\/\/github.com\/xolox\/vim-misc\/commit\/5082965\n\n \u00e2\u0080\u00a2 Improve xolox#misc#os#find_vim() function:\n   http:\/\/github.com\/xolox\/vim-misc\/commit\/37211f3","3":" \u00e2\u0080\u00a2 Finally started writing automated tests:\n   http:\/\/github.com\/xolox\/vim-misc\/commit\/1aed880\n\n \u00e2\u0080\u00a2 Bug fix based on tests: Don't add duplicate directory separators in xolox#misc#option#eval_tags():\n   http:\/\/github.com\/xolox\/vim-misc\/commit\/8a2773d\n\n \u00e2\u0080\u00a2 Bug fix based on tests: Don't generate errors on empty paths in xolox#misc#path#join():\n   http:\/\/github.com\/xolox\/vim-misc\/commit\/7c7d70f\n\n \u00e2\u0080\u00a2 Move xolox#misc#timer#format_timespan() -> xolox#misc#format#timestamp():\n   http:\/\/github.com\/xolox\/vim-misc\/commit\/1e4f278\n\n \u00e2\u0080\u00a2 Reliable detection of xolox#misc#timer#start() return values:\n   http:\/\/github.com\/xolox\/vim-misc\/commit\/abac1c8\n\n \u00e2\u0080\u00a2 Add string coercion to xolox#misc#msg#info() & similar functions:\n   http:\/\/github.com\/xolox\/vim-misc\/commit\/2a8eaa7\n\n \u00e2\u0080\u00a2 Add xolox#misc#format#pluralize() function:\n   http:\/\/github.com\/xolox\/vim-misc\/commit\/d250b06\n\n \u00e2\u0080\u00a2 Extract testing framework from test suite:\n   http:\/\/github.com\/xolox\/vim-misc\/commit\/ac6fc93\n\n \u00e2\u0080\u00a2 Add xolox#misc#str#ucfirst() function:\n   http:\/\/github.com\/xolox\/vim-misc\/commit\/5082965\n\n \u00e2\u0080\u00a2 Improve xolox#misc#os#find_vim() function:\n   http:\/\/github.com\/xolox\/vim-misc\/commit\/37211f3","package":"misc.zip","4":"misc.zip","src_id":"20274","5":"20274","creation_date":"1370289326","6":"1370289326"},{"0":"4597","vim_version":"7.0","1":"7.0","script_version":"1.1","2":"1.1","version_comment":" \u00e2\u0080\u00a2 Link to Vim Online & add installation instructions to README:\n   http:\/\/github.com\/xolox\/vim-misc\/commit\/578ee2e\n\n \u00e2\u0080\u00a2 Don't return duplicate matches in xolox#misc#path#which():\n   http:\/\/github.com\/xolox\/vim-misc\/commit\/b6d0aa5\n\n \u00e2\u0080\u00a2 Make xolox#misc#os#find_vim() configurable:\n   http:\/\/github.com\/xolox\/vim-misc\/commit\/f5b2eea","3":" \u00e2\u0080\u00a2 Link to Vim Online & add installation instructions to README:\n   http:\/\/github.com\/xolox\/vim-misc\/commit\/578ee2e\n\n \u00e2\u0080\u00a2 Don't return duplicate matches in xolox#misc#path#which():\n   http:\/\/github.com\/xolox\/vim-misc\/commit\/b6d0aa5\n\n \u00e2\u0080\u00a2 Make xolox#misc#os#find_vim() configurable:\n   http:\/\/github.com\/xolox\/vim-misc\/commit\/f5b2eea","package":"misc.zip","4":"misc.zip","src_id":"20258","5":"20258","creation_date":"1370096212","6":"1370096212"},{"0":"4597","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"misc.zip","4":"misc.zip","src_id":"20203","5":"20203","creation_date":"1369445228","6":"1369445228"}]},"4596":{"script_id":"4596","0":"4596","script_name":"verilog_auto_testbench","1":"verilog_auto_testbench","script_type":"utility","2":"utility","summary":"auto generate testbench and component instance current design unit","3":"auto generate testbench and component instance current design unit","description":"You can get latest version from https:\/\/github.com\/kdurant\/verilog-testbench\r\nFeature\r\nAuto generate testbench about current file\r\n\r\nAuto generate component instance about current file\r\n\r\nRapid input verilog port, reg and wire\r\n\r\nThis plugin don't check your syntax whether is corrected. You should invoke compiler to do it before use this plugin.","4":"You can get latest version from https:\/\/github.com\/kdurant\/verilog-testbench\r\nFeature\r\nAuto generate testbench about current file\r\n\r\nAuto generate component instance about current file\r\n\r\nRapid input verilog port, reg and wire\r\n\r\nThis plugin don't check your syntax whether is corrected. You should invoke compiler to do it before use this plugin.","install_details":"Installation\r\nThis plugin follows the standard runtime path structure, and as such it can be installed  plugin manager :\r\n    Pathogen\r\n    $ cd ~\/vimfiles\/bundle\r\n    $ git clone https:\/\/github.com\/kdurant\/verilog-testbench.git verilog-testbench\r\n     manual:\r\n    copy all of the files into your ~\/vimfiles\/directory\r\n","5":"Installation\r\nThis plugin follows the standard runtime path structure, and as such it can be installed  plugin manager :\r\n    Pathogen\r\n    $ cd ~\/vimfiles\/bundle\r\n    $ git clone https:\/\/github.com\/kdurant\/verilog-testbench.git verilog-testbench\r\n     manual:\r\n    copy all of the files into your ~\/vimfiles\/directory\r\n","first_name":"jun","6":"jun","last_name":"wang","7":"wang","releases":[{"0":"4596","vim_version":"7.0","1":"7.0","script_version":"2.4","2":"2.4","version_comment":"add insert function\r\nyou can rapid input verilog port, reg and wire","3":"add insert function\r\nyou can rapid input verilog port, reg and wire","package":"testbench-2.4.zip","4":"testbench-2.4.zip","src_id":"20759","5":"20759","creation_date":"1378445348","6":"1378445348"},{"0":"4596","vim_version":"7.0","1":"7.0","script_version":"2.3","2":"2.3","version_comment":"align port that instanced","3":"align port that instanced","package":"testbench.zip","4":"testbench.zip","src_id":"20742","5":"20742","creation_date":"1378091266","6":"1378091266"},{"0":"4596","vim_version":"7.0","1":"7.0","script_version":"2.2","2":"2.2","version_comment":"add instance function","3":"add instance function","package":"testbench.rar","4":"testbench.rar","src_id":"20724","5":"20724","creation_date":"1377701806","6":"1377701806"},{"0":"4596","vim_version":"7.0","1":"7.0","script_version":"2.1","2":"2.1","version_comment":"fix some bugs","3":"fix some bugs","package":"verilog_testbench.rar","4":"verilog_testbench.rar","src_id":"20695","5":"20695","creation_date":"1377082876","6":"1377082876"},{"0":"4596","vim_version":"7.0","1":"7.0","script_version":"2.0","2":"2.0","version_comment":"rewrite it","3":"rewrite it","package":"testbench.zip","4":"testbench.zip","src_id":"20694","5":"20694","creation_date":"1377063596","6":"1377063596"},{"0":"4596","vim_version":"7.3","1":"7.3","script_version":"1.1","2":"1.1","version_comment":"Fixed the missing port width problem","3":"Fixed the missing port width problem","package":"verilog_auto_testbench.vim","4":"verilog_auto_testbench.vim","src_id":"20199","5":"20199","creation_date":"1369317231","6":"1369317231"},{"0":"4596","vim_version":"7.3","1":"7.3","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"verilog_auto_testbench.vim","4":"verilog_auto_testbench.vim","src_id":"20198","5":"20198","creation_date":"1369303397","6":"1369303397"}]},"4595":{"script_id":"4595","0":"4595","script_name":"vim-bufferline","1":"vim-bufferline","script_type":"utility","2":"utility","summary":"super simple vim plugin to show the list of buffers in the command bar","3":"super simple vim plugin to show the list of buffers in the command bar","description":"Super simple vim plugin to show the list of buffers in the command bar.\r\n\r\nScreenshot here: https:\/\/raw.github.com\/bling\/vim-bufferline\/master\/bufferline.png\r\n\r\nLatest versions can be found at https:\/\/github.com\/bling\/vim-bufferline","4":"Super simple vim plugin to show the list of buffers in the command bar.\r\n\r\nScreenshot here: https:\/\/raw.github.com\/bling\/vim-bufferline\/master\/bufferline.png\r\n\r\nLatest versions can be found at https:\/\/github.com\/bling\/vim-bufferline","install_details":"Copy the script into your plugin folder, or you can install via Pathogen\/Vundle\/NeoBundle\/etc.","5":"Copy the script into your plugin folder, or you can install via Pathogen\/Vundle\/NeoBundle\/etc.","first_name":"Bailey","6":"Bailey","last_name":"Ling","7":"Ling","releases":[{"0":"4595","vim_version":"7.0","1":"7.0","script_version":"0.3","2":"0.3","version_comment":"fix potential infinite loop when viewing help files","3":"fix potential infinite loop when viewing help files","package":"bufferline.vim","4":"bufferline.vim","src_id":"20322","5":"20322","creation_date":"1370700251","6":"1370700251"},{"0":"4595","vim_version":"7.0","1":"7.0","script_version":"0.2","2":"0.2","version_comment":"* exposes public function bufferline#generate_string()\r\n* adds support for rotating buffers automatically with g:bufferline_rotate\r\n* adds support for disabling command bar echoing with g:bufferline_echo","3":"* exposes public function bufferline#generate_string()\r\n* adds support for rotating buffers automatically with g:bufferline_rotate\r\n* adds support for disabling command bar echoing with g:bufferline_echo","package":"bufferline.vim","4":"bufferline.vim","src_id":"20243","5":"20243","creation_date":"1370012599","6":"1370012599"},{"0":"4595","vim_version":"7.3","1":"7.3","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"bufferline.vim","4":"bufferline.vim","src_id":"20197","5":"20197","creation_date":"1369245750","6":"1369245750"}]},"4594":{"script_id":"4594","0":"4594","script_name":"header-info","1":"header-info","script_type":"utility","2":"utility","summary":"update your file header comments","3":"update your file header comments","description":"插件可以添加\/更新文件头注释\r\n\"vimmsf_header_info_range_marker(never modify me)\r\n\" ========================================================================\r\n\" file-name:     header_info.vim\r\n\" full-path:       \/home\/reaper-spring\/programs\/vim\/header-info\/plugin\/header_info.vim\r\n\" version:        1.0 \r\n\" author:          u are u\r\n\" email:           uremail@email.com\r\n\" homepage:    ur homepage\r\n\" last-modified: Wed 22 May 2013 09:06:16 PM CST\r\n\" description:    some desc.\r\n\" ======================================================================== \r\n\"vimmsf_header_info_range_marker(never modify me)\r\n\r\n插件会根据不同的文件类型选择不同的注释模板，所谓的模板是保存于插件目录templates中的文件，\r\n每个文件是一个模板，模板名随意，插件会根据目录中的filetype文件建立关联，每行建立一个关联，\r\n格式如下：\r\nfiletype -> tpn\r\n其中filetype对应vim的filetype选项，而tpn便是templates中模板文件名\r\n比如\r\nsh -> bash.txt\r\nvim读取shell脚本后filetype被设置成sh，当调用插件时便会使用bash.txt这个模板文件。\r\n默认如果在filetype中找不到文件类型对应的模板，则一律使用default.txt\r\n模板文件可以使用在marker文件中的自定义标记，每行一个。\r\n格式如下:\r\n$+mn+ -> action\r\n其中mn是标记名，action可以是文字常量（必须由单引号包裹），或者一段vim script代码。\r\n插件存在一个特殊标记，@+remained+@，如果它出现在模板文件行的末尾时，当插件更新文件头时会忽略本行。\r\n例如模板中有以下行\r\nfile-name: $+file+\r\n默认的当你编辑的文件名为file.txt时，插件会将其扩展为\r\nfile-name: file.txt\r\n无论你如何手动修改本行，例如file-name: test.txt, 下次调用插件更新时都会将还原为file-name: file.txt\r\n除非在模板中为此行加入特殊标记\r\nfile-name: $+file+ @+remained+@\r\n那么只有当第一次添加会扩展此行，以后的更新都会保留你手动修改的内容。\r\n另外无需在模板文件中添加注释符，插件会根据vim的commentstring选项自动选择。\r\n\r\n目前插件只支持单行字段注释，模板中有多少行就是多少行，不要手动进行增删，\r\nvimmsf_header_info_range_marker(never modify me)用于标记文件头范围，不要改动。\r\n\r\n使用方法: ctrl-k ctrl-h\r\n","4":"插件可以添加\/更新文件头注释\r\n\"vimmsf_header_info_range_marker(never modify me)\r\n\" ========================================================================\r\n\" file-name:     header_info.vim\r\n\" full-path:       \/home\/reaper-spring\/programs\/vim\/header-info\/plugin\/header_info.vim\r\n\" version:        1.0 \r\n\" author:          u are u\r\n\" email:           uremail@email.com\r\n\" homepage:    ur homepage\r\n\" last-modified: Wed 22 May 2013 09:06:16 PM CST\r\n\" description:    some desc.\r\n\" ======================================================================== \r\n\"vimmsf_header_info_range_marker(never modify me)\r\n\r\n插件会根据不同的文件类型选择不同的注释模板，所谓的模板是保存于插件目录templates中的文件，\r\n每个文件是一个模板，模板名随意，插件会根据目录中的filetype文件建立关联，每行建立一个关联，\r\n格式如下：\r\nfiletype -> tpn\r\n其中filetype对应vim的filetype选项，而tpn便是templates中模板文件名\r\n比如\r\nsh -> bash.txt\r\nvim读取shell脚本后filetype被设置成sh，当调用插件时便会使用bash.txt这个模板文件。\r\n默认如果在filetype中找不到文件类型对应的模板，则一律使用default.txt\r\n模板文件可以使用在marker文件中的自定义标记，每行一个。\r\n格式如下:\r\n$+mn+ -> action\r\n其中mn是标记名，action可以是文字常量（必须由单引号包裹），或者一段vim script代码。\r\n插件存在一个特殊标记，@+remained+@，如果它出现在模板文件行的末尾时，当插件更新文件头时会忽略本行。\r\n例如模板中有以下行\r\nfile-name: $+file+\r\n默认的当你编辑的文件名为file.txt时，插件会将其扩展为\r\nfile-name: file.txt\r\n无论你如何手动修改本行，例如file-name: test.txt, 下次调用插件更新时都会将还原为file-name: file.txt\r\n除非在模板中为此行加入特殊标记\r\nfile-name: $+file+ @+remained+@\r\n那么只有当第一次添加会扩展此行，以后的更新都会保留你手动修改的内容。\r\n另外无需在模板文件中添加注释符，插件会根据vim的commentstring选项自动选择。\r\n\r\n目前插件只支持单行字段注释，模板中有多少行就是多少行，不要手动进行增删，\r\nvimmsf_header_info_range_marker(never modify me)用于标记文件头范围，不要改动。\r\n\r\n使用方法: ctrl-k ctrl-h\r\n","install_details":"直接丢到.vim或vimfiles","5":"直接丢到.vim或vimfiles","first_name":"msf","6":"msf","last_name":"vim","7":"vim","releases":[{"0":"4594","vim_version":"7.0","1":"7.0","script_version":"1.1","2":"1.1","version_comment":"update formats of filetype and marker to more neat","3":"update formats of filetype and marker to more neat","package":"header-info.zip","4":"header-info.zip","src_id":"20234","5":"20234","creation_date":"1369923777","6":"1369923777"},{"0":"4594","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"header-info.zip","4":"header-info.zip","src_id":"20196","5":"20196","creation_date":"1369231205","6":"1369231205"}]},"4593":{"script_id":"4593","0":"4593","script_name":"fishruler","1":"fishruler","script_type":"utility","2":"utility","summary":"Fish text ruler","3":"Fish text ruler","description":"About\r\n-----\r\n\r\nFishruler allows you to visualize desired amount of the fish text.\r\nIt can be useful when you create a new database table, web-interface or\r\njust need some text for testing purposes.\r\n\r\n\r\nFish cheatsheet\r\n---------------\r\n\r\nFor list of most frequently used text sizes see `fishruler-cheatsheet.txt`.\r\nIt can be accessible through:\r\n\r\n    :h fishruler-cheatsheet.txt\r\n\r\nor\r\n\r\n    :FishCheatsheet\r\n\r\ncommands.\r\n\r\n\r\nInserting the fish text\r\n-----------------------\r\n\r\nFollowing command will insert 400 charcters of the lorem ipsum text:\r\n\r\n    :Fish 400\r\n\r\nYou can also insert full lorem ipsum text:\r\n\r\n    :Fish\r\n\r\n\r\nResources\r\n---------\r\n\r\nThe fish cheatsheet (`fishruler-cheatsheet.txt`) sizes are partially based\r\non the following resources:\r\n\r\n * http:\/\/stackoverflow.com\/questions\/20958\/list-of-standard-lengths-for-database-fields\r\n * http:\/\/webarchive.nationalarchives.gov.uk\/+\/http:\/\/www.cabinetoffice.gov.uk\/media\/254290\/GDS%20Catalogue%20Vol%202.pdf\r\n","4":"About\r\n-----\r\n\r\nFishruler allows you to visualize desired amount of the fish text.\r\nIt can be useful when you create a new database table, web-interface or\r\njust need some text for testing purposes.\r\n\r\n\r\nFish cheatsheet\r\n---------------\r\n\r\nFor list of most frequently used text sizes see `fishruler-cheatsheet.txt`.\r\nIt can be accessible through:\r\n\r\n    :h fishruler-cheatsheet.txt\r\n\r\nor\r\n\r\n    :FishCheatsheet\r\n\r\ncommands.\r\n\r\n\r\nInserting the fish text\r\n-----------------------\r\n\r\nFollowing command will insert 400 charcters of the lorem ipsum text:\r\n\r\n    :Fish 400\r\n\r\nYou can also insert full lorem ipsum text:\r\n\r\n    :Fish\r\n\r\n\r\nResources\r\n---------\r\n\r\nThe fish cheatsheet (`fishruler-cheatsheet.txt`) sizes are partially based\r\non the following resources:\r\n\r\n * http:\/\/stackoverflow.com\/questions\/20958\/list-of-standard-lengths-for-database-fields\r\n * http:\/\/webarchive.nationalarchives.gov.uk\/+\/http:\/\/www.cabinetoffice.gov.uk\/media\/254290\/GDS%20Catalogue%20Vol%202.pdf\r\n","install_details":"* Using pathogen (https:\/\/github.com\/tpope\/vim-pathogen) or vundle (https:\/\/github.com\/gmarik\/vundle) from https:\/\/github.com\/rdolgushin\/fishruler.vim \r\n* Standard Vim way (http:\/\/vimdoc.sourceforge.net\/htmldoc\/usr_05.html#add-plugin)","5":"* Using pathogen (https:\/\/github.com\/tpope\/vim-pathogen) or vundle (https:\/\/github.com\/gmarik\/vundle) from https:\/\/github.com\/rdolgushin\/fishruler.vim \r\n* Standard Vim way (http:\/\/vimdoc.sourceforge.net\/htmldoc\/usr_05.html#add-plugin)","first_name":"Roman","6":"Roman","last_name":"Dolgushin","7":"Dolgushin","releases":[{"0":"4593","vim_version":"7.0","1":"7.0","script_version":"1.1","2":"1.1","version_comment":"Initial upload","3":"Initial upload","package":"fishruler.zip","4":"fishruler.zip","src_id":"20194","5":"20194","creation_date":"1369190764","6":"1369190764"}]},"4592":{"script_id":"4592","0":"4592","script_name":"ctrlp-funky","1":"ctrlp-funky","script_type":"utility","2":"utility","summary":"A super simple function navigator for ctrlp.vim","3":"A super simple function navigator for ctrlp.vim","description":"ctrlp-funky\r\n============\r\nA super simple function navigator for ctrlp.vim.  \r\nFor lazy people who cannot wait until ctags finishes.\r\n\r\nSYNOPSIS\r\n----------\r\nThis is a ctrlp.vim extension. It simply navigates and jumps to function definitions from the current file without ctags. It just searches function definitions or equivalent lines using regular expressions, therefore some languages' abstraction aren't accurate because of hard to parse.\r\n\r\nOne of advantages of this plugin is that no configurations required in most of cases, so install, then it starts working and no ctags required.\r\n*If you want to have more accurate list of function defs, you should use other ctags based tools.*\r\n\r\nScreenshot: http:\/\/i.imgur.com\/yO4PWAF.png\r\n\r\n### Supported filetypes:\r\nSee help doc: https:\/\/github.com\/tacahiroy\/ctrlp-funky\/blob\/master\/doc\/ctrlp-funky.txt#L22\r\n\r\n\r\nPREMISE\r\n----------\r\nFirst of all, I believe you're a user of a great Vim plugin called [ctrlp.vim](https:\/\/github.com\/ctrlpvim\/ctrlp.vim).\r\nOtherwise, you need to install ctrlp.vim before start using this plugin.\r\n\r\n\r\nCONFIGURATION\r\n--------------\r\nIt should be useful to define key mappings like this:\r\n```vim\r\nnnoremap <Leader>fu :CtrlPFunky<Cr>\r\n\" narrow the list down with a word under cursor\r\nnnoremap <Leader>fU :execute 'CtrlPFunky ' . expand('<cword>')<Cr>\r\n```\r\n\r\n\r\nEXPERIMENTAL\r\n------------\r\n### MATCHED CHARS HIGHLIGHTING\r\nIf you want to have this highlight feature, you may configure like this:\r\n```vim\r\nlet g:ctrlp_funky_matchtype = 'path'\r\n```\r\nSee `:h g:ctrlp_funky_matchtype` for more details and notes.\r\n\r\n\r\n### SYNTAX HIGHLIGHTING\r\nI'd like to introduce one of ctrlp-funky options.\r\nDo you want to make ctrlp-funky funkier? Okay - you can do it with just 1 line config.\r\n```vim\r\nlet g:ctrlp_funky_syntax_highlight = 1\r\n```\r\nhttp:\/\/i.imgur.com\/CnKui5H.png\r\n\r\nNote that this feature doesn't work perfectly, because ctrlp-funky just sets\r\nfiletype to the funky buffer and the buffer contains '>' in the first column.\r\nIn some filetypes, this sign has special meaning such as HTML tag, so it breaks\r\nsyntax highlighting.\r\n\r\n\r\nLINK\r\n-------\r\n* [ctrlpvim\/ctrlp.vim](https:\/\/github.com\/ctrlpvim\/ctrlp.vim)\r\n* [vim.org\/ctrlp-funky](http:\/\/www.vim.org\/scripts\/script.php?script_id=4592)\r\n\r\n\r\nLICENSE\r\n-------\r\nCopyright (C) 2012-2019 Takahiro Yoshihara. Distributed under the MIT License.","4":"ctrlp-funky\r\n============\r\nA super simple function navigator for ctrlp.vim.  \r\nFor lazy people who cannot wait until ctags finishes.\r\n\r\nSYNOPSIS\r\n----------\r\nThis is a ctrlp.vim extension. It simply navigates and jumps to function definitions from the current file without ctags. It just searches function definitions or equivalent lines using regular expressions, therefore some languages' abstraction aren't accurate because of hard to parse.\r\n\r\nOne of advantages of this plugin is that no configurations required in most of cases, so install, then it starts working and no ctags required.\r\n*If you want to have more accurate list of function defs, you should use other ctags based tools.*\r\n\r\nScreenshot: http:\/\/i.imgur.com\/yO4PWAF.png\r\n\r\n### Supported filetypes:\r\nSee help doc: https:\/\/github.com\/tacahiroy\/ctrlp-funky\/blob\/master\/doc\/ctrlp-funky.txt#L22\r\n\r\n\r\nPREMISE\r\n----------\r\nFirst of all, I believe you're a user of a great Vim plugin called [ctrlp.vim](https:\/\/github.com\/ctrlpvim\/ctrlp.vim).\r\nOtherwise, you need to install ctrlp.vim before start using this plugin.\r\n\r\n\r\nCONFIGURATION\r\n--------------\r\nIt should be useful to define key mappings like this:\r\n```vim\r\nnnoremap <Leader>fu :CtrlPFunky<Cr>\r\n\" narrow the list down with a word under cursor\r\nnnoremap <Leader>fU :execute 'CtrlPFunky ' . expand('<cword>')<Cr>\r\n```\r\n\r\n\r\nEXPERIMENTAL\r\n------------\r\n### MATCHED CHARS HIGHLIGHTING\r\nIf you want to have this highlight feature, you may configure like this:\r\n```vim\r\nlet g:ctrlp_funky_matchtype = 'path'\r\n```\r\nSee `:h g:ctrlp_funky_matchtype` for more details and notes.\r\n\r\n\r\n### SYNTAX HIGHLIGHTING\r\nI'd like to introduce one of ctrlp-funky options.\r\nDo you want to make ctrlp-funky funkier? Okay - you can do it with just 1 line config.\r\n```vim\r\nlet g:ctrlp_funky_syntax_highlight = 1\r\n```\r\nhttp:\/\/i.imgur.com\/CnKui5H.png\r\n\r\nNote that this feature doesn't work perfectly, because ctrlp-funky just sets\r\nfiletype to the funky buffer and the buffer contains '>' in the first column.\r\nIn some filetypes, this sign has special meaning such as HTML tag, so it breaks\r\nsyntax highlighting.\r\n\r\n\r\nLINK\r\n-------\r\n* [ctrlpvim\/ctrlp.vim](https:\/\/github.com\/ctrlpvim\/ctrlp.vim)\r\n* [vim.org\/ctrlp-funky](http:\/\/www.vim.org\/scripts\/script.php?script_id=4592)\r\n\r\n\r\nLICENSE\r\n-------\r\nCopyright (C) 2012-2019 Takahiro Yoshihara. Distributed under the MIT License.","install_details":"### Vundle (https:\/\/github.com\/VundleVim\/Vundle.Vim)\r\n1. Run `:PluginInstall tacahiroy\/ctrlp-funky`\r\n2. Add `Plugin 'tacahiroy\/ctrlp-funky'` to _.vimrc_\r\n\r\n### vim-plug (https:\/\/github.com\/junegunn\/vim-plug)\r\n1. Add `Plug 'tacahiroy\/ctrlp-funky'` to _.vimrc_\r\n2. Run `:PlugInstall`\r\n\r\n### pathogen.vim (https:\/\/github.com\/tpope\/vim-pathogen)\r\n1. `cd ~\/.vim\/bundle`\r\n2. `git clone https:\/\/github.com\/tacahiroy\/ctrlp-funky.git`\r\n\r\n### Manually\r\nIf you don't use either plugin management systems, copy _autoload_ and _plugin_ directories to _.vim_ directory.\r\nOn Windows, basically, _vimfiles_ directory is used instead of _.vim_ directory.","5":"### Vundle (https:\/\/github.com\/VundleVim\/Vundle.Vim)\r\n1. Run `:PluginInstall tacahiroy\/ctrlp-funky`\r\n2. Add `Plugin 'tacahiroy\/ctrlp-funky'` to _.vimrc_\r\n\r\n### vim-plug (https:\/\/github.com\/junegunn\/vim-plug)\r\n1. Add `Plug 'tacahiroy\/ctrlp-funky'` to _.vimrc_\r\n2. Run `:PlugInstall`\r\n\r\n### pathogen.vim (https:\/\/github.com\/tpope\/vim-pathogen)\r\n1. `cd ~\/.vim\/bundle`\r\n2. `git clone https:\/\/github.com\/tacahiroy\/ctrlp-funky.git`\r\n\r\n### Manually\r\nIf you don't use either plugin management systems, copy _autoload_ and _plugin_ directories to _.vim_ directory.\r\nOn Windows, basically, _vimfiles_ directory is used instead of _.vim_ directory.","first_name":"Takahiro","6":"Takahiro","last_name":"Yoshihara","7":"Yoshihara","releases":[{"0":"4592","vim_version":"7.0","1":"7.0","script_version":"0.12.0","2":"0.12.0","version_comment":"+ Add support for rmarkdown (rmd) (#123)\r\n+ Add support for ColdFusion (cf) (#121)\r\n+ Add support for objc lightweight generic (#118)\r\n+ Add support for Vue.js (vue) (#117)\r\n+ Add support for GraphQL (#114)\r\n+ Add basic Groovy support\r\n+ Add super basic support for R\r\n+ Add support for ExUnit test for Elixir (#99)\r\n+ Add support for anonymous functions for Javascript (#98)\r\n+ Add private method and macro patterns for Elixir (#96)\r\n+ Add elm support (#90)\r\n+ Add haskell support (#91)\r\n+ Add plsql support (#86)\r\n+ Add proto (Protocol Buffers) support (#82)","3":"+ Add support for rmarkdown (rmd) (#123)\r\n+ Add support for ColdFusion (cf) (#121)\r\n+ Add support for objc lightweight generic (#118)\r\n+ Add support for Vue.js (vue) (#117)\r\n+ Add support for GraphQL (#114)\r\n+ Add basic Groovy support\r\n+ Add super basic support for R\r\n+ Add support for ExUnit test for Elixir (#99)\r\n+ Add support for anonymous functions for Javascript (#98)\r\n+ Add private method and macro patterns for Elixir (#96)\r\n+ Add elm support (#90)\r\n+ Add haskell support (#91)\r\n+ Add plsql support (#86)\r\n+ Add proto (Protocol Buffers) support (#82)","package":"ctrlp-funky-0.12.0.zip","4":"ctrlp-funky-0.12.0.zip","src_id":"26780","5":"26780","creation_date":"1570453670","6":"1570453670"},{"0":"4592","vim_version":"7.0","1":"7.0","script_version":"0.11.0","2":"0.11.0","version_comment":"+ Add basic C# (cs) support (#66)\r\n+ Add basic clojure support (#79)\r\n+ Add scss support (#69)\r\n+ Add very basic css support (#69)\r\n+ Add generator function support for javascript (#68)\r\n+ Add support for Perl Moose and Method::Signatures (#73) \r\n+ Add support for rspec definitions (#71)\r\n+ Add function name only (nudist) mode (#78)\r\n+ Fix invalid bufnr for cached buffers\r\n+ Remove custom highlight option","3":"+ Add basic C# (cs) support (#66)\r\n+ Add basic clojure support (#79)\r\n+ Add scss support (#69)\r\n+ Add very basic css support (#69)\r\n+ Add generator function support for javascript (#68)\r\n+ Add support for Perl Moose and Method::Signatures (#73) \r\n+ Add support for rspec definitions (#71)\r\n+ Add function name only (nudist) mode (#78)\r\n+ Fix invalid bufnr for cached buffers\r\n+ Remove custom highlight option","package":"ctrlp-funky-0.11.0.zip","4":"ctrlp-funky-0.11.0.zip","src_id":"23937","5":"23937","creation_date":"1453381104","6":"1453381104"},{"0":"4592","vim_version":"7.0","1":"7.0","script_version":"0.10.1","2":"0.10.1","version_comment":"+ Fix E688 problem with non English locales (#38)\r\n+ Add basic LaTeX support\r\n+ Add basic Dart support\r\n+ Improve TypeScript support (#64)\r\n+ Add MoonScript (moon) support (#62)\r\n+ Fix function name for typescript (#60)","3":"+ Fix E688 problem with non English locales (#38)\r\n+ Add basic LaTeX support\r\n+ Add basic Dart support\r\n+ Improve TypeScript support (#64)\r\n+ Add MoonScript (moon) support (#62)\r\n+ Fix function name for typescript (#60)","package":"ctrlp-funky-0.10.1.zip","4":"ctrlp-funky-0.10.1.zip","src_id":"23175","5":"23175","creation_date":"1429111703","6":"1429111703"},{"0":"4592","vim_version":"7.0","1":"7.0","script_version":"0.10.0","2":"0.10.0","version_comment":"+ Add multiple buffer support (minimum impl)\r\n\r\n+ Fix error on accept() if sort_by_mru is enabled (#59)\r\n+ Fix duplicate tag in the doc (#58)\r\n+ Fix doc entry for cache dir (#57)\r\n+ Add type declarations support for go (#53)\r\n+ Add clear cache functionality","3":"+ Add multiple buffer support (minimum impl)\r\n\r\n+ Fix error on accept() if sort_by_mru is enabled (#59)\r\n+ Fix duplicate tag in the doc (#58)\r\n+ Fix doc entry for cache dir (#57)\r\n+ Add type declarations support for go (#53)\r\n+ Add clear cache functionality","package":"ctrlp-funky-0.10.0.zip","4":"ctrlp-funky-0.10.0.zip","src_id":"22890","5":"22890","creation_date":"1423404307","6":"1423404307"},{"0":"4592","vim_version":"7.0","1":"7.0","script_version":"0.9.1","2":"0.9.1","version_comment":"* Add very basic Scala support\r\n* Add basic Elixir support\r\n* Add TRACE32 (cmm) and Makefile (make) support (#44)\r\n* Add basic TypeScript support (#52)\r\n* Improve Java support (#48)\r\n\r\n* Add clear cache functionality\r\n* Add 'g:ctrlp_funky_matchtype' (#13, #50)\r\n\r\n* Fix error when selecting a function in split window (#49)\r\n* Fix regexp for C++ to support scope resolution operator (#51)\r\n* Fix multi-lined function support for C and Java (#47)","3":"* Add very basic Scala support\r\n* Add basic Elixir support\r\n* Add TRACE32 (cmm) and Makefile (make) support (#44)\r\n* Add basic TypeScript support (#52)\r\n* Improve Java support (#48)\r\n\r\n* Add clear cache functionality\r\n* Add 'g:ctrlp_funky_matchtype' (#13, #50)\r\n\r\n* Fix error when selecting a function in split window (#49)\r\n* Fix regexp for C++ to support scope resolution operator (#51)\r\n* Fix multi-lined function support for C and Java (#47)","package":"ctrlp-funky-0.9.1.zip","4":"ctrlp-funky-0.9.1.zip","src_id":"22527","5":"22527","creation_date":"1413216174","6":"1413216174"},{"0":"4592","vim_version":"7.0","1":"7.0","script_version":"0.9.0","2":"0.9.0","version_comment":"* Add cache feature (#27).\r\n  ideas from dusans\r\n* php - Add support for extra keywords, final, static etc. (#35)\r\n  by axehead\r\n* Fix error a markdown file contains YAML Front matter (#36)\r\n  reported by dictav\r\n* markdown: Add h4 to h6 support","3":"* Add cache feature (#27).\r\n  ideas from dusans\r\n* php - Add support for extra keywords, final, static etc. (#35)\r\n  by axehead\r\n* Fix error a markdown file contains YAML Front matter (#36)\r\n  reported by dictav\r\n* markdown: Add h4 to h6 support","package":"ctrlp-funky-0.9.0.zip","4":"ctrlp-funky-0.9.0.zip","src_id":"22106","5":"22106","creation_date":"1404034703","6":"1404034703"},{"0":"4592","vim_version":"7.0","1":"7.0","script_version":"0.8.4","2":"0.8.4","version_comment":"* Add support for returning by reference function for PHP (#31)\r\n    by dingmingxin\r\n* Fix performance issue for python (#30)\r\n    by dusans\r\n* Add Jinja template support. (#29)\r\n    by vitalk","3":"* Add support for returning by reference function for PHP (#31)\r\n    by dingmingxin\r\n* Fix performance issue for python (#30)\r\n    by dusans\r\n* Add Jinja template support. (#29)\r\n    by vitalk","package":"ctrlp-funky-0.8.4.zip","4":"ctrlp-funky-0.8.4.zip","src_id":"21802","5":"21802","creation_date":"1398094534","6":"1398094534"},{"0":"4592","vim_version":"7.0","1":"7.0","script_version":"0.8.2","2":"0.8.2","version_comment":"* Add html\/xhtml support by Marc Mazer","3":"* Add html\/xhtml support by Marc Mazer","package":"ctrlp-funky-0.8.2.zip","4":"ctrlp-funky-0.8.2.zip","src_id":"21520","5":"21520","creation_date":"1393041109","6":"1393041109"},{"0":"4592","vim_version":"7.0","1":"7.0","script_version":"0.8.1","2":"0.8.1","version_comment":"* Add syntax highlighting feature for the funky buffer","3":"* Add syntax highlighting feature for the funky buffer","package":"ctrlp-funky-0.8.1.zip","4":"ctrlp-funky-0.8.1.zip","src_id":"21405","5":"21405","creation_date":"1391051437","6":"1391051437"},{"0":"4592","vim_version":"7.0","1":"7.0","script_version":"0.8.0","2":"0.8.0","version_comment":"+ 0.8.0: Add ability to custom highlight\r\n+ 0.7.1: Remove the old API\r\n+ 0.7.0: Add coffee-script support (#23) by kirstein\r\n+ Add post_extract_hook support\r\n+ Fix java: remove 'else if' from the list","3":"+ 0.8.0: Add ability to custom highlight\r\n+ 0.7.1: Remove the old API\r\n+ 0.7.0: Add coffee-script support (#23) by kirstein\r\n+ Add post_extract_hook support\r\n+ Fix java: remove 'else if' from the list","package":"ctrlp-funky-0.8.0.zip","4":"ctrlp-funky-0.8.0.zip","src_id":"21353","5":"21353","creation_date":"1390322876","6":"1390322876"},{"0":"4592","vim_version":"7.0","1":"7.0","script_version":"0.6.4","2":"0.6.4","version_comment":"* Improve javascript functions search\r\n* Improve java functions search","3":"* Improve javascript functions search\r\n* Improve java functions search","package":"ctrlp-funky-0.6.4.zip","4":"ctrlp-funky-0.6.4.zip","src_id":"20965","5":"20965","creation_date":"1382804202","6":"1382804202"},{"0":"4592","vim_version":"7.0","1":"7.0","script_version":"0.6.2","2":"0.6.2","version_comment":"* Improve internal interface\r\n* Add support for Perl\r\n* Add support for Go\r\n* Add anonymous function support for zsh\r\n* Improve regexp for C\/C++","3":"* Improve internal interface\r\n* Add support for Perl\r\n* Add support for Go\r\n* Add anonymous function support for zsh\r\n* Improve regexp for C\/C++","package":"ctrlp-funky-0.6.2.zip","4":"ctrlp-funky-0.6.2.zip","src_id":"20898","5":"20898","creation_date":"1381169765","6":"1381169765"},{"0":"4592","vim_version":"7.0","1":"7.0","script_version":"0.5.0","2":"0.5.0","version_comment":"+ Add MRU feature\r\n+ Add YAML support  by dusans (#20)\r\n+ Add javascript object function support by mephux (#17)\r\n+ Fix \"Pattern not found\" line appears in the list","3":"+ Add MRU feature\r\n+ Add YAML support  by dusans (#20)\r\n+ Add javascript object function support by mephux (#17)\r\n+ Fix \"Pattern not found\" line appears in the list","package":"ctrlp-funky-0.5.0.zip","4":"ctrlp-funky-0.5.0.zip","src_id":"20761","5":"20761","creation_date":"1378486661","6":"1378486661"},{"0":"4592","vim_version":"7.0","1":"7.0","script_version":"0.4.4","2":"0.4.4","version_comment":"* Add Lua support\r\n* Add new option: g:ctrlp_funky_sh_type to treat 'sh' as dash, bash, zsh etc.","3":"* Add Lua support\r\n* Add new option: g:ctrlp_funky_sh_type to treat 'sh' as dash, bash, zsh etc.","package":"ctrlp-funky-v0.4.4.zip","4":"ctrlp-funky-v0.4.4.zip","src_id":"20657","5":"20657","creation_date":"1376563403","6":"1376563403"},{"0":"4592","vim_version":"7.0","1":"7.0","script_version":"0.4.2","2":"0.4.2","version_comment":"- Add C support\r\n- Improve C++ pattern","3":"- Add C support\r\n- Improve C++ pattern","package":"ctrlp-funky-0.4.2.zip","4":"ctrlp-funky-0.4.2.zip","src_id":"20368","5":"20368","creation_date":"1371568232","6":"1371568232"},{"0":"4592","vim_version":"7.0","1":"7.0","script_version":"0.4.1","2":"0.4.1","version_comment":"Fix regex pattern for sh. No parentheses case can be detected.","3":"Fix regex pattern for sh. No parentheses case can be detected.","package":"ctrlp-funky-0.4.1.zip","4":"ctrlp-funky-0.4.1.zip","src_id":"20202","5":"20202","creation_date":"1369394172","6":"1369394172"},{"0":"4592","vim_version":"7.0","1":"7.0","script_version":"0.4.0","2":"0.4.0","version_comment":"Initial upload","3":"Initial upload","package":"ctrlp-funky-703b7f.zip","4":"ctrlp-funky-703b7f.zip","src_id":"20189","5":"20189","creation_date":"1369120406","6":"1369120406"}]},"4591":{"script_id":"4591","0":"4591","script_name":"winresizer.vim","1":"winresizer.vim","script_type":"utility","2":"utility","summary":"very simple vim plugin for easy resizing of your vim windows","3":"very simple vim plugin for easy resizing of your vim windows","description":"winresizer.vim\r\n================\r\n\r\nVery simple vim plugin for easy resizing of your vim windows.\r\n\r\nYou can resize windows continuously by using typical keymaps of Vim. (`h`, `j`, `k`, `l`)  \r\nThe WindowResize mode makes your operation more quickly and more naturally.\r\n\r\n## Demo\r\n\r\n### For terminal vim\r\n\r\ndemo\r\n\r\nhttps:\/\/raw.github.com\/wiki\/simeji\/winresizer\/images\/demo-for-terminal.gif\r\n\r\n### For MacVim(gui vim)\r\n\r\n* MacVim Window resize \r\n* Vim window resize\r\n\r\ndemo\r\n\r\nhttps:\/\/raw.github.com\/wiki\/simeji\/winresizer\/images\/demo-for-gui.gif\r\n\r\n## In default setting\r\n\r\n1. You press keys `Ctrl + E` or execute `:WinResizerStartResize` on vim(in normal mode), to run this plugin\r\n\r\n2. Start 'window resize mode', and you can resize current vim windows using 'h', 'j', 'k', 'l' keys\r\n\r\n3. You want to finish resize mode, then press \"Enter\" key\r\n\r\n4. If you cancel window resize, then press \"q\" key.\r\n   You will get window size of before change\r\n\r\n## Customize options\r\n\r\nYou can change setting and key mappings by using below options.(in your vimrc)\r\n\r\n|variable name|default value|description|\r\n|:-----------|:---------:|:----------|\r\ng:winresizer_enable\r\n   default: 1\r\n   desc:    Use winresizer (If this value is 0, this plugin will not work)\r\n\r\ng:winresizer_gui_enable\r\n   default: 0\r\n   desc:    Use winresizer in GUI Vim (If this value is 0, this plugin will not work in GUI Vim such as Mac Vim)\r\n\r\ng:winresizer_finish_with_escape\r\n   default: 1\r\n   desc:    If this value is 1, window resize mode is finished(fixed) by `Esc`\r\n\r\ng:winresizer_vert_resize\r\n   default: 10\r\n   desc:    The change width of window size when `left` or `right` key is pressed\r\n\r\ng:winresizer_horiz_resize\r\n   default: 3\r\n   desc:    The change height of window size when `down` or `up` key is pressed\r\n\r\ng:winresizer_start_key\r\n   default: `Ctrl + e`\r\n   desc:    Start window resize mode\r\n\r\ng:winresizer_gui_start_key\r\n   default: `Ctrl + a`\r\n   desc:    Start window resize mode (in GUI Vim)\r\n\r\ng:winresizer_keycode_left\r\n   default: 104(`h`)\r\n   desc:    Expand window size to left\r\n\r\ng:winresizer_keycode_right\r\n   default: 108(`l`)\r\n   desc:    Expand window size to right\r\n\r\ng:winresizer_keycode_down\r\n   default: 106(`j`)\r\n   desc:    Expand window size to down\r\n\r\ng:winresizer_keycode_up\r\n   default: 107(`k`)\r\n   desc:    Expand window size to up\r\n\r\ng:winresizer_keycode_finish\r\n   default: 13(`Enter`)\r\n   desc:    Fix and escape from window resize mode\r\n\r\ng:winresizer_keycode_cancel\r\n   default: 113(`q`)\r\n   desc:    Cancel and quit window resize mode\r\n\r\n\r\nIf you want to resize MacVim window itself, you must set below.\r\n\r\n```your_vimrc\r\nlet g:winresizer_gui_enable = 1\r\n```\r\n\r\n#### _Example in your .vimrc_\r\n\r\nIf you use winresizer with default settings. Don't have to do any settings.\r\n\r\n    \" If you want to start window resize mode by `Ctrl+T`\r\n    let g:winresizer_start_key = '<C-T>'\r\n    \r\n    \" If you cancel and quit window resize mode by `z` (keycode 122)\r\n    let g:winresizer_keycode_cancel = 122\r\n\r\n=-=-= [ Cheat sheet ]-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= \r\n\r\nkeymap of [window resize mode] (default setting)\r\n\r\nh : expand window size to left\r\nj : expand window size to down\r\nk : expand window size to up\r\nl : expand window size to right\r\nq : cancel resize window and escepe [window resize mode]\r\nEnter : fix and escape\r\n\r\n-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=\r\n\r\n## Latest version (development version) and issues\r\n\r\nhttps:\/\/github.com\/simeji\/winresizer\r\n\r\n## License\r\nwinresizer is released under the MIT license.\r\n","4":"winresizer.vim\r\n================\r\n\r\nVery simple vim plugin for easy resizing of your vim windows.\r\n\r\nYou can resize windows continuously by using typical keymaps of Vim. (`h`, `j`, `k`, `l`)  \r\nThe WindowResize mode makes your operation more quickly and more naturally.\r\n\r\n## Demo\r\n\r\n### For terminal vim\r\n\r\ndemo\r\n\r\nhttps:\/\/raw.github.com\/wiki\/simeji\/winresizer\/images\/demo-for-terminal.gif\r\n\r\n### For MacVim(gui vim)\r\n\r\n* MacVim Window resize \r\n* Vim window resize\r\n\r\ndemo\r\n\r\nhttps:\/\/raw.github.com\/wiki\/simeji\/winresizer\/images\/demo-for-gui.gif\r\n\r\n## In default setting\r\n\r\n1. You press keys `Ctrl + E` or execute `:WinResizerStartResize` on vim(in normal mode), to run this plugin\r\n\r\n2. Start 'window resize mode', and you can resize current vim windows using 'h', 'j', 'k', 'l' keys\r\n\r\n3. You want to finish resize mode, then press \"Enter\" key\r\n\r\n4. If you cancel window resize, then press \"q\" key.\r\n   You will get window size of before change\r\n\r\n## Customize options\r\n\r\nYou can change setting and key mappings by using below options.(in your vimrc)\r\n\r\n|variable name|default value|description|\r\n|:-----------|:---------:|:----------|\r\ng:winresizer_enable\r\n   default: 1\r\n   desc:    Use winresizer (If this value is 0, this plugin will not work)\r\n\r\ng:winresizer_gui_enable\r\n   default: 0\r\n   desc:    Use winresizer in GUI Vim (If this value is 0, this plugin will not work in GUI Vim such as Mac Vim)\r\n\r\ng:winresizer_finish_with_escape\r\n   default: 1\r\n   desc:    If this value is 1, window resize mode is finished(fixed) by `Esc`\r\n\r\ng:winresizer_vert_resize\r\n   default: 10\r\n   desc:    The change width of window size when `left` or `right` key is pressed\r\n\r\ng:winresizer_horiz_resize\r\n   default: 3\r\n   desc:    The change height of window size when `down` or `up` key is pressed\r\n\r\ng:winresizer_start_key\r\n   default: `Ctrl + e`\r\n   desc:    Start window resize mode\r\n\r\ng:winresizer_gui_start_key\r\n   default: `Ctrl + a`\r\n   desc:    Start window resize mode (in GUI Vim)\r\n\r\ng:winresizer_keycode_left\r\n   default: 104(`h`)\r\n   desc:    Expand window size to left\r\n\r\ng:winresizer_keycode_right\r\n   default: 108(`l`)\r\n   desc:    Expand window size to right\r\n\r\ng:winresizer_keycode_down\r\n   default: 106(`j`)\r\n   desc:    Expand window size to down\r\n\r\ng:winresizer_keycode_up\r\n   default: 107(`k`)\r\n   desc:    Expand window size to up\r\n\r\ng:winresizer_keycode_finish\r\n   default: 13(`Enter`)\r\n   desc:    Fix and escape from window resize mode\r\n\r\ng:winresizer_keycode_cancel\r\n   default: 113(`q`)\r\n   desc:    Cancel and quit window resize mode\r\n\r\n\r\nIf you want to resize MacVim window itself, you must set below.\r\n\r\n```your_vimrc\r\nlet g:winresizer_gui_enable = 1\r\n```\r\n\r\n#### _Example in your .vimrc_\r\n\r\nIf you use winresizer with default settings. Don't have to do any settings.\r\n\r\n    \" If you want to start window resize mode by `Ctrl+T`\r\n    let g:winresizer_start_key = '<C-T>'\r\n    \r\n    \" If you cancel and quit window resize mode by `z` (keycode 122)\r\n    let g:winresizer_keycode_cancel = 122\r\n\r\n=-=-= [ Cheat sheet ]-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= \r\n\r\nkeymap of [window resize mode] (default setting)\r\n\r\nh : expand window size to left\r\nj : expand window size to down\r\nk : expand window size to up\r\nl : expand window size to right\r\nq : cancel resize window and escepe [window resize mode]\r\nEnter : fix and escape\r\n\r\n-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=\r\n\r\n## Latest version (development version) and issues\r\n\r\nhttps:\/\/github.com\/simeji\/winresizer\r\n\r\n## License\r\nwinresizer is released under the MIT license.\r\n","install_details":"Just copy this script files autoload\/winresizer.vim and plugin\/winresizer.vim within Vim's path.\r\n\r\nIf you are using Vundle or NeoBundle, just add the following line to your .vimrc:\r\n\r\n(with Vundle)\r\n\"\"---------------------------------------\r\nBundle 'simeji\/winresizer.git'\r\n'\"\"---------------------------------------\r\n\r\n(with NeoBundle)\r\n\"\"---------------------------------------\r\nNeoBundle 'simeji\/winresizer.git'\r\n\"\"---------------------------------------","5":"Just copy this script files autoload\/winresizer.vim and plugin\/winresizer.vim within Vim's path.\r\n\r\nIf you are using Vundle or NeoBundle, just add the following line to your .vimrc:\r\n\r\n(with Vundle)\r\n\"\"---------------------------------------\r\nBundle 'simeji\/winresizer.git'\r\n'\"\"---------------------------------------\r\n\r\n(with NeoBundle)\r\n\"\"---------------------------------------\r\nNeoBundle 'simeji\/winresizer.git'\r\n\"\"---------------------------------------","first_name":"simeji","6":"simeji","last_name":"n","7":"n","releases":[{"0":"4591","vim_version":"7.0","1":"7.0","script_version":"1.1","2":"1.1","version_comment":"add function resize for MacVim and other GUI Vim","3":"add function resize for MacVim and other GUI Vim","package":"winresizer.tar.gz","4":"winresizer.tar.gz","src_id":"24051","5":"24051","creation_date":"1456585024","6":"1456585024"},{"0":"4591","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Add g:winresizer_finish_with_escape option, and edited README.\r\n\r\nIf don't want to use this function, add below setting in your .vimrc, please.\r\n\r\nlet g:winresizer_finish_with_escape = 0","3":"Add g:winresizer_finish_with_escape option, and edited README.\r\n\r\nIf don't want to use this function, add below setting in your .vimrc, please.\r\n\r\nlet g:winresizer_finish_with_escape = 0","package":"winresizer.tar.gz","4":"winresizer.tar.gz","src_id":"20487","5":"20487","creation_date":"1373055422","6":"1373055422"},{"0":"4591","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"winresizer.tar.gz","4":"winresizer.tar.gz","src_id":"20187","5":"20187","creation_date":"1369069232","6":"1369069232"}]},"4590":{"script_id":"4590","0":"4590","script_name":"localcomplete","1":"localcomplete","script_type":"utility","2":"utility","summary":"Search the current buffer for completions","3":"Search the current buffer for completions","description":"A completion function that searches the current buffer.  It allows to configure the order of matches and much more.\r\n\r\nFor more see github and the accompanying blog post:\r\nhttp:\/\/vertuxeltes.blogspot.de\/2013\/05\/powerful-insert-mode-completion.html\r\nhttps:\/\/github.com\/dirkwallenstein\/vim-localcomplete","4":"A completion function that searches the current buffer.  It allows to configure the order of matches and much more.\r\n\r\nFor more see github and the accompanying blog post:\r\nhttp:\/\/vertuxeltes.blogspot.de\/2013\/05\/powerful-insert-mode-completion.html\r\nhttps:\/\/github.com\/dirkwallenstein\/vim-localcomplete","install_details":"Please use Vundle or pathogen","5":"Please use Vundle or pathogen","first_name":"Dirk","6":"Dirk","last_name":"Wallenstein","7":"Wallenstein","releases":[{"0":"4590","vim_version":"7.0","1":"7.0","script_version":"1.0.1","2":"1.0.1","version_comment":"- the origin note is configurable\r\n- more case configuration","3":"- the origin note is configurable\r\n- more case configuration","package":"localcomplete-1.0.1.tar.gz","4":"localcomplete-1.0.1.tar.gz","src_id":"20494","5":"20494","creation_date":"1373133002","6":"1373133002"},{"0":"4590","vim_version":"7.0","1":"7.0","script_version":"1.0.0","2":"1.0.0","version_comment":"Initial upload","3":"Initial upload","package":"localcomplete-1.0.0.tar.gz","4":"localcomplete-1.0.0.tar.gz","src_id":"20186","5":"20186","creation_date":"1369064088","6":"1369064088"}]},"4589":{"script_id":"4589","0":"4589","script_name":"newt.vim","1":"newt.vim","script_type":"syntax","2":"syntax","summary":"NewtonScript syntax highlighting","3":"NewtonScript syntax highlighting","description":"VIM syntax highlighting for the NewtonScript (http:\/\/en.wikipedia.org\/wiki\/NewtonScript) language.","4":"VIM syntax highlighting for the NewtonScript (http:\/\/en.wikipedia.org\/wiki\/NewtonScript) language.","install_details":"","5":"","first_name":"Lay\u00c3\u00a1na","6":"Lay\u00c3\u00a1na","last_name":"\u01e8aynolj Kon\u00c3\u00b3vo","7":"Ǩaynolj Kon\u00c3\u00b3vo","releases":[{"0":"4589","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"newt.vim","4":"newt.vim","src_id":"20161","5":"20161","creation_date":"1368984268","6":"1368984268"}]},"4588":{"script_id":"4588","0":"4588","script_name":"vim-online-thesaurus","1":"vim-online-thesaurus","script_type":"utility","2":"utility","summary":"A Vim plugin for looking up words in an online thesaurus","3":"A Vim plugin for looking up words in an online thesaurus","description":"# Vim Online Thesaurus\r\n\r\nThis is a plugin for Vim allowing you to look up words in an online thesaurus,\r\nwhich is at the moment configured to be http:\/\/thesaurus.com\/\r\n\r\nThe plugin displays the definition of the word under the cursor and a list of\r\nsynonyms.\r\n\r\nScreenshot: https:\/\/raw.github.com\/beloglazov\/vim-online-thesaurus\/master\/screenshot.png\r\nHomepage: https:\/\/github.com\/beloglazov\/vim-online-thesaurus\r\n\r\nThe credit for the original idea and code goes to Nick Coleman:\r\nhttp:\/\/www.nickcoleman.org\/\r\n\r\n\r\n## Usage\r\n\r\nThe plugin provides the `:OnlineThesaurusCurrentWord` command to look up the     \r\ncurrent word under the cursor in an online thesaurus. Alternatively, you can     \r\nlook up any word with `:Thesaurus word`.                                         \r\n                                                                                 \r\nInternally, both commands make a request to http:\/\/thesaurus.com\/, parse the     \r\nresults, and display them in a vertical split in the bottom.                     \r\n                                                                                 \r\nBy default the `:OnlineThesaurusCurrentWord` command is mapped to                \r\n`<LocalLeader>K`.  If you haven't remapped `<LocalLeader>`, it defaults to `\\`.  \r\nTo close the split, just press `q`.\r\n\r\n\r\n## Configuration\r\n\r\nIf you want to disable the default key binding, add the following line to your\r\n.vimrc:\r\n\r\nlet g:online_thesaurus_map_keys = 0\r\n\r\nThen you can map the `:OnlineThesaurusCurrentWord` command to anything you want  \r\nas follows:                                                                      \r\n                                                                                 \r\nnnoremap <your key binding> :OnlineThesaurusCurrentWord<CR>\r\n\r\nEnjoy!\r\n\r\n\r\n## License\r\n\r\nCopyright (c) Anton Beloglazov. Distributed under the same terms as Vim itself.\r\nSee :help license.","4":"# Vim Online Thesaurus\r\n\r\nThis is a plugin for Vim allowing you to look up words in an online thesaurus,\r\nwhich is at the moment configured to be http:\/\/thesaurus.com\/\r\n\r\nThe plugin displays the definition of the word under the cursor and a list of\r\nsynonyms.\r\n\r\nScreenshot: https:\/\/raw.github.com\/beloglazov\/vim-online-thesaurus\/master\/screenshot.png\r\nHomepage: https:\/\/github.com\/beloglazov\/vim-online-thesaurus\r\n\r\nThe credit for the original idea and code goes to Nick Coleman:\r\nhttp:\/\/www.nickcoleman.org\/\r\n\r\n\r\n## Usage\r\n\r\nThe plugin provides the `:OnlineThesaurusCurrentWord` command to look up the     \r\ncurrent word under the cursor in an online thesaurus. Alternatively, you can     \r\nlook up any word with `:Thesaurus word`.                                         \r\n                                                                                 \r\nInternally, both commands make a request to http:\/\/thesaurus.com\/, parse the     \r\nresults, and display them in a vertical split in the bottom.                     \r\n                                                                                 \r\nBy default the `:OnlineThesaurusCurrentWord` command is mapped to                \r\n`<LocalLeader>K`.  If you haven't remapped `<LocalLeader>`, it defaults to `\\`.  \r\nTo close the split, just press `q`.\r\n\r\n\r\n## Configuration\r\n\r\nIf you want to disable the default key binding, add the following line to your\r\n.vimrc:\r\n\r\nlet g:online_thesaurus_map_keys = 0\r\n\r\nThen you can map the `:OnlineThesaurusCurrentWord` command to anything you want  \r\nas follows:                                                                      \r\n                                                                                 \r\nnnoremap <your key binding> :OnlineThesaurusCurrentWord<CR>\r\n\r\nEnjoy!\r\n\r\n\r\n## License\r\n\r\nCopyright (c) Anton Beloglazov. Distributed under the same terms as Vim itself.\r\nSee :help license.","install_details":"Unpack the tarball to your plugin directory. If you are using Vundle, just add the following line to your .vimrc:\r\n\r\nBundle 'beloglazov\/vim-online-thesaurus'\r\n\r\nThen run `:BundleInstall` to install the plugin.","5":"Unpack the tarball to your plugin directory. If you are using Vundle, just add the following line to your .vimrc:\r\n\r\nBundle 'beloglazov\/vim-online-thesaurus'\r\n\r\nThen run `:BundleInstall` to install the plugin.","first_name":"Anton","6":"Anton","last_name":"Beloglazov","7":"Beloglazov","releases":[{"0":"4588","vim_version":"7.0","1":"7.0","script_version":"0.3.2","2":"0.3.2","version_comment":"Moved the term into the window title (#32), fixed #34","3":"Moved the term into the window title (#32), fixed #34","package":"vim-online-thesaurus.tar.gz","4":"vim-online-thesaurus.tar.gz","src_id":"24030","5":"24030","creation_date":"1456038372","6":"1456038372"},{"0":"4588","vim_version":"7.0","1":"7.0","script_version":"0.3.1","2":"0.3.1","version_comment":"Added a mapping to look up expressions selected in visual mode: https:\/\/github.com\/beloglazov\/vim-online-thesaurus\/issues\/30","3":"Added a mapping to look up expressions selected in visual mode: https:\/\/github.com\/beloglazov\/vim-online-thesaurus\/issues\/30","package":"vim-online-thesaurus.tar.gz","4":"vim-online-thesaurus.tar.gz","src_id":"23449","5":"23449","creation_date":"1436240146","6":"1436240146"},{"0":"4588","vim_version":"7.0","1":"7.0","script_version":"0.3.0","2":"0.3.0","version_comment":"Added Windows support: https:\/\/github.com\/beloglazov\/vim-online-thesaurus\/pull\/28","3":"Added Windows support: https:\/\/github.com\/beloglazov\/vim-online-thesaurus\/pull\/28","package":"vim-online-thesaurus.tar.gz","4":"vim-online-thesaurus.tar.gz","src_id":"23385","5":"23385","creation_date":"1434304548","6":"1434304548"},{"0":"4588","vim_version":"7.0","1":"7.0","script_version":"0.2.3","2":"0.2.3","version_comment":"Fixed issue #25: https:\/\/github.com\/beloglazov\/vim-online-thesaurus\/issues\/25","3":"Fixed issue #25: https:\/\/github.com\/beloglazov\/vim-online-thesaurus\/issues\/25","package":"vim-online-thesaurus.tar.gz","4":"vim-online-thesaurus.tar.gz","src_id":"23230","5":"23230","creation_date":"1430113412","6":"1430113412"},{"0":"4588","vim_version":"7.0","1":"7.0","script_version":"0.2.2","2":"0.2.2","version_comment":"Improved cross-platform compatibility","3":"Improved cross-platform compatibility","package":"vim-online-thesaurus.tar.gz","4":"vim-online-thesaurus.tar.gz","src_id":"23198","5":"23198","creation_date":"1429498703","6":"1429498703"},{"0":"4588","vim_version":"7.0","1":"7.0","script_version":"0.2.1","2":"0.2.1","version_comment":"More robust word\/expression search","3":"More robust word\/expression search","package":"vim-online-thesaurus.tar.gz","4":"vim-online-thesaurus.tar.gz","src_id":"22979","5":"22979","creation_date":"1425511005","6":"1425511005"},{"0":"4588","vim_version":"7.0","1":"7.0","script_version":"0.2.0","2":"0.2.0","version_comment":"Added support for multiple word definitions, reuse the thesaurus window -- thanks to Shahaf Arad (av3r4ge).","3":"Added support for multiple word definitions, reuse the thesaurus window -- thanks to Shahaf Arad (av3r4ge).","package":"vim-online-thesaurus.tar.gz","4":"vim-online-thesaurus.tar.gz","src_id":"22977","5":"22977","creation_date":"1425440572","6":"1425440572"},{"0":"4588","vim_version":"7.0","1":"7.0","script_version":"0.1.9","2":"0.1.9","version_comment":"Fixed Windows compatibility: https:\/\/github.com\/beloglazov\/vim-online-thesaurus\/issues\/14","3":"Fixed Windows compatibility: https:\/\/github.com\/beloglazov\/vim-online-thesaurus\/issues\/14","package":"vim-online-thesaurus.tar.gz","4":"vim-online-thesaurus.tar.gz","src_id":"22907","5":"22907","creation_date":"1423696172","6":"1423696172"},{"0":"4588","vim_version":"7.0","1":"7.0","script_version":"0.1.8","2":"0.1.8","version_comment":"Improved Windows support: https:\/\/github.com\/beloglazov\/vim-online-thesaurus\/pull\/13","3":"Improved Windows support: https:\/\/github.com\/beloglazov\/vim-online-thesaurus\/pull\/13","package":"vim-online-thesaurus.tar.gz","4":"vim-online-thesaurus.tar.gz","src_id":"22893","5":"22893","creation_date":"1423442751","6":"1423442751"},{"0":"4588","vim_version":"7.0","1":"7.0","script_version":"0.1.7","2":"0.1.7","version_comment":"Updated the parser to adapt to the new HTML layout of thesaurus.com","3":"Updated the parser to adapt to the new HTML layout of thesaurus.com","package":"vim-online-thesaurus.tar.gz","4":"vim-online-thesaurus.tar.gz","src_id":"20979","5":"20979","creation_date":"1383042872","6":"1383042872"},{"0":"4588","vim_version":"7.0","1":"7.0","script_version":"0.1.6","2":"0.1.6","version_comment":"Split the default command into two: `:OnlineThesaurusCurrentWord` and a short command that can be called manually with an argument `:Thesaurus word`.","3":"Split the default command into two: `:OnlineThesaurusCurrentWord` and a short command that can be called manually with an argument `:Thesaurus word`.","package":"vim-online-thesaurus.tar.gz","4":"vim-online-thesaurus.tar.gz","src_id":"20867","5":"20867","creation_date":"1380674090","6":"1380674090"},{"0":"4588","vim_version":"7.0","1":"7.0","script_version":"0.1.5","2":"0.1.5","version_comment":"A few cross-platform compatibility improvements","3":"A few cross-platform compatibility improvements","package":"vim-online-thesaurus.tar.gz","4":"vim-online-thesaurus.tar.gz","src_id":"20697","5":"20697","creation_date":"1377135877","6":"1377135877"},{"0":"4588","vim_version":"7.0","1":"7.0","script_version":"0.1.4","2":"0.1.4","version_comment":"Fixed the plugin to work correctly with the new version of thesaurus.com","3":"Fixed the plugin to work correctly with the new version of thesaurus.com","package":"vim-online-thesaurus.tar.gz","4":"vim-online-thesaurus.tar.gz","src_id":"20696","5":"20696","creation_date":"1377092811","6":"1377092811"},{"0":"4588","vim_version":"7.0","1":"7.0","script_version":"0.1.3","2":"0.1.3","version_comment":"Fixed the documentation: `let g:online_thesaurus_map_keys = 0` to disable the default key binding","3":"Fixed the documentation: `let g:online_thesaurus_map_keys = 0` to disable the default key binding","package":"vim-online-thesaurus.tar.gz","4":"vim-online-thesaurus.tar.gz","src_id":"20362","5":"20362","creation_date":"1371363074","6":"1371363074"},{"0":"4588","vim_version":"7.0","1":"7.0","script_version":"0.1.2","2":"0.1.2","version_comment":"Replaced wget with curl (available on Mac OS X by default).","3":"Replaced wget with curl (available on Mac OS X by default).","package":"vim-online-thesaurus.tar.gz","4":"vim-online-thesaurus.tar.gz","src_id":"20220","5":"20220","creation_date":"1369652497","6":"1369652497"},{"0":"4588","vim_version":"7.0","1":"7.0","script_version":"0.1.1","2":"0.1.1","version_comment":"Fixed some Mac\/Linux compatibility issues.","3":"Fixed some Mac\/Linux compatibility issues.","package":"vim-online-thesaurus.tar.gz","4":"vim-online-thesaurus.tar.gz","src_id":"20175","5":"20175","creation_date":"1369052143","6":"1369052143"},{"0":"4588","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"vim-online-thesaurus.tar.gz","4":"vim-online-thesaurus.tar.gz","src_id":"20158","5":"20158","creation_date":"1368948012","6":"1368948012"}]},"4587":{"script_id":"4587","0":"4587","script_name":"vim-neatstatus","1":"vim-neatstatus","script_type":"utility","2":"utility","summary":"Simple and neat status line that looks good and works well.","3":"Simple and neat status line that looks good and works well.","description":"A neat status line with color changing mode indicator. It is nowhere near as powerful as Powerline but if you just need something simple, fast and easy this will work great.\r\n\r\nScreenshot: http:\/\/i.imgur.com\/7ySiHql.png\r\n\r\nInformation in the status line provided from left to right:\r\n\r\n    - Vim Mode (green box)\r\n    - Server name \/ session name (black box)\r\n    - File path\r\n    - File type (eg. python, ruby, etc..)\r\n    - File format (eg. unix, dos, etc..)\r\n    - File encoding (eg. utf8, latin1, etc..)\r\n    - Buffer number\r\n    - Current line, total number of lines (purple box)\r\n    - Percentage of file read\r\n    - Relative column number (from first character)\r\n    - Absolute column number (from start of line)\r\n    - Modified \/ Unmodified (pink box)\r\n\r\nWorks well with Obvious-Mode: vimscript#2212\r\n\r\n--\r\n\r\nGithub: https:\/\/github.com\/maciakl\/vim-neatstatus\r\n","4":"A neat status line with color changing mode indicator. It is nowhere near as powerful as Powerline but if you just need something simple, fast and easy this will work great.\r\n\r\nScreenshot: http:\/\/i.imgur.com\/7ySiHql.png\r\n\r\nInformation in the status line provided from left to right:\r\n\r\n    - Vim Mode (green box)\r\n    - Server name \/ session name (black box)\r\n    - File path\r\n    - File type (eg. python, ruby, etc..)\r\n    - File format (eg. unix, dos, etc..)\r\n    - File encoding (eg. utf8, latin1, etc..)\r\n    - Buffer number\r\n    - Current line, total number of lines (purple box)\r\n    - Percentage of file read\r\n    - Relative column number (from first character)\r\n    - Absolute column number (from start of line)\r\n    - Modified \/ Unmodified (pink box)\r\n\r\nWorks well with Obvious-Mode: vimscript#2212\r\n\r\n--\r\n\r\nGithub: https:\/\/github.com\/maciakl\/vim-neatstatus\r\n","install_details":"Place in .vim\/plugins\r\n\r\nYou can also install it via Pathogen: \r\n\r\ncd ~\/.vim\/bundle\r\ngit clone git:\/\/github.com\/maciakl\/vim-neatstatus.git","5":"Place in .vim\/plugins\r\n\r\nYou can also install it via Pathogen: \r\n\r\ncd ~\/.vim\/bundle\r\ngit clone git:\/\/github.com\/maciakl\/vim-neatstatus.git","first_name":"Luke","6":"Luke","last_name":"Maciak","7":"Maciak","releases":[{"0":"4587","vim_version":"7.3","1":"7.3","script_version":"0.2","2":"0.2","version_comment":"Fixed the console bug; Visual mode color indication now works normally.","3":"Fixed the console bug; Visual mode color indication now works normally.","package":"neatstatus.vim","4":"neatstatus.vim","src_id":"21603","5":"21603","creation_date":"1394588032","6":"1394588032"},{"0":"4587","vim_version":"7.3","1":"7.3","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"neatstatus.vim","4":"neatstatus.vim","src_id":"20156","5":"20156","creation_date":"1368931934","6":"1368931934"}]},"4586":{"script_id":"4586","0":"4586","script_name":"vim-colorscheme-switcher","1":"vim-colorscheme-switcher","script_type":"utility","2":"utility","summary":"Easily & quickly switch between color schemes","3":"Easily & quickly switch between color schemes","description":"The colorscheme switcher plug-in for the Vim text editor makes it easy to quickly switch between colorschemes. It defines commands and mappings to switch to the next and previous color schemes:\r\n\r\n\u00e2\u0080\u00a2 :NextColorScheme command and <F8> mapping\r\n\u00e2\u0080\u00a2 :PrevColorScheme command and <Shift-F8> mapping\r\n\r\nFor more information about the plug-in please refer to its homepage or the project page on GitHub: \r\n\r\n\u00e2\u0080\u00a2 http:\/\/peterodding.com\/code\/vim\/colorscheme-switcher\/ \r\n\u00e2\u0080\u00a2 http:\/\/github.com\/xolox\/vim-colorscheme-switcher\r\n\r\nIf you have questions, bug reports, suggestions, etc. the author can be contacted at peter@peterodding.com. If you like this plug-in please vote for it below!","4":"The colorscheme switcher plug-in for the Vim text editor makes it easy to quickly switch between colorschemes. It defines commands and mappings to switch to the next and previous color schemes:\r\n\r\n\u00e2\u0080\u00a2 :NextColorScheme command and <F8> mapping\r\n\u00e2\u0080\u00a2 :PrevColorScheme command and <Shift-F8> mapping\r\n\r\nFor more information about the plug-in please refer to its homepage or the project page on GitHub: \r\n\r\n\u00e2\u0080\u00a2 http:\/\/peterodding.com\/code\/vim\/colorscheme-switcher\/ \r\n\u00e2\u0080\u00a2 http:\/\/github.com\/xolox\/vim-colorscheme-switcher\r\n\r\nIf you have questions, bug reports, suggestions, etc. the author can be contacted at peter@peterodding.com. If you like this plug-in please vote for it below!","install_details":"Please note that the vim-colorscheme-switcher plug-in requires my vim-misc plug-in which is separately distributed (see vimscript #4597). \r\n\r\nUnzip the most recent ZIP archives of the vim-colorscheme-switcher and vim-misc plug-ins inside your Vim profile directory (usually this is ~\/.vim on UNIX and %USERPROFILE%\\vimfiles on Windows), restart Vim and execute the command :helptags ~\/.vim\/doc (use :helptags ~\\vimfiles\\doc instead on Windows). Now try it out: Execute :NextColorScheme to switch to the next color scheme.\r\n\r\nIf you didn't change the plug-in's configuration you can now use the F8 and Shift-F8 keys to switch to the next\/previous color scheme.\r\n\r\nIf you prefer you can also use Pathogen, Vundle or a similar tool to install & update the vim-colorscheme-switcher and vim-misc plug-ins using a local clone of the git repository.","5":"Please note that the vim-colorscheme-switcher plug-in requires my vim-misc plug-in which is separately distributed (see vimscript #4597). \r\n\r\nUnzip the most recent ZIP archives of the vim-colorscheme-switcher and vim-misc plug-ins inside your Vim profile directory (usually this is ~\/.vim on UNIX and %USERPROFILE%\\vimfiles on Windows), restart Vim and execute the command :helptags ~\/.vim\/doc (use :helptags ~\\vimfiles\\doc instead on Windows). Now try it out: Execute :NextColorScheme to switch to the next color scheme.\r\n\r\nIf you didn't change the plug-in's configuration you can now use the F8 and Shift-F8 keys to switch to the next\/previous color scheme.\r\n\r\nIf you prefer you can also use Pathogen, Vundle or a similar tool to install & update the vim-colorscheme-switcher and vim-misc plug-ins using a local clone of the git repository.","first_name":"Peter","6":"Peter","last_name":"Odding","7":"Odding","releases":[{"0":"4586","vim_version":"7.0","1":"7.0","script_version":"0.5.1","2":"0.5.1","version_comment":" \u00e2\u0080\u00a2 Potential workaround for color scheme switching in terminal Vim:\n   http:\/\/github.com\/xolox\/vim-colorscheme-switcher\/commit\/4d9807a","3":" \u00e2\u0080\u00a2 Potential workaround for color scheme switching in terminal Vim:\n   http:\/\/github.com\/xolox\/vim-colorscheme-switcher\/commit\/4d9807a","package":"colorscheme-switcher.zip","4":"colorscheme-switcher.zip","src_id":"23117","5":"23117","creation_date":"1427919003","6":"1427919003"},{"0":"4586","vim_version":"7.0","1":"7.0","script_version":"0.5","2":"0.5","version_comment":" \u00e2\u0080\u00a2 Make it possible to exclude color schemes in $VIMRUNTIME\/colors:\n   http:\/\/github.com\/xolox\/vim-colorscheme-switcher\/commit\/03ed734","3":" \u00e2\u0080\u00a2 Make it possible to exclude color schemes in $VIMRUNTIME\/colors:\n   http:\/\/github.com\/xolox\/vim-colorscheme-switcher\/commit\/03ed734","package":"colorscheme-switcher.zip","4":"colorscheme-switcher.zip","src_id":"22626","5":"22626","creation_date":"1416422862","6":"1416422862"},{"0":"4586","vim_version":"7.0","1":"7.0","script_version":"0.4.1","2":"0.4.1","version_comment":" \u00e2\u0080\u00a2 Mention vim-colorscheme-manager in README:\n   http:\/\/github.com\/xolox\/vim-colorscheme-switcher\/commit\/1c87ba8\n\n \u00e2\u0080\u00a2 Enable usage from vimrc (improved robustness, see issue #4 on GitHub):\n   http:\/\/github.com\/xolox\/vim-colorscheme-switcher\/commit\/689c86b","3":" \u00e2\u0080\u00a2 Mention vim-colorscheme-manager in README:\n   http:\/\/github.com\/xolox\/vim-colorscheme-switcher\/commit\/1c87ba8\n\n \u00e2\u0080\u00a2 Enable usage from vimrc (improved robustness, see issue #4 on GitHub):\n   http:\/\/github.com\/xolox\/vim-colorscheme-switcher\/commit\/689c86b","package":"colorscheme-switcher.zip","4":"colorscheme-switcher.zip","src_id":"22096","5":"22096","creation_date":"1403726424","6":"1403726424"},{"0":"4586","vim_version":"7.0","1":"7.0","script_version":"0.4","2":"0.4","version_comment":" \u00e2\u0080\u00a2 Implement request in issue #3 (option to override :colorscheme command):\n   http:\/\/github.com\/xolox\/vim-colorscheme-switcher\/commit\/25265ac","3":" \u00e2\u0080\u00a2 Implement request in issue #3 (option to override :colorscheme command):\n   http:\/\/github.com\/xolox\/vim-colorscheme-switcher\/commit\/25265ac","package":"colorscheme-switcher.zip","4":"colorscheme-switcher.zip","src_id":"22069","5":"22069","creation_date":"1403285585","6":"1403285585"},{"0":"4586","vim_version":"7.0","1":"7.0","script_version":"0.3","2":"0.3","version_comment":" \u00e2\u0080\u00a2 Implement :RandomColorScheme (mapped to <C-F8> by default):\n   http:\/\/github.com\/xolox\/vim-colorscheme-switcher\/commit\/9c52c02","3":" \u00e2\u0080\u00a2 Implement :RandomColorScheme (mapped to <C-F8> by default):\n   http:\/\/github.com\/xolox\/vim-colorscheme-switcher\/commit\/9c52c02","package":"colorscheme-switcher.zip","4":"colorscheme-switcher.zip","src_id":"22060","5":"22060","creation_date":"1403204259","6":"1403204259"},{"0":"4586","vim_version":"7.0","1":"7.0","script_version":"0.2.5","2":"0.2.5","version_comment":" \u00e2\u0080\u00a2 Make sure vim-misc is installed, politely complain if it isn't:\n   http:\/\/github.com\/xolox\/vim-colorscheme-switcher\/commit\/487260a","3":" \u00e2\u0080\u00a2 Make sure vim-misc is installed, politely complain if it isn't:\n   http:\/\/github.com\/xolox\/vim-colorscheme-switcher\/commit\/487260a","package":"colorscheme-switcher.zip","4":"colorscheme-switcher.zip","src_id":"20679","5":"20679","creation_date":"1376930294","6":"1376930294"},{"0":"4586","vim_version":"7.0","1":"7.0","script_version":"0.2.4","2":"0.2.4","version_comment":" \u00e2\u0080\u00a2 Document vim-misc as external dependency (needs to be installed separately from now on):\n   http:\/\/github.com\/xolox\/vim-colorscheme-switcher\/commit\/afeefed","3":" \u00e2\u0080\u00a2 Document vim-misc as external dependency (needs to be installed separately from now on):\n   http:\/\/github.com\/xolox\/vim-colorscheme-switcher\/commit\/afeefed","package":"colorscheme-switcher.zip","4":"colorscheme-switcher.zip","src_id":"20211","5":"20211","creation_date":"1369506683","6":"1369506683"},{"0":"4586","vim_version":"7.0","1":"7.0","script_version":"0.2.2","2":"0.2.2","version_comment":" \u00e2\u0080\u00a2 Updated miscellaneous scripts:\n   http:\/\/github.com\/xolox\/vim-colorscheme-switcher\/commit\/5e32341","3":" \u00e2\u0080\u00a2 Updated miscellaneous scripts:\n   http:\/\/github.com\/xolox\/vim-colorscheme-switcher\/commit\/5e32341","package":"colorscheme-switcher.zip","4":"colorscheme-switcher.zip","src_id":"20176","5":"20176","creation_date":"1369054017","6":"1369054017"},{"0":"4586","vim_version":"7.0","1":"7.0","script_version":"0.2.1","2":"0.2.1","version_comment":" \u00e2\u0080\u00a2 Add link to Vim Online page in README.md, also create INSTALL.md:\n   http:\/\/github.com\/xolox\/vim-colorscheme-switcher\/commit\/27e01bf\n\n \u00e2\u0080\u00a2 Updated miscellaneous scripts:\n   http:\/\/github.com\/xolox\/vim-colorscheme-switcher\/commit\/74e905c","3":" \u00e2\u0080\u00a2 Add link to Vim Online page in README.md, also create INSTALL.md:\n   http:\/\/github.com\/xolox\/vim-colorscheme-switcher\/commit\/27e01bf\n\n \u00e2\u0080\u00a2 Updated miscellaneous scripts:\n   http:\/\/github.com\/xolox\/vim-colorscheme-switcher\/commit\/74e905c","package":"colorscheme-switcher.zip","4":"colorscheme-switcher.zip","src_id":"20164","5":"20164","creation_date":"1369002763","6":"1369002763"},{"0":"4586","vim_version":"7.0","1":"7.0","script_version":"0.2","2":"0.2","version_comment":"Initial upload","3":"Initial upload","package":"colorscheme-switcher.zip","4":"colorscheme-switcher.zip","src_id":"20155","5":"20155","creation_date":"1368915867","6":"1368915867"}]},"4585":{"script_id":"4585","0":"4585","script_name":"vim-bgimg","1":"vim-bgimg","script_type":"utility","2":"utility","summary":"Background Image for Windows GVim","3":"Background Image for Windows GVim","description":"Windows only.\r\n\r\nUSAGE:\r\n  1. set background color\r\n    :call bgimg#set_bg(0xFFFFFF) \" 0xRRGGBB\r\n    For Example:\r\n    :call bgimg#set_bg(str2nr(synIDattr(hlID('Normal'), 'bg#')[1:], 16))\r\n  2. set background image\r\n    :call bgimg#set_image(\"path\/to\/img.bmp\")\r\n\r\nImage will be drawn for background color you set.\r\nBe aware of bitmap header version.  LoadImage() doesn't support newer one.","4":"Windows only.\r\n\r\nUSAGE:\r\n  1. set background color\r\n    :call bgimg#set_bg(0xFFFFFF) \" 0xRRGGBB\r\n    For Example:\r\n    :call bgimg#set_bg(str2nr(synIDattr(hlID('Normal'), 'bg#')[1:], 16))\r\n  2. set background image\r\n    :call bgimg#set_image(\"path\/to\/img.bmp\")\r\n\r\nImage will be drawn for background color you set.\r\nBe aware of bitmap header version.  LoadImage() doesn't support newer one.","install_details":"","5":"","first_name":"Yukihiro","6":"Yukihiro","last_name":"Nakadaira","7":"Nakadaira","releases":[{"0":"4585","vim_version":"7.3","1":"7.3","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"vim-bgimg.zip","4":"vim-bgimg.zip","src_id":"20152","5":"20152","creation_date":"1368807644","6":"1368807644"}]},"4584":{"script_id":"4584","0":"4584","script_name":"mix.vim","1":"mix.vim","script_type":"utility","2":"utility","summary":"Plugin for using Elixir's build tool, mix","3":"Plugin for using Elixir's build tool, mix","description":"## Usage \r\n\r\n:Mix [command] - runs the default mix task (the \"run\" task, unless otherwise configured), or the given command. \r\n:Mclean - cleans generated application files \r\n:Mcompile - compiles sources files \r\n:Mdeps - lists project dependencies and their status \r\n:Mdeps clean - removes dependency files \r\n:Mdeps compile - compiles dependencies \r\n:Mdeps get - gets all out of date dependencies \r\n:Mdeps unlock - unlocks all dependencies \r\n:Mdeps update - updates project dependencies \r\n\r\n## Planned commands \r\n\r\n:Mixfile - opens the project Mixfile. \r\n:Mdeps unlock <deps> - unlocks specific dependencies \r\n:Mdeps update <deps> - updates specific dependencies \r\n:Mdo - executes the commands separated by comma \r\n:Mescript - generates an escript and replaces the current buffer \r\n:Mrebar - installs rebar locally \r\n:Mrun - runs the given expression \r\n:Mtest - runs the project's tests","4":"## Usage \r\n\r\n:Mix [command] - runs the default mix task (the \"run\" task, unless otherwise configured), or the given command. \r\n:Mclean - cleans generated application files \r\n:Mcompile - compiles sources files \r\n:Mdeps - lists project dependencies and their status \r\n:Mdeps clean - removes dependency files \r\n:Mdeps compile - compiles dependencies \r\n:Mdeps get - gets all out of date dependencies \r\n:Mdeps unlock - unlocks all dependencies \r\n:Mdeps update - updates project dependencies \r\n\r\n## Planned commands \r\n\r\n:Mixfile - opens the project Mixfile. \r\n:Mdeps unlock <deps> - unlocks specific dependencies \r\n:Mdeps update <deps> - updates specific dependencies \r\n:Mdo - executes the commands separated by comma \r\n:Mescript - generates an escript and replaces the current buffer \r\n:Mrebar - installs rebar locally \r\n:Mrun - runs the given expression \r\n:Mtest - runs the project's tests","install_details":"I recommend installing pathogen.vim, then running the following:\r\n\r\ncd ~\/.vim\/bundle\r\ngit clone git:\/\/github.com\/mattonrails\/vim-mix.git","5":"I recommend installing pathogen.vim, then running the following:\r\n\r\ncd ~\/.vim\/bundle\r\ngit clone git:\/\/github.com\/mattonrails\/vim-mix.git","first_name":"Matthew","6":"Matthew","last_name":"Conway","7":"Conway","releases":[{"0":"4584","vim_version":"7.0","1":"7.0","script_version":"0.10","2":"0.10","version_comment":"Initial upload","3":"Initial upload","package":"vim-mix.zip","4":"vim-mix.zip","src_id":"20147","5":"20147","creation_date":"1368688613","6":"1368688613"}]},"4583":{"script_id":"4583","0":"4583","script_name":"DevLife","1":"DevLife","script_type":"game","2":"game","summary":"A very basic text game. Sort of RPG.","3":"A very basic text game. Sort of RPG.","description":"DevLife v1.1, Jan 2024\r\n========================\r\n(c)2024 Evgueni Antonov, https:\/\/www.linkedin.com\/in\/eantonoff\/\r\nLicense: GPL v3, http:\/\/www.gnu.org\/licenses\/gpl-3.0.html\r\n\r\nThank you for downloading DevLife!\r\n\r\nYou may freely distribute and modify the file, as long as the program\r\nremains free of charge.\r\n\r\n\r\nCHANGELOG\r\n------------------------\r\n2024-01-07: v1.1 Updated for Vim 8.2, tested on Lubuntu 22.04\r\n2013-05-10: v1.0 Initial version release for Vim 7.3, tested on Windows 7\r\n\r\n\r\nWHAT IS THIS\r\n------------------------\r\nA text-based role-playing-like game, designed to run as a Vimscript.\r\n\r\nIn short: You take the role of a software developer working for a\r\nsoftware development company. Your daily tasks are only three:\r\n- Work\r\n- Create code backups\r\n- Have fun\r\n\r\nThis is my first game ever and was created in no time, as an exercice\r\nto learn Vimscript. It is not perfect and trough testing I've found it\r\nis not well balanced, but it was never the point to make it perfect.\r\n\r\nEnjoy!\r\nEvgueni Antonov\r\n\r\n\r\nWHAT DO I NEED TO RUN IT\r\n------------------------\r\nYou need Vim (http:\/\/www.vim.org). \r\nThis script was written for Vim 7.3 for Windows 7 and is last fixed for\r\nVim 8.2 and tested on Lubuntu 22.04.\r\nIt is not designed to be run when multiple windows and buffers are open.\r\n\r\nI will upload this to GitHub, so for any bug-reports, please submit there.\r\n\r\nSo far, no bugs are discovered, if you discover one, please submit. If\r\nyou discover a way to better balance the game, please submit a feature\r\nrequest.\r\n\r\nThank you!\r\n\r\nFor details on how to run and play, please read the README.txt","4":"DevLife v1.1, Jan 2024\r\n========================\r\n(c)2024 Evgueni Antonov, https:\/\/www.linkedin.com\/in\/eantonoff\/\r\nLicense: GPL v3, http:\/\/www.gnu.org\/licenses\/gpl-3.0.html\r\n\r\nThank you for downloading DevLife!\r\n\r\nYou may freely distribute and modify the file, as long as the program\r\nremains free of charge.\r\n\r\n\r\nCHANGELOG\r\n------------------------\r\n2024-01-07: v1.1 Updated for Vim 8.2, tested on Lubuntu 22.04\r\n2013-05-10: v1.0 Initial version release for Vim 7.3, tested on Windows 7\r\n\r\n\r\nWHAT IS THIS\r\n------------------------\r\nA text-based role-playing-like game, designed to run as a Vimscript.\r\n\r\nIn short: You take the role of a software developer working for a\r\nsoftware development company. Your daily tasks are only three:\r\n- Work\r\n- Create code backups\r\n- Have fun\r\n\r\nThis is my first game ever and was created in no time, as an exercice\r\nto learn Vimscript. It is not perfect and trough testing I've found it\r\nis not well balanced, but it was never the point to make it perfect.\r\n\r\nEnjoy!\r\nEvgueni Antonov\r\n\r\n\r\nWHAT DO I NEED TO RUN IT\r\n------------------------\r\nYou need Vim (http:\/\/www.vim.org). \r\nThis script was written for Vim 7.3 for Windows 7 and is last fixed for\r\nVim 8.2 and tested on Lubuntu 22.04.\r\nIt is not designed to be run when multiple windows and buffers are open.\r\n\r\nI will upload this to GitHub, so for any bug-reports, please submit there.\r\n\r\nSo far, no bugs are discovered, if you discover one, please submit. If\r\nyou discover a way to better balance the game, please submit a feature\r\nrequest.\r\n\r\nThank you!\r\n\r\nFor details on how to run and play, please read the README.txt","install_details":"WINDOWS:\r\nJust copy the script file devlife.vim anywhere within Vim's path.\r\n\r\nLINUX:\r\nmkdir ~\/.vim\/plugin\r\ncp <DOWNLOADED_PATH>\/devlife.vim ~\/.vim\/plugin\r\n\r\nFor details: README.txt","5":"WINDOWS:\r\nJust copy the script file devlife.vim anywhere within Vim's path.\r\n\r\nLINUX:\r\nmkdir ~\/.vim\/plugin\r\ncp <DOWNLOADED_PATH>\/devlife.vim ~\/.vim\/plugin\r\n\r\nFor details: README.txt","first_name":"Evgueni","6":"Evgueni","last_name":"Antonov","7":"Antonov","releases":[{"0":"4583","vim_version":"7.3","1":"7.3","script_version":"1.1","2":"1.1","version_comment":"Updated for Vim 8.2, tested on Lubuntu 22.04. It should work on older Vim versions too. The first version was created on Vim 7.3, so this is the minimum version required, just in case.","3":"Updated for Vim 8.2, tested on Lubuntu 22.04. It should work on older Vim versions too. The first version was created on Vim 7.3, so this is the minimum version required, just in case.","package":"DevLife_11_STABLE.zip","4":"DevLife_11_STABLE.zip","src_id":"28605","5":"28605","creation_date":"1707071999","6":"1707071999"},{"0":"4583","vim_version":"7.3","1":"7.3","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"DevLife_10_STABLE.zip","4":"DevLife_10_STABLE.zip","src_id":"20133","5":"20133","creation_date":"1368506811","6":"1368506811"}]},"4582":{"script_id":"4582","0":"4582","script_name":"Conque GDB","1":"Conque GDB","script_type":"utility","2":"utility","summary":"GDB command line interface and terminal emulator in (G)Vim.","3":"GDB command line interface and terminal emulator in (G)Vim.","description":"Conque GDB turns Vim buffers into terminal emulators, which enables you to run CLI programs from inside Vim windows.\r\n\r\nAlthough you can run any CLI program with Conque GDB. The main reason for this plugin is to offer a nice and complete GDB command line interface inside of Vim. See demonstration video http:\/\/www.youtube.com\/watch?v=ZcSjaYSoqnc&feature=youtu.be (watch in HQ).\r\n\r\nIf you start a new debugging session with the ConqueGdb command, Conque GDB will automatically open the appropriate source files when break points are hit, and highlight the line where program execution has stopped.\r\n\r\nConque GDB runs on both Unix and Windows. However if you install Conque GDB on a Unix system with GDB 7.0+ compiled with python support, Conque GDB will be able to highlight lines to mark where you have currently placed break points.\r\n\r\nConque GDB ships with a modified version of Conque Term (Conque Shell) version 2.3. This new version of Conque Term comes with new options and new features. The most noticeable new feature is the ability to update windows that are not in focus.","4":"Conque GDB turns Vim buffers into terminal emulators, which enables you to run CLI programs from inside Vim windows.\r\n\r\nAlthough you can run any CLI program with Conque GDB. The main reason for this plugin is to offer a nice and complete GDB command line interface inside of Vim. See demonstration video http:\/\/www.youtube.com\/watch?v=ZcSjaYSoqnc&feature=youtu.be (watch in HQ).\r\n\r\nIf you start a new debugging session with the ConqueGdb command, Conque GDB will automatically open the appropriate source files when break points are hit, and highlight the line where program execution has stopped.\r\n\r\nConque GDB runs on both Unix and Windows. However if you install Conque GDB on a Unix system with GDB 7.0+ compiled with python support, Conque GDB will be able to highlight lines to mark where you have currently placed break points.\r\n\r\nConque GDB ships with a modified version of Conque Term (Conque Shell) version 2.3. This new version of Conque Term comes with new options and new features. The most noticeable new feature is the ability to update windows that are not in focus.","install_details":"Before installing you need (G)Vim 7.3+ compiled with +python support.\r\nOn Unix (OS X, Linux etc.) you need GDB 6.3+, but 7.0+ is recommended.\r\nOn Windows you need MinGW GDB 7.0+, see http:\/\/www.mingw.org\/wiki\/Getting_Started for MinGW installation instructions.\r\n\r\nDownload the latest conque_gdb.vmb file below. Open the conque_gdb.vmb file with vim and issue the following commands\r\n    :so %\r\n    :q\r\n\r\nWhen you have installed Conque GDB take a look at the help files doc\/conque_gdb.txt and doc\/conque_term.txt for a through explanation of the plugin.","5":"Before installing you need (G)Vim 7.3+ compiled with +python support.\r\nOn Unix (OS X, Linux etc.) you need GDB 6.3+, but 7.0+ is recommended.\r\nOn Windows you need MinGW GDB 7.0+, see http:\/\/www.mingw.org\/wiki\/Getting_Started for MinGW installation instructions.\r\n\r\nDownload the latest conque_gdb.vmb file below. Open the conque_gdb.vmb file with vim and issue the following commands\r\n    :so %\r\n    :q\r\n\r\nWhen you have installed Conque GDB take a look at the help files doc\/conque_gdb.txt and doc\/conque_term.txt for a through explanation of the plugin.","first_name":"Andreas","6":"Andreas","last_name":"Lynge","7":"Lynge","releases":[{"0":"4582","vim_version":"7.3","1":"7.3","script_version":"0.16","2":"0.16","version_comment":"Added command ConqueTermPaste which can be used to paste the previously yanked text.","3":"Added command ConqueTermPaste which can be used to paste the previously yanked text.","package":"conque_gdb.vmb","4":"conque_gdb.vmb","src_id":"24695","5":"24695","creation_date":"1478026025","6":"1478026025"},{"0":"4582","vim_version":"7.3","1":"7.3","script_version":"0.15","2":"0.15","version_comment":"* Fixed problem causing error E484 when starting vim with Conque GDB on some systems.","3":"* Fixed problem causing error E484 when starting vim with Conque GDB on some systems.","package":"conque_gdb.vmb","4":"conque_gdb.vmb","src_id":"24138","5":"24138","creation_date":"1458940617","6":"1458940617"},{"0":"4582","vim_version":"7.3","1":"7.3","script_version":"0.14","2":"0.14","version_comment":"* Added option to modify the amount of milliseconds to sleep before reading GDB output. Thanks to Matthias Bilger for implementing this option.","3":"* Added option to modify the amount of milliseconds to sleep before reading GDB output. Thanks to Matthias Bilger for implementing this option.","package":"conque_gdb.vmb","4":"conque_gdb.vmb","src_id":"23209","5":"23209","creation_date":"1429736553","6":"1429736553"},{"0":"4582","vim_version":"7.3","1":"7.3","script_version":"0.13","2":"0.13","version_comment":"* Added command (ConqueGdbExe) to change path to GDB executable at runtime, useful for cross development. Thanks to Anatolii Sakhnik for implementing this feature.","3":"* Added command (ConqueGdbExe) to change path to GDB executable at runtime, useful for cross development. Thanks to Anatolii Sakhnik for implementing this feature.","package":"conque_gdb.vmb","4":"conque_gdb.vmb","src_id":"22846","5":"22846","creation_date":"1422390911","6":"1422390911"},{"0":"4582","vim_version":"7.3","1":"7.3","script_version":"0.12","2":"0.12","version_comment":"* Added new option to enable\/disable saving of command history from keyboard mappings in the CLI window.\r\n* Improved the read unfocused option.\r\n* Fixed problem with having wrong window as previous window.","3":"* Added new option to enable\/disable saving of command history from keyboard mappings in the CLI window.\r\n* Improved the read unfocused option.\r\n* Fixed problem with having wrong window as previous window.","package":"conque_gdb.vmb","4":"conque_gdb.vmb","src_id":"22755","5":"22755","creation_date":"1420417956","6":"1420417956"},{"0":"4582","vim_version":"7.3","1":"7.3","script_version":"0.11","2":"0.11","version_comment":"* Resolved problem with moving cursor to wrong window when break points were hit. (This could happen when a taglist window was open while debugging).","3":"* Resolved problem with moving cursor to wrong window when break points were hit. (This could happen when a taglist window was open while debugging).","package":"conque_gdb.vmb","4":"conque_gdb.vmb","src_id":"22559","5":"22559","creation_date":"1414101994","6":"1414101994"},{"0":"4582","vim_version":"7.3","1":"7.3","script_version":"0.10","2":"0.10","version_comment":"* Fixed problem with setting breakpoints on multi-line macros.","3":"* Fixed problem with setting breakpoints on multi-line macros.","package":"conque_gdb.vmb","4":"conque_gdb.vmb","src_id":"22163","5":"22163","creation_date":"1404761685","6":"1404761685"},{"0":"4582","vim_version":"7.3","1":"7.3","script_version":"0.9","2":"0.9","version_comment":"* Solved problem with some times moving cursor to the wrong window when the same buffer was opened in multiple windows","3":"* Solved problem with some times moving cursor to the wrong window when the same buffer was opened in multiple windows","package":"conque_gdb.vmb","4":"conque_gdb.vmb","src_id":"21515","5":"21515","creation_date":"1392934606","6":"1392934606"},{"0":"4582","vim_version":"7.3","1":"7.3","script_version":"0.8","2":"0.8","version_comment":"* Fixed problem with Conque GDB not being able to remove breakpoints when a file buffer was reloaded. Again, thanks to Sergey Vlasov for discovering and reporting the problem.","3":"* Fixed problem with Conque GDB not being able to remove breakpoints when a file buffer was reloaded. Again, thanks to Sergey Vlasov for discovering and reporting the problem.","package":"conque_gdb.vmb","4":"conque_gdb.vmb","src_id":"21465","5":"21465","creation_date":"1392118761","6":"1392118761"},{"0":"4582","vim_version":"7.3","1":"7.3","script_version":"0.7","2":"0.7","version_comment":"* Fixed problem with always having terminal window as previous window when the g:ConqueTerm_ReadUnfocused option was enabled.\r\n* Improved Conque GDB window selection algorithm. It's now more intuitive which window is selected for source file when debugging a program and program execution stops.","3":"* Fixed problem with always having terminal window as previous window when the g:ConqueTerm_ReadUnfocused option was enabled.\r\n* Improved Conque GDB window selection algorithm. It's now more intuitive which window is selected for source file when debugging a program and program execution stops.","package":"conque_gdb.vmb","4":"conque_gdb.vmb","src_id":"21381","5":"21381","creation_date":"1390735406","6":"1390735406"},{"0":"4582","vim_version":"7.3","1":"7.3","script_version":"0.6","2":"0.6","version_comment":"* Fixed \"Command terminated, Press ENTER or type command to continue\" bug (caused by ignoring SIGCHLD with SIG_IGN). Thanks to Sergey Vlasov for discovering the problem and help fixing it.\r\n* Fixed g:ConqueTerm_Color option, such that we can disable terminal colors.","3":"* Fixed \"Command terminated, Press ENTER or type command to continue\" bug (caused by ignoring SIGCHLD with SIG_IGN). Thanks to Sergey Vlasov for discovering the problem and help fixing it.\r\n* Fixed g:ConqueTerm_Color option, such that we can disable terminal colors.","package":"conque_gdb.vmb","4":"conque_gdb.vmb","src_id":"21322","5":"21322","creation_date":"1389727640","6":"1389727640"},{"0":"4582","vim_version":"7.3","1":"7.3","script_version":"0.5","2":"0.5","version_comment":"* Disable session support\r\n* Better name for Conque GDB buffer","3":"* Disable session support\r\n* Better name for Conque GDB buffer","package":"conque_gdb.vmb","4":"conque_gdb.vmb","src_id":"20340","5":"20340","creation_date":"1370994467","6":"1370994467"},{"0":"4582","vim_version":"7.3","1":"7.3","script_version":"0.4","2":"0.4","version_comment":"* Bug fixes\r\n* New keyboard mappings","3":"* Bug fixes\r\n* New keyboard mappings","package":"conque_gdb.vmb","4":"conque_gdb.vmb","src_id":"20337","5":"20337","creation_date":"1370990356","6":"1370990356"},{"0":"4582","vim_version":"7.3","1":"7.3","script_version":"0.2","2":"0.2","version_comment":"* More intuitive output on Windows.\r\n* Fixed bug when setting break points on last line in functions on Unix.","3":"* More intuitive output on Windows.\r\n* Fixed bug when setting break points on last line in functions on Unix.","package":"conque_gdb.vmb","4":"conque_gdb.vmb","src_id":"20078","5":"20078","creation_date":"1368080131","6":"1368080131"},{"0":"4582","vim_version":"7.3","1":"7.3","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"conque_gdb.vmb","4":"conque_gdb.vmb","src_id":"20077","5":"20077","creation_date":"1368066101","6":"1368066101"}]},"4581":{"script_id":"4581","0":"4581","script_name":"vim-identifier-movement","1":"vim-identifier-movement","script_type":"ftplugin","2":"ftplugin","summary":"smartly move through program language identifier","3":"smartly move through program language identifier","description":"vim plugin, one way to improve move using \"w W b B\",\r\nsmartly move between language identifier, skip language keywords,comment,strings\r\n\r\ndefault key mapping:\r\n\t<C-n>\tnext language identifier\r\n\t<C-p>\tprevious language identifier\r\n\r\ncurrent support language:\r\n\tc, c++, vim, python\r\n\r\nhttps:\/\/github.com\/rargo\/vim-identifier-movement","4":"vim plugin, one way to improve move using \"w W b B\",\r\nsmartly move between language identifier, skip language keywords,comment,strings\r\n\r\ndefault key mapping:\r\n\t<C-n>\tnext language identifier\r\n\t<C-p>\tprevious language identifier\r\n\r\ncurrent support language:\r\n\tc, c++, vim, python\r\n\r\nhttps:\/\/github.com\/rargo\/vim-identifier-movement","install_details":"please consider pathogen, much easy\r\n    https:\/\/github.com\/tpope\/vim-pathogen","5":"please consider pathogen, much easy\r\n    https:\/\/github.com\/tpope\/vim-pathogen","first_name":"rargo","6":"rargo","last_name":"ye","7":"ye","releases":[{"0":"4581","vim_version":"7.0","1":"7.0","script_version":"1.2","2":"1.2","version_comment":"skip multiple lines comment","3":"skip multiple lines comment","package":"vim-identifier-movement.zip","4":"vim-identifier-movement.zip","src_id":"20134","5":"20134","creation_date":"1368520724","6":"1368520724"},{"0":"4581","vim_version":"7.0","1":"7.0","script_version":"1.1","2":"1.1","version_comment":"fix internal variable did_ftplugin conflict with vim basic package","3":"fix internal variable did_ftplugin conflict with vim basic package","package":"vim-identifier-movement.zip","4":"vim-identifier-movement.zip","src_id":"20096","5":"20096","creation_date":"1368328790","6":"1368328790"},{"0":"4581","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"vim-identifier-movement.zip","4":"vim-identifier-movement.zip","src_id":"20070","5":"20070","creation_date":"1368026854","6":"1368026854"}]},"4580":{"script_id":"4580","0":"4580","script_name":"vim-niji","1":"vim-niji","script_type":"utility","2":"utility","summary":"Yet another rainbow parentheses plugin.","3":"Yet another rainbow parentheses plugin.","description":"Niji (Rainbow) is yet another rainbow parentheses plugin for Vim. It\u00e2\u0080\u0099s good for Common Lisp, Scheme and Clojure \u00e2\u0080\u0094 with two colour schemes \u00e2\u0080\u0094 out-of-the-box. Just install, and you\u00e2\u0080\u0099re good to go. The filetypes, matching characters and colours Niji uses are completely configurable.\r\n\r\nWhilst not a fork, Niji builds upon the work of various rainbow parantheses plugins, starting with \u00e2\u0080\u0098RainbowParenthsis.vim\u00e2\u0080\u0099 by John Gilmore, \u00e2\u0080\u0098rainbow_parenthsis.vim\u00e2\u0080\u0099 by Martin Krischik and Luc Hermitte, and \u00e2\u0080\u0098rainbow_parentheses.vim\u00e2\u0080\u0099 by \u00e2\u0080\u0098kien\u00e2\u0080\u0099.\r\n\r\nNiji also takes its default colour scheme from the Lisp syntax file provided in distributions of Vim and written by Dr. Charles E. Campbell, Jr.","4":"Niji (Rainbow) is yet another rainbow parentheses plugin for Vim. It\u00e2\u0080\u0099s good for Common Lisp, Scheme and Clojure \u00e2\u0080\u0094 with two colour schemes \u00e2\u0080\u0094 out-of-the-box. Just install, and you\u00e2\u0080\u0099re good to go. The filetypes, matching characters and colours Niji uses are completely configurable.\r\n\r\nWhilst not a fork, Niji builds upon the work of various rainbow parantheses plugins, starting with \u00e2\u0080\u0098RainbowParenthsis.vim\u00e2\u0080\u0099 by John Gilmore, \u00e2\u0080\u0098rainbow_parenthsis.vim\u00e2\u0080\u0099 by Martin Krischik and Luc Hermitte, and \u00e2\u0080\u0098rainbow_parentheses.vim\u00e2\u0080\u0099 by \u00e2\u0080\u0098kien\u00e2\u0080\u0099.\r\n\r\nNiji also takes its default colour scheme from the Lisp syntax file provided in distributions of Vim and written by Dr. Charles E. Campbell, Jr.","install_details":"A Vimball is provided here. For other installation methods, check the GitHub project page: http:\/\/github.com\/amdt\/vim-niji\r\n\r\nOpen the Vimball with Vim. For example, from a UNIX shell you might run:\r\n\r\nvim vim-niji.vbm\r\n\r\nOnce loaded in Vim, run the following two commands:\r\n\r\n:so %\r\n:q","5":"A Vimball is provided here. For other installation methods, check the GitHub project page: http:\/\/github.com\/amdt\/vim-niji\r\n\r\nOpen the Vimball with Vim. For example, from a UNIX shell you might run:\r\n\r\nvim vim-niji.vbm\r\n\r\nOnce loaded in Vim, run the following two commands:\r\n\r\n:so %\r\n:q","first_name":"Alastair","6":"Alastair","last_name":"Touw","7":"Touw","releases":[{"0":"4580","vim_version":"7.0","1":"7.0","script_version":"v1.0.3","2":"v1.0.3","version_comment":"* Remove non-functional `g:niji_match_all_filetypes`.","3":"* Remove non-functional `g:niji_match_all_filetypes`.","package":"vim-niji-1.0.3.vmb","4":"vim-niji-1.0.3.vmb","src_id":"21966","5":"21966","creation_date":"1401524617","6":"1401524617"},{"0":"4580","vim_version":"7.0","1":"7.0","script_version":"1.0.2","2":"1.0.2","version_comment":"* Update documentation.","3":"* Update documentation.","package":"vim-niji-1.0.2.vmb","4":"vim-niji-1.0.2.vmb","src_id":"20261","5":"20261","creation_date":"1370169460","6":"1370169460"},{"0":"4580","vim_version":"7.0","1":"7.0","script_version":"1.0.1","2":"1.0.1","version_comment":"* Add 'GetLatestVimScripts' support.","3":"* Add 'GetLatestVimScripts' support.","package":"vim-niji-1.0.1.vmb","4":"vim-niji-1.0.1.vmb","src_id":"20068","5":"20068","creation_date":"1368013692","6":"1368013692"},{"0":"4580","vim_version":"7.0","1":"7.0","script_version":"1.0.0","2":"1.0.0","version_comment":"Initial upload","3":"Initial upload","package":"vim-niji.vmb","4":"vim-niji.vmb","src_id":"20067","5":"20067","creation_date":"1368011635","6":"1368011635"}]},"4579":{"script_id":"4579","0":"4579","script_name":"keepcomment.vim","1":"keepcomment.vim","script_type":"ftplugin","2":"ftplugin","summary":"Simple comment easy to keep coding","3":"Simple comment easy to keep coding","description":"`u    comment line(s)\r\n`o    uncomment line(s)\r\n\r\n`i     comment line(s) while keep coding\r\n            for trying new code line\r\n            but if you want code line(s) keep intact\r\n            ( default : same as `k, that is, to the upper )\r\n\r\n`k    comment out to the upper\r\n`j     comment out to the below\r\n      \r\nVisual blocking or numbering(buffer count) in normal mode \r\nwill work as expected.\r\n\r\nCurrently \r\nfor \r\n        python, Makefile, snippet, cpp, javascript, ruby, sh\r\n        matlab, tex, txt, anonymous, c, html\r\n\r\nYou might feel free to add other comment string and filetype\r\nby modifying s:CommentStringMap\r\nand sure you can change key map to your favorite.\r\n\r\n\r\nIf you're looking forward most mature and complete plugin,\r\nyou must ckeck [The NERD Commenter]\r\n\r\nhttp:\/\/www.vim.org\/scripts\/script.php?script_id=1218\r\n\r\n","4":"`u    comment line(s)\r\n`o    uncomment line(s)\r\n\r\n`i     comment line(s) while keep coding\r\n            for trying new code line\r\n            but if you want code line(s) keep intact\r\n            ( default : same as `k, that is, to the upper )\r\n\r\n`k    comment out to the upper\r\n`j     comment out to the below\r\n      \r\nVisual blocking or numbering(buffer count) in normal mode \r\nwill work as expected.\r\n\r\nCurrently \r\nfor \r\n        python, Makefile, snippet, cpp, javascript, ruby, sh\r\n        matlab, tex, txt, anonymous, c, html\r\n\r\nYou might feel free to add other comment string and filetype\r\nby modifying s:CommentStringMap\r\nand sure you can change key map to your favorite.\r\n\r\n\r\nIf you're looking forward most mature and complete plugin,\r\nyou must ckeck [The NERD Commenter]\r\n\r\nhttp:\/\/www.vim.org\/scripts\/script.php?script_id=1218\r\n\r\n","install_details":"drop in your plugin directory (i.e. vim\/vimfiles\/plugin etc)","5":"drop in your plugin directory (i.e. vim\/vimfiles\/plugin etc)","first_name":"Han-seok","6":"Han-seok","last_name":"Ryu","7":"Ryu","releases":[{"0":"4579","vim_version":"7.3","1":"7.3","script_version":"0.7","2":"0.7","version_comment":"remap","3":"remap","package":"keepcomment.vim","4":"keepcomment.vim","src_id":"21113","5":"21113","creation_date":"1385445186","6":"1385445186"},{"0":"4579","vim_version":"7.3","1":"7.3","script_version":"0.5","2":"0.5","version_comment":"directable comment (up down)","3":"directable comment (up down)","package":"keepcomment.vim","4":"keepcomment.vim","src_id":"21014","5":"21014","creation_date":"1383901567","6":"1383901567"},{"0":"4579","vim_version":"7.3","1":"7.3","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"KeepComment.vim","4":"KeepComment.vim","src_id":"20066","5":"20066","creation_date":"1368005065","6":"1368005065"}]},"4578":{"script_id":"4578","0":"4578","script_name":"throughpairs","1":"throughpairs","script_type":"ftplugin","2":"ftplugin","summary":"  spread or shrink the space of parenthesis symmetrically & smart traverse paren","3":"  spread or shrink the space of parenthesis symmetrically & smart traverse paren","description":" 1. traverse\r\n\r\n\r\nmap  <M-f> : forward traverse parentheses,  will stop at end position\r\nimap <M-b> : backward traverse parentheses, will stop at start position\r\n\r\n\r\n\r\nlet abc = func( foo( xyz ), love( child(toy, food(water) ), parent ) )\r\n                                        |                                               |  |              |  |\r\n                         |      |                   |          |               |           \r\n\r\n\r\n\r\n 2. spread or shrink\r\n\r\n\r\nimap <M-l> : spread out parentheses\r\nimap <M-h> : shink parentheses\r\n\r\n\r\n\r\n 3. easy pass\r\n\r\n\r\n<C-j> especially, in python coding can pass through \"...\" '...' (...) [...] <...> in insert mode selectively\r\n      if the cursor meet keyword (say, class object(abc), if (...), for(...), etc.)\r\n      <C-j> key will work as <right arrow> or <tab> or <enter> or spot \":\" and <enter>\r\n      so as to user don't care about which key to press.\r\n\r\n    (\"'[{word▌}]'\") \r\n    (\"'[{word}▌]'\") \r\n    (\"'[{word}]▌'\") \r\n    (\"'[{word}]'▌\") \r\n    (\"'[{word}]'\"▌) \r\n    (\"'[{word}]'\")▌       \r\n\r\n\r\n        in python \r\n            def func(▄) \r\n            def func(): \r\n                ▄ \r\n\r\n        in C \r\n            void func(▄) \r\n            void func() { \r\n                ▄ \r\n            } \r\n\r\n    else works like enter key if the pos of cursor is at last column. \r\n \r\n\r\nYou can add or modify \r\nlet g:closingList = [\"'\",'\"',\")\",\"]\",\">\",\"}\",\"$\",''] \r\n\r\nin which <C-j> key can pass through. \r\n\r\n\r\n\r\nNote : all work will be done in insert mode except <M-f>\r\n\r\n","4":" 1. traverse\r\n\r\n\r\nmap  <M-f> : forward traverse parentheses,  will stop at end position\r\nimap <M-b> : backward traverse parentheses, will stop at start position\r\n\r\n\r\n\r\nlet abc = func( foo( xyz ), love( child(toy, food(water) ), parent ) )\r\n                                        |                                               |  |              |  |\r\n                         |      |                   |          |               |           \r\n\r\n\r\n\r\n 2. spread or shrink\r\n\r\n\r\nimap <M-l> : spread out parentheses\r\nimap <M-h> : shink parentheses\r\n\r\n\r\n\r\n 3. easy pass\r\n\r\n\r\n<C-j> especially, in python coding can pass through \"...\" '...' (...) [...] <...> in insert mode selectively\r\n      if the cursor meet keyword (say, class object(abc), if (...), for(...), etc.)\r\n      <C-j> key will work as <right arrow> or <tab> or <enter> or spot \":\" and <enter>\r\n      so as to user don't care about which key to press.\r\n\r\n    (\"'[{word▌}]'\") \r\n    (\"'[{word}▌]'\") \r\n    (\"'[{word}]▌'\") \r\n    (\"'[{word}]'▌\") \r\n    (\"'[{word}]'\"▌) \r\n    (\"'[{word}]'\")▌       \r\n\r\n\r\n        in python \r\n            def func(▄) \r\n            def func(): \r\n                ▄ \r\n\r\n        in C \r\n            void func(▄) \r\n            void func() { \r\n                ▄ \r\n            } \r\n\r\n    else works like enter key if the pos of cursor is at last column. \r\n \r\n\r\nYou can add or modify \r\nlet g:closingList = [\"'\",'\"',\")\",\"]\",\">\",\"}\",\"$\",''] \r\n\r\nin which <C-j> key can pass through. \r\n\r\n\r\n\r\nNote : all work will be done in insert mode except <M-f>\r\n\r\n","install_details":"drop in your vimfiles\/plugin\r\n\r\nor\r\n\r\nusing Bundle\r\n\r\nin your .vimrc ( _vimrc for windows )\r\nBundle 'https:\/\/github.com\/escher9\/throughpairs'\r\n\r\n","5":"drop in your vimfiles\/plugin\r\n\r\nor\r\n\r\nusing Bundle\r\n\r\nin your .vimrc ( _vimrc for windows )\r\nBundle 'https:\/\/github.com\/escher9\/throughpairs'\r\n\r\n","first_name":"Han-seok","6":"Han-seok","last_name":"Ryu","7":"Ryu","releases":[{"0":"4578","vim_version":"7.3","1":"7.3","script_version":"1.0","2":"1.0","version_comment":"remap","3":"remap","package":"throughpairs.zip","4":"throughpairs.zip","src_id":"21095","5":"21095","creation_date":"1385201366","6":"1385201366"},{"0":"4578","vim_version":"7.3","1":"7.3","script_version":"1.0","2":"1.0","version_comment":"initial stable","3":"initial stable","package":"throughpairs.zip","4":"throughpairs.zip","src_id":"21091","5":"21091","creation_date":"1385093598","6":"1385093598"},{"0":"4578","vim_version":"7.3","1":"7.3","script_version":"0.5","2":"0.5","version_comment":"Initial upload","3":"Initial upload","package":"easy-through-pairing.vim","4":"easy-through-pairing.vim","src_id":"20130","5":"20130","creation_date":"1368485715","6":"1368485715"}]},"4577":{"script_id":"4577","0":"4577","script_name":"linepower.vim","1":"linepower.vim","script_type":"utility","2":"utility","summary":"local themes for powerline ","3":"local themes for powerline ","description":"This is redundant to http:\/\/www.vim.org\/scripts\/edit_script.php?script_id=4576\r\n\r\nPlease goto homepage for a better view and screenshots.\r\n\r\nHomepage: http:\/\/zhaocai.github.io\/linepower.vim\/ \r\n","4":"This is redundant to http:\/\/www.vim.org\/scripts\/edit_script.php?script_id=4576\r\n\r\nPlease goto homepage for a better view and screenshots.\r\n\r\nHomepage: http:\/\/zhaocai.github.io\/linepower.vim\/ \r\n","install_details":"http:\/\/zhaocai.github.io\/GoldenView.Vim\/\r\n","5":"http:\/\/zhaocai.github.io\/GoldenView.Vim\/\r\n","first_name":"Zhao","6":"Zhao","last_name":"Cai","7":"Cai","releases":[{"0":"4577","vim_version":"7.3","1":"7.3","script_version":"1.0.0","2":"1.0.0","version_comment":"Initial upload","3":"Initial upload","package":"linepower.vim-1.0.0.zip","4":"linepower.vim-1.0.0.zip","src_id":"20057","5":"20057","creation_date":"1367975312","6":"1367975312"}]},"4576":{"script_id":"4576","0":"4576","script_name":"linepower.vim","1":"linepower.vim","script_type":"utility","2":"utility","summary":"local themes for powerline","3":"local themes for powerline","description":"\nPlease goto homepage for a better view and screenshots.\n\nHomepage: http:\/\/zhaocai.github.io\/linepower.vim\/ \n\n\nThis powerline extension is a quickstart for adding customized powerline local themes in vim.\nYou may fork it and add more local themes for your convenience.\n\n## Included Local Themes\n\n- unite.vim\n- tagbar\n- nerdtree\n- rvm\/rbenv version\n- syntastic\n- vimshell\n- vimfiler\n- asyncommand\n- quickfix \/ locationlist\n","4":"\nPlease goto homepage for a better view and screenshots.\n\nHomepage: http:\/\/zhaocai.github.io\/linepower.vim\/ \n\n\nThis powerline extension is a quickstart for adding customized powerline local themes in vim.\nYou may fork it and add more local themes for your convenience.\n\n## Included Local Themes\n\n- unite.vim\n- tagbar\n- nerdtree\n- rvm\/rbenv version\n- syntastic\n- vimshell\n- vimfiler\n- asyncommand\n- quickfix \/ locationlist\n","install_details":"http:\/\/zhaocai.github.io\/linepower.vim\/\n","5":"http:\/\/zhaocai.github.io\/linepower.vim\/\n","first_name":"Zhao","6":"Zhao","last_name":"Cai","7":"Cai","releases":[{"0":"4576","vim_version":"7.3","1":"7.3","script_version":"1.4.0","2":"1.4.0","version_comment":"- update config file to upstream (visual_range, syntastic, etc.)\n","3":"- update config file to upstream (visual_range, syntastic, etc.)\n","package":"linepower.vim-1.4.0.zip","4":"linepower.vim-1.4.0.zip","src_id":"20706","5":"20706","creation_date":"1377347808","6":"1377347808"},{"0":"4576","vim_version":"7.3","1":"7.3","script_version":"1.3.0","2":"1.3.0","version_comment":"- change default divider (it is not well aligned)\n- separate quickfix\/locationlist local theme\n- add previewwindow local theme\n","3":"- change default divider (it is not well aligned)\n- separate quickfix\/locationlist local theme\n- add previewwindow local theme\n","package":"linepower.vim-1.3.0.zip","4":"linepower.vim-1.3.0.zip","src_id":"20193","5":"20193","creation_date":"1369181847","6":"1369181847"},{"0":"4576","vim_version":"7.3","1":"7.3","script_version":"1.2.0","2":"1.2.0","version_comment":"- tweak colors\n- 'only_ruby' option for rvm\/rbenv segments \n","3":"- tweak colors\n- 'only_ruby' option for rvm\/rbenv segments \n","package":"linepower.vim-1.2.0.zip","4":"linepower.vim-1.2.0.zip","src_id":"20076","5":"20076","creation_date":"1368061517","6":"1368061517"},{"0":"4576","vim_version":"7.3","1":"7.3","script_version":"1.1.0","2":"1.1.0","version_comment":"- update solarized colors\n- add vimshell, vimfiler local theme\n- improve tagbar theme\n","3":"- update solarized colors\n- add vimshell, vimfiler local theme\n- improve tagbar theme\n","package":"linepower.vim-1.1.0.zip","4":"linepower.vim-1.1.0.zip","src_id":"20063","5":"20063","creation_date":"1367996771","6":"1367996771"},{"0":"4576","vim_version":"7.3","1":"7.3","script_version":"1.0.0","2":"1.0.0","version_comment":"Initial upload","3":"Initial upload","package":"linepower.vim-1.0.0.zip","4":"linepower.vim-1.0.0.zip","src_id":"20056","5":"20056","creation_date":"1367975282","6":"1367975282"}]},"4575":{"script_id":"4575","0":"4575","script_name":"prev_indent","1":"prev_indent","script_type":"utility","2":"utility","summary":"Utility functions for custom indentation of line under cursor","3":"Utility functions for custom indentation of line under cursor","description":"This script provides 2 utility commands PrevIndent and AlignWith for doing\r\ncustom indentation tricks with line under cursor in Insert and Normal modes.\r\nOriginally there was only one of them: PrevIndent, and that explains the name\r\nof the script.\r\n\r\nCommand PrevIndent moves line under cursor to the previous indentation\r\nlevel. Normally this command is not really needed as soon as indentation\r\nlevels in most file types tend to correspond to the value of the\r\nshiftwidth and the result is easily achieved by pressing <C-d> in Insert\r\nmode. But this is not a case for some programming languages (for example\r\nHaskell indentation rules are very specific).\r\n\r\nCommand PrevIndent simply aligns the beginning of the current line with\r\nthe first previous line that starts from a less position.\r\n\r\nRecommended mappings are\r\n\r\nInsert mode:\r\n\r\n    imap <silent> <C-d>       <Plug>PrevIndent\r\n\r\nif you want to replace with PrevIndent standard <C-d> Insert mapping or\r\n\r\n    imap <silent> <C-g><C-g>  <Plug>PrevIndent\r\n\r\n(press <C-g> twice) otherwise.\r\n\r\nNormal mode:\r\n\r\n    nmap <silent> <C-k>k      :PrevIndent<CR>\r\n\r\nAnother command provided by the script is AlignWith. It finds a symbol\r\nthat was specified by user dynamically (i.e. using getchar()) in the right\r\nhand side of the previous line and aligns beginning of the current line\r\nwith the column of the found symbol. If a symbol was not found then it is\r\nsearched from beginning of the previous line. Repeating AlignWith will\r\ncycle alignment of the current line to the right through all searched\r\nsymbols in the previous line. User can specify an order of symbol to\r\nsearch. For example issuing command\r\n\r\n    :AlignWith 2\r\n\r\nand then pressing '(' will skip first found '(' in the previous line and\r\nalign current line to the second found parenthesis.\r\n\r\nRecommended mappings are\r\n\r\nInsert mode:\r\n\r\n    imap <silent> <C-g>g      <Plug>AlignWith\r\n\r\nNormal mode:\r\n\r\n    nmap <silent> <C-k>g      :AlignWith<CR>\r\n\r\nIn both Insert and Normal modes command AlignWith will wait until user\r\nenters a character to align with. So for example in Insert mode user must\r\nenter <C-g>g and another character after that.\r\n\r\nBoth commands must behave well for different settings of <Tab> expansions.","4":"This script provides 2 utility commands PrevIndent and AlignWith for doing\r\ncustom indentation tricks with line under cursor in Insert and Normal modes.\r\nOriginally there was only one of them: PrevIndent, and that explains the name\r\nof the script.\r\n\r\nCommand PrevIndent moves line under cursor to the previous indentation\r\nlevel. Normally this command is not really needed as soon as indentation\r\nlevels in most file types tend to correspond to the value of the\r\nshiftwidth and the result is easily achieved by pressing <C-d> in Insert\r\nmode. But this is not a case for some programming languages (for example\r\nHaskell indentation rules are very specific).\r\n\r\nCommand PrevIndent simply aligns the beginning of the current line with\r\nthe first previous line that starts from a less position.\r\n\r\nRecommended mappings are\r\n\r\nInsert mode:\r\n\r\n    imap <silent> <C-d>       <Plug>PrevIndent\r\n\r\nif you want to replace with PrevIndent standard <C-d> Insert mapping or\r\n\r\n    imap <silent> <C-g><C-g>  <Plug>PrevIndent\r\n\r\n(press <C-g> twice) otherwise.\r\n\r\nNormal mode:\r\n\r\n    nmap <silent> <C-k>k      :PrevIndent<CR>\r\n\r\nAnother command provided by the script is AlignWith. It finds a symbol\r\nthat was specified by user dynamically (i.e. using getchar()) in the right\r\nhand side of the previous line and aligns beginning of the current line\r\nwith the column of the found symbol. If a symbol was not found then it is\r\nsearched from beginning of the previous line. Repeating AlignWith will\r\ncycle alignment of the current line to the right through all searched\r\nsymbols in the previous line. User can specify an order of symbol to\r\nsearch. For example issuing command\r\n\r\n    :AlignWith 2\r\n\r\nand then pressing '(' will skip first found '(' in the previous line and\r\nalign current line to the second found parenthesis.\r\n\r\nRecommended mappings are\r\n\r\nInsert mode:\r\n\r\n    imap <silent> <C-g>g      <Plug>AlignWith\r\n\r\nNormal mode:\r\n\r\n    nmap <silent> <C-k>g      :AlignWith<CR>\r\n\r\nIn both Insert and Normal modes command AlignWith will wait until user\r\nenters a character to align with. So for example in Insert mode user must\r\nenter <C-g>g and another character after that.\r\n\r\nBoth commands must behave well for different settings of <Tab> expansions.","install_details":"put the script in plugin directory","5":"put the script in plugin directory","first_name":"Alexey","6":"Alexey","last_name":"Radkov","7":"Radkov","releases":[{"0":"4575","vim_version":"7.0","1":"7.0","script_version":"0.3","2":"0.3","version_comment":"minor improvements and fixes","3":"minor improvements and fixes","package":"prev_indent.vim","4":"prev_indent.vim","src_id":"21579","5":"21579","creation_date":"1394226696","6":"1394226696"},{"0":"4575","vim_version":"7.0","1":"7.0","script_version":"0.2.2","2":"0.2.2","version_comment":"skip empty lines when indenting","3":"skip empty lines when indenting","package":"prev_indent.vim","4":"prev_indent.vim","src_id":"20110","5":"20110","creation_date":"1368460450","6":"1368460450"},{"0":"4575","vim_version":"7.0","1":"7.0","script_version":"0.2.1","2":"0.2.1","version_comment":"Fixed command AlignWith in repeated mode","3":"Fixed command AlignWith in repeated mode","package":"prev_indent.vim","4":"prev_indent.vim","src_id":"20091","5":"20091","creation_date":"1368278919","6":"1368278919"},{"0":"4575","vim_version":"7.0","1":"7.0","script_version":"0.2","2":"0.2","version_comment":"Added command AlignWith to align against arbitrary symbol on the previous line","3":"Added command AlignWith to align against arbitrary symbol on the previous line","package":"prev_indent.vim","4":"prev_indent.vim","src_id":"20081","5":"20081","creation_date":"1368120988","6":"1368120988"},{"0":"4575","vim_version":"7.0","1":"7.0","script_version":"0.1.1","2":"0.1.1","version_comment":"Normal mode supported.","3":"Normal mode supported.","package":"prev_indent.vim","4":"prev_indent.vim","src_id":"20051","5":"20051","creation_date":"1367958147","6":"1367958147"},{"0":"4575","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"prev_indent.vim","4":"prev_indent.vim","src_id":"20050","5":"20050","creation_date":"1367956678","6":"1367956678"}]},"4574":{"script_id":"4574","0":"4574","script_name":"dummy test spam script uploaded by maint","1":"dummy test spam script uploaded by maint","script_type":"color scheme","2":"color scheme","summary":"xx","3":"xx","description":"xx","4":"xx","install_details":"xx","5":"xx","first_name":"Marc","6":"Marc","last_name":"Weber","7":"Weber","releases":[{"0":"4574","vim_version":"7.0","1":"7.0","script_version":"xx","2":"xx","version_comment":"Initial upload","3":"Initial upload","package":"xx","4":"xx","src_id":"20038","5":"20038","creation_date":"1367924885","6":"1367924885"}]},"4573":{"script_id":"4573","0":"4573","script_name":"dummy test spam script uploaded by maint","1":"dummy test spam script uploaded by maint","script_type":"color scheme","2":"color scheme","summary":"xx","3":"xx","description":"xx","4":"xx","install_details":"xx","5":"xx","first_name":"Marc","6":"Marc","last_name":"Weber","7":"Weber","releases":[{"0":"4573","vim_version":"7.0","1":"7.0","script_version":"xx","2":"xx","version_comment":"Initial upload","3":"Initial upload","package":"xx","4":"xx","src_id":"20039","5":"20039","creation_date":"1367924885","6":"1367924885"}]},"4572":{"script_id":"4572","0":"4572","script_name":"mystatusline","1":"mystatusline","script_type":"patch","2":"patch","summary":"a statusline style with RICH INFOMATION","3":"a statusline style with RICH INFOMATION","description":"this is the statusline style i'm using","4":"this is the statusline style i'm using","install_details":"\tfirst, put \"mystatusline.vim\"(this file) to dir vim73\/plugin or vimfiles\/plugin\r\n\tsecond, add the follow sentences to your .vimrc or _vimrc :\r\n\r\n\t\t\tset laststatus=2\r\n\t \t\tlet g:mystatusline_actived = 1\r\n\r\n\tthird, restart your vim and enjoy coding.\r\n","5":"\tfirst, put \"mystatusline.vim\"(this file) to dir vim73\/plugin or vimfiles\/plugin\r\n\tsecond, add the follow sentences to your .vimrc or _vimrc :\r\n\r\n\t\t\tset laststatus=2\r\n\t \t\tlet g:mystatusline_actived = 1\r\n\r\n\tthird, restart your vim and enjoy coding.\r\n","first_name":"luo","6":"luo","last_name":"chen","7":"chen","releases":[{"0":"4572","vim_version":"7.3","1":"7.3","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"mystatusline.vim","4":"mystatusline.vim","src_id":"20036","5":"20036","creation_date":"1367896061","6":"1367896061"}]},"4571":{"script_id":"4571","0":"4571","script_name":"rel-jump","1":"rel-jump","script_type":"ftplugin","2":"ftplugin","summary":"Turn up-down motions into jump-motions","3":"Turn up-down motions into jump-motions","description":"rel-jump.vim turns [count]j and [count]k motions into jumps. This way\r\nyou'll be able to jump back to the previous line by using <C-o>, which is\r\nvery handy in conjunction with Vim's relativenumber option.\r\n\r\nProject page: http:\/\/github.com\/buztard\/vim-rel-jump","4":"rel-jump.vim turns [count]j and [count]k motions into jumps. This way\r\nyou'll be able to jump back to the previous line by using <C-o>, which is\r\nvery handy in conjunction with Vim's relativenumber option.\r\n\r\nProject page: http:\/\/github.com\/buztard\/vim-rel-jump","install_details":"Unpack the most recent tarball in your .vim directory or use a plugin manager like vimscript #2332","5":"Unpack the most recent tarball in your .vim directory or use a plugin manager like vimscript #2332","first_name":"Bastian","6":"Bastian","last_name":"Winkler","7":"Winkler","releases":[{"0":"4571","vim_version":"7.3","1":"7.3","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"vim-rel-jump.tar.gz","4":"vim-rel-jump.tar.gz","src_id":"20026","5":"20026","creation_date":"1367797965","6":"1367797965"}]},"4570":{"script_id":"4570","0":"4570","script_name":"textobj-comment","1":"textobj-comment","script_type":"utility","2":"utility","summary":"Text objects for comments","3":"Text objects for comments","description":"The textobj-comment plugin provides text objects to select comments.\r\n\r\n\"ac\" selects a comment including the comment delimiters, \"ic\" selects the comment content without the delimiters.  A third text object, \"aC\", selects a \"big\" comment, including trailing or leading whitespace.\r\n\r\ntextobj-comment uses the filetype-specific 'comments' setting to determine what a comment looks like for a given language.  Make sure you have enabled filetype plugins in your configuration to make this work.\r\n\r\nIn order to find a target, textobj-comment looks for a comment under the cursor, in or at the end of the cursor line, and above the cursor line.  You can see a demo of the text objects and the heuristic in the documentation.\r\n\r\nThis plugin depends on the textobj-user plugin, version 0.4.0 (vimscript #2100).\r\nhttps:\/\/github.com\/kana\/vim-textobj-user\r\n","4":"The textobj-comment plugin provides text objects to select comments.\r\n\r\n\"ac\" selects a comment including the comment delimiters, \"ic\" selects the comment content without the delimiters.  A third text object, \"aC\", selects a \"big\" comment, including trailing or leading whitespace.\r\n\r\ntextobj-comment uses the filetype-specific 'comments' setting to determine what a comment looks like for a given language.  Make sure you have enabled filetype plugins in your configuration to make this work.\r\n\r\nIn order to find a target, textobj-comment looks for a comment under the cursor, in or at the end of the cursor line, and above the cursor line.  You can see a demo of the text objects and the heuristic in the documentation.\r\n\r\nThis plugin depends on the textobj-user plugin, version 0.4.0 (vimscript #2100).\r\nhttps:\/\/github.com\/kana\/vim-textobj-user\r\n","install_details":"Unzip the archive in your ~\/.vim directory.  (On Windows, replace \"~\/.vim\" with \"$HOME\\vimfiles\" everywhere.)\r\n\r\nThis plugin is also hosted on Github at https:\/\/github.com\/glts\/vim-textobj-comment\r\nWith the Pathogen plugin manager the installation is as simple as:\r\n\r\ncd ~\/.vim\/bundle\r\ngit clone git:\/\/github.com\/glts\/vim-textobj-comment.git textobj-comment\r\n\r\nBut this plugin also plays well with the built-in GetLatestVimScripts and other plugin managers such as Vundle, vim-addon-manager, and vim-flavor.\r\n\r\nDon't forget to install textobj-user first if your setup doesn't take care of dependencies automatically.\r\n","5":"Unzip the archive in your ~\/.vim directory.  (On Windows, replace \"~\/.vim\" with \"$HOME\\vimfiles\" everywhere.)\r\n\r\nThis plugin is also hosted on Github at https:\/\/github.com\/glts\/vim-textobj-comment\r\nWith the Pathogen plugin manager the installation is as simple as:\r\n\r\ncd ~\/.vim\/bundle\r\ngit clone git:\/\/github.com\/glts\/vim-textobj-comment.git textobj-comment\r\n\r\nBut this plugin also plays well with the built-in GetLatestVimScripts and other plugin managers such as Vundle, vim-addon-manager, and vim-flavor.\r\n\r\nDon't forget to install textobj-user first if your setup doesn't take care of dependencies automatically.\r\n","first_name":"David","6":"David","last_name":"B\u00c3\u00bcrgin","7":"B\u00c3\u00bcrgin","releases":[{"0":"4570","vim_version":"7.3","1":"7.3","script_version":"1.0.0","2":"1.0.0","version_comment":"Initial upload","3":"Initial upload","package":"textobj-comment.zip","4":"textobj-comment.zip","src_id":"20018","5":"20018","creation_date":"1367655516","6":"1367655516"}]},"4569":{"script_id":"4569","0":"4569","script_name":"breeze.vim","1":"breeze.vim","script_type":"utility","2":"utility","summary":"Html navigation like vim-easymotion","3":"Html navigation like vim-easymotion","description":"\r\nBreeze is a plugin that aims to help developers dealing with HTML files.\r\n\r\n\r\n\r\n","4":"\r\nBreeze is a plugin that aims to help developers dealing with HTML files.\r\n\r\n\r\n\r\n","install_details":"\r\nInstall with your favorite plugin manager.\r\n\r\nRequires Python 2.6+","5":"\r\nInstall with your favorite plugin manager.\r\n\r\nRequires Python 2.6+","first_name":"geck","6":"geck","last_name":" ","7":" ","releases":[{"0":"4569","vim_version":"7.2","1":"7.2","script_version":"2.0","2":"2.0","version_comment":"- Version 2.0","3":"- Version 2.0","package":"breeze.zip","4":"breeze.zip","src_id":"22179","5":"22179","creation_date":"1404976416","6":"1404976416"}]},"4568":{"script_id":"4568","0":"4568","script_name":"gitignore.vim","1":"gitignore.vim","script_type":"utility","2":"utility","summary":"Gitignore files support","3":"Gitignore files support","description":"This plugin provides syntax highlighting, code snippets (using snipMate (https:\/\/github.com\/msanders\/snipmate.vim)) based on https:\/\/github.com\/github\/gitignore snippets and supporing of tComment for `.gitignore` files in Vim.\r\n\r\nFor additional information visit GitHub repository https:\/\/github.com\/rdolgushin\/gitignore.vim. \r\n\r\nRequirements\r\n------------\r\n* For using code snippets your must install snipMate (https:\/\/github.com\/msanders\/snipmate.vim)\r\n* For more fun try out AutoComplPop (http:\/\/www.vim.org\/scripts\/script.php?script_id=1879)\r\n* For commenting\/uncommenting install tComment (https:\/\/github.com\/tomtom\/tcomment_vim)\r\n\r\nUsage\r\n-----\r\n\r\n### Snippets\r\n\r\nGitignore.vim contains an usual snipMate snippets. You can use it by opening your `.gitignore` file, typing snippet name (for example, `Python`) and pressing `<Tab>` key.\r\n\r\n### Commenting\r\n\r\nFor commenting you can use standard tComment `<C-_>` keymap.","4":"This plugin provides syntax highlighting, code snippets (using snipMate (https:\/\/github.com\/msanders\/snipmate.vim)) based on https:\/\/github.com\/github\/gitignore snippets and supporing of tComment for `.gitignore` files in Vim.\r\n\r\nFor additional information visit GitHub repository https:\/\/github.com\/rdolgushin\/gitignore.vim. \r\n\r\nRequirements\r\n------------\r\n* For using code snippets your must install snipMate (https:\/\/github.com\/msanders\/snipmate.vim)\r\n* For more fun try out AutoComplPop (http:\/\/www.vim.org\/scripts\/script.php?script_id=1879)\r\n* For commenting\/uncommenting install tComment (https:\/\/github.com\/tomtom\/tcomment_vim)\r\n\r\nUsage\r\n-----\r\n\r\n### Snippets\r\n\r\nGitignore.vim contains an usual snipMate snippets. You can use it by opening your `.gitignore` file, typing snippet name (for example, `Python`) and pressing `<Tab>` key.\r\n\r\n### Commenting\r\n\r\nFor commenting you can use standard tComment `<C-_>` keymap.","install_details":"* Using pathogen (https:\/\/github.com\/tpope\/vim-pathogen) or vundle(https:\/\/github.com\/gmarik\/vundle) from https:\/\/github.com\/rdolgushin\/gitignore.vim\r\n* Standard Vim way (http:\/\/vimdoc.sourceforge.net\/htmldoc\/usr_05.html#add-plugin)","5":"* Using pathogen (https:\/\/github.com\/tpope\/vim-pathogen) or vundle(https:\/\/github.com\/gmarik\/vundle) from https:\/\/github.com\/rdolgushin\/gitignore.vim\r\n* Standard Vim way (http:\/\/vimdoc.sourceforge.net\/htmldoc\/usr_05.html#add-plugin)","first_name":"Roman","6":"Roman","last_name":"Dolgushin","7":"Dolgushin","releases":[{"0":"4568","vim_version":"7.0","1":"7.0","script_version":"1.05","2":"1.05","version_comment":"Upgraded to https:\/\/github.com\/github\/gitignore\/commit\/eda2ee70de1bf7db7e0aba7c7b71aeb2c1c7eeec","3":"Upgraded to https:\/\/github.com\/github\/gitignore\/commit\/eda2ee70de1bf7db7e0aba7c7b71aeb2c1c7eeec","package":"gitignore.zip","4":"gitignore.zip","src_id":"21616","5":"21616","creation_date":"1394818802","6":"1394818802"},{"0":"4568","vim_version":"7.0","1":"7.0","script_version":"1.04f1","2":"1.04f1","version_comment":"Clojure snippet symlink fix","3":"Clojure snippet symlink fix","package":"gitignore.zip","4":"gitignore.zip","src_id":"21054","5":"21054","creation_date":"1384768213","6":"1384768213"},{"0":"4568","vim_version":"7.0","1":"7.0","script_version":"1.04","2":"1.04","version_comment":"Upgraded to https:\/\/github.com\/github\/gitignore\/commit\/f0f5e38db20332f55b95d938a55e98ae9b05bb3d","3":"Upgraded to https:\/\/github.com\/github\/gitignore\/commit\/f0f5e38db20332f55b95d938a55e98ae9b05bb3d","package":"gitignore.zip","4":"gitignore.zip","src_id":"21051","5":"21051","creation_date":"1384687250","6":"1384687250"},{"0":"4568","vim_version":"7.0","1":"7.0","script_version":"1.03","2":"1.03","version_comment":"plugin\/gitignore.vim removed (to fix Vim splash screen displaying)\r\n\r\nSnippets upgraded to following state: https:\/\/github.com\/github\/gitignore\/commit\/b2c694d792c005c770c42deaa868e97184e31794","3":"plugin\/gitignore.vim removed (to fix Vim splash screen displaying)\r\n\r\nSnippets upgraded to following state: https:\/\/github.com\/github\/gitignore\/commit\/b2c694d792c005c770c42deaa868e97184e31794","package":"gitignore.zip","4":"gitignore.zip","src_id":"20620","5":"20620","creation_date":"1376094000","6":"1376094000"},{"0":"4568","vim_version":"7.0","1":"7.0","script_version":"1.02","2":"1.02","version_comment":"Fixed and improved. See https:\/\/github.com\/rdolgushin\/gitignore.vim\/pull\/1","3":"Fixed and improved. See https:\/\/github.com\/rdolgushin\/gitignore.vim\/pull\/1","package":"gitignore.zip","4":"gitignore.zip","src_id":"19996","5":"19996","creation_date":"1367435509","6":"1367435509"},{"0":"4568","vim_version":"7.0","1":"7.0","script_version":"1.01","2":"1.01","version_comment":"Initial upload","3":"Initial upload","package":"gitignore.zip","4":"gitignore.zip","src_id":"19992","5":"19992","creation_date":"1367418781","6":"1367418781"}]},"4567":{"script_id":"4567","0":"4567","script_name":"w3af.vim","1":"w3af.vim","script_type":"syntax","2":"syntax","summary":"Syntax file for W3AF scripts","3":"Syntax file for W3AF scripts","description":"This syntax file provides syntax highlighting for W3AF scripts, W3AF is a Web Application Attack and Audit Framework (http:\/\/w3af.org\/).\r\n\r\nLicensed under GPLv2.0 like W3AF.","4":"This syntax file provides syntax highlighting for W3AF scripts, W3AF is a Web Application Attack and Audit Framework (http:\/\/w3af.org\/).\r\n\r\nLicensed under GPLv2.0 like W3AF.","install_details":"Just put the file in your vimfiles\/syntax folder. Add the following line to your vimrc file (or e.g filetype.vim to install it for all users) : \r\n\r\nau BufNewFile,BufRead *.w3af setf w3af","5":"Just put the file in your vimfiles\/syntax folder. Add the following line to your vimrc file (or e.g filetype.vim to install it for all users) : \r\n\r\nau BufNewFile,BufRead *.w3af setf w3af","first_name":"Dominique","6":"Dominique","last_name":"RIGHETTO","7":"RIGHETTO","releases":[{"0":"4567","vim_version":"7.3","1":"7.3","script_version":"1.0.0","2":"1.0.0","version_comment":"Initial upload","3":"Initial upload","package":"w3af.vim","4":"w3af.vim","src_id":"19985","5":"19985","creation_date":"1367352939","6":"1367352939"}]},"4554":{"script_id":"4554","0":"4554","script_name":"php annotations syntax","1":"php annotations syntax","script_type":"syntax","2":"syntax","summary":"syntax highlighting for php annotations","3":"syntax highlighting for php annotations","description":"Small script to add  annotations highlighting to php syntax.\r\n\r\nAnnotations within comments are highlighted with pre-defined SpecialComment highlight group name (used for example for backslash escapes in string literals).\r\n\r\nAnnotations highlighting is useful when they are used as more then documentation blocks or comments, like for actual program flow control, as doctrine ORM is using them. Some people might consider such use of comments, as part of the program logic, to be bad practice, and the script author here tends to agree. But this is how annotation syntax works in php, so this is how they  are used anyway. Doctrine ORM tends to look for annotations anywhere within a comment line, but only annotations that start at the beginning of a comment line will be highlighted here.\r\n\r\nphp annotations use docBlock comments (documentation comment blocks, beginning with \/** and ending with *\/) and the main use case for this syntax script is to contrast the regular annotations with any of them accidentally placed within simple comments, where they have no effect, so you can spot them easier.\r\n\r\nIf you find the highlighting annoying with your color scheme or with your annotations usage in php, you may use a command like\r\n     :highlight link SpecialComment Number\r\nto change the appearance (you can replace Number above with some other highlight group you may like), or you can disable the script with the\r\n     :let g:php_annotations_syntax = 0\r\ncommand in your .vimrc file.\r\n\r\nIf and when the main php syntax file provided with Vim ever gets updated to include annotations, this script will become obsolete.\r\n\r\nThat main file is getting quite old with all new php functions and classes added by every new php version; currently there are several newer alternatives on the Vim scripts site, but they like to replace, instead of extend, the main file provided by the distribution.","4":"Small script to add  annotations highlighting to php syntax.\r\n\r\nAnnotations within comments are highlighted with pre-defined SpecialComment highlight group name (used for example for backslash escapes in string literals).\r\n\r\nAnnotations highlighting is useful when they are used as more then documentation blocks or comments, like for actual program flow control, as doctrine ORM is using them. Some people might consider such use of comments, as part of the program logic, to be bad practice, and the script author here tends to agree. But this is how annotation syntax works in php, so this is how they  are used anyway. Doctrine ORM tends to look for annotations anywhere within a comment line, but only annotations that start at the beginning of a comment line will be highlighted here.\r\n\r\nphp annotations use docBlock comments (documentation comment blocks, beginning with \/** and ending with *\/) and the main use case for this syntax script is to contrast the regular annotations with any of them accidentally placed within simple comments, where they have no effect, so you can spot them easier.\r\n\r\nIf you find the highlighting annoying with your color scheme or with your annotations usage in php, you may use a command like\r\n     :highlight link SpecialComment Number\r\nto change the appearance (you can replace Number above with some other highlight group you may like), or you can disable the script with the\r\n     :let g:php_annotations_syntax = 0\r\ncommand in your .vimrc file.\r\n\r\nIf and when the main php syntax file provided with Vim ever gets updated to include annotations, this script will become obsolete.\r\n\r\nThat main file is getting quite old with all new php functions and classes added by every new php version; currently there are several newer alternatives on the Vim scripts site, but they like to replace, instead of extend, the main file provided by the distribution.","install_details":"Copy the provided script file php.vim into your\r\n        ~\/.vim\/after\/syntax\/                                                        (Linux\/Unix)\r\nor\r\n         %USERPROFILE%\\vimfiles\\after\\syntax\\         (Windows)\r\ndirectory.\r\n\r\nIf you already have some another php.vim file (perhaps your own) in your after\/syntax directory, you can create an after\/syntax\/php\/ directory to contain them both.","5":"Copy the provided script file php.vim into your\r\n        ~\/.vim\/after\/syntax\/                                                        (Linux\/Unix)\r\nor\r\n         %USERPROFILE%\\vimfiles\\after\\syntax\\         (Windows)\r\ndirectory.\r\n\r\nIf you already have some another php.vim file (perhaps your own) in your after\/syntax directory, you can create an after\/syntax\/php\/ directory to contain them both.","first_name":"Timothy","6":"Timothy","last_name":"Madden","7":"Madden","releases":[{"0":"4554","vim_version":"7.0","1":"7.0","script_version":"0.3","2":"0.3","version_comment":"Using the more specific SpecialComment highlight group instead of Special for the annotations.","3":"Using the more specific SpecialComment highlight group instead of Special for the annotations.","package":"php.vim","4":"php.vim","src_id":"19991","5":"19991","creation_date":"1367405703","6":"1367405703"},{"0":"4554","vim_version":"7.0","1":"7.0","script_version":"0.2","2":"0.2","version_comment":"Some support for one-line docBlock comments (like \/** @var ClassName $myObj *\/).\r\nHighlighting for strings, numbers and some operators and punctuation within the annotations.","3":"Some support for one-line docBlock comments (like \/** @var ClassName $myObj *\/).\r\nHighlighting for strings, numbers and some operators and punctuation within the annotations.","package":"php.vim","4":"php.vim","src_id":"19990","5":"19990","creation_date":"1367402191","6":"1367402191"},{"0":"4554","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"php.vim","4":"php.vim","src_id":"19971","5":"19971","creation_date":"1367252324","6":"1367252324"}]},"4553":{"script_id":"4553","0":"4553","script_name":"rspec.vim","1":"rspec.vim","script_type":"syntax","2":"syntax","summary":"Rspec syntax highlighting","3":"Rspec syntax highlighting","description":"# Rspec.vim\r\n\r\nThis is improved syntax highlighting for rspec. This is pulled from [Specky](http:\/\/www.vim.org\/scripts\/script.php?script_id=2286) which is a great plugin that just does a little too much for me.\r\n\r\n## Installation\r\n\r\n### With [Vundle](https:\/\/github.com\/gmarik\/vundle)\r\n\r\nAdd:\r\n\r\n```\r\nBundle 'Keithbsmiley\/rspec.vim'\r\n```\r\n\r\nTo your `.vimrc` and run `BundleInstall` from within vim or `vim +BundleInstall +qall` from the command line\r\n\r\n### With [Pathogen](https:\/\/github.com\/tpope\/vim-pathogen)\r\n\r\n```\r\ncd ~\/.vim\/bundle\r\ngit clone https:\/\/github.com\/Keithbsmiley\/rspec.vim.git\r\n```\r\n\r\n## Usage\r\n\r\nBy default this syntax is used with all `*_spec.rb` files. If you don't follow this norm use something like:\r\n\r\n```\r\nautocmd BufReadPost,BufNewFile *_foo.rb set filetype=rspec\r\n```\r\n\r\nIn your `~\/.vimrc`\r\n","4":"# Rspec.vim\r\n\r\nThis is improved syntax highlighting for rspec. This is pulled from [Specky](http:\/\/www.vim.org\/scripts\/script.php?script_id=2286) which is a great plugin that just does a little too much for me.\r\n\r\n## Installation\r\n\r\n### With [Vundle](https:\/\/github.com\/gmarik\/vundle)\r\n\r\nAdd:\r\n\r\n```\r\nBundle 'Keithbsmiley\/rspec.vim'\r\n```\r\n\r\nTo your `.vimrc` and run `BundleInstall` from within vim or `vim +BundleInstall +qall` from the command line\r\n\r\n### With [Pathogen](https:\/\/github.com\/tpope\/vim-pathogen)\r\n\r\n```\r\ncd ~\/.vim\/bundle\r\ngit clone https:\/\/github.com\/Keithbsmiley\/rspec.vim.git\r\n```\r\n\r\n## Usage\r\n\r\nBy default this syntax is used with all `*_spec.rb` files. If you don't follow this norm use something like:\r\n\r\n```\r\nautocmd BufReadPost,BufNewFile *_foo.rb set filetype=rspec\r\n```\r\n\r\nIn your `~\/.vimrc`\r\n","install_details":"","5":"","first_name":"Keith","6":"Keith","last_name":"Smiley","7":"Smiley","releases":[{"0":"4553","vim_version":"7.0","1":"7.0","script_version":"0.1.0","2":"0.1.0","version_comment":"Initial upload","3":"Initial upload","package":"rspec.vim-0.1.0.tar.gz","4":"rspec.vim-0.1.0.tar.gz","src_id":"19970","5":"19970","creation_date":"1367252194","6":"1367252194"}]},"4552":{"script_id":"4552","0":"4552","script_name":"esperanto","1":"esperanto","script_type":"utility","2":"utility","summary":"Plugin for typing in Esperanto","3":"Plugin for typing in Esperanto","description":"Github: https:\/\/github.com\/greyblake\/vim-esperanto\r\n\r\nThe plugin allows to use the international language in Vim. It doesn't require additional Esperanto keyboard in system, and keeps Vim behaviour the same as with English keyboard.","4":"Github: https:\/\/github.com\/greyblake\/vim-esperanto\r\n\r\nThe plugin allows to use the international language in Vim. It doesn't require additional Esperanto keyboard in system, and keeps Vim behaviour the same as with English keyboard.","install_details":"To install the plugin it's enough to copy plugin, doc directories into your .vim directory. But I would recommend to use plugin manager Pathogen or Vundle\r\n","5":"To install the plugin it's enough to copy plugin, doc directories into your .vim directory. But I would recommend to use plugin manager Pathogen or Vundle\r\n","first_name":"Sergey","6":"Sergey","last_name":"Potapov","7":"Potapov","releases":[{"0":"4552","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"vim-esperanto-0.1.zip","4":"vim-esperanto-0.1.zip","src_id":"19955","5":"19955","creation_date":"1367149499","6":"1367149499"}]},"4551":{"script_id":"4551","0":"4551","script_name":"reprocessed.vim","1":"reprocessed.vim","script_type":"ftplugin","2":"ftplugin","summary":"A plugin for working with the Processing programming language.","3":"A plugin for working with the Processing programming language.","description":"A plugin to make it easier to work with the Processing language in vim. It is originally based on https:\/\/github.com\/sophacles\/vim-processing, which was in turn an extension of vim script #2115.\r\n\r\nPlease note that this plugin has currently only been tested on OS X. I would love to hear from you if you use this plugin (successfully or otherwise) on Windows or Linux.\r\n\r\nFeatures:\r\n* Syntax highlighting\r\n* Documentation lookup\r\n* Run sketches from within vim\r\n\r\nFor more detailed information, please see the project on GitHub here: https:\/\/github.com\/willpragnell\/vim-reprocessed","4":"A plugin to make it easier to work with the Processing language in vim. It is originally based on https:\/\/github.com\/sophacles\/vim-processing, which was in turn an extension of vim script #2115.\r\n\r\nPlease note that this plugin has currently only been tested on OS X. I would love to hear from you if you use this plugin (successfully or otherwise) on Windows or Linux.\r\n\r\nFeatures:\r\n* Syntax highlighting\r\n* Documentation lookup\r\n* Run sketches from within vim\r\n\r\nFor more detailed information, please see the project on GitHub here: https:\/\/github.com\/willpragnell\/vim-reprocessed","install_details":"Extract to ~\/.vim, or ~\\vimfiles (Windows).","5":"Extract to ~\/.vim, or ~\\vimfiles (Windows).","first_name":"Will","6":"Will","last_name":"Pragnell","7":"Pragnell","releases":[{"0":"4551","vim_version":"7.3","1":"7.3","script_version":"0.1.0","2":"0.1.0","version_comment":"Initial upload","3":"Initial upload","package":"reprocessed.zip","4":"reprocessed.zip","src_id":"19953","5":"19953","creation_date":"1367090966","6":"1367090966"}]},"4550":{"script_id":"4550","0":"4550","script_name":"PreserveNoEOL","1":"PreserveNoEOL","script_type":"utility","2":"utility","summary":"Preserve missing EOL at the end of text files.","3":"Preserve missing EOL at the end of text files.","description":"DESCRIPTION\r\nThis plugin causes Vim to omit the final newline (<EOL>) at the end of a\r\ntext file when you save it, if it was missing when the file was read. If the\r\nfile was read with <EOL> at the end, it will be saved with one. If it was read\r\nwithout one, it will be saved without one.\r\n\r\nSome (arguably broken) Windows applications (also several text editors) create\r\nfiles without a final <EOL>, so if you have to interoperate with those, or\r\nwant to keep your commits to revision control clean of those changes, this\r\nplugin is for you.\r\n\r\nThis works for all three line ending styles which Vim recognizes: DOS\r\n(Windows), Unix, and traditional Mac. Multiple strategies are implemented to\r\nhandle these cases, so you can choose the one that fits you best.\r\n\r\nHOW IT WORKS\r\nExcept for the internal Vimscript implementation, all other strategies first\r\nlet Vim save the file as usual (with a final <EOL>), and then post-process (on\r\nBufWritePost) the file contents, using file-system API functions to truncate\r\nthe final <EOL>.\r\n\r\nRELATED WORKS\r\nThe pure Vimscript implementation is based on the following VimTip:\r\n    http:\/\/vim.wikia.com\/wiki\/Preserve_missing_end-of-line_at_end_of_text_files\r\n\r\nUSAGE\r\nIf you always want to preserve a misssing <EOL> in text files, just put\r\n    :let g:PreserveNoEOL = 1\r\ninto your vimrc and you're done. If you need more fine-grained control or\r\nwant to just turn this on in particular situations, you can use the following\r\ncommands or the buffer-local flag b:PreserveNoEOL.\r\n\r\n:PreserveNoEOL          For the current buffer, the 'noeol' setting will be\r\n                        preserved on writes. (Normally, Vim only does this for\r\n                        'binary' files.) This has the same effect as setting\r\n                        the marker buffer variable:\r\n                            let b:PreserveNoEOL = 1\r\n\r\n:SetNoEOL               When writing the current buffer, do not append an\r\n                        <EOL> at the end of the last line, even when there\r\n                        used to be one. Same as\r\n                            setlocal noeol | let b:PreserveNoEOL = 1","4":"DESCRIPTION\r\nThis plugin causes Vim to omit the final newline (<EOL>) at the end of a\r\ntext file when you save it, if it was missing when the file was read. If the\r\nfile was read with <EOL> at the end, it will be saved with one. If it was read\r\nwithout one, it will be saved without one.\r\n\r\nSome (arguably broken) Windows applications (also several text editors) create\r\nfiles without a final <EOL>, so if you have to interoperate with those, or\r\nwant to keep your commits to revision control clean of those changes, this\r\nplugin is for you.\r\n\r\nThis works for all three line ending styles which Vim recognizes: DOS\r\n(Windows), Unix, and traditional Mac. Multiple strategies are implemented to\r\nhandle these cases, so you can choose the one that fits you best.\r\n\r\nHOW IT WORKS\r\nExcept for the internal Vimscript implementation, all other strategies first\r\nlet Vim save the file as usual (with a final <EOL>), and then post-process (on\r\nBufWritePost) the file contents, using file-system API functions to truncate\r\nthe final <EOL>.\r\n\r\nRELATED WORKS\r\nThe pure Vimscript implementation is based on the following VimTip:\r\n    http:\/\/vim.wikia.com\/wiki\/Preserve_missing_end-of-line_at_end_of_text_files\r\n\r\nUSAGE\r\nIf you always want to preserve a misssing <EOL> in text files, just put\r\n    :let g:PreserveNoEOL = 1\r\ninto your vimrc and you're done. If you need more fine-grained control or\r\nwant to just turn this on in particular situations, you can use the following\r\ncommands or the buffer-local flag b:PreserveNoEOL.\r\n\r\n:PreserveNoEOL          For the current buffer, the 'noeol' setting will be\r\n                        preserved on writes. (Normally, Vim only does this for\r\n                        'binary' files.) This has the same effect as setting\r\n                        the marker buffer variable:\r\n                            let b:PreserveNoEOL = 1\r\n\r\n:SetNoEOL               When writing the current buffer, do not append an\r\n                        <EOL> at the end of the last line, even when there\r\n                        used to be one. Same as\r\n                            setlocal noeol | let b:PreserveNoEOL = 1","install_details":"INSTALLATION\r\nThis script is packaged as a vimball. If you have the \"gunzip\" decompressor\r\nin your PATH, simply edit the *.vmb.gz package in Vim; otherwise, decompress\r\nthe archive first, e.g. using WinZip. Inside Vim, install by sourcing the\r\nvimball or via the :UseVimball command.\r\n    vim PreserveNoEOL*.vmb.gz\r\n    :so %\r\nOn Linux \/ Unix systems, you also have to make the \"noeol\" script executable:\r\n    :! chmod +x ~\/.vim\/noeol\r\n\r\nTo uninstall, use the :RmVimball command.\r\n\r\nDEPENDENCIES\r\n- Requires Vim 7.0 or higher.\r\n- Vim with the Python (2.x) interface or the Perl interface (optional)\r\n- System Perl interpreter (optional)\r\n\r\nCONFIGURATION\r\nFor a permanent configuration, put the following commands into your vimrc:\r\n\r\nThis plugin supports multiple strategies for keeping the <EOL> off of text\r\nfiles:\r\nWhen Vim is compiled with +python support, a Python function is used to\r\nstrip off the trailing newline after writing the buffer. This even works with\r\n'readonly' files.\r\n    let g:PreserveNoEOL_Function = function('PreserveNoEOL#Python#Preserve')\r\nWhen Vim is compiled with +perl support, a Perl function is used to strip\r\noff the trailing newline after writing the buffer. This even works with\r\n'readonly' files.\r\n    let g:PreserveNoEOL_Function = function('PreserveNoEOL#Perl#Preserve')\r\nWithout Perl support, an similar Perl script is invoked as an external\r\nexecutable. This still requires an installed Perl interpreter, but no Perl\r\nsupport built into Vim.\r\n    let g:PreserveNoEOL_Function = function('PreserveNoEOL#Executable#Preserve')\r\nAs a fallback, a pure Vimscript implementation can be used. This temporarily\r\nsets the 'binary' option on each buffer write and messes with the line\r\nendings.\r\n    let g:PreserveNoEOL_Function = function('PreserveNoEOL#Internal#Preserve')\r\n\r\nThe processing can be delegated to an external executable named \"noeol\". It is\r\nlocated in 'runtimepath' or somewhere on PATH. On Windows, this Perl script is\r\ninvoked through the Perl interpreter. You can use a different path or\r\nexecutable via:\r\n    let g:PreserveNoEOL_Command = 'path\/to\/executable'\r\n\r\nINTEGRATION\r\nYou can influence the write behavior via the buffer-local variable\r\nb:PreserveNoEOL. When this evaluates to true, a 'noeol' setting will be\r\npreserved on writes.\r\nYou can use this variable in autocmds, filetype plugins or a local vimrc to\r\nchange the behavior for certain file types or files in a particular location.\r\n\r\nIf you want to indicate (e.g. in your 'statusline') that the current file's\r\nmissing EOL will be preserved, you can use the PreserveNoEOL#Info#IsPreserve()\r\nfunction, which returns 1 if the plugin will preserve it; 0 otherwise.","5":"INSTALLATION\r\nThis script is packaged as a vimball. If you have the \"gunzip\" decompressor\r\nin your PATH, simply edit the *.vmb.gz package in Vim; otherwise, decompress\r\nthe archive first, e.g. using WinZip. Inside Vim, install by sourcing the\r\nvimball or via the :UseVimball command.\r\n    vim PreserveNoEOL*.vmb.gz\r\n    :so %\r\nOn Linux \/ Unix systems, you also have to make the \"noeol\" script executable:\r\n    :! chmod +x ~\/.vim\/noeol\r\n\r\nTo uninstall, use the :RmVimball command.\r\n\r\nDEPENDENCIES\r\n- Requires Vim 7.0 or higher.\r\n- Vim with the Python (2.x) interface or the Perl interface (optional)\r\n- System Perl interpreter (optional)\r\n\r\nCONFIGURATION\r\nFor a permanent configuration, put the following commands into your vimrc:\r\n\r\nThis plugin supports multiple strategies for keeping the <EOL> off of text\r\nfiles:\r\nWhen Vim is compiled with +python support, a Python function is used to\r\nstrip off the trailing newline after writing the buffer. This even works with\r\n'readonly' files.\r\n    let g:PreserveNoEOL_Function = function('PreserveNoEOL#Python#Preserve')\r\nWhen Vim is compiled with +perl support, a Perl function is used to strip\r\noff the trailing newline after writing the buffer. This even works with\r\n'readonly' files.\r\n    let g:PreserveNoEOL_Function = function('PreserveNoEOL#Perl#Preserve')\r\nWithout Perl support, an similar Perl script is invoked as an external\r\nexecutable. This still requires an installed Perl interpreter, but no Perl\r\nsupport built into Vim.\r\n    let g:PreserveNoEOL_Function = function('PreserveNoEOL#Executable#Preserve')\r\nAs a fallback, a pure Vimscript implementation can be used. This temporarily\r\nsets the 'binary' option on each buffer write and messes with the line\r\nendings.\r\n    let g:PreserveNoEOL_Function = function('PreserveNoEOL#Internal#Preserve')\r\n\r\nThe processing can be delegated to an external executable named \"noeol\". It is\r\nlocated in 'runtimepath' or somewhere on PATH. On Windows, this Perl script is\r\ninvoked through the Perl interpreter. You can use a different path or\r\nexecutable via:\r\n    let g:PreserveNoEOL_Command = 'path\/to\/executable'\r\n\r\nINTEGRATION\r\nYou can influence the write behavior via the buffer-local variable\r\nb:PreserveNoEOL. When this evaluates to true, a 'noeol' setting will be\r\npreserved on writes.\r\nYou can use this variable in autocmds, filetype plugins or a local vimrc to\r\nchange the behavior for certain file types or files in a particular location.\r\n\r\nIf you want to indicate (e.g. in your 'statusline') that the current file's\r\nmissing EOL will be preserved, you can use the PreserveNoEOL#Info#IsPreserve()\r\nfunction, which returns 1 if the plugin will preserve it; 0 otherwise.","first_name":"Ingo","6":"Ingo","last_name":"Karkat","7":"Karkat","releases":[{"0":"4550","vim_version":"7.0","1":"7.0","script_version":"1.01","2":"1.01","version_comment":"In the Python strategy, support traditional Mac (CR) line endings, too.","3":"In the Python strategy, support traditional Mac (CR) line endings, too.","package":"PreserveNoEOL-1.01.vmb.gz","4":"PreserveNoEOL-1.01.vmb.gz","src_id":"19942","5":"19942","creation_date":"1366980807","6":"1366980807"},{"0":"4550","vim_version":"7.0","1":"7.0","script_version":"1.00","2":"1.00","version_comment":"Initial upload","3":"Initial upload","package":"PreserveNoEOL-1.00.vmb.gz","4":"PreserveNoEOL-1.00.vmb.gz","src_id":"19941","5":"19941","creation_date":"1366976236","6":"1366976236"}]},"4549":{"script_id":"4549","0":"4549","script_name":"svn_line_history.vim","1":"svn_line_history.vim","script_type":"utility","2":"utility","summary":"display svn blame (history) for selected line: commit number, message and diff","3":"display svn blame (history) for selected line: commit number, message and diff","description":"This plugin defines single command SvnLineHistory. When called this command will show some usefull data in a new buffer: \r\n    1. last commit number N in which the line under the cursor was changed. \r\n    2. last commit author and log message.\r\n    3. last commit diff \r\n\r\nThe current buffer file should be under Svn version control, and you need to have access to the repository. The command execution might take some time, because we need to send blame, log and diff requests to the repository server. The plugin will work even if the file has local changes which do not affect the current line.","4":"This plugin defines single command SvnLineHistory. When called this command will show some usefull data in a new buffer: \r\n    1. last commit number N in which the line under the cursor was changed. \r\n    2. last commit author and log message.\r\n    3. last commit diff \r\n\r\nThe current buffer file should be under Svn version control, and you need to have access to the repository. The command execution might take some time, because we need to send blame, log and diff requests to the repository server. The plugin will work even if the file has local changes which do not affect the current line.","install_details":"extract bundle in ~\/.vim directory","5":"extract bundle in ~\/.vim directory","first_name":"Dmitry","6":"Dmitry","last_name":"Ignatovich","7":"Ignatovich","releases":[{"0":"4549","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"svn_line_history.zip","4":"svn_line_history.zip","src_id":"19936","5":"19936","creation_date":"1366927839","6":"1366927839"}]},"4548":{"script_id":"4548","0":"4548","script_name":"vim-vagrant","1":"vim-vagrant","script_type":"utility","2":"utility","summary":"basic vim\/vagrant integration","3":"basic vim\/vagrant integration","description":"This plugin adds a :Vagrant command that runs vagrant, with tab completion of subcommands. It also sets up Vagrantfiles to be highlighted as Ruby.","4":"This plugin adds a :Vagrant command that runs vagrant, with tab completion of subcommands. It also sets up Vagrantfiles to be highlighted as Ruby.","install_details":"","5":"","first_name":"Mark","6":"Mark","last_name":"Cornick","7":"Cornick","releases":[{"0":"4548","vim_version":"7.0","1":"7.0","script_version":"1.1.2","2":"1.1.2","version_comment":"update with commands in Vagrant 1.7","3":"update with commands in Vagrant 1.7","package":"vim-vagrant-1.1.2.tar.gz","4":"vim-vagrant-1.1.2.tar.gz","src_id":"22683","5":"22683","creation_date":"1418238259","6":"1418238259"},{"0":"4548","vim_version":"7.3","1":"7.3","script_version":"1.1.1","2":"1.1.1","version_comment":"* move ftplugin to ftdetect","3":"* move ftplugin to ftdetect","package":"vim-vagrant-1.1.1.tar.gz","4":"vim-vagrant-1.1.1.tar.gz","src_id":"20311","5":"20311","creation_date":"1370580972","6":"1370580972"},{"0":"4548","vim_version":"7.3","1":"7.3","script_version":"1.1.0","2":"1.1.0","version_comment":"* don't load plugin if vagrant isn't installed\r\n* add MIT license\r\n","3":"* don't load plugin if vagrant isn't installed\r\n* add MIT license\r\n","package":"vim-vagrant-1.1.0.tar.gz","4":"vim-vagrant-1.1.0.tar.gz","src_id":"20191","5":"20191","creation_date":"1369162347","6":"1369162347"}]},"4547":{"script_id":"4547","0":"4547","script_name":"ruby-syntaxchecker","1":"ruby-syntaxchecker","script_type":"ftplugin","2":"ftplugin","summary":"Ruby syntax checker, display error and warnings in a quickfix split","3":"Ruby syntax checker, display error and warnings in a quickfix split","description":"ruby-syntaxchecker.vim\r\n\r\nhttps:\/\/github.com\/vantares\/ruby-syntaxchecker.vim\r\n\r\nruby syntax checker, toggles a quickfix window with the error list\r\n\r\ndescription\r\nYou need to install ruby It\\\\\\'s a simple program that just checks if your ruby code have any syntax warning or error.\r\n\r\nPressing F4 will run it using the \\\\\\\"quickfix\\\\\\\" feature. This way you can \\\\\\\"navigate\\\\\\\" through errors using :cn and other standard commands.","4":"ruby-syntaxchecker.vim\r\n\r\nhttps:\/\/github.com\/vantares\/ruby-syntaxchecker.vim\r\n\r\nruby syntax checker, toggles a quickfix window with the error list\r\n\r\ndescription\r\nYou need to install ruby It\\\\\\'s a simple program that just checks if your ruby code have any syntax warning or error.\r\n\r\nPressing F4 will run it using the \\\\\\\"quickfix\\\\\\\" feature. This way you can \\\\\\\"navigate\\\\\\\" through errors using :cn and other standard commands.","install_details":"install details\r\njust put the file in your ~\/.vim\/ftplugin\/ruby directory (if that doesn\\\\\\'t exist, create it)\r\n\r\nThe default mapping is F4, you can change it putting let g:ruby_syntaxcheck_map=\\\\\\'whatever\\\\\\' in your vimrc","5":"install details\r\njust put the file in your ~\/.vim\/ftplugin\/ruby directory (if that doesn\\\\\\'t exist, create it)\r\n\r\nThe default mapping is F4, you can change it putting let g:ruby_syntaxcheck_map=\\\\\\'whatever\\\\\\' in your vimrc","first_name":"Juan Carlos","6":"Juan Carlos","last_name":"Alvarez","7":"Alvarez","releases":[{"0":"4547","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"ruby-syntaxchecker.vim.zip","4":"ruby-syntaxchecker.vim.zip","src_id":"19934","5":"19934","creation_date":"1366900664","6":"1366900664"}]},"4546":{"script_id":"4546","0":"4546","script_name":"vterm","1":"vterm","script_type":"utility","2":"utility","summary":"A terminal emulator inside vim without extra dependencies","3":"A terminal emulator inside vim without extra dependencies","description":"The goal of vterm is to provide a clone of unix terminal inside vim right out of the box without any dependencies.\r\n\r\nTo start using it, just run :VTermStart\r\n\r\nPlease read the help file for more details and configurations or visit the github repo\r\nhttps:\/\/github.com\/sollidsnake\/vterm","4":"The goal of vterm is to provide a clone of unix terminal inside vim right out of the box without any dependencies.\r\n\r\nTo start using it, just run :VTermStart\r\n\r\nPlease read the help file for more details and configurations or visit the github repo\r\nhttps:\/\/github.com\/sollidsnake\/vterm","install_details":"Install using you favorite vim package manager or extract the files in your ~\/.vim folder.\r\nYou should run \":helptags ~\/.vim\/doc\" to update the help tags if you choose the second option.","5":"Install using you favorite vim package manager or extract the files in your ~\/.vim folder.\r\nYou should run \":helptags ~\/.vim\/doc\" to update the help tags if you choose the second option.","first_name":"Jesse","6":"Jesse","last_name":"Nazario","7":"Nazario","releases":[{"0":"4546","vim_version":"7.0","1":"7.0","script_version":"1.11","2":"1.11","version_comment":"- hostname fixed for zsh shells\r\n- make persistent insert work with previous and next commands in history\r\n- The nomodifiable option was causing some conflicts. Temporarily(?) removed.\r\n- minor fixes in start function\r\n- clear command will just scroll the screen instead of deleting everything","3":"- hostname fixed for zsh shells\r\n- make persistent insert work with previous and next commands in history\r\n- The nomodifiable option was causing some conflicts. Temporarily(?) removed.\r\n- minor fixes in start function\r\n- clear command will just scroll the screen instead of deleting everything","package":"vterm-1.11.tar.gz","4":"vterm-1.11.tar.gz","src_id":"19969","5":"19969","creation_date":"1367203819","6":"1367203819"},{"0":"4546","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"vterm-1.0.tar.gz","4":"vterm-1.0.tar.gz","src_id":"19928","5":"19928","creation_date":"1366833189","6":"1366833189"}]},"4545":{"script_id":"4545","0":"4545","script_name":"MPage","1":"MPage","script_type":"utility","2":"utility","summary":"Shows synchronized pages of a file in multiple windows","3":"Shows synchronized pages of a file in multiple windows","description":"MPage shows a file in multiple windows, with each sequential window showing sequential lines of text, rather like a book.\r\n\r\nUsage:\r\n\r\n   :MPage [splits]\r\n  :[splits]MPage\r\n\r\nwill split a window into \"splits\" pages.  Subsequently, a \r\n\r\n  :MPage\r\n\r\nwill turn multi-paging off for all windows holding the current window's buffer (this doesn't \"quit\" the windows, it merely turns off synchronization).\r\n\r\nA\r\n\r\n  :MPage!\r\n\r\nwill turn off multipaging for all windows in the current tab.\r\n\r\n:MPT  will toggle the current window's participation in multipaging.\r\n:MPN will go to the next mpage-controlled window        (accepts a count, too)\r\n:MPP will go to the previous mpage-controlled window  (accepts a count, too)\r\n\r\nAs always with my plugins, the latest version, albeit experimental, is available at my website:\r\n\r\n  http:\/\/www.drchip.org\/astronaut\/vim\/index.html#MPAGE\r\n\r\n\r\n","4":"MPage shows a file in multiple windows, with each sequential window showing sequential lines of text, rather like a book.\r\n\r\nUsage:\r\n\r\n   :MPage [splits]\r\n  :[splits]MPage\r\n\r\nwill split a window into \"splits\" pages.  Subsequently, a \r\n\r\n  :MPage\r\n\r\nwill turn multi-paging off for all windows holding the current window's buffer (this doesn't \"quit\" the windows, it merely turns off synchronization).\r\n\r\nA\r\n\r\n  :MPage!\r\n\r\nwill turn off multipaging for all windows in the current tab.\r\n\r\n:MPT  will toggle the current window's participation in multipaging.\r\n:MPN will go to the next mpage-controlled window        (accepts a count, too)\r\n:MPP will go to the previous mpage-controlled window  (accepts a count, too)\r\n\r\nAs always with my plugins, the latest version, albeit experimental, is available at my website:\r\n\r\n  http:\/\/www.drchip.org\/astronaut\/vim\/index.html#MPAGE\r\n\r\n\r\n","install_details":"1. You'll need to have plugins enabled: in your home directory, have at least the following two lines in your .vimrc file:\r\n   set nocp\r\n   filetype plugin on\r\n\r\n2. Using vim 7.1 or later:\r\n  vim mpage.vba.gz\r\n   :so %\r\n   :q \r\n","5":"1. You'll need to have plugins enabled: in your home directory, have at least the following two lines in your .vimrc file:\r\n   set nocp\r\n   filetype plugin on\r\n\r\n2. Using vim 7.1 or later:\r\n  vim mpage.vba.gz\r\n   :so %\r\n   :q \r\n","first_name":"Charles","6":"Charles","last_name":"Campbell","7":"Campbell","releases":[{"0":"4545","vim_version":"7.3","1":"7.3","script_version":"1","2":"1","version_comment":"Initial upload","3":"Initial upload","package":"mpage.vba.gz","4":"mpage.vba.gz","src_id":"19927","5":"19927","creation_date":"1366832643","6":"1366832643"}]},"4544":{"script_id":"4544","0":"4544","script_name":"vim-startify","1":"vim-startify","script_type":"utility","2":"utility","summary":"A fancy start screen for Vim.","3":"A fancy start screen for Vim.","description":"\r\n\r\nNOTE: Get the latest updates via github: https:\/\/github.com\/mhinz\/vim-startify\r\n\r\nIf you like this plugin, star it on github! \r\n\r\nScreenshot: https:\/\/github.com\/mhinz\/vim-startify\/raw\/master\/startify.png\r\n\r\n\r\n\r\nSTARTIFY\r\n\r\nStartify basically provides two things:\r\n\r\n1)  If you start Vim without giving any filenames to it (or pipe stuff to it so\r\n   it reads from STDIN), startify will show a small but pretty start screen\r\n   which shows recently used files and sessions by default.\r\n\r\n   Additionally, you can define bookmarks, thus entries for files that always\r\n   should be available in the start screen.\r\n\r\n   You can either navigate to a certain menu entry or you just key in whatever\r\n   is written between the square brackets on that line.\r\n\r\n2)  It eases handling of loading and saving sessions by only working with a\r\n   certain directory. Two commands are used for convenience:\r\n\r\n      :SLoad    load a session\r\n      :SSave    save a session\r\n\r\nThe default settings are pretty sane, so it should work without any\r\nconfiguration.\r\n","4":"\r\n\r\nNOTE: Get the latest updates via github: https:\/\/github.com\/mhinz\/vim-startify\r\n\r\nIf you like this plugin, star it on github! \r\n\r\nScreenshot: https:\/\/github.com\/mhinz\/vim-startify\/raw\/master\/startify.png\r\n\r\n\r\n\r\nSTARTIFY\r\n\r\nStartify basically provides two things:\r\n\r\n1)  If you start Vim without giving any filenames to it (or pipe stuff to it so\r\n   it reads from STDIN), startify will show a small but pretty start screen\r\n   which shows recently used files and sessions by default.\r\n\r\n   Additionally, you can define bookmarks, thus entries for files that always\r\n   should be available in the start screen.\r\n\r\n   You can either navigate to a certain menu entry or you just key in whatever\r\n   is written between the square brackets on that line.\r\n\r\n2)  It eases handling of loading and saving sessions by only working with a\r\n   certain directory. Two commands are used for convenience:\r\n\r\n      :SLoad    load a session\r\n      :SSave    save a session\r\n\r\nThe default settings are pretty sane, so it should work without any\r\nconfiguration.\r\n","install_details":"\r\nIf you have no preferred installation method, I suggest using tpope's pathogen:\r\n\r\n1. git clone https:\/\/github.com\/tpope\/vim-pathogen ~\/.vim\/bundle\/vim-pathogen\r\n1. mkdir -p ~\/.vim\/autoload && cd ~\/.vim\/autoload\r\n1. ln -s ..\/bundle\/vim-pathogen\/autoload\/pathogen.vim\r\n\r\nAfterwards installing vim-startify is as easy as pie:\r\n\r\n2. git clone https:\/\/github.com\/mhinz\/vim-startify ~\/.vim\/bundle\/vim-startify\r\n2. start Vim\r\n2. :Helptags\r\n2. :h startify\r\n","5":"\r\nIf you have no preferred installation method, I suggest using tpope's pathogen:\r\n\r\n1. git clone https:\/\/github.com\/tpope\/vim-pathogen ~\/.vim\/bundle\/vim-pathogen\r\n1. mkdir -p ~\/.vim\/autoload && cd ~\/.vim\/autoload\r\n1. ln -s ..\/bundle\/vim-pathogen\/autoload\/pathogen.vim\r\n\r\nAfterwards installing vim-startify is as easy as pie:\r\n\r\n2. git clone https:\/\/github.com\/mhinz\/vim-startify ~\/.vim\/bundle\/vim-startify\r\n2. start Vim\r\n2. :Helptags\r\n2. :h startify\r\n","first_name":"Marco","6":"Marco","last_name":"Hinz","7":"Hinz","releases":[{"0":"4544","vim_version":"7.0","1":"7.0","script_version":"1.7","2":"1.7","version_comment":"- new lists handling\r\n- improved buffer handling\r\n- improved plugin compatibility\r\n- added custom header\r\n- improved docs\r\n- lots of bugfixes\r\n- MIT licenset","3":"- new lists handling\r\n- improved buffer handling\r\n- improved plugin compatibility\r\n- added custom header\r\n- improved docs\r\n- lots of bugfixes\r\n- MIT licenset","package":"vim-startify-1.7.tar.gz","4":"vim-startify-1.7.tar.gz","src_id":"20600","5":"20600","creation_date":"1375651890","6":"1375651890"},{"0":"4544","vim_version":"7.0","1":"7.0","script_version":"1.6","2":"1.6","version_comment":"- proper handling of files containing spaces everywhere\r\n- (command argument completion for files with spaces)\r\n- commands remember the last used session now\r\n- less magic when opening sessions\r\n- command hardening\r\n- lots of function reordering","3":"- proper handling of files containing spaces everywhere\r\n- (command argument completion for files with spaces)\r\n- commands remember the last used session now\r\n- less magic when opening sessions\r\n- command hardening\r\n- lots of function reordering","package":"vim-startify-1.6.tar.gz","4":"vim-startify-1.6.tar.gz","src_id":"20231","5":"20231","creation_date":"1369904133","6":"1369904133"},{"0":"4544","vim_version":"7.0","1":"7.0","script_version":"1.5","2":"1.5","version_comment":"improved symlink handling, add set_mark() and open_buffers(), split mode (key 's', 'v' or '<space>' on some entries and commit via '<cr>'), add CONTRIBUTING file, improved several 'if' checks, added :SDelete, exclude bookmarked files from MRU list, 'e' -> empty buffer (normal mode); 'i' -> empty buffer (insert mode), new option: g:startify_custom_indices, removed option: g:startify_unlisted_buffer","3":"improved symlink handling, add set_mark() and open_buffers(), split mode (key 's', 'v' or '<space>' on some entries and commit via '<cr>'), add CONTRIBUTING file, improved several 'if' checks, added :SDelete, exclude bookmarked files from MRU list, 'e' -> empty buffer (normal mode); 'i' -> empty buffer (insert mode), new option: g:startify_custom_indices, removed option: g:startify_unlisted_buffer","package":"vim-startify-1.5.tar.gz","4":"vim-startify-1.5.tar.gz","src_id":"20071","5":"20071","creation_date":"1368026877","6":"1368026877"},{"0":"4544","vim_version":"7.0","1":"7.0","script_version":"1.3","2":"1.3","version_comment":"change working directory, more intelligent 'q', mouse support, create session dir on demand, configurable empty buffer key, bugfixes","3":"change working directory, more intelligent 'q', mouse support, create session dir on demand, configurable empty buffer key, bugfixes","package":"vim-startify-1.3.tar.gz","4":"vim-startify-1.3.tar.gz","src_id":"19951","5":"19951","creation_date":"1367081445","6":"1367081445"},{"0":"4544","vim_version":"7.0","1":"7.0","script_version":"1.2","2":"1.2","version_comment":"Windows support, added :Startify command, FAQ section in the docs, tons of bugfixes","3":"Windows support, added :Startify command, FAQ section in the docs, tons of bugfixes","package":"vim-startify-1.2.tar.gz","4":"vim-startify-1.2.tar.gz","src_id":"19943","5":"19943","creation_date":"1366984326","6":"1366984326"},{"0":"4544","vim_version":"7.0","1":"7.0","script_version":"1.1","2":"1.1","version_comment":"make commands take arguments + tab completion; bugfixes","3":"make commands take arguments + tab completion; bugfixes","package":"vim-startify-1.1.tar.gz","4":"vim-startify-1.1.tar.gz","src_id":"19924","5":"19924","creation_date":"1366813900","6":"1366813900"},{"0":"4544","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"vim-startify-1.0.tar.gz","4":"vim-startify-1.0.tar.gz","src_id":"19923","5":"19923","creation_date":"1366796250","6":"1366796250"}]},"4543":{"script_id":"4543","0":"4543","script_name":"eval.vim","1":"eval.vim","script_type":"utility","2":"utility","summary":"Evaluate line or region with ^C","3":"Evaluate line or region with ^C","description":"https:\/\/github.com\/amiorin\/vim-eval","4":"https:\/\/github.com\/amiorin\/vim-eval","install_details":"","5":"","first_name":"Alberto","6":"Alberto","last_name":"Miorin","7":"Miorin","releases":[{"0":"4543","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"vim-eval.zip","4":"vim-eval.zip","src_id":"19915","5":"19915","creation_date":"1366743789","6":"1366743789"}]},"4542":{"script_id":"4542","0":"4542","script_name":"ctrlp-z","1":"ctrlp-z","script_type":"utility","2":"utility","summary":"fasd interface with ctrlp.vim","3":"fasd interface with ctrlp.vim","description":"https:\/\/github.com\/amiorin\/ctrlp-z","4":"https:\/\/github.com\/amiorin\/ctrlp-z","install_details":"","5":"","first_name":"Alberto","6":"Alberto","last_name":"Miorin","7":"Miorin","releases":[{"0":"4542","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"ctrlp-z.zip","4":"ctrlp-z.zip","src_id":"19914","5":"19914","creation_date":"1366743649","6":"1366743649"}]},"4541":{"script_id":"4541","0":"4541","script_name":"fenced-code-blocks","1":"fenced-code-blocks","script_type":"utility","2":"utility","summary":"Edit fenced code blocks inside a GitHub Flavor Markdown in a better way","3":"Edit fenced code blocks inside a GitHub Flavor Markdown in a better way","description":"https:\/\/github.com\/amiorin\/vim-fenced-code-blocks","4":"https:\/\/github.com\/amiorin\/vim-fenced-code-blocks","install_details":"","5":"","first_name":"Alberto","6":"Alberto","last_name":"Miorin","7":"Miorin","releases":[{"0":"4541","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"vim-fenced-code-blocks.zip","4":"vim-fenced-code-blocks.zip","src_id":"19913","5":"19913","creation_date":"1366743563","6":"1366743563"}]},"4540":{"script_id":"4540","0":"4540","script_name":"project.vim","1":"project.vim","script_type":"utility","2":"utility","summary":"lcd to the root of the project everytime you BufEnter a file inside a project","3":"lcd to the root of the project everytime you BufEnter a file inside a project","description":"https:\/\/github.com\/amiorin\/vim-project","4":"https:\/\/github.com\/amiorin\/vim-project","install_details":"","5":"","first_name":"Alberto","6":"Alberto","last_name":"Miorin","7":"Miorin","releases":[{"0":"4540","vim_version":"7.0","1":"7.0","script_version":"1.4","2":"1.4","version_comment":"windows support added","3":"windows support added","package":"vim-project.zip","4":"vim-project.zip","src_id":"20157","5":"20157","creation_date":"1368945073","6":"1368945073"},{"0":"4540","vim_version":"7.0","1":"7.0","script_version":"1.3","2":"1.3","version_comment":"New command Welcome and bugfix order of projects not respected.","3":"New command Welcome and bugfix order of projects not respected.","package":"vim-project.zip","4":"vim-project.zip","src_id":"19984","5":"19984","creation_date":"1367351249","6":"1367351249"},{"0":"4540","vim_version":"7.0","1":"7.0","script_version":"1.2","2":"1.2","version_comment":"Callback command added","3":"Callback command added","package":"vim-project.zip","4":"vim-project.zip","src_id":"19949","5":"19949","creation_date":"1367056805","6":"1367056805"},{"0":"4540","vim_version":"7.0","1":"7.0","script_version":"1.1","2":"1.1","version_comment":"Bugfix ProjectPath","3":"Bugfix ProjectPath","package":"vim-project.zip","4":"vim-project.zip","src_id":"19919","5":"19919","creation_date":"1366764088","6":"1366764088"},{"0":"4540","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"vim-project.zip","4":"vim-project.zip","src_id":"19912","5":"19912","creation_date":"1366743408","6":"1366743408"}]},"4539":{"script_id":"4539","0":"4539","script_name":"bookmarks.vim","1":"bookmarks.vim","script_type":"utility","2":"utility","summary":"Global markers like bookmarks","3":"Global markers like bookmarks","description":"https:\/\/github.com\/amiorin\/vim-bookmarks","4":"https:\/\/github.com\/amiorin\/vim-bookmarks","install_details":"","5":"","first_name":"Alberto","6":"Alberto","last_name":"Miorin","7":"Miorin","releases":[{"0":"4539","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"vim-bookmarks.zip","4":"vim-bookmarks.zip","src_id":"19911","5":"19911","creation_date":"1366743236","6":"1366743236"}]},"4538":{"script_id":"4538","0":"4538","script_name":"vim-gitmodeline","1":"vim-gitmodeline","script_type":"ftplugin","2":"ftplugin","summary":"Store modelines in git config","3":"Store modelines in git config","description":"This is a vim plugin which reads modelines from the git config and sets it to the current buffer.\r\nTo set a modeline in the git config you can do it with the following command:\r\n\r\n  git config --add vim.modeline \"tabstop=8 shiftwidth=8 noexpandtab cindent\"\r\n\r\nThe allowed modelines are defined in a variable and can be overwritten and\r\nextended by setting the following in your .vimrc:\r\n\r\n  let g:git_modeline_allowed_items = [\r\n              \\ \"textwidth\",   \"tw\",\r\n              \\ \"softtabstop\", \"sts\",\r\n              \\ \"tabstop\",     \"ts\",\r\n              \\ \"shiftwidth\",  \"sw\",\r\n              \\ \"expandtab\",   \"et\",   \"noexpandtab\", \"noet\",\r\n              \\ \"filetype\",    \"ft\",\r\n              \\ \"foldmethod\",  \"fdm\",\r\n              \\ \"readonly\",    \"ro\",   \"noreadonly\", \"noro\",\r\n              \\ \"rightleft\",   \"rl\",   \"norightleft\", \"norl\",\r\n              \\ \"cindent\",     \"cin\",  \"nocindent\", \"nocin\",\r\n              \\ \"smartindent\", \"si\",   \"nosmartindent\", \"nosi\",\r\n              \\ \"autoindent\",  \"ai\",   \"noautoindent\", \"noai\",\r\n              \\ \"spell\",\r\n              \\ \"spelllang\"\r\n              \\ ]\r\n\r\nThe git repository can be found here: https:\/\/github.com\/cryptomilk\/git-modeline.vim\/","4":"This is a vim plugin which reads modelines from the git config and sets it to the current buffer.\r\nTo set a modeline in the git config you can do it with the following command:\r\n\r\n  git config --add vim.modeline \"tabstop=8 shiftwidth=8 noexpandtab cindent\"\r\n\r\nThe allowed modelines are defined in a variable and can be overwritten and\r\nextended by setting the following in your .vimrc:\r\n\r\n  let g:git_modeline_allowed_items = [\r\n              \\ \"textwidth\",   \"tw\",\r\n              \\ \"softtabstop\", \"sts\",\r\n              \\ \"tabstop\",     \"ts\",\r\n              \\ \"shiftwidth\",  \"sw\",\r\n              \\ \"expandtab\",   \"et\",   \"noexpandtab\", \"noet\",\r\n              \\ \"filetype\",    \"ft\",\r\n              \\ \"foldmethod\",  \"fdm\",\r\n              \\ \"readonly\",    \"ro\",   \"noreadonly\", \"noro\",\r\n              \\ \"rightleft\",   \"rl\",   \"norightleft\", \"norl\",\r\n              \\ \"cindent\",     \"cin\",  \"nocindent\", \"nocin\",\r\n              \\ \"smartindent\", \"si\",   \"nosmartindent\", \"nosi\",\r\n              \\ \"autoindent\",  \"ai\",   \"noautoindent\", \"noai\",\r\n              \\ \"spell\",\r\n              \\ \"spelllang\"\r\n              \\ ]\r\n\r\nThe git repository can be found here: https:\/\/github.com\/cryptomilk\/git-modeline.vim\/","install_details":"Use a bundle installer like dein.","5":"Use a bundle installer like dein.","first_name":"Andreas","6":"Andreas","last_name":"Schneider","7":"Schneider","releases":[{"0":"4538","vim_version":"7.3","1":"7.3","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"git_modeline.vim","4":"git_modeline.vim","src_id":"19894","5":"19894","creation_date":"1366648781","6":"1366648781"}]},"4537":{"script_id":"4537","0":"4537","script_name":"keymap.vim","1":"keymap.vim","script_type":"syntax","2":"syntax","summary":"Highligting for Linux console keyboard map files","3":"Highligting for Linux console keyboard map files","description":"Highlighting for Linux console keyboard map files, as described in keymaps manual page.\r\n\r\nNote that most users do not need to create or edit Linux keyboard map files and so will not need the syntax highlighted either.\r\n\r\nNo support yet for line continuation with backslash (which is supported by loadkeys command in the keymap file).\r\n\r\nBoth string and character escapes are included (highlighted) in all strings (double-quoted) and characters (single-quoted) appearing in the file.\r\n\r\nThere is no associated 'keymap' filetype, nor any auto-detection for it, so to see the highlighting you will have to use the:\r\n       :set syntax=keymap\r\ncommand manually (or in a modline if you wish).\r\n\r\nThe highlighting for the number prefix (0 for octal, 0x for hexadecimal, U+ for unicode characters), is currently linked to the Vim  'Special' highlighting group (used for example for backslash escapes in string literals). If that looks too distracting with your preferred color scheme, it can be disabled with:\r\n       :let g:keymap_number_prefix = 0\r\nin your ~\/.vimrc (or equivalent) file.\r\n\r\nAll key names (symbolic constants) that are highlighted are taken from the output of \r\n      dumpkeys --long-info\r\nfrom my Slackware 14.0 32-bit machine. It is possible your machine has a slightly different set of key names, you are welcome to report them to the script author.","4":"Highlighting for Linux console keyboard map files, as described in keymaps manual page.\r\n\r\nNote that most users do not need to create or edit Linux keyboard map files and so will not need the syntax highlighted either.\r\n\r\nNo support yet for line continuation with backslash (which is supported by loadkeys command in the keymap file).\r\n\r\nBoth string and character escapes are included (highlighted) in all strings (double-quoted) and characters (single-quoted) appearing in the file.\r\n\r\nThere is no associated 'keymap' filetype, nor any auto-detection for it, so to see the highlighting you will have to use the:\r\n       :set syntax=keymap\r\ncommand manually (or in a modline if you wish).\r\n\r\nThe highlighting for the number prefix (0 for octal, 0x for hexadecimal, U+ for unicode characters), is currently linked to the Vim  'Special' highlighting group (used for example for backslash escapes in string literals). If that looks too distracting with your preferred color scheme, it can be disabled with:\r\n       :let g:keymap_number_prefix = 0\r\nin your ~\/.vimrc (or equivalent) file.\r\n\r\nAll key names (symbolic constants) that are highlighted are taken from the output of \r\n      dumpkeys --long-info\r\nfrom my Slackware 14.0 32-bit machine. It is possible your machine has a slightly different set of key names, you are welcome to report them to the script author.","install_details":"Download keymap.vim syntax file to ~\/.vim\/syntax\/ directory or equivalent.","5":"Download keymap.vim syntax file to ~\/.vim\/syntax\/ directory or equivalent.","first_name":"Timothy","6":"Timothy","last_name":"Madden","7":"Madden","releases":[{"0":"4537","vim_version":"6.0","1":"6.0","script_version":"0.9","2":"0.9","version_comment":"Initial upload","3":"Initial upload","package":"keymap.vim","4":"keymap.vim","src_id":"19891","5":"19891","creation_date":"1366596314","6":"1366596314"}]},"4536":{"script_id":"4536","0":"4536","script_name":"nextval","1":"nextval","script_type":"utility","2":"utility","summary":"Inc-\/decrement the current value (bool, int, numeric, hex) with one keystroke","3":"Inc-\/decrement the current value (bool, int, numeric, hex) with one keystroke","description":"During editing position your cursor on a boolean, integer, number or hex value and press + or - in normal mode (esc).\r\n\r\nExamples:\r\n\r\n* switch=false # +\/- -> true\r\n* switch=TRUE  # +\/- -> FALSE\r\n* int=1 # - -> 0 -1 -2\r\n* num=4.98 # + -> 4.99 5.00\r\n* num=.4 # + -> .5\r\n* hex=0x19 # + -> 0x1a\r\n* hex=ab # + -> ac\r\n* hex=1B07 # -> 1B08\r\n* hex=#9 # + -> a\r\n\r\nNew variants:\r\n\r\n* test5 # int surrounded\r\n* test123test # int surrounded\r\n* True # boolean\r\n* 0xf9 # hex\r\n* 5A3 # tex\r\n* ’ # xml\/xhtml\r\n* \\x19 # unix, bash\r\n* FFh or 05A3H # intel assembly\r\n* #9 # modulo2\r\n* 16#5A3# # ada\/vhdl\r\n* 16r5A3 # smalltalk\/algol\r\n* 16#5A7 # postscript\/bash\r\n* \\u0019 \\U00000019 # bash\r\n* #16r4a # common lisp\r\n* &H5A3 or &5a3 # several basic\r\n* 0h5A3 ti series\r\n* U+20AD # unicode\r\n* S=U+9 # integer\r\n* $5A3 # assembly\/basic\r\n* H'ABCD' # microchip\r\n* x\"5A3\" # vhdl\r\n* 8'hFF # verilog\r\n* #x4a # common lisp\r\n* X'5A3' # ibm mainframe\r\n\r\nPlease provide feedback (Wiki\/Mail) - especially if you vote \"Unfulfilling\".","4":"During editing position your cursor on a boolean, integer, number or hex value and press + or - in normal mode (esc).\r\n\r\nExamples:\r\n\r\n* switch=false # +\/- -> true\r\n* switch=TRUE  # +\/- -> FALSE\r\n* int=1 # - -> 0 -1 -2\r\n* num=4.98 # + -> 4.99 5.00\r\n* num=.4 # + -> .5\r\n* hex=0x19 # + -> 0x1a\r\n* hex=ab # + -> ac\r\n* hex=1B07 # -> 1B08\r\n* hex=#9 # + -> a\r\n\r\nNew variants:\r\n\r\n* test5 # int surrounded\r\n* test123test # int surrounded\r\n* True # boolean\r\n* 0xf9 # hex\r\n* 5A3 # tex\r\n* ’ # xml\/xhtml\r\n* \\x19 # unix, bash\r\n* FFh or 05A3H # intel assembly\r\n* #9 # modulo2\r\n* 16#5A3# # ada\/vhdl\r\n* 16r5A3 # smalltalk\/algol\r\n* 16#5A7 # postscript\/bash\r\n* \\u0019 \\U00000019 # bash\r\n* #16r4a # common lisp\r\n* &H5A3 or &5a3 # several basic\r\n* 0h5A3 ti series\r\n* U+20AD # unicode\r\n* S=U+9 # integer\r\n* $5A3 # assembly\/basic\r\n* H'ABCD' # microchip\r\n* x\"5A3\" # vhdl\r\n* 8'hFF # verilog\r\n* #x4a # common lisp\r\n* X'5A3' # ibm mainframe\r\n\r\nPlease provide feedback (Wiki\/Mail) - especially if you vote \"Unfulfilling\".","install_details":"# example installation if you use pathogen:\r\nmkdir -p ~\/.vim\/bundle\/netxval\/plugin\r\ncp nextval.vim  ~\/.vim\/bundle\/netxval\/plugin\r\nvi .vimrc # if you want to modifiy the default keys (C-a\/C-x) and add e.g.:\r\nnmap <silent> <unique> + <Plug>nextvalInc\r\nnmap <silent> <unique> - <Plug>nextvalDec","5":"# example installation if you use pathogen:\r\nmkdir -p ~\/.vim\/bundle\/netxval\/plugin\r\ncp nextval.vim  ~\/.vim\/bundle\/netxval\/plugin\r\nvi .vimrc # if you want to modifiy the default keys (C-a\/C-x) and add e.g.:\r\nnmap <silent> <unique> + <Plug>nextvalInc\r\nnmap <silent> <unique> - <Plug>nextvalDec","first_name":"Michael","6":"Michael","last_name":"Arlt","7":"Arlt","releases":[{"0":"4536","vim_version":"7.0","1":"7.0","script_version":"1.11","2":"1.11","version_comment":"Bugfix for increment\/decrement in last empty line (thx to Serpent)","3":"Bugfix for increment\/decrement in last empty line (thx to Serpent)","package":"nextval.vim","4":"nextval.vim","src_id":"21028","5":"21028","creation_date":"1384200737","6":"1384200737"},{"0":"4536","vim_version":"7.0","1":"7.0","script_version":"1.1","2":"1.1","version_comment":"- Added boolen for python (True\/False)\r\n- Added integer surrounded by text\r\n- Added many hex-variants\r\n- Improved float\r\n- Bugfix: inc\/dec \"worked\" if you where near a value\r\n- Big thanx to serpent for code\/feedback\/ideas\r\n- Added expamples in source for simpler testing","3":"- Added boolen for python (True\/False)\r\n- Added integer surrounded by text\r\n- Added many hex-variants\r\n- Improved float\r\n- Bugfix: inc\/dec \"worked\" if you where near a value\r\n- Big thanx to serpent for code\/feedback\/ideas\r\n- Added expamples in source for simpler testing","package":"nextval.vim","4":"nextval.vim","src_id":"20920","5":"20920","creation_date":"1381730092","6":"1381730092"},{"0":"4536","vim_version":"7.0","1":"7.0","script_version":"1.02","2":"1.02","version_comment":"Set default keys to overwrite Vims internal cmd C-a (inc) and C-x (dec)  - thx to Serpent","3":"Set default keys to overwrite Vims internal cmd C-a (inc) and C-x (dec)  - thx to Serpent","package":"nextval.vim","4":"nextval.vim","src_id":"19917","5":"19917","creation_date":"1366749768","6":"1366749768"},{"0":"4536","vim_version":"7.0","1":"7.0","script_version":"1.01","2":"1.01","version_comment":"* Added standard check if already loaded\r\n* Uses <Plug> for automatic mapping (if not already defined)\r\n* Changed plugin calling (see usage)\r\n* Removed forgotten debug output (sorry)\r\n* Added buffer awareness","3":"* Added standard check if already loaded\r\n* Uses <Plug> for automatic mapping (if not already defined)\r\n* Changed plugin calling (see usage)\r\n* Removed forgotten debug output (sorry)\r\n* Added buffer awareness","package":"nextval.vim","4":"nextval.vim","src_id":"19895","5":"19895","creation_date":"1366649981","6":"1366649981"},{"0":"4536","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"nextval.vim","4":"nextval.vim","src_id":"19888","5":"19888","creation_date":"1366575577","6":"1366575577"}]},"4535":{"script_id":"4535","0":"4535","script_name":"vim-smartclose","1":"vim-smartclose","script_type":"utility","2":"utility","summary":"Close Vim windows in a smart way!","3":"Close Vim windows in a smart way!","description":"SmartClose is a wise closing utility. What does it mean? SmartClose plugin distinguishes two kinds of windows (the regular windows you use to work) and the auxiliary ones (a preview window, a NERDTree panel, a quickfix window, etc). Basically, the plugin allows you to close a window just with a single keystroke (<F10>). But if there are any auxiliary windows visible, it closes them first (in the LIFO order). It means, you don't have to leave the current (regular) window to close the auxiliary one. Just hit <F10> and you'll get it closed. If there are no auxiliary windows visible, <F10> will close the current window (and a tab if it would be the last window in the tab, or the editor itself, if it would be the last tab).\r\n\r\nIf you hit <F10> inside an auxiliary window, the window is closed immediately. And sometimes, the same behavior could be desired inside regular windows too, right? Even, if there are visible auxiliary ones, which will have the precedence, as said before. Therefore, the plugin provides you a configurable delay time. By default, during the first second after entering a regular window, hitting <F10> will close that window rather than any auxiliary ones.\r\n\r\nIn other words, the smart auxiliary windows closing feature is delayed about 1 sec. This way you can move into a regular window you want to close, press <F10> immediately, and close it even if there are open auxilary windows on the screen. The delay can be adjusted or even disabled.","4":"SmartClose is a wise closing utility. What does it mean? SmartClose plugin distinguishes two kinds of windows (the regular windows you use to work) and the auxiliary ones (a preview window, a NERDTree panel, a quickfix window, etc). Basically, the plugin allows you to close a window just with a single keystroke (<F10>). But if there are any auxiliary windows visible, it closes them first (in the LIFO order). It means, you don't have to leave the current (regular) window to close the auxiliary one. Just hit <F10> and you'll get it closed. If there are no auxiliary windows visible, <F10> will close the current window (and a tab if it would be the last window in the tab, or the editor itself, if it would be the last tab).\r\n\r\nIf you hit <F10> inside an auxiliary window, the window is closed immediately. And sometimes, the same behavior could be desired inside regular windows too, right? Even, if there are visible auxiliary ones, which will have the precedence, as said before. Therefore, the plugin provides you a configurable delay time. By default, during the first second after entering a regular window, hitting <F10> will close that window rather than any auxiliary ones.\r\n\r\nIn other words, the smart auxiliary windows closing feature is delayed about 1 sec. This way you can move into a regular window you want to close, press <F10> immediately, and close it even if there are open auxilary windows on the screen. The delay can be adjusted or even disabled.","install_details":"Place in ~\/.vim\/plugin\/smartclose.vim.\r\n\r\nThe most recent version can be always found on github: https:\/\/github.com\/szw\/vim-smartclose\r\n\r\nPlease, don't forget to star the repository if you like (and use) the plugin and rate the plugin here. This will let me know how many users it has and then how to proceed with further development :).","5":"Place in ~\/.vim\/plugin\/smartclose.vim.\r\n\r\nThe most recent version can be always found on github: https:\/\/github.com\/szw\/vim-smartclose\r\n\r\nPlease, don't forget to star the repository if you like (and use) the plugin and rate the plugin here. This will let me know how many users it has and then how to proceed with further development :).","first_name":"Szymon","6":"Szymon","last_name":"Wrozynski","7":"Wrozynski","releases":[{"0":"4535","vim_version":"7.0","1":"7.0","script_version":"0.0.2","2":"0.0.2","version_comment":"Initial upload","3":"Initial upload","package":"vim-smartclose-0.0.2.zip","4":"vim-smartclose-0.0.2.zip","src_id":"19884","5":"19884","creation_date":"1366540192","6":"1366540192"}]},"4534":{"script_id":"4534","0":"4534","script_name":"Deprecated","1":"Deprecated","script_type":"utility","2":"utility","summary":"Deprecated","3":"Deprecated","description":"Deprecated","4":"Deprecated","install_details":"","5":"","first_name":"fanhe","6":"fanhe","last_name":" ","7":" ","releases":[{"0":"4534","vim_version":"7.3","1":"7.3","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"dummy.tar.bz2","4":"dummy.tar.bz2","src_id":"19878","5":"19878","creation_date":"1366511781","6":"1366511781"}]},"4533":{"script_id":"4533","0":"4533","script_name":"milk.vim","1":"milk.vim","script_type":"color scheme","2":"color scheme","summary":"A light milky color scheme","3":"A light milky color scheme","description":"A light milky color scheme.","4":"A light milky color scheme.","install_details":"Put the file in your colors folder.","5":"Put the file in your colors folder.","first_name":"Mike","6":"Mike","last_name":"Z","7":"Z","releases":[{"0":"4533","vim_version":"7.0","1":"7.0","script_version":"1.1","2":"1.1","version_comment":"Brighter colors and underlines for search and incsearch.  Using background color tailored for my monitor.","3":"Brighter colors and underlines for search and incsearch.  Using background color tailored for my monitor.","package":"milk.vim","4":"milk.vim","src_id":"20367","5":"20367","creation_date":"1371522460","6":"1371522460"},{"0":"4533","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"milk.vim","4":"milk.vim","src_id":"19850","5":"19850","creation_date":"1366295231","6":"1366295231"}]},"4532":{"script_id":"4532","0":"4532","script_name":"TweetVim","1":"TweetVim","script_type":"utility","2":"utility","summary":"twitter client","3":"twitter client","description":"\r\n\r\n\r\ntweetvim is twitter client.\r\n===================\r\n\r\nLatest Version: https:\/\/github.com\/basyura\/TweetVim\r\n\r\nRequirement:\r\n------------------\r\n\r\n(*) optional\r\n\r\ncURL\r\nhttp:\/\/curl.haxx.se\/\r\n\r\ntwibill.vim\r\nhttps:\/\/github.com\/basyura\/twibill.vim\r\n\r\nopen-browser.vim\r\nhttps:\/\/github.com\/tyru\/open-browser.vim)\r\n\r\nunite-outline (*)\r\nhttps:\/\/github.com\/h1mesuke\/unite-outline\r\n\r\nbitly.vim (*)\r\nhttps:\/\/github.com\/basyura\/bitly.vim\r\n\r\nunite.vim (*)\r\nhttps:\/\/github.com\/Shougo\/unite.vim\r\n\r\nvimproc (*)\r\nhttps:\/\/github.com\/Shougo\/vimproc\r\n\r\nfavstar-vim (*)\r\nhttps:\/\/github.com\/mattn\/favstar-vim\r\n\r\n\r\nRelated plugin:\r\n--------------------\r\n\r\nneco-tweetvim\r\nhttps:\/\/github.com\/yomi322\/neco-tweetvim\r\n\r\n    plugin for neocomplcache.\r\n    you can complete screen name and hash tag in tweetvim_say buffer.\r\n\r\nunite-tweetvim\r\nhttps:\/\/github.com\/yomi322\/unite-tweetvim\r\n\r\n    plugin for unite.vim\r\n\r\nSTARTUP\r\n--------------\r\n\r\nThank you for using tweetvim.\r\nFirst, you must verify account.\r\n\r\n    :TweetVimHomeTimeline<CR>\r\n\r\nIf you are not verified, browser is launched by openbrowser.vim and display the number (pin).\r\nThen, input the number (pin) to the vim's command line.\r\n\r\n    Enter Twitter OAuth PIN: your number (pin)\r\n\r\ntweetvim save token to g:tweetvim_config_dir (default : ~\/.tweetvim).\r\n\r\nIf you want to use tweetvim conviniently, writes some key mappings in .vimrc\r\nlike this.\r\n\r\n    nnoremap <silent> s  :<C-u>TweetVimSay<CR>\r\n    nnoremap <silent> t  :TweetVimHomeTimeline<CR>\r\n    nnoremap <silent> tm :TweetVimMentions<CR>\r\n","4":"\r\n\r\n\r\ntweetvim is twitter client.\r\n===================\r\n\r\nLatest Version: https:\/\/github.com\/basyura\/TweetVim\r\n\r\nRequirement:\r\n------------------\r\n\r\n(*) optional\r\n\r\ncURL\r\nhttp:\/\/curl.haxx.se\/\r\n\r\ntwibill.vim\r\nhttps:\/\/github.com\/basyura\/twibill.vim\r\n\r\nopen-browser.vim\r\nhttps:\/\/github.com\/tyru\/open-browser.vim)\r\n\r\nunite-outline (*)\r\nhttps:\/\/github.com\/h1mesuke\/unite-outline\r\n\r\nbitly.vim (*)\r\nhttps:\/\/github.com\/basyura\/bitly.vim\r\n\r\nunite.vim (*)\r\nhttps:\/\/github.com\/Shougo\/unite.vim\r\n\r\nvimproc (*)\r\nhttps:\/\/github.com\/Shougo\/vimproc\r\n\r\nfavstar-vim (*)\r\nhttps:\/\/github.com\/mattn\/favstar-vim\r\n\r\n\r\nRelated plugin:\r\n--------------------\r\n\r\nneco-tweetvim\r\nhttps:\/\/github.com\/yomi322\/neco-tweetvim\r\n\r\n    plugin for neocomplcache.\r\n    you can complete screen name and hash tag in tweetvim_say buffer.\r\n\r\nunite-tweetvim\r\nhttps:\/\/github.com\/yomi322\/unite-tweetvim\r\n\r\n    plugin for unite.vim\r\n\r\nSTARTUP\r\n--------------\r\n\r\nThank you for using tweetvim.\r\nFirst, you must verify account.\r\n\r\n    :TweetVimHomeTimeline<CR>\r\n\r\nIf you are not verified, browser is launched by openbrowser.vim and display the number (pin).\r\nThen, input the number (pin) to the vim's command line.\r\n\r\n    Enter Twitter OAuth PIN: your number (pin)\r\n\r\ntweetvim save token to g:tweetvim_config_dir (default : ~\/.tweetvim).\r\n\r\nIf you want to use tweetvim conviniently, writes some key mappings in .vimrc\r\nlike this.\r\n\r\n    nnoremap <silent> s  :<C-u>TweetVimSay<CR>\r\n    nnoremap <silent> t  :TweetVimHomeTimeline<CR>\r\n    nnoremap <silent> tm :TweetVimMentions<CR>\r\n","install_details":"","5":"","first_name":"basyura","6":"basyura","last_name":" ","7":" ","releases":[{"0":"4532","vim_version":"7.3","1":"7.3","script_version":"2.0","2":"2.0","version_comment":"Initial upload","3":"Initial upload","package":"TweetVim.zip","4":"TweetVim.zip","src_id":"19848","5":"19848","creation_date":"1366289446","6":"1366289446"}]},"4531":{"script_id":"4531","0":"4531","script_name":"ploticus.vim","1":"ploticus.vim","script_type":"syntax","2":"syntax","summary":"Syntax file for Ploticus.","3":"Syntax file for Ploticus.","description":"Ploticus (http:\/\/ploticus.sourceforge.net\/) plotting and charting utility syntax file.","4":"Ploticus (http:\/\/ploticus.sourceforge.net\/) plotting and charting utility syntax file.","install_details":"","5":"","first_name":"Karel","6":"Karel","last_name":"Miklav","7":"Miklav","releases":[{"0":"4531","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"ploticus.vim","4":"ploticus.vim","src_id":"19846","5":"19846","creation_date":"1366282467","6":"1366282467"}]},"4530":{"script_id":"4530","0":"4530","script_name":"MakeDoxygenComment 2013","1":"MakeDoxygenComment 2013","script_type":"ftplugin","2":"ftplugin","summary":"Generate Doxygen Comment Skeleton","3":"Generate Doxygen Comment Skeleton","description":"Inserts java doxygen comments for functions.\r\nModified Leif Wickland's script to fix bugs and get it to work correctly in my Terminal IDE android environment.\r\n\r\nSee original script documentation at:\r\nhttp:\/\/www.vim.org\/scripts\/script.php?script_id=674\r\n\r\nChanges:\r\n* Supports functions on lines starting with a tab.\r\n* Fixes the bug for adding @return for void methods.\r\n* Fixed the incorrect documentation for what it generates (return instead of returns, and spaces).\r\n* Removed one extra space at end of parameters.\r\n* Supports omitting @brief tag. I uploaded a separate MakeDoxygenComment_no_brief.vim so you don't have to edit your .vimrc file if you want it removed.\r\n\r\nLimitations\r\n* Does not support more than one tab, and the tab must be 3 chars (see l:tabSize). Only supports 0 or 1 tab.\r\n\r\nBugs\r\nI've found a number of bugs that I've been trying to fix. Unfortunately the echo statements are not enough to debug it properly. For now you'll need to do some extra manual editing.\r\n* Incorrectly puts @return for class summaries.\r\n* Sometimes does not finish the doxygen comment properly (you have to manually type *\/)\r\n\r\nDevelopers\r\n* Uncomment out the echo lines if you are making changes and debugging the script.","4":"Inserts java doxygen comments for functions.\r\nModified Leif Wickland's script to fix bugs and get it to work correctly in my Terminal IDE android environment.\r\n\r\nSee original script documentation at:\r\nhttp:\/\/www.vim.org\/scripts\/script.php?script_id=674\r\n\r\nChanges:\r\n* Supports functions on lines starting with a tab.\r\n* Fixes the bug for adding @return for void methods.\r\n* Fixed the incorrect documentation for what it generates (return instead of returns, and spaces).\r\n* Removed one extra space at end of parameters.\r\n* Supports omitting @brief tag. I uploaded a separate MakeDoxygenComment_no_brief.vim so you don't have to edit your .vimrc file if you want it removed.\r\n\r\nLimitations\r\n* Does not support more than one tab, and the tab must be 3 chars (see l:tabSize). Only supports 0 or 1 tab.\r\n\r\nBugs\r\nI've found a number of bugs that I've been trying to fix. Unfortunately the echo statements are not enough to debug it properly. For now you'll need to do some extra manual editing.\r\n* Incorrectly puts @return for class summaries.\r\n* Sometimes does not finish the doxygen comment properly (you have to manually type *\/)\r\n\r\nDevelopers\r\n* Uncomment out the echo lines if you are making changes and debugging the script.","install_details":"Store MakeDoxygenComment.vim in ~\/.vim\/plugin\/\r\nThen\r\nIssue the :Dox command with the cursor on the function declaration.","5":"Store MakeDoxygenComment.vim in ~\/.vim\/plugin\/\r\nThen\r\nIssue the :Dox command with the cursor on the function declaration.","first_name":"Ryan","6":"Ryan","last_name":"De Boer","7":"De Boer","releases":[{"0":"4530","vim_version":"7.0","1":"7.0","script_version":"0.1.4.1","2":"0.1.4.1","version_comment":"Only use this version if you don't want a @brief comment and don't want to modify vimrc just to have let g:MakeDoxygenComment_briefTag=\"\"","3":"Only use this version if you don't want a @brief comment and don't want to modify vimrc just to have let g:MakeDoxygenComment_briefTag=\"\"","package":"MakeDoxygenComment_no_brief.vim","4":"MakeDoxygenComment_no_brief.vim","src_id":"19845","5":"19845","creation_date":"1366274983","6":"1366274983"},{"0":"4530","vim_version":"7.0","1":"7.0","script_version":"0.1.4","2":"0.1.4","version_comment":"Initial upload","3":"Initial upload","package":"MakeDoxygenComment.vim","4":"MakeDoxygenComment.vim","src_id":"19844","5":"19844","creation_date":"1366274790","6":"1366274790"}]},"4529":{"script_id":"4529","0":"4529","script_name":"GoldenView.Vim","1":"GoldenView.Vim","script_type":"utility","2":"utility","summary":"Always have a nice view for vim split windows","3":"Always have a nice view for vim split windows","description":"\nPlease goto homepage for a better view of the introduction.\n\nHomepage: http:\/\/zhaocai.github.io\/GoldenView.Vim\/ \nScreencast:  http:\/\/dl.dropboxusercontent.com\/u\/1897501\/Screencasts\/GoldenView.gif \n\n\nIf you like it, please star or fork in https:\/\/github.com\/zhaocai\/GoldenView.Vim so that more people may find it.\n\n\n\n\n\n\n>>> Introduction: \n\nThe initial motive for GoldenView comes from the frustration of using other vim plugins to autoresize split windows. The idea is deadly simple and very useful: resize the focused window to a proper size. However, in practice, many hiccups makes autoresizing not a smooth experience. Below are a list of issues I am trying to solve: \n\nFirst and the most important one, autoresizing should play nicely with existing plugins like tagbar, vimfiler, unite, VOoM, quickfix, undotree, gundo, etc. These windows should manage there own window size. \n\nSecond, autoresizing should take care of the other windows too. Resizing the focused window may cause the other windows become too small. When you have 4+ split windows, autoresizing may just make a mess out of it. \n\n\n\n\n>>> Features:\n\nGoldenView has preliminarily solved the issues described above. It also provides other features. Bascally, it does two things:\n\n1. Autoresizing\n\nFirst of all, it automatically resize the focused split window to a \"golden\" view based on golden ratio and textwidth.\n\n2. Tiled Windows Management\n\nSecond, it maps a single key (<C-L> by default) to nicely split windows to tiled windows.\n\n      ====+==============+============+===+\n      |   |              |            |   |\n      | F |              |    S1      | T |\n      | I |              +------------| A |\n      | L |  MAIN PANE   |    S2      | G |\n      | E |              +------------+ B |\n      | R |              |    S3      | A |\n      |   |              |            |   |\n      +===+==============+============+===+\n\nTo get this view, just hit <C-L> 4 times. or, if you have a large monitor, you may get tiled windows below.\n\n      +===+==============+==============+============+===+\n      |   |              |              |            |   |\n      | F |              |              |    S1      | T |\n      | I |              |              +------------| A |\n      | L |  MAIN PANE   |      M2      |    S2      | G |\n      | E |              |              +------------+ B |\n      | R |              |              |    S3      | A |\n      |   |              |              |            |   |\n      +===+==============+==============+============+===+\n\n\nTo quickly switch between those windows, a few keys are mapped to\n\n- Focuse to the main window\n- Switch with the largest, smallest, etc.\n- Jump to next and previous window\n\nRequirements:\n- Vim 7.3 or later\n","4":"\nPlease goto homepage for a better view of the introduction.\n\nHomepage: http:\/\/zhaocai.github.io\/GoldenView.Vim\/ \nScreencast:  http:\/\/dl.dropboxusercontent.com\/u\/1897501\/Screencasts\/GoldenView.gif \n\n\nIf you like it, please star or fork in https:\/\/github.com\/zhaocai\/GoldenView.Vim so that more people may find it.\n\n\n\n\n\n\n>>> Introduction: \n\nThe initial motive for GoldenView comes from the frustration of using other vim plugins to autoresize split windows. The idea is deadly simple and very useful: resize the focused window to a proper size. However, in practice, many hiccups makes autoresizing not a smooth experience. Below are a list of issues I am trying to solve: \n\nFirst and the most important one, autoresizing should play nicely with existing plugins like tagbar, vimfiler, unite, VOoM, quickfix, undotree, gundo, etc. These windows should manage there own window size. \n\nSecond, autoresizing should take care of the other windows too. Resizing the focused window may cause the other windows become too small. When you have 4+ split windows, autoresizing may just make a mess out of it. \n\n\n\n\n>>> Features:\n\nGoldenView has preliminarily solved the issues described above. It also provides other features. Bascally, it does two things:\n\n1. Autoresizing\n\nFirst of all, it automatically resize the focused split window to a \"golden\" view based on golden ratio and textwidth.\n\n2. Tiled Windows Management\n\nSecond, it maps a single key (<C-L> by default) to nicely split windows to tiled windows.\n\n      ====+==============+============+===+\n      |   |              |            |   |\n      | F |              |    S1      | T |\n      | I |              +------------| A |\n      | L |  MAIN PANE   |    S2      | G |\n      | E |              +------------+ B |\n      | R |              |    S3      | A |\n      |   |              |            |   |\n      +===+==============+============+===+\n\nTo get this view, just hit <C-L> 4 times. or, if you have a large monitor, you may get tiled windows below.\n\n      +===+==============+==============+============+===+\n      |   |              |              |            |   |\n      | F |              |              |    S1      | T |\n      | I |              |              +------------| A |\n      | L |  MAIN PANE   |      M2      |    S2      | G |\n      | E |              |              +------------+ B |\n      | R |              |              |    S3      | A |\n      |   |              |              |            |   |\n      +===+==============+==============+============+===+\n\n\nTo quickly switch between those windows, a few keys are mapped to\n\n- Focuse to the main window\n- Switch with the largest, smallest, etc.\n- Jump to next and previous window\n\nRequirements:\n- Vim 7.3 or later\n","install_details":"http:\/\/zhaocai.github.io\/GoldenView.Vim\/\n","5":"http:\/\/zhaocai.github.io\/GoldenView.Vim\/\n","first_name":"Zhao","6":"Zhao","last_name":"Cai","7":"Cai","releases":[{"0":"4529","vim_version":"7.3","1":"7.3","script_version":"1.3.6","2":"1.3.6","version_comment":"- Maintenance update\n","3":"- Maintenance update\n","package":"GoldenView.Vim-1.3.6.zip","4":"GoldenView.Vim-1.3.6.zip","src_id":"20059","5":"20059","creation_date":"1367977750","6":"1367977750"},{"0":"4529","vim_version":"7.3","1":"7.3","script_version":"1.0.0","2":"1.0.0","version_comment":"- 1 Major Enhancements\n    * add unite.vim local_theme\n- 5 Minor Enhancements\n    * tweak local colors for tagbar and vimfiler\n    * tagbar statusline\n    * rake install\/diff\n    * use @window_cached\n    * add config\n    \n","3":"- 1 Major Enhancements\n    * add unite.vim local_theme\n- 5 Minor Enhancements\n    * tweak local colors for tagbar and vimfiler\n    * tagbar statusline\n    * rake install\/diff\n    * use @window_cached\n    * add config\n    \n","package":"linepower.vim-1.0.0.zip","4":"linepower.vim-1.0.0.zip","src_id":"20058","5":"20058","creation_date":"1367975320","6":"1367975320"},{"0":"4529","vim_version":"7.3","1":"7.3","script_version":"1.3.5","2":"1.3.5","version_comment":"- Fix for issue #5 (github).  \n- Fix for Dirdiff, FencView\n- Improve tracing\n","3":"- Fix for issue #5 (github).  \n- Fix for Dirdiff, FencView\n- Improve tracing\n","package":"GoldenView.Vim-1.3.5.zip","4":"GoldenView.Vim-1.3.5.zip","src_id":"19946","5":"19946","creation_date":"1367010721","6":"1367010721"},{"0":"4529","vim_version":"7.3","1":"7.3","script_version":"1.3.0","2":"1.3.0","version_comment":"- Diff mode auto-resizing\n- refactor autocmd function: tweak restore behavior\n","3":"- Diff mode auto-resizing\n- refactor autocmd function: tweak restore behavior\n","package":"GoldenView.Vim-1.3.0.zip","4":"GoldenView.Vim-1.3.0.zip","src_id":"19896","5":"19896","creation_date":"1366667492","6":"1366667492"},{"0":"4529","vim_version":"7.3","1":"7.3","script_version":"1.2.2","2":"1.2.2","version_comment":"Improve documents and small bug fixes,\nLoad guard for #4 (github)\n","3":"Improve documents and small bug fixes,\nLoad guard for #4 (github)\n","package":"GoldenView.Vim-1.2.2.zip","4":"GoldenView.Vim-1.2.2.zip","src_id":"19886","5":"19886","creation_date":"1366571766","6":"1366571766"},{"0":"4529","vim_version":"7.3","1":"7.3","script_version":"1.2.0","2":"1.2.0","version_comment":"add restore rule for some special buffers, which solves all the hiccups I could identify so far.\n","3":"add restore rule for some special buffers, which solves all the hiccups I could identify so far.\n","package":"GoldenView.Vim-1.2.0.zip","4":"GoldenView.Vim-1.2.0.zip","src_id":"19861","5":"19861","creation_date":"1366344403","6":"1366344403"},{"0":"4529","vim_version":"7.3","1":"7.3","script_version":"1.1.2","2":"1.1.2","version_comment":"Improve documents, fix load sequence\n","3":"Improve documents, fix load sequence\n","package":"GoldenView.Vim-1.1.2.zip","4":"GoldenView.Vim-1.1.2.zip","src_id":"19853","5":"19853","creation_date":"1366312516","6":"1366312516"},{"0":"4529","vim_version":"7.0","1":"7.0","script_version":"1.1.1","2":"1.1.1","version_comment":"- Fix library script loading.\n","3":"- Fix library script loading.\n","package":"GoldenView.Vim-1.1.1.zip","4":"GoldenView.Vim-1.1.1.zip","src_id":"19852","5":"19852","creation_date":"1366306792","6":"1366306792"},{"0":"4529","vim_version":"7.0","1":"7.0","script_version":"1.1","2":"1.1","version_comment":"Initial upload","3":"Initial upload","package":"GoldenView.Vim.zip","4":"GoldenView.Vim.zip","src_id":"19841","5":"19841","creation_date":"1366253744","6":"1366253744"}]},"4528":{"script_id":"4528","0":"4528","script_name":"modepar","1":"modepar","script_type":"utility","2":"utility","summary":"Extended modelines to execute real Vim script when loading a file.","3":"Extended modelines to execute real Vim script when loading a file.","description":"Sometimes you want a bit of Vim code to be processed for a single file:\r\ne.g. special mappings or a few convenient functions. You can't\r\nput that into a filetype plugin, because it's for one file only, and perhaps\r\nit doesn't even have a filetype to begin with. You can write a Vim script for\r\nthat file, but you have to remember to source it, and it creates unnecessary\r\nfiles.\r\n\r\nFor instance, for a single file, you want to remap \"S\" to some function:\r\n\r\n        function! MyFunc ()\r\n           ...\r\n        endfunction\r\n        nnoremap <buffer> S :call MyFunc()<CR>\r\n\r\nModepars are meant to solve that issue: like modelines, they are bits of Vim\r\ncode contained directly in the file loaded in Vim, but unlike modelines, any\r\nVim code can be processed, not just options. Thus, the above example may appear\r\nas follows at the beginning or end of a TeX file:\r\n        \r\n        % modepar:\r\n        %\r\n        % function! MyFunc ()\r\n        %   ...\r\n        % endfunction\r\n        % nnoremap <buffer> S :call MyFunc()<CR>\r\n        %\r\n        % endmodepar\r\n\r\nThe comments make the code harmless to the TeX file, while the first and last\r\nlines signal that it should be sourced by Vim like a script.\r\n\r\nModepars are executed automatically when a file is loaded into a buffer, just\r\nlike modelines; they can also be (re)loaded by hand. All modepars are\r\nprotected by ids, and only authorized modepars are automatically executed.","4":"Sometimes you want a bit of Vim code to be processed for a single file:\r\ne.g. special mappings or a few convenient functions. You can't\r\nput that into a filetype plugin, because it's for one file only, and perhaps\r\nit doesn't even have a filetype to begin with. You can write a Vim script for\r\nthat file, but you have to remember to source it, and it creates unnecessary\r\nfiles.\r\n\r\nFor instance, for a single file, you want to remap \"S\" to some function:\r\n\r\n        function! MyFunc ()\r\n           ...\r\n        endfunction\r\n        nnoremap <buffer> S :call MyFunc()<CR>\r\n\r\nModepars are meant to solve that issue: like modelines, they are bits of Vim\r\ncode contained directly in the file loaded in Vim, but unlike modelines, any\r\nVim code can be processed, not just options. Thus, the above example may appear\r\nas follows at the beginning or end of a TeX file:\r\n        \r\n        % modepar:\r\n        %\r\n        % function! MyFunc ()\r\n        %   ...\r\n        % endfunction\r\n        % nnoremap <buffer> S :call MyFunc()<CR>\r\n        %\r\n        % endmodepar\r\n\r\nThe comments make the code harmless to the TeX file, while the first and last\r\nlines signal that it should be sourced by Vim like a script.\r\n\r\nModepars are executed automatically when a file is loaded into a buffer, just\r\nlike modelines; they can also be (re)loaded by hand. All modepars are\r\nprotected by ids, and only authorized modepars are automatically executed.","install_details":"Classic install\r\nmodepar\/plugin\/modepar.vim   goes into   ~\/.vim\/plugin\r\nmodepar\/doc\/modepar.txt          goes into   ~\/.vim\/doc\r\n\r\nPathogen;\r\nPut the entire \"modepar\" dir in \"~\/.vim\/bundle\".","5":"Classic install\r\nmodepar\/plugin\/modepar.vim   goes into   ~\/.vim\/plugin\r\nmodepar\/doc\/modepar.txt          goes into   ~\/.vim\/doc\r\n\r\nPathogen;\r\nPut the entire \"modepar\" dir in \"~\/.vim\/bundle\".","first_name":"Paul","6":"Paul","last_name":"Isambert","7":"Isambert","releases":[{"0":"4528","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"modepar.zip","4":"modepar.zip","src_id":"19838","5":"19838","creation_date":"1366231967","6":"1366231967"}]},"4527":{"script_id":"4527","0":"4527","script_name":"vim-emblem","1":"vim-emblem","script_type":"syntax","2":"syntax","summary":"Adds emblem support to vim.","3":"Adds emblem support to vim.","description":"`vim-emblem` adds emblem (http:\/\/emblemjs.com\/) support to vim.\r\n\r\nFeatures:\r\n\r\n* detects `*.emblem` files as `emblem`\r\n* sets standard coding style (two-space indentation)\r\n* syntax highlighting\r\n\r\nTodo: \r\n\r\n* smart indentation\r\n\r\nProject page: https:\/\/github.com\/heartsentwined\/vim-emblem","4":"`vim-emblem` adds emblem (http:\/\/emblemjs.com\/) support to vim.\r\n\r\nFeatures:\r\n\r\n* detects `*.emblem` files as `emblem`\r\n* sets standard coding style (two-space indentation)\r\n* syntax highlighting\r\n\r\nTodo: \r\n\r\n* smart indentation\r\n\r\nProject page: https:\/\/github.com\/heartsentwined\/vim-emblem","install_details":"Vundle and Pathogen compatible, or manual install (extract files) to `~\/.vim` \/ `$HOME\\vimfiles`.\r\n\r\nDetailed installation instructions at project page: https:\/\/github.com\/heartsentwined\/vim-emblem","5":"Vundle and Pathogen compatible, or manual install (extract files) to `~\/.vim` \/ `$HOME\\vimfiles`.\r\n\r\nDetailed installation instructions at project page: https:\/\/github.com\/heartsentwined\/vim-emblem","first_name":"hearts","6":"hearts","last_name":"entwined","7":"entwined","releases":[{"0":"4527","vim_version":"6.0","1":"6.0","script_version":"1.2.0","2":"1.2.0","version_comment":"highlight each xxx in xxx","3":"highlight each xxx in xxx","package":"vim-emblem-1.2.0.zip","4":"vim-emblem-1.2.0.zip","src_id":"19887","5":"19887","creation_date":"1366574442","6":"1366574442"},{"0":"4527","vim_version":"6.0","1":"6.0","script_version":"1.1.3","2":"1.1.3","version_comment":"bugfix: line-op wrongly recognized as alt-op","3":"bugfix: line-op wrongly recognized as alt-op","package":"vim-emblem-1.1.3.zip","4":"vim-emblem-1.1.3.zip","src_id":"19855","5":"19855","creation_date":"1366316937","6":"1366316937"},{"0":"4527","vim_version":"6.0","1":"6.0","script_version":"1.1.2","2":"1.1.2","version_comment":"do not highlight view as ctrl flow helper\r\nallow dot in handlebars helpers ","3":"do not highlight view as ctrl flow helper\r\nallow dot in handlebars helpers ","package":"vim-emblem-1.1.2.zip","4":"vim-emblem-1.1.2.zip","src_id":"19843","5":"19843","creation_date":"1366260738","6":"1366260738"},{"0":"4527","vim_version":"6.0","1":"6.0","script_version":"1.1.1","2":"1.1.1","version_comment":"do not insert comment leader on new line","3":"do not insert comment leader on new line","package":"vim-emblem-1.1.1.zip","4":"vim-emblem-1.1.1.zip","src_id":"19832","5":"19832","creation_date":"1366163551","6":"1366163551"},{"0":"4527","vim_version":"6.0","1":"6.0","script_version":"1.1.0","2":"1.1.0","version_comment":"bugfix: text and comment highlighting","3":"bugfix: text and comment highlighting","package":"vim-emblem-1.1.zip","4":"vim-emblem-1.1.zip","src_id":"19831","5":"19831","creation_date":"1366162678","6":"1366162678"},{"0":"4527","vim_version":"6.0","1":"6.0","script_version":"1.0.0","2":"1.0.0","version_comment":"Initial upload","3":"Initial upload","package":"vim-emblem-1.0.zip","4":"vim-emblem-1.0.zip","src_id":"19829","5":"19829","creation_date":"1366162326","6":"1366162326"}]},"4526":{"script_id":"4526","0":"4526","script_name":"vimongous","1":"vimongous","script_type":"utility","2":"utility","summary":"Query MongoDB from inside Vim","3":"Query MongoDB from inside Vim","description":"Vimongous is a Vim plugin for querying a MongoDB database from inside Vim. Query results are added to a new split buffer.\r\n\r\nFor a more detailed description (and the source), please visit: https:\/\/github.com\/robu3\/vimongous","4":"Vimongous is a Vim plugin for querying a MongoDB database from inside Vim. Query results are added to a new split buffer.\r\n\r\nFor a more detailed description (and the source), please visit: https:\/\/github.com\/robu3\/vimongous","install_details":"","5":"","first_name":"Robert","6":"Robert","last_name":"Mitchell","7":"Mitchell","releases":[{"0":"4526","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"vimongous-master.zip","4":"vimongous-master.zip","src_id":"19828","5":"19828","creation_date":"1366137755","6":"1366137755"}]},"4525":{"script_id":"4525","0":"4525","script_name":"vim-xtcl-syntax","1":"vim-xtcl-syntax","script_type":"syntax","2":"syntax","summary":"Syntax highlighting for Xilinx Vivado TCL scripts","3":"Syntax highlighting for Xilinx Vivado TCL scripts","description":"Grab the latest dev version from github: https:\/\/github.com\/amal-khailtash\/vim-xtcl-syntax.git\r\n\r\n### References\r\n\r\n* [Vivado Design Suite Tcl Command Reference Guide](http:\/\/www.xilinx.com\/support\/documentation\/sw_manuals\/xilinx2013_1\/ug835-vivado-tcl-commands.pdf)\r\n","4":"Grab the latest dev version from github: https:\/\/github.com\/amal-khailtash\/vim-xtcl-syntax.git\r\n\r\n### References\r\n\r\n* [Vivado Design Suite Tcl Command Reference Guide](http:\/\/www.xilinx.com\/support\/documentation\/sw_manuals\/xilinx2013_1\/ug835-vivado-tcl-commands.pdf)\r\n","install_details":"## Installation  \r\n\r\n_\\*Assuming **[VIM_ROOT]** is ~\/.vim (on \\*nix) or ~\/vimfiles (on Windows)_\r\n\r\nThis syntax file requires Vim 7 or higher is made up of 2 files:\r\n\r\n    ftdetect\/xtcl.vim\r\n    syntax\/xtcl.vim\r\n\r\n### Classic Install\r\n\r\n* Extract the zip contents to your **[VIM_ROOT]**\r\n\r\n### Vundle Install\r\n\r\n* Add \"Bundle 'vim-xtcl-syntax'\" to your vimrc\r\n\r\n### Pathogen Install\r\n\r\n1. Navigate to your **[VIM_ROOT]\/bundle** directory\r\n2. git clone https:\/\/github.com\/amal-khailtash\/vim-xtcl-syntax.git\r\n","5":"## Installation  \r\n\r\n_\\*Assuming **[VIM_ROOT]** is ~\/.vim (on \\*nix) or ~\/vimfiles (on Windows)_\r\n\r\nThis syntax file requires Vim 7 or higher is made up of 2 files:\r\n\r\n    ftdetect\/xtcl.vim\r\n    syntax\/xtcl.vim\r\n\r\n### Classic Install\r\n\r\n* Extract the zip contents to your **[VIM_ROOT]**\r\n\r\n### Vundle Install\r\n\r\n* Add \"Bundle 'vim-xtcl-syntax'\" to your vimrc\r\n\r\n### Pathogen Install\r\n\r\n1. Navigate to your **[VIM_ROOT]\/bundle** directory\r\n2. git clone https:\/\/github.com\/amal-khailtash\/vim-xtcl-syntax.git\r\n","first_name":"Amal","6":"Amal","last_name":"Khailtash","7":"Khailtash","releases":[{"0":"4525","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"vim-xtcl-syntax.zip","4":"vim-xtcl-syntax.zip","src_id":"19826","5":"19826","creation_date":"1366136763","6":"1366136763"}]},"4524":{"script_id":"4524","0":"4524","script_name":"vim-latex-live-preview","1":"vim-latex-live-preview","script_type":"utility","2":"utility","summary":"This plugin provides a live preview of the output PDF of your LaTeX file.","3":"This plugin provides a live preview of the output PDF of your LaTeX file.","description":"For more information please check the homepage (GitHub repository page): https:\/\/github.com\/xuhdev\/vim-latex-live-preview\r\n\r\nAnd there's a useful blog post: http:\/\/www.topbug.net\/blog\/2013\/06\/13\/live-preview-of-latex-in-vim\/index.html\r\n\r\nThis plugin provides a live preview of the output PDF of your LaTeX file. The display of the output PDF file will be updated lively as you type (just hold the cursor and you will see the PDF file updated). Currently, vim-latex-live-preview only support UNIX-like systems. Please let me know if you have any suggestions.","4":"For more information please check the homepage (GitHub repository page): https:\/\/github.com\/xuhdev\/vim-latex-live-preview\r\n\r\nAnd there's a useful blog post: http:\/\/www.topbug.net\/blog\/2013\/06\/13\/live-preview-of-latex-in-vim\/index.html\r\n\r\nThis plugin provides a live preview of the output PDF of your LaTeX file. The display of the output PDF file will be updated lively as you type (just hold the cursor and you will see the PDF file updated). Currently, vim-latex-live-preview only support UNIX-like systems. Please let me know if you have any suggestions.","install_details":"Before installation, you need to make sure your Vim version is later than 7.3, and is compiled with +python feature. Then copy plugin\/latexlivepreview.vim to ~\/.vim\/plugin.\r\n\r\nBy default, you need to have evince or okular installed as pdf viewers. But you can specify your own viewer by setting g:livepreview_previewer option in your .vimrc:\r\n\r\nlet g:livepreview_previewer = 'your_viewer'\r\n\r\nPlease note that not every pdf viewer could work with this plugin. Currently evince and okular are known to work well. You can check the list of working pdf viewers here:  https:\/\/github.com\/xuhdev\/vim-latex-live-preview\/wiki\/Known-Working-PDF-Viewers","5":"Before installation, you need to make sure your Vim version is later than 7.3, and is compiled with +python feature. Then copy plugin\/latexlivepreview.vim to ~\/.vim\/plugin.\r\n\r\nBy default, you need to have evince or okular installed as pdf viewers. But you can specify your own viewer by setting g:livepreview_previewer option in your .vimrc:\r\n\r\nlet g:livepreview_previewer = 'your_viewer'\r\n\r\nPlease note that not every pdf viewer could work with this plugin. Currently evince and okular are known to work well. You can check the list of working pdf viewers here:  https:\/\/github.com\/xuhdev\/vim-latex-live-preview\/wiki\/Known-Working-PDF-Viewers","first_name":"Hong","6":"Hong","last_name":"Xu","7":"Xu","releases":[{"0":"4524","vim_version":"7.3","1":"7.3","script_version":"0.1.0","2":"0.1.0","version_comment":"Initial upload","3":"Initial upload","package":"vim-latex-live-preview-0.1.0.zip","4":"vim-latex-live-preview-0.1.0.zip","src_id":"19825","5":"19825","creation_date":"1366131843","6":"1366131843"}]},"4523":{"script_id":"4523","0":"4523","script_name":"vim-multiple-cursors","1":"vim-multiple-cursors","script_type":"utility","2":"utility","summary":"True Sublime Text style multiple selections for Vim","3":"True Sublime Text style multiple selections for Vim","description":"See https:\/\/github.com\/terryma\/vim-multiple-cursors","4":"See https:\/\/github.com\/terryma\/vim-multiple-cursors","install_details":"See https:\/\/github.com\/terryma\/vim-multiple-cursors#installation","5":"See https:\/\/github.com\/terryma\/vim-multiple-cursors#installation","first_name":"Terry","6":"Terry","last_name":"Ma","7":"Ma","releases":[{"0":"4523","vim_version":"7.3","1":"7.3","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"vim-multiple-cursors.zip","4":"vim-multiple-cursors.zip","src_id":"19814","5":"19814","creation_date":"1365931017","6":"1365931017"}]},"4522":{"script_id":"4522","0":"4522","script_name":"VERun","1":"VERun","script_type":"utility","2":"utility","summary":"Easily run\/compile your files inside vim","3":"Easily run\/compile your files inside vim","description":"The main goal of VERun is to run your program with just one command without leaving vim. You just open the file you want to run and execute :VERun.\r\n\r\nMain features included in version 0.9:\r\n- Runs C\/C++, php, python, bash\/sh and makefiles with just one command, without needing to cd your dir nor configuring anything\r\n- Auto detect your C\/C++ headers and adds the links to the g++ command (see :h VECppAutoHeaderList)\r\n- Auto detect your python version\r\n- Option to execute your program in an external terminal\r\n- Currently supports only C\/C++, php, python, bash\/sh and makefiles\r\n\r\nTo compile\/run your program, run:\r\n\t:VERun\r\n\r\nFor further instructions and configuration check the help file included in the tar ball.\r\nPlease feel free to contact me for eventual bugs, suggestions, complains or anything","4":"The main goal of VERun is to run your program with just one command without leaving vim. You just open the file you want to run and execute :VERun.\r\n\r\nMain features included in version 0.9:\r\n- Runs C\/C++, php, python, bash\/sh and makefiles with just one command, without needing to cd your dir nor configuring anything\r\n- Auto detect your C\/C++ headers and adds the links to the g++ command (see :h VECppAutoHeaderList)\r\n- Auto detect your python version\r\n- Option to execute your program in an external terminal\r\n- Currently supports only C\/C++, php, python, bash\/sh and makefiles\r\n\r\nTo compile\/run your program, run:\r\n\t:VERun\r\n\r\nFor further instructions and configuration check the help file included in the tar ball.\r\nPlease feel free to contact me for eventual bugs, suggestions, complains or anything","install_details":"Download and extract the file in your ~\/.vim\/\r\n----\r\nIf you want the development version, check the git repository: https:\/\/github.com\/sollidsnake\/verun","5":"Download and extract the file in your ~\/.vim\/\r\n----\r\nIf you want the development version, check the git repository: https:\/\/github.com\/sollidsnake\/verun","first_name":"Jesse","6":"Jesse","last_name":"Nazario","7":"Nazario","releases":[{"0":"4522","vim_version":"7.0","1":"7.0","script_version":"0.9","2":"0.9","version_comment":"Initial upload","3":"Initial upload","package":"verun-0.9.tar.gz","4":"verun-0.9.tar.gz","src_id":"19813","5":"19813","creation_date":"1365881420","6":"1365881420"}]},"4521":{"script_id":"4521","0":"4521","script_name":"vim-auto-save","1":"vim-auto-save","script_type":"utility","2":"utility","summary":"Automatically save changes to disk","3":"Automatically save changes to disk","description":"AutoSave - automatically save changes to disk without having to use :w (or any binding to it) every time a buffer has been modified.\r\nAutoSave is disabled by default, run :AutoSaveToggle to enable\/disable AutoSave.\r\nIf you want plugin to be always enabled it can be done with g:auto_save option (place 'let g:auto_save = 1' in your .vimrc).\r\nInspired by the same feature in RubyMine text editor.","4":"AutoSave - automatically save changes to disk without having to use :w (or any binding to it) every time a buffer has been modified.\r\nAutoSave is disabled by default, run :AutoSaveToggle to enable\/disable AutoSave.\r\nIf you want plugin to be always enabled it can be done with g:auto_save option (place 'let g:auto_save = 1' in your .vimrc).\r\nInspired by the same feature in RubyMine text editor.","install_details":"Use vundle (https:\/\/github.com\/gmarik\/vundle) to install the plugin.\r\nPlugin repository on github: https:\/\/github.com\/907th\/vim-auto-save","5":"Use vundle (https:\/\/github.com\/gmarik\/vundle) to install the plugin.\r\nPlugin repository on github: https:\/\/github.com\/907th\/vim-auto-save","first_name":"Alexey","6":"Alexey","last_name":"Chernenkov","7":"Chernenkov","releases":[{"0":"4521","vim_version":"7.0","1":"7.0","script_version":"0.1.12","2":"0.1.12","version_comment":"Fixed support for b:auto_save option. Documentation updated.","3":"Fixed support for b:auto_save option. Documentation updated.","package":"vim-auto-save-0.1.12.tar.gz","4":"vim-auto-save-0.1.12.tar.gz","src_id":"26426","5":"26426","creation_date":"1553005216","6":"1553005216"},{"0":"4521","vim_version":"7.0","1":"7.0","script_version":"0.1.11","2":"0.1.11","version_comment":"Add `b:auto_save` magic var support","3":"Add `b:auto_save` magic var support","package":"vim-auto-save-0.1.11.tar.gz","4":"vim-auto-save-0.1.11.tar.gz","src_id":"26404","5":"26404","creation_date":"1551217455","6":"1551217455"},{"0":"4521","vim_version":"7.4","1":"7.4","script_version":"0.1.10","2":"0.1.10","version_comment":"Check if the buffer was actually modified before auto-saving. Previously auto-saving happened on every configured event (even when the buffer was not modified).","3":"Check if the buffer was actually modified before auto-saving. Previously auto-saving happened on every configured event (even when the buffer was not modified).","package":"vim-auto-save-0.1.10.tar.gz","4":"vim-auto-save-0.1.10.tar.gz","src_id":"25644","5":"25644","creation_date":"1510551495","6":"1510551495"},{"0":"4521","vim_version":"7.4","1":"7.4","script_version":"0.1.9","2":"0.1.9","version_comment":"Add pre-save hook, update docs.\r\nSee https:\/\/github.com\/907th\/vim-auto-save for more info","3":"Add pre-save hook, update docs.\r\nSee https:\/\/github.com\/907th\/vim-auto-save for more info","package":"vim-auto-save-0.1.9.tar.gz","4":"vim-auto-save-0.1.9.tar.gz","src_id":"24894","5":"24894","creation_date":"1484401459","6":"1484401459"},{"0":"4521","vim_version":"7.4","1":"7.4","script_version":"0.1.8","2":"0.1.8","version_comment":"See https:\/\/github.com\/907th\/vim-auto-save","3":"See https:\/\/github.com\/907th\/vim-auto-save","package":"vim-auto-save-0.1.8.tar.gz","4":"vim-auto-save-0.1.8.tar.gz","src_id":"24521","5":"24521","creation_date":"1473673612","6":"1473673612"},{"0":"4521","vim_version":"7.4","1":"7.4","script_version":"0.1.7","2":"0.1.7","version_comment":"Fixed interaction with Syntastic","3":"Fixed interaction with Syntastic","package":"vim-auto-save.tar.gz","4":"vim-auto-save.tar.gz","src_id":"22973","5":"22973","creation_date":"1425286025","6":"1425286025"},{"0":"4521","vim_version":"7.0","1":"7.0","script_version":"0.1.6","2":"0.1.6","version_comment":"Enable\/disable auto-save in insert mode via g:auto_save_in_insert_mode option (by Aaron Jensen)","3":"Enable\/disable auto-save in insert mode via g:auto_save_in_insert_mode option (by Aaron Jensen)","package":"vim-auto-save.tar.gz","4":"vim-auto-save.tar.gz","src_id":"22470","5":"22470","creation_date":"1412157619","6":"1412157619"},{"0":"4521","vim_version":"7.0","1":"7.0","script_version":"0.1.5","2":"0.1.5","version_comment":"Enable silent AutoSave (by Ryan Sepassi)","3":"Enable silent AutoSave (by Ryan Sepassi)","package":"vim-auto-save.tar.gz","4":"vim-auto-save.tar.gz","src_id":"22430","5":"22430","creation_date":"1410855738","6":"1410855738"},{"0":"4521","vim_version":"7.0","1":"7.0","script_version":"0.1.4","2":"0.1.4","version_comment":"Autosave on CursorHoldI too. Thanks to Premysl Kafka.","3":"Autosave on CursorHoldI too. Thanks to Premysl Kafka.","package":"vim-auto-save.tar.gz","4":"vim-auto-save.tar.gz","src_id":"21718","5":"21718","creation_date":"1396497474","6":"1396497474"},{"0":"4521","vim_version":"7.0","1":"7.0","script_version":"0.1.3","2":"0.1.3","version_comment":"Now you can prevent AutoSave from changing the `updatetime` with `g:auto_save_no_updatetime` option.","3":"Now you can prevent AutoSave from changing the `updatetime` with `g:auto_save_no_updatetime` option.","package":"vim-auto-save.tar.gz","4":"vim-auto-save.tar.gz","src_id":"20034","5":"20034","creation_date":"1367863130","6":"1367863130"},{"0":"4521","vim_version":"7.0","1":"7.0","script_version":"0.1.2","2":"0.1.2","version_comment":"Prevent plugin from loading twice and do not reset auto-save option if it's already set.","3":"Prevent plugin from loading twice and do not reset auto-save option if it's already set.","package":"vim-auto-save.tar.gz","4":"vim-auto-save.tar.gz","src_id":"19926","5":"19926","creation_date":"1366818332","6":"1366818332"},{"0":"4521","vim_version":"7.0","1":"7.0","script_version":"0.1.1","2":"0.1.1","version_comment":"Initial upload","3":"Initial upload","package":"vim-auto-save.tar.gz","4":"vim-auto-save.tar.gz","src_id":"19810","5":"19810","creation_date":"1365844477","6":"1365844477"}]},"4520":{"script_id":"4520","0":"4520","script_name":"vim-easy-align","1":"vim-easy-align","script_type":"utility","2":"utility","summary":"A powerful, yet easy-to-use Vim alignment plugin","3":"A powerful, yet easy-to-use Vim alignment plugin","description":"A powerful, yet easy-to-use Vim alignment plugin\r\n\r\nProject home (latest version):\r\nhttps:\/\/github.com\/junegunn\/vim-easy-align\r\n\r\nDemo:\r\nhttps:\/\/raw.github.com\/junegunn\/i\/master\/vim-easy-align.gif\r\n\r\nQuick start guide:\r\nhttps:\/\/github.com\/junegunn\/vim-easy-align#tldr---one-minute-guide\r\n\r\nFeatures:\r\n- Makes the common case easy\r\n  - Comes with a predefined set of alignment rules\r\n  - Provides a fast and intuitive interface\r\n- Extensible\r\n  - You can define your own rules\r\n  - Supports arbitrary regular expressions\r\n- Optimized for code editing\r\n  - Takes advantage of syntax highlighting feature to avoid unwanted alignments","4":"A powerful, yet easy-to-use Vim alignment plugin\r\n\r\nProject home (latest version):\r\nhttps:\/\/github.com\/junegunn\/vim-easy-align\r\n\r\nDemo:\r\nhttps:\/\/raw.github.com\/junegunn\/i\/master\/vim-easy-align.gif\r\n\r\nQuick start guide:\r\nhttps:\/\/github.com\/junegunn\/vim-easy-align#tldr---one-minute-guide\r\n\r\nFeatures:\r\n- Makes the common case easy\r\n  - Comes with a predefined set of alignment rules\r\n  - Provides a fast and intuitive interface\r\n- Extensible\r\n  - You can define your own rules\r\n  - Supports arbitrary regular expressions\r\n- Optimized for code editing\r\n  - Takes advantage of syntax highlighting feature to avoid unwanted alignments","install_details":"Extract in ~\/.vim, or use a plugin manager. Check out mine: https:\/\/github.com\/junegunn\/vim-plug","5":"Extract in ~\/.vim, or use a plugin manager. Check out mine: https:\/\/github.com\/junegunn\/vim-plug","first_name":"Junegunn","6":"Junegunn","last_name":"Choi","7":"Choi","releases":[{"0":"4520","vim_version":"7.0","1":"7.0","script_version":"2.9.3","2":"2.9.3","version_comment":"Better handling of tab characters","3":"Better handling of tab characters","package":"vim-easy-align.zip","4":"vim-easy-align.zip","src_id":"21888","5":"21888","creation_date":"1400209022","6":"1400209022"},{"0":"4520","vim_version":"7.0","1":"7.0","script_version":"2.9.2","2":"2.9.2","version_comment":"Removed +float dependency","3":"Removed +float dependency","package":"vim-easy-align.zip","4":"vim-easy-align.zip","src_id":"21347","5":"21347","creation_date":"1390181749","6":"1390181749"},{"0":"4520","vim_version":"7.3","1":"7.3","script_version":"2.9.1","2":"2.9.1","version_comment":"- visualrepeat integration\r\n- Helpfile updated","3":"- visualrepeat integration\r\n- Helpfile updated","package":"vim-easy-align.zip","4":"vim-easy-align.zip","src_id":"21169","5":"21169","creation_date":"1386431998","6":"1386431998"},{"0":"4520","vim_version":"7.3","1":"7.3","script_version":"2.9.0","2":"2.9.0","version_comment":"repeat.vim integration with <Plug>(EasyAlign) and <Plug>(LiveEasyAlign)","3":"repeat.vim integration with <Plug>(EasyAlign) and <Plug>(LiveEasyAlign)","package":"vim-easy-align.zip","4":"vim-easy-align.zip","src_id":"21161","5":"21161","creation_date":"1386253228","6":"1386253228"},{"0":"4520","vim_version":"7.3","1":"7.3","script_version":"2.8.1","2":"2.8.1","version_comment":"- A bug fix on hard-tab support","3":"- A bug fix on hard-tab support","package":"vim-easy-align.zip","4":"vim-easy-align.zip","src_id":"21117","5":"21117","creation_date":"1385525752","6":"1385525752"},{"0":"4520","vim_version":"7.3","1":"7.3","script_version":"2.8.0","2":"2.8.0","version_comment":"- Added `filter` option\r\n- Hard tab support","3":"- Added `filter` option\r\n- Hard tab support","package":"vim-easy-align.zip","4":"vim-easy-align.zip","src_id":"20988","5":"20988","creation_date":"1383236243","6":"1383236243"},{"0":"4520","vim_version":"7.3","1":"7.3","script_version":"2.7.0","2":"2.7.0","version_comment":"- Added LiveEasyAlign command (interactive mode with live preview)\r\n- Added & rule for LaTeX tables\r\n- Added g:easy_align_bypass_fold switch\r\n- Performance optimization\r\n- Bug fixes","3":"- Added LiveEasyAlign command (interactive mode with live preview)\r\n- Added & rule for LaTeX tables\r\n- Added g:easy_align_bypass_fold switch\r\n- Performance optimization\r\n- Bug fixes","package":"vim-easy-align.zip","4":"vim-easy-align.zip","src_id":"20940","5":"20940","creation_date":"1382365496","6":"1382365496"},{"0":"4520","vim_version":"7.3","1":"7.3","script_version":"2.6.1","2":"2.6.1","version_comment":"- Shorthand option notation now can be used with delimiter key as well","3":"- Shorthand option notation now can be used with delimiter key as well","package":"vim-easy-align.zip","4":"vim-easy-align.zip","src_id":"20897","5":"20897","creation_date":"1381148357","6":"1381148357"},{"0":"4520","vim_version":"7.3","1":"7.3","script_version":"2.6.0","2":"2.6.0","version_comment":"- Shorthand notation for options\r\n- Usability improvements","3":"- Shorthand notation for options\r\n- Usability improvements","package":"vim-easy-align.zip","4":"vim-easy-align.zip","src_id":"20884","5":"20884","creation_date":"1380958730","6":"1380958730"},{"0":"4520","vim_version":"7.3","1":"7.3","script_version":"2.5.1","2":"2.5.1","version_comment":"- Interactive mode made more forgiving of invalid inputs","3":"- Interactive mode made more forgiving of invalid inputs","package":"vim-easy-align.zip","4":"vim-easy-align.zip","src_id":"20856","5":"20856","creation_date":"1380249529","6":"1380249529"},{"0":"4520","vim_version":"7.3","1":"7.3","script_version":"2.5.0","2":"2.5.0","version_comment":"- Improved output: Colored and replayable\r\n- Fixed a minor bug in center-alignment\r\n- Fixed invalid type conversion in interactive mode user prompt","3":"- Improved output: Colored and replayable\r\n- Fixed a minor bug in center-alignment\r\n- Fixed invalid type conversion in interactive mode user prompt","package":"vim-easy-align.zip","4":"vim-easy-align.zip","src_id":"20821","5":"20821","creation_date":"1379703037","6":"1379703037"},{"0":"4520","vim_version":"7.3","1":"7.3","script_version":"2.4.2","2":"2.4.2","version_comment":"- Changed <Left> key to set left_margin to zero\r\n- Updated help file","3":"- Changed <Left> key to set left_margin to zero\r\n- Updated help file","package":"vim-easy-align.zip","4":"vim-easy-align.zip","src_id":"20814","5":"20814","creation_date":"1379431175","6":"1379431175"},{"0":"4520","vim_version":"7.3","1":"7.3","script_version":"2.4.1","2":"2.4.1","version_comment":"- <CTRL-\/> doesn't work on GVim. So added <CTRL-X> as another trigger for regular expression\r\n- <Left>, <Right> key to toggle stick_to_left option\r\n- Retain visual selection display on <CTRL-L\/R\/O\/X>","3":"- <CTRL-\/> doesn't work on GVim. So added <CTRL-X> as another trigger for regular expression\r\n- <Left>, <Right> key to toggle stick_to_left option\r\n- Retain visual selection display on <CTRL-L\/R\/O\/X>","package":"vim-easy-align.zip","4":"vim-easy-align.zip","src_id":"20802","5":"20802","creation_date":"1379129753","6":"1379129753"},{"0":"4520","vim_version":"7.3","1":"7.3","script_version":"2.4.0","2":"2.4.0","version_comment":"- Regular expression support in interactive mode (CTRL-\/)\r\n- Implemented `mode_sequence' expansion: e.g. lrc*, lrc**","3":"- Regular expression support in interactive mode (CTRL-\/)\r\n- Implemented `mode_sequence' expansion: e.g. lrc*, lrc**","package":"vim-easy-align.zip","4":"vim-easy-align.zip","src_id":"20796","5":"20796","creation_date":"1379087048","6":"1379087048"},{"0":"4520","vim_version":"7.3","1":"7.3","script_version":"2.3.1","2":"2.3.1","version_comment":"- Implemented 'stick_to_left' option in center-alignment mode","3":"- Implemented 'stick_to_left' option in center-alignment mode","package":"vim-easy-align.zip","4":"vim-easy-align.zip","src_id":"20708","5":"20708","creation_date":"1377358710","6":"1377358710"},{"0":"4520","vim_version":"7.3","1":"7.3","script_version":"2.3.0","2":"2.3.0","version_comment":"- Added special keys to set alignment options in interactive mode\r\n- Better center-alignment in the presence of leading whitespaces","3":"- Added special keys to set alignment options in interactive mode\r\n- Better center-alignment in the presence of leading whitespaces","package":"vim-easy-align.zip","4":"vim-easy-align.zip","src_id":"20700","5":"20700","creation_date":"1377192384","6":"1377192384"},{"0":"4520","vim_version":"7.3","1":"7.3","script_version":"2.2.0","2":"2.2.0","version_comment":"- Added center-alignment mode\r\n- Improved right-alignment mode\r\n- Added `mode_sequence` option","3":"- Added center-alignment mode\r\n- Improved right-alignment mode\r\n- Added `mode_sequence` option","package":"vim-easy-align.zip","4":"vim-easy-align.zip","src_id":"20674","5":"20674","creation_date":"1376878555","6":"1376878555"},{"0":"4520","vim_version":"7.3","1":"7.3","script_version":"2.1.0","2":"2.1.0","version_comment":"- Added `delimiter_align` option\r\n- Added support for regular expressions with lookaheads and lookbehinds","3":"- Added `delimiter_align` option\r\n- Added support for regular expressions with lookaheads and lookbehinds","package":"vim-easy-align.zip","4":"vim-easy-align.zip","src_id":"20636","5":"20636","creation_date":"1376394230","6":"1376394230"},{"0":"4520","vim_version":"7.3","1":"7.3","script_version":"2.0.0","2":"2.0.0","version_comment":"Major improvement in :EasyAlign command. Added support for arbitrary regular expressions.","3":"Major improvement in :EasyAlign command. Added support for arbitrary regular expressions.","package":"vim-easy-align.zip","4":"vim-easy-align.zip","src_id":"20608","5":"20608","creation_date":"1375803491","6":"1375803491"},{"0":"4520","vim_version":"7.3","1":"7.3","script_version":"1.7.1","2":"1.7.1","version_comment":"A bug fix (https:\/\/github.com\/junegunn\/vim-easy-align\/issues\/4)","3":"A bug fix (https:\/\/github.com\/junegunn\/vim-easy-align\/issues\/4)","package":"vim-easy-align.zip","4":"vim-easy-align.zip","src_id":"20584","5":"20584","creation_date":"1375368631","6":"1375368631"},{"0":"4520","vim_version":"7.3","1":"7.3","script_version":"1.7","2":"1.7","version_comment":"Made it possible to ignore delimiters in certain syntax highlighting groups (e.g. strings, comments)","3":"Made it possible to ignore delimiters in certain syntax highlighting groups (e.g. strings, comments)","package":"vim-easy-align.zip","4":"vim-easy-align.zip","src_id":"20577","5":"20577","creation_date":"1375178513","6":"1375178513"},{"0":"4520","vim_version":"7.3","1":"7.3","script_version":"1.6","2":"1.6","version_comment":"Added left-right alternating alignment mode (**)","3":"Added left-right alternating alignment mode (**)","package":"vim-easy-align.zip","4":"vim-easy-align.zip","src_id":"20531","5":"20531","creation_date":"1373987201","6":"1373987201"},{"0":"4520","vim_version":"7.3","1":"7.3","script_version":"1.5.1","2":"1.5.1","version_comment":"Improved recursive(*) alignment performance","3":"Improved recursive(*) alignment performance","package":"vim-easy-align.zip","4":"vim-easy-align.zip","src_id":"20490","5":"20490","creation_date":"1373091760","6":"1373091760"},{"0":"4520","vim_version":"7.3","1":"7.3","script_version":"1.5","2":"1.5","version_comment":"Ignore comment lines","3":"Ignore comment lines","package":"vim-easy-align.zip","4":"vim-easy-align.zip","src_id":"20372","5":"20372","creation_date":"1371619358","6":"1371619358"},{"0":"4520","vim_version":"7.3","1":"7.3","script_version":"1.4","2":"1.4","version_comment":"Added support for negative field numbers (backward scan). \r\nFixed invalid alignment in the presence of multibyte characters. \r\nAdded an alignment rule for closing braces.","3":"Added support for negative field numbers (backward scan). \r\nFixed invalid alignment in the presence of multibyte characters. \r\nAdded an alignment rule for closing braces.","package":"vim-easy-align.zip","4":"vim-easy-align.zip","src_id":"20113","5":"20113","creation_date":"1368460961","6":"1368460961"},{"0":"4520","vim_version":"7.3","1":"7.3","script_version":"1.3","2":"1.3","version_comment":"Fixed tag in help file. Updated a predefined alignment rule (=== in =).","3":"Fixed tag in help file. Updated a predefined alignment rule (=== in =).","package":"vim-easy-align.zip","4":"vim-easy-align.zip","src_id":"20085","5":"20085","creation_date":"1368177208","6":"1368177208"},{"0":"4520","vim_version":"7.3","1":"7.3","script_version":"1.2","2":"1.2","version_comment":"Added right-justification mode (enter key to toggle)","3":"Added right-justification mode (enter key to toggle)","package":"vim-easy-align.zip","4":"vim-easy-align.zip","src_id":"20030","5":"20030","creation_date":"1367840425","6":"1367840425"},{"0":"4520","vim_version":"7.3","1":"7.3","script_version":"1.1","2":"1.1","version_comment":"Partial alignment in blockwise-visual mode","3":"Partial alignment in blockwise-visual mode","package":"vim-easy-align.zip","4":"vim-easy-align.zip","src_id":"19994","5":"19994","creation_date":"1367420104","6":"1367420104"},{"0":"4520","vim_version":"7.3","1":"7.3","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"vim-easy-align.zip","4":"vim-easy-align.zip","src_id":"19806","5":"19806","creation_date":"1365784527","6":"1365784527"}]},"4519":{"script_id":"4519","0":"4519","script_name":"specta.vim","1":"specta.vim","script_type":"syntax","2":"syntax","summary":"Syntax highlighting for Specta\/Expecta","3":"Syntax highlighting for Specta\/Expecta","description":"specta.vim\r\nSyntax highlighting for the specta\/expecta Objective-C test frameworks.\r\n\r\nInstallation\r\n\r\nWith Vundle\r\n\r\nAdd:\r\n\r\nBundle 'Keithbsmiley\/specta.vim'\r\n\r\nTo your .vimrc and run BundleInstall from within vim or vim +BundleInstall +qall from the command line\r\n\r\nWith Pathogen\r\n\r\ncd ~\/.vim\/bundle git clone https:\/\/github.com\/Keithbsmiley\/specta.vim.git\r\n\r\nSetup\r\n\r\nYou can set the syntax for a file manually with set syntax=specta I recommend you do this in your .vimrc detecting your typical test filename, for example in mine I use:\r\n\r\nautocmd BufReadPost,BufWrite *Test.m set filetype=specta\r\n\r\nThis changes the filetype to specta whenever a file named *Test.m is read or written (written sets the syntax correctly for newly created files)\r\n\r\nI also recommend you install cocoa.vim which adds some Objective-C highlighting features (automatically used by specta.vim if installed).\r\n\r\nKnown issues\r\n\r\nRight parens ) at the end of describe blocks show up as errors\r\nHighlighting inside other blocks doesn\u00e2\u0080\u0099t work (this is because cocoa.vim messes with the block highlighting behavior)\r\nIf you find any other issues or have any recommendations on how to solve these let me know via issues\/pull requests","4":"specta.vim\r\nSyntax highlighting for the specta\/expecta Objective-C test frameworks.\r\n\r\nInstallation\r\n\r\nWith Vundle\r\n\r\nAdd:\r\n\r\nBundle 'Keithbsmiley\/specta.vim'\r\n\r\nTo your .vimrc and run BundleInstall from within vim or vim +BundleInstall +qall from the command line\r\n\r\nWith Pathogen\r\n\r\ncd ~\/.vim\/bundle git clone https:\/\/github.com\/Keithbsmiley\/specta.vim.git\r\n\r\nSetup\r\n\r\nYou can set the syntax for a file manually with set syntax=specta I recommend you do this in your .vimrc detecting your typical test filename, for example in mine I use:\r\n\r\nautocmd BufReadPost,BufWrite *Test.m set filetype=specta\r\n\r\nThis changes the filetype to specta whenever a file named *Test.m is read or written (written sets the syntax correctly for newly created files)\r\n\r\nI also recommend you install cocoa.vim which adds some Objective-C highlighting features (automatically used by specta.vim if installed).\r\n\r\nKnown issues\r\n\r\nRight parens ) at the end of describe blocks show up as errors\r\nHighlighting inside other blocks doesn\u00e2\u0080\u0099t work (this is because cocoa.vim messes with the block highlighting behavior)\r\nIf you find any other issues or have any recommendations on how to solve these let me know via issues\/pull requests","install_details":"","5":"","first_name":"Keith","6":"Keith","last_name":"Smiley","7":"Smiley","releases":[{"0":"4519","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"specta.tar.gz","4":"specta.tar.gz","src_id":"19805","5":"19805","creation_date":"1365698761","6":"1365698761"}]},"4518":{"script_id":"4518","0":"4518","script_name":"translator","1":"translator","script_type":"utility","2":"utility","summary":"Translate words with web translation engines and show result in vim","3":"Translate words with web translation engines and show result in vim","description":"Just use `:Tran` command. for example:\r\n     :Tran hello\r\n\r\nExecute ':help translator' to see more infomation in help.\r\n\r\nThe latest dev versions are on github:  https:\/\/github.com\/FuDesign2008\/translator.vim ","4":"Just use `:Tran` command. for example:\r\n     :Tran hello\r\n\r\nExecute ':help translator' to see more infomation in help.\r\n\r\nThe latest dev versions are on github:  https:\/\/github.com\/FuDesign2008\/translator.vim ","install_details":"Download the .zip package and extract it to your $VIMRUNTIME directory which would be ~\/.vim on UNIXy systems.\r\n","5":"Download the .zip package and extract it to your $VIMRUNTIME directory which would be ~\/.vim on UNIXy systems.\r\n","first_name":"fu","6":"fu","last_name":"design","7":"design","releases":[{"0":"4518","vim_version":"7.0","1":"7.0","script_version":"1.0.1","2":"1.0.1","version_comment":"Add help document","3":"Add help document","package":"translator.zip","4":"translator.zip","src_id":"19798","5":"19798","creation_date":"1365650037","6":"1365650037"},{"0":"4518","vim_version":"7.0","1":"7.0","script_version":"1.0.0","2":"1.0.0","version_comment":"Initial upload","3":"Initial upload","package":"translator.zip","4":"translator.zip","src_id":"19793","5":"19793","creation_date":"1365603168","6":"1365603168"}]},"4517":{"script_id":"4517","0":"4517","script_name":"templateX","1":"templateX","script_type":"utility","2":"utility","summary":"An advanced templating system","3":"An advanced templating system","description":"This is a plugin for Vim that will allow you to have a set of                                                                                                     \r\ntemplates for certain file types. It is useful for automating\r\nsome daily tasks with custom includes which enable you to\r\nextend the functionality of templateX.\r\n\r\nIts features makes it worth having more than only one look:\r\n\r\n  + Traverses templates folder during search for a template\r\n  + Uses templates with exact filename, *.extension or *\r\n  + Files with '%' are treated in a special way: etc%test as \/etc\/test\r\n  + User can select template variants - e.g. *.sh,shebang *.sh,shortopts\r\n  + Standard variables from the plugin are available\r\n  + Extensibe with custom include files (.vim) and templates\r\n  + Facts from facter (live or from file) can be available as template variables\r\n  + Functions as interface to logging and template variables\r\n  + Templates and includes are maintainable outside of plugin directory (central)\r\n  + Large set of example templates (bash, completion, ruby, perl, icinga, puppet)\r\n\r\nPlease provide feedback (Wiki\/Mail) - especially if you vote \"Unfulfilling\".\r\n\r\nHere is a list of all files (\"templateX\/\" at the beginning is removed) to get a better impression:\r\n\r\n# type filename \r\nd plugin\/\r\n- plugin\/templateX.vim\r\nd templates\/\r\n- templates\/*.sh,shebang\r\n- templates\/*.sh,yad-monitor_foreground_process\r\n- templates\/*.sh,shortopts\r\nd templates\/etc\/\r\nd templates\/etc\/icinga\/\r\nd templates\/etc\/icinga\/objects\/\r\n- templates\/etc\/icinga\/objects\/*.cfg.templateX.vim\r\nd templates\/etc\/icinga\/objects\/windows\/\r\n- templates\/etc\/icinga\/objects\/windows\/*.cfg\r\nd templates\/etc\/icinga\/objects\/linux\/\r\n- templates\/etc\/icinga\/objects\/linux\/*.cfg\r\nd templates\/etc\/bash_completion.d\/\r\n- templates\/etc\/bash_completion.d\/*\r\nd templates\/etc\/puppet\/\r\nd templates\/etc\/puppet\/modules\/\r\nd templates\/etc\/puppet\/modules\/*\/\r\nd templates\/etc\/puppet\/modules\/*\/manifests\/\r\nl templates\/etc\/puppet\/modules\/*\/manifests\/*.pp,complete -> init.pp,complete\r\n- templates\/etc\/puppet\/modules\/*\/manifests\/init.pp,complete\r\n- templates\/etc\/puppet\/modules\/*\/manifests\/params.pp\r\n- templates\/etc\/puppet\/modules\/*\/manifests\/init.pp,simple\r\n- templates\/etc\/puppet\/modules\/*\/manifests\/*.pp.templateX.vim\r\n- templates\/etc\/puppet\/modules\/*\/manifests\/install.pp\r\nl templates\/etc\/puppet\/modules\/*\/manifests\/* -> .\r\n- templates\/etc\/puppet\/modules\/*\/manifests\/service.pp\r\nl templates\/etc\/puppet\/modules\/*\/manifests\/*.pp,simple -> init.pp,simple\r\n- templates\/etc\/puppet\/modules\/*\/manifests\/config.pp\r\n- templates\/etc\/puppet\/modules\/*\/manifests\/init.pp,separate\r\nd templates\/etc\/puppet\/modules\/*\/files\/\r\nd templates\/etc\/puppet\/modules\/*\/files\/etc\/\r\nl templates\/etc\/puppet\/modules\/*\/files\/etc\/bash_completion.d -> ..\/..\/..\/..\/..\/bash_completion.d\r\nd templates\/etc\/puppet\/modules\/*\/tests\/\r\n- templates\/etc\/puppet\/modules\/*\/tests\/init.pp\r\nl templates\/etc\/puppet\/modules\/*\/tests\/*.pp.templateX.vim -> ..\/manifests\/*.pp.templateX.vim\r\n- templates\/etc\/puppet\/modules\/*\/tests\/*.pp\r\nd templates\/etc\/puppet\/modules\/*\/lib\/\r\nd templates\/etc\/puppet\/modules\/*\/lib\/facter\/\r\n- templates\/etc\/puppet\/modules\/*\/lib\/facter\/*.rb\r\n- templates\/etc\/puppet\/modules\/*\/lib\/facter\/*.templateX.vim\r\nd templates\/etc\/puppet\/modules\/*\/lib\/puppet\/\r\nd templates\/etc\/puppet\/modules\/*\/lib\/puppet\/parser\/\r\nd templates\/etc\/puppet\/modules\/*\/lib\/puppet\/parser\/functions\/\r\n- templates\/etc\/puppet\/modules\/*\/lib\/puppet\/parser\/functions\/*.rb\r\n- templates\/etc\/puppet\/modules\/*\/lib\/puppet\/parser\/functions\/*.templateX.vim\r\n- templates\/*.sh,yad-simple\r\n- templates\/*.sh,longopts\r\n- templates\/*.sh,yad-status_from_called\r\n- templates\/*.sh,yad-monitor_background_process\r\nd templates\/home\/\r\nd templates\/home\/*\/\r\nd templates\/home\/*\/.vim\/\r\nd templates\/home\/*\/.vim\/bundle\/\r\nd templates\/home\/*\/.vim\/bundle\/templateX\/\r\nd templates\/home\/*\/.vim\/bundle\/templateX\/templates\/\r\n- templates\/home\/*\/.vim\/bundle\/templateX\/templates\/*\r\n- templates\/home\/*\/.vim\/bundle\/templateX\/templates\/*.vim\r\nl templates\/home\/*\/.bash_completion.d -> ..\/..\/etc\/bash_completion.d\r\n- templates\/*.rb\r\n- templates\/*.pl\r\n- templates\/*.templateX.vim\r\n- COPYING\r\nd doc\/\r\n- doc\/templateX.txt\r\n- doc\/tags\r\n- README.rst\r\n","4":"This is a plugin for Vim that will allow you to have a set of                                                                                                     \r\ntemplates for certain file types. It is useful for automating\r\nsome daily tasks with custom includes which enable you to\r\nextend the functionality of templateX.\r\n\r\nIts features makes it worth having more than only one look:\r\n\r\n  + Traverses templates folder during search for a template\r\n  + Uses templates with exact filename, *.extension or *\r\n  + Files with '%' are treated in a special way: etc%test as \/etc\/test\r\n  + User can select template variants - e.g. *.sh,shebang *.sh,shortopts\r\n  + Standard variables from the plugin are available\r\n  + Extensibe with custom include files (.vim) and templates\r\n  + Facts from facter (live or from file) can be available as template variables\r\n  + Functions as interface to logging and template variables\r\n  + Templates and includes are maintainable outside of plugin directory (central)\r\n  + Large set of example templates (bash, completion, ruby, perl, icinga, puppet)\r\n\r\nPlease provide feedback (Wiki\/Mail) - especially if you vote \"Unfulfilling\".\r\n\r\nHere is a list of all files (\"templateX\/\" at the beginning is removed) to get a better impression:\r\n\r\n# type filename \r\nd plugin\/\r\n- plugin\/templateX.vim\r\nd templates\/\r\n- templates\/*.sh,shebang\r\n- templates\/*.sh,yad-monitor_foreground_process\r\n- templates\/*.sh,shortopts\r\nd templates\/etc\/\r\nd templates\/etc\/icinga\/\r\nd templates\/etc\/icinga\/objects\/\r\n- templates\/etc\/icinga\/objects\/*.cfg.templateX.vim\r\nd templates\/etc\/icinga\/objects\/windows\/\r\n- templates\/etc\/icinga\/objects\/windows\/*.cfg\r\nd templates\/etc\/icinga\/objects\/linux\/\r\n- templates\/etc\/icinga\/objects\/linux\/*.cfg\r\nd templates\/etc\/bash_completion.d\/\r\n- templates\/etc\/bash_completion.d\/*\r\nd templates\/etc\/puppet\/\r\nd templates\/etc\/puppet\/modules\/\r\nd templates\/etc\/puppet\/modules\/*\/\r\nd templates\/etc\/puppet\/modules\/*\/manifests\/\r\nl templates\/etc\/puppet\/modules\/*\/manifests\/*.pp,complete -> init.pp,complete\r\n- templates\/etc\/puppet\/modules\/*\/manifests\/init.pp,complete\r\n- templates\/etc\/puppet\/modules\/*\/manifests\/params.pp\r\n- templates\/etc\/puppet\/modules\/*\/manifests\/init.pp,simple\r\n- templates\/etc\/puppet\/modules\/*\/manifests\/*.pp.templateX.vim\r\n- templates\/etc\/puppet\/modules\/*\/manifests\/install.pp\r\nl templates\/etc\/puppet\/modules\/*\/manifests\/* -> .\r\n- templates\/etc\/puppet\/modules\/*\/manifests\/service.pp\r\nl templates\/etc\/puppet\/modules\/*\/manifests\/*.pp,simple -> init.pp,simple\r\n- templates\/etc\/puppet\/modules\/*\/manifests\/config.pp\r\n- templates\/etc\/puppet\/modules\/*\/manifests\/init.pp,separate\r\nd templates\/etc\/puppet\/modules\/*\/files\/\r\nd templates\/etc\/puppet\/modules\/*\/files\/etc\/\r\nl templates\/etc\/puppet\/modules\/*\/files\/etc\/bash_completion.d -> ..\/..\/..\/..\/..\/bash_completion.d\r\nd templates\/etc\/puppet\/modules\/*\/tests\/\r\n- templates\/etc\/puppet\/modules\/*\/tests\/init.pp\r\nl templates\/etc\/puppet\/modules\/*\/tests\/*.pp.templateX.vim -> ..\/manifests\/*.pp.templateX.vim\r\n- templates\/etc\/puppet\/modules\/*\/tests\/*.pp\r\nd templates\/etc\/puppet\/modules\/*\/lib\/\r\nd templates\/etc\/puppet\/modules\/*\/lib\/facter\/\r\n- templates\/etc\/puppet\/modules\/*\/lib\/facter\/*.rb\r\n- templates\/etc\/puppet\/modules\/*\/lib\/facter\/*.templateX.vim\r\nd templates\/etc\/puppet\/modules\/*\/lib\/puppet\/\r\nd templates\/etc\/puppet\/modules\/*\/lib\/puppet\/parser\/\r\nd templates\/etc\/puppet\/modules\/*\/lib\/puppet\/parser\/functions\/\r\n- templates\/etc\/puppet\/modules\/*\/lib\/puppet\/parser\/functions\/*.rb\r\n- templates\/etc\/puppet\/modules\/*\/lib\/puppet\/parser\/functions\/*.templateX.vim\r\n- templates\/*.sh,yad-simple\r\n- templates\/*.sh,longopts\r\n- templates\/*.sh,yad-status_from_called\r\n- templates\/*.sh,yad-monitor_background_process\r\nd templates\/home\/\r\nd templates\/home\/*\/\r\nd templates\/home\/*\/.vim\/\r\nd templates\/home\/*\/.vim\/bundle\/\r\nd templates\/home\/*\/.vim\/bundle\/templateX\/\r\nd templates\/home\/*\/.vim\/bundle\/templateX\/templates\/\r\n- templates\/home\/*\/.vim\/bundle\/templateX\/templates\/*\r\n- templates\/home\/*\/.vim\/bundle\/templateX\/templates\/*.vim\r\nl templates\/home\/*\/.bash_completion.d -> ..\/..\/etc\/bash_completion.d\r\n- templates\/*.rb\r\n- templates\/*.pl\r\n- templates\/*.templateX.vim\r\n- COPYING\r\nd doc\/\r\n- doc\/templateX.txt\r\n- doc\/tags\r\n- README.rst\r\n","install_details":"Installation is simple. If using Pathogen: unpack to ~\/.vim\/bundle\/templateX.\r\nExamine and customize the templates - use it.\r\nFor advanced configuration see README.rst.","5":"Installation is simple. If using Pathogen: unpack to ~\/.vim\/bundle\/templateX.\r\nExamine and customize the templates - use it.\r\nFor advanced configuration see README.rst.","first_name":"Michael","6":"Michael","last_name":"Arlt","7":"Arlt","releases":[{"0":"4517","vim_version":"7.0","1":"7.0","script_version":"1.14","2":"1.14","version_comment":"- Small bugfixes\/improvements in templates (especially YAD)\r\n- Additional YAD template\r\n- Renamed some templates                                                  \r\n- Cleanup of tabs\/spaces in Vim- and Puppet-templates","3":"- Small bugfixes\/improvements in templates (especially YAD)\r\n- Additional YAD template\r\n- Renamed some templates                                                  \r\n- Cleanup of tabs\/spaces in Vim- and Puppet-templates","package":"templateX.tar.gz","4":"templateX.tar.gz","src_id":"20336","5":"20336","creation_date":"1370973315","6":"1370973315"},{"0":"4517","vim_version":"7.0","1":"7.0","script_version":"1.13","2":"1.13","version_comment":"- Improved & shortened logging\r\n- Abort if user selects no template variant\r\n### no further ideas for improvement - your ideas are welcomed ###","3":"- Improved & shortened logging\r\n- Abort if user selects no template variant\r\n### no further ideas for improvement - your ideas are welcomed ###","package":"templateX.tar.gz","4":"templateX.tar.gz","src_id":"20151","5":"20151","creation_date":"1368806746","6":"1368806746"},{"0":"4517","vim_version":"7.0","1":"7.0","script_version":"1.12","2":"1.12","version_comment":"- Small improvements (no bugfixes)\r\n  - Logging for :TemplateXlog\r\n  - doc\/templateX.txt","3":"- Small improvements (no bugfixes)\r\n  - Logging for :TemplateXlog\r\n  - doc\/templateX.txt","package":"templateX.tar.gz","4":"templateX.tar.gz","src_id":"20139","5":"20139","creation_date":"1368555879","6":"1368555879"},{"0":"4517","vim_version":"7.0","1":"7.0","script_version":"1.11","2":"1.11","version_comment":"- YAD templates extended\r\n- Bugfixes\/small improvements in templates (completion, bash*getopt*, yad)","3":"- YAD templates extended\r\n- Bugfixes\/small improvements in templates (completion, bash*getopt*, yad)","package":"templateX.tar.gz","4":"templateX.tar.gz","src_id":"20115","5":"20115","creation_date":"1368468537","6":"1368468537"},{"0":"4517","vim_version":"7.0","1":"7.0","script_version":"1.1","2":"1.1","version_comment":"- New feature: Treat ``vi etc%test`` as vi \/etc\/test\r\n- New feature: User can select template variants\r\n- Reduced standard output to one line (no return needed)\r\n- Puppet templates (Designed f\u00c3\u00bcr Puppet 2.7 (Ubuntu 12.04))\r\n  - Design adjusted to `Modern Module Development from Ken Barber`__\r\n  - Variant example for manifests\/init.pp\r\n  - Moved modules templates in order to match puppet default location\r\n  - Subclasses can be in subfolders\r\n- Variant examples for Shellscripts (``*.sh``)\r\n  - longopts (uses getopt)\r\n  - shortopts (uses getopts)\r\n  - simple (shebang only)\r\n  - yad-frontend (frontend for scripts using yad - yet another dialog)\r\n- Completion template\r\n- Bugfixes in README.rst\r\n- Some smaller code improvements","3":"- New feature: Treat ``vi etc%test`` as vi \/etc\/test\r\n- New feature: User can select template variants\r\n- Reduced standard output to one line (no return needed)\r\n- Puppet templates (Designed f\u00c3\u00bcr Puppet 2.7 (Ubuntu 12.04))\r\n  - Design adjusted to `Modern Module Development from Ken Barber`__\r\n  - Variant example for manifests\/init.pp\r\n  - Moved modules templates in order to match puppet default location\r\n  - Subclasses can be in subfolders\r\n- Variant examples for Shellscripts (``*.sh``)\r\n  - longopts (uses getopt)\r\n  - shortopts (uses getopts)\r\n  - simple (shebang only)\r\n  - yad-frontend (frontend for scripts using yad - yet another dialog)\r\n- Completion template\r\n- Bugfixes in README.rst\r\n- Some smaller code improvements","package":"templateX.tar.gz","4":"templateX.tar.gz","src_id":"20092","5":"20092","creation_date":"1368303118","6":"1368303118"},{"0":"4517","vim_version":"7.0","1":"7.0","script_version":"1.01","2":"1.01","version_comment":"- Fixed case sensitivity (s\/...\/...\/gI) for tag replacement\r\n- Added message if factsfile missing\/access\r\n- Use echoe for error messages\r\n- Small changes in templates","3":"- Fixed case sensitivity (s\/...\/...\/gI) for tag replacement\r\n- Added message if factsfile missing\/access\r\n- Use echoe for error messages\r\n- Small changes in templates","package":"templateX.tar.gz","4":"templateX.tar.gz","src_id":"19865","5":"19865","creation_date":"1366443621","6":"1366443621"},{"0":"4517","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"templateX.tar.gz","4":"templateX.tar.gz","src_id":"19792","5":"19792","creation_date":"1365543139","6":"1365543139"}]},"4516":{"script_id":"4516","0":"4516","script_name":"Join","1":"Join","script_type":"utility","2":"utility","summary":"A more powerful line Join command in vim","3":"A more powerful line Join command in vim","description":"Join plugin provides more powerful line join features than the build-in :join.\r\n\r\nproject home, examples and screenshots: https:\/\/github.com\/sk1418\/Join\r\n\r\n\r\nFeatures\r\n\r\nExcept for all features provided by the build-in :join command, Join can:\r\nJoin lines with separator \r\nJoin lines with or without trimming leading whitespaces (Join! [bang] without trimming)\r\nJoin lines with negative count (backwards join)\r\nJoin lines in reverse\r\nJoin lines and keep joined lines (without removing)\r\nJoin lines with any combinations of above options\r\n\r\nUsage\r\n\r\nJoin plugin defines only one command: :Join. If there is no other customer command (by other plugins maybe) starts with J, :J is also available for :Join. The command format is:\r\n\r\n:[range]Join[!] [separator] [count] [flags]\r\n\r\nShort explanation: (detailed command description please check :h Join)\r\n\r\nall arguments are optional. If one argument was not given, the default value will be used:\r\n\r\narg      | Default value\r\n========================\r\nrange    | current line \r\ncount    | 1            \r\nbang     | \"\"           \r\nseparator| \" \"          \r\nflags    | \"\"           \r\n------------------------\r\nrange follows Vim's range definition\r\n\r\nseparator must be the 1st argument, and could be any string. It must be quoted by \" or ', depends on if an escaped special character is required.\r\n\r\nthe order of last two argument: count and flags are free. e.g :Join 5 rk and :Join rk 5, both are valid.\r\n\r\ncount could be negative number. In this case Join will do backwards join.\r\n\r\nflags :\r\n\r\nr : (reverse) join lines in reverse\r\nk : (keep) don't remove joined line after join\r\nIf you don't give [separator] and [flags] also give only positive [count], the :Join works as same as build-in :join\r\n\r\nExamples:\r\n\r\n\r\nMore examples with screenshots can be found at https:\/\/github.com\/sk1418\/Join\r\n\r\n(* indicates cursor in example)\r\n\r\nOriginal file: >\r\n\r\n    1\r\n    2\r\n    3\r\n    4\r\n    5*\r\n    6\r\n    7\r\n    8\r\n    9\r\n    10\r\n\r\n- with [separator] and [count] >\r\n\r\n   :J ', ' 3\r\n\r\nresult >\r\n\r\n    1\r\n    2\r\n    3\r\n    4\r\n    5, 6, 7\r\n    8*\r\n    9\r\n    10\r\n\r\n\r\n- with [separator], [count] and [flag] r  >\r\n\r\n :J '-' 3 r\r\n\r\nresult >\r\n\r\n    1\r\n    2\r\n    3\r\n    4\r\n    7-6-5\r\n    8*\r\n    9\r\n    10\r\n\r\n- with [separator], [count] and [flag] k >\r\n\r\n :J '-' 3 k\r\n\r\nresult >\r\n\r\n    1\r\n    2\r\n    3\r\n    4\r\n    *5-6-7\r\n    6\r\n    7\r\n    8\r\n    9\r\n    10\r\n\r\n\r\n- with negative [count] >\r\n\r\n :J -3\r\n\r\nresult >\r\n\r\n    1\r\n    2\r\n    3 4 5\r\n    6*\r\n    7\r\n    8\r\n    9\r\n    10\r\n\r\n\r\n- with special [separator], negative [count] and [flag] kr >\r\n\r\n :J \"'\\\"\\t\" -3 kr\r\n\r\nresult >\r\n\r\n    1\r\n    2\r\n    3\r\n    4\r\n    5'\"\t4'\"\t3\r\n    6*\r\n    7\r\n    8\r\n    9\r\n    10\r\n\r\n\r\n- with [range] and [count] >\r\n\r\n :2,5J 3\r\n\r\nresult >\r\n    1\r\n    2\r\n    3\r\n    4\r\n    5 6 7\r\n    8*\r\n    9\r\n    10\r\n\r\n- with [range], negative [count] and [flag] k >\r\n\r\n :5,7J -3 k\r\n\r\nresult >\r\n\r\n    1\r\n    2\r\n    3\r\n    4\r\n    *3 4 5\r\n    6\r\n    7\r\n    8\r\n    9\r\n    10\r\n","4":"Join plugin provides more powerful line join features than the build-in :join.\r\n\r\nproject home, examples and screenshots: https:\/\/github.com\/sk1418\/Join\r\n\r\n\r\nFeatures\r\n\r\nExcept for all features provided by the build-in :join command, Join can:\r\nJoin lines with separator \r\nJoin lines with or without trimming leading whitespaces (Join! [bang] without trimming)\r\nJoin lines with negative count (backwards join)\r\nJoin lines in reverse\r\nJoin lines and keep joined lines (without removing)\r\nJoin lines with any combinations of above options\r\n\r\nUsage\r\n\r\nJoin plugin defines only one command: :Join. If there is no other customer command (by other plugins maybe) starts with J, :J is also available for :Join. The command format is:\r\n\r\n:[range]Join[!] [separator] [count] [flags]\r\n\r\nShort explanation: (detailed command description please check :h Join)\r\n\r\nall arguments are optional. If one argument was not given, the default value will be used:\r\n\r\narg      | Default value\r\n========================\r\nrange    | current line \r\ncount    | 1            \r\nbang     | \"\"           \r\nseparator| \" \"          \r\nflags    | \"\"           \r\n------------------------\r\nrange follows Vim's range definition\r\n\r\nseparator must be the 1st argument, and could be any string. It must be quoted by \" or ', depends on if an escaped special character is required.\r\n\r\nthe order of last two argument: count and flags are free. e.g :Join 5 rk and :Join rk 5, both are valid.\r\n\r\ncount could be negative number. In this case Join will do backwards join.\r\n\r\nflags :\r\n\r\nr : (reverse) join lines in reverse\r\nk : (keep) don't remove joined line after join\r\nIf you don't give [separator] and [flags] also give only positive [count], the :Join works as same as build-in :join\r\n\r\nExamples:\r\n\r\n\r\nMore examples with screenshots can be found at https:\/\/github.com\/sk1418\/Join\r\n\r\n(* indicates cursor in example)\r\n\r\nOriginal file: >\r\n\r\n    1\r\n    2\r\n    3\r\n    4\r\n    5*\r\n    6\r\n    7\r\n    8\r\n    9\r\n    10\r\n\r\n- with [separator] and [count] >\r\n\r\n   :J ', ' 3\r\n\r\nresult >\r\n\r\n    1\r\n    2\r\n    3\r\n    4\r\n    5, 6, 7\r\n    8*\r\n    9\r\n    10\r\n\r\n\r\n- with [separator], [count] and [flag] r  >\r\n\r\n :J '-' 3 r\r\n\r\nresult >\r\n\r\n    1\r\n    2\r\n    3\r\n    4\r\n    7-6-5\r\n    8*\r\n    9\r\n    10\r\n\r\n- with [separator], [count] and [flag] k >\r\n\r\n :J '-' 3 k\r\n\r\nresult >\r\n\r\n    1\r\n    2\r\n    3\r\n    4\r\n    *5-6-7\r\n    6\r\n    7\r\n    8\r\n    9\r\n    10\r\n\r\n\r\n- with negative [count] >\r\n\r\n :J -3\r\n\r\nresult >\r\n\r\n    1\r\n    2\r\n    3 4 5\r\n    6*\r\n    7\r\n    8\r\n    9\r\n    10\r\n\r\n\r\n- with special [separator], negative [count] and [flag] kr >\r\n\r\n :J \"'\\\"\\t\" -3 kr\r\n\r\nresult >\r\n\r\n    1\r\n    2\r\n    3\r\n    4\r\n    5'\"\t4'\"\t3\r\n    6*\r\n    7\r\n    8\r\n    9\r\n    10\r\n\r\n\r\n- with [range] and [count] >\r\n\r\n :2,5J 3\r\n\r\nresult >\r\n    1\r\n    2\r\n    3\r\n    4\r\n    5 6 7\r\n    8*\r\n    9\r\n    10\r\n\r\n- with [range], negative [count] and [flag] k >\r\n\r\n :5,7J -3 k\r\n\r\nresult >\r\n\r\n    1\r\n    2\r\n    3\r\n    4\r\n    *3 4 5\r\n    6\r\n    7\r\n    8\r\n    9\r\n    10\r\n","install_details":"","5":"","first_name":"Kent","6":"Kent","last_name":"Yuan","7":"Yuan","releases":[{"0":"4516","vim_version":"7.3","1":"7.3","script_version":"1.0.1","2":"1.0.1","version_comment":"version 1.0.1  2013-11-07~\r\n- move vim codes to autoload\r\n- rename function names","3":"version 1.0.1  2013-11-07~\r\n- move vim codes to autoload\r\n- rename function names","package":"Join.tar.gz","4":"Join.tar.gz","src_id":"21013","5":"21013","creation_date":"1383847016","6":"1383847016"},{"0":"4516","vim_version":"7.3","1":"7.3","script_version":"1.0.0","2":"1.0.0","version_comment":"Initial upload","3":"Initial upload","package":"Join.tar.gz","4":"Join.tar.gz","src_id":"19791","5":"19791","creation_date":"1365524814","6":"1365524814"}]},"4515":{"script_id":"4515","0":"4515","script_name":"tornadotmpl.vim","1":"tornadotmpl.vim","script_type":"syntax","2":"syntax","summary":"syntax highlight for Python's Tornado templates.","3":"syntax highlight for Python's Tornado templates.","description":"This is a syntax highlight file for Tornado's templates: http:\/\/www.tornadoweb.org\/en\/stable\/template.html . Tornado is a web framework written in Python.\r\n\r\nTo use it, add something like the following in modeline to your templates:\r\n\r\n{# vim:se syntax=html.tornadotmpl: #}\r\n\r\nOr set the appropriate 'syntax' in some autocmd suitable for you.","4":"This is a syntax highlight file for Tornado's templates: http:\/\/www.tornadoweb.org\/en\/stable\/template.html . Tornado is a web framework written in Python.\r\n\r\nTo use it, add something like the following in modeline to your templates:\r\n\r\n{# vim:se syntax=html.tornadotmpl: #}\r\n\r\nOr set the appropriate 'syntax' in some autocmd suitable for you.","install_details":"drop it into your ~\/.vim\/syntax directory.","5":"drop it into your ~\/.vim\/syntax directory.","first_name":"lilydjwg","6":"lilydjwg","last_name":" ","7":" ","releases":[{"0":"4515","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"tornadotmpl.vim","4":"tornadotmpl.vim","src_id":"19788","5":"19788","creation_date":"1365497898","6":"1365497898"}]},"4514":{"script_id":"4514","0":"4514","script_name":"forest","1":"forest","script_type":"color scheme","2":"color scheme","summary":"Light background color scheme with earthy colors.","3":"Light background color scheme with earthy colors.","description":"Along the same lines as fruit, but with forest colors.","4":"Along the same lines as fruit, but with forest colors.","install_details":"Copy forest.vim to your ~\/.vim\/colors directory and use with :colors forest\r\n","5":"Copy forest.vim to your ~\/.vim\/colors directory and use with :colors forest\r\n","first_name":"Fox","6":"Fox","last_name":"Donut","7":"Donut","releases":[{"0":"4514","vim_version":"7.0","1":"7.0","script_version":"1.1","2":"1.1","version_comment":"Correction to uploaded file.","3":"Correction to uploaded file.","package":"forest.vim","4":"forest.vim","src_id":"19782","5":"19782","creation_date":"1365424963","6":"1365424963"}]},"4513":{"script_id":"4513","0":"4513","script_name":"haml instant","1":"haml instant","script_type":"ftplugin","2":"ftplugin","summary":"haml to html instant preview inside vim","3":"haml to html instant preview inside vim","description":"compile haml to html instantly in vim \r\n\r\nproject hosted on github\r\nhttps:\/\/github.com\/michalliu\/haml-instant","4":"compile haml to html instantly in vim \r\n\r\nproject hosted on github\r\nhttps:\/\/github.com\/michalliu\/haml-instant","install_details":"You need a tool to convert haml to html file. The official one is haml gem. And a js version developed by Tim Caswell.Haml-instant supports both of them.\r\n\r\nTo install the official one, please execute gem install haml in your console\r\nTo install the js version, please checkout and install them to your vim\r\njsruntime\r\njsoncodecs\r\nIf both of them is installed. The js version will takes precedence in Windows system, ruby version in *nix and mac.","5":"You need a tool to convert haml to html file. The official one is haml gem. And a js version developed by Tim Caswell.Haml-instant supports both of them.\r\n\r\nTo install the official one, please execute gem install haml in your console\r\nTo install the js version, please checkout and install them to your vim\r\njsruntime\r\njsoncodecs\r\nIf both of them is installed. The js version will takes precedence in Windows system, ruby version in *nix and mac.","first_name":"yf","6":"yf","last_name":"liu","7":"liu","releases":[{"0":"4513","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"haml-instant.zip","4":"haml-instant.zip","src_id":"19773","5":"19773","creation_date":"1365324099","6":"1365324099"}]},"4512":{"script_id":"4512","0":"4512","script_name":"thwins","1":"thwins","script_type":"utility","2":"utility","summary":"Keep Vim Displaying Three Windows","3":"Keep Vim Displaying Three Windows","description":"Windows are always organized as follows:\r\n\r\n===================\r\n|                  |        S1       |\r\n|    Main      |==========\r\n|                  |        S2       |\r\n===================\r\n\r\nMapped Keys:\r\n\r\n<C-H> Make the current buffer as the main window\r\n<C-L> Make current buffer displayed as full screen\r\n<C-C> Delete current buffer\r\n<C-D> Close all buffers except the current one\r\n<C-J> Move cursor to next buffer\r\n<C-K> Move cursor to previous buffer\r\n\r\nPriority Rules for Buffers\r\n\r\nCurrent > Main > Displayed > New opened > Others\r\n\r\nIssues: https:\/\/github.com\/mitnk\/thwins","4":"Windows are always organized as follows:\r\n\r\n===================\r\n|                  |        S1       |\r\n|    Main      |==========\r\n|                  |        S2       |\r\n===================\r\n\r\nMapped Keys:\r\n\r\n<C-H> Make the current buffer as the main window\r\n<C-L> Make current buffer displayed as full screen\r\n<C-C> Delete current buffer\r\n<C-D> Close all buffers except the current one\r\n<C-J> Move cursor to next buffer\r\n<C-K> Move cursor to previous buffer\r\n\r\nPriority Rules for Buffers\r\n\r\nCurrent > Main > Displayed > New opened > Others\r\n\r\nIssues: https:\/\/github.com\/mitnk\/thwins","install_details":"$ cp thwins.vim ~\/.vim\/plugin\/\r\n","5":"$ cp thwins.vim ~\/.vim\/plugin\/\r\n","first_name":"Hugo","6":"Hugo","last_name":"Wang","7":"Wang","releases":[{"0":"4512","vim_version":"7.0","1":"7.0","script_version":"0.1.1","2":"0.1.1","version_comment":"Improved events handle for BufEnter \/ BufLeave.","3":"Improved events handle for BufEnter \/ BufLeave.","package":"thwins.vim","4":"thwins.vim","src_id":"22629","5":"22629","creation_date":"1416451460","6":"1416451460"},{"0":"4512","vim_version":"7.0","1":"7.0","script_version":"0.1.0","2":"0.1.0","version_comment":"Initial upload","3":"Initial upload","package":"thwins.vim","4":"thwins.vim","src_id":"19772","5":"19772","creation_date":"1365306014","6":"1365306014"}]},"4511":{"script_id":"4511","0":"4511","script_name":"vim-ember-script","1":"vim-ember-script","script_type":"syntax","2":"syntax","summary":"Adds ember-script support to vim.","3":"Adds ember-script support to vim.","description":"`vim-ember-script` adds ember-script (http:\/\/emberscript.com\/) support to vim.\r\n\r\nFeatures:\r\n\r\n* detects `*.em` files as `ember-script`\r\n* sets standard coding style (two-space indentation)\r\n* smart indentation\r\n* syntax highlighting\r\n\r\nProject page: https:\/\/github.com\/heartsentwined\/vim-ember-script","4":"`vim-ember-script` adds ember-script (http:\/\/emberscript.com\/) support to vim.\r\n\r\nFeatures:\r\n\r\n* detects `*.em` files as `ember-script`\r\n* sets standard coding style (two-space indentation)\r\n* smart indentation\r\n* syntax highlighting\r\n\r\nProject page: https:\/\/github.com\/heartsentwined\/vim-ember-script","install_details":"Vundle and Pathogen compatible, or manual install (extract files) to `~\/.vim` \/ `$HOME\\vimfiles`.\r\n\r\n`vim-ember-script` expects vim-coffee-script (vimscript #3590) to be present. Make sure you install it too.\r\n\r\nDetailed installation instructions at project page: https:\/\/github.com\/heartsentwined\/vim-ember-script","5":"Vundle and Pathogen compatible, or manual install (extract files) to `~\/.vim` \/ `$HOME\\vimfiles`.\r\n\r\n`vim-ember-script` expects vim-coffee-script (vimscript #3590) to be present. Make sure you install it too.\r\n\r\nDetailed installation instructions at project page: https:\/\/github.com\/heartsentwined\/vim-ember-script","first_name":"hearts","6":"hearts","last_name":"entwined","7":"entwined","releases":[{"0":"4511","vim_version":"6.0","1":"6.0","script_version":"1.0.1","2":"1.0.1","version_comment":"use semver; minor fixes","3":"use semver; minor fixes","package":"vim-ember-script-1.0.1.zip","4":"vim-ember-script-1.0.1.zip","src_id":"19830","5":"19830","creation_date":"1366162573","6":"1366162573"},{"0":"4511","vim_version":"6.0","1":"6.0","script_version":"1.0.0","2":"1.0.0","version_comment":"Initial upload","3":"Initial upload","package":"vim-ember-script.zip","4":"vim-ember-script.zip","src_id":"19770","5":"19770","creation_date":"1365301873","6":"1365301873"}]},"4510":{"script_id":"4510","0":"4510","script_name":"HLPSL","1":"HLPSL","script_type":"patch","2":"patch","summary":"HLPSL plugin for GVim","3":"HLPSL plugin for GVim","description":" this is a plugin for hlpsl ,which is  a lauguage for specifying security protocols . The home page of this lauguage is www.avispa-project.org\/\r\n\r\nhotkeys :\r\n <leader>cc   comment one line  \r\n <leader>cu   cancel   one line comment\r\n <leader>qe   add comment at end of line\r\n\r\nlinux:\r\n  <F7> :call HLPSL_hlpsl2html() \r\n  <F8> :call HLPSL_hlpsl2htmlArguments() \r\n  <F9> :call HLPSL_hlpsl2latex() \r\n  <F10> :call HLPSL_hlpsl2latexArguments() \r\n  <F11> :call HLPSL_avispa() \r\n  <F12> :call HLPSL_avispaArguments() \r\n\r\n windows:\r\n   <F5> :call HLPSL_Ofmc() \r\n   <F6> :call HLPSL_OfmcArguments(usage: ofmc <IF File> [-theory <Theory file>] [-sessco] [-untyped] [-d <DEPTH>]\r\n[-p <PATH>]) \r\n   <F7> :call HLPSL_Clatse() \r\n   <F8> :call HLPSL_ClatseArguments(usage: clatse : -nb n -light-notype -short -out -dir d  -ns -noopt -v -col n -bench ) ","4":" this is a plugin for hlpsl ,which is  a lauguage for specifying security protocols . The home page of this lauguage is www.avispa-project.org\/\r\n\r\nhotkeys :\r\n <leader>cc   comment one line  \r\n <leader>cu   cancel   one line comment\r\n <leader>qe   add comment at end of line\r\n\r\nlinux:\r\n  <F7> :call HLPSL_hlpsl2html() \r\n  <F8> :call HLPSL_hlpsl2htmlArguments() \r\n  <F9> :call HLPSL_hlpsl2latex() \r\n  <F10> :call HLPSL_hlpsl2latexArguments() \r\n  <F11> :call HLPSL_avispa() \r\n  <F12> :call HLPSL_avispaArguments() \r\n\r\n windows:\r\n   <F5> :call HLPSL_Ofmc() \r\n   <F6> :call HLPSL_OfmcArguments(usage: ofmc <IF File> [-theory <Theory file>] [-sessco] [-untyped] [-d <DEPTH>]\r\n[-p <PATH>]) \r\n   <F7> :call HLPSL_Clatse() \r\n   <F8> :call HLPSL_ClatseArguments(usage: clatse : -nb n -light-notype -short -out -dir d  -ns -noopt -v -col n -bench ) ","install_details":"drop it to vimfiles or .vim \r\n\r\n","5":"drop it to vimfiles or .vim \r\n\r\n","first_name":"xing","6":"xing","last_name":"chao","7":"chao","releases":[{"0":"4510","vim_version":"7.0","1":"7.0","script_version":"7.0","2":"7.0","version_comment":"run ofmc clatse in windows ","3":"run ofmc clatse in windows ","package":"hlpsl.zip","4":"hlpsl.zip","src_id":"20192","5":"20192","creation_date":"1369174734","6":"1369174734"},{"0":"4510","vim_version":"7.0","1":"7.0","script_version":"6.0","2":"6.0","version_comment":"Initial upload","3":"Initial upload","package":"hlpsl-gvim.zip","4":"hlpsl-gvim.zip","src_id":"19769","5":"19769","creation_date":"1365282249","6":"1365282249"}]},"4509":{"script_id":"4509","0":"4509","script_name":"TLA+","1":"TLA+","script_type":"patch","2":"patch","summary":"TLA+ plugin for Gvim","3":"TLA+ plugin for Gvim","description":" this is a plugin for TLA+ language,although TLA+ toolbox already exists,but it is fun to create this .for more information about this lauguage ,access www.lamport.org\r\n\r\nthe hotkeys as follows:\r\n <leader>gi IF-THEN-ELSE    \r\n <leader>ga CASE \r\n <leader>go CASE-OTHER \r\n <leader>glc LET IN \/\\...\/\\ \r\n <leader>gld LET IN \\\/...\\\/ \r\n\r\n <leader>cc  comments one line  \r\n <leader>cu  cancelthe comments of one line  \r\n <leader>qp comments paragraph\r\n <leader>qe comments in the end of one line\r\n\r\n <F5>  TLA_Tla2Tex()\r\n <F6>  TLA_Tla2TexArguments()(-ptSize -textwidth -textheight)\r\n <F7>   pcal.trans \r\n <F8>   pcal.trans with  Arguments()\r\n <F9>   tla2sany.SANY\r\n <F10>  tla2sany.SANY with  Arguments(-s ,-d)\r\n <F11>  tlc2.TLC\r\n <F12>  tlc2.TLC with Arguments(-deadlock -simulate -depth -seed -aril -coverage -recover -cleanup -difftrace -terse -workers -config -nowarning )","4":" this is a plugin for TLA+ language,although TLA+ toolbox already exists,but it is fun to create this .for more information about this lauguage ,access www.lamport.org\r\n\r\nthe hotkeys as follows:\r\n <leader>gi IF-THEN-ELSE    \r\n <leader>ga CASE \r\n <leader>go CASE-OTHER \r\n <leader>glc LET IN \/\\...\/\\ \r\n <leader>gld LET IN \\\/...\\\/ \r\n\r\n <leader>cc  comments one line  \r\n <leader>cu  cancelthe comments of one line  \r\n <leader>qp comments paragraph\r\n <leader>qe comments in the end of one line\r\n\r\n <F5>  TLA_Tla2Tex()\r\n <F6>  TLA_Tla2TexArguments()(-ptSize -textwidth -textheight)\r\n <F7>   pcal.trans \r\n <F8>   pcal.trans with  Arguments()\r\n <F9>   tla2sany.SANY\r\n <F10>  tla2sany.SANY with  Arguments(-s ,-d)\r\n <F11>  tlc2.TLC\r\n <F12>  tlc2.TLC with Arguments(-deadlock -simulate -depth -seed -aril -coverage -recover -cleanup -difftrace -terse -workers -config -nowarning )","install_details":"copy to vimfiles or .vim\r\nedit  TLA_PATH in  syntax\\tla.vim  as the tla's path  ,default is c:\\tla \r\nmake sure pdflatex is in PATH to use TLATEX Typesetter\r\n\r\n\r\n\r\n","5":"copy to vimfiles or .vim\r\nedit  TLA_PATH in  syntax\\tla.vim  as the tla's path  ,default is c:\\tla \r\nmake sure pdflatex is in PATH to use TLATEX Typesetter\r\n\r\n\r\n\r\n","first_name":"xing","6":"xing","last_name":"chao","7":"chao","releases":[{"0":"4509","vim_version":"7.0","1":"7.0","script_version":"7.0","2":"7.0","version_comment":"add TLATEX Typesetter","3":"add TLATEX Typesetter","package":"tla+-gvim.zip","4":"tla+-gvim.zip","src_id":"20137","5":"20137","creation_date":"1368550854","6":"1368550854"}]},"4508":{"script_id":"4508","0":"4508","script_name":"pytest-compiler","1":"pytest-compiler","script_type":"utility","2":"utility","summary":"compiler plugin for py.test","3":"compiler plugin for py.test","description":"Provides `:compiler pytest` to work with Vim's `:make` command and plugins like MakeGreen: https:\/\/github.com\/reinh\/vim-makegreen\r\n\r\nIf you don't know this `:make` thingy, see `:help quickfix` to get started.\r\n\r\nFor any feedback, feel free to open an issue at https:\/\/github.com\/5long\/pytest-vim-compiler\/issues","4":"Provides `:compiler pytest` to work with Vim's `:make` command and plugins like MakeGreen: https:\/\/github.com\/reinh\/vim-makegreen\r\n\r\nIf you don't know this `:make` thingy, see `:help quickfix` to get started.\r\n\r\nFor any feedback, feel free to open an issue at https:\/\/github.com\/5long\/pytest-vim-compiler\/issues","install_details":"Download the .zip package and extract it to your $VIMRUNTIME directory which would be ~\/.vim on UNIXy systems.\r\n\r\nOr, If you're using tools like Pathogen \/ Vundle, the github repository is https:\/\/github.com\/5long\/pytest-vim-compiler","5":"Download the .zip package and extract it to your $VIMRUNTIME directory which would be ~\/.vim on UNIXy systems.\r\n\r\nOr, If you're using tools like Pathogen \/ Vundle, the github repository is https:\/\/github.com\/5long\/pytest-vim-compiler","first_name":"Whyme","6":"Whyme","last_name":"Lyu","7":"Lyu","releases":[{"0":"4508","vim_version":"6.0","1":"6.0","script_version":"0.6.0","2":"0.6.0","version_comment":"Include detailed multi-line error message as plain message\r\n","3":"Include detailed multi-line error message as plain message\r\n","package":"pytest-compiler-v0.6.0.zip","4":"pytest-compiler-v0.6.0.zip","src_id":"20597","5":"20597","creation_date":"1375544598","6":"1375544598"},{"0":"4508","vim_version":"6.0","1":"6.0","script_version":"0.5.1","2":"0.5.1","version_comment":"Remove underscores from header message\r\n","3":"Remove underscores from header message\r\n","package":"pytest-compiler-v0.5.1.zip","4":"pytest-compiler-v0.5.1.zip","src_id":"20550","5":"20550","creation_date":"1374317821","6":"1374317821"},{"0":"4508","vim_version":"6.0","1":"6.0","script_version":"0.5.0","2":"0.5.0","version_comment":"Don't mark messages as error","3":"Don't mark messages as error","package":"pytest-compiler-v0.5.0.zip","4":"pytest-compiler-v0.5.0.zip","src_id":"20547","5":"20547","creation_date":"1374304194","6":"1374304194"},{"0":"4508","vim_version":"6.0","1":"6.0","script_version":"0.4.0","2":"0.4.0","version_comment":"* Full stacktrace is now included\r\n* Include a header message for each test failure","3":"* Full stacktrace is now included\r\n* Include a header message for each test failure","package":"pytest-compiler-v0.4.0.zip","4":"pytest-compiler-v0.4.0.zip","src_id":"20546","5":"20546","creation_date":"1374303597","6":"1374303597"},{"0":"4508","vim_version":"6.0","1":"6.0","script_version":"0.3.1","2":"0.3.1","version_comment":"Just use -q","3":"Just use -q","package":"pytest-compiler-v0.3.1.zip","4":"pytest-compiler-v0.3.1.zip","src_id":"19842","5":"19842","creation_date":"1366257103","6":"1366257103"},{"0":"4508","vim_version":"6.0","1":"6.0","script_version":"0.3.0","2":"0.3.0","version_comment":"Ignore unparsed lines","3":"Ignore unparsed lines","package":"pytest-compiler-v0.3.0.zip","4":"pytest-compiler-v0.3.0.zip","src_id":"19824","5":"19824","creation_date":"1366124750","6":"1366124750"},{"0":"4508","vim_version":"6.0","1":"6.0","script_version":"0.2.0","2":"0.2.0","version_comment":"Error position should be within the test function","3":"Error position should be within the test function","package":"pytest-compiler-v0.2.0.zip","4":"pytest-compiler-v0.2.0.zip","src_id":"19790","5":"19790","creation_date":"1365514483","6":"1365514483"},{"0":"4508","vim_version":"6.0","1":"6.0","script_version":"0.1.0","2":"0.1.0","version_comment":"Initial upload","3":"Initial upload","package":"pytest-compiler-0.1.0.zip","4":"pytest-compiler-0.1.0.zip","src_id":"19767","5":"19767","creation_date":"1365270337","6":"1365270337"}]},"4507":{"script_id":"4507","0":"4507","script_name":"conflicts.vim","1":"conflicts.vim","script_type":"syntax","2":"syntax","summary":"Syntax for *.conflicts files","3":"Syntax for *.conflicts files","description":"Menhir (1) generates *.conflicts files when your grammar have some conflicts. This file allows you to have basic syntax highlighting when reading these files.\r\n\r\nProject home page: https:\/\/github.com\/bfontaine\/conflicts.vim\r\n\r\n\r\n[1]: http:\/\/gallium.inria.fr\/~fpottier\/menhir\/","4":"Menhir (1) generates *.conflicts files when your grammar have some conflicts. This file allows you to have basic syntax highlighting when reading these files.\r\n\r\nProject home page: https:\/\/github.com\/bfontaine\/conflicts.vim\r\n\r\n\r\n[1]: http:\/\/gallium.inria.fr\/~fpottier\/menhir\/","install_details":"Copy the file into ~\/.vim\/syntax\/, then add this line in your .vimrc:\r\n au BufNewFile,BufRead *.conflicts set ft=conflicts","5":"Copy the file into ~\/.vim\/syntax\/, then add this line in your .vimrc:\r\n au BufNewFile,BufRead *.conflicts set ft=conflicts","first_name":"Baptiste","6":"Baptiste","last_name":"Fontaine","7":"Fontaine","releases":[{"0":"4507","vim_version":"7.0","1":"7.0","script_version":"0.1.1","2":"0.1.1","version_comment":"Tokens can contain lower case letters, digits and underscores after the first character.","3":"Tokens can contain lower case letters, digits and underscores after the first character.","package":"conflicts.vim","4":"conflicts.vim","src_id":"19765","5":"19765","creation_date":"1365260527","6":"1365260527"},{"0":"4507","vim_version":"7.0","1":"7.0","script_version":"0.1.0","2":"0.1.0","version_comment":"Initial upload","3":"Initial upload","package":"conflicts.vim","4":"conflicts.vim","src_id":"19764","5":"19764","creation_date":"1365199545","6":"1365199545"}]},"4506":{"script_id":"4506","0":"4506","script_name":"textobj-latex","1":"textobj-latex","script_type":"ftplugin","2":"ftplugin","summary":"Text objects for LaTeX code","3":"Text objects for LaTeX code","description":"This plugin provides text objects for common LaTeX stuff that are not\r\nconveniently described by builtin Vim text-objects.\r\n\r\ntextobj-latex depends on Kana's textobj-user plugin (vimscript #2100).\r\n\r\nProject site: https:\/\/github.com\/rbonvall\/vim-textobj-latex","4":"This plugin provides text objects for common LaTeX stuff that are not\r\nconveniently described by builtin Vim text-objects.\r\n\r\ntextobj-latex depends on Kana's textobj-user plugin (vimscript #2100).\r\n\r\nProject site: https:\/\/github.com\/rbonvall\/vim-textobj-latex","install_details":"Follow the instructions at https:\/\/github.com\/rbonvall\/vim-textobj-latex\/blob\/master\/doc\/textobj-latex.txt","5":"Follow the instructions at https:\/\/github.com\/rbonvall\/vim-textobj-latex\/blob\/master\/doc\/textobj-latex.txt","first_name":"Roberto","6":"Roberto","last_name":"Bonvallet","7":"Bonvallet","releases":[{"0":"4506","vim_version":"7.0","1":"7.0","script_version":"0.90","2":"0.90","version_comment":"Initial upload","3":"Initial upload","package":"vim-textobj-latex-v0.90.zip","4":"vim-textobj-latex-v0.90.zip","src_id":"19763","5":"19763","creation_date":"1365188053","6":"1365188053"}]},"4505":{"script_id":"4505","0":"4505","script_name":"autohide","1":"autohide","script_type":"utility","2":"utility","summary":"Set 'hidden' attribute on swap files and the like in Windows","3":"Set 'hidden' attribute on swap files and the like in Windows","description":"A simple plugin to set the \"hidden\" filesystem attribute on a\r\nWindows system for files created by Vim. By default only nuisance files\r\ncreated by Vim automatically due to user settings are hidden. The user can\r\nconfigure the plugin to hide more files automatically, even files directly\r\ncreated by the user.\r\n\r\nThere are three options for the autohide plugin:\r\n\r\n*g:autohide_types* (default \"suv\")\r\n  b = backup files (currently doesn't work with 'backupdir')\r\n  s = swap files\r\n  u = undo files\r\n  v = viminfo\r\n  p = files matching pattern\r\n\r\n*g:autohide_file_list* (default [.*])\r\n  List of file patterns to hide when 'p' is part of |g:autohide_tipes|.\r\n  This is a wildcard, not a regular expression. So the default .* matches not\r\n  \"any characters\" but rather \"file names starting with a . character\". Set\r\n  this option to a |List| of wildcards for files you want Vim to hide while\r\n  you are editing.\r\n\r\n*g:autohide_max_wait_for_write* (default 2)\r\n  Maximum number of seconds to wait for the file being hidden to become\r\n  writable before giving up. Useful for network file systems where the undo\r\n  file especially may take a while to show as writable. Set to zero or less to\r\n  never wait.\r\n\r\nThere is also one public function if you want to hide files in ways the plugin\r\ndoesn't support yet:\r\n\r\nAutohide_DoHide({file})                                     *Autohide_DoHide()*\r\n  Sets the \"hidden\" filesystem attribute on {file}. Will properly escape the\r\n  file name before shelling out, so you shouldn't need to do that yourself.\r\n\r\nRepository (Mercurial): https:\/\/sourceforge.net\/projects\/vim-autohide-plugin\/","4":"A simple plugin to set the \"hidden\" filesystem attribute on a\r\nWindows system for files created by Vim. By default only nuisance files\r\ncreated by Vim automatically due to user settings are hidden. The user can\r\nconfigure the plugin to hide more files automatically, even files directly\r\ncreated by the user.\r\n\r\nThere are three options for the autohide plugin:\r\n\r\n*g:autohide_types* (default \"suv\")\r\n  b = backup files (currently doesn't work with 'backupdir')\r\n  s = swap files\r\n  u = undo files\r\n  v = viminfo\r\n  p = files matching pattern\r\n\r\n*g:autohide_file_list* (default [.*])\r\n  List of file patterns to hide when 'p' is part of |g:autohide_tipes|.\r\n  This is a wildcard, not a regular expression. So the default .* matches not\r\n  \"any characters\" but rather \"file names starting with a . character\". Set\r\n  this option to a |List| of wildcards for files you want Vim to hide while\r\n  you are editing.\r\n\r\n*g:autohide_max_wait_for_write* (default 2)\r\n  Maximum number of seconds to wait for the file being hidden to become\r\n  writable before giving up. Useful for network file systems where the undo\r\n  file especially may take a while to show as writable. Set to zero or less to\r\n  never wait.\r\n\r\nThere is also one public function if you want to hide files in ways the plugin\r\ndoesn't support yet:\r\n\r\nAutohide_DoHide({file})                                     *Autohide_DoHide()*\r\n  Sets the \"hidden\" filesystem attribute on {file}. Will properly escape the\r\n  file name before shelling out, so you shouldn't need to do that yourself.\r\n\r\nRepository (Mercurial): https:\/\/sourceforge.net\/projects\/vim-autohide-plugin\/","install_details":"New way: Unzip into $HOME\/vimfiles\/pack\/your_arbitrary_name_here\/start\/autohide\r\n\r\nOld way: Unzip each directory into the corresponding directory in your $HOME\/vimfiles directory, or unzip the whole thing into your $HOME\/vimfiles\/bundle directory as usual if you use Pathogen.","5":"New way: Unzip into $HOME\/vimfiles\/pack\/your_arbitrary_name_here\/start\/autohide\r\n\r\nOld way: Unzip each directory into the corresponding directory in your $HOME\/vimfiles directory, or unzip the whole thing into your $HOME\/vimfiles\/bundle directory as usual if you use Pathogen.","first_name":"Ben","6":"Ben","last_name":"Fritz","7":"Fritz","releases":[{"0":"4505","vim_version":"7.0","1":"7.0","script_version":"5","2":"5","version_comment":"Fix backup files not properly hidden when the file has an extension.","3":"Fix backup files not properly hidden when the file has an extension.","package":"autohide_v5.zip","4":"autohide_v5.zip","src_id":"26698","5":"26698","creation_date":"1565694989","6":"1565694989"},{"0":"4505","vim_version":"7.0","1":"7.0","script_version":"4","2":"4","version_comment":"Use \"very no magic\" to match file names literally in 'p' type","3":"Use \"very no magic\" to match file names literally in 'p' type","package":"autohide_v4.zip","4":"autohide_v4.zip","src_id":"20758","5":"20758","creation_date":"1378436393","6":"1378436393"},{"0":"4505","vim_version":"7.0","1":"7.0","script_version":"3","2":"3","version_comment":"Fix bug in pattern matching when shellslash not set.\r\nAllow hiding files on slow network locations with a configurable delay.","3":"Fix bug in pattern matching when shellslash not set.\r\nAllow hiding files on slow network locations with a configurable delay.","package":"autohide_v3.zip","4":"autohide_v3.zip","src_id":"20305","5":"20305","creation_date":"1370485115","6":"1370485115"},{"0":"4505","vim_version":"7.0","1":"7.0","script_version":"2","2":"2","version_comment":"Add hiding of user-specified file patters on write","3":"Add hiding of user-specified file patters on write","package":"autohide_v2.zip","4":"autohide_v2.zip","src_id":"19771","5":"19771","creation_date":"1365304978","6":"1365304978"},{"0":"4505","vim_version":"7.0","1":"7.0","script_version":"1","2":"1","version_comment":"Initial upload","3":"Initial upload","package":"autohide_v1.zip","4":"autohide_v1.zip","src_id":"19756","5":"19756","creation_date":"1364994042","6":"1364994042"}]},"4504":{"script_id":"4504","0":"4504","script_name":"dispatch.vim","1":"dispatch.vim","script_type":"utility","2":"utility","summary":"Asynchronous build and test dispatcher","3":"Asynchronous build and test dispatcher","description":"Leverage the power of Vim's compiler plugins without being bound by synchronicity.  Kick off builds and test suites using one of several asynchronous adapters (including tmux, screen, iTerm, Windows, and a headless mode), and when the job completes, errors will be loaded and parsed automatically.\r\n\r\nDetails:\r\n\r\nhttps:\/\/github.com\/tpope\/vim-dispatch#readme\r\n\r\nWatch a video:\r\n\r\nhttps:\/\/vimeo.com\/tpope\/vim-dispatch-teaser","4":"Leverage the power of Vim's compiler plugins without being bound by synchronicity.  Kick off builds and test suites using one of several asynchronous adapters (including tmux, screen, iTerm, Windows, and a headless mode), and when the job completes, errors will be loaded and parsed automatically.\r\n\r\nDetails:\r\n\r\nhttps:\/\/github.com\/tpope\/vim-dispatch#readme\r\n\r\nWatch a video:\r\n\r\nhttps:\/\/vimeo.com\/tpope\/vim-dispatch-teaser","install_details":"Extract in ~\/.vim (~\\vimfiles on Windows).","5":"Extract in ~\/.vim (~\\vimfiles on Windows).","first_name":"Tim","6":"Tim","last_name":"Pope","7":"Pope","releases":[{"0":"4504","vim_version":"7.0","1":"7.0","script_version":"1.8","2":"1.8","version_comment":"Support :vert Copen and other mods.\r\nProvide options for partially disabling strategies.\r\nBug fixes.","3":"Support :vert Copen and other mods.\r\nProvide options for partially disabling strategies.\r\nBug fixes.","package":"dispatch.zip","4":"dispatch.zip","src_id":"26528","5":"26528","creation_date":"1560085296","6":"1560085296"},{"0":"4504","vim_version":"7.0","1":"7.0","script_version":"1.7","2":"1.7","version_comment":"Support force killing a dispatch with :AbortDispatch!.\r\nSupport Fish shell.\r\nInvoke ShellCmdPost and :checktime on completion.\r\nBug fixes.","3":"Support force killing a dispatch with :AbortDispatch!.\r\nSupport Fish shell.\r\nInvoke ShellCmdPost and :checktime on completion.\r\nBug fixes.","package":"dispatch.zip","4":"dispatch.zip","src_id":"26405","5":"26405","creation_date":"1551420723","6":"1551420723"},{"0":"4504","vim_version":"7.0","1":"7.0","script_version":"1.6","2":"1.6","version_comment":"Provide maps for :Make, :Dispatch, :Start, and :Spawn.\r\nProvide :AbortDispatch.\r\nEnable :Dispatch -- to run :Make directly.\r\nSupport :{range}Spawn to interactively spawn default dispatch.\r\nSupport %:S to shell escape filename.\r\nUse job support plus FIFO for callback when dispatch completes.\r\nBug fixes and robustness improvements.","3":"Provide maps for :Make, :Dispatch, :Start, and :Spawn.\r\nProvide :AbortDispatch.\r\nEnable :Dispatch -- to run :Make directly.\r\nSupport :{range}Spawn to interactively spawn default dispatch.\r\nSupport %:S to shell escape filename.\r\nUse job support plus FIFO for callback when dispatch completes.\r\nBug fixes and robustness improvements.","package":"dispatch.zip","4":"dispatch.zip","src_id":"26157","5":"26157","creation_date":"1533131879","6":"1533131879"},{"0":"4504","vim_version":"7.0","1":"7.0","script_version":"1.5","2":"1.5","version_comment":"Provide m maps for :Make.\r\nShow :Dispatch command in quickfix title.\r\nInclude handler\/pid in summary and quickfix title.\r\nClear and claim quickfix list immediately after :Dispatch.\r\nOpen quickfix window with dispatched working directory.\r\nAccept :FocusDispatch :.Dispatch to focus buffer default.\r\nAllow configuration of size of quickfix window (and tmux panel).\r\nAuto-write before :Start, :Spawn, and :Dispatch :vimcommand.\r\nStore global focused command in session.\r\nSupport iTerm 3.\r\nEnable X11 terminal flags other than -e.\r\nAssorted bug fixes.","3":"Provide m maps for :Make.\r\nShow :Dispatch command in quickfix title.\r\nInclude handler\/pid in summary and quickfix title.\r\nClear and claim quickfix list immediately after :Dispatch.\r\nOpen quickfix window with dispatched working directory.\r\nAccept :FocusDispatch :.Dispatch to focus buffer default.\r\nAllow configuration of size of quickfix window (and tmux panel).\r\nAuto-write before :Start, :Spawn, and :Dispatch :vimcommand.\r\nStore global focused command in session.\r\nSupport iTerm 3.\r\nEnable X11 terminal flags other than -e.\r\nAssorted bug fixes.","package":"dispatch.zip","4":"dispatch.zip","src_id":"25907","5":"25907","creation_date":"1522556216","6":"1522556216"},{"0":"4504","vim_version":"7.0","1":"7.0","script_version":"1.4","2":"1.4","version_comment":"Show success\/failure (zero\/nonzero) exit status on completion.\r\nAlways open quickfix on failure exit status.\r\nPause after :Start failure exit status.\r\nSupport :Start -wait= for exit pause control.\r\nAdd make support to X11 handler.\r\nSet window title in tmux panes.\r\nAllow tmux completion to call other autocommands.\r\nFix X11 adapter in terminal with foreground :Make.\r\nSupport %< in makeprg string.\r\nDon't try to use clientserver support on Neovim.\r\nStrip `^O` from the output.\r\nFix focus after screen foreground :Dispatch.\r\nDrop interrupt special casing.","3":"Show success\/failure (zero\/nonzero) exit status on completion.\r\nAlways open quickfix on failure exit status.\r\nPause after :Start failure exit status.\r\nSupport :Start -wait= for exit pause control.\r\nAdd make support to X11 handler.\r\nSet window title in tmux panes.\r\nAllow tmux completion to call other autocommands.\r\nFix X11 adapter in terminal with foreground :Make.\r\nSupport %< in makeprg string.\r\nDon't try to use clientserver support on Neovim.\r\nStrip `^O` from the output.\r\nFix focus after screen foreground :Dispatch.\r\nDrop interrupt special casing.","package":"dispatch.zip","4":"dispatch.zip","src_id":"24152","5":"24152","creation_date":"1459551868","6":"1459551868"},{"0":"4504","vim_version":"7.0","1":"7.0","script_version":"1.3","2":"1.3","version_comment":"Support :Dispatch\/:Start -dir= to run in the given directory.\r\nSupport :Dispatch -compiler= to force compiler plugin.\r\nExpand `=vimexpr` in b:dispatch, with v:lnum set to :Dispatch's count.\r\nShow exact command that will run on :{count}FocusDispatch.\r\nUse g:completion_filter on completion results if available.\r\nMatch programs with dots in the name, e.g. \"py.test\".\r\nAvoid error on old Vim without haslocaldir().\r\nFix pid functions for cygwin shells.\r\nStrip out ^[[2K and ^[[0G in tmux output.","3":"Support :Dispatch\/:Start -dir= to run in the given directory.\r\nSupport :Dispatch -compiler= to force compiler plugin.\r\nExpand `=vimexpr` in b:dispatch, with v:lnum set to :Dispatch's count.\r\nShow exact command that will run on :{count}FocusDispatch.\r\nUse g:completion_filter on completion results if available.\r\nMatch programs with dots in the name, e.g. \"py.test\".\r\nAvoid error on old Vim without haslocaldir().\r\nFix pid functions for cygwin shells.\r\nStrip out ^[[2K and ^[[0G in tmux output.","package":"dispatch.zip","4":"dispatch.zip","src_id":"23267","5":"23267","creation_date":"1431053091","6":"1431053091"},{"0":"4504","vim_version":"7.0","1":"7.0","script_version":"1.2","2":"1.2","version_comment":"Make :Start idempotent, finding existing process if running.\r\nProvide :Spawn with :Start's old, non-idempotent behavior.\r\nShow PID of created process.\r\nEnable compiler plugins to provide custom completion.\r\nAllow :0Dispatch to bypass focus.\r\nStrip out ^[[K and progress bars in tmux output.\r\nDon't tmux pipe-pane if error format targets \\r or \\e.\r\nUse wmctrl if available to enable X11 :Start!.\r\nUse :cwindow semantics when opening\/closing quickfix window.\r\nRemove catch-all ignores from error formats.\r\nShow shell command not Vim command in \"Finished\" message.\r\nAdd QuickFixCmdPre cgetfile event.\r\nAdd QuickFix dispatch-make events.\r\nDon't fire modelines for QuickFix events.\r\nFix shell escaping of exported bash functions.\r\nFix output of :Focus when focused on Vim command.","3":"Make :Start idempotent, finding existing process if running.\r\nProvide :Spawn with :Start's old, non-idempotent behavior.\r\nShow PID of created process.\r\nEnable compiler plugins to provide custom completion.\r\nAllow :0Dispatch to bypass focus.\r\nStrip out ^[[K and progress bars in tmux output.\r\nDon't tmux pipe-pane if error format targets \\r or \\e.\r\nUse wmctrl if available to enable X11 :Start!.\r\nUse :cwindow semantics when opening\/closing quickfix window.\r\nRemove catch-all ignores from error formats.\r\nShow shell command not Vim command in \"Finished\" message.\r\nAdd QuickFixCmdPre cgetfile event.\r\nAdd QuickFix dispatch-make events.\r\nDon't fire modelines for QuickFix events.\r\nFix shell escaping of exported bash functions.\r\nFix output of :Focus when focused on Vim command.","package":"dispatch.zip","4":"dispatch.zip","src_id":"22206","5":"22206","creation_date":"1405378740","6":"1405378740"},{"0":"4504","vim_version":"7.0","1":"7.0","script_version":"1.1","2":"1.1","version_comment":"Force quickfix window to very bottom.\r\nFire a QuickFixCmdPost event after loading results.\r\nSet xterm title with screen and tmux.\r\nTweak screen adapter for wider version and distribution support.\r\nDefault :Start to b:start.\r\nEnsure identical environment vars (fixing in particular RVM support).\r\nAllow greater compiler detection control with g:dispatch_compilers.\r\nEnhance and fix bugs in compiler detection.\r\nDon't launch iTerm if not already running.\r\nNumerous small bug fixes.","3":"Force quickfix window to very bottom.\r\nFire a QuickFixCmdPost event after loading results.\r\nSet xterm title with screen and tmux.\r\nTweak screen adapter for wider version and distribution support.\r\nDefault :Start to b:start.\r\nEnsure identical environment vars (fixing in particular RVM support).\r\nAllow greater compiler detection control with g:dispatch_compilers.\r\nEnhance and fix bugs in compiler detection.\r\nDon't launch iTerm if not already running.\r\nNumerous small bug fixes.","package":"dispatch.zip","4":"dispatch.zip","src_id":"21706","5":"21706","creation_date":"1396371323","6":"1396371323"},{"0":"4504","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"dispatch.zip","4":"dispatch.zip","src_id":"19747","5":"19747","creation_date":"1364860482","6":"1364860482"}]},"4503":{"script_id":"4503","0":"4503","script_name":"vim-xkbswitch","1":"vim-xkbswitch","script_type":"utility","2":"utility","summary":"Automatic Keyboard Layout Switcher","3":"Automatic Keyboard Layout Switcher","description":"About:\r\n\r\nVim plugin XkbSwitch can be used to easily switch current keyboard layout back\r\nand forth when entering and leaving Insert mode. Say you are typing some\r\ndocument in Russian and have to leave Insert mode: when you press <Esc> your\r\nkeyboard layout switches to US\/English automatically. When you further enter\r\nInsert mode once again the Russian keyboard layout will be automatically\r\nswitched back!\r\n\r\nXkbSwitch requires OS dependent keyboard layout switcher. Currently it depends\r\non xkb-switch (http:\/\/github.com\/ierton\/xkb-switch) for UNIX \/ X Server and\r\nxkb-switch-win (http:\/\/github.com\/DeXP\/xkb-switch-win) for Windows. \r\n\r\nFor Mac OS X you can try Input Source Switcher\r\n(http:\/\/github.com\/vovkasm\/input-source-switcher) and set library path as\r\n\r\n    let g:XkbSwitchLib = '\/usr\/local\/lib\/libInputSourceSwitcher.dylib'\r\n\r\nGnome 3 no longer works correctly with xkb-switch, so consider switching to\r\ng3kb-switch (https:\/\/github.com\/lyokha\/g3kb-switch) if you are using this\r\nenvironment. The library path should be set as\r\n\r\n    let g:XkbSwitchLib = '\/usr\/local\/lib\/libg3kbswitch.so'\r\n\r\ngithub: http:\/\/github.com\/lyokha\/vim-xkbswitch\r\n\r\n\r\nFeatures:\r\n\r\n  - Supported OS: UNIX \/ X Server, Windows, Mac OS X\r\n  - Switches keyboard layout when entering \/ leaving Insert and Select modes\r\n  - Keyboard layouts are stored separately for each buffer\r\n  - Keyboard layouts are kept intact while navigating between windows or\r\n    tabs without leaving Insert mode\r\n  - Automatic loading of language-friendly Insert mode mappings. For example\r\n    when Russian mappings have loaded then if there was a mapping\r\n\r\n    <C-G>S        <Plug>ISurround\r\n\r\n    a new mapping\r\n\r\n    <C-G>Ы        <Plug>ISurround\r\n\r\n    will be loaded. Insert mode mappings duplicates make it easy to apply\r\n    existing maps in Insert mode without switching current keyboard layout\r\n  - Fast and easy building of custom syntax based keyboard layout switching\r\n    rules in Insert mode\r\n\r\n\r\nConfiguration:\r\n\r\nBasic configuration requires only 1 line in your .vimrc:\r\n\r\n    let g:XkbSwitchEnabled = 1\r\n\r\nAdditionally path to the backend switcher library can be defined:\r\n\r\n    let g:XkbSwitchLib = '\/usr\/local\/lib\/libxkbswitch.so'\r\n\r\nHowever normally it is not necessary as far as the plugin is able to find it\r\nautomatically. To enable Insert mode mappings duplicates user may want to add\r\n\r\n    let g:XkbSwitchIMappings = ['ru']\r\n\r\nHere Insert mappings duplicates for Russian winkeys layout will be generated\r\nwhenever Insert mode is started. It is possible to define a list of different\r\nlayouts, for example\r\n\r\n    let g:XkbSwitchIMappings = ['ru', 'de']\r\n\r\nbut currently only Russian winkeys layout translation map ('ru') is supported\r\nout of the box. There are 2 ways how a user can provide extra definitions of\r\nkeyboard layout translation maps (or replace existing default 'ru' map):\r\n\r\n  - Define variable g:XkbSwitchIMappingsTr:\r\n\r\n    let g:XkbSwitchIMappingsTr = {\r\n                \\ 'ru':\r\n                \\ {'<': 'qwertyuiop[]asdfghjkl;''zxcvbnm,.`\/'.\r\n                \\       'QWERTYUIOP{}ASDFGHJKL:\"ZXCVBNM<>?~@#$^&|',\r\n                \\  '>': 'йцукенгшщзхъфывапролджэячсмитьбюё.'.\r\n                \\       'ЙЦУКЕНГШЩЗХЪФЫВАПРОЛДЖЭЯЧСМИТЬБЮ,Ё\"№;:?\/'},\r\n                \\ 'de':\r\n                \\ {'<': 'yz-[];''\/YZ{}:\"<>?~@#^&*_\\',\r\n                \\  '>': 'zy\u00c3\u009f\u00c3\u00bc+\u00c3\u00b6\u00c3\u00a4-ZY\u00c3\u009c*\u00c3\u0096\u00c3\u0084;:_\u00c2\u00b0\"\u00c2\u00a7&\/(?#'},\r\n                \\ }\r\n\r\n  - Create a file with layout translation maps and put its path into variable\r\n    g:XkbSwitchIMappingsTrData, for example:\r\n\r\n    let g:XkbSwitchIMappingsTrData = $HOME.'\/opt\/xkbswitch.tr'\r\n\r\n    File with maps must follow this format:\r\n\r\n  ru  Russian winkeys layout\r\n  < qwertyuiop[]asdfghjkl;'zxcvbnm,.`\/QWERTYUIOP{}ASDFGHJKL:\"ZXCVBNM<>?~@#$^&|\r\n  > йцукенгшщзхъфывапролджэячсмитьбюё.ЙЦУКЕНГШЩЗХЪФЫВАПРОЛДЖЭЯЧСМИТЬБЮ,Ё\"№;:?\/\r\n\r\n  de\r\n  < yz-[];'\/YZ{}:\"<>?~@#^&*(_\\\r\n  > zy\u00c3\u009f\u00c3\u00bc+\u00c3\u00b6\u00c3\u00a4-ZY\u00c3\u009c*\u00c3\u0096\u00c3\u0084;:_\u00c2\u00b0\"\u00c2\u00a7&\/()?#\r\n\r\n    Sample file xkbswitch.tr with exactly this content is shipped with this\r\n    plugin distribution. It is encoded in UTF-8 and it is important as far as\r\n    its content is read using readfile()! If your locale is not UTF-8 and\r\n    you want to use this sample file then it seems that you will have to\r\n    re-encode it in your locale standard encoding\r\n\r\nBe very careful with mapping duplicates! They won't replace existing Insert\r\nmode mappings but may define extra mappings that will change normal Insert\r\nmode user experience. For example plugin echofunc defines Insert mode mappings\r\nfor '(' and ')', therefore assuming that in Deutsch translation map there\r\ncould be ')' to '=' translation, we would get '=' unusable in any keyboard\r\nlayout (as far as echofunc treats ')' in a very specific way). That is why\r\nthis translation is missing in example above and in file xkbswitch.tr content.\r\n\r\nThere are multiple examples of similar issues. For instance Russian winkeys\r\ntranslate '.' into 'ю' and when you are editing a C\/C++ source file with\r\nenabled omnicompletion plugin character 'ю' (which you can use in comments)\r\nwill always be replaced by '.'. To address these issues starting from version\r\n0.10 a new variable g:XkbSwitchSkipIMappings was introduced. It defines which\r\noriginal Insert mode mappings should not be translated for specific filetypes.\r\nAdd into your .vimrc lines\r\n\r\n    let g:XkbSwitchSkipIMappings = {'c': ['.', '>', ':', '\/*', '\/*<CR>'],\r\n            \\ 'cpp': ['.', '>', ':', '\/*', '\/*<CR>']}\r\n\r\nand now you will be able to print 'ю' in C and C++ source files. In this\r\nexample five Insert mode mappings were prohibited for translation in two\r\nfiletypes: C and C++, the first three correspond to omnicompletion plugin\r\nand the last two address plugin c.vim. Why mappings duplicates starting from\r\n'\/' were added: Russian winkeys translate '\/' into '.' and this makes vim\r\nwait for a next character input after '.' was inserted which makes\r\nomnicompletion plugin almost unusable.\r\n\r\nBeware: variable g:XkbSwitchSkipIMappings is not parameterized by keyboard\r\nlayouts but only by filetypes.\r\n\r\nBy default saved Normal mode keyboard layout is restored when leaving Insert\r\nmode, but you can specify to use particular layout for that:\r\n\r\n    let g:XkbSwitchNLayout = 'us'\r\n\r\nAlso you can specify original Insert mode keyboard layout:\r\n\r\n    let g:XkbSwitchILayout = 'us'\r\n\r\nIt makes sense to disable XkbSwitch for buffers with specific filetypes, for\r\nexample various file system or tag navigators. For example to disable\r\nXkbSwitch for NerdTree add in your .vimrc line\r\n\r\n    let g:XkbSwitchSkipFt = [ 'nerdtree' ]\r\n\r\nBy default (e.g. when g:XkbSwitchSkipFt is not defined in .vimrc) following\r\nfiletypes are skipped: 'tagbar', 'gundo', 'nerdtree' and 'fuf' (FuzzyFinder).\r\n\r\nYou can enable XkbSwitch in runtime (e.g. when g:XkbSwitchEnabled is not set\r\nin your .vimrc) by issuing command\r\n\r\n    :EnableXkbSwitch\r\n\r\nThis command will respect current settings of g:XkbSwitchIMappings etc. Be\r\naware that there is no way to disable XkbSwitch after it has been enabled.\r\n\r\n\r\nTroubleshooting:\r\n\r\n  - There is a known issue when vim-latex package is installed. In this case\r\n    entering Russian symbols in Insert mode when editing tex files becomes\r\n    impossible. The issue arises from clashing XkbSwitch Insert mappings\r\n    duplicates with mappings defined in vim-latex. To work this issue around\r\n    you can disable XkbSwitch Insert mode mappings duplicates for filetype\r\n    'tex':\r\n\r\n    let g:XkbSwitchIMappingsSkipFt = ['tex']\r\n\r\n  - Related to X Server only. When editing files on a remote host via ssh the\r\n    ssh -X option must be supplied:\r\n\r\n    ssh -X remote.host\r\n\r\n    This option will make ssh forward X Server protocol messages between the\r\n    local host and the remote host thus making it possible to switch the local\r\n    host keyboard layouts.\r\n\r\n  - Related to GTK based gvim only. In bare X terminals keycodes for <C-S> and\r\n    <C-Ы> are the same which makes it possible to leave sequences with control\r\n    keys in Insert mode mappings duplicates as they are. But this is not the\r\n    case in GTK based gvim. The issue is still investigated.","4":"About:\r\n\r\nVim plugin XkbSwitch can be used to easily switch current keyboard layout back\r\nand forth when entering and leaving Insert mode. Say you are typing some\r\ndocument in Russian and have to leave Insert mode: when you press <Esc> your\r\nkeyboard layout switches to US\/English automatically. When you further enter\r\nInsert mode once again the Russian keyboard layout will be automatically\r\nswitched back!\r\n\r\nXkbSwitch requires OS dependent keyboard layout switcher. Currently it depends\r\non xkb-switch (http:\/\/github.com\/ierton\/xkb-switch) for UNIX \/ X Server and\r\nxkb-switch-win (http:\/\/github.com\/DeXP\/xkb-switch-win) for Windows. \r\n\r\nFor Mac OS X you can try Input Source Switcher\r\n(http:\/\/github.com\/vovkasm\/input-source-switcher) and set library path as\r\n\r\n    let g:XkbSwitchLib = '\/usr\/local\/lib\/libInputSourceSwitcher.dylib'\r\n\r\nGnome 3 no longer works correctly with xkb-switch, so consider switching to\r\ng3kb-switch (https:\/\/github.com\/lyokha\/g3kb-switch) if you are using this\r\nenvironment. The library path should be set as\r\n\r\n    let g:XkbSwitchLib = '\/usr\/local\/lib\/libg3kbswitch.so'\r\n\r\ngithub: http:\/\/github.com\/lyokha\/vim-xkbswitch\r\n\r\n\r\nFeatures:\r\n\r\n  - Supported OS: UNIX \/ X Server, Windows, Mac OS X\r\n  - Switches keyboard layout when entering \/ leaving Insert and Select modes\r\n  - Keyboard layouts are stored separately for each buffer\r\n  - Keyboard layouts are kept intact while navigating between windows or\r\n    tabs without leaving Insert mode\r\n  - Automatic loading of language-friendly Insert mode mappings. For example\r\n    when Russian mappings have loaded then if there was a mapping\r\n\r\n    <C-G>S        <Plug>ISurround\r\n\r\n    a new mapping\r\n\r\n    <C-G>Ы        <Plug>ISurround\r\n\r\n    will be loaded. Insert mode mappings duplicates make it easy to apply\r\n    existing maps in Insert mode without switching current keyboard layout\r\n  - Fast and easy building of custom syntax based keyboard layout switching\r\n    rules in Insert mode\r\n\r\n\r\nConfiguration:\r\n\r\nBasic configuration requires only 1 line in your .vimrc:\r\n\r\n    let g:XkbSwitchEnabled = 1\r\n\r\nAdditionally path to the backend switcher library can be defined:\r\n\r\n    let g:XkbSwitchLib = '\/usr\/local\/lib\/libxkbswitch.so'\r\n\r\nHowever normally it is not necessary as far as the plugin is able to find it\r\nautomatically. To enable Insert mode mappings duplicates user may want to add\r\n\r\n    let g:XkbSwitchIMappings = ['ru']\r\n\r\nHere Insert mappings duplicates for Russian winkeys layout will be generated\r\nwhenever Insert mode is started. It is possible to define a list of different\r\nlayouts, for example\r\n\r\n    let g:XkbSwitchIMappings = ['ru', 'de']\r\n\r\nbut currently only Russian winkeys layout translation map ('ru') is supported\r\nout of the box. There are 2 ways how a user can provide extra definitions of\r\nkeyboard layout translation maps (or replace existing default 'ru' map):\r\n\r\n  - Define variable g:XkbSwitchIMappingsTr:\r\n\r\n    let g:XkbSwitchIMappingsTr = {\r\n                \\ 'ru':\r\n                \\ {'<': 'qwertyuiop[]asdfghjkl;''zxcvbnm,.`\/'.\r\n                \\       'QWERTYUIOP{}ASDFGHJKL:\"ZXCVBNM<>?~@#$^&|',\r\n                \\  '>': 'йцукенгшщзхъфывапролджэячсмитьбюё.'.\r\n                \\       'ЙЦУКЕНГШЩЗХЪФЫВАПРОЛДЖЭЯЧСМИТЬБЮ,Ё\"№;:?\/'},\r\n                \\ 'de':\r\n                \\ {'<': 'yz-[];''\/YZ{}:\"<>?~@#^&*_\\',\r\n                \\  '>': 'zy\u00c3\u009f\u00c3\u00bc+\u00c3\u00b6\u00c3\u00a4-ZY\u00c3\u009c*\u00c3\u0096\u00c3\u0084;:_\u00c2\u00b0\"\u00c2\u00a7&\/(?#'},\r\n                \\ }\r\n\r\n  - Create a file with layout translation maps and put its path into variable\r\n    g:XkbSwitchIMappingsTrData, for example:\r\n\r\n    let g:XkbSwitchIMappingsTrData = $HOME.'\/opt\/xkbswitch.tr'\r\n\r\n    File with maps must follow this format:\r\n\r\n  ru  Russian winkeys layout\r\n  < qwertyuiop[]asdfghjkl;'zxcvbnm,.`\/QWERTYUIOP{}ASDFGHJKL:\"ZXCVBNM<>?~@#$^&|\r\n  > йцукенгшщзхъфывапролджэячсмитьбюё.ЙЦУКЕНГШЩЗХЪФЫВАПРОЛДЖЭЯЧСМИТЬБЮ,Ё\"№;:?\/\r\n\r\n  de\r\n  < yz-[];'\/YZ{}:\"<>?~@#^&*(_\\\r\n  > zy\u00c3\u009f\u00c3\u00bc+\u00c3\u00b6\u00c3\u00a4-ZY\u00c3\u009c*\u00c3\u0096\u00c3\u0084;:_\u00c2\u00b0\"\u00c2\u00a7&\/()?#\r\n\r\n    Sample file xkbswitch.tr with exactly this content is shipped with this\r\n    plugin distribution. It is encoded in UTF-8 and it is important as far as\r\n    its content is read using readfile()! If your locale is not UTF-8 and\r\n    you want to use this sample file then it seems that you will have to\r\n    re-encode it in your locale standard encoding\r\n\r\nBe very careful with mapping duplicates! They won't replace existing Insert\r\nmode mappings but may define extra mappings that will change normal Insert\r\nmode user experience. For example plugin echofunc defines Insert mode mappings\r\nfor '(' and ')', therefore assuming that in Deutsch translation map there\r\ncould be ')' to '=' translation, we would get '=' unusable in any keyboard\r\nlayout (as far as echofunc treats ')' in a very specific way). That is why\r\nthis translation is missing in example above and in file xkbswitch.tr content.\r\n\r\nThere are multiple examples of similar issues. For instance Russian winkeys\r\ntranslate '.' into 'ю' and when you are editing a C\/C++ source file with\r\nenabled omnicompletion plugin character 'ю' (which you can use in comments)\r\nwill always be replaced by '.'. To address these issues starting from version\r\n0.10 a new variable g:XkbSwitchSkipIMappings was introduced. It defines which\r\noriginal Insert mode mappings should not be translated for specific filetypes.\r\nAdd into your .vimrc lines\r\n\r\n    let g:XkbSwitchSkipIMappings = {'c': ['.', '>', ':', '\/*', '\/*<CR>'],\r\n            \\ 'cpp': ['.', '>', ':', '\/*', '\/*<CR>']}\r\n\r\nand now you will be able to print 'ю' in C and C++ source files. In this\r\nexample five Insert mode mappings were prohibited for translation in two\r\nfiletypes: C and C++, the first three correspond to omnicompletion plugin\r\nand the last two address plugin c.vim. Why mappings duplicates starting from\r\n'\/' were added: Russian winkeys translate '\/' into '.' and this makes vim\r\nwait for a next character input after '.' was inserted which makes\r\nomnicompletion plugin almost unusable.\r\n\r\nBeware: variable g:XkbSwitchSkipIMappings is not parameterized by keyboard\r\nlayouts but only by filetypes.\r\n\r\nBy default saved Normal mode keyboard layout is restored when leaving Insert\r\nmode, but you can specify to use particular layout for that:\r\n\r\n    let g:XkbSwitchNLayout = 'us'\r\n\r\nAlso you can specify original Insert mode keyboard layout:\r\n\r\n    let g:XkbSwitchILayout = 'us'\r\n\r\nIt makes sense to disable XkbSwitch for buffers with specific filetypes, for\r\nexample various file system or tag navigators. For example to disable\r\nXkbSwitch for NerdTree add in your .vimrc line\r\n\r\n    let g:XkbSwitchSkipFt = [ 'nerdtree' ]\r\n\r\nBy default (e.g. when g:XkbSwitchSkipFt is not defined in .vimrc) following\r\nfiletypes are skipped: 'tagbar', 'gundo', 'nerdtree' and 'fuf' (FuzzyFinder).\r\n\r\nYou can enable XkbSwitch in runtime (e.g. when g:XkbSwitchEnabled is not set\r\nin your .vimrc) by issuing command\r\n\r\n    :EnableXkbSwitch\r\n\r\nThis command will respect current settings of g:XkbSwitchIMappings etc. Be\r\naware that there is no way to disable XkbSwitch after it has been enabled.\r\n\r\n\r\nTroubleshooting:\r\n\r\n  - There is a known issue when vim-latex package is installed. In this case\r\n    entering Russian symbols in Insert mode when editing tex files becomes\r\n    impossible. The issue arises from clashing XkbSwitch Insert mappings\r\n    duplicates with mappings defined in vim-latex. To work this issue around\r\n    you can disable XkbSwitch Insert mode mappings duplicates for filetype\r\n    'tex':\r\n\r\n    let g:XkbSwitchIMappingsSkipFt = ['tex']\r\n\r\n  - Related to X Server only. When editing files on a remote host via ssh the\r\n    ssh -X option must be supplied:\r\n\r\n    ssh -X remote.host\r\n\r\n    This option will make ssh forward X Server protocol messages between the\r\n    local host and the remote host thus making it possible to switch the local\r\n    host keyboard layouts.\r\n\r\n  - Related to GTK based gvim only. In bare X terminals keycodes for <C-S> and\r\n    <C-Ы> are the same which makes it possible to leave sequences with control\r\n    keys in Insert mode mappings duplicates as they are. But this is not the\r\n    case in GTK based gvim. The issue is still investigated.","install_details":"An external keyboard layout switcher must be installed (see Description). Extract content of the tarball in your home vim directory and run\r\n\r\n:helptags ~\/.vim\/doc\/\r\n\r\nin vim to create vim help tags.","5":"An external keyboard layout switcher must be installed (see Description). Extract content of the tarball in your home vim directory and run\r\n\r\n:helptags ~\/.vim\/doc\/\r\n\r\nin vim to create vim help tags.","first_name":"Alexey","6":"Alexey","last_name":"Radkov","7":"Radkov","releases":[{"0":"4503","vim_version":"7.3","1":"7.3","script_version":"0.20","2":"0.20","version_comment":"- Support for Sway via libswaykbswitch.so (thanks to Andrey Khorokhorin).\r\n- New utility keymap2imaptr.vim to help translate vim's language keymaps to vim-xkbswitch imap translation files.\r\n- Test more paths to detect the location of libg3kbswitch.so","3":"- Support for Sway via libswaykbswitch.so (thanks to Andrey Khorokhorin).\r\n- New utility keymap2imaptr.vim to help translate vim's language keymaps to vim-xkbswitch imap translation files.\r\n- Test more paths to detect the location of libg3kbswitch.so","package":"vim-xkbswitch-0.20.tgz","4":"vim-xkbswitch-0.20.tgz","src_id":"28418","5":"28418","creation_date":"1682024552","6":"1682024552"},{"0":"4503","vim_version":"7.3","1":"7.3","script_version":"0.19","2":"0.19","version_comment":"It's now possible to run a custom vim function when entering Insert mode. The function is pointed by variable g:XkbSwitchIEnterHook.","3":"It's now possible to run a custom vim function when entering Insert mode. The function is pointed by variable g:XkbSwitchIEnterHook.","package":"vim-xkbswitch-0.19.tgz","4":"vim-xkbswitch-0.19.tgz","src_id":"28339","5":"28339","creation_date":"1673035684","6":"1673035684"},{"0":"4503","vim_version":"7.3","1":"7.3","script_version":"0.18","2":"0.18","version_comment":"- Proper support for tracking keyboard layout state upon entering\/leaving Select mode using ModeChanged events.\r\n- Setting variables g:XkbSwitchSkipGhKeys and g:XkbSwitchSelectmodeKeys is now deprecated and has no effect when ModeChanged events are supported.","3":"- Proper support for tracking keyboard layout state upon entering\/leaving Select mode using ModeChanged events.\r\n- Setting variables g:XkbSwitchSkipGhKeys and g:XkbSwitchSelectmodeKeys is now deprecated and has no effect when ModeChanged events are supported.","package":"vim-xkbswitch-0.18.tgz","4":"vim-xkbswitch-0.18.tgz","src_id":"28322","5":"28322","creation_date":"1671599922","6":"1671599922"},{"0":"4503","vim_version":"7.3","1":"7.3","script_version":"0.17.2","2":"0.17.2","version_comment":"A few improvements and optimizations in the duplicate insert mappings load algorithm.","3":"A few improvements and optimizations in the duplicate insert mappings load algorithm.","package":"vim-xkbswitch-0.17.2.tgz","4":"vim-xkbswitch-0.17.2.tgz","src_id":"28318","5":"28318","creation_date":"1671394940","6":"1671394940"},{"0":"4503","vim_version":"7.3","1":"7.3","script_version":"0.17.1","2":"0.17.1","version_comment":"Bugfix: tracking of the keyboard layout state was getting broken after visiting the command-line window with commands q\/ and q?.","3":"Bugfix: tracking of the keyboard layout state was getting broken after visiting the command-line window with commands q\/ and q?.","package":"vim-xkbswitch-0.17.1.tgz","4":"vim-xkbswitch-0.17.1.tgz","src_id":"28266","5":"28266","creation_date":"1668480330","6":"1668480330"},{"0":"4503","vim_version":"7.3","1":"7.3","script_version":"0.17","2":"0.17","version_comment":"- Full support for tracking keyboard layout state upon entering\/leaving command line when searching patterns with \/ and ?.\r\n- Setting variables g:XkbSwitchAssistSKeymap and g:XkbSwitchLoadOnBufRead is now deprecated and has no effect.","3":"- Full support for tracking keyboard layout state upon entering\/leaving command line when searching patterns with \/ and ?.\r\n- Setting variables g:XkbSwitchAssistSKeymap and g:XkbSwitchLoadOnBufRead is now deprecated and has no effect.","package":"vim-xkbswitch-0.17.tgz","4":"vim-xkbswitch-0.17.tgz","src_id":"28265","5":"28265","creation_date":"1668369360","6":"1668369360"},{"0":"4503","vim_version":"7.3","1":"7.3","script_version":"0.16","2":"0.16","version_comment":"- Improvement: provide ability to toggle iminsert in Normal mode by defining variable g:XkbSwitchIminsertToggleKey.\r\n- Bugfix: added more backslashes to fix translations of insert mappings.","3":"- Improvement: provide ability to toggle iminsert in Normal mode by defining variable g:XkbSwitchIminsertToggleKey.\r\n- Bugfix: added more backslashes to fix translations of insert mappings.","package":"vim-xkbswitch-0.16.tgz","4":"vim-xkbswitch-0.16.tgz","src_id":"27984","5":"27984","creation_date":"1649470535","6":"1649470535"},{"0":"4503","vim_version":"7.3","1":"7.3","script_version":"0.15.2","2":"0.15.2","version_comment":"- In default g:XkbSwitchIMappingsTr the Ukrainian ('uk') keyboard layout translation map was added (thanks to kukushkawi).\r\n- Fixed wrong behavior of dynamic keymap assistance in Normal mode.","3":"- In default g:XkbSwitchIMappingsTr the Ukrainian ('uk') keyboard layout translation map was added (thanks to kukushkawi).\r\n- Fixed wrong behavior of dynamic keymap assistance in Normal mode.","package":"vim-xkbswitch-0.15.2.tgz","4":"vim-xkbswitch-0.15.2.tgz","src_id":"27967","5":"27967","creation_date":"1648151077","6":"1648151077"},{"0":"4503","vim_version":"7.3","1":"7.3","script_version":"0.15.1","2":"0.15.1","version_comment":"- Bugfix: insert mappings which contain single quotes must be escaped when building translations.\r\n- Never enable the plugin in nofile buftypes.","3":"- Bugfix: insert mappings which contain single quotes must be escaped when building translations.\r\n- Never enable the plugin in nofile buftypes.","package":"vim-xkbswitch-0.15.1.tgz","4":"vim-xkbswitch-0.15.1.tgz","src_id":"27731","5":"27731","creation_date":"1630961252","6":"1630961252"},{"0":"4503","vim_version":"7.3","1":"7.3","script_version":"0.15","2":"0.15","version_comment":"    - Integration with LeaderF plugin (thanks to Freed-Wu)\r\n    - Fixed interference with neovim's float windows","3":"    - Integration with LeaderF plugin (thanks to Freed-Wu)\r\n    - Fixed interference with neovim's float windows","package":"vim-xkbswitch-0.15.tgz","4":"vim-xkbswitch-0.15.tgz","src_id":"27391","5":"27391","creation_date":"1606931215","6":"1606931215"},{"0":"4503","vim_version":"7.3","1":"7.3","script_version":"0.14.3","2":"0.14.3","version_comment":"Bugfix for Mac users after previous version: Re-enable the plugin when vim has() both \"macunix\" and \"unix\".","3":"Bugfix for Mac users after previous version: Re-enable the plugin when vim has() both \"macunix\" and \"unix\".","package":"vim-xkbswitch-0.14.3.tgz","4":"vim-xkbswitch-0.14.3.tgz","src_id":"25033","5":"25033","creation_date":"1489656314","6":"1489656314"},{"0":"4503","vim_version":"7.3","1":"7.3","script_version":"0.14.2","2":"0.14.2","version_comment":"- Do not enable the plugin on Linux\/X11 when there is no X server run\r\n- Check validity of imap values when generating imappings, prefer function execute() to redir when reading them","3":"- Do not enable the plugin on Linux\/X11 when there is no X server run\r\n- Check validity of imap values when generating imappings, prefer function execute() to redir when reading them","package":"vim-xkbswitch-0.14.2.tgz","4":"vim-xkbswitch-0.14.2.tgz","src_id":"24990","5":"24990","creation_date":"1487762308","6":"1487762308"},{"0":"4503","vim_version":"7.3","1":"7.3","script_version":"0.14.1","2":"0.14.1","version_comment":"Keymap assistance refactored with more robust behaviour. Added dynamic keymap support. In the docs added an example of how to enable Powerline iminsert indicator.","3":"Keymap assistance refactored with more robust behaviour. Added dynamic keymap support. In the docs added an example of how to enable Powerline iminsert indicator.","package":"vim-xkbswitch-0.14.1.tgz","4":"vim-xkbswitch-0.14.1.tgz","src_id":"23972","5":"23972","creation_date":"1454243599","6":"1454243599"},{"0":"4503","vim_version":"7.3","1":"7.3","script_version":"0.14","2":"0.14","version_comment":"    - Keymap assistance in Normal and Command-line modes provides limited\r\n      support for using the last Insert mode keyboard layout in Normal mode\r\n      commands 'r' and 'f' and search lines (see updated docs)","3":"    - Keymap assistance in Normal and Command-line modes provides limited\r\n      support for using the last Insert mode keyboard layout in Normal mode\r\n      commands 'r' and 'f' and search lines (see updated docs)","package":"vim-xkbswitch-0.14.tgz","4":"vim-xkbswitch-0.14.tgz","src_id":"23964","5":"23964","creation_date":"1454094145","6":"1454094145"},{"0":"4503","vim_version":"7.3","1":"7.3","script_version":"0.13","2":"0.13","version_comment":"    - Named registers insertion keys translation (e.g <C-R>a to <C-R>ф for\r\n      Russian winkeys layout)\r\n    - Better xkbswitch library search algorithm\r\n    - Option for choosing unconditional keyboard layout when entering Insert\r\n      mode with buffer-variable b:XkbSwitchILayout. This can also be used to\r\n      disable keyboard layout switching when entering Insert mode (see updated\r\n      docs)","3":"    - Named registers insertion keys translation (e.g <C-R>a to <C-R>ф for\r\n      Russian winkeys layout)\r\n    - Better xkbswitch library search algorithm\r\n    - Option for choosing unconditional keyboard layout when entering Insert\r\n      mode with buffer-variable b:XkbSwitchILayout. This can also be used to\r\n      disable keyboard layout switching when entering Insert mode (see updated\r\n      docs)","package":"vim-xkbswitch-0.13.tgz","4":"vim-xkbswitch-0.13.tgz","src_id":"23891","5":"23891","creation_date":"1452613287","6":"1452613287"},{"0":"4503","vim_version":"7.3","1":"7.3","script_version":"0.12","2":"0.12","version_comment":"    - Added support for Mac OS X using external library Input Source Switcher\r\n      (see updated docs)\r\n    - Added new global variable g:XkbSwitchSkipGhKeys which can be used to\r\n      optionally disable gh-mappings required for Select mode support","3":"    - Added support for Mac OS X using external library Input Source Switcher\r\n      (see updated docs)\r\n    - Added new global variable g:XkbSwitchSkipGhKeys which can be used to\r\n      optionally disable gh-mappings required for Select mode support","package":"vim-xkbswitch-0.12.tgz","4":"vim-xkbswitch-0.12.tgz","src_id":"22759","5":"22759","creation_date":"1420551660","6":"1420551660"},{"0":"4503","vim_version":"7.3","1":"7.3","script_version":"0.11","2":"0.11","version_comment":"    - Implemented full support for various selection models defined with\r\n      option selectmode\r\n    - Do not duplicate <SNR> mappings","3":"    - Implemented full support for various selection models defined with\r\n      option selectmode\r\n    - Do not duplicate <SNR> mappings","package":"vim-xkbswitch-0.11.tgz","4":"vim-xkbswitch-0.11.tgz","src_id":"22282","5":"22282","creation_date":"1406964575","6":"1406964575"},{"0":"4503","vim_version":"7.0","1":"7.0","script_version":"0.10.1","2":"0.10.1","version_comment":"bugfix: bars in Insert mode mappings are now properly escaped","3":"bugfix: bars in Insert mode mappings are now properly escaped","package":"vim-xkbswitch-0.10.1.tgz","4":"vim-xkbswitch-0.10.1.tgz","src_id":"21598","5":"21598","creation_date":"1394528004","6":"1394528004"},{"0":"4503","vim_version":"7.3","1":"7.3","script_version":"0.10","2":"0.10","version_comment":"- Fixed building Insert mode mappings defined with <expr>\r\n- Added new variable g:XkbSwitchSkipIMappings to disable translation of\r\n  specific Insert mode mappings for specific file types","3":"- Fixed building Insert mode mappings defined with <expr>\r\n- Added new variable g:XkbSwitchSkipIMappings to disable translation of\r\n  specific Insert mode mappings for specific file types","package":"vim-xkbswitch-0.10.tgz","4":"vim-xkbswitch-0.10.tgz","src_id":"20491","5":"20491","creation_date":"1373110618","6":"1373110618"},{"0":"4503","vim_version":"7.3","1":"7.3","script_version":"0.9.4","2":"0.9.4","version_comment":"Switching between Select and Visual modes (with <C-g>) without flickers","3":"Switching between Select and Visual modes (with <C-g>) without flickers","package":"vim-xkbswitch-0.9.4.tgz","4":"vim-xkbswitch-0.9.4.tgz","src_id":"20483","5":"20483","creation_date":"1373038387","6":"1373038387"},{"0":"4503","vim_version":"7.3","1":"7.3","script_version":"0.9.3","2":"0.9.3","version_comment":"Better support and fixes in Select mode","3":"Better support and fixes in Select mode","package":"vim-xkbswitch-0.9.3.tgz","4":"vim-xkbswitch-0.9.3.tgz","src_id":"20442","5":"20442","creation_date":"1372239385","6":"1372239385"},{"0":"4503","vim_version":"7.3","1":"7.3","script_version":"0.9.2","2":"0.9.2","version_comment":"Further fixes related to the custom syntax based switching rules\r\nimplementation","3":"Further fixes related to the custom syntax based switching rules\r\nimplementation","package":"vim-xkbswitch-0.9.2.tgz","4":"vim-xkbswitch-0.9.2.tgz","src_id":"20107","5":"20107","creation_date":"1368434977","6":"1368434977"},{"0":"4503","vim_version":"7.3","1":"7.3","script_version":"0.9.1","2":"0.9.1","version_comment":"fixed broken layout switching","3":"fixed broken layout switching","package":"vim-xkbswitch-0.9.1.tgz","4":"vim-xkbswitch-0.9.1.tgz","src_id":"20105","5":"20105","creation_date":"1368394596","6":"1368394596"},{"0":"4503","vim_version":"7.3","1":"7.3","script_version":"0.9","2":"0.9","version_comment":"Implemented helpers for building custom keyboard layout switching rules\r\nbased on syntax inside Insert mode (see updated docs)","3":"Implemented helpers for building custom keyboard layout switching rules\r\nbased on syntax inside Insert mode (see updated docs)","package":"vim-xkbswitch-0.9.tgz","4":"vim-xkbswitch-0.9.tgz","src_id":"20104","5":"20104","creation_date":"1368392951","6":"1368392951"},{"0":"4503","vim_version":"7.3","1":"7.3","script_version":"0.8.2","2":"0.8.2","version_comment":"- The cause of the issue explained in the 0.8.1 change log discovered. It\r\n  affects gvim in client-server mode (e.g. when files are open from an\r\n  external application using options --remote-tab and similar). Variable\r\n  g:XkbSwitchFixNoBufLeave is not needed any more: the fix is applied\r\n  automatically in gvim with clientserver feature. Also this issue\r\n  investigation revealed that different switcher strategies implemented\r\n  inside backend libraries must be supported. Currently X server switcher\r\n  gets and sets keyboard layout globally whereas Windows switcher does it\r\n  locally in vim window. This difference is reflected in a new field\r\n  'local' in dictionary g:XkbSwitch","3":"- The cause of the issue explained in the 0.8.1 change log discovered. It\r\n  affects gvim in client-server mode (e.g. when files are open from an\r\n  external application using options --remote-tab and similar). Variable\r\n  g:XkbSwitchFixNoBufLeave is not needed any more: the fix is applied\r\n  automatically in gvim with clientserver feature. Also this issue\r\n  investigation revealed that different switcher strategies implemented\r\n  inside backend libraries must be supported. Currently X server switcher\r\n  gets and sets keyboard layout globally whereas Windows switcher does it\r\n  locally in vim window. This difference is reflected in a new field\r\n  'local' in dictionary g:XkbSwitch","package":"vim-xkbswitch-0.8.2.tgz","4":"vim-xkbswitch-0.8.2.tgz","src_id":"19900","5":"19900","creation_date":"1366699842","6":"1366699842"},{"0":"4503","vim_version":"7.3","1":"7.3","script_version":"0.8.1","2":"0.8.1","version_comment":"- Fixed a bug when original Insert mode layout could be lost when leaving\r\n  a buffer in Insert mode for a new tab in gvim. Thanks to zdm for code\r\n  contribution. The bug was caused by missing BufLeave events in certain\r\n  cases. It seems that it does not affect all vim flavors (both latest\r\n  Mercurial snapshot built on my Fedora 18 desktop and standard vim\r\n  distribution taken from repository seem to be not affected). You can\r\n  disable the code of the fix by adding in your .vimrc line\r\n\r\n    let g:XkbSwitchFixNoBufLeave = 0\r\n\r\n  if you know that your vim is good and always generates BufLeave events\r\n  when jumping to another tab while being in Insert mode","3":"- Fixed a bug when original Insert mode layout could be lost when leaving\r\n  a buffer in Insert mode for a new tab in gvim. Thanks to zdm for code\r\n  contribution. The bug was caused by missing BufLeave events in certain\r\n  cases. It seems that it does not affect all vim flavors (both latest\r\n  Mercurial snapshot built on my Fedora 18 desktop and standard vim\r\n  distribution taken from repository seem to be not affected). You can\r\n  disable the code of the fix by adding in your .vimrc line\r\n\r\n    let g:XkbSwitchFixNoBufLeave = 0\r\n\r\n  if you know that your vim is good and always generates BufLeave events\r\n  when jumping to another tab while being in Insert mode","package":"vim-xkbswitch-0.8.1.tgz","4":"vim-xkbswitch-0.8.1.tgz","src_id":"19864","5":"19864","creation_date":"1366409199","6":"1366409199"},{"0":"4503","vim_version":"7.3","1":"7.3","script_version":"0.8","2":"0.8","version_comment":"- Added possibility to specify default Normal mode and original Insert\r\n  mode keyboard layouts\r\n- Docs fixed and extended","3":"- Added possibility to specify default Normal mode and original Insert\r\n  mode keyboard layouts\r\n- Docs fixed and extended","package":"vim-xkbswitch-0.8.tgz","4":"vim-xkbswitch-0.8.tgz","src_id":"19863","5":"19863","creation_date":"1366399391","6":"1366399391"},{"0":"4503","vim_version":"7.3","1":"7.3","script_version":"0.7","2":"0.7","version_comment":"- Keyboard layouts are kept intact while navigating between windows or\r\n  tabs without leaving Insert mode\r\n- A new variable g:XkbSwitchSkipFt was introduced to provide ability of\r\n  disabling XkbSwitch for specific filetypes","3":"- Keyboard layouts are kept intact while navigating between windows or\r\n  tabs without leaving Insert mode\r\n- A new variable g:XkbSwitchSkipFt was introduced to provide ability of\r\n  disabling XkbSwitch for specific filetypes","package":"vim-xkbswitch-0.7.tgz","4":"vim-xkbswitch-0.7.tgz","src_id":"19862","5":"19862","creation_date":"1366364486","6":"1366364486"},{"0":"4503","vim_version":"7.3","1":"7.3","script_version":"0.6","2":"0.6","version_comment":"- Added variable g:XkbSwitchPostIEnterAuto to register InsertEnter\r\n   autocommands that should run after standard XkbSwitch InsertEnter\r\n   autocommand\r\n- Added an example of how custom keyboard layout switching rules inside\r\n   Insert mode can be implemented\r\n- Fixed Select mode switching broken in version 0.5","3":"- Added variable g:XkbSwitchPostIEnterAuto to register InsertEnter\r\n   autocommands that should run after standard XkbSwitch InsertEnter\r\n   autocommand\r\n- Added an example of how custom keyboard layout switching rules inside\r\n   Insert mode can be implemented\r\n- Fixed Select mode switching broken in version 0.5","package":"vim-xkbswitch-0.6.tgz","4":"vim-xkbswitch-0.6.tgz","src_id":"19818","5":"19818","creation_date":"1366028289","6":"1366028289"},{"0":"4503","vim_version":"7.3","1":"7.3","script_version":"0.5","2":"0.5","version_comment":"- Cleaner and more generic algorithm for switching layout when leaving\r\n   Insert mode: there is no default keyboard layout in Normal mode any\r\n   more; instead last layout that was actual when entering Insert mode is\r\n   being restored when leaving Insert mode.\r\n\r\n- Troubleshooting section in the documentation was extended","3":"- Cleaner and more generic algorithm for switching layout when leaving\r\n   Insert mode: there is no default keyboard layout in Normal mode any\r\n   more; instead last layout that was actual when entering Insert mode is\r\n   being restored when leaving Insert mode.\r\n\r\n- Troubleshooting section in the documentation was extended","package":"vim-xkbswitch-0.5.tgz","4":"vim-xkbswitch-0.5.tgz","src_id":"19816","5":"19816","creation_date":"1366010198","6":"1366010198"},{"0":"4503","vim_version":"7.3","1":"7.3","script_version":"0.4.1","2":"0.4.1","version_comment":"Search Windows libraries in $VIMRUNTIME by default","3":"Search Windows libraries in $VIMRUNTIME by default","package":"vim-xkbswitch-0.4.1.tgz","4":"vim-xkbswitch-0.4.1.tgz","src_id":"19803","5":"19803","creation_date":"1365688305","6":"1365688305"},{"0":"4503","vim_version":"7.3","1":"7.3","script_version":"0.4","2":"0.4","version_comment":"- Insert mode mappings duplicates factory algorithm reimplemented\r\n- New global variable g:XkbSwitchIMappingsSkipFt introduced. It is\r\n   supposed to be used to disable Insert mode mappings duplicates creation\r\n- Docs updated","3":"- Insert mode mappings duplicates factory algorithm reimplemented\r\n- New global variable g:XkbSwitchIMappingsSkipFt introduced. It is\r\n   supposed to be used to disable Insert mode mappings duplicates creation\r\n- Docs updated","package":"vim-xkbswitch-0.4.tgz","4":"vim-xkbswitch-0.4.tgz","src_id":"19799","5":"19799","creation_date":"1365664305","6":"1365664305"},{"0":"4503","vim_version":"7.2","1":"7.2","script_version":"0.3","2":"0.3","version_comment":"- Checking for library presence implemented by filereadable() instead\r\n   executable() - looks like it may have sense for Ubuntu\r\n- Fixed error messages upon start if g:XkbSwitchEnabled were not set\r\n- Added doc about command EnableXkbSwitch","3":"- Checking for library presence implemented by filereadable() instead\r\n   executable() - looks like it may have sense for Ubuntu\r\n- Fixed error messages upon start if g:XkbSwitchEnabled were not set\r\n- Added doc about command EnableXkbSwitch","package":"vim-xkbswitch-0.3.tgz","4":"vim-xkbswitch-0.3.tgz","src_id":"19776","5":"19776","creation_date":"1365354939","6":"1365354939"},{"0":"4503","vim_version":"7.2","1":"7.2","script_version":"0.2","2":"0.2","version_comment":"Better treatment of Insert mode mapping duplicates. Doc updated.","3":"Better treatment of Insert mode mapping duplicates. Doc updated.","package":"vim-xkbswitch-0.2.tgz","4":"vim-xkbswitch-0.2.tgz","src_id":"19754","5":"19754","creation_date":"1364992414","6":"1364992414"},{"0":"4503","vim_version":"7.2","1":"7.2","script_version":"0.1.1","2":"0.1.1","version_comment":"better check for Windows libs","3":"better check for Windows libs","package":"vim-xkbswitch-0.1.1.tgz","4":"vim-xkbswitch-0.1.1.tgz","src_id":"19744","5":"19744","creation_date":"1364841586","6":"1364841586"},{"0":"4503","vim_version":"7.2","1":"7.2","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"vim-xkbswitch-0.1.tgz","4":"vim-xkbswitch-0.1.tgz","src_id":"19743","5":"19743","creation_date":"1364840700","6":"1364840700"}]},"4502":{"script_id":"4502","0":"4502","script_name":"eighties.vim","1":"eighties.vim","script_type":"utility","2":"utility","summary":"Automatically resizes your windows","3":"Automatically resizes your windows","description":"GitHub: https:\/\/github.com\/justincampbell\/vim-eighties\r\nDemo: https:\/\/s3.amazonaws.com\/justincampbell\/vim-eighties.gif\r\n\r\n# Features\r\n\r\n* Resizes the width of the current window when switching\r\n* Calculates the minimum width (80 by default) + line numbers\/signs\/etc\r\n* Won't shrink the current window\r\n* Won't resize file browsers, such as NERDTree\r\n\r\n# Configuration & Defaults\r\n\r\nlet g:eighties_enabled = 1\r\nlet g:eighties_minimum_width = 80 \r\nlet g:eighties_extra_width = 0 \" Increase this if you want some extra room\r\nlet g:eighties_compute = 1 \" Disable this if you just want the minimum + extra","4":"GitHub: https:\/\/github.com\/justincampbell\/vim-eighties\r\nDemo: https:\/\/s3.amazonaws.com\/justincampbell\/vim-eighties.gif\r\n\r\n# Features\r\n\r\n* Resizes the width of the current window when switching\r\n* Calculates the minimum width (80 by default) + line numbers\/signs\/etc\r\n* Won't shrink the current window\r\n* Won't resize file browsers, such as NERDTree\r\n\r\n# Configuration & Defaults\r\n\r\nlet g:eighties_enabled = 1\r\nlet g:eighties_minimum_width = 80 \r\nlet g:eighties_extra_width = 0 \" Increase this if you want some extra room\r\nlet g:eighties_compute = 1 \" Disable this if you just want the minimum + extra","install_details":"Plug:\r\n\r\nPlug 'justincampbell\/vim-eighties'\r\n\r\nVundle:\r\n\r\nBundle 'justincampbell\/vim-eighties'\r\n\r\nPathogen:\r\n\r\ncd ~\/.vim\/bundle\r\ngit clone git:\/\/github.com\/justincampbell\/vim-eighties.git","5":"Plug:\r\n\r\nPlug 'justincampbell\/vim-eighties'\r\n\r\nVundle:\r\n\r\nBundle 'justincampbell\/vim-eighties'\r\n\r\nPathogen:\r\n\r\ncd ~\/.vim\/bundle\r\ngit clone git:\/\/github.com\/justincampbell\/vim-eighties.git","first_name":"Justin","6":"Justin","last_name":"Campbell","7":"Campbell","releases":[{"0":"4502","vim_version":"7.0","1":"7.0","script_version":"1.0.9","2":"1.0.9","version_comment":"* Add EightiesDisable and EightiesEnable commands","3":"* Add EightiesDisable and EightiesEnable commands","package":"vim-eighties.zip","4":"vim-eighties.zip","src_id":"24802","5":"24802","creation_date":"1481824919","6":"1481824919"},{"0":"4502","vim_version":"7.0","1":"7.0","script_version":"1.0.8","2":"1.0.8","version_comment":"* Fix logic for line number width\r\n* Allow for optional list of bufnames to not resize (@jondkinney)\r\n* Fix resize after first open (@flyingwitholdlady)","3":"* Fix logic for line number width\r\n* Allow for optional list of bufnames to not resize (@jondkinney)\r\n* Fix resize after first open (@flyingwitholdlady)","package":"vim-eighties.zip","4":"vim-eighties.zip","src_id":"23707","5":"23707","creation_date":"1446477320","6":"1446477320"},{"0":"4502","vim_version":"7.0","1":"7.0","script_version":"1.0.7","2":"1.0.7","version_comment":"* Fix error when files change outside of Vim (@mattmcmanus)","3":"* Fix error when files change outside of Vim (@mattmcmanus)","package":"vim-eighties.zip","4":"vim-eighties.zip","src_id":"22299","5":"22299","creation_date":"1407361881","6":"1407361881"},{"0":"4502","vim_version":"7.0","1":"7.0","script_version":"1.0.6","2":"1.0.6","version_comment":"* Fix NERDtree detection","3":"* Fix NERDtree detection","package":"vim-eighties.zip","4":"vim-eighties.zip","src_id":"20992","5":"20992","creation_date":"1383315245","6":"1383315245"},{"0":"4502","vim_version":"7.0","1":"7.0","script_version":"1.0.5","2":"1.0.5","version_comment":"* Added vimpanel support (@dexterry)","3":"* Added vimpanel support (@dexterry)","package":"vim-eighties.zip","4":"vim-eighties.zip","src_id":"19849","5":"19849","creation_date":"1366293089","6":"1366293089"},{"0":"4502","vim_version":"7.0","1":"7.0","script_version":"1.0.4","2":"1.0.4","version_comment":"* Fixed occasional errors with lots of buffers","3":"* Fixed occasional errors with lots of buffers","package":"vim-eighties.zip","4":"vim-eighties.zip","src_id":"19785","5":"19785","creation_date":"1365455174","6":"1365455174"},{"0":"4502","vim_version":"7.0","1":"7.0","script_version":"1.0.3","2":"1.0.3","version_comment":"* Resize when entering a window, instead of a buffer","3":"* Resize when entering a window, instead of a buffer","package":"vim-eighties.zip","4":"vim-eighties.zip","src_id":"19779","5":"19779","creation_date":"1365386489","6":"1365386489"},{"0":"4502","vim_version":"7.0","1":"7.0","script_version":"1.0.2","2":"1.0.2","version_comment":"Fixes `:e newfile`","3":"Fixes `:e newfile`","package":"vim-eighties.zip","4":"vim-eighties.zip","src_id":"19757","5":"19757","creation_date":"1364997344","6":"1364997344"},{"0":"4502","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"vim-eighties.zip","4":"vim-eighties.zip","src_id":"19741","5":"19741","creation_date":"1364823372","6":"1364823372"}]},"4501":{"script_id":"4501","0":"4501","script_name":"table-mode","1":"table-mode","script_type":"utility","2":"utility","summary":"Table Mode for VIM for allowing blazing fast table creation on the fly.","3":"Table Mode for VIM for allowing blazing fast table creation on the fly.","description":"VIM Table Mode\r\nAn awesome automatic table creator & formatter allowing one to create neat tables as you type.\r\nYou can find the original repository at https:\/\/github.com\/dhruvasagar\/vim-table-mode\r\n\r\nChange Log\r\nSee CHANGELOG.md\r\n\r\nGetting Started\r\nInstallation\r\n\r\nThere are 2 ways to do this\r\n\r\nI recommend installing pathogen.vim and then adding a git submodule for your plugin:\r\n\r\n$ cd ~\/.vim\r\n$ git submodule add git@github.com:dhruvasagar\/vim-table-mode.git bundle\/table-mode\r\nCopy autoload\/todomode.vim, plugin\/todo-mode.vim, doc\/todo-mode.txt to respective ~\/.vim\/autoload\/, ~\/.vim\/plugin and ~\/.vim\/doc under UNIX or vimfiles\/autoload\/, vimfiles\/plugin\/ and vimfiles\/doc under WINDOWS and restart VIM\r\n\r\nRequirements\r\n\r\nDepends on Tabular. Make sure Tabular is installed and loaded into your runtime to ensure this works.\r\n\r\nUsage\r\n\r\nOn the fly table creation :\r\n\r\nBy default the table column separator is '|' (it can be changed). As soon as you type it on a new line (ignores indentation) the script gets to work on creating a table around it. As you type and define more columns, the table is completed, formatted and aligned automatically on the fly.\r\n\r\nSince this could lead to unwanted behavior I have disabled table mode by default. You would have to use :TableModeToggle command or the table mode toggle mapping, which is <Leader>tm by default to toggle the table mode or you can directly use :TableModeEnable and :TableModeDisable to enable or disable the table mode. This is on a per buffer basis and so it does not cause any unusual behavior unless enabled explicitly. Please read :h table-mode for further information.\r\n\r\nFormat existing content into a table :\r\n\r\nTable Mode wouldn't justify it's name if it didn't allow formatting existing content into a table. And it does as promised. Like table creation on the fly as you type, formatting existing content into a table is equally simple. You can visually select multiple lines and call :Tableize on it, or alternatively use the mapping <Leader>T (this is configurable). :Tableize accepts a range and so you can also call it by giving lines manually like :line1,line2Tableize, but this is not that intuitive. You can also use the mapping <Leader>T with a [count] to apply it to the next [count] lines in usual vim style.\r\n\r\nDemo\r\n\r\n\r\n\r\nContributing\r\nReporting an Issue :\r\n\r\nUse Github Issue Tracker\r\nContributing to code :\r\n\r\nFork it.\r\nCommit your changes and give your commit message some love.\r\nPush to your fork on github.\r\nOpen a Pull Request.\r\nCredit\r\nI must thank Tim Pope for inspiration. The initial concept was created by him named cucumbertables.vim.\r\n\r\nAlso a shout out to godlygeek who developed the incredible Tabular plugin which does most of the grunt work behind the scenes.","4":"VIM Table Mode\r\nAn awesome automatic table creator & formatter allowing one to create neat tables as you type.\r\nYou can find the original repository at https:\/\/github.com\/dhruvasagar\/vim-table-mode\r\n\r\nChange Log\r\nSee CHANGELOG.md\r\n\r\nGetting Started\r\nInstallation\r\n\r\nThere are 2 ways to do this\r\n\r\nI recommend installing pathogen.vim and then adding a git submodule for your plugin:\r\n\r\n$ cd ~\/.vim\r\n$ git submodule add git@github.com:dhruvasagar\/vim-table-mode.git bundle\/table-mode\r\nCopy autoload\/todomode.vim, plugin\/todo-mode.vim, doc\/todo-mode.txt to respective ~\/.vim\/autoload\/, ~\/.vim\/plugin and ~\/.vim\/doc under UNIX or vimfiles\/autoload\/, vimfiles\/plugin\/ and vimfiles\/doc under WINDOWS and restart VIM\r\n\r\nRequirements\r\n\r\nDepends on Tabular. Make sure Tabular is installed and loaded into your runtime to ensure this works.\r\n\r\nUsage\r\n\r\nOn the fly table creation :\r\n\r\nBy default the table column separator is '|' (it can be changed). As soon as you type it on a new line (ignores indentation) the script gets to work on creating a table around it. As you type and define more columns, the table is completed, formatted and aligned automatically on the fly.\r\n\r\nSince this could lead to unwanted behavior I have disabled table mode by default. You would have to use :TableModeToggle command or the table mode toggle mapping, which is <Leader>tm by default to toggle the table mode or you can directly use :TableModeEnable and :TableModeDisable to enable or disable the table mode. This is on a per buffer basis and so it does not cause any unusual behavior unless enabled explicitly. Please read :h table-mode for further information.\r\n\r\nFormat existing content into a table :\r\n\r\nTable Mode wouldn't justify it's name if it didn't allow formatting existing content into a table. And it does as promised. Like table creation on the fly as you type, formatting existing content into a table is equally simple. You can visually select multiple lines and call :Tableize on it, or alternatively use the mapping <Leader>T (this is configurable). :Tableize accepts a range and so you can also call it by giving lines manually like :line1,line2Tableize, but this is not that intuitive. You can also use the mapping <Leader>T with a [count] to apply it to the next [count] lines in usual vim style.\r\n\r\nDemo\r\n\r\n\r\n\r\nContributing\r\nReporting an Issue :\r\n\r\nUse Github Issue Tracker\r\nContributing to code :\r\n\r\nFork it.\r\nCommit your changes and give your commit message some love.\r\nPush to your fork on github.\r\nOpen a Pull Request.\r\nCredit\r\nI must thank Tim Pope for inspiration. The initial concept was created by him named cucumbertables.vim.\r\n\r\nAlso a shout out to godlygeek who developed the incredible Tabular plugin which does most of the grunt work behind the scenes.","install_details":"","5":"","first_name":"Dhruva","6":"Dhruva","last_name":"Sagar","7":"Sagar","releases":[{"0":"4501","vim_version":"7.3","1":"7.3","script_version":"2.2","2":"2.2","version_comment":"Initial upload","3":"Initial upload","package":"table-mode.tar.bz2","4":"table-mode.tar.bz2","src_id":"19739","5":"19739","creation_date":"1364810735","6":"1364810735"}]},"4500":{"script_id":"4500","0":"4500","script_name":"rebtags","1":"rebtags","script_type":"utility","2":"utility","summary":"Easy tags rebuilding on your project directory.","3":"Easy tags rebuilding on your project directory.","description":"https:\/\/github.com\/jespino\/vim-rebtags\r\n\r\nRebTags provides a easy way to rebuild your tags file based on your project directory. It uses the repository directories (.git, .hg, _darcs...) as markers or a .ctags configuration file to find where must build the tags file.","4":"https:\/\/github.com\/jespino\/vim-rebtags\r\n\r\nRebTags provides a easy way to rebuild your tags file based on your project directory. It uses the repository directories (.git, .hg, _darcs...) as markers or a .ctags configuration file to find where must build the tags file.","install_details":"","5":"","first_name":"Jes\u00c3\u00bas","6":"Jes\u00c3\u00bas","last_name":"Espino","7":"Espino","releases":[{"0":"4500","vim_version":"7.0","1":"7.0","script_version":"0.2","2":"0.2","version_comment":"Refactoring the code and adding some extra settings.","3":"Refactoring the code and adding some extra settings.","package":"rebtags-0.2.tar.gz","4":"rebtags-0.2.tar.gz","src_id":"19753","5":"19753","creation_date":"1364970355","6":"1364970355"},{"0":"4500","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"rebtags-0.1.tar.gz","4":"rebtags-0.1.tar.gz","src_id":"19733","5":"19733","creation_date":"1364719819","6":"1364719819"}]},"4499":{"script_id":"4499","0":"4499","script_name":"vim-expand-region","1":"vim-expand-region","script_type":"utility","2":"utility","summary":"Incremental visual selection","3":"Incremental visual selection","description":"See https:\/\/github.com\/terryma\/vim-expand-region","4":"See https:\/\/github.com\/terryma\/vim-expand-region","install_details":"See https:\/\/github.com\/terryma\/vim-expand-region#installation","5":"See https:\/\/github.com\/terryma\/vim-expand-region#installation","first_name":"Terry","6":"Terry","last_name":"Ma","7":"Ma","releases":[{"0":"4499","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"vim-expand-region.zip","4":"vim-expand-region.zip","src_id":"19732","5":"19732","creation_date":"1364717623","6":"1364717623"}]},"4498":{"script_id":"4498","0":"4498","script_name":"Code Upstairs","1":"Code Upstairs","script_type":"ftplugin","2":"ftplugin","summary":"A plugin for browsing source code at functions level.","3":"A plugin for browsing source code at functions level.","description":"Readability of source code is decreasing when project is getting bigger. The\r\naim of this tool is to make code more easily readable and understandable.\r\nIn other words it is trying to put big projects more under control.\r\n\r\nNormally readability of long single function is preserved by using indentation of\r\ncode lines. This plugin provides kind of *indentation* at higher level -\r\n*indentation* of whole functions. \r\n\r\nUser can see fairly easily how current function is dependent upon others. He\r\nwill also get structure of all functions in code in a tree layout if code is clearly\r\nimplemented. So therefor _Code Upstairs_ is also kind of quality controller.\r\n\r\n_Code Upstairs_ is a programmer editors plugins. \r\n\r\n## Vim plugin ##\r\n\r\n### Usage ###\r\nOpen some file of your project and call:\r\n\r\n    :CUinit <directory> \r\n\r\nwhere `<directory>` is the root of your project. \r\nIf skipped current directory will be used.\r\n\r\nStatusline will appear if it was disabled, and you can see \r\nfunctions structure there,\r\nbut only when cursor is in some function body.\r\n\r\nTo turn off _Code Upstairs_ use:\r\n\r\n    :CUshutdown\r\n\r\n### Statusline ###\r\nFunctions structure is shown in statusline.\r\nBecause of limited space statusline is divided to layers. \r\nFollowing layers are shown in order from left to right:\r\n\r\n+ __(-)__ layer showing original vim statusline (like filename and cursor position)\r\n+ __(P)__ layer with parents of current function. Parent is a function from\r\n    which current function is called.\r\n+ __(S)__ siblings layer shows functions which are on the same level with\r\n   current function looking from parent perspective (Frankly saying siblings are\r\n   __pure child functions__ of parent function, check out next layer!)\r\n+ __(C)__ children layer shows __pure child functions__ of current function.\r\n   __Pure child function__ is a function which is called only from one parent. \r\n+ __(XX)__ (where `XX` is a number) layer shows children functions in distance\r\n   `XX` from current function. Those are not __pure child\r\n   functions__, they have more than one parent and therefore theirs calls are\r\n   distributed over code. Distance `XX` tells how far they are distributed.\r\n   Further functions distances can mean not clear implementation or code design.\r\n\r\n### Keybindings ###\r\nDefault keybindings can be change using variables given in parenthesis. \r\n\r\n+ `<space>.` and `<space>,` will switch layer forward and backward.\r\n  (`CUkeyNextLayer` and `CUkeyPrevLayer`)\r\n+ `<space>m` and `<space>n` will switch function in a layer forward and\r\n  backward. (`CUkeyNextFunction` and `CUkeyPrevFunction`)\r\n+ `<space>b` will jump to function definition (`CUkeyJumpToFunction`)\r\n+ `<space>v` will jump back (`CUkeyJumpBack`)\r\n+ `<space>\/` will highlight function name in vim window (`CUkeyHighlightFunction`)\r\n\r\n## _Code Upstairs_ Project Houses ##\r\n\r\n* [vim plugin at vim.org](http:\/\/www.vim.org\/scripts\/script.php?script_id=4498)\r\n* [at github](http:\/\/github.com\/wyderkat\/code_upstairs)\r\n* [at my website](http:\/\/www.cofoh.com\/code_upstairs)\r\n","4":"Readability of source code is decreasing when project is getting bigger. The\r\naim of this tool is to make code more easily readable and understandable.\r\nIn other words it is trying to put big projects more under control.\r\n\r\nNormally readability of long single function is preserved by using indentation of\r\ncode lines. This plugin provides kind of *indentation* at higher level -\r\n*indentation* of whole functions. \r\n\r\nUser can see fairly easily how current function is dependent upon others. He\r\nwill also get structure of all functions in code in a tree layout if code is clearly\r\nimplemented. So therefor _Code Upstairs_ is also kind of quality controller.\r\n\r\n_Code Upstairs_ is a programmer editors plugins. \r\n\r\n## Vim plugin ##\r\n\r\n### Usage ###\r\nOpen some file of your project and call:\r\n\r\n    :CUinit <directory> \r\n\r\nwhere `<directory>` is the root of your project. \r\nIf skipped current directory will be used.\r\n\r\nStatusline will appear if it was disabled, and you can see \r\nfunctions structure there,\r\nbut only when cursor is in some function body.\r\n\r\nTo turn off _Code Upstairs_ use:\r\n\r\n    :CUshutdown\r\n\r\n### Statusline ###\r\nFunctions structure is shown in statusline.\r\nBecause of limited space statusline is divided to layers. \r\nFollowing layers are shown in order from left to right:\r\n\r\n+ __(-)__ layer showing original vim statusline (like filename and cursor position)\r\n+ __(P)__ layer with parents of current function. Parent is a function from\r\n    which current function is called.\r\n+ __(S)__ siblings layer shows functions which are on the same level with\r\n   current function looking from parent perspective (Frankly saying siblings are\r\n   __pure child functions__ of parent function, check out next layer!)\r\n+ __(C)__ children layer shows __pure child functions__ of current function.\r\n   __Pure child function__ is a function which is called only from one parent. \r\n+ __(XX)__ (where `XX` is a number) layer shows children functions in distance\r\n   `XX` from current function. Those are not __pure child\r\n   functions__, they have more than one parent and therefore theirs calls are\r\n   distributed over code. Distance `XX` tells how far they are distributed.\r\n   Further functions distances can mean not clear implementation or code design.\r\n\r\n### Keybindings ###\r\nDefault keybindings can be change using variables given in parenthesis. \r\n\r\n+ `<space>.` and `<space>,` will switch layer forward and backward.\r\n  (`CUkeyNextLayer` and `CUkeyPrevLayer`)\r\n+ `<space>m` and `<space>n` will switch function in a layer forward and\r\n  backward. (`CUkeyNextFunction` and `CUkeyPrevFunction`)\r\n+ `<space>b` will jump to function definition (`CUkeyJumpToFunction`)\r\n+ `<space>v` will jump back (`CUkeyJumpBack`)\r\n+ `<space>\/` will highlight function name in vim window (`CUkeyHighlightFunction`)\r\n\r\n## _Code Upstairs_ Project Houses ##\r\n\r\n* [vim plugin at vim.org](http:\/\/www.vim.org\/scripts\/script.php?script_id=4498)\r\n* [at github](http:\/\/github.com\/wyderkat\/code_upstairs)\r\n* [at my website](http:\/\/www.cofoh.com\/code_upstairs)\r\n","install_details":"### Installation ###\r\nUnpack `cu-vim-VERSION.tgz` and the content of extracted `code_upstairs-VERSION` directory move\r\nto your `~\/.vim\/` or whole directory to Pathogen corner. \r\n\r\nCurrent version _Code Upstairs_ works only with **C** and **Python**. \r\nFor **C** you need to have installed `cscope` and\r\nfor **Python** you need `cscope` along with `pycscope` \r\n\r\nVim has to be compiled with `python` support. ","5":"### Installation ###\r\nUnpack `cu-vim-VERSION.tgz` and the content of extracted `code_upstairs-VERSION` directory move\r\nto your `~\/.vim\/` or whole directory to Pathogen corner. \r\n\r\nCurrent version _Code Upstairs_ works only with **C** and **Python**. \r\nFor **C** you need to have installed `cscope` and\r\nfor **Python** you need `cscope` along with `pycscope` \r\n\r\nVim has to be compiled with `python` support. ","first_name":"Tomasz","6":"Tomasz","last_name":"Wyderka","7":"Wyderka","releases":[{"0":"4498","vim_version":"7.0","1":"7.0","script_version":"0.4","2":"0.4","version_comment":"New functionality remembering last layer and function. JumpBack keybinding.","3":"New functionality remembering last layer and function. JumpBack keybinding.","package":"cu-vim-0.4.tgz","4":"cu-vim-0.4.tgz","src_id":"19758","5":"19758","creation_date":"1365020682","6":"1365020682"},{"0":"4498","vim_version":"7.0","1":"7.0","script_version":"0.3","2":"0.3","version_comment":"Auto-enabling status line. Proper failures handling (when cscope missing, etc).","3":"Auto-enabling status line. Proper failures handling (when cscope missing, etc).","package":"cu-vim-0.3.tgz","4":"cu-vim-0.3.tgz","src_id":"19740","5":"19740","creation_date":"1364813556","6":"1364813556"},{"0":"4498","vim_version":"7.0","1":"7.0","script_version":"0.2","2":"0.2","version_comment":"Fixed missing \"plugin\" directory","3":"Fixed missing \"plugin\" directory","package":"cu-vim-0.2.tgz","4":"cu-vim-0.2.tgz","src_id":"19731","5":"19731","creation_date":"1364704887","6":"1364704887"},{"0":"4498","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"cu-vim-0.1.tgz","4":"cu-vim-0.1.tgz","src_id":"19730","5":"19730","creation_date":"1364669073","6":"1364669073"}]},"4497":{"script_id":"4497","0":"4497","script_name":"Git Support","1":"Git Support","script_type":"utility","2":"utility","summary":"Inspect the state of a repository and execute Git commands without leaving Vim.","3":"Inspect the state of a repository and execute Git commands without leaving Vim.","description":"Integration of Git for Vim\/gVim:\r\n- use Git from within Vim and eliminate the need for context switches\r\n- quickly add the file in the current buffer or show its diff\r\n- the output of commands like \"git status\" is redirected into buffers\r\n- ... the commit can be manipulated from right there\r\n- show the stash, logs, branches, tags, remotes, ...\r\n- show the Git help in a buffer, or open it in the browser\r\n- each buffer comes with a short help: press <SHIFT+F1>\r\n\r\n- comes with a menu, which also serves as an overview of the plug-in's functionality\r\n- custom menu for often used combination of arguments\r\n- configurable syntax highlighting designed to match Git's own highlighting\r\n- automatic folds for diffs and logs\r\n\r\nSome screen shots :  https:\/\/wolfgangmehner.github.io\/vim-plugins\/gitsupport.html\r\n\r\nFor plug-in managers :  https:\/\/github.com\/WolfgangMehner\/git-support\r\n\r\nThe help file online :  https:\/\/wolfgangmehner.github.io\/vim-plugins\/doc\/gitsupport.html\r\n\r\nDOCUMENTATION\r\n--------------------------------------------------------\r\nThis plug-in comes with a help file (gitsupport.txt). Read it with\r\n\r\n    :help git-support\r\n\r\nGitHub\r\n--------------------------------------------------------\r\nGit Support is on GitHub. We are happy to receive your questions, suggestions, and bug reports here:\r\n\r\n    https:\/\/github.com\/WolfgangMehner\/git-support","4":"Integration of Git for Vim\/gVim:\r\n- use Git from within Vim and eliminate the need for context switches\r\n- quickly add the file in the current buffer or show its diff\r\n- the output of commands like \"git status\" is redirected into buffers\r\n- ... the commit can be manipulated from right there\r\n- show the stash, logs, branches, tags, remotes, ...\r\n- show the Git help in a buffer, or open it in the browser\r\n- each buffer comes with a short help: press <SHIFT+F1>\r\n\r\n- comes with a menu, which also serves as an overview of the plug-in's functionality\r\n- custom menu for often used combination of arguments\r\n- configurable syntax highlighting designed to match Git's own highlighting\r\n- automatic folds for diffs and logs\r\n\r\nSome screen shots :  https:\/\/wolfgangmehner.github.io\/vim-plugins\/gitsupport.html\r\n\r\nFor plug-in managers :  https:\/\/github.com\/WolfgangMehner\/git-support\r\n\r\nThe help file online :  https:\/\/wolfgangmehner.github.io\/vim-plugins\/doc\/gitsupport.html\r\n\r\nDOCUMENTATION\r\n--------------------------------------------------------\r\nThis plug-in comes with a help file (gitsupport.txt). Read it with\r\n\r\n    :help git-support\r\n\r\nGitHub\r\n--------------------------------------------------------\r\nGit Support is on GitHub. We are happy to receive your questions, suggestions, and bug reports here:\r\n\r\n    https:\/\/github.com\/WolfgangMehner\/git-support","install_details":"Copy the zip archive git-support.zip to $HOME\/.vim\/ (Linux\/Unix) or\r\n$HOME\/vimfiles (Windows) and run:\r\n    unzip git-support.zip\r\n\r\nRedo the helptags (Linux\/Windows):\r\n    :helptags $HOME\/.vim\/doc\/\r\n    :helptags $HOME\\vimfiles\\doc\\\r\n\r\nWindows: Set the correct executable. See git-support\/README.gitsupport or: \r\n    :help g:Git_Executable\r\n(the default is \"C:\\Program Files\\Git\\bin\\git.exe\")\r\n\r\nConsider configuring the syntax highlighting. By default, the syntax highlighting\r\nuses Vim's own syntax categories. See git-support\/README.gitsupport or\r\ngit-support\/rc\/additions.vimrc for information on how to configure the syntax\r\nhighlighting to look more like Git's output.","5":"Copy the zip archive git-support.zip to $HOME\/.vim\/ (Linux\/Unix) or\r\n$HOME\/vimfiles (Windows) and run:\r\n    unzip git-support.zip\r\n\r\nRedo the helptags (Linux\/Windows):\r\n    :helptags $HOME\/.vim\/doc\/\r\n    :helptags $HOME\\vimfiles\\doc\\\r\n\r\nWindows: Set the correct executable. See git-support\/README.gitsupport or: \r\n    :help g:Git_Executable\r\n(the default is \"C:\\Program Files\\Git\\bin\\git.exe\")\r\n\r\nConsider configuring the syntax highlighting. By default, the syntax highlighting\r\nuses Vim's own syntax categories. See git-support\/README.gitsupport or\r\ngit-support\/rc\/additions.vimrc for information on how to configure the syntax\r\nhighlighting to look more like Git's output.","first_name":"Wolfgang","6":"Wolfgang","last_name":"Mehner","7":"Mehner","releases":[{"0":"4497","vim_version":"8.0","1":"8.0","script_version":"0.9.4-1","2":"0.9.4-1","version_comment":"- Add command :GitTerm to execute Git in a terminal window (requires +terminal).\r\n- Improve :GitGrep (in case +conceal is available).\r\n- Improve :GitLog to support ranges.\r\n- Add maps to these buffers: branch, status\r\n- Adapt for running under Neovim more smoothly.\r\n- Minor changes.","3":"- Add command :GitTerm to execute Git in a terminal window (requires +terminal).\r\n- Improve :GitGrep (in case +conceal is available).\r\n- Improve :GitLog to support ranges.\r\n- Add maps to these buffers: branch, status\r\n- Adapt for running under Neovim more smoothly.\r\n- Minor changes.","package":"git-support.zip","4":"git-support.zip","src_id":"27382","5":"27382","creation_date":"1606077113","6":"1606077113"},{"0":"4497","vim_version":"7.3","1":"7.3","script_version":"0.9.3","2":"0.9.3","version_comment":"- Add: The diff buffer can be use to add\/reset chunks, added new maps.\r\n- Add: Extended command-line completion to handle options for Git commands.\r\n- Add: New maps for the buffer: log\r\n- Add: Command :GitEdit to quickly jump to configuration files.\r\n- Change: The status buffer can handle renamed files.\r\n- Improve syntax highlighting.\r\n- Minor changes.","3":"- Add: The diff buffer can be use to add\/reset chunks, added new maps.\r\n- Add: Extended command-line completion to handle options for Git commands.\r\n- Add: New maps for the buffer: log\r\n- Add: Command :GitEdit to quickly jump to configuration files.\r\n- Change: The status buffer can handle renamed files.\r\n- Improve syntax highlighting.\r\n- Minor changes.","package":"git-support.zip","4":"git-support.zip","src_id":"24382","5":"24382","creation_date":"1469284274","6":"1469284274"},{"0":"4497","vim_version":"7.0","1":"7.0","script_version":"0.9.2","2":"0.9.2","version_comment":"- Added: Command :GitBash for running interactive Git commands.\r\n- Added: Command :GitSlist as a shorthand for \":GitStash list\".\r\n- Added: New maps for the buffers: branch, remote, stash, tag\r\n- Added: New maps for the buffer: status\r\n- Added: New setting g:Git_BinPath, to set the path to the executables.\r\n- Added: Command-line completion for subcommands, branches, remotes, tags.\r\n- Changed: :GitShow shows different objects in an according way.\r\n- Changed: :GitCommitFile updates the file before committing.\r\n- Changed: :GitHelp shows man page text with appropriate width.\r\n- Changed: :GitStatus can be restricted to a path by passing it as an argument.\r\n- Changed: :GitStatus respects the option 'status.relativePaths'.\r\n- Changed: :GitStatus can work with changes introduced by Git version 1.8.5.\r\n- Changed: Calling :GitCheckout and :GitReset without arguments\r\n  (see g:Git_CheckoutExpandEmpty and g:Git_ResetExpandEmpty).\r\n- Fixed: Jumping to files was still not working correctly.\r\n- Fixed: Better compatibility with custom mappings\r\n  (use \"normal!\", \"noremap\" and \"noremenu\" consistently).\r\n- Improved syntax highlighting.\r\n- Minor changes.","3":"- Added: Command :GitBash for running interactive Git commands.\r\n- Added: Command :GitSlist as a shorthand for \":GitStash list\".\r\n- Added: New maps for the buffers: branch, remote, stash, tag\r\n- Added: New maps for the buffer: status\r\n- Added: New setting g:Git_BinPath, to set the path to the executables.\r\n- Added: Command-line completion for subcommands, branches, remotes, tags.\r\n- Changed: :GitShow shows different objects in an according way.\r\n- Changed: :GitCommitFile updates the file before committing.\r\n- Changed: :GitHelp shows man page text with appropriate width.\r\n- Changed: :GitStatus can be restricted to a path by passing it as an argument.\r\n- Changed: :GitStatus respects the option 'status.relativePaths'.\r\n- Changed: :GitStatus can work with changes introduced by Git version 1.8.5.\r\n- Changed: Calling :GitCheckout and :GitReset without arguments\r\n  (see g:Git_CheckoutExpandEmpty and g:Git_ResetExpandEmpty).\r\n- Fixed: Jumping to files was still not working correctly.\r\n- Fixed: Better compatibility with custom mappings\r\n  (use \"normal!\", \"noremap\" and \"noremenu\" consistently).\r\n- Improved syntax highlighting.\r\n- Minor changes.","package":"git-support.zip","4":"git-support.zip","src_id":"22574","5":"22574","creation_date":"1414426954","6":"1414426954"},{"0":"4497","vim_version":"7.0","1":"7.0","script_version":"0.9.1","2":"0.9.1","version_comment":"- Added: New maps for the buffers: blame, diff and status\r\n- Changed: Commands which open a file will jump to its window, if one exists.\r\n- Changed: Opening a diff in the status buffer (see g:Git_StatusStagedOpenDiff).\r\n- Changed: Calling :GitDiff without arguments (see g:Git_DiffExpandEmpty).\r\n- Added: Command :GitGrep and :GitGrepTop.\r\n- Added: Command :GitMergeUpstream.\r\n- Added: Custom menu (see g:Git_CustomMenu).\r\n- Added: Cmd. line completion for :GitHelp.\r\n- Added: Command :GitBlame supports ranges.\r\n- Fixed: Jumping from the status buffer to a file did not work when the working directory changed.\r\n- Changed: After jumping to a file\/buffer, open all folds under the cursor (see g:Git_OpenFoldAfterJump).\r\n- Changed: Default executables for Windows.\r\n- Added: Command :GitK.\r\n- Added: Settings g:Git_GitKExecutable and g:Git_GitKScript.\r\n- Improved syntax highlighting.\r\n- Minor bugfixes and improvements.","3":"- Added: New maps for the buffers: blame, diff and status\r\n- Changed: Commands which open a file will jump to its window, if one exists.\r\n- Changed: Opening a diff in the status buffer (see g:Git_StatusStagedOpenDiff).\r\n- Changed: Calling :GitDiff without arguments (see g:Git_DiffExpandEmpty).\r\n- Added: Command :GitGrep and :GitGrepTop.\r\n- Added: Command :GitMergeUpstream.\r\n- Added: Custom menu (see g:Git_CustomMenu).\r\n- Added: Cmd. line completion for :GitHelp.\r\n- Added: Command :GitBlame supports ranges.\r\n- Fixed: Jumping from the status buffer to a file did not work when the working directory changed.\r\n- Changed: After jumping to a file\/buffer, open all folds under the cursor (see g:Git_OpenFoldAfterJump).\r\n- Changed: Default executables for Windows.\r\n- Added: Command :GitK.\r\n- Added: Settings g:Git_GitKExecutable and g:Git_GitKScript.\r\n- Improved syntax highlighting.\r\n- Minor bugfixes and improvements.","package":"git-support.zip","4":"git-support.zip","src_id":"21252","5":"21252","creation_date":"1388313188","6":"1388313188"},{"0":"4497","vim_version":"7.0","1":"7.0","script_version":"0.9","2":"0.9","version_comment":"Initial upload","3":"Initial upload","package":"git-support.zip","4":"git-support.zip","src_id":"19729","5":"19729","creation_date":"1364667561","6":"1364667561"}]},"4496":{"script_id":"4496","0":"4496","script_name":"colorful-statusline","1":"colorful-statusline","script_type":"utility","2":"utility","summary":"A colorful statusline for vim.","3":"A colorful statusline for vim.","description":"colorful-statusline\r\n===================\r\n\r\nA colorful statusline for vim\r\n\r\nThis is a modify of http:\/\/www.vim.org\/scripts\/script.php?script_id=2879 .\r\n\r\nGitHub: https:\/\/github.com\/sangwich\/colorful-statusline\r\n\r\nIt will not be dependent on the grey2 colortheme.\r\n\r\nPreview : \r\n\r\nhttp:\/\/photo.blog.sina.com.cn\/photo\/5bc27867t78c51c25aefd\r\n\r\nhttp:\/\/photo.blog.sina.com.cn\/photo\/53ba4e4btd927842245ac\r\n\r\n\r\nWhen you switch colorscheme, the background of statusline changes too. \r\n\r\nYou should source colorful-statusline.vim by manual to recover it. \r\n\r\n         Like: \r\n         \r\n                  :colo underwater \r\n                  :source c:\/vim\/vimfiles\/plugin\/colorful-statusline.vim \r\n                  or \r\n                  :source ~\/.vim\/plugin\/colorful-statusline.vim \r\n\r\n         In fact, you can use autocmd in _vimrc to simplify this: \r\n         \r\n                  autocmd! ColorScheme *  source c:\/vim\/vimfiles\/plugin\/colorful-statusline.vim \r\n                  or \r\n                  autocmd! ColorScheme *  source ~\/.vim\/plugin\/colorful-statusline.vim\r\n \r\n","4":"colorful-statusline\r\n===================\r\n\r\nA colorful statusline for vim\r\n\r\nThis is a modify of http:\/\/www.vim.org\/scripts\/script.php?script_id=2879 .\r\n\r\nGitHub: https:\/\/github.com\/sangwich\/colorful-statusline\r\n\r\nIt will not be dependent on the grey2 colortheme.\r\n\r\nPreview : \r\n\r\nhttp:\/\/photo.blog.sina.com.cn\/photo\/5bc27867t78c51c25aefd\r\n\r\nhttp:\/\/photo.blog.sina.com.cn\/photo\/53ba4e4btd927842245ac\r\n\r\n\r\nWhen you switch colorscheme, the background of statusline changes too. \r\n\r\nYou should source colorful-statusline.vim by manual to recover it. \r\n\r\n         Like: \r\n         \r\n                  :colo underwater \r\n                  :source c:\/vim\/vimfiles\/plugin\/colorful-statusline.vim \r\n                  or \r\n                  :source ~\/.vim\/plugin\/colorful-statusline.vim \r\n\r\n         In fact, you can use autocmd in _vimrc to simplify this: \r\n         \r\n                  autocmd! ColorScheme *  source c:\/vim\/vimfiles\/plugin\/colorful-statusline.vim \r\n                  or \r\n                  autocmd! ColorScheme *  source ~\/.vim\/plugin\/colorful-statusline.vim\r\n \r\n","install_details":"copy it into ~\/.vim\/plugin or ~\/_vimfiles\/plugin\r\n\r\nenjoy! ","5":"copy it into ~\/.vim\/plugin or ~\/_vimfiles\/plugin\r\n\r\nenjoy! ","first_name":"z","6":"z","last_name":"jx","7":"jx","releases":[{"0":"4496","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"colorful-statusline.vim","4":"colorful-statusline.vim","src_id":"19728","5":"19728","creation_date":"1364664852","6":"1364664852"}]},"4495":{"script_id":"4495","0":"4495","script_name":"molokai_nancle","1":"molokai_nancle","script_type":"color scheme","2":"color scheme","summary":"Modify the VertSplit color of the original one","3":"Modify the VertSplit color of the original one","description":"Modify the VertSplit color of the original one, which makes it more cool","4":"Modify the VertSplit color of the original one, which makes it more cool","install_details":"put it in your color dir","5":"put it in your color dir","first_name":"7","6":"7","last_name":"LI","7":"LI","releases":[{"0":"4495","vim_version":"7.0","1":"7.0","script_version":"1.0.1","2":"1.0.1","version_comment":"Modified the vertical split","3":"Modified the vertical split","package":"molokai_nancle.vim","4":"molokai_nancle.vim","src_id":"19735","5":"19735","creation_date":"1364742090","6":"1364742090"},{"0":"4495","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"molokai_nancle.vim","4":"molokai_nancle.vim","src_id":"19727","5":"19727","creation_date":"1364663526","6":"1364663526"}]},"4494":{"script_id":"4494","0":"4494","script_name":"Brolink.vim","1":"Brolink.vim","script_type":"utility","2":"utility","summary":"Live browser editing for Vim","3":"Live browser editing for Vim","description":"Edit your web projects in Vim, with instant updates in the browser. Fast, easy, simple.\r\n\r\nInfo and latest version --> https:\/\/github.com\/jaxbot\/brolink.vim","4":"Edit your web projects in Vim, with instant updates in the browser. Fast, easy, simple.\r\n\r\nInfo and latest version --> https:\/\/github.com\/jaxbot\/brolink.vim","install_details":"","5":"","first_name":"Jonathan","6":"Jonathan","last_name":"Warner","7":"Warner","releases":[{"0":"4494","vim_version":"7.0","1":"7.0","script_version":"2.0","2":"2.0","version_comment":"Updated, rebuilt most of it","3":"Updated, rebuilt most of it","package":"brolink.vim-master.zip","4":"brolink.vim-master.zip","src_id":"21663","5":"21663","creation_date":"1395703909","6":"1395703909"},{"0":"4494","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"brolink.vim.zip","4":"brolink.vim.zip","src_id":"19725","5":"19725","creation_date":"1364581162","6":"1364581162"}]},"4493":{"script_id":"4493","0":"4493","script_name":"vim-rusmode","1":"vim-rusmode","script_type":"utility","2":"utility","summary":"Bind pressing russian key in normal mode to toggle layout and repeat same key.","3":"Bind pressing russian key in normal mode to toggle layout and repeat same key.","description":"https:\/\/github.com\/evindor\/vim-rusmode\r\nRusmode.vim\r\n\r\nNo Windows support for now.\r\n\r\nWhen you press russian key in normal mode this script will change your system layout and repeat same key press in appropriate language.\r\n\r\nSettings:\r\n\r\nSet layout to switch to. Defaults to 'U.S.'.\r\nlet g:rusmode_normal_layout='U.S.'\r\nYou can find out the name of layout by switching on it and running changeInput binary in plugin directory.\r\n\r\nAutomatically toggle to normal layout on leaving the insert mode. Defaults to 0.\r\nlet g:rusmode_autotoggle_insertleave=1","4":"https:\/\/github.com\/evindor\/vim-rusmode\r\nRusmode.vim\r\n\r\nNo Windows support for now.\r\n\r\nWhen you press russian key in normal mode this script will change your system layout and repeat same key press in appropriate language.\r\n\r\nSettings:\r\n\r\nSet layout to switch to. Defaults to 'U.S.'.\r\nlet g:rusmode_normal_layout='U.S.'\r\nYou can find out the name of layout by switching on it and running changeInput binary in plugin directory.\r\n\r\nAutomatically toggle to normal layout on leaving the insert mode. Defaults to 0.\r\nlet g:rusmode_autotoggle_insertleave=1","install_details":"Install with Vundle or Pathogen.\r\n\r\nLinux users need to provide correct commands to get and set current layout:\r\n\r\nlet g:rusmode_get_layout_command = 'setxkbmap -print | grep xkb_symbols | awk \\'{split($0,arr,\"+\")} END{print arr[2]}\\''\r\nlet g:rusmode_set_layout_command = 'setxkbmap -option \"grp:ctrl_shift_toggle,grp_led:scroll\" -layout \"us,ru\"'\r\nlet g:rusmode_normal_layout='us'\r\n\r\nThe following was tested under Ubuntu 12.10","5":"Install with Vundle or Pathogen.\r\n\r\nLinux users need to provide correct commands to get and set current layout:\r\n\r\nlet g:rusmode_get_layout_command = 'setxkbmap -print | grep xkb_symbols | awk \\'{split($0,arr,\"+\")} END{print arr[2]}\\''\r\nlet g:rusmode_set_layout_command = 'setxkbmap -option \"grp:ctrl_shift_toggle,grp_led:scroll\" -layout \"us,ru\"'\r\nlet g:rusmode_normal_layout='us'\r\n\r\nThe following was tested under Ubuntu 12.10","first_name":"Arseny","6":"Arseny","last_name":"Zarechnev","7":"Zarechnev","releases":[{"0":"4493","vim_version":"7.0","1":"7.0","script_version":"0.3.1","2":"0.3.1","version_comment":"Handle dot and slash in all layouts;","3":"Handle dot and slash in all layouts;","package":"vim-rusmode.zip","4":"vim-rusmode.zip","src_id":"19755","5":"19755","creation_date":"1364993682","6":"1364993682"},{"0":"4493","vim_version":"7.0","1":"7.0","script_version":"0.3","2":"0.3","version_comment":"Linux support;\r\nSample commands;","3":"Linux support;\r\nSample commands;","package":"vim-rusmode.zip","4":"vim-rusmode.zip","src_id":"19749","5":"19749","creation_date":"1364910025","6":"1364910025"},{"0":"4493","vim_version":"7.0","1":"7.0","script_version":"0.2","2":"0.2","version_comment":"Fixed counts and sequences;\r\nAdded user setting for default layout;\r\nAdded user setting for layout switching automatically on leaving insert mode.","3":"Fixed counts and sequences;\r\nAdded user setting for default layout;\r\nAdded user setting for layout switching automatically on leaving insert mode.","package":"vim-rusmode.zip","4":"vim-rusmode.zip","src_id":"19734","5":"19734","creation_date":"1364729896","6":"1364729896"},{"0":"4493","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"vim-rusmode.zip","4":"vim-rusmode.zip","src_id":"19724","5":"19724","creation_date":"1364568107","6":"1364568107"}]},"4492":{"script_id":"4492","0":"4492","script_name":"mercury","1":"mercury","script_type":"utility","2":"utility","summary":"execute any fragment of code directly from vim","3":"execute any fragment of code directly from vim","description":"mercury allows you to take a fragment of code from some source (current line, selection, buffer), execute the code intelligently, and then write the result to some destination (message window, selection, register, new split).\r\n\r\nFeatures include:\r\n\r\n * choose the correct interpreter with the correct switches, given the filetype.\r\n * execute it in a separate thread and terminate it after a timeout, so an endless loop will not freeze vim.\r\n * some language specific smartness (e.g. handling imports).\r\n\r\nCurrently supports python, ruby and javascript (using node) with more to come soon, hopefully.\r\n\r\nFor more information, head over to github: https:\/\/github.com\/nielsmadan\/mercury","4":"mercury allows you to take a fragment of code from some source (current line, selection, buffer), execute the code intelligently, and then write the result to some destination (message window, selection, register, new split).\r\n\r\nFeatures include:\r\n\r\n * choose the correct interpreter with the correct switches, given the filetype.\r\n * execute it in a separate thread and terminate it after a timeout, so an endless loop will not freeze vim.\r\n * some language specific smartness (e.g. handling imports).\r\n\r\nCurrently supports python, ruby and javascript (using node) with more to come soon, hopefully.\r\n\r\nFor more information, head over to github: https:\/\/github.com\/nielsmadan\/mercury","install_details":"mercury requires venom, which in turn requires vim to be compiled with python support (most vim distributions are). Vundle or pathogen are highly recommended for installation.\r\n\r\nVundle:\r\n\r\n    Bundle 'nielsmadan\/venom'\r\n    Bundle 'nielsmadan\/mercury'\r\n\r\nFor what it's worth, the order actually does not matter.\r\n\r\nPathogen:\r\n\r\nUnzip mercury.zip and venom.zip into your pathogen directory. You can get venom from here: http:\/\/www.vim.org\/scripts\/script.php?script_id=4491","5":"mercury requires venom, which in turn requires vim to be compiled with python support (most vim distributions are). Vundle or pathogen are highly recommended for installation.\r\n\r\nVundle:\r\n\r\n    Bundle 'nielsmadan\/venom'\r\n    Bundle 'nielsmadan\/mercury'\r\n\r\nFor what it's worth, the order actually does not matter.\r\n\r\nPathogen:\r\n\r\nUnzip mercury.zip and venom.zip into your pathogen directory. You can get venom from here: http:\/\/www.vim.org\/scripts\/script.php?script_id=4491","first_name":"Niels","6":"Niels","last_name":"Madan","7":"Madan","releases":[{"0":"4492","vim_version":"7.3","1":"7.3","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"mercury.zip","4":"mercury.zip","src_id":"19722","5":"19722","creation_date":"1364557045","6":"1364557045"}]},"4491":{"script_id":"4491","0":"4491","script_name":"venom","1":"venom","script_type":"utility","2":"utility","summary":"vim python interface extension","3":"vim python interface extension","description":"This is a possibly crazy project to extend the python interface of vim to the point where it's possible to write plugins in pure python (without using eval or command or knowing any vimscript, really).\r\n\r\nIt's very much work in progress at the moment, and this upload is just here to support plugins that use it, currently just vimscript #4492\r\n\r\nIt doesn't do anything by itself and it's not in a state where anyone else can build anything on top.\r\n\r\nIf you are curious, you can have a look at the code on github, too: https:\/\/github.com\/nielsmadan\/venom\r\n","4":"This is a possibly crazy project to extend the python interface of vim to the point where it's possible to write plugins in pure python (without using eval or command or knowing any vimscript, really).\r\n\r\nIt's very much work in progress at the moment, and this upload is just here to support plugins that use it, currently just vimscript #4492\r\n\r\nIt doesn't do anything by itself and it's not in a state where anyone else can build anything on top.\r\n\r\nIf you are curious, you can have a look at the code on github, too: https:\/\/github.com\/nielsmadan\/venom\r\n","install_details":"vundle or pathogen are highly recommended.\r\n\r\nFor vundle, add Bundle 'nielsmadan\/venom' to your .vimrc, for pathogen unzip venom.zip into your pathogen directory.","5":"vundle or pathogen are highly recommended.\r\n\r\nFor vundle, add Bundle 'nielsmadan\/venom' to your .vimrc, for pathogen unzip venom.zip into your pathogen directory.","first_name":"Niels","6":"Niels","last_name":"Madan","7":"Madan","releases":[{"0":"4491","vim_version":"7.3","1":"7.3","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"venom.zip","4":"venom.zip","src_id":"19721","5":"19721","creation_date":"1364556611","6":"1364556611"}]},"4490":{"script_id":"4490","0":"4490","script_name":"QFGrep.vim","1":"QFGrep.vim","script_type":"utility","2":"utility","summary":"A plugin to filter Quickfix entries","3":"A plugin to filter Quickfix entries","description":"##QFGrep\r\n\r\nThe QFGrep plugin would be helpful when you got a lot of entries in Quickfix.  For example, you did an Ack\/Grep with a not strict criteria. QFGrep can do further filtering for you, so that you could narrow your focus and jump to the right file right line quickly. At any time you could restore the original Quickfix entries. \r\n\r\nprojectHome & screencast: https:\/\/github.com\/sk1418\/QFGrep\r\n\r\n##Features\r\n\r\n- filter(Grep) entries in Quickfix\r\n- restore original Quickfix entries\r\n\r\n##Usage\r\n- fill Quickfix window with some entries (grep, vimgrep, ack or make),move curosr to quickfix buffer\r\n- `<Leader>g` input pattern to do further filtering\r\n- `<Leader>r` restore the Quickfix with original entries\r\n- `<Leader>v` input pattern to do further inverted filtering (like grep -v)\r\n- check the GIF animation on project homepage https:\/\/github.com\/sk1418\/QFGrep\r\n\r\n##Customization\r\n\r\n- mapping customization\r\n- message color-highligting customization\r\n- `:h QFGrep` to check details","4":"##QFGrep\r\n\r\nThe QFGrep plugin would be helpful when you got a lot of entries in Quickfix.  For example, you did an Ack\/Grep with a not strict criteria. QFGrep can do further filtering for you, so that you could narrow your focus and jump to the right file right line quickly. At any time you could restore the original Quickfix entries. \r\n\r\nprojectHome & screencast: https:\/\/github.com\/sk1418\/QFGrep\r\n\r\n##Features\r\n\r\n- filter(Grep) entries in Quickfix\r\n- restore original Quickfix entries\r\n\r\n##Usage\r\n- fill Quickfix window with some entries (grep, vimgrep, ack or make),move curosr to quickfix buffer\r\n- `<Leader>g` input pattern to do further filtering\r\n- `<Leader>r` restore the Quickfix with original entries\r\n- `<Leader>v` input pattern to do further inverted filtering (like grep -v)\r\n- check the GIF animation on project homepage https:\/\/github.com\/sk1418\/QFGrep\r\n\r\n##Customization\r\n\r\n- mapping customization\r\n- message color-highligting customization\r\n- `:h QFGrep` to check details","install_details":"extract the archive to ~\/.vim","5":"extract the archive to ~\/.vim","first_name":"Kent","6":"Kent","last_name":"Yuan","7":"Yuan","releases":[{"0":"4490","vim_version":"7.3","1":"7.3","script_version":"1.1.0","2":"1.1.0","version_comment":"version 1.1.0                2014-06-14~\r\n    - add QFGrepPat and QFGrepPatV command, by pass interactive `input()`\r\n    - create `<Plug>` mappings, remove global mapping variable","3":"version 1.1.0                2014-06-14~\r\n    - add QFGrepPat and QFGrepPatV command, by pass interactive `input()`\r\n    - create `<Plug>` mappings, remove global mapping variable","package":"QFGrep.tar.gz","4":"QFGrep.tar.gz","src_id":"22042","5":"22042","creation_date":"1403015277","6":"1403015277"},{"0":"4490","vim_version":"7.3","1":"7.3","script_version":"1.0.3","2":"1.0.3","version_comment":"version 1.0.3                2013-11-05~\r\n    - move the logic codes to autoload\r\n    - rename function names\r\n    - enhance formatting of documentation","3":"version 1.0.3                2013-11-05~\r\n    - move the logic codes to autoload\r\n    - rename function names\r\n    - enhance formatting of documentation","package":"QFGrep.tar.gz","4":"QFGrep.tar.gz","src_id":"21009","5":"21009","creation_date":"1383743787","6":"1383743787"},{"0":"4490","vim_version":"7.3","1":"7.3","script_version":"1.0.1","2":"1.0.1","version_comment":"- bugfixing, https:\/\/github.com\/sk1418\/QFGrep\/issues\/2\r\n- add feature, invert filtering, like grep -v","3":"- bugfixing, https:\/\/github.com\/sk1418\/QFGrep\/issues\/2\r\n- add feature, invert filtering, like grep -v","package":"QFGrep.tar.gz","4":"QFGrep.tar.gz","src_id":"20733","5":"20733","creation_date":"1377877949","6":"1377877949"},{"0":"4490","vim_version":"7.2","1":"7.2","script_version":"1.0.0","2":"1.0.0","version_comment":"Initial upload","3":"Initial upload","package":"QFGrep.tar.gz","4":"QFGrep.tar.gz","src_id":"19719","5":"19719","creation_date":"1364505004","6":"1364505004"}]},"4489":{"script_id":"4489","0":"4489","script_name":"last256","1":"last256","script_type":"color scheme","2":"color scheme","summary":"A dark vim color-scheme, based on vim-hybrid","3":"A dark vim color-scheme, based on vim-hybrid","description":"\r\nlast256 is a dark vim color-scheme, it was created based on vim-hybrid (https:\/\/github.com\/w0ng\/vim-hybrid).\r\n\r\n- Xresource color supports was removed\r\n- Some colors\/highlightings were changed, e.g. visual selection, cursorLine, background(`Normal`), some syntax ...\r\n- Some hi-groups were added: `FIXME`, `Important`, `MK1`, `MK2`,  `MK3`\r\n\r\nscreenshots and project home: https:\/\/github.com\/sk1418\/last256\r\n","4":"\r\nlast256 is a dark vim color-scheme, it was created based on vim-hybrid (https:\/\/github.com\/w0ng\/vim-hybrid).\r\n\r\n- Xresource color supports was removed\r\n- Some colors\/highlightings were changed, e.g. visual selection, cursorLine, background(`Normal`), some syntax ...\r\n- Some hi-groups were added: `FIXME`, `Important`, `MK1`, `MK2`,  `MK3`\r\n\r\nscreenshots and project home: https:\/\/github.com\/sk1418\/last256\r\n","install_details":"copy last256.vim to ~\/.vim\/colors\/ ","5":"copy last256.vim to ~\/.vim\/colors\/ ","first_name":"Kent","6":"Kent","last_name":"Yuan","7":"Yuan","releases":[{"0":"4489","vim_version":"7.0","1":"7.0","script_version":"1.1.0","2":"1.1.0","version_comment":" 2013-01-12   v1.1.0\r\n- adjusted many colors\r\n - fit terminal if terminal has solarized color scheme\r\n - add tabline colors\r\n - add new screenshot (github readme.md)","3":" 2013-01-12   v1.1.0\r\n- adjusted many colors\r\n - fit terminal if terminal has solarized color scheme\r\n - add tabline colors\r\n - add new screenshot (github readme.md)","package":"last256.vim","4":"last256.vim","src_id":"21311","5":"21311","creation_date":"1389562623","6":"1389562623"},{"0":"4489","vim_version":"7.3","1":"7.3","script_version":"1.0.0","2":"1.0.0","version_comment":"Initial upload","3":"Initial upload","package":"last256.vim","4":"last256.vim","src_id":"19717","5":"19717","creation_date":"1364501538","6":"1364501538"}]},"4488":{"script_id":"4488","0":"4488","script_name":"tbone.vim","1":"tbone.vim","script_type":"utility","2":"utility","summary":"tmux basics","3":"tmux basics","description":"Basic tmux support for Vim.\r\n\r\n* :Tmux lets you call any old tmux command (with really good tab complete).\r\n* :Tyank and :Tput give you direct access to tmux buffers.\r\n* :Twrite sends a chunk of text to another pane.  Give an argument like windowtitle.2, top-right, or last, or let it default to the previously given argument.\r\n* :Tattach lets you use a specific tmux session from outside of it.\r\n\r\nhttps:\/\/github.com\/tpope\/vim-tbone","4":"Basic tmux support for Vim.\r\n\r\n* :Tmux lets you call any old tmux command (with really good tab complete).\r\n* :Tyank and :Tput give you direct access to tmux buffers.\r\n* :Twrite sends a chunk of text to another pane.  Give an argument like windowtitle.2, top-right, or last, or let it default to the previously given argument.\r\n* :Tattach lets you use a specific tmux session from outside of it.\r\n\r\nhttps:\/\/github.com\/tpope\/vim-tbone","install_details":"Extract in ~\/.vim (~\\vimfiles on Windows).","5":"Extract in ~\/.vim (~\\vimfiles on Windows).","first_name":"Tim","6":"Tim","last_name":"Pope","7":"Pope","releases":[{"0":"4488","vim_version":"7.0","1":"7.0","script_version":"1.1","2":"1.1","version_comment":"Fix error on :Tattach.","3":"Fix error on :Tattach.","package":"tbone.zip","4":"tbone.zip","src_id":"19742","5":"19742","creation_date":"1364836726","6":"1364836726"},{"0":"4488","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"tbone.zip","4":"tbone.zip","src_id":"19709","5":"19709","creation_date":"1364361748","6":"1364361748"}]},"4487":{"script_id":"4487","0":"4487","script_name":"vim-signify","1":"vim-signify","script_type":"utility","2":"utility","summary":"Advanced plugin for showing VCS diffs in the SignColumn","3":"Advanced plugin for showing VCS diffs in the SignColumn","description":"NOTE: Get the latest updates via github: https:\/\/github.com\/mhinz\/vim-signify\r\n\r\nIf you like this plugin, star it on github!\r\n\r\n\r\n# vim-signify\r\n\r\nOr just: __sy__\r\n\r\nSy shows all added, deleted and modified lines since the last commit via Vim its\r\nsign column. It __supports several version control systems__.\r\n\r\nIt's __fast__, __highly configurable__ and __well documented__.\r\n\r\nFeatures:\r\n\r\n- supports git, mercurial, darcs, bazaar, subversion, cvs, rcs\r\n- quick jumping between changed lines\r\n- apart from signs there is also optional line highlighting\r\n- fully configurable through global variables (options and mappings)\r\n- optional preserving of signs from other plugins\r\n- you can toggle the plugin per buffer\r\n- exception lists for filetypes and filenames\r\n- good documentation\r\n\r\n- quick developer response! :-)\r\n\r\nLimits exist only in your mind!\r\n\r\n## What about vim-gitgutter?\r\n\r\nTo be honest, I don't understand why people always compare plugins like Sy to\r\nvim-gitgutter. I understand that it is by far the most known one, but primarily\r\nbecause it was featured on the Hacker News frontpage.\r\n\r\nDon't get me wrong, I don't intend to badmouth gitgutter, I even contributed to\r\nit once. (Granted, it was only a small fix.) And I'm glad about everyone\r\ncontributing to the Vim community, but there are two important facts one should\r\nconsider:\r\n\r\n1. There were other plugins providing the same functionality as gitgutter years\r\n   before its creation.\r\n\r\n1. Sy provides a superset of gitgutter.\r\n\r\nSo here is the short answer: The main difference is Sy its support for version\r\ncontrol systems other than git. Moreover, two of its design goals are speed and\r\nhigh configurability.\r\n\r\n## Sign explanation\r\n\r\n`+`\r\n\r\nA new line was added. The sign is shown on the same line as the new line.\r\n\r\n`_`\r\n\r\nA line was deleted. The sign is shown on the line above the deleted line. Special case: The first line was deleted. In this case the sign is shown on the same line.\r\n\r\n`!`\r\n\r\nA line was changed. Something was changed, but the amount of lines stayed the same. The sign is shown on the same line.\r\n\r\n`!_`\r\n\r\nA line was changed and one or more of the lines below were deleted. A combination of **!** and **_**. The sign is shown on the same line.\r\n\r\n## Longer introduction\r\n\r\n#### supports several version control systems\r\n\r\nThis plugin is based on the diffing features of the supported version control\r\nsystems. Since not all VCS support the same options, sometimes we have to fall\r\nback to the 'diff' executable.\r\n\r\nCurrent the following VCS are supported:\r\n\r\n- git\r\n- mercurial (hg)\r\n- bazaar (bzr)\r\n- darcs\r\n- subversion (svn)\r\n- cvs\r\n- rcs\r\n\r\n#### quick jumping between changed lines\r\n\r\nThere are mappings for jumping forth and back between changed lines (so-called\r\nhunks). The following example shows the default mappings and how to change them:\r\n\r\n```vim\r\nlet g:signify_mapping_next_hunk = '<leader>gj'\r\nlet g:signify_mapping_prev_hunk = '<leader>gk'\r\n```\r\n\r\nNote: In case you don't know about the mapleader, have a look at `:h mapleader`.\r\nThe default is the '\\' button.\r\n\r\n#### apart from signs there is also optional line highlighting\r\n\r\nSy shows you signs for changed lines. Moveover, you can enable highlighting of\r\nthe concerned lines:\r\n\r\n```vim\r\nlet g:signify_mapping_toggle_highlight = '<leader>gh'\r\n```\r\n\r\nYou can also change the highlighting classes for these lines. The defaults are:\r\n\r\n```vim\r\nlet g:signify_line_color_add    = 'DiffAdd'\r\nlet g:signify_line_color_delete = 'DiffDelete'\r\nlet g:signify_line_color_change = 'DiffChange'\r\n```\r\n\r\n#### you can toggle the plugin per buffer\r\n\r\nIn case you want to disable the plugin for the current buffer, you can toggle\r\nit:\r\n\r\n```vim\r\nlet g:signify_mapping_toggle = '<leader>gt'\r\n```\r\n\r\n#### exception lists for filetypes and filenames\r\n\r\nIf you want to disable Sy for certain kinds of filename or file types,\r\nyou explicitely have to create exception lists:\r\n\r\nExample:\r\n\r\n```vim\r\nlet g:signify_exceptions_filetype = [ 'vim', 'c' ]\r\nlet g:signify_exceptions_filename = [ '.vimrc' ]\r\n```\r\n\r\n#### good documentation\r\n\r\nYou should know by now!\r\n\r\n## Documentation\r\n\r\n`:h signify`\r\n\r\n## Configuration\r\n\r\nFor more info: `:h signify-options`\r\n\r\n__NOTE__: The shown assignments are only examples, not defaults.\r\n\r\n```vim\r\nlet g:signify_vcs_list = [ 'git', 'hg' ]\r\n\r\nlet g:signify_mapping_next_hunk = '<leader>gn'\r\nlet g:signify_mapping_prev_hunk = '<leader>gp'\r\n\r\nlet g:signify_mapping_toggle_highlight = '<leader>gh'\r\nlet g:signify_mapping_toggle           = '<leader>gt'\r\n\r\nlet g:signify_exceptions_filetype = [ 'vim', 'c' ]\r\nlet g:signify_exceptions_filename = [ '.vimrc' ]\r\n\r\nlet g:signify_sign_overwrite = 1\r\n\r\nlet g:signify_sign_add               = '+'\r\nlet g:signify_sign_delete            = '-'\r\nlet g:signify_sign_change            = '*'\r\nlet g:signify_sign_delete_first_line = '‾'\r\n\r\nlet g:signify_sign_color_guifg_add      = '#00ff00'\r\nlet g:signify_sign_color_guifg_delete   = '#ff0000'\r\nlet g:signify_sign_color_guifg_change   = '#ffff00'\r\nlet g:signify_sign_color_guibg          = '#111111'\r\n\r\nlet g:signify_sign_color_ctermfg_add    = 2\r\nlet g:signify_sign_color_ctermfg_delete = 1\r\nlet g:signify_sign_color_ctermfg_change = 3\r\nlet g:signify_sign_color_ctermbg        = 0\r\n\r\nlet g:signify_sign_color_group_add    = 'MyAdd'\r\nlet g:signify_sign_color_group_delete = 'MyDelete'\r\nlet g:signify_sign_color_group_change = 'MyChange'\r\n\r\nlet g:signify_line_color_add    = 'DiffAdd'\r\nlet g:signify_line_color_delete = 'DiffDelete'\r\nlet g:signify_line_color_change = 'DiffChange'\r\n\r\nlet g:signify_enable_cvs = 1\r\n\r\nlet g:signify_cursorhold_normal = 1\r\nlet g:signify_cursorhold_insert = 1\r\n```\r\n\r\n## Author\r\n\r\nMarco Hinz `<mh.codebro@gmail.com>`\r\n\r\n## License\r\n\r\nCopyright \u00c2\u00a9 2013 Marco Hinz. Revised BSD license.","4":"NOTE: Get the latest updates via github: https:\/\/github.com\/mhinz\/vim-signify\r\n\r\nIf you like this plugin, star it on github!\r\n\r\n\r\n# vim-signify\r\n\r\nOr just: __sy__\r\n\r\nSy shows all added, deleted and modified lines since the last commit via Vim its\r\nsign column. It __supports several version control systems__.\r\n\r\nIt's __fast__, __highly configurable__ and __well documented__.\r\n\r\nFeatures:\r\n\r\n- supports git, mercurial, darcs, bazaar, subversion, cvs, rcs\r\n- quick jumping between changed lines\r\n- apart from signs there is also optional line highlighting\r\n- fully configurable through global variables (options and mappings)\r\n- optional preserving of signs from other plugins\r\n- you can toggle the plugin per buffer\r\n- exception lists for filetypes and filenames\r\n- good documentation\r\n\r\n- quick developer response! :-)\r\n\r\nLimits exist only in your mind!\r\n\r\n## What about vim-gitgutter?\r\n\r\nTo be honest, I don't understand why people always compare plugins like Sy to\r\nvim-gitgutter. I understand that it is by far the most known one, but primarily\r\nbecause it was featured on the Hacker News frontpage.\r\n\r\nDon't get me wrong, I don't intend to badmouth gitgutter, I even contributed to\r\nit once. (Granted, it was only a small fix.) And I'm glad about everyone\r\ncontributing to the Vim community, but there are two important facts one should\r\nconsider:\r\n\r\n1. There were other plugins providing the same functionality as gitgutter years\r\n   before its creation.\r\n\r\n1. Sy provides a superset of gitgutter.\r\n\r\nSo here is the short answer: The main difference is Sy its support for version\r\ncontrol systems other than git. Moreover, two of its design goals are speed and\r\nhigh configurability.\r\n\r\n## Sign explanation\r\n\r\n`+`\r\n\r\nA new line was added. The sign is shown on the same line as the new line.\r\n\r\n`_`\r\n\r\nA line was deleted. The sign is shown on the line above the deleted line. Special case: The first line was deleted. In this case the sign is shown on the same line.\r\n\r\n`!`\r\n\r\nA line was changed. Something was changed, but the amount of lines stayed the same. The sign is shown on the same line.\r\n\r\n`!_`\r\n\r\nA line was changed and one or more of the lines below were deleted. A combination of **!** and **_**. The sign is shown on the same line.\r\n\r\n## Longer introduction\r\n\r\n#### supports several version control systems\r\n\r\nThis plugin is based on the diffing features of the supported version control\r\nsystems. Since not all VCS support the same options, sometimes we have to fall\r\nback to the 'diff' executable.\r\n\r\nCurrent the following VCS are supported:\r\n\r\n- git\r\n- mercurial (hg)\r\n- bazaar (bzr)\r\n- darcs\r\n- subversion (svn)\r\n- cvs\r\n- rcs\r\n\r\n#### quick jumping between changed lines\r\n\r\nThere are mappings for jumping forth and back between changed lines (so-called\r\nhunks). The following example shows the default mappings and how to change them:\r\n\r\n```vim\r\nlet g:signify_mapping_next_hunk = '<leader>gj'\r\nlet g:signify_mapping_prev_hunk = '<leader>gk'\r\n```\r\n\r\nNote: In case you don't know about the mapleader, have a look at `:h mapleader`.\r\nThe default is the '\\' button.\r\n\r\n#### apart from signs there is also optional line highlighting\r\n\r\nSy shows you signs for changed lines. Moveover, you can enable highlighting of\r\nthe concerned lines:\r\n\r\n```vim\r\nlet g:signify_mapping_toggle_highlight = '<leader>gh'\r\n```\r\n\r\nYou can also change the highlighting classes for these lines. The defaults are:\r\n\r\n```vim\r\nlet g:signify_line_color_add    = 'DiffAdd'\r\nlet g:signify_line_color_delete = 'DiffDelete'\r\nlet g:signify_line_color_change = 'DiffChange'\r\n```\r\n\r\n#### you can toggle the plugin per buffer\r\n\r\nIn case you want to disable the plugin for the current buffer, you can toggle\r\nit:\r\n\r\n```vim\r\nlet g:signify_mapping_toggle = '<leader>gt'\r\n```\r\n\r\n#### exception lists for filetypes and filenames\r\n\r\nIf you want to disable Sy for certain kinds of filename or file types,\r\nyou explicitely have to create exception lists:\r\n\r\nExample:\r\n\r\n```vim\r\nlet g:signify_exceptions_filetype = [ 'vim', 'c' ]\r\nlet g:signify_exceptions_filename = [ '.vimrc' ]\r\n```\r\n\r\n#### good documentation\r\n\r\nYou should know by now!\r\n\r\n## Documentation\r\n\r\n`:h signify`\r\n\r\n## Configuration\r\n\r\nFor more info: `:h signify-options`\r\n\r\n__NOTE__: The shown assignments are only examples, not defaults.\r\n\r\n```vim\r\nlet g:signify_vcs_list = [ 'git', 'hg' ]\r\n\r\nlet g:signify_mapping_next_hunk = '<leader>gn'\r\nlet g:signify_mapping_prev_hunk = '<leader>gp'\r\n\r\nlet g:signify_mapping_toggle_highlight = '<leader>gh'\r\nlet g:signify_mapping_toggle           = '<leader>gt'\r\n\r\nlet g:signify_exceptions_filetype = [ 'vim', 'c' ]\r\nlet g:signify_exceptions_filename = [ '.vimrc' ]\r\n\r\nlet g:signify_sign_overwrite = 1\r\n\r\nlet g:signify_sign_add               = '+'\r\nlet g:signify_sign_delete            = '-'\r\nlet g:signify_sign_change            = '*'\r\nlet g:signify_sign_delete_first_line = '‾'\r\n\r\nlet g:signify_sign_color_guifg_add      = '#00ff00'\r\nlet g:signify_sign_color_guifg_delete   = '#ff0000'\r\nlet g:signify_sign_color_guifg_change   = '#ffff00'\r\nlet g:signify_sign_color_guibg          = '#111111'\r\n\r\nlet g:signify_sign_color_ctermfg_add    = 2\r\nlet g:signify_sign_color_ctermfg_delete = 1\r\nlet g:signify_sign_color_ctermfg_change = 3\r\nlet g:signify_sign_color_ctermbg        = 0\r\n\r\nlet g:signify_sign_color_group_add    = 'MyAdd'\r\nlet g:signify_sign_color_group_delete = 'MyDelete'\r\nlet g:signify_sign_color_group_change = 'MyChange'\r\n\r\nlet g:signify_line_color_add    = 'DiffAdd'\r\nlet g:signify_line_color_delete = 'DiffDelete'\r\nlet g:signify_line_color_change = 'DiffChange'\r\n\r\nlet g:signify_enable_cvs = 1\r\n\r\nlet g:signify_cursorhold_normal = 1\r\nlet g:signify_cursorhold_insert = 1\r\n```\r\n\r\n## Author\r\n\r\nMarco Hinz `<mh.codebro@gmail.com>`\r\n\r\n## License\r\n\r\nCopyright \u00c2\u00a9 2013 Marco Hinz. Revised BSD license.","install_details":"I suggest using tpope's pathogen:\r\n\r\n- https:\/\/github.com\/tpope\/vim-pathogen\r\n\r\nAfterwards, just clone vim-signify into ~\/.vim\/bundle\/.","5":"I suggest using tpope's pathogen:\r\n\r\n- https:\/\/github.com\/tpope\/vim-pathogen\r\n\r\nAfterwards, just clone vim-signify into ~\/.vim\/bundle\/.","first_name":"Marco","6":"Marco","last_name":"Hinz","7":"Hinz","releases":[{"0":"4487","vim_version":"7.0","1":"7.0","script_version":"1.9","2":"1.9","version_comment":"- new option: g:signify_disable_by_default\r\n- improved hunk jumping code\r\n- color are set by groups only now (:h signify-colors)\r\n- add showcolors.bash\r\n- indicate number of deleted lines\r\n- various fixes\r\n- improved docs\r\n- update gif","3":"- new option: g:signify_disable_by_default\r\n- improved hunk jumping code\r\n- color are set by groups only now (:h signify-colors)\r\n- add showcolors.bash\r\n- indicate number of deleted lines\r\n- various fixes\r\n- improved docs\r\n- update gif","package":"vim-signify-1.9.tar.gz","4":"vim-signify-1.9.tar.gz","src_id":"20479","5":"20479","creation_date":"1372936477","6":"1372936477"},{"0":"4487","vim_version":"7.0","1":"7.0","script_version":"1.8","2":"1.8","version_comment":"- new option: g:signify_difftool\r\n- autocmd event juggling for improved sign redrawing\r\n- improved sanity checks\r\n- g:signify_update_on_bufenter = 0 per default now\r\n- CONTRIBUTING.md added\r\n- small fixes","3":"- new option: g:signify_difftool\r\n- autocmd event juggling for improved sign redrawing\r\n- improved sanity checks\r\n- g:signify_update_on_bufenter = 0 per default now\r\n- CONTRIBUTING.md added\r\n- small fixes","package":"vim-signify-1.8.tar.gz","4":"vim-signify-1.8.tar.gz","src_id":"20312","5":"20312","creation_date":"1370588030","6":"1370588030"},{"0":"4487","vim_version":"7.0","1":"7.0","script_version":"1.7","2":"1.7","version_comment":"support for Fossil SCM, much improved cursorhold, remove ]c and [c mappings for non-VCS files, improved doc, lots of fixes and refactoring","3":"support for Fossil SCM, much improved cursorhold, remove ]c and [c mappings for non-VCS files, improved doc, lots of fixes and refactoring","package":"vim-signify-1.7.tar.gz","4":"vim-signify-1.7.tar.gz","src_id":"19822","5":"19822","creation_date":"1366105730","6":"1366105730"},{"0":"4487","vim_version":"7.0","1":"7.0","script_version":"1.6","2":"1.6","version_comment":"fix sign overwriting, fix sign text options, handle return values of bzr properly","3":"fix sign overwriting, fix sign text options, handle return values of bzr properly","package":"vim-signify-1.6.tar.gz","4":"vim-signify-1.6.tar.gz","src_id":"19775","5":"19775","creation_date":"1365341481","6":"1365341481"},{"0":"4487","vim_version":"7.0","1":"7.0","script_version":"1.5","2":"1.5","version_comment":"New options for handling the default behaviour of line highlighting and updating signs on entering a buffer; a lot of refactoring","3":"New options for handling the default behaviour of line highlighting and updating signs on entering a buffer; a lot of refactoring","package":"vim-signify-1.5.tar.gz","4":"vim-signify-1.5.tar.gz","src_id":"19762","5":"19762","creation_date":"1365068292","6":"1365068292"},{"0":"4487","vim_version":"7.0","1":"7.0","script_version":"1.4","2":"1.4","version_comment":"handle files with conflict markers, many cosmetic changes","3":"handle files with conflict markers, many cosmetic changes","package":"vim-signify-1.4.tar.gz","4":"vim-signify-1.4.tar.gz","src_id":"19752","5":"19752","creation_date":"1364927263","6":"1364927263"},{"0":"4487","vim_version":"7.0","1":"7.0","script_version":"1.3","2":"1.3","version_comment":"fix important signmode bug","3":"fix important signmode bug","package":"vim-signify-1.3.tar.gz","4":"vim-signify-1.3.tar.gz","src_id":"19746","5":"19746","creation_date":"1364859467","6":"1364859467"},{"0":"4487","vim_version":"7.0","1":"7.0","script_version":"1.2","2":"1.2","version_comment":"Windows support, various bugfixes","3":"Windows support, various bugfixes","package":"vim-signify-1.2.tar.gz","4":"vim-signify-1.2.tar.gz","src_id":"19714","5":"19714","creation_date":"1364422458","6":"1364422458"},{"0":"4487","vim_version":"7.0","1":"7.0","script_version":"1.1","2":"1.1","version_comment":"changed handling of exception lists, corrected CVS support, new mappings [c and ]c, etc.","3":"changed handling of exception lists, corrected CVS support, new mappings [c and ]c, etc.","package":"vim-signify-1.1.tar.gz","4":"vim-signify-1.1.tar.gz","src_id":"19708","5":"19708","creation_date":"1364305869","6":"1364305869"},{"0":"4487","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"vim-signify-1.0.tar.gz","4":"vim-signify-1.0.tar.gz","src_id":"19703","5":"19703","creation_date":"1364250133","6":"1364250133"}]},"4486":{"script_id":"4486","0":"4486","script_name":"vim-rst-sections","1":"vim-rst-sections","script_type":"ftplugin","2":"ftplugin","summary":"Plugin to work with sections in ReST","3":"Plugin to work with sections in ReST","description":"This is a small vim extension to help making sections in restructured text\r\ndocuments.\r\n\r\nIt's very closely based on the nice https:\/\/github.com\/nvie\/vim-rst-tables\r\nextension by Vincent Driessen.  It includes some of Vincents's code from\r\nhttps:\/\/github.com\/nvie\/vim_bridge.\r\n\r\nThe latest version of the code for this plugin is at: \r\nhttps:\/\/github.com\/matthew-brett\/vim-rst-sections\r\n\r\nYou'll need python compiled into your vim for it to work (`:version` in vim will\r\ntell you).\r\n\r\n*******\r\nLicense\r\n*******\r\n\r\nI could not see a license for ``vim-rst-tables`` on which this is based.\r\n``vim-bridge`` is BSD licensed, as is this code.\r\n\r\nAssuming that that the ``vim-rst-tables`` code is in the public domain or BSD\r\nlicensed, I (Matthew Brett) release this code under the 2-clause BSD license.\r\nThe full text is in the ``LICENSE`` file in the same directory as this README.\r\nThanks to Vincent Driessen for sharing.\r\n\r\n******\r\nIn use\r\n******\r\n\r\nOnce you've installed the extension, then you can access it with your\r\n``<leader>`` key in vim.  I believe the default is ``\\``, for me it is mapped to\r\n``,``.  You can also call the various functions directly with commands such as\r\n``:call RstSectionStandardize()`` - see below.\r\n\r\n************************************\r\nConventional standard section markup\r\n************************************\r\n\r\nThe script mostly assumes that you are using, or want to use, the section\r\nheadings that the python documents use - see\r\nhttp:\/\/sphinx.pocoo.org\/rest.html#sections .  In summary, the convention is:\r\n\r\n* ``#`` with overline, for parts\r\n* ``*`` with overline, for chapters\r\n* ``=``, for sections\r\n* ``-``, for subsections\r\n* ``^``, for subsubsections\r\n* ``\"``, for paragraphs\r\n\r\n************************************************\r\nAutoconverting section markers to the convention\r\n************************************************\r\n\r\nIf you aren't using these conventions already, and you want to be able to use\r\n``rst-sections`` in a happy way, you may be able to automatically change to use\r\nthese conventions using the ``RstSectionStandardize`` vim function provided by\r\nthis extension.  Open the document you want to change, then run this::\r\n\r\n    call RstSectionStandardize()\r\n\r\nThe same function should also be accessible with the key combination\r\n``<leader><leader>p`` (\"p\" for Python standard sections).\r\n\r\n*******************\r\nMaking new sections\r\n*******************\r\n\r\nImagine you've just started a document.  You type this::\r\n\r\n    A big overall section\r\n\r\nWhile the cursor is on that line, type ``<leader><leader>d`` (for me that is\r\n``,,d``).  ``d`` is for 'down', you may see why later.  When you do this, you\r\nshould get the top section heading formatting::\r\n\r\n    #####################\r\n    A big overall section\r\n    #####################\r\n\r\nThen write some more text.  Add another section below:\r\n\r\n    A subsection for the big one\r\n\r\nType (for me) ``,,d`` and you get the top-level '#' under and overlining.  That\r\nis, you get the same level as the nearest section above you.  Type\r\n``,,d`` again and you go Down a level in the heirarchy to::\r\n\r\n    ****************************\r\n    A subsection for the big one\r\n    ****************************\r\n\r\nNow, with the cursor in the same place, try ``,,u`` (Up).  Notice that the\r\nheading level goes Up one level to the top level in the heirarchy again::\r\n\r\n    ############################\r\n    A subsection for the big one\r\n    ############################\r\n\r\nSo, if you are on a line that is not currently a section, then either of ``,,d``\r\nor ``,,u`` will format the line with the same section level as the nearest\r\nsection above you (or the top level if there is no section above you).  However,\r\npressing ``,,d`` on an existing section heading, will take you down a level in\r\nthe heirarchy, and pressing ``,,u`` will take you up a level in the heirarchy.\r\n\r\n***************************\r\nReformatting section markup\r\n***************************\r\n\r\nLet's say you edited your section title, so now the heading isn't aligned with\r\nthe text anymore::\r\n\r\n    ############################\r\n    A section for the big one\r\n    ############################\r\n\r\nYes, you've guessed it, ``,,r`` on the section or the underlining will reformat\r\nfor you::\r\n\r\n\r\n    #########################\r\n    A section for the big one\r\n    #########################","4":"This is a small vim extension to help making sections in restructured text\r\ndocuments.\r\n\r\nIt's very closely based on the nice https:\/\/github.com\/nvie\/vim-rst-tables\r\nextension by Vincent Driessen.  It includes some of Vincents's code from\r\nhttps:\/\/github.com\/nvie\/vim_bridge.\r\n\r\nThe latest version of the code for this plugin is at: \r\nhttps:\/\/github.com\/matthew-brett\/vim-rst-sections\r\n\r\nYou'll need python compiled into your vim for it to work (`:version` in vim will\r\ntell you).\r\n\r\n*******\r\nLicense\r\n*******\r\n\r\nI could not see a license for ``vim-rst-tables`` on which this is based.\r\n``vim-bridge`` is BSD licensed, as is this code.\r\n\r\nAssuming that that the ``vim-rst-tables`` code is in the public domain or BSD\r\nlicensed, I (Matthew Brett) release this code under the 2-clause BSD license.\r\nThe full text is in the ``LICENSE`` file in the same directory as this README.\r\nThanks to Vincent Driessen for sharing.\r\n\r\n******\r\nIn use\r\n******\r\n\r\nOnce you've installed the extension, then you can access it with your\r\n``<leader>`` key in vim.  I believe the default is ``\\``, for me it is mapped to\r\n``,``.  You can also call the various functions directly with commands such as\r\n``:call RstSectionStandardize()`` - see below.\r\n\r\n************************************\r\nConventional standard section markup\r\n************************************\r\n\r\nThe script mostly assumes that you are using, or want to use, the section\r\nheadings that the python documents use - see\r\nhttp:\/\/sphinx.pocoo.org\/rest.html#sections .  In summary, the convention is:\r\n\r\n* ``#`` with overline, for parts\r\n* ``*`` with overline, for chapters\r\n* ``=``, for sections\r\n* ``-``, for subsections\r\n* ``^``, for subsubsections\r\n* ``\"``, for paragraphs\r\n\r\n************************************************\r\nAutoconverting section markers to the convention\r\n************************************************\r\n\r\nIf you aren't using these conventions already, and you want to be able to use\r\n``rst-sections`` in a happy way, you may be able to automatically change to use\r\nthese conventions using the ``RstSectionStandardize`` vim function provided by\r\nthis extension.  Open the document you want to change, then run this::\r\n\r\n    call RstSectionStandardize()\r\n\r\nThe same function should also be accessible with the key combination\r\n``<leader><leader>p`` (\"p\" for Python standard sections).\r\n\r\n*******************\r\nMaking new sections\r\n*******************\r\n\r\nImagine you've just started a document.  You type this::\r\n\r\n    A big overall section\r\n\r\nWhile the cursor is on that line, type ``<leader><leader>d`` (for me that is\r\n``,,d``).  ``d`` is for 'down', you may see why later.  When you do this, you\r\nshould get the top section heading formatting::\r\n\r\n    #####################\r\n    A big overall section\r\n    #####################\r\n\r\nThen write some more text.  Add another section below:\r\n\r\n    A subsection for the big one\r\n\r\nType (for me) ``,,d`` and you get the top-level '#' under and overlining.  That\r\nis, you get the same level as the nearest section above you.  Type\r\n``,,d`` again and you go Down a level in the heirarchy to::\r\n\r\n    ****************************\r\n    A subsection for the big one\r\n    ****************************\r\n\r\nNow, with the cursor in the same place, try ``,,u`` (Up).  Notice that the\r\nheading level goes Up one level to the top level in the heirarchy again::\r\n\r\n    ############################\r\n    A subsection for the big one\r\n    ############################\r\n\r\nSo, if you are on a line that is not currently a section, then either of ``,,d``\r\nor ``,,u`` will format the line with the same section level as the nearest\r\nsection above you (or the top level if there is no section above you).  However,\r\npressing ``,,d`` on an existing section heading, will take you down a level in\r\nthe heirarchy, and pressing ``,,u`` will take you up a level in the heirarchy.\r\n\r\n***************************\r\nReformatting section markup\r\n***************************\r\n\r\nLet's say you edited your section title, so now the heading isn't aligned with\r\nthe text anymore::\r\n\r\n    ############################\r\n    A section for the big one\r\n    ############################\r\n\r\nYes, you've guessed it, ``,,r`` on the section or the underlining will reformat\r\nfor you::\r\n\r\n\r\n    #########################\r\n    A section for the big one\r\n    #########################","install_details":"Please, use pathogen!\r\n\r\nIf you are using pathogen:\r\n\r\n* ``cd ~\/.vim\/bundle``\r\n* unzip the zip file into that directory.\r\n\r\nIf you are not using pathogen:\r\n\r\n* unzip the source bundle to some directory.\r\n* Change directory into the new ``vim-rst-sections-<version-no>`` directory.\r\n* Copy the contents of the 'ftplugin' directory into your ``.vim\/ftplugin`` directory","5":"Please, use pathogen!\r\n\r\nIf you are using pathogen:\r\n\r\n* ``cd ~\/.vim\/bundle``\r\n* unzip the zip file into that directory.\r\n\r\nIf you are not using pathogen:\r\n\r\n* unzip the source bundle to some directory.\r\n* Change directory into the new ``vim-rst-sections-<version-no>`` directory.\r\n* Copy the contents of the 'ftplugin' directory into your ``.vim\/ftplugin`` directory","first_name":"Matthew","6":"Matthew","last_name":"Brett","7":"Brett","releases":[{"0":"4486","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"vim-rst-sections-0.1.zip","4":"vim-rst-sections-0.1.zip","src_id":"19695","5":"19695","creation_date":"1364157307","6":"1364157307"}]},"4485":{"script_id":"4485","0":"4485","script_name":"vim-git-log","1":"vim-git-log","script_type":"utility","2":"utility","summary":"View your git log interactively in Vim.  Side by side diffs!","3":"View your git log interactively in Vim.  Side by side diffs!","description":"vim-git-log is a Vim plugin that helps browse your git log.  This plugin\r\nrequires [Fugitive](https:\/\/github.com\/tpope\/vim-fugitive).\r\n\r\nSee the git repo here: https:\/\/github.com\/kablamo\/vim-git-log\r\n\r\nGitLog\r\n-------------\r\n\r\nTo open a new buffer which displays a list of the changes in your git repo:\r\n\r\n    :GitLog\r\n\r\nThis plugin is basically a wrapper around `git log` so nearly any option or\r\nargument that you can use with `git log` can be used here.  The exceptions are\r\n--pretty and options that affect --pretty.  Here are some more examples:\r\n\r\nView changes from the 'lib' directory instead of the repository root:\r\n\r\n    :GitLog lib\r\n\r\nView changes from a specifi author\/committer:\r\n\r\n    :GitLog --author Batman\r\n\r\nView changes where the commit message matches a (PCRE) regular expression\r\n\r\n    :GitLog --grep 'dinosaurs'\r\n\r\nView changes for a date range\r\n\r\n    :GitLog --since yesterday\r\n    :GitLog --since '1 month 1 week 1 day 1 hour 1 second'\r\n    :GitLog --since 2012-12-31\r\n    :GitLog --until 2012-12-31 23:30:60\r\n    :GitLog <since>..<until>\r\n\r\n\r\nHow to use the log browser\r\n--------------------------\r\n\r\nRunning any of the above commands will open a window titled 'GitLog' that looks\r\nlike this and allows you to browse the git log:\r\n\r\n    Eric Johnson 4 weeks ago 5ef0fb2\r\n    Added daysPerYear.\r\n    lib\/Networth\/Controller\/Calculator.pm\r\n    lib\/Networth\/Out\/RealCost.pm\r\n    root\/html\/calculator\/realCost.tt\r\n\r\n    Eric Johnson 5 weeks ago 9595fa0\r\n    fix css margin class.\r\n    root\/css\/networth.css\r\n    root\/css\/style.less\r\n    root\/css\/style.less.old\r\n    root\/html\/calculator\/realCost.tt\r\n    root\/html\/fi.tt\r\n\r\n    Eric Johnson 6 weeks ago ecf43db\r\n    Css tweaks.\r\n    root\/html\/calculator\/realCost.tt\r\n\r\nHere are some commands you can use in the browser:\r\n\r\n   <cr>  View the side by side diff of any file by putting your cursor on that\r\n         line and typing `d` (for diff).\r\n\r\n   d     This has the same behavior as `<cr>`.\r\n\r\n   n     Move your cursor to the first filename in the next commit.\r\n\r\n   N     Move your cursor to the first filename in the previous commit.\r\n\r\n\r\nTo quickly exit out of the diff and return to the 'GitLog' window, type `q`.\r\n\r\n\r\nRibbon\r\n-------------\r\n\r\n**First** mark your place with\r\n\r\n    :RibbonSave\r\n\r\nThis will place a tag named __ribbon at origin\/master.  Basically you are\r\nbookmarking our current spot with a `ribbon`.\r\n\r\n**Next**, use Fugitive to pull down the latest changes made by your fellow conspirators from the\r\nremote repository.  \r\n\r\n    :Git pull\r\n\r\nTo review those changes use the following command:\r\n\r\n    :Ribbon\r\n\r\nThis will open a window titled 'Ribbon' that looks like this:\r\n\r\n    Eric Johnson 6 weeks ago ecf43db\r\n    Css tweaks.\r\n    root\/html\/calculator\/realCost.tt\r\n\r\n    Eric Johnson 5 weeks ago 9595fa0\r\n    fix css margin class.\r\n    root\/css\/networth.css\r\n    root\/css\/style.less\r\n    root\/css\/style.less.old\r\n    root\/html\/calculator\/realCost.tt\r\n    root\/html\/fi.tt\r\n\r\n    Eric Johnson 4 weeks ago 5ef0fb2\r\n    Added daysPerYear.\r\n    lib\/Networth\/Controller\/Calculator.pm\r\n    lib\/Networth\/Out\/RealCost.pm\r\n    root\/html\/calculator\/realCost.tt\r\n\r\nSee the section on *How to use the GitLog browser* for a complete list of all\r\nthe commands available to you. \r\n\r\n**Finally**, after you have reviewed all the changes, mark your place again with:\r\n\r\n    :RibbonSave\r\n\r\nBonus tips\r\n----------\r\n\r\nThe default colors used in vimdiff look like they were created by crazy clowns.\r\nYou might like my colorscheme instead:\r\n\r\n    ⚡ mkdir -p ~\/.vim\/colors\/\r\n    ⚡ wget https:\/\/github.com\/kablamo\/dotfiles\/blob\/master\/links\/.vim\/colors\/iijo.vim -O ~\/tmp\/iijo.vim\r\n    ⚡ echo \"colorscheme iijo\" >> ~\/.vimrc\r\n\r\nHow to use vimdiff:\r\n - To switch windows type `ctl-w l` and `ctl-w h`.  For more help see `:help window-move-cursor`.\r\n - To open and close folds type `zo` and `zc`.  For more help see `:help fold-commands`.\r\n\r\nSee also\r\n--------\r\n\r\nThis script was inspired by\r\nhttp:\/\/gitready.com\/advanced\/2011\/10\/21\/ribbon-and-catchup-reading-new-commits.html\r\n\r\nI also wrote [git-ribbon](https:\/\/github.com\/kablamo\/git-ribbon), a little Perl\r\nscript that does pretty much the same thing but from the commandline.","4":"vim-git-log is a Vim plugin that helps browse your git log.  This plugin\r\nrequires [Fugitive](https:\/\/github.com\/tpope\/vim-fugitive).\r\n\r\nSee the git repo here: https:\/\/github.com\/kablamo\/vim-git-log\r\n\r\nGitLog\r\n-------------\r\n\r\nTo open a new buffer which displays a list of the changes in your git repo:\r\n\r\n    :GitLog\r\n\r\nThis plugin is basically a wrapper around `git log` so nearly any option or\r\nargument that you can use with `git log` can be used here.  The exceptions are\r\n--pretty and options that affect --pretty.  Here are some more examples:\r\n\r\nView changes from the 'lib' directory instead of the repository root:\r\n\r\n    :GitLog lib\r\n\r\nView changes from a specifi author\/committer:\r\n\r\n    :GitLog --author Batman\r\n\r\nView changes where the commit message matches a (PCRE) regular expression\r\n\r\n    :GitLog --grep 'dinosaurs'\r\n\r\nView changes for a date range\r\n\r\n    :GitLog --since yesterday\r\n    :GitLog --since '1 month 1 week 1 day 1 hour 1 second'\r\n    :GitLog --since 2012-12-31\r\n    :GitLog --until 2012-12-31 23:30:60\r\n    :GitLog <since>..<until>\r\n\r\n\r\nHow to use the log browser\r\n--------------------------\r\n\r\nRunning any of the above commands will open a window titled 'GitLog' that looks\r\nlike this and allows you to browse the git log:\r\n\r\n    Eric Johnson 4 weeks ago 5ef0fb2\r\n    Added daysPerYear.\r\n    lib\/Networth\/Controller\/Calculator.pm\r\n    lib\/Networth\/Out\/RealCost.pm\r\n    root\/html\/calculator\/realCost.tt\r\n\r\n    Eric Johnson 5 weeks ago 9595fa0\r\n    fix css margin class.\r\n    root\/css\/networth.css\r\n    root\/css\/style.less\r\n    root\/css\/style.less.old\r\n    root\/html\/calculator\/realCost.tt\r\n    root\/html\/fi.tt\r\n\r\n    Eric Johnson 6 weeks ago ecf43db\r\n    Css tweaks.\r\n    root\/html\/calculator\/realCost.tt\r\n\r\nHere are some commands you can use in the browser:\r\n\r\n   <cr>  View the side by side diff of any file by putting your cursor on that\r\n         line and typing `d` (for diff).\r\n\r\n   d     This has the same behavior as `<cr>`.\r\n\r\n   n     Move your cursor to the first filename in the next commit.\r\n\r\n   N     Move your cursor to the first filename in the previous commit.\r\n\r\n\r\nTo quickly exit out of the diff and return to the 'GitLog' window, type `q`.\r\n\r\n\r\nRibbon\r\n-------------\r\n\r\n**First** mark your place with\r\n\r\n    :RibbonSave\r\n\r\nThis will place a tag named __ribbon at origin\/master.  Basically you are\r\nbookmarking our current spot with a `ribbon`.\r\n\r\n**Next**, use Fugitive to pull down the latest changes made by your fellow conspirators from the\r\nremote repository.  \r\n\r\n    :Git pull\r\n\r\nTo review those changes use the following command:\r\n\r\n    :Ribbon\r\n\r\nThis will open a window titled 'Ribbon' that looks like this:\r\n\r\n    Eric Johnson 6 weeks ago ecf43db\r\n    Css tweaks.\r\n    root\/html\/calculator\/realCost.tt\r\n\r\n    Eric Johnson 5 weeks ago 9595fa0\r\n    fix css margin class.\r\n    root\/css\/networth.css\r\n    root\/css\/style.less\r\n    root\/css\/style.less.old\r\n    root\/html\/calculator\/realCost.tt\r\n    root\/html\/fi.tt\r\n\r\n    Eric Johnson 4 weeks ago 5ef0fb2\r\n    Added daysPerYear.\r\n    lib\/Networth\/Controller\/Calculator.pm\r\n    lib\/Networth\/Out\/RealCost.pm\r\n    root\/html\/calculator\/realCost.tt\r\n\r\nSee the section on *How to use the GitLog browser* for a complete list of all\r\nthe commands available to you. \r\n\r\n**Finally**, after you have reviewed all the changes, mark your place again with:\r\n\r\n    :RibbonSave\r\n\r\nBonus tips\r\n----------\r\n\r\nThe default colors used in vimdiff look like they were created by crazy clowns.\r\nYou might like my colorscheme instead:\r\n\r\n    ⚡ mkdir -p ~\/.vim\/colors\/\r\n    ⚡ wget https:\/\/github.com\/kablamo\/dotfiles\/blob\/master\/links\/.vim\/colors\/iijo.vim -O ~\/tmp\/iijo.vim\r\n    ⚡ echo \"colorscheme iijo\" >> ~\/.vimrc\r\n\r\nHow to use vimdiff:\r\n - To switch windows type `ctl-w l` and `ctl-w h`.  For more help see `:help window-move-cursor`.\r\n - To open and close folds type `zo` and `zc`.  For more help see `:help fold-commands`.\r\n\r\nSee also\r\n--------\r\n\r\nThis script was inspired by\r\nhttp:\/\/gitready.com\/advanced\/2011\/10\/21\/ribbon-and-catchup-reading-new-commits.html\r\n\r\nI also wrote [git-ribbon](https:\/\/github.com\/kablamo\/git-ribbon), a little Perl\r\nscript that does pretty much the same thing but from the commandline.","install_details":"","5":"","first_name":"eric","6":"eric","last_name":"johnson","7":"johnson","releases":[{"0":"4485","vim_version":"7.0","1":"7.0","script_version":"0.01","2":"0.01","version_comment":"Initial upload","3":"Initial upload","package":"vim-git-log-master.zip","4":"vim-git-log-master.zip","src_id":"19686","5":"19686","creation_date":"1364027988","6":"1364027988"}]},"4484":{"script_id":"4484","0":"4484","script_name":"AssistEnclose.vim","1":"AssistEnclose.vim","script_type":"ftplugin","2":"ftplugin","summary":"Assist manipulation on brackets, quotes","3":"Assist manipulation on brackets, quotes","description":"========================================================================= \r\n\r\n[ Usage ] \r\n\r\n___________ \r\n    1. Enclosing \r\n\r\n\r\nOn text \r\n\r\n<Alt>  +      ) ( \r\n\r\ntext    \t→    (text) \r\n\r\n\r\n\r\nvisual block on 'some text' and <Alt> + )(   on text \r\n\r\nsome text      →   (some text) \r\n\r\n\r\nwith the same way working on \r\n\r\n[...] <...> {....} \r\n\r\n<Alt> +  ][  or  ><  or  }{   \r\n\r\nto make each enclosing. \r\n\r\n\r\nBasically, enclosing range is in the unit of word, \r\nso you don't need care about cursor position precisely. \r\nRegardless of input mode(normal or visual), \r\nput on across somewhere of the word you want. \r\n\r\n\r\n\r\n\r\nWhen to make enclosure with single or double quotations \r\n\r\n             '...'           \"...\" \r\n\r\n<Alt> +         ';      or      \": \r\n\r\n(this is to make consistency with other key mapping) \r\n\r\n\r\n\r\n(example) \r\n\r\nstdio.h \r\n\r\n\"stdio.h\" \r\n\r\n<\"stdio.h\"> \r\n\r\n\r\n<...> {...} [...] (...) eat over single or double quotations '...' \"...\" \r\n\r\n\r\nIn (vertical)visual mode (<C-v>)\r\n\r\nby pressing <leader> key before same key operation,\r\nyou can encapsulate 'on each word'.\r\n\r\nw◘rd\r\nw◘rd\r\nw◘rd\r\n\r\n(word)\r\n(word)\r\n(word)  \r\n\r\n__________________________ \r\n    2. Delete contents in enclosure \r\n\r\n\r\nOn the word enclosed with (...) \r\n\r\n<Alt> + (( \r\n\r\nSame way is applied to   \r\n\r\n             {...}   [...]   <...>   \"...\"   '...' \r\n\r\n<Alt> +      {{      [[      <<      ::      ;;      on each \r\n\r\n\r\n\r\n\r\n___________________________________ \r\n    3. Delete enclosure leaving contents intact \r\n\r\n\r\nOn the word enclosed with (...) \r\n\r\n<Alt> + )) \r\n\r\nSame way is applied to   \r\n\r\n           {...}   [...]   <...>   \"...\"   '...' \r\n\r\n<Alt> +    }}      ]]      >>      \"\"      ''          on each \r\n\r\n\r\n\r\n\r\n________________________________________ \r\n    4. Blow out the contents at once in the enclosure \r\n\r\n\r\nhit <A-;'> to blow out in '...' or \"...\" \r\n\r\nhit <A-[]> to blow out in [...] <...> {...} (...) \r\n\r\n\r\nYou can also rearrange \"priority order\" by modifying g:ListBraTotal \r\n\r\nDefault order is  {...}\t  \u00c2\u00ad  (...)   \u00c2\u00ad <...>  \t\u00c2\u00ad   [...] \r\n\r\n                   ←                                      → \r\n                   High                                   Low \r\n\r\n\r\n___________________________________ \r\n    5. when manipulate snippets file or html file \r\n\r\n\r\nword -> ${1:word}           when in .snipptes \r\nword -> <em>word<\/em>       when in .html \r\nword -> \\emph{word}         when in .tex \r\n\r\nwith Alt + ][ \r\n\r\n\r\n______________ \r\n    6. smart escape \r\n\r\n\r\nThis function is separated to easy-through-pairing.vim\r\nfor functional rearrangement.\r\n\r\nplease, check if you thought this script not bad.\r\n\r\nhttp:\/\/www.vim.org\/scripts\/script.php?script_id=4578\r\n\r\n\r\n\r\n-------------------------------------------------------------------------- \r\n\r\n[ NOTE ] \r\n\r\n\r\nYou would have get more help from following scripts. \r\n\r\nCkeck out, \r\n\r\nsurround.vim \r\nhttp:\/\/www.vim.org\/scripts\/script.php?script_id=1697 \r\n\r\nautoclose.vim \r\nhttp:\/\/www.vim.org\/scripts\/script.php?script_id=1849 ","4":"========================================================================= \r\n\r\n[ Usage ] \r\n\r\n___________ \r\n    1. Enclosing \r\n\r\n\r\nOn text \r\n\r\n<Alt>  +      ) ( \r\n\r\ntext    \t→    (text) \r\n\r\n\r\n\r\nvisual block on 'some text' and <Alt> + )(   on text \r\n\r\nsome text      →   (some text) \r\n\r\n\r\nwith the same way working on \r\n\r\n[...] <...> {....} \r\n\r\n<Alt> +  ][  or  ><  or  }{   \r\n\r\nto make each enclosing. \r\n\r\n\r\nBasically, enclosing range is in the unit of word, \r\nso you don't need care about cursor position precisely. \r\nRegardless of input mode(normal or visual), \r\nput on across somewhere of the word you want. \r\n\r\n\r\n\r\n\r\nWhen to make enclosure with single or double quotations \r\n\r\n             '...'           \"...\" \r\n\r\n<Alt> +         ';      or      \": \r\n\r\n(this is to make consistency with other key mapping) \r\n\r\n\r\n\r\n(example) \r\n\r\nstdio.h \r\n\r\n\"stdio.h\" \r\n\r\n<\"stdio.h\"> \r\n\r\n\r\n<...> {...} [...] (...) eat over single or double quotations '...' \"...\" \r\n\r\n\r\nIn (vertical)visual mode (<C-v>)\r\n\r\nby pressing <leader> key before same key operation,\r\nyou can encapsulate 'on each word'.\r\n\r\nw◘rd\r\nw◘rd\r\nw◘rd\r\n\r\n(word)\r\n(word)\r\n(word)  \r\n\r\n__________________________ \r\n    2. Delete contents in enclosure \r\n\r\n\r\nOn the word enclosed with (...) \r\n\r\n<Alt> + (( \r\n\r\nSame way is applied to   \r\n\r\n             {...}   [...]   <...>   \"...\"   '...' \r\n\r\n<Alt> +      {{      [[      <<      ::      ;;      on each \r\n\r\n\r\n\r\n\r\n___________________________________ \r\n    3. Delete enclosure leaving contents intact \r\n\r\n\r\nOn the word enclosed with (...) \r\n\r\n<Alt> + )) \r\n\r\nSame way is applied to   \r\n\r\n           {...}   [...]   <...>   \"...\"   '...' \r\n\r\n<Alt> +    }}      ]]      >>      \"\"      ''          on each \r\n\r\n\r\n\r\n\r\n________________________________________ \r\n    4. Blow out the contents at once in the enclosure \r\n\r\n\r\nhit <A-;'> to blow out in '...' or \"...\" \r\n\r\nhit <A-[]> to blow out in [...] <...> {...} (...) \r\n\r\n\r\nYou can also rearrange \"priority order\" by modifying g:ListBraTotal \r\n\r\nDefault order is  {...}\t  \u00c2\u00ad  (...)   \u00c2\u00ad <...>  \t\u00c2\u00ad   [...] \r\n\r\n                   ←                                      → \r\n                   High                                   Low \r\n\r\n\r\n___________________________________ \r\n    5. when manipulate snippets file or html file \r\n\r\n\r\nword -> ${1:word}           when in .snipptes \r\nword -> <em>word<\/em>       when in .html \r\nword -> \\emph{word}         when in .tex \r\n\r\nwith Alt + ][ \r\n\r\n\r\n______________ \r\n    6. smart escape \r\n\r\n\r\nThis function is separated to easy-through-pairing.vim\r\nfor functional rearrangement.\r\n\r\nplease, check if you thought this script not bad.\r\n\r\nhttp:\/\/www.vim.org\/scripts\/script.php?script_id=4578\r\n\r\n\r\n\r\n-------------------------------------------------------------------------- \r\n\r\n[ NOTE ] \r\n\r\n\r\nYou would have get more help from following scripts. \r\n\r\nCkeck out, \r\n\r\nsurround.vim \r\nhttp:\/\/www.vim.org\/scripts\/script.php?script_id=1697 \r\n\r\nautoclose.vim \r\nhttp:\/\/www.vim.org\/scripts\/script.php?script_id=1849 ","install_details":"Just drop in .vim\/plugin or vimfiles\/plugin","5":"Just drop in .vim\/plugin or vimfiles\/plugin","first_name":"Han-seok","6":"Han-seok","last_name":"Ryu","7":"Ryu","releases":[{"0":"4484","vim_version":"7.3","1":"7.3","script_version":"0.18a","2":"0.18a","version_comment":"variable confuse fix (easy-through-pairing.vim)","3":"variable confuse fix (easy-through-pairing.vim)","package":"AssistEnclose.vim","4":"AssistEnclose.vim","src_id":"20131","5":"20131","creation_date":"1368487004","6":"1368487004"},{"0":"4484","vim_version":"7.3","1":"7.3","script_version":"0.18","2":"0.18","version_comment":"each encapsulation work version\r\nsmart escape is separated to easy-through-pairing.vim","3":"each encapsulation work version\r\nsmart escape is separated to easy-through-pairing.vim","package":"AssistEnclose.vim","4":"AssistEnclose.vim","src_id":"20109","5":"20109","creation_date":"1368452768","6":"1368452768"},{"0":"4484","vim_version":"7.3","1":"7.3","script_version":"0.17","2":"0.17","version_comment":"EscapeSmart update \r\nname changed to EasyThrough \r\nsilent added to mapping","3":"EscapeSmart update \r\nname changed to EasyThrough \r\nsilent added to mapping","package":"AssistEnclose.vim","4":"AssistEnclose.vim","src_id":"20033","5":"20033","creation_date":"1367862162","6":"1367862162"},{"0":"4484","vim_version":"7.3","1":"7.3","script_version":"0.16","2":"0.16","version_comment":"add smart escape <C-j>","3":"add smart escape <C-j>","package":"AssistEnclose.vim","4":"AssistEnclose.vim","src_id":"19907","5":"19907","creation_date":"1366704029","6":"1366704029"},{"0":"4484","vim_version":"7.3","1":"7.3","script_version":"0.15b","2":"0.15b","version_comment":"bug fix (range confuse)","3":"bug fix (range confuse)","package":"assistEncloseManip.vim","4":"assistEncloseManip.vim","src_id":"19903","5":"19903","creation_date":"1366701305","6":"1366701305"},{"0":"4484","vim_version":"7.3","1":"7.3","script_version":"0.15","2":"0.15","version_comment":"workaround complete\r\nadd \\emph{} for .tex file <M-][>","3":"workaround complete\r\nadd \\emph{} for .tex file <M-][>","package":"assistEncloseManip.vim","4":"assistEncloseManip.vim","src_id":"19899","5":"19899","creation_date":"1366698789","6":"1366698789"},{"0":"4484","vim_version":"7.3","1":"7.3","script_version":"0.14c","2":"0.14c","version_comment":"work around conflict with autoclose.vim \r\nfix visual mode 'V' enclosing","3":"work around conflict with autoclose.vim \r\nfix visual mode 'V' enclosing","package":"assistEncloseManip.vim","4":"assistEncloseManip.vim","src_id":"19761","5":"19761","creation_date":"1365066873","6":"1365066873"},{"0":"4484","vim_version":"7.3","1":"7.3","script_version":"0.14a","2":"0.14a","version_comment":"remapping keys\r\nfix visual block enclosing disorder\r\nfix abnormal when removing enclosure\r\nfix parameter error (for .snippets)\r\nfix infinite loop\r\nfunctions rewrite","3":"remapping keys\r\nfix visual block enclosing disorder\r\nfix abnormal when removing enclosure\r\nfix parameter error (for .snippets)\r\nfix infinite loop\r\nfunctions rewrite","package":"assistEncloseManip.vim","4":"assistEncloseManip.vim","src_id":"19697","5":"19697","creation_date":"1364185294","6":"1364185294"},{"0":"4484","vim_version":"7.3","1":"7.3","script_version":"0.14","2":"0.14","version_comment":"remapping keys\r\nfix visual block enclosing disorder\r\nfix abnormal when removing enclosure\r\nfix parameter error (for .snippets)\r\nfunctions rewrite","3":"remapping keys\r\nfix visual block enclosing disorder\r\nfix abnormal when removing enclosure\r\nfix parameter error (for .snippets)\r\nfunctions rewrite","package":"assistEncloseManip.vim","4":"assistEncloseManip.vim","src_id":"19694","5":"19694","creation_date":"1364150328","6":"1364150328"},{"0":"4484","vim_version":"7.3","1":"7.3","script_version":"0.12","2":"0.12","version_comment":"for .html .snippets key map added","3":"for .html .snippets key map added","package":"assistEncloseManip.vim","4":"assistEncloseManip.vim","src_id":"19682","5":"19682","creation_date":"1363960172","6":"1363960172"}]},"4483":{"script_id":"4483","0":"4483","script_name":"zarniwoop.vim","1":"zarniwoop.vim","script_type":"color scheme","2":"color scheme","summary":"A colourful, dark colour scheme for Vim.","3":"A colourful, dark colour scheme for Vim.","description":"A colourful, dark colour scheme. This scheme is basically jellybeans.vim (https:\/\/github.com\/nanotech\/jellybeans.vim) with a few tweaks here and there. \r\n\r\nDesigned primarily for a graphical Vim, but includes support for 256, 88, 16, and 8 color terminals. On a 16 or 8 color terminal, replace its colors with these for best results: https:\/\/raw.github.com\/xironix\/zarniwoop.vim\/master\/ansi-term-colors.txt\r\n\r\nIf you can\u00e2\u0080\u0099t change your terminal\u00e2\u0080\u0099s colors, set g:zarniwoop_use_lowcolor_black to zero in your .vimrc to render \u00e2\u0080\u0098black\u00e2\u0080\u0099 text as grey. \r\n\r\nScreenshots: http:\/\/dl.dropbox.com\/u\/698619\/Pictures\/GitHub\/zarniwoop.png \r\n\r\nFeel free to fork at https:\/\/github.com\/xironix\/zarniwoop.vim GitHub will also generally have a more recent version than Vim.org.","4":"A colourful, dark colour scheme. This scheme is basically jellybeans.vim (https:\/\/github.com\/nanotech\/jellybeans.vim) with a few tweaks here and there. \r\n\r\nDesigned primarily for a graphical Vim, but includes support for 256, 88, 16, and 8 color terminals. On a 16 or 8 color terminal, replace its colors with these for best results: https:\/\/raw.github.com\/xironix\/zarniwoop.vim\/master\/ansi-term-colors.txt\r\n\r\nIf you can\u00e2\u0080\u0099t change your terminal\u00e2\u0080\u0099s colors, set g:zarniwoop_use_lowcolor_black to zero in your .vimrc to render \u00e2\u0080\u0098black\u00e2\u0080\u0099 text as grey. \r\n\r\nScreenshots: http:\/\/dl.dropbox.com\/u\/698619\/Pictures\/GitHub\/zarniwoop.png \r\n\r\nFeel free to fork at https:\/\/github.com\/xironix\/zarniwoop.vim GitHub will also generally have a more recent version than Vim.org.","install_details":"Copy into \"~\/.vim\/colors\/\", then run \":colorscheme zarniwoop\". If you use Vundle or Pathogen, the Git repo is compatible.","5":"Copy into \"~\/.vim\/colors\/\", then run \":colorscheme zarniwoop\". If you use Vundle or Pathogen, the Git repo is compatible.","first_name":"Steffen L.","6":"Steffen L.","last_name":"Norgren","7":"Norgren","releases":[{"0":"4483","vim_version":"7.3","1":"7.3","script_version":"1.1","2":"1.1","version_comment":"Updated many colours to make me happier. =D","3":"Updated many colours to make me happier. =D","package":"zarniwoop.vim","4":"zarniwoop.vim","src_id":"19684","5":"19684","creation_date":"1363963019","6":"1363963019"},{"0":"4483","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"zarniwoop.vim","4":"zarniwoop.vim","src_id":"19676","5":"19676","creation_date":"1363948247","6":"1363948247"}]},"4482":{"script_id":"4482","0":"4482","script_name":"vim-tmuxify","1":"vim-tmuxify","script_type":"utility","2":"utility","summary":"Handling tmux panes like a boss.","3":"Handling tmux panes like a boss.","description":"\r\nNOTE: Get the latest updates via github: https:\/\/github.com\/mhinz\/vim-tmuxify\r\n\r\nIf you like this plugin, star it on github!\r\n\r\n\r\n# vim-tmuxify\r\n\r\nThis is a shiny Vim plugin for handling tmux panes from within Vim!\r\n\r\nFeatures:\r\n\r\n- create\/kill associated panes\r\n- associate tmuxify to already existing panes\r\n- send visually highlighted lines to the associated pane\r\n- send to pane by prompting for input\r\n- send to pane by setting a run command for the current filetype\r\n- once set, run commands are remembered, but can easily be reset\r\n- all the plugin configuration happens in one dictionary that holds filetypes as\r\n  keys and run commands as values\r\n\r\n## Feedback, please!\r\n\r\nIf you use any of my plugins, star it on github. This is a great way of getting\r\nfeedback! Same for issues or feature requests.\r\n\r\nThank you for flying mhi airlines. Get the Vim on!\r\n\r\n## Options\r\n\r\nPut these variables into your vimrc for great enjoyment. The shown examples\r\nare also the default values.\r\n\r\n```vim\r\nlet g:tmuxify_pane_split = '-v'\r\n```\r\n\r\nSplit either vertically or horizontally. The two possible values are therefore\r\n'-v' and '-h'.\r\n\r\n```vim\r\nlet g:tmuxify_pane_size = '10'\r\n```\r\n\r\nThe size of the associated pane.\r\n\r\n```vim\r\nlet g:tmuxify_run = {}\r\n```\r\n\r\nSet run commands for specific filetypes. '%' will be replaced by the full path\r\nto the current buffer.\r\n\r\nExample:\r\n\r\n```vim\r\nlet g:tmuxify_run = {\r\n    \\ 'sh': 'bash %',\r\n    \\ 'go': 'go build %',\r\n    \\}\r\n```\r\n\r\n## Mappings\r\n\r\n```vim\r\n<leader>mn\r\n```\r\n\r\nExecutes TxCreate. Creates a new pane and associates with it.\r\n\r\n```vim\r\n<leader>mq\r\n```\r\n\r\nExecutes TxKill. Closes the associated pane.\r\n\r\n```vim\r\n<leader>ms\r\n```\r\n\r\nExecutes TxSend. Prompts for input and sends it to the associated pane. This\r\nmapping also works on visual selections.\r\n\r\n```vim\r\n<leader>mr\r\n```\r\n\r\nExecutes TxRun. Prompts for input if there is no entry in g:tmuxify_run for\r\nthe current filetype. '%' will be replaced by the full path to the current\r\nbuffer.\r\n\r\n```vim\r\n<leader>mt\r\n```\r\n\r\nExecutes TxSetRunCmd. Change the run command for the current filetype.\r\n\r\n```vim\r\n<leader>mp\r\n```\r\n\r\nExecutes TxSetPane. Associate an already existing pane with tmuxify. Note: You\r\ncan use tab completion here.\r\n\r\n```vim\r\n<leader>mc\r\n```\r\n\r\nExecutes TxClear. This is a shortcut for TxSend('clear').\r\n\r\n```vim\r\n<leader>mb\r\n```\r\n\r\nExecutes TxSigInt. Sends an interrupt signal to the associated pane.\r\n\r\n## Documentation\r\n\r\n`:h tmuxify`\r\n\r\n## Author\r\n\r\nMarco Hinz `<mh.codebro@gmail.com>`\r\n\r\n## License\r\n\r\nCopyright \u00c2\u00a9 2013 Marco Hinz. Revised BSD license.","4":"\r\nNOTE: Get the latest updates via github: https:\/\/github.com\/mhinz\/vim-tmuxify\r\n\r\nIf you like this plugin, star it on github!\r\n\r\n\r\n# vim-tmuxify\r\n\r\nThis is a shiny Vim plugin for handling tmux panes from within Vim!\r\n\r\nFeatures:\r\n\r\n- create\/kill associated panes\r\n- associate tmuxify to already existing panes\r\n- send visually highlighted lines to the associated pane\r\n- send to pane by prompting for input\r\n- send to pane by setting a run command for the current filetype\r\n- once set, run commands are remembered, but can easily be reset\r\n- all the plugin configuration happens in one dictionary that holds filetypes as\r\n  keys and run commands as values\r\n\r\n## Feedback, please!\r\n\r\nIf you use any of my plugins, star it on github. This is a great way of getting\r\nfeedback! Same for issues or feature requests.\r\n\r\nThank you for flying mhi airlines. Get the Vim on!\r\n\r\n## Options\r\n\r\nPut these variables into your vimrc for great enjoyment. The shown examples\r\nare also the default values.\r\n\r\n```vim\r\nlet g:tmuxify_pane_split = '-v'\r\n```\r\n\r\nSplit either vertically or horizontally. The two possible values are therefore\r\n'-v' and '-h'.\r\n\r\n```vim\r\nlet g:tmuxify_pane_size = '10'\r\n```\r\n\r\nThe size of the associated pane.\r\n\r\n```vim\r\nlet g:tmuxify_run = {}\r\n```\r\n\r\nSet run commands for specific filetypes. '%' will be replaced by the full path\r\nto the current buffer.\r\n\r\nExample:\r\n\r\n```vim\r\nlet g:tmuxify_run = {\r\n    \\ 'sh': 'bash %',\r\n    \\ 'go': 'go build %',\r\n    \\}\r\n```\r\n\r\n## Mappings\r\n\r\n```vim\r\n<leader>mn\r\n```\r\n\r\nExecutes TxCreate. Creates a new pane and associates with it.\r\n\r\n```vim\r\n<leader>mq\r\n```\r\n\r\nExecutes TxKill. Closes the associated pane.\r\n\r\n```vim\r\n<leader>ms\r\n```\r\n\r\nExecutes TxSend. Prompts for input and sends it to the associated pane. This\r\nmapping also works on visual selections.\r\n\r\n```vim\r\n<leader>mr\r\n```\r\n\r\nExecutes TxRun. Prompts for input if there is no entry in g:tmuxify_run for\r\nthe current filetype. '%' will be replaced by the full path to the current\r\nbuffer.\r\n\r\n```vim\r\n<leader>mt\r\n```\r\n\r\nExecutes TxSetRunCmd. Change the run command for the current filetype.\r\n\r\n```vim\r\n<leader>mp\r\n```\r\n\r\nExecutes TxSetPane. Associate an already existing pane with tmuxify. Note: You\r\ncan use tab completion here.\r\n\r\n```vim\r\n<leader>mc\r\n```\r\n\r\nExecutes TxClear. This is a shortcut for TxSend('clear').\r\n\r\n```vim\r\n<leader>mb\r\n```\r\n\r\nExecutes TxSigInt. Sends an interrupt signal to the associated pane.\r\n\r\n## Documentation\r\n\r\n`:h tmuxify`\r\n\r\n## Author\r\n\r\nMarco Hinz `<mh.codebro@gmail.com>`\r\n\r\n## License\r\n\r\nCopyright \u00c2\u00a9 2013 Marco Hinz. Revised BSD license.","install_details":"I suggest using tpope's pathogen:\r\n\r\n- https:\/\/github.com\/tpope\/vim-pathogen\r\n\r\nAfterwards, just clone vim-signify into ~\/.vim\/bundle\/.","5":"I suggest using tpope's pathogen:\r\n\r\n- https:\/\/github.com\/tpope\/vim-pathogen\r\n\r\nAfterwards, just clone vim-signify into ~\/.vim\/bundle\/.","first_name":"Marco","6":"Marco","last_name":"Hinz","7":"Hinz","releases":[{"0":"4482","vim_version":"7.0","1":"7.0","script_version":"1.2","2":"1.2","version_comment":"improved sending of multiple lines","3":"improved sending of multiple lines","package":"vim-tmuxify-1.2.tar.gz","4":"vim-tmuxify-1.2.tar.gz","src_id":"19766","5":"19766","creation_date":"1365264357","6":"1365264357"},{"0":"4482","vim_version":"7.0","1":"7.0","script_version":"1.1","2":"1.1","version_comment":"Internal redesign \/ user interface hasn't changed","3":"Internal redesign \/ user interface hasn't changed","package":"vim-tmuxify-1.1.tar.gz","4":"vim-tmuxify-1.1.tar.gz","src_id":"19702","5":"19702","creation_date":"1364219545","6":"1364219545"},{"0":"4482","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"vim-tmuxify.tbz2","4":"vim-tmuxify.tbz2","src_id":"19675","5":"19675","creation_date":"1363946227","6":"1363946227"}]},"4481":{"script_id":"4481","0":"4481","script_name":"joy","1":"joy","script_type":"utility","2":"utility","summary":"Tab becomes Esc, just like Bill Joy!","3":"Tab becomes Esc, just like Bill Joy!","description":"Esc key where Bill Joy had his.\r\n\r\n\/\/ Introduction \/\/\r\n\r\ntl;dr:\r\n\r\n    :imap <tab> <esc>\r\n    (See: https:\/\/en.wikipedia.org\/wiki\/Vi#Creation )\r\n\r\nIBM made some really odd decisions in popularizing the current keyboard, so\r\nwe're taking the power back.\r\n\r\nThe :imap above is the real heart of vim-joy: just make it so hitting tab in Insert mode gets you out into Normal mode. The only extra complexity in this script is due to the \"Training Wheels\" needed to get used\r\nto not being able to hit tab normally. The <Tab>=<Esc> thing is is most surprising when:\r\n\r\n* When on an empty line, meaning \"increase indent\". Use <C-t> instead.\r\n* When in the middle of a line, and trying to line things up. I don't have an exact solution for this, other than to do the work in Normal mode (e.g. with\r\n  <C-v> combined with << and >>)\r\n\r\nTo affect the behavior of this plugin, you can either:\r\n\r\n   let g:joy_pure = 1\r\n\r\nCommit to using <C-t> instead of <Tab> for indentation. At this point it\r\nbecomes identical in behavior to Insert Mode <Tab> == <Esc>.\r\n\r\n   let g:joy_mixed = 1\r\n\r\nTo turn off the nag message, and forget about <C-t> for indent.\r\n\r\n\/\/ Temporarily Disabling \/\/\r\n\r\nSometimes you want to affect the behavior only for this session (e.g. for pair\r\nprogramming with someone who isn't feeling it)\r\n\r\nTo go back to impure mode:\r\n\r\n   :unlet g:joy_pure\r\n\r\nTo make <Tab> be default in behavior:\r\n\r\n   :unimap <Tab>\r\n\r\n\/\/ Thanks \/\/\r\n\r\nThanks to tpope, as always!\r\n\r\n\/\/ About \/\/\r\n\r\nGrab the latest version or report a bug on Github: http:\/\/github.com\/rking\/vim-joy","4":"Esc key where Bill Joy had his.\r\n\r\n\/\/ Introduction \/\/\r\n\r\ntl;dr:\r\n\r\n    :imap <tab> <esc>\r\n    (See: https:\/\/en.wikipedia.org\/wiki\/Vi#Creation )\r\n\r\nIBM made some really odd decisions in popularizing the current keyboard, so\r\nwe're taking the power back.\r\n\r\nThe :imap above is the real heart of vim-joy: just make it so hitting tab in Insert mode gets you out into Normal mode. The only extra complexity in this script is due to the \"Training Wheels\" needed to get used\r\nto not being able to hit tab normally. The <Tab>=<Esc> thing is is most surprising when:\r\n\r\n* When on an empty line, meaning \"increase indent\". Use <C-t> instead.\r\n* When in the middle of a line, and trying to line things up. I don't have an exact solution for this, other than to do the work in Normal mode (e.g. with\r\n  <C-v> combined with << and >>)\r\n\r\nTo affect the behavior of this plugin, you can either:\r\n\r\n   let g:joy_pure = 1\r\n\r\nCommit to using <C-t> instead of <Tab> for indentation. At this point it\r\nbecomes identical in behavior to Insert Mode <Tab> == <Esc>.\r\n\r\n   let g:joy_mixed = 1\r\n\r\nTo turn off the nag message, and forget about <C-t> for indent.\r\n\r\n\/\/ Temporarily Disabling \/\/\r\n\r\nSometimes you want to affect the behavior only for this session (e.g. for pair\r\nprogramming with someone who isn't feeling it)\r\n\r\nTo go back to impure mode:\r\n\r\n   :unlet g:joy_pure\r\n\r\nTo make <Tab> be default in behavior:\r\n\r\n   :unimap <Tab>\r\n\r\n\/\/ Thanks \/\/\r\n\r\nThanks to tpope, as always!\r\n\r\n\/\/ About \/\/\r\n\r\nGrab the latest version or report a bug on Github: http:\/\/github.com\/rking\/vim-joy","install_details":"If you don't have a preferred installation method, I recommend\r\ninstalling pathogen.vim: https:\/\/github.com\/tpope\/vim-pathogen \u00e2\u0080\u0094\r\nthen simply copy and paste:\r\n\r\n    cd ~\/.vim\/bundle\r\n    git clone https:\/\/github.com\/rking\/vim-joy.git\r\n\r\n Once you run :Helptags you can view the manual with :help joy\r\n\r\n","5":"If you don't have a preferred installation method, I recommend\r\ninstalling pathogen.vim: https:\/\/github.com\/tpope\/vim-pathogen \u00e2\u0080\u0094\r\nthen simply copy and paste:\r\n\r\n    cd ~\/.vim\/bundle\r\n    git clone https:\/\/github.com\/rking\/vim-joy.git\r\n\r\n Once you run :Helptags you can view the manual with :help joy\r\n\r\n","first_name":"Ryan","6":"Ryan","last_name":"King","7":"King","releases":[{"0":"4481","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"joy.vim","4":"joy.vim","src_id":"19674","5":"19674","creation_date":"1363909520","6":"1363909520"}]},"4480":{"script_id":"4480","0":"4480","script_name":"composer.vim","1":"composer.vim","script_type":"utility","2":"utility","summary":"Composer plugin for Vim","3":"Composer plugin for Vim","description":"Composer (http:\/\/getcomposer.org\/) is a Dependency Manager for PHP. This vim plugin is a wrapper for php composer.phar command. You can call :Composer about for example.\r\n\r\n:ComposerInstall is a shortcut for php composer.phar install.\r\n\r\n:ComposerUpdate to run php composer.phar update.\r\n\r\n:ComposerOpenJson to open composer.json file in a new buffer.\r\n\r\n:ComposerOpenLock to open lock file.","4":"Composer (http:\/\/getcomposer.org\/) is a Dependency Manager for PHP. This vim plugin is a wrapper for php composer.phar command. You can call :Composer about for example.\r\n\r\n:ComposerInstall is a shortcut for php composer.phar install.\r\n\r\n:ComposerUpdate to run php composer.phar update.\r\n\r\n:ComposerOpenJson to open composer.json file in a new buffer.\r\n\r\n:ComposerOpenLock to open lock file.","install_details":"","5":"","first_name":"Denis","6":"Denis","last_name":"Tukalenko","7":"Tukalenko","releases":[{"0":"4480","vim_version":"7.0","1":"7.0","script_version":"0.3","2":"0.3","version_comment":"Add docs","3":"Add docs","package":"Composer.vim.tar.gz","4":"Composer.vim.tar.gz","src_id":"20772","5":"20772","creation_date":"1378739989","6":"1378739989"},{"0":"4480","vim_version":"7.0","1":"7.0","script_version":"0.2","2":"0.2","version_comment":"ComposerOpenJson and ComposerOpenLock ","3":"ComposerOpenJson and ComposerOpenLock ","package":"Composer.vim.tar.gz","4":"Composer.vim.tar.gz","src_id":"19774","5":"19774","creation_date":"1365326561","6":"1365326561"},{"0":"4480","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"Composer.vim.tar.gz","4":"Composer.vim.tar.gz","src_id":"19673","5":"19673","creation_date":"1363887469","6":"1363887469"}]},"4479":{"script_id":"4479","0":"4479","script_name":"iwilldiffer.vim","1":"iwilldiffer.vim","script_type":"utility","2":"utility","summary":"Show git\/hg\/bzr add\/mode\/del signs in buffer","3":"Show git\/hg\/bzr add\/mode\/del signs in buffer","description":"Overview\r\n\r\niwilldiffer is a vim plugin that shows you vcs diff add\/mod\/del lines in the gutter.\r\niwilldiffer supports git, hg, bzr\r\n\r\n\r\nDependencies\r\n\r\nYou need diff, python (2.6+), vim, and whichever supported vcs tool you wish to use.\r\n\r\n\r\nUsage\r\n\r\nInstall the plugin (TODO: describe the magic which is installing vim plugins)\r\nYou might want the following in your .vimrc:\r\nlet g:iwilldiffer_check_on_open=1\r\nlet g:iwilldiffer_check_on_save=1\r\n\r\n\r\nGutter Color\r\n\r\nGutter background color is controlled by value for highlight SignColumn. Change this value in your colorscheme or add to your .vimrc:\r\n\r\nhighlight SignColumn guibg=foo ctermbg=foo\r\n\r\n\r\nFor more information or to report issues:\r\nhttps:\/\/bitbucket.org\/sirpengi\/iwilldiffer","4":"Overview\r\n\r\niwilldiffer is a vim plugin that shows you vcs diff add\/mod\/del lines in the gutter.\r\niwilldiffer supports git, hg, bzr\r\n\r\n\r\nDependencies\r\n\r\nYou need diff, python (2.6+), vim, and whichever supported vcs tool you wish to use.\r\n\r\n\r\nUsage\r\n\r\nInstall the plugin (TODO: describe the magic which is installing vim plugins)\r\nYou might want the following in your .vimrc:\r\nlet g:iwilldiffer_check_on_open=1\r\nlet g:iwilldiffer_check_on_save=1\r\n\r\n\r\nGutter Color\r\n\r\nGutter background color is controlled by value for highlight SignColumn. Change this value in your colorscheme or add to your .vimrc:\r\n\r\nhighlight SignColumn guibg=foo ctermbg=foo\r\n\r\n\r\nFor more information or to report issues:\r\nhttps:\/\/bitbucket.org\/sirpengi\/iwilldiffer","install_details":"","5":"","first_name":"Shu","6":"Shu","last_name":"Chen","7":"Chen","releases":[{"0":"4479","vim_version":"7.3","1":"7.3","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"iwilldiffer-0.1.tar.gz","4":"iwilldiffer-0.1.tar.gz","src_id":"19668","5":"19668","creation_date":"1363802775","6":"1363802775"}]},"4478":{"script_id":"4478","0":"4478","script_name":"vim-run-live","1":"vim-run-live","script_type":"utility","2":"utility","summary":"Run or Preview current buffer in highly configurable ways","3":"Run or Preview current buffer in highly configurable ways","description":"  This plugin can...\r\n\r\n  * Run a specified shell command on an entire buffer.\r\n  * Run a specified shell command for a selection.\r\n  * Watch for changes in the buffer and run a shell command automatically.\r\n\r\nOther than the installation steps, this plugin requires no additional configuration to get started. When <Leader>r or :WatchBuffer is run, the plugin will ask for the shell command to associate with the current buffer.\r\n\r\nA lot of things in the plugin are configurable including the events which trigger the live preview. This plugin can also remember the entered shell command for future use.\r\n\r\nCheck out the Github page for more details with screenshots.\r\n\r\n==============================\r\nhttps:\/\/github.com\/notalex\/vim-run-live","4":"  This plugin can...\r\n\r\n  * Run a specified shell command on an entire buffer.\r\n  * Run a specified shell command for a selection.\r\n  * Watch for changes in the buffer and run a shell command automatically.\r\n\r\nOther than the installation steps, this plugin requires no additional configuration to get started. When <Leader>r or :WatchBuffer is run, the plugin will ask for the shell command to associate with the current buffer.\r\n\r\nA lot of things in the plugin are configurable including the events which trigger the live preview. This plugin can also remember the entered shell command for future use.\r\n\r\nCheck out the Github page for more details with screenshots.\r\n\r\n==============================\r\nhttps:\/\/github.com\/notalex\/vim-run-live","install_details":"The easiest way to install this plugin is using Vundle. Check out the following link for more details.\r\nhttps:\/\/github.com\/gmarik\/vundle","5":"The easiest way to install this plugin is using Vundle. Check out the following link for more details.\r\nhttps:\/\/github.com\/gmarik\/vundle","first_name":"Alex","6":"Alex","last_name":"Johnson","7":"Johnson","releases":[{"0":"4478","vim_version":"7.0","1":"7.0","script_version":"1.1","2":"1.1","version_comment":"fix issues with skipping results window feature","3":"fix issues with skipping results window feature","package":"vim-run-live.tar.gz","4":"vim-run-live.tar.gz","src_id":"20019","5":"20019","creation_date":"1367739587","6":"1367739587"},{"0":"4478","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"vim-run-live.tar.gz","4":"vim-run-live.tar.gz","src_id":"19663","5":"19663","creation_date":"1363701215","6":"1363701215"}]},"4477":{"script_id":"4477","0":"4477","script_name":"vim-php-namespace","1":"vim-php-namespace","script_type":"ftplugin","2":"ftplugin","summary":"imports php namespaces","3":"imports php namespaces","description":"vim-php-namespace is a vim script for inserting \"use\" statements automatically.","4":"vim-php-namespace is a vim script for inserting \"use\" statements automatically.","install_details":"See https:\/\/github.com\/arnaud-lb\/vim-php-namespace\/blob\/master\/README.markdown","5":"See https:\/\/github.com\/arnaud-lb\/vim-php-namespace\/blob\/master\/README.markdown","first_name":"Arnaud","6":"Arnaud","last_name":"Le Blanc","7":"Le Blanc","releases":[{"0":"4477","vim_version":"7.0","1":"7.0","script_version":"1","2":"1","version_comment":"Initial upload","3":"Initial upload","package":"vim-php-namespace.tar.gz","4":"vim-php-namespace.tar.gz","src_id":"19644","5":"19644","creation_date":"1363296824","6":"1363296824"}]},"4476":{"script_id":"4476","0":"4476","script_name":"vim-scroll-position","1":"vim-scroll-position","script_type":"utility","2":"utility","summary":"Displays the relative position of the cursor on the left side of the screen","3":"Displays the relative position of the cursor on the left side of the screen","description":"Displays the relative position of the cursor within the buffer on the left side of the screen using the `sign` feature.\r\nThis plugin is experimental and might slow down the rendering of Vim.\r\n\r\nhttps:\/\/github.com\/junegunn\/vim-scroll-position\r\n\r\nSign style can be customized as follows.\r\n\r\n\" Default markers\r\nlet g:scroll_position_marker         = '>'\r\nlet g:scroll_position_visual_begin   = '^'\r\nlet g:scroll_position_visual_middle  = ':'\r\nlet g:scroll_position_visual_end     = 'v'\r\nlet g:scroll_position_visual_overlap = '<>'\r\n\r\n\" Additional markers disabled by default due to slow rendering\r\n\" let g:scroll_position_jump = '-'\r\n\" let g:scroll_position_change = '+'\r\n\r\n\" Not to enable plugin by default\r\n\" let g:scroll_position_auto_enable = 0\r\n\r\nset t_Co=256\r\n\r\nhi SignColumn                  ctermbg=232\r\nhi ScrollPositionMarker        ctermfg=208 ctermbg=232\r\nhi ScrollPositionVisualBegin   ctermfg=196 ctermbg=232\r\nhi ScrollPositionVisualMiddle  ctermfg=196 ctermbg=232\r\nhi ScrollPositionVisualEnd     ctermfg=196 ctermbg=232\r\nhi ScrollPositionVisualOverlap ctermfg=196 ctermbg=232\r\nhi ScrollPositionChange        ctermfg=124 ctermbg=232\r\nhi ScrollPositionJump          ctermfg=131 ctermbg=232","4":"Displays the relative position of the cursor within the buffer on the left side of the screen using the `sign` feature.\r\nThis plugin is experimental and might slow down the rendering of Vim.\r\n\r\nhttps:\/\/github.com\/junegunn\/vim-scroll-position\r\n\r\nSign style can be customized as follows.\r\n\r\n\" Default markers\r\nlet g:scroll_position_marker         = '>'\r\nlet g:scroll_position_visual_begin   = '^'\r\nlet g:scroll_position_visual_middle  = ':'\r\nlet g:scroll_position_visual_end     = 'v'\r\nlet g:scroll_position_visual_overlap = '<>'\r\n\r\n\" Additional markers disabled by default due to slow rendering\r\n\" let g:scroll_position_jump = '-'\r\n\" let g:scroll_position_change = '+'\r\n\r\n\" Not to enable plugin by default\r\n\" let g:scroll_position_auto_enable = 0\r\n\r\nset t_Co=256\r\n\r\nhi SignColumn                  ctermbg=232\r\nhi ScrollPositionMarker        ctermfg=208 ctermbg=232\r\nhi ScrollPositionVisualBegin   ctermfg=196 ctermbg=232\r\nhi ScrollPositionVisualMiddle  ctermfg=196 ctermbg=232\r\nhi ScrollPositionVisualEnd     ctermfg=196 ctermbg=232\r\nhi ScrollPositionVisualOverlap ctermfg=196 ctermbg=232\r\nhi ScrollPositionChange        ctermfg=124 ctermbg=232\r\nhi ScrollPositionJump          ctermfg=131 ctermbg=232","install_details":"Extract in ~\/.vim, or use Pathogen or Vundle","5":"Extract in ~\/.vim, or use Pathogen or Vundle","first_name":"Junegunn","6":"Junegunn","last_name":"Choi","7":"Choi","releases":[{"0":"4476","vim_version":"7.3","1":"7.3","script_version":"1.3","2":"1.3","version_comment":"Bug fixes and improvements","3":"Bug fixes and improvements","package":"vim-scroll-position.zip","4":"vim-scroll-position.zip","src_id":"20350","5":"20350","creation_date":"1371126959","6":"1371126959"}]},"4475":{"script_id":"4475","0":"4475","script_name":"voogle","1":"voogle","script_type":"utility","2":"utility","summary":"search google from vim easily with any modern browser","3":"search google from vim easily with any modern browser","description":"Opens a browser window with the word under the cursor or with the visually selected text.\r\nJust type `gs` in normal or visual mode\r\nSupported browsers: Chromium, Chrome, Firefox, links\r\n\r\nhttps:\/\/github.com\/g3orge\/vim-voogle","4":"Opens a browser window with the word under the cursor or with the visually selected text.\r\nJust type `gs` in normal or visual mode\r\nSupported browsers: Chromium, Chrome, Firefox, links\r\n\r\nhttps:\/\/github.com\/g3orge\/vim-voogle","install_details":"Just use pathogen or put the voogle.vim file inside plugin\/ directory","5":"Just use pathogen or put the voogle.vim file inside plugin\/ directory","first_name":"George","6":"George","last_name":"Papanikolaou","7":"Papanikolaou","releases":[{"0":"4475","vim_version":"7.0","1":"7.0","script_version":"1.2","2":"1.2","version_comment":"now works everywhere... I think. (incl. Mac OS X)","3":"now works everywhere... I think. (incl. Mac OS X)","package":"voogle.vim","4":"voogle.vim","src_id":"19873","5":"19873","creation_date":"1366503290","6":"1366503290"},{"0":"4475","vim_version":"7.0","1":"7.0","script_version":"1.1","2":"1.1","version_comment":"more configuration options and silent execution","3":"more configuration options and silent execution","package":"voogle.zip","4":"voogle.zip","src_id":"19648","5":"19648","creation_date":"1363345454","6":"1363345454"},{"0":"4475","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"voogle.zip","4":"voogle.zip","src_id":"19640","5":"19640","creation_date":"1363265636","6":"1363265636"}]},"4474":{"script_id":"4474","0":"4474","script_name":"interactive-replace","1":"interactive-replace","script_type":"utility","2":"utility","summary":"InteractiveReplace lets you choose replacement text for your search","3":"InteractiveReplace lets you choose replacement text for your search","description":"InteractiveReplace lets you interactively choose replacement text while you search\/replace.\r\n\r\n## Usage ##\r\nJust type\r\n\r\n    :InteractiveReplace\r\n\r\nat the Vim console, or type the shortcut binding in normal mode:\r\n\r\n     <leader>r\r\n\r\n(on my system that's `\\r`).\r\n\r\n\r\n## Examples ##\r\nSay you wanted to find and replace all occurrences of *Bel-air* in a text file, but you wanted to specify what the replacement text is each time without having to redo a substitution or create a very complicated regex.\r\n\r\nWith a search performed (e.g. `\/Bel-air`), type `\\r` to bring up InteractiveReplace. Then for each highlighted term, type the replacement text and press `Enter`.\r\n\r\nEasy consecutive substitutions: http:\/\/www.planetharold.com\/projects\/interactive-replace\/interactive-replace-1.png\r\n\r\n----------------\r\n\r\nIn a programming context, you can easily substitute variable names stemming from one `o`pened line.\r\n\r\nFor example, to write out a skeleton for your replaces, you could type (with the cursor on line 6):\r\n\r\n     7odrawChart data.tmp[Esc]\r\n\r\nto get: http:\/\/www.planetharold.com\/projects\/interactive-replace\/interactive-replace-2.png\r\n\r\nNow use InteractiveReplace on `\/tmp` to sequentially replace variable names: http:\/\/www.planetharold.com\/projects\/interactive-replace\/interactive-replace-3.png\r\n\r\n## F.A.Q. ##\r\n* How do I install Pathogen?\r\n     * Just put [pathogen.vim] into your ~\/.vim\/autoload folder. Then put these two lines in your *.vimrc* file: \r\n        * filetype plugin indent on\r\n        * execute pathogen#infect()\r\n* How do I install InteractiveReplace without using Pathogen?\r\n     * If you wanna be really dirty about it, download the zipball from https:\/\/github.com\/hwrod\/interactive-replace and extract the contents to your Vim directory.\r\n* How do I update InteractiveReplace?\r\n    * The beauty of installing with Pathogen is that you `cd` into `~\/.vim\/bundle\/interactive-replace\/` and type `$ git pull` to get the latest updates.\r\n\r\n## Todo\r\n\r\nThere are a few ways InteractiveReplace can be improved, including:\r\n\r\n* allowing `Enter` to skip replace (make no change)\r\n* highlighting the current search term in a different color\r\n* if nothing's in the `\/` register, ask user for a search term\r\n\r\nPull requests are highly encouraged (https:\/\/github.com\/hwrod\/interactive-replace). Questions\/comments welcome too.\r\n","4":"InteractiveReplace lets you interactively choose replacement text while you search\/replace.\r\n\r\n## Usage ##\r\nJust type\r\n\r\n    :InteractiveReplace\r\n\r\nat the Vim console, or type the shortcut binding in normal mode:\r\n\r\n     <leader>r\r\n\r\n(on my system that's `\\r`).\r\n\r\n\r\n## Examples ##\r\nSay you wanted to find and replace all occurrences of *Bel-air* in a text file, but you wanted to specify what the replacement text is each time without having to redo a substitution or create a very complicated regex.\r\n\r\nWith a search performed (e.g. `\/Bel-air`), type `\\r` to bring up InteractiveReplace. Then for each highlighted term, type the replacement text and press `Enter`.\r\n\r\nEasy consecutive substitutions: http:\/\/www.planetharold.com\/projects\/interactive-replace\/interactive-replace-1.png\r\n\r\n----------------\r\n\r\nIn a programming context, you can easily substitute variable names stemming from one `o`pened line.\r\n\r\nFor example, to write out a skeleton for your replaces, you could type (with the cursor on line 6):\r\n\r\n     7odrawChart data.tmp[Esc]\r\n\r\nto get: http:\/\/www.planetharold.com\/projects\/interactive-replace\/interactive-replace-2.png\r\n\r\nNow use InteractiveReplace on `\/tmp` to sequentially replace variable names: http:\/\/www.planetharold.com\/projects\/interactive-replace\/interactive-replace-3.png\r\n\r\n## F.A.Q. ##\r\n* How do I install Pathogen?\r\n     * Just put [pathogen.vim] into your ~\/.vim\/autoload folder. Then put these two lines in your *.vimrc* file: \r\n        * filetype plugin indent on\r\n        * execute pathogen#infect()\r\n* How do I install InteractiveReplace without using Pathogen?\r\n     * If you wanna be really dirty about it, download the zipball from https:\/\/github.com\/hwrod\/interactive-replace and extract the contents to your Vim directory.\r\n* How do I update InteractiveReplace?\r\n    * The beauty of installing with Pathogen is that you `cd` into `~\/.vim\/bundle\/interactive-replace\/` and type `$ git pull` to get the latest updates.\r\n\r\n## Todo\r\n\r\nThere are a few ways InteractiveReplace can be improved, including:\r\n\r\n* allowing `Enter` to skip replace (make no change)\r\n* highlighting the current search term in a different color\r\n* if nothing's in the `\/` register, ask user for a search term\r\n\r\nPull requests are highly encouraged (https:\/\/github.com\/hwrod\/interactive-replace). Questions\/comments welcome too.\r\n","install_details":"## Install ##\r\nIf you wanna be quick-and-dirty, download the zipfile below and extract the contents to your Vim directory.\r\n\r\nBetter yet, assuming you have Git and Pathogen installed, which you should, just run:\r\n\r\n     $ git clone https:\/\/github.com\/hwrod\/interactive-replace.git ~\/.vim\/bundle\/interactive-replace\r\n\r\nOptionally, to configure a different key binding, add this line to your *.vimrc* file:\r\n\r\n    let g:InteractiveReplace_map = 'X'\r\n\r\nwhere *X* is something like <F5> or \\i","5":"## Install ##\r\nIf you wanna be quick-and-dirty, download the zipfile below and extract the contents to your Vim directory.\r\n\r\nBetter yet, assuming you have Git and Pathogen installed, which you should, just run:\r\n\r\n     $ git clone https:\/\/github.com\/hwrod\/interactive-replace.git ~\/.vim\/bundle\/interactive-replace\r\n\r\nOptionally, to configure a different key binding, add this line to your *.vimrc* file:\r\n\r\n    let g:InteractiveReplace_map = 'X'\r\n\r\nwhere *X* is something like <F5> or \\i","first_name":"Harold","6":"Harold","last_name":"Rodriguez","7":"Rodriguez","releases":[{"0":"4474","vim_version":"7.0","1":"7.0","script_version":"1.0.0","2":"1.0.0","version_comment":"Initial upload","3":"Initial upload","package":"interactive-replace.zip","4":"interactive-replace.zip","src_id":"19639","5":"19639","creation_date":"1363226686","6":"1363226686"}]},"4473":{"script_id":"4473","0":"4473","script_name":"ghcmod","1":"ghcmod","script_type":"ftplugin","2":"ftplugin","summary":"Happy Haskell programming on Vim, powered by ghc-mod","3":"Happy Haskell programming on Vim, powered by ghc-mod","description":"https:\/\/github.com\/eagletmt\/ghcmod-vim\r\n\r\n* Displaying the type of sub-expressions (ghc-mod type)\r\n* Displaying error\/warning messages and their locations (ghc-mod check and ghc-mod lint)\r\n* Displaying the expansion of splices (ghc-mod expand)\r\n","4":"https:\/\/github.com\/eagletmt\/ghcmod-vim\r\n\r\n* Displaying the type of sub-expressions (ghc-mod type)\r\n* Displaying error\/warning messages and their locations (ghc-mod check and ghc-mod lint)\r\n* Displaying the expansion of splices (ghc-mod expand)\r\n","install_details":"","5":"","first_name":"Kohei","6":"Kohei","last_name":"Suzuki","7":"Suzuki","releases":[{"0":"4473","vim_version":"7.0","1":"7.0","script_version":"1.3.1","2":"1.3.1","version_comment":"https:\/\/github.com\/eagletmt\/ghcmod-vim\/releases\/tag\/v1.3.1","3":"https:\/\/github.com\/eagletmt\/ghcmod-vim\/releases\/tag\/v1.3.1","package":"ghcmod-vim-1.3.1.zip","4":"ghcmod-vim-1.3.1.zip","src_id":"23482","5":"23482","creation_date":"1437900098","6":"1437900098"},{"0":"4473","vim_version":"7.0","1":"7.0","script_version":"1.3.0","2":"1.3.0","version_comment":"https:\/\/github.com\/eagletmt\/ghcmod-vim\/releases\/tag\/v1.3.0","3":"https:\/\/github.com\/eagletmt\/ghcmod-vim\/releases\/tag\/v1.3.0","package":"ghcmod-vim-1.3.0.zip","4":"ghcmod-vim-1.3.0.zip","src_id":"23041","5":"23041","creation_date":"1426522477","6":"1426522477"},{"0":"4473","vim_version":"7.0","1":"7.0","script_version":"1.2.0","2":"1.2.0","version_comment":"- Support Cabal sandbox\r\n- Support lhaskell\r\n- Add another way to open the quickfix\r\n- Workaround `ghcmod#util#is_abspath()` on Windows with Vim < 7.4.001\r\n\r\nhttps:\/\/github.com\/eagletmt\/ghcmod-vim\/releases\/tag\/v1.2.0","3":"- Support Cabal sandbox\r\n- Support lhaskell\r\n- Add another way to open the quickfix\r\n- Workaround `ghcmod#util#is_abspath()` on Windows with Vim < 7.4.001\r\n\r\nhttps:\/\/github.com\/eagletmt\/ghcmod-vim\/releases\/tag\/v1.2.0","package":"ghcmod-vim-1.2.0.zip","4":"ghcmod-vim-1.2.0.zip","src_id":"21415","5":"21415","creation_date":"1391270927","6":"1391270927"},{"0":"4473","vim_version":"7.0","1":"7.0","script_version":"1.1.0","2":"1.1.0","version_comment":"- Specify line separator by \"-b\" option\r\n","3":"- Specify line separator by \"-b\" option\r\n","package":"ghcmod-vim-1.1.0.zip","4":"ghcmod-vim-1.1.0.zip","src_id":"20921","5":"20921","creation_date":"1381850562","6":"1381850562"},{"0":"4473","vim_version":"7.0","1":"7.0","script_version":"1.0.0","2":"1.0.0","version_comment":"- Refactor many autoload functions\r\n- Speed up boot time by moving autoload functions used at loading ftplugins\r\n- Add commands with `!` that is executed even if the current buffer is modified\r\n- Show splicing end locations in `:GhcModExpand`\r\n- Fix escaping in `:GhcModInfoPreview`\r\n- Fix ignorance of `g:ghcmod_ghc_options`","3":"- Refactor many autoload functions\r\n- Speed up boot time by moving autoload functions used at loading ftplugins\r\n- Add commands with `!` that is executed even if the current buffer is modified\r\n- Show splicing end locations in `:GhcModExpand`\r\n- Fix escaping in `:GhcModInfoPreview`\r\n- Fix ignorance of `g:ghcmod_ghc_options`","package":"ghcmod-vim-1.0.0.zip","4":"ghcmod-vim-1.0.0.zip","src_id":"19931","5":"19931","creation_date":"1366859353","6":"1366859353"},{"0":"4473","vim_version":"7.0","1":"7.0","script_version":"0.4.0","2":"0.4.0","version_comment":"Initial upload","3":"Initial upload","package":"ghcmod-vim-0.4.0.zip","4":"ghcmod-vim-0.4.0.zip","src_id":"19634","5":"19634","creation_date":"1363155938","6":"1363155938"}]},"4472":{"script_id":"4472","0":"4472","script_name":"obsession.vim","1":"obsession.vim","script_type":"utility","2":"utility","summary":"Continuously updated session files","3":"Continuously updated session files","description":"Vim features a :mksession command to write a file containing the current state of Vim: window positions, open folds, stuff like that.  For most of my existence, I found the interface way too awkward and manual to be useful, but I've recently discovered that the only thing standing between me and simple, no-hassle Vim sessions is a few tweaks:\r\n\r\n* Instead of making me remember to capture the session immediately before exiting Vim, allow me to do it at any time, and automatically re-invoke :mksession immediately before exit.\r\n* Also invoke :mksession whenever the layout changes (in particular, on BufEnter), so that even if Vim exits abnormally, I'm good to go.  If I load an existing session, automatically keep it updated as above.\r\n* If I try to create a new session on top of an existing session, don't refuse to overwrite it.  Just do what I mean.  If I pass in a directory rather than a file name, just create a Session.vim inside of it.\r\n* Don't capture options and maps.  Options are sometimes mutilated and maps just interfere with updating plugins.\r\n\r\nUse :Obsess (with optional file\/directory name) to start recording to a session file and :Obsess! to stop and throw it away.  That's it.  Load a session in the usual manner: vim -S, or :source it.\r\n\r\nhttps:\/\/github.com\/tpope\/vim-obsession","4":"Vim features a :mksession command to write a file containing the current state of Vim: window positions, open folds, stuff like that.  For most of my existence, I found the interface way too awkward and manual to be useful, but I've recently discovered that the only thing standing between me and simple, no-hassle Vim sessions is a few tweaks:\r\n\r\n* Instead of making me remember to capture the session immediately before exiting Vim, allow me to do it at any time, and automatically re-invoke :mksession immediately before exit.\r\n* Also invoke :mksession whenever the layout changes (in particular, on BufEnter), so that even if Vim exits abnormally, I'm good to go.  If I load an existing session, automatically keep it updated as above.\r\n* If I try to create a new session on top of an existing session, don't refuse to overwrite it.  Just do what I mean.  If I pass in a directory rather than a file name, just create a Session.vim inside of it.\r\n* Don't capture options and maps.  Options are sometimes mutilated and maps just interfere with updating plugins.\r\n\r\nUse :Obsess (with optional file\/directory name) to start recording to a session file and :Obsess! to stop and throw it away.  That's it.  Load a session in the usual manner: vim -S, or :source it.\r\n\r\nhttps:\/\/github.com\/tpope\/vim-obsession","install_details":"Extract in ~\/.vim (~\\vimfiles on Windows).","5":"Extract in ~\/.vim (~\\vimfiles on Windows).","first_name":"Tim","6":"Tim","last_name":"Pope","7":"Pope","releases":[{"0":"4472","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"obsession.zip","4":"obsession.zip","src_id":"19624","5":"19624","creation_date":"1362973571","6":"1362973571"}]},"4471":{"script_id":"4471","0":"4471","script_name":"noctu.vim","1":"noctu.vim","script_type":"color scheme","2":"color scheme","summary":"16-color terminal color scheme","3":"16-color terminal color scheme","description":"Rather than specifying particular color values for Vim, I prefer to have consistent colors across *all* software that I use in the terminal (e.g., colored output from git, tmux's status bar, etc.). Towards that end, this scheme is restricted to 16 ANSI colors (0 through 15), the representation of which can be redefined by configuring your terminal emulator. This means that you can change your color scheme \"globally\" without having to edit this script.\r\n\r\nThe color scheme has been tested against the following file types:\r\n\r\n- CSS\r\n- Git (commit messages, etc.)\r\n- HTML\r\n- JavaScript\r\n- LESS\r\n- Markdown\r\n- PHP\r\n- Ruby\r\n- Shell\r\n- Vim help\r\n- Vim script\r\n- Vimwiki\r\n- XML\r\n- YAML\r\n\r\nGitHub repository:\r\nhttps:\/\/github.com\/noahfrederick\/vim-noctu","4":"Rather than specifying particular color values for Vim, I prefer to have consistent colors across *all* software that I use in the terminal (e.g., colored output from git, tmux's status bar, etc.). Towards that end, this scheme is restricted to 16 ANSI colors (0 through 15), the representation of which can be redefined by configuring your terminal emulator. This means that you can change your color scheme \"globally\" without having to edit this script.\r\n\r\nThe color scheme has been tested against the following file types:\r\n\r\n- CSS\r\n- Git (commit messages, etc.)\r\n- HTML\r\n- JavaScript\r\n- LESS\r\n- Markdown\r\n- PHP\r\n- Ruby\r\n- Shell\r\n- Vim help\r\n- Vim script\r\n- Vimwiki\r\n- XML\r\n- YAML\r\n\r\nGitHub repository:\r\nhttps:\/\/github.com\/noahfrederick\/vim-noctu","install_details":"Just stick noctu.vim in your colors\/ directory, or if you manage your plug-ins with pathogen:\r\n\r\n    git clone git:\/\/github.com\/noahfrederick\/vim-noctu.git ~\/.vim\/bundle\/noctu","5":"Just stick noctu.vim in your colors\/ directory, or if you manage your plug-ins with pathogen:\r\n\r\n    git clone git:\/\/github.com\/noahfrederick\/vim-noctu.git ~\/.vim\/bundle\/noctu","first_name":"Noah","6":"Noah","last_name":"Frederick","7":"Frederick","releases":[{"0":"4471","vim_version":"7.0","1":"7.0","script_version":"1.2.1","2":"1.2.1","version_comment":"Better spelling highlights, better IncSearch","3":"Better spelling highlights, better IncSearch","package":"vim-noctu.zip","4":"vim-noctu.zip","src_id":"19784","5":"19784","creation_date":"1365452573","6":"1365452573"},{"0":"4471","vim_version":"7.0","1":"7.0","script_version":"1.1.0","2":"1.1.0","version_comment":"Initial upload","3":"Initial upload","package":"vim-noctu.zip","4":"vim-noctu.zip","src_id":"19623","5":"19623","creation_date":"1362971917","6":"1362971917"}]},"4470":{"script_id":"4470","0":"4470","script_name":"hemisu.vim","1":"hemisu.vim","script_type":"color scheme","2":"color scheme","summary":"A color scheme with light and dark variants","3":"A color scheme with light and dark variants","description":"Features:\r\n- Two modes: one optimized for daytime, the other optimized for low light conditions\r\n- Made to work with both GUIs (gui) and color terminals (cterm)\r\n- Provides harmonious colors and styles for all predefined UI elements and syntax groups\r\n\r\nHomepage:\r\nhttp:\/\/noahfrederick.com\/vim-color-scheme-hemisu\/\r\n\r\nGitHub repository:\r\nhttps:\/\/github.com\/noahfrederick\/vim-hemisu","4":"Features:\r\n- Two modes: one optimized for daytime, the other optimized for low light conditions\r\n- Made to work with both GUIs (gui) and color terminals (cterm)\r\n- Provides harmonious colors and styles for all predefined UI elements and syntax groups\r\n\r\nHomepage:\r\nhttp:\/\/noahfrederick.com\/vim-color-scheme-hemisu\/\r\n\r\nGitHub repository:\r\nhttps:\/\/github.com\/noahfrederick\/vim-hemisu","install_details":"Place hemisu.vim in your colors\/ runtime directory and set the color scheme with `:colorscheme hemisu`.","5":"Place hemisu.vim in your colors\/ runtime directory and set the color scheme with `:colorscheme hemisu`.","first_name":"Noah","6":"Noah","last_name":"Frederick","7":"Frederick","releases":[{"0":"4470","vim_version":"7.0","1":"7.0","script_version":"3.4","2":"3.4","version_comment":"Initial upload","3":"Initial upload","package":"vim-hemisu.zip","4":"vim-hemisu.zip","src_id":"19622","5":"19622","creation_date":"1362971454","6":"1362971454"}]},"4469":{"script_id":"4469","0":"4469","script_name":"vim-forrestgump","1":"vim-forrestgump","script_type":"utility","2":"utility","summary":"Run code inline and on-the-fly in vim. Inspired by TextMate's ⌘R.","3":"Run code inline and on-the-fly in vim. Inspired by TextMate's ⌘R.","description":"One thing I miss from textmate? ⌘R and ⌥⌘R.\r\n\r\nThe former would run the current script and display output in a separate window. The latter would run selected code (or the current line).\r\n\r\nThis simple plugin aims to mimic that.\r\n\r\n\r\nLANGUAGES SUPPORTED\r\nThe following interpreters should work out of the box (and can be changed to your liking):\r\n\r\nlet g:forrestgumps = {\r\n    \"php\":           [\"php\", \"<?php \"],\r\n    \"python\":      [\"python\"],\r\n    \"ruby\":          [\"ruby\"],\r\n    \"perl\":           [\"perl\"],\r\n    \"javascript\": [\"node\"],\r\n    \"coffee\":       [\"coffee\"],\r\n    \"sh\":             [\"sh\"],\r\n\r\n    \" Example:\r\n    \"&filetype\":   [\"\/usr\/bin\/&filetype\", \"Prepend this to code\"]\r\n}\r\n\r\n\r\nKEYMAPS\r\n\r\n    nmap <leader>r      Run entire file (doesn't have to be saved)\r\n    vmap <leader>r      Run current or selected line(s)","4":"One thing I miss from textmate? ⌘R and ⌥⌘R.\r\n\r\nThe former would run the current script and display output in a separate window. The latter would run selected code (or the current line).\r\n\r\nThis simple plugin aims to mimic that.\r\n\r\n\r\nLANGUAGES SUPPORTED\r\nThe following interpreters should work out of the box (and can be changed to your liking):\r\n\r\nlet g:forrestgumps = {\r\n    \"php\":           [\"php\", \"<?php \"],\r\n    \"python\":      [\"python\"],\r\n    \"ruby\":          [\"ruby\"],\r\n    \"perl\":           [\"perl\"],\r\n    \"javascript\": [\"node\"],\r\n    \"coffee\":       [\"coffee\"],\r\n    \"sh\":             [\"sh\"],\r\n\r\n    \" Example:\r\n    \"&filetype\":   [\"\/usr\/bin\/&filetype\", \"Prepend this to code\"]\r\n}\r\n\r\n\r\nKEYMAPS\r\n\r\n    nmap <leader>r      Run entire file (doesn't have to be saved)\r\n    vmap <leader>r      Run current or selected line(s)","install_details":"Unzip the tarball, and put the files into their respective ~\/.vim\/* folders. Alternatively, I'd recommend Vundle (https:\/\/github.com\/gmarik\/vundle), then all you'd need is: \r\n\r\n    Bundle \"hlissner\/vim-forrestgump\" \r\n\r\nThen restart and run: \r\n\r\n    :BundleInstall","5":"Unzip the tarball, and put the files into their respective ~\/.vim\/* folders. Alternatively, I'd recommend Vundle (https:\/\/github.com\/gmarik\/vundle), then all you'd need is: \r\n\r\n    Bundle \"hlissner\/vim-forrestgump\" \r\n\r\nThen restart and run: \r\n\r\n    :BundleInstall","first_name":"Henrik","6":"Henrik","last_name":"Lissner","7":"Lissner","releases":[{"0":"4469","vim_version":"7.0","1":"7.0","script_version":"1.0.2","2":"1.0.2","version_comment":"- Add shebang detection","3":"- Add shebang detection","package":"vim-forrestgump.tar.gz","4":"vim-forrestgump.tar.gz","src_id":"19657","5":"19657","creation_date":"1363500911","6":"1363500911"},{"0":"4469","vim_version":"7.0","1":"7.0","script_version":"1.0.1","2":"1.0.1","version_comment":"Initial upload","3":"Initial upload","package":"vim-forrestgump.tar.gz","4":"vim-forrestgump.tar.gz","src_id":"19614","5":"19614","creation_date":"1362868779","6":"1362868779"}]},"4468":{"script_id":"4468","0":"4468","script_name":"dubs-scheme","1":"dubs-scheme","script_type":"color scheme","2":"color scheme","summary":"a color scheme mainly for programming","3":"a color scheme mainly for programming","description":"This scheme is intended to help software developers to focus on the actual work and not on the elements of the programming languages.\r\n\r\nTested on different systems, most extensively on MS.\r\n\r\nLater version is tested with older VIM versions, too.\r\n\r\nInspired by the music of Tangerine Dream.","4":"This scheme is intended to help software developers to focus on the actual work and not on the elements of the programming languages.\r\n\r\nTested on different systems, most extensively on MS.\r\n\r\nLater version is tested with older VIM versions, too.\r\n\r\nInspired by the music of Tangerine Dream.","install_details":"Save the file into the directory containing the color schemes.","5":"Save the file into the directory containing the color schemes.","first_name":"Gabor","6":"Gabor","last_name":"Urban","7":"Urban","releases":[{"0":"4468","vim_version":"7.0","1":"7.0","script_version":"0.2","2":"0.2","version_comment":"There are more syntax elements added and finer settings are created for console mode.\r\n\r\n","3":"There are more syntax elements added and finer settings are created for console mode.\r\n\r\n","package":"dubs.vim","4":"dubs.vim","src_id":"21977","5":"21977","creation_date":"1401698771","6":"1401698771"},{"0":"4468","vim_version":"7.2","1":"7.2","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"dubs.vim","4":"dubs.vim","src_id":"19612","5":"19612","creation_date":"1362861411","6":"1362861411"}]},"4467":{"script_id":"4467","0":"4467","script_name":"vim-multiedit","1":"vim-multiedit","script_type":"utility","2":"utility","summary":"Multi-selection editing for vim, inspired by Sublime Text","3":"Multi-selection editing for vim, inspired by Sublime Text","description":"Do you envy Sublime Text 2's multiple selection and editing feature? This plugin tries to fill that text cursor shaped gap in your heart by letting you specify \"regions\" of text and edit them all from one place. \r\n\r\nUSAGE \r\nAdd edit-regions by using <leader>m in visual mode or <leader>mm in normal mode (selects the word under the cursor). You can also add disposable markers using <leader>mi (before cursor) and <leader>ma (after cursor).\r\n\r\nOnce all the regions are set, start editing with <leader>M (or <leader>C which will clear the main region before you start editing).\r\n\r\nWhen you're done, leave insert mode and it will copy the changes to all other regions.\r\n\r\nKEY MAPS \r\n\r\n    \" Insert a disposable marker after the cursor\r\n    nmap <leader>ma :MultieditAddMark a<CR>\r\n\r\n    \" Insert a disposable marker before the cursor\r\n    nmap <leader>mi :MultieditAddMark i<CR>\r\n\r\n    \" Make a new line and insert a marker\r\n    nmap <leader>mo o<Esc>:MultieditAddMark i<CR>\r\n    nmap <leader>mO O<Esc>:MultieditAddMark i<CR>\r\n\r\n    \" Insert a marker at the end\/start of a line\r\n    nmap <leader>mA $:MultieditAddMark a<CR>\r\n    nmap <leader>mI ^:MultieditAddMark i<CR>\r\n\r\n    \" Make the current selection\/word an edit region\r\n    vmap <leader>m :MultieditAddRegion<CR>  \r\n    nmap <leader>mm viw:MultieditAddRegion<CR>\r\n\r\n    \" Restore the regions from a previous edit session\r\n    nmap <leader>mu :MultieditRestore<CR>\r\n\r\n    \" Move cursor between regions n times\r\n    map ]m :MultieditHop 1<CR>\r\n    map [m :MultieditHop -1<CR>\r\n\r\n    \" Start editing!\r\n    nmap <leader>M :Multiedit<CR>\r\n\r\n    \" Clear the word and start editing\r\n    nmap <leader>C :Multiedit!<CR>\r\n\r\n    \" Unset the region under the cursor\r\n    nmap <silent> <leader>md :MultieditClear<CR>\r\n\r\n    \" Unset all regions\r\n    nmap <silent> <leader>mr :MultieditReset<CR>\r\n\r\nCUSTOMIZING\r\n\r\n    \" Disable all mappings? (So you can set your own)\r\n    let g:multiedit_no_mappings = 0\r\n\r\n    \" Reset all regions on InsertLeave when finished?\r\n    let g:multiedit_auto_reset = 1\r\n\r\n    \" Disposable marker character (beware characters with strlen > 1 - like\r\n    \" special\/unicode symbols - they don't work).\r\n    let g:multiedit_mark_character = '|'\r\n\r\n    \" If no selections are present and you initiate edit mode, should it\r\n    \" restore the previous regions?\r\n    let g:multiedit_auto_restore = 1\r\n\r\nThe highlight regions can be customized, these are the defaults:\r\n    hi default link MultieditRegions Search\r\n    hi default link MultieditFirstRegion IncSearch","4":"Do you envy Sublime Text 2's multiple selection and editing feature? This plugin tries to fill that text cursor shaped gap in your heart by letting you specify \"regions\" of text and edit them all from one place. \r\n\r\nUSAGE \r\nAdd edit-regions by using <leader>m in visual mode or <leader>mm in normal mode (selects the word under the cursor). You can also add disposable markers using <leader>mi (before cursor) and <leader>ma (after cursor).\r\n\r\nOnce all the regions are set, start editing with <leader>M (or <leader>C which will clear the main region before you start editing).\r\n\r\nWhen you're done, leave insert mode and it will copy the changes to all other regions.\r\n\r\nKEY MAPS \r\n\r\n    \" Insert a disposable marker after the cursor\r\n    nmap <leader>ma :MultieditAddMark a<CR>\r\n\r\n    \" Insert a disposable marker before the cursor\r\n    nmap <leader>mi :MultieditAddMark i<CR>\r\n\r\n    \" Make a new line and insert a marker\r\n    nmap <leader>mo o<Esc>:MultieditAddMark i<CR>\r\n    nmap <leader>mO O<Esc>:MultieditAddMark i<CR>\r\n\r\n    \" Insert a marker at the end\/start of a line\r\n    nmap <leader>mA $:MultieditAddMark a<CR>\r\n    nmap <leader>mI ^:MultieditAddMark i<CR>\r\n\r\n    \" Make the current selection\/word an edit region\r\n    vmap <leader>m :MultieditAddRegion<CR>  \r\n    nmap <leader>mm viw:MultieditAddRegion<CR>\r\n\r\n    \" Restore the regions from a previous edit session\r\n    nmap <leader>mu :MultieditRestore<CR>\r\n\r\n    \" Move cursor between regions n times\r\n    map ]m :MultieditHop 1<CR>\r\n    map [m :MultieditHop -1<CR>\r\n\r\n    \" Start editing!\r\n    nmap <leader>M :Multiedit<CR>\r\n\r\n    \" Clear the word and start editing\r\n    nmap <leader>C :Multiedit!<CR>\r\n\r\n    \" Unset the region under the cursor\r\n    nmap <silent> <leader>md :MultieditClear<CR>\r\n\r\n    \" Unset all regions\r\n    nmap <silent> <leader>mr :MultieditReset<CR>\r\n\r\nCUSTOMIZING\r\n\r\n    \" Disable all mappings? (So you can set your own)\r\n    let g:multiedit_no_mappings = 0\r\n\r\n    \" Reset all regions on InsertLeave when finished?\r\n    let g:multiedit_auto_reset = 1\r\n\r\n    \" Disposable marker character (beware characters with strlen > 1 - like\r\n    \" special\/unicode symbols - they don't work).\r\n    let g:multiedit_mark_character = '|'\r\n\r\n    \" If no selections are present and you initiate edit mode, should it\r\n    \" restore the previous regions?\r\n    let g:multiedit_auto_restore = 1\r\n\r\nThe highlight regions can be customized, these are the defaults:\r\n    hi default link MultieditRegions Search\r\n    hi default link MultieditFirstRegion IncSearch","install_details":"Unzip the tarball, and put the files into their respective ~\/.vim\/* folders. Alternatively, I'd recommend Vundle (https:\/\/github.com\/gmarik\/vundle), then all you'd need is: \r\n\r\n    Bundle \"hlissner\/vim-multiedit\" \r\n\r\nThen restart and run: \r\n\r\n    :BundleInstall \r\n\r\n--------------------- \r\nGITHUB: https:\/\/github.com\/hlissner\/vim-multiedit","5":"Unzip the tarball, and put the files into their respective ~\/.vim\/* folders. Alternatively, I'd recommend Vundle (https:\/\/github.com\/gmarik\/vundle), then all you'd need is: \r\n\r\n    Bundle \"hlissner\/vim-multiedit\" \r\n\r\nThen restart and run: \r\n\r\n    :BundleInstall \r\n\r\n--------------------- \r\nGITHUB: https:\/\/github.com\/hlissner\/vim-multiedit","first_name":"Henrik","6":"Henrik","last_name":"Lissner","7":"Lissner","releases":[{"0":"4467","vim_version":"7.0","1":"7.0","script_version":"2.0.2","2":"2.0.2","version_comment":"- Fix: when the region goes crazy when the text is at the start of the line (when\r\n  len == 0 it would suddenly expand to the length of the line)\r\n- Fix: when the cursor deletes past its boundaries it will leave multiedit\r\n  mode and reset your regions","3":"- Fix: when the region goes crazy when the text is at the start of the line (when\r\n  len == 0 it would suddenly expand to the length of the line)\r\n- Fix: when the cursor deletes past its boundaries it will leave multiedit\r\n  mode and reset your regions","package":"vim-multiedit.tar.gz","4":"vim-multiedit.tar.gz","src_id":"19718","5":"19718","creation_date":"1364503198","6":"1364503198"},{"0":"4467","vim_version":"7.0","1":"7.0","script_version":"2.0.1","2":"2.0.1","version_comment":"- New: four new keybinds for adding markers to the start\/end of a line or on\r\n  the next\/previous line\r\n- Changed: auto-removing disposable markers where entering insert mode (had\r\n  a strange effect when regions were at the start of a line)","3":"- New: four new keybinds for adding markers to the start\/end of a line or on\r\n  the next\/previous line\r\n- Changed: auto-removing disposable markers where entering insert mode (had\r\n  a strange effect when regions were at the start of a line)","package":"vim-multiedit.tar.gz","4":"vim-multiedit.tar.gz","src_id":"19705","5":"19705","creation_date":"1364285985","6":"1364285985"},{"0":"4467","vim_version":"7.0","1":"7.0","script_version":"2.0.0","2":"2.0.0","version_comment":"2013-03-25 [2.0.0]\r\n- New: jump between regions with ]m and [m\r\n- Changed: disposable marker will be automatically deleted when entering\r\n  insert mode\r\n- Changed: :MultieditAppendMark and :MultieditPrependMark are merged into\r\n  :MultieditAddMark [ia]\r\n- Changed: the default highlight color for MultieditRegion is now linked to\r\n   Search' hl group\r\n- Changed: in visual mode, <leader>mm is not <leader>m (it is still <leader>mm\r\n  in normal mode)\r\n- Removed: <leader>ms (sets the region under the cursor to the new\r\n  'main' region). <leader>mm and <leader>m will do so implicitly if\r\n  a pre-existing region is detected under the cursor\r\n- Removed: <leader>mn and <leader>mp - however, instructions on how to\r\n  restore this functionality can be found in |multiedit-settings|\r\n- Fixed: cursor position after editing\r\n- Fixed: old regions weren't saved and couldn't be restored (would throw an\r\n  error)\r\n- Fixed: when deleting the main region, the (automatically) assigned new main\r\n  region wasn't chosen based on the order in which they were set\r\n- Fixed: errors caused by overlap detection when deleting regions\r\n- General code clean up and refactoring across the board","3":"2013-03-25 [2.0.0]\r\n- New: jump between regions with ]m and [m\r\n- Changed: disposable marker will be automatically deleted when entering\r\n  insert mode\r\n- Changed: :MultieditAppendMark and :MultieditPrependMark are merged into\r\n  :MultieditAddMark [ia]\r\n- Changed: the default highlight color for MultieditRegion is now linked to\r\n   Search' hl group\r\n- Changed: in visual mode, <leader>mm is not <leader>m (it is still <leader>mm\r\n  in normal mode)\r\n- Removed: <leader>ms (sets the region under the cursor to the new\r\n  'main' region). <leader>mm and <leader>m will do so implicitly if\r\n  a pre-existing region is detected under the cursor\r\n- Removed: <leader>mn and <leader>mp - however, instructions on how to\r\n  restore this functionality can be found in |multiedit-settings|\r\n- Fixed: cursor position after editing\r\n- Fixed: old regions weren't saved and couldn't be restored (would throw an\r\n  error)\r\n- Fixed: when deleting the main region, the (automatically) assigned new main\r\n  region wasn't chosen based on the order in which they were set\r\n- Fixed: errors caused by overlap detection when deleting regions\r\n- General code clean up and refactoring across the board","package":"vim-multiedit.tar.gz","4":"vim-multiedit.tar.gz","src_id":"19699","5":"19699","creation_date":"1364202715","6":"1364202715"},{"0":"4467","vim_version":"7.0","1":"7.0","script_version":"1.1.3","2":"1.1.3","version_comment":"- Add :MultieditRestore to restore previous regions (if available). Use with \r\n  <leader>mu\r\n- Add g:multiedit_auto_restore to control :MultieditRestore being called when\r\n  edit mode is initiated without regions specified.","3":"- Add :MultieditRestore to restore previous regions (if available). Use with \r\n  <leader>mu\r\n- Add g:multiedit_auto_restore to control :MultieditRestore being called when\r\n  edit mode is initiated without regions specified.","package":"vim-multiedit.tar.gz","4":"vim-multiedit.tar.gz","src_id":"19629","5":"19629","creation_date":"1362999237","6":"1362999237"},{"0":"4467","vim_version":"7.0","1":"7.0","script_version":"1.1.2","2":"1.1.2","version_comment":"- Change :Multiedit! functionality to delete word before editing (like\r\n  [c]hange command). Use <leader>C to initiate this mode.\r\n- Remove <leader>mw - now <leader>mm does it's job (viw:MultieditAddRegion<CR>)","3":"- Change :Multiedit! functionality to delete word before editing (like\r\n  [c]hange command). Use <leader>C to initiate this mode.\r\n- Remove <leader>mw - now <leader>mm does it's job (viw:MultieditAddRegion<CR>)","package":"vim-multiedit.tar.gz","4":"vim-multiedit.tar.gz","src_id":"19628","5":"19628","creation_date":"1362996892","6":"1362996892"},{"0":"4467","vim_version":"7.0","1":"7.0","script_version":"1.1.1","2":"1.1.1","version_comment":"- Add :Multiedit! - will move insert caret to the start of the word, instead\r\n  of the end. Kep map for this is <leader>I\r\n- Fix automatically adding next\/prev occurrence when using :MultieditNextMatch\r\n  and :MultieditPreviousMatch","3":"- Add :Multiedit! - will move insert caret to the start of the word, instead\r\n  of the end. Kep map for this is <leader>I\r\n- Fix automatically adding next\/prev occurrence when using :MultieditNextMatch\r\n  and :MultieditPreviousMatch","package":"vim-multiedit.tar.gz","4":"vim-multiedit.tar.gz","src_id":"19625","5":"19625","creation_date":"1362981377","6":"1362981377"},{"0":"4467","vim_version":"7.0","1":"7.0","script_version":"1.1.0","2":"1.1.0","version_comment":"2013-03-10 [1.1.0]\r\n- Fix :MultieditClear \"Key not present\" bug\r\n- Fix bug with editing consecutive regions on the same line\r\n- Fix region reordering issue caused by clearing individual regions\r\n- Refactor multiedit#update() completely\r\n- Add :MultieditSet and <leader>ms - allowing you to change the \"editable\"\r\nregion","3":"2013-03-10 [1.1.0]\r\n- Fix :MultieditClear \"Key not present\" bug\r\n- Fix bug with editing consecutive regions on the same line\r\n- Fix region reordering issue caused by clearing individual regions\r\n- Refactor multiedit#update() completely\r\n- Add :MultieditSet and <leader>ms - allowing you to change the \"editable\"\r\nregion","package":"vim-multiedit.tar.gz","4":"vim-multiedit.tar.gz","src_id":"19618","5":"19618","creation_date":"1362930522","6":"1362930522"},{"0":"4467","vim_version":"7.0","1":"7.0","script_version":"1.0.1","2":"1.0.1","version_comment":"Changed default highlight color for the first region","3":"Changed default highlight color for the first region","package":"vim-multiedit.tar.gz","4":"vim-multiedit.tar.gz","src_id":"19610","5":"19610","creation_date":"1362799639","6":"1362799639"},{"0":"4467","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"vim-multiedit.tar.gz","4":"vim-multiedit.tar.gz","src_id":"19609","5":"19609","creation_date":"1362798921","6":"1362798921"}]},"4466":{"script_id":"4466","0":"4466","script_name":"vim-transmitty","1":"vim-transmitty","script_type":"utility","2":"utility","summary":"Transmit.app integration for VIM (Mac only)","3":"Transmit.app integration for VIM (Mac only)","description":"A simple vim plugin that sends the current file to Transmit to be uploaded, using its \"dropsend\" feature. The plugin also does a shallow search for compiled files. For example, if you're working on a SCSS, LESS or Stylus stylesheet, it will look for the compiled CSS file and upload that instead.\r\n\r\n\r\nKEY MAPS\r\n\r\n    <leader>ou        \" Send file to Transmit\r\n    <leader>oU       \" Send file to Transmit (but don't look for compiled files)","4":"A simple vim plugin that sends the current file to Transmit to be uploaded, using its \"dropsend\" feature. The plugin also does a shallow search for compiled files. For example, if you're working on a SCSS, LESS or Stylus stylesheet, it will look for the compiled CSS file and upload that instead.\r\n\r\n\r\nKEY MAPS\r\n\r\n    <leader>ou        \" Send file to Transmit\r\n    <leader>oU       \" Send file to Transmit (but don't look for compiled files)","install_details":"Unzip the tarball, and put the files into their respective ~\/.vim\/* folders. Alternatively, I'd recommend Vundle (https:\/\/github.com\/gmarik\/vundle), then all you'd need is: \r\n\r\n    Bundle \"hlissner\/vim-transmitty\"\r\n\r\nThen restart and run:\r\n\r\n    :BundleInstall\r\n\r\n---------------------\r\nGITHUB: https:\/\/github.com\/hlissner\/vim-transmitty","5":"Unzip the tarball, and put the files into their respective ~\/.vim\/* folders. Alternatively, I'd recommend Vundle (https:\/\/github.com\/gmarik\/vundle), then all you'd need is: \r\n\r\n    Bundle \"hlissner\/vim-transmitty\"\r\n\r\nThen restart and run:\r\n\r\n    :BundleInstall\r\n\r\n---------------------\r\nGITHUB: https:\/\/github.com\/hlissner\/vim-transmitty","first_name":"Henrik","6":"Henrik","last_name":"Lissner","7":"Lissner","releases":[{"0":"4466","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"vim-transmitty.tar.gz","4":"vim-transmitty.tar.gz","src_id":"19608","5":"19608","creation_date":"1362791965","6":"1362791965"}]},"4465":{"script_id":"4465","0":"4465","script_name":"LineJugglerCommands","1":"LineJugglerCommands","script_type":"utility","2":"utility","summary":"Commands to duplicate and move around lines.","3":"Commands to duplicate and move around lines.","description":"DESCRIPTION\r\nMost of the line manipulation mappings of the LineJuggler.vim plugin can\r\nalso be done with built-in Ex commands like :move, :put, etc. This plugin\r\nadds those commands that do not exist (in a simple form) as built-in commands.\r\nSometimes, a command is just more practical (e.g. in a script), more\r\nrepeatable (from the command-line history), or offers different line\r\naddressing.\r\nNamely, this plugin provides a :BlankLine command, a :Swap command to\r\nexchange two ranges of lines (or with a register), and a similar :Replace\r\ncommand.\r\n\r\nSOURCE\r\nInspired by the following Stack Overflow question:\r\n    http:\/\/stackoverflow.com\/questions\/15296393\/line-swapping-in-vim\/15298132\r\n\r\nSEE ALSO\r\n- This plugin is based on the functionality of the (required) LineJugger.vim\r\n  plugin (vimscript #4140), which offers many mappings to quickly duplicate\r\n  and move lines to above \/ below the current line.\r\n- ReplaceWithRegister.vim (vimscript #2703) provides normal and visual mode\r\n  gr commands that are similar to the :Replace Ex command.\r\n\r\nUSAGE\r\n:[range]BlankLine [N]   Add [N] blank line(s) below the current line \/ last\r\n                        line in [range].\r\n\r\n:[range]Swap {range}    Exchange the current line \/ line(s) given by [range]\r\n                        with the lines in {range}.\r\n:[range]Swap [[\"]x]     Exchange the current line \/ line(s) given by [range]\r\n                        with the text from register [x]. This always works\r\n                        linewise, like a combination of :delete [x] and\r\n                        :put.\r\n\r\n:[range]Replace {range} Replace the current line \/ line(s) given by [range]\r\n                        with the lines in {range}.\r\n:[range]Replace [[\"]x]\r\n                        Replace the current line \/ line(s) given by [range]\r\n                        with the text from register [x]. This always works\r\n                        linewise, like a combination of :delete and\r\n                        :put.\r\n\r\n                        Note: To use one of the numbered registers 1-9, you\r\n                        need to prepend the optional double quotes (\"1 - \"9),\r\n                        in order to disambiguate them from the absolute lines\r\n                        1 - 9.","4":"DESCRIPTION\r\nMost of the line manipulation mappings of the LineJuggler.vim plugin can\r\nalso be done with built-in Ex commands like :move, :put, etc. This plugin\r\nadds those commands that do not exist (in a simple form) as built-in commands.\r\nSometimes, a command is just more practical (e.g. in a script), more\r\nrepeatable (from the command-line history), or offers different line\r\naddressing.\r\nNamely, this plugin provides a :BlankLine command, a :Swap command to\r\nexchange two ranges of lines (or with a register), and a similar :Replace\r\ncommand.\r\n\r\nSOURCE\r\nInspired by the following Stack Overflow question:\r\n    http:\/\/stackoverflow.com\/questions\/15296393\/line-swapping-in-vim\/15298132\r\n\r\nSEE ALSO\r\n- This plugin is based on the functionality of the (required) LineJugger.vim\r\n  plugin (vimscript #4140), which offers many mappings to quickly duplicate\r\n  and move lines to above \/ below the current line.\r\n- ReplaceWithRegister.vim (vimscript #2703) provides normal and visual mode\r\n  gr commands that are similar to the :Replace Ex command.\r\n\r\nUSAGE\r\n:[range]BlankLine [N]   Add [N] blank line(s) below the current line \/ last\r\n                        line in [range].\r\n\r\n:[range]Swap {range}    Exchange the current line \/ line(s) given by [range]\r\n                        with the lines in {range}.\r\n:[range]Swap [[\"]x]     Exchange the current line \/ line(s) given by [range]\r\n                        with the text from register [x]. This always works\r\n                        linewise, like a combination of :delete [x] and\r\n                        :put.\r\n\r\n:[range]Replace {range} Replace the current line \/ line(s) given by [range]\r\n                        with the lines in {range}.\r\n:[range]Replace [[\"]x]\r\n                        Replace the current line \/ line(s) given by [range]\r\n                        with the text from register [x]. This always works\r\n                        linewise, like a combination of :delete and\r\n                        :put.\r\n\r\n                        Note: To use one of the numbered registers 1-9, you\r\n                        need to prepend the optional double quotes (\"1 - \"9),\r\n                        in order to disambiguate them from the absolute lines\r\n                        1 - 9.","install_details":"INSTALLATION\r\nThe code is hosted in a Git repo at\r\n    https:\/\/github.com\/inkarkat\/vim-LineJugglerCommands\r\nYou can use your favorite plugin manager, or \"git clone\" into a directory used\r\nfor Vim packages. Releases are on the \"stable\" branch, the latest unstable\r\ndevelopment snapshot on \"master\".\r\n\r\nThis script is also packaged as a vimball. If you have the \"gunzip\"\r\ndecompressor in your PATH, simply edit the *.vmb.gz package in Vim; otherwise,\r\ndecompress the archive first, e.g. using WinZip. Inside Vim, install by\r\nsourcing the vimball or via the :UseVimball command.\r\n    vim LineJugglerCommands*.vmb.gz\r\n    :so %\r\nTo uninstall, use the :RmVimball command.\r\n\r\nDEPENDENCIES\r\n- Requires Vim 7.0 or higher.\r\n- Requires the ingo-library.vim plugin (vimscript #4433), version 1.033 or\r\n  higher.\r\n- Requires the LineJuggler.vim plugin (vimscript #4140), version 2.11 or\r\n  higher.","5":"INSTALLATION\r\nThe code is hosted in a Git repo at\r\n    https:\/\/github.com\/inkarkat\/vim-LineJugglerCommands\r\nYou can use your favorite plugin manager, or \"git clone\" into a directory used\r\nfor Vim packages. Releases are on the \"stable\" branch, the latest unstable\r\ndevelopment snapshot on \"master\".\r\n\r\nThis script is also packaged as a vimball. If you have the \"gunzip\"\r\ndecompressor in your PATH, simply edit the *.vmb.gz package in Vim; otherwise,\r\ndecompress the archive first, e.g. using WinZip. Inside Vim, install by\r\nsourcing the vimball or via the :UseVimball command.\r\n    vim LineJugglerCommands*.vmb.gz\r\n    :so %\r\nTo uninstall, use the :RmVimball command.\r\n\r\nDEPENDENCIES\r\n- Requires Vim 7.0 or higher.\r\n- Requires the ingo-library.vim plugin (vimscript #4433), version 1.033 or\r\n  higher.\r\n- Requires the LineJuggler.vim plugin (vimscript #4140), version 2.11 or\r\n  higher.","first_name":"Ingo","6":"Ingo","last_name":"Karkat","7":"Karkat","releases":[{"0":"4465","vim_version":"7.0","1":"7.0","script_version":"1.21","2":"1.21","version_comment":"- Add :BlankLine command.\r\n- Move LineJuggler#FoldClosed() and LineJuggler#FoldClosedEnd() into ingo-library as ingo#range#NetStart() and ingo#range#NetEnd(). *** You need to update to ingo-library (vimscript #4433) version 1.033! *** *** You need to update to LineJuggler.vim (vimscript #4140) version 1.21! ***","3":"- Add :BlankLine command.\r\n- Move LineJuggler#FoldClosed() and LineJuggler#FoldClosedEnd() into ingo-library as ingo#range#NetStart() and ingo#range#NetEnd(). *** You need to update to ingo-library (vimscript #4433) version 1.033! *** *** You need to update to LineJuggler.vim (vimscript #4140) version 1.21! ***","package":"LineJugglerCommands-1.21.vmb.gz","4":"LineJugglerCommands-1.21.vmb.gz","src_id":"26262","5":"26262","creation_date":"1541373337","6":"1541373337"},{"0":"4465","vim_version":"7.0","1":"7.0","script_version":"1.20","2":"1.20","version_comment":"- ENH: Also allow to pass a [x] register to the :Replace command, and replace the range with its contents.\r\n- ENH: Also allow to pass a [x] register to the :Swap command, and put the range into the register and vice versa.","3":"- ENH: Also allow to pass a [x] register to the :Replace command, and replace the range with its contents.\r\n- ENH: Also allow to pass a [x] register to the :Swap command, and put the range into the register and vice versa.","package":"LineJugglerCommands-1.20.vmb.gz","4":"LineJugglerCommands-1.20.vmb.gz","src_id":"22057","5":"22057","creation_date":"1403203788","6":"1403203788"},{"0":"4465","vim_version":"7.0","1":"7.0","script_version":"1.10","2":"1.10","version_comment":"- Add :Replace command. *** You need to update to LineJuggler.vim (vimscript #4140) version 2.10! ***","3":"- Add :Replace command. *** You need to update to LineJuggler.vim (vimscript #4140) version 2.10! ***","package":"LineJugglerCommands-1.10.vmb.gz","4":"LineJugglerCommands-1.10.vmb.gz","src_id":"22019","5":"22019","creation_date":"1402487578","6":"1402487578"},{"0":"4465","vim_version":"7.0","1":"7.0","script_version":"1.00","2":"1.00","version_comment":"Initial upload","3":"Initial upload","package":"LineJugglerCommands-1.00.vmb.gz","4":"LineJugglerCommands-1.00.vmb.gz","src_id":"19607","5":"19607","creation_date":"1362775272","6":"1362775272"}]},"4464":{"script_id":"4464","0":"4464","script_name":"vim-tayra","1":"vim-tayra","script_type":"syntax","2":"syntax","summary":"Syntax highlighting for tayra scripts.","3":"Syntax highlighting for tayra scripts.","description":"Unzip in your .vim\/ directory.","4":"Unzip in your .vim\/ directory.","install_details":"","5":"","first_name":"Pratap","6":"Pratap","last_name":"Chakravarthy","7":"Chakravarthy","releases":[{"0":"4464","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"vim-tayra.tar.gz","4":"vim-tayra.tar.gz","src_id":"19595","5":"19595","creation_date":"1362490032","6":"1362490032"}]},"4463":{"script_id":"4463","0":"4463","script_name":"vim-easy-submode","1":"vim-easy-submode","script_type":"utility","2":"utility","summary":"using vim-submode easily","3":"using vim-submode easily","description":"*easysubmode* is a Vim plugin to provide Ex-commands for using vim-submode easily. \r\nvim-submode:\r\nhttps:\/\/github.com\/kana\/vim-submode\r\nhttps:\/\/github.com\/thinca\/vim-submode\/tree\/my-master\r\n\r\nLatest version:\r\nhttps:\/\/github.com\/boolfool\/vim-easy-submode","4":"*easysubmode* is a Vim plugin to provide Ex-commands for using vim-submode easily. \r\nvim-submode:\r\nhttps:\/\/github.com\/kana\/vim-submode\r\nhttps:\/\/github.com\/thinca\/vim-submode\/tree\/my-master\r\n\r\nLatest version:\r\nhttps:\/\/github.com\/boolfool\/vim-easy-submode","install_details":"","5":"","first_name":"bool","6":"bool","last_name":"fool","7":"fool","releases":[{"0":"4463","vim_version":"7.3","1":"7.3","script_version":"0.0.0","2":"0.0.0","version_comment":"Initial upload","3":"Initial upload","package":"vim-easy-submode-0.0.0.zip","4":"vim-easy-submode-0.0.0.zip","src_id":"19593","5":"19593","creation_date":"1362456345","6":"1362456345"}]},"4462":{"script_id":"4462","0":"4462","script_name":"ProportionalResize","1":"ProportionalResize","script_type":"utility","2":"utility","summary":"Adapt the window proportions after Vim is resized.","3":"Adapt the window proportions after Vim is resized.","description":"DESCRIPTION\r\nWhen Vim itself is resized, the rightmost and bottom windows receive or lose\r\nthe change in size; all other windows maintain their size as long as possible.\r\nWhat you usually want is that _all_ window heights and widths are adapted, so\r\nthat the proportions of the windows remain constant.\r\n\r\nThis plugin defines a :ProportionalResize command that wraps Ex commands\r\nlike\r\n    :set lines=40 columns=80\r\n    :simalt ~m\r\n    :Fullscreen\r\nand scales the window sizes to the new dimensions. It also records the window\r\nlayout during brief pauses and is then able to auto-adapt after spontaneous\r\nresizings through the mouse or window manager.\r\n\r\nSOURCE\r\nInspired by the following Stack Overflow question:\r\n    http:\/\/stackoverflow.com\/questions\/14649698\/how-to-resize-split-windows-in-vim-proportionally\r\n\r\nUSAGE\r\n:ProportionalResize {resize-cmd}\r\n                        Execute {resize-cmd} (e.g. :setlocal lines=40) and\r\n                        adapt the proportions of the current window layout to\r\n                        the new size. So if for example you have 3 windows\r\n                        split vertically 1:1:2, and a horizontal split 4:1,\r\n                        the proportions will be kept instead of the rightmost\r\n                        and bottom windows getting all the space increases.\r\n\r\n:NoProportionalResize {resize-cmd}\r\n                        Execute {resize-cmd} (e.g. :setlocal lines=40) without\r\n                        adapting the proportions of the current window layout.\r\n                        You can wrap commands which would confuse the plugin's\r\n                        algorithm (e.g. a rotate function that switches\r\n                        vertical with horizontal windows), so that it won't\r\n                        automatically adapt the window layout.","4":"DESCRIPTION\r\nWhen Vim itself is resized, the rightmost and bottom windows receive or lose\r\nthe change in size; all other windows maintain their size as long as possible.\r\nWhat you usually want is that _all_ window heights and widths are adapted, so\r\nthat the proportions of the windows remain constant.\r\n\r\nThis plugin defines a :ProportionalResize command that wraps Ex commands\r\nlike\r\n    :set lines=40 columns=80\r\n    :simalt ~m\r\n    :Fullscreen\r\nand scales the window sizes to the new dimensions. It also records the window\r\nlayout during brief pauses and is then able to auto-adapt after spontaneous\r\nresizings through the mouse or window manager.\r\n\r\nSOURCE\r\nInspired by the following Stack Overflow question:\r\n    http:\/\/stackoverflow.com\/questions\/14649698\/how-to-resize-split-windows-in-vim-proportionally\r\n\r\nUSAGE\r\n:ProportionalResize {resize-cmd}\r\n                        Execute {resize-cmd} (e.g. :setlocal lines=40) and\r\n                        adapt the proportions of the current window layout to\r\n                        the new size. So if for example you have 3 windows\r\n                        split vertically 1:1:2, and a horizontal split 4:1,\r\n                        the proportions will be kept instead of the rightmost\r\n                        and bottom windows getting all the space increases.\r\n\r\n:NoProportionalResize {resize-cmd}\r\n                        Execute {resize-cmd} (e.g. :setlocal lines=40) without\r\n                        adapting the proportions of the current window layout.\r\n                        You can wrap commands which would confuse the plugin's\r\n                        algorithm (e.g. a rotate function that switches\r\n                        vertical with horizontal windows), so that it won't\r\n                        automatically adapt the window layout.","install_details":"INSTALLATION\r\nThis script is packaged as a vimball. If you have the \"gunzip\" decompressor\r\nin your PATH, simply edit the *.vmb.gz package in Vim; otherwise, decompress\r\nthe archive first, e.g. using WinZip. Inside Vim, install by sourcing the\r\nvimball or via the :UseVimball command.\r\n    vim ProportionalResize*.vmb.gz\r\n    :so %\r\nTo uninstall, use the :RmVimball command.\r\n\r\nDEPENDENCIES\r\n- Requires Vim 7.3 or higher and the +float feature.\r\n- Requires the ingo-library.vim plugin (vimscript #4433), version 1.000 or\r\n  higher.\r\n\r\nCONFIGURATION\r\nFor a permanent configuration, put the following commands into your vimrc:\r\n\r\nThe plugin can also handle spontaneous resizings (i.e. when you simply use the\r\nmouse or your window manager's controls to resize the GVIM application \/ Vim\r\nterminal window). For that, it needs to record the original window\r\nproportions. By default, that is done whenever you pause operation\r\n(CursorHold). If you're too impatient, you can add additional events (but\r\nbalance that with the drag on performance), e.g. WinEnter:\r\n    let g:ProportionalResize_RecordEvents = 'CursorHold,CursorHoldI,WinEnter'\r\nIf you don't want this auto-adaptation at all, and only use the\r\n:ProportionalResize wrapper:\r\n    let g:ProportionalResize_RecordEvents = ''\r\n\r\nTo make the auto-adaptation react faster, the plugin decreases the\r\n'updatetime' option temporarily while Vim is being resized. To influence the\r\ndelay, modify:\r\n    let g:ProportionalResize_UpdateTime = 500\r\n\r\nINTEGRATION\r\nIf you have any plugins or mappings that alter the size of the Vim window\r\n(e.g. a :Fullscreen or :Maximize command) it's advisable to trigger it\r\nthrough the :ProportionalResize wrapper.","5":"INSTALLATION\r\nThis script is packaged as a vimball. If you have the \"gunzip\" decompressor\r\nin your PATH, simply edit the *.vmb.gz package in Vim; otherwise, decompress\r\nthe archive first, e.g. using WinZip. Inside Vim, install by sourcing the\r\nvimball or via the :UseVimball command.\r\n    vim ProportionalResize*.vmb.gz\r\n    :so %\r\nTo uninstall, use the :RmVimball command.\r\n\r\nDEPENDENCIES\r\n- Requires Vim 7.3 or higher and the +float feature.\r\n- Requires the ingo-library.vim plugin (vimscript #4433), version 1.000 or\r\n  higher.\r\n\r\nCONFIGURATION\r\nFor a permanent configuration, put the following commands into your vimrc:\r\n\r\nThe plugin can also handle spontaneous resizings (i.e. when you simply use the\r\nmouse or your window manager's controls to resize the GVIM application \/ Vim\r\nterminal window). For that, it needs to record the original window\r\nproportions. By default, that is done whenever you pause operation\r\n(CursorHold). If you're too impatient, you can add additional events (but\r\nbalance that with the drag on performance), e.g. WinEnter:\r\n    let g:ProportionalResize_RecordEvents = 'CursorHold,CursorHoldI,WinEnter'\r\nIf you don't want this auto-adaptation at all, and only use the\r\n:ProportionalResize wrapper:\r\n    let g:ProportionalResize_RecordEvents = ''\r\n\r\nTo make the auto-adaptation react faster, the plugin decreases the\r\n'updatetime' option temporarily while Vim is being resized. To influence the\r\ndelay, modify:\r\n    let g:ProportionalResize_UpdateTime = 500\r\n\r\nINTEGRATION\r\nIf you have any plugins or mappings that alter the size of the Vim window\r\n(e.g. a :Fullscreen or :Maximize command) it's advisable to trigger it\r\nthrough the :ProportionalResize wrapper.","first_name":"Ingo","6":"Ingo","last_name":"Karkat","7":"Karkat","releases":[{"0":"4462","vim_version":"7.0","1":"7.0","script_version":"1.01","2":"1.01","version_comment":"- Add :NoProportionalResize command.\r\n- BUG: Always restore the original 'updatetime' option value after the resize. Otherwise, the lower value may persist, e.g. when the \"Stale window dimensions record\" error is given.","3":"- Add :NoProportionalResize command.\r\n- BUG: Always restore the original 'updatetime' option value after the resize. Otherwise, the lower value may persist, e.g. when the \"Stale window dimensions record\" error is given.","package":"ProportionalResize-1.01.vmb.gz","4":"ProportionalResize-1.01.vmb.gz","src_id":"21928","5":"21928","creation_date":"1400848104","6":"1400848104"},{"0":"4462","vim_version":"7.0","1":"7.0","script_version":"1.00","2":"1.00","version_comment":"Initial upload","3":"Initial upload","package":"ProportionalResize-1.00.vmb.gz","4":"ProportionalResize-1.00.vmb.gz","src_id":"19591","5":"19591","creation_date":"1362415549","6":"1362415549"}]},"4461":{"script_id":"4461","0":"4461","script_name":"RelativeNumberCurrentWindow","1":"RelativeNumberCurrentWindow","script_type":"utility","2":"utility","summary":"Only show relative numbers in the currently active window.","3":"Only show relative numbers in the currently active window.","description":"DESCRIPTION\r\nThe 'relativenumber' setting helps you use the [count] for even quicker\r\nnavigation and manipulation, but it's only useful in the current window, where\r\nthe cursor is. For all other windows, the absolute line numbers offer a better\r\norientation (e.g. when you have the same buffer in splits above and below your\r\ncurrent window, and you need to decide which contains a location you want to\r\ngo to).\r\n\r\nThis plugin sets up autocmds to show relative numbers only in the current\r\nwindow, and switches them to absolute numbers when the window is left. Windows\r\nthat do not have 'relativenumber' set are left as-is.\r\n\r\nSEE ALSO\r\n- The CursorLineCurrentWindow plugin (vimscript #4178) enables the\r\n  'cursorline' setting only for the current window.\r\n\r\nRELATED WORKS\r\n- RelOps (vimscript #4212) switches to relative numbering only when in\r\n  operator-pending mode.\r\n- vim-numbertoggle (http:\/\/jeffkreeftmeijer.com\/2012\/relative-line-numbers-in-vim-for-super-fast-movement\/)\r\n  turns off relative numbering in insert mode, or when the focus is lost.\r\n- numbers.vim (https:\/\/github.com\/myusuf3\/numbers.vim) will alternate between\r\n  relative numbering in normal mode and absolute in insert mode.\r\n\r\nUSAGE\r\nGlobally enable 'relativenumber' in your vimrc via\r\n    :set relativenumber\r\nAfter sourcing this plugin, 'relativenumber' will only be active for the\r\ncurrent window. So with multiple split windows, only one of them, the one\r\nwhere the cursor is in, will have the 'relativenumber'; all others will have\r\n'number' set.","4":"DESCRIPTION\r\nThe 'relativenumber' setting helps you use the [count] for even quicker\r\nnavigation and manipulation, but it's only useful in the current window, where\r\nthe cursor is. For all other windows, the absolute line numbers offer a better\r\norientation (e.g. when you have the same buffer in splits above and below your\r\ncurrent window, and you need to decide which contains a location you want to\r\ngo to).\r\n\r\nThis plugin sets up autocmds to show relative numbers only in the current\r\nwindow, and switches them to absolute numbers when the window is left. Windows\r\nthat do not have 'relativenumber' set are left as-is.\r\n\r\nSEE ALSO\r\n- The CursorLineCurrentWindow plugin (vimscript #4178) enables the\r\n  'cursorline' setting only for the current window.\r\n\r\nRELATED WORKS\r\n- RelOps (vimscript #4212) switches to relative numbering only when in\r\n  operator-pending mode.\r\n- vim-numbertoggle (http:\/\/jeffkreeftmeijer.com\/2012\/relative-line-numbers-in-vim-for-super-fast-movement\/)\r\n  turns off relative numbering in insert mode, or when the focus is lost.\r\n- numbers.vim (https:\/\/github.com\/myusuf3\/numbers.vim) will alternate between\r\n  relative numbering in normal mode and absolute in insert mode.\r\n\r\nUSAGE\r\nGlobally enable 'relativenumber' in your vimrc via\r\n    :set relativenumber\r\nAfter sourcing this plugin, 'relativenumber' will only be active for the\r\ncurrent window. So with multiple split windows, only one of them, the one\r\nwhere the cursor is in, will have the 'relativenumber'; all others will have\r\n'number' set.","install_details":"INSTALLATION\r\nThis script is packaged as a vimball. If you have the \"gunzip\" decompressor\r\nin your PATH, simply edit the *.vmb.gz package in Vim; otherwise, decompress\r\nthe archive first, e.g. using WinZip. Inside Vim, install by sourcing the\r\nvimball or via the :UseVimball command.\r\n    vim RelativeNumberCurrentWindow*.vmb.gz\r\n    :so %\r\nTo uninstall, use the :RmVimball command.\r\n\r\nDEPENDENCIES\r\n- Requires Vim 7.0 or higher.\r\n\r\nCONFIGURATION\r\nFor the relative numbers, the necessary space is determined by the window\r\nheight; for absolute numbers, it's the number of lines in the buffer. This\r\ndiscrepancy can lead to changes in the width of the number column when\r\nswitching from one setting to the other. Because this shifting of the buffer\r\ncontents is visually distracting, the plugin sets up an autocmd that presets\r\n'numberwidth' to a high-enough value so that this doesn't happen. If you don't\r\nwant this, set:\r\n    let g:RelativeNumberCurrentWindow_SameNumberWidth = 0\r\n\r\nThe relative numbers don't help when Vim isn't the active application, but\r\nabsolute numbers can be beneficial, because compiler or test output may refer\r\nto lines currently open in Vim. Therefore, relative numbers for the current\r\nwindow are switched to absolute when Vim loses the focus FocusLost. If you\r\ndon't want this, set:\r\n    let g:RelativeNumberCurrentWindow_OnFocus = 0\r\n\r\nLikewise, in insert mode, relative numbers are useless, as you rarely do\r\nmovements in that mode and cannot prepend a [count], anyway. Absolute numbers\r\nrequire less screen updates and provide better orientation, so relative\r\nnumbers are switched to absolute when in insert mode. To disable this, set:\r\n    let g:RelativeNumberCurrentWindow_OnInsert = 0","5":"INSTALLATION\r\nThis script is packaged as a vimball. If you have the \"gunzip\" decompressor\r\nin your PATH, simply edit the *.vmb.gz package in Vim; otherwise, decompress\r\nthe archive first, e.g. using WinZip. Inside Vim, install by sourcing the\r\nvimball or via the :UseVimball command.\r\n    vim RelativeNumberCurrentWindow*.vmb.gz\r\n    :so %\r\nTo uninstall, use the :RmVimball command.\r\n\r\nDEPENDENCIES\r\n- Requires Vim 7.0 or higher.\r\n\r\nCONFIGURATION\r\nFor the relative numbers, the necessary space is determined by the window\r\nheight; for absolute numbers, it's the number of lines in the buffer. This\r\ndiscrepancy can lead to changes in the width of the number column when\r\nswitching from one setting to the other. Because this shifting of the buffer\r\ncontents is visually distracting, the plugin sets up an autocmd that presets\r\n'numberwidth' to a high-enough value so that this doesn't happen. If you don't\r\nwant this, set:\r\n    let g:RelativeNumberCurrentWindow_SameNumberWidth = 0\r\n\r\nThe relative numbers don't help when Vim isn't the active application, but\r\nabsolute numbers can be beneficial, because compiler or test output may refer\r\nto lines currently open in Vim. Therefore, relative numbers for the current\r\nwindow are switched to absolute when Vim loses the focus FocusLost. If you\r\ndon't want this, set:\r\n    let g:RelativeNumberCurrentWindow_OnFocus = 0\r\n\r\nLikewise, in insert mode, relative numbers are useless, as you rarely do\r\nmovements in that mode and cannot prepend a [count], anyway. Absolute numbers\r\nrequire less screen updates and provide better orientation, so relative\r\nnumbers are switched to absolute when in insert mode. To disable this, set:\r\n    let g:RelativeNumberCurrentWindow_OnInsert = 0","first_name":"Ingo","6":"Ingo","last_name":"Karkat","7":"Karkat","releases":[{"0":"4461","vim_version":"7.0","1":"7.0","script_version":"1.10","2":"1.10","version_comment":"- Plugin was broken by Vim 7.3.861, which fixed the resetting of 'rnu' when 'nu' is set. Add implementation that omits the workaround.\r\n- Handle combination of 'nu' and 'rnu' that results in different current line display since 7.3.1115.","3":"- Plugin was broken by Vim 7.3.861, which fixed the resetting of 'rnu' when 'nu' is set. Add implementation that omits the workaround.\r\n- Handle combination of 'nu' and 'rnu' that results in different current line display since 7.3.1115.","package":"RelativeNumberCurrentWindow-1.10.vmb.gz","4":"RelativeNumberCurrentWindow-1.10.vmb.gz","src_id":"22899","5":"22899","creation_date":"1423481576","6":"1423481576"},{"0":"4461","vim_version":"7.0","1":"7.0","script_version":"1.00","2":"1.00","version_comment":"Initial upload","3":"Initial upload","package":"RelativeNumberCurrentWindow-1.00.vmb.gz","4":"RelativeNumberCurrentWindow-1.00.vmb.gz","src_id":"19590","5":"19590","creation_date":"1362415453","6":"1362415453"}]},"4459":{"script_id":"4459","0":"4459","script_name":"neosnippet","1":"neosnippet","script_type":"utility","2":"utility","summary":"The neo-snippet plugin contains the neocomplcache snippet completion","3":"The neo-snippet plugin contains the neocomplcache snippet completion","description":"Neosnippet\r\n==========\r\n\r\nThe Neosnippet plug-In adds snippet support to Vim. Snippets are\r\nsmall templates for commonly used code that you can fill in on the\r\nfly. To use snippets can increase your productivity in Vim a lot.\r\nThe functionality of this plug-in is quite similar to plug-ins like\r\nsnipMate.vim or snippetsEmu.vim. But since you can choose snippets with the\r\n[Neocomplecache](https:\/\/github.com\/Shougo\/neocomplcache) interface, you might\r\nhave less trouble using them, because you do not have to remember each snippet\r\nname.\r\n\r\nNote: neocomplecache is NOT required! But recommended.\r\n\r\nConfiguration\r\n-------------\r\n\r\nThis is an example `~\/.vimrc` configuration for Neosnippet. It is assumes you\r\nalready have Neocomplecache configured. With the settings of the example, you\r\ncan use the following keys:\r\n\r\n* `C-k` to select-and-expand a snippet from the Neocomplecache popup (Use `C-n`\r\n  and `C-p` to select it). `C-k` can also be used to jump to the next field in\r\n  the snippet.\r\n* `Tab` to select the next field to fill in the snippet.\r\n\r\n\" Plugin key-mappings.\r\nimap <C-k>     <Plug>(neosnippet_expand_or_jump)\r\nsmap <C-k>     <Plug>(neosnippet_expand_or_jump)\r\n\r\n\" SuperTab like snippets behavior.\r\nimap <expr><TAB> neosnippet#expandable_or_jumpable() ? \"\\<Plug>(neosnippet_expand_or_jump)\" : pumvisible() ? \"\\<C-n>\" : \"\\<TAB>\"\r\nsmap <expr><TAB> neosnippet#expandable_or_jumpable() ? \"\\<Plug>(neosnippet_expand_or_jump)\" : \"\\<TAB>\"\r\n\r\n\" For snippet_complete marker.\r\nif has('conceal')\r\n  set conceallevel=2 concealcursor=i\r\nendif\r\n\r\nIf you want to use a different collection of snippets than the\r\nbuilt-in ones, then you can set a path to the snippets with\r\nthe `g:neosnippet#snippets_directory` variable (e.g [Honza's\r\nSnippets](https:\/\/github.com\/honza\/snipmate-snippets))\r\n\r\n\" Tell Neosnippet about the other snippets\r\nlet g:neosnippet#snippets_directory='~\/.vim\/bundle\/snipmate-snippets\/snippets'\r\n","4":"Neosnippet\r\n==========\r\n\r\nThe Neosnippet plug-In adds snippet support to Vim. Snippets are\r\nsmall templates for commonly used code that you can fill in on the\r\nfly. To use snippets can increase your productivity in Vim a lot.\r\nThe functionality of this plug-in is quite similar to plug-ins like\r\nsnipMate.vim or snippetsEmu.vim. But since you can choose snippets with the\r\n[Neocomplecache](https:\/\/github.com\/Shougo\/neocomplcache) interface, you might\r\nhave less trouble using them, because you do not have to remember each snippet\r\nname.\r\n\r\nNote: neocomplecache is NOT required! But recommended.\r\n\r\nConfiguration\r\n-------------\r\n\r\nThis is an example `~\/.vimrc` configuration for Neosnippet. It is assumes you\r\nalready have Neocomplecache configured. With the settings of the example, you\r\ncan use the following keys:\r\n\r\n* `C-k` to select-and-expand a snippet from the Neocomplecache popup (Use `C-n`\r\n  and `C-p` to select it). `C-k` can also be used to jump to the next field in\r\n  the snippet.\r\n* `Tab` to select the next field to fill in the snippet.\r\n\r\n\" Plugin key-mappings.\r\nimap <C-k>     <Plug>(neosnippet_expand_or_jump)\r\nsmap <C-k>     <Plug>(neosnippet_expand_or_jump)\r\n\r\n\" SuperTab like snippets behavior.\r\nimap <expr><TAB> neosnippet#expandable_or_jumpable() ? \"\\<Plug>(neosnippet_expand_or_jump)\" : pumvisible() ? \"\\<C-n>\" : \"\\<TAB>\"\r\nsmap <expr><TAB> neosnippet#expandable_or_jumpable() ? \"\\<Plug>(neosnippet_expand_or_jump)\" : \"\\<TAB>\"\r\n\r\n\" For snippet_complete marker.\r\nif has('conceal')\r\n  set conceallevel=2 concealcursor=i\r\nendif\r\n\r\nIf you want to use a different collection of snippets than the\r\nbuilt-in ones, then you can set a path to the snippets with\r\nthe `g:neosnippet#snippets_directory` variable (e.g [Honza's\r\nSnippets](https:\/\/github.com\/honza\/snipmate-snippets))\r\n\r\n\" Tell Neosnippet about the other snippets\r\nlet g:neosnippet#snippets_directory='~\/.vim\/bundle\/snipmate-snippets\/snippets'\r\n","install_details":"To install neosnippet and other Vim plug-ins it is recommended to use one of the\r\npopular package managers for Vim, rather than installing by drag and drop all\r\nrequired files into your `.vim` folder.\r\n\r\n### Manual (not recommended)\r\n\r\n1. Install the [Neocomplecache](https:\/\/github.com\/Shougo\/neocomplcache) plugin first.\r\n2. Put files in your Vim directory (usually `~\/.vim\/` or\r\n   `%PROGRAMFILES%\/Vim\/vimfiles` on Windows).\r\n\r\n### Vundle \r\n\r\n1. Setup the [vundle](https:\/\/github.com\/gmarik\/vundle) package manager \r\n2. Set the bundles for [Neocomplecache](https:\/\/github.com\/Shougo\/neocomplcache) and [Neobundle](https:\/\/github.com\/Shougo\/neosnippet) \r\n\r\n```\r\nBundle 'Shougo\/neocomplcache.git'\r\nBundle 'Shougo\/neosnippet.git'\r\n```\r\n\r\n3. Open up Vim and start installation with `:BundleInstall`\r\n\r\n### Neobundle \r\n\r\n1. Setup the [neobundle](https:\/\/github.com\/Shougo\/neobundle.vim) package manager \r\n2. Set the bundles for [Neocomplecache](https:\/\/github.com\/Shougo\/neocomplcache) and [Neobundle](https:\/\/github.com\/Shougo\/neosnippet) \r\n\r\n```\r\nNeoBundle 'Shougo\/neocomplcache.git'\r\nNeoBundle 'Shougo\/neosnippet.git'\r\n```\r\n\r\n3. Open up Vim and start installation with `:NeoBundleInstall`","5":"To install neosnippet and other Vim plug-ins it is recommended to use one of the\r\npopular package managers for Vim, rather than installing by drag and drop all\r\nrequired files into your `.vim` folder.\r\n\r\n### Manual (not recommended)\r\n\r\n1. Install the [Neocomplecache](https:\/\/github.com\/Shougo\/neocomplcache) plugin first.\r\n2. Put files in your Vim directory (usually `~\/.vim\/` or\r\n   `%PROGRAMFILES%\/Vim\/vimfiles` on Windows).\r\n\r\n### Vundle \r\n\r\n1. Setup the [vundle](https:\/\/github.com\/gmarik\/vundle) package manager \r\n2. Set the bundles for [Neocomplecache](https:\/\/github.com\/Shougo\/neocomplcache) and [Neobundle](https:\/\/github.com\/Shougo\/neosnippet) \r\n\r\n```\r\nBundle 'Shougo\/neocomplcache.git'\r\nBundle 'Shougo\/neosnippet.git'\r\n```\r\n\r\n3. Open up Vim and start installation with `:BundleInstall`\r\n\r\n### Neobundle \r\n\r\n1. Setup the [neobundle](https:\/\/github.com\/Shougo\/neobundle.vim) package manager \r\n2. Set the bundles for [Neocomplecache](https:\/\/github.com\/Shougo\/neocomplcache) and [Neobundle](https:\/\/github.com\/Shougo\/neosnippet) \r\n\r\n```\r\nNeoBundle 'Shougo\/neocomplcache.git'\r\nNeoBundle 'Shougo\/neosnippet.git'\r\n```\r\n\r\n3. Open up Vim and start installation with `:NeoBundleInstall`","first_name":"Shougo","6":"Shougo","last_name":"Matsushita","7":"Matsushita","releases":[{"0":"4459","vim_version":"7.2","1":"7.2","script_version":"3.0","2":"3.0","version_comment":"Initial upload","3":"Initial upload","package":"neosnippet-3.0.zip","4":"neosnippet-3.0.zip","src_id":"19582","5":"19582","creation_date":"1362203163","6":"1362203163"}]},"4458":{"script_id":"4458","0":"4458","script_name":"textobj-gitgutter","1":"textobj-gitgutter","script_type":"utility","2":"utility","summary":"text object for a gitgutter hunk","3":"text object for a gitgutter hunk","description":"textobj-gitgutter is a plugin which provides an inner-hunk text object for hunks provided by the vim-gitgutter plugin. See the included vim help for further details. \r\n\r\nRequirements:\r\n- textobj-user (vimscript#2100)\r\n- vim-gitgutter (https:\/\/github.com\/airblade\/vim-gitgutter)\r\n\r\nCode is maintained at:\r\n- https:\/\/github.com\/gilligan\/textobj-gitgutter","4":"textobj-gitgutter is a plugin which provides an inner-hunk text object for hunks provided by the vim-gitgutter plugin. See the included vim help for further details. \r\n\r\nRequirements:\r\n- textobj-user (vimscript#2100)\r\n- vim-gitgutter (https:\/\/github.com\/airblade\/vim-gitgutter)\r\n\r\nCode is maintained at:\r\n- https:\/\/github.com\/gilligan\/textobj-gitgutter","install_details":"","5":"","first_name":"Tobias","6":"Tobias","last_name":"Pflug","7":"Pflug","releases":[{"0":"4458","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"textobj-gitgutter.zip","4":"textobj-gitgutter.zip","src_id":"19579","5":"19579","creation_date":"1362166820","6":"1362166820"}]},"4457":{"script_id":"4457","0":"4457","script_name":"convert_case.vim","1":"convert_case.vim","script_type":"utility","2":"utility","summary":"Convert Case ","3":"Convert Case ","description":"\r\nSome times when you migrate from Windows to Linux you encounter issues in include directive where compiler looking for some include files and it can not find because upper\/lower case in include file name. this utility lets you convert few selected lines by range into lower or upper case as needed by situation.\r\nUse it as command\r\n:1,$ Tu   => Convets whole file to upper case\r\n:1,$ Tl   => Convets whole file to lower case\r\nExample\r\n\" convert line 1 to 10  to upper case \r\n1,10Tu   \r\n\r\n\" convert line 1 to 10  to lower case \r\n1,10Tl   \r\n","4":"\r\nSome times when you migrate from Windows to Linux you encounter issues in include directive where compiler looking for some include files and it can not find because upper\/lower case in include file name. this utility lets you convert few selected lines by range into lower or upper case as needed by situation.\r\nUse it as command\r\n:1,$ Tu   => Convets whole file to upper case\r\n:1,$ Tl   => Convets whole file to lower case\r\nExample\r\n\" convert line 1 to 10  to upper case \r\n1,10Tu   \r\n\r\n\" convert line 1 to 10  to lower case \r\n1,10Tl   \r\n","install_details":"Just drop this script in Plugin directory","5":"Just drop this script in Plugin directory","first_name":"vijayandra","6":"vijayandra","last_name":"singh","7":"singh","releases":[{"0":"4457","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"convert_case.vim","4":"convert_case.vim","src_id":"19569","5":"19569","creation_date":"1361745968","6":"1361745968"}]},"4456":{"script_id":"4456","0":"4456","script_name":"vgdb","1":"vgdb","script_type":"utility","2":"utility","summary":"visual gdb in vim","3":"visual gdb in vim","description":"VGdb is a perl program that allows the use of vim as a front end to gdb. It\r\nboth works on MS Windows and Linux. It both works in gvim and vim.\r\n\r\nIt open a vgdb window in vim that allows user to type gdb command\r\ndirectly, and gdb output is redirected to this windows. \r\n\r\nMSVC-style shortcuts are defined by default, and MSVC autoexp.dat is partially supported.\r\n\r\nA flash demo (__VGDB_DEMO__.htm) in my package helps you quickly go through the\r\nvgdb features. ","4":"VGdb is a perl program that allows the use of vim as a front end to gdb. It\r\nboth works on MS Windows and Linux. It both works in gvim and vim.\r\n\r\nIt open a vgdb window in vim that allows user to type gdb command\r\ndirectly, and gdb output is redirected to this windows. \r\n\r\nMSVC-style shortcuts are defined by default, and MSVC autoexp.dat is partially supported.\r\n\r\nA flash demo (__VGDB_DEMO__.htm) in my package helps you quickly go through the\r\nvgdb features. ","install_details":"On MS Windows, you need install Perl.\r\nModify vgdb.bat for your path.\r\nModify vgdb_install_mswin.bat that actually copy files to your folder.\r\nRun vgdb_install_mswin.bat to copy files.\r\n\r\nOn Linux, modify path in script vgdb_install and run it. \r\n\r\nNote: \r\ngvim MUST in the default search path.","5":"On MS Windows, you need install Perl.\r\nModify vgdb.bat for your path.\r\nModify vgdb_install_mswin.bat that actually copy files to your folder.\r\nRun vgdb_install_mswin.bat to copy files.\r\n\r\nOn Linux, modify path in script vgdb_install and run it. \r\n\r\nNote: \r\ngvim MUST in the default search path.","first_name":"Jian","6":"Jian","last_name":"Liang","7":"Liang","releases":[{"0":"4456","vim_version":"7.0","1":"7.0","script_version":"1.2","2":"1.2","version_comment":"version 1.2","3":"version 1.2","package":"vgdb-1.2.tgz","4":"vgdb-1.2.tgz","src_id":"20803","5":"20803","creation_date":"1379175952","6":"1379175952"},{"0":"4456","vim_version":"7.0","1":"7.0","script_version":"1.1","2":"1.1","version_comment":"> enhancement for showing variable and tracing pointer.\r\n> cross function execution point jump\r\n> many bugfix.","3":"> enhancement for showing variable and tracing pointer.\r\n> cross function execution point jump\r\n> many bugfix.","package":"vgdb-1.1.zip","4":"vgdb-1.1.zip","src_id":"20037","5":"20037","creation_date":"1367900509","6":"1367900509"},{"0":"4456","vim_version":"7.0","1":"7.0","script_version":"1","2":"1","version_comment":"Initial upload","3":"Initial upload","package":"vgdb.zip","4":"vgdb.zip","src_id":"19566","5":"19566","creation_date":"1361694381","6":"1361694381"}]},"4455":{"script_id":"4455","0":"4455","script_name":"rbenv.vim","1":"rbenv.vim","script_type":"utility","2":"utility","summary":"Minimal rbenv support","3":"Minimal rbenv support","description":"This simple plugin provides a :Rbenv command that wraps !rbenv with tab complete.  It also tells recent versions of https:\/\/github.com\/vim-ruby\/vim-ruby where your Ruby installs are located, so that it can set 'path' and 'tags' in your Ruby buffers to reflect the nearest .ruby-version file.\r\n\r\nhttps:\/\/github.com\/tpope\/vim-rbenv","4":"This simple plugin provides a :Rbenv command that wraps !rbenv with tab complete.  It also tells recent versions of https:\/\/github.com\/vim-ruby\/vim-ruby where your Ruby installs are located, so that it can set 'path' and 'tags' in your Ruby buffers to reflect the nearest .ruby-version file.\r\n\r\nhttps:\/\/github.com\/tpope\/vim-rbenv","install_details":"Extract in ~\/.vim (~\\vimfiles on Windows).","5":"Extract in ~\/.vim (~\\vimfiles on Windows).","first_name":"Tim","6":"Tim","last_name":"Pope","7":"Pope","releases":[{"0":"4455","vim_version":"7.0","1":"7.0","script_version":"1.1","2":"1.1","version_comment":"Provide :Rbenv.","3":"Provide :Rbenv.","package":"rbenv.zip","4":"rbenv.zip","src_id":"19585","5":"19585","creation_date":"1362236586","6":"1362236586"},{"0":"4455","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"rbenv.zip","4":"rbenv.zip","src_id":"19565","5":"19565","creation_date":"1361679340","6":"1361679340"}]},"4454":{"script_id":"4454","0":"4454","script_name":"vim-vimlparser","1":"vim-vimlparser","script_type":"utility","2":"utility","summary":"VimL parser","3":"VimL parser","description":"Try :call vimlparser#test('foo.vim').  It parse the file and shows the result of test compiler.\r\n\r\nfoo.vim:\r\nif x == y\r\n  echo z\r\nendif\r\n\r\nresult:\r\n(if (== x y)\r\n  (echo z))","4":"Try :call vimlparser#test('foo.vim').  It parse the file and shows the result of test compiler.\r\n\r\nfoo.vim:\r\nif x == y\r\n  echo z\r\nendif\r\n\r\nresult:\r\n(if (== x y)\r\n  (echo z))","install_details":":set runtimepath+=\/path\/to\/vim-vimlparser\r\n\r\nlatest source: https:\/\/github.com\/ynkdir\/vim-vimlparser","5":":set runtimepath+=\/path\/to\/vim-vimlparser\r\n\r\nlatest source: https:\/\/github.com\/ynkdir\/vim-vimlparser","first_name":"Yukihiro","6":"Yukihiro","last_name":"Nakadaira","7":"Nakadaira","releases":[{"0":"4454","vim_version":"7.3","1":"7.3","script_version":"0.3","2":"0.3","version_comment":"bug fix.\r\nnode.js version.","3":"bug fix.\r\nnode.js version.","package":"vim-vimlparser.zip","4":"vim-vimlparser.zip","src_id":"19726","5":"19726","creation_date":"1364634716","6":"1364634716"},{"0":"4454","vim_version":"7.3","1":"7.3","script_version":"0.2","2":"0.2","version_comment":"bug fix.\r\npython version.","3":"bug fix.\r\npython version.","package":"vim-vimlparser.zip","4":"vim-vimlparser.zip","src_id":"19578","5":"19578","creation_date":"1362059355","6":"1362059355"},{"0":"4454","vim_version":"7.3","1":"7.3","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"vim-vimlparser.zip","4":"vim-vimlparser.zip","src_id":"19563","5":"19563","creation_date":"1361590001","6":"1361590001"}]},"4453":{"script_id":"4453","0":"4453","script_name":"play.vim","1":"play.vim","script_type":"ftplugin","2":"ftplugin","summary":"Play! framework plugin for Vim","3":"Play! framework plugin for Vim","description":"Package contains syntax and snipMate snippets for Play! framework 1.x routes and templates.\r\n\r\nFor additional information visit GitHub repository https:\/\/github.com\/rdolgushin\/play.vim.\r\n\r\nNOTE:\r\n\r\nVim 7.4 now has broken Groovy syntax highlighting and play.vim will not be working correctly with it.\r\nYou can use fixed version for groovy.vim from https:\/\/github.com\/rdolgushin\/groovy.vim","4":"Package contains syntax and snipMate snippets for Play! framework 1.x routes and templates.\r\n\r\nFor additional information visit GitHub repository https:\/\/github.com\/rdolgushin\/play.vim.\r\n\r\nNOTE:\r\n\r\nVim 7.4 now has broken Groovy syntax highlighting and play.vim will not be working correctly with it.\r\nYou can use fixed version for groovy.vim from https:\/\/github.com\/rdolgushin\/groovy.vim","install_details":"* Using pathogen (https:\/\/github.com\/tpope\/vim-pathogen) or vundle (https:\/\/github.com\/gmarik\/vundle) from https:\/\/github.com\/rdolgushin\/play.vim \r\n* Standard Vim way (http:\/\/vimdoc.sourceforge.net\/htmldoc\/usr_05.html#add-plugin)","5":"* Using pathogen (https:\/\/github.com\/tpope\/vim-pathogen) or vundle (https:\/\/github.com\/gmarik\/vundle) from https:\/\/github.com\/rdolgushin\/play.vim \r\n* Standard Vim way (http:\/\/vimdoc.sourceforge.net\/htmldoc\/usr_05.html#add-plugin)","first_name":"Roman","6":"Roman","last_name":"Dolgushin","7":"Dolgushin","releases":[{"0":"4453","vim_version":"7.0","1":"7.0","script_version":"0.9.2","2":"0.9.2","version_comment":"tComment integration comes lazy (to fix Vim splash screen displaying)","3":"tComment integration comes lazy (to fix Vim splash screen displaying)","package":"play.zip","4":"play.zip","src_id":"20619","5":"20619","creation_date":"1376093311","6":"1376093311"},{"0":"4453","vim_version":"7.0","1":"7.0","script_version":"0.9.1","2":"0.9.1","version_comment":"Initial upload","3":"Initial upload","package":"play.zip","4":"play.zip","src_id":"19560","5":"19560","creation_date":"1361508856","6":"1361508856"}]},"4452":{"script_id":"4452","0":"4452","script_name":"vim-javascript","1":"vim-javascript","script_type":"syntax","2":"syntax","summary":"New maintained version of vim-javascript","3":"New maintained version of vim-javascript","description":"This is the source of the newly maintained vim-javascript which was originally located at http:\/\/www.vim.org\/scripts\/script.php?script_id=2765\r\n\r\nThe source of truth is the GitHub repo https:\/\/github.com\/pangloss\/vim-javascript","4":"This is the source of the newly maintained vim-javascript which was originally located at http:\/\/www.vim.org\/scripts\/script.php?script_id=2765\r\n\r\nThe source of truth is the GitHub repo https:\/\/github.com\/pangloss\/vim-javascript","install_details":"Installs with Vundle or Pathogen. See README on GitHub","5":"Installs with Vundle or Pathogen. See README on GitHub","first_name":"Josh","6":"Josh","last_name":"Perez","7":"Perez","releases":[{"0":"4452","vim_version":"6.0","1":"6.0","script_version":"1.0.0","2":"1.0.0","version_comment":"Initial upload","3":"Initial upload","package":"vim-javascript.zip","4":"vim-javascript.zip","src_id":"19555","5":"19555","creation_date":"1361336067","6":"1361336067"}]},"4451":{"script_id":"4451","0":"4451","script_name":"pry","1":"pry","script_type":"ftplugin","2":"ftplugin","summary":"Pry\/Vim Integration","3":"Pry\/Vim Integration","description":"For the high-falutin' concept, see: https:\/\/github.com\/pry\/pry\/wiki\/pry-de\r\n\r\niabbr bpry => require 'pry'; binding.pry # Very important for quickly dropping into pry\r\n\r\n<leader>bp and <leader><leader>p # same as bpry but from Normal Mode\r\n\r\n<f3> = kill-pry-rescue # see https:\/\/github.com\/ConradIrwin\/pry-rescue - this breaks you out of the auto-rescue'd pry\r\n\r\n<leader>ph = Grab the last line (or lines if given a numerical arg) from ~\/.pry_history - can be very handy, because you can perfect your code in the live coding environment of the Pry REPL, then slurp that into your editor.\r\n\r\nNote that there are ways to integrate back into the REPL from the editor. vslime and vimux do this, as long as you're in tmux. However, I currently just do \"!tmux send -t1\" in a manual :map from vim. This script might eventually include something like this. Please let me know if you already know what you want.","4":"For the high-falutin' concept, see: https:\/\/github.com\/pry\/pry\/wiki\/pry-de\r\n\r\niabbr bpry => require 'pry'; binding.pry # Very important for quickly dropping into pry\r\n\r\n<leader>bp and <leader><leader>p # same as bpry but from Normal Mode\r\n\r\n<f3> = kill-pry-rescue # see https:\/\/github.com\/ConradIrwin\/pry-rescue - this breaks you out of the auto-rescue'd pry\r\n\r\n<leader>ph = Grab the last line (or lines if given a numerical arg) from ~\/.pry_history - can be very handy, because you can perfect your code in the live coding environment of the Pry REPL, then slurp that into your editor.\r\n\r\nNote that there are ways to integrate back into the REPL from the editor. vslime and vimux do this, as long as you're in tmux. However, I currently just do \"!tmux send -t1\" in a manual :map from vim. This script might eventually include something like this. Please let me know if you already know what you want.","install_details":"Just put ruby_pry.vim in ~\/.vim\/ftplugin\/\r\n\r\nOr you could use Pathogen, installing to ~\/.vim\/bundle\/pry\/\r\n\r\n","5":"Just put ruby_pry.vim in ~\/.vim\/ftplugin\/\r\n\r\nOr you could use Pathogen, installing to ~\/.vim\/bundle\/pry\/\r\n\r\n","first_name":"Ryan","6":"Ryan","last_name":"King","7":"King","releases":[{"0":"4451","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"ruby_pry.vim","4":"ruby_pry.vim","src_id":"19553","5":"19553","creation_date":"1361286293","6":"1361286293"}]},"4450":{"script_id":"4450","0":"4450","script_name":"ag.vim","1":"ag.vim","script_type":"utility","2":"utility","summary":"Use ag, the_silver_searcher (better than ack, which is better than grep)","3":"Use ag, the_silver_searcher (better than ack, which is better than grep)","description":"Just like ack.vim but for the faster 'ag' utility.\r\n\r\nFor better formatting, see: https:\/\/github.com\/rking\/ag.vim#readme\r\n\r\nThis plugin is a front for ag, A.K.A. the_silver_searcher. Ag can be used as a replacement for 153% of the uses of ack. This plugin will allow you to run ag from vim, and shows the results in a split window.\r\nInstallation \r\n\r\n\r\nThe Silver Searcher\r\n\r\nYou have to install ag, of course.\r\n\r\nUsually it's a package named 'the_silver_searcher', but it should install easily from Github, otherwise:\r\n\r\ngit clone https:\/\/github.com\/ggreer\/the_silver_searcher\r\ncd the_silver_searcher && .\/build.sh && install\r\n\r\nThen, if you're using pathogen:\r\n\r\ncd ~\/.vim\/bundle && git clone https:\/\/github.com\/rking\/ag.vim\r\n# And run :Helptags from within vim\r\n\r\nIf you're using something else (whether it's manual install or some vim package manager), feel free to give me the pasteable line to put here as instructions. Really, people should probably be using Pathogen, in my opinion.\r\nConfiguation\r\n\r\nYou can specify a custom ag name and path in your .vimrc like so:\r\n\r\nlet g:agprg=\"<custom-ag-path-goes-here> --column\"\r\n\r\nUsage\r\n\r\n:Ag [options] {pattern} [{directory}]\r\n\r\nSearch recursively in {directory} (which defaults to the current directory) for the {pattern}.\r\n\r\nFiles containing the search term will be listed in the split window, along with the line number of the occurrence, once for each occurrence. [Enter] on a line in this window will open the file, and place the cursor on the matching line.\r\n\r\nJust like where you use :grep, :grepadd, :lgrep, and :lgrepadd, you can use :Ag, :AgAdd, :LAg, and :LAgAdd respectively. (See doc\/ag.txt, or install and :h Ag for more information.)\r\nGotchas\r\n\r\nSome characters have special meaning, and need to be escaped your search pattern. For instance, '#'. You have to escape it like this :Ag '\\\\\\#define foo' to search for #define foo.\r\n\r\nSometimes git grep is even faster, though in my experience it's not noticably so.\r\nKeyboard Shortcuts\r\n\r\nIn the quickfix window, you can use:\r\n\r\no    to open (same as enter)\r\ngo   to preview file (open but maintain focus on ag.vim results)\r\nt    to open in new tab\r\nT    to open in new tab silently\r\nh    to open in horizontal split\r\nH    to open in horizontal split silently\r\nv    to open in vertical split\r\ngv   to open in vertical split silently\r\nq    to close the quickfix window\r\n\r\nAcknowledgements\r\n\r\nThis Vim plugin is derived (and by derived, I mean copied, almost entirely) from milesz's ack.vim, which I also recommend installing since you might be in a situation where you have ack but not ag, and don't want to stop to install ag. Also, ack supports --type, and a few other features.","4":"Just like ack.vim but for the faster 'ag' utility.\r\n\r\nFor better formatting, see: https:\/\/github.com\/rking\/ag.vim#readme\r\n\r\nThis plugin is a front for ag, A.K.A. the_silver_searcher. Ag can be used as a replacement for 153% of the uses of ack. This plugin will allow you to run ag from vim, and shows the results in a split window.\r\nInstallation \r\n\r\n\r\nThe Silver Searcher\r\n\r\nYou have to install ag, of course.\r\n\r\nUsually it's a package named 'the_silver_searcher', but it should install easily from Github, otherwise:\r\n\r\ngit clone https:\/\/github.com\/ggreer\/the_silver_searcher\r\ncd the_silver_searcher && .\/build.sh && install\r\n\r\nThen, if you're using pathogen:\r\n\r\ncd ~\/.vim\/bundle && git clone https:\/\/github.com\/rking\/ag.vim\r\n# And run :Helptags from within vim\r\n\r\nIf you're using something else (whether it's manual install or some vim package manager), feel free to give me the pasteable line to put here as instructions. Really, people should probably be using Pathogen, in my opinion.\r\nConfiguation\r\n\r\nYou can specify a custom ag name and path in your .vimrc like so:\r\n\r\nlet g:agprg=\"<custom-ag-path-goes-here> --column\"\r\n\r\nUsage\r\n\r\n:Ag [options] {pattern} [{directory}]\r\n\r\nSearch recursively in {directory} (which defaults to the current directory) for the {pattern}.\r\n\r\nFiles containing the search term will be listed in the split window, along with the line number of the occurrence, once for each occurrence. [Enter] on a line in this window will open the file, and place the cursor on the matching line.\r\n\r\nJust like where you use :grep, :grepadd, :lgrep, and :lgrepadd, you can use :Ag, :AgAdd, :LAg, and :LAgAdd respectively. (See doc\/ag.txt, or install and :h Ag for more information.)\r\nGotchas\r\n\r\nSome characters have special meaning, and need to be escaped your search pattern. For instance, '#'. You have to escape it like this :Ag '\\\\\\#define foo' to search for #define foo.\r\n\r\nSometimes git grep is even faster, though in my experience it's not noticably so.\r\nKeyboard Shortcuts\r\n\r\nIn the quickfix window, you can use:\r\n\r\no    to open (same as enter)\r\ngo   to preview file (open but maintain focus on ag.vim results)\r\nt    to open in new tab\r\nT    to open in new tab silently\r\nh    to open in horizontal split\r\nH    to open in horizontal split silently\r\nv    to open in vertical split\r\ngv   to open in vertical split silently\r\nq    to close the quickfix window\r\n\r\nAcknowledgements\r\n\r\nThis Vim plugin is derived (and by derived, I mean copied, almost entirely) from milesz's ack.vim, which I also recommend installing since you might be in a situation where you have ack but not ag, and don't want to stop to install ag. Also, ack supports --type, and a few other features.","install_details":"(see above)","5":"(see above)","first_name":"Ryan","6":"Ryan","last_name":"King","7":"King","releases":[{"0":"4450","vim_version":"7.0","1":"7.0","script_version":"1.3.1","2":"1.3.1","version_comment":"Updating the rest of the commands. Thanks @wiredool !","3":"Updating the rest of the commands. Thanks @wiredool !","package":"ag-vim.tgz","4":"ag-vim.tgz","src_id":"19616","5":"19616","creation_date":"1362876313","6":"1362876313"},{"0":"4450","vim_version":"7.0","1":"7.0","script_version":"1.3","2":"1.3","version_comment":"Autoloading, plus more fixes","3":"Autoloading, plus more fixes","package":"ag-vim.tgz","4":"ag-vim.tgz","src_id":"19602","5":"19602","creation_date":"1362634450","6":"1362634450"},{"0":"4450","vim_version":"7.0","1":"7.0","script_version":"1.2","2":"1.2","version_comment":"Fix docs, :AgFile - thanks to some excellent Github contributors, scintill and mutewinter","3":"Fix docs, :AgFile - thanks to some excellent Github contributors, scintill and mutewinter","package":"ag.vim","4":"ag.vim","src_id":"19577","5":"19577","creation_date":"1362027455","6":"1362027455"}]},"4449":{"script_id":"4449","0":"4449","script_name":"QuickFixCurrentNumber","1":"QuickFixCurrentNumber","script_type":"utility","2":"utility","summary":"Locate the quickfix item at the cursor position.","3":"Locate the quickfix item at the cursor position.","description":"DESCRIPTION\r\nYou can navigate through the errors in the quickfix list with the built-in\r\n:cfirst, :cnext, etc. commands. The quickfix and location lists have a\r\nnotion of \"current item\" (the highlighted one), and you can easily jump back\r\nto it or others. But there's no built-in way to find out which error is at or\r\nafter the current cursor position, and you cannot limit the navigation to\r\nerrors in the current buffer.\r\n\r\nThis plugin provides additional quickfix commands like :Cnr and :Cgo to\r\nprint \/ go to the item at or after the cursor position, and motions like ]q\r\nto go to previous \/ next errors in the current buffer, based on the cursor\r\nposition.\r\n\r\nSOURCE\r\nInspired by the following Stack Overflow question:\r\n    http:\/\/stackoverflow.com\/questions\/14778612\/jump-to-the-errors-in-the-quickfix-or-location-list-for-the-current-line-in-vim\r\n\r\nUSAGE\r\n:Cnr, :Lnr              Print the number of the item in the quickfix \/\r\n                        location list for the current cursor position (or the\r\n                        next item after the cursor).\r\n\r\n:Cgo[!], :Lgo[!]        Go to the item in the quickfix \/ location list for the\r\ng<C-Q>                  current cursor position (or the next item after the\r\n                        cursor). g<C-Q> (and the commands when [!] is given)\r\n                        also jump to the last item if the cursor is after all\r\n                        errors; without [!], the commands then abort with an\r\n                        error.\r\n\r\n[q \/ ]q                 Go to [count] previous \/ next start of an error in the\r\n                        current buffer.\r\ng[q \/ g]q               Go to [count] first \/ last error in the current\r\n                        buffer.\r\n\r\n[l \/ ]l                 Go to [count] previous \/ next start of a location list\r\n                        item in the current buffer.\r\ng[l \/ g]l               Go to [count] first \/ last location list item in the\r\n                        current buffer.","4":"DESCRIPTION\r\nYou can navigate through the errors in the quickfix list with the built-in\r\n:cfirst, :cnext, etc. commands. The quickfix and location lists have a\r\nnotion of \"current item\" (the highlighted one), and you can easily jump back\r\nto it or others. But there's no built-in way to find out which error is at or\r\nafter the current cursor position, and you cannot limit the navigation to\r\nerrors in the current buffer.\r\n\r\nThis plugin provides additional quickfix commands like :Cnr and :Cgo to\r\nprint \/ go to the item at or after the cursor position, and motions like ]q\r\nto go to previous \/ next errors in the current buffer, based on the cursor\r\nposition.\r\n\r\nSOURCE\r\nInspired by the following Stack Overflow question:\r\n    http:\/\/stackoverflow.com\/questions\/14778612\/jump-to-the-errors-in-the-quickfix-or-location-list-for-the-current-line-in-vim\r\n\r\nUSAGE\r\n:Cnr, :Lnr              Print the number of the item in the quickfix \/\r\n                        location list for the current cursor position (or the\r\n                        next item after the cursor).\r\n\r\n:Cgo[!], :Lgo[!]        Go to the item in the quickfix \/ location list for the\r\ng<C-Q>                  current cursor position (or the next item after the\r\n                        cursor). g<C-Q> (and the commands when [!] is given)\r\n                        also jump to the last item if the cursor is after all\r\n                        errors; without [!], the commands then abort with an\r\n                        error.\r\n\r\n[q \/ ]q                 Go to [count] previous \/ next start of an error in the\r\n                        current buffer.\r\ng[q \/ g]q               Go to [count] first \/ last error in the current\r\n                        buffer.\r\n\r\n[l \/ ]l                 Go to [count] previous \/ next start of a location list\r\n                        item in the current buffer.\r\ng[l \/ g]l               Go to [count] first \/ last location list item in the\r\n                        current buffer.","install_details":"INSTALLATION\r\nThis script is packaged as a vimball. If you have the \"gunzip\" decompressor\r\nin your PATH, simply edit the *.vmb.gz package in Vim; otherwise, decompress\r\nthe archive first, e.g. using WinZip. Inside Vim, install by sourcing the\r\nvimball or via the :UseVimball command.\r\n    vim QuickFixCurrentNumber*.vmb.gz\r\n    :so %\r\nTo uninstall, use the :RmVimball command.\r\n\r\nDEPENDENCIES\r\n- Requires Vim 7.0 or higher.\r\n- Requires the ingo-library.vim plugin (vimscript #4433), version 1.023 or\r\n  higher.\r\n\r\nCONFIGURATION\r\nFor a permanent configuration, put the following commands into your vimrc:\r\n\r\nIf you want to use different mappings, map your keys to the\r\n<Plug>(QuickFixCurrentNumber...) mapping targets _before_ sourcing the script\r\n(e.g. in your vimrc):\r\n    nmap g<C-q> <Plug>(QuickFixCurrentNumberGo)\r\n    nmap ]q     <Plug>(QuickFixCurrentNumberQNext)\r\n    nmap [q     <Plug>(QuickFixCurrentNumberQPrev)\r\n    nmap ]l     <Plug>(QuickFixCurrentNumberLNext)\r\n    nmap [l     <Plug>(QuickFixCurrentNumberLPrev)\r\n    nmap g[q    <Plug>(QuickFixCurrentNumberQFirst)\r\n    nmap g]q    <Plug>(QuickFixCurrentNumberQLast)\r\n    nmap g[l    <Plug>(QuickFixCurrentNumberLFirst)\r\n    nmap g]l    <Plug>(QuickFixCurrentNumberLLast)\r\nIf you want no or only a few of the available mappings, you can completely\r\nturn off the creation of the default mappings via:\r\n    :let g:no_QuickFixCurrentNumber_maps = 1\r\nThis saves you from mapping dummy keys to all unwanted mapping targets.","5":"INSTALLATION\r\nThis script is packaged as a vimball. If you have the \"gunzip\" decompressor\r\nin your PATH, simply edit the *.vmb.gz package in Vim; otherwise, decompress\r\nthe archive first, e.g. using WinZip. Inside Vim, install by sourcing the\r\nvimball or via the :UseVimball command.\r\n    vim QuickFixCurrentNumber*.vmb.gz\r\n    :so %\r\nTo uninstall, use the :RmVimball command.\r\n\r\nDEPENDENCIES\r\n- Requires Vim 7.0 or higher.\r\n- Requires the ingo-library.vim plugin (vimscript #4433), version 1.023 or\r\n  higher.\r\n\r\nCONFIGURATION\r\nFor a permanent configuration, put the following commands into your vimrc:\r\n\r\nIf you want to use different mappings, map your keys to the\r\n<Plug>(QuickFixCurrentNumber...) mapping targets _before_ sourcing the script\r\n(e.g. in your vimrc):\r\n    nmap g<C-q> <Plug>(QuickFixCurrentNumberGo)\r\n    nmap ]q     <Plug>(QuickFixCurrentNumberQNext)\r\n    nmap [q     <Plug>(QuickFixCurrentNumberQPrev)\r\n    nmap ]l     <Plug>(QuickFixCurrentNumberLNext)\r\n    nmap [l     <Plug>(QuickFixCurrentNumberLPrev)\r\n    nmap g[q    <Plug>(QuickFixCurrentNumberQFirst)\r\n    nmap g]q    <Plug>(QuickFixCurrentNumberQLast)\r\n    nmap g[l    <Plug>(QuickFixCurrentNumberLFirst)\r\n    nmap g]l    <Plug>(QuickFixCurrentNumberLLast)\r\nIf you want no or only a few of the available mappings, you can completely\r\nturn off the creation of the default mappings via:\r\n    :let g:no_QuickFixCurrentNumber_maps = 1\r\nThis saves you from mapping dummy keys to all unwanted mapping targets.","first_name":"Ingo","6":"Ingo","last_name":"Karkat","7":"Karkat","releases":[{"0":"4449","vim_version":"7.0","1":"7.0","script_version":"1.11","2":"1.11","version_comment":"- :Cgo and :Lgo take [!] to behave like g<C-Q>, i.e. jump back to the last error instead of aborting. This is helpful because g<C-Q> only crudely distinguishes between location and quickfix list, and both may be in use. Thanks to Enno Nagel for the suggestion.\r\n- Allow to disable all default mappings via g:no_QuickFixCurrentNumber_maps. Some users may prefer straightforward navigation through quickfix errors with ]q (e.g. as provided by the unimpaired.vim plugin).\r\n- BUG: Script errors when jump mappings like ]q are executed in a quickfix \/ location list. Need to populate the bufferQflist property in the returned result and tweak the check in QuickFixCurrentNumber#Next(). Thanks to Enno Nagel for reporting this.\r\n- Use ingo\/err.vim for error reporting.","3":"- :Cgo and :Lgo take [!] to behave like g<C-Q>, i.e. jump back to the last error instead of aborting. This is helpful because g<C-Q> only crudely distinguishes between location and quickfix list, and both may be in use. Thanks to Enno Nagel for the suggestion.\r\n- Allow to disable all default mappings via g:no_QuickFixCurrentNumber_maps. Some users may prefer straightforward navigation through quickfix errors with ]q (e.g. as provided by the unimpaired.vim plugin).\r\n- BUG: Script errors when jump mappings like ]q are executed in a quickfix \/ location list. Need to populate the bufferQflist property in the returned result and tweak the check in QuickFixCurrentNumber#Next(). Thanks to Enno Nagel for reporting this.\r\n- Use ingo\/err.vim for error reporting.","package":"QuickFixCurrentNumber-1.11.vmb.gz","4":"QuickFixCurrentNumber-1.11.vmb.gz","src_id":"23010","5":"23010","creation_date":"1426068745","6":"1426068745"},{"0":"4449","vim_version":"7.0","1":"7.0","script_version":"1.10","2":"1.10","version_comment":"- g<C-Q> now also jumps to the last item if the cursor is after all errors; the commands continue to abort with a \"No more items\" error. This allows to jump to the next \/ closest error position, regardless of the cursor position. Thanks to Enno Nagel for the suggestion.\r\n- Factor out ingo#window#quickfix#TranslateVirtualColToByteCount() into ingo-library. *** You need to update to ingo-library (vimscript #4433) version 1.023! ***","3":"- g<C-Q> now also jumps to the last item if the cursor is after all errors; the commands continue to abort with a \"No more items\" error. This allows to jump to the next \/ closest error position, regardless of the cursor position. Thanks to Enno Nagel for the suggestion.\r\n- Factor out ingo#window#quickfix#TranslateVirtualColToByteCount() into ingo-library. *** You need to update to ingo-library (vimscript #4433) version 1.023! ***","package":"QuickFixCurrentNumber-1.10.vmb.gz","4":"QuickFixCurrentNumber-1.10.vmb.gz","src_id":"22989","5":"22989","creation_date":"1425845191","6":"1425845191"},{"0":"4449","vim_version":"7.0","1":"7.0","script_version":"1.00","2":"1.00","version_comment":"Initial upload","3":"Initial upload","package":"QuickFixCurrentNumber-1.00.vmb.gz","4":"QuickFixCurrentNumber-1.00.vmb.gz","src_id":"19551","5":"19551","creation_date":"1361275448","6":"1361275448"}]},"4440":{"script_id":"4440","0":"4440","script_name":"Flake8-vim","1":"Flake8-vim","script_type":"ftplugin","2":"ftplugin","summary":"Automatic syntax checker for Python, bundled with pep8, pyflakes and mccabe.","3":"Automatic syntax checker for Python, bundled with pep8, pyflakes and mccabe.","description":"Automatic syntax checker for Python programming language, bundled with pep8, pyflakes, mccabe for easy installation and use. Requires python-enabled Vim. Main development goes on https:\/\/github.com\/andviro\/flake8-vim \r\n\r\nAfter installation script is ready to go. Syntax checking starts on buffer write. See README.md for usage details.","4":"Automatic syntax checker for Python programming language, bundled with pep8, pyflakes, mccabe for easy installation and use. Requires python-enabled Vim. Main development goes on https:\/\/github.com\/andviro\/flake8-vim \r\n\r\nAfter installation script is ready to go. Syntax checking starts on buffer write. See README.md for usage details.","install_details":"Simply unpack files to your .vim directory. Preferred install method is through Vundle:\r\n\r\n:BundleInstall andviro\/flake8-vim","5":"Simply unpack files to your .vim directory. Preferred install method is through Vundle:\r\n\r\n:BundleInstall andviro\/flake8-vim","first_name":"Andrew","6":"Andrew","last_name":"Rodionoff","7":"Rodionoff","releases":[{"0":"4440","vim_version":"7.0","1":"7.0","script_version":"0.5","2":"0.5","version_comment":"fixed handling of syntax errors","3":"fixed handling of syntax errors","package":"flake8-vim.zip","4":"flake8-vim.zip","src_id":"19658","5":"19658","creation_date":"1363534694","6":"1363534694"},{"0":"4440","vim_version":"7.0","1":"7.0","script_version":"0.4","2":"0.4","version_comment":"added range support for PyFlakeAuto","3":"added range support for PyFlakeAuto","package":"flake8-vim.zip","4":"flake8-vim.zip","src_id":"19562","5":"19562","creation_date":"1361568530","6":"1361568530"},{"0":"4440","vim_version":"7.0","1":"7.0","script_version":"0.3","2":"0.3","version_comment":"fixed some pep8 messages not having type","3":"fixed some pep8 messages not having type","package":"flake8-vim.zip","4":"flake8-vim.zip","src_id":"19559","5":"19559","creation_date":"1361475325","6":"1361475325"},{"0":"4440","vim_version":"7.0","1":"7.0","script_version":"0.2","2":"0.2","version_comment":"windows-specific bugfixes, new option for maximum line length","3":"windows-specific bugfixes, new option for maximum line length","package":"flake8-vim.zip","4":"flake8-vim.zip","src_id":"19554","5":"19554","creation_date":"1361289468","6":"1361289468"},{"0":"4440","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"flake8-vim.zip","4":"flake8-vim.zip","src_id":"19535","5":"19535","creation_date":"1361113821","6":"1361113821"}]},"4439":{"script_id":"4439","0":"4439","script_name":"Dev_Delight","1":"Dev_Delight","script_type":"color scheme","2":"color scheme","summary":"This Color-Scheme provides a very Elegant Display with Minimal Eye-Strain","3":"This Color-Scheme provides a very Elegant Display with Minimal Eye-Strain","description":"This Script provides a GUI only color-scheme. \r\n\r\nGITHUB Repository:\r\n\r\nhttp:\/\/github.com\/sandeepsinghmails\/Dev_Delight\r\n\r\nScreenshot:\r\n\r\nhttp:\/\/github.com\/sandeepsinghmails\/Dev_Delight\/blob\/master\/Images\/Screenshot_1.jpeg\r\n\r\nHow To Use Dev_Delight?\r\n\r\nUse the command \":color Dev_Delight\"\r\n\r\nHow To Set Dev_Delight as your Default Color Scheme?\r\n\r\nAdd the following Line (as-it-is) to your .gvimrc File:\r\n\r\ncolorscheme Dev_Delight","4":"This Script provides a GUI only color-scheme. \r\n\r\nGITHUB Repository:\r\n\r\nhttp:\/\/github.com\/sandeepsinghmails\/Dev_Delight\r\n\r\nScreenshot:\r\n\r\nhttp:\/\/github.com\/sandeepsinghmails\/Dev_Delight\/blob\/master\/Images\/Screenshot_1.jpeg\r\n\r\nHow To Use Dev_Delight?\r\n\r\nUse the command \":color Dev_Delight\"\r\n\r\nHow To Set Dev_Delight as your Default Color Scheme?\r\n\r\nAdd the following Line (as-it-is) to your .gvimrc File:\r\n\r\ncolorscheme Dev_Delight","install_details":"Save the file as \"colors\/Dev_Delight.vim\" under your \".vim\" directory. \r\n\r\ni.e. as ~\/.vim\/colors\/Dev_Delight.vim (on GNU\/Linux OS).\r\n","5":"Save the file as \"colors\/Dev_Delight.vim\" under your \".vim\" directory. \r\n\r\ni.e. as ~\/.vim\/colors\/Dev_Delight.vim (on GNU\/Linux OS).\r\n","first_name":"Sandeep","6":"Sandeep","last_name":"Singh","7":"Singh","releases":[{"0":"4439","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial Upload","3":"Initial Upload","package":"Dev_Delight.zip","4":"Dev_Delight.zip","src_id":"19540","5":"19540","creation_date":"1361118766","6":"1361118766"}]},"4438":{"script_id":"4438","0":"4438","script_name":"rythm.vim","1":"rythm.vim","script_type":"ftplugin","2":"ftplugin","summary":"Rythm template engine plugin","3":"Rythm template engine plugin","description":"\r\n* Usage *\r\nBy default it recognizes Rythm templates stored in rythm\/ folder and files with double extension corresponging to *.rythm.html pattern, but you can extends this behaviour by adding custom autocmd in your .vimrc file. For example:\r\n\r\n  au BufRead,BufNewFile *\/views\/*.html :set ft=rythm\r\n\r\n* Tests *\r\nFor testing of syntax highlighting you can clone Rythm website repository from https:\/\/github.com\/greenlaw110\/rythm-website.","4":"\r\n* Usage *\r\nBy default it recognizes Rythm templates stored in rythm\/ folder and files with double extension corresponging to *.rythm.html pattern, but you can extends this behaviour by adding custom autocmd in your .vimrc file. For example:\r\n\r\n  au BufRead,BufNewFile *\/views\/*.html :set ft=rythm\r\n\r\n* Tests *\r\nFor testing of syntax highlighting you can clone Rythm website repository from https:\/\/github.com\/greenlaw110\/rythm-website.","install_details":"\r\n* Using pathogen (https:\/\/github.com\/tpope\/vim-pathogen) or vundle (https:\/\/github.com\/gmarik\/vundle) from https:\/\/github.com\/rdolgushin\/rythm.vim\r\n* Standard Vim way (http:\/\/vimdoc.sourceforge.net\/htmldoc\/usr_05.html#add-plugin)","5":"\r\n* Using pathogen (https:\/\/github.com\/tpope\/vim-pathogen) or vundle (https:\/\/github.com\/gmarik\/vundle) from https:\/\/github.com\/rdolgushin\/rythm.vim\r\n* Standard Vim way (http:\/\/vimdoc.sourceforge.net\/htmldoc\/usr_05.html#add-plugin)","first_name":"Roman","6":"Roman","last_name":"Dolgushin","7":"Dolgushin","releases":[{"0":"4438","vim_version":"7.0","1":"7.0","script_version":"1.02","2":"1.02","version_comment":"tComment support added","3":"tComment support added","package":"rythm.zip","4":"rythm.zip","src_id":"20668","5":"20668","creation_date":"1376772815","6":"1376772815"},{"0":"4438","vim_version":"7.0","1":"7.0","script_version":"1.01","2":"1.01","version_comment":"Syntax highlighting was fixed and improved. Added support of Matchit for html tags.","3":"Syntax highlighting was fixed and improved. Added support of Matchit for html tags.","package":"rythm.zip","4":"rythm.zip","src_id":"19515","5":"19515","creation_date":"1360979852","6":"1360979852"},{"0":"4438","vim_version":"6.0","1":"6.0","script_version":"1","2":"1","version_comment":"Initial upload","3":"Initial upload","package":"rythm.zip","4":"rythm.zip","src_id":"19514","5":"19514","creation_date":"1360939603","6":"1360939603"}]},"4437":{"script_id":"4437","0":"4437","script_name":"redif.vim","1":"redif.vim","script_type":"syntax","2":"syntax","summary":"Syntax highlighting for ReDIF format used by RePEc","3":"Syntax highlighting for ReDIF format used by RePEc","description":"Syntax highlighting for ReDIF format used by RePEc:\r\n\r\nSource: http:\/\/openlib.org\/acmes\/root\/docu\/redif_1.html\r\n\r\n####### Supported:\r\nComments\r\nFolding\r\nCorrect fields\r\nCorrect templates\r\nClusters\r\nSome special arguments\r\nLocalize spell checking for Title, Abstract and some others (use :set spell to enable it)\r\nHighlights as error:\r\n    - Fields that do not belong to the current template.\r\n    - Fields that should belong to a cluster but do not.\r\n    - Wrong arguments (for most fields but not all)\r\n\r\n####### Not supported:\r\nDoes not always highlights arguments as error even when they are erroneous. In particular:\r\n    - Does not check whether non-repeatable fields are repeated\r\n    - Does not check URLs\r\n    - Does not check logic (for instance \"40-30\" is not highlighted in a \"Pages\" field, even if 40 > 30)\r\n    - A few others\r\n\r\nMoreover, the spell checking does flag several common words in economics, such as Schumpeterian, macroeconometrics, etc.\r\n\r\nThe file is well-commented; you can read it for more information.","4":"Syntax highlighting for ReDIF format used by RePEc:\r\n\r\nSource: http:\/\/openlib.org\/acmes\/root\/docu\/redif_1.html\r\n\r\n####### Supported:\r\nComments\r\nFolding\r\nCorrect fields\r\nCorrect templates\r\nClusters\r\nSome special arguments\r\nLocalize spell checking for Title, Abstract and some others (use :set spell to enable it)\r\nHighlights as error:\r\n    - Fields that do not belong to the current template.\r\n    - Fields that should belong to a cluster but do not.\r\n    - Wrong arguments (for most fields but not all)\r\n\r\n####### Not supported:\r\nDoes not always highlights arguments as error even when they are erroneous. In particular:\r\n    - Does not check whether non-repeatable fields are repeated\r\n    - Does not check URLs\r\n    - Does not check logic (for instance \"40-30\" is not highlighted in a \"Pages\" field, even if 40 > 30)\r\n    - A few others\r\n\r\nMoreover, the spell checking does flag several common words in economics, such as Schumpeterian, macroeconometrics, etc.\r\n\r\nThe file is well-commented; you can read it for more information.","install_details":"Copy-paste it to $VIMRUNTIME\/syntax\/","5":"Copy-paste it to $VIMRUNTIME\/syntax\/","first_name":"Axel","6":"Axel","last_name":"Castellane","7":"Castellane","releases":[{"0":"4437","vim_version":"7.0","1":"7.0","script_version":"2.0","2":"2.0","version_comment":"    - folding (with foldmethod=syntax)\r\n    - @Spell for some fields\r\n    - faster and more accurate","3":"    - folding (with foldmethod=syntax)\r\n    - @Spell for some fields\r\n    - faster and more accurate","package":"redif.vim","4":"redif.vim","src_id":"19780","5":"19780","creation_date":"1365393297","6":"1365393297"},{"0":"4437","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"redif.vim","4":"redif.vim","src_id":"19512","5":"19512","creation_date":"1360819903","6":"1360819903"}]},"4436":{"script_id":"4436","0":"4436","script_name":"psearch.vim","1":"psearch.vim","script_type":"utility","2":"utility","summary":"Quick access to search results","3":"Quick access to search results","description":"\r\nExecute the :PSearch command and type something. You'll see a preview \r\nof all the lines where the pattern you gave matches in the currently open buffers. \r\nThe pattern is the one you would normally use doing searches with '\/' and '?' and \r\nwith the \"nomagic\" option set. \r\n\r\nTo interact with the matches list use the following keys: \r\n\r\n  UP, CTRL+K : move up in the list. \r\n\r\n  DOWN, CTRL+J : move down in the list. \r\n\r\n  LEFT, CTRL+H : view the matches list of the previous buffer. \r\n\r\n  RIGHT, CTRL+L : view the matches list of the next buffer. \r\n\r\n  RETURN, CTRL+G : go to the selected match. \r\n\r\n  CTRL+A : show jump marks for each result.\r\n\r\n  CTRL+T : move the cursor to the first match in the matches list. \r\n\r\n  CTRL+B : move the cursor to the last match in the matches list. \r\n\r\n  ESC, CTRL+C : close the matches list. \r\n\r\n\r\nPressing CTRL+A in the psearch navigation buffer will add jump marks denoted\r\nin the format <[a-z]> for each search result entry. When the marks have been\r\ndisplayed entering any of the letters used as mark will jump directly to the\r\nrespective entry and close the search navigation. Entering anything that is\r\nnot a mark will discard the action.\r\n","4":"\r\nExecute the :PSearch command and type something. You'll see a preview \r\nof all the lines where the pattern you gave matches in the currently open buffers. \r\nThe pattern is the one you would normally use doing searches with '\/' and '?' and \r\nwith the \"nomagic\" option set. \r\n\r\nTo interact with the matches list use the following keys: \r\n\r\n  UP, CTRL+K : move up in the list. \r\n\r\n  DOWN, CTRL+J : move down in the list. \r\n\r\n  LEFT, CTRL+H : view the matches list of the previous buffer. \r\n\r\n  RIGHT, CTRL+L : view the matches list of the next buffer. \r\n\r\n  RETURN, CTRL+G : go to the selected match. \r\n\r\n  CTRL+A : show jump marks for each result.\r\n\r\n  CTRL+T : move the cursor to the first match in the matches list. \r\n\r\n  CTRL+B : move the cursor to the last match in the matches list. \r\n\r\n  ESC, CTRL+C : close the matches list. \r\n\r\n\r\nPressing CTRL+A in the psearch navigation buffer will add jump marks denoted\r\nin the format <[a-z]> for each search result entry. When the marks have been\r\ndisplayed entering any of the letters used as mark will jump directly to the\r\nrespective entry and close the search navigation. Entering anything that is\r\nnot a mark will discard the action.\r\n","install_details":"\r\nInstall with your favorite plugin manager.\r\n\r\nRequires Python 2.6+\r\n","5":"\r\nInstall with your favorite plugin manager.\r\n\r\nRequires Python 2.6+\r\n","first_name":"geck","6":"geck","last_name":" ","7":" ","releases":[{"0":"4436","vim_version":"7.2","1":"7.2","script_version":"0.3","2":"0.3","version_comment":"- Added \"jump to mark\" functionality for quick access to search results.\r\n- Minor bugfixes.\r\n","3":"- Added \"jump to mark\" functionality for quick access to search results.\r\n- Minor bugfixes.\r\n","package":"psearch-0.3.zip","4":"psearch-0.3.zip","src_id":"19570","5":"19570","creation_date":"1361902980","6":"1361902980"},{"0":"4436","vim_version":"7.2","1":"7.2","script_version":"0.2","2":"0.2","version_comment":"- Searches are now performed in all buffers. \r\n- Fix issues with some input characters.\r\n","3":"- Searches are now performed in all buffers. \r\n- Fix issues with some input characters.\r\n","package":"psearch-0.2.zip","4":"psearch-0.2.zip","src_id":"19561","5":"19561","creation_date":"1361539461","6":"1361539461"},{"0":"4436","vim_version":"7.2","1":"7.2","script_version":"0.1.0","2":"0.1.0","version_comment":"Initial upload","3":"Initial upload","package":"psearch-0.1.0.zip","4":"psearch-0.1.0.zip","src_id":"19507","5":"19507","creation_date":"1360753704","6":"1360753704"}]},"4435":{"script_id":"4435","0":"4435","script_name":"tla.vim","1":"tla.vim","script_type":"color scheme","2":"color scheme","summary":"TLA+ specification language","3":"TLA+ specification language","description":"Syntax highlighting for the TLA+ specification language. TLA stands for the Temporal Logic of Actions. \r\n\r\nThe TLA home page is: http:\/\/research.microsoft.com\/en-us\/um\/people\/lamport\/tla\/tla.html\r\nIt says: \"TLA+ is based on the idea that the best way to describe things formally is with simple mathematics, and that a specification language should contain as little as possible beyond what is needed to write simple mathematics precisely. TLA+ is especially well suited for writing high-level specifications of concurrent and distributed systems.\"","4":"Syntax highlighting for the TLA+ specification language. TLA stands for the Temporal Logic of Actions. \r\n\r\nThe TLA home page is: http:\/\/research.microsoft.com\/en-us\/um\/people\/lamport\/tla\/tla.html\r\nIt says: \"TLA+ is based on the idea that the best way to describe things formally is with simple mathematics, and that a specification language should contain as little as possible beyond what is needed to write simple mathematics precisely. TLA+ is especially well suited for writing high-level specifications of concurrent and distributed systems.\"","install_details":"","5":"","first_name":"Diego","6":"Diego","last_name":"Ongaro","7":"Ongaro","releases":[{"0":"4435","vim_version":"7.0","1":"7.0","script_version":"2","2":"2","version_comment":"- adds TRUE and FALSE as booleans\r\n- fixes highlighting ----- when there\\\\\\'s not an even multiple of four\r\n- fixes highlighting of nested multi-line comments\r\n","3":"- adds TRUE and FALSE as booleans\r\n- fixes highlighting ----- when there\\\\\\'s not an even multiple of four\r\n- fixes highlighting of nested multi-line comments\r\n","package":"tla.vim","4":"tla.vim","src_id":"19542","5":"19542","creation_date":"1361239692","6":"1361239692"},{"0":"4435","vim_version":"7.0","1":"7.0","script_version":"1","2":"1","version_comment":"Initial upload","3":"Initial upload","package":"tla.vim","4":"tla.vim","src_id":"19505","5":"19505","creation_date":"1360749930","6":"1360749930"}]},"4434":{"script_id":"4434","0":"4434","script_name":"Erroneous","1":"Erroneous","script_type":"utility","2":"utility","summary":"The right way to handle errors","3":"The right way to handle errors","description":"GitHub repository: https:\/\/github.com\/idanarye\/vim-erroneous\r\n\r\nErroneous is a plugin for handling errors from external programs. Vim provides you with the :make command to run compilers and parse the errors using the 'errorformat' option, but you must set the 'errorformat' option in advance. If you use more than one language regularly, you'll have to change 'errorformat' often. This is usually done with file-type plugins - but that means you have to always compile from one of the source files(you can't, for example, compile from one of the configuration XML files). You can also set a long, compound 'errorformat' that can catch errors in many formats - but from my experience those catch-all 'errorformat's tend to identify error-description lines as error headlines and create entries in the quickfix list that are mapped to nowhere and send you to empty buffers. Not as fun as it sounds...\r\n\r\nErroneous takes a different approach - instead of parsing stderr based on the filetype, parsing is done based on the shell command that invoked the program that created the error. So, if you run javac MyClass.java Erroneous will automatically set the 'errorformat' to parse javac errors, while running gcc main.c will cause Erroneous to set 'errorformat' to parse gcc errors.\r\n\r\nErroneous can also read shebangs to know how to parse errors of interepted scripts in linux, and it provides API for other plugins that want to determine the error format by other means.","4":"GitHub repository: https:\/\/github.com\/idanarye\/vim-erroneous\r\n\r\nErroneous is a plugin for handling errors from external programs. Vim provides you with the :make command to run compilers and parse the errors using the 'errorformat' option, but you must set the 'errorformat' option in advance. If you use more than one language regularly, you'll have to change 'errorformat' often. This is usually done with file-type plugins - but that means you have to always compile from one of the source files(you can't, for example, compile from one of the configuration XML files). You can also set a long, compound 'errorformat' that can catch errors in many formats - but from my experience those catch-all 'errorformat's tend to identify error-description lines as error headlines and create entries in the quickfix list that are mapped to nowhere and send you to empty buffers. Not as fun as it sounds...\r\n\r\nErroneous takes a different approach - instead of parsing stderr based on the filetype, parsing is done based on the shell command that invoked the program that created the error. So, if you run javac MyClass.java Erroneous will automatically set the 'errorformat' to parse javac errors, while running gcc main.c will cause Erroneous to set 'errorformat' to parse gcc errors.\r\n\r\nErroneous can also read shebangs to know how to parse errors of interepted scripts in linux, and it provides API for other plugins that want to determine the error format by other means.","install_details":"After extracting the zip\/cloning from GitHub, you need to set the g:erroneous_errorFormatChooserPatterns and\/or the g:erroneous_errorFormatChooserWords dictionaries. See \":help erroneous-configurations\" for instructions how to do that.","5":"After extracting the zip\/cloning from GitHub, you need to set the g:erroneous_errorFormatChooserPatterns and\/or the g:erroneous_errorFormatChooserWords dictionaries. See \":help erroneous-configurations\" for instructions how to do that.","first_name":"Idan","6":"Idan","last_name":"Arye","7":"Arye","releases":[{"0":"4434","vim_version":"7.3","1":"7.3","script_version":"1.3.0","2":"1.3.0","version_comment":"Add an Omnipytent extension module","3":"Add an Omnipytent extension module","package":"erroneous_v1.3.0.zip","4":"erroneous_v1.3.0.zip","src_id":"25678","5":"25678","creation_date":"1512091045","6":"1512091045"},{"0":"4434","vim_version":"7.0","1":"7.0","script_version":"1.2.0","2":"1.2.0","version_comment":"Add Waf support","3":"Add Waf support","package":"erroneous_v1.2.0.zip","4":"erroneous_v1.2.0.zip","src_id":"22319","5":"22319","creation_date":"1407872151","6":"1407872151"},{"0":"4434","vim_version":"7.0","1":"7.0","script_version":"1.1.1","2":"1.1.1","version_comment":"Use IO.select to improve speed of Ruby implementation","3":"Use IO.select to improve speed of Ruby implementation","package":"erroneous_v1.1.1.zip","4":"erroneous_v1.1.1.zip","src_id":"22307","5":"22307","creation_date":"1407530218","6":"1407530218"},{"0":"4434","vim_version":"7.0","1":"7.0","script_version":"1.1.0","2":"1.1.0","version_comment":" * Added erroneous#parseXBuildErrorOutput for handling XBuild and MSBuild.\r\n * Can now read the shell exit code even without Ruby, so you no longer need Ruby support to run Maven(with Ruby it's still more awesome though).","3":" * Added erroneous#parseXBuildErrorOutput for handling XBuild and MSBuild.\r\n * Can now read the shell exit code even without Ruby, so you no longer need Ruby support to run Maven(with Ruby it's still more awesome though).","package":"erroneous_v1.1.0.zip","4":"erroneous_v1.1.0.zip","src_id":"21144","5":"21144","creation_date":"1386025313","6":"1386025313"},{"0":"4434","vim_version":"7.3","1":"7.3","script_version":"1.0.0","2":"1.0.0","version_comment":"Initial upload","3":"Initial upload","package":"erroneous_v1.0.0.zip","4":"erroneous_v1.0.0.zip","src_id":"19503","5":"19503","creation_date":"1360702773","6":"1360702773"}]},"4433":{"script_id":"4433","0":"4433","script_name":"ingo-library","1":"ingo-library","script_type":"utility","2":"utility","summary":"Vimscript library of common functions.","3":"Vimscript library of common functions.","description":"DESCRIPTION\r\nThis library contains common autoload functions that are used by almost all of\r\nmy plugins (http:\/\/www.vim.org\/account\/profile.php?user_id=9713). Instead of\r\nduplicating the functionality, or installing potentially conflicting versions\r\nwith each plugin, this one core dependency fosters a lean Vim runtime and\r\neasier plugin updates.\r\n\r\nSeparating common functions is explicitly recommended by Vim; see\r\nwrite-library-script. The autoload mechanism was created to make this\r\nreally easy and efficient. Only those scripts that contain functions that are\r\nactually used are loaded, the rest is ignored; it just \"wastes\" the space on\r\ndisk. (Not using autoload functions, and duplicating utility functions in the\r\nplugin script itself, now that would be truly bad.)\r\n\r\nStill, if you only use one or few of my plugins, yes, this might look\r\nwasteful. However, I have published an awful lot of plugins (most of which now\r\nuse ingo-library), and intend to continue to do so. Considering that, the\r\ndecision to extract the common functionality (which caused a lot of effort for\r\nme) benefits both users (no duplication, no incompatibilities, faster updates)\r\nand me (less overall effort in maintaining, more time for features). Please\r\nkeep that in mind before complaining about this dependency.\r\n\r\nFurthermore, several other authors have been following the same approach:\r\n\r\nRELATED WORKS\r\nOther authors have published separate support libraries, too:\r\n\r\n- genutils (vimscript #197) by Hari Krishna Dara\r\n- lh-vim-lib (vimscript #214) by Luc Hermitte\r\n- cecutil (vimscript #1066) by DrChip\r\n- tlib (vimscript #1863) by Thomas Link\r\n- TOVL (vimscript #1963) by Marc Weber\r\n- l9 (vimscript #3252) by Takeshi Nishida\r\n- anwolib (vimscript #3800) by Andy Wokula\r\n- vim-misc (vimscript #4597) by Peter Odding\r\n- maktaba (https:\/\/github.com\/google\/maktaba) by Google\r\n- vital (https:\/\/github.com\/vim-jp\/vital.vim) by the Japanese Vim user group\r\n- underscore.vim (vimscript #5149) by haya14busa provides functional\r\n  programming functions and depends on the (rather complex) vital library\r\n\r\nThere have been initiatives to gather and consolidate useful functions into a\r\n\"standard Vim library\", but these efforts have mostly fizzled out.\r\n\r\nUSAGE\r\nThis library is mainly intended to be used by my own plugins. However, I try\r\nto maintain backwards compatibility as much as possible. Feel free to use the\r\nlibrary for your own plugins and customizations, too. I'd also like to hear\r\nfrom you if you have additions or comments.\r\n\r\nEXCEPTION HANDLING\r\nFor exceptional conditions (e.g. cannot locate window that should be there)\r\nand programming errors (e.g. passing a wrong variable type to a library\r\nfunction), error strings are |:throw|n. These are prefixed with (something\r\nresembling) the short function name, so that it's possible to :catch these\r\nand e.g. convert them into a proper error (e.g. via\r\ningo#err#SetCustomException()).\r\n\r\nCONFIGURATION\r\nThe filespec to the external \"date\" command can be set via:\r\n    let g:IngoLibrary_DateCommand = 'date'\r\n\r\nThe preferred date format used by ingo#date#format#Preferred() can be set to a\r\nstrftime() format via:\r\n    let g:IngoLibrary_PreferredDateFormat = '%x'\r\n\r\nThe size of the file cache (in bytes) used by ingo#file#GetLines() can be set\r\nvia:\r\n    let g:IngoLibrary_FileCacheMaxSize = 1048576\r\n\r\nThe string used as a replacement for truncated text can be set via:\r\n    let g:IngoLibrary_TruncateEllipsis = \"\\u2026\"\r\n\r\nThe check for special windows in ingo#window#special#IsSpecialWindow() can be\r\ncustomized via a List of Expressions or Funcrefs that are passed the window\r\nnumber, and which should return a boolean flag. If any predicate is true, the\r\nwindow is deemed special.\r\n    let g:IngoLibrary_SpecialWindowPredicates =\r\n    \\   ['bufname(winbufnr(v:val)) =~# \"^\\\\[\\\\%(Scratch\\\\|clipboard\\\\)\\\\]$\"']\r\n\r\ningo#plugin#marks#Reserve() by default uses any unused mark. You can instead\r\nassign a fixed set of marks that will be available for plugins via:\r\n    let g:IngoLibrary_Marks = 'abcABC'\r\n\r\nSome special filenames are caught by BufNewFile,BufRead autocmds and\r\ntranslated into existing files. ingo#cmdargs#glob#Resolve() can be taught\r\nthose patterns by configuring a List of Funcrefs or expressions in\r\ng:IngoLibrary_SpecialFilePredicates that take a single filespec argument \/\r\nv:val and return whether this is an existing file. This will then correct the\r\nstatistics information returned by the function.\r\nBy default, includes any filespec that starts with a \"protocol:\/\" (e.g. scp:\/\/\r\nfor netrw), and also file:lnum[:column] special filenames if\r\nhttps:\/\/github.com\/bogado\/file-line is installed.\r\n\r\nThe ingo#text#InsertHere() function is often used to insert text at the cursor\r\nposition by plugins that don't want to offer separate insert \/ append mappings\r\n(comparable to |p|\/|P| pasting). The function tries to find a meaningful\r\ninsertion point. Its strategy can be tweaked via the following values:\r\n- insert1:  at the beginning of the line if the cursor is in column 1, else\r\n            appending after the character the cursor is on.\r\n- append$:  appending after the character if the cursor is at the end of the\r\n            line (with 'virtualedit' having \"onemore\": one beyond the end,\r\n            with \"all\": always insert before the cursor), else inserting\r\n            before the character the cursor is on.\r\n- insert:   always inserting before the character the cursor is on\r\n- append:   always appending after the character the cursor is on\r\n\r\nIf you use some operator-pending mappings as hooks into default motions (e.g.\r\n: or \/) that still maintain the original functionality,\r\ningo#query#get#Motion() can be instructed to ignore those mappings and instead\r\ntreat them as the built-in motions (i.e. still query the command-line or\r\nsearch pattern). Define those keys you want ignored as keys in a Dict (values\r\ndon't matter):\r\n    let g:IngoLibrary_QueryMotionIgnoredMotions = {':': 1, '\/': 1, '?': 1}\r\n\r\nIf you have custom operator-pending mappings that do some tricks like\r\nobtaining additional characters until they're done and moving the cursor,\r\ndefine those keys as keys, and an appendage pattern as value (or the empty\r\nString if there're no additional keys).\r\nThe appendage patterns will capture additional keys until either the pattern\r\ndoes not match any longer (the motion then is deemed invalid and aborts), or\r\nuntil the first capture group is non-empty (the motion then is deemed\r\ncomplete).\r\n    let g:IngoLibrary_QueryMotionCustomMotions = {'key': 'patter\\(n\\)'}\r\n\r\nMotions can be forced to be character- \/ line- \/ blockwise (forced-motion).\r\nIf you have mapped alternatives for v \/ V \/ CTRL-V, define them as keys in:\r\n    let g:IngoLibrary_QueryMotionCustomMotionModifiers = {\"\\<C-q>\": 1}\r\n\r\nIf you've remapped the c_CTRL-K trigger key for digraphs, you can adapt the\r\ndigraph detection by ingo#query#get#CharOrDigraph() and\r\ningo#query#get#[Valid]Char() to the changed mapping via:\r\n    let g:IngoLibrary_DigraphTriggerKey = \"\\<C-k>\"","4":"DESCRIPTION\r\nThis library contains common autoload functions that are used by almost all of\r\nmy plugins (http:\/\/www.vim.org\/account\/profile.php?user_id=9713). Instead of\r\nduplicating the functionality, or installing potentially conflicting versions\r\nwith each plugin, this one core dependency fosters a lean Vim runtime and\r\neasier plugin updates.\r\n\r\nSeparating common functions is explicitly recommended by Vim; see\r\nwrite-library-script. The autoload mechanism was created to make this\r\nreally easy and efficient. Only those scripts that contain functions that are\r\nactually used are loaded, the rest is ignored; it just \"wastes\" the space on\r\ndisk. (Not using autoload functions, and duplicating utility functions in the\r\nplugin script itself, now that would be truly bad.)\r\n\r\nStill, if you only use one or few of my plugins, yes, this might look\r\nwasteful. However, I have published an awful lot of plugins (most of which now\r\nuse ingo-library), and intend to continue to do so. Considering that, the\r\ndecision to extract the common functionality (which caused a lot of effort for\r\nme) benefits both users (no duplication, no incompatibilities, faster updates)\r\nand me (less overall effort in maintaining, more time for features). Please\r\nkeep that in mind before complaining about this dependency.\r\n\r\nFurthermore, several other authors have been following the same approach:\r\n\r\nRELATED WORKS\r\nOther authors have published separate support libraries, too:\r\n\r\n- genutils (vimscript #197) by Hari Krishna Dara\r\n- lh-vim-lib (vimscript #214) by Luc Hermitte\r\n- cecutil (vimscript #1066) by DrChip\r\n- tlib (vimscript #1863) by Thomas Link\r\n- TOVL (vimscript #1963) by Marc Weber\r\n- l9 (vimscript #3252) by Takeshi Nishida\r\n- anwolib (vimscript #3800) by Andy Wokula\r\n- vim-misc (vimscript #4597) by Peter Odding\r\n- maktaba (https:\/\/github.com\/google\/maktaba) by Google\r\n- vital (https:\/\/github.com\/vim-jp\/vital.vim) by the Japanese Vim user group\r\n- underscore.vim (vimscript #5149) by haya14busa provides functional\r\n  programming functions and depends on the (rather complex) vital library\r\n\r\nThere have been initiatives to gather and consolidate useful functions into a\r\n\"standard Vim library\", but these efforts have mostly fizzled out.\r\n\r\nUSAGE\r\nThis library is mainly intended to be used by my own plugins. However, I try\r\nto maintain backwards compatibility as much as possible. Feel free to use the\r\nlibrary for your own plugins and customizations, too. I'd also like to hear\r\nfrom you if you have additions or comments.\r\n\r\nEXCEPTION HANDLING\r\nFor exceptional conditions (e.g. cannot locate window that should be there)\r\nand programming errors (e.g. passing a wrong variable type to a library\r\nfunction), error strings are |:throw|n. These are prefixed with (something\r\nresembling) the short function name, so that it's possible to :catch these\r\nand e.g. convert them into a proper error (e.g. via\r\ningo#err#SetCustomException()).\r\n\r\nCONFIGURATION\r\nThe filespec to the external \"date\" command can be set via:\r\n    let g:IngoLibrary_DateCommand = 'date'\r\n\r\nThe preferred date format used by ingo#date#format#Preferred() can be set to a\r\nstrftime() format via:\r\n    let g:IngoLibrary_PreferredDateFormat = '%x'\r\n\r\nThe size of the file cache (in bytes) used by ingo#file#GetLines() can be set\r\nvia:\r\n    let g:IngoLibrary_FileCacheMaxSize = 1048576\r\n\r\nThe string used as a replacement for truncated text can be set via:\r\n    let g:IngoLibrary_TruncateEllipsis = \"\\u2026\"\r\n\r\nThe check for special windows in ingo#window#special#IsSpecialWindow() can be\r\ncustomized via a List of Expressions or Funcrefs that are passed the window\r\nnumber, and which should return a boolean flag. If any predicate is true, the\r\nwindow is deemed special.\r\n    let g:IngoLibrary_SpecialWindowPredicates =\r\n    \\   ['bufname(winbufnr(v:val)) =~# \"^\\\\[\\\\%(Scratch\\\\|clipboard\\\\)\\\\]$\"']\r\n\r\ningo#plugin#marks#Reserve() by default uses any unused mark. You can instead\r\nassign a fixed set of marks that will be available for plugins via:\r\n    let g:IngoLibrary_Marks = 'abcABC'\r\n\r\nSome special filenames are caught by BufNewFile,BufRead autocmds and\r\ntranslated into existing files. ingo#cmdargs#glob#Resolve() can be taught\r\nthose patterns by configuring a List of Funcrefs or expressions in\r\ng:IngoLibrary_SpecialFilePredicates that take a single filespec argument \/\r\nv:val and return whether this is an existing file. This will then correct the\r\nstatistics information returned by the function.\r\nBy default, includes any filespec that starts with a \"protocol:\/\" (e.g. scp:\/\/\r\nfor netrw), and also file:lnum[:column] special filenames if\r\nhttps:\/\/github.com\/bogado\/file-line is installed.\r\n\r\nThe ingo#text#InsertHere() function is often used to insert text at the cursor\r\nposition by plugins that don't want to offer separate insert \/ append mappings\r\n(comparable to |p|\/|P| pasting). The function tries to find a meaningful\r\ninsertion point. Its strategy can be tweaked via the following values:\r\n- insert1:  at the beginning of the line if the cursor is in column 1, else\r\n            appending after the character the cursor is on.\r\n- append$:  appending after the character if the cursor is at the end of the\r\n            line (with 'virtualedit' having \"onemore\": one beyond the end,\r\n            with \"all\": always insert before the cursor), else inserting\r\n            before the character the cursor is on.\r\n- insert:   always inserting before the character the cursor is on\r\n- append:   always appending after the character the cursor is on\r\n\r\nIf you use some operator-pending mappings as hooks into default motions (e.g.\r\n: or \/) that still maintain the original functionality,\r\ningo#query#get#Motion() can be instructed to ignore those mappings and instead\r\ntreat them as the built-in motions (i.e. still query the command-line or\r\nsearch pattern). Define those keys you want ignored as keys in a Dict (values\r\ndon't matter):\r\n    let g:IngoLibrary_QueryMotionIgnoredMotions = {':': 1, '\/': 1, '?': 1}\r\n\r\nIf you have custom operator-pending mappings that do some tricks like\r\nobtaining additional characters until they're done and moving the cursor,\r\ndefine those keys as keys, and an appendage pattern as value (or the empty\r\nString if there're no additional keys).\r\nThe appendage patterns will capture additional keys until either the pattern\r\ndoes not match any longer (the motion then is deemed invalid and aborts), or\r\nuntil the first capture group is non-empty (the motion then is deemed\r\ncomplete).\r\n    let g:IngoLibrary_QueryMotionCustomMotions = {'key': 'patter\\(n\\)'}\r\n\r\nMotions can be forced to be character- \/ line- \/ blockwise (forced-motion).\r\nIf you have mapped alternatives for v \/ V \/ CTRL-V, define them as keys in:\r\n    let g:IngoLibrary_QueryMotionCustomMotionModifiers = {\"\\<C-q>\": 1}\r\n\r\nIf you've remapped the c_CTRL-K trigger key for digraphs, you can adapt the\r\ndigraph detection by ingo#query#get#CharOrDigraph() and\r\ningo#query#get#[Valid]Char() to the changed mapping via:\r\n    let g:IngoLibrary_DigraphTriggerKey = \"\\<C-k>\"","install_details":"INSTALLATION\r\nThe code is hosted in a Git repo at\r\n    https:\/\/github.com\/inkarkat\/vim-ingo-library\r\nYou can use your favorite plugin manager, or \"git clone\" into a directory used\r\nfor Vim packages. Releases are on the \"stable\" branch, the latest unstable\r\ndevelopment snapshot on \"master\".\r\n\r\nThis script is also packaged as a vimball. If you have the \"gunzip\"\r\ndecompressor in your PATH, simply edit the *.vmb.gz package in Vim; otherwise,\r\ndecompress the archive first, e.g. using WinZip. Inside Vim, install by\r\nsourcing the vimball or via the :UseVimball command.\r\n    vim ingo-library*.vmb.gz\r\n    :so %\r\nTo uninstall, use the :RmVimball command.\r\n\r\nDEPENDENCIES\r\n- Requires Vim 7.0 or higher.","5":"INSTALLATION\r\nThe code is hosted in a Git repo at\r\n    https:\/\/github.com\/inkarkat\/vim-ingo-library\r\nYou can use your favorite plugin manager, or \"git clone\" into a directory used\r\nfor Vim packages. Releases are on the \"stable\" branch, the latest unstable\r\ndevelopment snapshot on \"master\".\r\n\r\nThis script is also packaged as a vimball. If you have the \"gunzip\"\r\ndecompressor in your PATH, simply edit the *.vmb.gz package in Vim; otherwise,\r\ndecompress the archive first, e.g. using WinZip. Inside Vim, install by\r\nsourcing the vimball or via the :UseVimball command.\r\n    vim ingo-library*.vmb.gz\r\n    :so %\r\nTo uninstall, use the :RmVimball command.\r\n\r\nDEPENDENCIES\r\n- Requires Vim 7.0 or higher.","first_name":"Ingo","6":"Ingo","last_name":"Karkat","7":"Karkat","releases":[{"0":"4433","vim_version":"7.0","1":"7.0","script_version":"1.044","2":"1.044","version_comment":"- Add ingo#cursor#IsBeyondEndOfLine() variant of ingo#cursor#IsAtEndOfLine().\r\n- ENH: Allow to customize the insertion point of ingo#text#InsertHere() via g:IngoLibrary_InsertHereStrategy.\r\n- CHG: Split ingo#subst#FirstSubstitution() into ingo#subst#FirstMatchingSubstitution() and ingo#subst#FirstChangingSubstitution().\r\n- Add ingo#text#IsInsert().\r\n- ingo#cmdargs#range#Parse(): BUG: Return [] as documented instead of ['', '', '', '', ''] on empty a:commandLine.\r\n- Add ingo\/plugin\/historyrecall.vim module.\r\n- Add ingo\/str\/remove.vim module.\r\n- Add ingo#lines#Delete() variant of ingo#lines#Replace().\r\n- ingo#plugin#register#{Set,PutContents}(): ENH: Also add the register contents to the search history when the target register is \"\/\".\r\n- Add ingo#query#motion#Get().\r\n- Add ingo#compat#getcharstr().\r\n- Add ingo#regexp#Anchored().\r\n- CHG: ingo#query#get#[Writable]Register(): Turn a:errorRegister and a:invalidRegisterExpr into option Dict values and add a:options.additionalValidExpr\r\n- Add ingo\/digraph.vim module.\r\n- Add ingo#query#get#CharOrDigraph().\r\n- ENH: ingo#query#get#[Valid]Char() takes digraphs by default; can be disabled via a:options.isAllowDigraphs = 0.\r\n- Add ingo#syntaxitem#HasHighlighting() from SameSyntaxMotion.vim.\r\n- Add ingo#cursor#IsOnWhitespace() and ingo#cursor#IsOnEmptyLine().\r\n- ingo#{area,text}#frompattern#Get(): ENH: Add cursorPos and additional arguments to context object, allow Predicate to influence returned result.\r\n- ingo#area#frompattern#Get(): BUG: a:matchCount uninitialized\r\n- Add ingo\/print\/highlighted.vim module (formerly unpublished separate EchoLine.vim autoload script).\r\n- ingo#option#listchars#Render(): ENH: Add a:options.tabWidth.\r\n- ingo#option#listchars#Render(): CHG: Deprecate a:isTextAtEnd argument, use a:options.isTextAtEnd now.\r\n- ingo#option#listchars#Render(): FIX: space rendering eclipses trail\r\n- ingo#option#listchars#Render(): ENH: Add a:options.isTextAtStart and render lead listchars option value (since Vim 8.2.2454).\r\n- ingo#print#highlighted#Line(): Use 'listchars' to render tabs and spaces, but now only if 'list' is on. Also support \"nbsp\", \"lead\", and \"eol\" options.\r\n- ingo#range#Get(): Don't clobber the search history.\r\n- ingo#range#lines#Get(): Allow a:options with fallback to the old single a:isGetAllRanges flag and don't clobber the search history by default, unless a:options.isKeepPatterns = 0.\r\n- ingo#ftplugin#onbufwinenter#Execute(): ENH: Also allow Funcref a:Action.\r\n- ingo#ftplugin#onbufwinenter#Execute(): ENH: Add a:when = \"delayed\".\r\n- ingo#escape#command#map[un]escape(), ingo#escape#mapping#keys(): Also convert between newline and <CR>.\r\n- Add ingo\/convert.vim module with ingo#convert#ToSingleLineString().","3":"- Add ingo#cursor#IsBeyondEndOfLine() variant of ingo#cursor#IsAtEndOfLine().\r\n- ENH: Allow to customize the insertion point of ingo#text#InsertHere() via g:IngoLibrary_InsertHereStrategy.\r\n- CHG: Split ingo#subst#FirstSubstitution() into ingo#subst#FirstMatchingSubstitution() and ingo#subst#FirstChangingSubstitution().\r\n- Add ingo#text#IsInsert().\r\n- ingo#cmdargs#range#Parse(): BUG: Return [] as documented instead of ['', '', '', '', ''] on empty a:commandLine.\r\n- Add ingo\/plugin\/historyrecall.vim module.\r\n- Add ingo\/str\/remove.vim module.\r\n- Add ingo#lines#Delete() variant of ingo#lines#Replace().\r\n- ingo#plugin#register#{Set,PutContents}(): ENH: Also add the register contents to the search history when the target register is \"\/\".\r\n- Add ingo#query#motion#Get().\r\n- Add ingo#compat#getcharstr().\r\n- Add ingo#regexp#Anchored().\r\n- CHG: ingo#query#get#[Writable]Register(): Turn a:errorRegister and a:invalidRegisterExpr into option Dict values and add a:options.additionalValidExpr\r\n- Add ingo\/digraph.vim module.\r\n- Add ingo#query#get#CharOrDigraph().\r\n- ENH: ingo#query#get#[Valid]Char() takes digraphs by default; can be disabled via a:options.isAllowDigraphs = 0.\r\n- Add ingo#syntaxitem#HasHighlighting() from SameSyntaxMotion.vim.\r\n- Add ingo#cursor#IsOnWhitespace() and ingo#cursor#IsOnEmptyLine().\r\n- ingo#{area,text}#frompattern#Get(): ENH: Add cursorPos and additional arguments to context object, allow Predicate to influence returned result.\r\n- ingo#area#frompattern#Get(): BUG: a:matchCount uninitialized\r\n- Add ingo\/print\/highlighted.vim module (formerly unpublished separate EchoLine.vim autoload script).\r\n- ingo#option#listchars#Render(): ENH: Add a:options.tabWidth.\r\n- ingo#option#listchars#Render(): CHG: Deprecate a:isTextAtEnd argument, use a:options.isTextAtEnd now.\r\n- ingo#option#listchars#Render(): FIX: space rendering eclipses trail\r\n- ingo#option#listchars#Render(): ENH: Add a:options.isTextAtStart and render lead listchars option value (since Vim 8.2.2454).\r\n- ingo#print#highlighted#Line(): Use 'listchars' to render tabs and spaces, but now only if 'list' is on. Also support \"nbsp\", \"lead\", and \"eol\" options.\r\n- ingo#range#Get(): Don't clobber the search history.\r\n- ingo#range#lines#Get(): Allow a:options with fallback to the old single a:isGetAllRanges flag and don't clobber the search history by default, unless a:options.isKeepPatterns = 0.\r\n- ingo#ftplugin#onbufwinenter#Execute(): ENH: Also allow Funcref a:Action.\r\n- ingo#ftplugin#onbufwinenter#Execute(): ENH: Add a:when = \"delayed\".\r\n- ingo#escape#command#map[un]escape(), ingo#escape#mapping#keys(): Also convert between newline and <CR>.\r\n- Add ingo\/convert.vim module with ingo#convert#ToSingleLineString().","package":"ingo-library-1.044.vmb.gz","4":"ingo-library-1.044.vmb.gz","src_id":"27985","5":"27985","creation_date":"1649482685","6":"1649482685"},{"0":"4433","vim_version":"7.0","1":"7.0","script_version":"1.043","2":"1.043","version_comment":"- Minor: Actually support no-argument form of ingo#query#get#[Writable]Register(), the documentation already states that the a:errorRegister defaults to the empty string.\r\n- Add ingo\/subs\/apply.vim module.\r\n- Add ingo#escape#file#CmdlineSpecialEscape().\r\n- Add ingo#buffer#IsWritable().\r\n- Deprecated: ingo#subst#expr#emulation#Substitute() is now available as a compat function ingo#compat#substitution#RecursiveSubstitutionExpression() because since Vim 8.0.20, the regexp engine is reentrant.\r\n- Add ingo#hlgroup#Get{Foreground,Background,}Color().\r\n- ingo#list#lcs#Find{All,Longest}Common(), ingo#subs#BraceCreation#FromList(): Add optional a:isIgnoreCase argument to ignore case differences when searching for common substrings.\r\n- Add ingo#window#special#HasOtherDiffWindow() variant of ingo#window#special#HasDiffWindow().\r\n- dirforaction: BUG: Passed filenames with escaped glob characters not handled correctly; need to use the unescaped filename for l:isAbsoluteFilename check.\r\n- dirforaction: ENH: Add a:parameters.completeFunctionHook.\r\n- Add ingo\/escape\/mapping.vim module.\r\n- Add ingo\/window\/iterate.vim module.\r\n- Add ingo#hlgroup#GetApplicableColorModes().\r\n- ingo#buffer#VisibleList(): ENH: Allow passing range of tab pages to be considered.\r\n- Add ingo\/list\/transform.vim module.\r\n- Add ingo#buffer#NameOrDefault().\r\n- Add ingo\/buffers.vim module.\r\n- Add ingo\/list\/reduce.vim module.\r\n- Add ingo#compat#getenv() and ingo#compat#setenv().\r\n- Add ingo#buffer#IsScratch().\r\n- Add ingo#encoding#IsUnicode().\r\n- Add ingo\/buffer\/network.vim module.\r\n- Add ingo\/ranges.vim module (originally from AdvancedSorters.vim).\r\n- ingo#file#GetLines(): Robustness: Empty a:filespec throws E17\r\n- Add ingo#subst#Recurringly().\r\n- Add ingo#text#Append() variant of ingo#text#Insert().\r\n- Add ingo\/text\/surroundings.vim modules.\r\n- Add ingo#regexp#EscapeLiteralReplacement().","3":"- Minor: Actually support no-argument form of ingo#query#get#[Writable]Register(), the documentation already states that the a:errorRegister defaults to the empty string.\r\n- Add ingo\/subs\/apply.vim module.\r\n- Add ingo#escape#file#CmdlineSpecialEscape().\r\n- Add ingo#buffer#IsWritable().\r\n- Deprecated: ingo#subst#expr#emulation#Substitute() is now available as a compat function ingo#compat#substitution#RecursiveSubstitutionExpression() because since Vim 8.0.20, the regexp engine is reentrant.\r\n- Add ingo#hlgroup#Get{Foreground,Background,}Color().\r\n- ingo#list#lcs#Find{All,Longest}Common(), ingo#subs#BraceCreation#FromList(): Add optional a:isIgnoreCase argument to ignore case differences when searching for common substrings.\r\n- Add ingo#window#special#HasOtherDiffWindow() variant of ingo#window#special#HasDiffWindow().\r\n- dirforaction: BUG: Passed filenames with escaped glob characters not handled correctly; need to use the unescaped filename for l:isAbsoluteFilename check.\r\n- dirforaction: ENH: Add a:parameters.completeFunctionHook.\r\n- Add ingo\/escape\/mapping.vim module.\r\n- Add ingo\/window\/iterate.vim module.\r\n- Add ingo#hlgroup#GetApplicableColorModes().\r\n- ingo#buffer#VisibleList(): ENH: Allow passing range of tab pages to be considered.\r\n- Add ingo\/list\/transform.vim module.\r\n- Add ingo#buffer#NameOrDefault().\r\n- Add ingo\/buffers.vim module.\r\n- Add ingo\/list\/reduce.vim module.\r\n- Add ingo#compat#getenv() and ingo#compat#setenv().\r\n- Add ingo#buffer#IsScratch().\r\n- Add ingo#encoding#IsUnicode().\r\n- Add ingo\/buffer\/network.vim module.\r\n- Add ingo\/ranges.vim module (originally from AdvancedSorters.vim).\r\n- ingo#file#GetLines(): Robustness: Empty a:filespec throws E17\r\n- Add ingo#subst#Recurringly().\r\n- Add ingo#text#Append() variant of ingo#text#Insert().\r\n- Add ingo\/text\/surroundings.vim modules.\r\n- Add ingo#regexp#EscapeLiteralReplacement().","package":"ingo-library-1.043.vmb.gz","4":"ingo-library-1.043.vmb.gz","src_id":"27942","5":"27942","creation_date":"1644039678","6":"1644039678"},{"0":"4433","vim_version":"7.0","1":"7.0","script_version":"1.042","2":"1.042","version_comment":"- BUG: ingo#join#Lines() inserts the separator before the line's last character when joining with a following empty line and ! a:isKeepSpace.\r\n- Support List of precisions in ingo#units#Format() and default to not showing a fraction for bytes in ingo#units#FormatBytesDecimal() and ingo#units#FormatBytesBinary() (as there are no fractional bytes).\r\n- Add ingo#regexp#collection#LargeRange().\r\n- Add ingo#text#InsertHere().\r\n- Expose ingo#mapmaker#OpfuncExpression(); it can avoid duplication of ...#Expression() functions in many plugins.\r\n- Add ingo\/change\/processed.vim module.\r\n- CHG: ingo#area#frompattern#GetCurrent() now takes optional arguments as Dictionary and adds a:options.firstLnum and a:options.lastLnum.\r\n- CHG: ingo#text#frompattern#GetCurrent() now take the optional a:currentPos as Dictionary and adds a:options.firstLnum, a:options.lastLnum, and a:options.returnValueOnNoSelection.","3":"- BUG: ingo#join#Lines() inserts the separator before the line's last character when joining with a following empty line and ! a:isKeepSpace.\r\n- Support List of precisions in ingo#units#Format() and default to not showing a fraction for bytes in ingo#units#FormatBytesDecimal() and ingo#units#FormatBytesBinary() (as there are no fractional bytes).\r\n- Add ingo#regexp#collection#LargeRange().\r\n- Add ingo#text#InsertHere().\r\n- Expose ingo#mapmaker#OpfuncExpression(); it can avoid duplication of ...#Expression() functions in many plugins.\r\n- Add ingo\/change\/processed.vim module.\r\n- CHG: ingo#area#frompattern#GetCurrent() now takes optional arguments as Dictionary and adds a:options.firstLnum and a:options.lastLnum.\r\n- CHG: ingo#text#frompattern#GetCurrent() now take the optional a:currentPos as Dictionary and adds a:options.firstLnum, a:options.lastLnum, and a:options.returnValueOnNoSelection.","package":"ingo-library-1.042.vmb.gz","4":"ingo-library-1.042.vmb.gz","src_id":"27262","5":"27262","creation_date":"1596498154","6":"1596498154"},{"0":"4433","vim_version":"7.0","1":"7.0","script_version":"1.041","2":"1.041","version_comment":"- Add ingo\/register\/pending.vim module.\r\n- ingo#regexp#EscapeLiteralText(): Make second argument (a:additionalEscapeCharacters) optional; many clients don't need this.\r\n- ingo#cmdargs#register#Parse{Ap,Pre}pendedWritableRegister(): ENH: Allow using the a:directSeparator default while supplying a:isPreferText by passing an empty List.\r\n- Introduce g:IngoLibrary_SpecialFilePredicates customization for ingo#cmdargs#glob#Resolve().\r\n- ingo#selection#Get{In,Ex}clusiveEndPos(): Prevent \"E951: \\% value too large\" by checking line length. This condition typically happens with a linewise selection (where the column is 2147483647).\r\n- Add ingo#window#quickfix#GetOtherList() variant of ingo#window#quickfix#GetList() that gets the quickfixType passed in.\r\n- Add ingo#window#quickfix#CmdPre() and ingo#window#quickfix#CmdPost().\r\n- Add optional a:Predicate argument to ingo#area#frompattern#Get() and ingo#text#frompattern#Get(). Additionally, the a:isOnlyFirstMatch and a:isUnique arguments are optional now, too.\r\n- Add ingo#str#trcd() variant of ingo#str#trd().\r\n- Add ingo#plugin#cmdcomplete#dirforaction#setup().\r\n- Add ingo#fs#path#IsPath().\r\n- ingo#plugin#cmdcomplete#dirforaction#setup(): ENH: Use special completion that only returns directories if a:parameters.action is \"chdir\".\r\n- Add ingo\/regexp\/parse.vim module.\r\n- CHG: Move ingo#regexp#multi#Expr() to ingo#regexp#parse#MultiExpr().\r\n- ingo#regexp#deconstruct#ToQuasiLiteral() also covers new ingo#regexp#deconstruct#TranslateSingleCharacterAtoms() and ingo#regexp#deconstruct#RemoveOtherAtoms().\r\n- Add ingo\/list\/merge.vim module.\r\n- Add ingo#collections#{CharacterCount,StringDisplayWidth}{Asc,Desc}Sort().\r\n- FIX: ingo#smartcase#IsSmartCasePattern() and ingo#smartcase#Undo() now also handle the smartcased single all-lower or -uppercase alphabetic word special case.","3":"- Add ingo\/register\/pending.vim module.\r\n- ingo#regexp#EscapeLiteralText(): Make second argument (a:additionalEscapeCharacters) optional; many clients don't need this.\r\n- ingo#cmdargs#register#Parse{Ap,Pre}pendedWritableRegister(): ENH: Allow using the a:directSeparator default while supplying a:isPreferText by passing an empty List.\r\n- Introduce g:IngoLibrary_SpecialFilePredicates customization for ingo#cmdargs#glob#Resolve().\r\n- ingo#selection#Get{In,Ex}clusiveEndPos(): Prevent \"E951: \\% value too large\" by checking line length. This condition typically happens with a linewise selection (where the column is 2147483647).\r\n- Add ingo#window#quickfix#GetOtherList() variant of ingo#window#quickfix#GetList() that gets the quickfixType passed in.\r\n- Add ingo#window#quickfix#CmdPre() and ingo#window#quickfix#CmdPost().\r\n- Add optional a:Predicate argument to ingo#area#frompattern#Get() and ingo#text#frompattern#Get(). Additionally, the a:isOnlyFirstMatch and a:isUnique arguments are optional now, too.\r\n- Add ingo#str#trcd() variant of ingo#str#trd().\r\n- Add ingo#plugin#cmdcomplete#dirforaction#setup().\r\n- Add ingo#fs#path#IsPath().\r\n- ingo#plugin#cmdcomplete#dirforaction#setup(): ENH: Use special completion that only returns directories if a:parameters.action is \"chdir\".\r\n- Add ingo\/regexp\/parse.vim module.\r\n- CHG: Move ingo#regexp#multi#Expr() to ingo#regexp#parse#MultiExpr().\r\n- ingo#regexp#deconstruct#ToQuasiLiteral() also covers new ingo#regexp#deconstruct#TranslateSingleCharacterAtoms() and ingo#regexp#deconstruct#RemoveOtherAtoms().\r\n- Add ingo\/list\/merge.vim module.\r\n- Add ingo#collections#{CharacterCount,StringDisplayWidth}{Asc,Desc}Sort().\r\n- FIX: ingo#smartcase#IsSmartCasePattern() and ingo#smartcase#Undo() now also handle the smartcased single all-lower or -uppercase alphabetic word special case.","package":"ingo-library-1.041.vmb.gz","4":"ingo-library-1.041.vmb.gz","src_id":"27073","5":"27073","creation_date":"1584049366","6":"1584049366"},{"0":"4433","vim_version":"7.0","1":"7.0","script_version":"1.040","2":"1.040","version_comment":"- Add ingo#str#TrimTrailing() variant of ingo#str#Trim().\r\n- Add ingo#date#format#FilesystemCompatibleTimestamp() variant.\r\n- Add ingo#window#quickfix#SetOtherList() generalization of ingo#window#quickfix#SetList().\r\n- Add ingo#window#quickfix#GetName() and ingo#window#quickfix#GetPrefix().\r\n- Add ingo#plugin#cmdcomplete#MakeFirstArgumentFixedListCompleteFunc() variant of ingo#plugin#cmdcomplete#MakeFixedListCompleteFunc().\r\n- Add ingo#change#virtcols#Get(), a variant of ingo#selection#virtcols#Get().\r\n- Add ingo\/plugin\/register.vim module.","3":"- Add ingo#str#TrimTrailing() variant of ingo#str#Trim().\r\n- Add ingo#date#format#FilesystemCompatibleTimestamp() variant.\r\n- Add ingo#window#quickfix#SetOtherList() generalization of ingo#window#quickfix#SetList().\r\n- Add ingo#window#quickfix#GetName() and ingo#window#quickfix#GetPrefix().\r\n- Add ingo#plugin#cmdcomplete#MakeFirstArgumentFixedListCompleteFunc() variant of ingo#plugin#cmdcomplete#MakeFixedListCompleteFunc().\r\n- Add ingo#change#virtcols#Get(), a variant of ingo#selection#virtcols#Get().\r\n- Add ingo\/plugin\/register.vim module.","package":"ingo-library-1.040.vmb.gz","4":"ingo-library-1.040.vmb.gz","src_id":"26804","5":"26804","creation_date":"1572549575","6":"1572549575"},{"0":"4433","vim_version":"7.0","1":"7.0","script_version":"1.039","2":"1.039","version_comment":"- Add ingo#date#format#Epoch().\r\n- Add ingo#collections#SortOnFirstListElement() and ingo#collections#SortOnSecondListElement().\r\n- Add ingo#range#sort#AscendingByStartLnum().\r\n- Add ingo#buffer#scratch#CreateWithWriter().\r\n- Add ingo#register#IsWritable().\r\n- ingo\/window\/locate.vim: ENH: Support special a:winVarName of \"bufnr\" that allows searching for bufnr instead of window-local variables.\r\n- ingo#window#switches#Win{Save,Restore}CurrentBuffer(): ENH: Also record \/ search in other tabpages if the new a:isSaveTabPage \/ a:isSearchTabPages is true.\r\n- Add ingo#window#special#HasDiffWindow().\r\n- Add ingo#funcref#UnaryIdentity().\r\n- Add ingo#pos#Sort().\r\n- Add ingo#area#frompattern#GetCurrent() and ingo#text#frompattern#GetCurrent(), variants of ...#GetAroundHere().\r\n- Add ingo#selection#Get{Ex,In}clusiveEndPos().\r\n- Add ingo#text#Replace(), a more generic variant of ingo#text#Remove().\r\n- Add optional a:NextFilenameFuncref to ingo#buffer#scratch#Create[WithWriter]().\r\n- ENH: Also support Funcref a:contentsCommand \/ a:scratchCommand for ingo#buffer#generate#Create() and ingo#buffer#scratch#Create[WithWriter]().\r\n- Add ingo#buffer#scratch#converted#Create() to convert buffer contents to a scratch buffer with the possibility to sync back and ingo#ftplugin#converter#builder#EditAsFiletype() that can be used by filetype plugins to edit one filetype in an intermediate different format.\r\n- ENH: Allow to preset reserved marks for ingo#plugin#marks#Reserve() via g:IngoLibrary_Marks.\r\n- ENH: ingo#selection#virtcols#Get() adds an effectiveEndVirtCol attribute.\r\n- Add ingo#selection#virtcols#GetLimitingPatterns().\r\n- Add ingo#regexp#virtcols#StartAnchorPattern() and ingo#regexp#virtcols#EndAnchorPattern().\r\n- ENH: ingo#plugin#cmd#withpattern#CommandWithPattern(): Also support a:CommandTemplate Funcref argument.\r\n- Add ingo#actions#ExecuteWithValOrFunc() variant of ingo#actions#EvaluateWithValOrFunc() that :executes the Action instead of eval()ing it.\r\n- FIX: ingo#register#accumulate#ExecuteOrFunc(): Need to use ingo#actions#ExecuteWithValOrFunc(), not ingo#actions#EvaluateWithValOrFunc().\r\n- ENH: ingo#cmdrangeconverter#LineToBufferRange(): Also allow Funcref argument for a function that takes the converted range.\r\n- Add ingo\/options\/listchars.vim module.","3":"- Add ingo#date#format#Epoch().\r\n- Add ingo#collections#SortOnFirstListElement() and ingo#collections#SortOnSecondListElement().\r\n- Add ingo#range#sort#AscendingByStartLnum().\r\n- Add ingo#buffer#scratch#CreateWithWriter().\r\n- Add ingo#register#IsWritable().\r\n- ingo\/window\/locate.vim: ENH: Support special a:winVarName of \"bufnr\" that allows searching for bufnr instead of window-local variables.\r\n- ingo#window#switches#Win{Save,Restore}CurrentBuffer(): ENH: Also record \/ search in other tabpages if the new a:isSaveTabPage \/ a:isSearchTabPages is true.\r\n- Add ingo#window#special#HasDiffWindow().\r\n- Add ingo#funcref#UnaryIdentity().\r\n- Add ingo#pos#Sort().\r\n- Add ingo#area#frompattern#GetCurrent() and ingo#text#frompattern#GetCurrent(), variants of ...#GetAroundHere().\r\n- Add ingo#selection#Get{Ex,In}clusiveEndPos().\r\n- Add ingo#text#Replace(), a more generic variant of ingo#text#Remove().\r\n- Add optional a:NextFilenameFuncref to ingo#buffer#scratch#Create[WithWriter]().\r\n- ENH: Also support Funcref a:contentsCommand \/ a:scratchCommand for ingo#buffer#generate#Create() and ingo#buffer#scratch#Create[WithWriter]().\r\n- Add ingo#buffer#scratch#converted#Create() to convert buffer contents to a scratch buffer with the possibility to sync back and ingo#ftplugin#converter#builder#EditAsFiletype() that can be used by filetype plugins to edit one filetype in an intermediate different format.\r\n- ENH: Allow to preset reserved marks for ingo#plugin#marks#Reserve() via g:IngoLibrary_Marks.\r\n- ENH: ingo#selection#virtcols#Get() adds an effectiveEndVirtCol attribute.\r\n- Add ingo#selection#virtcols#GetLimitingPatterns().\r\n- Add ingo#regexp#virtcols#StartAnchorPattern() and ingo#regexp#virtcols#EndAnchorPattern().\r\n- ENH: ingo#plugin#cmd#withpattern#CommandWithPattern(): Also support a:CommandTemplate Funcref argument.\r\n- Add ingo#actions#ExecuteWithValOrFunc() variant of ingo#actions#EvaluateWithValOrFunc() that :executes the Action instead of eval()ing it.\r\n- FIX: ingo#register#accumulate#ExecuteOrFunc(): Need to use ingo#actions#ExecuteWithValOrFunc(), not ingo#actions#EvaluateWithValOrFunc().\r\n- ENH: ingo#cmdrangeconverter#LineToBufferRange(): Also allow Funcref argument for a function that takes the converted range.\r\n- Add ingo\/options\/listchars.vim module.","package":"ingo-library-1.039.vmb.gz","4":"ingo-library-1.039.vmb.gz","src_id":"26741","5":"26741","creation_date":"1568174691","6":"1568174691"},{"0":"4433","vim_version":"7.0","1":"7.0","script_version":"1.038","2":"1.038","version_comment":"- ingo#compat#maparg() escaping didn't consider <; in fact, it needs to escape stand-alone < and escaped \\<, but not proper key notations like <C-CR>.\r\n- FIX: Make ingo#cmdline#showmode#TemporaryNoShowMode() work again.\r\n- Factor out ingo#msg#MsgFromCustomException().\r\n- Add ingo#regexp#MakeWholeWordOrWORDSearch() variant.\r\n- Add ingo#pos#Compare(), useful for sort().\r\n- FIX: Handle corner cases in ingo#join#Lines(). Return join success. Also do proper counting in ingo#join#Ranges().\r\n- Add ingo#join#Range() variant of ingo#join#Ranges().\r\n- FIX: ingo#comments#SplitAll(): isBlankRequired is missing from the returned List when there's no comment.\r\n- Add ingo\/comments\/indent.vim module.","3":"- ingo#compat#maparg() escaping didn't consider <; in fact, it needs to escape stand-alone < and escaped \\<, but not proper key notations like <C-CR>.\r\n- FIX: Make ingo#cmdline#showmode#TemporaryNoShowMode() work again.\r\n- Factor out ingo#msg#MsgFromCustomException().\r\n- Add ingo#regexp#MakeWholeWordOrWORDSearch() variant.\r\n- Add ingo#pos#Compare(), useful for sort().\r\n- FIX: Handle corner cases in ingo#join#Lines(). Return join success. Also do proper counting in ingo#join#Ranges().\r\n- Add ingo#join#Range() variant of ingo#join#Ranges().\r\n- FIX: ingo#comments#SplitAll(): isBlankRequired is missing from the returned List when there's no comment.\r\n- Add ingo\/comments\/indent.vim module.","package":"ingo-library-1.038.vmb.gz","4":"ingo-library-1.038.vmb.gz","src_id":"26529","5":"26529","creation_date":"1560134961","6":"1560134961"},{"0":"4433","vim_version":"7.0","1":"7.0","script_version":"1.037","2":"1.037","version_comment":"- Add ingo#dict#Make() (analog to ingo#list#Make()).","3":"- Add ingo#dict#Make() (analog to ingo#list#Make()).","package":"ingo-library-1.037.vmb.gz","4":"ingo-library-1.037.vmb.gz","src_id":"26438","5":"26438","creation_date":"1553836559","6":"1553836559"},{"0":"4433","vim_version":"7.0","1":"7.0","script_version":"1.036","2":"1.036","version_comment":"- FIX: ingo#strdisplaywidth#strleft includes multi-width character that straddles the specified width. Need to exclude this one.\r\n- Add ingo#strdisplaywidth#pad#Repeat[Exact]().\r\n- Make Unix date command used in ingo#date#epoch#ConvertTo() configurable via g:IngoLibrary_DateCommand.\r\n- ENH: Allow passing of a:truncationIndicator to ingo#avoidprompt#Truncate[To]().\r\n- Add ingo#fs#path#split#TruncateTo().\r\n- Add ingo#str#TrimPattern() variant of ingo#str#Trim().\r\n- Add ingo#date#epoch#Now().\r\n- Add ingo#date#strftime().\r\n- Add ingo#compat#trim().\r\n- Add ingo#buffer#locate#OtherWindowWithSameBuffer().\r\n- Add ingo#search#timelimited#FirstPatternThatMatchesInBuffer().\r\n- Add optional a:isPreferText flag to ingo#cmdargs#register#Parse{Prepended,Appended}WritableRegister().\r\n- Add ingo#comments#GetSplitIndentPattern() variant of ingo#comments#SplitIndentAndText() that just returns the pattern.\r\n- Extract ingo#cmdrange#FromCount() from ingo#cmdrangeconverter#LineToBufferRange().\r\n- Add ingo\/plugin\/cmd\/withpattern.vim module.\r\n- Add ingo\/view.vim module.\r\n- Add ingo#compat#commands#ForceSynchronousFeedkeys().\r\n- Add ingo\/plugin\/persistence.vim module; implementation based on my mark.vim plugin.\r\n- Add ingo#collections#SortOnOneAttribute(), ingo#collections#PrioritySort(), and ingo#collections#SortOnTwoAttributes().\r\n- Add ingo\/collections\/recursive.vim module.\r\n- ENH: ingo#cmdargs#range#Parse(): Add a:options.isOnlySingleAddress flag.\r\n- ENH: Add ingo#cmdargs#range#ParsePrependedRange().\r\n- Minor fixes to ingo#query#confirm#AutoAccelerators().\r\n- Expose ingo#collections#fromsplit#MapOne().\r\n- Add function\/uniquify.vim module.\r\n- Add ingo#compat#FromKey() for the reversing of ingo#compat#DictKey().\r\n- Add ingo#collections#SortOnOneListElement(), a variant of ingo#collections#SortOnOneAttribute().\r\n- Add ingo#regexp#MakeWholeWORDSearch() variant of ingo#regexp#MakeWholeWordSearch().\r\n- Add ingo\/file.vim module.\r\n- Add ingo#cmdargs#pattern#PatternExpr().\r\n- BUG: ingo#text#replace#Between() and ingo#text#replace#Area() mistakenly update current line instead of passed position.\r\n- BUG: ingo#text#replace#Between() and ingo#text#replace#Area() cause \"E684: list index out of range: 0\" when the replacement text is empty.\r\n- FIX: Off-by-one in ingo#area#IsEmpty(). Also check for invalid area.\r\n- Add ingo#area#EmptyArea().\r\n- FIX: Make ingo#pos#Before() return column 0 if passed a position with column 1; this matches the behavior of ingo#pos#After(), which also returns a non-existent position directly after the last character, and this fits in well with the area functions.\r\n- Add ingo#regexp#deconstruct#{Translate,Remove}CharacterClasses(), ingo#regexp#deconstruct#TranslateNumberEscapes(), ingo#regexp#deconstruct#TranslateBranches()  and include all translations in ingo#regexp#deconstruct#ToQuasiLiteral().\r\n- FIX: Don't match optionally matched atoms \\%[] in ingo#regexp#collection#Expr().\r\n- ENH: Add a:option.isCapture to ingo#regexp#collection#Expr().","3":"- FIX: ingo#strdisplaywidth#strleft includes multi-width character that straddles the specified width. Need to exclude this one.\r\n- Add ingo#strdisplaywidth#pad#Repeat[Exact]().\r\n- Make Unix date command used in ingo#date#epoch#ConvertTo() configurable via g:IngoLibrary_DateCommand.\r\n- ENH: Allow passing of a:truncationIndicator to ingo#avoidprompt#Truncate[To]().\r\n- Add ingo#fs#path#split#TruncateTo().\r\n- Add ingo#str#TrimPattern() variant of ingo#str#Trim().\r\n- Add ingo#date#epoch#Now().\r\n- Add ingo#date#strftime().\r\n- Add ingo#compat#trim().\r\n- Add ingo#buffer#locate#OtherWindowWithSameBuffer().\r\n- Add ingo#search#timelimited#FirstPatternThatMatchesInBuffer().\r\n- Add optional a:isPreferText flag to ingo#cmdargs#register#Parse{Prepended,Appended}WritableRegister().\r\n- Add ingo#comments#GetSplitIndentPattern() variant of ingo#comments#SplitIndentAndText() that just returns the pattern.\r\n- Extract ingo#cmdrange#FromCount() from ingo#cmdrangeconverter#LineToBufferRange().\r\n- Add ingo\/plugin\/cmd\/withpattern.vim module.\r\n- Add ingo\/view.vim module.\r\n- Add ingo#compat#commands#ForceSynchronousFeedkeys().\r\n- Add ingo\/plugin\/persistence.vim module; implementation based on my mark.vim plugin.\r\n- Add ingo#collections#SortOnOneAttribute(), ingo#collections#PrioritySort(), and ingo#collections#SortOnTwoAttributes().\r\n- Add ingo\/collections\/recursive.vim module.\r\n- ENH: ingo#cmdargs#range#Parse(): Add a:options.isOnlySingleAddress flag.\r\n- ENH: Add ingo#cmdargs#range#ParsePrependedRange().\r\n- Minor fixes to ingo#query#confirm#AutoAccelerators().\r\n- Expose ingo#collections#fromsplit#MapOne().\r\n- Add function\/uniquify.vim module.\r\n- Add ingo#compat#FromKey() for the reversing of ingo#compat#DictKey().\r\n- Add ingo#collections#SortOnOneListElement(), a variant of ingo#collections#SortOnOneAttribute().\r\n- Add ingo#regexp#MakeWholeWORDSearch() variant of ingo#regexp#MakeWholeWordSearch().\r\n- Add ingo\/file.vim module.\r\n- Add ingo#cmdargs#pattern#PatternExpr().\r\n- BUG: ingo#text#replace#Between() and ingo#text#replace#Area() mistakenly update current line instead of passed position.\r\n- BUG: ingo#text#replace#Between() and ingo#text#replace#Area() cause \"E684: list index out of range: 0\" when the replacement text is empty.\r\n- FIX: Off-by-one in ingo#area#IsEmpty(). Also check for invalid area.\r\n- Add ingo#area#EmptyArea().\r\n- FIX: Make ingo#pos#Before() return column 0 if passed a position with column 1; this matches the behavior of ingo#pos#After(), which also returns a non-existent position directly after the last character, and this fits in well with the area functions.\r\n- Add ingo#regexp#deconstruct#{Translate,Remove}CharacterClasses(), ingo#regexp#deconstruct#TranslateNumberEscapes(), ingo#regexp#deconstruct#TranslateBranches()  and include all translations in ingo#regexp#deconstruct#ToQuasiLiteral().\r\n- FIX: Don't match optionally matched atoms \\%[] in ingo#regexp#collection#Expr().\r\n- ENH: Add a:option.isCapture to ingo#regexp#collection#Expr().","package":"ingo-library-1.036.vmb.gz","4":"ingo-library-1.036.vmb.gz","src_id":"26421","5":"26421","creation_date":"1552875576","6":"1552875576"},{"0":"4433","vim_version":"7.0","1":"7.0","script_version":"1.035","2":"1.035","version_comment":"- Add ingo#compat#commands#NormalWithCount().\r\n- Add ingo#compat#haslocaldir().\r\n- Add ingo\/workingdir.vim module.\r\n- Add ingo\/selection\/virtcols.vim module.\r\n- Add ingo\/str\/list.vim module.\r\n- Add ingo#funcref#AsString().\r\n- Add ingo#compat#execute().\r\n- Add ingo#option#GetBinaryOptionValue().\r\n- Add ingo\/buffer\/ephemeral.vim module.\r\n- Add ingo\/lists\/find.vim module.\r\n- Add ingo\/folds\/containment.vim module.\r\n- Add ingo\/ftplugin\/setting.vim module.\r\n- Extract generic ingo#plugin#cmdcomplete#MakeCompleteFunc().\r\n- Add ingo#fs#path#split#StartsWith() (we already had ingo#fs#path#split#EndsWith()).\r\n- Add ingo#fs#path#Canonicalize().\r\n- Add ingo#avoidprompt#EchoMsg() and ingo#avoidprompt#EchoMsgAsSingleLine().\r\n- Tweak ingo#avoidprompt#MaxLength() algorithm; empirical testing showed that 1 more needs to be subtracted if :set noshowcmd ruler. Thanks to an9wer for making me aware of this.\r\n- CHG: Move ingo#list#Matches() to ingo#list#pattern#AllItemsMatch(). The previous name wasn't very clear.\r\n- Add ingo#list#pattern#{First,All}Match[Index]() functions.\r\n- ingo#query#{get#Number,fromlist#Query}(): ENH: Also support number entry with leading zeros\r\n- ingo#query#fromlist#Query(): BUG: Cannot conclude multi-digit entry with <Enter>\r\n- ingo#query#fromlist#Query(): BUG: Typing non-accellerator non-number characters are treated as literal \"0\"\r\n- Add ingo\/lists.vim module.\r\n- Add ingo\/regexp\/capture.vim module.\r\n- Add ingo#cmdargs#substitute#GetFlags().\r\n- Add ingo#subst#Indexed().\r\n- Add ingo#regexp#split#PrefixGroupsSuffix().\r\n- Add ingo#collections#SplitIntoMatches().\r\n- Add ingo#regexp#collection#ToBranches().\r\n- Add ingo\/regexp\/{deconstruct,length,multi} modules.\r\n- Add ingo#range#Is{In,Out}side().\r\n- Add ingo\/cursor\/keep.vim module.\r\n- Add ingo#folds#GetOpenFoldRange().\r\n- ingo#compat#commands#keeppatterns(): Don't remove the last search pattern when the search history wasn't modified. Allow to force compatibility function via g:IngoLibrary_CompatFor here, too.\r\n- Add ingo#regexp#split#GlobalFlags().\r\n- Add ingo#regexp#IsValid() (from mark.vim plugin).\r\n- Add ingo#matches#Any() and ingo#matches#All().\r\n- Add ingo#list#split#RemoveFromStartWhilePredicate().\r\n- Add ingo#cmdargs#file#FilterFileOptions() variant of ingo#cmdargs#file#FilterFileOptionsAndCommands()\r\n- Add ingo#cmdargs#file#FileOptionsAndCommandsToEscapedExCommandLine() and combining ingo#cmdargs#file#FilterFileOptionsToEscaped() and ingo#cmdargs#file#FilterFileOptionsAndCommandsToEscaped().\r\n- Add ingo#list#AddNonEmpty().","3":"- Add ingo#compat#commands#NormalWithCount().\r\n- Add ingo#compat#haslocaldir().\r\n- Add ingo\/workingdir.vim module.\r\n- Add ingo\/selection\/virtcols.vim module.\r\n- Add ingo\/str\/list.vim module.\r\n- Add ingo#funcref#AsString().\r\n- Add ingo#compat#execute().\r\n- Add ingo#option#GetBinaryOptionValue().\r\n- Add ingo\/buffer\/ephemeral.vim module.\r\n- Add ingo\/lists\/find.vim module.\r\n- Add ingo\/folds\/containment.vim module.\r\n- Add ingo\/ftplugin\/setting.vim module.\r\n- Extract generic ingo#plugin#cmdcomplete#MakeCompleteFunc().\r\n- Add ingo#fs#path#split#StartsWith() (we already had ingo#fs#path#split#EndsWith()).\r\n- Add ingo#fs#path#Canonicalize().\r\n- Add ingo#avoidprompt#EchoMsg() and ingo#avoidprompt#EchoMsgAsSingleLine().\r\n- Tweak ingo#avoidprompt#MaxLength() algorithm; empirical testing showed that 1 more needs to be subtracted if :set noshowcmd ruler. Thanks to an9wer for making me aware of this.\r\n- CHG: Move ingo#list#Matches() to ingo#list#pattern#AllItemsMatch(). The previous name wasn't very clear.\r\n- Add ingo#list#pattern#{First,All}Match[Index]() functions.\r\n- ingo#query#{get#Number,fromlist#Query}(): ENH: Also support number entry with leading zeros\r\n- ingo#query#fromlist#Query(): BUG: Cannot conclude multi-digit entry with <Enter>\r\n- ingo#query#fromlist#Query(): BUG: Typing non-accellerator non-number characters are treated as literal \"0\"\r\n- Add ingo\/lists.vim module.\r\n- Add ingo\/regexp\/capture.vim module.\r\n- Add ingo#cmdargs#substitute#GetFlags().\r\n- Add ingo#subst#Indexed().\r\n- Add ingo#regexp#split#PrefixGroupsSuffix().\r\n- Add ingo#collections#SplitIntoMatches().\r\n- Add ingo#regexp#collection#ToBranches().\r\n- Add ingo\/regexp\/{deconstruct,length,multi} modules.\r\n- Add ingo#range#Is{In,Out}side().\r\n- Add ingo\/cursor\/keep.vim module.\r\n- Add ingo#folds#GetOpenFoldRange().\r\n- ingo#compat#commands#keeppatterns(): Don't remove the last search pattern when the search history wasn't modified. Allow to force compatibility function via g:IngoLibrary_CompatFor here, too.\r\n- Add ingo#regexp#split#GlobalFlags().\r\n- Add ingo#regexp#IsValid() (from mark.vim plugin).\r\n- Add ingo#matches#Any() and ingo#matches#All().\r\n- Add ingo#list#split#RemoveFromStartWhilePredicate().\r\n- Add ingo#cmdargs#file#FilterFileOptions() variant of ingo#cmdargs#file#FilterFileOptionsAndCommands()\r\n- Add ingo#cmdargs#file#FileOptionsAndCommandsToEscapedExCommandLine() and combining ingo#cmdargs#file#FilterFileOptionsToEscaped() and ingo#cmdargs#file#FilterFileOptionsAndCommandsToEscaped().\r\n- Add ingo#list#AddNonEmpty().","package":"ingo-library-1.035.vmb.gz","4":"ingo-library-1.035.vmb.gz","src_id":"26238","5":"26238","creation_date":"1538254658","6":"1538254658"},{"0":"4433","vim_version":"7.0","1":"7.0","script_version":"1.034","2":"1.034","version_comment":"- Add ingo\/regexp\/split.vim module.\r\n- Add ingo#folds#LastVisibleLine(), ingo#folds#NextClosedLine(), ingo#folds#LastClosedLine() variants of existing ingo#folds#NextVisibleLine().\r\n- Add ingo\/plugin\/rendered.vim module.\r\n- Add ingo\/change.vim module.\r\n- Add ingo#undo#IsEnabled().\r\n- Add ingo#str#split#AtPrefix() and ingo#str#split#AtSuffix().\r\n- Add ingo\/lnum.vim module.\r\n- Add ingo#text#GetCharVirtCol().\r\n- Add ingo#compat#matchstrpos().","3":"- Add ingo\/regexp\/split.vim module.\r\n- Add ingo#folds#LastVisibleLine(), ingo#folds#NextClosedLine(), ingo#folds#LastClosedLine() variants of existing ingo#folds#NextVisibleLine().\r\n- Add ingo\/plugin\/rendered.vim module.\r\n- Add ingo\/change.vim module.\r\n- Add ingo#undo#IsEnabled().\r\n- Add ingo#str#split#AtPrefix() and ingo#str#split#AtSuffix().\r\n- Add ingo\/lnum.vim module.\r\n- Add ingo#text#GetCharVirtCol().\r\n- Add ingo#compat#matchstrpos().","package":"ingo-library-1.034.vmb.gz","4":"ingo-library-1.034.vmb.gz","src_id":"25826","5":"25826","creation_date":"1518553017","6":"1518553017"},{"0":"4433","vim_version":"7.0","1":"7.0","script_version":"1.033","2":"1.033","version_comment":"- Add ingo\/subs\/BraceCreation.vim and ingo\/subs\/BraceExpansion.vim modules.\r\n- Add ingo#query#get#WritableRegister() variant of ingo#query#get#Register().\r\n- Add ingo#str#find#StartIndex().\r\n- Fix recursive invocations of ingo#buffer#generate#Create().\r\n- Add ingo#mbyte#virtcol#GetColOfVirtCol().\r\n- Expose ingo#plugin#marks#FindUnused(), and have it optionally take the considered marks.\r\n- Add ingo#plugin#marks#Reuse().\r\n- BUG: ingo#syntaxitem#IsOnSyntax() considers empty a:stopItemPattern as unconditional stop.\r\n- Add ingo#regexp#build#UnderCursor().\r\n- Add ingo#escape#command#mapeval().\r\n- Add ingo#range#IsEntireBuffer().\r\n- Add ingo\/compat\/commands.vim module.\r\n- Add ingo#register#All() and ingo#register#Writable() (so that this information doesn't have to be duplicated any longer).\r\n- FIX: ingo#query#get#WritableRegister() doesn't consider all writable registers (-_* are writable, too).\r\n- Add ingo\/register\/accumulate.vim module.\r\n- Add ingo\/tabpage.vim module.\r\n- Add ingo#list#NonEmpty() and ingo#list#JoinNonEmpty().\r\n- Factor out ingo#filetype#GetPrimary() from ingo#filetype#IsPrimary().\r\n- Add ingo#fs#path#split#ChangeBasePath().\r\n- ENH: ingo#funcref#ToString() returns non-Funcref argument as is (instead of empty String). This allows to transparently handle function names (as String), too.\r\n- ingo#event#Trigger(): Temporarily disable modeline processing in compatibility implementation.\r\n- Add ingo#event#TriggerEverywhere() and ingo#event#TriggerEverywhereCustom() compatibility wrappers for :doautoall <nomodeline>.","3":"- Add ingo\/subs\/BraceCreation.vim and ingo\/subs\/BraceExpansion.vim modules.\r\n- Add ingo#query#get#WritableRegister() variant of ingo#query#get#Register().\r\n- Add ingo#str#find#StartIndex().\r\n- Fix recursive invocations of ingo#buffer#generate#Create().\r\n- Add ingo#mbyte#virtcol#GetColOfVirtCol().\r\n- Expose ingo#plugin#marks#FindUnused(), and have it optionally take the considered marks.\r\n- Add ingo#plugin#marks#Reuse().\r\n- BUG: ingo#syntaxitem#IsOnSyntax() considers empty a:stopItemPattern as unconditional stop.\r\n- Add ingo#regexp#build#UnderCursor().\r\n- Add ingo#escape#command#mapeval().\r\n- Add ingo#range#IsEntireBuffer().\r\n- Add ingo\/compat\/commands.vim module.\r\n- Add ingo#register#All() and ingo#register#Writable() (so that this information doesn't have to be duplicated any longer).\r\n- FIX: ingo#query#get#WritableRegister() doesn't consider all writable registers (-_* are writable, too).\r\n- Add ingo\/register\/accumulate.vim module.\r\n- Add ingo\/tabpage.vim module.\r\n- Add ingo#list#NonEmpty() and ingo#list#JoinNonEmpty().\r\n- Factor out ingo#filetype#GetPrimary() from ingo#filetype#IsPrimary().\r\n- Add ingo#fs#path#split#ChangeBasePath().\r\n- ENH: ingo#funcref#ToString() returns non-Funcref argument as is (instead of empty String). This allows to transparently handle function names (as String), too.\r\n- ingo#event#Trigger(): Temporarily disable modeline processing in compatibility implementation.\r\n- Add ingo#event#TriggerEverywhere() and ingo#event#TriggerEverywhereCustom() compatibility wrappers for :doautoall <nomodeline>.","package":"ingo-library-1.033.vmb.gz","4":"ingo-library-1.033.vmb.gz","src_id":"25713","5":"25713","creation_date":"1513243647","6":"1513243647"},{"0":"4433","vim_version":"7.0","1":"7.0","script_version":"1.032","2":"1.032","version_comment":"- ingo#query#get#{Register,Mark}(): Avoid throwing E523 on invalid user input when executed e.g. from within a |:map-expr|.\r\n- Add ingo\/subst\/replacement.vim module with functions originally in PatternsOnText.vim (vimscript #4602).\r\n- Add ingo\/lines\/empty.vim module.\r\n- CHG: Rename ingo#str#split#First() to ingo#str#split#MatchFirst() and add ingo#str#split#StrFirst() variant that uses a fixed string, not a pattern.\r\n- Add ingo\/list\/lcs.vim module.\r\n- Add ingo#list#IsEmpty().\r\n- Add ingo\/collection\/find.vim module.\r\n- Add ingo\/window.vim and ingo\/window\/adjacent modules.\r\n- Add ingo#list#Matches().\r\n- Add ingo\/list\/sequence.vim module.\r\n- Add ingo#fs#path#IsAbsolute() and ingo#fs#path#IsUpwards().\r\n- Add ingo\/area\/frompattern.vim module.\r\n- CHG: Rename ingo#selection#position#Get() to ingo#selection#area#Get(). Extend the function's API with options.\r\n- Add ingo#text#GetFromArea().\r\n- CHG: Rename ingo#text#replace#Area() to ingo#text#replace#Between() and add ingo#text#replace#Area() that actually takes a (single) a:area argument.\r\n- Add ingo\/area.vim module.\r\n- Add ingo#query#fromlist#QueryAsText() variant of ingo#query#fromlist#Query().\r\n- ENH: ingo#buffer#scratch#Create(): Allow to set the scratch buffer contents directly by passing a List as a:scratchCommand.\r\n- Extract generic ingo#buffer#generate#Create() from ingo\/buffer\/scratch.vim.\r\n- Add ingo#plugin#cmdcomplete#MakeListExprCompleteFunc() variant of ingo#plugin#cmdcomplete#MakeFixedListCompleteFunc().\r\n- Add ingo\/ftplugin\/converter\/external.vim module.","3":"- ingo#query#get#{Register,Mark}(): Avoid throwing E523 on invalid user input when executed e.g. from within a |:map-expr|.\r\n- Add ingo\/subst\/replacement.vim module with functions originally in PatternsOnText.vim (vimscript #4602).\r\n- Add ingo\/lines\/empty.vim module.\r\n- CHG: Rename ingo#str#split#First() to ingo#str#split#MatchFirst() and add ingo#str#split#StrFirst() variant that uses a fixed string, not a pattern.\r\n- Add ingo\/list\/lcs.vim module.\r\n- Add ingo#list#IsEmpty().\r\n- Add ingo\/collection\/find.vim module.\r\n- Add ingo\/window.vim and ingo\/window\/adjacent modules.\r\n- Add ingo#list#Matches().\r\n- Add ingo\/list\/sequence.vim module.\r\n- Add ingo#fs#path#IsAbsolute() and ingo#fs#path#IsUpwards().\r\n- Add ingo\/area\/frompattern.vim module.\r\n- CHG: Rename ingo#selection#position#Get() to ingo#selection#area#Get(). Extend the function's API with options.\r\n- Add ingo#text#GetFromArea().\r\n- CHG: Rename ingo#text#replace#Area() to ingo#text#replace#Between() and add ingo#text#replace#Area() that actually takes a (single) a:area argument.\r\n- Add ingo\/area.vim module.\r\n- Add ingo#query#fromlist#QueryAsText() variant of ingo#query#fromlist#Query().\r\n- ENH: ingo#buffer#scratch#Create(): Allow to set the scratch buffer contents directly by passing a List as a:scratchCommand.\r\n- Extract generic ingo#buffer#generate#Create() from ingo\/buffer\/scratch.vim.\r\n- Add ingo#plugin#cmdcomplete#MakeListExprCompleteFunc() variant of ingo#plugin#cmdcomplete#MakeFixedListCompleteFunc().\r\n- Add ingo\/ftplugin\/converter\/external.vim module.","package":"ingo-library-1.032.vmb.gz","4":"ingo-library-1.032.vmb.gz","src_id":"25582","5":"25582","creation_date":"1505906029","6":"1505906029"},{"0":"4433","vim_version":"7.0","1":"7.0","script_version":"1.031","2":"1.031","version_comment":"*** First release that's also available on GitHub: https:\/\/github.com\/inkarkat\/vim-ingo-library ***\r\n- FIX: Potentially invalid indexing of l:otherResult[l:i] in s:GetUnjoinedResult(). Use get() for inner List access, too.\r\n- Add special ingo#compat#synstack to work around missing patch 7.2.014: synstack() doesn't work in an empty line.\r\n- BUG: ingo#comments#SplitIndentAndText() and ingo#comments#RemoveCommentPrefix() fail with nestable comment prefixes with \"E688: More targets than List items\".","3":"*** First release that's also available on GitHub: https:\/\/github.com\/inkarkat\/vim-ingo-library ***\r\n- FIX: Potentially invalid indexing of l:otherResult[l:i] in s:GetUnjoinedResult(). Use get() for inner List access, too.\r\n- Add special ingo#compat#synstack to work around missing patch 7.2.014: synstack() doesn't work in an empty line.\r\n- BUG: ingo#comments#SplitIndentAndText() and ingo#comments#RemoveCommentPrefix() fail with nestable comment prefixes with \"E688: More targets than List items\".","package":"ingo-library-1.031.vmb.gz","4":"ingo-library-1.031.vmb.gz","src_id":"25358","5":"25358","creation_date":"1498576795","6":"1498576795"},{"0":"4433","vim_version":"7.0","1":"7.0","script_version":"1.030","2":"1.030","version_comment":"- Add escaping of additional values to ingo#option#Join() and split into ingo#option#Append() and ingo#option#Prepend().\r\n- Offer simpler ingo#option#JoinEscaped() and ingo#option#JoinUnescaped() for actual joining of values split via ingo#option#Split() \/ ingo#option#SplitAndUnescape().\r\n- Add ingo#str#EndsWith() variant of ingo#fs#path#split#Contains().\r\n- Add ingo#regexp#comments#GetFlexibleWhitespaceAndCommentPrefixPattern().\r\n- Add ingo\/hlgroup.vim module.\r\n- Add ingo#cursor#StartInsert() and ingo#cursor#StartAppend().\r\n- Add ingo\/compat\/command.vim module.\r\n- Add ingo#plugin#setting#Default().\r\n- BUG: ingo#mbyte#virtcol#GetVirtColOfCurrentCharacter() yields wrong values with single-width multibyte characters, and at the beginning of the line (column 1). Need to start with offset 1 (not 0), and account for that (subtract 1) in the final return. Need to check that the virtcol argument will be larger than 0.\r\n- Add ingo#format#Dict() variant of ingo#format#Format() that only handles identifier placeholders and a Dict containing them.\r\n- ENH: ingo#format#Format(): Also handle a:fmt without any \"%\" items without error.\r\n- Add ingo#compat#DictKey(), as Vim 7.4.1707 now allows using an empty dictionary key.\r\n- Add ingo#os#IsWindowsShell().\r\n- Generalize functions into ingo\/nary.vim and delegate ingo#binary#...() functions to those. Add ingo\/nary.vim module.\r\n- ENH: ingo#regexp#collection#LiteralToRegexp(): Support inverted collection via optional a:isInvert flag.\r\n- Add ingo#strdisplaywidth#CutLeft() variant of ingo#strdisplaywidth#strleft() that returns both parts. Same for ingo#strdisplaywidth#strright().\r\n- CHG: Rename ill-named ingo#strdisplaywidth#pad#Middle() to ingo#strdisplaywidth#pad#Center().\r\n- Add \"real\" ingo#strdisplaywidth#pad#Middle() that inserts the padding in the middle of the string \/ between the two passed string parts.\r\n- Add ingo#fs#path#split#PathAndName().\r\n- Add ingo#text#ReplaceChar(), a combination of ingo#text#GetChar(), ingo#text#Remove(), and ingo#text#Insert().\r\n- Add ingo#err#Command() for an alternative way of passing back [error] commands to be executed.\r\n- ingo#syntaxitem#IsOnSyntax(): Factor out synstack() emulation into ingo#compat#synstack() and unify similar function variants.\r\n- ENH: ingo#syntaxitem#IsOnSyntax(): Allow optional a:stopItemPattern to avoid considering syntax items at the bottom of the stack.\r\n- Add ingo#compat#synstack().\r\n- Add ingo\/dict\/count.vim module.\r\n- Add ingo\/digest.vim module.\r\n- Add ingo#buffer#VisibleList().","3":"- Add escaping of additional values to ingo#option#Join() and split into ingo#option#Append() and ingo#option#Prepend().\r\n- Offer simpler ingo#option#JoinEscaped() and ingo#option#JoinUnescaped() for actual joining of values split via ingo#option#Split() \/ ingo#option#SplitAndUnescape().\r\n- Add ingo#str#EndsWith() variant of ingo#fs#path#split#Contains().\r\n- Add ingo#regexp#comments#GetFlexibleWhitespaceAndCommentPrefixPattern().\r\n- Add ingo\/hlgroup.vim module.\r\n- Add ingo#cursor#StartInsert() and ingo#cursor#StartAppend().\r\n- Add ingo\/compat\/command.vim module.\r\n- Add ingo#plugin#setting#Default().\r\n- BUG: ingo#mbyte#virtcol#GetVirtColOfCurrentCharacter() yields wrong values with single-width multibyte characters, and at the beginning of the line (column 1). Need to start with offset 1 (not 0), and account for that (subtract 1) in the final return. Need to check that the virtcol argument will be larger than 0.\r\n- Add ingo#format#Dict() variant of ingo#format#Format() that only handles identifier placeholders and a Dict containing them.\r\n- ENH: ingo#format#Format(): Also handle a:fmt without any \"%\" items without error.\r\n- Add ingo#compat#DictKey(), as Vim 7.4.1707 now allows using an empty dictionary key.\r\n- Add ingo#os#IsWindowsShell().\r\n- Generalize functions into ingo\/nary.vim and delegate ingo#binary#...() functions to those. Add ingo\/nary.vim module.\r\n- ENH: ingo#regexp#collection#LiteralToRegexp(): Support inverted collection via optional a:isInvert flag.\r\n- Add ingo#strdisplaywidth#CutLeft() variant of ingo#strdisplaywidth#strleft() that returns both parts. Same for ingo#strdisplaywidth#strright().\r\n- CHG: Rename ill-named ingo#strdisplaywidth#pad#Middle() to ingo#strdisplaywidth#pad#Center().\r\n- Add \"real\" ingo#strdisplaywidth#pad#Middle() that inserts the padding in the middle of the string \/ between the two passed string parts.\r\n- Add ingo#fs#path#split#PathAndName().\r\n- Add ingo#text#ReplaceChar(), a combination of ingo#text#GetChar(), ingo#text#Remove(), and ingo#text#Insert().\r\n- Add ingo#err#Command() for an alternative way of passing back [error] commands to be executed.\r\n- ingo#syntaxitem#IsOnSyntax(): Factor out synstack() emulation into ingo#compat#synstack() and unify similar function variants.\r\n- ENH: ingo#syntaxitem#IsOnSyntax(): Allow optional a:stopItemPattern to avoid considering syntax items at the bottom of the stack.\r\n- Add ingo#compat#synstack().\r\n- Add ingo\/dict\/count.vim module.\r\n- Add ingo\/digest.vim module.\r\n- Add ingo#buffer#VisibleList().","package":"ingo-library-1.030.vmb.gz","4":"ingo-library-1.030.vmb.gz","src_id":"25262","5":"25262","creation_date":"1495827926","6":"1495827926"},{"0":"4433","vim_version":"7.0","1":"7.0","script_version":"1.029","2":"1.029","version_comment":"- CHG: ingo#comments#RemoveCommentPrefix() isn't useful as it omits any indent before the comment prefix. Change its implementation to just erase the prefix itself.\r\n- Add ingo#comments#SplitIndentAndText() to provide what ingo#comments#RemoveCommentPrefix() was previously used to: The line broken into indent (before, after, and with the comment prefix), and the remaining text.\r\n- Add ingo#indent#Split(), a simpler version of ingo#comments#SplitIndentAndText().\r\n- Add ingo#fs#traversal#FindFirstContainedInUpDir().\r\n- ingo#range#lines#Get(): A single (a:isGetAllRanges = 0) \/...\/ range already clobbers the last search pattern. Save and restore if necessary, and base didClobberSearchHistory on that check.\r\n- ingo#range#lines#Get(): Drop the ^ anchor for the range check to also detect \/...\/ as the end of the range.\r\n- Add ingo#cmdargs#register#ParsePrependedWritableRegister() alternative to ingo#cmdargs#register#ParseAppendedWritableRegister().\r\n- BUG: Optional a:position argument to ingo#window#preview#SplitToPreview() is mistakenly truncated to [1:2]. Inline the l:cursor and l:bufnr variables; they are only used in the function call, anyway.\r\n- Add ingo\/str\/find.vim module.\r\n- Add ingo\/str\/fromrange.vim module.\r\n- Add ingo#pos#SameLineIs[OnOr]After\/Before() variants.\r\n- Add ingo\/regexp\/build.vim module.\r\n- Add ingo#err#SetAndBeep().\r\n- FIX: ingo#query#get#Char() does not beep when validExpr is given and invalid character pressed.\r\n- Add ingo#query#get#ValidChar() variant that loops until a valid character has been pressed.\r\n- Add ingo\/range\/invert.vim module.\r\n- Add ingo\/line\/replace.vim and ingo\/lines\/replace.vim modules.\r\n- Extract ingo#range#merge#FromLnums() from ingo#range#merge#Merge().\r\n- ingo#range#lines#Get(): If the range is a backwards-looking ?{pattern}?, we need to attempt the match on any line with :global\/^\/... Else, the border behavior is inconsistent: ranges that extend the passed range at the bottom are (partially) included, but ranges that extend at the front would not be.\r\n- Add ingo\/math.vim, ingo\/binary.vim and ingo\/list\/split.vim modules.\r\n- Add ingo#comments#SplitAll(), a more powerful variant of ingo#comments#SplitIndentAndText().\r\n- Add ingo#compat#systemlist().\r\n- Add ingo#escape#OnlyUnescaped().\r\n- Add ingo#msg#ColoredMsg() and ingo#msg#ColoredStatusMsg().\r\n- Add ingo\/query\/recall.vim module.\r\n- Add ingo#register#GetAsList().\r\n- FIX: ingo#format#Format(): An invalid %0$ references the last passed argument instead of yielding the empty string (as [argument-index$] is 1-based). Add bounds check to avoid that\r\n- FIX: ingo#format#Format(): Also support escaping via \"%%\", as in printf().\r\n- Add ingo#subst#FirstSubstitution(), ingo#subst#FirstPattern(), ingo#subst#FirstParameter().\r\n- Add ingo#regexp#collection#Expr().\r\n- BUG: ingo#regexp#magic#Normalize() also processes the contents of collections [...]; especially the escaping of \"]\" wreaks havoc on the pattern. Rename s:ConvertMagicness() into ingo#regexp#magic#ConvertMagicnessOfElement() and introduce intermediate s:ConvertMagicnessOfFragment() that first separates collections from other elements and only invokes the former on those other elements.\r\n- Add ingo#collections#fromsplit#MapItemsAndSeparators().","3":"- CHG: ingo#comments#RemoveCommentPrefix() isn't useful as it omits any indent before the comment prefix. Change its implementation to just erase the prefix itself.\r\n- Add ingo#comments#SplitIndentAndText() to provide what ingo#comments#RemoveCommentPrefix() was previously used to: The line broken into indent (before, after, and with the comment prefix), and the remaining text.\r\n- Add ingo#indent#Split(), a simpler version of ingo#comments#SplitIndentAndText().\r\n- Add ingo#fs#traversal#FindFirstContainedInUpDir().\r\n- ingo#range#lines#Get(): A single (a:isGetAllRanges = 0) \/...\/ range already clobbers the last search pattern. Save and restore if necessary, and base didClobberSearchHistory on that check.\r\n- ingo#range#lines#Get(): Drop the ^ anchor for the range check to also detect \/...\/ as the end of the range.\r\n- Add ingo#cmdargs#register#ParsePrependedWritableRegister() alternative to ingo#cmdargs#register#ParseAppendedWritableRegister().\r\n- BUG: Optional a:position argument to ingo#window#preview#SplitToPreview() is mistakenly truncated to [1:2]. Inline the l:cursor and l:bufnr variables; they are only used in the function call, anyway.\r\n- Add ingo\/str\/find.vim module.\r\n- Add ingo\/str\/fromrange.vim module.\r\n- Add ingo#pos#SameLineIs[OnOr]After\/Before() variants.\r\n- Add ingo\/regexp\/build.vim module.\r\n- Add ingo#err#SetAndBeep().\r\n- FIX: ingo#query#get#Char() does not beep when validExpr is given and invalid character pressed.\r\n- Add ingo#query#get#ValidChar() variant that loops until a valid character has been pressed.\r\n- Add ingo\/range\/invert.vim module.\r\n- Add ingo\/line\/replace.vim and ingo\/lines\/replace.vim modules.\r\n- Extract ingo#range#merge#FromLnums() from ingo#range#merge#Merge().\r\n- ingo#range#lines#Get(): If the range is a backwards-looking ?{pattern}?, we need to attempt the match on any line with :global\/^\/... Else, the border behavior is inconsistent: ranges that extend the passed range at the bottom are (partially) included, but ranges that extend at the front would not be.\r\n- Add ingo\/math.vim, ingo\/binary.vim and ingo\/list\/split.vim modules.\r\n- Add ingo#comments#SplitAll(), a more powerful variant of ingo#comments#SplitIndentAndText().\r\n- Add ingo#compat#systemlist().\r\n- Add ingo#escape#OnlyUnescaped().\r\n- Add ingo#msg#ColoredMsg() and ingo#msg#ColoredStatusMsg().\r\n- Add ingo\/query\/recall.vim module.\r\n- Add ingo#register#GetAsList().\r\n- FIX: ingo#format#Format(): An invalid %0$ references the last passed argument instead of yielding the empty string (as [argument-index$] is 1-based). Add bounds check to avoid that\r\n- FIX: ingo#format#Format(): Also support escaping via \"%%\", as in printf().\r\n- Add ingo#subst#FirstSubstitution(), ingo#subst#FirstPattern(), ingo#subst#FirstParameter().\r\n- Add ingo#regexp#collection#Expr().\r\n- BUG: ingo#regexp#magic#Normalize() also processes the contents of collections [...]; especially the escaping of \"]\" wreaks havoc on the pattern. Rename s:ConvertMagicness() into ingo#regexp#magic#ConvertMagicnessOfElement() and introduce intermediate s:ConvertMagicnessOfFragment() that first separates collections from other elements and only invokes the former on those other elements.\r\n- Add ingo#collections#fromsplit#MapItemsAndSeparators().","package":"ingo-library-1.029.vmb.gz","4":"ingo-library-1.029.vmb.gz","src_id":"24918","5":"24918","creation_date":"1485258152","6":"1485258152"},{"0":"4433","vim_version":"7.0","1":"7.0","script_version":"1.028","2":"1.028","version_comment":"- ENH: Also support optional a:flagsMatchCount in ingo#cmdargs#pattern#ParseUnescaped() and ingo#cmdargs#pattern#ParseUnescapedWithLiteralWholeWord().\r\n- Add missing ingo#cmdargs#pattern#ParseWithLiteralWholeWord() variant.\r\n- ingo#codec#URL#Decode(): Also convert the character set to UTF-8 to properly handle non-ASCII characters. For example, %C3%9C should decode to \"\u00c3\u009c\", not to \"\u00c3\u0089œ\".\r\n- Add ingo#collections#SeparateItemsAndSeparators(), a variant of ingo#collections#SplitKeepSeparators().\r\n- Add ingo\/collections\/fromsplit.vim module.\r\n- Add ingo#list#Join().\r\n- Add ingo\/compat\/window.vim module.\r\n- Add ingo\/fs\/path\/asfilename.vim module.\r\n- Add ingo\/list\/find.vim module.\r\n- Add ingo#option#Join().\r\n- FIX: Correct delegation in ingo#buffer#temp#Execute(); wrong recursive call was used (after 1.027).\r\n- ENH: Add optional a:isSilent argument to ingo#buffer#temp#Execute().\r\n- ENH: Add optional a:reservedColumns also to ingo#avoidprompt#TruncateTo(), and pass this from ingo#avoidprompt#Truncate().\r\n- ingo#avoidprompt#TruncateTo(): The strright() cannot precisely account for the rendering of tab widths. Check the result, and if necessary, remove further characters until we go below the limit.\r\n- ENH: Add optional {context} to all ingo#err#... functions, in case other custom commands can be called between error setting and checking, to avoid clobbering of your error message.\r\n- Add ingo\/buffer\/locate.vim module.\r\n- Add ingo\/window\/locate.vim module.\r\n- Add ingo\/indent.vim module.\r\n- Add ingo#compat#getcurpos().","3":"- ENH: Also support optional a:flagsMatchCount in ingo#cmdargs#pattern#ParseUnescaped() and ingo#cmdargs#pattern#ParseUnescapedWithLiteralWholeWord().\r\n- Add missing ingo#cmdargs#pattern#ParseWithLiteralWholeWord() variant.\r\n- ingo#codec#URL#Decode(): Also convert the character set to UTF-8 to properly handle non-ASCII characters. For example, %C3%9C should decode to \"\u00c3\u009c\", not to \"\u00c3\u0089œ\".\r\n- Add ingo#collections#SeparateItemsAndSeparators(), a variant of ingo#collections#SplitKeepSeparators().\r\n- Add ingo\/collections\/fromsplit.vim module.\r\n- Add ingo#list#Join().\r\n- Add ingo\/compat\/window.vim module.\r\n- Add ingo\/fs\/path\/asfilename.vim module.\r\n- Add ingo\/list\/find.vim module.\r\n- Add ingo#option#Join().\r\n- FIX: Correct delegation in ingo#buffer#temp#Execute(); wrong recursive call was used (after 1.027).\r\n- ENH: Add optional a:isSilent argument to ingo#buffer#temp#Execute().\r\n- ENH: Add optional a:reservedColumns also to ingo#avoidprompt#TruncateTo(), and pass this from ingo#avoidprompt#Truncate().\r\n- ingo#avoidprompt#TruncateTo(): The strright() cannot precisely account for the rendering of tab widths. Check the result, and if necessary, remove further characters until we go below the limit.\r\n- ENH: Add optional {context} to all ingo#err#... functions, in case other custom commands can be called between error setting and checking, to avoid clobbering of your error message.\r\n- Add ingo\/buffer\/locate.vim module.\r\n- Add ingo\/window\/locate.vim module.\r\n- Add ingo\/indent.vim module.\r\n- Add ingo#compat#getcurpos().","package":"ingo-library-1.028.vmb.gz","4":"ingo-library-1.028.vmb.gz","src_id":"24774","5":"24774","creation_date":"1480515121","6":"1480515121"},{"0":"4433","vim_version":"7.0","1":"7.0","script_version":"1.027","2":"1.027","version_comment":"- Add ingo#buffer#temp#ExecuteWithText() and ingo#buffer#temp#CallWithText() variants that pre-initialize the buffer (a common use case).\r\n- Add ingo#msg#MsgFromShellError().\r\n- ENH: ingo#query#fromlist#Query(): Support headless (testing) mode via g:IngoLibrary_QueryChoices, like ingo#query#Confirm() already does.\r\n- Expose ingo#query#fromlist#RenderList(). Expose ingo#query#StripAccellerator().\r\n- ENH: ingo#cmdargs#pattern#Parse(): Add second optional a:flagsMatchCount argument, similar to what ingo#cmdargs#substitute#Parse() has in a:options.\r\n- Add ingo#cmdargs#pattern#RawParse().\r\n- Add ingo\/regexp\/collection.vim module.\r\n- Add ingo#str#trd().","3":"- Add ingo#buffer#temp#ExecuteWithText() and ingo#buffer#temp#CallWithText() variants that pre-initialize the buffer (a common use case).\r\n- Add ingo#msg#MsgFromShellError().\r\n- ENH: ingo#query#fromlist#Query(): Support headless (testing) mode via g:IngoLibrary_QueryChoices, like ingo#query#Confirm() already does.\r\n- Expose ingo#query#fromlist#RenderList(). Expose ingo#query#StripAccellerator().\r\n- ENH: ingo#cmdargs#pattern#Parse(): Add second optional a:flagsMatchCount argument, similar to what ingo#cmdargs#substitute#Parse() has in a:options.\r\n- Add ingo#cmdargs#pattern#RawParse().\r\n- Add ingo\/regexp\/collection.vim module.\r\n- Add ingo#str#trd().","package":"ingo-library-1.027.vmb.gz","4":"ingo-library-1.027.vmb.gz","src_id":"24573","5":"24573","creation_date":"1475228270","6":"1475228270"},{"0":"4433","vim_version":"7.0","1":"7.0","script_version":"1.026","2":"1.026","version_comment":"- Add ingo#strdisplaywidth#pad#Middle().\r\n- Add ingo\/format\/columns.vim module.\r\n- ENH: ingo#avoidprompt#TruncateTo() and ingo#strdisplaywidth#TruncateTo() have a configurable ellipsis string g:IngoLibrary_TruncateEllipsis, now defaulting to a single-char UTF-8 variant if we're in such encoding. Thanks to Daniel Hahler for sending a patch! It also handles pathologically small lengths that only show \/ cut into the ellipsis.\r\n- Add ingo#compat#strgetchar() and ingo#compat#strcharpart(), introduced in Vim 7.4.1730.\r\n- Support ingo#compat#strchars() optional {skipcc} argument, introduced in Vim 7.4.755.","3":"- Add ingo#strdisplaywidth#pad#Middle().\r\n- Add ingo\/format\/columns.vim module.\r\n- ENH: ingo#avoidprompt#TruncateTo() and ingo#strdisplaywidth#TruncateTo() have a configurable ellipsis string g:IngoLibrary_TruncateEllipsis, now defaulting to a single-char UTF-8 variant if we're in such encoding. Thanks to Daniel Hahler for sending a patch! It also handles pathologically small lengths that only show \/ cut into the ellipsis.\r\n- Add ingo#compat#strgetchar() and ingo#compat#strcharpart(), introduced in Vim 7.4.1730.\r\n- Support ingo#compat#strchars() optional {skipcc} argument, introduced in Vim 7.4.755.","package":"ingo-library-1.026.vmb.gz","4":"ingo-library-1.026.vmb.gz","src_id":"24439","5":"24439","creation_date":"1470926775","6":"1470926775"},{"0":"4433","vim_version":"7.0","1":"7.0","script_version":"1.025","2":"1.025","version_comment":"- Add ingo#str#Contains().\r\n- Add ingo#fs#path#split#Contains().\r\n- ingo#subst#pairs#Substitute(): Canonicalize path separators in {replacement}, too. This is important to match further pairs, too, as the pattern is always in canonical form, so the replacement has to be, too.\r\n- ingo#subst#pairs#Substitute() and ingo#subst#pairs#Split(): Only canonicalize path separators in {replacement} on demand, via additional a:isCanonicalizeReplacement argument. Some clients may not need iterative replacement, and treat the wildcard as a convenient regexp-shorthand, not overly filesystem-related.\r\n- ENH: Allow passing to ingo#subst#pairs#Substitute() [wildcard, replacement] Lists instead of {wildcard}={replacement} Strings, too.\r\n- Add ingo#collections#Partition().\r\n- Add ingo#text#frompattern#GetAroundHere().\r\n- Add ingo#cmdline#showmode#TemporaryNoShowMode() variant of ingo#cmdline#showmode#OneLineTemporaryNoShowMode().\r\n- ENH: Enable customization of ingo#window#special#IsSpecialWindow() via g:IngoLibrary_SpecialWindowPredicates.\r\n- Add ingo#query#Question().\r\n- ENH: Make ingo#window#special#SaveSpecialWindowSize() return sum of special windows' widths and sum of special windows' heights.\r\n- Add ingo\/swap.vim module.\r\n- Add ingo#collections#unique#Insert() and ingo#collections#unique#Add().\r\n- BUG: Unescaped backslash resulted in unclosed [...] regexp collection causing ingo#escape#file#fnameunescape() to fail to escape on Unix.\r\n- Add ingo#text#GetCharBefore() variant of ingo#text#GetChar().\r\n- Add optional a:characterOffset to ingo#record#PositionAndLocation().\r\n- Add ingo#regexp#MakeStartWordSearch() ingo#regexp#MakeEndWordSearch() variants of ingo#regexp#MakeWholeWordSearch().\r\n- Add ingo#pos#IsInsideVisualSelection().\r\n- Add ingo#escape#command#mapunescape().\r\n- ENH: Add second optional flag a:isKeepDirectories to ingo#cmdargs#glob#Expand() \/ ingo#cmdargs#glob#ExpandSingle().\r\n- Add ingo#range#borders#StartAndEndRange().\r\n- Add ingo#msg#VerboseMsg().\r\n- Add ingo#compat#sha256(), with a fallback to an external sha256sum command.\r\n- Add ingo#collections#Reduce().\r\n- Add ingo\/actions\/iterations.vim module.\r\n- Add ingo\/actions\/special.vim module.\r\n- Add ingo#collections#differences#ContainsLoosely() and ingo#collections#differences#ContainsStrictly().\r\n- Add ingo#buffer#ExistOtherLoadedBuffers().\r\n- FIX: Temporarily reset 'switchbuf' in ingo#buffer#visible#Execute() and ingo#buffer#temp#Execute(), to avoid that \"usetab\" switched to another tab page.\r\n- ingo#msg#HighlightMsg(): Make a:hlgroup optional, default to 'None' (so the function is useful to return to normal highlighting).\r\n- Add ingo#msg#HighlightN(), an :echon variant.","3":"- Add ingo#str#Contains().\r\n- Add ingo#fs#path#split#Contains().\r\n- ingo#subst#pairs#Substitute(): Canonicalize path separators in {replacement}, too. This is important to match further pairs, too, as the pattern is always in canonical form, so the replacement has to be, too.\r\n- ingo#subst#pairs#Substitute() and ingo#subst#pairs#Split(): Only canonicalize path separators in {replacement} on demand, via additional a:isCanonicalizeReplacement argument. Some clients may not need iterative replacement, and treat the wildcard as a convenient regexp-shorthand, not overly filesystem-related.\r\n- ENH: Allow passing to ingo#subst#pairs#Substitute() [wildcard, replacement] Lists instead of {wildcard}={replacement} Strings, too.\r\n- Add ingo#collections#Partition().\r\n- Add ingo#text#frompattern#GetAroundHere().\r\n- Add ingo#cmdline#showmode#TemporaryNoShowMode() variant of ingo#cmdline#showmode#OneLineTemporaryNoShowMode().\r\n- ENH: Enable customization of ingo#window#special#IsSpecialWindow() via g:IngoLibrary_SpecialWindowPredicates.\r\n- Add ingo#query#Question().\r\n- ENH: Make ingo#window#special#SaveSpecialWindowSize() return sum of special windows' widths and sum of special windows' heights.\r\n- Add ingo\/swap.vim module.\r\n- Add ingo#collections#unique#Insert() and ingo#collections#unique#Add().\r\n- BUG: Unescaped backslash resulted in unclosed [...] regexp collection causing ingo#escape#file#fnameunescape() to fail to escape on Unix.\r\n- Add ingo#text#GetCharBefore() variant of ingo#text#GetChar().\r\n- Add optional a:characterOffset to ingo#record#PositionAndLocation().\r\n- Add ingo#regexp#MakeStartWordSearch() ingo#regexp#MakeEndWordSearch() variants of ingo#regexp#MakeWholeWordSearch().\r\n- Add ingo#pos#IsInsideVisualSelection().\r\n- Add ingo#escape#command#mapunescape().\r\n- ENH: Add second optional flag a:isKeepDirectories to ingo#cmdargs#glob#Expand() \/ ingo#cmdargs#glob#ExpandSingle().\r\n- Add ingo#range#borders#StartAndEndRange().\r\n- Add ingo#msg#VerboseMsg().\r\n- Add ingo#compat#sha256(), with a fallback to an external sha256sum command.\r\n- Add ingo#collections#Reduce().\r\n- Add ingo\/actions\/iterations.vim module.\r\n- Add ingo\/actions\/special.vim module.\r\n- Add ingo#collections#differences#ContainsLoosely() and ingo#collections#differences#ContainsStrictly().\r\n- Add ingo#buffer#ExistOtherLoadedBuffers().\r\n- FIX: Temporarily reset 'switchbuf' in ingo#buffer#visible#Execute() and ingo#buffer#temp#Execute(), to avoid that \"usetab\" switched to another tab page.\r\n- ingo#msg#HighlightMsg(): Make a:hlgroup optional, default to 'None' (so the function is useful to return to normal highlighting).\r\n- Add ingo#msg#HighlightN(), an :echon variant.","package":"ingo-library-1.025.vmb.gz","4":"ingo-library-1.025.vmb.gz","src_id":"24435","5":"24435","creation_date":"1470758470","6":"1470758470"},{"0":"4433","vim_version":"7.0","1":"7.0","script_version":"1.024","2":"1.024","version_comment":"- FIX: Also correctly set change marks when replacing entire buffer with ingo#lines#Replace().\r\n- Add ingo\/collections\/differences.vim module.\r\n- Add ingo\/compat\/regexp.vim module.\r\n- Add ingo\/encoding.vim module.\r\n- Add ingo\/str\/join.vim module.\r\n- Add ingo#option#SplitAndUnescape().\r\n- Add ingo#list#Zip() and ingo#list#ZipLongest().\r\n- ingo#buffer#visible#Execute(): Restore the window layout when the buffer is visible but in a window with 0 height \/ width. And restore the previous window when the buffer isn't visible yet. Add a check that the command hasn't switched to another window (and go back if true) before closing the split window.\r\n- Add ingo\/regexp\/virtcols.vim module.\r\n- Add ingo#str#GetVirtCols() and ingo#text#RemoveVirtCol().\r\n- FIX: Off-by-one: Allow column 1 in ingo#text#Remove().\r\n- BUG: ingo#buffer#scratch#Create() with existing scratch buffer yields \"E95: Buffer with this name already exists\" instead of reusing the buffer.\r\n- Keep current cursor position when ingo#buffer#scratch#Create() removes the first empty line in the scratch buffer.\r\n- ingo#text#frompattern#GetHere(): Do not move the cursor (to the end of the matched pattern); this is unexpected and can be easily avoided.\r\n- FIX: ingo#cmdargs#GetStringExpr(): Escape (unescaped) double quotes when the argument contains backslashes; else, the expansion of \\x will silently fail.\r\n- Add ingo#cmdargs#GetUnescapedExpr(); when there's no need for empty expressions, the removal of the (single \/ double) quotes may be unexpected.\r\n- ingo#text#Insert(): Also allow insertion one beyond the last line (in column 1), just like setline() allows.\r\n- Rename ingo#date#format#Human() to ingo#date#format#Preferred(), default to %x value for strftime(), and allow to customize that (even dynamically, maybe based on 'spelllang').\r\n- Add optional a:templateForNewBuffer argument to ingo#fs#tempfile#Make() and ensure (by default) that the temp file isn't yet loaded in a Vim buffer (which would generate \"E139: file is loaded in another buffer\" on the usual :write, :saveas commands).\r\n- Add ingo#compat#shiftwidth(), taken from :h shiftwidth().","3":"- FIX: Also correctly set change marks when replacing entire buffer with ingo#lines#Replace().\r\n- Add ingo\/collections\/differences.vim module.\r\n- Add ingo\/compat\/regexp.vim module.\r\n- Add ingo\/encoding.vim module.\r\n- Add ingo\/str\/join.vim module.\r\n- Add ingo#option#SplitAndUnescape().\r\n- Add ingo#list#Zip() and ingo#list#ZipLongest().\r\n- ingo#buffer#visible#Execute(): Restore the window layout when the buffer is visible but in a window with 0 height \/ width. And restore the previous window when the buffer isn't visible yet. Add a check that the command hasn't switched to another window (and go back if true) before closing the split window.\r\n- Add ingo\/regexp\/virtcols.vim module.\r\n- Add ingo#str#GetVirtCols() and ingo#text#RemoveVirtCol().\r\n- FIX: Off-by-one: Allow column 1 in ingo#text#Remove().\r\n- BUG: ingo#buffer#scratch#Create() with existing scratch buffer yields \"E95: Buffer with this name already exists\" instead of reusing the buffer.\r\n- Keep current cursor position when ingo#buffer#scratch#Create() removes the first empty line in the scratch buffer.\r\n- ingo#text#frompattern#GetHere(): Do not move the cursor (to the end of the matched pattern); this is unexpected and can be easily avoided.\r\n- FIX: ingo#cmdargs#GetStringExpr(): Escape (unescaped) double quotes when the argument contains backslashes; else, the expansion of \\x will silently fail.\r\n- Add ingo#cmdargs#GetUnescapedExpr(); when there's no need for empty expressions, the removal of the (single \/ double) quotes may be unexpected.\r\n- ingo#text#Insert(): Also allow insertion one beyond the last line (in column 1), just like setline() allows.\r\n- Rename ingo#date#format#Human() to ingo#date#format#Preferred(), default to %x value for strftime(), and allow to customize that (even dynamically, maybe based on 'spelllang').\r\n- Add optional a:templateForNewBuffer argument to ingo#fs#tempfile#Make() and ensure (by default) that the temp file isn't yet loaded in a Vim buffer (which would generate \"E139: file is loaded in another buffer\" on the usual :write, :saveas commands).\r\n- Add ingo#compat#shiftwidth(), taken from :h shiftwidth().","package":"ingo-library-1.024.vmb.gz","4":"ingo-library-1.024.vmb.gz","src_id":"23215","5":"23215","creation_date":"1429789175","6":"1429789175"},{"0":"4433","vim_version":"7.0","1":"7.0","script_version":"1.023","2":"1.023","version_comment":"- ENH: Make ingo#selection#frompattern#GetPositions() automatically convert \\%# in the passed a:pattern to the hard-coded cursor column.\r\n- Add ingo#collections#mapsort().\r\n- Add ingo\/collections\/memoized.vim module.\r\n- ENH: Add optional a:isReturnAsList flag to ingo#buffer#temp#Execute() and ingo#buffer#temp#Call().\r\n- ENH: Also allow passing an items List to ingo#dict#Mirror() and ingo#dict#AddMirrored() (useful to influence which key from equal values is used).\r\n- ENH: Also support optional a:isEnsureUniqueness flag for ingo#dict#FromItems().\r\n- Expose ingo#regexp#MakeWholeWordSearch().\r\n- Add ingo#plugin#setting#GetTabLocal().\r\n- ENH: Add a:isFile flag to ingo#escape#file#bufnameescape() in order to do full matching on scratch buffer names. There, the expansion to a full absolute path must be skipped in order to match.\r\n- ENH: Add a:isGetAllRanges optional argument to ingo#range#lines#Get().\r\n- Add ingo#strdisplaywidth#TruncateTo().\r\n- Add ingo\/str\/frompattern.vim module.\r\n- Add ingo\/folds\/persistence.vim module.\r\n- Add ingo#cmdargs#pattern#IsDelimited().\r\n- Support ingo#query#fromlist#Query() querying of more than 10 elements by number. Break listing of query choices into multiple lines when the overall question doesn't fit in a single line.\r\n- Add ingo\/event.vim module.\r\n- Add ingo\/range\/merge.vim module.\r\n- Add ingo#filetype#IsPrimary().\r\n- Add ingo#plugin#setting#GetScope().\r\n- Add ingo#regexp#fromwildcard#AnchoredToPathBoundaries().\r\n- Use :close! in ingo#buffer#visible#Execute() to handle modified buffers when :set nohidden, too.\r\n- Improve heuristics of ingo#window#quickfix#IsQuickfixList() to also handle empty location list (with non-empty quickfix list).\r\n- Minor: ingo#text#Remove(): Correct exception prefix.\r\n- Add ingo#window#quickfix#TranslateVirtualColToByteCount() from autoload\/QuickFixCurrentNumber.vim.","3":"- ENH: Make ingo#selection#frompattern#GetPositions() automatically convert \\%# in the passed a:pattern to the hard-coded cursor column.\r\n- Add ingo#collections#mapsort().\r\n- Add ingo\/collections\/memoized.vim module.\r\n- ENH: Add optional a:isReturnAsList flag to ingo#buffer#temp#Execute() and ingo#buffer#temp#Call().\r\n- ENH: Also allow passing an items List to ingo#dict#Mirror() and ingo#dict#AddMirrored() (useful to influence which key from equal values is used).\r\n- ENH: Also support optional a:isEnsureUniqueness flag for ingo#dict#FromItems().\r\n- Expose ingo#regexp#MakeWholeWordSearch().\r\n- Add ingo#plugin#setting#GetTabLocal().\r\n- ENH: Add a:isFile flag to ingo#escape#file#bufnameescape() in order to do full matching on scratch buffer names. There, the expansion to a full absolute path must be skipped in order to match.\r\n- ENH: Add a:isGetAllRanges optional argument to ingo#range#lines#Get().\r\n- Add ingo#strdisplaywidth#TruncateTo().\r\n- Add ingo\/str\/frompattern.vim module.\r\n- Add ingo\/folds\/persistence.vim module.\r\n- Add ingo#cmdargs#pattern#IsDelimited().\r\n- Support ingo#query#fromlist#Query() querying of more than 10 elements by number. Break listing of query choices into multiple lines when the overall question doesn't fit in a single line.\r\n- Add ingo\/event.vim module.\r\n- Add ingo\/range\/merge.vim module.\r\n- Add ingo#filetype#IsPrimary().\r\n- Add ingo#plugin#setting#GetScope().\r\n- Add ingo#regexp#fromwildcard#AnchoredToPathBoundaries().\r\n- Use :close! in ingo#buffer#visible#Execute() to handle modified buffers when :set nohidden, too.\r\n- Improve heuristics of ingo#window#quickfix#IsQuickfixList() to also handle empty location list (with non-empty quickfix list).\r\n- Minor: ingo#text#Remove(): Correct exception prefix.\r\n- Add ingo#window#quickfix#TranslateVirtualColToByteCount() from autoload\/QuickFixCurrentNumber.vim.","package":"ingo-library-1.023.vmb.gz","4":"ingo-library-1.023.vmb.gz","src_id":"22895","5":"22895","creation_date":"1423481270","6":"1423481270"},{"0":"4433","vim_version":"7.0","1":"7.0","script_version":"1.022","2":"1.022","version_comment":"- Add ingo#pos#Before() and ingo#pos#After().\r\n- Move LineJuggler#FoldClosed() and LineJuggler#FoldClosedEnd() into ingo-library as ingo#range#NetStart() and ingo#range#NetEnd().\r\n- Add ingo\/regexp\/pairs.vim module.\r\n- Add ingo#compat#glob() and ingo#compat#globpath().\r\n- ingo#range#lines#Get() needs to consider and temporarily disable closed folds when resolving \/{pattern}\/ ranges.","3":"- Add ingo#pos#Before() and ingo#pos#After().\r\n- Move LineJuggler#FoldClosed() and LineJuggler#FoldClosedEnd() into ingo-library as ingo#range#NetStart() and ingo#range#NetEnd().\r\n- Add ingo\/regexp\/pairs.vim module.\r\n- Add ingo#compat#glob() and ingo#compat#globpath().\r\n- ingo#range#lines#Get() needs to consider and temporarily disable closed folds when resolving \/{pattern}\/ ranges.","package":"ingo-library-1.022.vmb.gz","4":"ingo-library-1.022.vmb.gz","src_id":"22460","5":"22460","creation_date":"1411723687","6":"1411723687"},{"0":"4433","vim_version":"7.0","1":"7.0","script_version":"1.021","2":"1.021","version_comment":"- Add ingo#compat#uniq().\r\n- Add ingo#option#Contains() and ingo#option#ContainsOneOf().\r\n- BUG: Wrong position type causes ingo#selection#position#get() to be one-off with :set selection=exclusive and when the cursor is after the selection.\r\n- Use built-in changenr() in ingo#undo#GetChangeNumber(); actually, the entire function could be replaced by the built-in, if it would not just return one less than the number of the undone change after undo. We want the result to represent the current change, regardless of what undo \/ redo was done earlier. Change the implementation to test for whether the current change is the last in the buffer, and if not, make a no-op change to get to an explicit change state.\r\n- Simplify ingo#buffer#temprange#Execute() by using changenr(). Keep using ingo#undo#GetChangeNumber() because we need to create a new no-op change when there was a previous :undo.\r\n- Add ingo\/smartcase.vim module.\r\n- FIX: ingo#cmdargs#substitute#Parse() branch for special case of {flags} without \/pat\/string\/ must only be entered when a:arguments is not empty.\r\n- ENH: Allow to pass path separator to ingo#regexp#fromwildcard#Convert() and ingo#regexp#fromwildcard#IsWildcardPathPattern().\r\n- Add ingo\/collections\/permute.vim module.\r\n- Add ingo#window#preview#OpenFilespec(), a wrapper around :pedit that performs the fnameescape() and obeys the custom g:previewwindowsplitmode.","3":"- Add ingo#compat#uniq().\r\n- Add ingo#option#Contains() and ingo#option#ContainsOneOf().\r\n- BUG: Wrong position type causes ingo#selection#position#get() to be one-off with :set selection=exclusive and when the cursor is after the selection.\r\n- Use built-in changenr() in ingo#undo#GetChangeNumber(); actually, the entire function could be replaced by the built-in, if it would not just return one less than the number of the undone change after undo. We want the result to represent the current change, regardless of what undo \/ redo was done earlier. Change the implementation to test for whether the current change is the last in the buffer, and if not, make a no-op change to get to an explicit change state.\r\n- Simplify ingo#buffer#temprange#Execute() by using changenr(). Keep using ingo#undo#GetChangeNumber() because we need to create a new no-op change when there was a previous :undo.\r\n- Add ingo\/smartcase.vim module.\r\n- FIX: ingo#cmdargs#substitute#Parse() branch for special case of {flags} without \/pat\/string\/ must only be entered when a:arguments is not empty.\r\n- ENH: Allow to pass path separator to ingo#regexp#fromwildcard#Convert() and ingo#regexp#fromwildcard#IsWildcardPathPattern().\r\n- Add ingo\/collections\/permute.vim module.\r\n- Add ingo#window#preview#OpenFilespec(), a wrapper around :pedit that performs the fnameescape() and obeys the custom g:previewwindowsplitmode.","package":"ingo-library-1.021.vmb.gz","4":"ingo-library-1.021.vmb.gz","src_id":"22180","5":"22180","creation_date":"1404984528","6":"1404984528"},{"0":"4433","vim_version":"7.0","1":"7.0","script_version":"1.020","2":"1.020","version_comment":"- Add ingo\/dict\/find.vim module.\r\n- Use ingo#escape#Unescape() in ingo#cmdargs#pattern#Unescape(). Add ingo#cmdargs#pattern#ParseUnescaped() to avoid the double and inefficient ingo#cmdargs#pattern#Unescape(ingo#cmdargs#pattern#Parse()) so far used by many clients.\r\n- Add ingo#cmdargs#pattern#ParseUnescapedWithLiteralWholeWord() for the common [\/]{pattern}[\/ behavior as built-in commands like |:djump|]. When the pattern isn't delimited by \/...\/, the returned pattern is modified so that only literal whole words are matched. so far used by many clients.\r\n- CHG: At ingo#regexp#FromLiteralText(), add the a:isWholeWordSearch also on either side, or when there are non-keyword characters in the middle of the text. The * command behavior where this is modeled after only handles a smaller subset, and this extension looks sensible and DWIM.\r\n- Add ingo#compat#abs().\r\n- Factor out and expose ingo#text#Replace#Area().\r\n- CHG: When replacing at the cursor position, also jump to the beginning of the replacement. This is more consistent with Vim's default behavior.\r\n- Add ingo\/record.vim module.\r\n- ENH: Allow passing optional a:tabnr to ingo#window#preview#IsPreviewWindowVisible().\r\n- Factor out ingo#window#preview#OpenBuffer().\r\n- CHG: Change optional a:cursor argument of ingo#window#preview#SplitToPreview() from 4-tuple getpos()-style to [lnum, col]-style.\r\n- Add ingo\/query\/fromlist.vim module.\r\n- Add ingo\/option.vim module.\r\n- Add ingo\/join.vim module.\r\n- Expose ingo#actions#GetValExpr().\r\n- Add ingo\/range\/lines.vim module.\r\n- ENH: Add a:options.commandExpr to ingo#cmdargs#range#Parse().","3":"- Add ingo\/dict\/find.vim module.\r\n- Use ingo#escape#Unescape() in ingo#cmdargs#pattern#Unescape(). Add ingo#cmdargs#pattern#ParseUnescaped() to avoid the double and inefficient ingo#cmdargs#pattern#Unescape(ingo#cmdargs#pattern#Parse()) so far used by many clients.\r\n- Add ingo#cmdargs#pattern#ParseUnescapedWithLiteralWholeWord() for the common [\/]{pattern}[\/ behavior as built-in commands like |:djump|]. When the pattern isn't delimited by \/...\/, the returned pattern is modified so that only literal whole words are matched. so far used by many clients.\r\n- CHG: At ingo#regexp#FromLiteralText(), add the a:isWholeWordSearch also on either side, or when there are non-keyword characters in the middle of the text. The * command behavior where this is modeled after only handles a smaller subset, and this extension looks sensible and DWIM.\r\n- Add ingo#compat#abs().\r\n- Factor out and expose ingo#text#Replace#Area().\r\n- CHG: When replacing at the cursor position, also jump to the beginning of the replacement. This is more consistent with Vim's default behavior.\r\n- Add ingo\/record.vim module.\r\n- ENH: Allow passing optional a:tabnr to ingo#window#preview#IsPreviewWindowVisible().\r\n- Factor out ingo#window#preview#OpenBuffer().\r\n- CHG: Change optional a:cursor argument of ingo#window#preview#SplitToPreview() from 4-tuple getpos()-style to [lnum, col]-style.\r\n- Add ingo\/query\/fromlist.vim module.\r\n- Add ingo\/option.vim module.\r\n- Add ingo\/join.vim module.\r\n- Expose ingo#actions#GetValExpr().\r\n- Add ingo\/range\/lines.vim module.\r\n- ENH: Add a:options.commandExpr to ingo#cmdargs#range#Parse().","package":"ingo-library-1.020.vmb.gz","4":"ingo-library-1.020.vmb.gz","src_id":"22014","5":"22014","creation_date":"1402474218","6":"1402474218"},{"0":"4433","vim_version":"7.0","1":"7.0","script_version":"1.019","2":"1.019","version_comment":"- Add ingo#plugin#setting#BooleanToStringValue().\r\n- Add ingo#strdisplaywidth#GetMinMax().\r\n- Add ingo\/undo.vim module.\r\n- Add ingo\/query.vim module.\r\n- Add ingo\/pos.vim module.\r\n- Add optional a:isBeep argument to ingo#msg#ErrorMsg().\r\n- ingo#fs#path#Normalize(): Don't normalize to Cygwin \/cygdrive\/x\/... when the chosen path separator is \"\\\". This would result in a mixed separator style that is not actually handled.\r\n- ingo#fs#path#Normalize(): Add special normalization to \"C:\/\" on Cygwin via \":\/\" path separator argument.\r\n- In ingo#actions#EvaluateWithValOrFunc(), remove any occurrence of \"v:val\" instead of passing an empty list or empty string. This is useful for invoking functions (an expression, not Funcref) with optional arguments.\r\n- ENH: Make ingo#lines#Replace() handle replacement with nothing (empty List) and replacing the entire buffer (without leaving an additional empty line).\r\n- Correct ingo#query#confirm#AutoAccelerators() default choice when not given (1 instead of 0). Avoid using the default choice's first character as accelerator unless in GUI dialog, as the plain text confirm() assigns a default accelerator.\r\n- Move subs\/URL.vim into ingo-library as ingo\/codec\/URL.vim module.\r\n- Allow optional a:ignorecase argument for ingo#str#StartsWith() and ingo#str#EndsWith().\r\n- Add ingo#fs#path#IsCaseInsensitive().\r\n- Add ingo#str#Equals() for when it's convenient to pass in the a:ignorecase flag. This avoids coding the conditional between ==# and ==? yourself.\r\n- Add ingo\/fs\/path\/split.vim module.\r\n- Add ingo#fs#path#Exists().\r\n- FIX: Correct ingo#escape#file#wildcardescape() of * and ? on Windows.","3":"- Add ingo#plugin#setting#BooleanToStringValue().\r\n- Add ingo#strdisplaywidth#GetMinMax().\r\n- Add ingo\/undo.vim module.\r\n- Add ingo\/query.vim module.\r\n- Add ingo\/pos.vim module.\r\n- Add optional a:isBeep argument to ingo#msg#ErrorMsg().\r\n- ingo#fs#path#Normalize(): Don't normalize to Cygwin \/cygdrive\/x\/... when the chosen path separator is \"\\\". This would result in a mixed separator style that is not actually handled.\r\n- ingo#fs#path#Normalize(): Add special normalization to \"C:\/\" on Cygwin via \":\/\" path separator argument.\r\n- In ingo#actions#EvaluateWithValOrFunc(), remove any occurrence of \"v:val\" instead of passing an empty list or empty string. This is useful for invoking functions (an expression, not Funcref) with optional arguments.\r\n- ENH: Make ingo#lines#Replace() handle replacement with nothing (empty List) and replacing the entire buffer (without leaving an additional empty line).\r\n- Correct ingo#query#confirm#AutoAccelerators() default choice when not given (1 instead of 0). Avoid using the default choice's first character as accelerator unless in GUI dialog, as the plain text confirm() assigns a default accelerator.\r\n- Move subs\/URL.vim into ingo-library as ingo\/codec\/URL.vim module.\r\n- Allow optional a:ignorecase argument for ingo#str#StartsWith() and ingo#str#EndsWith().\r\n- Add ingo#fs#path#IsCaseInsensitive().\r\n- Add ingo#str#Equals() for when it's convenient to pass in the a:ignorecase flag. This avoids coding the conditional between ==# and ==? yourself.\r\n- Add ingo\/fs\/path\/split.vim module.\r\n- Add ingo#fs#path#Exists().\r\n- FIX: Correct ingo#escape#file#wildcardescape() of * and ? on Windows.","package":"ingo-library-1.019.vmb.gz","4":"ingo-library-1.019.vmb.gz","src_id":"21934","5":"21934","creation_date":"1400959164","6":"1400959164"},{"0":"4433","vim_version":"7.0","1":"7.0","script_version":"1.018","2":"1.018","version_comment":"- FIX: Off-by-one: Allow column 1 in ingo#text#Insert(). Add special cases for insertion at front and end of line (in the hope that this is more efficient).\r\n- Add ingo#escape#file#wildcardescape().\r\n- I18N: Correctly capture last multi-byte character in ingo#text#Get(); don't just add one to the end column, but instead match at the column itself, too.\r\n- Add optional a:isExclusive flag to ingo#text#Get(), as clients may end up with that position, and doing a correct I18N-safe decrease before getting the text is a hen-and-egg problem.\r\n- Add ingo\/buffer\/temprange.vim module.\r\n- Add ingo#cursor#IsAtEndOfLine().\r\n- FIX: Off-by-one in emulated ingo#compat#strdisplaywidth() reported one too few.","3":"- FIX: Off-by-one: Allow column 1 in ingo#text#Insert(). Add special cases for insertion at front and end of line (in the hope that this is more efficient).\r\n- Add ingo#escape#file#wildcardescape().\r\n- I18N: Correctly capture last multi-byte character in ingo#text#Get(); don't just add one to the end column, but instead match at the column itself, too.\r\n- Add optional a:isExclusive flag to ingo#text#Get(), as clients may end up with that position, and doing a correct I18N-safe decrease before getting the text is a hen-and-egg problem.\r\n- Add ingo\/buffer\/temprange.vim module.\r\n- Add ingo#cursor#IsAtEndOfLine().\r\n- FIX: Off-by-one in emulated ingo#compat#strdisplaywidth() reported one too few.","package":"ingo-library-1.018.vmb.gz","4":"ingo-library-1.018.vmb.gz","src_id":"21772","5":"21772","creation_date":"1397487115","6":"1397487115"},{"0":"4433","vim_version":"7.0","1":"7.0","script_version":"1.017","2":"1.017","version_comment":"- CHG: Make ingo#cmdargs#file#FilterFileOptionsAndCommands() return the options and commands in a List, not as a joined String. This allows clients to easily re-escape them and handle multiple ones, e.g. ++ff=dos +setf\\ foo.\r\n- Add workarounds for fnameescape() bugs on Windows for ! and [] characters.\r\n- Add ingo#escape#UnescapeExpr().\r\n- Add ingo\/str\/restricted.vim module.\r\n- Make ingo#query#get#Char() only abort on <Esc> when that character is not in the validExpr (to allow to explicitly query it).\r\n- Add ingo\/query\/substitute.vim module.\r\n- Add ingo\/subst\/expr\/emulation.vim module.\r\n- Add ingo\/cmdargs\/register.vim module.","3":"- CHG: Make ingo#cmdargs#file#FilterFileOptionsAndCommands() return the options and commands in a List, not as a joined String. This allows clients to easily re-escape them and handle multiple ones, e.g. ++ff=dos +setf\\ foo.\r\n- Add workarounds for fnameescape() bugs on Windows for ! and [] characters.\r\n- Add ingo#escape#UnescapeExpr().\r\n- Add ingo\/str\/restricted.vim module.\r\n- Make ingo#query#get#Char() only abort on <Esc> when that character is not in the validExpr (to allow to explicitly query it).\r\n- Add ingo\/query\/substitute.vim module.\r\n- Add ingo\/subst\/expr\/emulation.vim module.\r\n- Add ingo\/cmdargs\/register.vim module.","package":"ingo-library-1.017.vmb.gz","4":"ingo-library-1.017.vmb.gz","src_id":"21607","5":"21607","creation_date":"1394703738","6":"1394703738"},{"0":"4433","vim_version":"7.0","1":"7.0","script_version":"1.016","2":"1.016","version_comment":"- Add ingo#window#quickfix#GetList() and ingo#window#quickfix#SetList().\r\n- Add ingo\/cursor.vim module.\r\n- Add ingo#text#Insert() and ingo#text#Remove().\r\n- Add ingo#str#StartsWith() and ingo#str#EndsWith().\r\n- Add ingo#dict#Mirror() and ingo#dict#AddMirrored().\r\n- BUG: Wrap :autocmd! undo_ftplugin_N in :execute to that superordinated ftplugins can append additional undo commands without causing \"E216: No such group or event: undo_ftplugin_N|setlocal\".\r\n- Add ingo\/motion\/helper.vim module.\r\n- Add ingo\/motion\/omap.vim module.\r\n- Add ingo\/subst\/pairs.vim module.\r\n- Add ingo\/plugin\/compiler.vim module.\r\n- Move ingo#escape#shellcommand#shellcmdescape() to ingo#compat#shellcommand#escape(), as it is only required for older Vim versions.","3":"- Add ingo#window#quickfix#GetList() and ingo#window#quickfix#SetList().\r\n- Add ingo\/cursor.vim module.\r\n- Add ingo#text#Insert() and ingo#text#Remove().\r\n- Add ingo#str#StartsWith() and ingo#str#EndsWith().\r\n- Add ingo#dict#Mirror() and ingo#dict#AddMirrored().\r\n- BUG: Wrap :autocmd! undo_ftplugin_N in :execute to that superordinated ftplugins can append additional undo commands without causing \"E216: No such group or event: undo_ftplugin_N|setlocal\".\r\n- Add ingo\/motion\/helper.vim module.\r\n- Add ingo\/motion\/omap.vim module.\r\n- Add ingo\/subst\/pairs.vim module.\r\n- Add ingo\/plugin\/compiler.vim module.\r\n- Move ingo#escape#shellcommand#shellcmdescape() to ingo#compat#shellcommand#escape(), as it is only required for older Vim versions.","package":"ingo-library-1.016.vmb.gz","4":"ingo-library-1.016.vmb.gz","src_id":"21356","5":"21356","creation_date":"1390396034","6":"1390396034"},{"0":"4433","vim_version":"7.0","1":"7.0","script_version":"1.015","2":"1.015","version_comment":"- Add ingo\/format.vim module.\r\n- FIX: Actually return the result of a Funcref passed to ingo#register#KeepRegisterExecuteOrFunc().\r\n- Make buffer argument of ingo#buffer#IsBlank() optional, defaulting to the current buffer.\r\n- Allow use of ingo#buffer#IsEmpty() with other buffers.\r\n- CHG: Pass _all_ additional arguments of ingo#actions#ValueOrFunc(), ingo#actions#NormalOrFunc(), ingo#actions#ExecuteOrFunc(), ingo#actions#EvaluateOrFunc() instead of only the first (interpreted as a List of arguments) when passed a Funcref as a:Action.\r\n- Add ingo#compat#setpos().\r\n- Add ingo\/print.vim module.","3":"- Add ingo\/format.vim module.\r\n- FIX: Actually return the result of a Funcref passed to ingo#register#KeepRegisterExecuteOrFunc().\r\n- Make buffer argument of ingo#buffer#IsBlank() optional, defaulting to the current buffer.\r\n- Allow use of ingo#buffer#IsEmpty() with other buffers.\r\n- CHG: Pass _all_ additional arguments of ingo#actions#ValueOrFunc(), ingo#actions#NormalOrFunc(), ingo#actions#ExecuteOrFunc(), ingo#actions#EvaluateOrFunc() instead of only the first (interpreted as a List of arguments) when passed a Funcref as a:Action.\r\n- Add ingo#compat#setpos().\r\n- Add ingo\/print.vim module.","package":"ingo-library-1.015.vmb.gz","4":"ingo-library-1.015.vmb.gz","src_id":"21122","5":"21122","creation_date":"1385654738","6":"1385654738"},{"0":"4433","vim_version":"7.0","1":"7.0","script_version":"1.014","2":"1.014","version_comment":"- Add ingo\/date\/format.vim module.\r\n- Add ingo#os#PathSeparator().\r\n- Add ingo\/foldtext.vim module.\r\n- Add ingo#os#IsCygwin().\r\n- ingo#fs#path#Normalize(): Also convert between the different D:\\ and \/cygdrive\/d\/ notations on Windows and Cygwin.\r\n- Add ingo#text#frompattern#GetHere().\r\n- Add ingo\/date\/epoch.vim module.\r\n- Add ingo#buffer#IsPersisted().\r\n- Add ingo\/list.vim module.\r\n- Add ingo\/query\/confirm.vim module.\r\n- Add ingo#text#GetChar().\r\n- Add ingo\/regexp\/fromwildcard.vim module (contributed by the EditSimilar.vim\r\n  plugin). In constrast to the simpler ingo#regexp#FromWildcard(), this\r\n  handles the full range of wildcards and considers the path separators on\r\n  different platforms.\r\n- Add ingo#register#KeepRegisterExecuteOrFunc().\r\n- Add ingo#actions#ValueOrFunc().\r\n- Add ingo\/funcref.vim module.\r\n- Add month and year granularity to ingo#date#HumanReltime().\r\n- Add ingo\/units.vim module.","3":"- Add ingo\/date\/format.vim module.\r\n- Add ingo#os#PathSeparator().\r\n- Add ingo\/foldtext.vim module.\r\n- Add ingo#os#IsCygwin().\r\n- ingo#fs#path#Normalize(): Also convert between the different D:\\ and \/cygdrive\/d\/ notations on Windows and Cygwin.\r\n- Add ingo#text#frompattern#GetHere().\r\n- Add ingo\/date\/epoch.vim module.\r\n- Add ingo#buffer#IsPersisted().\r\n- Add ingo\/list.vim module.\r\n- Add ingo\/query\/confirm.vim module.\r\n- Add ingo#text#GetChar().\r\n- Add ingo\/regexp\/fromwildcard.vim module (contributed by the EditSimilar.vim\r\n  plugin). In constrast to the simpler ingo#regexp#FromWildcard(), this\r\n  handles the full range of wildcards and considers the path separators on\r\n  different platforms.\r\n- Add ingo#register#KeepRegisterExecuteOrFunc().\r\n- Add ingo#actions#ValueOrFunc().\r\n- Add ingo\/funcref.vim module.\r\n- Add month and year granularity to ingo#date#HumanReltime().\r\n- Add ingo\/units.vim module.","package":"ingo-library-1.014.vmb.gz","4":"ingo-library-1.014.vmb.gz","src_id":"21041","5":"21041","creation_date":"1384418494","6":"1384418494"},{"0":"4433","vim_version":"7.0","1":"7.0","script_version":"1.013","2":"1.013","version_comment":"- Also avoid clobbering the last change ('.') in ingo#selection#Get() when 'cpo' contains \"y\".\r\n- Name the temp buffer for ingo#buffer#temp#Execute() and re-use previous instances to avoid increasing the buffer numbers and output of :ls!.\r\n- CHG: Make a:isIgnoreIndent flag to ingo#comments#CheckComment() optional and add a:isStripNonEssentialWhiteSpaceFromCommentString, which is also on by default for DWIM.\r\n- CHG: Don't strip whitespace in ingo#comments#RemoveCommentPrefix(); with the changed ingo#comments#CheckComment() default behavior, this isn't necessary, and is unexpected.\r\n- ingo#comments#RenderComment: When the text starts with indent identical to what 'commentstring' would render, avoid having duplicate indent.\r\n- Minor: Return last search pattern instead of empty string on ingo#search#pattern#GetLastForwardSearch(0).\r\n- Avoid using \\ze in ingo#regexp#comments#CommentToExpression(). It may be used in a larger expression that still wants to match after the prefix.\r\n- FIX: Correct case of ingo#os#IsWin*() function names.\r\n- ingo#regexp#FromWildcard(): Limit * glob matching to individual path components and add ** for cross-directory matching.\r\n- Consistently use operating system detection functions from ingo\/os.vim within the ingo-library.","3":"- Also avoid clobbering the last change ('.') in ingo#selection#Get() when 'cpo' contains \"y\".\r\n- Name the temp buffer for ingo#buffer#temp#Execute() and re-use previous instances to avoid increasing the buffer numbers and output of :ls!.\r\n- CHG: Make a:isIgnoreIndent flag to ingo#comments#CheckComment() optional and add a:isStripNonEssentialWhiteSpaceFromCommentString, which is also on by default for DWIM.\r\n- CHG: Don't strip whitespace in ingo#comments#RemoveCommentPrefix(); with the changed ingo#comments#CheckComment() default behavior, this isn't necessary, and is unexpected.\r\n- ingo#comments#RenderComment: When the text starts with indent identical to what 'commentstring' would render, avoid having duplicate indent.\r\n- Minor: Return last search pattern instead of empty string on ingo#search#pattern#GetLastForwardSearch(0).\r\n- Avoid using \\ze in ingo#regexp#comments#CommentToExpression(). It may be used in a larger expression that still wants to match after the prefix.\r\n- FIX: Correct case of ingo#os#IsWin*() function names.\r\n- ingo#regexp#FromWildcard(): Limit * glob matching to individual path components and add ** for cross-directory matching.\r\n- Consistently use operating system detection functions from ingo\/os.vim within the ingo-library.","package":"ingo-library-1.013.vmb.gz","4":"ingo-library-1.013.vmb.gz","src_id":"20799","5":"20799","creation_date":"1379102696","6":"1379102696"},{"0":"4433","vim_version":"7.0","1":"7.0","script_version":"1.012","2":"1.012","version_comment":"- CHG: Change return value format of ingo#selection#frompattern#GetPositions() to better match the arguments of functions like ingo#text#Get().\r\n- Add ingo\/os.vim module.\r\n- Add ingo#compat#fnameescape() and ingo#compat#shellescape() from escapings.vim.\r\n- Add remaining former escapings.vim functions as ingo\/escape\/shellcommand.vim\r\n  and ingo\/escape\/file.vim modules.\r\n- Add ingo\/motion\/boundary.vim module.\r\n- Add ingo#compat#maparg().\r\n- Add ingo\/escape\/command.vim module.\r\n- Add ingo\/text\/frompattern.vim module.","3":"- CHG: Change return value format of ingo#selection#frompattern#GetPositions() to better match the arguments of functions like ingo#text#Get().\r\n- Add ingo\/os.vim module.\r\n- Add ingo#compat#fnameescape() and ingo#compat#shellescape() from escapings.vim.\r\n- Add remaining former escapings.vim functions as ingo\/escape\/shellcommand.vim\r\n  and ingo\/escape\/file.vim modules.\r\n- Add ingo\/motion\/boundary.vim module.\r\n- Add ingo#compat#maparg().\r\n- Add ingo\/escape\/command.vim module.\r\n- Add ingo\/text\/frompattern.vim module.","package":"ingo-library-1.012.vmb.gz","4":"ingo-library-1.012.vmb.gz","src_id":"20754","5":"20754","creation_date":"1378377594","6":"1378377594"},{"0":"4433","vim_version":"7.0","1":"7.0","script_version":"1.011","2":"1.011","version_comment":"- Add ingo\/range.vim module.\r\n- Add ingo\/register.vim module.\r\n- Make ingo#collections#ToDict() handle empty list items via an optional a:emptyValue argument. This also distinguishes it from ingo#dict#FromKeys().\r\n- ENH: Handle empty list items in ingo#collections#Unique() and ingo#collections#UniqueStable().\r\n- Add ingo\/gui\/position.vim module.\r\n- Add ingo\/filetype.vim module.\r\n- Add ingo\/ftplugin\/onbufwinenter.vim module.\r\n- Add ingo\/selection\/frompattern.vim module.\r\n- Add ingo\/text.vim module.\r\n- Add ingo\/ftplugin\/windowsettings.vim module.\r\n- Add ingo\/text\/replace.vim module.\r\n- FIX: Use the rules for the \/pattern\/ separator as stated in :help E146 for ingo#cmdargs#pattern#Parse() and ingo#cmdargs#substitute#Parse().\r\n- FIX: Off-by-one in ingo#strdisplaywidth#HasMoreThan() and ingo#strdisplaywidth#strleft().\r\n- Add ingo#str#Reverse().\r\n- ingo#fs#traversal#FindLastContainedInUpDir now defaults to the current buffer's directory; omit the argument.\r\n- Add ingo#actions#EvaluateWithValOrFunc().\r\n- Extract ingo#fs#path#IsUncPathRoot().\r\n- Add ingo#fs#traversal#FindDirUpwards().","3":"- Add ingo\/range.vim module.\r\n- Add ingo\/register.vim module.\r\n- Make ingo#collections#ToDict() handle empty list items via an optional a:emptyValue argument. This also distinguishes it from ingo#dict#FromKeys().\r\n- ENH: Handle empty list items in ingo#collections#Unique() and ingo#collections#UniqueStable().\r\n- Add ingo\/gui\/position.vim module.\r\n- Add ingo\/filetype.vim module.\r\n- Add ingo\/ftplugin\/onbufwinenter.vim module.\r\n- Add ingo\/selection\/frompattern.vim module.\r\n- Add ingo\/text.vim module.\r\n- Add ingo\/ftplugin\/windowsettings.vim module.\r\n- Add ingo\/text\/replace.vim module.\r\n- FIX: Use the rules for the \/pattern\/ separator as stated in :help E146 for ingo#cmdargs#pattern#Parse() and ingo#cmdargs#substitute#Parse().\r\n- FIX: Off-by-one in ingo#strdisplaywidth#HasMoreThan() and ingo#strdisplaywidth#strleft().\r\n- Add ingo#str#Reverse().\r\n- ingo#fs#traversal#FindLastContainedInUpDir now defaults to the current buffer's directory; omit the argument.\r\n- Add ingo#actions#EvaluateWithValOrFunc().\r\n- Extract ingo#fs#path#IsUncPathRoot().\r\n- Add ingo#fs#traversal#FindDirUpwards().","package":"ingo-library-1.011.vmb.gz","4":"ingo-library-1.011.vmb.gz","src_id":"20589","5":"20589","creation_date":"1375429457","6":"1375429457"},{"0":"4433","vim_version":"7.0","1":"7.0","script_version":"1.010","2":"1.010","version_comment":"- Add ingo\/actions.vim module.\r\n- Add ingo\/cursor\/move.vim module.\r\n- Add ingo#collections#unique#AddNew() and ingo#collections#unique#InsertNew().\r\n- Add ingo\/selection\/position.vim module.\r\n- Add ingo\/plugin\/marks.vim module.\r\n- Add ingo\/date.vim module.\r\n- Add ingo#buffer#IsEmpty().\r\n- Add ingo\/buffer\/scratch.vim module.\r\n- Add ingo\/cmdargs\/command.vim module.\r\n- Add ingo\/cmdargs\/commandcommands.vim module.\r\n- Add ingo\/cmdargs\/range.vim module.","3":"- Add ingo\/actions.vim module.\r\n- Add ingo\/cursor\/move.vim module.\r\n- Add ingo#collections#unique#AddNew() and ingo#collections#unique#InsertNew().\r\n- Add ingo\/selection\/position.vim module.\r\n- Add ingo\/plugin\/marks.vim module.\r\n- Add ingo\/date.vim module.\r\n- Add ingo#buffer#IsEmpty().\r\n- Add ingo\/buffer\/scratch.vim module.\r\n- Add ingo\/cmdargs\/command.vim module.\r\n- Add ingo\/cmdargs\/commandcommands.vim module.\r\n- Add ingo\/cmdargs\/range.vim module.","package":"ingo-library-1.010.vmb.gz","4":"ingo-library-1.010.vmb.gz","src_id":"20500","5":"20500","creation_date":"1373354099","6":"1373354099"},{"0":"4433","vim_version":"7.0","1":"7.0","script_version":"1.009","2":"1.009","version_comment":"- Minor: Make substitute() robust against 'ignorecase' in various functions.\r\n- Add ingo\/subst.vim module.\r\n- Add ingo\/escape.vim module.\r\n- Add ingo\/regexp\/comments.vim module.\r\n- Add ingo\/cmdline\/showmode.vim module.\r\n- Add ingo\/str.vim module.\r\n- Add ingo\/strdisplaywidth\/pad.vim module.\r\n- Add ingo\/dict.vim module.\r\n- Add ingo#msg#HighlightMsg(), and allow to pass an optional highlight group to ingo#msg#StatusMsg().\r\n- Add ingo#collections#Flatten() and ingo#collections#Flatten1().\r\n- Move ingo#collections#MakeUnique() to ingo\/collections\/unique.vim.\r\n- Add ingo#collections#unique#ExtendWithNew().\r\n- Add ingo#fs#path#Equals().\r\n- Add ingo#tabstops#RenderMultiLine(), as ingo#tabstops#Render() does not properly render multi-line text.\r\n- Add ingo\/str\/split.vim module.\r\n- FIX: Avoid E108: No such variable: \"b:browsefilter\" in ingo#query#file#Browse().","3":"- Minor: Make substitute() robust against 'ignorecase' in various functions.\r\n- Add ingo\/subst.vim module.\r\n- Add ingo\/escape.vim module.\r\n- Add ingo\/regexp\/comments.vim module.\r\n- Add ingo\/cmdline\/showmode.vim module.\r\n- Add ingo\/str.vim module.\r\n- Add ingo\/strdisplaywidth\/pad.vim module.\r\n- Add ingo\/dict.vim module.\r\n- Add ingo#msg#HighlightMsg(), and allow to pass an optional highlight group to ingo#msg#StatusMsg().\r\n- Add ingo#collections#Flatten() and ingo#collections#Flatten1().\r\n- Move ingo#collections#MakeUnique() to ingo\/collections\/unique.vim.\r\n- Add ingo#collections#unique#ExtendWithNew().\r\n- Add ingo#fs#path#Equals().\r\n- Add ingo#tabstops#RenderMultiLine(), as ingo#tabstops#Render() does not properly render multi-line text.\r\n- Add ingo\/str\/split.vim module.\r\n- FIX: Avoid E108: No such variable: \"b:browsefilter\" in ingo#query#file#Browse().","package":"ingo-library-1.009.vmb.gz","4":"ingo-library-1.009.vmb.gz","src_id":"20476","5":"20476","creation_date":"1372861298","6":"1372861298"},{"0":"4433","vim_version":"7.0","1":"7.0","script_version":"1.008","2":"1.008","version_comment":"- Fix missing argument error for ingo#query#file#BrowseDirForOpenFile() and ingo#query#file#BrowseDirForAction().\r\n- Implement ingo#compat#strdisplaywidth() emulation inside the library; EchoWithoutScrolling.vim isn't used for that any more.\r\n- Add ingo\/avoidprompt.vim, ingo\/strdisplaywidth.vim, and ingo\/tabstops modules, containing the former EchoWithoutScrolling.vim functions.\r\n- Add ingo\/buffer\/temp.vim and ingo\/buffer\/visible.vim modules.\r\n- Add ingo\/regexp\/previoussubstitution.vim module.","3":"- Fix missing argument error for ingo#query#file#BrowseDirForOpenFile() and ingo#query#file#BrowseDirForAction().\r\n- Implement ingo#compat#strdisplaywidth() emulation inside the library; EchoWithoutScrolling.vim isn't used for that any more.\r\n- Add ingo\/avoidprompt.vim, ingo\/strdisplaywidth.vim, and ingo\/tabstops modules, containing the former EchoWithoutScrolling.vim functions.\r\n- Add ingo\/buffer\/temp.vim and ingo\/buffer\/visible.vim modules.\r\n- Add ingo\/regexp\/previoussubstitution.vim module.","package":"ingo-library-1.008.vmb.gz","4":"ingo-library-1.008.vmb.gz","src_id":"20346","5":"20346","creation_date":"1371110290","6":"1371110290"},{"0":"4433","vim_version":"7.0","1":"7.0","script_version":"1.007","2":"1.007","version_comment":"- Add ingo\/query\/get.vim module.\r\n- Add ingo\/query\/file.vim module.\r\n- Add ingo\/fs\/path.vim module.\r\n- Add ingo\/fs\/tempfile.vim module.\r\n- Add ingo\/cmdargs\/file.vim module.\r\n- Add ingo\/cmdargs\/glob.vim module.\r\n- CHG: Move most functions from ingo\/cmdargs.vim to new modules ingo\/cmdargs\/pattern.vim and ingo\/cmdargs\/substitute.vim.\r\n- Add ingo\/compat\/complete.vim module.","3":"- Add ingo\/query\/get.vim module.\r\n- Add ingo\/query\/file.vim module.\r\n- Add ingo\/fs\/path.vim module.\r\n- Add ingo\/fs\/tempfile.vim module.\r\n- Add ingo\/cmdargs\/file.vim module.\r\n- Add ingo\/cmdargs\/glob.vim module.\r\n- CHG: Move most functions from ingo\/cmdargs.vim to new modules ingo\/cmdargs\/pattern.vim and ingo\/cmdargs\/substitute.vim.\r\n- Add ingo\/compat\/complete.vim module.","package":"ingo-library-1.007.vmb.gz","4":"ingo-library-1.007.vmb.gz","src_id":"20306","5":"20306","creation_date":"1370508678","6":"1370508678"},{"0":"4433","vim_version":"7.0","1":"7.0","script_version":"1.006","2":"1.006","version_comment":"- Add ingo\/cmdrangeconverter.vim module.\r\n- Add ingo#mapmaker.vim module.\r\n- Add optional isReturnError flag on ingo#window#switches#GotoPreviousWindow().\r\n- Add ingo#msg#StatusMsg().\r\n- Add ingo\/selection\/patternmatch.vim module.\r\n- Add ingo\/selection.vim module.\r\n- Add ingo\/search\/pattern.vim module.\r\n- Add ingo\/regexp.vim module.\r\n- Add ingo\/regexp\/magic.vim module.\r\n- Add ingo\/collections\/rotate.vim module.\r\n- Redesign ingo#cmdargs#ParseSubstituteArgument() to the existing use cases.\r\n- Add ingo\/buffer.vim module.","3":"- Add ingo\/cmdrangeconverter.vim module.\r\n- Add ingo#mapmaker.vim module.\r\n- Add optional isReturnError flag on ingo#window#switches#GotoPreviousWindow().\r\n- Add ingo#msg#StatusMsg().\r\n- Add ingo\/selection\/patternmatch.vim module.\r\n- Add ingo\/selection.vim module.\r\n- Add ingo\/search\/pattern.vim module.\r\n- Add ingo\/regexp.vim module.\r\n- Add ingo\/regexp\/magic.vim module.\r\n- Add ingo\/collections\/rotate.vim module.\r\n- Redesign ingo#cmdargs#ParseSubstituteArgument() to the existing use cases.\r\n- Add ingo\/buffer.vim module.","package":"ingo-library-1.006.vmb.gz","4":"ingo-library-1.006.vmb.gz","src_id":"20227","5":"20227","creation_date":"1369824868","6":"1369824868"},{"0":"4433","vim_version":"7.0","1":"7.0","script_version":"1.005","2":"1.005","version_comment":"- Add ingo\/plugin\/setting.vim module.\r\n- Add ingo\/plugin\/cmdcomplete.vim module.\r\n- Add ingo\/search\/buffer.vim module.\r\n- Add ingo\/number.vim module.\r\n- Add ingo\/cmdrangeconverter.vim module.\r\n- Add ingo#err#IsSet() for those cases when wrapping the command in :if does\r\n  not work (e.g. :call'ing a range function).\r\n- Add ingo#mapmaker.vim module.\r\n- Add ingo#syntaxitem.vim module.\r\n- Add ingo#comments.vim module.","3":"- Add ingo\/plugin\/setting.vim module.\r\n- Add ingo\/plugin\/cmdcomplete.vim module.\r\n- Add ingo\/search\/buffer.vim module.\r\n- Add ingo\/number.vim module.\r\n- Add ingo\/cmdrangeconverter.vim module.\r\n- Add ingo#err#IsSet() for those cases when wrapping the command in :if does\r\n  not work (e.g. :call'ing a range function).\r\n- Add ingo#mapmaker.vim module.\r\n- Add ingo#syntaxitem.vim module.\r\n- Add ingo#comments.vim module.","package":"ingo-library-1.005.vmb.gz","4":"ingo-library-1.005.vmb.gz","src_id":"20010","5":"20010","creation_date":"1367497810","6":"1367497810"},{"0":"4433","vim_version":"7.0","1":"7.0","script_version":"1.004","2":"1.004","version_comment":"- Add ingo\/compat.vim module.\r\n- Add ingo\/lines module.\r\n- Add ingo\/matches module.\r\n- Add ingo\/mbyte\/virtcol module.\r\n- Add ingo\/window\/* modules.\r\n- FIX: ingo#external#LaunchGvim() broken with \"E117: Unknown function: s:externalLaunch\".","3":"- Add ingo\/compat.vim module.\r\n- Add ingo\/lines module.\r\n- Add ingo\/matches module.\r\n- Add ingo\/mbyte\/virtcol module.\r\n- Add ingo\/window\/* modules.\r\n- FIX: ingo#external#LaunchGvim() broken with \"E117: Unknown function: s:externalLaunch\".","package":"ingo-library-1.004.vmb.gz","4":"ingo-library-1.004.vmb.gz","src_id":"19794","5":"19794","creation_date":"1365607162","6":"1365607162"},{"0":"4433","vim_version":"7.0","1":"7.0","script_version":"1.003","2":"1.003","version_comment":"- Add ingo#msg#ShellError().\r\n- Add ingo#system#Chomped().\r\n- Add ingo\/fs\/traversal.vim module.\r\n- Add search\/timelimited.vim module.","3":"- Add ingo#msg#ShellError().\r\n- Add ingo#system#Chomped().\r\n- Add ingo\/fs\/traversal.vim module.\r\n- Add search\/timelimited.vim module.","package":"ingo-library-1.003.vmb.gz","4":"ingo-library-1.003.vmb.gz","src_id":"19712","5":"19712","creation_date":"1364417717","6":"1364417717"},{"0":"4433","vim_version":"7.0","1":"7.0","script_version":"1.002","2":"1.002","version_comment":"- Minor: Allow to specify filespec of GVIM executable in ingo#external#LaunchGvim().\r\n- Add err module for LineJugglerCommands.vim plugin.","3":"- Minor: Allow to specify filespec of GVIM executable in ingo#external#LaunchGvim().\r\n- Add err module for LineJugglerCommands.vim plugin.","package":"ingo-library-1.002.vmb.gz","4":"ingo-library-1.002.vmb.gz","src_id":"19605","5":"19605","creation_date":"1362774738","6":"1362774738"},{"0":"4433","vim_version":"7.0","1":"7.0","script_version":"1.001","2":"1.001","version_comment":"Add cmdargs and collections modules for use by PatternsOnText.vim plugin.","3":"Add cmdargs and collections modules for use by PatternsOnText.vim plugin.","package":"ingo-library-1.001.vmb.gz","4":"ingo-library-1.001.vmb.gz","src_id":"19557","5":"19557","creation_date":"1361458108","6":"1361458108"},{"0":"4433","vim_version":"7.0","1":"7.0","script_version":"1.000","2":"1.000","version_comment":"Initial upload","3":"Initial upload","package":"ingo-library-1.000.vmb.gz","4":"ingo-library-1.000.vmb.gz","src_id":"19499","5":"19499","creation_date":"1360686458","6":"1360686458"}]},"4432":{"script_id":"4432","0":"4432","script_name":"zoomwintab.vim","1":"zoomwintab.vim","script_type":"utility","2":"utility","summary":"zoomwintab.vim is a simple zoom window plugin","3":"zoomwintab.vim is a simple zoom window plugin","description":"zoomwintab.vim is a simple zoom window plugin that uses vim's tabs feature to zoom into a window inspired by ZoomWin plugin","4":"zoomwintab.vim is a simple zoom window plugin that uses vim's tabs feature to zoom into a window inspired by ZoomWin plugin","install_details":"","5":"","first_name":"Dmitry","6":"Dmitry","last_name":"Geurkov","7":"Geurkov","releases":[{"0":"4432","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"zoomwintab.vim-0.1.zip","4":"zoomwintab.vim-0.1.zip","src_id":"19497","5":"19497","creation_date":"1360674596","6":"1360674596"}]},"4431":{"script_id":"4431","0":"4431","script_name":"tcd.vim","1":"tcd.vim","script_type":"utility","2":"utility","summary":"Tab-specific directories","3":"Tab-specific directories","description":"Tab-specific directories\r\nFor Vim version 7.x\r\n\r\nTcd lets you set a working directory for a specific tab. Great if you've\r\ngot a session open and are editing some file in another location on the\r\nfilesystem, and decide you need to open more files in that directory.\r\nThis plugin works particularly well in combination with NERD_Tree.vim\r\n\r\n=============================================================================\r\nGlobal Commands\r\n\r\n:Tcd <dir>\r\n\r\nChanges the current working directory, but only in your current tab.\r\nWhen you enter this tab, the specified path will become your current\r\nworking directory. Saves the real current working directory, so when you\r\nexit this tab, you will return to your prior location.\r\n\r\n=============================================================================\r\nKnown Issues\r\n\r\n  1. The \"old cwd\" (the one you switch to when leaving the tab in which you\r\n     called :Tcd) is set the first time you call :Tcd. This means that if\r\n     change your working directory later with the built-in :cd command, this\r\n     new location will be ignored when leaving :Tcd tabs.\r\n\r\n     Workaround: Don't use :cd if you are still using :Tcd tabs. Instead,\r\n     call :Tcd in other tabs. I don't expect there to be a real fix for this\r\n     unless Vim adds some autocommand that is run whenever the current\r\n     working directory changes.\r\n\r\n=============================================================================\r\nLicense\r\n\r\ntcd.vim is released under the MIT license. See the comments at the head of\r\ntcd.vim for the full license text, or the \"COPYING\" file you should have\r\nreceived with your copy of this software.\r\n","4":"Tab-specific directories\r\nFor Vim version 7.x\r\n\r\nTcd lets you set a working directory for a specific tab. Great if you've\r\ngot a session open and are editing some file in another location on the\r\nfilesystem, and decide you need to open more files in that directory.\r\nThis plugin works particularly well in combination with NERD_Tree.vim\r\n\r\n=============================================================================\r\nGlobal Commands\r\n\r\n:Tcd <dir>\r\n\r\nChanges the current working directory, but only in your current tab.\r\nWhen you enter this tab, the specified path will become your current\r\nworking directory. Saves the real current working directory, so when you\r\nexit this tab, you will return to your prior location.\r\n\r\n=============================================================================\r\nKnown Issues\r\n\r\n  1. The \"old cwd\" (the one you switch to when leaving the tab in which you\r\n     called :Tcd) is set the first time you call :Tcd. This means that if\r\n     change your working directory later with the built-in :cd command, this\r\n     new location will be ignored when leaving :Tcd tabs.\r\n\r\n     Workaround: Don't use :cd if you are still using :Tcd tabs. Instead,\r\n     call :Tcd in other tabs. I don't expect there to be a real fix for this\r\n     unless Vim adds some autocommand that is run whenever the current\r\n     working directory changes.\r\n\r\n=============================================================================\r\nLicense\r\n\r\ntcd.vim is released under the MIT license. See the comments at the head of\r\ntcd.vim for the full license text, or the \"COPYING\" file you should have\r\nreceived with your copy of this software.\r\n","install_details":"1. Download tcd.zip\r\n2. Unzip tcd.zip\r\n3. Copy plugin\/tcd.vim and doc\/tcd.txt to your .vim or _vim's respective plugin, doc directories.\r\n4. Run :helptags on your doc directory, as with other Vim script packages.","5":"1. Download tcd.zip\r\n2. Unzip tcd.zip\r\n3. Copy plugin\/tcd.vim and doc\/tcd.txt to your .vim or _vim's respective plugin, doc directories.\r\n4. Run :helptags on your doc directory, as with other Vim script packages.","first_name":"Thomas","6":"Thomas","last_name":"Allen","7":"Allen","releases":[{"0":"4431","vim_version":"7.0","1":"7.0","script_version":"1.0.1","2":"1.0.1","version_comment":"Fix bad global function definition.","3":"Fix bad global function definition.","package":"tcd.zip","4":"tcd.zip","src_id":"23395","5":"23395","creation_date":"1434472108","6":"1434472108"},{"0":"4431","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"tcd.zip","4":"tcd.zip","src_id":"19496","5":"19496","creation_date":"1360631574","6":"1360631574"}]},"4430":{"script_id":"4430","0":"4430","script_name":"Vimogen","1":"Vimogen","script_type":"utility","2":"utility","summary":"Vim Plugin Manager for Pathogen","3":"Vim Plugin Manager for Pathogen","description":"For full instructions and the latest version of Vimogen, see: https:\/\/github.com\/rkulla\/vimogen\r\n\r\nVimogen is perhaps the easiest way to install, remove and update Vim plugins.\r\n\r\nEssentially a Pathogen bundle manager for vim plugins, by way of a shell script that updates your Git checkouts, Vimogen can install or update all of your plugins at once.\r\n\r\nCreate a text file in your home directory called .vimogen_repos (or let vimogen generate one for you) and put git URLs to Vim plugins in it, one line at a time, like:\r\n\r\n    https:\/\/github.com\/fatih\/vim-go\r\n    https:\/\/github.com\/tpope\/vim-surround\r\n    https:\/\/github.com\/tpope\/vim-rails\r\n    ...\r\n\r\nFortunately, all of the plug-ins on vim.org are mirrored on Github here: https:\/\/github.com\/vim-scripts\/\r\n\r\nRunning vimogen will give you the option to install, update, or uninstall the Vim plugins you specified in .vimogen_repos:\r\n\r\n    1) INSTALL\r\n    2) UNINSTALL\r\n    3) UPDATE\r\n    4) EXIT\r\n    Enter the number of the menu option to perform: 1\r\n\r\nIf you choose INSTALL, then it will a \"git clone\" on each of the git repositories that you specified in ~\/.vimogen_repos into your Pathogen dir (~\/.vim\/bundle). It will skip any directories that already exist. You can also append new plugin repos to the .vimogen_repos file later and install them incrementally by re-running Vimogen\\\\\\'s install command.\r\n\r\nIf you choose 2 to UNINSTALL, it will give you a list of all your plugins to choose from:\r\n\r\n    1) EXIT\r\n    2) ctrlp\r\n    3) nerdtree\r\n    4) pydiction\r\n    5) vim-fugitive\r\n    6) vim-surround\r\n    7) ZenCoding\r\n    Enter the number of the plugin you wish to uninstall:\r\n\r\nIf you choose UPDATE, then it will run a \"git pull\" on all your bundles. This way you can stay up-to-date with all the new features the plugin authors create, just by re-running this command often.\r\n\r\nYou can also update from the command-line (useful in scripts) with:\r\n\r\n    $ vimogen update\r\n\r\nTo see a list of what plugins your vimogen_repos file currently contains:\r\n\r\n    $ vimogen heap","4":"For full instructions and the latest version of Vimogen, see: https:\/\/github.com\/rkulla\/vimogen\r\n\r\nVimogen is perhaps the easiest way to install, remove and update Vim plugins.\r\n\r\nEssentially a Pathogen bundle manager for vim plugins, by way of a shell script that updates your Git checkouts, Vimogen can install or update all of your plugins at once.\r\n\r\nCreate a text file in your home directory called .vimogen_repos (or let vimogen generate one for you) and put git URLs to Vim plugins in it, one line at a time, like:\r\n\r\n    https:\/\/github.com\/fatih\/vim-go\r\n    https:\/\/github.com\/tpope\/vim-surround\r\n    https:\/\/github.com\/tpope\/vim-rails\r\n    ...\r\n\r\nFortunately, all of the plug-ins on vim.org are mirrored on Github here: https:\/\/github.com\/vim-scripts\/\r\n\r\nRunning vimogen will give you the option to install, update, or uninstall the Vim plugins you specified in .vimogen_repos:\r\n\r\n    1) INSTALL\r\n    2) UNINSTALL\r\n    3) UPDATE\r\n    4) EXIT\r\n    Enter the number of the menu option to perform: 1\r\n\r\nIf you choose INSTALL, then it will a \"git clone\" on each of the git repositories that you specified in ~\/.vimogen_repos into your Pathogen dir (~\/.vim\/bundle). It will skip any directories that already exist. You can also append new plugin repos to the .vimogen_repos file later and install them incrementally by re-running Vimogen\\\\\\'s install command.\r\n\r\nIf you choose 2 to UNINSTALL, it will give you a list of all your plugins to choose from:\r\n\r\n    1) EXIT\r\n    2) ctrlp\r\n    3) nerdtree\r\n    4) pydiction\r\n    5) vim-fugitive\r\n    6) vim-surround\r\n    7) ZenCoding\r\n    Enter the number of the plugin you wish to uninstall:\r\n\r\nIf you choose UPDATE, then it will run a \"git pull\" on all your bundles. This way you can stay up-to-date with all the new features the plugin authors create, just by re-running this command often.\r\n\r\nYou can also update from the command-line (useful in scripts) with:\r\n\r\n    $ vimogen update\r\n\r\nTo see a list of what plugins your vimogen_repos file currently contains:\r\n\r\n    $ vimogen heap","install_details":"     $ git clone https:\/\/github.com\/rkulla\/vimogen\r\n     $ cp vimogen to your $PATH and make sure it's executable","5":"     $ git clone https:\/\/github.com\/rkulla\/vimogen\r\n     $ cp vimogen to your $PATH and make sure it's executable","first_name":"ryan","6":"ryan","last_name":"kulla","7":"kulla","releases":[{"0":"4430","vim_version":"7.0","1":"7.0","script_version":"1.4.2","2":"1.4.2","version_comment":"Fixes some bugs and adds new arguments \"heap\" and \"update\"","3":"Fixes some bugs and adds new arguments \"heap\" and \"update\"","package":"vimogen-1.4.2.zip","4":"vimogen-1.4.2.zip","src_id":"24459","5":"24459","creation_date":"1471730916","6":"1471730916"},{"0":"4430","vim_version":"7.0","1":"7.0","script_version":"1.4.1","2":"1.4.1","version_comment":"Adds better user interface","3":"Adds better user interface","package":"vimogen-1.4.1.zip","4":"vimogen-1.4.1.zip","src_id":"21676","5":"21676","creation_date":"1395895629","6":"1395895629"},{"0":"4430","vim_version":"7.0","1":"7.0","script_version":"1.4","2":"1.4","version_comment":"New features and bug fixes. See README","3":"New features and bug fixes. See README","package":"vimogen-1.4.zip","4":"vimogen-1.4.zip","src_id":"21646","5":"21646","creation_date":"1395355843","6":"1395355843"},{"0":"4430","vim_version":"7.0","1":"7.0","script_version":"1.3","2":"1.3","version_comment":"Fixed a bug with skipping directories.Documentation enhancements.","3":"Fixed a bug with skipping directories.Documentation enhancements.","package":"vimogen-1.3.zip","4":"vimogen-1.3.zip","src_id":"19504","5":"19504","creation_date":"1360734596","6":"1360734596"},{"0":"4430","vim_version":"7.0","1":"7.0","script_version":"1.2","2":"1.2","version_comment":"Initial upload","3":"Initial upload","package":"vimogen-1.2.zip","4":"vimogen-1.2.zip","src_id":"19495","5":"19495","creation_date":"1360617731","6":"1360617731"}]},"4429":{"script_id":"4429","0":"4429","script_name":" Mini Year Todo & Gantt Planner for VIM ","1":" Mini Year Todo & Gantt Planner for VIM ","script_type":"utility","2":"utility","summary":"Draw a todo list and its Gantt chart over the year ","3":"Draw a todo list and its Gantt chart over the year ","description":"\r\n\r\n\"\r\n\" Mini Year Planner for VIM \r\n\" version 0.01\r\n\"\r\n\" Needs some joint efforts for a newer release, please.\r\n\" todo:\r\n\" Simple Tabulation of the months\r\n \r\n\" -----------------------------------------------------------\r\n\" How to ? \r\n\" Select the first line (###################) with shift+v \r\n\" then press ,q \r\n\" and you will see that it will attempt to draw you the tabs for the year \r\n\" If you enter 1testa;2    then it will prolongate the \"#\" line to reach the\r\n\" tabulation of the number 2\r\n\" -----------------------------------------------------------\r\n\r\n\r\n\r\n\r\n\" Example - Simple Project Bar Planner for the current year\r\n\" -----------------------------------------------------------\r\n\"                    #########################################################################\r\n\"                         1     2     3     4     5     6     7     8     9     10     11     12     \r\n\"1testa;    2;\r\n\"2testa;3.5;3.5;     #########(1m)###########\r\n\"testa; dsfkasdf;\r\n\"testa;dsfkasdf;\r\n\"5testa ;10.2;10.2;  #########(1m)#################################################\r\n\"6testa ;8.2;8.2;    #########(8m)#####################################\r\n\"\r\n\r\n\r\n\r\n\r\n","4":"\r\n\r\n\"\r\n\" Mini Year Planner for VIM \r\n\" version 0.01\r\n\"\r\n\" Needs some joint efforts for a newer release, please.\r\n\" todo:\r\n\" Simple Tabulation of the months\r\n \r\n\" -----------------------------------------------------------\r\n\" How to ? \r\n\" Select the first line (###################) with shift+v \r\n\" then press ,q \r\n\" and you will see that it will attempt to draw you the tabs for the year \r\n\" If you enter 1testa;2    then it will prolongate the \"#\" line to reach the\r\n\" tabulation of the number 2\r\n\" -----------------------------------------------------------\r\n\r\n\r\n\r\n\r\n\" Example - Simple Project Bar Planner for the current year\r\n\" -----------------------------------------------------------\r\n\"                    #########################################################################\r\n\"                         1     2     3     4     5     6     7     8     9     10     11     12     \r\n\"1testa;    2;\r\n\"2testa;3.5;3.5;     #########(1m)###########\r\n\"testa; dsfkasdf;\r\n\"testa;dsfkasdf;\r\n\"5testa ;10.2;10.2;  #########(1m)#################################################\r\n\"6testa ;8.2;8.2;    #########(8m)#####################################\r\n\"\r\n\r\n\r\n\r\n\r\n","install_details":"Add-on to the ~\/.vimrc","5":"Add-on to the ~\/.vimrc","first_name":"patrick295767","6":"patrick295767","last_name":"patrick295767","7":"patrick295767","releases":[{"0":"4429","vim_version":"7.0","1":"7.0","script_version":"0.01","2":"0.01","version_comment":"Initial upload","3":"Initial upload","package":"vim_planner.vim","4":"vim_planner.vim","src_id":"19494","5":"19494","creation_date":"1360605815","6":"1360605815"}]},"4428":{"script_id":"4428","0":"4428","script_name":"JavaScript Libraries Syntax","1":"JavaScript Libraries Syntax","script_type":"syntax","2":"syntax","summary":"Syntax for popular JavasSript libs","3":"Syntax for popular JavasSript libs","description":"javascript-libraries-syntax.vim\r\n===============================\r\n\r\nSyntax file for JavaScript libraries. Supports JavaScript libraris I am using (patches welcome).\r\nShould works well with other JavaScript syntax file. [SyntaxComplete][] also works well on all \r\nsupported languages.\r\n\r\n[SyntaxComplete]:http:\/\/www.vim.org\/scripts\/script.php?script_id=3172\r\n\r\nLibraries\r\n---------\r\n\r\n* [jQuery](http:\/\/jquery.com\/)\r\n* [underscore.js](http:\/\/underscorejs.org\/)\r\n* [lo-dash](http:\/\/lodash.com\/)\r\n* [Backbone.js](http:\/\/backbonejs.org\/)\r\n* [prelude.ls](http:\/\/gkz.github.com\/prelude-ls\/)\r\n* [AngularJS](http:\/\/angularjs.org\/)\r\n* [AngularUI](http:\/\/angular-ui.github.io)\r\n* [React](https:\/\/facebook.github.io\/react\/)\r\n* [Flux](https:\/\/facebook.github.io\/flux\/)\r\n* [RequireJS](http:\/\/requirejs.org\/)\r\n* [Sugar.js](http:\/\/sugarjs.com\/)\r\n* [Jasmine](http:\/\/pivotal.github.io\/jasmine\/)\r\n* [Chai](http:\/\/chaijs.com\/)\r\n* [Handlebars](http:\/\/handlebarsjs.com\/)\r\n\r\nFile Types\r\n----------\r\n\r\n* JavaScript\r\n* [CoffeeScript](http:\/\/coffeescript.org\/)\r\n* [LiveScript](http:\/\/livescript.net\/)\r\n* [TypeScript](http:\/\/www.typescriptlang.org\/)\r\n\r\nWill be more when SyntaxComplete has new version.\r\n\r\nInstall\r\n-------\r\n\r\nUse [pathogen][] or [vundle][] is recommended.\r\n\r\n[pathogen]:http:\/\/www.vim.org\/scripts\/script.php?script_id=2332\r\n[vundle]:https:\/\/github.com\/gmarik\/vundle\r\n\r\nConfig\r\n------\r\n\r\nYou can use g:used_javascript_libs to setup used libraries, ex:\r\n\r\n    let g:used_javascript_libs = 'underscore,backbone'\r\n\r\nSupport libs id:\r\n\r\n* jQuery: jquery\r\n* underscore.js: underscore\r\n* Lo-Dash: underscore\r\n* Backbone.js: backbone\r\n* prelude.ls: prelude\r\n* AngularJS: angularjs\r\n* AngularUI: angularui\r\n* React: react\r\n* Flux: flux\r\n* RequireJS: requirejs\r\n* Sugar.js: sugar\r\n* Jasmine: jasmine\r\n* Chai: chai\r\n* Handlebars: handlebars\r\n\r\nYou can use [local vimrc][] to setup libraries used in project. Sample code for local vimrc:\r\n\r\n    autocmd BufReadPre *.js let b:javascript_lib_use_jquery = 1\r\n    autocmd BufReadPre *.js let b:javascript_lib_use_underscore = 1\r\n    autocmd BufReadPre *.js let b:javascript_lib_use_backbone = 1\r\n    autocmd BufReadPre *.js let b:javascript_lib_use_prelude = 0\r\n    autocmd BufReadPre *.js let b:javascript_lib_use_angularjs = 0\r\n\r\n[local vimrc]:https:\/\/github.com\/MarcWeber\/vim-addon-local-vimrc\r\n\r\nTodo\r\n----\r\n\r\n* Support future version of SyntaxComplete\r\n\r\nKnown Issue\r\n-----------\r\n\r\nSyntaxComplete only accept groups with filetype prefixed. For example, 'javascript' files.\r\nOnly keywords in groups which's name matches \/javascript.*\/ will be available. So to make it\r\npossible to use SyntaxComplete on CoffeeScript, LiveScript and other compile to JavaScript\r\nlanguages. We must redefine all syntax many times, with different name prefix. SyntaxComplete\r\nmight have new feature to support a user define pattern for group name to include. \r\nAll repeat defination will be removed when SyntaxComplete supports this feature.\r\n\r\nCredits\r\n-------\r\n\r\n* Bruno Michel, [jQuery : Syntax file for jQuery][jquery.vim]\r\n* [Peter Renstr\u00c3\u00b6m][], for [summarize and explain AngularJS stuff][issue1].\r\n\r\n[jquery.vim]:http:\/\/www.vim.org\/scripts\/script.php?script_id=2416\r\n[Peter Renstr\u00c3\u00b6m]:https:\/\/github.com\/renstrom\r\n[issue1]:https:\/\/github.com\/othree\/javascript-libraries-syntax.vim\/issues\/1\r\n\r\nLicense\r\n-------\r\n\r\nCopyright (c) 2013 Wei-Ko Kao\r\n\r\nPermission is hereby granted, free of charge, to any person obtaining a copy\r\nof this software and associated documentation files (the \"Software\"), to deal\r\nin the Software without restriction, including without limitation the rights\r\nto use, copy, modify, merge, publish, distribute, sublicense, and\/or sell\r\ncopies of the Software, and to permit persons to whom the Software is\r\nfurnished to do so, subject to the following conditions:\r\n\r\nThe above copyright notice and this permission notice shall be included in\r\nall copies or substantial portions of the Software.\r\n\r\nTHE SOFTWARE IS PROVIDED \"AS IS\", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR\r\nIMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,\r\nFITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE\r\nAUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER\r\nLIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,\r\nOUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN\r\nTHE SOFTWARE.\r\n","4":"javascript-libraries-syntax.vim\r\n===============================\r\n\r\nSyntax file for JavaScript libraries. Supports JavaScript libraris I am using (patches welcome).\r\nShould works well with other JavaScript syntax file. [SyntaxComplete][] also works well on all \r\nsupported languages.\r\n\r\n[SyntaxComplete]:http:\/\/www.vim.org\/scripts\/script.php?script_id=3172\r\n\r\nLibraries\r\n---------\r\n\r\n* [jQuery](http:\/\/jquery.com\/)\r\n* [underscore.js](http:\/\/underscorejs.org\/)\r\n* [lo-dash](http:\/\/lodash.com\/)\r\n* [Backbone.js](http:\/\/backbonejs.org\/)\r\n* [prelude.ls](http:\/\/gkz.github.com\/prelude-ls\/)\r\n* [AngularJS](http:\/\/angularjs.org\/)\r\n* [AngularUI](http:\/\/angular-ui.github.io)\r\n* [React](https:\/\/facebook.github.io\/react\/)\r\n* [Flux](https:\/\/facebook.github.io\/flux\/)\r\n* [RequireJS](http:\/\/requirejs.org\/)\r\n* [Sugar.js](http:\/\/sugarjs.com\/)\r\n* [Jasmine](http:\/\/pivotal.github.io\/jasmine\/)\r\n* [Chai](http:\/\/chaijs.com\/)\r\n* [Handlebars](http:\/\/handlebarsjs.com\/)\r\n\r\nFile Types\r\n----------\r\n\r\n* JavaScript\r\n* [CoffeeScript](http:\/\/coffeescript.org\/)\r\n* [LiveScript](http:\/\/livescript.net\/)\r\n* [TypeScript](http:\/\/www.typescriptlang.org\/)\r\n\r\nWill be more when SyntaxComplete has new version.\r\n\r\nInstall\r\n-------\r\n\r\nUse [pathogen][] or [vundle][] is recommended.\r\n\r\n[pathogen]:http:\/\/www.vim.org\/scripts\/script.php?script_id=2332\r\n[vundle]:https:\/\/github.com\/gmarik\/vundle\r\n\r\nConfig\r\n------\r\n\r\nYou can use g:used_javascript_libs to setup used libraries, ex:\r\n\r\n    let g:used_javascript_libs = 'underscore,backbone'\r\n\r\nSupport libs id:\r\n\r\n* jQuery: jquery\r\n* underscore.js: underscore\r\n* Lo-Dash: underscore\r\n* Backbone.js: backbone\r\n* prelude.ls: prelude\r\n* AngularJS: angularjs\r\n* AngularUI: angularui\r\n* React: react\r\n* Flux: flux\r\n* RequireJS: requirejs\r\n* Sugar.js: sugar\r\n* Jasmine: jasmine\r\n* Chai: chai\r\n* Handlebars: handlebars\r\n\r\nYou can use [local vimrc][] to setup libraries used in project. Sample code for local vimrc:\r\n\r\n    autocmd BufReadPre *.js let b:javascript_lib_use_jquery = 1\r\n    autocmd BufReadPre *.js let b:javascript_lib_use_underscore = 1\r\n    autocmd BufReadPre *.js let b:javascript_lib_use_backbone = 1\r\n    autocmd BufReadPre *.js let b:javascript_lib_use_prelude = 0\r\n    autocmd BufReadPre *.js let b:javascript_lib_use_angularjs = 0\r\n\r\n[local vimrc]:https:\/\/github.com\/MarcWeber\/vim-addon-local-vimrc\r\n\r\nTodo\r\n----\r\n\r\n* Support future version of SyntaxComplete\r\n\r\nKnown Issue\r\n-----------\r\n\r\nSyntaxComplete only accept groups with filetype prefixed. For example, 'javascript' files.\r\nOnly keywords in groups which's name matches \/javascript.*\/ will be available. So to make it\r\npossible to use SyntaxComplete on CoffeeScript, LiveScript and other compile to JavaScript\r\nlanguages. We must redefine all syntax many times, with different name prefix. SyntaxComplete\r\nmight have new feature to support a user define pattern for group name to include. \r\nAll repeat defination will be removed when SyntaxComplete supports this feature.\r\n\r\nCredits\r\n-------\r\n\r\n* Bruno Michel, [jQuery : Syntax file for jQuery][jquery.vim]\r\n* [Peter Renstr\u00c3\u00b6m][], for [summarize and explain AngularJS stuff][issue1].\r\n\r\n[jquery.vim]:http:\/\/www.vim.org\/scripts\/script.php?script_id=2416\r\n[Peter Renstr\u00c3\u00b6m]:https:\/\/github.com\/renstrom\r\n[issue1]:https:\/\/github.com\/othree\/javascript-libraries-syntax.vim\/issues\/1\r\n\r\nLicense\r\n-------\r\n\r\nCopyright (c) 2013 Wei-Ko Kao\r\n\r\nPermission is hereby granted, free of charge, to any person obtaining a copy\r\nof this software and associated documentation files (the \"Software\"), to deal\r\nin the Software without restriction, including without limitation the rights\r\nto use, copy, modify, merge, publish, distribute, sublicense, and\/or sell\r\ncopies of the Software, and to permit persons to whom the Software is\r\nfurnished to do so, subject to the following conditions:\r\n\r\nThe above copyright notice and this permission notice shall be included in\r\nall copies or substantial portions of the Software.\r\n\r\nTHE SOFTWARE IS PROVIDED \"AS IS\", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR\r\nIMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,\r\nFITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE\r\nAUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER\r\nLIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,\r\nOUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN\r\nTHE SOFTWARE.\r\n","install_details":"Use pathogen or vundle.\r\n\r\nGithub: https:\/\/github.com\/othree\/javascript-libraries-syntax.vim","5":"Use pathogen or vundle.\r\n\r\nGithub: https:\/\/github.com\/othree\/javascript-libraries-syntax.vim","first_name":"wei ko","6":"wei ko","last_name":"kao","7":"kao","releases":[{"0":"4428","vim_version":"7.0","1":"7.0","script_version":"0.4.0","2":"0.4.0","version_comment":"- Add React, Flux, Chai, Handlbars\r\n- Default lib set\r\n- Bug fix\r\n","3":"- Add React, Flux, Chai, Handlbars\r\n- Default lib set\r\n- Bug fix\r\n","package":"javascript-libraries-syntax.vim-0.4.vmb","4":"javascript-libraries-syntax.vim-0.4.vmb","src_id":"22920","5":"22920","creation_date":"1424151143","6":"1424151143"},{"0":"4428","vim_version":"7.0","1":"7.0","script_version":"0.3.5","2":"0.3.5","version_comment":"* sugar.js, angularjs html attribute\r\n* minor changes","3":"* sugar.js, angularjs html attribute\r\n* minor changes","package":"javascript-libraries-syntax.vim-0.3.5.vba","4":"javascript-libraries-syntax.vim-0.3.5.vba","src_id":"22120","5":"22120","creation_date":"1404359709","6":"1404359709"},{"0":"4428","vim_version":"7.0","1":"7.0","script_version":"0.3.2","2":"0.3.2","version_comment":"* Fix coffee script compatible\r\n* Update jQuery syntax to latest version\r\n* Support lo-dash\r\n* jQuery selector update\r\n* Minor bug fix","3":"* Fix coffee script compatible\r\n* Update jQuery syntax to latest version\r\n* Support lo-dash\r\n* jQuery selector update\r\n* Minor bug fix","package":"javascript-libraries-syntax.vim-0.3.2.vmb","4":"javascript-libraries-syntax.vim-0.3.2.vmb","src_id":"19908","5":"19908","creation_date":"1366715096","6":"1366715096"},{"0":"4428","vim_version":"7.0","1":"7.0","script_version":"0.3.1","2":"0.3.1","version_comment":"Fix performance issue","3":"Fix performance issue","package":"javascript-libraries-syntax.vim-0.3.1.vmb","4":"javascript-libraries-syntax.vim-0.3.1.vmb","src_id":"19893","5":"19893","creation_date":"1366624720","6":"1366624720"},{"0":"4428","vim_version":"7.0","1":"7.0","script_version":"0.3","2":"0.3","version_comment":"Supports AngularJS, RequireJS\r\nSupport TypeScript\r\nSetup used libraries\r\nBetter init way","3":"Supports AngularJS, RequireJS\r\nSupport TypeScript\r\nSetup used libraries\r\nBetter init way","package":"javascript-libraries-syntax.vim-0.3.vmb","4":"javascript-libraries-syntax.vim-0.3.vmb","src_id":"19568","5":"19568","creation_date":"1361705489","6":"1361705489"},{"0":"4428","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"javascript-libraries-syntax.vim-0.1.vmb","4":"javascript-libraries-syntax.vim-0.1.vmb","src_id":"19493","5":"19493","creation_date":"1360551313","6":"1360551313"}]},"4427":{"script_id":"4427","0":"4427","script_name":"gf-ext","1":"gf-ext","script_type":"utility","2":"utility","summary":"Extend \"gf\" to support opening files in external programs","3":"Extend \"gf\" to support opening files in external programs","description":"gf-ext allows you to specify \"handlers\" for filetypes based on a regular expression you supply (often specifying a file extension).  This is useful when you want to view or edit files which are referenced in source code but aren't necessarily source text files themselves; for example `<img>` tags in HTML, source asset files, and so on.\r\n\r\nFull details available on the plugin's github page at http:\/\/github.com\/dpwright\/vim-gf-ext or in the plugin's documentation.  Please report any issues or submit any contributions through github.","4":"gf-ext allows you to specify \"handlers\" for filetypes based on a regular expression you supply (often specifying a file extension).  This is useful when you want to view or edit files which are referenced in source code but aren't necessarily source text files themselves; for example `<img>` tags in HTML, source asset files, and so on.\r\n\r\nFull details available on the plugin's github page at http:\/\/github.com\/dpwright\/vim-gf-ext or in the plugin's documentation.  Please report any issues or submit any contributions through github.","install_details":"Extract the zip file into your ~\/.vim folder, or install using Pathogen (http:\/\/github.com\/tpope\/vim-pathogen).\r\n\r\nI recommend installing from the plugin's github page at http:\/\/github.com\/dpwright\/vim-gf-ext as that will get updated much more frequently than this page does.","5":"Extract the zip file into your ~\/.vim folder, or install using Pathogen (http:\/\/github.com\/tpope\/vim-pathogen).\r\n\r\nI recommend installing from the plugin's github page at http:\/\/github.com\/dpwright\/vim-gf-ext as that will get updated much more frequently than this page does.","first_name":"Daniel P.","6":"Daniel P.","last_name":"Wright","7":"Wright","releases":[{"0":"4427","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"gf-ext.zip","4":"gf-ext.zip","src_id":"19478","5":"19478","creation_date":"1360125994","6":"1360125994"}]},"4426":{"script_id":"4426","0":"4426","script_name":"find-complete","1":"find-complete","script_type":"utility","2":"utility","summary":"Find files on path with file-name auto-complete functionality","3":"Find files on path with file-name auto-complete functionality","description":"A simple vim plugin to find files on path with filename auto-complete functionality.  Adds new cmd to use (:F) instead of :find.  You can tab a partial filename to complete it.","4":"A simple vim plugin to find files on path with filename auto-complete functionality.  Adds new cmd to use (:F) instead of :find.  You can tab a partial filename to complete it.","install_details":"1. Extract the gzipped tarball:\r\ntar zxvf vim-find-complete.tar.gz\r\n\r\nOR, find the plugin on Github:\r\ngit clone https:\/\/github.com\/stegtmeyer\/find-complete.git\r\n\r\n2. Copy the plugin to your vim plugins directory:\r\ncp find-complete\/plugin\/find-complete.vim ~\/.vim\/plugin\/ ","5":"1. Extract the gzipped tarball:\r\ntar zxvf vim-find-complete.tar.gz\r\n\r\nOR, find the plugin on Github:\r\ngit clone https:\/\/github.com\/stegtmeyer\/find-complete.git\r\n\r\n2. Copy the plugin to your vim plugins directory:\r\ncp find-complete\/plugin\/find-complete.vim ~\/.vim\/plugin\/ ","first_name":"Sean","6":"Sean","last_name":"Tegtmeyer","7":"Tegtmeyer","releases":[{"0":"4426","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Just updating that this should be used with 6.0, since 7.x has :find auto-complete functionality built in.","3":"Just updating that this should be used with 6.0, since 7.x has :find auto-complete functionality built in.","package":"vim-find-complete.tar.gz","4":"vim-find-complete.tar.gz","src_id":"19479","5":"19479","creation_date":"1360316569","6":"1360316569"}]},"4425":{"script_id":"4425","0":"4425","script_name":"phonzia","1":"phonzia","script_type":"color scheme","2":"color scheme","summary":"A dark color scheme","3":"A dark color scheme","description":"A self using corlor scheme\r\ndark and clear","4":"A self using corlor scheme\r\ndark and clear","install_details":"copy to your color directory and append statement below to your .vimrc\r\ncolorscheme phonzia\r\n ","5":"copy to your color directory and append statement below to your .vimrc\r\ncolorscheme phonzia\r\n ","first_name":"Phonzia","6":"Phonzia","last_name":"Yang","7":"Yang","releases":[{"0":"4425","vim_version":"7.3","1":"7.3","script_version":"1.0.0","2":"1.0.0","version_comment":"Initial upload","3":"Initial upload","package":"phonzia.vim","4":"phonzia.vim","src_id":"19472","5":"19472","creation_date":"1360049864","6":"1360049864"}]},"4424":{"script_id":"4424","0":"4424","script_name":"usefold","1":"usefold","script_type":"utility","2":"utility","summary":"indent based fold marker creation","3":"indent based fold marker creation","description":"Usefold provides functionality to ease putting fold markers based\r\non indentation when using the marker foldmethod. No maps are \r\nprovided by default but has to be set up by the user.\r\n\r\nUsefold_FoldDown \/ FoldUp \/ FromInside functions are provided\r\nand creates a fold between the current line and the first line\r\nbelow\/above that has the same level of indentation. In the last\r\ncase, FoldDown is called on the first line above the current\r\nthat is indented less than the current line.\r\nThe functions can also be given a parameter, to specify another\r\nline than the current.\r\n\r\nUsefold_foldtext is also provided and is (according to me, the author)\r\na better foldtext, that among other things preserve indentation.","4":"Usefold provides functionality to ease putting fold markers based\r\non indentation when using the marker foldmethod. No maps are \r\nprovided by default but has to be set up by the user.\r\n\r\nUsefold_FoldDown \/ FoldUp \/ FromInside functions are provided\r\nand creates a fold between the current line and the first line\r\nbelow\/above that has the same level of indentation. In the last\r\ncase, FoldDown is called on the first line above the current\r\nthat is indented less than the current line.\r\nThe functions can also be given a parameter, to specify another\r\nline than the current.\r\n\r\nUsefold_foldtext is also provided and is (according to me, the author)\r\na better foldtext, that among other things preserve indentation.","install_details":"Regular vimball installation, or get the pathogen compatible\r\nfiles\/file structure from https:\/\/github.com\/tlvb\/Usefold\r\n\r\nNo mappings provided by default, you decide yourself if and when you want what functions to be called.","5":"Regular vimball installation, or get the pathogen compatible\r\nfiles\/file structure from https:\/\/github.com\/tlvb\/Usefold\r\n\r\nNo mappings provided by default, you decide yourself if and when you want what functions to be called.","first_name":"Leo","6":"Leo","last_name":"B\u00c3\u00a4rring","7":"B\u00c3\u00a4rring","releases":[{"0":"4424","vim_version":"7.3","1":"7.3","script_version":"0.0.3","2":"0.0.3","version_comment":"Initial upload","3":"Initial upload","package":"usefold.vmb","4":"usefold.vmb","src_id":"19471","5":"19471","creation_date":"1360010547","6":"1360010547"}]},"4423":{"script_id":"4423","0":"4423","script_name":"fat-finger","1":"fat-finger","script_type":"utility","2":"utility","summary":"Simple vim plugin for common misspellings and typos","3":"Simple vim plugin for common misspellings and typos","description":"vim-fat-finger\r\nA simple vim plugin that automatically corrects common misspellings and typos as you type.\r\n\r\nMisspellings\r\nThis plugin supports over 4,000 common misspellings, as defined in plugin\/fat-finger.vim.\r\n\r\nThe settings in the plugin file are defined using Vim's iabbrev keyword, which is part of Vim's built-in abbreviations feature. The definitions follow a format of iabbrev, followed by the commonly misspelled word, and then finally the desired corrected version of misspelling.\r\n\r\nFor example:\r\n\r\niabbrev acheive achieve\r\niabbrev contraversy controversy\r\niabbrev demenor demeanor\r\niabbrev embarass embarrass\r\niabbrev lisence license\r\niabbrev morgage mortgage\r\niabbrev nightfa;; nightfall\r\niabbrev offred offered\r\niabbrev precice precise\r\niabbrev teh the                                                                                                  \r\n\r\n\r\nInstallation\r\n\r\n1. Unravel the gzipped tarball:\r\ntar xvfz vim-fat-finger.tar.gz\r\n\r\nOR, if you found the plugin on Github:\r\ngit clone git:\/\/github.com\/chip\/vim-fat-finger.git\r\n\r\n2. Copy the file to your vim plugins directory:\r\ncp vim-fat-finger\/plugin\/fat-finger.vim ~\/.vim\/plugin\/\r\n\r\n\r\nConfiguration\r\nSimply edit ~\/.vim\/plugin\/fat-finger.vim to suit your needs. If you don't like a specific definition, feel free to edit it or remove it altogether.\r\n\r\n\r\nLicense\r\nhttps:\/\/github.com\/chip\/vim-fat-finger\/blob\/master\/LICENSE.md\r\n\r\n\r\nTrolling\r\nFeel free to follow chip at http:\/\/chipcastle.com, or on https:\/\/github.com\/chip or https:\/\/twitter.com\/chipcastle","4":"vim-fat-finger\r\nA simple vim plugin that automatically corrects common misspellings and typos as you type.\r\n\r\nMisspellings\r\nThis plugin supports over 4,000 common misspellings, as defined in plugin\/fat-finger.vim.\r\n\r\nThe settings in the plugin file are defined using Vim's iabbrev keyword, which is part of Vim's built-in abbreviations feature. The definitions follow a format of iabbrev, followed by the commonly misspelled word, and then finally the desired corrected version of misspelling.\r\n\r\nFor example:\r\n\r\niabbrev acheive achieve\r\niabbrev contraversy controversy\r\niabbrev demenor demeanor\r\niabbrev embarass embarrass\r\niabbrev lisence license\r\niabbrev morgage mortgage\r\niabbrev nightfa;; nightfall\r\niabbrev offred offered\r\niabbrev precice precise\r\niabbrev teh the                                                                                                  \r\n\r\n\r\nInstallation\r\n\r\n1. Unravel the gzipped tarball:\r\ntar xvfz vim-fat-finger.tar.gz\r\n\r\nOR, if you found the plugin on Github:\r\ngit clone git:\/\/github.com\/chip\/vim-fat-finger.git\r\n\r\n2. Copy the file to your vim plugins directory:\r\ncp vim-fat-finger\/plugin\/fat-finger.vim ~\/.vim\/plugin\/\r\n\r\n\r\nConfiguration\r\nSimply edit ~\/.vim\/plugin\/fat-finger.vim to suit your needs. If you don't like a specific definition, feel free to edit it or remove it altogether.\r\n\r\n\r\nLicense\r\nhttps:\/\/github.com\/chip\/vim-fat-finger\/blob\/master\/LICENSE.md\r\n\r\n\r\nTrolling\r\nFeel free to follow chip at http:\/\/chipcastle.com, or on https:\/\/github.com\/chip or https:\/\/twitter.com\/chipcastle","install_details":"Installation\r\n\r\n1. Unravel the gzipped tarball:\r\ntar xvfz vim-fat-finger.tar.gz\r\n\r\nOR, if you found the plugin on Github:\r\ngit clone git:\/\/github.com\/chip\/vim-fat-finger.git\r\n\r\n2. Copy the file to your vim plugins directory:\r\ncp vim-fat-finger\/plugin\/fat-finger.vim ~\/.vim\/plugin\/\r\n","5":"Installation\r\n\r\n1. Unravel the gzipped tarball:\r\ntar xvfz vim-fat-finger.tar.gz\r\n\r\nOR, if you found the plugin on Github:\r\ngit clone git:\/\/github.com\/chip\/vim-fat-finger.git\r\n\r\n2. Copy the file to your vim plugins directory:\r\ncp vim-fat-finger\/plugin\/fat-finger.vim ~\/.vim\/plugin\/\r\n","first_name":"Chip","6":"Chip","last_name":"Castle","7":"Castle","releases":[{"0":"4423","vim_version":"7.0","1":"7.0","script_version":"1.0.0","2":"1.0.0","version_comment":"Initial upload","3":"Initial upload","package":"vim-fat-finger.tar.gz","4":"vim-fat-finger.tar.gz","src_id":"19465","5":"19465","creation_date":"1359830161","6":"1359830161"}]},"4422":{"script_id":"4422","0":"4422","script_name":"msbuild.vba","1":"msbuild.vba","script_type":"ftplugin","2":"ftplugin","summary":"Vim plugin for MSBuild project support","3":"Vim plugin for MSBuild project support","description":"This Vim plugin enables syntax support for all typical MSBuild project and include files matching the following patterns:\r\n\r\n    *.*proj\r\n    *.props\r\n    *.targets\r\n\r\nYou can also build an open project from within Vim using :make. Any warnings or errors can then be opened directly. You can also pass command line parameters to :make like you would to msbuild.exe, like:\r\n\r\n    :make \/t:rebuild\r\n\r\nSome items and imported projects or targets can also be opened with gf. Any environment variables in the path are expanded automatically if possible.","4":"This Vim plugin enables syntax support for all typical MSBuild project and include files matching the following patterns:\r\n\r\n    *.*proj\r\n    *.props\r\n    *.targets\r\n\r\nYou can also build an open project from within Vim using :make. Any warnings or errors can then be opened directly. You can also pass command line parameters to :make like you would to msbuild.exe, like:\r\n\r\n    :make \/t:rebuild\r\n\r\nSome items and imported projects or targets can also be opened with gf. Any environment variables in the path are expanded automatically if possible.","install_details":"To keep up-to-date with changes, I recommend using Git and installing pathogen from https:\/\/github.com\/tpope\/vim-pathogen so you can clone this repo or your own fork like so:\r\n\r\n    mkdir %USERPROFILE%\\vimfiles\\bundle\r\n    cd \/d %USERPROFILE%\\vimfiles\\bundle\r\n    git clone https:\/\/github.com\/heaths\/vim-msbuild.git\r\n\r\nTo make help content available when using pathogen, start vim and type :Helptags. You can then type :help msbuild for more information.\r\n\r\nIf you prefer to install the scripts directly, you can download the vimball, open it in vim, and install it like so:\r\n\r\n    vim msbuild.vba\r\n    :so %\r\n    :q","5":"To keep up-to-date with changes, I recommend using Git and installing pathogen from https:\/\/github.com\/tpope\/vim-pathogen so you can clone this repo or your own fork like so:\r\n\r\n    mkdir %USERPROFILE%\\vimfiles\\bundle\r\n    cd \/d %USERPROFILE%\\vimfiles\\bundle\r\n    git clone https:\/\/github.com\/heaths\/vim-msbuild.git\r\n\r\nTo make help content available when using pathogen, start vim and type :Helptags. You can then type :help msbuild for more information.\r\n\r\nIf you prefer to install the scripts directly, you can download the vimball, open it in vim, and install it like so:\r\n\r\n    vim msbuild.vba\r\n    :so %\r\n    :q","first_name":"Heath","6":"Heath","last_name":"Stewart","7":"Stewart","releases":[{"0":"4422","vim_version":"7.0","1":"7.0","script_version":"1.1","2":"1.1","version_comment":"Return reserved directory properties with a trailing backslash as documented. To avoid double backslash issues in authored paths (which works in MSBuild but errs in Vim), paths are simplified before an attempt is made to open them.","3":"Return reserved directory properties with a trailing backslash as documented. To avoid double backslash issues in authored paths (which works in MSBuild but errs in Vim), paths are simplified before an attempt is made to open them.","package":"msbuild.vba","4":"msbuild.vba","src_id":"19475","5":"19475","creation_date":"1360090669","6":"1360090669"},{"0":"4422","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"msbuild.vba","4":"msbuild.vba","src_id":"19463","5":"19463","creation_date":"1359785354","6":"1359785354"}]},"4421":{"script_id":"4421","0":"4421","script_name":"texlog.vim","1":"texlog.vim","script_type":"syntax","2":"syntax","summary":"Syntax highlighting and folding for TeX\/LaTeX log files","3":"Syntax highlighting and folding for TeX\/LaTeX log files","description":"Syntax highlighting and simple folding for TeX and LaTeX log files.\r\n\r\nThis Vim syntax plugin introduces the filetype \"texlog\". This filetype is detected automatically for files with the .log extension and the conventional magical first line:\r\n\r\nThis is .*TeX.*, Version .*\r\n\r\nShould filetype detection fail, you can set it yourself with \":setf texlog\".\r\n","4":"Syntax highlighting and simple folding for TeX and LaTeX log files.\r\n\r\nThis Vim syntax plugin introduces the filetype \"texlog\". This filetype is detected automatically for files with the .log extension and the conventional magical first line:\r\n\r\nThis is .*TeX.*, Version .*\r\n\r\nShould filetype detection fail, you can set it yourself with \":setf texlog\".\r\n","install_details":"Move the syntax file into the ~\/.vim\/syntax directory and the filetype detection script into ~\/.vim\/ftdetect (you may have to create that first). On Windows, replace \"~\/.vim\/\" with \"~\\vimfiles\\\".\r\n\r\nWith a plugin manager such as pathogen, the usual procedure applies:\r\n\r\ncd ~\/.vim\/bundle\r\ngit clone git:\/\/github.com\/glts\/vim-texlog.git texlog\r\n","5":"Move the syntax file into the ~\/.vim\/syntax directory and the filetype detection script into ~\/.vim\/ftdetect (you may have to create that first). On Windows, replace \"~\/.vim\/\" with \"~\\vimfiles\\\".\r\n\r\nWith a plugin manager such as pathogen, the usual procedure applies:\r\n\r\ncd ~\/.vim\/bundle\r\ngit clone git:\/\/github.com\/glts\/vim-texlog.git texlog\r\n","first_name":"David","6":"David","last_name":"B\u00c3\u00bcrgin","7":"B\u00c3\u00bcrgin","releases":[{"0":"4421","vim_version":"7.0","1":"7.0","script_version":"1.0.0","2":"1.0.0","version_comment":"Initial upload","3":"Initial upload","package":"texlog.zip","4":"texlog.zip","src_id":"19462","5":"19462","creation_date":"1359759467","6":"1359759467"}]},"4420":{"script_id":"4420","0":"4420","script_name":"Fold License","1":"Fold License","script_type":"utility","2":"utility","summary":"A vim plugin to hide the annoyng license at the top of each file","3":"A vim plugin to hide the annoyng license at the top of each file","description":"This script look for some keywords on licenses, identify a license block in the start of a file, and folds it. \r\n\r\nThe license can be commented in the following styles:\r\nC single line\r\nC multi line\r\nbash single line\r\n\r\nit should be fair easy to add other comment styles.\r\n\r\nfork it at https:\/\/github.com\/fotanus\/fold_license\r\n\r\n\r\n\r\n\r\n\r\n","4":"This script look for some keywords on licenses, identify a license block in the start of a file, and folds it. \r\n\r\nThe license can be commented in the following styles:\r\nC single line\r\nC multi line\r\nbash single line\r\n\r\nit should be fair easy to add other comment styles.\r\n\r\nfork it at https:\/\/github.com\/fotanus\/fold_license\r\n\r\n\r\n\r\n\r\n\r\n","install_details":"drop it in .vim\/plugins","5":"drop it in .vim\/plugins","first_name":"Felipe","6":"Felipe","last_name":"Tanus","7":"Tanus","releases":[{"0":"4420","vim_version":"6.0","1":"6.0","script_version":"0.2","2":"0.2","version_comment":"Fixed bug for files that have only one big comment block","3":"Fixed bug for files that have only one big comment block","package":"fold_license.vim","4":"fold_license.vim","src_id":"19502","5":"19502","creation_date":"1360700278","6":"1360700278"},{"0":"4420","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"fold_license.vim","4":"fold_license.vim","src_id":"19459","5":"19459","creation_date":"1359716598","6":"1359716598"}]},"4419":{"script_id":"4419","0":"4419","script_name":"sunny","1":"sunny","script_type":"color scheme","2":"color scheme","summary":"Color scheme for __terminal__ vim","3":"Color scheme for __terminal__ vim","description":"This is a color scheme for __terminal__ vim (as opposed to gvim) which I use when the sun is  high and I have to switch to a light color scheme.  It evolved over a few years from the calmar color scheme vimscript#1807. ","4":"This is a color scheme for __terminal__ vim (as opposed to gvim) which I use when the sun is  high and I have to switch to a light color scheme.  It evolved over a few years from the calmar color scheme vimscript#1807. ","install_details":"Put the script file inside your ~\/.vim\/colors directory.","5":"Put the script file inside your ~\/.vim\/colors directory.","first_name":"Marcin","6":"Marcin","last_name":"Szamotulski","7":"Szamotulski","releases":[{"0":"4419","vim_version":"7.0","1":"7.0","script_version":"1","2":"1","version_comment":"Initial upload","3":"Initial upload","package":"sunny.vim","4":"sunny.vim","src_id":"19458","5":"19458","creation_date":"1359713057","6":"1359713057"}]},"4418":{"script_id":"4418","0":"4418","script_name":"Bck","1":"Bck","script_type":"utility","2":"utility","summary":"Enhanced searching for Vim","3":"Enhanced searching for Vim","description":"Bck is a plugin that enhances searching in Vim. It puts bits and pieces \r\ntogether to make searching a better experience in Vim.\r\n\r\nSearching is powered by ack, which needs to be installed first. This plugin\r\nis similar to ack.vim but it brings several improvements:\r\n\r\n* You can specify search options using hotkeys which are displayed at the top of the Bck window\r\n* Each search result has an associated hotkey which can be used to view it\r\n* Cursorline is used to highlight the result\r\n* Results are displayed in the Bck window, but are available in the quickfix\r\nwindow as well\r\n\r\nBck provides a unified way to search in the following locations:\r\n\r\n* project - the closest parent dir which contains a .git folder (or .svn, .hg etc., configurable)\r\n* parent dir - relative to the current file\r\n* file - search only in the current file \r\n* current dir - in Vim's current working directory\r\n* buffers - all listed buffers\r\n\r\nOther search options are:\r\n\r\n* ignore case \/ match case\r\n* recursive \/ non-recursive\r\n* whole word \/ substring\r\n\r\nMore details on github: https:\/\/github.com\/mihaifm\/bck","4":"Bck is a plugin that enhances searching in Vim. It puts bits and pieces \r\ntogether to make searching a better experience in Vim.\r\n\r\nSearching is powered by ack, which needs to be installed first. This plugin\r\nis similar to ack.vim but it brings several improvements:\r\n\r\n* You can specify search options using hotkeys which are displayed at the top of the Bck window\r\n* Each search result has an associated hotkey which can be used to view it\r\n* Cursorline is used to highlight the result\r\n* Results are displayed in the Bck window, but are available in the quickfix\r\nwindow as well\r\n\r\nBck provides a unified way to search in the following locations:\r\n\r\n* project - the closest parent dir which contains a .git folder (or .svn, .hg etc., configurable)\r\n* parent dir - relative to the current file\r\n* file - search only in the current file \r\n* current dir - in Vim's current working directory\r\n* buffers - all listed buffers\r\n\r\nOther search options are:\r\n\r\n* ignore case \/ match case\r\n* recursive \/ non-recursive\r\n* whole word \/ substring\r\n\r\nMore details on github: https:\/\/github.com\/mihaifm\/bck","install_details":"This plugin uses ack for the search, which is a Perl script better that grep. Download and install from http:\/\/betterthangrep.com\/\r\nTo install this plugin just copy bck.vim in the plugin directory of your vim installation, or install via pathogen or vundle.","5":"This plugin uses ack for the search, which is a Perl script better that grep. Download and install from http:\/\/betterthangrep.com\/\r\nTo install this plugin just copy bck.vim in the plugin directory of your vim installation, or install via pathogen or vundle.","first_name":"Mihai","6":"Mihai","last_name":"Ciuraru","7":"Ciuraru","releases":[{"0":"4418","vim_version":"7.3","1":"7.3","script_version":"1.0.0","2":"1.0.0","version_comment":"Initial upload","3":"Initial upload","package":"bck.zip","4":"bck.zip","src_id":"19456","5":"19456","creation_date":"1359588098","6":"1359588098"}]},"4417":{"script_id":"4417","0":"4417","script_name":"holokai","1":"holokai","script_type":"color scheme","2":"color scheme","summary":"A slightly darker version of molokai","3":"A slightly darker version of molokai","description":"Holokai is inspired by molokai ( http:\/\/www.vim.org\/scripts\/script.php?script_id=2340 ).\r\n\r\nYou can see screenshots and get most up to date version at https:\/\/github.com\/changyuheng\/color-scheme-holokai-for-vim\r\n\r\nTo use this color scheme under x-terminal, you should enable 256-color support in both x-terminal and vim and also screen\/tmux in case you have one.","4":"Holokai is inspired by molokai ( http:\/\/www.vim.org\/scripts\/script.php?script_id=2340 ).\r\n\r\nYou can see screenshots and get most up to date version at https:\/\/github.com\/changyuheng\/color-scheme-holokai-for-vim\r\n\r\nTo use this color scheme under x-terminal, you should enable 256-color support in both x-terminal and vim and also screen\/tmux in case you have one.","install_details":"Extract the compress file and copy holokai.vim to your .vim\/colors folder or use Vundle-like plug-in manager to do so.","5":"Extract the compress file and copy holokai.vim to your .vim\/colors folder or use Vundle-like plug-in manager to do so.","first_name":"Henry","6":"Henry","last_name":"Chang","7":"Chang","releases":[{"0":"4417","vim_version":"7.0","1":"7.0","script_version":"1.3","2":"1.3","version_comment":"Update some colors.","3":"Update some colors.","package":"holokai.tar.xz","4":"holokai.tar.xz","src_id":"23863","5":"23863","creation_date":"1451888053","6":"1451888053"},{"0":"4417","vim_version":"7.0","1":"7.0","script_version":"1.2","2":"1.2","version_comment":"Refine the colors in pop-up menu.","3":"Refine the colors in pop-up menu.","package":"holokai.tar.gz","4":"holokai.tar.gz","src_id":"21426","5":"21426","creation_date":"1391508822","6":"1391508822"},{"0":"4417","vim_version":"7.0","1":"7.0","script_version":"1.1","2":"1.1","version_comment":"Reduce brightness of some colors.","3":"Reduce brightness of some colors.","package":"holokai.tar.gz","4":"holokai.tar.gz","src_id":"19589","5":"19589","creation_date":"1362390007","6":"1362390007"},{"0":"4417","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"holokai.tar.gz","4":"holokai.tar.gz","src_id":"19449","5":"19449","creation_date":"1359446580","6":"1359446580"}]},"4416":{"script_id":"4416","0":"4416","script_name":"vim-seek","1":"vim-seek","script_type":"utility","2":"utility","summary":"Seek makes navigating long lines effortless, acting like f but taking two chars","3":"Seek makes navigating long lines effortless, acting like f but taking two chars","description":"Seek is a vim plugin that aims to make inline navigation effortless. The motion seek, summoned with s by default, is similar to f, but instead of one it expects two characters. This greatly reduces the possible matches within the line and mostly allows you to get anywhere in a line with three keystrokes. Your cursor is left off at the first character typed, so if you seek to \"th\" your cursor will now be at \"t\". The forward seek motion is complemented by S, which seeks backwards. Additional useful motions are provided, most optional, please see the github.com\/goldfeld\/vim-seek readme.","4":"Seek is a vim plugin that aims to make inline navigation effortless. The motion seek, summoned with s by default, is similar to f, but instead of one it expects two characters. This greatly reduces the possible matches within the line and mostly allows you to get anywhere in a line with three keystrokes. Your cursor is left off at the first character typed, so if you seek to \"th\" your cursor will now be at \"t\". The forward seek motion is complemented by S, which seeks backwards. Additional useful motions are provided, most optional, please see the github.com\/goldfeld\/vim-seek readme.","install_details":"More at http:\/\/github.com\/goldfeld\/vim-seek","5":"More at http:\/\/github.com\/goldfeld\/vim-seek","first_name":"Vic","6":"Vic","last_name":"Goldfeld","7":"Goldfeld","releases":[{"0":"4416","vim_version":"7.0","1":"7.0","script_version":"0.7","2":"0.7","version_comment":"0.7 - 2013-03-10\r\noffer ignore case seek option and custom char aliases.\r\nhandle multi-byte string seeks correctly.\r\n\r\n0.5 - 2013-01-30\r\nallow key customization of all seek motions.\r\nimplement remote jump motions.","3":"0.7 - 2013-03-10\r\noffer ignore case seek option and custom char aliases.\r\nhandle multi-byte string seeks correctly.\r\n\r\n0.5 - 2013-01-30\r\nallow key customization of all seek motions.\r\nimplement remote jump motions.","package":"seek.vim","4":"seek.vim","src_id":"20596","5":"20596","creation_date":"1375527602","6":"1375527602"},{"0":"4416","vim_version":"7.3","1":"7.3","script_version":"0.2","2":"0.2","version_comment":"Initial upload","3":"Initial upload","package":"seek.vim","4":"seek.vim","src_id":"19439","5":"19439","creation_date":"1359367832","6":"1359367832"}]},"4415":{"script_id":"4415","0":"4415","script_name":"AWK-Support","1":"AWK-Support","script_type":"utility","2":"utility","summary":"AWK IDE -- Insert code snippets, run and check the code and look up help","3":"AWK IDE -- Insert code snippets, run and check the code and look up help","description":"AWK-IDE for Vim\/gVim is written to considerably speed up writing scripts in a\r\nconsistent style. This is done by inserting complete statements, idioms, code\r\nsnippets, templates, and comments. Compiling and viewing a document, format\r\nconversion and running make can be done with a few keystrokes.\r\n\r\n- insert various types of comments\r\n- insert complete but empty statements\r\n- insert often used code snippets\r\n- ... which come in an extendible template library\r\n- run scripts or run syntax check from within the editor\r\n- show compilation errors in a quickfix window\r\n\r\nSome screen shots :  https:\/\/wolfgangmehner.github.io\/vim-plugins\/awksupport.html\r\n\r\nFor plug-in managers :  https:\/\/github.com\/WolfgangMehner\/awk-support\r\n\r\nThe help file online :  https:\/\/wolfgangmehner.github.io\/vim-plugins\/doc\/awksupport.html\r\n\r\nThe key mappings of this plug-in :  https:\/\/wolfgangmehner.github.io\/vim-plugins\/awksupport\/awk-hotkeys.pdf\r\n\r\nDOCUMENTATION\r\n--------------------------------------------------------\r\nThis plug-in comes with a help file (awksupport.txt). Read it with\r\n\r\n    :h awksupport\r\n\r\n** PLEASE READ THE DOCUMENTATION **\r\n\r\nEditing actions differ for different modes! There are a lot of features which\r\ncan be configured or customized to match your needs.\r\n\r\nGitHub\r\n--------------------------------------------------------\r\nAWK-Support is on GitHub:\r\n\r\n    https:\/\/github.com\/WolfgangMehner\/vim-plugins\r\n\r\n(Please help us keep track of all the issues and name your report\/request \"AWK-Support: <title>\")\r\n\r\n","4":"AWK-IDE for Vim\/gVim is written to considerably speed up writing scripts in a\r\nconsistent style. This is done by inserting complete statements, idioms, code\r\nsnippets, templates, and comments. Compiling and viewing a document, format\r\nconversion and running make can be done with a few keystrokes.\r\n\r\n- insert various types of comments\r\n- insert complete but empty statements\r\n- insert often used code snippets\r\n- ... which come in an extendible template library\r\n- run scripts or run syntax check from within the editor\r\n- show compilation errors in a quickfix window\r\n\r\nSome screen shots :  https:\/\/wolfgangmehner.github.io\/vim-plugins\/awksupport.html\r\n\r\nFor plug-in managers :  https:\/\/github.com\/WolfgangMehner\/awk-support\r\n\r\nThe help file online :  https:\/\/wolfgangmehner.github.io\/vim-plugins\/doc\/awksupport.html\r\n\r\nThe key mappings of this plug-in :  https:\/\/wolfgangmehner.github.io\/vim-plugins\/awksupport\/awk-hotkeys.pdf\r\n\r\nDOCUMENTATION\r\n--------------------------------------------------------\r\nThis plug-in comes with a help file (awksupport.txt). Read it with\r\n\r\n    :h awksupport\r\n\r\n** PLEASE READ THE DOCUMENTATION **\r\n\r\nEditing actions differ for different modes! There are a lot of features which\r\ncan be configured or customized to match your needs.\r\n\r\nGitHub\r\n--------------------------------------------------------\r\nAWK-Support is on GitHub:\r\n\r\n    https:\/\/github.com\/WolfgangMehner\/vim-plugins\r\n\r\n(Please help us keep track of all the issues and name your report\/request \"AWK-Support: <title>\")\r\n\r\n","install_details":"Copy the zip archive awk-support.zip to $HOME\/.vim\/ or $VIM\/vimfiles\r\n(on the Windows platforms) and run\r\n    unzip awk-support.zip\r\nIf you have already an older version of this plug-in and you have modified the\r\ntemplate files you may want to save your templates first or copy the files from\r\nthe archive by hand. See also the file README.md within the zip file.","5":"Copy the zip archive awk-support.zip to $HOME\/.vim\/ or $VIM\/vimfiles\r\n(on the Windows platforms) and run\r\n    unzip awk-support.zip\r\nIf you have already an older version of this plug-in and you have modified the\r\ntemplate files you may want to save your templates first or copy the files from\r\nthe archive by hand. See also the file README.md within the zip file.","first_name":"Fritz","6":"Fritz","last_name":"Mehner","7":"Mehner","releases":[{"0":"4415","vim_version":"7.3","1":"7.3","script_version":"1.3","2":"1.3","version_comment":"- Add 'g:Awk_CustomTemplateFile'.\r\n- Add template personalization file and setup wizard.\r\n- Change the way lines of code are turned into comments\r\n  (insert no space after the hash).\r\n- Change the map for 'comment -> code' to '\\co' for consistency with the other\r\n  plug-ins. The old map '\\cu' still works, however.\r\n- Minor corrections and improvements.","3":"- Add 'g:Awk_CustomTemplateFile'.\r\n- Add template personalization file and setup wizard.\r\n- Change the way lines of code are turned into comments\r\n  (insert no space after the hash).\r\n- Change the map for 'comment -> code' to '\\co' for consistency with the other\r\n  plug-ins. The old map '\\cu' still works, however.\r\n- Minor corrections and improvements.","package":"awk-support.zip","4":"awk-support.zip","src_id":"24451","5":"24451","creation_date":"1471360706","6":"1471360706"},{"0":"4415","vim_version":"7.0","1":"7.0","script_version":"1.2","2":"1.2","version_comment":"- Bugfix: Setup of local templates in case of global installation.\r\n- 'Run -> make script executable' (\\re) is now a toggle.\r\n- The Awk executable can now be configured.\r\n- Adjusting end-of-line comments improved.\r\n- Minor corrections and improvements.","3":"- Bugfix: Setup of local templates in case of global installation.\r\n- 'Run -> make script executable' (\\re) is now a toggle.\r\n- The Awk executable can now be configured.\r\n- Adjusting end-of-line comments improved.\r\n- Minor corrections and improvements.","package":"awk-support.zip","4":"awk-support.zip","src_id":"21799","5":"21799","creation_date":"1398073118","6":"1398073118"},{"0":"4415","vim_version":"7.0","1":"7.0","script_version":"1.1","2":"1.1","version_comment":"- Map renamed: \\rt -> \\rx .\r\n- Wrapper-script missing.\r\n- Resolve home for linked home directories.\r\n- Footer did not appear in doc\/awk-hotkeys.pdf\r\n- Bugfix: mapleader issues fixed.","3":"- Map renamed: \\rt -> \\rx .\r\n- Wrapper-script missing.\r\n- Resolve home for linked home directories.\r\n- Footer did not appear in doc\/awk-hotkeys.pdf\r\n- Bugfix: mapleader issues fixed.","package":"awk-support.zip","4":"awk-support.zip","src_id":"20701","5":"20701","creation_date":"1377194513","6":"1377194513"},{"0":"4415","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"awk-support.zip","4":"awk-support.zip","src_id":"19436","5":"19436","creation_date":"1359302863","6":"1359302863"}]},"4414":{"script_id":"4414","0":"4414","script_name":"GlobalOptions","1":"GlobalOptions","script_type":"utility","2":"utility","summary":"Turn global options into buffer- or window-local ones.","3":"Turn global options into buffer- or window-local ones.","description":"DESCRIPTION\r\nFor some Vim options, it may be helpful to make a particular setting only for\r\ncertain buffers or windows. Some options offer this, but when the option is\r\nonly globally scoped, this cannot be easily done.\r\nFor example, the 'scrolloff' option can be set to a high value to effectively\r\ncenter the current line in the middle of the window. But one may only want\r\nthis for certain filetypes, or only in a particular window.\r\n\r\nHOW IT WORKS\r\nWhen a buffer- or window-local global option is set, autocmds are set up that\r\nmodify the global option depending on the currently active buffer \/ window.\r\nBecause there can be buffer-local autocmds, but not window-local ones, the\r\napproach taken is slightly different.\r\n\r\nUSAGE\r\n:SetBufferLocal\r\n                        Show all global options made buffer-local.\r\n:SetBufferLocal {option}?\r\n                        Show the buffer-local value of global {option} (if\r\n                        set).\r\n:SetBufferLocal {option}={value}\r\n                        Set the global {option} to {value}, but only in the\r\n                        current buffer. Effectively turns {option} into a\r\n                        buffer-local option.\r\n:SetBufferLocal {option}<\r\n                        Remove the buffer-local value of {option}, so that the\r\n                        global value will be used. Like :setlocal {option}<\r\n\r\n:SetWindowLocal\r\n                        Show all global options made window-local.\r\n:SetWindowLocal {option}?\r\n                        Show the window-local value of global {option} (if\r\n                        set).\r\n:SetWindowLocal {option}={value}\r\n                        Set the global {option} to {value}, but only in the\r\n                        current window. Effectively turns {option} into a\r\n                        window-local option.\r\n:SetWindowLocal {option}<\r\n                        Remove the window-local value of {option}, so that the\r\n                        global value will be used. Like :setlocal {option}<\r\n\r\nAlternatively, you can also directly use the following API functions.\r\nNote that these do less error checking than above commands.\r\nGlobalOptions#SetBufferLocal({option}, {value})\r\nGlobalOptions#ClearBufferLocal({option})\r\nGlobalOptions#SetWindowLocal({option}, {value})\r\nGlobalOptions#ClearWindowLocal({option})\r\n\r\nEXAMPLE\r\nPlace the current line in the middle of the window by setting 'scrolloff' (a\r\nglobal option) to a large value, but only for the current window:\r\n    :SetWindowLocal scrolloff=999\r\n\r\nPlace the current line in the middle of the window by setting 'scrolloff' (a\r\nglobal option) to a large value, but only for a certain filetype (best placed\r\ninto ~\/.vim\/ftplugin\/{filetype}.vim):\r\n    :call GlobalOptions#SetBufferLocal('scrolloff', 999)\r\n    :let b:undo_ftplugin = 'call GlobalOptions#ClearBufferLocal(\"scrolloff\")'\r\nNote that we use the API function in the undo command to avoid an error when\r\nthe buffer-local option has already been unset. (And also for setting it, to\r\nbe consistent and because it's slightly more efficient.)","4":"DESCRIPTION\r\nFor some Vim options, it may be helpful to make a particular setting only for\r\ncertain buffers or windows. Some options offer this, but when the option is\r\nonly globally scoped, this cannot be easily done.\r\nFor example, the 'scrolloff' option can be set to a high value to effectively\r\ncenter the current line in the middle of the window. But one may only want\r\nthis for certain filetypes, or only in a particular window.\r\n\r\nHOW IT WORKS\r\nWhen a buffer- or window-local global option is set, autocmds are set up that\r\nmodify the global option depending on the currently active buffer \/ window.\r\nBecause there can be buffer-local autocmds, but not window-local ones, the\r\napproach taken is slightly different.\r\n\r\nUSAGE\r\n:SetBufferLocal\r\n                        Show all global options made buffer-local.\r\n:SetBufferLocal {option}?\r\n                        Show the buffer-local value of global {option} (if\r\n                        set).\r\n:SetBufferLocal {option}={value}\r\n                        Set the global {option} to {value}, but only in the\r\n                        current buffer. Effectively turns {option} into a\r\n                        buffer-local option.\r\n:SetBufferLocal {option}<\r\n                        Remove the buffer-local value of {option}, so that the\r\n                        global value will be used. Like :setlocal {option}<\r\n\r\n:SetWindowLocal\r\n                        Show all global options made window-local.\r\n:SetWindowLocal {option}?\r\n                        Show the window-local value of global {option} (if\r\n                        set).\r\n:SetWindowLocal {option}={value}\r\n                        Set the global {option} to {value}, but only in the\r\n                        current window. Effectively turns {option} into a\r\n                        window-local option.\r\n:SetWindowLocal {option}<\r\n                        Remove the window-local value of {option}, so that the\r\n                        global value will be used. Like :setlocal {option}<\r\n\r\nAlternatively, you can also directly use the following API functions.\r\nNote that these do less error checking than above commands.\r\nGlobalOptions#SetBufferLocal({option}, {value})\r\nGlobalOptions#ClearBufferLocal({option})\r\nGlobalOptions#SetWindowLocal({option}, {value})\r\nGlobalOptions#ClearWindowLocal({option})\r\n\r\nEXAMPLE\r\nPlace the current line in the middle of the window by setting 'scrolloff' (a\r\nglobal option) to a large value, but only for the current window:\r\n    :SetWindowLocal scrolloff=999\r\n\r\nPlace the current line in the middle of the window by setting 'scrolloff' (a\r\nglobal option) to a large value, but only for a certain filetype (best placed\r\ninto ~\/.vim\/ftplugin\/{filetype}.vim):\r\n    :call GlobalOptions#SetBufferLocal('scrolloff', 999)\r\n    :let b:undo_ftplugin = 'call GlobalOptions#ClearBufferLocal(\"scrolloff\")'\r\nNote that we use the API function in the undo command to avoid an error when\r\nthe buffer-local option has already been unset. (And also for setting it, to\r\nbe consistent and because it's slightly more efficient.)","install_details":"INSTALLATION\r\nThis script is packaged as a vimball. If you have the \"gunzip\" decompressor\r\nin your PATH, simply edit the *.vmb.gz package in Vim; otherwise, decompress\r\nthe archive first, e.g. using WinZip. Inside Vim, install by sourcing the\r\nvimball or via the :UseVimball command.\r\n    vim GlobalOptions*.vmb.gz\r\n    :so %\r\nTo uninstall, use the :RmVimball command.\r\n\r\nDEPENDENCIES\r\n- Requires Vim 7.0 or higher.","5":"INSTALLATION\r\nThis script is packaged as a vimball. If you have the \"gunzip\" decompressor\r\nin your PATH, simply edit the *.vmb.gz package in Vim; otherwise, decompress\r\nthe archive first, e.g. using WinZip. Inside Vim, install by sourcing the\r\nvimball or via the :UseVimball command.\r\n    vim GlobalOptions*.vmb.gz\r\n    :so %\r\nTo uninstall, use the :RmVimball command.\r\n\r\nDEPENDENCIES\r\n- Requires Vim 7.0 or higher.","first_name":"Ingo","6":"Ingo","last_name":"Karkat","7":"Karkat","releases":[{"0":"4414","vim_version":"7.0","1":"7.0","script_version":"1.00","2":"1.00","version_comment":"Initial upload","3":"Initial upload","package":"GlobalOptions-1.00.vmb.gz","4":"GlobalOptions-1.00.vmb.gz","src_id":"19433","5":"19433","creation_date":"1359119835","6":"1359119835"}]},"4413":{"script_id":"4413","0":"4413","script_name":"darkgit.vim","1":"darkgit.vim","script_type":"color scheme","2":"color scheme","summary":"dark theme inspired in github.vim colorscheme","3":"dark theme inspired in github.vim colorscheme","description":"darkgit is a dark theme, inspired in github.vim colorscheme. it does not ressembles git, though.\r\n\r\nalso at https:\/\/github.com\/flipgthb\/misc","4":"darkgit is a dark theme, inspired in github.vim colorscheme. it does not ressembles git, though.\r\n\r\nalso at https:\/\/github.com\/flipgthb\/misc","install_details":"just put in ~\/.vim\/colors","5":"just put in ~\/.vim\/colors","first_name":"felippe","6":"felippe","last_name":"alves","7":"alves","releases":[{"0":"4413","vim_version":"7.0","1":"7.0","script_version":"1.1","2":"1.1","version_comment":"fixed some highlighting issues.","3":"fixed some highlighting issues.","package":"darkgit.vim","4":"darkgit.vim","src_id":"19424","5":"19424","creation_date":"1359048339","6":"1359048339"},{"0":"4413","vim_version":"7.0","1":"7.0","script_version":"1","2":"1","version_comment":"Initial upload","3":"Initial upload","package":"darkgit.vim","4":"darkgit.vim","src_id":"19423","5":"19423","creation_date":"1359044052","6":"1359044052"}]},"4412":{"script_id":"4412","0":"4412","script_name":"cljfold.vim","1":"cljfold.vim","script_type":"ftplugin","2":"ftplugin","summary":"Automagic folding of λ clojure code based on 'foldwords'","3":"Automagic folding of λ clojure code based on 'foldwords'","description":"cljfold.vim\r\n\r\nThis plugin is for automagic folding of λ clojure code based on 'foldwords' that are the start of code-blocks.\r\n\r\nThis defaults to 'def' and 'ns' via\r\n\r\nlet g:clojure_foldwords = \"def,ns\"\r\n\r\nby Greg Berenfield with much taken from Steve Losh and Meikel Brandmeyer\r\n\r\nSource\/bugs\/latest version on github @ https:\/\/github.com\/gberenfield\/cljfold.vim","4":"cljfold.vim\r\n\r\nThis plugin is for automagic folding of λ clojure code based on 'foldwords' that are the start of code-blocks.\r\n\r\nThis defaults to 'def' and 'ns' via\r\n\r\nlet g:clojure_foldwords = \"def,ns\"\r\n\r\nby Greg Berenfield with much taken from Steve Losh and Meikel Brandmeyer\r\n\r\nSource\/bugs\/latest version on github @ https:\/\/github.com\/gberenfield\/cljfold.vim","install_details":"unzip or better yet, try vundle with\r\n\r\nBundle 'gberenfield\/cljfold.vim'\r\n\r\nin your bundles.vim file.","5":"unzip or better yet, try vundle with\r\n\r\nBundle 'gberenfield\/cljfold.vim'\r\n\r\nin your bundles.vim file.","first_name":"Greg","6":"Greg","last_name":"Berenfield","7":"Berenfield","releases":[{"0":"4412","vim_version":"7.3","1":"7.3","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"cljfold.vim-master.zip","4":"cljfold.vim-master.zip","src_id":"19422","5":"19422","creation_date":"1359039177","6":"1359039177"}]},"4411":{"script_id":"4411","0":"4411","script_name":"metaweblog","1":"metaweblog","script_type":"utility","2":"utility","summary":"Submit your RST article in VIM  to Blog with metaweblog interface.","3":"Submit your RST article in VIM  to Blog with metaweblog interface.","description":"Submit your **RST** article in VIM to Blog with metaweblog interface. \r\n\r\nFeature:\r\n\r\n+ direct submit **RST** article to Blog.\r\n+ support **HTML** article\r\n+ automatic upload image resource and fix link for **RST** when new post\r\n+ browse recent blogs\r\n+ delete blog\r\n+ upload file manually\r\n\r\n","4":"Submit your **RST** article in VIM to Blog with metaweblog interface. \r\n\r\nFeature:\r\n\r\n+ direct submit **RST** article to Blog.\r\n+ support **HTML** article\r\n+ automatic upload image resource and fix link for **RST** when new post\r\n+ browse recent blogs\r\n+ delete blog\r\n+ upload file manually\r\n\r\n","install_details":"Install\r\n=======\r\n0. Please install Docutils_ as RST tools, and Pygments_ for syntax highlight\r\n\r\n.. _Docutils: http:\/\/docutils.sourceforge.net\/\r\n.. _Pygments: http:\/\/pygments.org\/\r\n\r\n1. install VIM plugin\r\n\r\n.. code:: bash\r\n\r\n    cp plugin\/metaweblog.vim  ~\/.vim\/plugin\/metaweblog.vim\r\n\r\n2. Create new configuration file in ``~\/.vim\/password.vim``\r\n\r\n.. code:: vim\r\n\r\n    # password.vim\r\n    let g:MetaWeblog_api_url='http:\/\/www.is-programmer.com\/xmlrpc'\r\n    let g:MetaWeblog_username='username'\r\n    let g:MetaWeblog_password='password'\r\n\r\n3. Install CSS to support style:\r\n\r\n.. code:: bash\r\n\r\n    # RST CSS style\r\n    cat \/usr\/lib\/python2.6\/site-packages\/docutils\/writers\/html4css1\/html4css1.css > blog.css\r\n    # code with scrolled bar\r\n    echo \"pre.code { overflow: auto; }\" >> bslog.css\r\n    # syntax highlight\r\n    pygmentize -S default -f html -a pre.code >> blog.css\r\n\r\n4. Upload blog.css to Blog site.\r\n\r\n","5":"Install\r\n=======\r\n0. Please install Docutils_ as RST tools, and Pygments_ for syntax highlight\r\n\r\n.. _Docutils: http:\/\/docutils.sourceforge.net\/\r\n.. _Pygments: http:\/\/pygments.org\/\r\n\r\n1. install VIM plugin\r\n\r\n.. code:: bash\r\n\r\n    cp plugin\/metaweblog.vim  ~\/.vim\/plugin\/metaweblog.vim\r\n\r\n2. Create new configuration file in ``~\/.vim\/password.vim``\r\n\r\n.. code:: vim\r\n\r\n    # password.vim\r\n    let g:MetaWeblog_api_url='http:\/\/www.is-programmer.com\/xmlrpc'\r\n    let g:MetaWeblog_username='username'\r\n    let g:MetaWeblog_password='password'\r\n\r\n3. Install CSS to support style:\r\n\r\n.. code:: bash\r\n\r\n    # RST CSS style\r\n    cat \/usr\/lib\/python2.6\/site-packages\/docutils\/writers\/html4css1\/html4css1.css > blog.css\r\n    # code with scrolled bar\r\n    echo \"pre.code { overflow: auto; }\" >> bslog.css\r\n    # syntax highlight\r\n    pygmentize -S default -f html -a pre.code >> blog.css\r\n\r\n4. Upload blog.css to Blog site.\r\n\r\n","first_name":"Yugang","6":"Yugang","last_name":"LIU","7":"LIU","releases":[{"0":"4411","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"vim-metaweblog.tar.gz","4":"vim-metaweblog.tar.gz","src_id":"19420","5":"19420","creation_date":"1358992328","6":"1358992328"}]},"4410":{"script_id":"4410","0":"4410","script_name":"characterize.vim","1":"characterize.vim","script_type":"utility","2":"utility","summary":"Unicode character metadata","3":"Unicode character metadata","description":"In Vim, pressing ga on a character reveals its representation in decimal, octal, and hex.  Characterize.vim modernizes this with the following additions:\r\n\r\n* Unicode character names: U+00A9 COPYRIGHT SYMBOL\r\n* Vim digraphs (type after <C-K> to insert the character): Co, cO\r\n* Emoji codes: :copyright:\r\n* HTML entities: &copy;\r\n\r\nhttps:\/\/github.com\/tpope\/vim-characterize","4":"In Vim, pressing ga on a character reveals its representation in decimal, octal, and hex.  Characterize.vim modernizes this with the following additions:\r\n\r\n* Unicode character names: U+00A9 COPYRIGHT SYMBOL\r\n* Vim digraphs (type after <C-K> to insert the character): Co, cO\r\n* Emoji codes: :copyright:\r\n* HTML entities: &copy;\r\n\r\nhttps:\/\/github.com\/tpope\/vim-characterize","install_details":"Extract in ~\/.vim (~\\vimfiles on Windows).","5":"Extract in ~\/.vim (~\\vimfiles on Windows).","first_name":"Tim","6":"Tim","last_name":"Pope","7":"Pope","releases":[{"0":"4410","vim_version":"7.0","1":"7.0","script_version":"1.1","2":"1.1","version_comment":"Update character definitions.\r\nImprove robustness of digraph handling.\r\nProvide <Plug> mapping.","3":"Update character definitions.\r\nImprove robustness of digraph handling.\r\nProvide <Plug> mapping.","package":"characterize.zip","4":"characterize.zip","src_id":"27645","5":"27645","creation_date":"1625457470","6":"1625457470"},{"0":"4410","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"characterize.zip","4":"characterize.zip","src_id":"19419","5":"19419","creation_date":"1358971288","6":"1358971288"}]},"4409":{"script_id":"4409","0":"4409","script_name":"Vimpanel","1":"Vimpanel","script_type":"utility","2":"utility","summary":"A modern side panel for Vim","3":"A modern side panel for Vim","description":"* Add any folder to the panel\r\n* Each folder can be expanded independently\r\n* You can stick files in there as well\r\n* Drag and drop works too\r\n* Create and display any number of panels\r\n* Session support: find your panels and all other windows the way you left them when you exited Vim\r\n* Filesystem operations, including file copying using visual selection\r\n* Propper handling of Windows paths\r\n* Explore the filesystem without constrains, in explorer mode\r\n* Use it for project management, keeping bookmarks, notes or anything you like\r\n\r\nVisit the project page for more details: https:\/\/github.com\/mihaifm\/vimpanel","4":"* Add any folder to the panel\r\n* Each folder can be expanded independently\r\n* You can stick files in there as well\r\n* Drag and drop works too\r\n* Create and display any number of panels\r\n* Session support: find your panels and all other windows the way you left them when you exited Vim\r\n* Filesystem operations, including file copying using visual selection\r\n* Propper handling of Windows paths\r\n* Explore the filesystem without constrains, in explorer mode\r\n* Use it for project management, keeping bookmarks, notes or anything you like\r\n\r\nVisit the project page for more details: https:\/\/github.com\/mihaifm\/vimpanel","install_details":"","5":"","first_name":"Mihai","6":"Mihai","last_name":"Ciuraru","7":"Ciuraru","releases":[{"0":"4409","vim_version":"7.0","1":"7.0","script_version":"1.0.3","2":"1.0.3","version_comment":"New features: \r\nSupport for named sessions. \r\nNew commands to toggle panels on the left\/right side of the screen. \r\nToggle the display of hidden files\/folders","3":"New features: \r\nSupport for named sessions. \r\nNew commands to toggle panels on the left\/right side of the screen. \r\nToggle the display of hidden files\/folders","package":"vimpanel.zip","4":"vimpanel.zip","src_id":"20678","5":"20678","creation_date":"1376903277","6":"1376903277"},{"0":"4409","vim_version":"7.3","1":"7.3","script_version":"1.0.0","2":"1.0.0","version_comment":"Initial upload","3":"Initial upload","package":"vimpanel.zip","4":"vimpanel.zip","src_id":"19418","5":"19418","creation_date":"1358940206","6":"1358940206"}]},"4408":{"script_id":"4408","0":"4408","script_name":"accelerated-jk","1":"accelerated-jk","script_type":"utility","2":"utility","summary":"accelerate 'j' and 'k' moving","3":"accelerate 'j' and 'k' moving","description":"accelerated-jk accelerates 'j'\/'k' mappings' steps while 'j' or 'k' is repeating.\r\nWhen the interval of key-repeat interval takes more than 150 ms, the step is\r\nreset.","4":"accelerated-jk accelerates 'j'\/'k' mappings' steps while 'j' or 'k' is repeating.\r\nWhen the interval of key-repeat interval takes more than 150 ms, the step is\r\nreset.","install_details":"1. unzip the archived file you downloaded.\r\n\r\n2. copy files in autoload\/ and plugin\/ to your Vim runtime path.\r\n\r\n3. add settings to your .vimrc for replacing 'j' and 'k' mappings.\r\n\r\n  e.g.\r\n        nmap j <Plug>(accelerated_jk_gj)\r\n        nmap k <Plug>(accelerated_jk_gk)","5":"1. unzip the archived file you downloaded.\r\n\r\n2. copy files in autoload\/ and plugin\/ to your Vim runtime path.\r\n\r\n3. add settings to your .vimrc for replacing 'j' and 'k' mappings.\r\n\r\n  e.g.\r\n        nmap j <Plug>(accelerated_jk_gj)\r\n        nmap k <Plug>(accelerated_jk_gk)","first_name":"Linda","6":"Linda","last_name":"Rhysd","7":"Rhysd","releases":[{"0":"4408","vim_version":"7.2","1":"7.2","script_version":"1.0.0","2":"1.0.0","version_comment":"Initial upload","3":"Initial upload","package":"accelerated-jk-ver1.0.0.zip","4":"accelerated-jk-ver1.0.0.zip","src_id":"19417","5":"19417","creation_date":"1358936811","6":"1358936811"}]},"4407":{"script_id":"4407","0":"4407","script_name":"haskell.vim","1":"haskell.vim","script_type":"indent","2":"indent","summary":"Another Haskell indent plugin.","3":"Another Haskell indent plugin.","description":"Another indentation script for Haskell. There is already one vimscript #1968.\r\n\r\nMappings:\r\n\r\nIf no 'g:Haskell_no_mapping' defined, <BS> and <C-d> will be imapped to dedent.","4":"Another indentation script for Haskell. There is already one vimscript #1968.\r\n\r\nMappings:\r\n\r\nIf no 'g:Haskell_no_mapping' defined, <BS> and <C-d> will be imapped to dedent.","install_details":"Put the script at ~\/.vim\/indent .","5":"Put the script at ~\/.vim\/indent .","first_name":"lilydjwg","6":"lilydjwg","last_name":" ","7":" ","releases":[{"0":"4407","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"haskell.vim","4":"haskell.vim","src_id":"19414","5":"19414","creation_date":"1358929146","6":"1358929146"}]},"4406":{"script_id":"4406","0":"4406","script_name":"lithochromatic","1":"lithochromatic","script_type":"color scheme","2":"color scheme","summary":"A clarity oriented, consistent vim color theme.","3":"A clarity oriented, consistent vim color theme.","description":"Lithochromatic Theme for Vim\r\n\r\nFor more info, see https:\/\/github.com\/cadadr\/vim-lithochromatic\r\n\r\nI'll likely forget to upload new versions here, so you probably want to watch the github.","4":"Lithochromatic Theme for Vim\r\n\r\nFor more info, see https:\/\/github.com\/cadadr\/vim-lithochromatic\r\n\r\nI'll likely forget to upload new versions here, so you probably want to watch the github.","install_details":"I've been away from vim for quite a while, so I don't know which package manager is used widely these days, but using one should be straightforward.\r\n\r\nTo install manually:\r\n\r\n$ mkdir -p ~\/.vim\/colors\/\r\n$ curl https:\/\/raw.github.com\/cadadr\/vim-lithochromatic\/default\/colors\/lithochromatic.vim > ~\/.vim\/colors\/lithochromatic.vim\r\nThen set your colorscheme to lithochromatic:\r\n\r\nif &term=~'xterm' || has(\"gui_running\")\r\n    set t_Co=256\r\n    colorscheme lithochromatic\r\nendif\r\nImportant: This color scheme only supports 256-color terminals and GUI Vim.","5":"I've been away from vim for quite a while, so I don't know which package manager is used widely these days, but using one should be straightforward.\r\n\r\nTo install manually:\r\n\r\n$ mkdir -p ~\/.vim\/colors\/\r\n$ curl https:\/\/raw.github.com\/cadadr\/vim-lithochromatic\/default\/colors\/lithochromatic.vim > ~\/.vim\/colors\/lithochromatic.vim\r\nThen set your colorscheme to lithochromatic:\r\n\r\nif &term=~'xterm' || has(\"gui_running\")\r\n    set t_Co=256\r\n    colorscheme lithochromatic\r\nendif\r\nImportant: This color scheme only supports 256-color terminals and GUI Vim.","first_name":"G\u00c3\u00b6ktu\u011f","6":"G\u00c3\u00b6ktuğ","last_name":"Kayaalp","7":"Kayaalp","releases":[{"0":"4406","vim_version":"7.0","1":"7.0","script_version":"1.2","2":"1.2","version_comment":"Add support for spell.","3":"Add support for spell.","package":"lithochromatic-1.2.tar.gz","4":"lithochromatic-1.2.tar.gz","src_id":"21015","5":"21015","creation_date":"1383907684","6":"1383907684"},{"0":"4406","vim_version":"7.3","1":"7.3","script_version":"1.1","2":"1.1","version_comment":"Drop patch number from version.\r\n\r\nEnhance markdown highlighting.","3":"Drop patch number from version.\r\n\r\nEnhance markdown highlighting.","package":"lithochromatic-1.1.tar.gz","4":"lithochromatic-1.1.tar.gz","src_id":"20587","5":"20587","creation_date":"1375424543","6":"1375424543"},{"0":"4406","vim_version":"7.3","1":"7.3","script_version":"1.0.7","2":"1.0.7","version_comment":"Fixes SpecialKey so that tabs do not look different from background when :set listchars.","3":"Fixes SpecialKey so that tabs do not look different from background when :set listchars.","package":"lithochromatic-1.0.7.tar.gz","4":"lithochromatic-1.0.7.tar.gz","src_id":"20325","5":"20325","creation_date":"1370736129","6":"1370736129"},{"0":"4406","vim_version":"7.3","1":"7.3","script_version":"1.0.6","2":"1.0.6","version_comment":"Fixes NonText display. Also switched to MIT License.","3":"Fixes NonText display. Also switched to MIT License.","package":"lithochromatic-1.0.6.tar.gz","4":"lithochromatic-1.0.6.tar.gz","src_id":"20324","5":"20324","creation_date":"1370725480","6":"1370725480"},{"0":"4406","vim_version":"7.0","1":"7.0","script_version":"1.0.5","2":"1.0.5","version_comment":"Removed all bolds.","3":"Removed all bolds.","package":"lithochromatic-1.0.5.tar.gz","4":"lithochromatic-1.0.5.tar.gz","src_id":"19801","5":"19801","creation_date":"1365671384","6":"1365671384"},{"0":"4406","vim_version":"7.3","1":"7.3","script_version":"1.0.4","2":"1.0.4","version_comment":"Fixes Pmenu colors for Gvim.","3":"Fixes Pmenu colors for Gvim.","package":"lithochromatic-1.0.4.tar.gz","4":"lithochromatic-1.0.4.tar.gz","src_id":"19596","5":"19596","creation_date":"1362516518","6":"1362516518"},{"0":"4406","vim_version":"7.3","1":"7.3","script_version":"1.0.3","2":"1.0.3","version_comment":"I don't know why I skipped 1.0.2, but it just happened. This version includes changes that enrich the look of Js and Css files, Markdown files, and improves on gui\/terminal consistency.","3":"I don't know why I skipped 1.0.2, but it just happened. This version includes changes that enrich the look of Js and Css files, Markdown files, and improves on gui\/terminal consistency.","package":"lithochromatic-1.0.3.tar.gz","4":"lithochromatic-1.0.3.tar.gz","src_id":"19480","5":"19480","creation_date":"1360324494","6":"1360324494"},{"0":"4406","vim_version":"7.3","1":"7.3","script_version":"1.0.1","2":"1.0.1","version_comment":"Fixes a silly mistake in the licence text.","3":"Fixes a silly mistake in the licence text.","package":"lithochromatic-1.0.1.tar.gz","4":"lithochromatic-1.0.1.tar.gz","src_id":"19441","5":"19441","creation_date":"1359376948","6":"1359376948"},{"0":"4406","vim_version":"7.3","1":"7.3","script_version":"1.0.0","2":"1.0.0","version_comment":"Initial upload","3":"Initial upload","package":"lithochromatic-1.0.0.tar.gz","4":"lithochromatic-1.0.0.tar.gz","src_id":"19413","5":"19413","creation_date":"1358902719","6":"1358902719"}]},"4405":{"script_id":"4405","0":"4405","script_name":"LaTeX-Support","1":"LaTeX-Support","script_type":"utility","2":"utility","summary":"LaTeX IDE -- Insert commands, run the typesetter and BibTeX and look up help","3":"LaTeX IDE -- Insert commands, run the typesetter and BibTeX and look up help","description":"LaTeX-IDE for Vim\/gVim is written to considerably speed up typesetting a\r\ndocument in a consistent style. This is done by inserting complete statements,\r\nidioms, code snippets, templates, and comments. Compiling and viewing a\r\ndocument, format conversion and running make can be done with a few keystrokes.\r\n\r\n- insert complete but empty statements\r\n- insert various types of comments\r\n- insert often used code snippets\r\n- change existing templates, add new templates\r\n- read, write, and maintain your own code snippets in a separate directory\r\n- show compilation errors in a quickfix window\r\n\r\nSome screen shots :  https:\/\/wolfgangmehner.github.io\/vim-plugins\/latexsupport.html\r\n\r\nFor plug-in managers :  https:\/\/github.com\/WolfgangMehner\/latex-support\r\n\r\nThe help file online :  https:\/\/wolfgangmehner.github.io\/vim-plugins\/doc\/latexsupport.html\r\n\r\nThe key mappings of this plug-in :  https:\/\/wolfgangmehner.github.io\/vim-plugins\/latexsupport\/latex-hotkeys.pdf\r\n\r\nDOCUMENTATION\r\n--------------------------------------------------------\r\nThis plug-in comes with a help file (latexsupport.txt). Read it with\r\n\r\n    :help latexsupport\r\n\r\n** PLEASE READ THE DOCUMENTATION **\r\n\r\nEditing actions differ for different modes! There are a lot of features which\r\ncan be configured or customized to match your needs.\r\n\r\n","4":"LaTeX-IDE for Vim\/gVim is written to considerably speed up typesetting a\r\ndocument in a consistent style. This is done by inserting complete statements,\r\nidioms, code snippets, templates, and comments. Compiling and viewing a\r\ndocument, format conversion and running make can be done with a few keystrokes.\r\n\r\n- insert complete but empty statements\r\n- insert various types of comments\r\n- insert often used code snippets\r\n- change existing templates, add new templates\r\n- read, write, and maintain your own code snippets in a separate directory\r\n- show compilation errors in a quickfix window\r\n\r\nSome screen shots :  https:\/\/wolfgangmehner.github.io\/vim-plugins\/latexsupport.html\r\n\r\nFor plug-in managers :  https:\/\/github.com\/WolfgangMehner\/latex-support\r\n\r\nThe help file online :  https:\/\/wolfgangmehner.github.io\/vim-plugins\/doc\/latexsupport.html\r\n\r\nThe key mappings of this plug-in :  https:\/\/wolfgangmehner.github.io\/vim-plugins\/latexsupport\/latex-hotkeys.pdf\r\n\r\nDOCUMENTATION\r\n--------------------------------------------------------\r\nThis plug-in comes with a help file (latexsupport.txt). Read it with\r\n\r\n    :help latexsupport\r\n\r\n** PLEASE READ THE DOCUMENTATION **\r\n\r\nEditing actions differ for different modes! There are a lot of features which\r\ncan be configured or customized to match your needs.\r\n\r\n","install_details":"Copy the zip archive latex-support.zip to $HOME\/.vim\/ or $VIM\/vimfiles\r\n(on the Windows platforms) and run\r\n    unzip latex-support.zip\r\nIf you have already an older version of this plug-in and you have modified the\r\ntemplate files you may want to save your templates first or copy the files from\r\nthe archive by hand. See also the file README.md within the zip file.","5":"Copy the zip archive latex-support.zip to $HOME\/.vim\/ or $VIM\/vimfiles\r\n(on the Windows platforms) and run\r\n    unzip latex-support.zip\r\nIf you have already an older version of this plug-in and you have modified the\r\ntemplate files you may want to save your templates first or copy the files from\r\nthe archive by hand. See also the file README.md within the zip file.","first_name":"Fritz","6":"Fritz","last_name":"Mehner","7":"Mehner","releases":[{"0":"4405","vim_version":"7.3","1":"7.3","script_version":"1.2","2":"1.2","version_comment":"- Add 'g:Latex_CustomTemplateFile'.\r\n- Add template personalization file and setup wizard.\r\n- Change some templates.\r\n- Add maps to bibtex buffers.","3":"- Add 'g:Latex_CustomTemplateFile'.\r\n- Add template personalization file and setup wizard.\r\n- Change some templates.\r\n- Add maps to bibtex buffers.","package":"latex-support.zip","4":"latex-support.zip","src_id":"24468","5":"24468","creation_date":"1472059648","6":"1472059648"},{"0":"4405","vim_version":"7.0","1":"7.0","script_version":"1.1.1","2":"1.1.1","version_comment":"- Added some new templates.\r\n- Added 'Latex_SetMapLeader' and 'Latex_ResetMapLeader'.\r\n- Bugfix: Resetting maplocalleader in filetype plug-in after setting it to the value of\r\n  g:Latex_MapLeader.\r\n- Bugfix: Better compatibility with custom mappings\r\n  (use \"normal!\" and \"noremap\" consistently).\r\n- Bugfix: Setup of local templates in case of global installation.\r\n- Bugfix: Renamed function which were named \"g:*\".\r\n- Always load the newest version of the template engine available on 'runtimepath'.","3":"- Added some new templates.\r\n- Added 'Latex_SetMapLeader' and 'Latex_ResetMapLeader'.\r\n- Bugfix: Resetting maplocalleader in filetype plug-in after setting it to the value of\r\n  g:Latex_MapLeader.\r\n- Bugfix: Better compatibility with custom mappings\r\n  (use \"normal!\" and \"noremap\" consistently).\r\n- Bugfix: Setup of local templates in case of global installation.\r\n- Bugfix: Renamed function which were named \"g:*\".\r\n- Always load the newest version of the template engine available on 'runtimepath'.","package":"latex-support.zip","4":"latex-support.zip","src_id":"22357","5":"22357","creation_date":"1408733923","6":"1408733923"},{"0":"4405","vim_version":"7.0","1":"7.0","script_version":"1.1","2":"1.1","version_comment":"- Beamer templates and snippets added.\r\n- Template added.\r\n- Integration of Make moved into the toolbox.\r\n- New map \\rc to start a converter.\r\n- Bugfix: Setup of local templates in case of global installation.\r\n- Bugfix: Map and menu entry 'Snippets->edit global templates'.\r\n- Bugfix: Starting an external viewer now works under Windows.\r\n- Minor bugfixes and improvements.","3":"- Beamer templates and snippets added.\r\n- Template added.\r\n- Integration of Make moved into the toolbox.\r\n- New map \\rc to start a converter.\r\n- Bugfix: Setup of local templates in case of global installation.\r\n- Bugfix: Map and menu entry 'Snippets->edit global templates'.\r\n- Bugfix: Starting an external viewer now works under Windows.\r\n- Minor bugfixes and improvements.","package":"latex-support.zip","4":"latex-support.zip","src_id":"21339","5":"21339","creation_date":"1389985726","6":"1389985726"},{"0":"4405","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"latex-support.zip","4":"latex-support.zip","src_id":"19411","5":"19411","creation_date":"1358854304","6":"1358854304"}]},"4404":{"script_id":"4404","0":"4404","script_name":"vim-line-numbers","1":"vim-line-numbers","script_type":"ftplugin","2":"ftplugin","summary":"adds line-numbers & ruler to most edit files","3":"adds line-numbers & ruler to most edit files","description":"This plugin adds line numbers and enables the ruler for all plugin files. this prevents them from showing up in other kind of splits or windows (such as your NERD_tree window). You can find the source at https:\/\/github.com\/Elzair\/vim-line-numbers","4":"This plugin adds line numbers and enables the ruler for all plugin files. this prevents them from showing up in other kind of splits or windows (such as your NERD_tree window). You can find the source at https:\/\/github.com\/Elzair\/vim-line-numbers","install_details":"To make it easy on yourself, use Pathogen and then type \"cd ~\/.vim\/bundle; git clone git:\/\/github.com\/Elzair\/vim-line-numbers.git\"","5":"To make it easy on yourself, use Pathogen and then type \"cd ~\/.vim\/bundle; git clone git:\/\/github.com\/Elzair\/vim-line-numbers.git\"","first_name":"Philip","6":"Philip","last_name":"Woods","7":"Woods","releases":[{"0":"4404","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"vim-line-numbers.tar.gz","4":"vim-line-numbers.tar.gz","src_id":"19408","5":"19408","creation_date":"1358796699","6":"1358796699"}]},"4403":{"script_id":"4403","0":"4403","script_name":"togglecursor","1":"togglecursor","script_type":"utility","2":"utility","summary":"Changes cursor shape in supported terminals.","3":"Changes cursor shape in supported terminals.","description":"This plugin aims to provide the ability to change the cursor when entering Vim's\r\ninsert mode on terminals that support it.  Currently, that's limited to iTerm,\r\nKonsole, XTerm, and VTE-based terminals (version v0.39 or higher).","4":"This plugin aims to provide the ability to change the cursor when entering Vim's\r\ninsert mode on terminals that support it.  Currently, that's limited to iTerm,\r\nKonsole, XTerm, and VTE-based terminals (version v0.39 or higher).","install_details":"Unzip into ``~\/.vim`` (or ``%USERPROFILE%\\vimfiles`` on Windows).  You may also\r\ninstall it under pathogen by extracting it into it's own directory under\r\n``bundle``, such as ``~\/.vim\/bundle\/vim-togglecursor``.\r\n\r\nThe latest version can be obtained from:\r\n    https:\/\/github.com\/jszakmeister\/vim-togglecursor","5":"Unzip into ``~\/.vim`` (or ``%USERPROFILE%\\vimfiles`` on Windows).  You may also\r\ninstall it under pathogen by extracting it into it's own directory under\r\n``bundle``, such as ``~\/.vim\/bundle\/vim-togglecursor``.\r\n\r\nThe latest version can be obtained from:\r\n    https:\/\/github.com\/jszakmeister\/vim-togglecursor","first_name":"John","6":"John","last_name":"Szakmeister","7":"Szakmeister","releases":[{"0":"4403","vim_version":"7.3","1":"7.3","script_version":"0.5.1","2":"0.5.1","version_comment":"Now supports OS X's native Terminal.app in Sierra or better.","3":"Now supports OS X's native Terminal.app in Sierra or better.","package":"togglecursor-0.5.1.zip","4":"togglecursor-0.5.1.zip","src_id":"24814","5":"24814","creation_date":"1482487062","6":"1482487062"},{"0":"4403","vim_version":"7.3","1":"7.3","script_version":"0.5.0","2":"0.5.0","version_comment":"Default to blinking forms of the cursors to match gvim's behavior.  This also adds support for setting NVIM_TUI_ENABLE_CURSOR_SHAPE under Neovim, and VTE3 support (thanks Keerthan Jaic), the ability to force a particular kind of escape sequence, and the ability to skip t_ti initialization if your terminal is having issues (mainly VTE 0.40.2-based ones).","3":"Default to blinking forms of the cursors to match gvim's behavior.  This also adds support for setting NVIM_TUI_ENABLE_CURSOR_SHAPE under Neovim, and VTE3 support (thanks Keerthan Jaic), the ability to force a particular kind of escape sequence, and the ability to skip t_ti initialization if your terminal is having issues (mainly VTE 0.40.2-based ones).","package":"togglecursor-0.5.0.zip","4":"togglecursor-0.5.0.zip","src_id":"23523","5":"23523","creation_date":"1439982605","6":"1439982605"},{"0":"4403","vim_version":"7.3","1":"7.3","script_version":"0.3.0","2":"0.3.0","version_comment":"Recognize Konsole via TERM_PROGRAM, and replace mode support.","3":"Recognize Konsole via TERM_PROGRAM, and replace mode support.","package":"togglecursor-0.3.0.zip","4":"togglecursor-0.3.0.zip","src_id":"22670","5":"22670","creation_date":"1417781423","6":"1417781423"},{"0":"4403","vim_version":"7.3","1":"7.3","script_version":"0.2.0","2":"0.2.0","version_comment":"Adds support for blinking cursors, and a uses a line cursor by default on xterms that support it.\r\n\r\nThanks to Keerthan Jaic for the patches!","3":"Adds support for blinking cursors, and a uses a line cursor by default on xterms that support it.\r\n\r\nThanks to Keerthan Jaic for the patches!","package":"togglecursor-0.2.0.zip","4":"togglecursor-0.2.0.zip","src_id":"21422","5":"21422","creation_date":"1391425712","6":"1391425712"},{"0":"4403","vim_version":"7.3","1":"7.3","script_version":"0.1.1","2":"0.1.1","version_comment":"Fixed wrong variable name is documentation for disabling the plugin, and added one more way of detecting iTerm2.","3":"Fixed wrong variable name is documentation for disabling the plugin, and added one more way of detecting iTerm2.","package":"togglecursor-0.1.1.zip","4":"togglecursor-0.1.1.zip","src_id":"20603","5":"20603","creation_date":"1375696993","6":"1375696993"},{"0":"4403","vim_version":"7.3","1":"7.3","script_version":"0.1.0","2":"0.1.0","version_comment":"Initial upload","3":"Initial upload","package":"togglecursor.zip","4":"togglecursor.zip","src_id":"19402","5":"19402","creation_date":"1358726382","6":"1358726382"}]},"4402":{"script_id":"4402","0":"4402","script_name":"vim-darksea","1":"vim-darksea","script_type":"color scheme","2":"color scheme","summary":"A vim colorscheme","3":"A vim colorscheme","description":"This is a simple 256 colors colorscheme, using mainly cold colors. Feel free to give feedback !\r\n\r\nYou can find latest version here: https:\/\/github.com\/gnujeremie\/colorscheme-gnujeremie","4":"This is a simple 256 colors colorscheme, using mainly cold colors. Feel free to give feedback !\r\n\r\nYou can find latest version here: https:\/\/github.com\/gnujeremie\/colorscheme-gnujeremie","install_details":"","5":"","first_name":"Gnu","6":"Gnu","last_name":"J\u00c3\u00a9r\u00c3\u00a9mie","7":"J\u00c3\u00a9r\u00c3\u00a9mie","releases":[{"0":"4402","vim_version":"7.3","1":"7.3","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"vim-darksea.vim.tgz","4":"vim-darksea.vim.tgz","src_id":"19400","5":"19400","creation_date":"1358692926","6":"1358692926"}]},"4401":{"script_id":"4401","0":"4401","script_name":"vim-sunshine","1":"vim-sunshine","script_type":"color scheme","2":"color scheme","summary":"A vim colorscheme","3":"A vim colorscheme","description":"This is a simple 256 colors colorscheme, using mainly warm colors. Feel free to give feedback !\r\n\r\nYou can find latest version here: https:\/\/github.com\/gnujeremie\/colorscheme-gnujeremie\r\n\r\nScreenshots:\r\n\r\nhttp:\/\/gnujeremie.net\/vim-sunshine\/sunshine-php.png\r\nhttp:\/\/gnujeremie.net\/vim-sunshine\/sunshine-html.png","4":"This is a simple 256 colors colorscheme, using mainly warm colors. Feel free to give feedback !\r\n\r\nYou can find latest version here: https:\/\/github.com\/gnujeremie\/colorscheme-gnujeremie\r\n\r\nScreenshots:\r\n\r\nhttp:\/\/gnujeremie.net\/vim-sunshine\/sunshine-php.png\r\nhttp:\/\/gnujeremie.net\/vim-sunshine\/sunshine-html.png","install_details":"","5":"","first_name":"Gnu","6":"Gnu","last_name":"J\u00c3\u00a9r\u00c3\u00a9mie","7":"J\u00c3\u00a9r\u00c3\u00a9mie","releases":[{"0":"4401","vim_version":"7.3","1":"7.3","script_version":"0.1.1","2":"0.1.1","version_comment":"Update colors after several days using it for real.","3":"Update colors after several days using it for real.","package":"vim-sunshine.vim.tgz","4":"vim-sunshine.vim.tgz","src_id":"19412","5":"19412","creation_date":"1358885301","6":"1358885301"},{"0":"4401","vim_version":"7.3","1":"7.3","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"vim-sunshine.vim.tgz","4":"vim-sunshine.vim.tgz","src_id":"19399","5":"19399","creation_date":"1358692651","6":"1358692651"}]},"4400":{"script_id":"4400","0":"4400","script_name":"tube.vim","1":"tube.vim","script_type":"utility","2":"utility","summary":"Painless MacVim\/Terminal interaction","3":"Painless MacVim\/Terminal interaction","description":"\r\nTube provides a tiny interface for sending commands from \r\nMacVim to a separate iTerm or Terminal window without leaving MacVim. \r\n\r\nDocumentation at https:\/\/github.com\/gcmt\/tube.vim","4":"\r\nTube provides a tiny interface for sending commands from \r\nMacVim to a separate iTerm or Terminal window without leaving MacVim. \r\n\r\nDocumentation at https:\/\/github.com\/gcmt\/tube.vim","install_details":"\r\nInstall with your favorite plugin manager.","5":"\r\nInstall with your favorite plugin manager.","first_name":"geck","6":"geck","last_name":" ","7":" ","releases":[{"0":"4400","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"First stable release","3":"First stable release","package":"tube.zip","4":"tube.zip","src_id":"22169","5":"22169","creation_date":"1404840963","6":"1404840963"}]},"4399":{"script_id":"4399","0":"4399","script_name":"(color scheme) Faded-White","1":"(color scheme) Faded-White","script_type":"color scheme","2":"color scheme","summary":"A light color scheme that looks as though it's been through the wash.","3":"A light color scheme that looks as though it's been through the wash.","description":"This is a light color scheme that looks as though it's been through the wash a few too many times. \r\n\r\nThe background isn't quite white and the colors aren't full color. Fairly good contrast and easy on the eyes.\r\n\r\nNOTE:\r\nI have not adjusted the terminal colors from my \"faded-black\" color scheme (vimscript#4398).\r\n","4":"This is a light color scheme that looks as though it's been through the wash a few too many times. \r\n\r\nThe background isn't quite white and the colors aren't full color. Fairly good contrast and easy on the eyes.\r\n\r\nNOTE:\r\nI have not adjusted the terminal colors from my \"faded-black\" color scheme (vimscript#4398).\r\n","install_details":"Copy\/Save this file to your \"colors\" directory.","5":"Copy\/Save this file to your \"colors\" directory.","first_name":"John","6":"John","last_name":"Kaul","7":"Kaul","releases":[{"0":"4399","vim_version":"7.0","1":"7.0","script_version":"0.1.0","2":"0.1.0","version_comment":"Initial upload","3":"Initial upload","package":"faded-white.vim","4":"faded-white.vim","src_id":"19381","5":"19381","creation_date":"1358355208","6":"1358355208"}]},"4398":{"script_id":"4398","0":"4398","script_name":"(color scheme) Faded-Black","1":"(color scheme) Faded-Black","script_type":"color scheme","2":"color scheme","summary":"A dark color scheme that looks as though it's been through the wash.","3":"A dark color scheme that looks as though it's been through the wash.","description":"This is a dark color scheme that looks as though it's been through the wash a few too many times.\r\n\r\nThe background isn't quite black and the colors aren't full color. Good contrast and easy on the eyes.","4":"This is a dark color scheme that looks as though it's been through the wash a few too many times.\r\n\r\nThe background isn't quite black and the colors aren't full color. Good contrast and easy on the eyes.","install_details":"Copy\/Save this file to your \"colors\" directory.","5":"Copy\/Save this file to your \"colors\" directory.","first_name":"John","6":"John","last_name":"Kaul","7":"Kaul","releases":[{"0":"4398","vim_version":"7.0","1":"7.0","script_version":"0.1.2","2":"0.1.2","version_comment":"Fixed: \r\no  Added and adjusted some terminal colors ","3":"Fixed: \r\no  Added and adjusted some terminal colors ","package":"faded-black.vim","4":"faded-black.vim","src_id":"19910","5":"19910","creation_date":"1366732274","6":"1366732274"},{"0":"4398","vim_version":"7.0","1":"7.0","script_version":"0.1.1","2":"0.1.1","version_comment":"Fixed:\r\no  Search background color\r\no  Include statement foreground color\r\no  Status lines colors\r\n","3":"Fixed:\r\no  Search background color\r\no  Include statement foreground color\r\no  Status lines colors\r\n","package":"faded-black.vim","4":"faded-black.vim","src_id":"19807","5":"19807","creation_date":"1365795714","6":"1365795714"},{"0":"4398","vim_version":"7.0","1":"7.0","script_version":"0.1.0","2":"0.1.0","version_comment":"Initial upload","3":"Initial upload","package":"faded-black.vim","4":"faded-black.vim","src_id":"19380","5":"19380","creation_date":"1358350408","6":"1358350408"}]},"4397":{"script_id":"4397","0":"4397","script_name":"CF Utils","1":"CF Utils","script_type":"syntax","2":"syntax","summary":"ColdFusion (CF) syntax highlighting and utilities for Vim","3":"ColdFusion (CF) syntax highlighting and utilities for Vim","description":"CF Utils for Vim was born out of the frustration with trying to write modern CF in Vim. Existing versions of the cf.vim syntax file don't support things like script based CFCs.\r\n\r\nWith CFML Utils, I also wanted to turn give Vim some basic functions found in ColdFusion Builder extensions. Things like the QueryParam Scanner and VarScoper extensions are awesome features and make debugging legacy (or poorly written code) a breeze. In future versions of CF Utils, I also want to add basic RDS support to make general debugging easier in Vim.","4":"CF Utils for Vim was born out of the frustration with trying to write modern CF in Vim. Existing versions of the cf.vim syntax file don't support things like script based CFCs.\r\n\r\nWith CFML Utils, I also wanted to turn give Vim some basic functions found in ColdFusion Builder extensions. Things like the QueryParam Scanner and VarScoper extensions are awesome features and make debugging legacy (or poorly written code) a breeze. In future versions of CF Utils, I also want to add basic RDS support to make general debugging easier in Vim.","install_details":"To install with Pathogen (vimscript #2332) unzip folder in ~\/.vim\/bundle\/cf-utils","5":"To install with Pathogen (vimscript #2332) unzip folder in ~\/.vim\/bundle\/cf-utils","first_name":"Dave","6":"Dave","last_name":"Long","7":"Long","releases":[{"0":"4397","vim_version":"7.0","1":"7.0","script_version":"0.8","2":"0.8","version_comment":"Initial upload","3":"Initial upload","package":"cf-utils.vim-master.zip","4":"cf-utils.vim-master.zip","src_id":"19373","5":"19373","creation_date":"1358179254","6":"1358179254"}]},"4396":{"script_id":"4396","0":"4396","script_name":"RocketJump","1":"RocketJump","script_type":"utility","2":"utility","summary":"Jump to a visible line using alphabetic signs instead of line numbers","3":"Jump to a visible line using alphabetic signs instead of line numbers","description":"RocketJump aims to make line navigation faster and easier by providing alphabetic signs as hints. The signs are placed for each second visible line so that only lowercase english letters are used (as the easiest characters to type). Once in sign mode, one can adjust this \"ruler\" by hitting space to shift all signs one line below (I found it to be less tensive for fingers than adding capital letters). Typing sign character moves cursor to corresponding line and exits sign mode.\r\n\r\nIn order to use sign jumps for yanking, deleting etc. a separate select state is provided: jumping creates linewise selection between jump points. Using sign jumps as motions for other commands is possible but not recommended -- Vim will treat it characterwise.\r\n\r\nUSAGE:\r\n(Default mappings are not meant to be used \"as is\", remapping them as single key commands is strongly advised)\r\n- Type gl to go into move state (jump in normal mode, change selection in visual mode);\r\n- Or type gn to go into select state (in normal mode stretches linewise selection to jump end line);\r\n- Adjust the signs with space key if required;\r\n- Type a sign character to jump to that line.\r\nWarning: using move state for motions (e.g., dgl<...>) will not work as one might expect, use select state instead (i.e., gn<...>d).\r\n\r\nSETTINGS (defaults listed):\r\n1. Starting ID for signs:\r\n    let g:rj_startid = 888888\r\n2. Characters used for signs:\r\n    let g:rj_chars = \"abcdefghijklmnopqrstuvwxyz\"\r\n3. Adjust command character\r\n    let g:rj_cmdchar = \" \"\r\n4. Sign color scheme\r\n    let g:rj_signscheme = (has(\"gui_running\")? \"guifg=burlywood3\" : \"ctermfg=burlywood3\")\r\n5. Mappings (declare g:rj_nomapping to disable them)\r\n    noremap <silent> gl :call RocketJump#PerformJump(0) <CR>\r\n    noremap <silent> gn V <bar> :call RocketJump#PerformJump(1) <CR>\r\n    vnoremap <silent> gl :call RocketJump#PerformJump(1) <CR>\r\n","4":"RocketJump aims to make line navigation faster and easier by providing alphabetic signs as hints. The signs are placed for each second visible line so that only lowercase english letters are used (as the easiest characters to type). Once in sign mode, one can adjust this \"ruler\" by hitting space to shift all signs one line below (I found it to be less tensive for fingers than adding capital letters). Typing sign character moves cursor to corresponding line and exits sign mode.\r\n\r\nIn order to use sign jumps for yanking, deleting etc. a separate select state is provided: jumping creates linewise selection between jump points. Using sign jumps as motions for other commands is possible but not recommended -- Vim will treat it characterwise.\r\n\r\nUSAGE:\r\n(Default mappings are not meant to be used \"as is\", remapping them as single key commands is strongly advised)\r\n- Type gl to go into move state (jump in normal mode, change selection in visual mode);\r\n- Or type gn to go into select state (in normal mode stretches linewise selection to jump end line);\r\n- Adjust the signs with space key if required;\r\n- Type a sign character to jump to that line.\r\nWarning: using move state for motions (e.g., dgl<...>) will not work as one might expect, use select state instead (i.e., gn<...>d).\r\n\r\nSETTINGS (defaults listed):\r\n1. Starting ID for signs:\r\n    let g:rj_startid = 888888\r\n2. Characters used for signs:\r\n    let g:rj_chars = \"abcdefghijklmnopqrstuvwxyz\"\r\n3. Adjust command character\r\n    let g:rj_cmdchar = \" \"\r\n4. Sign color scheme\r\n    let g:rj_signscheme = (has(\"gui_running\")? \"guifg=burlywood3\" : \"ctermfg=burlywood3\")\r\n5. Mappings (declare g:rj_nomapping to disable them)\r\n    noremap <silent> gl :call RocketJump#PerformJump(0) <CR>\r\n    noremap <silent> gn V <bar> :call RocketJump#PerformJump(1) <CR>\r\n    vnoremap <silent> gl :call RocketJump#PerformJump(1) <CR>\r\n","install_details":"Place in ~\/.vim\/plugin.","5":"Place in ~\/.vim\/plugin.","first_name":"Aleksey","6":"Aleksey","last_name":"Danilov","7":"Danilov","releases":[{"0":"4396","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"RocketJump.vim","4":"RocketJump.vim","src_id":"19369","5":"19369","creation_date":"1358161358","6":"1358161358"}]},"4395":{"script_id":"4395","0":"4395","script_name":"jk-jumps","1":"jk-jumps","script_type":"utility","2":"utility","summary":"Handle movements with j\/k as if they were real jumps","3":"Handle movements with j\/k as if they were real jumps","description":"You can easily use the |j| and |k| commands together with a count to jump up\r\nand down your file. Setting the |'relativenumber'| option makes this even\r\neasier. The only problem with this, is that Vim doesn't think of this kind of\r\nmovement as 'jumps'. (see |jump-motions| for the list). This can make using\r\nthe |jumplist| rather confusing.\r\nThis plugin tries to fix that by changing the j and k commands to act as\r\njumps, letting you use the jumplist to jump back and forward.","4":"You can easily use the |j| and |k| commands together with a count to jump up\r\nand down your file. Setting the |'relativenumber'| option makes this even\r\neasier. The only problem with this, is that Vim doesn't think of this kind of\r\nmovement as 'jumps'. (see |jump-motions| for the list). This can make using\r\nthe |jumplist| rather confusing.\r\nThis plugin tries to fix that by changing the j and k commands to act as\r\njumps, letting you use the jumplist to jump back and forward.","install_details":"Extract the zip to ~\/.vim or if you use Pathogen or a similar plugin you can also use the git-repository:\r\nhttps:\/\/github.com\/teranex\/jk-jumps.vim","5":"Extract the zip to ~\/.vim or if you use Pathogen or a similar plugin you can also use the git-repository:\r\nhttps:\/\/github.com\/teranex\/jk-jumps.vim","first_name":"Jeroen","6":"Jeroen","last_name":"Budts","7":"Budts","releases":[{"0":"4395","vim_version":"7.0","1":"7.0","script_version":"0.4","2":"0.4","version_comment":"Fixed jumping over closed folds","3":"Fixed jumping over closed folds","package":"jk-jumps.tar.gz","4":"jk-jumps.tar.gz","src_id":"19425","5":"19425","creation_date":"1359056563","6":"1359056563"},{"0":"4395","vim_version":"7.0","1":"7.0","script_version":"0.3","2":"0.3","version_comment":"correctly handle jumping up to a closed fold","3":"correctly handle jumping up to a closed fold","package":"jk-jumps.tar.gz","4":"jk-jumps.tar.gz","src_id":"19360","5":"19360","creation_date":"1358063842","6":"1358063842"},{"0":"4395","vim_version":"7.0","1":"7.0","script_version":"0.2","2":"0.2","version_comment":"Use <silent> in mappings","3":"Use <silent> in mappings","package":"jk-jumps.tar.gz","4":"jk-jumps.tar.gz","src_id":"19355","5":"19355","creation_date":"1358026920","6":"1358026920"},{"0":"4395","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"jk-jumps.vim.zip","4":"jk-jumps.vim.zip","src_id":"19354","5":"19354","creation_date":"1358024503","6":"1358024503"}]},"4394":{"script_id":"4394","0":"4394","script_name":"scriptease.vim","1":"scriptease.vim","script_type":"utility","2":"utility","summary":"A Vim plugin for Vim plugins","3":"A Vim plugin for Vim plugins","description":"Enjoy this amalgamation of crap I use for editing runtime files.\r\n\r\n:PP: Pretty print.\r\n:Runtime: Reload runtime files.  Like :runtime!, but it unlets any include guards first.\r\n:Disarm: Remove a runtime file's maps, commands, and autocommands, effectively disabling it.\r\n:Scriptnames: Load :scriptnames into the quickfix list.\r\n:Verbose: Capture the output of a :verbose invocation into the preview window.\r\n:Time: Measure how long a command takes.\r\n:Breakadd: Like its lowercase cousin, but makes it much easier to set breakpoints inside functions.  Also :Breakdel.\r\n:Vedit: Edit a file relative the runtime path. For example, `:Vedit plugin\/scriptease.vim`. Also, :Vsplit, :Vtabedit, etc.  Extracted from pathogen.vim (vimscript #2332).\r\nK: Look up the :help for the VimL construct under the cursor.\r\nzS: Show the active syntax highlighting groups under the cursor.\r\ng!: Eval a motion or selection as VimL and replace it with the result.  This is handy for doing math, even outside of VimL.  It's so handy, in fact, that it probably deserves its own plugin.\r\n\r\nhttps:\/\/github.com\/tpope\/vim-scriptease","4":"Enjoy this amalgamation of crap I use for editing runtime files.\r\n\r\n:PP: Pretty print.\r\n:Runtime: Reload runtime files.  Like :runtime!, but it unlets any include guards first.\r\n:Disarm: Remove a runtime file's maps, commands, and autocommands, effectively disabling it.\r\n:Scriptnames: Load :scriptnames into the quickfix list.\r\n:Verbose: Capture the output of a :verbose invocation into the preview window.\r\n:Time: Measure how long a command takes.\r\n:Breakadd: Like its lowercase cousin, but makes it much easier to set breakpoints inside functions.  Also :Breakdel.\r\n:Vedit: Edit a file relative the runtime path. For example, `:Vedit plugin\/scriptease.vim`. Also, :Vsplit, :Vtabedit, etc.  Extracted from pathogen.vim (vimscript #2332).\r\nK: Look up the :help for the VimL construct under the cursor.\r\nzS: Show the active syntax highlighting groups under the cursor.\r\ng!: Eval a motion or selection as VimL and replace it with the result.  This is handy for doing math, even outside of VimL.  It's so handy, in fact, that it probably deserves its own plugin.\r\n\r\nhttps:\/\/github.com\/tpope\/vim-scriptease","install_details":"Extract in ~\/.vim (~\\vimfiles on Windows).","5":"Extract in ~\/.vim (~\\vimfiles on Windows).","first_name":"Tim","6":"Tim","last_name":"Pope","7":"Pope","releases":[{"0":"4394","vim_version":"7.0","1":"7.0","script_version":"1.1","2":"1.1","version_comment":"Provide :Messages to load :messages into quickfix list.\r\nProvide lightweight REPL on :PP with no argument.\r\nSupport :PP <SID>Func() to call script function from current buffer.\r\nBenchmark repeat invocations on :[count]Time.\r\nShow :Verbose output in temp buffer only.\r\nSupport :source on fugitive:\/\/ paths.\r\nReplace g= map with g!.\r\nProvide basic Projectionist projections.\r\nSet dispatch.vim default task to :Runtime in .vim files.\r\nBug fixes and tweaks.","3":"Provide :Messages to load :messages into quickfix list.\r\nProvide lightweight REPL on :PP with no argument.\r\nSupport :PP <SID>Func() to call script function from current buffer.\r\nBenchmark repeat invocations on :[count]Time.\r\nShow :Verbose output in temp buffer only.\r\nSupport :source on fugitive:\/\/ paths.\r\nReplace g= map with g!.\r\nProvide basic Projectionist projections.\r\nSet dispatch.vim default task to :Runtime in .vim files.\r\nBug fixes and tweaks.","package":"scriptease.zip","4":"scriptease.zip","src_id":"28065","5":"28065","creation_date":"1653946105","6":"1653946105"},{"0":"4394","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"scriptease.zip","4":"scriptease.zip","src_id":"19352","5":"19352","creation_date":"1357970525","6":"1357970525"}]},"4393":{"script_id":"4393","0":"4393","script_name":"boshiamy input method keymap file","1":"boshiamy input method keymap file","script_type":"utility","2":"utility","summary":"This is the keymap file for Boshiamy chinese input method","3":"This is the keymap file for Boshiamy chinese input method","description":"將boshiamy.vim放在你vim的keymap目錄下。執行\r\n:set keymap=boshiamy\r\n你就可以在vim下使用蝦米輸入，<Ctrl-^>可以切換中英輸入模式。\r\n這個方法的唯一毛病就是如果同一個蝦米碼有兩個以上的選擇，你不能看到選擇。在注音輸法下，這可能會有問題，但蝦米輸入大致上不會有問題。我這篇介紹就是這樣打的。\r\n\r\n","4":"將boshiamy.vim放在你vim的keymap目錄下。執行\r\n:set keymap=boshiamy\r\n你就可以在vim下使用蝦米輸入，<Ctrl-^>可以切換中英輸入模式。\r\n這個方法的唯一毛病就是如果同一個蝦米碼有兩個以上的選擇，你不能看到選擇。在注音輸法下，這可能會有問題，但蝦米輸入大致上不會有問題。我這篇介紹就是這樣打的。\r\n\r\n","install_details":"put the file at keymap dir.\r\n:set keymap=boshiamy","5":"put the file at keymap dir.\r\n:set keymap=boshiamy","first_name":"Tsung-Han","6":"Tsung-Han","last_name":"Yang","7":"Yang","releases":[{"0":"4393","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"boshiamy.vim","4":"boshiamy.vim","src_id":"19342","5":"19342","creation_date":"1357790791","6":"1357790791"}]},"4392":{"script_id":"4392","0":"4392","script_name":"boshiamy-cue.vim","1":"boshiamy-cue.vim","script_type":"patch","2":"patch","summary":"Utilities for learning Boshiamy input method in traditional Chinese on vim","3":"Utilities for learning Boshiamy input method in traditional Chinese on vim","description":"Utilities for learning Boshiamy input method in traditional Chinese on vim and emacs.\r\n將boshiamy-cue.vim放在你的plugin目錄下。我使用WINDOWS，我就將這個檔案放在\"C:\\Program Files (x86)\\Vim\\vim73\\plugin\"。按F3可以在VIM下顯示蝦米碼。\r\n將boshiamy.vim放在你vim的keymap目錄下。執行\r\n:set keymap=boshiamy\r\n你就可以在vim下使用蝦米輸入，<Ctrl-^>可以切換中英輸入模式。\r\n這個方法的唯一毛病就是如果同一個蝦米碼有兩個以上的選擇，你不能看到選擇。在注音輸法下，這可能會有問題，但蝦米輸入大致上不會有問題。我這篇介紹就是這樣打的。","4":"Utilities for learning Boshiamy input method in traditional Chinese on vim and emacs.\r\n將boshiamy-cue.vim放在你的plugin目錄下。我使用WINDOWS，我就將這個檔案放在\"C:\\Program Files (x86)\\Vim\\vim73\\plugin\"。按F3可以在VIM下顯示蝦米碼。\r\n將boshiamy.vim放在你vim的keymap目錄下。執行\r\n:set keymap=boshiamy\r\n你就可以在vim下使用蝦米輸入，<Ctrl-^>可以切換中英輸入模式。\r\n這個方法的唯一毛病就是如果同一個蝦米碼有兩個以上的選擇，你不能看到選擇。在注音輸法下，這可能會有問題，但蝦米輸入大致上不會有問題。我這篇介紹就是這樣打的。","install_details":"put the file at plugin","5":"put the file at plugin","first_name":"Tsung-Han","6":"Tsung-Han","last_name":"Yang","7":"Yang","releases":[{"0":"4392","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"boshiamy-cue.vim","4":"boshiamy-cue.vim","src_id":"19341","5":"19341","creation_date":"1357790625","6":"1357790625"}]},"4391":{"script_id":"4391","0":"4391","script_name":"sensible.vim","1":"sensible.vim","script_type":"utility","2":"utility","summary":"Defaults everyone can agree on","3":"Defaults everyone can agree on","description":"Think of sensible.vim as one step above 'nocompatible' mode: a universal set of defaults that (hopefully) everyone can agree on.\r\n\r\n* If you're new to Vim, you can install this as a starting point, rather than copying some random vimrc you found.\r\n* If you're pair programming and you can't agree on whose vimrc to use, this can be your neutral territory.\r\n* If you're administrating a server with an account that's not exclusively yours, you can `scp` this up to make things a bit more tolerable.\r\n* If you're troubleshooting a plugin and need to rule out interference from your vimrc, having this installed will ensure you still have some basic amenities.\r\n\r\n## Features\r\n\r\nSee the source for the authoritative list of features.  (Don't worry, it's mostly :set calls.)  Here's a taste:\r\n\r\n* 'backspace': Backspace through anything in insert mode.\r\n* 'incsearch': Start searching before pressing enter.\r\n* 'listchars': Makes :set list (visible whitespace) prettier.\r\n* 'scrolloff': Always show at least one line above\/below the cursor.\r\n* runtime! macros\/matchit.vim: Load the version of matchit.vim that ships with Vim.\r\n\r\n\r\nhttps:\/\/github.com\/tpope\/vim-sensible","4":"Think of sensible.vim as one step above 'nocompatible' mode: a universal set of defaults that (hopefully) everyone can agree on.\r\n\r\n* If you're new to Vim, you can install this as a starting point, rather than copying some random vimrc you found.\r\n* If you're pair programming and you can't agree on whose vimrc to use, this can be your neutral territory.\r\n* If you're administrating a server with an account that's not exclusively yours, you can `scp` this up to make things a bit more tolerable.\r\n* If you're troubleshooting a plugin and need to rule out interference from your vimrc, having this installed will ensure you still have some basic amenities.\r\n\r\n## Features\r\n\r\nSee the source for the authoritative list of features.  (Don't worry, it's mostly :set calls.)  Here's a taste:\r\n\r\n* 'backspace': Backspace through anything in insert mode.\r\n* 'incsearch': Start searching before pressing enter.\r\n* 'listchars': Makes :set list (visible whitespace) prettier.\r\n* 'scrolloff': Always show at least one line above\/below the cursor.\r\n* runtime! macros\/matchit.vim: Load the version of matchit.vim that ships with Vim.\r\n\r\n\r\nhttps:\/\/github.com\/tpope\/vim-sensible","install_details":"Extract in ~\/.vim (~\\vimfiles on Windows).","5":"Extract in ~\/.vim (~\\vimfiles on Windows).","first_name":"Tim","6":"Tim","last_name":"Pope","7":"Pope","releases":[{"0":"4391","vim_version":"7.0","1":"7.0","script_version":"2.0","2":"2.0","version_comment":"Try to avoid overriding options set in user vimrc.\r\nProvide :DiffOrig, as found in the example at `:help :DiffOrig`.\r\nEnable Vim's included :Man command.\r\nEnable g:is_posix, for better highlighting of sh filetype.\r\nBreak undo with <C-G>u before delete word with <C-W>.\r\nAdd `set viewoptions-=options`.\r\nAdd `set display+=truncate`.\r\nAdd `set nolangremap`.\r\nAdd `set nocompatible`.\r\nReplace `set sidescrolloff=5` with `set sidescroll=1 sidescrolloff=2`.\r\nRemove `set autoindent`.\r\nRemove conditional `set encoding=utf-8`.\r\nDon't run `filetype plugin indent on` a second time.","3":"Try to avoid overriding options set in user vimrc.\r\nProvide :DiffOrig, as found in the example at `:help :DiffOrig`.\r\nEnable Vim's included :Man command.\r\nEnable g:is_posix, for better highlighting of sh filetype.\r\nBreak undo with <C-G>u before delete word with <C-W>.\r\nAdd `set viewoptions-=options`.\r\nAdd `set display+=truncate`.\r\nAdd `set nolangremap`.\r\nAdd `set nocompatible`.\r\nReplace `set sidescrolloff=5` with `set sidescroll=1 sidescrolloff=2`.\r\nRemove `set autoindent`.\r\nRemove conditional `set encoding=utf-8`.\r\nDon't run `filetype plugin indent on` a second time.","package":"sensible.zip","4":"sensible.zip","src_id":"28386","5":"28386","creation_date":"1679144283","6":"1679144283"},{"0":"4391","vim_version":"7.0","1":"7.0","script_version":"1.2","2":"1.2","version_comment":"Enable upwards tags file searching with `.\/tags;` in 'tags'.\r\nEnable joining commented lines with `formatoptions` j flag.\r\nRemove 'showcmd', 'shiftround', and 'fileformat' changes.\r\nAllow fish as 'shell' for compatible Vim versions.\r\nDon't override user specified 'ttimeoutlen'.\r\nDon't force `t_Co` to 16 for Eterm.\r\nAdd :diffupdate to CTRL-L map.","3":"Enable upwards tags file searching with `.\/tags;` in 'tags'.\r\nEnable joining commented lines with `formatoptions` j flag.\r\nRemove 'showcmd', 'shiftround', and 'fileformat' changes.\r\nAllow fish as 'shell' for compatible Vim versions.\r\nDon't override user specified 'ttimeoutlen'.\r\nDon't force `t_Co` to 16 for Eterm.\r\nAdd :diffupdate to CTRL-L map.","package":"sensible.zip","4":"sensible.zip","src_id":"25797","5":"25797","creation_date":"1516659774","6":"1516659774"},{"0":"4391","vim_version":"7.0","1":"7.0","script_version":"1.1","2":"1.1","version_comment":"Break undo after CTRL-U.\r\nSet shiftround.\r\nSet tabpagemax=50.\r\nSet nrformats-=octal.\r\nSet sessionoptions-=options.\r\nSet history=1000.\r\nSet ttimeoutlen=100.\r\nSet encoding=utf-8 in gvim.\r\nOverride shell=fish to use a supported shell instead.\r\nUse ASCII only listchars.\r\nDrop fillchars.\r\nDrop smartcase.\r\nDrop autowrite.\r\nDrop showmatch.\r\nDrop Y mapping.\r\nDon't clobber scroll offsets.\r\nDon't override a blank viminfo.\r\nDon't force UNIX line endings on Windows.\r\nStop setting temporary directories.","3":"Break undo after CTRL-U.\r\nSet shiftround.\r\nSet tabpagemax=50.\r\nSet nrformats-=octal.\r\nSet sessionoptions-=options.\r\nSet history=1000.\r\nSet ttimeoutlen=100.\r\nSet encoding=utf-8 in gvim.\r\nOverride shell=fish to use a supported shell instead.\r\nUse ASCII only listchars.\r\nDrop fillchars.\r\nDrop smartcase.\r\nDrop autowrite.\r\nDrop showmatch.\r\nDrop Y mapping.\r\nDon't clobber scroll offsets.\r\nDon't override a blank viminfo.\r\nDon't force UNIX line endings on Windows.\r\nStop setting temporary directories.","package":"sensible.zip","4":"sensible.zip","src_id":"21821","5":"21821","creation_date":"1398380929","6":"1398380929"},{"0":"4391","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"sensible.zip","4":"sensible.zip","src_id":"19340","5":"19340","creation_date":"1357787322","6":"1357787322"}]},"4390":{"script_id":"4390","0":"4390","script_name":"ferm.vim","1":"ferm.vim","script_type":"syntax","2":"syntax","summary":"Syntax highlighting for ferm; \"For Easy Rule Making\", a frontend for iptables.","3":"Syntax highlighting for ferm; \"For Easy Rule Making\", a frontend for iptables.","description":"This is a syntax highlighter for filetype 'ferm',  a frontend for iptables.\r\nferm = \"For Easy Rule Making\"\r\n\r\nFor latest developments, any mods, pull requests, etc, see:\r\n    https:\/\/github.com\/cometsong\/ferm.vim\r\n\r\n","4":"This is a syntax highlighter for filetype 'ferm',  a frontend for iptables.\r\nferm = \"For Easy Rule Making\"\r\n\r\nFor latest developments, any mods, pull requests, etc, see:\r\n    https:\/\/github.com\/cometsong\/ferm.vim\r\n\r\n","install_details":"Either copy the file inside the syntax dir to your own syntax dir...\r\nor use a plugin manager (e.g. pathogen, vim-addon-manager, etc) and install that way.  (See instructions for your own plugin manager for more info.)\r\n","5":"Either copy the file inside the syntax dir to your own syntax dir...\r\nor use a plugin manager (e.g. pathogen, vim-addon-manager, etc) and install that way.  (See instructions for your own plugin manager for more info.)\r\n","first_name":"Benjamin","6":"Benjamin","last_name":"L","7":"L","releases":[{"0":"4390","vim_version":"7.0","1":"7.0","script_version":"0.10","2":"0.10","version_comment":"Syntax repairs, feature additions, version updates. (Thanks @powerman!)","3":"Syntax repairs, feature additions, version updates. (Thanks @powerman!)","package":"ferm.vim.zip","4":"ferm.vim.zip","src_id":"27043","5":"27043","creation_date":"1583110565","6":"1583110565"},{"0":"4390","vim_version":"7.0","1":"7.0","script_version":"0.04","2":"0.04","version_comment":"Add ftdetect to identify ferm files.","3":"Add ftdetect to identify ferm files.","package":"ferm.vim.zip","4":"ferm.vim.zip","src_id":"19344","5":"19344","creation_date":"1357832475","6":"1357832475"},{"0":"4390","vim_version":"5.7","1":"5.7","script_version":"0.03","2":"0.03","version_comment":"Initial upload","3":"Initial upload","package":"ferm.vim.zip","4":"ferm.vim.zip","src_id":"19338","5":"19338","creation_date":"1357744889","6":"1357744889"}]},"4389":{"script_id":"4389","0":"4389","script_name":"ljyat","1":"ljyat","script_type":"color scheme","2":"color scheme","summary":"base on desert. author ljyat","3":"base on desert. author ljyat","description":"gvim.is better. base on desert","4":"gvim.is better. base on desert","install_details":"just copy this file to ~\/.vim\/colors\/ ","5":"just copy this file to ~\/.vim\/colors\/ ","first_name":"JingYu","6":"JingYu","last_name":"Li","7":"Li","releases":[{"0":"4389","vim_version":"7.0","1":"7.0","script_version":"2.0","2":"2.0","version_comment":"optimized ","3":"optimized ","package":"ljyat.vim","4":"ljyat.vim","src_id":"24229","5":"24229","creation_date":"1462448736","6":"1462448736"}]},"4388":{"script_id":"4388","0":"4388","script_name":"CoqIDE","1":"CoqIDE","script_type":"utility","2":"utility","summary":"Emulate Coq IDE in VIM","3":"Emulate Coq IDE in VIM","description":"You can use this script to make vim behaves like CoqIDE.\r\n\r\nThis script needs +perl vim option.\r\n\r\nShould work well on non-gui version of vim on unix systems.\r\n\r\nSee comments at beginning of coq_IDE.vim for more informations.\r\n","4":"You can use this script to make vim behaves like CoqIDE.\r\n\r\nThis script needs +perl vim option.\r\n\r\nShould work well on non-gui version of vim on unix systems.\r\n\r\nSee comments at beginning of coq_IDE.vim for more informations.\r\n","install_details":"Copy the coq_IDE.vim file to \"~\/.vim\/ftplugin\/coq_IDE.vim\" and add \"filetype plugin on\" in your \"~\/.vimrc\".\r\nAlternatively, you can \":source coq_IDE.vim\" whenever you want.\r\n\r\n\"coqtop\" should be accessible on PATH. If \"coqtop\" is not in\r\nyour PATH, add 'let CoqIDE_coqtop = \"\/path\/to\/coqtop\"' in your \"~\/.vimrc\".\r\n\r\nThis script comes with key bindings. These bindings are not loaded by default.\r\nYou can add \"let g:CoqIDEDefaultKeyMap = 1\" in your \"~\/.vimrc\" to load its automatically.\r\n\r\n<F2> undo last command\r\n<F3> send next command\r\n<F4> goto the command under the cursor\r\n<F5> undo all commands\r\n<F6> send all the buffer\r\n<F7> refresh screen\r\n<F8> kill coqtop\r\n\r\nb : break computation (only when a command is being interpreted)\r\n","5":"Copy the coq_IDE.vim file to \"~\/.vim\/ftplugin\/coq_IDE.vim\" and add \"filetype plugin on\" in your \"~\/.vimrc\".\r\nAlternatively, you can \":source coq_IDE.vim\" whenever you want.\r\n\r\n\"coqtop\" should be accessible on PATH. If \"coqtop\" is not in\r\nyour PATH, add 'let CoqIDE_coqtop = \"\/path\/to\/coqtop\"' in your \"~\/.vimrc\".\r\n\r\nThis script comes with key bindings. These bindings are not loaded by default.\r\nYou can add \"let g:CoqIDEDefaultKeyMap = 1\" in your \"~\/.vimrc\" to load its automatically.\r\n\r\n<F2> undo last command\r\n<F3> send next command\r\n<F4> goto the command under the cursor\r\n<F5> undo all commands\r\n<F6> send all the buffer\r\n<F7> refresh screen\r\n<F8> kill coqtop\r\n\r\nb : break computation (only when a command is being interpreted)\r\n","first_name":"Matthieu","6":"Matthieu","last_name":"Carlier","7":"Carlier","releases":[{"0":"4388","vim_version":"7.0","1":"7.0","script_version":"0.97b","2":"0.97b","version_comment":"Various improvements from Shu-Chun Weng:\r\n- Customize coqtop options: read from CoqIDE_coqtop_option variable\r\n- Check and show background goals when the foreground ones are all done.\r\n- ProceedUntilCursor reads the character under the cursor, too, so you can park the cursor on the period and still get the last command in.","3":"Various improvements from Shu-Chun Weng:\r\n- Customize coqtop options: read from CoqIDE_coqtop_option variable\r\n- Check and show background goals when the foreground ones are all done.\r\n- ProceedUntilCursor reads the character under the cursor, too, so you can park the cursor on the period and still get the last command in.","package":"coq_IDE-0.97b.tgz","4":"coq_IDE-0.97b.tgz","src_id":"20750","5":"20750","creation_date":"1378328350","6":"1378328350"},{"0":"4388","vim_version":"7.3","1":"7.3","script_version":"0.96b","2":"0.96b","version_comment":"Corrected script behavior when multiple files are edited.\r\nExpressions containing  '..' are now correctly sent to coqtop.","3":"Corrected script behavior when multiple files are edited.\r\nExpressions containing  '..' are now correctly sent to coqtop.","package":"coq_IDE-0.96b.tgz","4":"coq_IDE-0.96b.tgz","src_id":"20154","5":"20154","creation_date":"1368899484","6":"1368899484"},{"0":"4388","vim_version":"7.3","1":"7.3","script_version":"0.94b","2":"0.94b","version_comment":"Aesthetical changes + robustness on sourcing","3":"Aesthetical changes + robustness on sourcing","package":"coq_IDE-0.94b.tgz","4":"coq_IDE-0.94b.tgz","src_id":"19811","5":"19811","creation_date":"1365852237","6":"1365852237"},{"0":"4388","vim_version":"7.3","1":"7.3","script_version":"7.3","2":"7.3","version_comment":"Initial upload","3":"Initial upload","package":"coq_IDE.tgz","4":"coq_IDE.tgz","src_id":"19323","5":"19323","creation_date":"1357511776","6":"1357511776"}]},"4387":{"script_id":"4387","0":"4387","script_name":"projectroot","1":"projectroot","script_type":"utility","2":"utility","summary":"Automatic guessing of projectroots","3":"Automatic guessing of projectroots","description":"Github project: https:\/\/github.com\/dbakker\/vim-projectroot\r\n\r\nThere already are a ton of plugins (such as CtrlP) that try to guess what the main project folder is of a file that you're working on, but this plugin allows to easily re-use that functionality in your own custom mappings or scripts.\r\n\r\nFeatures:\r\n  * Works out-of-the-box on most projects by detecting folders such as .git.\r\n  * Very customizeable.\r\n  * Easy to use in mappings and your own scripts, just call ProjectRootGuess() to get the project root of the current file or ProjectRootGuess(file) for another file.\r\n  * Can be combined with existing plugins\r\n  * Tries to be as lightweight as possible. Only searches for a project root when a method such as ProjectRootGuess is used.\r\n\r\nMethods provided:\r\n  * ProjectRootGuess([file]): Returns the project root for the given file (or for the current file if none is given).\r\n  * ProjectRootExe(cmd): Temporarily changes the current directory to that of the project root, then executes the command.\r\n  * ProjectRootCD([file]): Changes the current directory to project root of the given file.\r\n  * ProjectRootBuffers([file]): Returns all buffers belonging to the same project of the given file.\r\n\r\nFor example, to automatically change the current directory to the projectroot of the current file you could add this to your .vimrc:\r\n\r\nau BufEnter * if &ft != 'help' | call ProjectRootCD() | endif\r\n","4":"Github project: https:\/\/github.com\/dbakker\/vim-projectroot\r\n\r\nThere already are a ton of plugins (such as CtrlP) that try to guess what the main project folder is of a file that you're working on, but this plugin allows to easily re-use that functionality in your own custom mappings or scripts.\r\n\r\nFeatures:\r\n  * Works out-of-the-box on most projects by detecting folders such as .git.\r\n  * Very customizeable.\r\n  * Easy to use in mappings and your own scripts, just call ProjectRootGuess() to get the project root of the current file or ProjectRootGuess(file) for another file.\r\n  * Can be combined with existing plugins\r\n  * Tries to be as lightweight as possible. Only searches for a project root when a method such as ProjectRootGuess is used.\r\n\r\nMethods provided:\r\n  * ProjectRootGuess([file]): Returns the project root for the given file (or for the current file if none is given).\r\n  * ProjectRootExe(cmd): Temporarily changes the current directory to that of the project root, then executes the command.\r\n  * ProjectRootCD([file]): Changes the current directory to project root of the given file.\r\n  * ProjectRootBuffers([file]): Returns all buffers belonging to the same project of the given file.\r\n\r\nFor example, to automatically change the current directory to the projectroot of the current file you could add this to your .vimrc:\r\n\r\nau BufEnter * if &ft != 'help' | call ProjectRootCD() | endif\r\n","install_details":"My recommended way of installing this plugin would be by using Vundle or Pathogen, and pointing them at https:\/\/github.com\/dbakker\/vim-projectroot .\r\n\r\nTo manually install the plugin just download projectroot.zip and put projectroot.vim in your plugin\/ folder. However, if you are contemplating to use this you're probably advanced enough to know this yourself. :)","5":"My recommended way of installing this plugin would be by using Vundle or Pathogen, and pointing them at https:\/\/github.com\/dbakker\/vim-projectroot .\r\n\r\nTo manually install the plugin just download projectroot.zip and put projectroot.vim in your plugin\/ folder. However, if you are contemplating to use this you're probably advanced enough to know this yourself. :)","first_name":"Daan","6":"Daan","last_name":"Bakker","7":"Bakker","releases":[{"0":"4387","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"projectroot.zip","4":"projectroot.zip","src_id":"19322","5":"19322","creation_date":"1357502374","6":"1357502374"}]},"4386":{"script_id":"4386","0":"4386","script_name":"Smartgf","1":"Smartgf","script_type":"utility","2":"utility","summary":"'goto file' on steroids!","3":"'goto file' on steroids!","description":"About\r\n-----\r\n**smartgf** is a 'goto file' on steroids!\r\n\r\nIt's better than default gf because:\r\n\r\n* It doesn't use ctags. So you don't need to run anything after changes.\r\n* It shows you all available matches.\r\n\r\nIt's better than ack.vim because:\r\n\r\n* It sets top priority for function\/method\/class\/module definition.\r\n* It uses filter by filetype by default.\r\n* It skips comments in the search.\r\n* You don't need to switch or use quickfix window. It works in command-line mode.\r\n\r\n![smartgf.vim](https:\/\/github.com\/gorkunov\/smartgf.vim\/raw\/master\/_assets\/smartgf.png)\r\n \r\nWatch [this screencast](https:\/\/vimeo.com\/56636037) for more details.\r\n\r\nInstallation\r\n------------\r\nFirst of all you need to have installed [ack](http:\/\/betterthangrep.com\/). So run this:\r\n\r\n    # on ubuntu\r\n    sudo apt-get install ack-grep\r\n\r\n    # on mac with homebrew\r\n    brew install ack\r\n\r\nOr see details instruction [here](https:\/\/github.com\/mileszs\/ack.vim).\r\n\r\nFor quick plugin installing use [pathogen.vim](https:\/\/github.com\/tpope\/vim-pathogen).\r\n\r\nIf you already have pathogen then put smartgf into ~\/.vim\/bundle like this:\r\n\r\n    cd ~\/.vim\/bundle\r\n    git clone https:\/\/github.com\/gorkunov\/smartgf.vim.git\r\n\r\nUsage\r\n-----\r\nSmartgf uses default 'gf' combination. Set cursor position under the function \r\nor method and type gf in normal mode. After that you will see dialog with search results. \r\nUse 1-9 keys as quick shortcuts to select search result or use j,k to change cursor \r\nposition in the dialog and o,Enter to choose selected item.\r\n\r\n*Note: By default smartgf uses filter by filetype and sets top priority for method definitions \r\nand also skips comments in the search results. If you want to skip those filters use 'gF' instead of 'gf'.*\r\n\r\n*Note: If you use rails.vim you should know that smartgf disable rails.vim 'gf' mappings.\r\nYou can change smartgf mappings (see configuration section) after that rails.vim should works in a normal way.*\r\n\r\nConfiguration\r\n-------------\r\nIf you want to change default smartgf settings add those lines to your vimrc file.\r\n\r\nAvailable settings for smartgf:\r\n\r\n```viml\r\n\"Key for running smartpaigf with all filters (ft\/comments\/def)\r\n\"default is 'gf'\r\nlet g:smartgf_key = 'gf'\r\n\r\n\"Key for running smartpaigf without filters\r\n\"default is 'gF'\r\nlet g:smartgf_no_filter_key = 'gF'\r\n\r\n\"Max entries count to display (search results dialog)\r\n\"default is 9\r\nlet g:smartgf_max_entries_per_page = 9\r\n\r\n\"Min space between text and file path in the search results list\r\n\"default is 5\r\nlet g:smartgf_divider_width = 5\r\n```\r\n\r\nLicense\r\n-------\r\nSmartgf is released under the [wtfpl](http:\/\/sam.zoy.org\/wtfpl\/COPYING)\r\n","4":"About\r\n-----\r\n**smartgf** is a 'goto file' on steroids!\r\n\r\nIt's better than default gf because:\r\n\r\n* It doesn't use ctags. So you don't need to run anything after changes.\r\n* It shows you all available matches.\r\n\r\nIt's better than ack.vim because:\r\n\r\n* It sets top priority for function\/method\/class\/module definition.\r\n* It uses filter by filetype by default.\r\n* It skips comments in the search.\r\n* You don't need to switch or use quickfix window. It works in command-line mode.\r\n\r\n![smartgf.vim](https:\/\/github.com\/gorkunov\/smartgf.vim\/raw\/master\/_assets\/smartgf.png)\r\n \r\nWatch [this screencast](https:\/\/vimeo.com\/56636037) for more details.\r\n\r\nInstallation\r\n------------\r\nFirst of all you need to have installed [ack](http:\/\/betterthangrep.com\/). So run this:\r\n\r\n    # on ubuntu\r\n    sudo apt-get install ack-grep\r\n\r\n    # on mac with homebrew\r\n    brew install ack\r\n\r\nOr see details instruction [here](https:\/\/github.com\/mileszs\/ack.vim).\r\n\r\nFor quick plugin installing use [pathogen.vim](https:\/\/github.com\/tpope\/vim-pathogen).\r\n\r\nIf you already have pathogen then put smartgf into ~\/.vim\/bundle like this:\r\n\r\n    cd ~\/.vim\/bundle\r\n    git clone https:\/\/github.com\/gorkunov\/smartgf.vim.git\r\n\r\nUsage\r\n-----\r\nSmartgf uses default 'gf' combination. Set cursor position under the function \r\nor method and type gf in normal mode. After that you will see dialog with search results. \r\nUse 1-9 keys as quick shortcuts to select search result or use j,k to change cursor \r\nposition in the dialog and o,Enter to choose selected item.\r\n\r\n*Note: By default smartgf uses filter by filetype and sets top priority for method definitions \r\nand also skips comments in the search results. If you want to skip those filters use 'gF' instead of 'gf'.*\r\n\r\n*Note: If you use rails.vim you should know that smartgf disable rails.vim 'gf' mappings.\r\nYou can change smartgf mappings (see configuration section) after that rails.vim should works in a normal way.*\r\n\r\nConfiguration\r\n-------------\r\nIf you want to change default smartgf settings add those lines to your vimrc file.\r\n\r\nAvailable settings for smartgf:\r\n\r\n```viml\r\n\"Key for running smartpaigf with all filters (ft\/comments\/def)\r\n\"default is 'gf'\r\nlet g:smartgf_key = 'gf'\r\n\r\n\"Key for running smartpaigf without filters\r\n\"default is 'gF'\r\nlet g:smartgf_no_filter_key = 'gF'\r\n\r\n\"Max entries count to display (search results dialog)\r\n\"default is 9\r\nlet g:smartgf_max_entries_per_page = 9\r\n\r\n\"Min space between text and file path in the search results list\r\n\"default is 5\r\nlet g:smartgf_divider_width = 5\r\n```\r\n\r\nLicense\r\n-------\r\nSmartgf is released under the [wtfpl](http:\/\/sam.zoy.org\/wtfpl\/COPYING)\r\n","install_details":"","5":"","first_name":"Alexander","6":"Alexander","last_name":"Gorkunov","7":"Gorkunov","releases":[{"0":"4386","vim_version":"7.0","1":"7.0","script_version":"1.0.2","2":"1.0.2","version_comment":"Fix navigation keys in readme\/legend","3":"Fix navigation keys in readme\/legend","package":"smartgf.zip","4":"smartgf.zip","src_id":"19319","5":"19319","creation_date":"1357486032","6":"1357486032"},{"0":"4386","vim_version":"7.0","1":"7.0","script_version":"1.0.1","2":"1.0.1","version_comment":"Fix docs https:\/\/github.com\/gorkunov\/smartgf.vim\/issues\/1","3":"Fix docs https:\/\/github.com\/gorkunov\/smartgf.vim\/issues\/1","package":"smartgf.zip","4":"smartgf.zip","src_id":"19318","5":"19318","creation_date":"1357476077","6":"1357476077"},{"0":"4386","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"smartgf.zip","4":"smartgf.zip","src_id":"19316","5":"19316","creation_date":"1357388737","6":"1357388737"}]},"4385":{"script_id":"4385","0":"4385","script_name":"Bufstop","1":"Bufstop","script_type":"utility","2":"utility","summary":"Fast and efficient buffer switching for Vim","3":"Fast and efficient buffer switching for Vim","description":"If you find yourself frequently switching back and forth between files, and looking for a faster way to do it, well, your journey has come to an end. Welcome to the Bufstop! \r\n\r\nBufstop is a plugin for faster buffer switching, built for efficiency and less keystrokes. It provides no less than 6 ways to display and switch buffers. \r\n\r\nCheck out the git repository for a detailed description: https:\/\/github.com\/mihaifm\/bufstop ","4":"If you find yourself frequently switching back and forth between files, and looking for a faster way to do it, well, your journey has come to an end. Welcome to the Bufstop! \r\n\r\nBufstop is a plugin for faster buffer switching, built for efficiency and less keystrokes. It provides no less than 6 ways to display and switch buffers. \r\n\r\nCheck out the git repository for a detailed description: https:\/\/github.com\/mihaifm\/bufstop ","install_details":"Copy the file in the plugin directory.","5":"Copy the file in the plugin directory.","first_name":"Mihai","6":"Mihai","last_name":"Ciuraru","7":"Ciuraru","releases":[{"0":"4385","vim_version":"7.0","1":"7.0","script_version":"1.6","2":"1.6","version_comment":"New features added, check the documentation and the git repository for more details.\r\n","3":"New features added, check the documentation and the git repository for more details.\r\n","package":"bufstop.zip","4":"bufstop.zip","src_id":"27686","5":"27686","creation_date":"1627614878","6":"1627614878"},{"0":"4385","vim_version":"7.0","1":"7.0","script_version":"1.4","2":"1.4","version_comment":"Multiple fixes and a new option to sort the buffers by most frequently used.","3":"Multiple fixes and a new option to sort the buffers by most frequently used.","package":"bufstop.vim","4":"bufstop.vim","src_id":"21995","5":"21995","creation_date":"1402142865","6":"1402142865"},{"0":"4385","vim_version":"7.0","1":"7.0","script_version":"1.3","2":"1.3","version_comment":"Reworked the way buffers are displayed in the command line with BufstopMode","3":"Reworked the way buffers are displayed in the command line with BufstopMode","package":"bufstop.vim","4":"bufstop.vim","src_id":"21836","5":"21836","creation_date":"1398543265","6":"1398543265"},{"0":"4385","vim_version":"7.0","1":"7.0","script_version":"1.2","2":"1.2","version_comment":"Major rework, new features added. Check out the github repo or the documentation for the new functionality.","3":"Major rework, new features added. Check out the github repo or the documentation for the new functionality.","package":"bufstop.vim","4":"bufstop.vim","src_id":"19358","5":"19358","creation_date":"1358029678","6":"1358029678"},{"0":"4385","vim_version":"7.0","1":"7.0","script_version":"1.1","2":"1.1","version_comment":"Some fixes","3":"Some fixes","package":"bufstop.vim","4":"bufstop.vim","src_id":"19332","5":"19332","creation_date":"1357687138","6":"1357687138"},{"0":"4385","vim_version":"7.3","1":"7.3","script_version":"1.1","2":"1.1","version_comment":"Initial upload","3":"Initial upload","package":"bufstop.vim","4":"bufstop.vim","src_id":"19311","5":"19311","creation_date":"1357348971","6":"1357348971"}]},"4384":{"script_id":"4384","0":"4384","script_name":"File Pirate","1":"File Pirate","script_type":"utility","2":"utility","summary":"A very fast file picker plug-in","3":"A very fast file picker plug-in","description":"File Pirate is a fuzzy file picker plug-in for Vim, in the tradition of Textmate GoToFile and the Cmd-T plug-in. Its key differentiating feature is that it is very fast, even for large repositories (expect real-time response for a directory of 50 000 files).\r\n\r\nIt requires Vim with Python support, the ability to compile native code, and a Mac or Linux system. Windows support is planned.\r\n\r\nAll key mappings are easily customisable.\r\n\r\nMore information and a screenshot: http:\/\/code.lardcave.net\/entries\/2012\/12\/27\/234103\/\r\n\r\nDetailed documentation, installation instructions, and download links: https:\/\/github.com\/nfd\/filepirate","4":"File Pirate is a fuzzy file picker plug-in for Vim, in the tradition of Textmate GoToFile and the Cmd-T plug-in. Its key differentiating feature is that it is very fast, even for large repositories (expect real-time response for a directory of 50 000 files).\r\n\r\nIt requires Vim with Python support, the ability to compile native code, and a Mac or Linux system. Windows support is planned.\r\n\r\nAll key mappings are easily customisable.\r\n\r\nMore information and a screenshot: http:\/\/code.lardcave.net\/entries\/2012\/12\/27\/234103\/\r\n\r\nDetailed documentation, installation instructions, and download links: https:\/\/github.com\/nfd\/filepirate","install_details":"1. Install Pathogen (or add ~\/.vim\/bundle\/filepirate to your plugin path some other way)\r\n2. Extract to ~\/.vim\/bundle\r\n3. cd ~\/.vim\/bundle\/filepirate\/plugin and type \"make\"\r\n","5":"1. Install Pathogen (or add ~\/.vim\/bundle\/filepirate to your plugin path some other way)\r\n2. Extract to ~\/.vim\/bundle\r\n3. cd ~\/.vim\/bundle\/filepirate\/plugin and type \"make\"\r\n","first_name":"Nicholas","6":"Nicholas","last_name":"FitzRoy-Dale","7":"FitzRoy-Dale","releases":[{"0":"4384","vim_version":"7.0","1":"7.0","script_version":"0.1.1","2":"0.1.1","version_comment":"Bug fixes: Window size restoration, directory scanning.","3":"Bug fixes: Window size restoration, directory scanning.","package":"filepirate-0.1.1.tar.gz","4":"filepirate-0.1.1.tar.gz","src_id":"19357","5":"19357","creation_date":"1358029164","6":"1358029164"},{"0":"4384","vim_version":"7.0","1":"7.0","script_version":"0.1.0","2":"0.1.0","version_comment":"Initial upload","3":"Initial upload","package":"filepirate-0.1.0.tar.gz","4":"filepirate-0.1.0.tar.gz","src_id":"19307","5":"19307","creation_date":"1357249706","6":"1357249706"}]},"4383":{"script_id":"4383","0":"4383","script_name":"configurationUtility.vim","1":"configurationUtility.vim","script_type":"indent","2":"indent","summary":"Save and load configuration files in a dictionary format with sections and items","3":"Save and load configuration files in a dictionary format with sections and items","description":"See latest version on github: https:\/\/github.com\/viaa\/VimPlugins\r\n\r\nName: configurationUtility.vim\r\nVersion: 1.0\r\nAuthor: Alexandre Viau (alexandreviau@gmail.com)\r\n\r\nNOTE: The configurationUtility.vim plugin is fully functional as it is, but I will not continue its development because I now use and develop the basicXmlParser.vim plugin to load and save data to configuration files. One advantage of the basicXmlParser plugin is that it offers unlimited levels of subitems of data but the configurationUtility offers only 2, but in many case for configuration files, 2 levels are enough. Here is the link to the basicXmlParser plugin http:\/\/www.vim.org\/scripts\/script.php?script_id=4380\r\n\r\nDescription: Save and load configuration files in a dictionary format containing sections and items. I wanted to have a way to save and load configuration data with items and sections like .ini files on Windows, and I found that it could be possible using dictionaries.\r\nThe functions in this plugin are used to create and load a file like this which contains a large dictionary that contains items and one level of subitems called sections.\r\n\r\nHere are the available functions:\r\ng:CfgLoadFromFile(file) \r\ng:CfgSaveToFile(cfg, file) \r\ng:CfgGetItem(dict, itemKey) \r\ng:CfgGetItemKey(dict, itemValue) \r\ng:CfgRemoveItem(dict, itemKey) \r\ng:CfgSetItem(dict, itemKey, itemValue) \r\ng:CfgGetSection(dict, sectionKey) \r\ng:CfgSetSection(dict, sectionKey, sectionvalue) \r\ng:CfgSectionRemove(dict, sectionKey) \r\ng:CfgSectionGetItem(dict, sectionKey, itemKey) \r\ng:CfgSectionGetItemKey(dict, itemValue) \r\ng:CfgSectionRemoveItem(dict, sectionKey, itemKey) \r\ng:CfgSectionSetItem(dict, sectionKey, itemKey, itemValue) \r\ng:CfgSectionExists(dict, sectionKey) \r\n\r\nThe sections themselves contains items. So at the first level there are items and sections, and in the sections there are items only.\r\nFor example here items would be 'history', 'favorites', 'lastPath'. The sections would be for example 'selectedFiles', 'marks', and items in the sections in this example would be 'B', 'C', etc...  \r\nlet g:Cfg = {'selectedFiles': {}\r\n\\, 'marks': {'A': 'C:\\Usb\\i_green\\apps'\r\n\\, 'B': 'C:\\Users\\User\\Desktop'\r\n\\, 'C': 'C:\\'\r\n\\, 'D': 'C:\\Usb\\i_green\\data'\r\n\\, 'F': 'C:\/Windows\/Microsoft.NET\/Framework64\/v4.0.30319'\r\n\\, 'G': 'G:\\'\r\n\\, 'H': 'C:\\Users'\r\n\\, '2': 'C:\/Usb\/iomega\/Video'\r\n\\, 'M': 'C:\\ProgramData\\Microsoft\\Windows\\Start Menu\\Programs'\r\n\\, 'P': 'C:\\vim\\vim73\\plugin'\r\n\\, 'S': 'C:\\Users\\User\\Documents\\Shortcuts'\r\n\\, 'T': 'C:\\Temp'\r\n\\, 'U': 'C:\\Usb'\r\n\\, 'V': 'C:\\vim\\vim73'\r\n\\, 'W': 'C:\/Usb\/z_white'\r\n\\, '3': 'C:\/Temp\/a1'\r\n\\, 'a': 'C:\\Usb\\z_white\\Apps\\Portable'\r\n\\, 'b': 'C:\\Users\\User\\Desktop'\r\n\\, 'c': 'C:\\Usb\\z_white\\Apps\\Portable\\CmdUtils'\r\n\\, 'd': 'C:\\Users\\User\\Documents'\r\n\\, 'e': 'C:\/Users\/User\/Documents\/emails'\r\n\\, 'f': 'C:\/Windows\/Microsoft.NET\/Framework64\/v4.0.30319'\r\n\\, 'g': 'G:\\'\r\n\\, 'h': 'C:\\Users\\User'\r\n\\, 'i': 'C:\\Usb\\i_green'\r\n\\, 'm': 'C:\/Users\/User\/AppData\/Roaming\/Microsoft\/Windows\/Start Menu\/Programs'\r\n\\, 'n': 'C:\/Usb\/i_green\/data\/Notes'\r\n\\, 'p': 'C:\\Usb\\i_green\\data\\Projects'\r\n\\, 'r': 'C:\\repository'\r\n\\, 's': 'C:\\Users\\User\\Documents\\Shortcuts'\r\n\\, 't': 'C:\\Temp'\r\n\\, 'u': 'C:\\Usb'\r\n\\, 'v': 'C:\\vim\\vim73'\r\n\\, 'w': 'C:\\Windows'\r\n\\, '8': 'C:\/HP'\r\n\\, '9': 'C:\/HP\/support'\r\n\\, 'z': 'C:\/Windows\/Logs'}\r\n\\, 'history': '[C:\/Usb\/z_white\/Data\/] [C:\/Usb\/z_white\/Data\/] [C:\/Temp\/allo] [C:\/Temp\/allo\/a5\/zzz\/wwwwwwww]'\r\n\\, 'favorites': '[C:\/cygwin] [C:\/cygwin\/usr\/share\/vim\/vim73]'\r\n\\, 'cursorPos': {'C:\/Temp\/a1': '..'\r\n\\, 'C:\/Temp\/a2': 'bclear.vim'\r\n\\, 'C:\/Temp\/a3': '.'\r\n\\, 'C:\/Temp\/a5': '..'\r\n\\, 'C:\/ProgramData\/Microsoft\/Windows\/Start Menu\/Programs\/Security and Protection': '..'\r\n\\, 'C:\/Usb\/iomega\/Documents\/Emails': 'John_bak.dbx'\r\n\\, 'C:\/Usb\/iomega\/Documents\/Orthodox (faire menage)\/Early Church Fathers v.2.0': 'ecf02.hlp'}\r\n\\, 'lastPath': 'C:\/Usb\/'}\r\n","4":"See latest version on github: https:\/\/github.com\/viaa\/VimPlugins\r\n\r\nName: configurationUtility.vim\r\nVersion: 1.0\r\nAuthor: Alexandre Viau (alexandreviau@gmail.com)\r\n\r\nNOTE: The configurationUtility.vim plugin is fully functional as it is, but I will not continue its development because I now use and develop the basicXmlParser.vim plugin to load and save data to configuration files. One advantage of the basicXmlParser plugin is that it offers unlimited levels of subitems of data but the configurationUtility offers only 2, but in many case for configuration files, 2 levels are enough. Here is the link to the basicXmlParser plugin http:\/\/www.vim.org\/scripts\/script.php?script_id=4380\r\n\r\nDescription: Save and load configuration files in a dictionary format containing sections and items. I wanted to have a way to save and load configuration data with items and sections like .ini files on Windows, and I found that it could be possible using dictionaries.\r\nThe functions in this plugin are used to create and load a file like this which contains a large dictionary that contains items and one level of subitems called sections.\r\n\r\nHere are the available functions:\r\ng:CfgLoadFromFile(file) \r\ng:CfgSaveToFile(cfg, file) \r\ng:CfgGetItem(dict, itemKey) \r\ng:CfgGetItemKey(dict, itemValue) \r\ng:CfgRemoveItem(dict, itemKey) \r\ng:CfgSetItem(dict, itemKey, itemValue) \r\ng:CfgGetSection(dict, sectionKey) \r\ng:CfgSetSection(dict, sectionKey, sectionvalue) \r\ng:CfgSectionRemove(dict, sectionKey) \r\ng:CfgSectionGetItem(dict, sectionKey, itemKey) \r\ng:CfgSectionGetItemKey(dict, itemValue) \r\ng:CfgSectionRemoveItem(dict, sectionKey, itemKey) \r\ng:CfgSectionSetItem(dict, sectionKey, itemKey, itemValue) \r\ng:CfgSectionExists(dict, sectionKey) \r\n\r\nThe sections themselves contains items. So at the first level there are items and sections, and in the sections there are items only.\r\nFor example here items would be 'history', 'favorites', 'lastPath'. The sections would be for example 'selectedFiles', 'marks', and items in the sections in this example would be 'B', 'C', etc...  \r\nlet g:Cfg = {'selectedFiles': {}\r\n\\, 'marks': {'A': 'C:\\Usb\\i_green\\apps'\r\n\\, 'B': 'C:\\Users\\User\\Desktop'\r\n\\, 'C': 'C:\\'\r\n\\, 'D': 'C:\\Usb\\i_green\\data'\r\n\\, 'F': 'C:\/Windows\/Microsoft.NET\/Framework64\/v4.0.30319'\r\n\\, 'G': 'G:\\'\r\n\\, 'H': 'C:\\Users'\r\n\\, '2': 'C:\/Usb\/iomega\/Video'\r\n\\, 'M': 'C:\\ProgramData\\Microsoft\\Windows\\Start Menu\\Programs'\r\n\\, 'P': 'C:\\vim\\vim73\\plugin'\r\n\\, 'S': 'C:\\Users\\User\\Documents\\Shortcuts'\r\n\\, 'T': 'C:\\Temp'\r\n\\, 'U': 'C:\\Usb'\r\n\\, 'V': 'C:\\vim\\vim73'\r\n\\, 'W': 'C:\/Usb\/z_white'\r\n\\, '3': 'C:\/Temp\/a1'\r\n\\, 'a': 'C:\\Usb\\z_white\\Apps\\Portable'\r\n\\, 'b': 'C:\\Users\\User\\Desktop'\r\n\\, 'c': 'C:\\Usb\\z_white\\Apps\\Portable\\CmdUtils'\r\n\\, 'd': 'C:\\Users\\User\\Documents'\r\n\\, 'e': 'C:\/Users\/User\/Documents\/emails'\r\n\\, 'f': 'C:\/Windows\/Microsoft.NET\/Framework64\/v4.0.30319'\r\n\\, 'g': 'G:\\'\r\n\\, 'h': 'C:\\Users\\User'\r\n\\, 'i': 'C:\\Usb\\i_green'\r\n\\, 'm': 'C:\/Users\/User\/AppData\/Roaming\/Microsoft\/Windows\/Start Menu\/Programs'\r\n\\, 'n': 'C:\/Usb\/i_green\/data\/Notes'\r\n\\, 'p': 'C:\\Usb\\i_green\\data\\Projects'\r\n\\, 'r': 'C:\\repository'\r\n\\, 's': 'C:\\Users\\User\\Documents\\Shortcuts'\r\n\\, 't': 'C:\\Temp'\r\n\\, 'u': 'C:\\Usb'\r\n\\, 'v': 'C:\\vim\\vim73'\r\n\\, 'w': 'C:\\Windows'\r\n\\, '8': 'C:\/HP'\r\n\\, '9': 'C:\/HP\/support'\r\n\\, 'z': 'C:\/Windows\/Logs'}\r\n\\, 'history': '[C:\/Usb\/z_white\/Data\/] [C:\/Usb\/z_white\/Data\/] [C:\/Temp\/allo] [C:\/Temp\/allo\/a5\/zzz\/wwwwwwww]'\r\n\\, 'favorites': '[C:\/cygwin] [C:\/cygwin\/usr\/share\/vim\/vim73]'\r\n\\, 'cursorPos': {'C:\/Temp\/a1': '..'\r\n\\, 'C:\/Temp\/a2': 'bclear.vim'\r\n\\, 'C:\/Temp\/a3': '.'\r\n\\, 'C:\/Temp\/a5': '..'\r\n\\, 'C:\/ProgramData\/Microsoft\/Windows\/Start Menu\/Programs\/Security and Protection': '..'\r\n\\, 'C:\/Usb\/iomega\/Documents\/Emails': 'John_bak.dbx'\r\n\\, 'C:\/Usb\/iomega\/Documents\/Orthodox (faire menage)\/Early Church Fathers v.2.0': 'ecf02.hlp'}\r\n\\, 'lastPath': 'C:\/Usb\/'}\r\n","install_details":"Copy the plugin to the vim plugin directory.","5":"Copy the plugin to the vim plugin directory.","first_name":"Alexandre","6":"Alexandre","last_name":"Viau","7":"Viau","releases":[{"0":"4383","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"configurationUtility.vim","4":"configurationUtility.vim","src_id":"19305","5":"19305","creation_date":"1357215158","6":"1357215158"}]},"4382":{"script_id":"4382","0":"4382","script_name":"asm2d-vim","1":"asm2d-vim","script_type":"syntax","2":"syntax","summary":"Vim plugin for the asm2d assembly language","3":"Vim plugin for the asm2d assembly language","description":"asm2d-vim is a lightweight Vim plugin to add syntax highlighting to assembly files for the asm2d (http:\/\/tapichu.github.com\/asm2d\/) assembler.\r\n\r\nIt also adds syntax highlighting to MIF (http:\/\/quartushelp.altera.com\/9.1\/mergedProjects\/reference\/glossary\/def_mif.htm) files, and it configures the program used by the :make command.\r\n\r\nThe most recent version can be found on github: http:\/\/tapichu.github.com\/asm2d-vim\/","4":"asm2d-vim is a lightweight Vim plugin to add syntax highlighting to assembly files for the asm2d (http:\/\/tapichu.github.com\/asm2d\/) assembler.\r\n\r\nIt also adds syntax highlighting to MIF (http:\/\/quartushelp.altera.com\/9.1\/mergedProjects\/reference\/glossary\/def_mif.htm) files, and it configures the program used by the :make command.\r\n\r\nThe most recent version can be found on github: http:\/\/tapichu.github.com\/asm2d-vim\/","install_details":"http:\/\/tapichu.github.com\/asm2d-vim\/","5":"http:\/\/tapichu.github.com\/asm2d-vim\/","first_name":"Eduardo","6":"Eduardo","last_name":"Lopez","7":"Lopez","releases":[{"0":"4382","vim_version":"7.3","1":"7.3","script_version":"0.1.2","2":"0.1.2","version_comment":"* Syntax for new instructions.\r\n* Mark lines with errors or warnings.\r\n* Quickfix window improvements (type of error, line numbers).\r\n* Setting to decide if quickfix window should be opened for warnings.","3":"* Syntax for new instructions.\r\n* Mark lines with errors or warnings.\r\n* Quickfix window improvements (type of error, line numbers).\r\n* Setting to decide if quickfix window should be opened for warnings.","package":"asm2d-vim-v0.1.2.zip","4":"asm2d-vim-v0.1.2.zip","src_id":"19333","5":"19333","creation_date":"1357709826","6":"1357709826"},{"0":"4382","vim_version":"7.3","1":"7.3","script_version":"0.1.1","2":"0.1.1","version_comment":"* Keywords for stack and keypress event instructions.\r\n* Character constants in syntax.\r\n","3":"* Keywords for stack and keypress event instructions.\r\n* Character constants in syntax.\r\n","package":"asm2d-vim-v0.1.1.zip","4":"asm2d-vim-v0.1.1.zip","src_id":"19312","5":"19312","creation_date":"1357353619","6":"1357353619"},{"0":"4382","vim_version":"7.3","1":"7.3","script_version":"0.1.0","2":"0.1.0","version_comment":"* Compilation errors in quickfix window.\r\n* Continue comments on the next line.\r\n* Highlight TODO and FIXME notes in comments.\r\n* Fix error with syntax priority.","3":"* Compilation errors in quickfix window.\r\n* Continue comments on the next line.\r\n* Highlight TODO and FIXME notes in comments.\r\n* Fix error with syntax priority.","package":"asm2d-vim-v0.1.0.zip","4":"asm2d-vim-v0.1.0.zip","src_id":"19310","5":"19310","creation_date":"1357290928","6":"1357290928"},{"0":"4382","vim_version":"7.3","1":"7.3","script_version":"0.0.3","2":"0.0.3","version_comment":"* Add arithmetic operators to syntax.\r\n* Compile the assembly code when opening the MIF file.\r\n* Configure extra parameters to the ':make' command.","3":"* Add arithmetic operators to syntax.\r\n* Compile the assembly code when opening the MIF file.\r\n* Configure extra parameters to the ':make' command.","package":"asm2d-vim-v0.0.3.zip","4":"asm2d-vim-v0.0.3.zip","src_id":"19306","5":"19306","creation_date":"1357245367","6":"1357245367"},{"0":"4382","vim_version":"7.3","1":"7.3","script_version":"0.0.2","2":"0.0.2","version_comment":"Initial upload","3":"Initial upload","package":"asm2d-vim-v0.0.2.zip","4":"asm2d-vim-v0.0.2.zip","src_id":"19302","5":"19302","creation_date":"1357194066","6":"1357194066"}]},"4381":{"script_id":"4381","0":"4381","script_name":"RepeatLast.vim","1":"RepeatLast.vim","script_type":"utility","2":"utility","summary":"Provides [count]\\. to repeat the last group of actions you performed.","3":"Provides [count]\\. to repeat the last group of actions you performed.","description":"RepeatLast.vim by joeytwiddle\r\n\r\nProvides <count>\\. to repeat the last group of actions you performed.\r\n\r\n                \"A beautiful monster\" -- bairui in #vim\r\n\r\nThe '.' key is fantastic for repeating the last 1 action you made.  But\r\nsometimes I do three actions, and then want to repeat them again.  Now\r\nthis is just 3\\.\r\n\r\nBEWARE: Because it uses macro recording *all the time*, it sort of takes\r\nover your Vim, and can impact your usual experience.  Be prepared!\r\n\r\n  :set ch=2       if the word \"recording\" hides messages you wanted\r\n\r\n  :let g:RepeatLast_TriggerCursorHold = 1  or  0   for GUI fixes\r\n\r\nAlso: :RepeatLastDisable :RepeatLastEnable :RepeatLastToggleDebugging\r\n\r\n\r\n\r\n== Usage ==\r\n\r\nAssuming your mapleader is '\\' (the default), these |mappings| are created:\r\n\r\n  \\?   Display a list of recently recorded actions\r\n\r\n  4\\?  Display the last four recorded actions\r\n\r\n  \\.   Repeat the last action (similar to . but may replay just a movement)\r\n\r\n  4\\.  Repeat the last four recorded actions (including movement actions)\r\n\r\n  \\\\.  Replay the last *repeated* action-group (all 4 actions above)\r\n\r\n  9\\\\. Replay the last *repeated* action-group 9 times (producing 9 times 4)\r\n\r\n  \\D   Forget (drop) the last action (e.g. to discard an unwanted movement)\r\n\r\n  3\\D  Drop the last 3 recorded actions (useful to get back to earlier state)\r\n\r\n  \\|  or  \\#\r\n\r\n       Temporarily enable\/disable recording for the next few actions\r\n\r\n       (Allows free movement without adding new actions to history)\r\n\r\n  4\\G  Grab the last 4 actions and store in register 'g'\r\n\r\n  @g   Repeat the actions stored in register 'g'\r\n\r\n  :let @i=@g\r\n\r\n       Copy the actions to register 'i', so 'g' may be overwritten.\r\n\r\n  :let g:RepeatLast_SaveToRegister = 'p'\r\n\r\n       Always save any repeated action-group into @p\r\n\r\n  :let g:RepeatLast_TriggerCursorHold = 0\r\n\r\n       Disable the UI fix.  CursorHold events will not fire.\r\n\r\nCommands are also available for the main shortcuts above:\r\n\r\n  :ShowRecent   :RepeatLast   :DropLast   :PauseRecording   :GrabLast\r\n\r\nCommands to toggle state at runtime:\r\n\r\n  :RepeatLastEnable    Enables action recording, enters macro record mode.\r\n\r\n  :RepeatLastDisable   Disables action recording, leaves macro record mode.\r\n\r\n  :RepeatLast<Ctrl-D>  or  <Tab>      More commands, some toggle info.\r\n\r\nNew feature - Auto Ignoring:\r\n\r\n  After executing a repeat action, action storage will be *temporarily\r\n  disabled* for the number of actions specified by:\r\n\r\n    let g:RepeatLast_Ignore_After_Use_For = 10\r\n\r\n  This allows you to move to a new location between executing repeats,\r\n  without recording those movement actions.\r\n\r\n  Once you have performed enough actions without executing a repeat, action\r\n  storage will be re-enabled, and the ignored actions will be added to the\r\n  history as one large entry.  Although g:RepeatLast_Stop_Ignoring_On_Edit\r\n  prevents this recovery.\r\n\r\nReading this rest of this file:\r\n\r\n  You may like to try  :FoldNicely\r\n\r\n\r\n\r\n== Limitations ==\r\n\r\nIt uses macro recording ALL THE TIME.  The word \"recording\" will forever be\r\ndisplayed in your command-line, hiding any messages usually displayed there\r\nby Vim's echo.  To make those hidden messages visible, you will need to:\r\n\r\n  :set cmdheight=2    or more\r\n\r\nBecause recording is enabled, for commands like `q:` and `q\/` you will need\r\nto press an extra `q` beforehand, and they will not be recorded in history.\r\n\r\nIf you want to record your own macro, you can disable the plugin with\r\n:RepeatLastDisable (or you could try just pressing 'q' for a one-time disable).\r\n\r\nCursorHold events do not fire in macro-recording mode.  Any visual tools,\r\ntaglist updates, etc. that require CursorHold *will not be triggered*.\r\nOther events such as CursorMove, InsertLeave, BufWritePost work fine.\r\nThe new option RepeatLast_TriggerCursorHold can now be used to force trigger\r\nof CursorHold events.  It may not be ideal, but mostly works ok.\r\n\r\n== Disadvantages ==\r\n\r\nMovements j and k will not return to the original column after passing\r\nthrough shorter lines.  (This is only a problem when using\r\nRepeatLast_TriggerCursorHold.)\r\n\r\nUse of some <Tab>-completion plugins may produce unexpected behaviour when\r\nreplaying actions including a <Tab>-completion.  (Although Vim's built-in\r\n'.' does not suffer from this.)\r\n","4":"RepeatLast.vim by joeytwiddle\r\n\r\nProvides <count>\\. to repeat the last group of actions you performed.\r\n\r\n                \"A beautiful monster\" -- bairui in #vim\r\n\r\nThe '.' key is fantastic for repeating the last 1 action you made.  But\r\nsometimes I do three actions, and then want to repeat them again.  Now\r\nthis is just 3\\.\r\n\r\nBEWARE: Because it uses macro recording *all the time*, it sort of takes\r\nover your Vim, and can impact your usual experience.  Be prepared!\r\n\r\n  :set ch=2       if the word \"recording\" hides messages you wanted\r\n\r\n  :let g:RepeatLast_TriggerCursorHold = 1  or  0   for GUI fixes\r\n\r\nAlso: :RepeatLastDisable :RepeatLastEnable :RepeatLastToggleDebugging\r\n\r\n\r\n\r\n== Usage ==\r\n\r\nAssuming your mapleader is '\\' (the default), these |mappings| are created:\r\n\r\n  \\?   Display a list of recently recorded actions\r\n\r\n  4\\?  Display the last four recorded actions\r\n\r\n  \\.   Repeat the last action (similar to . but may replay just a movement)\r\n\r\n  4\\.  Repeat the last four recorded actions (including movement actions)\r\n\r\n  \\\\.  Replay the last *repeated* action-group (all 4 actions above)\r\n\r\n  9\\\\. Replay the last *repeated* action-group 9 times (producing 9 times 4)\r\n\r\n  \\D   Forget (drop) the last action (e.g. to discard an unwanted movement)\r\n\r\n  3\\D  Drop the last 3 recorded actions (useful to get back to earlier state)\r\n\r\n  \\|  or  \\#\r\n\r\n       Temporarily enable\/disable recording for the next few actions\r\n\r\n       (Allows free movement without adding new actions to history)\r\n\r\n  4\\G  Grab the last 4 actions and store in register 'g'\r\n\r\n  @g   Repeat the actions stored in register 'g'\r\n\r\n  :let @i=@g\r\n\r\n       Copy the actions to register 'i', so 'g' may be overwritten.\r\n\r\n  :let g:RepeatLast_SaveToRegister = 'p'\r\n\r\n       Always save any repeated action-group into @p\r\n\r\n  :let g:RepeatLast_TriggerCursorHold = 0\r\n\r\n       Disable the UI fix.  CursorHold events will not fire.\r\n\r\nCommands are also available for the main shortcuts above:\r\n\r\n  :ShowRecent   :RepeatLast   :DropLast   :PauseRecording   :GrabLast\r\n\r\nCommands to toggle state at runtime:\r\n\r\n  :RepeatLastEnable    Enables action recording, enters macro record mode.\r\n\r\n  :RepeatLastDisable   Disables action recording, leaves macro record mode.\r\n\r\n  :RepeatLast<Ctrl-D>  or  <Tab>      More commands, some toggle info.\r\n\r\nNew feature - Auto Ignoring:\r\n\r\n  After executing a repeat action, action storage will be *temporarily\r\n  disabled* for the number of actions specified by:\r\n\r\n    let g:RepeatLast_Ignore_After_Use_For = 10\r\n\r\n  This allows you to move to a new location between executing repeats,\r\n  without recording those movement actions.\r\n\r\n  Once you have performed enough actions without executing a repeat, action\r\n  storage will be re-enabled, and the ignored actions will be added to the\r\n  history as one large entry.  Although g:RepeatLast_Stop_Ignoring_On_Edit\r\n  prevents this recovery.\r\n\r\nReading this rest of this file:\r\n\r\n  You may like to try  :FoldNicely\r\n\r\n\r\n\r\n== Limitations ==\r\n\r\nIt uses macro recording ALL THE TIME.  The word \"recording\" will forever be\r\ndisplayed in your command-line, hiding any messages usually displayed there\r\nby Vim's echo.  To make those hidden messages visible, you will need to:\r\n\r\n  :set cmdheight=2    or more\r\n\r\nBecause recording is enabled, for commands like `q:` and `q\/` you will need\r\nto press an extra `q` beforehand, and they will not be recorded in history.\r\n\r\nIf you want to record your own macro, you can disable the plugin with\r\n:RepeatLastDisable (or you could try just pressing 'q' for a one-time disable).\r\n\r\nCursorHold events do not fire in macro-recording mode.  Any visual tools,\r\ntaglist updates, etc. that require CursorHold *will not be triggered*.\r\nOther events such as CursorMove, InsertLeave, BufWritePost work fine.\r\nThe new option RepeatLast_TriggerCursorHold can now be used to force trigger\r\nof CursorHold events.  It may not be ideal, but mostly works ok.\r\n\r\n== Disadvantages ==\r\n\r\nMovements j and k will not return to the original column after passing\r\nthrough shorter lines.  (This is only a problem when using\r\nRepeatLast_TriggerCursorHold.)\r\n\r\nUse of some <Tab>-completion plugins may produce unexpected behaviour when\r\nreplaying actions including a <Tab>-completion.  (Although Vim's built-in\r\n'.' does not suffer from this.)\r\n","install_details":"Drop it in plugin\/ folder.\r\n\r\nLatest version at https:\/\/github.com\/joeytwiddle\/RepeatLast.vim","5":"Drop it in plugin\/ folder.\r\n\r\nLatest version at https:\/\/github.com\/joeytwiddle\/RepeatLast.vim","first_name":"joey","6":"joey","last_name":"twiddle","7":"twiddle","releases":[{"0":"4381","vim_version":"7.0","1":"7.0","script_version":"1.34g","2":"1.34g","version_comment":"After \\? (:ShowRecent) the <Enter> or <Space> used on the |hit-enter-prompt| should now be ignored.","3":"After \\? (:ShowRecent) the <Enter> or <Space> used on the |hit-enter-prompt| should now be ignored.","package":"RepeatLast.vim","4":"RepeatLast.vim","src_id":"20540","5":"20540","creation_date":"1374195155","6":"1374195155"},{"0":"4381","vim_version":"7.0","1":"7.0","script_version":"1.34f","2":"1.34f","version_comment":"Various modes for TriggerCursorHold, fairly safe default.  Added choice of clobbered Register, ReRepeat, GrabLast, and many more updates.  Now executing via macro rather than feedkeys, so noautocmd will work again.","3":"Various modes for TriggerCursorHold, fairly safe default.  Added choice of clobbered Register, ReRepeat, GrabLast, and many more updates.  Now executing via macro rather than feedkeys, so noautocmd will work again.","package":"RepeatLast.vim","4":"RepeatLast.vim","src_id":"20513","5":"20513","creation_date":"1373811557","6":"1373811557"},{"0":"4381","vim_version":"7.0","1":"7.0","script_version":"1.34e","2":"1.34e","version_comment":"Removed debugging code which I had accidentally left in","3":"Removed debugging code which I had accidentally left in","package":"RepeatLast.vim","4":"RepeatLast.vim","src_id":"20255","5":"20255","creation_date":"1370087995","6":"1370087995"},{"0":"4381","vim_version":"7.0","1":"7.0","script_version":"1.34d","2":"1.34d","version_comment":"reduced triggering of CursorHold based on user interaction speed, and other modes","3":"reduced triggering of CursorHold based on user interaction speed, and other modes","package":"RepeatLast.vim","4":"RepeatLast.vim","src_id":"20246","5":"20246","creation_date":"1370042203","6":"1370042203"},{"0":"4381","vim_version":"7.0","1":"7.0","script_version":"1.34c","2":"1.34c","version_comment":"Minor updates to documentation.","3":"Minor updates to documentation.","package":"RepeatLast.vim","4":"RepeatLast.vim","src_id":"20079","5":"20079","creation_date":"1368082393","6":"1368082393"},{"0":"4381","vim_version":"7.0","1":"7.0","script_version":"1.34","2":"1.34","version_comment":"Can now trigger CursorHold events, without which some visual plugins may not act normally.","3":"Can now trigger CursorHold events, without which some visual plugins may not act normally.","package":"RepeatLast.vim","4":"RepeatLast.vim","src_id":"19932","5":"19932","creation_date":"1366874441","6":"1366874441"},{"0":"4381","vim_version":"6.0","1":"6.0","script_version":"1","2":"1","version_comment":"Initial upload","3":"Initial upload","package":"RepeatLast.vim","4":"RepeatLast.vim","src_id":"19297","5":"19297","creation_date":"1357152928","6":"1357152928"}]},"4380":{"script_id":"4380","0":"4380","script_name":"basicXmlParser","1":"basicXmlParser","script_type":"utility","2":"utility","summary":"Create object trees and save them as xml, or create trees from xml files.","3":"Create object trees and save them as xml, or create trees from xml files.","description":"See latest version on github: https:\/\/github.com\/viaa\/VimPlugins\r\n\r\nDocumentation \r\n\r\nName: basicXmlParser.vim\r\nVersion: 1.1\r\nDescription: Plugin create object trees and get them or save them as xml, and to create object trees from a xml files. May be used as an object tree, the xml is the file format for load and save the object tree from and to a file. Serialization to xml is optional, the user is not required to load or to save to xml, the tree may be builded manually or programmatically. This plugin was created as a utility plugin to load and save configuration files. See the usage section on how to use the plugin.\r\nAuthor: Alexandre Viau (alexandreviau@gmail.com)\r\nInstallation: Copy the plugin to the vim plugin directory.\r\n\r\nUsage: \r\n\r\nThe following examples create, save to file and load from file the following xml tree: \r\n\r\n<root>\r\n   <Marks>\r\n      <A>\r\n         C:\\Usb\\i_green\\apps\r\n         <myLevel3>\r\n            myLevel3Value\r\n            <myLevel4>\r\n               myLevel4Value\r\n            <\/myLevel4>\r\n         <\/myLevel3>\r\n      <\/A>\r\n      <B>\r\n         C:\\Users\\User\\Desktop\\\r\n      <\/B>\r\n      <C>\r\n         C:\\\r\n      <\/C>\r\n   <\/Marks>\r\n   <LastPath>\r\n      d:\\\r\n   <\/LastPath>\r\n<\/root>\r\n\r\n<item name=\"root\">\r\n   <item name=\"Marks\">\r\n      <item name=\"A\">\r\n         C:\\Usb\\i_green\\apps\r\n         <item name=\"myLevel3\">\r\n            myLevel3Value\r\n            <item name=\"myLevel4\">\r\n               myLevel4Value\r\n            <\/item>\r\n         <\/item>\r\n      <\/item>\r\n      <item name=\"B\">\r\n         C:\\Users\\User\\Desktop\r\n      <\/item>\r\n      <item name=\"C\">\r\n         C:\\\r\n      <\/item>\r\n   <\/item>\r\n   <item name=\"LastPath\">\r\n      d:\\\r\n   <\/item>\r\n<\/item>\r\n\r\n\r\nCreate object trees and get them or save them as xml \r\n\r\nNOTE: Since the objects are really dictionaries, vim offers 2 syntaxes to interact with their content. One is like this for example \"myRoot.LastPath.Value\" the other is \"myRoot['LastPath'].Value\", in the following examples the first syntax is used but the second would work too.\r\n\r\nRoot level\r\nlet myRoot = g:Item.New()\r\n\r\nFirst level\r\ncal myRoot.Add(g:Item.New2('LastPath', 'd:\\'))\r\necho myRoot.LastPath.Value\r\n\r\ncal myRoot.Add(g:Item.New1('Marks'))\r\necho myRoot.Marks.Value\r\n\r\nSecond level\r\ncal myRoot.Marks.Add(g:Item.New2('A', 'C:\\Usb\\i_green\\apps'))\r\ncal myRoot.Marks.Add(g:Item.New2('B', 'C:\\Users\\User\\Desktop'))\r\ncal myRoot.Marks.Add(g:Item.New2('C', 'C:\\'))\r\necho myRoot.Marks.A.Value\r\necho myRoot.Marks.B.Value\r\necho myRoot.Marks.C.Value\r\nShow how many items there is in the second level\r\necho myRoot.Marks.Count()\r\n\r\nThird level\r\ncal myRoot.Marks.A.Add(g:Item.New2('myLevel3', 'myLevel3Value'))\r\necho myRoot.Marks.A.myLevel3.Value\r\nShow how many items there is in the third level\r\necho myRoot.Marks.A.Count()\r\n\r\nFourth level\r\ncal myRoot.Marks.A.myLevel3.Add(g:Item.New2('myLevel4', 'myLevel4Value'))\r\necho myRoot.Marks.A.myLevel3.myLevel4.Value\r\n\r\nTo get the xml as a list\r\nlet myXmlList = myRoot.ToXmlList()\r\necho myXmlList\r\n\r\nTo save the xml to a file\r\ncal myRoot.SaveToXml('c:\/temp\/cfg.xml')\r\n\r\nRemove an item\r\ncal myRoot.Marks.Remove('A')\r\necho myRoot.Marks.A.Value \" Should give an error saying that the key cannot be found\r\n\r\nCheck for existance of an item\r\nif myRoot.Marks.Contains('A') == 1\r\n  echo \"Contains the item A\"\r\nelse\r\n  echo \"Dosen't contain the item A\"\r\nendif\r\n\r\nExample to copy from third level to a new root. The \"Clone()\" method does a complete copy of the current item, without cloning, the affected variable becomes a refrence and modifying it would modify the original item as well. So use the \"Clone()\" methods if an independent copy is needed.\r\nlet myRoot2 = myRoot.Marks.A.myLevel3.Clone()\r\nDisplay value from new root, now what was 4th level is now first level\r\necho myRoot2.myLevel4.Value\r\n\r\nCreate object trees from a xml files \r\n\r\nNOTE: Since the objects are really dictionaries, vim offers 2 syntaxes to interact with their content. One is like this for example \"myRoot.LastPath.Value\" the other is \"myRoot['LastPath'].Value\", in the following examples the first syntax is used but the second would work too.\r\n\r\nLoad the file created in the previous example\r\nlet myRoot2 = g:Item.LoadFile('c:\/temp\/cfg.xml')\r\n\r\nShow some elements from the loaded xml file\r\necho myRoot2.LastPath.Value\r\necho myRoot2.Marks.A.Value\r\necho myRoot2.Marks.B.Value\r\necho myRoot2.Marks.A.myLevel3.Value\r\necho myRoot2.Marks.A.myLevel3.myLevel4.Value\r\necho myRoot2.Marks.C.Value\r\necho myRoot2.Marks.Value\r\n\r\nCreate object trees from expressions \r\n\r\nThere is another way of creating the object trees using expressions, the \"g:RootItem.LoadFile()\" function is an example how to do this. By expressions, I mean that something like exe 'cal items.Items' . level . '.Add(g:Item.New(\"' . tag . '\", \"\"))' may be used where the \"level\" variable would contain a string of the path to the items like for example \"myItem1.Items.myItem2.Items\".\r\nTodo: \r\n1. Automatically put every tag and values each on his own line (it should be like this to be parsed correctly)\r\n2. Get multiline values inside tags\r\n3. Add some kind of iterator (like in the configuration utility with an ienumerator syntax) to loop the items (without having to check in the client code that the value is a dictionary) See ShowMarks function in vimExplorer where a check for dictionary type is needed and checking if dictionary empty and also a key, value foreach loop dosen't work, the value is not set and there is need to get it using the full g:VeCfg.Mark[key].Value\r\n   Or at least find a way to filter out the items that are not dictionaries using the filter command.\r\n   Give examples how to iterate items in the usage section    \r\n4. Maybe find a way that to get or set a value that does not exist a check and creation would not be needed in the client code (maybe through a function)\r\n\r\n\r\nHistory: \r\n\r\n1.0 Initial release\r\n1.1 Added a function to remove items from the tree \"g:Item.Remove(name)\" by specifying its name in parameter\r\n    Added the \"Contains(name)\" function to check existance of an item\r\n    Changed the file format to display the xml tree with each tag being an \"item\" tag having a name attribute instead of having the name as the tag itself. One avantage of this format is to being able to have a \"\/\" in the tag name. So a xml tree formely in a format like this:\r\n<root>\r\n   <Marks>\r\n      <A>\r\n         C:\\Usb\\i_green\\apps\r\n         <myLevel3>\r\n            myLevel3Value\r\n            <myLevel4>\r\n               myLevel4Value\r\n            <\/myLevel4>\r\n         <\/myLevel3>\r\n      <\/A>\r\n      <B>\r\n         C:\\Users\\User\\Desktop\\\r\n      <\/B>\r\n      <C>\r\n         C:\\\r\n      <\/C>\r\n   <\/Marks>\r\n   <LastPath>\r\n      d:\\\r\n   <\/LastPath>\r\n<\/root>\r\n\r\nis now in a format like this:\r\n\r\n<item name=\"root\">\r\n   <item name=\"Marks\">\r\n      <item name=\"A\">\r\n         C:\\Usb\\i_green\\apps\r\n         <item name=\"myLevel3\">\r\n            myLevel3Value\r\n            <item name=\"myLevel4\">\r\n               myLevel4Value\r\n            <\/item>\r\n         <\/item>\r\n      <\/item>\r\n      <item name=\"B\">\r\n         C:\\Users\\User\\Desktop\r\n      <\/item>\r\n      <item name=\"C\">\r\n         C:\\\r\n      <\/item>\r\n   <\/item>\r\n   <item name=\"LastPath\">\r\n      d:\\\r\n   <\/item>\r\n<\/item>","4":"See latest version on github: https:\/\/github.com\/viaa\/VimPlugins\r\n\r\nDocumentation \r\n\r\nName: basicXmlParser.vim\r\nVersion: 1.1\r\nDescription: Plugin create object trees and get them or save them as xml, and to create object trees from a xml files. May be used as an object tree, the xml is the file format for load and save the object tree from and to a file. Serialization to xml is optional, the user is not required to load or to save to xml, the tree may be builded manually or programmatically. This plugin was created as a utility plugin to load and save configuration files. See the usage section on how to use the plugin.\r\nAuthor: Alexandre Viau (alexandreviau@gmail.com)\r\nInstallation: Copy the plugin to the vim plugin directory.\r\n\r\nUsage: \r\n\r\nThe following examples create, save to file and load from file the following xml tree: \r\n\r\n<root>\r\n   <Marks>\r\n      <A>\r\n         C:\\Usb\\i_green\\apps\r\n         <myLevel3>\r\n            myLevel3Value\r\n            <myLevel4>\r\n               myLevel4Value\r\n            <\/myLevel4>\r\n         <\/myLevel3>\r\n      <\/A>\r\n      <B>\r\n         C:\\Users\\User\\Desktop\\\r\n      <\/B>\r\n      <C>\r\n         C:\\\r\n      <\/C>\r\n   <\/Marks>\r\n   <LastPath>\r\n      d:\\\r\n   <\/LastPath>\r\n<\/root>\r\n\r\n<item name=\"root\">\r\n   <item name=\"Marks\">\r\n      <item name=\"A\">\r\n         C:\\Usb\\i_green\\apps\r\n         <item name=\"myLevel3\">\r\n            myLevel3Value\r\n            <item name=\"myLevel4\">\r\n               myLevel4Value\r\n            <\/item>\r\n         <\/item>\r\n      <\/item>\r\n      <item name=\"B\">\r\n         C:\\Users\\User\\Desktop\r\n      <\/item>\r\n      <item name=\"C\">\r\n         C:\\\r\n      <\/item>\r\n   <\/item>\r\n   <item name=\"LastPath\">\r\n      d:\\\r\n   <\/item>\r\n<\/item>\r\n\r\n\r\nCreate object trees and get them or save them as xml \r\n\r\nNOTE: Since the objects are really dictionaries, vim offers 2 syntaxes to interact with their content. One is like this for example \"myRoot.LastPath.Value\" the other is \"myRoot['LastPath'].Value\", in the following examples the first syntax is used but the second would work too.\r\n\r\nRoot level\r\nlet myRoot = g:Item.New()\r\n\r\nFirst level\r\ncal myRoot.Add(g:Item.New2('LastPath', 'd:\\'))\r\necho myRoot.LastPath.Value\r\n\r\ncal myRoot.Add(g:Item.New1('Marks'))\r\necho myRoot.Marks.Value\r\n\r\nSecond level\r\ncal myRoot.Marks.Add(g:Item.New2('A', 'C:\\Usb\\i_green\\apps'))\r\ncal myRoot.Marks.Add(g:Item.New2('B', 'C:\\Users\\User\\Desktop'))\r\ncal myRoot.Marks.Add(g:Item.New2('C', 'C:\\'))\r\necho myRoot.Marks.A.Value\r\necho myRoot.Marks.B.Value\r\necho myRoot.Marks.C.Value\r\nShow how many items there is in the second level\r\necho myRoot.Marks.Count()\r\n\r\nThird level\r\ncal myRoot.Marks.A.Add(g:Item.New2('myLevel3', 'myLevel3Value'))\r\necho myRoot.Marks.A.myLevel3.Value\r\nShow how many items there is in the third level\r\necho myRoot.Marks.A.Count()\r\n\r\nFourth level\r\ncal myRoot.Marks.A.myLevel3.Add(g:Item.New2('myLevel4', 'myLevel4Value'))\r\necho myRoot.Marks.A.myLevel3.myLevel4.Value\r\n\r\nTo get the xml as a list\r\nlet myXmlList = myRoot.ToXmlList()\r\necho myXmlList\r\n\r\nTo save the xml to a file\r\ncal myRoot.SaveToXml('c:\/temp\/cfg.xml')\r\n\r\nRemove an item\r\ncal myRoot.Marks.Remove('A')\r\necho myRoot.Marks.A.Value \" Should give an error saying that the key cannot be found\r\n\r\nCheck for existance of an item\r\nif myRoot.Marks.Contains('A') == 1\r\n  echo \"Contains the item A\"\r\nelse\r\n  echo \"Dosen't contain the item A\"\r\nendif\r\n\r\nExample to copy from third level to a new root. The \"Clone()\" method does a complete copy of the current item, without cloning, the affected variable becomes a refrence and modifying it would modify the original item as well. So use the \"Clone()\" methods if an independent copy is needed.\r\nlet myRoot2 = myRoot.Marks.A.myLevel3.Clone()\r\nDisplay value from new root, now what was 4th level is now first level\r\necho myRoot2.myLevel4.Value\r\n\r\nCreate object trees from a xml files \r\n\r\nNOTE: Since the objects are really dictionaries, vim offers 2 syntaxes to interact with their content. One is like this for example \"myRoot.LastPath.Value\" the other is \"myRoot['LastPath'].Value\", in the following examples the first syntax is used but the second would work too.\r\n\r\nLoad the file created in the previous example\r\nlet myRoot2 = g:Item.LoadFile('c:\/temp\/cfg.xml')\r\n\r\nShow some elements from the loaded xml file\r\necho myRoot2.LastPath.Value\r\necho myRoot2.Marks.A.Value\r\necho myRoot2.Marks.B.Value\r\necho myRoot2.Marks.A.myLevel3.Value\r\necho myRoot2.Marks.A.myLevel3.myLevel4.Value\r\necho myRoot2.Marks.C.Value\r\necho myRoot2.Marks.Value\r\n\r\nCreate object trees from expressions \r\n\r\nThere is another way of creating the object trees using expressions, the \"g:RootItem.LoadFile()\" function is an example how to do this. By expressions, I mean that something like exe 'cal items.Items' . level . '.Add(g:Item.New(\"' . tag . '\", \"\"))' may be used where the \"level\" variable would contain a string of the path to the items like for example \"myItem1.Items.myItem2.Items\".\r\nTodo: \r\n1. Automatically put every tag and values each on his own line (it should be like this to be parsed correctly)\r\n2. Get multiline values inside tags\r\n3. Add some kind of iterator (like in the configuration utility with an ienumerator syntax) to loop the items (without having to check in the client code that the value is a dictionary) See ShowMarks function in vimExplorer where a check for dictionary type is needed and checking if dictionary empty and also a key, value foreach loop dosen't work, the value is not set and there is need to get it using the full g:VeCfg.Mark[key].Value\r\n   Or at least find a way to filter out the items that are not dictionaries using the filter command.\r\n   Give examples how to iterate items in the usage section    \r\n4. Maybe find a way that to get or set a value that does not exist a check and creation would not be needed in the client code (maybe through a function)\r\n\r\n\r\nHistory: \r\n\r\n1.0 Initial release\r\n1.1 Added a function to remove items from the tree \"g:Item.Remove(name)\" by specifying its name in parameter\r\n    Added the \"Contains(name)\" function to check existance of an item\r\n    Changed the file format to display the xml tree with each tag being an \"item\" tag having a name attribute instead of having the name as the tag itself. One avantage of this format is to being able to have a \"\/\" in the tag name. So a xml tree formely in a format like this:\r\n<root>\r\n   <Marks>\r\n      <A>\r\n         C:\\Usb\\i_green\\apps\r\n         <myLevel3>\r\n            myLevel3Value\r\n            <myLevel4>\r\n               myLevel4Value\r\n            <\/myLevel4>\r\n         <\/myLevel3>\r\n      <\/A>\r\n      <B>\r\n         C:\\Users\\User\\Desktop\\\r\n      <\/B>\r\n      <C>\r\n         C:\\\r\n      <\/C>\r\n   <\/Marks>\r\n   <LastPath>\r\n      d:\\\r\n   <\/LastPath>\r\n<\/root>\r\n\r\nis now in a format like this:\r\n\r\n<item name=\"root\">\r\n   <item name=\"Marks\">\r\n      <item name=\"A\">\r\n         C:\\Usb\\i_green\\apps\r\n         <item name=\"myLevel3\">\r\n            myLevel3Value\r\n            <item name=\"myLevel4\">\r\n               myLevel4Value\r\n            <\/item>\r\n         <\/item>\r\n      <\/item>\r\n      <item name=\"B\">\r\n         C:\\Users\\User\\Desktop\r\n      <\/item>\r\n      <item name=\"C\">\r\n         C:\\\r\n      <\/item>\r\n   <\/item>\r\n   <item name=\"LastPath\">\r\n      d:\\\r\n   <\/item>\r\n<\/item>","install_details":"Installation: Copy the plugin to the vim plugin directory.","5":"Installation: Copy the plugin to the vim plugin directory.","first_name":"Alexandre","6":"Alexandre","last_name":"Viau","7":"Viau","releases":[{"0":"4380","vim_version":"7.0","1":"7.0","script_version":"1.1","2":"1.1","version_comment":"Added a function to remove items from the tree \"g:Item.Remove(name)\" by specifying its name in parameter\r\nAdded the \"Contains(name)\" function to check existance of an item\r\nChanged the file format to display the xml tree with each tag being an \"item\" tag having a name attribute instead of having the name as the tag itself. One avantage of this format is to being able to have a \"\/\" in the tag name. So a xml tree formely in a format like this:\r\n<root>\r\n   <Marks>\r\n      <A>\r\n         C:\\Usb\\i_green\\apps\r\n         <myLevel3>\r\n            myLevel3Value\r\n            <myLevel4>\r\n               myLevel4Value\r\n            <\/myLevel4>\r\n         <\/myLevel3>\r\n      <\/A>\r\n      <B>\r\n         C:\\Users\\User\\Desktop\\\r\n      <\/B>\r\n      <C>\r\n         C:\\\r\n      <\/C>\r\n   <\/Marks>\r\n   <LastPath>\r\n      d:\\\r\n   <\/LastPath>\r\n<\/root>\r\n\r\nis now in a format like this:\r\n\r\n<item name=\"root\">\r\n   <item name=\"Marks\">\r\n      <item name=\"A\">\r\n         C:\\Usb\\i_green\\apps\r\n         <item name=\"myLevel3\">\r\n            myLevel3Value\r\n            <item name=\"myLevel4\">\r\n               myLevel4Value\r\n            <\/item>\r\n         <\/item>\r\n      <\/item>\r\n      <item name=\"B\">\r\n         C:\\Users\\User\\Desktop\r\n      <\/item>\r\n      <item name=\"C\">\r\n         C:\\\r\n      <\/item>\r\n   <\/item>\r\n   <item name=\"LastPath\">\r\n      d:\\\r\n   <\/item>\r\n<\/item>","3":"Added a function to remove items from the tree \"g:Item.Remove(name)\" by specifying its name in parameter\r\nAdded the \"Contains(name)\" function to check existance of an item\r\nChanged the file format to display the xml tree with each tag being an \"item\" tag having a name attribute instead of having the name as the tag itself. One avantage of this format is to being able to have a \"\/\" in the tag name. So a xml tree formely in a format like this:\r\n<root>\r\n   <Marks>\r\n      <A>\r\n         C:\\Usb\\i_green\\apps\r\n         <myLevel3>\r\n            myLevel3Value\r\n            <myLevel4>\r\n               myLevel4Value\r\n            <\/myLevel4>\r\n         <\/myLevel3>\r\n      <\/A>\r\n      <B>\r\n         C:\\Users\\User\\Desktop\\\r\n      <\/B>\r\n      <C>\r\n         C:\\\r\n      <\/C>\r\n   <\/Marks>\r\n   <LastPath>\r\n      d:\\\r\n   <\/LastPath>\r\n<\/root>\r\n\r\nis now in a format like this:\r\n\r\n<item name=\"root\">\r\n   <item name=\"Marks\">\r\n      <item name=\"A\">\r\n         C:\\Usb\\i_green\\apps\r\n         <item name=\"myLevel3\">\r\n            myLevel3Value\r\n            <item name=\"myLevel4\">\r\n               myLevel4Value\r\n            <\/item>\r\n         <\/item>\r\n      <\/item>\r\n      <item name=\"B\">\r\n         C:\\Users\\User\\Desktop\r\n      <\/item>\r\n      <item name=\"C\">\r\n         C:\\\r\n      <\/item>\r\n   <\/item>\r\n   <item name=\"LastPath\">\r\n      d:\\\r\n   <\/item>\r\n<\/item>","package":"basicXmlParser.vim","4":"basicXmlParser.vim","src_id":"19385","5":"19385","creation_date":"1358577870","6":"1358577870"},{"0":"4380","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"basicXmlParser.vim","4":"basicXmlParser.vim","src_id":"19296","5":"19296","creation_date":"1357126382","6":"1357126382"}]},"4379":{"script_id":"4379","0":"4379","script_name":"paren-crosshairs","1":"paren-crosshairs","script_type":"utility","2":"utility","summary":"Displays crosshairs on the cursor when moving over parens ","3":"Displays crosshairs on the cursor when moving over parens ","description":"The matchparen plugin tries to do a good thing; namely, highlight the paren that matches the one under the cursor. However, my friends and I found that having two parentheses highlighted always confounds our intuition about where the cursor actually is.\r\n\r\nThis plugin deals with this problem by setting cursorline and cursorcolumn when the cursor is on a paren.\r\n\r\nFor screenshots and recent developments, see https:\/\/github.com\/chreekat\/vim-paren-crosshairs","4":"The matchparen plugin tries to do a good thing; namely, highlight the paren that matches the one under the cursor. However, my friends and I found that having two parentheses highlighted always confounds our intuition about where the cursor actually is.\r\n\r\nThis plugin deals with this problem by setting cursorline and cursorcolumn when the cursor is on a paren.\r\n\r\nFor screenshots and recent developments, see https:\/\/github.com\/chreekat\/vim-paren-crosshairs","install_details":"Untar the package and copy the plugin directory to ~\/.vim. Or, use pathogen or vundle with the github repo listed in the description.","5":"Untar the package and copy the plugin directory to ~\/.vim. Or, use pathogen or vundle with the github repo listed in the description.","first_name":"Bryan","6":"Bryan","last_name":"Richter","7":"Richter","releases":[{"0":"4379","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"paren-crosshairs.tar.gz","4":"paren-crosshairs.tar.gz","src_id":"19279","5":"19279","creation_date":"1357053291","6":"1357053291"}]},"4378":{"script_id":"4378","0":"4378","script_name":"smartpairs","1":"smartpairs","script_type":"utility","2":"utility","summary":"Fantastic selections for Vim","3":"Fantastic selections for Vim","description":"About\r\n\r\nSmartpairs allows you forget about difficult keys combination like vi{ or va\".\r\n\r\nNow you can use only one shortcut for all typical combinations. Even if you've already \r\nselected something you can easily fix selection by using smartpairs. \r\n\r\nPlugin searches first unpair symbol from the left of the current cursor\r\nposition and then runs target command with this symbol. When you press \r\n'v' again plugin extend current selection by next pairs.\r\n\r\nInstallation\r\n\r\nUse https:\/\/github.com\/tpope\/vim-pathogen for quick plugin installation. \r\n\r\nIf you already have pathogen then put smartpairs into ~\/.vim\/bundle like this:\r\n\r\n    cd ~\/.vim\/bundle\r\n    git clone https:\/\/github.com\/gorkunov\/smartpairs.vim.git\r\n\r\nMappings\r\n\r\nBy default smartpairs focuses on selection command but it also supports delete\/change\/yank.\r\n\r\nCommands list:\r\n\r\n    vi* -> viv\r\n    va* -> vav\r\n    ci* -> civ\r\n    ca* -> cav\r\n    di* -> div\r\n    da* -> dav\r\n    ya* -> yiv\r\n    ya* -> yav\r\n    Where * is in <, >, \", ', `, (, ), [, ], {, } or t as tag\r\n    \r\nAfter v* commands you can press v again and selection will be extended to \r\nthe next pairs.\r\n\r\nAdvanced configuration\r\n\r\nFor changing smartpairs keys binding add those lines to your .vimrc file:\r\n\r\n\"Key for running smartpairs in all modes (select\/delete\/change\/yank)\r\n\"default is 'v'\r\nlet g:smartpairs_key = 'v'\r\n\r\n\"Key for running smartpairs in the selection mode \r\n\"(extend current selection to the next pair)\r\n\"default is 'v'\r\nlet g:smartpairs_nextpairs_key = 'v'\r\n\r\n\"Key for running smartpairs in the selection mode\r\n\"for extending selection with IN-mod (like vi\")\r\n\"default is 'z'\r\nlet g:smartpairs_nextpairs_key_i = 'z'\r\n\r\n\"Key for running smartpairs in the selection mode \r\n\"for extending selection with ABOVE-mod (like va\")\r\n\"default is 'Z'\r\nlet g:smartpairs_nextpairs_key_a = 'Z'\r\n\r\n\"Smartpairs looks only 20 lines before cursor position\r\n\"but you can changes this limit:\r\nlet g:smartpairs_maxdepth = 20\r\n```\r\n\r\nLicense\r\n\r\nSmartpairs is released under the wtfpl (http:\/\/sam.zoy.org\/wtfpl\/COPYING)","4":"About\r\n\r\nSmartpairs allows you forget about difficult keys combination like vi{ or va\".\r\n\r\nNow you can use only one shortcut for all typical combinations. Even if you've already \r\nselected something you can easily fix selection by using smartpairs. \r\n\r\nPlugin searches first unpair symbol from the left of the current cursor\r\nposition and then runs target command with this symbol. When you press \r\n'v' again plugin extend current selection by next pairs.\r\n\r\nInstallation\r\n\r\nUse https:\/\/github.com\/tpope\/vim-pathogen for quick plugin installation. \r\n\r\nIf you already have pathogen then put smartpairs into ~\/.vim\/bundle like this:\r\n\r\n    cd ~\/.vim\/bundle\r\n    git clone https:\/\/github.com\/gorkunov\/smartpairs.vim.git\r\n\r\nMappings\r\n\r\nBy default smartpairs focuses on selection command but it also supports delete\/change\/yank.\r\n\r\nCommands list:\r\n\r\n    vi* -> viv\r\n    va* -> vav\r\n    ci* -> civ\r\n    ca* -> cav\r\n    di* -> div\r\n    da* -> dav\r\n    ya* -> yiv\r\n    ya* -> yav\r\n    Where * is in <, >, \", ', `, (, ), [, ], {, } or t as tag\r\n    \r\nAfter v* commands you can press v again and selection will be extended to \r\nthe next pairs.\r\n\r\nAdvanced configuration\r\n\r\nFor changing smartpairs keys binding add those lines to your .vimrc file:\r\n\r\n\"Key for running smartpairs in all modes (select\/delete\/change\/yank)\r\n\"default is 'v'\r\nlet g:smartpairs_key = 'v'\r\n\r\n\"Key for running smartpairs in the selection mode \r\n\"(extend current selection to the next pair)\r\n\"default is 'v'\r\nlet g:smartpairs_nextpairs_key = 'v'\r\n\r\n\"Key for running smartpairs in the selection mode\r\n\"for extending selection with IN-mod (like vi\")\r\n\"default is 'z'\r\nlet g:smartpairs_nextpairs_key_i = 'z'\r\n\r\n\"Key for running smartpairs in the selection mode \r\n\"for extending selection with ABOVE-mod (like va\")\r\n\"default is 'Z'\r\nlet g:smartpairs_nextpairs_key_a = 'Z'\r\n\r\n\"Smartpairs looks only 20 lines before cursor position\r\n\"but you can changes this limit:\r\nlet g:smartpairs_maxdepth = 20\r\n```\r\n\r\nLicense\r\n\r\nSmartpairs is released under the wtfpl (http:\/\/sam.zoy.org\/wtfpl\/COPYING)","install_details":"","5":"","first_name":"Alexander","6":"Alexander","last_name":"Gorkunov","7":"Gorkunov","releases":[{"0":"4378","vim_version":"7.3","1":"7.3","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"smartpairs.zip","4":"smartpairs.zip","src_id":"19267","5":"19267","creation_date":"1356949548","6":"1356949548"}]},"4377":{"script_id":"4377","0":"4377","script_name":"vim-tags","1":"vim-tags","script_type":"utility","2":"utility","summary":"The Ctags generator for Vim","3":"The Ctags generator for Vim","description":"About\r\n\r\nCtags support is a great feature in Vim. One approach to make use of Ctags is the way of Tim Pope's plugins. For example in Rails projects, Ctags are generated automatically while Bundler is running and installing new gems.\r\n\r\nVim-Tags plugin treats Ctags like more tightly coupled within a concrete project. It creates '.tags' files directly in the root project directory. Also, it can perform tags creation upon each file saving through forking - available under Unix-like operating systems. This option, however, may require some tweaking under Windows.\r\n\r\nVim-Tags is under active development. Currently, besides its main features, it provides some support for Ruby\/Rails projects (it can generate tags for gems listed in 'Gemfile.lock' file).\r\n\r\nUsage\r\n\r\nThe plugin has only one command and a few options described in the Configuration section:\r\n\r\n:TagsGenerate\r\n\r\nThis command generates one or more tags files. By default, it generates only the \"tags\" file collecting tags from all files nad subdirectories of the current working directory - assuming it's the root of the project.\r\n\r\nBy default, you rarely will have to use this command, because once the \"tags\" file is found in the root directory, the tags are generated on each file saving. So, in most cases, to enable Vim-Tags support just create empty \"tags\" file:\r\n\r\ntouch tags\r\n\r\nand start Vim. On first file saving (any file is considered), the tags will be generated.\r\n\r\nAdditionally, you can exclude some directories from the main \"tags\" file, especially if they contains rarely changed and heavy content, i.e. third-party libraries. Those directories must be placed directly at the root.\r\n\r\nTo exclude them, make empty files named exactly after those directories with \".tags\" suffixes: e.g. \"vendor.tags\" for the \"vendor\" directory and start (or restart) Vim. Beginning from the next Vim run, the plugin will be watching modification times of those directories and corresponding tags files and perform tags generation only if necessary.\r\n\r\nThe last but not least feature is the Ruby Bundler support. It's easy and straightforward. If your project root contains \"Gemfile.lock\" file, the plugin will be generating tags for all your Bundler gems referenced in the Gemfile. Here, \"Gemfile.lock\" modification time will be taken to find out whether the tags generation is required, just like in the custom directories case explained earlier. The plugin will create \"Gemfile.lock.tags\" file automatically\r\n\r\nConfiguration\r\n\r\nVim-Tags assumes that you have 'ctags' utility available in your shell. However it is possible to change or improve shell commands used by the plugin, e.g. in case you have to point a proper binary with absolute path or tweak some options.\r\n\r\nVim-Tags can be configured by setting some global variables in your \".vimrc\" file.\r\n\r\nThe available variables are:\r\n\r\n    vim_tags_auto_generate\r\n        Default: 1\r\n\r\n    If enabled, Vim-Tags will generate tags on file saving\r\n\r\n    let g:vim_tags_auto_generate = 1\r\n\r\n    vim_tags_project_tags_command\r\n        Default: \"ctags -R {OPTIONS} {DIRECTORY} 2>\/dev\/null &\"\r\n\r\n    This command is used for main Ctags generation.\r\n\r\n    let g:vim_tags_project_tags_command = \"ctags -R {OPTIONS} {DIRECTORY} 2>\/dev\/null &\"\r\n\r\n    vim_tags_gems_tags_command\r\n        Default: \"ctags -R -f Gemfile.lock.tags bundle show --paths 2>\/dev\/null &\"\r\n\r\n    Command used for Gemfile tags generation.\r\n\r\n    let g:vim_tags_gems_tags_command = \"ctags -R -f Gemfile.lock.tags `bundle show --paths` 2>\/dev\/null &\"\r\n\r\nAuthor and License\r\n\r\nVim-Tags plugin was written by Szymon Wrozynski. It is licensed under the same terms as Vim itself. For more info see :help license.","4":"About\r\n\r\nCtags support is a great feature in Vim. One approach to make use of Ctags is the way of Tim Pope's plugins. For example in Rails projects, Ctags are generated automatically while Bundler is running and installing new gems.\r\n\r\nVim-Tags plugin treats Ctags like more tightly coupled within a concrete project. It creates '.tags' files directly in the root project directory. Also, it can perform tags creation upon each file saving through forking - available under Unix-like operating systems. This option, however, may require some tweaking under Windows.\r\n\r\nVim-Tags is under active development. Currently, besides its main features, it provides some support for Ruby\/Rails projects (it can generate tags for gems listed in 'Gemfile.lock' file).\r\n\r\nUsage\r\n\r\nThe plugin has only one command and a few options described in the Configuration section:\r\n\r\n:TagsGenerate\r\n\r\nThis command generates one or more tags files. By default, it generates only the \"tags\" file collecting tags from all files nad subdirectories of the current working directory - assuming it's the root of the project.\r\n\r\nBy default, you rarely will have to use this command, because once the \"tags\" file is found in the root directory, the tags are generated on each file saving. So, in most cases, to enable Vim-Tags support just create empty \"tags\" file:\r\n\r\ntouch tags\r\n\r\nand start Vim. On first file saving (any file is considered), the tags will be generated.\r\n\r\nAdditionally, you can exclude some directories from the main \"tags\" file, especially if they contains rarely changed and heavy content, i.e. third-party libraries. Those directories must be placed directly at the root.\r\n\r\nTo exclude them, make empty files named exactly after those directories with \".tags\" suffixes: e.g. \"vendor.tags\" for the \"vendor\" directory and start (or restart) Vim. Beginning from the next Vim run, the plugin will be watching modification times of those directories and corresponding tags files and perform tags generation only if necessary.\r\n\r\nThe last but not least feature is the Ruby Bundler support. It's easy and straightforward. If your project root contains \"Gemfile.lock\" file, the plugin will be generating tags for all your Bundler gems referenced in the Gemfile. Here, \"Gemfile.lock\" modification time will be taken to find out whether the tags generation is required, just like in the custom directories case explained earlier. The plugin will create \"Gemfile.lock.tags\" file automatically\r\n\r\nConfiguration\r\n\r\nVim-Tags assumes that you have 'ctags' utility available in your shell. However it is possible to change or improve shell commands used by the plugin, e.g. in case you have to point a proper binary with absolute path or tweak some options.\r\n\r\nVim-Tags can be configured by setting some global variables in your \".vimrc\" file.\r\n\r\nThe available variables are:\r\n\r\n    vim_tags_auto_generate\r\n        Default: 1\r\n\r\n    If enabled, Vim-Tags will generate tags on file saving\r\n\r\n    let g:vim_tags_auto_generate = 1\r\n\r\n    vim_tags_project_tags_command\r\n        Default: \"ctags -R {OPTIONS} {DIRECTORY} 2>\/dev\/null &\"\r\n\r\n    This command is used for main Ctags generation.\r\n\r\n    let g:vim_tags_project_tags_command = \"ctags -R {OPTIONS} {DIRECTORY} 2>\/dev\/null &\"\r\n\r\n    vim_tags_gems_tags_command\r\n        Default: \"ctags -R -f Gemfile.lock.tags bundle show --paths 2>\/dev\/null &\"\r\n\r\n    Command used for Gemfile tags generation.\r\n\r\n    let g:vim_tags_gems_tags_command = \"ctags -R -f Gemfile.lock.tags `bundle show --paths` 2>\/dev\/null &\"\r\n\r\nAuthor and License\r\n\r\nVim-Tags plugin was written by Szymon Wrozynski. It is licensed under the same terms as Vim itself. For more info see :help license.","install_details":"Installation\r\n\r\nPlace in ~\/.vim\/plugin\/tags.vim or in case of Pathogen:\r\n\r\ncd ~\/.vim\/bundle\r\ngit clone https:\/\/github.com\/szw\/vim-tags.git\r\n\r\nVim-Tags requires ctags utility. On Ubuntu you can install it with:\r\n\r\nsudo apt-get install exuberant-ctags\r\n\r\nThe most recent version can be found here: https:\/\/github.com\/szw\/vim-tags","5":"Installation\r\n\r\nPlace in ~\/.vim\/plugin\/tags.vim or in case of Pathogen:\r\n\r\ncd ~\/.vim\/bundle\r\ngit clone https:\/\/github.com\/szw\/vim-tags.git\r\n\r\nVim-Tags requires ctags utility. On Ubuntu you can install it with:\r\n\r\nsudo apt-get install exuberant-ctags\r\n\r\nThe most recent version can be found here: https:\/\/github.com\/szw\/vim-tags","first_name":"Szymon","6":"Szymon","last_name":"Wrozynski","7":"Wrozynski","releases":[{"0":"4377","vim_version":"7.0","1":"7.0","script_version":"0.0.2","2":"0.0.2","version_comment":"Initial upload","3":"Initial upload","package":"vim-tags.zip","4":"vim-tags.zip","src_id":"19264","5":"19264","creation_date":"1356914415","6":"1356914415"}]},"4376":{"script_id":"4376","0":"4376","script_name":"vim-maximizer","1":"vim-maximizer","script_type":"utility","2":"utility","summary":"Maximizes and restores the current window in Vim.","3":"Maximizes and restores the current window in Vim.","description":"About\r\n\r\nMaximizer lets you maximize split windows and restore them automatically. It is very useful if you like to have many split windows per tab. And also, if the text you are working with does not ...subscribe to the ridiculous Church of 80-character Lines.... It means, while working with Ruby on Rails code. ;) Or just with lengthy HTML files.\r\n\r\nUsage\r\n\r\nMaximizer has only one command:\r\n\r\n:MaximizerToggle\r\n\r\nIt is meant to be mapped in many ways by the user himself. See Configuration to get some examples.\r\n\r\nUpon the first invocation of the command, Vim-Maximizer saves dimensions and positions of all windows in the current tab, and then it performs maximization of the active window. The second time the command is invoked, Maximizer restores all windows to the previously saved positions and the cycle repeats.\r\n\r\nConfiguration\r\n\r\nMaximizer is extremely handy with command mappings. The mappings can be defined for normal, insert, and visual modes. Here is the example of the <F3> key usage. You can paste it directly into your .vimrc file.\r\n\r\nnnoremap <silent><F3> :MaximizerToggle<CR>\r\nvnoremap <silent><F3> :MaximizerToggle<CR>gv\r\ninoremap <silent><F3> <C-o>:MaximizerToggle<CR>\r\n\r\nWith these mappings you can hit <F3> any time, not only in normal mode. Other handy situations may include typing some text while you don't fit the current split window or selecting some long lines in the visual mode. Just try it yourself.\r\n\r\nMaximizer respects minimal allowed window size, both vertically and horizontally. By default the minimal window height and width are set to 1. You can change those values by tweaking 'winminheight' ('wmh') and 'winminwidth' ('wmw') settings in your .vimrc.\r\n\r\nAuthor and License\r\n\r\nMaximizer was written by Szymon Wrozynski. It is licensed under the same terms as Vim itself.\r\n\r\nCopyright \u00c2\u00a9 2012 Szymon Wrozynski. See :help license\r\n","4":"About\r\n\r\nMaximizer lets you maximize split windows and restore them automatically. It is very useful if you like to have many split windows per tab. And also, if the text you are working with does not ...subscribe to the ridiculous Church of 80-character Lines.... It means, while working with Ruby on Rails code. ;) Or just with lengthy HTML files.\r\n\r\nUsage\r\n\r\nMaximizer has only one command:\r\n\r\n:MaximizerToggle\r\n\r\nIt is meant to be mapped in many ways by the user himself. See Configuration to get some examples.\r\n\r\nUpon the first invocation of the command, Vim-Maximizer saves dimensions and positions of all windows in the current tab, and then it performs maximization of the active window. The second time the command is invoked, Maximizer restores all windows to the previously saved positions and the cycle repeats.\r\n\r\nConfiguration\r\n\r\nMaximizer is extremely handy with command mappings. The mappings can be defined for normal, insert, and visual modes. Here is the example of the <F3> key usage. You can paste it directly into your .vimrc file.\r\n\r\nnnoremap <silent><F3> :MaximizerToggle<CR>\r\nvnoremap <silent><F3> :MaximizerToggle<CR>gv\r\ninoremap <silent><F3> <C-o>:MaximizerToggle<CR>\r\n\r\nWith these mappings you can hit <F3> any time, not only in normal mode. Other handy situations may include typing some text while you don't fit the current split window or selecting some long lines in the visual mode. Just try it yourself.\r\n\r\nMaximizer respects minimal allowed window size, both vertically and horizontally. By default the minimal window height and width are set to 1. You can change those values by tweaking 'winminheight' ('wmh') and 'winminwidth' ('wmw') settings in your .vimrc.\r\n\r\nAuthor and License\r\n\r\nMaximizer was written by Szymon Wrozynski. It is licensed under the same terms as Vim itself.\r\n\r\nCopyright \u00c2\u00a9 2012 Szymon Wrozynski. See :help license\r\n","install_details":"Installation\r\n\r\nPlace in ~\/.vim\/plugin\/maximizer.vim or in case of Pathogen:\r\n\r\ncd ~\/.vim\/bundle\r\ngit clone https:\/\/github.com\/szw\/vim-maximizer.git\r\n\r\nThe most recent version can be found here: https:\/\/github.com\/szw\/vim-maximizer","5":"Installation\r\n\r\nPlace in ~\/.vim\/plugin\/maximizer.vim or in case of Pathogen:\r\n\r\ncd ~\/.vim\/bundle\r\ngit clone https:\/\/github.com\/szw\/vim-maximizer.git\r\n\r\nThe most recent version can be found here: https:\/\/github.com\/szw\/vim-maximizer","first_name":"Szymon","6":"Szymon","last_name":"Wrozynski","7":"Wrozynski","releases":[{"0":"4376","vim_version":"7.0","1":"7.0","script_version":"1.0.1","2":"1.0.1","version_comment":"Initial upload","3":"Initial upload","package":"vim-maximizer.zip","4":"vim-maximizer.zip","src_id":"19263","5":"19263","creation_date":"1356913998","6":"1356913998"}]},"4375":{"script_id":"4375","0":"4375","script_name":"sleuth.vim","1":"sleuth.vim","script_type":"utility","2":"utility","summary":"Heuristically set buffer options","3":"Heuristically set buffer options","description":"This plugin automatically adjusts 'shiftwidth' and 'expandtab' heuristically based on the current file, or, in the case the current file is new, blank, or otherwise insufficient, by looking at other files of the same type in the current and parent directories.  In lieu of adjusting 'softtabstop', 'smarttab' is enabled.\r\n\r\nCompare to DetectIndent (vimscript #1171).  I wrote this because I wanted something fully automatic.  My goal is that by installing this plugin, you can remove all indenting related configuration from your vimrc.\r\n\r\nhttps:\/\/github.com\/tpope\/vim-sleuth","4":"This plugin automatically adjusts 'shiftwidth' and 'expandtab' heuristically based on the current file, or, in the case the current file is new, blank, or otherwise insufficient, by looking at other files of the same type in the current and parent directories.  In lieu of adjusting 'softtabstop', 'smarttab' is enabled.\r\n\r\nCompare to DetectIndent (vimscript #1171).  I wrote this because I wanted something fully automatic.  My goal is that by installing this plugin, you can remove all indenting related configuration from your vimrc.\r\n\r\nhttps:\/\/github.com\/tpope\/vim-sleuth","install_details":"Extract in ~\/.vim (~\\vimfiles on Windows).","5":"Extract in ~\/.vim (~\\vimfiles on Windows).","first_name":"Tim","6":"Tim","last_name":"Pope","7":"Pope","releases":[{"0":"4375","vim_version":"7.0","1":"7.0","script_version":"2.0","2":"2.0","version_comment":"Set endofline, fileformat, fileencoding, bomb from EditorConfig.\r\nSet filetype from modeline and EditorConfig.\r\nSet softtabstop to -1, always.\r\nDrop autocmd neighbor detection in favor of simple extension matching.\r\nEnable disabling heuristics on a per-filetype basis.\r\nBug fixes and assorted tweaks.","3":"Set endofline, fileformat, fileencoding, bomb from EditorConfig.\r\nSet filetype from modeline and EditorConfig.\r\nSet softtabstop to -1, always.\r\nDrop autocmd neighbor detection in favor of simple extension matching.\r\nEnable disabling heuristics on a per-filetype basis.\r\nBug fixes and assorted tweaks.","package":"sleuth.zip","4":"sleuth.zip","src_id":"28019","5":"28019","creation_date":"1651201169","6":"1651201169"},{"0":"4375","vim_version":"7.0","1":"7.0","script_version":"1.3","2":"1.3","version_comment":"Support EditorConfig and modelines.\r\nDetect 'textwidth' and 'fixendofline' in EditorConfig and modelines.\r\nShow reason for each option in :verbose Sleuth.\r\nAssorted performance improvements.\r\nUse most common indent increment, rather than smallest, as 'shiftwidth'.\r\nLeverage 'shiftwidth' of 0 to delegate to 'tabstop'.\r\nLimit neighbor detection to containing and parent directory.\r\nFix neighbor detection for *.h files.\r\nSkip over heredocs in shell scripts, Perl, PHP, and Ruby.\r\nLimit supported 'shiftwidth' values to 2, 3, and multiples of 4.\r\nProvide option to opt out of :filetype indent on.","3":"Support EditorConfig and modelines.\r\nDetect 'textwidth' and 'fixendofline' in EditorConfig and modelines.\r\nShow reason for each option in :verbose Sleuth.\r\nAssorted performance improvements.\r\nUse most common indent increment, rather than smallest, as 'shiftwidth'.\r\nLeverage 'shiftwidth' of 0 to delegate to 'tabstop'.\r\nLimit neighbor detection to containing and parent directory.\r\nFix neighbor detection for *.h files.\r\nSkip over heredocs in shell scripts, Perl, PHP, and Ruby.\r\nLimit supported 'shiftwidth' values to 2, 3, and multiples of 4.\r\nProvide option to opt out of :filetype indent on.","package":"sleuth.zip","4":"sleuth.zip","src_id":"27904","5":"27904","creation_date":"1641954183","6":"1641954183"},{"0":"4375","vim_version":"7.0","1":"7.0","script_version":"1.2","2":"1.2","version_comment":"Add option to limit number of other files checked, defaulting to 20.\r\nAdd global and local options to disable automatic detection.\r\nProvide :Sleuth for manual detection.\r\nAdd indicator for flagship.vim.\r\nSkip over Python style triple quoted strings.\r\nSkip over XML\/HTML style comments.\r\nSkip over backtick quoted strings in Go files only.\r\nAvoid activating on help buffers.\r\nCheck vimrc when sleuthing under Vim filetype.\r\nDisallow odd 'shiftwidth' values greater than 3.","3":"Add option to limit number of other files checked, defaulting to 20.\r\nAdd global and local options to disable automatic detection.\r\nProvide :Sleuth for manual detection.\r\nAdd indicator for flagship.vim.\r\nSkip over Python style triple quoted strings.\r\nSkip over XML\/HTML style comments.\r\nSkip over backtick quoted strings in Go files only.\r\nAvoid activating on help buffers.\r\nCheck vimrc when sleuthing under Vim filetype.\r\nDisallow odd 'shiftwidth' values greater than 3.","package":"sleuth.zip","4":"sleuth.zip","src_id":"27557","5":"27557","creation_date":"1617347028","6":"1617347028"},{"0":"4375","vim_version":"7.0","1":"7.0","script_version":"1.1","2":"1.1","version_comment":"Support custom tabstop in pure tabs files.\r\nFix performance issue with globbing for other files.\r\nSkip over POD comments.","3":"Support custom tabstop in pure tabs files.\r\nFix performance issue with globbing for other files.\r\nSkip over POD comments.","package":"sleuth.zip","4":"sleuth.zip","src_id":"19409","5":"19409","creation_date":"1358810337","6":"1358810337"},{"0":"4375","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"sleuth.zip","4":"sleuth.zip","src_id":"19261","5":"19261","creation_date":"1356909406","6":"1356909406"}]},"4374":{"script_id":"4374","0":"4374","script_name":"pyflakes-nopython.vim","1":"pyflakes-nopython.vim","script_type":"ftplugin","2":"ftplugin","summary":"Pyflakes.vim for Vim installations without Python support.","3":"Pyflakes.vim for Vim installations without Python support.","description":"This is a slightly modified version of the pyflakes.vim script that enables\r\nusing pyflakes even with Vim that has no Python support (in case you are, for\r\nany reason, stuck with such an installation of Vim). However, your system still\r\nhas to have Python installed.\r\n\r\nFor more information about pyflakes and the original pyflakes-vim, see\r\nhttp:\/\/www.vim.org\/scripts\/script.php?script_id=2441.\r\n\r\n\r\nDIFFERENCES FROM pyflakes-vim\r\n\r\nTo work around the unability to call Python code (and thus pyflakes) directly\r\nfrom vim, pyflakes-vim-nopython spawns an external Python process, writes the\r\ncurrent buffer content to its standard input and reads and parses its standard\r\noutput to get the results.\r\n\r\n\r\nKNOWN ISSUES\r\n\r\n* Doesn't work in cygwin when native (Windows) Python is used.\r\n* On Windows, messages are usually not refreshed when changing buffer contents without entering\/leaving Insert mode (via \"r\", \"x\", etc.)\r\n* In Windows gvim, each pyflakes check causes an annoying blink of the window title bar.\r\n* Running a separate Python process each time the source gets changed is not\r\n  very efficient and the time cost may be prohibitive on some machines.\r\n\r\n\r\nFINALLY\r\n\r\nIf you find any bugs, please let me know at WWuzzy@gmail.com. Thanks!","4":"This is a slightly modified version of the pyflakes.vim script that enables\r\nusing pyflakes even with Vim that has no Python support (in case you are, for\r\nany reason, stuck with such an installation of Vim). However, your system still\r\nhas to have Python installed.\r\n\r\nFor more information about pyflakes and the original pyflakes-vim, see\r\nhttp:\/\/www.vim.org\/scripts\/script.php?script_id=2441.\r\n\r\n\r\nDIFFERENCES FROM pyflakes-vim\r\n\r\nTo work around the unability to call Python code (and thus pyflakes) directly\r\nfrom vim, pyflakes-vim-nopython spawns an external Python process, writes the\r\ncurrent buffer content to its standard input and reads and parses its standard\r\noutput to get the results.\r\n\r\n\r\nKNOWN ISSUES\r\n\r\n* Doesn't work in cygwin when native (Windows) Python is used.\r\n* On Windows, messages are usually not refreshed when changing buffer contents without entering\/leaving Insert mode (via \"r\", \"x\", etc.)\r\n* In Windows gvim, each pyflakes check causes an annoying blink of the window title bar.\r\n* Running a separate Python process each time the source gets changed is not\r\n  very efficient and the time cost may be prohibitive on some machines.\r\n\r\n\r\nFINALLY\r\n\r\nIf you find any bugs, please let me know at WWuzzy@gmail.com. Thanks!","install_details":"1. Make sure your vimrc has:\r\n \r\n    filetype on            \" enables filetype detection\r\n    filetype plugin on     \" enables filetype specific plugins\r\n\r\n2. Download the latest version of pyflakes-vim-nopython.\r\n\r\n3. Extract pyflakes-nopython.tar.gz into ~\/.vim\/ftplugin\/python.\r\n\r\n4. Make sure that pyflakes can be found by Python. This is by default done by\r\n   enhancing the PYTHONPATH environment variable in the pyflakes-nopython.vim\r\n   script, and on most systems that should be sufficient. \r\n\r\nLastly, it is presumed that python can be called as \"python\" in the system shell.\r\n\r\nIf you need to change the way the pyflakes-wrapper.py gets invoked, you can\r\nchange the s:python_call variable near the top of pyflakes-nopython.vim.","5":"1. Make sure your vimrc has:\r\n \r\n    filetype on            \" enables filetype detection\r\n    filetype plugin on     \" enables filetype specific plugins\r\n\r\n2. Download the latest version of pyflakes-vim-nopython.\r\n\r\n3. Extract pyflakes-nopython.tar.gz into ~\/.vim\/ftplugin\/python.\r\n\r\n4. Make sure that pyflakes can be found by Python. This is by default done by\r\n   enhancing the PYTHONPATH environment variable in the pyflakes-nopython.vim\r\n   script, and on most systems that should be sufficient. \r\n\r\nLastly, it is presumed that python can be called as \"python\" in the system shell.\r\n\r\nIf you need to change the way the pyflakes-wrapper.py gets invoked, you can\r\nchange the s:python_call variable near the top of pyflakes-nopython.vim.","first_name":"Hynek","6":"Hynek","last_name":"Urban","7":"Urban","releases":[{"0":"4374","vim_version":"7.0","1":"7.0","script_version":"0.2","2":"0.2","version_comment":"A path-related bug removed.","3":"A path-related bug removed.","package":"pyflakes-nopython.tar.gz","4":"pyflakes-nopython.tar.gz","src_id":"19266","5":"19266","creation_date":"1356948830","6":"1356948830"},{"0":"4374","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"pyflakes-nopython.tar.gz","4":"pyflakes-nopython.tar.gz","src_id":"19260","5":"19260","creation_date":"1356903769","6":"1356903769"}]},"4373":{"script_id":"4373","0":"4373","script_name":"sh.vim","1":"sh.vim","script_type":"indent","2":"indent","summary":"Indenting for Shell script","3":"Indenting for Shell script","description":"Indenting for Shell script.\r\n\r\nhttps:\/\/github.com\/Clavelito\/indent-sh.vim-0.0\r\n\r\nhttps:\/\/github.com\/Clavelito\/indent-sh.vim-0.0-legacy\r\n","4":"Indenting for Shell script.\r\n\r\nhttps:\/\/github.com\/Clavelito\/indent-sh.vim-0.0\r\n\r\nhttps:\/\/github.com\/Clavelito\/indent-sh.vim-0.0-legacy\r\n","install_details":"","5":"","first_name":"Clavelito","6":"Clavelito","last_name":"Cla","7":"Cla","releases":[{"0":"4373","vim_version":"7.4","1":"7.4","script_version":"-","2":"-","version_comment":"-","3":"-","package":"finish","4":"finish","src_id":"28051","5":"28051","creation_date":"1653133429","6":"1653133429"}]},"4372":{"script_id":"4372","0":"4372","script_name":"awk.vim","1":"awk.vim","script_type":"indent","2":"indent","summary":"Indenting for AWK script","3":"Indenting for AWK script","description":"Indenting for AWK script.\r\n\r\nhttps:\/\/github.com\/Clavelito\/indent-awk.vim\r\n\r\nhttps:\/\/github.com\/Clavelito\/indent-awk.vim-legacy\r\n","4":"Indenting for AWK script.\r\n\r\nhttps:\/\/github.com\/Clavelito\/indent-awk.vim\r\n\r\nhttps:\/\/github.com\/Clavelito\/indent-awk.vim-legacy\r\n","install_details":"","5":"","first_name":"Clavelito","6":"Clavelito","last_name":"Cla","7":"Cla","releases":[{"0":"4372","vim_version":"7.4","1":"7.4","script_version":"-","2":"-","version_comment":"-","3":"-","package":"empty","4":"empty","src_id":"28329","5":"28329","creation_date":"1671965559","6":"1671965559"}]},"4371":{"script_id":"4371","0":"4371","script_name":"Gentooish II","1":"Gentooish II","script_type":"color scheme","2":"color scheme","summary":"A modified version of Gentooish","3":"A modified version of Gentooish","description":"This script is a modified version of the Gentooish color scheme (vimscript #2474) which has no background color (so it can be used in a transparent terminal without being ugly) and some other changes.","4":"This script is a modified version of the Gentooish color scheme (vimscript #2474) which has no background color (so it can be used in a transparent terminal without being ugly) and some other changes.","install_details":"Download and copy the file to the ~\/.vim directory (sorry Windows users, I don\\'t know where your vim directory is - maybe you should consider switching to GNU\/Linux ?) then extract it to have the file named gentooishII.vim in the ~\/.vim\/colors directory. Now, you can load the colorscheme with the command \\':colorscheme gentooishII\\'.","5":"Download and copy the file to the ~\/.vim directory (sorry Windows users, I don\\'t know where your vim directory is - maybe you should consider switching to GNU\/Linux ?) then extract it to have the file named gentooishII.vim in the ~\/.vim\/colors directory. Now, you can load the colorscheme with the command \\':colorscheme gentooishII\\'.","first_name":"Pascal","6":"Pascal","last_name":"C.Plusplus","7":"C.Plusplus","releases":[{"0":"4371","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"gentooishII.tar.gz","4":"gentooishII.tar.gz","src_id":"19246","5":"19246","creation_date":"1356628775","6":"1356628775"}]},"4370":{"script_id":"4370","0":"4370","script_name":"visualMarks.vim","1":"visualMarks.vim","script_type":"utility","2":"utility","summary":"Show file marks visually","3":"Show file marks visually","description":"See latest version on github: https:\/\/github.com\/viaa\/VimPlugins\r\n\r\n\" Documentation\r\n    \" Name: visualMarks.vim\r\n    \" Version: 2.2\r\n    \" Description: Simple plugin to show file marks visually\r\n    \" Author: Alexandre Viau (alexandreviau@gmail.com)\r\n    \" Installation: Copy the plugin to the vim plugin directory.\r\n\r\n\" Usage:\r\n    \" Simply use vim marks like usually doing\r\n    \" ma, mb, mc...mz\r\n    \" or\r\n    \" mA, mB, mC...mZ\r\n    \" to marks positions in files.\r\n    \" NOTE: Only new marks are shown visually, this means that the marks already in the viminfo file will not be showned visually.\r\n    \" <tab>m To show the marks log file (in a split view)\r\n    \" f3 To show the marks log file (in current buffer)\r\n    \" <tab>f3 To show the marks log file (in a new tab)\r\n    \" <s-tab>f3 Open and grep the marks log file\r\n    \" <tab>g To grep the marks log file\r\n    \" All files opened in vim are added to the log file\r\n\r\n\" Todo:\r\n    \" 1. Load the marks from vim info and show them visually.\r\n    \" 2. Add mapping to automatically mark with next unused mark.\r\n    \" 3. Show warning if mark already used somewhere to prevent overwriting marks.\r\n    \" 4. s0 Add the possibility to select a log in the log file and then go to that position in the file\r\n    \" 5. s0 Le type the recherche ne devrait pas etre regex car s'il y a des [ ou ] alors la chaine n'est pas trouvee\r\n    \" 6. s0 Fix the mapping for the search for the line number it is not working now, everything I put is not working\r\n\r\n\" History:\r\n    \" 1.0 Initial release\r\n    \" 1.1 Removed the space in the mappings that where moving the cursor to the right after execution\r\n    \" 1.2 Change the file format for unix\r\n    \"     Added a fold to history\r\n    \" 1.3 Added 2 mappings (commented, to uncomment if you want to) to remap ` on ' and ' on `, because ` is more useful and ' more close\r\n    \" 1.4 Now the marks are saved to a log file so that it can be viewed to remember the previous marked positions. Also the line logged is copied to the clipboard. Later I will add the possibility go to the positions marked in the log file.\r\n    \" 2.0 I added a log file where each mark location is saved to it. And doing <tab>m will show the log file and allow to choose one of the previously logged location. Also, all files opened in vim are added to the log file, so it is like an history of files opened and locations in files. Tab<f3> will run grep to search the log file.\r\n    \" 2.1 I added and modified mappings\r\n    \" 2.2 I added 't' to open a file in another tab and I removed the '!' in the 2nd autocommand because it suppressed the first autocommand (thanks to Xaizek for that tip)\r\n","4":"See latest version on github: https:\/\/github.com\/viaa\/VimPlugins\r\n\r\n\" Documentation\r\n    \" Name: visualMarks.vim\r\n    \" Version: 2.2\r\n    \" Description: Simple plugin to show file marks visually\r\n    \" Author: Alexandre Viau (alexandreviau@gmail.com)\r\n    \" Installation: Copy the plugin to the vim plugin directory.\r\n\r\n\" Usage:\r\n    \" Simply use vim marks like usually doing\r\n    \" ma, mb, mc...mz\r\n    \" or\r\n    \" mA, mB, mC...mZ\r\n    \" to marks positions in files.\r\n    \" NOTE: Only new marks are shown visually, this means that the marks already in the viminfo file will not be showned visually.\r\n    \" <tab>m To show the marks log file (in a split view)\r\n    \" f3 To show the marks log file (in current buffer)\r\n    \" <tab>f3 To show the marks log file (in a new tab)\r\n    \" <s-tab>f3 Open and grep the marks log file\r\n    \" <tab>g To grep the marks log file\r\n    \" All files opened in vim are added to the log file\r\n\r\n\" Todo:\r\n    \" 1. Load the marks from vim info and show them visually.\r\n    \" 2. Add mapping to automatically mark with next unused mark.\r\n    \" 3. Show warning if mark already used somewhere to prevent overwriting marks.\r\n    \" 4. s0 Add the possibility to select a log in the log file and then go to that position in the file\r\n    \" 5. s0 Le type the recherche ne devrait pas etre regex car s'il y a des [ ou ] alors la chaine n'est pas trouvee\r\n    \" 6. s0 Fix the mapping for the search for the line number it is not working now, everything I put is not working\r\n\r\n\" History:\r\n    \" 1.0 Initial release\r\n    \" 1.1 Removed the space in the mappings that where moving the cursor to the right after execution\r\n    \" 1.2 Change the file format for unix\r\n    \"     Added a fold to history\r\n    \" 1.3 Added 2 mappings (commented, to uncomment if you want to) to remap ` on ' and ' on `, because ` is more useful and ' more close\r\n    \" 1.4 Now the marks are saved to a log file so that it can be viewed to remember the previous marked positions. Also the line logged is copied to the clipboard. Later I will add the possibility go to the positions marked in the log file.\r\n    \" 2.0 I added a log file where each mark location is saved to it. And doing <tab>m will show the log file and allow to choose one of the previously logged location. Also, all files opened in vim are added to the log file, so it is like an history of files opened and locations in files. Tab<f3> will run grep to search the log file.\r\n    \" 2.1 I added and modified mappings\r\n    \" 2.2 I added 't' to open a file in another tab and I removed the '!' in the 2nd autocommand because it suppressed the first autocommand (thanks to Xaizek for that tip)\r\n","install_details":"Installation: Copy the plugin to the vim plugin directory.","5":"Installation: Copy the plugin to the vim plugin directory.","first_name":"Alexandre","6":"Alexandre","last_name":"Viau","7":"Viau","releases":[{"0":"4370","vim_version":"7.0","1":"7.0","script_version":"2.4","2":"2.4","version_comment":"Some extra lines are added to the log every time, this is fixed \r\nI remove error message if search string not found.\r\n","3":"Some extra lines are added to the log every time, this is fixed \r\nI remove error message if search string not found.\r\n","package":"visualMarks.vim","4":"visualMarks.vim","src_id":"24139","5":"24139","creation_date":"1458953701","6":"1458953701"},{"0":"4370","vim_version":"7.0","1":"7.0","script_version":"2.2","2":"2.2","version_comment":"I added 't' to open a file in another tab and I removed the '!' in the 2nd autocommand because it suppressed the first autocommand (thanks to Xaizek for that tip)\r\n","3":"I added 't' to open a file in another tab and I removed the '!' in the 2nd autocommand because it suppressed the first autocommand (thanks to Xaizek for that tip)\r\n","package":"visualMarks.vim","4":"visualMarks.vim","src_id":"23642","5":"23642","creation_date":"1444014852","6":"1444014852"},{"0":"4370","vim_version":"7.0","1":"7.0","script_version":"2.1","2":"2.1","version_comment":"I added and modified mappings","3":"I added and modified mappings","package":"visualMarks.vim","4":"visualMarks.vim","src_id":"23608","5":"23608","creation_date":"1442762194","6":"1442762194"},{"0":"4370","vim_version":"7.0","1":"7.0","script_version":"2.0","2":"2.0","version_comment":"    \" 2.0 I added a log file where each mark location is saved to it. And doing <tab>m will show the log file and allow to choose one of the previously logged location. Also, all files opened in vim are added to the log file, so it is like an history of files opened and locations in files. Tab<f3> will run grep to search the log file.\r\n","3":"    \" 2.0 I added a log file where each mark location is saved to it. And doing <tab>m will show the log file and allow to choose one of the previously logged location. Also, all files opened in vim are added to the log file, so it is like an history of files opened and locations in files. Tab<f3> will run grep to search the log file.\r\n","package":"visualMarks.vim","4":"visualMarks.vim","src_id":"23586","5":"23586","creation_date":"1442024251","6":"1442024251"},{"0":"4370","vim_version":"7.0","1":"7.0","script_version":"2.0","2":"2.0","version_comment":"I added a log file where each mark location is saved to it. And doing <tab>m will show the log file and allow to choose one of the previously logged location. Also, all files opened in vim are added to the log file, so it is like an history of files opened and locations in files. Tab<f3> will run grep to search the log file.\r\n","3":"I added a log file where each mark location is saved to it. And doing <tab>m will show the log file and allow to choose one of the previously logged location. Also, all files opened in vim are added to the log file, so it is like an history of files opened and locations in files. Tab<f3> will run grep to search the log file.\r\n","package":"visualMarks.vim","4":"visualMarks.vim","src_id":"23585","5":"23585","creation_date":"1442024016","6":"1442024016"},{"0":"4370","vim_version":"7.0","1":"7.0","script_version":"1.1","2":"1.1","version_comment":"Removed the space in the mappings that where moving the cursor to the right after execution","3":"Removed the space in the mappings that where moving the cursor to the right after execution","package":"visualMarks.vim","4":"visualMarks.vim","src_id":"19243","5":"19243","creation_date":"1356590343","6":"1356590343"},{"0":"4370","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"visualMarks.vim","4":"visualMarks.vim","src_id":"19239","5":"19239","creation_date":"1356514382","6":"1356514382"}]},"4369":{"script_id":"4369","0":"4369","script_name":"linuxsty.vim","1":"linuxsty.vim","script_type":"indent","2":"indent","summary":"Vim plugin to respect the Linux kernel coding style","3":"Vim plugin to respect the Linux kernel coding style","description":"This plugin is meant to help you respecting the Linux kernel coding style, described at:\r\nhttp:\/\/www.kernel.org\/doc\/Documentation\/CodingStyle\r\n\r\nIt will automatically apply known rules to kernel related files, such as .c, .h, Kconfig and patch files.\r\nThe main rules are about indentation and syntax error highlighting (like exceeding 80 chars).\r\n\r\nIf you have any comments, fixes or requests, feel free to contact me or send me a patch.\r\nThe development also takes place at https:\/\/github.com\/vivien\/vim-linux-coding-style.","4":"This plugin is meant to help you respecting the Linux kernel coding style, described at:\r\nhttp:\/\/www.kernel.org\/doc\/Documentation\/CodingStyle\r\n\r\nIt will automatically apply known rules to kernel related files, such as .c, .h, Kconfig and patch files.\r\nThe main rules are about indentation and syntax error highlighting (like exceeding 80 chars).\r\n\r\nIf you have any comments, fixes or requests, feel free to contact me or send me a patch.\r\nThe development also takes place at https:\/\/github.com\/vivien\/vim-linux-coding-style.","install_details":"Just copy the linuxsty.vim file in your ~\/.vim\/plugin directory.","5":"Just copy the linuxsty.vim file in your ~\/.vim\/plugin directory.","first_name":"Vivien","6":"Vivien","last_name":"Didelot","7":"Didelot","releases":[{"0":"4369","vim_version":"7.0","1":"7.0","script_version":"0.4","2":"0.4","version_comment":"Don't highlight trailing whitespace in insert mode, add some kernel types, add an option to apply style conditionally as well as a LinuxCodingStyle command.","3":"Don't highlight trailing whitespace in insert mode, add some kernel types, add an option to apply style conditionally as well as a LinuxCodingStyle command.","package":"linuxsty.vim","4":"linuxsty.vim","src_id":"23732","5":"23732","creation_date":"1447455078","6":"1447455078"},{"0":"4369","vim_version":"7.0","1":"7.0","script_version":"0.3","2":"0.3","version_comment":"set softtabstop and align parameters with the opening parenthesis","3":"set softtabstop and align parameters with the opening parenthesis","package":"linuxsty.vim","4":"linuxsty.vim","src_id":"22457","5":"22457","creation_date":"1411657730","6":"1411657730"},{"0":"4369","vim_version":"7.0","1":"7.0","script_version":"0.2","2":"0.2","version_comment":"Fix syntax highlighting","3":"Fix syntax highlighting","package":"linuxsty.vim","4":"linuxsty.vim","src_id":"19997","5":"19997","creation_date":"1367441078","6":"1367441078"},{"0":"4369","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"linuxsty.vim","4":"linuxsty.vim","src_id":"19237","5":"19237","creation_date":"1356374500","6":"1356374500"}]},"4368":{"script_id":"4368","0":"4368","script_name":"vim-steam","1":"vim-steam","script_type":"utility","2":"utility","summary":"Launch Steam games from Vim","3":"Launch Steam games from Vim","description":"Currently only supports Windows Steam, Linux support is coming relatively soon.\r\n\r\ntl;dr - :Steam audio<Tab><CR>\r\n        Launches Audiosurf (if you have it installed)\r\n\r\nThis is a plugin to launch steam games without having to leave vim. To use\r\nit, you must have Steam installed (obvioulsy), and your Vim installation must\r\nsupport Ruby. To check whether your Vim supports ruby, execute\r\n    :ruby puts \"It works!\"\r\n\r\n(this should cause the message \"It works!\" to be displayed in the status bar).","4":"Currently only supports Windows Steam, Linux support is coming relatively soon.\r\n\r\ntl;dr - :Steam audio<Tab><CR>\r\n        Launches Audiosurf (if you have it installed)\r\n\r\nThis is a plugin to launch steam games without having to leave vim. To use\r\nit, you must have Steam installed (obvioulsy), and your Vim installation must\r\nsupport Ruby. To check whether your Vim supports ruby, execute\r\n    :ruby puts \"It works!\"\r\n\r\n(this should cause the message \"It works!\" to be displayed in the status bar).","install_details":"Extract into your runtimepath (%userprofile%\/vimfiles). Using pathogen is recommended.","5":"Extract into your runtimepath (%userprofile%\/vimfiles). Using pathogen is recommended.","first_name":"Raphael","6":"Raphael","last_name":"Robatsch","7":"Robatsch","releases":[{"0":"4368","vim_version":"7.0","1":"7.0","script_version":"0.1.0","2":"0.1.0","version_comment":"Initial upload","3":"Initial upload","package":"vim-steam.zip","4":"vim-steam.zip","src_id":"19235","5":"19235","creation_date":"1356363071","6":"1356363071"}]},"4367":{"script_id":"4367","0":"4367","script_name":"RGSS Script Editor Plugin","1":"RGSS Script Editor Plugin","script_type":"utility","2":"utility","summary":"An RGSS Editor Plugin ","3":"An RGSS Editor Plugin ","description":"RGSS is short for Ruby Game Scripting System, naming varied scripting system from a series of proprietary game making software, aka RPGMaker series from EnterBrain inc.\r\n\r\nThis plugin only runs under win32(as the script host does), and contains more than \"rgss.vim\", we need 'msvcrt-ruby18.dll' and 'zlib.so' and 'zlib1.dll' along, so I packed them all, with a gvim72.exe.\r\n\r\nYou can use this plugin to open \"Scripts.rxdata\"\/\"Scripts.rvdata\"\/\"Scripts.rvdata2\", to edit, and to save back. The plugin transparently  compresses\/uncompresses scripts.\r\n\r\nShortcuts:\r\n  C-F   : full text search\r\n  F12   : Run Game \r\n  C-F12: Call RPGMaker to open the project file(if any)\r\n  C-G C-R C-I: (it's some kinda emacs..) full text search with \"Input::\" or \"Input.\"\r\n  C-G C-R C-A: (it's some kinda emacs..) the same with above, but for Audio\r\n  C-G C-R C-G: (it's some kinda emacs..) the same for Graphics\r\n  C-H wb : just like ?class Window_Base\r\n  C-H sb : just like ?class Scene_Base\r\n  C-H int: just like ?class Interpreter or ?class Game_Interpreter\r\n  C-H snt : for Scene_Title\r\n  C-H snb: for Scene_Battle\r\n\r\n\r\n","4":"RGSS is short for Ruby Game Scripting System, naming varied scripting system from a series of proprietary game making software, aka RPGMaker series from EnterBrain inc.\r\n\r\nThis plugin only runs under win32(as the script host does), and contains more than \"rgss.vim\", we need 'msvcrt-ruby18.dll' and 'zlib.so' and 'zlib1.dll' along, so I packed them all, with a gvim72.exe.\r\n\r\nYou can use this plugin to open \"Scripts.rxdata\"\/\"Scripts.rvdata\"\/\"Scripts.rvdata2\", to edit, and to save back. The plugin transparently  compresses\/uncompresses scripts.\r\n\r\nShortcuts:\r\n  C-F   : full text search\r\n  F12   : Run Game \r\n  C-F12: Call RPGMaker to open the project file(if any)\r\n  C-G C-R C-I: (it's some kinda emacs..) full text search with \"Input::\" or \"Input.\"\r\n  C-G C-R C-A: (it's some kinda emacs..) the same with above, but for Audio\r\n  C-G C-R C-G: (it's some kinda emacs..) the same for Graphics\r\n  C-H wb : just like ?class Window_Base\r\n  C-H sb : just like ?class Scene_Base\r\n  C-H int: just like ?class Interpreter or ?class Game_Interpreter\r\n  C-H snt : for Scene_Title\r\n  C-H snb: for Scene_Battle\r\n\r\n\r\n","install_details":":source rgss.vim\r\n\r\nI use BufReadPost and BufWritePost to do load\/save work, so it's transparent for *.rxdata *.rvdata *.rvdata2","5":":source rgss.vim\r\n\r\nI use BufReadPost and BufWritePost to do load\/save work, so it's transparent for *.rxdata *.rvdata *.rvdata2","first_name":"Sanae","6":"Sanae","last_name":"Kotiya","7":"Kotiya","releases":[{"0":"4367","vim_version":"7.2","1":"7.2","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"gvimrgss.rar","4":"gvimrgss.rar","src_id":"19230","5":"19230","creation_date":"1356135317","6":"1356135317"}]},"4366":{"script_id":"4366","0":"4366","script_name":"mylocalrc","1":"mylocalrc","script_type":"utility","2":"utility","summary":"Fixed classical localrc","3":"Fixed classical localrc","description":"Like original localrc but with fixed error: infinity loop on Windows platform when reduce path to upper directory.","4":"Like original localrc but with fixed error: infinity loop on Windows platform when reduce path to upper directory.","install_details":"","5":"","first_name":"Paul","6":"Paul","last_name":"V","7":"V","releases":[{"0":"4366","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"localrc.vim","4":"localrc.vim","src_id":"19219","5":"19219","creation_date":"1356001309","6":"1356001309"}]},"4365":{"script_id":"4365","0":"4365","script_name":"trans.vim","1":"trans.vim","script_type":"utility","2":"utility","summary":"Easier translation in vim","3":"Easier translation in vim","description":":Title: trans.vim\r\n:Author: Rykka\r\n:Version: 1.0\r\n:Github: https:\/\/github.com\/Rykka\/trans.vim\r\n:Update: 2013-01-10\r\n\r\n=========\r\nTrans.vim\r\n=========\r\n\r\n**Trans.vim** makes translation in vim easier::\r\n\r\n    使得翻译在vim容易。\r\n    vim内で翻訳が容易になります。\r\n    rend la traduction dans vim facile.\r\n    macht die \u00c3\u009cbersetzung in vim einfacher.\r\n    ...\r\n\r\nUsage\r\n-----\r\n\r\n``:Trans``\r\n    Translate word.\r\n\r\n    ``:Trans hello`` will echo ``你好`` and set register ``@\"`` to 你好\r\n\r\n    ``<leader>tt`` will translate word under cursor or current visual selection.\r\n\r\n``:TransTo``\r\n    Translate word with input lang code.\r\n\r\n    ``<leader>to`` will translate to lang code with word under cursor or current visual selection.\r\n\r\n``:TransPo``\r\n    Translate po file\r\n\r\n    When in a po buffer, ``:TransPo`` will fill all empty msgstr with translated msgid.\r\n\r\n    if the msg is::\r\n\r\n        msgid \"show all\"\r\n        msgstr \"\"\r\n\r\n    it will be translate to::\r\n\r\n        msgid \"show all\"\r\n        msgstr \"全部显示\"\r\n\r\n","4":":Title: trans.vim\r\n:Author: Rykka\r\n:Version: 1.0\r\n:Github: https:\/\/github.com\/Rykka\/trans.vim\r\n:Update: 2013-01-10\r\n\r\n=========\r\nTrans.vim\r\n=========\r\n\r\n**Trans.vim** makes translation in vim easier::\r\n\r\n    使得翻译在vim容易。\r\n    vim内で翻訳が容易になります。\r\n    rend la traduction dans vim facile.\r\n    macht die \u00c3\u009cbersetzung in vim einfacher.\r\n    ...\r\n\r\nUsage\r\n-----\r\n\r\n``:Trans``\r\n    Translate word.\r\n\r\n    ``:Trans hello`` will echo ``你好`` and set register ``@\"`` to 你好\r\n\r\n    ``<leader>tt`` will translate word under cursor or current visual selection.\r\n\r\n``:TransTo``\r\n    Translate word with input lang code.\r\n\r\n    ``<leader>to`` will translate to lang code with word under cursor or current visual selection.\r\n\r\n``:TransPo``\r\n    Translate po file\r\n\r\n    When in a po buffer, ``:TransPo`` will fill all empty msgstr with translated msgid.\r\n\r\n    if the msg is::\r\n\r\n        msgid \"show all\"\r\n        msgstr \"\"\r\n\r\n    it will be translate to::\r\n\r\n        msgid \"show all\"\r\n        msgstr \"全部显示\"\r\n\r\n","install_details":"Installation\r\n------------\r\n\r\nRequirment: \r\n\r\n    - Vim compiled with python. (or webapi.vim_)\r\n\r\nInstall:\r\n\r\n    - Vundle_:\r\n\r\n      In your Vimrc::\r\n      \r\n       Bundle 'Rykka\/trans.vim'\r\n       \" for no python version\r\n       \" Bundle 'mattn\/webapi-vim'\r\n      \r\n      Then use ``:BundleInstall`` to install. \r\n\r\n","5":"Installation\r\n------------\r\n\r\nRequirment: \r\n\r\n    - Vim compiled with python. (or webapi.vim_)\r\n\r\nInstall:\r\n\r\n    - Vundle_:\r\n\r\n      In your Vimrc::\r\n      \r\n       Bundle 'Rykka\/trans.vim'\r\n       \" for no python version\r\n       \" Bundle 'mattn\/webapi-vim'\r\n      \r\n      Then use ``:BundleInstall`` to install. \r\n\r\n","first_name":"Rykka","6":"Rykka","last_name":"f","7":"f","releases":[{"0":"4365","vim_version":"7.0","1":"7.0","script_version":"1.0.1","2":"1.0.1","version_comment":" \t- py: fix missing vcmd\/veval","3":" \t- py: fix missing vcmd\/veval","package":"trans.vim-1.0.1.zip","4":"trans.vim-1.0.1.zip","src_id":"19345","5":"19345","creation_date":"1357880798","6":"1357880798"},{"0":"4365","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"- Add 'Bing' oauth\r\n- Add 'Youdao' and 'Baidu'\r\n- Add ':TransTo'","3":"- Add 'Bing' oauth\r\n- Add 'Youdao' and 'Baidu'\r\n- Add ':TransTo'","package":"trans.vim-1.0.zip","4":"trans.vim-1.0.zip","src_id":"19339","5":"19339","creation_date":"1357754460","6":"1357754460"},{"0":"4365","vim_version":"7.0","1":"7.0","script_version":"0.92","2":"0.92","version_comment":"fix multiline translation","3":"fix multiline translation","package":"trans.vim-0.92.zip","4":"trans.vim-0.92.zip","src_id":"19222","5":"19222","creation_date":"1356078348","6":"1356078348"},{"0":"4365","vim_version":"7.0","1":"7.0","script_version":"0.91","2":"0.91","version_comment":"fix the mapping","3":"fix the mapping","package":"trans.vim-0.91.zip","4":"trans.vim-0.91.zip","src_id":"19216","5":"19216","creation_date":"1355988302","6":"1355988302"}]},"4364":{"script_id":"4364","0":"4364","script_name":"ExplainPattern","1":"ExplainPattern","script_type":"utility","2":"utility","summary":"Give detailed help on a given regexp pattern.","3":"Give detailed help on a given regexp pattern.","description":"Continued here: https:\/\/github.com\/Houl\/ExplainPattern-vim (2017 Aug 06)\r\n\r\n:ExplainPattern {pattern}               or\r\n:ExplainPattern {register}\r\n\r\n        parse the given Vim {pattern} and print a line of help\r\n        (with color) for each found pattern item.  Nested\r\n        items get extra indent.\r\n\r\n        A single-char argument is used as {register} argument:\r\n                \/\texplain the last search pattern\r\n                *\texplain pattern from the clipboard\r\n                a\texplain pattern from register a\r\n\r\n\r\nExample:  :ExplainPattern *\r\n\r\nRegister: *\r\nPattern: \\C^\\%(\\\\\\%(@<.\\|%[dxouU[(^$V#<>]\\=\\|z[1-9se(]\\|@[>=!]\\|_[[^$.]\\=\\|.\\)\\|.\\)\r\n  \\C         match case while matching the pattern\r\n  ^          match at start of line (or string)\r\n  \\%(        start of non-capturing group\r\n  |   \\\\         literal string (1 atom(s))\r\n  |   \\%(        start of non-capturing group\r\n  |   |   @<         literal string (2 atom(s))\r\n  |   |   .          match any character\r\n  |   | \\|         OR branch\r\n  |   |   %          literal string (1 atom(s))\r\n  |   |   [dxouU[(^$V#<>] collection\r\n  |   |   \\=         (multi) zero or one of the preceding atom\r\n  |   | \\|         OR branch\r\n  |   |   z          literal string (1 atom(s))\r\n  |   |   [1-9se(]   collection\r\n  |   | \\|         OR branch\r\n  |   |   @          literal string (1 atom(s))\r\n  |   |   [>=!]      collection\r\n  |   | \\|         OR branch\r\n  |   |   _          literal string (1 atom(s))\r\n  |   |   [[^$.]     collection\r\n  |   |   \\=         (multi) zero or one of the preceding atom\r\n  |   | \\|         OR branch\r\n  |   |   .          match any character\r\n  |   \\)         end of group\r\n  | \\|         OR branch\r\n  |   .          match any character\r\n  \\)         end of group\r\n\r\n2013 Jan 17","4":"Continued here: https:\/\/github.com\/Houl\/ExplainPattern-vim (2017 Aug 06)\r\n\r\n:ExplainPattern {pattern}               or\r\n:ExplainPattern {register}\r\n\r\n        parse the given Vim {pattern} and print a line of help\r\n        (with color) for each found pattern item.  Nested\r\n        items get extra indent.\r\n\r\n        A single-char argument is used as {register} argument:\r\n                \/\texplain the last search pattern\r\n                *\texplain pattern from the clipboard\r\n                a\texplain pattern from register a\r\n\r\n\r\nExample:  :ExplainPattern *\r\n\r\nRegister: *\r\nPattern: \\C^\\%(\\\\\\%(@<.\\|%[dxouU[(^$V#<>]\\=\\|z[1-9se(]\\|@[>=!]\\|_[[^$.]\\=\\|.\\)\\|.\\)\r\n  \\C         match case while matching the pattern\r\n  ^          match at start of line (or string)\r\n  \\%(        start of non-capturing group\r\n  |   \\\\         literal string (1 atom(s))\r\n  |   \\%(        start of non-capturing group\r\n  |   |   @<         literal string (2 atom(s))\r\n  |   |   .          match any character\r\n  |   | \\|         OR branch\r\n  |   |   %          literal string (1 atom(s))\r\n  |   |   [dxouU[(^$V#<>] collection\r\n  |   |   \\=         (multi) zero or one of the preceding atom\r\n  |   | \\|         OR branch\r\n  |   |   z          literal string (1 atom(s))\r\n  |   |   [1-9se(]   collection\r\n  |   | \\|         OR branch\r\n  |   |   @          literal string (1 atom(s))\r\n  |   |   [>=!]      collection\r\n  |   | \\|         OR branch\r\n  |   |   _          literal string (1 atom(s))\r\n  |   |   [[^$.]     collection\r\n  |   |   \\=         (multi) zero or one of the preceding atom\r\n  |   | \\|         OR branch\r\n  |   |   .          match any character\r\n  |   \\)         end of group\r\n  | \\|         OR branch\r\n  |   .          match any character\r\n  \\)         end of group\r\n\r\n2013 Jan 17","install_details":"This is a vimball archive, edit it in vim, do  :so %   , then restart.","5":"This is a vimball archive, edit it in vim, do  :so %   , then restart.","first_name":"Andy","6":"Andy","last_name":"Wokula","7":"Wokula","releases":[{"0":"4364","vim_version":"7.0","1":"7.0","script_version":"0.5","2":"0.5","version_comment":"Bug fixes (accept more patterns): `\\z(', `\\z1', ..., `[foo'; added cases where `^', `*', `$' become literal; `[=a=]` in collections, a few more.","3":"Bug fixes (accept more patterns): `\\z(', `\\z1', ..., `[foo'; added cases where `^', `*', `$' become literal; `[=a=]` in collections, a few more.","package":"explainpat_0.5.vmb","4":"explainpat_0.5.vmb","src_id":"19613","5":"19613","creation_date":"1362866827","6":"1362866827"},{"0":"4364","vim_version":"7.0","1":"7.0","script_version":"0.2","2":"0.2","version_comment":"include suggestions from vim_use","3":"include suggestions from vim_use","package":"explainpat_0.2.vmb","4":"explainpat_0.2.vmb","src_id":"19214","5":"19214","creation_date":"1355955145","6":"1355955145"},{"0":"4364","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Uploaded again, this time not gzipped (vimball anyway keeps an unpacked version on disk)","3":"Uploaded again, this time not gzipped (vimball anyway keeps an unpacked version on disk)","package":"explainpat_0.1.vmb","4":"explainpat_0.1.vmb","src_id":"19210","5":"19210","creation_date":"1355923999","6":"1355923999"}]},"4363":{"script_id":"4363","0":"4363","script_name":"vim-bind","1":"vim-bind","script_type":"syntax","2":"syntax","summary":"bindzone syntax highlight","3":"bindzone syntax highlight","description":"The stock bind zone syntax highlight is largely outdated, here's an updated one.\r\n\r\nPlease do file issues on github : https:\/\/github.com\/Absolight\/vim-bind","4":"The stock bind zone syntax highlight is largely outdated, here's an updated one.\r\n\r\nPlease do file issues on github : https:\/\/github.com\/Absolight\/vim-bind","install_details":"","5":"","first_name":"Mathieu","6":"Mathieu","last_name":"Arnold","7":"Arnold","releases":[{"0":"4363","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"First release.","3":"First release.","package":"vim-bind-1.0.zip","4":"vim-bind-1.0.zip","src_id":"19200","5":"19200","creation_date":"1355835100","6":"1355835100"}]},"4361":{"script_id":"4361","0":"4361","script_name":"incbool.vim","1":"incbool.vim","script_type":"utility","2":"utility","summary":"Toggle boolean values with C-a an C-x","3":"Toggle boolean values with C-a an C-x","description":"Script home is on the github: https:\/\/github.com\/can3p\/incbool.vim\r\n\r\nScript modifies original behavior of the <C-a> and <C-x> mapping and allows to\r\nincrease and decrease boolean values. It also take into account the register of\r\nthe word, so this how the words will be changed:\r\n\r\ntrue <-> false\r\nTrue <-> False\r\nTRUE <-> FALSE ","4":"Script home is on the github: https:\/\/github.com\/can3p\/incbool.vim\r\n\r\nScript modifies original behavior of the <C-a> and <C-x> mapping and allows to\r\nincrease and decrease boolean values. It also take into account the register of\r\nthe word, so this how the words will be changed:\r\n\r\ntrue <-> false\r\nTrue <-> False\r\nTRUE <-> FALSE ","install_details":"Use vundle and github repo or just unzip the archive in the .vim folder","5":"Use vundle and github repo or just unzip the archive in the .vim folder","first_name":"Dmitry","6":"Dmitry","last_name":"Petrov","7":"Petrov","releases":[{"0":"4361","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"incbool.vim-0.1.zip","4":"incbool.vim-0.1.zip","src_id":"19195","5":"19195","creation_date":"1355775515","6":"1355775515"}]},"4360":{"script_id":"4360","0":"4360","script_name":"vimExplorer","1":"vimExplorer","script_type":"utility","2":"utility","summary":"File manager. Explore directories quickly and operate on files.","3":"File manager. Explore directories quickly and operate on files.","description":"See latest version on github: https:\/\/github.com\/viaa\/VimPlugins\r\n\r\nDocumentation \r\n\r\nName: vimExplorer.vim\r\nVersion: 2.5.3\r\nDescription: File manager. Explore directories quickly and operate on files.\r\nAuthor: Alexandre Viau (alexandreviau@gmail.com)\r\nWebsite: The latest version is found on \"vim.org\"\r\n\r\nAbout  \r\n\r\nI would like if vimExplorer would become an open source, cross-platform, text and keyboard oriented filemanager alternative. It is now in that direction since version 2.0 vimExplorer is able to open, copy, move, delete, delete, run files and more. Using vim and its amazing text editing power and keyboard mapping habilities as an interface and numerous powerful shell commands for file management makes vimExplorer the ideal solution for fast and flexible file editing and management. I put a lot of thinking to make it as much comfortable, fast and easy to use as possible. With vimExplorer I try also to solve the difficulties (if I may say so) of file system access from vim (to find files, open them for edition, etc). Also to be able to do file management, grepping and searching from within vim without having to use an external program or shell could potentially increase productivity.\r\n\r\nInstallation \r\n\r\n- Copy the plugin to the vim plugin directory. \r\n- If you use the plugin in Windows, you will have to change the value of the \"g:VeLsCmdPath\" to that of the path where your ls command is located. Search for the variable using: \/let g:VeLsCmdPath (You may also set that variable to 'ls' simply and set the path to the executable using the system %path% variable)\r\n- There are mappings (<space>9 and <space>0) to switch between the ls command from \"UnxUtils\" or the ls command from \"Cygwin\". So you may use both like I do by setting a path for each of these variables \"g:VeLsCmdPathU\" and \"g:VeLsCmdPathC\". I personally use the ls command from \"UnxUtils\" for speed, and the ls command from \"Cygwin\" to display russian alphabet. I use these mappings to switch from one to another depending if I need they are file and directory names that are written with the russian alphabet.\r\n- If you use the plugin in Windows, you will have to change also the value of the \"g:VeGrepCmdPath\" to that of the path where your grep command is located. Search for the variable using: \/let g:VeGrepCmdPath (You may also set that variable to 'grep' simply and set the path to the executable using the system %path% variable)\r\n- vimExplorer requires depends on the \"basicXmlParser.vim\" plugin which is included at the top of this file to ensure compatibility and presence of the plugin.\r\n\r\nUsage \r\n\r\nMappings: \r\n\r\nOpen vimExplorer using the last accessed path \r\n\r\n<leader>ve Start vimExplorer in the current window\r\n<leader>vs Start vimExplorer in a new split (horizontal) window\r\n<leader>vv Start vimExplorer in a new vsplit (vertical) window\r\n<leader>vt Start vimExplorer in a new tab\r\n\r\n<leader>vd Start vimExplorer in double vertical panes (for file copy, move etc)\r\n<leader>vh Start vimExplorer in double horizontal panes (for file copy, move etc)\r\n<leader>vf Start vimExplorer with four panes (for file copy, move etc)\r\n<leader>vx Start vimExplorer with six panes (for file copy, move etc)\r\n\r\nNOTE: 1. There are other suggested mappings commented out where the preceding mappings are defined, to open vimExplorer in one key press. See \"other suggested mappings\" sections below in this documentation section.\r\n      2. You may create the number of panes vertical or horizontal you want by mixing the VimExplorerT, VimExplorerV and VimExplorerS in a command or a mapping you would add yourself to your vimrc. See the <leader>vd and <leader>vh mappings in this plugin as examples, these only use a combination of VimExplorerT and VimExplorerV or VimExplorers to create the panes. You may even have 4 or 6 panes even, as much as you need.\r\n\r\nOpen vimExplorer using a the current file's path \r\n\r\n<leader>VE Start vimExplorer in the current window\r\n<leader>VS Start vimExplorer in a new split (horizontal) window\r\n<leader>VV Start vimExplorer in a new vsplit (vertical) window\r\n<leader>VT Start vimExplorer in a new tab\r\n\r\nNOTE: With all directories, files and links (underlined text), all actions like <space>t (open in new tab), <space>v (open in vertical split), <space>s (open in split), <space>r (run), work with them. See \"File operations\"  section below for more of these actions and their definitions.\r\n\r\nDirectory browsing \r\n\r\n<space>l Open the selected directory or file (works also in the history bar and favorites bar at the top of the buffer and for grep results)\r\n<space>h Go to the parent directory\r\n\r\n<s-j> (shift-j) To open the next file in the preview window. You may hold the shift key then press many times j to preview one file after another. It will open the file and then pass to the next file, I found it better than to pass to the next file and open it because if you position the cursor on a file you do shift-j instead to have to do <enter> of <space>l to open the file then shift-j for next files.\r\n<s-k> (shift-k) Go open the previous file in the preview window. You may hold the shift key then press many times k to preview one file after another. It will open the file and then pass to the previous file, I found it better than to pass to the previous file and open it because if you position the cursor on a file you do shift-k instead to have to do <enter> of <space>l to open the file then shift-k for previous files.\r\n\r\n<space>a Go to the path at the top of the buffer to edit it. Press <space>l or <enter> (in normal mode) to go the that path once edited.\r\n<space>f Set filter to show only certain files\r\n<space>F Remove the filter and show all files\r\n<space>L Open the selected directory recursively\r\n<space>o Reload directory\r\n<space>p Copy path\r\n<space>P Show current path in different formats and to the clipboard\r\n<space>x Open directory in external file manager\r\n<space>X Open current directory with the gvim \"browse\" command to open a file in the current buffer\r\n<space>z Return to last path visited (toggle current and last)\r\n<space>9 If Windows is used to change the ls command for \"UnxUtils\" ls command\r\n<space>0 If Windows is used to Change the ls command for \"Cygwin\" ls command\r\nNOTE: 1. You may write or edit a path manually in the \"Path: \" bar at the top of the buffer. Once the path is entered, press <space>l or <enter> to go to that path.\r\n      2. You may change the path of the external file manager in the <space>x mapping.\r\n      3. Some file operations mappings work with the directories as well for example: <space>t to open in new tab, <space>x to open in external filemanager (check the \"File operations\" below)\r\n\r\nBrowsing history \r\n\r\n<space>l or <enter> Go to one of the history path shown at the top of the buffer, put cursor on one of the paths and execute this mapping.\r\n<space>; Go to the history list (then do ; or , (from the vim 'f' command) to move forward and backward from one path to another, then when on the desired path, do <space>l or <enter> to goto the directory.)\r\n<space>, Go to the end of the history list (then do ; or , (from the vim 'f' command) to move forward and backward from one path to another, then when on the desired path, do <space>, to goto the directory.)\r\n<space>H Delete the browsing history\r\nNOTE: 1. You may edit the history bar at the top of the buffer, you may add, remove or move paths on this line, it will be saved automatically when changing directory or doing <space>s to save the configuration or when vim quits if the cursor is in a vimExplorer window.\r\n      2. The maximum length of the history bar may be changed by setting the \"s:HistoryMaxLength\" variable\r\n      3. You may use the \"set wrap\" command to see all history if the list is long\r\n      4. Some file operations mappings work with the links in these history links for example: <space>t to open in new tab, <space>r to run, <space>x to open in external filemanager (check the \"File operations\" below)\r\n\r\nDirectory bookmarks \r\n\r\nma to mz Directory marks like similar to marks in vim using the m key but to mark directories instead of positions in files and ' or ` or ; to return to that directory. The maps are automatically activated on a directory listing. For example, press mw to mark the c:\\windows directory, then do 'w (or `w or ;w) to return to that directory. All letters may be used from a to z, A to Z and 0 to 9. Press '' to view a list of all the bookmarked directories sorted by mark, or press ;; to view the same list but sorted by paths. When '' or ;; is pressed, the list is shown and a mark is asked as input to goto to its directory, this is another way that marks are used.\r\nm0 to m9 Same like ma to mz but using numbers as marks\r\n'a to 'z or `a to `z To return to the directories marked by ma to mz  \r\n'0 to '9 or `0 to `9 Same like ma to mz but using numbers as marks\r\n<space>' Show all marked directories sorted by marks\r\n<space>` Show all marked directories sorted by marks\r\n<space>[ Show all marked directories sorted by directories\r\n\r\nDirectory favorites \r\n\r\n<space>b Add the path to the favorites bar\r\n<space>B Add the full path with the filename to the favorites bar (this allows to add \"shortcuts\" to files to run a file or to open a file)\r\n<space>: Go to the favorites list (then do ; or , (from the vim 'f' command) to move forward and backward from one path to another, then when on the desired path, do <space>l or <enter>to goto the directory.)\r\nNOTE: 1. The favorites bar is another way of bookmarking directories. It is independant from the directory bookmarks (marks) showned above. It is a feature on its own.\r\n      2. You may edit the favorites bar at the top of the buffer, you may add, remove or move paths on this line, it will be saved automatically when changing directory or doing <space>s to save the configuration or when vim quits if the cursor is in a vimExplorer window.\r\n      3. Some file operations mappings work with the links in these favorites links for example: <space>t to open in new tab, <space>r to run, <space>x to open in external filemanager (check the \"File operations\" below)\r\n      4. The favorites bar dosen't have a mapping to delete the bar like the history have <space>H. To delete the favorites bar, simply delete all the links from it and save the configuration (<space>s)\r\n\r\nDirectory file grep \r\n\r\n<space>g Grep current file\/directory or the selected files\/directories\r\nThe grep results appear after the file listing in the same buffer. You may position the cursor on a line in these results and press <space>l or <enter> to view it in the preview window.\r\nNOTE: 1. Some file operations mappings work with the links in these grep results links for example: <space>t to open in new tab, <space>r to run, <space>x to open in external filemanager (check the \"File operations\" below)\r\n\r\nDirectory file search \r\n\r\n<space>L  To search files in a directory, open the selected directory recursively using <space>L and then search the buffer for the file using vim's \"\/\" command or use vimgrep.\r\nNOTE: 1. Some file operations mappings work with the files and directories in these recursive listings for example: <space>t to open in new tab, <space>r to run, <space>x to open in external filemanager (check the \"File operations\" below)\r\n\r\nDirectory sorting \r\n\r\n<space>1 Sort by name\r\n<space>2 Sort by type\r\n<space>3 Sort by size\r\n<space>4 Sort by date\r\n\r\nFile operations \r\n\r\n<space>c Clone file\r\n<space>d New directory\r\n<space>D or <delete> Delete current file\/directory or selected files\/directories\r\n<space>l or <enter> Open the selected item in preview window\r\n<space>n New file\r\n<space>r Run the current file or the selected files\r\n<space>R Rename file\r\n<space>s or <enter> Open file in preview window\r\n<space>t Open current file\/directory or selected files\/directories in new tab\r\n<space>v Open file in vertical split window\r\n\r\nFile selection operations \r\n\r\nOperation that can be done on a group of selected files\/directories include for now: copy, move, delete, grep, open in new tab, run and a user defined command that a user can use to put the command he wants inside to execute on the selected files. \r\n\r\n<esc> Remove file selection\r\n<c-s> Toggle select\/deselect selected the file or files (if there are files selected in visual mode) to do an operation on it like copy, move, delete, grep etc\r\n<c-c> Copy files, toggle select\/deselect the file or files (if there are files selected in visual mode) and select the copy command as the command to run \r\n<c-x> Move files, toggle select\/deselect the file or files (if there are files selected in visual mode) and select the move command as the command to run \r\n<c-v> Paste files, RunCommand in the target directory (usually a paste command which is the copy or move itself). The target directory is simply a directory where the user goes after (in another window or in the same window).\r\n<c-u> Run the user defined command (the user may set a command to it to run on the selected files) See section \"How to run user-defined commands on selected files\"\r\n\r\nNOTE: 1. Set the variable \"s:ShowLastCommands\" to 1 if you want to see the last commands executed (appended at the end of the buffer after the file listing)\r\n      2. Since <c-v> is used to paste, use <c-q> to do a block selection in a vimExplorer window.\r\n\r\nShell operations \r\n\r\n<space><esc> Execute a command and insert its output in the buffer\r\n<space>C Open directory in shell\r\n\r\nConfiguration file operations \r\n\r\n<space>O Reload configuration from file (useful if the .config.vim file was edited manually and you want to reload it in the vimExplorer window that is currently opened)\r\n<space>S Save configuration file\r\n\r\nNOTE: 1. The configuration is automatically loaded when vim starts, and it is automatically closed when vim quits.\r\n      2. You may open the configuration file for edition, and after editing and saving the file, return to a vimExplorer window and do <space>O to reload the new configuration file.\r\n\r\nTo debug \r\n\r\n<leader>des To inspect the content of the g:VeSelectedFile object\r\n<leader>dec To inspect the content of the g:VeCommands object\r\n<leader>der To inspect the content of the g:VeCommandToRun object\r\n\r\nCommands: \r\n\r\nOpen vimExplorer using the last accessed path \r\n\r\nVimExplorerB Start vimExplorer in the current window\r\nVimExplorerS Start vimExplorer in a new split (horizontal) window\r\nVimExplorerV Start vimExplorer in a new vsplit (vertical) window\r\nVimExplorerT Start vimExplorer in a new tab\r\n\r\nOpen vimExplorer using a the current file's path \r\n\r\nVimExplorerBF Start vimExplorer in the current window\r\nVimExplorerSF Start vimExplorer in a new split (horizontal) window\r\nVimExplorerVF Start vimExplorer in a new vsplit (vertical) window\r\nVimExplorerTF Start vimExplorer in a new tab\r\n\r\nOpen vimExplorer using a path specified on the command line \r\n\r\nVimExplorerBP Start vimExplorer in the current window\r\nVimExplorerSP Start vimExplorer in a new split (horizontal) window\r\nVimExplorerVP Start vimExplorer in a new vsplit (vertical) window\r\nVimExplorerTP Start vimExplorer in a new tab\r\n\r\nHow to get the current path and filename for usage in external scripts \r\n\r\nIf you want to get the current path and filename from vimExplorer first cal the \"g:VeGetPath()\" then use the following variables as needed.\r\nThese paths variables may be used for example if you do new mappings or some kind of menu to execute operations on the current file or directory.\r\nNote that the current path and filename are copied when leaving the plugin or any file window for another window so the following variables could be used from there.\r\nIf you don't want to copy the path when leaving any file window, but just when leaving a vimExplorer window, set the variable \"s:GetPathOnLeaveAlways\" to 0\r\n\r\ng:VePaths.FileName  \r\ng:VePaths.FileNameQ  \r\ng:VePaths.FileName2Q  \r\ng:VePaths.PathS  \r\ng:VePaths.PathSQ  \r\ng:VePaths.PathS2Q  \r\ng:VePaths.FullPathS  \r\ng:VePaths.FullPathSQ  \r\ng:VePaths.FullPathS2Q  \r\ng:VePaths.PathB  \r\ng:VePaths.PathBQ  \r\ng:VePaths.PathB2Q  \r\ng:VePaths.FullPathB  \r\ng:VePaths.FullPathBQ  \r\ng:VePaths.FullPathB2Q  \r\ng:VePaths.Path2B  \r\ng:VePaths.Path2BQ  \r\ng:VePaths.Path2B2Q  \r\ng:VePaths.FullPath2B  \r\ng:VePaths.FullPath2BQ  \r\ng:VePaths.FullPath2B2Q  \r\ng:VePaths.DosFileName  \r\ng:VePaths.DosFileNameQ  \r\ng:VePaths.DosFileName2Q  \r\ng:VePaths.DosPathS  \r\ng:VePaths.DosPathSQ  \r\ng:VePaths.DosPathS2Q  \r\ng:VePaths.DosFullPathS  \r\ng:VePaths.DosFullPathSQ  \r\ng:VePaths.DosFullPathS2Q  \r\ng:VePaths.DosPathB  \r\ng:VePaths.DosPathBQ  \r\ng:VePaths.DosPathB2Q  \r\ng:VePaths.DosFullPathB  \r\ng:VePaths.DosFullPathBQ  \r\ng:VePaths.DosFullPathB2Q  \r\ng:VePaths.DosPath2B  \r\ng:VePaths.DosPath2BQ  \r\ng:VePaths.DosPath2B2Q  \r\ng:VePaths.DosFullPath2B  \r\ng:VePaths.DosFullPath2BQ  \r\ng:VePaths.DosFullPath2B2Q  \r\n\r\nHow to open vimExplorer from another script \r\n\r\nUse the VimExplorerE, VimExplorerT, etc and\/or other VimExplorer commands to start the plugin.\r\n\r\nHow to change the colors of the display \r\n\r\nFind the g:VeLs() function in the code and then find the comment section \"Set colors on specific items in the window\", there you'll find the highlight groups set as the first arguments of the matchadd() function. For example where there is \"cal matchadd('htmlLink', '\\[\\zs.\\{-}\\ze\\]')\" you may change \"htmlLink\" for some other highlight group of you choice.\r\n\r\nHow to run user-defined commands on selected files \r\n\r\nThis is useful if you want to command in batch on all the selected files.\r\nUse the \"ctrl-s\" mapping with or without visual selection to select files.\r\nThe command placed in \"Step1\" contains commands that are run on files, the command placed in \"Step2\" contains commands that are run on directories.\r\nYou may used all the placeholders found in the g:VeGethPath() function in your commands.\r\nThe values \"let g:VeCommands.User.Step1.Command.Value\" and\/or \"let g:VeCommands.User.Step2.Command.Value\" have to be initialized to a command or to '' (empty) before to run them using \":VimExplorerUC\" or the \"ctrl-u\" mapping. If initialize to '' (empty) then no command is ran, so if you don't want for example to run a command on directories do this on \"Step2\": let g:VeCommands.User.Step2.Command.Value = ''\r\nHere some sample user commands, run the commands using the \":VimExplorerUC\" command on the command-line or from a script, or use the \"ctrl-u\" mapping.\r\n\r\n\" Show full paths of selected files and directories and their \"PathSource\" (file or directory)\r\nlet g:VeCommands.User.Step1.Command.Value = 'echo \"%SelFullPathS% %SelPathSource%\"'\r\nlet g:VeCommands.User.Step2.Command.Value = 'echo \"%SelFullPathS% %SelPathSource%\"'\r\n\r\n\" Copy full paths of selected files and directories to the clipboard\r\nlet g:VeCommands.User.Step1.Command.Value = 'echo \"%SelFullPathS%\" | let @* = \"%SelFullPathS%\"'\r\nlet g:VeCommands.User.Step2.Command.Value = 'echo \"%SelFullPathS%\" | let @* = \"%SelFullPathS%\"'\r\n\r\n\" Rename files (Step1) (append '.txt' to selected files) (In Windows use \"!ren\", in Linux \"!mv\")\r\nlet g:VeCommands.User.Step1.Command.Value = 'cal system(\"ren \\\"%SelFileName%\\\" \\\"%SelFileName%.txt\\\"\")'\r\n\" Rename directories (Step2) (append '_bkp' to selected directories) (In Windows use \"!ren\", in Linux \"!mv\")\r\nlet g:VeCommands.User.Step2.Command.Value = 'cal system(\"ren \\\"%SelFileName%\\\" \\\"%SelFileName%_bkp\\\"\")'\r\n\r\nOther suggested mappings \r\n\r\nOther suggested mappings to open vimExplorer in one key press (to put in this plugin or in your vimrc) \r\nnmap <f2> :VimExplorerS<cr>\r\nnmap <f3> :VimExplorerV<cr>\r\nnmap <f4> :VimExplorerT<cr>\r\nnmap <f5> :VimExplorerE<cr>\r\nnmap <home> :VimExplorerS<cr>\r\nnmap <PageUp> :VimExplorerV<cr>\r\nnmap <PageDown> :VimExplorerT<cr>\r\nnmap <End> :VimExplorerE<cr>\r\n\" 2 vertical windows\r\nnmap <s-f2> :exe 'VimExplorerT' \\| exe 'VimExplorerV'<cr>\r\nnmap <s-home> :exe 'VimExplorerT' \\| exe 'VimExplorerV'<cr>\r\n\" 4 windows\r\nnmap <s-f3> :exe 'VimExplorerT' \\| exe 'VimExplorerV' \\| exe 'VimExplorerS' \\| wincmd l \\| exe 'VimExplorerS'<cr>\r\nnmap <s-PageUp> :exe 'VimExplorerT' \\| exe 'VimExplorerV' \\| exe 'VimExplorerS' \\| wincmd l \\| exe 'VimExplorerS'<cr>\r\n\" 6 windows\r\nnmap <s-f4> :exe 'VimExplorerT' \\| exe 'VimExplorerV' \\| exe 'VimExplorerS' \\| exe 'VimExplorerS' \\| wincmd l \\| exe 'VimExplorerS' \\| exe 'VimExplorerS'<cr>\r\nnmap <s-PageDown> :exe 'VimExplorerT' \\| exe 'VimExplorerV' \\| exe 'VimExplorerS' \\| exe 'VimExplorerS' \\| wincmd l \\| exe 'VimExplorerS' \\| exe 'VimExplorerS'<cr>\r\n\r\nTips \r\n- You may use the \"set wrap\" command to see all history if the list is long.\r\n- To search files in a directory, open the selected directory recursively using <space>L and then search the buffer for the file using vim's \"\/\" command or use vimgrep.\r\n- I use also the MRU plugin in combination with vimExplorer to have a list of the last opened files, I find it extremely useful for vim editing.\r\n- To go quickly to the favorites bar, do <space>; or <space>, which brings the cursor on the history bar, then do \"j\" to go down one line, then press \";\" or \",\" to go forward and backward on the favorites bar.\r\n- You may search the history and favorites using the \"\/\" or the \"?\" command, especially the \"?\" command as the links are at the top of the file.\r\n\r\nTodo \r\nCode organization \r\n- Check if g:VeFileName occurences really could not be replaced by g:VePaths.FileName\r\n- Maybe modify the function folds to do like this: fu! g:VeGotoMark(mark) \" {{2 instead of adding the full function name in comments above the function itself, thus if the parameter changed, I will not have to change the comment also.\r\nDocumentation \r\n- Add documentation about user-defined commands\r\nImprovements to current features \r\n- Add clone directory\r\n- The <space>o (reload) should remember the cursor position before to redo a g:VeLs()\r\n- The <space>R (rename) if an accent is added to the filename in the command line, then it is not the accent that appears in the filename once the rename is done but something else due to an encoding issue\r\n- History should not be completely cleared (deleted) when the maximum length is attained, but it should be cut at the end to be less than the maximum\r\n- 07.02.2013 23:15:42 (\u00c3\u0097\u00c3\u00b2) The favorites should not contain links in double\r\n- The filter dosen't work after a recursive listing example <space>L on c:\\temp then do \"f\" *.vim, only the current dir will be filtered, this is maybe because the results of a recursive listing are kept in memory when a directory dosen't change but an operation is done on it. To filter recursive results would be some kind of way of searching for files... maybe to refresh directory if a filter is done but to use memorized recursive listing for other operations...\r\n- Add pathsources that the user commands can be run onto\r\n- There are several modifications that could be done to the commands on selected files: grep recursive file\/directories results, user command to execute on recursive directories\/files and on grep results\r\n- Improve the run command to make it run asynchronously if possible in Linux\r\n- Maybe I should remove from selection the files after the command is ran like I did for the run command adding \"\\| let g:VeSelectedFiles = g:Item.New1('SelectedFiles') \\| cal g:VeLs()\" to the command\r\n- Maybe eventually, if it would proove to be better, to replace the ls command by the glob() function and use more the other file functions found in function-list like getftype() for example...but I'd say that ls is faster than glob and that it has dates, sorts etc\r\n- For now the encoding used for shell commands is 'latin1' which supports french special characters like accents, that makes it possible to run commands or copy (etc) files that have these special characters in their path. But it is not possible for now to run commands on files with other characters than included in 'latin1' encoding, like russian characters, chinese characters etc You may change the 'latin1' by something else if you wish by searching 'latin1' in the code. If I find a solution that works universally for all languages, like the use of utf-8, I will do the modification for it.\r\nNew features \r\n- Maybe add run (<space>r) to grep results?\r\n- Add commands to copy files, move files etc that can be used from command line and call these from the mappings\r\n- Add a bar for recent files: (see Mru plugin how its done, maybe use an autocommand on \"bufopen\") and add to g:VeCfg\r\n- Add a bar for buffers opened: list buffers (see vimrc <tab>b, add maybe mapping for close buffer maybe so a buffer \"link\" may be closed\r\n- Maybe add a function to collect words or strings from selected files, use the collect function from my vimrc and add a collect command\r\n- 11.02.2013 19:04:03 (\u00c3\u008f\u00c3\u00ad) Add clone of files links in favorites\r\n- 11.02.2013 19:04:20 (\u00c3\u008f\u00c3\u00ad) Add feature to go to the directory of a file in the favorites and to position the cursor to that file\r\nBugs \r\n- It seems again sometimes the content of a vimexplorer window is copied to the clipboard (see clear window before VeLs())\r\n- After starting vim and opening vimexplorer for first time, using a mark (example 'd to go to documents) there is the error: error detected ... g:VeLs: line 122 E33: No previous substitute regular expression\r\n- 23.02.2013 23:22:19 (\u00c3\u0091\u00c3\u00a1) ctrl-u presse 2 fois fait un : dans le command line et non un 1\/2 page up dans vim\r\n- Sometimes there is garbage from copy\/paste registers that come to replace the favorites in the favorites bar...I don't know what happen there.\r\n- When opening grep results in new tabs, the g:VeCommandToRun object is used to open the selected files, so the previous g:veCommandToRun which contained the grep command results is replaced by the OpenInNewTab command, that is why when returning to the VimExplorer window after viewing executing this OpenInNewTab on grep results command the previous grep results are not there anymore. This is somehow a limitation, to overcome this there could be an array of g:VeCommandToRun for example, but for now to leave it like this. \r\n- When selected files from a recursive listing, if the same filenames appear in other subdirs they are also highlighted (but not added to selection) this is because the highlight is based on the filename... I'm not sure there may be a simple solution to this\r\n- Cannot execute external commands (copy, delete, etc) on files that contains french accents for example or russian alphabet\r\n  - the fnamemodify() function with the :8 parameter to obtain dos names dosen't return the dos name if the path is not written in english (containing other characters than english chars) like in french or russian it dosen't work. So get the dos filename from the dir command using the dir \/x FullPath command\r\n  - Wait answer from Xaizek on this, I sent email to him\r\n- In the sample user commands, the copy to clipboard even with many selected files copies only one file to clipboard (maybe put a <cr> after the command?)\r\n- When opening a html file with \\ww (in my vimrc) in vimExplorer, the color syntax seemed one time to change in the code...to test\r\n- Cannot run commands on file written with the russian alphabet (see RunCommand() function, exe iconv(command, &enc, 'latin1')) This iconv() conversion works for french but not for russian (latin1 is also what is used in the shell (cp850) so there is not problem there, but with russian even by changing the shell with chcp 855 or chcp 866 and doing after the command with the russian name it dosen't work, for example echo system('chcp 855 & type \"' . iconv('c:\\temp\\Copy of Новый текстовый документ.txt', &enc, 'cp855') . '\"')\r\n- I noticed that the regular expression in g:VeGetPath() function ('[0-9]\\s\\w\\{3\\}\\s\\(\\s\\|[0-9]\\)[0-9]\\s\\([0-9][0-9]:[0-9][0-9]\\|\\s[0-9]\\{4\\}\\)\\s\\zs.*') which gets the filename dosen't work for computers where the information in the listing like the user name or the month is written in russian like for example \"drwxrwx---  1 Администратор          0 сен  8 10:13 colors\" the \"\\w\" in regular expression don't match characters in the russian alphabet. This seems like a vim limitation, I don't know yet how to solve this, maybe to change the code page of the shell with \"chcp\" before to issue the \"ls\" command (in Windows)... Maybe there are unicode matching characters in vim...\r\n- When using ctrl-i to return to next position in the buffer, there is a latence, like if vim was waiting for another key input like if it was using in another mapping\r\nAnnoyances \r\n- Try to find way not to see the appearing\/disapearing taskbar button when cal system('cd \"' . path . '\"') and exe 'silent r! ls.exe...' are executed\r\nHistory \r\n\r\n1.0 \r\n- First release\r\n1.1 \r\n- Modified the GetFileName() function: when there is very large files with the number of bytes taking much spaces, the filenames may not be aligned, so to find the position of the first filename was not enough, I had to find the position of the filename on the current line, each independently.\r\n- Added the favorites bar that offers another way of bookmarking directories other than directory marks.\r\n- Corrected the history bar and favorites bar, the links where not executed when <space>l or <enter> were pressed on the \"]\" character.\r\n- Added initialization of the fileName variable to '' in the GetFileName() function\r\n- Added possibility to edit the history bar and favorites bar. They will be saved when changing directories or when <space>s is pressed, or when vim quits if the cursor is in a vimExplorer window.\r\n- You may now write or edit a path manually in the \"Path: \" bar at the top of the buffer. Once the path is entered, press <space>l or <enter> to go to that path.\r\n- Now use <space>a to go the path at the top of the buffer to edit it. Press <space>l or <enter> (in normal mode) to go the that path once edited.\r\n- Modified comments: there was <space>g to execute history paths, now <space>l or <enter>. I modified other comments as well.\r\n1.2 \r\n- Added <space>e (edit) to open files in current buffer.\r\n- Changed commands VimExplorerB, VimExplorerBF, VimExplorerBP for VimExplorerE, VimExplorerEF, VimExplorerEP \r\n- Changed mappings \\vb and \\VB for \\ve and \\VE so it is similar to the <space>e command, to keep consistance between mappings.\r\n- Added very large max length for favorites not to autodelete them if there are too many like with the history bar.\r\n- Added the possibility to calg:VeGetPath() from any file, not just from a vimExplorer window, to get the multiple path formats to global variables. This allows for example to switch to another window where there would be a menu of links that contains the path variables in commands. One example could be that a code file is in edition, once saved, switch to menu window and execute the commands from the links. If you don't want to get the paths when leaving any files, set the \"s:GetPathOnLeaveAlways\" variable to 0\r\n- Modified comments\r\n1.3 \r\n- Added folds in GetFileName(), VeLs()\r\n- Modified comments, the \\vb and \\VB mappings where still in the documentation but they was replaced by \\ve and \\VE.\r\n2.0 \r\n- Give same behavior to all paths, this means that links, grep results paths, recursive listing paths all behave the same way like files in the directory listing. So now it is possible for example to open a link in the favorites bar or history bar in another tab using <space>t or to open a grep result in a vertical split window doing <space>v. See the \"File operations\" section in the documentation usage, to see other possible actions to do on directories, files and links.\r\n- Now directory may be opened in new tabs or new split etc like any file.\r\n- The configuration file is now a xml file the previous file format using a dictionary is not compatible anymore. The plugin used for this xml file is \"basicXmlParser.vim\" which is included in this plugin so that each release will have the corresponding working version of the plugin\r\n- Copy and move files and directories works in windows (not tested in linux)\r\n- Now possible to open multiple selected files each in a new tab\r\n- Added shift-j To open the next file in the preview window, shift-k Go open the previous file in the preview window, and also the default action now to open items is in the preview window\r\n- It is now possible to add files to the favorites bar using <space>B (<space>b add a directory). This means that the favorites bar can now be used to bookmark directories but also to contain links to files (like shortcuts).\r\n- Corrected bug in the GetFileName() function when there was a filter set with <space>f, the files could not opened.\r\n- I removed one function that was not used anymore to add favorites, it was replaced by AddToBar() which is used also for the history bar.\r\n- Removed the VeGetFileName() function, put its code in the VeGetPath() function  \r\n- Corrected a bug in the change directory function, now changes directory without interruption\r\n- Change <space>s (save configuration) for <space>S. <space>s is not used to select a file.  \r\n- Added <space>X Open current directory with the gvim \"browse\" command to open a file in the current buffer\r\n- Changed the fold level for the mappings so they appear at the first level for more easy access\r\n- Put the matchadd() to set the colors inside try..catch in case the highlight groups defined are not present in the current color scheme. I added a documentation section explaining how to change these colors.\r\n- Added a new variable to know what was the last history path added not to add the current path multiple times (suggestion from Xaizek)\r\n- Replaced the fixed value for the starting line of the directory listing by a function called \"g:VeGetDirectoryListLineNum()\"\r\n- Removed a \"\\s\" from the regexes to test if the line is a directory or a file (\"^d.\\{9}\\s\" or \"^-.\\{9}\\s\") because in cygwin there is only one \\s but with UnxUtils there are 2. \r\n- Changed the variable $home by $HOME because in linux it is case sensitive\r\n- Removed the option \"setlocal nowrap\" in the BuildWindow() function, because a user may want always to have the history and favorites bar wrapped\r\n- Corrected the <leader>VV mapping, it was <leader>VV> and was not executing\r\n- Corrected\/added <space>` to show the marks same like <space>'\r\n- Added user-commands that can be run on selected files\r\n- I remove TabEnter\/Leave and BufEnter\/Leave from the autocommands which call s:OnEnter() and s:OnLeave(), this was causing these functions to be called 3 times thus slowing access to the windows, this removed the necessity for the usage of the variable g:VeAutoRefreshOnEnter that was removed\r\n- Change map to nmap in mappings to start the plugin\r\n- Added mappings to inspect the content of the selected files object, the commands object and the command to run object\r\n- Added operations on selected files in a recursive listing also (ls -R) Copy, move, delete, OpenInNewTab etc\r\n- Added selection of items in the links bar\r\n2.1 \r\n- Added \"silent\" to the <space>x mappings\r\n- Corrected bug in the g:VeSetCursorPos(path) (to exit if there are no path)\r\n- Did testing when there are no VimExplorer.xml file\r\n- Change suggested mappings (commented out) (f2, f3, ..., Home, PageUp, etc)\r\n- Modified the installation instructions to indicated that if you use the plugin in Windows, you will have to change the value of the \"g:VeLsCmdPath\" to that of the path where your ls command is located. Search for the variable using: \/let g:VeLsCmdPath\r\n- Added <space>9 If Windows is used to change the ls command for \"UnxUtils\" ls command\r\n- Added <space>0 If Windows is used to Change the ls command for \"Cygwin\" ls command\r\n- Modified also the installation instructions to indicated that if you use the plugin in Windows, you will have to change also the value of the \"g:VeGrepCmdPath\" to that of the path where your grep command is located. Search for the variable using: \/let g:VeGrepCmdPath (You may also set that variable to 'grep' simply and set the path to the executable using the system %path% variable)\r\n- Change the regex so that the cursor position is remembered also when there is a filter: changed \"cal search('\\([0-9]\\s\\+\\|\\\/\\)\\zs\\s\\+' . g:VeCfg.CursorPos[g:VePath].Value . '$')\" to \"cal search('[0-9]\\zs\\s\\+' . g:VeCfg.CursorPos[g:VePath].Value . '$')\"\r\n- Changed ! for system() in the <space>c (clone) mapping, not to see the prompt window\r\n- Changed ! for system() in the <space>R (rename) mapping, not to see the prompt window\r\n- Changed unlet to unlet! in the <space>R command\r\n2.2 \r\n- Added many new paths formats for dos, so all the current path formats have their dos equivalent with 8 characters only for directory and file names.\r\n- Removed some blank spaces that where found after <cr> in some mappings that where \"pressing a space\" after executing the mapping\r\n- Improved organization and content in the documentation and remove old items in the documentation\r\n- Removed file selections after executing the run command\r\n- Removed the <c-a> mapping to select all files because it was selecting grep results also...\r\n- changed the default paths for ls.exe and grep.exe from \"UnxUtils\", they are now in the \"$vim\" folder this as the benefit of making these command move with the vim folder, so they are always available where the vim folder is copied. This is for \"UnxUtils\" on Windows, it as no impact on Linux or on Windows if \"Cygwin\" is used.\r\n- 23.01.2013 0:34:18 (\u00c3\u0091\u00c3\u00b0) I changed the exe command for Windows in the RunCommand() function by exe iconv(command, &enc, 'latin1') to be able to run commands on file with french accents. In my tests I could do for files with russian alphabet echo system('type \"' . iconv('c:\\temp\\Новый текстовый документ.txt', &enc, 'latin1') . '\"') and the content of that file was echoed, but it dosen't work for the run command for example\r\n2.3 \r\n- There was a some kind of bug in the g:VeLs() function, that the clear buffer statement was copying all the buffer into the paste register. I backed up the paste register before to execute that statement with 'let tmpReg = @\"' then set back the paste buffer. To find a better solution when I have time.\r\n2.4 \r\n- Copy and move etc in Linux now working, I modified the copy, move, delete etc. commands in linux to use forward slash '\/'.\r\n2.5 \r\n- Correction to the <space>r command (run selected files) which was not keeping cursor position and also there was a bug when running multiple files, the reinitialization was in the command step so reinitializing the selected file list after running the first command, but now it is reinitialized after the call to g:VeRunCommand(), also the set cursor position is set before doing a call to g:VeLs() after the call to g:VeRunCommand()\r\n- Added <space>: To go to the favorites list (then do ; or , (from the vim 'f' command) to move forward and backward from one path to another, then when on the desired path, do <space>l or <enter>to goto the directory.)\r\n- Corrected copy, move, delete, run etc commands by doubling the quotes found in the paths, because the command is delimited by single quotes, they had to be doubled or a error was occuring if the path contained single quotes.\r\n2.5.1 \r\n- Small correction with opening grep results in new tab when there is a single quote (or several) somewhere in the path\r\n2.5.2 \r\n- I removed a echo placed for debugging purposes that caused the \"press any key\" message to show\r\n2.5.3 \r\n- I changed the commands to clear the buffer in the g:VeLs() function to send the deleted content to the black hole register instead of the paste register which was backed up to a temporary variable and reset after.","4":"See latest version on github: https:\/\/github.com\/viaa\/VimPlugins\r\n\r\nDocumentation \r\n\r\nName: vimExplorer.vim\r\nVersion: 2.5.3\r\nDescription: File manager. Explore directories quickly and operate on files.\r\nAuthor: Alexandre Viau (alexandreviau@gmail.com)\r\nWebsite: The latest version is found on \"vim.org\"\r\n\r\nAbout  \r\n\r\nI would like if vimExplorer would become an open source, cross-platform, text and keyboard oriented filemanager alternative. It is now in that direction since version 2.0 vimExplorer is able to open, copy, move, delete, delete, run files and more. Using vim and its amazing text editing power and keyboard mapping habilities as an interface and numerous powerful shell commands for file management makes vimExplorer the ideal solution for fast and flexible file editing and management. I put a lot of thinking to make it as much comfortable, fast and easy to use as possible. With vimExplorer I try also to solve the difficulties (if I may say so) of file system access from vim (to find files, open them for edition, etc). Also to be able to do file management, grepping and searching from within vim without having to use an external program or shell could potentially increase productivity.\r\n\r\nInstallation \r\n\r\n- Copy the plugin to the vim plugin directory. \r\n- If you use the plugin in Windows, you will have to change the value of the \"g:VeLsCmdPath\" to that of the path where your ls command is located. Search for the variable using: \/let g:VeLsCmdPath (You may also set that variable to 'ls' simply and set the path to the executable using the system %path% variable)\r\n- There are mappings (<space>9 and <space>0) to switch between the ls command from \"UnxUtils\" or the ls command from \"Cygwin\". So you may use both like I do by setting a path for each of these variables \"g:VeLsCmdPathU\" and \"g:VeLsCmdPathC\". I personally use the ls command from \"UnxUtils\" for speed, and the ls command from \"Cygwin\" to display russian alphabet. I use these mappings to switch from one to another depending if I need they are file and directory names that are written with the russian alphabet.\r\n- If you use the plugin in Windows, you will have to change also the value of the \"g:VeGrepCmdPath\" to that of the path where your grep command is located. Search for the variable using: \/let g:VeGrepCmdPath (You may also set that variable to 'grep' simply and set the path to the executable using the system %path% variable)\r\n- vimExplorer requires depends on the \"basicXmlParser.vim\" plugin which is included at the top of this file to ensure compatibility and presence of the plugin.\r\n\r\nUsage \r\n\r\nMappings: \r\n\r\nOpen vimExplorer using the last accessed path \r\n\r\n<leader>ve Start vimExplorer in the current window\r\n<leader>vs Start vimExplorer in a new split (horizontal) window\r\n<leader>vv Start vimExplorer in a new vsplit (vertical) window\r\n<leader>vt Start vimExplorer in a new tab\r\n\r\n<leader>vd Start vimExplorer in double vertical panes (for file copy, move etc)\r\n<leader>vh Start vimExplorer in double horizontal panes (for file copy, move etc)\r\n<leader>vf Start vimExplorer with four panes (for file copy, move etc)\r\n<leader>vx Start vimExplorer with six panes (for file copy, move etc)\r\n\r\nNOTE: 1. There are other suggested mappings commented out where the preceding mappings are defined, to open vimExplorer in one key press. See \"other suggested mappings\" sections below in this documentation section.\r\n      2. You may create the number of panes vertical or horizontal you want by mixing the VimExplorerT, VimExplorerV and VimExplorerS in a command or a mapping you would add yourself to your vimrc. See the <leader>vd and <leader>vh mappings in this plugin as examples, these only use a combination of VimExplorerT and VimExplorerV or VimExplorers to create the panes. You may even have 4 or 6 panes even, as much as you need.\r\n\r\nOpen vimExplorer using a the current file's path \r\n\r\n<leader>VE Start vimExplorer in the current window\r\n<leader>VS Start vimExplorer in a new split (horizontal) window\r\n<leader>VV Start vimExplorer in a new vsplit (vertical) window\r\n<leader>VT Start vimExplorer in a new tab\r\n\r\nNOTE: With all directories, files and links (underlined text), all actions like <space>t (open in new tab), <space>v (open in vertical split), <space>s (open in split), <space>r (run), work with them. See \"File operations\"  section below for more of these actions and their definitions.\r\n\r\nDirectory browsing \r\n\r\n<space>l Open the selected directory or file (works also in the history bar and favorites bar at the top of the buffer and for grep results)\r\n<space>h Go to the parent directory\r\n\r\n<s-j> (shift-j) To open the next file in the preview window. You may hold the shift key then press many times j to preview one file after another. It will open the file and then pass to the next file, I found it better than to pass to the next file and open it because if you position the cursor on a file you do shift-j instead to have to do <enter> of <space>l to open the file then shift-j for next files.\r\n<s-k> (shift-k) Go open the previous file in the preview window. You may hold the shift key then press many times k to preview one file after another. It will open the file and then pass to the previous file, I found it better than to pass to the previous file and open it because if you position the cursor on a file you do shift-k instead to have to do <enter> of <space>l to open the file then shift-k for previous files.\r\n\r\n<space>a Go to the path at the top of the buffer to edit it. Press <space>l or <enter> (in normal mode) to go the that path once edited.\r\n<space>f Set filter to show only certain files\r\n<space>F Remove the filter and show all files\r\n<space>L Open the selected directory recursively\r\n<space>o Reload directory\r\n<space>p Copy path\r\n<space>P Show current path in different formats and to the clipboard\r\n<space>x Open directory in external file manager\r\n<space>X Open current directory with the gvim \"browse\" command to open a file in the current buffer\r\n<space>z Return to last path visited (toggle current and last)\r\n<space>9 If Windows is used to change the ls command for \"UnxUtils\" ls command\r\n<space>0 If Windows is used to Change the ls command for \"Cygwin\" ls command\r\nNOTE: 1. You may write or edit a path manually in the \"Path: \" bar at the top of the buffer. Once the path is entered, press <space>l or <enter> to go to that path.\r\n      2. You may change the path of the external file manager in the <space>x mapping.\r\n      3. Some file operations mappings work with the directories as well for example: <space>t to open in new tab, <space>x to open in external filemanager (check the \"File operations\" below)\r\n\r\nBrowsing history \r\n\r\n<space>l or <enter> Go to one of the history path shown at the top of the buffer, put cursor on one of the paths and execute this mapping.\r\n<space>; Go to the history list (then do ; or , (from the vim 'f' command) to move forward and backward from one path to another, then when on the desired path, do <space>l or <enter> to goto the directory.)\r\n<space>, Go to the end of the history list (then do ; or , (from the vim 'f' command) to move forward and backward from one path to another, then when on the desired path, do <space>, to goto the directory.)\r\n<space>H Delete the browsing history\r\nNOTE: 1. You may edit the history bar at the top of the buffer, you may add, remove or move paths on this line, it will be saved automatically when changing directory or doing <space>s to save the configuration or when vim quits if the cursor is in a vimExplorer window.\r\n      2. The maximum length of the history bar may be changed by setting the \"s:HistoryMaxLength\" variable\r\n      3. You may use the \"set wrap\" command to see all history if the list is long\r\n      4. Some file operations mappings work with the links in these history links for example: <space>t to open in new tab, <space>r to run, <space>x to open in external filemanager (check the \"File operations\" below)\r\n\r\nDirectory bookmarks \r\n\r\nma to mz Directory marks like similar to marks in vim using the m key but to mark directories instead of positions in files and ' or ` or ; to return to that directory. The maps are automatically activated on a directory listing. For example, press mw to mark the c:\\windows directory, then do 'w (or `w or ;w) to return to that directory. All letters may be used from a to z, A to Z and 0 to 9. Press '' to view a list of all the bookmarked directories sorted by mark, or press ;; to view the same list but sorted by paths. When '' or ;; is pressed, the list is shown and a mark is asked as input to goto to its directory, this is another way that marks are used.\r\nm0 to m9 Same like ma to mz but using numbers as marks\r\n'a to 'z or `a to `z To return to the directories marked by ma to mz  \r\n'0 to '9 or `0 to `9 Same like ma to mz but using numbers as marks\r\n<space>' Show all marked directories sorted by marks\r\n<space>` Show all marked directories sorted by marks\r\n<space>[ Show all marked directories sorted by directories\r\n\r\nDirectory favorites \r\n\r\n<space>b Add the path to the favorites bar\r\n<space>B Add the full path with the filename to the favorites bar (this allows to add \"shortcuts\" to files to run a file or to open a file)\r\n<space>: Go to the favorites list (then do ; or , (from the vim 'f' command) to move forward and backward from one path to another, then when on the desired path, do <space>l or <enter>to goto the directory.)\r\nNOTE: 1. The favorites bar is another way of bookmarking directories. It is independant from the directory bookmarks (marks) showned above. It is a feature on its own.\r\n      2. You may edit the favorites bar at the top of the buffer, you may add, remove or move paths on this line, it will be saved automatically when changing directory or doing <space>s to save the configuration or when vim quits if the cursor is in a vimExplorer window.\r\n      3. Some file operations mappings work with the links in these favorites links for example: <space>t to open in new tab, <space>r to run, <space>x to open in external filemanager (check the \"File operations\" below)\r\n      4. The favorites bar dosen't have a mapping to delete the bar like the history have <space>H. To delete the favorites bar, simply delete all the links from it and save the configuration (<space>s)\r\n\r\nDirectory file grep \r\n\r\n<space>g Grep current file\/directory or the selected files\/directories\r\nThe grep results appear after the file listing in the same buffer. You may position the cursor on a line in these results and press <space>l or <enter> to view it in the preview window.\r\nNOTE: 1. Some file operations mappings work with the links in these grep results links for example: <space>t to open in new tab, <space>r to run, <space>x to open in external filemanager (check the \"File operations\" below)\r\n\r\nDirectory file search \r\n\r\n<space>L  To search files in a directory, open the selected directory recursively using <space>L and then search the buffer for the file using vim's \"\/\" command or use vimgrep.\r\nNOTE: 1. Some file operations mappings work with the files and directories in these recursive listings for example: <space>t to open in new tab, <space>r to run, <space>x to open in external filemanager (check the \"File operations\" below)\r\n\r\nDirectory sorting \r\n\r\n<space>1 Sort by name\r\n<space>2 Sort by type\r\n<space>3 Sort by size\r\n<space>4 Sort by date\r\n\r\nFile operations \r\n\r\n<space>c Clone file\r\n<space>d New directory\r\n<space>D or <delete> Delete current file\/directory or selected files\/directories\r\n<space>l or <enter> Open the selected item in preview window\r\n<space>n New file\r\n<space>r Run the current file or the selected files\r\n<space>R Rename file\r\n<space>s or <enter> Open file in preview window\r\n<space>t Open current file\/directory or selected files\/directories in new tab\r\n<space>v Open file in vertical split window\r\n\r\nFile selection operations \r\n\r\nOperation that can be done on a group of selected files\/directories include for now: copy, move, delete, grep, open in new tab, run and a user defined command that a user can use to put the command he wants inside to execute on the selected files. \r\n\r\n<esc> Remove file selection\r\n<c-s> Toggle select\/deselect selected the file or files (if there are files selected in visual mode) to do an operation on it like copy, move, delete, grep etc\r\n<c-c> Copy files, toggle select\/deselect the file or files (if there are files selected in visual mode) and select the copy command as the command to run \r\n<c-x> Move files, toggle select\/deselect the file or files (if there are files selected in visual mode) and select the move command as the command to run \r\n<c-v> Paste files, RunCommand in the target directory (usually a paste command which is the copy or move itself). The target directory is simply a directory where the user goes after (in another window or in the same window).\r\n<c-u> Run the user defined command (the user may set a command to it to run on the selected files) See section \"How to run user-defined commands on selected files\"\r\n\r\nNOTE: 1. Set the variable \"s:ShowLastCommands\" to 1 if you want to see the last commands executed (appended at the end of the buffer after the file listing)\r\n      2. Since <c-v> is used to paste, use <c-q> to do a block selection in a vimExplorer window.\r\n\r\nShell operations \r\n\r\n<space><esc> Execute a command and insert its output in the buffer\r\n<space>C Open directory in shell\r\n\r\nConfiguration file operations \r\n\r\n<space>O Reload configuration from file (useful if the .config.vim file was edited manually and you want to reload it in the vimExplorer window that is currently opened)\r\n<space>S Save configuration file\r\n\r\nNOTE: 1. The configuration is automatically loaded when vim starts, and it is automatically closed when vim quits.\r\n      2. You may open the configuration file for edition, and after editing and saving the file, return to a vimExplorer window and do <space>O to reload the new configuration file.\r\n\r\nTo debug \r\n\r\n<leader>des To inspect the content of the g:VeSelectedFile object\r\n<leader>dec To inspect the content of the g:VeCommands object\r\n<leader>der To inspect the content of the g:VeCommandToRun object\r\n\r\nCommands: \r\n\r\nOpen vimExplorer using the last accessed path \r\n\r\nVimExplorerB Start vimExplorer in the current window\r\nVimExplorerS Start vimExplorer in a new split (horizontal) window\r\nVimExplorerV Start vimExplorer in a new vsplit (vertical) window\r\nVimExplorerT Start vimExplorer in a new tab\r\n\r\nOpen vimExplorer using a the current file's path \r\n\r\nVimExplorerBF Start vimExplorer in the current window\r\nVimExplorerSF Start vimExplorer in a new split (horizontal) window\r\nVimExplorerVF Start vimExplorer in a new vsplit (vertical) window\r\nVimExplorerTF Start vimExplorer in a new tab\r\n\r\nOpen vimExplorer using a path specified on the command line \r\n\r\nVimExplorerBP Start vimExplorer in the current window\r\nVimExplorerSP Start vimExplorer in a new split (horizontal) window\r\nVimExplorerVP Start vimExplorer in a new vsplit (vertical) window\r\nVimExplorerTP Start vimExplorer in a new tab\r\n\r\nHow to get the current path and filename for usage in external scripts \r\n\r\nIf you want to get the current path and filename from vimExplorer first cal the \"g:VeGetPath()\" then use the following variables as needed.\r\nThese paths variables may be used for example if you do new mappings or some kind of menu to execute operations on the current file or directory.\r\nNote that the current path and filename are copied when leaving the plugin or any file window for another window so the following variables could be used from there.\r\nIf you don't want to copy the path when leaving any file window, but just when leaving a vimExplorer window, set the variable \"s:GetPathOnLeaveAlways\" to 0\r\n\r\ng:VePaths.FileName  \r\ng:VePaths.FileNameQ  \r\ng:VePaths.FileName2Q  \r\ng:VePaths.PathS  \r\ng:VePaths.PathSQ  \r\ng:VePaths.PathS2Q  \r\ng:VePaths.FullPathS  \r\ng:VePaths.FullPathSQ  \r\ng:VePaths.FullPathS2Q  \r\ng:VePaths.PathB  \r\ng:VePaths.PathBQ  \r\ng:VePaths.PathB2Q  \r\ng:VePaths.FullPathB  \r\ng:VePaths.FullPathBQ  \r\ng:VePaths.FullPathB2Q  \r\ng:VePaths.Path2B  \r\ng:VePaths.Path2BQ  \r\ng:VePaths.Path2B2Q  \r\ng:VePaths.FullPath2B  \r\ng:VePaths.FullPath2BQ  \r\ng:VePaths.FullPath2B2Q  \r\ng:VePaths.DosFileName  \r\ng:VePaths.DosFileNameQ  \r\ng:VePaths.DosFileName2Q  \r\ng:VePaths.DosPathS  \r\ng:VePaths.DosPathSQ  \r\ng:VePaths.DosPathS2Q  \r\ng:VePaths.DosFullPathS  \r\ng:VePaths.DosFullPathSQ  \r\ng:VePaths.DosFullPathS2Q  \r\ng:VePaths.DosPathB  \r\ng:VePaths.DosPathBQ  \r\ng:VePaths.DosPathB2Q  \r\ng:VePaths.DosFullPathB  \r\ng:VePaths.DosFullPathBQ  \r\ng:VePaths.DosFullPathB2Q  \r\ng:VePaths.DosPath2B  \r\ng:VePaths.DosPath2BQ  \r\ng:VePaths.DosPath2B2Q  \r\ng:VePaths.DosFullPath2B  \r\ng:VePaths.DosFullPath2BQ  \r\ng:VePaths.DosFullPath2B2Q  \r\n\r\nHow to open vimExplorer from another script \r\n\r\nUse the VimExplorerE, VimExplorerT, etc and\/or other VimExplorer commands to start the plugin.\r\n\r\nHow to change the colors of the display \r\n\r\nFind the g:VeLs() function in the code and then find the comment section \"Set colors on specific items in the window\", there you'll find the highlight groups set as the first arguments of the matchadd() function. For example where there is \"cal matchadd('htmlLink', '\\[\\zs.\\{-}\\ze\\]')\" you may change \"htmlLink\" for some other highlight group of you choice.\r\n\r\nHow to run user-defined commands on selected files \r\n\r\nThis is useful if you want to command in batch on all the selected files.\r\nUse the \"ctrl-s\" mapping with or without visual selection to select files.\r\nThe command placed in \"Step1\" contains commands that are run on files, the command placed in \"Step2\" contains commands that are run on directories.\r\nYou may used all the placeholders found in the g:VeGethPath() function in your commands.\r\nThe values \"let g:VeCommands.User.Step1.Command.Value\" and\/or \"let g:VeCommands.User.Step2.Command.Value\" have to be initialized to a command or to '' (empty) before to run them using \":VimExplorerUC\" or the \"ctrl-u\" mapping. If initialize to '' (empty) then no command is ran, so if you don't want for example to run a command on directories do this on \"Step2\": let g:VeCommands.User.Step2.Command.Value = ''\r\nHere some sample user commands, run the commands using the \":VimExplorerUC\" command on the command-line or from a script, or use the \"ctrl-u\" mapping.\r\n\r\n\" Show full paths of selected files and directories and their \"PathSource\" (file or directory)\r\nlet g:VeCommands.User.Step1.Command.Value = 'echo \"%SelFullPathS% %SelPathSource%\"'\r\nlet g:VeCommands.User.Step2.Command.Value = 'echo \"%SelFullPathS% %SelPathSource%\"'\r\n\r\n\" Copy full paths of selected files and directories to the clipboard\r\nlet g:VeCommands.User.Step1.Command.Value = 'echo \"%SelFullPathS%\" | let @* = \"%SelFullPathS%\"'\r\nlet g:VeCommands.User.Step2.Command.Value = 'echo \"%SelFullPathS%\" | let @* = \"%SelFullPathS%\"'\r\n\r\n\" Rename files (Step1) (append '.txt' to selected files) (In Windows use \"!ren\", in Linux \"!mv\")\r\nlet g:VeCommands.User.Step1.Command.Value = 'cal system(\"ren \\\"%SelFileName%\\\" \\\"%SelFileName%.txt\\\"\")'\r\n\" Rename directories (Step2) (append '_bkp' to selected directories) (In Windows use \"!ren\", in Linux \"!mv\")\r\nlet g:VeCommands.User.Step2.Command.Value = 'cal system(\"ren \\\"%SelFileName%\\\" \\\"%SelFileName%_bkp\\\"\")'\r\n\r\nOther suggested mappings \r\n\r\nOther suggested mappings to open vimExplorer in one key press (to put in this plugin or in your vimrc) \r\nnmap <f2> :VimExplorerS<cr>\r\nnmap <f3> :VimExplorerV<cr>\r\nnmap <f4> :VimExplorerT<cr>\r\nnmap <f5> :VimExplorerE<cr>\r\nnmap <home> :VimExplorerS<cr>\r\nnmap <PageUp> :VimExplorerV<cr>\r\nnmap <PageDown> :VimExplorerT<cr>\r\nnmap <End> :VimExplorerE<cr>\r\n\" 2 vertical windows\r\nnmap <s-f2> :exe 'VimExplorerT' \\| exe 'VimExplorerV'<cr>\r\nnmap <s-home> :exe 'VimExplorerT' \\| exe 'VimExplorerV'<cr>\r\n\" 4 windows\r\nnmap <s-f3> :exe 'VimExplorerT' \\| exe 'VimExplorerV' \\| exe 'VimExplorerS' \\| wincmd l \\| exe 'VimExplorerS'<cr>\r\nnmap <s-PageUp> :exe 'VimExplorerT' \\| exe 'VimExplorerV' \\| exe 'VimExplorerS' \\| wincmd l \\| exe 'VimExplorerS'<cr>\r\n\" 6 windows\r\nnmap <s-f4> :exe 'VimExplorerT' \\| exe 'VimExplorerV' \\| exe 'VimExplorerS' \\| exe 'VimExplorerS' \\| wincmd l \\| exe 'VimExplorerS' \\| exe 'VimExplorerS'<cr>\r\nnmap <s-PageDown> :exe 'VimExplorerT' \\| exe 'VimExplorerV' \\| exe 'VimExplorerS' \\| exe 'VimExplorerS' \\| wincmd l \\| exe 'VimExplorerS' \\| exe 'VimExplorerS'<cr>\r\n\r\nTips \r\n- You may use the \"set wrap\" command to see all history if the list is long.\r\n- To search files in a directory, open the selected directory recursively using <space>L and then search the buffer for the file using vim's \"\/\" command or use vimgrep.\r\n- I use also the MRU plugin in combination with vimExplorer to have a list of the last opened files, I find it extremely useful for vim editing.\r\n- To go quickly to the favorites bar, do <space>; or <space>, which brings the cursor on the history bar, then do \"j\" to go down one line, then press \";\" or \",\" to go forward and backward on the favorites bar.\r\n- You may search the history and favorites using the \"\/\" or the \"?\" command, especially the \"?\" command as the links are at the top of the file.\r\n\r\nTodo \r\nCode organization \r\n- Check if g:VeFileName occurences really could not be replaced by g:VePaths.FileName\r\n- Maybe modify the function folds to do like this: fu! g:VeGotoMark(mark) \" {{2 instead of adding the full function name in comments above the function itself, thus if the parameter changed, I will not have to change the comment also.\r\nDocumentation \r\n- Add documentation about user-defined commands\r\nImprovements to current features \r\n- Add clone directory\r\n- The <space>o (reload) should remember the cursor position before to redo a g:VeLs()\r\n- The <space>R (rename) if an accent is added to the filename in the command line, then it is not the accent that appears in the filename once the rename is done but something else due to an encoding issue\r\n- History should not be completely cleared (deleted) when the maximum length is attained, but it should be cut at the end to be less than the maximum\r\n- 07.02.2013 23:15:42 (\u00c3\u0097\u00c3\u00b2) The favorites should not contain links in double\r\n- The filter dosen't work after a recursive listing example <space>L on c:\\temp then do \"f\" *.vim, only the current dir will be filtered, this is maybe because the results of a recursive listing are kept in memory when a directory dosen't change but an operation is done on it. To filter recursive results would be some kind of way of searching for files... maybe to refresh directory if a filter is done but to use memorized recursive listing for other operations...\r\n- Add pathsources that the user commands can be run onto\r\n- There are several modifications that could be done to the commands on selected files: grep recursive file\/directories results, user command to execute on recursive directories\/files and on grep results\r\n- Improve the run command to make it run asynchronously if possible in Linux\r\n- Maybe I should remove from selection the files after the command is ran like I did for the run command adding \"\\| let g:VeSelectedFiles = g:Item.New1('SelectedFiles') \\| cal g:VeLs()\" to the command\r\n- Maybe eventually, if it would proove to be better, to replace the ls command by the glob() function and use more the other file functions found in function-list like getftype() for example...but I'd say that ls is faster than glob and that it has dates, sorts etc\r\n- For now the encoding used for shell commands is 'latin1' which supports french special characters like accents, that makes it possible to run commands or copy (etc) files that have these special characters in their path. But it is not possible for now to run commands on files with other characters than included in 'latin1' encoding, like russian characters, chinese characters etc You may change the 'latin1' by something else if you wish by searching 'latin1' in the code. If I find a solution that works universally for all languages, like the use of utf-8, I will do the modification for it.\r\nNew features \r\n- Maybe add run (<space>r) to grep results?\r\n- Add commands to copy files, move files etc that can be used from command line and call these from the mappings\r\n- Add a bar for recent files: (see Mru plugin how its done, maybe use an autocommand on \"bufopen\") and add to g:VeCfg\r\n- Add a bar for buffers opened: list buffers (see vimrc <tab>b, add maybe mapping for close buffer maybe so a buffer \"link\" may be closed\r\n- Maybe add a function to collect words or strings from selected files, use the collect function from my vimrc and add a collect command\r\n- 11.02.2013 19:04:03 (\u00c3\u008f\u00c3\u00ad) Add clone of files links in favorites\r\n- 11.02.2013 19:04:20 (\u00c3\u008f\u00c3\u00ad) Add feature to go to the directory of a file in the favorites and to position the cursor to that file\r\nBugs \r\n- It seems again sometimes the content of a vimexplorer window is copied to the clipboard (see clear window before VeLs())\r\n- After starting vim and opening vimexplorer for first time, using a mark (example 'd to go to documents) there is the error: error detected ... g:VeLs: line 122 E33: No previous substitute regular expression\r\n- 23.02.2013 23:22:19 (\u00c3\u0091\u00c3\u00a1) ctrl-u presse 2 fois fait un : dans le command line et non un 1\/2 page up dans vim\r\n- Sometimes there is garbage from copy\/paste registers that come to replace the favorites in the favorites bar...I don't know what happen there.\r\n- When opening grep results in new tabs, the g:VeCommandToRun object is used to open the selected files, so the previous g:veCommandToRun which contained the grep command results is replaced by the OpenInNewTab command, that is why when returning to the VimExplorer window after viewing executing this OpenInNewTab on grep results command the previous grep results are not there anymore. This is somehow a limitation, to overcome this there could be an array of g:VeCommandToRun for example, but for now to leave it like this. \r\n- When selected files from a recursive listing, if the same filenames appear in other subdirs they are also highlighted (but not added to selection) this is because the highlight is based on the filename... I'm not sure there may be a simple solution to this\r\n- Cannot execute external commands (copy, delete, etc) on files that contains french accents for example or russian alphabet\r\n  - the fnamemodify() function with the :8 parameter to obtain dos names dosen't return the dos name if the path is not written in english (containing other characters than english chars) like in french or russian it dosen't work. So get the dos filename from the dir command using the dir \/x FullPath command\r\n  - Wait answer from Xaizek on this, I sent email to him\r\n- In the sample user commands, the copy to clipboard even with many selected files copies only one file to clipboard (maybe put a <cr> after the command?)\r\n- When opening a html file with \\ww (in my vimrc) in vimExplorer, the color syntax seemed one time to change in the code...to test\r\n- Cannot run commands on file written with the russian alphabet (see RunCommand() function, exe iconv(command, &enc, 'latin1')) This iconv() conversion works for french but not for russian (latin1 is also what is used in the shell (cp850) so there is not problem there, but with russian even by changing the shell with chcp 855 or chcp 866 and doing after the command with the russian name it dosen't work, for example echo system('chcp 855 & type \"' . iconv('c:\\temp\\Copy of Новый текстовый документ.txt', &enc, 'cp855') . '\"')\r\n- I noticed that the regular expression in g:VeGetPath() function ('[0-9]\\s\\w\\{3\\}\\s\\(\\s\\|[0-9]\\)[0-9]\\s\\([0-9][0-9]:[0-9][0-9]\\|\\s[0-9]\\{4\\}\\)\\s\\zs.*') which gets the filename dosen't work for computers where the information in the listing like the user name or the month is written in russian like for example \"drwxrwx---  1 Администратор          0 сен  8 10:13 colors\" the \"\\w\" in regular expression don't match characters in the russian alphabet. This seems like a vim limitation, I don't know yet how to solve this, maybe to change the code page of the shell with \"chcp\" before to issue the \"ls\" command (in Windows)... Maybe there are unicode matching characters in vim...\r\n- When using ctrl-i to return to next position in the buffer, there is a latence, like if vim was waiting for another key input like if it was using in another mapping\r\nAnnoyances \r\n- Try to find way not to see the appearing\/disapearing taskbar button when cal system('cd \"' . path . '\"') and exe 'silent r! ls.exe...' are executed\r\nHistory \r\n\r\n1.0 \r\n- First release\r\n1.1 \r\n- Modified the GetFileName() function: when there is very large files with the number of bytes taking much spaces, the filenames may not be aligned, so to find the position of the first filename was not enough, I had to find the position of the filename on the current line, each independently.\r\n- Added the favorites bar that offers another way of bookmarking directories other than directory marks.\r\n- Corrected the history bar and favorites bar, the links where not executed when <space>l or <enter> were pressed on the \"]\" character.\r\n- Added initialization of the fileName variable to '' in the GetFileName() function\r\n- Added possibility to edit the history bar and favorites bar. They will be saved when changing directories or when <space>s is pressed, or when vim quits if the cursor is in a vimExplorer window.\r\n- You may now write or edit a path manually in the \"Path: \" bar at the top of the buffer. Once the path is entered, press <space>l or <enter> to go to that path.\r\n- Now use <space>a to go the path at the top of the buffer to edit it. Press <space>l or <enter> (in normal mode) to go the that path once edited.\r\n- Modified comments: there was <space>g to execute history paths, now <space>l or <enter>. I modified other comments as well.\r\n1.2 \r\n- Added <space>e (edit) to open files in current buffer.\r\n- Changed commands VimExplorerB, VimExplorerBF, VimExplorerBP for VimExplorerE, VimExplorerEF, VimExplorerEP \r\n- Changed mappings \\vb and \\VB for \\ve and \\VE so it is similar to the <space>e command, to keep consistance between mappings.\r\n- Added very large max length for favorites not to autodelete them if there are too many like with the history bar.\r\n- Added the possibility to calg:VeGetPath() from any file, not just from a vimExplorer window, to get the multiple path formats to global variables. This allows for example to switch to another window where there would be a menu of links that contains the path variables in commands. One example could be that a code file is in edition, once saved, switch to menu window and execute the commands from the links. If you don't want to get the paths when leaving any files, set the \"s:GetPathOnLeaveAlways\" variable to 0\r\n- Modified comments\r\n1.3 \r\n- Added folds in GetFileName(), VeLs()\r\n- Modified comments, the \\vb and \\VB mappings where still in the documentation but they was replaced by \\ve and \\VE.\r\n2.0 \r\n- Give same behavior to all paths, this means that links, grep results paths, recursive listing paths all behave the same way like files in the directory listing. So now it is possible for example to open a link in the favorites bar or history bar in another tab using <space>t or to open a grep result in a vertical split window doing <space>v. See the \"File operations\" section in the documentation usage, to see other possible actions to do on directories, files and links.\r\n- Now directory may be opened in new tabs or new split etc like any file.\r\n- The configuration file is now a xml file the previous file format using a dictionary is not compatible anymore. The plugin used for this xml file is \"basicXmlParser.vim\" which is included in this plugin so that each release will have the corresponding working version of the plugin\r\n- Copy and move files and directories works in windows (not tested in linux)\r\n- Now possible to open multiple selected files each in a new tab\r\n- Added shift-j To open the next file in the preview window, shift-k Go open the previous file in the preview window, and also the default action now to open items is in the preview window\r\n- It is now possible to add files to the favorites bar using <space>B (<space>b add a directory). This means that the favorites bar can now be used to bookmark directories but also to contain links to files (like shortcuts).\r\n- Corrected bug in the GetFileName() function when there was a filter set with <space>f, the files could not opened.\r\n- I removed one function that was not used anymore to add favorites, it was replaced by AddToBar() which is used also for the history bar.\r\n- Removed the VeGetFileName() function, put its code in the VeGetPath() function  \r\n- Corrected a bug in the change directory function, now changes directory without interruption\r\n- Change <space>s (save configuration) for <space>S. <space>s is not used to select a file.  \r\n- Added <space>X Open current directory with the gvim \"browse\" command to open a file in the current buffer\r\n- Changed the fold level for the mappings so they appear at the first level for more easy access\r\n- Put the matchadd() to set the colors inside try..catch in case the highlight groups defined are not present in the current color scheme. I added a documentation section explaining how to change these colors.\r\n- Added a new variable to know what was the last history path added not to add the current path multiple times (suggestion from Xaizek)\r\n- Replaced the fixed value for the starting line of the directory listing by a function called \"g:VeGetDirectoryListLineNum()\"\r\n- Removed a \"\\s\" from the regexes to test if the line is a directory or a file (\"^d.\\{9}\\s\" or \"^-.\\{9}\\s\") because in cygwin there is only one \\s but with UnxUtils there are 2. \r\n- Changed the variable $home by $HOME because in linux it is case sensitive\r\n- Removed the option \"setlocal nowrap\" in the BuildWindow() function, because a user may want always to have the history and favorites bar wrapped\r\n- Corrected the <leader>VV mapping, it was <leader>VV> and was not executing\r\n- Corrected\/added <space>` to show the marks same like <space>'\r\n- Added user-commands that can be run on selected files\r\n- I remove TabEnter\/Leave and BufEnter\/Leave from the autocommands which call s:OnEnter() and s:OnLeave(), this was causing these functions to be called 3 times thus slowing access to the windows, this removed the necessity for the usage of the variable g:VeAutoRefreshOnEnter that was removed\r\n- Change map to nmap in mappings to start the plugin\r\n- Added mappings to inspect the content of the selected files object, the commands object and the command to run object\r\n- Added operations on selected files in a recursive listing also (ls -R) Copy, move, delete, OpenInNewTab etc\r\n- Added selection of items in the links bar\r\n2.1 \r\n- Added \"silent\" to the <space>x mappings\r\n- Corrected bug in the g:VeSetCursorPos(path) (to exit if there are no path)\r\n- Did testing when there are no VimExplorer.xml file\r\n- Change suggested mappings (commented out) (f2, f3, ..., Home, PageUp, etc)\r\n- Modified the installation instructions to indicated that if you use the plugin in Windows, you will have to change the value of the \"g:VeLsCmdPath\" to that of the path where your ls command is located. Search for the variable using: \/let g:VeLsCmdPath\r\n- Added <space>9 If Windows is used to change the ls command for \"UnxUtils\" ls command\r\n- Added <space>0 If Windows is used to Change the ls command for \"Cygwin\" ls command\r\n- Modified also the installation instructions to indicated that if you use the plugin in Windows, you will have to change also the value of the \"g:VeGrepCmdPath\" to that of the path where your grep command is located. Search for the variable using: \/let g:VeGrepCmdPath (You may also set that variable to 'grep' simply and set the path to the executable using the system %path% variable)\r\n- Change the regex so that the cursor position is remembered also when there is a filter: changed \"cal search('\\([0-9]\\s\\+\\|\\\/\\)\\zs\\s\\+' . g:VeCfg.CursorPos[g:VePath].Value . '$')\" to \"cal search('[0-9]\\zs\\s\\+' . g:VeCfg.CursorPos[g:VePath].Value . '$')\"\r\n- Changed ! for system() in the <space>c (clone) mapping, not to see the prompt window\r\n- Changed ! for system() in the <space>R (rename) mapping, not to see the prompt window\r\n- Changed unlet to unlet! in the <space>R command\r\n2.2 \r\n- Added many new paths formats for dos, so all the current path formats have their dos equivalent with 8 characters only for directory and file names.\r\n- Removed some blank spaces that where found after <cr> in some mappings that where \"pressing a space\" after executing the mapping\r\n- Improved organization and content in the documentation and remove old items in the documentation\r\n- Removed file selections after executing the run command\r\n- Removed the <c-a> mapping to select all files because it was selecting grep results also...\r\n- changed the default paths for ls.exe and grep.exe from \"UnxUtils\", they are now in the \"$vim\" folder this as the benefit of making these command move with the vim folder, so they are always available where the vim folder is copied. This is for \"UnxUtils\" on Windows, it as no impact on Linux or on Windows if \"Cygwin\" is used.\r\n- 23.01.2013 0:34:18 (\u00c3\u0091\u00c3\u00b0) I changed the exe command for Windows in the RunCommand() function by exe iconv(command, &enc, 'latin1') to be able to run commands on file with french accents. In my tests I could do for files with russian alphabet echo system('type \"' . iconv('c:\\temp\\Новый текстовый документ.txt', &enc, 'latin1') . '\"') and the content of that file was echoed, but it dosen't work for the run command for example\r\n2.3 \r\n- There was a some kind of bug in the g:VeLs() function, that the clear buffer statement was copying all the buffer into the paste register. I backed up the paste register before to execute that statement with 'let tmpReg = @\"' then set back the paste buffer. To find a better solution when I have time.\r\n2.4 \r\n- Copy and move etc in Linux now working, I modified the copy, move, delete etc. commands in linux to use forward slash '\/'.\r\n2.5 \r\n- Correction to the <space>r command (run selected files) which was not keeping cursor position and also there was a bug when running multiple files, the reinitialization was in the command step so reinitializing the selected file list after running the first command, but now it is reinitialized after the call to g:VeRunCommand(), also the set cursor position is set before doing a call to g:VeLs() after the call to g:VeRunCommand()\r\n- Added <space>: To go to the favorites list (then do ; or , (from the vim 'f' command) to move forward and backward from one path to another, then when on the desired path, do <space>l or <enter>to goto the directory.)\r\n- Corrected copy, move, delete, run etc commands by doubling the quotes found in the paths, because the command is delimited by single quotes, they had to be doubled or a error was occuring if the path contained single quotes.\r\n2.5.1 \r\n- Small correction with opening grep results in new tab when there is a single quote (or several) somewhere in the path\r\n2.5.2 \r\n- I removed a echo placed for debugging purposes that caused the \"press any key\" message to show\r\n2.5.3 \r\n- I changed the commands to clear the buffer in the g:VeLs() function to send the deleted content to the black hole register instead of the paste register which was backed up to a temporary variable and reset after.","install_details":"Copy the plugin to the vim plugin directory. \r\nIf you use the plugin in Windows, you will have to change the value of the \"g:VeLsCmdPath\" to that of the path where your ls command is located. Search for the variable using: \/let g:VeLsCmdPath (You may also set that variable to 'ls' simply and set the path to the executable using the system %path% variable)\r\nThere are mappings (<space>9 and <space>0) to switch between the ls command from \"UnxUtils\" or the ls command from \"Cygwin\". So you may use both like I do by setting a path for each of these variables \"g:VeLsCmdPathU\" and \"g:VeLsCmdPathC\". I personally use the ls command from \"UnxUtils\" for speed, and the ls command from \"Cygwin\" to display russian alphabet. I use these mappings to switch from one to another depending if I need they are file and directory names that are written with the russian alphabet.\r\nIf you use the plugin in Windows, you will have to change also the value of the \"g:VeGrepCmdPath\" to that of the path where your grep command is located. Search for the variable using: \/let g:VeGrepCmdPath (You may also set that variable to 'grep' simply and set the path to the executable using the system %path% variable)","5":"Copy the plugin to the vim plugin directory. \r\nIf you use the plugin in Windows, you will have to change the value of the \"g:VeLsCmdPath\" to that of the path where your ls command is located. Search for the variable using: \/let g:VeLsCmdPath (You may also set that variable to 'ls' simply and set the path to the executable using the system %path% variable)\r\nThere are mappings (<space>9 and <space>0) to switch between the ls command from \"UnxUtils\" or the ls command from \"Cygwin\". So you may use both like I do by setting a path for each of these variables \"g:VeLsCmdPathU\" and \"g:VeLsCmdPathC\". I personally use the ls command from \"UnxUtils\" for speed, and the ls command from \"Cygwin\" to display russian alphabet. I use these mappings to switch from one to another depending if I need they are file and directory names that are written with the russian alphabet.\r\nIf you use the plugin in Windows, you will have to change also the value of the \"g:VeGrepCmdPath\" to that of the path where your grep command is located. Search for the variable using: \/let g:VeGrepCmdPath (You may also set that variable to 'grep' simply and set the path to the executable using the system %path% variable)","first_name":"Alexandre","6":"Alexandre","last_name":"Viau","7":"Viau","releases":[{"0":"4360","vim_version":"7.0","1":"7.0","script_version":"2.5.3","2":"2.5.3","version_comment":"I changed the commands to clear the buffer in the g:VeLs() function to send the deleted content to the black hole register instead of the paste register which was backed up to a temporary variable and reset after.\r\n","3":"I changed the commands to clear the buffer in the g:VeLs() function to send the deleted content to the black hole register instead of the paste register which was backed up to a temporary variable and reset after.\r\n","package":"vimExplorer.vim","4":"vimExplorer.vim","src_id":"19615","5":"19615","creation_date":"1362870029","6":"1362870029"},{"0":"4360","vim_version":"7.0","1":"7.0","script_version":"2.5.2","2":"2.5.2","version_comment":"- I removed a echo placed for debugging purposes that caused the \"press any key\" message to show\r\n","3":"- I removed a echo placed for debugging purposes that caused the \"press any key\" message to show\r\n","package":"vimExplorer.vim","4":"vimExplorer.vim","src_id":"19489","5":"19489","creation_date":"1360410007","6":"1360410007"},{"0":"4360","vim_version":"7.0","1":"7.0","script_version":"2.5.1","2":"2.5.1","version_comment":"- Small correction with opening grep results in new tab when there is a single quote (or several) somewhere in the path\r\n","3":"- Small correction with opening grep results in new tab when there is a single quote (or several) somewhere in the path\r\n","package":"vimExplorer.vim","4":"vimExplorer.vim","src_id":"19484","5":"19484","creation_date":"1360357850","6":"1360357850"},{"0":"4360","vim_version":"7.0","1":"7.0","script_version":"2.5","2":"2.5","version_comment":"- Correction to the <space>r command (run selected files) which was not keeping cursor position and also there was a bug when running multiple files, the reinitialization was in the command step so reinitializing the selected file list after running the first command, but now it is reinitialized after the call to g:VeRunCommand(), also the set cursor position is set before doing a call to g:VeLs() after the call to g:VeRunCommand()\r\n- Added <space>: To go to the favorites list (then do ; or , (from the vim 'f' command) to move forward and backward from one path to another, then when on the desired path, do <space>l or <enter>to goto the directory.)\r\n- Corrected copy, move, delete, run etc commands by doubling the quotes found in the paths, because the command is delimited by single quotes, they had to be doubled or a error was occuring if the path contained single quotes.","3":"- Correction to the <space>r command (run selected files) which was not keeping cursor position and also there was a bug when running multiple files, the reinitialization was in the command step so reinitializing the selected file list after running the first command, but now it is reinitialized after the call to g:VeRunCommand(), also the set cursor position is set before doing a call to g:VeLs() after the call to g:VeRunCommand()\r\n- Added <space>: To go to the favorites list (then do ; or , (from the vim 'f' command) to move forward and backward from one path to another, then when on the desired path, do <space>l or <enter>to goto the directory.)\r\n- Corrected copy, move, delete, run etc commands by doubling the quotes found in the paths, because the command is delimited by single quotes, they had to be doubled or a error was occuring if the path contained single quotes.","package":"vimExplorer.vim","4":"vimExplorer.vim","src_id":"19483","5":"19483","creation_date":"1360354517","6":"1360354517"},{"0":"4360","vim_version":"7.0","1":"7.0","script_version":"2.4","2":"2.4","version_comment":"Copy and move etc in Linux now working, I modified the copy, move, delete etc. commands in linux to use forward slash '\/'.","3":"Copy and move etc in Linux now working, I modified the copy, move, delete etc. commands in linux to use forward slash '\/'.","package":"vimExplorer.vim","4":"vimExplorer.vim","src_id":"19438","5":"19438","creation_date":"1359319331","6":"1359319331"},{"0":"4360","vim_version":"7.0","1":"7.0","script_version":"2.3","2":"2.3","version_comment":"There was a some kind of bug in the g:VeLs() function, that the clear buffer statement was copying all the buffer into the paste register. I backed up the paste register before to execute that statement with 'let tmpReg = @\"' then set back the paste buffer. To find a better solution when I have time.\r\n","3":"There was a some kind of bug in the g:VeLs() function, that the clear buffer statement was copying all the buffer into the paste register. I backed up the paste register before to execute that statement with 'let tmpReg = @\"' then set back the paste buffer. To find a better solution when I have time.\r\n","package":"vimExplorer.vim","4":"vimExplorer.vim","src_id":"19430","5":"19430","creation_date":"1359115772","6":"1359115772"},{"0":"4360","vim_version":"7.0","1":"7.0","script_version":"2.2","2":"2.2","version_comment":"- Added many new paths formats for dos, so all the current path formats have their dos equivalent with 8 characters only for directory and file names.\r\n- Removed some blank spaces that where found after <cr> in some mappings that where \"pressing a space\" after executing the mapping\r\n- Improved organization and content in the documentation and remove old items in the documentation\r\n- Removed file selections after executing the run command\r\n- Removed the <c-a> mapping to select all files because it was selecting grep results also...\r\n- changed the default paths for ls.exe and grep.exe from \"UnxUtils\", they are now in the \"$vim\" folder this as the benefit of making these command move with the vim folder, so they are always available where the vim folder is copied. This is for \"UnxUtils\" on Windows, it as no impact on Linux or on Windows if \"Cygwin\" is used.\r\n- I changed the exe command for Windows in the RunCommand() function by exe iconv(command, &enc, 'latin1') to be able to run commands on file with french accents. In my tests I could do for files with russian alphabet echo system('type \"' . iconv('c:\\temp\\Новый текстовый документ.txt', &enc, 'latin1') . '\"') and the content of that file was echoed, but it dosen't work for the run command for example\r\n","3":"- Added many new paths formats for dos, so all the current path formats have their dos equivalent with 8 characters only for directory and file names.\r\n- Removed some blank spaces that where found after <cr> in some mappings that where \"pressing a space\" after executing the mapping\r\n- Improved organization and content in the documentation and remove old items in the documentation\r\n- Removed file selections after executing the run command\r\n- Removed the <c-a> mapping to select all files because it was selecting grep results also...\r\n- changed the default paths for ls.exe and grep.exe from \"UnxUtils\", they are now in the \"$vim\" folder this as the benefit of making these command move with the vim folder, so they are always available where the vim folder is copied. This is for \"UnxUtils\" on Windows, it as no impact on Linux or on Windows if \"Cygwin\" is used.\r\n- I changed the exe command for Windows in the RunCommand() function by exe iconv(command, &enc, 'latin1') to be able to run commands on file with french accents. In my tests I could do for files with russian alphabet echo system('type \"' . iconv('c:\\temp\\Новый текстовый документ.txt', &enc, 'latin1') . '\"') and the content of that file was echoed, but it dosen't work for the run command for example\r\n","package":"vimExplorer.vim","4":"vimExplorer.vim","src_id":"19421","5":"19421","creation_date":"1359025045","6":"1359025045"},{"0":"4360","vim_version":"7.0","1":"7.0","script_version":"2.1","2":"2.1","version_comment":"Corrected bug in the s:SetCursorPos(path) (to exit if there are no path)\r\nDid testing when there are no VimExplorer.xml file\r\nChange suggested mappings (commented out) (f2, f3, ..., Home, PageUp, etc)\r\nModified the installation instructions to indicated that if you use the plugin in Windows, you will have to change the value of the \"g:VeLsCmdPath\" to that of the path where your ls command is located. Search for the variable using: \/let g:VeLsCmdPath\r\nAdded <space>9 If Windows is used to change the ls command for \"UnxUtils\" ls command\r\nAdded <space>0 If Windows is used to Change the ls command for \"Cygwin\" ls command\r\nModified also the installation instructions to indicated that if you use the plugin in Windows, you will have to change also the value of the \"g:VeGrepCmdPath\" to that of the path where your grep command is located. Search for the variable using: \/let g:VeGrepCmdPath (You may also set that variable to 'grep' simply and set the path to the executable using the system %path% variable)\r\nChange the regex so that the cursor position is remembered also when there is a filter: changed \"cal search('\\([0-9]\\s\\+\\|\\\/\\)\\zs\\s\\+' . g:VeCfg.CursorPos[g:VePath].Value . '$')\" to \"cal search('[0-9]\\zs\\s\\+' . g:VeCfg.CursorPos[g:VePath].Value . '$')\"\r\n","3":"Corrected bug in the s:SetCursorPos(path) (to exit if there are no path)\r\nDid testing when there are no VimExplorer.xml file\r\nChange suggested mappings (commented out) (f2, f3, ..., Home, PageUp, etc)\r\nModified the installation instructions to indicated that if you use the plugin in Windows, you will have to change the value of the \"g:VeLsCmdPath\" to that of the path where your ls command is located. Search for the variable using: \/let g:VeLsCmdPath\r\nAdded <space>9 If Windows is used to change the ls command for \"UnxUtils\" ls command\r\nAdded <space>0 If Windows is used to Change the ls command for \"Cygwin\" ls command\r\nModified also the installation instructions to indicated that if you use the plugin in Windows, you will have to change also the value of the \"g:VeGrepCmdPath\" to that of the path where your grep command is located. Search for the variable using: \/let g:VeGrepCmdPath (You may also set that variable to 'grep' simply and set the path to the executable using the system %path% variable)\r\nChange the regex so that the cursor position is remembered also when there is a filter: changed \"cal search('\\([0-9]\\s\\+\\|\\\/\\)\\zs\\s\\+' . g:VeCfg.CursorPos[g:VePath].Value . '$')\" to \"cal search('[0-9]\\zs\\s\\+' . g:VeCfg.CursorPos[g:VePath].Value . '$')\"\r\n","package":"vimExplorer.vim","4":"vimExplorer.vim","src_id":"19398","5":"19398","creation_date":"1358691744","6":"1358691744"},{"0":"4360","vim_version":"7.0","1":"7.0","script_version":"2.0","2":"2.0","version_comment":"Give same behavior to all paths, this means that links, grep results paths, recursive listing paths all behave the same way like files in the directory listing. So now it is possible for example to open a link in the favorites bar or history bar in another tab using <space>t or to open a grep result in a vertical split window doing <space>v. See the \"File operations\" section in the documentation usage, to see other possible actions to do on directories, files and links.\r\nNow directory may be opened in new tabs or new split etc like any file.\r\nThe configuration file is now a xml file the previous file format using a dictionary is not compatible anymore. The plugin used for this xml file is \"basicXmlParser.vim\" which is included in this plugin so that each release will have the corresponding working version of the plugin\r\nCopy and move files and directories works in windows (not tested in linux)\r\nNow possible to open multiple selected files each in a new tab\r\nAdded shift-j To open the next file in the preview window, shift-k Go open the previous file in the preview window, and also the default action now to open items is in the preview window\r\nIt is now possible to add files to the favorites bar using <space>B (<space>b add a directory). This means that the favorites bar can now be used to bookmark directories but also to contain links to files (like shortcuts).\r\nCorrected bug in the GetFileName() function when there was a filter set with <space>f, the files could not opened.\r\nI removed one function that was not used anymore to add favorites, it was replaced by AddToBar() which is used also for the history bar.\r\nRemoved the VeGetFileName() function, put its code in the VeGetPath() function  \r\nCorrected a bug in the change directory function, now changes directory without interruption\r\nChange <space>s (save configuration) for <space>S. <space>s is not used to select a file.  \r\nAdded <space>X Open current directory with the gvim \"browse\" command to open a file in the current buffer\r\nChanged the fold level for the mappings so they appear at the first level for more easy access\r\nPut the matchadd() to set the colors inside try..catch in case the highlight groups defined are not present in the current color scheme. I added a documentation section explaining how to change these colors.\r\nAdded a new variable to know what was the last history path added not to add the current path multiple times (suggestion from Xaizek)\r\nReplaced the fixed value for the starting line of the directory listing by a function called \"g:VeGetDirectoryListLineNum()\"\r\nRemoved a \"\\s\" from the regexes to test if the line is a directory or a file (\"^d.\\{9}\\s\" or \"^-.\\{9}\\s\") because in cygwin there is only one \\s but with UnxUtils there are 2. \r\nChanged the variable $home by $HOME because in linux it is case sensitive\r\nRemoved the option \"setlocal nowrap\" in the BuildWindow() function, because a user may want always to have the history and favorites bar wrapped\r\nCorrected the <leader>VV mapping, it was <leader>VV> and was not executing\r\nCorrected\/added <space>` to show the marks same like <space>'\r\nAdded user-commands that can be run on selected files\r\nI remove TabEnter\/Leave and BufEnter\/Leave from the autocommands which call s:OnEnter() and s:OnLeave(), this was causing these functions to be called 3 times thus slowing access to the windows, this removed the necessity for the usage of the variable g:VeAutoRefreshOnEnter that was removed\r\nChange map to nmap in mappings to start the plugin\r\nAdded mappings to inspect the content of the selected files object, the commands object and the command to run object\r\nAdded operations on selected files in a recursive listing also (ls -R) Copy, move, delete, OpenInNewTab etc\r\nAdded selection of items in the links bar\r\n","3":"Give same behavior to all paths, this means that links, grep results paths, recursive listing paths all behave the same way like files in the directory listing. So now it is possible for example to open a link in the favorites bar or history bar in another tab using <space>t or to open a grep result in a vertical split window doing <space>v. See the \"File operations\" section in the documentation usage, to see other possible actions to do on directories, files and links.\r\nNow directory may be opened in new tabs or new split etc like any file.\r\nThe configuration file is now a xml file the previous file format using a dictionary is not compatible anymore. The plugin used for this xml file is \"basicXmlParser.vim\" which is included in this plugin so that each release will have the corresponding working version of the plugin\r\nCopy and move files and directories works in windows (not tested in linux)\r\nNow possible to open multiple selected files each in a new tab\r\nAdded shift-j To open the next file in the preview window, shift-k Go open the previous file in the preview window, and also the default action now to open items is in the preview window\r\nIt is now possible to add files to the favorites bar using <space>B (<space>b add a directory). This means that the favorites bar can now be used to bookmark directories but also to contain links to files (like shortcuts).\r\nCorrected bug in the GetFileName() function when there was a filter set with <space>f, the files could not opened.\r\nI removed one function that was not used anymore to add favorites, it was replaced by AddToBar() which is used also for the history bar.\r\nRemoved the VeGetFileName() function, put its code in the VeGetPath() function  \r\nCorrected a bug in the change directory function, now changes directory without interruption\r\nChange <space>s (save configuration) for <space>S. <space>s is not used to select a file.  \r\nAdded <space>X Open current directory with the gvim \"browse\" command to open a file in the current buffer\r\nChanged the fold level for the mappings so they appear at the first level for more easy access\r\nPut the matchadd() to set the colors inside try..catch in case the highlight groups defined are not present in the current color scheme. I added a documentation section explaining how to change these colors.\r\nAdded a new variable to know what was the last history path added not to add the current path multiple times (suggestion from Xaizek)\r\nReplaced the fixed value for the starting line of the directory listing by a function called \"g:VeGetDirectoryListLineNum()\"\r\nRemoved a \"\\s\" from the regexes to test if the line is a directory or a file (\"^d.\\{9}\\s\" or \"^-.\\{9}\\s\") because in cygwin there is only one \\s but with UnxUtils there are 2. \r\nChanged the variable $home by $HOME because in linux it is case sensitive\r\nRemoved the option \"setlocal nowrap\" in the BuildWindow() function, because a user may want always to have the history and favorites bar wrapped\r\nCorrected the <leader>VV mapping, it was <leader>VV> and was not executing\r\nCorrected\/added <space>` to show the marks same like <space>'\r\nAdded user-commands that can be run on selected files\r\nI remove TabEnter\/Leave and BufEnter\/Leave from the autocommands which call s:OnEnter() and s:OnLeave(), this was causing these functions to be called 3 times thus slowing access to the windows, this removed the necessity for the usage of the variable g:VeAutoRefreshOnEnter that was removed\r\nChange map to nmap in mappings to start the plugin\r\nAdded mappings to inspect the content of the selected files object, the commands object and the command to run object\r\nAdded operations on selected files in a recursive listing also (ls -R) Copy, move, delete, OpenInNewTab etc\r\nAdded selection of items in the links bar\r\n","package":"vimExplorer.vim","4":"vimExplorer.vim","src_id":"19386","5":"19386","creation_date":"1358577944","6":"1358577944"},{"0":"4360","vim_version":"7.0","1":"7.0","script_version":"1.3","2":"1.3","version_comment":"Added folds in GetFileName(), VeLs()\r\nModified comments, the \\vb and \\VB mappings where still in the documentation but they was replaced by \\ve and \\VE.","3":"Added folds in GetFileName(), VeLs()\r\nModified comments, the \\vb and \\VB mappings where still in the documentation but they was replaced by \\ve and \\VE.","package":"vimExplorer.vim","4":"vimExplorer.vim","src_id":"19224","5":"19224","creation_date":"1356094127","6":"1356094127"},{"0":"4360","vim_version":"7.0","1":"7.0","script_version":"1.2","2":"1.2","version_comment":"Added <space>e (edit) to open files in current buffer.\r\n    Changed commands VimExplorerB, VimExplorerBF, VimExplorerBP for VimExplorerE, VimExplorerEF, VimExplorerEP \r\n    Changed mappings \\vb and \\VB for \\vb and \\VE so it is similar to the <space>e command, to keep consistance between mappings.\r\n    Added very large max length for favorites not to autodelete them if there are too many like with the history bar.\r\n    Added the possibility to call g:VeGetPath() from any file, not just from a vimExplorer window, to get the multiple path formats to global variables. This allows for example to switch to another window where there would be a menu of links that contains the path variables in commands. One example could be that a code file is in edition, once saved, switch to menu window and execute the commands from the links. If you don't want to get the paths when leaving any files, set the \"s:GetPathOnLeaveAlways\" variable to 0\r\n    Modified comments","3":"Added <space>e (edit) to open files in current buffer.\r\n    Changed commands VimExplorerB, VimExplorerBF, VimExplorerBP for VimExplorerE, VimExplorerEF, VimExplorerEP \r\n    Changed mappings \\vb and \\VB for \\vb and \\VE so it is similar to the <space>e command, to keep consistance between mappings.\r\n    Added very large max length for favorites not to autodelete them if there are too many like with the history bar.\r\n    Added the possibility to call g:VeGetPath() from any file, not just from a vimExplorer window, to get the multiple path formats to global variables. This allows for example to switch to another window where there would be a menu of links that contains the path variables in commands. One example could be that a code file is in edition, once saved, switch to menu window and execute the commands from the links. If you don't want to get the paths when leaving any files, set the \"s:GetPathOnLeaveAlways\" variable to 0\r\n    Modified comments","package":"vimExplorer.vim","4":"vimExplorer.vim","src_id":"19217","5":"19217","creation_date":"1356000780","6":"1356000780"},{"0":"4360","vim_version":"7.0","1":"7.0","script_version":"1.1","2":"1.1","version_comment":"Modified the GetFileName() function: when there is very large files with the number of bytes taking much spaces, the filenames may not be aligned, so to find the position of the first filename was not enough, I had to find the position of the filename on the current line, each independently.\r\n    Added the favorites bar that offers another way of bookmarking directories other than directory marks.\r\n    Corrected the history bar and favorites bar, the links where not executed when <space>l or <enter> were pressed on the \"]\" character.\r\n    Added initialization of the fileName variable to '' in the GetFileName() function\r\n    Added possibility to edit the history bar and favorites bar. They will be saved when changing directories or when <space>s is pressed, or when vim quits if the cursor is in a vimExplorer window.\r\n    You may now write or edit a path manually in the \"Path: \" bar at the top of the buffer. Once the path is entered, press <space>l or <enter> to go to that path.\r\n    Now use <space>a to go the path at the top of the buffer to edit it. Press <space>l or <enter> (in normal mode) to go the that path once edited.\r\n    Modified comments: there was <space>g to execute history paths, now <space>l or <enter>. I modified other comments as well.","3":"Modified the GetFileName() function: when there is very large files with the number of bytes taking much spaces, the filenames may not be aligned, so to find the position of the first filename was not enough, I had to find the position of the filename on the current line, each independently.\r\n    Added the favorites bar that offers another way of bookmarking directories other than directory marks.\r\n    Corrected the history bar and favorites bar, the links where not executed when <space>l or <enter> were pressed on the \"]\" character.\r\n    Added initialization of the fileName variable to '' in the GetFileName() function\r\n    Added possibility to edit the history bar and favorites bar. They will be saved when changing directories or when <space>s is pressed, or when vim quits if the cursor is in a vimExplorer window.\r\n    You may now write or edit a path manually in the \"Path: \" bar at the top of the buffer. Once the path is entered, press <space>l or <enter> to go to that path.\r\n    Now use <space>a to go the path at the top of the buffer to edit it. Press <space>l or <enter> (in normal mode) to go the that path once edited.\r\n    Modified comments: there was <space>g to execute history paths, now <space>l or <enter>. I modified other comments as well.","package":"vimExplorer.vim","4":"vimExplorer.vim","src_id":"19201","5":"19201","creation_date":"1355837829","6":"1355837829"},{"0":"4360","vim_version":"7.3","1":"7.3","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"vimExplorer.vim","4":"vimExplorer.vim","src_id":"19191","5":"19191","creation_date":"1355745312","6":"1355745312"}]},"4359":{"script_id":"4359","0":"4359","script_name":"rsi.vim","1":"rsi.vim","script_type":"utility","2":"utility","summary":"Readline style insertion","3":"Readline style insertion","description":"You know Readline key bindings? Of course you do, they're in your shell, your REPL, and perhaps even the GUI for your OS. They're similar to Emacs key bindings (C-a for home), but with several concessions for UNIX (C-w for delete word).\r\n\r\nWith rsi.vim, I've taken that same concession philosophy and extended it to Vim. Get the most useful of the ubiquitous key bindings without blindly overriding built-in Vim functionality.\r\n\r\nC-a, C-b, C-d, C-e, C-f, C-t, M-b, M-d, M-f, M-n, and M-p are provided. Several of these let the original Vim functionality through under some circumstances (for example, at the end of the line). The meta maps are done in a way that works in the terminal without remapping escape.\r\n\r\nhttps:\/\/github.com\/tpope\/vim-rsi","4":"You know Readline key bindings? Of course you do, they're in your shell, your REPL, and perhaps even the GUI for your OS. They're similar to Emacs key bindings (C-a for home), but with several concessions for UNIX (C-w for delete word).\r\n\r\nWith rsi.vim, I've taken that same concession philosophy and extended it to Vim. Get the most useful of the ubiquitous key bindings without blindly overriding built-in Vim functionality.\r\n\r\nC-a, C-b, C-d, C-e, C-f, C-t, M-b, M-d, M-f, M-n, and M-p are provided. Several of these let the original Vim functionality through under some circumstances (for example, at the end of the line). The meta maps are done in a way that works in the terminal without remapping escape.\r\n\r\nhttps:\/\/github.com\/tpope\/vim-rsi","install_details":"Extract in ~\/.vim (~\\vimfiles on Windows).","5":"Extract in ~\/.vim (~\\vimfiles on Windows).","first_name":"Tim","6":"Tim","last_name":"Pope","7":"Pope","releases":[{"0":"4359","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"rsi.zip","4":"rsi.zip","src_id":"19189","5":"19189","creation_date":"1355699962","6":"1355699962"}]},"4358":{"script_id":"4358","0":"4358","script_name":"Tablify","1":"Tablify","script_type":"utility","2":"utility","summary":"Plugin for making nice-loking tables from plain structured text","3":"Plugin for making nice-loking tables from plain structured text","description":"Full information and up-to-date code you can find at https:\/\/github.com\/Stormherz\/tablify","4":"Full information and up-to-date code you can find at https:\/\/github.com\/Stormherz\/tablify","install_details":"Put tablify.vim in your vim's plugin directory and you're ready to go.\r\nFor pathogen (https:\/\/github.com\/tpope\/vim-pathogen) users, just:  \r\n\r\n    cd ~\/.vim\/bundle\r\n    git clone git:\/\/github.com\/Stormherz\/tablify.git\r\n\r\nAnd you're ready to go.\r\n","5":"Put tablify.vim in your vim's plugin directory and you're ready to go.\r\nFor pathogen (https:\/\/github.com\/tpope\/vim-pathogen) users, just:  \r\n\r\n    cd ~\/.vim\/bundle\r\n    git clone git:\/\/github.com\/Stormherz\/tablify.git\r\n\r\nAnd you're ready to go.\r\n","first_name":"Vladimir","6":"Vladimir","last_name":"Shvets","7":"Shvets","releases":[{"0":"4358","vim_version":"7.0","1":"7.0","script_version":"0.5.1-2","2":"0.5.1-2","version_comment":"Fixed a bug with newly created table alignment","3":"Fixed a bug with newly created table alignment","package":"tablify.vim","4":"tablify.vim","src_id":"25947","5":"25947","creation_date":"1524780185","6":"1524780185"},{"0":"4358","vim_version":"7.0","1":"7.0","script_version":"0.5.1","2":"0.5.1","version_comment":"Fixed a bug with newly created table alignment","3":"Fixed a bug with newly created table alignment","package":"tablify.vim","4":"tablify.vim","src_id":"25946","5":"25946","creation_date":"1524780142","6":"1524780142"},{"0":"4358","vim_version":"7.0","1":"7.0","script_version":"0.5.1","2":"0.5.1","version_comment":"reStructuredText table format support","3":"reStructuredText table format support","package":"tablify.vim","4":"tablify.vim","src_id":"25004","5":"25004","creation_date":"1488480652","6":"1488480652"},{"0":"4358","vim_version":"7.0","1":"7.0","script_version":"0.5","2":"0.5","version_comment":"Row\/column movement","3":"Row\/column movement","package":"tablify.vim","4":"tablify.vim","src_id":"19254","5":"19254","creation_date":"1356780001","6":"1356780001"},{"0":"4358","vim_version":"7.0","1":"7.0","script_version":"0.4.1","2":"0.4.1","version_comment":"Separate column alignments, sorting map changed to <Leader>tS","3":"Separate column alignments, sorting map changed to <Leader>tS","package":"tablify.vim","4":"tablify.vim","src_id":"19250","5":"19250","creation_date":"1356695720","6":"1356695720"},{"0":"4358","vim_version":"7.0","1":"7.0","script_version":"0.4","2":"0.4","version_comment":"Multiline cell content","3":"Multiline cell content","package":"tablify.vim","4":"tablify.vim","src_id":"19241","5":"19241","creation_date":"1356540685","6":"1356540685"},{"0":"4358","vim_version":"7.0","1":"7.0","script_version":"0.3","2":"0.3","version_comment":"Core functionality refactoring, added table selection and sorting","3":"Core functionality refactoring, added table selection and sorting","package":"tablify.vim","4":"tablify.vim","src_id":"19226","5":"19226","creation_date":"1356105539","6":"1356105539"},{"0":"4358","vim_version":"7.0","1":"7.0","script_version":"0.2.2","2":"0.2.2","version_comment":"Per-buffer configuration","3":"Per-buffer configuration","package":"tablify.vim","4":"tablify.vim","src_id":"19197","5":"19197","creation_date":"1355829172","6":"1355829172"},{"0":"4358","vim_version":"7.0","1":"7.0","script_version":"0.2.1","2":"0.2.1","version_comment":"Tablification with common prefix","3":"Tablification with common prefix","package":"tablify.vim","4":"tablify.vim","src_id":"19192","5":"19192","creation_date":"1355770654","6":"1355770654"},{"0":"4358","vim_version":"7.0","1":"7.0","script_version":"0.2","2":"0.2","version_comment":"Bug fixes, additional <Leader>tl mapping","3":"Bug fixes, additional <Leader>tl mapping","package":"tablify.vim","4":"tablify.vim","src_id":"19190","5":"19190","creation_date":"1355738889","6":"1355738889"},{"0":"4358","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"tablify.vim","4":"tablify.vim","src_id":"19188","5":"19188","creation_date":"1355677965","6":"1355677965"}]},"4357":{"script_id":"4357","0":"4357","script_name":"DistractFree","1":"DistractFree","script_type":"color scheme","2":"color scheme","summary":"An WriteRoom\/DarkRoom\/OmniWrite like plugin","3":"An WriteRoom\/DarkRoom\/OmniWrite like plugin","description":"PLEASE RATE THIS PLUGIN, IF YOU LIKE IT! \r\n\r\nFeedback is always welcome. See :h DistractFree-feedback. \r\n\r\nThis plugin has been made to enable a WriteRoom\/DarkRoom\/OmniWriter like behaviour in Vim.\r\n\r\nWhen enabled, all unnecessary features are turned off, so you can concentrate\r\non writing with Vim. It also creates on each side a couple of empty windows,\r\nso that the text will be centered around the screen.\r\n\r\nThis plugin defines the following commands:\r\n\r\n:DistractFreeToggle\r\n\r\nThis commnd toggles between normal Vim mode and the distraction free mode.\r\n\r\nAlternatively, you can use the key <leader>W in normal mode to toggle between normal\r\nmode and Distraction Free mode. (If you haven't setup your leaderkey, see| use the '\\' key)","4":"PLEASE RATE THIS PLUGIN, IF YOU LIKE IT! \r\n\r\nFeedback is always welcome. See :h DistractFree-feedback. \r\n\r\nThis plugin has been made to enable a WriteRoom\/DarkRoom\/OmniWriter like behaviour in Vim.\r\n\r\nWhen enabled, all unnecessary features are turned off, so you can concentrate\r\non writing with Vim. It also creates on each side a couple of empty windows,\r\nso that the text will be centered around the screen.\r\n\r\nThis plugin defines the following commands:\r\n\r\n:DistractFreeToggle\r\n\r\nThis commnd toggles between normal Vim mode and the distraction free mode.\r\n\r\nAlternatively, you can use the key <leader>W in normal mode to toggle between normal\r\nmode and Distraction Free mode. (If you haven't setup your leaderkey, see| use the '\\' key)","install_details":"edit the file DistractFree.vmb with vim. From within vim simply source this file (by typing):\r\n:so % \r\n\r\nVim will automatically install this plugin.","5":"edit the file DistractFree.vmb with vim. From within vim simply source this file (by typing):\r\n:so % \r\n\r\nVim will automatically install this plugin.","first_name":"Christian","6":"Christian","last_name":"Brabandt","7":"Brabandt","releases":[{"0":"4357","vim_version":"7.3","1":"7.3","script_version":"5","2":"5","version_comment":"- updated documentation by Ingo Karkat, Thanks!, issue #1\n- Make State of plugin avaivable to extern (patch by Ingo Karkat, Thanks!, issue #2)\n- Ensure, padding of 'stl' works correctly (patch by Ingo Karkat, Thanks!, issue #3)\n- :q in DistractMode quits vim correctly\n- Save\/Restore User highlighting\n(automatically uploaded)","3":"- updated documentation by Ingo Karkat, Thanks!, issue #1\n- Make State of plugin avaivable to extern (patch by Ingo Karkat, Thanks!, issue #2)\n- Ensure, padding of 'stl' works correctly (patch by Ingo Karkat, Thanks!, issue #3)\n- :q in DistractMode quits vim correctly\n- Save\/Restore User highlighting\n(automatically uploaded)","package":"DistractFree-0.5.vmb","4":"DistractFree-0.5.vmb","src_id":"20653","5":"20653","creation_date":"1376549393","6":"1376549393"},{"0":"4357","vim_version":"7.3","1":"7.3","script_version":"4","2":"4","version_comment":"- set\/restore guifont\n- updated colorscheme\n- remove font attribute from Normal highlighting\n- make current window the only window\n(automatically uploaded)","3":"- set\/restore guifont\n- updated colorscheme\n- remove font attribute from Normal highlighting\n- make current window the only window\n(automatically uploaded)","package":"DistractFree-0.4.vmb","4":"DistractFree-0.4.vmb","src_id":"19523","5":"19523","creation_date":"1361052096","6":"1361052096"},{"0":"4357","vim_version":"7.3","1":"7.3","script_version":"3","2":"3","version_comment":"Enable GLVS\n(automatically uploaded)","3":"Enable GLVS\n(automatically uploaded)","package":"DistractFree-0.3.vmb","4":"DistractFree-0.3.vmb","src_id":"19184","5":"19184","creation_date":"1355520751","6":"1355520751"},{"0":"4357","vim_version":"7.3","1":"7.3","script_version":"0.2","2":"0.2","version_comment":"Initial upload","3":"Initial upload","package":"DistractFree-0.2.vmb","4":"DistractFree-0.2.vmb","src_id":"19183","5":"19183","creation_date":"1355520410","6":"1355520410"}]},"4356":{"script_id":"4356","0":"4356","script_name":"Dscanner","1":"Dscanner","script_type":"ftplugin","2":"ftplugin","summary":"Autocompletion for the D language.","3":"Autocompletion for the D language.","description":"Dscanner is a D source code analyzer created by Hackerpilot. This plugin uses Dscanner to provide autocompletion for class\/struct\/object\/enum members, for function calls, and for scope and version statements.\r\n\r\nThis plugin is developed  under the Dscanner repository in GitHub:\r\nMain repo: https:\/\/github.com\/Hackerpilot\/Dscanner\r\nVim plugin repo: https:\/\/github.com\/Hackerpilot\/Dscanner\/tree\/master\/editors\/vim","4":"Dscanner is a D source code analyzer created by Hackerpilot. This plugin uses Dscanner to provide autocompletion for class\/struct\/object\/enum members, for function calls, and for scope and version statements.\r\n\r\nThis plugin is developed  under the Dscanner repository in GitHub:\r\nMain repo: https:\/\/github.com\/Hackerpilot\/Dscanner\r\nVim plugin repo: https:\/\/github.com\/Hackerpilot\/Dscanner\/tree\/master\/editors\/vim","install_details":"Installation and Configuration:\r\n\r\nPut the autoload and ftplugin folders in your vim runtime path.\r\n\r\nCompile dscanner and put it in your path, or set the global variable g:dscanner_path to where you put dscanner.\r\n\r\nIf you need to use an include path, use the global variable g:dscanner_includePath as a list of those paths.\r\n\r\n\r\nUsing on Windows:\r\n\r\nUnder Linux, Dscanner reads \/etc\/dmd.conf to get the default include paths. The equivalent file in Windows - 'sc.ini' - does not have a fixed location, so you need to configure the import paths manually. You need the \\src\\phobos and \\src\\druntime\\import folders from where you installed dmd. For example,\r\n\r\nlet g:dscanner_includePath=['C:\\Program Files\\dmd2\\src\\phobos','C:\\Program Files\\dmd2\\src\\druntime\\import']\r\n","5":"Installation and Configuration:\r\n\r\nPut the autoload and ftplugin folders in your vim runtime path.\r\n\r\nCompile dscanner and put it in your path, or set the global variable g:dscanner_path to where you put dscanner.\r\n\r\nIf you need to use an include path, use the global variable g:dscanner_includePath as a list of those paths.\r\n\r\n\r\nUsing on Windows:\r\n\r\nUnder Linux, Dscanner reads \/etc\/dmd.conf to get the default include paths. The equivalent file in Windows - 'sc.ini' - does not have a fixed location, so you need to configure the import paths manually. You need the \\src\\phobos and \\src\\druntime\\import folders from where you installed dmd. For example,\r\n\r\nlet g:dscanner_includePath=['C:\\Program Files\\dmd2\\src\\phobos','C:\\Program Files\\dmd2\\src\\druntime\\import']\r\n","first_name":"Idan","6":"Idan","last_name":"Arye","7":"Arye","releases":[{"0":"4356","vim_version":"7.3","1":"7.3","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"Dscanner.zip","4":"Dscanner.zip","src_id":"19174","5":"19174","creation_date":"1355357095","6":"1355357095"}]},"4355":{"script_id":"4355","0":"4355","script_name":"reStructuredText ftplugin","1":"reStructuredText ftplugin","script_type":"ftplugin","2":"ftplugin","summary":"Navigation and section handling for reStructuredText","3":"Navigation and section handling for reStructuredText","description":"This is a lightweight filetype plugin for reStructuredText files.\r\nIt features folding, navigation, and simple operations to manage sections.\r\n\r\n1. Folding\t\t\t\t\t\t\t*rst-folding*\r\n\r\nThe functionality of the plugin heavily depends on |folding| enabled\r\n(|'foldexpr'| is utilised to continuously inspect and cache definitions of\r\nsection decorations). As an extra bonus, folding allows you easily examine\r\nthe structure of the document.\r\n\r\nIf you prefer not to have any text folded set g:rst_fold_level or\r\nb:rst_fold_level variable in your |vimrc| to a substantially high value like 100.\r\n\r\n\t\t\t\t\t\t\t\t*:RstReset*\r\nI tried to reach a compromise between correctness and performance so the\r\nplugin relies on Vim to be notified on relevant changes. Section adornment\r\nstyles are cached internally so if you see something messed up, use :RstReset\r\ncommand to reinitialise internal plugin structures and parse text from scratch.\r\n\r\n2. Navigating Sections\t\t\t\t\t*rst-navigation*\r\n\r\nThe plugin overrides and enriches Vim standard navigation keys:\r\n\r\n]] - go forward to the start of the next sibling section\r\n\r\n<N>]] - search for the start of the next section which is N levels above the\r\ncurrent section\r\n\r\n[[ - go backward to the start of the section. If the cursor is already at\r\nthe start, go upwards to the next sibling section.\r\n\r\n<N>[[ - go up to the start of the parent section level N (in other words, 2[[\r\nwill navigate to the grandparent of the current section)\r\n\r\n][ - search forward to the end of the current section or, if the cursors is\r\nthere already, its prior sibling\r\n\r\n<N>][ - same as ][ but go to the end of the parent section which is N levels\r\nabove the current section.\r\n\r\n[] - search backward to the end of the previous sibling\r\n\r\n<N>[] - same as [] but look for the parent N levels above\r\n\r\n3. Navigating References\t\t\t\t*rst-references*\r\n\r\nThe plugin also creates normal mode mappings to follow references (section\r\nnames, citations, substitutions, hyperlinks)\r\n\r\n<LocalLeader>CTRL-] tries to follow a link under the cursor.\r\n<LocalLeader>] can be used to search for another matching target for last\r\nprocessed reference. Default value for <LocalLeader> is backslash.\r\n\r\nNOTE To avoid full-scale parsing, the plugin uses groups defined in rst |syntax|\r\nhighliting plugin shipped with Vim.\r\n\r\nAlso it is able to use some simple heuristics, the behaviour can be tuned via\r\ng:rstsearch_order variable.\r\n\r\n4. Adding Sections\t\t\t\t\t    *rst-add*\r\n\r\n<LocalLeader>O\r\n<LocalLeader>o - add a sibling above\/below current section\r\n\r\n<LocalLeader>A\r\n<LocalLeader>a - add a first\/last child for the current section. If the plugin\r\nhas not seen any adornments of this level, it invents one on its own.\r\n\r\nSee also |LocalLeader|\r\n\r\n5. Modifying sections\t\t\t\t\t    *rst-modify*\r\n\r\n<LocalLeader><\r\n<LocalLeader>> - promote\/demote current section making it one level higher or\r\nlower\r\n\r\n6. Customisation\t\t\t\t\t    *rst-customise*\r\n\r\nThe behaviour of the plugin can be customised through the following global\r\nvariables, please see ftplugin\/rst.vim for details: >\r\n\r\n    g:rsttitle_marks\r\n\r\n    g:rstfolding_alltitles\r\n\r\n    g:rstfolding_rxtitle\r\n    g:rstfolding_rxprintable\r\n    g:rstfolding_rxempty\r\n\r\n    g:rstfolding_rxtext\r\n\r\n    g:rstnav_rx\r\n\r\n    g:rstsearch_order - the list of methods used to follow links. Valid\r\n    entries are 'syntax', 'heuristics', 'user'. In the latter case you need to\r\n    define function g:RstUserSearch.\r\n","4":"This is a lightweight filetype plugin for reStructuredText files.\r\nIt features folding, navigation, and simple operations to manage sections.\r\n\r\n1. Folding\t\t\t\t\t\t\t*rst-folding*\r\n\r\nThe functionality of the plugin heavily depends on |folding| enabled\r\n(|'foldexpr'| is utilised to continuously inspect and cache definitions of\r\nsection decorations). As an extra bonus, folding allows you easily examine\r\nthe structure of the document.\r\n\r\nIf you prefer not to have any text folded set g:rst_fold_level or\r\nb:rst_fold_level variable in your |vimrc| to a substantially high value like 100.\r\n\r\n\t\t\t\t\t\t\t\t*:RstReset*\r\nI tried to reach a compromise between correctness and performance so the\r\nplugin relies on Vim to be notified on relevant changes. Section adornment\r\nstyles are cached internally so if you see something messed up, use :RstReset\r\ncommand to reinitialise internal plugin structures and parse text from scratch.\r\n\r\n2. Navigating Sections\t\t\t\t\t*rst-navigation*\r\n\r\nThe plugin overrides and enriches Vim standard navigation keys:\r\n\r\n]] - go forward to the start of the next sibling section\r\n\r\n<N>]] - search for the start of the next section which is N levels above the\r\ncurrent section\r\n\r\n[[ - go backward to the start of the section. If the cursor is already at\r\nthe start, go upwards to the next sibling section.\r\n\r\n<N>[[ - go up to the start of the parent section level N (in other words, 2[[\r\nwill navigate to the grandparent of the current section)\r\n\r\n][ - search forward to the end of the current section or, if the cursors is\r\nthere already, its prior sibling\r\n\r\n<N>][ - same as ][ but go to the end of the parent section which is N levels\r\nabove the current section.\r\n\r\n[] - search backward to the end of the previous sibling\r\n\r\n<N>[] - same as [] but look for the parent N levels above\r\n\r\n3. Navigating References\t\t\t\t*rst-references*\r\n\r\nThe plugin also creates normal mode mappings to follow references (section\r\nnames, citations, substitutions, hyperlinks)\r\n\r\n<LocalLeader>CTRL-] tries to follow a link under the cursor.\r\n<LocalLeader>] can be used to search for another matching target for last\r\nprocessed reference. Default value for <LocalLeader> is backslash.\r\n\r\nNOTE To avoid full-scale parsing, the plugin uses groups defined in rst |syntax|\r\nhighliting plugin shipped with Vim.\r\n\r\nAlso it is able to use some simple heuristics, the behaviour can be tuned via\r\ng:rstsearch_order variable.\r\n\r\n4. Adding Sections\t\t\t\t\t    *rst-add*\r\n\r\n<LocalLeader>O\r\n<LocalLeader>o - add a sibling above\/below current section\r\n\r\n<LocalLeader>A\r\n<LocalLeader>a - add a first\/last child for the current section. If the plugin\r\nhas not seen any adornments of this level, it invents one on its own.\r\n\r\nSee also |LocalLeader|\r\n\r\n5. Modifying sections\t\t\t\t\t    *rst-modify*\r\n\r\n<LocalLeader><\r\n<LocalLeader>> - promote\/demote current section making it one level higher or\r\nlower\r\n\r\n6. Customisation\t\t\t\t\t    *rst-customise*\r\n\r\nThe behaviour of the plugin can be customised through the following global\r\nvariables, please see ftplugin\/rst.vim for details: >\r\n\r\n    g:rsttitle_marks\r\n\r\n    g:rstfolding_alltitles\r\n\r\n    g:rstfolding_rxtitle\r\n    g:rstfolding_rxprintable\r\n    g:rstfolding_rxempty\r\n\r\n    g:rstfolding_rxtext\r\n\r\n    g:rstnav_rx\r\n\r\n    g:rstsearch_order - the list of methods used to follow links. Valid\r\n    entries are 'syntax', 'heuristics', 'user'. In the latter case you need to\r\n    define function g:RstUserSearch.\r\n","install_details":":so ft_rst.vmb\r\n\r\nAlso available from https:\/\/bitbucket.org\/khorser\/vim-rst-ftplugin and https:\/\/github.com\/khorser\/vim-rst-ftplugin\r\n","5":":so ft_rst.vmb\r\n\r\nAlso available from https:\/\/bitbucket.org\/khorser\/vim-rst-ftplugin and https:\/\/github.com\/khorser\/vim-rst-ftplugin\r\n","first_name":"Sergey","6":"Sergey","last_name":"Khorev","7":"Khorev","releases":[{"0":"4355","vim_version":"7.3","1":"7.3","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"ft_rst.vmb","4":"ft_rst.vmb","src_id":"19172","5":"19172","creation_date":"1355309549","6":"1355309549"}]},"4354":{"script_id":"4354","0":"4354","script_name":"indentLine.vim","1":"indentLine.vim","script_type":"utility","2":"utility","summary":"An indent guides plugin displaying thin vertical lines. ","3":"An indent guides plugin displaying thin vertical lines. ","description":"This plugin is used for displaying thin vertical lines at each indentation level for code indented with spaces. For code indented with tabs I think there is no need to support it, because you can use :set list lcs=tab:\\|\\ (here is a space).\r\n\r\nRequirements:\r\nThis plugin takes advantage of the newly provided conceal feature in Vim 7.3, so this plugin will not work with lower versions of Vim.\r\n\r\nInstallation:\r\nTo install the plugin just put the plugin files in your ~\/.vim (Linux) or ~\/vimfiles (Windows).\r\n\r\nIf you use a plugin manager you can put the whole directory into your ~\/.vim\/bundle\/ directory (Pathogen) or add the line Bundle 'Yggdroot\/indentLine' to your .vimrc (Vundle).\r\n\r\nCustomization:\r\nYou can change the color of indentLines:\r\nfor Vim, set g:indentLine_color_term in your .vimrc, e.g. let g:indentLine_color_term = 239,\r\nfor GVim, set g:indentLine_color_gui in your .vimrc, e.g. let g:indentLine_color_gui = '#A4E57E'\r\n\r\nYou can also change the indentLine char:\r\nfor both Vim and GVim, set let g:indentLine_char = 'c' where 'c' can be any ASCII character. You can also use one of \u00c2\u00a6, ┆ or │ to display more beautiful lines. However, these characters will only work with files whose encoding is UTF-8.\r\n\r\nGithub:\r\nhttps:\/\/github.com\/Yggdroot\/indentLine\r\n\r\nScreenshots: \r\nhttp:\/\/i.imgur.com\/KVi0T.jpg\r\nhttp:\/\/imgur.com\/zhV1v\r\nhttp:\/\/imgur.com\/cENlq\r\nhttp:\/\/i.imgur.com\/tLYkb79.png\r\nhttp:\/\/i.imgur.com\/Rfr0Nor.png","4":"This plugin is used for displaying thin vertical lines at each indentation level for code indented with spaces. For code indented with tabs I think there is no need to support it, because you can use :set list lcs=tab:\\|\\ (here is a space).\r\n\r\nRequirements:\r\nThis plugin takes advantage of the newly provided conceal feature in Vim 7.3, so this plugin will not work with lower versions of Vim.\r\n\r\nInstallation:\r\nTo install the plugin just put the plugin files in your ~\/.vim (Linux) or ~\/vimfiles (Windows).\r\n\r\nIf you use a plugin manager you can put the whole directory into your ~\/.vim\/bundle\/ directory (Pathogen) or add the line Bundle 'Yggdroot\/indentLine' to your .vimrc (Vundle).\r\n\r\nCustomization:\r\nYou can change the color of indentLines:\r\nfor Vim, set g:indentLine_color_term in your .vimrc, e.g. let g:indentLine_color_term = 239,\r\nfor GVim, set g:indentLine_color_gui in your .vimrc, e.g. let g:indentLine_color_gui = '#A4E57E'\r\n\r\nYou can also change the indentLine char:\r\nfor both Vim and GVim, set let g:indentLine_char = 'c' where 'c' can be any ASCII character. You can also use one of \u00c2\u00a6, ┆ or │ to display more beautiful lines. However, these characters will only work with files whose encoding is UTF-8.\r\n\r\nGithub:\r\nhttps:\/\/github.com\/Yggdroot\/indentLine\r\n\r\nScreenshots: \r\nhttp:\/\/i.imgur.com\/KVi0T.jpg\r\nhttp:\/\/imgur.com\/zhV1v\r\nhttp:\/\/imgur.com\/cENlq\r\nhttp:\/\/i.imgur.com\/tLYkb79.png\r\nhttp:\/\/i.imgur.com\/Rfr0Nor.png","install_details":"","5":"","first_name":"Yggdroot","6":"Yggdroot","last_name":"Chen","7":"Chen","releases":[{"0":"4354","vim_version":"7.3","1":"7.3","script_version":"1.0.6","2":"1.0.6","version_comment":"-add support for showing leading white spaces","3":"-add support for showing leading white spaces","package":"indentLine.zip","4":"indentLine.zip","src_id":"22741","5":"22741","creation_date":"1419767684","6":"1419767684"},{"0":"4354","vim_version":"7.3","1":"7.3","script_version":"1.0.5","2":"1.0.5","version_comment":"-trivial bug fix\r\n-file type support and some new feature\r\n-make performance better","3":"-trivial bug fix\r\n-file type support and some new feature\r\n-make performance better","package":"indentLine.zip","4":"indentLine.zip","src_id":"19847","5":"19847","creation_date":"1366283542","6":"1366283542"},{"0":"4354","vim_version":"7.3","1":"7.3","script_version":"1.0.4","2":"1.0.4","version_comment":"-add command to toggle the indentLine \r\n-use shiftwidth of modeline if modelines have set shiftwidth \r\n-modify command ResetIndentLines as IndentLinesReset\r\n-doc updated","3":"-add command to toggle the indentLine \r\n-use shiftwidth of modeline if modelines have set shiftwidth \r\n-modify command ResetIndentLines as IndentLinesReset\r\n-doc updated","package":"indentLine.zip","4":"indentLine.zip","src_id":"19573","5":"19573","creation_date":"1361940016","6":"1361940016"},{"0":"4354","vim_version":"7.3","1":"7.3","script_version":"1.0.3","2":"1.0.3","version_comment":"change default indentLine char to \"\u00c2\u00a6\" if encoding is utf-8\r\nchange color in light background to grey65","3":"change default indentLine char to \"\u00c2\u00a6\" if encoding is utf-8\r\nchange color in light background to grey65","package":"indentLine.zip","4":"indentLine.zip","src_id":"19325","5":"19325","creation_date":"1357551218","6":"1357551218"},{"0":"4354","vim_version":"7.3","1":"7.3","script_version":"1.0.2","2":"1.0.2","version_comment":"-move plugin file to after\/plugin\r\n-make indentline char configurable\r\n-add options to specify indent lines color\r\n-add option to specify indent level\r\n-add plugin doc file\r\n-allow the indent guides to be redrawn if 'shiftwidth' changes","3":"-move plugin file to after\/plugin\r\n-make indentline char configurable\r\n-add options to specify indent lines color\r\n-add option to specify indent level\r\n-add plugin doc file\r\n-allow the indent guides to be redrawn if 'shiftwidth' changes","package":"indentLine.zip","4":"indentLine.zip","src_id":"19240","5":"19240","creation_date":"1356533649","6":"1356533649"},{"0":"4354","vim_version":"7.3","1":"7.3","script_version":"1.0.1","2":"1.0.1","version_comment":"Initial upload","3":"Initial upload","package":"indentLine.vim","4":"indentLine.vim","src_id":"19171","5":"19171","creation_date":"1355306728","6":"1355306728"}]},"4353":{"script_id":"4353","0":"4353","script_name":"line_length.vim","1":"line_length.vim","script_type":"utility","2":"utility","summary":"Toggle hilighting of too long lines","3":"Toggle hilighting of too long lines","description":"This script adds the :LineLength command that can be used to toggle\r\nhilighting of the part of lines that are too long.\r\n\r\nThe code can also be found here: https:\/\/github.com\/aklt\/vim-line_length\r\n\r\nImportant: Please open an issue at github if you find a problem!\r\n\r\nAdd a mapping to toggle highlighting of long lines:\r\n\r\n    nmap R :LineLength<CR>\r\n\r\nThe max. line length can be set in a modeline in a comment within \r\none of the 5 last lines of a file:\r\n\r\n    \/\/ ...\r\n    \/\/ Lines longer than 80 characters will get a blue background\r\n    \/\/ ll: 80 blue\r\n\r\nCustomize defaults:\r\n\r\n    let g:LineLength_LineLength = 80\r\n    let g:LineLength_guibg = 'red'\r\n    let g:LineLength_ctermbg = 1\r\n\r\n","4":"This script adds the :LineLength command that can be used to toggle\r\nhilighting of the part of lines that are too long.\r\n\r\nThe code can also be found here: https:\/\/github.com\/aklt\/vim-line_length\r\n\r\nImportant: Please open an issue at github if you find a problem!\r\n\r\nAdd a mapping to toggle highlighting of long lines:\r\n\r\n    nmap R :LineLength<CR>\r\n\r\nThe max. line length can be set in a modeline in a comment within \r\none of the 5 last lines of a file:\r\n\r\n    \/\/ ...\r\n    \/\/ Lines longer than 80 characters will get a blue background\r\n    \/\/ ll: 80 blue\r\n\r\nCustomize defaults:\r\n\r\n    let g:LineLength_LineLength = 80\r\n    let g:LineLength_guibg = 'red'\r\n    let g:LineLength_ctermbg = 1\r\n\r\n","install_details":"unzip, open with vim and source it.  Requires the Vimball plugin","5":"unzip, open with vim and source it.  Requires the Vimball plugin","first_name":"Anders","6":"Anders","last_name":"Th\u00c3\u00b8gersen","7":"Th\u00c3\u00b8gersen","releases":[{"0":"4353","vim_version":"7.0","1":"7.0","script_version":"0.0.1","2":"0.0.1","version_comment":"Initial upload","3":"Initial upload","package":"line_length.vmb.zip","4":"line_length.vmb.zip","src_id":"19166","5":"19166","creation_date":"1355249504","6":"1355249504"}]},"4352":{"script_id":"4352","0":"4352","script_name":"tex_alt","1":"tex_alt","script_type":"ftplugin","2":"ftplugin","summary":"Lightweight alternative support for TeX","3":"Lightweight alternative support for TeX","description":"tex_alt is an alternative, lightweight support for LaTeX in Vim. There are many bundles that aim to do the same thing and possibly do it better, but this one is mine. Also, it\u00e2\u0080\u0099s much faster.\r\n\r\ntex_alt provides:\r\n* lighter, faster and less complete syntax highlighting,\r\n* autocompletion for commands, files and tags,\r\n* auto tag regeneration on file open and save,\r\n* basic compilation with a QuickFix window,\r\n* some more convenience settings.\r\n\r\ntex_alt doesn\u00e2\u0080\u0099t provide:\r\n* support for BibTeX,\r\n* support for mathematics, and\r\n* almost and IDE kind of behaviour in general.\r\n\r\nScreenshot: http:\/\/imageshack.us\/photo\/my-images\/600\/texalt02.png\/","4":"tex_alt is an alternative, lightweight support for LaTeX in Vim. There are many bundles that aim to do the same thing and possibly do it better, but this one is mine. Also, it\u00e2\u0080\u0099s much faster.\r\n\r\ntex_alt provides:\r\n* lighter, faster and less complete syntax highlighting,\r\n* autocompletion for commands, files and tags,\r\n* auto tag regeneration on file open and save,\r\n* basic compilation with a QuickFix window,\r\n* some more convenience settings.\r\n\r\ntex_alt doesn\u00e2\u0080\u0099t provide:\r\n* support for BibTeX,\r\n* support for mathematics, and\r\n* almost and IDE kind of behaviour in general.\r\n\r\nScreenshot: http:\/\/imageshack.us\/photo\/my-images\/600\/texalt02.png\/","install_details":"Copy the files named tex_alt.* to appropriate folders in ~\/.vim.\r\nCopy or append _ctags to ~\/.ctags.\r\n\r\nSee README for additional details.","5":"Copy the files named tex_alt.* to appropriate folders in ~\/.vim.\r\nCopy or append _ctags to ~\/.ctags.\r\n\r\nSee README for additional details.","first_name":"kamil","6":"kamil","last_name":"stachowski","7":"stachowski","releases":[{"0":"4352","vim_version":"7.0","1":"7.0","script_version":"0.21","2":"0.21","version_comment":"bugfixes mostly\r\nadded more snippets\r\nadded easier navigation through wrapped lines","3":"bugfixes mostly\r\nadded more snippets\r\nadded easier navigation through wrapped lines","package":"tex_alt.tar.gz","4":"tex_alt.tar.gz","src_id":"19238","5":"19238","creation_date":"1356392746","6":"1356392746"},{"0":"4352","vim_version":"7.0","1":"7.0","script_version":"0.2","2":"0.2","version_comment":"syntax rewritten from scratch\r\nadded autocompletion for commands, includes and tags\r\nadded auto tag regeneration\r\nadded graphics to _ctags","3":"syntax rewritten from scratch\r\nadded autocompletion for commands, includes and tags\r\nadded auto tag regeneration\r\nadded graphics to _ctags","package":"tex_alt.tar.gz","4":"tex_alt.tar.gz","src_id":"19206","5":"19206","creation_date":"1355873540","6":"1355873540"},{"0":"4352","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"tex_alt.tar.gz","4":"tex_alt.tar.gz","src_id":"19157","5":"19157","creation_date":"1355098641","6":"1355098641"}]},"4351":{"script_id":"4351","0":"4351","script_name":"whitespaste.vim","1":"whitespaste.vim","script_type":"utility","2":"utility","summary":"Automatically adjust blank lines when pasting","3":"Automatically adjust blank lines when pasting","description":"Github project: https:\/\/github.com\/AndrewRadev\/whitespaste.vim\r\n\r\nThis plugin remaps the standard \"p\" and \"P\" mappings to enhance their functionality. When pasting, it compresses all blank lines that result from the paste to a single one (or none, at the top and bottom of the file). That way, even if you copy any leftover whitespace, it'll be neatly trimmed to just one line. This takes effect only for linewise pasting, since it's not entirely clear what the behaviour should be for characterwise and blockwise pasting.\r\n\r\nIf you don't want to clobber your default \"p\" and \"P\" mappings, you can make whitespaste use different ones by setting two predefined variables:\r\n\r\n    let g:whitespaste_before_mapping = ',P'\r\n    let g:whitespaste_after_mapping  = ',p'\r\n\r\nIf you need more fine-grained control, you can disable mappings altogether by setting both of these variables to empty strings. You can then use the three provided <Plug> mappings for your purposes. For example:\r\n\r\n    let g:whitespaste_before_mapping = ''\r\n    let g:whitespaste_after_mapping  = ''\r\n\r\n    nmap ,P <Plug>WhitespasteBefore\r\n    nmap ,p <Plug>WhitespasteAfter\r\n\r\n    xmap ,P <Plug>WhitespasteVisual\r\n    xmap ,p <Plug>WhitespasteVisual\r\n\r\nThe plugin also takes care of special cases like pasting functions\/methods, if-clauses and so on. Currently, these special cases work only with ruby and vimscript, but see \":help whitespaste-extending\" to find out how you can extend the plugin for a different language or change it to fit your own coding style.\r\n\r\nWhitespaste can play well with other plugins like vim-pasta. The underlying paste command that is being executed is available as a global variable and can be changed. For example, here's how you could combine whitespaste with vim-pasta:\r\n\r\n    \" first, disable vim-pasta's mappings\r\n    let g:pasta_enabled_filetypes = []\r\n\r\n    \" then, set whitespaste's paste commands to execute vim-pasta's mappings\r\n    let g:whitespaste_paste_before_command = \"normal \\<Plug>BeforePasta\"\r\n    let g:whitespaste_paste_after_command  = \"normal \\<Plug>AfterPasta\"\r\n    let g:whitespaste_paste_visual_command = \"normal gv\\<Plug>VisualPasta\"\r\n\r\nIt's important to note that the plugin will take care of adjusting registers, so that you don't have to compensate for that in the command your provide. For example, even if you set the command to \"normal! p\", you could still use whitespaste with different registers and it would work correctly.","4":"Github project: https:\/\/github.com\/AndrewRadev\/whitespaste.vim\r\n\r\nThis plugin remaps the standard \"p\" and \"P\" mappings to enhance their functionality. When pasting, it compresses all blank lines that result from the paste to a single one (or none, at the top and bottom of the file). That way, even if you copy any leftover whitespace, it'll be neatly trimmed to just one line. This takes effect only for linewise pasting, since it's not entirely clear what the behaviour should be for characterwise and blockwise pasting.\r\n\r\nIf you don't want to clobber your default \"p\" and \"P\" mappings, you can make whitespaste use different ones by setting two predefined variables:\r\n\r\n    let g:whitespaste_before_mapping = ',P'\r\n    let g:whitespaste_after_mapping  = ',p'\r\n\r\nIf you need more fine-grained control, you can disable mappings altogether by setting both of these variables to empty strings. You can then use the three provided <Plug> mappings for your purposes. For example:\r\n\r\n    let g:whitespaste_before_mapping = ''\r\n    let g:whitespaste_after_mapping  = ''\r\n\r\n    nmap ,P <Plug>WhitespasteBefore\r\n    nmap ,p <Plug>WhitespasteAfter\r\n\r\n    xmap ,P <Plug>WhitespasteVisual\r\n    xmap ,p <Plug>WhitespasteVisual\r\n\r\nThe plugin also takes care of special cases like pasting functions\/methods, if-clauses and so on. Currently, these special cases work only with ruby and vimscript, but see \":help whitespaste-extending\" to find out how you can extend the plugin for a different language or change it to fit your own coding style.\r\n\r\nWhitespaste can play well with other plugins like vim-pasta. The underlying paste command that is being executed is available as a global variable and can be changed. For example, here's how you could combine whitespaste with vim-pasta:\r\n\r\n    \" first, disable vim-pasta's mappings\r\n    let g:pasta_enabled_filetypes = []\r\n\r\n    \" then, set whitespaste's paste commands to execute vim-pasta's mappings\r\n    let g:whitespaste_paste_before_command = \"normal \\<Plug>BeforePasta\"\r\n    let g:whitespaste_paste_after_command  = \"normal \\<Plug>AfterPasta\"\r\n    let g:whitespaste_paste_visual_command = \"normal gv\\<Plug>VisualPasta\"\r\n\r\nIt's important to note that the plugin will take care of adjusting registers, so that you don't have to compensate for that in the command your provide. For example, even if you set the command to \"normal! p\", you could still use whitespaste with different registers and it would work correctly.","install_details":"There are several ways to install the plugin. The recommended one is by using Tim Pope's pathogen (http:\/\/www.vim.org\/scripts\/script.php?script_id=2332). In that case, you can clone the plugin's git repository like so:\r\n\r\n    git clone git:\/\/github.com\/AndrewRadev\/whitespaste.vim.git ~\/.vim\/bundle\/whitespaste\r\n\r\nIf your vim configuration is under git version control, you could also set up the repository as a submodule, which would allow you to update more easily. The command is (provided you're in ~\/.vim):\r\n\r\n    git submodule add git:\/\/github.com\/AndrewRadev\/whitespaste.vim.git bundle\/whitespaste\r\n\r\nAnother way is to simply copy all the essential directories inside the ~\/.vim directory: plugin, autoload, doc.","5":"There are several ways to install the plugin. The recommended one is by using Tim Pope's pathogen (http:\/\/www.vim.org\/scripts\/script.php?script_id=2332). In that case, you can clone the plugin's git repository like so:\r\n\r\n    git clone git:\/\/github.com\/AndrewRadev\/whitespaste.vim.git ~\/.vim\/bundle\/whitespaste\r\n\r\nIf your vim configuration is under git version control, you could also set up the repository as a submodule, which would allow you to update more easily. The command is (provided you're in ~\/.vim):\r\n\r\n    git submodule add git:\/\/github.com\/AndrewRadev\/whitespaste.vim.git bundle\/whitespaste\r\n\r\nAnother way is to simply copy all the essential directories inside the ~\/.vim directory: plugin, autoload, doc.","first_name":"Andrew","6":"Andrew","last_name":"Radev","7":"Radev","releases":[{"0":"4351","vim_version":"7.0","1":"7.0","script_version":"0.3.0","2":"0.3.0","version_comment":"- Python support\r\n- Simple Elixir support\r\n- Various bugfixes","3":"- Python support\r\n- Simple Elixir support\r\n- Various bugfixes","package":"whitespaste.zip","4":"whitespaste.zip","src_id":"26040","5":"26040","creation_date":"1528652095","6":"1528652095"},{"0":"4351","vim_version":"7.0","1":"7.0","script_version":"v0.2.0","2":"v0.2.0","version_comment":"- Support for HTML tags\r\n- Pasting with a count\r\n- Various bugfixes","3":"- Support for HTML tags\r\n- Pasting with a count\r\n- Various bugfixes","package":"whitespaste.zip","4":"whitespaste.zip","src_id":"21386","5":"21386","creation_date":"1390763742","6":"1390763742"},{"0":"4351","vim_version":"7.0","1":"7.0","script_version":"0.1.0","2":"0.1.0","version_comment":"Initial upload","3":"Initial upload","package":"whitespaste.zip","4":"whitespaste.zip","src_id":"19155","5":"19155","creation_date":"1355057066","6":"1355057066"}]},"4350":{"script_id":"4350","0":"4350","script_name":"Inferno sh syntax","1":"Inferno sh syntax","script_type":"syntax","2":"syntax","summary":"OS Inferno shell syntax highlight","3":"OS Inferno shell syntax highlight","description":"Syntax highlight for OS Inferno shell (\/dis\/sh.dis).","4":"Syntax highlight for OS Inferno shell (\/dis\/sh.dis).","install_details":"Copy downloaded infsh.vim to ~\/.vim\/syntax\/\r\n\r\nTo autodetect filetype add this to ~\/.vimrc or .vim\/ftdetect\/infsh.vim:\r\nautocmd BufNewFile,BufRead profile,wmsetup\tsetf infsh\r\nautocmd BufNewFile,BufRead *\tif getline(1) =~ '^#!\/dis\/sh' || getline(1) =~ '^load ' || getline(2) =~ '^load ' | setlocal ft=infsh | endif","5":"Copy downloaded infsh.vim to ~\/.vim\/syntax\/\r\n\r\nTo autodetect filetype add this to ~\/.vimrc or .vim\/ftdetect\/infsh.vim:\r\nautocmd BufNewFile,BufRead profile,wmsetup\tsetf infsh\r\nautocmd BufNewFile,BufRead *\tif getline(1) =~ '^#!\/dis\/sh' || getline(1) =~ '^load ' || getline(2) =~ '^load ' | setlocal ft=infsh | endif","first_name":"Alex","6":"Alex","last_name":"Efros","7":"Efros","releases":[{"0":"4350","vim_version":"7.0","1":"7.0","script_version":"1.10","2":"1.10","version_comment":"add ability to include this syntax\r\nminor fix for comments","3":"add ability to include this syntax\r\nminor fix for comments","package":"infsh.vim","4":"infsh.vim","src_id":"19153","5":"19153","creation_date":"1355055552","6":"1355055552"},{"0":"4350","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"infsh.vim","4":"infsh.vim","src_id":"19151","5":"19151","creation_date":"1355044195","6":"1355044195"}]},"4349":{"script_id":"4349","0":"4349","script_name":"gruvbox","1":"gruvbox","script_type":"color scheme","2":"color scheme","summary":"Retro groove color scheme for Vim","3":"Retro groove color scheme for Vim","description":"Homesite: https:\/\/github.com\/morhetz\/gruvbox\r\n\r\nGruvbox is heavily inspired by badwolf (https:\/\/github.com\/sjl\/badwolf), jellybeans (https:\/\/github.com\/nanotech\/jellybeans.vim) and solarized (http:\/\/ethanschoonover.com\/solarized).\r\n\r\nDesigned as a bright theme with pastel \\'retro groove\\' colors and light\/dark mode switching in the way of solarized. The main focus when developing Gruvbox is to keep colors easily distinguishable, contrast enough and still pleasant for the eyes.\r\n\r\nScreenshots\r\n-----------\r\n\r\nRefer Gallery (https:\/\/github.com\/morhetz\/gruvbox\/wiki\/Gallery) for more syntax-specific screenshots.\r\n\r\nDark mode (http:\/\/i.imgur.com\/2870c.png)\r\nLight mode (http:\/\/i.imgur.com\/oS9I3.png)\r\n\r\nFeatures\r\n--------\r\n\r\n* Lots of style-customization options (contrast, color invertion, italics usage etc.)\r\n* Extended filetype highlighting: Html, Xml, Vim, Clojure, C, Python, JavaScript, CoffeeScript, Ruby, Objective-C, Go, Lua, MoonScript, Java\r\n* Supported plugins: EasyMotion, vim-sneak, Indent Guides, indentLine, Rainbow Parentheses, Airline, GitGutter, Signify, ShowMarks, Signature, Syntastic, CtrlP, Startify\r\n\r\nUsage\r\n-----\r\n\r\ngruvbox comes in two modes, dark and light. To toggle between them with F5 you can add these to your .vimrc\r\n\r\n\tmap <silent> <F5> :call gruvbox#bg_toggle()<CR>\r\n\timap <silent> <F5> <ESC>:call gruvbox#bg_toggle()<CR>a\r\n\tvmap <silent> <F5> <ESC>:call gruvbox#bg_toggle()<CR>gv\r\n\r\nJust setting background to an appropriate value would work as well\r\n\r\n\tset bg=dark    \" Setting dark mode\r\n\tset bg=light   \" Setting light mode\r\n\r\nSince gruvbox inverts cursor color, it could be awkward to determine current position, when the search is highlighted. To get single cursor color while searching, map these gruvbox functions same way:\r\n\r\n\tnnoremap <silent> <Leader><Space> :call gruvbox#hls_toggle()<CR>\r\n\tinoremap <silent> <Leader><Space> <ESC>:call gruvbox#hls_toggle()<CR>a\r\n\tvnoremap <silent> <Leader><Space> <ESC>:call gruvbox#hls_toggle()<CR>gv\r\n \r\n\tnnoremap <silent> <CR> :call gruvbox#hls_hide()<CR><CR>\r\n  \r\n\tnnoremap * :let @\/ = \"\"<CR>:call gruvbox#hls_show()<CR>*\r\n\tnnoremap \/ :let @\/ = \"\"<CR>:call gruvbox#hls_show()<CR>\/\r\n\tnnoremap ? :let @\/ = \"\"<CR>:call gruvbox#hls_show()<CR>?\r\n\r\nSo you'll get `g:gruvbox_hls_cursor` (orange by default) cursor color when highlight search is on and inverted one otherwise. With such mappings you could also toggle search highlight on and off with <Leader><Space> and hide it with Enter.\r\n\r\nToDo\r\n----\r\n\r\n* Filetype syntax highlighting (R, TeX and I'm still dissatisfied with CSS)\r\n* Plugin support (MiniBufExplorer, Tagbar)\r\n* Airline theme\r\n\r\nTroubleshooting, Configuration, Functions\r\n-------------------------------------------------\r\n\r\nPlease refer homesite (https:\/\/github.com\/morhetz\/gruvbox)\r\n\r\nLicense\r\n-------\r\nLicensed under MIT\/X11","4":"Homesite: https:\/\/github.com\/morhetz\/gruvbox\r\n\r\nGruvbox is heavily inspired by badwolf (https:\/\/github.com\/sjl\/badwolf), jellybeans (https:\/\/github.com\/nanotech\/jellybeans.vim) and solarized (http:\/\/ethanschoonover.com\/solarized).\r\n\r\nDesigned as a bright theme with pastel \\'retro groove\\' colors and light\/dark mode switching in the way of solarized. The main focus when developing Gruvbox is to keep colors easily distinguishable, contrast enough and still pleasant for the eyes.\r\n\r\nScreenshots\r\n-----------\r\n\r\nRefer Gallery (https:\/\/github.com\/morhetz\/gruvbox\/wiki\/Gallery) for more syntax-specific screenshots.\r\n\r\nDark mode (http:\/\/i.imgur.com\/2870c.png)\r\nLight mode (http:\/\/i.imgur.com\/oS9I3.png)\r\n\r\nFeatures\r\n--------\r\n\r\n* Lots of style-customization options (contrast, color invertion, italics usage etc.)\r\n* Extended filetype highlighting: Html, Xml, Vim, Clojure, C, Python, JavaScript, CoffeeScript, Ruby, Objective-C, Go, Lua, MoonScript, Java\r\n* Supported plugins: EasyMotion, vim-sneak, Indent Guides, indentLine, Rainbow Parentheses, Airline, GitGutter, Signify, ShowMarks, Signature, Syntastic, CtrlP, Startify\r\n\r\nUsage\r\n-----\r\n\r\ngruvbox comes in two modes, dark and light. To toggle between them with F5 you can add these to your .vimrc\r\n\r\n\tmap <silent> <F5> :call gruvbox#bg_toggle()<CR>\r\n\timap <silent> <F5> <ESC>:call gruvbox#bg_toggle()<CR>a\r\n\tvmap <silent> <F5> <ESC>:call gruvbox#bg_toggle()<CR>gv\r\n\r\nJust setting background to an appropriate value would work as well\r\n\r\n\tset bg=dark    \" Setting dark mode\r\n\tset bg=light   \" Setting light mode\r\n\r\nSince gruvbox inverts cursor color, it could be awkward to determine current position, when the search is highlighted. To get single cursor color while searching, map these gruvbox functions same way:\r\n\r\n\tnnoremap <silent> <Leader><Space> :call gruvbox#hls_toggle()<CR>\r\n\tinoremap <silent> <Leader><Space> <ESC>:call gruvbox#hls_toggle()<CR>a\r\n\tvnoremap <silent> <Leader><Space> <ESC>:call gruvbox#hls_toggle()<CR>gv\r\n \r\n\tnnoremap <silent> <CR> :call gruvbox#hls_hide()<CR><CR>\r\n  \r\n\tnnoremap * :let @\/ = \"\"<CR>:call gruvbox#hls_show()<CR>*\r\n\tnnoremap \/ :let @\/ = \"\"<CR>:call gruvbox#hls_show()<CR>\/\r\n\tnnoremap ? :let @\/ = \"\"<CR>:call gruvbox#hls_show()<CR>?\r\n\r\nSo you'll get `g:gruvbox_hls_cursor` (orange by default) cursor color when highlight search is on and inverted one otherwise. With such mappings you could also toggle search highlight on and off with <Leader><Space> and hide it with Enter.\r\n\r\nToDo\r\n----\r\n\r\n* Filetype syntax highlighting (R, TeX and I'm still dissatisfied with CSS)\r\n* Plugin support (MiniBufExplorer, Tagbar)\r\n* Airline theme\r\n\r\nTroubleshooting, Configuration, Functions\r\n-------------------------------------------------\r\n\r\nPlease refer homesite (https:\/\/github.com\/morhetz\/gruvbox)\r\n\r\nLicense\r\n-------\r\nLicensed under MIT\/X11","install_details":"","5":"","first_name":"Pavel","6":"Pavel","last_name":"Pertsev","7":"Pertsev","releases":[{"0":"4349","vim_version":"7.0","1":"7.0","script_version":"1.3.5","2":"1.3.5","version_comment":"First full-featured release","3":"First full-featured release","package":"gruvbox-1.3.5.zip","4":"gruvbox-1.3.5.zip","src_id":"21639","5":"21639","creation_date":"1395211511","6":"1395211511"},{"0":"4349","vim_version":"7.0","1":"7.0","script_version":"0.0.8","2":"0.0.8","version_comment":"Initial upload","3":"Initial upload","package":"gruvbox-0.0.8.zip","4":"gruvbox-0.0.8.zip","src_id":"19150","5":"19150","creation_date":"1355014448","6":"1355014448"}]},"4348":{"script_id":"4348","0":"4348","script_name":"textobj-indblock","1":"textobj-indblock","script_type":"utility","2":"utility","summary":"Text objects for blocks of indentation whitespace","3":"Text objects for blocks of indentation whitespace","description":"The textobj-indblock plugin provides text objects to select a block of indentation whitespace based on the indentation of the current line.\r\n\r\nThis plugin supplements, and in this respect closely follows the example of the textobj-indent plugin (vimscript #2484).\r\n\r\nSee the documentation there to learn more.\r\n\r\nThis plugin depends on the framework provided by the textobj-user plugin, version 0.4.0 (vimscript #2100).\r\n","4":"The textobj-indblock plugin provides text objects to select a block of indentation whitespace based on the indentation of the current line.\r\n\r\nThis plugin supplements, and in this respect closely follows the example of the textobj-indent plugin (vimscript #2484).\r\n\r\nSee the documentation there to learn more.\r\n\r\nThis plugin depends on the framework provided by the textobj-user plugin, version 0.4.0 (vimscript #2100).\r\n","install_details":"Unzip the archive in your ~\/.vim directory.  (On Windows, replace \"~\/.vim\" with \"~\\vimfiles\" everywhere.)\r\n\r\nThe source is also hosted on github at https:\/\/github.com\/glts\/vim-textobj-indblock\r\nWith the Pathogen plugin manager the installation is as simple as:\r\n\r\ncd ~\/.vim\/bundle\r\ngit clone git:\/\/github.com\/glts\/vim-textobj-indblock.git textobj-indblock\r\n\r\nBut this plugin also plays well with the built-in Getscript and other plugin managers such as Vundle, vim-addon-manager, and vim-flavor.\r\n\r\nFinally, don't forget to run \":helptags\" on your doc directory to register the help file.\r\n","5":"Unzip the archive in your ~\/.vim directory.  (On Windows, replace \"~\/.vim\" with \"~\\vimfiles\" everywhere.)\r\n\r\nThe source is also hosted on github at https:\/\/github.com\/glts\/vim-textobj-indblock\r\nWith the Pathogen plugin manager the installation is as simple as:\r\n\r\ncd ~\/.vim\/bundle\r\ngit clone git:\/\/github.com\/glts\/vim-textobj-indblock.git textobj-indblock\r\n\r\nBut this plugin also plays well with the built-in Getscript and other plugin managers such as Vundle, vim-addon-manager, and vim-flavor.\r\n\r\nFinally, don't forget to run \":helptags\" on your doc directory to register the help file.\r\n","first_name":"David","6":"David","last_name":"B\u00c3\u00bcrgin","7":"B\u00c3\u00bcrgin","releases":[{"0":"4348","vim_version":"7.0","1":"7.0","script_version":"1.1.0","2":"1.1.0","version_comment":"Updated to textobj-user version 0.4.0.\r\nMinor doc fixes.\r\nBetter Getscript support.","3":"Updated to textobj-user version 0.4.0.\r\nMinor doc fixes.\r\nBetter Getscript support.","package":"textobj-indblock.zip","4":"textobj-indblock.zip","src_id":"19783","5":"19783","creation_date":"1365432095","6":"1365432095"},{"0":"4348","vim_version":"7.0","1":"7.0","script_version":"1.0.1","2":"1.0.1","version_comment":"Corrected \"GetLatestVimScripts\" script name","3":"Corrected \"GetLatestVimScripts\" script name","package":"textobj-indblock.zip","4":"textobj-indblock.zip","src_id":"19466","5":"19466","creation_date":"1359843525","6":"1359843525"},{"0":"4348","vim_version":"7.0","1":"7.0","script_version":"1.0.0","2":"1.0.0","version_comment":"Initial upload","3":"Initial upload","package":"textobj-indblock.zip","4":"textobj-indblock.zip","src_id":"19149","5":"19149","creation_date":"1354998947","6":"1354998947"}]},"4347":{"script_id":"4347","0":"4347","script_name":"qfnotes","1":"qfnotes","script_type":"utility","2":"utility","summary":"Use quickfix to annotate your files","3":"Use quickfix to annotate your files","description":"qfnotes is a plugin to annotate files and store annotations in separate file(s).\r\n\r\nInitially I wanted to extend vimscript #2216 but ended up rewriting it completely.\r\n\r\nShort information (see :h qfnotes for more commands and detailed documentation):\r\n<Leader>qn  - add a new note (or edit current)\r\n<Leader>qd  - delete selected note(s)\r\n<Leader>qe  - edit selected note(s)\r\n<Leader>qE  - edit selected note in a buffer\r\n\r\n<Leader>qs  - save current notes file\r\n<Leader>ql  - load notes file with default name\r\n\r\n:QFXLoad and :QFXSave - load and save annotations\r\n","4":"qfnotes is a plugin to annotate files and store annotations in separate file(s).\r\n\r\nInitially I wanted to extend vimscript #2216 but ended up rewriting it completely.\r\n\r\nShort information (see :h qfnotes for more commands and detailed documentation):\r\n<Leader>qn  - add a new note (or edit current)\r\n<Leader>qd  - delete selected note(s)\r\n<Leader>qe  - edit selected note(s)\r\n<Leader>qE  - edit selected note in a buffer\r\n\r\n<Leader>qs  - save current notes file\r\n<Leader>ql  - load notes file with default name\r\n\r\n:QFXLoad and :QFXSave - load and save annotations\r\n","install_details":":so qfnotes.vmb\r\nAlso available from https:\/\/bitbucket.org\/khorser\/vim-qfnotes and https:\/\/github.com\/khorser\/vim-qfnotes","5":":so qfnotes.vmb\r\nAlso available from https:\/\/bitbucket.org\/khorser\/vim-qfnotes and https:\/\/github.com\/khorser\/vim-qfnotes","first_name":"Sergey","6":"Sergey","last_name":"Khorev","7":"Khorev","releases":[{"0":"4347","vim_version":"7.3","1":"7.3","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"qfnotes.vmb","4":"qfnotes.vmb","src_id":"19144","5":"19144","creation_date":"1354971242","6":"1354971242"}]},"4346":{"script_id":"4346","0":"4346","script_name":"Providex V6.0 Syntax files","1":"Providex V6.0 Syntax files","script_type":"syntax","2":"syntax","summary":"Providex .vim files Syntax, Indent, colorscheme and ftplugin","3":"Providex .vim files Syntax, Indent, colorscheme and ftplugin","description":"ProvideX is a business basic developed by Sage Software Canada. \r\n\r\nThese files allow you to do Providex Programming in Vim (obviously).  It will do all the highlighting as in the Providex Editor itself with a few enhancments and additional features as providex by Vim.\r\nAlso if you don't use line numbers you can take Full advantage of the indentation file which makes the code look really nice and neat and a lot easier to maintain.\r\n\r\nUnder the \"indent\" folder there is a providex.indent.readme.  It explains in detail all the rules of the indenation.  The readme was written in Vim.\r\nIt will automatically highlight any files ending in .pvx.  You can change this behavior by changing the \"filetype.vim\" file.","4":"ProvideX is a business basic developed by Sage Software Canada. \r\n\r\nThese files allow you to do Providex Programming in Vim (obviously).  It will do all the highlighting as in the Providex Editor itself with a few enhancments and additional features as providex by Vim.\r\nAlso if you don't use line numbers you can take Full advantage of the indentation file which makes the code look really nice and neat and a lot easier to maintain.\r\n\r\nUnder the \"indent\" folder there is a providex.indent.readme.  It explains in detail all the rules of the indenation.  The readme was written in Vim.\r\nIt will automatically highlight any files ending in .pvx.  You can change this behavior by changing the \"filetype.vim\" file.","install_details":"Just place the whole folder stucture of the .zip file under your $HOME\/.vim\/ folder.  \r\nVim by default will read this folder and process the \"filetype.vim\" file.  \r\nThe ftplugin folder will also be read and will automatically tell Vim to use the providex colorscheme file included and set Vim to ignore case \"set ic\".\r\nSo the structure for you should look like $HOME\/.vim\/filetype.vim or $HOME\/.vim\/syntax\/providex.vim, etc..\r\n","5":"Just place the whole folder stucture of the .zip file under your $HOME\/.vim\/ folder.  \r\nVim by default will read this folder and process the \"filetype.vim\" file.  \r\nThe ftplugin folder will also be read and will automatically tell Vim to use the providex colorscheme file included and set Vim to ignore case \"set ic\".\r\nSo the structure for you should look like $HOME\/.vim\/filetype.vim or $HOME\/.vim\/syntax\/providex.vim, etc..\r\n","first_name":"Tyler","6":"Tyler","last_name":"Harsh","7":"Harsh","releases":[{"0":"4346","vim_version":"6.0","1":"6.0","script_version":"1","2":"1","version_comment":"Initial upload","3":"Initial upload","package":"providex.vim.zip","4":"providex.vim.zip","src_id":"19132","5":"19132","creation_date":"1354901659","6":"1354901659"}]},"4345":{"script_id":"4345","0":"4345","script_name":"templator","1":"templator","script_type":"utility","2":"utility","summary":"Multi-file project templates using skeleton\/snippets engines","3":"Multi-file project templates using skeleton\/snippets engines","description":"This plugin provides the |:Templator| command that can be used to easily \r\ncreate multi-file projects.\r\n\r\nIn many programming languges\/environments, you usually work with a set of files \r\nthat belong together. E.g. if you create a c file, you usually also want to \r\ncreate a h header file. If you create a viewer file, you usually also want to \r\ncreate corresponding model and controller files. If you want to create a \r\nlibrary file, you usually also want to create some test file etc. This is were \r\ntemplator comes in.\r\n\r\nThe templator plugin allows the creation of filesets based on multi-file \r\ntemplates. Possible use cases:\r\n\r\n    - Create multi-file projects\r\n    - Create multiple-files within a project, e.g.\r\n        - a source file and the corresponding header file\r\n        - a source file and the corresponding test file\r\n        - files for a model, a view, and a controller\r\n\r\nTemplates can be written in any code template\/skeleton\/snippets style. At the \r\ntime of writing, templates can be written in:\r\n\r\n    - template vim (see |templator-tvim|) (\"tvim\" extension)\r\n    - tskeleton (vimscript #1160) (\"tskel\" extension)\r\n\r\nIt shoudln't be too difficult to add support for additional template \r\nengines.\r\n\r\n\r\nTutorial~\r\n\r\nThe vimplugin template, which is provided with the plugin, consist of the following files: >\r\n\r\n    ~\/.vim\/templator\/vimplugin.tvim\/README_${1}.TXT\r\n    ~\/.vim\/templator\/vimplugin.tvim\/docs\/${1}.txt\r\n    ~\/.vim\/templator\/vimplugin.tvim\/plugin\/${1}.vim\r\n    ~\/.vim\/templator\/vimplugin.tvim\/autoload\/${1}.vim\r\n\r\nand an optional vim script (see |templator-scripts|) in:\r\n    \r\n    ~\/.vim\/templator\/vimplugin.vim\r\n\r\nThe command call >\r\n\r\n    :Templator ~\/src\/foo\/bar\/vimplugin myplugin\r\n\r\nwill result in the creation of the following files: >\r\n\r\n    ~\/src\/foo\/bar\/README_myplugin.TXT\r\n    ~\/src\/foo\/bar\/docs\/myplugin.txt\r\n    ~\/src\/foo\/bar\/plugin\/myplugin.vim\r\n    ~\/src\/foo\/bar\/autoload\/myplugin.vim\r\n\r\nAny placeholders within the files are expanded.\r\n","4":"This plugin provides the |:Templator| command that can be used to easily \r\ncreate multi-file projects.\r\n\r\nIn many programming languges\/environments, you usually work with a set of files \r\nthat belong together. E.g. if you create a c file, you usually also want to \r\ncreate a h header file. If you create a viewer file, you usually also want to \r\ncreate corresponding model and controller files. If you want to create a \r\nlibrary file, you usually also want to create some test file etc. This is were \r\ntemplator comes in.\r\n\r\nThe templator plugin allows the creation of filesets based on multi-file \r\ntemplates. Possible use cases:\r\n\r\n    - Create multi-file projects\r\n    - Create multiple-files within a project, e.g.\r\n        - a source file and the corresponding header file\r\n        - a source file and the corresponding test file\r\n        - files for a model, a view, and a controller\r\n\r\nTemplates can be written in any code template\/skeleton\/snippets style. At the \r\ntime of writing, templates can be written in:\r\n\r\n    - template vim (see |templator-tvim|) (\"tvim\" extension)\r\n    - tskeleton (vimscript #1160) (\"tskel\" extension)\r\n\r\nIt shoudln't be too difficult to add support for additional template \r\nengines.\r\n\r\n\r\nTutorial~\r\n\r\nThe vimplugin template, which is provided with the plugin, consist of the following files: >\r\n\r\n    ~\/.vim\/templator\/vimplugin.tvim\/README_${1}.TXT\r\n    ~\/.vim\/templator\/vimplugin.tvim\/docs\/${1}.txt\r\n    ~\/.vim\/templator\/vimplugin.tvim\/plugin\/${1}.vim\r\n    ~\/.vim\/templator\/vimplugin.tvim\/autoload\/${1}.vim\r\n\r\nand an optional vim script (see |templator-scripts|) in:\r\n    \r\n    ~\/.vim\/templator\/vimplugin.vim\r\n\r\nThe command call >\r\n\r\n    :Templator ~\/src\/foo\/bar\/vimplugin myplugin\r\n\r\nwill result in the creation of the following files: >\r\n\r\n    ~\/src\/foo\/bar\/README_myplugin.TXT\r\n    ~\/src\/foo\/bar\/docs\/myplugin.txt\r\n    ~\/src\/foo\/bar\/plugin\/myplugin.vim\r\n    ~\/src\/foo\/bar\/autoload\/myplugin.vim\r\n\r\nAny placeholders within the files are expanded.\r\n","install_details":"In order to install the vba, open the vba file in VIM and type: >\r\n\r\n    :so %\r\n\r\nSee :help vimball for details.\r\n\r\nAlso available via git: http:\/\/github.com\/tomtom\/templator_vim\/\r\n\r\n\r\nOptional enhancements:\r\n\r\nIn order to use tskeleton-style template sets, tskeleton (vimscript #1160) must \r\nbe installed: http:\/\/www.vim.org\/scripts\/script.php?script_id=1160\r\n\r\nFor projects under VCS control, if you want support for filenames relative to \r\nthe project's root, tlib (vimscript #1863) must be installed: \r\nhttp:\/\/www.vim.org\/scripts\/script.php?script_id=1863\r\n","5":"In order to install the vba, open the vba file in VIM and type: >\r\n\r\n    :so %\r\n\r\nSee :help vimball for details.\r\n\r\nAlso available via git: http:\/\/github.com\/tomtom\/templator_vim\/\r\n\r\n\r\nOptional enhancements:\r\n\r\nIn order to use tskeleton-style template sets, tskeleton (vimscript #1160) must \r\nbe installed: http:\/\/www.vim.org\/scripts\/script.php?script_id=1160\r\n\r\nFor projects under VCS control, if you want support for filenames relative to \r\nthe project's root, tlib (vimscript #1863) must be installed: \r\nhttp:\/\/www.vim.org\/scripts\/script.php?script_id=1863\r\n","first_name":"Tom","6":"Tom","last_name":"Link","7":"Link","releases":[{"0":"4345","vim_version":"7.0","1":"7.0","script_version":"0.02","2":"0.02","version_comment":"- tvim: Support end marker in strings\n- Update r.tskel example template set\n- Updated r.tskel\n- g:templator#edit_again: The command used for editing files that already existed.\n- r.tskel: tests\/test_*.R: set  test_that context()\n- Renamed g:templator#drivers to g:templator#hooks\n- Enable place holders in directory names\n- New hook: IncludeFilename: Check whether file should be created\n- CheckArgs hook\n- addon-info\n- Moved r template set to rcom_vim\n- Minor improvements\n- tvim: Enable vimeval placeholders\n- New vimplugin template set\n- New vimfiletype template set\n- vimfiletype, vimplugin: doc templates\nMD5 checksum: fdf1ba7985f38db2a1c1d42f9a1f5459","3":"- tvim: Support end marker in strings\n- Update r.tskel example template set\n- Updated r.tskel\n- g:templator#edit_again: The command used for editing files that already existed.\n- r.tskel: tests\/test_*.R: set  test_that context()\n- Renamed g:templator#drivers to g:templator#hooks\n- Enable place holders in directory names\n- New hook: IncludeFilename: Check whether file should be created\n- CheckArgs hook\n- addon-info\n- Moved r template set to rcom_vim\n- Minor improvements\n- tvim: Enable vimeval placeholders\n- New vimplugin template set\n- New vimfiletype template set\n- vimfiletype, vimplugin: doc templates\nMD5 checksum: fdf1ba7985f38db2a1c1d42f9a1f5459","package":"templator.vba","4":"templator.vba","src_id":"20190","5":"20190","creation_date":"1369125247","6":"1369125247"},{"0":"4345","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"templator.vba","4":"templator.vba","src_id":"19125","5":"19125","creation_date":"1354821107","6":"1354821107"}]},"4344":{"script_id":"4344","0":"4344","script_name":"lua.vim","1":"lua.vim","script_type":"indent","2":"indent","summary":"better Lua indent file","3":"better Lua indent file","description":"This is a hastily hacked on version of the lua.vim indent file that ships with Vim. It auto-indents much better than the default one, especially when you have function arguments that span multiple lines inside of conditionals or just a function's multi-line argument list itself.\r\n\r\nFor an example of what it can accomplish, go here:\r\nhttps:\/\/gist.github.com\/4208232\r\n\r\nGitHub:\r\nhttps:\/\/github.com\/raymond-w-ko\/vim-lua-indent","4":"This is a hastily hacked on version of the lua.vim indent file that ships with Vim. It auto-indents much better than the default one, especially when you have function arguments that span multiple lines inside of conditionals or just a function's multi-line argument list itself.\r\n\r\nFor an example of what it can accomplish, go here:\r\nhttps:\/\/gist.github.com\/4208232\r\n\r\nGitHub:\r\nhttps:\/\/github.com\/raymond-w-ko\/vim-lua-indent","install_details":"Copy the lua.vim file into the indent\/ directory of your $HOME\/.vim\/ or $HOME\/vimfiles\/\r\nIf it doesn't exist, then create an indent\/ directory. This lua.vim will override the default one installed along with Vim.\r\nAlternatively, just use something like vim-pathogen.\r\n","5":"Copy the lua.vim file into the indent\/ directory of your $HOME\/.vim\/ or $HOME\/vimfiles\/\r\nIf it doesn't exist, then create an indent\/ directory. This lua.vim will override the default one installed along with Vim.\r\nAlternatively, just use something like vim-pathogen.\r\n","first_name":"Raymond","6":"Raymond","last_name":"Ko","7":"Ko","releases":[{"0":"4344","vim_version":"7.0","1":"7.0","script_version":"0.3","2":"0.3","version_comment":"Fix many more indenting cases.","3":"Fix many more indenting cases.","package":"lua.vim","4":"lua.vim","src_id":"23514","5":"23514","creation_date":"1439600627","6":"1439600627"},{"0":"4344","vim_version":"7.0","1":"7.0","script_version":"0.2.1","2":"0.2.1","version_comment":"Fix a bug where the indent script tries to balance parentheses in comments, leading huge amounts of leading whitespace if the previous line has an open left parentheses.","3":"Fix a bug where the indent script tries to balance parentheses in comments, leading huge amounts of leading whitespace if the previous line has an open left parentheses.","package":"lua.vim","4":"lua.vim","src_id":"19804","5":"19804","creation_date":"1365689268","6":"1365689268"},{"0":"4344","vim_version":"7.0","1":"7.0","script_version":"0.2","2":"0.2","version_comment":"add \"elseif\" and \"else\" to indentkeys so that it correctly auto-indents while in insert mode.","3":"add \"elseif\" and \"else\" to indentkeys so that it correctly auto-indents while in insert mode.","package":"lua.vim","4":"lua.vim","src_id":"19123","5":"19123","creation_date":"1354809563","6":"1354809563"},{"0":"4344","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"lua.vim","4":"lua.vim","src_id":"19112","5":"19112","creation_date":"1354652383","6":"1354652383"}]},"4343":{"script_id":"4343","0":"4343","script_name":"mkfile syntax","1":"mkfile syntax","script_type":"syntax","2":"syntax","summary":"mk (OS Inferno\/Plan9 make tool) syntax highlight","3":"mk (OS Inferno\/Plan9 make tool) syntax highlight","description":"Syntax highlight for mk's mkfiles (used in OS Inferno\/Plan9).","4":"Syntax highlight for mk's mkfiles (used in OS Inferno\/Plan9).","install_details":"Copy downloaded mkfile.vim to ~\/.vim\/syntax\/\r\n\r\nTo autodetect filetype add this to ~\/.vimrc or .vim\/ftdetect\/mkfile.vim:\r\nautocmd BufNewFile,BufRead mk*          if expand(\"<afile>\") !~ '\\.' | setf mkfile | endif\r\n\r\nSince version 1.10 it depends on infsh.vim (version 1.10 or higher), so you need to install it too:\r\nhttp:\/\/www.vim.org\/scripts\/script.php?script_id=4350","5":"Copy downloaded mkfile.vim to ~\/.vim\/syntax\/\r\n\r\nTo autodetect filetype add this to ~\/.vimrc or .vim\/ftdetect\/mkfile.vim:\r\nautocmd BufNewFile,BufRead mk*          if expand(\"<afile>\") !~ '\\.' | setf mkfile | endif\r\n\r\nSince version 1.10 it depends on infsh.vim (version 1.10 or higher), so you need to install it too:\r\nhttp:\/\/www.vim.org\/scripts\/script.php?script_id=4350","first_name":"Alex","6":"Alex","last_name":"Efros","7":"Efros","releases":[{"0":"4343","vim_version":"7.0","1":"7.0","script_version":"1.10","2":"1.10","version_comment":"include host os's and inferno's sh syntaxes\r\nadd heuristic to detect which sh syntax use to highlight recipe","3":"include host os's and inferno's sh syntaxes\r\nadd heuristic to detect which sh syntax use to highlight recipe","package":"mkfile.vim","4":"mkfile.vim","src_id":"19154","5":"19154","creation_date":"1355055688","6":"1355055688"},{"0":"4343","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"mkfile.vim","4":"mkfile.vim","src_id":"19111","5":"19111","creation_date":"1354648980","6":"1354648980"}]},"4342":{"script_id":"4342","0":"4342","script_name":"Lucid","1":"Lucid","script_type":"color scheme","2":"color scheme","summary":"PHP, HTML, Javscript, CSS","3":"PHP, HTML, Javscript, CSS","description":"I could not find a color scheme that makes PHP and HTML easily distinguishable on the same page, so I made this. Works good for Javascript and CSS too.\r\n\r\nLucid: http:\/\/dev.ryan-hanson.com\/images\/lucidss.png","4":"I could not find a color scheme that makes PHP and HTML easily distinguishable on the same page, so I made this. Works good for Javascript and CSS too.\r\n\r\nLucid: http:\/\/dev.ryan-hanson.com\/images\/lucidss.png","install_details":"I use this in GVIM 7.3 so I'm not sure if it's compatible in VIM for linux or not.","5":"I use this in GVIM 7.3 so I'm not sure if it's compatible in VIM for linux or not.","first_name":"Ryan","6":"Ryan","last_name":"Hanson","7":"Hanson","releases":[{"0":"4342","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"lucid.vim","4":"lucid.vim","src_id":"19108","5":"19108","creation_date":"1354641993","6":"1354641993"}]},"4341":{"script_id":"4341","0":"4341","script_name":"VimLogViewer","1":"VimLogViewer","script_type":"utility","2":"utility","summary":"log viewer like edit++","3":"log viewer like edit++","description":"This script has useful utilities for viewing log files(ex. Android logcat)\r\n[Features]\r\n1. searching keyword\r\nyou can searching the words you want to find from logs. and this results is put in the quick fix.\r\n,f          : search the word on current cursor position from current buffers(erase old list)\r\n,F         : search the word on current cursor position from current buffers(add to list)\r\nyou'll see result at quickfix view atfer typing short key, type \": copen\"\r\n\r\n2. keyword highlight\r\nIf you want to highlight the keywords in the logs, you can do it by short cuts below.\r\nfirst, move the cursor to the keywords you want to highlight. and then type \"\\\" + number\r\nyou can highlight ten differect colors by typing \"\\1\" or \"\\2\", ..., \"\\0\"  \r\n\r\n[usefule functions]\r\nSearchPatternFromBuffer(pattern)            : search the pattern from all buffers\r\nSearchPatternFromCurrentBuffer(pattern) : search the pattern from current buffers","4":"This script has useful utilities for viewing log files(ex. Android logcat)\r\n[Features]\r\n1. searching keyword\r\nyou can searching the words you want to find from logs. and this results is put in the quick fix.\r\n,f          : search the word on current cursor position from current buffers(erase old list)\r\n,F         : search the word on current cursor position from current buffers(add to list)\r\nyou'll see result at quickfix view atfer typing short key, type \": copen\"\r\n\r\n2. keyword highlight\r\nIf you want to highlight the keywords in the logs, you can do it by short cuts below.\r\nfirst, move the cursor to the keywords you want to highlight. and then type \"\\\" + number\r\nyou can highlight ten differect colors by typing \"\\1\" or \"\\2\", ..., \"\\0\"  \r\n\r\n[usefule functions]\r\nSearchPatternFromBuffer(pattern)            : search the pattern from all buffers\r\nSearchPatternFromCurrentBuffer(pattern) : search the pattern from current buffers","install_details":"just add script file into you plugin folder","5":"just add script file into you plugin folder","first_name":"Sung Keun","6":"Sung Keun","last_name":"Kim","7":"Kim","releases":[{"0":"4341","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"VimLogViewer.vim","4":"VimLogViewer.vim","src_id":"19104","5":"19104","creation_date":"1354623537","6":"1354623537"}]},"4340":{"script_id":"4340","0":"4340","script_name":"vim-addon-commandline-completion","1":"vim-addon-commandline-completion","script_type":"utility","2":"utility","summary":"provide nice selection of all <tab> completion choices in commandline","3":"provide nice selection of all <tab> completion choices in commandline","description":"Type <c-n> and get a list to select any item provided by <c-a> <tab> or <c-d> completion in Vim's commandline","4":"Type <c-n> and get a list to select any item provided by <c-a> <tab> or <c-d> completion in Vim's commandline","install_details":"Depends on tlib therefore I recommend using vim-addon-manager.\r\n\r\nThe downloadable textfile only contains these contents, because there are still some minor things to think about - thus its unstable.\r\n\r\ngoto github.com\/MarcWeber\/vim-addon-commandline-completion on the right there\r\nis \"downloads\" where you can get any revision\r\n\r\nPlugin managers such as\r\n  vim-addon-manager (will automatically fetch tlib dependency)\r\n  pathogen\r\n  vundle\r\n  ...\r\n","5":"Depends on tlib therefore I recommend using vim-addon-manager.\r\n\r\nThe downloadable textfile only contains these contents, because there are still some minor things to think about - thus its unstable.\r\n\r\ngoto github.com\/MarcWeber\/vim-addon-commandline-completion on the right there\r\nis \"downloads\" where you can get any revision\r\n\r\nPlugin managers such as\r\n  vim-addon-manager (will automatically fetch tlib dependency)\r\n  pathogen\r\n  vundle\r\n  ...\r\n","first_name":"Marc","6":"Marc","last_name":"Weber","7":"Weber","releases":[{"0":"4340","vim_version":"7.0","1":"7.0","script_version":"0.0","2":"0.0","version_comment":"Initial upload","3":"Initial upload","package":"downloadinfo.txt","4":"downloadinfo.txt","src_id":"19102","5":"19102","creation_date":"1354618037","6":"1354618037"}]},"4339":{"script_id":"4339","0":"4339","script_name":"kolor","1":"kolor","script_type":"color scheme","2":"color scheme","summary":"Colorful and eye comfortable. With 256 color terminal support.","3":"Colorful and eye comfortable. With 256 color terminal support.","description":"Colorful Vim color scheme with 256 color terminal support. Designed for optimal visibility and comfort.\r\n\r\n\r\nScreenshot \/ GitHub: https:\/\/github.com\/zeis\/vim-kolor\r\n\r\n\r\nOPTIONS\r\n-------------\r\nOptions must be set before the line \"colorscheme kolor\" in your vimrc.\r\n\r\n\r\nlet g:kolor_italic=1  \" Enable italic. Default: 1\r\nlet g:kolor_bold=1  \" Enable bold. Default: 1\r\nlet g:kolor_underlined=0  \" Enable underline. Default: 0\r\nlet g:kolor_alternative_matchparen=0  \" Gray 'MatchParen' color. Default: 0\r\nlet g:kolor_inverted_matchparen=0  \" White foreground 'MatchParen' color that might work better with some terminals. Default: 0\r\n\r\n\r\nDONATIONS\r\n-----------------\r\nThis color scheme is dedicated to the the Ugandan children. How about donating to them?\r\n","4":"Colorful Vim color scheme with 256 color terminal support. Designed for optimal visibility and comfort.\r\n\r\n\r\nScreenshot \/ GitHub: https:\/\/github.com\/zeis\/vim-kolor\r\n\r\n\r\nOPTIONS\r\n-------------\r\nOptions must be set before the line \"colorscheme kolor\" in your vimrc.\r\n\r\n\r\nlet g:kolor_italic=1  \" Enable italic. Default: 1\r\nlet g:kolor_bold=1  \" Enable bold. Default: 1\r\nlet g:kolor_underlined=0  \" Enable underline. Default: 0\r\nlet g:kolor_alternative_matchparen=0  \" Gray 'MatchParen' color. Default: 0\r\nlet g:kolor_inverted_matchparen=0  \" White foreground 'MatchParen' color that might work better with some terminals. Default: 0\r\n\r\n\r\nDONATIONS\r\n-----------------\r\nThis color scheme is dedicated to the the Ugandan children. How about donating to them?\r\n","install_details":"Copy kolor.vim to ~\/.vim\/colors (on Win <your-vim-dir>\\vimfiles\\colors). Then add the line \"colorscheme kolor\" in your vimrc file, and restart Vim.","5":"Copy kolor.vim to ~\/.vim\/colors (on Win <your-vim-dir>\\vimfiles\\colors). Then add the line \"colorscheme kolor\" in your vimrc file, and restart Vim.","first_name":"Alessandro","6":"Alessandro","last_name":"Di Martino","7":"Di Martino","releases":[{"0":"4339","vim_version":"7.0","1":"7.0","script_version":"1.4.2","2":"1.4.2","version_comment":"Minor addition: another option for matching parentheses color.","3":"Minor addition: another option for matching parentheses color.","package":"kolor.vim","4":"kolor.vim","src_id":"25506","5":"25506","creation_date":"1502619665","6":"1502619665"},{"0":"4339","vim_version":"7.0","1":"7.0","script_version":"1.4.1","2":"1.4.1","version_comment":"Minor improvements for HTML and XML.","3":"Minor improvements for HTML and XML.","package":"kolor.vim","4":"kolor.vim","src_id":"21276","5":"21276","creation_date":"1388914549","6":"1388914549"},{"0":"4339","vim_version":"7.0","1":"7.0","script_version":"1.4.0","2":"1.4.0","version_comment":"Added configuration options and changed DiffText color.","3":"Added configuration options and changed DiffText color.","package":"kolor.vim","4":"kolor.vim","src_id":"19636","5":"19636","creation_date":"1363204651","6":"1363204651"},{"0":"4339","vim_version":"7.0","1":"7.0","script_version":"1.3.0","2":"1.3.0","version_comment":"Improved diff highlighting. Very slight and final improvements to CIELAB color lightness.","3":"Improved diff highlighting. Very slight and final improvements to CIELAB color lightness.","package":"kolor.vim","4":"kolor.vim","src_id":"19198","5":"19198","creation_date":"1355832786","6":"1355832786"},{"0":"4339","vim_version":"7.0","1":"7.0","script_version":"1.2.0","2":"1.2.0","version_comment":"Removed non-text background. Changed tabline color.","3":"Removed non-text background. Changed tabline color.","package":"kolor.vim","4":"kolor.vim","src_id":"19148","5":"19148","creation_date":"1354988703","6":"1354988703"},{"0":"4339","vim_version":"7.0","1":"7.0","script_version":"1.1.0","2":"1.1.0","version_comment":"The statusbar contrast now matches the rest of the theme, and folding is more visible (thanks to the Arch Linux community for pointing it out). And some minor changes.","3":"The statusbar contrast now matches the rest of the theme, and folding is more visible (thanks to the Arch Linux community for pointing it out). And some minor changes.","package":"kolor.vim","4":"kolor.vim","src_id":"19147","5":"19147","creation_date":"1354988675","6":"1354988675"},{"0":"4339","vim_version":"7.0","1":"7.0","script_version":"1.0.0","2":"1.0.0","version_comment":"Initial upload","3":"Initial upload","package":"kolor.vim","4":"kolor.vim","src_id":"19096","5":"19096","creation_date":"1354578696","6":"1354578696"}]},"4338":{"script_id":"4338","0":"4338","script_name":"SameSyntaxMotion","1":"SameSyntaxMotion","script_type":"utility","2":"utility","summary":"Motions to the borders of the same syntax highlighting.","3":"Motions to the borders of the same syntax highlighting.","description":"DESCRIPTION\r\nVim offers many different powerful motions to position the cursor, but none\r\nleverages the syntactic analysis of the built-in syntax highlighting.\r\n\r\nThis plugin provides mappings to jump to the borders and next [count]\r\noccurrences of text highlighted in the same way as under the cursor. So when\r\nyou're in a large block of comments, a quick [y will take you to the\r\nbeginning of the comment. The ay and iy text objects will select the\r\nsurrounding text that belongs to the same syntax group, or is highlighted the\r\nsame way.\r\n\r\nRELATED WORKS\r\n- The SyntaxMotion plugin (vimscript #2965) by Dominique Pell\u00c3\u00a9 provides very\r\n  similar motions for normal and visual mode, but no operator-pending and text\r\n  objects. It does not skip over contained sub-syntax items and uses same\r\n  color as the distinguishing property.\r\n- textobj-syntax (vimscript #2716) provides similar ay and iy text objects,\r\n  but doesn't support a [count] to select multiple.\r\n\r\nUSAGE\r\n\"Same syntax\" in the context of the mappings and text objects means:\r\n1. The same highlight group is used to highlight the text. Transparent syntax\r\n   groups are ignored, highlight links are followed. Depending on the\r\n   colorscheme, this usually means if it has the same color and attributes,\r\n   it's the same, though (especially in low-color terminals) multiple\r\n   highlight groups may have the same visual appearance, but are _not_\r\n   identical.\r\n2. The same syntax group as under the cursor. When this group contains other\r\n   syntax groups (possibly with different highlighting), these are included.\r\n   So when you have escape sequences in a string (\"foo\\<CR>bar\"), quoted words\r\n   in a comment (# a \"foo\" piece), or keywords in a docstring (@author Ernie),\r\n   the entire text is treated as one syntax area, even though there are\r\n   different-colored pieces inside.\r\n3. Unhighlighted whitespace between the same syntax items is skipped. So when\r\n   there are multiple keywords in a row (FOO BAR BAZ), they are treated as one\r\n   area, even though the whitespace between them is not covered by the syntax.\r\n\r\n]y                      Go to [count] next start of the same syntax.\r\n]Y                      Go to [count] next end of the same syntax.\r\n[y                      Go to [count] previous start of the same syntax.\r\n[Y                      Go to [count] previous end of the same syntax.\r\n                        The 'wrapscan' setting applies.\r\n\r\nay                      \"a syntax\" text object, select [count] same syntax\r\n                        areas.\r\niy                      \"inner syntax\" text object, select [count] same syntax\r\n                        areas within the same line. Whitespace around the\r\n                        syntax area is not included. Unhighlighted whitespace\r\n                        delimits same syntax items here, so this selects\r\n                        individual keywords.","4":"DESCRIPTION\r\nVim offers many different powerful motions to position the cursor, but none\r\nleverages the syntactic analysis of the built-in syntax highlighting.\r\n\r\nThis plugin provides mappings to jump to the borders and next [count]\r\noccurrences of text highlighted in the same way as under the cursor. So when\r\nyou're in a large block of comments, a quick [y will take you to the\r\nbeginning of the comment. The ay and iy text objects will select the\r\nsurrounding text that belongs to the same syntax group, or is highlighted the\r\nsame way.\r\n\r\nRELATED WORKS\r\n- The SyntaxMotion plugin (vimscript #2965) by Dominique Pell\u00c3\u00a9 provides very\r\n  similar motions for normal and visual mode, but no operator-pending and text\r\n  objects. It does not skip over contained sub-syntax items and uses same\r\n  color as the distinguishing property.\r\n- textobj-syntax (vimscript #2716) provides similar ay and iy text objects,\r\n  but doesn't support a [count] to select multiple.\r\n\r\nUSAGE\r\n\"Same syntax\" in the context of the mappings and text objects means:\r\n1. The same highlight group is used to highlight the text. Transparent syntax\r\n   groups are ignored, highlight links are followed. Depending on the\r\n   colorscheme, this usually means if it has the same color and attributes,\r\n   it's the same, though (especially in low-color terminals) multiple\r\n   highlight groups may have the same visual appearance, but are _not_\r\n   identical.\r\n2. The same syntax group as under the cursor. When this group contains other\r\n   syntax groups (possibly with different highlighting), these are included.\r\n   So when you have escape sequences in a string (\"foo\\<CR>bar\"), quoted words\r\n   in a comment (# a \"foo\" piece), or keywords in a docstring (@author Ernie),\r\n   the entire text is treated as one syntax area, even though there are\r\n   different-colored pieces inside.\r\n3. Unhighlighted whitespace between the same syntax items is skipped. So when\r\n   there are multiple keywords in a row (FOO BAR BAZ), they are treated as one\r\n   area, even though the whitespace between them is not covered by the syntax.\r\n\r\n]y                      Go to [count] next start of the same syntax.\r\n]Y                      Go to [count] next end of the same syntax.\r\n[y                      Go to [count] previous start of the same syntax.\r\n[Y                      Go to [count] previous end of the same syntax.\r\n                        The 'wrapscan' setting applies.\r\n\r\nay                      \"a syntax\" text object, select [count] same syntax\r\n                        areas.\r\niy                      \"inner syntax\" text object, select [count] same syntax\r\n                        areas within the same line. Whitespace around the\r\n                        syntax area is not included. Unhighlighted whitespace\r\n                        delimits same syntax items here, so this selects\r\n                        individual keywords.","install_details":"INSTALLATION\r\nThe code is hosted in a Git repo at\r\n    https:\/\/github.com\/inkarkat\/vim-SameSyntaxMotion\r\nYou can use your favorite plugin manager, or \"git clone\" into a directory used\r\nfor Vim packages. Releases are on the \"stable\" branch, the latest unstable\r\ndevelopment snapshot on \"master\".\r\n\r\nThis script is also packaged as a vimball. If you have the \"gunzip\"\r\ndecompressor in your PATH, simply edit the *.vmb.gz package in Vim; otherwise,\r\ndecompress the archive first, e.g. using WinZip. Inside Vim, install by\r\nsourcing the vimball or via the :UseVimball command.\r\n    vim SameSyntaxMotion*.vmb.gz\r\n    :so %\r\nTo uninstall, use the :RmVimball command.\r\n\r\nDEPENDENCIES\r\n- Requires Vim 7.0 or higher.\r\n- Requires the CountJump plugin (vimscript #3130), version 1.90 or higher.\r\n\r\nCONFIGURATION\r\nFor a permanent configuration, put the following commands into your vimrc:\r\n\r\nTo change the default motion mappings, use:\r\n    let g:SameSyntaxMotion_BeginMapping = 'y'\r\n    let g:SameSyntaxMotion_EndMapping = 'Y'\r\nTo also change the [ \/ ] prefix to something else, follow the instructions for\r\nCountJump-remap-motions.\r\n\r\nTo change the default text object mappings, use:\r\n    let g:SameSyntaxMotion_TextObjectMapping = 'y'\r\nTo also change the a prefix to something else, follow the instructions for\r\nCountJump-remap-text-objects.","5":"INSTALLATION\r\nThe code is hosted in a Git repo at\r\n    https:\/\/github.com\/inkarkat\/vim-SameSyntaxMotion\r\nYou can use your favorite plugin manager, or \"git clone\" into a directory used\r\nfor Vim packages. Releases are on the \"stable\" branch, the latest unstable\r\ndevelopment snapshot on \"master\".\r\n\r\nThis script is also packaged as a vimball. If you have the \"gunzip\"\r\ndecompressor in your PATH, simply edit the *.vmb.gz package in Vim; otherwise,\r\ndecompress the archive first, e.g. using WinZip. Inside Vim, install by\r\nsourcing the vimball or via the :UseVimball command.\r\n    vim SameSyntaxMotion*.vmb.gz\r\n    :so %\r\nTo uninstall, use the :RmVimball command.\r\n\r\nDEPENDENCIES\r\n- Requires Vim 7.0 or higher.\r\n- Requires the CountJump plugin (vimscript #3130), version 1.90 or higher.\r\n\r\nCONFIGURATION\r\nFor a permanent configuration, put the following commands into your vimrc:\r\n\r\nTo change the default motion mappings, use:\r\n    let g:SameSyntaxMotion_BeginMapping = 'y'\r\n    let g:SameSyntaxMotion_EndMapping = 'Y'\r\nTo also change the [ \/ ] prefix to something else, follow the instructions for\r\nCountJump-remap-motions.\r\n\r\nTo change the default text object mappings, use:\r\n    let g:SameSyntaxMotion_TextObjectMapping = 'y'\r\nTo also change the a prefix to something else, follow the instructions for\r\nCountJump-remap-text-objects.","first_name":"Ingo","6":"Ingo","last_name":"Karkat","7":"Karkat","releases":[{"0":"4338","vim_version":"7.0","1":"7.0","script_version":"1.01","2":"1.01","version_comment":"- CountJump 1.9 renames g:CountJump_Context to g:CountJump_TextObjectContext. *** You need to update to CountJump.vim (vimscript #3130) version 1.90! ***","3":"- CountJump 1.9 renames g:CountJump_Context to g:CountJump_TextObjectContext. *** You need to update to CountJump.vim (vimscript #3130) version 1.90! ***","package":"SameSyntaxMotion-1.01.vmb.gz","4":"SameSyntaxMotion-1.01.vmb.gz","src_id":"26258","5":"26258","creation_date":"1541361863","6":"1541361863"},{"0":"4338","vim_version":"7.0","1":"7.0","script_version":"1.00","2":"1.00","version_comment":"Initial upload","3":"Initial upload","package":"SameSyntaxMotion-1.00.vmb.gz","4":"SameSyntaxMotion-1.00.vmb.gz","src_id":"19090","5":"19090","creation_date":"1354527241","6":"1354527241"}]},"4337":{"script_id":"4337","0":"4337","script_name":"vim-autoformat","1":"vim-autoformat","script_type":"utility","2":"utility","summary":"Autoformat your code","3":"Autoformat your code","description":"Format your code with only one button press! This plugin makes use of external formatprograms to achieve the best result. Check the list of formatprograms to see which languages are supported by default. You can easily customize or add your own formatprogram.\r\n\r\nFor more info, go to the repository page https:\/\/github.com\/Chiel92\/vim-autoformat .","4":"Format your code with only one button press! This plugin makes use of external formatprograms to achieve the best result. Check the list of formatprograms to see which languages are supported by default. You can easily customize or add your own formatprogram.\r\n\r\nFor more info, go to the repository page https:\/\/github.com\/Chiel92\/vim-autoformat .","install_details":"Go to the repository page https:\/\/github.com\/Chiel92\/vim-autoformat .\r\nThat's where the code lives, and that's where you will find installing details.\r\nThat being said, I may upload a new README.md when there have been major changes, just to notify the visitors of vim.org.","5":"Go to the repository page https:\/\/github.com\/Chiel92\/vim-autoformat .\r\nThat's where the code lives, and that's where you will find installing details.\r\nThat being said, I may upload a new README.md when there have been major changes, just to notify the visitors of vim.org.","first_name":"Chiel","6":"Chiel","last_name":"92","7":"92","releases":[{"0":"4337","vim_version":"7.0","1":"7.0","script_version":"1.04","2":"1.04","version_comment":"* The default behaviour of gq is enabled again by removing the fallback on auto-indenting.\r\nInstead, the fallback is only used when running the command `:Autoformat`.\r\n\r\n* For HTML,XML and XHTML, the option `textwidth` is taken into account when formatting.\r\nThis extends the way the formatting style will match your current vim settings.\r\n","3":"* The default behaviour of gq is enabled again by removing the fallback on auto-indenting.\r\nInstead, the fallback is only used when running the command `:Autoformat`.\r\n\r\n* For HTML,XML and XHTML, the option `textwidth` is taken into account when formatting.\r\nThis extends the way the formatting style will match your current vim settings.\r\n","package":"README.md","4":"README.md","src_id":"19710","5":"19710","creation_date":"1364376024","6":"1364376024"},{"0":"4337","vim_version":"7.0","1":"7.0","script_version":"1.03","2":"1.03","version_comment":"User defined options, such as shiftwidth and expandtab are taken into account.\r\nMore specifically:\r\n-    The options expandtab, shiftwidth, tabstop and softtabstop are not overwritten anymore.\r\n-    This obsoletes g:autoformat_no_default_shiftwidth.\r\n-    g:formatprg_args_expr_<filetype> is introduced, for dynamically defining formatprg arguments.\r\n\r\n","3":"User defined options, such as shiftwidth and expandtab are taken into account.\r\nMore specifically:\r\n-    The options expandtab, shiftwidth, tabstop and softtabstop are not overwritten anymore.\r\n-    This obsoletes g:autoformat_no_default_shiftwidth.\r\n-    g:formatprg_args_expr_<filetype> is introduced, for dynamically defining formatprg arguments.\r\n\r\n","package":"README.md","4":"README.md","src_id":"19653","5":"19653","creation_date":"1363440846","6":"1363440846"},{"0":"4337","vim_version":"7.0","1":"7.0","script_version":"1.02","2":"1.02","version_comment":"*    Customization of formatprograms can be done easily now, as explained above.\r\n*    I set the default tabwidth to 4 for all formatprograms as well as for vim itself.\r\n*    The default parameters for astyle have been slightly modified: it will wrap spaces around operators.\r\n*    phpCB has been removed from the defaults, due to code-breaking behaviour.\r\n*    XHTML default definition added\r\n*    When no formatter is installed or defined, vim will now auto-indent the file instead. This uses the indentfile for that specific filetype.\r\n\r\n","3":"*    Customization of formatprograms can be done easily now, as explained above.\r\n*    I set the default tabwidth to 4 for all formatprograms as well as for vim itself.\r\n*    The default parameters for astyle have been slightly modified: it will wrap spaces around operators.\r\n*    phpCB has been removed from the defaults, due to code-breaking behaviour.\r\n*    XHTML default definition added\r\n*    When no formatter is installed or defined, vim will now auto-indent the file instead. This uses the indentfile for that specific filetype.\r\n\r\n","package":"README.markdown","4":"README.markdown","src_id":"19620","5":"19620","creation_date":"1362943794","6":"1362943794"},{"0":"4337","vim_version":"7.0","1":"7.0","script_version":"1.01","2":"1.01","version_comment":"some missing files added and php support added","3":"some missing files added and php support added","package":"README.markdown","4":"README.markdown","src_id":"19126","5":"19126","creation_date":"1354835357","6":"1354835357"},{"0":"4337","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"README.markdown","4":"README.markdown","src_id":"19089","5":"19089","creation_date":"1354526560","6":"1354526560"}]},"4336":{"script_id":"4336","0":"4336","script_name":"REPL","1":"REPL","script_type":"utility","2":"utility","summary":"Minimalistic REPL","3":"Minimalistic REPL","description":"A script to interact with interpreters that have REPL.\r\nMain features:\r\n* non-intrusive\r\n* cross-platform (you need to install AND build Vimproc from https:\/\/github.com\/Shougo\/vimproc)\r\n* syntax highlighting is supported\r\n* easy to customise and add new interpreters (see plugin\/repl.vim for details)\r\n\r\nInterpreters supported out of box:\r\nShell: bash, tcsh, cmd.exe\r\nHaskell: GHCi, Hugs\r\nScheme: Racket, Chicken\r\nGNU R\r\nOcaml\r\nOctave\r\nPython\r\nComputer algebra: REDUCE, Maxima\r\n\r\nCommands:\r\n :Open<YourInterpreter> <ExtraArguments> - start session\r\n e.g.\r\n  :OpenGHCi to start GHCi \r\n  :OpenGHCi! to forcefully start a new session in a new window\r\n\r\n :CloseRepl (local to the repl window) - disconnect REPL\r\n :CloseRepl! - disconnect and wipeout the buffer\r\n :SaveInput <filename> - save input lines, use ! to force overwrite\r\n\r\nKeybinding:\r\n global:\r\n  <Leader>e - in normal mode: send current line to the interpreter, in visual mode: send selection\r\n\r\nLocal to the REPL window (normal mode only)\r\n  <Return> - send current command to the interpreter\r\n  <C-J> - copy current command to the command prompt\r\n  <C-K> - recall previous command to the command prompt\r\n  <count>[[ - navigate to the start of the current or previous command\r\n  <count>]] - navigate to the start of the next command\r\n  <count>[] - go to the end of the previous command\r\n  <count>][ - go to the end of current or the next command\r\n\r\nThe following function can be used to define your own mappings or autocommands:\r\n  repl#SendText(bufOrType, text)\r\n    bufOrType: buffer number or its type ('' means currently active buffer)\r\n    text: a list of strings to join and send to REPL\r\n\r\nHints:\r\n You may edit and re-execute commands and the plugin should update output using its markers\r\n\r\nFeel free to send you comments. Especially I would like to hear what autocommands are worth using besides CursorHold","4":"A script to interact with interpreters that have REPL.\r\nMain features:\r\n* non-intrusive\r\n* cross-platform (you need to install AND build Vimproc from https:\/\/github.com\/Shougo\/vimproc)\r\n* syntax highlighting is supported\r\n* easy to customise and add new interpreters (see plugin\/repl.vim for details)\r\n\r\nInterpreters supported out of box:\r\nShell: bash, tcsh, cmd.exe\r\nHaskell: GHCi, Hugs\r\nScheme: Racket, Chicken\r\nGNU R\r\nOcaml\r\nOctave\r\nPython\r\nComputer algebra: REDUCE, Maxima\r\n\r\nCommands:\r\n :Open<YourInterpreter> <ExtraArguments> - start session\r\n e.g.\r\n  :OpenGHCi to start GHCi \r\n  :OpenGHCi! to forcefully start a new session in a new window\r\n\r\n :CloseRepl (local to the repl window) - disconnect REPL\r\n :CloseRepl! - disconnect and wipeout the buffer\r\n :SaveInput <filename> - save input lines, use ! to force overwrite\r\n\r\nKeybinding:\r\n global:\r\n  <Leader>e - in normal mode: send current line to the interpreter, in visual mode: send selection\r\n\r\nLocal to the REPL window (normal mode only)\r\n  <Return> - send current command to the interpreter\r\n  <C-J> - copy current command to the command prompt\r\n  <C-K> - recall previous command to the command prompt\r\n  <count>[[ - navigate to the start of the current or previous command\r\n  <count>]] - navigate to the start of the next command\r\n  <count>[] - go to the end of the previous command\r\n  <count>][ - go to the end of current or the next command\r\n\r\nThe following function can be used to define your own mappings or autocommands:\r\n  repl#SendText(bufOrType, text)\r\n    bufOrType: buffer number or its type ('' means currently active buffer)\r\n    text: a list of strings to join and send to REPL\r\n\r\nHints:\r\n You may edit and re-execute commands and the plugin should update output using its markers\r\n\r\nFeel free to send you comments. Especially I would like to hear what autocommands are worth using besides CursorHold","install_details":":so vimrepl.vmb, restart Vim\r\n\r\nAlternatively you may find it on https:\/\/bitbucket.org\/khorser\/vim-repl and https:\/\/github.com\/khorser\/vim-repl","5":":so vimrepl.vmb, restart Vim\r\n\r\nAlternatively you may find it on https:\/\/bitbucket.org\/khorser\/vim-repl and https:\/\/github.com\/khorser\/vim-repl","first_name":"Sergey","6":"Sergey","last_name":"Khorev","7":"Khorev","releases":[{"0":"4336","vim_version":"7.3","1":"7.3","script_version":"1.2","2":"1.2","version_comment":"Add condensed mode for interpreters that support multi-line input like Python.","3":"Add condensed mode for interpreters that support multi-line input like Python.","package":"vimrepl.vmb","4":"vimrepl.vmb","src_id":"19335","5":"19335","creation_date":"1357731639","6":"1357731639"},{"0":"4336","vim_version":"7.3","1":"7.3","script_version":"1.1","2":"1.1","version_comment":"Make writing to the repl buffer more robust, expose a function to send text to REPL","3":"Make writing to the repl buffer more robust, expose a function to send text to REPL","package":"vimrepl.vmb","4":"vimrepl.vmb","src_id":"19232","5":"19232","creation_date":"1356149674","6":"1356149674"},{"0":"4336","vim_version":"7.3","1":"7.3","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"vimrepl.vmb","4":"vimrepl.vmb","src_id":"19088","5":"19088","creation_date":"1354520935","6":"1354520935"}]},"4335":{"script_id":"4335","0":"4335","script_name":"star search","1":"star search","script_type":"utility","2":"utility","summary":"star search","3":"star search","description":"normal mode:\r\nChange the behavior of the super star(*) key. Vim don't jump to the next match when * is pressed.\r\n\r\nvisual mode:\r\nAdd * key support for visual mode. You can select some text (using visual mode) and then press * for searching (don't jump to the next match).\r\n\r\nThinks to: \r\nhttps:\/\/github.com\/bronson\/vim-visual-star-search (for visual mode star key support)\r\n\r\nfor chinese user:\r\n=================\r\n普通模式下，修改了系统默认的 * 按键的行为，按下 * 后，Vim 不再会自动跳转到下一个匹配处了\r\n可视模式下，增加了 * 按键功能，首先可视模式下选择一段文字，然后敲击 * 可以搜索选中文字（此功能来源于 https:\/\/github.com\/bronson\/vim-visual-star-search）\r\n","4":"normal mode:\r\nChange the behavior of the super star(*) key. Vim don't jump to the next match when * is pressed.\r\n\r\nvisual mode:\r\nAdd * key support for visual mode. You can select some text (using visual mode) and then press * for searching (don't jump to the next match).\r\n\r\nThinks to: \r\nhttps:\/\/github.com\/bronson\/vim-visual-star-search (for visual mode star key support)\r\n\r\nfor chinese user:\r\n=================\r\n普通模式下，修改了系统默认的 * 按键的行为，按下 * 后，Vim 不再会自动跳转到下一个匹配处了\r\n可视模式下，增加了 * 按键功能，首先可视模式下选择一段文字，然后敲击 * 可以搜索选中文字（此功能来源于 https:\/\/github.com\/bronson\/vim-visual-star-search）\r\n","install_details":"","5":"","first_name":"Guodong","6":"Guodong","last_name":"Liang","7":"Liang","releases":[{"0":"4335","vim_version":"7.2","1":"7.2","script_version":"0.1.1","2":"0.1.1","version_comment":"Bugfix to yank.","3":"Bugfix to yank.","package":"starsearch.vim","4":"starsearch.vim","src_id":"20602","5":"20602","creation_date":"1375682701","6":"1375682701"},{"0":"4335","vim_version":"7.2","1":"7.2","script_version":"0.1.0","2":"0.1.0","version_comment":"Initial upload","3":"Initial upload","package":"starsearch.vim","4":"starsearch.vim","src_id":"19084","5":"19084","creation_date":"1354457847","6":"1354457847"}]},"4334":{"script_id":"4334","0":"4334","script_name":"TimeKeeper","1":"TimeKeeper","script_type":"utility","2":"utility","summary":"Time Tracking Utility","3":"Time Tracking Utility","description":"This is a git plugin that will track the time you spend working on a project.\r\n\r\nThis plugin will keep track of the time spent in the editor. Will try and workout how much time is being spent on the current activity, and it will track this data by project and the specific job within that project.\r\n\r\nThe times that are collected from the editor are stored in a simple comma separated timesheet. This should make it easy to use and import into different tools. It will stored by default in the $(HOME)\/timesheet.tmk. This is obviously configurable.\r\n\r\nThis plugin will also allow for the timesheet data to be added as a git note. This will allow for the time to be read by software that can read the contents of these notes.\r\n\r\nThe git notes are only added to the current branch for the current job, hopefully this will reduce the problems that git-notes have with push\/branching and merging.\r\n\r\nThe plugin will find other instances of vim with the plugin loaded, and the first one to load will become the master server. All other instances will send there updates to the server. If the current server disappears then the first to notice will become the new server. This will reduce the chance of two instances losing time updates from other servers.\r\n\r\nMore detailed information can be found at\r\n\r\n https:\/\/github.com\/PAntoine\/TimeKeeper \r\n\r\nCan you report any errors you find there.\r\n\r\nThank you.","4":"This is a git plugin that will track the time you spend working on a project.\r\n\r\nThis plugin will keep track of the time spent in the editor. Will try and workout how much time is being spent on the current activity, and it will track this data by project and the specific job within that project.\r\n\r\nThe times that are collected from the editor are stored in a simple comma separated timesheet. This should make it easy to use and import into different tools. It will stored by default in the $(HOME)\/timesheet.tmk. This is obviously configurable.\r\n\r\nThis plugin will also allow for the timesheet data to be added as a git note. This will allow for the time to be read by software that can read the contents of these notes.\r\n\r\nThe git notes are only added to the current branch for the current job, hopefully this will reduce the problems that git-notes have with push\/branching and merging.\r\n\r\nThe plugin will find other instances of vim with the plugin loaded, and the first one to load will become the master server. All other instances will send there updates to the server. If the current server disappears then the first to notice will become the new server. This will reduce the chance of two instances losing time updates from other servers.\r\n\r\nMore detailed information can be found at\r\n\r\n https:\/\/github.com\/PAntoine\/TimeKeeper \r\n\r\nCan you report any errors you find there.\r\n\r\nThank you.","install_details":"Copy into the usual location.\r\n\r\nIf your vim has been compiled with +clientserver then you will need to call TimeKeeper_StartTracking() once, and it will ask you for the name of the timetracking file. I would leave this as default, as the new location would have to be added to the .vimrc.\r\n\r\nIf you want to time-tracking to happen by default then the following should be added to the vimrc:\r\n\r\nlet g:TimeKeeperStartOnLoad = 1\r\n\r\nThis will cause the time tracking to start on load. ","5":"Copy into the usual location.\r\n\r\nIf your vim has been compiled with +clientserver then you will need to call TimeKeeper_StartTracking() once, and it will ask you for the name of the timetracking file. I would leave this as default, as the new location would have to be added to the .vimrc.\r\n\r\nIf you want to time-tracking to happen by default then the following should be added to the vimrc:\r\n\r\nlet g:TimeKeeperStartOnLoad = 1\r\n\r\nThis will cause the time tracking to start on load. ","first_name":"Peter","6":"Peter","last_name":"Antoine","7":"Antoine","releases":[{"0":"4334","vim_version":"7.3","1":"7.3","script_version":"2.1.0","2":"2.1.0","version_comment":"commit \"closes\" issued in redmine when issue is \"completed\"\r\nNow marks the items that have notes on them.\r\nstops messing up the yank buffer when windows update.","3":"commit \"closes\" issued in redmine when issue is \"completed\"\r\nNow marks the items that have notes on them.\r\nstops messing up the yank buffer when windows update.","package":"TimeKeeper-version_2.1.0.tar.gz","4":"TimeKeeper-version_2.1.0.tar.gz","src_id":"20041","5":"20041","creation_date":"1367931673","6":"1367931673"},{"0":"4334","vim_version":"7.3","1":"7.3","script_version":"2.0.1","2":"2.0.1","version_comment":"1.4.1 - Added the tag support to the git hooks.\r\n1.4.2 - Fixed the use of annotated tags and added to the githook the filter for the tag start.\r\n2.0.0 - Added the task list window.\r\n            Depreciated local file flag, now defaults to using a localfile if it finds one. Local file name has changed so does not pollute the working directory.\r\n            Added the task notes window.\r\n            Added multi-host\/user time tracking.\r\n            Fixed a couple of script issues.\r\n2.0.1 - GitHub User: mhhf found the following two problems on the Mac:\r\n             - Guard did not work correctly.\r\n             - bash command not portable.\r\n            ","3":"1.4.1 - Added the tag support to the git hooks.\r\n1.4.2 - Fixed the use of annotated tags and added to the githook the filter for the tag start.\r\n2.0.0 - Added the task list window.\r\n            Depreciated local file flag, now defaults to using a localfile if it finds one. Local file name has changed so does not pollute the working directory.\r\n            Added the task notes window.\r\n            Added multi-host\/user time tracking.\r\n            Fixed a couple of script issues.\r\n2.0.1 - GitHub User: mhhf found the following two problems on the Mac:\r\n             - Guard did not work correctly.\r\n             - bash command not portable.\r\n            ","package":"TimeKeeper-version_2.0.1.tar.gz","4":"TimeKeeper-version_2.0.1.tar.gz","src_id":"19940","5":"19940","creation_date":"1366971953","6":"1366971953"},{"0":"4334","vim_version":"7.3","1":"7.3","script_version":"1.4.0","2":"1.4.0","version_comment":"A few fixes, server disappearing spin, problem with double ## in redmine commit names, added time function, and fixed number of hours in a day problem.","3":"A few fixes, server disappearing spin, problem with double ## in redmine commit names, added time function, and fixed number of hours in a day problem.","package":"TimeKeeper-version_1.4.0.tar.gz","4":"TimeKeeper-version_1.4.0.tar.gz","src_id":"19646","5":"19646","creation_date":"1363341881","6":"1363341881"},{"0":"4334","vim_version":"7.3","1":"7.3","script_version":"1.2.0","2":"1.2.0","version_comment":"Added new reporting functions.\r\nAlso, made the non-redmine commit message human readable. The old format is still available use set TIMEKEEPER_OUTPUT_RAW_TIMESTAMP=1 to get it. ","3":"Added new reporting functions.\r\nAlso, made the non-redmine commit message human readable. The old format is still available use set TIMEKEEPER_OUTPUT_RAW_TIMESTAMP=1 to get it. ","package":"TimeKeeper-version_1.2.0.tar.gz","4":"TimeKeeper-version_1.2.0.tar.gz","src_id":"19384","5":"19384","creation_date":"1358371894","6":"1358371894"},{"0":"4334","vim_version":"7.3","1":"7.3","script_version":"1.1.4","2":"1.1.4","version_comment":"Fixed number of hours in a day and the initial commit time was wrong.","3":"Fixed number of hours in a day and the initial commit time was wrong.","package":"TimeKeeper-version_1.1.4.tar.gz","4":"TimeKeeper-version_1.1.4.tar.gz","src_id":"19329","5":"19329","creation_date":"1357634309","6":"1357634309"},{"0":"4334","vim_version":"7.0","1":"7.0","script_version":"1.1.0","2":"1.1.0","version_comment":"Added support for amending git commits.\r\n\r\nAdded git prepare-commit-msg and a post-commit hook to handle this. If you are going to upgrade to this version from 1.0.0 you will need to add a column to the timekeeper.tmk file before you start vim, or you will lose the time tracked on OTHER projects that you have been working on. If you are only working on oe project then don't worry. Any future changes will be backwards compatible.","3":"Added support for amending git commits.\r\n\r\nAdded git prepare-commit-msg and a post-commit hook to handle this. If you are going to upgrade to this version from 1.0.0 you will need to add a column to the timekeeper.tmk file before you start vim, or you will lose the time tracked on OTHER projects that you have been working on. If you are only working on oe project then don't worry. Any future changes will be backwards compatible.","package":"TimeKeeper-version_1.1.0.tar.gz","4":"TimeKeeper-version_1.1.0.tar.gz","src_id":"19146","5":"19146","creation_date":"1354977332","6":"1354977332"},{"0":"4334","vim_version":"7.0","1":"7.0","script_version":"1.0.0","2":"1.0.0","version_comment":"Initial upload","3":"Initial upload","package":"TimeKeeper-version_1.0.0.tar.gz","4":"TimeKeeper-version_1.0.0.tar.gz","src_id":"19083","5":"19083","creation_date":"1354455956","6":"1354455956"}]},"4333":{"script_id":"4333","0":"4333","script_name":"termpot","1":"termpot","script_type":"color scheme","2":"color scheme","summary":"Balanced color scheme (xterm-256color)","3":"Balanced color scheme (xterm-256color)","description":"Dark variant originally based on \"inkpot\", but has seen considerable changes. Light variant made from scratch. Only works in a terminal with 256 colors, such as XTerm or VTE terminals.\r\n\r\nScreenshots:\r\n\r\n * Dark: https:\/\/www.uninformativ.de\/desktop\/2021-10-01--katriawm-vim-termpot-showcase-dark.png\r\n * Light: https:\/\/www.uninformativ.de\/desktop\/2021-10-01--katriawm-vim-termpot-showcase-light.png\r\n\r\nUpstream: https:\/\/www.uninformativ.de\/git\/vim-termpot\r\n","4":"Dark variant originally based on \"inkpot\", but has seen considerable changes. Light variant made from scratch. Only works in a terminal with 256 colors, such as XTerm or VTE terminals.\r\n\r\nScreenshots:\r\n\r\n * Dark: https:\/\/www.uninformativ.de\/desktop\/2021-10-01--katriawm-vim-termpot-showcase-dark.png\r\n * Light: https:\/\/www.uninformativ.de\/desktop\/2021-10-01--katriawm-vim-termpot-showcase-light.png\r\n\r\nUpstream: https:\/\/www.uninformativ.de\/git\/vim-termpot\r\n","install_details":"Place in ~\/.vim\/colors","5":"Place in ~\/.vim\/colors","first_name":"Peter","6":"Peter","last_name":"Hofmann","7":"Hofmann","releases":[{"0":"4333","vim_version":"8.2","1":"8.2","script_version":"3","2":"3","version_comment":"Changes since 2:\r\n\r\n* 4c844e6 vim\/termpot: Increase brightness of some elements\r\n* 0150a44 Vim: Merge colorschemes termpot and vain256","3":"Changes since 2:\r\n\r\n* 4c844e6 vim\/termpot: Increase brightness of some elements\r\n* 0150a44 Vim: Merge colorschemes termpot and vain256","package":"termpot.vim","4":"termpot.vim","src_id":"27760","5":"27760","creation_date":"1633143032","6":"1633143032"},{"0":"4333","vim_version":"8.0","1":"8.0","script_version":"2","2":"2","version_comment":"Changes since 1.2:\r\n\r\n* 119dbd4 termpot: Add some missing colors, change version scheme\r\n* 182c67d Vim\/termpot: Increase readability when redshift is active\r\n* b30456e termpot: Avoid using the lower 16 colors","3":"Changes since 1.2:\r\n\r\n* 119dbd4 termpot: Add some missing colors, change version scheme\r\n* 182c67d Vim\/termpot: Increase readability when redshift is active\r\n* b30456e termpot: Avoid using the lower 16 colors","package":"termpot.vim","4":"termpot.vim","src_id":"27084","5":"27084","creation_date":"1584903662","6":"1584903662"},{"0":"4333","vim_version":"7.3","1":"7.3","script_version":"1.2","2":"1.2","version_comment":"Changes since 1.0:\r\n\r\n* 0919dc3 termpot: Include settings for cursor line\r\n* d49b189 Vim: termpot: VertSplit plays well with StatusLine\r\n* 1c8e880 Vim: termpot: Black background below text\r\n* 5abdee7 Vim: termpot: \"Cursor\" stuff is not needed","3":"Changes since 1.0:\r\n\r\n* 0919dc3 termpot: Include settings for cursor line\r\n* d49b189 Vim: termpot: VertSplit plays well with StatusLine\r\n* 1c8e880 Vim: termpot: Black background below text\r\n* 5abdee7 Vim: termpot: \"Cursor\" stuff is not needed","package":"termpot.vim","4":"termpot.vim","src_id":"20517","5":"20517","creation_date":"1373817388","6":"1373817388"},{"0":"4333","vim_version":"7.3","1":"7.3","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"termpot.vim","4":"termpot.vim","src_id":"19078","5":"19078","creation_date":"1354437094","6":"1354437094"}]},"4332":{"script_id":"4332","0":"4332","script_name":"weibo-vim","1":"weibo-vim","script_type":"utility","2":"utility","summary":"a plugin for Sina weibo","3":"a plugin for Sina weibo","description":"- Updated on 2012-12-02 \r\n\r\nPlease report bugs here  https:\/\/github.com\/wusuopu\/weibo-vim-plugin\/issues","4":"- Updated on 2012-12-02 \r\n\r\nPlease report bugs here  https:\/\/github.com\/wusuopu\/weibo-vim-plugin\/issues","install_details":"","5":"","first_name":"Long","6":"Long","last_name":"Changjin","7":"Changjin","releases":[{"0":"4332","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"weibo-vim-v0.1.zip","4":"weibo-vim-v0.1.zip","src_id":"19077","5":"19077","creation_date":"1354430474","6":"1354430474"}]},"4331":{"script_id":"4331","0":"4331","script_name":"TabLineNumbers","1":"TabLineNumbers","script_type":"utility","2":"utility","summary":"Initial upload","3":"Initial upload","description":"This script adds numbers for tabs for quicker navigation.\r\nScrenshoot: http:\/\/clck.ru\/4CZOk","4":"This script adds numbers for tabs for quicker navigation.\r\nScrenshoot: http:\/\/clck.ru\/4CZOk","install_details":"","5":"","first_name":"Alexander","6":"Alexander","last_name":"Tarmolov","7":"Tarmolov","releases":[{"0":"4331","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"TabLineNumbers.zip","4":"TabLineNumbers.zip","src_id":"19073","5":"19073","creation_date":"1354386308","6":"1354386308"}]},"4330":{"script_id":"4330","0":"4330","script_name":"adt.vim","1":"adt.vim","script_type":"utility","2":"utility","summary":"android development utility in VIM","3":"android development utility in VIM","description":"This is an utility for android development, it works on the current folder, you must ensure that the initial path contains a AndroidManifest.xml file and build.xml file, so that ant build can be executed. \r\n\r\nIt can run in windows and linux.\r\n\r\nFunctions:\r\n\tAdtLogcat\tFetch logs from android device and display in copen\r\n\t\t\twindow. If there are error or warning stacks, it will\r\n\t\t\tbe recorgnized as error, so that you can switch between\r\n\t\t\terror message and codes by :cn and :cp. By default, it\r\n\t\t\tis mapped as \"Al\"\r\n\r\n\tAdtBuild\tBuild the current android application, make sure there\r\n\t\t\tare build.xml and AndroidMenifest.xml in current folder. \r\n\t\t\tThe build log will be displayed in copen window, so\r\n\t\t\tthat you can switch between error message and codes by\r\n\t\t\t:cn and :cp. By default, it is mapped as \"Ab\"\r\n\r\n\tAdtRun\t\tRun the current android application, make sure there\r\n\t\t\tare build.xml and AndroidMenifest.xml in current\r\n\t\t\tfolder. By default, it is mapped as \"Ar\"\r\n\r\n\tAdtClean\tClean the current android application build\r\n\t\t\t\tenvirovement. By default, it is mapped as \"Ac\"\r\n\r\n\tAdtHelp\t\tGet the help information of the word under cursor,\r\n\t\t\tthe cooresponding html file in android docs folder\r\n\t\t\twill be opened by xdg-open. By default, it is mapped\r\n\t\t\tas \"Ah\"\r\n\r\n\tAdtJumpResouce\tIf the word under cursor is layout resource, it will\r\n\t\t\topen the xml layout resource in a splitted window. By\r\n\t\t\tdefault, it is mapped as \"Aj\"\r\n\r\n\tAdtCreate\tCreate a new project, it is mapped as \"Ap\"\r\n\r\n\tAdtStart\tStart the default activity for current android\r\n\t\t\tapplication. By default, it is mapped as \"As\"","4":"This is an utility for android development, it works on the current folder, you must ensure that the initial path contains a AndroidManifest.xml file and build.xml file, so that ant build can be executed. \r\n\r\nIt can run in windows and linux.\r\n\r\nFunctions:\r\n\tAdtLogcat\tFetch logs from android device and display in copen\r\n\t\t\twindow. If there are error or warning stacks, it will\r\n\t\t\tbe recorgnized as error, so that you can switch between\r\n\t\t\terror message and codes by :cn and :cp. By default, it\r\n\t\t\tis mapped as \"Al\"\r\n\r\n\tAdtBuild\tBuild the current android application, make sure there\r\n\t\t\tare build.xml and AndroidMenifest.xml in current folder. \r\n\t\t\tThe build log will be displayed in copen window, so\r\n\t\t\tthat you can switch between error message and codes by\r\n\t\t\t:cn and :cp. By default, it is mapped as \"Ab\"\r\n\r\n\tAdtRun\t\tRun the current android application, make sure there\r\n\t\t\tare build.xml and AndroidMenifest.xml in current\r\n\t\t\tfolder. By default, it is mapped as \"Ar\"\r\n\r\n\tAdtClean\tClean the current android application build\r\n\t\t\t\tenvirovement. By default, it is mapped as \"Ac\"\r\n\r\n\tAdtHelp\t\tGet the help information of the word under cursor,\r\n\t\t\tthe cooresponding html file in android docs folder\r\n\t\t\twill be opened by xdg-open. By default, it is mapped\r\n\t\t\tas \"Ah\"\r\n\r\n\tAdtJumpResouce\tIf the word under cursor is layout resource, it will\r\n\t\t\topen the xml layout resource in a splitted window. By\r\n\t\t\tdefault, it is mapped as \"Aj\"\r\n\r\n\tAdtCreate\tCreate a new project, it is mapped as \"Ap\"\r\n\r\n\tAdtStart\tStart the default activity for current android\r\n\t\t\tapplication. By default, it is mapped as \"As\"","install_details":"\tCopy adt.vim to the plugin folder of your vim location. \r\n\tIn the vimrc file, set some global variables\r\n\r\n\tg:adtVimHtmlViewer\tThe Html viewer for open android help file, if\r\n\t\t\t\tnot set, the default Html viewer is used.\r\n\r\n\tg:adtVimAndroidPath\tThe locaion where android sdk is installed, if\r\n\t\t\t\tnot set, in linux which android will be called\r\n\t\t\t\tand the output is taken as default; in windows\r\n\t\t\t\tit will keep empty and you will not be able to\r\n\t\t\t\tuse AdtHelp\r\n\r\n\tg:adtVimCat\t\tIn linux set it as cat, and in windows set it\r\n\t\t\t\tas type. If not set, cat will be the default\r\n\r\n\tg:adtVimFile\t\tThe log file to used, if not set, \/tmp\/l.txt\r\n\t\t\t\tis used, so, for window it is a must to set,\r\n\t\t\t\tor else, you will not be able to locate build\r\n\t\t\t\terror automatically","5":"\tCopy adt.vim to the plugin folder of your vim location. \r\n\tIn the vimrc file, set some global variables\r\n\r\n\tg:adtVimHtmlViewer\tThe Html viewer for open android help file, if\r\n\t\t\t\tnot set, the default Html viewer is used.\r\n\r\n\tg:adtVimAndroidPath\tThe locaion where android sdk is installed, if\r\n\t\t\t\tnot set, in linux which android will be called\r\n\t\t\t\tand the output is taken as default; in windows\r\n\t\t\t\tit will keep empty and you will not be able to\r\n\t\t\t\tuse AdtHelp\r\n\r\n\tg:adtVimCat\t\tIn linux set it as cat, and in windows set it\r\n\t\t\t\tas type. If not set, cat will be the default\r\n\r\n\tg:adtVimFile\t\tThe log file to used, if not set, \/tmp\/l.txt\r\n\t\t\t\tis used, so, for window it is a must to set,\r\n\t\t\t\tor else, you will not be able to locate build\r\n\t\t\t\terror automatically","first_name":"chen","6":"chen","last_name":"chi","7":"chi","releases":[{"0":"4330","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Add support for windows","3":"Add support for windows","package":"adt.vim","4":"adt.vim","src_id":"20579","5":"20579","creation_date":"1375276717","6":"1375276717"},{"0":"4330","vim_version":"7.0","1":"7.0","script_version":"0.1.3.3","2":"0.1.3.3","version_comment":"Add command for create new project \"Ap\"","3":"Add command for create new project \"Ap\"","package":"adt.vim","4":"adt.vim","src_id":"20383","5":"20383","creation_date":"1371809856","6":"1371809856"},{"0":"4330","vim_version":"7.0","1":"7.0","script_version":"0.1.3.2","2":"0.1.3.2","version_comment":"Use a better Javac efm","3":"Use a better Javac efm","package":"adt.vim","4":"adt.vim","src_id":"19349","5":"19349","creation_date":"1357911074","6":"1357911074"},{"0":"4330","vim_version":"7.0","1":"7.0","script_version":"0.1.3.1","2":"0.1.3.1","version_comment":"improve function AdtJumpResource, support jump in xml file and java file both. Add better way to read log pid.","3":"improve function AdtJumpResource, support jump in xml file and java file both. Add better way to read log pid.","package":"adt.vim","4":"adt.vim","src_id":"19127","5":"19127","creation_date":"1354852331","6":"1354852331"},{"0":"4330","vim_version":"7.0","1":"7.0","script_version":"0.1.3","2":"0.1.3","version_comment":"Add function AdtJumpResource, which can open the layout file under current cursor","3":"Add function AdtJumpResource, which can open the layout file under current cursor","package":"adt.vim","4":"adt.vim","src_id":"19119","5":"19119","creation_date":"1354769510","6":"1354769510"},{"0":"4330","vim_version":"7.0","1":"7.0","script_version":"0.1.2.2","2":"0.1.2.2","version_comment":"Get Pid by stable way, fix tiny bugs","3":"Get Pid by stable way, fix tiny bugs","package":"adt.vim","4":"adt.vim","src_id":"19115","5":"19115","creation_date":"1354673141","6":"1354673141"},{"0":"4330","vim_version":"7.0","1":"7.0","script_version":"0.1.2.1","2":"0.1.2.1","version_comment":"Fix bug that AdtLog can not catch some errors; Add g:adtVimHtmlViewer to enable user define html viewer. default is xdg-open, and I prefer elinks","3":"Fix bug that AdtLog can not catch some errors; Add g:adtVimHtmlViewer to enable user define html viewer. default is xdg-open, and I prefer elinks","package":"adt.vim","4":"adt.vim","src_id":"19101","5":"19101","creation_date":"1354598966","6":"1354598966"},{"0":"4330","vim_version":"7.0","1":"7.0","script_version":"0.1.2","2":"0.1.2","version_comment":"Add function AdtHelp","3":"Add function AdtHelp","package":"adt.vim","4":"adt.vim","src_id":"19091","5":"19091","creation_date":"1354537981","6":"1354537981"},{"0":"4330","vim_version":"7.0","1":"7.0","script_version":"0.1.1","2":"0.1.1","version_comment":"Add function AdtClean\r\nImprove the AdtLogcat function","3":"Add function AdtClean\r\nImprove the AdtLogcat function","package":"adt.vim","4":"adt.vim","src_id":"19082","5":"19082","creation_date":"1354445462","6":"1354445462"},{"0":"4330","vim_version":"7.2","1":"7.2","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"adt.vim","4":"adt.vim","src_id":"19072","5":"19072","creation_date":"1354385367","6":"1354385367"}]},"4329":{"script_id":"4329","0":"4329","script_name":"pl1.vim","1":"pl1.vim","script_type":"syntax","2":"syntax","summary":"PL1 Syntax Highlighting (aka PL\/1 or PL\/I)","3":"PL1 Syntax Highlighting (aka PL\/1 or PL\/I)","description":"Syntax highlighting for PL\/1 code","4":"Syntax highlighting for PL\/1 code","install_details":"Create a directory structure like the following in your home directory:\r\n\r\n   ~\/.vim\/syntax\/pl1.vim\r\n   ~\/.vim\/ftdetect\/pl1.vim\r\n\r\nwhere \"~\/.vim\" represents your private VIM configuration directory in your home directory (~ on unix like systems). Copy the file pl1.vim to ~\/.vim\/syntax\/pl1.vim.  The other file (~\/.vim\/ftdetect\/pl1.vim) should consist of the following two lines:\r\n\r\nau BufRead,BufNewFile *.pl1             set filetype=pl1\r\nau BufRead,BufNewFile *.inc             set filetype=pl1\r\n\r\nThat's it!  You can now have syntax highlighting for PL\/1 code!\r\n\r\nOPTION:\r\n\r\nI have difficulty reading the default color for VIM diffs.  In order to make the diff text more readable, I change the highlight color by placing the following 1-liner in my ~\/.vimrc file:\r\n\r\n\" Fix the difficult-to-read default setting for diff text\r\n\" highlighting.  The bang (!) is required since we are overwriting the\r\n\" DiffText setting. The highlighting for \"Todo\" also looks nice (yellow)\r\n\" if you don't like the \"MatchParen\" (Aqua) diff color.\r\nhighlight! link DiffText MatchParen   \" Aqua diff coloring\r\n\"   highlight! link DiffText Todo   \" Yellow diff coloring\r\n\r\n\r\n","5":"Create a directory structure like the following in your home directory:\r\n\r\n   ~\/.vim\/syntax\/pl1.vim\r\n   ~\/.vim\/ftdetect\/pl1.vim\r\n\r\nwhere \"~\/.vim\" represents your private VIM configuration directory in your home directory (~ on unix like systems). Copy the file pl1.vim to ~\/.vim\/syntax\/pl1.vim.  The other file (~\/.vim\/ftdetect\/pl1.vim) should consist of the following two lines:\r\n\r\nau BufRead,BufNewFile *.pl1             set filetype=pl1\r\nau BufRead,BufNewFile *.inc             set filetype=pl1\r\n\r\nThat's it!  You can now have syntax highlighting for PL\/1 code!\r\n\r\nOPTION:\r\n\r\nI have difficulty reading the default color for VIM diffs.  In order to make the diff text more readable, I change the highlight color by placing the following 1-liner in my ~\/.vimrc file:\r\n\r\n\" Fix the difficult-to-read default setting for diff text\r\n\" highlighting.  The bang (!) is required since we are overwriting the\r\n\" DiffText setting. The highlighting for \"Todo\" also looks nice (yellow)\r\n\" if you don't like the \"MatchParen\" (Aqua) diff color.\r\nhighlight! link DiffText MatchParen   \" Aqua diff coloring\r\n\"   highlight! link DiffText Todo   \" Yellow diff coloring\r\n\r\n\r\n","first_name":"Alan","6":"Alan","last_name":"Thompson","7":"Thompson","releases":[{"0":"4329","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"pl1.vim","4":"pl1.vim","src_id":"19071","5":"19071","creation_date":"1354315698","6":"1354315698"}]},"4328":{"script_id":"4328","0":"4328","script_name":"easel","1":"easel","script_type":"utility","2":"utility","summary":"your one-stop-shop for making color scheme development a breeze.","3":"your one-stop-shop for making color scheme development a breeze.","description":"easel includes:\r\n\r\n* A set of source files in different languages to try out your color scheme.\r\n* Functions and associated keybindings that come in useful when working on your colorscheme\r\n* A dark canvas scheme to base your own color scheme on.\r\n\r\n***quick how-to***\r\n\r\nStart a new color scheme:\r\n\r\n* Copy the dark_canvas directory out and rename it with whatever name you want to use for your color scheme\r\n* Also rename the file that is in the colors directory and change the name in the line: let colors_name = \"dark_canvas\"\r\n\r\nWork on the your color scheme:\r\n\r\n* Open one of the files in the test_subjects directory\r\n* Open your color scheme\r\n* source easel.vim (so easel.vim) from the plugin directory.\r\n\r\n***functions and mappings***\r\n\r\nHighlight and HighlightND (use inside color scheme file)\r\n\r\nThe canvas includes two vimscript functions that allow the definition of color scheme rules with less typing. They assume that colors are defined as pairs of RGB hex colors and matching entries in the 256 terminal color scheme palette (xtem). For example:\r\n\r\nlet s:lime = ['#aeee00', 154]\r\n\r\nThe Highlight function (with defaults) can be called:\r\n\r\ns:Highlight('Exception', s:lime, '', 'bold', '')\r\n\r\nWhich is equivalent to the command:\r\n\r\nhighlight guifg=#aeee00 guibg=bg gui='bold' guisp=fg ctermfg=154 ctermbg=bg cterm='bold'\r\n\r\nThe HighlightND function can be called in the same way, but does not add any default values.\r\n\r\n***SynStack***\r\n\r\nThis function will show you the syntax groups for the word under the cursor and also copy it to the s register (clobbering whatever was there before, so beware) for easy pasting. It is a slightly modified version of a function posed to stackoverflow.com. The mapping is <leader><F3>.\r\n\r\n***hexHighlight***\r\n\r\nThis function will replace any hex color codes with the actual colors. It was written by Yuri Feldmann and you can get it directly as a plugin on vim.org or on github. The mapping to toggle it on or off is <leader><F4>.\r\n\r\nIf you want to redefine the mappings, you can do so at the top of the easel.vim file for now (might make it configurable in the future at some point).\r\n\r\n***test subjects***\r\n\r\nThe goal is to have high quality and real code that shows all the different syntax constructs.\r\n\r\njavascript: underscore.js from underscore by Jeremy Ashkenas\r\npython: auth.py from requests by Kenneth Reitz\r\nruby: base.rb from sinatra by Blake Mizerany\r\nc: cluster.c from redis by Salvatore Sanfilippo\r\n\r\nThe respective license text has been added to the top of each source file if they weren't included already.\r\n\r\n***contribute***\r\n\r\nHead over to github: https:\/\/github.com\/nielsmadan\/easel\r\n\r\nPull requests welcome. If you have some idea about what other functions\/mappings might be useful when workin on a color scheme or if you have some test subject file in other languages.","4":"easel includes:\r\n\r\n* A set of source files in different languages to try out your color scheme.\r\n* Functions and associated keybindings that come in useful when working on your colorscheme\r\n* A dark canvas scheme to base your own color scheme on.\r\n\r\n***quick how-to***\r\n\r\nStart a new color scheme:\r\n\r\n* Copy the dark_canvas directory out and rename it with whatever name you want to use for your color scheme\r\n* Also rename the file that is in the colors directory and change the name in the line: let colors_name = \"dark_canvas\"\r\n\r\nWork on the your color scheme:\r\n\r\n* Open one of the files in the test_subjects directory\r\n* Open your color scheme\r\n* source easel.vim (so easel.vim) from the plugin directory.\r\n\r\n***functions and mappings***\r\n\r\nHighlight and HighlightND (use inside color scheme file)\r\n\r\nThe canvas includes two vimscript functions that allow the definition of color scheme rules with less typing. They assume that colors are defined as pairs of RGB hex colors and matching entries in the 256 terminal color scheme palette (xtem). For example:\r\n\r\nlet s:lime = ['#aeee00', 154]\r\n\r\nThe Highlight function (with defaults) can be called:\r\n\r\ns:Highlight('Exception', s:lime, '', 'bold', '')\r\n\r\nWhich is equivalent to the command:\r\n\r\nhighlight guifg=#aeee00 guibg=bg gui='bold' guisp=fg ctermfg=154 ctermbg=bg cterm='bold'\r\n\r\nThe HighlightND function can be called in the same way, but does not add any default values.\r\n\r\n***SynStack***\r\n\r\nThis function will show you the syntax groups for the word under the cursor and also copy it to the s register (clobbering whatever was there before, so beware) for easy pasting. It is a slightly modified version of a function posed to stackoverflow.com. The mapping is <leader><F3>.\r\n\r\n***hexHighlight***\r\n\r\nThis function will replace any hex color codes with the actual colors. It was written by Yuri Feldmann and you can get it directly as a plugin on vim.org or on github. The mapping to toggle it on or off is <leader><F4>.\r\n\r\nIf you want to redefine the mappings, you can do so at the top of the easel.vim file for now (might make it configurable in the future at some point).\r\n\r\n***test subjects***\r\n\r\nThe goal is to have high quality and real code that shows all the different syntax constructs.\r\n\r\njavascript: underscore.js from underscore by Jeremy Ashkenas\r\npython: auth.py from requests by Kenneth Reitz\r\nruby: base.rb from sinatra by Blake Mizerany\r\nc: cluster.c from redis by Salvatore Sanfilippo\r\n\r\nThe respective license text has been added to the top of each source file if they weren't included already.\r\n\r\n***contribute***\r\n\r\nHead over to github: https:\/\/github.com\/nielsmadan\/easel\r\n\r\nPull requests welcome. If you have some idea about what other functions\/mappings might be useful when workin on a color scheme or if you have some test subject file in other languages.","install_details":"","5":"","first_name":"Niels","6":"Niels","last_name":"Madan","7":"Madan","releases":[{"0":"4328","vim_version":"7.0","1":"7.0","script_version":"v1.0","2":"v1.0","version_comment":"Initial upload","3":"Initial upload","package":"easel.zip","4":"easel.zip","src_id":"19049","5":"19049","creation_date":"1354027108","6":"1354027108"}]},"4327":{"script_id":"4327","0":"4327","script_name":"rst tables","1":"rst tables","script_type":"ftplugin","2":"ftplugin","summary":"rst tables makes editing reStructuredText tables easy. [CJK, Unicode]","3":"rst tables makes editing reStructuredText tables easy. [CJK, Unicode]","description":"reStructuredText tables with improvement of cjk character alignment.\r\nTables will keep same indent as the first line.\r\nIt uses current buffer encoding, and should support any encoding like utf-8 and gbk ...\r\nUsage: (normal mode)\r\n\\\\c : create table, or fit column to text.\r\n\\\\f : format table, fit text to column.\r\n\r\nThis (rst tables) plugin is based on vimscript #3450\r\nIt's edited to improve cjk character alignment, also vim_bridge is not needed any more.\r\nUnfortunately, the author abandoned that plugin, so I uploaded this.\r\nThe modification was inspired by vimscript #4272.The original script is vimscript #3041.\r\n\r\nreStructuredText 表格，支持中文字符对齐，表格按第一行统一缩进。\r\n使用当前文件编码，理论上支持gbk，utf-8等多种字符编码。\r\n用法：(普通模式)\r\n\\\\c : 创建表格，或是调整列宽适应文本。\r\n\\\\f : 重新布局，调整文本换行适应列宽。\r\n\r\n本插件基于 vimscript #3450 修改，优化中文对齐，移除vim_bridge依赖。因为原作者已经停止维护，所以在此重新上传。\r\n中文字符宽度计算和去掉vim_bridge的依赖的实现，主要参考 vimscript #4272。最原始的插件是 vimscript #3041。","4":"reStructuredText tables with improvement of cjk character alignment.\r\nTables will keep same indent as the first line.\r\nIt uses current buffer encoding, and should support any encoding like utf-8 and gbk ...\r\nUsage: (normal mode)\r\n\\\\c : create table, or fit column to text.\r\n\\\\f : format table, fit text to column.\r\n\r\nThis (rst tables) plugin is based on vimscript #3450\r\nIt's edited to improve cjk character alignment, also vim_bridge is not needed any more.\r\nUnfortunately, the author abandoned that plugin, so I uploaded this.\r\nThe modification was inspired by vimscript #4272.The original script is vimscript #3041.\r\n\r\nreStructuredText 表格，支持中文字符对齐，表格按第一行统一缩进。\r\n使用当前文件编码，理论上支持gbk，utf-8等多种字符编码。\r\n用法：(普通模式)\r\n\\\\c : 创建表格，或是调整列宽适应文本。\r\n\\\\f : 重新布局，调整文本换行适应列宽。\r\n\r\n本插件基于 vimscript #3450 修改，优化中文对齐，移除vim_bridge依赖。因为原作者已经停止维护，所以在此重新上传。\r\n中文字符宽度计算和去掉vim_bridge的依赖的实现，主要参考 vimscript #4272。最原始的插件是 vimscript #3041。","install_details":"Place plugin file in .vim\/plugin folder.\r\nYour vim must have python interpreter support.\r\n\r\n把文件放到你的 .vim\/plugin 目录。\r\nvim 需要python支持。","5":"Place plugin file in .vim\/plugin folder.\r\nYour vim must have python interpreter support.\r\n\r\n把文件放到你的 .vim\/plugin 目录。\r\nvim 需要python支持。","first_name":"Li","6":"Li","last_name":"Chao","7":"Chao","releases":[{"0":"4327","vim_version":"7.0","1":"7.0","script_version":"0.3.3","2":"0.3.3","version_comment":"fix bound error in some case;\r\nignore '\\\\f' while no table is created yet, and no error message now.\r\n修正某些情况表格边界计算错误；\r\n直接忽略没有表格时的'\\\\f'，避免显示出错信息。","3":"fix bound error in some case;\r\nignore '\\\\f' while no table is created yet, and no error message now.\r\n修正某些情况表格边界计算错误；\r\n直接忽略没有表格时的'\\\\f'，避免显示出错信息。","package":"rst_tables.vim","4":"rst_tables.vim","src_id":"19897","5":"19897","creation_date":"1366681692","6":"1366681692"},{"0":"4327","vim_version":"7.0","1":"7.0","script_version":"0.3.2","2":"0.3.2","version_comment":"support table indent, same as first line.","3":"support table indent, same as first line.","package":"rst_tables.vim","4":"rst_tables.vim","src_id":"19571","5":"19571","creation_date":"1361932698","6":"1361932698"},{"0":"4327","vim_version":"7.0","1":"7.0","script_version":"0.3.1","2":"0.3.1","version_comment":"fix \\\\f error with texts outside right edge, and create columns.","3":"fix \\\\f error with texts outside right edge, and create columns.","package":"rst_tables.vim","4":"rst_tables.vim","src_id":"19060","5":"19060","creation_date":"1354157413","6":"1354157413"},{"0":"4327","vim_version":"7.0","1":"7.0","script_version":"0.3","2":"0.3","version_comment":"use current buffer encoding instead of utf-8;\r\nrestore ReformatTable behavior, to allow manual layout text in a cell.","3":"use current buffer encoding instead of utf-8;\r\nrestore ReformatTable behavior, to allow manual layout text in a cell.","package":"rst_tables.vim","4":"rst_tables.vim","src_id":"19055","5":"19055","creation_date":"1354085944","6":"1354085944"}]},"4326":{"script_id":"4326","0":"4326","script_name":"colorpicker","1":"colorpicker","script_type":"utility","2":"utility","summary":"A vim color picker plugin using gtk color chooser. Based on VIM-Color-Picker.","3":"A vim color picker plugin using gtk color chooser. Based on VIM-Color-Picker.","description":"It is color picker (chooser) that uses the vim python interface and the gtk python libraries. It is based on  vimscript #3224 along with some bug fixes and improvements.\r\n\r\nIf you select a hex color within vim and hit the <f5> (for now it is hardcoded, configuration options coming soon), and the gtk color picker will pop-up with the current color. This is useful when you only want to see the selected color, or make slight modifications.\r\n\r\nThe rgb() and rgba() formats are not currently supported. But I am working on it :)\r\n\r\nDevelopment over at https:\/\/github.com\/abijr\/colorpicker \r\nFeel free to report bugs, feature requests, etc.\r\n","4":"It is color picker (chooser) that uses the vim python interface and the gtk python libraries. It is based on  vimscript #3224 along with some bug fixes and improvements.\r\n\r\nIf you select a hex color within vim and hit the <f5> (for now it is hardcoded, configuration options coming soon), and the gtk color picker will pop-up with the current color. This is useful when you only want to see the selected color, or make slight modifications.\r\n\r\nThe rgb() and rgba() formats are not currently supported. But I am working on it :)\r\n\r\nDevelopment over at https:\/\/github.com\/abijr\/colorpicker \r\nFeel free to report bugs, feature requests, etc.\r\n","install_details":"","5":"","first_name":"Abimael","6":"Abimael","last_name":"Martinez","7":"Martinez","releases":[{"0":"4326","vim_version":"7.0","1":"7.0","script_version":"0.2","2":"0.2","version_comment":"Initial upload","3":"Initial upload","package":"colorpicker.tar.gz","4":"colorpicker.tar.gz","src_id":"19032","5":"19032","creation_date":"1353903984","6":"1353903984"}]},"4325":{"script_id":"4325","0":"4325","script_name":"vimcat","1":"vimcat","script_type":"utility","2":"utility","summary":"print syntax highlighted file to terminal","3":"print syntax highlighted file to terminal","description":"This script will convert a file to a highlighted version using ANSI escape codes and print it to your terminal, like cat only with colors.\r\n\r\nThis script is part of the vimpager project, which itself is available on vim.org here:\r\n\r\nhttp:\/\/www.vim.org\/scripts\/script.php?script_id=1723\r\n\r\nThe project is hosted on GitHub, where you can file issues and submit pull requests:\r\n\r\nhttps:\/\/github.com\/rkitover\/vimpager\r\n\r\nACKNOWLEDGEMENTS:\r\n\r\nMost of the code in this script is not mine, I only fixed some minor OS compatibility issues.\r\n\r\nThe following people are responsible for this functionality:\r\n\r\nOriginal vim script for highlighting with ANSI codes, AnsiHighlight by:\r\n\r\nMatthew Wozniski (mjw@drexel.edu)\r\n\r\nOriginal conversion to shell script by:\r\n\r\nMagnus Woldrich: https:\/\/github.com\/trapd00r\/utils\/blob\/master\/_v\r\n\r\nFixes to the highlighting code to make the utility actually usable (and not bleed the background color etc.) by:\r\n\r\nkrijesta: Chris Chambers <krijesta@google.com>","4":"This script will convert a file to a highlighted version using ANSI escape codes and print it to your terminal, like cat only with colors.\r\n\r\nThis script is part of the vimpager project, which itself is available on vim.org here:\r\n\r\nhttp:\/\/www.vim.org\/scripts\/script.php?script_id=1723\r\n\r\nThe project is hosted on GitHub, where you can file issues and submit pull requests:\r\n\r\nhttps:\/\/github.com\/rkitover\/vimpager\r\n\r\nACKNOWLEDGEMENTS:\r\n\r\nMost of the code in this script is not mine, I only fixed some minor OS compatibility issues.\r\n\r\nThe following people are responsible for this functionality:\r\n\r\nOriginal vim script for highlighting with ANSI codes, AnsiHighlight by:\r\n\r\nMatthew Wozniski (mjw@drexel.edu)\r\n\r\nOriginal conversion to shell script by:\r\n\r\nMagnus Woldrich: https:\/\/github.com\/trapd00r\/utils\/blob\/master\/_v\r\n\r\nFixes to the highlighting code to make the utility actually usable (and not bleed the background color etc.) by:\r\n\r\nkrijesta: Chris Chambers <krijesta@google.com>","install_details":"chmod +x vimcat\r\nmkdir ~\/bin\r\nmv vimcat ~\/bin\r\n\r\nadd $HOME\/bin to your PATH in your ~\/.bashrc or other shell startup file.\r\n\r\n# COMMAND LINE OPTIONS\r\n\r\n## -c cmd\r\n\r\nRun a vim command after opening the file. Multiple -c arguments are\r\nsupported.\r\n\r\n## --cmd cmd\r\n\r\nRun a vim command when entering vim before anything else. Multiple --cmd\r\narguments are supported.\r\n\r\n## -u vimrc\r\n\r\nUse an alternate .vimrc or .vimcatrc.","5":"chmod +x vimcat\r\nmkdir ~\/bin\r\nmv vimcat ~\/bin\r\n\r\nadd $HOME\/bin to your PATH in your ~\/.bashrc or other shell startup file.\r\n\r\n# COMMAND LINE OPTIONS\r\n\r\n## -c cmd\r\n\r\nRun a vim command after opening the file. Multiple -c arguments are\r\nsupported.\r\n\r\n## --cmd cmd\r\n\r\nRun a vim command when entering vim before anything else. Multiple --cmd\r\narguments are supported.\r\n\r\n## -u vimrc\r\n\r\nUse an alternate .vimrc or .vimcatrc.","first_name":"Rafael","6":"Rafael","last_name":"Kitover","7":"Kitover","releases":[{"0":"4325","vim_version":"7.0","1":"7.0","script_version":"2.06","2":"2.06","version_comment":"* Solaris compatibility fixes\r\n* remove array syntax for compatibility with more shells #118","3":"* Solaris compatibility fixes\r\n* remove array syntax for compatibility with more shells #118","package":"vimcat","4":"vimcat","src_id":"23422","5":"23422","creation_date":"1435522738","6":"1435522738"},{"0":"4325","vim_version":"7.0","1":"7.0","script_version":"2.0","2":"2.0","version_comment":"* support multiple -c and --cmd options, as\r\n  well as the -u option\r\n* support MSYS2\r\n","3":"* support multiple -c and --cmd options, as\r\n  well as the -u option\r\n* support MSYS2\r\n","package":"vimcat","4":"vimcat","src_id":"23237","5":"23237","creation_date":"1430326622","6":"1430326622"},{"0":"4325","vim_version":"7.0","1":"7.0","script_version":"1.8.9","2":"1.8.9","version_comment":"* security enhancements (snordhausen: Stefan Nordhausen) #78\r\n* exit on empty file instead of hanging (mapeiqi88) #80","3":"* security enhancements (snordhausen: Stefan Nordhausen) #78\r\n* exit on empty file instead of hanging (mapeiqi88) #80","package":"vimcat","4":"vimcat","src_id":"21937","5":"21937","creation_date":"1401020279","6":"1401020279"},{"0":"4325","vim_version":"7.0","1":"7.0","script_version":"1.8.8","2":"1.8.8","version_comment":"* don't clobber user's PATH (mayersj1: Steve Mayer)  #77","3":"* don't clobber user's PATH (mayersj1: Steve Mayer)  #77","package":"vimcat","4":"vimcat","src_id":"21745","5":"21745","creation_date":"1396894505","6":"1396894505"},{"0":"4325","vim_version":"7.0","1":"7.0","script_version":"1.8.3","2":"1.8.3","version_comment":"* manpage for vimcat available on github (aroig: Abdo Roig-Maranges)\r\n* add -c option for extra vim command (aroig: Abdo Roig-Maranges)\r\n* pass through if not on a tty (dfechner: Dustin Fechner)","3":"* manpage for vimcat available on github (aroig: Abdo Roig-Maranges)\r\n* add -c option for extra vim command (aroig: Abdo Roig-Maranges)\r\n* pass through if not on a tty (dfechner: Dustin Fechner)","package":"vimcat","4":"vimcat","src_id":"21229","5":"21229","creation_date":"1387792683","6":"1387792683"},{"0":"4325","vim_version":"7.0","1":"7.0","script_version":"1.7.9","2":"1.7.9","version_comment":"* reset fg color if no fg color is set (GitHub #56) (krijesta)\r\n* use \u0010#!\/usr\/bin\/env bash as the shebang","3":"* reset fg color if no fg color is set (GitHub #56) (krijesta)\r\n* use \u0010#!\/usr\/bin\/env bash as the shebang","package":"vimcat","4":"vimcat","src_id":"19492","5":"19492","creation_date":"1360526266","6":"1360526266"},{"0":"4325","vim_version":"7.0","1":"7.0","script_version":"1.7.8","2":"1.7.8","version_comment":"* change shebang from \/bin\/sh to \/bin\/bash, as it's a bash script (GitHub Issue #53)\r\n* use aixterm escapes for light non-bold colors (aroig: Abd\u00c3\u00b3 Roig-Maranges)\r\n* reads ~\/.vimcatrc if it exist for config (aroig: Abd\u00c3\u00b3 Roig-Maranges)\r\n* disables writing to viminfo (aroig: Abd\u00c3\u00b3 Roig-Maranges)\r\n* allow vimcat to read from stdin (krijesta: Chris Chambers)","3":"* change shebang from \/bin\/sh to \/bin\/bash, as it's a bash script (GitHub Issue #53)\r\n* use aixterm escapes for light non-bold colors (aroig: Abd\u00c3\u00b3 Roig-Maranges)\r\n* reads ~\/.vimcatrc if it exist for config (aroig: Abd\u00c3\u00b3 Roig-Maranges)\r\n* disables writing to viminfo (aroig: Abd\u00c3\u00b3 Roig-Maranges)\r\n* allow vimcat to read from stdin (krijesta: Chris Chambers)","package":"vimcat","4":"vimcat","src_id":"19272","5":"19272","creation_date":"1356972081","6":"1356972081"},{"0":"4325","vim_version":"7.0","1":"7.0","script_version":"1.7.7","2":"1.7.7","version_comment":"Initial upload","3":"Initial upload","package":"vimcat","4":"vimcat","src_id":"19031","5":"19031","creation_date":"1353897445","6":"1353897445"}]},"4324":{"script_id":"4324","0":"4324","script_name":"Change Syntax","1":"Change Syntax","script_type":"utility","2":"utility","summary":"Simple script for changing the current buffer's syntax language","3":"Simple script for changing the current buffer's syntax language","description":"NOTICE!\r\nI no longer support this as a plugin\/script. It was a stupid idea to start with, possibly slower than doing it with Vim's default functionality.\r\n\r\nIf you know how to delete this plugin from the listing, please contact me. :)","4":"NOTICE!\r\nI no longer support this as a plugin\/script. It was a stupid idea to start with, possibly slower than doing it with Vim's default functionality.\r\n\r\nIf you know how to delete this plugin from the listing, please contact me. :)","install_details":"","5":"","first_name":"Edu\u00c3\u00a1n","6":"Edu\u00c3\u00a1n","last_name":"L\u00c3\u00a1vaque","7":"L\u00c3\u00a1vaque","releases":[{"0":"4324","vim_version":"7.3","1":"7.3","script_version":"1.0.0","2":"1.0.0","version_comment":"Initial upload","3":"Initial upload","package":"change-syntax.zip","4":"change-syntax.zip","src_id":"19029","5":"19029","creation_date":"1353882525","6":"1353882525"}]},"4323":{"script_id":"4323","0":"4323","script_name":"vim-simple-todo","1":"vim-simple-todo","script_type":"utility","2":"utility","summary":"Useful mappings for manage simple TODO lists","3":"Useful mappings for manage simple TODO lists","description":"May be this is the smallest VIM plugin in the world. It adds some useful\r\nmappings for manage simple TODO lists and nothing more.\r\n\r\n[x] Create plugin\r\n[x] Add help documentation\r\n[x] Publish to GitHub\r\n[ ] Spread the word\r\n\r\nPlugin supports GitHub-like task lists\r\n(https:\/\/github.com\/blog\/1375-task-lists-in-gfm-issues-pulls-comments) as well.\r\n\r\n- [x] Support markdown list markers\r\n- [x] So it's easy to create tasks in issues or pull requests on GitHub\r\n\r\nAll this mappings work the same on NORMAL and INSERT modes.\r\n\r\n,i      create new todo under cursor\r\n,o      create new todo below current line\r\n,O      create new todo above current line\r\n,x      mark todo under cursor as done\r\n,X      mark todo as undone\r\n","4":"May be this is the smallest VIM plugin in the world. It adds some useful\r\nmappings for manage simple TODO lists and nothing more.\r\n\r\n[x] Create plugin\r\n[x] Add help documentation\r\n[x] Publish to GitHub\r\n[ ] Spread the word\r\n\r\nPlugin supports GitHub-like task lists\r\n(https:\/\/github.com\/blog\/1375-task-lists-in-gfm-issues-pulls-comments) as well.\r\n\r\n- [x] Support markdown list markers\r\n- [x] So it's easy to create tasks in issues or pull requests on GitHub\r\n\r\nAll this mappings work the same on NORMAL and INSERT modes.\r\n\r\n,i      create new todo under cursor\r\n,o      create new todo below current line\r\n,O      create new todo above current line\r\n,x      mark todo under cursor as done\r\n,X      mark todo as undone\r\n","install_details":"Use your favorite installation method, but I recommend to use\r\npathogen (https:\/\/github.com\/tpope\/vim-pathogen) and run:\r\n\r\ncd .vim\/bundle\r\ngit clone https:\/\/github.com\/vitalk\/vim-simple-todo","5":"Use your favorite installation method, but I recommend to use\r\npathogen (https:\/\/github.com\/tpope\/vim-pathogen) and run:\r\n\r\ncd .vim\/bundle\r\ngit clone https:\/\/github.com\/vitalk\/vim-simple-todo","first_name":"Vital","6":"Vital","last_name":"Kudzelka","7":"Kudzelka","releases":[{"0":"4323","vim_version":"7.0","1":"7.0","script_version":"0.18","2":"0.18","version_comment":"Suppress the search highlighting for the last used pattern on mark item as done\/undone. \r\n\r\nAs per https:\/\/github.com\/vitalk\/vim-simple-todo\/releases\/tag\/0.18.","3":"Suppress the search highlighting for the last used pattern on mark item as done\/undone. \r\n\r\nAs per https:\/\/github.com\/vitalk\/vim-simple-todo\/releases\/tag\/0.18.","package":"vim-simple-todo-0.18.zip","4":"vim-simple-todo-0.18.zip","src_id":"24980","5":"24980","creation_date":"1487679319","6":"1487679319"},{"0":"4323","vim_version":"7.0","1":"7.0","script_version":"0.17","2":"0.17","version_comment":"- New <plug>(simple-todo-mark-switch) mapping is defined to switch status of current todo. Mapping supports repeat via . as well. \r\n- Support bulk update of selected todos, e.g. mark as done\/undone.\r\n\r\nAs per https:\/\/github.com\/vitalk\/vim-simple-todo\/releases\/tag\/0.17","3":"- New <plug>(simple-todo-mark-switch) mapping is defined to switch status of current todo. Mapping supports repeat via . as well. \r\n- Support bulk update of selected todos, e.g. mark as done\/undone.\r\n\r\nAs per https:\/\/github.com\/vitalk\/vim-simple-todo\/releases\/tag\/0.17","package":"vim-simple-todo-0.17.zip","4":"vim-simple-todo-0.17.zip","src_id":"24979","5":"24979","creation_date":"1487679273","6":"1487679273"},{"0":"4323","vim_version":"7.0","1":"7.0","script_version":"0.16","2":"0.16","version_comment":"Optional key bindings for each mode. Key bindings can be disabled for each mode (NORMAL, INSERT, VISUAL) separately via g:simple_todo_map_NAME_mode_keys options. As per https:\/\/github.com\/vitalk\/vim-simple-todo\/releases\/tag\/0.16","3":"Optional key bindings for each mode. Key bindings can be disabled for each mode (NORMAL, INSERT, VISUAL) separately via g:simple_todo_map_NAME_mode_keys options. As per https:\/\/github.com\/vitalk\/vim-simple-todo\/releases\/tag\/0.16","package":"vim-simple-todo-0.16.zip","4":"vim-simple-todo-0.16.zip","src_id":"24978","5":"24978","creation_date":"1487679220","6":"1487679220"},{"0":"4323","vim_version":"7.0","1":"7.0","script_version":"0.15","2":"0.15","version_comment":"New plug mapping to create a list item (https:\/\/github.com\/vitalk\/vim-simple-todo\/releases\/tag\/0.15).","3":"New plug mapping to create a list item (https:\/\/github.com\/vitalk\/vim-simple-todo\/releases\/tag\/0.15).","package":"vim-simple-todo-0.15.zip","4":"vim-simple-todo-0.15.zip","src_id":"24049","5":"24049","creation_date":"1456564624","6":"1456564624"},{"0":"4323","vim_version":"7.0","1":"7.0","script_version":"0.14","2":"0.14","version_comment":"Repeatable plugs (https:\/\/github.com\/vitalk\/vim-simple-todo\/releases\/tag\/0.14).","3":"Repeatable plugs (https:\/\/github.com\/vitalk\/vim-simple-todo\/releases\/tag\/0.14).","package":"vim-simple-todo-0.14.zip","4":"vim-simple-todo-0.14.zip","src_id":"23654","5":"23654","creation_date":"1444284585","6":"1444284585"},{"0":"4323","vim_version":"7.0","1":"7.0","script_version":"0.13","2":"0.13","version_comment":"Tick symbol customization (https:\/\/github.com\/vitalk\/vim-simple-todo\/releases\/tag\/0.13).","3":"Tick symbol customization (https:\/\/github.com\/vitalk\/vim-simple-todo\/releases\/tag\/0.13).","package":"vim-simple-todo-0.13.zip","4":"vim-simple-todo-0.13.zip","src_id":"23653","5":"23653","creation_date":"1444284528","6":"1444284528"},{"0":"4323","vim_version":"7.0","1":"7.0","script_version":"0.12","2":"0.12","version_comment":"Create a new todo for current line (https:\/\/github.com\/vitalk\/vim-simple-todo\/releases\/tag\/0.12).","3":"Create a new todo for current line (https:\/\/github.com\/vitalk\/vim-simple-todo\/releases\/tag\/0.12).","package":"vim-simple-todo-0.12.zip","4":"vim-simple-todo-0.12.zip","src_id":"23554","5":"23554","creation_date":"1440681458","6":"1440681458"},{"0":"4323","vim_version":"7.0","1":"7.0","script_version":"0.11","2":"0.11","version_comment":"Insert list marker before the cursor in normal mode (https:\/\/github.com\/vitalk\/vim-simple-todo\/releases\/tag\/0.11).","3":"Insert list marker before the cursor in normal mode (https:\/\/github.com\/vitalk\/vim-simple-todo\/releases\/tag\/0.11).","package":"vim-simple-todo-0.11.zip","4":"vim-simple-todo-0.11.zip","src_id":"23493","5":"23493","creation_date":"1438163825","6":"1438163825"},{"0":"4323","vim_version":"7.0","1":"7.0","script_version":"0.10","2":"0.10","version_comment":"Disable showing commands in statusbar.","3":"Disable showing commands in statusbar.","package":"vim-simple-todo-0.10.zip","4":"vim-simple-todo-0.10.zip","src_id":"23454","5":"23454","creation_date":"1436342416","6":"1436342416"},{"0":"4323","vim_version":"7.0","1":"7.0","script_version":"0.9","2":"0.9","version_comment":"Use rich markdown formatting in README (https:\/\/github.com\/vitalk\/vim-simple-todo\/releases\/tag\/0.9).","3":"Use rich markdown formatting in README (https:\/\/github.com\/vitalk\/vim-simple-todo\/releases\/tag\/0.9).","package":"vim-simple-todo-0.9.zip","4":"vim-simple-todo-0.9.zip","src_id":"23048","5":"23048","creation_date":"1426580284","6":"1426580284"},{"0":"4323","vim_version":"7.0","1":"7.0","script_version":"0.8","2":"0.8","version_comment":"Support VISUAL mode (https:\/\/github.com\/vitalk\/vim-simple-todo\/releases\/tag\/0.8)","3":"Support VISUAL mode (https:\/\/github.com\/vitalk\/vim-simple-todo\/releases\/tag\/0.8)","package":"vim-simple-todo-0.8.zip","4":"vim-simple-todo-0.8.zip","src_id":"23018","5":"23018","creation_date":"1426268046","6":"1426268046"},{"0":"4323","vim_version":"7.0","1":"7.0","script_version":"0.7","2":"0.7","version_comment":"Rewrite README.","3":"Rewrite README.","package":"vim-simple-todo-0.7.zip","4":"vim-simple-todo-0.7.zip","src_id":"21794","5":"21794","creation_date":"1397983476","6":"1397983476"},{"0":"4323","vim_version":"7.0","1":"7.0","script_version":"0.6","2":"0.6","version_comment":"Support markdown list markers.","3":"Support markdown list markers.","package":"vim-simple-todo-0.6.zip","4":"vim-simple-todo-0.6.zip","src_id":"21775","5":"21775","creation_date":"1397553408","6":"1397553408"},{"0":"4323","vim_version":"7.0","1":"7.0","script_version":"0.5","2":"0.5","version_comment":"Add help documentation.","3":"Add help documentation.","package":"vim-simple-todo-0.5.zip","4":"vim-simple-todo-0.5.zip","src_id":"21768","5":"21768","creation_date":"1397472031","6":"1397472031"},{"0":"4323","vim_version":"7.0","1":"7.0","script_version":"0.4","2":"0.4","version_comment":"Allow remap default key bindings","3":"Allow remap default key bindings","package":"vim-simple-todo-0.4.zip","4":"vim-simple-todo-0.4.zip","src_id":"21765","5":"21765","creation_date":"1397394738","6":"1397394738"},{"0":"4323","vim_version":"7.0","1":"7.0","script_version":"0.3","2":"0.3","version_comment":"Fix compatibility with Auto-Pairs plugin.","3":"Fix compatibility with Auto-Pairs plugin.","package":"vim-simple-todo-0.3.zip","4":"vim-simple-todo-0.3.zip","src_id":"21709","5":"21709","creation_date":"1396383670","6":"1396383670"},{"0":"4323","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"update build","3":"update build","package":"vim-simple-todo-0.1.zip","4":"vim-simple-todo-0.1.zip","src_id":"19028","5":"19028","creation_date":"1353860210","6":"1353860210"}]},"4322":{"script_id":"4322","0":"4322","script_name":"ChangeGloballySmartCase","1":"ChangeGloballySmartCase","script_type":"utility","2":"utility","summary":"Change {motion} text and repeat as SmartCase substitution.","3":"Change {motion} text and repeat as SmartCase substitution.","description":"DESCRIPTION\r\nAs an add-on to the ChangeGlobally.vim plugin (vimscript #4321), this plugin\r\nimplements a gC variant that uses a \"smart case\" substitution which covers\r\nvariations in upper-\/lowercase (\"maxSize\" vs. \"MaxSize\") as well as different\r\ncoding styles like CamelCase and underscore_notation (\"maxSize\", \"MAX_SIZE\").\r\n\r\nThe gC command works just like built-in c, and after leaving insert mode\r\napplies the local substitution to all other occurrences (according to the\r\nSmartCase-rules) in the current line (in case of a small character change)\r\nor, when entire line(s) where changed, to the rest of the buffer.\r\nThis is especially useful for variable renamings and all the other small\r\ntactical edits that you're doing frequently. It is much faster than doing a\r\nsingle change and repeating it, or building a :substitute command,\r\nespecially since you would have to repeat that for all text variants that\r\nSmartCase covers.\r\n\r\nUSAGE\r\n[N][\"x]gC{motion}       Like gc, but also substitute close textual variants\r\n{Visual}[N][\"x]gC       of the changed text according to the SmartCase-rules:\r\n                        - variations in upper-\/lowercase\r\n                          (\"maxSize\" vs. \"MaxSize\")\r\n                        - different coding styles like CamelCase and\r\n                          underscore_notation (\"maxSize\", \"MAX_SIZE\")\r\n\r\n[\"x]gCC                 Like gcc, but with SmartCase-rules. It's probably\r\n                        less useful than gC, but added for completeness.\r\n\r\n[N][\"x]gX{motion}       Like gx, but also substitute close textual variants\r\n{Visual}[N][\"x]gX       of the changed text according to the SmartCase-rules:\r\n[\"x]gXX                 Like gxx, but with SmartCase-rules.\r\n\r\n[N][\"x]gC*{motion}      Delete the current whole \\<word\\> [into register x]\r\n                        and start inserting. After exiting insert mode, that\r\n                        text substitution, also to close textual variants\r\n                        according to the SmartCase-rules, is applied to all\r\n                        \/ the first [N] occurrences inside {motion} text.\r\n\r\n[N][\"x]gX*{motion}      Like gx_star, but with SmartCase-rules.\r\n[N][\"x]gCg*{motion}     Like gcg_star, but with SmartCase-rules.\r\n[N][\"x]gXg*{motion}     Like gxg_star, but with SmartCase-rules.\r\n[N][\"x]gC_ALT-8{motion} Like gc_ALT-8, but with SmartCase-rules.\r\n[N][\"x]gX_ALT-8{motion} Like gx_ALT-8, but with SmartCase-rules.\r\n[N][\"x]gCg_ALT-8{motion}Like gcg_ALT-8, but with SmartCase-rules.\r\n[N][\"x]gXg_ALT-8{motion}Like gxg_ALT-8, but with SmartCase-rules.\r\n\r\n[N][\"x]<Leader>gC{source-motion}{target-motion}\r\n                        Delete {source-motion} text [into register x] and\r\n                        and start inserting. After exiting insert mode, that\r\n                        text substitution, also to close textual variants\r\n                        according to the SmartCase-rules, is applied to all\r\n                        \/ the first [N] occurrences inside {target-motion}\r\n                        text.\r\n{Visual}[N][\"x]<Leader>gC{motion}\r\n                        Like v_<Leader>gc, but with SmartCase-rules.\r\n[N][\"x]<Leader>gX{source-motion}{target-motion}\r\n                        Like <Leader>gx, but with SmartCase-rules.\r\n{Visual}[N][\"x]<Leader>gX{motion}\r\n                        Like v_<Leader>gx, but with SmartCase-rules.\r\n\r\nEXAMPLE\r\nSuppose you have a line like this, and you want to rename the type from\r\n\"NodeList\" to \"FooBarSet\", and adapt the variable name, too:\r\nfunction set nodeList(nodeList:NodeList):void; \/\/ Update node list.\r\n\r\nWith the cursor on the start of any of the \"nodeList\", type gCe, enter the\r\ntext \"fooBarSet\", then press <Esc>. The line will turn into\r\nfunction set fooBarSet(fooBarSet:FooBarSet):void; \/\/ Update foo bar set.\r\nYou can now re-apply this substitution to other lines or a visual selection\r\nvia .","4":"DESCRIPTION\r\nAs an add-on to the ChangeGlobally.vim plugin (vimscript #4321), this plugin\r\nimplements a gC variant that uses a \"smart case\" substitution which covers\r\nvariations in upper-\/lowercase (\"maxSize\" vs. \"MaxSize\") as well as different\r\ncoding styles like CamelCase and underscore_notation (\"maxSize\", \"MAX_SIZE\").\r\n\r\nThe gC command works just like built-in c, and after leaving insert mode\r\napplies the local substitution to all other occurrences (according to the\r\nSmartCase-rules) in the current line (in case of a small character change)\r\nor, when entire line(s) where changed, to the rest of the buffer.\r\nThis is especially useful for variable renamings and all the other small\r\ntactical edits that you're doing frequently. It is much faster than doing a\r\nsingle change and repeating it, or building a :substitute command,\r\nespecially since you would have to repeat that for all text variants that\r\nSmartCase covers.\r\n\r\nUSAGE\r\n[N][\"x]gC{motion}       Like gc, but also substitute close textual variants\r\n{Visual}[N][\"x]gC       of the changed text according to the SmartCase-rules:\r\n                        - variations in upper-\/lowercase\r\n                          (\"maxSize\" vs. \"MaxSize\")\r\n                        - different coding styles like CamelCase and\r\n                          underscore_notation (\"maxSize\", \"MAX_SIZE\")\r\n\r\n[\"x]gCC                 Like gcc, but with SmartCase-rules. It's probably\r\n                        less useful than gC, but added for completeness.\r\n\r\n[N][\"x]gX{motion}       Like gx, but also substitute close textual variants\r\n{Visual}[N][\"x]gX       of the changed text according to the SmartCase-rules:\r\n[\"x]gXX                 Like gxx, but with SmartCase-rules.\r\n\r\n[N][\"x]gC*{motion}      Delete the current whole \\<word\\> [into register x]\r\n                        and start inserting. After exiting insert mode, that\r\n                        text substitution, also to close textual variants\r\n                        according to the SmartCase-rules, is applied to all\r\n                        \/ the first [N] occurrences inside {motion} text.\r\n\r\n[N][\"x]gX*{motion}      Like gx_star, but with SmartCase-rules.\r\n[N][\"x]gCg*{motion}     Like gcg_star, but with SmartCase-rules.\r\n[N][\"x]gXg*{motion}     Like gxg_star, but with SmartCase-rules.\r\n[N][\"x]gC_ALT-8{motion} Like gc_ALT-8, but with SmartCase-rules.\r\n[N][\"x]gX_ALT-8{motion} Like gx_ALT-8, but with SmartCase-rules.\r\n[N][\"x]gCg_ALT-8{motion}Like gcg_ALT-8, but with SmartCase-rules.\r\n[N][\"x]gXg_ALT-8{motion}Like gxg_ALT-8, but with SmartCase-rules.\r\n\r\n[N][\"x]<Leader>gC{source-motion}{target-motion}\r\n                        Delete {source-motion} text [into register x] and\r\n                        and start inserting. After exiting insert mode, that\r\n                        text substitution, also to close textual variants\r\n                        according to the SmartCase-rules, is applied to all\r\n                        \/ the first [N] occurrences inside {target-motion}\r\n                        text.\r\n{Visual}[N][\"x]<Leader>gC{motion}\r\n                        Like v_<Leader>gc, but with SmartCase-rules.\r\n[N][\"x]<Leader>gX{source-motion}{target-motion}\r\n                        Like <Leader>gx, but with SmartCase-rules.\r\n{Visual}[N][\"x]<Leader>gX{motion}\r\n                        Like v_<Leader>gx, but with SmartCase-rules.\r\n\r\nEXAMPLE\r\nSuppose you have a line like this, and you want to rename the type from\r\n\"NodeList\" to \"FooBarSet\", and adapt the variable name, too:\r\nfunction set nodeList(nodeList:NodeList):void; \/\/ Update node list.\r\n\r\nWith the cursor on the start of any of the \"nodeList\", type gCe, enter the\r\ntext \"fooBarSet\", then press <Esc>. The line will turn into\r\nfunction set fooBarSet(fooBarSet:FooBarSet):void; \/\/ Update foo bar set.\r\nYou can now re-apply this substitution to other lines or a visual selection\r\nvia .","install_details":"INSTALLATION\r\nThe code is hosted in a Git repo at\r\n    https:\/\/github.com\/inkarkat\/vim-ChangeGloballySmartCase\r\nYou can use your favorite plugin manager, or \"git clone\" into a directory used\r\nfor Vim packages. Releases are on the \"stable\" branch, the latest unstable\r\ndevelopment snapshot on \"master\".\r\n\r\nThis script is also packaged as a vimball. If you have the \"gunzip\"\r\ndecompressor in your PATH, simply edit the *.vmb.gz package in Vim; otherwise,\r\ndecompress the archive first, e.g. using WinZip. Inside Vim, install by\r\nsourcing the vimball or via the :UseVimball command.\r\n    vim ChangeGloballySmartCase*.vmb.gz\r\n    :so %\r\nTo uninstall, use the :RmVimball command.\r\n\r\nDEPENDENCIES\r\n- Requires Vim 7.0 or higher.\r\n- Requires the ingo-library.vim plugin (vimscript #4433), version 1.040 or\r\n  higher.\r\n- ChangeGlobally.vim (vimscript #4321) plugin (version 2.00 or higher)\r\n- SmartCase.vim (vimscript #1359)\r\n- repeat.vim (vimscript #2136) plugin (optional)\r\n- visualrepeat.vim (vimscript #3848) plugin (version 2.00 or higher; optional)\r\n\r\nCONFIGURATION\r\nFor a permanent configuration, put the following commands into your vimrc:\r\n\r\nIf you want no or only a few of the available mappings, you can completely\r\nturn off the creation of the default mappings by defining:\r\n    :let g:ChangeGloballySmartCase_no_mappings = 1\r\nThis saves you from mapping dummy keys to all unwanted mapping targets.\r\n\r\nIf you want to use different mappings, map your keys to the\r\n<Plug>(Change...SmartCase...) and <Plug>(Delete...SmartCase...) mapping\r\ntargets _before_ sourcing the script (e.g. in your vimrc):\r\n    nmap <Leader>C <Plug>(ChangeGloballySmartCaseOperator)\r\n    nmap <Leader>CC <Plug>(ChangeGloballySmartCaseLine)\r\n    xmap <Leader>C <Plug>(ChangeGloballySmartCaseVisual)\r\n    nmap <Leader>X <Plug>(DeleteGloballySmartCaseOperator)\r\n    nmap <Leader>XX <Plug>(DeleteGloballySmartCaseLine)\r\n    xmap <Leader>X <Plug>(DeleteGloballySmartCaseVisual)\r\n\r\n    nmap gC* <Plug>(ChangeWholeWordSmartCaseOperator)\r\n    nmap gX* <Plug>(DeleteWholeWordSmartCaseOperator)\r\n    nmap gCg* <Plug>(ChangeWordSmartCaseOperator)\r\n    nmap gXg* <Plug>(DeleteWordSmartCaseOperator)\r\n    nmap gC<A-8> <Plug>(ChangeWholeWORDSmartCaseOperator)\r\n    nmap gX<A-8> <Plug>(DeleteWholeWORDSmartCaseOperator)\r\n    nmap gCg<A-8> <Plug>(ChangeWORDSmartCaseOperator)\r\n    nmap gXg<A-8> <Plug>(DeleteWORDSmartCaseOperator)\r\n    nmap <Leader>gC <Plug>(ChangeOperatorSmartCaseOperator)\r\n    nmap <Leader>gX <Plug>(DeleteOperatorSmartCaseOperator)\r\n    xmap <Leader>gC <Plug>(ChangeSelectionSmartCaseOperator)\r\n    xmap <Leader>gX <Plug>(DeleteSelectionSmartCaseOperator)","5":"INSTALLATION\r\nThe code is hosted in a Git repo at\r\n    https:\/\/github.com\/inkarkat\/vim-ChangeGloballySmartCase\r\nYou can use your favorite plugin manager, or \"git clone\" into a directory used\r\nfor Vim packages. Releases are on the \"stable\" branch, the latest unstable\r\ndevelopment snapshot on \"master\".\r\n\r\nThis script is also packaged as a vimball. If you have the \"gunzip\"\r\ndecompressor in your PATH, simply edit the *.vmb.gz package in Vim; otherwise,\r\ndecompress the archive first, e.g. using WinZip. Inside Vim, install by\r\nsourcing the vimball or via the :UseVimball command.\r\n    vim ChangeGloballySmartCase*.vmb.gz\r\n    :so %\r\nTo uninstall, use the :RmVimball command.\r\n\r\nDEPENDENCIES\r\n- Requires Vim 7.0 or higher.\r\n- Requires the ingo-library.vim plugin (vimscript #4433), version 1.040 or\r\n  higher.\r\n- ChangeGlobally.vim (vimscript #4321) plugin (version 2.00 or higher)\r\n- SmartCase.vim (vimscript #1359)\r\n- repeat.vim (vimscript #2136) plugin (optional)\r\n- visualrepeat.vim (vimscript #3848) plugin (version 2.00 or higher; optional)\r\n\r\nCONFIGURATION\r\nFor a permanent configuration, put the following commands into your vimrc:\r\n\r\nIf you want no or only a few of the available mappings, you can completely\r\nturn off the creation of the default mappings by defining:\r\n    :let g:ChangeGloballySmartCase_no_mappings = 1\r\nThis saves you from mapping dummy keys to all unwanted mapping targets.\r\n\r\nIf you want to use different mappings, map your keys to the\r\n<Plug>(Change...SmartCase...) and <Plug>(Delete...SmartCase...) mapping\r\ntargets _before_ sourcing the script (e.g. in your vimrc):\r\n    nmap <Leader>C <Plug>(ChangeGloballySmartCaseOperator)\r\n    nmap <Leader>CC <Plug>(ChangeGloballySmartCaseLine)\r\n    xmap <Leader>C <Plug>(ChangeGloballySmartCaseVisual)\r\n    nmap <Leader>X <Plug>(DeleteGloballySmartCaseOperator)\r\n    nmap <Leader>XX <Plug>(DeleteGloballySmartCaseLine)\r\n    xmap <Leader>X <Plug>(DeleteGloballySmartCaseVisual)\r\n\r\n    nmap gC* <Plug>(ChangeWholeWordSmartCaseOperator)\r\n    nmap gX* <Plug>(DeleteWholeWordSmartCaseOperator)\r\n    nmap gCg* <Plug>(ChangeWordSmartCaseOperator)\r\n    nmap gXg* <Plug>(DeleteWordSmartCaseOperator)\r\n    nmap gC<A-8> <Plug>(ChangeWholeWORDSmartCaseOperator)\r\n    nmap gX<A-8> <Plug>(DeleteWholeWORDSmartCaseOperator)\r\n    nmap gCg<A-8> <Plug>(ChangeWORDSmartCaseOperator)\r\n    nmap gXg<A-8> <Plug>(DeleteWORDSmartCaseOperator)\r\n    nmap <Leader>gC <Plug>(ChangeOperatorSmartCaseOperator)\r\n    nmap <Leader>gX <Plug>(DeleteOperatorSmartCaseOperator)\r\n    xmap <Leader>gC <Plug>(ChangeSelectionSmartCaseOperator)\r\n    xmap <Leader>gX <Plug>(DeleteSelectionSmartCaseOperator)","first_name":"Ingo","6":"Ingo","last_name":"Karkat","7":"Karkat","releases":[{"0":"4322","vim_version":"7.0","1":"7.0","script_version":"2.00","2":"2.00","version_comment":"- Adapt to interface changes of ChangeGlobally.vim version 2.00\r\n- ENH: Allow to disable all default mappings via a single g:ChangeGloballySmartCase_no_mappings configuration flag. *** You need to update to ingo-library (vimscript #4433) version 1.040 and to ChangeGlobally.vim (vimscript #4321) version 2.00! ***","3":"- Adapt to interface changes of ChangeGlobally.vim version 2.00\r\n- ENH: Allow to disable all default mappings via a single g:ChangeGloballySmartCase_no_mappings configuration flag. *** You need to update to ingo-library (vimscript #4433) version 1.040 and to ChangeGlobally.vim (vimscript #4321) version 2.00! ***","package":"ChangeGloballySmartCase-2.00.vmb.gz","4":"ChangeGloballySmartCase-2.00.vmb.gz","src_id":"26970","5":"26970","creation_date":"1581309298","6":"1581309298"},{"0":"4322","vim_version":"7.0","1":"7.0","script_version":"1.30","2":"1.30","version_comment":"- Adapt to interface changes of ChangeGlobally.vim version 1.30\r\n- ENH: Implement global delete (gX{motion}, gXX) as a specialization of an empty change. *** You need to update to ingo-library (vimscript #4433) version 1.021 and to ChangeGlobally.vim (vimscript #4321) version 1.30! ***","3":"- Adapt to interface changes of ChangeGlobally.vim version 1.30\r\n- ENH: Implement global delete (gX{motion}, gXX) as a specialization of an empty change. *** You need to update to ingo-library (vimscript #4433) version 1.021 and to ChangeGlobally.vim (vimscript #4321) version 1.30! ***","package":"ChangeGloballySmartCase-1.30.vmb.gz","4":"ChangeGloballySmartCase-1.30.vmb.gz","src_id":"22693","5":"22693","creation_date":"1418415823","6":"1418415823"},{"0":"4322","vim_version":"7.0","1":"7.0","script_version":"1.20","2":"1.20","version_comment":"- Adapt to interface changes of ChangeGlobally.vim version 1.20\r\n- Use optional visualrepeat#reapply#VisualMode() for normal mode repeat of a visual mapping. When supplying a [count] on such repeat of a previous linewise selection, now [count] number of lines instead of [count] times the original selection is used.","3":"- Adapt to interface changes of ChangeGlobally.vim version 1.20\r\n- Use optional visualrepeat#reapply#VisualMode() for normal mode repeat of a visual mapping. When supplying a [count] on such repeat of a previous linewise selection, now [count] number of lines instead of [count] times the original selection is used.","package":"ChangeGloballySmartCase-1.20.vmb.gz","4":"ChangeGloballySmartCase-1.20.vmb.gz","src_id":"21060","5":"21060","creation_date":"1384855815","6":"1384855815"},{"0":"4322","vim_version":"7.0","1":"7.0","script_version":"1.00","2":"1.00","version_comment":"Initial upload","3":"Initial upload","package":"ChangeGloballySmartCase-1.00.vmb.gz","4":"ChangeGloballySmartCase-1.00.vmb.gz","src_id":"19022","5":"19022","creation_date":"1353669164","6":"1353669164"}]},"4321":{"script_id":"4321","0":"4321","script_name":"ChangeGlobally","1":"ChangeGlobally","script_type":"utility","2":"utility","summary":"Change {motion} text and repeat the substitution.","3":"Change {motion} text and repeat the substitution.","description":"DESCRIPTION\r\nChanging existing text is one of the main editing tasks. In Vim, there are two\r\napproaches: Either use the c and s commands, then quit insert mode; maybe\r\nrepeat this via . at another location. Or build a :substitute command for\r\ncontrolled replacement in the line, range, or buffer.\r\nThis plugin implements a hybrid of these two contrasting approaches: It offers\r\na gc command that works just like built-in c, and after leaving insert\r\nmode applies the local substitution to all other occurrences in the current\r\nline (in case of a small character change) or, when entire line(s) were\r\nchanged, to the rest of the buffer.\r\n\r\nHOW IT WORKS\r\nThe gc command hooks itself into the InsertLeave event, then applies\r\nsomething like :s\/\\=@\"\/\\=@.\/g to the line or buffer.\r\n\r\nSEE ALSO\r\n- ReplaceWithRegister (vimscript #2703) simplifies another frequent editing\r\n  task: Replace the selection with the contents of register.\r\n- ChangeGloballySmartCase (vimscript #4322) is an add-on to this plugin that\r\n  implements a gC variant that uses a \"smart case\" substitution which covers\r\n  variations in upper-\/lowercase (\"maxSize\" vs. \"MaxSize\") as well as\r\n  different coding styles like CamelCase and underscore_notation (\"maxSize\",\r\n  \"MAX_SIZE\").\r\n\r\nRELATED WORKS\r\n- Without the plugin, you can use the star or \/ commands to search for the\r\n  existing text, then use cgn to change the next occurrence, then repeat\r\n  this with . as often as needed.\r\n- multichange.vim (vimscript #4309) uses a command :[range]MultiChange to\r\n  modify the default c command to do an entire-word global substitution in the\r\n  entire range.\r\n- vim-subversive (https:\/\/github.com\/svermeulen\/vim-subversive) implements a\r\n  \"substitute over range motion\" that works like gc* and <Leader>gc, but\r\n  queries for the replacement text instead of letting you edit it in the\r\n  buffer.\r\n- vim-mode-plus for the Atom editor has an occurrence modifier for\r\n  operator-pending mode\r\n  (https:\/\/github.com\/t9md\/atom-vim-mode-plus\/wiki\/OccurrenceModifier) that\r\n  applies the current word to the {motion} text, working like gc* \/ gx* (but\r\n  not limited to change and delete, so other commands like gU also work).\r\n\r\nUSAGE\r\n[N][\"x]gc{motion}       Delete {motion} text [into register x] and start\r\n                        inserting.\r\n{Visual}[N][\"x]gc       Delete the highlighted text [into register x] and\r\n                        start inserting.\r\n                        After exiting insert mode, the substitution is\r\n                        applied:\r\n                        - For characterwise motions \/ selections: Globally to\r\n                          the changed line if possible, or globally in the\r\n                          entire buffer when no additional substitution can be\r\n                          made in the changed line or a very large [N] is\r\n                          given g:ChangeGlobally_GlobalCountThreshold.\r\n                        - For linewise motions \/ selections: Globally (for\r\n                          identical complete lines) in the entire buffer.\r\n                        - [N] times (including the just completed change, so\r\n                          only N > 1 really makes sense), starting from the\r\n                          position of the changed text, also moving into\r\n                          following lines if not all [N] substitutions can be\r\n                          made in the current line. To avoid this spill-over,\r\n                          and just apply all possible substitutions from the\r\n                          current position to the end of the line, you can\r\n                          specify g:ChangeGlobally_LimitToCurrentLineCount.\r\n                          Note: A possible [count] inside {motion} is\r\n                          different from [N]; e.g., 2gc3w changes 3 words, and\r\n                          then applies this change 1 more time.\r\n\r\n                        The substitution is always done case-sensitive,\r\n                        regardless of the 'ignorecase' setting.\r\n                        When the changed text is surrounded by keyword\r\n                        boundaries (\/\\<text\\>\/), only keyword matches are\r\n                        replaced so spurious matches inside keywords (e.g.\r\n                        \"IN\" inside \"rINg\") are ignored. This does not apply\r\n                        to visual selections.\r\n\r\n[\"x]gcc                 Delete [count] lines [into register x] and start\r\n                        insert linewise. If 'autoindent' is on, preserve the\r\n                        indent of the first line. After exiting insert mode,\r\n                        the substitution is applied globally.\r\n\r\n                        When a command is repeated via ., the previous\r\n                        substitution (without entering a new insert mode) is\r\n                        re-applied to the visual selection, [count] next\r\n                        lines, or the range of the previous substitution.\r\n                        For a command that used a limit [N], the number of\r\n                        substitutions and the start column from where they\r\n                        were applied are kept.\r\n\r\n                        With the visualrepeat.vim plugin, commands can be\r\n                        repeated on a blockwise-visual selection. In that\r\n                        case:\r\n                        - A repeat of gcc matches not only complete lines\r\n                          (they probably aren't fully selected), just the text\r\n                          itself.\r\n                        - Start column and [N] limit restrictions are dropped;\r\n                          the change is applied anywhere inside the selected\r\n                          block.\r\n                        All these modifications are kept for subsequent\r\n                        repeats of the repeat, so the blockwise repeat can be\r\n                        cleverly employed to remove certain change\r\n                        restrictions for following repeats of different kinds.\r\n\r\n[N][\"x]gx{motion}       Delete {motion} text [into register x] and apply the\r\n                        deletion.\r\n{Visual}[N][\"x]gx       Delete the highlighted text [into register x] and\r\n                        apply the deletion, like with gc.\r\n[\"x]gxx                 Delete [count] lines [into register x] and apply the\r\n                        deletion globally.\r\n\r\n[N][\"x]gc*{motion}      Delete the current whole \\<word\\> [into register x]\r\n                        and start inserting. After exiting insert mode, that\r\n                        text substitution is applied to all \/ the first [N]\r\n                        occurrences inside {motion} text.\r\n\r\n[N][\"x]gx*{motion}      Delete the current whole \\<word\\> [into register x]\r\n                        and apply the deletion to all \/ the first [N]\r\n                        occurrences inside {motion} text.\r\n\r\n[N][\"x]gcg*{motion}     Delete the current word [into register x] and\r\n                        start inserting. After exiting insert mode, that text\r\n                        substitution is applied to all \/ the first [N]\r\n                        occurrences inside {motion} text.\r\n\r\n[N][\"x]gxg*{motion}     Delete the current word [into register x] and\r\n                        apply the deletion to all \/ the first [N] occurrences\r\n                        inside {motion} text.\r\n\r\n[N][\"x]gc_ALT-8{motion} Delete the current whole \\_sWORD\\_s [into register x]\r\n                        and ALT-8t inserting. After exiting insert mode, that\r\n                        text substitution is applied to all \/ the first [N]\r\n                        occurrences inside {motion} text.\r\n\r\n[N][\"x]gx_ALT-8{motion} Delete the current whole \\_sWORD\\_s [into register x]\r\n                        and apply the deletion to all \/ the first [N]\r\n                        occurrences inside {motion} text.\r\n\r\n[N][\"x]gcg_ALT-8{motion}Delete the current WORD [into register x] and\r\n                        ALT-8t inserting. After exiting insert mode, that text\r\n                        substitution is applied to all \/ the first [N]\r\n                        occurrences inside {motion} text.\r\n\r\n[N][\"x]gxg_ALT-8{motion}Delete the current WORD [into register x] and\r\n                        apply the deletion to all \/ the first [N] occurrences\r\n                        inside {motion} text.\r\n\r\n[N][\"x]<Leader>gc{source-motion}{target-motion}\r\n                        Delete {source-motion} text [into register x] and\r\n                        start inserting. After exiting insert mode, that text\r\n                        substitution is applied to all \/ the first [N]\r\n                        occurrences inside {target-motion} text.\r\n{Visual}[N][\"x]<Leader>gc{motion}\r\n                        Delete the selected text [into register x] and start\r\n                        inserting. After exiting insert mode, that text\r\n                        substitution is applied to all \/ the first [N]\r\n                        occurrences inside {motion} text.\r\n\r\n[N][\"x]<Leader>gx{source-motion}{target-motion}\r\n                        Delete the {source-motion} text [into register x] and\r\n                        apply the deletion to all \/ the first [N] occurrences\r\n                        inside {target-motion} text.\r\n{Visual}[N][\"x]<Leader>gx{motion}\r\n                        Delete the selected text [into register x] and apply\r\n                        the deletion to all \/ the first [N] occurrences inside\r\n                        {motion} text.\r\n\r\n                        When any of these commands is repeated via ., the\r\n                        previous substitution of the same source text is\r\n                        re-applied to {motion} (relative to the current\r\n                        position now) again.\r\n                        With the visualrepeat.vim plugin, you can also\r\n                        directly reapply to the current selection instead of\r\n                        the previous {motion}. Further repeats will then\r\n                        target a selection of the same size as before.\r\nEXAMPLE\r\nSuppose you have a line like this, and you want to change \"de\" to \"en\":\r\nA[lang=de]:after, SPAN[lang=de]:after { content: url(\"lang.de.gif\"); }\r\n\r\nWith the cursor on the start of any of the \"de\", type |gc|e, enter the text\r\n\"en\", then press <Esc>. The line will turn into\r\nA[lang=en]:after, SPAN[lang=en]:after { content: url(\"lang.en.gif\"); }\r\nYou can now re-apply this substitution to other lines or a visual selection\r\nvia . repeat.\r\n\r\nNow we want to change all SPAN to DIV in the current paragraph. Position the\r\ncursor on the SPAN and type |gc*|ip, enter \"DIV\", and press <Esc>. You'll get\r\nA[lang=en]:after, DIV[lang=en]:after { content: url(\"lang.en.gif\"); }\r\nThe change is also propagated to surrounding lines, according to the ip text\r\nobject.\r\n\r\nNow let's get rid of the \":after\" in this line and the next 3 ones. With the\r\ncursor on the \":\", type |<Leader>gx|t,3+, and the line turns to\r\nA[lang=en], DIV[lang=en] { content: url(\"lang.en.gif\"); }\r\nas the t, chooses the source text (to be deleted), and 3+ is a motion that\r\nincludes the next 3 lines.","4":"DESCRIPTION\r\nChanging existing text is one of the main editing tasks. In Vim, there are two\r\napproaches: Either use the c and s commands, then quit insert mode; maybe\r\nrepeat this via . at another location. Or build a :substitute command for\r\ncontrolled replacement in the line, range, or buffer.\r\nThis plugin implements a hybrid of these two contrasting approaches: It offers\r\na gc command that works just like built-in c, and after leaving insert\r\nmode applies the local substitution to all other occurrences in the current\r\nline (in case of a small character change) or, when entire line(s) were\r\nchanged, to the rest of the buffer.\r\n\r\nHOW IT WORKS\r\nThe gc command hooks itself into the InsertLeave event, then applies\r\nsomething like :s\/\\=@\"\/\\=@.\/g to the line or buffer.\r\n\r\nSEE ALSO\r\n- ReplaceWithRegister (vimscript #2703) simplifies another frequent editing\r\n  task: Replace the selection with the contents of register.\r\n- ChangeGloballySmartCase (vimscript #4322) is an add-on to this plugin that\r\n  implements a gC variant that uses a \"smart case\" substitution which covers\r\n  variations in upper-\/lowercase (\"maxSize\" vs. \"MaxSize\") as well as\r\n  different coding styles like CamelCase and underscore_notation (\"maxSize\",\r\n  \"MAX_SIZE\").\r\n\r\nRELATED WORKS\r\n- Without the plugin, you can use the star or \/ commands to search for the\r\n  existing text, then use cgn to change the next occurrence, then repeat\r\n  this with . as often as needed.\r\n- multichange.vim (vimscript #4309) uses a command :[range]MultiChange to\r\n  modify the default c command to do an entire-word global substitution in the\r\n  entire range.\r\n- vim-subversive (https:\/\/github.com\/svermeulen\/vim-subversive) implements a\r\n  \"substitute over range motion\" that works like gc* and <Leader>gc, but\r\n  queries for the replacement text instead of letting you edit it in the\r\n  buffer.\r\n- vim-mode-plus for the Atom editor has an occurrence modifier for\r\n  operator-pending mode\r\n  (https:\/\/github.com\/t9md\/atom-vim-mode-plus\/wiki\/OccurrenceModifier) that\r\n  applies the current word to the {motion} text, working like gc* \/ gx* (but\r\n  not limited to change and delete, so other commands like gU also work).\r\n\r\nUSAGE\r\n[N][\"x]gc{motion}       Delete {motion} text [into register x] and start\r\n                        inserting.\r\n{Visual}[N][\"x]gc       Delete the highlighted text [into register x] and\r\n                        start inserting.\r\n                        After exiting insert mode, the substitution is\r\n                        applied:\r\n                        - For characterwise motions \/ selections: Globally to\r\n                          the changed line if possible, or globally in the\r\n                          entire buffer when no additional substitution can be\r\n                          made in the changed line or a very large [N] is\r\n                          given g:ChangeGlobally_GlobalCountThreshold.\r\n                        - For linewise motions \/ selections: Globally (for\r\n                          identical complete lines) in the entire buffer.\r\n                        - [N] times (including the just completed change, so\r\n                          only N > 1 really makes sense), starting from the\r\n                          position of the changed text, also moving into\r\n                          following lines if not all [N] substitutions can be\r\n                          made in the current line. To avoid this spill-over,\r\n                          and just apply all possible substitutions from the\r\n                          current position to the end of the line, you can\r\n                          specify g:ChangeGlobally_LimitToCurrentLineCount.\r\n                          Note: A possible [count] inside {motion} is\r\n                          different from [N]; e.g., 2gc3w changes 3 words, and\r\n                          then applies this change 1 more time.\r\n\r\n                        The substitution is always done case-sensitive,\r\n                        regardless of the 'ignorecase' setting.\r\n                        When the changed text is surrounded by keyword\r\n                        boundaries (\/\\<text\\>\/), only keyword matches are\r\n                        replaced so spurious matches inside keywords (e.g.\r\n                        \"IN\" inside \"rINg\") are ignored. This does not apply\r\n                        to visual selections.\r\n\r\n[\"x]gcc                 Delete [count] lines [into register x] and start\r\n                        insert linewise. If 'autoindent' is on, preserve the\r\n                        indent of the first line. After exiting insert mode,\r\n                        the substitution is applied globally.\r\n\r\n                        When a command is repeated via ., the previous\r\n                        substitution (without entering a new insert mode) is\r\n                        re-applied to the visual selection, [count] next\r\n                        lines, or the range of the previous substitution.\r\n                        For a command that used a limit [N], the number of\r\n                        substitutions and the start column from where they\r\n                        were applied are kept.\r\n\r\n                        With the visualrepeat.vim plugin, commands can be\r\n                        repeated on a blockwise-visual selection. In that\r\n                        case:\r\n                        - A repeat of gcc matches not only complete lines\r\n                          (they probably aren't fully selected), just the text\r\n                          itself.\r\n                        - Start column and [N] limit restrictions are dropped;\r\n                          the change is applied anywhere inside the selected\r\n                          block.\r\n                        All these modifications are kept for subsequent\r\n                        repeats of the repeat, so the blockwise repeat can be\r\n                        cleverly employed to remove certain change\r\n                        restrictions for following repeats of different kinds.\r\n\r\n[N][\"x]gx{motion}       Delete {motion} text [into register x] and apply the\r\n                        deletion.\r\n{Visual}[N][\"x]gx       Delete the highlighted text [into register x] and\r\n                        apply the deletion, like with gc.\r\n[\"x]gxx                 Delete [count] lines [into register x] and apply the\r\n                        deletion globally.\r\n\r\n[N][\"x]gc*{motion}      Delete the current whole \\<word\\> [into register x]\r\n                        and start inserting. After exiting insert mode, that\r\n                        text substitution is applied to all \/ the first [N]\r\n                        occurrences inside {motion} text.\r\n\r\n[N][\"x]gx*{motion}      Delete the current whole \\<word\\> [into register x]\r\n                        and apply the deletion to all \/ the first [N]\r\n                        occurrences inside {motion} text.\r\n\r\n[N][\"x]gcg*{motion}     Delete the current word [into register x] and\r\n                        start inserting. After exiting insert mode, that text\r\n                        substitution is applied to all \/ the first [N]\r\n                        occurrences inside {motion} text.\r\n\r\n[N][\"x]gxg*{motion}     Delete the current word [into register x] and\r\n                        apply the deletion to all \/ the first [N] occurrences\r\n                        inside {motion} text.\r\n\r\n[N][\"x]gc_ALT-8{motion} Delete the current whole \\_sWORD\\_s [into register x]\r\n                        and ALT-8t inserting. After exiting insert mode, that\r\n                        text substitution is applied to all \/ the first [N]\r\n                        occurrences inside {motion} text.\r\n\r\n[N][\"x]gx_ALT-8{motion} Delete the current whole \\_sWORD\\_s [into register x]\r\n                        and apply the deletion to all \/ the first [N]\r\n                        occurrences inside {motion} text.\r\n\r\n[N][\"x]gcg_ALT-8{motion}Delete the current WORD [into register x] and\r\n                        ALT-8t inserting. After exiting insert mode, that text\r\n                        substitution is applied to all \/ the first [N]\r\n                        occurrences inside {motion} text.\r\n\r\n[N][\"x]gxg_ALT-8{motion}Delete the current WORD [into register x] and\r\n                        apply the deletion to all \/ the first [N] occurrences\r\n                        inside {motion} text.\r\n\r\n[N][\"x]<Leader>gc{source-motion}{target-motion}\r\n                        Delete {source-motion} text [into register x] and\r\n                        start inserting. After exiting insert mode, that text\r\n                        substitution is applied to all \/ the first [N]\r\n                        occurrences inside {target-motion} text.\r\n{Visual}[N][\"x]<Leader>gc{motion}\r\n                        Delete the selected text [into register x] and start\r\n                        inserting. After exiting insert mode, that text\r\n                        substitution is applied to all \/ the first [N]\r\n                        occurrences inside {motion} text.\r\n\r\n[N][\"x]<Leader>gx{source-motion}{target-motion}\r\n                        Delete the {source-motion} text [into register x] and\r\n                        apply the deletion to all \/ the first [N] occurrences\r\n                        inside {target-motion} text.\r\n{Visual}[N][\"x]<Leader>gx{motion}\r\n                        Delete the selected text [into register x] and apply\r\n                        the deletion to all \/ the first [N] occurrences inside\r\n                        {motion} text.\r\n\r\n                        When any of these commands is repeated via ., the\r\n                        previous substitution of the same source text is\r\n                        re-applied to {motion} (relative to the current\r\n                        position now) again.\r\n                        With the visualrepeat.vim plugin, you can also\r\n                        directly reapply to the current selection instead of\r\n                        the previous {motion}. Further repeats will then\r\n                        target a selection of the same size as before.\r\nEXAMPLE\r\nSuppose you have a line like this, and you want to change \"de\" to \"en\":\r\nA[lang=de]:after, SPAN[lang=de]:after { content: url(\"lang.de.gif\"); }\r\n\r\nWith the cursor on the start of any of the \"de\", type |gc|e, enter the text\r\n\"en\", then press <Esc>. The line will turn into\r\nA[lang=en]:after, SPAN[lang=en]:after { content: url(\"lang.en.gif\"); }\r\nYou can now re-apply this substitution to other lines or a visual selection\r\nvia . repeat.\r\n\r\nNow we want to change all SPAN to DIV in the current paragraph. Position the\r\ncursor on the SPAN and type |gc*|ip, enter \"DIV\", and press <Esc>. You'll get\r\nA[lang=en]:after, DIV[lang=en]:after { content: url(\"lang.en.gif\"); }\r\nThe change is also propagated to surrounding lines, according to the ip text\r\nobject.\r\n\r\nNow let's get rid of the \":after\" in this line and the next 3 ones. With the\r\ncursor on the \":\", type |<Leader>gx|t,3+, and the line turns to\r\nA[lang=en], DIV[lang=en] { content: url(\"lang.en.gif\"); }\r\nas the t, chooses the source text (to be deleted), and 3+ is a motion that\r\nincludes the next 3 lines.","install_details":"INSTALLATION\r\nThe code is hosted in a Git repo at\r\n    https:\/\/github.com\/inkarkat\/vim-ChangeGlobally\r\nYou can use your favorite plugin manager, or \"git clone\" into a directory used\r\nfor Vim packages. Releases are on the \"stable\" branch, the latest unstable\r\ndevelopment snapshot on \"master\".\r\n\r\nThis script is also packaged as a vimball. If you have the \"gunzip\"\r\ndecompressor in your PATH, simply edit the *.vmb.gz package in Vim; otherwise,\r\ndecompress the archive first, e.g. using WinZip. Inside Vim, install by\r\nsourcing the vimball or via the :UseVimball command.\r\n    vim ChangeGlobally*.vmb.gz\r\n    :so %\r\nTo uninstall, use the :RmVimball command.\r\n\r\nDEPENDENCIES\r\n- Requires Vim 7.0 or higher.\r\n- Requires the ingo-library.vim plugin (vimscript #4433), version 1.040 or\r\n  higher.\r\n- repeat.vim (vimscript #2136) plugin (optional)\r\n- visualrepeat.vim (vimscript #3848) plugin (version 2.00 or higher; optional)\r\n\r\nCONFIGURATION\r\nFor a permanent configuration, put the following commands into your vimrc:\r\n\r\nTo apply a characterwise substitution globally in the entire buffer even when\r\nthere are additional substitutions in the current line, a very large [count]\r\ncan be supplied. To change the threshold, use:\r\n    let g:ChangeGlobally_GlobalCountThreshold = 999\r\nTo turn off this feature, set the threshold to 0.\r\n\r\nAs it's sometimes not easy to quickly count the number of occurrences to\r\nreplace, or particular occurrences have to be skipped, the special count value\r\nof 888 makes the commands switch to confirm each replacement (via the :s_c\r\nflag). You can change this value or turn off this feature by setting it to 0:\r\n    let g:ChangeGlobally_ConfirmCount = 0\r\n\r\nA count [N] for a characterwise gc motion \/ selection will also substitute\r\nin subsequent lines if there are less than [N] matches in the current line. To\r\navoid that, you can specify a special number [N], which limits the\r\nsubstitutions to the end of the current line. You can change this value or\r\nturn off this feature by setting it to 0:\r\n    let g:ChangeGlobally_LimitToCurrentLineCount = 99\r\n\r\nIf you want no or only a few of the available mappings, you can completely\r\nturn off the creation of the default mappings by defining:\r\n    :let g:ChangeGlobally_no_mappings = 1\r\nThis saves you from mapping dummy keys to all unwanted mapping targets.\r\n\r\nIf you want to use different mappings, map your keys to the <Plug>(Change...)\r\nand <Plug>(Delete...) mapping targets _before_ sourcing the script (e.g. in\r\nyour vimrc):\r\n    nmap <Leader>c <Plug>(ChangeGloballyOperator)\r\n    nmap <Leader>cc <Plug>(ChangeGloballyLine)\r\n    xmap <Leader>c <Plug>(ChangeGloballyVisual)\r\n    nmap <Leader>x <Plug>(DeleteGloballyOperator)\r\n    nmap <Leader>xx <Plug>(DeleteGloballyLine)\r\n    xmap <Leader>x <Plug>(DeleteGloballyVisual)\r\n\r\n    nmap gc* <Plug>(ChangeWholeWordOperator)\r\n    nmap gx* <Plug>(DeleteWholeWordOperator)\r\n    nmap gcg* <Plug>(ChangeWordOperator)\r\n    nmap gxg* <Plug>(DeleteWordOperator)\r\n    nmap gc<A-8> <Plug>(ChangeWholeWORDOperator)\r\n    nmap gx<A-8> <Plug>(DeleteWholeWORDOperator)\r\n    nmap gcg<A-8> <Plug>(ChangeWORDOperator)\r\n    nmap gxg<A-8> <Plug>(DeleteWORDOperator)\r\n    nmap <Leader>gc <Plug>(ChangeOperatorOperator)\r\n    nmap <Leader>gx <Plug>(DeleteOperatorOperator)\r\n    xmap <Leader>gc <Plug>(ChangeSelectionOperator)\r\n    xmap <Leader>gx <Plug>(DeleteSelectionOperator)","5":"INSTALLATION\r\nThe code is hosted in a Git repo at\r\n    https:\/\/github.com\/inkarkat\/vim-ChangeGlobally\r\nYou can use your favorite plugin manager, or \"git clone\" into a directory used\r\nfor Vim packages. Releases are on the \"stable\" branch, the latest unstable\r\ndevelopment snapshot on \"master\".\r\n\r\nThis script is also packaged as a vimball. If you have the \"gunzip\"\r\ndecompressor in your PATH, simply edit the *.vmb.gz package in Vim; otherwise,\r\ndecompress the archive first, e.g. using WinZip. Inside Vim, install by\r\nsourcing the vimball or via the :UseVimball command.\r\n    vim ChangeGlobally*.vmb.gz\r\n    :so %\r\nTo uninstall, use the :RmVimball command.\r\n\r\nDEPENDENCIES\r\n- Requires Vim 7.0 or higher.\r\n- Requires the ingo-library.vim plugin (vimscript #4433), version 1.040 or\r\n  higher.\r\n- repeat.vim (vimscript #2136) plugin (optional)\r\n- visualrepeat.vim (vimscript #3848) plugin (version 2.00 or higher; optional)\r\n\r\nCONFIGURATION\r\nFor a permanent configuration, put the following commands into your vimrc:\r\n\r\nTo apply a characterwise substitution globally in the entire buffer even when\r\nthere are additional substitutions in the current line, a very large [count]\r\ncan be supplied. To change the threshold, use:\r\n    let g:ChangeGlobally_GlobalCountThreshold = 999\r\nTo turn off this feature, set the threshold to 0.\r\n\r\nAs it's sometimes not easy to quickly count the number of occurrences to\r\nreplace, or particular occurrences have to be skipped, the special count value\r\nof 888 makes the commands switch to confirm each replacement (via the :s_c\r\nflag). You can change this value or turn off this feature by setting it to 0:\r\n    let g:ChangeGlobally_ConfirmCount = 0\r\n\r\nA count [N] for a characterwise gc motion \/ selection will also substitute\r\nin subsequent lines if there are less than [N] matches in the current line. To\r\navoid that, you can specify a special number [N], which limits the\r\nsubstitutions to the end of the current line. You can change this value or\r\nturn off this feature by setting it to 0:\r\n    let g:ChangeGlobally_LimitToCurrentLineCount = 99\r\n\r\nIf you want no or only a few of the available mappings, you can completely\r\nturn off the creation of the default mappings by defining:\r\n    :let g:ChangeGlobally_no_mappings = 1\r\nThis saves you from mapping dummy keys to all unwanted mapping targets.\r\n\r\nIf you want to use different mappings, map your keys to the <Plug>(Change...)\r\nand <Plug>(Delete...) mapping targets _before_ sourcing the script (e.g. in\r\nyour vimrc):\r\n    nmap <Leader>c <Plug>(ChangeGloballyOperator)\r\n    nmap <Leader>cc <Plug>(ChangeGloballyLine)\r\n    xmap <Leader>c <Plug>(ChangeGloballyVisual)\r\n    nmap <Leader>x <Plug>(DeleteGloballyOperator)\r\n    nmap <Leader>xx <Plug>(DeleteGloballyLine)\r\n    xmap <Leader>x <Plug>(DeleteGloballyVisual)\r\n\r\n    nmap gc* <Plug>(ChangeWholeWordOperator)\r\n    nmap gx* <Plug>(DeleteWholeWordOperator)\r\n    nmap gcg* <Plug>(ChangeWordOperator)\r\n    nmap gxg* <Plug>(DeleteWordOperator)\r\n    nmap gc<A-8> <Plug>(ChangeWholeWORDOperator)\r\n    nmap gx<A-8> <Plug>(DeleteWholeWORDOperator)\r\n    nmap gcg<A-8> <Plug>(ChangeWORDOperator)\r\n    nmap gxg<A-8> <Plug>(DeleteWORDOperator)\r\n    nmap <Leader>gc <Plug>(ChangeOperatorOperator)\r\n    nmap <Leader>gx <Plug>(DeleteOperatorOperator)\r\n    xmap <Leader>gc <Plug>(ChangeSelectionOperator)\r\n    xmap <Leader>gx <Plug>(DeleteSelectionOperator)","first_name":"Ingo","6":"Ingo","last_name":"Karkat","7":"Karkat","releases":[{"0":"4321","vim_version":"7.0","1":"7.0","script_version":"2.01","2":"2.01","version_comment":"- Support {target-motion} of |gv| in <Leader>gc and <Leader>gx to replace in the last selection. (Previously, the {source-motion} clobbered the user-established visual selection.)\r\n- The custom operators don't clobber the previous visual selection any longer.\r\n- BUG: Regression: gcc and gxx broken by forgotten adaptation of regexp magicness.","3":"- Support {target-motion} of |gv| in <Leader>gc and <Leader>gx to replace in the last selection. (Previously, the {source-motion} clobbered the user-established visual selection.)\r\n- The custom operators don't clobber the previous visual selection any longer.\r\n- BUG: Regression: gcc and gxx broken by forgotten adaptation of regexp magicness.","package":"ChangeGlobally-2.01.vmb.gz","4":"ChangeGlobally-2.01.vmb.gz","src_id":"27033","5":"27033","creation_date":"1582609448","6":"1582609448"},{"0":"4321","vim_version":"7.0","1":"7.0","script_version":"2.00","2":"2.00","version_comment":"- ENH: Add a set of mappings that apply the change \/ deletion of cword \/ cWORD \/ selection over the text moved over by {motion}. So instead of specifying the source text via {motion}, the target area is specified. There's even a mapping that lets you specify both source and target as two {motion}s!\r\n- Implement special case for the black-hole register, where we cannot extract the original text.\r\n- ENH: Allow to disable all default mappings via a single g:ChangeGlobally_no_mappings configuration flag. *** You need to update to ingo-library (vimscript #4433) version 1.040! ***","3":"- ENH: Add a set of mappings that apply the change \/ deletion of cword \/ cWORD \/ selection over the text moved over by {motion}. So instead of specifying the source text via {motion}, the target area is specified. There's even a mapping that lets you specify both source and target as two {motion}s!\r\n- Implement special case for the black-hole register, where we cannot extract the original text.\r\n- ENH: Allow to disable all default mappings via a single g:ChangeGlobally_no_mappings configuration flag. *** You need to update to ingo-library (vimscript #4433) version 1.040! ***","package":"ChangeGlobally-2.00.vmb.gz","4":"ChangeGlobally-2.00.vmb.gz","src_id":"26969","5":"26969","creation_date":"1581309048","6":"1581309048"},{"0":"4321","vim_version":"7.0","1":"7.0","script_version":"1.31","2":"1.31","version_comment":"- BUG: When a {N}gc{motion} substitution is repeated, is it applied only to the current, single line, not for {N} instances in subsequent lines. ChangeGlobally#Repeat().\r\n- Default to applying {N}gc{motion} beyond the current line, unless a count of g:ChangeGlobally_LimitToCurrentLineCount is given. Especially with 'hlsearch', one often can see the (low) number of substitutions in the few following lines, and it's comfortable to be able to change them all in one fell swoop, instead of applying to just the current line and then having to repeat over the next few lines with [count]. command.","3":"- BUG: When a {N}gc{motion} substitution is repeated, is it applied only to the current, single line, not for {N} instances in subsequent lines. ChangeGlobally#Repeat().\r\n- Default to applying {N}gc{motion} beyond the current line, unless a count of g:ChangeGlobally_LimitToCurrentLineCount is given. Especially with 'hlsearch', one often can see the (low) number of substitutions in the few following lines, and it's comfortable to be able to change them all in one fell swoop, instead of applying to just the current line and then having to repeat over the next few lines with [count]. command.","package":"ChangeGlobally-1.31.vmb.gz","4":"ChangeGlobally-1.31.vmb.gz","src_id":"26257","5":"26257","creation_date":"1541312806","6":"1541312806"},{"0":"4321","vim_version":"7.0","1":"7.0","script_version":"1.30","2":"1.30","version_comment":"- ENH: Implement global delete (gx{motion}, gxx) as a specialization of an empty change.","3":"- ENH: Implement global delete (gx{motion}, gxx) as a specialization of an empty change.","package":"ChangeGlobally-1.30.vmb.gz","4":"ChangeGlobally-1.30.vmb.gz","src_id":"22692","5":"22692","creation_date":"1418415760","6":"1418415760"},{"0":"4321","vim_version":"7.0","1":"7.0","script_version":"1.21","2":"1.21","version_comment":"- FIX: Disable global substitution when g:ChangeGlobally_GlobalCountThreshold is 0, as is documented.\r\n- ENH: Confirm each replacement via :s_c flag when a special g:ChangeGlobally_ConfirmCount is given.","3":"- FIX: Disable global substitution when g:ChangeGlobally_GlobalCountThreshold is 0, as is documented.\r\n- ENH: Confirm each replacement via :s_c flag when a special g:ChangeGlobally_ConfirmCount is given.","package":"ChangeGlobally-1.21.vmb.gz","4":"ChangeGlobally-1.21.vmb.gz","src_id":"21826","5":"21826","creation_date":"1398434160","6":"1398434160"},{"0":"4321","vim_version":"7.0","1":"7.0","script_version":"1.20","2":"1.20","version_comment":"- ENH: Special handling for repeat on blockwise selection (through visualrepeat.vim) that makes more sense.\r\n- Autocmds may interfere with the plugin when they temporarily leave insert mode (i_CTRL-O) or create an undo point (i_CTRL-G_u). Disable them until the user is done inserting.\r\n- Use optional visualrepeat#reapply#VisualMode() for normal mode repeat of a visual mapping. When supplying a [count] on such repeat of a previous linewise selection, now [count] number of lines instead of [count] times the original selection is used.\r\n- Avoid changing the jumplist.\r\n- ENH: Handle undo points created during insertion: Undo the whole insertion sequence (by using :undo with the original change number) and substitute the entire captured insertion, not just the last part, by detecting a multi-change insert and using the original start position instead of the start change mark.\r\n- Add dependency to ingo-library (vimscript #4433). *** You need to separately install ingo-library (vimscript #4433) version 1.011 (or higher)! ***","3":"- ENH: Special handling for repeat on blockwise selection (through visualrepeat.vim) that makes more sense.\r\n- Autocmds may interfere with the plugin when they temporarily leave insert mode (i_CTRL-O) or create an undo point (i_CTRL-G_u). Disable them until the user is done inserting.\r\n- Use optional visualrepeat#reapply#VisualMode() for normal mode repeat of a visual mapping. When supplying a [count] on such repeat of a previous linewise selection, now [count] number of lines instead of [count] times the original selection is used.\r\n- Avoid changing the jumplist.\r\n- ENH: Handle undo points created during insertion: Undo the whole insertion sequence (by using :undo with the original change number) and substitute the entire captured insertion, not just the last part, by detecting a multi-change insert and using the original start position instead of the start change mark.\r\n- Add dependency to ingo-library (vimscript #4433). *** You need to separately install ingo-library (vimscript #4433) version 1.011 (or higher)! ***","package":"ChangeGlobally-1.20.vmb.gz","4":"ChangeGlobally-1.20.vmb.gz","src_id":"21059","5":"21059","creation_date":"1384855525","6":"1384855525"},{"0":"4321","vim_version":"7.0","1":"7.0","script_version":"1.01","2":"1.01","version_comment":"BUG: Linewise changes (gcc) causes beep instead of substitution.","3":"BUG: Linewise changes (gcc) causes beep instead of substitution.","package":"ChangeGlobally-1.01.vmb.gz","4":"ChangeGlobally-1.01.vmb.gz","src_id":"19393","5":"19393","creation_date":"1358632696","6":"1358632696"},{"0":"4321","vim_version":"7.0","1":"7.0","script_version":"1.00","2":"1.00","version_comment":"Initial upload","3":"Initial upload","package":"ChangeGlobally-1.00.vmb.gz","4":"ChangeGlobally-1.00.vmb.gz","src_id":"19021","5":"19021","creation_date":"1353668903","6":"1353668903"}]},"4320":{"script_id":"4320","0":"4320","script_name":"SearchHighlighting","1":"SearchHighlighting","script_type":"utility","2":"utility","summary":"Highlighting of searches via star, auto-highlighting.","3":"Highlighting of searches via star, auto-highlighting.","description":"DESCRIPTION\r\nThis plugin changes the star command *, so that it doesn't jump to the next\r\nmatch. (Unless you supply a [count], so 1* now restores the old * behavior.)\r\nIf you issue a star command on the same text as before, the search\r\nhighlighting is turned off (via :nohlsearch); the search pattern remains\r\nset, so a n \/ N command will turn highlighting on again. With this, you\r\ncan easily toggle highlighting for the current word \/ visual selection.\r\n\r\nWith the disabling of the jump to the next match, there is no difference\r\nbetween * and # any more, so the # key can now be used for some other mapping.\r\n\r\nThis plugin also extends the star command to visual mode, where instead of\r\nthe current word, the selected text is used as the literal search pattern.\r\n\r\nThe auto-search functionality instantly highlights the word under the cursor\r\nwhen typing or moving around. This can be helpful while browsing source code;\r\nwhenever you position the cursor on an identifier, all other occurrences are\r\ninstantly highlighted. This functionality is toggled on\/off via <Leader>*. You\r\ncan also :nohlsearch to temporarily disable the highlighting.\r\n\r\nSEE ALSO\r\n- mark.vim (vimscript #2666) can highlight several patterns in different\r\n  colors simultaneously.\r\n- SearchAlternatives.vim (vimscript #4146) can add and subtract search\r\n  alternatives via mappings and commands.\r\n- To also show the number of matches when selecting a word (*, g* etc.),\r\n  you can append the corresponding command to the <Plug> mapping (see\r\n  SearchHighlighting-remap):\r\n    nmap <silent> * <Plug>SearchHighlightingStarm`:%s\/\/\/gn<CR>g``\r\n The SearchPosition.vim plugin (vimscript #2634) provides an extended\r\n  version of that command.\r\n\r\nRELATED WORKS\r\nI came up with this on my own; however, the idea can be traced back to\r\nfrancoissteinmetz and da.thompson in the comments of vimtip #1 (now at\r\nhttps:\/\/vim.fandom.com\/wiki\/Search_for_visually_selected_text):\r\n    map <silent> <F10> :set invhls<CR>:let @\/=\"<C-r><C-w>\"<CR>\r\n\r\n- highlight_word_under_cursor.vim (vimscript #4287) implements the search\r\n  auto-highlighting of the whole and optionally current word.\r\n- HiCursorWords (vimscript #4306) highlights the word under the cursor, with\r\n  optional delay and limited to certain syntax groups.\r\n- Matchmaker (https:\/\/github.com\/qstrahl\/vim-matchmaker) highlights the word\r\n  under the cursor with matchadd(), not the current search pattern.\r\n- star search (vimscript #4335) changes the behavior of * to not jump to the\r\n  next match, and includes the visual search from the next plugin\r\n- https:\/\/github.com\/bronson\/vim-visual-star-search provides searching of the\r\n  visual selection\r\n- visualstar.vim (vimscript #2944) provides searching of the visual selection\r\n- select & search (vimscript #4819) can use either n\/N or * in the visual\r\n  selection, and (like this plugin) can avoid jumping.\r\n- vim-cursorword (vimscript #5100) automatically underlines the current word\r\n  in the current window (like :SearchAutoHighlighting), but uses :match\r\n  instead of search\r\n- vim-asterisk (vimscript #5059) is quite similar, providing a z* mapping that\r\n  also doesn't jump, visual *, more intuitive smartcase handling, and can keep\r\n  the cursor position when jumping (like ,*)\r\n- searchant.vim (vimscript #5404) hooks into the built-in search commands and\r\n  provides a separate highlighting for the match last jumped to.\r\n\r\nUSAGE\r\n*                       Toggle search highlighting for the current whole\r\n                        \\<word\\> on\/off.\r\ng*                      Toggle search highlighting for the current word\r\n                        on\/off.\r\n\r\n{Visual}*               Toggle search highlighting for the selection on\/off.\r\n                        For a blockwise-visual selection, not just lines\r\n                        that match the block's lines on their own are matched,\r\n                        but all occurrences that contain the block's text,\r\n                        though not just with the same vertical alignment (that\r\n                        isn't possible to assert with Vim's regular\r\n                        expressions), and only the first line's match is\r\n                        highlighted. For example, a match on\r\n                            foo\r\n                            bar\r\n                        will also match all three occurrences in\r\n                            foo    my foo is        tell foo\r\n                            bar    inside bar               bar\r\n                        but not a single\r\n                            foo\r\n\r\n{count}*                Search forward for the {count}'th occurrence of the\r\n{count}g*               word nearest to the cursor.\r\n{Visual}{count}*\r\n\r\nALT-8                   Toggle search highlighting for the current whole\r\n                        \\_sWORD\\_s on\/off. With [count]: Search forward for the\r\n                        [count]'th occurrence.\r\ng_ALT-8                 Toggle search highlighting for the current WORD\r\n                        on\/off. With [count]: Search forward for the\r\n                        [count]'th occurrence.\r\n\r\n[count],*               Search forward for the [count]'th occurrence of the\r\n                        word under the cursor, keeping the cursor at the\r\n                        current position within the word's matches (via\r\n                        search-offset).\r\n                        Observes the new non-jumping behavior of the star\r\n                        commands without a [count].\r\n[count],g*              Like above: variants of the searches that keep the\r\n,_ALT-8                 cursor at the current relative match position.\r\n,g_ALT-8                Note that if you have set mapleader to \",\", some of\r\n                        these would conflict with other plugin mappings; you\r\n                        have to define|SearchHighlighting-configuration|\r\n                        yourself.\r\n\r\n[count],n               Repeat the latest \"\/\" search [count] times, keeping\r\n                        the cursor at the current position relative to the end\r\n                        of the current match (via search-offset).\r\n                        Like ,star, but reuses the last search pattern\r\n                        instead of searching for the word under the cursor.\r\n                        As such, the cursor can also be outside a match (but\r\n                        still within the same line), and a corresponding\r\n                        offset (the smallest possible if there are several\r\n                        nearby matches) is chosen.\r\n[count],N               Repeat the latest \"?\" search [count] times, keeping\r\n                        the cursor at the current position relative to the\r\n                        start of the current match (via search-offset).\r\n                        Note: To avoid another set of mappings, the search\r\n                        direction and offset anchor (start or end of match)\r\n                        are combined here. The search direction can easily be\r\n                        reverted via |n|\/|N|, anyway.\r\n\r\n<Leader>*               Toggle auto-search highlighting (using the last\r\n                        {what}; default is \"wword\").\r\n{Visual}<Leader>*       Toggle auto-search highlighting; when turning on, a\r\n                        {what} value of \"selection\" is used (but the preset\r\n                        isn't changed; the original value is used for a later\r\n                        non-visual mode auto-search).\r\n\r\n:SearchAutoHighlighting [{what}]\r\n                        Turn on automatic highlighting of occurrences of\r\n                        {what} in normal mode, and the selected text in visual\r\n                        \/ select mode. Possible values:\r\n                        cchar: current character under cursor\r\n                        wword: whole cword, like star; this is the default\r\n                        wWORD: whole cWORD, delimited by whitespace\r\n                        cword: current word under cursor\r\n                        cWORD: current WORD under cursor\r\n                        line:  current text in line, excluding indent and\r\n                               trailing whitespace\r\n                        exactline:  exact current line\r\n                        from-cursor:only consider the text from the beginning\r\n                                    of the line up to the cursor; ignore text\r\n                                    before the cursor\r\n                        to-cursor:  only consider the text from the cursor to\r\n                                    the end of the line\r\n                        selection:  only highlight selected text, in normal\r\n                                    mode, nothing is selected\r\n                        *-iw:       allow for variations in whitespace (also\r\n                                    newline characters, i.e. allow a match\r\n                                    distributed over multiple lines), and\r\n                                    ignore any comment prefixes (e.g. \/*, #),\r\n                                    too.\r\n                        *-nw:       allow for variations in whitespace and also\r\n                                    direct concatenation of lines (i.e. without\r\n                                    any whitespace in between)\r\n\r\n:NoSearchAutoHighlighting[!]\r\n                        Turn off automatic highlighting. With [!], also turn\r\n                        off all tab page- and window-local ones.\r\n\r\n:SearchAutoHighlightingWinLocal [{what}]\r\n:SearchAutoHighlightingTabLocal [{what}]\r\n                        Like :SearchAutoHighlighting, but limit the effect\r\n                        to the current window \/ tab page. Different {what}\r\n                        occurrences can be configured for each instance.\r\n\r\n:NoSearchAutoHighlightingWinLocal[!]\r\n:NoSearchAutoHighlightingTabLocal[!]\r\n                        Like :NoSearchAutoHighlighting, but only for the\r\n                        current window \/ tab page. With [!], it explicitly\r\n                        turns off Auto Search (even if a higher scope still\r\n                        has it active), without it, it will still consider the\r\n                        higher scopes.","4":"DESCRIPTION\r\nThis plugin changes the star command *, so that it doesn't jump to the next\r\nmatch. (Unless you supply a [count], so 1* now restores the old * behavior.)\r\nIf you issue a star command on the same text as before, the search\r\nhighlighting is turned off (via :nohlsearch); the search pattern remains\r\nset, so a n \/ N command will turn highlighting on again. With this, you\r\ncan easily toggle highlighting for the current word \/ visual selection.\r\n\r\nWith the disabling of the jump to the next match, there is no difference\r\nbetween * and # any more, so the # key can now be used for some other mapping.\r\n\r\nThis plugin also extends the star command to visual mode, where instead of\r\nthe current word, the selected text is used as the literal search pattern.\r\n\r\nThe auto-search functionality instantly highlights the word under the cursor\r\nwhen typing or moving around. This can be helpful while browsing source code;\r\nwhenever you position the cursor on an identifier, all other occurrences are\r\ninstantly highlighted. This functionality is toggled on\/off via <Leader>*. You\r\ncan also :nohlsearch to temporarily disable the highlighting.\r\n\r\nSEE ALSO\r\n- mark.vim (vimscript #2666) can highlight several patterns in different\r\n  colors simultaneously.\r\n- SearchAlternatives.vim (vimscript #4146) can add and subtract search\r\n  alternatives via mappings and commands.\r\n- To also show the number of matches when selecting a word (*, g* etc.),\r\n  you can append the corresponding command to the <Plug> mapping (see\r\n  SearchHighlighting-remap):\r\n    nmap <silent> * <Plug>SearchHighlightingStarm`:%s\/\/\/gn<CR>g``\r\n The SearchPosition.vim plugin (vimscript #2634) provides an extended\r\n  version of that command.\r\n\r\nRELATED WORKS\r\nI came up with this on my own; however, the idea can be traced back to\r\nfrancoissteinmetz and da.thompson in the comments of vimtip #1 (now at\r\nhttps:\/\/vim.fandom.com\/wiki\/Search_for_visually_selected_text):\r\n    map <silent> <F10> :set invhls<CR>:let @\/=\"<C-r><C-w>\"<CR>\r\n\r\n- highlight_word_under_cursor.vim (vimscript #4287) implements the search\r\n  auto-highlighting of the whole and optionally current word.\r\n- HiCursorWords (vimscript #4306) highlights the word under the cursor, with\r\n  optional delay and limited to certain syntax groups.\r\n- Matchmaker (https:\/\/github.com\/qstrahl\/vim-matchmaker) highlights the word\r\n  under the cursor with matchadd(), not the current search pattern.\r\n- star search (vimscript #4335) changes the behavior of * to not jump to the\r\n  next match, and includes the visual search from the next plugin\r\n- https:\/\/github.com\/bronson\/vim-visual-star-search provides searching of the\r\n  visual selection\r\n- visualstar.vim (vimscript #2944) provides searching of the visual selection\r\n- select & search (vimscript #4819) can use either n\/N or * in the visual\r\n  selection, and (like this plugin) can avoid jumping.\r\n- vim-cursorword (vimscript #5100) automatically underlines the current word\r\n  in the current window (like :SearchAutoHighlighting), but uses :match\r\n  instead of search\r\n- vim-asterisk (vimscript #5059) is quite similar, providing a z* mapping that\r\n  also doesn't jump, visual *, more intuitive smartcase handling, and can keep\r\n  the cursor position when jumping (like ,*)\r\n- searchant.vim (vimscript #5404) hooks into the built-in search commands and\r\n  provides a separate highlighting for the match last jumped to.\r\n\r\nUSAGE\r\n*                       Toggle search highlighting for the current whole\r\n                        \\<word\\> on\/off.\r\ng*                      Toggle search highlighting for the current word\r\n                        on\/off.\r\n\r\n{Visual}*               Toggle search highlighting for the selection on\/off.\r\n                        For a blockwise-visual selection, not just lines\r\n                        that match the block's lines on their own are matched,\r\n                        but all occurrences that contain the block's text,\r\n                        though not just with the same vertical alignment (that\r\n                        isn't possible to assert with Vim's regular\r\n                        expressions), and only the first line's match is\r\n                        highlighted. For example, a match on\r\n                            foo\r\n                            bar\r\n                        will also match all three occurrences in\r\n                            foo    my foo is        tell foo\r\n                            bar    inside bar               bar\r\n                        but not a single\r\n                            foo\r\n\r\n{count}*                Search forward for the {count}'th occurrence of the\r\n{count}g*               word nearest to the cursor.\r\n{Visual}{count}*\r\n\r\nALT-8                   Toggle search highlighting for the current whole\r\n                        \\_sWORD\\_s on\/off. With [count]: Search forward for the\r\n                        [count]'th occurrence.\r\ng_ALT-8                 Toggle search highlighting for the current WORD\r\n                        on\/off. With [count]: Search forward for the\r\n                        [count]'th occurrence.\r\n\r\n[count],*               Search forward for the [count]'th occurrence of the\r\n                        word under the cursor, keeping the cursor at the\r\n                        current position within the word's matches (via\r\n                        search-offset).\r\n                        Observes the new non-jumping behavior of the star\r\n                        commands without a [count].\r\n[count],g*              Like above: variants of the searches that keep the\r\n,_ALT-8                 cursor at the current relative match position.\r\n,g_ALT-8                Note that if you have set mapleader to \",\", some of\r\n                        these would conflict with other plugin mappings; you\r\n                        have to define|SearchHighlighting-configuration|\r\n                        yourself.\r\n\r\n[count],n               Repeat the latest \"\/\" search [count] times, keeping\r\n                        the cursor at the current position relative to the end\r\n                        of the current match (via search-offset).\r\n                        Like ,star, but reuses the last search pattern\r\n                        instead of searching for the word under the cursor.\r\n                        As such, the cursor can also be outside a match (but\r\n                        still within the same line), and a corresponding\r\n                        offset (the smallest possible if there are several\r\n                        nearby matches) is chosen.\r\n[count],N               Repeat the latest \"?\" search [count] times, keeping\r\n                        the cursor at the current position relative to the\r\n                        start of the current match (via search-offset).\r\n                        Note: To avoid another set of mappings, the search\r\n                        direction and offset anchor (start or end of match)\r\n                        are combined here. The search direction can easily be\r\n                        reverted via |n|\/|N|, anyway.\r\n\r\n<Leader>*               Toggle auto-search highlighting (using the last\r\n                        {what}; default is \"wword\").\r\n{Visual}<Leader>*       Toggle auto-search highlighting; when turning on, a\r\n                        {what} value of \"selection\" is used (but the preset\r\n                        isn't changed; the original value is used for a later\r\n                        non-visual mode auto-search).\r\n\r\n:SearchAutoHighlighting [{what}]\r\n                        Turn on automatic highlighting of occurrences of\r\n                        {what} in normal mode, and the selected text in visual\r\n                        \/ select mode. Possible values:\r\n                        cchar: current character under cursor\r\n                        wword: whole cword, like star; this is the default\r\n                        wWORD: whole cWORD, delimited by whitespace\r\n                        cword: current word under cursor\r\n                        cWORD: current WORD under cursor\r\n                        line:  current text in line, excluding indent and\r\n                               trailing whitespace\r\n                        exactline:  exact current line\r\n                        from-cursor:only consider the text from the beginning\r\n                                    of the line up to the cursor; ignore text\r\n                                    before the cursor\r\n                        to-cursor:  only consider the text from the cursor to\r\n                                    the end of the line\r\n                        selection:  only highlight selected text, in normal\r\n                                    mode, nothing is selected\r\n                        *-iw:       allow for variations in whitespace (also\r\n                                    newline characters, i.e. allow a match\r\n                                    distributed over multiple lines), and\r\n                                    ignore any comment prefixes (e.g. \/*, #),\r\n                                    too.\r\n                        *-nw:       allow for variations in whitespace and also\r\n                                    direct concatenation of lines (i.e. without\r\n                                    any whitespace in between)\r\n\r\n:NoSearchAutoHighlighting[!]\r\n                        Turn off automatic highlighting. With [!], also turn\r\n                        off all tab page- and window-local ones.\r\n\r\n:SearchAutoHighlightingWinLocal [{what}]\r\n:SearchAutoHighlightingTabLocal [{what}]\r\n                        Like :SearchAutoHighlighting, but limit the effect\r\n                        to the current window \/ tab page. Different {what}\r\n                        occurrences can be configured for each instance.\r\n\r\n:NoSearchAutoHighlightingWinLocal[!]\r\n:NoSearchAutoHighlightingTabLocal[!]\r\n                        Like :NoSearchAutoHighlighting, but only for the\r\n                        current window \/ tab page. With [!], it explicitly\r\n                        turns off Auto Search (even if a higher scope still\r\n                        has it active), without it, it will still consider the\r\n                        higher scopes.","install_details":"INSTALLATION\r\nThe code is hosted in a Git repo at\r\n    https:\/\/github.com\/inkarkat\/vim-SearchHighlighting\r\nYou can use your favorite plugin manager, or \"git clone\" into a directory used\r\nfor Vim packages. Releases are on the \"stable\" branch, the latest unstable\r\ndevelopment snapshot on \"master\".\r\n\r\nThis script is also packaged as a vimball. If you have the \"gunzip\"\r\ndecompressor in your PATH, simply edit the *.vmb.gz package in Vim; otherwise,\r\ndecompress the archive first, e.g. using WinZip. Inside Vim, install by\r\nsourcing the vimball or via the :UseVimball command.\r\n    vim SearchHighlighting*.vmb.gz\r\n    :so %\r\nTo uninstall, use the :RmVimball command.\r\n\r\nDEPENDENCIES\r\n- Requires Vim 7.0 or higher.\r\n- Requires the ingo-library.vim plugin (vimscript #4433), version 1.040 or\r\n  higher.\r\n\r\nCONFIGURATION\r\nIf you want to use different mappings, map your keys to the\r\n<Plug>SearchHighlighting... mapping targets _before_ sourcing the script (e.g.\r\nin your vimrc):\r\n    nmap <Leader>&   <Plug>SearchHighlightingWORD\r\n    nmap <Leader>&&  <Plug>SearchHighlightingGWORD\r\n    nmap <Leader>*.  <Plug>SearchHighlightingCStar\r\n    nmap <Leader>**. <Plug>SearchHighlightingCGStar\r\n    nmap <Leader>&.  <Plug>SearchHighlightingCWORD\r\n    nmap <Leader>&&. <Plug>SearchHighlightingCGWORD\r\n    nmap <Leader>**  <Plug>SearchHighlightingAutoSearch\r\n\r\nIf you do not want the new non-jumping behavior of the star commands at all:\r\n    let g:SearchHighlighting_NoJump = 0\r\n    let g:SearchHighlighting_ExtendStandardCommands = 1\r\n\r\nIf you want the new non-jumping behavior, but map it to different keys:\r\n    let g:SearchHighlighting_ExtendStandardCommands = 1\r\n    nmap <Leader>*  <Plug>SearchHighlightingStar\r\n    nmap <Leader>g* <Plug>SearchHighlightingGStar\r\n    vmap <Leader>*  <Plug>SearchHighlightingStar\r\n\r\nIf you want a mapping to turn off hlsearch, use this:\r\n    nmap <A-\/> <Plug>SearchHighlightingNohlsearch\r\n    vmap <A-\/> <Plug>SearchHighlightingNohlsearch\r\n\r\nTo toggle hlsearch (temporarily, so that a new search or n command will\r\nautomatically re-enable it), use:\r\n    nmap <F12> <Plug>SearchHighlightingToggleHlsearch\r\n    vmap <F12> <Plug>SearchHighlightingToggleHlsearch\r\n","5":"INSTALLATION\r\nThe code is hosted in a Git repo at\r\n    https:\/\/github.com\/inkarkat\/vim-SearchHighlighting\r\nYou can use your favorite plugin manager, or \"git clone\" into a directory used\r\nfor Vim packages. Releases are on the \"stable\" branch, the latest unstable\r\ndevelopment snapshot on \"master\".\r\n\r\nThis script is also packaged as a vimball. If you have the \"gunzip\"\r\ndecompressor in your PATH, simply edit the *.vmb.gz package in Vim; otherwise,\r\ndecompress the archive first, e.g. using WinZip. Inside Vim, install by\r\nsourcing the vimball or via the :UseVimball command.\r\n    vim SearchHighlighting*.vmb.gz\r\n    :so %\r\nTo uninstall, use the :RmVimball command.\r\n\r\nDEPENDENCIES\r\n- Requires Vim 7.0 or higher.\r\n- Requires the ingo-library.vim plugin (vimscript #4433), version 1.040 or\r\n  higher.\r\n\r\nCONFIGURATION\r\nIf you want to use different mappings, map your keys to the\r\n<Plug>SearchHighlighting... mapping targets _before_ sourcing the script (e.g.\r\nin your vimrc):\r\n    nmap <Leader>&   <Plug>SearchHighlightingWORD\r\n    nmap <Leader>&&  <Plug>SearchHighlightingGWORD\r\n    nmap <Leader>*.  <Plug>SearchHighlightingCStar\r\n    nmap <Leader>**. <Plug>SearchHighlightingCGStar\r\n    nmap <Leader>&.  <Plug>SearchHighlightingCWORD\r\n    nmap <Leader>&&. <Plug>SearchHighlightingCGWORD\r\n    nmap <Leader>**  <Plug>SearchHighlightingAutoSearch\r\n\r\nIf you do not want the new non-jumping behavior of the star commands at all:\r\n    let g:SearchHighlighting_NoJump = 0\r\n    let g:SearchHighlighting_ExtendStandardCommands = 1\r\n\r\nIf you want the new non-jumping behavior, but map it to different keys:\r\n    let g:SearchHighlighting_ExtendStandardCommands = 1\r\n    nmap <Leader>*  <Plug>SearchHighlightingStar\r\n    nmap <Leader>g* <Plug>SearchHighlightingGStar\r\n    vmap <Leader>*  <Plug>SearchHighlightingStar\r\n\r\nIf you want a mapping to turn off hlsearch, use this:\r\n    nmap <A-\/> <Plug>SearchHighlightingNohlsearch\r\n    vmap <A-\/> <Plug>SearchHighlightingNohlsearch\r\n\r\nTo toggle hlsearch (temporarily, so that a new search or n command will\r\nautomatically re-enable it), use:\r\n    nmap <F12> <Plug>SearchHighlightingToggleHlsearch\r\n    vmap <F12> <Plug>SearchHighlightingToggleHlsearch\r\n","first_name":"Ingo","6":"Ingo","last_name":"Karkat","7":"Karkat","releases":[{"0":"4320","vim_version":"7.0","1":"7.0","script_version":"2.11","2":"2.11","version_comment":"- Minor: Also trigger LastSearchPatternChanged during auto-search whenever the search pattern changes.\r\n- Trigger separate SearchHighlightingAutoSearch User event for plugins that just want to react on auto highlighting.\r\n- Add :SearchAutoHighlighting cchar for the current character","3":"- Minor: Also trigger LastSearchPatternChanged during auto-search whenever the search pattern changes.\r\n- Trigger separate SearchHighlightingAutoSearch User event for plugins that just want to react on auto highlighting.\r\n- Add :SearchAutoHighlighting cchar for the current character","package":"SearchHighlighting-2.11.vmb.gz","4":"SearchHighlighting-2.11.vmb.gz","src_id":"28383","5":"28383","creation_date":"1678810598","6":"1678810598"},{"0":"4320","vim_version":"7.0","1":"7.0","script_version":"2.10","2":"2.10","version_comment":"- ENH: Add ,n and ,N variants of ,* that reuse the last search pattern, and therefore also allow offsets outside of the match itself. *** You need to update to ingo-library (vimscript #4433) version 1.040! ***","3":"- ENH: Add ,n and ,N variants of ,* that reuse the last search pattern, and therefore also allow offsets outside of the match itself. *** You need to update to ingo-library (vimscript #4433) version 1.040! ***","package":"SearchHighlighting-2.10.vmb.gz","4":"SearchHighlighting-2.10.vmb.gz","src_id":"26805","5":"26805","creation_date":"1572549624","6":"1572549624"},{"0":"4320","vim_version":"7.0","1":"7.0","script_version":"2.01","2":"2.01","version_comment":"- ENH: Add ...-iw \/ ...-nw variants of exactline, line, selection that match ignoring whitespace differences \/ and no whitespace.\r\n- Trigger LastSearchPatternChanged User event to notify other plugins (e.g. my SearchRepeat.vim plugin (vimscript #4949)) of the change of register \/.\r\n- :SearchAutoHighlighting commands inform the SearchRepeat.vim plugin that the change in register \/ is automatic, not initiated by the user, so that the current custom search is kept active instead of reverting back to standard search.\r\n- ENH: Add from-cursor and to-cursor (and -iw, -nw variants) for :SearchAutoHighlighting. *** You need to update to ingo-library (vimscript #4433) version 1.036! ***","3":"- ENH: Add ...-iw \/ ...-nw variants of exactline, line, selection that match ignoring whitespace differences \/ and no whitespace.\r\n- Trigger LastSearchPatternChanged User event to notify other plugins (e.g. my SearchRepeat.vim plugin (vimscript #4949)) of the change of register \/.\r\n- :SearchAutoHighlighting commands inform the SearchRepeat.vim plugin that the change in register \/ is automatic, not initiated by the user, so that the current custom search is kept active instead of reverting back to standard search.\r\n- ENH: Add from-cursor and to-cursor (and -iw, -nw variants) for :SearchAutoHighlighting. *** You need to update to ingo-library (vimscript #4433) version 1.036! ***","package":"SearchHighlighting-2.01.vmb.gz","4":"SearchHighlighting-2.01.vmb.gz","src_id":"26606","5":"26606","creation_date":"1562872212","6":"1562872212"},{"0":"4320","vim_version":"7.0","1":"7.0","script_version":"2.00","2":"2.00","version_comment":"- ENH: Allow tab page- and window-local Auto Search Highlighting via new :SearchAutoHighlightingTabLocal, :SearchAutoHighlightingWinLocal commands.\r\n- ENH: Support v:hlsearch (available since Vim 7.4.079) via an alternative set of functions that don't use the s:isSearchOn internal flag.\r\n- BUG: Handle \"No string under cursor\" for ,* mapping correctly by returing the :echoerr call, not 0.\r\n- BUG: Off-by-one in ,* on second-to-last character.\r\n- ENH: <A-8>, g<A-8> mappings star-like search for [whole] cWORD (instead of cword).\r\n- Generalize the ,* mapping to support all four variants of the * mapping (whole \/ current, cword, cWORD), too.\r\n- Only define default ,* etc. mappings when the map leader isn't set to \",\", which would make it conflict with the <Leader>* Auto-Search mapping. Thanks to Ilya Tumaykin for raising this issue.\r\n- Don't show strange whitespace matches on \":SearchAutoHighlighting wWORD\" caused by empty \\%(^\\|\\s\\)\\zs\\ze\\%(\\s\\|$\\) pattern. Set completely empty pattern then.\r\n- Re-enable search highlighting when switching to a window that has Auto Search. Clear search highlighting when switching from a window that has Auto Search to one that hasn't, and search highlighting was previously turned off.\r\n- Save and restore the Auto Search pattern from a selection source when updating. *** You need to update to ingo-library (vimscript #4433) version 1.023! ***","3":"- ENH: Allow tab page- and window-local Auto Search Highlighting via new :SearchAutoHighlightingTabLocal, :SearchAutoHighlightingWinLocal commands.\r\n- ENH: Support v:hlsearch (available since Vim 7.4.079) via an alternative set of functions that don't use the s:isSearchOn internal flag.\r\n- BUG: Handle \"No string under cursor\" for ,* mapping correctly by returing the :echoerr call, not 0.\r\n- BUG: Off-by-one in ,* on second-to-last character.\r\n- ENH: <A-8>, g<A-8> mappings star-like search for [whole] cWORD (instead of cword).\r\n- Generalize the ,* mapping to support all four variants of the * mapping (whole \/ current, cword, cWORD), too.\r\n- Only define default ,* etc. mappings when the map leader isn't set to \",\", which would make it conflict with the <Leader>* Auto-Search mapping. Thanks to Ilya Tumaykin for raising this issue.\r\n- Don't show strange whitespace matches on \":SearchAutoHighlighting wWORD\" caused by empty \\%(^\\|\\s\\)\\zs\\ze\\%(\\s\\|$\\) pattern. Set completely empty pattern then.\r\n- Re-enable search highlighting when switching to a window that has Auto Search. Clear search highlighting when switching from a window that has Auto Search to one that hasn't, and search highlighting was previously turned off.\r\n- Save and restore the Auto Search pattern from a selection source when updating. *** You need to update to ingo-library (vimscript #4433) version 1.023! ***","package":"SearchHighlighting-2.00.vmb.gz","4":"SearchHighlighting-2.00.vmb.gz","src_id":"24928","5":"24928","creation_date":"1485527382","6":"1485527382"},{"0":"4320","vim_version":"7.0","1":"7.0","script_version":"1.22","2":"1.22","version_comment":"- Add <Leader>* visual mode mapping that turns on auto-search only for selected text (without affecting the original {what} default).\r\n- Add \"selection\" value for {what} in :SearchHighlightingAutoSearch that only highlights selected text.","3":"- Add <Leader>* visual mode mapping that turns on auto-search only for selected text (without affecting the original {what} default).\r\n- Add \"selection\" value for {what} in :SearchHighlightingAutoSearch that only highlights selected text.","package":"SearchHighlighting-1.22.vmb.gz","4":"SearchHighlighting-1.22.vmb.gz","src_id":"22058","5":"22058","creation_date":"1403203964","6":"1403203964"},{"0":"4320","vim_version":"7.0","1":"7.0","script_version":"1.21","2":"1.21","version_comment":"- Also abort on :SearchAutoHighlighting error.\r\n- Remove duplicate \/.*.*\/ in pattern for visual blockwise search.","3":"- Also abort on :SearchAutoHighlighting error.\r\n- Remove duplicate \/.*.*\/ in pattern for visual blockwise search.","package":"SearchHighlighting-1.21.vmb.gz","4":"SearchHighlighting-1.21.vmb.gz","src_id":"21929","5":"21929","creation_date":"1400848231","6":"1400848231"},{"0":"4320","vim_version":"7.0","1":"7.0","script_version":"1.20","2":"1.20","version_comment":"- ENH: Add ,* search that keeps the current position within the current word when jumping to subsequent matches.\r\n- Correctly emulate * behavior on whitespace-only lines where there's no cword: Issue \"E348: No string under cursor\".\r\n- Add dependency to ingo-library (vimscript #4433). *** You need to separately install ingo-library (vimscript #4433) version 1.015 (or higher)! ***\r\n- For a blockwise visual selection, don't just match the block's lines on their own, but also when contained in other text.\r\n- BUG: For {Visual}*, a [count] isn't considered.","3":"- ENH: Add ,* search that keeps the current position within the current word when jumping to subsequent matches.\r\n- Correctly emulate * behavior on whitespace-only lines where there's no cword: Issue \"E348: No string under cursor\".\r\n- Add dependency to ingo-library (vimscript #4433). *** You need to separately install ingo-library (vimscript #4433) version 1.015 (or higher)! ***\r\n- For a blockwise visual selection, don't just match the block's lines on their own, but also when contained in other text.\r\n- BUG: For {Visual}*, a [count] isn't considered.","package":"SearchHighlighting-1.20.vmb.gz","4":"SearchHighlighting-1.20.vmb.gz","src_id":"21125","5":"21125","creation_date":"1385714784","6":"1385714784"},{"0":"4320","vim_version":"7.0","1":"7.0","script_version":"1.02","2":"1.02","version_comment":"- For a blockwise visual selection, don't just match the block's lines on their own, but also when contained in other text.\r\n- BUG: For {Visual}*, a [count] isn't considered.","3":"- For a blockwise visual selection, don't just match the block's lines on their own, but also when contained in other text.\r\n- BUG: For {Visual}*, a [count] isn't considered.","package":"SearchHighlighting-1.02.vmb.gz","4":"SearchHighlighting-1.02.vmb.gz","src_id":"19405","5":"19405","creation_date":"1358754330","6":"1358754330"},{"0":"4320","vim_version":"7.0","1":"7.0","script_version":"1.01","2":"1.01","version_comment":"FIX: Prevent repeated error message when an invalid {what} was given to :SearchAutoHighlighting.","3":"FIX: Prevent repeated error message when an invalid {what} was given to :SearchAutoHighlighting.","package":"SearchHighlighting-1.01.vmb.gz","4":"SearchHighlighting-1.01.vmb.gz","src_id":"19092","5":"19092","creation_date":"1354552456","6":"1354552456"},{"0":"4320","vim_version":"7.0","1":"7.0","script_version":"1.00","2":"1.00","version_comment":"Initial upload","3":"Initial upload","package":"SearchHighlighting-1.00.vmb.gz","4":"SearchHighlighting-1.00.vmb.gz","src_id":"19020","5":"19020","creation_date":"1353660135","6":"1353660135"}]},"4319":{"script_id":"4319","0":"4319","script_name":"ColorSchemePicker","1":"ColorSchemePicker","script_type":"color scheme","2":"color scheme","summary":"Pick the VIM colorscheme that you are destined to be with.","3":"Pick the VIM colorscheme that you are destined to be with.","description":"Power VIM Users like us have already wasted tons of time to choose\r\nour favorite colorschemes, and may still not be satisfied with the\r\ncurrent colorschemes. So I wrote this plugin to help us out, to\r\nmeet the perfect colorsheme that we are DESTINED to be with.\r\njust like your lovely girlfriends\/wifes:)\r\nWritten by sunus Lee\r\nUsage:\r\nWhen you use vim open a file, I will randomly pick up a colorscheme for you.\r\n    ALL The Commands below are CaseSensitive\r\n    if you LOVE this colorscheme,\r\n    Enter( In Normal Mode )\r\n    :Love\r\n    then I will never change your colorscheme again.\r\n    if you HATE this colorscheme and don't want to see her again,\r\n    Enter( In Normal Mode )\r\n    :Hate\r\n    then I will never pick this colorscheme for you and then\r\n    randomly pick a new coloscheme.\r\n    if you somehow regret what you did and want to get the hated colorscheme back,\r\n    Enter(In Normal Mode)\r\n    :Back\r\n    then all you hated colorschem will back to select pool, and you might see\r\n    her again:)\r\n    Enter(In Normal Mode)\r\n    :CS\r\n    to see current colorscheme\r\nTips\r\nUse this plugin with a large colorsheme pool\r\nwill increase the possibility of meeting the right ColorScheme for you.\r\nSo, I recommand you also use the ColorScheme Pack at:\r\nvimscript #625\r\nColo(u)r Sampler Pack : Oct 2012 Update\r\nBig Thanks to Robert Melton for his awesome work!\r\n\r\n\r\nAny Feedback and Suggestions is welcomed\r\nmail me: sunus.the.dev[at]gmail.com\r\ngithub: https:\/\/github.com\/sunuslee\/vim-plugin-random-colorscheme-picker\r\n","4":"Power VIM Users like us have already wasted tons of time to choose\r\nour favorite colorschemes, and may still not be satisfied with the\r\ncurrent colorschemes. So I wrote this plugin to help us out, to\r\nmeet the perfect colorsheme that we are DESTINED to be with.\r\njust like your lovely girlfriends\/wifes:)\r\nWritten by sunus Lee\r\nUsage:\r\nWhen you use vim open a file, I will randomly pick up a colorscheme for you.\r\n    ALL The Commands below are CaseSensitive\r\n    if you LOVE this colorscheme,\r\n    Enter( In Normal Mode )\r\n    :Love\r\n    then I will never change your colorscheme again.\r\n    if you HATE this colorscheme and don't want to see her again,\r\n    Enter( In Normal Mode )\r\n    :Hate\r\n    then I will never pick this colorscheme for you and then\r\n    randomly pick a new coloscheme.\r\n    if you somehow regret what you did and want to get the hated colorscheme back,\r\n    Enter(In Normal Mode)\r\n    :Back\r\n    then all you hated colorschem will back to select pool, and you might see\r\n    her again:)\r\n    Enter(In Normal Mode)\r\n    :CS\r\n    to see current colorscheme\r\nTips\r\nUse this plugin with a large colorsheme pool\r\nwill increase the possibility of meeting the right ColorScheme for you.\r\nSo, I recommand you also use the ColorScheme Pack at:\r\nvimscript #625\r\nColo(u)r Sampler Pack : Oct 2012 Update\r\nBig Thanks to Robert Melton for his awesome work!\r\n\r\n\r\nAny Feedback and Suggestions is welcomed\r\nmail me: sunus.the.dev[at]gmail.com\r\ngithub: https:\/\/github.com\/sunuslee\/vim-plugin-random-colorscheme-picker\r\n","install_details":"Just copy randomColorPicker.vim to your VIM runtime plugin path:\r\n\r\nLinux:\r\n\r\nYou may need to create ~\/.vim\/plugin directory if it doesn't exist:\r\n\r\nmkdir -p ~\/.vim\/plugin\r\n\r\nthen:\r\n\r\ncp randomColorPicker.vim ~\/.vim\/plugin\r\n\r\nWindows:\r\n\r\n    1. create a directory at:\r\n\r\n    C:\\Users\\YourUsername\\vimfiles\\plugin\r\n\r\n    or enter directory:\r\n\r\n    C:\\Program Files\\vim\\vim73\\plugin\r\n\r\n    vim73 might be vim72 or whatever.. as long as it's where ur vim is installed, it's vaild.\r\n\r\n    2. copy randomColorPicker.vim to that directory.\r\n","5":"Just copy randomColorPicker.vim to your VIM runtime plugin path:\r\n\r\nLinux:\r\n\r\nYou may need to create ~\/.vim\/plugin directory if it doesn't exist:\r\n\r\nmkdir -p ~\/.vim\/plugin\r\n\r\nthen:\r\n\r\ncp randomColorPicker.vim ~\/.vim\/plugin\r\n\r\nWindows:\r\n\r\n    1. create a directory at:\r\n\r\n    C:\\Users\\YourUsername\\vimfiles\\plugin\r\n\r\n    or enter directory:\r\n\r\n    C:\\Program Files\\vim\\vim73\\plugin\r\n\r\n    vim73 might be vim72 or whatever.. as long as it's where ur vim is installed, it's vaild.\r\n\r\n    2. copy randomColorPicker.vim to that directory.\r\n","first_name":"sunus","6":"sunus","last_name":"lee","7":"lee","releases":[{"0":"4319","vim_version":"7.0","1":"7.0","script_version":"0.415","2":"0.415","version_comment":"fix a bug. you can not hate the one you just love.\r\nbut i don't think it's a good idea to do so:(","3":"fix a bug. you can not hate the one you just love.\r\nbut i don't think it's a good idea to do so:(","package":"randomColorPicker.tar","4":"randomColorPicker.tar","src_id":"19351","5":"19351","creation_date":"1357913306","6":"1357913306"},{"0":"4319","vim_version":"7.0","1":"7.0","script_version":"0.326","2":"0.326","version_comment":"tiny bug fix.","3":"tiny bug fix.","package":"randomColorPicker.tar","4":"randomColorPicker.tar","src_id":"19208","5":"19208","creation_date":"1355897739","6":"1355897739"},{"0":"4319","vim_version":"7.0","1":"7.0","script_version":"0.220","2":"0.220","version_comment":"add Windows Support! yay!","3":"add Windows Support! yay!","package":"randomColorPicker.tar","4":"randomColorPicker.tar","src_id":"19170","5":"19170","creation_date":"1355294523","6":"1355294523"},{"0":"4319","vim_version":"7.0","1":"7.0","script_version":"0.17","2":"0.17","version_comment":"some bug fixes.","3":"some bug fixes.","package":"randomColorPicker.tar","4":"randomColorPicker.tar","src_id":"19012","5":"19012","creation_date":"1353553719","6":"1353553719"},{"0":"4319","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"randomColorPicker.tar","4":"randomColorPicker.tar","src_id":"19009","5":"19009","creation_date":"1353516133","6":"1353516133"}]},"4318":{"script_id":"4318","0":"4318","script_name":"tranquil.vim","1":"tranquil.vim","script_type":"syntax","2":"syntax","summary":"syntax highlighting for tranquil","3":"syntax highlighting for tranquil","description":"Syntax highlighting for tranquil (https:\/\/github.com\/fjolnir\/tranquil)","4":"Syntax highlighting for tranquil (https:\/\/github.com\/fjolnir\/tranquil)","install_details":"Either copy the archive contents inside your .vim dir, or use a plugin manager (vundle, pathogen, etc) and install that way.","5":"Either copy the archive contents inside your .vim dir, or use a plugin manager (vundle, pathogen, etc) and install that way.","first_name":"Fj\u00c3\u00b6lnir","6":"Fj\u00c3\u00b6lnir","last_name":"\u00c3\u0081sgeirsson","7":"\u00c3\u0081sgeirsson","releases":[{"0":"4318","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"tranquil.vim.zip","4":"tranquil.vim.zip","src_id":"19006","5":"19006","creation_date":"1353501608","6":"1353501608"}]},"4317":{"script_id":"4317","0":"4317","script_name":"CommentFrame.vim","1":"CommentFrame.vim","script_type":"utility","2":"utility","summary":"Create comment frames or right-aligned lines.","3":"Create comment frames or right-aligned lines.","description":"This is a simple plugin to generate fancy-looking comments\/section dividers with centered titles and append them at the current cursor position.\r\n\r\nA single comment line with string arg put on right end of line can also be created. \r\n\r\nAll comment styles are customizable for different coding languages, added with keymaps, etc.\r\n\r\nThere is a plugin menu with all the default options in it as well. \r\n\r\n\r\nFor latest developments, any mods, pull requests, etc, see:\r\n          https:\/\/github.com\/cometsong\/CommentFrame.vim","4":"This is a simple plugin to generate fancy-looking comments\/section dividers with centered titles and append them at the current cursor position.\r\n\r\nA single comment line with string arg put on right end of line can also be created. \r\n\r\nAll comment styles are customizable for different coding languages, added with keymaps, etc.\r\n\r\nThere is a plugin menu with all the default options in it as well. \r\n\r\n\r\nFor latest developments, any mods, pull requests, etc, see:\r\n          https:\/\/github.com\/cometsong\/CommentFrame.vim","install_details":"Either copy the file inside the plugin dir to your own plugin dir, or use a plugin manager (e.g. pathogen, vim-addon-manager, etc) and install that way.  (See instructions for your own plugin manager for more info.)","5":"Either copy the file inside the plugin dir to your own plugin dir, or use a plugin manager (e.g. pathogen, vim-addon-manager, etc) and install that way.  (See instructions for your own plugin manager for more info.)","first_name":"Benjamin","6":"Benjamin","last_name":"L","7":"L","releases":[{"0":"4317","vim_version":"7.0","1":"7.0","script_version":"1.05","2":"1.05","version_comment":"Added plugin options to skip default key mappings and to init the default frame and line width of all pre-existing comment functions.","3":"Added plugin options to skip default key mappings and to init the default frame and line width of all pre-existing comment functions.","package":"CommentFrame.vim.tar.gz","4":"CommentFrame.vim.tar.gz","src_id":"26987","5":"26987","creation_date":"1581639331","6":"1581639331"},{"0":"4317","vim_version":"7.0","1":"7.0","script_version":"1.02","2":"1.02","version_comment":"Correct calls to s:MapKeys function.","3":"Correct calls to s:MapKeys function.","package":"CommentFrame.tar.gz","4":"CommentFrame.tar.gz","src_id":"19003","5":"19003","creation_date":"1353486978","6":"1353486978"},{"0":"4317","vim_version":"7.0","1":"7.0","script_version":"1.01","2":"1.01","version_comment":"Initial upload","3":"Initial upload","package":"CommentFrame.tar.gz","4":"CommentFrame.tar.gz","src_id":"18997","5":"18997","creation_date":"1353330604","6":"1353330604"}]},"4316":{"script_id":"4316","0":"4316","script_name":"KingTop","1":"KingTop","script_type":"color scheme","2":"color scheme","summary":"A dark and peaceful color scheme for long night coding","3":"A dark and peaceful color scheme for long night coding","description":"A dark and peaceful color scheme for long night coding.\r\n\r\nScreen shots : http:\/\/jpr75.deviantart.com\/#\/d5leoad\r\n\r\nBased on Inkpot color scheme (http:\/\/www.vim.org\/scripts\/script.php?script_id=1143).","4":"A dark and peaceful color scheme for long night coding.\r\n\r\nScreen shots : http:\/\/jpr75.deviantart.com\/#\/d5leoad\r\n\r\nBased on Inkpot color scheme (http:\/\/www.vim.org\/scripts\/script.php?script_id=1143).","install_details":"Copy the file to your .vim\/colors folder.","5":"Copy the file to your .vim\/colors folder.","first_name":"JP","6":"JP","last_name":"Ricaud","7":"Ricaud","releases":[{"0":"4316","vim_version":"7.0","1":"7.0","script_version":"1.0.1","2":"1.0.1","version_comment":"Better PHP rendering.\r\nSome tweaks and improvements.","3":"Better PHP rendering.\r\nSome tweaks and improvements.","package":"kingtop.vim","4":"kingtop.vim","src_id":"19362","5":"19362","creation_date":"1358086792","6":"1358086792"},{"0":"4316","vim_version":"7.0","1":"7.0","script_version":"1.0.0","2":"1.0.0","version_comment":"Initial upload","3":"Initial upload","package":"kingtop.vim","4":"kingtop.vim","src_id":"18991","5":"18991","creation_date":"1353256452","6":"1353256452"}]},"4315":{"script_id":"4315","0":"4315","script_name":"webBrowser","1":"webBrowser","script_type":"utility","2":"utility","summary":"Use vim as a web browser","3":"Use vim as a web browser","description":"See latest version on github: https:\/\/github.com\/viaa\/VimPlugins\r\n\r\nName: webBrowser.vim\r\nVersion: 1.6\r\nDescription: Uses the lynx text browser to browse websites and local files and return the rendered web pages inside vim. The links in the web pages may be \"clicked\" to follow them, so it turns vim into a simple web text based web browser. This plugin is based on the \"browser.vim\" plugin.\r\nAuthor: Alexandre Viau (alexandreviau@gmail.com)\r\nWebsite: The latest version is found on \"vim.org\"\r\n\r\nInstallation:  \r\nCopy the plugin to the vim plugin directory.\r\nIn the lynx.cfg file, set the following parameters: \r\nACCEPT_ALL_COOKIES:TRUE\r\nMAKE_LINKS_FOR_ALL_IMAGES:TRUE\r\nChange the following paths to your lynx files:\r\nlet s:lynxPath = 'c:\\lynx'\r\nlet s:lynxExe = s:lynxPath . 'lynx.exe'\r\nlet s:lynxCfg = '-cfg=' . s:lynxPath . 'lynx.cfg'\r\nlet s:lynxLss = '-lss=' . s:lynxPath . 'lynx.lss'\r\nlet s:lynxCmd = s:lynxExe . ' ' . s:lynxCfg . ' ' . s:lynxLss\r\nlet s:lynxDumpPath = 'c:\\lynx\\dump'\r\nlet s:lynxToolsPath = 'c:\\lynx\\tools'\r\n\r\nUsage: \r\n<leader>wb :WebBrowser (Open a new web browser tab with the address specified)\r\n<leader>wc :exe 'WebBrowser \"' . @* . '\"'<cr> (Open a new web browser tab with the address in the clipboard)\r\n<leader>wg :exe 'WebBrowser www.google.com\/search?q=\"' . input(\"Google \") . '\"'<cr> (Do a google search using the specified search keywords and open the results in a new tab)\r\n<leader>wp :exe 'WebBrowser www.wikipedia.com\/wiki\/\"' . input(\"Wikipedia \") . '\"'<cr> (Do a wikipedia search using the specified search keywords and open the results in a new tab)\r\n<leader>wd :WebDump (Downloads the specified webpage without opening it in vim)\r\n<space>l (Open link)\r\n<space>h (Previous page (\"back button\"))\r\n<space>j (Highlight links and go to next link)\r\n<space>k (Highlight links and go to previous link)\r\n\r\nTodo: \r\n- Redo the code that gets the link number and search for it at the end of the file (no need to move cursor) and to do it in a mapping, it may be done in a function\r\n- I added basicXmlParser in the plugin, add a webBrowser.xml file and in it, have 2 keys: history and favorites, which will be string of utl links\r\n- Add links bar like vimExplorer (favorites & history) with links not from utl but with brackets [http:\/\/yahoo.com] thus no need for utl\r\n- Use image_links and accept_all_cookies options in the command run from the plugin instead of having to modify the .cfg file\r\n\r\nHistory \r\n1.1 \r\n- Changed the file format to unix\r\n1.2 \r\n- Changed the mappings\r\n1.3 \r\n- Now the lynx command and others are ran using a call to the system() function so that the dos prompt window is not displayed on the screen\r\n- Added suggested mappings in comments (<insert>, <delete>, etc)\r\n- Added folds\r\n1.4 \r\n- Changed mappings \\wb etc to <leader>wb because it was causing my \"w\" key in normal mode to wait for another key\r\n1.5 \r\n- Added the webdump command and function to download in batch\r\n1.6 \r\n- Added documentation and usage\r\n","4":"See latest version on github: https:\/\/github.com\/viaa\/VimPlugins\r\n\r\nName: webBrowser.vim\r\nVersion: 1.6\r\nDescription: Uses the lynx text browser to browse websites and local files and return the rendered web pages inside vim. The links in the web pages may be \"clicked\" to follow them, so it turns vim into a simple web text based web browser. This plugin is based on the \"browser.vim\" plugin.\r\nAuthor: Alexandre Viau (alexandreviau@gmail.com)\r\nWebsite: The latest version is found on \"vim.org\"\r\n\r\nInstallation:  \r\nCopy the plugin to the vim plugin directory.\r\nIn the lynx.cfg file, set the following parameters: \r\nACCEPT_ALL_COOKIES:TRUE\r\nMAKE_LINKS_FOR_ALL_IMAGES:TRUE\r\nChange the following paths to your lynx files:\r\nlet s:lynxPath = 'c:\\lynx'\r\nlet s:lynxExe = s:lynxPath . 'lynx.exe'\r\nlet s:lynxCfg = '-cfg=' . s:lynxPath . 'lynx.cfg'\r\nlet s:lynxLss = '-lss=' . s:lynxPath . 'lynx.lss'\r\nlet s:lynxCmd = s:lynxExe . ' ' . s:lynxCfg . ' ' . s:lynxLss\r\nlet s:lynxDumpPath = 'c:\\lynx\\dump'\r\nlet s:lynxToolsPath = 'c:\\lynx\\tools'\r\n\r\nUsage: \r\n<leader>wb :WebBrowser (Open a new web browser tab with the address specified)\r\n<leader>wc :exe 'WebBrowser \"' . @* . '\"'<cr> (Open a new web browser tab with the address in the clipboard)\r\n<leader>wg :exe 'WebBrowser www.google.com\/search?q=\"' . input(\"Google \") . '\"'<cr> (Do a google search using the specified search keywords and open the results in a new tab)\r\n<leader>wp :exe 'WebBrowser www.wikipedia.com\/wiki\/\"' . input(\"Wikipedia \") . '\"'<cr> (Do a wikipedia search using the specified search keywords and open the results in a new tab)\r\n<leader>wd :WebDump (Downloads the specified webpage without opening it in vim)\r\n<space>l (Open link)\r\n<space>h (Previous page (\"back button\"))\r\n<space>j (Highlight links and go to next link)\r\n<space>k (Highlight links and go to previous link)\r\n\r\nTodo: \r\n- Redo the code that gets the link number and search for it at the end of the file (no need to move cursor) and to do it in a mapping, it may be done in a function\r\n- I added basicXmlParser in the plugin, add a webBrowser.xml file and in it, have 2 keys: history and favorites, which will be string of utl links\r\n- Add links bar like vimExplorer (favorites & history) with links not from utl but with brackets [http:\/\/yahoo.com] thus no need for utl\r\n- Use image_links and accept_all_cookies options in the command run from the plugin instead of having to modify the .cfg file\r\n\r\nHistory \r\n1.1 \r\n- Changed the file format to unix\r\n1.2 \r\n- Changed the mappings\r\n1.3 \r\n- Now the lynx command and others are ran using a call to the system() function so that the dos prompt window is not displayed on the screen\r\n- Added suggested mappings in comments (<insert>, <delete>, etc)\r\n- Added folds\r\n1.4 \r\n- Changed mappings \\wb etc to <leader>wb because it was causing my \"w\" key in normal mode to wait for another key\r\n1.5 \r\n- Added the webdump command and function to download in batch\r\n1.6 \r\n- Added documentation and usage\r\n","install_details":"Copy the file in the plugin directory.\r\n\r\nChange the paths to your lynx files:\r\n\r\nlet s:lynxPath = 'c:\\lynx\\'\r\nlet s:lynxExe = s:lynxPath . 'lynx.exe'\r\nlet s:lynxCfg = '-cfg=' . s:lynxPath . 'lynx.cfg'\r\nlet s:lynxLss = '-lss=' . s:lynxPath . 'lynx.lss'\r\nlet s:lynxCmd = s:lynxExe . ' ' . s:lynxCfg . ' ' . s:lynxLss\r\n\r\nlet s:lynxDumpPath = 'c:\\lynx\\dump\\'\r\nlet s:lynxToolsPath = 'c:\\lynx\\tools\\'","5":"Copy the file in the plugin directory.\r\n\r\nChange the paths to your lynx files:\r\n\r\nlet s:lynxPath = 'c:\\lynx\\'\r\nlet s:lynxExe = s:lynxPath . 'lynx.exe'\r\nlet s:lynxCfg = '-cfg=' . s:lynxPath . 'lynx.cfg'\r\nlet s:lynxLss = '-lss=' . s:lynxPath . 'lynx.lss'\r\nlet s:lynxCmd = s:lynxExe . ' ' . s:lynxCfg . ' ' . s:lynxLss\r\n\r\nlet s:lynxDumpPath = 'c:\\lynx\\dump\\'\r\nlet s:lynxToolsPath = 'c:\\lynx\\tools\\'","first_name":"Alexandre","6":"Alexandre","last_name":"Viau","7":"Viau","releases":[{"0":"4315","vim_version":"7.0","1":"7.0","script_version":"1.6","2":"1.6","version_comment":"- Added documentation and usage\r\n","3":"- Added documentation and usage\r\n","package":"webBrowser.vim","4":"webBrowser.vim","src_id":"20287","5":"20287","creation_date":"1370377598","6":"1370377598"},{"0":"4315","vim_version":"7.0","1":"7.0","script_version":"1.5","2":"1.5","version_comment":"Added the webdump command and function to download in batch\r\n","3":"Added the webdump command and function to download in batch\r\n","package":"webBrowser.vim","4":"webBrowser.vim","src_id":"20286","5":"20286","creation_date":"1370375681","6":"1370375681"},{"0":"4315","vim_version":"7.0","1":"7.0","script_version":"1.1","2":"1.1","version_comment":"Changed the file format to unix","3":"Changed the file format to unix","package":"webBrowser.vim","4":"webBrowser.vim","src_id":"18996","5":"18996","creation_date":"1353328793","6":"1353328793"},{"0":"4315","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"webBrowser.vim","4":"webBrowser.vim","src_id":"18987","5":"18987","creation_date":"1353155281","6":"1353155281"}]},"4314":{"script_id":"4314","0":"4314","script_name":"simpleSnip","1":"simpleSnip","script_type":"utility","2":"utility","summary":"Simple snippets utility.","3":"Simple snippets utility.","description":"See latest version on github: https:\/\/github.com\/viaa\/VimPlugins\r\n\r\nDocumentation \r\nName: simpleSnip.vim\r\nVersion: 1.5\r\nAuthors: Alexandre Viau with thanks to xaizek and Stephan Bittner for helping.\r\n\r\nDescription \r\n\r\nThis plugin allow to simply create and use snippets using vim abbreviations.\r\nIt allow to use placeholders in snippets and replace multiple placeholders\r\nat once. Snippets may be used with any programming languages or for any kind of writing, not only programming.\r\n\r\nInstallation \r\n\r\nUnpack the archive to your $VIM directory.  It should contain the plugin file\r\nnamed simpleSnip.vim and several example snippet files:\r\n - snipcs.vim (for C#)\r\n - sniphtml.vim (for HTML)\r\n - snipsql.vim (for SQL)\r\nThen source unpacked *.vim files (open the file and do :so%) or restart vim.\r\n\r\nUsage \r\n\r\n<leader>rs (reload the snippets used for the current file. For example if current file is a .cs (csharp file) <leader>rs will reload the snippets used for this file. It will reload the file and the snippets file which is a filetype pluging will be reloaded at the same time.)\r\n<leader>nc (to add a new snippet to a snippet file using the text in the clipboard (uses vim's auto-indenting)\r\n<leader>NC (to add a new snippet to a snippet file using the text in the clipboard (uses dosen't use vim's auto-indenting)\r\n<leader>ns (to add a new empty snippet to a snippet (uses vim's auto-indenting)\r\n<leader>NS (to add a new empty snippet to a snippet file (uses dosen't use vim's auto-indenting)\r\n<leader>gs (to temporarily load and use snippets from another filetype. Do <leader>rs to return to normal snippets)\r\n\r\nDo <leader>rs (\\rs by default) (rs for Reload Snippets) mapping to reload the snippets after \r\nthe snippets are modified. So for example if you are editing a .cs file and then you go to modify your snippets file \r\n(which is a filetype plugin) then save the snippets file and then returning to the .cs file in\r\nedition, reload the file to reload the snippets. To reload the snippets do <leader>rs (\\rs) \r\nor save the file and reload it using e %\r\n\r\nSee the snippets in the snippets file:\r\n\r\nThis usage example uses the CL snippet in the snipcs.vim: \r\n\r\nTo add a new class in c#, go in insert mode (i) and type CL then press the escape key. The snippet will be inserted.\r\nPress 'n' or 'N' to move to from one placeholder to another in the snippet (note: aa is used as a prefix to search, you may change it if you don't like).\r\nThen do the vim command 'cw' (change word) to replace the current placeholder by the text you type, press the escape key.\r\nIf the placeholder exists many times in the snippets, all occurences will be replaced after pressing the escape key.\r\n\r\nThis is an example of a snippet. Notice that it is simple a vim abbreviation\r\ncontaining placeholders prefixed by 'aa' and at then end the function S() is\r\ncalled. The number '2' in parameter to the S(2) function here means is the\r\nnumber of placeholders in the snippet, here the placeholders are 'exe'\r\nand 'ech'. You specify it so that the search will go back and the cursor \r\nwill be on the first placeholder when the snippet is inserted. Check the\r\nsnippets files for more example.\r\n\r\nabb MA \r\n\\class exe<cr>\r\n\\{<cr>\r\n\\static void Main()<cr>\r\n\\{<cr>\r\n\\ech<cr>\r\n\\}<cr>\r\n\\}\r\n\\<esc>:cal S(2)<cr>\r\n\r\nBe sure not to have blanks (spaces) after the <cr> in the snippets or the\r\nlines may not be automatically indented. And be sure there is a space\r\nafter the snippet name (here MA ).\r\n\r\nIf you prefer to indent the lines of code yourself in the snippet, add the \"\\<c-o>:set paste<cr>\" line as the second line of the snippets and indent your code.\r\nUse tabs or space to indent your code. Here's an example.\r\n      \r\niabb <buffer> CL \r\n\\<c-o>:set paste<cr>\r\n\\class from<cr>\r\n\\{<cr>\r\n\\   aaMemberType aaMemberName;\r\n\\   public from()<cr>\r\n\\   {<cr>\r\n\\       ech<cr>\r\n\\   }<cr>\r\n\\}\r\n\\<esc>:cal S(3)<cr>\r\n\r\nIt may be cases where vim will not indent like expected, like in the\r\npreceding snippet CL, then in these cases you should indent the code\r\nyourself using the \"\\<c-o>:set paste<cr>\" line.\r\n\r\nTo add a new snippet copy to clipboard the text you want to put to snippet, and then do <leader>nc (n for new, c for clipboard) \r\n(<leader> is \"\\\" by default so \\nc) then the text you copied to clipboard will be pasted to the file as a snippet compatible with \r\nsimpleSnip ready to be added or pasted directly to a snippets file.\r\nIf you want vim to automatically indent your snippet, delete the \"\\<c-o>:set paste<cr>\" line that is pasted with the snippet and\r\nbe sure then that there are no spaces or tabs in your snippet text.\r\n\r\nIf you want to simply add a new snippet you may use the <leader>ns (n for new, s for snippet), this will\r\nadd a new empty snippet in a snippet file.\r\n\r\nAbout automatic comments in snippets\r\nI noticed that the filetype plugins like cs.vim or vim.vim have parameters\r\nto automatically comment the following lines when pressing <enter> or o in\r\nnormal mode. Because of this, if you put comments in a snippets, all the\r\nlines after the commented line will also be automatically commented. You may\r\ndisable it by going to the filetype plugin of the file type you don't want\r\nthese automatic comments, for example if you edit a c# file, go to\r\nVIM$\/ftplugin\/cs.vim find the line:\r\nsetlocal fo-=t fo+=croql\r\nand comment it out.\r\n\" setlocal fo-=t fo+=croql\r\nFor other filetypes, the syntax may differ but it uses the setlocal command\r\nso find it or search for the word comment which may appear in the comments\r\nof that command. I think for vim.vim the command to comment out is also:\r\n\" setlocal fo-=t fo+=croql\r\n\r\nAbout snippets organization\r\nIf you like to organize the snippets with indenting like I did in the \r\nC# snippet file, you'll have to comment out a line in the \r\nVIM$\/ftplugin\/vim.vim file, if not the snippets will not keep their\r\nindentation but will be automatically align to the left. Comment\r\nout this line: \" setlocal com=sO:\\\"\\ -,mO:\\\"\\ \\ ,eO:\\\"\\\",:\\\"\r\n\r\nTo use snippets from other filetypes\r\nThe <leader>gs (get snippets) mapping allows to temporarily load snippets from another filetype to use them, then to come back to \r\nthe current file's filetype. Useful for example if one is using a c# file (with a cs filetype) then one need to insert a sql query but the \r\nsql snippets are not defined in the cs_simplesnip.vim (cs filetype) but they are defined in the sql_simplesnip.vim (sql filetype) file. \r\nDoing <leader>gs (\\gs) will change the filetype (temporarily) of the current file making vim think it is a sql file, so the sql snippets \r\nwill be loaded, then the user would insert the snippets he needs, then would do <leader>rs to reload the snippets for the current file type, \r\nso in this case the c# snippets would be reloaded. Another example would be to use c# snippets in a aspx file, or javascript snippets in html etc.\r\n\r\nTips \r\n\r\n1. Type :ab to see the available snippets for this file.\r\n\r\n2. If you should include several snippets that contain same placeholder\r\nnames, for example aaCommandName where aaCommandName is used in several\r\nsnippets, insert all the snippets before to change the aaCommandName by the\r\nactual name, then once all the snippets are inserted, replace the\r\naaCommandName and it will be replaced in every snippets at once. So to\r\nchange it only one time.\r\n\r\nBugs \r\n\r\n1. Il y a une erreur dans le replace all de simplesnip... voir et tester et corriger depuis les fold...avant c'etait ok\r\n2. Le probleme avec simplesnip c'est peut-etre a cause d'une espace <space> qui essaie de folder\/defolder..\r\n\r\nHistory \r\n\r\nVersion 1.0\r\n\r\n1. (Xaizek) for the let @\/ = \"aa\" to simulate a search command like \/aa but from code.\r\n2. (Stephan Bittner) for the normal \/aa\r\n to simulate a search command like \/aa but from code.\r\n\r\nVersion 1.1 \r\n\r\n1. (Xaizek) Changed filetype of all files from `dos` to `unix`.  The thing is\r\n   that Vim-scripts with `dos` eol's work on Windows without issues, but\r\n   produce plenty of errors while they are loaded on *nix systems.\r\n   While Vim-scripts with `unix` eol's work on all platforms.\r\n\r\n2. (Xaizek) Modified directory structure to look like this\r\n   ftplugin\r\n       cs_simplesnip.vim\r\n       html_simplesnip.vim\r\n       sql_simplesnip.vim\r\n   plugin\r\n       simpleSnip.vim\r\n\r\n3. (Alexandre) Renamed snippets files to add an underscore in the filenames\r\n   example cs_simplesnip.vim, so they will not conflict with files already\r\n   there, but will still be loaded according to the filetype.\r\n\r\n4. (Xaizek) Put `<buffer>` specifier to all :abb commands in the sample snippets,\r\n   so they are defined locally to each buffer.\r\n\r\n5. (Xaizek) Added `<silent>` specifier to the :imap command in simpleSnip.vim to\r\n   prevent `:call ReplaceAll()` displaying on the statusbar when I leave insert mode.\r\n\r\n6. (Xaizek) Change :abb to :iabb in the snippets files. Otherwise one will be surprised \r\n   with results after typing name of one of snippets while being in the command-line mode.\r\n\r\nVersion 1.2\r\n\r\n1. (Xaizek) Provided the paste\/nopaste solution to be able to\r\n   indent manually the snippets instead to have vim indent them manually.\r\n   In some cases, vim did not indent the lines as expected, so his\r\n   idea provides a way to manually indent the snippets.\r\n\r\nVersion 1.3\r\n\r\n1. Added <leader>rr mapping to reload the snippets. So for example if you\r\n   are editing a .cs file and then go to modify your snippets file (filetype\r\n   plugin) then save the snippets file and then returning to the .cs file in\r\n   edition, reload the file to reload the snippets. To do this do <leader>rs\r\n   (\\rs) (rs for Reload Snippets) or save the file and reload it using e %\r\n\r\nversion 1.4\r\n\r\n1. Modified usage instructions (be sure not to have blanks (spaces) after\r\n   <cr> in the snippets or the automatic indentation may not be like expected.\r\n\r\n2. I added a tips section to the help (comment at the top of the file).\r\n\r\n3. I started another snippet file for vimscript snippets.\r\n\r\n4. Added the NewSnippetFromClipboard() function which allows to paste as a snippet (in the snippet format) to a snippet file, text copied to the * register (clipboard).\r\n   So no need to manually add the snippets keywords or the \"\\\", \"<cr>\" etc. The NewSnippetFromClipboard() function will take care of this only you have to copy to clipboard\r\n   the text you want to put to snippet, and then do <leader>nc (n for new, c for clipboard) (<leader> is \"\\\" by default so \\nc) then the text you copied to \r\n   clipboard will be pasted to the file as a snippet compatible with simpleSnip ready to be added or pasted directly to a snippets file.\r\n\r\n5. Added the NewEmptySnippet() function which uses the NewSnippet() function to add a new snippet to a snippet file.  \r\n\r\n6. Added the NewSnippet() function which is used by NewEmptySnippet() and NewSnippetFromClipboard() functions\r\n\r\n7. Added several snippets for csharp, vimscript, html, javascript, aspx.\r\n\r\n8. Added the S1() function which is like the S() function but a prefix may\r\n   be passed in parameters. To use in case \"aa\" may match actual code in the\r\n   snippet that is not part of placeholders. See the DataAdapter snippet in the csharp snippet file for example.\r\n\r\n9. Modified the regex in the ReplaceAll() function and in this function, I\r\n   added code to go to the next match after a placeholder is modified. Before\r\n   the cursor was staying at the position of the last replacement thus one had\r\n   to do several N to go back.\r\n\r\n10. Added ability to temporarily load the snippets that are normally used for another filetype, for example\r\n    to use the snippets in the sql_simplesnip.vim filetype plugin when editing a c# code file, or to load\r\n    the c# snippets when editing an aspx file, or again, to load the javascript snippets when editing an\r\n    html file. It is easy to load <leader>gs, then to come back to previous snippets <leader>rs.\r\n\r\nVersion 1.5\r\n\r\n1. Added folds\r\n2. Corrected a bug in the ReplaceAll() function, there was a space left over at line 9 which doing an error message.\r\n\r\nVersion 1.6\r\n\r\n1. (Xaizek) When a placeholder to replace ended with the end of line ($) it was not replaced by the replace all function. This is corrected. Replaced let l:to = expand(\"<cword>\") by let l:to = getreg('.')\r\n\r\n","4":"See latest version on github: https:\/\/github.com\/viaa\/VimPlugins\r\n\r\nDocumentation \r\nName: simpleSnip.vim\r\nVersion: 1.5\r\nAuthors: Alexandre Viau with thanks to xaizek and Stephan Bittner for helping.\r\n\r\nDescription \r\n\r\nThis plugin allow to simply create and use snippets using vim abbreviations.\r\nIt allow to use placeholders in snippets and replace multiple placeholders\r\nat once. Snippets may be used with any programming languages or for any kind of writing, not only programming.\r\n\r\nInstallation \r\n\r\nUnpack the archive to your $VIM directory.  It should contain the plugin file\r\nnamed simpleSnip.vim and several example snippet files:\r\n - snipcs.vim (for C#)\r\n - sniphtml.vim (for HTML)\r\n - snipsql.vim (for SQL)\r\nThen source unpacked *.vim files (open the file and do :so%) or restart vim.\r\n\r\nUsage \r\n\r\n<leader>rs (reload the snippets used for the current file. For example if current file is a .cs (csharp file) <leader>rs will reload the snippets used for this file. It will reload the file and the snippets file which is a filetype pluging will be reloaded at the same time.)\r\n<leader>nc (to add a new snippet to a snippet file using the text in the clipboard (uses vim's auto-indenting)\r\n<leader>NC (to add a new snippet to a snippet file using the text in the clipboard (uses dosen't use vim's auto-indenting)\r\n<leader>ns (to add a new empty snippet to a snippet (uses vim's auto-indenting)\r\n<leader>NS (to add a new empty snippet to a snippet file (uses dosen't use vim's auto-indenting)\r\n<leader>gs (to temporarily load and use snippets from another filetype. Do <leader>rs to return to normal snippets)\r\n\r\nDo <leader>rs (\\rs by default) (rs for Reload Snippets) mapping to reload the snippets after \r\nthe snippets are modified. So for example if you are editing a .cs file and then you go to modify your snippets file \r\n(which is a filetype plugin) then save the snippets file and then returning to the .cs file in\r\nedition, reload the file to reload the snippets. To reload the snippets do <leader>rs (\\rs) \r\nor save the file and reload it using e %\r\n\r\nSee the snippets in the snippets file:\r\n\r\nThis usage example uses the CL snippet in the snipcs.vim: \r\n\r\nTo add a new class in c#, go in insert mode (i) and type CL then press the escape key. The snippet will be inserted.\r\nPress 'n' or 'N' to move to from one placeholder to another in the snippet (note: aa is used as a prefix to search, you may change it if you don't like).\r\nThen do the vim command 'cw' (change word) to replace the current placeholder by the text you type, press the escape key.\r\nIf the placeholder exists many times in the snippets, all occurences will be replaced after pressing the escape key.\r\n\r\nThis is an example of a snippet. Notice that it is simple a vim abbreviation\r\ncontaining placeholders prefixed by 'aa' and at then end the function S() is\r\ncalled. The number '2' in parameter to the S(2) function here means is the\r\nnumber of placeholders in the snippet, here the placeholders are 'exe'\r\nand 'ech'. You specify it so that the search will go back and the cursor \r\nwill be on the first placeholder when the snippet is inserted. Check the\r\nsnippets files for more example.\r\n\r\nabb MA \r\n\\class exe<cr>\r\n\\{<cr>\r\n\\static void Main()<cr>\r\n\\{<cr>\r\n\\ech<cr>\r\n\\}<cr>\r\n\\}\r\n\\<esc>:cal S(2)<cr>\r\n\r\nBe sure not to have blanks (spaces) after the <cr> in the snippets or the\r\nlines may not be automatically indented. And be sure there is a space\r\nafter the snippet name (here MA ).\r\n\r\nIf you prefer to indent the lines of code yourself in the snippet, add the \"\\<c-o>:set paste<cr>\" line as the second line of the snippets and indent your code.\r\nUse tabs or space to indent your code. Here's an example.\r\n      \r\niabb <buffer> CL \r\n\\<c-o>:set paste<cr>\r\n\\class from<cr>\r\n\\{<cr>\r\n\\   aaMemberType aaMemberName;\r\n\\   public from()<cr>\r\n\\   {<cr>\r\n\\       ech<cr>\r\n\\   }<cr>\r\n\\}\r\n\\<esc>:cal S(3)<cr>\r\n\r\nIt may be cases where vim will not indent like expected, like in the\r\npreceding snippet CL, then in these cases you should indent the code\r\nyourself using the \"\\<c-o>:set paste<cr>\" line.\r\n\r\nTo add a new snippet copy to clipboard the text you want to put to snippet, and then do <leader>nc (n for new, c for clipboard) \r\n(<leader> is \"\\\" by default so \\nc) then the text you copied to clipboard will be pasted to the file as a snippet compatible with \r\nsimpleSnip ready to be added or pasted directly to a snippets file.\r\nIf you want vim to automatically indent your snippet, delete the \"\\<c-o>:set paste<cr>\" line that is pasted with the snippet and\r\nbe sure then that there are no spaces or tabs in your snippet text.\r\n\r\nIf you want to simply add a new snippet you may use the <leader>ns (n for new, s for snippet), this will\r\nadd a new empty snippet in a snippet file.\r\n\r\nAbout automatic comments in snippets\r\nI noticed that the filetype plugins like cs.vim or vim.vim have parameters\r\nto automatically comment the following lines when pressing <enter> or o in\r\nnormal mode. Because of this, if you put comments in a snippets, all the\r\nlines after the commented line will also be automatically commented. You may\r\ndisable it by going to the filetype plugin of the file type you don't want\r\nthese automatic comments, for example if you edit a c# file, go to\r\nVIM$\/ftplugin\/cs.vim find the line:\r\nsetlocal fo-=t fo+=croql\r\nand comment it out.\r\n\" setlocal fo-=t fo+=croql\r\nFor other filetypes, the syntax may differ but it uses the setlocal command\r\nso find it or search for the word comment which may appear in the comments\r\nof that command. I think for vim.vim the command to comment out is also:\r\n\" setlocal fo-=t fo+=croql\r\n\r\nAbout snippets organization\r\nIf you like to organize the snippets with indenting like I did in the \r\nC# snippet file, you'll have to comment out a line in the \r\nVIM$\/ftplugin\/vim.vim file, if not the snippets will not keep their\r\nindentation but will be automatically align to the left. Comment\r\nout this line: \" setlocal com=sO:\\\"\\ -,mO:\\\"\\ \\ ,eO:\\\"\\\",:\\\"\r\n\r\nTo use snippets from other filetypes\r\nThe <leader>gs (get snippets) mapping allows to temporarily load snippets from another filetype to use them, then to come back to \r\nthe current file's filetype. Useful for example if one is using a c# file (with a cs filetype) then one need to insert a sql query but the \r\nsql snippets are not defined in the cs_simplesnip.vim (cs filetype) but they are defined in the sql_simplesnip.vim (sql filetype) file. \r\nDoing <leader>gs (\\gs) will change the filetype (temporarily) of the current file making vim think it is a sql file, so the sql snippets \r\nwill be loaded, then the user would insert the snippets he needs, then would do <leader>rs to reload the snippets for the current file type, \r\nso in this case the c# snippets would be reloaded. Another example would be to use c# snippets in a aspx file, or javascript snippets in html etc.\r\n\r\nTips \r\n\r\n1. Type :ab to see the available snippets for this file.\r\n\r\n2. If you should include several snippets that contain same placeholder\r\nnames, for example aaCommandName where aaCommandName is used in several\r\nsnippets, insert all the snippets before to change the aaCommandName by the\r\nactual name, then once all the snippets are inserted, replace the\r\naaCommandName and it will be replaced in every snippets at once. So to\r\nchange it only one time.\r\n\r\nBugs \r\n\r\n1. Il y a une erreur dans le replace all de simplesnip... voir et tester et corriger depuis les fold...avant c'etait ok\r\n2. Le probleme avec simplesnip c'est peut-etre a cause d'une espace <space> qui essaie de folder\/defolder..\r\n\r\nHistory \r\n\r\nVersion 1.0\r\n\r\n1. (Xaizek) for the let @\/ = \"aa\" to simulate a search command like \/aa but from code.\r\n2. (Stephan Bittner) for the normal \/aa\r\n to simulate a search command like \/aa but from code.\r\n\r\nVersion 1.1 \r\n\r\n1. (Xaizek) Changed filetype of all files from `dos` to `unix`.  The thing is\r\n   that Vim-scripts with `dos` eol's work on Windows without issues, but\r\n   produce plenty of errors while they are loaded on *nix systems.\r\n   While Vim-scripts with `unix` eol's work on all platforms.\r\n\r\n2. (Xaizek) Modified directory structure to look like this\r\n   ftplugin\r\n       cs_simplesnip.vim\r\n       html_simplesnip.vim\r\n       sql_simplesnip.vim\r\n   plugin\r\n       simpleSnip.vim\r\n\r\n3. (Alexandre) Renamed snippets files to add an underscore in the filenames\r\n   example cs_simplesnip.vim, so they will not conflict with files already\r\n   there, but will still be loaded according to the filetype.\r\n\r\n4. (Xaizek) Put `<buffer>` specifier to all :abb commands in the sample snippets,\r\n   so they are defined locally to each buffer.\r\n\r\n5. (Xaizek) Added `<silent>` specifier to the :imap command in simpleSnip.vim to\r\n   prevent `:call ReplaceAll()` displaying on the statusbar when I leave insert mode.\r\n\r\n6. (Xaizek) Change :abb to :iabb in the snippets files. Otherwise one will be surprised \r\n   with results after typing name of one of snippets while being in the command-line mode.\r\n\r\nVersion 1.2\r\n\r\n1. (Xaizek) Provided the paste\/nopaste solution to be able to\r\n   indent manually the snippets instead to have vim indent them manually.\r\n   In some cases, vim did not indent the lines as expected, so his\r\n   idea provides a way to manually indent the snippets.\r\n\r\nVersion 1.3\r\n\r\n1. Added <leader>rr mapping to reload the snippets. So for example if you\r\n   are editing a .cs file and then go to modify your snippets file (filetype\r\n   plugin) then save the snippets file and then returning to the .cs file in\r\n   edition, reload the file to reload the snippets. To do this do <leader>rs\r\n   (\\rs) (rs for Reload Snippets) or save the file and reload it using e %\r\n\r\nversion 1.4\r\n\r\n1. Modified usage instructions (be sure not to have blanks (spaces) after\r\n   <cr> in the snippets or the automatic indentation may not be like expected.\r\n\r\n2. I added a tips section to the help (comment at the top of the file).\r\n\r\n3. I started another snippet file for vimscript snippets.\r\n\r\n4. Added the NewSnippetFromClipboard() function which allows to paste as a snippet (in the snippet format) to a snippet file, text copied to the * register (clipboard).\r\n   So no need to manually add the snippets keywords or the \"\\\", \"<cr>\" etc. The NewSnippetFromClipboard() function will take care of this only you have to copy to clipboard\r\n   the text you want to put to snippet, and then do <leader>nc (n for new, c for clipboard) (<leader> is \"\\\" by default so \\nc) then the text you copied to \r\n   clipboard will be pasted to the file as a snippet compatible with simpleSnip ready to be added or pasted directly to a snippets file.\r\n\r\n5. Added the NewEmptySnippet() function which uses the NewSnippet() function to add a new snippet to a snippet file.  \r\n\r\n6. Added the NewSnippet() function which is used by NewEmptySnippet() and NewSnippetFromClipboard() functions\r\n\r\n7. Added several snippets for csharp, vimscript, html, javascript, aspx.\r\n\r\n8. Added the S1() function which is like the S() function but a prefix may\r\n   be passed in parameters. To use in case \"aa\" may match actual code in the\r\n   snippet that is not part of placeholders. See the DataAdapter snippet in the csharp snippet file for example.\r\n\r\n9. Modified the regex in the ReplaceAll() function and in this function, I\r\n   added code to go to the next match after a placeholder is modified. Before\r\n   the cursor was staying at the position of the last replacement thus one had\r\n   to do several N to go back.\r\n\r\n10. Added ability to temporarily load the snippets that are normally used for another filetype, for example\r\n    to use the snippets in the sql_simplesnip.vim filetype plugin when editing a c# code file, or to load\r\n    the c# snippets when editing an aspx file, or again, to load the javascript snippets when editing an\r\n    html file. It is easy to load <leader>gs, then to come back to previous snippets <leader>rs.\r\n\r\nVersion 1.5\r\n\r\n1. Added folds\r\n2. Corrected a bug in the ReplaceAll() function, there was a space left over at line 9 which doing an error message.\r\n\r\nVersion 1.6\r\n\r\n1. (Xaizek) When a placeholder to replace ended with the end of line ($) it was not replaced by the replace all function. This is corrected. Replaced let l:to = expand(\"<cword>\") by let l:to = getreg('.')\r\n\r\n","install_details":"Unpack the archive to your $VIM directory.  It should contain the plugin file\r\nnamed simpleSnip.vim and several example snippet files:\r\n - snipcs.vim (for C#)\r\n - sniphtml.vim (for HTML)\r\n - snipsql.vim (for SQL)\r\n\r\nThen source unpacked *.vim files (open the file and do :so%) or restart vim.","5":"Unpack the archive to your $VIM directory.  It should contain the plugin file\r\nnamed simpleSnip.vim and several example snippet files:\r\n - snipcs.vim (for C#)\r\n - sniphtml.vim (for HTML)\r\n - snipsql.vim (for SQL)\r\n\r\nThen source unpacked *.vim files (open the file and do :so%) or restart vim.","first_name":"Alexandre","6":"Alexandre","last_name":"Viau","7":"Viau","releases":[{"0":"4314","vim_version":"7.0","1":"7.0","script_version":"1.6","2":"1.6","version_comment":"When a placeholder to replace ended with the end of line ($) it was not replaced by the replace all function. This is corrected. Replaced let l:to = expand(\"<cword>\") by let l:to = getreg('.')\r\n","3":"When a placeholder to replace ended with the end of line ($) it was not replaced by the replace all function. This is corrected. Replaced let l:to = expand(\"<cword>\") by let l:to = getreg('.')\r\n","package":"simpleSnip.vim","4":"simpleSnip.vim","src_id":"19293","5":"19293","creation_date":"1357125998","6":"1357125998"},{"0":"4314","vim_version":"7.0","1":"7.0","script_version":"1.5","2":"1.5","version_comment":"1. Added folds\r\n2. Corrected a bug in the ReplaceAll() function, there was a space left over at line 9 which doing an error message.","3":"1. Added folds\r\n2. Corrected a bug in the ReplaceAll() function, there was a space left over at line 9 which doing an error message.","package":"simpleSnip.vim","4":"simpleSnip.vim","src_id":"19218","5":"19218","creation_date":"1356000879","6":"1356000879"},{"0":"4314","vim_version":"7.0","1":"7.0","script_version":"1.4","2":"1.4","version_comment":"1. Modified usage instructions (be sure not to have blanks (spaces) after\r\n   <cr> in the snippets or the automatic indentation may not be like expected.\r\n\r\n2. I added a tips section to the help (comment at the top of the file).\r\n\r\n3. I started another snippet file for vimscript snippets.\r\n\r\n4. Added the NewSnippetFromClipboard() function which allows to paste as a snippet (in the snippet format) to a snippet file, text copied to the * register (clipboard).\r\n   So no need to manually add the snippets keywords or the \"\\\", \"<cr>\" etc. The NewSnippetFromClipboard() function will take care of this only you have to copy to clipboard\r\n   the text you want to put to snippet, and then do <leader>nc (n for new, c for clipboard) (<leader> is \"\\\" by default so \\nc) then the text you copied to \r\n   clipboard will be pasted to the file as a snippet compatible with simpleSnip ready to be added or pasted directly to a snippets file.\r\n\r\n5. Added the NewEmptySnippet() function which uses the NewSnippet() function to add a new snippet to a snippet file.  \r\n\r\n6. Added the NewSnippet() function which is used by NewEmptySnippet() and NewSnippetFromClipboard() functions\r\n\r\n7. Added several snippets for csharp, vimscript, html, javascript, aspx.\r\n\r\n8. Added the S1() function which is like the S() function but a prefix may\r\n   be passed in parameters. To use in case \"aa\" may match actual code in the\r\n   snippet that is not part of placeholders. See the DataAdapter snippet in the csharp snippet file for example.\r\n\r\n9. Modified the regex in the ReplaceAll() function and in this function, I\r\n   added code to go to the next match after a placeholder is modified. Before\r\n   the cursor was staying at the position of the last replacement thus one had\r\n   to do several N to go back.\r\n\r\n10. Added ability to temporarily load the snippets that are normally used for another filetype, for example\r\n    to use the snippets in the sql_simplesnip.vim filetype plugin when editing a c# code file, or to load\r\n    the c# snippets when editing an aspx file, or again, to load the javascript snippets when editing an\r\n    html file. It is easy to load <leader>gs, then to come back to previous snippets <leader>rs.","3":"1. Modified usage instructions (be sure not to have blanks (spaces) after\r\n   <cr> in the snippets or the automatic indentation may not be like expected.\r\n\r\n2. I added a tips section to the help (comment at the top of the file).\r\n\r\n3. I started another snippet file for vimscript snippets.\r\n\r\n4. Added the NewSnippetFromClipboard() function which allows to paste as a snippet (in the snippet format) to a snippet file, text copied to the * register (clipboard).\r\n   So no need to manually add the snippets keywords or the \"\\\", \"<cr>\" etc. The NewSnippetFromClipboard() function will take care of this only you have to copy to clipboard\r\n   the text you want to put to snippet, and then do <leader>nc (n for new, c for clipboard) (<leader> is \"\\\" by default so \\nc) then the text you copied to \r\n   clipboard will be pasted to the file as a snippet compatible with simpleSnip ready to be added or pasted directly to a snippets file.\r\n\r\n5. Added the NewEmptySnippet() function which uses the NewSnippet() function to add a new snippet to a snippet file.  \r\n\r\n6. Added the NewSnippet() function which is used by NewEmptySnippet() and NewSnippetFromClipboard() functions\r\n\r\n7. Added several snippets for csharp, vimscript, html, javascript, aspx.\r\n\r\n8. Added the S1() function which is like the S() function but a prefix may\r\n   be passed in parameters. To use in case \"aa\" may match actual code in the\r\n   snippet that is not part of placeholders. See the DataAdapter snippet in the csharp snippet file for example.\r\n\r\n9. Modified the regex in the ReplaceAll() function and in this function, I\r\n   added code to go to the next match after a placeholder is modified. Before\r\n   the cursor was staying at the position of the last replacement thus one had\r\n   to do several N to go back.\r\n\r\n10. Added ability to temporarily load the snippets that are normally used for another filetype, for example\r\n    to use the snippets in the sql_simplesnip.vim filetype plugin when editing a c# code file, or to load\r\n    the c# snippets when editing an aspx file, or again, to load the javascript snippets when editing an\r\n    html file. It is easy to load <leader>gs, then to come back to previous snippets <leader>rs.","package":"simpleSnip1.4.zip","4":"simpleSnip1.4.zip","src_id":"19048","5":"19048","creation_date":"1354015025","6":"1354015025"},{"0":"4314","vim_version":"7.0","1":"7.0","script_version":"1.3","2":"1.3","version_comment":"1. Added <leader>rr mapping to reload the snippets. So for example if you\r\n   are editing a .cs file and then go to modify your snippets file (filetype\r\n   plugin) then save the snippets file and then returning to the .cs file in\r\n   edition, reload the file to reload the snippets. To do this do <leader>rs\r\n   (\\rs) (rs for Reload Snippets) or save the file and reload it using e %","3":"1. Added <leader>rr mapping to reload the snippets. So for example if you\r\n   are editing a .cs file and then go to modify your snippets file (filetype\r\n   plugin) then save the snippets file and then returning to the .cs file in\r\n   edition, reload the file to reload the snippets. To do this do <leader>rs\r\n   (\\rs) (rs for Reload Snippets) or save the file and reload it using e %","package":"simpleSnip1.3.zip","4":"simpleSnip1.3.zip","src_id":"19014","5":"19014","creation_date":"1353568924","6":"1353568924"},{"0":"4314","vim_version":"7.0","1":"7.0","script_version":"1.2","2":"1.2","version_comment":"1. (Xaizek) Provided the paste\/nopaste solution to be able to\r\nindent manually the snippets instead to have vim indent them manually.\r\nIn some cases, vim did not indent the lines as expected, so his\r\nidea provides a way to manually indent the snippets.\r\n","3":"1. (Xaizek) Provided the paste\/nopaste solution to be able to\r\nindent manually the snippets instead to have vim indent them manually.\r\nIn some cases, vim did not indent the lines as expected, so his\r\nidea provides a way to manually indent the snippets.\r\n","package":"simpleSnip1.2.zip","4":"simpleSnip1.2.zip","src_id":"19008","5":"19008","creation_date":"1353509793","6":"1353509793"},{"0":"4314","vim_version":"7.0","1":"7.0","script_version":"1.1","2":"1.1","version_comment":"1. (Xaizek) Changed filetype of all files from `dos` to `unix`.  The thing is\r\n   that Vim-scripts with `dos` eol's work on Windows without issues, but\r\n   produce plenty of errors while they are loaded on *nix systems.\r\n   While Vim-scripts with `unix` eol's work on all platforms.\r\n\r\n2. (Xaizek) Modified directory structure to look like this\r\n   ftplugin\r\n       cs_simplesnip.vim\r\n       html_simplesnip.vim\r\n       sql_simplesnip.vim\r\n   plugin\r\n       simpleSnip.vim\r\n\r\n3. (Alexandre) Renamed snippets files to add an underscore in the filenames\r\n   example cs_simplesnip.vim, so they will not conflict with files already\r\n   there, but will still be loaded according to the filetype.\r\n\r\n4. (Xaizek) Put `<buffer>` specifier to all :abb commands in the sample snippets,\r\n   so they are defined locally to each buffer.\r\n\r\n5. (Xaizek) Added `<silent>` specifier to the :imap command in simpleSnip.vim to\r\n   prevent `:call ReplaceAll()` displaying on the statusbar when I leave insert mode.\r\n\r\n6. (Xaizek) Change :abb to :iabb in the snippets files. Otherwise one will be surprised \r\n   with results after typing name of one of snippets while being in the command-line mode.","3":"1. (Xaizek) Changed filetype of all files from `dos` to `unix`.  The thing is\r\n   that Vim-scripts with `dos` eol's work on Windows without issues, but\r\n   produce plenty of errors while they are loaded on *nix systems.\r\n   While Vim-scripts with `unix` eol's work on all platforms.\r\n\r\n2. (Xaizek) Modified directory structure to look like this\r\n   ftplugin\r\n       cs_simplesnip.vim\r\n       html_simplesnip.vim\r\n       sql_simplesnip.vim\r\n   plugin\r\n       simpleSnip.vim\r\n\r\n3. (Alexandre) Renamed snippets files to add an underscore in the filenames\r\n   example cs_simplesnip.vim, so they will not conflict with files already\r\n   there, but will still be loaded according to the filetype.\r\n\r\n4. (Xaizek) Put `<buffer>` specifier to all :abb commands in the sample snippets,\r\n   so they are defined locally to each buffer.\r\n\r\n5. (Xaizek) Added `<silent>` specifier to the :imap command in simpleSnip.vim to\r\n   prevent `:call ReplaceAll()` displaying on the statusbar when I leave insert mode.\r\n\r\n6. (Xaizek) Change :abb to :iabb in the snippets files. Otherwise one will be surprised \r\n   with results after typing name of one of snippets while being in the command-line mode.","package":"simpleSnip1.1.zip","4":"simpleSnip1.1.zip","src_id":"18993","5":"18993","creation_date":"1353327913","6":"1353327913"},{"0":"4314","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"simpleSnip.zip","4":"simpleSnip.zip","src_id":"18984","5":"18984","creation_date":"1353147403","6":"1353147403"}]},"4313":{"script_id":"4313","0":"4313","script_name":"BufNameComplete","1":"BufNameComplete","script_type":"utility","2":"utility","summary":"Insert mode completion of filenames loaded in Vim.","3":"Insert mode completion of filenames loaded in Vim.","description":"DESCRIPTION\r\nThe built-in filename completion i_CTRL-X_CTRL-F searches the file system\r\nbased on the current directory, so potentially there can be many matches.\r\nBut often, the file one wants to refer to is already open inside Vim.\r\n\r\nThis plugin offers an alternative filename completion that just considers\r\nbuffers loaded in Vim. Matches can start at any path component, so the mapping\r\nis especially useful for inserting relative paths, e.g. in\r\n    #include \"lib\/f|\r\n\r\nSOURCE\r\nThis completion type was motivated by this Stack Overflow question:\r\n    http:\/\/stackoverflow.com\/questions\/13406751\/vim-completion-based-on-buffer-name\r\n\r\nSEE ALSO\r\n- Check out the CompleteHelper.vim plugin page (vimscript #3914) for a full\r\n  list of insert mode completions powered by it.\r\n\r\nUSAGE\r\nIn insert mode, invoke the completion via CTRL-X f\r\nYou can then search forward and backward via CTRL-N \/ CTRL-P, as usual.\r\n\r\nCTRL-X f                Search for filenames loaded in Vim buffers (:ls)\r\n                        that start with the same 'isfname' characters as\r\n                        before the cursor.\r\n                        Any path component or the file name itself can start\r\n                        with the characters. When there are no filename\r\n                        characters before the cursor, both filename and\r\n                        filespec (relative to the current directory) of all\r\n                        loaded buffers are listed.","4":"DESCRIPTION\r\nThe built-in filename completion i_CTRL-X_CTRL-F searches the file system\r\nbased on the current directory, so potentially there can be many matches.\r\nBut often, the file one wants to refer to is already open inside Vim.\r\n\r\nThis plugin offers an alternative filename completion that just considers\r\nbuffers loaded in Vim. Matches can start at any path component, so the mapping\r\nis especially useful for inserting relative paths, e.g. in\r\n    #include \"lib\/f|\r\n\r\nSOURCE\r\nThis completion type was motivated by this Stack Overflow question:\r\n    http:\/\/stackoverflow.com\/questions\/13406751\/vim-completion-based-on-buffer-name\r\n\r\nSEE ALSO\r\n- Check out the CompleteHelper.vim plugin page (vimscript #3914) for a full\r\n  list of insert mode completions powered by it.\r\n\r\nUSAGE\r\nIn insert mode, invoke the completion via CTRL-X f\r\nYou can then search forward and backward via CTRL-N \/ CTRL-P, as usual.\r\n\r\nCTRL-X f                Search for filenames loaded in Vim buffers (:ls)\r\n                        that start with the same 'isfname' characters as\r\n                        before the cursor.\r\n                        Any path component or the file name itself can start\r\n                        with the characters. When there are no filename\r\n                        characters before the cursor, both filename and\r\n                        filespec (relative to the current directory) of all\r\n                        loaded buffers are listed.","install_details":"INSTALLATION\r\nThis script is packaged as a vimball. If you have the \"gunzip\" decompressor\r\nin your PATH, simply edit the *.vmb.gz package in Vim; otherwise, decompress\r\nthe archive first, e.g. using WinZip. Inside Vim, install by sourcing the\r\nvimball or via the :UseVimball command.\r\n    vim BufNameComplete*.vmb.gz\r\n    :so %\r\nTo uninstall, use the :RmVimball command.\r\n\r\nDEPENDENCIES\r\n- Requires Vim 7.0 or higher.\r\n- Requires the CompleteHelper.vim plugin (vimscript #3914), version 1.10 or\r\n  higher.\r\n\r\nCONFIGURATION\r\nFor a permanent configuration, put the following commands into your vimrc:\r\n\r\nIf you want to use a different mapping, map your keys to the\r\n<Plug>(BufNameComplete) mapping target _before_ sourcing the script (e.g. in\r\nyour vimrc):\r\n    imap <C-x>f <Plug>(BufNameComplete)","5":"INSTALLATION\r\nThis script is packaged as a vimball. If you have the \"gunzip\" decompressor\r\nin your PATH, simply edit the *.vmb.gz package in Vim; otherwise, decompress\r\nthe archive first, e.g. using WinZip. Inside Vim, install by sourcing the\r\nvimball or via the :UseVimball command.\r\n    vim BufNameComplete*.vmb.gz\r\n    :so %\r\nTo uninstall, use the :RmVimball command.\r\n\r\nDEPENDENCIES\r\n- Requires Vim 7.0 or higher.\r\n- Requires the CompleteHelper.vim plugin (vimscript #3914), version 1.10 or\r\n  higher.\r\n\r\nCONFIGURATION\r\nFor a permanent configuration, put the following commands into your vimrc:\r\n\r\nIf you want to use a different mapping, map your keys to the\r\n<Plug>(BufNameComplete) mapping target _before_ sourcing the script (e.g. in\r\nyour vimrc):\r\n    imap <C-x>f <Plug>(BufNameComplete)","first_name":"Ingo","6":"Ingo","last_name":"Karkat","7":"Karkat","releases":[{"0":"4313","vim_version":"7.0","1":"7.0","script_version":"1.00","2":"1.00","version_comment":"Initial upload","3":"Initial upload","package":"BufNameComplete-1.00.vmb.gz","4":"BufNameComplete-1.00.vmb.gz","src_id":"18980","5":"18980","creation_date":"1353071288","6":"1353071288"}]},"4312":{"script_id":"4312","0":"4312","script_name":"mymarksbrowser","1":"mymarksbrowser","script_type":"utility","2":"utility","summary":"Improved marksbrowser","3":"Improved marksbrowser","description":"Based on original marksbrowser.vim.\r\nDifferences:\r\n1. CTRL-F2 - toggle window\r\n2. Browser window is live (refreshable) - shows new marks, new buffer (on buffer switching)","4":"Based on original marksbrowser.vim.\r\nDifferences:\r\n1. CTRL-F2 - toggle window\r\n2. Browser window is live (refreshable) - shows new marks, new buffer (on buffer switching)","install_details":"1. Depends on 'ctags.vim' -- install it first\r\n2. Copy 'mymarksbrowser.vim' to plugins folder as usual","5":"1. Depends on 'ctags.vim' -- install it first\r\n2. Copy 'mymarksbrowser.vim' to plugins folder as usual","first_name":"Paul","6":"Paul","last_name":"V","7":"V","releases":[{"0":"4312","vim_version":"7.0","1":"7.0","script_version":"1.1","2":"1.1","version_comment":"Depends now on ctags.vim -- install it first!\r\n\r\n* added tags names into marks browser\r\n* added highlighting of tag names","3":"Depends now on ctags.vim -- install it first!\r\n\r\n* added tags names into marks browser\r\n* added highlighting of tag names","package":"mymarksbrowser.vim","4":"mymarksbrowser.vim","src_id":"19002","5":"19002","creation_date":"1353486723","6":"1353486723"},{"0":"4312","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"mymarksbrowser.vim","4":"mymarksbrowser.vim","src_id":"18976","5":"18976","creation_date":"1352954747","6":"1352954747"}]},"4311":{"script_id":"4311","0":"4311","script_name":"doctest.vim","1":"doctest.vim","script_type":"syntax","2":"syntax","summary":"Highlighting for python doctest files including ReST markup","3":"Highlighting for python doctest files including ReST markup","description":"This is a syntax file for highlighting python doctest files.\r\n\r\nThis is useful when you have some doctests separated from the source code.\r\n\r\nIf the extension of your doctest files is not '.doctest', you should set the filetype to doctest.\r\n\r\nThe doctest blocks of the file are highlighted by 'syntax\/python.vim' whereas the rest of the file is highlighted by 'syntax\/rst.vim'.","4":"This is a syntax file for highlighting python doctest files.\r\n\r\nThis is useful when you have some doctests separated from the source code.\r\n\r\nIf the extension of your doctest files is not '.doctest', you should set the filetype to doctest.\r\n\r\nThe doctest blocks of the file are highlighted by 'syntax\/python.vim' whereas the rest of the file is highlighted by 'syntax\/rst.vim'.","install_details":"Place doctest.vim into a syntax directory.","5":"Place doctest.vim into a syntax directory.","first_name":"farid","6":"farid","last_name":"smai","7":"smai","releases":[{"0":"4311","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"doctest.vim","4":"doctest.vim","src_id":"18975","5":"18975","creation_date":"1352901177","6":"1352901177"}]},"4310":{"script_id":"4310","0":"4310","script_name":"vim-lesscss","1":"vim-lesscss","script_type":"utility","2":"utility","summary":"Update corresponding css files on the fly while edits less files ","3":"Update corresponding css files on the fly while edits less files ","description":"Vim plugin that make it easy to edit less files without need to manually\r\nupdate corresponding css file.\r\n\r\nJust open your `less` file in Vim and edit it. On save corresponding `css`\r\nfile will be created with the same name as original.\r\n\r\nUse ':Lesscss[!] [cmd] to run predefined command or reuse previous.\r\n\r\nEach command is a dictionary that define custom options you want to use\r\nwhen ':Lesscss' runs, such as less compiler options or output file location.\r\n\r\nCommand applied globally unless the ! is provided, in which case the command\r\napplied only to current buffer.\r\n\r\nFor example, to disable Lesscss for all buffers run:\r\n\r\n    :Lesscss off\r\n\r\nTo disable Lesscss only for current one use:\r\n\r\n    :Lesscss! off\r\n\r\nFor more details, see README on github:\r\n\r\nhttps:\/\/github.com\/vitalk\/vim-lesscss","4":"Vim plugin that make it easy to edit less files without need to manually\r\nupdate corresponding css file.\r\n\r\nJust open your `less` file in Vim and edit it. On save corresponding `css`\r\nfile will be created with the same name as original.\r\n\r\nUse ':Lesscss[!] [cmd] to run predefined command or reuse previous.\r\n\r\nEach command is a dictionary that define custom options you want to use\r\nwhen ':Lesscss' runs, such as less compiler options or output file location.\r\n\r\nCommand applied globally unless the ! is provided, in which case the command\r\napplied only to current buffer.\r\n\r\nFor example, to disable Lesscss for all buffers run:\r\n\r\n    :Lesscss off\r\n\r\nTo disable Lesscss only for current one use:\r\n\r\n    :Lesscss! off\r\n\r\nFor more details, see README on github:\r\n\r\nhttps:\/\/github.com\/vitalk\/vim-lesscss","install_details":"If your don't have a preferred way to install Vim plugins, try to use pathogen(http:\/\/www.vim.org\/scripts\/script.php?script_id=2332) and then run:\r\n\r\ncd ~\/.vim\/bundle\r\ngit clone git:\/\/github.com\/vitalk\/vim-lesscss.git","5":"If your don't have a preferred way to install Vim plugins, try to use pathogen(http:\/\/www.vim.org\/scripts\/script.php?script_id=2332) and then run:\r\n\r\ncd ~\/.vim\/bundle\r\ngit clone git:\/\/github.com\/vitalk\/vim-lesscss.git","first_name":"Vital","6":"Vital","last_name":"Kudzelka","7":"Kudzelka","releases":[{"0":"4310","vim_version":"7.0","1":"7.0","script_version":"0.7","2":"0.7","version_comment":"Support source map for output.","3":"Support source map for output.","package":"vim-lesscss-0.7.zip","4":"vim-lesscss-0.7.zip","src_id":"21880","5":"21880","creation_date":"1400006916","6":"1400006916"},{"0":"4310","vim_version":"7.0","1":"7.0","script_version":"0.4","2":"0.4","version_comment":"Add support of custom commads to :Lesscss.","3":"Add support of custom commads to :Lesscss.","package":"vim-lesscss-0.4.zip","4":"vim-lesscss-0.4.zip","src_id":"20728","5":"20728","creation_date":"1377787980","6":"1377787980"},{"0":"4310","vim_version":"7.0","1":"7.0","script_version":"0.2","2":"0.2","version_comment":"fail silently if cannot create output directory and prevent write to remote fs","3":"fail silently if cannot create output directory and prevent write to remote fs","package":"vim-lesscss-0.2.zip","4":"vim-lesscss-0.2.zip","src_id":"19056","5":"19056","creation_date":"1354092136","6":"1354092136"},{"0":"4310","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"vim-lesscss.tar.gz","4":"vim-lesscss.tar.gz","src_id":"18969","5":"18969","creation_date":"1352733850","6":"1352733850"}]},"4309":{"script_id":"4309","0":"4309","script_name":"multichange.vim","1":"multichange.vim","script_type":"utility","2":"utility","summary":"Edit a word and have the change propagate throughout the buffer","3":"Edit a word and have the change propagate throughout the buffer","description":"Github project: https:\/\/github.com\/AndrewRadev\/multichange.vim\r\n\r\nThe plugin exposes a command, :Multichange, that enters a special \"multi\" mode. In this mode, any change of a word with a \"c\" mapping is propagated throughout the entire file. Example:\r\n\r\n    def add(one, two):\r\n        return one + two\r\n\r\nIf we wanted to rename the \"one\" parameter to \"first\" and the \"two\" parameter to \"second\", we could do it in a number of ways using either the . mapping or substitutions. With multichange, we execute the :Multichange command, and then perform the cw operation on \"one\" and \"two\" within the argument list. Changing them to \"first\" and \"second\" will be performed for the entire file.\r\n\r\nNote that this works similarly to the * mapping -- it replaces words only, so it won't replace the \"one\" in \"one_more_thing\".\r\n\r\nTo exit \"multi\" mode, press <esc>. To limit the \"multi\" mode to only an area of the file (for example, to rename variables within a single function definition), select the desired area and then execute :Multichange.\r\n\r\nYou can also make a change in visual mode. For example, you want to change a function name in Vimscript:\r\n\r\n    function! s:BadName()\r\n    endfunction\r\n\r\n    call s:BadName()\r\n\r\nSince : is not in iskeyword (I think), you might have problems changing the function name using word motions. In this case, start \"multi\" mode as described above, then mark s:BadName in characterwise visual mode (with v). After pressing c, change the name to whatever you like. This will propagate the same way as the word change from before. The difference is that whatever was selected will be changed, regardless of word boundaries. So, if you only select \"Name\" and change it, any encounter of \"Name\" will be replaced.\r\n\r\nThe plugin also exposes a mapping for the :Multichange command that acts as a text object. Read the documentation for more details.\r\n","4":"Github project: https:\/\/github.com\/AndrewRadev\/multichange.vim\r\n\r\nThe plugin exposes a command, :Multichange, that enters a special \"multi\" mode. In this mode, any change of a word with a \"c\" mapping is propagated throughout the entire file. Example:\r\n\r\n    def add(one, two):\r\n        return one + two\r\n\r\nIf we wanted to rename the \"one\" parameter to \"first\" and the \"two\" parameter to \"second\", we could do it in a number of ways using either the . mapping or substitutions. With multichange, we execute the :Multichange command, and then perform the cw operation on \"one\" and \"two\" within the argument list. Changing them to \"first\" and \"second\" will be performed for the entire file.\r\n\r\nNote that this works similarly to the * mapping -- it replaces words only, so it won't replace the \"one\" in \"one_more_thing\".\r\n\r\nTo exit \"multi\" mode, press <esc>. To limit the \"multi\" mode to only an area of the file (for example, to rename variables within a single function definition), select the desired area and then execute :Multichange.\r\n\r\nYou can also make a change in visual mode. For example, you want to change a function name in Vimscript:\r\n\r\n    function! s:BadName()\r\n    endfunction\r\n\r\n    call s:BadName()\r\n\r\nSince : is not in iskeyword (I think), you might have problems changing the function name using word motions. In this case, start \"multi\" mode as described above, then mark s:BadName in characterwise visual mode (with v). After pressing c, change the name to whatever you like. This will propagate the same way as the word change from before. The difference is that whatever was selected will be changed, regardless of word boundaries. So, if you only select \"Name\" and change it, any encounter of \"Name\" will be replaced.\r\n\r\nThe plugin also exposes a mapping for the :Multichange command that acts as a text object. Read the documentation for more details.\r\n","install_details":"There are several ways to install the plugin. The recommended one is by using Tim Pope's pathogen (http:\/\/www.vim.org\/scripts\/script.php?script_id=2332). In that case, you can clone the plugin's git repository like so:\r\n\r\n    git clone git:\/\/github.com\/AndrewRadev\/multichange.vim.git ~\/.vim\/bundle\/multichange\r\n\r\nIf your vim configuration is under git version control, you could also set up the repository as a submodule, which would allow you to update more easily. The command is (provided you're in ~\/.vim):\r\n\r\n    git submodule add git:\/\/github.com\/AndrewRadev\/multichange.vim.git bundle\/multichange\r\n\r\nAnother way is to simply copy all the essential directories inside the ~\/.vim directory: autoload, doc, plugin.\r\n","5":"There are several ways to install the plugin. The recommended one is by using Tim Pope's pathogen (http:\/\/www.vim.org\/scripts\/script.php?script_id=2332). In that case, you can clone the plugin's git repository like so:\r\n\r\n    git clone git:\/\/github.com\/AndrewRadev\/multichange.vim.git ~\/.vim\/bundle\/multichange\r\n\r\nIf your vim configuration is under git version control, you could also set up the repository as a submodule, which would allow you to update more easily. The command is (provided you're in ~\/.vim):\r\n\r\n    git submodule add git:\/\/github.com\/AndrewRadev\/multichange.vim.git bundle\/multichange\r\n\r\nAnother way is to simply copy all the essential directories inside the ~\/.vim directory: autoload, doc, plugin.\r\n","first_name":"Andrew","6":"Andrew","last_name":"Radev","7":"Radev","releases":[{"0":"4309","vim_version":"7.0","1":"7.0","script_version":"0.2.0","2":"0.2.0","version_comment":"Mapping is a text object now, so it allows much easier targeting of the area of effect.","3":"Mapping is a text object now, so it allows much easier targeting of the area of effect.","package":"multichange.zip","4":"multichange.zip","src_id":"22838","5":"22838","creation_date":"1422353853","6":"1422353853"},{"0":"4309","vim_version":"7.0","1":"7.0","script_version":"0.1.0","2":"0.1.0","version_comment":"Initial upload","3":"Initial upload","package":"multichange.zip","4":"multichange.zip","src_id":"18968","5":"18968","creation_date":"1352574729","6":"1352574729"}]},"4308":{"script_id":"4308","0":"4308","script_name":"psettings","1":"psettings","script_type":"utility","2":"utility","summary":"Allows you to have per-project settings files for vim.","3":"Allows you to have per-project settings files for vim.","description":"psettings aka Project Settings\r\n===\r\n\r\nHomepage: http:\/\/margaine.com\/psettings\r\nGithub repository: https:\/\/github.com\/Ralt\/psettings\r\n\r\nDescription\r\n---\r\n\r\nThis plugin allows you to have different vim settings for each project.\r\n\r\nIf you're working with different coding standards (X project has shiftwidth 2,\r\nY project has shiftwidth 4, etc), it can become cumbersome to always work with\r\nvim.\r\n\r\nThis project solves this.\r\n\r\nUsage\r\n---\r\n\r\nPut a `.psettings` file at the root of your project. In this file, put the\r\nfollowing line:\r\n\r\n    Drupal\r\n\r\nThat is, if you want to use the `Drupal` project settings.\r\n\r\nThe default settings are in the `settings\/` folder of this plugin. You can add\r\nyour own settings folder by putting the following in your vimrc:\r\n\r\n    let g:psettings_custom_path = '\/your\/path\/to\/settings\/'\r\n\r\nIf a settings file is found in both folders, both will be used.\r\n\r\nThe names you put in the `.psettings` file must match the filename of the\r\nsettings file, less the `.vim` extension.\r\n\r\nYou can put several project settings in your `.psettings` file, each settings\r\nfile will be read sequentially. This allows you to have one \"major\" settings\r\nfile(for example, all the projects in the PHP language), and several \"minor\"\r\nsettings modes (Drupal projects, Symfony projects, Zend projects, etc).\r\n\r\nIf you simply want to run a project settings, you can also run the following\r\ncommand:\r\n\r\n    :call Psettings(\"Drupal\")\r\n\r\nRoadmap\r\n---\r\n\r\nSee the issue queue: https:\/\/github.com\/Ralt\/psettings\/issues?labels=enhancement&page=1&state=open\r\n\r\nContributors\r\n---\r\n\r\n- Florian Margaine - http:\/\/margaine.com\r\n\r\nLicense\r\n---\r\n\r\nMIT License.","4":"psettings aka Project Settings\r\n===\r\n\r\nHomepage: http:\/\/margaine.com\/psettings\r\nGithub repository: https:\/\/github.com\/Ralt\/psettings\r\n\r\nDescription\r\n---\r\n\r\nThis plugin allows you to have different vim settings for each project.\r\n\r\nIf you're working with different coding standards (X project has shiftwidth 2,\r\nY project has shiftwidth 4, etc), it can become cumbersome to always work with\r\nvim.\r\n\r\nThis project solves this.\r\n\r\nUsage\r\n---\r\n\r\nPut a `.psettings` file at the root of your project. In this file, put the\r\nfollowing line:\r\n\r\n    Drupal\r\n\r\nThat is, if you want to use the `Drupal` project settings.\r\n\r\nThe default settings are in the `settings\/` folder of this plugin. You can add\r\nyour own settings folder by putting the following in your vimrc:\r\n\r\n    let g:psettings_custom_path = '\/your\/path\/to\/settings\/'\r\n\r\nIf a settings file is found in both folders, both will be used.\r\n\r\nThe names you put in the `.psettings` file must match the filename of the\r\nsettings file, less the `.vim` extension.\r\n\r\nYou can put several project settings in your `.psettings` file, each settings\r\nfile will be read sequentially. This allows you to have one \"major\" settings\r\nfile(for example, all the projects in the PHP language), and several \"minor\"\r\nsettings modes (Drupal projects, Symfony projects, Zend projects, etc).\r\n\r\nIf you simply want to run a project settings, you can also run the following\r\ncommand:\r\n\r\n    :call Psettings(\"Drupal\")\r\n\r\nRoadmap\r\n---\r\n\r\nSee the issue queue: https:\/\/github.com\/Ralt\/psettings\/issues?labels=enhancement&page=1&state=open\r\n\r\nContributors\r\n---\r\n\r\n- Florian Margaine - http:\/\/margaine.com\r\n\r\nLicense\r\n---\r\n\r\nMIT License.","install_details":"","5":"","first_name":"Florian","6":"Florian","last_name":"Margaine","7":"Margaine","releases":[{"0":"4308","vim_version":"7.0","1":"7.0","script_version":"1.0.0","2":"1.0.0","version_comment":"Added new essential feature. Now feature complete.","3":"Added new essential feature. Now feature complete.","package":"psettings.zip","4":"psettings.zip","src_id":"18965","5":"18965","creation_date":"1352556272","6":"1352556272"},{"0":"4308","vim_version":"7.0","1":"7.0","script_version":"0.1.0","2":"0.1.0","version_comment":"Initial upload","3":"Initial upload","package":"psettings.zip","4":"psettings.zip","src_id":"18963","5":"18963","creation_date":"1352534467","6":"1352534467"}]},"4307":{"script_id":"4307","0":"4307","script_name":"show-git-log","1":"show-git-log","script_type":"utility","2":"utility","summary":"A plugin simply shows a file's git log in a new tab\/split window.","3":"A plugin simply shows a file's git log in a new tab\/split window.","description":"Using this plugin to show a file's git log commit infos.\r\n\r\nafter installation: \r\n    type:\r\n    tsl(show log in tab mode)\r\n    vsl(show log in vertically splite mode)\r\n    hsl(show log in horizontally split mode)\r\n\r\ngithub:\r\nhttps:\/\/github.com\/sunuslee\/vim-plugin-show-git-log","4":"Using this plugin to show a file's git log commit infos.\r\n\r\nafter installation: \r\n    type:\r\n    tsl(show log in tab mode)\r\n    vsl(show log in vertically splite mode)\r\n    hsl(show log in horizontally split mode)\r\n\r\ngithub:\r\nhttps:\/\/github.com\/sunuslee\/vim-plugin-show-git-log","install_details":"just put  showgitlog.vim into ~\/.vim\/plugin\/","5":"just put  showgitlog.vim into ~\/.vim\/plugin\/","first_name":"sunus","6":"sunus","last_name":"lee","7":"lee","releases":[{"0":"4307","vim_version":"7.3","1":"7.3","script_version":"0.2","2":"0.2","version_comment":"fix a bug, so now this plugin can auto-adjust file's path and find it's log correctly. ","3":"fix a bug, so now this plugin can auto-adjust file's path and find it's log correctly. ","package":"showgitlog.tar","4":"showgitlog.tar","src_id":"18962","5":"18962","creation_date":"1352468521","6":"1352468521"},{"0":"4307","vim_version":"7.3","1":"7.3","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"showgitlog.tar","4":"showgitlog.tar","src_id":"18959","5":"18959","creation_date":"1352449406","6":"1352449406"}]},"4306":{"script_id":"4306","0":"4306","script_name":"HiCursorWords","1":"HiCursorWords","script_type":"utility","2":"utility","summary":"Highlights words under the cursor.","3":"Highlights words under the cursor.","description":"This script highlights words under the cursor like many IDEs.\r\n\r\nThis doesn't provide scope-aware highlighting nor language specific one.\r\nYou can control highlighting by highlighting group names.\r\n\r\nVariables:\r\n\r\n  (A right hand side value is a default value.)\r\n\r\n  g:HiCursorWords_delay = 200\r\n      A delay for highlighting in milliseconds.\r\n      Smaller value may cause your machine slow down.\r\n\r\n  g:HiCursorWords_hiGroupRegexp = ''\r\n      If empty, all words are highlighted.\r\n      If not empty, only the specified highlight group is highlighted.\r\n      (my memo: 'Identifier\\|vimOperParen')\r\n\r\n      To investigate highlight group name, the next variable may help you.\r\n\r\n  g:HiCursorWords_debugEchoHiName = 0\r\n      If not 0, echoes the highlight group name under the cursor.\r\n\r\nHightlight groups:\r\n\r\n  (Do :highlight! as you like.)\r\n\r\n  WordUnderTheCursor\r\n","4":"This script highlights words under the cursor like many IDEs.\r\n\r\nThis doesn't provide scope-aware highlighting nor language specific one.\r\nYou can control highlighting by highlighting group names.\r\n\r\nVariables:\r\n\r\n  (A right hand side value is a default value.)\r\n\r\n  g:HiCursorWords_delay = 200\r\n      A delay for highlighting in milliseconds.\r\n      Smaller value may cause your machine slow down.\r\n\r\n  g:HiCursorWords_hiGroupRegexp = ''\r\n      If empty, all words are highlighted.\r\n      If not empty, only the specified highlight group is highlighted.\r\n      (my memo: 'Identifier\\|vimOperParen')\r\n\r\n      To investigate highlight group name, the next variable may help you.\r\n\r\n  g:HiCursorWords_debugEchoHiName = 0\r\n      If not 0, echoes the highlight group name under the cursor.\r\n\r\nHightlight groups:\r\n\r\n  (Do :highlight! as you like.)\r\n\r\n  WordUnderTheCursor\r\n","install_details":"Just source this file. (Put this file into the plugin directory.)\r\n","5":"Just source this file. (Put this file into the plugin directory.)\r\n","first_name":"Shuhei","6":"Shuhei","last_name":"Kubota","7":"Kubota","releases":[{"0":"4306","vim_version":"7.0","1":"7.0","script_version":"0.2","2":"0.2","version_comment":"* fixed mis-highlighting\r\n* fixed raised error, opening buffer","3":"* fixed mis-highlighting\r\n* fixed raised error, opening buffer","package":"hicursorwords.vim","4":"hicursorwords.vim","src_id":"19158","5":"19158","creation_date":"1355112934","6":"1355112934"},{"0":"4306","vim_version":"7.2","1":"7.2","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"hicursorwords.vim","4":"hicursorwords.vim","src_id":"18958","5":"18958","creation_date":"1352433717","6":"1352433717"}]},"4305":{"script_id":"4305","0":"4305","script_name":"green_light.vim","1":"green_light.vim","script_type":"color scheme","2":"color scheme","summary":"my favorite colorscheme","3":"my favorite colorscheme","description":"just modify the some default colors.  you can change them to your favorite colors\r\nif you want get best effect, please use gvim and add plugin TagHighlight:http:\/\/www.vim.org\/scripts\/script.php?script_id=2646","4":"just modify the some default colors.  you can change them to your favorite colors\r\nif you want get best effect, please use gvim and add plugin TagHighlight:http:\/\/www.vim.org\/scripts\/script.php?script_id=2646","install_details":"just copy this file to ~\/.vim\/colors\/\r\n","5":"just copy this file to ~\/.vim\/colors\/\r\n","first_name":"JingYu","6":"JingYu","last_name":"Li","7":"Li","releases":[{"0":"4305","vim_version":"7.2","1":"7.2","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"green_light.vim","4":"green_light.vim","src_id":"18957","5":"18957","creation_date":"1352429322","6":"1352429322"}]},"4304":{"script_id":"4304","0":"4304","script_name":"textobj-motionmotion","1":"textobj-motionmotion","script_type":"utility","2":"utility","summary":"Text objects for bounds of 2 motions","3":"Text objects for bounds of 2 motions","description":"*textobj-motionmotion* is a Vim plugin to provide text objets to select a\r\npiece of text bounded by the cursor positions of the following 2 motions.\r\n\r\nFor example, an asterisk (*) is used to denote the cursor position:\r\n>\r\n  .\/runtime\/doc\/mo*tion.txt\r\n<\r\n\"vim3bt.\" will select 'doc\/motion' as follows:\r\n(here (^) indicates the selected texts)\r\n>\r\n  .\/runtime\/doc\/motion.txt\r\n            ^^^^^^^^^^\r\n<\r\nRoughly speaking, this plugin makes an operator such that [\"^x]c{motion} to\r\nbe able to respond [\"x]cim{motion}{motion} (*im* is the default key mapping).\r\nHence the name \"motionmotion\" has been derived from.\r\n\r\nNote that this plugin is far from complete. Please use *[range]* or\r\n*Visual-mode* in the real world!\r\n\r\nRequirements:\r\n- Vim 7.2 or later\r\n- |textobj-user| 0.3.8 or later  (vimscript#2100) \r\n\r\nLatest version:\r\nhttps:\/\/github.com\/hchbaw\/textobj-motionmotion.vim\r\n\r\nDocument in HTML format:\r\nhttp:\/\/hchbaw.github.com\/experiment\/vim\/textobj-motionmotion.html\r\n\r\n","4":"*textobj-motionmotion* is a Vim plugin to provide text objets to select a\r\npiece of text bounded by the cursor positions of the following 2 motions.\r\n\r\nFor example, an asterisk (*) is used to denote the cursor position:\r\n>\r\n  .\/runtime\/doc\/mo*tion.txt\r\n<\r\n\"vim3bt.\" will select 'doc\/motion' as follows:\r\n(here (^) indicates the selected texts)\r\n>\r\n  .\/runtime\/doc\/motion.txt\r\n            ^^^^^^^^^^\r\n<\r\nRoughly speaking, this plugin makes an operator such that [\"^x]c{motion} to\r\nbe able to respond [\"x]cim{motion}{motion} (*im* is the default key mapping).\r\nHence the name \"motionmotion\" has been derived from.\r\n\r\nNote that this plugin is far from complete. Please use *[range]* or\r\n*Visual-mode* in the real world!\r\n\r\nRequirements:\r\n- Vim 7.2 or later\r\n- |textobj-user| 0.3.8 or later  (vimscript#2100) \r\n\r\nLatest version:\r\nhttps:\/\/github.com\/hchbaw\/textobj-motionmotion.vim\r\n\r\nDocument in HTML format:\r\nhttp:\/\/hchbaw.github.com\/experiment\/vim\/textobj-motionmotion.html\r\n\r\n","install_details":"","5":"","first_name":"Takeshi","6":"Takeshi","last_name":"Banse","7":"Banse","releases":[{"0":"4304","vim_version":"7.0","1":"7.0","script_version":"0.0.2.2","2":"0.0.2.2","version_comment":"Fix docs; thank you very much pekepeke!","3":"Fix docs; thank you very much pekepeke!","package":"textobj-motionmotion-v0.0.2.2.zip","4":"textobj-motionmotion-v0.0.2.2.zip","src_id":"20873","5":"20873","creation_date":"1380806371","6":"1380806371"},{"0":"4304","vim_version":"7.2","1":"7.2","script_version":"0.0.2.1","2":"0.0.2.1","version_comment":"correct docs; no code changes","3":"correct docs; no code changes","package":"textobj-motionmotion-v0.0.2.1.zip","4":"textobj-motionmotion-v0.0.2.1.zip","src_id":"18979","5":"18979","creation_date":"1353060003","6":"1353060003"},{"0":"4304","vim_version":"7.2","1":"7.2","script_version":"0.0.2","2":"0.0.2","version_comment":"Initial upload","3":"Initial upload","package":"textobj-motionmotion-v0.0.2.zip","4":"textobj-motionmotion-v0.0.2.zip","src_id":"18956","5":"18956","creation_date":"1352382214","6":"1352382214"}]},"4303":{"script_id":"4303","0":"4303","script_name":"custom_dict","1":"custom_dict","script_type":"utility","2":"utility","summary":"custom dict complete plugin","3":"custom dict complete plugin","description":"https:\/\/raw.github.com\/sunsol\/custom_dict\/master\/demo.gif\r\nhttps:\/\/raw.github.com\/sunsol\/custom_dict\/master\/demo.webm\r\n\r\n自定义字典补全\r\n带部分常用python标准库中文字典\r\n增加命令可以手动添加模块\r\n详细内容看演示和doc\/custom_dict.txt","4":"https:\/\/raw.github.com\/sunsol\/custom_dict\/master\/demo.gif\r\nhttps:\/\/raw.github.com\/sunsol\/custom_dict\/master\/demo.webm\r\n\r\n自定义字典补全\r\n带部分常用python标准库中文字典\r\n增加命令可以手动添加模块\r\n详细内容看演示和doc\/custom_dict.txt","install_details":"windows：解压至vimfiles目录\r\nlinux:解压至.vim","5":"windows：解压至vimfiles目录\r\nlinux:解压至.vim","first_name":"sunsol","6":"sunsol","last_name":"zn","7":"zn","releases":[{"0":"4303","vim_version":"7.3","1":"7.3","script_version":"2.0","2":"2.0","version_comment":"fix bug","3":"fix bug","package":"customdict.zip","4":"customdict.zip","src_id":"19821","5":"19821","creation_date":"1366088528","6":"1366088528"},{"0":"4303","vim_version":"7.2","1":"7.2","script_version":"2.0","2":"2.0","version_comment":"speed up. update python complete","3":"speed up. update python complete","package":"customdict.zip","4":"customdict.zip","src_id":"19817","5":"19817","creation_date":"1366010633","6":"1366010633"},{"0":"4303","vim_version":"7.3","1":"7.3","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"custom_dict.zip","4":"custom_dict.zip","src_id":"18954","5":"18954","creation_date":"1352356672","6":"1352356672"}]},"4302":{"script_id":"4302","0":"4302","script_name":"tshell","1":"tshell","script_type":"color scheme","2":"color scheme","summary":"A dark gray color scheme for GUI and 256 color terminal.","3":"A dark gray color scheme for GUI and 256 color terminal.","description":"I just modified the Gentooish color scheme and used the evening color for term,the main colors are dark-golden and dark-gray,you can change them to your favorite colors.","4":"I just modified the Gentooish color scheme and used the evening color for term,the main colors are dark-golden and dark-gray,you can change them to your favorite colors.","install_details":"Just put the tshell.vim  in your vimfiles\/colors  or .vim\/colors directory.","5":"Just put the tshell.vim  in your vimfiles\/colors  or .vim\/colors directory.","first_name":"\u957f\u677e","6":"长松","last_name":"\u7530","7":"田","releases":[{"0":"4302","vim_version":"7.0","1":"7.0","script_version":"0.2","2":"0.2","version_comment":"some details fix","3":"some details fix","package":"tshell.vim","4":"tshell.vim","src_id":"19043","5":"19043","creation_date":"1353995400","6":"1353995400"},{"0":"4302","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"tshell.vim","4":"tshell.vim","src_id":"18953","5":"18953","creation_date":"1352289396","6":"1352289396"}]},"4301":{"script_id":"4301","0":"4301","script_name":"vim-moncf","1":"vim-moncf","script_type":"syntax","2":"syntax","summary":"Vim syntax highlightning for mon.cf","3":"Vim syntax highlightning for mon.cf","description":"Vim syntax highlighting for mon.cf\r\n\r\n\"mon\" is Service Monitoring Daemon.\r\nhttps:\/\/mon.wiki.kernel.org\/index.php\/Main_Page","4":"Vim syntax highlighting for mon.cf\r\n\r\n\"mon\" is Service Monitoring Daemon.\r\nhttps:\/\/mon.wiki.kernel.org\/index.php\/Main_Page","install_details":"* Extract the file and put files in your Vim directory\r\n   (usually ~\/.vim\/ or Program Files\/Vim\/vimfiles on Windows).\r\n\r\n* If you use Vundle, you can install quite simply.\r\n\r\n    Sample `.vimrc`:\r\n\r\n    ```vim\r\n    Bundle 'unagi\/vim-moncf'\r\n    ```\r\n\r\n    Launch `vim`, run `:BundleInstall`","5":"* Extract the file and put files in your Vim directory\r\n   (usually ~\/.vim\/ or Program Files\/Vim\/vimfiles on Windows).\r\n\r\n* If you use Vundle, you can install quite simply.\r\n\r\n    Sample `.vimrc`:\r\n\r\n    ```vim\r\n    Bundle 'unagi\/vim-moncf'\r\n    ```\r\n\r\n    Launch `vim`, run `:BundleInstall`","first_name":"YAMAGUCHI","6":"YAMAGUCHI","last_name":"Rei","7":"Rei","releases":[{"0":"4301","vim_version":"7.3","1":"7.3","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"vim-moncf-0.1.zip","4":"vim-moncf-0.1.zip","src_id":"18949","5":"18949","creation_date":"1352131831","6":"1352131831"}]},"4300":{"script_id":"4300","0":"4300","script_name":"eunuch.vim","1":"eunuch.vim","script_type":"utility","2":"utility","summary":"Helpers for UNIX","3":"Helpers for UNIX","description":"Vim sugar for the UNIX shell commands that need it the most.  Commands include:\r\n\r\n* :Unlink: Delete a buffer and the file on disk simultaneously.\r\n* :Remove: Like :Unlink, but doesn't require a neckbeard.\r\n* :Move: Rename a buffer and the file on disk simultaneously.\r\n* :Chmod: Change the permissions of the current file.\r\n* :Find: Run `find` and load the results into the quickfix list.\r\n* :Locate: Run `locate` and load the results into the quickfix list.\r\n* :SudoWrite: Write a privileged file with sudo.\r\n* :Wall: Write every open window.  Handy for kicking off test autorunners.\r\n\r\nhttps:\/\/github.com\/tpope\/vim-eunuch","4":"Vim sugar for the UNIX shell commands that need it the most.  Commands include:\r\n\r\n* :Unlink: Delete a buffer and the file on disk simultaneously.\r\n* :Remove: Like :Unlink, but doesn't require a neckbeard.\r\n* :Move: Rename a buffer and the file on disk simultaneously.\r\n* :Chmod: Change the permissions of the current file.\r\n* :Find: Run `find` and load the results into the quickfix list.\r\n* :Locate: Run `locate` and load the results into the quickfix list.\r\n* :SudoWrite: Write a privileged file with sudo.\r\n* :Wall: Write every open window.  Handy for kicking off test autorunners.\r\n\r\nhttps:\/\/github.com\/tpope\/vim-eunuch","install_details":"Extract in ~\/.vim (~\\vimfiles on Windows).","5":"Extract in ~\/.vim (~\\vimfiles on Windows).","first_name":"Tim","6":"Tim","last_name":"Pope","7":"Pope","releases":[{"0":"4300","vim_version":"7.4","1":"7.4","script_version":"1.3","2":"1.3","version_comment":"Re-detect 'filetype' after typing a shebang line.\r\nFill in blank shebang line based on current 'filetype'.\r\nSupport :Move and :Rename in new files.\r\nProvide :Copy and :Duplicate.\r\nSupport :Delete and :Remove in empty directories.\r\nRequire ! when :Delete or :Remove can't be undone.\r\nProvide User autocommand events for :Chmod and :Remove.\r\nAlways create parent directories on :Mkdir (like `mkdir -p`).\r\nRun BufReadPre and Post autocmds for :SudoEdit.\r\nResolve symlinks in :SudoEdit, as required by sudo -e.\r\nSupport :SudoEdit and :SudoWrite with ! in 'guioptions'.\r\nDrop defunct support for SUDO_COMMAND filetype detection.\r\nDrop defunct support for skeleton init script.\r\nBump minimum Vim version to 7.4.\r\nBug fixes.","3":"Re-detect 'filetype' after typing a shebang line.\r\nFill in blank shebang line based on current 'filetype'.\r\nSupport :Move and :Rename in new files.\r\nProvide :Copy and :Duplicate.\r\nSupport :Delete and :Remove in empty directories.\r\nRequire ! when :Delete or :Remove can't be undone.\r\nProvide User autocommand events for :Chmod and :Remove.\r\nAlways create parent directories on :Mkdir (like `mkdir -p`).\r\nRun BufReadPre and Post autocmds for :SudoEdit.\r\nResolve symlinks in :SudoEdit, as required by sudo -e.\r\nSupport :SudoEdit and :SudoWrite with ! in 'guioptions'.\r\nDrop defunct support for SUDO_COMMAND filetype detection.\r\nDrop defunct support for skeleton init script.\r\nBump minimum Vim version to 7.4.\r\nBug fixes.","package":"eunuch.zip","4":"eunuch.zip","src_id":"28033","5":"28033","creation_date":"1651841522","6":"1651841522"},{"0":"4300","vim_version":"7.0","1":"7.0","script_version":"1.2","2":"1.2","version_comment":"Don't delete buffer after :Unlink\/:Remove.\r\nIntroduce :Delete to delete both file and buffer.\r\nReplace :Find and :Locate with :Cfind\/:Lfind and :Clocate\/:Llocate.\r\nPre-populate new \/etc\/init.d scripts from \/etc\/init.d\/skeleton.\r\nUse setfperm() rather than :!chmod for simple cases.\r\nUse sudo -A to prompt for password in GUI.\r\nRe-detect filetype after :Move\/:Rename.\r\nSupport virtual buffers, such as from Fugitive.\r\nBug fixes.","3":"Don't delete buffer after :Unlink\/:Remove.\r\nIntroduce :Delete to delete both file and buffer.\r\nReplace :Find and :Locate with :Cfind\/:Lfind and :Clocate\/:Llocate.\r\nPre-populate new \/etc\/init.d scripts from \/etc\/init.d\/skeleton.\r\nUse setfperm() rather than :!chmod for simple cases.\r\nUse sudo -A to prompt for password in GUI.\r\nRe-detect filetype after :Move\/:Rename.\r\nSupport virtual buffers, such as from Fugitive.\r\nBug fixes.","package":"eunuch.zip","4":"eunuch.zip","src_id":"26176","5":"26176","creation_date":"1533918045","6":"1533918045"},{"0":"4300","vim_version":"7.0","1":"7.0","script_version":"1.1","2":"1.1","version_comment":"Provide :Mkdir.\r\nAutomatic mkdir in :Move and :Rename.\r\nMake :Rename relative to containing directory.\r\nFix :Chmod error.\r\nRename :W to :Wall.\r\nSkip unwritable buffers in :Wall.\r\nProvide :SudoEdit.\r\nShow password prompt for sudo in GUI.\r\nBetter filetype detection for files edited with with sudoedit.\r\nSupport old Vim without fnameescape.","3":"Provide :Mkdir.\r\nAutomatic mkdir in :Move and :Rename.\r\nMake :Rename relative to containing directory.\r\nFix :Chmod error.\r\nRename :W to :Wall.\r\nSkip unwritable buffers in :Wall.\r\nProvide :SudoEdit.\r\nShow password prompt for sudo in GUI.\r\nBetter filetype detection for files edited with with sudoedit.\r\nSupport old Vim without fnameescape.","package":"eunuch.zip","4":"eunuch.zip","src_id":"21847","5":"21847","creation_date":"1398876512","6":"1398876512"},{"0":"4300","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"eunuch.zip","4":"eunuch.zip","src_id":"18948","5":"18948","creation_date":"1352086351","6":"1352086351"}]},"4299":{"script_id":"4299","0":"4299","script_name":"Vim bookmark","1":"Vim bookmark","script_type":"utility","2":"utility","summary":"A bookmark plugin","3":"A bookmark plugin","description":"See https:\/\/github.com\/name5566\/vim-bookmark for details.","4":"See https:\/\/github.com\/name5566\/vim-bookmark for details.","install_details":"","5":"","first_name":"Guodong","6":"Guodong","last_name":"Liang","7":"Liang","releases":[{"0":"4299","vim_version":"7.2","1":"7.2","script_version":"0.3.0","2":"0.3.0","version_comment":"add bookmark group.","3":"add bookmark group.","package":"vbookmark.vim","4":"vbookmark.vim","src_id":"18943","5":"18943","creation_date":"1352017483","6":"1352017483"},{"0":"4299","vim_version":"7.2","1":"7.2","script_version":"0.2.4","2":"0.2.4","version_comment":"Bugfix to restore the bookmark file.\r\nBugfix to jump a file does not exist.","3":"Bugfix to restore the bookmark file.\r\nBugfix to jump a file does not exist.","package":"vbookmark.vim","4":"vbookmark.vim","src_id":"18937","5":"18937","creation_date":"1351830103","6":"1351830103"},{"0":"4299","vim_version":"7.2","1":"7.2","script_version":"0.2.3","2":"0.2.3","version_comment":"Initial upload","3":"Initial upload","package":"vbookmark.vim","4":"vbookmark.vim","src_id":"18929","5":"18929","creation_date":"1351689239","6":"1351689239"}]},"4298":{"script_id":"4298","0":"4298","script_name":"vimside","1":"vimside","script_type":"utility","2":"utility","summary":"Vimside - Vim Scala Ide","3":"Vimside - Vim Scala Ide","description":"\r\nThis is the alpha release of Vimside (Vim Scala IDE).  Vimside is\r\nbuilt upon the ENSIME server: github: https:\/\/github.com\/aemoncannon\/ensime\r\nmanual: http:\/\/aemoncannon.github.com\/ensime\/index.html\r\n\r\nTwo outstanding Ensime features to be implemented are more\r\nregression tests and debugging. I also hope to port the latest\r\nverion of InSynth over to Ensime.\r\n\r\nWith this release there has been added the ActWin (Action Window)\r\nwhich can be used to display compile errors (generated by either\r\nEnsime or SBT) (a quickfix window replacement) and the result of\r\nthe command \"use-of-symbol-at-point\" can use the ActWin (rather\r\nthan quickfix window). The ActWin is highly configurable.\r\nAlso, User and Project Options can now be defined\r\nin Java-like properties files (rather than in the option.vim files).\r\nBy default the\r\n\r\nWith previous releases a variable at bottom of the plugin\/vimside.vim file\r\nhave been added which allows one to turn on logging during Vimside Option\r\nloading. For the Vimside logger, Options must first be loaded\r\nin order to configure it. Thus, no logging when loading Options.\r\nSo, I added a non-configurable logger that only logs in the\r\nvimside#options#manager.vim file. Hopefully, this will help\r\nusers figure out whats happening during option loading.\r\n\r\nAlso, the example project code has been moved under the directory\r\ndata\/vimside\/projects - since there are now two example projects\r\nand will be a couple more in the future. Additionally, the tests\r\nhave been moved under data\/vimside\/tests. I will be adding more\r\nunit\/regression tests in the future.\r\n\r\nI expect to continue to update the sources on github frequently, flushing\r\nout the features.  https:\/\/github.com\/megaannum\/vimside\r\n\r\nVimside communicates with the Ensime server using Shougo vimproc\r\n( git:\/\/github.com\/Shougo\/vimproc ),\r\na very clean and elegant C-language binding to sockets (and also pipes,\r\nptys, files, etc.).  Vimside also uses Shougo vimshell to launch and\r\ncommunicate with the Scala Repl.\r\n\r\nThe current pre-alpha has only be run against the Ensime pre-built\r\nensime_2.9.2-0.9.8.9.tar.gz and ensime_2.10.0-0.9.8.9.tar.gz\r\ndownloads.\r\n\r\nLook at the plugin\/vimside.vim file for key mappings: how to start the\r\nEnsime server and the currently supported commands.\r\n\r\nFeatures:\r\n\r\nVimside is based upon Ensime and, as a result, at the core of Vimside\r\nare the capabilities of Ensime. These are reflected in the Ensime\r\ncommands supported by Vimside. The full set of Emacs Ensime commands\r\nand key bindings can be found in comments in the Vimside file\r\nplugin\/Vimside.vim. Of those commands, those with Vim key mappings\r\nare also in that file and they, basically, reflect that part of Ensime\r\nthat is currently implemented in Vimside. I mirrored the Vim key\r\nmappings to reflect the Emacs-Ensime key bindings but the user is free\r\nto define their own mappings. At the top of the Vimside plugin file\r\nthere is code that will source a file called 'plugin_user.vim' located\r\nin the Vimside 'data' directory: ..\/data\/vimside\/plugin_user.vim\r\ninstead of the plugin file if it exists.\r\n\r\nCurrent Supported Ensime Commands:\r\n\r\n  Start Ensime\r\n    This makes sure that the current environment and Option settings are\r\n    correct and then launches the Ensime backend server. The Ensime server\r\n    writes a file where it puts the socket port that its client should use.\r\n    Vimside reads that file, gets the port number, and provides Ensime\r\n    with configuration information.\r\n\r\n  Stop Ensime\r\n    There is also an autocmd that will kill the Ensime server when the\r\n    user exists Vim.\r\n\r\n  Map <Tab> to Omni-Code Completion in insert mode\r\n    This mapping maybe overridden by the mapping is some other plugin\r\n    (like a snipmate binding), So, if it does not seem to work for you\r\n    list the current mappings and see what is overriding it.\r\n    Very Useful.\r\n\r\n  Symbol At Point\r\n    With cursor on variable, jump to the definition of its symbol.\r\n    One can easily jump back and forth.\r\n    The Emacs key binding uses the Meta key. In GVim I could get this\r\n    to work and so in GVim the key mapping mirrors the Emacs Ensime\r\n    key binding. But, with Vim in an XTerm, I could not get the Meta\/Alt\r\n    key to be recognized (and there is NO single place where there is\r\n    a definitive, failsafe guide for getting Meta\/Alt key mappings to\r\n    work, so I have a different binding for Vim.\r\n    Very useful.\r\n    Implementations: 1\r\n\r\n  Selection Expand\/Contract\r\n    Select the surrounding syntactic context and easily shrink\/grow the\r\n    selection.\r\n    Implementations: 2\r\n\r\n  Global Public Search\r\n    Search for method or types through project code using space separated\r\n    search terms.\r\n    Useful.\r\n    Implementations: 1\r\n\r\n  Hover To Symbol\r\n    Place cursor (or mouse) over a variable and its Symbol will be\r\n    displayed.\r\n    Cute but requires frequent server polling.\r\n    Implementations: 3\r\n\r\n  Open Browser Info\r\n    With cursor over Scala\/Java variable, type, etc. invoke the associated\r\n    on-line web api documentation (if it exists).\r\n    Useful.\r\n    Implementations: 1\r\n\r\n  Use of Symbol At Point\r\n    List all references to the symbol under the cursor.\r\n    Very useful.\r\n    Implementations: 1\r\n\r\n  SBT Command-Line\r\n    Switch to the sbt command-line (works for sbt projects only)\r\n    Implementations: 2\r\n\r\n  Launch Repl\r\n    Switch to the Scala interpreter, with project classes in the classpath.\r\n    TBD: cut\/paste code fragments into Repl.\r\n    Implementations: 1\r\n\r\n  Typecheck Current File\r\n    Typecheck the current file and display errors and warnings.\r\n    Very useful.\r\n    Implementations: 1\r\n\r\n  Typecheck All Files\r\n    Typecheck the all files and display errors and warnings.\r\n    Very useful.\r\n    Implementations: 1\r\n\r\n  Re-Show Errors\/Warnings\r\n    Show all errors and warnings in the project.\r\n    Very useful.\r\n    Implementations: 1\r\n\r\n  Format Source\r\n    Format the current Scala source file.\r\n    Useful.\r\n    Implementations: 1\r\n\r\n  Refactoring\r\n    Rename the symbol at point.\r\n    Organize imports.\r\n    Extract local.\r\n    Extract method.\r\n    Inline local.\r\n    Add import for type at point.\r\n    Import suggestions\r\n    Useful.\r\n    Implementations: 1\r\n\r\n  Building\r\n    Build the entire project.\r\n    Rebuild the project incrementally.\r\n    Useful.\r\n    Implementations: 1\r\n\r\n  Popup Menu\r\n    Bring up Popup menu with all Vimside commands (requires Forms library).\r\n    Useful for folks who have not yet learned the key mappings.\r\n    Implementations: 1\r\n\r\n  Browse Source Roots\r\n    Directory browser of project sources (project code base).\r\n    Implementations: 2\r\n\r\n  Browse Reference Source Roots\r\n    Directory browser of project reference sources (Java and Scala libraries).\r\n    Implementations: 2\r\n\r\n  Option Viewer\/Editor\r\n    Bring up the Option Viewer\/Editor (requires Forms library). Lets one\r\n    see all of the Vimside configurable Options and their current value.\r\n    To be implemented will be an Editor allowing for the modification of\r\n    some \"dynamic\" Options at runtime.\r\n    Implementations: 1\r\n\r\n  Completions\r\n    OmmiCompletions using <c-x><c-o>.\r\n    Very Useful.\r\n    Implementations: 1\r\n\r\n  Package Inspector\r\n    Inspect imported package, current file's package and the package\r\n    specified in the ensime configuration ':package'.\r\n    Very Useful.\r\n    Implementations: 1\r\n\r\n  Type Inspector\r\n    Click on type and see information, Click on information and see its\r\n    information. Move about Inspector history.\r\n    Very Useful.\r\n    Implementations: 1\r\n\r\nEnsime Capabilities to be Supported:\r\n\r\n  Scalex\r\n    Seems to be a dead project (see: http:\/\/scalex.org\/)\r\n\r\n  Run Application\r\n\r\n  Debug Application\r\n    Start and run the debugger.\r\n    Start and run the debugger.\r\n    Set a breakpoint.\r\n    Clear a breakpoint.\r\n    Step.\r\n    Step over.\r\n    Step out.\r\n    Continue from a breakpoint.\r\n    Kill the debug session.\r\n    Inspect the local variable at cursor.\r\n    Show backtrace.\r\n\r\n  And others\r\n\r\nKey Mappings\r\n  \" Start Ensime\r\n  if has(\"gui_running\")\r\n    <m-x>\r\n  else\r\n    <Leader>vs\r\n  endif\r\n  \" Stop Vimside\r\n  <Leader>vS\r\n\r\n  \" TAB\r\n  \"   Start completing a method\/variable.\r\n  <tab>\r\n\r\n  \" Inspect the type of the expression under the cursor.\r\n  <Leader>ti\r\n  \" Inspect package at point\r\n  <Leader>tp\r\n  \" Inspect the project package if set in envime configure file.\r\n  <Leader>to\r\n\r\n\r\n  \" M-. (dot)\r\n  \"   Jump to definition of symbol under cursor.\r\n  \"   Note that the Meta\/Alt keys, while easy to use with GVim, are,\r\n  \"   at best, an advanture and, at worst, impossible, to get working\r\n  \"   with non-GVim - thus the mapping is different for non-gui-running.\r\n  if has(\"gui_running\")\r\n    <m-.>\r\n  else\r\n    <Leader>m.\r\n  endif\r\n\r\n  \" M-, (comma)\r\n  \"   Pop back to previously visited position.\r\n  if has(\"gui_running\")\r\n    <m-,>\r\n  else\r\n    <Leader>m,\r\n  endif\r\n\r\n  \" Select the surrounding syntactic context. Subsequent taps of '.'\r\n  \"   and ',' will grow and shrink the selection, respectively.\r\n  <Leader>v.\r\n  <Leader>v,\r\n\r\n  \" Search globally for methods or types.\r\n  <Leader>vv\r\n\r\n  \" Scalex search for methods or types.\r\n  \" NOT IMPLEMENTED YET\r\n\r\n  \" Show (web api) documentation for symbol at point\r\n  <Leader>vt\r\n\r\n  \" Mouse Hover\r\n  \"   Echo the type of the expression under the cursor.\r\n  <Leader>vh\r\n\r\n  \"   Inspect the package of the current source file.\r\n  \" NOT IMPLEMENTED YET\r\n\r\n  \" List all references to the symbol under the cursor.\r\n  <Leader>vr\r\n\r\n  \" Switch to the sbt command-line (works for sbt projects only)\r\n  \"     s sbt switch\r\n  <Leader>ss\r\n  \" sbt do compile\r\n  <Leader>sc\r\n  \" sbt do clean\r\n  <Leader>sn\r\n  \" sbt do package\r\n  <Leader>sp\r\n  \" sbt do exit\r\n  <Leader>se\r\n\r\n  \" invoke the sbt command interpreter\r\n  <Leader>si\r\n\r\n  \" Switch to the scala interpreter, with project classes in the classpath.\r\n  <Leader>vz\r\n\r\n  \" Typecheck the current file.\r\n  <Leader>vc\r\n\r\n  \" Typecheck all files in the project.\r\n  <Leader>va\r\n\r\n  \" (Re-)Show all errors and warnings in the project.\r\n  <Leader>ve\r\n\r\n  \" Format the current Scala source file.\r\n  <Leader>vf\r\n\r\n  \" Undo a refactoring or formatting change.\r\n  \" NOT IMPLEMENTED YET\r\n\r\n  \" Go to the next compilation note in the current buffer.\r\n  \" NOT IMPLEMENTED YET\r\n\r\n  \" C-c C-d x\r\n  \"   Where x is one of:\r\n  \"     d Start and run the debugger.\r\n  \"     r Start and run the debugger.\r\n  \"     b Set a breakpoint.\r\n  \"     u Clear a breakpoint.\r\n  \"     s Step.\r\n  \"     n Step over.\r\n  \"     o Step out.\r\n  \"     c Continue from a breakpoint.\r\n  \"     q Kill the debug session.\r\n  \"     i Inspect the local variable at cursor.\r\n  \"     t Show backtrace.\r\n  \"     a Clear all breakes\r\n  \" NOT IMPLEMENTED YET\r\n\r\n  \"   Where x is one of:\r\n  \"     r Rename the symbol at point.\r\n  <Leader>rr\r\n  \"     o Organize imports.\r\n  <Leader>ro\r\n  \"     l Extract local.\r\n  <Leader>rl\r\n  \"     m Extract method.\r\n  <Leader>rm\r\n  \"     i Inline local.\r\n  <Leader>ri\r\n  \"     t Add import for type at point.\r\n  <Leader>rt\r\n\r\n  \" Import suggestions\r\n  <Leader>vi\r\n\r\n  \"   Where x is one of:\r\n  \"     b Build the entire project.\r\n  \"     r Rebuild the project, incrementally.\r\n  <Leader>vbb\r\n  <Leader>vbr\r\n\r\n  \" Reload the .ensime file and recompile the project. Useful if you hit\r\n  \"   a server bug.\r\n  \" NOT IMPLEMENTED YET\r\n\r\n  \" Start the automatic configuration file generator.\r\n  \" NOT IMPLEMENTED YET\r\n\r\n  \" Make PopUp\r\n  <Leader>vp\r\n\r\n  \" browse source roots\r\n  <Leader>vBs\r\n  \" browse referenct source roots\r\n  <Leader>vBr\r\n\r\n  \" option editor\r\n  <Leader>voe\r\n\r\n\r\n","4":"\r\nThis is the alpha release of Vimside (Vim Scala IDE).  Vimside is\r\nbuilt upon the ENSIME server: github: https:\/\/github.com\/aemoncannon\/ensime\r\nmanual: http:\/\/aemoncannon.github.com\/ensime\/index.html\r\n\r\nTwo outstanding Ensime features to be implemented are more\r\nregression tests and debugging. I also hope to port the latest\r\nverion of InSynth over to Ensime.\r\n\r\nWith this release there has been added the ActWin (Action Window)\r\nwhich can be used to display compile errors (generated by either\r\nEnsime or SBT) (a quickfix window replacement) and the result of\r\nthe command \"use-of-symbol-at-point\" can use the ActWin (rather\r\nthan quickfix window). The ActWin is highly configurable.\r\nAlso, User and Project Options can now be defined\r\nin Java-like properties files (rather than in the option.vim files).\r\nBy default the\r\n\r\nWith previous releases a variable at bottom of the plugin\/vimside.vim file\r\nhave been added which allows one to turn on logging during Vimside Option\r\nloading. For the Vimside logger, Options must first be loaded\r\nin order to configure it. Thus, no logging when loading Options.\r\nSo, I added a non-configurable logger that only logs in the\r\nvimside#options#manager.vim file. Hopefully, this will help\r\nusers figure out whats happening during option loading.\r\n\r\nAlso, the example project code has been moved under the directory\r\ndata\/vimside\/projects - since there are now two example projects\r\nand will be a couple more in the future. Additionally, the tests\r\nhave been moved under data\/vimside\/tests. I will be adding more\r\nunit\/regression tests in the future.\r\n\r\nI expect to continue to update the sources on github frequently, flushing\r\nout the features.  https:\/\/github.com\/megaannum\/vimside\r\n\r\nVimside communicates with the Ensime server using Shougo vimproc\r\n( git:\/\/github.com\/Shougo\/vimproc ),\r\na very clean and elegant C-language binding to sockets (and also pipes,\r\nptys, files, etc.).  Vimside also uses Shougo vimshell to launch and\r\ncommunicate with the Scala Repl.\r\n\r\nThe current pre-alpha has only be run against the Ensime pre-built\r\nensime_2.9.2-0.9.8.9.tar.gz and ensime_2.10.0-0.9.8.9.tar.gz\r\ndownloads.\r\n\r\nLook at the plugin\/vimside.vim file for key mappings: how to start the\r\nEnsime server and the currently supported commands.\r\n\r\nFeatures:\r\n\r\nVimside is based upon Ensime and, as a result, at the core of Vimside\r\nare the capabilities of Ensime. These are reflected in the Ensime\r\ncommands supported by Vimside. The full set of Emacs Ensime commands\r\nand key bindings can be found in comments in the Vimside file\r\nplugin\/Vimside.vim. Of those commands, those with Vim key mappings\r\nare also in that file and they, basically, reflect that part of Ensime\r\nthat is currently implemented in Vimside. I mirrored the Vim key\r\nmappings to reflect the Emacs-Ensime key bindings but the user is free\r\nto define their own mappings. At the top of the Vimside plugin file\r\nthere is code that will source a file called 'plugin_user.vim' located\r\nin the Vimside 'data' directory: ..\/data\/vimside\/plugin_user.vim\r\ninstead of the plugin file if it exists.\r\n\r\nCurrent Supported Ensime Commands:\r\n\r\n  Start Ensime\r\n    This makes sure that the current environment and Option settings are\r\n    correct and then launches the Ensime backend server. The Ensime server\r\n    writes a file where it puts the socket port that its client should use.\r\n    Vimside reads that file, gets the port number, and provides Ensime\r\n    with configuration information.\r\n\r\n  Stop Ensime\r\n    There is also an autocmd that will kill the Ensime server when the\r\n    user exists Vim.\r\n\r\n  Map <Tab> to Omni-Code Completion in insert mode\r\n    This mapping maybe overridden by the mapping is some other plugin\r\n    (like a snipmate binding), So, if it does not seem to work for you\r\n    list the current mappings and see what is overriding it.\r\n    Very Useful.\r\n\r\n  Symbol At Point\r\n    With cursor on variable, jump to the definition of its symbol.\r\n    One can easily jump back and forth.\r\n    The Emacs key binding uses the Meta key. In GVim I could get this\r\n    to work and so in GVim the key mapping mirrors the Emacs Ensime\r\n    key binding. But, with Vim in an XTerm, I could not get the Meta\/Alt\r\n    key to be recognized (and there is NO single place where there is\r\n    a definitive, failsafe guide for getting Meta\/Alt key mappings to\r\n    work, so I have a different binding for Vim.\r\n    Very useful.\r\n    Implementations: 1\r\n\r\n  Selection Expand\/Contract\r\n    Select the surrounding syntactic context and easily shrink\/grow the\r\n    selection.\r\n    Implementations: 2\r\n\r\n  Global Public Search\r\n    Search for method or types through project code using space separated\r\n    search terms.\r\n    Useful.\r\n    Implementations: 1\r\n\r\n  Hover To Symbol\r\n    Place cursor (or mouse) over a variable and its Symbol will be\r\n    displayed.\r\n    Cute but requires frequent server polling.\r\n    Implementations: 3\r\n\r\n  Open Browser Info\r\n    With cursor over Scala\/Java variable, type, etc. invoke the associated\r\n    on-line web api documentation (if it exists).\r\n    Useful.\r\n    Implementations: 1\r\n\r\n  Use of Symbol At Point\r\n    List all references to the symbol under the cursor.\r\n    Very useful.\r\n    Implementations: 1\r\n\r\n  SBT Command-Line\r\n    Switch to the sbt command-line (works for sbt projects only)\r\n    Implementations: 2\r\n\r\n  Launch Repl\r\n    Switch to the Scala interpreter, with project classes in the classpath.\r\n    TBD: cut\/paste code fragments into Repl.\r\n    Implementations: 1\r\n\r\n  Typecheck Current File\r\n    Typecheck the current file and display errors and warnings.\r\n    Very useful.\r\n    Implementations: 1\r\n\r\n  Typecheck All Files\r\n    Typecheck the all files and display errors and warnings.\r\n    Very useful.\r\n    Implementations: 1\r\n\r\n  Re-Show Errors\/Warnings\r\n    Show all errors and warnings in the project.\r\n    Very useful.\r\n    Implementations: 1\r\n\r\n  Format Source\r\n    Format the current Scala source file.\r\n    Useful.\r\n    Implementations: 1\r\n\r\n  Refactoring\r\n    Rename the symbol at point.\r\n    Organize imports.\r\n    Extract local.\r\n    Extract method.\r\n    Inline local.\r\n    Add import for type at point.\r\n    Import suggestions\r\n    Useful.\r\n    Implementations: 1\r\n\r\n  Building\r\n    Build the entire project.\r\n    Rebuild the project incrementally.\r\n    Useful.\r\n    Implementations: 1\r\n\r\n  Popup Menu\r\n    Bring up Popup menu with all Vimside commands (requires Forms library).\r\n    Useful for folks who have not yet learned the key mappings.\r\n    Implementations: 1\r\n\r\n  Browse Source Roots\r\n    Directory browser of project sources (project code base).\r\n    Implementations: 2\r\n\r\n  Browse Reference Source Roots\r\n    Directory browser of project reference sources (Java and Scala libraries).\r\n    Implementations: 2\r\n\r\n  Option Viewer\/Editor\r\n    Bring up the Option Viewer\/Editor (requires Forms library). Lets one\r\n    see all of the Vimside configurable Options and their current value.\r\n    To be implemented will be an Editor allowing for the modification of\r\n    some \"dynamic\" Options at runtime.\r\n    Implementations: 1\r\n\r\n  Completions\r\n    OmmiCompletions using <c-x><c-o>.\r\n    Very Useful.\r\n    Implementations: 1\r\n\r\n  Package Inspector\r\n    Inspect imported package, current file's package and the package\r\n    specified in the ensime configuration ':package'.\r\n    Very Useful.\r\n    Implementations: 1\r\n\r\n  Type Inspector\r\n    Click on type and see information, Click on information and see its\r\n    information. Move about Inspector history.\r\n    Very Useful.\r\n    Implementations: 1\r\n\r\nEnsime Capabilities to be Supported:\r\n\r\n  Scalex\r\n    Seems to be a dead project (see: http:\/\/scalex.org\/)\r\n\r\n  Run Application\r\n\r\n  Debug Application\r\n    Start and run the debugger.\r\n    Start and run the debugger.\r\n    Set a breakpoint.\r\n    Clear a breakpoint.\r\n    Step.\r\n    Step over.\r\n    Step out.\r\n    Continue from a breakpoint.\r\n    Kill the debug session.\r\n    Inspect the local variable at cursor.\r\n    Show backtrace.\r\n\r\n  And others\r\n\r\nKey Mappings\r\n  \" Start Ensime\r\n  if has(\"gui_running\")\r\n    <m-x>\r\n  else\r\n    <Leader>vs\r\n  endif\r\n  \" Stop Vimside\r\n  <Leader>vS\r\n\r\n  \" TAB\r\n  \"   Start completing a method\/variable.\r\n  <tab>\r\n\r\n  \" Inspect the type of the expression under the cursor.\r\n  <Leader>ti\r\n  \" Inspect package at point\r\n  <Leader>tp\r\n  \" Inspect the project package if set in envime configure file.\r\n  <Leader>to\r\n\r\n\r\n  \" M-. (dot)\r\n  \"   Jump to definition of symbol under cursor.\r\n  \"   Note that the Meta\/Alt keys, while easy to use with GVim, are,\r\n  \"   at best, an advanture and, at worst, impossible, to get working\r\n  \"   with non-GVim - thus the mapping is different for non-gui-running.\r\n  if has(\"gui_running\")\r\n    <m-.>\r\n  else\r\n    <Leader>m.\r\n  endif\r\n\r\n  \" M-, (comma)\r\n  \"   Pop back to previously visited position.\r\n  if has(\"gui_running\")\r\n    <m-,>\r\n  else\r\n    <Leader>m,\r\n  endif\r\n\r\n  \" Select the surrounding syntactic context. Subsequent taps of '.'\r\n  \"   and ',' will grow and shrink the selection, respectively.\r\n  <Leader>v.\r\n  <Leader>v,\r\n\r\n  \" Search globally for methods or types.\r\n  <Leader>vv\r\n\r\n  \" Scalex search for methods or types.\r\n  \" NOT IMPLEMENTED YET\r\n\r\n  \" Show (web api) documentation for symbol at point\r\n  <Leader>vt\r\n\r\n  \" Mouse Hover\r\n  \"   Echo the type of the expression under the cursor.\r\n  <Leader>vh\r\n\r\n  \"   Inspect the package of the current source file.\r\n  \" NOT IMPLEMENTED YET\r\n\r\n  \" List all references to the symbol under the cursor.\r\n  <Leader>vr\r\n\r\n  \" Switch to the sbt command-line (works for sbt projects only)\r\n  \"     s sbt switch\r\n  <Leader>ss\r\n  \" sbt do compile\r\n  <Leader>sc\r\n  \" sbt do clean\r\n  <Leader>sn\r\n  \" sbt do package\r\n  <Leader>sp\r\n  \" sbt do exit\r\n  <Leader>se\r\n\r\n  \" invoke the sbt command interpreter\r\n  <Leader>si\r\n\r\n  \" Switch to the scala interpreter, with project classes in the classpath.\r\n  <Leader>vz\r\n\r\n  \" Typecheck the current file.\r\n  <Leader>vc\r\n\r\n  \" Typecheck all files in the project.\r\n  <Leader>va\r\n\r\n  \" (Re-)Show all errors and warnings in the project.\r\n  <Leader>ve\r\n\r\n  \" Format the current Scala source file.\r\n  <Leader>vf\r\n\r\n  \" Undo a refactoring or formatting change.\r\n  \" NOT IMPLEMENTED YET\r\n\r\n  \" Go to the next compilation note in the current buffer.\r\n  \" NOT IMPLEMENTED YET\r\n\r\n  \" C-c C-d x\r\n  \"   Where x is one of:\r\n  \"     d Start and run the debugger.\r\n  \"     r Start and run the debugger.\r\n  \"     b Set a breakpoint.\r\n  \"     u Clear a breakpoint.\r\n  \"     s Step.\r\n  \"     n Step over.\r\n  \"     o Step out.\r\n  \"     c Continue from a breakpoint.\r\n  \"     q Kill the debug session.\r\n  \"     i Inspect the local variable at cursor.\r\n  \"     t Show backtrace.\r\n  \"     a Clear all breakes\r\n  \" NOT IMPLEMENTED YET\r\n\r\n  \"   Where x is one of:\r\n  \"     r Rename the symbol at point.\r\n  <Leader>rr\r\n  \"     o Organize imports.\r\n  <Leader>ro\r\n  \"     l Extract local.\r\n  <Leader>rl\r\n  \"     m Extract method.\r\n  <Leader>rm\r\n  \"     i Inline local.\r\n  <Leader>ri\r\n  \"     t Add import for type at point.\r\n  <Leader>rt\r\n\r\n  \" Import suggestions\r\n  <Leader>vi\r\n\r\n  \"   Where x is one of:\r\n  \"     b Build the entire project.\r\n  \"     r Rebuild the project, incrementally.\r\n  <Leader>vbb\r\n  <Leader>vbr\r\n\r\n  \" Reload the .ensime file and recompile the project. Useful if you hit\r\n  \"   a server bug.\r\n  \" NOT IMPLEMENTED YET\r\n\r\n  \" Start the automatic configuration file generator.\r\n  \" NOT IMPLEMENTED YET\r\n\r\n  \" Make PopUp\r\n  <Leader>vp\r\n\r\n  \" browse source roots\r\n  <Leader>vBs\r\n  \" browse referenct source roots\r\n  <Leader>vBr\r\n\r\n  \" option editor\r\n  <Leader>voe\r\n\r\n\r\n","install_details":"There are two ways to install Vimside: 1) the traditional Vim manual\r\ndownload-the-zip-file and manual download-all-dependency-zip-files\r\nand unzip everything in the right place and 2) use a third-party\r\nplugin manager. I would recommend using a plugin manager since you are\r\nnotified when updates are available and its just plain easier to to\r\ninstalls and updates with such a manager.\r\n\r\nOne must also install Ensime, the backend compilation server:\r\nhttps:\/\/github.com\/aemoncannon\/ensime\/\r\nThis is discussed below under \"Ensime Install\"\r\n\r\nAfter installing Vimside and directory layout should look like:\r\n\r\n    $HOME\/.vim\/\r\n      autoload\/\r\n        vimside.vim\r\n        vimside\/\r\n          \" vimside code\r\n      data\/\r\n        \" data that persists between invocations of a plugin\r\n        vimside\/\r\n            \" examples, local test Scala\/Java source tree\r\n      doc\/\r\n        vimside.txt\r\n      plugin\/\r\n        vimside.vim\r\n\r\n\r\n== Vim.org Install Plugin:\r\n\r\nAnyway, to get the Vimside zip file from vim.org go to\r\nhttp:\/\/www.vim.org\/scripts\/script.php?script_id=4298\r\nand download the latest version. Unzip it in your '.vim'\r\ndirectory (on Linux systems).\r\n\r\n\r\nNow, Vimside depends upon Vimshell and Vimproc.  It is recommended that\r\nyou get the latest releases of these since they both were modified to add\r\nsome support for capabilities identified while creating Vimside. They are\r\nlocated at:\r\nhttps:\/\/github.com\/Shougo\/vimproc\r\nhttps:\/\/github.com\/Shougo\/vimshell\r\nDownload them both and unzip them.\r\n\r\nFor Vimproc, there is an additional step because it includes a C-language\r\nlibrary. You must compile the library for your machine.  Vimproc comes with\r\na number of make-files. Pick the right one and build the library. Since\r\nVimside is for Scala programmers, I expect that building a C-library with\r\na supplied makefile will not be too challenging :-)\r\n\r\nIn addition, Vimside can be configured so that it can use the Vim\r\nForms and Self libraries. The latest version of these can be gotten\r\nfrom github or you can get released versions from vim.org:\r\nhttp:\/\/www.vim.org\/scripts\/script.php?script_id=4150\r\nhttp:\/\/www.vim.org\/scripts\/script.php?script_id=3072\r\n\r\nFor most of the Vimside commands there are associated Options that configure\r\nhow the command can be used. Many such Options allow the user to run one\r\nof multiple possible implementations.  In particular, there might be a\r\n\"native\" Vim, non-Forms-based solution and also a Forms-based solution. The\r\nForms-based solution is built upon \"native\" Vim but requires the downloading\r\nof the above two libraries: Self and Forms. Each such command with multiple\r\nimplementations can be configure individually to use or not use Forms.\r\n\r\nWhat's more, the Forms library allows one to used a popup menu\r\n(useful if you do not know all of the Vimside key-mappings yet).\r\nAnd, it is expected that the package-inspector and the type-inspector\r\nwill only have Forms implementations - how to do a type-inspector\r\notherwise might be a challenge.\r\n\r\n==Githup and Package Manager Install Plugin:\r\n\r\nIf, as a developer, one wants fixes as they appear, one can clone the\r\ngithub {Vimside} repository and, as updates appear, copy the files\r\nover to you Vim home location or you can use a plugin manager.\r\n\r\nVim has a number of third-party plugin managers. If you are using one\r\nyou can configure it to automatically download and install {Vimside}.\r\n\r\nIntalling with vim-addon-manager (VAM)\r\n\r\nFor more information about vim-addon-manager, see [vim-addon-manager](https:\/\/github.com\/MarcWeber\/vim-addon-manager) and [Vim-addon-manager getting started](https:\/\/github.com\/MarcWeber\/vim-addon-manager\/blob\/master\/doc\/vim-addon-manager-getting-started.txt)\r\n\r\nIn your .vimrc, add self as shown below:\r\n\r\n    fun SetupVAM()\r\n\r\n      ...\r\n\r\n      let g:vim_addon_manager = {}\r\n      let g:vim_addon_manager.plugin_sources = {}\r\n\r\n      ....\r\n\r\n      let g:vim_addon_manager.plugin_sources['self'] = {'type': 'git', 'url': 'git:\/\/github.com\/megaannum\/self'}\r\n      let g:vim_addon_manager.plugin_sources['forms'] = {'type': 'git', 'url': 'git:\/\/github.com\/megaannum\/forms'}\r\n      let g:vim_addon_manager.plugin_sources['vimproc'] = {'type': 'git', 'url': 'git:\/\/github.com\/Shougo\/vimproc'}\r\n      let g:vim_addon_manager.plugin_sources['vimshell'] = {'type': 'git', 'url': 'git:\/\/github.com\/Shougo\/vimshell'}\r\n      let g:vim_addon_manager.plugin_sources['ensime'] = {\"type\": \"git\", \"url\": \"git:\/\/github.com\/aemoncannon\/ensime\", \"branch\" : \"scala-2.9\"}\r\n      let g:vim_addon_manager.plugin_sources['vimside'] = {'type': 'git', 'url': 'git:\/\/github.com\/megaannum\/vimside'}\r\n\r\n\r\n      let plugins = [\r\n        \\ 'self',\r\n        \\ 'forms',\r\n        \\ 'vimproc',\r\n        \\ 'vimshell',\r\n        \\ 'ensime',\r\n        \\ 'vimside'\r\n        \\ ]\r\n\r\n      call vam#ActivateAddons(plugins,{'auto_install' : 0})\r\n\r\n      ...\r\n\r\n    endf\r\n    call SetupVAM()\r\n\r\nNote that to use Vimside, the 'self' and 'forms' libraries above are optional.\r\nWith the 'forms' library, Vimside supports additional features such as a\r\npopup-menu of commands and the type and package inspectors (not yet\r\nimplemented).\r\n\r\nAlso, when one downloads Vimproc, you MUST go into the vimproc directory\r\nand build the C-language file 'proc.c' using one of the supplied make files.\r\n\r\nNow start Vim. You will be asked by vim-addon-manager if you would like\r\nto download and install the plugins.\r\n\r\nInstalling with Pathogen:\r\nWith pathogen, you just have to clone all required plugins into your ~\/.vim\/bundle directory. Running the following lines as a bash script will do exactly that.\r\n\r\n    #!\/bin\/bash\r\n\r\n    declare -a repos=(\r\n      \"git:\/\/github.com\/megaannum\/self.git\"\r\n      \"git:\/\/github.com\/megaannum\/forms.git\"\r\n      \"git:\/\/github.com\/Shougo\/vimproc.git\"\r\n      \"git:\/\/github.com\/Shougo\/vimshell.git\"\r\n      \"-b scala-2.9 git:\/\/github.com\/aemoncannon\/ensime.git\"\r\n      \"git:\/\/github.com\/megaannum\/vimside.git\"\r\n    )\r\n\r\n    cd ~\/.vim\/bundle\r\n\r\n    for repo in \"${repos[@]}\"; do\r\n        git clone $repo\r\n    done;\r\n\r\nNote that you also with pathogen have to run *make* on the appropriate make file inside the vimproc plugin directory.\r\n\r\n== Ensime Install\r\n\r\nEnsime can be downloaded from https:\/\/github.com\/aemoncannon\/ensime\r\nand its on-line manual is at: aemoncannon.github.com\/ensime\/index.html\/.\r\n\r\nIn addition, for ENSIME, there are pre-built releases available at:\r\nhttps:\/\/github.com\/aemoncannon\/ensime\/downloads.\r\nI highly recommend getting these (Scala 2.9.2 and\/or 2.10.0)\r\nrather than trying to build the Ensime Scala code yourself.\r\n\r\nEnsime is not a Vim plugin. It is a Scale program. It has to be installed\r\nand built or a pre-build version has to be used. It can be downloaded\r\nfrom:\r\n\r\n    https:\/\/github.com\/aemoncannon\/ensime\r\n\r\nOne can the follow the instructions there and build it.\r\n\r\nI have never done this. Rather, I have downloaded a pre-build bundle.\r\nOne for Scala 2.9 and another for Scala 10.0. These can be found at:\r\n\r\n    https:\/\/www.dropbox.com\/sh\/ryd981hq08swyqr\/V9o9rDvxkS\/ENSIME%20Releases\r\n\r\nThe Ensime build directory has the following layout using\r\nensime_2.9.2-0.9.8.9 as an example:\r\n\r\n    ensime_2.9.2-0.9.8.9\/\r\n        bin\/\r\n        LICENSE\r\n        elisp\/\r\n        lib\/\r\n        README.md\r\n\r\nor ensime_2.10.0-0.9.8.9:\r\n\r\n    ensime_2.10.0-0.9.8.9\/\r\n        bin\/\r\n        elisp\/\r\n        lib\/\r\n        LICENSE\r\n        README.md\r\n\r\nIt is important that the value of the 'vimside-scala-version'\r\nOption agrees with the Ensime build version. For\r\nensime_2.9.2-0.9.8.9 (the default value):\r\n\r\n   call owner.Set(\"vimside-scala-version\", \"2.9.2\")\r\n\r\nor\r\n   vimside.scala.version=2.9.2\r\n\r\nand for ensime_2.10.0-0.9.8.9:\r\n\r\n   call owner.Set(\"vimside-scala-version\", \"2.10.0\")\r\n\r\nor\r\n\r\n   vimside.scala.version=\"2.10.0\"\r\n\r\nThese values can be set in 'data\/vimside\/options_user.vim'.\r\n\r\nIn addition, the version of Java ($JAVA_HOME\/bin\/java -version)\r\nin the window  that runs Vim (or launched GVim) must agree with\r\nthe value of the Option 'vimside-java-version'. This Option\r\nhas the default value of '1.7' and can be set, again, in\r\n'data\/vimside\/options_user.vim':\r\n\r\n  call owner.Set(\"vimside-java-version\", \"1.8\")\r\n\r\nor\r\n\r\n  vimside.java.version=1.8\r\n\r\nHaving built Ensime or downloaded a pre-built package, you must\r\nset an Option in Vimside so that Vimside can locate the script\r\nused to start the Ensime server. To set a Vimside Option, you\r\nmust copy the 'example_options_user.vim' or, when using\r\nproperties, 'example_vimside.properties' located in 'data\/vimside'\r\nto a file called 'options_user.vim' or 'vimside.properties' and edit it.\r\n\r\nThere is two different ways to do this.\r\n\r\nThe first is to set the Option 'ensime-install-path' or\r\nas a Property 'ensime.install.path' to the\r\nlocation of downloaded Ensime source. If you use the VAM plugin manager,\r\nthen Ensime will be in the directory:\r\n\r\n  $HOME\/.vim\/vim-addons\/ensime\r\nor\r\n  $HOME\/vimfiles\/vim-addons\/ensime\r\n\r\nso you would set the Option according\r\n\r\n  call owner.Set(\"ensime-install-path\", $HOME . \"\/.vim\/vim-addons\/ensime\")\r\nor\r\n  call owner.Set(\"ensime-install-path\", $HOME . \"\/vimfiles\/vim-addons\/ensime\")\r\n\r\nor, as a Property,\r\n\r\n  ensime.install.path=$HOME\/.vim\/vim-addons\/ensime\r\nor\r\n  ensime.install.path=$HOME\/vimfiles\/vim-addons\/ensime\r\n\r\nIf installed with pathogen, those paths are\r\n  $HOME\/.vim\/bundle\/ensime\r\nor\r\n  $HOME\/vimfiles\/bundle\/ensime\r\n\r\nThen depending upon the name of the build directory, which is under the\r\n'ensime-install-path' Option value directory location, you would\r\nset the value of the Option 'ensime-dist-dir' or Property\r\n'ensime.dist.dir' to that directory name.  For example:\r\n\r\n    call owner.Set(\"ensime-dist-dir\", \"ensime_2.9.2-0.9.8.9\")\r\nor\r\n    call owner.Set(\"ensime-dist-dir\", \"ensime_2.10.0-0.9.8.9\")\r\n\r\nor, as a Property,\r\n\r\n    ensime.dist.dir=ensime_2.9.2-0.9.8.9\r\nor\r\n    ensime.dist.dir=ensime_2.10.0-0.9.8.9\r\n\r\nAlternatively, you can specify the full path to the ensime distribution\r\nusing the Option 'ensime-dist-path' or Property 'ensime.dist.path'.\r\nAs an example, if you installed an Ensime build package in some Scala\r\ndirectory, you might set the Option as:\r\n\r\n    call owner.Set(\"ensime-dist-path\", $HOME . \"\/scala\/ensime\/ensime_2.9.2-0.9.8.9\")\r\n\r\nor, as a Property,\r\n\r\n    ensime.dist.path=$HOME\/scala\/ensime\/ensime_2.9.2-0.9.8.9\r\n\r\nIf you set the 'ensime-dist-path' ('ensime-dist.path'), it is checked first\r\nand, if it exists, it is used rather than the 'ensime-install-path'\r\nand 'ensime-dist-dir' ('ensime.install.path' and 'ensime.dist.dir')\r\ncombination.\r\n\r\nVimside supports the Ensime SBT commands. With such, there is an additional\r\nlibrary, an SBT Plugin that supports integration with the ENSIME IDE:\r\nhttps:\/\/github.com\/aemoncannon\/ensime-sbt-cmd\r\n\r\n== Vimside Testing\r\n\r\nRECOMMENDED for initial testing:\r\nTo run against test Scala\/Java project, first in data\/vimside directory\r\ncopy example_options_user.vim to options_user.vim.\r\n\r\n  > cd $HOME\/.vim\/data\/vimside\r\n  > \/bin\/cp example_options_user.vim options_user.vim\r\nor\r\n  > \/bin\/cp example_vimside.properties vimside.properties\r\n\r\nThen, in options_user.vim (or vimside.properties) uncomment the\r\nfollowing two lines:\r\n\r\n   call a:option.Set(\"ensime-config-file-name\", \"ensime_config.vim\")\r\n\r\nor, as a Property,\r\n\r\n   ensime.config.file.name=ensime_config.vim\r\n\r\nThis tells Vimside to use the test project code and to use the\r\nensime_config.vim as the source for Ensime Configuration.\r\n\r\nOne can also run Emacs and enter the command to start Ensime.\r\nI sometimes do this just to check-out how Emacs-Ensime does something\r\nthat I am trying to implement in VimL for Vimside.\r\n\r\nLastly, read the doc\/vimside.txt for more complete information.\r\n\r\nAcknowledgements and thanks:\r\nAemon Cannon for writing Ensime.\r\nDaniel Spiewak has a JEdit binding to Ensime and a simply great video\r\nexplaining why a true editor with Ensime is better than an Eclipse\r\nIde (https:\/\/www.youtube.com\/watch?v=cd2LV0xy9G8 MUST SEE)\r\nand usage examples (http:\/\/vimeo.com\/28597033),\r\nSven Eigenbrodt provided the Pathogen installation information.\r\n","5":"There are two ways to install Vimside: 1) the traditional Vim manual\r\ndownload-the-zip-file and manual download-all-dependency-zip-files\r\nand unzip everything in the right place and 2) use a third-party\r\nplugin manager. I would recommend using a plugin manager since you are\r\nnotified when updates are available and its just plain easier to to\r\ninstalls and updates with such a manager.\r\n\r\nOne must also install Ensime, the backend compilation server:\r\nhttps:\/\/github.com\/aemoncannon\/ensime\/\r\nThis is discussed below under \"Ensime Install\"\r\n\r\nAfter installing Vimside and directory layout should look like:\r\n\r\n    $HOME\/.vim\/\r\n      autoload\/\r\n        vimside.vim\r\n        vimside\/\r\n          \" vimside code\r\n      data\/\r\n        \" data that persists between invocations of a plugin\r\n        vimside\/\r\n            \" examples, local test Scala\/Java source tree\r\n      doc\/\r\n        vimside.txt\r\n      plugin\/\r\n        vimside.vim\r\n\r\n\r\n== Vim.org Install Plugin:\r\n\r\nAnyway, to get the Vimside zip file from vim.org go to\r\nhttp:\/\/www.vim.org\/scripts\/script.php?script_id=4298\r\nand download the latest version. Unzip it in your '.vim'\r\ndirectory (on Linux systems).\r\n\r\n\r\nNow, Vimside depends upon Vimshell and Vimproc.  It is recommended that\r\nyou get the latest releases of these since they both were modified to add\r\nsome support for capabilities identified while creating Vimside. They are\r\nlocated at:\r\nhttps:\/\/github.com\/Shougo\/vimproc\r\nhttps:\/\/github.com\/Shougo\/vimshell\r\nDownload them both and unzip them.\r\n\r\nFor Vimproc, there is an additional step because it includes a C-language\r\nlibrary. You must compile the library for your machine.  Vimproc comes with\r\na number of make-files. Pick the right one and build the library. Since\r\nVimside is for Scala programmers, I expect that building a C-library with\r\na supplied makefile will not be too challenging :-)\r\n\r\nIn addition, Vimside can be configured so that it can use the Vim\r\nForms and Self libraries. The latest version of these can be gotten\r\nfrom github or you can get released versions from vim.org:\r\nhttp:\/\/www.vim.org\/scripts\/script.php?script_id=4150\r\nhttp:\/\/www.vim.org\/scripts\/script.php?script_id=3072\r\n\r\nFor most of the Vimside commands there are associated Options that configure\r\nhow the command can be used. Many such Options allow the user to run one\r\nof multiple possible implementations.  In particular, there might be a\r\n\"native\" Vim, non-Forms-based solution and also a Forms-based solution. The\r\nForms-based solution is built upon \"native\" Vim but requires the downloading\r\nof the above two libraries: Self and Forms. Each such command with multiple\r\nimplementations can be configure individually to use or not use Forms.\r\n\r\nWhat's more, the Forms library allows one to used a popup menu\r\n(useful if you do not know all of the Vimside key-mappings yet).\r\nAnd, it is expected that the package-inspector and the type-inspector\r\nwill only have Forms implementations - how to do a type-inspector\r\notherwise might be a challenge.\r\n\r\n==Githup and Package Manager Install Plugin:\r\n\r\nIf, as a developer, one wants fixes as they appear, one can clone the\r\ngithub {Vimside} repository and, as updates appear, copy the files\r\nover to you Vim home location or you can use a plugin manager.\r\n\r\nVim has a number of third-party plugin managers. If you are using one\r\nyou can configure it to automatically download and install {Vimside}.\r\n\r\nIntalling with vim-addon-manager (VAM)\r\n\r\nFor more information about vim-addon-manager, see [vim-addon-manager](https:\/\/github.com\/MarcWeber\/vim-addon-manager) and [Vim-addon-manager getting started](https:\/\/github.com\/MarcWeber\/vim-addon-manager\/blob\/master\/doc\/vim-addon-manager-getting-started.txt)\r\n\r\nIn your .vimrc, add self as shown below:\r\n\r\n    fun SetupVAM()\r\n\r\n      ...\r\n\r\n      let g:vim_addon_manager = {}\r\n      let g:vim_addon_manager.plugin_sources = {}\r\n\r\n      ....\r\n\r\n      let g:vim_addon_manager.plugin_sources['self'] = {'type': 'git', 'url': 'git:\/\/github.com\/megaannum\/self'}\r\n      let g:vim_addon_manager.plugin_sources['forms'] = {'type': 'git', 'url': 'git:\/\/github.com\/megaannum\/forms'}\r\n      let g:vim_addon_manager.plugin_sources['vimproc'] = {'type': 'git', 'url': 'git:\/\/github.com\/Shougo\/vimproc'}\r\n      let g:vim_addon_manager.plugin_sources['vimshell'] = {'type': 'git', 'url': 'git:\/\/github.com\/Shougo\/vimshell'}\r\n      let g:vim_addon_manager.plugin_sources['ensime'] = {\"type\": \"git\", \"url\": \"git:\/\/github.com\/aemoncannon\/ensime\", \"branch\" : \"scala-2.9\"}\r\n      let g:vim_addon_manager.plugin_sources['vimside'] = {'type': 'git', 'url': 'git:\/\/github.com\/megaannum\/vimside'}\r\n\r\n\r\n      let plugins = [\r\n        \\ 'self',\r\n        \\ 'forms',\r\n        \\ 'vimproc',\r\n        \\ 'vimshell',\r\n        \\ 'ensime',\r\n        \\ 'vimside'\r\n        \\ ]\r\n\r\n      call vam#ActivateAddons(plugins,{'auto_install' : 0})\r\n\r\n      ...\r\n\r\n    endf\r\n    call SetupVAM()\r\n\r\nNote that to use Vimside, the 'self' and 'forms' libraries above are optional.\r\nWith the 'forms' library, Vimside supports additional features such as a\r\npopup-menu of commands and the type and package inspectors (not yet\r\nimplemented).\r\n\r\nAlso, when one downloads Vimproc, you MUST go into the vimproc directory\r\nand build the C-language file 'proc.c' using one of the supplied make files.\r\n\r\nNow start Vim. You will be asked by vim-addon-manager if you would like\r\nto download and install the plugins.\r\n\r\nInstalling with Pathogen:\r\nWith pathogen, you just have to clone all required plugins into your ~\/.vim\/bundle directory. Running the following lines as a bash script will do exactly that.\r\n\r\n    #!\/bin\/bash\r\n\r\n    declare -a repos=(\r\n      \"git:\/\/github.com\/megaannum\/self.git\"\r\n      \"git:\/\/github.com\/megaannum\/forms.git\"\r\n      \"git:\/\/github.com\/Shougo\/vimproc.git\"\r\n      \"git:\/\/github.com\/Shougo\/vimshell.git\"\r\n      \"-b scala-2.9 git:\/\/github.com\/aemoncannon\/ensime.git\"\r\n      \"git:\/\/github.com\/megaannum\/vimside.git\"\r\n    )\r\n\r\n    cd ~\/.vim\/bundle\r\n\r\n    for repo in \"${repos[@]}\"; do\r\n        git clone $repo\r\n    done;\r\n\r\nNote that you also with pathogen have to run *make* on the appropriate make file inside the vimproc plugin directory.\r\n\r\n== Ensime Install\r\n\r\nEnsime can be downloaded from https:\/\/github.com\/aemoncannon\/ensime\r\nand its on-line manual is at: aemoncannon.github.com\/ensime\/index.html\/.\r\n\r\nIn addition, for ENSIME, there are pre-built releases available at:\r\nhttps:\/\/github.com\/aemoncannon\/ensime\/downloads.\r\nI highly recommend getting these (Scala 2.9.2 and\/or 2.10.0)\r\nrather than trying to build the Ensime Scala code yourself.\r\n\r\nEnsime is not a Vim plugin. It is a Scale program. It has to be installed\r\nand built or a pre-build version has to be used. It can be downloaded\r\nfrom:\r\n\r\n    https:\/\/github.com\/aemoncannon\/ensime\r\n\r\nOne can the follow the instructions there and build it.\r\n\r\nI have never done this. Rather, I have downloaded a pre-build bundle.\r\nOne for Scala 2.9 and another for Scala 10.0. These can be found at:\r\n\r\n    https:\/\/www.dropbox.com\/sh\/ryd981hq08swyqr\/V9o9rDvxkS\/ENSIME%20Releases\r\n\r\nThe Ensime build directory has the following layout using\r\nensime_2.9.2-0.9.8.9 as an example:\r\n\r\n    ensime_2.9.2-0.9.8.9\/\r\n        bin\/\r\n        LICENSE\r\n        elisp\/\r\n        lib\/\r\n        README.md\r\n\r\nor ensime_2.10.0-0.9.8.9:\r\n\r\n    ensime_2.10.0-0.9.8.9\/\r\n        bin\/\r\n        elisp\/\r\n        lib\/\r\n        LICENSE\r\n        README.md\r\n\r\nIt is important that the value of the 'vimside-scala-version'\r\nOption agrees with the Ensime build version. For\r\nensime_2.9.2-0.9.8.9 (the default value):\r\n\r\n   call owner.Set(\"vimside-scala-version\", \"2.9.2\")\r\n\r\nor\r\n   vimside.scala.version=2.9.2\r\n\r\nand for ensime_2.10.0-0.9.8.9:\r\n\r\n   call owner.Set(\"vimside-scala-version\", \"2.10.0\")\r\n\r\nor\r\n\r\n   vimside.scala.version=\"2.10.0\"\r\n\r\nThese values can be set in 'data\/vimside\/options_user.vim'.\r\n\r\nIn addition, the version of Java ($JAVA_HOME\/bin\/java -version)\r\nin the window  that runs Vim (or launched GVim) must agree with\r\nthe value of the Option 'vimside-java-version'. This Option\r\nhas the default value of '1.7' and can be set, again, in\r\n'data\/vimside\/options_user.vim':\r\n\r\n  call owner.Set(\"vimside-java-version\", \"1.8\")\r\n\r\nor\r\n\r\n  vimside.java.version=1.8\r\n\r\nHaving built Ensime or downloaded a pre-built package, you must\r\nset an Option in Vimside so that Vimside can locate the script\r\nused to start the Ensime server. To set a Vimside Option, you\r\nmust copy the 'example_options_user.vim' or, when using\r\nproperties, 'example_vimside.properties' located in 'data\/vimside'\r\nto a file called 'options_user.vim' or 'vimside.properties' and edit it.\r\n\r\nThere is two different ways to do this.\r\n\r\nThe first is to set the Option 'ensime-install-path' or\r\nas a Property 'ensime.install.path' to the\r\nlocation of downloaded Ensime source. If you use the VAM plugin manager,\r\nthen Ensime will be in the directory:\r\n\r\n  $HOME\/.vim\/vim-addons\/ensime\r\nor\r\n  $HOME\/vimfiles\/vim-addons\/ensime\r\n\r\nso you would set the Option according\r\n\r\n  call owner.Set(\"ensime-install-path\", $HOME . \"\/.vim\/vim-addons\/ensime\")\r\nor\r\n  call owner.Set(\"ensime-install-path\", $HOME . \"\/vimfiles\/vim-addons\/ensime\")\r\n\r\nor, as a Property,\r\n\r\n  ensime.install.path=$HOME\/.vim\/vim-addons\/ensime\r\nor\r\n  ensime.install.path=$HOME\/vimfiles\/vim-addons\/ensime\r\n\r\nIf installed with pathogen, those paths are\r\n  $HOME\/.vim\/bundle\/ensime\r\nor\r\n  $HOME\/vimfiles\/bundle\/ensime\r\n\r\nThen depending upon the name of the build directory, which is under the\r\n'ensime-install-path' Option value directory location, you would\r\nset the value of the Option 'ensime-dist-dir' or Property\r\n'ensime.dist.dir' to that directory name.  For example:\r\n\r\n    call owner.Set(\"ensime-dist-dir\", \"ensime_2.9.2-0.9.8.9\")\r\nor\r\n    call owner.Set(\"ensime-dist-dir\", \"ensime_2.10.0-0.9.8.9\")\r\n\r\nor, as a Property,\r\n\r\n    ensime.dist.dir=ensime_2.9.2-0.9.8.9\r\nor\r\n    ensime.dist.dir=ensime_2.10.0-0.9.8.9\r\n\r\nAlternatively, you can specify the full path to the ensime distribution\r\nusing the Option 'ensime-dist-path' or Property 'ensime.dist.path'.\r\nAs an example, if you installed an Ensime build package in some Scala\r\ndirectory, you might set the Option as:\r\n\r\n    call owner.Set(\"ensime-dist-path\", $HOME . \"\/scala\/ensime\/ensime_2.9.2-0.9.8.9\")\r\n\r\nor, as a Property,\r\n\r\n    ensime.dist.path=$HOME\/scala\/ensime\/ensime_2.9.2-0.9.8.9\r\n\r\nIf you set the 'ensime-dist-path' ('ensime-dist.path'), it is checked first\r\nand, if it exists, it is used rather than the 'ensime-install-path'\r\nand 'ensime-dist-dir' ('ensime.install.path' and 'ensime.dist.dir')\r\ncombination.\r\n\r\nVimside supports the Ensime SBT commands. With such, there is an additional\r\nlibrary, an SBT Plugin that supports integration with the ENSIME IDE:\r\nhttps:\/\/github.com\/aemoncannon\/ensime-sbt-cmd\r\n\r\n== Vimside Testing\r\n\r\nRECOMMENDED for initial testing:\r\nTo run against test Scala\/Java project, first in data\/vimside directory\r\ncopy example_options_user.vim to options_user.vim.\r\n\r\n  > cd $HOME\/.vim\/data\/vimside\r\n  > \/bin\/cp example_options_user.vim options_user.vim\r\nor\r\n  > \/bin\/cp example_vimside.properties vimside.properties\r\n\r\nThen, in options_user.vim (or vimside.properties) uncomment the\r\nfollowing two lines:\r\n\r\n   call a:option.Set(\"ensime-config-file-name\", \"ensime_config.vim\")\r\n\r\nor, as a Property,\r\n\r\n   ensime.config.file.name=ensime_config.vim\r\n\r\nThis tells Vimside to use the test project code and to use the\r\nensime_config.vim as the source for Ensime Configuration.\r\n\r\nOne can also run Emacs and enter the command to start Ensime.\r\nI sometimes do this just to check-out how Emacs-Ensime does something\r\nthat I am trying to implement in VimL for Vimside.\r\n\r\nLastly, read the doc\/vimside.txt for more complete information.\r\n\r\nAcknowledgements and thanks:\r\nAemon Cannon for writing Ensime.\r\nDaniel Spiewak has a JEdit binding to Ensime and a simply great video\r\nexplaining why a true editor with Ensime is better than an Eclipse\r\nIde (https:\/\/www.youtube.com\/watch?v=cd2LV0xy9G8 MUST SEE)\r\nand usage examples (http:\/\/vimeo.com\/28597033),\r\nSven Eigenbrodt provided the Pathogen installation information.\r\n","first_name":"richard","6":"richard","last_name":"emberson","7":"emberson","releases":[{"0":"4298","vim_version":"7.0","1":"7.0","script_version":"0.4.0","2":"0.4.0","version_comment":"Big change was the addition of the ActWin (Action Window) which\r\nis now the default window for both compiler errors (via Ensime or\r\nSBT) and the uses-of-symbol-at-point command. Very configurable.\r\nThe quickfix window can still be use if desired via configuration.\r\nNow Vimside supports either initialization with the Option files\r\n'options_user.vim' and a project specific options file (and\/) or\r\nwith Properties file 'vimside.properties' and a project specific\r\nproperties file. See the 'data\/vimside\/PROPERTIES' file for\r\navailable Properties (or, changing '.' to '-', Options).\r\nAlso, bumped (after a long time, the version number.\r\n","3":"Big change was the addition of the ActWin (Action Window) which\r\nis now the default window for both compiler errors (via Ensime or\r\nSBT) and the uses-of-symbol-at-point command. Very configurable.\r\nThe quickfix window can still be use if desired via configuration.\r\nNow Vimside supports either initialization with the Option files\r\n'options_user.vim' and a project specific options file (and\/) or\r\nwith Properties file 'vimside.properties' and a project specific\r\nproperties file. See the 'data\/vimside\/PROPERTIES' file for\r\navailable Properties (or, changing '.' to '-', Options).\r\nAlso, bumped (after a long time, the version number.\r\n","package":"vimside.zip","4":"vimside.zip","src_id":"20712","5":"20712","creation_date":"1377466976","6":"1377466976"},{"0":"4298","vim_version":"7.3","1":"7.3","script_version":"0.2.23","2":"0.2.23","version_comment":"With this release, variable at bottom of the plugin\/vimside.vim file\r\nhave been added which allows one to turn on logging during Vimside Option\r\nloading. For the Vimside logger, Options must first be loaded\r\nin order to configure it. Thus, no logging when loading Options.\r\nSo, I added a non-configurable logger that only logs in the\r\nvimside#options#manager.vim file. Hopefully, this will help\r\nusers figure out whats happening during option loading.\r\nAlso, two Options have been removed, test-ensime-file-use and\r\ntest-ensime-file-dir; they might have been useful when there was only\r\none \"test\" project under data\/vimside not not now.\r\nI knew that the SExp parser was a \"quick and dirty\" implementation, what\r\nI had not realized was that it was really \"slow and dirty\"; with the\r\ntype inspector feature, getting the symbol-at-point info for String\r\ntook 65 seconds to parse. So, the SExp parse was re-written so that now\r\nit takes a little over 8 seconds - still long but much better.\r\nModified the ensime\/scheduler.vim Job adding code so that while processing\r\nthe current Jobs list, any add is saved in a separate list (like any remove)\r\nand only at the end of processing are the adds, if any, are done. This\r\nfixed a bug in the hover code. Also in scheduler.vim, because the result for\r\nsymbol-at-point for String was so large (a String of length 110K), all of\r\nit was not read from the socket during a single read. This was fixed so\r\nthat partial reads resulted in a second (and third) read to get the\r\nrest of the protocol message.\r\nIn the type-inspector window, a \":q\" now does what \"q\" does, it closes\r\nthe window. Also, changed current page name from \"s:page\" to \"s:current_page\"\r\nto mirror the current inspector's name. Also, the current_page is now\r\nonly generated if it does not exist (speeding up history previous\/next\r\noperations).\r\nFor certain symbols, symbol-at-point requests to the Ensime server backend\r\nwould cause it to generate scala-notes event messages and the reception of\r\nthese events would cause the between server polling times to be increase -\r\nwhich was bad since one is still waiting for the rpc response. This was\r\nfixed by check if there are any outstanding rpc's prior to adjusting\r\npolling time.\r\nAdded a couple of newly implemented features to the Forms popup menu.\r\nAdded a couple of newly implemented features to the Forms popup menu.\r\nUpdated where one could download the pre-build images of Ensime.\r\nFixed example to use the latest pre-build Ensime version numbers:\r\nensime_2.9.2-0.9.8.9 and ensime_2.10.0-0.9.8.9\r\nCommunications with the server is now both asynchronous and synchronous.\r\nGenerally, asynchronous will still be used for standard communication\r\nwhile synchronous is used for unit tests. Maybe, in time, some of the\r\ncommands will be synchronous - maybe configurable via Options.\r\nAdded unit tests.\r\nTests require runVimTests-1.22.zip and vimtap-0.4.0.zip.\r\n","3":"With this release, variable at bottom of the plugin\/vimside.vim file\r\nhave been added which allows one to turn on logging during Vimside Option\r\nloading. For the Vimside logger, Options must first be loaded\r\nin order to configure it. Thus, no logging when loading Options.\r\nSo, I added a non-configurable logger that only logs in the\r\nvimside#options#manager.vim file. Hopefully, this will help\r\nusers figure out whats happening during option loading.\r\nAlso, two Options have been removed, test-ensime-file-use and\r\ntest-ensime-file-dir; they might have been useful when there was only\r\none \"test\" project under data\/vimside not not now.\r\nI knew that the SExp parser was a \"quick and dirty\" implementation, what\r\nI had not realized was that it was really \"slow and dirty\"; with the\r\ntype inspector feature, getting the symbol-at-point info for String\r\ntook 65 seconds to parse. So, the SExp parse was re-written so that now\r\nit takes a little over 8 seconds - still long but much better.\r\nModified the ensime\/scheduler.vim Job adding code so that while processing\r\nthe current Jobs list, any add is saved in a separate list (like any remove)\r\nand only at the end of processing are the adds, if any, are done. This\r\nfixed a bug in the hover code. Also in scheduler.vim, because the result for\r\nsymbol-at-point for String was so large (a String of length 110K), all of\r\nit was not read from the socket during a single read. This was fixed so\r\nthat partial reads resulted in a second (and third) read to get the\r\nrest of the protocol message.\r\nIn the type-inspector window, a \":q\" now does what \"q\" does, it closes\r\nthe window. Also, changed current page name from \"s:page\" to \"s:current_page\"\r\nto mirror the current inspector's name. Also, the current_page is now\r\nonly generated if it does not exist (speeding up history previous\/next\r\noperations).\r\nFor certain symbols, symbol-at-point requests to the Ensime server backend\r\nwould cause it to generate scala-notes event messages and the reception of\r\nthese events would cause the between server polling times to be increase -\r\nwhich was bad since one is still waiting for the rpc response. This was\r\nfixed by check if there are any outstanding rpc's prior to adjusting\r\npolling time.\r\nAdded a couple of newly implemented features to the Forms popup menu.\r\nAdded a couple of newly implemented features to the Forms popup menu.\r\nUpdated where one could download the pre-build images of Ensime.\r\nFixed example to use the latest pre-build Ensime version numbers:\r\nensime_2.9.2-0.9.8.9 and ensime_2.10.0-0.9.8.9\r\nCommunications with the server is now both asynchronous and synchronous.\r\nGenerally, asynchronous will still be used for standard communication\r\nwhile synchronous is used for unit tests. Maybe, in time, some of the\r\ncommands will be synchronous - maybe configurable via Options.\r\nAdded unit tests.\r\nTests require runVimTests-1.22.zip and vimtap-0.4.0.zip.\r\n","package":"vimside.zip","4":"vimside.zip","src_id":"19696","5":"19696","creation_date":"1364164044","6":"1364164044"},{"0":"4298","vim_version":"7.3","1":"7.3","script_version":"0.2.21","2":"0.2.21","version_comment":"Type and Package Inspector","3":"Type and Package Inspector","package":"vimside.zip","4":"vimside.zip","src_id":"19638","5":"19638","creation_date":"1363225597","6":"1363225597"},{"0":"4298","vim_version":"7.0","1":"7.0","script_version":"0.2.17","2":"0.2.17","version_comment":"Added support for SBT (Simple Build Tool) projects.","3":"Added support for SBT (Simple Build Tool) projects.","package":"vimside.zip","4":"vimside.zip","src_id":"19521","5":"19521","creation_date":"1361051635","6":"1361051635"},{"0":"4298","vim_version":"7.0","1":"7.0","script_version":"0.2.14","2":"0.2.14","version_comment":"Implemented method vimside#ensime#swank#handle_no_response() which is call\r\nby vimside#ensime#io#ping(timeout) when the response from the Ensime server\r\nis empty which uses the previous checkin's Options\r\n    scheduler-many-max-count-no-events (default 50)\r\n    scheduler-events-max-count-no-events (default 50)\r\nto ultimately restore the schedule to a \"not expecting anything\/steady\" state\r\n(a long time between pings). This simply assures that if there is some\r\nbug in handling responses from the server, a fast ping rate will\r\nultimately stop and the system returned to steady-state.\r\n","3":"Implemented method vimside#ensime#swank#handle_no_response() which is call\r\nby vimside#ensime#io#ping(timeout) when the response from the Ensime server\r\nis empty which uses the previous checkin's Options\r\n    scheduler-many-max-count-no-events (default 50)\r\n    scheduler-events-max-count-no-events (default 50)\r\nto ultimately restore the schedule to a \"not expecting anything\/steady\" state\r\n(a long time between pings). This simply assures that if there is some\r\nbug in handling responses from the server, a fast ping rate will\r\nultimately stop and the system returned to steady-state.\r\n","package":"vimside.zip","4":"vimside.zip","src_id":"19288","5":"19288","creation_date":"1357064198","6":"1357064198"},{"0":"4298","vim_version":"7.0","1":"7.0","script_version":"0.2.13","2":"0.2.13","version_comment":"Added Build and Rebuild project commands.\r\nRe-wrote how the swank dispatch and scheduling code handle events.\r\nReplaced the scheduling Options with a new set of Options.","3":"Added Build and Rebuild project commands.\r\nRe-wrote how the swank dispatch and scheduling code handle events.\r\nReplaced the scheduling Options with a new set of Options.","package":"vimside.zip","4":"vimside.zip","src_id":"19262","5":"19262","creation_date":"1356913154","6":"1356913154"},{"0":"4298","vim_version":"7.0","1":"7.0","script_version":"0.2.12","2":"0.2.12","version_comment":"Added Imports (add\/suggest) Refactoring command.\r\nFixed Search command interaction with Time-base scheduler.\r\nFixed Search display of entered text prior to calling Ensime.\r\nFixed Search command result sorting.\r\nSearch now non-incremental by default.\r\nAdd Search Option allowing the setting for number of results:\r\n    'tailor-symbol-search-maximum-return'\r\nFixed Ensime config so that indexing is allowed on startup by default.\r\nUpgraded doc and example configs for Ensime Scala 2.10-RC3 build.\r\n","3":"Added Imports (add\/suggest) Refactoring command.\r\nFixed Search command interaction with Time-base scheduler.\r\nFixed Search display of entered text prior to calling Ensime.\r\nFixed Search command result sorting.\r\nSearch now non-incremental by default.\r\nAdd Search Option allowing the setting for number of results:\r\n    'tailor-symbol-search-maximum-return'\r\nFixed Ensime config so that indexing is allowed on startup by default.\r\nUpgraded doc and example configs for Ensime Scala 2.10-RC3 build.\r\n","package":"vimside.zip","4":"vimside.zip","src_id":"19156","5":"19156","creation_date":"1355077826","6":"1355077826"},{"0":"4298","vim_version":"7.0","1":"7.0","script_version":"0.2.11","2":"0.2.11","version_comment":"Add Refactor Options to validate allowed\/disallow identifier names.","3":"Add Refactor Options to validate allowed\/disallow identifier names.","package":"vimside.zip","4":"vimside.zip","src_id":"19098","5":"19098","creation_date":"1354583209","6":"1354583209"},{"0":"4298","vim_version":"7.0","1":"7.0","script_version":"0.2.10","2":"0.2.10","version_comment":"Add pathogen install instructions.\r\n","3":"Add pathogen install instructions.\r\n","package":"vimside.zip","4":"vimside.zip","src_id":"19086","5":"19086","creation_date":"1354495888","6":"1354495888"},{"0":"4298","vim_version":"7.0","1":"7.0","script_version":"0.2.9","2":"0.2.9","version_comment":"Added refactoring commands.\r\nChanged key mapping for vimside#command#SymbolAtPoint() and vimside#command#PreviousPosition().\r\nMade the test source code so that there are no compile errors.\r\n","3":"Added refactoring commands.\r\nChanged key mapping for vimside#command#SymbolAtPoint() and vimside#command#PreviousPosition().\r\nMade the test source code so that there are no compile errors.\r\n","package":"vimside.zip","4":"vimside.zip","src_id":"19085","5":"19085","creation_date":"1354476036","6":"1354476036"},{"0":"4298","vim_version":"7.0","1":"7.0","script_version":"0.2.8","2":"0.2.8","version_comment":"First pre-alpha code release.","3":"First pre-alpha code release.","package":"vimside.zip","4":"vimside.zip","src_id":"19066","5":"19066","creation_date":"1354224255","6":"1354224255"},{"0":"4298","vim_version":"7.0","1":"7.0","script_version":"0.2","2":"0.2","version_comment":"Initial upload","3":"Initial upload","package":"vimside.zip","4":"vimside.zip","src_id":"18917","5":"18917","creation_date":"1351444762","6":"1351444762"}]},"4297":{"script_id":"4297","0":"4297","script_name":"detailed","1":"detailed","script_type":"color scheme","2":"color scheme","summary":"Show subtler color variations than those lazy palette-shifting schemes!","3":"Show subtler color variations than those lazy palette-shifting schemes!","description":"\r\nSource repo: http:\/\/github.com\/rking\/vim-detailed\r\n\r\nSo many 256-color schemes merely shift the palette around, displaying only 8\r\ncolors (even though they're a *different* set of 8 colors than default).\r\n\r\nThis scheme is more detailed than that.\r\n\r\nYour eyes will learn to pick up on subtler patterns without requiring as\r\nmuch from your conscious mind.  Instead of the goal being merely looking\r\ncool, the goal is to maximize info bandwidth from the computer to the brain.\r\nThe regexes, for example, are much easier to pick out. The overall feel of a\r\ngiven file becomes much more intuitively recognizeable (you'll know you're\r\nin foo.rb, not bar.rb, without having to read any text). Certain bits will\r\n\"pop\" into being the right colors, such as the difference between\r\n\"RUBY_VERISON\" and \"RUBY_VERSION\", or # encoding: utf-8\r\n\r\n\/\/ 256 Color Requirement\r\n\r\nIf you aren't getting 256 colors, you aren't getting detailed.vim.\r\nTypically, you'll have to make sure your `$TERM` variable is set right. This\r\ncan get un-set by some programs, such as tmux. So you can force it to\r\nsomething like:\r\n\r\n    export TERM=screen-256color\r\n    # or:\r\n    export TERM=xterm-256color\r\n\r\nIf these are unavailable on the target system, you might have to place a\r\nterminfo file in `~\/.terminfo\/`  -or- you can be totally gross and force it\r\nwith `:set &t_Co=256` in vim. But don't be gross. It's uncouth.\r\n\r\n\/\/ Download\r\n\r\n If using Pathogen,\r\n\r\n     cd ~\/.vim\/bundle && git clone https:\/\/github.com\/rking\/vim-detailed\r\n\r\n If using no vim plugin manager:\r\n\r\n     mkdir -p ~\/.vim\/colors\/ && cd $_ && wget https:\/\/raw.github.com\/rking\/vim-detailed\/master\/colors\/detailed.vim\r\n\r\n\/\/ Setup\r\n\r\nIn your ~\/.vimrc (or ~\/.vim\/plugin\/colorscheme.vim if you like to organize):\r\n\r\n    colo detailed\r\n\r\nThis enables it globally. If you want to just do it for a trial, as long as\r\nyou have done one of the steps in the \"Download\" section, above, you can do:\r\n\r\n    vim foo.rb +colo\\ detailed\r\n\r\nOr, from within vim:\r\n\r\n    :colo detailed\r\n\r\n\/\/ Language Support So Far\r\n\r\n- Ruby: 113 details detailed.\r\n- C: 12 details detailed.\r\n- Go: 10 details detailed.\r\n- Diff: 10 details detailed.\r\n- Javascript: 4 details detailed.\r\n- Vim: 4 details detailed.\r\n\r\n# rking\/vim-detailed open issues\r\n  13  More troubleshooting help? 3\r\n  11  Smart Here-docs 1\r\n   9  Detail Python [actual-user-request] 4\r\n   7  Handle t_Co != 256\r\n   6  Pygments Companion\r\n   3  Distinguish Foo and Bar of \"class Foo < Bar\"","4":"\r\nSource repo: http:\/\/github.com\/rking\/vim-detailed\r\n\r\nSo many 256-color schemes merely shift the palette around, displaying only 8\r\ncolors (even though they're a *different* set of 8 colors than default).\r\n\r\nThis scheme is more detailed than that.\r\n\r\nYour eyes will learn to pick up on subtler patterns without requiring as\r\nmuch from your conscious mind.  Instead of the goal being merely looking\r\ncool, the goal is to maximize info bandwidth from the computer to the brain.\r\nThe regexes, for example, are much easier to pick out. The overall feel of a\r\ngiven file becomes much more intuitively recognizeable (you'll know you're\r\nin foo.rb, not bar.rb, without having to read any text). Certain bits will\r\n\"pop\" into being the right colors, such as the difference between\r\n\"RUBY_VERISON\" and \"RUBY_VERSION\", or # encoding: utf-8\r\n\r\n\/\/ 256 Color Requirement\r\n\r\nIf you aren't getting 256 colors, you aren't getting detailed.vim.\r\nTypically, you'll have to make sure your `$TERM` variable is set right. This\r\ncan get un-set by some programs, such as tmux. So you can force it to\r\nsomething like:\r\n\r\n    export TERM=screen-256color\r\n    # or:\r\n    export TERM=xterm-256color\r\n\r\nIf these are unavailable on the target system, you might have to place a\r\nterminfo file in `~\/.terminfo\/`  -or- you can be totally gross and force it\r\nwith `:set &t_Co=256` in vim. But don't be gross. It's uncouth.\r\n\r\n\/\/ Download\r\n\r\n If using Pathogen,\r\n\r\n     cd ~\/.vim\/bundle && git clone https:\/\/github.com\/rking\/vim-detailed\r\n\r\n If using no vim plugin manager:\r\n\r\n     mkdir -p ~\/.vim\/colors\/ && cd $_ && wget https:\/\/raw.github.com\/rking\/vim-detailed\/master\/colors\/detailed.vim\r\n\r\n\/\/ Setup\r\n\r\nIn your ~\/.vimrc (or ~\/.vim\/plugin\/colorscheme.vim if you like to organize):\r\n\r\n    colo detailed\r\n\r\nThis enables it globally. If you want to just do it for a trial, as long as\r\nyou have done one of the steps in the \"Download\" section, above, you can do:\r\n\r\n    vim foo.rb +colo\\ detailed\r\n\r\nOr, from within vim:\r\n\r\n    :colo detailed\r\n\r\n\/\/ Language Support So Far\r\n\r\n- Ruby: 113 details detailed.\r\n- C: 12 details detailed.\r\n- Go: 10 details detailed.\r\n- Diff: 10 details detailed.\r\n- Javascript: 4 details detailed.\r\n- Vim: 4 details detailed.\r\n\r\n# rking\/vim-detailed open issues\r\n  13  More troubleshooting help? 3\r\n  11  Smart Here-docs 1\r\n   9  Detail Python [actual-user-request] 4\r\n   7  Handle t_Co != 256\r\n   6  Pygments Companion\r\n   3  Distinguish Foo and Bar of \"class Foo < Bar\"","install_details":"(See Download and Setup, above)","5":"(See Download and Setup, above)","first_name":"Ryan","6":"Ryan","last_name":"King","7":"King","releases":[{"0":"4297","vim_version":"7.0","1":"7.0","script_version":"0.8","2":"0.8","version_comment":"Beginnings of JavaScript support","3":"Beginnings of JavaScript support","package":"detailed.vim","4":"detailed.vim","src_id":"19920","5":"19920","creation_date":"1366774638","6":"1366774638"},{"0":"4297","vim_version":"7.0","1":"7.0","script_version":"0.7","2":"0.7","version_comment":"Make visual selection green rather than light gray\r\nDistinguish between ' \" and ` in Ruby","3":"Make visual selection green rather than light gray\r\nDistinguish between ' \" and ` in Ruby","package":"detailed.vim","4":"detailed.vim","src_id":"19518","5":"19518","creation_date":"1361015810","6":"1361015810"},{"0":"4297","vim_version":"7.0","1":"7.0","script_version":"0.6","2":"0.6","version_comment":"Golang support + toned down colorcolumn","3":"Golang support + toned down colorcolumn","package":"detailed.vim","4":"detailed.vim","src_id":"19169","5":"19169","creation_date":"1355286011","6":"1355286011"},{"0":"4297","vim_version":"7.0","1":"7.0","script_version":"0.5","2":"0.5","version_comment":"Beginning of support for languages other than Ruby + minor refinements for Ruby itself (e.g., uses mint for method bodies rather than lilac)","3":"Beginning of support for languages other than Ruby + minor refinements for Ruby itself (e.g., uses mint for method bodies rather than lilac)","package":"detailed.vim","4":"detailed.vim","src_id":"19047","5":"19047","creation_date":"1354003668","6":"1354003668"},{"0":"4297","vim_version":"7.0","1":"7.0","script_version":"0.4","2":"0.4","version_comment":"Works in gvim now; forces black bg (for legibility); handful of minor updates.","3":"Works in gvim now; forces black bg (for legibility); handful of minor updates.","package":"detailed.vim","4":"detailed.vim","src_id":"18978","5":"18978","creation_date":"1353040713","6":"1353040713"},{"0":"4297","vim_version":"7.0","1":"7.0","script_version":"0.3","2":"0.3","version_comment":"Lots of minor updates. Getting better!","3":"Lots of minor updates. Getting better!","package":"detailed.vim","4":"detailed.vim","src_id":"18947","5":"18947","creation_date":"1352076117","6":"1352076117"},{"0":"4297","vim_version":"7.0","1":"7.0","script_version":"0.2","2":"0.2","version_comment":"Un-introducing last-minute glitch introduction. ☹","3":"Un-introducing last-minute glitch introduction. ☹","package":"detailed.vim","4":"detailed.vim","src_id":"18921","5":"18921","creation_date":"1351478130","6":"1351478130"}]},"4296":{"script_id":"4296","0":"4296","script_name":"ViewPort","1":"ViewPort","script_type":"utility","2":"utility","summary":"Make a buffer from part of a file","3":"Make a buffer from part of a file","description":"Note: if you want to downgrade the plugin, let me know what is wrong with it, I am sure it can be fixed.\r\n\r\nThis is a simple plugin which makes a buffer from a part of a buffer. Saving the new buffer will install the changes into the original buffer rather than save it to disk. This is a nice utility if you wan to make diffs of two parts of two files. If the original part of the file was modified an error message is given (like when saving to a modified file to a disk), you can use :w! to discard the changes made in original file. The script is using marks to track the positions, hence you can modify the original file.","4":"Note: if you want to downgrade the plugin, let me know what is wrong with it, I am sure it can be fixed.\r\n\r\nThis is a simple plugin which makes a buffer from a part of a buffer. Saving the new buffer will install the changes into the original buffer rather than save it to disk. This is a nice utility if you wan to make diffs of two parts of two files. If the original part of the file was modified an error message is given (like when saving to a modified file to a disk), you can use :w! to discard the changes made in original file. The script is using marks to track the positions, hence you can modify the original file.","install_details":"Copy the script to ~\/.vim\/plugin","5":"Copy the script to ~\/.vim\/plugin","first_name":"Marcin","6":"Marcin","last_name":"Szamotulski","7":"Szamotulski","releases":[{"0":"4296","vim_version":"7.4","1":"7.4","script_version":"4","2":"4","version_comment":"Sync with github version.","3":"Sync with github version.","package":"ViewPort.vmb","4":"ViewPort.vmb","src_id":"22001","5":"22001","creation_date":"1402235379","6":"1402235379"},{"0":"4296","vim_version":"7.0","1":"7.0","script_version":"3","2":"3","version_comment":"The ViewPort() function is now public (i.e. defined without <sid>)","3":"The ViewPort() function is now public (i.e. defined without <sid>)","package":"ViewPort.vmb","4":"ViewPort.vmb","src_id":"19435","5":"19435","creation_date":"1359234997","6":"1359234997"},{"0":"4296","vim_version":"7.0","1":"7.0","script_version":"2","2":"2","version_comment":"Doc added + fnameescape() in a proper way.","3":"Doc added + fnameescape() in a proper way.","package":"ViewPort.vmb","4":"ViewPort.vmb","src_id":"18910","5":"18910","creation_date":"1351379453","6":"1351379453"},{"0":"4296","vim_version":"7.0","1":"7.0","script_version":"1","2":"1","version_comment":"Initial upload","3":"Initial upload","package":"viewport.vim","4":"viewport.vim","src_id":"18905","5":"18905","creation_date":"1351354669","6":"1351354669"}]},"4295":{"script_id":"4295","0":"4295","script_name":"smartgrep","1":"smartgrep","script_type":"utility","2":"utility","summary":"Grep word in source file excluding comment","3":"Grep word in source file excluding comment","description":"smartgrep\r\n=======\r\nGrep word in source file excluding comment for vim plugin.\r\n\r\nSupport OS\r\n=======\r\nUnix, MacOS X, Windows\r\n\r\nSuport Language and Comment Type\r\n=======\r\nC, C++, Objective-C, C#(CSharp), Java Script   \/* *\/, \/\/\r\n\r\nUsage (smartgrep.vim command)\r\n=======\r\nDefine g:base_dir in your .vimrc file.  \r\n\texample:  \r\n\t\tlet g:base_dir=\"\/develop\/\"  \r\n  \r\n,g   -> recursive word grep for c,h file exclude comment by mouse cursored word  \r\n,h   -> recursive word grep for h file exclude comment by mouse cursored word  \r\n:Rn  -> recursive word grep for c,h file include comment  \r\n:Rh  -> recursive word grep for h file exclude comment  \r\n:R   -> recursive word grep for c,h file exclude comment  \r\n:Rno -> recursive grep for c,h file include comment  \r\n:Rho -> recursive grep for h file exclude comment  \r\n:Ro  -> recursive grep for c,h file exclude comment  \r\n:Rl  -> recursive word grep for c,h file exclude comment in sys_dir_w  \r\n:Rw  -> recursive word grep for c,h file exclude comment in sys_dir_l  \r\n\r\nUsage (smartgrep binary)\r\n=======\r\n$ cd {directory-you-want-to-grep}  \r\n$ smartgrep  \r\nUsage: smartgrep \/h {word}  : recursive      grep for .h                        excluding comment  \r\n                 \/b {word}  : recursive      grep for .cpp .c .mm .m .cs .js .h excluding comment  \r\n                 \/n {word}  : recursive      grep for .cpp .c .mm .m .cs .js .h including comment  \r\n                 \/hw {word} : recursive word grep for .h                        excluding comment  \r\n                 \/bw {word} : recursive word grep for .cpp .c .mm .m .cs .js .h excluding comment  \r\n                 \/nw {word} : recursive word grep for .cpp .c .mm .m .cs .js .h including comment  \r\n\r\nINSTALL\r\n=======\r\nIf you are Windows or Mac OS X user, read .\/plugin\/smartgrep.vim file.  \r\nIf you are Unix user, type 'make + [enter]' and read .\/plugin\/smartgrep.vim file.  \r\n\r\ngit hub repogitory\r\n=======\r\nhttps:\/\/github.com\/pebble8888\/smartgrep\r\n\r\nIf you have any comment, please issue it in github;\r\n","4":"smartgrep\r\n=======\r\nGrep word in source file excluding comment for vim plugin.\r\n\r\nSupport OS\r\n=======\r\nUnix, MacOS X, Windows\r\n\r\nSuport Language and Comment Type\r\n=======\r\nC, C++, Objective-C, C#(CSharp), Java Script   \/* *\/, \/\/\r\n\r\nUsage (smartgrep.vim command)\r\n=======\r\nDefine g:base_dir in your .vimrc file.  \r\n\texample:  \r\n\t\tlet g:base_dir=\"\/develop\/\"  \r\n  \r\n,g   -> recursive word grep for c,h file exclude comment by mouse cursored word  \r\n,h   -> recursive word grep for h file exclude comment by mouse cursored word  \r\n:Rn  -> recursive word grep for c,h file include comment  \r\n:Rh  -> recursive word grep for h file exclude comment  \r\n:R   -> recursive word grep for c,h file exclude comment  \r\n:Rno -> recursive grep for c,h file include comment  \r\n:Rho -> recursive grep for h file exclude comment  \r\n:Ro  -> recursive grep for c,h file exclude comment  \r\n:Rl  -> recursive word grep for c,h file exclude comment in sys_dir_w  \r\n:Rw  -> recursive word grep for c,h file exclude comment in sys_dir_l  \r\n\r\nUsage (smartgrep binary)\r\n=======\r\n$ cd {directory-you-want-to-grep}  \r\n$ smartgrep  \r\nUsage: smartgrep \/h {word}  : recursive      grep for .h                        excluding comment  \r\n                 \/b {word}  : recursive      grep for .cpp .c .mm .m .cs .js .h excluding comment  \r\n                 \/n {word}  : recursive      grep for .cpp .c .mm .m .cs .js .h including comment  \r\n                 \/hw {word} : recursive word grep for .h                        excluding comment  \r\n                 \/bw {word} : recursive word grep for .cpp .c .mm .m .cs .js .h excluding comment  \r\n                 \/nw {word} : recursive word grep for .cpp .c .mm .m .cs .js .h including comment  \r\n\r\nINSTALL\r\n=======\r\nIf you are Windows or Mac OS X user, read .\/plugin\/smartgrep.vim file.  \r\nIf you are Unix user, type 'make + [enter]' and read .\/plugin\/smartgrep.vim file.  \r\n\r\ngit hub repogitory\r\n=======\r\nhttps:\/\/github.com\/pebble8888\/smartgrep\r\n\r\nIf you have any comment, please issue it in github;\r\n","install_details":"","5":"","first_name":"pebble","6":"pebble","last_name":"on software","7":"on software","releases":[{"0":"4295","vim_version":"7.0","1":"7.0","script_version":"2.1","2":"2.1","version_comment":"Initial upload","3":"Initial upload","package":"smartgrep_2_1.zip","4":"smartgrep_2_1.zip","src_id":"18903","5":"18903","creation_date":"1351337221","6":"1351337221"}]},"4294":{"script_id":"4294","0":"4294","script_name":"git log","1":"git log","script_type":"utility","2":"utility","summary":"A Git Tree, Log and History Viewer and Diff Tool","3":"A Git Tree, Log and History Viewer and Diff Tool","description":"This plugin simply will show the commit history of the current file in the window and allow you to diff this against older commits. It also allows you to diff it against different commits in different branches.\r\n\r\nYou can find more information at: https:\/\/github.com\/PAntoine\/vimgitlog\r\n\r\nPlease can you report and problems there, as it is easier to track them in one place.","4":"This plugin simply will show the commit history of the current file in the window and allow you to diff this against older commits. It also allows you to diff it against different commits in different branches.\r\n\r\nYou can find more information at: https:\/\/github.com\/PAntoine\/vimgitlog\r\n\r\nPlease can you report and problems there, as it is easier to track them in one place.","install_details":"Copy the gitlog.vim file to plugins, the gitlog.txt to doc.\r\n\r\nCall :helpt <path to doc directory>\/gitlog.txt\r\n\r\nAnd that should be that.","5":"Copy the gitlog.vim file to plugins, the gitlog.txt to doc.\r\n\r\nCall :helpt <path to doc directory>\/gitlog.txt\r\n\r\nAnd that should be that.","first_name":"Peter","6":"Peter","last_name":"Antoine","7":"Antoine","releases":[{"0":"4294","vim_version":"7.3","1":"7.3","script_version":"6.0.0","2":"6.0.0","version_comment":"vimgitlog now works on windows.\r\n    \r\nBUG: Windows needs to pass unix paths to git\r\nBUG: Fix pathing for file diff\r\nBUG: Part of fix case-sensitive directory ordering.\r\nBUG: Fix setup for multi-byte encoding.\r\nBUG: Fix path handling for windows.","3":"vimgitlog now works on windows.\r\n    \r\nBUG: Windows needs to pass unix paths to git\r\nBUG: Fix pathing for file diff\r\nBUG: Part of fix case-sensitive directory ordering.\r\nBUG: Fix setup for multi-byte encoding.\r\nBUG: Fix path handling for windows.","package":"vimgitlog-version_6.0.0.tar.gz","4":"vimgitlog-version_6.0.0.tar.gz","src_id":"24909","5":"24909","creation_date":"1484897992","6":"1484897992"},{"0":"4294","vim_version":"7.3","1":"7.3","script_version":"5.1.1","2":"5.1.1","version_comment":"Basically fixed some backward compatibility issues with ubuntu 12.4 and added a couple of useful features.\r\n\r\n BUG: When refreshing a dir propagate changes up the tree.\r\n BUG: Open files in directory that have been deleted.\r\n BUG: Fixed undefined variable for old versions of git.\r\n BUG: Fixed work-dir work-tree incorrect parameter.\r\n BUG: fixed backwards compatibility issue with expand().\r\n BUG: fixed window error on exit.\r\n BUG: Fixed file-system deleted files not showing up in tree.\r\n BUG: Fixed tree reset in the root not correctly working.\r\n NEW_FEATURE: Added file commands.\r\n NEW_FEATURE: View commit as a patch.","3":"Basically fixed some backward compatibility issues with ubuntu 12.4 and added a couple of useful features.\r\n\r\n BUG: When refreshing a dir propagate changes up the tree.\r\n BUG: Open files in directory that have been deleted.\r\n BUG: Fixed undefined variable for old versions of git.\r\n BUG: Fixed work-dir work-tree incorrect parameter.\r\n BUG: fixed backwards compatibility issue with expand().\r\n BUG: fixed window error on exit.\r\n BUG: Fixed file-system deleted files not showing up in tree.\r\n BUG: Fixed tree reset in the root not correctly working.\r\n NEW_FEATURE: Added file commands.\r\n NEW_FEATURE: View commit as a patch.","package":"vimgitlog-version_5.1.1.tar.gz","4":"vimgitlog-version_5.1.1.tar.gz","src_id":"24873","5":"24873","creation_date":"1483472301","6":"1483472301"},{"0":"4294","vim_version":"7.4","1":"7.4","script_version":"5.1.0","2":"5.1.0","version_comment":"BUG: Not all hashes are 7 chars (and couple of syntax fixes)\r\nBUG: correctly find sub-directories when not started at root\r\nBUG: correctly find files when gitlog started in sub-dir\r\nBUG: Redraw messed up git tree\r\nBUG: tree open did not start at first tree item.\r\nNEW_FEATURE: Add version to make life eaiser\r\nNEW_FEATURE: Goto Previous Change\r\nNEW_FEATURE: Goto Next Change\r\nNEW_FEATURE: Allow for toggling the hidden files.\r\nNEW_FEATURE: Toggle branch window","3":"BUG: Not all hashes are 7 chars (and couple of syntax fixes)\r\nBUG: correctly find sub-directories when not started at root\r\nBUG: correctly find files when gitlog started in sub-dir\r\nBUG: Redraw messed up git tree\r\nBUG: tree open did not start at first tree item.\r\nNEW_FEATURE: Add version to make life eaiser\r\nNEW_FEATURE: Goto Previous Change\r\nNEW_FEATURE: Goto Next Change\r\nNEW_FEATURE: Allow for toggling the hidden files.\r\nNEW_FEATURE: Toggle branch window","package":"vimgitlog-version_5.1.0.tar.gz","4":"vimgitlog-version_5.1.0.tar.gz","src_id":"23775","5":"23775","creation_date":"1449332414","6":"1449332414"},{"0":"4294","vim_version":"7.4","1":"7.4","script_version":"5.0.0","2":"5.0.0","version_comment":"(I have upped the version requirements - as I dont current have version 7.3 to test against)\r\n\r\nPERFORMANCE: Tree walking time substantially better.\r\nPERFORMANCE: Reduced the amount of unrequired git accesses.\r\nNEW_FEATURE: Properly coalescing of the repo and local directory names.\r\nNEW_FEATURE: Make reset head also reset branch.\r\nNEW_FEATURE: Goto latest on current selected branch.\r\nNEW_FEATURE: sub-git trees supported.\r\nNEW_FEATURE: Handling of Non-git trees better.\r\nNEW_FEATURE: Repo support.\r\nNEW_FEATURE: additional command.\r\nBUG: If object type is different repo vs local add two items.\r\nBUG: Added back local dot files (woops!).\r\nBUG: Removed rubbish file added in empty directories.\r\nBUG: Fixed toggle resetting branch state.\r\nBUG: Syntax Fixes.\r\n","3":"(I have upped the version requirements - as I dont current have version 7.3 to test against)\r\n\r\nPERFORMANCE: Tree walking time substantially better.\r\nPERFORMANCE: Reduced the amount of unrequired git accesses.\r\nNEW_FEATURE: Properly coalescing of the repo and local directory names.\r\nNEW_FEATURE: Make reset head also reset branch.\r\nNEW_FEATURE: Goto latest on current selected branch.\r\nNEW_FEATURE: sub-git trees supported.\r\nNEW_FEATURE: Handling of Non-git trees better.\r\nNEW_FEATURE: Repo support.\r\nNEW_FEATURE: additional command.\r\nBUG: If object type is different repo vs local add two items.\r\nBUG: Added back local dot files (woops!).\r\nBUG: Removed rubbish file added in empty directories.\r\nBUG: Fixed toggle resetting branch state.\r\nBUG: Syntax Fixes.\r\n","package":"vimgitlog-version_5.0.0.tar.gz","4":"vimgitlog-version_5.0.0.tar.gz","src_id":"23260","5":"23260","creation_date":"1430848452","6":"1430848452"},{"0":"4294","vim_version":"7.3","1":"7.3","script_version":"4.0.1","2":"4.0.1","version_comment":"PA: BUG: Fixed issue with sym-link loops.\r\nPA: BUG: Fixed issue with trees not properly displaying in sub-dirs.\r\nPA: BUG: Fixed issue with documentation being wrong.\r\nPA: BUG: Fixed syntax highlighting.\r\nPA: BUG: Fixed manual opening of sub-dir was not correctly filtering.\r\nPA: NEW_FEATURE: Not walking links that loop.\r\nPA: NEW_FEATURE: Link highlighting.\r\n","3":"PA: BUG: Fixed issue with sym-link loops.\r\nPA: BUG: Fixed issue with trees not properly displaying in sub-dirs.\r\nPA: BUG: Fixed issue with documentation being wrong.\r\nPA: BUG: Fixed syntax highlighting.\r\nPA: BUG: Fixed manual opening of sub-dir was not correctly filtering.\r\nPA: NEW_FEATURE: Not walking links that loop.\r\nPA: NEW_FEATURE: Link highlighting.\r\n","package":"vimgitlog-version_4.0.1.tar.gz","4":"vimgitlog-version_4.0.1.tar.gz","src_id":"23049","5":"23049","creation_date":"1426617028","6":"1426617028"},{"0":"4294","vim_version":"7.3","1":"7.3","script_version":"4.0.0","2":"4.0.0","version_comment":"    Version 4.0.0\r\n    \r\n    NEW FEATURE: Show only changed files.\r\n    NEW FEATURE: Filter files and directories by name.\r\n    NEW FEATURE: Walk Full Tree.\r\n    NEW FEATURE: Ability to not check files.\r\n    Fixed for git behaviour change observed with git 1.9.+\r\n    Reorganised some of the code, as it was a bit rubbish.","3":"    Version 4.0.0\r\n    \r\n    NEW FEATURE: Show only changed files.\r\n    NEW FEATURE: Filter files and directories by name.\r\n    NEW FEATURE: Walk Full Tree.\r\n    NEW FEATURE: Ability to not check files.\r\n    Fixed for git behaviour change observed with git 1.9.+\r\n    Reorganised some of the code, as it was a bit rubbish.","package":"vimgitlog-version_4.0.0.tar.gz","4":"vimgitlog-version_4.0.0.tar.gz","src_id":"23039","5":"23039","creation_date":"1426455153","6":"1426455153"},{"0":"4294","vim_version":"7.3","1":"7.3","script_version":"3.1.0","2":"3.1.0","version_comment":"There is a keyhandling change that might annoy, but I think it makes more sense this way. Soz, if that annoys.\r\n\r\n- Changed <cr> on code tree to open local (also added 'p' for previous version).\r\n- Set scrolloff to 999 in tree - to center the tree.\r\n- Added indicator for the directories and their status.\r\n- Fixed syntax highlighting.\r\n- Added 'x' to close the parent in tree view.","3":"There is a keyhandling change that might annoy, but I think it makes more sense this way. Soz, if that annoys.\r\n\r\n- Changed <cr> on code tree to open local (also added 'p' for previous version).\r\n- Set scrolloff to 999 in tree - to center the tree.\r\n- Added indicator for the directories and their status.\r\n- Fixed syntax highlighting.\r\n- Added 'x' to close the parent in tree view.","package":"vimgitlog-version_3.1.0.tar.gz","4":"vimgitlog-version_3.1.0.tar.gz","src_id":"20319","5":"20319","creation_date":"1370675761","6":"1370675761"},{"0":"4294","vim_version":"7.3","1":"7.3","script_version":"3.0.0","2":"3.0.0","version_comment":"submodules\r\nAnd now for the understatement. Added Sub-Module support. Simple.","3":"submodules\r\nAnd now for the understatement. Added Sub-Module support. Simple.","package":"vimgitlog-version_3.0.0.tar.gz","4":"vimgitlog-version_3.0.0.tar.gz","src_id":"20213","5":"20213","creation_date":"1369508160","6":"1369508160"},{"0":"4294","vim_version":"7.3","1":"7.3","script_version":"2.1.2","2":"2.1.2","version_comment":"Fixed a few issues.\r\n - Now centres (better) on tree window open.\r\n - Can be opened to default mode.\r\n - Tree now properly opens directories that are sub.","3":"Fixed a few issues.\r\n - Now centres (better) on tree window open.\r\n - Can be opened to default mode.\r\n - Tree now properly opens directories that are sub.","package":"vimgitlog-version_2.1.2.tar.gz","4":"vimgitlog-version_2.1.2.tar.gz","src_id":"20195","5":"20195","creation_date":"1369218203","6":"1369218203"},{"0":"4294","vim_version":"7.3","1":"7.3","script_version":"2.1.1","2":"2.1.1","version_comment":"Added History TreeView.\r\nFixed Hi-lighting\r\nFixed Branch window's off by one.","3":"Added History TreeView.\r\nFixed Hi-lighting\r\nFixed Branch window's off by one.","package":"vimgitlog-version_2.1.1.tar.gz","4":"vimgitlog-version_2.1.1.tar.gz","src_id":"20040","5":"20040","creation_date":"1367931504","6":"1367931504"},{"0":"4294","vim_version":"7.3","1":"7.3","script_version":"2.0.2","2":"2.0.2","version_comment":"Fixed broken syntax and toggle.","3":"Fixed broken syntax and toggle.","package":"vimgitlog-version_2.0.2.tar.gz","4":"vimgitlog-version_2.0.2.tar.gz","src_id":"19945","5":"19945","creation_date":"1366994818","6":"1366994818"},{"0":"4294","vim_version":"7.3","1":"7.3","script_version":"2.0.1","2":"2.0.1","version_comment":"Incorrect version released - now releasing the correct one.","3":"Incorrect version released - now releasing the correct one.","package":"vimgitlog-version_2.0.1.tar.gz","4":"vimgitlog-version_2.0.1.tar.gz","src_id":"19944","5":"19944","creation_date":"1366992812","6":"1366992812"},{"0":"4294","vim_version":"7.3","1":"7.3","script_version":"2.0.0","2":"2.0.0","version_comment":"Added the ability to walk a revision tree for any commit.\r\nFixed bug in the branch window.","3":"Added the ability to walk a revision tree for any commit.\r\nFixed bug in the branch window.","package":"vimgitlog-version_2.0.0.tar.gz","4":"vimgitlog-version_2.0.0.tar.gz","src_id":"19939","5":"19939","creation_date":"1366971690","6":"1366971690"},{"0":"4294","vim_version":"7.3","1":"7.3","script_version":"1.3.1","2":"1.3.1","version_comment":"Fixed problem with marge branches not being diff'ed and fixed syntax highlighting to handle the branches.","3":"Fixed problem with marge branches not being diff'ed and fixed syntax highlighting to handle the branches.","package":"vimgitlog-version_1.3.1.tar.gz","4":"vimgitlog-version_1.3.1.tar.gz","src_id":"19647","5":"19647","creation_date":"1363342101","6":"1363342101"},{"0":"4294","vim_version":"7.3","1":"7.3","script_version":"1.3.0","2":"1.3.0","version_comment":"Added console support. Changed the way that files are loaded.","3":"Added console support. Changed the way that files are loaded.","package":"vimgitlog-version_1.3.0.tar.gz","4":"vimgitlog-version_1.3.0.tar.gz","src_id":"19331","5":"19331","creation_date":"1357677775","6":"1357677775"},{"0":"4294","vim_version":"7.3","1":"7.3","script_version":"1.2.0","2":"1.2.0","version_comment":"Added repository history search.\r\nJust select the commits in the log window and press 's' and then type in the search string and it will display a list of searches. The '<cr>' and 'o' keys will handle work the same as in the log window.","3":"Added repository history search.\r\nJust select the commits in the log window and press 's' and then type in the search string and it will display a list of searches. The '<cr>' and 'o' keys will handle work the same as in the log window.","package":"vimgitlog-version_1.2.0.tar.gz","4":"vimgitlog-version_1.2.0.tar.gz","src_id":"19187","5":"19187","creation_date":"1355575831","6":"1355575831"},{"0":"4294","vim_version":"7.0","1":"7.0","script_version":"1.1.2","2":"1.1.2","version_comment":"Fixed broken plugin. Also fixed issue that was caused if a branch name had special chars that the \"system\" callout did not like stopping the log from getting the branch information.","3":"Fixed broken plugin. Also fixed issue that was caused if a branch name had special chars that the \"system\" callout did not like stopping the log from getting the branch information.","package":"vimgitlog-version_1.1.2.tar.gz","4":"vimgitlog-version_1.1.2.tar.gz","src_id":"19160","5":"19160","creation_date":"1355139115","6":"1355139115"},{"0":"4294","vim_version":"7.0","1":"7.0","script_version":"1.1.1","2":"1.1.1","version_comment":"Fixed\/Added the ability to git diff files that are not in a repository that is a parent of the current one. Note sure if that is a fix or a new feature.","3":"Fixed\/Added the ability to git diff files that are not in a repository that is a parent of the current one. Note sure if that is a fix or a new feature.","package":"vimgitlog-version_1.1.1.tar.gz","4":"vimgitlog-version_1.1.1.tar.gz","src_id":"19036","5":"19036","creation_date":"1353936967","6":"1353936967"},{"0":"4294","vim_version":"7.0","1":"7.0","script_version":"1.1.0","2":"1.1.0","version_comment":"Initial upload","3":"Initial upload","package":"vimgitlog-version_1.1.0.tar.gz","4":"vimgitlog-version_1.1.0.tar.gz","src_id":"18900","5":"18900","creation_date":"1351325960","6":"1351325960"}]},"4293":{"script_id":"4293","0":"4293","script_name":"STL Syntax","1":"STL Syntax","script_type":"syntax","2":"syntax","summary":"Improved C++17 STL syntax highlighting ","3":"Improved C++17 STL syntax highlighting ","description":"Inspired by vimscript #2224\r\n\r\nGithub: https:\/\/github.com\/Mizuchi\/STL-Syntax","4":"Inspired by vimscript #2224\r\n\r\nGithub: https:\/\/github.com\/Mizuchi\/STL-Syntax","install_details":"copy stl.vim to .vim\/after\/syntax\/cpp\/stl.vim","5":"copy stl.vim to .vim\/after\/syntax\/cpp\/stl.vim","first_name":"Tianjiao","6":"Tianjiao","last_name":"Yin","7":"Yin","releases":[{"0":"4293","vim_version":"7.0","1":"7.0","script_version":"0.931","2":"0.931","version_comment":"fix extension name","3":"fix extension name","package":"stl.vim","4":"stl.vim","src_id":"26990","5":"26990","creation_date":"1581743366","6":"1581743366"},{"0":"4293","vim_version":"7.0","1":"7.0","script_version":"0.93","2":"0.93","version_comment":"Add C++17 stuffs","3":"Add C++17 stuffs","package":"stl.vim.txt","4":"stl.vim.txt","src_id":"26977","5":"26977","creation_date":"1581404354","6":"1581404354"},{"0":"4293","vim_version":"7.0","1":"7.0","script_version":"0.92","2":"0.92","version_comment":"add more","3":"add more","package":"stl.vim","4":"stl.vim","src_id":"22034","5":"22034","creation_date":"1402949130","6":"1402949130"},{"0":"4293","vim_version":"7.0","1":"7.0","script_version":"0.91","2":"0.91","version_comment":"fixed some bugs","3":"fixed some bugs","package":"stl.vim","4":"stl.vim","src_id":"21790","5":"21790","creation_date":"1397802763","6":"1397802763"},{"0":"4293","vim_version":"7.0","1":"7.0","script_version":"0.9","2":"0.9","version_comment":"1 add missiong iostream stuff\r\n2 change numeric_limits from function to type","3":"1 add missiong iostream stuff\r\n2 change numeric_limits from function to type","package":"stl.vim","4":"stl.vim","src_id":"21599","5":"21599","creation_date":"1394572145","6":"1394572145"},{"0":"4293","vim_version":"7.0","1":"7.0","script_version":"0.8","2":"0.8","version_comment":"add more missing stuff","3":"add more missing stuff","package":"stl.vim","4":"stl.vim","src_id":"21578","5":"21578","creation_date":"1394151660","6":"1394151660"},{"0":"4293","vim_version":"7.0","1":"7.0","script_version":"0.7","2":"0.7","version_comment":"add duration_cast, time_point_cast, lexical_cast","3":"add duration_cast, time_point_cast, lexical_cast","package":"stl.vim","4":"stl.vim","src_id":"21568","5":"21568","creation_date":"1393876373","6":"1393876373"},{"0":"4293","vim_version":"7.0","1":"7.0","script_version":"0.6","2":"0.6","version_comment":"1. add seconds, minutes, ... in std::chrono\r\n2. add some missing things, such as make_shared, get_deleter, etc","3":"1. add seconds, minutes, ... in std::chrono\r\n2. add some missing things, such as make_shared, get_deleter, etc","package":"stl.vim","4":"stl.vim","src_id":"21511","5":"21511","creation_date":"1392853060","6":"1392853060"},{"0":"4293","vim_version":"7.0","1":"7.0","script_version":"0.5","2":"0.5","version_comment":"Silly bug: time_t is a type, not a function!","3":"Silly bug: time_t is a type, not a function!","package":"stl.vim","4":"stl.vim","src_id":"21408","5":"21408","creation_date":"1391128065","6":"1391128065"},{"0":"4293","vim_version":"7.0","1":"7.0","script_version":"0.4","2":"0.4","version_comment":"add missing atomic_* type","3":"add missing atomic_* type","package":"stl.vim","4":"stl.vim","src_id":"21314","5":"21314","creation_date":"1389650857","6":"1389650857"},{"0":"4293","vim_version":"7.0","1":"7.0","script_version":"0.3","2":"0.3","version_comment":"Add some missing keyword and add support for C++14","3":"Add some missing keyword and add support for C++14","package":"stl.vim","4":"stl.vim","src_id":"20923","5":"20923","creation_date":"1381896059","6":"1381896059"},{"0":"4293","vim_version":"7.0","1":"7.0","script_version":"0.2","2":"0.2","version_comment":"fix: \"equal\" is a function in <algorithm>, not a functor.","3":"fix: \"equal\" is a function in <algorithm>, not a functor.","package":"stl.vim","4":"stl.vim","src_id":"18912","5":"18912","creation_date":"1351403423","6":"1351403423"},{"0":"4293","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"stl.vim","4":"stl.vim","src_id":"18895","5":"18895","creation_date":"1351254480","6":"1351254480"}]},"4292":{"script_id":"4292","0":"4292","script_name":"py-coverage","1":"py-coverage","script_type":"ftplugin","2":"ftplugin","summary":"Show python coverage results","3":"Show python coverage results","description":"py-coverage integrates with Ned Batchelder's code coverage tool for Python\r\n(http:\/\/nedbatchelder.com\/code\/coverage\/). After coverage data has been\r\ngathered, this plugin can be used to retrieve the results and present them in\r\nthe relevant buffers.\r\n\r\nSource lines lacking coverage (\"missing\") may be indicated by directly\r\nhighlighting the lines or by populating the quickfix or location lists. The\r\nfunction that retrieves the line numbers is also provided for low-level\r\naccess.\r\n\r\n:PyCoverageHighlight - Add missing lines in the current buffer to the PyCoverageMissing highlight group.\r\n:PyCoverageClear - Remove highlighting.\r\n:PyCoverageRemove - Remove highlighting and delete .coverage file.\r\n:PyCoverageSetQuickfix - Set the quickfix list to missing lines.\r\n:PyCoverageSetLoclist - Set the window's location list to the missing lines.\r\n\r\nPyCoverageMissingLines(buffer) - Return missing line numbers for the given buffer as a List.","4":"py-coverage integrates with Ned Batchelder's code coverage tool for Python\r\n(http:\/\/nedbatchelder.com\/code\/coverage\/). After coverage data has been\r\ngathered, this plugin can be used to retrieve the results and present them in\r\nthe relevant buffers.\r\n\r\nSource lines lacking coverage (\"missing\") may be indicated by directly\r\nhighlighting the lines or by populating the quickfix or location lists. The\r\nfunction that retrieves the line numbers is also provided for low-level\r\naccess.\r\n\r\n:PyCoverageHighlight - Add missing lines in the current buffer to the PyCoverageMissing highlight group.\r\n:PyCoverageClear - Remove highlighting.\r\n:PyCoverageRemove - Remove highlighting and delete .coverage file.\r\n:PyCoverageSetQuickfix - Set the quickfix list to missing lines.\r\n:PyCoverageSetLoclist - Set the window's location list to the missing lines.\r\n\r\nPyCoverageMissingLines(buffer) - Return missing line numbers for the given buffer as a List.","install_details":"","5":"","first_name":"Peter","6":"Peter","last_name":"Sagerson","7":"Sagerson","releases":[{"0":"4292","vim_version":"7.0","1":"7.0","script_version":"0.1.2","2":"0.1.2","version_comment":"Added :PyCoverageRemove (effectively `coverage erase`).","3":"Added :PyCoverageRemove (effectively `coverage erase`).","package":"vim-py-coverage.zip","4":"vim-py-coverage.zip","src_id":"24494","5":"24494","creation_date":"1472952615","6":"1472952615"},{"0":"4292","vim_version":"7.0","1":"7.0","script_version":"0.1.1","2":"0.1.1","version_comment":"Better behavior when .coverage isn't found.","3":"Better behavior when .coverage isn't found.","package":"vim-py-coverage.zip","4":"vim-py-coverage.zip","src_id":"18974","5":"18974","creation_date":"1352847059","6":"1352847059"},{"0":"4292","vim_version":"7.0","1":"7.0","script_version":"0.1.0","2":"0.1.0","version_comment":"Documentation additions and fixes.","3":"Documentation additions and fixes.","package":"vim-py-coverage.zip","4":"vim-py-coverage.zip","src_id":"18896","5":"18896","creation_date":"1351277369","6":"1351277369"}]},"4291":{"script_id":"4291","0":"4291","script_name":"last_edit_marker.vim","1":"last_edit_marker.vim","script_type":"utility","2":"utility","summary":"Keybind to quickly return to the last code you edited.","3":"Keybind to quickly return to the last code you edited.","description":"Automatically adds a global mark whenever you leave Insert mode, so you can\r\neasily return to text you were last working on, even if you have moved to a\r\ndifferent buffer!  I tend to need this after I have been navigating around\r\nfiles to do some research.  This saves us from hitting Ctrl-O repeatedly!\r\n\r\nIt sets global marker Z so you can jump back with g'Z but this is also bound to\r\nthe C-Y key for convenience.\r\n\r\nISSUES: not all edits require Insert mode.  e.g. undo or 4r0\r\nAnd leaving Insert mode is not always an edit (e.g. Insert mode on a\r\nconqueterm, or i<Esc> aborted edit).\r\n","4":"Automatically adds a global mark whenever you leave Insert mode, so you can\r\neasily return to text you were last working on, even if you have moved to a\r\ndifferent buffer!  I tend to need this after I have been navigating around\r\nfiles to do some research.  This saves us from hitting Ctrl-O repeatedly!\r\n\r\nIt sets global marker Z so you can jump back with g'Z but this is also bound to\r\nthe C-Y key for convenience.\r\n\r\nISSUES: not all edits require Insert mode.  e.g. undo or 4r0\r\nAnd leaving Insert mode is not always an edit (e.g. Insert mode on a\r\nconqueterm, or i<Esc> aborted edit).\r\n","install_details":"drop in plugin\/\r\n\r\nEdit the script if you do not want to overwrite the C-Y keybind, or if you want to\r\nuse a different global marker than Z.","5":"drop in plugin\/\r\n\r\nEdit the script if you do not want to overwrite the C-Y keybind, or if you want to\r\nuse a different global marker than Z.","first_name":"joey","6":"joey","last_name":"twiddle","7":"twiddle","releases":[{"0":"4291","vim_version":"6.0","1":"6.0","script_version":"1.4","2":"1.4","version_comment":"Initial upload","3":"Initial upload","package":"last_edit_marker.vim","4":"last_edit_marker.vim","src_id":"18889","5":"18889","creation_date":"1351121949","6":"1351121949"}]},"4290":{"script_id":"4290","0":"4290","script_name":"back_to_recent_buffer.vim","1":"back_to_recent_buffer.vim","script_type":"utility","2":"utility","summary":"Goes back to the previous buffer (rather than C-O previous position).","3":"Goes back to the previous buffer (rather than C-O previous position).","description":"Sometimes I use Ctrl-] a few times to read some code, perhaps navigating up\r\nand down in the files I visit.  Then I want to get back to where I was\r\nbefore, but Ctrl-O may require a lot of hits.\r\n\r\nHere we introduce an alternative, that goes back to the previous file, not\r\nthe previous position.  The default mapping is on C-U.\r\n\r\nIf you would rather go back to the last piece of code you were editing, see\r\nlast_edit_marker.vim\r\n\r\nBUG TODO: If there is no previous buffer, will loop forever!  We could check\r\nto see if we don't move at all, then abort.\r\n","4":"Sometimes I use Ctrl-] a few times to read some code, perhaps navigating up\r\nand down in the files I visit.  Then I want to get back to where I was\r\nbefore, but Ctrl-O may require a lot of hits.\r\n\r\nHere we introduce an alternative, that goes back to the previous file, not\r\nthe previous position.  The default mapping is on C-U.\r\n\r\nIf you would rather go back to the last piece of code you were editing, see\r\nlast_edit_marker.vim\r\n\r\nBUG TODO: If there is no previous buffer, will loop forever!  We could check\r\nto see if we don't move at all, then abort.\r\n","install_details":"drop in plugin\/\r\n\r\nEdit the mapping in the script if you do not want it to overwrite C-U.","5":"drop in plugin\/\r\n\r\nEdit the mapping in the script if you do not want it to overwrite C-U.","first_name":"joey","6":"joey","last_name":"twiddle","7":"twiddle","releases":[{"0":"4290","vim_version":"6.0","1":"6.0","script_version":"1.3","2":"1.3","version_comment":"Initial upload","3":"Initial upload","package":"back_to_recent_buffer.vim","4":"back_to_recent_buffer.vim","src_id":"18888","5":"18888","creation_date":"1351121692","6":"1351121692"}]},"4289":{"script_id":"4289","0":"4289","script_name":"blinking_statusline.vim","1":"blinking_statusline.vim","script_type":"utility","2":"utility","summary":"Briefly flash the status line of the focused window whenever you change window.","3":"Briefly flash the status line of the focused window whenever you change window.","description":"Blinks the status line of the newly focused window whenever you change window, by switching its highlight between \r\nStatusLineLit and StatusLineUnLit on WinEnter and CursorHold events.\r\n\r\nCan be helpful to visually track which window you have moved to.","4":"Blinks the status line of the newly focused window whenever you change window, by switching its highlight between \r\nStatusLineLit and StatusLineUnLit on WinEnter and CursorHold events.\r\n\r\nCan be helpful to visually track which window you have moved to.","install_details":"Drop in plugin\/\r\n\r\nAdd to your .vimrc:\r\n\r\n:let g:blinking_statusline = 1\r\n\r\nEdit the script to select the colours you want (or overwrite them at runtime).","5":"Drop in plugin\/\r\n\r\nAdd to your .vimrc:\r\n\r\n:let g:blinking_statusline = 1\r\n\r\nEdit the script to select the colours you want (or overwrite them at runtime).","first_name":"joey","6":"joey","last_name":"twiddle","7":"twiddle","releases":[{"0":"4289","vim_version":"6.0","1":"6.0","script_version":"0.9","2":"0.9","version_comment":"Initial upload","3":"Initial upload","package":"blinking_statusline.vim","4":"blinking_statusline.vim","src_id":"18887","5":"18887","creation_date":"1351121248","6":"1351121248"}]},"4288":{"script_id":"4288","0":"4288","script_name":"highlight_line_after_jump.vim","1":"highlight_line_after_jump.vim","script_type":"utility","2":"utility","summary":"Briefly highlights the cursor line whenever the cursor jumps vertically.","3":"Briefly highlights the cursor line whenever the cursor jumps vertically.","description":"Briefly highlights the cursor line whenever the cursor jumps vertically on\r\nthe screen.\r\n\r\nUseful if you keep losing where your cursor is when jumping around!\r\n\r\nCan use cursorline, or its own implementation.\r\n\r\n","4":"Briefly highlights the cursor line whenever the cursor jumps vertically on\r\nthe screen.\r\n\r\nUseful if you keep losing where your cursor is when jumping around!\r\n\r\nCan use cursorline, or its own implementation.\r\n\r\n","install_details":"drop in plugin\/\r\n\r\nOptions:\r\n\r\n:let g:hiline_min_lines = 3    \" only flashes the line after moving at least this far","5":"drop in plugin\/\r\n\r\nOptions:\r\n\r\n:let g:hiline_min_lines = 3    \" only flashes the line after moving at least this far","first_name":"joey","6":"joey","last_name":"twiddle","7":"twiddle","releases":[{"0":"4288","vim_version":"7.0","1":"7.0","script_version":"1.15","2":"1.15","version_comment":"Initial upload","3":"Initial upload","package":"highlight_line_after_jump.vim","4":"highlight_line_after_jump.vim","src_id":"18886","5":"18886","creation_date":"1351120604","6":"1351120604"}]},"4287":{"script_id":"4287","0":"4287","script_name":"highlight_word_under_cursor.vim","1":"highlight_word_under_cursor.vim","script_type":"utility","2":"utility","summary":"Temporary highlighting of all occurrences of the currently focused word.","3":"Temporary highlighting of all occurrences of the currently focused word.","description":"When you focus on a new word, all other occurrences of the word are lit up in red.\r\n\r\nIf you move again but remain on the same word, the highlight is removed.  So e.g. I just hit Space when I want to undo the highlighting.","4":"When you focus on a new word, all other occurrences of the word are lit up in red.\r\n\r\nIf you move again but remain on the same word, the highlight is removed.  So e.g. I just hit Space when I want to undo the highlighting.","install_details":"Drop in plugin\/\r\n\r\nIf you want to also highlight words which *contain* the current word, without being an exact match:\r\n\r\n:let g:hiword_partial = 1","5":"Drop in plugin\/\r\n\r\nIf you want to also highlight words which *contain* the current word, without being an exact match:\r\n\r\n:let g:hiword_partial = 1","first_name":"joey","6":"joey","last_name":"twiddle","7":"twiddle","releases":[{"0":"4287","vim_version":"7.0","1":"7.0","script_version":"1.14","2":"1.14","version_comment":"Initial upload","3":"Initial upload","package":"highlight_word_under_cursor.vim","4":"highlight_word_under_cursor.vim","src_id":"18885","5":"18885","creation_date":"1351120396","6":"1351120396"}]},"4286":{"script_id":"4286","0":"4286","script_name":"navigation_enhancer.vim","1":"navigation_enhancer.vim","script_type":"utility","2":"utility","summary":"When moving between windows, uses history not cursor position to select target.","3":"When moving between windows, uses history not cursor position to select target.","description":"Navigation Enhancer v2.0 by joey.neuralyte.org\r\n\r\naka Retrace Your Steps\r\n\r\nWhen moving the cursor between windows, given a choice of target windows,\r\nVim normally uses the *cursor position* to choose the destination window.\r\n\r\nHowever I think a more intuitive approach when there may be more than one\r\npotential target window is to pick the one which was *used most recently*.\r\n\r\nOr perhaps more accurately, we want the window that we *last entered from, in\r\nthat direction*.\r\n\r\nSo now if I casually move between windows in one direction, and then in the\r\nopposite direction, I should always return to the window I started from!\r\n","4":"Navigation Enhancer v2.0 by joey.neuralyte.org\r\n\r\naka Retrace Your Steps\r\n\r\nWhen moving the cursor between windows, given a choice of target windows,\r\nVim normally uses the *cursor position* to choose the destination window.\r\n\r\nHowever I think a more intuitive approach when there may be more than one\r\npotential target window is to pick the one which was *used most recently*.\r\n\r\nOr perhaps more accurately, we want the window that we *last entered from, in\r\nthat direction*.\r\n\r\nSo now if I casually move between windows in one direction, and then in the\r\nopposite direction, I should always return to the window I started from!\r\n","install_details":"drop in plugin\/\r\n\r\nCheck the mappings in the script to check that it intercepts the keys you use for window navigation.  (If C-W k or C-W-Up then fine.)","5":"drop in plugin\/\r\n\r\nCheck the mappings in the script to check that it intercepts the keys you use for window navigation.  (If C-W k or C-W-Up then fine.)","first_name":"joey","6":"joey","last_name":"twiddle","7":"twiddle","releases":[{"0":"4286","vim_version":"7.0","1":"7.0","script_version":"2.0","2":"2.0","version_comment":"Initial upload","3":"Initial upload","package":"navigation_enhancer.vim","4":"navigation_enhancer.vim","src_id":"18884","5":"18884","creation_date":"1351119928","6":"1351119928"}]},"4285":{"script_id":"4285","0":"4285","script_name":"toggle_maximize.vim","1":"toggle_maximize.vim","script_type":"utility","2":"utility","summary":"Keybinds to temporarily maximize the current window, squashing the rest.","3":"Keybinds to temporarily maximize the current window, squashing the rest.","description":"Vim can support complex window layouts, but they can put users off because\r\nthey reduce the size of the main editing window.  ToggleMaximize addresses\r\nthis issue, by allowing the user to switch between a large editor window,\r\nand his own complex window layout.\r\n\r\nPress Ctrl-F or Ctrl-\\ to maximize the size of the current window, press\r\nagain to restore the original window layout.\r\n\r\nCtrl-V and Ctrl-H toggle maximize in vertical\/horizontal direction only.\r\n\r\nMaximization is forced to respect winminwidth and winminheight, so if you\r\nhave these set, other windows will not fully shrink to the edges.\r\n\r\nIf the user changes the size of any windows after maximizing, the script\r\nstill thinks the toggle is ON, so next time it is used it will restore your\r\nold layout, rather than re-maximize (unlike some window managers).\r\n\r\n\r\n","4":"Vim can support complex window layouts, but they can put users off because\r\nthey reduce the size of the main editing window.  ToggleMaximize addresses\r\nthis issue, by allowing the user to switch between a large editor window,\r\nand his own complex window layout.\r\n\r\nPress Ctrl-F or Ctrl-\\ to maximize the size of the current window, press\r\nagain to restore the original window layout.\r\n\r\nCtrl-V and Ctrl-H toggle maximize in vertical\/horizontal direction only.\r\n\r\nMaximization is forced to respect winminwidth and winminheight, so if you\r\nhave these set, other windows will not fully shrink to the edges.\r\n\r\nIf the user changes the size of any windows after maximizing, the script\r\nstill thinks the toggle is ON, so next time it is used it will restore your\r\nold layout, rather than re-maximize (unlike some window managers).\r\n\r\n\r\n","install_details":"drop it in plugin\/\r\n\r\nEdit the bottom of the file to choose what keys you want to use.\r\n\r\nDefault keys are:\r\n  C-F     toggle maximize\r\n  C-V     toggle vertical maximize\r\n  C-H    toggle horizontal maximize","5":"drop it in plugin\/\r\n\r\nEdit the bottom of the file to choose what keys you want to use.\r\n\r\nDefault keys are:\r\n  C-F     toggle maximize\r\n  C-V     toggle vertical maximize\r\n  C-H    toggle horizontal maximize","first_name":"joey","6":"joey","last_name":"twiddle","7":"twiddle","releases":[{"0":"4285","vim_version":"6.0","1":"6.0","script_version":"1.28","2":"1.28","version_comment":"Better compatibility with windows_remember_size.vim","3":"Better compatibility with windows_remember_size.vim","package":"toggle_maximize.vim","4":"toggle_maximize.vim","src_id":"20448","5":"20448","creation_date":"1372278131","6":"1372278131"},{"0":"4285","vim_version":"7.0","1":"7.0","script_version":"1.27","2":"1.27","version_comment":"Initial upload","3":"Initial upload","package":"toggle_maximize.vim","4":"toggle_maximize.vim","src_id":"18883","5":"18883","creation_date":"1351119498","6":"1351119498"}]},"4284":{"script_id":"4284","0":"4284","script_name":"windows_remember_size.vim","1":"windows_remember_size.vim","script_type":"utility","2":"utility","summary":"Expands the current window when focused to the size you last gave it.","3":"Expands the current window when focused to the size you last gave it.","description":"== New version: tries to automatically keep up without whatever layout changes\r\nyou make, by storing an unfocused and focused size for each window. ==\r\n\r\nExplanation: Whenever you leave a window, it remembers what size it was, and\r\nwhenever you enter a window, it remembers what size it was before entering.\r\nThus it records \"focused\" and \"unfocused\" sizes for each window, and it will\r\ntry to grow\/shrink windows on entering\/leaving, to match the recorded value.\r\n\r\nNote: This system is not perfect, specifically when adding a new window\r\n(changing the layout) it makes no attempt to redistribute the space, so\r\nother windows will act greedily until they are adjusted.\r\n\r\nSolution: The best approach appears to be, as soon as your layout breaks in\r\nsome way, fix it immediately with 20<C-W>+ or whatever, to minimize the\r\ndamage (before the new broken values get recorded).  This is a small overhead\r\nfor the user, in exchange for the benefit gained with a fixed number of windows.\r\n\r\nIf you want to start afresh you can :call ForgetWindowSizes() and then Ctrl-=.\r\n\r\nOptions:\r\n\r\nNew feature: Set a default height for newly split windows, as percentage of\r\nthe size of the original window.  Without it Vim usually splits 50-50.\r\n\r\nlet g:wrs_default_height_pct = 90\r\n\r\nWe \"detect\" when a split is about to occur by mapping <Ctrl-W>s and :h\r\nbelow.  You may want to add more mappings for other splitting actions.","4":"== New version: tries to automatically keep up without whatever layout changes\r\nyou make, by storing an unfocused and focused size for each window. ==\r\n\r\nExplanation: Whenever you leave a window, it remembers what size it was, and\r\nwhenever you enter a window, it remembers what size it was before entering.\r\nThus it records \"focused\" and \"unfocused\" sizes for each window, and it will\r\ntry to grow\/shrink windows on entering\/leaving, to match the recorded value.\r\n\r\nNote: This system is not perfect, specifically when adding a new window\r\n(changing the layout) it makes no attempt to redistribute the space, so\r\nother windows will act greedily until they are adjusted.\r\n\r\nSolution: The best approach appears to be, as soon as your layout breaks in\r\nsome way, fix it immediately with 20<C-W>+ or whatever, to minimize the\r\ndamage (before the new broken values get recorded).  This is a small overhead\r\nfor the user, in exchange for the benefit gained with a fixed number of windows.\r\n\r\nIf you want to start afresh you can :call ForgetWindowSizes() and then Ctrl-=.\r\n\r\nOptions:\r\n\r\nNew feature: Set a default height for newly split windows, as percentage of\r\nthe size of the original window.  Without it Vim usually splits 50-50.\r\n\r\nlet g:wrs_default_height_pct = 90\r\n\r\nWe \"detect\" when a split is about to occur by mapping <Ctrl-W>s and :h\r\nbelow.  You may want to add more mappings for other splitting actions.","install_details":"Drop in plugin\/ folder","5":"Drop in plugin\/ folder","first_name":"joey","6":"joey","last_name":"twiddle","7":"twiddle","releases":[{"0":"4284","vim_version":"6.0","1":"6.0","script_version":"4.0","2":"4.0","version_comment":"Added new feature wrs_default_height_pct.  Do try this out.  Gives 90% of Vim's height to the currently focused window.  (Adds a little complexity to what was a tiny script.)\r\n\r\nAdded :noautocmd to ForgetWindowSizes, to prevent lots of events from firing.\r\n\r\nRemoved older implementation attempts.  See v3.0 for curiosity.","3":"Added new feature wrs_default_height_pct.  Do try this out.  Gives 90% of Vim's height to the currently focused window.  (Adds a little complexity to what was a tiny script.)\r\n\r\nAdded :noautocmd to ForgetWindowSizes, to prevent lots of events from firing.\r\n\r\nRemoved older implementation attempts.  See v3.0 for curiosity.","package":"windows_remember_size.vim","4":"windows_remember_size.vim","src_id":"20510","5":"20510","creation_date":"1373741857","6":"1373741857"},{"0":"4284","vim_version":"6.0","1":"6.0","script_version":"3.0","2":"3.0","version_comment":"Better compatibility with toggle_maximize.vim","3":"Better compatibility with toggle_maximize.vim","package":"windows_remember_size.vim","4":"windows_remember_size.vim","src_id":"20447","5":"20447","creation_date":"1372277786","6":"1372277786"},{"0":"4284","vim_version":"6.0","1":"6.0","script_version":"2.0","2":"2.0","version_comment":"Another alternative approach.","3":"Another alternative approach.","package":"windows_remember_size.vim","4":"windows_remember_size.vim","src_id":"18882","5":"18882","creation_date":"1351119195","6":"1351119195"},{"0":"4284","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"windows_remember_size.vim","4":"windows_remember_size.vim","src_id":"18881","5":"18881","creation_date":"1351119115","6":"1351119115"}]},"4283":{"script_id":"4283","0":"4283","script_name":"ctrlp-modified.vim","1":"ctrlp-modified.vim","script_type":"utility","2":"utility","summary":"Easily open locally modified files in your git-versioned projects.","3":"Easily open locally modified files in your git-versioned projects.","description":"A ctrlp extension to list locally modified files in your git-versioned projects.\r\n\r\nmap <Leader>m :CtrlPModified<CR>\r\n\r\nSource: https:\/\/github.com\/jasoncodes\/ctrlp-modified.vim\/tags","4":"A ctrlp extension to list locally modified files in your git-versioned projects.\r\n\r\nmap <Leader>m :CtrlPModified<CR>\r\n\r\nSource: https:\/\/github.com\/jasoncodes\/ctrlp-modified.vim\/tags","install_details":"Add ctrlp-modified after ctrlp in your Vundle config:\r\n\r\nBundle \\'kien\/ctrlp.vim\\'\r\nBundle \\'jasoncodes\/ctrlp-modified.vim\\'\r\n","5":"Add ctrlp-modified after ctrlp in your Vundle config:\r\n\r\nBundle \\'kien\/ctrlp.vim\\'\r\nBundle \\'jasoncodes\/ctrlp-modified.vim\\'\r\n","first_name":"Jason","6":"Jason","last_name":"Weathered","7":"Weathered","releases":[{"0":"4283","vim_version":"7.0","1":"7.0","script_version":"0.1.0","2":"0.1.0","version_comment":"Initial upload","3":"Initial upload","package":"jasoncodes-ctrlp-modified.vim-v0.1.0-0-g9650669.zip","4":"jasoncodes-ctrlp-modified.vim-v0.1.0-0-g9650669.zip","src_id":"18880","5":"18880","creation_date":"1351119035","6":"1351119035"}]},"4282":{"script_id":"4282","0":"4282","script_name":"breakindent_beta.vim","1":"breakindent_beta.vim","script_type":"utility","2":"utility","summary":"Improves indentation of wrapped lines by updating showbreak for current line.","3":"Improves indentation of wrapped lines by updating showbreak for current line.","description":"BreakIndent Beta tries to make wrapped lines look neater and less disruptive, by updating showbreak to indent them to the same column as the currently focused line.\r\n\r\nWarning: Because it changes showbreak, it can cause lines to visibly shift up and down when a new indent is applied.  To reduce how often this happens, you can enable breakindent_update_rarely, breakindent_match_gap or breakindent_never_shrink.\r\n\r\nBreakIndent Beta is a pure vimscript alternative to the old breakindent patch, which I failed to get working smoothly in modern Vim.  Unlike the breakindent patch, this vimscript *cannot* present a different indent for each line.  Instead it updates the showbreak option to fit the indent of the current cursor line.  Unfortunately this means that showbreak can change often, and other lines on the display may not appear at the ideal indent.\r\n\r\nSome commands that may be useful when wrapping long lines:\r\n\r\n   :set wrap                  \" This script does nothing in nowrap mode\r\n   :set linebreak nolist      \" Break lines cleanly at word gaps, hides tabs\r\n   :set list                  \" Visible tabs, breaks words anywhere\r\n\r\n   :set textwidth=0\r\n   :set wrapmargin=0          \" Attempts to disable auto-linefeed when typing\r\n   :set formatopts-=cq\r\n\r\n   :highlight NonText ctermfg=darkblue     \" Theme your indent symbols\r\n   :let g:breakindent_match_gap = 1        \" Change breakindent settings\r\n","4":"BreakIndent Beta tries to make wrapped lines look neater and less disruptive, by updating showbreak to indent them to the same column as the currently focused line.\r\n\r\nWarning: Because it changes showbreak, it can cause lines to visibly shift up and down when a new indent is applied.  To reduce how often this happens, you can enable breakindent_update_rarely, breakindent_match_gap or breakindent_never_shrink.\r\n\r\nBreakIndent Beta is a pure vimscript alternative to the old breakindent patch, which I failed to get working smoothly in modern Vim.  Unlike the breakindent patch, this vimscript *cannot* present a different indent for each line.  Instead it updates the showbreak option to fit the indent of the current cursor line.  Unfortunately this means that showbreak can change often, and other lines on the display may not appear at the ideal indent.\r\n\r\nSome commands that may be useful when wrapping long lines:\r\n\r\n   :set wrap                  \" This script does nothing in nowrap mode\r\n   :set linebreak nolist      \" Break lines cleanly at word gaps, hides tabs\r\n   :set list                  \" Visible tabs, breaks words anywhere\r\n\r\n   :set textwidth=0\r\n   :set wrapmargin=0          \" Attempts to disable auto-linefeed when typing\r\n   :set formatopts-=cq\r\n\r\n   :highlight NonText ctermfg=darkblue     \" Theme your indent symbols\r\n   :let g:breakindent_match_gap = 1        \" Change breakindent settings\r\n","install_details":"Drop the script in your plugin folder, or just source it when you need it.\r\n\r\nSee the source code for options, all of which can be changed at runtime through global vars.","5":"Drop the script in your plugin folder, or just source it when you need it.\r\n\r\nSee the source code for options, all of which can be changed at runtime through global vars.","first_name":"joey","6":"joey","last_name":"twiddle","7":"twiddle","releases":[{"0":"4282","vim_version":"6.0","1":"6.0","script_version":"1.6","2":"1.6","version_comment":"Latest stable well-documented version.","3":"Latest stable well-documented version.","package":"breakindent_beta.vim","4":"breakindent_beta.vim","src_id":"18879","5":"18879","creation_date":"1351118527","6":"1351118527"},{"0":"4282","vim_version":"7.0","1":"7.0","script_version":"1.2","2":"1.2","version_comment":"Added support for breakindent_match_gap","3":"Added support for breakindent_match_gap","package":"breakindent_beta.vim","4":"breakindent_beta.vim","src_id":"18878","5":"18878","creation_date":"1351118472","6":"1351118472"},{"0":"4282","vim_version":"6.0","1":"6.0","script_version":"1.1","2":"1.1","version_comment":"Initial upload","3":"Initial upload","package":"breakindent_beta.vim","4":"breakindent_beta.vim","src_id":"18877","5":"18877","creation_date":"1351118363","6":"1351118363"}]},"4281":{"script_id":"4281","0":"4281","script_name":"yars","1":"yars","script_type":"syntax","2":"syntax","summary":"Yet Another reStructuredText Syntax","3":"Yet Another reStructuredText Syntax","description":"Add support:\r\n* \".. code-block::\"\r\n* \".. math::\"\r\n* \".. graphviz::\"\r\n* rst list syntax\r\n\r\nPS: I already send a patch to the maintainer, didn't get response yet.  Maybe in the future, official syntax would contain my patch.  Anyway I released it as a plugin, since maybe someone would need this.  If you have any problem, contact me by e-mail.\r\n\r\nThis plugin contains some codes from vimscript #4112. This is a good plugin, though it does not fit my taste.\r\n","4":"Add support:\r\n* \".. code-block::\"\r\n* \".. math::\"\r\n* \".. graphviz::\"\r\n* rst list syntax\r\n\r\nPS: I already send a patch to the maintainer, didn't get response yet.  Maybe in the future, official syntax would contain my patch.  Anyway I released it as a plugin, since maybe someone would need this.  If you have any problem, contact me by e-mail.\r\n\r\nThis plugin contains some codes from vimscript #4112. This is a good plugin, though it does not fit my taste.\r\n","install_details":"copy rst.vim to .vim\/syntax\/rst.vim","5":"copy rst.vim to .vim\/syntax\/rst.vim","first_name":"Tianjiao","6":"Tianjiao","last_name":"Yin","7":"Yin","releases":[{"0":"4281","vim_version":"7.0","1":"7.0","script_version":"0.2","2":"0.2","version_comment":"Merge with the newest official syntax.","3":"Merge with the newest official syntax.","package":"rst.vim","4":"rst.vim","src_id":"18939","5":"18939","creation_date":"1351865610","6":"1351865610"},{"0":"4281","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"rst.vim","4":"rst.vim","src_id":"18863","5":"18863","creation_date":"1350976729","6":"1350976729"}]},"4280":{"script_id":"4280","0":"4280","script_name":"bundler.vim","1":"bundler.vim","script_type":"utility","2":"utility","summary":"Lightweight support for Ruby's Bundler","3":"Lightweight support for Ruby's Bundler","description":"This is a lightweight bag of Vim goodies for Bundler (http:\/\/gembundler.com), best accompanied by rake.vim (vimscript #3669) and\/or rails.vim (vimscript #1567).\r\n\r\nFeatures:\r\n\r\n* :Bundle, which wraps bundle.\r\n* An internalized version of bundle open: :Bopen (and :Bsplit, :Btabedit, etc.).\r\n* 'path' and 'tags' are automatically altered to include all gems from your bundle.  (Generate those tags with gem-ctags (https:\/\/github.com\/tpope\/gem-ctags)!)\r\n* Syntax highlighting for Gemfile and Gemfile.lock.\r\n\r\nhttps:\/\/github.com\/tpope\/vim-bundler","4":"This is a lightweight bag of Vim goodies for Bundler (http:\/\/gembundler.com), best accompanied by rake.vim (vimscript #3669) and\/or rails.vim (vimscript #1567).\r\n\r\nFeatures:\r\n\r\n* :Bundle, which wraps bundle.\r\n* An internalized version of bundle open: :Bopen (and :Bsplit, :Btabedit, etc.).\r\n* 'path' and 'tags' are automatically altered to include all gems from your bundle.  (Generate those tags with gem-ctags (https:\/\/github.com\/tpope\/gem-ctags)!)\r\n* Syntax highlighting for Gemfile and Gemfile.lock.\r\n\r\nhttps:\/\/github.com\/tpope\/vim-bundler","install_details":"Extract in ~\/.vim (~\\vimfiles on Windows).","5":"Extract in ~\/.vim (~\\vimfiles on Windows).","first_name":"Tim","6":"Tim","last_name":"Pope","7":"Pope","releases":[{"0":"4280","vim_version":"7.4","1":"7.4","script_version":"2.2","2":"2.2","version_comment":"Support :Bundle open.\r\nDeprecate :Btabedit and friends in favor of using :Bundle open.\r\nImprove :Bundle tab completion.\r\nSupport <mods> like :vertical and :tab.\r\nDefine commands globally, not per buffer.\r\nSupport calling :Bundle gem\/:Bundle init without Gemfile.\r\nUpdate gem under cursor with :.Dispatch.\r\nSupport operation in URL buffers, like fugitive:\/\/.\r\nDrop support for abandoned gems.rb\/gems.locked.\r\nBump minimum Vim version to 7.4.\r\nPublic API tweaks.","3":"Support :Bundle open.\r\nDeprecate :Btabedit and friends in favor of using :Bundle open.\r\nImprove :Bundle tab completion.\r\nSupport <mods> like :vertical and :tab.\r\nDefine commands globally, not per buffer.\r\nSupport calling :Bundle gem\/:Bundle init without Gemfile.\r\nUpdate gem under cursor with :.Dispatch.\r\nSupport operation in URL buffers, like fugitive:\/\/.\r\nDrop support for abandoned gems.rb\/gems.locked.\r\nBump minimum Vim version to 7.4.\r\nPublic API tweaks.","package":"bundler.zip","4":"bundler.zip","src_id":"28539","5":"28539","creation_date":"1693119017","6":"1693119017"},{"0":"4280","vim_version":"7.0","1":"7.0","script_version":"2.1","2":"2.1","version_comment":"Numerous improvements to gem finding, robustness, and performance.\r\nSupport projectionist.vim, with per-gem projections.\r\nSupport gems.rb and gems.locked.\r\nSyntax highlighting tweaks.\r\nCease setting makeprg=bundler.\r\nFilter 'path' and 'tags' to sub-dependencies when navigating gems.","3":"Numerous improvements to gem finding, robustness, and performance.\r\nSupport projectionist.vim, with per-gem projections.\r\nSupport gems.rb and gems.locked.\r\nSyntax highlighting tweaks.\r\nCease setting makeprg=bundler.\r\nFilter 'path' and 'tags' to sub-dependencies when navigating gems.","package":"bundler.zip","4":"bundler.zip","src_id":"26015","5":"26015","creation_date":"1527836919","6":"1527836919"},{"0":"4280","vim_version":"7.0","1":"7.0","script_version":"2.0","2":"2.0","version_comment":"Fast, static lock file parser.\r\nProvide a \"bundler\" compiler plugin.\r\nPress gf on gems in lock file to open them.\r\nHighlight missing gems in lock file as errors.\r\nHighlight .bundler\/config as yaml.\r\nProvide an official API.","3":"Fast, static lock file parser.\r\nProvide a \"bundler\" compiler plugin.\r\nPress gf on gems in lock file to open them.\r\nHighlight missing gems in lock file as errors.\r\nHighlight .bundler\/config as yaml.\r\nProvide an official API.","package":"bundler.zip","4":"bundler.zip","src_id":"19666","5":"19666","creation_date":"1363745210","6":"1363745210"},{"0":"4280","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"bundler.zip","4":"bundler.zip","src_id":"18853","5":"18853","creation_date":"1350857168","6":"1350857168"}]},"4279":{"script_id":"4279","0":"4279","script_name":"vim-cmake-project","1":"vim-cmake-project","script_type":"utility","2":"utility","summary":"CMake project management in VIM","3":"CMake project management in VIM","description":"CMake-Project is a plugin for cmake projects effective management. It provides\r\na sidebar that displays project files in the tree view.\r\n\r\nGet latest changes from Github https:\/\/github.com\/Ignotus\/vim-cmake-project","4":"CMake-Project is a plugin for cmake projects effective management. It provides\r\na sidebar that displays project files in the tree view.\r\n\r\nGet latest changes from Github https:\/\/github.com\/Ignotus\/vim-cmake-project","install_details":"Change your current directory to the plugin root archive directory and use\r\ninstall methods:\r\n    $ make install","5":"Change your current directory to the plugin root archive directory and use\r\ninstall methods:\r\n    $ make install","first_name":"Minh","6":"Minh","last_name":"Ngo","7":"Ngo","releases":[{"0":"4279","vim_version":"7.0","1":"7.0","script_version":"2.0.1","2":"2.0.1","version_comment":"    - Absolute path support\r\n    - Avoid generating a CMakeProject in the current directory if a destination doesn't exists\r\n","3":"    - Absolute path support\r\n    - Avoid generating a CMakeProject in the current directory if a destination doesn't exists\r\n","package":"vim-cmake-project-2.0.1.zip","4":"vim-cmake-project-2.0.1.zip","src_id":"21973","5":"21973","creation_date":"1401607648","6":"1401607648"},{"0":"4279","vim_version":"7.0","1":"7.0","script_version":"2.0.0","2":"2.0.0","version_comment":"Source code has been rewritten in Python. Interface was simplified. Please read doc\/cmake-project.txt for details.","3":"Source code has been rewritten in Python. Interface was simplified. Please read doc\/cmake-project.txt for details.","package":"vim-cmake-project-2.0.0.zip","4":"vim-cmake-project-2.0.0.zip","src_id":"21518","5":"21518","creation_date":"1392987974","6":"1392987974"},{"0":"4279","vim_version":"7.0","1":"7.0","script_version":"1.1.5","2":"1.1.5","version_comment":"Adding header files into the project.\r\nSorting tree items before inserting.","3":"Adding header files into the project.\r\nSorting tree items before inserting.","package":"vim-cmake-project-1.1.5.zip","4":"vim-cmake-project-1.1.5.zip","src_id":"18924","5":"18924","creation_date":"1351544789","6":"1351544789"},{"0":"4279","vim_version":"7.3","1":"7.3","script_version":"1.1.0","2":"1.1.0","version_comment":"- Remembering a file position\r\n- Hiding unneeded upper path element","3":"- Remembering a file position\r\n- Hiding unneeded upper path element","package":"vim-cmake-project-1.1.0.zip","4":"vim-cmake-project-1.1.0.zip","src_id":"18891","5":"18891","creation_date":"1351193129","6":"1351193129"},{"0":"4279","vim_version":"7.3","1":"7.3","script_version":"1.0.1","2":"1.0.1","version_comment":"Fixing bugs","3":"Fixing bugs","package":"vim-cmake-project-1.0.1.zip","4":"vim-cmake-project-1.0.1.zip","src_id":"18857","5":"18857","creation_date":"1350893132","6":"1350893132"}]},"4278":{"script_id":"4278","0":"4278","script_name":"Makeshift","1":"Makeshift","script_type":"utility","2":"utility","summary":"Selects the right 'makeprg' for your build system","3":"Selects the right 'makeprg' for your build system","description":"Introduction\r\n\r\nYou'll want to use this plugin if you work on a lot of projects with different build systems. You want your editor to be able to detect your current build system and set 'makeprg' accordingly.\r\n\r\nTo make building really fast, map the :make command to a function key in your vimrc.\r\n\r\nnnoremap <F5> :<C-U>make<CR>\r\n\r\nHow it works\r\n\r\nThis plug-in works by looking for known build files in the current working directory upwards, and sets 'makeprg'; by default this happens on start-up. You can use the command to re-evaluate 'makeprg':\r\n\r\n:Makeshift\r\n\r\nSometimes your build script won't be in the current working directory, this is particularly common when 'autochdir' is set. For this reason :Makeshift sets b:makeshift_root to be the directory containing the build script that it used to determine the build system.\r\n\r\n:MakeshiftBuild is a wrapper around Vim's own :make command, which changes directory to b:makeshift_root before calling :make with any arguments you provide and then returns to your working directory. If you often work in subdirectories, you may want to map the :MakeshiftBuild command to a function key in your vimrc:\r\n\r\nnnoremap <F5> :<C-U>MakeshiftBuild<CR>\r\nnnoremap <F6> :<C-U>MakeshiftBuild check<CR>\r\n...\r\n\r\nAlternatively you can use the makeshift_chdir option to automatically change the current working directory to the one containing your build script.\r\n\r\nSettings\r\n\r\nTo tune the behaviour of this plugin, add any of the following switches to your vimrc:\r\n\r\nlet g:makeshift_on_startup = 0\r\n\r\nTo prevent Makeshift from setting 'makeprg' on BufRead:\r\n\r\nlet g:makeshift_on_bufread = 0\r\n\r\nTo prevent Makeshift from setting 'makeprg' on BufNewFile:\r\n\r\nlet g:makeshift_on_bufnewfile = 0\r\n\r\nTo prevent Makeshift from setting 'makeprg' on BufEnter:\r\n\r\nlet g:makeshift_on_bufenter = 0\r\n\r\nTo automatically change directory to 'b:makeshift_root' when it is discovered:\r\n\r\nlet g:makeshift_chdir = 1\r\n\r\nTo try the build file in the current directory before searching from the file directory:\r\n\r\nlet g:makeshift_use_pwd_first = 1\r\n\r\nTo enable search for bundled build program\/script:\r\n\r\nlet g:makeshift_find_bundled = 1\r\n\r\nBuild Systems\r\n\r\nMakeshift currently associates the following files with their build systems:\r\n\r\n* Jamfile: bjam\r\n* Makefile: make\r\n* GNUmakefile: make\r\n* Rakefile: rake\r\n* SConstruct: scons\r\n* build.gradle: gradle\r\n* build.xml: ant\r\n* mix.exs: mix\r\n* pom.xml: mvn\r\n* build.ninja: ninja\r\n* wscript: waf\r\n\r\nAdding a new build system\r\n\r\nIf Makeshift doesn't already know about your build system, or you wish to override the default program for a given file, you can define a dictionary, which has filenames as keys and corresponding programs as values.\r\n\r\nlet g:makeshift_systems = {\r\n    \\'build.sbt ': 'sbt',\r\n    \\}\r\n\r\nRemoving a build system\r\n\r\nIf you don't want Makeshift to set 'makeprg' for a given build system, you can disable it by defining a list of the files to ignore.\r\n\r\nlet g:makeshift_ignored = ['Jamfile']\r\n\r\nLicense\r\n\r\nMakeshift is licensed under the same terms as Vim itself (see :help license).\r\n\r\nThanks\r\n\r\nIf you find this plug-in useful, please follow this repository on GitHub and vote for it vim.org. If you have something to say, you can contact @johnsyweb on Twitter and GitHub.\r\n\r\nMany thanks\r\n\r\nI'm grateful for contributions to what was a solo project (hooray for GitHub)! If you'd like to thank the contributors, you can find their details here:\r\n\r\nhttps:\/\/github.com\/johnsyweb\/vim-makeshift\/graphs\/contributors\r\n\r\nYou can grab the latest version of this plugin, submit an improvement or report a bug on GitHub: \r\n\r\n   https:\/\/github.com\/johnsyweb\/vim-makeshift\r\n\r\n","4":"Introduction\r\n\r\nYou'll want to use this plugin if you work on a lot of projects with different build systems. You want your editor to be able to detect your current build system and set 'makeprg' accordingly.\r\n\r\nTo make building really fast, map the :make command to a function key in your vimrc.\r\n\r\nnnoremap <F5> :<C-U>make<CR>\r\n\r\nHow it works\r\n\r\nThis plug-in works by looking for known build files in the current working directory upwards, and sets 'makeprg'; by default this happens on start-up. You can use the command to re-evaluate 'makeprg':\r\n\r\n:Makeshift\r\n\r\nSometimes your build script won't be in the current working directory, this is particularly common when 'autochdir' is set. For this reason :Makeshift sets b:makeshift_root to be the directory containing the build script that it used to determine the build system.\r\n\r\n:MakeshiftBuild is a wrapper around Vim's own :make command, which changes directory to b:makeshift_root before calling :make with any arguments you provide and then returns to your working directory. If you often work in subdirectories, you may want to map the :MakeshiftBuild command to a function key in your vimrc:\r\n\r\nnnoremap <F5> :<C-U>MakeshiftBuild<CR>\r\nnnoremap <F6> :<C-U>MakeshiftBuild check<CR>\r\n...\r\n\r\nAlternatively you can use the makeshift_chdir option to automatically change the current working directory to the one containing your build script.\r\n\r\nSettings\r\n\r\nTo tune the behaviour of this plugin, add any of the following switches to your vimrc:\r\n\r\nlet g:makeshift_on_startup = 0\r\n\r\nTo prevent Makeshift from setting 'makeprg' on BufRead:\r\n\r\nlet g:makeshift_on_bufread = 0\r\n\r\nTo prevent Makeshift from setting 'makeprg' on BufNewFile:\r\n\r\nlet g:makeshift_on_bufnewfile = 0\r\n\r\nTo prevent Makeshift from setting 'makeprg' on BufEnter:\r\n\r\nlet g:makeshift_on_bufenter = 0\r\n\r\nTo automatically change directory to 'b:makeshift_root' when it is discovered:\r\n\r\nlet g:makeshift_chdir = 1\r\n\r\nTo try the build file in the current directory before searching from the file directory:\r\n\r\nlet g:makeshift_use_pwd_first = 1\r\n\r\nTo enable search for bundled build program\/script:\r\n\r\nlet g:makeshift_find_bundled = 1\r\n\r\nBuild Systems\r\n\r\nMakeshift currently associates the following files with their build systems:\r\n\r\n* Jamfile: bjam\r\n* Makefile: make\r\n* GNUmakefile: make\r\n* Rakefile: rake\r\n* SConstruct: scons\r\n* build.gradle: gradle\r\n* build.xml: ant\r\n* mix.exs: mix\r\n* pom.xml: mvn\r\n* build.ninja: ninja\r\n* wscript: waf\r\n\r\nAdding a new build system\r\n\r\nIf Makeshift doesn't already know about your build system, or you wish to override the default program for a given file, you can define a dictionary, which has filenames as keys and corresponding programs as values.\r\n\r\nlet g:makeshift_systems = {\r\n    \\'build.sbt ': 'sbt',\r\n    \\}\r\n\r\nRemoving a build system\r\n\r\nIf you don't want Makeshift to set 'makeprg' for a given build system, you can disable it by defining a list of the files to ignore.\r\n\r\nlet g:makeshift_ignored = ['Jamfile']\r\n\r\nLicense\r\n\r\nMakeshift is licensed under the same terms as Vim itself (see :help license).\r\n\r\nThanks\r\n\r\nIf you find this plug-in useful, please follow this repository on GitHub and vote for it vim.org. If you have something to say, you can contact @johnsyweb on Twitter and GitHub.\r\n\r\nMany thanks\r\n\r\nI'm grateful for contributions to what was a solo project (hooray for GitHub)! If you'd like to thank the contributors, you can find their details here:\r\n\r\nhttps:\/\/github.com\/johnsyweb\/vim-makeshift\/graphs\/contributors\r\n\r\nYou can grab the latest version of this plugin, submit an improvement or report a bug on GitHub: \r\n\r\n   https:\/\/github.com\/johnsyweb\/vim-makeshift\r\n\r\n","install_details":"I recommend installing pathogen.vim (vimscript#2332), and then simply copy and paste:\r\n\r\ncd ~\/.vim\/bundle\r\ngit clone git:\/\/github.com\/johnsyweb\/vim-makeshift.git\r\nvim -cHelptags\r\n\r\nOnce help tags have been generated, you can view the manual with\r\n\r\n:help makeshift\r\n\r\nAlternatively, just unzip the file into your 'runtimepath' and run :helptags.","5":"I recommend installing pathogen.vim (vimscript#2332), and then simply copy and paste:\r\n\r\ncd ~\/.vim\/bundle\r\ngit clone git:\/\/github.com\/johnsyweb\/vim-makeshift.git\r\nvim -cHelptags\r\n\r\nOnce help tags have been generated, you can view the manual with\r\n\r\n:help makeshift\r\n\r\nAlternatively, just unzip the file into your 'runtimepath' and run :helptags.","first_name":"Pete","6":"Pete","last_name":"Johns","7":"Johns","releases":[{"0":"4278","vim_version":"7.0","1":"7.0","script_version":"0.15.0","2":"0.15.0","version_comment":"https:\/\/github.com\/johnsyweb\/vim-makeshift\/releases\/tag\/0.15.0","3":"https:\/\/github.com\/johnsyweb\/vim-makeshift\/releases\/tag\/0.15.0","package":"vim-makeshift-0.15.0.zip","4":"vim-makeshift-0.15.0.zip","src_id":"24940","5":"24940","creation_date":"1485952693","6":"1485952693"},{"0":"4278","vim_version":"7.0","1":"7.0","script_version":"0.14.0","2":"0.14.0","version_comment":"https:\/\/github.com\/johnsyweb\/vim-makeshift\/releases\/tag\/0.14.0","3":"https:\/\/github.com\/johnsyweb\/vim-makeshift\/releases\/tag\/0.14.0","package":"vim-makeshift-0.14.0.zip","4":"vim-makeshift-0.14.0.zip","src_id":"22636","5":"22636","creation_date":"1416517814","6":"1416517814"},{"0":"4278","vim_version":"7.0","1":"7.0","script_version":"0.13.0","2":"0.13.0","version_comment":"https:\/\/github.com\/johnsyweb\/vim-makeshift\/compare\/0.12.0...0.13.0","3":"https:\/\/github.com\/johnsyweb\/vim-makeshift\/compare\/0.12.0...0.13.0","package":"vim-makeshift-0.13.0.zip","4":"vim-makeshift-0.13.0.zip","src_id":"22516","5":"22516","creation_date":"1413015496","6":"1413015496"},{"0":"4278","vim_version":"7.0","1":"7.0","script_version":"0.12.0","2":"0.12.0","version_comment":"https:\/\/github.com\/johnsyweb\/vim-makeshift\/compare\/0.11.0...0.12.0","3":"https:\/\/github.com\/johnsyweb\/vim-makeshift\/compare\/0.11.0...0.12.0","package":"vim-makeshift-0.12.0.zip","4":"vim-makeshift-0.12.0.zip","src_id":"21834","5":"21834","creation_date":"1398483253","6":"1398483253"},{"0":"4278","vim_version":"7.0","1":"7.0","script_version":"0.11.0","2":"0.11.0","version_comment":"https:\/\/github.com\/johnsyweb\/vim-makeshift\/compare\/0.10.0...0.11.0","3":"https:\/\/github.com\/johnsyweb\/vim-makeshift\/compare\/0.10.0...0.11.0","package":"vim-makeshift-0.11.0.zip","4":"vim-makeshift-0.11.0.zip","src_id":"21789","5":"21789","creation_date":"1397791638","6":"1397791638"},{"0":"4278","vim_version":"7.0","1":"7.0","script_version":"0.10.0","2":"0.10.0","version_comment":"https:\/\/github.com\/johnsyweb\/vim-makeshift\/compare\/v0.9...0.10.0","3":"https:\/\/github.com\/johnsyweb\/vim-makeshift\/compare\/v0.9...0.10.0","package":"vim-makeshift-0.10.0.zip","4":"vim-makeshift-0.10.0.zip","src_id":"21647","5":"21647","creation_date":"1395377846","6":"1395377846"},{"0":"4278","vim_version":"7.0","1":"7.0","script_version":"0.9","2":"0.9","version_comment":"https:\/\/github.com\/johnsyweb\/vim-makeshift\/compare\/v0.8...v0.9","3":"https:\/\/github.com\/johnsyweb\/vim-makeshift\/compare\/v0.8...v0.9","package":"vim-makeshift-0.9.zip","4":"vim-makeshift-0.9.zip","src_id":"21540","5":"21540","creation_date":"1393494847","6":"1393494847"},{"0":"4278","vim_version":"7.0","1":"7.0","script_version":"0.8","2":"0.8","version_comment":"Add support for Gradle (thanks to Simon Lundstr\u00c3\u00b6m)","3":"Add support for Gradle (thanks to Simon Lundstr\u00c3\u00b6m)","package":"vim-makeshift-0.8.zip","4":"vim-makeshift-0.8.zip","src_id":"21313","5":"21313","creation_date":"1389646538","6":"1389646538"},{"0":"4278","vim_version":"7.0","1":"7.0","script_version":"0.7","2":"0.7","version_comment":"Add g:makeshift_root and :MakeshiftBuild\r\nAllow for passing arguments to :MakeshiftBuild\r\nFix typo\r\nAdd help for g:makeshift_root and :MakeshiftBuild\r\nUpdate README for v0.7\r\nBump version to 0.7\r\n","3":"Add g:makeshift_root and :MakeshiftBuild\r\nAllow for passing arguments to :MakeshiftBuild\r\nFix typo\r\nAdd help for g:makeshift_root and :MakeshiftBuild\r\nUpdate README for v0.7\r\nBump version to 0.7\r\n","package":"vim-makeshift-0.7.zip","4":"vim-makeshift-0.7.zip","src_id":"20994","5":"20994","creation_date":"1383381043","6":"1383381043"},{"0":"4278","vim_version":"7.0","1":"7.0","script_version":"0.6","2":"0.6","version_comment":"13d7f84 makeshift_define_command works around issue #2\r\n8c6361a Admit issue\r\n3d36530 Tidy whitespace\r\n","3":"13d7f84 makeshift_define_command works around issue #2\r\n8c6361a Admit issue\r\n3d36530 Tidy whitespace\r\n","package":"vim-makeshift-0.6.zip","4":"vim-makeshift-0.6.zip","src_id":"20153","5":"20153","creation_date":"1368875317","6":"1368875317"},{"0":"4278","vim_version":"7.0","1":"7.0","script_version":"0.4","2":"0.4","version_comment":"* cccc476 - (HEAD, v0.4, origin\/master, master) v0.4 (7 minutes ago) <Pete Johns>\r\n* b46c503 - Don't set makeprg=0 if no makefile is found. (7 days ago) <Pete Johns>\r\n","3":"* cccc476 - (HEAD, v0.4, origin\/master, master) v0.4 (7 minutes ago) <Pete Johns>\r\n* b46c503 - Don't set makeprg=0 if no makefile is found. (7 days ago) <Pete Johns>\r\n","package":"vim-makeshift-0.4.zip","4":"vim-makeshift-0.4.zip","src_id":"19025","5":"19025","creation_date":"1353811993","6":"1353811993"},{"0":"4278","vim_version":"7.0","1":"7.0","script_version":"0.3","2":"0.3","version_comment":"* 3ed1848 - (HEAD, v0.3, origin\/master, master) Bumped version. (5 minutes ago) <Pete Johns>\r\n* ce66a04 - Automatic re-evaluation on BufRead (4 days ago) <Pete Johns>\r\n* 336dfe1 - Dig upwards for build system (4 days ago) <Pete Johns>\r\n","3":"* 3ed1848 - (HEAD, v0.3, origin\/master, master) Bumped version. (5 minutes ago) <Pete Johns>\r\n* ce66a04 - Automatic re-evaluation on BufRead (4 days ago) <Pete Johns>\r\n* 336dfe1 - Dig upwards for build system (4 days ago) <Pete Johns>\r\n","package":"johnsyweb-vim-makeshift-v0.3-0-g3ed1848.zip","4":"johnsyweb-vim-makeshift-v0.3-0-g3ed1848.zip","src_id":"18897","5":"18897","creation_date":"1351287337","6":"1351287337"},{"0":"4278","vim_version":"7.0","1":"7.0","script_version":"0.2","2":"0.2","version_comment":"Issue #1: CMake does not generate a Makefile ","3":"Issue #1: CMake does not generate a Makefile ","package":"makeshift.zip","4":"makeshift.zip","src_id":"18859","5":"18859","creation_date":"1350915047","6":"1350915047"},{"0":"4278","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"makeshift.zip","4":"makeshift.zip","src_id":"18849","5":"18849","creation_date":"1350808954","6":"1350808954"}]},"4277":{"script_id":"4277","0":"4277","script_name":"Sunset","1":"Sunset","script_type":"utility","2":"utility","summary":"Automatically set background on local sunrise\/sunset time.","3":"Automatically set background on local sunrise\/sunset time.","description":"INTRODUCTION:\r\n\r\nSunset automatically sets 'background' when the sun rises and sets, and also when you start Vim. When the sun is up, or rises, it'll 'set background=light'. When the sun is down, or sets, it'll 'set background=dark'.\r\n\r\nSunset can also change your 'colorscheme', your Powerline (https:\/\/github.com\/Lokaltog\/vim-powerline) theme, or anything else you can think of. See \u00e2\u0080\u0098Sunset_daytime_callback()' and \u00e2\u0080\u0098Sunset_nighttime_callback()' in the documentation for details.\r\n\r\nSo as not to interrupt you, Sunset waits for four seconds (on the CursorHold event) after you've pressed a key or left insert mode before changing the background. If you change your background during the day or night, it'll respect that.\r\n\r\nCONTRIBUTIONS:\r\n\r\nIf you feel that Sunset can be improved, pull requests and issues are appreciated and humbly requested, on Github at: http:\/\/github.com\/amdt\/sunset\r\n\r\nREQUIREMENTS:\r\n\r\nVim compiled with +float support. Use ':version' to check if this feature is available in your build.\r\n\r\nRequires a system with 'strftime()', with the following format options:\r\n- %j returns the current day of the year.\r\n- %H returns the current hour of the day in 24-hour time.\r\n- %M returns the current minute of the hour.\r\n\r\nA colorscheme with both light and dark variants, such as Solarized (http:\/\/github.com\/altercation\/vim-colors-solarized) or Hemisu (http:\/\/github.com\/noahfrederick\/Hemisu).","4":"INTRODUCTION:\r\n\r\nSunset automatically sets 'background' when the sun rises and sets, and also when you start Vim. When the sun is up, or rises, it'll 'set background=light'. When the sun is down, or sets, it'll 'set background=dark'.\r\n\r\nSunset can also change your 'colorscheme', your Powerline (https:\/\/github.com\/Lokaltog\/vim-powerline) theme, or anything else you can think of. See \u00e2\u0080\u0098Sunset_daytime_callback()' and \u00e2\u0080\u0098Sunset_nighttime_callback()' in the documentation for details.\r\n\r\nSo as not to interrupt you, Sunset waits for four seconds (on the CursorHold event) after you've pressed a key or left insert mode before changing the background. If you change your background during the day or night, it'll respect that.\r\n\r\nCONTRIBUTIONS:\r\n\r\nIf you feel that Sunset can be improved, pull requests and issues are appreciated and humbly requested, on Github at: http:\/\/github.com\/amdt\/sunset\r\n\r\nREQUIREMENTS:\r\n\r\nVim compiled with +float support. Use ':version' to check if this feature is available in your build.\r\n\r\nRequires a system with 'strftime()', with the following format options:\r\n- %j returns the current day of the year.\r\n- %H returns the current hour of the day in 24-hour time.\r\n- %M returns the current minute of the hour.\r\n\r\nA colorscheme with both light and dark variants, such as Solarized (http:\/\/github.com\/altercation\/vim-colors-solarized) or Hemisu (http:\/\/github.com\/noahfrederick\/Hemisu).","install_details":"Installation is provided here with a Vimball. See ':help vimball' for installation instructions. If you prefer a package manager or manual install, please see the previously mentioned Github page.","5":"Installation is provided here with a Vimball. See ':help vimball' for installation instructions. If you prefer a package manager or manual install, please see the previously mentioned Github page.","first_name":"Alastair","6":"Alastair","last_name":"Touw","7":"Touw","releases":[{"0":"4277","vim_version":"7.4","1":"7.4","script_version":"3.1.0","2":"3.1.0","version_comment":"* Made 'g:sunset_utc_offset' optional\r\n(thanks to 'andreax79': https:\/\/github.com\/amdt\/sunset\/pull\/11)\r\n* Fixed an issue that caused a 'E122' error with the 'restore_cpoptions' function","3":"* Made 'g:sunset_utc_offset' optional\r\n(thanks to 'andreax79': https:\/\/github.com\/amdt\/sunset\/pull\/11)\r\n* Fixed an issue that caused a 'E122' error with the 'restore_cpoptions' function","package":"sunset-3.1.0.vmb","4":"sunset-3.1.0.vmb","src_id":"22957","5":"22957","creation_date":"1425105052","6":"1425105052"},{"0":"4277","vim_version":"7.4","1":"7.4","script_version":"3.0.0","2":"3.0.0","version_comment":"* Fixed an issue where 'cpoptions' may not be restored when the script finishes early\r\n* Updated the function names for the 'Sunset_daytime_callback()' and 'Sunset_nighttime_callback()' callbacks to match changes to the VimL interpreter","3":"* Fixed an issue where 'cpoptions' may not be restored when the script finishes early\r\n* Updated the function names for the 'Sunset_daytime_callback()' and 'Sunset_nighttime_callback()' callbacks to match changes to the VimL interpreter","package":"sunset-3.0.0.vmb","4":"sunset-3.0.0.vmb","src_id":"22933","5":"22933","creation_date":"1424604598","6":"1424604598"},{"0":"4277","vim_version":"7.3","1":"7.3","script_version":"2.0.1","2":"2.0.1","version_comment":"Fixed an issue where versions of Vim greater than 7.4.260 would not allow this script to run. (https:\/\/github.com\/amdt\/sunset\/issues\/8)","3":"Fixed an issue where versions of Vim greater than 7.4.260 would not allow this script to run. (https:\/\/github.com\/amdt\/sunset\/issues\/8)","package":"sunset-2.0.1.vmb","4":"sunset-2.0.1.vmb","src_id":"21872","5":"21872","creation_date":"1399561250","6":"1399561250"},{"0":"4277","vim_version":"7.3","1":"7.3","script_version":"2.0.0","2":"2.0.0","version_comment":"- Sunset now switches your background (or calls your callbacks) mid-way\r\n  through Civil Twilight time.\r\n- *Note:* Sunset 2.0.0 breaks compatibility with previous versions of\r\n  Sunset for users of the `sunset_callback()` callback.\r\n  'sunset_daytime_callback()' and 'sunset_nighttime_callback()' are\r\n  unaffected.","3":"- Sunset now switches your background (or calls your callbacks) mid-way\r\n  through Civil Twilight time.\r\n- *Note:* Sunset 2.0.0 breaks compatibility with previous versions of\r\n  Sunset for users of the `sunset_callback()` callback.\r\n  'sunset_daytime_callback()' and 'sunset_nighttime_callback()' are\r\n  unaffected.","package":"sunset-2.0.0.vmb","4":"sunset-2.0.0.vmb","src_id":"19353","5":"19353","creation_date":"1358002501","6":"1358002501"},{"0":"4277","vim_version":"7.3","1":"7.3","script_version":"1.2.1","2":"1.2.1","version_comment":"- Fix table of contents numbering in documentation.","3":"- Fix table of contents numbering in documentation.","package":"sunset-1.2.1.vmb","4":"sunset-1.2.1.vmb","src_id":"19013","5":"19013","creation_date":"1353563445","6":"1353563445"},{"0":"4277","vim_version":"7.3","1":"7.3","script_version":"1.2.0","2":"1.2.0","version_comment":"- GetLatestVimScripts-compatible.\r\n- New behaviour with 'sunset_daytime_callback()' and 'sunset_nighttime_callback()'.\r\n- sunset_callback() has been deprecated and will be removed in the next release.","3":"- GetLatestVimScripts-compatible.\r\n- New behaviour with 'sunset_daytime_callback()' and 'sunset_nighttime_callback()'.\r\n- sunset_callback() has been deprecated and will be removed in the next release.","package":"sunset-1.2.0.vmb","4":"sunset-1.2.0.vmb","src_id":"18950","5":"18950","creation_date":"1352152852","6":"1352152852"},{"0":"4277","vim_version":"7.3","1":"7.3","script_version":"1.1.0","2":"1.1.0","version_comment":"Added 'sunset_callback()'.","3":"Added 'sunset_callback()'.","package":"sunset-1.1.0.vmb","4":"sunset-1.1.0.vmb","src_id":"18920","5":"18920","creation_date":"1351466874","6":"1351466874"},{"0":"4277","vim_version":"7.3","1":"7.3","script_version":"1.0.3","2":"1.0.3","version_comment":"Initial upload","3":"Initial upload","package":"sunset-1.0.3.vmb","4":"sunset-1.0.3.vmb","src_id":"18846","5":"18846","creation_date":"1350771332","6":"1350771332"}]},"4276":{"script_id":"4276","0":"4276","script_name":"SnippetCompleteSnipMate","1":"SnippetCompleteSnipMate","script_type":"utility","2":"utility","summary":"Integrate snipMate snippets into SnippetComplete plugin.","3":"Integrate snipMate snippets into SnippetComplete plugin.","description":"DESCRIPTION\r\nSimple expansions can be done with Vim's built-in abbreviations, but for\r\nform-like text fragments that contain multiple cursor stops or mirrored\r\nreplacements of typed text, one needs a plugin like the popular snipMate\r\n(vimscript #2540). As many snippets start simple but are extended later on, it\r\nis useful to have a completion for both abbreviations and snippets, so that\r\nyou don't need to remember how the text fragment you want to use is defined.\r\n\r\nApart from the integration with abbreviations, this plugin offers the\r\nfollowing advantages over the CTRL-R <Tab> completion built into snipMate\r\nitself:\r\n- Summary rendering of the snippet expansion in the completion popup menu,\r\n  including the number of lines the snippet expands to and the number of\r\n  multi-snips alternatives.\r\n- Preview of the full snippet \/ all multi-snips (when 'completeopt' contains\r\n  \"preview\").\r\n\r\nThis plugin integrates snipMate snippets into the insert mode completion for\r\nVim abbreviations of the SnippetComplete.vim plugin (vimscript #2926), and\r\noffers an additional completion only for snipMate snippets.\r\n\r\nUSAGE\r\nThe plugin extends the i_CTRL-X_] completion of Vim insert mode\r\nabbreviations from the SnippetComplete.vim plugin with snippets from\r\nsnipMate. Just continue using that as before.\r\nSnippets appear in the completion popup prefixed with \"%N\", where N is the\r\nnumber of lines that the snippet expands to. Multi-snips appear as \"M*N\",\r\nwhere M is the number of alternatives.\r\n\r\nAlternatively, this plugin provides an additional CTRL-X <Tab> completion\r\nsolely for snipMate snippets, excluding Vim abbreviations.\r\n\r\nCTRL-X <Tab>            Find matches for snipMate snippets that start with the\r\n                        text in front of the cursor.\r\n                        If no matches were found that way, matches anywhere in\r\n                        the snippet or in the snippet's expanded text will be\r\n                        shown. So if you can't remember the shortcut, but a\r\n                        word fragment from the resulting expansion, just try\r\n                        with that.","4":"DESCRIPTION\r\nSimple expansions can be done with Vim's built-in abbreviations, but for\r\nform-like text fragments that contain multiple cursor stops or mirrored\r\nreplacements of typed text, one needs a plugin like the popular snipMate\r\n(vimscript #2540). As many snippets start simple but are extended later on, it\r\nis useful to have a completion for both abbreviations and snippets, so that\r\nyou don't need to remember how the text fragment you want to use is defined.\r\n\r\nApart from the integration with abbreviations, this plugin offers the\r\nfollowing advantages over the CTRL-R <Tab> completion built into snipMate\r\nitself:\r\n- Summary rendering of the snippet expansion in the completion popup menu,\r\n  including the number of lines the snippet expands to and the number of\r\n  multi-snips alternatives.\r\n- Preview of the full snippet \/ all multi-snips (when 'completeopt' contains\r\n  \"preview\").\r\n\r\nThis plugin integrates snipMate snippets into the insert mode completion for\r\nVim abbreviations of the SnippetComplete.vim plugin (vimscript #2926), and\r\noffers an additional completion only for snipMate snippets.\r\n\r\nUSAGE\r\nThe plugin extends the i_CTRL-X_] completion of Vim insert mode\r\nabbreviations from the SnippetComplete.vim plugin with snippets from\r\nsnipMate. Just continue using that as before.\r\nSnippets appear in the completion popup prefixed with \"%N\", where N is the\r\nnumber of lines that the snippet expands to. Multi-snips appear as \"M*N\",\r\nwhere M is the number of alternatives.\r\n\r\nAlternatively, this plugin provides an additional CTRL-X <Tab> completion\r\nsolely for snipMate snippets, excluding Vim abbreviations.\r\n\r\nCTRL-X <Tab>            Find matches for snipMate snippets that start with the\r\n                        text in front of the cursor.\r\n                        If no matches were found that way, matches anywhere in\r\n                        the snippet or in the snippet's expanded text will be\r\n                        shown. So if you can't remember the shortcut, but a\r\n                        word fragment from the resulting expansion, just try\r\n                        with that.","install_details":"INSTALLATION\r\nThis script is packaged as a vimball. If you have the \"gunzip\" decompressor\r\nin your PATH, simply edit the *.vmb.gz package in Vim; otherwise, decompress\r\nthe archive first, e.g. using WinZip. Inside Vim, install by sourcing the\r\nvimball or via the :UseVimball command.\r\n    vim SnippetCompleteSnipMate*.vmb.gz\r\n    :so %\r\n\r\nTo be able to access its snippets, snipMate must be patched. Open\r\n~\/.vim\/plugin\/snipMate.vim and insert the following function at the bottom:\r\n        fun! GetSnipsInCurrentScope()\r\n                let snips = {}\r\n                for scope in [bufnr('%')] + split(&ft, '\\.') + ['_']\r\n                        call extend(snips, get(s:snippets, scope, {}), 'keep')\r\n                        call extend(snips, get(s:multi_snips, scope, {}), 'keep')\r\n                endfor\r\n                return snips\r\n        endf\r\n\r\nTo uninstall, use the :RmVimball command.\r\n\r\nDEPENDENCIES\r\n- Requires Vim 7.0 or higher.\r\n- Requires the SnippetComplete.vim plugin (vimscript #2926), version 2.10 or\r\n  higher.\r\n- Requires the snipMate plugin (vimscript #2540)\r\n\r\nCONFIGURATION\r\nFor a permanent configuration, put the following commands into your vimrc:\r\n\r\nIf you want to use a different mapping, map your keys to the\r\n<Plug>(SnippetCompleteSnipMate) mapping target _before_ sourcing the script\r\n(e.g. in your vimrc):\r\n    imap <C-x><Tab> <Plug>(SnippetCompleteSnipMate)\r\nIf you don't need the additional mapping, disable it via:\r\n    imap <Plug>Disable(SnippetCompleteSnipMate) <Plug>(SnippetCompleteSnipMate)","5":"INSTALLATION\r\nThis script is packaged as a vimball. If you have the \"gunzip\" decompressor\r\nin your PATH, simply edit the *.vmb.gz package in Vim; otherwise, decompress\r\nthe archive first, e.g. using WinZip. Inside Vim, install by sourcing the\r\nvimball or via the :UseVimball command.\r\n    vim SnippetCompleteSnipMate*.vmb.gz\r\n    :so %\r\n\r\nTo be able to access its snippets, snipMate must be patched. Open\r\n~\/.vim\/plugin\/snipMate.vim and insert the following function at the bottom:\r\n        fun! GetSnipsInCurrentScope()\r\n                let snips = {}\r\n                for scope in [bufnr('%')] + split(&ft, '\\.') + ['_']\r\n                        call extend(snips, get(s:snippets, scope, {}), 'keep')\r\n                        call extend(snips, get(s:multi_snips, scope, {}), 'keep')\r\n                endfor\r\n                return snips\r\n        endf\r\n\r\nTo uninstall, use the :RmVimball command.\r\n\r\nDEPENDENCIES\r\n- Requires Vim 7.0 or higher.\r\n- Requires the SnippetComplete.vim plugin (vimscript #2926), version 2.10 or\r\n  higher.\r\n- Requires the snipMate plugin (vimscript #2540)\r\n\r\nCONFIGURATION\r\nFor a permanent configuration, put the following commands into your vimrc:\r\n\r\nIf you want to use a different mapping, map your keys to the\r\n<Plug>(SnippetCompleteSnipMate) mapping target _before_ sourcing the script\r\n(e.g. in your vimrc):\r\n    imap <C-x><Tab> <Plug>(SnippetCompleteSnipMate)\r\nIf you don't need the additional mapping, disable it via:\r\n    imap <Plug>Disable(SnippetCompleteSnipMate) <Plug>(SnippetCompleteSnipMate)","first_name":"Ingo","6":"Ingo","last_name":"Karkat","7":"Karkat","releases":[{"0":"4276","vim_version":"7.0","1":"7.0","script_version":"1.01","2":"1.01","version_comment":"CHG: Change default mapping to the more intuitive (for default snipMate trigger) i_CTRL-X_<Tab>.","3":"CHG: Change default mapping to the more intuitive (for default snipMate trigger) i_CTRL-X_<Tab>.","package":"SnippetCompleteSnipMate-1.01.vmb.gz","4":"SnippetCompleteSnipMate-1.01.vmb.gz","src_id":"19390","5":"19390","creation_date":"1358610797","6":"1358610797"},{"0":"4276","vim_version":"7.0","1":"7.0","script_version":"1.00","2":"1.00","version_comment":"Initial upload","3":"Initial upload","package":"SnippetCompleteSnipMate-1.00.vmb.gz","4":"SnippetCompleteSnipMate-1.00.vmb.gz","src_id":"18845","5":"18845","creation_date":"1350760745","6":"1350760745"}]},"4275":{"script_id":"4275","0":"4275","script_name":"sqlhana.vim","1":"sqlhana.vim","script_type":"syntax","2":"syntax","summary":"sqlhana.vim : Syntax file for SAP HANA","3":"sqlhana.vim : Syntax file for SAP HANA","description":"Syntax file for SAP HANA\r\n\r\nSupports all SQL elements of the SAP HANA SP6 release build 60.\r\n\r\nAssuming you are editing a .sql file (Vim sets the filetype to be SQL), then by default Vim assumes Oracle syntax.\r\n\r\nThis syntax file works in conjunction with ftplugin\/sql.vim, indent\/sql.vim and syntax\/sql.vim to load the correct SQL dialect.\r\n\r\nTo change from Oracle syntax to a different SQL dialect you can initiate this by running:\r\n:SQLSetType sqlhana.vim\r\nor\r\n:SQLSetType <tab key> to cycle through all supported SQL dialects.\r\nor \r\n:SQLSetType sqlh<tab key> to cycle through all supported SQL dialects starting with \"sqlh\". \r\n\r\n\r\nOr to change Vim's default Oracle dialect to HANA you can put the following in your .vimrc:\r\n    let g:sql_type_default = 'sqlhana'\r\n\r\nTo read more on these options see:\r\n:h sql.txt\r\n","4":"Syntax file for SAP HANA\r\n\r\nSupports all SQL elements of the SAP HANA SP6 release build 60.\r\n\r\nAssuming you are editing a .sql file (Vim sets the filetype to be SQL), then by default Vim assumes Oracle syntax.\r\n\r\nThis syntax file works in conjunction with ftplugin\/sql.vim, indent\/sql.vim and syntax\/sql.vim to load the correct SQL dialect.\r\n\r\nTo change from Oracle syntax to a different SQL dialect you can initiate this by running:\r\n:SQLSetType sqlhana.vim\r\nor\r\n:SQLSetType <tab key> to cycle through all supported SQL dialects.\r\nor \r\n:SQLSetType sqlh<tab key> to cycle through all supported SQL dialects starting with \"sqlh\". \r\n\r\n\r\nOr to change Vim's default Oracle dialect to HANA you can put the following in your .vimrc:\r\n    let g:sql_type_default = 'sqlhana'\r\n\r\nTo read more on these options see:\r\n:h sql.txt\r\n","install_details":"Put <sqlhana.vim> into your .vim\/syntax or vimfiles\/syntax directory  \r\n","5":"Put <sqlhana.vim> into your .vim\/syntax or vimfiles\/syntax directory  \r\n","first_name":"David","6":"David","last_name":"Fishburn","7":"Fishburn","releases":[{"0":"4275","vim_version":"7.0","1":"7.0","script_version":"SP6","2":"SP6","version_comment":"Updated for SAP HANA SP6 Build 60","3":"Updated for SAP HANA SP6 Build 60","package":"sqlhana.vim","4":"sqlhana.vim","src_id":"20844","5":"20844","creation_date":"1380070909","6":"1380070909"},{"0":"4275","vim_version":"7.0","1":"7.0","script_version":"SP4","2":"SP4","version_comment":"Added homepage reference to it's script location on vim.org.","3":"Added homepage reference to it's script location on vim.org.","package":"sqlhana.vim","4":"sqlhana.vim","src_id":"18830","5":"18830","creation_date":"1350511209","6":"1350511209"}]},"4274":{"script_id":"4274","0":"4274","script_name":"very monochrome grey theme","1":"very monochrome grey theme","script_type":"color scheme","2":"color scheme","summary":"Grey color sheme","3":"Grey color sheme","description":"A very grey monochrome color scheme for a pleasant coding!","4":"A very grey monochrome color scheme for a pleasant coding!","install_details":"","5":"","first_name":"eandi","6":"eandi","last_name":"eandi","7":"eandi","releases":[{"0":"4274","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"grey.vim","4":"grey.vim","src_id":"18828","5":"18828","creation_date":"1350508022","6":"1350508022"}]},"4273":{"script_id":"4273","0":"4273","script_name":"autochmodx.vim","1":"autochmodx.vim","script_type":"utility","2":"utility","summary":"If a current file looks like an executable script, make it executable by chmod","3":"If a current file looks like an executable script, make it executable by chmod","description":"If a current file looks like an executable script,\r\nmake it by executable running \"chmod +x %\".\r\n\r\nRequirements:\r\n- Vim 7.2 or later\r\n\r\nLatest version:\r\nhttp:\/\/github.com\/tyru\/autochmodx.vim\r\n\r\nLatest document:\r\nhttps:\/\/github.com\/tyru\/autochmodx.vim\/blob\/master\/doc\/autochmodx.txt\r\n\r\nLatest document with syntax highlight:\r\nhttp:\/\/vim-doc.heroku.com\/view?https:\/\/raw.github.com\/tyru\/autochmodx.vim\/master\/doc\/autochmodx.txt","4":"If a current file looks like an executable script,\r\nmake it by executable running \"chmod +x %\".\r\n\r\nRequirements:\r\n- Vim 7.2 or later\r\n\r\nLatest version:\r\nhttp:\/\/github.com\/tyru\/autochmodx.vim\r\n\r\nLatest document:\r\nhttps:\/\/github.com\/tyru\/autochmodx.vim\/blob\/master\/doc\/autochmodx.txt\r\n\r\nLatest document with syntax highlight:\r\nhttp:\/\/vim-doc.heroku.com\/view?https:\/\/raw.github.com\/tyru\/autochmodx.vim\/master\/doc\/autochmodx.txt","install_details":"","5":"","first_name":"tyru","6":"tyru","last_name":" ","7":" ","releases":[{"0":"4273","vim_version":"7.2","1":"7.2","script_version":"1.0.0","2":"1.0.0","version_comment":"Initial upload","3":"Initial upload","package":"autochmodx.zip","4":"autochmodx.zip","src_id":"18824","5":"18824","creation_date":"1350483051","6":"1350483051"}]},"4272":{"script_id":"4272","0":"4272","script_name":"Unicode RST Tables","1":"Unicode RST Tables","script_type":"utility","2":"utility","summary":"Allows to create and edit restructuredText tables easily (deprecated).","3":"Allows to create and edit restructuredText tables easily (deprecated).","description":"Note: This plugin is deprecated. I personally recommend use vimscript #4358 instead.\r\n\r\n===========================================================================\r\n\r\nOriginal plugin: vimscript #3041 \r\n\r\nFixed some bugs and add CJK and Python 3 support.\r\n\r\nHere's my script compared to other alternatives:\r\n\r\nvimscript #3777: RST Tables (CJK)\r\nThis script used gbk to encode the text, may not work with some language.\r\nMy script used unicode, should works for any language.\r\n\r\nvimscript #3450: RST Tables\r\nThis script doesn't support python 3.\r\n\r\n\r\n This plugin allows to create and edit restructuredText tables easily.\r\n\r\nIts adds two new commands (<Leader> is \"\\\" by default):\r\n\r\n    <Leader><Leader>c  ->  Creates a new restructuredText table.\r\n    <Leader><Leader>f  ->  Fix table columns in a table.\r\n\r\nFor example, if you have a paragraph with data like this:\r\n\r\n nombre      apellido    edad\r\n pepe        zarate      28\r\n toto        garcia      29\r\n\r\nAlso, you could use \"|\" as delimiter:\r\n\r\n nombre|apellido|edad\r\n pepe|zarate|28\r\n toto|garcia|29\r\n\r\nyou can press \"\\\\c\" to create a simple table:\r\n\r\n    +--------+----------+------+\r\n    | nombre | apellido | edad |\r\n    +========+==========+======+\r\n    | pepe   | zarate   | 28   |\r\n    +--------+----------+------+\r\n    | toto   | garcia   | 29   |\r\n    +--------+----------+------+\r\n\r\n\r\nNow, if you change the table content, for example adding characters\r\nto the first content row.\r\n\r\n    +--------+----------+------+\r\n    | nombre | apellido | edad |\r\n    +========+==========+======+\r\n    | Un nombre muy largo que rompe la tabla   | zarate   | 28   |\r\n    +--------+----------+------+\r\n    | toto   | un appellido largo...   | 29   |\r\n    +--------+----------+------+\r\n\r\nyou need to fix the columns widths. So, press \"\\\\f\" and you will gets:\r\n\r\n    +----------------------------------------+-----------------------+------+\r\n    | nombre                                 | apellido              | edad |\r\n    +========================================+=======================+======+\r\n    | Un nombre muy largo que rompe la tabla | zarate                | 28   |\r\n    +----------------------------------------+-----------------------+------+\r\n    | toto                                   | un appellido largo... | 29   |\r\n    +----------------------------------------+-----------------------+------+ ","4":"Note: This plugin is deprecated. I personally recommend use vimscript #4358 instead.\r\n\r\n===========================================================================\r\n\r\nOriginal plugin: vimscript #3041 \r\n\r\nFixed some bugs and add CJK and Python 3 support.\r\n\r\nHere's my script compared to other alternatives:\r\n\r\nvimscript #3777: RST Tables (CJK)\r\nThis script used gbk to encode the text, may not work with some language.\r\nMy script used unicode, should works for any language.\r\n\r\nvimscript #3450: RST Tables\r\nThis script doesn't support python 3.\r\n\r\n\r\n This plugin allows to create and edit restructuredText tables easily.\r\n\r\nIts adds two new commands (<Leader> is \"\\\" by default):\r\n\r\n    <Leader><Leader>c  ->  Creates a new restructuredText table.\r\n    <Leader><Leader>f  ->  Fix table columns in a table.\r\n\r\nFor example, if you have a paragraph with data like this:\r\n\r\n nombre      apellido    edad\r\n pepe        zarate      28\r\n toto        garcia      29\r\n\r\nAlso, you could use \"|\" as delimiter:\r\n\r\n nombre|apellido|edad\r\n pepe|zarate|28\r\n toto|garcia|29\r\n\r\nyou can press \"\\\\c\" to create a simple table:\r\n\r\n    +--------+----------+------+\r\n    | nombre | apellido | edad |\r\n    +========+==========+======+\r\n    | pepe   | zarate   | 28   |\r\n    +--------+----------+------+\r\n    | toto   | garcia   | 29   |\r\n    +--------+----------+------+\r\n\r\n\r\nNow, if you change the table content, for example adding characters\r\nto the first content row.\r\n\r\n    +--------+----------+------+\r\n    | nombre | apellido | edad |\r\n    +========+==========+======+\r\n    | Un nombre muy largo que rompe la tabla   | zarate   | 28   |\r\n    +--------+----------+------+\r\n    | toto   | un appellido largo...   | 29   |\r\n    +--------+----------+------+\r\n\r\nyou need to fix the columns widths. So, press \"\\\\f\" and you will gets:\r\n\r\n    +----------------------------------------+-----------------------+------+\r\n    | nombre                                 | apellido              | edad |\r\n    +========================================+=======================+======+\r\n    | Un nombre muy largo que rompe la tabla | zarate                | 28   |\r\n    +----------------------------------------+-----------------------+------+\r\n    | toto                                   | un appellido largo... | 29   |\r\n    +----------------------------------------+-----------------------+------+ ","install_details":" Install the python extension to vim (either 2 or 3) and then copy the file `rst_table.vim`\r\nto the `.vim\/plugin` directory in your home directory. ","5":" Install the python extension to vim (either 2 or 3) and then copy the file `rst_table.vim`\r\nto the `.vim\/plugin` directory in your home directory. ","first_name":"Tianjiao","6":"Tianjiao","last_name":"Yin","7":"Yin","releases":[{"0":"4272","vim_version":"7.0","1":"7.0","script_version":"0.1.1","2":"0.1.1","version_comment":"fixed such bug:\r\n\r\n1\r\n2 fix|me\r\n3 test|it\r\n\r\nIn previous version, create table does not work correctly.","3":"fixed such bug:\r\n\r\n1\r\n2 fix|me\r\n3 test|it\r\n\r\nIn previous version, create table does not work correctly.","package":"rst_table.vim","4":"rst_table.vim","src_id":"18869","5":"18869","creation_date":"1351048870","6":"1351048870"},{"0":"4272","vim_version":"7.3","1":"7.3","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"rst_table.vim","4":"rst_table.vim","src_id":"18815","5":"18815","creation_date":"1350336144","6":"1350336144"}]},"4271":{"script_id":"4271","0":"4271","script_name":"CY","1":"CY","script_type":"utility","2":"utility","summary":"Fast input method for Chinese (穿越输入法)","3":"Fast input method for Chinese (穿越输入法)","description":"Chinese\r\n==========\r\n\r\n穿越中文输入法（CY Input Method）是一个在 Vim 编辑器 中使用的中文输入方法，目的是为了方便软件开发人员输入中文。\r\n\r\nGithub :   https:\/\/github.com\/cy2081\/vim-cyim\r\n\r\n中文编码\r\n------------\r\n\r\n采用小小音形输入法中的编码，请参考： http:\/\/xxyx.ys168.com\/\r\n\r\n主要特性\r\n------------\r\n\r\n  * 从键盘设置到汉字编码方法都进行了优化\r\n  * 在 Vim 编辑器当中使用，充分利用 Vim 的各种特性。\r\n  * 汉字字词编码方案采用最多四个字母组成的音形码方式，尽可能实现简单高效。\r\n  * 所有的目标就是为了快速输入，并且尽可能简单易学。\r\n  * 支持连续输入\r\n  * 当输入大写英文字母时自动切换到英文。\r\n  * 支持搜索和全屏定位跳转\r\n  * 每次输入自动记录到名称为 y 的 register，供以后随时调用\r\n \r\n\r\n快捷键\r\n--------\r\n\r\n   <Alt-i> 或 <Ctrl-z>  输入法开关\r\n\r\n   <Ctrl-d>  取消当前的中文候选\r\n\r\n   <Ctrl-h> 和 <Backspace> 一样，用于删除前边输入的字母，为了方便\r\n   还可选用<Ctrl-Space>\r\n\r\n   ^ 用于中英文快速切换\r\n\r\n   <Ctrl-e> 中英文标点切换\r\n\r\n   <Ctrl-^> 显示菜单，设置输入法:\r\n    (m) 码表切换\r\n    (.) 中英标点切换\r\n    (p) 最大词长: 设为 1 为单字模试\r\n    (g) gb2312开关: 滤掉 gb2312 范围内的汉字\r\n    (c) 简繁转换开关\r\n    (q) 退出\r\n\r\n   <Ctrl-f> 设置搜索关键词，用第一个字符进行全屏定位\r\n   ,g 开始搜索词汇\r\n   ,f 开始全屏定位\r\n\r\n   <Ctrl-s> 输入前置字符\r\n   <Ctrl-u> 删除刚才新输入的字词\r\n\r\n   ' 单引号切换到临时英文，可在文件cy.cy当中的 EnChar 当中设置\r\n   { 大括号切换到临时拼音 ，在文件cy.cy当中的 PyChar 当中设置\r\n   输入大写英文字母自动切换到英文模式\r\n\r\n   - 向上翻页\r\n   = 向下翻页\r\n\r\n   空格或数字选字, 回车输英文\r\n   ' 单引号选择第二候选词\r\n   \" 双引号选择第三候选词\r\n   \\ 反斜线选择第四候选词\r\n   | 竖线选择第五候选词\r\n    \r\n\r\n中文搜索方法\r\n------------------\r\n  \r\n在输入状态按 Ctrl 和 f 键，然后接着输入要搜索的词汇，用第一个字符进行全屏定位。在普通状态时，按 ,g 可搜索匹配，按 ,f 可全屏定位，根据位置输入相应字符即可。\r\n\r\n每次输入自动记录到名称为 y 的 register，从而可以随时调用。\r\n\r\n\r\n","4":"Chinese\r\n==========\r\n\r\n穿越中文输入法（CY Input Method）是一个在 Vim 编辑器 中使用的中文输入方法，目的是为了方便软件开发人员输入中文。\r\n\r\nGithub :   https:\/\/github.com\/cy2081\/vim-cyim\r\n\r\n中文编码\r\n------------\r\n\r\n采用小小音形输入法中的编码，请参考： http:\/\/xxyx.ys168.com\/\r\n\r\n主要特性\r\n------------\r\n\r\n  * 从键盘设置到汉字编码方法都进行了优化\r\n  * 在 Vim 编辑器当中使用，充分利用 Vim 的各种特性。\r\n  * 汉字字词编码方案采用最多四个字母组成的音形码方式，尽可能实现简单高效。\r\n  * 所有的目标就是为了快速输入，并且尽可能简单易学。\r\n  * 支持连续输入\r\n  * 当输入大写英文字母时自动切换到英文。\r\n  * 支持搜索和全屏定位跳转\r\n  * 每次输入自动记录到名称为 y 的 register，供以后随时调用\r\n \r\n\r\n快捷键\r\n--------\r\n\r\n   <Alt-i> 或 <Ctrl-z>  输入法开关\r\n\r\n   <Ctrl-d>  取消当前的中文候选\r\n\r\n   <Ctrl-h> 和 <Backspace> 一样，用于删除前边输入的字母，为了方便\r\n   还可选用<Ctrl-Space>\r\n\r\n   ^ 用于中英文快速切换\r\n\r\n   <Ctrl-e> 中英文标点切换\r\n\r\n   <Ctrl-^> 显示菜单，设置输入法:\r\n    (m) 码表切换\r\n    (.) 中英标点切换\r\n    (p) 最大词长: 设为 1 为单字模试\r\n    (g) gb2312开关: 滤掉 gb2312 范围内的汉字\r\n    (c) 简繁转换开关\r\n    (q) 退出\r\n\r\n   <Ctrl-f> 设置搜索关键词，用第一个字符进行全屏定位\r\n   ,g 开始搜索词汇\r\n   ,f 开始全屏定位\r\n\r\n   <Ctrl-s> 输入前置字符\r\n   <Ctrl-u> 删除刚才新输入的字词\r\n\r\n   ' 单引号切换到临时英文，可在文件cy.cy当中的 EnChar 当中设置\r\n   { 大括号切换到临时拼音 ，在文件cy.cy当中的 PyChar 当中设置\r\n   输入大写英文字母自动切换到英文模式\r\n\r\n   - 向上翻页\r\n   = 向下翻页\r\n\r\n   空格或数字选字, 回车输英文\r\n   ' 单引号选择第二候选词\r\n   \" 双引号选择第三候选词\r\n   \\ 反斜线选择第四候选词\r\n   | 竖线选择第五候选词\r\n    \r\n\r\n中文搜索方法\r\n------------------\r\n  \r\n在输入状态按 Ctrl 和 f 键，然后接着输入要搜索的词汇，用第一个字符进行全屏定位。在普通状态时，按 ,g 可搜索匹配，按 ,f 可全屏定位，根据位置输入相应字符即可。\r\n\r\n每次输入自动记录到名称为 y 的 register，从而可以随时调用。\r\n\r\n\r\n","install_details":"下载安装文件，然后解压缩，把plugin目录下的文件复制到 Vim 的 plugin 目录下，重启 Vim 即可。\r\n\r\n如果需要配置，请修改 cy.vim 文件前边的参数，其中有说明。","5":"下载安装文件，然后解压缩，把plugin目录下的文件复制到 Vim 的 plugin 目录下，重启 Vim 即可。\r\n\r\n如果需要配置，请修改 cy.vim 文件前边的参数，其中有说明。","first_name":"Huxi","6":"Huxi","last_name":"Fun","7":"Fun","releases":[{"0":"4271","vim_version":"7.0","1":"7.0","script_version":"4.0","2":"4.0","version_comment":"更新中文编码","3":"更新中文编码","package":"cyim-4.0.tgz","4":"cyim-4.0.tgz","src_id":"27616","5":"27616","creation_date":"1622159477","6":"1622159477"},{"0":"4271","vim_version":"7.0","1":"7.0","script_version":"3.7","2":"3.7","version_comment":"优化中文编码，更新说明文档","3":"优化中文编码，更新说明文档","package":"cyim-3.7.zip","4":"cyim-3.7.zip","src_id":"25585","5":"25585","creation_date":"1506000615","6":"1506000615"},{"0":"4271","vim_version":"7.0","1":"7.0","script_version":"2.2","2":"2.2","version_comment":"更新了中文编码。","3":"更新了中文编码。","package":"cyim-2.2.zip","4":"cyim-2.2.zip","src_id":"19630","5":"19630","creation_date":"1363058653","6":"1363058653"},{"0":"4271","vim_version":"7.0","1":"7.0","script_version":"2.0","2":"2.0","version_comment":"A new version.","3":"A new version.","package":"cyim-2.0.zip","4":"cyim-2.0.zip","src_id":"19229","5":"19229","creation_date":"1356114314","6":"1356114314"},{"0":"4271","vim_version":"7.0","1":"7.0","script_version":"1.2","2":"1.2","version_comment":"improve config","3":"improve config","package":"cyim-1.2.zip","4":"cyim-1.2.zip","src_id":"18837","5":"18837","creation_date":"1350629725","6":"1350629725"},{"0":"4271","vim_version":"7.0","1":"7.0","script_version":"1.1","2":"1.1","version_comment":"add search and jump support","3":"add search and jump support","package":"cyim-1.1.zip","4":"cyim-1.1.zip","src_id":"18822","5":"18822","creation_date":"1350449537","6":"1350449537"},{"0":"4271","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"cyim-1.0.zip","4":"cyim-1.0.zip","src_id":"18812","5":"18812","creation_date":"1350324016","6":"1350324016"}]},"4270":{"script_id":"4270","0":"4270","script_name":"vim-eco","1":"vim-eco","script_type":"utility","2":"utility","summary":"Eco support for Vim","3":"Eco support for Vim","description":"This project adds eco support to the vim editor. Most of the code is originally from Mick Koch's vim-coffee-script (http:\/\/www.vim.org\/scripts\/script.php?script_id=3590) and some of the features (most notably syntax highlighting) depend on installing that plugin as well.\r\n\r\nIncluded features:\r\n  - eco filetype detection\r\n  - automatic indenting\r\n  - syntax highlighting\r\n  - surround.vim support\r\n\r\nPlease see the project page for much more information:\r\nhttp:\/\/github.com\/AndrewRadev\/vim-eco\r\n","4":"This project adds eco support to the vim editor. Most of the code is originally from Mick Koch's vim-coffee-script (http:\/\/www.vim.org\/scripts\/script.php?script_id=3590) and some of the features (most notably syntax highlighting) depend on installing that plugin as well.\r\n\r\nIncluded features:\r\n  - eco filetype detection\r\n  - automatic indenting\r\n  - syntax highlighting\r\n  - surround.vim support\r\n\r\nPlease see the project page for much more information:\r\nhttp:\/\/github.com\/AndrewRadev\/vim-eco\r\n","install_details":"Unzip the archive into .vim.\r\n\r\nSince this plugin has rolling versions based on git commits, it may be more convenient to install and upgrade it using pathogen and git. The readme has instructions for doing this:\r\nhttp:\/\/github.com\/AndrewRadev\/vim-eco#readme","5":"Unzip the archive into .vim.\r\n\r\nSince this plugin has rolling versions based on git commits, it may be more convenient to install and upgrade it using pathogen and git. The readme has instructions for doing this:\r\nhttp:\/\/github.com\/AndrewRadev\/vim-eco#readme","first_name":"Andrew","6":"Andrew","last_name":"Radev","7":"Radev","releases":[{"0":"4270","vim_version":"7.0","1":"7.0","script_version":"2bc1ee8","2":"2bc1ee8","version_comment":"- Highlight missing colon after \"if\"\r\n- Use html.vim for matchit support","3":"- Highlight missing colon after \"if\"\r\n- Use html.vim for matchit support","package":"vim-eco.zip","4":"vim-eco.zip","src_id":"22837","5":"22837","creation_date":"1422352125","6":"1422352125"},{"0":"4270","vim_version":"7.3","1":"7.3","script_version":"306ebff","2":"306ebff","version_comment":"Initial upload","3":"Initial upload","package":"vim-eco.zip","4":"vim-eco.zip","src_id":"18809","5":"18809","creation_date":"1350286551","6":"1350286551"}]},"4269":{"script_id":"4269","0":"4269","script_name":"rvm.vim","1":"rvm.vim","script_type":"utility","2":"utility","summary":"Switch Ruby versions from inside Vim","3":"Switch Ruby versions from inside Vim","description":"Want to use RVM with Vim?  You don't need a plugin to do that:  Just start Vim from your RVM enabled shell and it will work.  But say you started MacVim from Launchpad, or you started Vim with one version of Ruby and now you want another.  That's where rvm.vim comes in.\r\n\r\n    :Rvm 1.9.2\r\n\r\nIf you want to see the version that was chosen, use \"use\":\r\n\r\n    :Rvm use default\r\n\r\nIf you leave off the version, it goes .rvmrc hunting relative to the current buffer.\r\n\r\n    :Rvm\r\n    :Rvm use\r\n\r\nIf you really want to get crazy, you can make this happen automatically as you switch from buffer to buffer.\r\n\r\n    :autocmd BufEnter * Rvm\r\n\r\nYou can also invoke any old command.\r\n\r\n    :Rvm install 1.9.3\r\n\r\nAdd %{rvm#statusline()} to 'statusline' (or 'titlestring') to see the current Ruby version at all times.\r\n\r\nReport bugs at https:\/\/github.com\/tpope\/vim-rvm\/issues.","4":"Want to use RVM with Vim?  You don't need a plugin to do that:  Just start Vim from your RVM enabled shell and it will work.  But say you started MacVim from Launchpad, or you started Vim with one version of Ruby and now you want another.  That's where rvm.vim comes in.\r\n\r\n    :Rvm 1.9.2\r\n\r\nIf you want to see the version that was chosen, use \"use\":\r\n\r\n    :Rvm use default\r\n\r\nIf you leave off the version, it goes .rvmrc hunting relative to the current buffer.\r\n\r\n    :Rvm\r\n    :Rvm use\r\n\r\nIf you really want to get crazy, you can make this happen automatically as you switch from buffer to buffer.\r\n\r\n    :autocmd BufEnter * Rvm\r\n\r\nYou can also invoke any old command.\r\n\r\n    :Rvm install 1.9.3\r\n\r\nAdd %{rvm#statusline()} to 'statusline' (or 'titlestring') to see the current Ruby version at all times.\r\n\r\nReport bugs at https:\/\/github.com\/tpope\/vim-rvm\/issues.","install_details":"Extract in ~\/.vim (~\\vimfiles on Windows).","5":"Extract in ~\/.vim (~\\vimfiles on Windows).","first_name":"Tim","6":"Tim","last_name":"Pope","7":"Pope","releases":[{"0":"4269","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"rvm.zip","4":"rvm.zip","src_id":"18797","5":"18797","creation_date":"1350147342","6":"1350147342"}]},"4268":{"script_id":"4268","0":"4268","script_name":"ctagloader","1":"ctagloader","script_type":"utility","2":"utility","summary":"The script will traverse path tree and load ctag found on the way.","3":"The script will traverse path tree and load ctag found on the way.","description":"This script will automatically traverse your path tree from the current directory all the way to root and load tags files found along the way.\r\nThis is often useful when you have a root ctag file for your project and you often work in some subdirectories of your projects.\r\nFor example, if you have a project structured as follows:\r\nfoo\/\r\n     bar\/\r\n     baz\/\r\nThere is a ctag file (often named as tags\/TAGS) in foo\/ and you constantly work in foo\/bar\/ or foo\/baz\/\r\nSay you are now in foo\/bar\/. If you execute \"vim hello_world.c\", the ctag file in foo\/ will be found and loaded.","4":"This script will automatically traverse your path tree from the current directory all the way to root and load tags files found along the way.\r\nThis is often useful when you have a root ctag file for your project and you often work in some subdirectories of your projects.\r\nFor example, if you have a project structured as follows:\r\nfoo\/\r\n     bar\/\r\n     baz\/\r\nThere is a ctag file (often named as tags\/TAGS) in foo\/ and you constantly work in foo\/bar\/ or foo\/baz\/\r\nSay you are now in foo\/bar\/. If you execute \"vim hello_world.c\", the ctag file in foo\/ will be found and loaded.","install_details":"Put ctagloader.vim into ~\/.vim\/plugin\/. Then, when you load a file in vim, all the ctag files found should already be loaded. You can check if your ctag file is loaded by :set tags?.","5":"Put ctagloader.vim into ~\/.vim\/plugin\/. Then, when you load a file in vim, all the ctag files found should already be loaded. You can check if your ctag file is loaded by :set tags?.","first_name":"Zuocheng","6":"Zuocheng","last_name":"Ren","7":"Ren","releases":[{"0":"4268","vim_version":"7.0","1":"7.0","script_version":"0.11","2":"0.11","version_comment":"ctag can output a tag file either called tags or TAGS. Now it can match both tags and TAGS.","3":"ctag can output a tag file either called tags or TAGS. Now it can match both tags and TAGS.","package":"ctagloader.vim","4":"ctagloader.vim","src_id":"18813","5":"18813","creation_date":"1350329352","6":"1350329352"},{"0":"4268","vim_version":"7.0","1":"7.0","script_version":"0.10","2":"0.10","version_comment":"Initial upload","3":"Initial upload","package":"ctagloader.vim","4":"ctagloader.vim","src_id":"18792","5":"18792","creation_date":"1350061764","6":"1350061764"}]},"4267":{"script_id":"4267","0":"4267","script_name":"LineEndComplete","1":"LineEndComplete","script_type":"utility","2":"utility","summary":"Insert mode completion that completes the rest of the line.","3":"Insert mode completion that completes the rest of the line.","description":"DESCRIPTION\r\nThe i_CTRL-X_CTRL-L completion completes entire, identical lines. Sometimes,\r\nyou need completion of an almost-identical line with differences in indent or\r\na prefix string.\r\nThis plugin provides a completion mapping that takes the base text before the\r\ncursor, and offers the missing parts of other lines that also have this base\r\ntext. If you know the exact common text, or to whittle down the number of\r\nmatches, you can also select the completion base yourself before invoking the\r\nmapping.\r\n\r\nSEE ALSO\r\n- Check out the CompleteHelper.vim plugin page (vimscript #3914) for a full\r\n  list of insert mode completions powered by it.\r\n\r\nUSAGE\r\nIn insert mode, invoke the completion via CTRL-X $.\r\nAlternatively, you can pre-select the base (via select or visual mode) before\r\ninvoking the completion. This ensures that the best context for completion is\r\nchosen.\r\n\r\nYou can then search forward and backward via CTRL-N \/ CTRL-P, as usual.\r\n\r\nCTRL-X $                Find matches starting with the MotionComplete-base\r\n                        text before the cursor, until the end of that line.\r\n\r\n{Visual}CTRL-X $        Find matches starting with the selected text, until\r\n                        the end of that line.","4":"DESCRIPTION\r\nThe i_CTRL-X_CTRL-L completion completes entire, identical lines. Sometimes,\r\nyou need completion of an almost-identical line with differences in indent or\r\na prefix string.\r\nThis plugin provides a completion mapping that takes the base text before the\r\ncursor, and offers the missing parts of other lines that also have this base\r\ntext. If you know the exact common text, or to whittle down the number of\r\nmatches, you can also select the completion base yourself before invoking the\r\nmapping.\r\n\r\nSEE ALSO\r\n- Check out the CompleteHelper.vim plugin page (vimscript #3914) for a full\r\n  list of insert mode completions powered by it.\r\n\r\nUSAGE\r\nIn insert mode, invoke the completion via CTRL-X $.\r\nAlternatively, you can pre-select the base (via select or visual mode) before\r\ninvoking the completion. This ensures that the best context for completion is\r\nchosen.\r\n\r\nYou can then search forward and backward via CTRL-N \/ CTRL-P, as usual.\r\n\r\nCTRL-X $                Find matches starting with the MotionComplete-base\r\n                        text before the cursor, until the end of that line.\r\n\r\n{Visual}CTRL-X $        Find matches starting with the selected text, until\r\n                        the end of that line.","install_details":"INSTALLATION\r\nThis script is packaged as a vimball. If you have the \"gunzip\" decompressor\r\nin your PATH, simply edit the *.vmb.gz package in Vim; otherwise, decompress\r\nthe archive first, e.g. using WinZip. Inside Vim, install by sourcing the\r\nvimball or via the :UseVimball command.\r\n    vim LineEndComplete*.vmb.gz\r\n    :so %\r\nTo uninstall, use the :RmVimball command.\r\n\r\nDEPENDENCIES\r\n- Requires Vim 7.0 or higher.\r\n- Requires the MotionComplete.vim plugin (vimscript #4265).\r\n\r\nCONFIGURATION\r\nThe general MotionComplete-configuration applies here, too.\r\n\r\nFor a permanent configuration, put the following commands into your vimrc:\r\n\r\nIf you want to use different mappings, map your keys to the\r\n<Plug>(LineEndComplete...) mapping targets _before_ sourcing the script\r\n(e.g. in your vimrc):\r\n    imap <C-x>$ <Plug>(LineEndComplete)\r\n    vmap <C-x>$ <Plug>(LineEndComplete)","5":"INSTALLATION\r\nThis script is packaged as a vimball. If you have the \"gunzip\" decompressor\r\nin your PATH, simply edit the *.vmb.gz package in Vim; otherwise, decompress\r\nthe archive first, e.g. using WinZip. Inside Vim, install by sourcing the\r\nvimball or via the :UseVimball command.\r\n    vim LineEndComplete*.vmb.gz\r\n    :so %\r\nTo uninstall, use the :RmVimball command.\r\n\r\nDEPENDENCIES\r\n- Requires Vim 7.0 or higher.\r\n- Requires the MotionComplete.vim plugin (vimscript #4265).\r\n\r\nCONFIGURATION\r\nThe general MotionComplete-configuration applies here, too.\r\n\r\nFor a permanent configuration, put the following commands into your vimrc:\r\n\r\nIf you want to use different mappings, map your keys to the\r\n<Plug>(LineEndComplete...) mapping targets _before_ sourcing the script\r\n(e.g. in your vimrc):\r\n    imap <C-x>$ <Plug>(LineEndComplete)\r\n    vmap <C-x>$ <Plug>(LineEndComplete)","first_name":"Ingo","6":"Ingo","last_name":"Karkat","7":"Karkat","releases":[{"0":"4267","vim_version":"7.0","1":"7.0","script_version":"1.00","2":"1.00","version_comment":"Initial upload","3":"Initial upload","package":"LineEndComplete-1.00.vmb.gz","4":"LineEndComplete-1.00.vmb.gz","src_id":"18785","5":"18785","creation_date":"1350044983","6":"1350044983"}]},"4266":{"script_id":"4266","0":"4266","script_name":"BracketComplete","1":"BracketComplete","script_type":"utility","2":"utility","summary":"Insert mode completion for text inside various brackets.","3":"Insert mode completion for text inside various brackets.","description":"DESCRIPTION\r\nFrequently, text inside parentheses, be it a warning \"(don't do this)\" or\r\nfunction arguments \"(foo, bar, 42)\" is repeated. This also applies to other\r\nbracket delimiters, e.g. HTML tags \"<img src='banner.jpg' alt=''>\" or arrays\r\n\"[1, 2, 3]\".\r\nThis plugin provides a completion mapping that, when you realize you're typing\r\nthe same contents of a bracket-delimited text again, completes the entire text\r\ninside the brackets from other matches in the buffer. The completion base\r\nalways contains the entire text between the cursor and the previous opening\r\nbracket, so it doesn't matter how far you've already been into retyping this.\r\n\r\nSEE ALSO\r\n- Check out the CompleteHelper.vim plugin page (vimscript #3914) for a full\r\n  list of insert mode completions powered by it.\r\n\r\nUSAGE\r\nIn insert mode, invoke the completion via CTRL-X %.\r\nYou can then search forward and backward via CTRL-N \/ CTRL-P, as usual.\r\n\r\nCTRL-X %                Find matches for the text before the cursor, up to the\r\n                        previous bracket ( [ { < on the current line, and\r\n                        offer matches of the entire text inside the brackets,\r\n                        like the i( i[ i{ i< text objects.\r\n                        This also works for tag-blocks with the it text\r\n                        object; \"<b>f|\" will complete to \"<b>foo bar<\/b>\".","4":"DESCRIPTION\r\nFrequently, text inside parentheses, be it a warning \"(don't do this)\" or\r\nfunction arguments \"(foo, bar, 42)\" is repeated. This also applies to other\r\nbracket delimiters, e.g. HTML tags \"<img src='banner.jpg' alt=''>\" or arrays\r\n\"[1, 2, 3]\".\r\nThis plugin provides a completion mapping that, when you realize you're typing\r\nthe same contents of a bracket-delimited text again, completes the entire text\r\ninside the brackets from other matches in the buffer. The completion base\r\nalways contains the entire text between the cursor and the previous opening\r\nbracket, so it doesn't matter how far you've already been into retyping this.\r\n\r\nSEE ALSO\r\n- Check out the CompleteHelper.vim plugin page (vimscript #3914) for a full\r\n  list of insert mode completions powered by it.\r\n\r\nUSAGE\r\nIn insert mode, invoke the completion via CTRL-X %.\r\nYou can then search forward and backward via CTRL-N \/ CTRL-P, as usual.\r\n\r\nCTRL-X %                Find matches for the text before the cursor, up to the\r\n                        previous bracket ( [ { < on the current line, and\r\n                        offer matches of the entire text inside the brackets,\r\n                        like the i( i[ i{ i< text objects.\r\n                        This also works for tag-blocks with the it text\r\n                        object; \"<b>f|\" will complete to \"<b>foo bar<\/b>\".","install_details":"INSTALLATION\r\nThis script is packaged as a vimball. If you have the \"gunzip\" decompressor\r\nin your PATH, simply edit the *.vmb.gz package in Vim; otherwise, decompress\r\nthe archive first, e.g. using WinZip. Inside Vim, install by sourcing the\r\nvimball or via the :UseVimball command.\r\n    vim BracketComplete*.vmb.gz\r\n    :so %\r\nTo uninstall, use the :RmVimball command.\r\n\r\nDEPENDENCIES\r\n- Requires Vim 7.0 or higher.\r\n- Requires the MotionComplete.vim plugin (vimscript #4265).\r\n\r\nCONFIGURATION\r\nThe general MotionComplete-configuration applies here, too.\r\n\r\nFor a permanent configuration, put the following commands into your vimrc:\r\n\r\nThe recognized bracket types are defined via a Dictionary. Its keys are the\r\nopening brackets, which are mapped to an object that must have an \"opposite\"\r\nattribute that specifies the closing bracket. If there's a text object, it can\r\nbe specified via the \"textobject\" attribute (without the preceding \"a\" \/ \"i\");\r\notherwise, a search to the closing bracket is used to retrieve the text.\r\nTo add an imaginary bracketing from : to ;, use:\r\n    runtime plugin\/BracketComplete.vim  \" Define the default brackets first.\r\n    let g:BracketComplete_BracketConfig[':'] = {'opposite': ';'}\r\n\r\nIf you want to use different mapping, map your keys to the\r\n<Plug>(BracketComplete...) mapping target _before_ sourcing the script\r\n(e.g. in your vimrc):\r\n    imap <C-x>% <Plug>(BracketComplete)","5":"INSTALLATION\r\nThis script is packaged as a vimball. If you have the \"gunzip\" decompressor\r\nin your PATH, simply edit the *.vmb.gz package in Vim; otherwise, decompress\r\nthe archive first, e.g. using WinZip. Inside Vim, install by sourcing the\r\nvimball or via the :UseVimball command.\r\n    vim BracketComplete*.vmb.gz\r\n    :so %\r\nTo uninstall, use the :RmVimball command.\r\n\r\nDEPENDENCIES\r\n- Requires Vim 7.0 or higher.\r\n- Requires the MotionComplete.vim plugin (vimscript #4265).\r\n\r\nCONFIGURATION\r\nThe general MotionComplete-configuration applies here, too.\r\n\r\nFor a permanent configuration, put the following commands into your vimrc:\r\n\r\nThe recognized bracket types are defined via a Dictionary. Its keys are the\r\nopening brackets, which are mapped to an object that must have an \"opposite\"\r\nattribute that specifies the closing bracket. If there's a text object, it can\r\nbe specified via the \"textobject\" attribute (without the preceding \"a\" \/ \"i\");\r\notherwise, a search to the closing bracket is used to retrieve the text.\r\nTo add an imaginary bracketing from : to ;, use:\r\n    runtime plugin\/BracketComplete.vim  \" Define the default brackets first.\r\n    let g:BracketComplete_BracketConfig[':'] = {'opposite': ';'}\r\n\r\nIf you want to use different mapping, map your keys to the\r\n<Plug>(BracketComplete...) mapping target _before_ sourcing the script\r\n(e.g. in your vimrc):\r\n    imap <C-x>% <Plug>(BracketComplete)","first_name":"Ingo","6":"Ingo","last_name":"Karkat","7":"Karkat","releases":[{"0":"4266","vim_version":"7.0","1":"7.0","script_version":"1.01","2":"1.01","version_comment":"CHG: Change default mapping to the more intuitive i_CTRL-X_%.","3":"CHG: Change default mapping to the more intuitive i_CTRL-X_%.","package":"BracketComplete-1.01.vmb.gz","4":"BracketComplete-1.01.vmb.gz","src_id":"19391","5":"19391","creation_date":"1358610889","6":"1358610889"},{"0":"4266","vim_version":"7.0","1":"7.0","script_version":"1.00","2":"1.00","version_comment":"Initial upload","3":"Initial upload","package":"BracketComplete-1.00.vmb.gz","4":"BracketComplete-1.00.vmb.gz","src_id":"18784","5":"18784","creation_date":"1350044889","6":"1350044889"}]},"4265":{"script_id":"4265","0":"4265","script_name":"MotionComplete","1":"MotionComplete","script_type":"utility","2":"utility","summary":"Insert mode completion for chunks covered by queried {motion} or text object.","3":"Insert mode completion for chunks covered by queried {motion} or text object.","description":"DESCRIPTION\r\nMost insert mode completions complete only the current word (or an entire\r\nline), so one has to repeat i_CTRL-X_CTRL-N to complete the following words.\r\nFor longer completions, this is slow, especially because you sometimes have to\r\nchoose from multiple choices.\r\nThe completion provided by this plugin assumes that you know a Vim motion\r\n(e.g. '3e', ')' or '\/bar\/e') or text object which covers the text you want\r\ncompleted. When you invoke the completion, the completion base (some text\r\nbefore the cursor, or the currently selected text) will be presented and the\r\nmotion to cover the completion text (including the completion base) will be\r\nqueried. Then, the list of completion candidates will be prepared and selected\r\nin the usual way.\r\n\r\nSEE ALSO\r\n- Check out the CompleteHelper.vim plugin page (vimscript #3914) for a full\r\n  list of insert mode completions powered by it.\r\n\r\nUSAGE\r\nIn insert mode, invoke the completion via CTRL-X CTRL-M.\r\n\r\nThis completion method is probably only used for longer matches, as\r\ninvoking this completion method with the querying of the {motion} isn't\r\nvery fast. For motions that cover many words or entire sentences, an empty\r\nbase isn't helpful, there would be far too many matches. To ensure a\r\ncompletion base, this completion includes more than the usual keyword\r\ncharacters directly before the cursor. It looks for the following before the\r\ncursor, possibly with whitespace between it and the cursor:\r\n- keyword character(s), e.g \"foo\" in \"return (foo|\"\r\n- non-keyword non-whitespace character(s), e.g. \"\/*\" in \"return 0; \/* |\"\r\n- keyword character(s) followed by non-keyword non-whitespace characters,\r\n  e.g. \"foo(\" in \"return foo(|\"\r\nWhen the completion base starts with a keyword character, matches must start\r\nat a \\<word border.\r\nAlternatively, you can pre-select the base (via select or visual mode) before\r\ninvoking the completion. This ensures that the best context for completion is\r\nchosen.\r\n\r\nInput the {motion}.\r\nYou can then search forward and backward via CTRL-N \/ CTRL-P, as usual.\r\n\r\nCTRL-X CTRL-M           The completion first queries for {motion} (press\r\n                        <Enter> to conclude), then finds matches starting with\r\n                        the MotionComplete-base text before the cursor,\r\n                        covering {motion}.\r\n\r\n{Visual}CTRL-X CTRL-M   The completion first queries for {motion} (press\r\n                        <Enter> to conclude), then finds matches starting with\r\n                        the selected text, covering {motion}.\r\n                        Use this to define the completion base text (quickly\r\n                        done from insert mode via [CTRL-]SHIFT-<Left>) for\r\n                        better matches.\r\n\r\nEXAMPLE\r\nA quick|\r\n       ^ cursor, just triggered motion completion.\r\n\r\n(Somewhere else, a match:)\r\n    v---v completion base\r\nThe quick brown fox jumps over the lazy dog.\r\n    ^----------- \"5w\" --------^ completion via motion 5w","4":"DESCRIPTION\r\nMost insert mode completions complete only the current word (or an entire\r\nline), so one has to repeat i_CTRL-X_CTRL-N to complete the following words.\r\nFor longer completions, this is slow, especially because you sometimes have to\r\nchoose from multiple choices.\r\nThe completion provided by this plugin assumes that you know a Vim motion\r\n(e.g. '3e', ')' or '\/bar\/e') or text object which covers the text you want\r\ncompleted. When you invoke the completion, the completion base (some text\r\nbefore the cursor, or the currently selected text) will be presented and the\r\nmotion to cover the completion text (including the completion base) will be\r\nqueried. Then, the list of completion candidates will be prepared and selected\r\nin the usual way.\r\n\r\nSEE ALSO\r\n- Check out the CompleteHelper.vim plugin page (vimscript #3914) for a full\r\n  list of insert mode completions powered by it.\r\n\r\nUSAGE\r\nIn insert mode, invoke the completion via CTRL-X CTRL-M.\r\n\r\nThis completion method is probably only used for longer matches, as\r\ninvoking this completion method with the querying of the {motion} isn't\r\nvery fast. For motions that cover many words or entire sentences, an empty\r\nbase isn't helpful, there would be far too many matches. To ensure a\r\ncompletion base, this completion includes more than the usual keyword\r\ncharacters directly before the cursor. It looks for the following before the\r\ncursor, possibly with whitespace between it and the cursor:\r\n- keyword character(s), e.g \"foo\" in \"return (foo|\"\r\n- non-keyword non-whitespace character(s), e.g. \"\/*\" in \"return 0; \/* |\"\r\n- keyword character(s) followed by non-keyword non-whitespace characters,\r\n  e.g. \"foo(\" in \"return foo(|\"\r\nWhen the completion base starts with a keyword character, matches must start\r\nat a \\<word border.\r\nAlternatively, you can pre-select the base (via select or visual mode) before\r\ninvoking the completion. This ensures that the best context for completion is\r\nchosen.\r\n\r\nInput the {motion}.\r\nYou can then search forward and backward via CTRL-N \/ CTRL-P, as usual.\r\n\r\nCTRL-X CTRL-M           The completion first queries for {motion} (press\r\n                        <Enter> to conclude), then finds matches starting with\r\n                        the MotionComplete-base text before the cursor,\r\n                        covering {motion}.\r\n\r\n{Visual}CTRL-X CTRL-M   The completion first queries for {motion} (press\r\n                        <Enter> to conclude), then finds matches starting with\r\n                        the selected text, covering {motion}.\r\n                        Use this to define the completion base text (quickly\r\n                        done from insert mode via [CTRL-]SHIFT-<Left>) for\r\n                        better matches.\r\n\r\nEXAMPLE\r\nA quick|\r\n       ^ cursor, just triggered motion completion.\r\n\r\n(Somewhere else, a match:)\r\n    v---v completion base\r\nThe quick brown fox jumps over the lazy dog.\r\n    ^----------- \"5w\" --------^ completion via motion 5w","install_details":"INSTALLATION\r\nThis script is packaged as a vimball. If you have the \"gunzip\" decompressor\r\nin your PATH, simply edit the *.vmb.gz package in Vim; otherwise, decompress\r\nthe archive first, e.g. using WinZip. Inside Vim, install by sourcing the\r\nvimball or via the :UseVimball command.\r\n    vim MotionComplete*.vmb.gz\r\n    :so %\r\nTo uninstall, use the :RmVimball command.\r\n\r\nDEPENDENCIES\r\n- Requires Vim 7.0 or higher.\r\n- Requires the CompleteHelper.vim plugin (vimscript #3914).\r\n\r\nCONFIGURATION\r\nFor a permanent configuration, put the following commands into your vimrc:\r\n\r\nAnaloguous to the 'complete' option, you can specify which buffers will be\r\nscanned for completion candidates. Currently, '.' (current buffer), and 'w'\r\n(buffers from other windows) are supported.\r\n    let g:MotionComplete_complete = '.,w'\r\nThe global setting can be overridden for a particular buffer\r\n(b:MotionComplete_complete).\r\n\r\nTo avoid that huge amounts of text are offered for completion, the maximum\r\nnumber of characters to be captured by {motion} is limited:\r\n    let g:MotionComplete_maxCaptureLength = &columns * 3\r\n\r\nTo speed up the search and to avoid that many lines are offered for\r\ncompletion, the maximum number of lines to be searched for \/pattern\/ and\r\n?pattern? motions is limited:\r\n    let g:MotionComplete_searchScopeLines = 5\r\n\r\nIf you want to use different mappings, map your keys to the\r\n<Plug>(MotionComplete) mapping targets _before_ sourcing the script (e.g.\r\nin your vimrc):\r\n    imap <C-x><C-m> <Plug>(MotionComplete)\r\n    xmap <C-x><C-m> <Plug>(MotionComplete)\r\n    smap <C-x><C-m> <Plug>(MotionComplete)","5":"INSTALLATION\r\nThis script is packaged as a vimball. If you have the \"gunzip\" decompressor\r\nin your PATH, simply edit the *.vmb.gz package in Vim; otherwise, decompress\r\nthe archive first, e.g. using WinZip. Inside Vim, install by sourcing the\r\nvimball or via the :UseVimball command.\r\n    vim MotionComplete*.vmb.gz\r\n    :so %\r\nTo uninstall, use the :RmVimball command.\r\n\r\nDEPENDENCIES\r\n- Requires Vim 7.0 or higher.\r\n- Requires the CompleteHelper.vim plugin (vimscript #3914).\r\n\r\nCONFIGURATION\r\nFor a permanent configuration, put the following commands into your vimrc:\r\n\r\nAnaloguous to the 'complete' option, you can specify which buffers will be\r\nscanned for completion candidates. Currently, '.' (current buffer), and 'w'\r\n(buffers from other windows) are supported.\r\n    let g:MotionComplete_complete = '.,w'\r\nThe global setting can be overridden for a particular buffer\r\n(b:MotionComplete_complete).\r\n\r\nTo avoid that huge amounts of text are offered for completion, the maximum\r\nnumber of characters to be captured by {motion} is limited:\r\n    let g:MotionComplete_maxCaptureLength = &columns * 3\r\n\r\nTo speed up the search and to avoid that many lines are offered for\r\ncompletion, the maximum number of lines to be searched for \/pattern\/ and\r\n?pattern? motions is limited:\r\n    let g:MotionComplete_searchScopeLines = 5\r\n\r\nIf you want to use different mappings, map your keys to the\r\n<Plug>(MotionComplete) mapping targets _before_ sourcing the script (e.g.\r\nin your vimrc):\r\n    imap <C-x><C-m> <Plug>(MotionComplete)\r\n    xmap <C-x><C-m> <Plug>(MotionComplete)\r\n    smap <C-x><C-m> <Plug>(MotionComplete)","first_name":"Ingo","6":"Ingo","last_name":"Karkat","7":"Karkat","releases":[{"0":"4265","vim_version":"7.0","1":"7.0","script_version":"1.00","2":"1.00","version_comment":"Initial upload","3":"Initial upload","package":"MotionComplete-1.00.vmb.gz","4":"MotionComplete-1.00.vmb.gz","src_id":"18782","5":"18782","creation_date":"1350043087","6":"1350043087"}]},"4264":{"script_id":"4264","0":"4264","script_name":"VimChatBot","1":"VimChatBot","script_type":"game","2":"game","summary":"A simple self-teaching chat bot game for Vim","3":"A simple self-teaching chat bot game for Vim","description":"Agetian's Vim ChatBot (C) 2012 by Michael Kamensky, all rights reserved.\r\nThis script is distributed under Vim license.\r\n==============================================================================\r\n\r\nVim ChatBot is a simple self-teaching chat bot game for Vim. It will try to\r\ncommunicate with the human and will accumulate the human's questions and answers\r\nover time, utilizing them later and trying to mimic human behavior. This chat\r\nbot is not meant to be smart, at best it resembles a talking parrot and it's far\r\nfrom being a real human-like chat robot companion. It's meant to be fun and it\r\nwas originally intended as a little project to teach myself how to script Vim.\r\n\r\nIMPORTANT -- READ BEFORE USING OR DON'T TELL ME YOU WERE NOT WARNED:\r\n====================================================================\r\n\r\nVim ChatBot will use the currently open file in the buffer as a source and as a\r\ntarget for its database of known questions and replies! It will automatically\r\nappend new lines to the end of the current file as it learns the phrases from\r\nthe human! Therefore, if you were working on some important document prior to\r\nstarting the chat bot, make sure you switch to a new document or open your chat\r\ndatabase before initiating a conversation.\r\n \r\nVim ChatBot will never automatically save the file for you though, and it's\r\nalways up to you to decide if you want to save the updated database or not. You\r\nshould do it explicitly using the :write (or another command) to save the file. \r\n\r\nVim ChatBot utilizes the concept of a here-document (similar to here-documents\r\nin bash) to be able to store its database of known questions and replies in the\r\nscript file itself. When VimChatBot.vim is opened in Vim, the chat bot will\r\nautomatically append new entries to the end of the script file as it learns new\r\nphrases from you, and it will not corrupt the script file. If you'd like to keep\r\nthe updated database, you need to make sure you save the script file (:w or :x)\r\nafter you're done chatting.\r\n\r\nStarting the Vim ChatBot\r\n========================\r\n\r\nBy default, Vim ChatBot maps itself to the <Leader>Cb command in normal mode\r\n(<Leader> is the backslash symbol by default, so unless you've changed your\r\nleader, the default command to start Vim Chatbot is \\Cb ).\r\n\r\nIf the <Leader>Cb command is already taken by something among your scripts, feel\r\nfree to change the mapping (just search for nnoremap in the script file and\r\nchange the mapping to another combination of keys).\r\n\r\nMacros\r\n======\r\n\r\nYou can use the following macros when typing answers, the bot will also utilize\r\nthem when learning to use the phrase from you:\r\n\r\n$TIME$ - refers to the current time.\r\n$TIME12$ - (experimental) refers to the current time in 12-hour format.\r\n$DAY$ - refers to the current day.\r\n$WEEKDAY$ - refers to the current day of the week.\r\n$MONTH$ - refers to the current month.\r\n$YEAR$ - refers to the current year.\r\n\r\nFinishing the conversation\r\n==========================\r\n\r\nTo finish the conversation, type \/Q into the \"You Say:\" prompt. Unless you are\r\nasked something (or told something) by the bot and it's waiting for you to teach\r\nit how to reply to that, \/Q will end the conversation immediately. If, however,\r\nthe bot is waiting for your reply to learn something from you, \/Q will merely\r\ninform the bot that you don't have the intention to answer the question. If you\r\nwant to quit the conversation altogether, you will need to type \/Q again.\r\n\r\nCtrl+C can be used as the universal quit command if you want to quit chatting\r\nwhen in the middle of a bot-asked question and when you don't feel like typing\r\n\/Q twice.\r\n\r\nMagical contexts\r\n================\r\n\r\nBy default, Vim ChatBot treats the first two responses as special, that is, the\r\nbot will store a separate set of responses for the phrases you type as your\r\nfirst and as your second lines, and will respond accordingly. This is to prevent\r\nabsolute stupidity, such as saying \"Hi!\" in the middle of a conversation. The\r\nnumber of \"magical contexts\" (responses which should be treated specially) can\r\nbe modified and is stored in the s:MagicalContexts variable.\r\n\r\nDatabase Modification\r\n=====================\r\n\r\nYou can modify the database manually by adding or removing phrases in case you\r\nare not satisfied with something that the bot has learned or would like to teach\r\nit something without having to go through the process of teaching-by-chatting. \r\n\r\nThe database for Vim ChatBot is stored in the following way:\r\n\r\n<Phrase>:::[MagicalContextID]\r\n<Response1>\r\n<Response2>\r\n...\r\n<BLANK_LINE>\r\n\r\nQuirks\r\n======\r\n\r\nThe database structure described above has an important consequence: when\r\nspeaking to Vim ChatBot, never use a triple colon (:::) symbol in your phrases,\r\nthey will confuse the bot and may make it behave more stupidly than normal.\r\n\r\nIn the beginning of the conversation, the bot might seem not to recognize some\r\nof the phrases you taught it before - this is due to the magical contexts\r\nkicking in, the bot hasn't yet been taught to recognize that specific phrase in\r\nthat particular position. This is normal behavior, just patiently repeat the\r\nlesson.\r\n\r\nIf you have a Python-enabled version of Vim, ChatBot will utilize the Python\r\nrandom number generation algorithm from the \"random\" library. If your Vim is not\r\nPython-enabled, a simpler algorithm will be utilized instead, based on the idea\r\nsuggested by Bee-9 at:\r\nhttp:\/\/vim.1045645.n5.nabble.com\/simple-16-bit-random-number-generator-td2843842.html\r\nThis algorithm is less efficient and will produce less random numbers, which may\r\nor may not be apparent in the actual conversation with the bot (your mileage may\r\nvary). At any rate, a Python-enabled Vim is recommended for more randomness, but\r\nnot strictly required.\r\n\r\n==============================================================================\r\nRemember: Don't take Vim ChatBot seriously and just have fun! :)\r\n","4":"Agetian's Vim ChatBot (C) 2012 by Michael Kamensky, all rights reserved.\r\nThis script is distributed under Vim license.\r\n==============================================================================\r\n\r\nVim ChatBot is a simple self-teaching chat bot game for Vim. It will try to\r\ncommunicate with the human and will accumulate the human's questions and answers\r\nover time, utilizing them later and trying to mimic human behavior. This chat\r\nbot is not meant to be smart, at best it resembles a talking parrot and it's far\r\nfrom being a real human-like chat robot companion. It's meant to be fun and it\r\nwas originally intended as a little project to teach myself how to script Vim.\r\n\r\nIMPORTANT -- READ BEFORE USING OR DON'T TELL ME YOU WERE NOT WARNED:\r\n====================================================================\r\n\r\nVim ChatBot will use the currently open file in the buffer as a source and as a\r\ntarget for its database of known questions and replies! It will automatically\r\nappend new lines to the end of the current file as it learns the phrases from\r\nthe human! Therefore, if you were working on some important document prior to\r\nstarting the chat bot, make sure you switch to a new document or open your chat\r\ndatabase before initiating a conversation.\r\n \r\nVim ChatBot will never automatically save the file for you though, and it's\r\nalways up to you to decide if you want to save the updated database or not. You\r\nshould do it explicitly using the :write (or another command) to save the file. \r\n\r\nVim ChatBot utilizes the concept of a here-document (similar to here-documents\r\nin bash) to be able to store its database of known questions and replies in the\r\nscript file itself. When VimChatBot.vim is opened in Vim, the chat bot will\r\nautomatically append new entries to the end of the script file as it learns new\r\nphrases from you, and it will not corrupt the script file. If you'd like to keep\r\nthe updated database, you need to make sure you save the script file (:w or :x)\r\nafter you're done chatting.\r\n\r\nStarting the Vim ChatBot\r\n========================\r\n\r\nBy default, Vim ChatBot maps itself to the <Leader>Cb command in normal mode\r\n(<Leader> is the backslash symbol by default, so unless you've changed your\r\nleader, the default command to start Vim Chatbot is \\Cb ).\r\n\r\nIf the <Leader>Cb command is already taken by something among your scripts, feel\r\nfree to change the mapping (just search for nnoremap in the script file and\r\nchange the mapping to another combination of keys).\r\n\r\nMacros\r\n======\r\n\r\nYou can use the following macros when typing answers, the bot will also utilize\r\nthem when learning to use the phrase from you:\r\n\r\n$TIME$ - refers to the current time.\r\n$TIME12$ - (experimental) refers to the current time in 12-hour format.\r\n$DAY$ - refers to the current day.\r\n$WEEKDAY$ - refers to the current day of the week.\r\n$MONTH$ - refers to the current month.\r\n$YEAR$ - refers to the current year.\r\n\r\nFinishing the conversation\r\n==========================\r\n\r\nTo finish the conversation, type \/Q into the \"You Say:\" prompt. Unless you are\r\nasked something (or told something) by the bot and it's waiting for you to teach\r\nit how to reply to that, \/Q will end the conversation immediately. If, however,\r\nthe bot is waiting for your reply to learn something from you, \/Q will merely\r\ninform the bot that you don't have the intention to answer the question. If you\r\nwant to quit the conversation altogether, you will need to type \/Q again.\r\n\r\nCtrl+C can be used as the universal quit command if you want to quit chatting\r\nwhen in the middle of a bot-asked question and when you don't feel like typing\r\n\/Q twice.\r\n\r\nMagical contexts\r\n================\r\n\r\nBy default, Vim ChatBot treats the first two responses as special, that is, the\r\nbot will store a separate set of responses for the phrases you type as your\r\nfirst and as your second lines, and will respond accordingly. This is to prevent\r\nabsolute stupidity, such as saying \"Hi!\" in the middle of a conversation. The\r\nnumber of \"magical contexts\" (responses which should be treated specially) can\r\nbe modified and is stored in the s:MagicalContexts variable.\r\n\r\nDatabase Modification\r\n=====================\r\n\r\nYou can modify the database manually by adding or removing phrases in case you\r\nare not satisfied with something that the bot has learned or would like to teach\r\nit something without having to go through the process of teaching-by-chatting. \r\n\r\nThe database for Vim ChatBot is stored in the following way:\r\n\r\n<Phrase>:::[MagicalContextID]\r\n<Response1>\r\n<Response2>\r\n...\r\n<BLANK_LINE>\r\n\r\nQuirks\r\n======\r\n\r\nThe database structure described above has an important consequence: when\r\nspeaking to Vim ChatBot, never use a triple colon (:::) symbol in your phrases,\r\nthey will confuse the bot and may make it behave more stupidly than normal.\r\n\r\nIn the beginning of the conversation, the bot might seem not to recognize some\r\nof the phrases you taught it before - this is due to the magical contexts\r\nkicking in, the bot hasn't yet been taught to recognize that specific phrase in\r\nthat particular position. This is normal behavior, just patiently repeat the\r\nlesson.\r\n\r\nIf you have a Python-enabled version of Vim, ChatBot will utilize the Python\r\nrandom number generation algorithm from the \"random\" library. If your Vim is not\r\nPython-enabled, a simpler algorithm will be utilized instead, based on the idea\r\nsuggested by Bee-9 at:\r\nhttp:\/\/vim.1045645.n5.nabble.com\/simple-16-bit-random-number-generator-td2843842.html\r\nThis algorithm is less efficient and will produce less random numbers, which may\r\nor may not be apparent in the actual conversation with the bot (your mileage may\r\nvary). At any rate, a Python-enabled Vim is recommended for more randomness, but\r\nnot strictly required.\r\n\r\n==============================================================================\r\nRemember: Don't take Vim ChatBot seriously and just have fun! :)\r\n","install_details":"Either put the file VimChatBot.vim to your \"plugin\" folder so it's auto-loaded, or unpack to any folder you like and then :source the script file when necessary.\r\n\r\nBefore initiating the chat bot conversation, make sure you either:\r\n1) have the script file itself open in the current buffer (in this case, the here-document database in the end of VimChatBot.vim will be used);\r\n2) have your own chat database file open in the current buffer (should initially be an empty file, will then be auto-filled with known questions and replies by the chat bot);\r\n3) have a new empty file open in the current buffer (in case you don't yet have a chat bot database and you don't want to use VimChatBot.vim as a source\/target for the database).\r\n\r\nOnce ready, use the <Leader>Cb command in normal mode (by default) to initiate a conversation.\r\nMake sure you've read and understood all the information in the detailed description before starting!\r\n","5":"Either put the file VimChatBot.vim to your \"plugin\" folder so it's auto-loaded, or unpack to any folder you like and then :source the script file when necessary.\r\n\r\nBefore initiating the chat bot conversation, make sure you either:\r\n1) have the script file itself open in the current buffer (in this case, the here-document database in the end of VimChatBot.vim will be used);\r\n2) have your own chat database file open in the current buffer (should initially be an empty file, will then be auto-filled with known questions and replies by the chat bot);\r\n3) have a new empty file open in the current buffer (in case you don't yet have a chat bot database and you don't want to use VimChatBot.vim as a source\/target for the database).\r\n\r\nOnce ready, use the <Leader>Cb command in normal mode (by default) to initiate a conversation.\r\nMake sure you've read and understood all the information in the detailed description before starting!\r\n","first_name":"Michael","6":"Michael","last_name":"Kamensky","7":"Kamensky","releases":[{"0":"4264","vim_version":"7.4","1":"7.4","script_version":"1.9","2":"1.9","version_comment":"- Updated the stupid line endings to use Unix format so that the chat bot works equally well on both Windows and *nix systems without having one to do :setlocal ff=unix and :w on the script before using it.","3":"- Updated the stupid line endings to use Unix format so that the chat bot works equally well on both Windows and *nix systems without having one to do :setlocal ff=unix and :w on the script before using it.","package":"VimChatBot_v19.zip","4":"VimChatBot_v19.zip","src_id":"21760","5":"21760","creation_date":"1397233550","6":"1397233550"},{"0":"4264","vim_version":"7.3","1":"7.3","script_version":"1.8","2":"1.8","version_comment":"- **NOTE:** this is a special update build for Vim\/GVim v7.4 only! If you are using Vim 7.3 or an earlier build, please keep using VimChatBot v1.7 which is actually the preferred build for older Vims! This version requires Vim 7.4, the script interface on vim.org doesn't let me specify 7.4 as the target version, so I had to specify 7.3 instead, sorry.\r\n- updated the human input routines to account for some of the changes in Vim 7.4 that broke the echo output.","3":"- **NOTE:** this is a special update build for Vim\/GVim v7.4 only! If you are using Vim 7.3 or an earlier build, please keep using VimChatBot v1.7 which is actually the preferred build for older Vims! This version requires Vim 7.4, the script interface on vim.org doesn't let me specify 7.4 as the target version, so I had to specify 7.3 instead, sorry.\r\n- updated the human input routines to account for some of the changes in Vim 7.4 that broke the echo output.","package":"VimChatBot_v18.zip","4":"VimChatBot_v18.zip","src_id":"20747","5":"20747","creation_date":"1378223270","6":"1378223270"},{"0":"4264","vim_version":"7.0","1":"7.0","script_version":"1.7","2":"1.7","version_comment":"- Made one of the chat bot's inquiries less confusing to the user.\r\n","3":"- Made one of the chat bot's inquiries less confusing to the user.\r\n","package":"VimChatBot_v17.zip","4":"VimChatBot_v17.zip","src_id":"19228","5":"19228","creation_date":"1356110786","6":"1356110786"},{"0":"4264","vim_version":"7.0","1":"7.0","script_version":"1.6","2":"1.6","version_comment":"- Auto set the regular expression search to ignore case mode prior to initiating the chat (to make it case-insensitive no matter what settings the user has), then restore the case-sensitivity setting after the chat is over.\r\n","3":"- Auto set the regular expression search to ignore case mode prior to initiating the chat (to make it case-insensitive no matter what settings the user has), then restore the case-sensitivity setting after the chat is over.\r\n","package":"VimChatBot_v16.zip","4":"VimChatBot_v16.zip","src_id":"18806","5":"18806","creation_date":"1350241359","6":"1350241359"},{"0":"4264","vim_version":"7.0","1":"7.0","script_version":"1.5","2":"1.5","version_comment":"- Added a possibility of the chat bot initiating the conversation first (has a random 50% chance of happening).\r\n- Some minor refactoring\r\n","3":"- Added a possibility of the chat bot initiating the conversation first (has a random 50% chance of happening).\r\n- Some minor refactoring\r\n","package":"VimChatBot_v15.zip","4":"VimChatBot_v15.zip","src_id":"18805","5":"18805","creation_date":"1350233603","6":"1350233603"},{"0":"4264","vim_version":"7.0","1":"7.0","script_version":"1.4","2":"1.4","version_comment":"- Added support for macros $HOUR$, $MINUTE$, and $SECOND$ referring to the individual components (hours, minutes, seconds) of current time.\r\n","3":"- Added support for macros $HOUR$, $MINUTE$, and $SECOND$ referring to the individual components (hours, minutes, seconds) of current time.\r\n","package":"VimChatBot_v14.zip","4":"VimChatBot_v14.zip","src_id":"18794","5":"18794","creation_date":"1350131910","6":"1350131910"},{"0":"4264","vim_version":"7.3","1":"7.3","script_version":"1.3","2":"1.3","version_comment":"- Fixed a bug with the chat initiation always mapping to \\Cb instead of <Leader>Cb\r\n- Less global namespace pollution due to the use of local functions\r\n- Added a Vim version check, currently set to v7.0 (not sure if this script would run on Vim below v7.0, don't have an older build to test on).\r\n- Added a load-only-once check.\r\n- Added some basic documentation to the script file itself.\r\n- Changed the name of the function MainChatLoop to VCB_MainChatLoop, following the naming scheme of other functions.\r\n","3":"- Fixed a bug with the chat initiation always mapping to \\Cb instead of <Leader>Cb\r\n- Less global namespace pollution due to the use of local functions\r\n- Added a Vim version check, currently set to v7.0 (not sure if this script would run on Vim below v7.0, don't have an older build to test on).\r\n- Added a load-only-once check.\r\n- Added some basic documentation to the script file itself.\r\n- Changed the name of the function MainChatLoop to VCB_MainChatLoop, following the naming scheme of other functions.\r\n","package":"VimChatBot_v13.zip","4":"VimChatBot_v13.zip","src_id":"18791","5":"18791","creation_date":"1350053004","6":"1350053004"},{"0":"4264","vim_version":"7.3","1":"7.3","script_version":"1.2b","2":"1.2b","version_comment":"- Some more code cleanup, added the proper header to the script, added the vi compatibility mode check\/workaround. Functionally the same as v1.2a. ","3":"- Some more code cleanup, added the proper header to the script, added the vi compatibility mode check\/workaround. Functionally the same as v1.2a. ","package":"VimChatBot_v12b.zip","4":"VimChatBot_v12b.zip","src_id":"18790","5":"18790","creation_date":"1350049667","6":"1350049667"},{"0":"4264","vim_version":"7.3","1":"7.3","script_version":"1.2a","2":"1.2a","version_comment":"Code Cleanup: Gave the functions more unique names, hopefully this will ensure much better compatibility with other scripts.","3":"Code Cleanup: Gave the functions more unique names, hopefully this will ensure much better compatibility with other scripts.","package":"VimChatBot_v12a.zip","4":"VimChatBot_v12a.zip","src_id":"18786","5":"18786","creation_date":"1350045232","6":"1350045232"},{"0":"4264","vim_version":"7.3","1":"7.3","script_version":"1.2","2":"1.2","version_comment":"- Code cleanup: removed the unnecessary \"s:\" flags for most variables that just need to be local to their functions. No other functional difference from the previous version.","3":"- Code cleanup: removed the unnecessary \"s:\" flags for most variables that just need to be local to their functions. No other functional difference from the previous version.","package":"VimChatBot_v12.zip","4":"VimChatBot_v12.zip","src_id":"18783","5":"18783","creation_date":"1350043639","6":"1350043639"},{"0":"4264","vim_version":"7.3","1":"7.3","script_version":"1.1","2":"1.1","version_comment":"- Added some basic macro functionality, you can now use $TIME$, $DAY$, $WEEKDAY$, $MONTH$, and $YEAR$ to refer to the current time\/date while speaking. Check the README for details.\r\n- Fixed a potential crash-prone spot in one of the functions. ","3":"- Added some basic macro functionality, you can now use $TIME$, $DAY$, $WEEKDAY$, $MONTH$, and $YEAR$ to refer to the current time\/date while speaking. Check the README for details.\r\n- Fixed a potential crash-prone spot in one of the functions. ","package":"VimChatBot_v11.zip","4":"VimChatBot_v11.zip","src_id":"18781","5":"18781","creation_date":"1350039103","6":"1350039103"},{"0":"4264","vim_version":"7.3","1":"7.3","script_version":"1.0a","2":"1.0a","version_comment":"- Updated the README file with some additional information on the possible quirks in behavior, please read the \"Quirks\" section of the updated file.\r\n","3":"- Updated the README file with some additional information on the possible quirks in behavior, please read the \"Quirks\" section of the updated file.\r\n","package":"VimChatBot_v10a.zip","4":"VimChatBot_v10a.zip","src_id":"18779","5":"18779","creation_date":"1350036185","6":"1350036185"},{"0":"4264","vim_version":"7.3","1":"7.3","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"VimChatBot_v10.zip","4":"VimChatBot_v10.zip","src_id":"18777","5":"18777","creation_date":"1350034255","6":"1350034255"}]},"4263":{"script_id":"4263","0":"4263","script_name":"autotags","1":"autotags","script_type":"utility","2":"utility","summary":"vim plugin for easy ctags and cscope handling in a separate directory ","3":"vim plugin for easy ctags and cscope handling in a separate directory ","description":"This script is a wrapper for ctags and cscope, so tags for all languages\r\nsupported by ctags can be build (cscope is additionally used for C\/C++).\r\n\r\nFeatures:\r\n1. No configuration needed\r\n2. Build\/rebuild index for project with a single key stroke\r\n3. Tags are loaded then automatically when a file is opened anywhere in project tree\r\n4. Tags are stored in a separate directory and don't clog you project tree \r\n5. Extra directories (like library source or includes) can be added with a single key stroke too\r\n\r\nPut autotags.vim in your ~\/.vim\/plugin directory, open source code and\r\npress F4 (map AutotagsUpdate to change it).\r\n\r\nYou can reindex sources by pressing F4 again.\r\n\r\nTo build and load additional tags for another directory (i.e. external\r\nproject or library code you want to navigate to) press F3 (or map\r\nAutotagsAdd).\r\n\r\nScript builds and loads ctags and cscope databases via a single command.\r\nAll ctags and cscope files are stored in separate directory ~\/.autotags by\r\ndefault. You can set it via\r\n    let g:autotagsdir = $HOME.\"\/boo\"\r\n\r\nProject root directory will be asked when indexing new project. After that\r\ntags will be loaded automatically when source files somewhere in project\r\ntree are opened (if path contains project root).\r\n\r\nExact tags location:\r\n~\/.autotags\/byhash\/<source dir name hash>\/<ctags and cscope files>\r\n\r\nAlso `origin` symlink points back to source dir\r\n~\/.autotags\/byhash\/<source dir name hash>\/origin\r\n\r\n`include_*` symlinks point to additional tags for external directories\r\n~\/.autotags\/byhash\/<source dir name hash>\/include_*\r\n\r\nTags for non-existing source directories are removed automatically\r\n(checked at startup)\r\n\r\nAlso ctags file ~\/.autotags\/global_tags is built for \/usr\/include once\r\n\r\nPlatforms:\r\nunix, cygwin\r\n\r\nDependencies:\r\nctags and cscope\r\nmd5sum\r\n\r\ncscope_maps.vim plugin is recommended\r\n\r\nHomepage:\r\nhttps:\/\/github.com\/basilgor\/vim-autotags","4":"This script is a wrapper for ctags and cscope, so tags for all languages\r\nsupported by ctags can be build (cscope is additionally used for C\/C++).\r\n\r\nFeatures:\r\n1. No configuration needed\r\n2. Build\/rebuild index for project with a single key stroke\r\n3. Tags are loaded then automatically when a file is opened anywhere in project tree\r\n4. Tags are stored in a separate directory and don't clog you project tree \r\n5. Extra directories (like library source or includes) can be added with a single key stroke too\r\n\r\nPut autotags.vim in your ~\/.vim\/plugin directory, open source code and\r\npress F4 (map AutotagsUpdate to change it).\r\n\r\nYou can reindex sources by pressing F4 again.\r\n\r\nTo build and load additional tags for another directory (i.e. external\r\nproject or library code you want to navigate to) press F3 (or map\r\nAutotagsAdd).\r\n\r\nScript builds and loads ctags and cscope databases via a single command.\r\nAll ctags and cscope files are stored in separate directory ~\/.autotags by\r\ndefault. You can set it via\r\n    let g:autotagsdir = $HOME.\"\/boo\"\r\n\r\nProject root directory will be asked when indexing new project. After that\r\ntags will be loaded automatically when source files somewhere in project\r\ntree are opened (if path contains project root).\r\n\r\nExact tags location:\r\n~\/.autotags\/byhash\/<source dir name hash>\/<ctags and cscope files>\r\n\r\nAlso `origin` symlink points back to source dir\r\n~\/.autotags\/byhash\/<source dir name hash>\/origin\r\n\r\n`include_*` symlinks point to additional tags for external directories\r\n~\/.autotags\/byhash\/<source dir name hash>\/include_*\r\n\r\nTags for non-existing source directories are removed automatically\r\n(checked at startup)\r\n\r\nAlso ctags file ~\/.autotags\/global_tags is built for \/usr\/include once\r\n\r\nPlatforms:\r\nunix, cygwin\r\n\r\nDependencies:\r\nctags and cscope\r\nmd5sum\r\n\r\ncscope_maps.vim plugin is recommended\r\n\r\nHomepage:\r\nhttps:\/\/github.com\/basilgor\/vim-autotags","install_details":"Put autotags.vim in your ~\/.vim\/plugin directory","5":"Put autotags.vim in your ~\/.vim\/plugin directory","first_name":"Basil","6":"Basil","last_name":"Gor","7":"Gor","releases":[{"0":"4263","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"autotags.vim","4":"autotags.vim","src_id":"18776","5":"18776","creation_date":"1349982767","6":"1349982767"}]},"4262":{"script_id":"4262","0":"4262","script_name":"vim-xdc-syntax","1":"vim-xdc-syntax","script_type":"syntax","2":"syntax","summary":"Syntax highlighting for Xilinx Design Constraints","3":"Syntax highlighting for Xilinx Design Constraints","description":"Grab the latest dev version from github: https:\/\/github.com\/amal-khailtash\/vim-xdc-syntax.git\r\n\r\n### References\r\n\r\n* [Vivado Design Suite User Guide - Using Constraints](http:\/\/www.xilinx.com\/support\/documentation\/sw_manuals\/xilinx2013_1\/ug903-vivado-using-constraints.pdf)\r\n* [Vivado Design Suite Tcl Command Reference Guide](http:\/\/www.xilinx.com\/support\/documentation\/sw_manuals\/xilinx2013_1\/ug835-vivado-tcl-commands.pdf)","4":"Grab the latest dev version from github: https:\/\/github.com\/amal-khailtash\/vim-xdc-syntax.git\r\n\r\n### References\r\n\r\n* [Vivado Design Suite User Guide - Using Constraints](http:\/\/www.xilinx.com\/support\/documentation\/sw_manuals\/xilinx2013_1\/ug903-vivado-using-constraints.pdf)\r\n* [Vivado Design Suite Tcl Command Reference Guide](http:\/\/www.xilinx.com\/support\/documentation\/sw_manuals\/xilinx2013_1\/ug835-vivado-tcl-commands.pdf)","install_details":"## Installation  \r\n\r\n_\\*Assuming **[VIM_ROOT]** is ~\/.vim (on \\*nix) or ~\/vimfiles (on Windows)_\r\n\r\nThis syntax file requires Vim 7 or higher is made up of 2 files:\r\n\r\n    ftdetect\/xdc.vim\r\n    syntax\/xdc.vim\r\n\r\n### Classic Install\r\n\r\n* Extract the zip contents to your **[VIM_ROOT]**\r\n\r\n### Vundle Install\r\n\r\n* Add \"Bundle 'vim-xdc-syntax'\" to your vimrc\r\n\r\n### Pathogen Install\r\n\r\n1. Navigate to your **[VIM_ROOT]\/bundle** directory\r\n2. git clone https:\/\/github.com\/amal-khailtash\/vim-xdc-syntax.git\r\n","5":"## Installation  \r\n\r\n_\\*Assuming **[VIM_ROOT]** is ~\/.vim (on \\*nix) or ~\/vimfiles (on Windows)_\r\n\r\nThis syntax file requires Vim 7 or higher is made up of 2 files:\r\n\r\n    ftdetect\/xdc.vim\r\n    syntax\/xdc.vim\r\n\r\n### Classic Install\r\n\r\n* Extract the zip contents to your **[VIM_ROOT]**\r\n\r\n### Vundle Install\r\n\r\n* Add \"Bundle 'vim-xdc-syntax'\" to your vimrc\r\n\r\n### Pathogen Install\r\n\r\n1. Navigate to your **[VIM_ROOT]\/bundle** directory\r\n2. git clone https:\/\/github.com\/amal-khailtash\/vim-xdc-syntax.git\r\n","first_name":"Amal","6":"Amal","last_name":"Khailtash","7":"Khailtash","releases":[{"0":"4262","vim_version":"7.0","1":"7.0","script_version":"1.2","2":"1.2","version_comment":"Skipped v1.1","3":"Skipped v1.1","package":"vim-xdc-syntax.zip","4":"vim-xdc-syntax.zip","src_id":"19827","5":"19827","creation_date":"1366137002","6":"1366137002"},{"0":"4262","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"vim-xdc-syntax.zip","4":"vim-xdc-syntax.zip","src_id":"18774","5":"18774","creation_date":"1349898624","6":"1349898624"}]},"4261":{"script_id":"4261","0":"4261","script_name":"tumblr.vim","1":"tumblr.vim","script_type":"syntax","2":"syntax","summary":"Syntax highlighting for Tumblr themes.","3":"Syntax highlighting for Tumblr themes.","description":"Syntax highlighting for Tumblr themes. \r\n\r\nScreenshot: http:\/\/i.imgur.com\/2IzwA.png\r\nSource: https:\/\/github.com\/liamcurry\/tumblr.vim\r\n\r\nBy default it will highlight any files matching *.tumblr.html, but you can change this by adding this to your .vimrc (replace .tblr.html with whatever extension you like):\r\n\r\nau BufRead,BufNewFile *.tblr.html set filetype=tumblr\r\n\r\nNote: this is a fork of Liam Cooke's original version here: http:\/\/www.vim.org\/scripts\/script.php?script_id=3011. The main difference between the repositories is that this version is easily installable via pathogen or vundle, and it requires no changes to your .vimrc file.","4":"Syntax highlighting for Tumblr themes. \r\n\r\nScreenshot: http:\/\/i.imgur.com\/2IzwA.png\r\nSource: https:\/\/github.com\/liamcurry\/tumblr.vim\r\n\r\nBy default it will highlight any files matching *.tumblr.html, but you can change this by adding this to your .vimrc (replace .tblr.html with whatever extension you like):\r\n\r\nau BufRead,BufNewFile *.tblr.html set filetype=tumblr\r\n\r\nNote: this is a fork of Liam Cooke's original version here: http:\/\/www.vim.org\/scripts\/script.php?script_id=3011. The main difference between the repositories is that this version is easily installable via pathogen or vundle, and it requires no changes to your .vimrc file.","install_details":"With pathogen or vundle:\r\n\r\ngit clone https:\/\/github.com\/liamcurry\/tumblr.vim.git ~\/.vim\/bundle\/tumblr.vim\r\n\r\nWith pathogen or vundle and git submodules:\r\n\r\ngit submodule add https:\/\/github.com\/liamcurry\/tumblr.vim.git ~\/.vim\/bundle\/tumblr.vim\r\n\r\nOtherwise, download the zip file and place the files in their respective folders in your ~\/.vim folder.","5":"With pathogen or vundle:\r\n\r\ngit clone https:\/\/github.com\/liamcurry\/tumblr.vim.git ~\/.vim\/bundle\/tumblr.vim\r\n\r\nWith pathogen or vundle and git submodules:\r\n\r\ngit submodule add https:\/\/github.com\/liamcurry\/tumblr.vim.git ~\/.vim\/bundle\/tumblr.vim\r\n\r\nOtherwise, download the zip file and place the files in their respective folders in your ~\/.vim folder.","first_name":"Liam","6":"Liam","last_name":"Curry","7":"Curry","releases":[{"0":"4261","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"tumblr.vim.zip","4":"tumblr.vim.zip","src_id":"18772","5":"18772","creation_date":"1349889521","6":"1349889521"}]},"4260":{"script_id":"4260","0":"4260","script_name":"vim-herokudoc-theme","1":"vim-herokudoc-theme","script_type":"color scheme","2":"color scheme","summary":"Color scheme inspired Heroku documentation colors","3":"Color scheme inspired Heroku documentation colors","description":"Repo & Screenshot:\r\nhttps:\/\/github.com\/uu59\/vim-herokudoc-theme\r\n","4":"Repo & Screenshot:\r\nhttps:\/\/github.com\/uu59\/vim-herokudoc-theme\r\n","install_details":"1. Download and put this file into your ~\/.vim\/colors\r\n2. put \"colo herokudoc\" into your ~\/.vimrc\r\n3. (Re)start your Vim","5":"1. Download and put this file into your ~\/.vim\/colors\r\n2. put \"colo herokudoc\" into your ~\/.vimrc\r\n3. (Re)start your Vim","first_name":"uu","6":"uu","last_name":"59","7":"59","releases":[{"0":"4260","vim_version":"7.0","1":"7.0","script_version":"0.1.0","2":"0.1.0","version_comment":"support vim on terminal by CSApprox","3":"support vim on terminal by CSApprox","package":"herokudoc.vim","4":"herokudoc.vim","src_id":"19181","5":"19181","creation_date":"1355428111","6":"1355428111"},{"0":"4260","vim_version":"7.0","1":"7.0","script_version":"0.0.1","2":"0.0.1","version_comment":"Initial upload","3":"Initial upload","package":"herokudoc.vim","4":"herokudoc.vim","src_id":"18771","5":"18771","creation_date":"1349872212","6":"1349872212"}]},"4258":{"script_id":"4258","0":"4258","script_name":"sha3.vim","1":"sha3.vim","script_type":"utility","2":"utility","summary":"sha3 function","3":"sha3 function","description":":echo sha3#sha3_512('foo')\r\n1597842aac52bc9d13fe249d808afbf44da13524759477404c3592ee331173e89fe1cbf21a7e4360990d565fad4643cdb209d80fa41a91dea97e665022c92135\r\n","4":":echo sha3#sha3_512('foo')\r\n1597842aac52bc9d13fe249d808afbf44da13524759477404c3592ee331173e89fe1cbf21a7e4360990d565fad4643cdb209d80fa41a91dea97e665022c92135\r\n","install_details":"Copy this file to ~\/.vim\/autoload\/ directory.\r\n\r\nhttps:\/\/gist.github.com\/3848180","5":"Copy this file to ~\/.vim\/autoload\/ directory.\r\n\r\nhttps:\/\/gist.github.com\/3848180","first_name":"Yukihiro","6":"Yukihiro","last_name":"Nakadaira","7":"Nakadaira","releases":[{"0":"4258","vim_version":"7.3","1":"7.3","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"sha3.vim","4":"sha3.vim","src_id":"18760","5":"18760","creation_date":"1349656496","6":"1349656496"}]},"4257":{"script_id":"4257","0":"4257","script_name":"djangojump","1":"djangojump","script_type":"ftplugin","2":"ftplugin","summary":"jump between template, view, url  in django project","3":"jump between template, view, url  in django project","description":"description\r\n=============\r\n\r\nvim-djangojump plugin is used for \r\njumping between url, view function and \r\ntemplate immediately. \r\n\r\nnote: now open vim at django project\\\\'s \r\nroot path where has settings.py file \r\n\r\nemail: itachi.akatuki.sh@gmail.com\r\n\r\ntip: \r\n1. url => view function \r\n   :DUrltoview \/app1\/overview\/ \r\n\r\n2. view function ==> template file \r\n   :DViewtotpl (at line which contains \r\n   template\\\\'s name) \r\n\r\n   example code: \r\n      .... \r\n   (*)   return render_to_response(\\\\\\\"index.html\\\\\\\") \r\n\r\n   cursor at this line(*) and call command \r\n   :DViewtotpl \r\n\r\n3. template file ==> view function \r\n   :DTpltoview \r\n\r\n4. js which template includes ==> js source file\r\n   css which template includes ==> css source file\r\n   :DGotoscript\r\n\r\n5. reload cache \r\n   :DReloadCache\r\n\r\n6. url ==> template file\r\n   :DUrltotpl \/xxx\/yyy\/\r\n\r\ninstall details\r\n=============\r\n\r\nlinux platform is ok,  it\\'s not tested under windows platform, maybe it can work correctly. \r\n\r\n1. copy djangojump.vim to ~\/.vim\/plugin\/ folder \r\n2. open vim at django project root folder, then you can use these commands \r\n\r\nnote: this plugin need python2.6+ support, at first opening vim, it would be slow, but after it would work normally.\r\n\r\n\r\nhotkeys\r\n===============\r\ntemplate ==> view function\r\nnmap <c-d><c-t> :DTpltoview<CR>\r\n\r\nview function ==> view\r\nnmap <c-d><c-v> :DViewtotpl<CR>\r\n\r\nurl ==>  view function\r\nnmap <c-d><c-u> :DUrltoview \r\n\r\ntemplate ==> script(js, css)\r\nnmap <c-d><c-s> :DGotoscript<CR>\r\n\r\nreload cache if add file or remove file\r\nnmap <c-d><c-r> :DReloadCache<CR>\r\n\r\nurl ==> template file\r\nnmap <c-d><c-i> :DUrltotpl<CR>","4":"description\r\n=============\r\n\r\nvim-djangojump plugin is used for \r\njumping between url, view function and \r\ntemplate immediately. \r\n\r\nnote: now open vim at django project\\\\'s \r\nroot path where has settings.py file \r\n\r\nemail: itachi.akatuki.sh@gmail.com\r\n\r\ntip: \r\n1. url => view function \r\n   :DUrltoview \/app1\/overview\/ \r\n\r\n2. view function ==> template file \r\n   :DViewtotpl (at line which contains \r\n   template\\\\'s name) \r\n\r\n   example code: \r\n      .... \r\n   (*)   return render_to_response(\\\\\\\"index.html\\\\\\\") \r\n\r\n   cursor at this line(*) and call command \r\n   :DViewtotpl \r\n\r\n3. template file ==> view function \r\n   :DTpltoview \r\n\r\n4. js which template includes ==> js source file\r\n   css which template includes ==> css source file\r\n   :DGotoscript\r\n\r\n5. reload cache \r\n   :DReloadCache\r\n\r\n6. url ==> template file\r\n   :DUrltotpl \/xxx\/yyy\/\r\n\r\ninstall details\r\n=============\r\n\r\nlinux platform is ok,  it\\'s not tested under windows platform, maybe it can work correctly. \r\n\r\n1. copy djangojump.vim to ~\/.vim\/plugin\/ folder \r\n2. open vim at django project root folder, then you can use these commands \r\n\r\nnote: this plugin need python2.6+ support, at first opening vim, it would be slow, but after it would work normally.\r\n\r\n\r\nhotkeys\r\n===============\r\ntemplate ==> view function\r\nnmap <c-d><c-t> :DTpltoview<CR>\r\n\r\nview function ==> view\r\nnmap <c-d><c-v> :DViewtotpl<CR>\r\n\r\nurl ==>  view function\r\nnmap <c-d><c-u> :DUrltoview \r\n\r\ntemplate ==> script(js, css)\r\nnmap <c-d><c-s> :DGotoscript<CR>\r\n\r\nreload cache if add file or remove file\r\nnmap <c-d><c-r> :DReloadCache<CR>\r\n\r\nurl ==> template file\r\nnmap <c-d><c-i> :DUrltotpl<CR>","install_details":"linux platform is ok,  it\\\\'s not tested under windows platform, maybe it can work correctly. \r\n\r\n1. copy djangojump.vim to ~\/.vim\/plugin\/ folder \r\n2. open vim at django project root folder, then you can use these commands \r\n\r\nnote: this plugin need python2.6+ support","5":"linux platform is ok,  it\\\\'s not tested under windows platform, maybe it can work correctly. \r\n\r\n1. copy djangojump.vim to ~\/.vim\/plugin\/ folder \r\n2. open vim at django project root folder, then you can use these commands \r\n\r\nnote: this plugin need python2.6+ support","first_name":"hello","6":"hello","last_name":"world","7":"world","releases":[{"0":"4257","vim_version":"7.2","1":"7.2","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"vim-djangojump.zip","4":"vim-djangojump.zip","src_id":"18752","5":"18752","creation_date":"1349519158","6":"1349519158"}]},"4256":{"script_id":"4256","0":"4256","script_name":"ozzy.vim","1":"ozzy.vim","script_type":"utility","2":"utility","summary":"Database-driven file search","3":"Database-driven file search","description":"\r\nDatabase-driven file search. Ozzy does not perform a runtime file search. \r\nInstead, it keeps track of all files you open over time into an external database,\r\nso that you can open them regardless your current working directory. \r\nThe only thing you are required to do in order to open a certain file is to edit it at least once.\r\n\r\n\r\nCommands\r\n------------------------------------------------------------------------------------------\r\n\r\nOzzy\r\n\r\nThis is the most important command. Use this command and a small window will \r\npopup at the bottom of the Vim window with a special command line. Start typing \r\nthe file you want to open and you'll see the list updating as you type. Below there\r\nis list of all the mappings you can use to interact with the window:\r\n\r\n  * UP, TAB, CTRL+K: move up in the list.\r\n\r\n  * DOWN, CTRL+J: move down in the list.\r\n\r\n  * RETURN, CTRL+O, CTRL+E: open the selected file.\r\n\r\n  * ESC, CTRL+C: close the list.\r\n\r\n  * CTRL+D: delete the selected file (it won't show up anymore in the list until\r\n                     you'll edit that file again).\r\n\r\n  * CTRL+U: clear the current search.\r\n\r\n\r\nOzzyReset\r\n\r\nTo remove all tracked files from the database.\r\n\r\n\r\nCalculator on the fly\r\n------------------------------------------------------------------------------------------\r\n\r\nOzzy integrates a tiny calculator. Just type some arithmetic expressions in the \r\ncommand line and you'll see the result. The expressions must follow the `python` \r\nnotation, so you'll have to use the `**` operator in order to compute the power of a \r\nnumber. All functions from the python `math` module are also available.\r\n","4":"\r\nDatabase-driven file search. Ozzy does not perform a runtime file search. \r\nInstead, it keeps track of all files you open over time into an external database,\r\nso that you can open them regardless your current working directory. \r\nThe only thing you are required to do in order to open a certain file is to edit it at least once.\r\n\r\n\r\nCommands\r\n------------------------------------------------------------------------------------------\r\n\r\nOzzy\r\n\r\nThis is the most important command. Use this command and a small window will \r\npopup at the bottom of the Vim window with a special command line. Start typing \r\nthe file you want to open and you'll see the list updating as you type. Below there\r\nis list of all the mappings you can use to interact with the window:\r\n\r\n  * UP, TAB, CTRL+K: move up in the list.\r\n\r\n  * DOWN, CTRL+J: move down in the list.\r\n\r\n  * RETURN, CTRL+O, CTRL+E: open the selected file.\r\n\r\n  * ESC, CTRL+C: close the list.\r\n\r\n  * CTRL+D: delete the selected file (it won't show up anymore in the list until\r\n                     you'll edit that file again).\r\n\r\n  * CTRL+U: clear the current search.\r\n\r\n\r\nOzzyReset\r\n\r\nTo remove all tracked files from the database.\r\n\r\n\r\nCalculator on the fly\r\n------------------------------------------------------------------------------------------\r\n\r\nOzzy integrates a tiny calculator. Just type some arithmetic expressions in the \r\ncommand line and you'll see the result. The expressions must follow the `python` \r\nnotation, so you'll have to use the `**` operator in order to compute the power of a \r\nnumber. All functions from the python `math` module are also available.\r\n","install_details":"\r\nInstall with your favorite plugin manager.\r\n\r\nRequires Python 2.6+","5":"\r\nInstall with your favorite plugin manager.\r\n\r\nRequires Python 2.6+","first_name":"geck","6":"geck","last_name":" ","7":" ","releases":[{"0":"4256","vim_version":"7.3","1":"7.3","script_version":"3.3","2":"3.3","version_comment":"- Minor changes in the matching process. Now it's hopefully a little more intelligent.\r\n- Improve vim settings management in the launcher window.\r\n- Add new setting 'g:ozzy_show_file_names'.\r\n- Fix: the size of opened windows is no more affected by the opening of the launcher.\r\n- Fix: issues with characters such as '%' and quotes.\r\n- Fix: the launcher now gets closed correctly with Ctrl+C.\r\n- Fix: issues with file names containing white spaces.","3":"- Minor changes in the matching process. Now it's hopefully a little more intelligent.\r\n- Improve vim settings management in the launcher window.\r\n- Add new setting 'g:ozzy_show_file_names'.\r\n- Fix: the size of opened windows is no more affected by the opening of the launcher.\r\n- Fix: issues with characters such as '%' and quotes.\r\n- Fix: the launcher now gets closed correctly with Ctrl+C.\r\n- Fix: issues with file names containing white spaces.","package":"ozzy-3.3.zip","4":"ozzy-3.3.zip","src_id":"20422","5":"20422","creation_date":"1372113448","6":"1372113448"}]},"4255":{"script_id":"4255","0":"4255","script_name":"xqmarklogic","1":"xqmarklogic","script_type":"ftplugin","2":"ftplugin","summary":"vim file type plugin to run an xquery against a MarkLogic server","3":"vim file type plugin to run an xquery against a MarkLogic server","description":"Vim filetype plugin enables you to run xquery files against a MarkLogic server, it displays the results in a separate window.\r\n\r\nSource: https:\/\/github.com\/coledarr\/vim-xqmarklogic\r\n\r\nRequirements\r\n\r\nvim (obviously), MarkLogic (probably obvious), and curl (not so obvious)\r\nAny recent vintage vim should work.\r\nMarkLogic6 works, but probably both older and newer versions will as well.\r\ncurl needs to be available on the local machine\r\n\r\n","4":"Vim filetype plugin enables you to run xquery files against a MarkLogic server, it displays the results in a separate window.\r\n\r\nSource: https:\/\/github.com\/coledarr\/vim-xqmarklogic\r\n\r\nRequirements\r\n\r\nvim (obviously), MarkLogic (probably obvious), and curl (not so obvious)\r\nAny recent vintage vim should work.\r\nMarkLogic6 works, but probably both older and newer versions will as well.\r\ncurl needs to be available on the local machine\r\n\r\n","install_details":"Works with pathogen.vim, should work with vundle, or other similar plugin managers\r\n\r\nManual Installation\r\n\r\n    1.  copy vim-xqmarklogic\/ftplugin\/xquery.vim to ~\/.vim\/ftplugin (or ~\\vimfiles\\ftplugin)\r\n    2. copy vim-xqmarklogic\/doc\/xqmarklogic.txt to ~\/.vim\/ftplugin (or ~\\vimfiles\\ftplugin)\r\n    3. In vim run:\r\n          :helptags\r\n          :help xqmarklogic-config-marklogic\r\n     This will provide the details to setup MarkLogic server side of the plugin.\r\n","5":"Works with pathogen.vim, should work with vundle, or other similar plugin managers\r\n\r\nManual Installation\r\n\r\n    1.  copy vim-xqmarklogic\/ftplugin\/xquery.vim to ~\/.vim\/ftplugin (or ~\\vimfiles\\ftplugin)\r\n    2. copy vim-xqmarklogic\/doc\/xqmarklogic.txt to ~\/.vim\/ftplugin (or ~\\vimfiles\\ftplugin)\r\n    3. In vim run:\r\n          :helptags\r\n          :help xqmarklogic-config-marklogic\r\n     This will provide the details to setup MarkLogic server side of the plugin.\r\n","first_name":"Darren","6":"Darren","last_name":"Cole","7":"Cole","releases":[{"0":"4255","vim_version":"7.0","1":"7.0","script_version":"1.1.1","2":"1.1.1","version_comment":"Minor improvement to :XQexploreDb output","3":"Minor improvement to :XQexploreDb output","package":"xqmarklogic.zip","4":"xqmarklogic.zip","src_id":"20659","5":"20659","creation_date":"1376580084","6":"1376580084"},{"0":"4255","vim_version":"7.0","1":"7.0","script_version":"1.1.0","2":"1.1.0","version_comment":"Add explicit LICENSE file, better quotes (works in csh now). Version bump because I changed XQsetPassword to now prompt for password (wont take an argument anymore).  Add XQsetDefaultPassword to set a default password (not just a buffer specific password).  Also prompt on when query is executed if none is set, and then uses that password for later queries.","3":"Add explicit LICENSE file, better quotes (works in csh now). Version bump because I changed XQsetPassword to now prompt for password (wont take an argument anymore).  Add XQsetDefaultPassword to set a default password (not just a buffer specific password).  Also prompt on when query is executed if none is set, and then uses that password for later queries.","package":"xqmarklogic.zip","4":"xqmarklogic.zip","src_id":"19079","5":"19079","creation_date":"1354439115","6":"1354439115"},{"0":"4255","vim_version":"7.0","1":"7.0","script_version":"1.0.7","2":"1.0.7","version_comment":"Add settings to customize mappings\r\nAdd mappings to results window\r\nUpdate docs","3":"Add settings to customize mappings\r\nAdd mappings to results window\r\nUpdate docs","package":"xqmarklogic.zip","4":"xqmarklogic.zip","src_id":"18875","5":"18875","creation_date":"1351110990","6":"1351110990"},{"0":"4255","vim_version":"7.0","1":"7.0","script_version":"1.0.5","2":"1.0.5","version_comment":"Skip indenting results if over 400 lines\r\nWarn if xquery buffer has changed but was not saved\r\nAdd XQexploreDb command and Mapping\r\n    List documents in database with some extra info\r\n    (somewhat like \"Explore\" button in Query Console)","3":"Skip indenting results if over 400 lines\r\nWarn if xquery buffer has changed but was not saved\r\nAdd XQexploreDb command and Mapping\r\n    List documents in database with some extra info\r\n    (somewhat like \"Explore\" button in Query Console)","package":"xqmarklogic.zip","4":"xqmarklogic.zip","src_id":"18861","5":"18861","creation_date":"1350937200","6":"1350937200"},{"0":"4255","vim_version":"7.0","1":"7.0","script_version":"1.0.2","2":"1.0.2","version_comment":"Can turn off setting mappings.\r\nCan turn on or off showing in query of: curl command, query duration, database used.\r\nCan turn off query cleanup\r\nUpdate helpfile","3":"Can turn off setting mappings.\r\nCan turn on or off showing in query of: curl command, query duration, database used.\r\nCan turn off query cleanup\r\nUpdate helpfile","package":"xqmarklogic.zip","4":"xqmarklogic.zip","src_id":"18773","5":"18773","creation_date":"1349894974","6":"1349894974"},{"0":"4255","vim_version":"7.0","1":"7.0","script_version":"1.0.0","2":"1.0.0","version_comment":"Initial upload","3":"Initial upload","package":"xqmarklogic.zip","4":"xqmarklogic.zip","src_id":"18748","5":"18748","creation_date":"1349382984","6":"1349382984"}]},"4254":{"script_id":"4254","0":"4254","script_name":"plsql.vim","1":"plsql.vim","script_type":"syntax","2":"syntax","summary":"Syntax for Oracle PL\/SQL language with folding feature","3":"Syntax for Oracle PL\/SQL language with folding feature","description":"Based on the standard syntax file for plsql.vim.\r\n\r\nNew features ( comparing to the standard plsql.vim, contained in Vim 7.3):\r\n\r\n   1) Now you can use multilined literal strings. The string\r\n'A\r\nB\r\nC\r\n'   will be highlighted properly.\r\n\r\n\r\n   1) folding feature for procedures and functions ( including internal procedures and functions)\r\nfor a simple example, the procedure \"testProcedure\" with comments will be folded: \r\n\r\ndeclare\r\n\r\n  \/*\r\n    Test procedure;    \r\n  *\/\r\n  procedure testProcedure\r\n  is\r\n  begin\r\n    null;\r\n  end testProcedure;\r\n  \r\nbegin\r\n  testProcedure();\r\nend;\r\n\r\n","4":"Based on the standard syntax file for plsql.vim.\r\n\r\nNew features ( comparing to the standard plsql.vim, contained in Vim 7.3):\r\n\r\n   1) Now you can use multilined literal strings. The string\r\n'A\r\nB\r\nC\r\n'   will be highlighted properly.\r\n\r\n\r\n   1) folding feature for procedures and functions ( including internal procedures and functions)\r\nfor a simple example, the procedure \"testProcedure\" with comments will be folded: \r\n\r\ndeclare\r\n\r\n  \/*\r\n    Test procedure;    \r\n  *\/\r\n  procedure testProcedure\r\n  is\r\n  begin\r\n    null;\r\n  end testProcedure;\r\n  \r\nbegin\r\n  testProcedure();\r\nend;\r\n\r\n","install_details":"Put it into syntax directory. Execute :set foldmethod=syntax ( can do it in your .vimrc)","5":"Put it into syntax directory. Execute :set foldmethod=syntax ( can do it in your .vimrc)","first_name":"Eugene","6":"Eugene","last_name":"Lysyonok","7":"Lysyonok","releases":[{"0":"4254","vim_version":"7.3","1":"7.3","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"plsql.vim","4":"plsql.vim","src_id":"18747","5":"18747","creation_date":"1349358025","6":"1349358025"}]},"4253":{"script_id":"4253","0":"4253","script_name":"TagManager","1":"TagManager","script_type":"utility","2":"utility","summary":"Project aware incremental tags manager","3":"Project aware incremental tags manager","description":"Beware: this is a wrapping script over plugin TagHighlight. Hopefully its functionality will eventually appear in TagHighlight.\r\n\r\nThis plugin is capable of managing both tag jumps and highlights databases simultaneously for different projects. It consists of two standalone applications BuildTags and MakeVimHlTags and this file. To manage tag highlights it uses excellent plugin TagHighlight (http:\/\/www.vim.org\/scripts\/script.php?script_id=2646) as backend. The plugin also needs exuberant ctags and (optionally) cscope packages.\r\n\r\nTagManager can manage both jumps and highlights tags incrementally, it means that projects may depend on other projects and user can setup his projects in such a way that he would need to update only small pieces of tags databases related to changes he would have made for a small project: all not changed dependencies would not be rebuilt and would be attached to the small projects as is. For example user can manage a small project my_proj which depends on large 3rd-party libraries libLarge1 and libLarge2 that he would definitely never change (we denote this sort of dependency as my_proj:libLarge1,libLarge2), then when he decide to update the tags of the project my_proj, tags from libLarge1 and libLarge2 will be attached to those from my_proj not having been rebuilt.\r\n\r\nThe plugin provides 3 commands:\r\n\r\n    UpdateProjectJumps\r\n    UpdateProjectHighlights\r\n    UpdateProjectTags\r\n\r\nNormally you will need only UpdateProjectTags which is a simple sequence of the first two. Issuing :UpdateProjectTags will update both jumps and highlights tags in the project you are currently in.\r\n\r\nTo use the plugin efficiently add following lines in your .vimrc:\r\n\r\n    if !exists('g:TagHighlightSettings')\r\n        let g:TagHighlightSettings = {}\r\n    endif\r\n    let g:TagHighlightSettings['LanguageDetectionMethods'] =\r\n                                            \\ ['Extension', 'FileType']\r\n    let g:TagHighlightSettings['FileTypeLanguageOverrides'] =\r\n                                            \\ {'svn': 'c', 'tagbar': 'c'}\r\n    let g:loaded_TagHighlight = 2\r\n\r\nSetting variable g:TagHighlightSettings['FileTypeLanguageOverrides'] will let you enjoy tag highlights in tagbar window and when committed svn changes. Line 'let g:loaded_TagHighlight = 2' will prevent loading of TagHighlight before TagManager thus letting the latter to manage initialization of the former itself. This is important because TagManager depends on TagHighlight plugin and autocommands from TagManager must go before corresponding autocommands from TagHighlight. Value 2 will make TagManager aware that variable g:loaded_TagHighlight was only initialized in .vimrc and TagHighlight is really not loaded yet.\r\n\r\nYou also may want to put scripts BuildTags and MakeVimHlTags in some directory listed in your $PATH environment variable (by default this plugin expects to find them in $HOME\/bin\/), and create new environment variable $TAGSDIR where all plugin data will be saved. Now you can additionally use BuildTags and MakeVimHlTags as standalone scripts and create tags for vim directly from command line. To see available command-line options run the scripts with option --help.\r\n\r\nBy default plugin reads configuration file $HOME\/.vim-TagManager.conf where a user defines settings for building and updating tags for his projects. Each line in the configuration file corresponds to one project and consists of 5 columns, separated with double semicolon (possibly surrounded by spaces or tabs). The first column is a directory match pattern used to define where the project resides, second column - name of the project with optionally appended (after colon) comma-separated list of other projects upon which this project depends, third column - language for building tag highlights (for example 'c' or 'python'), if user do not want to specify any language (i.e. highlights tags will be built for any languages that TagHighlight supports) then he can put in this column special placeholder - exclamation sign (!) which denotes empty value, fourth column - root directory for building jumps and highlights tags, fifth column - options for MakeVimHlTags, to see them run\r\n\r\n    MakeVimHlTags --help\r\n\r\nin command line. Please make sure that you understand the difference between values in column 1 and column 4: the former will be used in autocommands for finding out if specific directory matches project directory pattern and thus may contain glob symbols like '*' or '?', whereas the latter denotes the root directory for building tags. Values in any column may refer to environment variables: they will be expanded. An example of configuration file is shipped with this distribution.","4":"Beware: this is a wrapping script over plugin TagHighlight. Hopefully its functionality will eventually appear in TagHighlight.\r\n\r\nThis plugin is capable of managing both tag jumps and highlights databases simultaneously for different projects. It consists of two standalone applications BuildTags and MakeVimHlTags and this file. To manage tag highlights it uses excellent plugin TagHighlight (http:\/\/www.vim.org\/scripts\/script.php?script_id=2646) as backend. The plugin also needs exuberant ctags and (optionally) cscope packages.\r\n\r\nTagManager can manage both jumps and highlights tags incrementally, it means that projects may depend on other projects and user can setup his projects in such a way that he would need to update only small pieces of tags databases related to changes he would have made for a small project: all not changed dependencies would not be rebuilt and would be attached to the small projects as is. For example user can manage a small project my_proj which depends on large 3rd-party libraries libLarge1 and libLarge2 that he would definitely never change (we denote this sort of dependency as my_proj:libLarge1,libLarge2), then when he decide to update the tags of the project my_proj, tags from libLarge1 and libLarge2 will be attached to those from my_proj not having been rebuilt.\r\n\r\nThe plugin provides 3 commands:\r\n\r\n    UpdateProjectJumps\r\n    UpdateProjectHighlights\r\n    UpdateProjectTags\r\n\r\nNormally you will need only UpdateProjectTags which is a simple sequence of the first two. Issuing :UpdateProjectTags will update both jumps and highlights tags in the project you are currently in.\r\n\r\nTo use the plugin efficiently add following lines in your .vimrc:\r\n\r\n    if !exists('g:TagHighlightSettings')\r\n        let g:TagHighlightSettings = {}\r\n    endif\r\n    let g:TagHighlightSettings['LanguageDetectionMethods'] =\r\n                                            \\ ['Extension', 'FileType']\r\n    let g:TagHighlightSettings['FileTypeLanguageOverrides'] =\r\n                                            \\ {'svn': 'c', 'tagbar': 'c'}\r\n    let g:loaded_TagHighlight = 2\r\n\r\nSetting variable g:TagHighlightSettings['FileTypeLanguageOverrides'] will let you enjoy tag highlights in tagbar window and when committed svn changes. Line 'let g:loaded_TagHighlight = 2' will prevent loading of TagHighlight before TagManager thus letting the latter to manage initialization of the former itself. This is important because TagManager depends on TagHighlight plugin and autocommands from TagManager must go before corresponding autocommands from TagHighlight. Value 2 will make TagManager aware that variable g:loaded_TagHighlight was only initialized in .vimrc and TagHighlight is really not loaded yet.\r\n\r\nYou also may want to put scripts BuildTags and MakeVimHlTags in some directory listed in your $PATH environment variable (by default this plugin expects to find them in $HOME\/bin\/), and create new environment variable $TAGSDIR where all plugin data will be saved. Now you can additionally use BuildTags and MakeVimHlTags as standalone scripts and create tags for vim directly from command line. To see available command-line options run the scripts with option --help.\r\n\r\nBy default plugin reads configuration file $HOME\/.vim-TagManager.conf where a user defines settings for building and updating tags for his projects. Each line in the configuration file corresponds to one project and consists of 5 columns, separated with double semicolon (possibly surrounded by spaces or tabs). The first column is a directory match pattern used to define where the project resides, second column - name of the project with optionally appended (after colon) comma-separated list of other projects upon which this project depends, third column - language for building tag highlights (for example 'c' or 'python'), if user do not want to specify any language (i.e. highlights tags will be built for any languages that TagHighlight supports) then he can put in this column special placeholder - exclamation sign (!) which denotes empty value, fourth column - root directory for building jumps and highlights tags, fifth column - options for MakeVimHlTags, to see them run\r\n\r\n    MakeVimHlTags --help\r\n\r\nin command line. Please make sure that you understand the difference between values in column 1 and column 4: the former will be used in autocommands for finding out if specific directory matches project directory pattern and thus may contain glob symbols like '*' or '?', whereas the latter denotes the root directory for building tags. Values in any column may refer to environment variables: they will be expanded. An example of configuration file is shipped with this distribution.","install_details":"Prerequisites: sh, perl, ctags, cscope (optionally), vim script TagHighlight (http:\/\/www.vim.org\/scripts\/script.php?script_id=2646)\r\n\r\n1. Extract the tarball in your $HOME\/.vim directory\r\n2. Copy or move scripts BuildTags and MakeVimHlTags from directory TagManager\/ in some directory referred in the $PATH. By default TagManager expects to find them in $HOME\/bin\/, but if you prefer another path then assign corresponding values (path + script name) to variables g:TagMgrTagsBuilder and g:TagMgrHighlightsBuilder in your .vimrc\r\n3. Define directory where TagManager will store tags databases. This is made by assigning either vim global variable g:TagMgrTagsdir in .vimrc or (preferred) environment variable $TAGSDIR\r\n4. If you prefer highlights in the tagbar (http:\/\/www.vim.org\/scripts\/script.php?script_id=3465) or when you edit messages for subversion commits then add following lines in your .vimrc:\r\n\r\n   if !exists('g:TagHighlightSettings')\r\n       let g:TagHighlightSettings = {}\r\n   endif\r\n   let g:TagHighlightSettings['LanguageDetectionMethods'] =\r\n                                           \\ ['Extension', 'FileType']\r\n   let g:TagHighlightSettings['FileTypeLanguageOverrides'] =\r\n                                           \\ {'svn': 'c', 'tagbar': 'c'}\r\n   let g:loaded_TagHighlight = 2\r\n\r\n5. Create configuration file for your projects (default path is $HOME\/.vim-TagManager.conf but it can be changed via variable g:TagMgrDataFile). An example is given in file TagManager\/vim-TagManager.conf.sample)","5":"Prerequisites: sh, perl, ctags, cscope (optionally), vim script TagHighlight (http:\/\/www.vim.org\/scripts\/script.php?script_id=2646)\r\n\r\n1. Extract the tarball in your $HOME\/.vim directory\r\n2. Copy or move scripts BuildTags and MakeVimHlTags from directory TagManager\/ in some directory referred in the $PATH. By default TagManager expects to find them in $HOME\/bin\/, but if you prefer another path then assign corresponding values (path + script name) to variables g:TagMgrTagsBuilder and g:TagMgrHighlightsBuilder in your .vimrc\r\n3. Define directory where TagManager will store tags databases. This is made by assigning either vim global variable g:TagMgrTagsdir in .vimrc or (preferred) environment variable $TAGSDIR\r\n4. If you prefer highlights in the tagbar (http:\/\/www.vim.org\/scripts\/script.php?script_id=3465) or when you edit messages for subversion commits then add following lines in your .vimrc:\r\n\r\n   if !exists('g:TagHighlightSettings')\r\n       let g:TagHighlightSettings = {}\r\n   endif\r\n   let g:TagHighlightSettings['LanguageDetectionMethods'] =\r\n                                           \\ ['Extension', 'FileType']\r\n   let g:TagHighlightSettings['FileTypeLanguageOverrides'] =\r\n                                           \\ {'svn': 'c', 'tagbar': 'c'}\r\n   let g:loaded_TagHighlight = 2\r\n\r\n5. Create configuration file for your projects (default path is $HOME\/.vim-TagManager.conf but it can be changed via variable g:TagMgrDataFile). An example is given in file TagManager\/vim-TagManager.conf.sample)","first_name":"Alexey","6":"Alexey","last_name":"Radkov","7":"Radkov","releases":[{"0":"4253","vim_version":"7.0","1":"7.0","script_version":"0.2","2":"0.2","version_comment":"runtime TagManager in .vimrc is not needed any more; minor internal improvements","3":"runtime TagManager in .vimrc is not needed any more; minor internal improvements","package":"TagManager-0.2.tgz","4":"TagManager-0.2.tgz","src_id":"20285","5":"20285","creation_date":"1370369042","6":"1370369042"},{"0":"4253","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"TagManager-0.1.tgz","4":"TagManager-0.1.tgz","src_id":"18743","5":"18743","creation_date":"1349250767","6":"1349250767"}]},"4252":{"script_id":"4252","0":"4252","script_name":"easytree.vim","1":"easytree.vim","script_type":"utility","2":"utility","summary":"easytree.vim - is a simple tree file manager for vim","3":"easytree.vim - is a simple tree file manager for vim","description":"easytree.vim - is a simple tree file manager for vim. While being highly inspired by NERDTree \r\nit differs from it in it's approach to a file management and takes a more traditional vim yank\/paste file copy\/paste\/delete \r\napproach It's also more simpler in it's functionality and has much less features compared to other file managers. \r\nIt's goal is to be as fast and as minimalistic as possible. Just the right tool for just the right task\r\n\r\nhttps:\/\/github.com\/troydm\/easytree.vim","4":"easytree.vim - is a simple tree file manager for vim. While being highly inspired by NERDTree \r\nit differs from it in it's approach to a file management and takes a more traditional vim yank\/paste file copy\/paste\/delete \r\napproach It's also more simpler in it's functionality and has much less features compared to other file managers. \r\nIt's goal is to be as fast and as minimalistic as possible. Just the right tool for just the right task\r\n\r\nhttps:\/\/github.com\/troydm\/easytree.vim","install_details":"","5":"","first_name":"Dmitry","6":"Dmitry","last_name":"Geurkov","7":"Geurkov","releases":[{"0":"4252","vim_version":"7.3","1":"7.3","script_version":"0.2.1","2":"0.2.1","version_comment":"added tree settings save\/load methods\r\nadded ignore file\/dir\/find results change methods\r\nsome minor bugs fixed","3":"added tree settings save\/load methods\r\nadded ignore file\/dir\/find results change methods\r\nsome minor bugs fixed","package":"easytree.vim-0.2.1.zip","4":"easytree.vim-0.2.1.zip","src_id":"19350","5":"19350","creation_date":"1357911665","6":"1357911665"},{"0":"4252","vim_version":"7.0","1":"7.0","script_version":"0.2","2":"0.2","version_comment":"many bug fixes","3":"many bug fixes","package":"easytree.vim-0.2.zip","4":"easytree.vim-0.2.zip","src_id":"18839","5":"18839","creation_date":"1350653447","6":"1350653447"},{"0":"4252","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"easytree.vim-0.1.zip","4":"easytree.vim-0.1.zip","src_id":"18734","5":"18734","creation_date":"1349177332","6":"1349177332"}]},"4251":{"script_id":"4251","0":"4251","script_name":"GuessIndent","1":"GuessIndent","script_type":"utility","2":"utility","summary":"Indentation guessing plugin","3":"Indentation guessing plugin","description":"GuessIndent Plugin\r\n------------------\r\n\r\nThis plugin is based on the DetectIndent plugin by Ciaran McCreesh.\r\nMany thanks to him for inspiration and code.\r\n\r\nSource code and development is at https:\/\/github.com\/ogier\/guessindent\r\n\r\nUsage:\r\n------\r\n\r\n    :GuessIndent\r\n\r\nThe :GuessIndent command tries to determine whether the active file\r\nuses tabs or spaces for indentation as a convention. If the file\r\nappers to use spaces for indentation, the plugin will try to\r\nintelligently set the 'shiftwidth' and 'softtabstop' options.\r\n\r\nYou can run this command automatically every time a file is loaded.\r\nTo do that, include the following in your ~\/.vimrc file:\r\n\r\n    autocmd BufReadPost * :GuessIndent\r\n\r\nCustomizing:\r\n------------\r\n\r\nIf at least 3\/4 of the lines in the active file appear to use spaces\r\nfor indentation, then 'expandtab' will be set. If at least 3\/4 of\r\nthe lines in the active file use tabs for indentation, 'noexpandtab'\r\nwill be set. If no tabs or spaces are used (for example if the file\r\nis new) then the command does nothing. If there is a roughly even mix\r\nthen the file is considered to be ambiguous.\r\n\r\nIf the file sometimes uses spaces and sometimes uses tabs for\r\nindentation ambiguously, spaces are arbitrarily chosen as the\r\nindentation method and 'expandtab' is set. If you prefer to use\r\ntabs in this case and set 'noexpandtab', include the following\r\nin your ~\/.vimrc file:\r\n\r\n    let g:guessindent_prefer_tabs = 1\r\n\r\nFor performance reasons, :GuessIndent reads a limited number of\r\nlines from the active file. The default is currently to read a\r\nmaximum of 1024 lines. To change this maximum, include the\r\nfollowing in your ~\/.vimrc file:\r\n\r\n    let g:guessindent_max_lines_to_analyse = 2048\r\n\r\nLicense\r\n-------\r\n\r\nThis plugin is distributed under the same terms as vim istelf.\r\nContributions are welcome.","4":"GuessIndent Plugin\r\n------------------\r\n\r\nThis plugin is based on the DetectIndent plugin by Ciaran McCreesh.\r\nMany thanks to him for inspiration and code.\r\n\r\nSource code and development is at https:\/\/github.com\/ogier\/guessindent\r\n\r\nUsage:\r\n------\r\n\r\n    :GuessIndent\r\n\r\nThe :GuessIndent command tries to determine whether the active file\r\nuses tabs or spaces for indentation as a convention. If the file\r\nappers to use spaces for indentation, the plugin will try to\r\nintelligently set the 'shiftwidth' and 'softtabstop' options.\r\n\r\nYou can run this command automatically every time a file is loaded.\r\nTo do that, include the following in your ~\/.vimrc file:\r\n\r\n    autocmd BufReadPost * :GuessIndent\r\n\r\nCustomizing:\r\n------------\r\n\r\nIf at least 3\/4 of the lines in the active file appear to use spaces\r\nfor indentation, then 'expandtab' will be set. If at least 3\/4 of\r\nthe lines in the active file use tabs for indentation, 'noexpandtab'\r\nwill be set. If no tabs or spaces are used (for example if the file\r\nis new) then the command does nothing. If there is a roughly even mix\r\nthen the file is considered to be ambiguous.\r\n\r\nIf the file sometimes uses spaces and sometimes uses tabs for\r\nindentation ambiguously, spaces are arbitrarily chosen as the\r\nindentation method and 'expandtab' is set. If you prefer to use\r\ntabs in this case and set 'noexpandtab', include the following\r\nin your ~\/.vimrc file:\r\n\r\n    let g:guessindent_prefer_tabs = 1\r\n\r\nFor performance reasons, :GuessIndent reads a limited number of\r\nlines from the active file. The default is currently to read a\r\nmaximum of 1024 lines. To change this maximum, include the\r\nfollowing in your ~\/.vimrc file:\r\n\r\n    let g:guessindent_max_lines_to_analyse = 2048\r\n\r\nLicense\r\n-------\r\n\r\nThis plugin is distributed under the same terms as vim istelf.\r\nContributions are welcome.","install_details":"Unzip and install to ~\/.vim\/plugin and ~\/.vim\/doc. You may need to run :Helptags before you can see the documentation with :help GuessIndent.","5":"Unzip and install to ~\/.vim\/plugin and ~\/.vim\/doc. You may need to run :Helptags before you can see the documentation with :help GuessIndent.","first_name":"Alex","6":"Alex","last_name":"Ogier","7":"Ogier","releases":[{"0":"4251","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"guessindent-1.0.zip","4":"guessindent-1.0.zip","src_id":"18733","5":"18733","creation_date":"1349135108","6":"1349135108"}]},"4250":{"script_id":"4250","0":"4250","script_name":"CommandAlias","1":"CommandAlias","script_type":"utility","2":"utility","summary":"Make aliases to vim command","3":"Make aliases to vim command","description":"Description\r\n===========\r\n\r\nNote: the interface has changed slightly: buflocal aliases added. To redefine\r\ndefault range add it to the cmd rather than to the alias (this seems to be\r\nmore intuitive).\r\n\r\n\r\nThis plugin implements aliases for command names, without vim restriction:\r\nuser defined commands via :command must begin with a capital letter. Using\r\nthis plugin you make an alias to a command where the alias, is any sequence.\r\nYou can also register a default range or count with the alias. In this way\r\nyou can change the default range or count of vim commands.\r\nTo define alias use the command: \r\n```viml\r\n:CmdAlias [alias] [range][command] [history] [buflocal] [match_end] \r\n```\r\nwhere `[alias]` is the alias name, `[command]` is the command that should be\r\nexecuted. You might pretend new default `[range]` or count to the command. The\r\n`[alias]` is any vim pattern that will be used to match what you are entering in\r\nthe `:` command line (the pattern will have pretended `\\C^` and appended `\\\\>` -\r\nthe later one unless [match_end] is specified and equal `0`). For\r\ncommands which do not run external programs you can also set `[history]=1`\r\n(default is `0`), then the command history will remember what you have typped\r\nrather than what was executed. But usage of it is limited, for example you can\r\nuse with commands that echo some output because it will be hidden by next call\r\nto `histdel()` vim function. If `[buflocal]` has true value (`1` for example)\r\nthen the alias will be only valid in the current buffer (it will be denotes\r\nwith @ when listing the aliases as Vim does for maps).\r\n\r\n\r\nNote: If you define `[match_end] = 0` you might fall into troubles, simply\r\nbecause the plugin might substitute part of a command name.  So don't use\r\nit unless you really want to experiment - you've been warned ;).\r\n\r\n\r\nIf you don't provide any argument to the `:CmdAlias` command it will list all\r\naliases.\r\n\r\n\r\nThe order in which you define aliases matters. More recent aliases are matched\r\nfirst. If you want to list the aliases in alphabetic order use:\r\n```viml\r\n:CmdAlias\r\n```\r\nIf you want to list them in the order they are tried:\r\n```viml\r\n:CmdAlias!\r\n```\r\nNote that\r\n```viml\r\n:CmdAlias {alias}\r\n```\r\nwill list all aliases which starts with {alias} but\r\n```viml\r\n:CmdAlias! {alias}\r\n```\r\nwill remove the {alias} (has to be equal to the registered alias).\r\n\r\n\r\nExamples: \r\n---------\r\n```viml\r\n:CmdAlias ali\\%[as] CmdAlias\r\n```\r\nNote: this alias would not work if we defined it with `[history]=1`.\r\n```viml\r\n:CmdAlias s %s\r\n```\r\nChange the default range of `:s` command from the current line to whole\r\nbuffer. Note that `:su` will act with vim default range (the current line).\r\n```viml\r\n:CmdAlias a\\%[ppend] Append \r\n```\r\ndefine alias to the user command Append which will overwrite the vim command\r\n:append. The  `\\%[...]` allows that if you type: 'a' or 'ap' or 'app', ...\r\nor 'append' then the Append command will be used (as with vim many commands)\r\n```viml\r\n:CmdAlias bc\\%[lose] BufClose\r\n``` \r\nYou will find the handy BufClose command in BufClose plugin by Christian\r\nRobinson.\r\n\r\nTip: to find if an alias is not coliding type ':\\<alias\\>\\<C-d\\>'.\r\nSee `:help c^D`.\r\n\r\n```viml\r\n:CmdAlias SP  1,\/\\\\\\\\begin{document}\/-1s\r\n```\r\nThe :SP command will substitute in the LaTeX preambule (which starts in the\r\nfirst line and ends before `\\begin{document}`). Note that the Vim pattern to\r\nfind `\\begin...` is `\\\\begin...` and each backslash needs to be escaped onece\r\nmore. Thus we have four slashes (like in *Python* :).\r\n\r\n\r\nVIMRC\r\n-----\r\n\r\nTo configure aliases on startup you have to add the following lines to your\r\nvimrc file:\r\n```viml\r\naugroup VIMRC_aliases\r\n    au!\r\n    au VimEnter * CmdAlias ...\r\n    ...\r\naugroup END\r\n```\r\n\r\nOther Commands and Maps:\r\n------------------------\r\n\r\n```viml\r\n:CmdAliasToggle \r\n```\r\ntoggles on\/of the aliases. Since the plugin remaps \\<CR\\> in the command line\r\nthis just deletes\/sets up the \\<CR\\> map.  When you want to type a function:\r\n```viml\r\n:fun! X()\r\n```\r\nThe plugin also defines \\<C-M\\> map to \\<CR\\> which doesn't trigger\r\naliasing mechanism. So you can type ':fun! X()\\<C-M\\>' on the command line.\r\n```viml\r\n:CmdAlias! {alias} \r\n```\r\nremoves {alias}, this command has a nice completion.\r\n\r\nNote: If you have installed my [system plugin](http:\/\/www.vim.org\/scripts\/script.php?script_id=4224)\r\nyou need to update it to version 3 (otherwise you will get an error).\r\n\r\nThere is another [plugin](http:\/\/www.vim.org\/scripts\/script.php?script_id=746)\r\nwith the same functionality, but different implementation and thus a different\r\nlimitations.  It uses cabbreviations.  The problem with them is that it is\r\nmore difficult to get the command bang working (what was the purpose of\r\nimplementing this plugin). The range and the count probably could be\r\nimplemented using the same range parser used by this plugin. The advantage of\r\nthe cabbreviations approach is that after hitting the ' ' you get the real\r\ncommand together with its completion.  Implementing completion for aliases\r\nwithin this approach would be quite tedious.\r\n\r\nThe aliasing works also when joining commands on the command line with \"|\",\r\nfor example with a dummy alias:\r\n```viml\r\n  Alias S %s\r\n```  \r\nyou can run:\r\n```viml\r\n:S\/aaa\/yyy\/|S\/bbb\/xxx\r\n```\r\nNote: the first command has to end with \/ (to use |, this is a vim\r\nrequirement.)\r\n\r\nNote: using the expression register: you need Vim 7.3.686. There is also:\r\n```viml\r\n cnoremap <C-M> <CR>\r\n```\r\nIt will not trigger aliases, any way it might be a good idea to have such\r\na map in case you want to avoid aliases.\r\n\r\nIf you want to debug define a list\r\n```viml\r\n let g:cmd_alias_debug = []\r\n``` \r\nand for all calls an entry to this list will be appended.\r\n(except command lines which matches `cmd_alias_debug` since we don't want to\r\nrecord accessing to this variable)\r\n\r\n\r\nIdeas for aliases:\r\n```viml\r\nCmdAlias h\\%[elp] top\\ help   \" very useful if you use 'splitbelow', but you want help to split above\r\nCmdAlias re reg\\ \"0-*+\/ 1\r\nCmdAlias rn reg\\ 123456789 1\r\nCmdAlias ra reg abcdefghijklmnopqrstuwxyz 1\r\nCmdAlias bc\\%[close] BufClose\r\n```\r\nFor the last alias one you need the\r\n[BufClose](http:\/\/www.vim.org\/scripts\/script.php?script_id=559) plugin.\r\n\r\n\r\nAuthor: Marcin Szamotulski\r\nEmail: mszamot [AT] gmail [DOT] com\r\nCopyright: \u00c2\u00a9 Marcin Szamotulski, 2012-2014\r\nLicense: vim-license, see `:help license`\r\n","4":"Description\r\n===========\r\n\r\nNote: the interface has changed slightly: buflocal aliases added. To redefine\r\ndefault range add it to the cmd rather than to the alias (this seems to be\r\nmore intuitive).\r\n\r\n\r\nThis plugin implements aliases for command names, without vim restriction:\r\nuser defined commands via :command must begin with a capital letter. Using\r\nthis plugin you make an alias to a command where the alias, is any sequence.\r\nYou can also register a default range or count with the alias. In this way\r\nyou can change the default range or count of vim commands.\r\nTo define alias use the command: \r\n```viml\r\n:CmdAlias [alias] [range][command] [history] [buflocal] [match_end] \r\n```\r\nwhere `[alias]` is the alias name, `[command]` is the command that should be\r\nexecuted. You might pretend new default `[range]` or count to the command. The\r\n`[alias]` is any vim pattern that will be used to match what you are entering in\r\nthe `:` command line (the pattern will have pretended `\\C^` and appended `\\\\>` -\r\nthe later one unless [match_end] is specified and equal `0`). For\r\ncommands which do not run external programs you can also set `[history]=1`\r\n(default is `0`), then the command history will remember what you have typped\r\nrather than what was executed. But usage of it is limited, for example you can\r\nuse with commands that echo some output because it will be hidden by next call\r\nto `histdel()` vim function. If `[buflocal]` has true value (`1` for example)\r\nthen the alias will be only valid in the current buffer (it will be denotes\r\nwith @ when listing the aliases as Vim does for maps).\r\n\r\n\r\nNote: If you define `[match_end] = 0` you might fall into troubles, simply\r\nbecause the plugin might substitute part of a command name.  So don't use\r\nit unless you really want to experiment - you've been warned ;).\r\n\r\n\r\nIf you don't provide any argument to the `:CmdAlias` command it will list all\r\naliases.\r\n\r\n\r\nThe order in which you define aliases matters. More recent aliases are matched\r\nfirst. If you want to list the aliases in alphabetic order use:\r\n```viml\r\n:CmdAlias\r\n```\r\nIf you want to list them in the order they are tried:\r\n```viml\r\n:CmdAlias!\r\n```\r\nNote that\r\n```viml\r\n:CmdAlias {alias}\r\n```\r\nwill list all aliases which starts with {alias} but\r\n```viml\r\n:CmdAlias! {alias}\r\n```\r\nwill remove the {alias} (has to be equal to the registered alias).\r\n\r\n\r\nExamples: \r\n---------\r\n```viml\r\n:CmdAlias ali\\%[as] CmdAlias\r\n```\r\nNote: this alias would not work if we defined it with `[history]=1`.\r\n```viml\r\n:CmdAlias s %s\r\n```\r\nChange the default range of `:s` command from the current line to whole\r\nbuffer. Note that `:su` will act with vim default range (the current line).\r\n```viml\r\n:CmdAlias a\\%[ppend] Append \r\n```\r\ndefine alias to the user command Append which will overwrite the vim command\r\n:append. The  `\\%[...]` allows that if you type: 'a' or 'ap' or 'app', ...\r\nor 'append' then the Append command will be used (as with vim many commands)\r\n```viml\r\n:CmdAlias bc\\%[lose] BufClose\r\n``` \r\nYou will find the handy BufClose command in BufClose plugin by Christian\r\nRobinson.\r\n\r\nTip: to find if an alias is not coliding type ':\\<alias\\>\\<C-d\\>'.\r\nSee `:help c^D`.\r\n\r\n```viml\r\n:CmdAlias SP  1,\/\\\\\\\\begin{document}\/-1s\r\n```\r\nThe :SP command will substitute in the LaTeX preambule (which starts in the\r\nfirst line and ends before `\\begin{document}`). Note that the Vim pattern to\r\nfind `\\begin...` is `\\\\begin...` and each backslash needs to be escaped onece\r\nmore. Thus we have four slashes (like in *Python* :).\r\n\r\n\r\nVIMRC\r\n-----\r\n\r\nTo configure aliases on startup you have to add the following lines to your\r\nvimrc file:\r\n```viml\r\naugroup VIMRC_aliases\r\n    au!\r\n    au VimEnter * CmdAlias ...\r\n    ...\r\naugroup END\r\n```\r\n\r\nOther Commands and Maps:\r\n------------------------\r\n\r\n```viml\r\n:CmdAliasToggle \r\n```\r\ntoggles on\/of the aliases. Since the plugin remaps \\<CR\\> in the command line\r\nthis just deletes\/sets up the \\<CR\\> map.  When you want to type a function:\r\n```viml\r\n:fun! X()\r\n```\r\nThe plugin also defines \\<C-M\\> map to \\<CR\\> which doesn't trigger\r\naliasing mechanism. So you can type ':fun! X()\\<C-M\\>' on the command line.\r\n```viml\r\n:CmdAlias! {alias} \r\n```\r\nremoves {alias}, this command has a nice completion.\r\n\r\nNote: If you have installed my [system plugin](http:\/\/www.vim.org\/scripts\/script.php?script_id=4224)\r\nyou need to update it to version 3 (otherwise you will get an error).\r\n\r\nThere is another [plugin](http:\/\/www.vim.org\/scripts\/script.php?script_id=746)\r\nwith the same functionality, but different implementation and thus a different\r\nlimitations.  It uses cabbreviations.  The problem with them is that it is\r\nmore difficult to get the command bang working (what was the purpose of\r\nimplementing this plugin). The range and the count probably could be\r\nimplemented using the same range parser used by this plugin. The advantage of\r\nthe cabbreviations approach is that after hitting the ' ' you get the real\r\ncommand together with its completion.  Implementing completion for aliases\r\nwithin this approach would be quite tedious.\r\n\r\nThe aliasing works also when joining commands on the command line with \"|\",\r\nfor example with a dummy alias:\r\n```viml\r\n  Alias S %s\r\n```  \r\nyou can run:\r\n```viml\r\n:S\/aaa\/yyy\/|S\/bbb\/xxx\r\n```\r\nNote: the first command has to end with \/ (to use |, this is a vim\r\nrequirement.)\r\n\r\nNote: using the expression register: you need Vim 7.3.686. There is also:\r\n```viml\r\n cnoremap <C-M> <CR>\r\n```\r\nIt will not trigger aliases, any way it might be a good idea to have such\r\na map in case you want to avoid aliases.\r\n\r\nIf you want to debug define a list\r\n```viml\r\n let g:cmd_alias_debug = []\r\n``` \r\nand for all calls an entry to this list will be appended.\r\n(except command lines which matches `cmd_alias_debug` since we don't want to\r\nrecord accessing to this variable)\r\n\r\n\r\nIdeas for aliases:\r\n```viml\r\nCmdAlias h\\%[elp] top\\ help   \" very useful if you use 'splitbelow', but you want help to split above\r\nCmdAlias re reg\\ \"0-*+\/ 1\r\nCmdAlias rn reg\\ 123456789 1\r\nCmdAlias ra reg abcdefghijklmnopqrstuwxyz 1\r\nCmdAlias bc\\%[close] BufClose\r\n```\r\nFor the last alias one you need the\r\n[BufClose](http:\/\/www.vim.org\/scripts\/script.php?script_id=559) plugin.\r\n\r\n\r\nAuthor: Marcin Szamotulski\r\nEmail: mszamot [AT] gmail [DOT] com\r\nCopyright: \u00c2\u00a9 Marcin Szamotulski, 2012-2014\r\nLicense: vim-license, see `:help license`\r\n","install_details":"Install http:\/\/www.vim.org\/scripts\/script.php?script_id=4856 and then open the vimball archive in vim and source it with :so% .","5":"Install http:\/\/www.vim.org\/scripts\/script.php?script_id=4856 and then open the vimball archive in vim and source it with :so% .","first_name":"Marcin","6":"Marcin","last_name":"Szamotulski","7":"Szamotulski","releases":[{"0":"4250","vim_version":"7.3","1":"7.3","script_version":"4","2":"4","version_comment":"New version.  Also install: http:\/\/www.vim.org\/scripts\/script.php?script_id=4856 .","3":"New version.  Also install: http:\/\/www.vim.org\/scripts\/script.php?script_id=4856 .","package":"cmdalias.vmb","4":"cmdalias.vmb","src_id":"21442","5":"21442","creation_date":"1391766673","6":"1391766673"},{"0":"4250","vim_version":"7.3","1":"7.3","script_version":"3","2":"3","version_comment":"Update to make it work with my new plugin Enchanted Vim (persistent very magic option) http:\/\/www.vim.org\/scripts\/script.php?script_id=4849","3":"Update to make it work with my new plugin Enchanted Vim (persistent very magic option) http:\/\/www.vim.org\/scripts\/script.php?script_id=4849","package":"cmd_alias.vim","4":"cmd_alias.vim","src_id":"21418","5":"21418","creation_date":"1391347336","6":"1391347336"},{"0":"4250","vim_version":"7.3","1":"7.3","script_version":"2","2":"2","version_comment":"Note: the interface has changed slightly (in version 2): buflocal aliases\r\nadded. To redefine default range add it to the cmd rather than to the alias\r\n(this seems to be more intuitive).\r\n","3":"Note: the interface has changed slightly (in version 2): buflocal aliases\r\nadded. To redefine default range add it to the cmd rather than to the alias\r\n(this seems to be more intuitive).\r\n","package":"cmd_alias.vim","4":"cmd_alias.vim","src_id":"18742","5":"18742","creation_date":"1349249142","6":"1349249142"},{"0":"4250","vim_version":"7.0","1":"7.0","script_version":"1","2":"1","version_comment":"Initial upload","3":"Initial upload","package":"cmd_alias.vim","4":"cmd_alias.vim","src_id":"18732","5":"18732","creation_date":"1349121382","6":"1349121382"}]},"4249":{"script_id":"4249","0":"4249","script_name":"write.vim","1":"write.vim","script_type":"utility","2":"utility","summary":"Get your author on.","3":"Get your author on.","description":"Adds utilities to write non-code text, such as articles\/novels\/journal entries\/etc.\r\n\r\nIncludes the :WriteOn, :WriteOff, and :Write commands (the last which toggles writer mode).\r\n\r\nIn writer mode the cursor moves screen-wise instead of line-wise. Line numbers are turned off and spell is turned on. Numerous other tweaks are included.","4":"Adds utilities to write non-code text, such as articles\/novels\/journal entries\/etc.\r\n\r\nIncludes the :WriteOn, :WriteOff, and :Write commands (the last which toggles writer mode).\r\n\r\nIn writer mode the cursor moves screen-wise instead of line-wise. Line numbers are turned off and spell is turned on. Numerous other tweaks are included.","install_details":"Install write.vim into plugin\/ and write.txt into doc\/, or just use vundle and install from http:\/\/github.com\/Soares\/write.vim.","5":"Install write.vim into plugin\/ and write.txt into doc\/, or just use vundle and install from http:\/\/github.com\/Soares\/write.vim.","first_name":"Nathaniel","6":"Nathaniel","last_name":"Soares","7":"Soares","releases":[{"0":"4249","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"write.zip","4":"write.zip","src_id":"18727","5":"18727","creation_date":"1349104092","6":"1349104092"}]},"4248":{"script_id":"4248","0":"4248","script_name":"PatternComplete","1":"PatternComplete","script_type":"utility","2":"utility","summary":"Insert mode completion for matches of queried \/ last search pattern.","3":"Insert mode completion for matches of queried \/ last search pattern.","description":"DESCRIPTION\r\nThis plugin offers completions that either use the last search pattern or\r\nquery for a regular expression, and then offer all matches for completion.\r\n\r\nWithout this plugin, you can just directly insert the contents of the last\r\nsearch pattern register via CTRL-R \/, but the register can contain \\<word\\>\r\nboundary characters from a star search or other non-literal regexp atoms\r\nlike \\V, .*, etc., which you usually don't want inserted into the text.\r\n\r\nSEE ALSO\r\n- Check out the CompleteHelper.vim plugin page (vimscript #3914) for a full\r\n  list of insert mode completions powered by it.\r\n\r\nUSAGE\r\nCTRL-X \/                Use a \"\/\"-delimited (g:PatternComplete_DelimitersPattern)\r\n                        \/{pattern}\/ base before the cursor, or (if no such\r\n                        base) first query for {pattern} (press <Enter> to\r\n                        conclude), and find matches for {pattern}.\r\n{Visual}CTRL-X \/        The completion finds matches for the selected pattern.\r\n\r\nCTRL-X *                Use a \"\/\"-delimited \/{pattern}\/ base before the\r\n                        cursor, or first query for {pattern} (press <Enter>\r\n                        to conclude), and find matches for \\<{pattern}\\>, or\r\n                        {pattern} surrounded by whitespace as a fallback.\r\n\r\n{Visual}CTRL-X *        Find whole word (or whole WORD as a fallback) matches\r\n                        for the selected pattern.\r\n\r\nCTRL-X &                Find matches for the last search pattern, quote\/.\r\n\r\nCTRL-R &                Insert first match for the last search pattern\r\n                        quote\/ into the command-line.\r\n\r\nCTRL-X ?                Find matches, reusing the {pattern} from the last\r\n                        pattern completion.","4":"DESCRIPTION\r\nThis plugin offers completions that either use the last search pattern or\r\nquery for a regular expression, and then offer all matches for completion.\r\n\r\nWithout this plugin, you can just directly insert the contents of the last\r\nsearch pattern register via CTRL-R \/, but the register can contain \\<word\\>\r\nboundary characters from a star search or other non-literal regexp atoms\r\nlike \\V, .*, etc., which you usually don't want inserted into the text.\r\n\r\nSEE ALSO\r\n- Check out the CompleteHelper.vim plugin page (vimscript #3914) for a full\r\n  list of insert mode completions powered by it.\r\n\r\nUSAGE\r\nCTRL-X \/                Use a \"\/\"-delimited (g:PatternComplete_DelimitersPattern)\r\n                        \/{pattern}\/ base before the cursor, or (if no such\r\n                        base) first query for {pattern} (press <Enter> to\r\n                        conclude), and find matches for {pattern}.\r\n{Visual}CTRL-X \/        The completion finds matches for the selected pattern.\r\n\r\nCTRL-X *                Use a \"\/\"-delimited \/{pattern}\/ base before the\r\n                        cursor, or first query for {pattern} (press <Enter>\r\n                        to conclude), and find matches for \\<{pattern}\\>, or\r\n                        {pattern} surrounded by whitespace as a fallback.\r\n\r\n{Visual}CTRL-X *        Find whole word (or whole WORD as a fallback) matches\r\n                        for the selected pattern.\r\n\r\nCTRL-X &                Find matches for the last search pattern, quote\/.\r\n\r\nCTRL-R &                Insert first match for the last search pattern\r\n                        quote\/ into the command-line.\r\n\r\nCTRL-X ?                Find matches, reusing the {pattern} from the last\r\n                        pattern completion.","install_details":"INSTALLATION\r\nThe code is hosted in a Git repo at\r\n    https:\/\/github.com\/inkarkat\/vim-PatternComplete\r\nYou can use your favorite plugin manager, or \"git clone\" into a directory used\r\nfor Vim packages. Releases are on the \"stable\" branch, the latest unstable\r\ndevelopment snapshot on \"master\".\r\n\r\nThis script is also packaged as a vimball. If you have the \"gunzip\"\r\ndecompressor in your PATH, simply edit the *.vmb.gz package in Vim; otherwise,\r\ndecompress the archive first, e.g. using WinZip. Inside Vim, install by\r\nsourcing the vimball or via the :UseVimball command.\r\n    vim PatternComplete*.vmb.gz\r\n    :so %\r\nTo uninstall, use the :RmVimball command.\r\n\r\nDEPENDENCIES\r\n- Requires Vim 7.0 or higher.\r\n- Requires the ingo-library.vim plugin (vimscript #4433), version 1.011 or\r\n  higher.\r\n- Requires the CompleteHelper.vim plugin (vimscript #3914), version 1.50 or\r\n  higher.\r\n\r\nCONFIGURATION\r\nFor a permanent configuration, put the following commands into your vimrc:\r\n\r\nBy default, the 'complete' option controls which buffers will be scanned for\r\ncompletion candidates. You can override that either for the entire plugin, or\r\nonly for particular buffers; see CompleteHelper_complete for supported\r\nvalues.\r\n    let g:PatternComplete_complete = '.,w,b,u'\r\n\r\nThe possible regular expression delimiters for a \/{pattern}\/ base before the\r\ncursor (for i_CTRL-X_\/ and i_CTRL-X_star) can be configured as a pattern:\r\n    let g:PatternComplete_DelimitersPattern = '[\/?#@]'\r\n\r\nIf you want to use different mappings, map your keys to the\r\n<Plug>(PatternComplete) mapping targets _before_ sourcing the script (e.g.\r\nin your vimrc):\r\n    imap <C-x>\/ <Plug>(PatternCompleteInput)\r\n    imap <C-x>* <Plug>(PatternCompleteWordInput)\r\n    vmap <C-x>\/ <Plug>(PatternCompleteInput)\r\n    vmap <C-x>* <Plug>(PatternCompleteWordInput)\r\n    imap <C-x>& <Plug>(PatternCompleteSearch)\r\n    cmap <C-r>& <Plug>(PatternCompleteSearchMatch)\r\n    imap <C-x>? <Plug>(PatternCompleteLast)\r\n","5":"INSTALLATION\r\nThe code is hosted in a Git repo at\r\n    https:\/\/github.com\/inkarkat\/vim-PatternComplete\r\nYou can use your favorite plugin manager, or \"git clone\" into a directory used\r\nfor Vim packages. Releases are on the \"stable\" branch, the latest unstable\r\ndevelopment snapshot on \"master\".\r\n\r\nThis script is also packaged as a vimball. If you have the \"gunzip\"\r\ndecompressor in your PATH, simply edit the *.vmb.gz package in Vim; otherwise,\r\ndecompress the archive first, e.g. using WinZip. Inside Vim, install by\r\nsourcing the vimball or via the :UseVimball command.\r\n    vim PatternComplete*.vmb.gz\r\n    :so %\r\nTo uninstall, use the :RmVimball command.\r\n\r\nDEPENDENCIES\r\n- Requires Vim 7.0 or higher.\r\n- Requires the ingo-library.vim plugin (vimscript #4433), version 1.011 or\r\n  higher.\r\n- Requires the CompleteHelper.vim plugin (vimscript #3914), version 1.50 or\r\n  higher.\r\n\r\nCONFIGURATION\r\nFor a permanent configuration, put the following commands into your vimrc:\r\n\r\nBy default, the 'complete' option controls which buffers will be scanned for\r\ncompletion candidates. You can override that either for the entire plugin, or\r\nonly for particular buffers; see CompleteHelper_complete for supported\r\nvalues.\r\n    let g:PatternComplete_complete = '.,w,b,u'\r\n\r\nThe possible regular expression delimiters for a \/{pattern}\/ base before the\r\ncursor (for i_CTRL-X_\/ and i_CTRL-X_star) can be configured as a pattern:\r\n    let g:PatternComplete_DelimitersPattern = '[\/?#@]'\r\n\r\nIf you want to use different mappings, map your keys to the\r\n<Plug>(PatternComplete) mapping targets _before_ sourcing the script (e.g.\r\nin your vimrc):\r\n    imap <C-x>\/ <Plug>(PatternCompleteInput)\r\n    imap <C-x>* <Plug>(PatternCompleteWordInput)\r\n    vmap <C-x>\/ <Plug>(PatternCompleteInput)\r\n    vmap <C-x>* <Plug>(PatternCompleteWordInput)\r\n    imap <C-x>& <Plug>(PatternCompleteSearch)\r\n    cmap <C-r>& <Plug>(PatternCompleteSearchMatch)\r\n    imap <C-x>? <Plug>(PatternCompleteLast)\r\n","first_name":"Ingo","6":"Ingo","last_name":"Karkat","7":"Karkat","releases":[{"0":"4248","vim_version":"7.0","1":"7.0","script_version":"1.10","2":"1.10","version_comment":"- ENH: Add <C-x>? mapping to reuse last search pattern.\r\n- ENH: Also support visual mode variants for <C-x>\/ and <C-x>*.\r\n- ENH: Also handle \/{pattern}\/ base before cursor; this is often quicker and more comfortable to enter (using register contents, other completions, etc.) than the explicit user query that has been the only possibility so far.","3":"- ENH: Add <C-x>? mapping to reuse last search pattern.\r\n- ENH: Also support visual mode variants for <C-x>\/ and <C-x>*.\r\n- ENH: Also handle \/{pattern}\/ base before cursor; this is often quicker and more comfortable to enter (using register contents, other completions, etc.) than the explicit user query that has been the only possibility so far.","package":"PatternComplete-1.10.vmb.gz","4":"PatternComplete-1.10.vmb.gz","src_id":"25565","5":"25565","creation_date":"1505557245","6":"1505557245"},{"0":"4248","vim_version":"7.0","1":"7.0","script_version":"1.02","2":"1.02","version_comment":"- Use a:options.abbreviate instead of explicit abbreviation loop. *** You need to update to CompleteHelper.vim (vimscript #3914) version 1.50! ***\r\n- Remove default g:PatternComplete_complete configuration and default to 'complete' option value instead.\r\n- Use more functions from the ingo-library. *** You need to update to ingo-library (vimscript #4433) version 1.011! ***","3":"- Use a:options.abbreviate instead of explicit abbreviation loop. *** You need to update to CompleteHelper.vim (vimscript #3914) version 1.50! ***\r\n- Remove default g:PatternComplete_complete configuration and default to 'complete' option value instead.\r\n- Use more functions from the ingo-library. *** You need to update to ingo-library (vimscript #4433) version 1.011! ***","package":"PatternComplete-1.02.vmb.gz","4":"PatternComplete-1.02.vmb.gz","src_id":"24210","5":"24210","creation_date":"1461833695","6":"1461833695"},{"0":"4248","vim_version":"7.0","1":"7.0","script_version":"1.01","2":"1.01","version_comment":"- DWIM: Remove the \\<...\\> enclosure when the last used search pattern is a whole word search (that just has no matches now).\r\n- Add dependency to ingo-library (vimscript #4433).","3":"- DWIM: Remove the \\<...\\> enclosure when the last used search pattern is a whole word search (that just has no matches now).\r\n- Add dependency to ingo-library (vimscript #4433).","package":"PatternComplete-1.01.vmb.gz","4":"PatternComplete-1.01.vmb.gz","src_id":"20527","5":"20527","creation_date":"1373896248","6":"1373896248"},{"0":"4248","vim_version":"7.0","1":"7.0","script_version":"1.00","2":"1.00","version_comment":"Initial upload","3":"Initial upload","package":"PatternComplete-1.00.vmb.gz","4":"PatternComplete-1.00.vmb.gz","src_id":"18725","5":"18725","creation_date":"1349078321","6":"1349078321"}]},"4247":{"script_id":"4247","0":"4247","script_name":"tabdiff","1":"tabdiff","script_type":"utility","2":"utility","summary":"A different way to diff.","3":"A different way to diff.","description":"Calling :TabDiff will open each pair of buffers in a vertically split tab and in diff mode. Now you can\r\n\r\nvim -c \"silent :TabDiff\" a A b B c C\r\n\r\nTo diff a bunch of files at once in different tabs.","4":"Calling :TabDiff will open each pair of buffers in a vertically split tab and in diff mode. Now you can\r\n\r\nvim -c \"silent :TabDiff\" a A b B c C\r\n\r\nTo diff a bunch of files at once in different tabs.","install_details":"Install tabdiff.vim into plugin\/ and tabdiff.txt into doc\/ or just use a bundle manager and install from github.com\/Soares\/tabdiff.vim.","5":"Install tabdiff.vim into plugin\/ and tabdiff.txt into doc\/ or just use a bundle manager and install from github.com\/Soares\/tabdiff.vim.","first_name":"Nathaniel","6":"Nathaniel","last_name":"Soares","7":"Soares","releases":[{"0":"4247","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"tabdiff.zip","4":"tabdiff.zip","src_id":"18721","5":"18721","creation_date":"1349022106","6":"1349022106"}]},"4246":{"script_id":"4246","0":"4246","script_name":"longline.vim","1":"longline.vim","script_type":"utility","2":"utility","summary":"Avoid long lines.","3":"Avoid long lines.","description":"longline#Show() highlights lines that are too long.\r\nlongline#Hide() unhighlights them.\r\nlongline#Toggle() does what you might expect.\r\nlongline#Exists() tells you whether there is a line in the file that is too long and is useful for statusline warnings.\r\n\r\nthe :LongLines command calls longline#Toggle()\r\n\r\nYou may configure how long is too long either globally or by file type.","4":"longline#Show() highlights lines that are too long.\r\nlongline#Hide() unhighlights them.\r\nlongline#Toggle() does what you might expect.\r\nlongline#Exists() tells you whether there is a line in the file that is too long and is useful for statusline warnings.\r\n\r\nthe :LongLines command calls longline#Toggle()\r\n\r\nYou may configure how long is too long either globally or by file type.","install_details":"Install longline.vim into plugin\/ and longline.txt into doc\/, or just use vundle with github.com\/Soares\/longline.vim.","5":"Install longline.vim into plugin\/ and longline.txt into doc\/, or just use vundle with github.com\/Soares\/longline.vim.","first_name":"Nathaniel","6":"Nathaniel","last_name":"Soares","7":"Soares","releases":[{"0":"4246","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"longline.zip","4":"longline.zip","src_id":"18720","5":"18720","creation_date":"1349021920","6":"1349021920"}]},"4245":{"script_id":"4245","0":"4245","script_name":"butane.vim","1":"butane.vim","script_type":"utility","2":"utility","summary":"Light up your buffers.","3":"Light up your buffers.","description":"Adds the :Bclose command, which closes a buffer without re-arranging the windows.","4":"Adds the :Bclose command, which closes a buffer without re-arranging the windows.","install_details":"Install butane.vim into your plugins\/ directory and butane.txt into your doc\/ directory.\r\n\r\nAlternatively, use vundle to install directly from github: https:\/\/github.com\/Soares\/butane.vim","5":"Install butane.vim into your plugins\/ directory and butane.txt into your doc\/ directory.\r\n\r\nAlternatively, use vundle to install directly from github: https:\/\/github.com\/Soares\/butane.vim","first_name":"Nathaniel","6":"Nathaniel","last_name":"Soares","7":"Soares","releases":[{"0":"4245","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"butane.zip","4":"butane.zip","src_id":"18719","5":"18719","creation_date":"1349021294","6":"1349021294"}]},"4244":{"script_id":"4244","0":"4244","script_name":"yacom","1":"yacom","script_type":"utility","2":"utility","summary":"easily toggle comments in line(s)","3":"easily toggle comments in line(s)","description":"(Y)et (A)nother (COM)ment is a vim commenting plugin with an extremely minimalist approach. It has only one keybind (default `<leader>c`) to toggle the comment (i.e. comment if not commented, uncomment otherwise) the current line (normal mode) or the selected line(s) (visual mode).\r\n\r\nSee https:\/\/github.com\/gokcehan\/vim-yacom for more information.","4":"(Y)et (A)nother (COM)ment is a vim commenting plugin with an extremely minimalist approach. It has only one keybind (default `<leader>c`) to toggle the comment (i.e. comment if not commented, uncomment otherwise) the current line (normal mode) or the selected line(s) (visual mode).\r\n\r\nSee https:\/\/github.com\/gokcehan\/vim-yacom for more information.","install_details":"Get the latest version from https:\/\/github.com\/gokcehan\/vim-yacom","5":"Get the latest version from https:\/\/github.com\/gokcehan\/vim-yacom","first_name":"gokcehan","6":"gokcehan","last_name":"kara","7":"kara","releases":[{"0":"4244","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"yacom.vim","4":"yacom.vim","src_id":"18717","5":"18717","creation_date":"1348939333","6":"1348939333"}]},"4243":{"script_id":"4243","0":"4243","script_name":"IndentTab","1":"IndentTab","script_type":"utility","2":"utility","summary":"Use tabs for indent at the beginning, spaces for alignment in the rest of a line","3":"Use tabs for indent at the beginning, spaces for alignment in the rest of a line","description":"DESCRIPTION\r\nThis plugin allows you to use your normal tab settings ('tabstop',\r\n'smarttabstop', 'expandtab') for the beginning of the line (up to the first\r\nnon-whitespace character), and have <Tab> expanded to the appropriate number\r\nof spaces (i.e. like :set expandtab) anywhere else. This effectively\r\ndistinguishes \"indenting\" from \"alignment\"; the characters inserted by <Tab>\r\ndepend on the local context.\r\n\r\nHOW IT WORKS\r\nThis plugin overrides the default behavior of the <Tab> and <BS> keys in\r\ninsert mode.\r\n\r\nRELATED WORKS\r\n- ctab.vim (vimscript #231) by Michael Geddes exists since 2002. It also\r\n  offers global and buffer-local mappings, but uses a slightly different\r\n  approach, does not handle comment[prefixes], instead has some\r\n  filetype-specific stuff. It also remaps <CR>, o and O, and additionally\r\n  offers a :RetabIndent command.\r\n- http:\/\/vim.wikia.com\/wiki\/Converting_tabs_to_spaces\r\n\r\nUSAGE\r\nThe indent tab can be en-\/disabled globally or only for a particular buffer.\r\n    call IndentTab#Set( isTurnOn, isGlobal )\r\nYou probably want to define your own mappings \/ commands for that, or do this\r\nfor certain filetypes only.\r\n\r\n<Tab>                   Uses normal tab settings at the beginning of the line\r\n                        (before the first non-whitespace character), and\r\n                        inserts spaces otherwise.\r\n<BS>                    Uses normal tab settings to delete tabs at the\r\n                        beginning of the line; elsewhere it also removes\r\n                        \"space-expanded\" tabs as if 'softtabstop' were\r\n                        enabled.\r\n                        The exact circumstances under which the normal tab\r\n                        settings apply are configured by the\r\n                        g:IndentTab_scopes setting.","4":"DESCRIPTION\r\nThis plugin allows you to use your normal tab settings ('tabstop',\r\n'smarttabstop', 'expandtab') for the beginning of the line (up to the first\r\nnon-whitespace character), and have <Tab> expanded to the appropriate number\r\nof spaces (i.e. like :set expandtab) anywhere else. This effectively\r\ndistinguishes \"indenting\" from \"alignment\"; the characters inserted by <Tab>\r\ndepend on the local context.\r\n\r\nHOW IT WORKS\r\nThis plugin overrides the default behavior of the <Tab> and <BS> keys in\r\ninsert mode.\r\n\r\nRELATED WORKS\r\n- ctab.vim (vimscript #231) by Michael Geddes exists since 2002. It also\r\n  offers global and buffer-local mappings, but uses a slightly different\r\n  approach, does not handle comment[prefixes], instead has some\r\n  filetype-specific stuff. It also remaps <CR>, o and O, and additionally\r\n  offers a :RetabIndent command.\r\n- http:\/\/vim.wikia.com\/wiki\/Converting_tabs_to_spaces\r\n\r\nUSAGE\r\nThe indent tab can be en-\/disabled globally or only for a particular buffer.\r\n    call IndentTab#Set( isTurnOn, isGlobal )\r\nYou probably want to define your own mappings \/ commands for that, or do this\r\nfor certain filetypes only.\r\n\r\n<Tab>                   Uses normal tab settings at the beginning of the line\r\n                        (before the first non-whitespace character), and\r\n                        inserts spaces otherwise.\r\n<BS>                    Uses normal tab settings to delete tabs at the\r\n                        beginning of the line; elsewhere it also removes\r\n                        \"space-expanded\" tabs as if 'softtabstop' were\r\n                        enabled.\r\n                        The exact circumstances under which the normal tab\r\n                        settings apply are configured by the\r\n                        g:IndentTab_scopes setting.","install_details":"INSTALLATION\r\nThis script is packaged as a vimball. If you have the \"gunzip\" decompressor\r\nin your PATH, simply edit the *.vmb.gz package in Vim; otherwise, decompress\r\nthe archive first, e.g. using WinZip. Inside Vim, install by sourcing the\r\nvimball or via the :UseVimball command.\r\n    vim IndentTab*.vmb.gz\r\n    :so %\r\nTo uninstall, use the :RmVimball command.\r\n\r\nDEPENDENCIES\r\n- Requires Vim 7.0 or higher.\r\n- Requires the ingo-library.vim plugin (vimscript #4433), version 1.005 or\r\n  higher.\r\n\r\nCONFIGURATION\r\nFor a permanent configuration, put the following commands into your vimrc:\r\n\r\nDetermine where the buffer's indent settings are applied. Elsewhere, spaces\r\nare used for alignment. Comma-separated list of the following values:\r\n    indent:         Initial whitespace at the beginning of a line.\r\n    commentprefix:  Initial whitespace after a comment prefix, in case the line\r\n                    begins with the comment prefix, not any indent.\r\n    comment:        Inside comments, as determined by syntax highlighting.\r\n    string:         Inside strings, as determined by syntax highlighting.\r\n    let g:IndentTab_scopes = 'indent,commentprefix,string'\r\n\r\nINTEGRATION\r\nTo determine whether the 'indenttab' setting is active in the current buffer,\r\nyou can call IndentTab#Info#IndentTab(), which yields a boolean value. This\r\ncan be used as a replacement for a hypothetical \":set indenttab?\", e.g. in a\r\ncustom 'statusline'.\r\n\r\nSUPERTAB INTEGRATION\r\nPlugins like SuperTab (vimscript #1643) overload the <Tab> key with\r\ninsert-mode completion and fall back to inserting a literal <Tab> character.\r\nThis is in conflict with this plugin's maps. To integrate, set\r\n    let g:IndentTab_IsSuperTab = 1\r\nThis avoids that IndentTab overrides the <Tab> mapping. Inside SuperTab,\r\ninstead of returning a literal <Tab>, you need to use the function\r\nIndentTab#SuperTabIntegration#GetExpr() instead. ","5":"INSTALLATION\r\nThis script is packaged as a vimball. If you have the \"gunzip\" decompressor\r\nin your PATH, simply edit the *.vmb.gz package in Vim; otherwise, decompress\r\nthe archive first, e.g. using WinZip. Inside Vim, install by sourcing the\r\nvimball or via the :UseVimball command.\r\n    vim IndentTab*.vmb.gz\r\n    :so %\r\nTo uninstall, use the :RmVimball command.\r\n\r\nDEPENDENCIES\r\n- Requires Vim 7.0 or higher.\r\n- Requires the ingo-library.vim plugin (vimscript #4433), version 1.005 or\r\n  higher.\r\n\r\nCONFIGURATION\r\nFor a permanent configuration, put the following commands into your vimrc:\r\n\r\nDetermine where the buffer's indent settings are applied. Elsewhere, spaces\r\nare used for alignment. Comma-separated list of the following values:\r\n    indent:         Initial whitespace at the beginning of a line.\r\n    commentprefix:  Initial whitespace after a comment prefix, in case the line\r\n                    begins with the comment prefix, not any indent.\r\n    comment:        Inside comments, as determined by syntax highlighting.\r\n    string:         Inside strings, as determined by syntax highlighting.\r\n    let g:IndentTab_scopes = 'indent,commentprefix,string'\r\n\r\nINTEGRATION\r\nTo determine whether the 'indenttab' setting is active in the current buffer,\r\nyou can call IndentTab#Info#IndentTab(), which yields a boolean value. This\r\ncan be used as a replacement for a hypothetical \":set indenttab?\", e.g. in a\r\ncustom 'statusline'.\r\n\r\nSUPERTAB INTEGRATION\r\nPlugins like SuperTab (vimscript #1643) overload the <Tab> key with\r\ninsert-mode completion and fall back to inserting a literal <Tab> character.\r\nThis is in conflict with this plugin's maps. To integrate, set\r\n    let g:IndentTab_IsSuperTab = 1\r\nThis avoids that IndentTab overrides the <Tab> mapping. Inside SuperTab,\r\ninstead of returning a literal <Tab>, you need to use the function\r\nIndentTab#SuperTabIntegration#GetExpr() instead. ","first_name":"Ingo","6":"Ingo","last_name":"Karkat","7":"Karkat","releases":[{"0":"4243","vim_version":"7.0","1":"7.0","script_version":"1.10","2":"1.10","version_comment":"- The scope tests that use syntax highlighting can be wrong when there's no separating whitespace. To properly detect the scope, we need to first insert whitespace, then perform the scope tests that use syntax highlighting.\r\n- FIX: In IndentTab#SuperTabIntegration#GetExpr(), prefer buffer-local setting over global one to correctly implement the precedence.\r\n- Add dependency to ingo-library (vimscript #4433).","3":"- The scope tests that use syntax highlighting can be wrong when there's no separating whitespace. To properly detect the scope, we need to first insert whitespace, then perform the scope tests that use syntax highlighting.\r\n- FIX: In IndentTab#SuperTabIntegration#GetExpr(), prefer buffer-local setting over global one to correctly implement the precedence.\r\n- Add dependency to ingo-library (vimscript #4433).","package":"IndentTab-1.10.vmb.gz","4":"IndentTab-1.10.vmb.gz","src_id":"20011","5":"20011","creation_date":"1367497875","6":"1367497875"},{"0":"4243","vim_version":"7.0","1":"7.0","script_version":"1.00","2":"1.00","version_comment":"Initial upload","3":"Initial upload","package":"IndentTab-1.00.vmb.gz","4":"IndentTab-1.00.vmb.gz","src_id":"18710","5":"18710","creation_date":"1348861212","6":"1348861212"}]},"4242":{"script_id":"4242","0":"4242","script_name":"SameFiletypeComplete","1":"SameFiletypeComplete","script_type":"utility","2":"utility","summary":"Insert mode completion from buffers with the same filetype.","3":"Insert mode completion from buffers with the same filetype.","description":"DESCRIPTION\r\nWhen editing multiple projects (e.g. Python and Java) concurrently, or even\r\nwhen different types of files (like C source code, its Makefile, and the\r\ncorresponding HTML documentation) are open in Vim, the general insert-mode\r\ncompletion i_CTRL-N becomes less useful. It searches for keywords in open\r\nwindows, listed buffers, and other sources as defined by the 'complete'\r\nsetting; there's no way to restrict the sources to consider only buffers that\r\nhave the same filetype as the current buffer, so a lot of unrelated cruft\r\nclutters the list of completion matches.\r\n\r\nThis plugin offers an alternative completion that works like the general one,\r\nbut lists completion candidates only from buffers that have the same\r\n'filetype' as the current buffer. When you're editing a Python file, you'll\r\nonly get matches from other open Python files. Switch to the Makefile and all\r\nthose inapplicable Python keywords won't be offered there.\r\n\r\nSOURCE\r\nThis completion type was motivated by this Stack Overflow question:\r\n    http:\/\/stackoverflow.com\/questions\/12610516\/can-vims-keyword-completion-be-limited-to-only-same-filetype\r\n\r\nSEE ALSO\r\n- Check out the CompleteHelper.vim plugin page (vimscript #3914) for a full\r\n  list of insert mode completions powered by it.\r\n\r\nUSAGE\r\nIn insert mode, invoke the completion via CTRL-X =\r\nYou can then search forward and backward via CTRL-N \/ CTRL-P, as usual.\r\n\r\nCTRL-X =                Find matches for words that start with the\r\n                        keyword in front of the cursor, looking only into\r\n                        buffers with the same 'filetype'.\r\n                        Further use of CTRL-X = will copy the words following\r\n                        the previous expansion.","4":"DESCRIPTION\r\nWhen editing multiple projects (e.g. Python and Java) concurrently, or even\r\nwhen different types of files (like C source code, its Makefile, and the\r\ncorresponding HTML documentation) are open in Vim, the general insert-mode\r\ncompletion i_CTRL-N becomes less useful. It searches for keywords in open\r\nwindows, listed buffers, and other sources as defined by the 'complete'\r\nsetting; there's no way to restrict the sources to consider only buffers that\r\nhave the same filetype as the current buffer, so a lot of unrelated cruft\r\nclutters the list of completion matches.\r\n\r\nThis plugin offers an alternative completion that works like the general one,\r\nbut lists completion candidates only from buffers that have the same\r\n'filetype' as the current buffer. When you're editing a Python file, you'll\r\nonly get matches from other open Python files. Switch to the Makefile and all\r\nthose inapplicable Python keywords won't be offered there.\r\n\r\nSOURCE\r\nThis completion type was motivated by this Stack Overflow question:\r\n    http:\/\/stackoverflow.com\/questions\/12610516\/can-vims-keyword-completion-be-limited-to-only-same-filetype\r\n\r\nSEE ALSO\r\n- Check out the CompleteHelper.vim plugin page (vimscript #3914) for a full\r\n  list of insert mode completions powered by it.\r\n\r\nUSAGE\r\nIn insert mode, invoke the completion via CTRL-X =\r\nYou can then search forward and backward via CTRL-N \/ CTRL-P, as usual.\r\n\r\nCTRL-X =                Find matches for words that start with the\r\n                        keyword in front of the cursor, looking only into\r\n                        buffers with the same 'filetype'.\r\n                        Further use of CTRL-X = will copy the words following\r\n                        the previous expansion.","install_details":"INSTALLATION\r\nThis script is packaged as a vimball. If you have the \"gunzip\" decompressor\r\nin your PATH, simply edit the *.vmb.gz package in Vim; otherwise, decompress\r\nthe archive first, e.g. using WinZip. Inside Vim, install by sourcing the\r\nvimball or via the :UseVimball command.\r\n    vim SameFiletypeComplete*.vmb.gz\r\n    :so %\r\nTo uninstall, use the :RmVimball command.\r\n\r\nDEPENDENCIES\r\n- Requires Vim 7.0 or higher.\r\n- Requires the CompleteHelper.vim plugin (vimscript #3914), version 1.30 or\r\n  higher.\r\n\r\nCONFIGURATION\r\nFor a permanent configuration, put the following commands into your vimrc:\r\n\r\nAnaloguous to the 'complete' option, you can specify which buffers will be\r\nscanned for completion candidates. Currently, '.' (current buffer), 'w'\r\n(buffers from other windows), and 'b' (other listed buffers) are supported.\r\n    let g:SameFiletypeComplete_complete = '.,w,b'\r\nThe global setting can be overridden for a particular buffer\r\n(b:SameFiletypeComplete_complete).\r\n\r\nIf you want to use a different mapping, map your keys to the\r\n<Plug>(SameFiletypeComplete) mapping target _before_ sourcing the script (e.g.\r\nin your vimrc):\r\n    imap <C-x>= <Plug>(SameFiletypeComplete)","5":"INSTALLATION\r\nThis script is packaged as a vimball. If you have the \"gunzip\" decompressor\r\nin your PATH, simply edit the *.vmb.gz package in Vim; otherwise, decompress\r\nthe archive first, e.g. using WinZip. Inside Vim, install by sourcing the\r\nvimball or via the :UseVimball command.\r\n    vim SameFiletypeComplete*.vmb.gz\r\n    :so %\r\nTo uninstall, use the :RmVimball command.\r\n\r\nDEPENDENCIES\r\n- Requires Vim 7.0 or higher.\r\n- Requires the CompleteHelper.vim plugin (vimscript #3914), version 1.30 or\r\n  higher.\r\n\r\nCONFIGURATION\r\nFor a permanent configuration, put the following commands into your vimrc:\r\n\r\nAnaloguous to the 'complete' option, you can specify which buffers will be\r\nscanned for completion candidates. Currently, '.' (current buffer), 'w'\r\n(buffers from other windows), and 'b' (other listed buffers) are supported.\r\n    let g:SameFiletypeComplete_complete = '.,w,b'\r\nThe global setting can be overridden for a particular buffer\r\n(b:SameFiletypeComplete_complete).\r\n\r\nIf you want to use a different mapping, map your keys to the\r\n<Plug>(SameFiletypeComplete) mapping target _before_ sourcing the script (e.g.\r\nin your vimrc):\r\n    imap <C-x>= <Plug>(SameFiletypeComplete)","first_name":"Ingo","6":"Ingo","last_name":"Karkat","7":"Karkat","releases":[{"0":"4242","vim_version":"7.0","1":"7.0","script_version":"1.00","2":"1.00","version_comment":"Initial upload","3":"Initial upload","package":"SameFiletypeComplete-1.00.vmb.gz","4":"SameFiletypeComplete-1.00.vmb.gz","src_id":"18702","5":"18702","creation_date":"1348754772","6":"1348754772"}]},"4241":{"script_id":"4241","0":"4241","script_name":"betterSearch.vim","1":"betterSearch.vim","script_type":"utility","2":"utility","summary":"Provide better search functionality by capturing all matched line","3":"Provide better search functionality by capturing all matched line","description":"This script will now only updated @ github\r\nYou may get it from \r\nhttps:\/\/github.com\/kenng\/vim-bettersearch\r\n\r\n** note: tested in Linux\/MS window environment using GVIM **\r\n** note: BetterSearchVisualSelect command is found working in Linux, but might not working in MS Window environment at the moment ** \r\n\r\nProblem: \r\nHaving a large file and you need to search for a few keywords from it? \r\nAnd wish that you can at once glance all the search result? \r\nBest with highlight on the keyword? \r\nAnd you would wish to jump to that particular line when you see something interesting?\r\nHere is a good news for you! : )\r\nSolution approach: works somewhat similarly to notepad++ search function\r\n\r\nFeatures offered by betterSearch: \r\n- This script is written to copy all the search result and put it to window above the content. \r\n- If the line number is switch on, the search result is 'jumpable' to the content window by just enter on that particular search line\r\n- Search term highlight can be switched on and off\r\n- Search keyword can be saved to clipboard\r\n\r\nThere are a few way to use the function of this script.\r\n[ usage 1 ]  \r\nUser intended to type in the search words\r\n:BetterSearchPromptOn\r\nthen <ENTER>. \r\nA window will pop up for user input. \r\nThe user input can consists of more than one search term. For example: search_A|search_B|search_C...\r\n\r\n[ usage 2 ] \r\nUser intended to use the word under the cursor as the search term\r\n:BetterSearchPromptOn    \r\nthen <ENTER>. and press <ENTER> again when the user input dialog box appear without type in any word\r\n\r\n[ usage 3 ] \r\nUser intended to use the word highlighted in visual mode\r\nHightlight the word, then type\r\n:BetterSearchVisualSelect\r\nthen <ENTER>. \r\n\r\n[ jump to line ]\r\nA search window will be open up on top of the current window. \r\nPress <ENTER> on that particular line to jump to the content window.\r\n\r\n[ other commands ]\r\nOther command available by the script. (or press F1 when the focus\/cursor is at the search window)\r\n':BetterSearchSwitchWin'        - to switch between the 'Search Window' and the 'Content Window'\r\n':BetterSearchVisualSelect'     - to search based on the visually selected word\r\n':BetterSearchHighlighToggle'   - to toggle keyword highlight on off (default is on)\r\n':BetterSearchHighlightLimit'    - to toggle line limit to switch off keyword highlight, for efficiency purpose, \r\n                               - especially for large matched, default is 5000 line\r\n':BetterSearchCopyToClipBoard' - to toggle whether to save to the search words to clipboard, default is off\r\n\r\n[ mapping ]\r\nSuggest to map following in .vimrc, e.g: \r\nnnoremap <A-S-F7> :BetterSearchPromptOn<CR>\r\nvnoremap <A-S-F7> :BetterSearchVisualSelect<CR>\r\nnnoremap <A-w>  :BetterSearchSwitchWin<CR>\r\nnnoremap <A-S-q>  :BetterSearchCloseWin<CR>","4":"This script will now only updated @ github\r\nYou may get it from \r\nhttps:\/\/github.com\/kenng\/vim-bettersearch\r\n\r\n** note: tested in Linux\/MS window environment using GVIM **\r\n** note: BetterSearchVisualSelect command is found working in Linux, but might not working in MS Window environment at the moment ** \r\n\r\nProblem: \r\nHaving a large file and you need to search for a few keywords from it? \r\nAnd wish that you can at once glance all the search result? \r\nBest with highlight on the keyword? \r\nAnd you would wish to jump to that particular line when you see something interesting?\r\nHere is a good news for you! : )\r\nSolution approach: works somewhat similarly to notepad++ search function\r\n\r\nFeatures offered by betterSearch: \r\n- This script is written to copy all the search result and put it to window above the content. \r\n- If the line number is switch on, the search result is 'jumpable' to the content window by just enter on that particular search line\r\n- Search term highlight can be switched on and off\r\n- Search keyword can be saved to clipboard\r\n\r\nThere are a few way to use the function of this script.\r\n[ usage 1 ]  \r\nUser intended to type in the search words\r\n:BetterSearchPromptOn\r\nthen <ENTER>. \r\nA window will pop up for user input. \r\nThe user input can consists of more than one search term. For example: search_A|search_B|search_C...\r\n\r\n[ usage 2 ] \r\nUser intended to use the word under the cursor as the search term\r\n:BetterSearchPromptOn    \r\nthen <ENTER>. and press <ENTER> again when the user input dialog box appear without type in any word\r\n\r\n[ usage 3 ] \r\nUser intended to use the word highlighted in visual mode\r\nHightlight the word, then type\r\n:BetterSearchVisualSelect\r\nthen <ENTER>. \r\n\r\n[ jump to line ]\r\nA search window will be open up on top of the current window. \r\nPress <ENTER> on that particular line to jump to the content window.\r\n\r\n[ other commands ]\r\nOther command available by the script. (or press F1 when the focus\/cursor is at the search window)\r\n':BetterSearchSwitchWin'        - to switch between the 'Search Window' and the 'Content Window'\r\n':BetterSearchVisualSelect'     - to search based on the visually selected word\r\n':BetterSearchHighlighToggle'   - to toggle keyword highlight on off (default is on)\r\n':BetterSearchHighlightLimit'    - to toggle line limit to switch off keyword highlight, for efficiency purpose, \r\n                               - especially for large matched, default is 5000 line\r\n':BetterSearchCopyToClipBoard' - to toggle whether to save to the search words to clipboard, default is off\r\n\r\n[ mapping ]\r\nSuggest to map following in .vimrc, e.g: \r\nnnoremap <A-S-F7> :BetterSearchPromptOn<CR>\r\nvnoremap <A-S-F7> :BetterSearchVisualSelect<CR>\r\nnnoremap <A-w>  :BetterSearchSwitchWin<CR>\r\nnnoremap <A-S-q>  :BetterSearchCloseWin<CR>","install_details":"### Using Pathogon\r\n\r\n```\r\nmkdir -p ~\/.vim\/bundle\r\ncd ~\/.vim\/bundle\r\ngit clone https:\/\/github.com\/kenng\/vim-bettersearch.git\r\n```\r\n\r\n### The OLD way\r\n1. Paste the betterSearch.vim script into plugin folder.\r\n   E.g. Vim\\vim73\\plugin.\r\n2. Restart the Vim session\r\n","5":"### Using Pathogon\r\n\r\n```\r\nmkdir -p ~\/.vim\/bundle\r\ncd ~\/.vim\/bundle\r\ngit clone https:\/\/github.com\/kenng\/vim-bettersearch.git\r\n```\r\n\r\n### The OLD way\r\n1. Paste the betterSearch.vim script into plugin folder.\r\n   E.g. Vim\\vim73\\plugin.\r\n2. Restart the Vim session\r\n","first_name":"kn","6":"kn","last_name":"n","7":"n","releases":[{"0":"4241","vim_version":"7.0","1":"7.0","script_version":"0.0.9","2":"0.0.9","version_comment":"v0.0.9: highlight of result follows option ignorecase; custom highlight defined \r\nv0.0.8: revert function gotoLine() as it is easy and accurate","3":"v0.0.9: highlight of result follows option ignorecase; custom highlight defined \r\nv0.0.8: revert function gotoLine() as it is easy and accurate","package":"betterSearch.vim","4":"betterSearch.vim","src_id":"21849","5":"21849","creation_date":"1398953784","6":"1398953784"},{"0":"4241","vim_version":"7.0","1":"7.0","script_version":"0.0.7","2":"0.0.7","version_comment":" [ version ] 0.0.7 ( 29 Mar 2014 )\r\n   - fixed bug not able to jump to line when line number is switched on\r\n   - fixed bug not able to jump to line which contains certain regexp\r\n\r\n","3":" [ version ] 0.0.7 ( 29 Mar 2014 )\r\n   - fixed bug not able to jump to line when line number is switched on\r\n   - fixed bug not able to jump to line which contains certain regexp\r\n\r\n","package":"betterSearch.vim","4":"betterSearch.vim","src_id":"21690","5":"21690","creation_date":"1396051569","6":"1396051569"},{"0":"4241","vim_version":"7.0","1":"7.0","script_version":"0.0.5","2":"0.0.5","version_comment":"enable [Enter] to jump to particular line without line number switched on","3":"enable [Enter] to jump to particular line without line number switched on","package":"betterSearch.vim","4":"betterSearch.vim","src_id":"21558","5":"21558","creation_date":"1393764416","6":"1393764416"},{"0":"4241","vim_version":"7.0","1":"7.0","script_version":"0.0.4","2":"0.0.4","version_comment":"- enhanced help description","3":"- enhanced help description","package":"betterSearch.vim","4":"betterSearch.vim","src_id":"19309","5":"19309","creation_date":"1357253971","6":"1357253971"},{"0":"4241","vim_version":"7.0","1":"7.0","script_version":"0.0.3","2":"0.0.3","version_comment":"- showed the file path\r\n- added function to close the bettersearch window from anywhere\r\n- fixed visual select search\r\n","3":"- showed the file path\r\n- added function to close the bettersearch window from anywhere\r\n- fixed visual select search\r\n","package":"betterSearch.vim","4":"betterSearch.vim","src_id":"19308","5":"19308","creation_date":"1357252137","6":"1357252137"},{"0":"4241","vim_version":"7.0","1":"7.0","script_version":"0.0.2","2":"0.0.2","version_comment":"- able to set highlight syntax for search term\r\n- change default shortcut for syntax=c, help=F1\r\n- improve help description","3":"- able to set highlight syntax for search term\r\n- change default shortcut for syntax=c, help=F1\r\n- improve help description","package":"betterSearch.vim","4":"betterSearch.vim","src_id":"18726","5":"18726","creation_date":"1349085975","6":"1349085975"},{"0":"4241","vim_version":"7.0","1":"7.0","script_version":"0.0.1","2":"0.0.1","version_comment":"Initial upload","3":"Initial upload","package":"betterSearch.vim","4":"betterSearch.vim","src_id":"18698","5":"18698","creation_date":"1348739477","6":"1348739477"}]},"4240":{"script_id":"4240","0":"4240","script_name":"colorschemer","1":"colorschemer","script_type":"utility","2":"utility","summary":"Vim colorschemer","3":"Vim colorschemer","description":"The ColorSchemer is a Forms library based utility.\r\nThe Forms library  can be found at\r\nhttp:\/\/www.vim.org\/scripts\/script.php?script_id=4150\r\nor\r\nhttps:\/\/github.com\/megaannum\/forms\r\n\r\n\r\nThe ColorSchemer consist of three parts:\r\n  Basic utilty and core data,\r\n  Cterm distilled color scheme data files and\r\n  Gui distilled color scheme data files.\r\n\r\nThe core subset of colorschemer does not require either the\r\ncterm or gui data files. It consist of the Distill code\r\nfound in 'distill.vim' and the Viewer code found in 'viewer.vim'.\r\nIn addition, it has a collection of some 687 third-party color\r\nscheme files.\r\n\r\nThe Distiller will take one or more color scheme files and\r\nproduce 'distilled' versions of those color schema.\r\nThe processing does the following:\r\n*  It eliminates those highlight group declarations that are redundant,\r\n*  It eliminates those group attributes that are redundant,\r\n*  Generates a standard comment header and initial VimL code:\r\n\r\n        set background= 'light' or 'dark'\r\n        hi clear\r\n\r\n        if exists(\"syntax_on\")\r\n            syntax reset\r\n        endif\r\n\r\n        let g:colors_name = expand(\"<sfile>:t:r\")\r\n\r\n*  Output highlight group definitions targeted for specific GVim and Vim\r\nconfigurations:\r\n\r\n        if has(\"gui_running\")\r\n            \" highlights for GVim\r\n        elseif &t_Co == 256\r\n            \" highlights for 256 color Xterm Vim\r\n        elseif &t_Co == 88\r\n            \" highlights for 88 urvxt color Vim\r\n        elseif &t_Co == 16\r\n            \" highlights for 16 color Xterm Vim\r\n        else \" &t_Co == 8\r\n            \" highlights for 8 color Xterm Vim\r\n        endif\r\n\r\n*  It eliminates redundant link definitions,\r\n*  The background color set depends primarily on the Normal background value and not what the color scheme file says (because, they sometimes lie).\r\n*  When appropriate generates both a 'dark' and 'light' version of the same base color scheme file.\r\n\r\nOne of the Distill functions takes all of the 687 third-party color\r\nschema and distills them. It should be noted that slightly different\r\nresults are achieved when executing the Distill code in GVim versus\r\nVim (some color schemes only have definitions for GVim or Vim).\r\n\r\nAlso part of the core distribution that allows one to very easily\r\nview different file-types applying different color schemes.\r\nFar easier and quicker than other ways.\r\nThe viewer can be invoked through the mapping:\r\n\r\n    <Leader>cv\r\n\r\nThe Cterm distribution contains the set of distilled files generated\r\nby the distill script by using Vim. A user can simply download this\r\nset if they do not want to generate them themselves using distill.vim.\r\n\r\nThe Gui distribution contains the set of distilled files generated\r\nby the distill script by using GVim. A user can simply download this\r\nset if they do not want to generate them themselves using distill.vim.\r\n\r\n\r\nThe release version can also be found at:\r\nhttps:\/\/github.com\/megaannum\/colorschemer\r\n\r\nExamples images of the color schemer viewer can be found at:\r\nhttps:\/\/github.com\/megaannum\/colorschemer\/tree\/master\/images\r\n\r\n","4":"The ColorSchemer is a Forms library based utility.\r\nThe Forms library  can be found at\r\nhttp:\/\/www.vim.org\/scripts\/script.php?script_id=4150\r\nor\r\nhttps:\/\/github.com\/megaannum\/forms\r\n\r\n\r\nThe ColorSchemer consist of three parts:\r\n  Basic utilty and core data,\r\n  Cterm distilled color scheme data files and\r\n  Gui distilled color scheme data files.\r\n\r\nThe core subset of colorschemer does not require either the\r\ncterm or gui data files. It consist of the Distill code\r\nfound in 'distill.vim' and the Viewer code found in 'viewer.vim'.\r\nIn addition, it has a collection of some 687 third-party color\r\nscheme files.\r\n\r\nThe Distiller will take one or more color scheme files and\r\nproduce 'distilled' versions of those color schema.\r\nThe processing does the following:\r\n*  It eliminates those highlight group declarations that are redundant,\r\n*  It eliminates those group attributes that are redundant,\r\n*  Generates a standard comment header and initial VimL code:\r\n\r\n        set background= 'light' or 'dark'\r\n        hi clear\r\n\r\n        if exists(\"syntax_on\")\r\n            syntax reset\r\n        endif\r\n\r\n        let g:colors_name = expand(\"<sfile>:t:r\")\r\n\r\n*  Output highlight group definitions targeted for specific GVim and Vim\r\nconfigurations:\r\n\r\n        if has(\"gui_running\")\r\n            \" highlights for GVim\r\n        elseif &t_Co == 256\r\n            \" highlights for 256 color Xterm Vim\r\n        elseif &t_Co == 88\r\n            \" highlights for 88 urvxt color Vim\r\n        elseif &t_Co == 16\r\n            \" highlights for 16 color Xterm Vim\r\n        else \" &t_Co == 8\r\n            \" highlights for 8 color Xterm Vim\r\n        endif\r\n\r\n*  It eliminates redundant link definitions,\r\n*  The background color set depends primarily on the Normal background value and not what the color scheme file says (because, they sometimes lie).\r\n*  When appropriate generates both a 'dark' and 'light' version of the same base color scheme file.\r\n\r\nOne of the Distill functions takes all of the 687 third-party color\r\nschema and distills them. It should be noted that slightly different\r\nresults are achieved when executing the Distill code in GVim versus\r\nVim (some color schemes only have definitions for GVim or Vim).\r\n\r\nAlso part of the core distribution that allows one to very easily\r\nview different file-types applying different color schemes.\r\nFar easier and quicker than other ways.\r\nThe viewer can be invoked through the mapping:\r\n\r\n    <Leader>cv\r\n\r\nThe Cterm distribution contains the set of distilled files generated\r\nby the distill script by using Vim. A user can simply download this\r\nset if they do not want to generate them themselves using distill.vim.\r\n\r\nThe Gui distribution contains the set of distilled files generated\r\nby the distill script by using GVim. A user can simply download this\r\nset if they do not want to generate them themselves using distill.vim.\r\n\r\n\r\nThe release version can also be found at:\r\nhttps:\/\/github.com\/megaannum\/colorschemer\r\n\r\nExamples images of the color schemer viewer can be found at:\r\nhttps:\/\/github.com\/megaannum\/colorschemer\/tree\/master\/images\r\n\r\n","install_details":"To get the Basic utilty and core data:\r\n  Download the colorschemer_core.zip file\r\n\r\nTo get the Cterm distilled color scheme files\r\n  Download the colorschemer_cterm.zip file\r\n\r\nTo get the Gui distilled color scheme files\r\n  Download the colorschemer_gui.zip file\r\n\r\n\r\nA zip snapshot of the {ColorSchemer} library can be downloaded\r\nfrom www.vim.org (http:\/\/www.vim.org\/scripts\/script.php?script_id=4240)\r\n\r\n\r\nIn your Vim home, normally $HOME\/.vim in Unix, unzip the file:\r\n\r\n    # cd $HOME\/.vim\r\n    # unzip colorschemer_core.zip\r\n    # unzip colorschemer_cterm.zip       -- optional\r\n    # unzip colorschemer_gui.zip         -- optional\r\n\r\n\r\nOn a Windows system, vim home is normally $HOME\/vimfiles.\r\n\r\n    TODO how to unpack on Windows?\r\n\r\n{ColorSchemer} is also available via\r\n[githup](http:\/\/github.com\/megaannum\/colorschemer).\r\nOne can download a release from github and extract content.\r\n\r\nIf as a developer, one wants fixes as they appear, one can clone the\r\ngithub {ColorSchemer} repository and, as updates appear, copy the files\r\nover to you Vim home location.\r\n\r\nVim has a number of third-party plugin managers. If you are using one\r\nyou can configure it to automatically download and install {ColorSchemer}.\r\n\r\nAfter unpacking the ColorSchemer directory layout should look like:\r\n\r\n    $HOME\/.vim\/\r\n      autoload\/\r\n        colorschemer\/\r\n          distill.vim\r\n            \" generate distilled color scheme files\r\n          util.vim\r\n          viewer.vim\r\n            \" view test files with their syntax allowing for\r\n            \" very quick toggling through color schemes\r\n      data\/\r\n        \" data that persists between invocations of a plugin\r\n        colorschemer\/\r\n            \" colorschemer data\r\n            colors\/\r\n              \" source Vim color scheme files (some 688 of them!)\r\n            distilled\/\r\n              \" target directory for files generated by distill.vim\r\n            distilled.cterm\/\r\n              \" generated using distill.vim in Vim\r\n              \" optional part of the colorschemer_cterm.zip\r\n            distilled.gui\/\r\n              \" generated using distill.vim in GVim\r\n              \" optional part of the colorschemer_gui.zip\r\n            test\/\r\n              \" test source files (c, pl, java, scala, tex, html)\r\n              \" users can add addition ones\r\n      doc\/\r\n        colorschemer.txt\r\n      plugin\/\r\n        colorschemer.vim\r\n\r\nIntalling with vim-addon-manager (VAM)\r\n\r\nFor more information about vim-addon-manager, see [vim-addon-manager](https:\/\/github.com\/MarcWeber\/vim-addon-manager) and [Vim-addon-manager getting started](https:\/\/github.com\/MarcWeber\/vim-addon-manager\/blob\/master\/doc\/vim-addon-manager-getting-started.txt)\r\n\r\nIn your .vimrc, add self as shown below:\r\n\r\n    fun SetupVAM()\r\n\r\n      ...\r\n\r\n      let g:vim_addon_manager = {}\r\n      let g:vim_addon_manager.plugin_sources = {}\r\n\r\n      ....\r\n\r\n      let g:vim_addon_manager.plugin_sources['self'] = {'type': 'git', 'url': 'git:\/\/github.com\/megaannum\/self'}\r\n      let g:vim_addon_manager.plugin_sources['forms'] = {'type': 'git', 'url': 'git:\/\/github.com\/megaannum\/forms'}\r\n      let g:vim_addon_manager.plugin_sources['colorschemer'] = {'type': 'git', 'url': 'git:\/\/github.com\/megaannum\/colorschemer'}\r\n\r\n\r\n      let plugins = [\r\n        \\ 'self',\r\n        \\ 'forms',\r\n        \\ 'colorschemer'\r\n        \\ ]\r\n\r\n      call vam#ActivateAddons(plugins,{'auto_install' : 0})\r\n\r\n      ...\r\n\r\n    endf\r\n    call SetupVAM()\r\n\r\n\r\nNow start Vim. You will be asked by vim-addon-manager\r\nif you would like to download and install the self plugin (no dependencies).\r\n\r\nInstalling with pathogen:\r\nI do not use pathogen. An example usage would be welcome.\r\n\r\n","5":"To get the Basic utilty and core data:\r\n  Download the colorschemer_core.zip file\r\n\r\nTo get the Cterm distilled color scheme files\r\n  Download the colorschemer_cterm.zip file\r\n\r\nTo get the Gui distilled color scheme files\r\n  Download the colorschemer_gui.zip file\r\n\r\n\r\nA zip snapshot of the {ColorSchemer} library can be downloaded\r\nfrom www.vim.org (http:\/\/www.vim.org\/scripts\/script.php?script_id=4240)\r\n\r\n\r\nIn your Vim home, normally $HOME\/.vim in Unix, unzip the file:\r\n\r\n    # cd $HOME\/.vim\r\n    # unzip colorschemer_core.zip\r\n    # unzip colorschemer_cterm.zip       -- optional\r\n    # unzip colorschemer_gui.zip         -- optional\r\n\r\n\r\nOn a Windows system, vim home is normally $HOME\/vimfiles.\r\n\r\n    TODO how to unpack on Windows?\r\n\r\n{ColorSchemer} is also available via\r\n[githup](http:\/\/github.com\/megaannum\/colorschemer).\r\nOne can download a release from github and extract content.\r\n\r\nIf as a developer, one wants fixes as they appear, one can clone the\r\ngithub {ColorSchemer} repository and, as updates appear, copy the files\r\nover to you Vim home location.\r\n\r\nVim has a number of third-party plugin managers. If you are using one\r\nyou can configure it to automatically download and install {ColorSchemer}.\r\n\r\nAfter unpacking the ColorSchemer directory layout should look like:\r\n\r\n    $HOME\/.vim\/\r\n      autoload\/\r\n        colorschemer\/\r\n          distill.vim\r\n            \" generate distilled color scheme files\r\n          util.vim\r\n          viewer.vim\r\n            \" view test files with their syntax allowing for\r\n            \" very quick toggling through color schemes\r\n      data\/\r\n        \" data that persists between invocations of a plugin\r\n        colorschemer\/\r\n            \" colorschemer data\r\n            colors\/\r\n              \" source Vim color scheme files (some 688 of them!)\r\n            distilled\/\r\n              \" target directory for files generated by distill.vim\r\n            distilled.cterm\/\r\n              \" generated using distill.vim in Vim\r\n              \" optional part of the colorschemer_cterm.zip\r\n            distilled.gui\/\r\n              \" generated using distill.vim in GVim\r\n              \" optional part of the colorschemer_gui.zip\r\n            test\/\r\n              \" test source files (c, pl, java, scala, tex, html)\r\n              \" users can add addition ones\r\n      doc\/\r\n        colorschemer.txt\r\n      plugin\/\r\n        colorschemer.vim\r\n\r\nIntalling with vim-addon-manager (VAM)\r\n\r\nFor more information about vim-addon-manager, see [vim-addon-manager](https:\/\/github.com\/MarcWeber\/vim-addon-manager) and [Vim-addon-manager getting started](https:\/\/github.com\/MarcWeber\/vim-addon-manager\/blob\/master\/doc\/vim-addon-manager-getting-started.txt)\r\n\r\nIn your .vimrc, add self as shown below:\r\n\r\n    fun SetupVAM()\r\n\r\n      ...\r\n\r\n      let g:vim_addon_manager = {}\r\n      let g:vim_addon_manager.plugin_sources = {}\r\n\r\n      ....\r\n\r\n      let g:vim_addon_manager.plugin_sources['self'] = {'type': 'git', 'url': 'git:\/\/github.com\/megaannum\/self'}\r\n      let g:vim_addon_manager.plugin_sources['forms'] = {'type': 'git', 'url': 'git:\/\/github.com\/megaannum\/forms'}\r\n      let g:vim_addon_manager.plugin_sources['colorschemer'] = {'type': 'git', 'url': 'git:\/\/github.com\/megaannum\/colorschemer'}\r\n\r\n\r\n      let plugins = [\r\n        \\ 'self',\r\n        \\ 'forms',\r\n        \\ 'colorschemer'\r\n        \\ ]\r\n\r\n      call vam#ActivateAddons(plugins,{'auto_install' : 0})\r\n\r\n      ...\r\n\r\n    endf\r\n    call SetupVAM()\r\n\r\n\r\nNow start Vim. You will be asked by vim-addon-manager\r\nif you would like to download and install the self plugin (no dependencies).\r\n\r\nInstalling with pathogen:\r\nI do not use pathogen. An example usage would be welcome.\r\n\r\n","first_name":"richard","6":"richard","last_name":"emberson","7":"emberson","releases":[{"0":"4240","vim_version":"7.3","1":"7.3","script_version":"1.2b","2":"1.2b","version_comment":"Gui Data Initial Release","3":"Gui Data Initial Release","package":"colorschemer_gui.zip","4":"colorschemer_gui.zip","src_id":"18730","5":"18730","creation_date":"1349107555","6":"1349107555"},{"0":"4240","vim_version":"7.3","1":"7.3","script_version":"1.2a","2":"1.2a","version_comment":"Cterm data Initial Release","3":"Cterm data Initial Release","package":"colorschemer_cterm.zip","4":"colorschemer_cterm.zip","src_id":"18729","5":"18729","creation_date":"1349107484","6":"1349107484"},{"0":"4240","vim_version":"7.3","1":"7.3","script_version":"1.2","2":"1.2","version_comment":"Core Initial Release","3":"Core Initial Release","package":"colorschemer_core.zip","4":"colorschemer_core.zip","src_id":"18728","5":"18728","creation_date":"1349107409","6":"1349107409"}]},"4239":{"script_id":"4239","0":"4239","script_name":"Freya","1":"Freya","script_type":"color scheme","2":"color scheme","summary":"A dark color scheme with warm colors.","3":"A dark color scheme with warm colors.","description":"This is an extended and updated version of the original Freya color scheme by Georg Dahn. The original can be found here: http:\/\/www.vim.org\/scripts\/script.php?script_id=1651\r\n\r\nThis color scheme fully supports HTML, CSS, TagList, CtrlP and NERDTree\r\n\r\nThis color scheme is for GUI only but will work with 256 color terminals with the CSApprox plugin.\r\n\r\nScreenshot: http:\/\/i.imgur.com\/ncwZ9.png","4":"This is an extended and updated version of the original Freya color scheme by Georg Dahn. The original can be found here: http:\/\/www.vim.org\/scripts\/script.php?script_id=1651\r\n\r\nThis color scheme fully supports HTML, CSS, TagList, CtrlP and NERDTree\r\n\r\nThis color scheme is for GUI only but will work with 256 color terminals with the CSApprox plugin.\r\n\r\nScreenshot: http:\/\/i.imgur.com\/ncwZ9.png","install_details":"Just put it in \"~\/.vim\/colors\" or in \"<your vim directory>\\vimfiles\\colors\" on Windows.\r\n\r\nDo \":color freya\" to apply it. If you want to install it as your default color scheme, just add \"color freya\" to your vimrc file.","5":"Just put it in \"~\/.vim\/colors\" or in \"<your vim directory>\\vimfiles\\colors\" on Windows.\r\n\r\nDo \":color freya\" to apply it. If you want to install it as your default color scheme, just add \"color freya\" to your vimrc file.","first_name":"Gary","6":"Gary","last_name":"Willoughby","7":"Willoughby","releases":[{"0":"4239","vim_version":"7.0","1":"7.0","script_version":"2.3","2":"2.3","version_comment":"Added new CursorColumn highlighting group.","3":"Added new CursorColumn highlighting group.","package":"freya.vim","4":"freya.vim","src_id":"18873","5":"18873","creation_date":"1351103305","6":"1351103305"},{"0":"4239","vim_version":"7.0","1":"7.0","script_version":"2.2","2":"2.2","version_comment":"Modified some colors and made the UI colors a little more subdued for a darker, cleaner look.","3":"Modified some colors and made the UI colors a little more subdued for a darker, cleaner look.","package":"freya.vim","4":"freya.vim","src_id":"18801","5":"18801","creation_date":"1350155956","6":"1350155956"},{"0":"4239","vim_version":"7.3","1":"7.3","script_version":"2.1","2":"2.1","version_comment":"Initial upload","3":"Initial upload","package":"freya.vim","4":"freya.vim","src_id":"18688","5":"18688","creation_date":"1348592643","6":"1348592643"}]},"4238":{"script_id":"4238","0":"4238","script_name":"RepeatableYank","1":"RepeatableYank","script_type":"utility","2":"utility","summary":"Repeatable appending yank to a named register.","3":"Repeatable appending yank to a named register.","description":"DESCRIPTION\r\nText fragments can be collected and accumulated by first yanking into a\r\nlowercase register, and then subsequently yanking into the uppercase variant.\r\nThe problem is that the register must be specified on every yank command, and\r\none accidental omission of uppercasing the register results in the\r\nirrecoverable loss of all fragments collected so far.\r\n\r\nThis can be somewhat remedied by enabling the non-default cpo-y setting,\r\nwhich allows a repeat of a yank (plus remembered last register) via .\r\n\r\nThis plugin instead offers an alternative yank command gy, which allows to\r\nspecify the accumulator register only once on its initial use, can then be\r\nrepeated as an operator, linewise, in visual mode and via ., and enhances\r\nsome yank semantics for special cases.  For example, subsequent blockwise\r\nyanks are merged as blocks to the right, instead of added below the existing\r\ntext blocks.\r\n\r\nUSAGE\r\n[\"x]gy{motion}          Yank {motion} text into register x.\r\n[\"x][count]gyy          Yank [count] lines into register x.\r\n{Visual}[\"x]gy          Yank the selected text into register x.\r\n\r\n                        Subsequent gy commands without an explicit register\r\n                        and command repeats via . will append (in the case\r\n                        of named registers {a-zA-Z}) the text to \/ overwrite\r\n                        (for registers {0-9*+~\/-}) the previously used\r\n                        register x, until another register is explicitly\r\n                        given.\r\n                        Therefore, you can gradually build up text in a named\r\n                        register, or easily update the system clipboard\r\n                        without having to repeat the register on every yank.\r\n\r\n                        Subsequent blockwise yanks are merged as blocks to the\r\n                        right:\r\n                            ab -> ab12\r\n                            cd    cd34\r\n                        instead of added below the existing text blocks:\r\n                            ab -> ab\r\n                            cd    cd\r\n                                  12\r\n                                  34\r\n\r\n[\"x]gly{motion}         Yank {motion} text as a new line into register x.\r\n{Visual}[\"x]gly         Yank the selected text as a new line into register x.\r\n                        When repeated, the text will be automatically\r\n                        separated from the existing contents by a newline\r\n                        character. This is useful for collecting individual\r\n                        words (without surrounding whitespace), or other\r\n                        phrases when you intend to work on them as separate\r\n                        lines.\r\n\r\n                        You can also use this mapping to avoid the special\r\n                        RepeatableYank-block-merge behavior.\r\n\r\nEXAMPLE\r\nStart by yanking \"an entire line\" into register a:\r\n    \"agyy\r\n   an entire line\r\n\r\nAdd \"another line\" to the same register a without specifying it again:\r\n    gyy\r\n   an entire line\r\n    another line\r\n\r\nAdd \"word1\" and \"word2\"; even though the register is now of linewise type,\r\nthese are added on a single line:\r\n    gyw w.\r\n   an entire line\r\n    another line\r\n    word1 word2\r\n\r\nNow, let's yank a vertical block of \"ABC\" into another register:\r\n    <C-V>2j \"bgy\r\n   A\r\n    B\r\n    C\r\nAnother vertical block of \"123\" is appended blockwise to the right:\r\n    l1v.\r\n   A1\r\n    B2\r\n    C3\r\n\r\nYou can build up multiple registers in parallel. To switch to another register\r\nwithout starting over, just specify the uppercase register name:\r\n    \"Agyy\r\n   an entire line\r\n    another line\r\n    word1 word2\r\n    +addition after register switch\r\n\r\nThis is an example of gly:\r\nStart by yanking \"word1\" into register a:\r\n    \"aglyi\"\r\n   word1\r\n\r\nAdd \"word2\" and \"word3\", but on separate lines, so that the register contents\r\ndon't turn into a mess of \"word1word2word3\":\r\n    glyi\"\r\n    word1\r\n    word2\r\n    w.\r\n    word1\r\n    word2\r\n    word3","4":"DESCRIPTION\r\nText fragments can be collected and accumulated by first yanking into a\r\nlowercase register, and then subsequently yanking into the uppercase variant.\r\nThe problem is that the register must be specified on every yank command, and\r\none accidental omission of uppercasing the register results in the\r\nirrecoverable loss of all fragments collected so far.\r\n\r\nThis can be somewhat remedied by enabling the non-default cpo-y setting,\r\nwhich allows a repeat of a yank (plus remembered last register) via .\r\n\r\nThis plugin instead offers an alternative yank command gy, which allows to\r\nspecify the accumulator register only once on its initial use, can then be\r\nrepeated as an operator, linewise, in visual mode and via ., and enhances\r\nsome yank semantics for special cases.  For example, subsequent blockwise\r\nyanks are merged as blocks to the right, instead of added below the existing\r\ntext blocks.\r\n\r\nUSAGE\r\n[\"x]gy{motion}          Yank {motion} text into register x.\r\n[\"x][count]gyy          Yank [count] lines into register x.\r\n{Visual}[\"x]gy          Yank the selected text into register x.\r\n\r\n                        Subsequent gy commands without an explicit register\r\n                        and command repeats via . will append (in the case\r\n                        of named registers {a-zA-Z}) the text to \/ overwrite\r\n                        (for registers {0-9*+~\/-}) the previously used\r\n                        register x, until another register is explicitly\r\n                        given.\r\n                        Therefore, you can gradually build up text in a named\r\n                        register, or easily update the system clipboard\r\n                        without having to repeat the register on every yank.\r\n\r\n                        Subsequent blockwise yanks are merged as blocks to the\r\n                        right:\r\n                            ab -> ab12\r\n                            cd    cd34\r\n                        instead of added below the existing text blocks:\r\n                            ab -> ab\r\n                            cd    cd\r\n                                  12\r\n                                  34\r\n\r\n[\"x]gly{motion}         Yank {motion} text as a new line into register x.\r\n{Visual}[\"x]gly         Yank the selected text as a new line into register x.\r\n                        When repeated, the text will be automatically\r\n                        separated from the existing contents by a newline\r\n                        character. This is useful for collecting individual\r\n                        words (without surrounding whitespace), or other\r\n                        phrases when you intend to work on them as separate\r\n                        lines.\r\n\r\n                        You can also use this mapping to avoid the special\r\n                        RepeatableYank-block-merge behavior.\r\n\r\nEXAMPLE\r\nStart by yanking \"an entire line\" into register a:\r\n    \"agyy\r\n   an entire line\r\n\r\nAdd \"another line\" to the same register a without specifying it again:\r\n    gyy\r\n   an entire line\r\n    another line\r\n\r\nAdd \"word1\" and \"word2\"; even though the register is now of linewise type,\r\nthese are added on a single line:\r\n    gyw w.\r\n   an entire line\r\n    another line\r\n    word1 word2\r\n\r\nNow, let's yank a vertical block of \"ABC\" into another register:\r\n    <C-V>2j \"bgy\r\n   A\r\n    B\r\n    C\r\nAnother vertical block of \"123\" is appended blockwise to the right:\r\n    l1v.\r\n   A1\r\n    B2\r\n    C3\r\n\r\nYou can build up multiple registers in parallel. To switch to another register\r\nwithout starting over, just specify the uppercase register name:\r\n    \"Agyy\r\n   an entire line\r\n    another line\r\n    word1 word2\r\n    +addition after register switch\r\n\r\nThis is an example of gly:\r\nStart by yanking \"word1\" into register a:\r\n    \"aglyi\"\r\n   word1\r\n\r\nAdd \"word2\" and \"word3\", but on separate lines, so that the register contents\r\ndon't turn into a mess of \"word1word2word3\":\r\n    glyi\"\r\n    word1\r\n    word2\r\n    w.\r\n    word1\r\n    word2\r\n    word3","install_details":"INSTALLATION\r\nThis script is packaged as a vimball. If you have the \"gunzip\" decompressor\r\nin your PATH, simply edit the *.vmb.gz package in Vim; otherwise, decompress\r\nthe archive first, e.g. using WinZip. Inside Vim, install by sourcing the\r\nvimball or via the :UseVimball command.\r\n    vim RepeatableYank*.vmb.gz\r\n    :so %\r\nTo uninstall, use the :RmVimball command.\r\n\r\nDEPENDENCIES\r\n- Requires Vim 7.0 or higher.\r\n- Requires the ingo-library.vim plugin (vimscript #4433), version 1.008 or\r\n  higher.\r\n- repeat.vim (vimscript #2136) plugin (optional).\r\n- visualrepeat.vim (vimscript #3848) plugin (version 2.00 or higher; optional)\r\n\r\nCONFIGURATION\r\nFor a permanent configuration, put the following commands into your vimrc:\r\n\r\nSince you don't need this plugin to repeat yanks to the unnamed register (just\r\nuse the built-in y), register \"a is used as the default register, i.e. when\r\nyou use gy for the first time without explicitly specifying a register. To\r\nchange this default to another register (e.g. the clipboard), use:\r\n    let g:RepeatableYank_DefaultRegister = '+'\r\n\r\nIf you want to use different mappings, map your keys to the\r\n<Plug>RepeatableYank... mapping targets _before_ sourcing the script (e.g. in\r\nyour vimrc):\r\n    nmap <Leader>y  <Plug>RepeatableYankOperator\r\n    nmap <Leader>yy <Plug>RepeatableYankLine\r\n    xmap <Leader>y  <Plug>RepeatableYankVisual\r\n    nmap <Leader>ly <Plug>RepeatableYankAsLineOperator\r\n    xmap <Leader>ly <Plug>RepeatableYankAsLineVisual\r\n\r\nIf you don't need the gly mappings introduced in version 1.10:\r\n    nmap <Plug>DisableRepeatableYankAsLineOperator <Plug>RepeatableYankAsLineOperator\r\n    xmap <Plug>DisableRepeatableYankAsLineVisual   <Plug>RepeatableYankAsLineVisual","5":"INSTALLATION\r\nThis script is packaged as a vimball. If you have the \"gunzip\" decompressor\r\nin your PATH, simply edit the *.vmb.gz package in Vim; otherwise, decompress\r\nthe archive first, e.g. using WinZip. Inside Vim, install by sourcing the\r\nvimball or via the :UseVimball command.\r\n    vim RepeatableYank*.vmb.gz\r\n    :so %\r\nTo uninstall, use the :RmVimball command.\r\n\r\nDEPENDENCIES\r\n- Requires Vim 7.0 or higher.\r\n- Requires the ingo-library.vim plugin (vimscript #4433), version 1.008 or\r\n  higher.\r\n- repeat.vim (vimscript #2136) plugin (optional).\r\n- visualrepeat.vim (vimscript #3848) plugin (version 2.00 or higher; optional)\r\n\r\nCONFIGURATION\r\nFor a permanent configuration, put the following commands into your vimrc:\r\n\r\nSince you don't need this plugin to repeat yanks to the unnamed register (just\r\nuse the built-in y), register \"a is used as the default register, i.e. when\r\nyou use gy for the first time without explicitly specifying a register. To\r\nchange this default to another register (e.g. the clipboard), use:\r\n    let g:RepeatableYank_DefaultRegister = '+'\r\n\r\nIf you want to use different mappings, map your keys to the\r\n<Plug>RepeatableYank... mapping targets _before_ sourcing the script (e.g. in\r\nyour vimrc):\r\n    nmap <Leader>y  <Plug>RepeatableYankOperator\r\n    nmap <Leader>yy <Plug>RepeatableYankLine\r\n    xmap <Leader>y  <Plug>RepeatableYankVisual\r\n    nmap <Leader>ly <Plug>RepeatableYankAsLineOperator\r\n    xmap <Leader>ly <Plug>RepeatableYankAsLineVisual\r\n\r\nIf you don't need the gly mappings introduced in version 1.10:\r\n    nmap <Plug>DisableRepeatableYankAsLineOperator <Plug>RepeatableYankAsLineOperator\r\n    xmap <Plug>DisableRepeatableYankAsLineVisual   <Plug>RepeatableYankAsLineVisual","first_name":"Ingo","6":"Ingo","last_name":"Karkat","7":"Karkat","releases":[{"0":"4238","vim_version":"7.0","1":"7.0","script_version":"1.20","2":"1.20","version_comment":"- Use optional visualrepeat#reapply#VisualMode() for normal mode repeat of a visual mapping. When supplying a [count] on such repeat of a previous linewise selection, now [count] number of lines instead of [count] times the original selection is used.\r\n- Avoid changing the jumplist.\r\n- Add dependency to ingo-library (vimscript #4433). *** You need to separately install ingo-library (vimscript #4433) version 1.008 (or higher)! ***","3":"- Use optional visualrepeat#reapply#VisualMode() for normal mode repeat of a visual mapping. When supplying a [count] on such repeat of a previous linewise selection, now [count] number of lines instead of [count] times the original selection is used.\r\n- Avoid changing the jumplist.\r\n- Add dependency to ingo-library (vimscript #4433). *** You need to separately install ingo-library (vimscript #4433) version 1.008 (or higher)! ***","package":"RepeatableYank-1.20.vmb.gz","4":"RepeatableYank-1.20.vmb.gz","src_id":"21085","5":"21085","creation_date":"1385040125","6":"1385040125"},{"0":"4238","vim_version":"7.0","1":"7.0","script_version":"1.10","2":"1.10","version_comment":"- ENH: Add alternative gly mapping to yank as new line.\r\n- FIX: When appending a block consisting of a single line, the merge doesn't capture the new block at all.","3":"- ENH: Add alternative gly mapping to yank as new line.\r\n- FIX: When appending a block consisting of a single line, the merge doesn't capture the new block at all.","package":"RepeatableYank-1.10.vmb.gz","4":"RepeatableYank-1.10.vmb.gz","src_id":"19244","5":"19244","creation_date":"1356596399","6":"1356596399"},{"0":"4238","vim_version":"7.0","1":"7.0","script_version":"1.00","2":"1.00","version_comment":"Initial upload","3":"Initial upload","package":"RepeatableYank-1.00.vmb.gz","4":"RepeatableYank-1.00.vmb.gz","src_id":"18681","5":"18681","creation_date":"1348516926","6":"1348516926"}]},"4237":{"script_id":"4237","0":"4237","script_name":"taboo.vim","1":"taboo.vim","script_type":"utility","2":"utility","summary":"Easily customize your tabline","3":"Easily customize your tabline","description":"\r\nTaboo aims to ease the way you set your vim tabline. In addition, it provides fews useful utilities for renaming tabs.\r\n\r\nCheck the documentation at https:\/\/github.com\/gcmt\/taboo.vim","4":"\r\nTaboo aims to ease the way you set your vim tabline. In addition, it provides fews useful utilities for renaming tabs.\r\n\r\nCheck the documentation at https:\/\/github.com\/gcmt\/taboo.vim","install_details":"\r\nInstall with your favorite plugin manager.","5":"\r\nInstall with your favorite plugin manager.","first_name":"geck","6":"geck","last_name":" ","7":" ","releases":[{"0":"4237","vim_version":"7.2","1":"7.2","script_version":"1.0","2":"1.0","version_comment":"- Major overhaul","3":"- Major overhaul","package":"taboo.zip","4":"taboo.zip","src_id":"22172","5":"22172","creation_date":"1404914069","6":"1404914069"}]},"4224":{"script_id":"4224","0":"4224","script_name":"System","1":"System","script_type":"utility","2":"utility","summary":" A way to use system commands with `: !`","3":" A way to use system commands with `: !`","description":"I# System Vim Plugin\r\n\r\nThis is a tiny vim script which might have been discovered ages ago (but I am\r\nunaware). Its rather for vim than gvim users.\r\n\r\nWhen executing commands from vim you enter a vim shell where you see the\r\noutput. In many situations this is not what you want and you'd prefer \r\n```viml\r\n    :call system(\"command\")\r\n```\r\nbut it is a lot to type, and you don't have completion. With this snippet\r\nevery command which starts with:\r\n```viml\r\n    :! command\r\n```\r\n(note the space after the `!`) will be wrapped into `system()` and the output\r\nwill be echoed. The plugin refreshes the history with what you typed rather\r\nthan the call to the `system()` function.\r\n\r\nThere are some configuration variables:\r\n```viml\r\n    g:system_expand = 1\r\n```\r\nby default `%` (with modifiers) is expanded in the same way as by the `:!`.\r\n```viml\r\n    g:system_echocmd = 0\r\n```\r\necho the command together with its output (by default off).\r\n\r\nThe reason why I like it is that I have different background colors in vim\r\n(dark) and terminal (light). If I stay inside vim I am not flushed with\r\nbright colors which is a annoying (and may be eyes tiring).\r\n\r\nBenefits: you get completion for system commands and system files.\r\n\r\nYou can use the expression register with Vim 7.3.686.  With an earlier version\r\nyou will not be able to use it.\r\n\r\n# Requirements\r\nYou have to also install [CRDispatcher](https:\/\/github.com\/coot\/CRDispatcher)\r\nplugin.\r\n\r\nI learned how to do that reading the\r\n[EmacsCommandLine Plugin](https:\/\/github.com\/houtsnip\/vim-emacscommandline).\r\n\r\nOther plugins with shell like functionality:\r\n* [vim-addon-async](https:\/\/github.com\/MarcWeber\/vim-addon-async)\r\n* [Conque Shell Plugin](http:\/\/code.google.com\/p\/conque)\r\n* [VimProc Plugin](http:\/\/github.com\/Shougo\/vimproc\/tree\/master\/doc\/vimproc.txt)\r\n\r\n## Copyright\r\n\u00c2\u00a9 Marcin Szamotulski, 2012-2014\r\n\r\n## License\r\nVim license, see :help license\r\n","4":"I# System Vim Plugin\r\n\r\nThis is a tiny vim script which might have been discovered ages ago (but I am\r\nunaware). Its rather for vim than gvim users.\r\n\r\nWhen executing commands from vim you enter a vim shell where you see the\r\noutput. In many situations this is not what you want and you'd prefer \r\n```viml\r\n    :call system(\"command\")\r\n```\r\nbut it is a lot to type, and you don't have completion. With this snippet\r\nevery command which starts with:\r\n```viml\r\n    :! command\r\n```\r\n(note the space after the `!`) will be wrapped into `system()` and the output\r\nwill be echoed. The plugin refreshes the history with what you typed rather\r\nthan the call to the `system()` function.\r\n\r\nThere are some configuration variables:\r\n```viml\r\n    g:system_expand = 1\r\n```\r\nby default `%` (with modifiers) is expanded in the same way as by the `:!`.\r\n```viml\r\n    g:system_echocmd = 0\r\n```\r\necho the command together with its output (by default off).\r\n\r\nThe reason why I like it is that I have different background colors in vim\r\n(dark) and terminal (light). If I stay inside vim I am not flushed with\r\nbright colors which is a annoying (and may be eyes tiring).\r\n\r\nBenefits: you get completion for system commands and system files.\r\n\r\nYou can use the expression register with Vim 7.3.686.  With an earlier version\r\nyou will not be able to use it.\r\n\r\n# Requirements\r\nYou have to also install [CRDispatcher](https:\/\/github.com\/coot\/CRDispatcher)\r\nplugin.\r\n\r\nI learned how to do that reading the\r\n[EmacsCommandLine Plugin](https:\/\/github.com\/houtsnip\/vim-emacscommandline).\r\n\r\nOther plugins with shell like functionality:\r\n* [vim-addon-async](https:\/\/github.com\/MarcWeber\/vim-addon-async)\r\n* [Conque Shell Plugin](http:\/\/code.google.com\/p\/conque)\r\n* [VimProc Plugin](http:\/\/github.com\/Shougo\/vimproc\/tree\/master\/doc\/vimproc.txt)\r\n\r\n## Copyright\r\n\u00c2\u00a9 Marcin Szamotulski, 2012-2014\r\n\r\n## License\r\nVim license, see :help license\r\n","install_details":"First install http:\/\/www.vim.org\/scripts\/script.php?script_id=4856 then put the vim script file in to your plugin folder.","5":"First install http:\/\/www.vim.org\/scripts\/script.php?script_id=4856 then put the vim script file in to your plugin folder.","first_name":"Marcin","6":"Marcin","last_name":"Szamotulski","7":"Szamotulski","releases":[{"0":"4224","vim_version":"7.3","1":"7.3","script_version":"5","2":"5","version_comment":"Updated version.  Please also update: http:\/\/www.vim.org\/scripts\/script.php?script_id=4856 .","3":"Updated version.  Please also update: http:\/\/www.vim.org\/scripts\/script.php?script_id=4856 .","package":"system.vim","4":"system.vim","src_id":"21552","5":"21552","creation_date":"1393666832","6":"1393666832"},{"0":"4224","vim_version":"7.0","1":"7.0","script_version":"4","2":"4","version_comment":"New version.  Also install: http:\/\/www.vim.org\/scripts\/script.php?script_id=4856 .","3":"New version.  Also install: http:\/\/www.vim.org\/scripts\/script.php?script_id=4856 .","package":"system.vim","4":"system.vim","src_id":"21441","5":"21441","creation_date":"1391766634","6":"1391766634"},{"0":"4224","vim_version":"7.3","1":"7.3","script_version":"3","2":"3","version_comment":"Update to make it work with my new plugin Enchanted Vim (persistent very magic option) http:\/\/www.vim.org\/scripts\/script.php?script_id=4849","3":"Update to make it work with my new plugin Enchanted Vim (persistent very magic option) http:\/\/www.vim.org\/scripts\/script.php?script_id=4849","package":"system.vim","4":"system.vim","src_id":"21417","5":"21417","creation_date":"1391347264","6":"1391347264"},{"0":"4224","vim_version":"7.0","1":"7.0","script_version":"2","2":"2","version_comment":"Handles command line history.","3":"Handles command line history.","package":"system.vim","4":"system.vim","src_id":"18655","5":"18655","creation_date":"1348301062","6":"1348301062"},{"0":"4224","vim_version":"7.0","1":"7.0","script_version":"1","2":"1","version_comment":"Initial upload","3":"Initial upload","package":"system.vim","4":"system.vim","src_id":"18653","5":"18653","creation_date":"1348259710","6":"1348259710"}]},"4223":{"script_id":"4223","0":"4223","script_name":"votl","1":"votl","script_type":"ftplugin","2":"ftplugin","summary":"A Vim Outliner","3":"A Vim Outliner","description":"\r\nvotl is an outline processor designed for super fast authoring. It was\r\noriginally forked from VimOutliner and features include tree expand and\r\ncollapse, tree promotion and demotion, sorting children, level sensitive\r\ncolors, checkboxes and completion percentages for todo lists, tags, quick\r\ntime and date entry, unformatted and formatted body text, tables, and\r\nsupport for calendar entries.\r\n\r\nThe file extension used by votl is .votl and remains compatible with the\r\nexisting .otl file format that VimOutliner uses.\r\n\r\nThe votl enhancements not found in VimOutliner are:\r\n\r\n - Cycle over folds under the current header with <Tab>.\r\n - Quickly jumping between sections with the [[ ]] { } keystrokes.\r\n - Better coloring and support for much finer grained syntax highlighting.\r\n - Support for daily diary\/journaling with a Calendar.\r\n - New support for tagging and the ability to quickly search for tags.\r\n   Formatted exactly like Emacs org-mode tags.\r\n - Support for RestructuredText formatted tables.\r\n - Code cleanup\/simplification and a better user experience.\r\n\r\nSource on github: https:\/\/github.com\/insanum\/votl\r\n","4":"\r\nvotl is an outline processor designed for super fast authoring. It was\r\noriginally forked from VimOutliner and features include tree expand and\r\ncollapse, tree promotion and demotion, sorting children, level sensitive\r\ncolors, checkboxes and completion percentages for todo lists, tags, quick\r\ntime and date entry, unformatted and formatted body text, tables, and\r\nsupport for calendar entries.\r\n\r\nThe file extension used by votl is .votl and remains compatible with the\r\nexisting .otl file format that VimOutliner uses.\r\n\r\nThe votl enhancements not found in VimOutliner are:\r\n\r\n - Cycle over folds under the current header with <Tab>.\r\n - Quickly jumping between sections with the [[ ]] { } keystrokes.\r\n - Better coloring and support for much finer grained syntax highlighting.\r\n - Support for daily diary\/journaling with a Calendar.\r\n - New support for tagging and the ability to quickly search for tags.\r\n   Formatted exactly like Emacs org-mode tags.\r\n - Support for RestructuredText formatted tables.\r\n - Code cleanup\/simplification and a better user experience.\r\n\r\nSource on github: https:\/\/github.com\/insanum\/votl\r\n","install_details":"","5":"","first_name":"Eric","6":"Eric","last_name":"Davis","7":"Davis","releases":[{"0":"4223","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"votl-0.1.zip","4":"votl-0.1.zip","src_id":"18651","5":"18651","creation_date":"1348258479","6":"1348258479"}]},"4222":{"script_id":"4222","0":"4222","script_name":"conque-repl.vim","1":"conque-repl.vim","script_type":"utility","2":"utility","summary":"Use vim as a command editor for REPL programs","3":"Use vim as a command editor for REPL programs","description":"  Vim ConqueShell Repl\r\n  \r\n  This plugin makes really easy sending input\/reading output from\r\nREPLs through vim. It has similar goals to the slime.vim plugin\r\nbut it doesn't need screen or tmux and works with gvim. Instead it \r\nit depends on the ConqueShell plugin(http:\/\/www.vim.org\/scripts\/script.php?script_id=2771), so vim must be compiled with python support.\r\n\r\nUsage\r\n\r\n  With the default configuration F5 and F6 are mapped\r\nrespectively, but only if they are not mapped yet. The mappings can be\r\ncustomized by setting g:conque_repl_send_key and g:conque_repl_send_buffer_key\r\nin your vimrc.\r\n        \r\n  The idea is that you have two buffers in split windows, one where you are\r\nediting commands, and another where conqueshell is running a repl for some\r\nlanguage(python, ruby, node.js, coffeescript...) or any other process that\r\naccepts commands interactively. So in the default setup:\r\n\r\n  - Hitting F5 in normal or insert mode will send the line under the cursor to \r\n    the repl.\r\n  - Hitting F5 in visual mode will send the selected text to the repl.\r\n \r\n  - Hitting F6 in normal or insert mode will send the entire buffer to the repl.\r\n\r\n  Unlike the default ConqueShell commands for sending text, these leave the\r\noriginal buffers focused and with text selected(in case of running in visual mode), transforming vim into a\r\nnice multi line command editor with syntax highlighting\/indentation.\r\n\r\n  This plugin works well with the scratch.vim plugin.","4":"  Vim ConqueShell Repl\r\n  \r\n  This plugin makes really easy sending input\/reading output from\r\nREPLs through vim. It has similar goals to the slime.vim plugin\r\nbut it doesn't need screen or tmux and works with gvim. Instead it \r\nit depends on the ConqueShell plugin(http:\/\/www.vim.org\/scripts\/script.php?script_id=2771), so vim must be compiled with python support.\r\n\r\nUsage\r\n\r\n  With the default configuration F5 and F6 are mapped\r\nrespectively, but only if they are not mapped yet. The mappings can be\r\ncustomized by setting g:conque_repl_send_key and g:conque_repl_send_buffer_key\r\nin your vimrc.\r\n        \r\n  The idea is that you have two buffers in split windows, one where you are\r\nediting commands, and another where conqueshell is running a repl for some\r\nlanguage(python, ruby, node.js, coffeescript...) or any other process that\r\naccepts commands interactively. So in the default setup:\r\n\r\n  - Hitting F5 in normal or insert mode will send the line under the cursor to \r\n    the repl.\r\n  - Hitting F5 in visual mode will send the selected text to the repl.\r\n \r\n  - Hitting F6 in normal or insert mode will send the entire buffer to the repl.\r\n\r\n  Unlike the default ConqueShell commands for sending text, these leave the\r\noriginal buffers focused and with text selected(in case of running in visual mode), transforming vim into a\r\nnice multi line command editor with syntax highlighting\/indentation.\r\n\r\n  This plugin works well with the scratch.vim plugin.","install_details":" If you are using Vundle add this to your vimrc:\r\n\r\nBundle 'tarruda\/vim-conque-shell'\r\nBundle 'tarruda\/vim-conque-repl'\r\n\r\n\r\n  Or copy vim-conque-repl.vim to the plugins directory.\r\n","5":" If you are using Vundle add this to your vimrc:\r\n\r\nBundle 'tarruda\/vim-conque-shell'\r\nBundle 'tarruda\/vim-conque-repl'\r\n\r\n\r\n  Or copy vim-conque-repl.vim to the plugins directory.\r\n","first_name":"Thiago","6":"Thiago","last_name":"Padilha","7":"Padilha","releases":[{"0":"4222","vim_version":"7.3","1":"7.3","script_version":"0.0.1","2":"0.0.1","version_comment":"Initial upload","3":"Initial upload","package":"vim-conque-repl.zip","4":"vim-conque-repl.zip","src_id":"18646","5":"18646","creation_date":"1348198560","6":"1348198560"}]},"4221":{"script_id":"4221","0":"4221","script_name":"localbundle.vim","1":"localbundle.vim","script_type":"utility","2":"utility","summary":"  faster loading and working speed with vundle","3":"  faster loading and working speed with vundle","description":"This is a vim plugin for the Vundle_ users.\r\nseperated from my previous forked vundle repo to a single plugin.\r\n\r\nIt will copy all file of the bundles in ~\/.vim\/bundle\/ into ~\/.vim\/localbundle\/\r\n\r\nand remove runtimepath of these bundles. \r\nand add  ~\/.vim\/localbundle\/ to &rtp.\r\n\r\nThis will greatly increasing the loading and working speed with\r\na big numbers of bundles.\r\n\r\n* Command:\r\n\r\n  ``:LocalBundle``\r\n\r\n  This will copy all bundles in ~\/.vim\/bundle\/ into ~\/.vim\/localbundle\/\r\n  \r\n  Also it will reset the &rtp, and will generate the help tag file.\r\n\r\n","4":"This is a vim plugin for the Vundle_ users.\r\nseperated from my previous forked vundle repo to a single plugin.\r\n\r\nIt will copy all file of the bundles in ~\/.vim\/bundle\/ into ~\/.vim\/localbundle\/\r\n\r\nand remove runtimepath of these bundles. \r\nand add  ~\/.vim\/localbundle\/ to &rtp.\r\n\r\nThis will greatly increasing the loading and working speed with\r\na big numbers of bundles.\r\n\r\n* Command:\r\n\r\n  ``:LocalBundle``\r\n\r\n  This will copy all bundles in ~\/.vim\/bundle\/ into ~\/.vim\/localbundle\/\r\n  \r\n  Also it will reset the &rtp, and will generate the help tag file.\r\n\r\n","install_details":"* Install and Useage\r\n\r\n  Use it with Vundle_.\r\n  Put this in your vimrc, \r\n  should be put at the end of your Bundle part::\r\n      \r\n      Bundle 'Rykka\/localbundle.vim'\r\n\r\n      call localbundle#init()\r\n\r\n  ``g:localbundle_rtp`` can be used to add another &rtp if needed.\r\n\r\n  You can get the latest version at LocalBundle_\r\n\r\n:NOTE: you should NOT install from vim.org.\r\n            use Vundle_!\r\n\r\n.. _Vundle: http:\/\/github.com\/gmarik\/vundle\r\n.. _LocalBundle: https:\/\/github.com\/Rykka\/localbundle.vim\r\n","5":"* Install and Useage\r\n\r\n  Use it with Vundle_.\r\n  Put this in your vimrc, \r\n  should be put at the end of your Bundle part::\r\n      \r\n      Bundle 'Rykka\/localbundle.vim'\r\n\r\n      call localbundle#init()\r\n\r\n  ``g:localbundle_rtp`` can be used to add another &rtp if needed.\r\n\r\n  You can get the latest version at LocalBundle_\r\n\r\n:NOTE: you should NOT install from vim.org.\r\n            use Vundle_!\r\n\r\n.. _Vundle: http:\/\/github.com\/gmarik\/vundle\r\n.. _LocalBundle: https:\/\/github.com\/Rykka\/localbundle.vim\r\n","first_name":"Rykka","6":"Rykka","last_name":"f","7":"f","releases":[{"0":"4221","vim_version":"7.0","1":"7.0","script_version":"0.5","2":"0.5","version_comment":"Initial upload","3":"Initial upload","package":"localbundle.vim-0.5.zip","4":"localbundle.vim-0.5.zip","src_id":"18639","5":"18639","creation_date":"1348064589","6":"1348064589"}]},"4220":{"script_id":"4220","0":"4220","script_name":"cospe.vim","1":"cospe.vim","script_type":"utility","2":"utility","summary":"Script to send your buffer or selection to http:\/\/cos.pe and returns a url","3":"Script to send your buffer or selection to http:\/\/cos.pe and returns a url","description":"cospe.vim is a vim plugin for pasting to http:\/\/cos.pe\r\n\r\nThis script is a copy of dpaste.vim but paste into cos.pe instead dpaste.com\r\n\r\nThanks to Alexandre Fiori for creating cos.pe and Bartek Ciszkowski Maintainer of dpaste.vim. \r\n\r\nUsage: \r\n- :Cospe  (create a paste from the current buffer or selection) \r\n\r\nYou can also map paste to CTRL + P, just add this to your .vimrc: \r\nmap ^P :Dpaste<CR> \r\n(where ^P is entered using CTRL + V, CTRL + P in Vim) ","4":"cospe.vim is a vim plugin for pasting to http:\/\/cos.pe\r\n\r\nThis script is a copy of dpaste.vim but paste into cos.pe instead dpaste.com\r\n\r\nThanks to Alexandre Fiori for creating cos.pe and Bartek Ciszkowski Maintainer of dpaste.vim. \r\n\r\nUsage: \r\n- :Cospe  (create a paste from the current buffer or selection) \r\n\r\nYou can also map paste to CTRL + P, just add this to your .vimrc: \r\nmap ^P :Dpaste<CR> \r\n(where ^P is entered using CTRL + V, CTRL + P in Vim) ","install_details":"Put cospe.vim file in ~\/.vim\/plugin directory","5":"Put cospe.vim file in ~\/.vim\/plugin directory","first_name":"Felippe","6":"Felippe","last_name":"Bueno","7":"Bueno","releases":[{"0":"4220","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"updated vim version required.","3":"updated vim version required.","package":"cospe.vim","4":"cospe.vim","src_id":"18636","5":"18636","creation_date":"1347981161","6":"1347981161"}]},"4219":{"script_id":"4219","0":"4219","script_name":"mkvimball.vim","1":"mkvimball.vim","script_type":"utility","2":"utility","summary":"Create a vimball from a list of input files","3":"Create a vimball from a list of input files","description":"This script is intended for plugin developers.\r\n\r\nVimball archives (or .vmb \/ .vba, see vimscript #1502 for Vimball plugin) are a good way to distribute your plugin to users. They help users with plugin installation, in that users no longer need to know their runtime directory, to unpack a .zip file in there. With a vimball the plugin installation happens entirely within Vim, and all a user has to do is open the vimball file and follow the simple instruction that shows up, of executing \":source %\".\r\n\r\nThey also help with plugin un-installation, when users normally need to find plugin files to be deleted, but with a vimball users can invoke one :RmVimball command\r\n\r\nThe `mkvimball` Vim script will create a vimball for your plugin from a list of input files. The files can be specified on the command line, in an environment variable, or read from the standard input. Although the script can be installed in the user runtime directory, like any vimball, it is intended primarily for use from the command line, or from a Makefile that you use with your plugin source files. So you might want to install it in your project directory, next to the Makefile or the other build files. You can also run the script with the :runtime or :source command from Vim, if you set :args beforehand the same as on the command line.\r\n\r\nThe source code repository for the project is available at http:\/\/code.google.com\/p\/dbgp-client\/.\r\n\r\nTo run on the command line, you would need a command like:\r\n        vim -V1 -i NONE -u NORC -nNesS mkvimball -c \"echo ''|qall\"! -- VimballName srcfiles...\r\n\r\nOn Linux the script uses a shebang line equivalent to the above command, so if you make the script executable, with `chmod +x mkvimball`, you can run the script as follows:\r\n        .\/mkvimball -- VimballName srcfiles ....\r\n\r\nOn Windows there is no equivalent to the shebang line, and also Vim is not necessarily on PATH, which can make things a little complicated.\r\n\r\nNormally the Windows file associations are used for such purpose. You can follow the wiki page at http:\/\/vim.wikia.com\/wiki\/Windows_file_associations, and associate a new file extension like .exim to the above command line. Here 'exim' stands for \"improved ex mode', and sometimes Vim was also installed with the name `exim`, in addition to the name `vim`. The mkvimball script itself can register\/unregister the a file extension, for the current user or all users, with the following command:\r\n       vim -i NONE -V1 -nNesS mkvimball -c \"echo ''|qall\"! -- --register-file-type     { --user | --system } [.ext]\r\n       vim -i NONE -V1 -nNesS mkvimabll -c \"echo ''|qall\"! -- --unregister-file-type { --user | --system } [.ext]\r\nYou only need to register the file type once. The default file extension [.ext] is \".exim\". After that you should rename mkvimball file to mkvimball.exim, exit current cmd.exe window, and use the `mkvimball` command normally.\r\n\r\nHowever the Windows file associations are specific to the computer where they are configured, and Vim plugins on the other hand are public-domain or open-source and shared with any one who would like to get the source code to build a vimball. To use `mkvimball` with such a public audience you can use a wrapper .cmd file to invoke the full command line. The `mkvimball` script can generate a pair of such wrappers (.cmd and .js, where .js is a JScript file running with Windows Script Host WSH, and is invoked from the .cmd file), if you run it once with this command:\r\n       vim -i NONE -V1 -nNesS mkvimball -c \"echo ''|qall\"! -- --write-cmd-script\r\nthan you can use the `mkvimball` command normally.\r\n\r\nThe generated scripts \/ file association can read the Windows registry to find Vim installation directory, or search for Vim in %ProgramFiles% or %VIMRUNTIME%.\r\n\r\nOne last note about the installation: if your project uses php and you know it can be found on path, you can run the script with php, since it is a valid php file as it stands. Just use `php mkvimball VimballName scrfiles...`. Funny (or lucky), but it works, and it makes for an interesting observation ...\r\n\r\nNext, the script relies on the standard vimballPlugin to create or list the vimball archive. The script will normally set g:vimball_home to the current directory given as '.'. If the vimball to be created already exists, it will be overwritten.\r\n\r\nThe names of files from the command line, that are found in or below the current directory, will be re-written to be relative to the current directory (as if with expand('%:.'). Nothing special about it, this is done mostly to fix some attempts by Vim to match a file name argument (from command line) with an existing buffer name upon start-up, when Vim may modify the file name arg for this purpose. But it is also a good sanity check.\r\n\r\nTo remove some parent directory component from all input file names given, set the environment variable SRC_PATH_PREFIX to the prefix to be removed. Or set g:mkvimball_src_path_prefix variable on the command line before running the script, like:\r\n         mkvimball --cmd 'let g:mkvimball_src_path_prefix=\"src\/\"' -- Vimball srcfiles...\r\nNote that the `mkvimball` script will not read the .vimrc file, so you can not specify the variable in there.\r\n\r\nTo prevent implicit file name modification you can specify the list of files as standard input to the command, like\r\n         VIMBALL_FILES=- mkvimball -- VimballName <listfile.txt\r\nor in the VIMBALL_FILES environment variable, like\r\n         VIMBALL_FILES=\"plugin\/file1.vim plugin\/file2.vim\" mkvimball -- VimballName\r\nThe script will split the list into files around spaces in this case, or with the Vim regular expression given in g:mkvimball_delimiter_regexp variable.\r\n\r\nTo read the list of input files from standad input, set VIMBALL_FILES to the value \"-\" (a single dash), or for Linux systems you may also set it empty (Windows does not have empty environment variables). You should also make sure standard input ends with an empty line or with a line containing just a single dot. If the end-of-file is reached without an empty line or a dot line, Vim will stop script execution when that happens, before it can create the vimball. This is because the command line invoking the script will run Vim in ex mode (command mode) which reads Vim commands from standard input.\r\n\r\nIf you just pass a vimball file as the single argument to the script, you will get a listing of the vimball archive contents, created with :VimballList command provided by the standard vimball plugin.\r\n\r\nInstead of running the script from the command line, you may use :source or :runtime command in a running instance of Vim, and be sure to set script arguments with the :args command as a first step. If you want to list a vimball archive in this way, you may need to use the :messages command afterwards, like this:\r\n          :arglocal\r\n          :argdelete *\r\n          :argadd VimballFileName.vba\r\n          :runtime mkvimball\r\n          :messages\r\n          :argglobal","4":"This script is intended for plugin developers.\r\n\r\nVimball archives (or .vmb \/ .vba, see vimscript #1502 for Vimball plugin) are a good way to distribute your plugin to users. They help users with plugin installation, in that users no longer need to know their runtime directory, to unpack a .zip file in there. With a vimball the plugin installation happens entirely within Vim, and all a user has to do is open the vimball file and follow the simple instruction that shows up, of executing \":source %\".\r\n\r\nThey also help with plugin un-installation, when users normally need to find plugin files to be deleted, but with a vimball users can invoke one :RmVimball command\r\n\r\nThe `mkvimball` Vim script will create a vimball for your plugin from a list of input files. The files can be specified on the command line, in an environment variable, or read from the standard input. Although the script can be installed in the user runtime directory, like any vimball, it is intended primarily for use from the command line, or from a Makefile that you use with your plugin source files. So you might want to install it in your project directory, next to the Makefile or the other build files. You can also run the script with the :runtime or :source command from Vim, if you set :args beforehand the same as on the command line.\r\n\r\nThe source code repository for the project is available at http:\/\/code.google.com\/p\/dbgp-client\/.\r\n\r\nTo run on the command line, you would need a command like:\r\n        vim -V1 -i NONE -u NORC -nNesS mkvimball -c \"echo ''|qall\"! -- VimballName srcfiles...\r\n\r\nOn Linux the script uses a shebang line equivalent to the above command, so if you make the script executable, with `chmod +x mkvimball`, you can run the script as follows:\r\n        .\/mkvimball -- VimballName srcfiles ....\r\n\r\nOn Windows there is no equivalent to the shebang line, and also Vim is not necessarily on PATH, which can make things a little complicated.\r\n\r\nNormally the Windows file associations are used for such purpose. You can follow the wiki page at http:\/\/vim.wikia.com\/wiki\/Windows_file_associations, and associate a new file extension like .exim to the above command line. Here 'exim' stands for \"improved ex mode', and sometimes Vim was also installed with the name `exim`, in addition to the name `vim`. The mkvimball script itself can register\/unregister the a file extension, for the current user or all users, with the following command:\r\n       vim -i NONE -V1 -nNesS mkvimball -c \"echo ''|qall\"! -- --register-file-type     { --user | --system } [.ext]\r\n       vim -i NONE -V1 -nNesS mkvimabll -c \"echo ''|qall\"! -- --unregister-file-type { --user | --system } [.ext]\r\nYou only need to register the file type once. The default file extension [.ext] is \".exim\". After that you should rename mkvimball file to mkvimball.exim, exit current cmd.exe window, and use the `mkvimball` command normally.\r\n\r\nHowever the Windows file associations are specific to the computer where they are configured, and Vim plugins on the other hand are public-domain or open-source and shared with any one who would like to get the source code to build a vimball. To use `mkvimball` with such a public audience you can use a wrapper .cmd file to invoke the full command line. The `mkvimball` script can generate a pair of such wrappers (.cmd and .js, where .js is a JScript file running with Windows Script Host WSH, and is invoked from the .cmd file), if you run it once with this command:\r\n       vim -i NONE -V1 -nNesS mkvimball -c \"echo ''|qall\"! -- --write-cmd-script\r\nthan you can use the `mkvimball` command normally.\r\n\r\nThe generated scripts \/ file association can read the Windows registry to find Vim installation directory, or search for Vim in %ProgramFiles% or %VIMRUNTIME%.\r\n\r\nOne last note about the installation: if your project uses php and you know it can be found on path, you can run the script with php, since it is a valid php file as it stands. Just use `php mkvimball VimballName scrfiles...`. Funny (or lucky), but it works, and it makes for an interesting observation ...\r\n\r\nNext, the script relies on the standard vimballPlugin to create or list the vimball archive. The script will normally set g:vimball_home to the current directory given as '.'. If the vimball to be created already exists, it will be overwritten.\r\n\r\nThe names of files from the command line, that are found in or below the current directory, will be re-written to be relative to the current directory (as if with expand('%:.'). Nothing special about it, this is done mostly to fix some attempts by Vim to match a file name argument (from command line) with an existing buffer name upon start-up, when Vim may modify the file name arg for this purpose. But it is also a good sanity check.\r\n\r\nTo remove some parent directory component from all input file names given, set the environment variable SRC_PATH_PREFIX to the prefix to be removed. Or set g:mkvimball_src_path_prefix variable on the command line before running the script, like:\r\n         mkvimball --cmd 'let g:mkvimball_src_path_prefix=\"src\/\"' -- Vimball srcfiles...\r\nNote that the `mkvimball` script will not read the .vimrc file, so you can not specify the variable in there.\r\n\r\nTo prevent implicit file name modification you can specify the list of files as standard input to the command, like\r\n         VIMBALL_FILES=- mkvimball -- VimballName <listfile.txt\r\nor in the VIMBALL_FILES environment variable, like\r\n         VIMBALL_FILES=\"plugin\/file1.vim plugin\/file2.vim\" mkvimball -- VimballName\r\nThe script will split the list into files around spaces in this case, or with the Vim regular expression given in g:mkvimball_delimiter_regexp variable.\r\n\r\nTo read the list of input files from standad input, set VIMBALL_FILES to the value \"-\" (a single dash), or for Linux systems you may also set it empty (Windows does not have empty environment variables). You should also make sure standard input ends with an empty line or with a line containing just a single dot. If the end-of-file is reached without an empty line or a dot line, Vim will stop script execution when that happens, before it can create the vimball. This is because the command line invoking the script will run Vim in ex mode (command mode) which reads Vim commands from standard input.\r\n\r\nIf you just pass a vimball file as the single argument to the script, you will get a listing of the vimball archive contents, created with :VimballList command provided by the standard vimball plugin.\r\n\r\nInstead of running the script from the command line, you may use :source or :runtime command in a running instance of Vim, and be sure to set script arguments with the :args command as a first step. If you want to list a vimball archive in this way, you may need to use the :messages command afterwards, like this:\r\n          :arglocal\r\n          :argdelete *\r\n          :argadd VimballFileName.vba\r\n          :runtime mkvimball\r\n          :messages\r\n          :argglobal","install_details":"Open the downloaded .vba file in Vim. Vim will show a status line saying you should use \":so %\" command to install the vimball.\r\nIf you downloaded the .zip file, Vim can usually open it directly, so you do not have to unpack it first.\r\n\r\nNext you may want to cd to the directory where you want the mkvimball script installed, for example in your project directory. Than you should type\r\n               :cd ..your-project-dir...\r\n               :let g:vimball_home='.'\r\n               :source %\r\nto unpack the script into that directory.\r\n\r\nOtherwise, only run `:so %` and the script will be placed by default in your Vim runtime directory, usually ~\/.vim\/ on Linux, and  %USERPROFILE%\\vimfiles\\ on Windows.\r\n\r\nAs the next step, you should now to the following:\r\n   - Linux: run `chmod +x ~\/.vim\/mkvimball`\r\n   - Windows: create a file type association or generate a wrapper script, as described above.","5":"Open the downloaded .vba file in Vim. Vim will show a status line saying you should use \":so %\" command to install the vimball.\r\nIf you downloaded the .zip file, Vim can usually open it directly, so you do not have to unpack it first.\r\n\r\nNext you may want to cd to the directory where you want the mkvimball script installed, for example in your project directory. Than you should type\r\n               :cd ..your-project-dir...\r\n               :let g:vimball_home='.'\r\n               :source %\r\nto unpack the script into that directory.\r\n\r\nOtherwise, only run `:so %` and the script will be placed by default in your Vim runtime directory, usually ~\/.vim\/ on Linux, and  %USERPROFILE%\\vimfiles\\ on Windows.\r\n\r\nAs the next step, you should now to the following:\r\n   - Linux: run `chmod +x ~\/.vim\/mkvimball`\r\n   - Windows: create a file type association or generate a wrapper script, as described above.","first_name":"Timothy","6":"Timothy","last_name":"Madden","7":"Madden","releases":[{"0":"4219","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Added command line options for Windows file type registration and\/or wrapper script creation.\r\nChanged script name from mkvimball.vim to mkvimball.","3":"Added command line options for Windows file type registration and\/or wrapper script creation.\r\nChanged script name from mkvimball.vim to mkvimball.","package":"mkvimball.vba","4":"mkvimball.vba","src_id":"18945","5":"18945","creation_date":"1352047494","6":"1352047494"},{"0":"4219","vim_version":"7.2","1":"7.2","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"mkvimball.vba.zip","4":"mkvimball.vba.zip","src_id":"18634","5":"18634","creation_date":"1347922509","6":"1347922509"}]},"4218":{"script_id":"4218","0":"4218","script_name":"vim2grace","1":"vim2grace","script_type":"utility","2":"utility","summary":"Grace\/Common Music integration","3":"Grace\/Common Music integration","description":"This program provides a very simple way to pass blocks of source code from\r\nwithin vim (or other external editor) to Grace\/Common Music for automatic\r\nexecution.\r\n\r\nThe program should be able to work without modification for any editor,\r\nnot just vim.  All your editor has to do is write the blocks of source\r\ncode you want to send to Grace to a fifo (which is just like writing\r\nto a regular file, so every editor should be capable of doing this).\r\n\r\nThis program has only undergone very minimal testing, and the\r\ntesting was done only on Linux with Grace 3.8.0 from svn.\r\nUSE AT YOUR OWN RISK.\r\n\r\nThe program does nothing fancy.  It just uses a fifo for one-directional\r\ncommunication from vim to Grace.  That means that no results or errors\r\nare passed from Grace back to vim.  To see any results or errors, you will\r\nhave to look at the Grace screen.\r\n\r\nMore information on Grace\/Common Music can be found here:\r\n\r\n  http:\/\/commonmusic.sourceforge.net\/\r\n\r\nUSAGE:\r\n\r\nHere's how you could use vim2grace, should you choose to:\r\n\r\n - First, download vim2grace.scm from the link at the bottom of this page.\r\n\r\n - Second, if you want to change the default location of the fifo,\r\n   change the \"vim2grace-fifo\" variable near the top of vim2grace.scm,\r\n   or set a VIM2GRACE_FIFO environment variable, which will override\r\n   the hardcoded variable in the source.\r\n\r\n   NOTE:  Because ANY scheme source code written to this fifo will be\r\n          automatically executed, you should keep this file under your control\r\n          and only writeable by you! I recommend keeping it somewhere in your\r\n          home directory and making sure your home directory is \"chmod 700\"\r\n          (ie.  only readable, executable, and writeable by you).\r\n\r\n - Third, start Grace and use the \"File->Load File...\" menu option to\r\n   load and run vim2grace.scm\r\n\r\n   Now Grace is in an infinite loop, waiting to read data from the fifo.\r\n   When it manages to read in an entire file from the fifo (up to the EOF),\r\n   it will assume what it read was Scheme source code and run it,\r\n   printing any errors, and then try to read another file's worth of data\r\n   from the fifo, etc..\r\n\r\n - Fourth, in your ~\/.vimrc you can (for example), create some key bindings\r\n   like the following:\r\n\r\n    :nnoremap <F3> vip:w>> ~\/.vim2grace-fifo<CR>\r\n    :vnoremap <F4> :w>> ~\/.vim2grace-fifo<CR>\r\n\r\n - Fifth, now type a block of Scheme source code in to vim, place your cursor\r\n   somewhere within the block and hit F3 and your code should be passed\r\n   to Grace via the fifo.  Alternatively, you can select some code in\r\n   visual block mode and hit F4 to do the same.  Of course, you're free to\r\n   map any other keys, not just F3 and F4.\r\n\r\nTROUBLESHOOTING:\r\n\r\n  Problem:  You just made your editor write some code to the fifo and\r\n            your editor is stuck at a blank screen.\r\n\r\n  Solution: This probably means that nothing is reading from the fifo.\r\n            Make sure Grace has started, and is running vim2grace.scm\r\n\r\n            If this does not help, you could always at least un-hang your\r\n            editor by typing the following in your shell:\r\n\r\n               cat ~\/.vim2grace-fifo\r\n\r\n            (or whatever the path is to the fifo you had your editor use).\r\n\r\n  Problem:  Using vim2grace to pass an expression like (+ 1 1) that\r\n            usually prints something when typed directly in to the Grace\r\n            editor prints nothing.\r\n\r\n  Solution: When you execute blocks of code from the Grace editor,\r\n            it runs them using (eval), which prints the value of the\r\n            expression it evaluates.  Instead of (eval), vim2grace\r\n            uses (load), which does not print the values of the expressions\r\n            it evaluates.  To see their values, try explicitly wrapping your\r\n            expression in a print statement, like: (print (+ 1 1))\r\n            Future versions of vim2grace might use (eval) too.\r\n\r\n  Problem:  There's a bug in the code you passed from vim to Grace, and Grace\r\n            is stuck in an infinite loop or you have some other reason for\r\n            wanting to interrupt Grace.\r\n\r\n  Solution: The easiest thing is to just quit Grace (or kill it using the\r\n            unix\/linux \"kill\" command).\r\n\r\n            As an alternative, instead of loading vim2grace.scm directly\r\n            in to Grace, you could try loading it in Grace's editor using\r\n            the \"File->Open...\" menu option, select the entire source code\r\n            and select the \"Eval->Execute\" menu option from within\r\n            the Grace editor.\r\n\r\n            Then, if you need to interrupt Grace for any reason, you\r\n            could use the \"Eval->Interrupt Scheme\" menu option.\r\n\r\n  Problem:  Calls to procedures like (mp:receive) that are supposed to do\r\n            some background processing don't work.\r\n\r\n  Solution: Unfortunately, there is no solution for this problem right now,\r\n            and it's not exactly clear why it's happening.  However, my guess\r\n            is that it's a consequence of relying on reading from a fifo, which\r\n            blocks all processing until more data is ready to be read from the\r\n            fifo.  I'm guessing that no background processing can be done while\r\n            Grace is blocked.  Perhaps a future version of vim2grep will use\r\n            some non-blocking or threaded means of communication, which should\r\n            hopefully fix the problem.\r\n","4":"This program provides a very simple way to pass blocks of source code from\r\nwithin vim (or other external editor) to Grace\/Common Music for automatic\r\nexecution.\r\n\r\nThe program should be able to work without modification for any editor,\r\nnot just vim.  All your editor has to do is write the blocks of source\r\ncode you want to send to Grace to a fifo (which is just like writing\r\nto a regular file, so every editor should be capable of doing this).\r\n\r\nThis program has only undergone very minimal testing, and the\r\ntesting was done only on Linux with Grace 3.8.0 from svn.\r\nUSE AT YOUR OWN RISK.\r\n\r\nThe program does nothing fancy.  It just uses a fifo for one-directional\r\ncommunication from vim to Grace.  That means that no results or errors\r\nare passed from Grace back to vim.  To see any results or errors, you will\r\nhave to look at the Grace screen.\r\n\r\nMore information on Grace\/Common Music can be found here:\r\n\r\n  http:\/\/commonmusic.sourceforge.net\/\r\n\r\nUSAGE:\r\n\r\nHere's how you could use vim2grace, should you choose to:\r\n\r\n - First, download vim2grace.scm from the link at the bottom of this page.\r\n\r\n - Second, if you want to change the default location of the fifo,\r\n   change the \"vim2grace-fifo\" variable near the top of vim2grace.scm,\r\n   or set a VIM2GRACE_FIFO environment variable, which will override\r\n   the hardcoded variable in the source.\r\n\r\n   NOTE:  Because ANY scheme source code written to this fifo will be\r\n          automatically executed, you should keep this file under your control\r\n          and only writeable by you! I recommend keeping it somewhere in your\r\n          home directory and making sure your home directory is \"chmod 700\"\r\n          (ie.  only readable, executable, and writeable by you).\r\n\r\n - Third, start Grace and use the \"File->Load File...\" menu option to\r\n   load and run vim2grace.scm\r\n\r\n   Now Grace is in an infinite loop, waiting to read data from the fifo.\r\n   When it manages to read in an entire file from the fifo (up to the EOF),\r\n   it will assume what it read was Scheme source code and run it,\r\n   printing any errors, and then try to read another file's worth of data\r\n   from the fifo, etc..\r\n\r\n - Fourth, in your ~\/.vimrc you can (for example), create some key bindings\r\n   like the following:\r\n\r\n    :nnoremap <F3> vip:w>> ~\/.vim2grace-fifo<CR>\r\n    :vnoremap <F4> :w>> ~\/.vim2grace-fifo<CR>\r\n\r\n - Fifth, now type a block of Scheme source code in to vim, place your cursor\r\n   somewhere within the block and hit F3 and your code should be passed\r\n   to Grace via the fifo.  Alternatively, you can select some code in\r\n   visual block mode and hit F4 to do the same.  Of course, you're free to\r\n   map any other keys, not just F3 and F4.\r\n\r\nTROUBLESHOOTING:\r\n\r\n  Problem:  You just made your editor write some code to the fifo and\r\n            your editor is stuck at a blank screen.\r\n\r\n  Solution: This probably means that nothing is reading from the fifo.\r\n            Make sure Grace has started, and is running vim2grace.scm\r\n\r\n            If this does not help, you could always at least un-hang your\r\n            editor by typing the following in your shell:\r\n\r\n               cat ~\/.vim2grace-fifo\r\n\r\n            (or whatever the path is to the fifo you had your editor use).\r\n\r\n  Problem:  Using vim2grace to pass an expression like (+ 1 1) that\r\n            usually prints something when typed directly in to the Grace\r\n            editor prints nothing.\r\n\r\n  Solution: When you execute blocks of code from the Grace editor,\r\n            it runs them using (eval), which prints the value of the\r\n            expression it evaluates.  Instead of (eval), vim2grace\r\n            uses (load), which does not print the values of the expressions\r\n            it evaluates.  To see their values, try explicitly wrapping your\r\n            expression in a print statement, like: (print (+ 1 1))\r\n            Future versions of vim2grace might use (eval) too.\r\n\r\n  Problem:  There's a bug in the code you passed from vim to Grace, and Grace\r\n            is stuck in an infinite loop or you have some other reason for\r\n            wanting to interrupt Grace.\r\n\r\n  Solution: The easiest thing is to just quit Grace (or kill it using the\r\n            unix\/linux \"kill\" command).\r\n\r\n            As an alternative, instead of loading vim2grace.scm directly\r\n            in to Grace, you could try loading it in Grace's editor using\r\n            the \"File->Open...\" menu option, select the entire source code\r\n            and select the \"Eval->Execute\" menu option from within\r\n            the Grace editor.\r\n\r\n            Then, if you need to interrupt Grace for any reason, you\r\n            could use the \"Eval->Interrupt Scheme\" menu option.\r\n\r\n  Problem:  Calls to procedures like (mp:receive) that are supposed to do\r\n            some background processing don't work.\r\n\r\n  Solution: Unfortunately, there is no solution for this problem right now,\r\n            and it's not exactly clear why it's happening.  However, my guess\r\n            is that it's a consequence of relying on reading from a fifo, which\r\n            blocks all processing until more data is ready to be read from the\r\n            fifo.  I'm guessing that no background processing can be done while\r\n            Grace is blocked.  Perhaps a future version of vim2grep will use\r\n            some non-blocking or threaded means of communication, which should\r\n            hopefully fix the problem.\r\n","install_details":"","5":"","first_name":"Gnosis","6":"Gnosis","last_name":"Ouroubouros","7":"Ouroubouros","releases":[{"0":"4218","vim_version":"5.7","1":"5.7","script_version":"0.2","2":"0.2","version_comment":"Now printing a message informing the user of which fifo the program is reading from.","3":"Now printing a message informing the user of which fifo the program is reading from.","package":"vim2grace.scm","4":"vim2grace.scm","src_id":"18631","5":"18631","creation_date":"1347891726","6":"1347891726"},{"0":"4218","vim_version":"5.7","1":"5.7","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"vim2grace.scm","4":"vim2grace.scm","src_id":"18630","5":"18630","creation_date":"1347824605","6":"1347824605"}]},"4217":{"script_id":"4217","0":"4217","script_name":"layoutManager","1":"layoutManager","script_type":"utility","2":"utility","summary":"Create layouts from tabs, templates and windows and control them.","3":"Create layouts from tabs, templates and windows and control them.","description":"See latest version on github: https:\/\/github.com\/viaa\/VimPlugins\r\n\r\n\"===========================================\r\n\" LayoutManager plugin\r\n\"===========================================\r\n\r\n\" Version 1.0.2\r\n\"\r\n\" LayoutManager.vim allows to create layouts composed named of tabs and windows and do operations on these tabs and windows. The main idea is that tabs and windows are given names, for example, a window named \"menu\" could contain a menu file, another window called \"code\" could contain the code file, another one named \"output\" could contain the compiler's output text etc. The goal was to have a multiple windows environment similar to an IDE environment like visual studio for examples with windows and tabs with names that do different things, and were content may be \"sent\" to specific windows using commands, links (utl), mappings and especially from other script files and project files etc.\r\n\" \r\n\" In the zip file, I put in the example of a project file (.vim) I am currently doing that will be using the layoutManager.vim plugin. It is not finished but you are free to look at it to see how to use the plugin.\r\n\" \r\n\" I tried to use an object programming style in vimscript because I thought it was suitable for this type of application.\r\n\" \r\n\" Here is an example of utilisation of layoutManager.vim:\r\n\" \r\n\" \" Create a new layout\r\n\" let myLayout1 = g:lmLayout.New('MyLayout1')\r\n\" \r\n\" \" Add tabs to the layout\r\n\" call myLayout1.Tabs.Add(g:lmTab.New('MyTab1', 'MyTemplate1'))\r\n\" call myLayout1.Tabs.Add(g:lmTab.New('MyTab2', 'MyTemplate2'))\r\n\" \r\n\" \" Send commands to some of the windows of MyTab1\r\n\" call myLayout1.Tabs.MyTab1.Windows.code.Execute('e ' . $VIM . '\/vimrc') \" Show the vimrc file in the code window\r\n\" call myLayout1.Tabs.MyTab1.Windows.output.Write(\"this is the output window 1!\", 3) \" Write text in the output window\r\n\" call myLayout1.Tabs.MyTab1.Windows.files.ExecuteShell('dir c:') \" List a directory in the files window\r\n\" call myLayout1.Tabs.MyTab1.Windows.code.SetFocus()\r\n\" \r\n\" \" Send commands to some of the windows of MyTab2\r\n\" call myLayout1.Tabs.MyTab2.Windows.menu.Write(\"this is the menu!\", 3) \" Write text in the menu window\r\n\" call myLayout1.Tabs.MyTab2.Windows.code2.Execute('e ' . $VIM . '\/vimrc') \" Show the vimrc file in the code2 window\r\n\" \r\n\" let myLayout2 = s:layout.New('MyLayout2')\r\n\" \r\n\" \" Set focus to MyTab1\r\n\" call myLayout1.Tabs.MyTab1.SetFocus()\r\n\" \r\n\" Note that I didn't finish the examples or the documentation, but the plugin is working fine with these initial features. Feel free to propose any features or to send comments.\r\n\r\n\" See sample project file included in the zip file\r\n\r\n\" Todo: \r\n\" Remove tabs and windows from the containers, at the same time from the editor\r\n\" Ajouter une fonction pour aller directement a une fenetre style gt 1 gt 5 pour les tabs mais pour une fenetre\r\n","4":"See latest version on github: https:\/\/github.com\/viaa\/VimPlugins\r\n\r\n\"===========================================\r\n\" LayoutManager plugin\r\n\"===========================================\r\n\r\n\" Version 1.0.2\r\n\"\r\n\" LayoutManager.vim allows to create layouts composed named of tabs and windows and do operations on these tabs and windows. The main idea is that tabs and windows are given names, for example, a window named \"menu\" could contain a menu file, another window called \"code\" could contain the code file, another one named \"output\" could contain the compiler's output text etc. The goal was to have a multiple windows environment similar to an IDE environment like visual studio for examples with windows and tabs with names that do different things, and were content may be \"sent\" to specific windows using commands, links (utl), mappings and especially from other script files and project files etc.\r\n\" \r\n\" In the zip file, I put in the example of a project file (.vim) I am currently doing that will be using the layoutManager.vim plugin. It is not finished but you are free to look at it to see how to use the plugin.\r\n\" \r\n\" I tried to use an object programming style in vimscript because I thought it was suitable for this type of application.\r\n\" \r\n\" Here is an example of utilisation of layoutManager.vim:\r\n\" \r\n\" \" Create a new layout\r\n\" let myLayout1 = g:lmLayout.New('MyLayout1')\r\n\" \r\n\" \" Add tabs to the layout\r\n\" call myLayout1.Tabs.Add(g:lmTab.New('MyTab1', 'MyTemplate1'))\r\n\" call myLayout1.Tabs.Add(g:lmTab.New('MyTab2', 'MyTemplate2'))\r\n\" \r\n\" \" Send commands to some of the windows of MyTab1\r\n\" call myLayout1.Tabs.MyTab1.Windows.code.Execute('e ' . $VIM . '\/vimrc') \" Show the vimrc file in the code window\r\n\" call myLayout1.Tabs.MyTab1.Windows.output.Write(\"this is the output window 1!\", 3) \" Write text in the output window\r\n\" call myLayout1.Tabs.MyTab1.Windows.files.ExecuteShell('dir c:') \" List a directory in the files window\r\n\" call myLayout1.Tabs.MyTab1.Windows.code.SetFocus()\r\n\" \r\n\" \" Send commands to some of the windows of MyTab2\r\n\" call myLayout1.Tabs.MyTab2.Windows.menu.Write(\"this is the menu!\", 3) \" Write text in the menu window\r\n\" call myLayout1.Tabs.MyTab2.Windows.code2.Execute('e ' . $VIM . '\/vimrc') \" Show the vimrc file in the code2 window\r\n\" \r\n\" let myLayout2 = s:layout.New('MyLayout2')\r\n\" \r\n\" \" Set focus to MyTab1\r\n\" call myLayout1.Tabs.MyTab1.SetFocus()\r\n\" \r\n\" Note that I didn't finish the examples or the documentation, but the plugin is working fine with these initial features. Feel free to propose any features or to send comments.\r\n\r\n\" See sample project file included in the zip file\r\n\r\n\" Todo: \r\n\" Remove tabs and windows from the containers, at the same time from the editor\r\n\" Ajouter une fonction pour aller directement a une fenetre style gt 1 gt 5 pour les tabs mais pour une fenetre\r\n","install_details":"Copy the file layoutManager.vim to your vim plugin directory.","5":"Copy the file layoutManager.vim to your vim plugin directory.","first_name":"Alexandre","6":"Alexandre","last_name":"Viau","7":"Viau","releases":[{"0":"4217","vim_version":"7.0","1":"7.0","script_version":"1.0.3","2":"1.0.3","version_comment":"Changed the file format to unix","3":"Changed the file format to unix","package":"layoutManager.vim","4":"layoutManager.vim","src_id":"18995","5":"18995","creation_date":"1353328758","6":"1353328758"},{"0":"4217","vim_version":"7.0","1":"7.0","script_version":"1.0.2","2":"1.0.2","version_comment":"I included a better sample project file to use with the plugin. I use this sample project file myself so I tested it.","3":"I included a better sample project file to use with the plugin. I use this sample project file myself so I tested it.","package":"layoutManager.zip","4":"layoutManager.zip","src_id":"18986","5":"18986","creation_date":"1353155063","6":"1353155063"},{"0":"4217","vim_version":"7.0","1":"7.0","script_version":"1.0.1","2":"1.0.1","version_comment":"Added documentation to the file.","3":"Added documentation to the file.","package":"layoutManager.vim","4":"layoutManager.vim","src_id":"18610","5":"18610","creation_date":"1347699295","6":"1347699295"},{"0":"4217","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"layoutManager.vim","4":"layoutManager.vim","src_id":"18608","5":"18608","creation_date":"1347698358","6":"1347698358"}]},"4216":{"script_id":"4216","0":"4216","script_name":"fwk_ctags","1":"fwk_ctags","script_type":"utility","2":"utility","summary":"  Manage your ctags tags configurations simple and efficent","3":"  Manage your ctags tags configurations simple and efficent","description":"*fwk_ctags.txt*   Manage your ctags configurations simple and efficent.\r\n                Copyright (c) 2010-2012 Sergey Vakulenko\r\n                License:      GPL\r\n\r\n                                                                     *fwk_ctags*\r\n\r\nINTRODUCTION                    |fwk_ctags_introduction|\r\nINSTALLATION                    |fwk_ctags_installation|\r\nUSAGE                           |fwk_ctags_usage|\r\nGLOBAL VARIABLES                |fwk_ctags_variables|\r\nFUNCTIONS                       |fwk_ctags_func|\r\nEXEMPLES                        |fwk_ctags_exemples|\r\nFAQ                             |fwk_ctags_faq|\r\nCHANGES                         |fwk_ctags_changes|\r\n\r\n\r\n==============================================================================\r\nINTRODUCTION                                            *fwk_ctags_introduction*\r\n\r\nThis plugin was conceived to unify and generalize your vim \/ ctags interaction.\r\n\r\nlook the video tutorial like introduction:\r\n\r\nhttp:\/\/www.youtube.com\/watch?v=GBaT3n8CTK8\r\n\r\n==============================================================================\r\nINSTALLATION                                            *fwk_ctags_installation*\r\n\r\nPre-requirements~\r\n- ctags must be installed in your machine.\r\n- popup menus not works in vim console (but hot maps works!)\r\n\r\nJust drop files in zip archive to your vimfiles(win32) or .vim (linux\/ubuntu),\r\nor your custom path.\r\n\r\nThen, customize your cfg file ( looks section EXEMPLES for more information).\r\n\r\nFinnaly, set |g:fwk_ctags_config_to_load| variable in your vimrc. On start, plugin \r\nwill read this variable to load configuration path with tags:\r\n\r\n>\r\n    let g:fwk_ctags_config_to_load = 'path\/to\/configuration_file.cfg'\r\n>\r\n\r\nPlugin files~\r\ndoc\/fwk_ctags.txt\r\nplugin\/fwk_ctags.vim\r\nplugin\/ctags_config_sample.cfg\r\n\r\n\r\n==============================================================================\r\nUSAGE                                                          *fwk_ctags_usage*\r\n\r\nUsing *fwk_ctags* , You can create your configuration file with all ctags projects and then,\r\nswitch between them.\r\n\r\nBenefits of plugin:\r\n - You generalize you ctags configurations for different languages\r\n    (Python, C++, Java, Ruby, ...) in one config file.\r\n    \r\n - You can switch between ctags projects with maps or popup menus (simplest way!)\r\n\r\n - You can create simple single configuration as create few configurations,\r\n   which will be used dependly from |hostname()| or platform names (|win32|, |linux|).\r\n\r\n - you can refresh\/update your config with ctags in real time, no need restart. \r\n   After refresh, plugin collect new maps\/menus and remove olds ones.\r\n\r\n - you can browse ctags config in real time.\r\n\r\n - When you change your current ctags project, plugin remove previous tags\r\n   path, but not touch preseted tags paths ( |g:fwk_ctags_default_tags| ).\r\n\r\n - To make generation more faster, plugin create an tag file for each path: \r\n   In case when path wasnt modified, generation for this path will be skipped\r\n   (you will feel difference in big project).\r\n                                    \r\n\r\n\r\n\r\nFormat of a project in Configuration file~\r\n\r\n{ProjectName} {\r\n    map:{MapCombination}\r\n    \r\n    gen:{directoryToGeneratePath1}\r\n    gen:{directoryToGeneratePath2}\r\n    gen:{directoryToGeneratePath...N}\r\n    ...\r\n    set:{directoryToSetPath1}\r\n    set:{directoryToSetPath2}\r\n    set:{directoryToSetPath...N}\r\n    ...\r\n    pref:{SpecialCtagsOptions1}\r\n    pref:{SpecialCtagsOptions2}\r\n    pref:{SpecialCtagsOptions...N}\r\n}\r\n\r\nReal exemple of configuration file:~\r\nPython Django AppEngine ppdlive {\r\n    map:\\tp\r\n    set:\/usr\/lib\/python2.7\/dist-packages\/django\r\n    gen:\/home\/sergey\/workspace\/appEngine\/vppdlive\/ppdlive\r\n}\r\n\r\n\r\nHere:\r\n\"Python Django AppEngine ppdlive\" is {ProjectName}.\r\n\"map\" is {MapCombination}.\r\n\"set\" is {directoryToSetPath}.\r\n\"gen\" is {directoryToGeneratePath}.\r\n\r\n\r\nSyntax explainations:~\r\n\r\n{ProjectName}    - this is name of your project. Can contain spaces. {ProjectName}\r\nwill be uses as description in popup menu.\r\n\r\n{MapCombination} - this is root prefix of your hotkey. Finnaly for this project,\r\nyou will got combinations two combinations:\r\n{MapCombination}1 to generate tags for project.\r\n{MapCombination}2 to set tags for project.\r\n\r\nExemple for {MapCombination}:\r\nWe set {MapCombination} to \\tg. Finnaly, we will got maps:\r\n\\tg1    to generate tags\r\n\\tg2    to set tags\r\n\r\nTip: you can omit {MapCombination}, if you use only menus.\r\n\r\n\r\n{directoryToGeneratePath} - In project this is path for which need to generate tags.\r\nYou can set theses variables as many as you want. \r\n\r\n{directoryToSetPath}      - This is path which need to add to |tags| path of vim.\r\nYou can set theses variables as many you want. \r\n\r\n{SpecialCtagsOptions}     - this is help special instructions for ctags:\r\nadvanced options, to make ctags parse better.\r\nFor exemple, you can add regex rules to parse objective c code, like described\r\nin this page http:\/\/www.gregsexton.org\/2011\/04\/objective-c-exuberant-ctags-regex .\r\nIn |fwk_ctags_exemples| , we demonstrate how can be used this option.\r\n\r\n\r\nExemple: {directoryToGeneratePath} you can generate tags for your new\/updated sources and {directoryToSetPath}\r\n for connect tags paths of big projects (core library headers).\r\n\r\nTip: one 'set' or 'gen' option must be set in project configuration\r\n( otherwise, there is no sense in project configuration ).\r\n\r\nTip2: All {directoryToGeneratePath} paths will be added automaticly to list of {directoryToSetPath}.\r\n\r\nTip3: All rules {SpecialCtagsOptions} is ctags native.\r\nLook 'man ctags' for more information. \r\n\r\n\r\n\r\n\r\n==============================================================================\r\nGLOBAL VARIABLES                                           *fwk_ctags_variables*\r\n\r\n\r\nMust be set!~\r\n|g:fwk_ctags_config_to_load|        Path to fwk_ctags cfg to load. \r\n                                  Must be set to run plugin.\r\nPossible values: ~\r\nvariable not set                - execution of plugin will be skipped.\r\nvariable was set, with cfg path - plugin will loaded and and cfg file will be applied.\r\nvariable set, but empty ('')    - plugin will be loaded, but configuration skipped.\r\n                                  use can use |TagsLoadConfig| command to load\r\n                                  configuration file after (Normally, you dont\r\n                                  need this fonctionnality).\r\n\r\n\r\n|g:fwk_ctags_default_flags|         This is default option for ctags. \r\n                                  It will be apply for each project that you generate.\r\n                                  You can rewrite it.\r\nDefault value is:~\r\n-R --c++-kinds=+p --ocaml-kinds --fields=+iaS --extra=+q\r\n\r\n|g:fwk_ctags_default_tags|          This is default tags for vim set |tags| option.\r\n                                  Set it if you want add tags constant path.\r\n                                  It will be added before operation \r\n                                  'switch ctags project'. By default is empty.\r\n\r\n\r\n|g:fwk_ctags_popup_menu_root_path| prefix in popup menu. you can rewrite it.\r\nDefault value is:~\r\nPopUp.&Tags\r\n\r\n\r\n|g:fwk_ctags_map_refresh_config|   map for refresh current config file conbination\r\nDefault value is:~\r\n\\tgcr\r\n\r\n|g:fwk_ctags_map_open_curr_config| map to open current config file\r\nDefault value is:~\r\n\\tgcO\r\n\r\n\r\n|g:fwk_ctags_gen_sup_map| default prefix for generate map\r\nDefault value is:~\r\n'1'\r\n\r\n|g:fwk_ctags_set_sup_map| default prefix for set map \r\nDefault value is:~\r\n'2'\r\n\r\n\r\n\r\n==============================================================================\r\nFUNCTIONS                                                    *fwk_ctags_func*\r\n\r\nThis is additional API (normally, you dont need it):~\r\n\r\n|TagsLoadConfig| {config_file}   Function to load config file manually.\r\n                               After load, menus and maps from previous cfg file\r\n                               will be remove.\r\n\r\n|TagsBrowseConfig|               Function to browse config file manually. Like\r\n                               |TagsLoadConfig| , but with use of vim standart\r\n                               |browse()|.\r\n                                \r\n==============================================================================\r\nEXEMPLES                                                    *fwk_ctags_exemples*\r\n\r\nVIMRC SETTINGS:~\r\nExemple 1: simple config in vimrc to start plugin:\r\n\r\n>\r\n \"START FWK_CTAGS PLUGIN\r\n let g:fwk_ctags_config_to_load = 'd:\\programs\\vim\\plugin\\ctags_config_home_win32.cfg'\r\n>\r\n\r\nExemple 2: advanced settings in your .vimrc, to start plugin, and uses differents\r\nconfig files:\r\n>\r\n \"START FWK_CTAGS PLUGIN\r\n if has('win32')\r\n    let g:fwk_ctags_config_to_load = 'd:\\programs\\vim\\plugin\\ctags_config_home_win32.cfg'\r\n else \"linux\r\n    if hostname() == 'home'\r\n        let g:fwk_ctags_config_to_load = '\/home\/sergey\/.vim\/plugin\/ctags_config_home_linux.cfg'\r\n    else \"work \r\n        let g:fwk_ctags_config_to_load = '\/home\/svakulenko\/.vim\/plugin\/ctags_config_work.cfg'\r\n    endif\r\n endif\r\n<\r\n\r\n\r\nPROJECTS CONFIGS:~\r\n\r\n\r\nctags_config_home_win32.cfg ~\r\n--------------------------------------------------------------------\r\n\r\nmy library project {\r\n        gen:H:\\sources\\library\r\n}    \r\n\r\n\r\nctags_config_home_linux.cfg~\r\n--------------------------------------------------------------------\r\nHome Vim {\r\n    map:\\tg\r\n    gen:\/home\/sergey\/.vim\/vim_extention\/vimrc_config\r\n    gen:\/home\/sergey\/.vim\r\n}\r\n\r\n\r\nPython Django AppEngine ppdlive {\r\n    map:\\tp\r\n    set:\/usr\/lib\/python2.7\/dist-packages\/django\r\n    gen:\/home\/sergey\/workspace\/appEngine\/vppdlive\/ppdlive\r\n}\r\n\r\n\r\nctags_config_work.cfg~\r\n--------------------------------------------------------------------\r\nDefault ctags for vim distro {\r\n    map:\\tgh\r\n    gen:\/home\/svakulenko\/.vim\/vim_extention\/vimrc_config\r\n    gen:\/home\/svakulenko\/.vim\r\n}\r\n\r\nWS Client Java {\r\n    map:\\tgj\r\n    gen:\/home\/svakulenko\/depots\/svn\/trunk\/apps\/Android\/eclipse\/workspace\/WeatherStationClient\/src\r\n}\r\n\r\n\r\n\r\nWS JNI {\r\n    map:\\tgn\r\n    gen:\/home\/svakulenko\/depots\/svn\/trunk\/generic\/lib\r\n    gen:\/home\/svakulenko\/depots\/svn\/trunk\/apps\/Android\/lib0\r\n    gen:\/home\/svakulenko\/depots\/svn\/trunk\/generic\/lib1\r\n    gen:\/home\/svakulenko\/depots\/svn\/trunk\/generic\/lib2\r\n    gen:\/home\/svakulenko\/depots\/svn\/trunk\/generic\/lib3\r\n    gen:\/home\/svakulenko\/depots\/svn\/trunk\/apps\/iOS\/lib4\r\n}\r\n\r\n\r\nuse of the tip from this link http:\/\/www.gregsexton.org\/2011\/04\/objective-c-exuberant-ctags-regex\r\nto work with objective-c code:\r\n\r\nIOS Project {\r\n    map:\\tgm\r\n    gen:\/home\/svakulenko\/depots\/svn\/trunk\/apps\/iOS\r\n    pref:--langdef=objc\r\n    pref:--langmap=objc:.m.h\r\n    pref:--regex-objc=\/^[[:space:]]*[-+][[:space:]]*\\([[:alpha:]]+[[:space:]]*\\*?\\)[[:space:]]*([[:alnum:]]+):[[:space:]]*\\(\/\\1\/m,method\/\r\n    pref:--regex-objc=\/^[[:space:]]*[-+][[:space:]]*\\([[:alpha:]]+[[:space:]]*\\*?\\)[[:space:]]*([[:alnum:]]+)[[:space:]]*\\{\/\\1\/m,method\/\r\n    pref:--regex-objc=\/^[[:space:]]*[-+][[:space:]]*\\([[:alpha:]]+[[:space:]]*\\*?\\)[[:space:]]*([[:alnum:]]+)[[:space:]]*\\;\/\\1\/m,method\/\r\n    pref:--regex-objc=\/^[[:space:]]*\\@property[[:space:]]+.*[[:space:]]+\\*?(.*);$\/\\1\/p,property\/\r\n    pref:--regex-objc=\/^[[:space:]]*\\@implementation[[:space:]]+(.*)$\/\\1\/c,class\/\r\n    pref:--regex-objc=\/^[[:space:]]*\\@interface[[:space:]]+(.*)[[:space:]]+:.*{\/\\1\/i,interface\/\r\n}        \r\n\r\n\r\n==============================================================================\r\nFAQ                                                              *fwk_ctags_faq*\r\n\r\n    1.1 When I call project hotkey, I got many warnings in output. Why?\r\n        - Normally, output that you see is generated by original utility ctags.\r\n        if you see warnings, that is warnings of ctags. To be sure, you can \r\n        always test generation of tags manually.\r\n\r\n\r\n==============================================================================\r\nCHANGES                                                      *fwk_ctags_changes*\r\n\r\n\r\n\r\n0.6 - share plugin. init upload\r\n\r\n\r\n==============================================================================\r\n vim:tw=78:ts=8:ft=help:norl:\r\n\r\n","4":"*fwk_ctags.txt*   Manage your ctags configurations simple and efficent.\r\n                Copyright (c) 2010-2012 Sergey Vakulenko\r\n                License:      GPL\r\n\r\n                                                                     *fwk_ctags*\r\n\r\nINTRODUCTION                    |fwk_ctags_introduction|\r\nINSTALLATION                    |fwk_ctags_installation|\r\nUSAGE                           |fwk_ctags_usage|\r\nGLOBAL VARIABLES                |fwk_ctags_variables|\r\nFUNCTIONS                       |fwk_ctags_func|\r\nEXEMPLES                        |fwk_ctags_exemples|\r\nFAQ                             |fwk_ctags_faq|\r\nCHANGES                         |fwk_ctags_changes|\r\n\r\n\r\n==============================================================================\r\nINTRODUCTION                                            *fwk_ctags_introduction*\r\n\r\nThis plugin was conceived to unify and generalize your vim \/ ctags interaction.\r\n\r\nlook the video tutorial like introduction:\r\n\r\nhttp:\/\/www.youtube.com\/watch?v=GBaT3n8CTK8\r\n\r\n==============================================================================\r\nINSTALLATION                                            *fwk_ctags_installation*\r\n\r\nPre-requirements~\r\n- ctags must be installed in your machine.\r\n- popup menus not works in vim console (but hot maps works!)\r\n\r\nJust drop files in zip archive to your vimfiles(win32) or .vim (linux\/ubuntu),\r\nor your custom path.\r\n\r\nThen, customize your cfg file ( looks section EXEMPLES for more information).\r\n\r\nFinnaly, set |g:fwk_ctags_config_to_load| variable in your vimrc. On start, plugin \r\nwill read this variable to load configuration path with tags:\r\n\r\n>\r\n    let g:fwk_ctags_config_to_load = 'path\/to\/configuration_file.cfg'\r\n>\r\n\r\nPlugin files~\r\ndoc\/fwk_ctags.txt\r\nplugin\/fwk_ctags.vim\r\nplugin\/ctags_config_sample.cfg\r\n\r\n\r\n==============================================================================\r\nUSAGE                                                          *fwk_ctags_usage*\r\n\r\nUsing *fwk_ctags* , You can create your configuration file with all ctags projects and then,\r\nswitch between them.\r\n\r\nBenefits of plugin:\r\n - You generalize you ctags configurations for different languages\r\n    (Python, C++, Java, Ruby, ...) in one config file.\r\n    \r\n - You can switch between ctags projects with maps or popup menus (simplest way!)\r\n\r\n - You can create simple single configuration as create few configurations,\r\n   which will be used dependly from |hostname()| or platform names (|win32|, |linux|).\r\n\r\n - you can refresh\/update your config with ctags in real time, no need restart. \r\n   After refresh, plugin collect new maps\/menus and remove olds ones.\r\n\r\n - you can browse ctags config in real time.\r\n\r\n - When you change your current ctags project, plugin remove previous tags\r\n   path, but not touch preseted tags paths ( |g:fwk_ctags_default_tags| ).\r\n\r\n - To make generation more faster, plugin create an tag file for each path: \r\n   In case when path wasnt modified, generation for this path will be skipped\r\n   (you will feel difference in big project).\r\n                                    \r\n\r\n\r\n\r\nFormat of a project in Configuration file~\r\n\r\n{ProjectName} {\r\n    map:{MapCombination}\r\n    \r\n    gen:{directoryToGeneratePath1}\r\n    gen:{directoryToGeneratePath2}\r\n    gen:{directoryToGeneratePath...N}\r\n    ...\r\n    set:{directoryToSetPath1}\r\n    set:{directoryToSetPath2}\r\n    set:{directoryToSetPath...N}\r\n    ...\r\n    pref:{SpecialCtagsOptions1}\r\n    pref:{SpecialCtagsOptions2}\r\n    pref:{SpecialCtagsOptions...N}\r\n}\r\n\r\nReal exemple of configuration file:~\r\nPython Django AppEngine ppdlive {\r\n    map:\\tp\r\n    set:\/usr\/lib\/python2.7\/dist-packages\/django\r\n    gen:\/home\/sergey\/workspace\/appEngine\/vppdlive\/ppdlive\r\n}\r\n\r\n\r\nHere:\r\n\"Python Django AppEngine ppdlive\" is {ProjectName}.\r\n\"map\" is {MapCombination}.\r\n\"set\" is {directoryToSetPath}.\r\n\"gen\" is {directoryToGeneratePath}.\r\n\r\n\r\nSyntax explainations:~\r\n\r\n{ProjectName}    - this is name of your project. Can contain spaces. {ProjectName}\r\nwill be uses as description in popup menu.\r\n\r\n{MapCombination} - this is root prefix of your hotkey. Finnaly for this project,\r\nyou will got combinations two combinations:\r\n{MapCombination}1 to generate tags for project.\r\n{MapCombination}2 to set tags for project.\r\n\r\nExemple for {MapCombination}:\r\nWe set {MapCombination} to \\tg. Finnaly, we will got maps:\r\n\\tg1    to generate tags\r\n\\tg2    to set tags\r\n\r\nTip: you can omit {MapCombination}, if you use only menus.\r\n\r\n\r\n{directoryToGeneratePath} - In project this is path for which need to generate tags.\r\nYou can set theses variables as many as you want. \r\n\r\n{directoryToSetPath}      - This is path which need to add to |tags| path of vim.\r\nYou can set theses variables as many you want. \r\n\r\n{SpecialCtagsOptions}     - this is help special instructions for ctags:\r\nadvanced options, to make ctags parse better.\r\nFor exemple, you can add regex rules to parse objective c code, like described\r\nin this page http:\/\/www.gregsexton.org\/2011\/04\/objective-c-exuberant-ctags-regex .\r\nIn |fwk_ctags_exemples| , we demonstrate how can be used this option.\r\n\r\n\r\nExemple: {directoryToGeneratePath} you can generate tags for your new\/updated sources and {directoryToSetPath}\r\n for connect tags paths of big projects (core library headers).\r\n\r\nTip: one 'set' or 'gen' option must be set in project configuration\r\n( otherwise, there is no sense in project configuration ).\r\n\r\nTip2: All {directoryToGeneratePath} paths will be added automaticly to list of {directoryToSetPath}.\r\n\r\nTip3: All rules {SpecialCtagsOptions} is ctags native.\r\nLook 'man ctags' for more information. \r\n\r\n\r\n\r\n\r\n==============================================================================\r\nGLOBAL VARIABLES                                           *fwk_ctags_variables*\r\n\r\n\r\nMust be set!~\r\n|g:fwk_ctags_config_to_load|        Path to fwk_ctags cfg to load. \r\n                                  Must be set to run plugin.\r\nPossible values: ~\r\nvariable not set                - execution of plugin will be skipped.\r\nvariable was set, with cfg path - plugin will loaded and and cfg file will be applied.\r\nvariable set, but empty ('')    - plugin will be loaded, but configuration skipped.\r\n                                  use can use |TagsLoadConfig| command to load\r\n                                  configuration file after (Normally, you dont\r\n                                  need this fonctionnality).\r\n\r\n\r\n|g:fwk_ctags_default_flags|         This is default option for ctags. \r\n                                  It will be apply for each project that you generate.\r\n                                  You can rewrite it.\r\nDefault value is:~\r\n-R --c++-kinds=+p --ocaml-kinds --fields=+iaS --extra=+q\r\n\r\n|g:fwk_ctags_default_tags|          This is default tags for vim set |tags| option.\r\n                                  Set it if you want add tags constant path.\r\n                                  It will be added before operation \r\n                                  'switch ctags project'. By default is empty.\r\n\r\n\r\n|g:fwk_ctags_popup_menu_root_path| prefix in popup menu. you can rewrite it.\r\nDefault value is:~\r\nPopUp.&Tags\r\n\r\n\r\n|g:fwk_ctags_map_refresh_config|   map for refresh current config file conbination\r\nDefault value is:~\r\n\\tgcr\r\n\r\n|g:fwk_ctags_map_open_curr_config| map to open current config file\r\nDefault value is:~\r\n\\tgcO\r\n\r\n\r\n|g:fwk_ctags_gen_sup_map| default prefix for generate map\r\nDefault value is:~\r\n'1'\r\n\r\n|g:fwk_ctags_set_sup_map| default prefix for set map \r\nDefault value is:~\r\n'2'\r\n\r\n\r\n\r\n==============================================================================\r\nFUNCTIONS                                                    *fwk_ctags_func*\r\n\r\nThis is additional API (normally, you dont need it):~\r\n\r\n|TagsLoadConfig| {config_file}   Function to load config file manually.\r\n                               After load, menus and maps from previous cfg file\r\n                               will be remove.\r\n\r\n|TagsBrowseConfig|               Function to browse config file manually. Like\r\n                               |TagsLoadConfig| , but with use of vim standart\r\n                               |browse()|.\r\n                                \r\n==============================================================================\r\nEXEMPLES                                                    *fwk_ctags_exemples*\r\n\r\nVIMRC SETTINGS:~\r\nExemple 1: simple config in vimrc to start plugin:\r\n\r\n>\r\n \"START FWK_CTAGS PLUGIN\r\n let g:fwk_ctags_config_to_load = 'd:\\programs\\vim\\plugin\\ctags_config_home_win32.cfg'\r\n>\r\n\r\nExemple 2: advanced settings in your .vimrc, to start plugin, and uses differents\r\nconfig files:\r\n>\r\n \"START FWK_CTAGS PLUGIN\r\n if has('win32')\r\n    let g:fwk_ctags_config_to_load = 'd:\\programs\\vim\\plugin\\ctags_config_home_win32.cfg'\r\n else \"linux\r\n    if hostname() == 'home'\r\n        let g:fwk_ctags_config_to_load = '\/home\/sergey\/.vim\/plugin\/ctags_config_home_linux.cfg'\r\n    else \"work \r\n        let g:fwk_ctags_config_to_load = '\/home\/svakulenko\/.vim\/plugin\/ctags_config_work.cfg'\r\n    endif\r\n endif\r\n<\r\n\r\n\r\nPROJECTS CONFIGS:~\r\n\r\n\r\nctags_config_home_win32.cfg ~\r\n--------------------------------------------------------------------\r\n\r\nmy library project {\r\n        gen:H:\\sources\\library\r\n}    \r\n\r\n\r\nctags_config_home_linux.cfg~\r\n--------------------------------------------------------------------\r\nHome Vim {\r\n    map:\\tg\r\n    gen:\/home\/sergey\/.vim\/vim_extention\/vimrc_config\r\n    gen:\/home\/sergey\/.vim\r\n}\r\n\r\n\r\nPython Django AppEngine ppdlive {\r\n    map:\\tp\r\n    set:\/usr\/lib\/python2.7\/dist-packages\/django\r\n    gen:\/home\/sergey\/workspace\/appEngine\/vppdlive\/ppdlive\r\n}\r\n\r\n\r\nctags_config_work.cfg~\r\n--------------------------------------------------------------------\r\nDefault ctags for vim distro {\r\n    map:\\tgh\r\n    gen:\/home\/svakulenko\/.vim\/vim_extention\/vimrc_config\r\n    gen:\/home\/svakulenko\/.vim\r\n}\r\n\r\nWS Client Java {\r\n    map:\\tgj\r\n    gen:\/home\/svakulenko\/depots\/svn\/trunk\/apps\/Android\/eclipse\/workspace\/WeatherStationClient\/src\r\n}\r\n\r\n\r\n\r\nWS JNI {\r\n    map:\\tgn\r\n    gen:\/home\/svakulenko\/depots\/svn\/trunk\/generic\/lib\r\n    gen:\/home\/svakulenko\/depots\/svn\/trunk\/apps\/Android\/lib0\r\n    gen:\/home\/svakulenko\/depots\/svn\/trunk\/generic\/lib1\r\n    gen:\/home\/svakulenko\/depots\/svn\/trunk\/generic\/lib2\r\n    gen:\/home\/svakulenko\/depots\/svn\/trunk\/generic\/lib3\r\n    gen:\/home\/svakulenko\/depots\/svn\/trunk\/apps\/iOS\/lib4\r\n}\r\n\r\n\r\nuse of the tip from this link http:\/\/www.gregsexton.org\/2011\/04\/objective-c-exuberant-ctags-regex\r\nto work with objective-c code:\r\n\r\nIOS Project {\r\n    map:\\tgm\r\n    gen:\/home\/svakulenko\/depots\/svn\/trunk\/apps\/iOS\r\n    pref:--langdef=objc\r\n    pref:--langmap=objc:.m.h\r\n    pref:--regex-objc=\/^[[:space:]]*[-+][[:space:]]*\\([[:alpha:]]+[[:space:]]*\\*?\\)[[:space:]]*([[:alnum:]]+):[[:space:]]*\\(\/\\1\/m,method\/\r\n    pref:--regex-objc=\/^[[:space:]]*[-+][[:space:]]*\\([[:alpha:]]+[[:space:]]*\\*?\\)[[:space:]]*([[:alnum:]]+)[[:space:]]*\\{\/\\1\/m,method\/\r\n    pref:--regex-objc=\/^[[:space:]]*[-+][[:space:]]*\\([[:alpha:]]+[[:space:]]*\\*?\\)[[:space:]]*([[:alnum:]]+)[[:space:]]*\\;\/\\1\/m,method\/\r\n    pref:--regex-objc=\/^[[:space:]]*\\@property[[:space:]]+.*[[:space:]]+\\*?(.*);$\/\\1\/p,property\/\r\n    pref:--regex-objc=\/^[[:space:]]*\\@implementation[[:space:]]+(.*)$\/\\1\/c,class\/\r\n    pref:--regex-objc=\/^[[:space:]]*\\@interface[[:space:]]+(.*)[[:space:]]+:.*{\/\\1\/i,interface\/\r\n}        \r\n\r\n\r\n==============================================================================\r\nFAQ                                                              *fwk_ctags_faq*\r\n\r\n    1.1 When I call project hotkey, I got many warnings in output. Why?\r\n        - Normally, output that you see is generated by original utility ctags.\r\n        if you see warnings, that is warnings of ctags. To be sure, you can \r\n        always test generation of tags manually.\r\n\r\n\r\n==============================================================================\r\nCHANGES                                                      *fwk_ctags_changes*\r\n\r\n\r\n\r\n0.6 - share plugin. init upload\r\n\r\n\r\n==============================================================================\r\n vim:tw=78:ts=8:ft=help:norl:\r\n\r\n","install_details":"Pre-requirements~\r\n- ctags must be installed in your machine.\r\n- popup menus not works in vim console (but hot maps works!)\r\n\r\nJust drop files in zip archive to your vimfiles(win32) or .vim (linux\/ubuntu),\r\nor your custom path.\r\n\r\nThen, customize your cfg file ( looks section EXEMPLES for more information).\r\n\r\nFinnaly, set |g:fwk_ctags_config_to_load| variable in your vimrc. On start, plugin \r\nwill read this variable to load configuration path with tags:\r\n\r\n>\r\n    let g:fwk_ctags_config_to_load = 'path\/to\/configuration_file.cfg'\r\n>\r\n\r\nPlugin files~\r\ndoc\/fwk_ctags.txt\r\nplugin\/fwk_ctags.vim\r\nplugin\/ctags_config_sample.cfg (sample configuration)\r\n","5":"Pre-requirements~\r\n- ctags must be installed in your machine.\r\n- popup menus not works in vim console (but hot maps works!)\r\n\r\nJust drop files in zip archive to your vimfiles(win32) or .vim (linux\/ubuntu),\r\nor your custom path.\r\n\r\nThen, customize your cfg file ( looks section EXEMPLES for more information).\r\n\r\nFinnaly, set |g:fwk_ctags_config_to_load| variable in your vimrc. On start, plugin \r\nwill read this variable to load configuration path with tags:\r\n\r\n>\r\n    let g:fwk_ctags_config_to_load = 'path\/to\/configuration_file.cfg'\r\n>\r\n\r\nPlugin files~\r\ndoc\/fwk_ctags.txt\r\nplugin\/fwk_ctags.vim\r\nplugin\/ctags_config_sample.cfg (sample configuration)\r\n","first_name":"Sergey","6":"Sergey","last_name":"Vakulenko","7":"Vakulenko","releases":[{"0":"4216","vim_version":"7.0","1":"7.0","script_version":"0.6","2":"0.6","version_comment":"Initial upload","3":"Initial upload","package":"fwk_ctags.zip","4":"fwk_ctags.zip","src_id":"18607","5":"18607","creation_date":"1347698182","6":"1347698182"}]},"4215":{"script_id":"4215","0":"4215","script_name":"R-MacVim","1":"R-MacVim","script_type":"ftplugin","2":"ftplugin","summary":"R plugin for MacVim (R Vim Mac, R MacVim)","3":"R plugin for MacVim (R Vim Mac, R MacVim)","description":"## What is it?\r\n- It is a R plugin for MacVim.\r\n \r\n- It allows you to send selected words, lines and blocks to R (by CMD+r).\r\n\r\n- It also allows you to source the whole R file (by CMD+R). \r\n\r\n- It also allows you to change your working directory (by CMD+d).\r\n\r\n- It also allows you to comment or uncomment single or multiple lines (by CMD+3).\r\n\r\n- Key maps are changable (see below).\r\n\r\n- For development and bug reports:\r\n http:\/\/github.com\/randy3k\/r-macvim\r\n\r\n- Stable updates will be uploaded to:\r\n http:\/\/www.vim.org\/scripts\/script.php?script_id=4215\r\n\r\n- This plugin aims at being simple. For more plugins, see:\r\n Vim-R-plugin: http:\/\/www.vim.org\/scripts\/script.php?script_id=2628\r\n","4":"## What is it?\r\n- It is a R plugin for MacVim.\r\n \r\n- It allows you to send selected words, lines and blocks to R (by CMD+r).\r\n\r\n- It also allows you to source the whole R file (by CMD+R). \r\n\r\n- It also allows you to change your working directory (by CMD+d).\r\n\r\n- It also allows you to comment or uncomment single or multiple lines (by CMD+3).\r\n\r\n- Key maps are changable (see below).\r\n\r\n- For development and bug reports:\r\n http:\/\/github.com\/randy3k\/r-macvim\r\n\r\n- Stable updates will be uploaded to:\r\n http:\/\/www.vim.org\/scripts\/script.php?script_id=4215\r\n\r\n- This plugin aims at being simple. For more plugins, see:\r\n Vim-R-plugin: http:\/\/www.vim.org\/scripts\/script.php?script_id=2628\r\n","install_details":"## Installation\r\n\r\n- Copy the file r.vim to ~\/.vim\/ftplugin\/\r\n\r\n- You can change the key mappings by\r\n\r\n        let g:r_macvim_RSource     = '<D-R>'\r\n        let g:r_macvim_RSend       = '<D-r>'\r\n        let g:r_macvim_RChgWorkDir = '<D-d>'\r\n        let g:r_macvim_RComment    = '<D-3>'\r\n\r\n- If you want to use R.app instead of R64.app, also add the following to your .vimrc file:\r\n\r\n        let g:r_macvim_use32 = 1","5":"## Installation\r\n\r\n- Copy the file r.vim to ~\/.vim\/ftplugin\/\r\n\r\n- You can change the key mappings by\r\n\r\n        let g:r_macvim_RSource     = '<D-R>'\r\n        let g:r_macvim_RSend       = '<D-r>'\r\n        let g:r_macvim_RChgWorkDir = '<D-d>'\r\n        let g:r_macvim_RComment    = '<D-3>'\r\n\r\n- If you want to use R.app instead of R64.app, also add the following to your .vimrc file:\r\n\r\n        let g:r_macvim_use32 = 1","first_name":"Randy","6":"Randy","last_name":"Lai","7":"Lai","releases":[{"0":"4215","vim_version":"7.3","1":"7.3","script_version":"1.0.6","2":"1.0.6","version_comment":"v1.0.6","3":"v1.0.6","package":"R-MacVim_v1.0.6.zip","4":"R-MacVim_v1.0.6.zip","src_id":"18913","5":"18913","creation_date":"1351413205","6":"1351413205"},{"0":"4215","vim_version":"7.3","1":"7.3","script_version":"1.0.5","2":"1.0.5","version_comment":"v1.0.5","3":"v1.0.5","package":"R-MacVim_v1.0.5.zip","4":"R-MacVim_v1.0.5.zip","src_id":"18902","5":"18902","creation_date":"1351336531","6":"1351336531"},{"0":"4215","vim_version":"7.3","1":"7.3","script_version":"1.0.4","2":"1.0.4","version_comment":"Simplify the plugin","3":"Simplify the plugin","package":"R-MacVim_v1.0.4.zip","4":"R-MacVim_v1.0.4.zip","src_id":"18898","5":"18898","creation_date":"1351291639","6":"1351291639"}]},"4214":{"script_id":"4214","0":"4214","script_name":"gvimt","1":"gvimt","script_type":"utility","2":"utility","summary":"Open new files in gvim in new tabs, splits or vertical splits","3":"Open new files in gvim in new tabs, splits or vertical splits","description":"gvimt.bat is a script for Windows to open new files in gvim in new tabs, splits or vertical splits.  It starts gvim if it is not running already.\r\n\r\nCall it from SendTo menu, from Context menu entries or from the command line.\r\n\r\nIt ignores command line vim, and gvims where the --servername parameter has changed the name to not include \"GVIM\" \r\n\r\nIt prefers to use vim.exe (command line vim, not gvim) to check if gvim is already running.  If that's not available it will use the tasklist command (which exists from Windows XP, but not in Windows 2000).  On Windows 2000 you'll need to have an instance of gvim running already.  Tasklist is not always reliable when using several remote desktop sessions on a machine (because for some reason %SESSIONNAME% parameter is not always populated in the batch file's environment).\r\n\r\nIt creates gvimt.tmp while it is running, if it crashes or goes wrong for some reason, delete this file.\r\n\r\nWhy use this instead of simpler methods?\r\n========================================\r\nThere are simpler ways to call gvim directly passing file names to new tabs.  There is the --remote-tab parameter, for example.  Some methods are discussed here: http:\/\/vim.wikia.com\/wiki\/Launch_files_in_new_tabs_under_Windows\r\n\r\nThere are some problems doing this with many files from the Windows context menu:\r\n- There is no --remote-split parameter so a different approach is needed for opening files in a new split window.  --remote-send can be used to send an arbitary command for this, but unlike --remote-tab it will not open a new instance of gvim if one doesn't already exist.\r\n- If you select multiple files and use the Windows context menu, each file gets its own invocation of the command.  gvim does not handle several simultaneous --remote-tab commands well.\r\n- The SendTo menu does pass all the selected files to one command, but it is an extra click on the right menu to get there, so it is nice to use the Context menu.","4":"gvimt.bat is a script for Windows to open new files in gvim in new tabs, splits or vertical splits.  It starts gvim if it is not running already.\r\n\r\nCall it from SendTo menu, from Context menu entries or from the command line.\r\n\r\nIt ignores command line vim, and gvims where the --servername parameter has changed the name to not include \"GVIM\" \r\n\r\nIt prefers to use vim.exe (command line vim, not gvim) to check if gvim is already running.  If that's not available it will use the tasklist command (which exists from Windows XP, but not in Windows 2000).  On Windows 2000 you'll need to have an instance of gvim running already.  Tasklist is not always reliable when using several remote desktop sessions on a machine (because for some reason %SESSIONNAME% parameter is not always populated in the batch file's environment).\r\n\r\nIt creates gvimt.tmp while it is running, if it crashes or goes wrong for some reason, delete this file.\r\n\r\nWhy use this instead of simpler methods?\r\n========================================\r\nThere are simpler ways to call gvim directly passing file names to new tabs.  There is the --remote-tab parameter, for example.  Some methods are discussed here: http:\/\/vim.wikia.com\/wiki\/Launch_files_in_new_tabs_under_Windows\r\n\r\nThere are some problems doing this with many files from the Windows context menu:\r\n- There is no --remote-split parameter so a different approach is needed for opening files in a new split window.  --remote-send can be used to send an arbitary command for this, but unlike --remote-tab it will not open a new instance of gvim if one doesn't already exist.\r\n- If you select multiple files and use the Windows context menu, each file gets its own invocation of the command.  gvim does not handle several simultaneous --remote-tab commands well.\r\n- The SendTo menu does pass all the selected files to one command, but it is an extra click on the right menu to get there, so it is nice to use the Context menu.","install_details":"Create directory C:\\Batch Files\\ and extract the package there. (If you want another directory, change \"set batch_path=\" at the start of gvimt.bat, and modify gvim.reg accordingly.)\r\n\r\nIf you do not have vim.exe, and do not have the tasklist command (e.g. using Windows 2000), edit the batch file and change \"set already_ran\" to \"=true\" at the start of gvimt.bat.\r\n\r\nIf your gvim typically takes longer than a second to start up, change \"set vim_startup_time_ms\" to be more milliseconds. \r\n\r\nIf you find tv and ts commands open files on more than one tab, change \"set tabsplit_wait_s\" to be more seconds.\r\n\r\nIf gvim.exe or vim.exe are not in your path, edit gvimt.bat and change \"set gvim_path=\" and \"set vim_path=\" at the start.  Paths should end with \\ and be quoted, e.g. \r\n\r\n    set vim_path=\"c:\\program files\\vim\\vim73\\\"\r\n    set gvim_path=\"c:\\program files\\vim\\vim73\\\"\r\n\r\nOptionally run the gvimt.reg file to create Context Menu entries.\r\n\r\nOptionally, create shortcuts in your SendTo directory with these targets:\r\n\"c:\\batch files\\gvimt.bat\" t \r\n\"c:\\batch files\\gvimt.bat\" v\r\n\"c:\\batch files\\gvimt.bat\" s\r\n\"c:\\batch files\\gvimt.bat\" tv\r\n\"c:\\batch files\\gvimt.bat\" ts\r\n\r\nName these three shortcuts something like \"Edit with Vim Tab\", \"Edit with Vim VSplit\", \"Edit with Vim Split\", \"Edit with Vim VSplit Tab\", and \"Edit with Vim Split Tab\"\r\n\r\nYour SendTo menu directory location depends on which version of Windows you are using.  Under XP it is probably c:\\documents and settings\\username\\SendTo.\r\n","5":"Create directory C:\\Batch Files\\ and extract the package there. (If you want another directory, change \"set batch_path=\" at the start of gvimt.bat, and modify gvim.reg accordingly.)\r\n\r\nIf you do not have vim.exe, and do not have the tasklist command (e.g. using Windows 2000), edit the batch file and change \"set already_ran\" to \"=true\" at the start of gvimt.bat.\r\n\r\nIf your gvim typically takes longer than a second to start up, change \"set vim_startup_time_ms\" to be more milliseconds. \r\n\r\nIf you find tv and ts commands open files on more than one tab, change \"set tabsplit_wait_s\" to be more seconds.\r\n\r\nIf gvim.exe or vim.exe are not in your path, edit gvimt.bat and change \"set gvim_path=\" and \"set vim_path=\" at the start.  Paths should end with \\ and be quoted, e.g. \r\n\r\n    set vim_path=\"c:\\program files\\vim\\vim73\\\"\r\n    set gvim_path=\"c:\\program files\\vim\\vim73\\\"\r\n\r\nOptionally run the gvimt.reg file to create Context Menu entries.\r\n\r\nOptionally, create shortcuts in your SendTo directory with these targets:\r\n\"c:\\batch files\\gvimt.bat\" t \r\n\"c:\\batch files\\gvimt.bat\" v\r\n\"c:\\batch files\\gvimt.bat\" s\r\n\"c:\\batch files\\gvimt.bat\" tv\r\n\"c:\\batch files\\gvimt.bat\" ts\r\n\r\nName these three shortcuts something like \"Edit with Vim Tab\", \"Edit with Vim VSplit\", \"Edit with Vim Split\", \"Edit with Vim VSplit Tab\", and \"Edit with Vim Split Tab\"\r\n\r\nYour SendTo menu directory location depends on which version of Windows you are using.  Under XP it is probably c:\\documents and settings\\username\\SendTo.\r\n","first_name":"Geoff","6":"Geoff","last_name":"Wood","7":"Wood","releases":[{"0":"4214","vim_version":"7.0","1":"7.0","script_version":"10","2":"10","version_comment":"Stop using short paths to be Windows 7 compatible\r\n","3":"Stop using short paths to be Windows 7 compatible\r\n","package":"gvimt.zip","4":"gvimt.zip","src_id":"21671","5":"21671","creation_date":"1395833583","6":"1395833583"},{"0":"4214","vim_version":"7.0","1":"7.0","script_version":"9","2":"9","version_comment":"gw 2\/12\/13 Prefer to use cmd-line vim to list remote servers. If it does have to use tasklist, handle case where sessionname is not populated (by failing more nicely)","3":"gw 2\/12\/13 Prefer to use cmd-line vim to list remote servers. If it does have to use tasklist, handle case where sessionname is not populated (by failing more nicely)","package":"gvimt.zip","4":"gvimt.zip","src_id":"21160","5":"21160","creation_date":"1386250357","6":"1386250357"},{"0":"4214","vim_version":"7.0","1":"7.0","script_version":"8","2":"8","version_comment":"Fixed so only considers if vim is already running in this user session, to avoid failure when another user is running vim","3":"Fixed so only considers if vim is already running in this user session, to avoid failure when another user is running vim","package":"gvimt.zip","4":"gvimt.zip","src_id":"20365","5":"20365","creation_date":"1371488744","6":"1371488744"},{"0":"4214","vim_version":"7.0","1":"7.0","script_version":"7","2":"7","version_comment":"Fixed problem where new Tab + Split options were oopening files on more than one tab if you passed more than about five filenames.","3":"Fixed problem where new Tab + Split options were oopening files on more than one tab if you passed more than about five filenames.","package":"gvimt.zip","4":"gvimt.zip","src_id":"20087","5":"20087","creation_date":"1368184767","6":"1368184767"},{"0":"4214","vim_version":"7.0","1":"7.0","script_version":"6","2":"6","version_comment":"Added tv and ts so you can open a new single tab with a split view of several files","3":"Added tv and ts so you can open a new single tab with a split view of several files","package":"gvimt.zip","4":"gvimt.zip","src_id":"20080","5":"20080","creation_date":"1368095270","6":"1368095270"},{"0":"4214","vim_version":"7.0","1":"7.0","script_version":"5","2":"5","version_comment":"Goes to normal mode first to make sure commands execute and don't just go into the file being edited.\r\nWaits a bit when starting vim.\r\nClears the command from the command line afterwards.","3":"Goes to normal mode first to make sure commands execute and don't just go into the file being edited.\r\nWaits a bit when starting vim.\r\nClears the command from the command line afterwards.","package":"gvimt.zip","4":"gvimt.zip","src_id":"18767","5":"18767","creation_date":"1349787633","6":"1349787633"},{"0":"4214","vim_version":"7.0","1":"7.0","script_version":"4","2":"4","version_comment":"Expand passed filename to full path so can call from command line for a file in the local directory, as well.\r\n\r\nAlso fixed typo recently introduced where vsplits were just acting as splits\r\n\r\n","3":"Expand passed filename to full path so can call from command line for a file in the local directory, as well.\r\n\r\nAlso fixed typo recently introduced where vsplits were just acting as splits\r\n\r\n","package":"gvimt.zip","4":"gvimt.zip","src_id":"18701","5":"18701","creation_date":"1348753636","6":"1348753636"},{"0":"4214","vim_version":"7.0","1":"7.0","script_version":"3","2":"3","version_comment":"Removed dependency on awk and grep\r\nAdded vim_path option in case gvim.exe is not in your path","3":"Removed dependency on awk and grep\r\nAdded vim_path option in case gvim.exe is not in your path","package":"gvimt.zip","4":"gvimt.zip","src_id":"18686","5":"18686","creation_date":"1348590122","6":"1348590122"},{"0":"4214","vim_version":"7.0","1":"7.0","script_version":"2","2":"2","version_comment":"Added command to raise Vim to foreground\r\n\r\nUpdated install instructions to mention changing gvim.reg if you change the path from C:\\Batch Files\\","3":"Added command to raise Vim to foreground\r\n\r\nUpdated install instructions to mention changing gvim.reg if you change the path from C:\\Batch Files\\","package":"gvimt.zip","4":"gvimt.zip","src_id":"18683","5":"18683","creation_date":"1348578804","6":"1348578804"},{"0":"4214","vim_version":"7.0","1":"7.0","script_version":"1","2":"1","version_comment":"Initial upload","3":"Initial upload","package":"gvimt.zip","4":"gvimt.zip","src_id":"18592","5":"18592","creation_date":"1347540023","6":"1347540023"}]},"4213":{"script_id":"4213","0":"4213","script_name":"jinja","1":"jinja","script_type":"indent","2":"indent","summary":"jinja syntax and indent plugin","3":"jinja syntax and indent plugin","description":"# Jinja for Vim\r\n\r\nJinja bundle for vim.\r\n\r\n\r\n## Feature\r\n\r\n1. full syntax support\r\n2. great indent support\r\n\r\n## Installation\r\n\r\n### Install with [Vundle](https:\/\/github.com\/gmarik\/vundle)\r\n\r\nIf you are not using vundle, you really should have a try.\r\nEdit your vimrc:\r\n\r\n    Bundle \"lepture\/vim-jinja\"\r\n\r\nAnd install it:\r\n\r\n    :so ~\/.vimrc\r\n    :BundleInstall\r\n\r\n\r\n### Install with [pathogen](https:\/\/github.com\/tpope\/vim-pathogen)\r\n\r\nIf you prefer tpope's pathogen, that's ok. Just clone it:\r\n\r\n    cd ~\/.vim\/bundle\r\n    git clone https:\/\/github.com\/lepture\/vim-jinja.git\r\n\r\n\r\n## Configuration\r\n\r\nNo configuration is needed, if you are using vim 7.2+, it will detect if\r\na html file is a jinja template.\r\n\r\nBut if you want to ensure it works well, you can edit your vimrc:\r\n\r\n```vim\r\nau BufNewFile,BufRead *.html,*.htm,*.shtml,*.stm set ft=jinja\r\n```\r\n\r\n\r\n## Bug report\r\n\r\nReport a bug on [GitHub Issues](https:\/\/github.com\/lepture\/vim-jinja\/issues).\r\n","4":"# Jinja for Vim\r\n\r\nJinja bundle for vim.\r\n\r\n\r\n## Feature\r\n\r\n1. full syntax support\r\n2. great indent support\r\n\r\n## Installation\r\n\r\n### Install with [Vundle](https:\/\/github.com\/gmarik\/vundle)\r\n\r\nIf you are not using vundle, you really should have a try.\r\nEdit your vimrc:\r\n\r\n    Bundle \"lepture\/vim-jinja\"\r\n\r\nAnd install it:\r\n\r\n    :so ~\/.vimrc\r\n    :BundleInstall\r\n\r\n\r\n### Install with [pathogen](https:\/\/github.com\/tpope\/vim-pathogen)\r\n\r\nIf you prefer tpope's pathogen, that's ok. Just clone it:\r\n\r\n    cd ~\/.vim\/bundle\r\n    git clone https:\/\/github.com\/lepture\/vim-jinja.git\r\n\r\n\r\n## Configuration\r\n\r\nNo configuration is needed, if you are using vim 7.2+, it will detect if\r\na html file is a jinja template.\r\n\r\nBut if you want to ensure it works well, you can edit your vimrc:\r\n\r\n```vim\r\nau BufNewFile,BufRead *.html,*.htm,*.shtml,*.stm set ft=jinja\r\n```\r\n\r\n\r\n## Bug report\r\n\r\nReport a bug on [GitHub Issues](https:\/\/github.com\/lepture\/vim-jinja\/issues).\r\n","install_details":"","5":"","first_name":"Hsiaoming","6":"Hsiaoming","last_name":"Yang","7":"Yang","releases":[{"0":"4213","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"vim-jinja.zip","4":"vim-jinja.zip","src_id":"18591","5":"18591","creation_date":"1347535018","6":"1347535018"}]},"4212":{"script_id":"4212","0":"4212","script_name":"RelOps","1":"RelOps","script_type":"utility","2":"utility","summary":"Relative line numbers for pending operations","3":"Relative line numbers for pending operations","description":"Vim 7.3 introduced an interesting functionality: relative line numbers.\r\n\r\nThe problem with Vim\u00e2\u0080\u0098s implementation is that you have to decide between relative and absolute line numbers;\r\nyou can\u00e2\u0080\u0098t have both of them at the same time and manual switching is a nuisance.\r\nMoreover on some computers relative line numbers might cause the screen to flicker when moving the cursor.\r\n\r\nRelOps gives you the best of both worlds. This plugin enables relative line numbering\r\nwhen it is most useful: in operator-pending mode\r\nAs soon as a motion is passed or the operation is canceled, relative line numbers\r\nare disabled again (unless 'rnu' is set by hand).","4":"Vim 7.3 introduced an interesting functionality: relative line numbers.\r\n\r\nThe problem with Vim\u00e2\u0080\u0098s implementation is that you have to decide between relative and absolute line numbers;\r\nyou can\u00e2\u0080\u0098t have both of them at the same time and manual switching is a nuisance.\r\nMoreover on some computers relative line numbers might cause the screen to flicker when moving the cursor.\r\n\r\nRelOps gives you the best of both worlds. This plugin enables relative line numbering\r\nwhen it is most useful: in operator-pending mode\r\nAs soon as a motion is passed or the operation is canceled, relative line numbers\r\nare disabled again (unless 'rnu' is set by hand).","install_details":"Extract into ~\/.vim \r\nRun :helptags ~\/.vim\/doc in vim\r\n\r\nOr use a plugin manager (Vundle, Pathogen, vim-addon-manager)","5":"Extract into ~\/.vim \r\nRun :helptags ~\/.vim\/doc in vim\r\n\r\nOr use a plugin manager (Vundle, Pathogen, vim-addon-manager)","first_name":"Mohammed","6":"Mohammed","last_name":"Chelouti","7":"Chelouti","releases":[{"0":"4212","vim_version":"7.3","1":"7.3","script_version":"1.1","2":"1.1","version_comment":"- Add support for user mappings.\r\n- Add mapping to temporarily enable rnu.\r\n- Fixed some bugs.","3":"- Add support for user mappings.\r\n- Add mapping to temporarily enable rnu.\r\n- Fixed some bugs.","package":"relops.zip","4":"relops.zip","src_id":"18671","5":"18671","creation_date":"1348360050","6":"1348360050"},{"0":"4212","vim_version":"7.3","1":"7.3","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"relops.zip","4":"relops.zip","src_id":"18589","5":"18589","creation_date":"1347488400","6":"1347488400"}]},"4211":{"script_id":"4211","0":"4211","script_name":"PinyinSearch","1":"PinyinSearch","script_type":"utility","2":"utility","summary":"Allow you to search Chinese by the first letter of Chinese pinyin","3":"Allow you to search Chinese by the first letter of Chinese pinyin","description":"INTRODUCTION:\r\n=============\r\n\tAllow searching of Chinese in VIM by the first letter of Chinese pinyin.\r\n\tVim中允许使用拼音首字母搜索中文.\r\n\r\nUSAGE:\r\n======\r\n\tcall PinyinSearch() and enter the target chars(first letters of the word),all the matching words will be highlighted, you can use 'n' and 'N' to jump.\r\n\r\n\tDuring a normal searching (i.e. you are searching for pure english),\tcall PinyinNext() and all the matching Chinese will also be highlighted.\r\n\r\n ------------------------------------------------------------------------------------------\r\n\r\n\tPinyinSearch()函数接受首字母输入,将高亮所有匹配的中英文,并允许用n,N跳转搜索结果.\r\n\r\n\t正在用'\/'搜索英文时,调用PinyinNext()函数可以将匹配的中文也加入搜索.\r\n\r\nEXAMPLE:\r\n========\r\n\r\n\t\t----------START OF EXAMPLE FILE----------------\r\n\t\t今天是个好日子,心想的事儿都能成,\r\n\r\n\t\t大能猫dn\r\n\t\t----------END OF EXAMPLE FILE----------------\r\n\tIn normal mode, enter '\/dn'\t, then \"dn\" will be highlighted.\r\n\tThen, call PinyinNext(), then \"大能\" and \"都能\" will also be highlighted, and the cursor will jump to \"大能\".\r\n\r\n\tOr you can just simply call PinyinSearch() and enter 'dn', both English and Chinese will be searched.\r\n\r\n\r\n\r\n\r\nThe Project is maintained at \r\nhttp:\/\/github.com\/ppwwyyxx\/vim-PinyinSearch","4":"INTRODUCTION:\r\n=============\r\n\tAllow searching of Chinese in VIM by the first letter of Chinese pinyin.\r\n\tVim中允许使用拼音首字母搜索中文.\r\n\r\nUSAGE:\r\n======\r\n\tcall PinyinSearch() and enter the target chars(first letters of the word),all the matching words will be highlighted, you can use 'n' and 'N' to jump.\r\n\r\n\tDuring a normal searching (i.e. you are searching for pure english),\tcall PinyinNext() and all the matching Chinese will also be highlighted.\r\n\r\n ------------------------------------------------------------------------------------------\r\n\r\n\tPinyinSearch()函数接受首字母输入,将高亮所有匹配的中英文,并允许用n,N跳转搜索结果.\r\n\r\n\t正在用'\/'搜索英文时,调用PinyinNext()函数可以将匹配的中文也加入搜索.\r\n\r\nEXAMPLE:\r\n========\r\n\r\n\t\t----------START OF EXAMPLE FILE----------------\r\n\t\t今天是个好日子,心想的事儿都能成,\r\n\r\n\t\t大能猫dn\r\n\t\t----------END OF EXAMPLE FILE----------------\r\n\tIn normal mode, enter '\/dn'\t, then \"dn\" will be highlighted.\r\n\tThen, call PinyinNext(), then \"大能\" and \"都能\" will also be highlighted, and the cursor will jump to \"大能\".\r\n\r\n\tOr you can just simply call PinyinSearch() and enter 'dn', both English and Chinese will be searched.\r\n\r\n\r\n\r\n\r\nThe Project is maintained at \r\nhttp:\/\/github.com\/ppwwyyxx\/vim-PinyinSearch","install_details":"1. copy PinyinSearch.vim to your plugin directory\r\n\r\n2. specify the location of dict file in your .vimrc, e.g.:\r\n\r\n\t\tlet g:PinyinSearch_Dict = '\/home\/wyx\/.vim\/PinyinSearch.dict'\r\n\r\n3. (optional)add your custom key map, e.g.:\r\n\r\n                nnoremap ? :call PinyinSearch()<CR>\r\n                \" I suggest use '?' to search Pinyin (since we have 'N', why using ? to search backward)\r\n                nnoremap <Leader>pn :call PinyinNext()<CR>","5":"1. copy PinyinSearch.vim to your plugin directory\r\n\r\n2. specify the location of dict file in your .vimrc, e.g.:\r\n\r\n\t\tlet g:PinyinSearch_Dict = '\/home\/wyx\/.vim\/PinyinSearch.dict'\r\n\r\n3. (optional)add your custom key map, e.g.:\r\n\r\n                nnoremap ? :call PinyinSearch()<CR>\r\n                \" I suggest use '?' to search Pinyin (since we have 'N', why using ? to search backward)\r\n                nnoremap <Leader>pn :call PinyinNext()<CR>","first_name":"Yuxin","6":"Yuxin","last_name":"Wu","7":"Wu","releases":[{"0":"4211","vim_version":"7.0","1":"7.0","script_version":"0.8","2":"0.8","version_comment":"change to a new dict; fix highlight problem","3":"change to a new dict; fix highlight problem","package":"PinyinSearch.tar.gz","4":"PinyinSearch.tar.gz","src_id":"19442","5":"19442","creation_date":"1359382659","6":"1359382659"},{"0":"4211","vim_version":"7.0","1":"7.0","script_version":"0.7","2":"0.7","version_comment":"fix bug on nomatch","3":"fix bug on nomatch","package":"PinyinSearch.tar.gz","4":"PinyinSearch.tar.gz","src_id":"19057","5":"19057","creation_date":"1354105012","6":"1354105012"},{"0":"4211","vim_version":"7.0","1":"7.0","script_version":"0.6","2":"0.6","version_comment":"easier to use with n\/N navigate","3":"easier to use with n\/N navigate","package":"vim-PinyinSearch.tar.gz","4":"vim-PinyinSearch.tar.gz","src_id":"18904","5":"18904","creation_date":"1351352221","6":"1351352221"},{"0":"4211","vim_version":"7.0","1":"7.0","script_version":"0.5","2":"0.5","version_comment":"Initial upload","3":"Initial upload","package":"PinyinSearch.tar.gz","4":"PinyinSearch.tar.gz","src_id":"18582","5":"18582","creation_date":"1347336265","6":"1347336265"}]},"4210":{"script_id":"4210","0":"4210","script_name":"easybuffer.vim","1":"easybuffer.vim","script_type":"utility","2":"utility","summary":"vim plugin to quickly switch between buffers","3":"vim plugin to quickly switch between buffers","description":"easybuffer.vim - is a simple plugin to quickly switch between buffers using corresponding keys \r\nor buffer numbers displayed in easybuffer quick switch window\r\n\r\nhttps:\/\/github.com\/troydm\/easybuffer.vim","4":"easybuffer.vim - is a simple plugin to quickly switch between buffers using corresponding keys \r\nor buffer numbers displayed in easybuffer quick switch window\r\n\r\nhttps:\/\/github.com\/troydm\/easybuffer.vim","install_details":"","5":"","first_name":"Dmitry","6":"Dmitry","last_name":"Geurkov","7":"Geurkov","releases":[{"0":"4210","vim_version":"7.3","1":"7.3","script_version":"0.1.5","2":"0.1.5","version_comment":"sorting added","3":"sorting added","package":"easybuffer.vim-0.1.5.zip","4":"easybuffer.vim-0.1.5.zip","src_id":"21372","5":"21372","creation_date":"1390650753","6":"1390650753"},{"0":"4210","vim_version":"7.0","1":"7.0","script_version":"0.1.4","2":"0.1.4","version_comment":"added some new options\r\nadded zoomwintab plugin support","3":"added some new options\r\nadded zoomwintab plugin support","package":"easybuffer.vim-0.1.4.zip","4":"easybuffer.vim-0.1.4.zip","src_id":"19510","5":"19510","creation_date":"1360782243","6":"1360782243"},{"0":"4210","vim_version":"7.0","1":"7.0","script_version":"0.1.3","2":"0.1.3","version_comment":"some changes\r\nclose buffer shortcut added","3":"some changes\r\nclose buffer shortcut added","package":"easybuffer.vim-0.1.3.zip","4":"easybuffer.vim-0.1.3.zip","src_id":"18633","5":"18633","creation_date":"1347906972","6":"1347906972"},{"0":"4210","vim_version":"7.0","1":"7.0","script_version":"0.1.2","2":"0.1.2","version_comment":"highlighting changed\r\nsome bugs fixed","3":"highlighting changed\r\nsome bugs fixed","package":"easybuffer.vim-0.1.2.zip","4":"easybuffer.vim-0.1.2.zip","src_id":"18600","5":"18600","creation_date":"1347658594","6":"1347658594"},{"0":"4210","vim_version":"7.0","1":"7.0","script_version":"0.1.1","2":"0.1.1","version_comment":"some bug fixes","3":"some bug fixes","package":"easybuffer.vim-0.1.1.zip","4":"easybuffer.vim-0.1.1.zip","src_id":"18587","5":"18587","creation_date":"1347445275","6":"1347445275"},{"0":"4210","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"easybuffer.vim-0.1.zip","4":"easybuffer.vim-0.1.zip","src_id":"18578","5":"18578","creation_date":"1347223306","6":"1347223306"}]},"4209":{"script_id":"4209","0":"4209","script_name":"Vimarok","1":"Vimarok","script_type":"utility","2":"utility","summary":"Plugin for control amarok via dbus-python","3":"Plugin for control amarok via dbus-python","description":"vimarok.txt     Show playlist and control amarok from vim via dbus-python.\r\n\r\nAuthor:     Lei Liu <liunx163@163.com>\r\nLicense:    Vim license, see license\r\nHomepage:   https:\/\/github.com\/liunx\/Vimarok\r\nVersion:    0.1.0\r\n\r\n==============================================================================\r\nContents                                            vimarok vimarok-contents\r\n        1. Intro ............................ vimarok-intro\r\n            Supported features .............. vimarok-features \r\n        2. Requirements ..................... vimarok-requirements\r\n        3. Installation ..................... vimarok-installation\r\n        4. Usage ............................ vimarok-usage\r\n            Commands ........................ vimarok-commands\r\n            Key mappings .................... vimarok-keys\r\n        5. Configuration .................... vimarok-configuration\r\n        6. Troubleshooting & Know issues .... vimarok-issues\r\n        7. History .......................... vimarok-history\r\n        8. Todo ............................. vimarok-todo\r\n        9. Credits .......................... vimarok-credits\r\n==============================================================================\r\n1. Intro                                                vimarok-intro\r\n\r\nVimarok is a plugin that used to control amarok music player. I am not means \r\nto make vim as a music player, I just let vim to cooperate with amarok,\r\nluckly, vim has many interfaces to other languages, so I use dbus-python to\r\njoin them together. If you like listen music while playing with vim, please\r\nhave a try.\r\n\r\n------------------------------------------------------------------------------\r\nSUPPORTED FEATURES                                      vimarok-features\r\n\r\nIt has the basic features like:\r\n\r\n  - play,pause,next,prev,back\/forword etc.\r\n  - show playlist in side bar.\r\n  - select & play the track in playlist.\r\n\r\n==============================================================================\r\n2. Requirements                                         vimarok-requirements\r\n\r\nYou need vim version > 7.0 and with +python feature compiled, also your \r\nsytem need to support dbus and has amarok with dbus feature installed,\r\ndbus-python module is needed. \r\n\r\n==============================================================================\r\n3. Installation                                         vimarok-installation\r\n\r\nJust put the files from plugin, doc, in right place, then restart your vim.\r\n\r\n==============================================================================\r\n4. Usage                                                vimarok-usage\r\n\r\nWhen you doing some work with vim while listening music, and you don't want\r\nto do switch between vim and amarok, in this situaction, you may want to do\r\nit in vim way. In this time, you can just type \":TogglePlayList\" to start \r\nup the playlist, and do something you like.\r\n\r\n------------------------------------------------------------------------------\r\nCOMMANDS                                                vimarok-commands\r\n\r\n:Toggleplaylist                                         :Toggleplaylist\r\n    Toggle the play list window.\r\n\r\n------------------------------------------------------------------------------\r\nKEY MAPPINGS                                            vimarok-keys\r\n\r\nThe keys below are just work in the playlist window.\r\n\r\n    >  : play next track'\r\n    <  : play previous track'\r\n    ]  : play forward'\r\n    [  : play backward'\r\n    +  : volume up'\r\n    -  : volume down'\r\n    p  : play'\r\n    s  : stop'\r\n    r  : toggle single track repeat'\r\n    m  : toggle mute'\r\n    o  : show amarok OSD'\r\n    $  : stop after current track'\r\n    L  : toggle play list loop mode'\r\n    R  : toggle play list random mode'\r\n    <CR>   : play track'\r\n    <Space> : switch between play & pause'\r\n    F1 : toggle the help contents'\r\n\r\n==============================================================================\r\n5. Configuration                                        vimarok-configuration\r\n\r\n                                                    g:amarok_volume_factor\r\ng:amarok_volume_factor\r\nDefault: 1\r\n\r\nThis option is a delta value when you volume up\/down by.\r\n\r\nExample:\r\n\r\n        let g:amarok_volume_factor = 2\r\n\r\n\r\n                                                    g:amarok_track_factor\r\ng:amarok_track_factor\r\nDefault: 1000\r\n\r\nThis option is a delta value when play for\/backward. Remember that the unit\r\nis ms, so it's better not to make it too small.\r\n\r\nExample:\r\n\r\n        let g:amarok_volume_factor = 2000\r\n\r\n\r\n                                                    g:amarok_playlist_width \r\ng:amarok_playlist_width\r\nDefault: 30\r\n\r\nThis option define the width of playlist window.\r\n\r\nExample:\r\n\r\n        let g:amarok_playlist_width = 30\r\n\r\n\r\n                                                    g:amarok_playlist_left \r\ng:amarok_playlist_left\r\nDefault: 0\r\n\r\nBy default, the playlist will open in right-hand side.\r\n\r\nExample:\r\n\r\n        let g:amarok_playlist_left = 1\r\n\r\n\r\n\r\n==============================================================================\r\n6. Troubleshooting & Know issues                        vimarok-issues\r\n\r\n==============================================================================\r\n7. History                                              vimarok-history\r\n\r\n==============================================================================\r\n8. Todo                                                 vimarok-todo\r\n\r\n==============================================================================\r\n9. Credits                                              vimarok-credits\r\n\r\nThis plugin's window manage function was heavily inspired by the 'Tagbar' \r\n& 'Taglist' plugin by Jan Larres & Yegappan Lakshmanan and uses a few amount \r\nof code from them.\r\n\r\nOriginal taglist copyright notice:\r\nPermission is hereby granted to use and distribute this code, with or without\r\nmodifications, provided that this copyright notice is copied with it. Like\r\nanything else that's free, taglist.vim is provided *as is* and comes with no\r\nwarranty of any kind, either expressed or implied. In no event will the\r\ncopyright holder be liable for any damamges resulting from the use of this\r\nsoftware.\r\n\r\n==============================================================================\r\n vim: tw=78 ts=8 sw=4 sts=4 et ft=help\r\n","4":"vimarok.txt     Show playlist and control amarok from vim via dbus-python.\r\n\r\nAuthor:     Lei Liu <liunx163@163.com>\r\nLicense:    Vim license, see license\r\nHomepage:   https:\/\/github.com\/liunx\/Vimarok\r\nVersion:    0.1.0\r\n\r\n==============================================================================\r\nContents                                            vimarok vimarok-contents\r\n        1. Intro ............................ vimarok-intro\r\n            Supported features .............. vimarok-features \r\n        2. Requirements ..................... vimarok-requirements\r\n        3. Installation ..................... vimarok-installation\r\n        4. Usage ............................ vimarok-usage\r\n            Commands ........................ vimarok-commands\r\n            Key mappings .................... vimarok-keys\r\n        5. Configuration .................... vimarok-configuration\r\n        6. Troubleshooting & Know issues .... vimarok-issues\r\n        7. History .......................... vimarok-history\r\n        8. Todo ............................. vimarok-todo\r\n        9. Credits .......................... vimarok-credits\r\n==============================================================================\r\n1. Intro                                                vimarok-intro\r\n\r\nVimarok is a plugin that used to control amarok music player. I am not means \r\nto make vim as a music player, I just let vim to cooperate with amarok,\r\nluckly, vim has many interfaces to other languages, so I use dbus-python to\r\njoin them together. If you like listen music while playing with vim, please\r\nhave a try.\r\n\r\n------------------------------------------------------------------------------\r\nSUPPORTED FEATURES                                      vimarok-features\r\n\r\nIt has the basic features like:\r\n\r\n  - play,pause,next,prev,back\/forword etc.\r\n  - show playlist in side bar.\r\n  - select & play the track in playlist.\r\n\r\n==============================================================================\r\n2. Requirements                                         vimarok-requirements\r\n\r\nYou need vim version > 7.0 and with +python feature compiled, also your \r\nsytem need to support dbus and has amarok with dbus feature installed,\r\ndbus-python module is needed. \r\n\r\n==============================================================================\r\n3. Installation                                         vimarok-installation\r\n\r\nJust put the files from plugin, doc, in right place, then restart your vim.\r\n\r\n==============================================================================\r\n4. Usage                                                vimarok-usage\r\n\r\nWhen you doing some work with vim while listening music, and you don't want\r\nto do switch between vim and amarok, in this situaction, you may want to do\r\nit in vim way. In this time, you can just type \":TogglePlayList\" to start \r\nup the playlist, and do something you like.\r\n\r\n------------------------------------------------------------------------------\r\nCOMMANDS                                                vimarok-commands\r\n\r\n:Toggleplaylist                                         :Toggleplaylist\r\n    Toggle the play list window.\r\n\r\n------------------------------------------------------------------------------\r\nKEY MAPPINGS                                            vimarok-keys\r\n\r\nThe keys below are just work in the playlist window.\r\n\r\n    >  : play next track'\r\n    <  : play previous track'\r\n    ]  : play forward'\r\n    [  : play backward'\r\n    +  : volume up'\r\n    -  : volume down'\r\n    p  : play'\r\n    s  : stop'\r\n    r  : toggle single track repeat'\r\n    m  : toggle mute'\r\n    o  : show amarok OSD'\r\n    $  : stop after current track'\r\n    L  : toggle play list loop mode'\r\n    R  : toggle play list random mode'\r\n    <CR>   : play track'\r\n    <Space> : switch between play & pause'\r\n    F1 : toggle the help contents'\r\n\r\n==============================================================================\r\n5. Configuration                                        vimarok-configuration\r\n\r\n                                                    g:amarok_volume_factor\r\ng:amarok_volume_factor\r\nDefault: 1\r\n\r\nThis option is a delta value when you volume up\/down by.\r\n\r\nExample:\r\n\r\n        let g:amarok_volume_factor = 2\r\n\r\n\r\n                                                    g:amarok_track_factor\r\ng:amarok_track_factor\r\nDefault: 1000\r\n\r\nThis option is a delta value when play for\/backward. Remember that the unit\r\nis ms, so it's better not to make it too small.\r\n\r\nExample:\r\n\r\n        let g:amarok_volume_factor = 2000\r\n\r\n\r\n                                                    g:amarok_playlist_width \r\ng:amarok_playlist_width\r\nDefault: 30\r\n\r\nThis option define the width of playlist window.\r\n\r\nExample:\r\n\r\n        let g:amarok_playlist_width = 30\r\n\r\n\r\n                                                    g:amarok_playlist_left \r\ng:amarok_playlist_left\r\nDefault: 0\r\n\r\nBy default, the playlist will open in right-hand side.\r\n\r\nExample:\r\n\r\n        let g:amarok_playlist_left = 1\r\n\r\n\r\n\r\n==============================================================================\r\n6. Troubleshooting & Know issues                        vimarok-issues\r\n\r\n==============================================================================\r\n7. History                                              vimarok-history\r\n\r\n==============================================================================\r\n8. Todo                                                 vimarok-todo\r\n\r\n==============================================================================\r\n9. Credits                                              vimarok-credits\r\n\r\nThis plugin's window manage function was heavily inspired by the 'Tagbar' \r\n& 'Taglist' plugin by Jan Larres & Yegappan Lakshmanan and uses a few amount \r\nof code from them.\r\n\r\nOriginal taglist copyright notice:\r\nPermission is hereby granted to use and distribute this code, with or without\r\nmodifications, provided that this copyright notice is copied with it. Like\r\nanything else that's free, taglist.vim is provided *as is* and comes with no\r\nwarranty of any kind, either expressed or implied. In no event will the\r\ncopyright holder be liable for any damamges resulting from the use of this\r\nsoftware.\r\n\r\n==============================================================================\r\n vim: tw=78 ts=8 sw=4 sts=4 et ft=help\r\n","install_details":"cp plugin\/amarok.vim to <your home dir>\/.vim\/plugin\/\r\ncp doc\/amarok.txt to <your home dir>\/.vim\/doc\/\r\n","5":"cp plugin\/amarok.vim to <your home dir>\/.vim\/plugin\/\r\ncp doc\/amarok.txt to <your home dir>\/.vim\/doc\/\r\n","first_name":"Lei","6":"Lei","last_name":"Liu","7":"Liu","releases":[{"0":"4209","vim_version":"7.0","1":"7.0","script_version":"0.1.2","2":"0.1.2","version_comment":"fix add help & playlist many times problem, thanks 刘铮臻<liuzhengzhen9036@gmail.com> for his feed back & bug report!","3":"fix add help & playlist many times problem, thanks 刘铮臻<liuzhengzhen9036@gmail.com> for his feed back & bug report!","package":"liunx-Vimarok-630ad9a.zip","4":"liunx-Vimarok-630ad9a.zip","src_id":"18712","5":"18712","creation_date":"1348914650","6":"1348914650"},{"0":"4209","vim_version":"7.0","1":"7.0","script_version":"0.1.1","2":"0.1.1","version_comment":"fix play track problem, that when you select a track, but display another track.","3":"fix play track problem, that when you select a track, but display another track.","package":"liunx-Vimarok-67096df.zip","4":"liunx-Vimarok-67096df.zip","src_id":"18576","5":"18576","creation_date":"1347207561","6":"1347207561"},{"0":"4209","vim_version":"7.0","1":"7.0","script_version":"0.1.0","2":"0.1.0","version_comment":"Initial upload","3":"Initial upload","package":"liunx-Vimarok-86a176c.zip","4":"liunx-Vimarok-86a176c.zip","src_id":"18575","5":"18575","creation_date":"1347206768","6":"1347206768"}]},"4208":{"script_id":"4208","0":"4208","script_name":"nant 0.91 errorformat","1":"nant 0.91 errorformat","script_type":"utility","2":"utility","summary":"nant 0.91 errorformat","3":"nant 0.91 errorformat","description":"Nothing much","4":"Nothing much","install_details":"just put it into your compiler directory","5":"just put it into your compiler directory","first_name":"quangang","6":"quangang","last_name":"sheng","7":"sheng","releases":[{"0":"4208","vim_version":"7.3","1":"7.3","script_version":"1.2","2":"1.2","version_comment":"add support too filename(lineno), and remove other messages which are neither errors nor warnings","3":"add support too filename(lineno), and remove other messages which are neither errors nor warnings","package":"nant.vim","4":"nant.vim","src_id":"20929","5":"20929","creation_date":"1382089468","6":"1382089468"},{"0":"4208","vim_version":"7.3","1":"7.3","script_version":"1.1","2":"1.1","version_comment":"add support for such situation:\r\nFILE_NAME:(LINENO:COLUMNNO): (Location of symbol of previous error\/warning)","3":"add support for such situation:\r\nFILE_NAME:(LINENO:COLUMNNO): (Location of symbol of previous error\/warning)","package":"nant.vim","4":"nant.vim","src_id":"18571","5":"18571","creation_date":"1347174069","6":"1347174069"},{"0":"4208","vim_version":"7.3","1":"7.3","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"nant.vim","4":"nant.vim","src_id":"18570","5":"18570","creation_date":"1347159581","6":"1347159581"}]},"4207":{"script_id":"4207","0":"4207","script_name":"vim-clojure-sql","1":"vim-clojure-sql","script_type":"syntax","2":"syntax","summary":"SQL syntax-highlighting within Clojure files","3":"SQL syntax-highlighting within Clojure files","description":"A very simple plugin to enable SQL syntax highlighting inside strings in a Clojure file. If you can handle the visual trip of two syntax highlighters co-existing, this plugin will provide. ","4":"A very simple plugin to enable SQL syntax highlighting inside strings in a Clojure file. If you can handle the visual trip of two syntax highlighters co-existing, this plugin will provide. ","install_details":"Install vimclojure.\r\nInstall Pathogen.\r\nUnpack this plugin to ~\/.vim\/bundle\/vim-clojure-sql.","5":"Install vimclojure.\r\nInstall Pathogen.\r\nUnpack this plugin to ~\/.vim\/bundle\/vim-clojure-sql.","first_name":"Kris","6":"Kris","last_name":"Jenkins","7":"Jenkins","releases":[{"0":"4207","vim_version":"7.3","1":"7.3","script_version":"1.0.0","2":"1.0.0","version_comment":"Initial upload","3":"Initial upload","package":"vim-clojure-sql.tar.gz","4":"vim-clojure-sql.tar.gz","src_id":"18564","5":"18564","creation_date":"1347029942","6":"1347029942"}]},"4206":{"script_id":"4206","0":"4206","script_name":"vim-java-sql","1":"vim-java-sql","script_type":"syntax","2":"syntax","summary":"SQL syntax-highlighting within .java files.","3":"SQL syntax-highlighting within .java files.","description":"A very simple plugin to enable SQL syntax highlighting inside strings in a\r\nJava file. If you can handle the visual trip of two syntax highlighters\r\nco-existing, this plugin will provide.","4":"A very simple plugin to enable SQL syntax highlighting inside strings in a\r\nJava file. If you can handle the visual trip of two syntax highlighters\r\nco-existing, this plugin will provide.","install_details":"install details\r\nInstall Pathogen (https:\/\/github.com\/tpope\/vim-pathogen\/). \r\nUnpack to ~\/.vim\/bundle\/vim-java-sql.","5":"install details\r\nInstall Pathogen (https:\/\/github.com\/tpope\/vim-pathogen\/). \r\nUnpack to ~\/.vim\/bundle\/vim-java-sql.","first_name":"Kris","6":"Kris","last_name":"Jenkins","7":"Jenkins","releases":[{"0":"4206","vim_version":"7.3","1":"7.3","script_version":"1.0.0","2":"1.0.0","version_comment":"Initial upload","3":"Initial upload","package":"vim-java-sql.tar.gz","4":"vim-java-sql.tar.gz","src_id":"18563","5":"18563","creation_date":"1347029797","6":"1347029797"}]},"4205":{"script_id":"4205","0":"4205","script_name":"cppSyntaxCheck","1":"cppSyntaxCheck","script_type":"utility","2":"utility","summary":"A syntax check script for cpp","3":"A syntax check script for cpp","description":"This a script use g++ as a parser to check the syntax of cpp source code, and show where the errors and warnings are. Installion is in a easy way and everytime you save the file, syntax errors and warnings are showed.\r\nYou can also check errors in quickfix window by using command :cw\r\nSee the install details for install guide, if you find any bugs or method to make it better, please contact me using e-mail: phonzia@gmail.com\r\n\r\nKey binding:\r\n<Leader>s      go to next signed error or warning line\r\n\r\nYou can also download it from github:\r\nhttps:\/\/github.com\/phonzia\/cppSyntaxCheck.git","4":"This a script use g++ as a parser to check the syntax of cpp source code, and show where the errors and warnings are. Installion is in a easy way and everytime you save the file, syntax errors and warnings are showed.\r\nYou can also check errors in quickfix window by using command :cw\r\nSee the install details for install guide, if you find any bugs or method to make it better, please contact me using e-mail: phonzia@gmail.com\r\n\r\nKey binding:\r\n<Leader>s      go to next signed error or warning line\r\n\r\nYou can also download it from github:\r\nhttps:\/\/github.com\/phonzia\/cppSyntaxCheck.git","install_details":"Put the script cppSyntaxCheck.vim in folder ~\/.vim\/plugin, then it works\r\nYou can also add statement like below in order to adjust to your environment\r\nlet g:include_path=\":..\/include:.\/include:.\/tinyxml\"\r\nlet g:compile_flag=\"-D_LINUX_\"\r\nlet g:cpp_compiler=\"\/usr\/bin\/g++\"\r\nlet g:enable_warning=1\r\nlet g:cpp_compiler=\"LANG=C g++ -Wall\"\r\nlet g:longest_text=120\r\n\r\n","5":"Put the script cppSyntaxCheck.vim in folder ~\/.vim\/plugin, then it works\r\nYou can also add statement like below in order to adjust to your environment\r\nlet g:include_path=\":..\/include:.\/include:.\/tinyxml\"\r\nlet g:compile_flag=\"-D_LINUX_\"\r\nlet g:cpp_compiler=\"\/usr\/bin\/g++\"\r\nlet g:enable_warning=1\r\nlet g:cpp_compiler=\"LANG=C g++ -Wall\"\r\nlet g:longest_text=120\r\n\r\n","first_name":"Phonzia","6":"Phonzia","last_name":"Yang","7":"Yang","releases":[{"0":"4205","vim_version":"7.3","1":"7.3","script_version":"1.1","2":"1.1","version_comment":"1.Fix A bug which may cause vim crash\r\n2.Optimized for better performance","3":"1.Fix A bug which may cause vim crash\r\n2.Optimized for better performance","package":"cppSyntaxCheck.vim","4":"cppSyntaxCheck.vim","src_id":"20174","5":"20174","creation_date":"1369044233","6":"1369044233"},{"0":"4205","vim_version":"7.3","1":"7.3","script_version":"0.6","2":"0.6","version_comment":"Now you can check errors in quickfix window","3":"Now you can check errors in quickfix window","package":"cppSyntaxCheck.vim","4":"cppSyntaxCheck.vim","src_id":"20148","5":"20148","creation_date":"1368717240","6":"1368717240"},{"0":"4205","vim_version":"7.3","1":"7.3","script_version":"0.5","2":"0.5","version_comment":"1. Show a hint message instead of error\/warning message if error\/warning message is too long. You can custumize your longest length. ","3":"1. Show a hint message instead of error\/warning message if error\/warning message is too long. You can custumize your longest length. ","package":"cppSyntaxCheck.vim","4":"cppSyntaxCheck.vim","src_id":"20146","5":"20146","creation_date":"1368678371","6":"1368678371"},{"0":"4205","vim_version":"7.3","1":"7.3","script_version":"0.4","2":"0.4","version_comment":"Modifies:\r\n1. Add a shortcut key <Leader>s to go to signed error\r\n2. Optimized to be faster","3":"Modifies:\r\n1. Add a shortcut key <Leader>s to go to signed error\r\n2. Optimized to be faster","package":"cppSyntaxCheck.vim","4":"cppSyntaxCheck.vim","src_id":"20112","5":"20112","creation_date":"1368460718","6":"1368460718"},{"0":"4205","vim_version":"7.3","1":"7.3","script_version":"0.3","2":"0.3","version_comment":"modifies:\r\n1. The analyze results will not lost when switching between buffers in this version, we don't need to resave to trigger the analyze again when swiching to another file and switching back later","3":"modifies:\r\n1. The analyze results will not lost when switching between buffers in this version, we don't need to resave to trigger the analyze again when swiching to another file and switching back later","package":"cppSyntaxCheck.vim","4":"cppSyntaxCheck.vim","src_id":"18549","5":"18549","creation_date":"1346813255","6":"1346813255"},{"0":"4205","vim_version":"7.3","1":"7.3","script_version":"0.2","2":"0.2","version_comment":"add option g:enable_warning to enable and disable warnings","3":"add option g:enable_warning to enable and disable warnings","package":"cppSyntaxCheck.vim","4":"cppSyntaxCheck.vim","src_id":"18544","5":"18544","creation_date":"1346753046","6":"1346753046"},{"0":"4205","vim_version":"7.3","1":"7.3","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"cppSyntaxCheck.vim","4":"cppSyntaxCheck.vim","src_id":"18542","5":"18542","creation_date":"1346713666","6":"1346713666"}]},"4204":{"script_id":"4204","0":"4204","script_name":"My Code Style Toggle","1":"My Code Style Toggle","script_type":"utility","2":"utility","summary":"help you toggle the style of the code blocks easily !","3":"help you toggle the style of the code blocks easily !","description":"Your boss ask for some specific unique style of code blocks ?\r\nThis can help you toggle it easily and you can keep your own habit by this way .\r\njust try to use <F5> and <F6> to toggle !\r\n\r\nif (a == b) {\r\n        r = true ;\r\n}\r\n\r\nor :\r\n\r\nif (a == b)\r\n{\r\n        r = true ;\r\n}\r\n","4":"Your boss ask for some specific unique style of code blocks ?\r\nThis can help you toggle it easily and you can keep your own habit by this way .\r\njust try to use <F5> and <F6> to toggle !\r\n\r\nif (a == b) {\r\n        r = true ;\r\n}\r\n\r\nor :\r\n\r\nif (a == b)\r\n{\r\n        r = true ;\r\n}\r\n","install_details":"put the mycodestyle.vim file to dir vim\/vim73\/plugin or vim\/vimfiles\/plugin .\r\nthe default keys mapped is <F5> and <F6>. And you can change these by editting the source code.\r\n","5":"put the mycodestyle.vim file to dir vim\/vim73\/plugin or vim\/vimfiles\/plugin .\r\nthe default keys mapped is <F5> and <F6>. And you can change these by editting the source code.\r\n","first_name":"luo","6":"luo","last_name":"chen","7":"chen","releases":[{"0":"4204","vim_version":"7.3","1":"7.3","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"mycodestyle.vim","4":"mycodestyle.vim","src_id":"18530","5":"18530","creation_date":"1346581270","6":"1346581270"}]},"4203":{"script_id":"4203","0":"4203","script_name":"tropikos","1":"tropikos","script_type":"color scheme","2":"color scheme","summary":"Tropikos color scheme","3":"Tropikos color scheme","description":"Github repository and screenshots: \r\nhttps:\/\/github.com\/blackgate\/tropikos-vim-theme","4":"Github repository and screenshots: \r\nhttps:\/\/github.com\/blackgate\/tropikos-vim-theme","install_details":"Just copy the contents to your .vim folder, then run \"colorscheme tropikos\" on vim or add to the .vimrc file.","5":"Just copy the contents to your .vim folder, then run \"colorscheme tropikos\" on vim or add to the .vimrc file.","first_name":"Hugo","6":"Hugo","last_name":"Pires","7":"Pires","releases":[{"0":"4203","vim_version":"7.0","1":"7.0","script_version":"1.1","2":"1.1","version_comment":"Fixed some colors","3":"Fixed some colors","package":"tropikos.zip","4":"tropikos.zip","src_id":"18682","5":"18682","creation_date":"1348528360","6":"1348528360"},{"0":"4203","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"tropikos.zip","4":"tropikos.zip","src_id":"18528","5":"18528","creation_date":"1346534399","6":"1346534399"}]},"4202":{"script_id":"4202","0":"4202","script_name":"altr","1":"altr","script_type":"utility","2":"utility","summary":"Switch to the missing file without interaction","3":"Switch to the missing file without interaction","description":"*altr* is a Vim plugin to switch files easily.\n\nFor example, suppose that you are developing a Vim plugin which is called\n\"foo\".  You often edit specific files such as \"autoload\/foo.vim\",\n\"doc\/foo.txt\", \"plugin\/foo.vim\", etc.  Sometimes one of the files is not\ndisplayed in any window.  So you have to open the missing file explicitly.\nBut there are many ways to open the missing file.  How do you open the missing\nfile?  |:edit|, |:buffer|, or your favorite buffer-management plugin?\n\nWhatever you choose, you have to type some keys to specify what the missing\nfile is.  So there is no way to open the missing file WITHOUT INTERACTION.\nYou'll probably wish if there is a command to open the missing file without\ninteraction.  This plugin, altr, provides the command.\n\nThe best keys and Ex commands to open the missing file are varied for each\nuser.  So that altr doesn't define neither the default keys nor the default Ex\ncommands.  See |altr-examples| for details.\n\n\nRequirements:\n- Vim 7.2 or later\n\nLatest version:\nhttp:\/\/github.com\/kana\/vim-altr\n\nDocument in HTML format:\nhttp:\/\/vim-doc.heroku.com\/view?https:\/\/github.com\/kana\/vim-altr\/blob\/master\/doc\/altr.txt","4":"*altr* is a Vim plugin to switch files easily.\n\nFor example, suppose that you are developing a Vim plugin which is called\n\"foo\".  You often edit specific files such as \"autoload\/foo.vim\",\n\"doc\/foo.txt\", \"plugin\/foo.vim\", etc.  Sometimes one of the files is not\ndisplayed in any window.  So you have to open the missing file explicitly.\nBut there are many ways to open the missing file.  How do you open the missing\nfile?  |:edit|, |:buffer|, or your favorite buffer-management plugin?\n\nWhatever you choose, you have to type some keys to specify what the missing\nfile is.  So there is no way to open the missing file WITHOUT INTERACTION.\nYou'll probably wish if there is a command to open the missing file without\ninteraction.  This plugin, altr, provides the command.\n\nThe best keys and Ex commands to open the missing file are varied for each\nuser.  So that altr doesn't define neither the default keys nor the default Ex\ncommands.  See |altr-examples| for details.\n\n\nRequirements:\n- Vim 7.2 or later\n\nLatest version:\nhttp:\/\/github.com\/kana\/vim-altr\n\nDocument in HTML format:\nhttp:\/\/vim-doc.heroku.com\/view?https:\/\/github.com\/kana\/vim-altr\/blob\/master\/doc\/altr.txt","install_details":"...","5":"...","first_name":"Kana","6":"Kana","last_name":"Natsuno","7":"Natsuno","releases":[{"0":"4202","vim_version":"7.0","1":"7.0","script_version":"0.0.2","2":"0.0.2","version_comment":"Initial upload","3":"Initial upload","package":"vim-altr-0.0.2.zip","4":"vim-altr-0.0.2.zip","src_id":"18520","5":"18520","creation_date":"1346480494","6":"1346480494"}]},"4201":{"script_id":"4201","0":"4201","script_name":"tabpagecd","1":"tabpagecd","script_type":"utility","2":"utility","summary":"Use one tab page per project","3":"Use one tab page per project","description":"*tabpagecd* is a Vim plugin to use one tab page per project.  It records\na current working directory for each tab page, and it changes the current\nworking directory whenever you activate another tab page.  So that it makes\neasy to deal with project-local files.\n\n\nRequirements:\n- Vim 7.3 or later\n\nLatest version:\nhttp:\/\/github.com\/kana\/vim-tabpagecd\n\nDocument in HTML format:\nhttp:\/\/vim-doc.heroku.com\/view?https:\/\/github.com\/kana\/vim-tabpagecd\/blob\/master\/doc\/tabpagecd.txt","4":"*tabpagecd* is a Vim plugin to use one tab page per project.  It records\na current working directory for each tab page, and it changes the current\nworking directory whenever you activate another tab page.  So that it makes\neasy to deal with project-local files.\n\n\nRequirements:\n- Vim 7.3 or later\n\nLatest version:\nhttp:\/\/github.com\/kana\/vim-tabpagecd\n\nDocument in HTML format:\nhttp:\/\/vim-doc.heroku.com\/view?https:\/\/github.com\/kana\/vim-tabpagecd\/blob\/master\/doc\/tabpagecd.txt","install_details":"...","5":"...","first_name":"Kana","6":"Kana","last_name":"Natsuno","7":"Natsuno","releases":[{"0":"4201","vim_version":"7.0","1":"7.0","script_version":"0.0.1","2":"0.0.1","version_comment":"Initial upload","3":"Initial upload","package":"vim-tabpagecd-0.0.1.zip","4":"vim-tabpagecd-0.0.1.zip","src_id":"18519","5":"18519","creation_date":"1346473567","6":"1346473567"}]},"4200":{"script_id":"4200","0":"4200","script_name":"transliterate","1":"transliterate","script_type":"utility","2":"utility","summary":"Text transliteration","3":"Text transliteration","description":"NOTE: The plugin is not maintained anymore. Even if someone finds a critical bug. Tough luck.\r\n\r\n\r\n\r\nThis plugin allows transforming one set of symbols into another.\r\n\r\nCurrently the following transformations are supported out-of-the-box:\r\n * X-SAMPA to IPA\r\n * Latin to Russian Cyrillic\r\n\r\nIt's possible and easy to add custom transformations.","4":"NOTE: The plugin is not maintained anymore. Even if someone finds a critical bug. Tough luck.\r\n\r\n\r\n\r\nThis plugin allows transforming one set of symbols into another.\r\n\r\nCurrently the following transformations are supported out-of-the-box:\r\n * X-SAMPA to IPA\r\n * Latin to Russian Cyrillic\r\n\r\nIt's possible and easy to add custom transformations.","install_details":"Unpack the transliterate directory in the archive somewhere into the runtime path.","5":"Unpack the transliterate directory in the archive somewhere into the runtime path.","first_name":"Fanael","6":"Fanael","last_name":"Linithien","7":"Linithien","releases":[{"0":"4200","vim_version":"7.0","1":"7.0","script_version":"0.2.3.1","2":"0.2.3.1","version_comment":"Added missing _o and _r in X-SAMPA mode.","3":"Added missing _o and _r in X-SAMPA mode.","package":"transliterate.zip","4":"transliterate.zip","src_id":"19165","5":"19165","creation_date":"1355246860","6":"1355246860"},{"0":"4200","vim_version":"7.0","1":"7.0","script_version":"0.2.3","2":"0.2.3","version_comment":"Added a command that sets the transliteration mode to make vim know how to complete the mode names","3":"Added a command that sets the transliteration mode to make vim know how to complete the mode names","package":"transliterate.zip","4":"transliterate.zip","src_id":"18626","5":"18626","creation_date":"1347795289","6":"1347795289"},{"0":"4200","vim_version":"7.0","1":"7.0","script_version":"0.2.2.1","2":"0.2.2.1","version_comment":"* Bugfixes for Russian Cyrillic\r\n* Documentation improvements","3":"* Bugfixes for Russian Cyrillic\r\n* Documentation improvements","package":"transliterate.zip","4":"transliterate.zip","src_id":"18624","5":"18624","creation_date":"1347791107","6":"1347791107"},{"0":"4200","vim_version":"7.0","1":"7.0","script_version":"0.2.2","2":"0.2.2","version_comment":"Added support for Russian Cyrillic","3":"Added support for Russian Cyrillic","package":"transliterate.zip","4":"transliterate.zip","src_id":"18615","5":"18615","creation_date":"1347723409","6":"1347723409"},{"0":"4200","vim_version":"7.0","1":"7.0","script_version":"0.2.1","2":"0.2.1","version_comment":"User-defined modes should now work correctly","3":"User-defined modes should now work correctly","package":"transliterate.zip","4":"transliterate.zip","src_id":"18612","5":"18612","creation_date":"1347715785","6":"1347715785"},{"0":"4200","vim_version":"7.0","1":"7.0","script_version":"0.2","2":"0.2","version_comment":"* Different key mapping configuration method\r\n* Support for user-defined transliteration modes","3":"* Different key mapping configuration method\r\n* Support for user-defined transliteration modes","package":"transliterate.zip","4":"transliterate.zip","src_id":"18532","5":"18532","creation_date":"1346607282","6":"1346607282"},{"0":"4200","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"transliterate.zip","4":"transliterate.zip","src_id":"18518","5":"18518","creation_date":"1346438251","6":"1346438251"}]},"4199":{"script_id":"4199","0":"4199","script_name":"tinykeymap","1":"tinykeymap","script_type":"utility","2":"utility","summary":"Tiny, temporary keymaps","3":"Tiny, temporary keymaps","description":"This plugin is a 90% clone of Andy Wokula's tinymode (vimscript #2223). \r\nIt takes a different approach that hopefully avoids certain problems \r\nwithout creating new ones. tinymode actually creates maps to do its job, \r\ntinykeymap only creates maps for the entry sequence and uses the \r\n|getchar()| function to handle further input.\r\n\r\nThis plugin lets users define \"temporary keymaps\", a.k.a. tinykeymaps, \r\nwith the |tinykeymap#EnterMap()| function. Users can define a map to \r\nactivate a tinykeymap. Users can then use single key shortcuts to \r\ntrigger commands defined with |tinykeymap#Map()|. Pressing an undefined \r\nkey or <Esc>, deactivates the tinykeymap.\r\n\r\ntinykeymap comes with some example maps to make it easier to ...\r\n\r\n    buffers ... navigate\/operate on buffers\r\n    diff    ... navigate\/operate on |diff|s\r\n    filter  ... \"filter\" text in a buffer using folds\r\n    lines   ... navigate\/operate on lines (similar to vimscript #4140)\r\n    loc     ... navigate the |location-list|\r\n    qfl     ... navigate the |quickfix| list\r\n    tabs    ... navigate\/operate on tabs\r\n    undo    ... navigate\/operate on the undo tree (with optional support for \r\n                vimscript #4177)\r\n    windows ... navigate\/operate on windows\r\n\r\nExample definition for a \"tabs\" tinykeymap (heavily based on Andy \r\nWokula's tabs mode for tinymode): >\r\n\r\n    call tinykeymap#EnterMap('tabs', 'gt', {'name': 'Tabs mode'})\r\n    call tinykeymap#Map('tabs', 'n', 'tabnew') \r\n    call tinykeymap#Map('tabs', 't', 'norm! gt') \r\n    call tinykeymap#Map('tabs', 'T', 'norm! gT') \r\n    call tinykeymap#Map(\"tabs\", \"^\", \"tabfirst\")\r\n    call tinykeymap#Map(\"tabs\", \"$\", \"tablast\")\r\n    call tinykeymap#Map(\"tabs\", \"c\", \"tabclose\")\r\n\r\nExample use of the above tinykeymap: E.g. pressing gt3n^c2t will:\r\n\r\n    gt ... Enter tabs mode\r\n    3n ... create 3 new tabs,\r\n    ^  ... select the first one,\r\n    c  ... close it, and\r\n    2t ... move to the second tab on the right.\r\n\r\nA tinykeymap is exited (1) by pressing <Esc> or (2) by timeout (see \r\n|g:tinykeymap#timeout|).\r\n\r\ntinykeymap comes with the following pre-defined tinykeymaps:\r\n\r\n    tabs    gt         :: Operate on tabs\r\n    windows <C-W>      :: Operate on windows\r\n    buffers <Leader>mb :: Operate on buffers\r\n    diff    <Leader>md :: Make it easier to work with |diff|s\r\n    filter  <Leader>mf :: Fold lines not matching some pattern (default: word \r\n                         under cursor)\r\n    lines   <Leader>ml :: Operate on lines\r\n    loc     <Leader>mo :: Operate on the |location-list|\r\n    qfl     <Leader>mq :: Operate on the |quickfix| list\r\n    undo    <Leader>mu :: Operate on the |undo| tree\r\n\r\nDifferences to tinymode:\r\n\r\n    - tinykeymaps and maps may have options (optional)\r\n    - tinykeymaps can be buffer-local\r\n    - dealing with [count] is easier (if a map contains \"<count>\", this \r\n      placeholder is replaced with the current [count], i.e. a \r\n      previously entered number; otherwise the expression is evaluated \r\n      [count] times)\r\n","4":"This plugin is a 90% clone of Andy Wokula's tinymode (vimscript #2223). \r\nIt takes a different approach that hopefully avoids certain problems \r\nwithout creating new ones. tinymode actually creates maps to do its job, \r\ntinykeymap only creates maps for the entry sequence and uses the \r\n|getchar()| function to handle further input.\r\n\r\nThis plugin lets users define \"temporary keymaps\", a.k.a. tinykeymaps, \r\nwith the |tinykeymap#EnterMap()| function. Users can define a map to \r\nactivate a tinykeymap. Users can then use single key shortcuts to \r\ntrigger commands defined with |tinykeymap#Map()|. Pressing an undefined \r\nkey or <Esc>, deactivates the tinykeymap.\r\n\r\ntinykeymap comes with some example maps to make it easier to ...\r\n\r\n    buffers ... navigate\/operate on buffers\r\n    diff    ... navigate\/operate on |diff|s\r\n    filter  ... \"filter\" text in a buffer using folds\r\n    lines   ... navigate\/operate on lines (similar to vimscript #4140)\r\n    loc     ... navigate the |location-list|\r\n    qfl     ... navigate the |quickfix| list\r\n    tabs    ... navigate\/operate on tabs\r\n    undo    ... navigate\/operate on the undo tree (with optional support for \r\n                vimscript #4177)\r\n    windows ... navigate\/operate on windows\r\n\r\nExample definition for a \"tabs\" tinykeymap (heavily based on Andy \r\nWokula's tabs mode for tinymode): >\r\n\r\n    call tinykeymap#EnterMap('tabs', 'gt', {'name': 'Tabs mode'})\r\n    call tinykeymap#Map('tabs', 'n', 'tabnew') \r\n    call tinykeymap#Map('tabs', 't', 'norm! gt') \r\n    call tinykeymap#Map('tabs', 'T', 'norm! gT') \r\n    call tinykeymap#Map(\"tabs\", \"^\", \"tabfirst\")\r\n    call tinykeymap#Map(\"tabs\", \"$\", \"tablast\")\r\n    call tinykeymap#Map(\"tabs\", \"c\", \"tabclose\")\r\n\r\nExample use of the above tinykeymap: E.g. pressing gt3n^c2t will:\r\n\r\n    gt ... Enter tabs mode\r\n    3n ... create 3 new tabs,\r\n    ^  ... select the first one,\r\n    c  ... close it, and\r\n    2t ... move to the second tab on the right.\r\n\r\nA tinykeymap is exited (1) by pressing <Esc> or (2) by timeout (see \r\n|g:tinykeymap#timeout|).\r\n\r\ntinykeymap comes with the following pre-defined tinykeymaps:\r\n\r\n    tabs    gt         :: Operate on tabs\r\n    windows <C-W>      :: Operate on windows\r\n    buffers <Leader>mb :: Operate on buffers\r\n    diff    <Leader>md :: Make it easier to work with |diff|s\r\n    filter  <Leader>mf :: Fold lines not matching some pattern (default: word \r\n                         under cursor)\r\n    lines   <Leader>ml :: Operate on lines\r\n    loc     <Leader>mo :: Operate on the |location-list|\r\n    qfl     <Leader>mq :: Operate on the |quickfix| list\r\n    undo    <Leader>mu :: Operate on the |undo| tree\r\n\r\nDifferences to tinymode:\r\n\r\n    - tinykeymaps and maps may have options (optional)\r\n    - tinykeymaps can be buffer-local\r\n    - dealing with [count] is easier (if a map contains \"<count>\", this \r\n      placeholder is replaced with the current [count], i.e. a \r\n      previously entered number; otherwise the expression is evaluated \r\n      [count] times)\r\n","install_details":"In order to install the vba, open the vba file in VIM and type: >\r\n\r\n    :so %\r\n\r\nSee :help vimball for details.\r\n\r\nBy default, tinykeymap will load all tinykeymaps in your 'runtimepath'. \r\nIf this is not what you want, set |g:tinykeymaps_default| in your \r\n|vimrc| file.\r\n\r\nAlso available via git: http:\/\/github.com\/tomtom\/tinykeymap_vim\/","5":"In order to install the vba, open the vba file in VIM and type: >\r\n\r\n    :so %\r\n\r\nSee :help vimball for details.\r\n\r\nBy default, tinykeymap will load all tinykeymaps in your 'runtimepath'. \r\nIf this is not what you want, set |g:tinykeymaps_default| in your \r\n|vimrc| file.\r\n\r\nAlso available via git: http:\/\/github.com\/tomtom\/tinykeymap_vim\/","first_name":"Tom","6":"Tom","last_name":"Link","7":"Link","releases":[{"0":"4199","vim_version":"7.0","1":"7.0","script_version":"0.06","2":"0.06","version_comment":"- tinykeymap#Info(): display map arg first (patch by Chr Brabandt)\n- tinykeymap#EnterMap(): Ignore conflicts for maps to the same tinykeymap (patch by Chr Brabandt)\n- g:tinykeymap#debug: Help debugging\n- filter tinykeymap: <cr> ... leave folds intact (patch by Chr Brabandt)\n- tabs: up & down: move tab page left\/right\n- addon-info\n- autokey, autokey_msecs options\n- Help template\nMD5 checksum: 01926a3a2f612acc40569b1b176271be","3":"- tinykeymap#Info(): display map arg first (patch by Chr Brabandt)\n- tinykeymap#EnterMap(): Ignore conflicts for maps to the same tinykeymap (patch by Chr Brabandt)\n- g:tinykeymap#debug: Help debugging\n- filter tinykeymap: <cr> ... leave folds intact (patch by Chr Brabandt)\n- tabs: up & down: move tab page left\/right\n- addon-info\n- autokey, autokey_msecs options\n- Help template\nMD5 checksum: 01926a3a2f612acc40569b1b176271be","package":"tinykeymap.vba","4":"tinykeymap.vba","src_id":"20980","5":"20980","creation_date":"1383071360","6":"1383071360"},{"0":"4199","vim_version":"7.0","1":"7.0","script_version":"0.05","2":"0.05","version_comment":"- g:tinykeymap#mapleader defaults to '<Leader>m' (no need to use mapleader directly)\n- :TinykeymapsInfo command: give information on loaded tinykeymaps\n- Fix handling of conflicting maps\nMD5 checksum: 07833eda99f35110f6d2d527fc088e1c","3":"- g:tinykeymap#mapleader defaults to '<Leader>m' (no need to use mapleader directly)\n- :TinykeymapsInfo command: give information on loaded tinykeymaps\n- Fix handling of conflicting maps\nMD5 checksum: 07833eda99f35110f6d2d527fc088e1c","package":"tinykeymap.vba","4":"tinykeymap.vba","src_id":"18970","5":"18970","creation_date":"1352743788","6":"1352743788"},{"0":"4199","vim_version":"7.0","1":"7.0","script_version":"0.04","2":"0.04","version_comment":"- If mapleader isn't defined use \"\\\", which is vim's default mapleader\nMD5 checksum: b982d342ca7cecce4f3fdde81e9003ae","3":"- If mapleader isn't defined use \"\\\", which is vim's default mapleader\nMD5 checksum: b982d342ca7cecce4f3fdde81e9003ae","package":"tinykeymap.vba","4":"tinykeymap.vba","src_id":"18966","5":"18966","creation_date":"1352566541","6":"1352566541"},{"0":"4199","vim_version":"7.0","1":"7.0","script_version":"0.03","2":"0.03","version_comment":"- fix msg variable name typo\n- Merge branch 'a_little_bit_fix' of https:\/\/github.com\/NagatoPain\/tinykeymap_vim\n- g:tinykeymap#mapleader: Check whether mapleader is defined (reported by C Brabandt)\nMD5 checksum: bbe0b05d5cefcf3d6f9328995762711e","3":"- fix msg variable name typo\n- Merge branch 'a_little_bit_fix' of https:\/\/github.com\/NagatoPain\/tinykeymap_vim\n- g:tinykeymap#mapleader: Check whether mapleader is defined (reported by C Brabandt)\nMD5 checksum: bbe0b05d5cefcf3d6f9328995762711e","package":"tinykeymap.vba","4":"tinykeymap.vba","src_id":"18961","5":"18961","creation_date":"1352457871","6":"1352457871"},{"0":"4199","vim_version":"7.0","1":"7.0","script_version":"0.02a","2":"0.02a","version_comment":"Re-packaged (forgot some files)","3":"Re-packaged (forgot some files)","package":"tinykeymap.vba","4":"tinykeymap.vba","src_id":"18715","5":"18715","creation_date":"1348933411","6":"1348933411"},{"0":"4199","vim_version":"7.0","1":"7.0","script_version":"0.02","2":"0.02","version_comment":"- Misc improvements: multi-key maps, more options etc.\n- Improved \"buffers\" map\n- Improved \"undo\" map\n- Improved \"windows\" map\n- New \"diff\" map\n- New \"filter\" map\n- New \"lines\" map\n- New \"qfl\" map\n- Moved maps to autoload\/tinykeymap\/map\n- Make sure a map is loaded upon activation\n- lines, qfl: Highlight the current line if tlib is installed\n- <count0>: Insert 0 by default\n- diff: G, P, u maps; highlight current line if tlib is installed\n- qfl: <cr> calls :cc (not c)\n- Map for location-list\n- Call \"norm! zz\" after some actions\n- filter: use g:tinykeymap#map#filter#rx instead of g:tinykeymap#filter#rx\nMD5 checksum: 829fc233090bf9d543c9851d236df60f","3":"- Misc improvements: multi-key maps, more options etc.\n- Improved \"buffers\" map\n- Improved \"undo\" map\n- Improved \"windows\" map\n- New \"diff\" map\n- New \"filter\" map\n- New \"lines\" map\n- New \"qfl\" map\n- Moved maps to autoload\/tinykeymap\/map\n- Make sure a map is loaded upon activation\n- lines, qfl: Highlight the current line if tlib is installed\n- <count0>: Insert 0 by default\n- diff: G, P, u maps; highlight current line if tlib is installed\n- qfl: <cr> calls :cc (not c)\n- Map for location-list\n- Call \"norm! zz\" after some actions\n- filter: use g:tinykeymap#map#filter#rx instead of g:tinykeymap#filter#rx\nMD5 checksum: 829fc233090bf9d543c9851d236df60f","package":"tinykeymap.vba","4":"tinykeymap.vba","src_id":"18708","5":"18708","creation_date":"1348831080","6":"1348831080"},{"0":"4199","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"tinykeymap.vba","4":"tinykeymap.vba","src_id":"18517","5":"18517","creation_date":"1346420621","6":"1346420621"}]},"4198":{"script_id":"4198","0":"4198","script_name":"asyncfinder.vim","1":"asyncfinder.vim","script_type":"utility","2":"utility","summary":"asyncfinder.vim - simple asynchronous fuzzy file finder for vim","3":"asyncfinder.vim - simple asynchronous fuzzy file finder for vim","description":"asyncfinder.vim\r\n\r\nasyncfinder.vim - simple asynchronous fuzzy file finder for vim that won't make you wait for results evar! EVAR! It uses python's threading module and does pattern matching in background thread so your vim won't get stuck and you won't get frustuated by waiting for results. It's quite similar to FuzzyFinder, ku, ctrl-p and unite.vim and inspired by those plugins but is much more simple in it's functionality.\r\n\r\nhttps:\/\/github.com\/troydm\/asyncfinder.vim","4":"asyncfinder.vim\r\n\r\nasyncfinder.vim - simple asynchronous fuzzy file finder for vim that won't make you wait for results evar! EVAR! It uses python's threading module and does pattern matching in background thread so your vim won't get stuck and you won't get frustuated by waiting for results. It's quite similar to FuzzyFinder, ku, ctrl-p and unite.vim and inspired by those plugins but is much more simple in it's functionality.\r\n\r\nhttps:\/\/github.com\/troydm\/asyncfinder.vim","install_details":"","5":"","first_name":"Dmitry","6":"Dmitry","last_name":"Geurkov","7":"Geurkov","releases":[{"0":"4198","vim_version":"7.3","1":"7.3","script_version":"0.2.8","2":"0.2.8","version_comment":"added text searching functionality\r\nstatus line implemented","3":"added text searching functionality\r\nstatus line implemented","package":"asyncfinder-v0.2.8.zip","4":"asyncfinder-v0.2.8.zip","src_id":"24090","5":"24090","creation_date":"1457733642","6":"1457733642"},{"0":"4198","vim_version":"7.0","1":"7.0","script_version":"0.2.6","2":"0.2.6","version_comment":"fuzzy matching enchanced","3":"fuzzy matching enchanced","package":"asyncfinder.vim-0.2.6.zip","4":"asyncfinder.vim-0.2.6.zip","src_id":"18553","5":"18553","creation_date":"1346863944","6":"1346863944"},{"0":"4198","vim_version":"7.0","1":"7.0","script_version":"0.2.5","2":"0.2.5","version_comment":"command ! bang added to repeat previous pattern searches","3":"command ! bang added to repeat previous pattern searches","package":"asyncfinder.vim-0.2.5.zip","4":"asyncfinder.vim-0.2.5.zip","src_id":"18540","5":"18540","creation_date":"1346686500","6":"1346686500"},{"0":"4198","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"asyncfinder.vim-0.1.zip","4":"asyncfinder.vim-0.1.zip","src_id":"18514","5":"18514","creation_date":"1346342626","6":"1346342626"}]},"4197":{"script_id":"4197","0":"4197","script_name":"numsign.vim","1":"numsign.vim","script_type":"utility","2":"utility","summary":" jump between signs  according sign ID or Line Number","3":" jump between signs  according sign ID or Line Number","description":"\" Script Name: numsign.vim \r\n\" Version:     1.01\r\n\" Last Change: Sep 21, 2012\r\n\" Author:      hjjdebug\r\n\" Email:       hejinjing@tom.com\r\n\" Description: like ultra edit signs but beyond it , jump between signs  according sign ID or line Number\r\n\"\r\n\" Usage:\r\n\" it has tow working mode,  default is jump between signs according sign ID,\r\n\" you can use \\sm, which will toggle according sign ID  or according Line Number\r\n\"\r\n\"                <C-F2>   \\ss ----> toggle sign\r\n\"                <F2>     \\sn ----> jump to next sign\r\n\"                <S-F2>   \\sp ----> jump to previous sign\r\n\"                         \\sc ----> clear all signs\r\n\"                         \\sm ----> toggle working mode\r\n\"                         \\sl ----> list current buffer signs","4":"\" Script Name: numsign.vim \r\n\" Version:     1.01\r\n\" Last Change: Sep 21, 2012\r\n\" Author:      hjjdebug\r\n\" Email:       hejinjing@tom.com\r\n\" Description: like ultra edit signs but beyond it , jump between signs  according sign ID or line Number\r\n\"\r\n\" Usage:\r\n\" it has tow working mode,  default is jump between signs according sign ID,\r\n\" you can use \\sm, which will toggle according sign ID  or according Line Number\r\n\"\r\n\"                <C-F2>   \\ss ----> toggle sign\r\n\"                <F2>     \\sn ----> jump to next sign\r\n\"                <S-F2>   \\sp ----> jump to previous sign\r\n\"                         \\sc ----> clear all signs\r\n\"                         \\sm ----> toggle working mode\r\n\"                         \\sl ----> list current buffer signs","install_details":"put this file in your vimfile\/plugin or equivalent","5":"put this file in your vimfile\/plugin or equivalent","first_name":"jinjing","6":"jinjing","last_name":"he","7":"he","releases":[{"0":"4197","vim_version":"7.0","1":"7.0","script_version":"1.02","2":"1.02","version_comment":"change next placeID use current MaximumID+1, so when you remove the last sign, you can reuse the last signID","3":"change next placeID use current MaximumID+1, so when you remove the last sign, you can reuse the last signID","package":"numsign.vim","4":"numsign.vim","src_id":"18645","5":"18645","creation_date":"1348197296","6":"1348197296"},{"0":"4197","vim_version":"7.0","1":"7.0","script_version":"1.01","2":"1.01","version_comment":"solve the problem. when insert or remove lines, goto next or previous sign will goto the old place.","3":"solve the problem. when insert or remove lines, goto next or previous sign will goto the old place.","package":"numsign.vim","4":"numsign.vim","src_id":"18567","5":"18567","creation_date":"1347116791","6":"1347116791"}]},"4196":{"script_id":"4196","0":"4196","script_name":"GrepTasks","1":"GrepTasks","script_type":"utility","2":"utility","summary":"Grep for tasks and TODO markers.","3":"Grep for tasks and TODO markers.","description":"DESCRIPTION\r\nThis plugin defines commands to search for tasks and TODO markers embedded in\r\nfiles, and populates the quickfix list with the resulting lines. Most IDEs\r\noffer such a view, too.\r\n\r\nHOW IT WORKS\r\nThe :vimgrep command is used with a predefined pattern. Search targets for\r\nthe current buffer, all arguments, listed buffers, windows in the current tab\r\npage or all tab pages can be used (leveraging the GrepHere.vim and\r\nGrepCommands.vim plugins).\r\n\r\nSEE ALSO\r\n- To move to individual tasks and TODO markers in the current buffer without\r\n  building and going through the quickfix list, you can use the companion\r\n  TaskMotions.vim plugin (vimscript #3990).\r\n\r\nRELATED WORKS\r\n- TaskList.vim (vimscript #2607) searches only the current file triggered by a\r\n  mapping, and displays in a scratch buffer.\r\n\r\nUSAGE\r\nAll commands search for case-sensitive occurrences of FIXME:, TODO:, and XXX:\r\nin the files. (This is customizable via g:GrepTasks_PatternTemplate).\r\nWhen the optional [{pattern}] is specified, only occurrences that contain the\r\n{pattern} after the marker keyword are included.\r\n\r\n:GrepHereTasks[!] [{pattern}]\r\n                        Search for tasks and TODOs in the current buffer and\r\n                        set the error list to the matches.\r\n\r\n:ArgGrepTasks[!] [{pattern}]\r\n                        Search for tasks and TODOs in all files from the\r\n                        argument-list and set the error list to the matches.\r\n\r\n:BufGrepTasks[!] [{pattern}]\r\n                        Search for tasks and TODOs in all listed buffers and\r\n                        set the error list to the matches.\r\n\r\n:WinGrepTasks[!] [{pattern}]\r\n                        Search for tasks and TODOs in all buffers visible in\r\n                        the current tab and set the error list to the matches.\r\n\r\n:TabGrepTasks[!] [{pattern}]\r\n                        Search for tasks and TODOs in all buffers visible in\r\n                        all tab pages and set the error list to the matches.\r\n\r\n:VimGrepTasks[!] [\/{pattern}\/] {file} ...\r\n                        Search for tasks and TODOs in the files {file} ... and\r\n                        set the error list to the matches.","4":"DESCRIPTION\r\nThis plugin defines commands to search for tasks and TODO markers embedded in\r\nfiles, and populates the quickfix list with the resulting lines. Most IDEs\r\noffer such a view, too.\r\n\r\nHOW IT WORKS\r\nThe :vimgrep command is used with a predefined pattern. Search targets for\r\nthe current buffer, all arguments, listed buffers, windows in the current tab\r\npage or all tab pages can be used (leveraging the GrepHere.vim and\r\nGrepCommands.vim plugins).\r\n\r\nSEE ALSO\r\n- To move to individual tasks and TODO markers in the current buffer without\r\n  building and going through the quickfix list, you can use the companion\r\n  TaskMotions.vim plugin (vimscript #3990).\r\n\r\nRELATED WORKS\r\n- TaskList.vim (vimscript #2607) searches only the current file triggered by a\r\n  mapping, and displays in a scratch buffer.\r\n\r\nUSAGE\r\nAll commands search for case-sensitive occurrences of FIXME:, TODO:, and XXX:\r\nin the files. (This is customizable via g:GrepTasks_PatternTemplate).\r\nWhen the optional [{pattern}] is specified, only occurrences that contain the\r\n{pattern} after the marker keyword are included.\r\n\r\n:GrepHereTasks[!] [{pattern}]\r\n                        Search for tasks and TODOs in the current buffer and\r\n                        set the error list to the matches.\r\n\r\n:ArgGrepTasks[!] [{pattern}]\r\n                        Search for tasks and TODOs in all files from the\r\n                        argument-list and set the error list to the matches.\r\n\r\n:BufGrepTasks[!] [{pattern}]\r\n                        Search for tasks and TODOs in all listed buffers and\r\n                        set the error list to the matches.\r\n\r\n:WinGrepTasks[!] [{pattern}]\r\n                        Search for tasks and TODOs in all buffers visible in\r\n                        the current tab and set the error list to the matches.\r\n\r\n:TabGrepTasks[!] [{pattern}]\r\n                        Search for tasks and TODOs in all buffers visible in\r\n                        all tab pages and set the error list to the matches.\r\n\r\n:VimGrepTasks[!] [\/{pattern}\/] {file} ...\r\n                        Search for tasks and TODOs in the files {file} ... and\r\n                        set the error list to the matches.","install_details":"INSTALLATION\r\nThis script is packaged as a vimball. If you have the \"gunzip\" decompressor\r\nin your PATH, simply edit the *.vmb.gz package in Vim; otherwise, decompress\r\nthe archive first, e.g. using WinZip. Inside Vim, install by sourcing the\r\nvimball or via the :UseVimball command.\r\n    vim GrepTasks*.vmb.gz\r\n    :so %\r\nTo uninstall, use the :RmVimball command.\r\n\r\nDEPENDENCIES\r\n- Requires Vim 7.0 or higher.\r\n- Requires the ingo-library.vim plugin (vimscript #4433), version 1.008 or\r\n  higher.\r\n- Requires the GrepCommands plugin (vimscript #4173).\r\n- Requires the GrepHere plugin (vimscript #4191).\r\n\r\nCONFIGURATION\r\nFor a permanent configuration, put the following commands into your vimrc:\r\n\r\nTasks and TODO markers are detected by a regular expression, which is built\r\nfrom a printf()-style template, into which the optional filter pattern is\r\ninserted at the %s keyword:\r\n    let g:GrepTasks_PatternTemplate = '\\<TODO:\\s\\?.*%s'\r\n\r\nBy default, the quickfix list is filled with all found tasks; the first found\r\ntask isn't jumped to. You can adapt that by changing the :vimgrep flags:\r\n    let g:GrepTasks_GrepFlags = 'gj'","5":"INSTALLATION\r\nThis script is packaged as a vimball. If you have the \"gunzip\" decompressor\r\nin your PATH, simply edit the *.vmb.gz package in Vim; otherwise, decompress\r\nthe archive first, e.g. using WinZip. Inside Vim, install by sourcing the\r\nvimball or via the :UseVimball command.\r\n    vim GrepTasks*.vmb.gz\r\n    :so %\r\nTo uninstall, use the :RmVimball command.\r\n\r\nDEPENDENCIES\r\n- Requires Vim 7.0 or higher.\r\n- Requires the ingo-library.vim plugin (vimscript #4433), version 1.008 or\r\n  higher.\r\n- Requires the GrepCommands plugin (vimscript #4173).\r\n- Requires the GrepHere plugin (vimscript #4191).\r\n\r\nCONFIGURATION\r\nFor a permanent configuration, put the following commands into your vimrc:\r\n\r\nTasks and TODO markers are detected by a regular expression, which is built\r\nfrom a printf()-style template, into which the optional filter pattern is\r\ninserted at the %s keyword:\r\n    let g:GrepTasks_PatternTemplate = '\\<TODO:\\s\\?.*%s'\r\n\r\nBy default, the quickfix list is filled with all found tasks; the first found\r\ntask isn't jumped to. You can adapt that by changing the :vimgrep flags:\r\n    let g:GrepTasks_GrepFlags = 'gj'","first_name":"Ingo","6":"Ingo","last_name":"Karkat","7":"Karkat","releases":[{"0":"4196","vim_version":"7.0","1":"7.0","script_version":"1.01","2":"1.01","version_comment":"- FIX: Use the rules for the \/pattern\/ separator as stated in :help E146.\r\n- Add dependency to ingo-library (vimscript #4433). *** You need to separately install ingo-library (vimscript #4433) version 1.008 (or higher)! ***","3":"- FIX: Use the rules for the \/pattern\/ separator as stated in :help E146.\r\n- Add dependency to ingo-library (vimscript #4433). *** You need to separately install ingo-library (vimscript #4433) version 1.008 (or higher)! ***","package":"GrepTasks-1.01.vmb.gz","4":"GrepTasks-1.01.vmb.gz","src_id":"21195","5":"21195","creation_date":"1387051362","6":"1387051362"},{"0":"4196","vim_version":"7.0","1":"7.0","script_version":"1.00","2":"1.00","version_comment":"Initial upload","3":"Initial upload","package":"GrepTasks-1.00.vmb.gz","4":"GrepTasks-1.00.vmb.gz","src_id":"18499","5":"18499","creation_date":"1346075850","6":"1346075850"}]},"4195":{"script_id":"4195","0":"4195","script_name":"harlequin","1":"harlequin","script_type":"color scheme","2":"color scheme","summary":"Dark, high contrast, warm colorscheme for gvim and 256 color terminal","3":"Dark, high contrast, warm colorscheme for gvim and 256 color terminal","description":"- dark background, warm colors, high contrast, but nothing too garish\r\n- everything that's constantly on screen and not code is low key\r\n- no color clashes, where very different colors are close to each other\r\n\r\ncontribute\r\n--------------\r\n\r\nhttps:\/\/github.com\/nielsmadan\/harlequin\r\n\r\nPull requests welcome. Please open issues if you find something that looks wonky.\r\n\r\nscreenshots\r\n-----------------\r\n\r\nPython: http:\/\/i.imgur.com\/IX2F1.png\r\n\r\nC: http:\/\/i.imgur.com\/ODbCD.png\r\n\r\nClojure: http:\/\/i.imgur.com\/LoUNY.png\r\n\r\nDiffmode: http:\/\/i.imgur.com\/7GlFM.png\r\n\r\nLanguges supported: C, python, ruby, javascript, clojure, scala, vimscript, xml, html, and css\r\nPlugins supported: minibufexplorer, vim-easymotion, vimdiff, CtrlP","4":"- dark background, warm colors, high contrast, but nothing too garish\r\n- everything that's constantly on screen and not code is low key\r\n- no color clashes, where very different colors are close to each other\r\n\r\ncontribute\r\n--------------\r\n\r\nhttps:\/\/github.com\/nielsmadan\/harlequin\r\n\r\nPull requests welcome. Please open issues if you find something that looks wonky.\r\n\r\nscreenshots\r\n-----------------\r\n\r\nPython: http:\/\/i.imgur.com\/IX2F1.png\r\n\r\nC: http:\/\/i.imgur.com\/ODbCD.png\r\n\r\nClojure: http:\/\/i.imgur.com\/LoUNY.png\r\n\r\nDiffmode: http:\/\/i.imgur.com\/7GlFM.png\r\n\r\nLanguges supported: C, python, ruby, javascript, clojure, scala, vimscript, xml, html, and css\r\nPlugins supported: minibufexplorer, vim-easymotion, vimdiff, CtrlP","install_details":"","5":"","first_name":"Niels","6":"Niels","last_name":"Madan","7":"Madan","releases":[{"0":"4195","vim_version":"7.0","1":"7.0","script_version":"2.1","2":"2.1","version_comment":"minor update, improve search highlighting.","3":"minor update, improve search highlighting.","package":"harlequin.vim","4":"harlequin.vim","src_id":"25259","5":"25259","creation_date":"1495800607","6":"1495800607"},{"0":"4195","vim_version":"7.0","1":"7.0","script_version":"v2.0","2":"v2.0","version_comment":"256 color terminal support","3":"256 color terminal support","package":"harlequin.vim","4":"harlequin.vim","src_id":"18999","5":"18999","creation_date":"1353364541","6":"1353364541"},{"0":"4195","vim_version":"7.0","1":"7.0","script_version":"1.5","2":"1.5","version_comment":"Hand-optimize for javascript, scala, css, and CtrlP.","3":"Hand-optimize for javascript, scala, css, and CtrlP.","package":"harlequin.vim","4":"harlequin.vim","src_id":"18803","5":"18803","creation_date":"1350216305","6":"1350216305"},{"0":"4195","vim_version":"7.0","1":"7.0","script_version":"1.3","2":"1.3","version_comment":"Hand-optimize for clojure, ruby, vimscript and easymotion.","3":"Hand-optimize for clojure, ruby, vimscript and easymotion.","package":"harlequin.vim","4":"harlequin.vim","src_id":"18657","5":"18657","creation_date":"1348320963","6":"1348320963"},{"0":"4195","vim_version":"7.0","1":"7.0","script_version":"1.1","2":"1.1","version_comment":"Add definitions for xml, html and minibufexplorer.","3":"Add definitions for xml, html and minibufexplorer.","package":"harlequin.vim","4":"harlequin.vim","src_id":"18596","5":"18596","creation_date":"1347621542","6":"1347621542"},{"0":"4195","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"harlequin.vim","4":"harlequin.vim","src_id":"18496","5":"18496","creation_date":"1346002066","6":"1346002066"}]},"4194":{"script_id":"4194","0":"4194","script_name":"FileTags","1":"FileTags","script_type":"utility","2":"utility","summary":"Easily locate previously-used files, directories and URLs","3":"Easily locate previously-used files, directories and URLs","description":"Ever edit a file in a deeply-nested directory and then need to locate it a few days or weeks later, but have no recourse but to run a search\/find for it? Or, have multiple files with the same name (such as \"build.xml\"), but for different projects and need to keep them straight?\r\n\r\nExample:\r\n\r\nGiven these files, create tags using :EditTags:\r\n\r\nSome\/project\/build.xml (tags: build project local)\r\nSome\/Other\/Project\/build.xml (tags: build otherProject local)\r\nSome\/Other\/Project\/src\/com\/company\/SomeFile.java (tags: otherProject some file local)\r\n\/vim\/.vimrc (tags: vim rc global)\r\n\r\nThen, you can locate the files by using :LocateTagMatches and the other flavours provided. (:LocateTagMatches bui oth--\"build\" and \"otherProject\" need not be specified fully). If multiple matches are found (:LoateTagMatches bui), they are put in a list and you can pick the one you want (or hit escape to change your mind).\r\n\r\nFeatures:\r\n- Search by tags\r\n- Select from list in case of multiple matches\r\n- Copy result to clipboard\r\n- Open resulting file in current or new window\r\n- Attempt to guess initial tag set based on path, extension or URL components\r\n- Supports two files, one for entries with the tag \"global\" and one with the tag \"local\". Useful in case you have to go across multiple computers (home and work, for example). The local variation can be used for work-specific files and URLs, for example, and won't clutter the global file that might be shared across multiple computers.","4":"Ever edit a file in a deeply-nested directory and then need to locate it a few days or weeks later, but have no recourse but to run a search\/find for it? Or, have multiple files with the same name (such as \"build.xml\"), but for different projects and need to keep them straight?\r\n\r\nExample:\r\n\r\nGiven these files, create tags using :EditTags:\r\n\r\nSome\/project\/build.xml (tags: build project local)\r\nSome\/Other\/Project\/build.xml (tags: build otherProject local)\r\nSome\/Other\/Project\/src\/com\/company\/SomeFile.java (tags: otherProject some file local)\r\n\/vim\/.vimrc (tags: vim rc global)\r\n\r\nThen, you can locate the files by using :LocateTagMatches and the other flavours provided. (:LocateTagMatches bui oth--\"build\" and \"otherProject\" need not be specified fully). If multiple matches are found (:LoateTagMatches bui), they are put in a list and you can pick the one you want (or hit escape to change your mind).\r\n\r\nFeatures:\r\n- Search by tags\r\n- Select from list in case of multiple matches\r\n- Copy result to clipboard\r\n- Open resulting file in current or new window\r\n- Attempt to guess initial tag set based on path, extension or URL components\r\n- Supports two files, one for entries with the tag \"global\" and one with the tag \"local\". Useful in case you have to go across multiple computers (home and work, for example). The local variation can be used for work-specific files and URLs, for example, and won't clutter the global file that might be shared across multiple computers.","install_details":"Pathogen or &runtimepath. The plugin defines the commands and options (not very many).\r\n\r\nRequires my UtilityFunctions (http:\/\/vim.sourceforge.net\/scripts\/script.php?script_id=4193).","5":"Pathogen or &runtimepath. The plugin defines the commands and options (not very many).\r\n\r\nRequires my UtilityFunctions (http:\/\/vim.sourceforge.net\/scripts\/script.php?script_id=4193).","first_name":"Salman","6":"Salman","last_name":"Halim","7":"Halim","releases":[{"0":"4194","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"FileTags.zip","4":"FileTags.zip","src_id":"18492","5":"18492","creation_date":"1345950476","6":"1345950476"}]},"4193":{"script_id":"4193","0":"4193","script_name":"UtilityFunctions","1":"UtilityFunctions","script_type":"utility","2":"utility","summary":"Data structures and utility functions","3":"Data structures and utility functions","description":"Contains general utility functions (functions.vim) and two data structures: a set (like a built-in List, except that its contents are unique) and a MultiDictionary (allows the addition of multiple Dictionary objects and retrieval and key\/value iterations across all the collections as if they were one).","4":"Contains general utility functions (functions.vim) and two data structures: a set (like a built-in List, except that its contents are unique) and a MultiDictionary (allows the addition of multiple Dictionary objects and retrieval and key\/value iterations across all the collections as if they were one).","install_details":"Either put them in your autoload directory or use pathogen.","5":"Either put them in your autoload directory or use pathogen.","first_name":"Salman","6":"Salman","last_name":"Halim","7":"Halim","releases":[{"0":"4193","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"functions.zip","4":"functions.zip","src_id":"18491","5":"18491","creation_date":"1345949643","6":"1345949643"}]},"4192":{"script_id":"4192","0":"4192","script_name":"html_annoyance","1":"html_annoyance","script_type":"syntax","2":"syntax","summary":"HTML syntax file, removes annoying underlining from <a> whitespace","3":"HTML syntax file, removes annoying underlining from <a> whitespace","description":"Html <A>nnoyance\r\n\r\nThis is an extra HTML syntax file which fixes one of vim's annoyances. \r\nPreview: https:\/\/raw.github.com\/tudorprodan\/html_annoyance.vim\/master\/preview.png\r\n\r\nIt removes the underlining from leading and trailing whitespace in <A> tags.\r\n\r\nRepository:\r\nhttps:\/\/github.com\/tudorprodan\/html_annoyance.vim","4":"Html <A>nnoyance\r\n\r\nThis is an extra HTML syntax file which fixes one of vim's annoyances. \r\nPreview: https:\/\/raw.github.com\/tudorprodan\/html_annoyance.vim\/master\/preview.png\r\n\r\nIt removes the underlining from leading and trailing whitespace in <A> tags.\r\n\r\nRepository:\r\nhttps:\/\/github.com\/tudorprodan\/html_annoyance.vim","install_details":"Manual installation\r\nCopy after\/syntax\/html.vim to ~\/.vim\/after\/syntax\/html.vim.\r\n\r\nUsing pathogen\r\nPlace the content of this repository in a new bundle.\r\ngit clone <this_repository> ~\/.vim\/bundle\/html_annoyance\r\n-or-\r\ngit submodule add <this_repo> ~\/.vim\/bundle\/html_annoyance`\r\n","5":"Manual installation\r\nCopy after\/syntax\/html.vim to ~\/.vim\/after\/syntax\/html.vim.\r\n\r\nUsing pathogen\r\nPlace the content of this repository in a new bundle.\r\ngit clone <this_repository> ~\/.vim\/bundle\/html_annoyance\r\n-or-\r\ngit submodule add <this_repo> ~\/.vim\/bundle\/html_annoyance`\r\n","first_name":"Tudor","6":"Tudor","last_name":"Prodan","7":"Prodan","releases":[{"0":"4192","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"html_annoyance.tar.gz","4":"html_annoyance.tar.gz","src_id":"18489","5":"18489","creation_date":"1345891464","6":"1345891464"}]},"4191":{"script_id":"4191","0":"4191","script_name":"GrepHere","1":"GrepHere","script_type":"utility","2":"utility","summary":"List occurrences in the current buffer in the quickfix window.","3":"List occurrences in the current buffer in the quickfix window.","description":"DESCRIPTION\r\nThis plugin defines a command and mappings to quickly list all occurrences of\r\nthe last search pattern, passed pattern, current word or selection in the\r\nquickfix list. This is useful to get a somewhat persistent list of matches\r\nthat act like bookmarks, so you can recall them later (when your search\r\npattern has changed).\r\n\r\nHOW IT WORKS\r\nThe plugin uses :vimgrep over the current buffer.\r\n\r\nSOURCE\r\nInspired by vimtip #483: Using GREP for a \"list occurrences\" and quickfix help\r\ncommand.\r\n    http:\/\/vim.wikia.com\/wiki\/Search_using_quickfix_to_list_occurrences\r\n    command GREP :execute 'grep '.expand('<cword>') expand('%') | :copen | cc\r\n\r\nSEE ALSO\r\n- The GrepCommands plugin (vimscript #4173) provides additional grep commands\r\n  covering arguments, buffers, windows and tab pages.\r\n- The FindOccurrence plugin (vimscript #0000) can also show all occurrences of\r\n  the <cword>, last search pattern, etc., but instead of the quickfix list,\r\n  the result is either jumped to or listed.\r\n- The SearchPosition plugin (vimscript #2634) shows the relation of the cursor\r\n  position to the other matches of the search pattern, and provides similar\r\n  mappings. Like the quickfix list, it can provide an orientation of where and\r\n  how many matches there are.\r\n\r\nRELATED WORKS\r\n- outline (vimscript #1947) creates a custom view of the file based on regex,\r\n  in a scratch buffer\r\n- ttoc (vimscript #2014) is based on outline and creates a regexp-based table\r\n  of contents of the current buffer\r\n\r\nUSAGE\r\n:[range]GrepHere [{pattern}]\r\n:[range]GrepHere \/{pattern}\/[g][j]\r\n:[range]GrepHereAdd [{pattern}]\r\n:[range]GrepHereAdd \/{pattern}\/[g][j]\r\n                        Grep the passed pattern (or last search pattern if\r\n                        omitted) in (line in [range] of) the current file (or\r\n                        the current entry of the quickfix list).\r\n\r\n<A-N>                   Grep the last search pattern in the current file\r\n                        and show matching lines in the quickfix window (but\r\n                        don't go there).\r\n                        This is similar to [N defined by\r\n                        FindOccurrence.vim, but uses the quickfix list\r\n                        instead of just printing all matching lines.\r\n\r\n<A-M>                   Grep the current whole word under the cursor in the\r\n                        current file and show matching lines in the quickfix\r\n                        window (but don't go there).\r\n                        This is similar to [I defined by\r\n                        FindOccurrence.vim, but uses the quickfix list\r\n                        instead of just printing all matching lines.\r\ng<A-M>                  Grep the current word under the cursor in the current\r\n                        file and show matching lines in the quickfix window\r\n                        (but don't go there).\r\n                        Only whole keywords are searched for, like with the\r\n                        star command.\r\n{Visual}<A-M>           Grep the selected text in the current file and show\r\n                        matching lines in the quickfix window (but don't go\r\n                        there).\r\n\r\n                        Imagine 'M' stood for \"more occurrences\".\r\n                        These mappings reuse the last used <cword> when issued\r\n                        on a blank line.","4":"DESCRIPTION\r\nThis plugin defines a command and mappings to quickly list all occurrences of\r\nthe last search pattern, passed pattern, current word or selection in the\r\nquickfix list. This is useful to get a somewhat persistent list of matches\r\nthat act like bookmarks, so you can recall them later (when your search\r\npattern has changed).\r\n\r\nHOW IT WORKS\r\nThe plugin uses :vimgrep over the current buffer.\r\n\r\nSOURCE\r\nInspired by vimtip #483: Using GREP for a \"list occurrences\" and quickfix help\r\ncommand.\r\n    http:\/\/vim.wikia.com\/wiki\/Search_using_quickfix_to_list_occurrences\r\n    command GREP :execute 'grep '.expand('<cword>') expand('%') | :copen | cc\r\n\r\nSEE ALSO\r\n- The GrepCommands plugin (vimscript #4173) provides additional grep commands\r\n  covering arguments, buffers, windows and tab pages.\r\n- The FindOccurrence plugin (vimscript #0000) can also show all occurrences of\r\n  the <cword>, last search pattern, etc., but instead of the quickfix list,\r\n  the result is either jumped to or listed.\r\n- The SearchPosition plugin (vimscript #2634) shows the relation of the cursor\r\n  position to the other matches of the search pattern, and provides similar\r\n  mappings. Like the quickfix list, it can provide an orientation of where and\r\n  how many matches there are.\r\n\r\nRELATED WORKS\r\n- outline (vimscript #1947) creates a custom view of the file based on regex,\r\n  in a scratch buffer\r\n- ttoc (vimscript #2014) is based on outline and creates a regexp-based table\r\n  of contents of the current buffer\r\n\r\nUSAGE\r\n:[range]GrepHere [{pattern}]\r\n:[range]GrepHere \/{pattern}\/[g][j]\r\n:[range]GrepHereAdd [{pattern}]\r\n:[range]GrepHereAdd \/{pattern}\/[g][j]\r\n                        Grep the passed pattern (or last search pattern if\r\n                        omitted) in (line in [range] of) the current file (or\r\n                        the current entry of the quickfix list).\r\n\r\n<A-N>                   Grep the last search pattern in the current file\r\n                        and show matching lines in the quickfix window (but\r\n                        don't go there).\r\n                        This is similar to [N defined by\r\n                        FindOccurrence.vim, but uses the quickfix list\r\n                        instead of just printing all matching lines.\r\n\r\n<A-M>                   Grep the current whole word under the cursor in the\r\n                        current file and show matching lines in the quickfix\r\n                        window (but don't go there).\r\n                        This is similar to [I defined by\r\n                        FindOccurrence.vim, but uses the quickfix list\r\n                        instead of just printing all matching lines.\r\ng<A-M>                  Grep the current word under the cursor in the current\r\n                        file and show matching lines in the quickfix window\r\n                        (but don't go there).\r\n                        Only whole keywords are searched for, like with the\r\n                        star command.\r\n{Visual}<A-M>           Grep the selected text in the current file and show\r\n                        matching lines in the quickfix window (but don't go\r\n                        there).\r\n\r\n                        Imagine 'M' stood for \"more occurrences\".\r\n                        These mappings reuse the last used <cword> when issued\r\n                        on a blank line.","install_details":"INSTALLATION\r\nThis script is packaged as a vimball. If you have the \"gunzip\" decompressor\r\nin your PATH, simply edit the *.vmb.gz package in Vim; otherwise, decompress\r\nthe archive first, e.g. using WinZip. Inside Vim, install by sourcing the\r\nvimball or via the :UseVimball command.\r\n    vim GrepHere*.vmb.gz\r\n    :so %\r\nTo uninstall, use the :RmVimball command.\r\n\r\nDEPENDENCIES\r\n- Requires Vim 7.0 or higher.\r\n- Requires the ingo-library.vim plugin (vimscript #4433), version 1.012 or\r\n  higher.\r\n- Requires the GrepCommands.vim plugin (vimscript #4173), version 1.02 or\r\n  higher.\r\n\r\nCONFIGURATION\r\nFor a permanent configuration, put the following commands into your vimrc:\r\n\r\nThe :GrepHere command without arguments lists all occurrences, and (other\r\nthan the ALT-SHIFT-N mapping), jumps to the first occurrence. You can change\r\nthat via:\r\n    let g:GrepHere_EmptyCommandGrepFlags = 'g'\r\nWhen you provide any arguments to :GrepHere, provide the flags there, if\r\ndesired.\r\n\r\nBy default, the mappings list all occurrences in a line and do not jump to the\r\nfirst match; you can adapt the behavior by removing some of the :vimgrep\r\nflags:\r\n    let g:GrepHere_MappingGrepFlags = 'gj'\r\n\r\nIf you want to use different mappings, map your keys to the\r\n<Plug>(GrepHere...) mapping targets _before_ sourcing the script (e.g. in your\r\nvimrc):\r\n    nmap <Leader>N <Plug>(GrepHereCurrent)\r\n    nmap <Leader>M <Plug>(GrepHereWholeCword)\r\n    nmap <Leader>gM <Plug>(GrepHereCword)\r\n    vmap <Leader>M <Plug>(GrepHereCword)","5":"INSTALLATION\r\nThis script is packaged as a vimball. If you have the \"gunzip\" decompressor\r\nin your PATH, simply edit the *.vmb.gz package in Vim; otherwise, decompress\r\nthe archive first, e.g. using WinZip. Inside Vim, install by sourcing the\r\nvimball or via the :UseVimball command.\r\n    vim GrepHere*.vmb.gz\r\n    :so %\r\nTo uninstall, use the :RmVimball command.\r\n\r\nDEPENDENCIES\r\n- Requires Vim 7.0 or higher.\r\n- Requires the ingo-library.vim plugin (vimscript #4433), version 1.012 or\r\n  higher.\r\n- Requires the GrepCommands.vim plugin (vimscript #4173), version 1.02 or\r\n  higher.\r\n\r\nCONFIGURATION\r\nFor a permanent configuration, put the following commands into your vimrc:\r\n\r\nThe :GrepHere command without arguments lists all occurrences, and (other\r\nthan the ALT-SHIFT-N mapping), jumps to the first occurrence. You can change\r\nthat via:\r\n    let g:GrepHere_EmptyCommandGrepFlags = 'g'\r\nWhen you provide any arguments to :GrepHere, provide the flags there, if\r\ndesired.\r\n\r\nBy default, the mappings list all occurrences in a line and do not jump to the\r\nfirst match; you can adapt the behavior by removing some of the :vimgrep\r\nflags:\r\n    let g:GrepHere_MappingGrepFlags = 'gj'\r\n\r\nIf you want to use different mappings, map your keys to the\r\n<Plug>(GrepHere...) mapping targets _before_ sourcing the script (e.g. in your\r\nvimrc):\r\n    nmap <Leader>N <Plug>(GrepHereCurrent)\r\n    nmap <Leader>M <Plug>(GrepHereWholeCword)\r\n    nmap <Leader>gM <Plug>(GrepHereCword)\r\n    vmap <Leader>M <Plug>(GrepHereCword)","first_name":"Ingo","6":"Ingo","last_name":"Karkat","7":"Karkat","releases":[{"0":"4191","vim_version":"7.0","1":"7.0","script_version":"1.11","2":"1.11","version_comment":"- ENH: Allow [range] for :GrepHere.\r\n- Add dependency to ingo-library (vimscript #4433). *** You need to separately install ingo-library (vimscript #4433) version 1.012 (or higher)! *** *** You need to upgrade to GrepCommands.vim plugin (vimscript #4173), version 1.02 or higher! ***","3":"- ENH: Allow [range] for :GrepHere.\r\n- Add dependency to ingo-library (vimscript #4433). *** You need to separately install ingo-library (vimscript #4433) version 1.012 (or higher)! *** *** You need to upgrade to GrepCommands.vim plugin (vimscript #4173), version 1.02 or higher! ***","package":"GrepHere-1.11.vmb.gz","4":"GrepHere-1.11.vmb.gz","src_id":"24771","5":"24771","creation_date":"1480431631","6":"1480431631"},{"0":"4191","vim_version":"7.0","1":"7.0","script_version":"1.10","2":"1.10","version_comment":"Make default flags for an empty :GrepHere command configurable via g:GrepHere_EmptyCommandGrepFlags. Default to 'g': List all occurrences, jump to first occurrence.\r\n","3":"Make default flags for an empty :GrepHere command configurable via g:GrepHere_EmptyCommandGrepFlags. Default to 'g': List all occurrences, jump to first occurrence.\r\n","package":"GrepHere-1.10.vmb.gz","4":"GrepHere-1.10.vmb.gz","src_id":"18555","5":"18555","creation_date":"1346919582","6":"1346919582"},{"0":"4191","vim_version":"7.0","1":"7.0","script_version":"1.00","2":"1.00","version_comment":"Initial upload","3":"Initial upload","package":"GrepHere-1.00.vmb.gz","4":"GrepHere-1.00.vmb.gz","src_id":"18479","5":"18479","creation_date":"1345817001","6":"1345817001"}]},"4190":{"script_id":"4190","0":"4190","script_name":"easymenu.vim","1":"easymenu.vim","script_type":"utility","2":"utility","summary":"Data-driven, hierarchical Menu Creation","3":"Data-driven, hierarchical Menu Creation","description":"The problem statement is that creating and maintain Vim menus is painful.\r\nThis plug-in provides a data-driven, hierarchical means of defining\r\nnon-trivial menus for your users' consumption.\r\n\r\nConsider the following, simple, menu structure:\r\n\r\n|Test| File Edit ... Help\r\n+-----------+\r\n| Module A  |______________\r\n| Module B >| Compile  F11 |\r\n+===========| Run      F12 |\r\n            | ------------ |\r\n            | Obsolete     |\r\n            +==============+\r\n\r\nHere's the structure created with Vim's built-in commands:\r\n\r\n1amenu <silent> Test.Module\\ A.Compile :make amod<CR>\r\n1amenu <silent> Test.Module\\ A.Run :make testamod<CR>\r\n1amenu <silent> Test.Module\\ B.Compile<Tab>F11 :make bmod<CR>\r\n1amenu <silent> Test.Module\\ B.Run<Tab>F12 :make testbmod<CR>\r\n1amenu <silent> Test.Module\\ B.Obsolete :call MyFunction()<CR>\r\n1amenu <silent> Test.Module\\ B.-sep-\r\n1amenu <silent> disable Test.Module\\ B.Obsolete\r\n\r\nNote the repetition of the hierarchical menu names and the backslash-\r\nescaping of spaces.\r\n\r\nThe structure really gets messy as it scales up.  In order to defeat\r\nthe repeated \"higher-level\" menu names, you could store them in Vim\r\nvariables but that results in additional boilerplate (including the need\r\nto use execute rather than menu directly).\r\n\r\nWith this plugin, the menus are represented in a recursive data structure:\r\n\r\nsource easymenu.vim\r\ncall g:LoadMenu(\r\n\\ [\r\n\\ {\r\n\\   'text': 'Test',\r\n\\   'priority': 1,\r\n\\   'children': [\r\n\\               {\r\n\\                 'text': 'Module A',\r\n\\                 'children': [\r\n\\                             {\r\n\\                               'text': 'Compile',\r\n\\                               'command': ':make amod',\r\n\\                             },\r\n\\                             {\r\n\\                               'text': 'Run',\r\n\\                               'command': ':make testamod',\r\n\\                             },\r\n\\                             ],\r\n\\               },\r\n\\               {\r\n\\                 'text': 'Module B',\r\n\\                 'children': [\r\n\\                             {\r\n\\                               'text': 'Compile<Tab>F11',\r\n\\                               'command': ':make bmod',\r\n\\                             },\r\n\\                             {\r\n\\                               'text': 'Run<Tab>F12',\r\n\\                               'command': ':make testbmod',\r\n\\                             },\r\n\\                             {\r\n\\                               'text': '-sep-',\r\n\\                             },\r\n\\                             {\r\n\\                               'text': 'Obsolete',\r\n\\                               'able': 'disable',\r\n\\                             },\r\n\\                             ],\r\n\\               },\r\n\\               ],\r\n\\ },\r\n\\ ],\r\n\\ )\r\n\r\n","4":"The problem statement is that creating and maintain Vim menus is painful.\r\nThis plug-in provides a data-driven, hierarchical means of defining\r\nnon-trivial menus for your users' consumption.\r\n\r\nConsider the following, simple, menu structure:\r\n\r\n|Test| File Edit ... Help\r\n+-----------+\r\n| Module A  |______________\r\n| Module B >| Compile  F11 |\r\n+===========| Run      F12 |\r\n            | ------------ |\r\n            | Obsolete     |\r\n            +==============+\r\n\r\nHere's the structure created with Vim's built-in commands:\r\n\r\n1amenu <silent> Test.Module\\ A.Compile :make amod<CR>\r\n1amenu <silent> Test.Module\\ A.Run :make testamod<CR>\r\n1amenu <silent> Test.Module\\ B.Compile<Tab>F11 :make bmod<CR>\r\n1amenu <silent> Test.Module\\ B.Run<Tab>F12 :make testbmod<CR>\r\n1amenu <silent> Test.Module\\ B.Obsolete :call MyFunction()<CR>\r\n1amenu <silent> Test.Module\\ B.-sep-\r\n1amenu <silent> disable Test.Module\\ B.Obsolete\r\n\r\nNote the repetition of the hierarchical menu names and the backslash-\r\nescaping of spaces.\r\n\r\nThe structure really gets messy as it scales up.  In order to defeat\r\nthe repeated \"higher-level\" menu names, you could store them in Vim\r\nvariables but that results in additional boilerplate (including the need\r\nto use execute rather than menu directly).\r\n\r\nWith this plugin, the menus are represented in a recursive data structure:\r\n\r\nsource easymenu.vim\r\ncall g:LoadMenu(\r\n\\ [\r\n\\ {\r\n\\   'text': 'Test',\r\n\\   'priority': 1,\r\n\\   'children': [\r\n\\               {\r\n\\                 'text': 'Module A',\r\n\\                 'children': [\r\n\\                             {\r\n\\                               'text': 'Compile',\r\n\\                               'command': ':make amod',\r\n\\                             },\r\n\\                             {\r\n\\                               'text': 'Run',\r\n\\                               'command': ':make testamod',\r\n\\                             },\r\n\\                             ],\r\n\\               },\r\n\\               {\r\n\\                 'text': 'Module B',\r\n\\                 'children': [\r\n\\                             {\r\n\\                               'text': 'Compile<Tab>F11',\r\n\\                               'command': ':make bmod',\r\n\\                             },\r\n\\                             {\r\n\\                               'text': 'Run<Tab>F12',\r\n\\                               'command': ':make testbmod',\r\n\\                             },\r\n\\                             {\r\n\\                               'text': '-sep-',\r\n\\                             },\r\n\\                             {\r\n\\                               'text': 'Obsolete',\r\n\\                               'able': 'disable',\r\n\\                             },\r\n\\                             ],\r\n\\               },\r\n\\               ],\r\n\\ },\r\n\\ ],\r\n\\ )\r\n\r\n","install_details":"Extract easymenu.tgz into its own directory for use with pathogen, otherwise just make sure easymenu.vim goes into the plugin directory and easymenu.txt goes into the doc directory.\r\n\r\nAlternatively, you can just source the file directly from your script or $HOME\/.vimrc.","5":"Extract easymenu.tgz into its own directory for use with pathogen, otherwise just make sure easymenu.vim goes into the plugin directory and easymenu.txt goes into the doc directory.\r\n\r\nAlternatively, you can just source the file directly from your script or $HOME\/.vimrc.","first_name":"Chad","6":"Chad","last_name":"Moore","7":"Moore","releases":[{"0":"4190","vim_version":"7.0","1":"7.0","script_version":"0.1.0","2":"0.1.0","version_comment":"Initial upload (plugin\/easymenu.vim, doc\/easymenu.txt).","3":"Initial upload (plugin\/easymenu.vim, doc\/easymenu.txt).","package":"easymenu.tgz","4":"easymenu.tgz","src_id":"18478","5":"18478","creation_date":"1345808072","6":"1345808072"}]},"4189":{"script_id":"4189","0":"4189","script_name":"Close Location List Before Quit","1":"Close Location List Before Quit","script_type":"utility","2":"utility","summary":"Simple closes the location list before quit","3":"Simple closes the location list before quit","description":"Based on http:\/\/www.vim.org\/scripts\/script.php?script_id=1072 , this closes the location list before vim is quit. This is ordinarily not particularly useful but serves as a workaround for the vim issue described here: https:\/\/github.com\/scrooloose\/syntastic\/issues\/286 , which appears to affect Macvim + Syntastic combination only.  Try this if you're using MacVim + Syntastic and MacVim freezes on-close.","4":"Based on http:\/\/www.vim.org\/scripts\/script.php?script_id=1072 , this closes the location list before vim is quit. This is ordinarily not particularly useful but serves as a workaround for the vim issue described here: https:\/\/github.com\/scrooloose\/syntastic\/issues\/286 , which appears to affect Macvim + Syntastic combination only.  Try this if you're using MacVim + Syntastic and MacVim freezes on-close.","install_details":"Copy to \"plugin\" folder","5":"Copy to \"plugin\" folder","first_name":"Ben","6":"Ben","last_name":"Regenspan","7":"Regenspan","releases":[{"0":"4189","vim_version":"7.0","1":"7.0","script_version":"1.1","2":"1.1","version_comment":"Work on non-GUI mode also; bug is there too.","3":"Work on non-GUI mode also; bug is there too.","package":"closeLclBeforeQuit.vim","4":"closeLclBeforeQuit.vim","src_id":"18468","5":"18468","creation_date":"1345744447","6":"1345744447"},{"0":"4189","vim_version":"7.0","1":"7.0","script_version":"1","2":"1","version_comment":"Initial upload","3":"Initial upload","package":"closeLclBeforeQuit.vim","4":"closeLclBeforeQuit.vim","src_id":"18467","5":"18467","creation_date":"1345742808","6":"1345742808"}]},"4188":{"script_id":"4188","0":"4188","script_name":"HybridText","1":"HybridText","script_type":"syntax","2":"syntax","summary":"A blend of useful document syntax for text files","3":"A blend of useful document syntax for text files","description":"Plain text files do not have a syntax, but we use different kinds of syntax in text files. So that you can easily swing from making GTD-style todo lists to writing documents in Markdown, without using dozens of pseudo filetypes, the HybridText syntax file attempts to merge elements of several common, helpful markup schemes: Markdown, Markdown extensions, Pandoc, reStructuredText, Mind Maps, and TaskPaper.\r\n\r\nOptional ColorBoost extends existing colorschemes, in order to support advanced effects.\r\n\r\nThe following sample is an exhaustive look at everything HybridText does, but all you really need is to know is how to use your chosen markup. Follow the install details at the bottom of this page to test, and to automatically load the syntax.\r\n\r\nVersion 1.2 sample, rendered: http:\/\/antelucan.com\/vimupdate\/f\/HybridTextSyntax-1-2.html\r\nIn colorscheme FluidVision: http:\/\/antelucan.com\/vimupdate\/f\/HybridTextSyntax-1-2.fluidvision.html\r\nIn colorscheme Spectro: http:\/\/antelucan.com\/vimupdate\/f\/HybridTextSyntax-1-2.spectro.html\r\n\r\nPlain text file: http:\/\/antelucan.com\/vimupdate\/f\/HybridTextSyntax-1-2.txt\r\n\r\nMind Maps may be converted at Text 2 Mind Map (http:\/\/www.text2mindmap.com): note that only *ten* levels are supported, and pasted text must use tabs instead of spaces.\r\n\r\nMind Map results from text2mindmap.com: http:\/\/antelucan.com\/vimupdate\/f\/NonsenseMindMap.png\r\nMind Map highlighted by HybridText: http:\/\/antelucan.com\/vimupdate\/f\/NonsenseMindMap.html\r\n\r\n----------------------------------------------------------------------------------------------------------------------------\r\n\r\nUpdate history:\r\n\r\nVersion 1.2 fixes a major top-level goof (I was configuring so much stuff at the bottom, I accidentally switched off text emphasis at the top!) Apart from that, there's more support for Markdown and reStructuredText, extended support for block quotes, and various adjustments and fixes. I feel there's more to do, but I need a breather.\r\n\r\nThe support file (linked above) has been re-organized into better groupings, in order to demonstrate\/check the highlighting. Instead of going all through Markdown, and then reStructuredText, like things are put together--for example, the two markups use a slightly different method of indicating line breaks\/blocks of lines, so it's useful to put them together in order to make sure the highlighting is consistent between different kinds of documents.\r\n\r\nVersion 1.1 introduces Mind Mapping--12 levels of gradient indentations for brainstorming.\r\n\r\nVersion 1.1 also now includes ColorBoost, an optional enhancement for existing colorschemes. ColorBoost defines header levels, creates gradiated effects, and allows text emphasis within other definitions. This is a cheat to make HybridText compatible with other schemes, and can be turned off with a line in VIMRC.\r\n\r\nChanging colorschemes with a file open will clear ColorBoost colors until the buffer is reloaded. Type command :e to restore.\r\n\r\n\r\nThe following pages are examples using different colorschemes in version 1.1, in order to demonstrate ColorBoost.\r\n\r\nSample, Festoon Light: http:\/\/antelucan.com\/vimupdate\/f\/hybrid-txt-festoon-light.html\r\nSample, Festoon Dark: http:\/\/antelucan.com\/vimupdate\/f\/hybrid-txt-festoon-dark.html\r\nSample, Solarized Dark with ColorBoost: http:\/\/antelucan.com\/vimupdate\/f\/hybrid-txt-solarized-dark.html\r\nSample, Twilight with ColorBoost: http:\/\/antelucan.com\/vimupdate\/f\/hybrid-txt-twilight.html\r\nSample, CalmBreeze with ColorBoost: http:\/\/antelucan.com\/vimupdate\/f\/hybrid-txt-calmbreeze.html\r\n\r\nSample, Tabula without ColorBoost: http:\/\/antelucan.com\/vimupdate\/f\/hybrid-txt-tabula.html\r\n\r\nVersion 1.0: [Fixed in 1.1] For best results (but not required), use the colorscheme Festoon vimscript #3852. Text emphasis within other defined blocks require extra definitions, and many colorschemes fail to support header levels. Nested blockquotes use a gradiated colorscheme especially written for Festoon.\r\n","4":"Plain text files do not have a syntax, but we use different kinds of syntax in text files. So that you can easily swing from making GTD-style todo lists to writing documents in Markdown, without using dozens of pseudo filetypes, the HybridText syntax file attempts to merge elements of several common, helpful markup schemes: Markdown, Markdown extensions, Pandoc, reStructuredText, Mind Maps, and TaskPaper.\r\n\r\nOptional ColorBoost extends existing colorschemes, in order to support advanced effects.\r\n\r\nThe following sample is an exhaustive look at everything HybridText does, but all you really need is to know is how to use your chosen markup. Follow the install details at the bottom of this page to test, and to automatically load the syntax.\r\n\r\nVersion 1.2 sample, rendered: http:\/\/antelucan.com\/vimupdate\/f\/HybridTextSyntax-1-2.html\r\nIn colorscheme FluidVision: http:\/\/antelucan.com\/vimupdate\/f\/HybridTextSyntax-1-2.fluidvision.html\r\nIn colorscheme Spectro: http:\/\/antelucan.com\/vimupdate\/f\/HybridTextSyntax-1-2.spectro.html\r\n\r\nPlain text file: http:\/\/antelucan.com\/vimupdate\/f\/HybridTextSyntax-1-2.txt\r\n\r\nMind Maps may be converted at Text 2 Mind Map (http:\/\/www.text2mindmap.com): note that only *ten* levels are supported, and pasted text must use tabs instead of spaces.\r\n\r\nMind Map results from text2mindmap.com: http:\/\/antelucan.com\/vimupdate\/f\/NonsenseMindMap.png\r\nMind Map highlighted by HybridText: http:\/\/antelucan.com\/vimupdate\/f\/NonsenseMindMap.html\r\n\r\n----------------------------------------------------------------------------------------------------------------------------\r\n\r\nUpdate history:\r\n\r\nVersion 1.2 fixes a major top-level goof (I was configuring so much stuff at the bottom, I accidentally switched off text emphasis at the top!) Apart from that, there's more support for Markdown and reStructuredText, extended support for block quotes, and various adjustments and fixes. I feel there's more to do, but I need a breather.\r\n\r\nThe support file (linked above) has been re-organized into better groupings, in order to demonstrate\/check the highlighting. Instead of going all through Markdown, and then reStructuredText, like things are put together--for example, the two markups use a slightly different method of indicating line breaks\/blocks of lines, so it's useful to put them together in order to make sure the highlighting is consistent between different kinds of documents.\r\n\r\nVersion 1.1 introduces Mind Mapping--12 levels of gradient indentations for brainstorming.\r\n\r\nVersion 1.1 also now includes ColorBoost, an optional enhancement for existing colorschemes. ColorBoost defines header levels, creates gradiated effects, and allows text emphasis within other definitions. This is a cheat to make HybridText compatible with other schemes, and can be turned off with a line in VIMRC.\r\n\r\nChanging colorschemes with a file open will clear ColorBoost colors until the buffer is reloaded. Type command :e to restore.\r\n\r\n\r\nThe following pages are examples using different colorschemes in version 1.1, in order to demonstrate ColorBoost.\r\n\r\nSample, Festoon Light: http:\/\/antelucan.com\/vimupdate\/f\/hybrid-txt-festoon-light.html\r\nSample, Festoon Dark: http:\/\/antelucan.com\/vimupdate\/f\/hybrid-txt-festoon-dark.html\r\nSample, Solarized Dark with ColorBoost: http:\/\/antelucan.com\/vimupdate\/f\/hybrid-txt-solarized-dark.html\r\nSample, Twilight with ColorBoost: http:\/\/antelucan.com\/vimupdate\/f\/hybrid-txt-twilight.html\r\nSample, CalmBreeze with ColorBoost: http:\/\/antelucan.com\/vimupdate\/f\/hybrid-txt-calmbreeze.html\r\n\r\nSample, Tabula without ColorBoost: http:\/\/antelucan.com\/vimupdate\/f\/hybrid-txt-tabula.html\r\n\r\nVersion 1.0: [Fixed in 1.1] For best results (but not required), use the colorscheme Festoon vimscript #3852. Text emphasis within other defined blocks require extra definitions, and many colorschemes fail to support header levels. Nested blockquotes use a gradiated colorscheme especially written for Festoon.\r\n","install_details":"Save the file to your syntax directory.\r\n\r\nTo test: open a text file and enter the command :set filetype=hybrid\r\n\r\nTo load the syntax automatically, create a file called 'txt.vim' in your ftdetect directory with the following line inside:\r\n\r\nau BufRead,BufNewFile *.txt\tset syntax=hybrid\r\n","5":"Save the file to your syntax directory.\r\n\r\nTo test: open a text file and enter the command :set filetype=hybrid\r\n\r\nTo load the syntax automatically, create a file called 'txt.vim' in your ftdetect directory with the following line inside:\r\n\r\nau BufRead,BufNewFile *.txt\tset syntax=hybrid\r\n","first_name":"carson","6":"carson","last_name":"fire","7":"fire","releases":[{"0":"4188","vim_version":"7.3","1":"7.3","script_version":"1.2","2":"1.2","version_comment":"More support for Markdown and reStructuredText, including line breaks\/blocks, cosmetic support for setext headers, and expanded support for block quotes; more refinements to dialogue\/quotation highlighting; and fixed a MAJOR goof from 1.1: top-level text emphasis disappeared in the last version.  Many apologies!","3":"More support for Markdown and reStructuredText, including line breaks\/blocks, cosmetic support for setext headers, and expanded support for block quotes; more refinements to dialogue\/quotation highlighting; and fixed a MAJOR goof from 1.1: top-level text emphasis disappeared in the last version.  Many apologies!","package":"hybrid.vim","4":"hybrid.vim","src_id":"18494","5":"18494","creation_date":"1345999954","6":"1345999954"},{"0":"4188","vim_version":"7.3","1":"7.3","script_version":"1.1","2":"1.1","version_comment":"Added a gradiated indentation scheme for Mind Mapping; optional ColorBoost enhances pre-existing colorschemes.","3":"Added a gradiated indentation scheme for Mind Mapping; optional ColorBoost enhances pre-existing colorschemes.","package":"hybrid.vim","4":"hybrid.vim","src_id":"18473","5":"18473","creation_date":"1345767642","6":"1345767642"},{"0":"4188","vim_version":"7.3","1":"7.3","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"hybrid.vim","4":"hybrid.vim","src_id":"18459","5":"18459","creation_date":"1345670593","6":"1345670593"}]},"4187":{"script_id":"4187","0":"4187","script_name":"cmd.vim","1":"cmd.vim","script_type":"color scheme","2":"color scheme","summary":"Color scheme for the windows XP full screen console","3":"Color scheme for the windows XP full screen console","description":"This scheme was made for the 16 color full screen console in Windows XP. It's named \"cmd\" after cmd.exe. Full screen consoles give an immersive experience I prefer over a window. But there aren't many schemes designed for a 16 color console.\r\n\r\nEvery option has been tested in the windows XP console to make sure it looks OK. (except for commented options)","4":"This scheme was made for the 16 color full screen console in Windows XP. It's named \"cmd\" after cmd.exe. Full screen consoles give an immersive experience I prefer over a window. But there aren't many schemes designed for a 16 color console.\r\n\r\nEvery option has been tested in the windows XP console to make sure it looks OK. (except for commented options)","install_details":"Put the file in your \"colors\" folder.","5":"Put the file in your \"colors\" folder.","first_name":"Mike","6":"Mike","last_name":"Z","7":"Z","releases":[{"0":"4187","vim_version":"7.3","1":"7.3","script_version":"2.0","2":"2.0","version_comment":"More options specified and a few tweaks.","3":"More options specified and a few tweaks.","package":"cmd.vim","4":"cmd.vim","src_id":"18649","5":"18649","creation_date":"1348235388","6":"1348235388"},{"0":"4187","vim_version":"7.3","1":"7.3","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"cmd.vim","4":"cmd.vim","src_id":"18457","5":"18457","creation_date":"1345662076","6":"1345662076"}]},"4186":{"script_id":"4186","0":"4186","script_name":"dwm.vim","1":"dwm.vim","script_type":"utility","2":"utility","summary":"Tiled Window Management for Vim","3":"Tiled Window Management for Vim","description":"dwm.vim adds tiled window management capabilities to Vim. \r\nIt is highly inspired by dwm (Dynamic Window Manager) [http:\/\/dwm.suckless.org\/] tiled layout management. \r\n\r\nWindows are always organised as follows: \r\n\r\n================= \r\n|              |       S1         | \r\n|              |========== \r\n|      M     |       S2         | \r\n|              |========== \r\n|              |       S3         | \r\n================= \r\n\r\nUse the following commands to create, close and browse windows: \r\n\r\n- CTRL-N Creates a new window and place it in the area [M] & stacks all previous windows in the [S] areas. \r\n- CTRL-C Close the current window if no unsaved changes \r\n- CTRL-J Jumps to next window (clockwise) \r\n- CTRL-K Jumps to previous window (anti-clockwise) \r\n- CTRL-H Focus the current window, that is, place it in the [M] area & stacks all other windows in the [S] areas \r\n\r\nThere's only one tiled layout available right now, but the project is open for contribution: \r\n\r\nPLEASE FORK: https:\/\/github.com\/spolu\/dwm.vim\r\n ","4":"dwm.vim adds tiled window management capabilities to Vim. \r\nIt is highly inspired by dwm (Dynamic Window Manager) [http:\/\/dwm.suckless.org\/] tiled layout management. \r\n\r\nWindows are always organised as follows: \r\n\r\n================= \r\n|              |       S1         | \r\n|              |========== \r\n|      M     |       S2         | \r\n|              |========== \r\n|              |       S3         | \r\n================= \r\n\r\nUse the following commands to create, close and browse windows: \r\n\r\n- CTRL-N Creates a new window and place it in the area [M] & stacks all previous windows in the [S] areas. \r\n- CTRL-C Close the current window if no unsaved changes \r\n- CTRL-J Jumps to next window (clockwise) \r\n- CTRL-K Jumps to previous window (anti-clockwise) \r\n- CTRL-H Focus the current window, that is, place it in the [M] area & stacks all other windows in the [S] areas \r\n\r\nThere's only one tiled layout available right now, but the project is open for contribution: \r\n\r\nPLEASE FORK: https:\/\/github.com\/spolu\/dwm.vim\r\n ","install_details":"- copy the dwn.vim file into $HOME\/.vim\/plugin directory\r\n- start vim","5":"- copy the dwn.vim file into $HOME\/.vim\/plugin directory\r\n- start vim","first_name":"Stanislas","6":"Stanislas","last_name":"Polu","7":"Polu","releases":[{"0":"4186","vim_version":"7.0","1":"7.0","script_version":"0.1.2","2":"0.1.2","version_comment":"- use of `hasmapto`\r\n- various cleanup","3":"- use of `hasmapto`\r\n- various cleanup","package":"dwm.vim","4":"dwm.vim","src_id":"19295","5":"19295","creation_date":"1357126221","6":"1357126221"},{"0":"4186","vim_version":"7.0","1":"7.0","script_version":"0.1.1","2":"0.1.1","version_comment":"- Changed mapping from C-F to C-H for focus\r\n- Added a sentinel for mappings to avoid conflicts\r\n- Added a fullscreen mode (C-L) (focus to return to normal mode)","3":"- Changed mapping from C-F to C-H for focus\r\n- Added a sentinel for mappings to avoid conflicts\r\n- Added a fullscreen mode (C-L) (focus to return to normal mode)","package":"dwm.vim","4":"dwm.vim","src_id":"18463","5":"18463","creation_date":"1345739812","6":"1345739812"},{"0":"4186","vim_version":"7.0","1":"7.0","script_version":"0.1.0","2":"0.1.0","version_comment":"Initial upload","3":"Initial upload","package":"dwm.vim","4":"dwm.vim","src_id":"18456","5":"18456","creation_date":"1345656217","6":"1345656217"}]},"4185":{"script_id":"4185","0":"4185","script_name":"PrevInsertComplete","1":"PrevInsertComplete","script_type":"utility","2":"utility","summary":"Recall and insert mode completion for previously inserted text.","3":"Recall and insert mode completion for previously inserted text.","description":"DESCRIPTION\r\nThis plugin lets you quickly recall previous insertions and insert them again\r\nat the cursor position. Essentially, it's the built-in i_CTRL-A command\r\nsouped up with history and selection.\r\n\r\nIn insert mode, you can narrow down the candidates by typing a keyword first;\r\nthen, only insertions with a match will be offered as completion candidates.\r\nIn normal mode, you can directly recall the [count]'th previous insertion, or\r\nhave it list the last 9 insertions and let you choose.\r\nTo avoid that the many minor tactical edits clobber up the history, only\r\nsignificant (longer) edits are recalled.\r\n\r\nSEE ALSO\r\n- Check out the CompleteHelper.vim plugin page (vimscript #3914) for a full\r\n  list of insert mode completions powered by it.\r\n\r\nUSAGE\r\nCTRL-X CTRL-A           Find previous insertions (i_CTRL-A, quote.) whose\r\n                        contents match the keyword before the cursor. First, a\r\n                        match at the beginning is tried; if that returns no\r\n                        results, it may match anywhere.\r\n                        Further use of CTRL-X CTRL-A will append insertions done\r\n                        after the previous recall.\r\n\r\n[count]q<CTRL-@>        Recall and append previous [count]'th insertion.\r\n\r\n[count]q<CTRL-A>        Lists the last 9 insertions, then prompts for a number.\r\n                        The chosen insertion is appended [count] times.","4":"DESCRIPTION\r\nThis plugin lets you quickly recall previous insertions and insert them again\r\nat the cursor position. Essentially, it's the built-in i_CTRL-A command\r\nsouped up with history and selection.\r\n\r\nIn insert mode, you can narrow down the candidates by typing a keyword first;\r\nthen, only insertions with a match will be offered as completion candidates.\r\nIn normal mode, you can directly recall the [count]'th previous insertion, or\r\nhave it list the last 9 insertions and let you choose.\r\nTo avoid that the many minor tactical edits clobber up the history, only\r\nsignificant (longer) edits are recalled.\r\n\r\nSEE ALSO\r\n- Check out the CompleteHelper.vim plugin page (vimscript #3914) for a full\r\n  list of insert mode completions powered by it.\r\n\r\nUSAGE\r\nCTRL-X CTRL-A           Find previous insertions (i_CTRL-A, quote.) whose\r\n                        contents match the keyword before the cursor. First, a\r\n                        match at the beginning is tried; if that returns no\r\n                        results, it may match anywhere.\r\n                        Further use of CTRL-X CTRL-A will append insertions done\r\n                        after the previous recall.\r\n\r\n[count]q<CTRL-@>        Recall and append previous [count]'th insertion.\r\n\r\n[count]q<CTRL-A>        Lists the last 9 insertions, then prompts for a number.\r\n                        The chosen insertion is appended [count] times.","install_details":"INSTALLATION\r\nThe code is hosted in a Git repo at\r\n    https:\/\/github.com\/inkarkat\/vim-PrevInsertComplete\r\nYou can use your favorite plugin manager, or \"git clone\" into a directory used\r\nfor Vim packages. Releases are on the \"stable\" branch, the latest unstable\r\ndevelopment snapshot on \"master\".\r\n\r\nThis script is also packaged as a vimball. If you have the \"gunzip\"\r\ndecompressor in your PATH, simply edit the *.vmb.gz package in Vim; otherwise,\r\ndecompress the archive first, e.g. using WinZip. Inside Vim, install by\r\nsourcing the vimball or via the :UseVimball command.\r\n    vim PrevInsertComplete*.vmb.gz\r\n    :so %\r\nTo uninstall, use the :RmVimball command.\r\n\r\nDEPENDENCIES\r\n- Requires Vim 7.0 or higher.\r\n- Requires the ingo-library.vim plugin (vimscript #4433), version 1.015 or\r\n  higher.\r\n- Requires the CompleteHelper.vim plugin (vimscript #3914), version 1.11 or\r\n  higher.\r\n- repeat.vim (vimscript #2136) plugin (optional)\r\n\r\nCONFIGURATION\r\nFor a permanent configuration, put the following commands into your vimrc:\r\n\r\nVery short insertions are often just minor corrections and not worthwhile to\r\nrecall. The threshold number of inserted characters can be set via:\r\n    let g:PrevInsertComplete_MinLength = 6\r\n\r\nThe number of recorded insertions can be adjusted.\r\n    let g:PrevInsertComplete_HistorySize = 100\r\n\r\nThe recorded insertions can be kept and restored across Vim sessions, using\r\nthe viminfo file. For this to work, the \"!\" flag must be part of the\r\n'viminfo' setting:\r\n    set viminfo+=!  \" Save and restore global variables.\r\nBy default, all recorded insertions are persisted. You can reduce the maximum\r\nnumber of insertions to be stored via:\r\n    let g:PrevInsertComplete_PersistSize = 10\r\nor completely turn off persistence by setting the variable to 0.\r\n\r\nIf you want to use different mappings, map your keys to the\r\n<Plug>(PrevInsert...) mapping targets _before_ sourcing the script (e.g. in\r\nyour vimrc):\r\n    imap <C-a> <Plug>(PrevInsertComplete)\r\n    nmap <Leader><C-a> <Plug>(PrevInsertRecall)\r\n    nmap <Leader><A-a> <Plug>(PrevInsertList)","5":"INSTALLATION\r\nThe code is hosted in a Git repo at\r\n    https:\/\/github.com\/inkarkat\/vim-PrevInsertComplete\r\nYou can use your favorite plugin manager, or \"git clone\" into a directory used\r\nfor Vim packages. Releases are on the \"stable\" branch, the latest unstable\r\ndevelopment snapshot on \"master\".\r\n\r\nThis script is also packaged as a vimball. If you have the \"gunzip\"\r\ndecompressor in your PATH, simply edit the *.vmb.gz package in Vim; otherwise,\r\ndecompress the archive first, e.g. using WinZip. Inside Vim, install by\r\nsourcing the vimball or via the :UseVimball command.\r\n    vim PrevInsertComplete*.vmb.gz\r\n    :so %\r\nTo uninstall, use the :RmVimball command.\r\n\r\nDEPENDENCIES\r\n- Requires Vim 7.0 or higher.\r\n- Requires the ingo-library.vim plugin (vimscript #4433), version 1.015 or\r\n  higher.\r\n- Requires the CompleteHelper.vim plugin (vimscript #3914), version 1.11 or\r\n  higher.\r\n- repeat.vim (vimscript #2136) plugin (optional)\r\n\r\nCONFIGURATION\r\nFor a permanent configuration, put the following commands into your vimrc:\r\n\r\nVery short insertions are often just minor corrections and not worthwhile to\r\nrecall. The threshold number of inserted characters can be set via:\r\n    let g:PrevInsertComplete_MinLength = 6\r\n\r\nThe number of recorded insertions can be adjusted.\r\n    let g:PrevInsertComplete_HistorySize = 100\r\n\r\nThe recorded insertions can be kept and restored across Vim sessions, using\r\nthe viminfo file. For this to work, the \"!\" flag must be part of the\r\n'viminfo' setting:\r\n    set viminfo+=!  \" Save and restore global variables.\r\nBy default, all recorded insertions are persisted. You can reduce the maximum\r\nnumber of insertions to be stored via:\r\n    let g:PrevInsertComplete_PersistSize = 10\r\nor completely turn off persistence by setting the variable to 0.\r\n\r\nIf you want to use different mappings, map your keys to the\r\n<Plug>(PrevInsert...) mapping targets _before_ sourcing the script (e.g. in\r\nyour vimrc):\r\n    imap <C-a> <Plug>(PrevInsertComplete)\r\n    nmap <Leader><C-a> <Plug>(PrevInsertRecall)\r\n    nmap <Leader><A-a> <Plug>(PrevInsertList)","first_name":"Ingo","6":"Ingo","last_name":"Karkat","7":"Karkat","releases":[{"0":"4185","vim_version":"7.0","1":"7.0","script_version":"1.12","2":"1.12","version_comment":"- BUG: \"E899: Argument of insert() must be a List or Blob\" in PrevInsertComplete#Record#Insertion().","3":"- BUG: \"E899: Argument of insert() must be a List or Blob\" in PrevInsertComplete#Record#Insertion().","package":"PrevInsertComplete-1.12.vmb.gz","4":"PrevInsertComplete-1.12.vmb.gz","src_id":"27423","5":"27423","creation_date":"1609169515","6":"1609169515"},{"0":"4185","vim_version":"7.0","1":"7.0","script_version":"1.11","2":"1.11","version_comment":"- Change qa mapping default to q<C-@>; I found it confusing that I could not record macros into register a any more. To keep the previous mapping, use > :nmap qa <Plug>(PrevInsertRecall)\r\n- Make recall of insertion (q<CTRL-@>, q<CTRL-A>) repeatable.\r\n- Add dependency to ingo-library (vimscript #4433). *** You need to separately install ingo-library (vimscript #4433) version 1.015 (or higher)! ***","3":"- Change qa mapping default to q<C-@>; I found it confusing that I could not record macros into register a any more. To keep the previous mapping, use > :nmap qa <Plug>(PrevInsertRecall)\r\n- Make recall of insertion (q<CTRL-@>, q<CTRL-A>) repeatable.\r\n- Add dependency to ingo-library (vimscript #4433). *** You need to separately install ingo-library (vimscript #4433) version 1.015 (or higher)! ***","package":"PrevInsertComplete-1.11.vmb.gz","4":"PrevInsertComplete-1.11.vmb.gz","src_id":"21124","5":"21124","creation_date":"1385714512","6":"1385714512"},{"0":"4185","vim_version":"7.0","1":"7.0","script_version":"1.10","2":"1.10","version_comment":"ENH: Persist recorded insertions across Vim invocations in the |viminfo| file. This can be controlled by the |g:PrevInsertComplete_PersistSize|\r\nconfiguration.","3":"ENH: Persist recorded insertions across Vim invocations in the |viminfo| file. This can be controlled by the |g:PrevInsertComplete_PersistSize|\r\nconfiguration.","package":"PrevInsertComplete-1.10.vmb.gz","4":"PrevInsertComplete-1.10.vmb.gz","src_id":"18808","5":"18808","creation_date":"1350285206","6":"1350285206"},{"0":"4185","vim_version":"7.0","1":"7.0","script_version":"1.00","2":"1.00","version_comment":"Initial upload","3":"Initial upload","package":"PrevInsertComplete-1.00.vmb.gz","4":"PrevInsertComplete-1.00.vmb.gz","src_id":"18454","5":"18454","creation_date":"1345633322","6":"1345633322"}]},"4184":{"script_id":"4184","0":"4184","script_name":"pybreak","1":"pybreak","script_type":"ftplugin","2":"ftplugin","summary":"Fast toggling of set_trace statement in python files, for easier debugging","3":"Fast toggling of set_trace statement in python files, for easier debugging","description":"Get the latest version from github: https:\/\/github.com\/nthorne\/vim-pybreak\r\n\r\nPybreak is a python filetype plugin for easily toggling set_trace statements, making it more convenient to debug python scripts. The following python filetype keymappings are provided:\r\n\r\n* <localleader>d - inserts a set_trace statement after the cursor position if\r\n  no statements (as inserted by pybreak) are found on the current line. _If_,\r\n  however, any set_trace statements are found at the current line, they are\r\n  removed, and no further set_trace statements are inserted.\r\n* <localleader>D - as <localleader>d, with the minor difference that this\r\n  keymapping inserts the set_trace statement _at_ the cursor position.\r\n* <localleader>da - removes _all_ set_trace statements in the active buffer\r\n* <localleader>de - toggles set_trace (see <localleader>d), writes the\r\n  buffer to disk, and then executes the file with the python interpreter.\r\n\r\nIf the script does not work, make sure that the file being edited is recognized as a python file (set ft? returning filetype=python).\r\n\r\nThis script is released under the GNU General Public License v.3","4":"Get the latest version from github: https:\/\/github.com\/nthorne\/vim-pybreak\r\n\r\nPybreak is a python filetype plugin for easily toggling set_trace statements, making it more convenient to debug python scripts. The following python filetype keymappings are provided:\r\n\r\n* <localleader>d - inserts a set_trace statement after the cursor position if\r\n  no statements (as inserted by pybreak) are found on the current line. _If_,\r\n  however, any set_trace statements are found at the current line, they are\r\n  removed, and no further set_trace statements are inserted.\r\n* <localleader>D - as <localleader>d, with the minor difference that this\r\n  keymapping inserts the set_trace statement _at_ the cursor position.\r\n* <localleader>da - removes _all_ set_trace statements in the active buffer\r\n* <localleader>de - toggles set_trace (see <localleader>d), writes the\r\n  buffer to disk, and then executes the file with the python interpreter.\r\n\r\nIf the script does not work, make sure that the file being edited is recognized as a python file (set ft? returning filetype=python).\r\n\r\nThis script is released under the GNU General Public License v.3","install_details":"Preferred method of installation is to use pathogen (vimscript #2332). If you still want to install pybreak the old fashioned way, simply extract the tarball into your .vim directory.","5":"Preferred method of installation is to use pathogen (vimscript #2332). If you still want to install pybreak the old fashioned way, simply extract the tarball into your .vim directory.","first_name":"Niklas","6":"Niklas","last_name":"Th\u00c3\u00b6rne","7":"Th\u00c3\u00b6rne","releases":[{"0":"4184","vim_version":"7.0","1":"7.0","script_version":"1.1","2":"1.1","version_comment":"Corrected bug where line starting with ; could be inserted. Preserving indentation when first item on line.","3":"Corrected bug where line starting with ; could be inserted. Preserving indentation when first item on line.","package":"pybreak-1.1.tar.gz","4":"pybreak-1.1.tar.gz","src_id":"18472","5":"18472","creation_date":"1345760310","6":"1345760310"},{"0":"4184","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"pybreak-1.0.tar.gz","4":"pybreak-1.0.tar.gz","src_id":"18453","5":"18453","creation_date":"1345627103","6":"1345627103"}]},"4183":{"script_id":"4183","0":"4183","script_name":"vim-g","1":"vim-g","script_type":"utility","2":"utility","summary":"Quick Google lookup directly from Vim","3":"Quick Google lookup directly from Vim","description":"vim-g\r\n\r\nvim-g is a tiny plugin that allows you to perform a quick Google search directly from Vim. It opens a new browser window with results. vim-g uses Perl for url encoding.\r\n\r\nThe most recent version can be found on Github: https:\/\/github.com\/szw\/vim-g\r\n\r\nUsage\r\n\r\nTo lookup a word (or words) in Google use G command:\r\n\r\n:G hello\r\n:G start up\r\n\r\nG command can use a word under the cursor. Just move the cursor to the word and type the same command in the command line:\r\n\r\n:G\r\n\r\nAdditionally, you can select words in the visual mode exactly in the same way. Just select words and type :G. You can also prepend your selection with more clues:\r\n\r\n:G function\r\n:G ruby\r\n\r\nThere is also a special command named Gf to prepend the current file type automatically:\r\n\r\n:Gf\r\n:Gf strpos\r\n:Gf function\r\n\r\nThere is also a special command named Gf to prepend the current file type automatically:\r\n\r\n:Gf\r\n:Gf strpos\r\n:Gf function\r\n\r\nMoreover, you can use double quotes (\") to perform phrase search. Just enclose some words between quotation marks as you type. Also, you don't have to close manually open quotation marks. vim-g will add the missing one itself.\r\n\r\nExamples:\r\n\r\n:G \"foo bar\"\r\n:Gf \" help substitute\r\n:G foo bar \" something else\r\n\r\nWhat's even more interesting this also works in the visual mode. Therefore, you can perform a strict phrase search on selected words. Just select words and type:\r\n\r\n:G \"\r\n:G \"foo bar\r\n\r\nConfiguration\r\n\r\nThere are just a few global variables (options) you may set in the .vimrc file.\r\n\r\n    g:vim_g_open_command\r\n\r\n    Sets the command used to open the URL. In case of Ubuntu this could be \"xdg-open\" and that is the default value:\r\n\r\n    let g:vim_g_open_command = \"xdg-open\"\r\n\r\n    g:vim_g_perl_command\r\n\r\n    Sets the Perl command. By default it's \"perl\":\r\n\r\n    let g:vim_g_perl_command = \"perl\"\r\n\r\n    g:vim_g_query_url\r\n\r\n    Sets the query URL. By default it points to Google of course, but you might want to place your favorite search engine there:\r\n\r\n    let g:vim_g_query_url = \"http:\/\/google.com\/search?q=\"\r\n\r\nLicense\r\n\r\nCopyright \u00c2\u00a9 2012 Szymon Wrozynski. Distributed under the same terms as Vim itself.\r\n\r\nSee :help license","4":"vim-g\r\n\r\nvim-g is a tiny plugin that allows you to perform a quick Google search directly from Vim. It opens a new browser window with results. vim-g uses Perl for url encoding.\r\n\r\nThe most recent version can be found on Github: https:\/\/github.com\/szw\/vim-g\r\n\r\nUsage\r\n\r\nTo lookup a word (or words) in Google use G command:\r\n\r\n:G hello\r\n:G start up\r\n\r\nG command can use a word under the cursor. Just move the cursor to the word and type the same command in the command line:\r\n\r\n:G\r\n\r\nAdditionally, you can select words in the visual mode exactly in the same way. Just select words and type :G. You can also prepend your selection with more clues:\r\n\r\n:G function\r\n:G ruby\r\n\r\nThere is also a special command named Gf to prepend the current file type automatically:\r\n\r\n:Gf\r\n:Gf strpos\r\n:Gf function\r\n\r\nThere is also a special command named Gf to prepend the current file type automatically:\r\n\r\n:Gf\r\n:Gf strpos\r\n:Gf function\r\n\r\nMoreover, you can use double quotes (\") to perform phrase search. Just enclose some words between quotation marks as you type. Also, you don't have to close manually open quotation marks. vim-g will add the missing one itself.\r\n\r\nExamples:\r\n\r\n:G \"foo bar\"\r\n:Gf \" help substitute\r\n:G foo bar \" something else\r\n\r\nWhat's even more interesting this also works in the visual mode. Therefore, you can perform a strict phrase search on selected words. Just select words and type:\r\n\r\n:G \"\r\n:G \"foo bar\r\n\r\nConfiguration\r\n\r\nThere are just a few global variables (options) you may set in the .vimrc file.\r\n\r\n    g:vim_g_open_command\r\n\r\n    Sets the command used to open the URL. In case of Ubuntu this could be \"xdg-open\" and that is the default value:\r\n\r\n    let g:vim_g_open_command = \"xdg-open\"\r\n\r\n    g:vim_g_perl_command\r\n\r\n    Sets the Perl command. By default it's \"perl\":\r\n\r\n    let g:vim_g_perl_command = \"perl\"\r\n\r\n    g:vim_g_query_url\r\n\r\n    Sets the query URL. By default it points to Google of course, but you might want to place your favorite search engine there:\r\n\r\n    let g:vim_g_query_url = \"http:\/\/google.com\/search?q=\"\r\n\r\nLicense\r\n\r\nCopyright \u00c2\u00a9 2012 Szymon Wrozynski. Distributed under the same terms as Vim itself.\r\n\r\nSee :help license","install_details":"Installation\r\n\r\nPlace in ~\/.vim\/plugin\/g.vim or in case of Pathogen:\r\n\r\ncd ~\/.vim\/bundle\r\ngit clone https:\/\/github.com\/szw\/vim-g.git","5":"Installation\r\n\r\nPlace in ~\/.vim\/plugin\/g.vim or in case of Pathogen:\r\n\r\ncd ~\/.vim\/bundle\r\ngit clone https:\/\/github.com\/szw\/vim-g.git","first_name":"Szymon","6":"Szymon","last_name":"Wrozynski","7":"Wrozynski","releases":[{"0":"4183","vim_version":"7.0","1":"7.0","script_version":"0.0.5","2":"0.0.5","version_comment":"Added Vim help file","3":"Added Vim help file","package":"vim-g.zip","4":"vim-g.zip","src_id":"19290","5":"19290","creation_date":"1357080037","6":"1357080037"},{"0":"4183","vim_version":"7.0","1":"7.0","script_version":"0.0.4","2":"0.0.4","version_comment":"Automatically close every open quotation mark, not only the standalone ones.","3":"Automatically close every open quotation mark, not only the standalone ones.","package":"szw-vim-g-0.0.4.zip","4":"szw-vim-g-0.0.4.zip","src_id":"18461","5":"18461","creation_date":"1345711586","6":"1345711586"},{"0":"4183","vim_version":"7.0","1":"7.0","script_version":"0.0.3","2":"0.0.3","version_comment":"Adds support for strict phrase search","3":"Adds support for strict phrase search","package":"szw-vim-g-0.0.3.zip","4":"szw-vim-g-0.0.3.zip","src_id":"18460","5":"18460","creation_date":"1345676181","6":"1345676181"},{"0":"4183","vim_version":"7.0","1":"7.0","script_version":"0.0.2","2":"0.0.2","version_comment":"Initial upload","3":"Initial upload","package":"szw-vim-g-0.0.2.zip","4":"szw-vim-g-0.0.2.zip","src_id":"18451","5":"18451","creation_date":"1345626315","6":"1345626315"}]},"4182":{"script_id":"4182","0":"4182","script_name":"shellasync.vim","1":"shellasync.vim","script_type":"utility","2":"utility","summary":"shellasync.vim plugin for asynchronously executing shell commands in vim","3":"shellasync.vim plugin for asynchronously executing shell commands in vim","description":"shellasync.vim plugin allows you to asynchronously execute shell commands inside vim and see \r\noutput inside a seperate window buffer without waiting for a command to finish. \r\nIt uses python's subprocess and threading capabilities to execute shell commands in seperate thread and non-blockingly \r\nget the output as the command executes\r\n\r\nPlatform: only unix based operating systems are supported\r\n\r\nRequirements: vim compiled with python support\r\n\r\nGithub: https:\/\/github.com\/troydm\/shellasync.vim","4":"shellasync.vim plugin allows you to asynchronously execute shell commands inside vim and see \r\noutput inside a seperate window buffer without waiting for a command to finish. \r\nIt uses python's subprocess and threading capabilities to execute shell commands in seperate thread and non-blockingly \r\nget the output as the command executes\r\n\r\nPlatform: only unix based operating systems are supported\r\n\r\nRequirements: vim compiled with python support\r\n\r\nGithub: https:\/\/github.com\/troydm\/shellasync.vim","install_details":"","5":"","first_name":"Dmitry","6":"Dmitry","last_name":"Geurkov","7":"Geurkov","releases":[{"0":"4182","vim_version":"7.3","1":"7.3","script_version":"0.3.7","2":"0.3.7","version_comment":"lot of bugs fixed","3":"lot of bugs fixed","package":"shellasync.vim-0.3.7.zip","4":"shellasync.vim-0.3.7.zip","src_id":"19457","5":"19457","creation_date":"1359658445","6":"1359658445"},{"0":"4182","vim_version":"7.3","1":"7.3","script_version":"0.3.6","2":"0.3.6","version_comment":"added ShellSend and ShellSelect commands","3":"added ShellSend and ShellSelect commands","package":"shellasync.vim-0.3.6.zip","4":"shellasync.vim-0.3.6.zip","src_id":"19203","5":"19203","creation_date":"1355840389","6":"1355840389"},{"0":"4182","vim_version":"7.0","1":"7.0","script_version":"0.3.5","2":"0.3.5","version_comment":"pseudo shell terminal added","3":"pseudo shell terminal added","package":"shellasync.vim-0.3.5.zip","4":"shellasync.vim-0.3.5.zip","src_id":"18637","5":"18637","creation_date":"1348001684","6":"1348001684"},{"0":"4182","vim_version":"7.0","1":"7.0","script_version":"0.3.4","2":"0.3.4","version_comment":"complete rewrite of plugin\r\nadded ShellList command","3":"complete rewrite of plugin\r\nadded ShellList command","package":"shellasync.vim-0.3.4.zip","4":"shellasync.vim-0.3.4.zip","src_id":"18566","5":"18566","creation_date":"1347050125","6":"1347050125"},{"0":"4182","vim_version":"7.0","1":"7.0","script_version":"0.3.3","2":"0.3.3","version_comment":"better output handling","3":"better output handling","package":"shellasync.vim-0.3.3.zip","4":"shellasync.vim-0.3.3.zip","src_id":"18541","5":"18541","creation_date":"1346686630","6":"1346686630"},{"0":"4182","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"shellasync.vim-0.1.zip","4":"shellasync.vim-0.1.zip","src_id":"18438","5":"18438","creation_date":"1345473068","6":"1345473068"}]},"4181":{"script_id":"4181","0":"4181","script_name":"omgrofl.vim","1":"omgrofl.vim","script_type":"syntax","2":"syntax","summary":"syntax file for the Omgrofl language","3":"syntax file for the Omgrofl language","description":"This is a syntax file for the Omgrofl language:\r\nhttp:\/\/esolangs.org\/wiki\/omgrofl\r\n\r\nSee the code on Github: https:\/\/github.com\/bfontaine\/omgrofl.vim","4":"This is a syntax file for the Omgrofl language:\r\nhttp:\/\/esolangs.org\/wiki\/omgrofl\r\n\r\nSee the code on Github: https:\/\/github.com\/bfontaine\/omgrofl.vim","install_details":"Put the script into ~\/.vim\/syntax\/","5":"Put the script into ~\/.vim\/syntax\/","first_name":"Baptiste","6":"Baptiste","last_name":"Fontaine","7":"Fontaine","releases":[{"0":"4181","vim_version":"7.0","1":"7.0","script_version":"1.0.1","2":"1.0.1","version_comment":"- Support for the 'nope' keyword\r\n- Negative numbers removed\r\n- Some improvements for the 'wtf' statement","3":"- Support for the 'nope' keyword\r\n- Negative numbers removed\r\n- Some improvements for the 'wtf' statement","package":"omgrofl.vim","4":"omgrofl.vim","src_id":"18448","5":"18448","creation_date":"1345590096","6":"1345590096"},{"0":"4181","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"omgrofl.vim","4":"omgrofl.vim","src_id":"18431","5":"18431","creation_date":"1345373774","6":"1345373774"}]},"4180":{"script_id":"4180","0":"4180","script_name":"vim-dict","1":"vim-dict","script_type":"utility","2":"utility","summary":"The Dict client for Vim","3":"The Dict client for Vim","description":"vim-dict\r\n\r\nvim-dict is a dict client. It uses curl to connect to dict servers, so make sure you have curl installed.\r\n\r\nThe most recent version can be found on github: https:\/\/github.com\/szw\/vim-dict\r\n\r\nUsage\r\n\r\nTo lookup a word (or words) in the dictionary use Dict command:\r\n\r\n:Dict hello\r\n:Dict start up\r\n\r\nThe Dict command uses hosts and databases defined in the g:dict_hosts global list. By default it is set to [[\"dict.org\", [\"all\"]]] (the format will be explained a bit later).\r\n\r\nDict command can use a current word under the cursor. Just move the cursor to a word and type in the command line:\r\n\r\n:Dict\r\n\r\nYou can also select words in the visual mode with help of the DictSelection command:\r\n\r\n:DictSelection\r\n\r\nConfiguration\r\n\r\nThere are just a few global variables (options) you may set in the .vimrc file.\r\n\r\n    g:dict_hosts\r\n\r\n    The most important one is a list g:dict_hosts mentioned earlier. It combines hosts\/databases used by vim-dict. The list entries are lists themselves and share the following format:\r\n\r\n    [\"host_name\", [\"database1\", \"database2\", ...]]\r\n\r\n    The sample extract from someone's ~\/.vimrc file could look like this:\r\n\r\n    let g:dict_hosts = [\r\n        \\[\"dict.org\", [\"all\"]],\r\n        \\[\"dict.mova.org\", [\"slovnyk_en-pl\", \"slovnyk_pl-en\"]]\r\n    \\]\r\n\r\n    Moreover vim-dict can help you figure out what databases are available on your servers. There is a special command for this:\r\n\r\n    :DictShowDb\r\n\r\n    You can even open your .vimrc and provide some host urls only:\r\n\r\n    let g:dict_hosts = [\r\n        \\[\"dict.org\", []],\r\n        \\[\"dict.mova.org\", []]\r\n    \\]\r\n\r\n    Then save and reload .vimrc, perform DictShowDb and yank-paste the databases you want :).\r\n\r\n    The list of DICT servers can be found on the internet, e.g. here.\r\n\r\n    g:dict_leave_pw\r\n\r\n    If set to 1 vim-dict leaves the preview window (the focus remains on the current window). By default it is set to 0.\r\n\r\n    Example:\r\n\r\n    let g:dict_leave_pw = 0\r\n\r\n    g:dict_curl_command\r\n\r\n    This variable holds the curl command to be fired by Dict function. You will find it handy if curl is not on your $PATH environment variable. By default it is set to \"curl\".\r\n\r\n    Example:\r\n\r\n    let g:dict_curl_command = \"curl\"\r\n\r\n    g:dict_curl_options\r\n\r\n    Sometimes you might want to add additional options to the curl invocation, e.g. additonal proxy settings. By default it defines only the connection timeout. Notice, the option -s (silent) is always present regardless of this variable.\r\n\r\n    Example:\r\n\r\n    let g:dict_curl_options = \"--connect-timeout 30\"\r\n\r\nLicense\r\n\r\nCopyright \u00c2\u00a9 2012 Szymon Wrozynski. Distributed under the same terms as Vim itself. See :help license\r\n\r\n","4":"vim-dict\r\n\r\nvim-dict is a dict client. It uses curl to connect to dict servers, so make sure you have curl installed.\r\n\r\nThe most recent version can be found on github: https:\/\/github.com\/szw\/vim-dict\r\n\r\nUsage\r\n\r\nTo lookup a word (or words) in the dictionary use Dict command:\r\n\r\n:Dict hello\r\n:Dict start up\r\n\r\nThe Dict command uses hosts and databases defined in the g:dict_hosts global list. By default it is set to [[\"dict.org\", [\"all\"]]] (the format will be explained a bit later).\r\n\r\nDict command can use a current word under the cursor. Just move the cursor to a word and type in the command line:\r\n\r\n:Dict\r\n\r\nYou can also select words in the visual mode with help of the DictSelection command:\r\n\r\n:DictSelection\r\n\r\nConfiguration\r\n\r\nThere are just a few global variables (options) you may set in the .vimrc file.\r\n\r\n    g:dict_hosts\r\n\r\n    The most important one is a list g:dict_hosts mentioned earlier. It combines hosts\/databases used by vim-dict. The list entries are lists themselves and share the following format:\r\n\r\n    [\"host_name\", [\"database1\", \"database2\", ...]]\r\n\r\n    The sample extract from someone's ~\/.vimrc file could look like this:\r\n\r\n    let g:dict_hosts = [\r\n        \\[\"dict.org\", [\"all\"]],\r\n        \\[\"dict.mova.org\", [\"slovnyk_en-pl\", \"slovnyk_pl-en\"]]\r\n    \\]\r\n\r\n    Moreover vim-dict can help you figure out what databases are available on your servers. There is a special command for this:\r\n\r\n    :DictShowDb\r\n\r\n    You can even open your .vimrc and provide some host urls only:\r\n\r\n    let g:dict_hosts = [\r\n        \\[\"dict.org\", []],\r\n        \\[\"dict.mova.org\", []]\r\n    \\]\r\n\r\n    Then save and reload .vimrc, perform DictShowDb and yank-paste the databases you want :).\r\n\r\n    The list of DICT servers can be found on the internet, e.g. here.\r\n\r\n    g:dict_leave_pw\r\n\r\n    If set to 1 vim-dict leaves the preview window (the focus remains on the current window). By default it is set to 0.\r\n\r\n    Example:\r\n\r\n    let g:dict_leave_pw = 0\r\n\r\n    g:dict_curl_command\r\n\r\n    This variable holds the curl command to be fired by Dict function. You will find it handy if curl is not on your $PATH environment variable. By default it is set to \"curl\".\r\n\r\n    Example:\r\n\r\n    let g:dict_curl_command = \"curl\"\r\n\r\n    g:dict_curl_options\r\n\r\n    Sometimes you might want to add additional options to the curl invocation, e.g. additonal proxy settings. By default it defines only the connection timeout. Notice, the option -s (silent) is always present regardless of this variable.\r\n\r\n    Example:\r\n\r\n    let g:dict_curl_options = \"--connect-timeout 30\"\r\n\r\nLicense\r\n\r\nCopyright \u00c2\u00a9 2012 Szymon Wrozynski. Distributed under the same terms as Vim itself. See :help license\r\n\r\n","install_details":"Place in ~\/.vim\/plugin\/dict.vim or in case of Pathogen:\r\n\r\ncd ~\/.vim\/bundle\r\ngit clone https:\/\/github.com\/szw\/vim-dict.git\r\n","5":"Place in ~\/.vim\/plugin\/dict.vim or in case of Pathogen:\r\n\r\ncd ~\/.vim\/bundle\r\ngit clone https:\/\/github.com\/szw\/vim-dict.git\r\n","first_name":"Szymon","6":"Szymon","last_name":"Wrozynski","7":"Wrozynski","releases":[{"0":"4180","vim_version":"7.0","1":"7.0","script_version":"1.2.1","2":"1.2.1","version_comment":"Added vim help file and some minor fixes","3":"Added vim help file and some minor fixes","package":"vim-dict.zip","4":"vim-dict.zip","src_id":"19289","5":"19289","creation_date":"1357079895","6":"1357079895"},{"0":"4180","vim_version":"7.0","1":"7.0","script_version":"1.2.0","2":"1.2.0","version_comment":"DictSelection is no longer necessary. Now dict command can be performed in visual mode","3":"DictSelection is no longer necessary. Now dict command can be performed in visual mode","package":"szw-vim-dict-1.2.0.zip","4":"szw-vim-dict-1.2.0.zip","src_id":"18450","5":"18450","creation_date":"1345625754","6":"1345625754"},{"0":"4180","vim_version":"7.0","1":"7.0","script_version":"1.1.1","2":"1.1.1","version_comment":"New options (g:dict_curl_options, g:dict_curl_command) and a few more improvements","3":"New options (g:dict_curl_options, g:dict_curl_command) and a few more improvements","package":"szw-vim-dict-1.1.1.zip","4":"szw-vim-dict-1.1.1.zip","src_id":"18446","5":"18446","creation_date":"1345511796","6":"1345511796"},{"0":"4180","vim_version":"7.0","1":"7.0","script_version":"1.1.0","2":"1.1.0","version_comment":"Support for multiple hosts\/databases. Support for show:db.","3":"Support for multiple hosts\/databases. Support for show:db.","package":"szw-vim-dict-1.1.0.zip","4":"szw-vim-dict-1.1.0.zip","src_id":"18434","5":"18434","creation_date":"1345410367","6":"1345410367"},{"0":"4180","vim_version":"7.0","1":"7.0","script_version":"1.0.0","2":"1.0.0","version_comment":"Initial upload","3":"Initial upload","package":"szw-vim-dict-1.0.0.zip","4":"szw-vim-dict-1.0.0.zip","src_id":"18429","5":"18429","creation_date":"1345353771","6":"1345353771"}]},"4179":{"script_id":"4179","0":"4179","script_name":"X Marks the Spot","1":"X Marks the Spot","script_type":"utility","2":"utility","summary":"Easy mappings for creating and navigating through lower-case marks","3":"Easy mappings for creating and navigating through lower-case marks","description":"Visit the official repository for the latest version. http:\/\/github.com\/john2x\/x-marks-the-spot.vim\r\n\r\nVim marks for pirates. Arr!\r\n\r\nEasy mappings for creating and navigating through lower-case marks.\r\n\r\nBasic usage\r\n-----------\r\nDefault mappings:\r\n\r\n- `<leader>x`: Add mark `x` in the current cursor location, where `x` is the next\r\navailable mark.\r\n- `<leader>X`: Delete all marks at the current line.\r\n- `<BS>`: Go to the previous closest mark (mode 1) or the previously\r\nassigned mark (mode 2).\r\n- `<S-BS>`: Go to next closest mark (mode 1) or the next assigned mark\r\n(mode 2).\r\n\r\nTo override them, add the following to your vimrc:\r\n\r\n\tnmap <unique> <leader>x <Plug>XmarksthespotAddmark\r\n\tnmap <unique> <leader>X <Plug>XmarksthespotRemovemarks\r\n\tnmap <unique> <S-BS> <Plug>XmarksthespotNextmark\r\n\tnmap <unique> <BS> <Plug>XmarksthespotPreviousmark\r\n\r\nInstall\r\n-------\r\n\r\nJust place in your `.vim\/plugins` directory. Pathogen ready.\r\n\r\nOptions\r\n-------\r\n\r\nTo set options, set their values in your vimrc.\r\n\r\n### X\\_MARKS\\_NAVIGATION\\_MODE\r\n\r\nChoose between two mark navigation modes. \r\n\r\n- `let g:X_MARKS_NAVIGATION_MODE = 1` - (default) Move through marks based on position.\r\nBasically just calls `['` and `]'` for moving backward and forward, respectively.\r\n\r\n- `let g:X_MARKS_NAVIGATION_MODE = 2` - Move through marks based on the order of\r\ntheir assignment, regardless of their positions.\r\n\r\n### X\\_MARKS\\_RESET\\_MARKS\\_ON\\_BUF\\_READ\r\n\r\n- `let g:X_MARKS_RESET_MARKS_ON_BUF_READ = 0` - (default) Don't clear all buffer\r\nmarks when initializing X Marks The Spot for the current buffer.\r\n\r\n- `let g:X_MARKS_RESET_MARKS_ON_BUF_READ = 1` - Clear all buffer\r\nmarks when initializing X Marks The Spot for the current buffer.\r\n\r\n### X\\_MARKS\\_SHOW\\_SIGNS\r\n\r\n(Experimental)\r\n\r\n- `let g:X_MARKS_SHOW_SIGNS = 0` - Don't show signs for mark location\r\n\r\n- `let g:X_MARKS_SHOW_SIGNS = 1` - (default) Show signs for mark location\r\n\r\nTo Do List\r\n----------\r\n\r\n1. Allow mode 1 to \"cycle\" to the first\/last mark when at the last\/first mark.\r\n2. Add an option to limit one mark per line. (DONE)\r\n3. Don't store marks in a dict anymore.\r\n4. Show signs for marks.\r\n\r\nLicense\r\n-------\r\n\r\nCopyright (c) John Louis Del Rosario. Distributed under the same terms as Vim\r\nitself. See `:help license`.","4":"Visit the official repository for the latest version. http:\/\/github.com\/john2x\/x-marks-the-spot.vim\r\n\r\nVim marks for pirates. Arr!\r\n\r\nEasy mappings for creating and navigating through lower-case marks.\r\n\r\nBasic usage\r\n-----------\r\nDefault mappings:\r\n\r\n- `<leader>x`: Add mark `x` in the current cursor location, where `x` is the next\r\navailable mark.\r\n- `<leader>X`: Delete all marks at the current line.\r\n- `<BS>`: Go to the previous closest mark (mode 1) or the previously\r\nassigned mark (mode 2).\r\n- `<S-BS>`: Go to next closest mark (mode 1) or the next assigned mark\r\n(mode 2).\r\n\r\nTo override them, add the following to your vimrc:\r\n\r\n\tnmap <unique> <leader>x <Plug>XmarksthespotAddmark\r\n\tnmap <unique> <leader>X <Plug>XmarksthespotRemovemarks\r\n\tnmap <unique> <S-BS> <Plug>XmarksthespotNextmark\r\n\tnmap <unique> <BS> <Plug>XmarksthespotPreviousmark\r\n\r\nInstall\r\n-------\r\n\r\nJust place in your `.vim\/plugins` directory. Pathogen ready.\r\n\r\nOptions\r\n-------\r\n\r\nTo set options, set their values in your vimrc.\r\n\r\n### X\\_MARKS\\_NAVIGATION\\_MODE\r\n\r\nChoose between two mark navigation modes. \r\n\r\n- `let g:X_MARKS_NAVIGATION_MODE = 1` - (default) Move through marks based on position.\r\nBasically just calls `['` and `]'` for moving backward and forward, respectively.\r\n\r\n- `let g:X_MARKS_NAVIGATION_MODE = 2` - Move through marks based on the order of\r\ntheir assignment, regardless of their positions.\r\n\r\n### X\\_MARKS\\_RESET\\_MARKS\\_ON\\_BUF\\_READ\r\n\r\n- `let g:X_MARKS_RESET_MARKS_ON_BUF_READ = 0` - (default) Don't clear all buffer\r\nmarks when initializing X Marks The Spot for the current buffer.\r\n\r\n- `let g:X_MARKS_RESET_MARKS_ON_BUF_READ = 1` - Clear all buffer\r\nmarks when initializing X Marks The Spot for the current buffer.\r\n\r\n### X\\_MARKS\\_SHOW\\_SIGNS\r\n\r\n(Experimental)\r\n\r\n- `let g:X_MARKS_SHOW_SIGNS = 0` - Don't show signs for mark location\r\n\r\n- `let g:X_MARKS_SHOW_SIGNS = 1` - (default) Show signs for mark location\r\n\r\nTo Do List\r\n----------\r\n\r\n1. Allow mode 1 to \"cycle\" to the first\/last mark when at the last\/first mark.\r\n2. Add an option to limit one mark per line. (DONE)\r\n3. Don't store marks in a dict anymore.\r\n4. Show signs for marks.\r\n\r\nLicense\r\n-------\r\n\r\nCopyright (c) John Louis Del Rosario. Distributed under the same terms as Vim\r\nitself. See `:help license`.","install_details":"Place in .vim\/plugins directory. Pathogen ready.","5":"Place in .vim\/plugins directory. Pathogen ready.","first_name":"John Louis","6":"John Louis","last_name":"del Rosario","7":"del Rosario","releases":[{"0":"4179","vim_version":"7.3","1":"7.3","script_version":"0.0.1","2":"0.0.1","version_comment":"Initial upload","3":"Initial upload","package":"x-marks-the-spot.zip","4":"x-marks-the-spot.zip","src_id":"18428","5":"18428","creation_date":"1345353650","6":"1345353650"}]},"4178":{"script_id":"4178","0":"4178","script_name":"CursorLineCurrentWindow","1":"CursorLineCurrentWindow","script_type":"utility","2":"utility","summary":"Only highlight the screen line of the cursor in the currently active window.","3":"Only highlight the screen line of the cursor in the currently active window.","description":"DESCRIPTION\r\nThe 'cursorline' setting makes it easy to locate the cursor position. However,\r\nwhen there are split windows, each one shows its cursor line, and the only\r\nindication of the currently active window is the different 'statusline'\r\nhighlighting (with hl-StatusLine vs. hl-StatusLineNC).\r\n\r\nThis plugin avoids the clutter of multiple highlighted screen lines with split\r\nwindows by disabling the 'cursorline', 'cursorcolumn', and\/or 'wincolor'\r\nsettings for all but the current window. Unlike a simplistic solution with a\r\nfew autocmds, this plugin still allows for exceptions like disabling the\r\ncursorline for a particular window or making it permanent for (another)\r\nwindow.\r\n\r\nSEE ALSO\r\n- The RelativeNumberCurrentWindow plugin (vimscript #4461) enables the\r\n  'relativenumber' setting only for the current window.\r\n\r\nRELATED WORKS\r\nThe basic idea is outlined in the Vim Tips Wiki:\r\n    http:\/\/vim.wikia.com\/wiki\/Highlight_current_line\r\n- cursorline_current.vim (vimscript #5740) enables cursorline only in the\r\n  current window and when not in insert mode.\r\n\r\nUSAGE\r\nGlobally enable 'cursorline', 'cursorcolumn' and\/or 'wincolor' in your\r\nvimrc; e.g.\r\n    :set cursorline cursorcolumn\r\nAfter sourcing this plugin, the option(s) will only be active for the current\r\nwindow. So with multiple split windows, only one of them, the one where the\r\ncursor is in, will have 'cursorline' and 'cursorcolumn' enabled.\r\n\r\nDisable cursorline for the current window via:\r\n    :setlocal nocursorline\r\nThis will persist even after moving away and back to the window.\r\n\r\nDisable cursorline globally via:\r\n    :set nocursorline\r\nAs soon as you enter a window, its line highlighting will vanish.\r\n\r\nFor some kind of files it is helpful to keep the line highlighting active,\r\ne.g. to serve as a ruler. You can keep the highlighting for a particular\r\nwindow by setting a window-local variable:\r\n    :let w:persistent_cursorline = 1","4":"DESCRIPTION\r\nThe 'cursorline' setting makes it easy to locate the cursor position. However,\r\nwhen there are split windows, each one shows its cursor line, and the only\r\nindication of the currently active window is the different 'statusline'\r\nhighlighting (with hl-StatusLine vs. hl-StatusLineNC).\r\n\r\nThis plugin avoids the clutter of multiple highlighted screen lines with split\r\nwindows by disabling the 'cursorline', 'cursorcolumn', and\/or 'wincolor'\r\nsettings for all but the current window. Unlike a simplistic solution with a\r\nfew autocmds, this plugin still allows for exceptions like disabling the\r\ncursorline for a particular window or making it permanent for (another)\r\nwindow.\r\n\r\nSEE ALSO\r\n- The RelativeNumberCurrentWindow plugin (vimscript #4461) enables the\r\n  'relativenumber' setting only for the current window.\r\n\r\nRELATED WORKS\r\nThe basic idea is outlined in the Vim Tips Wiki:\r\n    http:\/\/vim.wikia.com\/wiki\/Highlight_current_line\r\n- cursorline_current.vim (vimscript #5740) enables cursorline only in the\r\n  current window and when not in insert mode.\r\n\r\nUSAGE\r\nGlobally enable 'cursorline', 'cursorcolumn' and\/or 'wincolor' in your\r\nvimrc; e.g.\r\n    :set cursorline cursorcolumn\r\nAfter sourcing this plugin, the option(s) will only be active for the current\r\nwindow. So with multiple split windows, only one of them, the one where the\r\ncursor is in, will have 'cursorline' and 'cursorcolumn' enabled.\r\n\r\nDisable cursorline for the current window via:\r\n    :setlocal nocursorline\r\nThis will persist even after moving away and back to the window.\r\n\r\nDisable cursorline globally via:\r\n    :set nocursorline\r\nAs soon as you enter a window, its line highlighting will vanish.\r\n\r\nFor some kind of files it is helpful to keep the line highlighting active,\r\ne.g. to serve as a ruler. You can keep the highlighting for a particular\r\nwindow by setting a window-local variable:\r\n    :let w:persistent_cursorline = 1","install_details":"INSTALLATION\r\nThe code is hosted in a Git repo at\r\n    https:\/\/github.com\/inkarkat\/vim-CursorLineCurrentWindow\r\nYou can use your favorite plugin manager, or \"git clone\" into a directory used\r\nfor Vim packages. Releases are on the \"stable\" branch, the latest unstable\r\ndevelopment snapshot on \"master\".\r\n\r\nThis script is also packaged as a vimball. If you have the \"gunzip\"\r\ndecompressor in your PATH, simply edit the *.vmb.gz package in Vim; otherwise,\r\ndecompress the archive first, e.g. using WinZip. Inside Vim, install by\r\nsourcing the vimball or via the :UseVimball command.\r\n    vim CursorLineCurrentWindow*.vmb.gz\r\n    :so %\r\nTo uninstall, use the :RmVimball command.\r\n\r\nDEPENDENCIES\r\n- Requires Vim 7.0 or higher.\r\n\r\nCONFIGURATION\r\nFor a permanent configuration, put the following commands into your vimrc:\r\n\r\nBy default, the plugin will localize any of 'cursorline', 'cursorcolumn', or\r\n'wincolor' options, provided they are set during startup. To cover options\r\nthat may be set on demand or to drop a set option, the List of option names\r\ncan be overridden:\r\n    let g:CursorLineCurrentWindow_OptionNames = ['cursorline']","5":"INSTALLATION\r\nThe code is hosted in a Git repo at\r\n    https:\/\/github.com\/inkarkat\/vim-CursorLineCurrentWindow\r\nYou can use your favorite plugin manager, or \"git clone\" into a directory used\r\nfor Vim packages. Releases are on the \"stable\" branch, the latest unstable\r\ndevelopment snapshot on \"master\".\r\n\r\nThis script is also packaged as a vimball. If you have the \"gunzip\"\r\ndecompressor in your PATH, simply edit the *.vmb.gz package in Vim; otherwise,\r\ndecompress the archive first, e.g. using WinZip. Inside Vim, install by\r\nsourcing the vimball or via the :UseVimball command.\r\n    vim CursorLineCurrentWindow*.vmb.gz\r\n    :so %\r\nTo uninstall, use the :RmVimball command.\r\n\r\nDEPENDENCIES\r\n- Requires Vim 7.0 or higher.\r\n\r\nCONFIGURATION\r\nFor a permanent configuration, put the following commands into your vimrc:\r\n\r\nBy default, the plugin will localize any of 'cursorline', 'cursorcolumn', or\r\n'wincolor' options, provided they are set during startup. To cover options\r\nthat may be set on demand or to drop a set option, the List of option names\r\ncan be overridden:\r\n    let g:CursorLineCurrentWindow_OptionNames = ['cursorline']","first_name":"Ingo","6":"Ingo","last_name":"Karkat","7":"Karkat","releases":[{"0":"4178","vim_version":"7.0","1":"7.0","script_version":"2.00","2":"2.00","version_comment":"- ENH: Generalize to also handle 'cursorcolumn' and non-flag window options like (new in Vim 8.1.1391) 'wincolor'.","3":"- ENH: Generalize to also handle 'cursorcolumn' and non-flag window options like (new in Vim 8.1.1391) 'wincolor'.","package":"CursorLineCurrentWindow-2.00.vmb.gz","4":"CursorLineCurrentWindow-2.00.vmb.gz","src_id":"26971","5":"26971","creation_date":"1581309712","6":"1581309712"},{"0":"4178","vim_version":"7.0","1":"7.0","script_version":"1.00","2":"1.00","version_comment":"Initial upload","3":"Initial upload","package":"CursorLineCurrentWindow.vba.gz","4":"CursorLineCurrentWindow.vba.gz","src_id":"18427","5":"18427","creation_date":"1345321164","6":"1345321164"}]},"4177":{"script_id":"4177","0":"4177","script_name":"undotree.vim","1":"undotree.vim","script_type":"utility","2":"utility","summary":"Display your undo history in a graph.","3":"Display your undo history in a graph.","description":"Find the latest version in github:\r\nhttps:\/\/github.com\/mbbill\/undotree\r\n\r\nVim 7.0 added a new feature named **Undo branches**. Basically it's a kind of ability to go back to the text after any change, even if they were undone. Vim stores undo history in a tree which you can browse and manipulate through a bunch of commands. But that was not enough straightforward and a bit hard to use. You may use `:help new-undo-branches` or `:help undo-tree` to get more detailed help.  \r\nNow this plug-in will free you from those commands and bring back the power of undo tree.\r\nThis script is written purely in Vim script with no additional dependency.\r\n\r\nScreenshot\r\nhttps:\/\/sites.google.com\/site\/mbbill\/undotree_new.png\r\n\r\nUsage\r\n 1. Use `:UndotreeToggle` to toggle the undo-tree panel. You may want to map this command to whatever hotkey by adding the following line to your vimrc, take F5 for example.\r\n\r\n    nnoremap    <F5>    :UndotreeToggle<cr>\r\n\r\nFor more details, refer to the github page or README.md within this package.\r\n\r\nSubmit Issues\r\nhttps:\/\/github.com\/mbbill\/undotree\/issues","4":"Find the latest version in github:\r\nhttps:\/\/github.com\/mbbill\/undotree\r\n\r\nVim 7.0 added a new feature named **Undo branches**. Basically it's a kind of ability to go back to the text after any change, even if they were undone. Vim stores undo history in a tree which you can browse and manipulate through a bunch of commands. But that was not enough straightforward and a bit hard to use. You may use `:help new-undo-branches` or `:help undo-tree` to get more detailed help.  \r\nNow this plug-in will free you from those commands and bring back the power of undo tree.\r\nThis script is written purely in Vim script with no additional dependency.\r\n\r\nScreenshot\r\nhttps:\/\/sites.google.com\/site\/mbbill\/undotree_new.png\r\n\r\nUsage\r\n 1. Use `:UndotreeToggle` to toggle the undo-tree panel. You may want to map this command to whatever hotkey by adding the following line to your vimrc, take F5 for example.\r\n\r\n    nnoremap    <F5>    :UndotreeToggle<cr>\r\n\r\nFor more details, refer to the github page or README.md within this package.\r\n\r\nSubmit Issues\r\nhttps:\/\/github.com\/mbbill\/undotree\/issues","install_details":"Unpack all scripts into *plugin* directory and that's all. There is no additional dependency.","5":"Unpack all scripts into *plugin* directory and that's all. There is no additional dependency.","first_name":"Ming","6":"Ming","last_name":"Bai","7":"Bai","releases":[{"0":"4177","vim_version":"7.3","1":"7.3","script_version":"4.3","2":"4.3","version_comment":"Several fixes and enhancements.","3":"Several fixes and enhancements.","package":"undotree-rel_4.3.zip","4":"undotree-rel_4.3.zip","src_id":"19541","5":"19541","creation_date":"1361184055","6":"1361184055"},{"0":"4177","vim_version":"7.0","1":"7.0","script_version":"4.2","2":"4.2","version_comment":"Fixed some small issue.","3":"Fixed some small issue.","package":"undotree-rel_4.2.zip","4":"undotree-rel_4.2.zip","src_id":"19023","5":"19023","creation_date":"1353729791","6":"1353729791"},{"0":"4177","vim_version":"7.3","1":"7.3","script_version":"4.1","2":"4.1","version_comment":"Enhanced tree style. Multi-window switching support.","3":"Enhanced tree style. Multi-window switching support.","package":"mbbill-undotree-rel_4.1-0-gb05bb19.zip","4":"mbbill-undotree-rel_4.1-0-gb05bb19.zip","src_id":"18552","5":"18552","creation_date":"1346853342","6":"1346853342"},{"0":"4177","vim_version":"7.3","1":"7.3","script_version":"4.0","2":"4.0","version_comment":"Live updated highlight for changed text. Screenshot: http:\/\/files.myopera.com\/mbbill\/files\/undotree.png\r\nCustomizable key mappings.\r\nFixed some minor bugs.\r\n","3":"Live updated highlight for changed text. Screenshot: http:\/\/files.myopera.com\/mbbill\/files\/undotree.png\r\nCustomizable key mappings.\r\nFixed some minor bugs.\r\n","package":"mbbill-undotree-rel_4.0-0-gfb621a8.zip","4":"mbbill-undotree-rel_4.0-0-gfb621a8.zip","src_id":"18511","5":"18511","creation_date":"1346309809","6":"1346309809"},{"0":"4177","vim_version":"7.0","1":"7.0","script_version":"3.1","2":"3.1","version_comment":"Added saved status, relative timestamp and ability of clear undo history.","3":"Added saved status, relative timestamp and ability of clear undo history.","package":"mbbill-undotree-rel_3.1-0-gf2bc4af.zip","4":"mbbill-undotree-rel_3.1-0-gf2bc4af.zip","src_id":"18490","5":"18490","creation_date":"1345894096","6":"1345894096"},{"0":"4177","vim_version":"7.0","1":"7.0","script_version":"3.0","2":"3.0","version_comment":"Add diff panel. Performance improvement.","3":"Add diff panel. Performance improvement.","package":"mbbill-undotree-rel_3.0-0-g58ade90.zip","4":"mbbill-undotree-rel_3.0-0-g58ade90.zip","src_id":"18475","5":"18475","creation_date":"1345777068","6":"1345777068"},{"0":"4177","vim_version":"7.0","1":"7.0","script_version":"2.2","2":"2.2","version_comment":"Stable version.","3":"Stable version.","package":"mbbill-undotree-rel_2.2-0-gc8b7adb.zip","4":"mbbill-undotree-rel_2.2-0-gc8b7adb.zip","src_id":"18447","5":"18447","creation_date":"1345514382","6":"1345514382"},{"0":"4177","vim_version":"7.0","1":"7.0","script_version":"2.1","2":"2.1","version_comment":"Fixed some annoying issues.","3":"Fixed some annoying issues.","package":"mbbill-undotree-rel_2.1-0-g2fecc10.zip","4":"mbbill-undotree-rel_2.1-0-g2fecc10.zip","src_id":"18436","5":"18436","creation_date":"1345449892","6":"1345449892"},{"0":"4177","vim_version":"7.0","1":"7.0","script_version":"2","2":"2","version_comment":"Added some new features: hotkey support. handle undo levels, auto refresh, and so on.","3":"Added some new features: hotkey support. handle undo levels, auto refresh, and so on.","package":"mbbill-undotree-rel_2-0-g9121bda.zip","4":"mbbill-undotree-rel_2-0-g9121bda.zip","src_id":"18432","5":"18432","creation_date":"1345375583","6":"1345375583"},{"0":"4177","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"mbbill-undotree-rel_1-0-g062df4e.zip","4":"mbbill-undotree-rel_1-0-g062df4e.zip","src_id":"18424","5":"18424","creation_date":"1345302774","6":"1345302774"}]},"4176":{"script_id":"4176","0":"4176","script_name":"Rainbow Parentheses Improved","1":"Rainbow Parentheses Improved","script_type":"utility","2":"utility","summary":"shorter code, no level limit, smooth and fast, powerful configuration.","3":"shorter code, no level limit, smooth and fast, powerful configuration.","description":"More details in Github: http:\/\/github.com\/luochen1990\/rainbow\r\n\r\n(这里有中文版: http:\/\/github.com\/luochen1990\/rainbow\/blob\/master\/README_zh.md)\r\n\r\nAny problem, create a new issue here: http:\/\/github.com\/luochen1990\/rainbow\/issues\r\n\r\n-------------------------------------------------------------------------------------------------------- \r\n\r\n### What is improved ? \r\n\r\n- smoother and faster. (linear time complexity) \r\n- the code is shorter and easier to be read now. (shorter than 100 lines) \r\n- no limit of parentheses levels. \r\n- separately edit guifgs and ctermfgs (the colors used to highlight) \r\n- now you can design your own parentheses  such as 'begin' and 'end' . (you can also design  what kinds of parentheses to use for different filetypes. ) \r\n- you can also configure seprately for different type of files. \r\n- now you can even decide to let some operators (like + - * \/ , ==) hilighted with the parentheses together.\r\n- now json style configuration used, more understandable and more readable, easily for advanced configuration.\r\n- the last , but not the least , the chinese statement is added as you see. \r\n\r\n### scripts I referenced: \r\n- http:\/\/www.vim.org\/scripts\/script.php?script_id=1561\r\n- http:\/\/www.vim.org\/scripts\/script.php?script_id=3772\r\n\r\n**Rate this script if you like it, and i'll appreciate it and improve this plugin for you because of your support !  just choose `Life Changing` and click `rate` :) **\r\n","4":"More details in Github: http:\/\/github.com\/luochen1990\/rainbow\r\n\r\n(这里有中文版: http:\/\/github.com\/luochen1990\/rainbow\/blob\/master\/README_zh.md)\r\n\r\nAny problem, create a new issue here: http:\/\/github.com\/luochen1990\/rainbow\/issues\r\n\r\n-------------------------------------------------------------------------------------------------------- \r\n\r\n### What is improved ? \r\n\r\n- smoother and faster. (linear time complexity) \r\n- the code is shorter and easier to be read now. (shorter than 100 lines) \r\n- no limit of parentheses levels. \r\n- separately edit guifgs and ctermfgs (the colors used to highlight) \r\n- now you can design your own parentheses  such as 'begin' and 'end' . (you can also design  what kinds of parentheses to use for different filetypes. ) \r\n- you can also configure seprately for different type of files. \r\n- now you can even decide to let some operators (like + - * \/ , ==) hilighted with the parentheses together.\r\n- now json style configuration used, more understandable and more readable, easily for advanced configuration.\r\n- the last , but not the least , the chinese statement is added as you see. \r\n\r\n### scripts I referenced: \r\n- http:\/\/www.vim.org\/scripts\/script.php?script_id=1561\r\n- http:\/\/www.vim.org\/scripts\/script.php?script_id=3772\r\n\r\n**Rate this script if you like it, and i'll appreciate it and improve this plugin for you because of your support !  just choose `Life Changing` and click `rate` :) **\r\n","install_details":"go to Github http:\/\/github.com\/luochen1990\/rainbow for more details","5":"go to Github http:\/\/github.com\/luochen1990\/rainbow for more details","first_name":"luo","6":"luo","last_name":"chen","7":"chen","releases":[{"0":"4176","vim_version":"7.3","1":"7.3","script_version":"3.4.0","2":"3.4.0","version_comment":"new: Rainbow Syntax Cluster\r\ncompatibility: work with NeoVim\r\n","3":"new: Rainbow Syntax Cluster\r\ncompatibility: work with NeoVim\r\n","package":"rainbow.vim","4":"rainbow.vim","src_id":"23739","5":"23739","creation_date":"1447865459","6":"1447865459"},{"0":"4176","vim_version":"7.3","1":"7.3","script_version":"3.3.1","2":"3.3.1","version_comment":"spell checking and folding problems fixed.","3":"spell checking and folding problems fixed.","package":"rainbow.vim","4":"rainbow.vim","src_id":"22662","5":"22662","creation_date":"1417509847","6":"1417509847"},{"0":"4176","vim_version":"7.3","1":"7.3","script_version":"3.3.0","2":"3.3.0","version_comment":"configuration format modified, option containedin moved into parentheses; multi sub-region supported; configuration for php updated; configuration for css added.","3":"configuration format modified, option containedin moved into parentheses; multi sub-region supported; configuration for php updated; configuration for css added.","package":"rainbow.vim","4":"rainbow.vim","src_id":"22310","5":"22310","creation_date":"1407577970","6":"1407577970"},{"0":"4176","vim_version":"7.3","1":"7.3","script_version":"3.2.3","2":"3.2.3","version_comment":"compatibility with other syntax plugins improved.","3":"compatibility with other syntax plugins improved.","package":"rainbow.vim","4":"rainbow.vim","src_id":"22291","5":"22291","creation_date":"1407326498","6":"1407326498"},{"0":"4176","vim_version":"7.3","1":"7.3","script_version":"3.2.2","2":"3.2.2","version_comment":"code reduced; configuration method for parentheses extended.","3":"code reduced; configuration method for parentheses extended.","package":"rainbow.vim","4":"rainbow.vim","src_id":"22279","5":"22279","creation_date":"1406789566","6":"1406789566"},{"0":"4176","vim_version":"7.3","1":"7.3","script_version":"3.2.1","2":"3.2.1","version_comment":"default configuration for html\/xhtml\/xml updated, tag matchs more accurate now.","3":"default configuration for html\/xhtml\/xml updated, tag matchs more accurate now.","package":"rainbow.vim","4":"rainbow.vim","src_id":"22167","5":"22167","creation_date":"1404806466","6":"1404806466"},{"0":"4176","vim_version":"7.3","1":"7.3","script_version":"3.2.0","2":"3.2.0","version_comment":"default configuration reduced; html self-closing tags properly treated.","3":"default configuration reduced; html self-closing tags properly treated.","package":"rainbow.vim","4":"rainbow.vim","src_id":"22148","5":"22148","creation_date":"1404718537","6":"1404718537"},{"0":"4176","vim_version":"7.3","1":"7.3","script_version":"3.1.3","2":"3.1.3","version_comment":"fixed: highlighting missing when switching colorsheme.","3":"fixed: highlighting missing when switching colorsheme.","package":"rainbow.vim","4":"rainbow.vim","src_id":"21844","5":"21844","creation_date":"1398847143","6":"1398847143"},{"0":"4176","vim_version":"7.3","1":"7.3","script_version":"3.1.1","2":"3.1.1","version_comment":"default configuration updated for more special filetypes","3":"default configuration updated for more special filetypes","package":"rainbow.vim","4":"rainbow.vim","src_id":"21279","5":"21279","creation_date":"1388977159","6":"1388977159"},{"0":"4176","vim_version":"7.3","1":"7.3","script_version":"3.1","2":"3.1","version_comment":"syntax fold supported; separately configuration easier.","3":"syntax fold supported; separately configuration easier.","package":"rainbow.vim","4":"rainbow.vim","src_id":"21270","5":"21270","creation_date":"1388720719","6":"1388720719"},{"0":"4176","vim_version":"7.3","1":"7.3","script_version":"3.0","2":"3.0","version_comment":"json style configuration supported.","3":"json style configuration supported.","package":"rainbow.vim","4":"rainbow.vim","src_id":"21267","5":"21267","creation_date":"1388586175","6":"1388586175"},{"0":"4176","vim_version":"7.3","1":"7.3","script_version":"2.51","2":"2.51","version_comment":"* added a shorter command :Rainbow instead of :RainbowToggle to toggle it\r\n* comment updated","3":"* added a shorter command :Rainbow instead of :RainbowToggle to toggle it\r\n* comment updated","package":"rainbow.vim","4":"rainbow.vim","src_id":"18989","5":"18989","creation_date":"1353222085","6":"1353222085"},{"0":"4176","vim_version":"7.3","1":"7.3","script_version":"2.5","2":"2.5","version_comment":"*!! now you can choose to add operators which will be hilighted with the parentheses they are contained.\r\n(现在你可以允许一些符号跟着包含它们的括号一起高亮)\r\n*you can also config it separately for each type of file.\r\n(你也可以根据文件类型分别设置哪些符号将同时被高亮)","3":"*!! now you can choose to add operators which will be hilighted with the parentheses they are contained.\r\n(现在你可以允许一些符号跟着包含它们的括号一起高亮)\r\n*you can also config it separately for each type of file.\r\n(你也可以根据文件类型分别设置哪些符号将同时被高亮)","package":"rainbow.vim","4":"rainbow.vim","src_id":"18964","5":"18964","creation_date":"1352540038","6":"1352540038"},{"0":"4176","vim_version":"7.3","1":"7.3","script_version":"2.41","2":"2.41","version_comment":"*updated the advanced configuration demo of 2.4 \r\n*a little change of code","3":"*updated the advanced configuration demo of 2.4 \r\n*a little change of code","package":"rainbow.vim","4":"rainbow.vim","src_id":"18907","5":"18907","creation_date":"1351359800","6":"1351359800"},{"0":"4176","vim_version":"7.3","1":"7.3","script_version":"2.4","2":"2.4","version_comment":"*higher priority of syntax definition.\r\n*now you can define the parentheses used for each type of file separately.\r\n*script details about configuration updated.","3":"*higher priority of syntax definition.\r\n*now you can define the parentheses used for each type of file separately.\r\n*script details about configuration updated.","package":"rainbow.vim","4":"rainbow.vim","src_id":"18865","5":"18865","creation_date":"1350993414","6":"1350993414"},{"0":"4176","vim_version":"7.3","1":"7.3","script_version":"2.3","2":"2.3","version_comment":"* you can use global variables to set this plugin now . which makes it easier to make your vimrc portable . (read the comment  in the rainbow.vim to know more)","3":"* you can use global variables to set this plugin now . which makes it easier to make your vimrc portable . (read the comment  in the rainbow.vim to know more)","package":"rainbow.vim","4":"rainbow.vim","src_id":"18574","5":"18574","creation_date":"1347198596","6":"1347198596"},{"0":"4176","vim_version":"7.3","1":"7.3","script_version":"2.2","2":"2.2","version_comment":"*bug fixed: now your own syntax highlighting won't be covered .\r\n*changed colors: now 5 colors is reserved .","3":"*bug fixed: now your own syntax highlighting won't be covered .\r\n*changed colors: now 5 colors is reserved .","package":"rainbow.vim","4":"rainbow.vim","src_id":"18539","5":"18539","creation_date":"1346686028","6":"1346686028"},{"0":"4176","vim_version":"7.3","1":"7.3","script_version":"2.1","2":"2.1","version_comment":"* now you needn't to set the max levels of parentheses. It can automatically use the colors circularly. (and the time complexity is linear dependent on the number of colors)","3":"* now you needn't to set the max levels of parentheses. It can automatically use the colors circularly. (and the time complexity is linear dependent on the number of colors)","package":"rainbow.vim","4":"rainbow.vim","src_id":"18455","5":"18455","creation_date":"1345654410","6":"1345654410"},{"0":"4176","vim_version":"7.3","1":"7.3","script_version":"2.01","2":"2.01","version_comment":"*fixed the bug of RPToggle of version 2.0 , now called RainbowToggle","3":"*fixed the bug of RPToggle of version 2.0 , now called RainbowToggle","package":"rainbow_parentheses.vim","4":"rainbow_parentheses.vim","src_id":"18452","5":"18452","creation_date":"1345626696","6":"1345626696"},{"0":"4176","vim_version":"7.3","1":"7.3","script_version":"2.0","2":"2.0","version_comment":"*smoother and can be deeper.\r\n*now you can design your own parentheses like 'begin..end'.\r\n*separately edit guifg and ctermfg now, which makes config easier\r\n*shorter code and simpler document.\r\n*added a command : RPToggle","3":"*smoother and can be deeper.\r\n*now you can design your own parentheses like 'begin..end'.\r\n*separately edit guifg and ctermfg now, which makes config easier\r\n*shorter code and simpler document.\r\n*added a command : RPToggle","package":"rainbow_parentheses.vim","4":"rainbow_parentheses.vim","src_id":"18449","5":"18449","creation_date":"1345591397","6":"1345591397"},{"0":"4176","vim_version":"7.3","1":"7.3","script_version":"1.01","2":"1.01","version_comment":"1. no global variable used. (不再使用全局变量进行设置）\r\n2. fixed the bug of treating '<' and '>' as brackets even don't need to highlighting them.（修正关于大于号、小于号的bug）\r\n3. simple configuration.（现在设置更简单）\r\n4. completed document.（现在有完整的文档帮助进行更详细设置）","3":"1. no global variable used. (不再使用全局变量进行设置）\r\n2. fixed the bug of treating '<' and '>' as brackets even don't need to highlighting them.（修正关于大于号、小于号的bug）\r\n3. simple configuration.（现在设置更简单）\r\n4. completed document.（现在有完整的文档帮助进行更详细设置）","package":"rainbow_parentheses_improved.zip","4":"rainbow_parentheses_improved.zip","src_id":"18422","5":"18422","creation_date":"1345213782","6":"1345213782"}]},"4175":{"script_id":"4175","0":"4175","script_name":"rslate","1":"rslate","script_type":"color scheme","2":"color scheme","summary":"a modified slate theme for R","3":"a modified slate theme for R","description":"A modified slate theme R intended for use with vimscript #2628. \r\n\r\nScreenshot: http:\/\/pds.ceu.hu\/sites\/default\/files\/imagefield_files\/page\/node-27767\/more_images\/rslate.png","4":"A modified slate theme R intended for use with vimscript #2628. \r\n\r\nScreenshot: http:\/\/pds.ceu.hu\/sites\/default\/files\/imagefield_files\/page\/node-27767\/more_images\/rslate.png","install_details":"","5":"","first_name":"Juraj","6":"Juraj","last_name":"Medzihorsky","7":"Medzihorsky","releases":[{"0":"4175","vim_version":"7.0","1":"7.0","script_version":"21-01-12","2":"21-01-12","version_comment":"Initial upload","3":"Initial upload","package":"rslate.vim","4":"rslate.vim","src_id":"18419","5":"18419","creation_date":"1345195411","6":"1345195411"}]},"4174":{"script_id":"4174","0":"4174","script_name":"rgbr","1":"rgbr","script_type":"color scheme","2":"color scheme","summary":"a simple color scheme for R","3":"a simple color scheme for R","description":"A simple dark-on-light scheme with black, red, green, and blue for R intended for use with vimscript #2628.\r\n\r\nScreenshot: http:\/\/pds.ceu.hu\/sites\/default\/files\/imagefield_files\/page\/node-27767\/more_images\/rgbr.png","4":"A simple dark-on-light scheme with black, red, green, and blue for R intended for use with vimscript #2628.\r\n\r\nScreenshot: http:\/\/pds.ceu.hu\/sites\/default\/files\/imagefield_files\/page\/node-27767\/more_images\/rgbr.png","install_details":"","5":"","first_name":"Juraj","6":"Juraj","last_name":"Medzihorsky","7":"Medzihorsky","releases":[{"0":"4174","vim_version":"7.0","1":"7.0","script_version":"17-08-12","2":"17-08-12","version_comment":"Initial upload","3":"Initial upload","package":"rgbr.vim","4":"rgbr.vim","src_id":"18418","5":"18418","creation_date":"1345194218","6":"1345194218"}]},"4173":{"script_id":"4173","0":"4173","script_name":"GrepCommands","1":"GrepCommands","script_type":"utility","2":"utility","summary":"Perform :vimgrep over arguments, buffers, windows.","3":"Perform :vimgrep over arguments, buffers, windows.","description":"DESCRIPTION\r\nThis plugin defines variants of the built-in :vimgrep command which target\r\nall arguments, listed buffers, windows in the current tab page or all tab\r\npages for its search. Additionally, the search defaults to the last search\r\npattern, so using these commands is often much faster than building the\r\nequivalent search with :vimgrep.\r\n\r\nSEE ALSO\r\n- The GrepHere plugin (vimscript #4191) provides a :GrepHere command that\r\n  covers only the current buffer.\r\n\r\nRELATED WORKS\r\n- This is a modern re-implementation of the similar commands defined by\r\n  greputils.vim (vimscript #1062), which hasn't been updated since 2005.\r\n- brep (vimscript #3653) can grep buffers (also unlisted with [!]) and show\r\n  them in the quickfix list.\r\n- greplace (vimscript #1813) can search buffers and arguments; it shows the\r\n  matches in a special replace buffer that can be edited and incorporated into\r\n  the original files.\r\n\r\nUSAGE\r\n:ArgGrep[Add][!] [{pattern}]\r\n:ArgGrep[Add][!] \/{pattern}\/[g][j]\r\n                        Search for {pattern} (or last search pattern if\r\n                        omitted) in all files from the argument-list and set\r\n                        the error list to the matches.\r\n                        Same as :vimgrep {pattern} ##.\r\n\r\n:BufGrep[Add][!] [{pattern}]\r\n:BufGrep[Add][!] \/{pattern}\/[g][j]\r\n                        Search for {pattern} (or last search pattern if\r\n                        omitted) in all listed buffers and set the error list\r\n                        to the matches.\r\n\r\n:WinGrep[Add][!] [{pattern}]\r\n:WinGrep[Add][!] \/{pattern}\/[g][j]\r\n                        Search for {pattern} (or last search pattern if\r\n                        omitted) in all buffers visible in the current tab\r\n                        page and set the error list to the matches.\r\n\r\n:TabGrep[Add][!] [{pattern}]\r\n:TabGrep[Add][!] \/{pattern}\/[g][j]\r\n                        Search for {pattern} (or last search pattern if\r\n                        omitted) in all buffers visible in all tab pages and\r\n                        set the error list to the matches.","4":"DESCRIPTION\r\nThis plugin defines variants of the built-in :vimgrep command which target\r\nall arguments, listed buffers, windows in the current tab page or all tab\r\npages for its search. Additionally, the search defaults to the last search\r\npattern, so using these commands is often much faster than building the\r\nequivalent search with :vimgrep.\r\n\r\nSEE ALSO\r\n- The GrepHere plugin (vimscript #4191) provides a :GrepHere command that\r\n  covers only the current buffer.\r\n\r\nRELATED WORKS\r\n- This is a modern re-implementation of the similar commands defined by\r\n  greputils.vim (vimscript #1062), which hasn't been updated since 2005.\r\n- brep (vimscript #3653) can grep buffers (also unlisted with [!]) and show\r\n  them in the quickfix list.\r\n- greplace (vimscript #1813) can search buffers and arguments; it shows the\r\n  matches in a special replace buffer that can be edited and incorporated into\r\n  the original files.\r\n\r\nUSAGE\r\n:ArgGrep[Add][!] [{pattern}]\r\n:ArgGrep[Add][!] \/{pattern}\/[g][j]\r\n                        Search for {pattern} (or last search pattern if\r\n                        omitted) in all files from the argument-list and set\r\n                        the error list to the matches.\r\n                        Same as :vimgrep {pattern} ##.\r\n\r\n:BufGrep[Add][!] [{pattern}]\r\n:BufGrep[Add][!] \/{pattern}\/[g][j]\r\n                        Search for {pattern} (or last search pattern if\r\n                        omitted) in all listed buffers and set the error list\r\n                        to the matches.\r\n\r\n:WinGrep[Add][!] [{pattern}]\r\n:WinGrep[Add][!] \/{pattern}\/[g][j]\r\n                        Search for {pattern} (or last search pattern if\r\n                        omitted) in all buffers visible in the current tab\r\n                        page and set the error list to the matches.\r\n\r\n:TabGrep[Add][!] [{pattern}]\r\n:TabGrep[Add][!] \/{pattern}\/[g][j]\r\n                        Search for {pattern} (or last search pattern if\r\n                        omitted) in all buffers visible in all tab pages and\r\n                        set the error list to the matches.","install_details":"INSTALLATION\r\nThis script is packaged as a vimball. If you have the \"gunzip\" decompressor\r\nin your PATH, simply edit the *.vmb.gz package in Vim; otherwise, decompress\r\nthe archive first, e.g. using WinZip. Inside Vim, install by sourcing the\r\nvimball or via the :UseVimball command.\r\n    vim GrepCommands.vmb.gz\r\n    :so %\r\nTo uninstall, use the :RmVimball command.\r\n\r\nDEPENDENCIES\r\n- Requires Vim 7.0 or higher.\r\n- Requires the ingo-library.vim plugin (vimscript #4433), version 1.012 or\r\n  higher.","5":"INSTALLATION\r\nThis script is packaged as a vimball. If you have the \"gunzip\" decompressor\r\nin your PATH, simply edit the *.vmb.gz package in Vim; otherwise, decompress\r\nthe archive first, e.g. using WinZip. Inside Vim, install by sourcing the\r\nvimball or via the :UseVimball command.\r\n    vim GrepCommands.vmb.gz\r\n    :so %\r\nTo uninstall, use the :RmVimball command.\r\n\r\nDEPENDENCIES\r\n- Requires Vim 7.0 or higher.\r\n- Requires the ingo-library.vim plugin (vimscript #4433), version 1.012 or\r\n  higher.","first_name":"Ingo","6":"Ingo","last_name":"Karkat","7":"Karkat","releases":[{"0":"4173","vim_version":"7.0","1":"7.0","script_version":"1.02","2":"1.02","version_comment":"- Internal API changes to enable :GrepHere within a [range].\r\n- FIX: v:searchforward requires Vim 7.2; explicitly check for its existence and else just assume forward search.\r\n- Add dependency to ingo-library (vimscript #4433). *** You need to separately install ingo-library (vimscript #4433) version 1.012 (or higher)! ***","3":"- Internal API changes to enable :GrepHere within a [range].\r\n- FIX: v:searchforward requires Vim 7.2; explicitly check for its existence and else just assume forward search.\r\n- Add dependency to ingo-library (vimscript #4433). *** You need to separately install ingo-library (vimscript #4433) version 1.012 (or higher)! ***","package":"GrepCommands-1.02.vmb.gz","4":"GrepCommands-1.02.vmb.gz","src_id":"24770","5":"24770","creation_date":"1480431566","6":"1480431566"},{"0":"4173","vim_version":"7.0","1":"7.0","script_version":"1.01","2":"1.01","version_comment":"BUG: Forgot to append l:patternFlags and enclose in delimiters when there's a non-whitespace pattern; this makes the GrepHere plugin's mappings wrongly jump to the first match.\r\n","3":"BUG: Forgot to append l:patternFlags and enclose in delimiters when there's a non-whitespace pattern; this makes the GrepHere plugin's mappings wrongly jump to the first match.\r\n","package":"GrepCommands-1.01.vmb.gz","4":"GrepCommands-1.01.vmb.gz","src_id":"18480","5":"18480","creation_date":"1345817477","6":"1345817477"},{"0":"4173","vim_version":"7.0","1":"7.0","script_version":"1.00","2":"1.00","version_comment":"Initial upload","3":"Initial upload","package":"GrepCommands.vba.gz","4":"GrepCommands.vba.gz","src_id":"18414","5":"18414","creation_date":"1345102510","6":"1345102510"}]},"4172":{"script_id":"4172","0":"4172","script_name":"switch.vim","1":"switch.vim","script_type":"utility","2":"utility","summary":"Switch segments of text with predefined replacements","3":"Switch segments of text with predefined replacements","description":"Github project: https:\/\/github.com\/AndrewRadev\/switch.vim\r\nScreencast: http:\/\/youtu.be\/zIOOLZJb87U\r\n\r\nThe main entry point of the plugin is a single command, \":Switch\". When the command is executed, the plugin looks for one of a few specific patterns under the cursor and performs a substition depending on the pattern. For example, if the cursor is on the \"true\" in the following code:\r\n\r\n    flag = true\r\n\r\nThen, upon executing \":Switch\", the \"true\" will turn into \"false\".\r\n\r\nIt is highly recommended to map the \":Switch\" command to a key. For example, to map it to \"-\", place the following in your .vimrc:\r\n\r\n    nnoremap - :Switch<cr>\r\n\r\nHere's a list of some of the built-in switch definitions. To see all definitions, read the documentation. To see the actual definitions with their patterns and replacements, look at the file plugin\/switch.vim.\r\n\r\nGlobal:\r\n\r\n  Boolean conditions:\r\n      foo && bar\r\n      foo || bar\r\n\r\n  Boolean constants:\r\n      flag = true\r\n      flag = false\r\n\r\n      flag = True\r\n      flag = False\r\n\r\nRuby:\r\n\r\n  Hash style:\r\n      foo = { :one => 'two' }\r\n      foo = { one: 'two' }\r\n\r\n  If-clauses:\r\n      if predicate?\r\n        puts 'Hello, World!'\r\n      end\r\n\r\n      if true and (predicate?)\r\n        puts 'Hello, World!'\r\n      end\r\n\r\n      if false or (predicate?)\r\n        puts 'Hello, World!'\r\n      end\r\n\r\n  Rspec should\/should_not:\r\n      1.should eq 1\r\n      1.should_not eq 1\r\n\r\n  Tap:\r\n    foo = user.comments.map(&:author).first\r\n    foo = user.comments.tap { |o| puts o.inspect }.map(&:author).first\r\n\r\n  String style (Note that it only works for single-word strings):\r\n    foo = 'bar'\r\n    foo = \"baz\"\r\n    foo = :baz\r\n\r\nPHP:\r\n\r\n  \"Echo\" in tags:\r\n      <?php \"Text\" ?>\r\n      <?php echo \"Text\" ?>\r\n\r\nEruby:\r\n\r\n  If-clauses:\r\n      <% if predicate? %>\r\n        <%= 'Hello, World!' %>\r\n      <% end %>\r\n\r\n      <% if true and (predicate?) %>\r\n        <%= 'Hello, World!' %>\r\n      <% end %>\r\n\r\n      <% if false or (predicate?) %>\r\n        <%= 'Hello, World!' %>\r\n      <% end %>\r\n\r\n  Tag type:\r\n      <% something %>\r\n      <%# something %>\r\n      <%=raw something %>\r\n      <%= something %>\r\n\r\n  Hash style:\r\n      <% foo = { :one => 'two' } %>\r\n      <% foo = { one: 'two' } %>\r\n\r\nC++:\r\n\r\n  Pointer dots\/arrows:\r\n    Object* foo = bar.baz;\r\n    Object* foo = bar->baz;\r\n\r\nCoffeescript:\r\n\r\n  Arrows:\r\n    functionCall (foo) ->\r\n    functionCall (foo) =>\r\n\r\nFor more detailed information, please read the docs or check out the README on github.\r\n","4":"Github project: https:\/\/github.com\/AndrewRadev\/switch.vim\r\nScreencast: http:\/\/youtu.be\/zIOOLZJb87U\r\n\r\nThe main entry point of the plugin is a single command, \":Switch\". When the command is executed, the plugin looks for one of a few specific patterns under the cursor and performs a substition depending on the pattern. For example, if the cursor is on the \"true\" in the following code:\r\n\r\n    flag = true\r\n\r\nThen, upon executing \":Switch\", the \"true\" will turn into \"false\".\r\n\r\nIt is highly recommended to map the \":Switch\" command to a key. For example, to map it to \"-\", place the following in your .vimrc:\r\n\r\n    nnoremap - :Switch<cr>\r\n\r\nHere's a list of some of the built-in switch definitions. To see all definitions, read the documentation. To see the actual definitions with their patterns and replacements, look at the file plugin\/switch.vim.\r\n\r\nGlobal:\r\n\r\n  Boolean conditions:\r\n      foo && bar\r\n      foo || bar\r\n\r\n  Boolean constants:\r\n      flag = true\r\n      flag = false\r\n\r\n      flag = True\r\n      flag = False\r\n\r\nRuby:\r\n\r\n  Hash style:\r\n      foo = { :one => 'two' }\r\n      foo = { one: 'two' }\r\n\r\n  If-clauses:\r\n      if predicate?\r\n        puts 'Hello, World!'\r\n      end\r\n\r\n      if true and (predicate?)\r\n        puts 'Hello, World!'\r\n      end\r\n\r\n      if false or (predicate?)\r\n        puts 'Hello, World!'\r\n      end\r\n\r\n  Rspec should\/should_not:\r\n      1.should eq 1\r\n      1.should_not eq 1\r\n\r\n  Tap:\r\n    foo = user.comments.map(&:author).first\r\n    foo = user.comments.tap { |o| puts o.inspect }.map(&:author).first\r\n\r\n  String style (Note that it only works for single-word strings):\r\n    foo = 'bar'\r\n    foo = \"baz\"\r\n    foo = :baz\r\n\r\nPHP:\r\n\r\n  \"Echo\" in tags:\r\n      <?php \"Text\" ?>\r\n      <?php echo \"Text\" ?>\r\n\r\nEruby:\r\n\r\n  If-clauses:\r\n      <% if predicate? %>\r\n        <%= 'Hello, World!' %>\r\n      <% end %>\r\n\r\n      <% if true and (predicate?) %>\r\n        <%= 'Hello, World!' %>\r\n      <% end %>\r\n\r\n      <% if false or (predicate?) %>\r\n        <%= 'Hello, World!' %>\r\n      <% end %>\r\n\r\n  Tag type:\r\n      <% something %>\r\n      <%# something %>\r\n      <%=raw something %>\r\n      <%= something %>\r\n\r\n  Hash style:\r\n      <% foo = { :one => 'two' } %>\r\n      <% foo = { one: 'two' } %>\r\n\r\nC++:\r\n\r\n  Pointer dots\/arrows:\r\n    Object* foo = bar.baz;\r\n    Object* foo = bar->baz;\r\n\r\nCoffeescript:\r\n\r\n  Arrows:\r\n    functionCall (foo) ->\r\n    functionCall (foo) =>\r\n\r\nFor more detailed information, please read the docs or check out the README on github.\r\n","install_details":"There are several ways to install the plugin. The recommended one is by using Tim Pope's pathogen (http:\/\/www.vim.org\/scripts\/script.php?script_id=2332). In that case, you can clone the plugin's git repository like so:\r\n\r\n    git clone git:\/\/github.com\/AndrewRadev\/switch.vim.git ~\/.vim\/bundle\/switch\r\n\r\nIf your vim configuration is under git version control, you could also set up the repository as a submodule, which would allow you to update more easily. The command is (provided you're in ~\/.vim):\r\n\r\n    git submodule add git:\/\/github.com\/AndrewRadev\/switch.vim.git bundle\/switch\r\n\r\nAnother way is to simply copy all the essential directories inside the ~\/.vim directory: plugin, autoload, doc.\r\n","5":"There are several ways to install the plugin. The recommended one is by using Tim Pope's pathogen (http:\/\/www.vim.org\/scripts\/script.php?script_id=2332). In that case, you can clone the plugin's git repository like so:\r\n\r\n    git clone git:\/\/github.com\/AndrewRadev\/switch.vim.git ~\/.vim\/bundle\/switch\r\n\r\nIf your vim configuration is under git version control, you could also set up the repository as a submodule, which would allow you to update more easily. The command is (provided you're in ~\/.vim):\r\n\r\n    git submodule add git:\/\/github.com\/AndrewRadev\/switch.vim.git bundle\/switch\r\n\r\nAnother way is to simply copy all the essential directories inside the ~\/.vim directory: plugin, autoload, doc.\r\n","first_name":"Andrew","6":"Andrew","last_name":"Radev","7":"Radev","releases":[{"0":"4172","vim_version":"7.0","1":"7.0","script_version":"0.3.0","2":"0.3.0","version_comment":"- Haml support\r\n- Coffeescript dictionary shorthand\r\n- Default mapping\r\n- Various bugfixes","3":"- Haml support\r\n- Coffeescript dictionary shorthand\r\n- Default mapping\r\n- Various bugfixes","package":"switch.zip","4":"switch.zip","src_id":"22836","5":"22836","creation_date":"1422351809","6":"1422351809"},{"0":"4172","vim_version":"7.0","1":"7.0","script_version":"0.2.0","2":"0.2.0","version_comment":"- Better customization\r\n- More switches","3":"- Better customization\r\n- More switches","package":"switch.zip","4":"switch.zip","src_id":"21385","5":"21385","creation_date":"1390763463","6":"1390763463"},{"0":"4172","vim_version":"7.0","1":"7.0","script_version":"0.1.1","2":"0.1.1","version_comment":"Bugfix for multibyte characters","3":"Bugfix for multibyte characters","package":"switch.zip","4":"switch.zip","src_id":"18583","5":"18583","creation_date":"1347386106","6":"1347386106"},{"0":"4172","vim_version":"7.0","1":"7.0","script_version":"0.1.0","2":"0.1.0","version_comment":"- Better customization options\r\n- Builtin for C++ pointers\r\n- Builtin for coffeescript arrows\r\n- Builtin for ruby's tap method\r\n- Builtin for ruby string types\r\n- Bugfixes\r\n","3":"- Better customization options\r\n- Builtin for C++ pointers\r\n- Builtin for coffeescript arrows\r\n- Builtin for ruby's tap method\r\n- Builtin for ruby string types\r\n- Bugfixes\r\n","package":"switch.zip","4":"switch.zip","src_id":"18573","5":"18573","creation_date":"1347195521","6":"1347195521"},{"0":"4172","vim_version":"7.0","1":"7.0","script_version":"0.0.1","2":"0.0.1","version_comment":"Initial upload","3":"Initial upload","package":"switch.zip","4":"switch.zip","src_id":"18405","5":"18405","creation_date":"1345013476","6":"1345013476"}]},"4171":{"script_id":"4171","0":"4171","script_name":"sideways.vim","1":"sideways.vim","script_type":"utility","2":"utility","summary":"Move function arguments (and other delimited-by-something items) left and right","3":"Move function arguments (and other delimited-by-something items) left and right","description":"Github project: https:\/\/github.com\/AndrewRadev\/sideways.vim\r\n\r\nThe plugin defines two commands, \":SidewaysLeft\" and \":SidewaysRight\", which move the item under the cursor left or right, where an \"item\" is defined by a delimiter. As an example:\r\n\r\n    def function(one, two, three):\r\n        pass\r\n\r\nPlacing the cursor on \"two\" and executing `:SidewaysLeft`, the \"one\" and \"two\" arguments will switch their places, resulting in this:\r\n\r\n    def function(two, one, three):\r\n        pass\r\n\r\nIn this case, the delimiter is a comma. The plugin currently works with various other cases and it's intended to make the process configurable. While this particular example is in python, this should work for arguments in many different languages that use round braces to denote function calls.\r\n\r\nFor ruby and eruby, it detects method calls without braces as well:\r\n\r\n    link_to user_registration_path, 'Something'\r\n    # changes to:\r\n    link_to 'Something', user_registration_path\r\n\r\nApart from functions, it works for square-bracket lists in dynamic languages:\r\n\r\n    list = [one, [two, four, five], three]\r\n\r\nNotice that, if you experiment with this example, you'll find that you can move the entire second list around. The plugin takes into consideration nested structures.\r\n\r\nIt also works for multiline lists. Try experimenting with this example:\r\n\r\n    <div class=\"example\"\r\n         style=\"color: red;\"\r\n         something=\"other\">\r\n      Example\r\n    <\/div>\r\n\r\nApart from functions, it works for a lot of other things, but it's recommended to look at the github project or the help files for additional details. The plugin also provides:\r\n\r\n- A text object to change\/delete\/yank items in lists\r\n- A mapping to add new items forwards or backwards in the list\r\n","4":"Github project: https:\/\/github.com\/AndrewRadev\/sideways.vim\r\n\r\nThe plugin defines two commands, \":SidewaysLeft\" and \":SidewaysRight\", which move the item under the cursor left or right, where an \"item\" is defined by a delimiter. As an example:\r\n\r\n    def function(one, two, three):\r\n        pass\r\n\r\nPlacing the cursor on \"two\" and executing `:SidewaysLeft`, the \"one\" and \"two\" arguments will switch their places, resulting in this:\r\n\r\n    def function(two, one, three):\r\n        pass\r\n\r\nIn this case, the delimiter is a comma. The plugin currently works with various other cases and it's intended to make the process configurable. While this particular example is in python, this should work for arguments in many different languages that use round braces to denote function calls.\r\n\r\nFor ruby and eruby, it detects method calls without braces as well:\r\n\r\n    link_to user_registration_path, 'Something'\r\n    # changes to:\r\n    link_to 'Something', user_registration_path\r\n\r\nApart from functions, it works for square-bracket lists in dynamic languages:\r\n\r\n    list = [one, [two, four, five], three]\r\n\r\nNotice that, if you experiment with this example, you'll find that you can move the entire second list around. The plugin takes into consideration nested structures.\r\n\r\nIt also works for multiline lists. Try experimenting with this example:\r\n\r\n    <div class=\"example\"\r\n         style=\"color: red;\"\r\n         something=\"other\">\r\n      Example\r\n    <\/div>\r\n\r\nApart from functions, it works for a lot of other things, but it's recommended to look at the github project or the help files for additional details. The plugin also provides:\r\n\r\n- A text object to change\/delete\/yank items in lists\r\n- A mapping to add new items forwards or backwards in the list\r\n","install_details":"The easiest way to install the plugin is with a plugin manager:\r\n\r\n- vim-plug: https:\/\/github.com\/junegunn\/vim-plug\r\n- Vundle:   https:\/\/github.com\/VundleVim\/Vundle.vim\r\n\r\nIf you use one, just follow the instructions in its documentation.\r\n\r\nYou can install the plugin yourself using Vim's |packages| functionality by cloning the project (or adding it as a submodule) under `~\/.vim\/pack\/<any-name>\/start\/`. For example:\r\n\r\n    git clone https:\/\/github.com\/AndrewRadev\/sideways.vim ~\/.vim\/pack\/_\/start\/sideways\r\n\r\nThis should automatically load the plugin for you on Vim start. Alternatively, you can add it to `~\/.vim\/pack\/<any-name>\/opt\/` instead and load it in your .vimrc manually with:\r\n\r\n    packadd sideways\r\n\r\nIf you'd rather not use git, you can download the files from this page and unzip them in the relevant directory.\r\n","5":"The easiest way to install the plugin is with a plugin manager:\r\n\r\n- vim-plug: https:\/\/github.com\/junegunn\/vim-plug\r\n- Vundle:   https:\/\/github.com\/VundleVim\/Vundle.vim\r\n\r\nIf you use one, just follow the instructions in its documentation.\r\n\r\nYou can install the plugin yourself using Vim's |packages| functionality by cloning the project (or adding it as a submodule) under `~\/.vim\/pack\/<any-name>\/start\/`. For example:\r\n\r\n    git clone https:\/\/github.com\/AndrewRadev\/sideways.vim ~\/.vim\/pack\/_\/start\/sideways\r\n\r\nThis should automatically load the plugin for you on Vim start. Alternatively, you can add it to `~\/.vim\/pack\/<any-name>\/opt\/` instead and load it in your .vimrc manually with:\r\n\r\n    packadd sideways\r\n\r\nIf you'd rather not use git, you can download the files from this page and unzip them in the relevant directory.\r\n","first_name":"Andrew","6":"Andrew","last_name":"Radev","7":"Radev","releases":[{"0":"4171","vim_version":"7.0","1":"7.0","script_version":"0.4.0","2":"0.4.0","version_comment":"- JSX support\r\n- Rust support\r\n- Support for items that span multiple lines\r\n- Mappings for adding new items\r\n- Lots of bugfixes","3":"- JSX support\r\n- Rust support\r\n- Support for items that span multiple lines\r\n- Mappings for adding new items\r\n- Lots of bugfixes","package":"sideways.zip","4":"sideways.zip","src_id":"27301","5":"27301","creation_date":"1598892816","6":"1598892816"},{"0":"4171","vim_version":"7.0","1":"7.0","script_version":"0.3.0","2":"0.3.0","version_comment":"- Multiline lists\r\n- Support for handlebars templates\r\n- Various bugfixes","3":"- Multiline lists\r\n- Support for handlebars templates\r\n- Various bugfixes","package":"sideways.zip","4":"sideways.zip","src_id":"24358","5":"24358","creation_date":"1467537323","6":"1467537323"},{"0":"4171","vim_version":"7.0","1":"7.0","script_version":"0.2.0","2":"0.2.0","version_comment":"- Coffeescript methods\r\n- Ruby methods in haml\r\n- Haml classes\r\n- HTML attributes\r\n- Various bugfixes","3":"- Coffeescript methods\r\n- Ruby methods in haml\r\n- Haml classes\r\n- HTML attributes\r\n- Various bugfixes","package":"sideways.zip","4":"sideways.zip","src_id":"22832","5":"22832","creation_date":"1422350579","6":"1422350579"},{"0":"4171","vim_version":"7.0","1":"7.0","script_version":"0.1.0","2":"0.1.0","version_comment":"- Ruby methods without brackets\r\n- Go lists\r\n- Argument text object\r\n- Various bugfixes","3":"- Ruby methods without brackets\r\n- Go lists\r\n- Argument text object\r\n- Various bugfixes","package":"sideways.zip","4":"sideways.zip","src_id":"21341","5":"21341","creation_date":"1390067429","6":"1390067429"},{"0":"4171","vim_version":"7.0","1":"7.0","script_version":"0.0.2","2":"0.0.2","version_comment":"- Single-line CSS declarations\r\n- Various bugfixes and refactoring","3":"- Single-line CSS declarations\r\n- Various bugfixes and refactoring","package":"sideways.zip","4":"sideways.zip","src_id":"18756","5":"18756","creation_date":"1349548583","6":"1349548583"},{"0":"4171","vim_version":"7.0","1":"7.0","script_version":"0.0.1","2":"0.0.1","version_comment":"Initial upload","3":"Initial upload","package":"sideways.zip","4":"sideways.zip","src_id":"18404","5":"18404","creation_date":"1345013060","6":"1345013060"}]},"4170":{"script_id":"4170","0":"4170","script_name":"Vdebug","1":"Vdebug","script_type":"utility","2":"utility","summary":"Multi-language DBGP debugger client (PHP, Python, Perl, Ruby, etc.)","3":"Multi-language DBGP debugger client (PHP, Python, Perl, Ruby, etc.)","description":"Vdebug is a new, fast, powerful debugger client for Vim. It's multi-language, and has been tested with PHP, Python, Ruby, NodeJS and Tcl. It interfaces with any debugger that faithfully uses the DBGP protocol, such as Xdebug for PHP. There are step-by-step instructions for setting up debugging with all of the aforementioned languages in the Vim help file that comes with Vdebug.\r\n\r\nIt builds on the experience gained through the legacy of the Xdebug Vim script originally created by Seung Woo Shin and extended by so many others, but it's a total rebuild to allow for a nicer interface and support of new features.\r\n\r\nPlus, I find it a LOT faster. Why not try it for yourself?\r\n\r\nIt's written in Python, and has an object-oriented interface that is easy to extend and can even be used from the command-line. It even has unit tests covering some of the more critical parts of the code.\r\n\r\n--------------------\r\nMain features\r\n--------------------\r\n\r\n- Multi-language support\r\n- Set and remove breakpoints (line, conditional, exception, return and call)\r\n- Watch window showing all variables, and allowing you to switch context (to globals, etc)\r\n- Watch window variables shown as a tree, and drill down into child elements\r\n- Run \"eval\" commands on code snippets and see the output as a tree\r\n- Run to cursor\r\n- Support for debugging scripts on a remote machine\r\n- The usual commands: run, step over, step in, step out, stop and detach\r\n- IDE key support\r\n- Complete key re-mapping possible\r\n- Lots of configuration options\r\n- Log to file or Vim window\r\n\r\n-----------------\r\nHow to use\r\n-----------------\r\n\r\nThere is very extensive help provided in the form of a Vim help file. This goes through absolutely everything, from installation to configuration, setting up debuggers for various languages, explanation of the interface, options, remote server debugging and more.\r\n\r\nTo get this help, type:\r\n\r\n    :help Vdebug\r\n\r\nafter installing the plugin.","4":"Vdebug is a new, fast, powerful debugger client for Vim. It's multi-language, and has been tested with PHP, Python, Ruby, NodeJS and Tcl. It interfaces with any debugger that faithfully uses the DBGP protocol, such as Xdebug for PHP. There are step-by-step instructions for setting up debugging with all of the aforementioned languages in the Vim help file that comes with Vdebug.\r\n\r\nIt builds on the experience gained through the legacy of the Xdebug Vim script originally created by Seung Woo Shin and extended by so many others, but it's a total rebuild to allow for a nicer interface and support of new features.\r\n\r\nPlus, I find it a LOT faster. Why not try it for yourself?\r\n\r\nIt's written in Python, and has an object-oriented interface that is easy to extend and can even be used from the command-line. It even has unit tests covering some of the more critical parts of the code.\r\n\r\n--------------------\r\nMain features\r\n--------------------\r\n\r\n- Multi-language support\r\n- Set and remove breakpoints (line, conditional, exception, return and call)\r\n- Watch window showing all variables, and allowing you to switch context (to globals, etc)\r\n- Watch window variables shown as a tree, and drill down into child elements\r\n- Run \"eval\" commands on code snippets and see the output as a tree\r\n- Run to cursor\r\n- Support for debugging scripts on a remote machine\r\n- The usual commands: run, step over, step in, step out, stop and detach\r\n- IDE key support\r\n- Complete key re-mapping possible\r\n- Lots of configuration options\r\n- Log to file or Vim window\r\n\r\n-----------------\r\nHow to use\r\n-----------------\r\n\r\nThere is very extensive help provided in the form of a Vim help file. This goes through absolutely everything, from installation to configuration, setting up debuggers for various languages, explanation of the interface, options, remote server debugging and more.\r\n\r\nTo get this help, type:\r\n\r\n    :help Vdebug\r\n\r\nafter installing the plugin.","install_details":"--------------------\r\nRequirements\r\n--------------------\r\n- Vim compiled with Python 2.4+ support, tabs and signs\r\n- A programming language that has a DBGP debugger, e.g. PHP, Python, Ruby, Perl, Tcl, NodeJS... (set-up included in the Vim help)\r\n\r\n-----------\r\nClassic\r\n-----------\r\nClone or download a tarball of the plugin and move its content in your ~\/.vim\/ directory.\r\n\r\nYour ~\/.vim\/plugins\/ directory should now contain vdebug.vim and a directory called \"python\".\r\n\r\n----------------------------------\r\nUsing git and Pathogen\r\n----------------------------------\r\nClone https:\/\/github.com\/joonty\/vdebug.git in your ~\/.vim\/bundle directory\r\n\r\n-------------------\r\nUsing vundle\r\n-------------------\r\nAdd this to your ~\/.vimrc file:\r\n\r\n    Bundle 'joonty\/vdebug.git'\r\n\r\nThen, from the command line, run:\r\n\r\n    vim +BundleInstall +qall","5":"--------------------\r\nRequirements\r\n--------------------\r\n- Vim compiled with Python 2.4+ support, tabs and signs\r\n- A programming language that has a DBGP debugger, e.g. PHP, Python, Ruby, Perl, Tcl, NodeJS... (set-up included in the Vim help)\r\n\r\n-----------\r\nClassic\r\n-----------\r\nClone or download a tarball of the plugin and move its content in your ~\/.vim\/ directory.\r\n\r\nYour ~\/.vim\/plugins\/ directory should now contain vdebug.vim and a directory called \"python\".\r\n\r\n----------------------------------\r\nUsing git and Pathogen\r\n----------------------------------\r\nClone https:\/\/github.com\/joonty\/vdebug.git in your ~\/.vim\/bundle directory\r\n\r\n-------------------\r\nUsing vundle\r\n-------------------\r\nAdd this to your ~\/.vimrc file:\r\n\r\n    Bundle 'joonty\/vdebug.git'\r\n\r\nThen, from the command line, run:\r\n\r\n    vim +BundleInstall +qall","first_name":"Jon","6":"Jon","last_name":"Cairns","7":"Cairns","releases":[{"0":"4170","vim_version":"7.0","1":"7.0","script_version":"1.5.1","2":"1.5.1","version_comment":"Bug fixes:\r\n * Fix buffers not being wiped out after ending a session (thanks @BlackIkeEagle, #226)\r\n\r\nFeatures:\r\n * Add :VdebugEval! command, which remembers the eval expression when stepping\r\n through, as an alternative to :VdebugTrace (thanks @benjifisher, #193)","3":"Bug fixes:\r\n * Fix buffers not being wiped out after ending a session (thanks @BlackIkeEagle, #226)\r\n\r\nFeatures:\r\n * Add :VdebugEval! command, which remembers the eval expression when stepping\r\n through, as an alternative to :VdebugTrace (thanks @benjifisher, #193)","package":"vdebug-1.5.1.tar.gz","4":"vdebug-1.5.1.tar.gz","src_id":"23580","5":"23580","creation_date":"1441640305","6":"1441640305"},{"0":"4170","vim_version":"7.0","1":"7.0","script_version":"1.5.0","2":"1.5.0","version_comment":"=== Vdebug 1.5.0 \/ 2015-08-28\r\nBug fixes:\r\n * Fix for remote and local file paths with a windows\/unix setup (thanks @brothert, #130)\r\n * Sort path maps by remote path length (thanks @ragol and @adambiggs, #153, #201)\r\n * Default \\\"stop\\\" behaviour (default <F6>) actually stops rather than detaches (issue #166)\r\n * Various documentation fixes (issue #172, issue #223, thanks @loonies for #210)\r\n * Add documentation to show that komodo-debug doesn\\'t work with nodejs > 0.10 (#202, #223)\r\n * Don\\'t override previously defined breakpoint highlights (#208)\r\n\r\nFeatures:\r\n * Add support for Python 2.4 (thanks @mbarbon, #189)\r\n * Add Vagrantfile and bootstrap for easier local development\r\n * Add new VdebugTrace command for tracking individual variables and expressions (thanks @escher9, #178)\r\n * Show ellipses for truncated arrays in watch window (#177)\r\n * Bind to all available interfaces by default, instead of just localhost (#209, thanks @zolem)\r\n\r\nMisc:\r\n * Changed HISTORY to CHANGELOG","3":"=== Vdebug 1.5.0 \/ 2015-08-28\r\nBug fixes:\r\n * Fix for remote and local file paths with a windows\/unix setup (thanks @brothert, #130)\r\n * Sort path maps by remote path length (thanks @ragol and @adambiggs, #153, #201)\r\n * Default \\\"stop\\\" behaviour (default <F6>) actually stops rather than detaches (issue #166)\r\n * Various documentation fixes (issue #172, issue #223, thanks @loonies for #210)\r\n * Add documentation to show that komodo-debug doesn\\'t work with nodejs > 0.10 (#202, #223)\r\n * Don\\'t override previously defined breakpoint highlights (#208)\r\n\r\nFeatures:\r\n * Add support for Python 2.4 (thanks @mbarbon, #189)\r\n * Add Vagrantfile and bootstrap for easier local development\r\n * Add new VdebugTrace command for tracking individual variables and expressions (thanks @escher9, #178)\r\n * Show ellipses for truncated arrays in watch window (#177)\r\n * Bind to all available interfaces by default, instead of just localhost (#209, thanks @zolem)\r\n\r\nMisc:\r\n * Changed HISTORY to CHANGELOG","package":"vdebug-1.5.0.tar.gz","4":"vdebug-1.5.0.tar.gz","src_id":"23553","5":"23553","creation_date":"1440603126","6":"1440603126"},{"0":"4170","vim_version":"7.0","1":"7.0","script_version":"1.4.2","2":"1.4.2","version_comment":"Bug fixes:\r\n * Allow overriding of options dictionary after sourcing vdebug (issues #112, #113)\r\n * Show local file path in stack window if using path mapping (issue #118)\r\n * Change function names for stricter rules introduced in Vim v.7.4.260 (thanks @BlackEagle, #158 and #155)\r\n\r\nDocumentation:\r\n * Various fixes\r\n * Mention vim-nox package for Debian (thanks @henningda, #138)\r\n * Add Python installation for Windows information (issue #135)\r\n\r\nFeatures:\r\n * Add completion to :Breakpoint command (thanks @tommcdo, #124)\r\n * Add VdebugStart command (thanks @blueyed, #132)\r\n * Sleep for 100ms in wait loop, don't consume as much CPU (thanks @blueyed, #133)","3":"Bug fixes:\r\n * Allow overriding of options dictionary after sourcing vdebug (issues #112, #113)\r\n * Show local file path in stack window if using path mapping (issue #118)\r\n * Change function names for stricter rules introduced in Vim v.7.4.260 (thanks @BlackEagle, #158 and #155)\r\n\r\nDocumentation:\r\n * Various fixes\r\n * Mention vim-nox package for Debian (thanks @henningda, #138)\r\n * Add Python installation for Windows information (issue #135)\r\n\r\nFeatures:\r\n * Add completion to :Breakpoint command (thanks @tommcdo, #124)\r\n * Add VdebugStart command (thanks @blueyed, #132)\r\n * Sleep for 100ms in wait loop, don't consume as much CPU (thanks @blueyed, #133)","package":"vdebug-1.4.2.tar.gz","4":"vdebug-1.4.2.tar.gz","src_id":"21885","5":"21885","creation_date":"1400161987","6":"1400161987"},{"0":"4170","vim_version":"7.0","1":"7.0","script_version":"1.4.2","2":"1.4.2","version_comment":"Bug fixes:\r\n * Add compatibility fix for Python debugging (due to incorrect \"file:\/\" prefix) (issue #68, #102)\r\n * Fix remote path slash replacement (issue #94)\r\n * Fix rendering of unicode in watch window (issue #95)\r\n * Stop errors being thrown on Vim 7.4 (issue #98, #96, #99)\r\n * Fix error message on plugin reload, from function definition (thanks @glittershark, #106)\r\n\r\nDocumentation:\r\n * Correct minor spelling and grammar errors in help doc (thanks @dkinzer, #108)\r\n * Change the description for setting up the python debugger in the docs\r\n\r\nOther:\r\n * Add cucumber for integration tests, and add lots of features","3":"Bug fixes:\r\n * Add compatibility fix for Python debugging (due to incorrect \"file:\/\" prefix) (issue #68, #102)\r\n * Fix remote path slash replacement (issue #94)\r\n * Fix rendering of unicode in watch window (issue #95)\r\n * Stop errors being thrown on Vim 7.4 (issue #98, #96, #99)\r\n * Fix error message on plugin reload, from function definition (thanks @glittershark, #106)\r\n\r\nDocumentation:\r\n * Correct minor spelling and grammar errors in help doc (thanks @dkinzer, #108)\r\n * Change the description for setting up the python debugger in the docs\r\n\r\nOther:\r\n * Add cucumber for integration tests, and add lots of features","package":"vdebug-1.4.2.tar.gz","4":"vdebug-1.4.2.tar.gz","src_id":"21024","5":"21024","creation_date":"1384161647","6":"1384161647"},{"0":"4170","vim_version":"7.0","1":"7.0","script_version":"1.4.1","2":"1.4.1","version_comment":"Bug fixes:\r\n * Fix folds being forgotten after debugging (issue #56)\r\n * Don't overwrite features array if it exists (issue #59)\r\n * Mapping of single modes (thanks @xbot, #66)\r\n * Stop empty buffers from being created (issue #70)\r\n * Fix ElementTree deprecation warning (thanks @InFog, #89)\r\n * Fix minheight error for windows (thanks @zhaocai, #73, also #84)\r\n * Fix filename handling on windows (thanks @Chronial, #74)\r\n * Use :mkexrc for restoring keymapping (thanks @Chronial and @qstrahl, #75)\r\n * Fix window destruction (thanks @Chronial, #76)\r\n * Inspect PHP constants with cursor eval (issue #80)\r\n * Don't cut final character when inspecting variables at end of line (issue #85)\r\n\r\nDocumentation:\r\n * Test suite requirements (thanks @michaeltwofish, #61)\r\n * Add helptag instructions to README (issue #67)\r\n * Add 'eval_visual' to documentation (issue #88)","3":"Bug fixes:\r\n * Fix folds being forgotten after debugging (issue #56)\r\n * Don't overwrite features array if it exists (issue #59)\r\n * Mapping of single modes (thanks @xbot, #66)\r\n * Stop empty buffers from being created (issue #70)\r\n * Fix ElementTree deprecation warning (thanks @InFog, #89)\r\n * Fix minheight error for windows (thanks @zhaocai, #73, also #84)\r\n * Fix filename handling on windows (thanks @Chronial, #74)\r\n * Use :mkexrc for restoring keymapping (thanks @Chronial and @qstrahl, #75)\r\n * Fix window destruction (thanks @Chronial, #76)\r\n * Inspect PHP constants with cursor eval (issue #80)\r\n * Don't cut final character when inspecting variables at end of line (issue #85)\r\n\r\nDocumentation:\r\n * Test suite requirements (thanks @michaeltwofish, #61)\r\n * Add helptag instructions to README (issue #67)\r\n * Add 'eval_visual' to documentation (issue #88)","package":"vdebug-1.4.1.tar.gz","4":"vdebug-1.4.1.tar.gz","src_id":"20327","5":"20327","creation_date":"1370769183","6":"1370769183"},{"0":"4170","vim_version":"7.0","1":"7.0","script_version":"1.4.0","2":"1.4.0","version_comment":"Features:\r\n * Set debugger features with g:vdebug_features dictionary (issue #55)\r\n * Allow use of '~' in log files (issue #53)\r\n\r\nBug fixes:\r\n * Print error message if trying to start debugger with unsaved buffers (issue #57)\r\n * Don't allow visual eval outside of debugging session (issue #52)\r\n * Show updated key mappings in status window (issue #51)\r\n * Fix problem with stuck breakpoints after debugging (issue #48, #43)\r\n * Swap back to original tab after debugging session closes (issue #23)","3":"Features:\r\n * Set debugger features with g:vdebug_features dictionary (issue #55)\r\n * Allow use of '~' in log files (issue #53)\r\n\r\nBug fixes:\r\n * Print error message if trying to start debugger with unsaved buffers (issue #57)\r\n * Don't allow visual eval outside of debugging session (issue #52)\r\n * Show updated key mappings in status window (issue #51)\r\n * Fix problem with stuck breakpoints after debugging (issue #48, #43)\r\n * Swap back to original tab after debugging session closes (issue #23)","package":"vdebug-1.4.0.tar.gz","4":"vdebug-1.4.0.tar.gz","src_id":"19599","5":"19599","creation_date":"1362580100","6":"1362580100"},{"0":"4170","vim_version":"7.0","1":"7.0","script_version":"1.3.2","2":"1.3.2","version_comment":"Features:\r\n * Don't allow breakpoints to be set on empty lines (issue #27)\r\n * Add :VdebugOpt command for easy setting and getting of options (issue #38)\r\n\r\nBug fixes:\r\n * Small fixes for documentation (thanks: https:\/\/github.com\/grota, #31)\r\n * Parse continuous mode option as an integer (thanks: https:\/\/github.com\/grota, #32)\r\n * Stop Xdebug hanging when using the detach command (issue #33)\r\n * Don't use recursive Vim mapping (issue #34)\r\n * Track movement of line breaks with Vim signs (issue #35)\r\n * Add \"default\" keyword to highlights, to allow custom colours (issue #36)\r\n * Fix check for multibyte support (issue #37)\r\n * Fix deprecation warning in Python 2.6, catching string exceptions (issue #39)\r\n * Stop source code panel opening in incorrect position (issue #40)","3":"Features:\r\n * Don't allow breakpoints to be set on empty lines (issue #27)\r\n * Add :VdebugOpt command for easy setting and getting of options (issue #38)\r\n\r\nBug fixes:\r\n * Small fixes for documentation (thanks: https:\/\/github.com\/grota, #31)\r\n * Parse continuous mode option as an integer (thanks: https:\/\/github.com\/grota, #32)\r\n * Stop Xdebug hanging when using the detach command (issue #33)\r\n * Don't use recursive Vim mapping (issue #34)\r\n * Track movement of line breaks with Vim signs (issue #35)\r\n * Add \"default\" keyword to highlights, to allow custom colours (issue #36)\r\n * Fix check for multibyte support (issue #37)\r\n * Fix deprecation warning in Python 2.6, catching string exceptions (issue #39)\r\n * Stop source code panel opening in incorrect position (issue #40)","package":"vdebug-1.3.2.tar.gz","4":"vdebug-1.3.2.tar.gz","src_id":"19445","5":"19445","creation_date":"1359391664","6":"1359391664"},{"0":"4170","vim_version":"7.0","1":"7.0","script_version":"1.3.1","2":"1.3.1","version_comment":"Bug fixes: \r\n* Filepath problems with Windows version \r\n\r\nOther: \r\n* Packaged tests as an easy-to-run suite \r\n* Set up on Travis CI\r\n* Re-uploaded archive with gzip compression","3":"Bug fixes: \r\n* Filepath problems with Windows version \r\n\r\nOther: \r\n* Packaged tests as an easy-to-run suite \r\n* Set up on Travis CI\r\n* Re-uploaded archive with gzip compression","package":"vdebug-1.3.1.tar.gz","4":"vdebug-1.3.1.tar.gz","src_id":"19268","5":"19268","creation_date":"1356951480","6":"1356951480"},{"0":"4170","vim_version":"7.0","1":"7.0","script_version":"1.3.0","2":"1.3.0","version_comment":" * Support and compatibility fixes for debugging Tcl, plus help file updates\r\n * Non-multibyte Vim installations now use ASCII watch window marker characters as a fallback (thanks: https:\/\/github.com\/satiani, #21)\r\n * Watch window marker characters are fully customizable\r\n * Satiani added multiple file path mappings, for remote debugging (thanks: https:\/\/github.com\/satiani, #20)\r\n * Vdebug re-maps previous key mappings after shutting down (issue #16)\r\n * Added 'watch_window_style' option that allows for a compact or (default) expanded watch window (thanks: https:\/\/github.com\/georgjaehnig, #13)\r\n * Simple continuous mode added, where vdebug starts listening after a connection closes, to allow for debugging to start again immediately (issue #19)\r\n * LOTS of bug fixes - see HISTORY file for more\r\n","3":" * Support and compatibility fixes for debugging Tcl, plus help file updates\r\n * Non-multibyte Vim installations now use ASCII watch window marker characters as a fallback (thanks: https:\/\/github.com\/satiani, #21)\r\n * Watch window marker characters are fully customizable\r\n * Satiani added multiple file path mappings, for remote debugging (thanks: https:\/\/github.com\/satiani, #20)\r\n * Vdebug re-maps previous key mappings after shutting down (issue #16)\r\n * Added 'watch_window_style' option that allows for a compact or (default) expanded watch window (thanks: https:\/\/github.com\/georgjaehnig, #13)\r\n * Simple continuous mode added, where vdebug starts listening after a connection closes, to allow for debugging to start again immediately (issue #19)\r\n * LOTS of bug fixes - see HISTORY file for more\r\n","package":"vdebug-1.3.0.tar.gz","4":"vdebug-1.3.0.tar.gz","src_id":"19211","5":"19211","creation_date":"1355925122","6":"1355925122"},{"0":"4170","vim_version":"7.0","1":"7.0","script_version":"1.2","2":"1.2","version_comment":" * Support for nodejs debugging using the komodo-debug package in NPM\r\n * Keyboard interrupt while Vim is waiting for a connection (thanks: http:\/\/github.com\/artnez, #6)\r\n * Fixed overwriting dir function with badly named variable (thanks: http:\/\/github.com\/csomme, #8)\r\n * Function keys for debugger are only mapped when the session starts, and are unmapped when it's closed (issue #1)\r\n * Removed the help tags file from the git repo (issue #10)","3":" * Support for nodejs debugging using the komodo-debug package in NPM\r\n * Keyboard interrupt while Vim is waiting for a connection (thanks: http:\/\/github.com\/artnez, #6)\r\n * Fixed overwriting dir function with badly named variable (thanks: http:\/\/github.com\/csomme, #8)\r\n * Function keys for debugger are only mapped when the session starts, and are unmapped when it's closed (issue #1)\r\n * Removed the help tags file from the git repo (issue #10)","package":"vdebug-1.2.tar.gz","4":"vdebug-1.2.tar.gz","src_id":"18749","5":"18749","creation_date":"1349454002","6":"1349454002"},{"0":"4170","vim_version":"7.0","1":"7.0","script_version":"1.1","2":"1.1","version_comment":"Fix for Windows file paths; close and open tree nodes on watch window; evaluate variable under cursor with <F12>.","3":"Fix for Windows file paths; close and open tree nodes on watch window; evaluate variable under cursor with <F12>.","package":"vdebug-1.1.tar.gz","4":"vdebug-1.1.tar.gz","src_id":"18513","5":"18513","creation_date":"1346342188","6":"1346342188"},{"0":"4170","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"vdebug-1.0.tar.gz","4":"vdebug-1.0.tar.gz","src_id":"18401","5":"18401","creation_date":"1344942784","6":"1344942784"}]},"4169":{"script_id":"4169","0":"4169","script_name":"VPSIONKI DATA","1":"VPSIONKI DATA","script_type":"utility","2":"utility","summary":"Portable Vim code to handle database as CSV file (eg. for contacts)","3":"Portable Vim code to handle database as CSV file (eg. for contacts)","description":"\" Plugin name :    VPSIONKI DATA\r\n\" Plugin function: CSV Contact - VIM Plugin\r\n\"\r\n\r\n\" Version: \r\n\" Code version : 0.0099\r\n\r\n\" Current status:\r\n\"    First Initial Basic version (under work)\r\n\r\n\" Author:  \r\n\" Initially started by Patrick295767 <\/\\at\/\\> gmail <\\{dot}> com\r\n\" Help, patches, comments, add-ons, flowers, ...  in further progressing welcome anytime. \r\n\r\n\" Aim:\r\n\"      Create a portable program for database \r\n\"       \r\n\"      Format to be handled in one soon future: CSV (Windows) and dbf\r\n\"      Allow the multi-lines for the NOTES + being compatible with the use of \r\n\"      mutt and mutt-query.\r\n\r\n\" Use: \r\n\" To start the CSV Contact plugin\r\n\"    Press \\ followed by k\r\n\"    Once pressed, you may see your CSV file, and you can press\r\n\"    h to display the previous record number\r\n\"    j for going down to select the data (ex. address, name, surname, ...)\r\n\"    k for going up to select the data (ex. address, name, surname, ...)\r\n\"    l to display the next record number\r\n\"    \/ to start the search\r\n\r\n\" Tips: You could for instance use the unison program to sync this csv file. \r\n\r\n\" Dependencies:\r\n\"    Does not need python\r\n\"    Does not need perl\r\n\"    ...\r\n\"    Does only require Vim or Gvim :):)\r\n\"    -> Remains Portable\r\n\r\n\r\n\" Variables:\r\n\" Please edit this line to setup your txt (csv file)\"\r\n\"     It might look like :   \"record1\",\"bla\",\"bla\" \\n  \"record2\",\"bla\",\"bla\"\r\nlet g:myvarabookvimcsvfile='c:\\docs\\outlook-contacts.txt'\r\nif has(\"unix\")\r\n  let g:myvarabookvimcsvfile='~\/contacts\/outlook-contacts.txt'\r\nendif\r\n","4":"\" Plugin name :    VPSIONKI DATA\r\n\" Plugin function: CSV Contact - VIM Plugin\r\n\"\r\n\r\n\" Version: \r\n\" Code version : 0.0099\r\n\r\n\" Current status:\r\n\"    First Initial Basic version (under work)\r\n\r\n\" Author:  \r\n\" Initially started by Patrick295767 <\/\\at\/\\> gmail <\\{dot}> com\r\n\" Help, patches, comments, add-ons, flowers, ...  in further progressing welcome anytime. \r\n\r\n\" Aim:\r\n\"      Create a portable program for database \r\n\"       \r\n\"      Format to be handled in one soon future: CSV (Windows) and dbf\r\n\"      Allow the multi-lines for the NOTES + being compatible with the use of \r\n\"      mutt and mutt-query.\r\n\r\n\" Use: \r\n\" To start the CSV Contact plugin\r\n\"    Press \\ followed by k\r\n\"    Once pressed, you may see your CSV file, and you can press\r\n\"    h to display the previous record number\r\n\"    j for going down to select the data (ex. address, name, surname, ...)\r\n\"    k for going up to select the data (ex. address, name, surname, ...)\r\n\"    l to display the next record number\r\n\"    \/ to start the search\r\n\r\n\" Tips: You could for instance use the unison program to sync this csv file. \r\n\r\n\" Dependencies:\r\n\"    Does not need python\r\n\"    Does not need perl\r\n\"    ...\r\n\"    Does only require Vim or Gvim :):)\r\n\"    -> Remains Portable\r\n\r\n\r\n\" Variables:\r\n\" Please edit this line to setup your txt (csv file)\"\r\n\"     It might look like :   \"record1\",\"bla\",\"bla\" \\n  \"record2\",\"bla\",\"bla\"\r\nlet g:myvarabookvimcsvfile='c:\\docs\\outlook-contacts.txt'\r\nif has(\"unix\")\r\n  let g:myvarabookvimcsvfile='~\/contacts\/outlook-contacts.txt'\r\nendif\r\n","install_details":"\" INSTALL: \r\n\"\r\n\" Add this code to your vim configuration\r\n\" and edit the variable with your CSV contact file:  g:myvarabookvimcsvfile ","5":"\" INSTALL: \r\n\"\r\n\" Add this code to your vim configuration\r\n\" and edit the variable with your CSV contact file:  g:myvarabookvimcsvfile ","first_name":"patrick295767","6":"patrick295767","last_name":"patrick295767","7":"patrick295767","releases":[{"0":"4169","vim_version":"7.0","1":"7.0","script_version":"0.0099","2":"0.0099","version_comment":"Initial upload","3":"Initial upload","package":"Plugin_VIM_Contacts_CSV.vim","4":"Plugin_VIM_Contacts_CSV.vim","src_id":"18400","5":"18400","creation_date":"1344912339","6":"1344912339"}]},"4168":{"script_id":"4168","0":"4168","script_name":"SyntaxRange","1":"SyntaxRange","script_type":"utility","2":"utility","summary":"Define a different filetype syntax on regions of a buffer.","3":"Define a different filetype syntax on regions of a buffer.","description":"DESCRIPTION\r\nThis plugin provides commands and functions to set up regions in the current\r\nbuffer that either use a syntax different from the buffer's 'filetype', or\r\ncompletely ignore the syntax.\r\n\r\nSEE ALSO\r\n- If you also want different buffer options (like indent settings, etc.) for\r\n  each syntax region, the OnSyntaxChange.vim plugin (vimscript #4085) allows\r\n  you to dynamically change the buffer options as you move through the buffer.\r\n\r\nRELATED WORKS\r\n- If the highlighting doesn't work properly, you could alternatively edit the\r\n  range(s) in a separate scratch buffer. Plugins like NrrwRgn (vimscript #3075)\r\n  provide commands to set these up, with automatic syncing back to the\r\n  original buffer.\r\n\r\nSOURCE\r\nThe code to include a different syntax in a region is based on\r\n    http:\/\/vim.wikia.com\/wiki\/Different_syntax_highlighting_within_regions_of_a_file\r\n\r\nUSAGE\r\nFor quick, ad-hoc manipulation of the syntax withing a range of lines, the\r\nfollowing commands are provided:\r\n\r\n:[range]SyntaxIgnore    Ignore the buffer's filetype syntax for the current\r\n                        line \/ lines in [range]. (Top-level keywords will\r\n                        still be highlighted.)\r\n                        This can be a useful fix when some text fragments\r\n                        confuse the syntax highlighting. (For example, when\r\n                        buffer syntax set to an inlined here-document is\r\n                        negatively affected by the foreign code surrounding\r\n                        the here-document.)\r\n\r\n:[range]SyntaxInclude {filetype}\r\n                        Use the {filetype} syntax for the current line \/ lines\r\n                        in [range].\r\n\r\n                        Line numbers in [range] are fixed; i.e. they do not\r\n                        adapt to inserted \/ deleted lines. But when in a\r\n                        range, the last line ($) is interpreted as \"end of\r\n                        file\".\r\n\r\nFor finer control and use in custom mappings or syntax tweaks, the following\r\nfunctions can be used. You'll find the details directly in the\r\n.vim\/autoload\/SyntaxRange.vim implementation file.\r\n\r\nSyntaxRange#Include( startPattern, endPattern, filetype, ... )\r\n                        Use the {filetype} syntax for the region defined by\r\n                        {startPattern} and {endPattern}.\r\nSyntaxRange#IncludeEx( regionDefinition, filetype )\r\n                        Use the {filetype} syntax for the region defined by\r\n                        {regionDefinition}.\r\n\r\nEXAMPLE\r\nTo highlight the text between the markers\r\n    @begin=c@\r\n    int i = 42;\r\n    @end=c@\r\nwith C syntax, and make the markers themselves fade into the background:\r\n    :call SyntaxRange#Include('@begin=c@', '@end=c@', 'c', 'NonText')\r\n\r\nTo highlight inline patches inside emails:\r\n    :call SyntaxRange#IncludeEx('start=\"^changeset\\|^Index: \\|^diff \\|^--- .*\\%( ----\\)\\@<!$\" skip=\"^[-+@       ]\" end=\"^$\"', 'diff')\r\nTo install this automatically for the \"mail\" filetype, put above line into a\r\nscript in ~\/.vim\/after\/syntax\/mail\/SyntaxInclude.vim","4":"DESCRIPTION\r\nThis plugin provides commands and functions to set up regions in the current\r\nbuffer that either use a syntax different from the buffer's 'filetype', or\r\ncompletely ignore the syntax.\r\n\r\nSEE ALSO\r\n- If you also want different buffer options (like indent settings, etc.) for\r\n  each syntax region, the OnSyntaxChange.vim plugin (vimscript #4085) allows\r\n  you to dynamically change the buffer options as you move through the buffer.\r\n\r\nRELATED WORKS\r\n- If the highlighting doesn't work properly, you could alternatively edit the\r\n  range(s) in a separate scratch buffer. Plugins like NrrwRgn (vimscript #3075)\r\n  provide commands to set these up, with automatic syncing back to the\r\n  original buffer.\r\n\r\nSOURCE\r\nThe code to include a different syntax in a region is based on\r\n    http:\/\/vim.wikia.com\/wiki\/Different_syntax_highlighting_within_regions_of_a_file\r\n\r\nUSAGE\r\nFor quick, ad-hoc manipulation of the syntax withing a range of lines, the\r\nfollowing commands are provided:\r\n\r\n:[range]SyntaxIgnore    Ignore the buffer's filetype syntax for the current\r\n                        line \/ lines in [range]. (Top-level keywords will\r\n                        still be highlighted.)\r\n                        This can be a useful fix when some text fragments\r\n                        confuse the syntax highlighting. (For example, when\r\n                        buffer syntax set to an inlined here-document is\r\n                        negatively affected by the foreign code surrounding\r\n                        the here-document.)\r\n\r\n:[range]SyntaxInclude {filetype}\r\n                        Use the {filetype} syntax for the current line \/ lines\r\n                        in [range].\r\n\r\n                        Line numbers in [range] are fixed; i.e. they do not\r\n                        adapt to inserted \/ deleted lines. But when in a\r\n                        range, the last line ($) is interpreted as \"end of\r\n                        file\".\r\n\r\nFor finer control and use in custom mappings or syntax tweaks, the following\r\nfunctions can be used. You'll find the details directly in the\r\n.vim\/autoload\/SyntaxRange.vim implementation file.\r\n\r\nSyntaxRange#Include( startPattern, endPattern, filetype, ... )\r\n                        Use the {filetype} syntax for the region defined by\r\n                        {startPattern} and {endPattern}.\r\nSyntaxRange#IncludeEx( regionDefinition, filetype )\r\n                        Use the {filetype} syntax for the region defined by\r\n                        {regionDefinition}.\r\n\r\nEXAMPLE\r\nTo highlight the text between the markers\r\n    @begin=c@\r\n    int i = 42;\r\n    @end=c@\r\nwith C syntax, and make the markers themselves fade into the background:\r\n    :call SyntaxRange#Include('@begin=c@', '@end=c@', 'c', 'NonText')\r\n\r\nTo highlight inline patches inside emails:\r\n    :call SyntaxRange#IncludeEx('start=\"^changeset\\|^Index: \\|^diff \\|^--- .*\\%( ----\\)\\@<!$\" skip=\"^[-+@       ]\" end=\"^$\"', 'diff')\r\nTo install this automatically for the \"mail\" filetype, put above line into a\r\nscript in ~\/.vim\/after\/syntax\/mail\/SyntaxInclude.vim","install_details":"INSTALLATION\r\nThe code is hosted in a Git repo at\r\n    https:\/\/github.com\/inkarkat\/vim-SyntaxRange\r\nYou can use your favorite plugin manager, or \"git clone\" into a directory used\r\nfor Vim packages. Releases are on the \"stable\" branch, the latest unstable\r\ndevelopment snapshot on \"master\".\r\n\r\nThis script is also packaged as a vimball. If you have the \"gunzip\"\r\ndecompressor in your PATH, simply edit the *.vmb.gz package in Vim; otherwise,\r\ndecompress the archive first, e.g. using WinZip. Inside Vim, install by\r\nsourcing the vimball or via the :UseVimball command.\r\n    vim SyntaxRange*.vmb.gz\r\n    :so %\r\nTo uninstall, use the :RmVimball command.\r\n\r\nDEPENDENCIES\r\n- Requires Vim 7.0 or higher.\r\n- Requires the ingo-library.vim plugin (vimscript #4433), version 1.022 or\r\n  higher.\r\n\r\nINTEGRATION\r\nTo automatically include a syntax in a certain {filetype}, you can put the\r\ncommand into a script in\r\n    ~\/.vim\/after\/syntax\/{filetype}\/SyntaxInclude.vim\r\nIf you want to include a syntax in several (or even all) syntaxes, you can put\r\nthis into your vimrc:\r\n    :autocmd Syntax * call SyntaxRange#Include(...)\r\n\r\nIf you have a filetype1 syntax that includes filetype2 and vice versa, you\r\nwill run into E169: Command too recursive. This can be solved by inclusion\r\nguards around each invocation. In ~\/.vim\/after\/syntax\/filetype1.vim:\r\n    let b:loaded_filetype1_syntax_includes = 1\r\n    if !exists('b:loaded_filetype2_syntax_includes')\r\n        call SyntaxRange#Include('...', '...', 'filetype2')\r\n    endif\r\n    ...\r\n    unlet b:loaded_filetype1_syntax_includes\r\nAnd the inverse in ~\/.vim\/after\/syntax\/filetype2.vim:\r\n    let b:loaded_filetype2_syntax_includes = 1\r\n    if !exists('b:loaded_filetype1_syntax_includes')\r\n        call SyntaxRange#Include('...', '...', 'filetype1')\r\n    endif\r\n    ...\r\n    unlet b:loaded_filetype2_syntax_includes","5":"INSTALLATION\r\nThe code is hosted in a Git repo at\r\n    https:\/\/github.com\/inkarkat\/vim-SyntaxRange\r\nYou can use your favorite plugin manager, or \"git clone\" into a directory used\r\nfor Vim packages. Releases are on the \"stable\" branch, the latest unstable\r\ndevelopment snapshot on \"master\".\r\n\r\nThis script is also packaged as a vimball. If you have the \"gunzip\"\r\ndecompressor in your PATH, simply edit the *.vmb.gz package in Vim; otherwise,\r\ndecompress the archive first, e.g. using WinZip. Inside Vim, install by\r\nsourcing the vimball or via the :UseVimball command.\r\n    vim SyntaxRange*.vmb.gz\r\n    :so %\r\nTo uninstall, use the :RmVimball command.\r\n\r\nDEPENDENCIES\r\n- Requires Vim 7.0 or higher.\r\n- Requires the ingo-library.vim plugin (vimscript #4433), version 1.022 or\r\n  higher.\r\n\r\nINTEGRATION\r\nTo automatically include a syntax in a certain {filetype}, you can put the\r\ncommand into a script in\r\n    ~\/.vim\/after\/syntax\/{filetype}\/SyntaxInclude.vim\r\nIf you want to include a syntax in several (or even all) syntaxes, you can put\r\nthis into your vimrc:\r\n    :autocmd Syntax * call SyntaxRange#Include(...)\r\n\r\nIf you have a filetype1 syntax that includes filetype2 and vice versa, you\r\nwill run into E169: Command too recursive. This can be solved by inclusion\r\nguards around each invocation. In ~\/.vim\/after\/syntax\/filetype1.vim:\r\n    let b:loaded_filetype1_syntax_includes = 1\r\n    if !exists('b:loaded_filetype2_syntax_includes')\r\n        call SyntaxRange#Include('...', '...', 'filetype2')\r\n    endif\r\n    ...\r\n    unlet b:loaded_filetype1_syntax_includes\r\nAnd the inverse in ~\/.vim\/after\/syntax\/filetype2.vim:\r\n    let b:loaded_filetype2_syntax_includes = 1\r\n    if !exists('b:loaded_filetype1_syntax_includes')\r\n        call SyntaxRange#Include('...', '...', 'filetype1')\r\n    endif\r\n    ...\r\n    unlet b:loaded_filetype2_syntax_includes","first_name":"Ingo","6":"Ingo","last_name":"Karkat","7":"Karkat","releases":[{"0":"4168","vim_version":"7.0","1":"7.0","script_version":"1.03","2":"1.03","version_comment":"- SyntaxRange#Include(): Escape double quotes in a:startPattern and a:endPattern; i.e. handle the patterns transparently. Found in tmsanrinsha's fork.\r\n- ENH: Avoid to re-include same syntax file if multiple ranges are specified with :SyntaxInclude \/ if SyntaxRange#Include[Ex]() is invoked multiple times per buffer. Found in tmsanrinsha's fork.","3":"- SyntaxRange#Include(): Escape double quotes in a:startPattern and a:endPattern; i.e. handle the patterns transparently. Found in tmsanrinsha's fork.\r\n- ENH: Avoid to re-include same syntax file if multiple ranges are specified with :SyntaxInclude \/ if SyntaxRange#Include[Ex]() is invoked multiple times per buffer. Found in tmsanrinsha's fork.","package":"SyntaxRange-1.03.vmb.gz","4":"SyntaxRange-1.03.vmb.gz","src_id":"25372","5":"25372","creation_date":"1499097843","6":"1499097843"},{"0":"4168","vim_version":"7.0","1":"7.0","script_version":"1.02","2":"1.02","version_comment":"- Set main_syntax to the buffer's syntax during :syntax include of the subordinate syntax script. Some scripts may make special arrangements when included. Suggested by OOO.\r\n- Handle :.SyntaxInclude and :.SyntaxIgnore on folded lines correctly. Use ingo#range#NetStart\/End().\r\n- Add dependency to ingo-library (vimscript #4433). *** You need to separately install ingo-library (vimscript #4433) version 1.022 (or higher)! ***","3":"- Set main_syntax to the buffer's syntax during :syntax include of the subordinate syntax script. Some scripts may make special arrangements when included. Suggested by OOO.\r\n- Handle :.SyntaxInclude and :.SyntaxIgnore on folded lines correctly. Use ingo#range#NetStart\/End().\r\n- Add dependency to ingo-library (vimscript #4433). *** You need to separately install ingo-library (vimscript #4433) version 1.022 (or higher)! ***","package":"SyntaxRange-1.02.vmb.gz","4":"SyntaxRange-1.02.vmb.gz","src_id":"23217","5":"23217","creation_date":"1429789552","6":"1429789552"},{"0":"4168","vim_version":"7.0","1":"7.0","script_version":"1.01","2":"1.01","version_comment":"Avoid \"E108: No such variable: b:current_syntax\" when the (misbehaving) included syntax doesn't set it. Reported by o2genum at http:\/\/stackoverflow.com\/a\/16162412\/813602.","3":"Avoid \"E108: No such variable: b:current_syntax\" when the (misbehaving) included syntax doesn't set it. Reported by o2genum at http:\/\/stackoverflow.com\/a\/16162412\/813602.","package":"SyntaxRange-1.01.vmb.gz","4":"SyntaxRange-1.01.vmb.gz","src_id":"21088","5":"21088","creation_date":"1385040793","6":"1385040793"},{"0":"4168","vim_version":"7.0","1":"7.0","script_version":"1.00","2":"1.00","version_comment":"Initial upload","3":"Initial upload","package":"SyntaxRange.vba.gz","4":"SyntaxRange.vba.gz","src_id":"18399","5":"18399","creation_date":"1344847175","6":"1344847175"}]},"4167":{"script_id":"4167","0":"4167","script_name":"Area search","1":"Area search","script_type":"utility","2":"utility","summary":"Search for area containing keywords","3":"Search for area containing keywords","description":"A","4":"A","install_details":"A","5":"A","first_name":"G","6":"G","last_name":"A","7":"A","releases":[{"0":"4167","vim_version":"7.3","1":"7.3","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"area_search.vim","4":"area_search.vim","src_id":"18391","5":"18391","creation_date":"1344750837","6":"1344750837"}]},"4166":{"script_id":"4166","0":"4166","script_name":"locator","1":"locator","script_type":"utility","2":"utility","summary":"Shows where is your cursor, including folds, classes, functions, and more.","3":"Shows where is your cursor, including folds, classes, functions, and more.","description":"Plugin that shows you full \"path\" to the cursor, including folds, classes, functions, and more.\r\n\r\nThere are already several plugins on http:\/\/www.vim.org that show you name of the\r\nfunction that cursor is currently in, but I want to see full \"path\" to the\r\ncursor, including folds, classes, and maybe comment sections.\r\n\r\nScreenshots: \r\n   http:\/\/goo.gl\/nFW8S (test C file with folds and functions)\r\n   http:\/\/goo.gl\/GRMAB (test C file with comment sections, folds and functions)\r\n   http:\/\/goo.gl\/9rVfJ (Java file with sections, functions and nested classes)\r\n   http:\/\/goo.gl\/fTjpF (C file with folds, sections and functions)\r\n   http:\/\/goo.gl\/lbgSh (C++ class declaration, i.e. header file)\r\n   http:\/\/goo.gl\/G7O7U (C++ source file)\r\n\r\nRead the docs in HTML format there: http:\/\/goo.gl\/8EqCI\r\n\r\n========================================================================\r\n\r\nAutogenerated git repository: https:\/\/github.com\/vim-scripts\/locator (Note that this repository is auto-generated by http:\/\/vim-scripts.org as a mirror of http:\/\/www.vim.org) ","4":"Plugin that shows you full \"path\" to the cursor, including folds, classes, functions, and more.\r\n\r\nThere are already several plugins on http:\/\/www.vim.org that show you name of the\r\nfunction that cursor is currently in, but I want to see full \"path\" to the\r\ncursor, including folds, classes, and maybe comment sections.\r\n\r\nScreenshots: \r\n   http:\/\/goo.gl\/nFW8S (test C file with folds and functions)\r\n   http:\/\/goo.gl\/GRMAB (test C file with comment sections, folds and functions)\r\n   http:\/\/goo.gl\/9rVfJ (Java file with sections, functions and nested classes)\r\n   http:\/\/goo.gl\/fTjpF (C file with folds, sections and functions)\r\n   http:\/\/goo.gl\/lbgSh (C++ class declaration, i.e. header file)\r\n   http:\/\/goo.gl\/G7O7U (C++ source file)\r\n\r\nRead the docs in HTML format there: http:\/\/goo.gl\/8EqCI\r\n\r\n========================================================================\r\n\r\nAutogenerated git repository: https:\/\/github.com\/vim-scripts\/locator (Note that this repository is auto-generated by http:\/\/vim-scripts.org as a mirror of http:\/\/www.vim.org) ","install_details":"There is an optional dependency: plugin matchit ( vimscript #39 ), it is needed for *.vim files (Locator doesn't work with *.vim files without matchit), and also needed for better handling of c\/cpp\/java files.\r\n\r\nUse pathogen.","5":"There is an optional dependency: plugin matchit ( vimscript #39 ), it is needed for *.vim files (Locator doesn't work with *.vim files without matchit), and also needed for better handling of c\/cpp\/java files.\r\n\r\nUse pathogen.","first_name":"Dmitry","6":"Dmitry","last_name":"Frank","7":"Frank","releases":[{"0":"4166","vim_version":"7.0","1":"7.0","script_version":"1.3","2":"1.3","version_comment":"Added C++ support. Screenshots:\r\nhttp:\/\/goo.gl\/lbgSh (C++ header file)\r\nhttp:\/\/goo.gl\/G7O7U (C++ source file)\r\n","3":"Added C++ support. Screenshots:\r\nhttp:\/\/goo.gl\/lbgSh (C++ header file)\r\nhttp:\/\/goo.gl\/G7O7U (C++ source file)\r\n","package":"locator-1.3.zip","4":"locator-1.3.zip","src_id":"19026","5":"19026","creation_date":"1353848162","6":"1353848162"},{"0":"4166","vim_version":"7.0","1":"7.0","script_version":"1.2","2":"1.2","version_comment":"Resolved issues with folded buffers (you can read about these issues in previous versions of locator, :help locator-known-issues)","3":"Resolved issues with folded buffers (you can read about these issues in previous versions of locator, :help locator-known-issues)","package":"locator.zip","4":"locator.zip","src_id":"18420","5":"18420","creation_date":"1345199350","6":"1345199350"},{"0":"4166","vim_version":"7.0","1":"7.0","script_version":"1.01","2":"1.01","version_comment":"Little bugfixes.","3":"Little bugfixes.","package":"locator.zip","4":"locator.zip","src_id":"18390","5":"18390","creation_date":"1344720386","6":"1344720386"},{"0":"4166","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"locator.zip","4":"locator.zip","src_id":"18389","5":"18389","creation_date":"1344718153","6":"1344718153"}]},"4165":{"script_id":"4165","0":"4165","script_name":"directoryBrowser","1":"directoryBrowser","script_type":"utility","2":"utility","summary":"Directory listing and file operations in vim (replaced by vimExplorer)","3":"Directory listing and file operations in vim (replaced by vimExplorer)","description":"See latest version on github: https:\/\/github.com\/viaa\/VimPlugins\r\n\r\nThis plugin which was a Windows-only plugin, is now replaced by another plugin (written from scratch) called vimExplorer which uses the ls commands and is a much improved version of directoryBrowser. It works for Linux and on Windows using the cygwin or UnxUtils ls command.\r\n\r\nIf you insist using directoryBrowser for Windows, you may download it from this page, but I will not update new versions of it. I suggest to use vimExplorer instead: http:\/\/www.vim.org\/scripts\/script.php?script_id=4360","4":"See latest version on github: https:\/\/github.com\/viaa\/VimPlugins\r\n\r\nThis plugin which was a Windows-only plugin, is now replaced by another plugin (written from scratch) called vimExplorer which uses the ls commands and is a much improved version of directoryBrowser. It works for Linux and on Windows using the cygwin or UnxUtils ls command.\r\n\r\nIf you insist using directoryBrowser for Windows, you may download it from this page, but I will not update new versions of it. I suggest to use vimExplorer instead: http:\/\/www.vim.org\/scripts\/script.php?script_id=4360","install_details":"","5":"","first_name":"Alexandre","6":"Alexandre","last_name":"Viau","7":"Viau","releases":[{"0":"4165","vim_version":"7.0","1":"7.0","script_version":"5.0","2":"5.0","version_comment":"- Added directory marks like similar to marks in vim using the m key but to mark directories instead of positions in files and ' or ` or ; to return to that directory. The maps are automatically activated on a directory listing. For example, press mw to mark the c:\\windows directory, then do 'w (or `w or ;w) to return to that directory. All letters may be used from a to z, A to Z and 0 to 9. Press '' to view a list of all the bookmarked directories sorted by mark, or press ;; to view the same list but sorted by paths. When '' or ;; is pressed, the list is shown and a mark is asked as input to goto to its directory, this is another way that marks are used.\r\n- New functions to save data to a configuration files, used by the directory marking feature, it allows for now to save the marked directories.\r\n","3":"- Added directory marks like similar to marks in vim using the m key but to mark directories instead of positions in files and ' or ` or ; to return to that directory. The maps are automatically activated on a directory listing. For example, press mw to mark the c:\\windows directory, then do 'w (or `w or ;w) to return to that directory. All letters may be used from a to z, A to Z and 0 to 9. Press '' to view a list of all the bookmarked directories sorted by mark, or press ;; to view the same list but sorted by paths. When '' or ;; is pressed, the list is shown and a mark is asked as input to goto to its directory, this is another way that marks are used.\r\n- New functions to save data to a configuration files, used by the directory marking feature, it allows for now to save the marked directories.\r\n","package":"directoryBrowser.vim","4":"directoryBrowser.vim","src_id":"19062","5":"19062","creation_date":"1354192181","6":"1354192181"},{"0":"4165","vim_version":"7.0","1":"7.0","script_version":"4.4.3","2":"4.4.3","version_comment":"\" 4.4.3     - Removed <space>f2 to find files, there was already <space>f3 mapped to find files.\r\n\"           - Removed an extra tabe in dirFind and dirGrep functions that opened an extra tab for nothing.\r\n\"           - Modified paths in the dirFind and dirGrep functions\r\n","3":"\" 4.4.3     - Removed <space>f2 to find files, there was already <space>f3 mapped to find files.\r\n\"           - Removed an extra tabe in dirFind and dirGrep functions that opened an extra tab for nothing.\r\n\"           - Modified paths in the dirFind and dirGrep functions\r\n","package":"directoryBrowser.vim","4":"directoryBrowser.vim","src_id":"19004","5":"19004","creation_date":"1353487111","6":"1353487111"},{"0":"4165","vim_version":"7.0","1":"7.0","script_version":"4.4.2","2":"4.4.2","version_comment":"Changed the file format to unix","3":"Changed the file format to unix","package":"directoryBrowser.vim","4":"directoryBrowser.vim","src_id":"18994","5":"18994","creation_date":"1353328663","6":"1353328663"},{"0":"4165","vim_version":"7.0","1":"7.0","script_version":"4.4.1","2":"4.4.1","version_comment":"- open file with browser.vim plugin that use the links browser as an external tool\r\n- change mapping \\ key by <enter> because \\ is may be often used in other plugins\r\n","3":"- open file with browser.vim plugin that use the links browser as an external tool\r\n- change mapping \\ key by <enter> because \\ is may be often used in other plugins\r\n","package":"directoryBrowser.vim","4":"directoryBrowser.vim","src_id":"18985","5":"18985","creation_date":"1353154797","6":"1353154797"},{"0":"4165","vim_version":"7.0","1":"7.0","script_version":"4.4","2":"4.4","version_comment":"Small modification to the search string for finding previously browsed directory.\r\n","3":"Small modification to the search string for finding previously browsed directory.\r\n","package":"directoryBrowser.vim","4":"directoryBrowser.vim","src_id":"18609","5":"18609","creation_date":"1347698691","6":"1347698691"},{"0":"4165","vim_version":"7.0","1":"7.0","script_version":"4.3 ","2":"4.3 ","version_comment":"- Corrected bug concerning the @H browsing history register.\r\n- Corrected issues with cursor position on previously browsed files and directory.\r\n-  Corrected bug when first time vim opened and directory listed, there was an error message saying that empty dictionnary, that is because no directory was browsed so the variables to index the dictionnary were empty.\r\n-  Small amelioration of the isDir() detection function, added \\s\\{4\\} to the time regex. I add problems with a file menu that this function was detecting as a directory listing but it was not.\r\n-  Two commands added to the compile\/run sample menu in the help section, these 2 commands are to source a vim script and source a vim macro.","3":"- Corrected bug concerning the @H browsing history register.\r\n- Corrected issues with cursor position on previously browsed files and directory.\r\n-  Corrected bug when first time vim opened and directory listed, there was an error message saying that empty dictionnary, that is because no directory was browsed so the variables to index the dictionnary were empty.\r\n-  Small amelioration of the isDir() detection function, added \\s\\{4\\} to the time regex. I add problems with a file menu that this function was detecting as a directory listing but it was not.\r\n-  Two commands added to the compile\/run sample menu in the help section, these 2 commands are to source a vim script and source a vim macro.","package":"directoryBrowser.vim","4":"directoryBrowser.vim","src_id":"18586","5":"18586","creation_date":"1347431169","6":"1347431169"},{"0":"4165","vim_version":"7.0","1":"7.0","script_version":"4.2","2":"4.2","version_comment":"Modified <space>h, <space>l behavior. Added the ability to remember last position of the cursor in a directory so that if a user returns to a previously browsed directory, the cursor will position itself to the file it was last time in that directory.","3":"Modified <space>h, <space>l behavior. Added the ability to remember last position of the cursor in a directory so that if a user returns to a previously browsed directory, the cursor will position itself to the file it was last time in that directory.","package":"directoryBrowser.vim","4":"directoryBrowser.vim","src_id":"18579","5":"18579","creation_date":"1347265545","6":"1347265545"},{"0":"4165","vim_version":"7.0","1":"7.0","script_version":"4.1","2":"4.1","version_comment":"- Fixed 2 places in code (in dirDelete and recursive grep) that were not changed to use the path variables.\r\n- Added <space><enter> open utl link under cursor (utl plugin required)","3":"- Fixed 2 places in code (in dirDelete and recursive grep) that were not changed to use the path variables.\r\n- Added <space><enter> open utl link under cursor (utl plugin required)","package":"directoryBrowser.vim","4":"directoryBrowser.vim","src_id":"18559","5":"18559","creation_date":"1347003527","6":"1347003527"},{"0":"4165","vim_version":"7.0","1":"7.0","script_version":"4.0","2":"4.0","version_comment":"- 2012-09-04 11:43:43 (mar.) Changes to many code not to use registers to keep paths info, but global variables instead. These global variables may be used anywhere in vim, and if the registers are needed to paste path information, do <space>p to copy the path info from the variables to the registers. Now registers will not be overwritten by the plugin except for the @H register which contains the browsing history.\r\n- 2012-09-04 11:45:27 (mar.) There are new global variables similar to the variable to keep path info, but they keep the previous file path info. This is used to execute actions from one window or tab to another, one example is the contextual menu, other example may be project files with link to compile, run etc.\r\n- 2012-09-03 11:05:17 (lun.) Modified <space>M now the contextual menu is very useful as it opens in a split window and may execute actions on the file where the cursor was before switching to the menu window. That file may be a file in edition or a directory listing. So instead of copying links at the top of the file like in previous versions of the plugin, now the menu is opened in a split window (or a tab). It is still possible to put links at the top of files if the links are specific to the file, but it is more convenient to have it in a split window. Autocommands onEnter and onLeave window\/tab where added to make this possible, these autocommands copy the paths when entering or leaving a window\/tab and keep the previous path in registers and if the file moved to is the menu file, the current file path registers do not contain the path of the menu file like other files but they contain the path of the previous file, so that it may be used for lauching actions on the previous file be it a file in edition or a file in a directory listing.\r\n- 2012-09-03 23:25:23 (lun.) I included a big part of my own to-date contextual menu as an example in this plugin usage section. This one works with the new modifications concerning the menu file displayed in a window\/tab.\r\n- 2012-09-04 00:18:07 (mar.) The paths are not copied anymore to the registers at each operations, only when the user presses <space>p the paths are copied to register for pasting. \r\n- 2012-08-31 05:36:44 (ven.) Modified <space><esc> to execute the command in the current path of the current directory listing if no path specified.\r\n- 2012-08-31 05:41:22 (ven.) Modified <space>i and <space>m to changed copy the path at the same time the listing is changed and to change vim's directory to the copied directory.","3":"- 2012-09-04 11:43:43 (mar.) Changes to many code not to use registers to keep paths info, but global variables instead. These global variables may be used anywhere in vim, and if the registers are needed to paste path information, do <space>p to copy the path info from the variables to the registers. Now registers will not be overwritten by the plugin except for the @H register which contains the browsing history.\r\n- 2012-09-04 11:45:27 (mar.) There are new global variables similar to the variable to keep path info, but they keep the previous file path info. This is used to execute actions from one window or tab to another, one example is the contextual menu, other example may be project files with link to compile, run etc.\r\n- 2012-09-03 11:05:17 (lun.) Modified <space>M now the contextual menu is very useful as it opens in a split window and may execute actions on the file where the cursor was before switching to the menu window. That file may be a file in edition or a directory listing. So instead of copying links at the top of the file like in previous versions of the plugin, now the menu is opened in a split window (or a tab). It is still possible to put links at the top of files if the links are specific to the file, but it is more convenient to have it in a split window. Autocommands onEnter and onLeave window\/tab where added to make this possible, these autocommands copy the paths when entering or leaving a window\/tab and keep the previous path in registers and if the file moved to is the menu file, the current file path registers do not contain the path of the menu file like other files but they contain the path of the previous file, so that it may be used for lauching actions on the previous file be it a file in edition or a file in a directory listing.\r\n- 2012-09-03 23:25:23 (lun.) I included a big part of my own to-date contextual menu as an example in this plugin usage section. This one works with the new modifications concerning the menu file displayed in a window\/tab.\r\n- 2012-09-04 00:18:07 (mar.) The paths are not copied anymore to the registers at each operations, only when the user presses <space>p the paths are copied to register for pasting. \r\n- 2012-08-31 05:36:44 (ven.) Modified <space><esc> to execute the command in the current path of the current directory listing if no path specified.\r\n- 2012-08-31 05:41:22 (ven.) Modified <space>i and <space>m to changed copy the path at the same time the listing is changed and to change vim's directory to the copied directory.","package":"directoryBrowser.vim","4":"directoryBrowser.vim","src_id":"18548","5":"18548","creation_date":"1346781375","6":"1346781375"},{"0":"4165","vim_version":"7.0","1":"7.0","script_version":"3.3","2":"3.3","version_comment":"- <space>J show browsing history (show list of paths and files browsed in this session. Useful to go back to previously browsed directories even to go return to directories of files that were opened or run etc. The list may be saved with the <space>w command. Utl plugin required.\r\n- Removed a tab character that was invisible after the <space>z command","3":"- <space>J show browsing history (show list of paths and files browsed in this session. Useful to go back to previously browsed directories even to go return to directories of files that were opened or run etc. The list may be saved with the <space>w command. Utl plugin required.\r\n- Removed a tab character that was invisible after the <space>z command","package":"directoryBrowser.vim","4":"directoryBrowser.vim","src_id":"18515","5":"18515","creation_date":"1346346038","6":"1346346038"},{"0":"4165","vim_version":"7.0","1":"7.0","script_version":"3.2","2":"3.2","version_comment":"- Modified the behavior of the <space>C command, in some cases it was not changing to the directory","3":"- Modified the behavior of the <space>C command, in some cases it was not changing to the directory","package":"directoryBrowser.vim","4":"directoryBrowser.vim","src_id":"18498","5":"18498","creation_date":"1346074338","6":"1346074338"},{"0":"4165","vim_version":"7.0","1":"7.0","script_version":"3.1","2":"3.1","version_comment":"- Don't use version 3.0, use version 3.1 instead.\r\n- <space><tab> open default 'browsing history' file called 'dirlist_', useful for fast browsing\r\n","3":"- Don't use version 3.0, use version 3.1 instead.\r\n- <space><tab> open default 'browsing history' file called 'dirlist_', useful for fast browsing\r\n","package":"directoryBrowser.vim","4":"directoryBrowser.vim","src_id":"18497","5":"18497","creation_date":"1346044318","6":"1346044318"},{"0":"4165","vim_version":"7.0","1":"7.0","script_version":"3","2":"3","version_comment":"- \\a to \\z list a:\\ to z:\\ root directories in current buffer (appended)\r\n- \\A to \\Z list a:\\ to z:\\ root directories in new buffer\r\n- -a to -z list a:\\ to z:\\ root directories in split window\r\n- -A to -Z list a:\\ to z:\\ root directories in vertical split window\r\n- =a to =z list a:\\ to z:\\ root directories in new tab\r\n- f\/ Change backslash to forwardslash on the current line\r\n- f<Bslash> Change forwardslash to backslash on the current line\r\n- ff<Bslash> Change backslash to double backslash on the current line\r\n- fff<Bslash> Change forwardslash to double backslash on the current line\r\n- ffff<Bslash> Change doublebackslash to backslash the current line\r\n- <space><f5> copy current file's path+filename relative to current directory with backslash\r\n- <space><f6> copy current file's path+filename relative to current directory with forward slash\r\n- <space><f7> copy current file's path only (with backslash)\r\n- <space><f8> copy current file's path only (with forward slash)\r\n- <space><f9> copy current file's filename only (without path)\r\n- <space><f10> copy current file's path+filename relative to current directory with the line number (in utl format)\r\n- <space>! Layout 1 (2 vertical panes)\r\n- <space>@ Layout 2 (2 horizontal panes)\r\n- <space># Layout 3 (3 panes: 2 vertical, 1 horizontal)\r\n- <space>$ Layout 4 (4 panes)\r\n- <space>^ Layout 6 (6 panes)\r\n- <space>* Layout 8 (8 panes)\r\n- <space>) Layout 10 (10 panes)\r\n- <space>- toggle show file owner\r\n- <space>0 to change directory attributes\r\n- <space>9 to change directory time display and sorting\r\n- <space>a interchanged with <space>A\r\n- <space>b changed list buffers to open in new tab instead of opening in current tab (not related to directory browsing but useful. Requires utl.vim)\r\n- <space>I open file in internet explorer\r\n- <space>L to list current directory and its subdirectories recursively\r\n- <space>M open a \"contextual menu\" to run operations on files (requires the utl plugin)\r\n- <space>n new file in new tab\r\n- <space>N new file in current tab\r\n- <space>O open file in notepad\r\n- <space>q show available volumes\r\n- <space>Q show available volumes with names and details about shares and computers\r\n- <space>T open directory in new tab\r\n- <space>u open filename in clipboard current tab\r\n- <space>U open filename in clipboard in new tab\r\n- <space>w to save (append) directory listing to disk (useful for shorcuts)\r\n- <space>W to save (overwrite) directory listing to disk\r\n- <space>X to show directory and subdirectories structure of current directory using the \"tree\" command\r\n- <space>y list the directory of the path in clipboard (with or without filename) in a new split window\r\n- <space>Y list the directory of the path in clipboard (with or without filename) in the current buffer\r\n- <space>z open utl link under cursor in a split window (utl plugin required)\r\n- <space>Z open utl link under cursor in tab (utl plugin required)\r\n- Remove dirOfStr language requirement. Searching for a language specific string was not needed. \r\n- Changes with cursor position and listing position specially using <space>i and <space>m. \r\n- Set g:dir instead of g:dirBuf as defaut when doing \\A..\\Z (listing drives using capital letters) with is more convenient because this way one my list content of another drive in the same buffer using the \\ shortcut key so one may have all his directory browsing inside the same buffer, with is nice if saved to file using <space>w for later viewing and continuation. \r\n- Added <space>F to list the directory of the current file\r\n- Changed behavior of <space>i \"go to previous dir listing\", now it will go to top of current dir then to previous dir if <space>i is typed a second time. \r\n- Modified search string to find current directory (not to conflict with the directory showned by the tree command)\r\n- uu, uuu, uuuu, uuuuu, UU, UUU, UUUU, uur abbreviations used with the utl plugin to insert links and references\r\n","3":"- \\a to \\z list a:\\ to z:\\ root directories in current buffer (appended)\r\n- \\A to \\Z list a:\\ to z:\\ root directories in new buffer\r\n- -a to -z list a:\\ to z:\\ root directories in split window\r\n- -A to -Z list a:\\ to z:\\ root directories in vertical split window\r\n- =a to =z list a:\\ to z:\\ root directories in new tab\r\n- f\/ Change backslash to forwardslash on the current line\r\n- f<Bslash> Change forwardslash to backslash on the current line\r\n- ff<Bslash> Change backslash to double backslash on the current line\r\n- fff<Bslash> Change forwardslash to double backslash on the current line\r\n- ffff<Bslash> Change doublebackslash to backslash the current line\r\n- <space><f5> copy current file's path+filename relative to current directory with backslash\r\n- <space><f6> copy current file's path+filename relative to current directory with forward slash\r\n- <space><f7> copy current file's path only (with backslash)\r\n- <space><f8> copy current file's path only (with forward slash)\r\n- <space><f9> copy current file's filename only (without path)\r\n- <space><f10> copy current file's path+filename relative to current directory with the line number (in utl format)\r\n- <space>! Layout 1 (2 vertical panes)\r\n- <space>@ Layout 2 (2 horizontal panes)\r\n- <space># Layout 3 (3 panes: 2 vertical, 1 horizontal)\r\n- <space>$ Layout 4 (4 panes)\r\n- <space>^ Layout 6 (6 panes)\r\n- <space>* Layout 8 (8 panes)\r\n- <space>) Layout 10 (10 panes)\r\n- <space>- toggle show file owner\r\n- <space>0 to change directory attributes\r\n- <space>9 to change directory time display and sorting\r\n- <space>a interchanged with <space>A\r\n- <space>b changed list buffers to open in new tab instead of opening in current tab (not related to directory browsing but useful. Requires utl.vim)\r\n- <space>I open file in internet explorer\r\n- <space>L to list current directory and its subdirectories recursively\r\n- <space>M open a \"contextual menu\" to run operations on files (requires the utl plugin)\r\n- <space>n new file in new tab\r\n- <space>N new file in current tab\r\n- <space>O open file in notepad\r\n- <space>q show available volumes\r\n- <space>Q show available volumes with names and details about shares and computers\r\n- <space>T open directory in new tab\r\n- <space>u open filename in clipboard current tab\r\n- <space>U open filename in clipboard in new tab\r\n- <space>w to save (append) directory listing to disk (useful for shorcuts)\r\n- <space>W to save (overwrite) directory listing to disk\r\n- <space>X to show directory and subdirectories structure of current directory using the \"tree\" command\r\n- <space>y list the directory of the path in clipboard (with or without filename) in a new split window\r\n- <space>Y list the directory of the path in clipboard (with or without filename) in the current buffer\r\n- <space>z open utl link under cursor in a split window (utl plugin required)\r\n- <space>Z open utl link under cursor in tab (utl plugin required)\r\n- Remove dirOfStr language requirement. Searching for a language specific string was not needed. \r\n- Changes with cursor position and listing position specially using <space>i and <space>m. \r\n- Set g:dir instead of g:dirBuf as defaut when doing \\A..\\Z (listing drives using capital letters) with is more convenient because this way one my list content of another drive in the same buffer using the \\ shortcut key so one may have all his directory browsing inside the same buffer, with is nice if saved to file using <space>w for later viewing and continuation. \r\n- Added <space>F to list the directory of the current file\r\n- Changed behavior of <space>i \"go to previous dir listing\", now it will go to top of current dir then to previous dir if <space>i is typed a second time. \r\n- Modified search string to find current directory (not to conflict with the directory showned by the tree command)\r\n- uu, uuu, uuuu, uuuuu, UU, UUU, UUUU, uur abbreviations used with the utl plugin to insert links and references\r\n","package":"directoryBrowser.vim","4":"directoryBrowser.vim","src_id":"18495","5":"18495","creation_date":"1346001093","6":"1346001093"},{"0":"4165","vim_version":"7.0","1":"7.0","script_version":"2","2":"2","version_comment":"I modified the number of caracters to read between the beginning of line and the filename, in win2000 it was 39, in xp\/7 36, I set it to 36 because I assume most people use on of these versions.","3":"I modified the number of caracters to read between the beginning of line and the filename, in win2000 it was 39, in xp\/7 36, I set it to 36 because I assume most people use on of these versions.","package":"directoryBrowser.vim","4":"directoryBrowser.vim","src_id":"18387","5":"18387","creation_date":"1344613315","6":"1344613315"},{"0":"4165","vim_version":"7.0","1":"7.0","script_version":"1","2":"1","version_comment":"Initial upload","3":"Initial upload","package":"directoryBrowser.vim","4":"directoryBrowser.vim","src_id":"18386","5":"18386","creation_date":"1344524990","6":"1344524990"}]},"4164":{"script_id":"4164","0":"4164","script_name":"hybrid.vim","1":"hybrid.vim","script_type":"color scheme","2":"color scheme","summary":"A dark colourscheme combining Jellybeans, Solarized and Tomorrow-Night","3":"A dark colourscheme combining Jellybeans, Solarized and Tomorrow-Night","description":"A dark colourscheme for Vim that combines the:\r\n-   Colour palette from Tomorrow-Night: https:\/\/github.com\/chriskempson\/vim-tomorrow-theme\r\n-   Syntax group highlighting scheme from jellybeans: https:\/\/github.com\/nanotech\/jellybeans.vim\r\n-   Vim code from solarized: https:\/\/github.com\/altercation\/vim-colors-solarized\r\n\r\nScreenshots available from:\r\n-   https:\/\/github.com\/w0ng\/vim-hybrid\r\n\r\nRecommended terminal colours: \r\n1.  Add these colours to ~\/.Xresources: \r\n    - https:\/\/gist.github.com\/3278077\r\n2.  Use Xresources colours by setting in ~\/.vimrc:\r\n        let g:hybrid_use_Xresources = 1\r\n        colorscheme hybrid\r\n\r\n","4":"A dark colourscheme for Vim that combines the:\r\n-   Colour palette from Tomorrow-Night: https:\/\/github.com\/chriskempson\/vim-tomorrow-theme\r\n-   Syntax group highlighting scheme from jellybeans: https:\/\/github.com\/nanotech\/jellybeans.vim\r\n-   Vim code from solarized: https:\/\/github.com\/altercation\/vim-colors-solarized\r\n\r\nScreenshots available from:\r\n-   https:\/\/github.com\/w0ng\/vim-hybrid\r\n\r\nRecommended terminal colours: \r\n1.  Add these colours to ~\/.Xresources: \r\n    - https:\/\/gist.github.com\/3278077\r\n2.  Use Xresources colours by setting in ~\/.vimrc:\r\n        let g:hybrid_use_Xresources = 1\r\n        colorscheme hybrid\r\n\r\n","install_details":"Copy hybrid.vim to ~\/.vim\/colors\/\r\n\r\n","5":"Copy hybrid.vim to ~\/.vim\/colors\/\r\n\r\n","first_name":"Andrew","6":"Andrew","last_name":"Wong","7":"Wong","releases":[{"0":"4164","vim_version":"7.3","1":"7.3","script_version":"1.01","2":"1.01","version_comment":"Latest version. Check github for changelog","3":"Latest version. Check github for changelog","package":"hybrid.vim","4":"hybrid.vim","src_id":"19720","5":"19720","creation_date":"1364520547","6":"1364520547"},{"0":"4164","vim_version":"7.3","1":"7.3","script_version":"1.00","2":"1.00","version_comment":"Initial upload","3":"Initial upload","package":"hybrid.vim","4":"hybrid.vim","src_id":"18385","5":"18385","creation_date":"1344500874","6":"1344500874"}]},"4163":{"script_id":"4163","0":"4163","script_name":"michael.vim","1":"michael.vim","script_type":"color scheme","2":"color scheme","summary":"A dark background color scheme with (mostly) matte colors","3":"A dark background color scheme with (mostly) matte colors","description":"\"michael\" is a dark background based color scheme with muted, less intense colors. The background color has been shamelessly copied from the \"inkpot\" color scheme. Everything else has been customized.\r\n\r\nScreenshots:\r\nC++:    http:\/\/i45.tinypic.com\/2mdqr9h.jpg\r\nJava:   http:\/\/i50.tinypic.com\/4qsxat.jpg\r\nHTML: http:\/\/i50.tinypic.com\/2w6s5l4.jpg","4":"\"michael\" is a dark background based color scheme with muted, less intense colors. The background color has been shamelessly copied from the \"inkpot\" color scheme. Everything else has been customized.\r\n\r\nScreenshots:\r\nC++:    http:\/\/i45.tinypic.com\/2mdqr9h.jpg\r\nJava:   http:\/\/i50.tinypic.com\/4qsxat.jpg\r\nHTML: http:\/\/i50.tinypic.com\/2w6s5l4.jpg","install_details":"To install, copy to ~\/.vim\/colors directory.\r\nAfter installation, enable it with :colorscheme michael\r\nThis scheme is currently meant to work with GVim only. Further versions will enable support for terminals.","5":"To install, copy to ~\/.vim\/colors directory.\r\nAfter installation, enable it with :colorscheme michael\r\nThis scheme is currently meant to work with GVim only. Further versions will enable support for terminals.","first_name":"Namit","6":"Namit","last_name":"Bhalla","7":"Bhalla","releases":[{"0":"4163","vim_version":"7.0","1":"7.0","script_version":"0.2","2":"0.2","version_comment":"File format corrected.","3":"File format corrected.","package":"michael.vim","4":"michael.vim","src_id":"18397","5":"18397","creation_date":"1344781026","6":"1344781026"},{"0":"4163","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"michael.vim","4":"michael.vim","src_id":"18379","5":"18379","creation_date":"1344459536","6":"1344459536"}]},"4162":{"script_id":"4162","0":"4162","script_name":"Simple CSS align (SCSSA)","1":"Simple CSS align (SCSSA)","script_type":"utility","2":"utility","summary":"Align selected CSS properties","3":"Align selected CSS properties","description":"Very very simple plugin which provides only one command:\r\n\r\n:SCSSA\r\n\r\nTo use it, select some lines containing CSS properties, then use the command.\r\nIt will align them. That's all :-)\r\n\r\n--- \r\n\r\nFOR A COMPLETE DOCUMENTATION, READ THE FILE HEADER: \r\nALL IS EXPLAINED AND PROBABLY MORE UP2DATE THAN ON THIS PAGE! \r\n\r\n--- \r\n\r\nIf you want to be sure having the last version of this plugin, check my github repository (in case of I forgot to update here): \r\nhttps:\/\/github.com\/webastien\/vim\/blob\/master\/vim\/plugin\/SCSSA.vim \r\n\r\nOn github, you will also find my VIm configuration. Feel free to extract parts of code you need from my sources. \r\nThis could be better but I use those for my daily works without problems and it will be improved over the time. \r\nI always miss time to refactor and clean the code, so if you want to help, you're welcome ;-)","4":"Very very simple plugin which provides only one command:\r\n\r\n:SCSSA\r\n\r\nTo use it, select some lines containing CSS properties, then use the command.\r\nIt will align them. That's all :-)\r\n\r\n--- \r\n\r\nFOR A COMPLETE DOCUMENTATION, READ THE FILE HEADER: \r\nALL IS EXPLAINED AND PROBABLY MORE UP2DATE THAN ON THIS PAGE! \r\n\r\n--- \r\n\r\nIf you want to be sure having the last version of this plugin, check my github repository (in case of I forgot to update here): \r\nhttps:\/\/github.com\/webastien\/vim\/blob\/master\/vim\/plugin\/SCSSA.vim \r\n\r\nOn github, you will also find my VIm configuration. Feel free to extract parts of code you need from my sources. \r\nThis could be better but I use those for my daily works without problems and it will be improved over the time. \r\nI always miss time to refactor and clean the code, so if you want to help, you're welcome ;-)","install_details":"    Required:\r\n  - Drop this file to your plugin directory of vim.\r\n \r\n    Optional:\r\n  - Map a key to call the \"SCSSA\" command.\r\n    To do it, add this to your .vimrc:\r\n          vmap YOURKEY :SCSSA<CR>\r\n    (where YOURKEY is the key you've choosed)\r\n \r\n    Example: vmap + :SCSSA<CR>\r\n\r\n    Eventually:                                                                                                                                       \r\n  - Sort your properties in the same time.\r\n    Add to your keymapping \"gv!YOURSORTCOMMAND<CR>\".\r\n \r\n    Example: vmap + :SCSSA<CR>gv!sort<CR>\r\n    (this exampe use the shell command \"sort\").","5":"    Required:\r\n  - Drop this file to your plugin directory of vim.\r\n \r\n    Optional:\r\n  - Map a key to call the \"SCSSA\" command.\r\n    To do it, add this to your .vimrc:\r\n          vmap YOURKEY :SCSSA<CR>\r\n    (where YOURKEY is the key you've choosed)\r\n \r\n    Example: vmap + :SCSSA<CR>\r\n\r\n    Eventually:                                                                                                                                       \r\n  - Sort your properties in the same time.\r\n    Add to your keymapping \"gv!YOURSORTCOMMAND<CR>\".\r\n \r\n    Example: vmap + :SCSSA<CR>gv!sort<CR>\r\n    (this exampe use the shell command \"sort\").","first_name":"S\u00c3\u00a9bastien","6":"S\u00c3\u00a9bastien","last_name":"<anon>","7":"<anon>","releases":[{"0":"4162","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"SCSSA.vim","4":"SCSSA.vim","src_id":"18378","5":"18378","creation_date":"1344452693","6":"1344452693"}]},"4161":{"script_id":"4161","0":"4161","script_name":"flexddpl.vim","1":"flexddpl.vim","script_type":"syntax","2":"syntax","summary":"Basic highlighting for FlexDDPL policies","3":"Basic highlighting for FlexDDPL policies","description":"The Flexible Data Distribution Policy Language (FlexDDPL) is a declarative language for expressing storage gateway options and constraints. This syntax file makes editing the policies in a text editor more comfortable.","4":"The Flexible Data Distribution Policy Language (FlexDDPL) is a declarative language for expressing storage gateway options and constraints. This syntax file makes editing the policies in a text editor more comfortable.","install_details":"Activate with something like the following in your ~\/.vimrc:\r\nau BufNewFile,BufRead *.flexddpl set syntax=flexddpl","5":"Activate with something like the following in your ~\/.vimrc:\r\nau BufNewFile,BufRead *.flexddpl set syntax=flexddpl","first_name":"Josef","6":"Josef","last_name":"Spillner","7":"Spillner","releases":[{"0":"4161","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"flexddpl.vim","4":"flexddpl.vim","src_id":"18375","5":"18375","creation_date":"1344412981","6":"1344412981"}]},"4160":{"script_id":"4160","0":"4160","script_name":"Drupal","1":"Drupal","script_type":"utility","2":"utility","summary":"A very simple plugin to help develop with Drupal","3":"A very simple plugin to help develop with Drupal","description":"Simple plugin for VIm to help develop with Drupal.\r\nIt's the tool I use for my works, so it will probably include more features in the future.\r\n\r\nBut... It is not supposed to become a huge plugin because one of the reasons I like VI is its lightness, so...\r\nThis + Drush + the rest of my VIm config is enough for me, I don't want an editor that take too much memory.\r\n\r\n---\r\n\r\nFOR A COMPLETE DOCUMENTATION, READ THE FILE HEADER:\r\nALL IS EXPLAINED AND PROBABLY MORE UP2DATE THAN ON THIS PAGE!\r\n\r\n---\r\n\r\nUSAGE:\r\n\r\n  - \"ResetVimDrupalCache\" command:                  ** args: none **\r\n      Reset the internal cache.\r\n \r\n    Use it if a new module\/theme\/file is not autocompleted.\r\n \r\n \r\n  - \"Hook\" command:                          **  args: {hook_name} **\r\n      Implement the named hook, where the cursor is.\r\n \r\n    For convinience, the module name is guessed by the file path,\r\n    when this is ambiguous or indeterminate, a prompt is displayed.\r\n    A cache (renewed each time vim is opened) is used to not ask\r\n    several times for the same file in which module it is associated.\r\n \r\n    Note that:\r\n    - If the hook implementation already exists (and found by ctags),\r\n      a new function is NOT created: The cursor is placed on this instead.\r\n    - If the hook contains a specific part (like hook_form_FORM_ID_alter),                                                                            \r\n      a dialog will ask what use for it (in this example value of FORM_ID)\r\n \r\n \r\n  - \"EditDrupal\" command:    **  args: {module \/ theme} {filepath} **\r\n      Edit a Drupal file.                      \/!\\ Require Drush! \/!\\\r\n \r\n    {module \/ theme} is the (machine) name of a module or a theme,\r\n    {filepath} is the path of a file, relative to this module \/ theme\r\n\r\n    You can use \"\/\" as module argument: It will point to the Drupal root.\r\n \r\n    Some file are excluded from the autocomplete list.\r\n    By default: *.png, *.gif, *.jpg and *.jpeg\r\n    You can change which ones by adding (and adapting) this to your .vimrc:\r\n          let g:Drupal_excluded_extensions = 'png,gif,jpg,jpeg'\r\n    (coma separated file extensions to exclude, or empty to allow all files)\r\n\r\n---\r\n\r\nIf you want to be sure having the last version of this plugin, check my github repository (in case of I forgot to update here):\r\nhttps:\/\/github.com\/webastien\/vim\/blob\/master\/vim\/plugin\/drupal.vim\r\n\r\nOn github, you will also find my VIm configuration. Feel free to extract parts of code you need from my sources.\r\nThis could be better but I use those for my daily works without problems and it will be improved over the time.\r\nI always miss time to refactor and clean the code, so if you want to help, you're welcome ;-)","4":"Simple plugin for VIm to help develop with Drupal.\r\nIt's the tool I use for my works, so it will probably include more features in the future.\r\n\r\nBut... It is not supposed to become a huge plugin because one of the reasons I like VI is its lightness, so...\r\nThis + Drush + the rest of my VIm config is enough for me, I don't want an editor that take too much memory.\r\n\r\n---\r\n\r\nFOR A COMPLETE DOCUMENTATION, READ THE FILE HEADER:\r\nALL IS EXPLAINED AND PROBABLY MORE UP2DATE THAN ON THIS PAGE!\r\n\r\n---\r\n\r\nUSAGE:\r\n\r\n  - \"ResetVimDrupalCache\" command:                  ** args: none **\r\n      Reset the internal cache.\r\n \r\n    Use it if a new module\/theme\/file is not autocompleted.\r\n \r\n \r\n  - \"Hook\" command:                          **  args: {hook_name} **\r\n      Implement the named hook, where the cursor is.\r\n \r\n    For convinience, the module name is guessed by the file path,\r\n    when this is ambiguous or indeterminate, a prompt is displayed.\r\n    A cache (renewed each time vim is opened) is used to not ask\r\n    several times for the same file in which module it is associated.\r\n \r\n    Note that:\r\n    - If the hook implementation already exists (and found by ctags),\r\n      a new function is NOT created: The cursor is placed on this instead.\r\n    - If the hook contains a specific part (like hook_form_FORM_ID_alter),                                                                            \r\n      a dialog will ask what use for it (in this example value of FORM_ID)\r\n \r\n \r\n  - \"EditDrupal\" command:    **  args: {module \/ theme} {filepath} **\r\n      Edit a Drupal file.                      \/!\\ Require Drush! \/!\\\r\n \r\n    {module \/ theme} is the (machine) name of a module or a theme,\r\n    {filepath} is the path of a file, relative to this module \/ theme\r\n\r\n    You can use \"\/\" as module argument: It will point to the Drupal root.\r\n \r\n    Some file are excluded from the autocomplete list.\r\n    By default: *.png, *.gif, *.jpg and *.jpeg\r\n    You can change which ones by adding (and adapting) this to your .vimrc:\r\n          let g:Drupal_excluded_extensions = 'png,gif,jpg,jpeg'\r\n    (coma separated file extensions to exclude, or empty to allow all files)\r\n\r\n---\r\n\r\nIf you want to be sure having the last version of this plugin, check my github repository (in case of I forgot to update here):\r\nhttps:\/\/github.com\/webastien\/vim\/blob\/master\/vim\/plugin\/drupal.vim\r\n\r\nOn github, you will also find my VIm configuration. Feel free to extract parts of code you need from my sources.\r\nThis could be better but I use those for my daily works without problems and it will be improved over the time.\r\nI always miss time to refactor and clean the code, so if you want to help, you're welcome ;-)","install_details":"\r\n    Required:\r\n  - Drop this file to your plugin directory of vim.\r\n \r\n    Recommanded:\r\n  - Install Drush! http:\/\/drupal.org\/project\/drush\/\r\n    \/!\\ \"EditDrupal\" command will not work without!\r\n \r\n  - Add an abbreviation for \"EditDrupal\" command.\r\n    To do it, add this to your .vimrc:\r\n          cabbrev YOURABBR <c-r>= ((getcmdtype() == ':' && getcmdpos() == 1)? 'EditDrupal': 'YOURABBR')<CR>\r\n    (where YOURABBR is the abbreviation you've choosed)\r\n \r\n    Example: cabbrev ed <c-r>= ((getcmdtype() == ':' && getcmdpos() == 1)? 'EditDrupal': 'ed')<CR>\r\n             Now, when you are in command mode, type ed<space> and 'ed' has been replaced by 'EditDrupal'.\r\n \r\n    Optional:\r\n  - Map a key to call the \"ResetVimDrupalCache\" command.\r\n    To do it, add this to your .vimrc:\r\n          nmap YOURKEY :ResetVimDrupalCache<CR>\r\n    (where YOURKEY is the key you've choosed)\r\n \r\n    Example: nmap <F10> :ResetVimDrupalCache<CR>","5":"\r\n    Required:\r\n  - Drop this file to your plugin directory of vim.\r\n \r\n    Recommanded:\r\n  - Install Drush! http:\/\/drupal.org\/project\/drush\/\r\n    \/!\\ \"EditDrupal\" command will not work without!\r\n \r\n  - Add an abbreviation for \"EditDrupal\" command.\r\n    To do it, add this to your .vimrc:\r\n          cabbrev YOURABBR <c-r>= ((getcmdtype() == ':' && getcmdpos() == 1)? 'EditDrupal': 'YOURABBR')<CR>\r\n    (where YOURABBR is the abbreviation you've choosed)\r\n \r\n    Example: cabbrev ed <c-r>= ((getcmdtype() == ':' && getcmdpos() == 1)? 'EditDrupal': 'ed')<CR>\r\n             Now, when you are in command mode, type ed<space> and 'ed' has been replaced by 'EditDrupal'.\r\n \r\n    Optional:\r\n  - Map a key to call the \"ResetVimDrupalCache\" command.\r\n    To do it, add this to your .vimrc:\r\n          nmap YOURKEY :ResetVimDrupalCache<CR>\r\n    (where YOURKEY is the key you've choosed)\r\n \r\n    Example: nmap <F10> :ResetVimDrupalCache<CR>","first_name":"S\u00c3\u00a9bastien","6":"S\u00c3\u00a9bastien","last_name":"<anon>","7":"<anon>","releases":[{"0":"4160","vim_version":"7.0","1":"7.0","script_version":"1.1","2":"1.1","version_comment":"New functionalities (main is \"DrupalEdit\")","3":"New functionalities (main is \"DrupalEdit\")","package":"drupal.vim","4":"drupal.vim","src_id":"18377","5":"18377","creation_date":"1344451202","6":"1344451202"},{"0":"4160","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"drupal.vim","4":"drupal.vim","src_id":"18373","5":"18373","creation_date":"1344284506","6":"1344284506"}]},"4159":{"script_id":"4159","0":"4159","script_name":"phpvim","1":"phpvim","script_type":"syntax","2":"syntax","summary":"PHP syntax file updated for PHP 5.4","3":"PHP syntax file updated for PHP 5.4","description":"This script is based on Paul Garvin's vimuser 5.3 script vimscript #2874. Thanks for his script generator.\r\n\r\nThis is an updated version of the php.vim syntax file distributed with VIM. The list of PHP constants, functions, and classes was updated to be current with PHP 5.4\r\n","4":"This script is based on Paul Garvin's vimuser 5.3 script vimscript #2874. Thanks for his script generator.\r\n\r\nThis is an updated version of the php.vim syntax file distributed with VIM. The list of PHP constants, functions, and classes was updated to be current with PHP 5.4\r\n","install_details":"Create the following directory if it does not already exist and place php.vim inside of it. \r\nUnix: \/home\/<username>\/.vim\/syntax\/ \r\nWindows up to & incl XP: C:\\Documents and Settings\\<username>\\_vim\\syntax\\ \r\nWindows Vista & 7: C:\\Users\\<username\\_vim\\syntax\\\r\n ","5":"Create the following directory if it does not already exist and place php.vim inside of it. \r\nUnix: \/home\/<username>\/.vim\/syntax\/ \r\nWindows up to & incl XP: C:\\Documents and Settings\\<username>\\_vim\\syntax\\ \r\nWindows Vista & 7: C:\\Users\\<username\\_vim\\syntax\\\r\n ","first_name":"Laruence","6":"Laruence","last_name":" ","7":" ","releases":[{"0":"4159","vim_version":"7.3","1":"7.3","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"php54.tar.gz","4":"php54.tar.gz","src_id":"18372","5":"18372","creation_date":"1344152410","6":"1344152410"}]},"4158":{"script_id":"4158","0":"4158","script_name":"bwm color scheme","1":"bwm color scheme","script_type":"color scheme","2":"color scheme","summary":"Color scheme","3":"Color scheme","description":"Light and dark have there issue, this one moderate simple color scheme.","4":"Light and dark have there issue, this one moderate simple color scheme.","install_details":"Drop it in color scheme directory.","5":"Drop it in color scheme directory.","first_name":"vijayandra","6":"vijayandra","last_name":"singh","7":"singh","releases":[{"0":"4158","vim_version":"5.7","1":"5.7","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"bwn.vim","4":"bwn.vim","src_id":"18365","5":"18365","creation_date":"1343956808","6":"1343956808"}]},"4157":{"script_id":"4157","0":"4157","script_name":"pb.vim","1":"pb.vim","script_type":"utility","2":"utility","summary":"plugin for interacting with Mac OS X pastebuffer","3":"plugin for interacting with Mac OS X pastebuffer","description":"vim plugin simplifies interaction with Mac OS X pastebuffer\r\nusing pbcopy and pbpaste utilities by providing convenient commands for\r\nyanking into Mac OS X pastebuffer and pasting from it\r\n\r\nhttps:\/\/github.com\/troydm\/pb.vim","4":"vim plugin simplifies interaction with Mac OS X pastebuffer\r\nusing pbcopy and pbpaste utilities by providing convenient commands for\r\nyanking into Mac OS X pastebuffer and pasting from it\r\n\r\nhttps:\/\/github.com\/troydm\/pb.vim","install_details":"","5":"","first_name":"Dmitry","6":"Dmitry","last_name":"Geurkov","7":"Geurkov","releases":[{"0":"4157","vim_version":"7.0","1":"7.0","script_version":"0.2","2":"0.2","version_comment":"visual mode support added","3":"visual mode support added","package":"pb.vim-0.2.zip","4":"pb.vim-0.2.zip","src_id":"18533","5":"18533","creation_date":"1346612119","6":"1346612119"},{"0":"4157","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"pb.vim-0.1.zip","4":"pb.vim-0.1.zip","src_id":"18360","5":"18360","creation_date":"1343836908","6":"1343836908"}]},"4156":{"script_id":"4156","0":"4156","script_name":"LogViewer","1":"LogViewer","script_type":"utility","2":"utility","summary":"Comfortable examination of multiple parallel logfiles.","3":"Comfortable examination of multiple parallel logfiles.","description":"DESCRIPTION\r\nMany applications produce multiple log files; there may be one per component\r\nor one production log and a separate debug log, or one from the server daemon\r\nand one from the client application. During analysis, one may need to step\r\nthrough them in tandem, when one provides details that the other doesn't.\r\nDoing this manually in split windows is tedious; 'scrollbind' usually doesn't\r\nhelp because different amounts of log lines are written to each file.\r\n\r\nAs long as each log file provides a timestamp or similar monotonically\r\nincreasing field, this plugin automatically syncs the cursor movement in one\r\nlog window to all other windows. When moving to another line in the current\r\nwindow, all log lines that fall in the time range covered by the movement are\r\nhighlighted automatically.\r\n\r\nThis screenshot shows the plugin in action:\r\n    https:\/\/raw.githubusercontent.com\/inkarkat\/vim-LogViewer\/master\/doc\/LogViewer.png\r\n\r\nUSAGE\r\nThe plugin is either activated automatically for the 'filetype' values in\r\ng:LogViewer_Filetypes, or it can be manually activated for any buffer with\r\nthe :LogViewerEnable command.\r\nWith the default automatic syncing, any log buffer will automatically set up\r\nthe corresponding autocommands; without it, you need to kick off syncing in\r\none buffer via :LogViewerMaster. The current line in the current buffer will\r\nbe highlighted and marked with the \"T\" (for target) sign:\r\nT 2012-08-01 10:01:22.342\r\n\r\nWhen you move to another line, the plugin will mark the synced move in other\r\nbuffers to an adjacent line like this:\r\n  2012-08-01 10:01:22.342\r\n> 2012-08-01 10:01:23.234\r\nWhen the timespan in the current buffer covers multiple log lines in another\r\nbuffer, the start of the range is marked with \"-\" and the end of the range\r\nwith \"V\" (downward move) \/ \"^\" (upward move):\r\n  2012-08-01 10:01:22.342\r\n- 2012-08-01 10:01:23.234\r\n  2012-08-01 10:01:23.250\r\nV 2012-08-01 10:01:26.012\r\n\r\n:LogViewerEnable        Consider the current buffer as a log (even though its\r\n                        'filetype' does not automatically make it one).\r\n\r\n:LogViewerDisable       Exclude the current buffer from the log syncing; any\r\n                        signs and automatic updates are removed from it.\r\n\r\n:LogViewerMaster        Designate the current buffer as the log master. Only\r\n                        cursor movements in this buffer will sync to other\r\n                        buffers; movements in other buffers won't affect the\r\n                        markers any more.\r\n\r\n:LogViewerUpdate CursorMoved | CursorHold | Manual\r\n                        Set the trigger for the syncing to the passed event.\r\n                        By default, each cursor movement will immediately\r\n                        update all other log buffers. With CursorHold, this\r\n                        will only happen after 'updatetime'. With Manual, it\r\n                        has to be explicitly triggered with\r\n                        :LogViewerTarget.\r\n\r\n<Leader>tlv             Toggle syncing between the default update trigger\r\n                        (g:LogViewer_SyncUpdate) and manual updating (or\r\n                        CursorMoved if the default sync is set to manual).\r\n\r\n:LogViewerTarget        Set the target log line (the basis for the\r\n                        highlighting in all other log buffers) to the current\r\n                        line in the current buffer.\r\n:[count]LogViewerTarget Set the target log line to [count] timestamps down\r\n                        from the current target timestamp.\r\n:LogViewerTarget {timestamp}\r\n                        Set the target log line to the first timestamp that\r\n                        matches {timestamp}. Useful to proceed to the\r\n                        beginning of a date when interesting things have\r\n                        happened.","4":"DESCRIPTION\r\nMany applications produce multiple log files; there may be one per component\r\nor one production log and a separate debug log, or one from the server daemon\r\nand one from the client application. During analysis, one may need to step\r\nthrough them in tandem, when one provides details that the other doesn't.\r\nDoing this manually in split windows is tedious; 'scrollbind' usually doesn't\r\nhelp because different amounts of log lines are written to each file.\r\n\r\nAs long as each log file provides a timestamp or similar monotonically\r\nincreasing field, this plugin automatically syncs the cursor movement in one\r\nlog window to all other windows. When moving to another line in the current\r\nwindow, all log lines that fall in the time range covered by the movement are\r\nhighlighted automatically.\r\n\r\nThis screenshot shows the plugin in action:\r\n    https:\/\/raw.githubusercontent.com\/inkarkat\/vim-LogViewer\/master\/doc\/LogViewer.png\r\n\r\nUSAGE\r\nThe plugin is either activated automatically for the 'filetype' values in\r\ng:LogViewer_Filetypes, or it can be manually activated for any buffer with\r\nthe :LogViewerEnable command.\r\nWith the default automatic syncing, any log buffer will automatically set up\r\nthe corresponding autocommands; without it, you need to kick off syncing in\r\none buffer via :LogViewerMaster. The current line in the current buffer will\r\nbe highlighted and marked with the \"T\" (for target) sign:\r\nT 2012-08-01 10:01:22.342\r\n\r\nWhen you move to another line, the plugin will mark the synced move in other\r\nbuffers to an adjacent line like this:\r\n  2012-08-01 10:01:22.342\r\n> 2012-08-01 10:01:23.234\r\nWhen the timespan in the current buffer covers multiple log lines in another\r\nbuffer, the start of the range is marked with \"-\" and the end of the range\r\nwith \"V\" (downward move) \/ \"^\" (upward move):\r\n  2012-08-01 10:01:22.342\r\n- 2012-08-01 10:01:23.234\r\n  2012-08-01 10:01:23.250\r\nV 2012-08-01 10:01:26.012\r\n\r\n:LogViewerEnable        Consider the current buffer as a log (even though its\r\n                        'filetype' does not automatically make it one).\r\n\r\n:LogViewerDisable       Exclude the current buffer from the log syncing; any\r\n                        signs and automatic updates are removed from it.\r\n\r\n:LogViewerMaster        Designate the current buffer as the log master. Only\r\n                        cursor movements in this buffer will sync to other\r\n                        buffers; movements in other buffers won't affect the\r\n                        markers any more.\r\n\r\n:LogViewerUpdate CursorMoved | CursorHold | Manual\r\n                        Set the trigger for the syncing to the passed event.\r\n                        By default, each cursor movement will immediately\r\n                        update all other log buffers. With CursorHold, this\r\n                        will only happen after 'updatetime'. With Manual, it\r\n                        has to be explicitly triggered with\r\n                        :LogViewerTarget.\r\n\r\n<Leader>tlv             Toggle syncing between the default update trigger\r\n                        (g:LogViewer_SyncUpdate) and manual updating (or\r\n                        CursorMoved if the default sync is set to manual).\r\n\r\n:LogViewerTarget        Set the target log line (the basis for the\r\n                        highlighting in all other log buffers) to the current\r\n                        line in the current buffer.\r\n:[count]LogViewerTarget Set the target log line to [count] timestamps down\r\n                        from the current target timestamp.\r\n:LogViewerTarget {timestamp}\r\n                        Set the target log line to the first timestamp that\r\n                        matches {timestamp}. Useful to proceed to the\r\n                        beginning of a date when interesting things have\r\n                        happened.","install_details":"INSTALLATION\r\nThe code is hosted in a Git repo at\r\n    https:\/\/github.com\/inkarkat\/vim-LogViewer\r\nYou can use your favorite plugin manager, or \"git clone\" into a directory used\r\nfor Vim packages. Releases are on the \"stable\" branch, the latest unstable\r\ndevelopment snapshot on \"master\".\r\n\r\nThis script is also packaged as a vimball. If you have the \"gunzip\"\r\ndecompressor in your PATH, simply edit the *.vmb.gz package in Vim; otherwise,\r\ndecompress the archive first, e.g. using WinZip. Inside Vim, install by\r\nsourcing the vimball or via the :UseVimball command.\r\n    vim LogViewer*.vmb.gz\r\n    :so %\r\nTo uninstall, use the :RmVimball command.\r\n\r\nDEPENDENCIES\r\n- Requires Vim 7.0 or higher.\r\n- Requires the ingo-library.vim plugin (vimscript #4433), version 1.032 or\r\n  higher.\r\n\r\nCONFIGURATION\r\nFor a permanent configuration, put the following commands into your vimrc:\r\n\r\nTo change the default update trigger (that can be switched via\r\n:LogViewerUpdate to Manual :\r\n    let g:LogViewer_SyncUpdate = 'Manual'\r\n\r\nBy default, there is no master log file; movements in any log buffer cause\r\nsyncing in the other buffers. To turn that off:\r\n    let g:LogViewer_SyncAll = 0\r\nYou will need to use :LogViewerMaster on one log buffer to start the\r\nsyncing.\r\n\r\nOnly buffers with certain filetypes are considered log files. The setting is a\r\ncomma-separated list of filetypes (autocmd-patterns):\r\n    let g:LogViewer_Filetypes = 'log4j,syslog'\r\n\r\nBy default, the timestamp is expected as a whitespace-separated decimal number\r\nstarting at the first column. You should define the appropriate timestamp\r\nformat for each log filetype (from g:LogViewer_Filetypes). Typically, this\r\nis done in ~\/.vim\/ftplugin\/{filetype}_LogViewer.vim. For example, the log4j\r\ntimestamp pattern corresponding to the \"%d\" format is:\r\n    let b:logTimestampExpr = '^\\d\\S\\+\\d \\d\\S\\+\\d\\ze\\s' \" %d, e.g. 2011-08-17 13:08:30,509\r\nIf most \/ all of your logfiles have a differing timestamp format, you can\r\nalternatively just redefine the global default as well.\r\nTo determine the chronological order, LogViewer uses a numerical compare for\r\ninteger timestamps, and case-sensitive string comparison for everything else.\r\n\r\nTo mark the current target logline and the corresponding log line ranges in\r\nthe other log buffers, LogViewer uses signs:\r\n    LogViewerTarget     The target log line at the current cursor position, or\r\n                        set via :LogViewerTarget\r\n    LogViewerFrom       The (earliest when moving down towards later log\r\n                        entries) log line corresponding to the move of the\r\n                        target.\r\n    LogViewerTo         The last log line corresponding to the move of the\r\n                        target.\r\n\r\nYou can redefine the sign definitions after the plugin\/LogViewer.vim script\r\nhas been sourced, e.g.:\r\n    runtime plugin\/LogViewer.vim\r\n    sign define LogViewerTarget   text=T linehl=CursorLine\r\n\r\nThe default signs use line highlighting for a |hl-CursorLine|-like visual\r\nindication of the positions (the 'cursorline' setting is disabled\r\nautomatically for log windows); you can define you own colors for those, too:\r\n    highlight LogViewerTarget gui=underline guibg=Red\r\n\r\nIf you want to use a different mapping, map your keys to the\r\n<Plug>(LogViewerToggle) mapping target _before_ sourcing the script (e.g. in\r\nyour vimrc):\r\n    nmap <Leader>LV <Plug>(LogViewerToggle)\r\n\r\nINTEGRATION\r\nThe plugin emits User events for each buffer that is considered (or not any\r\nlonger) by the plugin, via two LogViewerEnable and LogViewerDisable events:\r\n    augroup LogViewerCustomization\r\n        autocmd!\r\n        autocmd User LogViewerEnable  unsilent echomsg 'Enabled LogViewer for buffer'\r\n        autocmd User LogViewerDisable unsilent echomsg 'Disabled LogViewer for buffer'\r\n    augroup END","5":"INSTALLATION\r\nThe code is hosted in a Git repo at\r\n    https:\/\/github.com\/inkarkat\/vim-LogViewer\r\nYou can use your favorite plugin manager, or \"git clone\" into a directory used\r\nfor Vim packages. Releases are on the \"stable\" branch, the latest unstable\r\ndevelopment snapshot on \"master\".\r\n\r\nThis script is also packaged as a vimball. If you have the \"gunzip\"\r\ndecompressor in your PATH, simply edit the *.vmb.gz package in Vim; otherwise,\r\ndecompress the archive first, e.g. using WinZip. Inside Vim, install by\r\nsourcing the vimball or via the :UseVimball command.\r\n    vim LogViewer*.vmb.gz\r\n    :so %\r\nTo uninstall, use the :RmVimball command.\r\n\r\nDEPENDENCIES\r\n- Requires Vim 7.0 or higher.\r\n- Requires the ingo-library.vim plugin (vimscript #4433), version 1.032 or\r\n  higher.\r\n\r\nCONFIGURATION\r\nFor a permanent configuration, put the following commands into your vimrc:\r\n\r\nTo change the default update trigger (that can be switched via\r\n:LogViewerUpdate to Manual :\r\n    let g:LogViewer_SyncUpdate = 'Manual'\r\n\r\nBy default, there is no master log file; movements in any log buffer cause\r\nsyncing in the other buffers. To turn that off:\r\n    let g:LogViewer_SyncAll = 0\r\nYou will need to use :LogViewerMaster on one log buffer to start the\r\nsyncing.\r\n\r\nOnly buffers with certain filetypes are considered log files. The setting is a\r\ncomma-separated list of filetypes (autocmd-patterns):\r\n    let g:LogViewer_Filetypes = 'log4j,syslog'\r\n\r\nBy default, the timestamp is expected as a whitespace-separated decimal number\r\nstarting at the first column. You should define the appropriate timestamp\r\nformat for each log filetype (from g:LogViewer_Filetypes). Typically, this\r\nis done in ~\/.vim\/ftplugin\/{filetype}_LogViewer.vim. For example, the log4j\r\ntimestamp pattern corresponding to the \"%d\" format is:\r\n    let b:logTimestampExpr = '^\\d\\S\\+\\d \\d\\S\\+\\d\\ze\\s' \" %d, e.g. 2011-08-17 13:08:30,509\r\nIf most \/ all of your logfiles have a differing timestamp format, you can\r\nalternatively just redefine the global default as well.\r\nTo determine the chronological order, LogViewer uses a numerical compare for\r\ninteger timestamps, and case-sensitive string comparison for everything else.\r\n\r\nTo mark the current target logline and the corresponding log line ranges in\r\nthe other log buffers, LogViewer uses signs:\r\n    LogViewerTarget     The target log line at the current cursor position, or\r\n                        set via :LogViewerTarget\r\n    LogViewerFrom       The (earliest when moving down towards later log\r\n                        entries) log line corresponding to the move of the\r\n                        target.\r\n    LogViewerTo         The last log line corresponding to the move of the\r\n                        target.\r\n\r\nYou can redefine the sign definitions after the plugin\/LogViewer.vim script\r\nhas been sourced, e.g.:\r\n    runtime plugin\/LogViewer.vim\r\n    sign define LogViewerTarget   text=T linehl=CursorLine\r\n\r\nThe default signs use line highlighting for a |hl-CursorLine|-like visual\r\nindication of the positions (the 'cursorline' setting is disabled\r\nautomatically for log windows); you can define you own colors for those, too:\r\n    highlight LogViewerTarget gui=underline guibg=Red\r\n\r\nIf you want to use a different mapping, map your keys to the\r\n<Plug>(LogViewerToggle) mapping target _before_ sourcing the script (e.g. in\r\nyour vimrc):\r\n    nmap <Leader>LV <Plug>(LogViewerToggle)\r\n\r\nINTEGRATION\r\nThe plugin emits User events for each buffer that is considered (or not any\r\nlonger) by the plugin, via two LogViewerEnable and LogViewerDisable events:\r\n    augroup LogViewerCustomization\r\n        autocmd!\r\n        autocmd User LogViewerEnable  unsilent echomsg 'Enabled LogViewer for buffer'\r\n        autocmd User LogViewerDisable unsilent echomsg 'Disabled LogViewer for buffer'\r\n    augroup END","first_name":"Ingo","6":"Ingo","last_name":"Karkat","7":"Karkat","releases":[{"0":"4156","vim_version":"7.0","1":"7.0","script_version":"1.20","2":"1.20","version_comment":"- ENH: Add <Leader>tlv mapping to quickly enable \/ disable sync updates.\r\n- With Manual updating, don't automatically adapt the signs to show the perspective from the current buffer. The user doesn't expect any change to the displayed situation here, only do this when explicitly triggered via :LogViewerTarget.\r\n- ENH: Define user events LogViewerEnable and LogViewerDisable to allow hooking into the plugin functionality.\r\n- ENH: The default extraction pattern for the timestamp can now also be reconfigured globally (via g:LogViewer_TimestampExpr), not just for individual buffers via b:logTimestampExpr.","3":"- ENH: Add <Leader>tlv mapping to quickly enable \/ disable sync updates.\r\n- With Manual updating, don't automatically adapt the signs to show the perspective from the current buffer. The user doesn't expect any change to the displayed situation here, only do this when explicitly triggered via :LogViewerTarget.\r\n- ENH: Define user events LogViewerEnable and LogViewerDisable to allow hooking into the plugin functionality.\r\n- ENH: The default extraction pattern for the timestamp can now also be reconfigured globally (via g:LogViewer_TimestampExpr), not just for individual buffers via b:logTimestampExpr.","package":"LogViewer-1.20.vmb.gz","4":"LogViewer-1.20.vmb.gz","src_id":"26957","5":"26957","creation_date":"1580767148","6":"1580767148"},{"0":"4156","vim_version":"7.0","1":"7.0","script_version":"1.11","2":"1.11","version_comment":"- ENH: Keep previous (last accessed) window on :windo.\r\n- BUG: Movement in visual mode either causes beeps (at first selection) or distorts the selection; need to exit visual mode before syncing to be able to properly restore it.\r\n- Don't override existing b:logTimestampExpr in ftplugin\/log4j_LogViewer.vim. This way, users don't necessarily need to use after\/ftplugin to override this with a custom value.\r\n- Use first non-empty line in buffer to detect used log4j timestamp format.\r\n- Add precise pattern for %d log4j format, and check that first. *** You need to update to ingo-library (vimscript #4433) version 1.032! ***","3":"- ENH: Keep previous (last accessed) window on :windo.\r\n- BUG: Movement in visual mode either causes beeps (at first selection) or distorts the selection; need to exit visual mode before syncing to be able to properly restore it.\r\n- Don't override existing b:logTimestampExpr in ftplugin\/log4j_LogViewer.vim. This way, users don't necessarily need to use after\/ftplugin to override this with a custom value.\r\n- Use first non-empty line in buffer to detect used log4j timestamp format.\r\n- Add precise pattern for %d log4j format, and check that first. *** You need to update to ingo-library (vimscript #4433) version 1.032! ***","package":"LogViewer-1.11.vmb.gz","4":"LogViewer-1.11.vmb.gz","src_id":"26241","5":"26241","creation_date":"1538607655","6":"1538607655"},{"0":"4156","vim_version":"7.0","1":"7.0","script_version":"1.10","2":"1.10","version_comment":"- Syncing on the CursorMoved event disturbs the selection, making it impossible to select multiple log lines. Explicitly restore the visual selection.\r\n- Add b:logTimestampExpr definition for log4j filetype to the plugin.\r\n- Add :LogViewerEnable \/ :LogViewerDisable commands to explicitly manage individual buffers, and allow use of the plugin for filetypes that haven't been included in g:LogViewer_Filetypes.\r\n- Add dependency to ingo-library (vimscript #4433). *** You need to separately install ingo-library (vimscript #4433) version 1.008 (or higher)! ***","3":"- Syncing on the CursorMoved event disturbs the selection, making it impossible to select multiple log lines. Explicitly restore the visual selection.\r\n- Add b:logTimestampExpr definition for log4j filetype to the plugin.\r\n- Add :LogViewerEnable \/ :LogViewerDisable commands to explicitly manage individual buffers, and allow use of the plugin for filetypes that haven't been included in g:LogViewer_Filetypes.\r\n- Add dependency to ingo-library (vimscript #4433). *** You need to separately install ingo-library (vimscript #4433) version 1.008 (or higher)! ***","package":"LogViewer-1.10.vmb.gz","4":"LogViewer-1.10.vmb.gz","src_id":"22583","5":"22583","creation_date":"1414592942","6":"1414592942"},{"0":"4156","vim_version":"7.0","1":"7.0","script_version":"1.00","2":"1.00","version_comment":"Initial upload","3":"Initial upload","package":"LogViewer.vba.gz","4":"LogViewer.vba.gz","src_id":"18359","5":"18359","creation_date":"1343830176","6":"1343830176"}]},"4155":{"script_id":"4155","0":"4155","script_name":"AlignFromCursor","1":"AlignFromCursor","script_type":"utility","2":"utility","summary":"Perform :left \/ :right only for the text on and right of the cursor.","3":"Perform :left \/ :right only for the text on and right of the cursor.","description":"DESCRIPTION\r\nThis plugin offers commands and mappings that align only the text to the right\r\nof the cursor, and keep the text to the left unmodified, unlike the built-in\r\n:left and :right, which always work on the entire line.\r\nThis is useful e.g. for right-aligning the \"-- Author\" attribution in a\r\nfortune, the help tags definitions in this help file, or to left-align a\r\ncomment to a particular column.\r\nThe alignment width defaults to 'textwidth', can be passed as a [count] to the\r\nmappings, and there are mappings that take the actual width from adjacent\r\nprevious \/ next lines.\r\n\r\nRELATED WORKS\r\n- The Align plugin (vimscript #294) offers a general-purpose :Align command\r\n  and many mappings for text alignment along various characters, but those are\r\n  more specialized for certain syntax fragments and do not consider the\r\n  current cursor position like this plugin.\r\n- The Tabular plugin (https:\/\/github.com\/godlygeek\/tabular) is similar to the\r\n  Align plugin.\r\n- The vim-easy-align plugin (vimscript #4520) is also similar to Align, and\r\n  asserts it's easy to use.\r\n- right_align (vimscript #3728) has a :RightAlign command that aligns to\r\n  'textwidth' in full increments of 'shiftwidth'.\r\n\r\nUSAGE\r\n[width]<Leader>le\r\n:[range]LeftAlignFromCursor [width]\r\n                        Left-align the text on and right of the cursor to\r\n                        [width] columns (default 'textwidth' or 80 when\r\n                        'textwidth' is 0). Cp. :left.\r\n                        Applies to all lines in [range], based on the current\r\n                        cursor position.\r\n                        In visual mode: Applies to the selected text, based on\r\n                        the leftmost selected column.\r\n\r\n[count]<Leader>lp       Left-align the text on and right of the cursor to the\r\n[count]<Leader>ln       indent of the [count]'th previous \/ next unfolded line.\r\n                        In visual mode: Left-align the selected text to the\r\n                        indent of the [count]'th unfolded line above \/ below\r\n                        the visual selection.\r\n\r\n[width]<Leader>ri\r\n:[range]RightAlignFromCursor [width]\r\n                        Right-align the text on and right of the cursor to\r\n                        [width] columns (default 'textwidth' or 80 when\r\n                        'textwidth' is 0). Cp. :right.\r\n                        Applies to all lines in [range], based on the current\r\n                        cursor position.\r\n                        In visual mode: Applies to the selected text, based on\r\n                        the leftmost selected column.\r\n\r\n[count]<Leader>rp       Right-align the text on and right of the cursor to the\r\n[count]<Leader>rn       width of the [count]'th previous \/ next unfolded line.\r\n                        In visual mode: Right-align the selected text to the\r\n                        width of the [count]'th unfolded line above \/ below\r\n                        the visual selection.","4":"DESCRIPTION\r\nThis plugin offers commands and mappings that align only the text to the right\r\nof the cursor, and keep the text to the left unmodified, unlike the built-in\r\n:left and :right, which always work on the entire line.\r\nThis is useful e.g. for right-aligning the \"-- Author\" attribution in a\r\nfortune, the help tags definitions in this help file, or to left-align a\r\ncomment to a particular column.\r\nThe alignment width defaults to 'textwidth', can be passed as a [count] to the\r\nmappings, and there are mappings that take the actual width from adjacent\r\nprevious \/ next lines.\r\n\r\nRELATED WORKS\r\n- The Align plugin (vimscript #294) offers a general-purpose :Align command\r\n  and many mappings for text alignment along various characters, but those are\r\n  more specialized for certain syntax fragments and do not consider the\r\n  current cursor position like this plugin.\r\n- The Tabular plugin (https:\/\/github.com\/godlygeek\/tabular) is similar to the\r\n  Align plugin.\r\n- The vim-easy-align plugin (vimscript #4520) is also similar to Align, and\r\n  asserts it's easy to use.\r\n- right_align (vimscript #3728) has a :RightAlign command that aligns to\r\n  'textwidth' in full increments of 'shiftwidth'.\r\n\r\nUSAGE\r\n[width]<Leader>le\r\n:[range]LeftAlignFromCursor [width]\r\n                        Left-align the text on and right of the cursor to\r\n                        [width] columns (default 'textwidth' or 80 when\r\n                        'textwidth' is 0). Cp. :left.\r\n                        Applies to all lines in [range], based on the current\r\n                        cursor position.\r\n                        In visual mode: Applies to the selected text, based on\r\n                        the leftmost selected column.\r\n\r\n[count]<Leader>lp       Left-align the text on and right of the cursor to the\r\n[count]<Leader>ln       indent of the [count]'th previous \/ next unfolded line.\r\n                        In visual mode: Left-align the selected text to the\r\n                        indent of the [count]'th unfolded line above \/ below\r\n                        the visual selection.\r\n\r\n[width]<Leader>ri\r\n:[range]RightAlignFromCursor [width]\r\n                        Right-align the text on and right of the cursor to\r\n                        [width] columns (default 'textwidth' or 80 when\r\n                        'textwidth' is 0). Cp. :right.\r\n                        Applies to all lines in [range], based on the current\r\n                        cursor position.\r\n                        In visual mode: Applies to the selected text, based on\r\n                        the leftmost selected column.\r\n\r\n[count]<Leader>rp       Right-align the text on and right of the cursor to the\r\n[count]<Leader>rn       width of the [count]'th previous \/ next unfolded line.\r\n                        In visual mode: Right-align the selected text to the\r\n                        width of the [count]'th unfolded line above \/ below\r\n                        the visual selection.","install_details":"INSTALLATION\r\nThis script is packaged as a vimball. If you have the \"gunzip\" decompressor\r\nin your PATH, simply edit the *.vmb.gz package in Vim; otherwise, decompress\r\nthe archive first, e.g. using WinZip. Inside Vim, install by sourcing the\r\nvimball or via the :UseVimball command.\r\n    vim AlignFromCursor*.vmb.gz\r\n    :so %\r\nTo uninstall, use the :RmVimball command.\r\n\r\nDEPENDENCIES\r\n- Requires Vim 7.0 or higher.\r\n- Requires the ingo-library.vim plugin (vimscript #4433), version 1.016 or\r\n  higher.\r\n- IndentTab.vim (vimscript #3848) plugin (optional)\r\n- repeat.vim (vimscript #2136) plugin (optional)\r\n- visualrepeat.vim (vimscript #3848) plugin (optional)\r\n\r\nCONFIGURATION\r\nFor a permanent configuration, put the following commands into your vimrc:\r\n\r\nIf you want to use different mappings, map your keys to the\r\n<Plug>(Left|Right)Align... mapping targets _before_ sourcing the script (e.g.\r\nin your vimrc):\r\n    nmap <silent> <Leader>ri <Plug>RightAlignFromCursor\r\n    nmap <silent> <Leader>le <Plug>LeftAlignFromCursor\r\n    xmap <silent> <Leader>ri <Plug>RightAlignFromCursor\r\n    xmap <silent> <Leader>le <Plug>LeftAlignFromCursor\r\n    nmap <silent> <Leader>rp <Plug>RightAlignToPreviousLine\r\n    nmap <silent> <Leader>rn <Plug>RightAlignToNextLine\r\n    nmap <silent> <Leader>lp <Plug>LeftAlignToPreviousLine\r\n    nmap <silent> <Leader>ln <Plug>LeftAlignToNextLine\r\n    xmap <silent> <Leader>rp <Plug>RightAlignToPreviousLine\r\n    xmap <silent> <Leader>rn <Plug>RightAlignToNextLine\r\n    xmap <silent> <Leader>lp <Plug>LeftAlignToPreviousLine\r\n    xmap <silent> <Leader>ln <Plug>LeftAlignToNextLine","5":"INSTALLATION\r\nThis script is packaged as a vimball. If you have the \"gunzip\" decompressor\r\nin your PATH, simply edit the *.vmb.gz package in Vim; otherwise, decompress\r\nthe archive first, e.g. using WinZip. Inside Vim, install by sourcing the\r\nvimball or via the :UseVimball command.\r\n    vim AlignFromCursor*.vmb.gz\r\n    :so %\r\nTo uninstall, use the :RmVimball command.\r\n\r\nDEPENDENCIES\r\n- Requires Vim 7.0 or higher.\r\n- Requires the ingo-library.vim plugin (vimscript #4433), version 1.016 or\r\n  higher.\r\n- IndentTab.vim (vimscript #3848) plugin (optional)\r\n- repeat.vim (vimscript #2136) plugin (optional)\r\n- visualrepeat.vim (vimscript #3848) plugin (optional)\r\n\r\nCONFIGURATION\r\nFor a permanent configuration, put the following commands into your vimrc:\r\n\r\nIf you want to use different mappings, map your keys to the\r\n<Plug>(Left|Right)Align... mapping targets _before_ sourcing the script (e.g.\r\nin your vimrc):\r\n    nmap <silent> <Leader>ri <Plug>RightAlignFromCursor\r\n    nmap <silent> <Leader>le <Plug>LeftAlignFromCursor\r\n    xmap <silent> <Leader>ri <Plug>RightAlignFromCursor\r\n    xmap <silent> <Leader>le <Plug>LeftAlignFromCursor\r\n    nmap <silent> <Leader>rp <Plug>RightAlignToPreviousLine\r\n    nmap <silent> <Leader>rn <Plug>RightAlignToNextLine\r\n    nmap <silent> <Leader>lp <Plug>LeftAlignToPreviousLine\r\n    nmap <silent> <Leader>ln <Plug>LeftAlignToNextLine\r\n    xmap <silent> <Leader>rp <Plug>RightAlignToPreviousLine\r\n    xmap <silent> <Leader>rn <Plug>RightAlignToNextLine\r\n    xmap <silent> <Leader>lp <Plug>LeftAlignToPreviousLine\r\n    xmap <silent> <Leader>ln <Plug>LeftAlignToNextLine","first_name":"Ingo","6":"Ingo","last_name":"Karkat","7":"Karkat","releases":[{"0":"4155","vim_version":"7.0","1":"7.0","script_version":"2.02","2":"2.02","version_comment":"- Improve internal efficiency.\r\n- Extract AlignFromCursor#GetRetabbedFromCol() and expose for reuse.\r\n- BUG: :LeftAlignFromCursor adds one character too few if the first left-aligned character is double width (e.g. ^X unprintable or Kanji character).","3":"- Improve internal efficiency.\r\n- Extract AlignFromCursor#GetRetabbedFromCol() and expose for reuse.\r\n- BUG: :LeftAlignFromCursor adds one character too few if the first left-aligned character is double width (e.g. ^X unprintable or Kanji character).","package":"AlignFromCursor-2.02.vmb.gz","4":"AlignFromCursor-2.02.vmb.gz","src_id":"24863","5":"24863","creation_date":"1483044723","6":"1483044723"},{"0":"4155","vim_version":"7.0","1":"7.0","script_version":"2.01","2":"2.01","version_comment":"- Support the IndentTab setting provided by the optional IndentTab plugin (vimscript #4243). I.e. align with spaces when there's text before the cursor. *** You need to update to ingo-library (vimscript #4433) version 1.016! ***","3":"- Support the IndentTab setting provided by the optional IndentTab plugin (vimscript #4243). I.e. align with spaces when there's text before the cursor. *** You need to update to ingo-library (vimscript #4433) version 1.016! ***","package":"AlignFromCursor-2.01.vmb.gz","4":"AlignFromCursor-2.01.vmb.gz","src_id":"21403","5":"21403","creation_date":"1391028464","6":"1391028464"},{"0":"4155","vim_version":"7.0","1":"7.0","script_version":"2.00","2":"2.00","version_comment":"- Use visible lines for the relative [count] in <Leader>lp \/ <Leader>ln \/ <Leader>rp \/ <Leader>rn. This is consistent with other Vim commands and allows benefitting from 'relativenumber'. When addressing a folded line, the indent of the first contained line is used.\r\n- ENH: Add visual mode <Leader>lp \/ <Leader>ln \/ <Leader>rp \/ <Leader>rn mappings that work on the selection and take the [count]'th above \/ below line.\r\n- CHG: Make repeats of the mappings use the previous width instead of just re-applying them at the current cursor position. DWIM.\r\n- BUG: Don't delete whitespace immediately after the cursor position if the cursor rests on a non-whitespace character. This makes the alignment _after_ the cursor position, not _from_ it. (Though this was a nice DWIM feature when on the last character of a word; but it makes it impossible to do an actual align from there, and is inconsistent.)\r\n- Add dependency to ingo-library (vimscript #4433). *** You need to separately install ingo-library (vimscript #4433) version 1.004 (or higher)! ***","3":"- Use visible lines for the relative [count] in <Leader>lp \/ <Leader>ln \/ <Leader>rp \/ <Leader>rn. This is consistent with other Vim commands and allows benefitting from 'relativenumber'. When addressing a folded line, the indent of the first contained line is used.\r\n- ENH: Add visual mode <Leader>lp \/ <Leader>ln \/ <Leader>rp \/ <Leader>rn mappings that work on the selection and take the [count]'th above \/ below line.\r\n- CHG: Make repeats of the mappings use the previous width instead of just re-applying them at the current cursor position. DWIM.\r\n- BUG: Don't delete whitespace immediately after the cursor position if the cursor rests on a non-whitespace character. This makes the alignment _after_ the cursor position, not _from_ it. (Though this was a nice DWIM feature when on the last character of a word; but it makes it impossible to do an actual align from there, and is inconsistent.)\r\n- Add dependency to ingo-library (vimscript #4433). *** You need to separately install ingo-library (vimscript #4433) version 1.004 (or higher)! ***","package":"AlignFromCursor-2.00.vmb.gz","4":"AlignFromCursor-2.00.vmb.gz","src_id":"20541","5":"20541","creation_date":"1374230530","6":"1374230530"},{"0":"4155","vim_version":"7.0","1":"7.0","script_version":"1.12","2":"1.12","version_comment":"Fix slowness of :RightAlignFromCursor in connection with plugins like recover.vim, caused by the repeated triggers of InsertEnter \/ InsertLeave events inserting a single space.","3":"Fix slowness of :RightAlignFromCursor in connection with plugins like recover.vim, caused by the repeated triggers of InsertEnter \/ InsertLeave events inserting a single space.","package":"AlignFromCursor-1.12.vmb.gz","4":"AlignFromCursor-1.12.vmb.gz","src_id":"19388","5":"19388","creation_date":"1358591416","6":"1358591416"},{"0":"4155","vim_version":"7.0","1":"7.0","script_version":"1.11","2":"1.11","version_comment":"BUG: On repeat, the original [count] is overridden by the align commands, causing e.g. a toggling of right-align and align to column 1 on repeated <Leader>ri.","3":"BUG: On repeat, the original [count] is overridden by the align commands, causing e.g. a toggling of right-align and align to column 1 on repeated <Leader>ri.","package":"AlignFromCursor-1.11.vmb.gz","4":"AlignFromCursor-1.11.vmb.gz","src_id":"19124","5":"19124","creation_date":"1354809819","6":"1354809819"},{"0":"4155","vim_version":"7.0","1":"7.0","script_version":"1.10","2":"1.10","version_comment":"ENH: Do not :retab the entire line (which also affects leading indent and whitespace after the area, just render the modified whitespace around the cursor according to the buffer's indent settings.","3":"ENH: Do not :retab the entire line (which also affects leading indent and whitespace after the area, just render the modified whitespace around the cursor according to the buffer's indent settings.","package":"AlignFromCursor.vba.gz","4":"AlignFromCursor.vba.gz","src_id":"18362","5":"18362","creation_date":"1343917695","6":"1343917695"},{"0":"4155","vim_version":"7.0","1":"7.0","script_version":"1.00","2":"1.00","version_comment":"Initial upload","3":"Initial upload","package":"AlignFromCursor.vba.gz","4":"AlignFromCursor.vba.gz","src_id":"18358","5":"18358","creation_date":"1343828143","6":"1343828143"}]},"4154":{"script_id":"4154","0":"4154","script_name":"allegro","1":"allegro","script_type":"syntax","2":"syntax","summary":"Allegro gaming library syntax file","3":"Allegro gaming library syntax file","description":"Provides syntax highlighting for Allegro gaming library API","4":"Provides syntax highlighting for Allegro gaming library API","install_details":"","5":"","first_name":"Yves","6":"Yves","last_name":"GLAMOUR","7":"GLAMOUR","releases":[{"0":"4154","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"allegro.vim","4":"allegro.vim","src_id":"18354","5":"18354","creation_date":"1343744103","6":"1343744103"}]},"4153":{"script_id":"4153","0":"4153","script_name":"stl","1":"stl","script_type":"syntax","2":"syntax","summary":"C++ STL Syntax File","3":"C++ STL Syntax File","description":"Provides syntax highlighting for C++ STL","4":"Provides syntax highlighting for C++ STL","install_details":"","5":"","first_name":"Yves","6":"Yves","last_name":"GLAMOUR","7":"GLAMOUR","releases":[{"0":"4153","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"stl.vim","4":"stl.vim","src_id":"18353","5":"18353","creation_date":"1343744029","6":"1343744029"}]},"4152":{"script_id":"4152","0":"4152","script_name":"ArgsAndMore","1":"ArgsAndMore","script_type":"utility","2":"utility","summary":"Apply commands to multiple buffers and manage the argument list.","3":"Apply commands to multiple buffers and manage the argument list.","description":"DESCRIPTION\r\nThis plugin supports you with batch processing many files by extending the\r\nbuilt-in :windo, :argdo, etc. commands. You can filter the argument list,\r\nadd files _not_ matching a pattern, convert between arguments and quickfix\r\nlist, and apply arbitrary Ex commands (also partially) via :Argdo, then\r\nanalyze any errors and retry on an argument list where the successfully\r\nprocessed arguments have been removed.\r\n\r\nSEE ALSO\r\nRELATED WORKS\r\n- The :ArgsNegated command was inspired by the following Stack Overflow\r\n  question:\r\n    http:\/\/stackoverflow.com\/questions\/11547662\/how-can-i-negate-a-glob-in-vim\r\n- The https:\/\/github.com\/nelstrom\/vim-qargs plugin has a :Qargs command\r\n  similar (but more simplistic) than :CListToArgs.\r\n- Pretty Args (vimscript #4681) provides an :Arg command which takes\r\n  filename-modifiers to print a shortened argument list, e.g. just the\r\n  filenames.\r\n- JustDo (vimscript #4981) provides a :BufDo command that skips unmodifiable\r\n  buffers.\r\n\r\nUSAGE\r\n:[range]Bufdo[!] {cmd}  Execute {cmd} in each buffer in the buffer list, then\r\n                        return back to the original one.\r\n                        Any encountered errors are also put into the\r\n                        quickfix list.\r\n\r\n:[range]BufdoWrite[!] {cmd}\r\n                        Execute {cmd} in each buffer in the buffer list and\r\n                        automatically persist any changes (:update).\r\n\r\n:[range]Windo {cmd}     Execute {cmd} in each window, then return back to the\r\n                        original one.\r\n\r\n:[range]Winbufdo {cmd}  Execute {cmd} in each different buffer shown in one of\r\n                        the windows in the current tab page (once per buffer),\r\n                        then return back to the original one.\r\n\r\n:[range]Tabdo {cmd}     Execute {cmd} once in each tab page, then return back\r\n                        to the original one.\r\n\r\n:[range]Tabwindo {cmd}  Execute {cmd} in each open window on each tab page,\r\n                        then return back to the original one.\r\n\r\n:[range]Argdo[!] {cmd}  Execute {cmd} for each file in the argument list, then\r\n                        return back to the original file and argument.\r\n                        [range] is emulated for older Vim versions, but can\r\n                        only be used interactively (not in scripts).\r\n\r\n                        In contrast to :argdo, this also avoids the\r\n                        hit-enter prompt (all files will be processed\r\n                        without further interaction from you), and an error\r\n                        summary will be printed.\r\n                        To work on the errors \/ arguments with errors, you can\r\n                        use :ArgdoErrors and :ArgdoDeleteSuccessful.\r\n                        Also, any encountered errors are put into the\r\n                        quickfix list.\r\n\r\n:[range]ArgdoWrite[!] {cmd}\r\n                        Execute {cmd} in each buffer in the argument list and\r\n                        automatically persist any changes (:update).\r\n:[range]ArgdoConfirmWrite[!] {cmd}\r\n                        Like :ArgdoWrite, but confirm each write, allowing\r\n                        to review the automatically applied changes of {cmd}\r\n                        before persisting them. When you quit the argument\r\n                        processing before the last argument, this will not\r\n                        return to the original file (to make it easier to\r\n                        process the remaining arguments again).\r\n\r\n:ArgdoErrors            List all error messages that occurred during the last\r\n                        :Argdo command, and for each unique error, print the\r\n                        argument number and filespec.\r\n\r\n:ArgdoDeleteSuccessful  Delete those arguments from the argument list that\r\n                        didn't cause any error messages during the last\r\n                        :Argdo command.\r\n\r\n:[range]ArgsFilter {expr}\r\n                        Apply the filter() of {expr} to the argument list,\r\n                        and keep only those where {expr} yields true. This\r\n                        allows you to :argdelete multiple arguments at once\r\n                        and to delete without specifying the full filename.\r\n\r\n:[range]ArgsFilterDo[!] {expr}\r\n                        Apply the filter() of {expr} to the argument list\r\n                        within the context of each argument, and keep only\r\n                        those where {expr} yields true. In contrast to\r\n                        :ArgsFilter, this allows filtering based on buffer\r\n                        contents (or buffer variables, buffer settings).\r\n                        For example, remove all arguments whose buffers have\r\n                        more than 100 lines:\r\n                            :ArgsFilterDo line('$') <= 100\r\n\r\n:ArgsNegated[!] {arglist}\r\n                        Define all files except {arglist} as the new argument\r\n                        list and edit the first one.\r\n\r\n:[range]ArgsList[!]     List each argument number and filespec in a neat list\r\n                        (not just one after the other as :args). With [!],\r\n                        expand all arguments to absolute filespecs.\r\n:[range]ArgsList[!] {glob}\r\n                        List each argument number and filespec that matches\r\n                        (with [!]: does not match) {glob} in a neat list.\r\n                        Matching and printing is done to the full filespec.\r\n\r\n:[range]ArgsToQuickfix  Show all arguments as a quickfix list.\r\n\r\n:CListToArgs            Convert the files in the quickfix list to arguments.\r\n:[count]CListToArgsAdd\r\n\r\n:LListToArgs            Convert the files in the window's location list to\r\n:[count]LListToArgsAdd  arguments.\r\n\r\n:CList[!], :LList[!]    List each file that has listed errors in the quickfix\r\n                        \/ location list in a neat list. With [!], expand all\r\n                        to absolute filespecs.\r\n:CList[!] {glob}        List each file that has listed errors in the quickfix\r\n:LList[!] {glob}        \/ location list that matches (with [!]: does not\r\n                        match) {glob} in a neat list. Matching and printing is\r\n                        done to the full filespec.\r\n\r\n:[range]CDoEntry {cmd}  Execute {cmd} on each entry in the quickfix \/\r\n:[range]LDoEntry {cmd}  location list (limited to buffers in [range]).\r\n\r\n:[range]CDoFile {cmd}   Execute {cmd} once on each file that appears in the\r\n:[range]LDoFile {cmd}   quickfix \/ location list (limited to buffers in\r\n                        [range]).\r\n\r\n:[range]CDoFixEntry {cmd}\r\n:[range]LDoFixEntry {cmd}\r\n                        Execute {cmd} on each entry in the quickfix \/ location\r\n                        list (limited to buffers in [range]). If the {cmd}\r\n                        does not abort and changes the buffer (i.e. increases\r\n                        b:changedtick), that entry is removed from the\r\n                        quickfix \/ location list. Else, the original entry is\r\n                        augmented with error information. (Entries for buffers\r\n                        outside [range] are kept as-is.)\r\n","4":"DESCRIPTION\r\nThis plugin supports you with batch processing many files by extending the\r\nbuilt-in :windo, :argdo, etc. commands. You can filter the argument list,\r\nadd files _not_ matching a pattern, convert between arguments and quickfix\r\nlist, and apply arbitrary Ex commands (also partially) via :Argdo, then\r\nanalyze any errors and retry on an argument list where the successfully\r\nprocessed arguments have been removed.\r\n\r\nSEE ALSO\r\nRELATED WORKS\r\n- The :ArgsNegated command was inspired by the following Stack Overflow\r\n  question:\r\n    http:\/\/stackoverflow.com\/questions\/11547662\/how-can-i-negate-a-glob-in-vim\r\n- The https:\/\/github.com\/nelstrom\/vim-qargs plugin has a :Qargs command\r\n  similar (but more simplistic) than :CListToArgs.\r\n- Pretty Args (vimscript #4681) provides an :Arg command which takes\r\n  filename-modifiers to print a shortened argument list, e.g. just the\r\n  filenames.\r\n- JustDo (vimscript #4981) provides a :BufDo command that skips unmodifiable\r\n  buffers.\r\n\r\nUSAGE\r\n:[range]Bufdo[!] {cmd}  Execute {cmd} in each buffer in the buffer list, then\r\n                        return back to the original one.\r\n                        Any encountered errors are also put into the\r\n                        quickfix list.\r\n\r\n:[range]BufdoWrite[!] {cmd}\r\n                        Execute {cmd} in each buffer in the buffer list and\r\n                        automatically persist any changes (:update).\r\n\r\n:[range]Windo {cmd}     Execute {cmd} in each window, then return back to the\r\n                        original one.\r\n\r\n:[range]Winbufdo {cmd}  Execute {cmd} in each different buffer shown in one of\r\n                        the windows in the current tab page (once per buffer),\r\n                        then return back to the original one.\r\n\r\n:[range]Tabdo {cmd}     Execute {cmd} once in each tab page, then return back\r\n                        to the original one.\r\n\r\n:[range]Tabwindo {cmd}  Execute {cmd} in each open window on each tab page,\r\n                        then return back to the original one.\r\n\r\n:[range]Argdo[!] {cmd}  Execute {cmd} for each file in the argument list, then\r\n                        return back to the original file and argument.\r\n                        [range] is emulated for older Vim versions, but can\r\n                        only be used interactively (not in scripts).\r\n\r\n                        In contrast to :argdo, this also avoids the\r\n                        hit-enter prompt (all files will be processed\r\n                        without further interaction from you), and an error\r\n                        summary will be printed.\r\n                        To work on the errors \/ arguments with errors, you can\r\n                        use :ArgdoErrors and :ArgdoDeleteSuccessful.\r\n                        Also, any encountered errors are put into the\r\n                        quickfix list.\r\n\r\n:[range]ArgdoWrite[!] {cmd}\r\n                        Execute {cmd} in each buffer in the argument list and\r\n                        automatically persist any changes (:update).\r\n:[range]ArgdoConfirmWrite[!] {cmd}\r\n                        Like :ArgdoWrite, but confirm each write, allowing\r\n                        to review the automatically applied changes of {cmd}\r\n                        before persisting them. When you quit the argument\r\n                        processing before the last argument, this will not\r\n                        return to the original file (to make it easier to\r\n                        process the remaining arguments again).\r\n\r\n:ArgdoErrors            List all error messages that occurred during the last\r\n                        :Argdo command, and for each unique error, print the\r\n                        argument number and filespec.\r\n\r\n:ArgdoDeleteSuccessful  Delete those arguments from the argument list that\r\n                        didn't cause any error messages during the last\r\n                        :Argdo command.\r\n\r\n:[range]ArgsFilter {expr}\r\n                        Apply the filter() of {expr} to the argument list,\r\n                        and keep only those where {expr} yields true. This\r\n                        allows you to :argdelete multiple arguments at once\r\n                        and to delete without specifying the full filename.\r\n\r\n:[range]ArgsFilterDo[!] {expr}\r\n                        Apply the filter() of {expr} to the argument list\r\n                        within the context of each argument, and keep only\r\n                        those where {expr} yields true. In contrast to\r\n                        :ArgsFilter, this allows filtering based on buffer\r\n                        contents (or buffer variables, buffer settings).\r\n                        For example, remove all arguments whose buffers have\r\n                        more than 100 lines:\r\n                            :ArgsFilterDo line('$') <= 100\r\n\r\n:ArgsNegated[!] {arglist}\r\n                        Define all files except {arglist} as the new argument\r\n                        list and edit the first one.\r\n\r\n:[range]ArgsList[!]     List each argument number and filespec in a neat list\r\n                        (not just one after the other as :args). With [!],\r\n                        expand all arguments to absolute filespecs.\r\n:[range]ArgsList[!] {glob}\r\n                        List each argument number and filespec that matches\r\n                        (with [!]: does not match) {glob} in a neat list.\r\n                        Matching and printing is done to the full filespec.\r\n\r\n:[range]ArgsToQuickfix  Show all arguments as a quickfix list.\r\n\r\n:CListToArgs            Convert the files in the quickfix list to arguments.\r\n:[count]CListToArgsAdd\r\n\r\n:LListToArgs            Convert the files in the window's location list to\r\n:[count]LListToArgsAdd  arguments.\r\n\r\n:CList[!], :LList[!]    List each file that has listed errors in the quickfix\r\n                        \/ location list in a neat list. With [!], expand all\r\n                        to absolute filespecs.\r\n:CList[!] {glob}        List each file that has listed errors in the quickfix\r\n:LList[!] {glob}        \/ location list that matches (with [!]: does not\r\n                        match) {glob} in a neat list. Matching and printing is\r\n                        done to the full filespec.\r\n\r\n:[range]CDoEntry {cmd}  Execute {cmd} on each entry in the quickfix \/\r\n:[range]LDoEntry {cmd}  location list (limited to buffers in [range]).\r\n\r\n:[range]CDoFile {cmd}   Execute {cmd} once on each file that appears in the\r\n:[range]LDoFile {cmd}   quickfix \/ location list (limited to buffers in\r\n                        [range]).\r\n\r\n:[range]CDoFixEntry {cmd}\r\n:[range]LDoFixEntry {cmd}\r\n                        Execute {cmd} on each entry in the quickfix \/ location\r\n                        list (limited to buffers in [range]). If the {cmd}\r\n                        does not abort and changes the buffer (i.e. increases\r\n                        b:changedtick), that entry is removed from the\r\n                        quickfix \/ location list. Else, the original entry is\r\n                        augmented with error information. (Entries for buffers\r\n                        outside [range] are kept as-is.)\r\n","install_details":"INSTALLATION\r\nThe code is hosted in a Git repo at\r\n    https:\/\/github.com\/inkarkat\/vim-ArgsAndMore\r\nYou can use your favorite plugin manager, or \"git clone\" into a directory used\r\nfor Vim packages. Releases are on the \"stable\" branch, the latest unstable\r\ndevelopment snapshot on \"master\".\r\n\r\nThis script is also packaged as a vimball. If you have the \"gunzip\"\r\ndecompressor in your PATH, simply edit the *.vmb.gz package in Vim; otherwise,\r\ndecompress the archive first, e.g. using WinZip. Inside Vim, install by\r\nsourcing the vimball or via the :UseVimball command.\r\n    vim ArgsAndMore*.vmb.gz\r\n    :so %\r\nTo uninstall, use the :RmVimball command.\r\n\r\nDEPENDENCIES\r\n- Requires Vim 7.0 or higher.\r\n- Requires the ingo-library.vim plugin (vimscript #4433), version 1.035 or\r\n  higher.\r\n\r\nCONFIGURATION\r\nAfter each {cmd}, an extra Ex command (sequence) can be executed. By default,\r\na delay of 100 ms is introduced here. This allows you to abort an interactive\r\n:s\/\/\/c substitution by pressing CTRL-C twice within the delay. (Without the\r\ndelay, it may or may not abort.) To also persist any changes to the buffer,\r\nyou could use:\r\n    let g:ArgsAndMore_AfterCommand = 'update | sleep 100m'\r\n\r\nDuring :argdo, syntax highlighting of freshly loaded buffers is turned off for\r\nperformance reasons, but for interactive commands, it is useful to have syntax\r\nhighlighting. Therefore, the :Argdo and :Bufdo commands detect interactive\r\ncommands and overrule the default syntax suppression then. By default, this\r\napplies to the :substitute command with the :s_c flag; you can adapt the\r\npattern to match other commands, too:\r\n    let g:ArgsAndMore_InteractiveCommandPattern = '...'","5":"INSTALLATION\r\nThe code is hosted in a Git repo at\r\n    https:\/\/github.com\/inkarkat\/vim-ArgsAndMore\r\nYou can use your favorite plugin manager, or \"git clone\" into a directory used\r\nfor Vim packages. Releases are on the \"stable\" branch, the latest unstable\r\ndevelopment snapshot on \"master\".\r\n\r\nThis script is also packaged as a vimball. If you have the \"gunzip\"\r\ndecompressor in your PATH, simply edit the *.vmb.gz package in Vim; otherwise,\r\ndecompress the archive first, e.g. using WinZip. Inside Vim, install by\r\nsourcing the vimball or via the :UseVimball command.\r\n    vim ArgsAndMore*.vmb.gz\r\n    :so %\r\nTo uninstall, use the :RmVimball command.\r\n\r\nDEPENDENCIES\r\n- Requires Vim 7.0 or higher.\r\n- Requires the ingo-library.vim plugin (vimscript #4433), version 1.035 or\r\n  higher.\r\n\r\nCONFIGURATION\r\nAfter each {cmd}, an extra Ex command (sequence) can be executed. By default,\r\na delay of 100 ms is introduced here. This allows you to abort an interactive\r\n:s\/\/\/c substitution by pressing CTRL-C twice within the delay. (Without the\r\ndelay, it may or may not abort.) To also persist any changes to the buffer,\r\nyou could use:\r\n    let g:ArgsAndMore_AfterCommand = 'update | sleep 100m'\r\n\r\nDuring :argdo, syntax highlighting of freshly loaded buffers is turned off for\r\nperformance reasons, but for interactive commands, it is useful to have syntax\r\nhighlighting. Therefore, the :Argdo and :Bufdo commands detect interactive\r\ncommands and overrule the default syntax suppression then. By default, this\r\napplies to the :substitute command with the :s_c flag; you can adapt the\r\npattern to match other commands, too:\r\n    let g:ArgsAndMore_InteractiveCommandPattern = '...'","first_name":"Ingo","6":"Ingo","last_name":"Karkat","7":"Karkat","releases":[{"0":"4152","vim_version":"7.0","1":"7.0","script_version":"2.11","2":"2.11","version_comment":"- Support [range] on :ArgsFilter.\r\n- Add :ArgsFilterDo variant of :ArgsFilter.\r\n- Use proper error aborting for :Bufdo, :Argdo, and :[CL]Do*.\r\n- FIX: Avoid creating jump on :bufdo \/ :windo \/ :tabdo.\r\n- Support [!] on :Bufdo[Write], :Argdo[[Confirm]Write], ArgsFilterDo to force iteration when the current buffer has unpersisted modifications and 'hidden' isn't set (just like with the built-in :argdo, :bufdo). *** You need to update to ingo-library (vimscript #4433) version 1.035! ***","3":"- Support [range] on :ArgsFilter.\r\n- Add :ArgsFilterDo variant of :ArgsFilter.\r\n- Use proper error aborting for :Bufdo, :Argdo, and :[CL]Do*.\r\n- FIX: Avoid creating jump on :bufdo \/ :windo \/ :tabdo.\r\n- Support [!] on :Bufdo[Write], :Argdo[[Confirm]Write], ArgsFilterDo to force iteration when the current buffer has unpersisted modifications and 'hidden' isn't set (just like with the built-in :argdo, :bufdo). *** You need to update to ingo-library (vimscript #4433) version 1.035! ***","package":"ArgsAndMore-2.11.vmb.gz","4":"ArgsAndMore-2.11.vmb.gz","src_id":"26530","5":"26530","creation_date":"1560134989","6":"1560134989"},{"0":"4152","vim_version":"7.0","1":"7.0","script_version":"2.10","2":"2.10","version_comment":"- FIX: :Bufdo..., :Win..., :Tab... in recent Vim 7.4 defaults to wrong range. Forgot -range=% argument.\r\n- Add :CDoFile, :CDoEntry, :CDoFixEntry commands for iteration over quickfix \/ location list.","3":"- FIX: :Bufdo..., :Win..., :Tab... in recent Vim 7.4 defaults to wrong range. Forgot -range=% argument.\r\n- Add :CDoFile, :CDoEntry, :CDoFixEntry commands for iteration over quickfix \/ location list.","package":"ArgsAndMore-2.10.vmb.gz","4":"ArgsAndMore-2.10.vmb.gz","src_id":"22988","5":"22988","creation_date":"1425845141","6":"1425845141"},{"0":"4152","vim_version":"7.0","1":"7.0","script_version":"2.00","2":"2.00","version_comment":"- Use ingo#msg#WarningMsg().\r\n- ENH: Keep previous (last accessed) window on :Windo. Thanks to Daniel Hahler for the patch.\r\n- ENH: Keep alternate buffer (#) on :Argdo and :Bufdo commands. Thanks to Daniel Hahler for the suggestion.\r\n- Handle modified buffers together with :set nohidden when restoring the original buffer after :Argdo and :Bufdo by using :hide.\r\n- FIX: :Argdo may fail to restore the original buffer. Ensure that argidx() actually points to valid argument; this may not be the case when arguments have only been :argadd'ed, but not visited yet.\r\n- Support the -addr=arguments attribute in Vim 7.4.530 or later for :Argdo... commands. With that, relative addressing can also be used non-interactively.\r\n- Support ranges in :Bufdo..., :Windo..., :Tabdo... if supported by Vim.\r\n- Support ranges in :ArgsList and :ArgsToQuickfix if supported by Vim.\r\n- Switch to ingo#regexp#fromwildcard#AnchoredToPathBoundaries() to correctly enforce path boundaries in :ArgsList {glob}. *** You need to update to ingo-library (vimscript #4433) version 1.023! ***","3":"- Use ingo#msg#WarningMsg().\r\n- ENH: Keep previous (last accessed) window on :Windo. Thanks to Daniel Hahler for the patch.\r\n- ENH: Keep alternate buffer (#) on :Argdo and :Bufdo commands. Thanks to Daniel Hahler for the suggestion.\r\n- Handle modified buffers together with :set nohidden when restoring the original buffer after :Argdo and :Bufdo by using :hide.\r\n- FIX: :Argdo may fail to restore the original buffer. Ensure that argidx() actually points to valid argument; this may not be the case when arguments have only been :argadd'ed, but not visited yet.\r\n- Support the -addr=arguments attribute in Vim 7.4.530 or later for :Argdo... commands. With that, relative addressing can also be used non-interactively.\r\n- Support ranges in :Bufdo..., :Windo..., :Tabdo... if supported by Vim.\r\n- Support ranges in :ArgsList and :ArgsToQuickfix if supported by Vim.\r\n- Switch to ingo#regexp#fromwildcard#AnchoredToPathBoundaries() to correctly enforce path boundaries in :ArgsList {glob}. *** You need to update to ingo-library (vimscript #4433) version 1.023! ***","package":"ArgsAndMore-2.00.vmb.gz","4":"ArgsAndMore-2.00.vmb.gz","src_id":"22897","5":"22897","creation_date":"1423481458","6":"1423481458"},{"0":"4152","vim_version":"7.0","1":"7.0","script_version":"1.22","2":"1.22","version_comment":"- Add :CList and :LList, analog to :ArgsList.\r\n- FIX: :ArgsList printed \"cnt\" is zero-based, not 1-based.\r\n- Add :ArgdoConfirmWrite variant of :ArgdoWrite.\r\n- Also catch custom exceptions and errors caused by the passed user command (or configured post-command). *** You need to update to ingo-library (vimscript #4433) version 1.017! ***","3":"- Add :CList and :LList, analog to :ArgsList.\r\n- FIX: :ArgsList printed \"cnt\" is zero-based, not 1-based.\r\n- Add :ArgdoConfirmWrite variant of :ArgdoWrite.\r\n- Also catch custom exceptions and errors caused by the passed user command (or configured post-command). *** You need to update to ingo-library (vimscript #4433) version 1.017! ***","package":"ArgsAndMore-1.22.vmb.gz","4":"ArgsAndMore-1.22.vmb.gz","src_id":"21660","5":"21660","creation_date":"1395676290","6":"1395676290"},{"0":"4152","vim_version":"7.0","1":"7.0","script_version":"1.21","2":"1.21","version_comment":"- FIX: Use the rules for the \/pattern\/ separator as stated in :help E146 in the default of g:ArgsAndMore_InteractiveCommandPattern.\r\n- Minor: Exclude further special buffers from syntax enabling.\r\n- :ArgsList also handles ** and [...] wildcards.\r\n- Move escapings.vim into ingo-library. *** You need to update to ingo-library (vimscript #4433) version 1.014! ***","3":"- FIX: Use the rules for the \/pattern\/ separator as stated in :help E146 in the default of g:ArgsAndMore_InteractiveCommandPattern.\r\n- Minor: Exclude further special buffers from syntax enabling.\r\n- :ArgsList also handles ** and [...] wildcards.\r\n- Move escapings.vim into ingo-library. *** You need to update to ingo-library (vimscript #4433) version 1.014! ***","package":"ArgsAndMore-1.21.vmb.gz","4":"ArgsAndMore-1.21.vmb.gz","src_id":"21092","5":"21092","creation_date":"1385132770","6":"1385132770"},{"0":"4152","vim_version":"7.0","1":"7.0","script_version":"1.20","2":"1.20","version_comment":"- Add dependency to ingo-library (vimscript #4433). *** You need to separately install ingo-library (vimscript #4433) version 1.007 (or higher)! ***\r\n- ENH: Add :ArgdoWrite and :BufdoWrite variants that also perform an automatic :update.\r\n- ENH: Add errors from :Argdo and :BufDo to the quickfix list to allow easier rework.\r\n- Avoid script errors when using :Argdo 3s\/foo\/bar\r\n- ENH: Enable syntax highlighting on :Argdo \/ :Bufdo on freshly loaded buffers when the command is an interactive one (:s\/\/\/c, according to g:ArgsAndMore_InteractiveCommandPattern), but for performance reasons not in the general case.\r\n- In :{range}Argdo, emulate the behavior of the built-in :argdo to disable syntax highlighting during to speed up the iteration, but consider our own enhancement, the exception for interactive commands.","3":"- Add dependency to ingo-library (vimscript #4433). *** You need to separately install ingo-library (vimscript #4433) version 1.007 (or higher)! ***\r\n- ENH: Add :ArgdoWrite and :BufdoWrite variants that also perform an automatic :update.\r\n- ENH: Add errors from :Argdo and :BufDo to the quickfix list to allow easier rework.\r\n- Avoid script errors when using :Argdo 3s\/foo\/bar\r\n- ENH: Enable syntax highlighting on :Argdo \/ :Bufdo on freshly loaded buffers when the command is an interactive one (:s\/\/\/c, according to g:ArgsAndMore_InteractiveCommandPattern), but for performance reasons not in the general case.\r\n- In :{range}Argdo, emulate the behavior of the built-in :argdo to disable syntax highlighting during to speed up the iteration, but consider our own enhancement, the exception for interactive commands.","package":"ArgsAndMore-1.20.vmb.gz","4":"ArgsAndMore-1.20.vmb.gz","src_id":"20542","5":"20542","creation_date":"1374230892","6":"1374230892"},{"0":"4152","vim_version":"7.0","1":"7.0","script_version":"1.11","2":"1.11","version_comment":"FIX: Factor out s:sort() and also use numerical sort in the one missed case.","3":"FIX: Factor out s:sort() and also use numerical sort in the one missed case.","package":"ArgsAndMore-1.11.vmb.gz","4":"ArgsAndMore-1.11.vmb.gz","src_id":"19404","5":"19404","creation_date":"1358754272","6":"1358754272"},{"0":"4152","vim_version":"7.0","1":"7.0","script_version":"1.10","2":"1.10","version_comment":"- Add g:ArgsAndMore_AfterCommand hook before buffer switching and use this by default to add a small delay, which allows for aborting an interactive s\/\/\/c substitution by pressing CTRL-C twice within the delay.\r\n- Add :Bufdo command for completeness, to get the new hook, and the enhanced error reporting of :Argdo.","3":"- Add g:ArgsAndMore_AfterCommand hook before buffer switching and use this by default to add a small delay, which allows for aborting an interactive s\/\/\/c substitution by pressing CTRL-C twice within the delay.\r\n- Add :Bufdo command for completeness, to get the new hook, and the enhanced error reporting of :Argdo.","package":"ArgsAndMore-1.10.vmb.gz","4":"ArgsAndMore-1.10.vmb.gz","src_id":"18580","5":"18580","creation_date":"1347274538","6":"1347274538"},{"0":"4152","vim_version":"7.0","1":"7.0","script_version":"1.01","2":"1.01","version_comment":"- Do not use <f-args> because of its unescaping behavior.\r\n- FIX: \"E480: No match\" on :ArgsNegated with ..\/other\/path relative argument; need to issue a dummy :chdir to convert relative args before doing the :argdelete.","3":"- Do not use <f-args> because of its unescaping behavior.\r\n- FIX: \"E480: No match\" on :ArgsNegated with ..\/other\/path relative argument; need to issue a dummy :chdir to convert relative args before doing the :argdelete.","package":"ArgsAndMore-1.01.vmb.gz","4":"ArgsAndMore-1.01.vmb.gz","src_id":"18504","5":"18504","creation_date":"1346154177","6":"1346154177"},{"0":"4152","vim_version":"7.0","1":"7.0","script_version":"1.00","2":"1.00","version_comment":"Initial upload","3":"Initial upload","package":"ArgsAndMore.vba.gz","4":"ArgsAndMore.vba.gz","src_id":"18348","5":"18348","creation_date":"1343676258","6":"1343676258"}]},"4151":{"script_id":"4151","0":"4151","script_name":"vlog_inst_gen","1":"vlog_inst_gen","script_type":"utility","2":"utility","summary":"utility for verilog instance generation","3":"utility for verilog instance generation","description":"This script is used for automatically generating verilog instance from the file. When you type the given hot-key, instance will be copied to system clipboard, and display or not by  its working mode. Once your file can access syntax check, this plunin will work, or there must be a bug. It's encouraged to share it with me and all other people.\r\n\r\nSupported working mode:\r\n    mode 0(default): \r\n        copy inst to clipboard and echo inst in commandline\r\n    mode 1:\r\n        only copy to clipboard\r\n    mode 2:\r\n        copy to clipboard and echo inst in split window\r\n    mode 3:\r\n        copy to clipboard and update inst_comment to file\r\n    \r\n  To change the default working mode, you should modify the line in this script \"let g:vlog_inst_gen_mode=x\", x is the default working mode; or you can add  \"let g:vlog_inst_gen_mode=x\" to your _vimrc or .vimrc file.\r\n\r\nUser defined command:\r\n        VlogInstGen : generate verilog instance\r\n        VlogInstMod : change working mode\r\nDefault hot-keys:\r\n        ,ig         : VlogInstGen\r\n        ,im        : VlogInstMod\r\nContact:\r\n        mingforregister@163.com\r\n\r\nv1.6 md5sum: 5dcf0cb9f833ff77c03cfd4e1bfbbe48\r\nThis version can work in both windows and linux, when used in linux do not need dos2unix any more!","4":"This script is used for automatically generating verilog instance from the file. When you type the given hot-key, instance will be copied to system clipboard, and display or not by  its working mode. Once your file can access syntax check, this plunin will work, or there must be a bug. It's encouraged to share it with me and all other people.\r\n\r\nSupported working mode:\r\n    mode 0(default): \r\n        copy inst to clipboard and echo inst in commandline\r\n    mode 1:\r\n        only copy to clipboard\r\n    mode 2:\r\n        copy to clipboard and echo inst in split window\r\n    mode 3:\r\n        copy to clipboard and update inst_comment to file\r\n    \r\n  To change the default working mode, you should modify the line in this script \"let g:vlog_inst_gen_mode=x\", x is the default working mode; or you can add  \"let g:vlog_inst_gen_mode=x\" to your _vimrc or .vimrc file.\r\n\r\nUser defined command:\r\n        VlogInstGen : generate verilog instance\r\n        VlogInstMod : change working mode\r\nDefault hot-keys:\r\n        ,ig         : VlogInstGen\r\n        ,im        : VlogInstMod\r\nContact:\r\n        mingforregister@163.com\r\n\r\nv1.6 md5sum: 5dcf0cb9f833ff77c03cfd4e1bfbbe48\r\nThis version can work in both windows and linux, when used in linux do not need dos2unix any more!","install_details":"Only tested in gvim7.3 for windows version, it may works well in linux, you can try.\r\nMethod1: copy this file to your $VIM_HOME\/vim74\/plugin, recommanded!\r\nMethod2: \r\ncopy the vlog_inst_gen.vim file to $VLOG_INST_GEN_DIR\r\nadded the following to your vimrc(_vimrc for windows and .vimrc for linux)\r\nso $VLOG_INST_GEN_DIR\/vlog_inst_gen.vim\r\n\r\n","5":"Only tested in gvim7.3 for windows version, it may works well in linux, you can try.\r\nMethod1: copy this file to your $VIM_HOME\/vim74\/plugin, recommanded!\r\nMethod2: \r\ncopy the vlog_inst_gen.vim file to $VLOG_INST_GEN_DIR\r\nadded the following to your vimrc(_vimrc for windows and .vimrc for linux)\r\nso $VLOG_INST_GEN_DIR\/vlog_inst_gen.vim\r\n\r\n","first_name":"wenming","6":"wenming","last_name":"zhang","7":"zhang","releases":[{"0":"4151","vim_version":"7.4","1":"7.4","script_version":"1.6","2":"1.6","version_comment":"1. Thank LongTang for bugs feedback\r\n2. Fix bug when used in linux and ports more than 100\r\n3. Run faster than before\r\n","3":"1. Thank LongTang for bugs feedback\r\n2. Fix bug when used in linux and ports more than 100\r\n3. Run faster than before\r\n","package":"vlog_inst_gen.vim","4":"vlog_inst_gen.vim","src_id":"28073","5":"28073","creation_date":"1654771170","6":"1654771170"},{"0":"4151","vim_version":"7.4","1":"7.4","script_version":"1.5","2":"1.5","version_comment":"1. Thank LongTang for bugs feedback\r\n2. Parameter support keywords signed\/integer\/real\/realtime\/time\r\n3. Support `ifdef\/`else\/`endif in module port declearation\r\n4. Disable port declearation check","3":"1. Thank LongTang for bugs feedback\r\n2. Parameter support keywords signed\/integer\/real\/realtime\/time\r\n3. Support `ifdef\/`else\/`endif in module port declearation\r\n4. Disable port declearation check","package":"vlog_inst_gen.vim","4":"vlog_inst_gen.vim","src_id":"25540","5":"25540","creation_date":"1504059542","6":"1504059542"},{"0":"4151","vim_version":"7.3","1":"7.3","script_version":"1.4","2":"1.4","version_comment":"add one feature: \r\ncopy instance also to clickboard \", so that you can use key 'p' to paste it. Also you can disable this feature by modifying  this script's line:\r\n    let g:is_copy_inst_to_doublequotation = 1\r\nto:\r\n    let g:is_copy_inst_to_doublequotation = 0\r\n","3":"add one feature: \r\ncopy instance also to clickboard \", so that you can use key 'p' to paste it. Also you can disable this feature by modifying  this script's line:\r\n    let g:is_copy_inst_to_doublequotation = 1\r\nto:\r\n    let g:is_copy_inst_to_doublequotation = 0\r\n","package":"vlog_inst_gen.vim","4":"vlog_inst_gen.vim","src_id":"18437","5":"18437","creation_date":"1345471449","6":"1345471449"},{"0":"4151","vim_version":"7.3","1":"7.3","script_version":"1.3","2":"1.3","version_comment":"only modified a little that you can't feel..","3":"only modified a little that you can't feel..","package":"vlog_inst_gen.vim","4":"vlog_inst_gen.vim","src_id":"18374","5":"18374","creation_date":"1344329472","6":"1344329472"},{"0":"4151","vim_version":"7.3","1":"7.3","script_version":"1.2","2":"1.2","version_comment":"1. add user defined command:\r\n        VlogInstGen and VlogInstMod\r\n2. change key-mapping to ,ig and ,im\r\n        ig: instance generation\r\n        im: instance mode\r\n3. add my voice to zhizhi\r\n        hot-key:,zz  ,,,  ,tc","3":"1. add user defined command:\r\n        VlogInstGen and VlogInstMod\r\n2. change key-mapping to ,ig and ,im\r\n        ig: instance generation\r\n        im: instance mode\r\n3. add my voice to zhizhi\r\n        hot-key:,zz  ,,,  ,tc","package":"vlog_inst_gen.vim","4":"vlog_inst_gen.vim","src_id":"18343","5":"18343","creation_date":"1343635362","6":"1343635362"},{"0":"4151","vim_version":"7.3","1":"7.3","script_version":"1.1","2":"1.1","version_comment":"Add working mode information to file head...\r\nUpdate file head information; \r\nRemove test functions; \r\nRemove additional records when I debugging; \r\nRemove additional key-map(eg. reload this script) ","3":"Add working mode information to file head...\r\nUpdate file head information; \r\nRemove test functions; \r\nRemove additional records when I debugging; \r\nRemove additional key-map(eg. reload this script) ","package":"vlog_inst_gen.vim","4":"vlog_inst_gen.vim","src_id":"18342","5":"18342","creation_date":"1343617510","6":"1343617510"},{"0":"4151","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"vlog_inst_gen.vim","4":"vlog_inst_gen.vim","src_id":"18339","5":"18339","creation_date":"1343611801","6":"1343611801"}]},"4150":{"script_id":"4150","0":"4150","script_name":"forms","1":"forms","script_type":"utility","2":"utility","summary":"Vim Forms TUI libraray","3":"Vim Forms TUI libraray","description":"Forms is a Vim TUI (Text User Interface) library. It allows for the creation\r\nand display of text-based forms in both console Vim and GVim. Many of the\r\nstandard GUI widget types are supported by Forms such as labels, buttons,\r\nmenus and layout constructs. It supports navigation, selection and input with\r\na keyboard, as well as, navigation and selection with a mouse.\r\n\r\nScreen-shot (background: dark\/light) of clone of GVim menu\/popup:\r\nhttps:\/\/github.com\/megaannum\/forms\/tree\/master\/images\/menu_file.png\r\nhttps:\/\/github.com\/megaannum\/forms\/tree\/master\/images\/menu_edit_colorscheme.png\r\nhttps:\/\/github.com\/megaannum\/forms\/tree\/master\/images\/popup_change.png\r\n\r\nSome example (background: dark\/light) forms from the \"Examples\" form:\r\nhttps:\/\/github.com\/megaannum\/forms\/tree\/master\/images\/examples.png\r\nhttps:\/\/github.com\/megaannum\/forms\/tree\/master\/images\/examples_andmorelabels.png\r\nhttps:\/\/github.com\/megaannum\/forms\/tree\/master\/images\/examples_boxchars.png\r\nhttps:\/\/github.com\/megaannum\/forms\/tree\/master\/images\/examples_checkboxes.png\r\nhttps:\/\/github.com\/megaannum\/forms\/tree\/master\/images\/examples_colorchooser.png\r\nhttps:\/\/github.com\/megaannum\/forms\/tree\/master\/images\/examples_confirmchoice.png\r\nhttps:\/\/github.com\/megaannum\/forms\/tree\/master\/images\/examples_dropshodow.png\r\nhttps:\/\/github.com\/megaannum\/forms\/tree\/master\/images\/examples_filebrowser.png\r\nhttps:\/\/github.com\/megaannum\/forms\/tree\/master\/images\/examples_fixedlayout.png\r\nhttps:\/\/github.com\/megaannum\/forms\/tree\/master\/images\/examples_foureditors.png\r\nhttps:\/\/github.com\/megaannum\/forms\/tree\/master\/images\/examples_frames.png\r\nhttps:\/\/github.com\/megaannum\/forms\/tree\/master\/images\/examples_getinput.png\r\nhttps:\/\/github.com\/megaannum\/forms\/tree\/master\/images\/examples_information.png\r\nhttps:\/\/github.com\/megaannum\/forms\/tree\/master\/images\/examples_labelsingrid.png\r\nhttps:\/\/github.com\/megaannum\/forms\/tree\/master\/images\/examples_labels.png\r\nhttps:\/\/github.com\/megaannum\/forms\/tree\/master\/images\/examples_menusubmenu.png\r\nhttps:\/\/github.com\/megaannum\/forms\/tree\/master\/images\/examples_morelabels.png\r\nhttps:\/\/github.com\/megaannum\/forms\/tree\/master\/images\/examples_palletdesigner.png\r\nhttps:\/\/github.com\/megaannum\/forms\/tree\/master\/images\/examples_popdownlist.png\r\nhttps:\/\/github.com\/megaannum\/forms\/tree\/master\/images\/examples_radiobuttons.png\r\nhttps:\/\/github.com\/megaannum\/forms\/tree\/master\/images\/examples_resize.png\r\nhttps:\/\/github.com\/megaannum\/forms\/tree\/master\/images\/examples_runtimepathviewer.png\r\nhttps:\/\/github.com\/megaannum\/forms\/tree\/master\/images\/examples_selectlists.png\r\nhttps:\/\/github.com\/megaannum\/forms\/tree\/master\/images\/examples_sliders.png\r\nhttps:\/\/github.com\/megaannum\/forms\/tree\/master\/images\/examples_subform.png\r\nhttps:\/\/github.com\/megaannum\/forms\/tree\/master\/images\/examples_texteditor.png\r\nhttps:\/\/github.com\/megaannum\/forms\/tree\/master\/images\/examples_textsearch.png\r\nhttps:\/\/github.com\/megaannum\/forms\/tree\/master\/images\/examples_textsearchreplace.png\r\nhttps:\/\/github.com\/megaannum\/forms\/tree\/master\/images\/examples_togglebuttons.png\r\nhttps:\/\/github.com\/megaannum\/forms\/tree\/master\/images\/examples_vimhomeviewer.png\r\nhttps:\/\/github.com\/megaannum\/forms\/tree\/master\/images\/examples_vlabels.png\r\n\r\nCode for the above examples can be found at:\r\nhttps:\/\/github.com\/megaannum\/forms\/blob\/master\/autoload\/forms\/menu.vim\r\nhttps:\/\/github.com\/megaannum\/forms\/tree\/master\/autoload\/forms\/dialog\r\nhttps:\/\/github.com\/megaannum\/forms\/tree\/master\/autoload\/forms\/example\r\n\r\nForms tutorial:\r\nhttps:\/\/github.com\/megaannum\/forms\/blob\/master\/tutorial\/forms\/Tutorial.md\r\n\r\nA user can always stop a form with no side effects by entering <Esc>.\r\nThis is basically a \"panic button\"; the user wants out.\r\nIf the user is a couple of sub-forms deep in a presentation, each <Esc>\r\nentered pops the user out of the current form only.\r\nDevelopers should be aware that a user might not take any of the actions\r\noffered by a form and simply enter <Esc>. Such user action, <Esc>\r\nto exit Forms, should NOT be prevented by a forms developer.\r\n\r\nThe behavior of a form created with the Forms library differs from that of a\r\nGUI form. Generally, a GUI form can be displayed and moved about anywhere on\r\nthe screen. On the other hand, a TUI form has to reside within the Vim\/GVim\r\nwindow; it can not be moved outside of the text area. In addition, when a form\r\nis being displayed, it captures all user input, keyboard and mouse in that\r\nwindow, so that there is no access to the underlying text until the form is\r\nclosed. In that sense, all Forms forms are like modal GUI forms.\r\n\r\nBecause a form must fit within a text window, it is sometimes the case that\r\nthe form's height and\/or width is greater than that of the hosting window.\r\nForm developer should be aware of this and strive to make their forms\r\nsmaller than expected window sizes. One approach is to break a large form\r\ninto a number of sub-forms.\r\nIn case a form is too big, an information form is displayed to the user\r\nstating that fact along with a suggested size to enlarge the window to\r\nso that the form will fit. If the window is too small even to display\r\nthe information form, an error message is output (via a thrown exception).\r\n\r\nA form can be displayed over the current text or the form can create a new tab\r\nand displayed there.\r\n\r\nStrictly speaking, the Forms library is a library and, so, there ought not\r\nbe any mappings. But, while developing Forms a number of examples were\r\ncreated which, it turns out, were critical for uncovering bugs, missing\r\nfeatures in the implementation and usage issues. Two of the examples\r\nmight have general appeal, the menu and popup forms that mirror the\r\ncapability (and copy some of the support code of) the GVim menu and popup.\r\nWhile power users will disdain the Forms menu and popup examples\r\nas superfluous, covering Vim commands that are know by heart, so to\r\npower users disdain the GVim menu\/popup - so, the power user is not\r\nthe target user.  Rather, the same users that find the GVim menu\/popup\r\nuseful will find the Forms menu\/popup equally useful.\r\nHere are the mappings for the menu and popup:\r\n\r\n    nmap <Leader>m :call forms#menu#MakeMenu('n')<CR>\r\n    vmap <Leader>m :call forms#menu#MakeMenu('v')<CR>\r\n    nmap <Leader>p :call forms#menu#MakePopUp('n')<CR>\r\n    vmap <Leader>p :call forms#menu#MakePopUp('v')<CR>\r\n\r\nIt should be noted that there are normal and visual mode mappings.\r\nThat is because some capabilities of the menu\/popup are enabled\/disabled\r\ndepending upon mode, as well as, which command to ultimately execute\r\nmay depend upon mode.\r\n\r\nThere is also a mapping which launches a form that links to some 40 Forms\r\ndemonstration forms. The demonstration forms range from a simple box\r\ndrawing example to a file browser and color chooser:\r\n\r\n    nmap <Leader>d :call forms#example#demo#Make()<CR>\r\n\r\nIf any of the demonstration forms do not display or function as one might\r\nexpect on your platform, then drop me a line - thanks.\r\n\r\nOne will observe that these mappings use the characters: 'm' 'p' and 'd'.\r\nWhile the demo mapping can\/should ultimately be commented out by\r\nall but Forms developers, at least for the non-power user, having\r\na short, easy to remember, mnemonic mapping for menu and popup is certainly\r\nreasonable.\r\n\r\nSource can be found at: https:\/\/github.com\/megaannum\/forms\r\n\r\nThe Forms library is currently being used in the following scripts:\r\nColorschemer utility\r\n  http:\/\/www.vim.org\/scripts\/script.php?script_id=4240\r\nVimside, Vim Scala IDE\r\n  http:\/\/www.vim.org\/scripts\/script.php?script_id=4298\r\n","4":"Forms is a Vim TUI (Text User Interface) library. It allows for the creation\r\nand display of text-based forms in both console Vim and GVim. Many of the\r\nstandard GUI widget types are supported by Forms such as labels, buttons,\r\nmenus and layout constructs. It supports navigation, selection and input with\r\na keyboard, as well as, navigation and selection with a mouse.\r\n\r\nScreen-shot (background: dark\/light) of clone of GVim menu\/popup:\r\nhttps:\/\/github.com\/megaannum\/forms\/tree\/master\/images\/menu_file.png\r\nhttps:\/\/github.com\/megaannum\/forms\/tree\/master\/images\/menu_edit_colorscheme.png\r\nhttps:\/\/github.com\/megaannum\/forms\/tree\/master\/images\/popup_change.png\r\n\r\nSome example (background: dark\/light) forms from the \"Examples\" form:\r\nhttps:\/\/github.com\/megaannum\/forms\/tree\/master\/images\/examples.png\r\nhttps:\/\/github.com\/megaannum\/forms\/tree\/master\/images\/examples_andmorelabels.png\r\nhttps:\/\/github.com\/megaannum\/forms\/tree\/master\/images\/examples_boxchars.png\r\nhttps:\/\/github.com\/megaannum\/forms\/tree\/master\/images\/examples_checkboxes.png\r\nhttps:\/\/github.com\/megaannum\/forms\/tree\/master\/images\/examples_colorchooser.png\r\nhttps:\/\/github.com\/megaannum\/forms\/tree\/master\/images\/examples_confirmchoice.png\r\nhttps:\/\/github.com\/megaannum\/forms\/tree\/master\/images\/examples_dropshodow.png\r\nhttps:\/\/github.com\/megaannum\/forms\/tree\/master\/images\/examples_filebrowser.png\r\nhttps:\/\/github.com\/megaannum\/forms\/tree\/master\/images\/examples_fixedlayout.png\r\nhttps:\/\/github.com\/megaannum\/forms\/tree\/master\/images\/examples_foureditors.png\r\nhttps:\/\/github.com\/megaannum\/forms\/tree\/master\/images\/examples_frames.png\r\nhttps:\/\/github.com\/megaannum\/forms\/tree\/master\/images\/examples_getinput.png\r\nhttps:\/\/github.com\/megaannum\/forms\/tree\/master\/images\/examples_information.png\r\nhttps:\/\/github.com\/megaannum\/forms\/tree\/master\/images\/examples_labelsingrid.png\r\nhttps:\/\/github.com\/megaannum\/forms\/tree\/master\/images\/examples_labels.png\r\nhttps:\/\/github.com\/megaannum\/forms\/tree\/master\/images\/examples_menusubmenu.png\r\nhttps:\/\/github.com\/megaannum\/forms\/tree\/master\/images\/examples_morelabels.png\r\nhttps:\/\/github.com\/megaannum\/forms\/tree\/master\/images\/examples_palletdesigner.png\r\nhttps:\/\/github.com\/megaannum\/forms\/tree\/master\/images\/examples_popdownlist.png\r\nhttps:\/\/github.com\/megaannum\/forms\/tree\/master\/images\/examples_radiobuttons.png\r\nhttps:\/\/github.com\/megaannum\/forms\/tree\/master\/images\/examples_resize.png\r\nhttps:\/\/github.com\/megaannum\/forms\/tree\/master\/images\/examples_runtimepathviewer.png\r\nhttps:\/\/github.com\/megaannum\/forms\/tree\/master\/images\/examples_selectlists.png\r\nhttps:\/\/github.com\/megaannum\/forms\/tree\/master\/images\/examples_sliders.png\r\nhttps:\/\/github.com\/megaannum\/forms\/tree\/master\/images\/examples_subform.png\r\nhttps:\/\/github.com\/megaannum\/forms\/tree\/master\/images\/examples_texteditor.png\r\nhttps:\/\/github.com\/megaannum\/forms\/tree\/master\/images\/examples_textsearch.png\r\nhttps:\/\/github.com\/megaannum\/forms\/tree\/master\/images\/examples_textsearchreplace.png\r\nhttps:\/\/github.com\/megaannum\/forms\/tree\/master\/images\/examples_togglebuttons.png\r\nhttps:\/\/github.com\/megaannum\/forms\/tree\/master\/images\/examples_vimhomeviewer.png\r\nhttps:\/\/github.com\/megaannum\/forms\/tree\/master\/images\/examples_vlabels.png\r\n\r\nCode for the above examples can be found at:\r\nhttps:\/\/github.com\/megaannum\/forms\/blob\/master\/autoload\/forms\/menu.vim\r\nhttps:\/\/github.com\/megaannum\/forms\/tree\/master\/autoload\/forms\/dialog\r\nhttps:\/\/github.com\/megaannum\/forms\/tree\/master\/autoload\/forms\/example\r\n\r\nForms tutorial:\r\nhttps:\/\/github.com\/megaannum\/forms\/blob\/master\/tutorial\/forms\/Tutorial.md\r\n\r\nA user can always stop a form with no side effects by entering <Esc>.\r\nThis is basically a \"panic button\"; the user wants out.\r\nIf the user is a couple of sub-forms deep in a presentation, each <Esc>\r\nentered pops the user out of the current form only.\r\nDevelopers should be aware that a user might not take any of the actions\r\noffered by a form and simply enter <Esc>. Such user action, <Esc>\r\nto exit Forms, should NOT be prevented by a forms developer.\r\n\r\nThe behavior of a form created with the Forms library differs from that of a\r\nGUI form. Generally, a GUI form can be displayed and moved about anywhere on\r\nthe screen. On the other hand, a TUI form has to reside within the Vim\/GVim\r\nwindow; it can not be moved outside of the text area. In addition, when a form\r\nis being displayed, it captures all user input, keyboard and mouse in that\r\nwindow, so that there is no access to the underlying text until the form is\r\nclosed. In that sense, all Forms forms are like modal GUI forms.\r\n\r\nBecause a form must fit within a text window, it is sometimes the case that\r\nthe form's height and\/or width is greater than that of the hosting window.\r\nForm developer should be aware of this and strive to make their forms\r\nsmaller than expected window sizes. One approach is to break a large form\r\ninto a number of sub-forms.\r\nIn case a form is too big, an information form is displayed to the user\r\nstating that fact along with a suggested size to enlarge the window to\r\nso that the form will fit. If the window is too small even to display\r\nthe information form, an error message is output (via a thrown exception).\r\n\r\nA form can be displayed over the current text or the form can create a new tab\r\nand displayed there.\r\n\r\nStrictly speaking, the Forms library is a library and, so, there ought not\r\nbe any mappings. But, while developing Forms a number of examples were\r\ncreated which, it turns out, were critical for uncovering bugs, missing\r\nfeatures in the implementation and usage issues. Two of the examples\r\nmight have general appeal, the menu and popup forms that mirror the\r\ncapability (and copy some of the support code of) the GVim menu and popup.\r\nWhile power users will disdain the Forms menu and popup examples\r\nas superfluous, covering Vim commands that are know by heart, so to\r\npower users disdain the GVim menu\/popup - so, the power user is not\r\nthe target user.  Rather, the same users that find the GVim menu\/popup\r\nuseful will find the Forms menu\/popup equally useful.\r\nHere are the mappings for the menu and popup:\r\n\r\n    nmap <Leader>m :call forms#menu#MakeMenu('n')<CR>\r\n    vmap <Leader>m :call forms#menu#MakeMenu('v')<CR>\r\n    nmap <Leader>p :call forms#menu#MakePopUp('n')<CR>\r\n    vmap <Leader>p :call forms#menu#MakePopUp('v')<CR>\r\n\r\nIt should be noted that there are normal and visual mode mappings.\r\nThat is because some capabilities of the menu\/popup are enabled\/disabled\r\ndepending upon mode, as well as, which command to ultimately execute\r\nmay depend upon mode.\r\n\r\nThere is also a mapping which launches a form that links to some 40 Forms\r\ndemonstration forms. The demonstration forms range from a simple box\r\ndrawing example to a file browser and color chooser:\r\n\r\n    nmap <Leader>d :call forms#example#demo#Make()<CR>\r\n\r\nIf any of the demonstration forms do not display or function as one might\r\nexpect on your platform, then drop me a line - thanks.\r\n\r\nOne will observe that these mappings use the characters: 'm' 'p' and 'd'.\r\nWhile the demo mapping can\/should ultimately be commented out by\r\nall but Forms developers, at least for the non-power user, having\r\na short, easy to remember, mnemonic mapping for menu and popup is certainly\r\nreasonable.\r\n\r\nSource can be found at: https:\/\/github.com\/megaannum\/forms\r\n\r\nThe Forms library is currently being used in the following scripts:\r\nColorschemer utility\r\n  http:\/\/www.vim.org\/scripts\/script.php?script_id=4240\r\nVimside, Vim Scala IDE\r\n  http:\/\/www.vim.org\/scripts\/script.php?script_id=4298\r\n","install_details":"Download forms.zip and unzip in $HOME\/.vim.After unpacking the {Forms} directory\r\nlayout should look like:\r\n    $HOME\/.vim\/\r\n      autoload\/\r\n        forms.vim\r\n        forms\/\r\n          menu.vim\r\n          dialog\/...\r\n          examples\/...\r\n      doc\/forms.vim\r\n      plugin\/forms.vim\r\n      tutorial\/forms\/...\r\n\r\nIntalling with vim-addon-manager (VAM)\r\n\r\nFor more information about vim-addon-manager, see\r\n[vim-addon-manager](https:\/\/github.com\/MarcWeber\/vim-addon-manager) and\r\n[Vim-addon-manager getting\r\nstarted](https:\/\/github.com\/MarcWeber\/vim-addon-manager\/blob\/master\/doc\/vim-addon-manager-getting-started.txt)\r\n\r\nIn your .vimrc, add self as shown below:\r\n\r\n    fun SetupVAM()\r\n      ...\r\n      let g:vim_addon_manager = {}\r\n      let g:vim_addon_manager.plugin_sources = {}\r\n      ....\r\n      let g:vim_addon_manager.plugin_sources['self'] = {'type': 'git', 'url':\r\n'git:\/\/github.com\/megaannum\/self'}\r\n      let g:vim_addon_manager.plugin_sources['forms'] = {'type': 'git', 'url':\r\n'git:\/\/github.com\/megaannum\/forms'}\r\n\r\n\r\n      let plugins = [\r\n        \\ 'self',\r\n        \\ 'forms'\r\n        \\ ]\r\n\r\n      call vam#ActivateAddons(plugins,{'auto_install' : 0})\r\n      ...\r\n    endf\r\n    call SetupVAM()\r\n\r\nNow start Vim. You will be asked by vim-addon-manager\r\nif you would like to download and install the self plugin (no dependencies).\r\n\r\nInstalling with pathogen\r\n\r\nI do not use pathogen. An example usage would be welcome.\r\n\r\nConfiguring Xterm and .vimrc for Forms\r\n\r\nFor console-base Vim running in an Xterm, the font used by Vim is the font\r\nused by the Xterm. Running on my Linux systems I found the following\r\nworks to launch an Xterm appropriately configured: >\r\n    \/usr\/bin\/xterm -g 80x30 -bg lightgrey -sl 1000 +si -fn \\\r\n       '-misc-fixed-medium-r-normal-*-20-*-*-*-*-*-iso10646-*'\r\nIf with say, the font 10x20, then you may not be able to render all of\r\nthe unicode characters, but it ought to still work.\r\n\r\nThere is support for 256, 88, 16 and 8 color Xterms though\r\nthe 256 looks best. In your .vimrc file add one of:\r\n    if ($TERM == 'xterm')\r\n        let &t_Co=256\r\n    endif\r\nor\r\n    if ($TERM == 'xterm')\r\n        let &t_Co=88\r\n    endif\r\nor\r\n    if ($TERM == 'xterm')\r\n        let &t_Co=16\r\n    endif\r\nor\r\n    if ($TERM == 'xterm')\r\n        let &t_Co=8\r\n    endif\r\n\r\nOf course setting the number of colors to 88 for an 8 color xterm will not work.\r\n\r\nFor Vim urxvt256c (on Linux) the Forms demos work.\r\nVim knows that  &t_Co == 256.\r\n\r\nForms works with 88 color verion of rxvt that supports Unicode, urxvt.\r\nVim knows that  &t_Co == 88.\r\n\r\nForms works with non-Unicode, 8 color rxvt.\r\nVim knows that  &t_Co == 8.\r\n\r\nForms works kconsole (though kconsole's UTF-8 9608 2588 FULL BLOCK does not\r\nrender correctly).\r\nAdd to .vimrc file:\r\n      let &t_Co=256\r\n      let g:FORMS_COLOR_TERM_KONSOLE = 1\r\n\r\nForms works eterm (well, I hope it works, no access to ETerm so could not test).\r\nAdd to .vimrc file:\r\n      let &t_Co=256\r\n      let g:FORMS_COLOR_TERM_ETERM = 1\r\n\r\nFor GVim (on Linux) the Forms demos work.\r\n\r\nIt has not been tested on Mac or Window GVim.\r\n\r\nSee the doc\/forms.txt for more information.\r\n\r\nThe Forms library depends upon the Self library:\r\nhttp:\/\/www.vim.org\/scripts\/script.php?script_id=3072\r\n","5":"Download forms.zip and unzip in $HOME\/.vim.After unpacking the {Forms} directory\r\nlayout should look like:\r\n    $HOME\/.vim\/\r\n      autoload\/\r\n        forms.vim\r\n        forms\/\r\n          menu.vim\r\n          dialog\/...\r\n          examples\/...\r\n      doc\/forms.vim\r\n      plugin\/forms.vim\r\n      tutorial\/forms\/...\r\n\r\nIntalling with vim-addon-manager (VAM)\r\n\r\nFor more information about vim-addon-manager, see\r\n[vim-addon-manager](https:\/\/github.com\/MarcWeber\/vim-addon-manager) and\r\n[Vim-addon-manager getting\r\nstarted](https:\/\/github.com\/MarcWeber\/vim-addon-manager\/blob\/master\/doc\/vim-addon-manager-getting-started.txt)\r\n\r\nIn your .vimrc, add self as shown below:\r\n\r\n    fun SetupVAM()\r\n      ...\r\n      let g:vim_addon_manager = {}\r\n      let g:vim_addon_manager.plugin_sources = {}\r\n      ....\r\n      let g:vim_addon_manager.plugin_sources['self'] = {'type': 'git', 'url':\r\n'git:\/\/github.com\/megaannum\/self'}\r\n      let g:vim_addon_manager.plugin_sources['forms'] = {'type': 'git', 'url':\r\n'git:\/\/github.com\/megaannum\/forms'}\r\n\r\n\r\n      let plugins = [\r\n        \\ 'self',\r\n        \\ 'forms'\r\n        \\ ]\r\n\r\n      call vam#ActivateAddons(plugins,{'auto_install' : 0})\r\n      ...\r\n    endf\r\n    call SetupVAM()\r\n\r\nNow start Vim. You will be asked by vim-addon-manager\r\nif you would like to download and install the self plugin (no dependencies).\r\n\r\nInstalling with pathogen\r\n\r\nI do not use pathogen. An example usage would be welcome.\r\n\r\nConfiguring Xterm and .vimrc for Forms\r\n\r\nFor console-base Vim running in an Xterm, the font used by Vim is the font\r\nused by the Xterm. Running on my Linux systems I found the following\r\nworks to launch an Xterm appropriately configured: >\r\n    \/usr\/bin\/xterm -g 80x30 -bg lightgrey -sl 1000 +si -fn \\\r\n       '-misc-fixed-medium-r-normal-*-20-*-*-*-*-*-iso10646-*'\r\nIf with say, the font 10x20, then you may not be able to render all of\r\nthe unicode characters, but it ought to still work.\r\n\r\nThere is support for 256, 88, 16 and 8 color Xterms though\r\nthe 256 looks best. In your .vimrc file add one of:\r\n    if ($TERM == 'xterm')\r\n        let &t_Co=256\r\n    endif\r\nor\r\n    if ($TERM == 'xterm')\r\n        let &t_Co=88\r\n    endif\r\nor\r\n    if ($TERM == 'xterm')\r\n        let &t_Co=16\r\n    endif\r\nor\r\n    if ($TERM == 'xterm')\r\n        let &t_Co=8\r\n    endif\r\n\r\nOf course setting the number of colors to 88 for an 8 color xterm will not work.\r\n\r\nFor Vim urxvt256c (on Linux) the Forms demos work.\r\nVim knows that  &t_Co == 256.\r\n\r\nForms works with 88 color verion of rxvt that supports Unicode, urxvt.\r\nVim knows that  &t_Co == 88.\r\n\r\nForms works with non-Unicode, 8 color rxvt.\r\nVim knows that  &t_Co == 8.\r\n\r\nForms works kconsole (though kconsole's UTF-8 9608 2588 FULL BLOCK does not\r\nrender correctly).\r\nAdd to .vimrc file:\r\n      let &t_Co=256\r\n      let g:FORMS_COLOR_TERM_KONSOLE = 1\r\n\r\nForms works eterm (well, I hope it works, no access to ETerm so could not test).\r\nAdd to .vimrc file:\r\n      let &t_Co=256\r\n      let g:FORMS_COLOR_TERM_ETERM = 1\r\n\r\nFor GVim (on Linux) the Forms demos work.\r\n\r\nIt has not been tested on Mac or Window GVim.\r\n\r\nSee the doc\/forms.txt for more information.\r\n\r\nThe Forms library depends upon the Self library:\r\nhttp:\/\/www.vim.org\/scripts\/script.php?script_id=3072\r\n","first_name":"richard","6":"richard","last_name":"emberson","7":"emberson","releases":[{"0":"4150","vim_version":"7.0","1":"7.0","script_version":"1.21.2","2":"1.21.2","version_comment":"Previous version did not have the plugin\/forms.vim file (dumb error in my zipper script).","3":"Previous version did not have the plugin\/forms.vim file (dumb error in my zipper script).","package":"forms.zip","4":"forms.zip","src_id":"19320","5":"19320","creation_date":"1357488590","6":"1357488590"},{"0":"4150","vim_version":"7.0","1":"7.0","script_version":"1.21.1","2":"1.21.1","version_comment":"Commented out log statements in Forest\/Node demos.\r\nFixed finding focus for a Deck.\r\nForm demo now open in tab.\r\nFixed dotvimviewer demo to display '.vim' dir.\r\nForms Label checks that 'text' is String or Number.\r\nAdd 'hide' method to SelectList to clear selection item highlight.\r\nFixed 'Form too big' width message.\r\nRemoved Deck __textblock and simply space-out deck prior to each draw.\r\nAdded NodeViewer (node viewer).\r\nAdded ForestViewer\/NodeViewer demo.\r\nAdded ForestViewer (muilti-hierarchical node viewer).\r\nReplaced IS_TRUE\/IS_FALSE with 1\/0.\r\nForm Command event not executing properly.\r\nMade all character varibles globals rather than per-buffer.\r\n","3":"Commented out log statements in Forest\/Node demos.\r\nFixed finding focus for a Deck.\r\nForm demo now open in tab.\r\nFixed dotvimviewer demo to display '.vim' dir.\r\nForms Label checks that 'text' is String or Number.\r\nAdd 'hide' method to SelectList to clear selection item highlight.\r\nFixed 'Form too big' width message.\r\nRemoved Deck __textblock and simply space-out deck prior to each draw.\r\nAdded NodeViewer (node viewer).\r\nAdded ForestViewer\/NodeViewer demo.\r\nAdded ForestViewer (muilti-hierarchical node viewer).\r\nReplaced IS_TRUE\/IS_FALSE with 1\/0.\r\nForm Command event not executing properly.\r\nMade all character varibles globals rather than per-buffer.\r\n","package":"forms.zip","4":"forms.zip","src_id":"19065","5":"19065","creation_date":"1354223853","6":"1354223853"},{"0":"4150","vim_version":"7.3","1":"7.3","script_version":"1.15","2":"1.15","version_comment":"Checkin error: fix tabs and read-only files issues.","3":"Checkin error: fix tabs and read-only files issues.","package":"forms.zip","4":"forms.zip","src_id":"18739","5":"18739","creation_date":"1349209521","6":"1349209521"},{"0":"4150","vim_version":"7.0","1":"7.0","script_version":"1.13","2":"1.13","version_comment":"Added a directory brower dialog.\r\nFixed file browser dialog so that it returned the correct result.\r\nFixed Forms event handling so that nested Form could return result to parent Form.\r\nFixed writing a String consisting of a single multi-byte char.\r\nAdded guard to make sure popdown list's select list has select list prior to accessing it. \r\nChanged highlight group names from *Hi to *FORMS_HL\r\nAdded method to PopupList to support setting its postion (and the underlying selectlist's position.\r\nAdded arrow drawing ASCII and UTF-8 characters\r\nThe glyph highlighting methods now have guards to make sure that the highlight actually exists. \r\nExtended poldownlist example\r\nAdded <Leader>cc mapping for invoking ColorChooser to plugin\r\nChanged function names in xterm88 to include \"88\" in names\r\nAdded map from color name to rgb values.\r\nIf log file in non-writeable directory, write to $HOME directory\r\nAdd logforce method which logs by-passing boolean guard\r\nAdded autoload action guard let g:forms_reload_highlights_on_colorscheme_event\r\nAdd function! g:ShouldLoadeHighlights() which loads\r\nChecks if highlights should be loaded\r\nAdded foreground (light\/dark) color variables\r\nAdded foreground color to some of the highlights\r\nAdded function allowing pattern to be directly used in defining highlight\r\nSelect list now starts display at it chosen postion, rather than always at 0.\r\nPopdown list now uses Select list (rather than menu) and is some 500 to 1000 faster to build. \r\nBackground Glyph now takes optional bacground highlight\r\nIf its a read-only-file, then Forms converts it to read-file and on Forms exit restores to read-only\r\n","3":"Added a directory brower dialog.\r\nFixed file browser dialog so that it returned the correct result.\r\nFixed Forms event handling so that nested Form could return result to parent Form.\r\nFixed writing a String consisting of a single multi-byte char.\r\nAdded guard to make sure popdown list's select list has select list prior to accessing it. \r\nChanged highlight group names from *Hi to *FORMS_HL\r\nAdded method to PopupList to support setting its postion (and the underlying selectlist's position.\r\nAdded arrow drawing ASCII and UTF-8 characters\r\nThe glyph highlighting methods now have guards to make sure that the highlight actually exists. \r\nExtended poldownlist example\r\nAdded <Leader>cc mapping for invoking ColorChooser to plugin\r\nChanged function names in xterm88 to include \"88\" in names\r\nAdded map from color name to rgb values.\r\nIf log file in non-writeable directory, write to $HOME directory\r\nAdd logforce method which logs by-passing boolean guard\r\nAdded autoload action guard let g:forms_reload_highlights_on_colorscheme_event\r\nAdd function! g:ShouldLoadeHighlights() which loads\r\nChecks if highlights should be loaded\r\nAdded foreground (light\/dark) color variables\r\nAdded foreground color to some of the highlights\r\nAdded function allowing pattern to be directly used in defining highlight\r\nSelect list now starts display at it chosen postion, rather than always at 0.\r\nPopdown list now uses Select list (rather than menu) and is some 500 to 1000 faster to build. \r\nBackground Glyph now takes optional bacground highlight\r\nIf its a read-only-file, then Forms converts it to read-file and on Forms exit restores to read-only\r\n","package":"forms.zip","4":"forms.zip","src_id":"18711","5":"18711","creation_date":"1348870343","6":"1348870343"},{"0":"4150","vim_version":"7.0","1":"7.0","script_version":"1.6","2":"1.6","version_comment":"Added support for 8 and 16 color terminals.\r\nWorks with non-unicode characters sets (there is some degradation).\r\n","3":"Added support for 8 and 16 color terminals.\r\nWorks with non-unicode characters sets (there is some degradation).\r\n","package":"forms.zip","4":"forms.zip","src_id":"18510","5":"18510","creation_date":"1346279173","6":"1346279173"},{"0":"4150","vim_version":"7.0","1":"7.0","script_version":"1.5","2":"1.5","version_comment":"Refactored code, Color utilities and Terminal code in separate files\r\nRefactored code, Highlighting values defined and generated\r\nCorrected XTerm colors\r\nAdded urxvt 88 color suport (Color Util and Forms Highlight)\r\nAdded Konsole, Eterm and urxvt256c\r\nHighlight colors now configurable","3":"Refactored code, Color utilities and Terminal code in separate files\r\nRefactored code, Highlighting values defined and generated\r\nCorrected XTerm colors\r\nAdded urxvt 88 color suport (Color Util and Forms Highlight)\r\nAdded Konsole, Eterm and urxvt256c\r\nHighlight colors now configurable","package":"forms.zip","4":"forms.zip","src_id":"18507","5":"18507","creation_date":"1346176890","6":"1346176890"}]},"4149":{"script_id":"4149","0":"4149","script_name":"tui","1":"tui","script_type":"utility","2":"utility","summary":"Place holder for Vim TUI","3":"Place holder for Vim TUI","description":"Not functional yet.","4":"Not functional yet.","install_details":"Nothing to install","5":"Nothing to install","first_name":"richard","6":"richard","last_name":"emberson","7":"emberson","releases":[{"0":"4149","vim_version":"7.0","1":"7.0","script_version":"0.0","2":"0.0","version_comment":"Initial upload","3":"Initial upload","package":"tui.zip","4":"tui.zip","src_id":"18331","5":"18331","creation_date":"1343421520","6":"1343421520"}]},"4148":{"script_id":"4148","0":"4148","script_name":"Teradata 13.10 syntax","1":"Teradata 13.10 syntax","script_type":"syntax","2":"syntax","summary":"Teradata 13.10 SQL and BTEQ syntax file","3":"Teradata 13.10 SQL and BTEQ syntax file","description":"Syntax file for Teradata 13.10 SQL and BTEQ commands.","4":"Syntax file for Teradata 13.10 SQL and BTEQ commands.","install_details":"","5":"","first_name":"Milan","6":"Milan","last_name":"Opath","7":"Opath","releases":[{"0":"4148","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"teradata_13_10.vim","4":"teradata_13_10.vim","src_id":"18322","5":"18322","creation_date":"1343330792","6":"1343330792"}]},"4147":{"script_id":"4147","0":"4147","script_name":"oldenglish.vim","1":"oldenglish.vim","script_type":"utility","2":"utility","summary":"Vim keymap file for Old English (Anglo-Saxon)","3":"Vim keymap file for Old English (Anglo-Saxon)","description":"This keymap file allows you to easily type Old English in Vim using your regular Latin keyboard, with no cumbersome, finger-twisting combinations or the use of the compose key. It is straightforward and can be modified for your needs.\r\n\r\nThe combinations used for scribal abbreviations were chosen with QWERTY keyboards in mind. Change them if you use other keyboard layout.\r\n\r\nThis keymap file was originally created to ease the task of typing in massive amounts of Old English text for the Wikisource electronic edition of \u00c3\u0086lfric's Lives of Saints (http:\/\/en.wikisource.org\/wiki\/\u00c3\u0086lfric's_Lives_of_Saints).\r\n\r\n\r\n\r\nIn case you want to read more about Old English, here are the first paragraphs of two articles from Wikipedia:\r\n\r\nOld English (\u00c3\u0086nglisc, Anglisc, Englisc) or Anglo-Saxon is an early form of the English language that was spoken and written by the Anglo-Saxons and their descendants in parts of what are now England and southern and eastern Scotland, more specifically in the England Old Period, between at least the mid-5th century and the mid-12th century. What survives through writing represents primarily the literary register of Anglo-Saxon.\r\n(from http:\/\/en.wikipedia.org\/wiki\/Old_English)\r\n\r\nThe Old English Latin alphabet \u00e2\u0080\u0093 although it did not have a standard orthography \u00e2\u0080\u0093 generally consisted of 24 letters, and was in use for writing Old English from the 9th to the 12th centuries. Of these, 20 were directly adopted letters of the Latin alphabet, two were modifications of Latin letters (\u00c3\u0086, \u00c3\u0090), and two were developments from the runic alphabet (Ƿ, \u00c3\u009e). The letters K, Q and Z were not in the spelling of native English words.\r\n(from http:\/\/en.wikipedia.org\/wiki\/Old_English_Latin_alphabet)\r\n","4":"This keymap file allows you to easily type Old English in Vim using your regular Latin keyboard, with no cumbersome, finger-twisting combinations or the use of the compose key. It is straightforward and can be modified for your needs.\r\n\r\nThe combinations used for scribal abbreviations were chosen with QWERTY keyboards in mind. Change them if you use other keyboard layout.\r\n\r\nThis keymap file was originally created to ease the task of typing in massive amounts of Old English text for the Wikisource electronic edition of \u00c3\u0086lfric's Lives of Saints (http:\/\/en.wikisource.org\/wiki\/\u00c3\u0086lfric's_Lives_of_Saints).\r\n\r\n\r\n\r\nIn case you want to read more about Old English, here are the first paragraphs of two articles from Wikipedia:\r\n\r\nOld English (\u00c3\u0086nglisc, Anglisc, Englisc) or Anglo-Saxon is an early form of the English language that was spoken and written by the Anglo-Saxons and their descendants in parts of what are now England and southern and eastern Scotland, more specifically in the England Old Period, between at least the mid-5th century and the mid-12th century. What survives through writing represents primarily the literary register of Anglo-Saxon.\r\n(from http:\/\/en.wikipedia.org\/wiki\/Old_English)\r\n\r\nThe Old English Latin alphabet \u00e2\u0080\u0093 although it did not have a standard orthography \u00e2\u0080\u0093 generally consisted of 24 letters, and was in use for writing Old English from the 9th to the 12th centuries. Of these, 20 were directly adopted letters of the Latin alphabet, two were modifications of Latin letters (\u00c3\u0086, \u00c3\u0090), and two were developments from the runic alphabet (Ƿ, \u00c3\u009e). The letters K, Q and Z were not in the spelling of native English words.\r\n(from http:\/\/en.wikipedia.org\/wiki\/Old_English_Latin_alphabet)\r\n","install_details":"Just put the oldenglish.vim file in ~\/.vim\/keymap\/ or other appropriate path.\r\n\r\nIn order to use it, run \u00e2\u0080\u0098:set keymap=oldenglish\u00e2\u0080\u0099. To return to the default keymap, run \u00e2\u0080\u0098:set keymap=\u00e2\u0080\u0099. You can bind these to keys in the usual way (see \u00e2\u0080\u0098:h map.txt\u00e2\u0080\u0099).","5":"Just put the oldenglish.vim file in ~\/.vim\/keymap\/ or other appropriate path.\r\n\r\nIn order to use it, run \u00e2\u0080\u0098:set keymap=oldenglish\u00e2\u0080\u0099. To return to the default keymap, run \u00e2\u0080\u0098:set keymap=\u00e2\u0080\u0099. You can bind these to keys in the usual way (see \u00e2\u0080\u0098:h map.txt\u00e2\u0080\u0099).","first_name":"J\u00c3\u00bada","6":"J\u00c3\u00bada","last_name":"Ron\u00c3\u00a9n","7":"Ron\u00c3\u00a9n","releases":[{"0":"4147","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"oldenglish.vim","4":"oldenglish.vim","src_id":"18321","5":"18321","creation_date":"1343328271","6":"1343328271"}]},"4146":{"script_id":"4146","0":"4146","script_name":"SearchAlternatives","1":"SearchAlternatives","script_type":"utility","2":"utility","summary":"Add \/ subtract alternatives to \/ from the search pattern.","3":"Add \/ subtract alternatives to \/ from the search pattern.","description":"DESCRIPTION\r\nThis plugin provides mappings and commands to add and subtract alternative\r\nbranches to the current search pattern. Currently searching for \"foo,\" but\r\nalso want to find matches for \"bar\"? You could type \/foo\\|bar<CR> or\r\n\/<C-R>\/\\|bar<CR>, but once you want to limit the search to whole \\<words\\>\r\n(like the star command), and juggle several alternatives, adding and\r\ndropping them as you search, this plugin is quicker than manually editing the\r\nsearch command-line (which you can still do).\r\n\r\nSEE ALSO\r\nRELATED WORKS\r\n- Add to Word Search (vimscript #3955) can add the keyword under the cursor to\r\n  the search pattern and search forward \/ backward like * \/ #.\r\n\r\nUSAGE\r\n<Leader>+               Add the current whole \\<word\\> as an alternative to the\r\n                        search pattern, similar to the star command.\r\n\r\n<Leader>g+              Add the current word as an alternative to the search\r\n                        pattern, similar to the gstar command.\r\n\r\n{Visual}<Leader>+       Add the current selection as an alternative to the\r\n                        search pattern.\r\n                        For a blockwise-visual selection, each line of the\r\n                        block (minus leading and trailing whitespace) is added\r\n                        as a separate alternative search pattern. When the\r\n                        first selected line of the block is surrounded by non-\r\n                        keyword characters, the match is done with \\<...\\>.\r\n                        If the blockwise-visual selection is only comprised\r\n                        of a single line, all WORDs of that line are added as\r\n                        separate alternative whole \\<word\\> search patterns.\r\n\r\n<Leader>-               Remove the current whole \\<word\\> from the alternatives\r\n                        in the search pattern.\r\n\r\n<Leader>g-              Remove the current word from the alternatives in the\r\n                        search pattern.\r\n\r\n{Visual}<Leader>-       Remove the current selection from the alternatives in\r\n                        the search pattern.\r\n                        For a blockwise-visual selection, this has the same\r\n                        special behavior as {Visual}<Leader>+.\r\n\r\n:SearchAdd {expr}       Add {expr} as an alternative to the search pattern.\r\n\r\n:SearchRemove {expr}    Remove {expr} from the alternatives in the search\r\n                        pattern.\r\n:[N]SearchRemove        Remove the [N]'th \/ last alternative from the\r\n                        alternatives in the search pattern.\r\n","4":"DESCRIPTION\r\nThis plugin provides mappings and commands to add and subtract alternative\r\nbranches to the current search pattern. Currently searching for \"foo,\" but\r\nalso want to find matches for \"bar\"? You could type \/foo\\|bar<CR> or\r\n\/<C-R>\/\\|bar<CR>, but once you want to limit the search to whole \\<words\\>\r\n(like the star command), and juggle several alternatives, adding and\r\ndropping them as you search, this plugin is quicker than manually editing the\r\nsearch command-line (which you can still do).\r\n\r\nSEE ALSO\r\nRELATED WORKS\r\n- Add to Word Search (vimscript #3955) can add the keyword under the cursor to\r\n  the search pattern and search forward \/ backward like * \/ #.\r\n\r\nUSAGE\r\n<Leader>+               Add the current whole \\<word\\> as an alternative to the\r\n                        search pattern, similar to the star command.\r\n\r\n<Leader>g+              Add the current word as an alternative to the search\r\n                        pattern, similar to the gstar command.\r\n\r\n{Visual}<Leader>+       Add the current selection as an alternative to the\r\n                        search pattern.\r\n                        For a blockwise-visual selection, each line of the\r\n                        block (minus leading and trailing whitespace) is added\r\n                        as a separate alternative search pattern. When the\r\n                        first selected line of the block is surrounded by non-\r\n                        keyword characters, the match is done with \\<...\\>.\r\n                        If the blockwise-visual selection is only comprised\r\n                        of a single line, all WORDs of that line are added as\r\n                        separate alternative whole \\<word\\> search patterns.\r\n\r\n<Leader>-               Remove the current whole \\<word\\> from the alternatives\r\n                        in the search pattern.\r\n\r\n<Leader>g-              Remove the current word from the alternatives in the\r\n                        search pattern.\r\n\r\n{Visual}<Leader>-       Remove the current selection from the alternatives in\r\n                        the search pattern.\r\n                        For a blockwise-visual selection, this has the same\r\n                        special behavior as {Visual}<Leader>+.\r\n\r\n:SearchAdd {expr}       Add {expr} as an alternative to the search pattern.\r\n\r\n:SearchRemove {expr}    Remove {expr} from the alternatives in the search\r\n                        pattern.\r\n:[N]SearchRemove        Remove the [N]'th \/ last alternative from the\r\n                        alternatives in the search pattern.\r\n","install_details":"INSTALLATION\r\nThe code is hosted in a Git repo at\r\n    https:\/\/github.com\/inkarkat\/vim-SearchAlternatives\r\nYou can use your favorite plugin manager, or \"git clone\" into a directory used\r\nfor Vim packages. Releases are on the \"stable\" branch, the latest unstable\r\ndevelopment snapshot on \"master\".\r\n\r\nThis script is also packaged as a vimball. If you have the \"gunzip\"\r\ndecompressor in your PATH, simply edit the *.vmb.gz package in Vim; otherwise,\r\ndecompress the archive first, e.g. using WinZip. Inside Vim, install by\r\nsourcing the vimball or via the :UseVimball command.\r\n    vim SearchAlternatives*.vmb.gz\r\n    :so %\r\nTo uninstall, use the :RmVimball command.\r\n\r\nDEPENDENCIES\r\n- Requires Vim 7.0 or higher.\r\n- Requires the ingo-library.vim plugin (vimscript #4433), version 1.035 or\r\n  higher.","5":"INSTALLATION\r\nThe code is hosted in a Git repo at\r\n    https:\/\/github.com\/inkarkat\/vim-SearchAlternatives\r\nYou can use your favorite plugin manager, or \"git clone\" into a directory used\r\nfor Vim packages. Releases are on the \"stable\" branch, the latest unstable\r\ndevelopment snapshot on \"master\".\r\n\r\nThis script is also packaged as a vimball. If you have the \"gunzip\"\r\ndecompressor in your PATH, simply edit the *.vmb.gz package in Vim; otherwise,\r\ndecompress the archive first, e.g. using WinZip. Inside Vim, install by\r\nsourcing the vimball or via the :UseVimball command.\r\n    vim SearchAlternatives*.vmb.gz\r\n    :so %\r\nTo uninstall, use the :RmVimball command.\r\n\r\nDEPENDENCIES\r\n- Requires Vim 7.0 or higher.\r\n- Requires the ingo-library.vim plugin (vimscript #4433), version 1.035 or\r\n  higher.","first_name":"Ingo","6":"Ingo","last_name":"Karkat","7":"Karkat","releases":[{"0":"4146","vim_version":"7.0","1":"7.0","script_version":"1.11","2":"1.11","version_comment":"- Abort :SearchRemove command on error.\r\n- ENH: When adding a pattern (e.g. \/foo\/) when a shorter prefix (\/fo\/) already exists, the shorter one will eclipse the longer one (only \"fo\" will be matched in \"foobar\"). A new algorithm determines \/ estimates (in case of multis) the match length, and adds shorter ones after longer ones, to avoid the problem. In case of varying match lengths (e.g. with * and \\+ multis), it cannot completely fix it, but it's always equal or better than the original simple addition at the end.\r\n- ENH: When removing a branch, existing global regexp flags like for case sensitivity (\/\\c, \/\\C) and regexp engine type (\/\\%#=0) caused a mismatch, and the corresponding branch could not be found. Now, we extract those flags and segregate them from the comparisons. On addition via SearchAlternatives#AddPattern(), make global flags unique and put them to the front of the search pattern. *** You need to update to ingo-library (vimscript #4433) version 1.035! ***","3":"- Abort :SearchRemove command on error.\r\n- ENH: When adding a pattern (e.g. \/foo\/) when a shorter prefix (\/fo\/) already exists, the shorter one will eclipse the longer one (only \"fo\" will be matched in \"foobar\"). A new algorithm determines \/ estimates (in case of multis) the match length, and adds shorter ones after longer ones, to avoid the problem. In case of varying match lengths (e.g. with * and \\+ multis), it cannot completely fix it, but it's always equal or better than the original simple addition at the end.\r\n- ENH: When removing a branch, existing global regexp flags like for case sensitivity (\/\\c, \/\\C) and regexp engine type (\/\\%#=0) caused a mismatch, and the corresponding branch could not be found. Now, we extract those flags and segregate them from the comparisons. On addition via SearchAlternatives#AddPattern(), make global flags unique and put them to the front of the search pattern. *** You need to update to ingo-library (vimscript #4433) version 1.035! ***","package":"SearchAlternatives-1.11.vmb.gz","4":"SearchAlternatives-1.11.vmb.gz","src_id":"26950","5":"26950","creation_date":"1580492766","6":"1580492766"},{"0":"4146","vim_version":"7.0","1":"7.0","script_version":"1.10","2":"1.10","version_comment":"- ENH: Blockwise <Leader>+ \/ <Leader>- add \/ remove each partial selected trimmed line as a separate search alternative, or individual words when a single line is blockwise-selected.\r\n- ENH: Implement command completion that offers existing alternatives (to remove or clone-and-modify them).\r\n- Add dependency to ingo-library (vimscript #4433). *** You need to separately install ingo-library (vimscript #4433) version 1.009 (or higher)! ***","3":"- ENH: Blockwise <Leader>+ \/ <Leader>- add \/ remove each partial selected trimmed line as a separate search alternative, or individual words when a single line is blockwise-selected.\r\n- ENH: Implement command completion that offers existing alternatives (to remove or clone-and-modify them).\r\n- Add dependency to ingo-library (vimscript #4433). *** You need to separately install ingo-library (vimscript #4433) version 1.009 (or higher)! ***","package":"SearchAlternatives-1.10.vmb.gz","4":"SearchAlternatives-1.10.vmb.gz","src_id":"20543","5":"20543","creation_date":"1374231442","6":"1374231442"},{"0":"4146","vim_version":"7.0","1":"7.0","script_version":"1.00","2":"1.00","version_comment":"Initial upload","3":"Initial upload","package":"SearchAlternatives.vba.gz","4":"SearchAlternatives.vba.gz","src_id":"18314","5":"18314","creation_date":"1343303541","6":"1343303541"}]},"4145":{"script_id":"4145","0":"4145","script_name":"vim-rooter","1":"vim-rooter","script_type":"utility","2":"utility","summary":"Changes working directory to the project root when you open a file.","3":"Changes working directory to the project root when you open a file.","description":"Please see https:\/\/github.com\/airblade\/vim-rooter\r\n","4":"Please see https:\/\/github.com\/airblade\/vim-rooter\r\n","install_details":"Install into `~\/.vim\/plugin\/rooter.vim` or, if you're using Pathogen, into\r\n`~\/.vim\/bundle\/rooter.vim`.\r\n","5":"Install into `~\/.vim\/plugin\/rooter.vim` or, if you're using Pathogen, into\r\n`~\/.vim\/bundle\/rooter.vim`.\r\n","first_name":"Andrew","6":"Andrew","last_name":"Stewart","7":"Stewart","releases":[{"0":"4145","vim_version":"7.0","1":"7.0","script_version":"393255b","2":"393255b","version_comment":"Allows configuration of \"root\" file\/directory patterns.  Various bug-fixes and performance improvements.","3":"Allows configuration of \"root\" file\/directory patterns.  Various bug-fixes and performance improvements.","package":"vim-rooter.tar.gz","4":"vim-rooter.tar.gz","src_id":"21300","5":"21300","creation_date":"1389345150","6":"1389345150"},{"0":"4145","vim_version":"7.0","1":"7.0","script_version":"c5b3e00","2":"c5b3e00","version_comment":"Initial upload","3":"Initial upload","package":"rooter.tar.gz","4":"rooter.tar.gz","src_id":"18307","5":"18307","creation_date":"1343048136","6":"1343048136"}]},"4144":{"script_id":"4144","0":"4144","script_name":"vim-logaling","1":"vim-logaling","script_type":"utility","2":"utility","summary":"A logaling-command front-end","3":"A logaling-command front-end","description":"This is a front-end of logaling-command.\r\nlogaling-command is a glossary management tool written by Ruby.\r\nSee GitHub project page: https:\/\/github.com\/logaling\/logaling-command\r\n\r\nYou can run logaling-command in Vim.\r\n\r\nFor MS Windows user, please let me know this plugin can be run on Windows or not.\r\n\r\nGitHub repository: https:\/\/github.com\/tacahiroy\/vim-logaling","4":"This is a front-end of logaling-command.\r\nlogaling-command is a glossary management tool written by Ruby.\r\nSee GitHub project page: https:\/\/github.com\/logaling\/logaling-command\r\n\r\nYou can run logaling-command in Vim.\r\n\r\nFor MS Windows user, please let me know this plugin can be run on Windows or not.\r\n\r\nGitHub repository: https:\/\/github.com\/tacahiroy\/vim-logaling","install_details":"Needless to say, you're a user of logaling-command.\r\nIf not, you have to install logaling-command first.\r\n\r\n% gem install logaling-command\r\n\r\nIf you use [Vundle](https:\/\/github.com\/gmarik\/vundle.git) it's very easy, you just run command\r\n:BundleInstall tacahiroy\/vim-logaling\r\nin Vim.  \r\nAnd also put \r\nBundle 'tacahiroy\/vim-logaling'\r\ninto `.vimrc`.\r\n\r\nIf you use [pathogen.vim](https:\/\/github.com\/tpope\/vim-pathogen), you just execute following:\r\n\r\n    cd ~\/.vim\/bundle\r\n    git clone git:\/\/github.com\/tacahiroy\/vim-logaling.git\r\n\r\nIf you don't use either, you must copy 'autoload', 'plugin' and 'doc'\r\n directories to $HOME\/.vim directory.\r\nOn windows, you must copy to $HOME\/vimfiles directory instead of $HOME\/.vim.\r\n","5":"Needless to say, you're a user of logaling-command.\r\nIf not, you have to install logaling-command first.\r\n\r\n% gem install logaling-command\r\n\r\nIf you use [Vundle](https:\/\/github.com\/gmarik\/vundle.git) it's very easy, you just run command\r\n:BundleInstall tacahiroy\/vim-logaling\r\nin Vim.  \r\nAnd also put \r\nBundle 'tacahiroy\/vim-logaling'\r\ninto `.vimrc`.\r\n\r\nIf you use [pathogen.vim](https:\/\/github.com\/tpope\/vim-pathogen), you just execute following:\r\n\r\n    cd ~\/.vim\/bundle\r\n    git clone git:\/\/github.com\/tacahiroy\/vim-logaling.git\r\n\r\nIf you don't use either, you must copy 'autoload', 'plugin' and 'doc'\r\n directories to $HOME\/.vim directory.\r\nOn windows, you must copy to $HOME\/vimfiles directory instead of $HOME\/.vim.\r\n","first_name":"Takahiro","6":"Takahiro","last_name":"Yoshihara","7":"Yoshihara","releases":[{"0":"4144","vim_version":"7.0","1":"7.0","script_version":"0.4.8","2":"0.4.8","version_comment":"Add logaling-command version 0.1.7 support","3":"Add logaling-command version 0.1.7 support","package":"vim-logaling-v0.4.8-017.zip","4":"vim-logaling-v0.4.8-017.zip","src_id":"18349","5":"18349","creation_date":"1343693211","6":"1343693211"},{"0":"4144","vim_version":"7.0","1":"7.0","script_version":"0.4.6","2":"0.4.6","version_comment":"Initial upload","3":"Initial upload","package":"vim-logaling-v0.4.6-015.zip","4":"vim-logaling-v0.4.6-015.zip","src_id":"18304","5":"18304","creation_date":"1342995410","6":"1342995410"}]},"4143":{"script_id":"4143","0":"4143","script_name":"seeks.vim","1":"seeks.vim","script_type":"utility","2":"utility","summary":"Make a seeks search inside vim","3":"Make a seeks search inside vim","description":"Homepage: https:\/\/github.com\/sanpii\/seeks.vim\r\nScreenshot: http:\/\/cloud.github.com\/downloads\/sanpii\/seeks.vim\/seeks-vim.png\r\n\r\n# Requirements\r\n\r\n    * https:\/\/github.com\/mattn\/webapi-vim\r\n\r\n## Usage\r\n\r\n    nnoremap <silent> <C-K> :call seeks#Search('<cword>')<CR>\r\n\r\n### Commands\r\n\r\n    :Seeks [query]\r\n\r\n## Configuration\r\n\r\n    let g:seeks_node = 'http:\/\/seeks.fr'\r\n    let g:seeks_max_results = 5","4":"Homepage: https:\/\/github.com\/sanpii\/seeks.vim\r\nScreenshot: http:\/\/cloud.github.com\/downloads\/sanpii\/seeks.vim\/seeks-vim.png\r\n\r\n# Requirements\r\n\r\n    * https:\/\/github.com\/mattn\/webapi-vim\r\n\r\n## Usage\r\n\r\n    nnoremap <silent> <C-K> :call seeks#Search('<cword>')<CR>\r\n\r\n### Commands\r\n\r\n    :Seeks [query]\r\n\r\n## Configuration\r\n\r\n    let g:seeks_node = 'http:\/\/seeks.fr'\r\n    let g:seeks_max_results = 5","install_details":"I recommend installation with pathogen.vim.\r\n\r\n$ cd ~\/.vim\/bundle\r\n$ git clone https:\/\/github.com\/sanpii\/seeks.vim.git","5":"I recommend installation with pathogen.vim.\r\n\r\n$ cd ~\/.vim\/bundle\r\n$ git clone https:\/\/github.com\/sanpii\/seeks.vim.git","first_name":"","6":"","last_name":"","7":"","releases":[{"0":"4143","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"seeks-vim.tar.gz","4":"seeks-vim.tar.gz","src_id":"18303","5":"18303","creation_date":"1342988898","6":"1342988898"}]},"4142":{"script_id":"4142","0":"4142","script_name":"FileFastSelector","1":"FileFastSelector","script_type":"utility","2":"utility","summary":"Plugin allows to open files with minimal number of keystrokes.","3":"Plugin allows to open files with minimal number of keystrokes.","description":"FileFastSelector plugin tries to provide fast way to open files using minimal number of keystrokes. It's inspired by Command-T plugin but requires python support instead of ruby.\r\n\r\nFiles are selected by typing characters that appear in their paths, and are ordered by length of common substring with search string.\r\n\r\nRoot directory for search is current vim directory. Or if tags file exists somewhere in parent directories its path will be used as root.\r\n\r\nSource code is also available on bitbucket: https:\/\/bitbucket.org\/madevgeny\/fastfileselector.\r\n\r\nNOTE: FileFastSelector requires a version of VIM with Python support enabled.\r\n\r\nUsage:\r\nCommand :FFS toggles visibility of fast file selector buffer.\r\nParameter g:FFS_window_height sets height of search buffer. Default = 15.\r\nParameter g:FFS_ignore_list sets list of dirs\/files to ignore use Unix shell-style wildcards. Default = ['.*', '*.bak', '~*', '*~', '*.obj', '*.pdb', '*.res', '*.dll', '*.idb', '*.exe', '*.lib', '*.so', '*.a', '*.pyc', 'CMakeFiles'].\r\nParameter g:FFS_ignore_case, if set letters case will be ignored during search. On windows default = 1, on unix default = 0.\r\nParameter g:FFS_history_size sets the maximum number of stored search queries in history. Default = 10.\r\n\r\nTo get queries history press <Ctrl-H> in insert or normal mode in\r\nsearch string. Autocompletion using history also works by\r\n<Ctrl-X><Ctrl-U>.","4":"FileFastSelector plugin tries to provide fast way to open files using minimal number of keystrokes. It's inspired by Command-T plugin but requires python support instead of ruby.\r\n\r\nFiles are selected by typing characters that appear in their paths, and are ordered by length of common substring with search string.\r\n\r\nRoot directory for search is current vim directory. Or if tags file exists somewhere in parent directories its path will be used as root.\r\n\r\nSource code is also available on bitbucket: https:\/\/bitbucket.org\/madevgeny\/fastfileselector.\r\n\r\nNOTE: FileFastSelector requires a version of VIM with Python support enabled.\r\n\r\nUsage:\r\nCommand :FFS toggles visibility of fast file selector buffer.\r\nParameter g:FFS_window_height sets height of search buffer. Default = 15.\r\nParameter g:FFS_ignore_list sets list of dirs\/files to ignore use Unix shell-style wildcards. Default = ['.*', '*.bak', '~*', '*~', '*.obj', '*.pdb', '*.res', '*.dll', '*.idb', '*.exe', '*.lib', '*.so', '*.a', '*.pyc', 'CMakeFiles'].\r\nParameter g:FFS_ignore_case, if set letters case will be ignored during search. On windows default = 1, on unix default = 0.\r\nParameter g:FFS_history_size sets the maximum number of stored search queries in history. Default = 10.\r\n\r\nTo get queries history press <Ctrl-H> in insert or normal mode in\r\nsearch string. Autocompletion using history also works by\r\n<Ctrl-X><Ctrl-U>.","install_details":"NOTE: FileFastSelector requires a version of VIM with Python support enabled.\r\n\r\nJust drop this file in your plugin directory.\r\nIf you use Vundle (https:\/\/github.com\/gmarik\/vundle\/), you could add \r\n\r\nBundle('https:\/\/bitbucket.org\/madevgeny\/fastfileselector.git')\r\n\r\nto your Vundle config to install FileFastSelector.\r\n","5":"NOTE: FileFastSelector requires a version of VIM with Python support enabled.\r\n\r\nJust drop this file in your plugin directory.\r\nIf you use Vundle (https:\/\/github.com\/gmarik\/vundle\/), you could add \r\n\r\nBundle('https:\/\/bitbucket.org\/madevgeny\/fastfileselector.git')\r\n\r\nto your Vundle config to install FileFastSelector.\r\n","first_name":"Evgeny","6":"Evgeny","last_name":"Podjachev","7":"Podjachev","releases":[{"0":"4142","vim_version":"7.0","1":"7.0","script_version":"0.3.3","2":"0.3.3","version_comment":"Fixed work on some vim builds.\r\nSupport of vim builds with enabled python3 support.","3":"Fixed work on some vim builds.\r\nSupport of vim builds with enabled python3 support.","package":"fastfileselector.zip","4":"fastfileselector.zip","src_id":"21209","5":"21209","creation_date":"1387364547","6":"1387364547"},{"0":"4142","vim_version":"7.3","1":"7.3","script_version":"0.3.1","2":"0.3.1","version_comment":"Removed message \"press any key to continue\" in some cases. Thanks to Dmitry Frank.\r\nFixed error on closing FFS window in some cases. Thanks to Dmitry Frank.","3":"Removed message \"press any key to continue\" in some cases. Thanks to Dmitry Frank.\r\nFixed error on closing FFS window in some cases. Thanks to Dmitry Frank.","package":"fastfileselector.vim","4":"fastfileselector.vim","src_id":"20629","5":"20629","creation_date":"1376220510","6":"1376220510"},{"0":"4142","vim_version":"7.0","1":"7.0","script_version":"0.3.0","2":"0.3.0","version_comment":"Fixed issue with TabBar plugin.\r\nAdded parameter g:FFS_be_silent_on_python_lack to suppress error message if vim doesn't have python support.","3":"Fixed issue with TabBar plugin.\r\nAdded parameter g:FFS_be_silent_on_python_lack to suppress error message if vim doesn't have python support.","package":"fastfileselector.vim","4":"fastfileselector.vim","src_id":"18967","5":"18967","creation_date":"1352570622","6":"1352570622"},{"0":"4142","vim_version":"7.0","1":"7.0","script_version":"0.2.3","2":"0.2.3","version_comment":"Fixed opening files with spaces in path.\r\nFixed case sensitive search.\r\nRemoved fastfileselector buffer from buffers list.","3":"Fixed opening files with spaces in path.\r\nFixed case sensitive search.\r\nRemoved fastfileselector buffer from buffers list.","package":"fastfileselector.vim","4":"fastfileselector.vim","src_id":"18946","5":"18946","creation_date":"1352056959","6":"1352056959"},{"0":"4142","vim_version":"7.0","1":"7.0","script_version":"0.2.2","2":"0.2.2","version_comment":"Fixed autocompletion by <Ctrl-X><Ctrl-U>.\r\nFixed immediate opening of first file after closing history menu.\r\nRemoved '\\' and '\/' from color highlighting as they\tmay produce errors.","3":"Fixed autocompletion by <Ctrl-X><Ctrl-U>.\r\nFixed immediate opening of first file after closing history menu.\r\nRemoved '\\' and '\/' from color highlighting as they\tmay produce errors.","package":"fastfileselector.vim","4":"fastfileselector.vim","src_id":"18388","5":"18388","creation_date":"1344701733","6":"1344701733"},{"0":"4142","vim_version":"7.0","1":"7.0","script_version":"0.2.1","2":"0.2.1","version_comment":"Bug fixes and optimization of search.","3":"Bug fixes and optimization of search.","package":"fastfileselector.vim","4":"fastfileselector.vim","src_id":"18310","5":"18310","creation_date":"1343157738","6":"1343157738"},{"0":"4142","vim_version":"7.0","1":"7.0","script_version":"0.2.0","2":"0.2.0","version_comment":"Added support of GetLatestVimScripts.","3":"Added support of GetLatestVimScripts.","package":"fastfileselector.vim","4":"fastfileselector.vim","src_id":"18300","5":"18300","creation_date":"1342905069","6":"1342905069"},{"0":"4142","vim_version":"7.0","1":"7.0","script_version":"0.1.0","2":"0.1.0","version_comment":"Initial upload","3":"Initial upload","package":"fastfileselector.vim","4":"fastfileselector.vim","src_id":"18299","5":"18299","creation_date":"1342904854","6":"1342904854"}]},"4141":{"script_id":"4141","0":"4141","script_name":"Freebasic vim syntax file","1":"Freebasic vim syntax file","script_type":"syntax","2":"syntax","summary":"Freebasic syntax file.  Can be used since v5.7","3":"Freebasic syntax file.  Can be used since v5.7","description":"This is the freebasic syntax file I have provided since v5.7.  It handles all (as far as I know) of the freebasic commands.  If you find that there are some it does not cover - please do let me know at markem-at-sim1.us.","4":"This is the freebasic syntax file I have provided since v5.7.  It handles all (as far as I know) of the freebasic commands.  If you find that there are some it does not cover - please do let me know at markem-at-sim1.us.","install_details":"You may have to modify the filetype.vim file.  If so, you should insert the following lines:\r\n\r\n\\\" FreeBasic file (similar to QBasic)\r\nau BufNewFile,BufRead *.fb,*.bi\t\t\tsetf freebasic\r\n\r\n","5":"You may have to modify the filetype.vim file.  If so, you should insert the following lines:\r\n\r\n\\\" FreeBasic file (similar to QBasic)\r\nau BufNewFile,BufRead *.fb,*.bi\t\t\tsetf freebasic\r\n\r\n","first_name":"Mark","6":"Mark","last_name":"Manning","7":"Manning","releases":[{"0":"4141","vim_version":"7.0","1":"7.0","script_version":"7.0b","2":"7.0b","version_comment":"Ok. Found the &B (binary) and &O (octal) were not there and then I found a problem. I had \"\\\\.\" when it should have been \"\\\\\\\\.\". Fix this. Makes the code look a lot nicer. :-)","3":"Ok. Found the &B (binary) and &O (octal) were not there and then I found a problem. I had \"\\\\.\" when it should have been \"\\\\\\\\.\". Fix this. Makes the code look a lot nicer. :-)","package":"freebasic.vim","4":"freebasic.vim","src_id":"26739","5":"26739","creation_date":"1568097333","6":"1568097333"},{"0":"4141","vim_version":"7.0","1":"7.0","script_version":"v7.0","2":"v7.0","version_comment":"Mark,\r\n\r\nI understand you made the freebasic.vim file that ships with VIM (7.4\r\nhere), and also have the file on github.  I've made a number of changes\r\nto the file to fix a lot of things that just weren't working such as\r\npreprocessor directives (#ifdef, #define, etc).  Fixed up comment\r\nhandling a bit, and added multi-line comments (\/' '\/).  Changed a few\r\nother classifications too to make the code highlight more like how code\r\nis highlighted in other languages such as C, Python, etc.  User-defined\r\nidentifiers are not colored at all, which makes code a lot more\r\nreadable.  Numbers also were not being highlighted at all before; not\r\nsure why but I fixed that.  There are still some broken things I\r\nencounter once in a while, but overall the highlighting is much\r\nimproved. If you want to take a look and merge this into the official\r\nVIM distribution, that'd be great for other users.\r\n\r\nI borrowed some code from other syntax files that ship with VIM, such as\r\nthe HiLink macro, though I am not sure that was necessary.\r\n\r\nMichael\r\ntorriem@gmail.com","3":"Mark,\r\n\r\nI understand you made the freebasic.vim file that ships with VIM (7.4\r\nhere), and also have the file on github.  I've made a number of changes\r\nto the file to fix a lot of things that just weren't working such as\r\npreprocessor directives (#ifdef, #define, etc).  Fixed up comment\r\nhandling a bit, and added multi-line comments (\/' '\/).  Changed a few\r\nother classifications too to make the code highlight more like how code\r\nis highlighted in other languages such as C, Python, etc.  User-defined\r\nidentifiers are not colored at all, which makes code a lot more\r\nreadable.  Numbers also were not being highlighted at all before; not\r\nsure why but I fixed that.  There are still some broken things I\r\nencounter once in a while, but overall the highlighting is much\r\nimproved. If you want to take a look and merge this into the official\r\nVIM distribution, that'd be great for other users.\r\n\r\nI borrowed some code from other syntax files that ship with VIM, such as\r\nthe HiLink macro, though I am not sure that was necessary.\r\n\r\nMichael\r\ntorriem@gmail.com","package":"freebasic.vim","4":"freebasic.vim","src_id":"22940","5":"22940","creation_date":"1424698629","6":"1424698629"},{"0":"4141","vim_version":"7.0","1":"7.0","script_version":"v5.7","2":"v5.7","version_comment":"Initial upload","3":"Initial upload","package":"freebasic.vim","4":"freebasic.vim","src_id":"18297","5":"18297","creation_date":"1342839540","6":"1342839540"}]},"4140":{"script_id":"4140","0":"4140","script_name":"LineJuggler","1":"LineJuggler","script_type":"utility","2":"utility","summary":"Duplicate and move around lines.","3":"Duplicate and move around lines.","description":"DESCRIPTION\r\nThis plugin offers mappings to quickly duplicate and move lines to above \/\r\nbelow the current line. A [count] either specifies the number of lines, or the\r\nrelative visible target line, therefore it's especially easy to clone lines\r\nwhen 'relativenumber' is set.\r\nThe mappings can save you several keystrokes over an explicit |dd|\/\r\n|yy|[{motion}, ...]|p| sequence in cases where the other lines are nearby and\r\nvisible in the current window.\r\n\r\nOftentimes, duplication in source code is a code smell. Please use this plugin\r\nresponsibly ;-)\r\n\r\nSEE ALSO\r\n- The swap functionality of the plugin's [E \/ ]E mappings are also\r\n  available as an Ex :Swap command, provided by the companion\r\n  LineJugglerCommands.vim plugin (vimscript #4465).\r\n- http:\/\/vim.wikia.com\/wiki\/Quickly_adding_and_deleting_empty_lines has\r\n  a simple implementation of the [<Space> mapping; it also offers mappings\r\n  that delete blank empty lines above \/ below the current line \/ selection\r\n  without changing the current position; these can complement the mappings\r\n  provided by this plugin.\r\n\r\nRELATED WORKS\r\n- Idea, design and implementation of the [<Space> and [e mappings are based on\r\n  Tim Pope's unimpaired.vim plugin (vimscript #1590). In addition, unimpaired\r\n  provides other, unrelated functionality (all via [... \/ ]... mappings), but\r\n  doesn't offer customization of the mappings.\r\n- textmanip.vim (vimscript #3491) provides mappings to move and duplicate\r\n  (selected \/ current) line(s).\r\n- upAndDown (vimscript #2586) provides mappings to move line(s) \/ selection up\r\n  or down.\r\n- move (vimscript #4687) also provides mappings to move lines \/ selection\r\n  around.\r\n- vim-schlepp (https:\/\/github.com\/zirrostig\/vim-schlepp), too\r\n\r\nUSAGE\r\n[<Space>                Add [count] blank lines above the current line \/ above\r\n                        the start of the selection.\r\n                        In a single-line characterwise-visual selection:\r\n                        Add [count] spaces before the start of the selection.\r\n\r\n]<Space>                Add [count] blank lines below the current line \/ below\r\n                        the end of the selection.\r\n                        In a single-line characterwise-visual selection:\r\n                        Add [count] spaces after the end of the selection.\r\n\r\n[e                      Move the current line \/ selection [count] lines above.\r\n\r\n]e                      Move the current line \/ selection [count] lines below.\r\n                        In a single-line characterwise-visual selection:\r\n                        Move the selected text to the same start column\r\n                        [count] lines above \/ below (regardless of whether the\r\n                        target line is that long already; missing columns are\r\n                        filled up with spaces).\r\n\r\n[E                      Exchange the current line with the line \/ closed fold\r\n                        [count] lines above.\r\n                        Exchange the current closed fold with the same amount\r\n                        of visible lines as are in the fold, [count] lines\r\n                        above.\r\n{Visual}[E              Exchange the selection with the same amount of visible\r\n                        lines located [count] lines above.\r\n                        In a single-line characterwise-visual selection:\r\n                        Exchange the selected text with the same-sized\r\n                        area [count] lines above.\r\n]E                      Exchange the current line with the line \/ closed fold\r\n                        [count] lines below.\r\n                        Exchange the current closed fold with the same amount\r\n                        of visible lines as are in the fold, [count] lines\r\n                        below.\r\n{Visual}]E              Exchange the selection with the same amount of visible\r\n                        lines located [count] lines below.\r\n                        In a single-line characterwise-visual selection:\r\n                        Exchange the selected text with the same-sized\r\n                        area [count] lines below.\r\n\r\n[d                      Duplicate the current line \/ selection directly\r\n                        above \/ across [count] lines above the current line \/\r\n                        above the start of the selection.\r\n                        In a single-line characterwise-visual selection:\r\n                        Duplicate before the selection (to [count] characters\r\n                        before the start of the selection).\r\n]d                      Duplicate the current line \/ selection directly\r\n                        below \/ across [count] lines below the current line \/\r\n                        below the end of the selection.\r\n                        In a single-line characterwise-visual selection:\r\n                        Duplicate after the selection (to [count] characters\r\n                        after the end of the selection).\r\n[N][d{M}, [N]]d{M}      Duplicate {M} lines across [N] lines. A combination\r\n                        of [d and [D.\r\n\r\n[D                      Duplicate the current  \/ [count] lines to above the\r\n                        current line.\r\n{Visual}[D              Duplicate the selection [count] times above the\r\n                        selection.\r\n                        In a single-line characterwise-visual selection:\r\n                        Duplicate before the selection [count] times.\r\n]D                      Duplicate the current  \/ [count] lines to below that\r\n                        range.\r\n{Visual}]D              Duplicate the selection [count] times below the\r\n                        selection.\r\n                        In a single-line characterwise-visual selection:\r\n                        Duplicate after the selection [count] times.\r\n[N][D{M}, [N]]D{M}      Duplicate [N] lines across {M} lines. A combination\r\n                        of [d and [D. Equivalent to [N][d{M}, but with\r\n                        reverse order of the numbers.\r\n\r\n[f                      Fetch the line [count] visible lines below the current\r\n                        line and duplicate it below the current line.\r\n]f                      Fetch the line [count] visible lines above the current\r\n                        line and duplicate it below the current line.\r\n{Visual}[f              Fetch the same number of visible lines starting from\r\n                        the line [count] lines below the current line and\r\n                        duplicate them above the start of the selection.\r\n{Visual}]f              Fetch the same number of visible lines starting from\r\n                        the line [count] lines above the current line and\r\n                        duplicate them below the end of the selection.\r\n\r\n[r                      Fetch the line [count] visible lines below the current\r\n                        line and replace the current line with it.\r\n]r                      Fetch the line [count] visible lines above the current\r\n                        line and replace the current line with it.\r\n{Visual}[r              Replace the selection with the same number of visible\r\n                        lines fetched starting from the line [count] lines\r\n                        below the current line.\r\n{Visual}]r              Replace the selection with the same number of visible\r\n                        lines fetched starting from the line [count] lines\r\n                        above the current line.\r\n                        In a single-line characterwise-visual selection:\r\n                        Replace the selected text with the same-sized\r\n                        area [count] lines below \/ above.\r\n\r\n                        When the cursor is on a closed fold or the selection\r\n                        contains a closed fold, the entire set of folded lines\r\n                        is used. All mappings treat closed folds as a fixed\r\n                        entity, so they will never move \/ duplicate into a\r\n                        closed fold, always over it.\r\n                        A [count] specifies visible lines, closed folds are\r\n                        counted as one line, so you can use the\r\n                        'relativenumber' column to easily reach a target.\r\n                        (Except for v_[d and v_]d when at the opposite\r\n                        side of the selection.)","4":"DESCRIPTION\r\nThis plugin offers mappings to quickly duplicate and move lines to above \/\r\nbelow the current line. A [count] either specifies the number of lines, or the\r\nrelative visible target line, therefore it's especially easy to clone lines\r\nwhen 'relativenumber' is set.\r\nThe mappings can save you several keystrokes over an explicit |dd|\/\r\n|yy|[{motion}, ...]|p| sequence in cases where the other lines are nearby and\r\nvisible in the current window.\r\n\r\nOftentimes, duplication in source code is a code smell. Please use this plugin\r\nresponsibly ;-)\r\n\r\nSEE ALSO\r\n- The swap functionality of the plugin's [E \/ ]E mappings are also\r\n  available as an Ex :Swap command, provided by the companion\r\n  LineJugglerCommands.vim plugin (vimscript #4465).\r\n- http:\/\/vim.wikia.com\/wiki\/Quickly_adding_and_deleting_empty_lines has\r\n  a simple implementation of the [<Space> mapping; it also offers mappings\r\n  that delete blank empty lines above \/ below the current line \/ selection\r\n  without changing the current position; these can complement the mappings\r\n  provided by this plugin.\r\n\r\nRELATED WORKS\r\n- Idea, design and implementation of the [<Space> and [e mappings are based on\r\n  Tim Pope's unimpaired.vim plugin (vimscript #1590). In addition, unimpaired\r\n  provides other, unrelated functionality (all via [... \/ ]... mappings), but\r\n  doesn't offer customization of the mappings.\r\n- textmanip.vim (vimscript #3491) provides mappings to move and duplicate\r\n  (selected \/ current) line(s).\r\n- upAndDown (vimscript #2586) provides mappings to move line(s) \/ selection up\r\n  or down.\r\n- move (vimscript #4687) also provides mappings to move lines \/ selection\r\n  around.\r\n- vim-schlepp (https:\/\/github.com\/zirrostig\/vim-schlepp), too\r\n\r\nUSAGE\r\n[<Space>                Add [count] blank lines above the current line \/ above\r\n                        the start of the selection.\r\n                        In a single-line characterwise-visual selection:\r\n                        Add [count] spaces before the start of the selection.\r\n\r\n]<Space>                Add [count] blank lines below the current line \/ below\r\n                        the end of the selection.\r\n                        In a single-line characterwise-visual selection:\r\n                        Add [count] spaces after the end of the selection.\r\n\r\n[e                      Move the current line \/ selection [count] lines above.\r\n\r\n]e                      Move the current line \/ selection [count] lines below.\r\n                        In a single-line characterwise-visual selection:\r\n                        Move the selected text to the same start column\r\n                        [count] lines above \/ below (regardless of whether the\r\n                        target line is that long already; missing columns are\r\n                        filled up with spaces).\r\n\r\n[E                      Exchange the current line with the line \/ closed fold\r\n                        [count] lines above.\r\n                        Exchange the current closed fold with the same amount\r\n                        of visible lines as are in the fold, [count] lines\r\n                        above.\r\n{Visual}[E              Exchange the selection with the same amount of visible\r\n                        lines located [count] lines above.\r\n                        In a single-line characterwise-visual selection:\r\n                        Exchange the selected text with the same-sized\r\n                        area [count] lines above.\r\n]E                      Exchange the current line with the line \/ closed fold\r\n                        [count] lines below.\r\n                        Exchange the current closed fold with the same amount\r\n                        of visible lines as are in the fold, [count] lines\r\n                        below.\r\n{Visual}]E              Exchange the selection with the same amount of visible\r\n                        lines located [count] lines below.\r\n                        In a single-line characterwise-visual selection:\r\n                        Exchange the selected text with the same-sized\r\n                        area [count] lines below.\r\n\r\n[d                      Duplicate the current line \/ selection directly\r\n                        above \/ across [count] lines above the current line \/\r\n                        above the start of the selection.\r\n                        In a single-line characterwise-visual selection:\r\n                        Duplicate before the selection (to [count] characters\r\n                        before the start of the selection).\r\n]d                      Duplicate the current line \/ selection directly\r\n                        below \/ across [count] lines below the current line \/\r\n                        below the end of the selection.\r\n                        In a single-line characterwise-visual selection:\r\n                        Duplicate after the selection (to [count] characters\r\n                        after the end of the selection).\r\n[N][d{M}, [N]]d{M}      Duplicate {M} lines across [N] lines. A combination\r\n                        of [d and [D.\r\n\r\n[D                      Duplicate the current  \/ [count] lines to above the\r\n                        current line.\r\n{Visual}[D              Duplicate the selection [count] times above the\r\n                        selection.\r\n                        In a single-line characterwise-visual selection:\r\n                        Duplicate before the selection [count] times.\r\n]D                      Duplicate the current  \/ [count] lines to below that\r\n                        range.\r\n{Visual}]D              Duplicate the selection [count] times below the\r\n                        selection.\r\n                        In a single-line characterwise-visual selection:\r\n                        Duplicate after the selection [count] times.\r\n[N][D{M}, [N]]D{M}      Duplicate [N] lines across {M} lines. A combination\r\n                        of [d and [D. Equivalent to [N][d{M}, but with\r\n                        reverse order of the numbers.\r\n\r\n[f                      Fetch the line [count] visible lines below the current\r\n                        line and duplicate it below the current line.\r\n]f                      Fetch the line [count] visible lines above the current\r\n                        line and duplicate it below the current line.\r\n{Visual}[f              Fetch the same number of visible lines starting from\r\n                        the line [count] lines below the current line and\r\n                        duplicate them above the start of the selection.\r\n{Visual}]f              Fetch the same number of visible lines starting from\r\n                        the line [count] lines above the current line and\r\n                        duplicate them below the end of the selection.\r\n\r\n[r                      Fetch the line [count] visible lines below the current\r\n                        line and replace the current line with it.\r\n]r                      Fetch the line [count] visible lines above the current\r\n                        line and replace the current line with it.\r\n{Visual}[r              Replace the selection with the same number of visible\r\n                        lines fetched starting from the line [count] lines\r\n                        below the current line.\r\n{Visual}]r              Replace the selection with the same number of visible\r\n                        lines fetched starting from the line [count] lines\r\n                        above the current line.\r\n                        In a single-line characterwise-visual selection:\r\n                        Replace the selected text with the same-sized\r\n                        area [count] lines below \/ above.\r\n\r\n                        When the cursor is on a closed fold or the selection\r\n                        contains a closed fold, the entire set of folded lines\r\n                        is used. All mappings treat closed folds as a fixed\r\n                        entity, so they will never move \/ duplicate into a\r\n                        closed fold, always over it.\r\n                        A [count] specifies visible lines, closed folds are\r\n                        counted as one line, so you can use the\r\n                        'relativenumber' column to easily reach a target.\r\n                        (Except for v_[d and v_]d when at the opposite\r\n                        side of the selection.)","install_details":"INSTALLATION\r\nThe code is hosted in a Git repo at\r\n    https:\/\/github.com\/inkarkat\/vim-LineJuggler\r\nYou can use your favorite plugin manager, or \"git clone\" into a directory used\r\nfor Vim packages. Releases are on the \"stable\" branch, the latest unstable\r\ndevelopment snapshot on \"master\".\r\n\r\nThis script is also packaged as a vimball. If you have the \"gunzip\"\r\ndecompressor in your PATH, simply edit the *.vmb.gz package in Vim; otherwise,\r\ndecompress the archive first, e.g. using WinZip. Inside Vim, install by\r\nsourcing the vimball or via the :UseVimball command.\r\n    vim LineJuggler*.vmb.gz\r\n    :so %\r\nTo uninstall, use the :RmVimball command.\r\n\r\nDEPENDENCIES\r\n- Requires Vim 7.0 or higher.\r\n- Requires the ingo-library.vim plugin (vimscript #4433), version 1.022 or\r\n  higher.\r\n- repeat.vim (vimscript #2136) plugin (optional)\r\n- visualrepeat.vim (vimscript #3848) plugin (optional)\r\n\r\nCONFIGURATION\r\nFor a permanent configuration, put the following commands into your vimrc:\r\n\r\nIf you want to use different mappings, map your keys to the\r\n<Plug>(LineJuggler...) mapping targets _before_ sourcing the script (e.g. in\r\nyour vimrc):\r\n    nmap <C-Up>   <Plug>(LineJugglerBlankUp)\r\n    nmap <C-Down> <Plug>(LineJugglerBlankDown)\r\n    vmap <C-Up>   <Plug>(LineJugglerBlankUp)\r\n    vmap <C-Down> <Plug>(LineJugglerBlankDown)\r\n    ...\r\nThe [d||[D combination mappings are only defined for low values of {M}. For\r\nhow many (and the default mapping keys) are configured via two variables:\r\n    let g:LineJuggler_DupRangeOver= [9, '[%dD', ']%dD']\r\n    let g:LineJuggler_DupOverRange= [9, '[%dd', ']%dd']\r\nThe first number specifies the upper limit of {M}; with 0, no combination\r\nmappings are defined. The second and third argument represent the mapping\r\nkeys, with the {M} number inserted at the %d.","5":"INSTALLATION\r\nThe code is hosted in a Git repo at\r\n    https:\/\/github.com\/inkarkat\/vim-LineJuggler\r\nYou can use your favorite plugin manager, or \"git clone\" into a directory used\r\nfor Vim packages. Releases are on the \"stable\" branch, the latest unstable\r\ndevelopment snapshot on \"master\".\r\n\r\nThis script is also packaged as a vimball. If you have the \"gunzip\"\r\ndecompressor in your PATH, simply edit the *.vmb.gz package in Vim; otherwise,\r\ndecompress the archive first, e.g. using WinZip. Inside Vim, install by\r\nsourcing the vimball or via the :UseVimball command.\r\n    vim LineJuggler*.vmb.gz\r\n    :so %\r\nTo uninstall, use the :RmVimball command.\r\n\r\nDEPENDENCIES\r\n- Requires Vim 7.0 or higher.\r\n- Requires the ingo-library.vim plugin (vimscript #4433), version 1.022 or\r\n  higher.\r\n- repeat.vim (vimscript #2136) plugin (optional)\r\n- visualrepeat.vim (vimscript #3848) plugin (optional)\r\n\r\nCONFIGURATION\r\nFor a permanent configuration, put the following commands into your vimrc:\r\n\r\nIf you want to use different mappings, map your keys to the\r\n<Plug>(LineJuggler...) mapping targets _before_ sourcing the script (e.g. in\r\nyour vimrc):\r\n    nmap <C-Up>   <Plug>(LineJugglerBlankUp)\r\n    nmap <C-Down> <Plug>(LineJugglerBlankDown)\r\n    vmap <C-Up>   <Plug>(LineJugglerBlankUp)\r\n    vmap <C-Down> <Plug>(LineJugglerBlankDown)\r\n    ...\r\nThe [d||[D combination mappings are only defined for low values of {M}. For\r\nhow many (and the default mapping keys) are configured via two variables:\r\n    let g:LineJuggler_DupRangeOver= [9, '[%dD', ']%dD']\r\n    let g:LineJuggler_DupOverRange= [9, '[%dd', ']%dd']\r\nThe first number specifies the upper limit of {M}; with 0, no combination\r\nmappings are defined. The second and third argument represent the mapping\r\nkeys, with the {M} number inserted at the %d.","first_name":"Ingo","6":"Ingo","last_name":"Karkat","7":"Karkat","releases":[{"0":"4140","vim_version":"7.0","1":"7.0","script_version":"2.11","2":"2.11","version_comment":"- ]e \/ [e cause fold update \/ may close all folds (e.g. in HTML) (after Vim 7.4.700). Culprit is the :move command; temporarily disable folding during its execution to avoid that.\r\n- Move LineJuggler#FoldClosed() and LineJuggler#FoldClosedEnd() into ingo-library as ingo#range#NetStart() and ingo#range#NetEnd(). *** You need to update to ingo-library (vimscript #4433) version 1.022! ***","3":"- ]e \/ [e cause fold update \/ may close all folds (e.g. in HTML) (after Vim 7.4.700). Culprit is the :move command; temporarily disable folding during its execution to avoid that.\r\n- Move LineJuggler#FoldClosed() and LineJuggler#FoldClosedEnd() into ingo-library as ingo#range#NetStart() and ingo#range#NetEnd(). *** You need to update to ingo-library (vimscript #4433) version 1.022! ***","package":"LineJuggler-2.11.vmb.gz","4":"LineJuggler-2.11.vmb.gz","src_id":"26261","5":"26261","creation_date":"1541373266","6":"1541373266"},{"0":"4140","vim_version":"7.0","1":"7.0","script_version":"2.10","2":"2.10","version_comment":"- ENH: Add combination mappings of ]d and ]D that can specify both a number of lines and number of skipped lines (one limited to a small range of 1..9) to handle the often-needed use case of duplicating a few lines with a little offset, without having to go through visual mode and ]D.\r\n- Expose (most of) s:RepFetch() as LineJuggler#ReplaceRanges() for use with the companion LineJugglerCommands.vim plugin.","3":"- ENH: Add combination mappings of ]d and ]D that can specify both a number of lines and number of skipped lines (one limited to a small range of 1..9) to handle the often-needed use case of duplicating a few lines with a little offset, without having to go through visual mode and ]D.\r\n- Expose (most of) s:RepFetch() as LineJuggler#ReplaceRanges() for use with the companion LineJugglerCommands.vim plugin.","package":"LineJuggler-2.10.vmb.gz","4":"LineJuggler-2.10.vmb.gz","src_id":"22018","5":"22018","creation_date":"1402487528","6":"1402487528"},{"0":"4140","vim_version":"7.0","1":"7.0","script_version":"2.01","2":"2.01","version_comment":"- Adapt to changed ingo#register#KeepRegisterExecuteOrFunc() interface.\r\n- FIX: Intra-line ]r and ]E do not work in Vim versions before 7.3.590; need to use ingo#compat#setpos().\r\n- XXX: Include workaround for wrong cursor position at the beginning, not the end of an intra-line swap to the end of the line, starting with Vim 7.4.034. *** You need to update to ingo-library (vimscript #4433) version 1.015! ***","3":"- Adapt to changed ingo#register#KeepRegisterExecuteOrFunc() interface.\r\n- FIX: Intra-line ]r and ]E do not work in Vim versions before 7.3.590; need to use ingo#compat#setpos().\r\n- XXX: Include workaround for wrong cursor position at the beginning, not the end of an intra-line swap to the end of the line, starting with Vim 7.4.034. *** You need to update to ingo-library (vimscript #4433) version 1.015! ***","package":"LineJuggler-2.01.vmb.gz","4":"LineJuggler-2.01.vmb.gz","src_id":"21216","5":"21216","creation_date":"1387439983","6":"1387439983"},{"0":"4140","vim_version":"7.0","1":"7.0","script_version":"2.00","2":"2.00","version_comment":"- ENH: Implement special DWIM behavior for duplication of characterwise single-line selection:\r\n  Add spaces before \/ after the selection ([<Space> \/ ]<Space>).\r\n  Duplicate before \/ after the selection in the same line, either with [count]\r\n  as character offset ([d \/ ]d) or repeat count ([D \/ ]D).\r\n  Move only selection above \/ below ([e \/ ]e).\r\n  Exchange only selection above \/ below ([E \/ ]E).\r\n  Replace selection with text from above \/ below (]r \/ [r).\r\n  *** You need to update to ingo-library (vimscript #4433) version 1.014! ***","3":"- ENH: Implement special DWIM behavior for duplication of characterwise single-line selection:\r\n  Add spaces before \/ after the selection ([<Space> \/ ]<Space>).\r\n  Duplicate before \/ after the selection in the same line, either with [count]\r\n  as character offset ([d \/ ]d) or repeat count ([D \/ ]D).\r\n  Move only selection above \/ below ([e \/ ]e).\r\n  Exchange only selection above \/ below ([E \/ ]E).\r\n  Replace selection with text from above \/ below (]r \/ [r).\r\n  *** You need to update to ingo-library (vimscript #4433) version 1.014! ***","package":"LineJuggler-2.00.vmb.gz","4":"LineJuggler-2.00.vmb.gz","src_id":"21042","5":"21042","creation_date":"1384418586","6":"1384418586"},{"0":"4140","vim_version":"7.0","1":"7.0","script_version":"1.23","2":"1.23","version_comment":"- Add message \"N lines swapped with M lines\" on [E \/ ]E.\r\n- Add message \"Replaced N lines\" for [r \/ ]r.\r\n- Add dependency to ingo-library (vimscript #4433). *** You need to separately install ingo-library (vimscript #4433) version 1.004 (or higher)! ***","3":"- Add message \"N lines swapped with M lines\" on [E \/ ]E.\r\n- Add message \"Replaced N lines\" for [r \/ ]r.\r\n- Add dependency to ingo-library (vimscript #4433). *** You need to separately install ingo-library (vimscript #4433) version 1.004 (or higher)! ***","package":"LineJuggler-1.23.vmb.gz","4":"LineJuggler-1.23.vmb.gz","src_id":"20966","5":"20966","creation_date":"1382818795","6":"1382818795"},{"0":"4140","vim_version":"7.0","1":"7.0","script_version":"1.22","2":"1.22","version_comment":"- Expose s:DoSwap() as LineJuggler#SwapRanges() for use with the companion LineJugglerCommands.vim plugin.","3":"- Expose s:DoSwap() as LineJuggler#SwapRanges() for use with the companion LineJugglerCommands.vim plugin.","package":"LineJuggler-1.22.vmb.gz","4":"LineJuggler-1.22.vmb.gz","src_id":"19606","5":"19606","creation_date":"1362774778","6":"1362774778"},{"0":"4140","vim_version":"7.0","1":"7.0","script_version":"1.21","2":"1.21","version_comment":"- Avoid clobbering the expression register.","3":"- Avoid clobbering the expression register.","package":"LineJuggler-1.21.vmb.gz","4":"LineJuggler-1.21.vmb.gz","src_id":"18537","5":"18537","creation_date":"1346664526","6":"1346664526"},{"0":"4140","vim_version":"7.0","1":"7.0","script_version":"1.20","2":"1.20","version_comment":"- CHG: [d \/ ]d duplication without [count] still duplicates to the directly adjacent line, but with [count] now across [count] lines, which aligns with the 'relativenumber' hint.\r\n- FIX: Correct clipping at the end for the ]E mapping.\r\n- FIX: Make sure that v_[E \/ v_]E never swap with a single folded target line; this special behavior is reserved for the single-line normal mode swap.\r\n- CHG: For visual selections in v_[E, v_[f, v_[r, also use the amount of visible lines, not the number of lines contained in the selection. This makes it more consistent with the overall plugin behavior and is hopefully also more useful.\r\n- The workaround in s:PutWrapper() is not necessary after Vim version 7.3.272; add conditional.","3":"- CHG: [d \/ ]d duplication without [count] still duplicates to the directly adjacent line, but with [count] now across [count] lines, which aligns with the 'relativenumber' hint.\r\n- FIX: Correct clipping at the end for the ]E mapping.\r\n- FIX: Make sure that v_[E \/ v_]E never swap with a single folded target line; this special behavior is reserved for the single-line normal mode swap.\r\n- CHG: For visual selections in v_[E, v_[f, v_[r, also use the amount of visible lines, not the number of lines contained in the selection. This makes it more consistent with the overall plugin behavior and is hopefully also more useful.\r\n- The workaround in s:PutWrapper() is not necessary after Vim version 7.3.272; add conditional.","package":"LineJuggler.vba.gz","4":"LineJuggler.vba.gz","src_id":"18325","5":"18325","creation_date":"1343389127","6":"1343389127"},{"0":"4140","vim_version":"7.0","1":"7.0","script_version":"1.10","2":"1.10","version_comment":"CHG: Split [f and {Visual}[f behaviors into two families of mappings:\r\na) [f to fetch below current line and {Visual}[f to fetch selected number of lines above\/below selection\r\nb) [r to fetch and replace current line \/ selection.","3":"CHG: Split [f and {Visual}[f behaviors into two families of mappings:\r\na) [f to fetch below current line and {Visual}[f to fetch selected number of lines above\/below selection\r\nb) [r to fetch and replace current line \/ selection.","package":"LineJuggler.vba.gz","4":"LineJuggler.vba.gz","src_id":"18308","5":"18308","creation_date":"1343052003","6":"1343052003"},{"0":"4140","vim_version":"7.0","1":"7.0","script_version":"1.00","2":"1.00","version_comment":"Initial upload","3":"Initial upload","package":"LineJuggler.vba.gz","4":"LineJuggler.vba.gz","src_id":"18292","5":"18292","creation_date":"1342789264","6":"1342789264"}]},"4139":{"script_id":"4139","0":"4139","script_name":"star.vim","1":"star.vim","script_type":"syntax","2":"syntax","summary":"syntax highlighting for Self-defining Text Archive and Retrieval (STAR) format","3":"syntax highlighting for Self-defining Text Archive and Retrieval (STAR) format","description":"Syntax highlighting for Self-defining Text Archive and Retrieval (STAR) format [1]. macromolecular Crystallographic Information File (mmCIF) [2] files are in STAR format.\r\n\r\n[1] http:\/\/mmcif.rcsb.org\/mmcif-early\/background\/index.html\r\n[2] http:\/\/mmcif.rcsb.org\/","4":"Syntax highlighting for Self-defining Text Archive and Retrieval (STAR) format [1]. macromolecular Crystallographic Information File (mmCIF) [2] files are in STAR format.\r\n\r\n[1] http:\/\/mmcif.rcsb.org\/mmcif-early\/background\/index.html\r\n[2] http:\/\/mmcif.rcsb.org\/","install_details":"Download and save into ~\/.vim\/syntax\/star.vim .\r\n\r\nFor automatic syntax recognition:\r\necho -e \"if getline(1) =~ '^data_[0-9][[:alnum:]]\\{3\\}$'\\n  setfiletype star\\nendif\" >> ~\/.vim\/scripts.vim","5":"Download and save into ~\/.vim\/syntax\/star.vim .\r\n\r\nFor automatic syntax recognition:\r\necho -e \"if getline(1) =~ '^data_[0-9][[:alnum:]]\\{3\\}$'\\n  setfiletype star\\nendif\" >> ~\/.vim\/scripts.vim","first_name":"Laszlo","6":"Laszlo","last_name":"Kajan","7":"Kajan","releases":[{"0":"4139","vim_version":"7.0","1":"7.0","script_version":"1.0.0","2":"1.0.0","version_comment":"Initial upload","3":"Initial upload","package":"star.vim","4":"star.vim","src_id":"18289","5":"18289","creation_date":"1342717341","6":"1342717341"}]},"4138":{"script_id":"4138","0":"4138","script_name":"Toggle NERDTree width","1":"Toggle NERDTree width","script_type":"utility","2":"utility","summary":"Changes width of the NERDTree to see even the longest file names","3":"Changes width of the NERDTree to see even the longest file names","description":"This little script is a plugin for the NERDTree plugin. It adds a new key (w) for the NERDTree which toggles its width between the normal width and the width of the longest file name.\r\nQuite useful if you want to have a clear view on your files and don't want to maximize your NERDTree.","4":"This little script is a plugin for the NERDTree plugin. It adds a new key (w) for the NERDTree which toggles its width between the normal width and the width of the longest file name.\r\nQuite useful if you want to have a clear view on your files and don't want to maximize your NERDTree.","install_details":"You need, of course, the NERDTree plugin.\r\nThen, put this script in your ~\/.vim\/nerdtree_plugin\/","5":"You need, of course, the NERDTree plugin.\r\nThen, put this script in your ~\/.vim\/nerdtree_plugin\/","first_name":"Daniel","6":"Daniel","last_name":"Schemala","7":"Schemala","releases":[{"0":"4138","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"toggle_width.vim","4":"toggle_width.vim","src_id":"18278","5":"18278","creation_date":"1342512925","6":"1342512925"}]},"4137":{"script_id":"4137","0":"4137","script_name":"refactor-rails.vim","1":"refactor-rails.vim","script_type":"utility","2":"utility","summary":"A vim plugin to help refactoring rails projects","3":"A vim plugin to help refactoring rails projects","description":"A plugin that simplifies some of the process used to refactor projects in rails. \r\n\r\nVisit: https:\/\/github.com\/sandeepravi\/refactor-rails.vim for further details","4":"A plugin that simplifies some of the process used to refactor projects in rails. \r\n\r\nVisit: https:\/\/github.com\/sandeepravi\/refactor-rails.vim for further details","install_details":"Initital Uplaod","5":"Initital Uplaod","first_name":"Sandeep","6":"Sandeep","last_name":"Ravichandran","7":"Ravichandran","releases":[{"0":"4137","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"refactor-rails.vim.zip","4":"refactor-rails.vim.zip","src_id":"18277","5":"18277","creation_date":"1342508806","6":"1342508806"}]},"4136":{"script_id":"4136","0":"4136","script_name":"Briofita","1":"Briofita","script_type":"color scheme","2":"color scheme","summary":"dark, colorful, highly customized scheme for gvim and 256-color terminals","3":"dark, colorful, highly customized scheme for gvim and 256-color terminals","description":"Briofita is a colorful dark background Vim colorscheme for both gvim (Vim GUI) and 256-colors terminals. It has MANY custom highlights and supports syntax coloring for several languages, utilities, plugins, tools...\r\n\r\nAlthough heavier than common Vim colorschemes it runs smoothly on current computers.  I have been using it daily since its first version, for work, research and study. \r\n\r\nBriofita colorscheme is fit for common, non-specialized usage but polished, colorful highlights are provided in support of authoring, writing, publishing (Asciidoc, Markdown, ...) and software development (java, javascript, julia, perl, python, ruby, haskell, lua, c\/c++, shellscript, sql, css, HTML\/XHTML, XML, csv, yaml, json, ...) including Vim-related development  (VimL \/ Vimscript, help authoring, customization of plugins highlights).\r\n\r\nDevelopment repository in Github:  https:\/\/github.com\/sonobre\/briofita_vim\r\n","4":"Briofita is a colorful dark background Vim colorscheme for both gvim (Vim GUI) and 256-colors terminals. It has MANY custom highlights and supports syntax coloring for several languages, utilities, plugins, tools...\r\n\r\nAlthough heavier than common Vim colorschemes it runs smoothly on current computers.  I have been using it daily since its first version, for work, research and study. \r\n\r\nBriofita colorscheme is fit for common, non-specialized usage but polished, colorful highlights are provided in support of authoring, writing, publishing (Asciidoc, Markdown, ...) and software development (java, javascript, julia, perl, python, ruby, haskell, lua, c\/c++, shellscript, sql, css, HTML\/XHTML, XML, csv, yaml, json, ...) including Vim-related development  (VimL \/ Vimscript, help authoring, customization of plugins highlights).\r\n\r\nDevelopment repository in Github:  https:\/\/github.com\/sonobre\/briofita_vim\r\n","install_details":"BASIC INSTALLATION: \r\n\r\na. Download the zip file.\r\n\r\nb. Unpack it. In the uncompressed directory you will get \"colors\", \"autoload\" and \"doc\" sub-directories.\r\n\r\nc. If you do NOT use a bundle-based plugin (like Pathogen):\r\n     1 copy the content of the \"colors\" directory into your \".vim\/colors\" directory;\r\n     2 copy the content of the \"doc\" directory into your \".vim\/doc\" directory;\r\n        restart Vim and do :helptags;\r\n        do :help briofita, and read the help file to learn about Briofita;\r\n     3 run command :colorscheme briofita to start the colorscheme;\r\n     NOTE: if you use the Lightline statusline plugin it will automatically \r\n                  scan the autoload directory and detect the briofita theme.\r\n\r\nd. If you use Pathogen or other bundle-based plugin:\r\n     1 create under your \".vim\/bundle\" directory a new directory, and name it \"briofita\";\r\n        and copy the unzipped file tree under the \".vim\/bundle\/briofita\" directory;\r\n     2 restart Vim and do :Helptags (Pathogen command);\r\n        do :help briofita, and read the help file to learn about Briofita;\r\n     3 command :colorscheme briofita;\r\n\r\nTo uninstall, simply delete all the unzipped directory tree for Briofita from above mentioned directories.\r\n\r\nIf you want to install the colorscheme, but not the plugin follow\r\nthe above instructions \"c.1\" and \"c.3\" (or \"d.1\" and \"d.3\") and then just delete the plugin (\"briofita-support.vim\") from\r\nthe plugin sub-directory  and the help file (\"briofita.txt\") from the doc sub-directory.\r\n\r\nADVANCED INSTALLATION\r\n\r\nperform a git clone operation so that you get a local copy of the github repository\r\n","5":"BASIC INSTALLATION: \r\n\r\na. Download the zip file.\r\n\r\nb. Unpack it. In the uncompressed directory you will get \"colors\", \"autoload\" and \"doc\" sub-directories.\r\n\r\nc. If you do NOT use a bundle-based plugin (like Pathogen):\r\n     1 copy the content of the \"colors\" directory into your \".vim\/colors\" directory;\r\n     2 copy the content of the \"doc\" directory into your \".vim\/doc\" directory;\r\n        restart Vim and do :helptags;\r\n        do :help briofita, and read the help file to learn about Briofita;\r\n     3 run command :colorscheme briofita to start the colorscheme;\r\n     NOTE: if you use the Lightline statusline plugin it will automatically \r\n                  scan the autoload directory and detect the briofita theme.\r\n\r\nd. If you use Pathogen or other bundle-based plugin:\r\n     1 create under your \".vim\/bundle\" directory a new directory, and name it \"briofita\";\r\n        and copy the unzipped file tree under the \".vim\/bundle\/briofita\" directory;\r\n     2 restart Vim and do :Helptags (Pathogen command);\r\n        do :help briofita, and read the help file to learn about Briofita;\r\n     3 command :colorscheme briofita;\r\n\r\nTo uninstall, simply delete all the unzipped directory tree for Briofita from above mentioned directories.\r\n\r\nIf you want to install the colorscheme, but not the plugin follow\r\nthe above instructions \"c.1\" and \"c.3\" (or \"d.1\" and \"d.3\") and then just delete the plugin (\"briofita-support.vim\") from\r\nthe plugin sub-directory  and the help file (\"briofita.txt\") from the doc sub-directory.\r\n\r\nADVANCED INSTALLATION\r\n\r\nperform a git clone operation so that you get a local copy of the github repository\r\n","first_name":"Sergio","6":"Sergio","last_name":"Nobre","7":"Nobre","releases":[{"0":"4136","vim_version":"8.0","1":"8.0","script_version":"4.1.0","2":"4.1.0","version_comment":"Few syntax coloring changes (enhancements). Small number of new highlights. Added two global variables for the user to skip internal setting of two Vim options.","3":"Few syntax coloring changes (enhancements). Small number of new highlights. Added two global variables for the user to skip internal setting of two Vim options.","package":"briofita_v4.1.0.zip","4":"briofita_v4.1.0.zip","src_id":"26188","5":"26188","creation_date":"1534893822","6":"1534893822"},{"0":"4136","vim_version":"8.0","1":"8.0","script_version":"4.0.0","2":"4.0.0","version_comment":"Fully refactored Briofita colorscheme with improved colors for many file types and programming languages.","3":"Fully refactored Briofita colorscheme with improved colors for many file types and programming languages.","package":"briofita_v4.0.0.zip","4":"briofita_v4.0.0.zip","src_id":"25304","5":"25304","creation_date":"1497216479","6":"1497216479"}]},"4135":{"script_id":"4135","0":"4135","script_name":"change-hash-syntax","1":"change-hash-syntax","script_type":"syntax","2":"syntax","summary":"Change Ruby hash syntax to 1.9","3":"Change Ruby hash syntax to 1.9","description":"This plugin chnages Ruby hash syntax to 1.9\r\n\r\n# before\r\nhash = { :one => 1, :two => 2 }\r\n\r\n# after\r\nhash = { one: 1, two: 2 }\r\n\r\n\r\nTo change hash syntax, just call :ChangeHashSyntax. By default it operates on the entire file. Pass a range (or use V to select some lines) to restrict the portion of the file that gets fixed.","4":"This plugin chnages Ruby hash syntax to 1.9\r\n\r\n# before\r\nhash = { :one => 1, :two => 2 }\r\n\r\n# after\r\nhash = { one: 1, two: 2 }\r\n\r\n\r\nTo change hash syntax, just call :ChangeHashSyntax. By default it operates on the entire file. Pass a range (or use V to select some lines) to restrict the portion of the file that gets fixed.","install_details":"","5":"","first_name":"Vitaly","6":"Vitaly","last_name":"Tatarintsev","7":"Tatarintsev","releases":[{"0":"4135","vim_version":"7.0","1":"7.0","script_version":"0.01","2":"0.01","version_comment":"Initial upload","3":"Initial upload","package":"change-hash-syntax.vim","4":"change-hash-syntax.vim","src_id":"18274","5":"18274","creation_date":"1342470451","6":"1342470451"}]},"4134":{"script_id":"4134","0":"4134","script_name":"spacepaste.vim","1":"spacepaste.vim","script_type":"utility","2":"utility","summary":"Interface to spacepaste-based pastebins","3":"Interface to spacepaste-based pastebins","description":"GitHub URL: https:\/\/github.com\/jmcantrell\/vim-spacepaste","4":"GitHub URL: https:\/\/github.com\/jmcantrell\/vim-spacepaste","install_details":"Extract to ~\/.vim","5":"Extract to ~\/.vim","first_name":"Jeremy","6":"Jeremy","last_name":"Cantrell","7":"Cantrell","releases":[{"0":"4134","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"jmcantrell-vim-spacepaste-71bf16b.zip","4":"jmcantrell-vim-spacepaste-71bf16b.zip","src_id":"18270","5":"18270","creation_date":"1342410483","6":"1342410483"}]},"4133":{"script_id":"4133","0":"4133","script_name":"rainbow-end","1":"rainbow-end","script_type":"utility","2":"utility","summary":"Rainbow highlight Ruby block open\/close keywords","3":"Rainbow highlight Ruby block open\/close keywords","description":"This plugin highlights Ruby opening and closing keywords with a rainbow of colors.","4":"This plugin highlights Ruby opening and closing keywords with a rainbow of colors.","install_details":"* Use Pathogen or Vundle!                                                                                                                \r\n* Or the old fashioned way, drop rainbow_end.vim into .vim\/plugin.                                                                                                           \r\n* Either way you have to choose a mapping to toggle highlighting on and off and add it to your .vimrc, here is an example:                                                                                                                 \r\n     \r\n    nnoremap <silent> <leader>b :call ToggleRainbow()<CR>  ","5":"* Use Pathogen or Vundle!                                                                                                                \r\n* Or the old fashioned way, drop rainbow_end.vim into .vim\/plugin.                                                                                                           \r\n* Either way you have to choose a mapping to toggle highlighting on and off and add it to your .vimrc, here is an example:                                                                                                                 \r\n     \r\n    nnoremap <silent> <leader>b :call ToggleRainbow()<CR>  ","first_name":"Michael","6":"Michael","last_name":"Nussbaum","7":"Nussbaum","releases":[{"0":"4133","vim_version":"7.3","1":"7.3","script_version":"0.1.1","2":"0.1.1","version_comment":"Bug fixes","3":"Bug fixes","package":"rainbow-end.tgz","4":"rainbow-end.tgz","src_id":"18276","5":"18276","creation_date":"1342503704","6":"1342503704"},{"0":"4133","vim_version":"7.3","1":"7.3","script_version":"0.1.0","2":"0.1.0","version_comment":"Initial upload","3":"Initial upload","package":"rainbow-end.tgz","4":"rainbow-end.tgz","src_id":"18268","5":"18268","creation_date":"1342398994","6":"1342398994"}]},"4132":{"script_id":"4132","0":"4132","script_name":"QueryCommandComplete","1":"QueryCommandComplete","script_type":"utility","2":"utility","summary":"Create completions from any command","3":"Create completions from any command","description":"Query Command Complete\r\n======================\r\n\r\nVim plugin to suggest completions with the results of an external\r\nquery command.\r\n\r\nThe original intention is to use it as a mutt query_command wrapper\r\nto complete addresses in the mail headers, but it can be adapted\r\nto any other kind of functionality by modifying the exposed setting\r\nparameters.\r\n\r\nLast Change: 2013 Jun 16\r\nAuthor: Caio Rom\u00c3\u00a3o (http:\/\/caioromao.com)\r\nLicense: This file is placed in the public domain\r\nContributors:\r\n  Brian Henderson https:\/\/github.com\/bhenderson\r\n  Mark Stillwell  https:\/\/github.com\/marklee77\r\n  Rui Abreu Ferreira http:\/\/ruiabreu.org\r\n\r\nSetup:\r\n  This plugin exports the completion function QueryCommandComplete,\r\n  which can be set as the complete function (or omni function) for\r\n  any filetype. If you have a working mutt setup with query_command\r\n  configured, the plugin works out of the box.\r\n\r\n  Example:\r\n      let g:qcc_query_command='abook'\r\n      au BufRead \/tmp\/mutt* setlocal omnifunc=QueryCommandComplete\r\n\r\nSettings:\r\n  Note: Overriding settings on a buffer-basis is supported. So\r\n        b:qcc_query_command takes precedence over g:qcc_query_command\r\n\r\n  g:qcc_query_command\r\n      External command that queries for contacts\r\n      If empty, QueryCommandComplete tries to guess what command to\r\n      run by executing `mutt -Q query_command`.\r\n\r\n  g:qcc_line_separator\r\n      Separator for each entry in the result from the query\r\n      default: '\\n'\r\n\r\n  g:qcc_field_separator\r\n      Separator for the fields of an entry from the result\r\n      default: '\\t'\r\n\r\n  g:qcc_pattern\r\n      Pattern used to match against the current line to decide\r\n      whether to call the query command\r\n      default: '^\\(To\\|Cc\\|Bcc\\|From\\|Reply-To\\):'\r\n\r\n  g:qcc_multiline\r\n      Whether to try matching g:qcc_pattern against the current\r\n      and any previous line\r\n      default: 0\r\n\r\n  g:qcc_multiline_pattern\r\n      Pattern to match against the current line when deciding\r\n      wether to keep looking for a line that matches g:qcc_pattern\r\n      This provides finer control over the recursion, which\r\n      is useful if calling the completion on really big files.\r\n      default: '.*'\r\n\r\n  g:qcc_format_word\r\n      Format string to be used when building the word field\r\n      of the completion (i.e.: the final result, what gets fed into\r\n      the current line when you select an option)\r\n      default: '${1} <${0}>' (as in: FirstName <email@domain.com>)\r\n\r\n  g:qcc_format_abbr\r\n      Format string to be used when building the abbreviation\r\n      for the completion menu (i.e.: the first row in the completion\r\n      menu).\r\n      default: '${1}'\r\n\r\n  g:qcc_format_menu\r\n      Format string for the optional second column of the completion\r\n      menu.\r\n      default: '${2}'\r\n","4":"Query Command Complete\r\n======================\r\n\r\nVim plugin to suggest completions with the results of an external\r\nquery command.\r\n\r\nThe original intention is to use it as a mutt query_command wrapper\r\nto complete addresses in the mail headers, but it can be adapted\r\nto any other kind of functionality by modifying the exposed setting\r\nparameters.\r\n\r\nLast Change: 2013 Jun 16\r\nAuthor: Caio Rom\u00c3\u00a3o (http:\/\/caioromao.com)\r\nLicense: This file is placed in the public domain\r\nContributors:\r\n  Brian Henderson https:\/\/github.com\/bhenderson\r\n  Mark Stillwell  https:\/\/github.com\/marklee77\r\n  Rui Abreu Ferreira http:\/\/ruiabreu.org\r\n\r\nSetup:\r\n  This plugin exports the completion function QueryCommandComplete,\r\n  which can be set as the complete function (or omni function) for\r\n  any filetype. If you have a working mutt setup with query_command\r\n  configured, the plugin works out of the box.\r\n\r\n  Example:\r\n      let g:qcc_query_command='abook'\r\n      au BufRead \/tmp\/mutt* setlocal omnifunc=QueryCommandComplete\r\n\r\nSettings:\r\n  Note: Overriding settings on a buffer-basis is supported. So\r\n        b:qcc_query_command takes precedence over g:qcc_query_command\r\n\r\n  g:qcc_query_command\r\n      External command that queries for contacts\r\n      If empty, QueryCommandComplete tries to guess what command to\r\n      run by executing `mutt -Q query_command`.\r\n\r\n  g:qcc_line_separator\r\n      Separator for each entry in the result from the query\r\n      default: '\\n'\r\n\r\n  g:qcc_field_separator\r\n      Separator for the fields of an entry from the result\r\n      default: '\\t'\r\n\r\n  g:qcc_pattern\r\n      Pattern used to match against the current line to decide\r\n      whether to call the query command\r\n      default: '^\\(To\\|Cc\\|Bcc\\|From\\|Reply-To\\):'\r\n\r\n  g:qcc_multiline\r\n      Whether to try matching g:qcc_pattern against the current\r\n      and any previous line\r\n      default: 0\r\n\r\n  g:qcc_multiline_pattern\r\n      Pattern to match against the current line when deciding\r\n      wether to keep looking for a line that matches g:qcc_pattern\r\n      This provides finer control over the recursion, which\r\n      is useful if calling the completion on really big files.\r\n      default: '.*'\r\n\r\n  g:qcc_format_word\r\n      Format string to be used when building the word field\r\n      of the completion (i.e.: the final result, what gets fed into\r\n      the current line when you select an option)\r\n      default: '${1} <${0}>' (as in: FirstName <email@domain.com>)\r\n\r\n  g:qcc_format_abbr\r\n      Format string to be used when building the abbreviation\r\n      for the completion menu (i.e.: the first row in the completion\r\n      menu).\r\n      default: '${1}'\r\n\r\n  g:qcc_format_menu\r\n      Format string for the optional second column of the completion\r\n      menu.\r\n      default: '${2}'\r\n","install_details":"Just put querycommandcomplete.vim inside your plugins folder.\r\n\r\nFor pathogen\/vundle users:\r\n - https:\/\/github.com\/caio\/querycommandcomplete.vim","5":"Just put querycommandcomplete.vim inside your plugins folder.\r\n\r\nFor pathogen\/vundle users:\r\n - https:\/\/github.com\/caio\/querycommandcomplete.vim","first_name":"Caio","6":"Caio","last_name":"Rom\u00c3\u00a3o","7":"Rom\u00c3\u00a3o","releases":[{"0":"4132","vim_version":"7.0","1":"7.0","script_version":"0.4","2":"0.4","version_comment":"* Template support for the completion menu\r\n* Read settings from buffer variables \r\n* Dropped requirement for having everything set up during source time","3":"* Template support for the completion menu\r\n* Read settings from buffer variables \r\n* Dropped requirement for having everything set up during source time","package":"querycommandcomplete.vim","4":"querycommandcomplete.vim","src_id":"20369","5":"20369","creation_date":"1371588125","6":"1371588125"},{"0":"4132","vim_version":"7.0","1":"7.0","script_version":"0.3","2":"0.3","version_comment":"New features contributed by marklee77 on github: support for a placeholder (%s) in g:qcc_pattern and multiline feature (on my default if using the plugin without any configuration)","3":"New features contributed by marklee77 on github: support for a placeholder (%s) in g:qcc_pattern and multiline feature (on my default if using the plugin without any configuration)","package":"querycommandcomplete.vim","4":"querycommandcomplete.vim","src_id":"19255","5":"19255","creation_date":"1356808589","6":"1356808589"},{"0":"4132","vim_version":"7.0","1":"7.0","script_version":"0.2","2":"0.2","version_comment":"New functionality contributed by bhenderson on github. Now the plugin can be used without previous configuration when the user has mutt properly setup.","3":"New functionality contributed by bhenderson on github. Now the plugin can be used without previous configuration when the user has mutt properly setup.","package":"querycommandcomplete.vim","4":"querycommandcomplete.vim","src_id":"18632","5":"18632","creation_date":"1347906023","6":"1347906023"},{"0":"4132","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"querycommandcomplete.vim","4":"querycommandcomplete.vim","src_id":"18266","5":"18266","creation_date":"1342365877","6":"1342365877"}]},"4131":{"script_id":"4131","0":"4131","script_name":"bls","1":"bls","script_type":"utility","2":"utility","summary":"bls: is a python script to list buffers opened in all (g)vim servers","3":"bls: is a python script to list buffers opened in all (g)vim servers","description":"This is a python script, intended to use in a terminal. It will list all the buffers opened in currently running vim servers (however all the suspended servers will be omitted)","4":"This is a python script, intended to use in a terminal. It will list all the buffers opened in currently running vim servers (however all the suspended servers will be omitted)","install_details":"Put the scrip somewhere in your $PATH and make it executable. Your vim (gvim) need to be compiled with the client-server feature (:echo has(\"client-server\")). Furthermore, if you use vim rather than gvim, you'd better make an alias in your shell to \"vim --servername VIM\". Only if you specify the --servername option the script will see the buffers of this vim instance (gvim is automatically run as a server). ","5":"Put the scrip somewhere in your $PATH and make it executable. Your vim (gvim) need to be compiled with the client-server feature (:echo has(\"client-server\")). Furthermore, if you use vim rather than gvim, you'd better make an alias in your shell to \"vim --servername VIM\". Only if you specify the --servername option the script will see the buffers of this vim instance (gvim is automatically run as a server). ","first_name":"Marcin","6":"Marcin","last_name":"Szamotulski","7":"Szamotulski","releases":[{"0":"4131","vim_version":"7.0","1":"7.0","script_version":"1","2":"1","version_comment":"Initial upload","3":"Initial upload","package":"bls","4":"bls","src_id":"18258","5":"18258","creation_date":"1342281719","6":"1342281719"}]},"4130":{"script_id":"4130","0":"4130","script_name":"vim-pipe","1":"vim-pipe","script_type":"utility","2":"utility","summary":"Send a buffer to a shell command & quickly see the result.","3":"Send a buffer to a shell command & quickly see the result.","description":"Vim Pipe provides REPL-like development for other shell tools. For example you can instantly send an SQL script to the database and see the results in a temporary buffer.\r\n\r\nSee https:\/\/github.com\/krisajenkins\/vim-pipe for more.","4":"Vim Pipe provides REPL-like development for other shell tools. For example you can instantly send an SQL script to the database and see the results in a temporary buffer.\r\n\r\nSee https:\/\/github.com\/krisajenkins\/vim-pipe for more.","install_details":"Install Pathogen (https:\/\/github.com\/tpope\/vim-pathogen\/).\r\nUnpack to ~\/.vim\/bundle\/vim-pipe.","5":"Install Pathogen (https:\/\/github.com\/tpope\/vim-pathogen\/).\r\nUnpack to ~\/.vim\/bundle\/vim-pipe.","first_name":"Kris","6":"Kris","last_name":"Jenkins","7":"Jenkins","releases":[{"0":"4130","vim_version":"7.0","1":"7.0","script_version":"1.2.0","2":"1.2.0","version_comment":"Bugfix: Line numbering of the input was off by one.\r\nThe output buffer now shows execution time.\r\nImproved docs.\r\n","3":"Bugfix: Line numbering of the input was off by one.\r\nThe output buffer now shows execution time.\r\nImproved docs.\r\n","package":"vim-pipe.tar.gz","4":"vim-pipe.tar.gz","src_id":"18486","5":"18486","creation_date":"1345845113","6":"1345845113"},{"0":"4130","vim_version":"7.0","1":"7.0","script_version":"1.1.0","2":"1.1.0","version_comment":"Improved documentation & a \"Running\" message, to give some feedback when the command takes a while to run.","3":"Improved documentation & a \"Running\" message, to give some feedback when the command takes a while to run.","package":"vim-pipe.tgz","4":"vim-pipe.tgz","src_id":"18316","5":"18316","creation_date":"1343308325","6":"1343308325"},{"0":"4130","vim_version":"7.0","1":"7.0","script_version":"1.0.0","2":"1.0.0","version_comment":"Initial upload","3":"Initial upload","package":"vim-pipe.tgz","4":"vim-pipe.tgz","src_id":"18254","5":"18254","creation_date":"1342170645","6":"1342170645"}]},"4129":{"script_id":"4129","0":"4129","script_name":"ConflictDetection","1":"ConflictDetection","script_type":"utility","2":"utility","summary":"Detect and highlight SCM conflict markers.","3":"Detect and highlight SCM conflict markers.","description":"DESCRIPTION\r\nThis plugin detects and highlights conflict markers such as <<<<<<<, =======,\r\nand >>>>>>>, which are inserted by source code management systems on merges to\r\nindicate that the automatic resolution failed; this plugin helps you with\r\nbecoming aware of and finding them.\r\n\r\nRELATED WORKS\r\nTo quickly locate and resolve the conflicts, you can use the motions and text\r\nobjects provided by the companion ConflictMotions.vim plugin (vimscript\r\n#3991).\r\n\r\n\r\nUSAGE\r\nThe plugin automatically adds syntax definitions for the conflict markers and\r\nthe conflicted lines which are enclosed in the markers. Lines originating from\r\n\"our\" version are highlighted in a different way than lines from \"their\"\r\nversion, so it's easier for you to visually differentiate the alternatives and\r\nmake the right editing choices to resolve the conflict. The \"base\" version of\r\nthe diff3-style syntax is supported, too.\r\n\r\n:ConflictSyntax [{syntax}]\r\n                        Remove \/ change the syntax (to {syntax}) while keeping\r\n                        the conflict syntax definitions (:setl syntax=...\r\n                        would remove them as well). Useful when the filetype's\r\n                        own syntax interferes with the overlaid conflict\r\n                        syntax definitions.\r\n\r\nThe plugin warns you when a buffer that contains conflict markers is edited or\r\nsaved. Cp. g:ConflictDetection_WarnEvents\r\n\r\nThe detections stores its status in the buffer variable b:conflicted. You can\r\nevaluate this boolean variable in a custom statusline to indicate whether\r\nthe buffer contains conflicts.","4":"DESCRIPTION\r\nThis plugin detects and highlights conflict markers such as <<<<<<<, =======,\r\nand >>>>>>>, which are inserted by source code management systems on merges to\r\nindicate that the automatic resolution failed; this plugin helps you with\r\nbecoming aware of and finding them.\r\n\r\nRELATED WORKS\r\nTo quickly locate and resolve the conflicts, you can use the motions and text\r\nobjects provided by the companion ConflictMotions.vim plugin (vimscript\r\n#3991).\r\n\r\n\r\nUSAGE\r\nThe plugin automatically adds syntax definitions for the conflict markers and\r\nthe conflicted lines which are enclosed in the markers. Lines originating from\r\n\"our\" version are highlighted in a different way than lines from \"their\"\r\nversion, so it's easier for you to visually differentiate the alternatives and\r\nmake the right editing choices to resolve the conflict. The \"base\" version of\r\nthe diff3-style syntax is supported, too.\r\n\r\n:ConflictSyntax [{syntax}]\r\n                        Remove \/ change the syntax (to {syntax}) while keeping\r\n                        the conflict syntax definitions (:setl syntax=...\r\n                        would remove them as well). Useful when the filetype's\r\n                        own syntax interferes with the overlaid conflict\r\n                        syntax definitions.\r\n\r\nThe plugin warns you when a buffer that contains conflict markers is edited or\r\nsaved. Cp. g:ConflictDetection_WarnEvents\r\n\r\nThe detections stores its status in the buffer variable b:conflicted. You can\r\nevaluate this boolean variable in a custom statusline to indicate whether\r\nthe buffer contains conflicts.","install_details":"INSTALLATION\r\nThis script is packaged as a vimball. If you have the \"gunzip\" decompressor\r\nin your PATH, simply edit the *.vmb.gz package in Vim; otherwise, decompress\r\nthe archive first, e.g. using WinZip. Inside Vim, install by sourcing the\r\nvimball or via the :UseVimball command.\r\n    vim ConflictDetection*.vmb.gz\r\n    :so %\r\nTo uninstall, use the :RmVimball command.\r\n\r\nDEPENDENCIES\r\n- Requires Vim 7.0 or higher.\r\n- Requires the ingo-library.vim plugin (vimscript #4433), version 1.003 or\r\n  higher.\r\n\r\n\r\nCONFIGURATION\r\nFor a permanent configuration, put the following commands into your vimrc:\r\n\r\nBy default, the DiffAdd (our version), DiffText (their version), and\r\nDiffChange (base version) highlight groups are used for highlighting\r\nconflicted lines. The lines containing the highlight markers are colored with\r\na foreground color derived from the correspoding groups.\r\nYou may define your own colors via the :highlight command:\r\n    highlight def link conflictOurs                     guibg=Green\r\n    highlight def link conflictBase                     guibg=Brown\r\n    highlight def link conflictTheirs                   guibg=Red\r\n    highlight def link conflictSeparatorMarkerSymbol    guifg=Black\r\n    highlight def conflictOursMarker                    guifg=Green\r\n    highlight def conflictBaseMarker                    guifg=Brown\r\n    highlight def conflictTheirsMarker                  guifg=Red\r\n\r\nThe buffer is searched for conflict markers when a file is edited and when the\r\nbuffer is saved, and the status is updated accordingly. The autocmd-events\r\nare stored in a variable. If you don't need the auto-detection, empty the\r\nevent list:\r\n    let g:ConflictDetection_AutoDetectEvents = ''\r\n\r\nA warning message is issued when the buffer is read or written and conflict\r\nmarkers have been detected. You can empty \/ edit the autocmd-events list if\r\nyou don't want a warning at all \/ on buffer writes only:\r\n    let g:ConflictDetection_WarnEvents = 'BufWritePost'","5":"INSTALLATION\r\nThis script is packaged as a vimball. If you have the \"gunzip\" decompressor\r\nin your PATH, simply edit the *.vmb.gz package in Vim; otherwise, decompress\r\nthe archive first, e.g. using WinZip. Inside Vim, install by sourcing the\r\nvimball or via the :UseVimball command.\r\n    vim ConflictDetection*.vmb.gz\r\n    :so %\r\nTo uninstall, use the :RmVimball command.\r\n\r\nDEPENDENCIES\r\n- Requires Vim 7.0 or higher.\r\n- Requires the ingo-library.vim plugin (vimscript #4433), version 1.003 or\r\n  higher.\r\n\r\n\r\nCONFIGURATION\r\nFor a permanent configuration, put the following commands into your vimrc:\r\n\r\nBy default, the DiffAdd (our version), DiffText (their version), and\r\nDiffChange (base version) highlight groups are used for highlighting\r\nconflicted lines. The lines containing the highlight markers are colored with\r\na foreground color derived from the correspoding groups.\r\nYou may define your own colors via the :highlight command:\r\n    highlight def link conflictOurs                     guibg=Green\r\n    highlight def link conflictBase                     guibg=Brown\r\n    highlight def link conflictTheirs                   guibg=Red\r\n    highlight def link conflictSeparatorMarkerSymbol    guifg=Black\r\n    highlight def conflictOursMarker                    guifg=Green\r\n    highlight def conflictBaseMarker                    guifg=Brown\r\n    highlight def conflictTheirsMarker                  guifg=Red\r\n\r\nThe buffer is searched for conflict markers when a file is edited and when the\r\nbuffer is saved, and the status is updated accordingly. The autocmd-events\r\nare stored in a variable. If you don't need the auto-detection, empty the\r\nevent list:\r\n    let g:ConflictDetection_AutoDetectEvents = ''\r\n\r\nA warning message is issued when the buffer is read or written and conflict\r\nmarkers have been detected. You can empty \/ edit the autocmd-events list if\r\nyou don't want a warning at all \/ on buffer writes only:\r\n    let g:ConflictDetection_WarnEvents = 'BufWritePost'","first_name":"Ingo","6":"Ingo","last_name":"Karkat","7":"Karkat","releases":[{"0":"4129","vim_version":"7.0","1":"7.0","script_version":"1.12","2":"1.12","version_comment":"- To avoid false positives (e.g. in nested email replies), ensure that both \"our\" and \"theirs\" markers do exist.\r\n- Add dependency to ingo-library (vimscript #4433) *** DOWNLOAD AND INSTALL SEPARATELY ***","3":"- To avoid false positives (e.g. in nested email replies), ensure that both \"our\" and \"theirs\" markers do exist.\r\n- Add dependency to ingo-library (vimscript #4433) *** DOWNLOAD AND INSTALL SEPARATELY ***","package":"ConflictDetection-1.12.vmb.gz","4":"ConflictDetection-1.12.vmb.gz","src_id":"19713","5":"19713","creation_date":"1364418131","6":"1364418131"},{"0":"4129","vim_version":"7.0","1":"7.0","script_version":"1.11","2":"1.11","version_comment":"FIX: Prevent error on Vim 7.0 - 7.2.","3":"FIX: Prevent error on Vim 7.0 - 7.2.","package":"ConflictDetection-1.11.vmb.gz","4":"ConflictDetection-1.11.vmb.gz","src_id":"19107","5":"19107","creation_date":"1354640848","6":"1354640848"},{"0":"4129","vim_version":"7.0","1":"7.0","script_version":"1.10","2":"1.10","version_comment":"ENH: Add :ConflictSyntax command to work around interference of the conflict highlightings with the original filetype's syntax.","3":"ENH: Add :ConflictSyntax command to work around interference of the conflict highlightings with the original filetype's syntax.","package":"ConflictDetection-1.10.vmb.gz","4":"ConflictDetection-1.10.vmb.gz","src_id":"19106","5":"19106","creation_date":"1354633460","6":"1354633460"},{"0":"4129","vim_version":"7.0","1":"7.0","script_version":"1.02","2":"1.02","version_comment":"FIX: Avoid E417 \/ E421 in conflict marker highlight group definitions when no original color is defined (i.e. when the colorscheme does not define a cterm \/ gui background color for DiffAdd\/Change\/Text). Thanks to Dave Goodell for sending a patch.\r\n","3":"FIX: Avoid E417 \/ E421 in conflict marker highlight group definitions when no original color is defined (i.e. when the colorscheme does not define a cterm \/ gui background color for DiffAdd\/Change\/Text). Thanks to Dave Goodell for sending a patch.\r\n","package":"ConflictDetection-1.02.vmb.gz","4":"ConflictDetection-1.02.vmb.gz","src_id":"18983","5":"18983","creation_date":"1353100485","6":"1353100485"},{"0":"4129","vim_version":"7.0","1":"7.0","script_version":"1.01","2":"1.01","version_comment":"Avoid long search delays on very large files.","3":"Avoid long search delays on very large files.","package":"ConflictDetection-1.01.vmb.gz","4":"ConflictDetection-1.01.vmb.gz","src_id":"18825","5":"18825","creation_date":"1350491407","6":"1350491407"},{"0":"4129","vim_version":"7.0","1":"7.0","script_version":"1.00","2":"1.00","version_comment":"Initial upload","3":"Initial upload","package":"ConflictDetection.vba.gz","4":"ConflictDetection.vba.gz","src_id":"18253","5":"18253","creation_date":"1342162637","6":"1342162637"}]},"4128":{"script_id":"4128","0":"4128","script_name":"log4perl.vim","1":"log4perl.vim","script_type":"syntax","2":"syntax","summary":"Log::Log4perl configuration syntax","3":"Log::Log4perl configuration syntax","description":"Syntax highlighting for a great Perl logging module Log::Log4perl, descendant of Java's Log4j.\r\n","4":"Syntax highlighting for a great Perl logging module Log::Log4perl, descendant of Java's Log4j.\r\n","install_details":"","5":"","first_name":"Stanislaw","6":"Stanislaw","last_name":"Klekot","7":"Klekot","releases":[{"0":"4128","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"log4perl.vim","4":"log4perl.vim","src_id":"18250","5":"18250","creation_date":"1342125274","6":"1342125274"}]},"4127":{"script_id":"4127","0":"4127","script_name":"slapd.vim","1":"slapd.vim","script_type":"syntax","2":"syntax","summary":"OpenLDAP (database, access and schema) configuration","3":"OpenLDAP (database, access and schema) configuration","description":"Syntax highlighting for OpenLDAP configuration file. This syntax supports databases and daemon configuration, tree access directives and schema definition, that is, most of the things required in OpenLDAP administration.\r\nNote that this script is intended for monolithic slapd.conf, not for config stored in LDAP tree. The latter one is to be edited with LDAP client, not with text editor.\r\n","4":"Syntax highlighting for OpenLDAP configuration file. This syntax supports databases and daemon configuration, tree access directives and schema definition, that is, most of the things required in OpenLDAP administration.\r\nNote that this script is intended for monolithic slapd.conf, not for config stored in LDAP tree. The latter one is to be edited with LDAP client, not with text editor.\r\n","install_details":"","5":"","first_name":"Stanislaw","6":"Stanislaw","last_name":"Klekot","7":"Klekot","releases":[{"0":"4127","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"slapd.vim","4":"slapd.vim","src_id":"18249","5":"18249","creation_date":"1342124729","6":"1342124729"}]},"4126":{"script_id":"4126","0":"4126","script_name":"fix-git-diff-path.vim","1":"fix-git-diff-path.vim","script_type":"ftplugin","2":"ftplugin","summary":"Fix file paths from git diff output to DoTheRightThing","3":"Fix file paths from git diff output to DoTheRightThing","description":"https:\/\/github.com\/alikins\/vim-fix-git-diff-path\r\n\r\ngit diff includes a \"a\/path\/to\/file\" in git diff\r\noutput. This is a pain, if you want to cut and\r\npaste that path. This tries to let you just\r\nc&p that entire prefixed path and do the\r\nright thing. Ie, open the file referenced.\r\nIt should work anywhere in the git project\r\nof the current working dir. It's mostly\r\nintended for use from the command line but\r\nin theory, any file loading command should work\r\nwe well.\r\n\r\nbugs: - doesn't work if you are out of the git project\r\n        directory.\r\n      - probably confused if you have an actual file\r\n        name something like a\/path\/to\/file\r\n\r\n\r\nthis is based heavily on file_line.vim form\r\nhttps:\/\/github.com\/bogado\/file-line\r\n","4":"https:\/\/github.com\/alikins\/vim-fix-git-diff-path\r\n\r\ngit diff includes a \"a\/path\/to\/file\" in git diff\r\noutput. This is a pain, if you want to cut and\r\npaste that path. This tries to let you just\r\nc&p that entire prefixed path and do the\r\nright thing. Ie, open the file referenced.\r\nIt should work anywhere in the git project\r\nof the current working dir. It's mostly\r\nintended for use from the command line but\r\nin theory, any file loading command should work\r\nwe well.\r\n\r\nbugs: - doesn't work if you are out of the git project\r\n        directory.\r\n      - probably confused if you have an actual file\r\n        name something like a\/path\/to\/file\r\n\r\n\r\nthis is based heavily on file_line.vim form\r\nhttps:\/\/github.com\/bogado\/file-line\r\n","install_details":"https:\/\/github.com\/alikins\/vim-fix-git-diff-path","5":"https:\/\/github.com\/alikins\/vim-fix-git-diff-path","first_name":"Adrian","6":"Adrian","last_name":"LIkins","7":"LIkins","releases":[{"0":"4126","vim_version":"7.0","1":"7.0","script_version":"37.4.0","2":"37.4.0","version_comment":"Initial upload","3":"Initial upload","package":"vim-fix-git-diff-path-37.4.0.tar.gz","4":"vim-fix-git-diff-path-37.4.0.tar.gz","src_id":"18245","5":"18245","creation_date":"1342041700","6":"1342041700"}]},"4125":{"script_id":"4125","0":"4125","script_name":"tagbar-phpctags","1":"tagbar-phpctags","script_type":"utility","2":"utility","summary":"Using phpctags to generate php ctags index for vim plugin tagbar.","3":"Using phpctags to generate php ctags index for vim plugin tagbar.","description":"Github Reop: https:\/\/github.com\/techlivezheng\/tagbar-phpctags\r\n\r\nAn addon plugin for vimscript#3465 using [phpctags](https:\/\/github.com\/techlivezheng\/phpctags) to generate php ctags index.\r\n\r\nProvide a much better PHP syntax outline support than the orginal ctags. Methods and properties even local variables assigned in functions are list in their own scope.\r\n\r\nLocation of phpctags should be in system '$PATH' environment variable.\r\n\r\nOr, the locateion of phpctags can be configured in vimrc as such:\r\n\r\nlet g:tagbar_phpctags_bin='PATH_TO_phpctags'","4":"Github Reop: https:\/\/github.com\/techlivezheng\/tagbar-phpctags\r\n\r\nAn addon plugin for vimscript#3465 using [phpctags](https:\/\/github.com\/techlivezheng\/phpctags) to generate php ctags index.\r\n\r\nProvide a much better PHP syntax outline support than the orginal ctags. Methods and properties even local variables assigned in functions are list in their own scope.\r\n\r\nLocation of phpctags should be in system '$PATH' environment variable.\r\n\r\nOr, the locateion of phpctags can be configured in vimrc as such:\r\n\r\nlet g:tagbar_phpctags_bin='PATH_TO_phpctags'","install_details":"","5":"","first_name":"Techlive","6":"Techlive","last_name":"Zheng","7":"Zheng","releases":[{"0":"4125","vim_version":"7.0","1":"7.0","script_version":"0.5.1","2":"0.5.1","version_comment":"support for phpctags v0.5.1","3":"support for phpctags v0.5.1","package":"tagbar-phpctags-0.5.1.zip","4":"tagbar-phpctags-0.5.1.zip","src_id":"20419","5":"20419","creation_date":"1372082453","6":"1372082453"},{"0":"4125","vim_version":"7.0","1":"7.0","script_version":"0.5","2":"0.5","version_comment":"support for phpctags v0.5","3":"support for phpctags v0.5","package":"tagbar-phpctags-0.5.zip","4":"tagbar-phpctags-0.5.zip","src_id":"20417","5":"20417","creation_date":"1372069530","6":"1372069530"},{"0":"4125","vim_version":"7.0","1":"7.0","script_version":"0.4.2","2":"0.4.2","version_comment":"support for phpctags v0.4.2","3":"support for phpctags v0.4.2","package":"tagbar-phpctags-0.4.2.zip","4":"tagbar-phpctags-0.4.2.zip","src_id":"20062","5":"20062","creation_date":"1367994129","6":"1367994129"},{"0":"4125","vim_version":"7.0","1":"7.0","script_version":"0.4.1","2":"0.4.1","version_comment":"support for phpctags v0.4.1","3":"support for phpctags v0.4.1","package":"tagbar-phpctags-0.4.1.zip","4":"tagbar-phpctags-0.4.1.zip","src_id":"20043","5":"20043","creation_date":"1367932562","6":"1367932562"},{"0":"4125","vim_version":"7.0","1":"7.0","script_version":"0.4","2":"0.4","version_comment":"support for phpctags v0.4","3":"support for phpctags v0.4","package":"tagbar-phpctags-0.4.zip","4":"tagbar-phpctags-0.4.zip","src_id":"20042","5":"20042","creation_date":"1367932244","6":"1367932244"},{"0":"4125","vim_version":"7.0","1":"7.0","script_version":"0.3","2":"0.3","version_comment":"support for phpctags v0.3","3":"support for phpctags v0.3","package":"tagbar-phpctags-0.3.zip","4":"tagbar-phpctags-0.3.zip","src_id":"19948","5":"19948","creation_date":"1367040790","6":"1367040790"},{"0":"4125","vim_version":"7.0","1":"7.0","script_version":"0.2","2":"0.2","version_comment":"Support for phpctags v0.2.","3":"Support for phpctags v0.2.","package":"techlivezheng-tagbar-phpctags-v0.2-0-ge22db08.tar.gz","4":"techlivezheng-tagbar-phpctags-v0.2-0-ge22db08.tar.gz","src_id":"18493","5":"18493","creation_date":"1345971822","6":"1345971822"},{"0":"4125","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"techlivezheng-tagbar-phpctags-v0.1-0-g2301253.tar.gz","4":"techlivezheng-tagbar-phpctags-v0.1-0-g2301253.tar.gz","src_id":"18242","5":"18242","creation_date":"1341879363","6":"1341879363"}]},"4124":{"script_id":"4124","0":"4124","script_name":"oh-l_l_vim","1":"oh-l_l_vim","script_type":"color scheme","2":"color scheme","summary":"oh-l_l_vim","3":"oh-l_l_vim","description":"oh-l_l_vim","4":"oh-l_l_vim","install_details":"oh-l_l_vim","5":"oh-l_l_vim","first_name":"vim","6":"vim","last_name":"cai","7":"cai","releases":[{"0":"4124","vim_version":"7.3","1":"7.3","script_version":"7.0","2":"7.0","version_comment":"Initial upload","3":"Initial upload","package":"oh-l_l_vim","4":"oh-l_l_vim","src_id":"18238","5":"18238","creation_date":"1341826272","6":"1341826272"}]},"4123":{"script_id":"4123","0":"4123","script_name":"TaggedSearchPattern","1":"TaggedSearchPattern","script_type":"utility","2":"utility","summary":"Attach names to search patterns for easier recall.","3":"Attach names to search patterns for easier recall.","description":"DESCRIPTION\r\nYou use text searches all the time in Vim. While it is simple to recall\r\nprevious patterns through the cmdline-history, quickly recognizing them can\r\nbe hard, especially if it's a long convoluted regular expression that you've\r\nconfidently built some hours ago, but now all variants stored in the history\r\nlook like nearly identical gibberish.\r\n\r\nThis plugin allows you to \"tag\" individual searches with a name, so that these\r\nsearches are documented and therefore become easier to recognize and recall.\r\nYou can also pre-seed your search history with frequently needed searches.\r\n\r\nHOW IT WORKS\r\nTagged searches reside in the normal search history like all other searches.\r\nThe tagging works by prepending a special regular expression branch that never\r\nmatches any text.\r\n\r\nRELATED WORKS\r\nInspired by\r\nhttp:\/\/stackoverflow.com\/questions\/10174171\/indicator-to-see-from-which-function-a-search-string-comes\/\r\n\r\nAn alternative is to append a literal NUL character (^@, enter via <C-V><C-@>)\r\nafter the concluded search pattern, e.g.\r\n    \/foobar\/^@tag here\r\nVim will ignore everything after the NUL byte, but it'll still show the whole\r\nline in the search history, including the tag. (Discovered by glts in\r\nhttp:\/\/stackoverflow.com\/a\/20020360\/813602) This depends on an implementation\r\ndetail, and the tag position makes it more difficult to search \/ recall.\r\n\r\nUSAGE\r\nInside the search command-lines (:\/, :?), tag (and un-tag) the current\r\nsearch with CTRL-T, type the tag name, and store and activate the search with\r\n<Enter> as usual.\r\nSince tagged searches start with the tag, recall is as simple as entering the\r\nsearch command-line via :\/, typing the first letters of the tag and pressing\r\nc_<Up> (repeatedly if there are many).\r\nWhen you're in the cmdline-window via q\/, just search for tags via\r\n\/^{tag-name}. Or open a filtered view of the search cmdline-window through\r\nq_CTRL-T.\r\n\r\nCTRL-T                  Prepend the search-neutral tag expression and position\r\n                        the cursor before it at the beginning of the\r\n                        command-line, so that the tag can be entered.\r\n                        For the tag, stick to alphanumeric characters\r\n                        (whitespace is okay, too). Do not use characters like\r\n                        \\, &, |, etc. that have a special meaning in a regexp!\r\n\r\n                        When the current search already has been tagged:\r\n                        Remove the tag and the following search-neutral tag\r\n                        expression.\r\n                        You can use CTRL-T CTRL-T to rename a tagged search\r\n                        pattern.\r\n\r\nCTRL-G CTRL-T           Like c_CTRL-T, but ensure that the search tag will\r\n                        be unique in the search history (by removing any\r\n                        previous searches with the same tag)\r\n                        g:TaggedSearchPattern_UniqueTagPattern\r\n\r\nq CTRL-T                Open the search command-line window as with q\/ and\r\n                        list only tagged searches. The tag names are\r\n                        highlighted for easier recognition. As usual, <Enter>\r\n                        uses the current search pattern under the cursor, or\r\n                        press CTRL-C to continue editing in Command-line mode.\r\n\r\nIf you don't use them, tagged searches will eventually be expelled from the\r\nsearch history, just like any other search pattern. You can delay this by\r\nincreasing the 'history' setting and the \"\/\" value of 'viminfo'.\r\nAlternatively, you can automatically define often-used tagged searches\r\n(globally in .vimrc, or maybe only when certain filetypes are loaded via a\r\nftplugin), like this:\r\n    call TaggedSearchPattern#HistAdd('mytag', '\\<search\\d\\+\\|pattern\\>')\r\n    call TaggedSearchPattern#HistAdd('unique', '\\<pattern\\>', 1)","4":"DESCRIPTION\r\nYou use text searches all the time in Vim. While it is simple to recall\r\nprevious patterns through the cmdline-history, quickly recognizing them can\r\nbe hard, especially if it's a long convoluted regular expression that you've\r\nconfidently built some hours ago, but now all variants stored in the history\r\nlook like nearly identical gibberish.\r\n\r\nThis plugin allows you to \"tag\" individual searches with a name, so that these\r\nsearches are documented and therefore become easier to recognize and recall.\r\nYou can also pre-seed your search history with frequently needed searches.\r\n\r\nHOW IT WORKS\r\nTagged searches reside in the normal search history like all other searches.\r\nThe tagging works by prepending a special regular expression branch that never\r\nmatches any text.\r\n\r\nRELATED WORKS\r\nInspired by\r\nhttp:\/\/stackoverflow.com\/questions\/10174171\/indicator-to-see-from-which-function-a-search-string-comes\/\r\n\r\nAn alternative is to append a literal NUL character (^@, enter via <C-V><C-@>)\r\nafter the concluded search pattern, e.g.\r\n    \/foobar\/^@tag here\r\nVim will ignore everything after the NUL byte, but it'll still show the whole\r\nline in the search history, including the tag. (Discovered by glts in\r\nhttp:\/\/stackoverflow.com\/a\/20020360\/813602) This depends on an implementation\r\ndetail, and the tag position makes it more difficult to search \/ recall.\r\n\r\nUSAGE\r\nInside the search command-lines (:\/, :?), tag (and un-tag) the current\r\nsearch with CTRL-T, type the tag name, and store and activate the search with\r\n<Enter> as usual.\r\nSince tagged searches start with the tag, recall is as simple as entering the\r\nsearch command-line via :\/, typing the first letters of the tag and pressing\r\nc_<Up> (repeatedly if there are many).\r\nWhen you're in the cmdline-window via q\/, just search for tags via\r\n\/^{tag-name}. Or open a filtered view of the search cmdline-window through\r\nq_CTRL-T.\r\n\r\nCTRL-T                  Prepend the search-neutral tag expression and position\r\n                        the cursor before it at the beginning of the\r\n                        command-line, so that the tag can be entered.\r\n                        For the tag, stick to alphanumeric characters\r\n                        (whitespace is okay, too). Do not use characters like\r\n                        \\, &, |, etc. that have a special meaning in a regexp!\r\n\r\n                        When the current search already has been tagged:\r\n                        Remove the tag and the following search-neutral tag\r\n                        expression.\r\n                        You can use CTRL-T CTRL-T to rename a tagged search\r\n                        pattern.\r\n\r\nCTRL-G CTRL-T           Like c_CTRL-T, but ensure that the search tag will\r\n                        be unique in the search history (by removing any\r\n                        previous searches with the same tag)\r\n                        g:TaggedSearchPattern_UniqueTagPattern\r\n\r\nq CTRL-T                Open the search command-line window as with q\/ and\r\n                        list only tagged searches. The tag names are\r\n                        highlighted for easier recognition. As usual, <Enter>\r\n                        uses the current search pattern under the cursor, or\r\n                        press CTRL-C to continue editing in Command-line mode.\r\n\r\nIf you don't use them, tagged searches will eventually be expelled from the\r\nsearch history, just like any other search pattern. You can delay this by\r\nincreasing the 'history' setting and the \"\/\" value of 'viminfo'.\r\nAlternatively, you can automatically define often-used tagged searches\r\n(globally in .vimrc, or maybe only when certain filetypes are loaded via a\r\nftplugin), like this:\r\n    call TaggedSearchPattern#HistAdd('mytag', '\\<search\\d\\+\\|pattern\\>')\r\n    call TaggedSearchPattern#HistAdd('unique', '\\<pattern\\>', 1)","install_details":"INSTALLATION\r\nThe code is hosted in a Git repo at\r\n    https:\/\/github.com\/inkarkat\/vim-TaggedSearchPattern\r\nYou can use your favorite plugin manager, or \"git clone\" into a directory used\r\nfor Vim packages. Releases are on the \"stable\" branch, the latest unstable\r\ndevelopment snapshot on \"master\".\r\n\r\nThis script is also packaged as a vimball. If you have the \"gunzip\"\r\ndecompressor in your PATH, simply edit the *.vmb.gz package in Vim; otherwise,\r\ndecompress the archive first, e.g. using WinZip. Inside Vim, install by\r\nsourcing the vimball or via the :UseVimball command.\r\n    vim TaggedSearchPattern*.vmb.gz\r\n    :so %\r\nTo uninstall, use the :RmVimball command.\r\n\r\nDEPENDENCIES\r\n- Requires Vim 7.0 or higher.\r\n\r\nCONFIGURATION\r\nFor a permanent configuration, put the following commands into your vimrc:\r\n\r\nFor certain tag names, you can ensure that each tagged search pattern only\r\nexists once in the search history (previous patterns with the same tag are\r\ndeleted). By default, any tag name ending with a \"!\" is a unique one:\r\n    let g:TaggedSearchPattern_UniqueTagPattern = '.!$'\r\nTo make all tag searches unique, use this:\r\n    let g:TaggedSearchPattern_UniqueTagPattern = '.'\r\n\r\nTo turn off the highlighting of the tag name and search-neutral tag expression\r\nin the search cmdline-window:\r\n    let g:TaggedSearchPattern_HighlightTags = 0\r\n\r\nTo change the highlighting colors, redefine (after any :colorscheme command)\r\nor link the two highlight groups:\r\n    highlight link TaggedSearchTag Search\r\n    highlight TaggedSearchNeutral ctermfg=Black guifg=White\r\n\r\nIf you want to use different mappings, map your keys to the\r\n<Plug>(TaggedSearchPattern...) mapping targets _before_ sourcing the script\r\n(e.g. in your vimrc):\r\n    cmap <C-t> <Plug>(TaggedSearchPatternToggle)\r\n    cmap <C-g><C-t> <Plug>(TaggedSearchPatternUniqueToggle)\r\n    nmap q<C-t> <Plug>(TaggedSearchPatternList)","5":"INSTALLATION\r\nThe code is hosted in a Git repo at\r\n    https:\/\/github.com\/inkarkat\/vim-TaggedSearchPattern\r\nYou can use your favorite plugin manager, or \"git clone\" into a directory used\r\nfor Vim packages. Releases are on the \"stable\" branch, the latest unstable\r\ndevelopment snapshot on \"master\".\r\n\r\nThis script is also packaged as a vimball. If you have the \"gunzip\"\r\ndecompressor in your PATH, simply edit the *.vmb.gz package in Vim; otherwise,\r\ndecompress the archive first, e.g. using WinZip. Inside Vim, install by\r\nsourcing the vimball or via the :UseVimball command.\r\n    vim TaggedSearchPattern*.vmb.gz\r\n    :so %\r\nTo uninstall, use the :RmVimball command.\r\n\r\nDEPENDENCIES\r\n- Requires Vim 7.0 or higher.\r\n\r\nCONFIGURATION\r\nFor a permanent configuration, put the following commands into your vimrc:\r\n\r\nFor certain tag names, you can ensure that each tagged search pattern only\r\nexists once in the search history (previous patterns with the same tag are\r\ndeleted). By default, any tag name ending with a \"!\" is a unique one:\r\n    let g:TaggedSearchPattern_UniqueTagPattern = '.!$'\r\nTo make all tag searches unique, use this:\r\n    let g:TaggedSearchPattern_UniqueTagPattern = '.'\r\n\r\nTo turn off the highlighting of the tag name and search-neutral tag expression\r\nin the search cmdline-window:\r\n    let g:TaggedSearchPattern_HighlightTags = 0\r\n\r\nTo change the highlighting colors, redefine (after any :colorscheme command)\r\nor link the two highlight groups:\r\n    highlight link TaggedSearchTag Search\r\n    highlight TaggedSearchNeutral ctermfg=Black guifg=White\r\n\r\nIf you want to use different mappings, map your keys to the\r\n<Plug>(TaggedSearchPattern...) mapping targets _before_ sourcing the script\r\n(e.g. in your vimrc):\r\n    cmap <C-t> <Plug>(TaggedSearchPatternToggle)\r\n    cmap <C-g><C-t> <Plug>(TaggedSearchPatternUniqueToggle)\r\n    nmap q<C-t> <Plug>(TaggedSearchPatternList)","first_name":"Ingo","6":"Ingo","last_name":"Karkat","7":"Karkat","releases":[{"0":"4123","vim_version":"7.0","1":"7.0","script_version":"1.10","2":"1.10","version_comment":"- Make <C-t> mapping configurable.\r\n- ENH: Allow unique tags, identified via g:TaggedSearchPattern_UniqueTagPattern or forced via different mapping.\r\n- Add <C-g><C-t> variant that enforces unique tag.\r\n- Minor: Remove q<C-t> filter pattern from search history.","3":"- Make <C-t> mapping configurable.\r\n- ENH: Allow unique tags, identified via g:TaggedSearchPattern_UniqueTagPattern or forced via different mapping.\r\n- Add <C-g><C-t> variant that enforces unique tag.\r\n- Minor: Remove q<C-t> filter pattern from search history.","package":"TaggedSearchPattern-1.10.vmb.gz","4":"TaggedSearchPattern-1.10.vmb.gz","src_id":"26277","5":"26277","creation_date":"1542575783","6":"1542575783"},{"0":"4123","vim_version":"7.0","1":"7.0","script_version":"1.00","2":"1.00","version_comment":"Initial upload","3":"Initial upload","package":"TaggedSearchPattern.vba.gz","4":"TaggedSearchPattern.vba.gz","src_id":"18237","5":"18237","creation_date":"1341821723","6":"1341821723"}]},"4122":{"script_id":"4122","0":"4122","script_name":"ptsc-header","1":"ptsc-header","script_type":"utility","2":"utility","summary":"Header parser for the Plain Text\/Source Code File Header","3":"Header parser for the Plain Text\/Source Code File Header","description":"Repository: http:\/\/darcsden.com\/karl\/vim-ptsc-header\r\nThat repo will always have the last version. Try to use it instead.\r\n\r\nThis plugin implements the Internet Draft about Plain Text\/Source Code File Header as defined in http:\/\/tools.ietf.org\/html\/draft-swindell-ptsc-hdr-01. It's similar to Vim's modelines, but adapting them to the Internet Draft. It's intended to define what kind of indentation is used in the file. They are even more readable than Vim's modelines! But overall, they're a (not-yet-implemented) standard that doesn't depend on a concrete editor, unlike Vim's.","4":"Repository: http:\/\/darcsden.com\/karl\/vim-ptsc-header\r\nThat repo will always have the last version. Try to use it instead.\r\n\r\nThis plugin implements the Internet Draft about Plain Text\/Source Code File Header as defined in http:\/\/tools.ietf.org\/html\/draft-swindell-ptsc-hdr-01. It's similar to Vim's modelines, but adapting them to the Internet Draft. It's intended to define what kind of indentation is used in the file. They are even more readable than Vim's modelines! But overall, they're a (not-yet-implemented) standard that doesn't depend on a concrete editor, unlike Vim's.","install_details":"Put the file inside \r\n1. \"~\/.vim\/plugin\" or\r\n2. \"\/usr\/share\/vim\/vim73\/plugin\"\r\nor get it from the repo:\r\ncd ~\/.vim\/bundle && darcs get http:\/\/darcsden.com\/karl\/vim-ptsc-header --lazy","5":"Put the file inside \r\n1. \"~\/.vim\/plugin\" or\r\n2. \"\/usr\/share\/vim\/vim73\/plugin\"\r\nor get it from the repo:\r\ncd ~\/.vim\/bundle && darcs get http:\/\/darcsden.com\/karl\/vim-ptsc-header --lazy","first_name":"Carlos","6":"Carlos","last_name":"Ruiz-Henestrosa","7":"Ruiz-Henestrosa","releases":[{"0":"4122","vim_version":"7.0","1":"7.0","script_version":"2012W27","2":"2012W27","version_comment":"Initial upload","3":"Initial upload","package":"ptsc-header.vim","4":"ptsc-header.vim","src_id":"18234","5":"18234","creation_date":"1341701319","6":"1341701319"}]},"4121":{"script_id":"4121","0":"4121","script_name":"kickAssembler syntax","1":"kickAssembler syntax","script_type":"syntax","2":"syntax","summary":"Kick Assembler syntax file","3":"Kick Assembler syntax file","description":"The Kick Assembler (http:\/\/www.theweb.dk\/KickAssembler\/) syntax file.\r\n\r\nSyntax file is hosted on https:\/\/bitbucket.org\/gryf\/kickass-syntax-vim, and mirrored on https:\/\/github.com\/gryf\/kickass-syntax-vim.","4":"The Kick Assembler (http:\/\/www.theweb.dk\/KickAssembler\/) syntax file.\r\n\r\nSyntax file is hosted on https:\/\/bitbucket.org\/gryf\/kickass-syntax-vim, and mirrored on https:\/\/github.com\/gryf\/kickass-syntax-vim.","install_details":"To install this file place it in ~\/.vim\/syntax (*nix\/Mac) or in $VIMRUNTIME\/syntax on Windows or just use NeoBundle, Pathogen or Vundle, and than issue command:\r\n\r\n:set filetype=kickass\r\n\r\nYou can also add to your vimrc file autocommand:\r\n\r\nautocmd BufRead *.asm set filetype=kickass\r\n\r\nFrom now on, all files with extension 'asm' will have brand new kickass syntax.","5":"To install this file place it in ~\/.vim\/syntax (*nix\/Mac) or in $VIMRUNTIME\/syntax on Windows or just use NeoBundle, Pathogen or Vundle, and than issue command:\r\n\r\n:set filetype=kickass\r\n\r\nYou can also add to your vimrc file autocommand:\r\n\r\nautocmd BufRead *.asm set filetype=kickass\r\n\r\nFrom now on, all files with extension 'asm' will have brand new kickass syntax.","first_name":"Roman","6":"Roman","last_name":"Dobosz","7":"Dobosz","releases":[{"0":"4121","vim_version":"7.0","1":"7.0","script_version":"1.3","2":"1.3","version_comment":"Updated to KickAssembler 3.36 changes","3":"Updated to KickAssembler 3.36 changes","package":"kickass.vim","4":"kickass.vim","src_id":"22320","5":"22320","creation_date":"1407872456","6":"1407872456"},{"0":"4121","vim_version":"7.0","1":"7.0","script_version":"1.2","2":"1.2","version_comment":"Updated to KickAssembler 3.25 changes","3":"Updated to KickAssembler 3.25 changes","package":"kickass.vim","4":"kickass.vim","src_id":"18302","5":"18302","creation_date":"1342947728","6":"1342947728"},{"0":"4121","vim_version":"7.0","1":"7.0","script_version":"1.1","2":"1.1","version_comment":"Removed label highlight, turned on number highlight, small fixes","3":"Removed label highlight, turned on number highlight, small fixes","package":"kickass.vim","4":"kickass.vim","src_id":"18239","5":"18239","creation_date":"1341826683","6":"1341826683"},{"0":"4121","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"kickass.vim","4":"kickass.vim","src_id":"18222","5":"18222","creation_date":"1341515333","6":"1341515333"}]},"4120":{"script_id":"4120","0":"4120","script_name":"viske","1":"viske","script_type":"utility","2":"utility","summary":"timeline calendar.","3":"timeline calendar.","description":"You can manage your daily schedule on vim with timeline calendar.\r\nDetailed descriptions are available on below website.\r\n\r\n(English)\r\nhttp:\/\/vimyum.blogspot.com\/2012\/06\/vim-scheduler-viske.html\r\n(Japanese)\r\nhttp:\/\/vimyum.blogspot.com\/2012\/06\/vim-viske.html\r\n\r\n(Latest versions)\r\nhttps:\/\/github.com\/vimyum\/viske","4":"You can manage your daily schedule on vim with timeline calendar.\r\nDetailed descriptions are available on below website.\r\n\r\n(English)\r\nhttp:\/\/vimyum.blogspot.com\/2012\/06\/vim-scheduler-viske.html\r\n(Japanese)\r\nhttp:\/\/vimyum.blogspot.com\/2012\/06\/vim-viske.html\r\n\r\n(Latest versions)\r\nhttps:\/\/github.com\/vimyum\/viske","install_details":"","5":"","first_name":"takahiro","6":"takahiro","last_name":"sagara","7":"sagara","releases":[{"0":"4120","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"change default language (English)","3":"change default language (English)","package":"viske.tar.gz","4":"viske.tar.gz","src_id":"18212","5":"18212","creation_date":"1341235527","6":"1341235527"}]},"4119":{"script_id":"4119","0":"4119","script_name":"vktheming","1":"vktheming","script_type":"utility","2":"utility","summary":"Make your vimwiki colorful","3":"Make your vimwiki colorful","description":"Introduction:\r\nSet colors for vimwiki_html from your current vim color scheme setting.\r\n\r\nUsage:\r\nOpen vimwiki index page (VimwikiIndex) and excute command 'VKtheming'.\r\nRecommend you excute this command in 'vim-gui'.","4":"Introduction:\r\nSet colors for vimwiki_html from your current vim color scheme setting.\r\n\r\nUsage:\r\nOpen vimwiki index page (VimwikiIndex) and excute command 'VKtheming'.\r\nRecommend you excute this command in 'vim-gui'.","install_details":"Unzip all files into your vim runtime directory","5":"Unzip all files into your vim runtime directory","first_name":"kai","6":"kai","last_name":"yang","7":"yang","releases":[{"0":"4119","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"vktheming-0.1.zip","4":"vktheming-0.1.zip","src_id":"18206","5":"18206","creation_date":"1341153956","6":"1341153956"}]},"4118":{"script_id":"4118","0":"4118","script_name":"vim-signature","1":"vim-signature","script_type":"utility","2":"utility","summary":"Plugin to toggle, display and navigate marks and signs","3":"Plugin to toggle, display and navigate marks and signs","description":"Note: The github mirror https:\/\/github.com\/kshenoy\/vim-signature will always contain the latest version\r\n\r\n\r\nvim-signature is a plugin to place, toggle and display marks.  \r\n  \r\nApart from the above, you can also  \r\n* Navigate forward\/backward by position\/alphabetical order  \r\n* Displaying multiple marks (upto 2, limited by the signs feature)  \r\n* Placing custom signs !@#$%^&*() as visual markers  \r\n\r\n\r\n### Screenshots  \r\nhttp:\/\/imgur.com\/a\/3KQyt\r\n  \r\n\r\n## Requirements  \r\nRequires Vim to be compiled with +signs to display marks.  \r\n\r\n\r\n## Installation\r\nI highly recommend using Pathogen or Vundler to do the grunt work for you.  \r\nIf for some reason, you do not want to use any of these excellent plugins,  \r\nthen unzip it to your ~\/.vim directory. You know how it goes...  \r\n\r\nOnce that's done, out of the box, the followings mappings are defined by default  \r\n\r\n````\r\n  m[a-zA-Z]    : Toggle mark\r\n  m<Space>     : Delete all marks\r\n  m,           : Place the next available mark\r\n  ]`           : Jump to next mark\r\n  [`           : Jump to prev mark\r\n  ]'           : Jump to start of next line containing a mark\r\n  ['           : Jump to start of prev line containing a mark\r\n  `]           : Jump by alphabetical order to next mark\r\n  `[           : Jump by alphabetical order to prev mark\r\n  ']           : Jump by alphabetical order to start of next line containing a mark\r\n  '[           : Jump by alphabetical order to start of prev line containing a mark\r\n\r\n  m[0-9]       : Toggle the corresponding marker !@#$%^&*()\r\n  m<S-[0-9]>   : Remove all markers of the same type\r\n  ]-           : Jump to next line having same marker\r\n  [-           : Jump to prev line having same marker\r\n  m<BackSpace> : Remove all markers\r\n````\r\n\r\nThis will allow the use of default behavior of m to set marks and, if the line already contains the mark, it'll be unset.\r\nThe default behavior of ]', [', `] and [` is supported and enhanced by wrapping around when beginning or end of file is reached.\r\n\r\nThe command `:SignatureToggle` can be used to show\/hide the signs. This is a buffer-specific command.\r\nNote that this does not delete any of the marks but only hides them.\r\n\r\nIf for some reason, the marks and their sign displays go out of sync, use `:SignatureRefresh` to refresh them.\r\n\r\nFor more details on customization refer the help\r\n\r\n\r\n## Thanks to...\r\n* Sergey Khorev for [mark-tools](http:\/\/www.vim.org\/scripts\/script.php?script_id=2929)\r\n* Zak Johnson for [vim-showmarks](https:\/\/github.com\/zakj\/vim-showmarks)\r\n\r\n\r\n## ToDo:\r\n* Add support for non-Alphabetical marks\r\n* Tie the Signature functions to vim commands that affect mark placement","4":"Note: The github mirror https:\/\/github.com\/kshenoy\/vim-signature will always contain the latest version\r\n\r\n\r\nvim-signature is a plugin to place, toggle and display marks.  \r\n  \r\nApart from the above, you can also  \r\n* Navigate forward\/backward by position\/alphabetical order  \r\n* Displaying multiple marks (upto 2, limited by the signs feature)  \r\n* Placing custom signs !@#$%^&*() as visual markers  \r\n\r\n\r\n### Screenshots  \r\nhttp:\/\/imgur.com\/a\/3KQyt\r\n  \r\n\r\n## Requirements  \r\nRequires Vim to be compiled with +signs to display marks.  \r\n\r\n\r\n## Installation\r\nI highly recommend using Pathogen or Vundler to do the grunt work for you.  \r\nIf for some reason, you do not want to use any of these excellent plugins,  \r\nthen unzip it to your ~\/.vim directory. You know how it goes...  \r\n\r\nOnce that's done, out of the box, the followings mappings are defined by default  \r\n\r\n````\r\n  m[a-zA-Z]    : Toggle mark\r\n  m<Space>     : Delete all marks\r\n  m,           : Place the next available mark\r\n  ]`           : Jump to next mark\r\n  [`           : Jump to prev mark\r\n  ]'           : Jump to start of next line containing a mark\r\n  ['           : Jump to start of prev line containing a mark\r\n  `]           : Jump by alphabetical order to next mark\r\n  `[           : Jump by alphabetical order to prev mark\r\n  ']           : Jump by alphabetical order to start of next line containing a mark\r\n  '[           : Jump by alphabetical order to start of prev line containing a mark\r\n\r\n  m[0-9]       : Toggle the corresponding marker !@#$%^&*()\r\n  m<S-[0-9]>   : Remove all markers of the same type\r\n  ]-           : Jump to next line having same marker\r\n  [-           : Jump to prev line having same marker\r\n  m<BackSpace> : Remove all markers\r\n````\r\n\r\nThis will allow the use of default behavior of m to set marks and, if the line already contains the mark, it'll be unset.\r\nThe default behavior of ]', [', `] and [` is supported and enhanced by wrapping around when beginning or end of file is reached.\r\n\r\nThe command `:SignatureToggle` can be used to show\/hide the signs. This is a buffer-specific command.\r\nNote that this does not delete any of the marks but only hides them.\r\n\r\nIf for some reason, the marks and their sign displays go out of sync, use `:SignatureRefresh` to refresh them.\r\n\r\nFor more details on customization refer the help\r\n\r\n\r\n## Thanks to...\r\n* Sergey Khorev for [mark-tools](http:\/\/www.vim.org\/scripts\/script.php?script_id=2929)\r\n* Zak Johnson for [vim-showmarks](https:\/\/github.com\/zakj\/vim-showmarks)\r\n\r\n\r\n## ToDo:\r\n* Add support for non-Alphabetical marks\r\n* Tie the Signature functions to vim commands that affect mark placement","install_details":"For those of you -\r\n* Pathogen: Unzip contents of the zip file to .vim\/bundle folder\r\n* Vundle\/NeoBundle: Add 'Bundle \"kshenoy\/vim-signature\" ' to .vimrc\r\n\r\nI highly recommend using a plugin manager to do the dirty work for you. \r\nIf you still insist on not using one, unzip the contents of the vim-signature folder to your .vim folder.","5":"For those of you -\r\n* Pathogen: Unzip contents of the zip file to .vim\/bundle folder\r\n* Vundle\/NeoBundle: Add 'Bundle \"kshenoy\/vim-signature\" ' to .vimrc\r\n\r\nI highly recommend using a plugin manager to do the dirty work for you. \r\nIf you still insist on not using one, unzip the contents of the vim-signature folder to your .vim folder.","first_name":"Kartik","6":"Kartik","last_name":"Shenoy","7":"Shenoy","releases":[{"0":"4118","vim_version":"7.0","1":"7.0","script_version":"2.0","2":"2.0","version_comment":"Changed the way the plugin handles mappings. \r\nFull changelist is here https:\/\/github.com\/kshenoy\/vim-signature\/commit\/0117f59f8cfb633baa3058ba77cdc31c315de911","3":"Changed the way the plugin handles mappings. \r\nFull changelist is here https:\/\/github.com\/kshenoy\/vim-signature\/commit\/0117f59f8cfb633baa3058ba77cdc31c315de911","package":"vim-signature.zip","4":"vim-signature.zip","src_id":"21237","5":"21237","creation_date":"1388020668","6":"1388020668"}]},"4117":{"script_id":"4117","0":"4117","script_name":"VcsMessageRecall","1":"VcsMessageRecall","script_type":"utility","2":"utility","summary":"Browse and re-insert previous VCS commit messages.","3":"Browse and re-insert previous VCS commit messages.","description":"DESCRIPTION\r\nThis plugin automatically persists commit messages from Git, Mercurial,\r\nSubversion (and potentially other version control systems) when Vim is invoked\r\nas the commit message editor. It sets up mappings and commands to iterate\r\nthrough stored past messages, and recall the contents (without the boilerplate\r\ntext at the bottom of each message) for use in the currently edited message.\r\nThis way, you automatically collect a history of (committed or aborted) past\r\nmessages, and can quickly base your current message on contents recalled from\r\nthat history.\r\n\r\nRELATED WORKS\r\n- svn_commit (vimscript #1451) will look in the current directory for aborted\r\n  subversion commit log messages, and then read in the newest one to your\r\n  current commit log.\r\n- vim-git-msg-wheel (vimscript #5750) shows a completion menu with the last\r\n  Git commit messages (titles only), by querying Git's log.\r\n\r\nUSAGE\r\nSee MessageRecall-message-usage for the available mappings and commands.\r\n\r\nThe commit messages are stored separately for each repository, no matter from\r\nwhich subdirectory of the repository you're committing. The location of the\r\nmessage store is\r\n    {.git,.hg,.svn}\/commit-msgs\/\r\nAs repositories typically contain totally different projects, it's unlikely\r\nthat you need to recall messages from a different repository, but if you need\r\nto, you can still pass that path to the :MessageRecall command, or even\r\nreconfigure the plugin to use a single, global message store.\r\n\r\nEXAMPLE\r\nYou commit a set of changes via \"git commit\". Vim is invoked on the\r\n.git\/COMMIT_EDITMSG file, which so far just shows the boilerplate comments at\r\nthe bottom of the file.\r\nYou press CTRL-P to recall the previous commit message, because this commit is\r\nrelated to it, and you want to re-use parts of its description. The previous\r\ncommit message is inserted above the boilerplate.\r\nWas it that message? You browse through some more via CTRL-P and CTRL-N, then\r\nstart editing. Oh, there also was some useful information in the third last\r\ncommit. A 3_CTRL-P opens that message in the preview window (because your\r\ncurrent message is now modified, and therefore won't be replaced).\r\nFrom there, you yank and paste the sentence into your current commit message.\r\nYou could have also incorporated the entire message via :3MessageRecall,\r\neither from the preview window, or directly inside the current message.\r\n\r\nFinally, you finish your message. But DUH! you actually forgot to fix\r\nsomething. You bail out via :cquit!, and Git aborts the commit. Nothing is\r\nlost, though. On the next try, a simple CTRL-P or :MessageRecall will retrieve\r\nyour carefully crafted text.","4":"DESCRIPTION\r\nThis plugin automatically persists commit messages from Git, Mercurial,\r\nSubversion (and potentially other version control systems) when Vim is invoked\r\nas the commit message editor. It sets up mappings and commands to iterate\r\nthrough stored past messages, and recall the contents (without the boilerplate\r\ntext at the bottom of each message) for use in the currently edited message.\r\nThis way, you automatically collect a history of (committed or aborted) past\r\nmessages, and can quickly base your current message on contents recalled from\r\nthat history.\r\n\r\nRELATED WORKS\r\n- svn_commit (vimscript #1451) will look in the current directory for aborted\r\n  subversion commit log messages, and then read in the newest one to your\r\n  current commit log.\r\n- vim-git-msg-wheel (vimscript #5750) shows a completion menu with the last\r\n  Git commit messages (titles only), by querying Git's log.\r\n\r\nUSAGE\r\nSee MessageRecall-message-usage for the available mappings and commands.\r\n\r\nThe commit messages are stored separately for each repository, no matter from\r\nwhich subdirectory of the repository you're committing. The location of the\r\nmessage store is\r\n    {.git,.hg,.svn}\/commit-msgs\/\r\nAs repositories typically contain totally different projects, it's unlikely\r\nthat you need to recall messages from a different repository, but if you need\r\nto, you can still pass that path to the :MessageRecall command, or even\r\nreconfigure the plugin to use a single, global message store.\r\n\r\nEXAMPLE\r\nYou commit a set of changes via \"git commit\". Vim is invoked on the\r\n.git\/COMMIT_EDITMSG file, which so far just shows the boilerplate comments at\r\nthe bottom of the file.\r\nYou press CTRL-P to recall the previous commit message, because this commit is\r\nrelated to it, and you want to re-use parts of its description. The previous\r\ncommit message is inserted above the boilerplate.\r\nWas it that message? You browse through some more via CTRL-P and CTRL-N, then\r\nstart editing. Oh, there also was some useful information in the third last\r\ncommit. A 3_CTRL-P opens that message in the preview window (because your\r\ncurrent message is now modified, and therefore won't be replaced).\r\nFrom there, you yank and paste the sentence into your current commit message.\r\nYou could have also incorporated the entire message via :3MessageRecall,\r\neither from the preview window, or directly inside the current message.\r\n\r\nFinally, you finish your message. But DUH! you actually forgot to fix\r\nsomething. You bail out via :cquit!, and Git aborts the commit. Nothing is\r\nlost, though. On the next try, a simple CTRL-P or :MessageRecall will retrieve\r\nyour carefully crafted text.","install_details":"INSTALLATION\r\nThe code is hosted in a Git repo at\r\n    https:\/\/github.com\/inkarkat\/vim-VcsMessageRecall\r\nYou can use your favorite plugin manager, or \"git clone\" into a directory used\r\nfor Vim packages. Releases are on the \"stable\" branch, the latest unstable\r\ndevelopment snapshot on \"master\".\r\n\r\nThis script is also packaged as a vimball. If you have the \"gunzip\"\r\ndecompressor in your PATH, simply edit the *.vmb.gz package in Vim; otherwise,\r\ndecompress the archive first, e.g. using WinZip. Inside Vim, install by\r\nsourcing the vimball or via the :UseVimball command.\r\n    vim VcsMessageRecall*.vmb.gz\r\n    :so %\r\nTo uninstall, use the :RmVimball command.\r\n\r\nDEPENDENCIES\r\n- Requires Vim 7.0 or higher.\r\n- Requires the ingo-library.vim plugin (vimscript #4433), version 1.038 or\r\n  higher.\r\n- Requires the EditSimilar plugin (vimscript #2544), version 2.00 or higher.\r\n- Requires the BufferPersist plugin (vimscript #4115).\r\n- Requires the MessageRecall plugin (vimscript #4116).\r\n\r\nCONFIGURATION\r\nYou can override the autocmds after the plugin has been sourced, e.g. in a\r\nfile .vim\/after\/plugin\/VcsMessageRecall.vim\r\nFor example, to use a single, global message store for all Subversion commits:\r\n    autocmd! VcsMessageRecall FileType svn,svn.*\r\n    \\   call VcsMessageRecall#Setup(\r\n    \\       $HOME . '\/.svn-commit-msgs',\r\n    \\       '--This line, and those below, will be ignored--'\r\n    \\   )\r\n\r\nIf you use a localized version of the VCS utilities, you have to adapt the\r\npatterns for the boilerplate detection.","5":"INSTALLATION\r\nThe code is hosted in a Git repo at\r\n    https:\/\/github.com\/inkarkat\/vim-VcsMessageRecall\r\nYou can use your favorite plugin manager, or \"git clone\" into a directory used\r\nfor Vim packages. Releases are on the \"stable\" branch, the latest unstable\r\ndevelopment snapshot on \"master\".\r\n\r\nThis script is also packaged as a vimball. If you have the \"gunzip\"\r\ndecompressor in your PATH, simply edit the *.vmb.gz package in Vim; otherwise,\r\ndecompress the archive first, e.g. using WinZip. Inside Vim, install by\r\nsourcing the vimball or via the :UseVimball command.\r\n    vim VcsMessageRecall*.vmb.gz\r\n    :so %\r\nTo uninstall, use the :RmVimball command.\r\n\r\nDEPENDENCIES\r\n- Requires Vim 7.0 or higher.\r\n- Requires the ingo-library.vim plugin (vimscript #4433), version 1.038 or\r\n  higher.\r\n- Requires the EditSimilar plugin (vimscript #2544), version 2.00 or higher.\r\n- Requires the BufferPersist plugin (vimscript #4115).\r\n- Requires the MessageRecall plugin (vimscript #4116).\r\n\r\nCONFIGURATION\r\nYou can override the autocmds after the plugin has been sourced, e.g. in a\r\nfile .vim\/after\/plugin\/VcsMessageRecall.vim\r\nFor example, to use a single, global message store for all Subversion commits:\r\n    autocmd! VcsMessageRecall FileType svn,svn.*\r\n    \\   call VcsMessageRecall#Setup(\r\n    \\       $HOME . '\/.svn-commit-msgs',\r\n    \\       '--This line, and those below, will be ignored--'\r\n    \\   )\r\n\r\nIf you use a localized version of the VCS utilities, you have to adapt the\r\npatterns for the boilerplate detection.","first_name":"Ingo","6":"Ingo","last_name":"Karkat","7":"Karkat","releases":[{"0":"4117","vim_version":"7.0","1":"7.0","script_version":"1.05","2":"1.05","version_comment":"- ENH: Message stores from working copies that are located next to the current one are configured (in |b:MessageRecall_ConfiguredMessageStores|) automatically for easy access via :MessageStore {dir}. *** You need to update to ingo-library (vimscript #4433) version 1.038! ***","3":"- ENH: Message stores from working copies that are located next to the current one are configured (in |b:MessageRecall_ConfiguredMessageStores|) automatically for easy access via :MessageStore {dir}. *** You need to update to ingo-library (vimscript #4433) version 1.038! ***","package":"VcsMessageRecall-1.05.vmb.gz","4":"VcsMessageRecall-1.05.vmb.gz","src_id":"27030","5":"27030","creation_date":"1582519830","6":"1582519830"},{"0":"4117","vim_version":"7.0","1":"7.0","script_version":"1.04","2":"1.04","version_comment":"- Factor out function to and use ingo-library.\r\n- Support Subversion 1.7 repository layout with only a single .svn directory inside the working copy root.\r\n- FIX: Make Mercurial root dir detection work when CWD is outside of the working copy. *** You need to separately install ingo-library (vimscript #4433) version 1.012 (or higher)! ***\r\n- FIX: On Cygwin and Mercurial, the system() calls have a trailing newline, which breaks the concatenation and leads to strange errors.","3":"- Factor out function to and use ingo-library.\r\n- Support Subversion 1.7 repository layout with only a single .svn directory inside the working copy root.\r\n- FIX: Make Mercurial root dir detection work when CWD is outside of the working copy. *** You need to separately install ingo-library (vimscript #4433) version 1.012 (or higher)! ***\r\n- FIX: On Cygwin and Mercurial, the system() calls have a trailing newline, which breaks the concatenation and leads to strange errors.","package":"VcsMessageRecall-1.04.vmb.gz","4":"VcsMessageRecall-1.04.vmb.gz","src_id":"22723","5":"22723","creation_date":"1419333805","6":"1419333805"},{"0":"4117","vim_version":"7.0","1":"7.0","script_version":"1.02","2":"1.02","version_comment":"- FIX: Typo in function name breaks Subversion support.\r\n- FIX: Avoid determining message store location when a stored message is edited.\r\n- Split off VcsMessageRecall#Setup() to consolidate the setup duplicated for each VCS and to introduce error handling. Exceptions should not reach the user, as this aborts the opening of the file. Rather, just print out the error and continue.\r\n- Revise range regexp again to also match an empty line above the boilerplate; this will be discarded by BufferPersist, anyway. We need a match in that case to properly replace a just-opened, otherwise empty commit message via CTRL-P or :MessageRecall.","3":"- FIX: Typo in function name breaks Subversion support.\r\n- FIX: Avoid determining message store location when a stored message is edited.\r\n- Split off VcsMessageRecall#Setup() to consolidate the setup duplicated for each VCS and to introduce error handling. Exceptions should not reach the user, as this aborts the opening of the file. Rather, just print out the error and continue.\r\n- Revise range regexp again to also match an empty line above the boilerplate; this will be discarded by BufferPersist, anyway. We need a match in that case to properly replace a just-opened, otherwise empty commit message via CTRL-P or :MessageRecall.","package":"VcsMessageRecall.vba.gz","4":"VcsMessageRecall.vba.gz","src_id":"18247","5":"18247","creation_date":"1342103051","6":"1342103051"},{"0":"4117","vim_version":"7.0","1":"7.0","script_version":"1.01","2":"1.01","version_comment":"Revise range regexp to avoid capturing an empty line before (more empty lines before) the boilerplate, and to avoid capturing the first line of the boilerplate when at line 1.","3":"Revise range regexp to avoid capturing an empty line before (more empty lines before) the boilerplate, and to avoid capturing the first line of the boilerplate when at line 1.","package":"VcsMessageRecall.vba.gz","4":"VcsMessageRecall.vba.gz","src_id":"18198","5":"18198","creation_date":"1340875227","6":"1340875227"},{"0":"4117","vim_version":"7.0","1":"7.0","script_version":"1.00","2":"1.00","version_comment":"Initial upload","3":"Initial upload","package":"VcsMessageRecall.vba.gz","4":"VcsMessageRecall.vba.gz","src_id":"18190","5":"18190","creation_date":"1340626172","6":"1340626172"}]},"4116":{"script_id":"4116","0":"4116","script_name":"MessageRecall","1":"MessageRecall","script_type":"utility","2":"utility","summary":"Browse and re-insert previous (commit, status) messages.","3":"Browse and re-insert previous (commit, status) messages.","description":"DESCRIPTION\r\nThis plugin automatically persists (parts of) buffers used for the editing of\r\ncommit (or other) messages, where Vim is invoked as the editor from an\r\nexternal tool. In these buffers, it sets up mappings and commands to iterate\r\nthrough stored past messages, and recall the contents for use in the currently\r\nedited message. This way, you automatically collect a history of (committed or\r\naborted) past messages, and can quickly base your current message on contents\r\nrecalled from that history.\r\n\r\nSEE ALSO\r\nThis plugin is used by:\r\n- VcsMessageRecall.vim (vimscript #4117):\r\n  Browse and re-insert previous VCS commit messages.\r\n\r\nRELATED WORKS\r\nUSAGE\r\nThe plugin is completely inactive until you set it up for a particular\r\nbuffer through the following function; you'll find the details directly in the\r\n.vim\/autoload\/MessageRecall.vim implementation file.\r\n\r\nMessageRecall#Setup( messageStoreDirspec, ... )\r\n\r\nINSIDE THE CURRENT MESSAGE BUFFER\r\nAfter setup, the following mappings and commands are available in the current\r\nmessage buffer:\r\n\r\nCTRL-P, CTRL-N          When the buffer has no unsaved changes: Replace the\r\n                        edited message with a [count]'th previous \/ next\r\n                        stored message.\r\n                        When the buffer is modified: Open the [count]'th\r\n                        previous \/ first stored message in the preview window.\r\n                        When the buffer is modified and a stored message is\r\n                        already being previewed: Open the [count]'th previous\r\n                        \/ next stored message there.\r\n\r\n:[count]MessageView\r\n                        View the [count]'th previous stored message in the\r\n                        preview-window.\r\n:MessageView {message}|{filespec}\r\n                        View {message} (auto-completed from the message store\r\n                        directory) or any arbitrary {filespec} contents\r\n                        in the preview-window.\r\n\r\n:[count]MessageRecall[!]\r\n                        Insert the [count]'th previous stored message below\r\n                        the current line.\r\n:MessageRecall[!] {message}|{filespec}\r\n                        Insert {message} (auto-completed from the message\r\n                        store directory) or any arbitrary {filespec} contents\r\n                        below the current line.\r\n\r\n                        When the existing message consists of just empty\r\n                        lines (originating from the message template that the\r\n                        tool invoking Vim has put there), the inserted message\r\n                        replaces those empty lines. With [!]: Replace an\r\n                        existing message with the inserted one.\r\n\r\nINSIDE A MESSAGE PREVIEW WINDOW\r\nCTRL-P, CTRL-N          Go to the previous \/ next stored message.\r\n\r\n:MessageRecall          Insert the previewed stored message below the current\r\n                        line in the buffer from which the message preview was\r\n                        opened.\r\n\r\nINSIDE BOTH\r\n:[N]MessageList         Show all \/ the last [N] messages in the\r\n                        location-list-window; most recent first. (So the\r\n                        line number directly corresponds to {count} in\r\n                        :{count}MessageRecall.)\r\n\r\n:[N]MessageGrep [arguments]\r\n                        Search for [arguments] in all \/ the last [N] stored\r\n                        messages, and set the location-list to the matches.\r\n\r\n:[N]MessageVimGrep [\/]{pattern}[\/]\r\n                        Search for {pattern} in all \/ the last [N] stored\r\n                        messages, and set the location-list to the matches.\r\n\r\n:MessageStore[!] {dirspec}| {identifier}|N\r\n                        Add the directory {dirspec} as a source (with [!]: set\r\n                        as the sole source) for recalled messages.\r\n                        If message stores have been preconfigured (cp.\r\n                        g:MessageRecall_ConfiguredMessageStores), these can\r\n                        be referenced via their short {identifier} instead, or\r\n                        by the N'th last accessed message store .\r\n:MessageStore           List all message store directories for the current\r\n                        buffer.\r\n\r\n:[N]MessagePrune[!]     Remove all \/ the oldest [N] messages from the message\r\n                        store, with [!] without confirmation.\r\n:MessagePrune[!] {fileglob}\r\n                        Remove all files matching {fileglob} from the message\r\n                        store, with [!] without confirmation.","4":"DESCRIPTION\r\nThis plugin automatically persists (parts of) buffers used for the editing of\r\ncommit (or other) messages, where Vim is invoked as the editor from an\r\nexternal tool. In these buffers, it sets up mappings and commands to iterate\r\nthrough stored past messages, and recall the contents for use in the currently\r\nedited message. This way, you automatically collect a history of (committed or\r\naborted) past messages, and can quickly base your current message on contents\r\nrecalled from that history.\r\n\r\nSEE ALSO\r\nThis plugin is used by:\r\n- VcsMessageRecall.vim (vimscript #4117):\r\n  Browse and re-insert previous VCS commit messages.\r\n\r\nRELATED WORKS\r\nUSAGE\r\nThe plugin is completely inactive until you set it up for a particular\r\nbuffer through the following function; you'll find the details directly in the\r\n.vim\/autoload\/MessageRecall.vim implementation file.\r\n\r\nMessageRecall#Setup( messageStoreDirspec, ... )\r\n\r\nINSIDE THE CURRENT MESSAGE BUFFER\r\nAfter setup, the following mappings and commands are available in the current\r\nmessage buffer:\r\n\r\nCTRL-P, CTRL-N          When the buffer has no unsaved changes: Replace the\r\n                        edited message with a [count]'th previous \/ next\r\n                        stored message.\r\n                        When the buffer is modified: Open the [count]'th\r\n                        previous \/ first stored message in the preview window.\r\n                        When the buffer is modified and a stored message is\r\n                        already being previewed: Open the [count]'th previous\r\n                        \/ next stored message there.\r\n\r\n:[count]MessageView\r\n                        View the [count]'th previous stored message in the\r\n                        preview-window.\r\n:MessageView {message}|{filespec}\r\n                        View {message} (auto-completed from the message store\r\n                        directory) or any arbitrary {filespec} contents\r\n                        in the preview-window.\r\n\r\n:[count]MessageRecall[!]\r\n                        Insert the [count]'th previous stored message below\r\n                        the current line.\r\n:MessageRecall[!] {message}|{filespec}\r\n                        Insert {message} (auto-completed from the message\r\n                        store directory) or any arbitrary {filespec} contents\r\n                        below the current line.\r\n\r\n                        When the existing message consists of just empty\r\n                        lines (originating from the message template that the\r\n                        tool invoking Vim has put there), the inserted message\r\n                        replaces those empty lines. With [!]: Replace an\r\n                        existing message with the inserted one.\r\n\r\nINSIDE A MESSAGE PREVIEW WINDOW\r\nCTRL-P, CTRL-N          Go to the previous \/ next stored message.\r\n\r\n:MessageRecall          Insert the previewed stored message below the current\r\n                        line in the buffer from which the message preview was\r\n                        opened.\r\n\r\nINSIDE BOTH\r\n:[N]MessageList         Show all \/ the last [N] messages in the\r\n                        location-list-window; most recent first. (So the\r\n                        line number directly corresponds to {count} in\r\n                        :{count}MessageRecall.)\r\n\r\n:[N]MessageGrep [arguments]\r\n                        Search for [arguments] in all \/ the last [N] stored\r\n                        messages, and set the location-list to the matches.\r\n\r\n:[N]MessageVimGrep [\/]{pattern}[\/]\r\n                        Search for {pattern} in all \/ the last [N] stored\r\n                        messages, and set the location-list to the matches.\r\n\r\n:MessageStore[!] {dirspec}| {identifier}|N\r\n                        Add the directory {dirspec} as a source (with [!]: set\r\n                        as the sole source) for recalled messages.\r\n                        If message stores have been preconfigured (cp.\r\n                        g:MessageRecall_ConfiguredMessageStores), these can\r\n                        be referenced via their short {identifier} instead, or\r\n                        by the N'th last accessed message store .\r\n:MessageStore           List all message store directories for the current\r\n                        buffer.\r\n\r\n:[N]MessagePrune[!]     Remove all \/ the oldest [N] messages from the message\r\n                        store, with [!] without confirmation.\r\n:MessagePrune[!] {fileglob}\r\n                        Remove all files matching {fileglob} from the message\r\n                        store, with [!] without confirmation.","install_details":"INSTALLATION\r\nThe code is hosted in a Git repo at\r\n    https:\/\/github.com\/inkarkat\/vim-MessageRecall\r\nYou can use your favorite plugin manager, or \"git clone\" into a directory used\r\nfor Vim packages. Releases are on the \"stable\" branch, the latest unstable\r\ndevelopment snapshot on \"master\".\r\n\r\nThis script is also packaged as a vimball. If you have the \"gunzip\"\r\ndecompressor in your PATH, simply edit the *.vmb.gz package in Vim; otherwise,\r\ndecompress the archive first, e.g. using WinZip. Inside Vim, install by\r\nsourcing the vimball or via the :UseVimball command.\r\n    vim MessageRecall*.vmb.gz\r\n    :so %\r\nTo uninstall, use the :RmVimball command.\r\n\r\nDEPENDENCIES\r\n- Requires Vim 7.0 or higher.\r\n- Requires the ingo-library.vim plugin (vimscript #4433), version 1.038 or\r\n  higher.\r\n- Requires the BufferPersist plugin (vimscript #4115).\r\n\r\nCONFIGURATION\r\nFor a permanent configuration, put the following commands into your vimrc:\r\n\r\nWhen you have multiple, related repositories, you may wish to recall messages\r\nfrom other message stores. Though this is possible via :MessageRecall\r\npath\/to\/other\/message-store, it is tedious, and you cannot browse \/ preview\r\nthem as easily as the ones from the current message store. For this, you can\r\ndefine additional message stores via:\r\n    let b:MessageRecall_MessageStores = ['', 'path\/to\/other\/message-store']\r\nThe empty string stands for the current message store; by omitting it, its\r\nmessages won't be offered any more. Note that this only affects recall and\r\npreview; the edited messages are still exclusively persisted to the current\r\nmessage store.\r\n\r\nIf you don't want to directly add more message stores, but enable the user to\r\nquickly do so, you can configure additional message stores together with short\r\nidentifying names:\r\n    let g:MessageRecall_ConfiguredMessageStores = {\r\n    \\   'repo1': '\/path\/to\/repo1\/.svn\/commit-msgs',\r\n    \\   'repo2': '\/path\/to\/repo2\/.git\/commit-msgs',\r\n    \\]\r\n\r\nIf you want to use different mappings, first disable the default key mappings\r\nin your vimrc:\r\n    map <Plug>DisableMessageRecallPreviewPrev <Plug>(MessageRecallPreviewPrev)\r\n    map <Plug>DisableMessageRecallPreviewNext <Plug>(MessageRecallPreviewNext)\r\n    map <Plug>DisableMessageRecallGoPrev      <Plug>(MessageRecallGoPrev)\r\n    map <Plug>DisableMessageRecallGoNext      <Plug>(MessageRecallGoNext)\r\nSince there's no common filetype for this plugin, User events are fired for\r\neach message buffer. You can hook into these events to define alternative\r\nmappings:\r\n    autocmd User MessageRecallBuffer  map <buffer> <Leader>P <Plug>(MessageRecallGoPrev)\r\n    autocmd User MessageRecallBuffer  map <buffer> <Leader>N <Plug>(MessageRecallGoNext)\r\n    autocmd User MessageRecallPreview map <buffer> <Leader>P <Plug>(MessageRecallPreviewPrev)\r\n    autocmd User MessageRecallPreview map <buffer> <Leader>N <Plug>(MessageRecallPreviewNext)","5":"INSTALLATION\r\nThe code is hosted in a Git repo at\r\n    https:\/\/github.com\/inkarkat\/vim-MessageRecall\r\nYou can use your favorite plugin manager, or \"git clone\" into a directory used\r\nfor Vim packages. Releases are on the \"stable\" branch, the latest unstable\r\ndevelopment snapshot on \"master\".\r\n\r\nThis script is also packaged as a vimball. If you have the \"gunzip\"\r\ndecompressor in your PATH, simply edit the *.vmb.gz package in Vim; otherwise,\r\ndecompress the archive first, e.g. using WinZip. Inside Vim, install by\r\nsourcing the vimball or via the :UseVimball command.\r\n    vim MessageRecall*.vmb.gz\r\n    :so %\r\nTo uninstall, use the :RmVimball command.\r\n\r\nDEPENDENCIES\r\n- Requires Vim 7.0 or higher.\r\n- Requires the ingo-library.vim plugin (vimscript #4433), version 1.038 or\r\n  higher.\r\n- Requires the BufferPersist plugin (vimscript #4115).\r\n\r\nCONFIGURATION\r\nFor a permanent configuration, put the following commands into your vimrc:\r\n\r\nWhen you have multiple, related repositories, you may wish to recall messages\r\nfrom other message stores. Though this is possible via :MessageRecall\r\npath\/to\/other\/message-store, it is tedious, and you cannot browse \/ preview\r\nthem as easily as the ones from the current message store. For this, you can\r\ndefine additional message stores via:\r\n    let b:MessageRecall_MessageStores = ['', 'path\/to\/other\/message-store']\r\nThe empty string stands for the current message store; by omitting it, its\r\nmessages won't be offered any more. Note that this only affects recall and\r\npreview; the edited messages are still exclusively persisted to the current\r\nmessage store.\r\n\r\nIf you don't want to directly add more message stores, but enable the user to\r\nquickly do so, you can configure additional message stores together with short\r\nidentifying names:\r\n    let g:MessageRecall_ConfiguredMessageStores = {\r\n    \\   'repo1': '\/path\/to\/repo1\/.svn\/commit-msgs',\r\n    \\   'repo2': '\/path\/to\/repo2\/.git\/commit-msgs',\r\n    \\]\r\n\r\nIf you want to use different mappings, first disable the default key mappings\r\nin your vimrc:\r\n    map <Plug>DisableMessageRecallPreviewPrev <Plug>(MessageRecallPreviewPrev)\r\n    map <Plug>DisableMessageRecallPreviewNext <Plug>(MessageRecallPreviewNext)\r\n    map <Plug>DisableMessageRecallGoPrev      <Plug>(MessageRecallGoPrev)\r\n    map <Plug>DisableMessageRecallGoNext      <Plug>(MessageRecallGoNext)\r\nSince there's no common filetype for this plugin, User events are fired for\r\neach message buffer. You can hook into these events to define alternative\r\nmappings:\r\n    autocmd User MessageRecallBuffer  map <buffer> <Leader>P <Plug>(MessageRecallGoPrev)\r\n    autocmd User MessageRecallBuffer  map <buffer> <Leader>N <Plug>(MessageRecallGoNext)\r\n    autocmd User MessageRecallPreview map <buffer> <Leader>P <Plug>(MessageRecallPreviewPrev)\r\n    autocmd User MessageRecallPreview map <buffer> <Leader>N <Plug>(MessageRecallPreviewNext)","first_name":"Ingo","6":"Ingo","last_name":"Karkat","7":"Karkat","releases":[{"0":"4116","vim_version":"7.0","1":"7.0","script_version":"1.30","2":"1.30","version_comment":"- ENH: Sort the :MessageStore completion candidates for configured message stores by last modification time (instead of alphabetically by identifier), so stores that were recently updated come first.\r\n- ENH: Allow :MessageStore referencing via N count of configured stores, too.","3":"- ENH: Sort the :MessageStore completion candidates for configured message stores by last modification time (instead of alphabetically by identifier), so stores that were recently updated come first.\r\n- ENH: Allow :MessageStore referencing via N count of configured stores, too.","package":"MessageRecall-1.30.vmb.gz","4":"MessageRecall-1.30.vmb.gz","src_id":"27031","5":"27031","creation_date":"1582520314","6":"1582520314"},{"0":"4116","vim_version":"7.0","1":"7.0","script_version":"1.20","2":"1.20","version_comment":"- ENH: Add :MessageList, :MessageGrep, and :MessageVimGrep commands.\r\n- ENH: Add :MessagePrune.\r\n- Refactoring. *** You need to update to ingo-library (vimscript #4433) version 1.023! ***","3":"- ENH: Add :MessageList, :MessageGrep, and :MessageVimGrep commands.\r\n- ENH: Add :MessagePrune.\r\n- Refactoring. *** You need to update to ingo-library (vimscript #4433) version 1.023! ***","package":"MessageRecall-1.20.vmb.gz","4":"MessageRecall-1.20.vmb.gz","src_id":"26279","5":"26279","creation_date":"1542577365","6":"1542577365"},{"0":"4116","vim_version":"7.0","1":"7.0","script_version":"1.10","2":"1.10","version_comment":"- ENH: For :MessageRecall command completion, return the messages from other message stores also in reverse order, so that the latest one comes first.\r\n- ENH: Allow to override \/ extend the message store(s) via b:MessageRecall_MessageStores configuration.\r\n- Get rid of the dependency to the EditSimilar.vim plugin.\r\n- ENH: Add :MessageStore command that allows to add \/ replace message stores. Presets can be configured via the new b:MessageRecall_ConfiguredMessageStores variable.\r\n- Use ingo#compat#glob() and ingo#compat#globpath(). *** You need to update to ingo-library (vimscript #4433) version 1.022! *** The dependency to the EditSimilar.vim plugin has been dropped.","3":"- ENH: For :MessageRecall command completion, return the messages from other message stores also in reverse order, so that the latest one comes first.\r\n- ENH: Allow to override \/ extend the message store(s) via b:MessageRecall_MessageStores configuration.\r\n- Get rid of the dependency to the EditSimilar.vim plugin.\r\n- ENH: Add :MessageStore command that allows to add \/ replace message stores. Presets can be configured via the new b:MessageRecall_ConfiguredMessageStores variable.\r\n- Use ingo#compat#glob() and ingo#compat#globpath(). *** You need to update to ingo-library (vimscript #4433) version 1.022! *** The dependency to the EditSimilar.vim plugin has been dropped.","package":"MessageRecall-1.10.vmb.gz","4":"MessageRecall-1.10.vmb.gz","src_id":"22720","5":"22720","creation_date":"1419333670","6":"1419333670"},{"0":"4116","vim_version":"7.0","1":"7.0","script_version":"1.03","2":"1.03","version_comment":"- Adapt to changed EditSimilar.vim interface that returns the success status now. Abort on error for own plugin commands. *** You need to update to EditSimilar.vim (vimscript #2544) version 2.40! ***","3":"- Adapt to changed EditSimilar.vim interface that returns the success status now. Abort on error for own plugin commands. *** You need to update to EditSimilar.vim (vimscript #2544) version 2.40! ***","package":"MessageRecall-1.03.vmb.gz","4":"MessageRecall-1.03.vmb.gz","src_id":"21784","5":"21784","creation_date":"1397651753","6":"1397651753"},{"0":"4116","vim_version":"7.0","1":"7.0","script_version":"1.02","2":"1.02","version_comment":"- CHG: Only replace on <C-p> \/ <C-n> in the message buffer when the considered range is just empty lines. I came to dislike the previous replacement also when the message had been persisted.\r\n- CHG: On <C-p> \/ <C-n> in the original message buffer: When the buffer is modified and a stored message is already being previewed, change the semantics of count to be interpreted relative to the currently previewed stored message. Beforehand, one had to use increasing <C-p>, 2<C-p>, 3<C-p>, etc. to iterate through stored messages (or go to the preview window and invoke the mapping there).\r\n- ENH: Allow to override the default <C-p> \/ <C-n> mappings.\r\n- Add dependency to ingo-library (vimscript #4433). *** You need to separately install ingo-library (vimscript #4433) version 1.012 (or higher)! ***","3":"- CHG: Only replace on <C-p> \/ <C-n> in the message buffer when the considered range is just empty lines. I came to dislike the previous replacement also when the message had been persisted.\r\n- CHG: On <C-p> \/ <C-n> in the original message buffer: When the buffer is modified and a stored message is already being previewed, change the semantics of count to be interpreted relative to the currently previewed stored message. Beforehand, one had to use increasing <C-p>, 2<C-p>, 3<C-p>, etc. to iterate through stored messages (or go to the preview window and invoke the mapping there).\r\n- ENH: Allow to override the default <C-p> \/ <C-n> mappings.\r\n- Add dependency to ingo-library (vimscript #4433). *** You need to separately install ingo-library (vimscript #4433) version 1.012 (or higher)! ***","package":"MessageRecall-1.02.vmb.gz","4":"MessageRecall-1.02.vmb.gz","src_id":"21082","5":"21082","creation_date":"1385039710","6":"1385039710"},{"0":"4116","vim_version":"7.0","1":"7.0","script_version":"1.01","2":"1.01","version_comment":"BUG: Script error E486 when replacing a non-matching commit message buffer.","3":"BUG: Script error E486 when replacing a non-matching commit message buffer.","package":"MessageRecall.vba.gz","4":"MessageRecall.vba.gz","src_id":"18246","5":"18246","creation_date":"1342102988","6":"1342102988"},{"0":"4116","vim_version":"7.0","1":"7.0","script_version":"1.00","2":"1.00","version_comment":"Initial upload","3":"Initial upload","package":"MessageRecall.vba.gz","4":"MessageRecall.vba.gz","src_id":"18189","5":"18189","creation_date":"1340625777","6":"1340625777"}]},"4115":{"script_id":"4115","0":"4115","script_name":"BufferPersist","1":"BufferPersist","script_type":"utility","2":"utility","summary":"Save certain buffers somewhere when quitting them.","3":"Save certain buffers somewhere when quitting them.","description":"DESCRIPTION\r\nThis plugin automatically persists (parts of) certain buffers when Vim is done\r\nediting the buffer, regardless of whether is was saved to a file or discarded.\r\nIn this way, this is related to the built-in persistent-undo functionality,\r\nbut rather meant for building a history of file contents to allow browsing and\r\nrecall, especially for things like commit messages, where Vim is invoked as\r\nthe editor from an external tool.\r\n\r\nSEE ALSO\r\nThis plugin is used by:\r\nMessageRecall (vimscript #4116): Browse and re-insert previous (commit,\r\n                                 status) messages.\r\n\r\nUSAGE\r\nThe plugin is completely inactive until you set it up for a particular\r\nbuffer through the following function; you'll find the details directly in the\r\n.vim\/autoload\/BufferPersist.vim implementation file.\r\n\r\nBufferPersist#Setup( BufferStoreFuncref, ... )\r\n\r\n\r\nEXAMPLE\r\nLet's store the first three lines of each edited text file in the temp\r\ndirectory, using the text file's filename prefixed with \"preview-\":\r\n    function! BufferStore( bufNr )\r\n        return $TEMP . '\/preview-' . fnamemodify(bufname(a:bufNr), ':t')\r\n    endfunction\r\n    autocmd BufNew,BufRead *.txt call BufferPersist#Setup(\r\n    \\   function('BufferStore'),\r\n    \\   {'range': '1,3'}\r\n    \\)","4":"DESCRIPTION\r\nThis plugin automatically persists (parts of) certain buffers when Vim is done\r\nediting the buffer, regardless of whether is was saved to a file or discarded.\r\nIn this way, this is related to the built-in persistent-undo functionality,\r\nbut rather meant for building a history of file contents to allow browsing and\r\nrecall, especially for things like commit messages, where Vim is invoked as\r\nthe editor from an external tool.\r\n\r\nSEE ALSO\r\nThis plugin is used by:\r\nMessageRecall (vimscript #4116): Browse and re-insert previous (commit,\r\n                                 status) messages.\r\n\r\nUSAGE\r\nThe plugin is completely inactive until you set it up for a particular\r\nbuffer through the following function; you'll find the details directly in the\r\n.vim\/autoload\/BufferPersist.vim implementation file.\r\n\r\nBufferPersist#Setup( BufferStoreFuncref, ... )\r\n\r\n\r\nEXAMPLE\r\nLet's store the first three lines of each edited text file in the temp\r\ndirectory, using the text file's filename prefixed with \"preview-\":\r\n    function! BufferStore( bufNr )\r\n        return $TEMP . '\/preview-' . fnamemodify(bufname(a:bufNr), ':t')\r\n    endfunction\r\n    autocmd BufNew,BufRead *.txt call BufferPersist#Setup(\r\n    \\   function('BufferStore'),\r\n    \\   {'range': '1,3'}\r\n    \\)","install_details":"INSTALLATION\r\nThis script is packaged as a vimball. If you have the \"gunzip\" decompressor\r\nin your PATH, simply edit the *.vba.gz package in Vim; otherwise, decompress\r\nthe archive first, e.g. using WinZip. Inside Vim, install by sourcing the\r\nvimball or via the :UseVimball command.\r\n    vim BufferPersist.vba.gz\r\n    :so %\r\nTo uninstall, use the :RmVimball command.\r\n\r\nDEPENDENCIES\r\n- Requires Vim 7.0 or higher.","5":"INSTALLATION\r\nThis script is packaged as a vimball. If you have the \"gunzip\" decompressor\r\nin your PATH, simply edit the *.vba.gz package in Vim; otherwise, decompress\r\nthe archive first, e.g. using WinZip. Inside Vim, install by sourcing the\r\nvimball or via the :UseVimball command.\r\n    vim BufferPersist.vba.gz\r\n    :so %\r\nTo uninstall, use the :RmVimball command.\r\n\r\nDEPENDENCIES\r\n- Requires Vim 7.0 or higher.","first_name":"Ingo","6":"Ingo","last_name":"Karkat","7":"Karkat","releases":[{"0":"4115","vim_version":"7.0","1":"7.0","script_version":"1.00","2":"1.00","version_comment":"Initial upload","3":"Initial upload","package":"BufferPersist.vba.gz","4":"BufferPersist.vba.gz","src_id":"18188","5":"18188","creation_date":"1340625567","6":"1340625567"}]},"4114":{"script_id":"4114","0":"4114","script_name":"LineMotion","1":"LineMotion","script_type":"patch","2":"patch","summary":"a Vim Plug-in, move fast in linei of text.","3":"a Vim Plug-in, move fast in linei of text.","description":"LineMotion provides a simpler and fast way to move in line of text.\r\n\r\nOnly two method of movement - Lright() and Lleft() in LineMotion. When the method is triggered first, the cursor will move right\/left to the middle ofthe line. And next it move a half of last distance of movement when triggered.\r\n\r\nBy default, there is no key binding. Because I konw that the default binding is suitable to my own taste, and the default binding may conflict with other plugins you may have installed. Of course, it's easy to set the key binding by which movement method is triggered, just put the following statement(ifmy taste is suitable for you) in your vimrc:\r\n\r\n nmap <leader>l :Lright<cr>\r\n nmap <leader>h :Lleft<cr>\r\n\r\nMake sure you already put the statements in your vimrc as above.\r\n\r\nType <leader>l to move the cursor to the middle of the line. If the target you wanna move to is right of the cursor, type <leader>l again. Otherwise, type <leader>h. It's easy to use, isn't it?\r\n\r\nThe project page of LineMotion is here: https:\/\/github.com\/handsomecheung\/vim-linemotion\r\nPlease report any issues here: https:\/\/github.com\/handsomecheung\/vim-linemotion\/issues","4":"LineMotion provides a simpler and fast way to move in line of text.\r\n\r\nOnly two method of movement - Lright() and Lleft() in LineMotion. When the method is triggered first, the cursor will move right\/left to the middle ofthe line. And next it move a half of last distance of movement when triggered.\r\n\r\nBy default, there is no key binding. Because I konw that the default binding is suitable to my own taste, and the default binding may conflict with other plugins you may have installed. Of course, it's easy to set the key binding by which movement method is triggered, just put the following statement(ifmy taste is suitable for you) in your vimrc:\r\n\r\n nmap <leader>l :Lright<cr>\r\n nmap <leader>h :Lleft<cr>\r\n\r\nMake sure you already put the statements in your vimrc as above.\r\n\r\nType <leader>l to move the cursor to the middle of the line. If the target you wanna move to is right of the cursor, type <leader>l again. Otherwise, type <leader>h. It's easy to use, isn't it?\r\n\r\nThe project page of LineMotion is here: https:\/\/github.com\/handsomecheung\/vim-linemotion\r\nPlease report any issues here: https:\/\/github.com\/handsomecheung\/vim-linemotion\/issues","install_details":"Decompress the tar ball you download, and put the linemotion.vim in ~\/.vim\/plugin\/ .\r\n\r\nBesides, LineMotion is compatible with pathogen!","5":"Decompress the tar ball you download, and put the linemotion.vim in ~\/.vim\/plugin\/ .\r\n\r\nBesides, LineMotion is compatible with pathogen!","first_name":"Handsome","6":"Handsome","last_name":"Cheung","7":"Cheung","releases":[{"0":"4114","vim_version":"7.0","1":"7.0","script_version":"0.0.1","2":"0.0.1","version_comment":"Initial upload","3":"Initial upload","package":"vim-linemotion.zip","4":"vim-linemotion.zip","src_id":"18186","5":"18186","creation_date":"1340589327","6":"1340589327"}]},"4113":{"script_id":"4113","0":"4113","script_name":"hickop","1":"hickop","script_type":"color scheme","2":"color scheme","summary":"simple dark colorscheme for vim and gvim","3":"simple dark colorscheme for vim and gvim","description":"This is an 'easy to the eyes' colorscheme with only essentials highlights.\r\nMade it so the colors are the same in vim and gvim without any trick.\r\n\r\nGithub repository with preview: \r\nhttps:\/\/github.com\/hickop\/vim-hickop-colors","4":"This is an 'easy to the eyes' colorscheme with only essentials highlights.\r\nMade it so the colors are the same in vim and gvim without any trick.\r\n\r\nGithub repository with preview: \r\nhttps:\/\/github.com\/hickop\/vim-hickop-colors","install_details":"copy in ~\/.vim\/colors\/ and :colorscheme hickop","5":"copy in ~\/.vim\/colors\/ and :colorscheme hickop","first_name":"hickop","6":"hickop","last_name":" ","7":" ","releases":[{"0":"4113","vim_version":"7.0","1":"7.0","script_version":"1.2","2":"1.2","version_comment":"Make ErrorMsg readable.","3":"Make ErrorMsg readable.","package":"hickop.vim","4":"hickop.vim","src_id":"18982","5":"18982","creation_date":"1353092308","6":"1353092308"},{"0":"4113","vim_version":"7.0","1":"7.0","script_version":"1.1","2":"1.1","version_comment":"Brighter red.","3":"Brighter red.","package":"hickop.vim","4":"hickop.vim","src_id":"18577","5":"18577","creation_date":"1347219734","6":"1347219734"},{"0":"4113","vim_version":"7.3","1":"7.3","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"hickop.vim","4":"hickop.vim","src_id":"18182","5":"18182","creation_date":"1340465901","6":"1340465901"}]},"4112":{"script_id":"4112","0":"4112","script_name":"riv.vim","1":"riv.vim","script_type":"utility","2":"utility","summary":"Take Notes in rst.","3":"Take Notes in rst.","description":"Intro\r\n=====\r\n\r\n**Riv** is a vim plugin for taking notes with reStructuredText_.\r\n\r\n.. figure:: https:\/\/github.com\/Rykka\/github_things\/raw\/master\/image\/rst_quick_start.gif \r\n\r\ngithub: https:\/\/github.com\/Rykka\/riv.vim\r\n\r\nComparion\r\n=========\r\n\r\nFirst things first.\r\n\r\nAs there are some other note plugins in vim. \r\nlike vimwiki_, vim-notes_,  VOoM_ etc.\r\n\r\nAlso org-mode_ if you are Emacs fan.\r\n\r\n**Why using this plugin?**\r\n\r\nIn comparition, the most advantage of **Riv.vim** is reStructuredText_ support. \r\n\r\n    reStructuredText is a markup language.\r\n\r\n    It's syntax are markdown_ alike, but more powerful and extensible, table, LaTex ect. are supported.\r\n\r\n    It's widely used in python community. And have many relevent plugins. Sphinx_ (www.readthedocs.org) Pygments_, Nikola_, etc.\r\n\r\n    There is a post of comparions between reStructuredText and markdown https:\/\/gist.github.com\/dupuy\/1855764\r\n\r\nSee More Intro on github: https:\/\/github.com\/Rykka\/riv.vim\r\n\r\n","4":"Intro\r\n=====\r\n\r\n**Riv** is a vim plugin for taking notes with reStructuredText_.\r\n\r\n.. figure:: https:\/\/github.com\/Rykka\/github_things\/raw\/master\/image\/rst_quick_start.gif \r\n\r\ngithub: https:\/\/github.com\/Rykka\/riv.vim\r\n\r\nComparion\r\n=========\r\n\r\nFirst things first.\r\n\r\nAs there are some other note plugins in vim. \r\nlike vimwiki_, vim-notes_,  VOoM_ etc.\r\n\r\nAlso org-mode_ if you are Emacs fan.\r\n\r\n**Why using this plugin?**\r\n\r\nIn comparition, the most advantage of **Riv.vim** is reStructuredText_ support. \r\n\r\n    reStructuredText is a markup language.\r\n\r\n    It's syntax are markdown_ alike, but more powerful and extensible, table, LaTex ect. are supported.\r\n\r\n    It's widely used in python community. And have many relevent plugins. Sphinx_ (www.readthedocs.org) Pygments_, Nikola_, etc.\r\n\r\n    There is a post of comparions between reStructuredText and markdown https:\/\/gist.github.com\/dupuy\/1855764\r\n\r\nSee More Intro on github: https:\/\/github.com\/Rykka\/riv.vim\r\n\r\n","install_details":"extract zip  to your vim dir \r\n\r\nor    \r\n\r\n  ``Bundle 'Rykka\/riv.vim'``\r\n","5":"extract zip  to your vim dir \r\n\r\nor    \r\n\r\n  ``Bundle 'Rykka\/riv.vim'``\r\n","first_name":"Rykka","6":"Rykka","last_name":"f","7":"f","releases":[{"0":"4112","vim_version":"7.0","1":"7.0","script_version":"0.7.8","2":"0.7.8","version_comment":"use clickable.vim for links.","3":"use clickable.vim for links.","package":"riv.vim-0.7.8.zip","4":"riv.vim-0.7.8.zip","src_id":"22575","5":"22575","creation_date":"1414427047","6":"1414427047"},{"0":"4112","vim_version":"7.0","1":"7.0","script_version":"0.7.7","2":"0.7.7","version_comment":"Lots of new features.\r\nSee https:\/\/github.com\/Rykka\/riv.vim\/blob\/master\/changelog.rst","3":"Lots of new features.\r\nSee https:\/\/github.com\/Rykka\/riv.vim\/blob\/master\/changelog.rst","package":"riv.vim-0.7.7.zip","4":"riv.vim-0.7.7.zip","src_id":"22372","5":"22372","creation_date":"1409183401","6":"1409183401"},{"0":"4112","vim_version":"7.0","1":"7.0","script_version":"0.76","2":"0.76","version_comment":"many bug fix and many features","3":"many bug fix and many features","package":"riv.vim-master.zip","4":"riv.vim-master.zip","src_id":"22296","5":"22296","creation_date":"1407358189","6":"1407358189"},{"0":"4112","vim_version":"7.0","1":"7.0","script_version":"0.73","2":"0.73","version_comment":"Rewrite command and menu. Add rst documents. Highlights improvement. Bug Fixed...\r\nSee details in https:\/\/github.com\/Rykka\/riv.vim\/blob\/master\/doc\/riv_log.rst ","3":"Rewrite command and menu. Add rst documents. Highlights improvement. Bug Fixed...\r\nSee details in https:\/\/github.com\/Rykka\/riv.vim\/blob\/master\/doc\/riv_log.rst ","package":"riv.vim-0.73.zip","4":"riv.vim-0.73.zip","src_id":"18838","5":"18838","creation_date":"1350637973","6":"1350637973"},{"0":"4112","vim_version":"7.0","1":"7.0","script_version":"0.71","2":"0.71","version_comment":"File: \tDONE 2012-09-13 extension style show in vim only.\r\nFile: \tDONE 2012-09-13 now square style (moinmoin) use [[xxx]]. easier for regxp match\r\n....\r\nSee details in https:\/\/github.com\/Rykka\/riv.vim#this","3":"File: \tDONE 2012-09-13 extension style show in vim only.\r\nFile: \tDONE 2012-09-13 now square style (moinmoin) use [[xxx]]. easier for regxp match\r\n....\r\nSee details in https:\/\/github.com\/Rykka\/riv.vim#this","package":"riv.vim-0.71.zip","4":"riv.vim-0.71.zip","src_id":"18638","5":"18638","creation_date":"1348048723","6":"1348048723"},{"0":"4112","vim_version":"7.0","1":"7.0","script_version":"0.70","2":"0.70","version_comment":"  :Table_:  DONE 2012-07-17 7b407b4b_ a table parser of vim version.\r\n  :Table_:  DONE 2012-07-17 7b407b4b_ rewrite the table actions. \r\n  :Table_:  DONE 2012-07-18 a1f112d1_ add create table action.\r\n  :Lists_:  FIXED 2012-07-19 fix list shifting with indent 0\r\n  :Helpers_: DONE 2012-07-19 add folding to section helper\r\n  :File_:   DONE 2012-07-21 improved link converting. add option\r\n","3":"  :Table_:  DONE 2012-07-17 7b407b4b_ a table parser of vim version.\r\n  :Table_:  DONE 2012-07-17 7b407b4b_ rewrite the table actions. \r\n  :Table_:  DONE 2012-07-18 a1f112d1_ add create table action.\r\n  :Lists_:  FIXED 2012-07-19 fix list shifting with indent 0\r\n  :Helpers_: DONE 2012-07-19 add folding to section helper\r\n  :File_:   DONE 2012-07-21 improved link converting. add option\r\n","package":"riv.vim-0.70.zip","4":"riv.vim-0.70.zip","src_id":"18294","5":"18294","creation_date":"1342806110","6":"1342806110"},{"0":"4112","vim_version":"7.0","1":"7.0","script_version":"0.69","2":"0.69","version_comment":"  :Indent_: DONE 2012-07-07 8b2c4611_ Rewrite the indent for list and insert.\r\n  :File_:   DONE 2012-07-07 dceab5c1_ Add File helper.\r\n  :Document: DONE 2012-07-08 69e5a86e_ commit links\r\n  :File_:   DONE 2012-07-08 a207e1e0_ Add Section helper.\r\n  :Intro_:  DONE 2012-07-09 add Riv quickstart\r\n  :Insert_: DONE 2012-07-13 rewrite and add options about ``i_tab``. \r\n","3":"  :Indent_: DONE 2012-07-07 8b2c4611_ Rewrite the indent for list and insert.\r\n  :File_:   DONE 2012-07-07 dceab5c1_ Add File helper.\r\n  :Document: DONE 2012-07-08 69e5a86e_ commit links\r\n  :File_:   DONE 2012-07-08 a207e1e0_ Add Section helper.\r\n  :Intro_:  DONE 2012-07-09 add Riv quickstart\r\n  :Insert_: DONE 2012-07-13 rewrite and add options about ``i_tab``. \r\n","package":"riv.vim-0.69.zip","4":"riv.vim-0.69.zip","src_id":"18255","5":"18255","creation_date":"1342190064","6":"1342190064"},{"0":"4112","vim_version":"7.0","1":"7.0","script_version":"0.68","2":"0.68","version_comment":"    :Patterns:  DONE 2012-07-07 a2334f7b_ Rewrite the pattern and syntax patterns part. \r\n    :Todos_:    DONE 2012-07-07 a2334f7b_ Rewrite todo and todo helper.Add Todo Priorities. \r\n    :Syntax_:   DONE 2012-07-07 a2334f7b_ Cursor highlight will highlight the todo item \r\n    :Syntax_:   DONE 2012-07-07 a2334f7b_ Cursor highlight will check it's valid file\r\n    :Lists_:    DONE 2012-07-07 0a959662_ Add list types 0 ~ 4 \r\n    :Todos_:    DONE 2012-07-07 142b6c49_ Add Prior in helpr\r\n","3":"    :Patterns:  DONE 2012-07-07 a2334f7b_ Rewrite the pattern and syntax patterns part. \r\n    :Todos_:    DONE 2012-07-07 a2334f7b_ Rewrite todo and todo helper.Add Todo Priorities. \r\n    :Syntax_:   DONE 2012-07-07 a2334f7b_ Cursor highlight will highlight the todo item \r\n    :Syntax_:   DONE 2012-07-07 a2334f7b_ Cursor highlight will check it's valid file\r\n    :Lists_:    DONE 2012-07-07 0a959662_ Add list types 0 ~ 4 \r\n    :Todos_:    DONE 2012-07-07 142b6c49_ Add Prior in helpr\r\n","package":"riv.vim-0.68.zip","4":"riv.vim-0.68.zip","src_id":"18231","5":"18231","creation_date":"1341637341","6":"1341637341"},{"0":"4112","vim_version":"7.0","1":"7.0","script_version":"0.66-1","2":"0.66-1","version_comment":"* DONE 2012-07-02 fix list: get_older get_parent \r\n","3":"* DONE 2012-07-02 fix list: get_older get_parent \r\n","package":"riv.vim-0.66-1.zip","4":"riv.vim-0.66-1.zip","src_id":"18209","5":"18209","creation_date":"1341178572","6":"1341178572"},{"0":"4112","vim_version":"7.0","1":"7.0","script_version":"0.66","2":"0.66","version_comment":"  :Todos_:   DONE 2012-06-29 add field list for todo items.\r\n  :Publish_: DONE 2012-06-29 Support the reStructuredText document not in a project.\r\n  :Insert_:  DONE 2012-06-29 9229651d_ ``<Tab>`` and ``<S-Tab>`` \r\n             before list item will now shift the list. \r\n  :Lists_:   DONE 2012-06-30 2b81464f_ bullet list will auto numbered when change to\r\n             enumerated list.\r\n  :Links_:   DONE 2012-06-30 69555b21_ Optimized link finding. Add email web link.\r\n  :Links_:   DONE 2012-06-30 69555b21_ Add anonymous phase target and reference \r\n             jumping and highlighting. \r\n  :Highlighting_:   DONE 2012-07-01 4dc853c1_ fix doctest highlighting\r\n  :Table_:   DONE 2012-07-01 38a8cebb_ Support simple table folding.\r\nAnd More...\r\n","3":"  :Todos_:   DONE 2012-06-29 add field list for todo items.\r\n  :Publish_: DONE 2012-06-29 Support the reStructuredText document not in a project.\r\n  :Insert_:  DONE 2012-06-29 9229651d_ ``<Tab>`` and ``<S-Tab>`` \r\n             before list item will now shift the list. \r\n  :Lists_:   DONE 2012-06-30 2b81464f_ bullet list will auto numbered when change to\r\n             enumerated list.\r\n  :Links_:   DONE 2012-06-30 69555b21_ Optimized link finding. Add email web link.\r\n  :Links_:   DONE 2012-06-30 69555b21_ Add anonymous phase target and reference \r\n             jumping and highlighting. \r\n  :Highlighting_:   DONE 2012-07-01 4dc853c1_ fix doctest highlighting\r\n  :Table_:   DONE 2012-07-01 38a8cebb_ Support simple table folding.\r\nAnd More...\r\n","package":"riv.vim-0.66.zip","4":"riv.vim-0.66.zip","src_id":"18207","5":"18207","creation_date":"1341165795","6":"1341165795"},{"0":"4112","vim_version":"7.0","1":"7.0","script_version":"0.65","2":"0.65","version_comment":"  + DONE 2012-06-27 take care of the slash of directory in windows .\r\n  + FIXED 2012-06-28 correct cursor position when creating todo items and list items.\r\n  + FIXED 2012-06-28 link highlight group removed after open another buffer.\r\n  + FIXED 2012-06-28 auto mkdir when write file to disk\r\n  + DONE 2012-06-28 format the scratch index, sort with year\/month\/day \r\n","3":"  + DONE 2012-06-27 take care of the slash of directory in windows .\r\n  + FIXED 2012-06-28 correct cursor position when creating todo items and list items.\r\n  + FIXED 2012-06-28 link highlight group removed after open another buffer.\r\n  + FIXED 2012-06-28 auto mkdir when write file to disk\r\n  + DONE 2012-06-28 format the scratch index, sort with year\/month\/day \r\n","package":"riv.vim-0.65.zip","4":"riv.vim-0.65.zip","src_id":"18200","5":"18200","creation_date":"1340884909","6":"1340884909"},{"0":"4112","vim_version":"7.0","1":"7.0","script_version":"0.64","2":"0.64","version_comment":"\r\n  + DONE 2012-06-23  README : rewrite intro\/feature part\r\n  + DONE 2012-06-24  Doc  : Help document from README.\r\n  + DONE 2012-06-24  Menu : add and fix.\r\n  + DONE 2012-06-24  A shortcut to add date and time.\r\n  + FIXED 2012-06-23 Fold : table should not show an empty line in folding of lists.\r\n    (nothing wrong, just indent it with the list.)\r\n  + DONE 2012-06-23  Fold : the fold text should showing correct line while editing.\r\n  + FIXED 2012-06-24 Fold : wrong end of section when fold_blank is 0.\r\n","3":"\r\n  + DONE 2012-06-23  README : rewrite intro\/feature part\r\n  + DONE 2012-06-24  Doc  : Help document from README.\r\n  + DONE 2012-06-24  Menu : add and fix.\r\n  + DONE 2012-06-24  A shortcut to add date and time.\r\n  + FIXED 2012-06-23 Fold : table should not show an empty line in folding of lists.\r\n    (nothing wrong, just indent it with the list.)\r\n  + DONE 2012-06-23  Fold : the fold text should showing correct line while editing.\r\n  + FIXED 2012-06-24 Fold : wrong end of section when fold_blank is 0.\r\n","package":"riv.vim-0.64.zip","4":"riv.vim-0.64.zip","src_id":"18183","5":"18183","creation_date":"1340479396","6":"1340479396"},{"0":"4112","vim_version":"7.0","1":"7.0","script_version":"0.63","2":"0.63","version_comment":"Initial upload","3":"Initial upload","package":"riv.vim-0.63.zip","4":"riv.vim-0.63.zip","src_id":"18179","5":"18179","creation_date":"1340396896","6":"1340396896"}]},"4111":{"script_id":"4111","0":"4111","script_name":"log4j.vim","1":"log4j.vim","script_type":"syntax","2":"syntax","summary":"Adds syntax highlighting for log4j and log4php log files","3":"Adds syntax highlighting for log4j and log4php log files","description":"Adds syntax highlighting for log4j and log4php log files. Initially created to solve log4php syntax highlighting.\r\n\r\nhttps:\/\/github.com\/tetsuo13\/Vim-log4j","4":"Adds syntax highlighting for log4j and log4php log files. Initially created to solve log4php syntax highlighting.\r\n\r\nhttps:\/\/github.com\/tetsuo13\/Vim-log4j","install_details":"Copy log4j.vim into your ~\/.vim\/syntax directory. Because there is no reliable method of detecting log files generated from log4j\/log4php, you can output log files have a .log extension and add the following to your ~\/.vimrc file to trigger the syntax highlighting:\r\n\r\nautocmd BufRead,BufNewFile *.log set syntax=log4j\r\n\r\nIf renaming log file extensions is not possible or desirable you can specify the exact name or pattern for the log files:\r\n\r\nautocmd BufRead,BufNewFile program_log set syntax=log4j","5":"Copy log4j.vim into your ~\/.vim\/syntax directory. Because there is no reliable method of detecting log files generated from log4j\/log4php, you can output log files have a .log extension and add the following to your ~\/.vimrc file to trigger the syntax highlighting:\r\n\r\nautocmd BufRead,BufNewFile *.log set syntax=log4j\r\n\r\nIf renaming log file extensions is not possible or desirable you can specify the exact name or pattern for the log files:\r\n\r\nautocmd BufRead,BufNewFile program_log set syntax=log4j","first_name":"Andrei","6":"Andrei","last_name":"Nicholson","7":"Nicholson","releases":[{"0":"4111","vim_version":"6.0","1":"6.0","script_version":"0.3","2":"0.3","version_comment":"Handle periods in logger name","3":"Handle periods in logger name","package":"tetsuo13-Vim-log4j-0.3-0-g0e0654d.zip","4":"tetsuo13-Vim-log4j-0.3-0-g0e0654d.zip","src_id":"18230","5":"18230","creation_date":"1341628596","6":"1341628596"},{"0":"4111","vim_version":"6.0","1":"6.0","script_version":"0.2","2":"0.2","version_comment":"Logger names can contain things other than letters","3":"Logger names can contain things other than letters","package":"tetsuo13-Vim-log4j-0.2-0-g97df89f.zip","4":"tetsuo13-Vim-log4j-0.2-0-g97df89f.zip","src_id":"18180","5":"18180","creation_date":"1340416550","6":"1340416550"},{"0":"4111","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"tetsuo13-Vim-log4j-0.1-0-gc88aeac.zip","4":"tetsuo13-Vim-log4j-0.1-0-gc88aeac.zip","src_id":"18176","5":"18176","creation_date":"1340325590","6":"1340325590"}]},"4110":{"script_id":"4110","0":"4110","script_name":"sml_polyml.vim","1":"sml_polyml.vim","script_type":"ftplugin","2":"ftplugin","summary":"Poly\/ML integration","3":"Poly\/ML integration","description":"Uses Poly\/ML's IDE mode to provide features for editing Standard ML.  This includes compilation (even before saving the file), find expression types, finding symbol declarations and generating accessors for record datatypes.\r\n\r\nSee http:\/\/www.polyml.org\/","4":"Uses Poly\/ML's IDE mode to provide features for editing Standard ML.  This includes compilation (even before saving the file), find expression types, finding symbol declarations and generating accessors for record datatypes.\r\n\r\nSee http:\/\/www.polyml.org\/","install_details":"Unzip the file to your vim directory.  Documentation is provided in the header of ftplugin\/sml_polyml.vim","5":"Unzip the file to your vim directory.  Documentation is provided in the header of ftplugin\/sml_polyml.vim","first_name":"Alex","6":"Alex","last_name":"Merry","7":"Merry","releases":[{"0":"4110","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"sml_polyml.zip","4":"sml_polyml.zip","src_id":"18173","5":"18173","creation_date":"1340290175","6":"1340290175"}]},"4109":{"script_id":"4109","0":"4109","script_name":"autumnleaf_modified.vim","1":"autumnleaf_modified.vim","script_type":"color scheme","2":"color scheme","summary":"a light, simple and beautiful color scheme for programming and good for your eye","3":"a light, simple and beautiful color scheme for programming and good for your eye","description":"Modified according to the color scheme \"autumnleaf.vim\" . I think it is more beautiful than the original one. It is my color scheme for programming, and I enjoy it. Hope U enjoy it too.","4":"Modified according to the color scheme \"autumnleaf.vim\" . I think it is more beautiful than the original one. It is my color scheme for programming, and I enjoy it. Hope U enjoy it too.","install_details":"copy the file  \"autumnleaf_modified.vim\" to  ~\/.vim\/colors","5":"copy the file  \"autumnleaf_modified.vim\" to  ~\/.vim\/colors","first_name":"7","6":"7","last_name":"LI","7":"LI","releases":[{"0":"4109","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"autumnleaf_modified.vim","4":"autumnleaf_modified.vim","src_id":"18172","5":"18172","creation_date":"1340283076","6":"1340283076"}]},"4106":{"script_id":"4106","0":"4106","script_name":"fish-syntax","1":"fish-syntax","script_type":"syntax","2":"syntax","summary":"fish syntax based on sh","3":"fish syntax based on sh","description":"it's very simple syntax plugin, I just added fish keywords to sh syntax\r\n\r\nhttps:\/\/github.com\/aliva\/vim-fish","4":"it's very simple syntax plugin, I just added fish keywords to sh syntax\r\n\r\nhttps:\/\/github.com\/aliva\/vim-fish","install_details":"","5":"","first_name":"Ali","6":"Ali","last_name":"Vakilzade","7":"Vakilzade","releases":[{"0":"4106","vim_version":"7.0","1":"7.0","script_version":"4","2":"4","version_comment":"* autodetect  \"#!\/usr\/bin\/env fish\" as fish","3":"* autodetect  \"#!\/usr\/bin\/env fish\" as fish","package":"vim-fish.zip","4":"vim-fish.zip","src_id":"20242","5":"20242","creation_date":"1370010034","6":"1370010034"},{"0":"4106","vim_version":"7.0","1":"7.0","script_version":"3","2":"3","version_comment":"'in' and 'alias' added to keywords","3":"'in' and 'alias' added to keywords","package":"vim-fish.zip","4":"vim-fish.zip","src_id":"19922","5":"19922","creation_date":"1366793488","6":"1366793488"},{"0":"4106","vim_version":"7.0","1":"7.0","script_version":"2","2":"2","version_comment":"auto detect fish scripts using shebang ","3":"auto detect fish scripts using shebang ","package":"vim-fish-2.zip","4":"vim-fish-2.zip","src_id":"18214","5":"18214","creation_date":"1341306893","6":"1341306893"},{"0":"4106","vim_version":"7.0","1":"7.0","script_version":"1","2":"1","version_comment":"Initial upload","3":"Initial upload","package":"vim-fish.zip","4":"vim-fish.zip","src_id":"18168","5":"18168","creation_date":"1340209408","6":"1340209408"}]},"4105":{"script_id":"4105","0":"4105","script_name":"pysource.vim","1":"pysource.vim","script_type":"ftplugin","2":"ftplugin","summary":"View python source easily","3":"View python source easily","description":"Creates mappings to view python source easily. If your cursor is over the from module import class it will open up the module in a new tab, split or vsplit. \r\n\r\nFeel free to report issues here: https:\/\/github.com\/cwood\/pysource.vim or email me.","4":"Creates mappings to view python source easily. If your cursor is over the from module import class it will open up the module in a new tab, split or vsplit. \r\n\r\nFeel free to report issues here: https:\/\/github.com\/cwood\/pysource.vim or email me.","install_details":"Put into your ftplugin or use pathogen\/vundle. ","5":"Put into your ftplugin or use pathogen\/vundle. ","first_name":"Colin","6":"Colin","last_name":"Wood","7":"Wood","releases":[{"0":"4105","vim_version":"7.3","1":"7.3","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"cwood-pysource.vim-v1.0.0-0-gea98621.zip","4":"cwood-pysource.vim-v1.0.0-0-gea98621.zip","src_id":"18159","5":"18159","creation_date":"1340074859","6":"1340074859"}]},"4104":{"script_id":"4104","0":"4104","script_name":"gdbmgr","1":"gdbmgr","script_type":"utility","2":"utility","summary":"vim interface to gdb","3":"vim interface to gdb","description":"Gdbmgr supports a user-controllable multiple-tiled window interface to gdb, and does not need any external scripting support such as perl or python.  Try out the tutorial -- it contains seven examples with detailed instructions on how to compile the example code, run it, and use gdbmgr with it.\r\n\r\nUsing gdbgmgr is straightforward; you may start gdbmgr up from a running vim or, if you take the suggestion (:help gdbmgr-suggest), then attempting editing a program\\'s binary will bring up gdbmgr with that program loaded.\r\n\r\n  :DI programname...starts up gdbgmr with the given programname\r\n  :DR [args]..............runs the program (with optional arguments)\r\n  :DQ........................quit gdbmgr\r\n\r\nStandard Windows:\r\nBy default at startup you\\'ll have seven tiled windows in a tab:\r\n  Netrw................: useful for bringing source code into the Source window and setting breakpoints and examining variables\r\n  Messages........: shows messages issued by gdb\r\n  Function Stack..: shows current function stack\r\n  Source Window.: shows current source code\r\n  Expr..................: enter expressions to be evaluated (ie. shows variable values)\r\n  Breakpt.............: shows list of breakpoints\r\n  Watchpoint........: shows list of watchpoints\r\n\r\nOptional Windows:\r\nOther available gdbmgr windows include:\r\n  BufExplorer..: the buffer explorer shows its output here (see vimscript#42) - thanks to Jeff Lanzarotta for including some interface code!\r\n  Commands..: enter commands to gdb via this window.  This window is stacked with the Source Window; ie. when you run your program, the commands window is displayed instead of the Source Window.\r\n  Tags............: shows CtagExpl or HdrTag output (tags, hdrtags)\r\n  Threads......: shows the results of gdb\\'s \\\"info threads\\\" command\r\n\r\nForeign Apps:\r\n  Gdbmgr provides an interface to various \\\"foreign apps\\\"; ie. vimscripts that are external to gdbmgr itself.  Currently, gdbmgr provides interfaces to:\r\n  bufexplorer\r\n  CtagExpl\r\n  Hdrtag\r\n  netrw   (built-in interface)\r\n\r\nInstalling gdbmgr:\r\nGdbmgr does not require perl, python, or any other external scripting support.  However, it does need to have forkpty() support compiled in; you can get this by configuring your vim to support perl, python, or modify vim\\'s Makefile with EXTRA_LIBS = -lutil. \r\n\r\nRead :help gdbmgr-install   for information on how to get your vim configured and compiled for gdbmgr.\r\nRead :help gdbmgr-tutorial  to learn many of the details of using gdbmgr.  Examples are included!\r\n\r\nSupported:\r\nstepping - continue\r\nexamining variable values (with ballooneval, simply point the mouse at the variable name in the source code)\r\nbreakpoints\r\nwatchpoints\r\nfunction stack\r\nexamining core dumps\r\nmultiple-file source code programs supported\r\n\r\nSee gdbmgr's online documentation and examples at http:\/\/www.drchip.org\/astronaut\/vim\/doc\/gdbmgr.txt.html .\r\n\r\n(alpha\/beta version available at http:\/\/www.drchip.org\/astronaut\/vim\/index.html#GDBMGR)\r\n","4":"Gdbmgr supports a user-controllable multiple-tiled window interface to gdb, and does not need any external scripting support such as perl or python.  Try out the tutorial -- it contains seven examples with detailed instructions on how to compile the example code, run it, and use gdbmgr with it.\r\n\r\nUsing gdbgmgr is straightforward; you may start gdbmgr up from a running vim or, if you take the suggestion (:help gdbmgr-suggest), then attempting editing a program\\'s binary will bring up gdbmgr with that program loaded.\r\n\r\n  :DI programname...starts up gdbgmr with the given programname\r\n  :DR [args]..............runs the program (with optional arguments)\r\n  :DQ........................quit gdbmgr\r\n\r\nStandard Windows:\r\nBy default at startup you\\'ll have seven tiled windows in a tab:\r\n  Netrw................: useful for bringing source code into the Source window and setting breakpoints and examining variables\r\n  Messages........: shows messages issued by gdb\r\n  Function Stack..: shows current function stack\r\n  Source Window.: shows current source code\r\n  Expr..................: enter expressions to be evaluated (ie. shows variable values)\r\n  Breakpt.............: shows list of breakpoints\r\n  Watchpoint........: shows list of watchpoints\r\n\r\nOptional Windows:\r\nOther available gdbmgr windows include:\r\n  BufExplorer..: the buffer explorer shows its output here (see vimscript#42) - thanks to Jeff Lanzarotta for including some interface code!\r\n  Commands..: enter commands to gdb via this window.  This window is stacked with the Source Window; ie. when you run your program, the commands window is displayed instead of the Source Window.\r\n  Tags............: shows CtagExpl or HdrTag output (tags, hdrtags)\r\n  Threads......: shows the results of gdb\\'s \\\"info threads\\\" command\r\n\r\nForeign Apps:\r\n  Gdbmgr provides an interface to various \\\"foreign apps\\\"; ie. vimscripts that are external to gdbmgr itself.  Currently, gdbmgr provides interfaces to:\r\n  bufexplorer\r\n  CtagExpl\r\n  Hdrtag\r\n  netrw   (built-in interface)\r\n\r\nInstalling gdbmgr:\r\nGdbmgr does not require perl, python, or any other external scripting support.  However, it does need to have forkpty() support compiled in; you can get this by configuring your vim to support perl, python, or modify vim\\'s Makefile with EXTRA_LIBS = -lutil. \r\n\r\nRead :help gdbmgr-install   for information on how to get your vim configured and compiled for gdbmgr.\r\nRead :help gdbmgr-tutorial  to learn many of the details of using gdbmgr.  Examples are included!\r\n\r\nSupported:\r\nstepping - continue\r\nexamining variable values (with ballooneval, simply point the mouse at the variable name in the source code)\r\nbreakpoints\r\nwatchpoints\r\nfunction stack\r\nexamining core dumps\r\nmultiple-file source code programs supported\r\n\r\nSee gdbmgr's online documentation and examples at http:\/\/www.drchip.org\/astronaut\/vim\/doc\/gdbmgr.txt.html .\r\n\r\n(alpha\/beta version available at http:\/\/www.drchip.org\/astronaut\/vim\/index.html#GDBMGR)\r\n","install_details":"* needs huge\/large vim and linux\r\ncd $HOME\/.vim\r\nmv [wherever]\/gdbmgr.tar.gz .\r\ngunzip gdbmgr.tar.gz\r\ntar -xf gdbmgr.tar\r\nvi\r\n:helptags ~\/.vim\/doc\r\n:q\r\n","5":"* needs huge\/large vim and linux\r\ncd $HOME\/.vim\r\nmv [wherever]\/gdbmgr.tar.gz .\r\ngunzip gdbmgr.tar.gz\r\ntar -xf gdbmgr.tar\r\nvi\r\n:helptags ~\/.vim\/doc\r\n:q\r\n","first_name":"Charles","6":"Charles","last_name":"Campbell","7":"Campbell","releases":[{"0":"4104","vim_version":"7.3","1":"7.3","script_version":"1","2":"1","version_comment":"vim interface to gdb (with getscripts support)","3":"vim interface to gdb (with getscripts support)","package":"gdbmgr.tar.gz","4":"gdbmgr.tar.gz","src_id":"18153","5":"18153","creation_date":"1340050371","6":"1340050371"}]},"4103":{"script_id":"4103","0":"4103","script_name":"GdbFromVim","1":"GdbFromVim","script_type":"utility","2":"utility","summary":"This pluging lets you debug your applications with gdb from vim,","3":"This pluging lets you debug your applications with gdb from vim,","description":"Requirements\r\n\r\n    GdbFromVim requires Vim 7.3+ compiled with Python support.\r\n    Python 2.6+\r\n    Gdblib - https:\/\/github.com\/skibyte\/gdblib <-- MAKE SURE TO USE THE LAST gdblib VERSION!!!\r\n\r\nYou can obtain the latest GdbFromVim development version from : https:\/\/github.com\/skibyte\/gdb-from-vim\r\n\r\nSetting the application to debug:  let g:gdb_from_vim_app = 'application'\r\nSettings the arguments for the application: let g:gdb_from_vim_args = 'arguments'\r\nSetting the gdb path let g:gdb_from_vim_path = '\/usr\/bin\/gdb'\r\n\r\n\r\n-------------------------------------------------------------------------------------------------------------\r\nCommands\r\n-------------------------------------------------------------------------------------------------------------\r\nGdbFromVimRun:  This command starts the execution of the program.\r\n\r\nGdbFromVimStep:  This commands steps into a function.\r\n\r\nGdbFromVimNext:   This commands pass over a function.\r\n\r\nGdbFromVimContinue: This command continues with the execution of the program, this command is also\r\nused to start remote debugging.\r\n\r\nGdbFromVimAddBreakpoint:  This command adds a breakpoint in the current line.\r\n\r\nGdbFromVimDeleteBreakpoint:This command deletes the breakpoint specified by its number.\r\n\r\nGdbFromVimDeleteAllBreakpoints: This command deletes all the breakpoints previously set.\r\n\r\nGdbFromVimClear: This commands deletes the breakpoint in the current line.\r\n\r\nGdbFromVimPrint: This command prints the value of a variable, it requires an argument, For example: GdbFromVimPrint point->x\r\n\r\nGdbFromVimPrintBreakpoints:This command prints all the breakpoints set in the application, the values are printed in the quickfix list.\r\n\r\nGdbFromVimTty: This command is used to redirect the IO to the specified tty passed as argument.\r\n\r\nGdbFromVimClose: Closes the current gdb connection, this command might be used if you want to change the application to debug at runtime.\r\n\r\nGdbFromVimRemote : This command is used to perform remote debugging, it receives as argument the\r\nhost and its port:\r\n\r\n    GdbFromVimRemote 127.0.0.1:1234\r\n\r\nGdbFromVimSymbolFile : Adds the symbol file passed as argument to gdb.\r\n","4":"Requirements\r\n\r\n    GdbFromVim requires Vim 7.3+ compiled with Python support.\r\n    Python 2.6+\r\n    Gdblib - https:\/\/github.com\/skibyte\/gdblib <-- MAKE SURE TO USE THE LAST gdblib VERSION!!!\r\n\r\nYou can obtain the latest GdbFromVim development version from : https:\/\/github.com\/skibyte\/gdb-from-vim\r\n\r\nSetting the application to debug:  let g:gdb_from_vim_app = 'application'\r\nSettings the arguments for the application: let g:gdb_from_vim_args = 'arguments'\r\nSetting the gdb path let g:gdb_from_vim_path = '\/usr\/bin\/gdb'\r\n\r\n\r\n-------------------------------------------------------------------------------------------------------------\r\nCommands\r\n-------------------------------------------------------------------------------------------------------------\r\nGdbFromVimRun:  This command starts the execution of the program.\r\n\r\nGdbFromVimStep:  This commands steps into a function.\r\n\r\nGdbFromVimNext:   This commands pass over a function.\r\n\r\nGdbFromVimContinue: This command continues with the execution of the program, this command is also\r\nused to start remote debugging.\r\n\r\nGdbFromVimAddBreakpoint:  This command adds a breakpoint in the current line.\r\n\r\nGdbFromVimDeleteBreakpoint:This command deletes the breakpoint specified by its number.\r\n\r\nGdbFromVimDeleteAllBreakpoints: This command deletes all the breakpoints previously set.\r\n\r\nGdbFromVimClear: This commands deletes the breakpoint in the current line.\r\n\r\nGdbFromVimPrint: This command prints the value of a variable, it requires an argument, For example: GdbFromVimPrint point->x\r\n\r\nGdbFromVimPrintBreakpoints:This command prints all the breakpoints set in the application, the values are printed in the quickfix list.\r\n\r\nGdbFromVimTty: This command is used to redirect the IO to the specified tty passed as argument.\r\n\r\nGdbFromVimClose: Closes the current gdb connection, this command might be used if you want to change the application to debug at runtime.\r\n\r\nGdbFromVimRemote : This command is used to perform remote debugging, it receives as argument the\r\nhost and its port:\r\n\r\n    GdbFromVimRemote 127.0.0.1:1234\r\n\r\nGdbFromVimSymbolFile : Adds the symbol file passed as argument to gdb.\r\n","install_details":"Extract the plugin and documentation in your vim installation","5":"Extract the plugin and documentation in your vim installation","first_name":"Fernando","6":"Fernando","last_name":"Castillo","7":"Castillo","releases":[{"0":"4103","vim_version":"7.3","1":"7.3","script_version":"0.7.2","2":"0.7.2","version_comment":"Added GdbFromVimRemote to perform remote debugging and GdbFromVimSymbolFile to load symbols","3":"Added GdbFromVimRemote to perform remote debugging and GdbFromVimSymbolFile to load symbols","package":"gdb_from_vim_0.7.2.tar.gz","4":"gdb_from_vim_0.7.2.tar.gz","src_id":"18244","5":"18244","creation_date":"1342021588","6":"1342021588"},{"0":"4103","vim_version":"7.3","1":"7.3","script_version":"0.7","2":"0.7","version_comment":"Added GdbFromVimContinue\r\nGdbFromVimTty\r\nAsk for program to debug if g:gdb_from_vim_app is not defined","3":"Added GdbFromVimContinue\r\nGdbFromVimTty\r\nAsk for program to debug if g:gdb_from_vim_app is not defined","package":"gdbfromvim.vim","4":"gdbfromvim.vim","src_id":"18166","5":"18166","creation_date":"1340156007","6":"1340156007"},{"0":"4103","vim_version":"7.3","1":"7.3","script_version":"0.5","2":"0.5","version_comment":"Initial upload","3":"Initial upload","package":"gdbfromvim.vim","4":"gdbfromvim.vim","src_id":"18147","5":"18147","creation_date":"1339968341","6":"1339968341"}]},"4102":{"script_id":"4102","0":"4102","script_name":"vim-brunch","1":"vim-brunch","script_type":"utility","2":"utility","summary":"Easy file navigation for brunch projects","3":"Easy file navigation for brunch projects","description":"Inspired by vim-rails this plugin makes navigating through your brunch (http:\/\/brunch.io) projects a lot more comfortable. Besides an interface to the brunch command line it offers ex commands to quickly move from one brunch file to one of its related files.\r\n\r\nWant to open your user model? Type :Bmodel user. Need the corresponding unit test in a vertical split? Just go :BVtest.\r\n\r\nGrab the latest dev version from github: https:\/\/github.com\/drichard\/vim-brunch","4":"Inspired by vim-rails this plugin makes navigating through your brunch (http:\/\/brunch.io) projects a lot more comfortable. Besides an interface to the brunch command line it offers ex commands to quickly move from one brunch file to one of its related files.\r\n\r\nWant to open your user model? Type :Bmodel user. Need the corresponding unit test in a vertical split? Just go :BVtest.\r\n\r\nGrab the latest dev version from github: https:\/\/github.com\/drichard\/vim-brunch","install_details":"Extract the archive into your .vim directory.","5":"Extract the archive into your .vim directory.","first_name":"David","6":"David","last_name":"Richard","7":"Richard","releases":[{"0":"4102","vim_version":"7.0","1":"7.0","script_version":"0.2.0","2":"0.2.0","version_comment":"Add optional bang ! modifier to most commands","3":"Add optional bang ! modifier to most commands","package":"vim-brunch.zip","4":"vim-brunch.zip","src_id":"18160","5":"18160","creation_date":"1340095687","6":"1340095687"},{"0":"4102","vim_version":"7.0","1":"7.0","script_version":"0.1.0","2":"0.1.0","version_comment":"Initial upload","3":"Initial upload","package":"vim-brunch.zip","4":"vim-brunch.zip","src_id":"18146","5":"18146","creation_date":"1339968062","6":"1339968062"}]},"4101":{"script_id":"4101","0":"4101","script_name":"PEGJS.vim","1":"PEGJS.vim","script_type":"syntax","2":"syntax","summary":"syntax highlighting for PEG.js grammar files","3":"syntax highlighting for PEG.js grammar files","description":"Syntax highlighting for peg-js files.\r\n\r\nDetails about PEG.js here: http:\/\/pegjs.majda.cz\/\r\n\r\nCode repository for this script: https:\/\/github.com\/alunny\/pegjs-vim","4":"Syntax highlighting for peg-js files.\r\n\r\nDetails about PEG.js here: http:\/\/pegjs.majda.cz\/\r\n\r\nCode repository for this script: https:\/\/github.com\/alunny\/pegjs-vim","install_details":"Copy the script to your ~\/.vim\/syntax directory.\r\n\r\nThen \":setf pegjs\" in a file, or add \"au BufRead,BufNewFile *.pegjs setfiletype pegjs\" to your vimrc.","5":"Copy the script to your ~\/.vim\/syntax directory.\r\n\r\nThen \":setf pegjs\" in a file, or add \"au BufRead,BufNewFile *.pegjs setfiletype pegjs\" to your vimrc.","first_name":"Andrew","6":"Andrew","last_name":"Lunny","7":"Lunny","releases":[{"0":"4101","vim_version":"7.0","1":"7.0","script_version":"3","2":"3","version_comment":"handle blocks inside blocks correctly","3":"handle blocks inside blocks correctly","package":"pegjs.vim","4":"pegjs.vim","src_id":"18136","5":"18136","creation_date":"1339863941","6":"1339863941"},{"0":"4101","vim_version":"7.0","1":"7.0","script_version":"2","2":"2","version_comment":"support for single-line\/inline comments","3":"support for single-line\/inline comments","package":"pegjs.vim","4":"pegjs.vim","src_id":"18133","5":"18133","creation_date":"1339825330","6":"1339825330"},{"0":"4101","vim_version":"7.0","1":"7.0","script_version":"1","2":"1","version_comment":"Initial upload","3":"Initial upload","package":"pegjs.vim","4":"pegjs.vim","src_id":"18132","5":"18132","creation_date":"1339824673","6":"1339824673"}]},"4100":{"script_id":"4100","0":"4100","script_name":"abc-vim","1":"abc-vim","script_type":"syntax","2":"syntax","summary":"abc music notation syntax, 2.1 and up","3":"abc music notation syntax, 2.1 and up","description":"DEPRECATED: Because of more recent editors, like SublimeText, I don't think I'll ever be able to work on a proper Vim script that could encompass the features I feel need to be provided. None the less, I'll keep this here in case others need it.","4":"DEPRECATED: Because of more recent editors, like SublimeText, I don't think I'll ever be able to work on a proper Vim script that could encompass the features I feel need to be provided. None the less, I'll keep this here in case others need it.","install_details":"For now, copy the abc.vim script to your $VIMRUNTIME or ~\/.vim\/syntax\/ folder.\r\nOn Windows, copy abc.vim to $VIMRUNTIME\\vimfiles\\syntax\\.\r\n\r\nI'm looking into using Vimball, so this will get easier to use after I get a decent set of scripts working. Currently, I'm not very good with getting Vimball to do what I want. Sorry.","5":"For now, copy the abc.vim script to your $VIMRUNTIME or ~\/.vim\/syntax\/ folder.\r\nOn Windows, copy abc.vim to $VIMRUNTIME\\vimfiles\\syntax\\.\r\n\r\nI'm looking into using Vimball, so this will get easier to use after I get a decent set of scripts working. Currently, I'm not very good with getting Vimball to do what I want. Sorry.","first_name":"Lee","6":"Lee","last_name":"Savide","7":"Savide","releases":[{"0":"4100","vim_version":"7.3","1":"7.3","script_version":"1.0","2":"1.0","version_comment":"Syntax script only; Currently the only working script at the moment.","3":"Syntax script only; Currently the only working script at the moment.","package":"abc.vim","4":"abc.vim","src_id":"19094","5":"19094","creation_date":"1354572942","6":"1354572942"}]},"4099":{"script_id":"4099","0":"4099","script_name":"oh-l\u00c3\u00a0-l\u00c3\u00a0","1":"oh-l\u00c3\u00a0-l\u00c3\u00a0","script_type":"color scheme","2":"color scheme","summary":"High contrast dark color scheme with black background","3":"High contrast dark color scheme with black background","description":"This is a high contrast dark color scheme with black background, based on named colors.  The GUI variant uses LimeGreen, Coral, Tomato, and even DeepPink.\r\n\r\nScreenshot of an older version: http:\/\/i49.tinypic.com\/33k6a2e.jpg","4":"This is a high contrast dark color scheme with black background, based on named colors.  The GUI variant uses LimeGreen, Coral, Tomato, and even DeepPink.\r\n\r\nScreenshot of an older version: http:\/\/i49.tinypic.com\/33k6a2e.jpg","install_details":"Install as usually (put into ~\/.vim\/colors).","5":"Install as usually (put into ~\/.vim\/colors).","first_name":"Alexey","6":"Alexey","last_name":"Muranov","7":"Muranov","releases":[{"0":"4099","vim_version":"7.0","1":"7.0","script_version":"0.9.6","2":"0.9.6","version_comment":"Avoid bright white colors.","3":"Avoid bright white colors.","package":"oh-la-la.vim","4":"oh-la-la.vim","src_id":"20150","5":"20150","creation_date":"1368792591","6":"1368792591"}]},"4098":{"script_id":"4098","0":"4098","script_name":"sharefix","1":"sharefix","script_type":"utility","2":"utility","summary":"Share quickfixes among commands and functions","3":"Share quickfixes among commands and functions","description":"Sharefix addresses the pain point of your quickfix list being wiped out\r\nbetween running different commands or functions that update the list.\r\n\r\nFor example, you run your unit tests and get a list of tests that\r\nfailed. Then when you make some changes, write the file, and your linter\r\nauto command kicks off and clears the list of tests. Now to fix the\r\nother failed tests you have to rerun all your tests.\r\n\r\nSharefix lets you easily make your quickfix commands or functions play\r\nnicely together and share the list with each other.\r\n\r\nThis plugin is developed on github:\r\n\r\nhttps:\/\/github.com\/samiconductor\/vim-sharefix","4":"Sharefix addresses the pain point of your quickfix list being wiped out\r\nbetween running different commands or functions that update the list.\r\n\r\nFor example, you run your unit tests and get a list of tests that\r\nfailed. Then when you make some changes, write the file, and your linter\r\nauto command kicks off and clears the list of tests. Now to fix the\r\nother failed tests you have to rerun all your tests.\r\n\r\nSharefix lets you easily make your quickfix commands or functions play\r\nnicely together and share the list with each other.\r\n\r\nThis plugin is developed on github:\r\n\r\nhttps:\/\/github.com\/samiconductor\/vim-sharefix","install_details":"Unzip sharefix.zip into your vim runtime or clone the project from github and place it in your runtime.","5":"Unzip sharefix.zip into your vim runtime or clone the project from github and place it in your runtime.","first_name":"Sam","6":"Sam","last_name":"Simmons","7":"Simmons","releases":[{"0":"4098","vim_version":"7.3","1":"7.3","script_version":"1.0.0","2":"1.0.0","version_comment":"Initial upload","3":"Initial upload","package":"sharefix.zip","4":"sharefix.zip","src_id":"18109","5":"18109","creation_date":"1339300747","6":"1339300747"}]},"4097":{"script_id":"4097","0":"4097","script_name":"fisa-color-scheme","1":"fisa-color-scheme","script_type":"color scheme","2":"color scheme","summary":"soft color scheme for terminals with 256 colors","3":"soft color scheme for terminals with 256 colors","description":"Soft color scheme for terminals with 256 colors, better looking with a dark but not pure-black background terminal.\r\n\r\nOfficial repo:\r\nhttps:\/\/github.com\/fisadev\/fisa-vim-colorscheme\r\n\r\n","4":"Soft color scheme for terminals with 256 colors, better looking with a dark but not pure-black background terminal.\r\n\r\nOfficial repo:\r\nhttps:\/\/github.com\/fisadev\/fisa-vim-colorscheme\r\n\r\n","install_details":"just put the file under your .vim\/colors folder, or install it from the official repo using a plugin manager (Bundle, Vundle, Pathogen, ...)","5":"just put the file under your .vim\/colors folder, or install it from the official repo using a plugin manager (Bundle, Vundle, Pathogen, ...)","first_name":"Juan Pedro","6":"Juan Pedro","last_name":"Fisanotti","7":"Fisanotti","releases":[{"0":"4097","vim_version":"7.0","1":"7.0","script_version":"ef9dd4","2":"ef9dd4","version_comment":"changed to dark background for the tab bar","3":"changed to dark background for the tab bar","package":"fisa.vim","4":"fisa.vim","src_id":"20870","5":"20870","creation_date":"1380757474","6":"1380757474"},{"0":"4097","vim_version":"7.0","1":"7.0","script_version":"f3e1ce","2":"f3e1ce","version_comment":"added coloring for sign column","3":"added coloring for sign column","package":"fisa.vim","4":"fisa.vim","src_id":"19597","5":"19597","creation_date":"1362517158","6":"1362517158"}]},"4096":{"script_id":"4096","0":"4096","script_name":"maven-ide","1":"maven-ide","script_type":"utility","2":"utility","summary":"maven-ide plugin","3":"maven-ide plugin","description":"The goal of maven-ide plugin is to provide ide functionality for the\r\ndevelopment of java maven projects.\r\n\r\nFeatures include:\r\n    o Project tree for file navigation and environment context management.\r\n    o Quickfix for output of maven plugins compile,junit,checkstyle.\r\n    o Optional single source file compilation directly with javac.\r\n    o Compilation is background via AsyncCommand.\r\n    o Debug using yavdb, allows debug of class main or attach to jvm debug\r\n       port.\r\n    o Allow attach to a debug process on a remote host.\r\n    o Junit run\/quickfix\/debug.\r\n    o Dependency source file and javadoc integration. Javadoc viewing uses\r\n      lynx.\r\n    o Exctags tag navigation.\r\n    o Extract the maven main (source, resources), test (source, resources)\r\n      directories from the project pom.xml.\r\n    o Auto generation of project environment ie classpath, tag files.\r\n    o Dependency management for maven parent\/child\/sibling projects extracted\r\n      from project poms.\r\n    o Autocomplete on methods, auto add of imports etc is via the vjde plugin\r\n      project.\r\n    o Auto build of javadoc from source when it does not exist.\r\n","4":"The goal of maven-ide plugin is to provide ide functionality for the\r\ndevelopment of java maven projects.\r\n\r\nFeatures include:\r\n    o Project tree for file navigation and environment context management.\r\n    o Quickfix for output of maven plugins compile,junit,checkstyle.\r\n    o Optional single source file compilation directly with javac.\r\n    o Compilation is background via AsyncCommand.\r\n    o Debug using yavdb, allows debug of class main or attach to jvm debug\r\n       port.\r\n    o Allow attach to a debug process on a remote host.\r\n    o Junit run\/quickfix\/debug.\r\n    o Dependency source file and javadoc integration. Javadoc viewing uses\r\n      lynx.\r\n    o Exctags tag navigation.\r\n    o Extract the maven main (source, resources), test (source, resources)\r\n      directories from the project pom.xml.\r\n    o Auto generation of project environment ie classpath, tag files.\r\n    o Dependency management for maven parent\/child\/sibling projects extracted\r\n      from project poms.\r\n    o Autocomplete on methods, auto add of imports etc is via the vjde plugin\r\n      project.\r\n    o Auto build of javadoc from source when it does not exist.\r\n","install_details":"See doc\/maven-ide.txt","5":"See doc\/maven-ide.txt","first_name":"Daren","6":"Daren","last_name":"Isaacs","7":"Isaacs","releases":[{"0":"4096","vim_version":"7.0","1":"7.0","script_version":"0.6","2":"0.6","version_comment":"Many bug fixes.","3":"Many bug fixes.","package":"maven-ide-0.6.tar.gz","4":"maven-ide-0.6.tar.gz","src_id":"19067","5":"19067","creation_date":"1354246934","6":"1354246934"},{"0":"4096","vim_version":"7.0","1":"7.0","script_version":"0.5.0","2":"0.5.0","version_comment":"Initial upload","3":"Initial upload","package":"maven-ide-0.5.0.tar.gz","4":"maven-ide-0.5.0.tar.gz","src_id":"18103","5":"18103","creation_date":"1339123443","6":"1339123443"}]},"4095":{"script_id":"4095","0":"4095","script_name":"vim-django","1":"vim-django","script_type":"utility","2":"utility","summary":"Support for Django through VIM","3":"Support for Django through VIM","description":"Vim-Django\r\nVim-Django is a vim script that helps manage a django app. It has wrapping's for the django-admin.py, your projects manage.py and some helper commands. It also has some quick ways to find templates, edit related files in a app, create new apps, and help manage django while using Vim.\r\n\r\nCommands\r\nDjangoAdmin will run any command through the django-admin.py command.\r\n\r\nDjangoManage will run the management command for the project\r\n\r\nDjangoProjectActivate will activate the project. This will go through your g:django_projects and find all the django projects. It will also set up DJANGO_SETTINGS_MODULE in your environment and the directory where the settings file is stored in your PYTHONPATH.\r\n\r\nDjangoCreateApp will create a new app under your projects base. It will autocomplete the path. It just needs is a python path such as, colinbits.apps.new_app this will be created in the folder colinbits, apps, then run the django-admin.py to create the app there.\r\n\r\nMappings\r\nThere are mappings for easily editing related django files while working on a app. They all can be changed if you dont like how they are currently mapped. There are mappins for (v|views), (u|urls), (a|admin), and (t|tests). If you want to remap these you can call the function django#apps#edit('name_of_file.py', 'split') and it will open up the file it fineds in a split.\r\n\r\nConfiguration\r\ng:django_projects is where your django projects are located.\r\n\r\ng:django_activate_virtualenv when true will activate a virtualenv that starts with the same name. An example being. colinbits, is the site, and the virtuale env being colinbits.com.\r\n\r\nCustom Activation of Projects\r\nSince not everyone uses the default settings file vim-django will allow you to add a custom function to activate any project. In your vimrc you can define a function called ActivateProject it needs to accept one argument. From here you can have it activate the project.\r\n\r\nWorking with other Scripts\r\nNERDTree: g:django_activate_nerdtree when set to 1 will launch nerdtree when activating the django project.\r\n\r\nVirtualEnv: g:django_activate_virtualenv when set to 1 will activate the virtual env that starts with the same name.\r\n\r\nInstalling\r\nI recommend using pathogen or vundle to install this script. Else, you can put the django.vim in the plug-ins directory. This script does require python to be compiled in.\r\n\r\nScreen shots\r\n\r\n\r\nFAQ\r\nWorking with virtualenv's\r\nI actully reccomend installing vim-virtualenv","4":"Vim-Django\r\nVim-Django is a vim script that helps manage a django app. It has wrapping's for the django-admin.py, your projects manage.py and some helper commands. It also has some quick ways to find templates, edit related files in a app, create new apps, and help manage django while using Vim.\r\n\r\nCommands\r\nDjangoAdmin will run any command through the django-admin.py command.\r\n\r\nDjangoManage will run the management command for the project\r\n\r\nDjangoProjectActivate will activate the project. This will go through your g:django_projects and find all the django projects. It will also set up DJANGO_SETTINGS_MODULE in your environment and the directory where the settings file is stored in your PYTHONPATH.\r\n\r\nDjangoCreateApp will create a new app under your projects base. It will autocomplete the path. It just needs is a python path such as, colinbits.apps.new_app this will be created in the folder colinbits, apps, then run the django-admin.py to create the app there.\r\n\r\nMappings\r\nThere are mappings for easily editing related django files while working on a app. They all can be changed if you dont like how they are currently mapped. There are mappins for (v|views), (u|urls), (a|admin), and (t|tests). If you want to remap these you can call the function django#apps#edit('name_of_file.py', 'split') and it will open up the file it fineds in a split.\r\n\r\nConfiguration\r\ng:django_projects is where your django projects are located.\r\n\r\ng:django_activate_virtualenv when true will activate a virtualenv that starts with the same name. An example being. colinbits, is the site, and the virtuale env being colinbits.com.\r\n\r\nCustom Activation of Projects\r\nSince not everyone uses the default settings file vim-django will allow you to add a custom function to activate any project. In your vimrc you can define a function called ActivateProject it needs to accept one argument. From here you can have it activate the project.\r\n\r\nWorking with other Scripts\r\nNERDTree: g:django_activate_nerdtree when set to 1 will launch nerdtree when activating the django project.\r\n\r\nVirtualEnv: g:django_activate_virtualenv when set to 1 will activate the virtual env that starts with the same name.\r\n\r\nInstalling\r\nI recommend using pathogen or vundle to install this script. Else, you can put the django.vim in the plug-ins directory. This script does require python to be compiled in.\r\n\r\nScreen shots\r\n\r\n\r\nFAQ\r\nWorking with virtualenv's\r\nI actully reccomend installing vim-virtualenv","install_details":"Copy into your plugin directory or use vundle\/pathogen","5":"Copy into your plugin directory or use vundle\/pathogen","first_name":"Colin","6":"Colin","last_name":"Wood","7":"Wood","releases":[{"0":"4095","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Vim Django stable release. If you have any issues please email me or create a new issue on github.com\/cwood\/vim-django. It would be greatly appreciated! ","3":"Vim Django stable release. If you have any issues please email me or create a new issue on github.com\/cwood\/vim-django. It would be greatly appreciated! ","package":"vim-django-1.0.tar.gz","4":"vim-django-1.0.tar.gz","src_id":"18623","5":"18623","creation_date":"1347765945","6":"1347765945"},{"0":"4095","vim_version":"7.3","1":"7.3","script_version":"0.3.1","2":"0.3.1","version_comment":"Keymappings to work with related files when in a app.\r\nExtensions to work with NERDTree and VirtualEnv\r\nCustom activation of projects\r\nMisc bug fixes","3":"Keymappings to work with related files when in a app.\r\nExtensions to work with NERDTree and VirtualEnv\r\nCustom activation of projects\r\nMisc bug fixes","package":"cwood-vim-django-0.3.1a-0-gd3cac29.tar.gz","4":"cwood-vim-django-0.3.1a-0-gd3cac29.tar.gz","src_id":"18301","5":"18301","creation_date":"1342930940","6":"1342930940"},{"0":"4095","vim_version":"7.3","1":"7.3","script_version":"0.2.1a","2":"0.2.1a","version_comment":"Updated with documentation\r\nCan now create apps using DjangoCreateApp\r\nSome bug fixes and changing managment commands to better reflect the script name","3":"Updated with documentation\r\nCan now create apps using DjangoCreateApp\r\nSome bug fixes and changing managment commands to better reflect the script name","package":"cwood-vim-django-0.2.1a-0-ge339a41 (1).zip","4":"cwood-vim-django-0.2.1a-0-ge339a41 (1).zip","src_id":"18192","5":"18192","creation_date":"1340631245","6":"1340631245"},{"0":"4095","vim_version":"7.3","1":"7.3","script_version":"0.0.1","2":"0.0.1","version_comment":"Initial upload","3":"Initial upload","package":"vim-django.zip","4":"vim-django.zip","src_id":"18102","5":"18102","creation_date":"1339122058","6":"1339122058"}]},"4094":{"script_id":"4094","0":"4094","script_name":"tips.vim","1":"tips.vim","script_type":"utility","2":"utility","summary":"Show vim tips everytime when you enter vim","3":"Show vim tips everytime when you enter vim","description":"Show vim tips everytime when you enter vim. \r\n\r\nScreenshot:https:\/\/github.com\/downloads\/yesmeck\/tips.vim\/screenshot.png \r\n\r\n**Requirement** \r\n\r\nruby \r\n\r\n**Usage** \r\n\r\nJust open your vim! Or use command  :NextTip  to view more tips. \r\n\r\nYour can submit your tips to http:\/\/vim-tips.org \r\n\r\nDevelop version: https:\/\/github.com\/yesmeck\/tips.vim \r\nReport a issue:https:\/\/github.com\/yesmeck\/tips.vim\/issues","4":"Show vim tips everytime when you enter vim. \r\n\r\nScreenshot:https:\/\/github.com\/downloads\/yesmeck\/tips.vim\/screenshot.png \r\n\r\n**Requirement** \r\n\r\nruby \r\n\r\n**Usage** \r\n\r\nJust open your vim! Or use command  :NextTip  to view more tips. \r\n\r\nYour can submit your tips to http:\/\/vim-tips.org \r\n\r\nDevelop version: https:\/\/github.com\/yesmeck\/tips.vim \r\nReport a issue:https:\/\/github.com\/yesmeck\/tips.vim\/issues","install_details":"Save to .vim\/plugin","5":"Save to .vim\/plugin","first_name":"Wei","6":"Wei","last_name":"Zhu","7":"Zhu","releases":[{"0":"4094","vim_version":"7.0","1":"7.0","script_version":"1.0.0","2":"1.0.0","version_comment":"Initial upload","3":"Initial upload","package":"vim-tips.tar.gz","4":"vim-tips.tar.gz","src_id":"18098","5":"18098","creation_date":"1339080738","6":"1339080738"}]},"4093":{"script_id":"4093","0":"4093","script_name":"shuffle.vim","1":"shuffle.vim","script_type":"utility","2":"utility","summary":"Do the random shuffle of lines in vim's buffer","3":"Do the random shuffle of lines in vim's buffer","description":"This is a simple script to do the random shuffle of the lines in\r\nbuffer.  Please notice that this script need python2 support!\r\nIn order to use the map conveniently, you may want to define some key\r\nmap yourself.\r\n\r\nUsage:\r\n   Press \"V\" to select some line.  Use command :Shuffle to do the left\r\n  work.\r\n","4":"This is a simple script to do the random shuffle of the lines in\r\nbuffer.  Please notice that this script need python2 support!\r\nIn order to use the map conveniently, you may want to define some key\r\nmap yourself.\r\n\r\nUsage:\r\n   Press \"V\" to select some line.  Use command :Shuffle to do the left\r\n  work.\r\n","install_details":"Copy it to the plugin directory","5":"Copy it to the plugin directory","first_name":"Yichao","6":"Yichao","last_name":"Zhou","7":"Zhou","releases":[{"0":"4093","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"shuffle.vim","4":"shuffle.vim","src_id":"18093","5":"18093","creation_date":"1338951697","6":"1338951697"}]},"4092":{"script_id":"4092","0":"4092","script_name":"Vitra","1":"Vitra","script_type":"utility","2":"utility","summary":"Trac UI for vim","3":"Trac UI for vim","description":"Vitra (Trac client UI for ViM) http:\/\/trac.edgewall.org\r\n\r\nVitra is a Trac client UI for the wonderful universal editor Vim. It talks to a trac server via XML-RPC. It provides a fancy UI for both wiki and tickets. A paginated list of tickets window, full ticket detail window along with attachment window makes a great UI for ticket manipulation. The wiki UI combines the list of wiki pages, edit window with the content of the wiki and a preview window. It also has timeline, search and changeset windows.\r\n\r\nThe homepage of the plugin and the development happens here:\r\nhttp:\/\/nsmgr8.github.com\/vitra\/\r\nhttps:\/\/github.com\/nsmgr8\/vitra","4":"Vitra (Trac client UI for ViM) http:\/\/trac.edgewall.org\r\n\r\nVitra is a Trac client UI for the wonderful universal editor Vim. It talks to a trac server via XML-RPC. It provides a fancy UI for both wiki and tickets. A paginated list of tickets window, full ticket detail window along with attachment window makes a great UI for ticket manipulation. The wiki UI combines the list of wiki pages, edit window with the content of the wiki and a preview window. It also has timeline, search and changeset windows.\r\n\r\nThe homepage of the plugin and the development happens here:\r\nhttp:\/\/nsmgr8.github.com\/vitra\/\r\nhttps:\/\/github.com\/nsmgr8\/vitra","install_details":"See the README.md file","5":"See the README.md file","first_name":"Nasimul","6":"Nasimul","last_name":"Haque","7":"Haque","releases":[{"0":"4092","vim_version":"7.3","1":"7.3","script_version":"1.3","2":"1.3","version_comment":"- Add kerberos authentication\r\n- Improve encoding support\r\n- few bugfixes","3":"- Add kerberos authentication\r\n- Improve encoding support\r\n- few bugfixes","package":"vitra-1.3.zip","4":"vitra-1.3.zip","src_id":"18267","5":"18267","creation_date":"1342382304","6":"1342382304"},{"0":"4092","vim_version":"7.3","1":"7.3","script_version":"1.2","2":"1.2","version_comment":"- Documentation on digest authentication\r\n- Reload page after wiki save\r\n- Fix trac server change\r\n- Open own windows for different changesets and searches\r\n- Fix general commands on ticket\/wiki windows\r\n- Improvement on command tab completion","3":"- Documentation on digest authentication\r\n- Reload page after wiki save\r\n- Fix trac server change\r\n- Open own windows for different changesets and searches\r\n- Fix general commands on ticket\/wiki windows\r\n- Improvement on command tab completion","package":"vitra-1.2.zip","4":"vitra-1.2.zip","src_id":"18201","5":"18201","creation_date":"1341010116","6":"1341010116"},{"0":"4092","vim_version":"7.3","1":"7.3","script_version":"1.1","2":"1.1","version_comment":"Reduced RPC requests for both wiki and ticket UI","3":"Reduced RPC requests for both wiki and ticket UI","package":"vitra-1.1.zip","4":"vitra-1.1.zip","src_id":"18111","5":"18111","creation_date":"1339336886","6":"1339336886"},{"0":"4092","vim_version":"7.3","1":"7.3","script_version":"1.0","2":"1.0","version_comment":"* Formatted ticket view\r\n* Friendly message on error\r\n* Timeline filtering\r\nand many more to make it 1.0","3":"* Formatted ticket view\r\n* Friendly message on error\r\n* Timeline filtering\r\nand many more to make it 1.0","package":"vitra-1.0.zip","4":"vitra-1.0.zip","src_id":"18101","5":"18101","creation_date":"1339105391","6":"1339105391"},{"0":"4092","vim_version":"7.3","1":"7.3","script_version":"0.6","2":"0.6","version_comment":"Improved documentation. Help now includes usage detail.","3":"Improved documentation. Help now includes usage detail.","package":"vitra-0.6.zip","4":"vitra-0.6.zip","src_id":"18092","5":"18092","creation_date":"1338899102","6":"1338899102"},{"0":"4092","vim_version":"7.3","1":"7.3","script_version":"0.5","2":"0.5","version_comment":"Initial upload","3":"Initial upload","package":"vitra-0.5.zip","4":"vitra-0.5.zip","src_id":"18087","5":"18087","creation_date":"1338772612","6":"1338772612"}]},"4091":{"script_id":"4091","0":"4091","script_name":"Difference mode color settings","1":"Difference mode color settings","script_type":"ftplugin","2":"ftplugin","summary":"plugin for setting colors in difference mode","3":"plugin for setting colors in difference mode","description":"Simple yet effective color setting for vim in difference mode.\r\nThe color theme is based on the mgdiff difference tool.","4":"Simple yet effective color setting for vim in difference mode.\r\nThe color theme is based on the mgdiff difference tool.","install_details":"copy the file kamarali_diff.vim into your ~\/.vim\/plugin directory.","5":"copy the file kamarali_diff.vim into your ~\/.vim\/plugin directory.","first_name":"kamarali","6":"kamarali","last_name":"khan","7":"khan","releases":[{"0":"4091","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"kamarali_diff.vim","4":"kamarali_diff.vim","src_id":"18085","5":"18085","creation_date":"1338699248","6":"1338699248"}]},"4089":{"script_id":"4089","0":"4089","script_name":"css3 mod","1":"css3 mod","script_type":"syntax","2":"syntax","summary":"Enhanced version of CSS syntax highlighting script for vim, supports for CSS3","3":"Enhanced version of CSS syntax highlighting script for vim, supports for CSS3","description":"\r\nIntroduction\r\n  \r\nThe script is based on the original css syntax file : http:\/\/fleiner.com\/vim\/syntax\/css.vim ,\r\nand support for CSS3 syntax highlighting .\r\nThis script include many of CSS3 Property,Attribute and Selector ,\r\nand the prefix \" -moz-,-webkit- ,-o-,-ms- \" support ,\r\nand complete the At-rule groups , see the https:\/\/developer.mozilla.org\/en-US\/docs\/CSS\/At-rule .\r\nAlso , it support the beautify CSS feature , you can use it to by the :CSSBeautify command .\r\n\r\nOptions\r\n\r\nAs a optional, \"css_default_sync\" argument can be used for switch the syntax synchronization settings.\r\nBy default, to use \"syn sync minlines=2000\" as setting of synchronization. If you have a slow machine,\r\nso, you can use the following option(to use \"syn sync maxlines=200\"):\r\n\r\nlet g:css_default_sync == 1\r\n\r\nFor the CSSBeautify command :\r\n\r\n\/* Original *\/\r\n\r\nstyle:\r\n\r\nbody{ width:680px ;\r\nbackground-color:#FFF;\r\nbox-shadow: -1px 1px 3px #DDD;\r\npadding: 10px\r\n}\r\na:nth-of-type(2n) \r\n{\r\n  background-color:#FFF!important\r\n}\r\n.class #id{border-radius:0px!important;}\r\n\r\n\/* After the command execution *\/\r\n\r\nstyle:\r\n\r\nbody {\r\nwidth: 680px ;\r\nbackground-color: #FFF ;\r\nbox-shadow: -1px 1px 3px #DDD ;\r\npadding: 10px ;\r\n}\r\na:nth-of-type(2n) {\r\nbackground-color: #FFF !important;\r\n}\r\n.class #id {\r\nborder-radius: 0px !important;\r\n}\r\n\r\nScreenshots: \r\nhttp:\/\/i.imgur.com\/HjD48SP.jpg\r\nhttp:\/\/i.imgur.com\/MBzDyhm.jpg\r\nhttp:\/\/i.imgur.com\/HR2nYl2.jpg\r\n\r\n\r\nGithub repositories:\r\nFirst - https:\/\/github.com\/fremff\/vim-css-syntax\r\nSecond - https:\/\/github.com\/vim-scripts\/css3-mod\r\n\r\n","4":"\r\nIntroduction\r\n  \r\nThe script is based on the original css syntax file : http:\/\/fleiner.com\/vim\/syntax\/css.vim ,\r\nand support for CSS3 syntax highlighting .\r\nThis script include many of CSS3 Property,Attribute and Selector ,\r\nand the prefix \" -moz-,-webkit- ,-o-,-ms- \" support ,\r\nand complete the At-rule groups , see the https:\/\/developer.mozilla.org\/en-US\/docs\/CSS\/At-rule .\r\nAlso , it support the beautify CSS feature , you can use it to by the :CSSBeautify command .\r\n\r\nOptions\r\n\r\nAs a optional, \"css_default_sync\" argument can be used for switch the syntax synchronization settings.\r\nBy default, to use \"syn sync minlines=2000\" as setting of synchronization. If you have a slow machine,\r\nso, you can use the following option(to use \"syn sync maxlines=200\"):\r\n\r\nlet g:css_default_sync == 1\r\n\r\nFor the CSSBeautify command :\r\n\r\n\/* Original *\/\r\n\r\nstyle:\r\n\r\nbody{ width:680px ;\r\nbackground-color:#FFF;\r\nbox-shadow: -1px 1px 3px #DDD;\r\npadding: 10px\r\n}\r\na:nth-of-type(2n) \r\n{\r\n  background-color:#FFF!important\r\n}\r\n.class #id{border-radius:0px!important;}\r\n\r\n\/* After the command execution *\/\r\n\r\nstyle:\r\n\r\nbody {\r\nwidth: 680px ;\r\nbackground-color: #FFF ;\r\nbox-shadow: -1px 1px 3px #DDD ;\r\npadding: 10px ;\r\n}\r\na:nth-of-type(2n) {\r\nbackground-color: #FFF !important;\r\n}\r\n.class #id {\r\nborder-radius: 0px !important;\r\n}\r\n\r\nScreenshots: \r\nhttp:\/\/i.imgur.com\/HjD48SP.jpg\r\nhttp:\/\/i.imgur.com\/MBzDyhm.jpg\r\nhttp:\/\/i.imgur.com\/HR2nYl2.jpg\r\n\r\n\r\nGithub repositories:\r\nFirst - https:\/\/github.com\/fremff\/vim-css-syntax\r\nSecond - https:\/\/github.com\/vim-scripts\/css3-mod\r\n\r\n","install_details":"Put the css.vim to ~\/.vim\/syntax ,or $Vim\/vimfiles\/syntax","5":"Put the css.vim to ~\/.vim\/syntax ,or $Vim\/vimfiles\/syntax","first_name":"fremff","6":"fremff","last_name":"ff","7":"ff","releases":[{"0":"4089","vim_version":"7.0","1":"7.0","script_version":"1.3.0","2":"1.3.0","version_comment":"add a option to switch the syntax sync setting,\r\nadd more properties and it's values,\r\nfix bugs.\r\nmore changes, see the link : https:\/\/github.com\/fremff\/vim-css-syntax\/commits\/master","3":"add a option to switch the syntax sync setting,\r\nadd more properties and it's values,\r\nfix bugs.\r\nmore changes, see the link : https:\/\/github.com\/fremff\/vim-css-syntax\/commits\/master","package":"css.zip","4":"css.zip","src_id":"20069","5":"20069","creation_date":"1368022690","6":"1368022690"},{"0":"4089","vim_version":"7.0","1":"7.0","script_version":"1.2.5","2":"1.2.5","version_comment":"Adjustment part *. Prop, * .Attr items prefix\r\nat-rule gorup fine-tuning and remove some of the items skipnl parameters\r\nFor the cssCharset syntax group,  remove cssCharsetString syntax item, and \r\ncssPseudoClasses syntax cluster changed its name to cssPseudo, and  added the syntax cssPseudoElement item\r\nFixed the bug for the CSSBeautify command, this command should not match that included in the regex () of\r\n\"{\" or\"}\"\r\nContinue to adjust the the syntax highlight file structure","3":"Adjustment part *. Prop, * .Attr items prefix\r\nat-rule gorup fine-tuning and remove some of the items skipnl parameters\r\nFor the cssCharset syntax group,  remove cssCharsetString syntax item, and \r\ncssPseudoClasses syntax cluster changed its name to cssPseudo, and  added the syntax cssPseudoElement item\r\nFixed the bug for the CSSBeautify command, this command should not match that included in the regex () of\r\n\"{\" or\"}\"\r\nContinue to adjust the the syntax highlight file structure","package":"css.zip","4":"css.zip","src_id":"19867","5":"19867","creation_date":"1366476936","6":"1366476936"},{"0":"4089","vim_version":"7.0","1":"7.0","script_version":"1.2.0","2":"1.2.0","version_comment":"This update includes many improvements:\r\nAdjust the syntax file structure\r\nAdd more properties,Attribute and selector\r\nAdd CSS files beautification features, use : CSSBeautify command\r\nBug fixes, etc.","3":"This update includes many improvements:\r\nAdjust the syntax file structure\r\nAdd more properties,Attribute and selector\r\nAdd CSS files beautification features, use : CSSBeautify command\r\nBug fixes, etc.","package":"css.zip","4":"css.zip","src_id":"19837","5":"19837","creation_date":"1366195882","6":"1366195882"},{"0":"4089","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"add a new \"supports\" group,\r\nfixed some bugs ","3":"add a new \"supports\" group,\r\nfixed some bugs ","package":"css.zip","4":"css.zip","src_id":"19444","5":"19444","creation_date":"1359383678","6":"1359383678"},{"0":"4089","vim_version":"7.0","1":"7.0","script_version":"0.98","2":"0.98","version_comment":"Fixed some At-rule groups bugs,\r\nAdd a new At-rule group KeyFrame，\r\nSome minor changes","3":"Fixed some At-rule groups bugs,\r\nAdd a new At-rule group KeyFrame，\r\nSome minor changes","package":"css.zip","4":"css.zip","src_id":"18925","5":"18925","creation_date":"1351599387","6":"1351599387"},{"0":"4089","vim_version":"7.0","1":"7.0","script_version":"0.95","2":"0.95","version_comment":"fixed some bugs，adjust the position of the syntax group，and some minor changes","3":"fixed some bugs，adjust the position of the syntax group，and some minor changes","package":"css.zip","4":"css.zip","src_id":"18848","5":"18848","creation_date":"1350803422","6":"1350803422"},{"0":"4089","vim_version":"7.0","1":"7.0","script_version":"0.91","2":"0.91","version_comment":" New added \"cssDocument\" and \"cssNameSpace\" at-rule groups,\r\nadded some  Attr item,\r\nand some small fixed\r\n\r\nFixed a bug of \"cssNameSpace\" group  ","3":" New added \"cssDocument\" and \"cssNameSpace\" at-rule groups,\r\nadded some  Attr item,\r\nand some small fixed\r\n\r\nFixed a bug of \"cssNameSpace\" group  ","package":"css.zip","4":"css.zip","src_id":"18674","5":"18674","creation_date":"1348410430","6":"1348410430"},{"0":"4089","vim_version":"7.0","1":"7.0","script_version":"0.71","2":"0.71","version_comment":"fixed bugs,adjust the prefix,and added a new highlight group \"cssPseudoElement\"","3":"fixed bugs,adjust the prefix,and added a new highlight group \"cssPseudoElement\"","package":"css.zip","4":"css.zip","src_id":"18561","5":"18561","creation_date":"1347009549","6":"1347009549"},{"0":"4089","vim_version":"7.0","1":"7.0","script_version":"0.50","2":"0.50","version_comment":"A few little fixed ,a many minor changes，and a small amount of prefix change","3":"A few little fixed ,a many minor changes，and a small amount of prefix change","package":"css.zip","4":"css.zip","src_id":"18509","5":"18509","creation_date":"1346183834","6":"1346183834"},{"0":"4089","vim_version":"7.0","1":"7.0","script_version":"0.30","2":"0.30","version_comment":"Added more \"attribute\",and some  \"pseudoclassid\"\r\nSome small fixes","3":"Added more \"attribute\",and some  \"pseudoclassid\"\r\nSome small fixes","package":"css.zip","4":"css.zip","src_id":"18096","5":"18096","creation_date":"1339066606","6":"1339066606"},{"0":"4089","vim_version":"7.0","1":"7.0","script_version":"0.15","2":"0.15","version_comment":"Update a little \"keyword\",\r\nsome minor adjustments","3":"Update a little \"keyword\",\r\nsome minor adjustments","package":"css.zip","4":"css.zip","src_id":"18076","5":"18076","creation_date":"1338596616","6":"1338596616"},{"0":"4089","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"css.zip","4":"css.zip","src_id":"18069","5":"18069","creation_date":"1338490011","6":"1338490011"}]},"4088":{"script_id":"4088","0":"4088","script_name":"taggatron","1":"taggatron","script_type":"utility","2":"utility","summary":"Lightweight tag file manager for use with ctags","3":"Lightweight tag file manager for use with ctags","description":"A simple tag file manager for Vim\r\n------------------------------------------------\r\n\r\nAre you managing your tag files manually? Are you constantly trying to recall the right command line arguments for ctags-exuberant? Would you like a very light tag manager to solve your problems? Look no further.\r\n\r\nTaggatron allows you to set up rules for creating your tag files, based on the language. It separates tag files for different languages (I decided this was the way I wanted to go, as it is neater and easier to maintain), and incorporates the Autotag script by Craig Emery to update tag files incrementally as you edit your files.\r\n\r\nFor information on how to configure and use Taggatron, go to the source code repository on github: https:\/\/github.com\/joonty\/vim-taggatron\r\n","4":"A simple tag file manager for Vim\r\n------------------------------------------------\r\n\r\nAre you managing your tag files manually? Are you constantly trying to recall the right command line arguments for ctags-exuberant? Would you like a very light tag manager to solve your problems? Look no further.\r\n\r\nTaggatron allows you to set up rules for creating your tag files, based on the language. It separates tag files for different languages (I decided this was the way I wanted to go, as it is neater and easier to maintain), and incorporates the Autotag script by Craig Emery to update tag files incrementally as you edit your files.\r\n\r\nFor information on how to configure and use Taggatron, go to the source code repository on github: https:\/\/github.com\/joonty\/vim-taggatron\r\n","install_details":"This is easily installed using Vundle. Just add \"Bundle 'joonty\/vim-phpqa.git'\" to your .vimrc and run \"vim +BundleInstall +qall\". \r\n\r\nOtherwise, the files in each directory in the package should be added to the corresponding directory in your .vim\/ folder.","5":"This is easily installed using Vundle. Just add \"Bundle 'joonty\/vim-phpqa.git'\" to your .vimrc and run \"vim +BundleInstall +qall\". \r\n\r\nOtherwise, the files in each directory in the package should be added to the corresponding directory in your .vim\/ folder.","first_name":"Jon","6":"Jon","last_name":"Cairns","7":"Cairns","releases":[{"0":"4088","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"vim-taggatron.tar.gz","4":"vim-taggatron.tar.gz","src_id":"18059","5":"18059","creation_date":"1338307812","6":"1338307812"}]},"4087":{"script_id":"4087","0":"4087","script_name":"EditPlus","1":"EditPlus","script_type":"color scheme","2":"color scheme","summary":"A color scheme that mimics the standard scheme found in the EditPlus text editor","3":"A color scheme that mimics the standard scheme found in the EditPlus text editor","description":"A color scheme that mimics the standard color scheme found in the EditPlus text editor.\r\n\r\nThis color scheme also fully supports HTML, CSS, TagList and NERDTree\r\n\r\nThis color scheme is for GUI only but will work with 256 color terminals with the CSApprox plugin.\r\n\r\nScreenshot: http:\/\/i.imgur.com\/0wtAz.png","4":"A color scheme that mimics the standard color scheme found in the EditPlus text editor.\r\n\r\nThis color scheme also fully supports HTML, CSS, TagList and NERDTree\r\n\r\nThis color scheme is for GUI only but will work with 256 color terminals with the CSApprox plugin.\r\n\r\nScreenshot: http:\/\/i.imgur.com\/0wtAz.png","install_details":"Just put it in \"~\/.vim\/colors\" or in \"<your vim directory>\\vimfiles\\colors\" on Windows.\r\n\r\nDo \":color editplus\" to apply it. If you want to install it as your default color scheme, just add \"color editplus\" to your vimrc file.","5":"Just put it in \"~\/.vim\/colors\" or in \"<your vim directory>\\vimfiles\\colors\" on Windows.\r\n\r\nDo \":color editplus\" to apply it. If you want to install it as your default color scheme, just add \"color editplus\" to your vimrc file.","first_name":"Gary","6":"Gary","last_name":"Willoughby","7":"Willoughby","releases":[{"0":"4087","vim_version":"7.0","1":"7.0","script_version":"1.4","2":"1.4","version_comment":"Added new CursorColumn highlighting group.","3":"Added new CursorColumn highlighting group.","package":"editplus.vim","4":"editplus.vim","src_id":"18874","5":"18874","creation_date":"1351103324","6":"1351103324"},{"0":"4087","vim_version":"7.0","1":"7.0","script_version":"1.3","2":"1.3","version_comment":"Updated a few colors to make the UI a little more subtle and to make nerdtree a little better looking.","3":"Updated a few colors to make the UI a little more subtle and to make nerdtree a little better looking.","package":"editplus.vim","4":"editplus.vim","src_id":"18802","5":"18802","creation_date":"1350157233","6":"1350157233"},{"0":"4087","vim_version":"7.3","1":"7.3","script_version":"1.2","2":"1.2","version_comment":"Added highlight groups of the CtrlP plugin.","3":"Added highlight groups of the CtrlP plugin.","package":"editplus.vim","4":"editplus.vim","src_id":"18687","5":"18687","creation_date":"1348591776","6":"1348591776"},{"0":"4087","vim_version":"7.3","1":"7.3","script_version":"1.1","2":"1.1","version_comment":"Initial upload","3":"Initial upload","package":"editplus.vim","4":"editplus.vim","src_id":"18037","5":"18037","creation_date":"1338044217","6":"1338044217"}]},"4086":{"script_id":"4086","0":"4086","script_name":"python_fold_compact","1":"python_fold_compact","script_type":"ftplugin","2":"ftplugin","summary":"python fold","3":"python fold","description":"only for use 4 space instead tab python script\r\npreview https:\/\/github.com\/sunsol\/vim_python_fold_compact\/raw\/master\/python_fold_compact_preview.jpg\r\n","4":"only for use 4 space instead tab python script\r\npreview https:\/\/github.com\/sunsol\/vim_python_fold_compact\/raw\/master\/python_fold_compact_preview.jpg\r\n","install_details":"place into \/ftplugin","5":"place into \/ftplugin","first_name":"sunsol","6":"sunsol","last_name":"zn","7":"zn","releases":[{"0":"4086","vim_version":"7.0","1":"7.0","script_version":"0.2","2":"0.2","version_comment":"add foldtext func","3":"add foldtext func","package":"python_fold_compact.vim","4":"python_fold_compact.vim","src_id":"18036","5":"18036","creation_date":"1338041333","6":"1338041333"}]},"4085":{"script_id":"4085","0":"4085","script_name":"OnSyntaxChange","1":"OnSyntaxChange","script_type":"utility","2":"utility","summary":"Generate events when moving onto \/ off a syntax group.","3":"Generate events when moving onto \/ off a syntax group.","description":"DESCRIPTION\r\nThis plugin can set up custom User events similar to the InsertEnter and\r\nInsertLeave events that fire when the cursor moves onto \/ off text that is\r\nmatched by a particular syntax group. You can use a custom :autocmd to\r\nperform an action or change a Vim setting depending on the syntax under the\r\ncursor.\r\n\r\nHOW IT WORKS\r\nThe plugin checks for changes to the syntax group under the cursor whenever\r\nthe cursor changes, and keeps track of the state using the event definition\r\nname. Having many definitions or complex syntaxes may slow down cursor\r\nmovement noticeably, but the plugin takes care that only necessary hooks are\r\ninstalled in the proper scope. So as long as you only have buffer-local\r\ndefinitions, other buffers won't be affected at all.\r\n\r\nSEE ALSO\r\n- With the SyntaxRange.vim plugin (vimscript #4168), you can define regions in\r\n  a buffer that are highlighted with a different syntax (which could then\r\n  trigger this plugin to change buffer options).\r\n\r\nRELATED WORKS\r\n- hookcursormoved (vimscript #2037) allows to call a registered function when\r\n  the syntax group under the cursor has changed, or a syntax group of a\r\n  particular name has been left. It also offers other hooks like change of\r\n  line number and movement into parentheses.\r\n\r\nUSAGE\r\nThe following is an overview; you'll find the details directly in the\r\nimplementation file .vim\/autoload\/OnSyntaxChange.vim.\r\nTo set up User events for a particular syntax group, invoke:\r\n\r\nOnSyntaxChange#Install( name, SyntaxItemPattern, isBufferLocal, mode )\r\n\r\nYou need to give your event definition a name; it is used to differentiate\r\ndifferent setups and is included in the event names that will be generated:\r\n    Syntax{name}Enter{MODE}\r\n    Syntax{name}Leave{MODE}\r\n\r\nThe SyntaxItemPattern is a regular expression that matches the syntax group;\r\nboth the actual and effective names are considered (e.g. in Vimscript,\r\n\"vimLineComment\" is linked to \"Comment\").\r\nAlternatively, you can pass a Funcref that is invoked with an isInsertMode\r\nflag as the first argument and the syntax check position as the second\r\nargument (which is equal to the cursor position except when appending at the\r\nend of a line), and is supposed to return 1 or 0, depending on whether we're\r\ncurrently \"on\" or \"off\" the syntax. This can be used for advanced checking,\r\nbut should in general be avoided for performance reasons.\r\n\r\nEvents can be generated globally for all buffers, or just for a particular\r\nbuffer; use the latter to create events for particular filetypes (via an\r\n:autocmd FileType or in a ~\/.vim\/ftplugin\/{filetype}.vim script).\r\n\r\nThe mode specifies whether the syntax check should only be performed in\r\nnormal, insert, or any of both modes. For example:\r\n    call OnSyntaxChange#Install('Comment', '^Comment$', 0, 'a')\r\n\r\nTo handle the generated events, define one or more :autocmd for the User\r\nevent, matching the event name, e.g.\r\n    autocmd User SyntaxCommentEnterA unsilent echo \"entered comment\"\r\n    autocmd User SyntaxCommentLeaveA unsilent echo \"left comment\"\r\n\r\nEXAMPLE\r\nEnable 'list' when inside string (e.g. to see the difference between <Tab> and\r\n<Space>).\r\nThis should only affect both modes, so mode is \"a\". Let's do this only for C\r\nfiles:\r\n    autocmd FileType c call OnSyntaxChange#Install('CString', 'String$', 1, 'a')\r\n    autocmd FileType c autocmd User SyntaxCStringEnterA setlocal list\r\n    autocmd FileType c autocmd User SyntaxCStringLeaveA setlocal nolist\r\n(Better put these, without the :autocmd, into ~\/.vim\/after\/ftplugin\/c.vim)\r\n(Note: Proper autocmd hygiene, i.e. use of autocmd-groups is recommended.)\r\n\r\n------------------------------------------------------------------------------\r\n\r\nDisable the AutoComplPop plugin (vimscript #1879) when inside a comment.\r\n(Inspired by http:\/\/stackoverflow.com\/questions\/10723499\/)\r\nLet's do this globally. Since the completion only works in insert mode, use\r\nmode \"i\".\r\n    call OnSyntaxChange#Install('Comment', '^Comment$', 0, 'i')\r\n    autocmd User SyntaxCommentEnterI silent! AcpLock\r\n    autocmd User SyntaxCommentLeaveI silent! AcpUnlock\r\nSame for the Neocomplete plugin (https:\/\/github.com\/Shougo\/neocomplete.vim):\r\n    autocmd User SyntaxCommentEnterI silent! NeoCompleteLock\r\n    autocmd User SyntaxCommentLeaveI silent! NeoCompleteUnlock","4":"DESCRIPTION\r\nThis plugin can set up custom User events similar to the InsertEnter and\r\nInsertLeave events that fire when the cursor moves onto \/ off text that is\r\nmatched by a particular syntax group. You can use a custom :autocmd to\r\nperform an action or change a Vim setting depending on the syntax under the\r\ncursor.\r\n\r\nHOW IT WORKS\r\nThe plugin checks for changes to the syntax group under the cursor whenever\r\nthe cursor changes, and keeps track of the state using the event definition\r\nname. Having many definitions or complex syntaxes may slow down cursor\r\nmovement noticeably, but the plugin takes care that only necessary hooks are\r\ninstalled in the proper scope. So as long as you only have buffer-local\r\ndefinitions, other buffers won't be affected at all.\r\n\r\nSEE ALSO\r\n- With the SyntaxRange.vim plugin (vimscript #4168), you can define regions in\r\n  a buffer that are highlighted with a different syntax (which could then\r\n  trigger this plugin to change buffer options).\r\n\r\nRELATED WORKS\r\n- hookcursormoved (vimscript #2037) allows to call a registered function when\r\n  the syntax group under the cursor has changed, or a syntax group of a\r\n  particular name has been left. It also offers other hooks like change of\r\n  line number and movement into parentheses.\r\n\r\nUSAGE\r\nThe following is an overview; you'll find the details directly in the\r\nimplementation file .vim\/autoload\/OnSyntaxChange.vim.\r\nTo set up User events for a particular syntax group, invoke:\r\n\r\nOnSyntaxChange#Install( name, SyntaxItemPattern, isBufferLocal, mode )\r\n\r\nYou need to give your event definition a name; it is used to differentiate\r\ndifferent setups and is included in the event names that will be generated:\r\n    Syntax{name}Enter{MODE}\r\n    Syntax{name}Leave{MODE}\r\n\r\nThe SyntaxItemPattern is a regular expression that matches the syntax group;\r\nboth the actual and effective names are considered (e.g. in Vimscript,\r\n\"vimLineComment\" is linked to \"Comment\").\r\nAlternatively, you can pass a Funcref that is invoked with an isInsertMode\r\nflag as the first argument and the syntax check position as the second\r\nargument (which is equal to the cursor position except when appending at the\r\nend of a line), and is supposed to return 1 or 0, depending on whether we're\r\ncurrently \"on\" or \"off\" the syntax. This can be used for advanced checking,\r\nbut should in general be avoided for performance reasons.\r\n\r\nEvents can be generated globally for all buffers, or just for a particular\r\nbuffer; use the latter to create events for particular filetypes (via an\r\n:autocmd FileType or in a ~\/.vim\/ftplugin\/{filetype}.vim script).\r\n\r\nThe mode specifies whether the syntax check should only be performed in\r\nnormal, insert, or any of both modes. For example:\r\n    call OnSyntaxChange#Install('Comment', '^Comment$', 0, 'a')\r\n\r\nTo handle the generated events, define one or more :autocmd for the User\r\nevent, matching the event name, e.g.\r\n    autocmd User SyntaxCommentEnterA unsilent echo \"entered comment\"\r\n    autocmd User SyntaxCommentLeaveA unsilent echo \"left comment\"\r\n\r\nEXAMPLE\r\nEnable 'list' when inside string (e.g. to see the difference between <Tab> and\r\n<Space>).\r\nThis should only affect both modes, so mode is \"a\". Let's do this only for C\r\nfiles:\r\n    autocmd FileType c call OnSyntaxChange#Install('CString', 'String$', 1, 'a')\r\n    autocmd FileType c autocmd User SyntaxCStringEnterA setlocal list\r\n    autocmd FileType c autocmd User SyntaxCStringLeaveA setlocal nolist\r\n(Better put these, without the :autocmd, into ~\/.vim\/after\/ftplugin\/c.vim)\r\n(Note: Proper autocmd hygiene, i.e. use of autocmd-groups is recommended.)\r\n\r\n------------------------------------------------------------------------------\r\n\r\nDisable the AutoComplPop plugin (vimscript #1879) when inside a comment.\r\n(Inspired by http:\/\/stackoverflow.com\/questions\/10723499\/)\r\nLet's do this globally. Since the completion only works in insert mode, use\r\nmode \"i\".\r\n    call OnSyntaxChange#Install('Comment', '^Comment$', 0, 'i')\r\n    autocmd User SyntaxCommentEnterI silent! AcpLock\r\n    autocmd User SyntaxCommentLeaveI silent! AcpUnlock\r\nSame for the Neocomplete plugin (https:\/\/github.com\/Shougo\/neocomplete.vim):\r\n    autocmd User SyntaxCommentEnterI silent! NeoCompleteLock\r\n    autocmd User SyntaxCommentLeaveI silent! NeoCompleteUnlock","install_details":"INSTALLATION\r\nThe code is hosted in a Git repo at\r\n    https:\/\/github.com\/inkarkat\/vim-OnSyntaxChange\r\nYou can use your favorite plugin manager, or \"git clone\" into a directory used\r\nfor Vim packages. Releases are on the \"stable\" branch, the latest unstable\r\ndevelopment snapshot on \"master\".\r\n\r\nThis script is also packaged as a vimball. If you have the \"gunzip\"\r\ndecompressor in your PATH, simply edit the *.vmb.gz package in Vim; otherwise,\r\ndecompress the archive first, e.g. using WinZip. Inside Vim, install by\r\nsourcing the vimball or via the :UseVimball command.\r\n    vim OnSyntaxChange*.vmb.gz\r\n    :so %\r\nTo uninstall, use the :RmVimball command.\r\n\r\nDEPENDENCIES\r\n- Requires Vim 7.0 or higher.\r\n- Requires the ingo-library.vim plugin (vimscript #4433), version 1.023 or\r\n  higher.","5":"INSTALLATION\r\nThe code is hosted in a Git repo at\r\n    https:\/\/github.com\/inkarkat\/vim-OnSyntaxChange\r\nYou can use your favorite plugin manager, or \"git clone\" into a directory used\r\nfor Vim packages. Releases are on the \"stable\" branch, the latest unstable\r\ndevelopment snapshot on \"master\".\r\n\r\nThis script is also packaged as a vimball. If you have the \"gunzip\"\r\ndecompressor in your PATH, simply edit the *.vmb.gz package in Vim; otherwise,\r\ndecompress the archive first, e.g. using WinZip. Inside Vim, install by\r\nsourcing the vimball or via the :UseVimball command.\r\n    vim OnSyntaxChange*.vmb.gz\r\n    :so %\r\nTo uninstall, use the :RmVimball command.\r\n\r\nDEPENDENCIES\r\n- Requires Vim 7.0 or higher.\r\n- Requires the ingo-library.vim plugin (vimscript #4433), version 1.023 or\r\n  higher.","first_name":"Ingo","6":"Ingo","last_name":"Karkat","7":"Karkat","releases":[{"0":"4085","vim_version":"7.0","1":"7.0","script_version":"1.10","2":"1.10","version_comment":"- ENH: Also support Funcref for a:SyntaxItemPattern to allow advanced syntax\r\n  checking (or skipping syntax queried altogether and instead do a simple\r\n  pattern matching around the cursor position).","3":"- ENH: Also support Funcref for a:SyntaxItemPattern to allow advanced syntax\r\n  checking (or skipping syntax queried altogether and instead do a simple\r\n  pattern matching around the cursor position).","package":"OnSyntaxChange-1.10.vmb.gz","4":"OnSyntaxChange-1.10.vmb.gz","src_id":"28370","5":"28370","creation_date":"1676830833","6":"1676830833"},{"0":"4085","vim_version":"7.0","1":"7.0","script_version":"1.02","2":"1.02","version_comment":"- Add dependency to ingo-library (vimscript #4433). *** You need to separately install ingo-library (vimscript #4433) version 1.023 (or higher)! ***","3":"- Add dependency to ingo-library (vimscript #4433). *** You need to separately install ingo-library (vimscript #4433) version 1.023 (or higher)! ***","package":"OnSyntaxChange-1.02.vmb.gz","4":"OnSyntaxChange-1.02.vmb.gz","src_id":"26256","5":"26256","creation_date":"1541278455","6":"1541278455"},{"0":"4085","vim_version":"7.0","1":"7.0","script_version":"1.01","2":"1.01","version_comment":"Do not trigger modeline processing when triggering.","3":"Do not trigger modeline processing when triggering.","package":"OnSyntaxChange-1.01.vmb.gz","4":"OnSyntaxChange-1.01.vmb.gz","src_id":"19406","5":"19406","creation_date":"1358754377","6":"1358754377"},{"0":"4085","vim_version":"7.0","1":"7.0","script_version":"1.00","2":"1.00","version_comment":"Initial upload","3":"Initial upload","package":"OnSyntaxChange.vba.gz","4":"OnSyntaxChange.vba.gz","src_id":"18034","5":"18034","creation_date":"1337977233","6":"1337977233"}]},"4084":{"script_id":"4084","0":"4084","script_name":"cst","1":"cst","script_type":"syntax","2":"syntax","summary":"CodeSmith syntax","3":"CodeSmith syntax","description":"This is a start to get correct syntax coloring for CodeSmith C# templates (*.cst) files.","4":"This is a start to get correct syntax coloring for CodeSmith C# templates (*.cst) files.","install_details":"Copy the given cst.vim to your vim\/syntax folder.\r\n\r\nAdd to your _vimrc the following line:\r\n\r\nautocmd BufNewFile,BufRead *.cst setfiletype cst\r\n\r\nDone. All *.cst files should now be colored like CS files but with recognized CodeSmith tags.","5":"Copy the given cst.vim to your vim\/syntax folder.\r\n\r\nAdd to your _vimrc the following line:\r\n\r\nautocmd BufNewFile,BufRead *.cst setfiletype cst\r\n\r\nDone. All *.cst files should now be colored like CS files but with recognized CodeSmith tags.","first_name":"Werner","6":"Werner","last_name":"Beroux","7":"Beroux","releases":[{"0":"4084","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"cst.vim","4":"cst.vim","src_id":"18027","5":"18027","creation_date":"1337858282","6":"1337858282"}]},"4083":{"script_id":"4083","0":"4083","script_name":"php-cs-fixer","1":"php-cs-fixer","script_type":"utility","2":"utility","summary":"Integrate php-cs-fixer created by fabpot.","3":"Integrate php-cs-fixer created by fabpot.","description":"Look at https:\/\/github.com\/stephpy\/vim-php-cs-fixer","4":"Look at https:\/\/github.com\/stephpy\/vim-php-cs-fixer","install_details":"Look at https:\/\/github.com\/stephpy\/vim-php-cs-fixer","5":"Look at https:\/\/github.com\/stephpy\/vim-php-cs-fixer","first_name":"St\u00c3\u00a9phane","6":"St\u00c3\u00a9phane","last_name":"PY","7":"PY","releases":[{"0":"4083","vim_version":"7.0","1":"7.0","script_version":"1.0.0","2":"1.0.0","version_comment":"Initial upload","3":"Initial upload","package":"php-cs-fixer.zip","4":"php-cs-fixer.zip","src_id":"18025","5":"18025","creation_date":"1337849509","6":"1337849509"}]},"4082":{"script_id":"4082","0":"4082","script_name":"cscope.vim","1":"cscope.vim","script_type":"utility","2":"utility","summary":"create\/update\/connect cscope database smartly.","3":"create\/update\/connect cscope database smartly.","description":"# Introduction\r\nCscove(new name for this plugin, since cscope.vim is used too widely.) is a\r\nsmart cscope helper for vim.\r\n\r\nIt will try to find a proper cscope database for current file, then connect to\r\nit. If there is no proper cscope database for current file, you are prompted to\r\nspecify a folder with a string like --\r\n\r\n    Can not find proper cscope db, please input a path to create cscope db for.\r\n\r\nThen the plugin will create cscope database for you, connect to it, and find\r\nwhat you want. The found result will be listed in a location list window. Next\r\ntime when you open the same file or other file that the cscope database can be\r\nused for, the plugin will connect to the cscope database automatically. You\r\nneed not take care of anything about cscope database.\r\n\r\nWhen you have a file edited\/added in those folders for which cscope databases\r\nhave been created, cscove will automatically update the corresponding database.\r\n\r\nCscove frees you from creating\/connecting\/updating cscope database, let you\r\nfocus on code browsing.\r\n\r\n# Example settings\r\nThe default key mappings has been removed from the plugin itself, since users\r\nmay prefer different choices.\r\nSo to use the plugin, you must define your own key mappings first.\r\n\r\nBelow is the minimum key mappings.\r\n\r\n    nnoremap <leader>fa :call cscope#findInteractive(expand('<cword>'))<CR>\r\n    nnoremap <leader>l :call ToggleLocationList()<CR>\r\n\r\nSome optional key mappings to search directly.\r\n\r\n    \" s: Find this C symbol\r\n    nnoremap  <leader>fs :call cscope#find('s', expand('<cword>'))<CR>\r\n    \" g: Find this definition\r\n    nnoremap  <leader>fg :call cscope#find('g', expand('<cword>'))<CR>\r\n    \" d: Find functions called by this function\r\n    nnoremap  <leader>fd :call cscope#find('d', expand('<cword>'))<CR>\r\n    \" c: Find functions calling this function\r\n    nnoremap  <leader>fc :call cscope#find('c', expand('<cword>'))<CR>\r\n    \" t: Find this text string\r\n    nnoremap  <leader>ft :call cscope#find('t', expand('<cword>'))<CR>\r\n    \" e: Find this egrep pattern\r\n    nnoremap  <leader>fe :call cscope#find('e', expand('<cword>'))<CR>\r\n    \" f: Find this file\r\n    nnoremap  <leader>ff :call cscope#find('f', expand('<cword>'))<CR>\r\n    \" i: Find files #including this file\r\n    nnoremap  <leader>fi :call cscope#find('i', expand('<cword>'))<CR>\r\n\r\n# Screencast\r\nPlease note that line number changes in location list after file saved.\r\n![cscove.vim](https:\/\/brookhong.github.io\/assets\/images\/cscove.gif)\r\n","4":"# Introduction\r\nCscove(new name for this plugin, since cscope.vim is used too widely.) is a\r\nsmart cscope helper for vim.\r\n\r\nIt will try to find a proper cscope database for current file, then connect to\r\nit. If there is no proper cscope database for current file, you are prompted to\r\nspecify a folder with a string like --\r\n\r\n    Can not find proper cscope db, please input a path to create cscope db for.\r\n\r\nThen the plugin will create cscope database for you, connect to it, and find\r\nwhat you want. The found result will be listed in a location list window. Next\r\ntime when you open the same file or other file that the cscope database can be\r\nused for, the plugin will connect to the cscope database automatically. You\r\nneed not take care of anything about cscope database.\r\n\r\nWhen you have a file edited\/added in those folders for which cscope databases\r\nhave been created, cscove will automatically update the corresponding database.\r\n\r\nCscove frees you from creating\/connecting\/updating cscope database, let you\r\nfocus on code browsing.\r\n\r\n# Example settings\r\nThe default key mappings has been removed from the plugin itself, since users\r\nmay prefer different choices.\r\nSo to use the plugin, you must define your own key mappings first.\r\n\r\nBelow is the minimum key mappings.\r\n\r\n    nnoremap <leader>fa :call cscope#findInteractive(expand('<cword>'))<CR>\r\n    nnoremap <leader>l :call ToggleLocationList()<CR>\r\n\r\nSome optional key mappings to search directly.\r\n\r\n    \" s: Find this C symbol\r\n    nnoremap  <leader>fs :call cscope#find('s', expand('<cword>'))<CR>\r\n    \" g: Find this definition\r\n    nnoremap  <leader>fg :call cscope#find('g', expand('<cword>'))<CR>\r\n    \" d: Find functions called by this function\r\n    nnoremap  <leader>fd :call cscope#find('d', expand('<cword>'))<CR>\r\n    \" c: Find functions calling this function\r\n    nnoremap  <leader>fc :call cscope#find('c', expand('<cword>'))<CR>\r\n    \" t: Find this text string\r\n    nnoremap  <leader>ft :call cscope#find('t', expand('<cword>'))<CR>\r\n    \" e: Find this egrep pattern\r\n    nnoremap  <leader>fe :call cscope#find('e', expand('<cword>'))<CR>\r\n    \" f: Find this file\r\n    nnoremap  <leader>ff :call cscope#find('f', expand('<cword>'))<CR>\r\n    \" i: Find files #including this file\r\n    nnoremap  <leader>fi :call cscope#find('i', expand('<cword>'))<CR>\r\n\r\n# Screencast\r\nPlease note that line number changes in location list after file saved.\r\n![cscove.vim](https:\/\/brookhong.github.io\/assets\/images\/cscove.gif)\r\n","install_details":"Just unzip the zip file to your VIM file path, usually to be ~\/.vim. \r\n\r\nor \r\n\r\nBundle 'brookhong\/cscope.vim'","5":"Just unzip the zip file to your VIM file path, usually to be ~\/.vim. \r\n\r\nor \r\n\r\nBundle 'brookhong\/cscope.vim'","first_name":"brook","6":"brook","last_name":"hong","7":"hong","releases":[{"0":"4082","vim_version":"7.2","1":"7.2","script_version":"2.0","2":"2.0","version_comment":"1. auto update cscope database after files edited\/added\r\n2. add an interactive interfce: cscope#findInteractive\r\n3. remove default key mappings\r\n4. remove unnecessary commands\r\n5. update help doc","3":"1. auto update cscope database after files edited\/added\r\n2. add an interactive interfce: cscope#findInteractive\r\n3. remove default key mappings\r\n4. remove unnecessary commands\r\n5. update help doc","package":"cscope.zip","4":"cscope.zip","src_id":"23086","5":"23086","creation_date":"1427097477","6":"1427097477"},{"0":"4082","vim_version":"7.2","1":"7.2","script_version":"1.01","2":"1.01","version_comment":"minor fix of CscopeFind","3":"minor fix of CscopeFind","package":"cscope.zip","4":"cscope.zip","src_id":"18067","5":"18067","creation_date":"1338437188","6":"1338437188"},{"0":"4082","vim_version":"7.2","1":"7.2","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"cscope.zip","4":"cscope.zip","src_id":"18020","5":"18020","creation_date":"1337779513","6":"1337779513"}]},"4081":{"script_id":"4081","0":"4081","script_name":"EscapeBchars","1":"EscapeBchars","script_type":"utility","2":"utility","summary":"Function to escape the characters used in comments.","3":"Function to escape the characters used in comments.","description":"This plugin enables the escape of comment characters (mainly in FoldImproved and MapComments (coming soon)) in function's strings.","4":"This plugin enables the escape of comment characters (mainly in FoldImproved and MapComments (coming soon)) in function's strings.","install_details":"Put the EscapeBchars_VERSION.tar.gz into your .vim directory then\r\ntar xzf EscapeBchars_VERSION.tar.gz","5":"Put the EscapeBchars_VERSION.tar.gz into your .vim directory then\r\ntar xzf EscapeBchars_VERSION.tar.gz","first_name":"Ga\u00c3\u00abl","6":"Ga\u00c3\u00abl","last_name":"Induni","7":"Induni","releases":[{"0":"4081","vim_version":"7.0","1":"7.0","script_version":"0.2","2":"0.2","version_comment":"Enabled GetLatestVimScript","3":"Enabled GetLatestVimScript","package":"EscapeBchars_0_2.tar.gz","4":"EscapeBchars_0_2.tar.gz","src_id":"18017","5":"18017","creation_date":"1337611546","6":"1337611546"},{"0":"4081","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"EscapeBchars_0_1.tar.gz","4":"EscapeBchars_0_1.tar.gz","src_id":"18016","5":"18016","creation_date":"1337611472","6":"1337611472"}]},"4080":{"script_id":"4080","0":"4080","script_name":"HgCi","1":"HgCi","script_type":"utility","2":"utility","summary":"Script to be used with autocmd bufwritepost when a commit is needed.","3":"Script to be used with autocmd bufwritepost when a commit is needed.","description":"This script is intended to be used with autocmd bufwritepost when a mercurial commit is needed after each change in the file.","4":"This script is intended to be used with autocmd bufwritepost when a mercurial commit is needed after each change in the file.","install_details":"put the HgCi_VERSION.tar.gz into your .vim directory then\r\ntar xzf HgCi_VERSION.tar.gz","5":"put the HgCi_VERSION.tar.gz into your .vim directory then\r\ntar xzf HgCi_VERSION.tar.gz","first_name":"Ga\u00c3\u00abl","6":"Ga\u00c3\u00abl","last_name":"Induni","7":"Induni","releases":[{"0":"4080","vim_version":"7.0","1":"7.0","script_version":"0.2","2":"0.2","version_comment":"Enabled GetLatestVimScript","3":"Enabled GetLatestVimScript","package":"HgCi_0_2.tar.gz","4":"HgCi_0_2.tar.gz","src_id":"18011","5":"18011","creation_date":"1337609500","6":"1337609500"},{"0":"4080","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"HgCi_0_1.tar.gz","4":"HgCi_0_1.tar.gz","src_id":"18010","5":"18010","creation_date":"1337609312","6":"1337609312"}]},"4079":{"script_id":"4079","0":"4079","script_name":"sourcebeautify.vim","1":"sourcebeautify.vim","script_type":"utility","2":"utility","summary":"make your source code pretty in vim","3":"make your source code pretty in vim","description":"Website: https:\/\/github.com\/michalliu\/sourcebeautify.vim\r\n\r\nThis script can beautify html,css,javascript,json files\r\n\r\nTo support json file, your need add following code to your vimrc\r\nau BufRead,BufNewFile *.json setf json\r\n\r\nI suggest to use json.vim http:\/\/www.vim.org\/scripts\/script.php?script_id=1945\r\n\r\n\r\nJust hit\r\n\r\n<Leader>sb\r\n\r\nto see what happens","4":"Website: https:\/\/github.com\/michalliu\/sourcebeautify.vim\r\n\r\nThis script can beautify html,css,javascript,json files\r\n\r\nTo support json file, your need add following code to your vimrc\r\nau BufRead,BufNewFile *.json setf json\r\n\r\nI suggest to use json.vim http:\/\/www.vim.org\/scripts\/script.php?script_id=1945\r\n\r\n\r\nJust hit\r\n\r\n<Leader>sb\r\n\r\nto see what happens","install_details":"this plugin requires jsruntime http:\/\/www.vim.org\/scripts\/script.php?script_id=4050 and jsoncodecs http:\/\/www.vim.org\/scripts\/script.php?script_id=4056 installed\r\n\r\nput sourcebeautify to $VIM\/plugin\r\n","5":"this plugin requires jsruntime http:\/\/www.vim.org\/scripts\/script.php?script_id=4050 and jsoncodecs http:\/\/www.vim.org\/scripts\/script.php?script_id=4056 installed\r\n\r\nput sourcebeautify to $VIM\/plugin\r\n","first_name":"yf","6":"yf","last_name":"liu","7":"liu","releases":[{"0":"4079","vim_version":"7.0","1":"7.0","script_version":"2.0","2":"2.0","version_comment":"fix css beautify media query","3":"fix css beautify media query","package":"sourcebeautify.zip","4":"sourcebeautify.zip","src_id":"22052","5":"22052","creation_date":"1403070017","6":"1403070017"},{"0":"4079","vim_version":"7.0","1":"7.0","script_version":"1.9","2":"1.9","version_comment":"Using linux line endings","3":"Using linux line endings","package":"sourcebeautify.zip","4":"sourcebeautify.zip","src_id":"22041","5":"22041","creation_date":"1403009761","6":"1403009761"},{"0":"4079","vim_version":"7.0","1":"7.0","script_version":"1.8","2":"1.8","version_comment":"supports beautify SQL,XML files","3":"supports beautify SQL,XML files","package":"sourcebeautify.zip","4":"sourcebeautify.zip","src_id":"22035","5":"22035","creation_date":"1402949861","6":"1402949861"},{"0":"4079","vim_version":"7.0","1":"7.0","script_version":"1.3","2":"1.3","version_comment":"beautify JSON bug fix ( jsonlint issue 22 )","3":"beautify JSON bug fix ( jsonlint issue 22 )","package":"sourcebeautify.zip","4":"sourcebeautify.zip","src_id":"18058","5":"18058","creation_date":"1338305182","6":"1338305182"},{"0":"4079","vim_version":"7.0","1":"7.0","script_version":"1.2","2":"1.2","version_comment":"switch to use linux line ending","3":"switch to use linux line ending","package":"sourcebeautify.zip","4":"sourcebeautify.zip","src_id":"18047","5":"18047","creation_date":"1338121315","6":"1338121315"},{"0":"4079","vim_version":"7.0","1":"7.0","script_version":"1.1","2":"1.1","version_comment":"add beautifier and error checker for json file which is powered by jsonlint https:\/\/github.com\/zaach\/jsonlint","3":"add beautifier and error checker for json file which is powered by jsonlint https:\/\/github.com\/zaach\/jsonlint","package":"sourcebeautify.zip","4":"sourcebeautify.zip","src_id":"18039","5":"18039","creation_date":"1338056652","6":"1338056652"},{"0":"4079","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"sourcebeautify.zip","4":"sourcebeautify.zip","src_id":"18007","5":"18007","creation_date":"1337595888","6":"1337595888"}]},"4078":{"script_id":"4078","0":"4078","script_name":"jshint.vim","1":"jshint.vim","script_type":"utility","2":"utility","summary":"JSHint Integration","3":"JSHint Integration","description":"jshint.vim facilitates tight integration between JSHint and Vim.\r\n\r\nJavaScript files are automatically passed through JSHint when a buffer is saved, placing any warnings in the quickfix window for easy navigation to the source of the warning. To achieve acceptable performance, Google's V8 Engine is used for JavaScript execution.\r\n\r\nhttps:\/\/github.com\/joestelmach\/jshint.vim","4":"jshint.vim facilitates tight integration between JSHint and Vim.\r\n\r\nJavaScript files are automatically passed through JSHint when a buffer is saved, placing any warnings in the quickfix window for easy navigation to the source of the warning. To achieve acceptable performance, Google's V8 Engine is used for JavaScript execution.\r\n\r\nhttps:\/\/github.com\/joestelmach\/jshint.vim","install_details":"","5":"","first_name":"Joe","6":"Joe","last_name":"Stelmach","7":"Stelmach","releases":[{"0":"4078","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"jshint.vim.zip","4":"jshint.vim.zip","src_id":"17996","5":"17996","creation_date":"1337464099","6":"1337464099"}]},"4077":{"script_id":"4077","0":"4077","script_name":"gprof.vim","1":"gprof.vim","script_type":"ftplugin","2":"ftplugin","summary":"A file type plugin for gprof (GNU profiler) output ","3":"A file type plugin for gprof (GNU profiler) output ","description":"This is a filetype plugin for gprof output files (GNU profiler). It provides a mapping to facilitate navigation in gprof files as well as syntax highlighting of gprof output.\r\n\r\nScreencast demo: http:\/\/shelr.tv\/records\/4fb8d6739660807d3d00000a\r\nScreenshot: http:\/\/dominique.pelle.free.fr\/pic\/ft_gprof.png\r\n\r\nGprof output files have no specific extension. To recognize the file type, you will need to explicitly set the file type with the Ex command \":set filetype gprof\".  For example, to look at the gprof output when profiling Vim, you can use:\r\n\r\n  $ gprof vim gmon.out | vim - -c 'setfiletype gprof'\r\n\r\nAlternatively, you can also add the following lines into your $VIMRUNTIME\/scripts.vim to automatically recognize the gprof file type when reading from stdin: >\r\n\r\n   \" Gprof (gnu profiler)\r\n   elseif s:line1 == 'Flat profile:' \r\n   \\   && s:line2 == '' \r\n   \\   && s:line3 =~ '^Each sample counts as .* seconds.$'\r\n     set ft=gprof\r\n \r\nVim should then figure the gprof file type automatically when using:\r\n\r\n  $ gprof vim gmon.out | vim -\r\n\r\nGprof output contains a flat profile section and a call graph section. Analyzing the output of gprof often requires jumping back in forth in the gprof output. This can be cumbersome. The plugin makes it easier. When the cursor is located in a line in the gprof flat profile or in a line in the call graph, pressing CTRL-] jumps to the corresponding function in the call graph. The jump is remembered in the jumplist so pressing CTRL-I jumps back to the position prior to pressing CTRL-].\r\n\r\nFor further information about the GNU profiler, see:\r\n\r\n  ftp:\/\/ftp.gnu.org\/old-gnu\/Manuals\/gprof-2.9.1\/html_mono\/gprof.html","4":"This is a filetype plugin for gprof output files (GNU profiler). It provides a mapping to facilitate navigation in gprof files as well as syntax highlighting of gprof output.\r\n\r\nScreencast demo: http:\/\/shelr.tv\/records\/4fb8d6739660807d3d00000a\r\nScreenshot: http:\/\/dominique.pelle.free.fr\/pic\/ft_gprof.png\r\n\r\nGprof output files have no specific extension. To recognize the file type, you will need to explicitly set the file type with the Ex command \":set filetype gprof\".  For example, to look at the gprof output when profiling Vim, you can use:\r\n\r\n  $ gprof vim gmon.out | vim - -c 'setfiletype gprof'\r\n\r\nAlternatively, you can also add the following lines into your $VIMRUNTIME\/scripts.vim to automatically recognize the gprof file type when reading from stdin: >\r\n\r\n   \" Gprof (gnu profiler)\r\n   elseif s:line1 == 'Flat profile:' \r\n   \\   && s:line2 == '' \r\n   \\   && s:line3 =~ '^Each sample counts as .* seconds.$'\r\n     set ft=gprof\r\n \r\nVim should then figure the gprof file type automatically when using:\r\n\r\n  $ gprof vim gmon.out | vim -\r\n\r\nGprof output contains a flat profile section and a call graph section. Analyzing the output of gprof often requires jumping back in forth in the gprof output. This can be cumbersome. The plugin makes it easier. When the cursor is located in a line in the gprof flat profile or in a line in the call graph, pressing CTRL-] jumps to the corresponding function in the call graph. The jump is remembered in the jumplist so pressing CTRL-I jumps back to the position prior to pressing CTRL-].\r\n\r\nFor further information about the GNU profiler, see:\r\n\r\n  ftp:\/\/ftp.gnu.org\/old-gnu\/Manuals\/gprof-2.9.1\/html_mono\/gprof.html","install_details":"Install the plugin with:\r\n\r\n  $ mkdir ~\/.vim\r\n  $ cd ~\/.vim\r\n  $ unzip \/path-to\/ft_gprof.zip\r\n  $ vim -c 'helptags ~\/.vim\/doc'","5":"Install the plugin with:\r\n\r\n  $ mkdir ~\/.vim\r\n  $ cd ~\/.vim\r\n  $ unzip \/path-to\/ft_gprof.zip\r\n  $ vim -c 'helptags ~\/.vim\/doc'","first_name":"Dominique","6":"Dominique","last_name":"Pell\u00c3\u00a9","7":"Pell\u00c3\u00a9","releases":[{"0":"4077","vim_version":"6.0","1":"6.0","script_version":"0.4","2":"0.4","version_comment":"- added link to screencast demo http:\/\/shelr.tv\/records\/4fb8d6739660807d3d00000a","3":"- added link to screencast demo http:\/\/shelr.tv\/records\/4fb8d6739660807d3d00000a","package":"ft_gprof.zip","4":"ft_gprof.zip","src_id":"18000","5":"18000","creation_date":"1337514074","6":"1337514074"},{"0":"4077","vim_version":"6.0","1":"6.0","script_version":"0.3","2":"0.3","version_comment":"- huge speed up of syntax highlighting\r\n- fixes for syntax highlighting\r\n- fixed error when loading 2 gprof files","3":"- huge speed up of syntax highlighting\r\n- fixes for syntax highlighting\r\n- fixed error when loading 2 gprof files","package":"ft_gprof.zip","4":"ft_gprof.zip","src_id":"17999","5":"17999","creation_date":"1337503477","6":"1337503477"},{"0":"4077","vim_version":"6.0","1":"6.0","script_version":"0.2","2":"0.2","version_comment":"- fixes for c++: function names can contain * [ ] . which messed up pattern matching when pressing CTRL-]\r\n- fixes in syntax highlighting\r\n- jumplist now works as expected (can press CTRL-I after CTRL-])","3":"- fixes for c++: function names can contain * [ ] . which messed up pattern matching when pressing CTRL-]\r\n- fixes in syntax highlighting\r\n- jumplist now works as expected (can press CTRL-I after CTRL-])","package":"ft_gprof.zip","4":"ft_gprof.zip","src_id":"17997","5":"17997","creation_date":"1337468200","6":"1337468200"},{"0":"4077","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"ft_gprof.zip","4":"ft_gprof.zip","src_id":"17994","5":"17994","creation_date":"1337430355","6":"1337430355"}]},"4076":{"script_id":"4076","0":"4076","script_name":"vmark.vim: Visual Bookmarking","1":"vmark.vim: Visual Bookmarking","script_type":"utility","2":"utility","summary":"Toggle visual bookmarking and jump through bookmarks","3":"Toggle visual bookmarking and jump through bookmarks","description":"Usage:\r\n   Normal Mode\r\n     mm     Toggle visual bookmark current line\r\n     ma     Remove all bookmarks\r\n     mn     Move to next bookmark below current line.  Will wrap around at end.\r\n     <F2>   Same as above (mn)\r\n     mp     Move to previous bookmark above current line.  Will wrap around at top.\r\n     <F3>   Same as above (mp)\r\n\r\nConfiguration:\r\n     b:vm_maxmarks - Max number of bookmarks allowed in a buffer\r\n     b:vm_guifg    - Foreground color for bookmarked line in GVIM\r\n     b:vm_guibg    - Background color for bookmarked line in GVIM\r\n     b:vm_ctermfg  - Foreground color for bookmarked line in VIM\r\n     b:vm_ctermbg  - Background color for bookmarked line in VIM\r\n\r\nLimitation:\r\n   If syntax highlighting based on keywords is turned on and the line being bookmarked starts with a keyword, the keyword may not be highlighted but the rest of the line after the keyword should be highlighted normally.\r\n\r\nAcknowledgement:\r\n   Took cues from Amit Sethi's highlight.vim (http:\/\/www.vim.org\/scripts\/script.php?script_id=1599)","4":"Usage:\r\n   Normal Mode\r\n     mm     Toggle visual bookmark current line\r\n     ma     Remove all bookmarks\r\n     mn     Move to next bookmark below current line.  Will wrap around at end.\r\n     <F2>   Same as above (mn)\r\n     mp     Move to previous bookmark above current line.  Will wrap around at top.\r\n     <F3>   Same as above (mp)\r\n\r\nConfiguration:\r\n     b:vm_maxmarks - Max number of bookmarks allowed in a buffer\r\n     b:vm_guifg    - Foreground color for bookmarked line in GVIM\r\n     b:vm_guibg    - Background color for bookmarked line in GVIM\r\n     b:vm_ctermfg  - Foreground color for bookmarked line in VIM\r\n     b:vm_ctermbg  - Background color for bookmarked line in VIM\r\n\r\nLimitation:\r\n   If syntax highlighting based on keywords is turned on and the line being bookmarked starts with a keyword, the keyword may not be highlighted but the rest of the line after the keyword should be highlighted normally.\r\n\r\nAcknowledgement:\r\n   Took cues from Amit Sethi's highlight.vim (http:\/\/www.vim.org\/scripts\/script.php?script_id=1599)","install_details":"Copy vmark.vim to .vim\/plugin directory","5":"Copy vmark.vim to .vim\/plugin directory","first_name":"Michael","6":"Michael","last_name":"Zhou","7":"Zhou","releases":[{"0":"4076","vim_version":"6.0","1":"6.0","script_version":"1.3","2":"1.3","version_comment":"Merged key mappings and other changes from serpent7776.  The plugin can also be accessed from https:\/\/github.com\/michaelzhou999\/vmark","3":"Merged key mappings and other changes from serpent7776.  The plugin can also be accessed from https:\/\/github.com\/michaelzhou999\/vmark","package":"vmark.vim","4":"vmark.vim","src_id":"21778","5":"21778","creation_date":"1397592130","6":"1397592130"},{"0":"4076","vim_version":"6.0","1":"6.0","script_version":"1.2","2":"1.2","version_comment":"Added an autocmd to highlight all marked lines.  This fixed the issue where highlights are lost when a previous buffer is reloaded into vim\/gvim.","3":"Added an autocmd to highlight all marked lines.  This fixed the issue where highlights are lost when a previous buffer is reloaded into vim\/gvim.","package":"vmark.vim","4":"vmark.vim","src_id":"18122","5":"18122","creation_date":"1339621744","6":"1339621744"},{"0":"4076","vim_version":"7.0","1":"7.0","script_version":"1.1","2":"1.1","version_comment":"Fixed undefined variables defect for multiple buffers.","3":"Fixed undefined variables defect for multiple buffers.","package":"vmark.vim","4":"vmark.vim","src_id":"17995","5":"17995","creation_date":"1337434897","6":"1337434897"},{"0":"4076","vim_version":"7.0","1":"7.0","script_version":"1","2":"1","version_comment":"Initial upload","3":"Initial upload","package":"vmark.vim","4":"vmark.vim","src_id":"17993","5":"17993","creation_date":"1337402317","6":"1337402317"}]},"4075":{"script_id":"4075","0":"4075","script_name":"burnttoast256","1":"burnttoast256","script_type":"color scheme","2":"color scheme","summary":"A dark color scheme for 256-color terminals that I find easily readable.","3":"A dark color scheme for 256-color terminals that I find easily readable.","description":"Github: https:\/\/github.com\/quantum-omega\/vim-burnttoast256\r\n\r\nThis is the color theme I made for myself as I prefer to work on a dark background, namely black, without text that is too bright while still keeping a good contrast.  I based it heavily on http:\/\/www.vim.org\/scripts\/script.php?script_id=2140 and if you don't like my scheme you might like his. Check it out.\r\n\r\nIt includes colors for the normal text, the cursor and cursor line and column, search, status line, selection, line numbers, etc., as well as colors for syntax highlighting, diff mode, and some others.\r\n\r\nThe color scheme should be exactly the same in gvim but hasn't been tested for readability in gvim recently. Requires version 7.3+, as it has colors for \"CursorLineNr\", but it probably will work on previous versions without any problems.\r\n","4":"Github: https:\/\/github.com\/quantum-omega\/vim-burnttoast256\r\n\r\nThis is the color theme I made for myself as I prefer to work on a dark background, namely black, without text that is too bright while still keeping a good contrast.  I based it heavily on http:\/\/www.vim.org\/scripts\/script.php?script_id=2140 and if you don't like my scheme you might like his. Check it out.\r\n\r\nIt includes colors for the normal text, the cursor and cursor line and column, search, status line, selection, line numbers, etc., as well as colors for syntax highlighting, diff mode, and some others.\r\n\r\nThe color scheme should be exactly the same in gvim but hasn't been tested for readability in gvim recently. Requires version 7.3+, as it has colors for \"CursorLineNr\", but it probably will work on previous versions without any problems.\r\n","install_details":"Manual\r\n====\r\nTo install, just put the file `colors\/burntoast256.vim` in your `~\/.vim\/colors` folder and add to your .vimrc:\r\n    colorscheme burnttoast256\r\n\r\nVundle\r\n====\r\nAfter `call vundle#begin()`, place:\r\n\r\n    Plugin 'quantum-omega\/vim-burnttoast256', { 'name': 'burnttoast256' }\r\n\r\nAfter `call vundle#end()`, place:\r\n\r\n    colorscheme burnttoast256\r\n\r\nIn Vim, run:\r\n\r\n    :PluginInstall","5":"Manual\r\n====\r\nTo install, just put the file `colors\/burntoast256.vim` in your `~\/.vim\/colors` folder and add to your .vimrc:\r\n    colorscheme burnttoast256\r\n\r\nVundle\r\n====\r\nAfter `call vundle#begin()`, place:\r\n\r\n    Plugin 'quantum-omega\/vim-burnttoast256', { 'name': 'burnttoast256' }\r\n\r\nAfter `call vundle#end()`, place:\r\n\r\n    colorscheme burnttoast256\r\n\r\nIn Vim, run:\r\n\r\n    :PluginInstall","first_name":"Francois","6":"Francois","last_name":"Labelle","7":"Labelle","releases":[{"0":"4075","vim_version":"7.0","1":"7.0","script_version":"1.4","2":"1.4","version_comment":"Fixes a few inconsistencies between terminal and GUI colors.","3":"Fixes a few inconsistencies between terminal and GUI colors.","package":"vim-burnttoast256-1.4.zip","4":"vim-burnttoast256-1.4.zip","src_id":"27401","5":"27401","creation_date":"1607740015","6":"1607740015"},{"0":"4075","vim_version":"7.3","1":"7.3","script_version":"1.3","2":"1.3","version_comment":"Small fixes, vundle-compatible","3":"Small fixes, vundle-compatible","package":"vim-burnttoast256-1.3.zip","4":"vim-burnttoast256-1.3.zip","src_id":"27372","5":"27372","creation_date":"1605590615","6":"1605590615"},{"0":"4075","vim_version":"7.3","1":"7.3","script_version":"1.2","2":"1.2","version_comment":"Initial upload","3":"Initial upload","package":"burnttoast256.vim","4":"burnttoast256.vim","src_id":"17991","5":"17991","creation_date":"1337348954","6":"1337348954"}]},"4074":{"script_id":"4074","0":"4074","script_name":"Xdebug","1":"Xdebug","script_type":"utility","2":"utility","summary":"An awesome debugging client for Vim, Xdebug and PHP","3":"An awesome debugging client for Vim, Xdebug and PHP","description":"======================================================================================================================\r\n*NOTICE:* This plugin has been superseded by my newer multi-language debugger client, Vdebug. I strongly recommend using that one instead: vimscript #4170\r\n======================================================================================================================\r\n\r\nThis is YET another version of the DBGP client script that Seung Woo Shin created (see http:\/\/www.vim.org\/scripts\/script.php?script_id=1152). The reason I've added this as a new script is because I've added enough new features to warrant it. Here's a few of the best:\r\n\r\n- The debugger session opens in a new tab, so that your carefully configured windows don't get messed up. When you end the session the whole tab closes.\r\n- The watch window now clears each time a new request is made, so that it doesn't get confusing.\r\n- Do a quick eval on expressions under visual selection (with <Leader>e in visual mode).\r\n- If the maximum depth is reached on an array or object in the watch window, hit <CR> (return key) and the contents will be inserted inline - great for searching deeper, and deeper, and deeper...\r\n- Better code folding in the watch window.\r\n- ...\r\n\r\nTo see a list of all the changes, view the github repository at https:\/\/github.com\/joonty\/vim-xdebug.\r\n\r\nFor a description of how to configure the environment, see Timothy Madding's great description on his version of the script at http:\/\/www.vim.org\/scripts\/script.php?script_id=4009.","4":"======================================================================================================================\r\n*NOTICE:* This plugin has been superseded by my newer multi-language debugger client, Vdebug. I strongly recommend using that one instead: vimscript #4170\r\n======================================================================================================================\r\n\r\nThis is YET another version of the DBGP client script that Seung Woo Shin created (see http:\/\/www.vim.org\/scripts\/script.php?script_id=1152). The reason I've added this as a new script is because I've added enough new features to warrant it. Here's a few of the best:\r\n\r\n- The debugger session opens in a new tab, so that your carefully configured windows don't get messed up. When you end the session the whole tab closes.\r\n- The watch window now clears each time a new request is made, so that it doesn't get confusing.\r\n- Do a quick eval on expressions under visual selection (with <Leader>e in visual mode).\r\n- If the maximum depth is reached on an array or object in the watch window, hit <CR> (return key) and the contents will be inserted inline - great for searching deeper, and deeper, and deeper...\r\n- Better code folding in the watch window.\r\n- ...\r\n\r\nTo see a list of all the changes, view the github repository at https:\/\/github.com\/joonty\/vim-xdebug.\r\n\r\nFor a description of how to configure the environment, see Timothy Madding's great description on his version of the script at http:\/\/www.vim.org\/scripts\/script.php?script_id=4009.","install_details":"(Excerpt from Timothy Madden's script page)\r\n\r\nUnpack the .zip archive into the directory: \r\n\r\n    %USERPROFILE%\\vimfiles                 (on Windows) \r\nor \r\n    $HOME\/.vim                                         (on Linux\/Unix\/...) \r\n\r\nThe %USERPROFILE% directory on Windows is usually: \r\n         C:\\Users\\_User_Name \r\n                 or \r\n         C:\\Documents and Settings\\_User_Name\\ \r\n\r\nYou may also use the system plugin directory for vim on your system if you want to install for all users. \r\n\r\nThis will just install the two files debugger.vim and debugger.py (no documentation file included) and will directly map the <F5> key to start a debugging session (or continue running the debugged script), and also a few other keys for debugging (F2, F3, F4 - step into, step over, step out;  <F11> - get list of script variables in the current context). \r\n\r\nYou may wish to map <C-M-Up> and <C-M-Down> keys (Alt+Ctrl+Up-Arrow, Alt+Ctrl+Down-Arrorw) to the :Up and :Dn commands, to navigate the call stack of your php script with them. However the eval ,e command may only use variables from the context of the innermost (nested) stack frame. \r\n\r\nAs mentioned above you also need python2, php with XDebug extension, Vim with +python  and +signs features and the browser extension (plug-in) for XDebug.","5":"(Excerpt from Timothy Madden's script page)\r\n\r\nUnpack the .zip archive into the directory: \r\n\r\n    %USERPROFILE%\\vimfiles                 (on Windows) \r\nor \r\n    $HOME\/.vim                                         (on Linux\/Unix\/...) \r\n\r\nThe %USERPROFILE% directory on Windows is usually: \r\n         C:\\Users\\_User_Name \r\n                 or \r\n         C:\\Documents and Settings\\_User_Name\\ \r\n\r\nYou may also use the system plugin directory for vim on your system if you want to install for all users. \r\n\r\nThis will just install the two files debugger.vim and debugger.py (no documentation file included) and will directly map the <F5> key to start a debugging session (or continue running the debugged script), and also a few other keys for debugging (F2, F3, F4 - step into, step over, step out;  <F11> - get list of script variables in the current context). \r\n\r\nYou may wish to map <C-M-Up> and <C-M-Down> keys (Alt+Ctrl+Up-Arrow, Alt+Ctrl+Down-Arrorw) to the :Up and :Dn commands, to navigate the call stack of your php script with them. However the eval ,e command may only use variables from the context of the innermost (nested) stack frame. \r\n\r\nAs mentioned above you also need python2, php with XDebug extension, Vim with +python  and +signs features and the browser extension (plug-in) for XDebug.","first_name":"Jon","6":"Jon","last_name":"Cairns","7":"Cairns","releases":[{"0":"4074","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"xdebug.tar.gz","4":"xdebug.tar.gz","src_id":"17990","5":"17990","creation_date":"1337344850","6":"1337344850"}]},"4073":{"script_id":"4073","0":"4073","script_name":"highlights for radiologist","1":"highlights for radiologist","script_type":"color scheme","2":"color scheme","summary":"color highlights for radiologist's reading job ","3":"color highlights for radiologist's reading job ","description":"color highlights for radiologist's reading job\r\nrecommended color scheme  \r\n  --> source $VIMRUNTIME\/colors\/murphy.vim","4":"color highlights for radiologist's reading job\r\nrecommended color scheme  \r\n  --> source $VIMRUNTIME\/colors\/murphy.vim","install_details":"very simple \r\nadd this line to _vimrc in vim install directory \r\n:source c:\\path\\highlights_for_radiologist.vim ","5":"very simple \r\nadd this line to _vimrc in vim install directory \r\n:source c:\\path\\highlights_for_radiologist.vim ","first_name":"Seungchan","6":"Seungchan","last_name":"Lee","7":"Lee","releases":[{"0":"4073","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"highlights_for_radiologist.vim","4":"highlights_for_radiologist.vim","src_id":"17982","5":"17982","creation_date":"1337238419","6":"1337238419"}]},"4072":{"script_id":"4072","0":"4072","script_name":"sonoma.vim","1":"sonoma.vim","script_type":"color scheme","2":"color scheme","summary":"-","3":"-","description":"-","4":"-","install_details":"-","5":"-","first_name":"B","6":"B","last_name":"M","7":"M","releases":[{"0":"4072","vim_version":"7.0","1":"7.0","script_version":"1.3","2":"1.3","version_comment":"-","3":"-","package":"sonoma.vim","4":"sonoma.vim","src_id":"27958","5":"27958","creation_date":"1646617027","6":"1646617027"}]},"4071":{"script_id":"4071","0":"4071","script_name":"PyChimp","1":"PyChimp","script_type":"color scheme","2":"color scheme","summary":"Colorscheme specifically for Python (and some others as well)","3":"Colorscheme specifically for Python (and some others as well)","description":"This is a colorscheme is created using ideas borrowed for Python's own IDLE and Molokai created by Thosmas Restrepo\r\n\r\nhttp:\/\/www.vim.org\/scripts\/script.php?script_id=2340\r\n\r\nThis colorscheme is best used for coding Python and HTML (Pretty surprising that HTML, CSS and JS syntax also looks good. So, I think Django coding can be done with this as well) :)\r\n\r\n*** I have moved to github, follow me here: https:\/\/github.com\/Pychimp\/Pychimp-vim ***","4":"This is a colorscheme is created using ideas borrowed for Python's own IDLE and Molokai created by Thosmas Restrepo\r\n\r\nhttp:\/\/www.vim.org\/scripts\/script.php?script_id=2340\r\n\r\nThis colorscheme is best used for coding Python and HTML (Pretty surprising that HTML, CSS and JS syntax also looks good. So, I think Django coding can be done with this as well) :)\r\n\r\n*** I have moved to github, follow me here: https:\/\/github.com\/Pychimp\/Pychimp-vim ***","install_details":"Download the script and move it to your ~\/.vim\/colors, and its equivivalent in Windows. \r\n\r\nTo set it for one time use, Start vim and type \" :colorscheme pychimp \"\r\n\r\nTou use it as default colorscheme for all ocassions, add \" colorscheme pychimp \" in your ~\/.vimrc file","5":"Download the script and move it to your ~\/.vim\/colors, and its equivivalent in Windows. \r\n\r\nTo set it for one time use, Start vim and type \" :colorscheme pychimp \"\r\n\r\nTou use it as default colorscheme for all ocassions, add \" colorscheme pychimp \" in your ~\/.vimrc file","first_name":"Pratheek","6":"Pratheek","last_name":"","7":"","releases":[{"0":"4071","vim_version":"7.0","1":"7.0","script_version":"1","2":"1","version_comment":"Initial upload","3":"Initial upload","package":"pychimp.vim","4":"pychimp.vim","src_id":"17973","5":"17973","creation_date":"1337156637","6":"1337156637"}]},"4070":{"script_id":"4070","0":"4070","script_name":"html_FileCompletion","1":"html_FileCompletion","script_type":"ftplugin","2":"ftplugin","summary":"Base dir- and URL-aware file completion for HTML links.","3":"Base dir- and URL-aware file completion for HTML links.","description":"DESCRIPTION\r\nThis plugin offers insert mode file completion for HTML links to local files,\r\ntaking into account a base directory (document root) and base URL (web server\r\nlocation) to enable completion of absolute (\/foo...) and fully qualified\r\n(http:\/\/host\/foo...) links.\r\n\r\nRELATED WORKS\r\n- FilePathConvert.vim (vimscript #4885) converts filespecs between absolute,\r\n  relative, and URL (file:\/\/) formats.\r\n\r\nUSAGE\r\nCTRL-X CTRL-F           Find matches for file names that start with the same\r\n                        'isfname' characters as before the cursor. File names\r\n                        are inserted in URL-escaped form (e.g. <Space> -> %20)\r\n                        and always with forward slashes as path separator.\r\n                        An absolute file path starting with \"\/\" is interpreted\r\n                        relative to b:basedir, and a base URL b:baseurl is\r\n                        stripped off the front. This enables you to complete\r\n                        file links even though they are specified as absolute\r\n                        or fully qualified links in the HTML.\r\n                        When there are no matches within the base directory,\r\n                        this falls back to default, non-URL-escaped file\r\n                        completion (i_CTRL-X_CTRL-F).","4":"DESCRIPTION\r\nThis plugin offers insert mode file completion for HTML links to local files,\r\ntaking into account a base directory (document root) and base URL (web server\r\nlocation) to enable completion of absolute (\/foo...) and fully qualified\r\n(http:\/\/host\/foo...) links.\r\n\r\nRELATED WORKS\r\n- FilePathConvert.vim (vimscript #4885) converts filespecs between absolute,\r\n  relative, and URL (file:\/\/) formats.\r\n\r\nUSAGE\r\nCTRL-X CTRL-F           Find matches for file names that start with the same\r\n                        'isfname' characters as before the cursor. File names\r\n                        are inserted in URL-escaped form (e.g. <Space> -> %20)\r\n                        and always with forward slashes as path separator.\r\n                        An absolute file path starting with \"\/\" is interpreted\r\n                        relative to b:basedir, and a base URL b:baseurl is\r\n                        stripped off the front. This enables you to complete\r\n                        file links even though they are specified as absolute\r\n                        or fully qualified links in the HTML.\r\n                        When there are no matches within the base directory,\r\n                        this falls back to default, non-URL-escaped file\r\n                        completion (i_CTRL-X_CTRL-F).","install_details":"INSTALLATION\r\nThis script is packaged as a vimball. If you have the \"gunzip\" decompressor\r\nin your PATH, simply edit the *.vmb.gz package in Vim; otherwise, decompress\r\nthe archive first, e.g. using WinZip. Inside Vim, install by sourcing the\r\nvimball or via the :UseVimball command.\r\n    vim html_FileCompletion*.vmb.gz\r\n    :so %\r\nTo uninstall, use the :RmVimball command.\r\n\r\nDEPENDENCIES\r\n- Requires Vim 7.0 or higher.\r\n- Requires the ingo-library.vim plugin (vimscript #4433), version 1.019 or\r\n  higher.\r\n\r\nCONFIGURATION\r\nSet the following variables in autocmds, filetype plugins or a local vimrc:\r\n                                                                   b:basedir\r\nSpecifies the local directory that represents the document root of the edited\r\nHTML file, i.e. where an absolute link starting with \"\/\" points to. To make\r\nthis resistant to changes in the CWD, this should be an absolute dirspec. In a\r\nlocal vimrc located at the document root, you could use:\r\n    let b:basedir = expand('<sfile>:p:h')\r\n                                                                  b:baseurl\r\nSpecifies the server location of the b:basedir document root; i.e. a fully\r\nqualified link to the document root, including protocol and hostname.\r\n\r\nFor a permanent configuration, put the following commands into your vimrc:\r\n\r\nThe b:basedir can be auto-discovered when it isn't set. Starting with the\r\ndirectory the current file is in, it will traverse the directory hierarchy\r\nupward until it finds a directory that does _not_ contain typical HTML files,\r\nand will then take the previous directory as the document root. You can adapt\r\nthe file glob of what represents files within the document root via:\r\n    let g:html_FileCompletion_WithinDocRootGlob = '*.{htm,html,xhtml,asp,gsp,jsp,php}'","5":"INSTALLATION\r\nThis script is packaged as a vimball. If you have the \"gunzip\" decompressor\r\nin your PATH, simply edit the *.vmb.gz package in Vim; otherwise, decompress\r\nthe archive first, e.g. using WinZip. Inside Vim, install by sourcing the\r\nvimball or via the :UseVimball command.\r\n    vim html_FileCompletion*.vmb.gz\r\n    :so %\r\nTo uninstall, use the :RmVimball command.\r\n\r\nDEPENDENCIES\r\n- Requires Vim 7.0 or higher.\r\n- Requires the ingo-library.vim plugin (vimscript #4433), version 1.019 or\r\n  higher.\r\n\r\nCONFIGURATION\r\nSet the following variables in autocmds, filetype plugins or a local vimrc:\r\n                                                                   b:basedir\r\nSpecifies the local directory that represents the document root of the edited\r\nHTML file, i.e. where an absolute link starting with \"\/\" points to. To make\r\nthis resistant to changes in the CWD, this should be an absolute dirspec. In a\r\nlocal vimrc located at the document root, you could use:\r\n    let b:basedir = expand('<sfile>:p:h')\r\n                                                                  b:baseurl\r\nSpecifies the server location of the b:basedir document root; i.e. a fully\r\nqualified link to the document root, including protocol and hostname.\r\n\r\nFor a permanent configuration, put the following commands into your vimrc:\r\n\r\nThe b:basedir can be auto-discovered when it isn't set. Starting with the\r\ndirectory the current file is in, it will traverse the directory hierarchy\r\nupward until it finds a directory that does _not_ contain typical HTML files,\r\nand will then take the previous directory as the document root. You can adapt\r\nthe file glob of what represents files within the document root via:\r\n    let g:html_FileCompletion_WithinDocRootGlob = '*.{htm,html,xhtml,asp,gsp,jsp,php}'","first_name":"Ingo","6":"Ingo","last_name":"Karkat","7":"Karkat","releases":[{"0":"4070","vim_version":"7.0","1":"7.0","script_version":"1.20","2":"1.20","version_comment":"- Detect absolute filespecs and handle them like the build-in file completion, as the default mapping overrides that. If the user wants to convert the filespec into a link, she must do this explicitly via the html_PathConvert.vim plugin.\r\n- Add dependency to ingo-library (vimscript #4433). *** You need to separately install ingo-library (vimscript #4433) version 1.019 (or higher)! ***","3":"- Detect absolute filespecs and handle them like the build-in file completion, as the default mapping overrides that. If the user wants to convert the filespec into a link, she must do this explicitly via the html_PathConvert.vim plugin.\r\n- Add dependency to ingo-library (vimscript #4433). *** You need to separately install ingo-library (vimscript #4433) version 1.019 (or higher)! ***","package":"html_FileCompletion-1.20.vmb.gz","4":"html_FileCompletion-1.20.vmb.gz","src_id":"21970","5":"21970","creation_date":"1401561931","6":"1401561931"},{"0":"4070","vim_version":"7.0","1":"7.0","script_version":"1.12","2":"1.12","version_comment":"FIX: Include autoload scripts in Vimball that are missing in version 1.11.","3":"FIX: Include autoload scripts in Vimball that are missing in version 1.11.","package":"html_FileCompletion-1.12.vmb.gz","4":"html_FileCompletion-1.12.vmb.gz","src_id":"21911","5":"21911","creation_date":"1400658342","6":"1400658342"},{"0":"4070","vim_version":"7.0","1":"7.0","script_version":"1.11","2":"1.11","version_comment":"FIX: Do not clobber the global CWD when the buffer has a local CWD set.","3":"FIX: Do not clobber the global CWD when the buffer has a local CWD set.","package":"html_FileCompletion.vba.gz","4":"html_FileCompletion.vba.gz","src_id":"18130","5":"18130","creation_date":"1339765793","6":"1339765793"},{"0":"4070","vim_version":"7.0","1":"7.0","script_version":"1.10","2":"1.10","version_comment":"ENH: Auto-discover b:basedir by traversing up the directories until one is found that contains no HTML files.","3":"ENH: Auto-discover b:basedir by traversing up the directories until one is found that contains no HTML files.","package":"html_FileCompletion.vba.gz","4":"html_FileCompletion.vba.gz","src_id":"18009","5":"18009","creation_date":"1337602276","6":"1337602276"},{"0":"4070","vim_version":"7.0","1":"7.0","script_version":"1.00","2":"1.00","version_comment":"Initial upload","3":"Initial upload","package":"html_FileCompletion.vba.gz","4":"html_FileCompletion.vba.gz","src_id":"17968","5":"17968","creation_date":"1337109936","6":"1337109936"}]},"4069":{"script_id":"4069","0":"4069","script_name":"Ubloh Color Scheme","1":"Ubloh Color Scheme","script_type":"color scheme","2":"color scheme","summary":"A dark color scheme for Ruby.","3":"A dark color scheme for Ruby.","description":"A dark vim and gvim color scheme for Ruby.\r\n\r\nScreenshot : http:\/\/i47.tinypic.com\/124d477.png\r\n","4":"A dark vim and gvim color scheme for Ruby.\r\n\r\nScreenshot : http:\/\/i47.tinypic.com\/124d477.png\r\n","install_details":"Place in your ~\/.vim\/colors and type :colorscheme ubloh.\r\n","5":"Place in your ~\/.vim\/colors and type :colorscheme ubloh.\r\n","first_name":"Jeremy","6":"Jeremy","last_name":"Blain","7":"Blain","releases":[{"0":"4069","vim_version":"7.3","1":"7.3","script_version":"1.3.1","2":"1.3.1","version_comment":"Constants color is more pale.\r\n","3":"Constants color is more pale.\r\n","package":"ubloh.vim","4":"ubloh.vim","src_id":"18223","5":"18223","creation_date":"1341518365","6":"1341518365"},{"0":"4069","vim_version":"7.3","1":"7.3","script_version":"1.3","2":"1.3","version_comment":"Added some XML coloration.\r\n","3":"Added some XML coloration.\r\n","package":"ubloh.vim","4":"ubloh.vim","src_id":"18205","5":"18205","creation_date":"1341150933","6":"1341150933"},{"0":"4069","vim_version":"7.3","1":"7.3","script_version":"1.2","2":"1.2","version_comment":"Improvement to some colors and to the console version.","3":"Improvement to some colors and to the console version.","package":"ubloh.vim","4":"ubloh.vim","src_id":"18144","5":"18144","creation_date":"1339938399","6":"1339938399"},{"0":"4069","vim_version":"7.3","1":"7.3","script_version":"1.1","2":"1.1","version_comment":"Colors are more pale and coherent.","3":"Colors are more pale and coherent.","package":"ubloh.vim","4":"ubloh.vim","src_id":"18057","5":"18057","creation_date":"1338288849","6":"1338288849"},{"0":"4069","vim_version":"7.3","1":"7.3","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"ubloh.vim","4":"ubloh.vim","src_id":"17967","5":"17967","creation_date":"1337106667","6":"1337106667"}]},"4068":{"script_id":"4068","0":"4068","script_name":"lingodirector.vim","1":"lingodirector.vim","script_type":"color scheme","2":"color scheme","summary":"Lingo Director color scheme","3":"Lingo Director color scheme","description":"This is an update of original lingodirector.vim color scheme (vimscript #1012) for Vim 7.2+ (cleanups, fixes for latest Vim).","4":"This is an update of original lingodirector.vim color scheme (vimscript #1012) for Vim 7.2+ (cleanups, fixes for latest Vim).","install_details":"Copy to ~\/.vim\/colors\/ directory.","5":"Copy to ~\/.vim\/colors\/ directory.","first_name":"Krzysztof","6":"Krzysztof","last_name":"Pawlik","7":"Pawlik","releases":[{"0":"4068","vim_version":"7.2","1":"7.2","script_version":"1.1","2":"1.1","version_comment":"Initial upload","3":"Initial upload","package":"lingodirector.vim","4":"lingodirector.vim","src_id":"17957","5":"17957","creation_date":"1337014353","6":"1337014353"}]},"4067":{"script_id":"4067","0":"4067","script_name":"automatic for Verilog & RtlTree","1":"automatic for Verilog & RtlTree","script_type":"ftplugin","2":"ftplugin","summary":"Automatic generator for Verilog HDL (upgraded) & RtlTree","3":"Automatic generator for Verilog HDL (upgraded) & RtlTree","description":"upgrade form   \"http:\/\/www.vim.org\/scripts\/script.php?script_id=2372\r\n\r\nSupport Automatic functions like Emacs for Verilog HDL \r\n\r\nDate: 2017-09-18 upload.\r\n\r\nDescription:\r\n    For write verilog code more automatic.\r\n    Like Emacs for Verilog HDL.\r\n\r\nUse it in gvim.\r\n\r\nFile path:\r\n    vim\/.vim\/plugin\/automatic.vim   -- vim script\r\n    vim\/.vim\/after                  -- icon images\r\n\r\nFunction:\r\nuse in gvim normal mode:\r\n\r\nAutoTemplate    -- Add simple format code in *.v.\r\n                   include: AutoHeader ...\r\n                   setenv in your .cshrc for AutoHeader:\r\n                       setenv COMPANY \"your company name\"\r\n                       setenv USER_DIT \"your alias name\"\r\n               \r\n<F2>            -- Comment\/un-Comment single line with simple info.  -- with \/\/\r\n<F3>            -- Comment\/un-Comment multi  line,  -- with \/*  ... *\/\r\n                   use <Ctrl-V> select multi lines, then <F3>\r\n<F4>            -- Add a comment at end of current line\r\n              \r\n\r\n\r\n\r\n<Shift-F1>      -- AutoArg, Auto fill module module port arg(same as Emacs).\r\n                   below line \/*autoarg*\/\r\n<Shift-F2>      -- Auto Define Signals, \r\n                   below line \/*autodef*\/\r\n<Shift-F3>      -- Auto Instance.   -- line with \/*autoinst*\/\r\n                   goto module instantiation line, the <Shift-F3>.\r\n                   It is more useful.\r\n                   -- sometimes with bug, please re-open .v file.\r\n\r\n:RtlTree        -- Like Verdi. \r\n                   Left-Click:  go to specified sub-module instance line.\r\n                   Left-DoubleClick \/ Enter Key:  go to specified module define line.\r\n                   <Crtl-Alt-A>: go to hierarchical module instantiation line.\r\n                   <Crtl-Alt-N>: go to hierarchical module define line.\r\n                   -- Verdi is more powerful, so ...\r\n\r\n\r\nIcon shortcut in gvim GUI upper-rigth:\r\nPN: always @(posedge clk or negedge rst_n)\r\n* : always @(*)\r\nNN: always @(negedge clk or negedge rst_n)\r\nShowCall: goto current sub-modue instance line in parent module source file.\r\n             -- only use in RtlTree have open.\r\nShowDef : goto current sub-modue source file. -- only use in RtlTree have open.\r\n\r\n\r\nNote:\r\nSome function base on tags.\r\nYou may need update tags with ctags_gen script with all your *.v file.\r\nctags_gen *.v    or\r\nctags_gen -L verilog_file.lst\r\n\r\nYou can modify this automatic.vim for your want.\r\n\r\n\r\n\r\n\r\n\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\r\n\/\/         version info before 2014.\r\n\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\r\n\r\n=========================================================\r\n=  Install\r\n=========================================================\r\n\r\n1. vim version need >= 7.0\r\n2. copy automatic.vim to your home directory .vim\/plugin\/\r\n3. decompress Draw_pixmaps.rar, copy *.xpm file to .vim\/after,\r\n   if directory no exist, create it.\r\n4. modify your vim config file .vimrc:\r\n   \r\n   set fileformat=unix\r\n   syntax on\r\n\r\n   set expandtab        \" use <space> char replace <tab> char\r\n\r\n   set shiftwidth=4\r\n   set tabstop=4\r\n   set ruler\r\n   \r\n   set smartindent\r\n   set incsearch\r\n   set hlsearch\r\n\r\n   map <F4> :RtlTree<CR>\r\n   map <F5> <C-w><C-w>\r\n\r\n   \" save cursor position at exit edit file\r\n   autocmd BufReadPost *\r\n       \\ if (line(\"'\\\"\") > 0 && line(\"'\\\"\") <= line(\"$\") |\r\n       \\    exe \"normal g`\\\"\" |\r\n       \\ endif\r\n\r\n\r\n=========================================================\r\n=  Usage\r\n=========================================================\r\n\r\n== Automatic for Verilog\r\n\r\n1. Auto Argument,         :call AutoArg()   or shortcut key <Shift>+<F1>\r\n2. Auto Definition,       :call AutoDef()   or shortcut key <Shift>+<F2>\r\n3. Auto Instance,         :call AutoInst(0) or shortcut key <Shift>+<F3>  \"key words \/*autoinst*\/\r\n4. Auto Comment,\r\n     single line comment, :call AutoComment()  or shortcut key <F2>\r\n     multi line comment,  :call AutoComment2() or shortcut key <F3>\r\n5. \"Always @\" block quick input template, leftclick icon \"AL**\"\r\n6. abbrev \"<=\" to \"<= #1\" in insert mode\r\n\r\n== Draw wave\r\n\r\n1. leftclick icon \"CLK\" to create a clock signal wave\r\n2. leftclick icon \"SIG\" to create a one-bit signal wave\r\n3. leftclick icon \"BUS\" to create a bus signal wave\r\n4. leftclick icon \"SEP\" to create a blank line\r\n5. leftclick icon \"NEG\" to add a flag char 'neg' to end of one sig\r\n6. to draw wave use shortcut key <F8> \r\n\r\nnote: goto bottom line of sig line(total 3 lines) to create a new sig\/blank line\r\n\r\n== RtlTree\r\n\r\n1. Only use in gvim\r\n2. use script ctags_gen to create file tags, rtltree work need file tags\r\n3. Use like Verdi\r\n\r\n\r\n=========================================================\r\n=  Limit\r\n=========================================================\r\n\r\n1. One design unit per file\r\n\r\n        A file must not contain more than one design unit. Everything contained in a design\r\n     unit must be completely contained in a single module\/endmodule construct.\r\n\r\n2. File naming conventions\r\n\r\n    The file name must be composed in the following way:\r\n    <design unit name>.v\r\n\r\n    where:\r\n    <design unit name> is the name of the design unit (i.e., module name).\r\n\r\n    example: spooler.v Synthesizable Verilog code for module spooler\r\n\r\n","4":"upgrade form   \"http:\/\/www.vim.org\/scripts\/script.php?script_id=2372\r\n\r\nSupport Automatic functions like Emacs for Verilog HDL \r\n\r\nDate: 2017-09-18 upload.\r\n\r\nDescription:\r\n    For write verilog code more automatic.\r\n    Like Emacs for Verilog HDL.\r\n\r\nUse it in gvim.\r\n\r\nFile path:\r\n    vim\/.vim\/plugin\/automatic.vim   -- vim script\r\n    vim\/.vim\/after                  -- icon images\r\n\r\nFunction:\r\nuse in gvim normal mode:\r\n\r\nAutoTemplate    -- Add simple format code in *.v.\r\n                   include: AutoHeader ...\r\n                   setenv in your .cshrc for AutoHeader:\r\n                       setenv COMPANY \"your company name\"\r\n                       setenv USER_DIT \"your alias name\"\r\n               \r\n<F2>            -- Comment\/un-Comment single line with simple info.  -- with \/\/\r\n<F3>            -- Comment\/un-Comment multi  line,  -- with \/*  ... *\/\r\n                   use <Ctrl-V> select multi lines, then <F3>\r\n<F4>            -- Add a comment at end of current line\r\n              \r\n\r\n\r\n\r\n<Shift-F1>      -- AutoArg, Auto fill module module port arg(same as Emacs).\r\n                   below line \/*autoarg*\/\r\n<Shift-F2>      -- Auto Define Signals, \r\n                   below line \/*autodef*\/\r\n<Shift-F3>      -- Auto Instance.   -- line with \/*autoinst*\/\r\n                   goto module instantiation line, the <Shift-F3>.\r\n                   It is more useful.\r\n                   -- sometimes with bug, please re-open .v file.\r\n\r\n:RtlTree        -- Like Verdi. \r\n                   Left-Click:  go to specified sub-module instance line.\r\n                   Left-DoubleClick \/ Enter Key:  go to specified module define line.\r\n                   <Crtl-Alt-A>: go to hierarchical module instantiation line.\r\n                   <Crtl-Alt-N>: go to hierarchical module define line.\r\n                   -- Verdi is more powerful, so ...\r\n\r\n\r\nIcon shortcut in gvim GUI upper-rigth:\r\nPN: always @(posedge clk or negedge rst_n)\r\n* : always @(*)\r\nNN: always @(negedge clk or negedge rst_n)\r\nShowCall: goto current sub-modue instance line in parent module source file.\r\n             -- only use in RtlTree have open.\r\nShowDef : goto current sub-modue source file. -- only use in RtlTree have open.\r\n\r\n\r\nNote:\r\nSome function base on tags.\r\nYou may need update tags with ctags_gen script with all your *.v file.\r\nctags_gen *.v    or\r\nctags_gen -L verilog_file.lst\r\n\r\nYou can modify this automatic.vim for your want.\r\n\r\n\r\n\r\n\r\n\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\r\n\/\/         version info before 2014.\r\n\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\r\n\r\n=========================================================\r\n=  Install\r\n=========================================================\r\n\r\n1. vim version need >= 7.0\r\n2. copy automatic.vim to your home directory .vim\/plugin\/\r\n3. decompress Draw_pixmaps.rar, copy *.xpm file to .vim\/after,\r\n   if directory no exist, create it.\r\n4. modify your vim config file .vimrc:\r\n   \r\n   set fileformat=unix\r\n   syntax on\r\n\r\n   set expandtab        \" use <space> char replace <tab> char\r\n\r\n   set shiftwidth=4\r\n   set tabstop=4\r\n   set ruler\r\n   \r\n   set smartindent\r\n   set incsearch\r\n   set hlsearch\r\n\r\n   map <F4> :RtlTree<CR>\r\n   map <F5> <C-w><C-w>\r\n\r\n   \" save cursor position at exit edit file\r\n   autocmd BufReadPost *\r\n       \\ if (line(\"'\\\"\") > 0 && line(\"'\\\"\") <= line(\"$\") |\r\n       \\    exe \"normal g`\\\"\" |\r\n       \\ endif\r\n\r\n\r\n=========================================================\r\n=  Usage\r\n=========================================================\r\n\r\n== Automatic for Verilog\r\n\r\n1. Auto Argument,         :call AutoArg()   or shortcut key <Shift>+<F1>\r\n2. Auto Definition,       :call AutoDef()   or shortcut key <Shift>+<F2>\r\n3. Auto Instance,         :call AutoInst(0) or shortcut key <Shift>+<F3>  \"key words \/*autoinst*\/\r\n4. Auto Comment,\r\n     single line comment, :call AutoComment()  or shortcut key <F2>\r\n     multi line comment,  :call AutoComment2() or shortcut key <F3>\r\n5. \"Always @\" block quick input template, leftclick icon \"AL**\"\r\n6. abbrev \"<=\" to \"<= #1\" in insert mode\r\n\r\n== Draw wave\r\n\r\n1. leftclick icon \"CLK\" to create a clock signal wave\r\n2. leftclick icon \"SIG\" to create a one-bit signal wave\r\n3. leftclick icon \"BUS\" to create a bus signal wave\r\n4. leftclick icon \"SEP\" to create a blank line\r\n5. leftclick icon \"NEG\" to add a flag char 'neg' to end of one sig\r\n6. to draw wave use shortcut key <F8> \r\n\r\nnote: goto bottom line of sig line(total 3 lines) to create a new sig\/blank line\r\n\r\n== RtlTree\r\n\r\n1. Only use in gvim\r\n2. use script ctags_gen to create file tags, rtltree work need file tags\r\n3. Use like Verdi\r\n\r\n\r\n=========================================================\r\n=  Limit\r\n=========================================================\r\n\r\n1. One design unit per file\r\n\r\n        A file must not contain more than one design unit. Everything contained in a design\r\n     unit must be completely contained in a single module\/endmodule construct.\r\n\r\n2. File naming conventions\r\n\r\n    The file name must be composed in the following way:\r\n    <design unit name>.v\r\n\r\n    where:\r\n    <design unit name> is the name of the design unit (i.e., module name).\r\n\r\n    example: spooler.v Synthesizable Verilog code for module spooler\r\n\r\n","install_details":"","5":"","first_name":"zhang","6":"zhang","last_name":"guo","7":"guo","releases":[{"0":"4067","vim_version":"7.0","1":"7.0","script_version":"2.2.4","2":"2.2.4","version_comment":"clear a AutoInstUpdate INST_DEL problem for null comma inst port line","3":"clear a AutoInstUpdate INST_DEL problem for null comma inst port line","package":"automatic_vim_2017_09_18.tar.gz","4":"automatic_vim_2017_09_18.tar.gz","src_id":"25576","5":"25576","creation_date":"1505743983","6":"1505743983"},{"0":"4067","vim_version":"7.0","1":"7.0","script_version":"2.2.3","2":"2.2.3","version_comment":"UPDATE:\r\n1. clear a AutoArg bug\r\n2. resume AutoInst*(1) function for multi-times instance & update\r\n","3":"UPDATE:\r\n1. clear a AutoArg bug\r\n2. resume AutoInst*(1) function for multi-times instance & update\r\n","package":"automatic_vim_2017_09_16.tar.gz","4":"automatic_vim_2017_09_16.tar.gz","src_id":"25567","5":"25567","creation_date":"1505568902","6":"1505568902"},{"0":"4067","vim_version":"7.0","1":"7.0","script_version":"2.2.1","2":"2.2.1","version_comment":"clear a AutoInstPortReAlign bug","3":"clear a AutoInstPortReAlign bug","package":"automatic_vim_2017_08_28.tar.gz","4":"automatic_vim_2017_08_28.tar.gz","src_id":"25535","5":"25535","creation_date":"1503922650","6":"1503922650"},{"0":"4067","vim_version":"7.0","1":"7.0","script_version":"2.20","2":"2.20","version_comment":"1. Add New AutoInstUpdate series function\r\n        a) AutoInstUpdate\r\n               Update module instance, detect the Newst append and have deleted module ports\r\n               It is very useful for RTL code module instance update.\r\n        \r\n        b) AutoInstUpdateOrder\r\n               Update module instance, instance port order same with module port.\r\n               It is very useful for RTL code module instance update.\r\n        \r\n        c) AutoInstPortReAlign\r\n               Auto Inst Port signal auto Re-Align format, only Re-Align port connection\r\n        \r\n        d) AppendPortDriectionToInst\r\n               Append port direction info(comment) to have instanced module port instanced line\r\n\r\n2. CreateRtlTree update\r\n        use verilog \"()\" & \"{}\" pair to skip module define block, skip always block, Concatenate block and so on\r\n\r\n","3":"1. Add New AutoInstUpdate series function\r\n        a) AutoInstUpdate\r\n               Update module instance, detect the Newst append and have deleted module ports\r\n               It is very useful for RTL code module instance update.\r\n        \r\n        b) AutoInstUpdateOrder\r\n               Update module instance, instance port order same with module port.\r\n               It is very useful for RTL code module instance update.\r\n        \r\n        c) AutoInstPortReAlign\r\n               Auto Inst Port signal auto Re-Align format, only Re-Align port connection\r\n        \r\n        d) AppendPortDriectionToInst\r\n               Append port direction info(comment) to have instanced module port instanced line\r\n\r\n2. CreateRtlTree update\r\n        use verilog \"()\" & \"{}\" pair to skip module define block, skip always block, Concatenate block and so on\r\n\r\n","package":"automatic_vim_2017_08_27.tar.gz","4":"automatic_vim_2017_08_27.tar.gz","src_id":"25532","5":"25532","creation_date":"1503811366","6":"1503811366"},{"0":"4067","vim_version":"7.0","1":"7.0","script_version":"2.1.0","2":"2.1.0","version_comment":"1. get sub-instance algorithm modify, use verilog 2001 syntax Module instantiation\r\n   replace old algorithm (use keywords autoinst)\r\n2. function ShowCall & ShowDef update\r\n3. rtltree little upgrade, support `ifdef `ifndef `elsif `else `endif in rtltree\r\n   window","3":"1. get sub-instance algorithm modify, use verilog 2001 syntax Module instantiation\r\n   replace old algorithm (use keywords autoinst)\r\n2. function ShowCall & ShowDef update\r\n3. rtltree little upgrade, support `ifdef `ifndef `elsif `else `endif in rtltree\r\n   window","package":"automatic_vim_2017_01_01.tar.gz","4":"automatic_vim_2017_01_01.tar.gz","src_id":"24869","5":"24869","creation_date":"1483251330","6":"1483251330"},{"0":"4067","vim_version":"7.0","1":"7.0","script_version":" 2.0.1","2":" 2.0.1","version_comment":"1. add Search menu, -- search instance \/ module \/ Trace Driver(Lite)\r\n   -- for the Search & Trace, add backward & forward history feature like verdi\r\n2. some function short-cut key modify\r\n","3":"1. add Search menu, -- search instance \/ module \/ Trace Driver(Lite)\r\n   -- for the Search & Trace, add backward & forward history feature like verdi\r\n2. some function short-cut key modify\r\n","package":"automatic_vim_2016_08_24.tar.gz","4":"automatic_vim_2016_08_24.tar.gz","src_id":"24464","5":"24464","creation_date":"1472002572","6":"1472002572"},{"0":"4067","vim_version":"7.0","1":"7.0","script_version":"2.0.0","2":"2.0.0","version_comment":"upload after more than one year.","3":"upload after more than one year.","package":"automatic_vim_2016_02_27.tar.gz","4":"automatic_vim_2016_02_27.tar.gz","src_id":"24050","5":"24050","creation_date":"1456576232","6":"1456576232"},{"0":"4067","vim_version":"7.0","1":"7.0","script_version":"v1.4","2":"v1.4","version_comment":"1. Add always block quick input template\r\n2. clr rtltree no definition g: variable bug (NERDTree)\r\n3. update Draw wave for negedge toggle logic\r\n4. update FileHeader for .v file","3":"1. Add always block quick input template\r\n2. clr rtltree no definition g: variable bug (NERDTree)\r\n3. update Draw wave for negedge toggle logic\r\n4. update FileHeader for .v file","package":"automatic_v1.4.rar","4":"automatic_v1.4.rar","src_id":"21221","5":"21221","creation_date":"1387595155","6":"1387595155"},{"0":"4067","vim_version":"7.0","1":"7.0","script_version":"1.3","2":"1.3","version_comment":"rtltree support tree fold, it's init_max_display_layer is 3","3":"rtltree support tree fold, it's init_max_display_layer is 3","package":"automatic_v1.3.rar","4":"automatic_v1.3.rar","src_id":"19487","5":"19487","creation_date":"1360386330","6":"1360386330"},{"0":"4067","vim_version":"7.0","1":"7.0","script_version":"1.2.3","2":"1.2.3","version_comment":"fix some bugs on function AutoDef","3":"fix some bugs on function AutoDef","package":"automatic_v1.2.3.rar","4":"automatic_v1.2.3.rar","src_id":"19346","5":"19346","creation_date":"1357903432","6":"1357903432"},{"0":"4067","vim_version":"7.0","1":"7.0","script_version":"1.2.2","2":"1.2.2","version_comment":"fix AutoArg bug\r\nfix AutoInst bug (function GetIO)","3":"fix AutoArg bug\r\nfix AutoInst bug (function GetIO)","package":"automatic.rar","4":"automatic.rar","src_id":"19005","5":"19005","creation_date":"1353499137","6":"1353499137"},{"0":"4067","vim_version":"7.0","1":"7.0","script_version":"1.2.1","2":"1.2.1","version_comment":"add icon for DrawTiming, only use in gvim.  Usage: decompress Draw_pixmaps.rar , modify the icon file path in file automatic.vim","3":"add icon for DrawTiming, only use in gvim.  Usage: decompress Draw_pixmaps.rar , modify the icon file path in file automatic.vim","package":"automatic.rar","4":"automatic.rar","src_id":"18926","5":"18926","creation_date":"1351600500","6":"1351600500"},{"0":"4067","vim_version":"7.0","1":"7.0","script_version":"1.2","2":"1.2","version_comment":"new add RtlTree   \r\n   - it's useful, refrence NERDTree source code, work like EDA tool verdi.","3":"new add RtlTree   \r\n   - it's useful, refrence NERDTree source code, work like EDA tool verdi.","package":"automatic1.2.rar","4":"automatic1.2.rar","src_id":"18369","5":"18369","creation_date":"1344093199","6":"1344093199"},{"0":"4067","vim_version":"7.0","1":"7.0","script_version":"v1.1","2":"v1.1","version_comment":"upgrade a little, and clr a bug about autodef","3":"upgrade a little, and clr a bug about autodef","package":"automatic.rar","4":"automatic.rar","src_id":"18105","5":"18105","creation_date":"1339205537","6":"1339205537"},{"0":"4067","vim_version":"7.3","1":"7.3","script_version":"1.01","2":"1.01","version_comment":"append file: ctags_gen","3":"append file: ctags_gen","package":"automatic.rar","4":"automatic.rar","src_id":"17956","5":"17956","creation_date":"1337008740","6":"1337008740"},{"0":"4067","vim_version":"7.0","1":"7.0","script_version":"1.00","2":"1.00","version_comment":"Initial upload","3":"Initial upload","package":"automatic.rar","4":"automatic.rar","src_id":"17955","5":"17955","creation_date":"1337008528","6":"1337008528"}]},"4066":{"script_id":"4066","0":"4066","script_name":"matchindent.vim","1":"matchindent.vim","script_type":"utility","2":"utility","summary":"Match indentation style","3":"Match indentation style","description":"Some people like tabs, some like spaces. Very few people like it when you edit their stuff and use a different method of indentation.\r\n\r\nThis plugin scans through a file when it\\'s opened and attempts to guess which style of indentation is being used. It then overrides your preferences so that you match the style of the file.\r\n\r\nCurrently it only detects the three most common styles of indentation, tabs, 2 spaces and 4 spaces. Patches to make this plugin more general are welcomed.\r\n\r\nThe most up to date version of this script is available at https:\/\/github.com\/conormcd\/matchindent.vim","4":"Some people like tabs, some like spaces. Very few people like it when you edit their stuff and use a different method of indentation.\r\n\r\nThis plugin scans through a file when it\\'s opened and attempts to guess which style of indentation is being used. It then overrides your preferences so that you match the style of the file.\r\n\r\nCurrently it only detects the three most common styles of indentation, tabs, 2 spaces and 4 spaces. Patches to make this plugin more general are welcomed.\r\n\r\nThe most up to date version of this script is available at https:\/\/github.com\/conormcd\/matchindent.vim","install_details":"Drop the included matchindent.vim into your .vim\/plugin directory or use Pathogen.","5":"Drop the included matchindent.vim into your .vim\/plugin directory or use Pathogen.","first_name":"Conor","6":"Conor","last_name":"McDermottroe","7":"McDermottroe","releases":[{"0":"4066","vim_version":"7.0","1":"7.0","script_version":"0.0.1","2":"0.0.1","version_comment":"Initial upload","3":"Initial upload","package":"matchindent.vim-0.0.1.tgz","4":"matchindent.vim-0.0.1.tgz","src_id":"17953","5":"17953","creation_date":"1336991708","6":"1336991708"}]},"4065":{"script_id":"4065","0":"4065","script_name":"cmdpathup","1":"cmdpathup","script_type":"utility","2":"utility","summary":"Hotkey for going one level up when editing a path on command line","3":"Hotkey for going one level up when editing a path on command line","description":"This plugin provides a hotkey to go up by one level\r\nwhen editing a file path on the vim command line.\r\n\r\nSuppose you edit a file system path in the command line\r\nwhere | represents the position of the cursor\r\n\r\n:e ~\/foo\/bar\/foo-bar\/|barbar\r\n\r\nThen pressing the plugin hotkey will result in\r\n\r\n:e ~\/foo\/bar\/|barbar\r\n\r\nIn contrast you would have to press <c-w> four times to\r\ndelete '\/', 'bar', '-', and 'for' one by one.","4":"This plugin provides a hotkey to go up by one level\r\nwhen editing a file path on the vim command line.\r\n\r\nSuppose you edit a file system path in the command line\r\nwhere | represents the position of the cursor\r\n\r\n:e ~\/foo\/bar\/foo-bar\/|barbar\r\n\r\nThen pressing the plugin hotkey will result in\r\n\r\n:e ~\/foo\/bar\/|barbar\r\n\r\nIn contrast you would have to press <c-w> four times to\r\ndelete '\/', 'bar', '-', and 'for' one by one.","install_details":"You can simply extract the content of the .tar.gz into your vim directory.\r\nHowever, I recommend to use pathogen (http:\/\/www.vim.org\/scripts\/script.php?script_id=2332)\r\nand to extract into bundle\/vim-cmdpathup instead.\r\n\r\nYou can also directly clone from the github repository into bundle\/.\r\nhttps:\/\/github.com\/cgraeser\/vim-cmdpathup.\r\n","5":"You can simply extract the content of the .tar.gz into your vim directory.\r\nHowever, I recommend to use pathogen (http:\/\/www.vim.org\/scripts\/script.php?script_id=2332)\r\nand to extract into bundle\/vim-cmdpathup instead.\r\n\r\nYou can also directly clone from the github repository into bundle\/.\r\nhttps:\/\/github.com\/cgraeser\/vim-cmdpathup.\r\n","first_name":"Carsten","6":"Carsten","last_name":"Gr\u00c3\u00a4ser","7":"Gr\u00c3\u00a4ser","releases":[{"0":"4065","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"cmdpathup.tar.gz","4":"cmdpathup.tar.gz","src_id":"17947","5":"17947","creation_date":"1336945622","6":"1336945622"}]},"4064":{"script_id":"4064","0":"4064","script_name":"license loader","1":"license loader","script_type":"utility","2":"utility","summary":"a vim script to load a license template","3":"a vim script to load a license template","description":"a vim script to load a license template\r\n\r\nUsage:\r\n:call  LoadMyLicense('apache')\r\n\r\nyou can add or modify the license template in templates\/license\/*","4":"a vim script to load a license template\r\n\r\nUsage:\r\n:call  LoadMyLicense('apache')\r\n\r\nyou can add or modify the license template in templates\/license\/*","install_details":"1.  copy plugin\/loadLicences.vim to ~\/.vim\/plugin\/\r\n    copy templates\/license\/* to ~\/.vim\/templates\/license\/\r\n\r\n2. edit .vimrc add following lines\r\n\r\nlet g:T_AUTHOR = \"XXX\"\r\nlet g:T_AUTHOR_EMAIL = \"foo@far.com\"\r\nlet g:T_DATE_FORMAT = \"%c\"\r\n\r\n\" maybe you need following settings to\r\n\" fast input template information not defined\r\n\"  in formate of <+template+>\r\nnnoremap <C-j> \/<+.\\{-1,}+><CR>c\/+>\/e<CR>\r\ninoremap <C-j> <ESC>\/<+.\\{-1,}+><CR>c\/+>\/e<CR>\r\n","5":"1.  copy plugin\/loadLicences.vim to ~\/.vim\/plugin\/\r\n    copy templates\/license\/* to ~\/.vim\/templates\/license\/\r\n\r\n2. edit .vimrc add following lines\r\n\r\nlet g:T_AUTHOR = \"XXX\"\r\nlet g:T_AUTHOR_EMAIL = \"foo@far.com\"\r\nlet g:T_DATE_FORMAT = \"%c\"\r\n\r\n\" maybe you need following settings to\r\n\" fast input template information not defined\r\n\"  in formate of <+template+>\r\nnnoremap <C-j> \/<+.\\{-1,}+><CR>c\/+>\/e<CR>\r\ninoremap <C-j> <ESC>\/<+.\\{-1,}+><CR>c\/+>\/e<CR>\r\n","first_name":"zpcat ","6":"zpcat ","last_name":"su","7":"su","releases":[{"0":"4064","vim_version":"7.0","1":"7.0","script_version":"0.1-beta","2":"0.1-beta","version_comment":"Initial upload","3":"Initial upload","package":"licenseLoader-0.1beta.tar.gz","4":"licenseLoader-0.1beta.tar.gz","src_id":"17944","5":"17944","creation_date":"1336897713","6":"1336897713"}]},"4063":{"script_id":"4063","0":"4063","script_name":"_jsbeautify","1":"_jsbeautify","script_type":"utility","2":"utility","summary":"Modified base on jsbeautify.vim (move comma to head of ojbect's attribute line)","3":"Modified base on jsbeautify.vim (move comma to head of ojbect's attribute line)","description":"Another plugin to format your JavaScript source code\r\n\r\nI modified the jsbeautify.vim as I need. (Original jsbeautify.vim is here: http:\/\/www.vim.org\/scripts\/script.php?script_id=2727 ) (changes happened on lines 1, 4, 532, 534, 538, 540 and 503)\r\n\r\n\r\n{\r\n        a: 'a',\r\n        b: 'b'\r\n}\r\n\r\nMove the comma after Object's attribute to next line's front.\r\n\r\n{\r\n        a: 'a'\r\n        ,b: 'b'\r\n}\r\n There won't be a newline after } , when it's in an Expression. Such as function({},{}).\r\n\r\n Example for these 2 changes mentioned above:\r\n⇲\r\nvar p_roleMutexGroupListGrid, p_assignedMutexRoleGrid, p_unassignedMutexRoleGrid, p_roleDetailsForm;\r\nvar PID = pffp.setPID({}, {\r\n        \/*若在維護中需要修改權限設置，請到全局配置文件中去修改。*\/\r\n        roleMutexGroup_query: 101101\r\n        ,roleMutexGroupMember_query: 101201\r\n        ,roleMutexGroupMember_assign: 101202\r\n        ,roleMutexGroupMember_remove: 101203\r\n        ,roleMutexGroupMember_details: 101204\r\n        ,role_details: 100805\r\n});\r\n$(function() {\r\n        var array1 = [1, 2, 3];\r\n        var array2 = [];\r\n        for (var i = 0; i <= 3; i++) {\r\n                array2.push(i);\r\n        }\r\n        if ({\r\n                a: ''\r\n                ,b: ''\r\n                ,c: 2\r\n        } === {\r\n                b: ''\r\n                ,c: 2\r\n                ,a: ''\r\n        } && ['', '', 1] == ['', '', 1]) {\r\n                pffp.filterPermissionFunc({}, [PID.roleMutexGroup_query], [initRoleMutexGroupGrid])();\/\/  There won be a newline after } , when it's in an Expression.\r\n        }\r\n});\r\nvar initRoleMutexGroupGrid = function() {\r\n        p_roleMutexGroupListGrid = pffp.initGrid(null, {\r\n                id: 'roleMutexGroupListGrid'\r\n                ,confId: 'roleMutexGroupListGrid_conf'\r\n                ,topBtn: true\r\n                ,passParam: {}\r\n        }, RMGGridRowClick); \/\/  There won be a newline after } , when it's in an Expression.\r\n}\r\n⇱ END\r\n\r\n\r\n\r\nThis vim-script also works at a low performance:)  \r\nvim-jsbeautify : Simple javascript formater base on js-beautify  http:\/\/www.vim.org\/scripts\/script.php?script_id=4017(this one looks like the one which can be faster, but I haven't try it. )\r\n\r\nusage:\r\n  <leader>_ff\r\nor\r\n  bind the g:_Jsbeautify() function to any short key you like.\r\n\r\nThanks jsbeautify.vim's author : aj3423          (as the name I know).\r\n(I just a beginner, don't know how to write a complete vim-script file. )","4":"Another plugin to format your JavaScript source code\r\n\r\nI modified the jsbeautify.vim as I need. (Original jsbeautify.vim is here: http:\/\/www.vim.org\/scripts\/script.php?script_id=2727 ) (changes happened on lines 1, 4, 532, 534, 538, 540 and 503)\r\n\r\n\r\n{\r\n        a: 'a',\r\n        b: 'b'\r\n}\r\n\r\nMove the comma after Object's attribute to next line's front.\r\n\r\n{\r\n        a: 'a'\r\n        ,b: 'b'\r\n}\r\n There won't be a newline after } , when it's in an Expression. Such as function({},{}).\r\n\r\n Example for these 2 changes mentioned above:\r\n⇲\r\nvar p_roleMutexGroupListGrid, p_assignedMutexRoleGrid, p_unassignedMutexRoleGrid, p_roleDetailsForm;\r\nvar PID = pffp.setPID({}, {\r\n        \/*若在維護中需要修改權限設置，請到全局配置文件中去修改。*\/\r\n        roleMutexGroup_query: 101101\r\n        ,roleMutexGroupMember_query: 101201\r\n        ,roleMutexGroupMember_assign: 101202\r\n        ,roleMutexGroupMember_remove: 101203\r\n        ,roleMutexGroupMember_details: 101204\r\n        ,role_details: 100805\r\n});\r\n$(function() {\r\n        var array1 = [1, 2, 3];\r\n        var array2 = [];\r\n        for (var i = 0; i <= 3; i++) {\r\n                array2.push(i);\r\n        }\r\n        if ({\r\n                a: ''\r\n                ,b: ''\r\n                ,c: 2\r\n        } === {\r\n                b: ''\r\n                ,c: 2\r\n                ,a: ''\r\n        } && ['', '', 1] == ['', '', 1]) {\r\n                pffp.filterPermissionFunc({}, [PID.roleMutexGroup_query], [initRoleMutexGroupGrid])();\/\/  There won be a newline after } , when it's in an Expression.\r\n        }\r\n});\r\nvar initRoleMutexGroupGrid = function() {\r\n        p_roleMutexGroupListGrid = pffp.initGrid(null, {\r\n                id: 'roleMutexGroupListGrid'\r\n                ,confId: 'roleMutexGroupListGrid_conf'\r\n                ,topBtn: true\r\n                ,passParam: {}\r\n        }, RMGGridRowClick); \/\/  There won be a newline after } , when it's in an Expression.\r\n}\r\n⇱ END\r\n\r\n\r\n\r\nThis vim-script also works at a low performance:)  \r\nvim-jsbeautify : Simple javascript formater base on js-beautify  http:\/\/www.vim.org\/scripts\/script.php?script_id=4017(this one looks like the one which can be faster, but I haven't try it. )\r\n\r\nusage:\r\n  <leader>_ff\r\nor\r\n  bind the g:_Jsbeautify() function to any short key you like.\r\n\r\nThanks jsbeautify.vim's author : aj3423          (as the name I know).\r\n(I just a beginner, don't know how to write a complete vim-script file. )","install_details":"input into your\r\nvimfiles\/plugin, too\r\n\r\nI located it to \/usr\/share\/vim\/vim72\/plugin\/_jsbeautify.vim\r\n","5":"input into your\r\nvimfiles\/plugin, too\r\n\r\nI located it to \/usr\/share\/vim\/vim72\/plugin\/_jsbeautify.vim\r\n","first_name":"will","6":"will","last_name":"king","7":"king","releases":[{"0":"4063","vim_version":"7.2","1":"7.2","script_version":"2.2","2":"2.2","version_comment":"add some comments in code.\r\nAnd change a word \"endfunctio\" to \"endfunction\"","3":"add some comments in code.\r\nAnd change a word \"endfunctio\" to \"endfunction\"","package":"_jsbeautify.vim.2.2.zip","4":"_jsbeautify.vim.2.2.zip","src_id":"18834","5":"18834","creation_date":"1350533223","6":"1350533223"},{"0":"4063","vim_version":"7.2","1":"7.2","script_version":"2.1","2":"2.1","version_comment":"add inner function deindent(num)\r\n\r\ncase statement in switch starts with one more indent in this version.\r\n\r\nSo far so good , but more test is needed.","3":"add inner function deindent(num)\r\n\r\ncase statement in switch starts with one more indent in this version.\r\n\r\nSo far so good , but more test is needed.","package":"_jsbeautify.vim.2.1.zip","4":"_jsbeautify.vim.2.1.zip","src_id":"18466","5":"18466","creation_date":"1345741006","6":"1345741006"},{"0":"4063","vim_version":"7.2","1":"7.2","script_version":"2.0","2":"2.0","version_comment":"versino 1.2 will cause \\ff or :call g:Jsbeautify() retire.\r\nI've changed _jsbeautify.vim. This version can work with jsbeautify.vim.\r\n\\_ff and :call g:_Jsbeautify() to use  _jsbeautify.vim.\r\n\\ff and :call g:Jsbeautify() to use jsbeautify.vim.","3":"versino 1.2 will cause \\ff or :call g:Jsbeautify() retire.\r\nI've changed _jsbeautify.vim. This version can work with jsbeautify.vim.\r\n\\_ff and :call g:_Jsbeautify() to use  _jsbeautify.vim.\r\n\\ff and :call g:Jsbeautify() to use jsbeautify.vim.","package":"_jsbeautify.vim","4":"_jsbeautify.vim","src_id":"17941","5":"17941","creation_date":"1336822723","6":"1336822723"},{"0":"4063","vim_version":"7.2","1":"7.2","script_version":"1.2","2":"1.2","version_comment":"Initial upload","3":"Initial upload","package":"_jsbeautify.vim","4":"_jsbeautify.vim","src_id":"17940","5":"17940","creation_date":"1336820365","6":"1336820365"}]},"4062":{"script_id":"4062","0":"4062","script_name":"vtimer.vim","1":"vtimer.vim","script_type":"utility","2":"utility","summary":"Recording time spent with vim, and total lines written.","3":"Recording time spent with vim, and total lines written.","description":"Commands:\r\n        :Showtime\t      show total time\r\n\r\n        :Resettime           reset total time\r\n\r\n        :Showline             show total line\r\n\r\n        :Resetline             reset total line\r\n","4":"Commands:\r\n        :Showtime\t      show total time\r\n\r\n        :Resettime           reset total time\r\n\r\n        :Showline             show total line\r\n\r\n        :Resetline             reset total line\r\n","install_details":"Easy, move it to your own $HOME\/.vim\/plugin\/","5":"Easy, move it to your own $HOME\/.vim\/plugin\/","first_name":"Dai","6":"Dai","last_name":"Cang","7":"Cang","releases":[{"0":"4062","vim_version":"7.0","1":"7.0","script_version":"1.1","2":"1.1","version_comment":"add a function to count totalline","3":"add a function to count totalline","package":"vtimer.vim","4":"vtimer.vim","src_id":"18296","5":"18296","creation_date":"1342837796","6":"1342837796"},{"0":"4062","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"vtimer.vim","4":"vtimer.vim","src_id":"17939","5":"17939","creation_date":"1336781351","6":"1336781351"}]},"4061":{"script_id":"4061","0":"4061","script_name":"mathematic.vim","1":"mathematic.vim","script_type":"utility","2":"utility","summary":"for inputting mathematic symbols.","3":"for inputting mathematic symbols.","description":"This is a vim keymap file contains mathematic symbols.\r\nwith some effort to reduce typing conflict and increase typing speed.\r\n\r\nAlso contains a keyhelper for help inputting.\r\n\r\n- Superscript and Subscript :\r\n\r\n        `0 ⁰  `+ ⁺ ... ( 0-9 + - ( ) \/ ^ . , > < )\r\n        `a ᵃ  `A ᴬ ... ( a-z except q , Some of A-Z)\r\n\r\n        _0 ₀  _+ ₊ ... ( 0-9 + - ( ) \/ ^ )\r\n        _a ₐ  _e ₑ ... (a e h i k l m n o p r s t u v x)\r\n\r\n\r\n- Short CMD  :\r\n\r\n        Greek Alphabet:\r\n                    \\GA  => Α , \\GD   => Δ\r\n                    \\Ga  => α , \\Gg   => γ\r\n\r\n        Fractions   :\r\n                    \\1\/2   => \u00c2\u00bd , \\1\/3 => ⅓\r\n                    \\2\/3   => ⅔ , \\3\/5 => ⅗\r\n\r\n        Arrows      :\r\n                    \\<--   => ←  , \\--v => ↓  , \\==>  => ⇒\r\n                    \\<---  => ⟵  , \\--^ => ↑  , \\===> => ⟹\r\n\r\n        Grouping    : \r\n                    \\(U    => ⎛  , \\]U  => ⎤\r\n                    \\(M    => ⎜  , \\]M  => ⎥\r\n                    \\(B    => ⎝  , \\]B  => ⎦\r\n                    \\(V    => ︵ , \\]V  => ︺\r\n\r\n\r\n        Operator    :\r\n                    \\U.    => ⨃ , \\UU   => ∪  , \\UN  => ∩\r\n                    \\I1    => ∫ , \\I3   => ∭  , \\I=  => ⨎\r\n                    \\IO1   => ∮ , \\IO3  => ∰  , \\IOW => ∳\r\n                    \\PDF   => ∂ , \\THF  => ∴  , \\BCS => ∵\r\n                    \\MUL   => \u00c3\u0097 , \\DIV  => \u00c3\u00b7\r\n                    \\SQRT2 => √ , \\SQRT3 => ∛ , \\SQRT4 => ∜\r\n\r\n        Relations   : \r\n                    \\<=    => ≤ , \\>=  => ≥   , \\!=  => ≠\r\n                    \\<~    => ⪝ , \\>~  => ⪞   , \\!>  => ≯\r\n                    \\o+    => ⊕ , \\o-  => ⊖   , \\ox  => ⊗\r\n                    \\O+    => ⨀ , \\O+  => ⨁   , \\OX  => ⨂\r\n\r\n        Sets        :\r\n                    \\SUBO  => ⊂ , \\SUBE => ⊆  , \\SUBN => ⊄\r\n                    \\SUPO  => ⊃ , \\SUPE => ⊇  , \\SUPX => ⊉\r\n                    \\AND   => ∧ , \\OR   => ∨  , \\NOT  => \u00c2\u00ac\r\n                    \\XOR   => ⊕\r\n                    \\EXTS  => ∃ , \\EXTN => ∄  , \\FALL => ∀\r\n                    \\BOT   => ⊥ , \\TOP => ⊤   , \\LFT  => ⊣\r\n                    \\RGT   => ⊢\r\n\r\n        Misc        :\r\n                    \\INF  => ∞  , \\PRT  => ∝\r\n                    \\ARC   => ⌒ , \\ANG  => ∠\r\n                    \\DEGC  => ℃ , \\DEGF => ℉\r\n                    \\OHM   => Ω , \\MHO  => ℧  , \\ANGS => Å\r\n                    \\a\/c   => ℀ , \\a\/s  => ℁  , \\No   => №\r\n                    \\TM    => \u00e2\u0084\u00a2 , \\CO   => \u00c2\u00a9  , \\RO   => \u00c2\u00ae\r\n                    \\AE    => \u00c3\u0086 , \\ae   => \u00c3\u00a6  , \\fi   => fi\r\n\r\n        Fonts       :\r\n                    \\BBA   => 𝔸 , \\BBH => ℍ   , \\BB0  => 𝟘\r\n                    \\FKH   => ℋ , \\FKI => ℑ   , \\FKL  => ℒ\r\n\r\n\r\n- Latex CMD:\r\n\r\n        Based on Vim-Latex suite.\r\n        Only contains latex command which have corresponding unicode chars.\r\n        Fixed some incorrect mapping of Vim-Latex suite:\r\n        (\\bigodot \\bigoplus \\bigotimes \\long...arrow \\iint ...)\r\n\r\n        e.g: \r\n            \\neq     => ≠  ,  \\Leftarrow =>  ⇐\r\n            \\simeq   => ≃  ,  \\Re        =>  ℜ\r\n            \\mathbbA => 𝔸  ,  \\mathfrakA =>  𝔄\r\n            ...\r\n\r\n        You can use Vim-Latex suite to check these command.\r\n        or this pdf of math symbols.\r\n        http:\/\/amath.colorado.edu\/documentation\/LaTeX\/Symbols.pdf \r\n\r\n- Key Helper(`:KeyHelper`):\r\n\r\n        KeyHelper makes viewing and inputting these symbols easier.\r\n\r\n        It will dynamicly showing matching keymap with your input.\r\n        And press '<Enter>' in the KeyHelper window to append to file.\r\n\r\n        And you can input more unicode symbols:\r\n        0x2500-0x2800,  0x1D100 - 0x1D1DD\r\n    \r\n\r\n","4":"This is a vim keymap file contains mathematic symbols.\r\nwith some effort to reduce typing conflict and increase typing speed.\r\n\r\nAlso contains a keyhelper for help inputting.\r\n\r\n- Superscript and Subscript :\r\n\r\n        `0 ⁰  `+ ⁺ ... ( 0-9 + - ( ) \/ ^ . , > < )\r\n        `a ᵃ  `A ᴬ ... ( a-z except q , Some of A-Z)\r\n\r\n        _0 ₀  _+ ₊ ... ( 0-9 + - ( ) \/ ^ )\r\n        _a ₐ  _e ₑ ... (a e h i k l m n o p r s t u v x)\r\n\r\n\r\n- Short CMD  :\r\n\r\n        Greek Alphabet:\r\n                    \\GA  => Α , \\GD   => Δ\r\n                    \\Ga  => α , \\Gg   => γ\r\n\r\n        Fractions   :\r\n                    \\1\/2   => \u00c2\u00bd , \\1\/3 => ⅓\r\n                    \\2\/3   => ⅔ , \\3\/5 => ⅗\r\n\r\n        Arrows      :\r\n                    \\<--   => ←  , \\--v => ↓  , \\==>  => ⇒\r\n                    \\<---  => ⟵  , \\--^ => ↑  , \\===> => ⟹\r\n\r\n        Grouping    : \r\n                    \\(U    => ⎛  , \\]U  => ⎤\r\n                    \\(M    => ⎜  , \\]M  => ⎥\r\n                    \\(B    => ⎝  , \\]B  => ⎦\r\n                    \\(V    => ︵ , \\]V  => ︺\r\n\r\n\r\n        Operator    :\r\n                    \\U.    => ⨃ , \\UU   => ∪  , \\UN  => ∩\r\n                    \\I1    => ∫ , \\I3   => ∭  , \\I=  => ⨎\r\n                    \\IO1   => ∮ , \\IO3  => ∰  , \\IOW => ∳\r\n                    \\PDF   => ∂ , \\THF  => ∴  , \\BCS => ∵\r\n                    \\MUL   => \u00c3\u0097 , \\DIV  => \u00c3\u00b7\r\n                    \\SQRT2 => √ , \\SQRT3 => ∛ , \\SQRT4 => ∜\r\n\r\n        Relations   : \r\n                    \\<=    => ≤ , \\>=  => ≥   , \\!=  => ≠\r\n                    \\<~    => ⪝ , \\>~  => ⪞   , \\!>  => ≯\r\n                    \\o+    => ⊕ , \\o-  => ⊖   , \\ox  => ⊗\r\n                    \\O+    => ⨀ , \\O+  => ⨁   , \\OX  => ⨂\r\n\r\n        Sets        :\r\n                    \\SUBO  => ⊂ , \\SUBE => ⊆  , \\SUBN => ⊄\r\n                    \\SUPO  => ⊃ , \\SUPE => ⊇  , \\SUPX => ⊉\r\n                    \\AND   => ∧ , \\OR   => ∨  , \\NOT  => \u00c2\u00ac\r\n                    \\XOR   => ⊕\r\n                    \\EXTS  => ∃ , \\EXTN => ∄  , \\FALL => ∀\r\n                    \\BOT   => ⊥ , \\TOP => ⊤   , \\LFT  => ⊣\r\n                    \\RGT   => ⊢\r\n\r\n        Misc        :\r\n                    \\INF  => ∞  , \\PRT  => ∝\r\n                    \\ARC   => ⌒ , \\ANG  => ∠\r\n                    \\DEGC  => ℃ , \\DEGF => ℉\r\n                    \\OHM   => Ω , \\MHO  => ℧  , \\ANGS => Å\r\n                    \\a\/c   => ℀ , \\a\/s  => ℁  , \\No   => №\r\n                    \\TM    => \u00e2\u0084\u00a2 , \\CO   => \u00c2\u00a9  , \\RO   => \u00c2\u00ae\r\n                    \\AE    => \u00c3\u0086 , \\ae   => \u00c3\u00a6  , \\fi   => fi\r\n\r\n        Fonts       :\r\n                    \\BBA   => 𝔸 , \\BBH => ℍ   , \\BB0  => 𝟘\r\n                    \\FKH   => ℋ , \\FKI => ℑ   , \\FKL  => ℒ\r\n\r\n\r\n- Latex CMD:\r\n\r\n        Based on Vim-Latex suite.\r\n        Only contains latex command which have corresponding unicode chars.\r\n        Fixed some incorrect mapping of Vim-Latex suite:\r\n        (\\bigodot \\bigoplus \\bigotimes \\long...arrow \\iint ...)\r\n\r\n        e.g: \r\n            \\neq     => ≠  ,  \\Leftarrow =>  ⇐\r\n            \\simeq   => ≃  ,  \\Re        =>  ℜ\r\n            \\mathbbA => 𝔸  ,  \\mathfrakA =>  𝔄\r\n            ...\r\n\r\n        You can use Vim-Latex suite to check these command.\r\n        or this pdf of math symbols.\r\n        http:\/\/amath.colorado.edu\/documentation\/LaTeX\/Symbols.pdf \r\n\r\n- Key Helper(`:KeyHelper`):\r\n\r\n        KeyHelper makes viewing and inputting these symbols easier.\r\n\r\n        It will dynamicly showing matching keymap with your input.\r\n        And press '<Enter>' in the KeyHelper window to append to file.\r\n\r\n        And you can input more unicode symbols:\r\n        0x2500-0x2800,  0x1D100 - 0x1D1DD\r\n    \r\n\r\n","install_details":"Extract to your ~\/.vim folder.\r\n\r\n- You can make a mapping to use it easyier:\r\n   \r\n        \" use it\r\n        map <leader>km :set keymap=mathematic<CR>\r\n        \" stop use it\r\n        map <leader>kn :set keymap=<CR>\r\n        \" view it's details, modify it at your convenience.\r\n        map <leader>kvm :sp ~\/.vim\/keymap\/mathematic.vim<CR>\r\n    \r\n        \" show inputting cmd:\r\n        \" set showcmd\r\n        \" when a longer time for inputting is needed:\r\n        \" set timeoutlen=3000\r\n        \" or disable inputting timeout:\r\n        \" set notimeout\r\n\r\n':h keymap' for further details.\r\n\r\n\r\n- Using KeyHelper: (`:KeyHelper (<leader>\\)`)\r\n\r\n        \" if your mathematic.vim is not in '~\/.vim\/bundle\/' or '~\/.vim\/keymap'\r\n        \" then you should set g:mathematic_user_dir\r\n        \" let g:mathematic_user_dir = \"~\/.vim\/myplug\/keymap\/mathematic.vim\"\r\n        \" map KeyHelper with another mapping\r\n        \" nmap <leader>kk :KeyHelper<CR>\r\n        \" if you want fuzzy matching\r\n        \" let g:mathematic_fuzzymatch = 1\r\n\r\nPost issues and suggestions at https:\/\/github.com\/Rykka\/mathematic.vim.\r\n\r\nTo request adding keymap CMDS , please post CMD and Character.\r\n","5":"Extract to your ~\/.vim folder.\r\n\r\n- You can make a mapping to use it easyier:\r\n   \r\n        \" use it\r\n        map <leader>km :set keymap=mathematic<CR>\r\n        \" stop use it\r\n        map <leader>kn :set keymap=<CR>\r\n        \" view it's details, modify it at your convenience.\r\n        map <leader>kvm :sp ~\/.vim\/keymap\/mathematic.vim<CR>\r\n    \r\n        \" show inputting cmd:\r\n        \" set showcmd\r\n        \" when a longer time for inputting is needed:\r\n        \" set timeoutlen=3000\r\n        \" or disable inputting timeout:\r\n        \" set notimeout\r\n\r\n':h keymap' for further details.\r\n\r\n\r\n- Using KeyHelper: (`:KeyHelper (<leader>\\)`)\r\n\r\n        \" if your mathematic.vim is not in '~\/.vim\/bundle\/' or '~\/.vim\/keymap'\r\n        \" then you should set g:mathematic_user_dir\r\n        \" let g:mathematic_user_dir = \"~\/.vim\/myplug\/keymap\/mathematic.vim\"\r\n        \" map KeyHelper with another mapping\r\n        \" nmap <leader>kk :KeyHelper<CR>\r\n        \" if you want fuzzy matching\r\n        \" let g:mathematic_fuzzymatch = 1\r\n\r\nPost issues and suggestions at https:\/\/github.com\/Rykka\/mathematic.vim.\r\n\r\nTo request adding keymap CMDS , please post CMD and Character.\r\n","first_name":"Rykka","6":"Rykka","last_name":"f","7":"f","releases":[{"0":"4061","vim_version":"7.0","1":"7.0","script_version":"1.10","2":"1.10","version_comment":"-- add  KeyHelper\r\n-- add   symbols  0x2500-0x2800","3":"-- add  KeyHelper\r\n-- add   symbols  0x2500-0x2800","package":"mathematic.vim-1.10.zip","4":"mathematic.vim-1.10.zip","src_id":"17942","5":"17942","creation_date":"1336828951","6":"1336828951"},{"0":"4061","vim_version":"7.0","1":"7.0","script_version":"1.01","2":"1.01","version_comment":"remove duplicated part.","3":"remove duplicated part.","package":"mathematic.vim-1.01.zip","4":"mathematic.vim-1.01.zip","src_id":"17931","5":"17931","creation_date":"1336737115","6":"1336737115"}]},"4060":{"script_id":"4060","0":"4060","script_name":"nosyntaxwords","1":"nosyntaxwords","script_type":"utility","2":"utility","summary":"find words that are not syntactically highlighted in current buffer","3":"find words that are not syntactically highlighted in current buffer","description":"This plugin provides commands to find words that are not syntactically highlighted in current buffer. I mostly used them to debug vim syntax engine \/ ctags \/ plugin TagHighlight etc.\r\n\r\nCommands:\r\n\r\n:NextNoSyntaxWord - find next word that is not syntactically highlighted.\r\n:GetNoSyntaxWords - get list of words that are not syntactically highlighted and show it.\r\n\r\nThe list is stored in buffer variable b:nosyntaxwords and it can be shown again by issuing command\r\n\r\n:echo b:nosyntaxwords\r\n\r\nDue to difference between algorithms 'normal w' and 'expand(\"<cword>\")' that are used in implementation of the plugin, global variable g:NswSkipSymbols was involved. This variable is a dictionary that contains lists of special symbols for specified filetypes that are supposed to be not syntactically highlighted for this filetype and must be skipped when using 'normal w', otherwise they will be included in the list or, even worse (if they do not belong to 'iskeyword' list), following them words will be included in the list.\r\n                                                                           \r\nBy default g:NswSkipSymbols has support for filetypes 'c', 'cpp', 'python', 'perl', 'vim' and 'tagbar', but if needed this can be extended for using with other filetypes, default symbols for a supported filetype can be changed as well. For example, to add support for filetype 'ruby' put in your .vimrc lines\r\n\r\nlet g:NswSkipSymbols = {}\r\nlet g:NswSkipSymbols['ruby'] = ['(', ')']       \" whatever else\r\n\r\nTo use this plugin efficiently i recommend to use following mappings:\r\n\r\nnmap <silent> ,vv  :echo synIDattr(synID(line(\".\"), col(\".\"), 1), \"name\")<CR>\r\nnmap <silent> ,vn  :NextNoSyntaxWord<CR>\r\nnmap <silent> ,vl  :GetNoSyntaxWords<CR>\r\n\r\n(mapping ,vv is for showing syntax class of word under cursor and does not refer directly to this plugin).","4":"This plugin provides commands to find words that are not syntactically highlighted in current buffer. I mostly used them to debug vim syntax engine \/ ctags \/ plugin TagHighlight etc.\r\n\r\nCommands:\r\n\r\n:NextNoSyntaxWord - find next word that is not syntactically highlighted.\r\n:GetNoSyntaxWords - get list of words that are not syntactically highlighted and show it.\r\n\r\nThe list is stored in buffer variable b:nosyntaxwords and it can be shown again by issuing command\r\n\r\n:echo b:nosyntaxwords\r\n\r\nDue to difference between algorithms 'normal w' and 'expand(\"<cword>\")' that are used in implementation of the plugin, global variable g:NswSkipSymbols was involved. This variable is a dictionary that contains lists of special symbols for specified filetypes that are supposed to be not syntactically highlighted for this filetype and must be skipped when using 'normal w', otherwise they will be included in the list or, even worse (if they do not belong to 'iskeyword' list), following them words will be included in the list.\r\n                                                                           \r\nBy default g:NswSkipSymbols has support for filetypes 'c', 'cpp', 'python', 'perl', 'vim' and 'tagbar', but if needed this can be extended for using with other filetypes, default symbols for a supported filetype can be changed as well. For example, to add support for filetype 'ruby' put in your .vimrc lines\r\n\r\nlet g:NswSkipSymbols = {}\r\nlet g:NswSkipSymbols['ruby'] = ['(', ')']       \" whatever else\r\n\r\nTo use this plugin efficiently i recommend to use following mappings:\r\n\r\nnmap <silent> ,vv  :echo synIDattr(synID(line(\".\"), col(\".\"), 1), \"name\")<CR>\r\nnmap <silent> ,vn  :NextNoSyntaxWord<CR>\r\nnmap <silent> ,vl  :GetNoSyntaxWords<CR>\r\n\r\n(mapping ,vv is for showing syntax class of word under cursor and does not refer directly to this plugin).","install_details":"put the script in plugin directory","5":"put the script in plugin directory","first_name":"Alexey","6":"Alexey","last_name":"Radkov","7":"Radkov","releases":[{"0":"4060","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"nosyntaxwords.vim","4":"nosyntaxwords.vim","src_id":"17920","5":"17920","creation_date":"1336652857","6":"1336652857"}]},"4059":{"script_id":"4059","0":"4059","script_name":"DBGPavim","1":"DBGPavim","script_type":"utility","2":"utility","summary":"An improved Python\/PHP debugger","3":"An improved Python\/PHP debugger","description":"This is a plugin to enable php debug in VIM with Xdebug, which originates from http:\/\/www.vim.org\/scripts\/script.php?script_id=1152.\r\nBut most of the code, especially the debugger backend has been rewritten.\r\n\r\n中文文档\r\nhttps:\/\/brookhong.github.io\/2014\/09\/27\/dbgpavim-cn.html\r\n\r\nScreencast --\r\nhttps:\/\/raw.githubusercontent.com\/brookhong\/brookhong.github.io\/master\/assets\/images\/DBGPavim.gif\r\nhttp:\/\/youtu.be\/GY3EcGQvw00\r\n\r\nTested with --\r\n* XDebug 2.2 - PHP 5.4 - GVIM 7.3 - Python 2.7 @ Windows 7\r\n* XDebug 2.0 - PHP 5.2 - VIM 7.3  - Python 2.7@ Linux\r\n* XDebug 2.0 - PHP 5.2 - VIM 7.3  - Python 2.3@ Linux\r\n* XDebug 2.2 - PHP 5.2 - VIM 7.3  - Python 2.7@ Linux\r\n\r\nThe source code is hosted at https:\/\/github.com\/brookhong\/DBGPavim.\r\nSome screenshots (under windows) are here at http:\/\/sharing-from-brook.16002.n6.nabble.com\/Debug-php-in-VIM-with-Xdebug-and-DBGPavim-td4930670.html.\r\n\r\n## The enhancements are --\r\n\r\n### Non blocking debugger backend.\r\nSo that VIM users do not need to wait for connection from apache server. No timeout things, users press F5 to start debugger backend, and uses his\/her VIM normally. Debug backend won't stop users to interact with VIM. Users can press F6 to stop debugger backend anytime.\r\n\r\n### Catch all connections from apache server.\r\nThis is very important for a large website, especially for thoes pages who contain AJAX requests. In that case, one reload of a page may trigger dozens of http request, each of them goes to a different URL. The new debugger backend will catch all connections from apache server. Users can debug all of them without missing anyone.\r\n\r\n### Break only at breakpoints\r\n\r\n    let g:dbgPavimBreakAtEntry = 0\r\n\r\n    The setting will cause debugger backend to break only at breakpoints. Default value is 1, which means it works like before, the debugger backend breaks at entry.\r\n\r\n### New commands and function keys\r\n\r\nIn normal mode\r\n\r\n    <F5>      => start debugger backend\r\n    <F6>      => stop debugger backend\r\n    <F8>      => toggle dbgPavimBreakAtEntry, when g:dbgPavimBreakAtEntry=0, debugger backend breaks only at breakpoints.\r\n\r\n    :Bl        => to list all breakpoints\r\n    :Bp        => toggle breakpoint on current line\r\n\r\nIn debuggin mode \r\n\r\n    <F1>      => toggle help window\r\n    <F2>      => step into \r\n    <F3>      => step over \r\n    <F4>      => step out \r\n    <F5>      => start debugging \/ run\r\n    <F6>      => stop debugging \r\n    <F7>      => evalute expression and display result. cursor is automatically move to watch window. type line and just press enter. \r\n    <F9>      => toggle layout\r\n    <F11>     => shows all variables \r\n    <F12>     => shows variable on current cursor \r\n\r\n    :Pg        => to print value of complex variables like $this->savings[3]\r\n    :Up        => goto upper level of stack \r\n    :Dn        => goto lower level of stack \r\n\r\nIn Watch window\r\n\r\n    If you press Enter key at a line which ends with --\r\n    \r\n    (object)  => to get value of an object.\r\n    (array)   => to get value of an array.\r\n\r\n    If you press Enter key at a line of output from command :Bl, that breakpoint will be located.\r\n\r\nIn Stack window\r\n\r\n    If you press Enter key at a line, stack level will be set.\r\n\r\n### Windows Support\r\n\r\n### Status line for debugger backend\r\n\r\n    After user press <F5> to start debugger backend, a string like \"PHP-bae-LISN\" will show up at the right side of status line.\r\n\r\n    The status string looks like -- \r\n\r\n    PHP-<bae|bap>-<LISN|PENDn|CONN|CLSD>\r\n\r\n    bae       => means Break At Entry\r\n    bap       => means Break only At breakPoints\r\n\r\n    LISN      => means the debugger backend is listening.\r\n    PENDn     => means there are n connections waiting for debugging.\r\n    CONN      => means debug session has been established, and being debugged.\r\n    CLSD      => means the debugger backend has stopped.\r\n\r\n### New layout of windows\r\n\r\n### Remote debugging\r\n\r\nIn case that you need run VIM on a different machine from server where apache httpd runs, configuration for DBGPavim --\r\n\r\n    let g:dbgPavimPathMap = [['D:\/works\/php','\/var\/www'],]\r\n\r\nSome change for Apache configuration is also necessary --\r\n\r\n    php_value xdebug.remote_host <ip_address_where_you_run_vim>\r\n\r\n## Usage\r\n\r\n* Make sure your vim has python(at least 2.3) supported, in vim with command\r\n\r\n    :version\r\n\r\n    In case of your VIM don't support python, download VIM source package from http:\/\/www.vim.org\/download.php, then build your own VIM with commands --\r\n\r\n    .\/configure --prefix=\/opt\/vim --enable-pythoninterp --with-python-config-dir=\/usr\/lib\/python2.4\/config\r\n    make\r\n    make install\r\n\r\n* Install xdebug for php, and edit php.ini\r\n\r\n    zend_extension=path_to_xdebug.so\r\n    xdebug.remote_enable=1\r\n\r\n* Edit your ~\/.vimrc\r\n\r\n    let g:dbgPavimPort = 9009\r\n    let g:dbgPavimBreakAtEntry = 0\r\n\r\n* Edit your apche configure file\r\n\r\n    In your VirtualHost section, set debugger port same as the one in your vimrc\r\n\r\n    php_value xdebug.remote_port 9009\r\n\r\n* Save debugger.py and debugger.vim to your ~\/.vim\/plugin\r\n\r\n* Open your php file, use :Bp to set breakpoints\r\n\r\n* Now, press F5 to start debugger backend\r\n\r\n* Back to your browser, add XDEBUG_SESSION_START=1 to your URL, for example, http:\/\/localhost\/index.php?XDEBUG_SESSION_START=1. If you would like to debug from CLI, start your php script like \r\n\r\n    php -dxdebug.remote_autostart=1 -dxdebug.remote_port=9009 test.php\r\n\r\nIf you are tied of adding XDEBUG_SESSION_START=1 in query string, there is a XDEBUG_SESSION helper at http:\/\/userscripts.org\/scripts\/review\/132695, a user script for Google Chrome. It also works for Firefox with help of GreaseMonkey.","4":"This is a plugin to enable php debug in VIM with Xdebug, which originates from http:\/\/www.vim.org\/scripts\/script.php?script_id=1152.\r\nBut most of the code, especially the debugger backend has been rewritten.\r\n\r\n中文文档\r\nhttps:\/\/brookhong.github.io\/2014\/09\/27\/dbgpavim-cn.html\r\n\r\nScreencast --\r\nhttps:\/\/raw.githubusercontent.com\/brookhong\/brookhong.github.io\/master\/assets\/images\/DBGPavim.gif\r\nhttp:\/\/youtu.be\/GY3EcGQvw00\r\n\r\nTested with --\r\n* XDebug 2.2 - PHP 5.4 - GVIM 7.3 - Python 2.7 @ Windows 7\r\n* XDebug 2.0 - PHP 5.2 - VIM 7.3  - Python 2.7@ Linux\r\n* XDebug 2.0 - PHP 5.2 - VIM 7.3  - Python 2.3@ Linux\r\n* XDebug 2.2 - PHP 5.2 - VIM 7.3  - Python 2.7@ Linux\r\n\r\nThe source code is hosted at https:\/\/github.com\/brookhong\/DBGPavim.\r\nSome screenshots (under windows) are here at http:\/\/sharing-from-brook.16002.n6.nabble.com\/Debug-php-in-VIM-with-Xdebug-and-DBGPavim-td4930670.html.\r\n\r\n## The enhancements are --\r\n\r\n### Non blocking debugger backend.\r\nSo that VIM users do not need to wait for connection from apache server. No timeout things, users press F5 to start debugger backend, and uses his\/her VIM normally. Debug backend won't stop users to interact with VIM. Users can press F6 to stop debugger backend anytime.\r\n\r\n### Catch all connections from apache server.\r\nThis is very important for a large website, especially for thoes pages who contain AJAX requests. In that case, one reload of a page may trigger dozens of http request, each of them goes to a different URL. The new debugger backend will catch all connections from apache server. Users can debug all of them without missing anyone.\r\n\r\n### Break only at breakpoints\r\n\r\n    let g:dbgPavimBreakAtEntry = 0\r\n\r\n    The setting will cause debugger backend to break only at breakpoints. Default value is 1, which means it works like before, the debugger backend breaks at entry.\r\n\r\n### New commands and function keys\r\n\r\nIn normal mode\r\n\r\n    <F5>      => start debugger backend\r\n    <F6>      => stop debugger backend\r\n    <F8>      => toggle dbgPavimBreakAtEntry, when g:dbgPavimBreakAtEntry=0, debugger backend breaks only at breakpoints.\r\n\r\n    :Bl        => to list all breakpoints\r\n    :Bp        => toggle breakpoint on current line\r\n\r\nIn debuggin mode \r\n\r\n    <F1>      => toggle help window\r\n    <F2>      => step into \r\n    <F3>      => step over \r\n    <F4>      => step out \r\n    <F5>      => start debugging \/ run\r\n    <F6>      => stop debugging \r\n    <F7>      => evalute expression and display result. cursor is automatically move to watch window. type line and just press enter. \r\n    <F9>      => toggle layout\r\n    <F11>     => shows all variables \r\n    <F12>     => shows variable on current cursor \r\n\r\n    :Pg        => to print value of complex variables like $this->savings[3]\r\n    :Up        => goto upper level of stack \r\n    :Dn        => goto lower level of stack \r\n\r\nIn Watch window\r\n\r\n    If you press Enter key at a line which ends with --\r\n    \r\n    (object)  => to get value of an object.\r\n    (array)   => to get value of an array.\r\n\r\n    If you press Enter key at a line of output from command :Bl, that breakpoint will be located.\r\n\r\nIn Stack window\r\n\r\n    If you press Enter key at a line, stack level will be set.\r\n\r\n### Windows Support\r\n\r\n### Status line for debugger backend\r\n\r\n    After user press <F5> to start debugger backend, a string like \"PHP-bae-LISN\" will show up at the right side of status line.\r\n\r\n    The status string looks like -- \r\n\r\n    PHP-<bae|bap>-<LISN|PENDn|CONN|CLSD>\r\n\r\n    bae       => means Break At Entry\r\n    bap       => means Break only At breakPoints\r\n\r\n    LISN      => means the debugger backend is listening.\r\n    PENDn     => means there are n connections waiting for debugging.\r\n    CONN      => means debug session has been established, and being debugged.\r\n    CLSD      => means the debugger backend has stopped.\r\n\r\n### New layout of windows\r\n\r\n### Remote debugging\r\n\r\nIn case that you need run VIM on a different machine from server where apache httpd runs, configuration for DBGPavim --\r\n\r\n    let g:dbgPavimPathMap = [['D:\/works\/php','\/var\/www'],]\r\n\r\nSome change for Apache configuration is also necessary --\r\n\r\n    php_value xdebug.remote_host <ip_address_where_you_run_vim>\r\n\r\n## Usage\r\n\r\n* Make sure your vim has python(at least 2.3) supported, in vim with command\r\n\r\n    :version\r\n\r\n    In case of your VIM don't support python, download VIM source package from http:\/\/www.vim.org\/download.php, then build your own VIM with commands --\r\n\r\n    .\/configure --prefix=\/opt\/vim --enable-pythoninterp --with-python-config-dir=\/usr\/lib\/python2.4\/config\r\n    make\r\n    make install\r\n\r\n* Install xdebug for php, and edit php.ini\r\n\r\n    zend_extension=path_to_xdebug.so\r\n    xdebug.remote_enable=1\r\n\r\n* Edit your ~\/.vimrc\r\n\r\n    let g:dbgPavimPort = 9009\r\n    let g:dbgPavimBreakAtEntry = 0\r\n\r\n* Edit your apche configure file\r\n\r\n    In your VirtualHost section, set debugger port same as the one in your vimrc\r\n\r\n    php_value xdebug.remote_port 9009\r\n\r\n* Save debugger.py and debugger.vim to your ~\/.vim\/plugin\r\n\r\n* Open your php file, use :Bp to set breakpoints\r\n\r\n* Now, press F5 to start debugger backend\r\n\r\n* Back to your browser, add XDEBUG_SESSION_START=1 to your URL, for example, http:\/\/localhost\/index.php?XDEBUG_SESSION_START=1. If you would like to debug from CLI, start your php script like \r\n\r\n    php -dxdebug.remote_autostart=1 -dxdebug.remote_port=9009 test.php\r\n\r\nIf you are tied of adding XDEBUG_SESSION_START=1 in query string, there is a XDEBUG_SESSION helper at http:\/\/userscripts.org\/scripts\/review\/132695, a user script for Google Chrome. It also works for Firefox with help of GreaseMonkey.","install_details":"Just unzip the zip file to your VIM file path, usually to be ~\/.vim.\r\n","5":"Just unzip the zip file to your VIM file path, usually to be ~\/.vim.\r\n","first_name":"brook","6":"brook","last_name":"hong","7":"hong","releases":[{"0":"4059","vim_version":"7.2","1":"7.2","script_version":"1.07","2":"1.07","version_comment":"1. Disable all breakpoints with :Bc & Enable all breakpoints with :Bu\r\n2. load dbgpavim.py on demand to speed up vim startup\r\n3. fix some bugs\r\n","3":"1. Disable all breakpoints with :Bc & Enable all breakpoints with :Bu\r\n2. load dbgpavim.py on demand to speed up vim startup\r\n3. fix some bugs\r\n","package":"DBGPavim.zip","4":"DBGPavim.zip","src_id":"21841","5":"21841","creation_date":"1398776864","6":"1398776864"},{"0":"4059","vim_version":"7.2","1":"7.2","script_version":"1.06","2":"1.06","version_comment":"1. fix error for getting value in array whose key name contains space\r\n2. avoid accidental hangs when exiting\r\n3. fix bug to remove breakpoint in debugging\r\n4. show classname when debugging php\r\n5. g:dbgPavimOnce=1 to let your site accessible when debugging\r\n6. ratio for windows width\/height\r\n7. enable customization of mapping for windows resize and highlight settings","3":"1. fix error for getting value in array whose key name contains space\r\n2. avoid accidental hangs when exiting\r\n3. fix bug to remove breakpoint in debugging\r\n4. show classname when debugging php\r\n5. g:dbgPavimOnce=1 to let your site accessible when debugging\r\n6. ratio for windows width\/height\r\n7. enable customization of mapping for windows resize and highlight settings","package":"DBGPavim.zip","4":"DBGPavim.zip","src_id":"20399","5":"20399","creation_date":"1371916313","6":"1371916313"},{"0":"4059","vim_version":"7.2","1":"7.2","script_version":"1.05","2":"1.05","version_comment":"1. object\/array expansion inline in watch window\r\n2. list breakpoints to location list\r\n3. some bug fixes\r\n","3":"1. object\/array expansion inline in watch window\r\n2. list breakpoints to location list\r\n3. some bug fixes\r\n","package":"DBGPavim.zip","4":"DBGPavim.zip","src_id":"19372","5":"19372","creation_date":"1358178577","6":"1358178577"},{"0":"4059","vim_version":"7.2","1":"7.2","script_version":"1.04","2":"1.04","version_comment":"1. pretty output in watch window for python debugging\r\n2. user friendly notice of exception\r\n3. :We [foo]  => to eval expression `foo` automatically after each step","3":"1. pretty output in watch window for python debugging\r\n2. user friendly notice of exception\r\n3. :We [foo]  => to eval expression `foo` automatically after each step","package":"DBGPavim.zip","4":"DBGPavim.zip","src_id":"19017","5":"19017","creation_date":"1353639936","6":"1353639936"},{"0":"4059","vim_version":"7.2","1":"7.2","script_version":"1.03","2":"1.03","version_comment":"1. :Wc $foo to toggle watch on variable $foo, :Wl to list watched variables\r\n2. customizable key mappings\r\n3. keep other tabs intact after debugging completed\r\n4. bug fix for windows\r\n","3":"1. :Wc $foo to toggle watch on variable $foo, :Wl to list watched variables\r\n2. customizable key mappings\r\n3. keep other tabs intact after debugging completed\r\n4. bug fix for windows\r\n","package":"DBGPavim.zip","4":"DBGPavim.zip","src_id":"18810","5":"18810","creation_date":"1350306685","6":"1350306685"},{"0":"4059","vim_version":"7.2","1":"7.2","script_version":"1.02","2":"1.02","version_comment":"1. dbgPavimBreakAtEntry default as 0, so it will not break at entry by default.\r\n2. doc for python debugging\r\n3. :Dp command to debug current file from CLI\r\n","3":"1. dbgPavimBreakAtEntry default as 0, so it will not break at entry by default.\r\n2. doc for python debugging\r\n3. :Dp command to debug current file from CLI\r\n","package":"DBGPavim.zip","4":"DBGPavim.zip","src_id":"18692","5":"18692","creation_date":"1348670790","6":"1348670790"},{"0":"4059","vim_version":"7.2","1":"7.2","script_version":"1.01","2":"1.01","version_comment":"1. remote debugging support\r\n2. doc embeded\r\n3. rename all global parameters from g:debuggerXXXX to g:dbgPavimXXXX\r\n","3":"1. remote debugging support\r\n2. doc embeded\r\n3. rename all global parameters from g:debuggerXXXX to g:dbgPavimXXXX\r\n","package":"DBGPavim.zip","4":"DBGPavim.zip","src_id":"17974","5":"17974","creation_date":"1337174647","6":"1337174647"},{"0":"4059","vim_version":"7.2","1":"7.2","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"DBGPavim.zip","4":"DBGPavim.zip","src_id":"17919","5":"17919","creation_date":"1336652647","6":"1336652647"}]},"4058":{"script_id":"4058","0":"4058","script_name":"jsflakes","1":"jsflakes","script_type":"ftplugin","2":"ftplugin","summary":"check errors for javascript on the fly","3":"check errors for javascript on the fly","description":"duplicate scripts, sry, my fault i'm unable to delete it\r\n\r\nplease follow this script\r\n\r\nhttp:\/\/www.vim.org\/scripts\/script.php?script_id=4057","4":"duplicate scripts, sry, my fault i'm unable to delete it\r\n\r\nplease follow this script\r\n\r\nhttp:\/\/www.vim.org\/scripts\/script.php?script_id=4057","install_details":"put to ftplugin","5":"put to ftplugin","first_name":"yf","6":"yf","last_name":"liu","7":"liu","releases":[{"0":"4058","vim_version":"7.0","1":"7.0","script_version":"1.1","2":"1.1","version_comment":"switch to use location list instead of quickfix","3":"switch to use location list instead of quickfix","package":"jsflakes.zip","4":"jsflakes.zip","src_id":"18005","5":"18005","creation_date":"1337595392","6":"1337595392"},{"0":"4058","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"upload","3":"upload","package":"jsflakes.zip","4":"jsflakes.zip","src_id":"17965","5":"17965","creation_date":"1337081391","6":"1337081391"}]},"4057":{"script_id":"4057","0":"4057","script_name":"jsflakes.vim","1":"jsflakes.vim","script_type":"ftplugin","2":"ftplugin","summary":"A powerful vim plugin lint javascript code on the fly","3":"A powerful vim plugin lint javascript code on the fly","description":"Watch live video: http:\/\/michalliu.github.com\/jsflakes.vim\/jsflakes.html\r\n\r\nFor javascript file, jsflakes will automaticlly check errors in your code while you editing.\r\n\r\nIf you don't like this behaviour. You can toggle the Automatic Lint by <Leader>al , your vim's <Leader> is often \\.\r\n\r\nThe command to run jshint manaually is \r\n\r\n:JSHint\r\n\r\nThe current errors are added to the window's location list. You can aslo use quickfix commands, like\r\n\r\n:lli list errors in your javascript code\r\n:lopen open location window\r\n\r\n\r\nAdvance Usage\r\nJsflakes aslo support html file, add following to your vimrc\r\n\r\nau FileType html source $VIM\\vimfiles\\ftplugin\\javascript\\jsflakes.vim\r\nJsflakes use jslint to check errors. Jslint has many options, Jslint option file should be at ~\/.jshintrc by default. your can change it to other location by adding following line to your vimrc\r\n\r\nlet g:jshint_rcfile = {PATH}\r\nJsflakes aslo provide commands to run javascript directly inside VIM\r\n\r\nRunJS\r\n\r\n:RunJS   run javascript code\r\nRunJSBlock\r\n\r\n:RunJS 1,2  run javascript code from line 1 to line 2\r\nRunHtml\r\n\r\n:RunHtml   run html code\r\nRunHtmlBlock\r\n\r\n:RunHtmlBlock 1,2  run html code from line 1 to line 2","4":"Watch live video: http:\/\/michalliu.github.com\/jsflakes.vim\/jsflakes.html\r\n\r\nFor javascript file, jsflakes will automaticlly check errors in your code while you editing.\r\n\r\nIf you don't like this behaviour. You can toggle the Automatic Lint by <Leader>al , your vim's <Leader> is often \\.\r\n\r\nThe command to run jshint manaually is \r\n\r\n:JSHint\r\n\r\nThe current errors are added to the window's location list. You can aslo use quickfix commands, like\r\n\r\n:lli list errors in your javascript code\r\n:lopen open location window\r\n\r\n\r\nAdvance Usage\r\nJsflakes aslo support html file, add following to your vimrc\r\n\r\nau FileType html source $VIM\\vimfiles\\ftplugin\\javascript\\jsflakes.vim\r\nJsflakes use jslint to check errors. Jslint has many options, Jslint option file should be at ~\/.jshintrc by default. your can change it to other location by adding following line to your vimrc\r\n\r\nlet g:jshint_rcfile = {PATH}\r\nJsflakes aslo provide commands to run javascript directly inside VIM\r\n\r\nRunJS\r\n\r\n:RunJS   run javascript code\r\nRunJSBlock\r\n\r\n:RunJS 1,2  run javascript code from line 1 to line 2\r\nRunHtml\r\n\r\n:RunHtml   run html code\r\nRunHtmlBlock\r\n\r\n:RunHtmlBlock 1,2  run html code from line 1 to line 2","install_details":"this plugin requires jsruntime http:\/\/www.vim.org\/scripts\/script.php?script_id=4050 and jsoncodecs http:\/\/www.vim.org\/scripts\/script.php?script_id=4056 installed\r\n\r\nput jsflakes to $VIM\/ftplugin\r\n\r\nyou should enable file type plugin by add following lines to your vimrc\r\n\r\n filetype on\r\n filetype plugin on","5":"this plugin requires jsruntime http:\/\/www.vim.org\/scripts\/script.php?script_id=4050 and jsoncodecs http:\/\/www.vim.org\/scripts\/script.php?script_id=4056 installed\r\n\r\nput jsflakes to $VIM\/ftplugin\r\n\r\nyou should enable file type plugin by add following lines to your vimrc\r\n\r\n filetype on\r\n filetype plugin on","first_name":"yf","6":"yf","last_name":"liu","7":"liu","releases":[{"0":"4057","vim_version":"7.0","1":"7.0","script_version":"1.5","2":"1.5","version_comment":"switch to use linux line endings","3":"switch to use linux line endings","package":"jsflakes.zip","4":"jsflakes.zip","src_id":"18048","5":"18048","creation_date":"1338121398","6":"1338121398"},{"0":"4057","vim_version":"7.0","1":"7.0","script_version":"1.4","2":"1.4","version_comment":"sometimes It's very annoying when automatic lint is enabled, now you can toggle the auto lint by <Leader>al\r\nthis version aslo fix some encoding errors\r\n","3":"sometimes It's very annoying when automatic lint is enabled, now you can toggle the auto lint by <Leader>al\r\nthis version aslo fix some encoding errors\r\n","package":"jsflakes.zip","4":"jsflakes.zip","src_id":"18029","5":"18029","creation_date":"1337860666","6":"1337860666"},{"0":"4057","vim_version":"7.0","1":"7.0","script_version":"1.3","2":"1.3","version_comment":"switch to use location list instead of quick fix, thanks Doug McInnes","3":"switch to use location list instead of quick fix, thanks Doug McInnes","package":"jsflakes.zip","4":"jsflakes.zip","src_id":"18006","5":"18006","creation_date":"1337595520","6":"1337595520"},{"0":"4057","vim_version":"7.0","1":"7.0","script_version":"1.2","2":"1.2","version_comment":"1. update jslint to latest\r\n2. improve user exprience\r\n3. handle HTML parse exception","3":"1. update jslint to latest\r\n2. improve user exprience\r\n3. handle HTML parse exception","package":"jsflakes.zip","4":"jsflakes.zip","src_id":"17964","5":"17964","creation_date":"1337081341","6":"1337081341"},{"0":"4057","vim_version":"7.0","1":"7.0","script_version":"1.1","2":"1.1","version_comment":"fix unix path issue","3":"fix unix path issue","package":"jsflakes.zip","4":"jsflakes.zip","src_id":"17922","5":"17922","creation_date":"1336708240","6":"1336708240"},{"0":"4057","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"repacking","3":"repacking","package":"jsflakes.zip","4":"jsflakes.zip","src_id":"17917","5":"17917","creation_date":"1336638237","6":"1336638237"}]},"4056":{"script_id":"4056","0":"4056","script_name":"jsoncodecs.vim","1":"jsoncodecs.vim","script_type":"utility","2":"utility","summary":"Dumps lines from vim to a valid JSON string","3":"Dumps lines from vim to a valid JSON string","description":"Use g:loaded_jsoncodecs to check whether jsoncodecs is loaded\r\n\r\nSample code \r\n    if exists(\\\"g:loaded_jsoncodecs\\\")\r\n        \/\/ do what you like\r\n    endif\r\n\r\n\r\n\r\nIt provide the following functions\r\n\r\n1. b:json_dump_string({lines})\r\n\r\n    This functions take a list contains lines as input, output is a valid JSON string\r\n\r\n2.  b:json_dumplines\r\n\r\n     This is a utility function print out the result from json_dump_string\r\n\r\n     :1,$call b:json_dumplines()","4":"Use g:loaded_jsoncodecs to check whether jsoncodecs is loaded\r\n\r\nSample code \r\n    if exists(\\\"g:loaded_jsoncodecs\\\")\r\n        \/\/ do what you like\r\n    endif\r\n\r\n\r\n\r\nIt provide the following functions\r\n\r\n1. b:json_dump_string({lines})\r\n\r\n    This functions take a list contains lines as input, output is a valid JSON string\r\n\r\n2.  b:json_dumplines\r\n\r\n     This is a utility function print out the result from json_dump_string\r\n\r\n     :1,$call b:json_dumplines()","install_details":"put to $VIM\/plugin","5":"put to $VIM\/plugin","first_name":"yf","6":"yf","last_name":"liu","7":"liu","releases":[{"0":"4056","vim_version":"7.0","1":"7.0","script_version":"1.2","2":"1.2","version_comment":"switch to use linux line endings","3":"switch to use linux line endings","package":"jsoncodecs.zip","4":"jsoncodecs.zip","src_id":"18046","5":"18046","creation_date":"1338121232","6":"1338121232"},{"0":"4056","vim_version":"7.0","1":"7.0","script_version":"1.1","2":"1.1","version_comment":"code optimazation","3":"code optimazation","package":"jsoncodecs.zip","4":"jsoncodecs.zip","src_id":"17966","5":"17966","creation_date":"1337081967","6":"1337081967"},{"0":"4056","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"jsoncodecs.zip","4":"jsoncodecs.zip","src_id":"17913","5":"17913","creation_date":"1336636063","6":"1336636063"}]},"4055":{"script_id":"4055","0":"4055","script_name":"TimeTap","1":"TimeTap","script_type":"utility","2":"utility","summary":"TimeTap helps you track the time you spend coding on each project while in Vim.","3":"TimeTap helps you track the time you spend coding on each project while in Vim.","description":"\r\nOnce it's launched you don't have to bother anymore starting\/stopping timers or inventing some arbitrary amount of time to fill your fancy time tracker.\r\n\r\nDownload the latest version at https:\/\/github.com\/rainerborene\/vim-timetap","4":"\r\nOnce it's launched you don't have to bother anymore starting\/stopping timers or inventing some arbitrary amount of time to fill your fancy time tracker.\r\n\r\nDownload the latest version at https:\/\/github.com\/rainerborene\/vim-timetap","install_details":"\r\nIf you don't have a preferred installation method, I recommend installing pathogen.vim, and the simply copy and paste:\r\n\r\ngit clone git:\/\/github.com\/rainerborene\/vim-timetap.git ~\/.vim\/bundle\/timetap","5":"\r\nIf you don't have a preferred installation method, I recommend installing pathogen.vim, and the simply copy and paste:\r\n\r\ngit clone git:\/\/github.com\/rainerborene\/vim-timetap.git ~\/.vim\/bundle\/timetap","first_name":"Rainer","6":"Rainer","last_name":"Borene","7":"Borene","releases":[{"0":"4055","vim_version":"7.3","1":"7.3","script_version":"0.1.0","2":"0.1.0","version_comment":"Initial upload","3":"Initial upload","package":"timetap.zip","4":"timetap.zip","src_id":"17905","5":"17905","creation_date":"1336486466","6":"1336486466"}]},"4054":{"script_id":"4054","0":"4054","script_name":"PHPUnit QF","1":"PHPUnit QF","script_type":"utility","2":"utility","summary":"Run PHPUnit tests from within vim and put the errors into the quickfix list.","3":"Run PHPUnit tests from within vim and put the errors into the quickfix list.","description":"----------------------------------\r\nPHPUnit runner for Vim\r\n----------------------------------\r\n\r\nPHPUnitQf is a plugin for Vim that allows you to run PHPUnit tests easily from the Vim window. It then reads the output and puts the errors into the quickfix list, so you can easily jump to them. It's configurable too, so if you use a PHPUnit wrapper command or have a special set of arguments, then that's no problem.\r\n\r\nHow to use\r\n----------------\r\n\r\nIn a Vim window, run:\r\n\r\n:Test <args>\r\nWhere <args> are passed directly to the PHPUnit command. To set up a custom PHPUnit command see the configuration section below. You can also set default arguments which will always be passed.\r\n\r\nConfiguration\r\n-------------------\r\n\r\nBy default, the command used to run PHPUnit is phpunit, but you can change it in your vimrc file with:\r\n\r\nlet g:phpunit_cmd = \"\/usr\/bin\/mytest\"\r\nTo pass arguments to the command, use:\r\n\r\nlet g:phpunit_args = \"--configuration \/path\/to\/config\"\r\nYou can also specify arguments to be placed after the \"dynamic\" argument (the argument passed when running from within Vim):\r\n\r\nlet g:phpunit_args_append = \"--repeat\"\r\nThe output is written to a temporary file. You can change the location of this (default value is \/tmp\/vim_phpunit.out) with:\r\n\r\nlet g:phpunit_tmpfile = \"\/my\/new\/tmp\/file\"\r\n\r\nSource\r\n----------\r\n\r\nThe source code is hosted at Github: https:\/\/github.com\/joonty\/vim-phpunitqf\r\n\r\nLicense\r\n-----------\r\n\r\nThis plugin is released under the MIT License.","4":"----------------------------------\r\nPHPUnit runner for Vim\r\n----------------------------------\r\n\r\nPHPUnitQf is a plugin for Vim that allows you to run PHPUnit tests easily from the Vim window. It then reads the output and puts the errors into the quickfix list, so you can easily jump to them. It's configurable too, so if you use a PHPUnit wrapper command or have a special set of arguments, then that's no problem.\r\n\r\nHow to use\r\n----------------\r\n\r\nIn a Vim window, run:\r\n\r\n:Test <args>\r\nWhere <args> are passed directly to the PHPUnit command. To set up a custom PHPUnit command see the configuration section below. You can also set default arguments which will always be passed.\r\n\r\nConfiguration\r\n-------------------\r\n\r\nBy default, the command used to run PHPUnit is phpunit, but you can change it in your vimrc file with:\r\n\r\nlet g:phpunit_cmd = \"\/usr\/bin\/mytest\"\r\nTo pass arguments to the command, use:\r\n\r\nlet g:phpunit_args = \"--configuration \/path\/to\/config\"\r\nYou can also specify arguments to be placed after the \"dynamic\" argument (the argument passed when running from within Vim):\r\n\r\nlet g:phpunit_args_append = \"--repeat\"\r\nThe output is written to a temporary file. You can change the location of this (default value is \/tmp\/vim_phpunit.out) with:\r\n\r\nlet g:phpunit_tmpfile = \"\/my\/new\/tmp\/file\"\r\n\r\nSource\r\n----------\r\n\r\nThe source code is hosted at Github: https:\/\/github.com\/joonty\/vim-phpunitqf\r\n\r\nLicense\r\n-----------\r\n\r\nThis plugin is released under the MIT License.","install_details":"Installation is easy-peasy if you're using Vundle. Just add this to your .vimrc file:\r\n\r\nBundle 'joonty\/vim-phpunitqf.git'\r\nand run vim +BundleInstall +qall from a terminal.\r\n\r\nIf you aren't using vundle, you will have to extract the files in each folder to the correct folder in .vim\/.\r\n\r\nNote: your vim installation must be compiled with python for this plugin to work.","5":"Installation is easy-peasy if you're using Vundle. Just add this to your .vimrc file:\r\n\r\nBundle 'joonty\/vim-phpunitqf.git'\r\nand run vim +BundleInstall +qall from a terminal.\r\n\r\nIf you aren't using vundle, you will have to extract the files in each folder to the correct folder in .vim\/.\r\n\r\nNote: your vim installation must be compiled with python for this plugin to work.","first_name":"Jon","6":"Jon","last_name":"Cairns","7":"Cairns","releases":[{"0":"4054","vim_version":"7.0","1":"7.0","script_version":"0.3","2":"0.3","version_comment":"Added support for callbacks, to allow for dynamic argument modification.","3":"Added support for callbacks, to allow for dynamic argument modification.","package":"phpunitqf-0.3.tar.gz","4":"phpunitqf-0.3.tar.gz","src_id":"18018","5":"18018","creation_date":"1337701917","6":"1337701917"},{"0":"4054","vim_version":"6.0","1":"6.0","script_version":"0.2","2":"0.2","version_comment":"Fixed a couple of nasty bugs with line matching and error log persistence","3":"Fixed a couple of nasty bugs with line matching and error log persistence","package":"phpunitqf-0.2.tar.gz","4":"phpunitqf-0.2.tar.gz","src_id":"17907","5":"17907","creation_date":"1336490206","6":"1336490206"},{"0":"4054","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"phpunitqf-0.1.tar.gz","4":"phpunitqf-0.1.tar.gz","src_id":"17904","5":"17904","creation_date":"1336485171","6":"1336485171"}]},"4053":{"script_id":"4053","0":"4053","script_name":"Transpose","1":"Transpose","script_type":"utility","2":"utility","summary":"Swap lines with columns in matrices of text, delimited text, etc.","3":"Swap lines with columns in matrices of text, delimited text, etc.","description":"This plugin performs transposition (in the sense of matrix transposition) on your input.\r\n\r\n123\r\n456\r\n789\r\n\r\nTranspose the above array and get\r\n\r\n147\r\n258\r\n369\r\n\r\nProvided commands can transpose:\r\n\r\n* Arrays of individual characters\r\n* Arrays of tabulation-separated fields\r\n* Arrays with a delimiter (CSV, default delimiter being a semicolon)\r\n* Arrays of words (whitespace-separated fields)\r\n* Arrays with delimiters of your choice with a provided vim search pattern\r\n\r\nScreenshots and development available at https:\/\/github.com\/salsifis\/vim-transpose\r\n\r\nRun :help transpose-tutorial after installing and generating help tags.","4":"This plugin performs transposition (in the sense of matrix transposition) on your input.\r\n\r\n123\r\n456\r\n789\r\n\r\nTranspose the above array and get\r\n\r\n147\r\n258\r\n369\r\n\r\nProvided commands can transpose:\r\n\r\n* Arrays of individual characters\r\n* Arrays of tabulation-separated fields\r\n* Arrays with a delimiter (CSV, default delimiter being a semicolon)\r\n* Arrays of words (whitespace-separated fields)\r\n* Arrays with delimiters of your choice with a provided vim search pattern\r\n\r\nScreenshots and development available at https:\/\/github.com\/salsifis\/vim-transpose\r\n\r\nRun :help transpose-tutorial after installing and generating help tags.","install_details":"","5":"","first_name":"Benoit","6":"Benoit","last_name":"Mortgat","7":"Mortgat","releases":[{"0":"4053","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"CSV: Allow override of default separator\r\nUpdate '< and '> marks when transposing\r\nAllow some commands to be chained","3":"CSV: Allow override of default separator\r\nUpdate '< and '> marks when transposing\r\nAllow some commands to be chained","package":"Transpose.7z","4":"Transpose.7z","src_id":"23473","5":"23473","creation_date":"1437029459","6":"1437029459"},{"0":"4053","vim_version":"7.0","1":"7.0","script_version":"0.3","2":"0.3","version_comment":"Fixed additional line appearing when transposing whole buffer","3":"Fixed additional line appearing when transposing whole buffer","package":"Transpose.tar.gz","4":"Transpose.tar.gz","src_id":"17927","5":"17927","creation_date":"1336725513","6":"1336725513"},{"0":"4053","vim_version":"7.0","1":"7.0","script_version":"0.2","2":"0.2","version_comment":"Fixed invalid tokenization of empty lines.","3":"Fixed invalid tokenization of empty lines.","package":"transpose.tar.gz","4":"transpose.tar.gz","src_id":"17910","5":"17910","creation_date":"1336582176","6":"1336582176"},{"0":"4053","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"transpose.tar.gz","4":"transpose.tar.gz","src_id":"17903","5":"17903","creation_date":"1336484198","6":"1336484198"}]},"4052":{"script_id":"4052","0":"4052","script_name":"vim-mou","1":"vim-mou","script_type":"ftplugin","2":"ftplugin","summary":"Preview Makrdown file with Mou.app","3":"Preview Makrdown file with Mou.app","description":"You can preview markdown file with Mou.app\r\n\r\nOpen current file with Mou.app\r\n:MouOpen\r\n\r\nClose\r\n:MouQuit\r\n\r\nhttps:\/\/github.com\/cfddream\/vim-mou","4":"You can preview markdown file with Mou.app\r\n\r\nOpen current file with Mou.app\r\n:MouOpen\r\n\r\nClose\r\n:MouQuit\r\n\r\nhttps:\/\/github.com\/cfddream\/vim-mou","install_details":"MacOSX","5":"MacOSX","first_name":"FangDun","6":"FangDun","last_name":"Cai","7":"Cai","releases":[{"0":"4052","vim_version":"7.0","1":"7.0","script_version":"0.0.1","2":"0.0.1","version_comment":"Initial upload","3":"Initial upload","package":"vim-mou.tar.gz","4":"vim-mou.tar.gz","src_id":"17891","5":"17891","creation_date":"1336386138","6":"1336386138"}]},"4051":{"script_id":"4051","0":"4051","script_name":"maven-plugin","1":"maven-plugin","script_type":"utility","2":"utility","summary":"Help development in Maven","3":"Help development in Maven","description":"Check the repository of GitHub to get the newest source:\r\nhttps:\/\/github.com\/mikelue\/vim-maven-plugin","4":"Check the repository of GitHub to get the newest source:\r\nhttps:\/\/github.com\/mikelue\/vim-maven-plugin","install_details":"Check the repository of GitHub to get the newest source:\r\nhttps:\/\/github.com\/mikelue\/vim-maven-plugin","5":"Check the repository of GitHub to get the newest source:\r\nhttps:\/\/github.com\/mikelue\/vim-maven-plugin","first_name":"Mike","6":"Mike","last_name":"Lue","7":"Lue","releases":[{"0":"4051","vim_version":"7.4","1":"7.4","script_version":"1.1","2":"1.1","version_comment":"* Improve the sorting for search paths\r\n* Improve sorting of |maven#getListOfPaths()|\r\n* Improve command |:MvnNewMainFile| and |:MvnNewTestFile|\r\n* Merge modifications by richox <richselian@gmail.com>","3":"* Improve the sorting for search paths\r\n* Improve sorting of |maven#getListOfPaths()|\r\n* Improve command |:MvnNewMainFile| and |:MvnNewTestFile|\r\n* Merge modifications by richox <richselian@gmail.com>","package":"vim-maven-plugin-1.1.zip","4":"vim-maven-plugin-1.1.zip","src_id":"23596","5":"23596","creation_date":"1442397525","6":"1442397525"}]},"4050":{"script_id":"4050","0":"4050","script_name":"jsruntime.vim","1":"jsruntime.vim","script_type":"utility","2":"utility","summary":"Run javascript in vim","3":"Run javascript in vim","description":"This is Javascript Runtime in Vim \r\nLatest Update -- Supports Win\/Linux\/Mac up to Vim 8.0\r\n\r\nAs you know, Vim is well integrated with python,perl etc, but no javascript, that is what this plugin does. \r\n\r\nThis plugin provide the ability to integrate your Vim with javascript, It use PyV8 as javascript interpreter. if PyV8 not supported, it use node, cscript, spiderMonkey as fallbacks. \r\n\r\nThe github-repo: https:\/\/github.com\/michalliu\/jsruntime.vim \r\n\r\n\r\nList of plugins powered by jsruntime.vim \r\n---------------------------------------------------------- \r\njsflakes.vim (Lint javascript code on the fly) http:\/\/www.vim.org\/scripts\/script.php?script_id=4057\r\nsourcebeautify.vim(beautify your source code javascript\/css\/html\/json etc. ) http:\/\/www.vim.org\/scripts\/script.php?script_id=4079\r\n\r\nMy other vim projects\r\n----------------------------\r\nIntegrated Vim Development Enviroment for mac - https:\/\/github.com\/michalliu\/gvimim-macvim\r\nIntegrated Vim Development Enviroment for windows & Linux - https:\/\/github.com\/michalliu\/gvimim","4":"This is Javascript Runtime in Vim \r\nLatest Update -- Supports Win\/Linux\/Mac up to Vim 8.0\r\n\r\nAs you know, Vim is well integrated with python,perl etc, but no javascript, that is what this plugin does. \r\n\r\nThis plugin provide the ability to integrate your Vim with javascript, It use PyV8 as javascript interpreter. if PyV8 not supported, it use node, cscript, spiderMonkey as fallbacks. \r\n\r\nThe github-repo: https:\/\/github.com\/michalliu\/jsruntime.vim \r\n\r\n\r\nList of plugins powered by jsruntime.vim \r\n---------------------------------------------------------- \r\njsflakes.vim (Lint javascript code on the fly) http:\/\/www.vim.org\/scripts\/script.php?script_id=4057\r\nsourcebeautify.vim(beautify your source code javascript\/css\/html\/json etc. ) http:\/\/www.vim.org\/scripts\/script.php?script_id=4079\r\n\r\nMy other vim projects\r\n----------------------------\r\nIntegrated Vim Development Enviroment for mac - https:\/\/github.com\/michalliu\/gvimim-macvim\r\nIntegrated Vim Development Enviroment for windows & Linux - https:\/\/github.com\/michalliu\/gvimim","install_details":"This plugin is a bit large because it packing with PyV8 for both windows,linux and mac to make this plugin much easier to use https:\/\/github.com\/michalliu\/jsruntime.vim\/issues\/5\r\n\r\nYou have to combine these parts after download. \r\n\r\nLinux\/Mac users      --------------->   cat jsruntime.zip.part* > jsruntime.zip \r\nWindows users --------------->  copy \/b jsruntime.zip.part* jsruntime.zip \r\n\r\nunzip it then put  plugin\/jsruntime to $VIM\\autoload","5":"This plugin is a bit large because it packing with PyV8 for both windows,linux and mac to make this plugin much easier to use https:\/\/github.com\/michalliu\/jsruntime.vim\/issues\/5\r\n\r\nYou have to combine these parts after download. \r\n\r\nLinux\/Mac users      --------------->   cat jsruntime.zip.part* > jsruntime.zip \r\nWindows users --------------->  copy \/b jsruntime.zip.part* jsruntime.zip \r\n\r\nunzip it then put  plugin\/jsruntime to $VIM\\autoload","first_name":"yf","6":"yf","last_name":"liu","7":"liu","releases":[{"0":"4050","vim_version":"7.0","1":"7.0","script_version":"7.0","2":"7.0","version_comment":"add mac os support. now jsruntime.vim is supports win\/linux\/mac up to vim 8.0","3":"add mac os support. now jsruntime.vim is supports win\/linux\/mac up to vim 8.0","package":"jsruntime.vim.zip.part02","4":"jsruntime.vim.zip.part02","src_id":"24745","5":"24745","creation_date":"1479424753","6":"1479424753"},{"0":"4050","vim_version":"7.0","1":"7.0","script_version":"7.0","2":"7.0","version_comment":"add mac os support. now jsruntime.vim is supports win\/linux\/mac up to vim 8.0","3":"add mac os support. now jsruntime.vim is supports win\/linux\/mac up to vim 8.0","package":"jsruntime.vim.zip.part01","4":"jsruntime.vim.zip.part01","src_id":"24744","5":"24744","creation_date":"1479424689","6":"1479424689"},{"0":"4050","vim_version":"7.0","1":"7.0","script_version":"7.0","2":"7.0","version_comment":"add mac os support. now jsruntime.vim is supports win\/linux\/mac up to vim 8.0","3":"add mac os support. now jsruntime.vim is supports win\/linux\/mac up to vim 8.0","package":"jsruntime.vim.zip.part00","4":"jsruntime.vim.zip.part00","src_id":"24743","5":"24743","creation_date":"1479424597","6":"1479424597"},{"0":"4050","vim_version":"7.0","1":"7.0","script_version":"6.0","2":"6.0","version_comment":"improve compatibility","3":"improve compatibility","package":"jsruntime.zip","4":"jsruntime.zip","src_id":"24411","5":"24411","creation_date":"1469776101","6":"1469776101"}]},"4049":{"script_id":"4049","0":"4049","script_name":"london.vim","1":"london.vim","script_type":"syntax","2":"syntax","summary":"London Framework template syntax","3":"London Framework template syntax","description":"Type \":setfiletype htmllondon\" from within Vim to select highlighting for London HTML templates.  If you desire Django template highlighting but not HTML highlighting, type \":setfiletype london\" instead.  Items highlighted include tem    plate tags, built-in filters, arguments and comments.\r\n\r\nhttps:\/\/github.com\/avelino\/london.vim","4":"Type \":setfiletype htmllondon\" from within Vim to select highlighting for London HTML templates.  If you desire Django template highlighting but not HTML highlighting, type \":setfiletype london\" instead.  Items highlighted include tem    plate tags, built-in filters, arguments and comments.\r\n\r\nhttps:\/\/github.com\/avelino\/london.vim","install_details":"Save the files london.vim to your ~\/.vim\/syntax directory.","5":"Save the files london.vim to your ~\/.vim\/syntax directory.","first_name":"Thiago","6":"Thiago","last_name":"Avelino","7":"Avelino","releases":[{"0":"4049","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"london.vim","4":"london.vim","src_id":"17882","5":"17882","creation_date":"1336320138","6":"1336320138"}]},"4048":{"script_id":"4048","0":"4048","script_name":"AmbiCompletion","1":"AmbiCompletion","script_type":"utility","2":"utility","summary":"Ambiguous completion","3":"Ambiguous completion","description":"This script provides an ambiguous completion functionality.\r\n\r\nA long function name, tired to type, a vague memory of spelling, ...\r\nAmbiguous completion supports you with similar words in your buffer.\r\n\r\nYour type does not need to match the beginning of answer word.\r\n\"egining\" -> \"beginning\"\r\n\r\nFor those who are forgetful.\r\n\r\nThis is a fork of the first version of Word Fuzzy Completion.\r\n(http:\/\/www.vim.org\/scripts\/script.php?script_id=3857)\r\nadding architectural changes(mainly no need +python), middle-word-match, global candidates, speed tuning.\r\n\r\nUsage:\r\n\r\n  1. Set completefunc to g:AmbiCompletion.\r\n\r\n      :set completefunc=g:AmbiCompletion\r\n      :set completefunc=g:AmbiCompletion9 \"if you download ambicompletion9.vim\r\n\r\n      \"optional\r\n      :inoremap <C-U>  <C-X><C-U>\r\n\r\nVariables:\r\n\r\n  (A right hand side value is a default value.)\r\n\r\n  g:AmbiCompletion_cacheCheckpoint = 50\r\n\r\n      cache-updating interval.\r\n      The cache is updated when changedtick progresses by this value.\r\n\r\nCommands:\r\n  \r\n  AmbiCompletionRefreshCache\r\n\r\n      clear the cache.\r\n","4":"This script provides an ambiguous completion functionality.\r\n\r\nA long function name, tired to type, a vague memory of spelling, ...\r\nAmbiguous completion supports you with similar words in your buffer.\r\n\r\nYour type does not need to match the beginning of answer word.\r\n\"egining\" -> \"beginning\"\r\n\r\nFor those who are forgetful.\r\n\r\nThis is a fork of the first version of Word Fuzzy Completion.\r\n(http:\/\/www.vim.org\/scripts\/script.php?script_id=3857)\r\nadding architectural changes(mainly no need +python), middle-word-match, global candidates, speed tuning.\r\n\r\nUsage:\r\n\r\n  1. Set completefunc to g:AmbiCompletion.\r\n\r\n      :set completefunc=g:AmbiCompletion\r\n      :set completefunc=g:AmbiCompletion9 \"if you download ambicompletion9.vim\r\n\r\n      \"optional\r\n      :inoremap <C-U>  <C-X><C-U>\r\n\r\nVariables:\r\n\r\n  (A right hand side value is a default value.)\r\n\r\n  g:AmbiCompletion_cacheCheckpoint = 50\r\n\r\n      cache-updating interval.\r\n      The cache is updated when changedtick progresses by this value.\r\n\r\nCommands:\r\n  \r\n  AmbiCompletionRefreshCache\r\n\r\n      clear the cache.\r\n","install_details":"Put this plugin in your plugin directory(e.g. $VIMRUNTIME\/plugin).\r\nThen source it or restart VIM.","5":"Put this plugin in your plugin directory(e.g. $VIMRUNTIME\/plugin).\r\nThen source it or restart VIM.","first_name":"Shuhei","6":"Shuhei","last_name":"Kubota","7":"Kubota","releases":[{"0":"4048","vim_version":"8.2","1":"8.2","script_version":"2.0a10","2":"2.0a10","version_comment":"fix lambda","3":"fix lambda","package":"ambicompletion9.vim","4":"ambicompletion9.vim","src_id":"27455","5":"27455","creation_date":"1611573421","6":"1611573421"},{"0":"4048","vim_version":"8.2","1":"8.2","script_version":"2.0a9","2":"2.0a9","version_comment":"fix variable declaration, add g:AmbiCompletion_useMatchFuzzy","3":"fix variable declaration, add g:AmbiCompletion_useMatchFuzzy","package":"ambicompletion9.vim","4":"ambicompletion9.vim","src_id":"27341","5":"27341","creation_date":"1603230346","6":"1603230346"},{"0":"4048","vim_version":"8.0","1":"8.0","script_version":"2.0a8","2":"2.0a8","version_comment":"fix function type error","3":"fix function type error","package":"ambicompletion9.vim","4":"ambicompletion9.vim","src_id":"27285","5":"27285","creation_date":"1597593622","6":"1597593622"},{"0":"4048","vim_version":"8.0","1":"8.0","script_version":"2.0a7","2":"2.0a7","version_comment":"fix function type error","3":"fix function type error","package":"ambicompletion9.vim","4":"ambicompletion9.vim","src_id":"27276","5":"27276","creation_date":"1597151276","6":"1597151276"},{"0":"4048","vim_version":"8.0","1":"8.0","script_version":"2.0a6","2":"2.0a6","version_comment":"fix scoring innacuracy","3":"fix scoring innacuracy","package":"ambicompletion9.vim","4":"ambicompletion9.vim","src_id":"27265","5":"27265","creation_date":"1596647106","6":"1596647106"},{"0":"4048","vim_version":"8.0","1":"8.0","script_version":"2.0a5","2":"2.0a5","version_comment":"faster","3":"faster","package":"ambicompletion9.vim","4":"ambicompletion9.vim","src_id":"27260","5":"27260","creation_date":"1596353217","6":"1596353217"},{"0":"4048","vim_version":"8.0","1":"8.0","script_version":"2.0a4","2":"2.0a4","version_comment":"fix sudden death\r\n","3":"fix sudden death\r\n","package":"ambicompletion9.vim","4":"ambicompletion9.vim","src_id":"27252","5":"27252","creation_date":"1595939608","6":"1595939608"},{"0":"4048","vim_version":"8.0","1":"8.0","script_version":"2.0a3","2":"2.0a3","version_comment":"REQUIRES 8.2.1261^. A little quicker.","3":"REQUIRES 8.2.1261^. A little quicker.","package":"ambicompletion9.vim","4":"ambicompletion9.vim","src_id":"27240","5":"27240","creation_date":"1595411888","6":"1595411888"},{"0":"4048","vim_version":"8.0","1":"8.0","script_version":"2.0a2","2":"2.0a2","version_comment":"fix sudden death ","3":"fix sudden death ","package":"ambicompletion9.vim","4":"ambicompletion9.vim","src_id":"27219","5":"27219","creation_date":"1593626674","6":"1593626674"},{"0":"4048","vim_version":"8.0","1":"8.0","script_version":"2.0a","2":"2.0a","version_comment":"It now performs faster. (REQUIRES vim9script)","3":"It now performs faster. (REQUIRES vim9script)","package":"ambicompletion9.vim","4":"ambicompletion9.vim","src_id":"27210","5":"27210","creation_date":"1592652332","6":"1592652332"},{"0":"4048","vim_version":"8.0","1":"8.0","script_version":"1.2","2":"1.2","version_comment":"auto re-complete if few candidates","3":"auto re-complete if few candidates","package":"ambicompletion.vim","4":"ambicompletion.vim","src_id":"26358","5":"26358","creation_date":"1548347236","6":"1548347236"},{"0":"4048","vim_version":"7.0","1":"7.0","script_version":"1.1","2":"1.1","version_comment":"better filtering & speed tuning\r\n","3":"better filtering & speed tuning\r\n","package":"ambicompletion.vim","4":"ambicompletion.vim","src_id":"26305","5":"26305","creation_date":"1545418628","6":"1545418628"},{"0":"4048","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"global candidates by default, speed tuning","3":"global candidates by default, speed tuning","package":"ambicompletion.vim","4":"ambicompletion.vim","src_id":"26303","5":"26303","creation_date":"1545303703","6":"1545303703"},{"0":"4048","vim_version":"7.0","1":"7.0","script_version":"0.7","2":"0.7","version_comment":"Added partial scan feature (g:AmbiCompletion_cacheScanRange) and cache retention feature (g:AmbiCompletion_cacheRetention).","3":"Added partial scan feature (g:AmbiCompletion_cacheScanRange) and cache retention feature (g:AmbiCompletion_cacheRetention).","package":"ambicompletion.vim","4":"ambicompletion.vim","src_id":"24417","5":"24417","creation_date":"1469962972","6":"1469962972"},{"0":"4048","vim_version":"7.0","1":"7.0","script_version":"0.6","2":"0.6","version_comment":"Each-buffer cache of candidates & Global word completion.","3":"Each-buffer cache of candidates & Global word completion.","package":"ambicompletion.vim","4":"ambicompletion.vim","src_id":"23754","5":"23754","creation_date":"1448347252","6":"1448347252"},{"0":"4048","vim_version":"7.0","1":"7.0","script_version":"0.5","2":"0.5","version_comment":"More timely cache refreshing.","3":"More timely cache refreshing.","package":"ambicompletion.vim","4":"ambicompletion.vim","src_id":"23747","5":"23747","creation_date":"1448119682","6":"1448119682"},{"0":"4048","vim_version":"7.0","1":"7.0","script_version":"0.4","2":"0.4","version_comment":"x10 faster!\r\nmore multibyte-completion accuracy","3":"x10 faster!\r\nmore multibyte-completion accuracy","package":"ambicompletion.vim","4":"ambicompletion.vim","src_id":"22911","5":"22911","creation_date":"1423819278","6":"1423819278"},{"0":"4048","vim_version":"7.0","1":"7.0","script_version":"0.3","2":"0.3","version_comment":"implemented a simple caching mechanism.","3":"implemented a simple caching mechanism.","package":"ambicompletion.vim","4":"ambicompletion.vim","src_id":"22877","5":"22877","creation_date":"1423139842","6":"1423139842"},{"0":"4048","vim_version":"7.0","1":"7.0","script_version":"0.2b","2":"0.2b","version_comment":"fixed encoding handling in +python","3":"fixed encoding handling in +python","package":"ambicompletion.vim","4":"ambicompletion.vim","src_id":"18534","5":"18534","creation_date":"1346662479","6":"1346662479"},{"0":"4048","vim_version":"7.0","1":"7.0","script_version":"0.2a","2":"0.2a","version_comment":"added encoding handling in +python.\r\nadded among-buffers collection by letting g:AmbiCompletion_allBuffers = 1.\r\n","3":"added encoding handling in +python.\r\nadded among-buffers collection by letting g:AmbiCompletion_allBuffers = 1.\r\n","package":"ambicompletion.vim","4":"ambicompletion.vim","src_id":"18371","5":"18371","creation_date":"1344149558","6":"1344149558"},{"0":"4048","vim_version":"7.3","1":"7.3","script_version":"0.1a","2":"0.1a","version_comment":"Initial upload","3":"Initial upload","package":"ambicompletion.vim","4":"ambicompletion.vim","src_id":"17872","5":"17872","creation_date":"1336194588","6":"1336194588"}]},"4047":{"script_id":"4047","0":"4047","script_name":"RbREPL.vim","1":"RbREPL.vim","script_type":"utility","2":"utility","summary":"Run a Ruby REPL in VIM.","3":"Run a Ruby REPL in VIM.","description":"# RbREPL.vim\r\n\r\nRbREPL.vim is a VIM plugin that allows you to run a Ruby interactive\r\ninterpreter inside a VIM buffer.\r\n\r\n# Preview\r\n\r\nScreenshot: http:\/\/farm7.static.flickr.com\/6029\/5926293207_eec79bce06_z.jpg\r\nVideo: http:\/\/www.youtube.com\/watch?v=kzZD7FeKfcQ\r\n\r\n# Warning\r\n\r\n*Multiline statements <del>don't yet<\/del> sort-of work.*\r\n\r\nThis plugin is in its early stages and I'm very new to Ruby programming.\r\nIt _probably_ won't do anything harmful to your computer, but it might,\r\nat times, not work as expected. \r\n\r\n# Usage\r\n\r\nStart the REPL using `<leader>R` or `:RbREPLToggle<CR>`. Type away. To\r\nstop the REPL run either of those commands again. This will not close\r\nthe buffer.\r\n\r\nIt's possible to evaluate a file you're working on inside the REPL by\r\nrunning the command `:RbREPLEvalFile<CR>` on a Ruby file.\r\n","4":"# RbREPL.vim\r\n\r\nRbREPL.vim is a VIM plugin that allows you to run a Ruby interactive\r\ninterpreter inside a VIM buffer.\r\n\r\n# Preview\r\n\r\nScreenshot: http:\/\/farm7.static.flickr.com\/6029\/5926293207_eec79bce06_z.jpg\r\nVideo: http:\/\/www.youtube.com\/watch?v=kzZD7FeKfcQ\r\n\r\n# Warning\r\n\r\n*Multiline statements <del>don't yet<\/del> sort-of work.*\r\n\r\nThis plugin is in its early stages and I'm very new to Ruby programming.\r\nIt _probably_ won't do anything harmful to your computer, but it might,\r\nat times, not work as expected. \r\n\r\n# Usage\r\n\r\nStart the REPL using `<leader>R` or `:RbREPLToggle<CR>`. Type away. To\r\nstop the REPL run either of those commands again. This will not close\r\nthe buffer.\r\n\r\nIt's possible to evaluate a file you're working on inside the REPL by\r\nrunning the command `:RbREPLEvalFile<CR>` on a Ruby file.\r\n","install_details":"Use `pathogen` and clone this repository into your `bundle` directory.","5":"Use `pathogen` and clone this repository into your `bundle` directory.","first_name":"Bogdan","6":"Bogdan","last_name":"Popa","7":"Popa","releases":[{"0":"4047","vim_version":"7.0","1":"7.0","script_version":"0.0.9","2":"0.0.9","version_comment":"Initial upload","3":"Initial upload","package":"rbrepl.vim","4":"rbrepl.vim","src_id":"17870","5":"17870","creation_date":"1336160751","6":"1336160751"}]},"4043":{"script_id":"4043","0":"4043","script_name":"neocomplcache-snippets_complete","1":"neocomplcache-snippets_complete","script_type":"utility","2":"utility","summary":"neocomplcache complete snippets source","3":"neocomplcache complete snippets source","description":"* Warning! *\r\n\r\nneocomplcache-snippets_complete is obsolute.\r\nneosnippet is available. \r\nhttps:\/\/github.com\/Shougo\/neosnippet\r\n\r\n==============================================================================\r\nINTRODUCTION\t\t\t\t\t*neocomplcache-snippets-complete-introduction*\r\n\r\nThis source analyzes snippet files for completion. The source offer a function\r\nsimilar with snipMate.vim and snippetsEmu.vim. Because you can search a snippet\r\nwith a function of neocomplcache, you may omit trouble to learn.\r\n\r\n==============================================================================\r\nEXAMPLES\t\t\t\t\t*neocomplcache-snippets-complete-examples*\r\n\r\n\" Plugin key-mappings.\r\nimap <C-k>     <Plug>(neocomplcache_snippets_expand)\r\nsmap <C-k>     <Plug>(neocomplcache_snippets_expand)\r\n\t\r\n\" SuperTab like snippets behavior.\r\n\"imap <expr><TAB> neocomplcache#sources#snippets_complete#expandable() ?\r\n\" \\ \"\\<Plug>(neocomplcache_snippets_expand)\" : pumvisible() ? \"\\<C-n>\" : \"\\<TAB>\"\r\n\t\r\n\" For snippet_complete marker.\r\nif has('conceal')\r\n  set conceallevel=2 concealcursor=i\r\nendif","4":"* Warning! *\r\n\r\nneocomplcache-snippets_complete is obsolute.\r\nneosnippet is available. \r\nhttps:\/\/github.com\/Shougo\/neosnippet\r\n\r\n==============================================================================\r\nINTRODUCTION\t\t\t\t\t*neocomplcache-snippets-complete-introduction*\r\n\r\nThis source analyzes snippet files for completion. The source offer a function\r\nsimilar with snipMate.vim and snippetsEmu.vim. Because you can search a snippet\r\nwith a function of neocomplcache, you may omit trouble to learn.\r\n\r\n==============================================================================\r\nEXAMPLES\t\t\t\t\t*neocomplcache-snippets-complete-examples*\r\n\r\n\" Plugin key-mappings.\r\nimap <C-k>     <Plug>(neocomplcache_snippets_expand)\r\nsmap <C-k>     <Plug>(neocomplcache_snippets_expand)\r\n\t\r\n\" SuperTab like snippets behavior.\r\n\"imap <expr><TAB> neocomplcache#sources#snippets_complete#expandable() ?\r\n\" \\ \"\\<Plug>(neocomplcache_snippets_expand)\" : pumvisible() ? \"\\<C-n>\" : \"\\<TAB>\"\r\n\t\r\n\" For snippet_complete marker.\r\nif has('conceal')\r\n  set conceallevel=2 concealcursor=i\r\nendif","install_details":"1: Install neocomplcache(https:\/\/github.com\/Shougo\/neocomplcache).\r\n2: Extract the file and put files in your Vim directory\r\n   (usually ~\/.vim\/ or Program Files\/Vim\/vimfiles on Windows).","5":"1: Install neocomplcache(https:\/\/github.com\/Shougo\/neocomplcache).\r\n2: Extract the file and put files in your Vim directory\r\n   (usually ~\/.vim\/ or Program Files\/Vim\/vimfiles on Windows).","first_name":"Shougo","6":"Shougo","last_name":"Matsushita","7":"Matsushita","releases":[{"0":"4043","vim_version":"7.2","1":"7.2","script_version":"2.0","2":"2.0","version_comment":"Initial upload","3":"Initial upload","package":"neocomplcache-snippets-complete-1.0.zip","4":"neocomplcache-snippets-complete-1.0.zip","src_id":"17861","5":"17861","creation_date":"1336010780","6":"1336010780"}]},"4042":{"script_id":"4042","0":"4042","script_name":"Ideone.vim","1":"Ideone.vim","script_type":"utility","2":"utility","summary":"vimscript for ideone","3":"vimscript for ideone","description":"This is vimscript for ideone (http:\/\/ideone.com)\n\nUsage:\n\n  :Ideone\n    post whole text to ideone.\n\n  :'<,'>Ideone\n    post selected text to ideone.\n\n  :Ideone -p\n    post whole text to ideone with private. require username\/password\n\nRequire:\n  webapi-vim (http:\/\/www.vim.org\/scripts\/script.php?script_id=4019)\n","4":"This is vimscript for ideone (http:\/\/ideone.com)\n\nUsage:\n\n  :Ideone\n    post whole text to ideone.\n\n  :'<,'>Ideone\n    post selected text to ideone.\n\n  :Ideone -p\n    post whole text to ideone with private. require username\/password\n\nRequire:\n  webapi-vim (http:\/\/www.vim.org\/scripts\/script.php?script_id=4019)\n","install_details":"copy it to your plugin directory.\n\n# cd ~\/.vim\n# unzip ideone-vim.zip\n\nor if you install pathogen.vim:\n\n# cd ~\/.vim\/bundle # or make directory\n# unzip \/path\/to\/ideone-vim.zip\n","5":"copy it to your plugin directory.\n\n# cd ~\/.vim\n# unzip ideone-vim.zip\n\nor if you install pathogen.vim:\n\n# cd ~\/.vim\/bundle # or make directory\n# unzip \/path\/to\/ideone-vim.zip\n","first_name":"Yasuhiro","6":"Yasuhiro","last_name":"Matsumoto","7":"Matsumoto","releases":[{"0":"4042","vim_version":"7.0","1":"7.0","script_version":"0.02","2":"0.02","version_comment":"[fix] Clear echo line.\n","3":"[fix] Clear echo line.\n","package":"ideone-vim.zip","4":"ideone-vim.zip","src_id":"17898","5":"17898","creation_date":"1336451700","6":"1336451700"},{"0":"4042","vim_version":"7.0","1":"7.0","script_version":"0.01","2":"0.01","version_comment":"Initial Release\n","3":"Initial Release\n","package":"ideone-vim.zip","4":"ideone-vim.zip","src_id":"17859","5":"17859","creation_date":"1335932144","6":"1335932144"}]},"4041":{"script_id":"4041","0":"4041","script_name":"VDBI.vim","1":"VDBI.vim","script_type":"utility","2":"utility","summary":"Database client for Vim","3":"Database client for Vim","description":"This is vim script to manipulate database.\r\n\r\nref: http:\/\/mattn.github.com\/vdbi-vim\/\r\n\r\nSource Repository.\r\nref: http:\/\/github.com\/mattn\/vdbi-vim\r\n\r\nThis plugin provides following interfaces.\r\n\r\n* Browsing tables\r\n* Browsing columns\r\n* Easy operations.\r\n* Data viewer.\r\n\r\nSupported database.\r\n\r\n* Oracle\r\n* SQLite\r\n* MySQL\r\n* PostgreSQL\r\n\r\nTo start VDBI, type ':VDBI'.\r\nTo open query editor, type <leader>s.\r\n","4":"This is vim script to manipulate database.\r\n\r\nref: http:\/\/mattn.github.com\/vdbi-vim\/\r\n\r\nSource Repository.\r\nref: http:\/\/github.com\/mattn\/vdbi-vim\r\n\r\nThis plugin provides following interfaces.\r\n\r\n* Browsing tables\r\n* Browsing columns\r\n* Easy operations.\r\n* Data viewer.\r\n\r\nSupported database.\r\n\r\n* Oracle\r\n* SQLite\r\n* MySQL\r\n* PostgreSQL\r\n\r\nTo start VDBI, type ':VDBI'.\r\nTo open query editor, type <leader>s.\r\n","install_details":"# cd ~\/.vim\r\n# unzip vdbi-vim.zip\r\n\r\nor if you install pathogen.vim:\r\n\r\n# cd ~\/.vim\/bundle # or make directory\r\n# unzip \/path\/to\/vdbi-vim.zip\r\n\r\nif you get sources from repository:\r\n\r\n# cd ~\/.vim\/bundle # or make directory\r\n# git clone http:\/\/github.com\/mattn\/vdbi-vim.git\r\n\r\nyou need to install database drivers you want to use.\r\n\r\n# cpanm DBI Plack JSON\r\n# cpanm ...extra-dbi-module...\r\n","5":"# cd ~\/.vim\r\n# unzip vdbi-vim.zip\r\n\r\nor if you install pathogen.vim:\r\n\r\n# cd ~\/.vim\/bundle # or make directory\r\n# unzip \/path\/to\/vdbi-vim.zip\r\n\r\nif you get sources from repository:\r\n\r\n# cd ~\/.vim\/bundle # or make directory\r\n# git clone http:\/\/github.com\/mattn\/vdbi-vim.git\r\n\r\nyou need to install database drivers you want to use.\r\n\r\n# cpanm DBI Plack JSON\r\n# cpanm ...extra-dbi-module...\r\n","first_name":"Yasuhiro","6":"Yasuhiro","last_name":"Matsumoto","7":"Matsumoto","releases":[{"0":"4041","vim_version":"7.0","1":"7.0","script_version":"0.01","2":"0.01","version_comment":"Initial upload","3":"Initial upload","package":"vdbi-vim.zip","4":"vdbi-vim.zip","src_id":"17856","5":"17856","creation_date":"1335930724","6":"1335930724"}]},"4040":{"script_id":"4040","0":"4040","script_name":"Fortune vimtips","1":"Fortune vimtips","script_type":"utility","2":"utility","summary":"vimtips is a project to use fortune software to view vimtips.","3":"vimtips is a project to use fortune software to view vimtips.","description":"vimtips is a project to use fortune software to view vimtips. Open tips in a new buffer when you launch vim.","4":"vimtips is a project to use fortune software to view vimtips. Open tips in a new buffer when you launch vim.","install_details":"Clone git repository to have vimtips file and launch the install script\r\nhttps:\/\/github.com\/hobbestigrou\/vimtips-fortune","5":"Clone git repository to have vimtips file and launch the install script\r\nhttps:\/\/github.com\/hobbestigrou\/vimtips-fortune","first_name":"Natal","6":"Natal","last_name":"Ng\u00c3\u00a9tal","7":"Ng\u00c3\u00a9tal","releases":[{"0":"4040","vim_version":"7.0","1":"7.0","script_version":"0.7","2":"0.7","version_comment":"New release 0.7.\r\n\r\n    * Remove some duplicate.","3":"New release 0.7.\r\n\r\n    * Remove some duplicate.","package":"fortunes-vimtips.tar.gz","4":"fortunes-vimtips.tar.gz","src_id":"24469","5":"24469","creation_date":"1472069246","6":"1472069246"},{"0":"4040","vim_version":"7.0","1":"7.0","script_version":"0.6","2":"0.6","version_comment":"New release 0.6.\r\n\r\n  *  Fixed the duplicate tip on Vim\r\n","3":"New release 0.6.\r\n\r\n  *  Fixed the duplicate tip on Vim\r\n","package":"fortunes-vimtips.tar.gz","4":"fortunes-vimtips.tar.gz","src_id":"19688","5":"19688","creation_date":"1364053335","6":"1364053335"},{"0":"4040","vim_version":"7.0","1":"7.0","script_version":"0.5","2":"0.5","version_comment":"New release 0.5. \r\n\r\n  * Add a new option to display the tip on a gvim tooltip","3":"New release 0.5. \r\n\r\n  * Add a new option to display the tip on a gvim tooltip","package":"fortunes-vimtips.tar.gz","4":"fortunes-vimtips.tar.gz","src_id":"19437","5":"19437","creation_date":"1359309078","6":"1359309078"},{"0":"4040","vim_version":"7.0","1":"7.0","script_version":"0.4","2":"0.4","version_comment":"New release 0.4.\r\n\r\n  * Remove install script\r\n  * Handle window focus restore even if original winnr changed\r\n  * Add configuration variable\r\n  * First version not relying on an external fortune program","3":"New release 0.4.\r\n\r\n  * Remove install script\r\n  * Handle window focus restore even if original winnr changed\r\n  * Add configuration variable\r\n  * First version not relying on an external fortune program","package":"fortune-vimtips.tar.gz","4":"fortune-vimtips.tar.gz","src_id":"18066","5":"18066","creation_date":"1338408750","6":"1338408750"},{"0":"4040","vim_version":"7.0","1":"7.0","script_version":"0.3","2":"0.3","version_comment":"New release 0.3.\r\n\r\n  * Add new option auto_display.\r\n  * Add documentation file.\r\n  * Correct a mistake in a :s command.\r\n  * Minor change to resolve a bug, when starting vim in gui mode.\r\n  * New tips. ","3":"New release 0.3.\r\n\r\n  * Add new option auto_display.\r\n  * Add documentation file.\r\n  * Correct a mistake in a :s command.\r\n  * Minor change to resolve a bug, when starting vim in gui mode.\r\n  * New tips. ","package":"fortune-vimtips.tar.gz","4":"fortune-vimtips.tar.gz","src_id":"18021","5":"18021","creation_date":"1337796797","6":"1337796797"},{"0":"4040","vim_version":"7.0","1":"7.0","script_version":"0.2","2":"0.2","version_comment":"New version 0.2. \r\n\r\n  *  Restore the original window in all case. \r\n  * Save and restore the window when using the :Fortune \r\n  * Fix avoid multiple sources. \r\n  * Suppress the nul character add by vim at the end of the tip. \r\n  * Add a validation to detect windows environnement","3":"New version 0.2. \r\n\r\n  *  Restore the original window in all case. \r\n  * Save and restore the window when using the :Fortune \r\n  * Fix avoid multiple sources. \r\n  * Suppress the nul character add by vim at the end of the tip. \r\n  * Add a validation to detect windows environnement","package":"fortune-vimtips.tar.gz","4":"fortune-vimtips.tar.gz","src_id":"17881","5":"17881","creation_date":"1336313199","6":"1336313199"},{"0":"4040","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"vimtips-fortune.tar.gz","4":"vimtips-fortune.tar.gz","src_id":"17850","5":"17850","creation_date":"1335909448","6":"1335909448"}]},"4039":{"script_id":"4039","0":"4039","script_name":"evervim","1":"evervim","script_type":"utility","2":"utility","summary":"Edit evernote on vim.","3":"Edit evernote on vim.","description":"evervim is plugin for edit evernote(http:\/\/www.evernote.com) on vim. \r\nThis plugin can edit evernote by markdown or law XML. \r\n\r\n==============================================================================\r\nREQUIRES\r\n\r\nrequires:\r\n * python\r\n * the \"markdown\" package for python\r\n * vim with +python\r\nIf your vim was compiled with +python, :echo has('python') will return 1.\r\n\r\n==============================================================================\r\nINSTALL\r\n\r\nInstall files into Vim script directory.\r\nAfter install,\r\n\r\n\t:EvervimSetup\r\n\r\ncommand is added. Do it for setting, and input evernote userID and password.\r\n\r\n==============================================================================\r\nUSAGE\r\n\r\nDisplay NotebookList\r\n\r\n\t:EvervimNotebookList\r\n\r\nNotebookList is displayed, choice one and <CR>,\r\nnotes in notebook will be listed.\r\nchoice one and <CR> too, the note will be displayd.\r\n\r\nNote is formatted\r\n 1 line is Title\r\n 2 line is Tags (comma deliminated)\r\n 3 line after body\r\n\r\n\r\n==============================================================================\r\nDEVELOPMENT\r\n\r\nevervim developed on github. \r\n\r\nLatest Version: \r\nhttps:\/\/github.com\/kakkyz81\/evervim\r\n","4":"evervim is plugin for edit evernote(http:\/\/www.evernote.com) on vim. \r\nThis plugin can edit evernote by markdown or law XML. \r\n\r\n==============================================================================\r\nREQUIRES\r\n\r\nrequires:\r\n * python\r\n * the \"markdown\" package for python\r\n * vim with +python\r\nIf your vim was compiled with +python, :echo has('python') will return 1.\r\n\r\n==============================================================================\r\nINSTALL\r\n\r\nInstall files into Vim script directory.\r\nAfter install,\r\n\r\n\t:EvervimSetup\r\n\r\ncommand is added. Do it for setting, and input evernote userID and password.\r\n\r\n==============================================================================\r\nUSAGE\r\n\r\nDisplay NotebookList\r\n\r\n\t:EvervimNotebookList\r\n\r\nNotebookList is displayed, choice one and <CR>,\r\nnotes in notebook will be listed.\r\nchoice one and <CR> too, the note will be displayd.\r\n\r\nNote is formatted\r\n 1 line is Title\r\n 2 line is Tags (comma deliminated)\r\n 3 line after body\r\n\r\n\r\n==============================================================================\r\nDEVELOPMENT\r\n\r\nevervim developed on github. \r\n\r\nLatest Version: \r\nhttps:\/\/github.com\/kakkyz81\/evervim\r\n","install_details":"","5":"","first_name":"kakkyz","6":"kakkyz","last_name":"","7":"","releases":[{"0":"4039","vim_version":"7.0","1":"7.0","script_version":"0.3.6","2":"0.3.6","version_comment":"Ver.0.3.6:2012-06-03\r\n- Add g:evervim_splitoption.","3":"Ver.0.3.6:2012-06-03\r\n- Add g:evervim_splitoption.","package":"evervim.zip","4":"evervim.zip","src_id":"18082","5":"18082","creation_date":"1338693972","6":"1338693972"},{"0":"4039","vim_version":"7.0","1":"7.0","script_version":"0.3.5","2":"0.3.5","version_comment":"- Add :EvervimOpenBrowser. If you want use that command, install openbrowser.vim.\r\n- Add :EvervimOpenClient. Only windows,open note on \r\n  Evernote Client by ENScript.exe.\r\n- Bug fix. Stopped auto upload when reuse __EVERVIM_NOTE__ buf. ","3":"- Add :EvervimOpenBrowser. If you want use that command, install openbrowser.vim.\r\n- Add :EvervimOpenClient. Only windows,open note on \r\n  Evernote Client by ENScript.exe.\r\n- Bug fix. Stopped auto upload when reuse __EVERVIM_NOTE__ buf. ","package":"evervim.zip","4":"evervim.zip","src_id":"17862","5":"17862","creation_date":"1336025314","6":"1336025314"},{"0":"4039","vim_version":"7.0","1":"7.0","script_version":"0.3.0","2":"0.3.0","version_comment":"Initial upload","3":"Initial upload","package":"evervim.zip","4":"evervim.zip","src_id":"17837","5":"17837","creation_date":"1335751338","6":"1335751338"}]},"4038":{"script_id":"4038","0":"4038","script_name":"vim-dasm","1":"vim-dasm","script_type":"syntax","2":"syntax","summary":"Syntax highlighting for dasm & dasm16","3":"Syntax highlighting for dasm & dasm16","description":"This plugin adds syntax highlighting support for DASM.\r\n\r\nPlease see the project page for much more information: \r\nhttp:\/\/github.com\/pksunkara\/vim-dasm\r\n ","4":"This plugin adds syntax highlighting support for DASM.\r\n\r\nPlease see the project page for much more information: \r\nhttp:\/\/github.com\/pksunkara\/vim-dasm\r\n ","install_details":"Untar the archive into .vim. \r\n\r\nSince this plugin has rolling versions based on git commits, it may be more convenient to install and upgrade it using pathogen and git. The readme has instructions for doing this: \r\nhttp:\/\/github.com\/pksunkara\/vim-dasm#readme","5":"Untar the archive into .vim. \r\n\r\nSince this plugin has rolling versions based on git commits, it may be more convenient to install and upgrade it using pathogen and git. The readme has instructions for doing this: \r\nhttp:\/\/github.com\/pksunkara\/vim-dasm#readme","first_name":"Pavan Kumar","6":"Pavan Kumar","last_name":"Sunkara","7":"Sunkara","releases":[{"0":"4038","vim_version":"7.0","1":"7.0","script_version":"1","2":"1","version_comment":"Initial upload","3":"Initial upload","package":"vim-dasm.tar","4":"vim-dasm.tar","src_id":"17835","5":"17835","creation_date":"1335687805","6":"1335687805"}]},"4037":{"script_id":"4037","0":"4037","script_name":"bestfriend.vim","1":"bestfriend.vim","script_type":"utility","2":"utility","summary":"Know your best friend","3":"Know your best friend","description":"bestfriend.vim\r\n==========\r\n\r\nWho is the best friend?\r\nIf you want to know, this is an answer.\r\n\r\nThis plugin is not so practical, but might provide bit interest :)\r\n\r\nUsage\r\n----------\r\nbestfriend.vim provides 2 commands to show your best friend.\r\n\r\n* `:BestFriend` shows edit time of the current file.\r\n\r\n    1: ~\/.vimrc                                               00:56 (01:04)\r\n\r\n* `:BestFriends` shows ranking of edit time.\r\n\r\n    1: ~\/.vimrc                                                                              00:56 (01:04)\r\n    2: ~\/foo\/bar\/baz.pl                                                                  00:33 (00:33)\r\n    3: ~\/hoge\/hige\/huga.rb                                                           00:01 (00:01)\r\n    4: ~\/.zshrc                                                                              00:00 (00:00)\r\n    6: ~\/something\/vim\/vim-bestfriend\/autoload\/bestfriend.vim   00:00 (00:03)\r\n    7: ~\/something\/vim\/vim-bestfriend\/plugin\/bestfriend.vim       00:00 (00:01)\r\n    8: ~\/something\/vim\/vim-bestfriend\/README.md                  00:00 (00:13)\r\n    9: ~\/.zshenv                                                                           00:00 (00:00)  \r\n   10: ~\/.tmux.conf                                                                      00:00 (00:00)\r\n\r\nActually bestfriend.vim provides several options.\r\n\r\nRelated links\r\n----------\r\n\r\nGitHub repository: https:\/\/github.com\/tacahiroy\/vim-bestfriend\r\n\r\nLicense\r\n----------\r\n\r\nCopyright (c) 2012 Takahiro YOSHIHARA. Distributed under the MIT License.\r\n","4":"bestfriend.vim\r\n==========\r\n\r\nWho is the best friend?\r\nIf you want to know, this is an answer.\r\n\r\nThis plugin is not so practical, but might provide bit interest :)\r\n\r\nUsage\r\n----------\r\nbestfriend.vim provides 2 commands to show your best friend.\r\n\r\n* `:BestFriend` shows edit time of the current file.\r\n\r\n    1: ~\/.vimrc                                               00:56 (01:04)\r\n\r\n* `:BestFriends` shows ranking of edit time.\r\n\r\n    1: ~\/.vimrc                                                                              00:56 (01:04)\r\n    2: ~\/foo\/bar\/baz.pl                                                                  00:33 (00:33)\r\n    3: ~\/hoge\/hige\/huga.rb                                                           00:01 (00:01)\r\n    4: ~\/.zshrc                                                                              00:00 (00:00)\r\n    6: ~\/something\/vim\/vim-bestfriend\/autoload\/bestfriend.vim   00:00 (00:03)\r\n    7: ~\/something\/vim\/vim-bestfriend\/plugin\/bestfriend.vim       00:00 (00:01)\r\n    8: ~\/something\/vim\/vim-bestfriend\/README.md                  00:00 (00:13)\r\n    9: ~\/.zshenv                                                                           00:00 (00:00)  \r\n   10: ~\/.tmux.conf                                                                      00:00 (00:00)\r\n\r\nActually bestfriend.vim provides several options.\r\n\r\nRelated links\r\n----------\r\n\r\nGitHub repository: https:\/\/github.com\/tacahiroy\/vim-bestfriend\r\n\r\nLicense\r\n----------\r\n\r\nCopyright (c) 2012 Takahiro YOSHIHARA. Distributed under the MIT License.\r\n","install_details":"If you use Vundle (https:\/\/github.com\/gmarik\/vundle.git) it's very easy to install, you just\r\nrun command\r\n:BundleInstall tacahiroy\/vim-bestfriend\r\ninside vim.\r\nDon't for get put `Bundle 'tacahiroy\/vim-bestfriend'` into `.vimrc`.\r\n\r\nIf you use pathogen.vim (https:\/\/github.com\/tpope\/vim-pathogen), you just execute following to install this plugin:\r\n\r\n    cd ~\/.vim\/bundle\r\n    git clone git:\/\/github.com\/tacahiroy\/vim-bestfriend.git\r\n\r\nIf you use neither Vundle nor pathogen, copy autoload and plugin directory\r\ninto your `$HOME\/.vim` directory.\r\n* on Windows, you probably copy those files into `$HOME\/vimfiles` directory.","5":"If you use Vundle (https:\/\/github.com\/gmarik\/vundle.git) it's very easy to install, you just\r\nrun command\r\n:BundleInstall tacahiroy\/vim-bestfriend\r\ninside vim.\r\nDon't for get put `Bundle 'tacahiroy\/vim-bestfriend'` into `.vimrc`.\r\n\r\nIf you use pathogen.vim (https:\/\/github.com\/tpope\/vim-pathogen), you just execute following to install this plugin:\r\n\r\n    cd ~\/.vim\/bundle\r\n    git clone git:\/\/github.com\/tacahiroy\/vim-bestfriend.git\r\n\r\nIf you use neither Vundle nor pathogen, copy autoload and plugin directory\r\ninto your `$HOME\/.vim` directory.\r\n* on Windows, you probably copy those files into `$HOME\/vimfiles` directory.","first_name":"Takahiro","6":"Takahiro","last_name":"Yoshihara","7":"Yoshihara","releases":[{"0":"4037","vim_version":"7.0","1":"7.0","script_version":"0.0.3","2":"0.0.3","version_comment":"Added option 'g:bestfriend_observe_cursor_position' for accurate time calculation. It is useful especially on Vim (CUI).","3":"Added option 'g:bestfriend_observe_cursor_position' for accurate time calculation. It is useful especially on Vim (CUI).","package":"bestfriend-0.0.3.zip","4":"bestfriend-0.0.3.zip","src_id":"17875","5":"17875","creation_date":"1336263163","6":"1336263163"},{"0":"4037","vim_version":"7.0","1":"7.0","script_version":"0.0.2","2":"0.0.2","version_comment":"* Fixed helptag duplication error","3":"* Fixed helptag duplication error","package":"bestfriend-0.0.2.zip","4":"bestfriend-0.0.2.zip","src_id":"17839","5":"17839","creation_date":"1335777321","6":"1335777321"},{"0":"4037","vim_version":"7.0","1":"7.0","script_version":"0.0.1","2":"0.0.1","version_comment":"Initial upload","3":"Initial upload","package":"bestfriend.zip","4":"bestfriend.zip","src_id":"17834","5":"17834","creation_date":"1335657108","6":"1335657108"}]},"4036":{"script_id":"4036","0":"4036","script_name":"ucpp-vim-syntax","1":"ucpp-vim-syntax","script_type":"syntax","2":"syntax","summary":"uC++ Syntax Highlighting","3":"uC++ Syntax Highlighting","description":"Highlight \u00c2\u00b5C++ source code contained in '.ucpp' or '.uh' files.","4":"Highlight \u00c2\u00b5C++ source code contained in '.ucpp' or '.uh' files.","install_details":"Copy subdirectories into ~\/.vim\/","5":"Copy subdirectories into ~\/.vim\/","first_name":"Felix","6":"Felix","last_name":"Fung","7":"Fung","releases":[{"0":"4036","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"ucpp-vim-syntax.tar.gz","4":"ucpp-vim-syntax.tar.gz","src_id":"17828","5":"17828","creation_date":"1335569330","6":"1335569330"}]},"4035":{"script_id":"4035","0":"4035","script_name":"modx","1":"modx","script_type":"syntax","2":"syntax","summary":"Highlights MODX template tags within HTML.","3":"Highlights MODX template tags within HTML.","description":"Extends Vim HTML syntax highlighting to support http:\/\/modx.com content management system tags.\r\n\r\nSupports MODX Revolution only.\r\n\r\nPlease see project page for more info or to report issues:\r\nhttps:\/\/github.com\/rosstimson\/modx.vim","4":"Extends Vim HTML syntax highlighting to support http:\/\/modx.com content management system tags.\r\n\r\nSupports MODX Revolution only.\r\n\r\nPlease see project page for more info or to report issues:\r\nhttps:\/\/github.com\/rosstimson\/modx.vim","install_details":"Extract into ~\/.vim or use Pathogen (recommended).","5":"Extract into ~\/.vim or use Pathogen (recommended).","first_name":"Ross","6":"Ross","last_name":"Timson","7":"Timson","releases":[{"0":"4035","vim_version":"7.3","1":"7.3","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"modx.tar.gz","4":"modx.tar.gz","src_id":"17827","5":"17827","creation_date":"1335559436","6":"1335559436"}]},"4034":{"script_id":"4034","0":"4034","script_name":"SAS Indent","1":"SAS Indent","script_type":"indent","2":"indent","summary":"Indent Script for SAS 9.1\/9.2\/9.3\/9.4","3":"Indent Script for SAS 9.1\/9.2\/9.3\/9.4","description":"Indent script for SAS. The algorithm is supposed to be rather tolerable.\r\n\r\nExamples of the indenting results are shown as following:\r\n\r\n1. For data step\/proc sections, the script can properly indent with or without the closing run\/quit statements.\r\n   (SAS does not require explicit closing statements for data step\/proc sections.)\r\n\r\n   data female;\r\n      set total; where gender = 0;\r\n   data male;\r\n      set total; where gender = 1;\r\n   run;\r\n   proc sort data = new; by gender;\r\n   proc freq data = new;\r\n      table gender \/ missing;\r\n   endsas;\r\n\r\n2. The script can also recognize which procedure supports run-processing and indent accordingly.\r\n\r\n   proc reg;\r\n      model y = x1-x5;\r\n   run;\r\n      model y = x1-x10;\r\n   run;\r\n   quit;      \r\n\r\n3. The indentation is properly managed when mixed with macros.\r\n   (Nesting macro is evil. Don't do it)\r\n\r\n   %macro test();\r\n      data new;\r\n         set old; where age >= 18;\r\n         format gender gender.;\r\n      proc freq;\r\n         table gender;\r\n   %mend;\r\n\r\n4. Logic expressions.\r\n\r\n   data a;\r\n      set b; where age >= 18;\r\n      if numtx = 1 and not (pid > 0 and dcitag in (1, 2)) then strata = 3;\r\n      else if pid > 0 then do;\r\n         if dcitag in (1, 2) then do; \r\n            strata = 1; dcitype = 1;\r\n         end;\r\n         else if dcipsh1 = 1 then do;\r\n            strata = 1; dcitype = 3;\r\n         end;\r\n         else if numtx > 1 then strata = 2;\r\n      end;\r\n      else do;\r\n         if dcitag2 in (1, 2) then do; strata = 1; dcitype = 2; end;\r\n         else if dcipsh1 = 1 then do; strata = 1; dcitype = 3; end;\r\n         else if pid < 0 and dcipsh1 ~= 1 and numtx > 1 then strata = 2;\r\n      end;\r\n   run;\r\n\r\nPlease also check out my SAS syntax script: http:\/\/vim.sourceforge.net\/scripts\/script.php?script_id=3522","4":"Indent script for SAS. The algorithm is supposed to be rather tolerable.\r\n\r\nExamples of the indenting results are shown as following:\r\n\r\n1. For data step\/proc sections, the script can properly indent with or without the closing run\/quit statements.\r\n   (SAS does not require explicit closing statements for data step\/proc sections.)\r\n\r\n   data female;\r\n      set total; where gender = 0;\r\n   data male;\r\n      set total; where gender = 1;\r\n   run;\r\n   proc sort data = new; by gender;\r\n   proc freq data = new;\r\n      table gender \/ missing;\r\n   endsas;\r\n\r\n2. The script can also recognize which procedure supports run-processing and indent accordingly.\r\n\r\n   proc reg;\r\n      model y = x1-x5;\r\n   run;\r\n      model y = x1-x10;\r\n   run;\r\n   quit;      \r\n\r\n3. The indentation is properly managed when mixed with macros.\r\n   (Nesting macro is evil. Don't do it)\r\n\r\n   %macro test();\r\n      data new;\r\n         set old; where age >= 18;\r\n         format gender gender.;\r\n      proc freq;\r\n         table gender;\r\n   %mend;\r\n\r\n4. Logic expressions.\r\n\r\n   data a;\r\n      set b; where age >= 18;\r\n      if numtx = 1 and not (pid > 0 and dcitag in (1, 2)) then strata = 3;\r\n      else if pid > 0 then do;\r\n         if dcitag in (1, 2) then do; \r\n            strata = 1; dcitype = 1;\r\n         end;\r\n         else if dcipsh1 = 1 then do;\r\n            strata = 1; dcitype = 3;\r\n         end;\r\n         else if numtx > 1 then strata = 2;\r\n      end;\r\n      else do;\r\n         if dcitag2 in (1, 2) then do; strata = 1; dcitype = 2; end;\r\n         else if dcipsh1 = 1 then do; strata = 1; dcitype = 3; end;\r\n         else if pid < 0 and dcipsh1 ~= 1 and numtx > 1 then strata = 2;\r\n      end;\r\n   run;\r\n\r\nPlease also check out my SAS syntax script: http:\/\/vim.sourceforge.net\/scripts\/script.php?script_id=3522","install_details":"","5":"","first_name":"Zhenhuan","6":"Zhenhuan","last_name":"Hu","7":"Hu","releases":[{"0":"4034","vim_version":"7.0","1":"7.0","script_version":"3.0.1","2":"3.0.1","version_comment":"Fix an issue in indenting macro %end.","3":"Fix an issue in indenting macro %end.","package":"sas.vim","4":"sas.vim","src_id":"25030","5":"25030","creation_date":"1489419850","6":"1489419850"},{"0":"4034","vim_version":"7.0","1":"7.0","script_version":"3.0.0","2":"3.0.0","version_comment":"Support proper indentation for run-processing procedures.","3":"Support proper indentation for run-processing procedures.","package":"sas.vim","4":"sas.vim","src_id":"25024","5":"25024","creation_date":"1489180284","6":"1489180284"},{"0":"4034","vim_version":"7.0","1":"7.0","script_version":"2.2","2":"2.2","version_comment":"Change the behavior how ENDSAS is indented. Now it indents at the same level as the first non-blank line of the program instead of no indent.","3":"Change the behavior how ENDSAS is indented. Now it indents at the same level as the first non-blank line of the program instead of no indent.","package":"sas.vim","4":"sas.vim","src_id":"24437","5":"24437","creation_date":"1470772888","6":"1470772888"},{"0":"4034","vim_version":"7.0","1":"7.0","script_version":"2.1","2":"2.1","version_comment":"Fix an issue when no indent is made at the end of a macro","3":"Fix an issue when no indent is made at the end of a macro","package":"sas.vim","4":"sas.vim","src_id":"24433","5":"24433","creation_date":"1470691165","6":"1470691165"},{"0":"4034","vim_version":"7.0","1":"7.0","script_version":"2.0","2":"2.0","version_comment":"Implemented a brand new algorithm for indenting. Now indenting will be correct with or without close data\/proc section by run statement. Added enddata keyword.","3":"Implemented a brand new algorithm for indenting. Now indenting will be correct with or without close data\/proc section by run statement. Added enddata keyword.","package":"sas.vim","4":"sas.vim","src_id":"17911","5":"17911","creation_date":"1336593869","6":"1336593869"},{"0":"4034","vim_version":"7.0","1":"7.0","script_version":"1.1","2":"1.1","version_comment":"Optimized the indenting approach. Added keyword QUIT.","3":"Optimized the indenting approach. Added keyword QUIT.","package":"sas.vim","4":"sas.vim","src_id":"17843","5":"17843","creation_date":"1335801261","6":"1335801261"},{"0":"4034","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"sas.vim","4":"sas.vim","src_id":"17826","5":"17826","creation_date":"1335477936","6":"1335477936"}]},"4033":{"script_id":"4033","0":"4033","script_name":"vim4rally","1":"vim4rally","script_type":"utility","2":"utility","summary":"Rally ALM Integration for Vim","3":"Rally ALM Integration for Vim","description":"Rally ALM Integration for Vim\r\n\r\nRally is an award winning Agile Lifecycle Management (ALM) tool that helps organizations predictably deliver valuable, quality software.  Deliver the features users love.  Faster.\r\n\r\nAs a vim user, you know what productivity _really_ means.  This plugin lets you collaborate with your agile team using Rally and keep your fingers on the keyboard. \r\n        \r\nThis plugin provides the ability to search and display stories, tasks, and defects.  It also supports updating task estimate and todo.  Lastly, you can also show iteration burndown and cumulative flow charts for the current active iteration.\r\n\r\nWritten mostly in ruby, the latest version uses vim7.4, ruby2.0, and is compatible with vundle plugin manager.   Note:  Earlier versions of this plugin have supported and required vim7.2 patch 374 or greater (that patch has a req'd ruby interface fix) and ruby 1.8.6 or greater.   With all the dependency goodness lately, YMMV.  \r\n\r\nBefore installing, read the Requirements and Installation notes https:\/\/github.com\/davidpthomas\/vim4rally\/blob\/master\/doc\/rally.txt\r\n\r\nGet the latest plugin and see screenshots in github https:\/\/github.com\/davidpthomas\/vim4rally\r\n\r\nOverview video (5min): http:\/\/screencast.com\/t\/9a27gnOOA\r\n\r\nHappy vimming!","4":"Rally ALM Integration for Vim\r\n\r\nRally is an award winning Agile Lifecycle Management (ALM) tool that helps organizations predictably deliver valuable, quality software.  Deliver the features users love.  Faster.\r\n\r\nAs a vim user, you know what productivity _really_ means.  This plugin lets you collaborate with your agile team using Rally and keep your fingers on the keyboard. \r\n        \r\nThis plugin provides the ability to search and display stories, tasks, and defects.  It also supports updating task estimate and todo.  Lastly, you can also show iteration burndown and cumulative flow charts for the current active iteration.\r\n\r\nWritten mostly in ruby, the latest version uses vim7.4, ruby2.0, and is compatible with vundle plugin manager.   Note:  Earlier versions of this plugin have supported and required vim7.2 patch 374 or greater (that patch has a req'd ruby interface fix) and ruby 1.8.6 or greater.   With all the dependency goodness lately, YMMV.  \r\n\r\nBefore installing, read the Requirements and Installation notes https:\/\/github.com\/davidpthomas\/vim4rally\/blob\/master\/doc\/rally.txt\r\n\r\nGet the latest plugin and see screenshots in github https:\/\/github.com\/davidpthomas\/vim4rally\r\n\r\nOverview video (5min): http:\/\/screencast.com\/t\/9a27gnOOA\r\n\r\nHappy vimming!","install_details":"See doc\/rally.txt for requirements and installation details.","5":"See doc\/rally.txt for requirements and installation details.","first_name":"David","6":"David","last_name":"Thomas","7":"Thomas","releases":[{"0":"4033","vim_version":"7.0","1":"7.0","script_version":"1.1","2":"1.1","version_comment":"Get latest release from https:\/\/github.com\/davidpthomas\/vim4rally","3":"Get latest release from https:\/\/github.com\/davidpthomas\/vim4rally","package":"GET_LATEST_FROM_GITHUB.txt","4":"GET_LATEST_FROM_GITHUB.txt","src_id":"21121","5":"21121","creation_date":"1385593206","6":"1385593206"}]},"4032":{"script_id":"4032","0":"4032","script_name":"muxmate","1":"muxmate","script_type":"utility","2":"utility","summary":"An easy way to send shell commands to tmux from vim.","3":"An easy way to send shell commands to tmux from vim.","description":"## Getting Started\r\n\r\n`Leader + s` opens up the session select setting.\r\n\r\n```sh\r\nSelect a tmux session\r\n=====================\r\n(0) session_one\r\n(1) another_session\r\n(2) another_session\r\n```\r\n\r\nThen you can choose the current session based on the number.\r\n\r\n`Leader + sx` opens up the shell command input. For example.\r\n\r\n```sh\r\nShell command: ls -al\r\n```\r\n\r\n## Integration With Rails\r\n\r\nCurrently I have coupled some rails commands to start.\r\n\r\n`Leader + sf` to run the spec file.\r\n`Leader + sl` to run the spec file's current line number.\r\n`Leader + sS` to run all the specs.\r\n\r\n## TODO\r\n\r\nI was thinking about putting up snippets for different commands for\r\ndifferent languages, kind of like snipmate snippets.\r\n\r\nAdd docs.","4":"## Getting Started\r\n\r\n`Leader + s` opens up the session select setting.\r\n\r\n```sh\r\nSelect a tmux session\r\n=====================\r\n(0) session_one\r\n(1) another_session\r\n(2) another_session\r\n```\r\n\r\nThen you can choose the current session based on the number.\r\n\r\n`Leader + sx` opens up the shell command input. For example.\r\n\r\n```sh\r\nShell command: ls -al\r\n```\r\n\r\n## Integration With Rails\r\n\r\nCurrently I have coupled some rails commands to start.\r\n\r\n`Leader + sf` to run the spec file.\r\n`Leader + sl` to run the spec file's current line number.\r\n`Leader + sS` to run all the specs.\r\n\r\n## TODO\r\n\r\nI was thinking about putting up snippets for different commands for\r\ndifferent languages, kind of like snipmate snippets.\r\n\r\nAdd docs.","install_details":"Copy plugin to ~\/.vim\/","5":"Copy plugin to ~\/.vim\/","first_name":"William","6":"William","last_name":"Estoque","7":"Estoque","releases":[{"0":"4032","vim_version":"7.0","1":"7.0","script_version":"0.0.2","2":"0.0.2","version_comment":"Renamed main file from vimux.vim to muxmate.vim","3":"Renamed main file from vimux.vim to muxmate.vim","package":"muxmate.tar.gz","4":"muxmate.tar.gz","src_id":"17823","5":"17823","creation_date":"1335463757","6":"1335463757"},{"0":"4032","vim_version":"7.0","1":"7.0","script_version":"0.0.1","2":"0.0.1","version_comment":"Initial upload","3":"Initial upload","package":"muxmate.tar.gz","4":"muxmate.tar.gz","src_id":"17822","5":"17822","creation_date":"1335463204","6":"1335463204"}]},"4031":{"script_id":"4031","0":"4031","script_name":"rstatusline","1":"rstatusline","script_type":"utility","2":"utility","summary":"show buffer list on statusline with highlight","3":"show buffer list on statusline with highlight","description":"rstatusline is a small plugin to show buffer list on statusline with highlight on current buffer name.","4":"rstatusline is a small plugin to show buffer list on statusline with highlight on current buffer name.","install_details":"cp rstatusline.vim to ~\/.vim\/plugin\r\n\r\nto use this plugin please comment out the statusline options(eg: laststatus,statusline) set by yourself in vimrc.\r\nfor convenience, you may map some keybinds like these:\r\nmap <f3> :bp<cr>\r\nmap <f4> :bn<cr>","5":"cp rstatusline.vim to ~\/.vim\/plugin\r\n\r\nto use this plugin please comment out the statusline options(eg: laststatus,statusline) set by yourself in vimrc.\r\nfor convenience, you may map some keybinds like these:\r\nmap <f3> :bp<cr>\r\nmap <f4> :bn<cr>","first_name":"ruoshan","6":"ruoshan","last_name":"huang","7":"huang","releases":[{"0":"4031","vim_version":"7.0","1":"7.0","script_version":"0.1.4","2":"0.1.4","version_comment":"fix the long-exist noshowing full buffer-list problem. change user customization option more friendly.","3":"fix the long-exist noshowing full buffer-list problem. change user customization option more friendly.","package":"rstatusline.vim","4":"rstatusline.vim","src_id":"21533","5":"21533","creation_date":"1393299234","6":"1393299234"},{"0":"4031","vim_version":"7.0","1":"7.0","script_version":"0.1.3","2":"0.1.3","version_comment":"bug-fix:highlight same name in different window with different buffer.","3":"bug-fix:highlight same name in different window with different buffer.","package":"rstatusline.vim","4":"rstatusline.vim","src_id":"18355","5":"18355","creation_date":"1343748082","6":"1343748082"},{"0":"4031","vim_version":"7.0","1":"7.0","script_version":"v0.1.2","2":"v0.1.2","version_comment":"fix the improper total buf count (exclude hidden ones). fix two or more spaces been shown between list items (only one space separator now). never show the hidden buffers now.","3":"fix the improper total buf count (exclude hidden ones). fix two or more spaces been shown between list items (only one space separator now). never show the hidden buffers now.","package":"rstatusline.vim","4":"rstatusline.vim","src_id":"17847","5":"17847","creation_date":"1335884920","6":"1335884920"},{"0":"4031","vim_version":"7.0","1":"7.0","script_version":"v0.1.1","2":"v0.1.1","version_comment":"correct some mistake","3":"correct some mistake","package":"rstatusline.vim","4":"rstatusline.vim","src_id":"17820","5":"17820","creation_date":"1335441111","6":"1335441111"},{"0":"4031","vim_version":"7.0","1":"7.0","script_version":"v0.1","2":"v0.1","version_comment":"Initial upload","3":"Initial upload","package":"rstatusline.vim","4":"rstatusline.vim","src_id":"17817","5":"17817","creation_date":"1335416610","6":"1335416610"}]},"4030":{"script_id":"4030","0":"4030","script_name":"vim-cpp-auto-include","1":"vim-cpp-auto-include","script_type":"ftplugin","2":"ftplugin","summary":"Automatically insert or delete `#include`s for C++ code","3":"Automatically insert or delete `#include`s for C++ code","description":"For updated information, see https:\/\/github.com\/quark-zju\/vim-cpp-auto-include\r\n\r\nScreencast\r\n====\r\nhttps:\/\/github.com\/quark-zju\/vim-cpp-auto-include\/raw\/master\/demo\/vim-cpp-auto-include-demo.gif\r\n\r\nNote\r\n====\r\nThis plugin is intended to be simple and intended to be used on simple C++ files only.\r\n\r\nUsage\r\n====\r\n:w\r\n\r\nConfiguration\r\n====\r\nBy default, only C++ files in \/tmp are processed.\r\n\r\nAdd following line in your `.vimrc` to make your C++ code in `\/some\/path\/` processed when saving:\r\n\r\n    autocmd BufWritePre \/some\/path\/**.cpp :ruby CppAutoInclude::process\r\n \r\nIf you want more control, feel free to edit the source :)","4":"For updated information, see https:\/\/github.com\/quark-zju\/vim-cpp-auto-include\r\n\r\nScreencast\r\n====\r\nhttps:\/\/github.com\/quark-zju\/vim-cpp-auto-include\/raw\/master\/demo\/vim-cpp-auto-include-demo.gif\r\n\r\nNote\r\n====\r\nThis plugin is intended to be simple and intended to be used on simple C++ files only.\r\n\r\nUsage\r\n====\r\n:w\r\n\r\nConfiguration\r\n====\r\nBy default, only C++ files in \/tmp are processed.\r\n\r\nAdd following line in your `.vimrc` to make your C++ code in `\/some\/path\/` processed when saving:\r\n\r\n    autocmd BufWritePre \/some\/path\/**.cpp :ruby CppAutoInclude::process\r\n \r\nIf you want more control, feel free to edit the source :)","install_details":"Copy the script to ~\/.vim\/plugin\/\r\n\r\nAlternatively, with Vundle, add \"Bundle 'quark-zju\/vim-cpp-auto-include'\" in ~\/.vimrc and run \"BundleInstall\" in vim.","5":"Copy the script to ~\/.vim\/plugin\/\r\n\r\nAlternatively, with Vundle, add \"Bundle 'quark-zju\/vim-cpp-auto-include'\" in ~\/.vimrc and run \"BundleInstall\" in vim.","first_name":"WU","6":"WU","last_name":"Jun","7":"Jun","releases":[{"0":"4030","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"cpp_auto_include.vim","4":"cpp_auto_include.vim","src_id":"17814","5":"17814","creation_date":"1335314475","6":"1335314475"}]},"4029":{"script_id":"4029","0":"4029","script_name":"a new txt2tags syntax","1":"a new txt2tags syntax","script_type":"syntax","2":"syntax","summary":"a new version of txt2tags syntax file","3":"a new version of txt2tags syntax file","description":"syn match t2tTitle1 '^ *\\(=\\)[^=]\\(\\|.*[^=]\\)\\1\\(\\[[a-z0-9_-]*\\]\\)\\=\\s*$' contains=t2tTitleMark,t2tTitleRef\r\nsyn match t2tTitle2 '^ *\\(==\\)[^=]\\(\\|.*[^=]\\)\\1\\(\\[[a-z0-9_-]*\\]\\)\\=\\s*$' contains=t2tTitleMark,t2tTitleRef\r\nsyn match t2tTitle3 '^ *\\(===\\)[^=]\\(\\|.*[^=]\\)\\1\\(\\[[a-z0-9_-]*\\]\\)\\=\\s*$' contains=t2tTitleMark,t2tTitleRef\r\nsyn match t2tTitle4 '^ *\\(====\\)[^=]\\(\\|.*[^=]\\)\\1\\(\\[[a-z0-9_-]*\\]\\)\\=\\s*$' contains=t2tTitleMark,t2tTitleRef\r\nsyn match t2tTitle5 '^ *\\(=====\\)[^=]\\(\\|.*[^=]\\)\\1\\(\\[[a-z0-9_-]*\\]\\)\\=\\s*$' contains=t2tTitleMark,t2tTitleRef\r\n\r\netc\r\nadd +aaa+ ++aaa++ different color.","4":"syn match t2tTitle1 '^ *\\(=\\)[^=]\\(\\|.*[^=]\\)\\1\\(\\[[a-z0-9_-]*\\]\\)\\=\\s*$' contains=t2tTitleMark,t2tTitleRef\r\nsyn match t2tTitle2 '^ *\\(==\\)[^=]\\(\\|.*[^=]\\)\\1\\(\\[[a-z0-9_-]*\\]\\)\\=\\s*$' contains=t2tTitleMark,t2tTitleRef\r\nsyn match t2tTitle3 '^ *\\(===\\)[^=]\\(\\|.*[^=]\\)\\1\\(\\[[a-z0-9_-]*\\]\\)\\=\\s*$' contains=t2tTitleMark,t2tTitleRef\r\nsyn match t2tTitle4 '^ *\\(====\\)[^=]\\(\\|.*[^=]\\)\\1\\(\\[[a-z0-9_-]*\\]\\)\\=\\s*$' contains=t2tTitleMark,t2tTitleRef\r\nsyn match t2tTitle5 '^ *\\(=====\\)[^=]\\(\\|.*[^=]\\)\\1\\(\\[[a-z0-9_-]*\\]\\)\\=\\s*$' contains=t2tTitleMark,t2tTitleRef\r\n\r\netc\r\nadd +aaa+ ++aaa++ different color.","install_details":"","5":"","first_name":"thomas","6":"thomas","last_name":"young","7":"young","releases":[{"0":"4029","vim_version":"7.0","1":"7.0","script_version":"2.1","2":"2.1","version_comment":"Initial upload","3":"Initial upload","package":"txt2tags.vim","4":"txt2tags.vim","src_id":"17813","5":"17813","creation_date":"1335265529","6":"1335265529"}]},"4028":{"script_id":"4028","0":"4028","script_name":"vim-addon-ruby-debug-ide","1":"vim-addon-ruby-debug-ide","script_type":"utility","2":"utility","summary":"ruby-debug-ide implementation","3":"ruby-debug-ide implementation","description":"full debugger implementation for ruby.\r\nWork in progress, check github page:\r\nhttps:\/\/github.com\/MarcWeber\/vim-addon-ruby-debug-ide\r\n\r\nbasics are working and remaining stuff can be implemented easily, progress see README.\r\nbreakpoints, stepping, restarting, var view\r\n\r\nbased on vim-addon-async (async communication without blocking vim)\r\n\r\nWith nox patch (client-server without X) this can be used on servers to debug ruby code, see docs of vim-addon-async.","4":"full debugger implementation for ruby.\r\nWork in progress, check github page:\r\nhttps:\/\/github.com\/MarcWeber\/vim-addon-ruby-debug-ide\r\n\r\nbasics are working and remaining stuff can be implemented easily, progress see README.\r\nbreakpoints, stepping, restarting, var view\r\n\r\nbased on vim-addon-async (async communication without blocking vim)\r\n\r\nWith nox patch (client-server without X) this can be used on servers to debug ruby code, see docs of vim-addon-async.","install_details":"Use my github page to latest version, please:\r\nhttps:\/\/github.com\/MarcWeber\/vim-addon-ruby-debug-ide\r\n\r\nrecommended way use VAM \"github:MarcWeber\/vim-addon-ruby-debug-ide\",\r\nin a couple of days the addon name can be used.\r\n\r\nYes you can install manually, see addon-info.json for list of dependencies.","5":"Use my github page to latest version, please:\r\nhttps:\/\/github.com\/MarcWeber\/vim-addon-ruby-debug-ide\r\n\r\nrecommended way use VAM \"github:MarcWeber\/vim-addon-ruby-debug-ide\",\r\nin a couple of days the addon name can be used.\r\n\r\nYes you can install manually, see addon-info.json for list of dependencies.","first_name":"Marc","6":"Marc","last_name":"Weber","7":"Weber","releases":[{"0":"4028","vim_version":"7.0","1":"7.0","script_version":"0.0","2":"0.0","version_comment":"Initial upload","3":"Initial upload","package":"rd.zip","4":"rd.zip","src_id":"17809","5":"17809","creation_date":"1335114327","6":"1335114327"}]},"4027":{"script_id":"4027","0":"4027","script_name":"vim-htmldjango_omnicomplete","1":"vim-htmldjango_omnicomplete","script_type":"ftplugin","2":"ftplugin","summary":"htmldjango filetype omnicomplete - completes template tags\/filters\/variables ","3":"htmldjango filetype omnicomplete - completes template tags\/filters\/variables ","description":"Vim htmldjango autocomplete\r\n\r\nAn omnicomplete tailored to django templates \"tags\/variables\/filters\/templates\" I mainly find it useful for completing template and static directory paths. It will also fall back to regular html omnicomplete\r\n\r\nRepo: http:\/\/github.com\/mjbrownie\/vim-htmldjango_omnicomplete (star it for updates, feedback appreciated)\r\n\r\n\r\nScreenshots:\r\n\r\n    block: https:\/\/github.com\/mjbrownie\/vim-htmldjango_omnicomplete\/raw\/master\/examples\/block_eample.png\r\n    url: https:\/\/github.com\/mjbrownie\/vim-htmldjango_omnicomplete\/raw\/master\/examples\/url_example.png\r\n    extends: https:\/\/github.com\/mjbrownie\/vim-htmldjango_omnicomplete\/blob\/master\/examples\/extends_example.png\r\n\r\nEg.\r\n\r\n    1. Filters\r\n\r\n        {{ somevar|a<c-x><c-o>}} should complete 'add' , 'addslashes'\r\n\r\n    2. Tags\r\n\r\n        {% cy<c-x><x-o> %} should complete 'cycle'\r\n\r\n    3. Load statements\r\n\r\n        It also should grab any libs you have {% load tag_lib %} in the file.\r\n        Although it needs them in INSTALLED_APPS.\r\n\r\n        {% load <c-x><c-o> %} will complete libraries (eg. 'cache', 'humanize')\r\n\r\n    4. template filenames\r\n\r\n        {% extends '<c-x><c-o>' %} will list base.html ... etc\r\n\r\n    5. url complete\r\n\r\n        {% url <c-x><c-o> %} should complete views and named urls\r\n\r\n    6. super block complete\r\n\r\n        eg {% block c<c-x><c-o> %} to complete 'content' or something defined\r\n        in an extended template.\r\n\r\n\r\n    7. static files complete\r\n\r\n        eg {% static \"r<c-x><c-o>\" %}\r\n\r\n        <script src=\"{% static \"<c-x><c-o>\" %}\" \/> - completes js files in static\r\n        <style src=\"{% static \"<c-x><c-o>\" %}\" \/> - completes css files in static\r\n        <img src=\"{% static \"<c-x><c-o>\" %}\" \/> - completes img files in static\r\n        {{ s<c-x><x-o> }}\r\n\r\n    8. optional variable name completion (placeholder)\r\n\r\n        will complete any maps defined in the python htmldjango_opts['variable']\r\n        dict list. See below for info.\r\n\r\n\r\n    Where possible info panels show the functions __doc__. Most of the\r\n    internal ones are decent.\r\n\r\nRequires:\r\n\r\n    +python\r\n\r\n    I have this working on command line vim for linux and mac (I had to compile my own for osx with .\/configure --enable-pythoninterp --with-features=huge). \r\n\r\n    also I have DJANGO_SETTINGS_MODULE set in my vimrc. please look at my dotfiles if you are having trouble\r\n\r\n    https:\/\/github.com\/mjbrownie\/dotfiles\/blob\/master\/_vimrc#L312-L340\r\n\r\nSETUP\r\n\r\n    1. I like pathogen\/Vundle clone into ~\/.vim\/bundle directory.\r\n\r\n        Alternately just stick the vim file in your ~\/.vim\/autoload\/ dir.\r\n\r\n    2. in .vimrc set the omnifunc Eg.\r\n\r\n        au FileType htmldjango set omnifunc=htmldjangocomplete#CompleteDjango\r\n\r\n    3. Optional: At the moment you need to force a html flavour for htmlcompletion\r\n\r\n        in .vimrc\r\n\r\n        let g:htmldjangocomplete_html_flavour = 'html401s'\r\n\r\n        :verbose function htmlcomplete#CheckDoctype for DocType details\r\n\r\n        Choices:\r\n            'html401t' 'xhtml10s' 'html32' 'html40t' 'html40f' 'html40s'\r\n            'html401t' 'html401f' 'html401s' 'xhtml10t' 'xhtml10f' 'xhtml10s'\r\n            'xhtml11'\r\n\r\n            'html5' if you have html5.vim\r\n\r\nTESTING\r\n\r\n    django needs to be in sys.path along with DJANGO_SETTINGS_MODULE in your\r\n    environment.\r\n\r\n    To test...\r\n\r\n    :python import django\r\n\r\n    should not result in an error\r\n\r\n    :python from django.conf import settings; print settings.INSTALLED_APPS\r\n    :python from django.conf import settings; print settings.TEMPLATE_DIRS\r\n\r\n    should show the apps template dirs you need\r\n\r\n    I've only tested this on a mac with vim 7.3 and django 1.4","4":"Vim htmldjango autocomplete\r\n\r\nAn omnicomplete tailored to django templates \"tags\/variables\/filters\/templates\" I mainly find it useful for completing template and static directory paths. It will also fall back to regular html omnicomplete\r\n\r\nRepo: http:\/\/github.com\/mjbrownie\/vim-htmldjango_omnicomplete (star it for updates, feedback appreciated)\r\n\r\n\r\nScreenshots:\r\n\r\n    block: https:\/\/github.com\/mjbrownie\/vim-htmldjango_omnicomplete\/raw\/master\/examples\/block_eample.png\r\n    url: https:\/\/github.com\/mjbrownie\/vim-htmldjango_omnicomplete\/raw\/master\/examples\/url_example.png\r\n    extends: https:\/\/github.com\/mjbrownie\/vim-htmldjango_omnicomplete\/blob\/master\/examples\/extends_example.png\r\n\r\nEg.\r\n\r\n    1. Filters\r\n\r\n        {{ somevar|a<c-x><c-o>}} should complete 'add' , 'addslashes'\r\n\r\n    2. Tags\r\n\r\n        {% cy<c-x><x-o> %} should complete 'cycle'\r\n\r\n    3. Load statements\r\n\r\n        It also should grab any libs you have {% load tag_lib %} in the file.\r\n        Although it needs them in INSTALLED_APPS.\r\n\r\n        {% load <c-x><c-o> %} will complete libraries (eg. 'cache', 'humanize')\r\n\r\n    4. template filenames\r\n\r\n        {% extends '<c-x><c-o>' %} will list base.html ... etc\r\n\r\n    5. url complete\r\n\r\n        {% url <c-x><c-o> %} should complete views and named urls\r\n\r\n    6. super block complete\r\n\r\n        eg {% block c<c-x><c-o> %} to complete 'content' or something defined\r\n        in an extended template.\r\n\r\n\r\n    7. static files complete\r\n\r\n        eg {% static \"r<c-x><c-o>\" %}\r\n\r\n        <script src=\"{% static \"<c-x><c-o>\" %}\" \/> - completes js files in static\r\n        <style src=\"{% static \"<c-x><c-o>\" %}\" \/> - completes css files in static\r\n        <img src=\"{% static \"<c-x><c-o>\" %}\" \/> - completes img files in static\r\n        {{ s<c-x><x-o> }}\r\n\r\n    8. optional variable name completion (placeholder)\r\n\r\n        will complete any maps defined in the python htmldjango_opts['variable']\r\n        dict list. See below for info.\r\n\r\n\r\n    Where possible info panels show the functions __doc__. Most of the\r\n    internal ones are decent.\r\n\r\nRequires:\r\n\r\n    +python\r\n\r\n    I have this working on command line vim for linux and mac (I had to compile my own for osx with .\/configure --enable-pythoninterp --with-features=huge). \r\n\r\n    also I have DJANGO_SETTINGS_MODULE set in my vimrc. please look at my dotfiles if you are having trouble\r\n\r\n    https:\/\/github.com\/mjbrownie\/dotfiles\/blob\/master\/_vimrc#L312-L340\r\n\r\nSETUP\r\n\r\n    1. I like pathogen\/Vundle clone into ~\/.vim\/bundle directory.\r\n\r\n        Alternately just stick the vim file in your ~\/.vim\/autoload\/ dir.\r\n\r\n    2. in .vimrc set the omnifunc Eg.\r\n\r\n        au FileType htmldjango set omnifunc=htmldjangocomplete#CompleteDjango\r\n\r\n    3. Optional: At the moment you need to force a html flavour for htmlcompletion\r\n\r\n        in .vimrc\r\n\r\n        let g:htmldjangocomplete_html_flavour = 'html401s'\r\n\r\n        :verbose function htmlcomplete#CheckDoctype for DocType details\r\n\r\n        Choices:\r\n            'html401t' 'xhtml10s' 'html32' 'html40t' 'html40f' 'html40s'\r\n            'html401t' 'html401f' 'html401s' 'xhtml10t' 'xhtml10f' 'xhtml10s'\r\n            'xhtml11'\r\n\r\n            'html5' if you have html5.vim\r\n\r\nTESTING\r\n\r\n    django needs to be in sys.path along with DJANGO_SETTINGS_MODULE in your\r\n    environment.\r\n\r\n    To test...\r\n\r\n    :python import django\r\n\r\n    should not result in an error\r\n\r\n    :python from django.conf import settings; print settings.INSTALLED_APPS\r\n    :python from django.conf import settings; print settings.TEMPLATE_DIRS\r\n\r\n    should show the apps template dirs you need\r\n\r\n    I've only tested this on a mac with vim 7.3 and django 1.4","install_details":"pathogen and github clone recommended as updates will be less frequent here.\r\n\r\ncd ~\/.vim\/bundle && git clone git@github.com:mjbrownie\/vim-htmldjango_omnicomplete.git\r\n\r\nor extract and copy .vim file to ~\/.vim\/autoload","5":"pathogen and github clone recommended as updates will be less frequent here.\r\n\r\ncd ~\/.vim\/bundle && git clone git@github.com:mjbrownie\/vim-htmldjango_omnicomplete.git\r\n\r\nor extract and copy .vim file to ~\/.vim\/autoload","first_name":"Michael","6":"Michael","last_name":"Brown","7":"Brown","releases":[{"0":"4027","vim_version":"7.0","1":"7.0","script_version":"0.9.4","2":"0.9.4","version_comment":"Django 1.8 compatibility","3":"Django 1.8 compatibility","package":"vim-htmldjango_omnicomplete-0.9.4.zip","4":"vim-htmldjango_omnicomplete-0.9.4.zip","src_id":"23324","5":"23324","creation_date":"1432892781","6":"1432892781"},{"0":"4027","vim_version":"7.0","1":"7.0","script_version":"0.9.3","2":"0.9.3","version_comment":"Added support for django 1.7+ - Thanks Daniel Hahler ","3":"Added support for django 1.7+ - Thanks Daniel Hahler ","package":"vim-htmldjango_omnicomplete-0.9.3.zip","4":"vim-htmldjango_omnicomplete-0.9.3.zip","src_id":"22758","5":"22758","creation_date":"1420508941","6":"1420508941"},{"0":"4027","vim_version":"7.0","1":"7.0","script_version":"0.9","2":"0.9","version_comment":"Added staticfiles {% static %} for js\/css\/img in all app\/project directories","3":"Added staticfiles {% static %} for js\/css\/img in all app\/project directories","package":"vim-htmldjango_omnicomplete-master.tar.gz","4":"vim-htmldjango_omnicomplete-master.tar.gz","src_id":"19042","5":"19042","creation_date":"1353972289","6":"1353972289"},{"0":"4027","vim_version":"7.0","1":"7.0","script_version":"0.8.1","2":"0.8.1","version_comment":"Added warning suppression to stop depreciation messages in apps appearing on initial load.","3":"Added warning suppression to stop depreciation messages in apps appearing on initial load.","package":"vim-htmldjango_omnicomplete-b54beb0e57.tar.gz","4":"vim-htmldjango_omnicomplete-b54beb0e57.tar.gz","src_id":"19024","5":"19024","creation_date":"1353769616","6":"1353769616"},{"0":"4027","vim_version":"7.2","1":"7.2","script_version":"0.8","2":"0.8","version_comment":"added {% block | %} name autocomplete","3":"added {% block | %} name autocomplete","package":"mjbrownie-vim-htmldjango_omnicomplete-7c6d8c7.tar.gz","4":"mjbrownie-vim-htmldjango_omnicomplete-7c6d8c7.tar.gz","src_id":"18003","5":"18003","creation_date":"1337574037","6":"1337574037"},{"0":"4027","vim_version":"7.0","1":"7.0","script_version":"0.7","2":"0.7","version_comment":"added named url completion, improved support for inline include tag matching.\r\nFixed missing glob import","3":"added named url completion, improved support for inline include tag matching.\r\nFixed missing glob import","package":"mjbrownie-vim-htmldjango_omnicomplete-69a285f.zip","4":"mjbrownie-vim-htmldjango_omnicomplete-69a285f.zip","src_id":"17829","5":"17829","creation_date":"1335578343","6":"1335578343"}]},"4026":{"script_id":"4026","0":"4026","script_name":"Splice","1":"Splice","script_type":"utility","2":"utility","summary":"Initial stable release.","3":"Initial stable release.","description":"Splice is a Vim plugin for resolving conflicts during three-way merges.\r\n\r\nIt's designed to be used as a merge tool for version control systems like Mercurial and Git.\r\n\r\nGo to the site for more information: http:\/\/sjl.bitbucket.org\/splice.vim\/","4":"Splice is a Vim plugin for resolving conflicts during three-way merges.\r\n\r\nIt's designed to be used as a merge tool for version control systems like Mercurial and Git.\r\n\r\nGo to the site for more information: http:\/\/sjl.bitbucket.org\/splice.vim\/","install_details":"Use Pathogen.","5":"Use Pathogen.","first_name":"Steve","6":"Steve","last_name":"Losh","7":"Losh","releases":[{"0":"4026","vim_version":"7.3","1":"7.3","script_version":"1.1.0","2":"1.1.0","version_comment":"Initial Python 3 support.","3":"Initial Python 3 support.","package":"splice.zip","4":"splice.zip","src_id":"24593","5":"24593","creation_date":"1475932223","6":"1475932223"},{"0":"4026","vim_version":"7.3","1":"7.3","script_version":"1.0.1","2":"1.0.1","version_comment":"Various bugfixes.","3":"Various bugfixes.","package":"splice.zip","4":"splice.zip","src_id":"19173","5":"19173","creation_date":"1355336044","6":"1355336044"},{"0":"4026","vim_version":"7.3","1":"7.3","script_version":"1.0.0","2":"1.0.0","version_comment":"Initial upload","3":"Initial upload","package":"splice.zip","4":"splice.zip","src_id":"17800","5":"17800","creation_date":"1334941290","6":"1334941290"}]},"4025":{"script_id":"4025","0":"4025","script_name":"DBGp X client","1":"DBGp X client","script_type":"utility","2":"utility","summary":"a real remote debugger (tested only with XDebug\/PHP)","3":"a real remote debugger (tested only with XDebug\/PHP)","description":"This python script provide debugger interface to DBGp protocol, \r\nNow support debugging files between two hosts that the path of the project on remote host and local host is different.\r\n\r\nThe original script was written by Sam Ghods and Seung Woo Shin,\r\nlocated at: \r\nvimscript #1929\r\nvimscript #1152\r\nThis is a slightly modified version of that script with a few additional capabilities. \r\n\r\nRequirements) \r\n- DBGp protocol enabled debugging module. such as xdebug. \r\n  ( I don't know there are free DBGp debugger except xdebug ) \r\n- +python2.7 , +sign feature  !\r\n- this vim script. ( debugger.vim \/ debugger.py ) \r\n\r\n\r\nUsage) \r\n1. setup xdebug correctly. or other DBGp enabled server, \r\n    (with proper remote debug option, etc xdebug.remote_enable = 1) \r\n\r\n2. If you are debugging on two machines, \r\n    and the path of your project is different between local host and remote host,\r\n    you should  add a user mapping for local files to remote files in your vimrc like this:\r\n\r\n    let g:debuggerPath = {'sep': ['\/', '\/'], 'map': [\r\n                          \\['\/local\/path\/to\/project1', '\/remote\/path\/to\/project\/1'],\r\n                          \\['\/local\/path\/to\/project2', '\/remote\/path\/to\/project\/2'],\r\n                          \\['\/local\/path\/to\/project3', '\/remote\/path\/to\/project\/3'],\r\n                          \\]}\r\n\r\n    The key \"sep\" means the path separator of os,\r\n    On unix and Mac, is \"\/\", On Windows, it is \"\\\".\r\n    As you can see, the first element in sep list is the local path\r\n    separator, the second element in sep list is the remote path\r\n    separator.\r\n\r\n3. press <F5> and browse php file within 8 seconds. :-) \r\n    (If you are using Xdebug, just add param to the url etc index.php?XDEBUG_SESSION_START=1 )\r\n\r\n    If you did setup correctly, server will make connection to vim, \r\n    all the windows currently opened will be closed and debugger interface will be shown. \r\n\r\n4. in debuggin mode \r\n<F1> : resizing windows \r\n<F2> : step into \r\n<F3> : step over \r\n<F4> : step out \r\n<F5> : run to breakpoint\r\n\r\n<S-F5> stop debugging\r\n\r\n<F10> : shows variable on current cursor \r\n<F11> : shows context\r\n<F12> : shows property on current cursor \r\n\r\n,e : evalute expression and display result. cursor is automatically move to watch window. type line and just press enter. \r\n\r\ncommand line command) \r\n:Bp    : toggle breakpoint on current line \r\n:Up    : goto upper level of stack \r\n:Dn    : goto lower level of stack \r\n\r\n5. press <S-F5> to stop debugging. \r\n\r\n**This script has only been tested with XDebug for PHP debugging. But it may work with other debuggers.\r\n\r\nOkay, forget my poor English...\r\n============================================================================\r\n\r\n这是一个利用 DBGp 协议实现的调试器，\r\n开发机上需要有python环境，一般linux自带，win下个python2.7安装之～\r\n同时vim必须要有+python和+sign特性，这个在现有的gvim7.3上应该都支持了。\r\n\r\n插件基于DBGp client，主要增改是：\r\n\r\n**** 1，增加远程机器调试支持！\r\n因为远程机器上的项目，文件物理地址一般跟开发机器不同，需要做路径映射，\r\n这个使用过其它 IDE(比如netbeans) 做调试的同学应该很清楚，\r\n比如服务器上的文件 \/var\/www\/index.php，\r\n在你的开发机器上这个文件可能位于 \/home\/me\/develop\/index.php\r\n那你就必须将 \/home\/me\/develop\/ 映射到 \/var\/www\/，\r\n可用的配置项是：\r\n\r\n    let g:debuggerPath = {'sep': ['\/', '\/'], 'map': [\r\n            \\['\/home\/me\/develop\/', '\/var\/www\/'],\r\n            \\]}\r\n\r\n        其中，sep对应的列表项第一项是你开发机的目录分隔符，第二项是服务器的，\r\n        在linux和mac上是 \/，而在windows上是 \\，注意：是单一字符，反斜杠不要写两遍！用单引号括起来。\r\n\r\n        同时，map对应的列表项则是每一项 开发机路径，服务器路径 的映射，记住路径最后要以分割符结尾。\r\n\r\n\r\n**** 2，增加一键获取当前位置变量值的功能(默认快捷键 F10 )\r\nDBGp本身有property_get方法可以获取格式化很漂亮的变量值，但有时候不可用！！\r\n新增的这个一键获取当前位置变量值的功能和netbeans调试器的功能一致，都是利用 eval $var 实现，\r\n在property_get不可用的情况下可使用该方法替代它！\r\n远程调试的过程中property_get经常是不可用的，一般只在第一个堆栈有效，\r\n但是服务器和开发机同一台机时，几乎没有什么问题！？\r\n希望哪位同学知道为什么的能告知我一声。。。\r\n\r\n\r\n**** 3，移除mksession相关实现\r\n这个实现导致插件在不同平台上可用性下降（需要写磁盘文件），\r\n而且本身在Vim里的特性支持也并不稳定，故移除之！\r\n\r\n\r\n**** 4，重定义部分快捷键\r\n\r\n\r\n**** 5，总的来说，就是这样了。","4":"This python script provide debugger interface to DBGp protocol, \r\nNow support debugging files between two hosts that the path of the project on remote host and local host is different.\r\n\r\nThe original script was written by Sam Ghods and Seung Woo Shin,\r\nlocated at: \r\nvimscript #1929\r\nvimscript #1152\r\nThis is a slightly modified version of that script with a few additional capabilities. \r\n\r\nRequirements) \r\n- DBGp protocol enabled debugging module. such as xdebug. \r\n  ( I don't know there are free DBGp debugger except xdebug ) \r\n- +python2.7 , +sign feature  !\r\n- this vim script. ( debugger.vim \/ debugger.py ) \r\n\r\n\r\nUsage) \r\n1. setup xdebug correctly. or other DBGp enabled server, \r\n    (with proper remote debug option, etc xdebug.remote_enable = 1) \r\n\r\n2. If you are debugging on two machines, \r\n    and the path of your project is different between local host and remote host,\r\n    you should  add a user mapping for local files to remote files in your vimrc like this:\r\n\r\n    let g:debuggerPath = {'sep': ['\/', '\/'], 'map': [\r\n                          \\['\/local\/path\/to\/project1', '\/remote\/path\/to\/project\/1'],\r\n                          \\['\/local\/path\/to\/project2', '\/remote\/path\/to\/project\/2'],\r\n                          \\['\/local\/path\/to\/project3', '\/remote\/path\/to\/project\/3'],\r\n                          \\]}\r\n\r\n    The key \"sep\" means the path separator of os,\r\n    On unix and Mac, is \"\/\", On Windows, it is \"\\\".\r\n    As you can see, the first element in sep list is the local path\r\n    separator, the second element in sep list is the remote path\r\n    separator.\r\n\r\n3. press <F5> and browse php file within 8 seconds. :-) \r\n    (If you are using Xdebug, just add param to the url etc index.php?XDEBUG_SESSION_START=1 )\r\n\r\n    If you did setup correctly, server will make connection to vim, \r\n    all the windows currently opened will be closed and debugger interface will be shown. \r\n\r\n4. in debuggin mode \r\n<F1> : resizing windows \r\n<F2> : step into \r\n<F3> : step over \r\n<F4> : step out \r\n<F5> : run to breakpoint\r\n\r\n<S-F5> stop debugging\r\n\r\n<F10> : shows variable on current cursor \r\n<F11> : shows context\r\n<F12> : shows property on current cursor \r\n\r\n,e : evalute expression and display result. cursor is automatically move to watch window. type line and just press enter. \r\n\r\ncommand line command) \r\n:Bp    : toggle breakpoint on current line \r\n:Up    : goto upper level of stack \r\n:Dn    : goto lower level of stack \r\n\r\n5. press <S-F5> to stop debugging. \r\n\r\n**This script has only been tested with XDebug for PHP debugging. But it may work with other debuggers.\r\n\r\nOkay, forget my poor English...\r\n============================================================================\r\n\r\n这是一个利用 DBGp 协议实现的调试器，\r\n开发机上需要有python环境，一般linux自带，win下个python2.7安装之～\r\n同时vim必须要有+python和+sign特性，这个在现有的gvim7.3上应该都支持了。\r\n\r\n插件基于DBGp client，主要增改是：\r\n\r\n**** 1，增加远程机器调试支持！\r\n因为远程机器上的项目，文件物理地址一般跟开发机器不同，需要做路径映射，\r\n这个使用过其它 IDE(比如netbeans) 做调试的同学应该很清楚，\r\n比如服务器上的文件 \/var\/www\/index.php，\r\n在你的开发机器上这个文件可能位于 \/home\/me\/develop\/index.php\r\n那你就必须将 \/home\/me\/develop\/ 映射到 \/var\/www\/，\r\n可用的配置项是：\r\n\r\n    let g:debuggerPath = {'sep': ['\/', '\/'], 'map': [\r\n            \\['\/home\/me\/develop\/', '\/var\/www\/'],\r\n            \\]}\r\n\r\n        其中，sep对应的列表项第一项是你开发机的目录分隔符，第二项是服务器的，\r\n        在linux和mac上是 \/，而在windows上是 \\，注意：是单一字符，反斜杠不要写两遍！用单引号括起来。\r\n\r\n        同时，map对应的列表项则是每一项 开发机路径，服务器路径 的映射，记住路径最后要以分割符结尾。\r\n\r\n\r\n**** 2，增加一键获取当前位置变量值的功能(默认快捷键 F10 )\r\nDBGp本身有property_get方法可以获取格式化很漂亮的变量值，但有时候不可用！！\r\n新增的这个一键获取当前位置变量值的功能和netbeans调试器的功能一致，都是利用 eval $var 实现，\r\n在property_get不可用的情况下可使用该方法替代它！\r\n远程调试的过程中property_get经常是不可用的，一般只在第一个堆栈有效，\r\n但是服务器和开发机同一台机时，几乎没有什么问题！？\r\n希望哪位同学知道为什么的能告知我一声。。。\r\n\r\n\r\n**** 3，移除mksession相关实现\r\n这个实现导致插件在不同平台上可用性下降（需要写磁盘文件），\r\n而且本身在Vim里的特性支持也并不稳定，故移除之！\r\n\r\n\r\n**** 4，重定义部分快捷键\r\n\r\n\r\n**** 5，总的来说，就是这样了。","install_details":"put all files in ~\/.vim\/plugin directory(or equivalent, e.g. $HOME\\vim73\\plugin))","5":"put all files in ~\/.vim\/plugin directory(or equivalent, e.g. $HOME\\vim73\\plugin))","first_name":"-","6":"-","last_name":"-","7":"-","releases":[{"0":"4025","vim_version":"7.0","1":"7.0","script_version":"2.0.2","2":"2.0.2","version_comment":"Auto detect if using the Mini Buffer Explorer vim plugin","3":"Auto detect if using the Mini Buffer Explorer vim plugin","package":"debugger2.0.2.zip","4":"debugger2.0.2.zip","src_id":"17812","5":"17812","creation_date":"1335242459","6":"1335242459"}]},"4024":{"script_id":"4024","0":"4024","script_name":"vim-addon-rdebug","1":"vim-addon-rdebug","script_type":"utility","2":"utility","summary":"minimal ruby rdebug implementation","3":"minimal ruby rdebug implementation","description":"run ruby process using vim-addon-async, but intercept line locations of ruby rdebug debugger and show lines.\r\nYou can talk to the debugger and add breakpoints.\r\n\r\nKISS debugging for ruby","4":"run ruby process using vim-addon-async, but intercept line locations of ruby rdebug debugger and show lines.\r\nYou can talk to the debugger and add breakpoints.\r\n\r\nKISS debugging for ruby","install_details":"github.com\/MarcWeber\/vim-addon-rdebug\r\n(I recommend vim-addon-manager due to dependencies, but all other ways will also work)","5":"github.com\/MarcWeber\/vim-addon-rdebug\r\n(I recommend vim-addon-manager due to dependencies, but all other ways will also work)","first_name":"Marc","6":"Marc","last_name":"Weber","7":"Weber","releases":[{"0":"4024","vim_version":"7.0","1":"7.0","script_version":"0.0","2":"0.0","version_comment":"Initial upload","3":"Initial upload","package":"vim-addon-rdebug-0.0.zip","4":"vim-addon-rdebug-0.0.zip","src_id":"17793","5":"17793","creation_date":"1334839052","6":"1334839052"}]},"4023":{"script_id":"4023","0":"4023","script_name":"autolink","1":"autolink","script_type":"utility","2":"utility","summary":"find and insert URLs for links in Markdown and ReST","3":"find and insert URLs for links in Markdown and ReST","description":"This vim plugin automatically finds and inserts URLs for links in Markdown and\r\nReST documents.\r\n\r\n## Search for URLs\r\n\r\nautolink.vim uses the [Blekko][] search engine API to find URLs matching the\r\nlink IDs in [Markdown][] and [reStructuredText][] reference-style links. It\r\nautomatically inserts the first link found.\r\n\r\n[Markdown]: http:\/\/daringfireball.net\/projects\/markdown\/\r\n[reStructuredText]: http:\/\/docutils.sourceforge.net\/rst.html\r\n[Blekko]: http:\/\/blekko.com\/\r\n\r\nFor example, say you have this document:\r\n\r\n    I think [Markdown][] is really great.\r\n\r\n    [Markdown]: need a URL for this\r\n\r\nWith your cursor on the last line, you can type ``<leader>ac`` (for\r\n*auto-complete* link) and the last line will become:\r\n\r\n    [Markdown]: http:\/\/daringfireball.net\/projects\/markdown\/\r\n\r\nBehind the scenes, the plugin searches on Blekko for the word \"Markdown\" and\r\ninserts the first result's URL, a reasonable guess for a relevant link on the\r\nsubject, in the appropriate place. This also works in ReST documents on\r\nhyperlink target lines like `.. _Markdown: link goes here`.\r\n\r\n## Create Link Definitions\r\n\r\nThis plugin can help you insert the markup for reference-style links. For\r\nexample, suppose you have just typed this paragraph:\r\n\r\n    I prefer the [vim text editor][vim].\r\n\r\nType ``<leader>am`` (for *auto-make* link) to add a definition for the link\r\nbelow the current paragraph:\r\n\r\n    I prefer the [vim text editor][vim].\r\n\r\n    [vim]: \r\n\r\nThis also works in ReST for reference-style links like `` `foo`_``.\r\n\r\nThe plugin is careful to insert newlines between text paragraphs and blocks of\r\nlink references to make your document look nice.\r\n\r\n## All Together Now\r\n\r\nTo insert and complete a link definition in one fell swoop, use ``<leader>al``\r\n(for *auto-link*, the name of this plugin). This will add a reference to your\r\nlink after the current paragraph, fill it out with a search result, and then\r\njump back to your current cursor position to let you keep writing. (If your leader is `\\`, then it's like typing ``mq\\am\\ac`q``.)\r\n","4":"This vim plugin automatically finds and inserts URLs for links in Markdown and\r\nReST documents.\r\n\r\n## Search for URLs\r\n\r\nautolink.vim uses the [Blekko][] search engine API to find URLs matching the\r\nlink IDs in [Markdown][] and [reStructuredText][] reference-style links. It\r\nautomatically inserts the first link found.\r\n\r\n[Markdown]: http:\/\/daringfireball.net\/projects\/markdown\/\r\n[reStructuredText]: http:\/\/docutils.sourceforge.net\/rst.html\r\n[Blekko]: http:\/\/blekko.com\/\r\n\r\nFor example, say you have this document:\r\n\r\n    I think [Markdown][] is really great.\r\n\r\n    [Markdown]: need a URL for this\r\n\r\nWith your cursor on the last line, you can type ``<leader>ac`` (for\r\n*auto-complete* link) and the last line will become:\r\n\r\n    [Markdown]: http:\/\/daringfireball.net\/projects\/markdown\/\r\n\r\nBehind the scenes, the plugin searches on Blekko for the word \"Markdown\" and\r\ninserts the first result's URL, a reasonable guess for a relevant link on the\r\nsubject, in the appropriate place. This also works in ReST documents on\r\nhyperlink target lines like `.. _Markdown: link goes here`.\r\n\r\n## Create Link Definitions\r\n\r\nThis plugin can help you insert the markup for reference-style links. For\r\nexample, suppose you have just typed this paragraph:\r\n\r\n    I prefer the [vim text editor][vim].\r\n\r\nType ``<leader>am`` (for *auto-make* link) to add a definition for the link\r\nbelow the current paragraph:\r\n\r\n    I prefer the [vim text editor][vim].\r\n\r\n    [vim]: \r\n\r\nThis also works in ReST for reference-style links like `` `foo`_``.\r\n\r\nThe plugin is careful to insert newlines between text paragraphs and blocks of\r\nlink references to make your document look nice.\r\n\r\n## All Together Now\r\n\r\nTo insert and complete a link definition in one fell swoop, use ``<leader>al``\r\n(for *auto-link*, the name of this plugin). This will add a reference to your\r\nlink after the current paragraph, fill it out with a search result, and then\r\njump back to your current cursor position to let you keep writing. (If your leader is `\\`, then it's like typing ``mq\\am\\ac`q``.)\r\n","install_details":"Clone from GitHub into your pathogen bundles directory:\r\ngit clone git:\/\/github.com\/sampsyo\/autolink.vim.git","5":"Clone from GitHub into your pathogen bundles directory:\r\ngit clone git:\/\/github.com\/sampsyo\/autolink.vim.git","first_name":"Adrian","6":"Adrian","last_name":"Sampson","7":"Sampson","releases":[{"0":"4023","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"autolink.tar.gz","4":"autolink.tar.gz","src_id":"17790","5":"17790","creation_date":"1334775448","6":"1334775448"}]},"4022":{"script_id":"4022","0":"4022","script_name":"SpaceBetween","1":"SpaceBetween","script_type":"utility","2":"utility","summary":"This plugin fix spaces between = { } in your *.rb file before save it automat","3":"This plugin fix spaces between = { } in your *.rb file before save it automat","description":"https:\/\/github.com\/gagoar\/SpaceBetween\r\nSpace Between\r\nThis plugin fix spaces between = [ ]{ } in your *.rb file before save it automatically\r\n\r\n\r\n\r\nif you need call this function before save, you can call it manually doing:\r\n\r\n:SpaceBetween","4":"https:\/\/github.com\/gagoar\/SpaceBetween\r\nSpace Between\r\nThis plugin fix spaces between = [ ]{ } in your *.rb file before save it automatically\r\n\r\n\r\n\r\nif you need call this function before save, you can call it manually doing:\r\n\r\n:SpaceBetween","install_details":"Simple to use too: just put this files under plugin in to your vim configuration, if you are using janus , put it under ~\/.janus like this:\r\n\r\ngit clone git@github.com:gagoar\/SpaceBetween.git\r\nthen all you need to do is restart your vim\/mvim","5":"Simple to use too: just put this files under plugin in to your vim configuration, if you are using janus , put it under ~\/.janus like this:\r\n\r\ngit clone git@github.com:gagoar\/SpaceBetween.git\r\nthen all you need to do is restart your vim\/mvim","first_name":"German","6":"German","last_name":"Frigerio","7":"Frigerio","releases":[{"0":"4022","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"SpaceBetween.vim","4":"SpaceBetween.vim","src_id":"17789","5":"17789","creation_date":"1334753566","6":"1334753566"}]},"4021":{"script_id":"4021","0":"4021","script_name":"restore_view.vim","1":"restore_view.vim","script_type":"utility","2":"utility","summary":"A plugin for automatically restoring file's cursor position and folding","3":"A plugin for automatically restoring file's cursor position and folding","description":"This is plugin for automatically restore one file's cursor position and folding information after restart vim.\r\n\r\nThis is a simple script to autosave cursor position and fold\r\ninformation using vim\\\\\\'s mkview.  Although you can easily do this job by\r\njust add serveral line to {.,_}vimrc, write a script plugin can make it\r\nmore clean and nice.  We assume you use a new enough vim to enjoy\r\nthese feature. Hope you love it:)\r\n                                                                        \r\nViews are only be saved when you save\/write a file or EXIT VIM.\r\n     \r\nSuggested Setting:\r\nPlease put them in you vimrc:\r\nset viewoptions=cursor,folds,slash,unix\r\n\" let g:skipview_files = ['*\\.vim']\r\n                                                                   \r\nSet it in a plugin file looks dirty to me.  So you\\\\\\'d better do it your\r\nself.  This only keywords not in viewoptions is \\\\\\\"options\\\\\\\". I believe it\r\ndoes not belong to a view.  If you think you need it, feel free to\r\nput it in.  If you do not want views of some files to be saved, please\r\nset g:loaded_restore_view. The longer time you use, the bigger view\r\nfolder you will have.  So if you use UNIX environment, you may need to\r\nuse cron to do some clean job.\r\n","4":"This is plugin for automatically restore one file's cursor position and folding information after restart vim.\r\n\r\nThis is a simple script to autosave cursor position and fold\r\ninformation using vim\\\\\\'s mkview.  Although you can easily do this job by\r\njust add serveral line to {.,_}vimrc, write a script plugin can make it\r\nmore clean and nice.  We assume you use a new enough vim to enjoy\r\nthese feature. Hope you love it:)\r\n                                                                        \r\nViews are only be saved when you save\/write a file or EXIT VIM.\r\n     \r\nSuggested Setting:\r\nPlease put them in you vimrc:\r\nset viewoptions=cursor,folds,slash,unix\r\n\" let g:skipview_files = ['*\\.vim']\r\n                                                                   \r\nSet it in a plugin file looks dirty to me.  So you\\\\\\'d better do it your\r\nself.  This only keywords not in viewoptions is \\\\\\\"options\\\\\\\". I believe it\r\ndoes not belong to a view.  If you think you need it, feel free to\r\nput it in.  If you do not want views of some files to be saved, please\r\nset g:loaded_restore_view. The longer time you use, the bigger view\r\nfolder you will have.  So if you use UNIX environment, you may need to\r\nuse cron to do some clean job.\r\n","install_details":"","5":"","first_name":"Yichao","6":"Yichao","last_name":"Zhou","7":"Zhou","releases":[{"0":"4021","vim_version":"7.0","1":"7.0","script_version":"1.3","2":"1.3","version_comment":"Disable mkview and load view when 'diff' is enabled.\r\n\r\nThanks Enno Nagel for the discussion and suggestion.","3":"Disable mkview and load view when 'diff' is enabled.\r\n\r\nThanks Enno Nagel for the discussion and suggestion.","package":"restore_view.vim","4":"restore_view.vim","src_id":"22634","5":"22634","creation_date":"1416494361","6":"1416494361"},{"0":"4021","vim_version":"7.0","1":"7.0","script_version":"1.2","2":"1.2","version_comment":"Modify the check function.  Silent both mkview and loadview.  Stop saving view when leaving buffer.\r\n\r\nThanks Enno Nagel for the discussion and suggestion.","3":"Modify the check function.  Silent both mkview and loadview.  Stop saving view when leaving buffer.\r\n\r\nThanks Enno Nagel for the discussion and suggestion.","package":"restore_view.vim","4":"restore_view.vim","src_id":"22255","5":"22255","creation_date":"1406119471","6":"1406119471"},{"0":"4021","vim_version":"7.0","1":"7.0","script_version":"1.1","2":"1.1","version_comment":"Now g:skipview_files can be regular expression.","3":"Now g:skipview_files can be regular expression.","package":"restore_view.vim","4":"restore_view.vim","src_id":"17787","5":"17787","creation_date":"1334729199","6":"1334729199"},{"0":"4021","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"restore_view.vim","4":"restore_view.vim","src_id":"17786","5":"17786","creation_date":"1334726924","6":"1334726924"}]},"4020":{"script_id":"4020","0":"4020","script_name":"flipwords.vim","1":"flipwords.vim","script_type":"utility","2":"utility","summary":"Provides the command Flip that changes the order of two delimited words","3":"Provides the command Flip that changes the order of two delimited words","description":"Flipwords\r\n\r\nThe plugin Flipwords provides the command Flip that changes the order of two delimited words on a single line.\r\n\r\nExamples\r\n\r\n    Flip\t- flip two white-space delimited words\r\n    Flip ,\t- flip two items in a comma-delimited list \r\n    Flip , )\t- flip last two parameters (nested parens are not handled)\r\n    Flip = ;\t- flip two words delimited by '=' and ';' (c assignment)\r\n    Flip = )\\zs\t- flip two words delimited by '=' where the second word ends with and includes ')'\r\n\r\nSome effects of the Flip command (the coursor is at the character following '|'):\r\n\r\n    ~~ let |b = a\r\n    :Flip =\r\n    ~~ let |a = b\r\n\r\n    ~~ call doThis(|\"one\", \"two\", \"three\")\r\n    :Flip ,\r\n    ~~ call doThis(|\"two\", \"one\", \"three\")\r\n\r\n    ~~ call doThis(\"one\", |\"two\", \"three\")\r\n    :Flip ,\r\n    ~~ call doThis(\"one\", |\"three\"), \"two\"\r\n\r\n    ~~ call doThis(\"one\", |\"two\", \"three\")\r\n    :Flip , )\r\n    ~~ call doThis(\"one\", |\"three\", \"two\")\r\n\r\n    ~~ if |result == getValue() \" some comment\r\n    :Flip == )\\zs\r\n    ~~ if |getValue() == result \" some comment\r\n\r\nRepository: https:\/\/github.com\/mmahnic\/vim-flipwords\r\nSimilar plugin: vimscript #2843 (FlipLR)","4":"Flipwords\r\n\r\nThe plugin Flipwords provides the command Flip that changes the order of two delimited words on a single line.\r\n\r\nExamples\r\n\r\n    Flip\t- flip two white-space delimited words\r\n    Flip ,\t- flip two items in a comma-delimited list \r\n    Flip , )\t- flip last two parameters (nested parens are not handled)\r\n    Flip = ;\t- flip two words delimited by '=' and ';' (c assignment)\r\n    Flip = )\\zs\t- flip two words delimited by '=' where the second word ends with and includes ')'\r\n\r\nSome effects of the Flip command (the coursor is at the character following '|'):\r\n\r\n    ~~ let |b = a\r\n    :Flip =\r\n    ~~ let |a = b\r\n\r\n    ~~ call doThis(|\"one\", \"two\", \"three\")\r\n    :Flip ,\r\n    ~~ call doThis(|\"two\", \"one\", \"three\")\r\n\r\n    ~~ call doThis(\"one\", |\"two\", \"three\")\r\n    :Flip ,\r\n    ~~ call doThis(\"one\", |\"three\"), \"two\"\r\n\r\n    ~~ call doThis(\"one\", |\"two\", \"three\")\r\n    :Flip , )\r\n    ~~ call doThis(\"one\", |\"three\", \"two\")\r\n\r\n    ~~ if |result == getValue() \" some comment\r\n    :Flip == )\\zs\r\n    ~~ if |getValue() == result \" some comment\r\n\r\nRepository: https:\/\/github.com\/mmahnic\/vim-flipwords\r\nSimilar plugin: vimscript #2843 (FlipLR)","install_details":"Unpack into Vim runtime directory (eg. ~\/.vim\/) or use pathogen.","5":"Unpack into Vim runtime directory (eg. ~\/.vim\/) or use pathogen.","first_name":"Marko","6":"Marko","last_name":"Mahni\u010d","7":"Mahnič","releases":[{"0":"4020","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"flipwords-0.1.zip","4":"flipwords-0.1.zip","src_id":"17783","5":"17783","creation_date":"1334654189","6":"1334654189"}]},"4019":{"script_id":"4019","0":"4019","script_name":"WebAPI.vim","1":"WebAPI.vim","script_type":"utility","2":"utility","summary":"vimscript for gist","3":"vimscript for gist","description":"Interface to Web APIs\n\nwebapi-vim include:\n\n* XML parser Library.\n* HTML parser Library.\n* JSON parser Library.\n* HTTP client.\n\nand some utility functions.\n","4":"Interface to Web APIs\n\nwebapi-vim include:\n\n* XML parser Library.\n* HTML parser Library.\n* JSON parser Library.\n* HTTP client.\n\nand some utility functions.\n","install_details":"copy it to your plugin directory.\n","5":"copy it to your plugin directory.\n","first_name":"Yasuhiro","6":"Yasuhiro","last_name":"Matsumoto","7":"Matsumoto","releases":[{"0":"4019","vim_version":"7.0","1":"7.0","script_version":"0.3","2":"0.3","version_comment":"Bug fixes.\n","3":"Bug fixes.\n","package":"webapi-vim.zip","4":"webapi-vim.zip","src_id":"22542","5":"22542","creation_date":"1413685732","6":"1413685732"},{"0":"4019","vim_version":"7.0","1":"7.0","script_version":"0.2","2":"0.2","version_comment":"Bug fixes.\n","3":"Bug fixes.\n","package":"webapi-vim.zip","4":"webapi-vim.zip","src_id":"19175","5":"19175","creation_date":"1355358311","6":"1355358311"},{"0":"4019","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"webapi-vim.zip","4":"webapi-vim.zip","src_id":"17780","5":"17780","creation_date":"1334506208","6":"1334506208"}]},"4018":{"script_id":"4018","0":"4018","script_name":"clean_imports","1":"clean_imports","script_type":"utility","2":"utility","summary":"Makes use of the Java checkstyle tool to clean your Java file of unused imports","3":"Makes use of the Java checkstyle tool to clean your Java file of unused imports","description":"This is a simple bash script that can be used as a filter in vim to clean your java of unused imports.\r\n\r\nIf you have the JavaImp plugin installed (vimscript #325) you can use it in conjunction with this to also sort your imports as well as clean them.\r\n\r\nI have been using it in my own code and it works quite nicely.  See http:\/\/paulbourke.blogspot.com\/2012\/04\/clean-your-java-imports-in-vim.html for more info.","4":"This is a simple bash script that can be used as a filter in vim to clean your java of unused imports.\r\n\r\nIf you have the JavaImp plugin installed (vimscript #325) you can use it in conjunction with this to also sort your imports as well as clean them.\r\n\r\nI have been using it in my own code and it works quite nicely.  See http:\/\/paulbourke.blogspot.com\/2012\/04\/clean-your-java-imports-in-vim.html for more info.","install_details":"Save the script somewhere in your path such as ~\/bin and then add something like the following to your .vimrc\r\n\r\n\" F7 to call clean redundant Java imports and sort them\r\nfunction JavaImpClean()\r\n    %!~\/bin\/clean_imports.sh %\r\n    :JavaImpSort\r\nendfunction\r\n:command JavaImpClean exec JavaImpClean()\r\n:nnoremap <F7> :JavaImpClean<CR>","5":"Save the script somewhere in your path such as ~\/bin and then add something like the following to your .vimrc\r\n\r\n\" F7 to call clean redundant Java imports and sort them\r\nfunction JavaImpClean()\r\n    %!~\/bin\/clean_imports.sh %\r\n    :JavaImpSort\r\nendfunction\r\n:command JavaImpClean exec JavaImpClean()\r\n:nnoremap <F7> :JavaImpClean<CR>","first_name":"Paul","6":"Paul","last_name":"Bourke","7":"Bourke","releases":[{"0":"4018","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"clean_imports.sh","4":"clean_imports.sh","src_id":"17776","5":"17776","creation_date":"1334489826","6":"1334489826"}]},"4017":{"script_id":"4017","0":"4017","script_name":"vim-jsbeautify","1":"vim-jsbeautify","script_type":"utility","2":"utility","summary":"Simple javascript formater base on js-beautify","3":"Simple javascript formater base on js-beautify","description":"vim-jsbeautify.vim\r\n============\r\n\r\nLINK ON GITHUB: https:\/\/github.com\/maksimr\/vim-jsbeautify\r\n\r\n## About\r\n\r\nVim plugin based on js-beautify\r\n\r\nFor more info, online demo and tests see [http:\/\/jsbeautifier.org\/](online javascript beautifier)\r\n\r\nInstallation\r\n------------\r\n\r\n\r\n### With Pathogen\r\n\r\n```\r\ncd ~\/.vim\/bundle\r\ngit clone https:\/\/github.com\/maksimr\/vim-jsbeautify.git\r\ncd vim-jsbeautify && git submodule foreach git pull\r\n```\r\n\r\n### With Vundle\r\nAdd this to .vimrc:\r\n\r\n```vim\r\n\r\n  Bundle 'maksimr\/vim-jsbeautify'\r\n\r\n  \" and go to plugin direcotory and run git submodule foreach git pull\r\n\r\n```\r\nor (recomended)\r\n\r\n```vim\r\n\r\n  Bundle 'maksimr\/vim-jsbeautify'\r\n  Bundle 'einars\/js-beautify'\r\n\r\n  \" set path to js-beautify file\r\n  let g:jsbeautify_file = fnameescape(fnamemodify(expand(\"<sfile>\"), \":h\").\"\/bundle\/js-beautify\/beautify.js\")\r\n\r\n```\r\n\r\nConfiguration\r\n-------------\r\n\r\nConfiguration jsbeautify\r\n\r\n```vim\r\n  \".vimrc\r\n\r\n  let g:jsbeautify = {\"indent_size\": 4, \"indent_char\": \"\\t\"}\r\n\r\n```\r\n\r\nRun on v8\r\n\r\n```vim\r\n  \".vimrc\r\n\r\n  \" by default\r\n  let g:jsbeautify_engine = \"node\"\r\n\r\n  \" If you bin name for node is nodejs\r\n  let g:jsbeautify_engine = \"nodejs\"\r\n\r\n  let g:jsbeautify_engine = \"v8\"\r\n\r\n  \" or if you have other alias\r\n  let g:jsbeautify_engine = \"v8-alias\"\r\n\r\n```\r\n\r\nUsage\r\n\r\n```vim\r\n  \".vimrc\r\n\r\n  map <c-f> :call JsBeautify()<cr>\r\n\r\n```\r\n\r\nFunction JsBeautify takes two parameters. First `start line` second `end line`,\r\nby default `start line` equal '0' and `end line` equal '$'\r\n\r\n(version: 0.1)\r\n","4":"vim-jsbeautify.vim\r\n============\r\n\r\nLINK ON GITHUB: https:\/\/github.com\/maksimr\/vim-jsbeautify\r\n\r\n## About\r\n\r\nVim plugin based on js-beautify\r\n\r\nFor more info, online demo and tests see [http:\/\/jsbeautifier.org\/](online javascript beautifier)\r\n\r\nInstallation\r\n------------\r\n\r\n\r\n### With Pathogen\r\n\r\n```\r\ncd ~\/.vim\/bundle\r\ngit clone https:\/\/github.com\/maksimr\/vim-jsbeautify.git\r\ncd vim-jsbeautify && git submodule foreach git pull\r\n```\r\n\r\n### With Vundle\r\nAdd this to .vimrc:\r\n\r\n```vim\r\n\r\n  Bundle 'maksimr\/vim-jsbeautify'\r\n\r\n  \" and go to plugin direcotory and run git submodule foreach git pull\r\n\r\n```\r\nor (recomended)\r\n\r\n```vim\r\n\r\n  Bundle 'maksimr\/vim-jsbeautify'\r\n  Bundle 'einars\/js-beautify'\r\n\r\n  \" set path to js-beautify file\r\n  let g:jsbeautify_file = fnameescape(fnamemodify(expand(\"<sfile>\"), \":h\").\"\/bundle\/js-beautify\/beautify.js\")\r\n\r\n```\r\n\r\nConfiguration\r\n-------------\r\n\r\nConfiguration jsbeautify\r\n\r\n```vim\r\n  \".vimrc\r\n\r\n  let g:jsbeautify = {\"indent_size\": 4, \"indent_char\": \"\\t\"}\r\n\r\n```\r\n\r\nRun on v8\r\n\r\n```vim\r\n  \".vimrc\r\n\r\n  \" by default\r\n  let g:jsbeautify_engine = \"node\"\r\n\r\n  \" If you bin name for node is nodejs\r\n  let g:jsbeautify_engine = \"nodejs\"\r\n\r\n  let g:jsbeautify_engine = \"v8\"\r\n\r\n  \" or if you have other alias\r\n  let g:jsbeautify_engine = \"v8-alias\"\r\n\r\n```\r\n\r\nUsage\r\n\r\n```vim\r\n  \".vimrc\r\n\r\n  map <c-f> :call JsBeautify()<cr>\r\n\r\n```\r\n\r\nFunction JsBeautify takes two parameters. First `start line` second `end line`,\r\nby default `start line` equal '0' and `end line` equal '$'\r\n\r\n(version: 0.1)\r\n","install_details":"","5":"","first_name":"Maksim","6":"Maksim","last_name":"Ryzhikov","7":"Ryzhikov","releases":[{"0":"4017","vim_version":"7.3","1":"7.3","script_version":"0.1.1","2":"0.1.1","version_comment":"Fix shell escape","3":"Fix shell escape","package":"vim-jsbeautify.zip","4":"vim-jsbeautify.zip","src_id":"17801","5":"17801","creation_date":"1334948108","6":"1334948108"},{"0":"4017","vim_version":"7.3","1":"7.3","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"vim-jsbeautify.zip","4":"vim-jsbeautify.zip","src_id":"17771","5":"17771","creation_date":"1334397213","6":"1334397213"}]},"4016":{"script_id":"4016","0":"4016","script_name":"StripWhiteSpaces","1":"StripWhiteSpaces","script_type":"utility","2":"utility","summary":"Strip White Space on save file","3":"Strip White Space on save file","description":"https:\/\/github.com\/gagoar\/StripWhiteSpaces\r\n\r\nThis plugin strip all the white spaces in your file before save it automatically\r\n","4":"https:\/\/github.com\/gagoar\/StripWhiteSpaces\r\n\r\nThis plugin strip all the white spaces in your file before save it automatically\r\n","install_details":"Simple to use too: just put this files under plugin in to your vim configuration, if you are using janus, put it under ~\/.janus like this:\r\n\r\ngit clone git@github.com:gagoar\/StripWhiteSpaces.git\r\nthen all you need to do is restart your vim\/mvim\r\n\r\nif you need call this function before save, you can call it manually doing:\r\n\r\n:StripWhiteSpaces\r\n","5":"Simple to use too: just put this files under plugin in to your vim configuration, if you are using janus, put it under ~\/.janus like this:\r\n\r\ngit clone git@github.com:gagoar\/StripWhiteSpaces.git\r\nthen all you need to do is restart your vim\/mvim\r\n\r\nif you need call this function before save, you can call it manually doing:\r\n\r\n:StripWhiteSpaces\r\n","first_name":"German","6":"German","last_name":"Frigerio","7":"Frigerio","releases":[{"0":"4016","vim_version":"7.0","1":"7.0","script_version":"1.2","2":"1.2","version_comment":"disable  by demand.\r\nnew trailing line remover at the end of the file","3":"disable  by demand.\r\nnew trailing line remover at the end of the file","package":"StripWhiteSpaces.zip","4":"StripWhiteSpaces.zip","src_id":"22182","5":"22182","creation_date":"1405006126","6":"1405006126"},{"0":"4016","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"StripWhiteSpaces.vim","4":"StripWhiteSpaces.vim","src_id":"17770","5":"17770","creation_date":"1334384685","6":"1334384685"}]},"4015":{"script_id":"4015","0":"4015","script_name":"close-duplicate-tabs","1":"close-duplicate-tabs","script_type":"utility","2":"utility","summary":"A plugin for closing duplicate tab pages.","3":"A plugin for closing duplicate tab pages.","description":"When using tab pages, this plugin can help you close tabs\r\nwith the same file that might have accidentaly opened while\r\neditting in a rush.\r\n\r\nThe source is at:\r\n\r\nhttps:\/\/github.com\/sorribas\/vim-close-duplicate-tabs","4":"When using tab pages, this plugin can help you close tabs\r\nwith the same file that might have accidentaly opened while\r\neditting in a rush.\r\n\r\nThe source is at:\r\n\r\nhttps:\/\/github.com\/sorribas\/vim-close-duplicate-tabs","install_details":"Unzip the archive on your .vim directory.","5":"Unzip the archive on your .vim directory.","first_name":"Eduardo","6":"Eduardo","last_name":"Sorribas","7":"Sorribas","releases":[{"0":"4015","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"close-duplicate-tabs-v0.1.zip","4":"close-duplicate-tabs-v0.1.zip","src_id":"17767","5":"17767","creation_date":"1334327134","6":"1334327134"}]},"4014":{"script_id":"4014","0":"4014","script_name":"Vitality","1":"Vitality","script_type":"utility","2":"utility","summary":"Make Vim play nicely with iTerm 2 and tmux.","3":"Make Vim play nicely with iTerm 2 and tmux.","description":"Vitality makes Vim play nicely with iTerm 2 and tmux.\r\n\r\nFor example: it restores the FocusGained and FocusLost autocommands when running Vim in iTerm 2, even through tmux!\r\n\r\nFor more information: https:\/\/github.com\/sjl\/vitality.vim","4":"Vitality makes Vim play nicely with iTerm 2 and tmux.\r\n\r\nFor example: it restores the FocusGained and FocusLost autocommands when running Vim in iTerm 2, even through tmux!\r\n\r\nFor more information: https:\/\/github.com\/sjl\/vitality.vim","install_details":"Use Pathogen.","5":"Use Pathogen.","first_name":"Steve","6":"Steve","last_name":"Losh","7":"Losh","releases":[{"0":"4014","vim_version":"7.3","1":"7.3","script_version":"2.1.0","2":"2.1.0","version_comment":"* Add vitality_normal_cursor and vitality_insert_cursor to allow configuring more cursor types (thanks lnikkila).\r\n* Preserve existing terminal codes the user has set (thanks aaronjensen).\r\n* Don't spew errors on FocusGained if no autocommands are defined (thanks xsimov).\r\n","3":"* Add vitality_normal_cursor and vitality_insert_cursor to allow configuring more cursor types (thanks lnikkila).\r\n* Preserve existing terminal codes the user has set (thanks aaronjensen).\r\n* Don't spew errors on FocusGained if no autocommands are defined (thanks xsimov).\r\n","package":"vitality.zip","4":"vitality.zip","src_id":"24761","5":"24761","creation_date":"1479907553","6":"1479907553"},{"0":"4014","vim_version":"7.2","1":"7.2","script_version":"1.1.0","2":"1.1.0","version_comment":"* Handle focus events in command line mode (thanks aaronjensen).\r\n* Make features configurable (thanks dmedvinsky).","3":"* Handle focus events in command line mode (thanks aaronjensen).\r\n* Make features configurable (thanks dmedvinsky).","package":"vitality.zip","4":"vitality.zip","src_id":"17781","5":"17781","creation_date":"1334508747","6":"1334508747"},{"0":"4014","vim_version":"7.0","1":"7.0","script_version":"1.0.0","2":"1.0.0","version_comment":"Initial upload","3":"Initial upload","package":"vitality.zip","4":"vitality.zip","src_id":"17765","5":"17765","creation_date":"1334274690","6":"1334274690"}]},"4013":{"script_id":"4013","0":"4013","script_name":"readnovel","1":"readnovel","script_type":"utility","2":"utility","summary":"看中文txt小说插件","3":"看中文txt小说插件","description":"只适用gvim和txt文件,本文件放到plugin目录\r\nF5 读取字体等设置（默认保存在.vim\/read_novel_config.vim）\r\nF6 保存字体窗口大小等设置\r\nF7 截断长行（略耗时）必须先设置好字体和窗口再作这一步\r\nF8 自动滚屏（按Ctrl-C中止）\r\nF9 开始测试读文速度，读完一屏后按空格翻页，不要使用jk或鼠标翻页\r\nF10 停止测试（一般需要读文7-8页较为准确，停止后按F6保存测试结果）\r\n\r\n使用方法：\r\n第一次使用：用gvim打开txt小说，调整读小说所用的字体和窗口大小，设置好颜色，按F6保存\r\n看新的小说：用gvim打开新小说，按F5，再按F7\r\n看小说：用gvim打开txt小说，按F5,再按F8\r\n调整阅读速度：用gvim打开已断行的小说，按F5,按F9开始看小说，期间按空格或pgdn翻页，不受打扰的看10页以后按F10结束，再按F6保存","4":"只适用gvim和txt文件,本文件放到plugin目录\r\nF5 读取字体等设置（默认保存在.vim\/read_novel_config.vim）\r\nF6 保存字体窗口大小等设置\r\nF7 截断长行（略耗时）必须先设置好字体和窗口再作这一步\r\nF8 自动滚屏（按Ctrl-C中止）\r\nF9 开始测试读文速度，读完一屏后按空格翻页，不要使用jk或鼠标翻页\r\nF10 停止测试（一般需要读文7-8页较为准确，停止后按F6保存测试结果）\r\n\r\n使用方法：\r\n第一次使用：用gvim打开txt小说，调整读小说所用的字体和窗口大小，设置好颜色，按F6保存\r\n看新的小说：用gvim打开新小说，按F5，再按F7\r\n看小说：用gvim打开txt小说，按F5,再按F8\r\n调整阅读速度：用gvim打开已断行的小说，按F5,按F9开始看小说，期间按空格或pgdn翻页，不受打扰的看10页以后按F10结束，再按F6保存","install_details":"copy to plugin\/","5":"copy to plugin\/","first_name":"sunsol","6":"sunsol","last_name":"zn","7":"zn","releases":[{"0":"4013","vim_version":"7.0","1":"7.0","script_version":"0.2","2":"0.2","version_comment":"修正enc不是utf-8时无法正常执行的问题","3":"修正enc不是utf-8时无法正常执行的问题","package":"readnovel.vim","4":"readnovel.vim","src_id":"18041","5":"18041","creation_date":"1338093711","6":"1338093711"},{"0":"4013","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"readnovel.vim","4":"readnovel.vim","src_id":"17760","5":"17760","creation_date":"1334242363","6":"1334242363"}]},"4012":{"script_id":"4012","0":"4012","script_name":"Vimpy","1":"Vimpy","script_type":"utility","2":"utility","summary":"Write Vim scripts in Python. Not Vimscript.","3":"Write Vim scripts in Python. Not Vimscript.","description":"Simply put, Vimpy allows you to write Vim plugins without writing any\r\nVimscript. This is done by abstracting Vim commands through a Pythonic\r\ninterface.\r\n\r\nNOTE: This is pre-alpha softare. As much as it should work as documented, there\r\nis potential for issues to arrise. If they do, please create an issue\r\n(https:\/\/github.com\/LimpidTech\/Vimpy\/issues\/new) so that we can make this\r\nsoftware better. We welcome any feedback, suggestions, or complaints. Please\r\ndon't be shy!\r\n\r\nDocumentation\r\n-------------\r\n\r\nVimpy's documentation is available at the GitHub wiki page\r\n(https:\/\/github.com\/LimpidTech\/Vimpy\/wiki). If you run into any problems with\r\nthe documentation, or if you just have a recommendation on how to make it\r\nbetter - please don't hesitate to create a new issue\r\n(https:\/\/github.com\/LimpidTech\/Vimpy\/issues\/new). We expect that Vimpy might\r\nhave a couple issues, and will always want to make this library better in any\r\nway possible.\r\n\r\nQuick Start\r\n-----------\r\n\r\nThe quick start from this README document has been moved to the wiki. You can\r\nfind it here: https:\/\/github.com\/LimpidTech\/Vimpy\/wiki\/Quick-Start\r\n","4":"Simply put, Vimpy allows you to write Vim plugins without writing any\r\nVimscript. This is done by abstracting Vim commands through a Pythonic\r\ninterface.\r\n\r\nNOTE: This is pre-alpha softare. As much as it should work as documented, there\r\nis potential for issues to arrise. If they do, please create an issue\r\n(https:\/\/github.com\/LimpidTech\/Vimpy\/issues\/new) so that we can make this\r\nsoftware better. We welcome any feedback, suggestions, or complaints. Please\r\ndon't be shy!\r\n\r\nDocumentation\r\n-------------\r\n\r\nVimpy's documentation is available at the GitHub wiki page\r\n(https:\/\/github.com\/LimpidTech\/Vimpy\/wiki). If you run into any problems with\r\nthe documentation, or if you just have a recommendation on how to make it\r\nbetter - please don't hesitate to create a new issue\r\n(https:\/\/github.com\/LimpidTech\/Vimpy\/issues\/new). We expect that Vimpy might\r\nhave a couple issues, and will always want to make this library better in any\r\nway possible.\r\n\r\nQuick Start\r\n-----------\r\n\r\nThe quick start from this README document has been moved to the wiki. You can\r\nfind it here: https:\/\/github.com\/LimpidTech\/Vimpy\/wiki\/Quick-Start\r\n","install_details":"This script requires Pathogen, and requires that you have a version of vim compiled with +python.\r\n\r\nYou can check that your Vim is compatible on Unix systems with:\r\n\r\nvim --version | grep +python\r\n\r\nIf you don't get anything back, you'll need to rebuild Vim with a Python interpreter.","5":"This script requires Pathogen, and requires that you have a version of vim compiled with +python.\r\n\r\nYou can check that your Vim is compatible on Unix systems with:\r\n\r\nvim --version | grep +python\r\n\r\nIf you don't get anything back, you'll need to rebuild Vim with a Python interpreter.","first_name":"Brandon","6":"Brandon","last_name":"Stoner","7":"Stoner","releases":[{"0":"4012","vim_version":"7.0","1":"7.0","script_version":"0.2.0","2":"0.2.0","version_comment":"Version 0.2.0","3":"Version 0.2.0","package":"vimpy-master.zip","4":"vimpy-master.zip","src_id":"20464","5":"20464","creation_date":"1372645964","6":"1372645964"}]},"4011":{"script_id":"4011","0":"4011","script_name":"vimux","1":"vimux","script_type":"utility","2":"utility","summary":"effortless vim and tmux interaction","3":"effortless vim and tmux interaction","description":"The function RunVimTmuxCommand(command) is the core of Vimux. It will\r\ncreate a split pane in the current window and run the passed command in it.\r\n\r\n    :call RunVimTmuxCommand(\"ls\")\r\n\r\nThis will run the command in a split pane without losing focus of vim. If the\r\ncommand takes a long time to return you can continue to use vim while the\r\nprocess finishes and will see the output in the pane when it's finished. Check\r\nout http:\/\/github.com\/benmills\/vimux for more information and updates.","4":"The function RunVimTmuxCommand(command) is the core of Vimux. It will\r\ncreate a split pane in the current window and run the passed command in it.\r\n\r\n    :call RunVimTmuxCommand(\"ls\")\r\n\r\nThis will run the command in a split pane without losing focus of vim. If the\r\ncommand takes a long time to return you can continue to use vim while the\r\nprocess finishes and will see the output in the pane when it's finished. Check\r\nout http:\/\/github.com\/benmills\/vimux for more information and updates.","install_details":"Move plugin\/vimux.vim from the unachieved folder into ~\/.vim\/plugin\/ or if you use pathogen you can move the unachieved folder into ~\/.vim\/bundle.\r\n\r\nOnce you have the vimux installed as a vim plugin you should be able to start vim and run :PromptVimTmuxCommand. If vimux was installed correctly you should see Command? You can then type any command to be executed and watch vimux create a pane for you.","5":"Move plugin\/vimux.vim from the unachieved folder into ~\/.vim\/plugin\/ or if you use pathogen you can move the unachieved folder into ~\/.vim\/bundle.\r\n\r\nOnce you have the vimux installed as a vim plugin you should be able to start vim and run :PromptVimTmuxCommand. If vimux was installed correctly you should see Command? You can then type any command to be executed and watch vimux create a pane for you.","first_name":"ben","6":"ben","last_name":"mills","7":"mills","releases":[{"0":"4011","vim_version":"7.0","1":"7.0","script_version":"1.0.0","2":"1.0.0","version_comment":"* Remove ruby as a dependency","3":"* Remove ruby as a dependency","package":"vimux-1.0.0.zip","4":"vimux-1.0.0.zip","src_id":"20361","5":"20361","creation_date":"1371355385","6":"1371355385"},{"0":"4011","vim_version":"7.0","1":"7.0","script_version":"0.3.1","2":"0.3.1","version_comment":"* Bug fixes\r\n* Normalized API to `Vimux<command>`\r\n* Added new command to clear pane history","3":"* Bug fixes\r\n* Normalized API to `Vimux<command>`\r\n* Added new command to clear pane history","package":"benmills-vimux-0.3.1-0-gf476177.tar.gz","4":"benmills-vimux-0.3.1-0-gf476177.tar.gz","src_id":"18175","5":"18175","creation_date":"1340310463","6":"1340310463"},{"0":"4011","vim_version":"7.0","1":"7.0","script_version":"0.20","2":"0.20","version_comment":"Initial upload","3":"Initial upload","package":"vimux-0.2.0.tar","4":"vimux-0.2.0.tar","src_id":"17755","5":"17755","creation_date":"1334157243","6":"1334157243"}]},"4010":{"script_id":"4010","0":"4010","script_name":"Vim-Gromacs","1":"Vim-Gromacs","script_type":"syntax","2":"syntax","summary":"Plugin Vim to manipulate Gromacs files (syntax highlighting, macros)","3":"Plugin Vim to manipulate Gromacs files (syntax highlighting, macros)","description":"Vim-Gromacs is a plugin to easy manipulate Gromacs (http:\/\/www.gromacs.org\/) files in Vim.\r\n\r\nIt contains a set of files to enable syntax highlighting for Gromacs files.\r\nIt works with mdp, gro, top\/itp, xvg and ndx files.\r\n\r\nIt contains also macros to comment\/uncomment easily selections of a file and to jump to different sections ([...]) of a file :\r\nShortcuts for the macros:\r\n]; -- Comment the selection\r\n]: -- Uncomment the selection\r\n], -- Jump to the next section\r\n]! -- Jump to the previous section\r\n\r\nA section is defined by '[....]'\r\n\r\nYou can follow it on GitHub: https:\/\/github.com\/HubLot\/vim-gromacs","4":"Vim-Gromacs is a plugin to easy manipulate Gromacs (http:\/\/www.gromacs.org\/) files in Vim.\r\n\r\nIt contains a set of files to enable syntax highlighting for Gromacs files.\r\nIt works with mdp, gro, top\/itp, xvg and ndx files.\r\n\r\nIt contains also macros to comment\/uncomment easily selections of a file and to jump to different sections ([...]) of a file :\r\nShortcuts for the macros:\r\n]; -- Comment the selection\r\n]: -- Uncomment the selection\r\n], -- Jump to the next section\r\n]! -- Jump to the previous section\r\n\r\nA section is defined by '[....]'\r\n\r\nYou can follow it on GitHub: https:\/\/github.com\/HubLot\/vim-gromacs","install_details":"1. Download the vimball (gromacs.vba) to any directory. \r\n2. Open the file in vim ($ vim gromacs.vba) \r\n3. Source the file (:so %)","5":"1. Download the vimball (gromacs.vba) to any directory. \r\n2. Open the file in vim ($ vim gromacs.vba) \r\n3. Source the file (:so %)","first_name":"hubert","6":"hubert","last_name":"santuz","7":"santuz","releases":[{"0":"4010","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"gromacs.vba","4":"gromacs.vba","src_id":"17750","5":"17750","creation_date":"1334072479","6":"1334072479"}]},"4009":{"script_id":"4009","0":"4009","script_name":"XDebug (DBGp) client (for PHP)","1":"XDebug (DBGp) client (for PHP)","script_type":"utility","2":"utility","summary":"minimal php debug client for XDebug (DBGp)","3":"minimal php debug client for XDebug (DBGp)","description":"This is a modification of vimscript #1929 (DBGp client for PHP, which in turn is based on vimscript#1152 - remote PHP debugger) to make it work on Windows too. See that script for a link to a (Linux) tutorial on using vim to debug php. Or just keep reading this page.\r\n\r\nYou can see the the link to the wiki page above for an introduction to the concept model involved in debugging php pages.\r\nA couple of screen-shots are available here: http:\/\/code.google.com\/p\/dbgp-client\/wiki\/screenshots\r\nA page with setup instructions is available at http:\/\/code.google.com\/p\/dbgp-client\/wiki\/setup\r\n\r\nWith this script you should be able to perform simple (minimal) debugging steps into a php web page or a php command line script (actually the php script may also be a GUI application, not necessarily command-line) Note that there are a number of DBGp clients out there with more features (see a list at http:\/\/xdebug.org\/docs\/remote), but you might want this script if you want to debug from Vim. You might also find vim scripts similar to this one (for example vimscript #3320, search Vim scripts for \"XDebug\" or \"php debug\" to find them) but I do not know how good they are or if they work on both Windows and Linux.\r\n\r\nNow to clarify: DBGp is the protocol for communication between a debug server (the debugger engine) and a debug client (the user interface with the opened source files and breakpoint markers on the proper lines). It is suited for remote debugging of your scripts, but it is the same mechanism used for debugging scripts locally also. The XDebug php extension is the debugger engine, that implements DBGp in php. This vim script is the debugger client that implements DBGp for Vim. Note that in this case the server initiates a new connection with the client, and not the other way around as one might expect.\r\n\r\nYou need to have XDebug extension installed and enabled in php (check the output of `php -m`), in order for php to work as a debug server and start a debugging session (see the XDebug documentation at http:\/\/xdebug.org\/docs\/). This script will only turn Vim into the debug client. You will need python2 installed (http:\/\/www.python.org\/download\/, not tested with python3) and Vim with +python and +signs features (most Vim distributions have them, see :version command). The default 'nopaste' option in Vim should be in effect, for expression evaluation in the debugger to work as expected. Some people like to copy\/paste text, like samples of code for example, and for this they like to set 'paste' option in Vim (also because Vim feels more Windows-compatible with it), but unfortunately that will disable insert-mode mappings, that are used by the plugin. You can just set 'nopaste' during debugging, and set 'paste' back on after if you want.\r\n\r\nTo debug web pages, you may want to install the XDebug extension for Firefox \/ Chrome \/ Safari \/ Opera (maybe others?), or else you will need to manually add an XDEBUG_SESSSION_START query parameter to the page URL in order to start the debug session (but to submit a form and debug the referred page using a manual URL parameter, you will need quite some extra work).\r\n\r\nWith the browser extension installed, you should:\r\n      1. Enable web page debugging from the browser with the toolbar button provided by the extension.\r\n          This will tell php to start a debugging session on the next page, and than open a connection to the debug client.\r\n      2. Press <F5> - Start\/Continue debugging (by default) in Vim. Vim will now wait for the new connection from the server.\r\n      3. Immediately reload or access the web page to be debugged (currently within 5 seconds since you start debugging in Vim).\r\n\r\nFor command line scripts, XDebug expects the XDEBUG_CONFIG environment variable to be set before php is invoked, in order to start a debugging session (and connect to the debug client). On a bash\/sh shell (including cygwin\/mingw if on Windows), the command line would look like:\r\n              XDEBUG_CONFIG=\"ide-key=vim\"    php     ..\/path\/to\/script-file.php   script-args....\r\nOn a plain cmd.exe console window on Windows you would need separate commands:\r\n              Set XDEBUG_CONFIG=ide-key=vim\r\n              php  ..\/path\/to\/script-file.php   script-args...\r\nAgain, you should press <F5> (by default) in Vim immediately before executing the above php command.\r\n\r\nIf you have some stubborn firewall, you should also make sure Vim is allowed to listen and receive connections on the debugging port (default 9000).\r\n\r\nYou might try the script with other debuggers than php, that implement the DBGp protocol (protocol specifications can be found on XDebug web site at http:\/\/xdebug.org\/docs-dbgp.php), but it has only been tested with php (that is, with XDebug). If you do, you may leave the script author a message about it.\r\n\r\nCurrently the script still has a few bugs, is missing a documentation file (but it will display a shortcuts window once debugging is started), and only supports simple debugging commands. Once a debugging session is started, you may evaluate php expressions, including function calls, with the ,e (a comma and the letter e) keyboard shortcut. Note that XDebug (DBGp) has a \"starting\" state when your script is not being debugged yet (is not started) but the debugging session is started (just use step in\/step over to enter your script), and a similar \"stopping\" state when your script has finished, but the debugging session is still active (for collecting certain statistics and other information, use <F6> - stop debugging to end the debugging session). The web browser will keep loading the page (will show the loading indicator) until you finish the debugging session.\r\n\r\nIn general different debuggers use different keys for debugging functions. This script will map by default almost all function keys F1 to F12 for debugging functions. However you most likely already have other mappings for some of these (or you may have plug-in scripts that have other mappings for some of these), so you should set the global option g:debuggerMapDefaultKeys in your ~\/.vimrc file to one of these values:\r\n     0 - disable default key mappings (use when you set your own mappings in ~\/.vimrc for the debugging functions, recommended)\r\n     1 - map  <F1> to <F12> keys\r\n     2 - map <M-F1>..<M-F12> In this case <M-F4> (or Alt+F4) is also mapped to <M-C-F4>\r\n     3 - map <S-F1>..<S-F12>\r\n     4 - map <C-F1>..<C-F12>\r\n     5 - map <M-C-F1..12>\r\n     6 - map <M-S-F1..12>\r\n     7 - map <C-S-F1..12>\r\n\r\nFor example to use Alt+Ctrl+F1 to Alt+Ctrl+F12 for debugging, write the following line in ~\/.vimrc (or ~\/_vimrc on Windows)\r\n     let g:debuggerMapDefaultKeys = 5\r\nOn Linux however the Alt+Ctrl+F1.. keys are used to switch virtual consoles. So beware that Vim may not be able to sense all of these key combinations on all systems, so you may need to try more than one set of them before you choose one. Also, if you change this option, note that the shortcuts window in the debugger will still display <F1>,...<F12> as the debugging keys...\r\n\r\nAnother known problem is that the script does not properly save\/restore Vim windows for multiple tabs before and after a debugging session (it tries to use the :mksession and :source commands for this purpose) and as such it is currently recommended that you start a new Vim instance before debugging, or to use a single tab in your (existing) vim session.\r\n\r\nIf you would like to submit patches or you have modifications to the script, you can send them to the author.\r\n\r\nTODO:\r\nWhen debugging files on a remote web server (not the local host) you can not currently open the source files being debugged, so this is not supported yet. One way around this problem is to use symlinks on your computer so that the file paths on the server match the file paths on the client. It is possible to modify the script so as to include a user mapping for remote files to local files (if you have an exact copy of the source files on the local computer) or to some other remote protocol (if you can open the remote files through FTP \/ HTTP \/ VPN \/ SSH \/ network shares...).\r\n\r\nThe project source code repository and issue tracker can be found at: http:\/\/code.google.com\/p\/dbgp-client\/\r\nYou are welcome to use the tracker there for suggestions or issues that you may have.","4":"This is a modification of vimscript #1929 (DBGp client for PHP, which in turn is based on vimscript#1152 - remote PHP debugger) to make it work on Windows too. See that script for a link to a (Linux) tutorial on using vim to debug php. Or just keep reading this page.\r\n\r\nYou can see the the link to the wiki page above for an introduction to the concept model involved in debugging php pages.\r\nA couple of screen-shots are available here: http:\/\/code.google.com\/p\/dbgp-client\/wiki\/screenshots\r\nA page with setup instructions is available at http:\/\/code.google.com\/p\/dbgp-client\/wiki\/setup\r\n\r\nWith this script you should be able to perform simple (minimal) debugging steps into a php web page or a php command line script (actually the php script may also be a GUI application, not necessarily command-line) Note that there are a number of DBGp clients out there with more features (see a list at http:\/\/xdebug.org\/docs\/remote), but you might want this script if you want to debug from Vim. You might also find vim scripts similar to this one (for example vimscript #3320, search Vim scripts for \"XDebug\" or \"php debug\" to find them) but I do not know how good they are or if they work on both Windows and Linux.\r\n\r\nNow to clarify: DBGp is the protocol for communication between a debug server (the debugger engine) and a debug client (the user interface with the opened source files and breakpoint markers on the proper lines). It is suited for remote debugging of your scripts, but it is the same mechanism used for debugging scripts locally also. The XDebug php extension is the debugger engine, that implements DBGp in php. This vim script is the debugger client that implements DBGp for Vim. Note that in this case the server initiates a new connection with the client, and not the other way around as one might expect.\r\n\r\nYou need to have XDebug extension installed and enabled in php (check the output of `php -m`), in order for php to work as a debug server and start a debugging session (see the XDebug documentation at http:\/\/xdebug.org\/docs\/). This script will only turn Vim into the debug client. You will need python2 installed (http:\/\/www.python.org\/download\/, not tested with python3) and Vim with +python and +signs features (most Vim distributions have them, see :version command). The default 'nopaste' option in Vim should be in effect, for expression evaluation in the debugger to work as expected. Some people like to copy\/paste text, like samples of code for example, and for this they like to set 'paste' option in Vim (also because Vim feels more Windows-compatible with it), but unfortunately that will disable insert-mode mappings, that are used by the plugin. You can just set 'nopaste' during debugging, and set 'paste' back on after if you want.\r\n\r\nTo debug web pages, you may want to install the XDebug extension for Firefox \/ Chrome \/ Safari \/ Opera (maybe others?), or else you will need to manually add an XDEBUG_SESSSION_START query parameter to the page URL in order to start the debug session (but to submit a form and debug the referred page using a manual URL parameter, you will need quite some extra work).\r\n\r\nWith the browser extension installed, you should:\r\n      1. Enable web page debugging from the browser with the toolbar button provided by the extension.\r\n          This will tell php to start a debugging session on the next page, and than open a connection to the debug client.\r\n      2. Press <F5> - Start\/Continue debugging (by default) in Vim. Vim will now wait for the new connection from the server.\r\n      3. Immediately reload or access the web page to be debugged (currently within 5 seconds since you start debugging in Vim).\r\n\r\nFor command line scripts, XDebug expects the XDEBUG_CONFIG environment variable to be set before php is invoked, in order to start a debugging session (and connect to the debug client). On a bash\/sh shell (including cygwin\/mingw if on Windows), the command line would look like:\r\n              XDEBUG_CONFIG=\"ide-key=vim\"    php     ..\/path\/to\/script-file.php   script-args....\r\nOn a plain cmd.exe console window on Windows you would need separate commands:\r\n              Set XDEBUG_CONFIG=ide-key=vim\r\n              php  ..\/path\/to\/script-file.php   script-args...\r\nAgain, you should press <F5> (by default) in Vim immediately before executing the above php command.\r\n\r\nIf you have some stubborn firewall, you should also make sure Vim is allowed to listen and receive connections on the debugging port (default 9000).\r\n\r\nYou might try the script with other debuggers than php, that implement the DBGp protocol (protocol specifications can be found on XDebug web site at http:\/\/xdebug.org\/docs-dbgp.php), but it has only been tested with php (that is, with XDebug). If you do, you may leave the script author a message about it.\r\n\r\nCurrently the script still has a few bugs, is missing a documentation file (but it will display a shortcuts window once debugging is started), and only supports simple debugging commands. Once a debugging session is started, you may evaluate php expressions, including function calls, with the ,e (a comma and the letter e) keyboard shortcut. Note that XDebug (DBGp) has a \"starting\" state when your script is not being debugged yet (is not started) but the debugging session is started (just use step in\/step over to enter your script), and a similar \"stopping\" state when your script has finished, but the debugging session is still active (for collecting certain statistics and other information, use <F6> - stop debugging to end the debugging session). The web browser will keep loading the page (will show the loading indicator) until you finish the debugging session.\r\n\r\nIn general different debuggers use different keys for debugging functions. This script will map by default almost all function keys F1 to F12 for debugging functions. However you most likely already have other mappings for some of these (or you may have plug-in scripts that have other mappings for some of these), so you should set the global option g:debuggerMapDefaultKeys in your ~\/.vimrc file to one of these values:\r\n     0 - disable default key mappings (use when you set your own mappings in ~\/.vimrc for the debugging functions, recommended)\r\n     1 - map  <F1> to <F12> keys\r\n     2 - map <M-F1>..<M-F12> In this case <M-F4> (or Alt+F4) is also mapped to <M-C-F4>\r\n     3 - map <S-F1>..<S-F12>\r\n     4 - map <C-F1>..<C-F12>\r\n     5 - map <M-C-F1..12>\r\n     6 - map <M-S-F1..12>\r\n     7 - map <C-S-F1..12>\r\n\r\nFor example to use Alt+Ctrl+F1 to Alt+Ctrl+F12 for debugging, write the following line in ~\/.vimrc (or ~\/_vimrc on Windows)\r\n     let g:debuggerMapDefaultKeys = 5\r\nOn Linux however the Alt+Ctrl+F1.. keys are used to switch virtual consoles. So beware that Vim may not be able to sense all of these key combinations on all systems, so you may need to try more than one set of them before you choose one. Also, if you change this option, note that the shortcuts window in the debugger will still display <F1>,...<F12> as the debugging keys...\r\n\r\nAnother known problem is that the script does not properly save\/restore Vim windows for multiple tabs before and after a debugging session (it tries to use the :mksession and :source commands for this purpose) and as such it is currently recommended that you start a new Vim instance before debugging, or to use a single tab in your (existing) vim session.\r\n\r\nIf you would like to submit patches or you have modifications to the script, you can send them to the author.\r\n\r\nTODO:\r\nWhen debugging files on a remote web server (not the local host) you can not currently open the source files being debugged, so this is not supported yet. One way around this problem is to use symlinks on your computer so that the file paths on the server match the file paths on the client. It is possible to modify the script so as to include a user mapping for remote files to local files (if you have an exact copy of the source files on the local computer) or to some other remote protocol (if you can open the remote files through FTP \/ HTTP \/ VPN \/ SSH \/ network shares...).\r\n\r\nThe project source code repository and issue tracker can be found at: http:\/\/code.google.com\/p\/dbgp-client\/\r\nYou are welcome to use the tracker there for suggestions or issues that you may have.","install_details":"Unpack the .zip archive into the directory:\r\n\r\n    %USERPROFILE%\\vimfiles                 (on Windows)\r\nor\r\n    $HOME\/.vim                                         (on Linux\/Unix\/...)\r\n\r\nThe %USERPROFILE% directory on Windows is usually:\r\n         C:\\Users\\_User_Name\r\n                 or\r\n         C:\\Documents and Settings\\_User_Name\\\r\n\r\nYou may also use the system plugin directory for vim on your system if you want to install for all users.\r\n\r\nThis will just install the two files debugger.vim and debugger.py (no documentation file included) and will directly map the <F5> key to start a debugging session (or continue running the debugged script), and also a few other keys for debugging (F2, F3, F4 - step into, step over, step out;  <F11> - get list of script variables in the current context).\r\n\r\nYou may wish to map <C-M-Up> and <C-M-Down> keys (Alt+Ctrl+Up-Arrow, Alt+Ctrl+Down-Arrorw) to the :Up and :Dn commands, to navigate the call stack of your php script with them. However the eval ,e command may only use variables from the innermost (nested) stack frame.\r\n\r\nAs mentioned above you need python2, php with XDebug extension, Vim with +python  and +signs features (and the default 'nopaste' option) and the browser extension (plug-in) for XDebug.","5":"Unpack the .zip archive into the directory:\r\n\r\n    %USERPROFILE%\\vimfiles                 (on Windows)\r\nor\r\n    $HOME\/.vim                                         (on Linux\/Unix\/...)\r\n\r\nThe %USERPROFILE% directory on Windows is usually:\r\n         C:\\Users\\_User_Name\r\n                 or\r\n         C:\\Documents and Settings\\_User_Name\\\r\n\r\nYou may also use the system plugin directory for vim on your system if you want to install for all users.\r\n\r\nThis will just install the two files debugger.vim and debugger.py (no documentation file included) and will directly map the <F5> key to start a debugging session (or continue running the debugged script), and also a few other keys for debugging (F2, F3, F4 - step into, step over, step out;  <F11> - get list of script variables in the current context).\r\n\r\nYou may wish to map <C-M-Up> and <C-M-Down> keys (Alt+Ctrl+Up-Arrow, Alt+Ctrl+Down-Arrorw) to the :Up and :Dn commands, to navigate the call stack of your php script with them. However the eval ,e command may only use variables from the innermost (nested) stack frame.\r\n\r\nAs mentioned above you need python2, php with XDebug extension, Vim with +python  and +signs features (and the default 'nopaste' option) and the browser extension (plug-in) for XDebug.","first_name":"Timothy","6":"Timothy","last_name":"Madden","7":"Madden","releases":[{"0":"4009","vim_version":"6.0","1":"6.0","script_version":"0.55","2":"0.55","version_comment":"Added option to disable\/change default key mappings","3":"Added option to disable\/change default key mappings","package":"debugger.zip","4":"debugger.zip","src_id":"17766","5":"17766","creation_date":"1334277422","6":"1334277422"},{"0":"4009","vim_version":"6.0","1":"6.0","script_version":"0.51","2":"0.51","version_comment":"Added a short status line message if python can not be loaded, since many new Windows users are likely not to have it.","3":"Added a short status line message if python can not be loaded, since many new Windows users are likely not to have it.","package":"debugger.zip","4":"debugger.zip","src_id":"17753","5":"17753","creation_date":"1334095410","6":"1334095410"},{"0":"4009","vim_version":"6.0","1":"6.0","script_version":"0.5","2":"0.5","version_comment":"Initial upload","3":"Initial upload","package":"debugger.zip","4":"debugger.zip","src_id":"17744","5":"17744","creation_date":"1333970660","6":"1333970660"}]},"4008":{"script_id":"4008","0":"4008","script_name":"youdao.dict","1":"youdao.dict","script_type":"utility","2":"utility","summary":"a translation tools use youdao dict","3":"a translation tools use youdao dict","description":"a translation tools use youdao dict\r\nit is good for chiness this inital version (i will do more later for all language)\r\nfor  google translation become Fee-based services and free services is hard to visit\r\n==========================\r\nthis version only support english word to chinese\r\n+++\r\nversion controller under github: https:\/\/howl-anderson@github.com\/howl-anderson\/youdao.dict.git\r\n\r\n\r\n","4":"a translation tools use youdao dict\r\nit is good for chiness this inital version (i will do more later for all language)\r\nfor  google translation become Fee-based services and free services is hard to visit\r\n==========================\r\nthis version only support english word to chinese\r\n+++\r\nversion controller under github: https:\/\/howl-anderson@github.com\/howl-anderson\/youdao.dict.git\r\n\r\n\r\n","install_details":"make sure you had install pyquery and python lxml\r\nget the plugin zip package unzip and put it to you .vim dir\r\nyou should map key like <code>map <F2> <ESC>:call Youdao()<cr><\/code> in your .vimrc file\r\nusage:set cursor on your english word and press the key you had map, translation will dispaly in your vim information area","5":"make sure you had install pyquery and python lxml\r\nget the plugin zip package unzip and put it to you .vim dir\r\nyou should map key like <code>map <F2> <ESC>:call Youdao()<cr><\/code> in your .vimrc file\r\nusage:set cursor on your english word and press the key you had map, translation will dispaly in your vim information area","first_name":"howl","6":"howl","last_name":"anderson","7":"anderson","releases":[{"0":"4008","vim_version":"7.2","1":"7.2","script_version":"0.2","2":"0.2","version_comment":"you can choice use youdao api key or use pyquery\/lxml","3":"you can choice use youdao api key or use pyquery\/lxml","package":"youdao.dict.zip","4":"youdao.dict.zip","src_id":"17821","5":"17821","creation_date":"1335446939","6":"1335446939"},{"0":"4008","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"youdao.dict.zip","4":"youdao.dict.zip","src_id":"17741","5":"17741","creation_date":"1333926622","6":"1333926622"}]},"4007":{"script_id":"4007","0":"4007","script_name":"python-imports.vim","1":"python-imports.vim","script_type":"ftplugin","2":"ftplugin","summary":"Scripted insertion of import statements","3":"Scripted insertion of import statements","description":"This plugin automates the insertion of import statements at the top of a python script. It contains a function capable of adding import statements at the top of the file. This function is mapped to <C-f>. So you can for example type \"sys.exit<C-f>\" and the plugin will append \"import sys\" above the other import statements at the top of the file, unless sys already was imported. The script tries to maintain the import statements in order.\r\n\r\nIf you define\r\n let g:PythonAutoAddImports = 1\r\nin your vimrc, this script will additionally hook into the period key, such that for common modules,\r\nimports are added as you type: Typing\r\n if len(sys.argv) == 0:\r\ninto an empty file will leave you with\r\n import sys\r\n if len(sys.argv) == 0:\r\nthen.\r\n\r\nThis plugin is in its early stages. Also, it is my first vim plugin, so do not expect everything to run smoothly yet. I maintain this script an vim repo at github:\r\n\r\nhttps:\/\/github.com\/phillipberndt\/python-imports.vim","4":"This plugin automates the insertion of import statements at the top of a python script. It contains a function capable of adding import statements at the top of the file. This function is mapped to <C-f>. So you can for example type \"sys.exit<C-f>\" and the plugin will append \"import sys\" above the other import statements at the top of the file, unless sys already was imported. The script tries to maintain the import statements in order.\r\n\r\nIf you define\r\n let g:PythonAutoAddImports = 1\r\nin your vimrc, this script will additionally hook into the period key, such that for common modules,\r\nimports are added as you type: Typing\r\n if len(sys.argv) == 0:\r\ninto an empty file will leave you with\r\n import sys\r\n if len(sys.argv) == 0:\r\nthen.\r\n\r\nThis plugin is in its early stages. Also, it is my first vim plugin, so do not expect everything to run smoothly yet. I maintain this script an vim repo at github:\r\n\r\nhttps:\/\/github.com\/phillipberndt\/python-imports.vim","install_details":"Copy python.vim into your ~\/.vim\/ftplugin folder. If you use Pathogen, create a directory ~\/.vim\/bundle\/vim-python-imports\/ftplugin and copy it there.","5":"Copy python.vim into your ~\/.vim\/ftplugin folder. If you use Pathogen, create a directory ~\/.vim\/bundle\/vim-python-imports\/ftplugin and copy it there.","first_name":"Phillip","6":"Phillip","last_name":"Berndt","7":"Berndt","releases":[{"0":"4007","vim_version":"7.0","1":"7.0","script_version":"0.2","2":"0.2","version_comment":"Various bug fixes","3":"Various bug fixes","package":"python.vim","4":"python.vim","src_id":"18938","5":"18938","creation_date":"1351849071","6":"1351849071"},{"0":"4007","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"python.vim","4":"python.vim","src_id":"17735","5":"17735","creation_date":"1333823732","6":"1333823732"}]},"4006":{"script_id":"4006","0":"4006","script_name":"HyperList","1":"HyperList","script_type":"utility","2":"utility","summary":"Everything. Concise and precise. Outliner, organizer, brainstormer, project mgmt","3":"Everything. Concise and precise. Outliner, organizer, brainstormer, project mgmt","description":"Outliner, todo-list, process description, project management, password encryption handler, idea organizer, logic tool, mind map... or for any number of different usages. Your imagination is (almost) the only limit. HyperList can be used to describe any state or transition - anything from simple shopping and todo lists to large project plans, process design, the human history, the human DNA or the whole universe. HyperList is a methodology to describe anything in plain text (see http:\/\/isene.org\/hyperlist\/). With HyperList, descriptions become simple, easily readable, concise and precise.\r\n\r\nThis VIM plugin makes it easy to create and manage HyperLists using VIM. This is one of the most feature-rich VIM plugins ever created. Github repo: https:\/\/github.com\/isene\/hyperlist.vim\r\n\r\nThe plugin includes a large range of features such as:\r\n\r\n* Automatically recognize files with the extension \".hl\"\r\n* Syntax highlighting of every HyperList element\r\n* Syntax highlighting of bold, italics and underline (using *word*, \/word\/ and _word_)\r\n* Automatic underlining of State or Transition items in a list\r\n* Collapse and uncollapse parts of a HyperList\r\n* Syntax highlighting of folded parts of a list\r\n* Set a specific fold level to unfold items down to that level\r\n* Linking\/referencing between elements (items) in a list\r\n* Easy navigation in lists, including jumping to references\r\n* Easy navigation to elements that needs filling out (when you use a list as a template)\r\n* Open referenced file under cursor using (g)VIM or external program (user definable)\r\n* Autonumbering of items and sub-items (children) and renumbering of visually selected items\r\n* Sorting a visually selected set of items (while letting the children stay with their parents\r\n* Create and toggle checkboxes, even with a time stamp for completion\r\n* Show\/hide of words or regex patterns\r\n* \"Presentation mode\" that folds everything but the current item\r\n* Highlighting of the current item and its children\r\n* Encrypt and decrypt whole lists or parts of a list\r\n* Autoencrypt\/decrypt files that has a file name starting with a dot\r\n* Export a HyperList to HTML, LaTeX or TPP formats\r\n* Transfer all items tagged with future dates\/times to a Google calendar\r\n* Show the complexity level of a HyperList\r\n* Description on how to include HyperLists within other filetypes, taking full advantage of the above features when including a HyperList in e.g. a normal .txt document\r\n* Menus with submenus for gVIM users\r\n* ... and there are many more features. Check out the comprehensive documentation (type \":help HyperList\" in VIM after install)\r\n\r\nFor a complete tutorial, go through the file HyperListTutorialAndTestSuite.hl in the documentation folder (~\/.vim\/doc\/HyperListTutorialAndTestSuite.hl). This file also serves as a complete test suite for releases of this plugin.\r\n\r\nThis VIM plugin is the continuation of the now deprecated WOIM plugin (http:\/\/www.vim.org\/scripts\/script.php?script_id=2518)\r\n\r\nThere is virtually no limit to what you can use HyperLists for. Contact me at g @ isene . com if you have any questions or suggestions, or if you just want to have a chat about HyperList (or any other things that are cool & interesting). See http:\/\/isene.org for more of my work.\r\n","4":"Outliner, todo-list, process description, project management, password encryption handler, idea organizer, logic tool, mind map... or for any number of different usages. Your imagination is (almost) the only limit. HyperList can be used to describe any state or transition - anything from simple shopping and todo lists to large project plans, process design, the human history, the human DNA or the whole universe. HyperList is a methodology to describe anything in plain text (see http:\/\/isene.org\/hyperlist\/). With HyperList, descriptions become simple, easily readable, concise and precise.\r\n\r\nThis VIM plugin makes it easy to create and manage HyperLists using VIM. This is one of the most feature-rich VIM plugins ever created. Github repo: https:\/\/github.com\/isene\/hyperlist.vim\r\n\r\nThe plugin includes a large range of features such as:\r\n\r\n* Automatically recognize files with the extension \".hl\"\r\n* Syntax highlighting of every HyperList element\r\n* Syntax highlighting of bold, italics and underline (using *word*, \/word\/ and _word_)\r\n* Automatic underlining of State or Transition items in a list\r\n* Collapse and uncollapse parts of a HyperList\r\n* Syntax highlighting of folded parts of a list\r\n* Set a specific fold level to unfold items down to that level\r\n* Linking\/referencing between elements (items) in a list\r\n* Easy navigation in lists, including jumping to references\r\n* Easy navigation to elements that needs filling out (when you use a list as a template)\r\n* Open referenced file under cursor using (g)VIM or external program (user definable)\r\n* Autonumbering of items and sub-items (children) and renumbering of visually selected items\r\n* Sorting a visually selected set of items (while letting the children stay with their parents\r\n* Create and toggle checkboxes, even with a time stamp for completion\r\n* Show\/hide of words or regex patterns\r\n* \"Presentation mode\" that folds everything but the current item\r\n* Highlighting of the current item and its children\r\n* Encrypt and decrypt whole lists or parts of a list\r\n* Autoencrypt\/decrypt files that has a file name starting with a dot\r\n* Export a HyperList to HTML, LaTeX or TPP formats\r\n* Transfer all items tagged with future dates\/times to a Google calendar\r\n* Show the complexity level of a HyperList\r\n* Description on how to include HyperLists within other filetypes, taking full advantage of the above features when including a HyperList in e.g. a normal .txt document\r\n* Menus with submenus for gVIM users\r\n* ... and there are many more features. Check out the comprehensive documentation (type \":help HyperList\" in VIM after install)\r\n\r\nFor a complete tutorial, go through the file HyperListTutorialAndTestSuite.hl in the documentation folder (~\/.vim\/doc\/HyperListTutorialAndTestSuite.hl). This file also serves as a complete test suite for releases of this plugin.\r\n\r\nThis VIM plugin is the continuation of the now deprecated WOIM plugin (http:\/\/www.vim.org\/scripts\/script.php?script_id=2518)\r\n\r\nThere is virtually no limit to what you can use HyperLists for. Contact me at g @ isene . com if you have any questions or suggestions, or if you just want to have a chat about HyperList (or any other things that are cool & interesting). See http:\/\/isene.org for more of my work.\r\n","install_details":"Download hyperlist.vmb. Then do:\r\n\r\nvim hyperlist.vmb\r\n:so %\r\n:q ","5":"Download hyperlist.vmb. Then do:\r\n\r\nvim hyperlist.vmb\r\n:so %\r\n:q ","first_name":"Geir","6":"Geir","last_name":"Isene","7":"Isene","releases":[{"0":"4006","vim_version":"7.0","1":"7.0","script_version":"2.5","2":"2.5","version_comment":"Included Substitutions (the reason for the HyperList 2.5 upgrade)","3":"Included Substitutions (the reason for the HyperList 2.5 upgrade)","package":"hyperlist.vmb","4":"hyperlist.vmb","src_id":"28541","5":"28541","creation_date":"1693435527","6":"1693435527"},{"0":"4006","vim_version":"7.0","1":"7.0","script_version":"2.4.7","2":"2.4.7","version_comment":"Fixed bugs in LaTeX conversion & ogther minor glitches.","3":"Fixed bugs in LaTeX conversion & ogther minor glitches.","package":"hyperlist.vmb","4":"hyperlist.vmb","src_id":"28534","5":"28534","creation_date":"1692805278","6":"1692805278"},{"0":"4006","vim_version":"7.0","1":"7.0","script_version":"2.4.6","2":"2.4.6","version_comment":"Added \"\/\" to Operators to cater for \"AND\/OR:\"\r\nBugfix of autoencryption","3":"Added \"\/\" to Operators to cater for \"AND\/OR:\"\r\nBugfix of autoencryption","package":"hyperlist.vmb","4":"hyperlist.vmb","src_id":"28372","5":"28372","creation_date":"1677702481","6":"1677702481"},{"0":"4006","vim_version":"7.0","1":"7.0","script_version":"2.4.5","2":"2.4.5","version_comment":"Fixed Neovim compatibility issues","3":"Fixed Neovim compatibility issues","package":"hyperlist.vmb","4":"hyperlist.vmb","src_id":"27608","5":"27608","creation_date":"1621199153","6":"1621199153"},{"0":"4006","vim_version":"7.0","1":"7.0","script_version":"2.4.4","2":"2.4.4","version_comment":"Refactoring (thanks to Nick Jensen [nickspoons] for guidance.","3":"Refactoring (thanks to Nick Jensen [nickspoons] for guidance.","package":"hyperlist.vmb","4":"hyperlist.vmb","src_id":"27267","5":"27267","creation_date":"1596689113","6":"1596689113"},{"0":"4006","vim_version":"7.0","1":"7.0","script_version":"2.4.3","2":"2.4.3","version_comment":"Several important upgrades under the hood. Programs for opening files in references can now be set by the user by setting the global variables in vimrc:\r\ng:wordprocessingprogram = \"\", g:spreadsheetprogram = \"\", g:presentationprogram = \"\", g:imageprogram = \"\", g:pdfprogram = \"\", g:browserprogram = \"\"\r\n","3":"Several important upgrades under the hood. Programs for opening files in references can now be set by the user by setting the global variables in vimrc:\r\ng:wordprocessingprogram = \"\", g:spreadsheetprogram = \"\", g:presentationprogram = \"\", g:imageprogram = \"\", g:pdfprogram = \"\", g:browserprogram = \"\"\r\n","package":"hyperlist.vmb","4":"hyperlist.vmb","src_id":"27259","5":"27259","creation_date":"1596326260","6":"1596326260"},{"0":"4006","vim_version":"7.0","1":"7.0","script_version":"2.4.2","2":"2.4.2","version_comment":"Quickfix: C-SPACE now maps to zA (toggles fold recursively)\r\nSeveral bugfixes in the HTML conversion\r\n","3":"Quickfix: C-SPACE now maps to zA (toggles fold recursively)\r\nSeveral bugfixes in the HTML conversion\r\n","package":"hyperlist.vmb","4":"hyperlist.vmb","src_id":"27242","5":"27242","creation_date":"1595488614","6":"1595488614"},{"0":"4006","vim_version":"7.0","1":"7.0","script_version":"2.4.1","2":"2.4.1","version_comment":"Updated to be compatible with HyperList definition v. 2.4\r\nIncluded full tutorial\/test suite (thanks to Don Kelley).\r\nImproved LaTeX export.\r\nImproved GotoRef() (mapped to 'gr' and '<CR>'). GotoRef() now also opens files if the format is <file:...>. GotoRef() handles the new relative references like <+2> and <-5>. \r\nSome other minor changes and clean-ups of the documentation.","3":"Updated to be compatible with HyperList definition v. 2.4\r\nIncluded full tutorial\/test suite (thanks to Don Kelley).\r\nImproved LaTeX export.\r\nImproved GotoRef() (mapped to 'gr' and '<CR>'). GotoRef() now also opens files if the format is <file:...>. GotoRef() handles the new relative references like <+2> and <-5>. \r\nSome other minor changes and clean-ups of the documentation.","package":"hyperlist.vmb","4":"hyperlist.vmb","src_id":"26779","5":"26779","creation_date":"1570396900","6":"1570396900"},{"0":"4006","vim_version":"7.0","1":"7.0","script_version":"2.3.17","2":"2.3.17","version_comment":"Significant release:\r\nAdded a GVIM menu. Full rework of the color schemes for VIM & gVIM.\r\nImprovement to Goto Reference (gr) and Autonumbering and more.\r\nSeveral minor changes and improvement in the docs.\r\nThanks to Don Kelley for suggestions and for extensive testing.\r\n","3":"Significant release:\r\nAdded a GVIM menu. Full rework of the color schemes for VIM & gVIM.\r\nImprovement to Goto Reference (gr) and Autonumbering and more.\r\nSeveral minor changes and improvement in the docs.\r\nThanks to Don Kelley for suggestions and for extensive testing.\r\n","package":"hyperlist.vmb","4":"hyperlist.vmb","src_id":"26699","5":"26699","creation_date":"1565851184","6":"1565851184"},{"0":"4006","vim_version":"7.0","1":"7.0","script_version":"2.3.16","2":"2.3.16","version_comment":"Improved the CalendarAdd functionality to include the item and all its children in the event description and the filename in the header for easy reference.","3":"Improved the CalendarAdd functionality to include the item and all its children in the event description and the filename in the header for easy reference.","package":"hyperlist.vmb","4":"hyperlist.vmb","src_id":"26688","5":"26688","creation_date":"1564903166","6":"1564903166"},{"0":"4006","vim_version":"7.0","1":"7.0","script_version":"2.3.15","2":"2.3.15","version_comment":"Added function CalendarAdd to add items with future dates as events to your Google calendar (requires gcalcli - https:\/\/github.com\/insanum\/gcalcli) - mapped to <leader>G","3":"Added function CalendarAdd to add items with future dates as events to your Google calendar (requires gcalcli - https:\/\/github.com\/insanum\/gcalcli) - mapped to <leader>G","package":"hyperlist.vmb","4":"hyperlist.vmb","src_id":"26686","5":"26686","creation_date":"1564634538","6":"1564634538"},{"0":"4006","vim_version":"7.0","1":"7.0","script_version":"2.3.14","2":"2.3.14","version_comment":"Added the feature to highlight\/focus the current part of a HyperList (toggles with <leader>h)","3":"Added the feature to highlight\/focus the current part of a HyperList (toggles with <leader>h)","package":"hyperlist.vmb","4":"hyperlist.vmb","src_id":"26491","5":"26491","creation_date":"1558246268","6":"1558246268"},{"0":"4006","vim_version":"7.0","1":"7.0","script_version":"2.3.13","2":"2.3.13","version_comment":"Added function Renumber() to (re)number items on same indent (using <leader>R in visual mode)","3":"Added function Renumber() to (re)number items on same indent (using <leader>R in visual mode)","package":"hyperlist.vmb","4":"hyperlist.vmb","src_id":"26251","5":"26251","creation_date":"1540413782","6":"1540413782"},{"0":"4006","vim_version":"7.0","1":"7.0","script_version":"2.3.12","2":"2.3.12","version_comment":"Minor fix to bold\/italics\/underlined elements","3":"Minor fix to bold\/italics\/underlined elements","package":"hyperlist.vmb","4":"hyperlist.vmb","src_id":"26059","5":"26059","creation_date":"1529345300","6":"1529345300"},{"0":"4006","vim_version":"7.0","1":"7.0","script_version":"2.3.11","2":"2.3.11","version_comment":"Added TPP conversion (info on TPP: https:\/\/github.com\/cbbrowne\/tpp). Pressing <leader>T now converts the HyperList into a basic TPP presentation.","3":"Added TPP conversion (info on TPP: https:\/\/github.com\/cbbrowne\/tpp). Pressing <leader>T now converts the HyperList into a basic TPP presentation.","package":"hyperlist.vmb","4":"hyperlist.vmb","src_id":"25838","5":"25838","creation_date":"1519377356","6":"1519377356"},{"0":"4006","vim_version":"7.0","1":"7.0","script_version":"2.3.10","2":"2.3.10","version_comment":"Prettified LaTeX output ( <leader>L )","3":"Prettified LaTeX output ( <leader>L )","package":"hyperlist.vmb","4":"hyperlist.vmb","src_id":"25825","5":"25825","creation_date":"1518529400","6":"1518529400"},{"0":"4006","vim_version":"7.0","1":"7.0","script_version":"2.3.9","2":"2.3.9","version_comment":"Fixed bugs in LaTeX & HTML conversion (to accept space in refs)\r\n","3":"Fixed bugs in LaTeX & HTML conversion (to accept space in refs)\r\n","package":"hyperlist.vmb","4":"hyperlist.vmb","src_id":"25802","5":"25802","creation_date":"1517006787","6":"1517006787"},{"0":"4006","vim_version":"7.0","1":"7.0","script_version":"2.3.8","2":"2.3.8","version_comment":"Added a sorting function: vmap <leader>s\r\nTo sort a set of items at a specific indentation, visually select (V) the\r\nitems you want to sort (including all the children of those items) and press\r\n<leader>s and the items in the range will be alphabetically sorted - but only\r\nthe items on the same level\/indentation as the first item selected. The sorted\r\nitems will keep their children. This is useful if parts of a HyperList is\r\nnumbered and you get the numbering out of sequence and wants to resort them.\r\nOne caveat, the last line in the selection cannot be the very last line in\r\nthe document (there must be an item or an empty line below it).","3":"Added a sorting function: vmap <leader>s\r\nTo sort a set of items at a specific indentation, visually select (V) the\r\nitems you want to sort (including all the children of those items) and press\r\n<leader>s and the items in the range will be alphabetically sorted - but only\r\nthe items on the same level\/indentation as the first item selected. The sorted\r\nitems will keep their children. This is useful if parts of a HyperList is\r\nnumbered and you get the numbering out of sequence and wants to resort them.\r\nOne caveat, the last line in the selection cannot be the very last line in\r\nthe document (there must be an item or an empty line below it).","package":"hyperlist.vmb","4":"hyperlist.vmb","src_id":"25623","5":"25623","creation_date":"1509116690","6":"1509116690"},{"0":"4006","vim_version":"7.0","1":"7.0","script_version":"2.3.7","2":"2.3.7","version_comment":"Autonumbering now works also with numbers ending in a period (both 4.2.1 and 4.2.1. now works for <cr>, <c-t> and <c-d>).","3":"Autonumbering now works also with numbers ending in a period (both 4.2.1 and 4.2.1. now works for <cr>, <c-t> and <c-d>).","package":"hyperlist.vmb","4":"hyperlist.vmb","src_id":"25498","5":"25498","creation_date":"1502483636","6":"1502483636"},{"0":"4006","vim_version":"7.0","1":"7.0","script_version":"2.3.6","2":"2.3.6","version_comment":"Added basic autonumbering (with <leader># or <leader>an)\r\n\r\n<leader># or <leader>an toggles autonumbering of new items (the previous item must be numbered for the next item to be autonumbered). An item is indented to the right with <c-t>, adding one level of numbering. An item is indented to the left with <c-d>, removing one level of numbering and increasing the number by one. Thanks to Jerry Antosh for the suggestion and for testing.\r\n\r\n","3":"Added basic autonumbering (with <leader># or <leader>an)\r\n\r\n<leader># or <leader>an toggles autonumbering of new items (the previous item must be numbered for the next item to be autonumbered). An item is indented to the right with <c-t>, adding one level of numbering. An item is indented to the left with <c-d>, removing one level of numbering and increasing the number by one. Thanks to Jerry Antosh for the suggestion and for testing.\r\n\r\n","package":"hyperlist.vmb","4":"hyperlist.vmb","src_id":"25318","5":"25318","creation_date":"1497730036","6":"1497730036"},{"0":"4006","vim_version":"7.0","1":"7.0","script_version":"2.3.5","2":"2.3.5","version_comment":"Added the function Complexity() to give a complexity score for a HyperList","3":"Added the function Complexity() to give a complexity score for a HyperList","package":"hyperlist.vmb","4":"hyperlist.vmb","src_id":"24901","5":"24901","creation_date":"1484556235","6":"1484556235"},{"0":"4006","vim_version":"7.0","1":"7.0","script_version":"2.3.4","2":"2.3.4","version_comment":"Fixed opening\/editing of default files opened via 'gf' (calling the OpenFile function)","3":"Fixed opening\/editing of default files opened via 'gf' (calling the OpenFile function)","package":"hyperlist.vmb","4":"hyperlist.vmb","src_id":"24498","5":"24498","creation_date":"1473069543","6":"1473069543"},{"0":"4006","vim_version":"7.0","1":"7.0","script_version":"2.3.3","2":"2.3.3","version_comment":"Fixed bug in install package.","3":"Fixed bug in install package.","package":"hyperlist.vmb","4":"hyperlist.vmb","src_id":"24403","5":"24403","creation_date":"1469570098","6":"1469570098"},{"0":"4006","vim_version":"7.0","1":"7.0","script_version":"2.3.2","2":"2.3.2","version_comment":"Added functionality to Show\/Hide of words under cursor\/regex pattern. Taken from VIM script #1594 (thanks to Amit Sethi).","3":"Added functionality to Show\/Hide of words under cursor\/regex pattern. Taken from VIM script #1594 (thanks to Amit Sethi).","package":"hyperlist.vmb","4":"hyperlist.vmb","src_id":"24352","5":"24352","creation_date":"1467284737","6":"1467284737"},{"0":"4006","vim_version":"7.0","1":"7.0","script_version":"2.3.1","2":"2.3.1","version_comment":"Added the function OpenFile() to open referenced file (mapped to \\'gf\\')\r\nUse \\\"gf\\\" to open the file under the cursor. Graphic files are opened in \\\"feh\\\", pdf files in \\\"zathura\\\" and MS\/OOO docs in \\\"LibreOffice\\\". Other filetypes are opened in VIM for editing. All this can be changed by editing the function OpenFile() in the file \\\"hyperlist.vim\\\".\r\n","3":"Added the function OpenFile() to open referenced file (mapped to \\'gf\\')\r\nUse \\\"gf\\\" to open the file under the cursor. Graphic files are opened in \\\"feh\\\", pdf files in \\\"zathura\\\" and MS\/OOO docs in \\\"LibreOffice\\\". Other filetypes are opened in VIM for editing. All this can be changed by editing the function OpenFile() in the file \\\"hyperlist.vim\\\".\r\n","package":"hyperlist.vba","4":"hyperlist.vba","src_id":"23426","5":"23426","creation_date":"1435677729","6":"1435677729"},{"0":"4006","vim_version":"7.0","1":"7.0","script_version":"2.3","2":"2.3","version_comment":"Updated plugin to HyperList definition version 2.3. \r\nMade the changes necessary to accommodate for Twitter-type (hash)Tags. \r\nNew markup for References (and included \\\"@\\\" in references). \r\nFixed bold\/italic\/underlined. \r\nChanged the Change Markup. \r\nUpdated Latex\/HTML conversion. \r\nUpdated documentation. \r\n","3":"Updated plugin to HyperList definition version 2.3. \r\nMade the changes necessary to accommodate for Twitter-type (hash)Tags. \r\nNew markup for References (and included \\\"@\\\" in references). \r\nFixed bold\/italic\/underlined. \r\nChanged the Change Markup. \r\nUpdated Latex\/HTML conversion. \r\nUpdated documentation. \r\n","package":"hyperlist.vba","4":"hyperlist.vba","src_id":"22912","5":"22912","creation_date":"1423819663","6":"1423819663"},{"0":"4006","vim_version":"7.0","1":"7.0","script_version":"2.1.7","2":"2.1.7","version_comment":"Changes:      Fixed bugs in Identifier and Multi. Cosmetic fixes.","3":"Changes:      Fixed bugs in Identifier and Multi. Cosmetic fixes.","package":"hyperlist.vba","4":"hyperlist.vba","src_id":"18827","5":"18827","creation_date":"1350505695","6":"1350505695"},{"0":"4006","vim_version":"7.0","1":"7.0","script_version":"2.1.6","2":"2.1.6","version_comment":"The Outliner \/ MindStructure \/ Logicizer \/ UniverseMapper \/ CoffeeMaker just got better:\r\nFixed the GotoRef function (mapped to \"gr\" and \"<CR>\")","3":"The Outliner \/ MindStructure \/ Logicizer \/ UniverseMapper \/ CoffeeMaker just got better:\r\nFixed the GotoRef function (mapped to \"gr\" and \"<CR>\")","package":"hyperlist.vba","4":"hyperlist.vba","src_id":"18816","5":"18816","creation_date":"1350337261","6":"1350337261"},{"0":"4006","vim_version":"7.0","1":"7.0","script_version":"2.1.5","2":"2.1.5","version_comment":"  Added \"zx\" as a command to update folding (to update syntax).\r\n  Added <CR> as an alternative to gr (Goto Ref).\r\n  Added a mark (m') to gr\/<CR> to facilitate easy jump back.\r\n  Speed-up. Also added a global variable that can be set if you don't want the\r\n  collapse functions active, set this: (\"g:disable_collapse\") - it will\r\n  considerably speed up large HyperListS.\r\n  Fixed syntax highlighting for the first line in a HyperList.\r\n  Documentation updates.\r\n","3":"  Added \"zx\" as a command to update folding (to update syntax).\r\n  Added <CR> as an alternative to gr (Goto Ref).\r\n  Added a mark (m') to gr\/<CR> to facilitate easy jump back.\r\n  Speed-up. Also added a global variable that can be set if you don't want the\r\n  collapse functions active, set this: (\"g:disable_collapse\") - it will\r\n  considerably speed up large HyperListS.\r\n  Fixed syntax highlighting for the first line in a HyperList.\r\n  Documentation updates.\r\n","package":"hyperlist.vba","4":"hyperlist.vba","src_id":"18799","5":"18799","creation_date":"1350150352","6":"1350150352"},{"0":"4006","vim_version":"7.0","1":"7.0","script_version":"2.1.3","2":"2.1.3","version_comment":"Changes:\r\nIncluded more accented characters. \r\nSpeedup; Adjusted minimum and maximum lines of sync'ing. \r\nFixed identifiers.\r\n","3":"Changes:\r\nIncluded more accented characters. \r\nSpeedup; Adjusted minimum and maximum lines of sync'ing. \r\nFixed identifiers.\r\n","package":"hyperlist.vba","4":"hyperlist.vba","src_id":"18672","5":"18672","creation_date":"1348391837","6":"1348391837"},{"0":"4006","vim_version":"7.0","1":"7.0","script_version":"2.1.2","2":"2.1.2","version_comment":"Important security upgrade: Removed traces of encrypted data upon en\/decrypting (part of) a HyperList.","3":"Important security upgrade: Removed traces of encrypted data upon en\/decrypting (part of) a HyperList.","package":"hyperlist.vba","4":"hyperlist.vba","src_id":"18233","5":"18233","creation_date":"1341665457","6":"1341665457"},{"0":"4006","vim_version":"7.0","1":"7.0","script_version":"2.1.1","2":"2.1.1","version_comment":"New HyperList version (2.1) with important changes (see http:\/\/isene.com\/hyperlist.pdf)\r\n\r\nUpgraded plugin to reflect the new Hyperlist version (2.1)","3":"New HyperList version (2.1) with important changes (see http:\/\/isene.com\/hyperlist.pdf)\r\n\r\nUpgraded plugin to reflect the new Hyperlist version (2.1)","package":"hyperlist.vba","4":"hyperlist.vba","src_id":"17833","5":"17833","creation_date":"1335654788","6":"1335654788"},{"0":"4006","vim_version":"7.0","1":"7.0","script_version":"2.1","2":"2.1","version_comment":"Better syntax highlighting for folds (both term & gui and both for dark and light backgrounds). \r\nAdded \"sync minlines\/maxlines\" settings to be changed for slow computers.","3":"Better syntax highlighting for folds (both term & gui and both for dark and light backgrounds). \r\nAdded \"sync minlines\/maxlines\" settings to be changed for slow computers.","package":"hyperlist.vba","4":"hyperlist.vba","src_id":"17782","5":"17782","creation_date":"1334562450","6":"1334562450"},{"0":"4006","vim_version":"7.0","1":"7.0","script_version":"2.0","2":"2.0","version_comment":"Initial upload","3":"Initial upload","package":"hyperlist.vba","4":"hyperlist.vba","src_id":"17728","5":"17728","creation_date":"1333637767","6":"1333637767"}]},"4005":{"script_id":"4005","0":"4005","script_name":"TextTransform","1":"TextTransform","script_type":"utility","2":"utility","summary":"Create text transformation mappings and commands.","3":"Create text transformation mappings and commands.","description":"DESCRIPTION\r\nThis plugin allows you to build your own text transformations. You only supply\r\nthe transformation algorithm in the form of a Vim function that takes a string\r\nand returns the transformed text (think substitute()), and TextTransform\r\nwill create all appropriate mappings and \/ or commands with a single call!\r\n\r\nDo you often perform the same :substitute commands over and over again? You\r\nmay be able to save yourself a lot of typing by creating custom commands and\r\nmappings for it. Because the mappings (like built-in Vim commands such as gU\r\nor g?)  are applicable to text moved over by {motion}, entire lines, and the\r\nvisual selection, you'll also have way more flexibility and places where you\r\ncan apply them (compared to the line-based range of :substitute).\r\n\r\nRELATED WORKS\r\n- Idea, design and implementation are based on Tim Pope's unimpaired.vim\r\n  plugin (vimscript #1590). It implements XML, URL and C String encoding\r\n  mappings, but isn't extensible with other algorithms.\r\n  The TextTransform plugin enhances unimpaired's transformation function with\r\n  handling of text objects and a list of selection fallbacks, and allows to\r\n  not only create mappings, but also transformation commands.\r\n- vim-transform (https:\/\/github.com\/t9md\/vim-transform) pipes the selection\r\n  through (multiple, configurable) external commands.\r\n\r\nUSAGE\r\nTextTransform#MakeMappings( {mapArgs}, {key}, {algorithm} [, {selectionModes}] )\r\n\r\n                        Create normal and visual mode mappings that apply\r\n                        {algorithm} to the text covered by {motion}, [count]\r\n                        line(s), and the visual selection.\r\n\r\n                        When {key} is <Leader>xy, the following mappings will\r\n                        be created:\r\n                        - <Leader>xy{motion}    applies to moved-over text\r\n                        - <Leader>xyy           applies to entire current line\r\n                        - {Visual}<Leader>xy    applies to visual selection\r\n                        For the linewise normal mode mapping, the last\r\n                        character of {key} is doubled, as is customary in Vim.\r\n\r\n                        When {key} is empty, only <Plug> mappings are created;\r\n                        mappings are also skipped when there are existing\r\n                        mappings to the <Plug> mappings. When {algorithm} is\r\n                        \"MyTransform\", the following <Plug> mappings are\r\n                        generated:\r\n                            nmap <Plug>TextTMyTransformOperator\r\n                            nmap <Plug>TextTMyTransformLine\r\n                            vmap <Plug>TextTMyTransformVisual\r\n                       Use this to selectively override or disable individual\r\n                        mappings.\r\n\r\n                        :map-arguments can be passed in {mapArgs}, e.g.\r\n                        \"<buffer>\" to make the generated mappings\r\n                        buffer-local.\r\n\r\n                        {algorithm} is the name of a function: \"MyTransform\",\r\n                        or a Funcref: function(\"MyTransform\"). This function\r\n                        must take one string argument and return a string.\r\n                            function MyTransform( text )\r\n                                return '[' . toupper(a:text) . ']'\r\n                            endfunction\r\n                       When the text that the mapping applies to spans more\r\n                        than one line, {algorithm} is invoked only once with\r\n                        the entire, newline-delimited text. You need to\r\n                        consider that when using regular expression atoms like\r\n                        ^ and $.\r\n                        If the algorithm needs to inspect the place in the\r\n                        buffer from where the text was retrieved, this\r\n                        information is provided in g:TextTransformContext, a\r\n                        dictionary with the following keys:\r\n                            \"mapMode\":  indicates what triggered the\r\n                                        transformation, one of\r\n                                        \"n\": normal mode mapping for line(s)\r\n                                             e.g. <Leader>xyy\r\n                                        \"o\": operator pending mode mapping for\r\n                                             moved-over text\r\n                                             e.g. <Leader>xy{motion}\r\n                                        \"v\": visual mode mapping\r\n                                             e.g. {Visual}<Leader>xy\r\n                                        \"c\": custom Ex command\r\n                            \"mode\": indicates the selection mode, one of \"v\",\r\n                                    \"V\", or \"^V\" (like visualmode())\r\n                            \"startPos\": the start position of the text\r\n                            \"endPos\"  : the end position of the text\r\n                            \"arguments\":List of optional passed command\r\n                                        arguments (when arguments have been\r\n                                        configured for a command; always empty\r\n                                        for mappings).\r\n                            \"isBang\":   Flag whether a [!] was passed to the\r\n                                        command; always 0 for mappings.\r\n                            \"register\": Used register (as v:register has\r\n                                        been clobbered). Commands need to pass\r\n                                        :command-register in\r\n                                        {commandOptions} to fill this.\r\n                            \"isAlgorithmRepeat\":\r\n                                        Flag whether the same\r\n                                        TextTransform-algorithm is used\r\n                                        (either through another mapping \/\r\n                                        command invocation, or via a mapping\r\n                                        repeat .) as the last time.\r\n                            \"isRepeat\": Flag whether the last used mapping\r\n                                        with the same algorithm has been\r\n                                        repeated via the . command. For\r\n                                        commands that process each line\r\n                                        individually, is 1 on subsequently\r\n                                        processed lines after the first line.\r\n\r\n                        The function can :throw an exception to signal an\r\n                        error. When the original text is returned,\r\n                        TextTransform will print an error that nothing was\r\n                        transformed. Do this when the transformation is not\r\n                        applicable.\r\n\r\n                        By default, the <Leader>xyy mapping will be applied to\r\n                        the entire line. For some transformations, a different\r\n                        default scope may make more sense, like the text\r\n                        between quotes. After all, the <Leader>xyy mapping is\r\n                        often faster than <Leader>xy{motion} or first doing a\r\n                        visual selection, and is easiest to commit to muscle\r\n                        memory, so it should \"do what I mean\".\r\n\r\n                        The optional {selectionModes} argument is a single\r\n                        text object (such as \"aw\"), motion (e.g. \"$\"),\r\n                        Funcref (for a custom selection), \/-delimited\r\n                        \"\/{pattern}\/\" (which selects the text region under \/\r\n                        after the cursor that matches {pattern}), or the\r\n                        string \"lines\", which represents the default behavior.\r\n                        If you pass a list of these, TextTransform tries each\r\n                        selectionMode, one after the other, until one captures\r\n                        non-empty text. For example, the passed list ['i\"',\r\n                        \"i'\", \"lines\"] will cause TextTransform to first try\r\n                        to capture the text inside double quotes, then fall\r\n                        back to text inside single quotes when the first one\r\n                        doesn't yield any text. Finally, the \"lines\" will\r\n                        transform the entire line if the single quote capture\r\n                        failed, too.\r\n                        A custom function should create a visual selection and\r\n                        return a non-zero value if the selection can be made.\r\n                        (Otherwise, the next selectionMode in the list is\r\n                        tried.) Here's a senseless example which selects\r\n                        [count] characters to the right of the cursor:\r\n                            function! MySelect()\r\n                                execute 'normal! lv' . v:count1 . \"l\\<Esc>\"\r\n                                return 1\r\n                            endfunction\r\n\r\nTextTransform#MakeCommand( {commandOptions}, {commandName}, {algorithm} [, {options}] )\r\n\r\n                        Create a custom command {commandName} that takes a\r\n                        range (defaulting to the current line), and applies\r\n                        {algorithm} to the line(s). With an optional [!], the\r\n                        usual \"Nothing transformed\" error is suppressed.\r\n\r\n                        :command attributes can be passed in\r\n                        {commandOptions}. For example, pass \"-range=%\" to make\r\n                        the command apply to the entire buffer when no range\r\n                        is specified. You can pass \"-nargs=...\" to pass\r\n                        arguments to the algorithm (via\r\n                        g:TextTransformContext.arguments).\r\n\r\n                        {algorithm} is the name of a function or a Funcref,\r\n                        cp. Transform-algorithm.\r\n\r\n                        The optional {options} dictionary can contain the\r\n                        following keys:\r\n    isProcessEntireText Flag whether all lines are passed as one\r\n                        newline-delimited string to {algorithm}, like mappings\r\n                        from TextTransform#MakeMappings() do. Off by\r\n                        default, so that each line is passed to {algorithm}\r\n                        individually (without the newline). This allows for a\r\n                        more efficient transformation. For subsequent lines,\r\n                        g:TextTransformContext.isRepeat is set to 1.\r\n                        You need to enable this if {algorithm} transforms the\r\n                        newline, adds or removes lines.\r\n\r\nTextTransform#MakeSelectionCommand( {commandOptions}, {commandName}, {algorithm}, {selectionModes} )\r\n\r\n                        Create a custom command {commandName} that applies\r\n                        {algorithm} on the TextTransform-selectionModes\r\n                        specified by {selectionModes}, or the current visual\r\n                        selection (when invoked from visual mode).\r\n                        This is useful for algorithms that do not make sense\r\n                        on entire lines. It's the command-variant of the\r\n                        line-based mapping created by\r\n                        TextTransform#MakeMappings(). For seldomly used\r\n                        transformations, a command may have advantages over a\r\n                        mapping: It doesn't take up precious mapping keys and\r\n                        is more explorable via command-line completion.\r\n\r\n                        Rest of the arguments as with TextTransform#MakeCommand().\r\n\r\nEXAMPLE\r\nHere's a stupid transformation function that replaces all alphabetic\r\ncharacters with \"X\":\r\n    function! BlankOut( text )\r\n        return substitute(a:text, '\\a', 'X', 'g')\r\n    endfunction\r\nWith this, this single call:\r\n    call TextTransform#MakeMappings('', '<Leader>x', 'BlankOut')\r\ncreates this set of mappings:\r\n\r\n    <Leader>x{motion}   transforms the text covered by {motion}\r\n    <Leader>xx          transforms [count] line(s)\r\n    {Visual}<Leader>x   transforms the visual selection\r\n\r\nYou can set up a command for this transformation just as easily:\r\n    call TextTransform#MakeCommand('', 'TextBlankOut', 'BlankOut')\r\nso you can blank out the next three lines via\r\n    :.,.+2TextBlankOut","4":"DESCRIPTION\r\nThis plugin allows you to build your own text transformations. You only supply\r\nthe transformation algorithm in the form of a Vim function that takes a string\r\nand returns the transformed text (think substitute()), and TextTransform\r\nwill create all appropriate mappings and \/ or commands with a single call!\r\n\r\nDo you often perform the same :substitute commands over and over again? You\r\nmay be able to save yourself a lot of typing by creating custom commands and\r\nmappings for it. Because the mappings (like built-in Vim commands such as gU\r\nor g?)  are applicable to text moved over by {motion}, entire lines, and the\r\nvisual selection, you'll also have way more flexibility and places where you\r\ncan apply them (compared to the line-based range of :substitute).\r\n\r\nRELATED WORKS\r\n- Idea, design and implementation are based on Tim Pope's unimpaired.vim\r\n  plugin (vimscript #1590). It implements XML, URL and C String encoding\r\n  mappings, but isn't extensible with other algorithms.\r\n  The TextTransform plugin enhances unimpaired's transformation function with\r\n  handling of text objects and a list of selection fallbacks, and allows to\r\n  not only create mappings, but also transformation commands.\r\n- vim-transform (https:\/\/github.com\/t9md\/vim-transform) pipes the selection\r\n  through (multiple, configurable) external commands.\r\n\r\nUSAGE\r\nTextTransform#MakeMappings( {mapArgs}, {key}, {algorithm} [, {selectionModes}] )\r\n\r\n                        Create normal and visual mode mappings that apply\r\n                        {algorithm} to the text covered by {motion}, [count]\r\n                        line(s), and the visual selection.\r\n\r\n                        When {key} is <Leader>xy, the following mappings will\r\n                        be created:\r\n                        - <Leader>xy{motion}    applies to moved-over text\r\n                        - <Leader>xyy           applies to entire current line\r\n                        - {Visual}<Leader>xy    applies to visual selection\r\n                        For the linewise normal mode mapping, the last\r\n                        character of {key} is doubled, as is customary in Vim.\r\n\r\n                        When {key} is empty, only <Plug> mappings are created;\r\n                        mappings are also skipped when there are existing\r\n                        mappings to the <Plug> mappings. When {algorithm} is\r\n                        \"MyTransform\", the following <Plug> mappings are\r\n                        generated:\r\n                            nmap <Plug>TextTMyTransformOperator\r\n                            nmap <Plug>TextTMyTransformLine\r\n                            vmap <Plug>TextTMyTransformVisual\r\n                       Use this to selectively override or disable individual\r\n                        mappings.\r\n\r\n                        :map-arguments can be passed in {mapArgs}, e.g.\r\n                        \"<buffer>\" to make the generated mappings\r\n                        buffer-local.\r\n\r\n                        {algorithm} is the name of a function: \"MyTransform\",\r\n                        or a Funcref: function(\"MyTransform\"). This function\r\n                        must take one string argument and return a string.\r\n                            function MyTransform( text )\r\n                                return '[' . toupper(a:text) . ']'\r\n                            endfunction\r\n                       When the text that the mapping applies to spans more\r\n                        than one line, {algorithm} is invoked only once with\r\n                        the entire, newline-delimited text. You need to\r\n                        consider that when using regular expression atoms like\r\n                        ^ and $.\r\n                        If the algorithm needs to inspect the place in the\r\n                        buffer from where the text was retrieved, this\r\n                        information is provided in g:TextTransformContext, a\r\n                        dictionary with the following keys:\r\n                            \"mapMode\":  indicates what triggered the\r\n                                        transformation, one of\r\n                                        \"n\": normal mode mapping for line(s)\r\n                                             e.g. <Leader>xyy\r\n                                        \"o\": operator pending mode mapping for\r\n                                             moved-over text\r\n                                             e.g. <Leader>xy{motion}\r\n                                        \"v\": visual mode mapping\r\n                                             e.g. {Visual}<Leader>xy\r\n                                        \"c\": custom Ex command\r\n                            \"mode\": indicates the selection mode, one of \"v\",\r\n                                    \"V\", or \"^V\" (like visualmode())\r\n                            \"startPos\": the start position of the text\r\n                            \"endPos\"  : the end position of the text\r\n                            \"arguments\":List of optional passed command\r\n                                        arguments (when arguments have been\r\n                                        configured for a command; always empty\r\n                                        for mappings).\r\n                            \"isBang\":   Flag whether a [!] was passed to the\r\n                                        command; always 0 for mappings.\r\n                            \"register\": Used register (as v:register has\r\n                                        been clobbered). Commands need to pass\r\n                                        :command-register in\r\n                                        {commandOptions} to fill this.\r\n                            \"isAlgorithmRepeat\":\r\n                                        Flag whether the same\r\n                                        TextTransform-algorithm is used\r\n                                        (either through another mapping \/\r\n                                        command invocation, or via a mapping\r\n                                        repeat .) as the last time.\r\n                            \"isRepeat\": Flag whether the last used mapping\r\n                                        with the same algorithm has been\r\n                                        repeated via the . command. For\r\n                                        commands that process each line\r\n                                        individually, is 1 on subsequently\r\n                                        processed lines after the first line.\r\n\r\n                        The function can :throw an exception to signal an\r\n                        error. When the original text is returned,\r\n                        TextTransform will print an error that nothing was\r\n                        transformed. Do this when the transformation is not\r\n                        applicable.\r\n\r\n                        By default, the <Leader>xyy mapping will be applied to\r\n                        the entire line. For some transformations, a different\r\n                        default scope may make more sense, like the text\r\n                        between quotes. After all, the <Leader>xyy mapping is\r\n                        often faster than <Leader>xy{motion} or first doing a\r\n                        visual selection, and is easiest to commit to muscle\r\n                        memory, so it should \"do what I mean\".\r\n\r\n                        The optional {selectionModes} argument is a single\r\n                        text object (such as \"aw\"), motion (e.g. \"$\"),\r\n                        Funcref (for a custom selection), \/-delimited\r\n                        \"\/{pattern}\/\" (which selects the text region under \/\r\n                        after the cursor that matches {pattern}), or the\r\n                        string \"lines\", which represents the default behavior.\r\n                        If you pass a list of these, TextTransform tries each\r\n                        selectionMode, one after the other, until one captures\r\n                        non-empty text. For example, the passed list ['i\"',\r\n                        \"i'\", \"lines\"] will cause TextTransform to first try\r\n                        to capture the text inside double quotes, then fall\r\n                        back to text inside single quotes when the first one\r\n                        doesn't yield any text. Finally, the \"lines\" will\r\n                        transform the entire line if the single quote capture\r\n                        failed, too.\r\n                        A custom function should create a visual selection and\r\n                        return a non-zero value if the selection can be made.\r\n                        (Otherwise, the next selectionMode in the list is\r\n                        tried.) Here's a senseless example which selects\r\n                        [count] characters to the right of the cursor:\r\n                            function! MySelect()\r\n                                execute 'normal! lv' . v:count1 . \"l\\<Esc>\"\r\n                                return 1\r\n                            endfunction\r\n\r\nTextTransform#MakeCommand( {commandOptions}, {commandName}, {algorithm} [, {options}] )\r\n\r\n                        Create a custom command {commandName} that takes a\r\n                        range (defaulting to the current line), and applies\r\n                        {algorithm} to the line(s). With an optional [!], the\r\n                        usual \"Nothing transformed\" error is suppressed.\r\n\r\n                        :command attributes can be passed in\r\n                        {commandOptions}. For example, pass \"-range=%\" to make\r\n                        the command apply to the entire buffer when no range\r\n                        is specified. You can pass \"-nargs=...\" to pass\r\n                        arguments to the algorithm (via\r\n                        g:TextTransformContext.arguments).\r\n\r\n                        {algorithm} is the name of a function or a Funcref,\r\n                        cp. Transform-algorithm.\r\n\r\n                        The optional {options} dictionary can contain the\r\n                        following keys:\r\n    isProcessEntireText Flag whether all lines are passed as one\r\n                        newline-delimited string to {algorithm}, like mappings\r\n                        from TextTransform#MakeMappings() do. Off by\r\n                        default, so that each line is passed to {algorithm}\r\n                        individually (without the newline). This allows for a\r\n                        more efficient transformation. For subsequent lines,\r\n                        g:TextTransformContext.isRepeat is set to 1.\r\n                        You need to enable this if {algorithm} transforms the\r\n                        newline, adds or removes lines.\r\n\r\nTextTransform#MakeSelectionCommand( {commandOptions}, {commandName}, {algorithm}, {selectionModes} )\r\n\r\n                        Create a custom command {commandName} that applies\r\n                        {algorithm} on the TextTransform-selectionModes\r\n                        specified by {selectionModes}, or the current visual\r\n                        selection (when invoked from visual mode).\r\n                        This is useful for algorithms that do not make sense\r\n                        on entire lines. It's the command-variant of the\r\n                        line-based mapping created by\r\n                        TextTransform#MakeMappings(). For seldomly used\r\n                        transformations, a command may have advantages over a\r\n                        mapping: It doesn't take up precious mapping keys and\r\n                        is more explorable via command-line completion.\r\n\r\n                        Rest of the arguments as with TextTransform#MakeCommand().\r\n\r\nEXAMPLE\r\nHere's a stupid transformation function that replaces all alphabetic\r\ncharacters with \"X\":\r\n    function! BlankOut( text )\r\n        return substitute(a:text, '\\a', 'X', 'g')\r\n    endfunction\r\nWith this, this single call:\r\n    call TextTransform#MakeMappings('', '<Leader>x', 'BlankOut')\r\ncreates this set of mappings:\r\n\r\n    <Leader>x{motion}   transforms the text covered by {motion}\r\n    <Leader>xx          transforms [count] line(s)\r\n    {Visual}<Leader>x   transforms the visual selection\r\n\r\nYou can set up a command for this transformation just as easily:\r\n    call TextTransform#MakeCommand('', 'TextBlankOut', 'BlankOut')\r\nso you can blank out the next three lines via\r\n    :.,.+2TextBlankOut","install_details":"INSTALLATION\r\nThe code is hosted in a Git repo at\r\n    https:\/\/github.com\/inkarkat\/vim-TextTransform\r\nYou can use your favorite plugin manager, or \"git clone\" into a directory used\r\nfor Vim packages. Releases are on the \"stable\" branch, the latest unstable\r\ndevelopment snapshot on \"master\".\r\n\r\nThis script is also packaged as a vimball. If you have the \"gunzip\"\r\ndecompressor in your PATH, simply edit the *.vmb.gz package in Vim; otherwise,\r\ndecompress the archive first, e.g. using WinZip. Inside Vim, install by\r\nsourcing the vimball or via the :UseVimball command.\r\n    vim TextTransform*.vmb.gz\r\n    :so %\r\nTo uninstall, use the :RmVimball command.\r\n\r\nDEPENDENCIES\r\n- Requires Vim 7.0 or higher.\r\n- Requires the ingo-library.vim plugin (vimscript #4433), version 1.022 or\r\n  higher.\r\n- repeat.vim (vimscript #2136) plugin (optional)\r\n- visualrepeat.vim (vimscript #3848) plugin (optional)","5":"INSTALLATION\r\nThe code is hosted in a Git repo at\r\n    https:\/\/github.com\/inkarkat\/vim-TextTransform\r\nYou can use your favorite plugin manager, or \"git clone\" into a directory used\r\nfor Vim packages. Releases are on the \"stable\" branch, the latest unstable\r\ndevelopment snapshot on \"master\".\r\n\r\nThis script is also packaged as a vimball. If you have the \"gunzip\"\r\ndecompressor in your PATH, simply edit the *.vmb.gz package in Vim; otherwise,\r\ndecompress the archive first, e.g. using WinZip. Inside Vim, install by\r\nsourcing the vimball or via the :UseVimball command.\r\n    vim TextTransform*.vmb.gz\r\n    :so %\r\nTo uninstall, use the :RmVimball command.\r\n\r\nDEPENDENCIES\r\n- Requires Vim 7.0 or higher.\r\n- Requires the ingo-library.vim plugin (vimscript #4433), version 1.022 or\r\n  higher.\r\n- repeat.vim (vimscript #2136) plugin (optional)\r\n- visualrepeat.vim (vimscript #3848) plugin (optional)","first_name":"Ingo","6":"Ingo","last_name":"Karkat","7":"Karkat","releases":[{"0":"4005","vim_version":"7.0","1":"7.0","script_version":"1.25","2":"1.25","version_comment":"- Minor: Remove debugging output when a command transforms whole lines.\r\n- FIX: Correctly handle command range of :. when on a closed fold. Need to use ingo#range#NetStart().\r\n- The selectionModes argument may (in \/{pattern}\/ form) contain special characters (e.g. \"|\" in \/foo\\|bar\/) that need escaping in order to survive.\r\n- Add TextTransform#Selections#EntireBuffer() utility text selection.\r\n- FIX: Redefinition of l:SelectionModes inside loop (since 1.12) may cause \"E705: Variable name conflicts with existing function\" (in Vim 7.2.000). Move the variable definition out of the loop.\r\n- Don't apply TextTransform#Selections#SurroundedByCharsInSingleLine() when [count] is given; skip to the next selectionMode then.\r\n- Handle non-String results returned by the algorithm via TextTransform#ToText().\r\n- When transforming individual lines and we get multiple lines as the algorithm's result, setline() cannot be used; instead, use ingo#lines#Replace().\r\n- When transforming individual or whole lines and we get multiple \/ additional lines as the algorithm's result, these need to be accounted for, for cursor positioning and reporting.\r\n- Add TextTransform#ToText() to handle non-String results returned by the algorithm. Floats need to be explicitly converted; Lists should be flattened, too, to yield correct results for the modification check with the original text. Dicts and Funcrefs should not be returned and cause an exception.\r\n- Pass v:count, not v:count1 to (visual)repeat.vim; this matters when using TextTransform#Selections#SurroundedByCharsInSingleLine(), which doesn't handle a count.\r\n- FIX: Do not attempt to restore empty visual mode, as this results in a beep; this can happen when no visual selection wasn't done yet.\r\n- ENH: Add g:TextTransformContext.register for transformations that use a (user-specified) register.\r\n- ENH: Keep the original register contents of the default register (that is used for buffer manipulation) during application of the algorithm. The user may want to access it. *** You need to update to ingo-library (vimscript #4433) version 1.022! ***","3":"- Minor: Remove debugging output when a command transforms whole lines.\r\n- FIX: Correctly handle command range of :. when on a closed fold. Need to use ingo#range#NetStart().\r\n- The selectionModes argument may (in \/{pattern}\/ form) contain special characters (e.g. \"|\" in \/foo\\|bar\/) that need escaping in order to survive.\r\n- Add TextTransform#Selections#EntireBuffer() utility text selection.\r\n- FIX: Redefinition of l:SelectionModes inside loop (since 1.12) may cause \"E705: Variable name conflicts with existing function\" (in Vim 7.2.000). Move the variable definition out of the loop.\r\n- Don't apply TextTransform#Selections#SurroundedByCharsInSingleLine() when [count] is given; skip to the next selectionMode then.\r\n- Handle non-String results returned by the algorithm via TextTransform#ToText().\r\n- When transforming individual lines and we get multiple lines as the algorithm's result, setline() cannot be used; instead, use ingo#lines#Replace().\r\n- When transforming individual or whole lines and we get multiple \/ additional lines as the algorithm's result, these need to be accounted for, for cursor positioning and reporting.\r\n- Add TextTransform#ToText() to handle non-String results returned by the algorithm. Floats need to be explicitly converted; Lists should be flattened, too, to yield correct results for the modification check with the original text. Dicts and Funcrefs should not be returned and cause an exception.\r\n- Pass v:count, not v:count1 to (visual)repeat.vim; this matters when using TextTransform#Selections#SurroundedByCharsInSingleLine(), which doesn't handle a count.\r\n- FIX: Do not attempt to restore empty visual mode, as this results in a beep; this can happen when no visual selection wasn't done yet.\r\n- ENH: Add g:TextTransformContext.register for transformations that use a (user-specified) register.\r\n- ENH: Keep the original register contents of the default register (that is used for buffer manipulation) during application of the algorithm. The user may want to access it. *** You need to update to ingo-library (vimscript #4433) version 1.022! ***","package":"TextTransform-1.25.vmb.gz","4":"TextTransform-1.25.vmb.gz","src_id":"26444","5":"26444","creation_date":"1553917171","6":"1553917171"},{"0":"4005","vim_version":"7.0","1":"7.0","script_version":"1.24","2":"1.24","version_comment":"- ENH: Allow optional [!] for made commands, and suppress the \"Nothing transformed\" error in that case. This can help when using the resulting command as an optional step, as prefixing with :silent! can be difficult to combine with ranges, and would suppress _all_ transformation errors.\r\n- ENH: Add g:TextTransformContext.isBang (for custom transformation commands).","3":"- ENH: Allow optional [!] for made commands, and suppress the \"Nothing transformed\" error in that case. This can help when using the resulting command as an optional step, as prefixing with :silent! can be difficult to combine with ranges, and would suppress _all_ transformation errors.\r\n- ENH: Add g:TextTransformContext.isBang (for custom transformation commands).","package":"TextTransform-1.24.vmb.gz","4":"TextTransform-1.24.vmb.gz","src_id":"22061","5":"22061","creation_date":"1403204451","6":"1403204451"},{"0":"4005","vim_version":"7.0","1":"7.0","script_version":"1.23","2":"1.23","version_comment":"- ENH: Support selection mode \"\/{pattern}\/\", which selects the text region under \/ after the cursor that matches {pattern}.\r\n- Minor: Also handle :echoerr in the algorithm.","3":"- ENH: Support selection mode \"\/{pattern}\/\", which selects the text region under \/ after the cursor that matches {pattern}.\r\n- Minor: Also handle :echoerr in the algorithm.","package":"TextTransform-1.23.vmb.gz","4":"TextTransform-1.23.vmb.gz","src_id":"21972","5":"21972","creation_date":"1401562148","6":"1401562148"},{"0":"4005","vim_version":"7.0","1":"7.0","script_version":"1.22","2":"1.22","version_comment":"- Add TextTransform\/Selections.vim.","3":"- Add TextTransform\/Selections.vim.","package":"TextTransform-1.22.vmb.gz","4":"TextTransform-1.22.vmb.gz","src_id":"21574","5":"21574","creation_date":"1394116000","6":"1394116000"},{"0":"4005","vim_version":"7.0","1":"7.0","script_version":"1.21","2":"1.21","version_comment":"- Minor: Use functions for newer ingo-library.\r\n- Need to use ingo#compat#setpos() to restore the selection in Vim versions before 7.3.590.","3":"- Minor: Use functions for newer ingo-library.\r\n- Need to use ingo#compat#setpos() to restore the selection in Vim versions before 7.3.590.","package":"TextTransform-1.21.vmb.gz","4":"TextTransform-1.21.vmb.gz","src_id":"21326","5":"21326","creation_date":"1389817941","6":"1389817941"},{"0":"4005","vim_version":"7.0","1":"7.0","script_version":"1.20","2":"1.20","version_comment":"- FIX: When the selection mode is a text object, and the text is at the end of the line, the replacement is inserted one-off to the left.\r\n- Implement abort on error for generated commands.\r\n- Add g:TextTransformContext.mapMode context information so that transformations can query from which source (line- or motion-mapping, or custom command) they've been triggered.\r\n- Add g:TextTransformContext.isAlgorithmRepeat and g:TextTransformContext.isRepeat context information (the latter through additional <Plug>TextR... mappings) so that transformations that e.g. query the user for something can skip the query and re-use the previously entered value on a repeat of the mapping. It also allows commands that process the lines individually to do different processing (or caching of expensive values) for the first processed line.\r\n- Allow to pass command arguments, which are then accessible to the algorithm through g:TextTransformContext.arguments.\r\n- Minor: Make substitute() robust against 'ignorecase'.","3":"- FIX: When the selection mode is a text object, and the text is at the end of the line, the replacement is inserted one-off to the left.\r\n- Implement abort on error for generated commands.\r\n- Add g:TextTransformContext.mapMode context information so that transformations can query from which source (line- or motion-mapping, or custom command) they've been triggered.\r\n- Add g:TextTransformContext.isAlgorithmRepeat and g:TextTransformContext.isRepeat context information (the latter through additional <Plug>TextR... mappings) so that transformations that e.g. query the user for something can skip the query and re-use the previously entered value on a repeat of the mapping. It also allows commands that process the lines individually to do different processing (or caching of expensive values) for the first processed line.\r\n- Allow to pass command arguments, which are then accessible to the algorithm through g:TextTransformContext.arguments.\r\n- Minor: Make substitute() robust against 'ignorecase'.","package":"TextTransform-1.20.vmb.gz","4":"TextTransform-1.20.vmb.gz","src_id":"20846","5":"20846","creation_date":"1380124666","6":"1380124666"},{"0":"4005","vim_version":"7.0","1":"7.0","script_version":"1.11","2":"1.11","version_comment":"- Avoid changing the jumplist.\r\n- Add dependency to ingo-library (vimscript #4433).\r\n- FIX: When the selection mode is a text object, must still establish a visual selection of the yanked text so that g:TextTransformContext contains valid data for use by a:algorithm.","3":"- Avoid changing the jumplist.\r\n- Add dependency to ingo-library (vimscript #4433).\r\n- FIX: When the selection mode is a text object, must still establish a visual selection of the yanked text so that g:TextTransformContext contains valid data for use by a:algorithm.","package":"TextTransform-1.11.vmb.gz","4":"TextTransform-1.11.vmb.gz","src_id":"20149","5":"20149","creation_date":"1368790559","6":"1368790559"},{"0":"4005","vim_version":"7.0","1":"7.0","script_version":"1.10","2":"1.10","version_comment":"- FIX: In a blockwise visual selection with $ to the end of the lines, only the square block from '< to '> is transformed. Need to yank the selection with gvy instead of defining a new selection with the marks, a mistake inherited from the original unimpaired.vim implementation.\r\n- Save and restore the original visual area to avoid clobbering the '< and '> marks and gv by line- and motion mappings.\r\n- Temporarily set g:TextTransformContext to the begin and end of the currently transformed area to offer an extended interface to algorithms.","3":"- FIX: In a blockwise visual selection with $ to the end of the lines, only the square block from '< to '> is transformed. Need to yank the selection with gvy instead of defining a new selection with the marks, a mistake inherited from the original unimpaired.vim implementation.\r\n- Save and restore the original visual area to avoid clobbering the '< and '> marks and gv by line- and motion mappings.\r\n- Temporarily set g:TextTransformContext to the begin and end of the currently transformed area to offer an extended interface to algorithms.","package":"TextTransform-1.10.vmb.gz","4":"TextTransform-1.10.vmb.gz","src_id":"19407","5":"19407","creation_date":"1358754587","6":"1358754587"},{"0":"4005","vim_version":"7.0","1":"7.0","script_version":"1.03","2":"1.03","version_comment":"- For the custom operators, handle readonly and nomodifiable buffers by printing just the warning \/ error, without the multi-line function error.\r\n- Avoid clobbering the expression register (for commands that us  options.isProcessEntireText).","3":"- For the custom operators, handle readonly and nomodifiable buffers by printing just the warning \/ error, without the multi-line function error.\r\n- Avoid clobbering the expression register (for commands that us  options.isProcessEntireText).","package":"TextTransform-1.03.vmb.gz","4":"TextTransform-1.03.vmb.gz","src_id":"18550","5":"18550","creation_date":"1346844630","6":"1346844630"},{"0":"4005","vim_version":"7.0","1":"7.0","script_version":"1.02","2":"1.02","version_comment":"Avoid \"E706: Variable type mismatch\" when TextTransform#Arbitrary#Expression() is used with both Funcref- and String-type algorithms.","3":"Avoid \"E706: Variable type mismatch\" when TextTransform#Arbitrary#Expression() is used with both Funcref- and String-type algorithms.","package":"TextTransform.vba.gz","4":"TextTransform.vba.gz","src_id":"18344","5":"18344","creation_date":"1343656228","6":"1343656228"},{"0":"4005","vim_version":"7.0","1":"7.0","script_version":"1.01","2":"1.01","version_comment":"In mappings and selection commands, place the cursor at the beginning of the transformed text, to be consistent with built-in transformation commands like gU, and because it makes much more sense.","3":"In mappings and selection commands, place the cursor at the beginning of the transformed text, to be consistent with built-in transformation commands like gU, and because it makes much more sense.","package":"TextTransform.vba.gz","4":"TextTransform.vba.gz","src_id":"17726","5":"17726","creation_date":"1333633196","6":"1333633196"},{"0":"4005","vim_version":"7.0","1":"7.0","script_version":"1.00","2":"1.00","version_comment":"Initial upload","3":"Initial upload","package":"TextTransform.vba.gz","4":"TextTransform.vba.gz","src_id":"17723","5":"17723","creation_date":"1333617267","6":"1333617267"}]},"4004":{"script_id":"4004","0":"4004","script_name":"dosbatch_movement","1":"dosbatch_movement","script_type":"ftplugin","2":"ftplugin","summary":"Movement over MSDOS batch file functions \/ labels with ]m etc. ","3":"Movement over MSDOS batch file functions \/ labels with ]m etc. ","description":"DESCRIPTION\r\nThis filetype plugin provides movement commands and text objects for MSDOS\r\nbatch file functions and labels.\r\n\r\nUSAGE\r\n                        Move around MSDOS batch file functions \/ labels.\r\n                        A new section is also defined by a comment starting with\r\n                        ::- or ::= or ::*.\r\n]m                      Go to [count] next start of a function \/ label.\r\n]M                      Go to [count] next end of a function \/ label.\r\n[m                      Go to [count] previous start of a function \/ label.\r\n[M                      Go to [count] previous end of a function \/ label.\r\n\r\nim                      \"inner method\" text object, select [count] function \/\r\n                        label contents.\r\nam                      \"a method\" text object, select [count] function \/ label,\r\n                        including the function \/ label definition and end.","4":"DESCRIPTION\r\nThis filetype plugin provides movement commands and text objects for MSDOS\r\nbatch file functions and labels.\r\n\r\nUSAGE\r\n                        Move around MSDOS batch file functions \/ labels.\r\n                        A new section is also defined by a comment starting with\r\n                        ::- or ::= or ::*.\r\n]m                      Go to [count] next start of a function \/ label.\r\n]M                      Go to [count] next end of a function \/ label.\r\n[m                      Go to [count] previous start of a function \/ label.\r\n[M                      Go to [count] previous end of a function \/ label.\r\n\r\nim                      \"inner method\" text object, select [count] function \/\r\n                        label contents.\r\nam                      \"a method\" text object, select [count] function \/ label,\r\n                        including the function \/ label definition and end.","install_details":"INSTALLATION\r\nThis script is packaged as a vimball. If you have the \"gunzip\" decompressor\r\nin your PATH, simply edit the *.vba.gz package in Vim; otherwise, decompress\r\nthe archive first, e.g. using WinZip. Inside Vim, install by sourcing the\r\nvimball or via the :UseVimball command.\r\n    vim dosbatch_movement.vba.gz\r\n    :so %\r\nTo uninstall, use the :RmVimball command.\r\n\r\nDEPENDENCIES\r\n- Requires Vim 7.0 or higher.\r\n- Requires the CountJump plugin (vimscript #3130).","5":"INSTALLATION\r\nThis script is packaged as a vimball. If you have the \"gunzip\" decompressor\r\nin your PATH, simply edit the *.vba.gz package in Vim; otherwise, decompress\r\nthe archive first, e.g. using WinZip. Inside Vim, install by sourcing the\r\nvimball or via the :UseVimball command.\r\n    vim dosbatch_movement.vba.gz\r\n    :so %\r\nTo uninstall, use the :RmVimball command.\r\n\r\nDEPENDENCIES\r\n- Requires Vim 7.0 or higher.\r\n- Requires the CountJump plugin (vimscript #3130).","first_name":"Ingo","6":"Ingo","last_name":"Karkat","7":"Karkat","releases":[{"0":"4004","vim_version":"7.0","1":"7.0","script_version":"1.00","2":"1.00","version_comment":"Initial upload","3":"Initial upload","package":"dosbatch_movement.vba.gz","4":"dosbatch_movement.vba.gz","src_id":"17716","5":"17716","creation_date":"1333534145","6":"1333534145"}]},"4003":{"script_id":"4003","0":"4003","script_name":"vbs_movement","1":"vbs_movement","script_type":"ftplugin","2":"ftplugin","summary":"Movement over VBScript classes \/ functions \/ properties \/ subs with ]m etc. ","3":"Movement over VBScript classes \/ functions \/ properties \/ subs with ]m etc. ","description":"DESCRIPTION\r\nThis filetype plugin provides movement commands and text objects for Visual\r\nBasic Script classes, functions, properties, and subs.\r\n\r\nUSAGE\r\n                        Move around VBScript functions, properties and subs:\r\n]m                      Go to [count] next start of a function \/ property \/ sub.\r\n]M                      Go to [count] next end of a function \/ property \/ sub.\r\n[m                      Go to [count] previous start of a function \/ property \/ sub.\r\n[M                      Go to [count] previous end of a function \/ property \/ sub.\r\n\r\n]gm                     Go to [count] next start of a class.\r\n]gM                     Go to [count] next end of a class.\r\n[gm                     Go to [count] previous start of a class.\r\n[gM                     Go to [count] previous end of a class.\r\n\r\nim                      \"inner method\" text object, select [count] function \/\r\n                        property \/ sub contents.\r\nam                      \"a method\" text object, select [count] function \/\r\n                        property \/ subs, including the function \/ property \/ sub\r\n                        definition and 'end ...'.\r\n\r\nigm                     \"inner class\" text object, select [count] class contents.\r\nagm                     \"a class\" text object, select [count] classes, including\r\n                        the class definition and \"end class\"","4":"DESCRIPTION\r\nThis filetype plugin provides movement commands and text objects for Visual\r\nBasic Script classes, functions, properties, and subs.\r\n\r\nUSAGE\r\n                        Move around VBScript functions, properties and subs:\r\n]m                      Go to [count] next start of a function \/ property \/ sub.\r\n]M                      Go to [count] next end of a function \/ property \/ sub.\r\n[m                      Go to [count] previous start of a function \/ property \/ sub.\r\n[M                      Go to [count] previous end of a function \/ property \/ sub.\r\n\r\n]gm                     Go to [count] next start of a class.\r\n]gM                     Go to [count] next end of a class.\r\n[gm                     Go to [count] previous start of a class.\r\n[gM                     Go to [count] previous end of a class.\r\n\r\nim                      \"inner method\" text object, select [count] function \/\r\n                        property \/ sub contents.\r\nam                      \"a method\" text object, select [count] function \/\r\n                        property \/ subs, including the function \/ property \/ sub\r\n                        definition and 'end ...'.\r\n\r\nigm                     \"inner class\" text object, select [count] class contents.\r\nagm                     \"a class\" text object, select [count] classes, including\r\n                        the class definition and \"end class\"","install_details":"INSTALLATION\r\nThis script is packaged as a vimball. If you have the \"gunzip\" decompressor\r\nin your PATH, simply edit the *.vba.gz package in Vim; otherwise, decompress\r\nthe archive first, e.g. using WinZip. Inside Vim, install by sourcing the\r\nvimball or via the :UseVimball command.\r\n    vim vbs_movement.vba.gz\r\n    :so %\r\nTo uninstall, use the :RmVimball command.\r\n\r\nDEPENDENCIES\r\n- Requires Vim 7.0 or higher.\r\n- Requires the CountJump plugin (vimscript #3130).","5":"INSTALLATION\r\nThis script is packaged as a vimball. If you have the \"gunzip\" decompressor\r\nin your PATH, simply edit the *.vba.gz package in Vim; otherwise, decompress\r\nthe archive first, e.g. using WinZip. Inside Vim, install by sourcing the\r\nvimball or via the :UseVimball command.\r\n    vim vbs_movement.vba.gz\r\n    :so %\r\nTo uninstall, use the :RmVimball command.\r\n\r\nDEPENDENCIES\r\n- Requires Vim 7.0 or higher.\r\n- Requires the CountJump plugin (vimscript #3130).","first_name":"Ingo","6":"Ingo","last_name":"Karkat","7":"Karkat","releases":[{"0":"4003","vim_version":"7.0","1":"7.0","script_version":"1.00","2":"1.00","version_comment":"Initial upload","3":"Initial upload","package":"vbs_movement.vba.gz","4":"vbs_movement.vba.gz","src_id":"17715","5":"17715","creation_date":"1333534058","6":"1333534058"}]},"4002":{"script_id":"4002","0":"4002","script_name":"vim_movement","1":"vim_movement","script_type":"ftplugin","2":"ftplugin","summary":"Movement over Vim functions with ]m etc. ","3":"Movement over Vim functions with ]m etc. ","description":"DESCRIPTION\r\nThis filetype plugin provides movement commands and text objects for Vim\r\nfunctions.\r\nThis is duplicated from $VIMRUNTIME\/ftplugin\/vim.vim, using the (IMHO) correct\r\nmappings \"move to method\", not \"move to paragraph\".\r\n\r\nUSAGE\r\n                        Move around Vim functions:\r\n]m                      Go to [count] next start of a function.\r\n]M                      Go to [count] next end of a function.\r\n[m                      Go to [count] previous start of a function.\r\n[M                      Go to [count] previous end of a function.\r\n\r\nim                      \"inner method\" text object, select [count] function contents.\r\nam                      \"a method\" text object, select [count] functions, including\r\n                        the function definition and 'endfunction'.","4":"DESCRIPTION\r\nThis filetype plugin provides movement commands and text objects for Vim\r\nfunctions.\r\nThis is duplicated from $VIMRUNTIME\/ftplugin\/vim.vim, using the (IMHO) correct\r\nmappings \"move to method\", not \"move to paragraph\".\r\n\r\nUSAGE\r\n                        Move around Vim functions:\r\n]m                      Go to [count] next start of a function.\r\n]M                      Go to [count] next end of a function.\r\n[m                      Go to [count] previous start of a function.\r\n[M                      Go to [count] previous end of a function.\r\n\r\nim                      \"inner method\" text object, select [count] function contents.\r\nam                      \"a method\" text object, select [count] functions, including\r\n                        the function definition and 'endfunction'.","install_details":"DESCRIPTION\r\nThis filetype plugin provides movement commands and text objects for Vim\r\nfunctions.\r\nThis is duplicated from $VIMRUNTIME\/ftplugin\/vim.vim, using the (IMHO) correct\r\nmappings \"move to method\", not \"move to paragraph\".\r\n\r\nUSAGE\r\n\t\t\tMove around Vim functions:\r\n]m\t\t\tGo to [count] next start of a function.\r\n]M\t\t\tGo to [count] next end of a function.\r\n[m\t\t\tGo to [count] previous start of a function.\r\n[M\t\t\tGo to [count] previous end of a function.\r\n\r\nim\t\t\t\"inner method\" text object, select [count] function contents.\r\nam\t\t\t\"a method\" text object, select [count] functions, including\r\n\t\t\tthe function definition and 'endfunction'.","5":"DESCRIPTION\r\nThis filetype plugin provides movement commands and text objects for Vim\r\nfunctions.\r\nThis is duplicated from $VIMRUNTIME\/ftplugin\/vim.vim, using the (IMHO) correct\r\nmappings \"move to method\", not \"move to paragraph\".\r\n\r\nUSAGE\r\n\t\t\tMove around Vim functions:\r\n]m\t\t\tGo to [count] next start of a function.\r\n]M\t\t\tGo to [count] next end of a function.\r\n[m\t\t\tGo to [count] previous start of a function.\r\n[M\t\t\tGo to [count] previous end of a function.\r\n\r\nim\t\t\t\"inner method\" text object, select [count] function contents.\r\nam\t\t\t\"a method\" text object, select [count] functions, including\r\n\t\t\tthe function definition and 'endfunction'.","first_name":"Ingo","6":"Ingo","last_name":"Karkat","7":"Karkat","releases":[{"0":"4002","vim_version":"7.0","1":"7.0","script_version":"1.00","2":"1.00","version_comment":"Initial upload","3":"Initial upload","package":"vim_movement.vba.gz","4":"vim_movement.vba.gz","src_id":"17714","5":"17714","creation_date":"1333533942","6":"1333533942"}]},"4000":{"script_id":"4000","0":"4000","script_name":"Clam","1":"Clam","script_type":"utility","2":"utility","summary":"A lightweight plugin for working with shell commands.","3":"A lightweight plugin for working with shell commands.","description":"Clam is a lightweight plugin for working with shell commands.\r\n\r\nRead the documentation for more info: http:\/\/bit.ly\/HehqTJ","4":"Clam is a lightweight plugin for working with shell commands.\r\n\r\nRead the documentation for more info: http:\/\/bit.ly\/HehqTJ","install_details":"Use Pathogen.","5":"Use Pathogen.","first_name":"Steve","6":"Steve","last_name":"Losh","7":"Losh","releases":[{"0":"4000","vim_version":"7.0","1":"7.0","script_version":"1.4.0","2":"1.4.0","version_comment":"* Added g:clam_winheight and g:clam_winwidth settings (thanks jethrovt).\r\n* Don't highlght ANSI color codes more often than needed (thanks LnL7).\r\n* Improved highlighting for hg status output.\r\n","3":"* Added g:clam_winheight and g:clam_winwidth settings (thanks jethrovt).\r\n* Don't highlght ANSI color codes more often than needed (thanks LnL7).\r\n* Improved highlighting for hg status output.\r\n","package":"clam.zip","4":"clam.zip","src_id":"24750","5":"24750","creation_date":"1479555876","6":"1479555876"},{"0":"4000","vim_version":"7.3","1":"7.3","script_version":"1.3.0","2":"1.3.0","version_comment":"* Added support for custom syntax highlighting for commands (thanks to \u00c3\u009cmit Kablan).\r\n* Preliminary syntax files for pacman and hg commands.\r\n","3":"* Added support for custom syntax highlighting for commands (thanks to \u00c3\u009cmit Kablan).\r\n* Preliminary syntax files for pacman and hg commands.\r\n","package":"clam.zip","4":"clam.zip","src_id":"18568","5":"18568","creation_date":"1347127762","6":"1347127762"},{"0":"4000","vim_version":"7.2","1":"7.2","script_version":"1.2.0","2":"1.2.0","version_comment":"* Added support for ranges in the :Clam command.\r\n* Added the :ClamVisual command.\r\n* Added the g:clam_winpos option.","3":"* Added support for ranges in the :Clam command.\r\n* Added the :ClamVisual command.\r\n* Added the g:clam_winpos option.","package":"clam.zip","4":"clam.zip","src_id":"17764","5":"17764","creation_date":"1334265782","6":"1334265782"},{"0":"4000","vim_version":"7.2","1":"7.2","script_version":"1.1.0","2":"1.1.0","version_comment":"* Added the g:clam_autoreturn setting.","3":"* Added the g:clam_autoreturn setting.","package":"clam.zip","4":"clam.zip","src_id":"17711","5":"17711","creation_date":"1333493331","6":"1333493331"},{"0":"4000","vim_version":"7.2","1":"7.2","script_version":"1.0.0","2":"1.0.0","version_comment":"Initial upload","3":"Initial upload","package":"clam.zip","4":"clam.zip","src_id":"17709","5":"17709","creation_date":"1333484048","6":"1333484048"}]},"3999":{"script_id":"3999","0":"3999","script_name":"Ayumi","1":"Ayumi","script_type":"color scheme","2":"color scheme","summary":"A color scheme like my favorite singer ayumi with colors defined by HighlightTag","3":"A color scheme like my favorite singer ayumi with colors defined by HighlightTag","description":"A color scheme for vim. The color style just like my favorite singer ayumi-hamasiki. It also support colors defined by HighlightTag plugin like bandit.vim.\r\ngit responsity: https:\/\/github.com\/lorry-lee\/vim-ayumi\r\n\r\nScreenShot: https:\/\/github.com\/lorry-lee\/vim-ayumi\/raw\/master\/screenshot\/ayumi.jpg","4":"A color scheme for vim. The color style just like my favorite singer ayumi-hamasiki. It also support colors defined by HighlightTag plugin like bandit.vim.\r\ngit responsity: https:\/\/github.com\/lorry-lee\/vim-ayumi\r\n\r\nScreenShot: https:\/\/github.com\/lorry-lee\/vim-ayumi\/raw\/master\/screenshot\/ayumi.jpg","install_details":"Put the ayumi.vim in your colors folder.","5":"Put the ayumi.vim in your colors folder.","first_name":"lorry","6":"lorry","last_name":"lee","7":"lee","releases":[{"0":"3999","vim_version":"7.0","1":"7.0","script_version":"1.0.0","2":"1.0.0","version_comment":"Initial upload","3":"Initial upload","package":"ayumi.vim","4":"ayumi.vim","src_id":"17705","5":"17705","creation_date":"1333382697","6":"1333382697"}]},"3998":{"script_id":"3998","0":"3998","script_name":"paredit.vim","1":"paredit.vim","script_type":"utility","2":"utility","summary":"Paredit Mode: Structured Editing of Lisp S-expressions","3":"Paredit Mode: Structured Editing of Lisp S-expressions","description":"Paredit performs structured editing of Lisp S-expressions in Vim. Paredit.vim is similar to paredit.el for Emacs. Paredit Mode tries to maintain the balanced state of matched characters (parenthesis marks, square and curly braces, double quotes). Matched characters are inserted and removed in pairs, also when working with a block of text (well, mostly). Paredit also implements many paredit.el s-expression handling functions, like Split\/Join\/Wrap\/Splice\/Raise. Slurpage and Barfage known from Emacs is also possible but in a different fashion: you don't move the list element in or out of the list, rather you move the opening or closing parenthesis over the element or sub-list.\r\n\r\nParedit.vim is also part of the Slimv plugin (http:\/\/www.vim.org\/scripts\/script.php?script_id=2531). Slimv is a SWANK client for Vim, similarly to SLIME for Emacs. Paredit.vim is extracted from Slimv for users who want to use a different SWANK client or don't need a SWANK client at all. In case you need structured editing together with the SWANK functionality then please install Slimv instead, you don't need to additionally install Paredit.\r\n\r\nFor more information see the included documentation.","4":"Paredit performs structured editing of Lisp S-expressions in Vim. Paredit.vim is similar to paredit.el for Emacs. Paredit Mode tries to maintain the balanced state of matched characters (parenthesis marks, square and curly braces, double quotes). Matched characters are inserted and removed in pairs, also when working with a block of text (well, mostly). Paredit also implements many paredit.el s-expression handling functions, like Split\/Join\/Wrap\/Splice\/Raise. Slurpage and Barfage known from Emacs is also possible but in a different fashion: you don't move the list element in or out of the list, rather you move the opening or closing parenthesis over the element or sub-list.\r\n\r\nParedit.vim is also part of the Slimv plugin (http:\/\/www.vim.org\/scripts\/script.php?script_id=2531). Slimv is a SWANK client for Vim, similarly to SLIME for Emacs. Paredit.vim is extracted from Slimv for users who want to use a different SWANK client or don't need a SWANK client at all. In case you need structured editing together with the SWANK functionality then please install Slimv instead, you don't need to additionally install Paredit.\r\n\r\nFor more information see the included documentation.","install_details":"The plugin is installed the usual way: extract the zip archive into your vimfiles or runtime directory.\r\nPlease note that Paredit version numbers follow the Slimv versioning because paredit.vim is also part of Slimv.\r\n\r\nSee the included documentation for customization instructions.","5":"The plugin is installed the usual way: extract the zip archive into your vimfiles or runtime directory.\r\nPlease note that Paredit version numbers follow the Slimv versioning because paredit.vim is also part of Slimv.\r\n\r\nSee the included documentation for customization instructions.","first_name":"Tamas","6":"Tamas","last_name":"Kovacs","7":"Kovacs","releases":[{"0":"3998","vim_version":"7.0","1":"7.0","script_version":"0.9.13","2":"0.9.13","version_comment":"Always leave cursor to opening char's pos after wrapping selection.\r\nFix possible cursor move problem caused by &indentexpr when using the c operator.\r\nBugfix: 2 keymaps assumed g:paredit_leader is identical to ','.\r\nFix for paredit 'x' and 'X' when clipboard=unnamed.\r\nAdded support for hy.\r\nUse <Leader> instead of mapleader.\r\nEnhanced detection of forms balanced state.\r\nUnescaped square brackets in balance detection.\r\nBugfix: pressing <Tab> (for completion) followed by ')'.\r\nRemove invalid uses of `call`.\r\nFixed problem with 'x' and 'X' commands when erasing multi-byte unicode character.\r\nFix Paredit burfing (by moving parens left or right) when there are stings as elements.\r\nAdded paredit support for shen language.\r\nDo not skip parens after \\\\ when searching for pairs.","3":"Always leave cursor to opening char's pos after wrapping selection.\r\nFix possible cursor move problem caused by &indentexpr when using the c operator.\r\nBugfix: 2 keymaps assumed g:paredit_leader is identical to ','.\r\nFix for paredit 'x' and 'X' when clipboard=unnamed.\r\nAdded support for hy.\r\nUse <Leader> instead of mapleader.\r\nEnhanced detection of forms balanced state.\r\nUnescaped square brackets in balance detection.\r\nBugfix: pressing <Tab> (for completion) followed by ')'.\r\nRemove invalid uses of `call`.\r\nFixed problem with 'x' and 'X' commands when erasing multi-byte unicode character.\r\nFix Paredit burfing (by moving parens left or right) when there are stings as elements.\r\nAdded paredit support for shen language.\r\nDo not skip parens after \\\\ when searching for pairs.","package":"paredit0913.zip","4":"paredit0913.zip","src_id":"25042","5":"25042","creation_date":"1489937622","6":"1489937622"},{"0":"3998","vim_version":"7.0","1":"7.0","script_version":"0.9.12","2":"0.9.12","version_comment":"Add Racket support for delimiter '[]' and '{}' (by Jimmy Lu).\r\nFixed ,< and ,> when 'whichwrap' contains 'h' and 'l'.","3":"Add Racket support for delimiter '[]' and '{}' (by Jimmy Lu).\r\nFixed ,< and ,> when 'whichwrap' contains 'h' and 'l'.","package":"paredit0912.zip","4":"paredit0912.zip","src_id":"21254","5":"21254","creation_date":"1388314869","6":"1388314869"},{"0":"3998","vim_version":"7.0","1":"7.0","script_version":"0.9.11","2":"0.9.11","version_comment":"Added options g:paredit_disable_clojure, g:paredit_disable_lisp, g:paredit_disable_scheme. Added repeat.vim support to many Paredit modification actions (by Logan Campbell). Returning cursor to start position after \" wrap (by Logan Campbell). Do not insert newline if item is selected in completion popup menu by pressing <CR>. Delete into the \"*\" register when option clipboard=unnamed. Handle #\"\" regexp syntax definition also when searching for paren matches. Bugfixes: Wrap accomodates strings (thanks to Colin Jones). Don't move cursor for v) when selection mode is inclusive (by John Szakmeister).","3":"Added options g:paredit_disable_clojure, g:paredit_disable_lisp, g:paredit_disable_scheme. Added repeat.vim support to many Paredit modification actions (by Logan Campbell). Returning cursor to start position after \" wrap (by Logan Campbell). Do not insert newline if item is selected in completion popup menu by pressing <CR>. Delete into the \"*\" register when option clipboard=unnamed. Handle #\"\" regexp syntax definition also when searching for paren matches. Bugfixes: Wrap accomodates strings (thanks to Colin Jones). Don't move cursor for v) when selection mode is inclusive (by John Szakmeister).","package":"paredit0911.zip","4":"paredit0911.zip","src_id":"20778","5":"20778","creation_date":"1378761878","6":"1378761878"},{"0":"3998","vim_version":"7.0","1":"7.0","script_version":"0.9.10","2":"0.9.10","version_comment":"Paredit initialization on filetype instead of filename extension. Do not permanently set 'iskeyword'. Added '^' macro prefix. Treat #_(...) type of clojure comments as regular forms. Handle VimClojure's #\"\" regexp syntax definition. Bugfixes: 'cc', 'Vc' did not delete line. 'd', 'c', 'vc', 'cW' cursor positioning problems. 'C' extra whitespace and trailing \". Reset indent after 'cc'. 'dd', ',>' EOL problem. Indentation when 'indentexpr' takes no argument (thanks to Tim Pope). Keep cursor inside \"\" when deleting over trailing \" via 'cW', 'C', etc. Use &ft instead of SlimvGetFiletype().","3":"Paredit initialization on filetype instead of filename extension. Do not permanently set 'iskeyword'. Added '^' macro prefix. Treat #_(...) type of clojure comments as regular forms. Handle VimClojure's #\"\" regexp syntax definition. Bugfixes: 'cc', 'Vc' did not delete line. 'd', 'c', 'vc', 'cW' cursor positioning problems. 'C' extra whitespace and trailing \". Reset indent after 'cc'. 'dd', ',>' EOL problem. Indentation when 'indentexpr' takes no argument (thanks to Tim Pope). Keep cursor inside \"\" when deleting over trailing \" via 'cW', 'C', etc. Use &ft instead of SlimvGetFiletype().","package":"paredit0910.zip","4":"paredit0910.zip","src_id":"19751","5":"19751","creation_date":"1364923655","6":"1364923655"},{"0":"3998","vim_version":"7.0","1":"7.0","script_version":"0.9.9","2":"0.9.9","version_comment":"Handle [] and {} delimiters in Scheme like in Clojure. Ignore (, [, or { when preceded by \\.","3":"Handle [] and {} delimiters in Scheme like in Clojure. Ignore (, [, or { when preceded by \\.","package":"paredit099.zip","4":"paredit099.zip","src_id":"19001","5":"19001","creation_date":"1353400425","6":"1353400425"},{"0":"3998","vim_version":"7.0","1":"7.0","script_version":"0.9.8","2":"0.9.8","version_comment":"Delete empty lines when re-gathering Electric Returns. Special handling of cw, cb, ciw, caw supporting repeat ('.'). Bugfixes: PareditToggle ckecks if buffer was registered for Paredit. Electric Return re-gathering at end of line with no virtualedit. Extra character at the end of selection using 'v('. Paredit 'x' at end of line when 'whichwrap' includes h,l. Paredit Wrap when line ends in a multibyte character (thanks to Sung Pae).","3":"Delete empty lines when re-gathering Electric Returns. Special handling of cw, cb, ciw, caw supporting repeat ('.'). Bugfixes: PareditToggle ckecks if buffer was registered for Paredit. Electric Return re-gathering at end of line with no virtualedit. Extra character at the end of selection using 'v('. Paredit 'x' at end of line when 'whichwrap' includes h,l. Paredit Wrap when line ends in a multibyte character (thanks to Sung Pae).","package":"paredit098.zip","4":"paredit098.zip","src_id":"18426","5":"18426","creation_date":"1345307046","6":"1345307046"},{"0":"3998","vim_version":"7.0","1":"7.0","script_version":"0.9.7","2":"0.9.7","version_comment":"Identify VimClojure REPL prompt position (thanks to David Greenberg). Added <leader><Up> for Splice-killing-backward, <leader><Down> for Splice-killing-forward, <leader>I for Raise. Added 'Electric Return' feature and new option g:paredit_electric_return.","3":"Identify VimClojure REPL prompt position (thanks to David Greenberg). Added <leader><Up> for Splice-killing-backward, <leader><Down> for Splice-killing-forward, <leader>I for Raise. Added 'Electric Return' feature and new option g:paredit_electric_return.","package":"paredit097.zip","4":"paredit097.zip","src_id":"18063","5":"18063","creation_date":"1338321567","6":"1338321567"},{"0":"3998","vim_version":"7.0","1":"7.0","script_version":"0.9.6","2":"0.9.6","version_comment":"Initial upload","3":"Initial upload","package":"paredit096.zip","4":"paredit096.zip","src_id":"17699","5":"17699","creation_date":"1333288815","6":"1333288815"}]},"3997":{"script_id":"3997","0":"3997","script_name":"removed","1":"removed","script_type":"utility","2":"utility","summary":" ","3":" ","description":" ","4":" ","install_details":" ","5":" ","first_name":"David","6":"David","last_name":"B\u00c3\u00bcrgin","7":"B\u00c3\u00bcrgin","releases":[{"0":"3997","vim_version":"7.0","1":"7.0","script_version":"  ","2":"  ","version_comment":"removed","3":"removed","package":"removed","4":"removed","src_id":"22539","5":"22539","creation_date":"1413654597","6":"1413654597"}]},"3996":{"script_id":"3996","0":"3996","script_name":"portmon","1":"portmon","script_type":"utility","2":"utility","summary":"分析portmon的输出文件","3":"分析portmon的输出文件","description":"提取portmon输出文件中的读写字符，统计读写次数。打开protmon文件，输入:Portmon。需要python3.","4":"提取portmon输出文件中的读写字符，统计读写次数。打开protmon文件，输入:Portmon。需要python3.","install_details":"放到plugin目录下即可。","5":"放到plugin目录下即可。","first_name":"Zhang","6":"Zhang","last_name":"ahu","7":"ahu","releases":[{"0":"3996","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"portmon.vim","4":"portmon.vim","src_id":"17693","5":"17693","creation_date":"1333170048","6":"1333170048"}]},"3995":{"script_id":"3995","0":"3995","script_name":"vroom","1":"vroom","script_type":"utility","2":"utility","summary":"Helps you run your Ruby tests","3":"Helps you run your Ruby tests","description":"Vroom is a plugin for running you Ruby tests, specs, and features. It allows you to speed up your development since you don't have to jump around to different windows or tabs.\r\n\r\nIf you're hacking away on your awesome Ruby app, and you open your spec, you can easily run the whole file by hitting <Leader>r, or nearest test with <Leader>R. This is then remembered, so if you switch back to your code, you can then hit <Leader>r again and that last test will be run.","4":"Vroom is a plugin for running you Ruby tests, specs, and features. It allows you to speed up your development since you don't have to jump around to different windows or tabs.\r\n\r\nIf you're hacking away on your awesome Ruby app, and you open your spec, you can easily run the whole file by hitting <Leader>r, or nearest test with <Leader>R. This is then remembered, so if you switch back to your code, you can then hit <Leader>r again and that last test will be run.","install_details":"","5":"","first_name":"Mike","6":"Mike","last_name":"Skalnik","7":"Skalnik","releases":[{"0":"3995","vim_version":"7.0","1":"7.0","script_version":"1.0.2","2":"1.0.2","version_comment":"* Support configuration of cucumber runner\r\n* Can skip `bundle exec` if not requiring 'spec_helper'\r\n","3":"* Support configuration of cucumber runner\r\n* Can skip `bundle exec` if not requiring 'spec_helper'\r\n","package":"skalnik-vim-vroom-1.0.2-0-gce0e6c8.zip","4":"skalnik-vim-vroom-1.0.2-0-gce0e6c8.zip","src_id":"17769","5":"17769","creation_date":"1334372203","6":"1334372203"},{"0":"3995","vim_version":"7.0","1":"7.0","script_version":"1.0.1","2":"1.0.1","version_comment":"Initial upload","3":"Initial upload","package":"skalnik-vim-vroom-1.0.1-0-g7b83254.zip","4":"skalnik-vim-vroom-1.0.1-0-g7b83254.zip","src_id":"17692","5":"17692","creation_date":"1333156193","6":"1333156193"}]},"3994":{"script_id":"3994","0":"3994","script_name":"instant-markdown.vim","1":"instant-markdown.vim","script_type":"utility","2":"utility","summary":"Real-time Markdown previews from Vim!","3":"Real-time Markdown previews from Vim!","description":"Want to instantly preview finnicky markdown files, but don't want to leave your favorite editor, or have to do it in some crappy browser textarea? vim-instant-markdown is your friend! When you open a markdown file in vim, a browser window will open which shows the compiled markdown in real-time, and closes once you close the file in vim.\r\n\r\nAs a bonus, github-flavored-markdown is supported, and styles used while previewing are the same as those github uses!\r\n\r\nSupported platforms: OSX and Unix\/Linuxes\r\n\r\nTo file bugs, feature requests, send patches, or to simply follow the development of instant-markdown, visit its project page at https:\/\/github.com\/suan\/vim-instant-markdown","4":"Want to instantly preview finnicky markdown files, but don't want to leave your favorite editor, or have to do it in some crappy browser textarea? vim-instant-markdown is your friend! When you open a markdown file in vim, a browser window will open which shows the compiled markdown in real-time, and closes once you close the file in vim.\r\n\r\nAs a bonus, github-flavored-markdown is supported, and styles used while previewing are the same as those github uses!\r\n\r\nSupported platforms: OSX and Unix\/Linuxes\r\n\r\nTo file bugs, feature requests, send patches, or to simply follow the development of instant-markdown, visit its project page at https:\/\/github.com\/suan\/vim-instant-markdown","install_details":"You first need to have node.js with npm installed.\r\n\r\n[sudo] npm -g install instant-markdown-d\r\n\r\nIf you're using Linux, the xdg-utils package needs to be installed.\r\n\r\nDownload the script into ~\/.vim\/plugin\r\n\r\n\r\nConfiguration\r\n-------------\r\nBy default, vim-instant-markdown will update the display in realtime.  If that taxes your system too much, you can specify\r\n    let g:instant_markdown_slow = 1\r\nbefore loading the plugin (for example place that in your `~\/.vimrc`). This will cause vim-instant-markdown to only refresh on the following events:\r\n- No keys have been pressed for a while\r\n- A while after you leave insert mode\r\n- You save the file being edited\r\n\r\nBy default, vim-instant-markdown will automatically launch the preview window when you open a markdown file. If you want to manually control this behavior, you can specify\r\n    let g:instant_markdown_autostart = 0\r\nin your .vimrc. You can then manually trigger preview via the command :InstantMarkdownPreview. This command is only available inside markdown buffers and when the autostart option is turned off.","5":"You first need to have node.js with npm installed.\r\n\r\n[sudo] npm -g install instant-markdown-d\r\n\r\nIf you're using Linux, the xdg-utils package needs to be installed.\r\n\r\nDownload the script into ~\/.vim\/plugin\r\n\r\n\r\nConfiguration\r\n-------------\r\nBy default, vim-instant-markdown will update the display in realtime.  If that taxes your system too much, you can specify\r\n    let g:instant_markdown_slow = 1\r\nbefore loading the plugin (for example place that in your `~\/.vimrc`). This will cause vim-instant-markdown to only refresh on the following events:\r\n- No keys have been pressed for a while\r\n- A while after you leave insert mode\r\n- You save the file being edited\r\n\r\nBy default, vim-instant-markdown will automatically launch the preview window when you open a markdown file. If you want to manually control this behavior, you can specify\r\n    let g:instant_markdown_autostart = 0\r\nin your .vimrc. You can then manually trigger preview via the command :InstantMarkdownPreview. This command is only available inside markdown buffers and when the autostart option is turned off.","first_name":"Suan","6":"Suan","last_name":"Yeo","7":"Yeo","releases":[{"0":"3994","vim_version":"7.3","1":"7.3","script_version":"0.0.7","2":"0.0.7","version_comment":"### 0.0.7 (10-31-2013)\r\nthanks to @terryma!\r\n\r\n- Added option to only start previewing markdown on demand","3":"### 0.0.7 (10-31-2013)\r\nthanks to @terryma!\r\n\r\n- Added option to only start previewing markdown on demand","package":"instant-markdown.vim","4":"instant-markdown.vim","src_id":"20987","5":"20987","creation_date":"1383224423","6":"1383224423"},{"0":"3994","vim_version":"7.3","1":"7.3","script_version":"0.0.5","2":"0.0.5","version_comment":"### 0.0.5 (12-05-2012)\r\nThese changes are _also_ courtesy of @chreekat!\r\n\r\n- Plugin no longer breaks vim mouse scrolling\r\n- No longer errors upon opening an empty markdown file\r\n- `instant_markdown_slow` option to update preview less frequently","3":"### 0.0.5 (12-05-2012)\r\nThese changes are _also_ courtesy of @chreekat!\r\n\r\n- Plugin no longer breaks vim mouse scrolling\r\n- No longer errors upon opening an empty markdown file\r\n- `instant_markdown_slow` option to update preview less frequently","package":"instant-markdown.vim","4":"instant-markdown.vim","src_id":"19120","5":"19120","creation_date":"1354777326","6":"1354777326"},{"0":"3994","vim_version":"7.3","1":"7.3","script_version":"0.0.4","2":"0.0.4","version_comment":"### 0.0.3 (04-26-2012)\r\nSome changes for this release were made in the backend. Do `[sudo] npm -g update instant-markdown-d` to get them.\r\n\r\n- Delay starting the `instant-markdown-d` server. This fixed the plugin for a few people who were getting empty browser windows.\r\n- Display a message with configuration instructions when the preview window can't be closed due to Firefox restrictions.\r\n\r\n### 0.0.4 (12-05-2012)\r\nAll these changes courtesy of @chreekat, THANKS!\r\n\r\n- Is now an `after\/ftplugin` plugin. Markdown filetype detection is left to Vim itself, or other plugins.\r\n- Behavior when multiple markdown files are open has been improved\r\n- No more weird characters taking over the status\/command bar while editing\r\n- Internals have been completely rewritten and are much more cleaner and adhere to vim script best practices","3":"### 0.0.3 (04-26-2012)\r\nSome changes for this release were made in the backend. Do `[sudo] npm -g update instant-markdown-d` to get them.\r\n\r\n- Delay starting the `instant-markdown-d` server. This fixed the plugin for a few people who were getting empty browser windows.\r\n- Display a message with configuration instructions when the preview window can't be closed due to Firefox restrictions.\r\n\r\n### 0.0.4 (12-05-2012)\r\nAll these changes courtesy of @chreekat, THANKS!\r\n\r\n- Is now an `after\/ftplugin` plugin. Markdown filetype detection is left to Vim itself, or other plugins.\r\n- Behavior when multiple markdown files are open has been improved\r\n- No more weird characters taking over the status\/command bar while editing\r\n- Internals have been completely rewritten and are much more cleaner and adhere to vim script best practices","package":"instant-markdown.vim","4":"instant-markdown.vim","src_id":"19116","5":"19116","creation_date":"1354691086","6":"1354691086"},{"0":"3994","vim_version":"7.0","1":"7.0","script_version":"0.0.2","2":"0.0.2","version_comment":"Initial upload","3":"Initial upload","package":"instant-markdown.vim","4":"instant-markdown.vim","src_id":"17688","5":"17688","creation_date":"1332990172","6":"1332990172"}]},"3993":{"script_id":"3993","0":"3993","script_name":"gitvimrc.vim","1":"gitvimrc.vim","script_type":"utility","2":"utility","summary":"Source .vimrc file from git repository's root","3":"Source .vimrc file from git repository's root","description":"When loading a buffer, this script will determine the root of the git repository containing the loaded file, and if it exists, source REPO_ROOT\/.vimrc","4":"When loading a buffer, this script will determine the root of the git repository containing the loaded file, and if it exists, source REPO_ROOT\/.vimrc","install_details":"Source this file in your vimrc.","5":"Source this file in your vimrc.","first_name":"Joel","6":"Joel","last_name":"Nothman","7":"Nothman","releases":[{"0":"3993","vim_version":"7.0","1":"7.0","script_version":"1","2":"1","version_comment":"Initial upload","3":"Initial upload","package":"gitvimrc.vim","4":"gitvimrc.vim","src_id":"17687","5":"17687","creation_date":"1332978314","6":"1332978314"}]},"3992":{"script_id":"3992","0":"3992","script_name":"Sauce","1":"Sauce","script_type":"utility","2":"utility","summary":"Manage multiple vimrc files dynamically","3":"Manage multiple vimrc files dynamically","description":"Sauce is a lightweight manager for multiple vimrc files, which can be used to load different settings for different environments. In short, you can maintain lots of different vim settings files and only load the one(s) you need when you need them.\r\n\r\nThis can be used as a simple project organiser tool. For instance:\r\n\r\n\" Load the MyProject sauce\r\n:Sauce MyProject\r\n\r\nThis \"sauce\" (read: source) can contain anything that you would put in your vimrc, and can be used to override those settings. In this case, it could be used to CD into the project directory, set spaces instead of tabs, open NERDTree, set configuration options for PHPQA tools, etc.\r\n\r\nThere's even autocomplete on the sauce names, so you don't need to remember them :)\r\n\r\nVisit the Github repository page to read more about usage: https:\/\/github.com\/joonty\/vim-sauce\r\n\r\nThe autocomplete won't currently work on Windows, but plans are under way to change this.","4":"Sauce is a lightweight manager for multiple vimrc files, which can be used to load different settings for different environments. In short, you can maintain lots of different vim settings files and only load the one(s) you need when you need them.\r\n\r\nThis can be used as a simple project organiser tool. For instance:\r\n\r\n\" Load the MyProject sauce\r\n:Sauce MyProject\r\n\r\nThis \"sauce\" (read: source) can contain anything that you would put in your vimrc, and can be used to override those settings. In this case, it could be used to CD into the project directory, set spaces instead of tabs, open NERDTree, set configuration options for PHPQA tools, etc.\r\n\r\nThere's even autocomplete on the sauce names, so you don't need to remember them :)\r\n\r\nVisit the Github repository page to read more about usage: https:\/\/github.com\/joonty\/vim-sauce\r\n\r\nThe autocomplete won't currently work on Windows, but plans are under way to change this.","install_details":"If you're using Vundle, just add:\r\n\r\nBundle 'joonty\/vim-sauce.git'\r\n\r\nTo your vimrc file, then install as normal. Otherwise, extract the files in each folder to the corresponding folder in your \".vim\/\" directory.","5":"If you're using Vundle, just add:\r\n\r\nBundle 'joonty\/vim-sauce.git'\r\n\r\nTo your vimrc file, then install as normal. Otherwise, extract the files in each folder to the corresponding folder in your \".vim\/\" directory.","first_name":"Jon","6":"Jon","last_name":"Cairns","7":"Cairns","releases":[{"0":"3992","vim_version":"7.0","1":"7.0","script_version":"0.3.0","2":"0.3.0","version_comment":"* Add :SauceRename command\r\n* Allow usage of custom skeletons (thanks @UmkaDK)","3":"* Add :SauceRename command\r\n* Allow usage of custom skeletons (thanks @UmkaDK)","package":"vim-sauce-0.3.0.tgz","4":"vim-sauce-0.3.0.tgz","src_id":"20444","5":"20444","creation_date":"1372258897","6":"1372258897"},{"0":"3992","vim_version":"7.0","1":"7.0","script_version":"0.2","2":"0.2","version_comment":"You can now copy an existing Sauce when creating a new one, for copying common configurations.\r\n\r\nAlso, an error no longer appears when using on Windows. However, the autocomplete doesn't yet work.","3":"You can now copy an existing Sauce when creating a new one, for copying common configurations.\r\n\r\nAlso, an error no longer appears when using on Windows. However, the autocomplete doesn't yet work.","package":"vim-sauce-0.2.tgz","4":"vim-sauce-0.2.tgz","src_id":"18012","5":"18012","creation_date":"1337610560","6":"1337610560"},{"0":"3992","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"vim-sauce.tgz","4":"vim-sauce.tgz","src_id":"17685","5":"17685","creation_date":"1332962248","6":"1332962248"}]},"3991":{"script_id":"3991","0":"3991","script_name":"ConflictMotions","1":"ConflictMotions","script_type":"utility","2":"utility","summary":"Motions to and inside SCM conflict markers.","3":"Motions to and inside SCM conflict markers.","description":"DESCRIPTION\r\nThis plugin defines movement commands and text objects to go to and operate on\r\nconflicting lines, as indicated by many revision control systems, like\r\nSubversion, Git, etc. The source code management system inserts conflict\r\nmarkers such as <<<<<<<, =======, and >>>>>>> on merges to indicate that the\r\nautomatic resolution failed; this plugin helps you with locating and resolving\r\nthese conflicts.\r\n\r\nSEE ALSO\r\nTo be alerted to the existence of conflict markers and to visually\r\ndifferentiate the conflicted lines, you can use the highlighting, warnings and\r\ncustom buffer status provided by the companion ConflictDetection.vim plugin\r\n(vimscript #4129).\r\n\r\nRELATED WORKS\r\n- conflict-marker.vim (https:\/\/github.com\/rhysd\/conflict-marker.vim)\r\n  highlights conflicts and provides quite similar motions (utilizing\r\n  matchit.vim for jumps within a conflict), and similar commands to resolve a\r\n  conflict.\r\n- The ConflictToDiff plugin (vimscript #621) can split a (it says CVS, but\r\n  also works for other tools) conflict file back into the two conflicting\r\n  versions and a merge target, and offers commands to merge them.\r\n- unimpaired.vim (vimscript #1590) has (among many other, largely unrelated)\r\n  [n \/ ]n mappings that jump between conflict markers (like [x \/ ]x).\r\n\r\nUSAGE\r\n]x                      Go to [count] next start of a conflict.\r\n]X                      Go to [count] next end of a conflict.\r\n[x                      Go to [count] previous start of a conflict.\r\n[X                      Go to [count] previous end of a conflict.\r\n\r\n]=                      Go to [count] next conflict marker.\r\n[=                      Go to [count] previous conflict marker.\r\n                        Mnemonic: = is in the separator between our and their\r\n                        changes.\r\n\r\nax                      \"a conflict\" text object, select [count] conflicts,\r\n                        including the conflict markers.\r\n\r\na=                      \"a conflict section\" text object, select [count]\r\n                        sections (i.e. either ours, theirs, or base) including\r\n                        the conflict marker above, and in the case of \"theirs\"\r\n                        changes, also the ending conflict marker below.\r\n\r\ni=                      \"inner conflict section\" text object, select current\r\n                        section (i.e. either ours, theirs, or base) without\r\n                        the surrounding conflict markers.\r\n\r\n:ConflictTake           From the conflict the cursor is in, remove the markers\r\n                        and keep the section the cursor is inside.\r\n:ConflictTake [none this ours base theirs both all query] [...]\r\n:ConflictTake [-.<|>+*?][...]\r\n                        From the conflict the cursor is in, remove the markers\r\n                        and keep the passed section(s) (in the order they are\r\n                        specified).\r\n                            none, - = delete the entire conflict\r\n                            both    = ours theirs               (+ = <>)\r\n                            all     = ours [base] theirs        (* = <|>)\r\n                            query   = ask which sections to take\r\n                        Note: | must be escaped as \\|.\r\n:[range]ConflictTake [none this ours base theirs both all range query] [...]\r\n:[range]ConflictTake [-.<|>+*:?][...]\r\n                        When the cursor is inside a conflict, and the [range]\r\n                        covers part of that conflict:\r\n                        From the conflict the cursor is in, remove the markers\r\n                        and keep the passed range (without contained markers)\r\n                        (and any passed sections in addition; include the\r\n                        \"range\" \/ \":\" argument to put the range somewhere\r\n                        other than the end).\r\n                        Otherwise, when a large range (like %) is passed:\r\n                        For each conflict that starts in [range], remove the\r\n                        markers and keep the passed section(s) \/ ask which\r\n                        section(s) should be kept. You can answer the question\r\n                        with either the symbol or the choice's starting\r\n                        letter. An uppercase letter will apply the choice to\r\n                        all following conflicts.\r\n\r\n<Leader>xd              Delete the entire current conflict \/ all conflicts in\r\n                        the selection.\r\n<Leader>x<              Keep our changes, delete the rest.\r\n<Leader>x|              Keep the change base, delete the rest.\r\n<Leader>x>              Keep their changes, delete the rest.\r\n\r\n<Leader>x.              Keep the current conflict section, delete the rest.\r\n{Visual}<Leader>x.      From the conflict the cursor is in, remove the markers\r\n                        and keep the selected lines (without contained markers).\r\n                        For each conflict that starts in the selection, remove\r\n                        the markers and ask which section(s) should be kept.","4":"DESCRIPTION\r\nThis plugin defines movement commands and text objects to go to and operate on\r\nconflicting lines, as indicated by many revision control systems, like\r\nSubversion, Git, etc. The source code management system inserts conflict\r\nmarkers such as <<<<<<<, =======, and >>>>>>> on merges to indicate that the\r\nautomatic resolution failed; this plugin helps you with locating and resolving\r\nthese conflicts.\r\n\r\nSEE ALSO\r\nTo be alerted to the existence of conflict markers and to visually\r\ndifferentiate the conflicted lines, you can use the highlighting, warnings and\r\ncustom buffer status provided by the companion ConflictDetection.vim plugin\r\n(vimscript #4129).\r\n\r\nRELATED WORKS\r\n- conflict-marker.vim (https:\/\/github.com\/rhysd\/conflict-marker.vim)\r\n  highlights conflicts and provides quite similar motions (utilizing\r\n  matchit.vim for jumps within a conflict), and similar commands to resolve a\r\n  conflict.\r\n- The ConflictToDiff plugin (vimscript #621) can split a (it says CVS, but\r\n  also works for other tools) conflict file back into the two conflicting\r\n  versions and a merge target, and offers commands to merge them.\r\n- unimpaired.vim (vimscript #1590) has (among many other, largely unrelated)\r\n  [n \/ ]n mappings that jump between conflict markers (like [x \/ ]x).\r\n\r\nUSAGE\r\n]x                      Go to [count] next start of a conflict.\r\n]X                      Go to [count] next end of a conflict.\r\n[x                      Go to [count] previous start of a conflict.\r\n[X                      Go to [count] previous end of a conflict.\r\n\r\n]=                      Go to [count] next conflict marker.\r\n[=                      Go to [count] previous conflict marker.\r\n                        Mnemonic: = is in the separator between our and their\r\n                        changes.\r\n\r\nax                      \"a conflict\" text object, select [count] conflicts,\r\n                        including the conflict markers.\r\n\r\na=                      \"a conflict section\" text object, select [count]\r\n                        sections (i.e. either ours, theirs, or base) including\r\n                        the conflict marker above, and in the case of \"theirs\"\r\n                        changes, also the ending conflict marker below.\r\n\r\ni=                      \"inner conflict section\" text object, select current\r\n                        section (i.e. either ours, theirs, or base) without\r\n                        the surrounding conflict markers.\r\n\r\n:ConflictTake           From the conflict the cursor is in, remove the markers\r\n                        and keep the section the cursor is inside.\r\n:ConflictTake [none this ours base theirs both all query] [...]\r\n:ConflictTake [-.<|>+*?][...]\r\n                        From the conflict the cursor is in, remove the markers\r\n                        and keep the passed section(s) (in the order they are\r\n                        specified).\r\n                            none, - = delete the entire conflict\r\n                            both    = ours theirs               (+ = <>)\r\n                            all     = ours [base] theirs        (* = <|>)\r\n                            query   = ask which sections to take\r\n                        Note: | must be escaped as \\|.\r\n:[range]ConflictTake [none this ours base theirs both all range query] [...]\r\n:[range]ConflictTake [-.<|>+*:?][...]\r\n                        When the cursor is inside a conflict, and the [range]\r\n                        covers part of that conflict:\r\n                        From the conflict the cursor is in, remove the markers\r\n                        and keep the passed range (without contained markers)\r\n                        (and any passed sections in addition; include the\r\n                        \"range\" \/ \":\" argument to put the range somewhere\r\n                        other than the end).\r\n                        Otherwise, when a large range (like %) is passed:\r\n                        For each conflict that starts in [range], remove the\r\n                        markers and keep the passed section(s) \/ ask which\r\n                        section(s) should be kept. You can answer the question\r\n                        with either the symbol or the choice's starting\r\n                        letter. An uppercase letter will apply the choice to\r\n                        all following conflicts.\r\n\r\n<Leader>xd              Delete the entire current conflict \/ all conflicts in\r\n                        the selection.\r\n<Leader>x<              Keep our changes, delete the rest.\r\n<Leader>x|              Keep the change base, delete the rest.\r\n<Leader>x>              Keep their changes, delete the rest.\r\n\r\n<Leader>x.              Keep the current conflict section, delete the rest.\r\n{Visual}<Leader>x.      From the conflict the cursor is in, remove the markers\r\n                        and keep the selected lines (without contained markers).\r\n                        For each conflict that starts in the selection, remove\r\n                        the markers and ask which section(s) should be kept.","install_details":"INSTALLATION\r\nThe code is hosted in a Git repo at\r\n    https:\/\/github.com\/inkarkat\/vim-ConflictMotions\r\nYou can use your favorite plugin manager, or \"git clone\" into a directory used\r\nfor Vim packages. Releases are on the \"stable\" branch, the latest unstable\r\ndevelopment snapshot on \"master\".\r\n\r\nThis script is also packaged as a vimball. If you have the \"gunzip\"\r\ndecompressor in your PATH, simply edit the *.vmb.gz package in Vim; otherwise,\r\ndecompress the archive first, e.g. using WinZip. Inside Vim, install by\r\nsourcing the vimball or via the :UseVimball command.\r\n    vim ConflictMotions*.vmb.gz\r\n    :so %\r\nTo uninstall, use the :RmVimball command.\r\n\r\nDEPENDENCIES\r\n- Requires Vim 7.0 or higher.\r\n- Requires the CountJump plugin (vimscript #3130).\r\n- Requires the ingo-library.vim plugin (vimscript #4433), version 1.029 or\r\n  higher.\r\n- repeat.vim (vimscript #2136) plugin (optional)\r\n- visualrepeat.vim (vimscript #3848) plugin (optional)\r\n\r\nCONFIGURATION\r\nFor a permanent configuration, put the following commands into your vimrc:\r\n\r\nTo change the default motion mappings, use:\r\n    let g:ConflictMotions_ConflictBeginMapping = 'x'\r\n    let g:ConflictMotions_ConflictEndMapping = 'X'\r\n    let g:ConflictMotions_MarkerMapping = '='\r\nTo also change the [ \/ ] prefix to something else, follow the instructions for\r\nCountJump-remap-motions. (This requires CountJump 1.60.)\r\n\r\nTo change the default text object mappings, use:\r\n    let g:ConflictMotions_ConflictMapping = 'x'\r\n    let g:ConflictMotions_SectionMapping = '='\r\nTo also change the i \/ a prefix to something else, follow the instructions for\r\nCountJump-remap-text-objects. (This requires CountJump 1.60.)\r\n\r\nIf you don't want the mappings for :ConflictTake:\r\n    let g:ConflictMotions_TakeMappingPrefix = ''\r\nTo redefine the mappings, either clear the prefix and use the\r\n<Plug>(ConflictMotionsTake...) mapping targets, or adapt via the prefix and\r\nmapping configuration, e.g.:\r\n    let g:ConflictMotions_TakeMappingPrefix = '<Leader>='\r\n    let g:ConflictMotions_TakeMappings = [['d', 'None'], ['x', 'This'], ['o', 'Ours'], ['b', 'Base'], ['t', 'Theirs']]","5":"INSTALLATION\r\nThe code is hosted in a Git repo at\r\n    https:\/\/github.com\/inkarkat\/vim-ConflictMotions\r\nYou can use your favorite plugin manager, or \"git clone\" into a directory used\r\nfor Vim packages. Releases are on the \"stable\" branch, the latest unstable\r\ndevelopment snapshot on \"master\".\r\n\r\nThis script is also packaged as a vimball. If you have the \"gunzip\"\r\ndecompressor in your PATH, simply edit the *.vmb.gz package in Vim; otherwise,\r\ndecompress the archive first, e.g. using WinZip. Inside Vim, install by\r\nsourcing the vimball or via the :UseVimball command.\r\n    vim ConflictMotions*.vmb.gz\r\n    :so %\r\nTo uninstall, use the :RmVimball command.\r\n\r\nDEPENDENCIES\r\n- Requires Vim 7.0 or higher.\r\n- Requires the CountJump plugin (vimscript #3130).\r\n- Requires the ingo-library.vim plugin (vimscript #4433), version 1.029 or\r\n  higher.\r\n- repeat.vim (vimscript #2136) plugin (optional)\r\n- visualrepeat.vim (vimscript #3848) plugin (optional)\r\n\r\nCONFIGURATION\r\nFor a permanent configuration, put the following commands into your vimrc:\r\n\r\nTo change the default motion mappings, use:\r\n    let g:ConflictMotions_ConflictBeginMapping = 'x'\r\n    let g:ConflictMotions_ConflictEndMapping = 'X'\r\n    let g:ConflictMotions_MarkerMapping = '='\r\nTo also change the [ \/ ] prefix to something else, follow the instructions for\r\nCountJump-remap-motions. (This requires CountJump 1.60.)\r\n\r\nTo change the default text object mappings, use:\r\n    let g:ConflictMotions_ConflictMapping = 'x'\r\n    let g:ConflictMotions_SectionMapping = '='\r\nTo also change the i \/ a prefix to something else, follow the instructions for\r\nCountJump-remap-text-objects. (This requires CountJump 1.60.)\r\n\r\nIf you don't want the mappings for :ConflictTake:\r\n    let g:ConflictMotions_TakeMappingPrefix = ''\r\nTo redefine the mappings, either clear the prefix and use the\r\n<Plug>(ConflictMotionsTake...) mapping targets, or adapt via the prefix and\r\nmapping configuration, e.g.:\r\n    let g:ConflictMotions_TakeMappingPrefix = '<Leader>='\r\n    let g:ConflictMotions_TakeMappings = [['d', 'None'], ['x', 'This'], ['o', 'Ours'], ['b', 'Base'], ['t', 'Theirs']]","first_name":"Ingo","6":"Ingo","last_name":"Karkat","7":"Karkat","releases":[{"0":"3991","vim_version":"7.0","1":"7.0","script_version":"2.11","2":"2.11","version_comment":"- FIX: Need to convert the passed range into net lines, as we're gonna turn off folding.\r\n- Adapt: :ConflictTake does not recognize that it has no range passed since Vim 8.1.1241. Thanks to lilydjwg for submitting a patch. Need to default -range to -1 and check <count> == -1 instead of <line2>. *** You need to update to ingo-library (vimscript #4433) version 1.029! ***","3":"- FIX: Need to convert the passed range into net lines, as we're gonna turn off folding.\r\n- Adapt: :ConflictTake does not recognize that it has no range passed since Vim 8.1.1241. Thanks to lilydjwg for submitting a patch. Need to default -range to -1 and check <count> == -1 instead of <line2>. *** You need to update to ingo-library (vimscript #4433) version 1.029! ***","package":"ConflictMotions-2.11.vmb.gz","4":"ConflictMotions-2.11.vmb.gz","src_id":"26952","5":"26952","creation_date":"1580675501","6":"1580675501"},{"0":"3991","vim_version":"7.0","1":"7.0","script_version":"2.10","2":"2.10","version_comment":"- ENH: Define both normal and visual mode mappings for all mappings, not the exclusive either-or. The new visual mode mappings will select the corresponding section in all conflicts found in the selected range. (Application on a partially selected conflict is denied by an error since version 2.02.)\r\n- ENH: Enable repeat of all mappings, also (with visualrepeat.vim) across modes. Thanks to Maxim Gonchar for the suggestion.\r\n- Handle folded ranges overlapping the conflicts. Thanks to Maxim Gonchar for reporting this. When querying which conflict sections to keep, open folds so that if possible the entire conflict is visible, but at least the section markers.\r\n- Re-allow combining range inside conflict with section argument, but only for the :ConflictTake command, not the mappings.","3":"- ENH: Define both normal and visual mode mappings for all mappings, not the exclusive either-or. The new visual mode mappings will select the corresponding section in all conflicts found in the selected range. (Application on a partially selected conflict is denied by an error since version 2.02.)\r\n- ENH: Enable repeat of all mappings, also (with visualrepeat.vim) across modes. Thanks to Maxim Gonchar for the suggestion.\r\n- Handle folded ranges overlapping the conflicts. Thanks to Maxim Gonchar for reporting this. When querying which conflict sections to keep, open folds so that if possible the entire conflict is visible, but at least the section markers.\r\n- Re-allow combining range inside conflict with section argument, but only for the :ConflictTake command, not the mappings.","package":"ConflictMotions-2.10.vmb.gz","4":"ConflictMotions-2.10.vmb.gz","src_id":"22226","5":"22226","creation_date":"1405953362","6":"1405953362"},{"0":"3991","vim_version":"7.0","1":"7.0","script_version":"2.02","2":"2.02","version_comment":"- Regression: Version 2.01 introduced a bad offset calculation, potentially resulting in left-over conflicts, e.g. on :%ConflictTake.\r\n- Do not allow combination of a range inside a conflict with a section argument, as the two contradict each other. Print an error instead.","3":"- Regression: Version 2.01 introduced a bad offset calculation, potentially resulting in left-over conflicts, e.g. on :%ConflictTake.\r\n- Do not allow combination of a range inside a conflict with a section argument, as the two contradict each other. Print an error instead.","package":"ConflictMotions-2.02.vmb.gz","4":"ConflictMotions-2.02.vmb.gz","src_id":"22217","5":"22217","creation_date":"1405797035","6":"1405797035"},{"0":"3991","vim_version":"7.0","1":"7.0","script_version":"2.01","2":"2.01","version_comment":"- BUG: \"E16: Invalid range\" error when taking a conflict section of a hunk at the end of the file. Use ingo#lines#PutBefore(). Thanks to Kballard for reporting this on the Vim Tips Wiki and suggesting the fix.\r\n- BUG: Taking conflicts where a single hunk spans the entire buffer adds a blank line. Use ingo#lines#Replace(), which now handles this. Thanks to Kballard for reporting this on the Vim Tips Wiki.\r\n- The CountJump operator-pending mapping will beep when the inner conflict section is empty, but for taking such a section, the beep is unexpected. Detect this special case and skip the CountJump text object then. Thanks to Kballard for reporting this on the Vim Tips Wiki.\r\n- Abort on error of :ConflictTake.\r\n- Use ingo#register#KeepRegisterExecuteOrFunc(). *** You need to update to ingo-library (vimscript #4433) version 1.019! ***","3":"- BUG: \"E16: Invalid range\" error when taking a conflict section of a hunk at the end of the file. Use ingo#lines#PutBefore(). Thanks to Kballard for reporting this on the Vim Tips Wiki and suggesting the fix.\r\n- BUG: Taking conflicts where a single hunk spans the entire buffer adds a blank line. Use ingo#lines#Replace(), which now handles this. Thanks to Kballard for reporting this on the Vim Tips Wiki.\r\n- The CountJump operator-pending mapping will beep when the inner conflict section is empty, but for taking such a section, the beep is unexpected. Detect this special case and skip the CountJump text object then. Thanks to Kballard for reporting this on the Vim Tips Wiki.\r\n- Abort on error of :ConflictTake.\r\n- Use ingo#register#KeepRegisterExecuteOrFunc(). *** You need to update to ingo-library (vimscript #4433) version 1.019! ***","package":"ConflictMotions-2.01.vmb.gz","4":"ConflictMotions-2.01.vmb.gz","src_id":"21967","5":"21967","creation_date":"1401561670","6":"1401561670"},{"0":"3991","vim_version":"7.0","1":"7.0","script_version":"2.00","2":"2.00","version_comment":"- FIX: Don't create the default mapping for <Plug>(ConflictMotionsTakeSelection) in select mode; it should insert a literal <Leader> there.\r\n- Add the :ConflictTake command to resolve a conflict by picking a section(s).\r\n- Add dependency to ingo-library (vimscript #4433).","3":"- FIX: Don't create the default mapping for <Plug>(ConflictMotionsTakeSelection) in select mode; it should insert a literal <Leader> there.\r\n- Add the :ConflictTake command to resolve a conflict by picking a section(s).\r\n- Add dependency to ingo-library (vimscript #4433).","package":"ConflictMotions-2.00.vmb.gz","4":"ConflictMotions-2.00.vmb.gz","src_id":"19902","5":"19902","creation_date":"1366701115","6":"1366701115"},{"0":"3991","vim_version":"7.0","1":"7.0","script_version":"1.10","2":"1.10","version_comment":"The [z \/ ]z mappings disable the built-in mappings for moving over the current open fold. Oops! Change default to [= \/ ]= \/ i= \/ a=. (= as for the characters in the separator between our and their change).","3":"The [z \/ ]z mappings disable the built-in mappings for moving over the current open fold. Oops! Change default to [= \/ ]= \/ i= \/ a=. (= as for the characters in the separator between our and their change).","package":"ConflictMotions-1.10.vmb.gz","4":"ConflictMotions-1.10.vmb.gz","src_id":"18556","5":"18556","creation_date":"1346919695","6":"1346919695"},{"0":"3991","vim_version":"7.0","1":"7.0","script_version":"1.00","2":"1.00","version_comment":"Initial upload","3":"Initial upload","package":"ConflictMotions.vba.gz","4":"ConflictMotions.vba.gz","src_id":"17682","5":"17682","creation_date":"1332934554","6":"1332934554"}]},"3990":{"script_id":"3990","0":"3990","script_name":"TaskMotions","1":"TaskMotions","script_type":"utility","2":"utility","summary":"Motions to task and TODO markers.","3":"Motions to task and TODO markers.","description":"DESCRIPTION\r\nThis plugin defines movement commands to go to a task or TODO marker embedded\r\nin the file, like this:\r\n    \/\/ TODO: Check the return code from the frobnicator.\r\n\r\nRELATED WORKS\r\nTo get a list of all tasks and TODO markers in the current file or project,\r\nyou can use the companion GrepTasks.vim plugin (vimscript #4196).\r\n\r\nUSAGE\r\n]t\t\t\tGo to [count] next start of a task or TODO marker.\r\n[t\t\t\tGo to [count] previous start of a task or TODO marker.","4":"DESCRIPTION\r\nThis plugin defines movement commands to go to a task or TODO marker embedded\r\nin the file, like this:\r\n    \/\/ TODO: Check the return code from the frobnicator.\r\n\r\nRELATED WORKS\r\nTo get a list of all tasks and TODO markers in the current file or project,\r\nyou can use the companion GrepTasks.vim plugin (vimscript #4196).\r\n\r\nUSAGE\r\n]t\t\t\tGo to [count] next start of a task or TODO marker.\r\n[t\t\t\tGo to [count] previous start of a task or TODO marker.","install_details":"INSTALLATION\r\nThis script is packaged as a vimball. If you have the \"gunzip\" decompressor\r\nin your PATH, simply edit the *.vmb.gz package in Vim; otherwise, decompress\r\nthe archive first, e.g. using WinZip. Inside Vim, install by sourcing the\r\nvimball or via the :UseVimball command.\r\n    vim TaskMotions*.vmb.gz\r\n    :so %\r\nTo uninstall, use the :RmVimball command.\r\n\r\nDEPENDENCIES\r\n- Requires Vim 7.0 or higher.\r\n- Requires the CountJump plugin (vimscript #3130), version 1.81 or higher.\r\n\r\nCONFIGURATION\r\nFor a permanent configuration, put the following commands into your vimrc:\r\n\r\nTasks and TODO markers are defined by a regular expression. Change it via:\r\n    let g:TaskMotions_Pattern = '\\<TODO:'\r\n\r\nTo change the default mappings from ]t to ]x, use:\r\n    let g:TaskMotions_Mapping = 'x'\r\nTo also change the [ \/ ] prefix to something else, follow the instructions for\r\nCountJump-remap-motions.","5":"INSTALLATION\r\nThis script is packaged as a vimball. If you have the \"gunzip\" decompressor\r\nin your PATH, simply edit the *.vmb.gz package in Vim; otherwise, decompress\r\nthe archive first, e.g. using WinZip. Inside Vim, install by sourcing the\r\nvimball or via the :UseVimball command.\r\n    vim TaskMotions*.vmb.gz\r\n    :so %\r\nTo uninstall, use the :RmVimball command.\r\n\r\nDEPENDENCIES\r\n- Requires Vim 7.0 or higher.\r\n- Requires the CountJump plugin (vimscript #3130), version 1.81 or higher.\r\n\r\nCONFIGURATION\r\nFor a permanent configuration, put the following commands into your vimrc:\r\n\r\nTasks and TODO markers are defined by a regular expression. Change it via:\r\n    let g:TaskMotions_Pattern = '\\<TODO:'\r\n\r\nTo change the default mappings from ]t to ]x, use:\r\n    let g:TaskMotions_Mapping = 'x'\r\nTo also change the [ \/ ] prefix to something else, follow the instructions for\r\nCountJump-remap-motions.","first_name":"Ingo","6":"Ingo","last_name":"Karkat","7":"Karkat","releases":[{"0":"3990","vim_version":"7.0","1":"7.0","script_version":"1.01","2":"1.01","version_comment":"Wrap around search when 'wrapscan' is set.\r\nThis requires CountJump version 1.81.","3":"Wrap around search when 'wrapscan' is set.\r\nThis requires CountJump version 1.81.","package":"TaskMotions-1.01.vmb.gz","4":"TaskMotions-1.01.vmb.gz","src_id":"18818","5":"18818","creation_date":"1350392798","6":"1350392798"},{"0":"3990","vim_version":"7.0","1":"7.0","script_version":"1.00","2":"1.00","version_comment":"Initial upload.","3":"Initial upload.","package":"TaskMotions.vba.gz","4":"TaskMotions.vba.gz","src_id":"17681","5":"17681","creation_date":"1332934460","6":"1332934460"}]},"3980":{"script_id":"3980","0":"3980","script_name":"phpqa","1":"phpqa","script_type":"utility","2":"utility","summary":"Run PHP QA tools and show highlighted results","3":"Run PHP QA tools and show highlighted results","description":"This is a plugin for Vim that integrates PHP quality checking tools, to allow you to code to a particular standard and easily spot errors and violations.\r\n\r\nIt uses PHP linter to check for syntax errors, integrates with PHP Code Sniffer and PHP Mess Detector to check for coding standard violations, and reads clover code coverage files to mark lines of code that aren't covered by tests. By default, mess detector and code sniffer automatically run when a PHP file is saved, and it can be easily configured to load code coverage markers when a file is opened.\r\n\r\nMore information regarding configuration and usage can be found on the Github repository page: https:\/\/github.com\/joonty\/vim-phpqa","4":"This is a plugin for Vim that integrates PHP quality checking tools, to allow you to code to a particular standard and easily spot errors and violations.\r\n\r\nIt uses PHP linter to check for syntax errors, integrates with PHP Code Sniffer and PHP Mess Detector to check for coding standard violations, and reads clover code coverage files to mark lines of code that aren't covered by tests. By default, mess detector and code sniffer automatically run when a PHP file is saved, and it can be easily configured to load code coverage markers when a file is opened.\r\n\r\nMore information regarding configuration and usage can be found on the Github repository page: https:\/\/github.com\/joonty\/vim-phpqa","install_details":"This is easily installed using Vundle. Just add \"Bundle 'joonty\/vim-phpqa.git'\" to your .vimrc and run \"vim +BundleInstall +qall\".\r\n\r\nOtherwise, the files in each directory in the package should be added to the corresponding directory in your .vim\/ folder.","5":"This is easily installed using Vundle. Just add \"Bundle 'joonty\/vim-phpqa.git'\" to your .vimrc and run \"vim +BundleInstall +qall\".\r\n\r\nOtherwise, the files in each directory in the package should be added to the corresponding directory in your .vim\/ folder.","first_name":"Jon","6":"Jon","last_name":"Cairns","7":"Cairns","releases":[{"0":"3980","vim_version":"7.0","1":"7.0","script_version":"0.7.0","2":"0.7.0","version_comment":"A plethora of changes! Take a look at https:\/\/github.com\/joonty\/vim-phpqa\/issues?q=milestone%3A%22Version+0.7.0%22+is%3Aclosed for a list of issues and pull requests that have gone into this release.","3":"A plethora of changes! Take a look at https:\/\/github.com\/joonty\/vim-phpqa\/issues?q=milestone%3A%22Version+0.7.0%22+is%3Aclosed for a list of issues and pull requests that have gone into this release.","package":"phpqa-0.7.0.tar.gz","4":"phpqa-0.7.0.tar.gz","src_id":"23672","5":"23672","creation_date":"1444898142","6":"1444898142"},{"0":"3980","vim_version":"7.0","1":"7.0","script_version":"0.6","2":"0.6","version_comment":"Improved code coverage efficiency, and option to stop the location list opening automatically after mess detector\/codesniffer violations are found.","3":"Improved code coverage efficiency, and option to stop the location list opening automatically after mess detector\/codesniffer violations are found.","package":"phpqa-0.6.tgz","4":"phpqa-0.6.tgz","src_id":"17935","5":"17935","creation_date":"1336743574","6":"1336743574"},{"0":"3980","vim_version":"7.0","1":"7.0","script_version":"0.5","2":"0.5","version_comment":"Major reworking to vastly improve speed. No longer needs Perl, but code coverage support is supplied by Python.","3":"Major reworking to vastly improve speed. No longer needs Perl, but code coverage support is supplied by Python.","package":"phpqa-0.5.tgz","4":"phpqa-0.5.tgz","src_id":"17909","5":"17909","creation_date":"1336565404","6":"1336565404"},{"0":"3980","vim_version":"7.0","1":"7.0","script_version":"0.4","2":"0.4","version_comment":"Added clover code coverage support, and made everything more configurable.","3":"Added clover code coverage support, and made everything more configurable.","package":"phpqa-0.4.tgz","4":"phpqa-0.4.tgz","src_id":"17684","5":"17684","creation_date":"1332941832","6":"1332941832"},{"0":"3980","vim_version":"7.0","1":"7.0","script_version":"0.3","2":"0.3","version_comment":"Initial upload","3":"Initial upload","package":"phpqa.tgz","4":"phpqa.tgz","src_id":"17664","5":"17664","creation_date":"1332837969","6":"1332837969"}]},"3979":{"script_id":"3979","0":"3979","script_name":"vim-pomodoro","1":"vim-pomodoro","script_type":"utility","2":"utility","summary":"Vim plugin for the Pomdoro time management technique","3":"Vim plugin for the Pomdoro time management technique","description":"vim-pomodoro is a Vim plugin for the Pomodoro time management technique (http:\/\/www.pomodorotechnique.com\/).\r\n\r\nONLY for Linux\/Mac OS X!\r\n\r\nUsage\r\n---------\r\nThe usage of vim-pomodoro is simple. `:PomodoroStart [pomodoro_name]` starts a new pomodoro. The parameter `pomodoro_name` is optional. After a pomodoro ended, a confirmation dialog will remind you to take a break. When the break has ended, another dialog will ask you if you want to start a new pomodoro. Furthermore, the remaining time of a pomodoro can be displayed in the \r\nstatusline of vim.\r\n\r\nIf you do not want vim-pomodoro to use popup windows but text dialogs inside Vim, add `set guioptions+=c` to your `~\/.gvimrc`. Please note that this will *globally* disable popup notification windows in Vim.\r\n\r\nAlso, in addition to the default notifications inside vim, vim-pomodoro allows to add \r\nfurther external notifications, such as sounds, system-notification popups etc.\r\n\r\nConfiguration\r\n-------------------\r\nAdd the following options to your `~\/.vimrc` to configure vim-pomodoro \r\n\r\n        \" Duration of a pomodoro in minutes (default: 25)\r\n        let g:pomodoro_time_work = 25\r\n\r\n        \" Duration of a break in minutes (default: 5)\r\n        let g:pomodoro_time_slack = 5 \r\n\r\n        \" Log completed pomodoros, 0 = False, 1 = True (default: 0)\r\n        let g:pomodoro_do_log = 0 \r\n\r\n        \" Path to the pomodoro log file (default: \/tmp\/pomodoro.log)\r\n        let g:pomodoro_log_file = \"\/tmp\/pomodoro.log\" \r\n\r\nTo display the remaining time of a pomodoro in your statusline, add \r\n\r\n        set statusline=%#ErrorMsg#%{PomodoroStatus()}%#StatusLine# \r\n\r\nto your `~\/.vimrc` \r\n\r\n>> External Notifications \r\nNotifications outside vim can be enabled through the option `g:pomodoro_notification_cmd`. \r\nFor instance, to play a soundfile after each completed pomodoro or break, add something like \r\n\r\n        let g:pomodoro_notification_cmd = \"mpg123 -q ~\/.vim\/pomodoro-notification.mp3\"\r\n\r\nto your `~\/.vimrc`. System-wide notifications can, for instance, be done via zenity and \r\nthe option\r\n\r\n        let g:pomodoro_notification_cmd = 'zenity --notification --text=\"Pomodoro finished\"''\r\n\r\nDevelopment, Screenshots and more...\r\n------------------------------------------------------\r\nMain development of vim-pomodoro is done at https:\/\/github.com\/mnick\/vim-pomodoro along with up-to-date documentation and screenshots.\r\n","4":"vim-pomodoro is a Vim plugin for the Pomodoro time management technique (http:\/\/www.pomodorotechnique.com\/).\r\n\r\nONLY for Linux\/Mac OS X!\r\n\r\nUsage\r\n---------\r\nThe usage of vim-pomodoro is simple. `:PomodoroStart [pomodoro_name]` starts a new pomodoro. The parameter `pomodoro_name` is optional. After a pomodoro ended, a confirmation dialog will remind you to take a break. When the break has ended, another dialog will ask you if you want to start a new pomodoro. Furthermore, the remaining time of a pomodoro can be displayed in the \r\nstatusline of vim.\r\n\r\nIf you do not want vim-pomodoro to use popup windows but text dialogs inside Vim, add `set guioptions+=c` to your `~\/.gvimrc`. Please note that this will *globally* disable popup notification windows in Vim.\r\n\r\nAlso, in addition to the default notifications inside vim, vim-pomodoro allows to add \r\nfurther external notifications, such as sounds, system-notification popups etc.\r\n\r\nConfiguration\r\n-------------------\r\nAdd the following options to your `~\/.vimrc` to configure vim-pomodoro \r\n\r\n        \" Duration of a pomodoro in minutes (default: 25)\r\n        let g:pomodoro_time_work = 25\r\n\r\n        \" Duration of a break in minutes (default: 5)\r\n        let g:pomodoro_time_slack = 5 \r\n\r\n        \" Log completed pomodoros, 0 = False, 1 = True (default: 0)\r\n        let g:pomodoro_do_log = 0 \r\n\r\n        \" Path to the pomodoro log file (default: \/tmp\/pomodoro.log)\r\n        let g:pomodoro_log_file = \"\/tmp\/pomodoro.log\" \r\n\r\nTo display the remaining time of a pomodoro in your statusline, add \r\n\r\n        set statusline=%#ErrorMsg#%{PomodoroStatus()}%#StatusLine# \r\n\r\nto your `~\/.vimrc` \r\n\r\n>> External Notifications \r\nNotifications outside vim can be enabled through the option `g:pomodoro_notification_cmd`. \r\nFor instance, to play a soundfile after each completed pomodoro or break, add something like \r\n\r\n        let g:pomodoro_notification_cmd = \"mpg123 -q ~\/.vim\/pomodoro-notification.mp3\"\r\n\r\nto your `~\/.vimrc`. System-wide notifications can, for instance, be done via zenity and \r\nthe option\r\n\r\n        let g:pomodoro_notification_cmd = 'zenity --notification --text=\"Pomodoro finished\"''\r\n\r\nDevelopment, Screenshots and more...\r\n------------------------------------------------------\r\nMain development of vim-pomodoro is done at https:\/\/github.com\/mnick\/vim-pomodoro along with up-to-date documentation and screenshots.\r\n","install_details":"vim-pomodoro requires AsyncCommand (vimscript #3431, https:\/\/github.com\/pydave\/AsyncCommand) to be installed. The recommended installation method for both plugins is via Vundle (vimscript #3458, https:\/\/github.com\/gmarik\/vundle). \r\nAdd \r\n\r\n        Bundle 'pydave\/AsyncCommand'\r\n        Bundle 'mnick\/vim-pomodoro'\r\n\r\nto your `~\/.vimrc` and run `BundleInstall` afterwards.\r\n\r\nIf you don't want to use Vundle, first install AsyncCommand and simply extract the tarfile in your ~\/.vim directory afterwards.","5":"vim-pomodoro requires AsyncCommand (vimscript #3431, https:\/\/github.com\/pydave\/AsyncCommand) to be installed. The recommended installation method for both plugins is via Vundle (vimscript #3458, https:\/\/github.com\/gmarik\/vundle). \r\nAdd \r\n\r\n        Bundle 'pydave\/AsyncCommand'\r\n        Bundle 'mnick\/vim-pomodoro'\r\n\r\nto your `~\/.vimrc` and run `BundleInstall` afterwards.\r\n\r\nIf you don't want to use Vundle, first install AsyncCommand and simply extract the tarfile in your ~\/.vim directory afterwards.","first_name":"Maximilian","6":"Maximilian","last_name":"Nickel","7":"Nickel","releases":[{"0":"3979","vim_version":"7.0","1":"7.0","script_version":"0.1.2","2":"0.1.2","version_comment":"minor bugfix","3":"minor bugfix","package":"vim-pomodoro-0.1.2.tar.bz2","4":"vim-pomodoro-0.1.2.tar.bz2","src_id":"17655","5":"17655","creation_date":"1332626574","6":"1332626574"}]},"3978":{"script_id":"3978","0":"3978","script_name":"cudajinja.vim","1":"cudajinja.vim","script_type":"syntax","2":"syntax","summary":"Jinja templating syntax for CUDA","3":"Jinja templating syntax for CUDA","description":"Based on the htmljinja.vim","4":"Based on the htmljinja.vim","install_details":"Put the files into .vim\/syntax\/","5":"Put the files into .vim\/syntax\/","first_name":"Tomi","6":"Tomi","last_name":"Pievil\u00c3\u00a4inen","7":"Pievil\u00c3\u00a4inen","releases":[{"0":"3978","vim_version":"7.0","1":"7.0","script_version":"2","2":"2","version_comment":"This c.vim is needed too, because the standard C syntax file includes Jinja related elements too where they shouldn't be (because it's meant to be used standalone).","3":"This c.vim is needed too, because the standard C syntax file includes Jinja related elements too where they shouldn't be (because it's meant to be used standalone).","package":"c.vim","4":"c.vim","src_id":"17643","5":"17643","creation_date":"1332492868","6":"1332492868"},{"0":"3978","vim_version":"7.0","1":"7.0","script_version":"1","2":"1","version_comment":"Initial upload","3":"Initial upload","package":"cudajinja.vim","4":"cudajinja.vim","src_id":"17642","5":"17642","creation_date":"1332492760","6":"1332492760"}]},"3977":{"script_id":"3977","0":"3977","script_name":"vim-addon-commenting","1":"vim-addon-commenting","script_type":"utility","2":"utility","summary":"minimal commenting plugin","3":"minimal commenting plugin","description":"This minimal commenting implementation found at github.com\/MarcWeber\/vim-addon-commenting just does what I think everybody wants:\r\ncomment, uncomment, automatically detects filetype (if either &commentstring or &comments is set correctly).\r\nAnd it is aware of cursor column. What else do you need (..).\r\n\r\nsyntax (sublanguage) based commenting? Try tcomment intsead","4":"This minimal commenting implementation found at github.com\/MarcWeber\/vim-addon-commenting just does what I think everybody wants:\r\ncomment, uncomment, automatically detects filetype (if either &commentstring or &comments is set correctly).\r\nAnd it is aware of cursor column. What else do you need (..).\r\n\r\nsyntax (sublanguage) based commenting? Try tcomment intsead","install_details":"put into your ~\/.vim folder or use VAM, pathogen, vundle, .. (whatever you like)","5":"put into your ~\/.vim folder or use VAM, pathogen, vundle, .. (whatever you like)","first_name":"Marc","6":"Marc","last_name":"Weber","7":"Weber","releases":[{"0":"3977","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"vim-addon-commenting.zip","4":"vim-addon-commenting.zip","src_id":"17637","5":"17637","creation_date":"1332415807","6":"1332415807"}]},"3976":{"script_id":"3976","0":"3976","script_name":"vim-human-dates","1":"vim-human-dates","script_type":"utility","2":"utility","summary":"Wouldn't it be nice if you could view epoch dates in a format that made sense?","3":"Wouldn't it be nice if you could view epoch dates in a format that made sense?","description":"vim-human-dates turns a date like 1332006094952 into a format like 3\/17\/12 10:41:34am (-193,308 seconds from now).\r\n\r\nThe only mapping is <leader>j.\r\n\r\nThe github repostiory is here:\r\n\r\nhttps:\/\/github.com\/beaugunderson\/vim-human-dates","4":"vim-human-dates turns a date like 1332006094952 into a format like 3\/17\/12 10:41:34am (-193,308 seconds from now).\r\n\r\nThe only mapping is <leader>j.\r\n\r\nThe github repostiory is here:\r\n\r\nhttps:\/\/github.com\/beaugunderson\/vim-human-dates","install_details":"","5":"","first_name":"Beau","6":"Beau","last_name":"Gunderson","7":"Gunderson","releases":[{"0":"3976","vim_version":"7.2","1":"7.2","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"beaugunderson-vim-human-dates-ade4527.tar.gz","4":"beaugunderson-vim-human-dates-ade4527.tar.gz","src_id":"17634","5":"17634","creation_date":"1332393807","6":"1332393807"}]},"3975":{"script_id":"3975","0":"3975","script_name":"Finder for vim","1":"Finder for vim","script_type":"utility","2":"utility","summary":"Finder for VIm","3":"Finder for VIm","description":"after set g:paths in finder.vim , you can find your file by press <C-f> then input regular expression(now only support python's regular) to find file, it will open an window which list all the files that founded.\r\n\r\nmove cursor to the file path that you want to open,\r\npress <Enter>, it will hide the find result window and edit the file in last window.\r\npress <Space>,same as <Enter> but keep the find result window\r\npress <ESC>  to close the findResult window.\r\n\r\nNeed python support.\r\n\r\nGet lasted version on github: https:\/\/github.com\/xieyu\/Finder\r\n\r\n","4":"after set g:paths in finder.vim , you can find your file by press <C-f> then input regular expression(now only support python's regular) to find file, it will open an window which list all the files that founded.\r\n\r\nmove cursor to the file path that you want to open,\r\npress <Enter>, it will hide the find result window and edit the file in last window.\r\npress <Space>,same as <Enter> but keep the find result window\r\npress <ESC>  to close the findResult window.\r\n\r\nNeed python support.\r\n\r\nGet lasted version on github: https:\/\/github.com\/xieyu\/Finder\r\n\r\n","install_details":"change g:paths, g:paths_sep to your own in finder.vim, then drop it to plugin ","5":"change g:paths, g:paths_sep to your own in finder.vim, then drop it to plugin ","first_name":"yu","6":"yu","last_name":"xie","7":"xie","releases":[{"0":"3975","vim_version":"7.0","1":"7.0","script_version":"0.01","2":"0.01","version_comment":"Initial upload","3":"Initial upload","package":"finder_for_vim.zip","4":"finder_for_vim.zip","src_id":"17626","5":"17626","creation_date":"1332347413","6":"1332347413"}]},"3974":{"script_id":"3974","0":"3974","script_name":"showmarks2","1":"showmarks2","script_type":"ftplugin","2":"ftplugin","summary":"bookmark works like MS utilities","3":"bookmark works like MS utilities","description":"^F2: toggle a bookmark at cursor\r\nF2: goto next bookmark\r\nshift-F2:goto previous bookmark\r\n^shift-F2: clear all bookmark\r\nthe rest: the same as before\r\n\r\ncopied from showmarks.vim, and then changed.\r\nI am a week old with vim. The status is crude, but works fine (Windows).\r\n\r\nThanks for reading!","4":"^F2: toggle a bookmark at cursor\r\nF2: goto next bookmark\r\nshift-F2:goto previous bookmark\r\n^shift-F2: clear all bookmark\r\nthe rest: the same as before\r\n\r\ncopied from showmarks.vim, and then changed.\r\nI am a week old with vim. The status is crude, but works fine (Windows).\r\n\r\nThanks for reading!","install_details":"drop in plugin directory.\r\n","5":"drop in plugin directory.\r\n","first_name":"john","6":"john","last_name":"kim","7":"kim","releases":[{"0":"3974","vim_version":"7.0","1":"7.0","script_version":"1.5","2":"1.5","version_comment":"Cleaned up, a little further going away from the org ShowMarks.\r\nI feel strange problems have gone, though not tested much.\r\nAt least, the code is legible now; You and I can fix something.\r\nPlease, write to me, if you find it is useful\/need fix\/etc.\r\nThanks!\r\n","3":"Cleaned up, a little further going away from the org ShowMarks.\r\nI feel strange problems have gone, though not tested much.\r\nAt least, the code is legible now; You and I can fix something.\r\nPlease, write to me, if you find it is useful\/need fix\/etc.\r\nThanks!\r\n","package":"showmarks2.vim","4":"showmarks2.vim","src_id":"17691","5":"17691","creation_date":"1333130048","6":"1333130048"},{"0":"3974","vim_version":"7.0","1":"7.0","script_version":"1.4","2":"1.4","version_comment":"Tested on Ubuntu.\r\nFix \/ added \"autochdir\" to place _session & _viminfo in the current working directory.\r\nAdded F11 = SaveSession()\r\nI might have committed this file in \"utility\" type.\r\n","3":"Tested on Ubuntu.\r\nFix \/ added \"autochdir\" to place _session & _viminfo in the current working directory.\r\nAdded F11 = SaveSession()\r\nI might have committed this file in \"utility\" type.\r\n","package":"showmarks2.vim","4":"showmarks2.vim","src_id":"17663","5":"17663","creation_date":"1332793296","6":"1332793296"},{"0":"3974","vim_version":"7.0","1":"7.0","script_version":"1.3","2":"1.3","version_comment":"Fixed the highlights disappearing after auto loading info (Something eats it up?)\r\nEnabled auto-loading\/auto-saving; See the comment (in line) about how to setup this on Win-XP.\r\n-. I see error message about \"viminfo\" not found, for the first round, depending on setup. Please, would you fix it for me?\r\nAdded\/changed F12; \"SaveSessionAs()\". It would be nice to have \"default path at no entry\". Would you please add that?\r\nSorry, but I have not tried this on Ubuntu, yet. Perhaps, I will finish here, until test it on Ubuntu.\r\n\r\n","3":"Fixed the highlights disappearing after auto loading info (Something eats it up?)\r\nEnabled auto-loading\/auto-saving; See the comment (in line) about how to setup this on Win-XP.\r\n-. I see error message about \"viminfo\" not found, for the first round, depending on setup. Please, would you fix it for me?\r\nAdded\/changed F12; \"SaveSessionAs()\". It would be nice to have \"default path at no entry\". Would you please add that?\r\nSorry, but I have not tried this on Ubuntu, yet. Perhaps, I will finish here, until test it on Ubuntu.\r\n\r\n","package":"showmarks2.vim","4":"showmarks2.vim","src_id":"17639","5":"17639","creation_date":"1332440055","6":"1332440055"},{"0":"3974","vim_version":"7.0","1":"7.0","script_version":"1.2","2":"1.2","version_comment":"Fixed cursor jumping after marking using 'm'.\r\nExtended ShowMarks() function to outside, for the reason below.\r\nAdded example of auto session\/marks loading\/saving (I have them in _vimrc).\r\nThanks to the vim community!\r\n","3":"Fixed cursor jumping after marking using 'm'.\r\nExtended ShowMarks() function to outside, for the reason below.\r\nAdded example of auto session\/marks loading\/saving (I have them in _vimrc).\r\nThanks to the vim community!\r\n","package":"showmarks2.vim","4":"showmarks2.vim","src_id":"17627","5":"17627","creation_date":"1332371439","6":"1332371439"},{"0":"3974","vim_version":"7.0","1":"7.0","script_version":"1.1","2":"1.1","version_comment":"Someone liked to have <F2> keys mapped already, so be it.\r\nBTW, are you getting good contrast for the highlights?\r\n","3":"Someone liked to have <F2> keys mapped already, so be it.\r\nBTW, are you getting good contrast for the highlights?\r\n","package":"showmarks2.vim","4":"showmarks2.vim","src_id":"17625","5":"17625","creation_date":"1332337833","6":"1332337833"},{"0":"3974","vim_version":"7.0","1":"7.0","script_version":"1","2":"1","version_comment":"Initial upload","3":"Initial upload","package":"showmarks2.vim","4":"showmarks2.vim","src_id":"17616","5":"17616","creation_date":"1332289611","6":"1332289611"}]},"3973":{"script_id":"3973","0":"3973","script_name":"diff-toggle","1":"diff-toggle","script_type":"ftplugin","2":"ftplugin","summary":"Toggle diff lines","3":"Toggle diff lines","description":"https:\/\/github.com\/twe4ked\/vim-diff-toggle","4":"https:\/\/github.com\/twe4ked\/vim-diff-toggle","install_details":"","5":"","first_name":"Odin","6":"Odin","last_name":"Dutton","7":"Dutton","releases":[{"0":"3973","vim_version":"7.0","1":"7.0","script_version":"0.2","2":"0.2","version_comment":"* 1f6d522 Add @inkarkat to the list of contributors.\r\n* 72b8479 Update README to reflect new functionality.\r\n* c8d715c Remove `cursor` call that wasn't doing anything.\r\n* b19134b Don't move to the cursor when toggling.\r\n* 8aaa05a ENH: Support toggling of visual selection.\r\n* 1f43ff3 ENH: Support toggling [count] lines.\r\n* b047d93 Delete added lines as toggle action.\r\n* 4381b04 Turn script into ftplugin.\r\n* 519d32f Remove ability to toggle `+` lines.\r\n","3":"* 1f6d522 Add @inkarkat to the list of contributors.\r\n* 72b8479 Update README to reflect new functionality.\r\n* c8d715c Remove `cursor` call that wasn't doing anything.\r\n* b19134b Don't move to the cursor when toggling.\r\n* 8aaa05a ENH: Support toggling of visual selection.\r\n* 1f43ff3 ENH: Support toggling [count] lines.\r\n* b047d93 Delete added lines as toggle action.\r\n* 4381b04 Turn script into ftplugin.\r\n* 519d32f Remove ability to toggle `+` lines.\r\n","package":"diff_toggle.vim","4":"diff_toggle.vim","src_id":"18251","5":"18251","creation_date":"1342132880","6":"1342132880"},{"0":"3973","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"diff_toggle.vim","4":"diff_toggle.vim","src_id":"17613","5":"17613","creation_date":"1332218729","6":"1332218729"}]},"3972":{"script_id":"3972","0":"3972","script_name":"css3 syntax plus","1":"css3 syntax plus","script_type":"syntax","2":"syntax","summary":"A lightweight css3 syntax file for vim","3":"A lightweight css3 syntax file for vim","description":"Repository: https:\/\/github.com\/kight\/CSS3-syntax-file-for-vim\r\n\r\n1.Compatible with default css syntax in vim.\r\n2.Support vendor prefix highlight.\r\n3.Compatible with vundle\r\n4.One-click installation.\r\n5.CSS 3 Properties which do not have any browser support will -NOT- be highlighted\r\n","4":"Repository: https:\/\/github.com\/kight\/CSS3-syntax-file-for-vim\r\n\r\n1.Compatible with default css syntax in vim.\r\n2.Support vendor prefix highlight.\r\n3.Compatible with vundle\r\n4.One-click installation.\r\n5.CSS 3 Properties which do not have any browser support will -NOT- be highlighted\r\n","install_details":"run .\/install.sh\r\n","5":"run .\/install.sh\r\n","first_name":"Junqing","6":"Junqing","last_name":"Wang","7":"Wang","releases":[{"0":"3972","vim_version":"7.0","1":"7.0","script_version":"0.4","2":"0.4","version_comment":"add more attributes highlight\r\na highlight bug fix for @keyframes","3":"add more attributes highlight\r\na highlight bug fix for @keyframes","package":"CSS3-syntax-file.tar","4":"CSS3-syntax-file.tar","src_id":"17633","5":"17633","creation_date":"1332390271","6":"1332390271"},{"0":"3972","vim_version":"7.0","1":"7.0","script_version":"0.3","2":"0.3","version_comment":"CSS 3 Properties which do not have any browser support will -NOT- be highlighted","3":"CSS 3 Properties which do not have any browser support will -NOT- be highlighted","package":"CSS3-syntax-file.tar","4":"CSS3-syntax-file.tar","src_id":"17624","5":"17624","creation_date":"1332321082","6":"1332321082"},{"0":"3972","vim_version":"7.0","1":"7.0","script_version":"0.21","2":"0.21","version_comment":"a quick fix of typing error","3":"a quick fix of typing error","package":"CSS3-syntax-file.tar","4":"CSS3-syntax-file.tar","src_id":"17617","5":"17617","creation_date":"1332300957","6":"1332300957"},{"0":"3972","vim_version":"7.0","1":"7.0","script_version":"0.2","2":"0.2","version_comment":"make it compatible with \"vundle\"---vim plugin manager","3":"make it compatible with \"vundle\"---vim plugin manager","package":"CSS3-syntax-file.tar","4":"CSS3-syntax-file.tar","src_id":"17614","5":"17614","creation_date":"1332252289","6":"1332252289"},{"0":"3972","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"css3_syntax_file.tar","4":"css3_syntax_file.tar","src_id":"17611","5":"17611","creation_date":"1332154333","6":"1332154333"}]},"3971":{"script_id":"3971","0":"3971","script_name":"regexroute.vim","1":"regexroute.vim","script_type":"syntax","2":"syntax","summary":"Syntax Highlighting for Yate","3":"Syntax Highlighting for Yate","description":"  The regexroute vim syntax file should cover all of the configuration files used by the Yate (http:\/\/yate.null.ro) open source communications engine.\r\n","4":"  The regexroute vim syntax file should cover all of the configuration files used by the Yate (http:\/\/yate.null.ro) open source communications engine.\r\n","install_details":"Untar, then copy yate-vim\/regexroute.vim to ~\/.vim\/syntax, add the contents of yate-vim\/filetype.vim to ~\/.vim\/filetype.vim.  Then edit any yate configuration file.","5":"Untar, then copy yate-vim\/regexroute.vim to ~\/.vim\/syntax, add the contents of yate-vim\/filetype.vim to ~\/.vim\/filetype.vim.  Then edit any yate configuration file.","first_name":"TJ","6":"TJ","last_name":"Vanderpoel","7":"Vanderpoel","releases":[{"0":"3971","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"yate-vim.tar.gz","4":"yate-vim.tar.gz","src_id":"17610","5":"17610","creation_date":"1332102771","6":"1332102771"}]},"3970":{"script_id":"3970","0":"3970","script_name":"mediawiki.vim","1":"mediawiki.vim","script_type":"syntax","2":"syntax","summary":"This holds a syntax highlighter for MediaWiki-based projects, mostly Wikipedia.","3":"This holds a syntax highlighter for MediaWiki-based projects, mostly Wikipedia.","description":"This holds a syntax highlighter for MediaWiki-based projects, mostly Wikipedia.\r\n\r\nFiles ending in .wiki will be highlighted. To force highlighting on any file, run :setfiletype mediawiki.","4":"This holds a syntax highlighter for MediaWiki-based projects, mostly Wikipedia.\r\n\r\nFiles ending in .wiki will be highlighted. To force highlighting on any file, run :setfiletype mediawiki.","install_details":"See README.md, or head to https:\/\/github.com\/chikamichi\/mediawiki.vim.","5":"See README.md, or head to https:\/\/github.com\/chikamichi\/mediawiki.vim.","first_name":"Jean-Denis","6":"Jean-Denis","last_name":"Vauguet","7":"Vauguet","releases":[{"0":"3970","vim_version":"7.0","1":"7.0","script_version":"0.2","2":"0.2","version_comment":"Enhanced syntax support.","3":"Enhanced syntax support.","package":"mediawiki.vim-0.2.zip","4":"mediawiki.vim-0.2.zip","src_id":"21133","5":"21133","creation_date":"1385835953","6":"1385835953"},{"0":"3970","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"mediawiki.vim.tar.gz","4":"mediawiki.vim.tar.gz","src_id":"17609","5":"17609","creation_date":"1332080015","6":"1332080015"}]},"3969":{"script_id":"3969","0":"3969","script_name":"source.vim","1":"source.vim","script_type":"utility","2":"utility","summary":"source vim plugins and remote scripts","3":"source vim plugins and remote scripts","description":"This plugin will download and run any remote snippets and plugins found in your vimrc.\r\n\r\nUse in a similar fashion as the built-in source command:\r\n\r\nSource git:\/\/github.com\/mileszs\/ack.vim.git\r\nSource git:\/\/gist.github.com\/1229444.git\r\nSource https:\/\/raw.github.com\/gist\/1229444\/6d07d825fa99a26d2dcc0fd83e9a8b1c78978bfa\/statusline-help.vim\r\n\r\nIf sourcing a repository on Github, you can source the project page instead:\r\n\r\nSource https:\/\/github.com\/mileszs\/ack.vim\r\nSource https:\/\/gist.github.com\/1229444\r\n\r\nIf installing a plugin requires a few commands, add them after the repository:\r\n\r\nSource git:\/\/git.wincent.com\/command-t.git rake make\r\n\r\nAutomatic updates occur once a week when starting Vim. This will git pull any repositories and re-download any other files. You can force an update calling the Source command with a bang:\r\n\r\nSource! https:\/\/github.com\/kien\/ctrlp.vim\r\n\r\nREQUIREMENTS\r\n\r\nSeveral system commands are called: echo, cat, cd, mkdir, rm, mv, date. Also, if sourcing a git repository, the git command is used. And if sourcing a regular text, the curl command is used.\r\n\r\nI've only tested this with OS X 10.7 and Ubuntu 10.04.4 LTS.","4":"This plugin will download and run any remote snippets and plugins found in your vimrc.\r\n\r\nUse in a similar fashion as the built-in source command:\r\n\r\nSource git:\/\/github.com\/mileszs\/ack.vim.git\r\nSource git:\/\/gist.github.com\/1229444.git\r\nSource https:\/\/raw.github.com\/gist\/1229444\/6d07d825fa99a26d2dcc0fd83e9a8b1c78978bfa\/statusline-help.vim\r\n\r\nIf sourcing a repository on Github, you can source the project page instead:\r\n\r\nSource https:\/\/github.com\/mileszs\/ack.vim\r\nSource https:\/\/gist.github.com\/1229444\r\n\r\nIf installing a plugin requires a few commands, add them after the repository:\r\n\r\nSource git:\/\/git.wincent.com\/command-t.git rake make\r\n\r\nAutomatic updates occur once a week when starting Vim. This will git pull any repositories and re-download any other files. You can force an update calling the Source command with a bang:\r\n\r\nSource! https:\/\/github.com\/kien\/ctrlp.vim\r\n\r\nREQUIREMENTS\r\n\r\nSeveral system commands are called: echo, cat, cd, mkdir, rm, mv, date. Also, if sourcing a git repository, the git command is used. And if sourcing a regular text, the curl command is used.\r\n\r\nI've only tested this with OS X 10.7 and Ubuntu 10.04.4 LTS.","install_details":"Install in ~\/.vim\/plugin\r\n\r\nAdd this line to the top of your .vimrc:\r\nruntime plugin\/source.vim\r\n\r\nFor nicely formatted documentation, see the README on GitHub: \r\nhttps:\/\/github.com\/suderman\/source.vim","5":"Install in ~\/.vim\/plugin\r\n\r\nAdd this line to the top of your .vimrc:\r\nruntime plugin\/source.vim\r\n\r\nFor nicely formatted documentation, see the README on GitHub: \r\nhttps:\/\/github.com\/suderman\/source.vim","first_name":"Jon","6":"Jon","last_name":"Suderman","7":"Suderman","releases":[{"0":"3969","vim_version":"7.2","1":"7.2","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"source.vim","4":"source.vim","src_id":"17600","5":"17600","creation_date":"1331926112","6":"1331926112"}]},"3968":{"script_id":"3968","0":"3968","script_name":"JumpToTrailingWhitespace","1":"JumpToTrailingWhitespace","script_type":"utility","2":"utility","summary":"Motions to locate unwanted whitespace at the end of lines.","3":"Motions to locate unwanted whitespace at the end of lines.","description":"DESCRIPTION\r\nThis plugin provides movement commands to quickly go to whitespace at the end\r\nof each line. (Usually in order to remove it).\r\n\r\nSEE ALSO\r\nThis plugin leverages the superior detection and customization facilities of\r\nthe companion ShowTrailingWhitespace.vim plugin (vimscript #3966), though it\r\ncan also be used without it if you're not interested in highlighting and\r\ncustomizing.\r\n\r\nInstead of jumping and deleting each occurrence manually, you can use the\r\ncompanion DeleteTrailingWhitespace.vim (vimscript #3967) plugin to strip off\r\nthe trailing whitespace with one command, or even have this done automatically\r\non each write.\r\n\r\nUSAGE\r\n]$                      Go to [count] next occurrence of trailing whitespace.\r\n[$                      Go to [count] previous occurrence of trailing\r\n                        whitespace.\r\n\r\nNormal, operator-pending, and visual mode mappings are defined, even though\r\nthe latter two are typically less useful that the normal mode mappings. The\r\n'wrapscan' setting applies.","4":"DESCRIPTION\r\nThis plugin provides movement commands to quickly go to whitespace at the end\r\nof each line. (Usually in order to remove it).\r\n\r\nSEE ALSO\r\nThis plugin leverages the superior detection and customization facilities of\r\nthe companion ShowTrailingWhitespace.vim plugin (vimscript #3966), though it\r\ncan also be used without it if you're not interested in highlighting and\r\ncustomizing.\r\n\r\nInstead of jumping and deleting each occurrence manually, you can use the\r\ncompanion DeleteTrailingWhitespace.vim (vimscript #3967) plugin to strip off\r\nthe trailing whitespace with one command, or even have this done automatically\r\non each write.\r\n\r\nUSAGE\r\n]$                      Go to [count] next occurrence of trailing whitespace.\r\n[$                      Go to [count] previous occurrence of trailing\r\n                        whitespace.\r\n\r\nNormal, operator-pending, and visual mode mappings are defined, even though\r\nthe latter two are typically less useful that the normal mode mappings. The\r\n'wrapscan' setting applies.","install_details":"INSTALLATION\r\nThis script is packaged as a vimball. If you have the \"gunzip\" decompressor\r\nin your PATH, simply edit the *.vmb.gz package in Vim; otherwise, decompress\r\nthe archive first, e.g. using WinZip. Inside Vim, install by sourcing the\r\nvimball or via the :UseVimball command.\r\n    vim JumpToTrailingWhitespace*.vmb.gz\r\n    :so %\r\nTo uninstall, use the :RmVimball command.\r\n\r\nDEPENDENCIES\r\n- Requires Vim 7.0 or higher.\r\n- Requires the CountJump plugin (vimscript #3130), version 1.70 or higher.\r\n- The ShowTrailingWhitespace.vim plugin (vimscript #3966) complements this\r\n  script, but is not required. With it, the jumps consider the whitespace\r\n  exceptions for certain filetypes.\r\n\r\n\r\nCONFIGURATION\r\nFor a permanent configuration, put the following commands into your vimrc:\r\n\r\nTo change the default mappings from ]$ to ]x, use:\r\n    let g:JumpToTrailingWhitespace_Mapping = 'x'\r\nTo also change the [ \/ ] prefix to something else, follow the instructions for\r\nCountJump-remap-motions. (This requires CountJump 1.60.)","5":"INSTALLATION\r\nThis script is packaged as a vimball. If you have the \"gunzip\" decompressor\r\nin your PATH, simply edit the *.vmb.gz package in Vim; otherwise, decompress\r\nthe archive first, e.g. using WinZip. Inside Vim, install by sourcing the\r\nvimball or via the :UseVimball command.\r\n    vim JumpToTrailingWhitespace*.vmb.gz\r\n    :so %\r\nTo uninstall, use the :RmVimball command.\r\n\r\nDEPENDENCIES\r\n- Requires Vim 7.0 or higher.\r\n- Requires the CountJump plugin (vimscript #3130), version 1.70 or higher.\r\n- The ShowTrailingWhitespace.vim plugin (vimscript #3966) complements this\r\n  script, but is not required. With it, the jumps consider the whitespace\r\n  exceptions for certain filetypes.\r\n\r\n\r\nCONFIGURATION\r\nFor a permanent configuration, put the following commands into your vimrc:\r\n\r\nTo change the default mappings from ]$ to ]x, use:\r\n    let g:JumpToTrailingWhitespace_Mapping = 'x'\r\nTo also change the [ \/ ] prefix to something else, follow the instructions for\r\nCountJump-remap-motions. (This requires CountJump 1.60.)","first_name":"Ingo","6":"Ingo","last_name":"Karkat","7":"Karkat","releases":[{"0":"3968","vim_version":"7.0","1":"7.0","script_version":"1.10","2":"1.10","version_comment":"- As the search obeys the 'wrapscan' setting, also issue corresponding \"trailing whitespace search hit BOTTOM, continuing at TOP\" wrap warning messages. This requires the enhanced CountJump plugin version 1.70.","3":"- As the search obeys the 'wrapscan' setting, also issue corresponding \"trailing whitespace search hit BOTTOM, continuing at TOP\" wrap warning messages. This requires the enhanced CountJump plugin version 1.70.","package":"JumpToTrailingWhitespace-1.10.vmb.gz","4":"JumpToTrailingWhitespace-1.10.vmb.gz","src_id":"18536","5":"18536","creation_date":"1346664447","6":"1346664447"},{"0":"3968","vim_version":"7.0","1":"7.0","script_version":"1.01","2":"1.01","version_comment":"- CHG: Change g:JumpToTrailingWhitespace_mapping to g:JumpToTrailingWhitespace_Mapping.\r\n- Document changing of [ \/ ] prefix through new CountJump 1.60.","3":"- CHG: Change g:JumpToTrailingWhitespace_mapping to g:JumpToTrailingWhitespace_Mapping.\r\n- Document changing of [ \/ ] prefix through new CountJump 1.60.","package":"JumpToTrailingWhitespace.vba.gz","4":"JumpToTrailingWhitespace.vba.gz","src_id":"17679","5":"17679","creation_date":"1332934077","6":"1332934077"},{"0":"3968","vim_version":"7.0","1":"7.0","script_version":"1.00","2":"1.00","version_comment":"Initial upload","3":"Initial upload","package":"JumpToTrailingWhitespace.vba.gz","4":"JumpToTrailingWhitespace.vba.gz","src_id":"17598","5":"17598","creation_date":"1331900397","6":"1331900397"}]},"3967":{"script_id":"3967","0":"3967","script_name":"DeleteTrailingWhitespace","1":"DeleteTrailingWhitespace","script_type":"utility","2":"utility","summary":"Delete unwanted whitespace at the end of lines.","3":"Delete unwanted whitespace at the end of lines.","description":"DESCRIPTION\r\nThis plugin deletes whitespace at the end of each line, on demand via the\r\n:DeleteTrailingWhitespace command, or automatically when the buffer is\r\nwritten.\r\n\r\nSEE ALSO\r\nThis plugin leverages the superior detection and customization facilities of\r\nthe companion ShowTrailingWhitespace.vim plugin (vimscript #3966), though it\r\ncan also be used without it if you're not interested in highlighting and\r\ncustomizing.\r\n\r\nTo quickly locate the occurrences of trailing whitespace, you can use the\r\ncompanion JumpToTrailingWhitespace.vim plugin (vimscript #3968).\r\n\r\nRELATED WORKS\r\nThe basic substitution commands as well as more elaborate scriptlets, as the\r\nidea of automating this can be found in this VimTip:\r\n    http:\/\/vim.wikia.com\/wiki\/Remove_unwanted_spaces\r\nThere are already a number of plugins that define such a command; most bundle\r\nthis functionality together with the highlighting of trailing whitespace.\r\nHowever, most of them cannot consider whitespace exceptions and are not as\r\nflexible.\r\n- trailing-whitespace (vimscript #3201) defines :FixWhitespace.\r\n- bad-whitespace (vimscript #3735) defines :EraseBadWhitespace.\r\n- Trailer Trash (vimscript #3938) defines :Trim.\r\n- StripWhiteSpaces (vimscript #4016) defines :StripWhiteSpaces and strips\r\n  automatically, too, but is way more simple than this plugin.\r\n- WhiteWash (vimscript #3920) provides functions that also can strip visible\r\n  ^M and sequential whitespacw between words.\r\n- strip_trailing_whitespace.vim (vimscript #5695) is another alternative which\r\n  offers a command and configurable mappings.\r\n\r\nUSAGE\r\n:[range]DeleteTrailingWhitespace\r\n                        Delete all trailing whitespace in the current buffer\r\n                        or [range].","4":"DESCRIPTION\r\nThis plugin deletes whitespace at the end of each line, on demand via the\r\n:DeleteTrailingWhitespace command, or automatically when the buffer is\r\nwritten.\r\n\r\nSEE ALSO\r\nThis plugin leverages the superior detection and customization facilities of\r\nthe companion ShowTrailingWhitespace.vim plugin (vimscript #3966), though it\r\ncan also be used without it if you're not interested in highlighting and\r\ncustomizing.\r\n\r\nTo quickly locate the occurrences of trailing whitespace, you can use the\r\ncompanion JumpToTrailingWhitespace.vim plugin (vimscript #3968).\r\n\r\nRELATED WORKS\r\nThe basic substitution commands as well as more elaborate scriptlets, as the\r\nidea of automating this can be found in this VimTip:\r\n    http:\/\/vim.wikia.com\/wiki\/Remove_unwanted_spaces\r\nThere are already a number of plugins that define such a command; most bundle\r\nthis functionality together with the highlighting of trailing whitespace.\r\nHowever, most of them cannot consider whitespace exceptions and are not as\r\nflexible.\r\n- trailing-whitespace (vimscript #3201) defines :FixWhitespace.\r\n- bad-whitespace (vimscript #3735) defines :EraseBadWhitespace.\r\n- Trailer Trash (vimscript #3938) defines :Trim.\r\n- StripWhiteSpaces (vimscript #4016) defines :StripWhiteSpaces and strips\r\n  automatically, too, but is way more simple than this plugin.\r\n- WhiteWash (vimscript #3920) provides functions that also can strip visible\r\n  ^M and sequential whitespacw between words.\r\n- strip_trailing_whitespace.vim (vimscript #5695) is another alternative which\r\n  offers a command and configurable mappings.\r\n\r\nUSAGE\r\n:[range]DeleteTrailingWhitespace\r\n                        Delete all trailing whitespace in the current buffer\r\n                        or [range].","install_details":"INSTALLATION\r\nThe code is hosted in a Git repo at\r\n    https:\/\/github.com\/inkarkat\/vim-DeleteTrailingWhitespace\r\nYou can use your favorite plugin manager, or \"git clone\" into a directory used\r\nfor Vim packages. Releases are on the \"stable\" branch, the latest unstable\r\ndevelopment snapshot on \"master\".\r\n\r\nThis script is also packaged as a vimball. If you have the \"gunzip\"\r\ndecompressor in your PATH, simply edit the *.vmb.gz package in Vim; otherwise,\r\ndecompress the archive first, e.g. using WinZip. Inside Vim, install by\r\nsourcing the vimball or via the :UseVimball command.\r\n    vim DeleteTrailingWhitespace*.vmb.gz\r\n    :so %\r\nTo uninstall, use the :RmVimball command.\r\n\r\nDEPENDENCIES\r\n- Requires Vim 7.0 or higher.\r\n- Requires the ingo-library.vim plugin (vimscript #4433), version 1.036 or\r\n  higher.\r\n- The ShowTrailingWhitespace.vim plugin (vimscript #3966) complements this\r\n  script, but is not required. With it, this plugin considers the whitespace\r\n  exceptions for certain filetypes.\r\n\r\nCONFIGURATION\r\nFor a permanent configuration, put the following commands into your vimrc:\r\n\r\nThis plugin doesn't come with predefined mappings, but if you want some, you\r\ncan trivially define them yourself:\r\n    nnoremap <Leader>d$ :<C-u>%DeleteTrailingWhitespace<CR>\r\n    vnoremap <Leader>d$ :DeleteTrailingWhitespace<CR>\r\n\r\nBy default, trailing whitespace is processed before writing the buffer when it\r\nhas been detected and is currently being highlighted by the\r\nShowTrailingWhitespace.vim plugin.\r\nTo turn off the automatic deletion of trailing whitespace, use:\r\n    let g:DeleteTrailingWhitespace = 0\r\nIf you want to eradicate all trailing whitespace all the time, use:\r\n    let g:DeleteTrailingWhitespace = 1\r\nAlso see the following configuration option to turn off the confirmation\r\nqueries in case you want unconditional, fully automatic removal.\r\n\r\nFor processing, the default asks whether to remove or keep the whitespace\r\n(either for the current buffer, or all buffers in the entire Vim session, or\r\nfor the current buffer across time and Vim sessions).\r\nAlternatively, the plugin can just abort the write, unless ! is given:\r\n    let g:DeleteTrailingWhitespace_Action = 'abort'\r\nTo automatically eradicate the trailing whitespace, use:\r\n    let g:DeleteTrailingWhitespace_Action = 'delete'\r\n\r\nWhen the plugin is configured to ask the user, and she gives a negative\r\nanswer, the ShowTrailingWhitespace.vim highlighting is turned off\r\nautomatically; when you ignore it, there's typically no sense in still\r\nhighlighting it. If you don't want that, keep the highlighting via:\r\n    let g:DeleteTrailingWhitespace_ChoiceAffectsHighlighting = []\r\nor selectively keep the highlighting by removing responses from:\r\n    let g:DeleteTrailingWhitespace_ChoiceAffectsHighlighting =\r\n    \\ ['No', 'Never', 'Never ever', 'Never ever recalled', 'Never ever highlight', 'Nowhere']\r\n\r\nThe global detection and processing behavior can be changed for individual\r\nbuffers by setting the corresponding buffer-local variables.","5":"INSTALLATION\r\nThe code is hosted in a Git repo at\r\n    https:\/\/github.com\/inkarkat\/vim-DeleteTrailingWhitespace\r\nYou can use your favorite plugin manager, or \"git clone\" into a directory used\r\nfor Vim packages. Releases are on the \"stable\" branch, the latest unstable\r\ndevelopment snapshot on \"master\".\r\n\r\nThis script is also packaged as a vimball. If you have the \"gunzip\"\r\ndecompressor in your PATH, simply edit the *.vmb.gz package in Vim; otherwise,\r\ndecompress the archive first, e.g. using WinZip. Inside Vim, install by\r\nsourcing the vimball or via the :UseVimball command.\r\n    vim DeleteTrailingWhitespace*.vmb.gz\r\n    :so %\r\nTo uninstall, use the :RmVimball command.\r\n\r\nDEPENDENCIES\r\n- Requires Vim 7.0 or higher.\r\n- Requires the ingo-library.vim plugin (vimscript #4433), version 1.036 or\r\n  higher.\r\n- The ShowTrailingWhitespace.vim plugin (vimscript #3966) complements this\r\n  script, but is not required. With it, this plugin considers the whitespace\r\n  exceptions for certain filetypes.\r\n\r\nCONFIGURATION\r\nFor a permanent configuration, put the following commands into your vimrc:\r\n\r\nThis plugin doesn't come with predefined mappings, but if you want some, you\r\ncan trivially define them yourself:\r\n    nnoremap <Leader>d$ :<C-u>%DeleteTrailingWhitespace<CR>\r\n    vnoremap <Leader>d$ :DeleteTrailingWhitespace<CR>\r\n\r\nBy default, trailing whitespace is processed before writing the buffer when it\r\nhas been detected and is currently being highlighted by the\r\nShowTrailingWhitespace.vim plugin.\r\nTo turn off the automatic deletion of trailing whitespace, use:\r\n    let g:DeleteTrailingWhitespace = 0\r\nIf you want to eradicate all trailing whitespace all the time, use:\r\n    let g:DeleteTrailingWhitespace = 1\r\nAlso see the following configuration option to turn off the confirmation\r\nqueries in case you want unconditional, fully automatic removal.\r\n\r\nFor processing, the default asks whether to remove or keep the whitespace\r\n(either for the current buffer, or all buffers in the entire Vim session, or\r\nfor the current buffer across time and Vim sessions).\r\nAlternatively, the plugin can just abort the write, unless ! is given:\r\n    let g:DeleteTrailingWhitespace_Action = 'abort'\r\nTo automatically eradicate the trailing whitespace, use:\r\n    let g:DeleteTrailingWhitespace_Action = 'delete'\r\n\r\nWhen the plugin is configured to ask the user, and she gives a negative\r\nanswer, the ShowTrailingWhitespace.vim highlighting is turned off\r\nautomatically; when you ignore it, there's typically no sense in still\r\nhighlighting it. If you don't want that, keep the highlighting via:\r\n    let g:DeleteTrailingWhitespace_ChoiceAffectsHighlighting = []\r\nor selectively keep the highlighting by removing responses from:\r\n    let g:DeleteTrailingWhitespace_ChoiceAffectsHighlighting =\r\n    \\ ['No', 'Never', 'Never ever', 'Never ever recalled', 'Never ever highlight', 'Nowhere']\r\n\r\nThe global detection and processing behavior can be changed for individual\r\nbuffers by setting the corresponding buffer-local variables.","first_name":"Ingo","6":"Ingo","last_name":"Karkat","7":"Karkat","releases":[{"0":"3967","vim_version":"7.0","1":"7.0","script_version":"1.10","2":"1.10","version_comment":"- ENH: Add \"Forever\" and \"Never ever\" choices that persist the response for the current file across Vim session.\r\n- ENH: If ShowTrailingWhitespace.vim (version 1.10 or higher) is installed, offer a \"Never ever highlight\" choice that turns off highlighting for the current file persistently across Vim sessions.\r\n- CHG: Make asking for action (instead of aborting) the default action, now that we offer many more choices, and the whole persistent recall of responses only works there. It's also more friendly and transparent towards first-time users of the plugin. To restore the original behavior: > let g:DeleteTrailingWhitespace_Action = 'abort'\r\n- CHG: g:DeleteTrailingWhitespace_ChoiceAffectsHighlighting now is a List of possible responses that if missing will keep the highlighting for that particular response.\r\n- BUG: DeleteTrailingWhitespace_Action checks window-local instead of buffer-local override. Thanks to Enno for noticing.\r\n- Add dependency to ingo-library (vimscript #4433). *** You need to separately install ingo-library (vimscript #4433) version 1.036 (or higher)! ***","3":"- ENH: Add \"Forever\" and \"Never ever\" choices that persist the response for the current file across Vim session.\r\n- ENH: If ShowTrailingWhitespace.vim (version 1.10 or higher) is installed, offer a \"Never ever highlight\" choice that turns off highlighting for the current file persistently across Vim sessions.\r\n- CHG: Make asking for action (instead of aborting) the default action, now that we offer many more choices, and the whole persistent recall of responses only works there. It's also more friendly and transparent towards first-time users of the plugin. To restore the original behavior: > let g:DeleteTrailingWhitespace_Action = 'abort'\r\n- CHG: g:DeleteTrailingWhitespace_ChoiceAffectsHighlighting now is a List of possible responses that if missing will keep the highlighting for that particular response.\r\n- BUG: DeleteTrailingWhitespace_Action checks window-local instead of buffer-local override. Thanks to Enno for noticing.\r\n- Add dependency to ingo-library (vimscript #4433). *** You need to separately install ingo-library (vimscript #4433) version 1.036 (or higher)! ***","package":"DeleteTrailingWhitespace-1.10.vmb.gz","4":"DeleteTrailingWhitespace-1.10.vmb.gz","src_id":"26956","5":"26956","creation_date":"1580766276","6":"1580766276"},{"0":"3967","vim_version":"7.0","1":"7.0","script_version":"1.06","2":"1.06","version_comment":"- FIX: Warning for nomodifiable buffer does not consider buffer-local b:DeleteTrailingWhitespace_Action (after version 1.05).","3":"- FIX: Warning for nomodifiable buffer does not consider buffer-local b:DeleteTrailingWhitespace_Action (after version 1.05).","package":"DeleteTrailingWhitespace-1.06.vmb.gz","4":"DeleteTrailingWhitespace-1.06.vmb.gz","src_id":"22945","5":"22945","creation_date":"1424796354","6":"1424796354"},{"0":"3967","vim_version":"7.0","1":"7.0","script_version":"1.05","2":"1.05","version_comment":"- Corner case: Avoid \"E21: Cannot make changes, 'modifiable' is off\" on a nomodifiable buffer when g:DeleteTrailingWhitespace_Action = 'delete', and instead just show a warning. Thanks to Enno Nagel for raising this issue.","3":"- Corner case: Avoid \"E21: Cannot make changes, 'modifiable' is off\" on a nomodifiable buffer when g:DeleteTrailingWhitespace_Action = 'delete', and instead just show a warning. Thanks to Enno Nagel for raising this issue.","package":"DeleteTrailingWhitespace-1.05.vmb.gz","4":"DeleteTrailingWhitespace-1.05.vmb.gz","src_id":"22694","5":"22694","creation_date":"1418415876","6":"1418415876"},{"0":"3967","vim_version":"7.0","1":"7.0","script_version":"1.04","2":"1.04","version_comment":"- Minor: Make substitute() robust against 'ignorecase'.\r\n- Minor: Correct lnum for no-modifiable buffer check.\r\n- Handle local exception regular expressions that contain a \"\/\" character. This must be escaped for the :substitute\/ command.","3":"- Minor: Make substitute() robust against 'ignorecase'.\r\n- Minor: Correct lnum for no-modifiable buffer check.\r\n- Handle local exception regular expressions that contain a \"\/\" character. This must be escaped for the :substitute\/ command.","package":"DeleteTrailingWhitespace-1.04.vmb.gz","4":"DeleteTrailingWhitespace-1.04.vmb.gz","src_id":"21194","5":"21194","creation_date":"1387051179","6":"1387051179"},{"0":"3967","vim_version":"7.0","1":"7.0","script_version":"1.03","2":"1.03","version_comment":"Handle readonly and nomodifiable buffers by printing just the warning \/ error, without the multi-line function error.","3":"Handle readonly and nomodifiable buffers by printing just the warning \/ error, without the multi-line function error.","package":"DeleteTrailingWhitespace.vba.gz","4":"DeleteTrailingWhitespace.vba.gz","src_id":"17794","5":"17794","creation_date":"1334839450","6":"1334839450"},{"0":"3967","vim_version":"7.0","1":"7.0","script_version":"1.02","2":"1.02","version_comment":"FIX: Avoid polluting search history.FIX: Avoid polluting search history.","3":"FIX: Avoid polluting search history.FIX: Avoid polluting search history.","package":"DeleteTrailingWhitespace.vba.gz","4":"DeleteTrailingWhitespace.vba.gz","src_id":"17774","5":"17774","creation_date":"1334434796","6":"1334434796"},{"0":"3967","vim_version":"7.0","1":"7.0","script_version":"1.01","2":"1.01","version_comment":"Define command with -bar so that it can be chained.","3":"Define command with -bar so that it can be chained.","package":"DeleteTrailingWhitespace.vba.gz","4":"DeleteTrailingWhitespace.vba.gz","src_id":"17713","5":"17713","creation_date":"1333531618","6":"1333531618"},{"0":"3967","vim_version":"7.0","1":"7.0","script_version":"1.00","2":"1.00","version_comment":"Initial upload","3":"Initial upload","package":"DeleteTrailingWhitespace.vba.gz","4":"DeleteTrailingWhitespace.vba.gz","src_id":"17597","5":"17597","creation_date":"1331900265","6":"1331900265"}]},"3966":{"script_id":"3966","0":"3966","script_name":"ShowTrailingWhitespace","1":"ShowTrailingWhitespace","script_type":"utility","2":"utility","summary":"Detect unwanted whitespace at the end of lines.","3":"Detect unwanted whitespace at the end of lines.","description":"DESCRIPTION\r\nThis plugin highlights whitespace at the end of each line (except when typing\r\nat the end of a line). It uses the matchadd()-function, therefore doesn't\r\ninterfere with syntax highlighting and leaves the :match command for other\r\nuses.\r\nHighlighting can be switched on\/off globally and for individual buffers. The\r\nplugin comes with exceptions for certain filetypes, where certain lines can \/\r\nmust include trailing whitespace; additional patterns can be configured.\r\n\r\nSEE ALSO\r\nMany plugins also come with a command to strip off the trailing whitespace;\r\nthis plugin separates this into the companion DeleteTrailingWhitespace.vim\r\nplugin (vimscript #3967), which can even remove the trailing whitespace\r\nautomatically on each write.\r\n\r\nTo quickly locate the occurrences of trailing whitespace, you can use the\r\ncompanion JumpToTrailingWhitespace.vim plugin (vimscript #3968).\r\n\r\nRELATED WORKS\r\nThere are already a number of plugins for this purpose, most based on this\r\nVimTip:\r\n    http:\/\/vim.wikia.com\/wiki\/Highlight_unwanted_spaces\r\nHowever, most of them use the older :match command and are not as flexible.\r\n- smartmatcheol.vim (vimscript #2635) highlights based on file extension or\r\n  name.\r\n- trailing-whitespace (vimscript #3201) uses :match.\r\n- bad-whitespace (vimscript #3735) uses :match, allows on\/off\/toggling via\r\n  commands.\r\n- Trailer Trash (vimscript #3938) uses :match.\r\n- DynamicSigns (vimscript #3965) can show whitespace errors (also mixed\r\n  indent) in the sign column.\r\n- better-whitespace (vimscript #4859) can use either :match or :syntax (with\r\n  the option of excluding the current line), and has a :StripWhitespace\r\n  command, also automatic triggering for some filetypes.\r\n- ShowSpaces (vimscript #5148) highlights spaces inside indentation, per\r\n  buffer \/ filetype.\r\n\r\nUSAGE\r\nBy default, trailing whitespace is highlighted in all Vim buffers. Some users\r\nmay want to selectively enable \/ disable this for certain filetypes, or files\r\nin a particular directory hierarchy, or toggle this on demand. Since it's\r\ndifficult to accommodate all these demands with short and easy mappings and\r\ncommands, this plugin does not define any of them, and leaves it to you to\r\ntailor the plugin to your needs. See ShowTrailingWhitespace-configuration\r\nbelow.","4":"DESCRIPTION\r\nThis plugin highlights whitespace at the end of each line (except when typing\r\nat the end of a line). It uses the matchadd()-function, therefore doesn't\r\ninterfere with syntax highlighting and leaves the :match command for other\r\nuses.\r\nHighlighting can be switched on\/off globally and for individual buffers. The\r\nplugin comes with exceptions for certain filetypes, where certain lines can \/\r\nmust include trailing whitespace; additional patterns can be configured.\r\n\r\nSEE ALSO\r\nMany plugins also come with a command to strip off the trailing whitespace;\r\nthis plugin separates this into the companion DeleteTrailingWhitespace.vim\r\nplugin (vimscript #3967), which can even remove the trailing whitespace\r\nautomatically on each write.\r\n\r\nTo quickly locate the occurrences of trailing whitespace, you can use the\r\ncompanion JumpToTrailingWhitespace.vim plugin (vimscript #3968).\r\n\r\nRELATED WORKS\r\nThere are already a number of plugins for this purpose, most based on this\r\nVimTip:\r\n    http:\/\/vim.wikia.com\/wiki\/Highlight_unwanted_spaces\r\nHowever, most of them use the older :match command and are not as flexible.\r\n- smartmatcheol.vim (vimscript #2635) highlights based on file extension or\r\n  name.\r\n- trailing-whitespace (vimscript #3201) uses :match.\r\n- bad-whitespace (vimscript #3735) uses :match, allows on\/off\/toggling via\r\n  commands.\r\n- Trailer Trash (vimscript #3938) uses :match.\r\n- DynamicSigns (vimscript #3965) can show whitespace errors (also mixed\r\n  indent) in the sign column.\r\n- better-whitespace (vimscript #4859) can use either :match or :syntax (with\r\n  the option of excluding the current line), and has a :StripWhitespace\r\n  command, also automatic triggering for some filetypes.\r\n- ShowSpaces (vimscript #5148) highlights spaces inside indentation, per\r\n  buffer \/ filetype.\r\n\r\nUSAGE\r\nBy default, trailing whitespace is highlighted in all Vim buffers. Some users\r\nmay want to selectively enable \/ disable this for certain filetypes, or files\r\nin a particular directory hierarchy, or toggle this on demand. Since it's\r\ndifficult to accommodate all these demands with short and easy mappings and\r\ncommands, this plugin does not define any of them, and leaves it to you to\r\ntailor the plugin to your needs. See ShowTrailingWhitespace-configuration\r\nbelow.","install_details":"INSTALLATION\r\nThe code is hosted in a Git repo at\r\n    https:\/\/github.com\/inkarkat\/vim-ShowTrailingWhitespace\r\nYou can use your favorite plugin manager, or \"git clone\" into a directory used\r\nfor Vim packages. Releases are on the \"stable\" branch, the latest unstable\r\ndevelopment snapshot on \"master\".\r\n\r\nThis script is also packaged as a vimball. If you have the \"gunzip\"\r\ndecompressor in your PATH, simply edit the *.vmb.gz package in Vim; otherwise,\r\ndecompress the archive first, e.g. using WinZip. Inside Vim, install by\r\nsourcing the vimball or via the :UseVimball command.\r\n    vim ShowTrailingWhitespace*.vmb.gz\r\n    :so %\r\nTo uninstall, use the :RmVimball command.\r\n\r\nDEPENDENCIES\r\n- Requires Vim 7.1 with \"matchadd()\", or Vim 7.2 or higher.\r\n- Requires the ingo-library.vim plugin (vimscript #4433), version 1.043 or\r\n  higher.\r\n\r\nCONFIGURATION\r\nFor a permanent configuration, put the following commands into your vimrc:\r\n\r\nTo change the highlighting colors (do this after any :colorscheme):\r\n    highlight ShowTrailingWhitespace ctermbg=Red guibg=Red\r\nThe default highlighting links to the \"Error\" highlight group.\r\n\r\nAs a background color is needed to highlight the whitespace, the plugin\r\ninspects the linked highlight group and switches to its foreground color if\r\nyour chosen colorscheme does not define a background color there. You can turn\r\noff this logic via:\r\n    let g:ShowTrailingWhitespace_IsAutomaticBackground = 0\r\n\r\nBy default, highlighting is enabled for all buffers, and you can (selectively)\r\ndisable it. To work from the opposite premise, launch Vim with highlighting\r\ndisabled:\r\n    let g:ShowTrailingWhitespace = 0\r\n\r\nWith regards to exceptions, the plugin offers multiple approaches: The most\r\ngeneric is a filter function where your code tells the plugin whether it\r\nshould check or ignore. By default, the plugin uses this to offer a file-based\r\nset of blacklists, one persisted and one only for the current session.\r\nAlternatively, you can use Vim's built-in functionality like :autocmd or\r\nfiletype-plugins, and invoke plugin function to enable \/ disable it from\r\nthere. These plugin functions can also be used to define custom toggle\r\ncommands or mappings, allowing you to interactively control the plugin.\r\n\r\nIn addition to toggling the highlighting on\/off via\r\ng:ShowTrailingWhitespace, the decision can also be influenced by buffer\r\nsettings or the environment. By default, buffers that are not persisted to\r\ndisk (unless they are explicitly marked as \"[Scratch]\" buffers) or not\r\nmodifiable (like user interface windows from various plugins, but note that\r\nclearing the option is usually done too late) are skipped. You can disable\r\nthis filtering:\r\n    let g:ShowTrailingWhitespace_FilterFunc = ''\r\nor install your own custom filter function instead:\r\n    let g:ShowTrailingWhitespace_FilterFunc = function('MyFunc')\r\n\r\nThe default filter also checks two blacklists:\r\n- *g:ShowTrailingWhitespace_Blacklist* (valid for the current Vim session)\r\n- *g:SHOWTRAILINGWHITESPACE_BLACKLIST* (persisted across Vim sessions)\r\nYou can define your own commands or mappings to add or remove the current file\r\nto that blacklist:\r\n    command! -bar ShowTrailingWhitespaceBlacklistForSession  call ShowTrailingWhitespace#Filter#BlacklistFile(0)\r\n    command! -bar ShowTrailingWhitespaceBlacklistPermanently call ShowTrailingWhitespace#Filter#BlacklistFile(1)\r\n    command! -bar ShowTrailingWhitespaceBlacklistRemoveFile  call ShowTrailingWhitespace#Filter#RemoveFileFromBlacklist()\r\n\r\nHighlighting can be enabled \/ disabled globally and for individual buffers.\r\nAnalog to the :set and :setlocal commands, you can define the following\r\ncommands:\r\n    command! -bar ShowTrailingWhitespaceOn          call ShowTrailingWhitespace#Set(1,1)\r\n    command! -bar ShowTrailingWhitespaceOff         call ShowTrailingWhitespace#Set(0,1)\r\n    command! -bar ShowTrailingWhitespaceBufferOn    call ShowTrailingWhitespace#Set(1,0)\r\n    command! -bar ShowTrailingWhitespaceBufferOff   call ShowTrailingWhitespace#Set(0,0)\r\nTo set the local highlighting back to its global value (like :set {option}<\r\ndoes), the following command can be defined:\r\n    command! -bar ShowTrailingWhitespaceBufferClear call ShowTrailingWhitespace#Reset()\r\n\r\nYou can also define a quick mapping to toggle the highlighting (here, locally;\r\nfor global toggling use ShowTrailingWhitespace#Toggle(1):\r\n    nnoremap <silent> <Leader>t$ :<C-u>call ShowTrailingWhitespace#Toggle(0)<Bar>\r\n    \\ echo (ShowTrailingWhitespace#IsSet() ?\r\n    \\   'Show trailing whitespace' :\r\n    \\   'Not showing trailing whitespace')<CR>\r\n\r\nFor some filetypes, trailing whitespace is part of the syntax or even\r\nmandatory. To disable the plugin for a filetype, put the following in a file\r\nnamed e.g. ftplugin\/{filetype}_ShowTrailingWhitespace.vim:\r\n    if ShowTrailingWhitespace#IsSet()\r\n        call ShowTrailingWhitespace#Set(0,0)\r\n    endif\r\nThe plugin already ships with some common exceptions; you can submit yours,\r\ntoo!\r\n\r\nSome filetypes need trailing whitespace only in certain places. If you don't\r\nwant to be bothered by these showing up as false positives, you may be able to\r\naugment the regular expression so that these places do not match. The\r\nShowTrailingWhitespace#SetLocalExtraPattern() function takes a regular\r\nexpression that is prepended to the pattern for the trailing whitespace\r\n('\\s\\+\\%#\\@<!$' in insert mode, '\\s\\+$' otherwise). For a certain filetype,\r\nthis is best set in a file ftplugin\/{filetype}_ShowTrailingWhitespace.vim.\r\n\r\nINTEGRATION\r\nThe ShowTrailingWhitespace#IsSet() function can be used to query the on\/off\r\nstatus for the current buffer, e.g. for use in the statusline.\r\n\r\nTo obtain the pattern for matching trailing whitespace, including any\r\nShowTrailingWhitespace-exceptions, you can use the function\r\nShowTrailingWhitespace#Pattern(0).","5":"INSTALLATION\r\nThe code is hosted in a Git repo at\r\n    https:\/\/github.com\/inkarkat\/vim-ShowTrailingWhitespace\r\nYou can use your favorite plugin manager, or \"git clone\" into a directory used\r\nfor Vim packages. Releases are on the \"stable\" branch, the latest unstable\r\ndevelopment snapshot on \"master\".\r\n\r\nThis script is also packaged as a vimball. If you have the \"gunzip\"\r\ndecompressor in your PATH, simply edit the *.vmb.gz package in Vim; otherwise,\r\ndecompress the archive first, e.g. using WinZip. Inside Vim, install by\r\nsourcing the vimball or via the :UseVimball command.\r\n    vim ShowTrailingWhitespace*.vmb.gz\r\n    :so %\r\nTo uninstall, use the :RmVimball command.\r\n\r\nDEPENDENCIES\r\n- Requires Vim 7.1 with \"matchadd()\", or Vim 7.2 or higher.\r\n- Requires the ingo-library.vim plugin (vimscript #4433), version 1.043 or\r\n  higher.\r\n\r\nCONFIGURATION\r\nFor a permanent configuration, put the following commands into your vimrc:\r\n\r\nTo change the highlighting colors (do this after any :colorscheme):\r\n    highlight ShowTrailingWhitespace ctermbg=Red guibg=Red\r\nThe default highlighting links to the \"Error\" highlight group.\r\n\r\nAs a background color is needed to highlight the whitespace, the plugin\r\ninspects the linked highlight group and switches to its foreground color if\r\nyour chosen colorscheme does not define a background color there. You can turn\r\noff this logic via:\r\n    let g:ShowTrailingWhitespace_IsAutomaticBackground = 0\r\n\r\nBy default, highlighting is enabled for all buffers, and you can (selectively)\r\ndisable it. To work from the opposite premise, launch Vim with highlighting\r\ndisabled:\r\n    let g:ShowTrailingWhitespace = 0\r\n\r\nWith regards to exceptions, the plugin offers multiple approaches: The most\r\ngeneric is a filter function where your code tells the plugin whether it\r\nshould check or ignore. By default, the plugin uses this to offer a file-based\r\nset of blacklists, one persisted and one only for the current session.\r\nAlternatively, you can use Vim's built-in functionality like :autocmd or\r\nfiletype-plugins, and invoke plugin function to enable \/ disable it from\r\nthere. These plugin functions can also be used to define custom toggle\r\ncommands or mappings, allowing you to interactively control the plugin.\r\n\r\nIn addition to toggling the highlighting on\/off via\r\ng:ShowTrailingWhitespace, the decision can also be influenced by buffer\r\nsettings or the environment. By default, buffers that are not persisted to\r\ndisk (unless they are explicitly marked as \"[Scratch]\" buffers) or not\r\nmodifiable (like user interface windows from various plugins, but note that\r\nclearing the option is usually done too late) are skipped. You can disable\r\nthis filtering:\r\n    let g:ShowTrailingWhitespace_FilterFunc = ''\r\nor install your own custom filter function instead:\r\n    let g:ShowTrailingWhitespace_FilterFunc = function('MyFunc')\r\n\r\nThe default filter also checks two blacklists:\r\n- *g:ShowTrailingWhitespace_Blacklist* (valid for the current Vim session)\r\n- *g:SHOWTRAILINGWHITESPACE_BLACKLIST* (persisted across Vim sessions)\r\nYou can define your own commands or mappings to add or remove the current file\r\nto that blacklist:\r\n    command! -bar ShowTrailingWhitespaceBlacklistForSession  call ShowTrailingWhitespace#Filter#BlacklistFile(0)\r\n    command! -bar ShowTrailingWhitespaceBlacklistPermanently call ShowTrailingWhitespace#Filter#BlacklistFile(1)\r\n    command! -bar ShowTrailingWhitespaceBlacklistRemoveFile  call ShowTrailingWhitespace#Filter#RemoveFileFromBlacklist()\r\n\r\nHighlighting can be enabled \/ disabled globally and for individual buffers.\r\nAnalog to the :set and :setlocal commands, you can define the following\r\ncommands:\r\n    command! -bar ShowTrailingWhitespaceOn          call ShowTrailingWhitespace#Set(1,1)\r\n    command! -bar ShowTrailingWhitespaceOff         call ShowTrailingWhitespace#Set(0,1)\r\n    command! -bar ShowTrailingWhitespaceBufferOn    call ShowTrailingWhitespace#Set(1,0)\r\n    command! -bar ShowTrailingWhitespaceBufferOff   call ShowTrailingWhitespace#Set(0,0)\r\nTo set the local highlighting back to its global value (like :set {option}<\r\ndoes), the following command can be defined:\r\n    command! -bar ShowTrailingWhitespaceBufferClear call ShowTrailingWhitespace#Reset()\r\n\r\nYou can also define a quick mapping to toggle the highlighting (here, locally;\r\nfor global toggling use ShowTrailingWhitespace#Toggle(1):\r\n    nnoremap <silent> <Leader>t$ :<C-u>call ShowTrailingWhitespace#Toggle(0)<Bar>\r\n    \\ echo (ShowTrailingWhitespace#IsSet() ?\r\n    \\   'Show trailing whitespace' :\r\n    \\   'Not showing trailing whitespace')<CR>\r\n\r\nFor some filetypes, trailing whitespace is part of the syntax or even\r\nmandatory. To disable the plugin for a filetype, put the following in a file\r\nnamed e.g. ftplugin\/{filetype}_ShowTrailingWhitespace.vim:\r\n    if ShowTrailingWhitespace#IsSet()\r\n        call ShowTrailingWhitespace#Set(0,0)\r\n    endif\r\nThe plugin already ships with some common exceptions; you can submit yours,\r\ntoo!\r\n\r\nSome filetypes need trailing whitespace only in certain places. If you don't\r\nwant to be bothered by these showing up as false positives, you may be able to\r\naugment the regular expression so that these places do not match. The\r\nShowTrailingWhitespace#SetLocalExtraPattern() function takes a regular\r\nexpression that is prepended to the pattern for the trailing whitespace\r\n('\\s\\+\\%#\\@<!$' in insert mode, '\\s\\+$' otherwise). For a certain filetype,\r\nthis is best set in a file ftplugin\/{filetype}_ShowTrailingWhitespace.vim.\r\n\r\nINTEGRATION\r\nThe ShowTrailingWhitespace#IsSet() function can be used to query the on\/off\r\nstatus for the current buffer, e.g. for use in the statusline.\r\n\r\nTo obtain the pattern for matching trailing whitespace, including any\r\nShowTrailingWhitespace-exceptions, you can use the function\r\nShowTrailingWhitespace#Pattern(0).","first_name":"Ingo","6":"Ingo","last_name":"Karkat","7":"Karkat","releases":[{"0":"3966","vim_version":"7.0","1":"7.0","script_version":"1.12","2":"1.12","version_comment":"- More robust and efficient iteration through visible windows through |win_execute()| (where available).\r\n- Add (hard, previously only optional) dependency to ingo-library (vimscript #4433).\r\n- diff filetype: Exclude patch instructions that just consist of # + single space. *** You need to separately install ingo-library (vimscript #4433) version 1.043 (or higher)! ***","3":"- More robust and efficient iteration through visible windows through |win_execute()| (where available).\r\n- Add (hard, previously only optional) dependency to ingo-library (vimscript #4433).\r\n- diff filetype: Exclude patch instructions that just consist of # + single space. *** You need to separately install ingo-library (vimscript #4433) version 1.043 (or higher)! ***","package":"ShowTrailingWhitespace-1.12.vmb.gz","4":"ShowTrailingWhitespace-1.12.vmb.gz","src_id":"28244","5":"28244","creation_date":"1667322276","6":"1667322276"},{"0":"3966","vim_version":"7.0","1":"7.0","script_version":"1.11","2":"1.11","version_comment":"- Neovim does not have the TerminalOpen event; don't use it then, to avoid startup errors. (Patch by subnut.)\r\n- Exempt the \"xxd\" filetype used e.g. by the Hexman plugin (vimscript #666).\r\n- ENH: The plugin now inspects the linked highlight group and switches to its foreground color if your chosen colorscheme does not define a background color there, to avoid that no trailing whitespace highlighting can be seen. This logic can be disabled through g:ShowTrailingWhitespace_IsAutomaticBackground. Thanks to subnut for raising this issue, providing a suggestion on how to fix that and a patch for Neovim compatibility.","3":"- Neovim does not have the TerminalOpen event; don't use it then, to avoid startup errors. (Patch by subnut.)\r\n- Exempt the \"xxd\" filetype used e.g. by the Hexman plugin (vimscript #666).\r\n- ENH: The plugin now inspects the linked highlight group and switches to its foreground color if your chosen colorscheme does not define a background color there, to avoid that no trailing whitespace highlighting can be seen. This logic can be disabled through g:ShowTrailingWhitespace_IsAutomaticBackground. Thanks to subnut for raising this issue, providing a suggestion on how to fix that and a patch for Neovim compatibility.","package":"ShowTrailingWhitespace-1.11.vmb.gz","4":"ShowTrailingWhitespace-1.11.vmb.gz","src_id":"27411","5":"27411","creation_date":"1608568967","6":"1608568967"},{"0":"3966","vim_version":"7.0","1":"7.0","script_version":"1.10","2":"1.10","version_comment":"- The default g:ShowTrailingWhitespace_FilterFunc now also skips highlighting in |terminal-window|s. Unfortunately, this requires a special hook, as the 'buftype' gets set too late.\r\n- ENH: Make the default filter also consider session-local and persistent blacklists for files where highlighting should be off. Offer public functions to implement custom commands or mappings for blacklist management. See |ShowTrailingWhitespace-blacklist| for details.\r\n- FIX: Avoid creating jump when enabling \/ setting a local extra pattern.\r\n  *** You need to separately install ingo-library (vimscript #4433) version 1.036 (or higher) in order to use the blacklist feature! ***","3":"- The default g:ShowTrailingWhitespace_FilterFunc now also skips highlighting in |terminal-window|s. Unfortunately, this requires a special hook, as the 'buftype' gets set too late.\r\n- ENH: Make the default filter also consider session-local and persistent blacklists for files where highlighting should be off. Offer public functions to implement custom commands or mappings for blacklist management. See |ShowTrailingWhitespace-blacklist| for details.\r\n- FIX: Avoid creating jump when enabling \/ setting a local extra pattern.\r\n  *** You need to separately install ingo-library (vimscript #4433) version 1.036 (or higher) in order to use the blacklist feature! ***","package":"ShowTrailingWhitespace-1.10.vmb.gz","4":"ShowTrailingWhitespace-1.10.vmb.gz","src_id":"27234","5":"27234","creation_date":"1594522706","6":"1594522706"},{"0":"3966","vim_version":"7.0","1":"7.0","script_version":"1.03","2":"1.03","version_comment":"- Exempt the \"unite\" filetype used by the Unite plugin (vimscript #3396). Thanks to Fernando \"Firef0x\" G.P. da Silva for the patch.","3":"- Exempt the \"unite\" filetype used by the Unite plugin (vimscript #3396). Thanks to Fernando \"Firef0x\" G.P. da Silva for the patch.","package":"ShowTrailingWhitespace-1.03.vmb.gz","4":"ShowTrailingWhitespace-1.03.vmb.gz","src_id":"23061","5":"23061","creation_date":"1426783527","6":"1426783527"},{"0":"3966","vim_version":"7.0","1":"7.0","script_version":"1.02","2":"1.02","version_comment":"- Add whitespace exception for the \"markdown\" filetype.\r\n- Make ShowTrailingWhitespace#IsSet() also handle Vim 7.0\/1 where the g:ShowTrailingWhitespace variable is not set. Return 0 instead of causing a function abort.\r\n- ENH: Keep previous (last accessed) window on :windo.","3":"- Add whitespace exception for the \"markdown\" filetype.\r\n- Make ShowTrailingWhitespace#IsSet() also handle Vim 7.0\/1 where the g:ShowTrailingWhitespace variable is not set. Return 0 instead of causing a function abort.\r\n- ENH: Keep previous (last accessed) window on :windo.","package":"ShowTrailingWhitespace-1.02.vmb.gz","4":"ShowTrailingWhitespace-1.02.vmb.gz","src_id":"22992","5":"22992","creation_date":"1425845344","6":"1425845344"},{"0":"3966","vim_version":"7.0","1":"7.0","script_version":"1.01","2":"1.01","version_comment":"- Minor: Also exclude quickfix and help buffers from detection.\r\n- Add whitespace exception for the \"dosbatch\" filetype.","3":"- Minor: Also exclude quickfix and help buffers from detection.\r\n- Add whitespace exception for the \"dosbatch\" filetype.","package":"ShowTrailingWhitespace-1.01.vmb.gz","4":"ShowTrailingWhitespace-1.01.vmb.gz","src_id":"21196","5":"21196","creation_date":"1387051561","6":"1387051561"},{"0":"3966","vim_version":"7.0","1":"7.0","script_version":"1.00","2":"1.00","version_comment":"Initial upload","3":"Initial upload","package":"ShowTrailingWhitespace.vba.gz","4":"ShowTrailingWhitespace.vba.gz","src_id":"17596","5":"17596","creation_date":"1331900164","6":"1331900164"}]},"3965":{"script_id":"3965","0":"3965","script_name":"DynamicSigns","1":"DynamicSigns","script_type":"ftplugin","2":"ftplugin","summary":"Use Signs for different things","3":"Use Signs for different things","description":"This plugin enables you to use signs |sign-support| for different things. For\r\nexample you can use signs to display Indentation-Levels, display line\r\nwhitespace errors, display marks |mark-motion|, display the differences\r\nbetween the current editing file and the file on disk or whenever an\r\nexpression evalutates true (similar to how fold-expressions work |fold-expr|)\r\n\r\nAll you need to do, is configure the plugin by setting some configuration\r\nvariables and run |:Signs|","4":"This plugin enables you to use signs |sign-support| for different things. For\r\nexample you can use signs to display Indentation-Levels, display line\r\nwhitespace errors, display marks |mark-motion|, display the differences\r\nbetween the current editing file and the file on disk or whenever an\r\nexpression evalutates true (similar to how fold-expressions work |fold-expr|)\r\n\r\nAll you need to do, is configure the plugin by setting some configuration\r\nvariables and run |:Signs|","install_details":"unzip the zip archive into your ~\/.vim directory on unix or $VIM\/vimfiles directory on Windows. Afterwards run the :helptags command, \r\ne.g. :helptags ~\/.vim\/doc (Unix)\r\n:helptags $VIM\/vimfiles\/doc (Windows)\r\n\r\nread the help at :h DynamicSigns.txt","5":"unzip the zip archive into your ~\/.vim directory on unix or $VIM\/vimfiles directory on Windows. Afterwards run the :helptags command, \r\ne.g. :helptags ~\/.vim\/doc (Unix)\r\n:helptags $VIM\/vimfiles\/doc (Windows)\r\n\r\nread the help at :h DynamicSigns.txt","first_name":"Christian","6":"Christian","last_name":"Brabandt","7":"Brabandt","releases":[{"0":"3965","vim_version":"7.3","1":"7.3","script_version":"0.2","2":"0.2","version_comment":"Initial upload","3":"Initial upload","package":"DynamicSigns.zip","4":"DynamicSigns.zip","src_id":"17595","5":"17595","creation_date":"1331851384","6":"1331851384"}]},"3964":{"script_id":"3964","0":"3964","script_name":"vim less","1":"vim less","script_type":"syntax","2":"syntax","summary":"less support for vim","3":"less support for vim","description":"update: \r\nI just try my best to enhance this script as follows:\r\n1) better syntax highlight. \r\n2) indent support (just use the css indent file is enough actually. >.<).\r\n3) auto compile file.less to file.css, and echo any errors if you have lessc installed.\r\n\r\nThe script is now available on github. https:\/\/github.com\/KohPoll\/vim-less.git\r\n\r\nI just begin to use less(http:\/\/lesscss.org). It can help us to write css more productivity. \r\nBut I just can not find a less syntax file for vim, so I wrote a simple one.\r\nI am just new to vim, and this is the very first script for vim I've written. \r\nJust take your decision.","4":"update: \r\nI just try my best to enhance this script as follows:\r\n1) better syntax highlight. \r\n2) indent support (just use the css indent file is enough actually. >.<).\r\n3) auto compile file.less to file.css, and echo any errors if you have lessc installed.\r\n\r\nThe script is now available on github. https:\/\/github.com\/KohPoll\/vim-less.git\r\n\r\nI just begin to use less(http:\/\/lesscss.org). It can help us to write css more productivity. \r\nBut I just can not find a less syntax file for vim, so I wrote a simple one.\r\nI am just new to vim, and this is the very first script for vim I've written. \r\nJust take your decision.","install_details":"If you have pathogen(http:\/\/www.vim.org\/scripts\/script.php?script_id=2332) install, just cd to your vim configuration folder(~\/.vim\/bundle\/, or PATH-OF-VIM\/vimfiles\/bundle\/),and execute git clone https:\/\/github.com\/KohPoll\/vim-less.git\r\nIf you do not, then download it, unzip it, and copy all this stuffs into the correspond folders.of your vim configuration folder(that means ~\/.vim\/, on windows, it may be PATH-OF-VIM\/vimfiles\/).\r\n ","5":"If you have pathogen(http:\/\/www.vim.org\/scripts\/script.php?script_id=2332) install, just cd to your vim configuration folder(~\/.vim\/bundle\/, or PATH-OF-VIM\/vimfiles\/bundle\/),and execute git clone https:\/\/github.com\/KohPoll\/vim-less.git\r\nIf you do not, then download it, unzip it, and copy all this stuffs into the correspond folders.of your vim configuration folder(that means ~\/.vim\/, on windows, it may be PATH-OF-VIM\/vimfiles\/).\r\n ","first_name":"Kong","6":"Kong","last_name":"Xiangpeng","7":"Xiangpeng","releases":[{"0":"3964","vim_version":"7.0","1":"7.0","script_version":"2.1","2":"2.1","version_comment":"enhance the mixin syntax definition to support the less 'guard expression' feature.","3":"enhance the mixin syntax definition to support the less 'guard expression' feature.","package":"vim-less.zip","4":"vim-less.zip","src_id":"18367","5":"18367","creation_date":"1344085052","6":"1344085052"},{"0":"3964","vim_version":"7.0","1":"7.0","script_version":"2.0","2":"2.0","version_comment":"enhance many stuff. better syntax highlight, indent support, auto compile less file when saving.","3":"enhance many stuff. better syntax highlight, indent support, auto compile less file when saving.","package":"vim-less.zip","4":"vim-less.zip","src_id":"18366","5":"18366","creation_date":"1343985447","6":"1343985447"},{"0":"3964","vim_version":"7.0","1":"7.0","script_version":"1.1","2":"1.1","version_comment":"My fault. I did not pay attention to the filetype.This verson convert the filetype to unix(not dos).","3":"My fault. I did not pay attention to the filetype.This verson convert the filetype to unix(not dos).","package":"less.vim","4":"less.vim","src_id":"17803","5":"17803","creation_date":"1334986465","6":"1334986465"},{"0":"3964","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"less.vim","4":"less.vim","src_id":"17588","5":"17588","creation_date":"1331538146","6":"1331538146"}]},"3963":{"script_id":"3963","0":"3963","script_name":"Colorizer","1":"Colorizer","script_type":"ftplugin","2":"ftplugin","summary":"highlight color codes and names","3":"highlight color codes and names","description":"This plugin is based on the css_color plugin by Nikolaus Hofer. The idea is to highlight color names and codes in the same color that they represent.\r\n\r\nThe plugin understands the W3-Colors (used for CSS files for example), the Color names from the X11 Window System and also codes in hex notation, like #FF0000 (which represents Red in the RGB color system). Additionally, it supports the CSS color specifications, e.g. rgb(RR,GG,BB) color representation in either absolutely values or as percentage and also the HVL Color representation like hvl(H,V,L)\r\n\r\nIt works best in the gui version of Vim, but the plugin also supports 256 and 88 color terminals and translates the colors to those supported by the terminal. 16 and 8 color terminals should work theoretically too, but hasn't been widely tested. Note, that translating the colors to the terminal might impose a performance penalty, depending on the terminal type and the number of matches in the file.\r\n\r\nScreenshot: http:\/\/www.256bit.org\/~chrisbra\/Colorizer.png","4":"This plugin is based on the css_color plugin by Nikolaus Hofer. The idea is to highlight color names and codes in the same color that they represent.\r\n\r\nThe plugin understands the W3-Colors (used for CSS files for example), the Color names from the X11 Window System and also codes in hex notation, like #FF0000 (which represents Red in the RGB color system). Additionally, it supports the CSS color specifications, e.g. rgb(RR,GG,BB) color representation in either absolutely values or as percentage and also the HVL Color representation like hvl(H,V,L)\r\n\r\nIt works best in the gui version of Vim, but the plugin also supports 256 and 88 color terminals and translates the colors to those supported by the terminal. 16 and 8 color terminals should work theoretically too, but hasn't been widely tested. Note, that translating the colors to the terminal might impose a performance penalty, depending on the terminal type and the number of matches in the file.\r\n\r\nScreenshot: http:\/\/www.256bit.org\/~chrisbra\/Colorizer.png","install_details":"1) open the .vmb file with Vim\r\n2) source the file (:so %)\r\n3) restart Vim\r\n4) read the help at :h Colorizer","5":"1) open the .vmb file with Vim\r\n2) source the file (:so %)\r\n3) restart Vim\r\n4) read the help at :h Colorizer","first_name":"Christian","6":"Christian","last_name":"Brabandt","7":"Brabandt","releases":[{"0":"3963","vim_version":"7.3","1":"7.3","script_version":"10","2":"10","version_comment":"- Also highlight Ansi Term sequences\n- Match colornames using the \"old\" RE Engine, if Vim supports it.\n- Make |:RGB2Xterm| output the color name in its color\n- Rename |:RGB2Xterm| to |:RGB2Term|\n- Highlight Taskwarrior file\n- Code refactoring\n- Make |:ColorSwapFgBg| work as expected (did not always toggle reliably\n  between all states)\n- Correctly parse Ansi Term colors\n- |:Term2RGB|\n- Highlight Vim color files correctly\n- merge colorhighlight plugin https:\/\/github.com\/blueyed\/colorhighlight.vim\n(automatically uploaded)","3":"- Also highlight Ansi Term sequences\n- Match colornames using the \"old\" RE Engine, if Vim supports it.\n- Make |:RGB2Xterm| output the color name in its color\n- Rename |:RGB2Xterm| to |:RGB2Term|\n- Highlight Taskwarrior file\n- Code refactoring\n- Make |:ColorSwapFgBg| work as expected (did not always toggle reliably\n  between all states)\n- Correctly parse Ansi Term colors\n- |:Term2RGB|\n- Highlight Vim color files correctly\n- merge colorhighlight plugin https:\/\/github.com\/blueyed\/colorhighlight.vim\n(automatically uploaded)","package":"Colorizer-0.10.vmb","4":"Colorizer-0.10.vmb","src_id":"21679","5":"21679","creation_date":"1395958439","6":"1395958439"},{"0":"3963","vim_version":"7.3","1":"7.3","script_version":"9","2":"9","version_comment":"- https:\/\/github.com\/chrisbra\/color_highlight\/issues\/15 (rgba highlighting\n  didn't work for floating point value of alpha, reported by LiTuX.S, thanks!)\n- https:\/\/github.com\/chrisbra\/color_highlight\/issues\/16 (rgb() pattern did\n  match too much, reported by taecilla, thanks!)\n- https:\/\/github.com\/chrisbra\/color_highlight\/issues\/19 (error on calling\n  ColorWinEnter() command, reported by wedgwood, thanks!)\n- https:\/\/github.com\/chrisbra\/color_highlight\/issues\/20 and\n  https:\/\/github.com\/chrisbra\/color_highlight\/issues\/21\n  (also color on split commands, reported by wedgwood and Andri M\u00c3\u0083\u00c6\u0092\u00c3\u0082\u00c2\u00b6ll, Thanks!)\n- https:\/\/github.com\/chrisbra\/color_highlight\/issues\/22 (Make sure, patterns\n  like white-space won't get colored, reported by Andri M\u00c3\u0083\u00c6\u0092\u00c3\u0082\u00c2\u00b6ll, Thanks!)\n- https:\/\/github.com\/chrisbra\/color_highlight\/issues\/23 (ColorToggle got\n  confused when several windows with highlighting exists, reported by Andri\n  M\u00c3\u0083\u00c6\u0092\u00c3\u0082\u00c2\u00b6ll, Thanks!)\n- https:\/\/github.com\/chrisbra\/color_highlight\/issues\/24 (turning off coloring\n  should also remove the autocommands, reported by Andri M\u00c3\u0083\u00c6\u0092\u00c3\u0082\u00c2\u00b6ll, Thanks!)\n(automatically uploaded)","3":"- https:\/\/github.com\/chrisbra\/color_highlight\/issues\/15 (rgba highlighting\n  didn't work for floating point value of alpha, reported by LiTuX.S, thanks!)\n- https:\/\/github.com\/chrisbra\/color_highlight\/issues\/16 (rgb() pattern did\n  match too much, reported by taecilla, thanks!)\n- https:\/\/github.com\/chrisbra\/color_highlight\/issues\/19 (error on calling\n  ColorWinEnter() command, reported by wedgwood, thanks!)\n- https:\/\/github.com\/chrisbra\/color_highlight\/issues\/20 and\n  https:\/\/github.com\/chrisbra\/color_highlight\/issues\/21\n  (also color on split commands, reported by wedgwood and Andri M\u00c3\u0083\u00c6\u0092\u00c3\u0082\u00c2\u00b6ll, Thanks!)\n- https:\/\/github.com\/chrisbra\/color_highlight\/issues\/22 (Make sure, patterns\n  like white-space won't get colored, reported by Andri M\u00c3\u0083\u00c6\u0092\u00c3\u0082\u00c2\u00b6ll, Thanks!)\n- https:\/\/github.com\/chrisbra\/color_highlight\/issues\/23 (ColorToggle got\n  confused when several windows with highlighting exists, reported by Andri\n  M\u00c3\u0083\u00c6\u0092\u00c3\u0082\u00c2\u00b6ll, Thanks!)\n- https:\/\/github.com\/chrisbra\/color_highlight\/issues\/24 (turning off coloring\n  should also remove the autocommands, reported by Andri M\u00c3\u0083\u00c6\u0092\u00c3\u0082\u00c2\u00b6ll, Thanks!)\n(automatically uploaded)","package":"Colorizer-0.9.vmb","4":"Colorizer-0.9.vmb","src_id":"20647","5":"20647","creation_date":"1376511317","6":"1376511317"},{"0":"3963","vim_version":"7.3","1":"7.3","script_version":"8","2":"8","version_comment":"- https:\/\/github.com\/chrisbra\/color_highlight\/issues\/13 (colorizing should not\n  stop at word-boundaries, reported by teschmitz, thanks!)\n- https:\/\/github.com\/chrisbra\/color_highlight\/issues\/14 (convert highlighting\n  to syntax groups, so TOhtml works, reported by teschmitz, thanks!)\n(automatically uploaded)","3":"- https:\/\/github.com\/chrisbra\/color_highlight\/issues\/13 (colorizing should not\n  stop at word-boundaries, reported by teschmitz, thanks!)\n- https:\/\/github.com\/chrisbra\/color_highlight\/issues\/14 (convert highlighting\n  to syntax groups, so TOhtml works, reported by teschmitz, thanks!)\n(automatically uploaded)","package":"Colorizer-0.8.vmb","4":"Colorizer-0.8.vmb","src_id":"19185","5":"19185","creation_date":"1355520906","6":"1355520906"},{"0":"3963","vim_version":"7.3","1":"7.3","script_version":"7","2":"7","version_comment":"- Highlight rgb colors with whitespace after comma (reported by sergey-vlasov\n  in https:\/\/github.com\/chrisbra\/color_highlight\/issues\/12, thanks!)\n- Save and restore the search register, so the plugin doesn't clobber it\n- check for 'ed' and 'gd' defaults\n(automatically uploaded)","3":"- Highlight rgb colors with whitespace after comma (reported by sergey-vlasov\n  in https:\/\/github.com\/chrisbra\/color_highlight\/issues\/12, thanks!)\n- Save and restore the search register, so the plugin doesn't clobber it\n- check for 'ed' and 'gd' defaults\n(automatically uploaded)","package":"Colorizer-0.7.vmb","4":"Colorizer-0.7.vmb","src_id":"18312","5":"18312","creation_date":"1343248715","6":"1343248715"},{"0":"3963","vim_version":"7.3","1":"7.3","script_version":"6","2":"6","version_comment":"- Fix various issues with hsl coloring (reported by teschmitz in https:\/\/github.com\/chrisbra\/color_highlight\/issues\/9, thanks!)\n- Make it possible, to skip coloring comments (reported by teschmitz in https:\/\/github.com\/chrisbra\/color_highlight\/issues\/10, thanks!)\n- search highlighting should overrule color highlighting(reported by teschmitz in https:\/\/github.com\/chrisbra\/color_highlight\/issues\/11, thanks!)\n- updated documentation (suggested by teschmitz, thanks!)\n(automatically uploaded)","3":"- Fix various issues with hsl coloring (reported by teschmitz in https:\/\/github.com\/chrisbra\/color_highlight\/issues\/9, thanks!)\n- Make it possible, to skip coloring comments (reported by teschmitz in https:\/\/github.com\/chrisbra\/color_highlight\/issues\/10, thanks!)\n- search highlighting should overrule color highlighting(reported by teschmitz in https:\/\/github.com\/chrisbra\/color_highlight\/issues\/11, thanks!)\n- updated documentation (suggested by teschmitz, thanks!)\n(automatically uploaded)","package":"Colorizer-0.6.vmb","4":"Colorizer-0.6.vmb","src_id":"17985","5":"17985","creation_date":"1337281537","6":"1337281537"},{"0":"3963","vim_version":"7.3","1":"7.3","script_version":"5","2":"5","version_comment":"Fix issue 7 (reported by teschmitz in https:\/\/github.com\/chrisbra\/color_highlight\/issues\/7, thanks!)\n(automatically uploaded)","3":"Fix issue 7 (reported by teschmitz in https:\/\/github.com\/chrisbra\/color_highlight\/issues\/7, thanks!)\n(automatically uploaded)","package":"Colorizer-0.5.vmb","4":"Colorizer-0.5.vmb","src_id":"17708","5":"17708","creation_date":"1333459255","6":"1333459255"},{"0":"3963","vim_version":"7.3","1":"7.3","script_version":"4","2":"4","version_comment":"- |:ColorSwapFgBg| (suggested by teschmitz, in https:\/\/github.com\/chrisbra\/color_highlight\/issues\/3, thanks!)\n- make automatic color loading work (reported by wedgwood in https:\/\/github.com\/chrisbra\/color_highlight\/issues\/6, thanks!) |Colorizer-auto| and |Colorizer-hl-ft|\n- more documentation updates\n- added Mappings (suggested by Ingo Karkat, thanks!) |Colorizer-maps|\n- prevent highlighting of color names (suggested by Tarlika Schmitz in https:\/\/github.com\/chrisbra\/color_highlight\/issues\/5, thanks!) |Colorizer-hl-names|\n- enable filetype specific autocommands, so that for certain filetypes colors are highlighted automatically |Colorizer-hl-ft| (suggested by Tarlika Schmitz, thanks!)\n(automatically uploaded)","3":"- |:ColorSwapFgBg| (suggested by teschmitz, in https:\/\/github.com\/chrisbra\/color_highlight\/issues\/3, thanks!)\n- make automatic color loading work (reported by wedgwood in https:\/\/github.com\/chrisbra\/color_highlight\/issues\/6, thanks!) |Colorizer-auto| and |Colorizer-hl-ft|\n- more documentation updates\n- added Mappings (suggested by Ingo Karkat, thanks!) |Colorizer-maps|\n- prevent highlighting of color names (suggested by Tarlika Schmitz in https:\/\/github.com\/chrisbra\/color_highlight\/issues\/5, thanks!) |Colorizer-hl-names|\n- enable filetype specific autocommands, so that for certain filetypes colors are highlighted automatically |Colorizer-hl-ft| (suggested by Tarlika Schmitz, thanks!)\n(automatically uploaded)","package":"Colorizer-0.4.vmb","4":"Colorizer-0.4.vmb","src_id":"17650","5":"17650","creation_date":"1332533873","6":"1332533873"},{"0":"3963","vim_version":"7.3","1":"7.3","script_version":"3","2":"3","version_comment":"- Use the g:colorizer_fgcontrast variable to have lesser contrast between foreground and background colors (patch by Ingo Karkat, thanks!)\n- gvim did not color rgb(...) codes\n- did not correctly highlight 3 letter color codes (issue https:\/\/github.com\/chrisbra\/color_highlight\/issues\/1, reported by Taybin Rutkin, thanks!)\n- support autoloading (requested by Ingo Karkat, thanks!)\n- add |GLVS| support\n- |:ColorContrast| to interactively switch between contrast settings (suggested by Ingo Karkat, thanks!)\n(automatically uploaded)","3":"- Use the g:colorizer_fgcontrast variable to have lesser contrast between foreground and background colors (patch by Ingo Karkat, thanks!)\n- gvim did not color rgb(...) codes\n- did not correctly highlight 3 letter color codes (issue https:\/\/github.com\/chrisbra\/color_highlight\/issues\/1, reported by Taybin Rutkin, thanks!)\n- support autoloading (requested by Ingo Karkat, thanks!)\n- add |GLVS| support\n- |:ColorContrast| to interactively switch between contrast settings (suggested by Ingo Karkat, thanks!)\n(automatically uploaded)","package":"color_highlight-0.3.vmb","4":"color_highlight-0.3.vmb","src_id":"17594","5":"17594","creation_date":"1331840628","6":"1331840628"},{"0":"3963","vim_version":"7.3","1":"7.3","script_version":"0.2","2":"0.2","version_comment":"Initial upload","3":"Initial upload","package":"color_highlight-0.2.vmb","4":"color_highlight-0.2.vmb","src_id":"17577","5":"17577","creation_date":"1331299864","6":"1331299864"}]},"3962":{"script_id":"3962","0":"3962","script_name":"hammer.vim","1":"hammer.vim","script_type":"utility","2":"utility","summary":"Transform your markup language of choice to HTML, and open the transformed HTML.","3":"Transform your markup language of choice to HTML, and open the transformed HTML.","description":"\r\nHammer is a Vim plugin written (mostly) in Ruby.  It can be used to transform your markup language\r\nof choice to HTML, and open the transformed HTML in whatever your favorite browser is.\r\n\r\nIt supports a large number of markup languages out of box but it also supports   adding custom\r\nrenderers for markup languages it does not support.\r\n\r\nIt has support for multiple different layouts (with one styled like the GitHub   README layout). You\r\ncan use your favorite template language to draw up your own   layouts (ERB, HAML, \u00e2\u0080\u00a6). Layouts are\r\npassed the rendered HTML as a partial.\r\n\r\nPeople familiar with Ruby web development should feel right at home with the layout & partial style\r\ntemplates.\r\n","4":"\r\nHammer is a Vim plugin written (mostly) in Ruby.  It can be used to transform your markup language\r\nof choice to HTML, and open the transformed HTML in whatever your favorite browser is.\r\n\r\nIt supports a large number of markup languages out of box but it also supports   adding custom\r\nrenderers for markup languages it does not support.\r\n\r\nIt has support for multiple different layouts (with one styled like the GitHub   README layout). You\r\ncan use your favorite template language to draw up your own   layouts (ERB, HAML, \u00e2\u0080\u00a6). Layouts are\r\npassed the rendered HTML as a partial.\r\n\r\nPeople familiar with Ruby web development should feel right at home with the layout & partial style\r\ntemplates.\r\n","install_details":"You may need to install other dependencies for your markup language (See Above)\r\n\r\n    $ [sudo] gem install github-markup tilt coderay\r\n    $ git clone git:\/\/github.com\/robgleeson\/hammer.vim.git\r\n    $ cp -R hammer.vim\/plugin\/* $HOME\/.vim\/plugin\r\n","5":"You may need to install other dependencies for your markup language (See Above)\r\n\r\n    $ [sudo] gem install github-markup tilt coderay\r\n    $ git clone git:\/\/github.com\/robgleeson\/hammer.vim.git\r\n    $ cp -R hammer.vim\/plugin\/* $HOME\/.vim\/plugin\r\n","first_name":"Matthias","6":"Matthias","last_name":"Guenther","7":"Guenther","releases":[{"0":"3962","vim_version":"7.0","1":"7.0","script_version":"1.0.0","2":"1.0.0","version_comment":"Initial upload","3":"Initial upload","package":"hammer.vim.zip","4":"hammer.vim.zip","src_id":"17573","5":"17573","creation_date":"1331157690","6":"1331157690"}]},"3961":{"script_id":"3961","0":"3961","script_name":"flashdevelop.vim","1":"flashdevelop.vim","script_type":"ftplugin","2":"ftplugin","summary":"FlashDevelop features for VIM","3":"FlashDevelop features for VIM","description":"Check for updates on Github: https:\/\/github.com\/endel\/flashdevelop.vim\r\n\r\nThis plugin aims to provide productive features for editing ActionScript 3.0 files inside your VIM. \r\n\r\nIt\\\\\\'s actually on early development stage, but you can try it and improve it if you feel adventurous.\r\n\r\nRequirements\r\nVIM with ruby bindings. (+ruby)\r\nsprout gem (gem install sprout)\r\nvim-rooter plugin\r\nCustom ctags configuration, as described above.\r\nctags\r\nflashdevelop.vim requires a custom ctags configuration for ActionScript files.\r\n\r\nCopy the contents of support\/ctags into your ~\/.ctags\r\n\r\nFeatures currently avaible\r\nCompilation through project-sprouts. (:make)\r\nKeyboard bindings\r\n\r\nLeader + N - Create a new class\r\nLeader + R - Swap between implementation and test classes.\r\nLeader + m - Autocomplete\r\nIf cursor inside a class name:\r\nCreate a class if it\\\\\\'s name isn\\\\\\'t defined, otherwise, try to import it.","4":"Check for updates on Github: https:\/\/github.com\/endel\/flashdevelop.vim\r\n\r\nThis plugin aims to provide productive features for editing ActionScript 3.0 files inside your VIM. \r\n\r\nIt\\\\\\'s actually on early development stage, but you can try it and improve it if you feel adventurous.\r\n\r\nRequirements\r\nVIM with ruby bindings. (+ruby)\r\nsprout gem (gem install sprout)\r\nvim-rooter plugin\r\nCustom ctags configuration, as described above.\r\nctags\r\nflashdevelop.vim requires a custom ctags configuration for ActionScript files.\r\n\r\nCopy the contents of support\/ctags into your ~\/.ctags\r\n\r\nFeatures currently avaible\r\nCompilation through project-sprouts. (:make)\r\nKeyboard bindings\r\n\r\nLeader + N - Create a new class\r\nLeader + R - Swap between implementation and test classes.\r\nLeader + m - Autocomplete\r\nIf cursor inside a class name:\r\nCreate a class if it\\\\\\'s name isn\\\\\\'t defined, otherwise, try to import it.","install_details":"I recommend you to use pathogen and install it ad ~\/.vim\/bundle directory.","5":"I recommend you to use pathogen and install it ad ~\/.vim\/bundle directory.","first_name":"Endel","6":"Endel","last_name":"Dreyer","7":"Dreyer","releases":[{"0":"3961","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"endel-flashdevelop.vim-479a143.zip","4":"endel-flashdevelop.vim-479a143.zip","src_id":"17568","5":"17568","creation_date":"1331033184","6":"1331033184"}]},"3960":{"script_id":"3960","0":"3960","script_name":"tabman.vim","1":"tabman.vim","script_type":"utility","2":"utility","summary":"Tab management for Vim","3":"Tab management for Vim","description":"A small utility to help managing tab pages and the windows they contain.\r\n\r\nGit repository (with screenshot): http:\/\/github.com\/kien\/tabman.vim","4":"A small utility to help managing tab pages and the windows they contain.\r\n\r\nGit repository (with screenshot): http:\/\/github.com\/kien\/tabman.vim","install_details":"Extract the archive to ~\/.vim on Linux\/MacOSX or $HOME\\vimfiles on Windows.","5":"Extract the archive to ~\/.vim on Linux\/MacOSX or $HOME\\vimfiles on Windows.","first_name":" ","6":" ","last_name":" ","7":" ","releases":[{"0":"3960","vim_version":"7.0","1":"7.0","script_version":"1.2","2":"1.2","version_comment":"Initial upload","3":"Initial upload","package":"tabman.zip","4":"tabman.zip","src_id":"17560","5":"17560","creation_date":"1330861905","6":"1330861905"}]},"3959":{"script_id":"3959","0":"3959","script_name":"workflowish","1":"workflowish","script_type":"utility","2":"utility","summary":"ToDo manager plugin inspired by workflowy.com","3":"ToDo manager plugin inspired by workflowy.com","description":"By defining a simple syntax in Vim and using brilliant folding capabilities workflowish can simulate 99% of Workflowy's features.\r\n\r\nMain repository:  https:\/\/github.com\/lukaszkorecki\/workflowish\r\n\r\nFeatures?\r\n\r\n- searching (duh, it's, like, in Vim, broseph)\r\n- deleting (as above)\r\n- folding as a substitute for great zoom feature\r\n- notes (just add \\ in the beginning of the line to start a comment)\r\n- vimgrep for filtering lines\r\n- todos:\r\n  - a todo which is not completed is a line which starts with *\r\n  - completed todo starts with a -\r\n\r\nThanks to the long running tradition, workflowish files have .wofl extension.\r\n","4":"By defining a simple syntax in Vim and using brilliant folding capabilities workflowish can simulate 99% of Workflowy's features.\r\n\r\nMain repository:  https:\/\/github.com\/lukaszkorecki\/workflowish\r\n\r\nFeatures?\r\n\r\n- searching (duh, it's, like, in Vim, broseph)\r\n- deleting (as above)\r\n- folding as a substitute for great zoom feature\r\n- notes (just add \\ in the beginning of the line to start a comment)\r\n- vimgrep for filtering lines\r\n- todos:\r\n  - a todo which is not completed is a line which starts with *\r\n  - completed todo starts with a -\r\n\r\nThanks to the long running tradition, workflowish files have .wofl extension.\r\n","install_details":"Use Pathogen, or copy the archive contents to your ~\/.vim","5":"Use Pathogen, or copy the archive contents to your ~\/.vim","first_name":"\u0141ukasz","6":"Łukasz","last_name":"Korecki","7":"Korecki","releases":[{"0":"3959","vim_version":"7.0","1":"7.0","script_version":"0.0.2","2":"0.0.2","version_comment":"added better item counters and Workflowy plain text import","3":"added better item counters and Workflowy plain text import","package":"workflowish-0.0.2.zip","4":"workflowish-0.0.2.zip","src_id":"18072","5":"18072","creation_date":"1338538128","6":"1338538128"},{"0":"3959","vim_version":"7.2","1":"7.2","script_version":"0.0.1","2":"0.0.1","version_comment":"Initial upload","3":"Initial upload","package":"workflowish.zip","4":"workflowish.zip","src_id":"17558","5":"17558","creation_date":"1330797632","6":"1330797632"}]},"3958":{"script_id":"3958","0":"3958","script_name":"mystatusinfo.vim","1":"mystatusinfo.vim","script_type":"utility","2":"utility","summary":"Display Current Tab info on status line","3":"Display Current Tab info on status line","description":"Multiple file on different tabs becomes confusing when they have same file name, this utility displays current tab info on status line.","4":"Multiple file on different tabs becomes confusing when they have same file name, this utility displays current tab info on status line.","install_details":"Just drop it in plugin directory or paste these contents in vimrc file.\r\nset statusline=%{CurTabColor()}\\ %<%F%h%m%r%h%w%y\\ %{strftime(\\\"%c\\\",getftime(expand(\\\"%:p\\\")))}%=\\ l:%l\\,%L\\ c:%c%V\\ ps:%o\\ hex:%b\\ %P\r\n\r\nfu! CurTabColor()\r\n\r\n  let currentTab = tabpagenr()\r\n  let s_line= '(tb=' . currentTab . ')'\r\n  return s_line\r\n\r\nendf","5":"Just drop it in plugin directory or paste these contents in vimrc file.\r\nset statusline=%{CurTabColor()}\\ %<%F%h%m%r%h%w%y\\ %{strftime(\\\"%c\\\",getftime(expand(\\\"%:p\\\")))}%=\\ l:%l\\,%L\\ c:%c%V\\ ps:%o\\ hex:%b\\ %P\r\n\r\nfu! CurTabColor()\r\n\r\n  let currentTab = tabpagenr()\r\n  let s_line= '(tb=' . currentTab . ')'\r\n  return s_line\r\n\r\nendf","first_name":"vijayandra","6":"vijayandra","last_name":"singh","7":"singh","releases":[{"0":"3958","vim_version":"7.0","1":"7.0","script_version":"1.10","2":"1.10","version_comment":"Initial upload","3":"Initial upload","package":"mystatusinfo.vim","4":"mystatusinfo.vim","src_id":"17556","5":"17556","creation_date":"1330738097","6":"1330738097"}]},"3957":{"script_id":"3957","0":"3957","script_name":"calendar.vim","1":"calendar.vim","script_type":"utility","2":"utility","summary":"calendar 日历 农历","3":"calendar 日历 农历","description":"在原来的日历控件中增加农历功能,\r\n映射快捷按键是   m\r\n光标移到某天上,按m,会在状态栏显示当前的农历\r\n","4":"在原来的日历控件中增加农历功能,\r\n映射快捷按键是   m\r\n光标移到某天上,按m,会在状态栏显示当前的农历\r\n","install_details":"将文件放到plugin目录下即可","5":"将文件放到plugin目录下即可","first_name":"Zhang","6":"Zhang","last_name":"ping","7":"ping","releases":[{"0":"3957","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"calendar.vim","4":"calendar.vim","src_id":"17550","5":"17550","creation_date":"1330658116","6":"1330658116"}]},"3956":{"script_id":"3956","0":"3956","script_name":"fwk notes","1":"fwk notes","script_type":"utility","2":"utility","summary":"This plugin was created to manages your task\/notes by days\/weeks\/years.","3":"This plugin was created to manages your task\/notes by days\/weeks\/years.","description":"*fwk_notes.txt*   Manage your notes, track your tasks.\r\n                Copyright (c) 2010-2012 Sergey Vakulenko\r\n                License:      Vim License\r\n\r\n                                                                     *fwk_notes*\r\n\r\nINTRODUCTION                    |fwk_notes_introduction|\r\nINSTALLATION                    |fwk_notes_installation|\r\nUSAGE                           |fwk_notes_usage|\r\nHOTKEYS                         |fwk_notes_hotkeys|\r\nGLOBAL VARIABLES                |fwk_notes_variables|\r\nCHANGES                         |fwk_notes_changes|\r\n\r\n\r\n==============================================================================\r\nINTRODUCTION                                            *fwk_notes_introduction*\r\nThis plugin was created to manages your task\/notes by days\/weeks\/years.\r\nAlso, you can add your custom notes, of two types, static and dynamic.\r\n\r\n==============================================================================\r\nINSTALLATION                                            *fwk_notes_installation*\r\n\r\nJust drop files in zip archive to your vimfiles(win32) or .vim (linux\/ubuntu),\r\nor your custom path.\r\n\r\nPlugin files~\r\ndoc\\fwk_notes.txt\r\nplugin\\fwk_notes.vim\r\nplugin\\fwk_tab_aranger.vim\r\nplugin\\fwk_library_io_templates.vim\r\nsyntax\\notes.vim\r\ntemplates\\template_notes_common.notes\r\ntemplates\\template_notes_daily.notes\r\n\r\n\r\nAttention!~\r\nIts important that variable |g:fwk_templates_directory| contain the directory \r\nwith templates. By default, this path is $VIM\/vimfiles\/templates for win32,\r\nand $HOME\/.vim\/templates for linux. Anyway, you can change this variable to\r\nyour proper, if you want other placehold for templates.\r\n\r\n==============================================================================\r\nUSAGE                                                          *fwk_notes_usage*\r\n\r\nMain fonctionnality is to track your daily tasks and make the notes.\r\nBeside main fonctionnality (task tracking), you can create your custom notes.\r\nCustom notes can be of two types : static and dynamic.\r\nStatic notes will be created once, and then your map will only open this file.\r\nDynamic notes will be creates every new day. This is useful if you need to \r\nmake some notes each day. \r\n\r\nvideo tutorial\/demonstration\r\nhttp:\/\/www.youtube.com\/watch?v=sX93En-eQ6Y\r\n\r\n==============================================================================\r\nHOTKEYS                                                      *fwk_notes_hotkeys*\r\n\r\nMaps local to *.notes extention ~\r\n--------------------------------------------------------------------\r\nNavigation ~\r\n\\cd          open daily tasks\r\nctrl-Up      move to next day\r\nctrl-Down    move to previous day\r\n\r\nalt-Up       just to next notes section\r\nalt-Down     just to previous notes section\r\n             notes section can be:\r\n             To Do | Events | notes | Questions\r\n\r\nTasks management ~\r\nalt-d        create task ( 1), 2), 3), ... )\r\nalt-a        create subtask ( a), b), c), ...)\r\nalt-b        create sub_sub_task ( -), -), -), ...)\r\n\r\n\r\nStatus management ~\r\n\\cd          change status to |Done|. In this status, date and time will be added\r\n             automaticly.\r\n\\cp          change status to |Skip|.\r\n\\ci          change status to |Important|.\r\n\\c1          change status to |Group1|.\r\n\\c2          change status to |Group2|.\r\n\r\nYou can also apply all this commands in visual mode, by selecting the group of\r\ntasks.\r\n\r\nGlobal maps ~\r\n--------------------------------------------------------------------\r\nmap \\nd       open daily tasks. Its belong to dynamic notes.\r\n\r\n\r\nif you want to track some of your personal information \r\n(dictinnary per day, ...), you can create you proper maps:\r\n\r\n                                                                  *fwk_dynamic*\r\nDynamic notes, generate file each new day ~\r\nmap \\nv :|FwkNoteDynamic| Dictionnary<CR>\r\nmap \\nx :|FwkNoteDynamic| SpecialNotes<CR>\r\nmap \\nx :|FwkNoteDynamic| <SomeName><CR>\r\n....\r\n\r\n\r\n                                                                   *fwk_static*\r\nStatic notes, generate only one file and then reuse it: ~\r\nmap \\nv :|FwkNoteStatic| Dictionnary<CR>\r\nmap \\nx :|FwkNoteStatic| SpecialNotes<CR>\r\nmap \\nx :|FwkNoteStatic| <SomeName><CR>\r\n....\r\n\r\n\r\n\r\nTips: ~\r\nyou can always change\/comment maps. you can find them in fwk_notes.vim,\r\nfunction |FWK_Note_NotesMaps|.\r\n==============================================================================\r\nGLOBAL VARIABLES                                           *fwk_notes_variables*\r\n\r\n\r\nGlobal variables ~\r\n\r\n|g:fwk_notes_notes_directory|     Set path to notes directory. If not \r\n                                defined, will be used $VIM\/notes (win32) or \r\n                                $VIM\/notes (linux).\r\n\r\n|g:fwk_notes_disable|             1 if you want to disable plugin. By default\r\n                                plugin is on.\r\n\r\n|g:fwk_notes_open_node_mode|      Strategy to open notes. Possible values is\r\n                                0 to 3.\r\n        strategies: ~\r\n        0 - window mode (will be opened in same window only if only 1 window\r\n        in tab. Otherwise open happens in split mode). This is default mode.\r\n        1 - tab mode (will be opened in new tab).\r\n        2 - split mode, will be opened in same tab, but in new window.\r\n        3 - standard e:\r\n                                                     \r\n\r\n==============================================================================\r\nCHANGES                                                      *fwk_notes_changes*\r\n\r\n0.5    - added documentation\r\n       - fix bug with wrong indentation from words of form [a-z]\\+)\r\n       - add of templates\r\n\r\n\r\n\r\n\r\n==============================================================================\r\n vim:tw=78:ts=8:ft=help:norl:\r\n\r\n","4":"*fwk_notes.txt*   Manage your notes, track your tasks.\r\n                Copyright (c) 2010-2012 Sergey Vakulenko\r\n                License:      Vim License\r\n\r\n                                                                     *fwk_notes*\r\n\r\nINTRODUCTION                    |fwk_notes_introduction|\r\nINSTALLATION                    |fwk_notes_installation|\r\nUSAGE                           |fwk_notes_usage|\r\nHOTKEYS                         |fwk_notes_hotkeys|\r\nGLOBAL VARIABLES                |fwk_notes_variables|\r\nCHANGES                         |fwk_notes_changes|\r\n\r\n\r\n==============================================================================\r\nINTRODUCTION                                            *fwk_notes_introduction*\r\nThis plugin was created to manages your task\/notes by days\/weeks\/years.\r\nAlso, you can add your custom notes, of two types, static and dynamic.\r\n\r\n==============================================================================\r\nINSTALLATION                                            *fwk_notes_installation*\r\n\r\nJust drop files in zip archive to your vimfiles(win32) or .vim (linux\/ubuntu),\r\nor your custom path.\r\n\r\nPlugin files~\r\ndoc\\fwk_notes.txt\r\nplugin\\fwk_notes.vim\r\nplugin\\fwk_tab_aranger.vim\r\nplugin\\fwk_library_io_templates.vim\r\nsyntax\\notes.vim\r\ntemplates\\template_notes_common.notes\r\ntemplates\\template_notes_daily.notes\r\n\r\n\r\nAttention!~\r\nIts important that variable |g:fwk_templates_directory| contain the directory \r\nwith templates. By default, this path is $VIM\/vimfiles\/templates for win32,\r\nand $HOME\/.vim\/templates for linux. Anyway, you can change this variable to\r\nyour proper, if you want other placehold for templates.\r\n\r\n==============================================================================\r\nUSAGE                                                          *fwk_notes_usage*\r\n\r\nMain fonctionnality is to track your daily tasks and make the notes.\r\nBeside main fonctionnality (task tracking), you can create your custom notes.\r\nCustom notes can be of two types : static and dynamic.\r\nStatic notes will be created once, and then your map will only open this file.\r\nDynamic notes will be creates every new day. This is useful if you need to \r\nmake some notes each day. \r\n\r\nvideo tutorial\/demonstration\r\nhttp:\/\/www.youtube.com\/watch?v=sX93En-eQ6Y\r\n\r\n==============================================================================\r\nHOTKEYS                                                      *fwk_notes_hotkeys*\r\n\r\nMaps local to *.notes extention ~\r\n--------------------------------------------------------------------\r\nNavigation ~\r\n\\cd          open daily tasks\r\nctrl-Up      move to next day\r\nctrl-Down    move to previous day\r\n\r\nalt-Up       just to next notes section\r\nalt-Down     just to previous notes section\r\n             notes section can be:\r\n             To Do | Events | notes | Questions\r\n\r\nTasks management ~\r\nalt-d        create task ( 1), 2), 3), ... )\r\nalt-a        create subtask ( a), b), c), ...)\r\nalt-b        create sub_sub_task ( -), -), -), ...)\r\n\r\n\r\nStatus management ~\r\n\\cd          change status to |Done|. In this status, date and time will be added\r\n             automaticly.\r\n\\cp          change status to |Skip|.\r\n\\ci          change status to |Important|.\r\n\\c1          change status to |Group1|.\r\n\\c2          change status to |Group2|.\r\n\r\nYou can also apply all this commands in visual mode, by selecting the group of\r\ntasks.\r\n\r\nGlobal maps ~\r\n--------------------------------------------------------------------\r\nmap \\nd       open daily tasks. Its belong to dynamic notes.\r\n\r\n\r\nif you want to track some of your personal information \r\n(dictinnary per day, ...), you can create you proper maps:\r\n\r\n                                                                  *fwk_dynamic*\r\nDynamic notes, generate file each new day ~\r\nmap \\nv :|FwkNoteDynamic| Dictionnary<CR>\r\nmap \\nx :|FwkNoteDynamic| SpecialNotes<CR>\r\nmap \\nx :|FwkNoteDynamic| <SomeName><CR>\r\n....\r\n\r\n\r\n                                                                   *fwk_static*\r\nStatic notes, generate only one file and then reuse it: ~\r\nmap \\nv :|FwkNoteStatic| Dictionnary<CR>\r\nmap \\nx :|FwkNoteStatic| SpecialNotes<CR>\r\nmap \\nx :|FwkNoteStatic| <SomeName><CR>\r\n....\r\n\r\n\r\n\r\nTips: ~\r\nyou can always change\/comment maps. you can find them in fwk_notes.vim,\r\nfunction |FWK_Note_NotesMaps|.\r\n==============================================================================\r\nGLOBAL VARIABLES                                           *fwk_notes_variables*\r\n\r\n\r\nGlobal variables ~\r\n\r\n|g:fwk_notes_notes_directory|     Set path to notes directory. If not \r\n                                defined, will be used $VIM\/notes (win32) or \r\n                                $VIM\/notes (linux).\r\n\r\n|g:fwk_notes_disable|             1 if you want to disable plugin. By default\r\n                                plugin is on.\r\n\r\n|g:fwk_notes_open_node_mode|      Strategy to open notes. Possible values is\r\n                                0 to 3.\r\n        strategies: ~\r\n        0 - window mode (will be opened in same window only if only 1 window\r\n        in tab. Otherwise open happens in split mode). This is default mode.\r\n        1 - tab mode (will be opened in new tab).\r\n        2 - split mode, will be opened in same tab, but in new window.\r\n        3 - standard e:\r\n                                                     \r\n\r\n==============================================================================\r\nCHANGES                                                      *fwk_notes_changes*\r\n\r\n0.5    - added documentation\r\n       - fix bug with wrong indentation from words of form [a-z]\\+)\r\n       - add of templates\r\n\r\n\r\n\r\n\r\n==============================================================================\r\n vim:tw=78:ts=8:ft=help:norl:\r\n\r\n","install_details":"Just drop files in zip archive to your vimfiles(win32) or .vim (linux\/ubuntu),\r\nor your custom path.\r\n\r\nAttention!~\r\nIts important that variable |g:fwk_templates_directory| contain the directory \r\nwith templates. By default, this path is $VIM\/vimfiles\/templates for win32,\r\nand $HOME\/.vim\/templates for linux. Anyway, you can change this variable to\r\nyour proper, if you want other placehold for templates.","5":"Just drop files in zip archive to your vimfiles(win32) or .vim (linux\/ubuntu),\r\nor your custom path.\r\n\r\nAttention!~\r\nIts important that variable |g:fwk_templates_directory| contain the directory \r\nwith templates. By default, this path is $VIM\/vimfiles\/templates for win32,\r\nand $HOME\/.vim\/templates for linux. Anyway, you can change this variable to\r\nyour proper, if you want other placehold for templates.","first_name":"Sergey","6":"Sergey","last_name":"Vakulenko","7":"Vakulenko","releases":[{"0":"3956","vim_version":"7.0","1":"7.0","script_version":"0.81","2":"0.81","version_comment":"0.81 \r\n     change map alt-space to alt-b (bacause alt space is mapped in linux by OS)\r\n","3":"0.81 \r\n     change map alt-space to alt-b (bacause alt space is mapped in linux by OS)\r\n","package":"fwk_notes.zip","4":"fwk_notes.zip","src_id":"18061","5":"18061","creation_date":"1338320178","6":"1338320178"},{"0":"3956","vim_version":"7.0","1":"7.0","script_version":"0.6","2":"0.6","version_comment":"fix task numbs > 10","3":"fix task numbs > 10","package":"fwk_notes.zip","4":"fwk_notes.zip","src_id":"17656","5":"17656","creation_date":"1332627009","6":"1332627009"},{"0":"3956","vim_version":"7.0","1":"7.0","script_version":"0.5","2":"0.5","version_comment":"Initial upload","3":"Initial upload","package":"fwk_notes.zip","4":"fwk_notes.zip","src_id":"17549","5":"17549","creation_date":"1330603590","6":"1330603590"}]},"3955":{"script_id":"3955","0":"3955","script_name":"Add to Word Search","1":"Add to Word Search","script_type":"utility","2":"utility","summary":"Vim plugin to append more words to searches.","3":"Vim plugin to append more words to searches.","description":"When searching through code one often needs to add more related\r\nterms to the search. For example, if I found a call to a function inside\r\na different one, or when a type is typedef'ed to something else (in C).\r\nThis module aims to allow you to convenietly add search terms to the search\r\nso you can find all the occurences of all of them.\r\n","4":"When searching through code one often needs to add more related\r\nterms to the search. For example, if I found a call to a function inside\r\na different one, or when a type is typedef'ed to something else (in C).\r\nThis module aims to allow you to convenietly add search terms to the search\r\nso you can find all the occurences of all of them.\r\n","install_details":"To use: put this in ~\/.vim\/plugin\/ , which can be typed by installing the\r\nRuby rake package and typing rake install.\r\n","5":"To use: put this in ~\/.vim\/plugin\/ , which can be typed by installing the\r\nRuby rake package and typing rake install.\r\n","first_name":"Shlomi","6":"Shlomi","last_name":"Fish","7":"Fish","releases":[{"0":"3955","vim_version":"7.0","1":"7.0","script_version":"0.2.1","2":"0.2.1","version_comment":"Fixes an error when :set nowrapscan is set.","3":"Fixes an error when :set nowrapscan is set.","package":"add-to-word-search-0.2.1.zip","4":"add-to-word-search-0.2.1.zip","src_id":"17592","5":"17592","creation_date":"1331668558","6":"1331668558"},{"0":"3955","vim_version":"7.0","1":"7.0","script_version":"0.2.0","2":"0.2.0","version_comment":"Initial upload","3":"Initial upload","package":"add-to-word-search-0.2.0.zip","4":"add-to-word-search-0.2.0.zip","src_id":"17545","5":"17545","creation_date":"1330464494","6":"1330464494"}]},"3954":{"script_id":"3954","0":"3954","script_name":"tortex","1":"tortex","script_type":"color scheme","2":"color scheme","summary":"clear & soft","3":"clear & soft","description":"modified from Thorsten Maerz's torte. \r\nsupport GUI & Term\r\n","4":"modified from Thorsten Maerz's torte. \r\nsupport GUI & Term\r\n","install_details":"","5":"","first_name":"bo","6":"bo","last_name":"shi","7":"shi","releases":[{"0":"3954","vim_version":"7.0","1":"7.0","script_version":"1.2","2":"1.2","version_comment":"modified from Thorsten Maerz's torte.\r\nsupport GUI & Term ","3":"modified from Thorsten Maerz's torte.\r\nsupport GUI & Term ","package":"tortex.vim","4":"tortex.vim","src_id":"17541","5":"17541","creation_date":"1330416616","6":"1330416616"}]},"3952":{"script_id":"3952","0":"3952","script_name":"Improved paragraph motion","1":"Improved paragraph motion","script_type":"utility","2":"utility","summary":"Improve paragraph motion ","3":"Improve paragraph motion ","description":"A simple utility improve the \"{\" and \"}\" motion in normal \/ visual mode.\r\nIn vim, a blank line only containing white space is NOT a paragraph\r\nboundary, this utility remap the key \"{\" and \"}\" to handle that.\r\n\r\nIt supports in normal and visual mode, and able to handle with count. It\r\nalso support redefine the regexp for boundary, or local definition of\r\nboundary.\r\n\r\nThe utility uses a custom regexp to define paragraph boundaries, the\r\nmatched line will be treated as paragraph boundary.\r\nNote that the regexp will be enforced to match from the start of line, to\r\navoid strange behaviour when moving.\r\n\r\nConfiguration Variables:\r\ng:ip_skipfold     Set as 1 will make the \"{\" and \"}\" motion skip paragraph\r\n                  boundaries in closed fold.\r\n                  Default is 0.\r\n\r\ng:ip_boundary     The global definition of paragraph boundary.\r\n                  Default value is \"\\s*$\".\r\n                  It can be changed in .vimrc or anytime. Defining\r\n                  b:ip_boundary will override this setting.\r\n\r\n                  Example:\r\n                      :let g:ip_boundary = '\"\\?\\s*$'\r\n                  Setting that will make empty lines, and lines only\r\n                  contains '\"' as boundaries.\r\n\r\n                  Note that there is no need adding a \"^\" sign at the\r\n                  beginning. It is enforced by the script.\r\n\r\nb:ip_boundary     Local definition of paragraph boundary. It will override\r\n                  g:ip_boundary if set. Useful when customize boundary for\r\n                  local buffer or only apply to particular file type.\r\n                  Default is unset.","4":"A simple utility improve the \"{\" and \"}\" motion in normal \/ visual mode.\r\nIn vim, a blank line only containing white space is NOT a paragraph\r\nboundary, this utility remap the key \"{\" and \"}\" to handle that.\r\n\r\nIt supports in normal and visual mode, and able to handle with count. It\r\nalso support redefine the regexp for boundary, or local definition of\r\nboundary.\r\n\r\nThe utility uses a custom regexp to define paragraph boundaries, the\r\nmatched line will be treated as paragraph boundary.\r\nNote that the regexp will be enforced to match from the start of line, to\r\navoid strange behaviour when moving.\r\n\r\nConfiguration Variables:\r\ng:ip_skipfold     Set as 1 will make the \"{\" and \"}\" motion skip paragraph\r\n                  boundaries in closed fold.\r\n                  Default is 0.\r\n\r\ng:ip_boundary     The global definition of paragraph boundary.\r\n                  Default value is \"\\s*$\".\r\n                  It can be changed in .vimrc or anytime. Defining\r\n                  b:ip_boundary will override this setting.\r\n\r\n                  Example:\r\n                      :let g:ip_boundary = '\"\\?\\s*$'\r\n                  Setting that will make empty lines, and lines only\r\n                  contains '\"' as boundaries.\r\n\r\n                  Note that there is no need adding a \"^\" sign at the\r\n                  beginning. It is enforced by the script.\r\n\r\nb:ip_boundary     Local definition of paragraph boundary. It will override\r\n                  g:ip_boundary if set. Useful when customize boundary for\r\n                  local buffer or only apply to particular file type.\r\n                  Default is unset.","install_details":"Simply copy the file to plugin folder and restart vim.\r\n\r\nIf you do not know where to place it,\r\ncheck with \"USING A GLOBAL PLUGIN\" under :help standard-plugin\r\n\r\nWithout any setting, it will treat empty line (with or without space) as\r\nparagraph boundary.\r\n","5":"Simply copy the file to plugin folder and restart vim.\r\n\r\nIf you do not know where to place it,\r\ncheck with \"USING A GLOBAL PLUGIN\" under :help standard-plugin\r\n\r\nWithout any setting, it will treat empty line (with or without space) as\r\nparagraph boundary.\r\n","first_name":"Luke","6":"Luke","last_name":"Ng","7":"Ng","releases":[{"0":"3952","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"ipmotion.vim","4":"ipmotion.vim","src_id":"17531","5":"17531","creation_date":"1330339330","6":"1330339330"}]},"3951":{"script_id":"3951","0":"3951","script_name":"tmpclip.vim","1":"tmpclip.vim","script_type":"utility","2":"utility","summary":"Use a temp file as a clipboard","3":"Use a temp file as a clipboard","description":"This allows copy\/paste from one vim session to another outside of a window manager. In my case, I have muliple PuTTY windows, each running screen, where many screens have an instance of vim.\r\n\r\nProvides two convenience commands: `TmpClipWrite` and `TmpClipRead` which work with the default (\") register. Implementing functions are `tmpClipWrite` and `tmpClipRead` which accept the register as an argument.\r\n\r\nSample usage:\r\n\r\n  Vim instance #1 (source)\r\n    \r\n    yy                - Yank [copy] the current line\r\n    :TmpClipWrite     - Write it to ~\/.tmpclip\r\n\r\n  Vim instance #2 (destination)\r\n\r\n    :TmpClipRead      - Read ~\/.tmpclip\r\n    p                 - Put [paste] it\r\n","4":"This allows copy\/paste from one vim session to another outside of a window manager. In my case, I have muliple PuTTY windows, each running screen, where many screens have an instance of vim.\r\n\r\nProvides two convenience commands: `TmpClipWrite` and `TmpClipRead` which work with the default (\") register. Implementing functions are `tmpClipWrite` and `tmpClipRead` which accept the register as an argument.\r\n\r\nSample usage:\r\n\r\n  Vim instance #1 (source)\r\n    \r\n    yy                - Yank [copy] the current line\r\n    :TmpClipWrite     - Write it to ~\/.tmpclip\r\n\r\n  Vim instance #2 (destination)\r\n\r\n    :TmpClipRead      - Read ~\/.tmpclip\r\n    p                 - Put [paste] it\r\n","install_details":"~\/.vim\/plugin\/tmpclip.vim","5":"~\/.vim\/plugin\/tmpclip.vim","first_name":"Ryan","6":"Ryan","last_name":"Gies","7":"Gies","releases":[{"0":"3951","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"tmpclip.vim","4":"tmpclip.vim","src_id":"17524","5":"17524","creation_date":"1330081263","6":"1330081263"}]},"3950":{"script_id":"3950","0":"3950","script_name":"EasyColour","1":"EasyColour","script_type":"utility","2":"utility","summary":"Colour Schemes made Easy!","3":"Colour Schemes made Easy!","description":"This plugin makes it really easy to create your own colour scheme for Vim.  You don't need to understand Vim script and you can base your colour scheme on an existing one if you like.\r\n\r\nFor colour schemes written entirely with EasyColour, the plugin automatically handles details like:\r\n\r\n* Working with limited numbers of colours (the nearest available colour is automatically found for 8, 16 and 256 colour terminals);\r\n* Changing the background colour: define your colour scheme with (say) a dark background with light foreground colours, set the 'LightAuto' flag and EasyColour will automatically choose some dark foreground colours to work with a light background.\r\n\r\nWhy write a colour scheme like this:\r\n\r\n    let colors_name = \"mycolourscheme\"\r\n    hi Normal guibg=DarkBlue guifg=White ctermbg=4\r\n    hi Statement ctermfg=3 ctermbg=6 gui=undercurl guifg=Yellow guibg=#f6e8d0 guisp=Red\r\n    hi Keyword guifg=White guibg=DarkBlue ctermfg=0 ctermbg=4\r\n    hi Comment guifg=SeaGreen ctermfg=2 gui=Bold cterm=bold\r\n\r\nwhen you can write it like this:\r\n\r\n    Dark:\r\n        Normal:White,DarkBlue\r\n        Statement:Yellow,#F6E8D0,Red,Undercurl\r\n        Keyword:White\r\n        Comment:SeaGreen,Style=Bold\r\n\r\nwith all of the styles automatically highlighted (when you save) so you can see what the colours look like?\r\n\r\nI've ported my 'Bandit' colour scheme from the previous (already customised!) format into EasyColour now: it's included in the distribution as an example of a fairly advanced colour scheme.\r\n\r\nMore details on the website: http:\/\/www.cgtk.co.uk\/vim-scripts\/easycolour","4":"This plugin makes it really easy to create your own colour scheme for Vim.  You don't need to understand Vim script and you can base your colour scheme on an existing one if you like.\r\n\r\nFor colour schemes written entirely with EasyColour, the plugin automatically handles details like:\r\n\r\n* Working with limited numbers of colours (the nearest available colour is automatically found for 8, 16 and 256 colour terminals);\r\n* Changing the background colour: define your colour scheme with (say) a dark background with light foreground colours, set the 'LightAuto' flag and EasyColour will automatically choose some dark foreground colours to work with a light background.\r\n\r\nWhy write a colour scheme like this:\r\n\r\n    let colors_name = \"mycolourscheme\"\r\n    hi Normal guibg=DarkBlue guifg=White ctermbg=4\r\n    hi Statement ctermfg=3 ctermbg=6 gui=undercurl guifg=Yellow guibg=#f6e8d0 guisp=Red\r\n    hi Keyword guifg=White guibg=DarkBlue ctermfg=0 ctermbg=4\r\n    hi Comment guifg=SeaGreen ctermfg=2 gui=Bold cterm=bold\r\n\r\nwhen you can write it like this:\r\n\r\n    Dark:\r\n        Normal:White,DarkBlue\r\n        Statement:Yellow,#F6E8D0,Red,Undercurl\r\n        Keyword:White\r\n        Comment:SeaGreen,Style=Bold\r\n\r\nwith all of the styles automatically highlighted (when you save) so you can see what the colours look like?\r\n\r\nI've ported my 'Bandit' colour scheme from the previous (already customised!) format into EasyColour now: it's included in the distribution as an example of a fairly advanced colour scheme.\r\n\r\nMore details on the website: http:\/\/www.cgtk.co.uk\/vim-scripts\/easycolour","install_details":"Use pathogen!\r\n\r\nAlternatively, unzip into your vimfiles directory or read the instructions in the included doc\/EasyColour.txt.","5":"Use pathogen!\r\n\r\nAlternatively, unzip into your vimfiles directory or read the instructions in the included doc\/EasyColour.txt.","first_name":"Al","6":"Al","last_name":"Budden","7":"Budden","releases":[{"0":"3950","vim_version":"7.0","1":"7.0","script_version":"r1.1.1","2":"r1.1.1","version_comment":"Added copy of rgb.txt to the distribution.","3":"Added copy of rgb.txt to the distribution.","package":"easycolour_r1.1.1.zip","4":"easycolour_r1.1.1.zip","src_id":"17571","5":"17571","creation_date":"1331146225","6":"1331146225"},{"0":"3950","vim_version":"7.0","1":"7.0","script_version":"r1.1.0","2":"r1.1.0","version_comment":"Added support for custom colour definitions (the 'Colours' section).  Added support for linking highlight groups together (with the @ symbol). Now allow multiple highlight groups on the left of the ':'.","3":"Added support for custom colour definitions (the 'Colours' section).  Added support for linking highlight groups together (with the @ symbol). Now allow multiple highlight groups on the left of the ':'.","package":"easycolour_r1.1.0.zip","4":"easycolour_r1.1.0.zip","src_id":"17523","5":"17523","creation_date":"1330076964","6":"1330076964"},{"0":"3950","vim_version":"7.0","1":"7.0","script_version":"r1.0.0","2":"r1.0.0","version_comment":"Initial upload","3":"Initial upload","package":"easycolour_r1.0.0.zip","4":"easycolour_r1.0.0.zip","src_id":"17517","5":"17517","creation_date":"1330010810","6":"1330010810"}]},"3949":{"script_id":"3949","0":"3949","script_name":"pyunit.vim","1":"pyunit.vim","script_type":"ftplugin","2":"ftplugin","summary":"A simple compiler for using Python unittest with VIM","3":"A simple compiler for using Python unittest with VIM","description":"****************\r\n pyunit.vim\r\n****************\r\n:VERSION: 0.1.0\r\n\r\nA simple compiler for Python unittest on VIM. Useful to use with vim-makegreen_\r\nOriginal script is found on http:\/\/ftp.twaren.net\/vim\/runtime\/compiler\/pyunit.vim\r\n\r\nSee http:\/\/blog.staz.be\/?post\/2010\/09\/04\/Python-unit-test-and-vim for find how to use it with vim-makegreen_\r\n\r\n.. _vim-makegreen: https:\/\/github.com\/reinh\/vim-makegreen\r\n\r\nhow to install\r\n============================\r\nuse vundle_ or pathogen_ is recommended or simply extract to your vim directory\r\n\r\n.. _vundle: https:\/\/github.com\/gmarik\/vundle\r\n.. _pathogen: http:\/\/www.vim.org\/scripts\/script.php?script_id=2332","4":"****************\r\n pyunit.vim\r\n****************\r\n:VERSION: 0.1.0\r\n\r\nA simple compiler for Python unittest on VIM. Useful to use with vim-makegreen_\r\nOriginal script is found on http:\/\/ftp.twaren.net\/vim\/runtime\/compiler\/pyunit.vim\r\n\r\nSee http:\/\/blog.staz.be\/?post\/2010\/09\/04\/Python-unit-test-and-vim for find how to use it with vim-makegreen_\r\n\r\n.. _vim-makegreen: https:\/\/github.com\/reinh\/vim-makegreen\r\n\r\nhow to install\r\n============================\r\nuse vundle_ or pathogen_ is recommended or simply extract to your vim directory\r\n\r\n.. _vundle: https:\/\/github.com\/gmarik\/vundle\r\n.. _pathogen: http:\/\/www.vim.org\/scripts\/script.php?script_id=2332","install_details":"","5":"","first_name":"Alisue","6":"Alisue","last_name":"Lambda","7":"Lambda","releases":[{"0":"3949","vim_version":"7.0","1":"7.0","script_version":"0.1.0","2":"0.1.0","version_comment":"Initial upload","3":"Initial upload","package":"pyunit.vim.tar.gz","4":"pyunit.vim.tar.gz","src_id":"17513","5":"17513","creation_date":"1329842106","6":"1329842106"}]},"3948":{"script_id":"3948","0":"3948","script_name":"django.vim","1":"django.vim","script_type":"ftplugin","2":"ftplugin","summary":"A simple compiler for using Django unittest with VIM","3":"A simple compiler for using Django unittest with VIM","description":"****************\r\n django.vim\r\n****************\r\n:VERSION: 0.1.0\r\n\r\nA simple compiler for executing Django Unittest on VIM. Useful to use with vim-makegreen_\r\n\r\nSee http:\/\/blog.staz.be\/?post\/2010\/09\/04\/Python-unit-test-and-vim for find how to use it with vim-makegreen_\r\n\r\n.. _vim-makegreen: https:\/\/github.com\/reinh\/vim-makegreen\r\n\r\n","4":"****************\r\n django.vim\r\n****************\r\n:VERSION: 0.1.0\r\n\r\nA simple compiler for executing Django Unittest on VIM. Useful to use with vim-makegreen_\r\n\r\nSee http:\/\/blog.staz.be\/?post\/2010\/09\/04\/Python-unit-test-and-vim for find how to use it with vim-makegreen_\r\n\r\n.. _vim-makegreen: https:\/\/github.com\/reinh\/vim-makegreen\r\n\r\n","install_details":"how to install\r\n============================\r\nuse vundle_ or pathogen_ is recommended or simply extract to your vim directory\r\n\r\n.. _vundle: https:\/\/github.com\/gmarik\/vundle\r\n.. _pathogen: http:\/\/www.vim.org\/scripts\/script.php?script_id=2332\r\n\r\nIt is strongly recommended to use vim-localrc_ to configure. Create ``.local.vimrc`` in your\r\ntop level of django project directory as::\r\n\r\n    \" Use django unittest compiler\r\n    compiler django\r\n\r\n    \" Optional\r\n    \" Run unittest with the current editing app\r\n    nmap <Leader>t :call DjangoMakeGreen(\"%\")\r\n    \" Run unittest with whole project\r\n    nmap <Leader>T :call DjangoMakeGreen(\".\")\r\n\r\n.. _vim-localrc: https:\/\/github.com\/thinca\/vim-localrc\r\n\r\nhow to use with vim-makegreen\r\n==========================================================\r\nReplace your keymap with::\r\n\r\n    \" Run unittest with the current editing app\r\n    nmap <Leader>t :call DjangoMakeGreen(\"%\")\r\n    \" Run unittest with whole project\r\n    nmap <Leader>T :call DjangoMakeGreen(\".\")","5":"how to install\r\n============================\r\nuse vundle_ or pathogen_ is recommended or simply extract to your vim directory\r\n\r\n.. _vundle: https:\/\/github.com\/gmarik\/vundle\r\n.. _pathogen: http:\/\/www.vim.org\/scripts\/script.php?script_id=2332\r\n\r\nIt is strongly recommended to use vim-localrc_ to configure. Create ``.local.vimrc`` in your\r\ntop level of django project directory as::\r\n\r\n    \" Use django unittest compiler\r\n    compiler django\r\n\r\n    \" Optional\r\n    \" Run unittest with the current editing app\r\n    nmap <Leader>t :call DjangoMakeGreen(\"%\")\r\n    \" Run unittest with whole project\r\n    nmap <Leader>T :call DjangoMakeGreen(\".\")\r\n\r\n.. _vim-localrc: https:\/\/github.com\/thinca\/vim-localrc\r\n\r\nhow to use with vim-makegreen\r\n==========================================================\r\nReplace your keymap with::\r\n\r\n    \" Run unittest with the current editing app\r\n    nmap <Leader>t :call DjangoMakeGreen(\"%\")\r\n    \" Run unittest with whole project\r\n    nmap <Leader>T :call DjangoMakeGreen(\".\")","first_name":"Alisue","6":"Alisue","last_name":"Lambda","7":"Lambda","releases":[{"0":"3948","vim_version":"7.0","1":"7.0","script_version":"0.1.1","2":"0.1.1","version_comment":"Fix function issue","3":"Fix function issue","package":"django.vim.tar.gz","4":"django.vim.tar.gz","src_id":"17512","5":"17512","creation_date":"1329841841","6":"1329841841"},{"0":"3948","vim_version":"7.0","1":"7.0","script_version":"0.1.0","2":"0.1.0","version_comment":"Initial upload","3":"Initial upload","package":"django.vim.tar.gz","4":"django.vim.tar.gz","src_id":"17511","5":"17511","creation_date":"1329839266","6":"1329839266"}]},"3947":{"script_id":"3947","0":"3947","script_name":"Skittles Berry","1":"Skittles Berry","script_type":"color scheme","2":"color scheme","summary":"More colorful successor to Skittles Dark","3":"More colorful successor to Skittles Dark","description":"Slightly higher contrast, brighter, friendlier, spiritual successor to my Skittles Dark vim colorscheme.\r\n\r\nMore frequent updates, issues, comments, screenshots, etc. at https:\/\/github.com\/shawncplus\/skittles_berry","4":"Slightly higher contrast, brighter, friendlier, spiritual successor to my Skittles Dark vim colorscheme.\r\n\r\nMore frequent updates, issues, comments, screenshots, etc. at https:\/\/github.com\/shawncplus\/skittles_berry","install_details":"","5":"","first_name":"Shawn","6":"Shawn","last_name":"Biddle","7":"Biddle","releases":[{"0":"3947","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"skittles_berry.vim","4":"skittles_berry.vim","src_id":"17503","5":"17503","creation_date":"1329768792","6":"1329768792"}]},"3946":{"script_id":"3946","0":"3946","script_name":"hop language syntax highlight","1":"hop language syntax highlight","script_type":"syntax","2":"syntax","summary":"hop language (scheme web extention ) syntax highlight","3":"hop language (scheme web extention ) syntax highlight","description":"This is highlight for web multi-party language hop, extention of scheme bigloo package.\r\n\r\n\r\nhttp:\/\/hop.inria.fr\r\n\r\nhttp:\/\/www-sop.inria.fr\/indes\/fp\/Bigloo\r\n\r\n\r\n\r\nlatest version in git:\r\n\r\nhttps:\/\/github.com\/svakulenko\/gvim_extention\/blob\/master\/binaries\/hop.zip?raw=true\r\n","4":"This is highlight for web multi-party language hop, extention of scheme bigloo package.\r\n\r\n\r\nhttp:\/\/hop.inria.fr\r\n\r\nhttp:\/\/www-sop.inria.fr\/indes\/fp\/Bigloo\r\n\r\n\r\n\r\nlatest version in git:\r\n\r\nhttps:\/\/github.com\/svakulenko\/gvim_extention\/blob\/master\/binaries\/hop.zip?raw=true\r\n","install_details":"put it in your vimfiles (win32) or .vim (linux) directory.\r\n","5":"put it in your vimfiles (win32) or .vim (linux) directory.\r\n","first_name":"Sergey","6":"Sergey","last_name":"Vakulenko","7":"Vakulenko","releases":[{"0":"3946","vim_version":"7.0","1":"7.0","script_version":"0.6","2":"0.6","version_comment":"update syntax ","3":"update syntax ","package":"hop.zip","4":"hop.zip","src_id":"17593","5":"17593","creation_date":"1331757815","6":"1331757815"},{"0":"3946","vim_version":"7.0","1":"7.0","script_version":"0.5","2":"0.5","version_comment":"add syntax constructions for hop","3":"add syntax constructions for hop","package":"hop.zip","4":"hop.zip","src_id":"17502","5":"17502","creation_date":"1329766074","6":"1329766074"},{"0":"3946","vim_version":"7.0","1":"7.0","script_version":"0.4","2":"0.4","version_comment":"add linux compatability for this script (tested with ubuntu 11.04)","3":"add linux compatability for this script (tested with ubuntu 11.04)","package":"hop.zip","4":"hop.zip","src_id":"17499","5":"17499","creation_date":"1329730393","6":"1329730393"},{"0":"3946","vim_version":"7.0","1":"7.0","script_version":"0.3","2":"0.3","version_comment":"check existance of scheme plugin (inherite original scheme syntax)","3":"check existance of scheme plugin (inherite original scheme syntax)","package":"hop.zip","4":"hop.zip","src_id":"17496","5":"17496","creation_date":"1329693304","6":"1329693304"}]},"3945":{"script_id":"3945","0":"3945","script_name":"fountainwiki.vim","1":"fountainwiki.vim","script_type":"utility","2":"utility","summary":"Wiki and indentation for Fountain screenplay files","3":"Wiki and indentation for Fountain screenplay files","description":"Plugin offers light wikification of Fountain files, plus indentation.\r\n\r\nFountain syntax is the screenwriter's Markdown. Details: http:\/\/fountain.io\r\n\r\nCHARACTER NAMES, ## Section headers, and [[notes]] become automatic WikiWords, with no deviation from Fountain syntax whatsoever.  Simply press 'enter', and a new file opens for keeping notes.\r\n\r\nEmulates Vimwiki navigation and operation, and offers navigation and wikification of subordinate files of your choosing: plain text, markup syntax, etc. Or choose Vimwiki in order to use its search function and other features.\r\n\r\nOther helpful features for screenwriting: shift-enter for ALL CAPS carriage return, and Vimwiki-style header promotion\/demotion.\r\n\r\nFountain syntax file: (vimscript #3880)\r\n\r\nIn the works for the next version: more independent wiki-like features for non-wiki subordinate files (i.e., wikification of text files), and all filetypes highlighted and clickable (for linking various text, PDF, MS Word, image references, etc), which will make the system useful for overall project management. Will also include support for a deviation syntax for more compact scripts (plays, comic books) that use the character\/dialogue form, 'CHARACTER: Dialogue...', but otherwise emulates Fountain. Also, strengthening of pattern matches (I've already found some weaknesses) and, of course, some bug fixes.","4":"Plugin offers light wikification of Fountain files, plus indentation.\r\n\r\nFountain syntax is the screenwriter's Markdown. Details: http:\/\/fountain.io\r\n\r\nCHARACTER NAMES, ## Section headers, and [[notes]] become automatic WikiWords, with no deviation from Fountain syntax whatsoever.  Simply press 'enter', and a new file opens for keeping notes.\r\n\r\nEmulates Vimwiki navigation and operation, and offers navigation and wikification of subordinate files of your choosing: plain text, markup syntax, etc. Or choose Vimwiki in order to use its search function and other features.\r\n\r\nOther helpful features for screenwriting: shift-enter for ALL CAPS carriage return, and Vimwiki-style header promotion\/demotion.\r\n\r\nFountain syntax file: (vimscript #3880)\r\n\r\nIn the works for the next version: more independent wiki-like features for non-wiki subordinate files (i.e., wikification of text files), and all filetypes highlighted and clickable (for linking various text, PDF, MS Word, image references, etc), which will make the system useful for overall project management. Will also include support for a deviation syntax for more compact scripts (plays, comic books) that use the character\/dialogue form, 'CHARACTER: Dialogue...', but otherwise emulates Fountain. Also, strengthening of pattern matches (I've already found some weaknesses) and, of course, some bug fixes.","install_details":"Open the vba file and type:\r\n\r\n    :so %\r\n\r\nSee :help vimball for details.","5":"Open the vba file and type:\r\n\r\n    :so %\r\n\r\nSee :help vimball for details.","first_name":"carson","6":"carson","last_name":"fire","7":"fire","releases":[{"0":"3945","vim_version":"7.3","1":"7.3","script_version":"1.3","2":"1.3","version_comment":"* Cleaner innards, better internal notes.\r\n* More concise help file.\r\n* Commands shortened; all begin with 'Fn' for quick access.\r\n* Coordinated with Vimwiki navigation and functions.\r\n* Complimentary navigation scheme for other subordinate files.\r\n* Subordinate files wikified.\r\n* Vimwiki-like header adjustment.\r\n* Intuitive shortcut for ALLCAP LINES carriage return.\r\n* Better title page text block protection (indentation).","3":"* Cleaner innards, better internal notes.\r\n* More concise help file.\r\n* Commands shortened; all begin with 'Fn' for quick access.\r\n* Coordinated with Vimwiki navigation and functions.\r\n* Complimentary navigation scheme for other subordinate files.\r\n* Subordinate files wikified.\r\n* Vimwiki-like header adjustment.\r\n* Intuitive shortcut for ALLCAP LINES carriage return.\r\n* Better title page text block protection (indentation).","package":"fountainwiki-1-3.vba","4":"fountainwiki-1-3.vba","src_id":"17525","5":"17525","creation_date":"1330083021","6":"1330083021"},{"0":"3945","vim_version":"7.3","1":"7.3","script_version":"1.2","2":"1.2","version_comment":"Vimballed, now with proper help file. Wiki file now opens full window (more common behavior), but with the sidebar still available as an option. New command brings you back to your screenplay. Hack added for properly exploiting Vimwiki search (if using Vimwiki in conjunction). More options for customizing indentation. Filename token deprecated, now optional.","3":"Vimballed, now with proper help file. Wiki file now opens full window (more common behavior), but with the sidebar still available as an option. New command brings you back to your screenplay. Hack added for properly exploiting Vimwiki search (if using Vimwiki in conjunction). More options for customizing indentation. Filename token deprecated, now optional.","package":"fountainwiki-1-2.vba","4":"fountainwiki-1-2.vba","src_id":"17510","5":"17510","creation_date":"1329823745","6":"1329823745"},{"0":"3945","vim_version":"7.3","1":"7.3","script_version":"1.1","2":"1.1","version_comment":"[[Notes]] are now FountainWikiWords, along with CHARACTER NAMES and ## Section headers.  Filename token made optional. ","3":"[[Notes]] are now FountainWikiWords, along with CHARACTER NAMES and ## Section headers.  Filename token made optional. ","package":"fountainwiki.vim","4":"fountainwiki.vim","src_id":"17498","5":"17498","creation_date":"1329723997","6":"1329723997"},{"0":"3945","vim_version":"7.3","1":"7.3","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"fountainwiki.vim","4":"fountainwiki.vim","src_id":"17492","5":"17492","creation_date":"1329647778","6":"1329647778"}]},"3944":{"script_id":"3944","0":"3944","script_name":"Yii API manual for Vim","1":"Yii API manual for Vim","script_type":"utility","2":"utility","summary":"API manual for Yii PHP framework","3":"API manual for Yii PHP framework","description":"This is the API manual for Yii as Vim plugin. For details and latest versions also check the development site:\r\n\r\n  https:\/\/github.com\/mikehaertl\/yii-api-vim","4":"This is the API manual for Yii as Vim plugin. For details and latest versions also check the development site:\r\n\r\n  https:\/\/github.com\/mikehaertl\/yii-api-vim","install_details":"Download the files from here, extract the package and move the docs\/ directory to your ~\/.vim directory.\r\n\r\nAlternatively you can use a plugin manager like Vundle (recommended).\r\n\r\nIf the help is not available after installation, you can try to issue this command in VIM:\r\n\r\n:helptags ~\/.vimrc\/doc","5":"Download the files from here, extract the package and move the docs\/ directory to your ~\/.vim directory.\r\n\r\nAlternatively you can use a plugin manager like Vundle (recommended).\r\n\r\nIf the help is not available after installation, you can try to issue this command in VIM:\r\n\r\n:helptags ~\/.vimrc\/doc","first_name":"Michael","6":"Michael","last_name":"H\u00c3\u00a4rtl","7":"H\u00c3\u00a4rtl","releases":[{"0":"3944","vim_version":"7.0","1":"7.0","script_version":"1.1.9","2":"1.1.9","version_comment":"Initial upload","3":"Initial upload","package":"yii-api-vim-v1.1.9.tar.gz","4":"yii-api-vim-v1.1.9.tar.gz","src_id":"17489","5":"17489","creation_date":"1329554351","6":"1329554351"}]},"3943":{"script_id":"3943","0":"3943","script_name":"pdv-standalone","1":"pdv-standalone","script_type":"utility","2":"utility","summary":"PHP Documentor for vim as standalone plugin","3":"PHP Documentor for vim as standalone plugin","description":"This is a standalone version of Tobias Schlitt's famous phpDocumentor for Vim plugin.\r\n\r\nI was pretty happy with Tobias' original plugin (thanks Tobias!) but i had two issues with it:\r\n\r\n * You had to alter the code to configure the plugin\r\n* Tobias integrated the latest version into his new VIP (VIM integration for PHP) repository but i didn't need\/want the rest in there\r\n\r\n(If you prefer Tobias' original repo, you find it at https:\/\/github.com\/tobyS\/vip.)\r\n\r\nFind full installation instructions and configuration options on the development site at github:\r\n\r\n  https:\/\/github.com\/mikehaertl\/pdv-standalone","4":"This is a standalone version of Tobias Schlitt's famous phpDocumentor for Vim plugin.\r\n\r\nI was pretty happy with Tobias' original plugin (thanks Tobias!) but i had two issues with it:\r\n\r\n * You had to alter the code to configure the plugin\r\n* Tobias integrated the latest version into his new VIP (VIM integration for PHP) repository but i didn't need\/want the rest in there\r\n\r\n(If you prefer Tobias' original repo, you find it at https:\/\/github.com\/tobyS\/vip.)\r\n\r\nFind full installation instructions and configuration options on the development site at github:\r\n\r\n  https:\/\/github.com\/mikehaertl\/pdv-standalone","install_details":"","5":"","first_name":"Michael","6":"Michael","last_name":"H\u00c3\u00a4rtl","7":"H\u00c3\u00a4rtl","releases":[{"0":"3943","vim_version":"7.0","1":"7.0","script_version":"1.0.1","2":"1.0.1","version_comment":"Initial upload","3":"Initial upload","package":"pdv-standalone.vim","4":"pdv-standalone.vim","src_id":"17488","5":"17488","creation_date":"1329554029","6":"1329554029"}]},"3942":{"script_id":"3942","0":"3942","script_name":"sandbox_hg","1":"sandbox_hg","script_type":"utility","2":"utility","summary":"Same as sandbox.vim but for hg(mercurial).","3":"Same as sandbox.vim but for hg(mercurial).","description":"After installing this plugin, ':Sandhg <hg working copy>' on the command line will create a new buffer \r\nwhich list the currnet status of the sandbox. In the buffer, a few handy mapping are available like diffing, commit, revert, etc. See the help at  the bottom of the buffer. \r\n\r\nScreenshot: \r\nhttp:\/\/files.myopera.com\/wzhliang\/albums\/649613\/sandbox.png \r\n\r\nLinux only! \r\n\r\nDepends on: hg, diffuse, or meld for GUI diffing. tortoisehg for other GUI stuff\r\n \r\n---------- H E L P ----------- \r\nc         Commit a single file or selected files. \r\nd         Diff the file specified in the current line. \r\ne         Open the file in question in a new tab. \r\nr         Revert a single file or selected files. \r\nt         Select\/Unselect a single file. \r\nC-D     Reset selection. \r\n<F5>    Refresh the buffer. \r\nq       Quit ","4":"After installing this plugin, ':Sandhg <hg working copy>' on the command line will create a new buffer \r\nwhich list the currnet status of the sandbox. In the buffer, a few handy mapping are available like diffing, commit, revert, etc. See the help at  the bottom of the buffer. \r\n\r\nScreenshot: \r\nhttp:\/\/files.myopera.com\/wzhliang\/albums\/649613\/sandbox.png \r\n\r\nLinux only! \r\n\r\nDepends on: hg, diffuse, or meld for GUI diffing. tortoisehg for other GUI stuff\r\n \r\n---------- H E L P ----------- \r\nc         Commit a single file or selected files. \r\nd         Diff the file specified in the current line. \r\ne         Open the file in question in a new tab. \r\nr         Revert a single file or selected files. \r\nt         Select\/Unselect a single file. \r\nC-D     Reset selection. \r\n<F5>    Refresh the buffer. \r\nq       Quit ","install_details":"This plugin is distributed as a vimball. So simply edit the vimbal and :so it.","5":"This plugin is distributed as a vimball. So simply edit the vimbal and :so it.","first_name":"Wenzhi","6":"Wenzhi","last_name":"Liang","7":"Liang","releases":[{"0":"3942","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"sandbox_hg-0.1.vba","4":"sandbox_hg-0.1.vba","src_id":"17486","5":"17486","creation_date":"1329492240","6":"1329492240"}]},"3941":{"script_id":"3941","0":"3941","script_name":"CodeCommenter","1":"CodeCommenter","script_type":"utility","2":"utility","summary":"Code Comment Assistant","3":"Code Comment Assistant","description":"codecommenter - Code Comment Assistant \r\n\r\nLanguage:    Php, Python, Js, Java, C, C#, C++\r\nMaintainer:   九九 <xjiujiu@foxmail.com>\r\nLicense:      BSD New \r\nRequires:     Vim >= 7.2\r\nLast Change:  2012-02-17 \r\nVersion:      1.0.0\r\n\r\nInstallation \r\n------------ \r\n\r\n1. Place this file and ipyqtmacvim.scpt in ~\/.vim\/plugins\/\r\n\r\n2. Place the following line in your .vimrc (requires Vim >= 7.2) \r\n\"\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\r\n\"Config your commenter items\r\nlet g:myCodeCommenterConfigItems  = {\r\n            \\ 'author': 'xjiujiu',                                 ==> To config the author of these code \r\n            \\ 'siteUrl': 'http:\/\/www.xjiujiu.com',         ==> To config the site of the author \r\n            \\ 'email': 'xjiujiu@foxmail.com',             ==> To config the email of the author \r\n            \\ 'linsence': 'BSD NEW',                       ==> To config the code linsence \r\n            \\ 'copyRight': 'Copyright (c) 2011-2012 http:\/\/www.xjiujiu.com.All right reserved',    ==> To config the copyright information \r\n            \\ 'companyName': 'HongJuZi',                ==> Your company name \r\n            \\ 'projectDecription': 'HongJuZi Framework',   ==> To config the decsription of the project \r\n            \\ 'versionBySvn': 1                                ==> To config the version of the file is gen by subversion or by the script function\r\n\"            \\ }\r\n   This enables Vim to use your system clipboard. \r\n   \r\n3. If desired, configure the hotkeys to run codeCommenter.The default hotkey is <Ctrl-M>\r\n\r\nExamples\r\n--------------\r\n\" Version: $Id: test-codecommenter.vim 74 2012-02-17 01:45:19Z xjiujiu@gmail.com $\r\n\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\r\n\/\/f - <Ctrl-M>\r\n\"\"\"\r\n \" @Version\t\t\t$Id: test-codecommenter.vim 74 2012-02-17 01:45:19Z xjiujiu@gmail.com $\r\n \" @Package \t\tNone\r\n \" @Subpackage \t\tNone\r\n \" @CopyRight \t\tCopyright (c) 2011-2012 http:\/\/www.xjiujiu.com.All right reserved\r\n \" \r\n\"\"\"\r\n\/**\r\n * @Version\t\t\t\t$Id: test-codecommenter.vim 74 2012-02-17 01:45:19Z xjiujiu@gmail.com $\r\n * @Package: \t\t\tNone\r\n * @Subpackage: \t\tNone\r\n * @CopyRight: \t\t\tCopyright (c) 2011-2012 http:\/\/www.xjiujiu.com.All right reserved\r\n * @License: \t\t\tApache GNU\r\n * \r\n *\/\r\n\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\r\n\/\/c - <Ctrl-M>\r\n\"\"\"\r\n \" @point\r\n \" \r\n \" @desc\r\n \" \r\n \" @Author \t\t\t九九 <xjiujiu@foxmail.com>\r\n \" @Package \t\tNone\r\n \" @Version\t\t\t$Id: test-codecommenter.vim 74 2012-02-17 01:45:19Z xjiujiu@gmail.com $\r\n\"\"\"\r\n\r\n\/**\r\n * @point\r\n * \r\n * @desc\r\n * \r\n * @Author \t\t\t\t九九 <xjiujiu@foxmail.com>\r\n * @Package \t\t\tNone\r\n * @Version\t\t\t\t$Id: test-codecommenter.vim 74 2012-02-17 01:45:19Z xjiujiu@gmail.com $\r\n *\/\r\n\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\r\n\/\/m - <Ctrl-M>\r\n\/**\r\n * @point\r\n * \r\n * @desc\r\n * \r\n * @Access public\r\n * @Param string test\r\n * @Param  int yes\r\n * @Return void\r\n * @Exception none\r\n *\/\r\n\r\n\"\"\"\r\n \" @point\r\n \" \r\n \" @desc\r\n \" \r\n \" @Access public\r\n \" @Param string test\r\n \" @Param  int yes\r\n \" @Return void\r\n \" @Exception none\r\n\"\"\"\r\nfunction GetName(string test, int yes)\r\nendfunction\r\n\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\r\n\/\/v - <Ctrl-M>\r\n\/**\r\n * var $string     \r\n *\/\r\n\r\n\"\"\"\r\n \" var \r\n\"\"\"\r\nlet var = 1\r\n$string     = \"test\"\r\n\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\r\n\r\n\r\nTroubleshooting \r\n--------------- \r\n\/**\r\n * The file type can't be supported!\r\n *\/\r\nThis means you file type can't be supported now!\r\n:(\r\n\r\nContact \r\n------- \r\n\r\nxjiujiu at xjiujiu@foxmail.com\r\n\r\nLinux OS Notice\r\n-------\r\n You need to change the enter mode.Please use dos2unix tool to do this.Example:\r\ndos2unix YourPath\/codecommenter.vim","4":"codecommenter - Code Comment Assistant \r\n\r\nLanguage:    Php, Python, Js, Java, C, C#, C++\r\nMaintainer:   九九 <xjiujiu@foxmail.com>\r\nLicense:      BSD New \r\nRequires:     Vim >= 7.2\r\nLast Change:  2012-02-17 \r\nVersion:      1.0.0\r\n\r\nInstallation \r\n------------ \r\n\r\n1. Place this file and ipyqtmacvim.scpt in ~\/.vim\/plugins\/\r\n\r\n2. Place the following line in your .vimrc (requires Vim >= 7.2) \r\n\"\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\r\n\"Config your commenter items\r\nlet g:myCodeCommenterConfigItems  = {\r\n            \\ 'author': 'xjiujiu',                                 ==> To config the author of these code \r\n            \\ 'siteUrl': 'http:\/\/www.xjiujiu.com',         ==> To config the site of the author \r\n            \\ 'email': 'xjiujiu@foxmail.com',             ==> To config the email of the author \r\n            \\ 'linsence': 'BSD NEW',                       ==> To config the code linsence \r\n            \\ 'copyRight': 'Copyright (c) 2011-2012 http:\/\/www.xjiujiu.com.All right reserved',    ==> To config the copyright information \r\n            \\ 'companyName': 'HongJuZi',                ==> Your company name \r\n            \\ 'projectDecription': 'HongJuZi Framework',   ==> To config the decsription of the project \r\n            \\ 'versionBySvn': 1                                ==> To config the version of the file is gen by subversion or by the script function\r\n\"            \\ }\r\n   This enables Vim to use your system clipboard. \r\n   \r\n3. If desired, configure the hotkeys to run codeCommenter.The default hotkey is <Ctrl-M>\r\n\r\nExamples\r\n--------------\r\n\" Version: $Id: test-codecommenter.vim 74 2012-02-17 01:45:19Z xjiujiu@gmail.com $\r\n\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\r\n\/\/f - <Ctrl-M>\r\n\"\"\"\r\n \" @Version\t\t\t$Id: test-codecommenter.vim 74 2012-02-17 01:45:19Z xjiujiu@gmail.com $\r\n \" @Package \t\tNone\r\n \" @Subpackage \t\tNone\r\n \" @CopyRight \t\tCopyright (c) 2011-2012 http:\/\/www.xjiujiu.com.All right reserved\r\n \" \r\n\"\"\"\r\n\/**\r\n * @Version\t\t\t\t$Id: test-codecommenter.vim 74 2012-02-17 01:45:19Z xjiujiu@gmail.com $\r\n * @Package: \t\t\tNone\r\n * @Subpackage: \t\tNone\r\n * @CopyRight: \t\t\tCopyright (c) 2011-2012 http:\/\/www.xjiujiu.com.All right reserved\r\n * @License: \t\t\tApache GNU\r\n * \r\n *\/\r\n\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\r\n\/\/c - <Ctrl-M>\r\n\"\"\"\r\n \" @point\r\n \" \r\n \" @desc\r\n \" \r\n \" @Author \t\t\t九九 <xjiujiu@foxmail.com>\r\n \" @Package \t\tNone\r\n \" @Version\t\t\t$Id: test-codecommenter.vim 74 2012-02-17 01:45:19Z xjiujiu@gmail.com $\r\n\"\"\"\r\n\r\n\/**\r\n * @point\r\n * \r\n * @desc\r\n * \r\n * @Author \t\t\t\t九九 <xjiujiu@foxmail.com>\r\n * @Package \t\t\tNone\r\n * @Version\t\t\t\t$Id: test-codecommenter.vim 74 2012-02-17 01:45:19Z xjiujiu@gmail.com $\r\n *\/\r\n\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\r\n\/\/m - <Ctrl-M>\r\n\/**\r\n * @point\r\n * \r\n * @desc\r\n * \r\n * @Access public\r\n * @Param string test\r\n * @Param  int yes\r\n * @Return void\r\n * @Exception none\r\n *\/\r\n\r\n\"\"\"\r\n \" @point\r\n \" \r\n \" @desc\r\n \" \r\n \" @Access public\r\n \" @Param string test\r\n \" @Param  int yes\r\n \" @Return void\r\n \" @Exception none\r\n\"\"\"\r\nfunction GetName(string test, int yes)\r\nendfunction\r\n\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\r\n\/\/v - <Ctrl-M>\r\n\/**\r\n * var $string     \r\n *\/\r\n\r\n\"\"\"\r\n \" var \r\n\"\"\"\r\nlet var = 1\r\n$string     = \"test\"\r\n\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\r\n\r\n\r\nTroubleshooting \r\n--------------- \r\n\/**\r\n * The file type can't be supported!\r\n *\/\r\nThis means you file type can't be supported now!\r\n:(\r\n\r\nContact \r\n------- \r\n\r\nxjiujiu at xjiujiu@foxmail.com\r\n\r\nLinux OS Notice\r\n-------\r\n You need to change the enter mode.Please use dos2unix tool to do this.Example:\r\ndos2unix YourPath\/codecommenter.vim","install_details":"Copy the codecommenter.vim to {your_vim_path}\/plugins\/codecommenter.vim\r\nDone.","5":"Copy the codecommenter.vim to {your_vim_path}\/plugins\/codecommenter.vim\r\nDone.","first_name":"xiang","6":"xiang","last_name":"jiujiu","7":"jiujiu","releases":[{"0":"3941","vim_version":"7.0","1":"7.0","script_version":"2.0","2":"2.0","version_comment":"1. Add InhertDoc comment\r\n>>Example:\r\n    \/\/i -> C-M    (CTRL + M)\r\n    \/**\r\n     * @point\r\n     * \r\n     * @desc\r\n     * \r\n     * {@inheritdoc}\r\n     * \r\n     * @author xjiujiu <xjiujiu@foxmail.com>\r\n     *\/\r\n\r\n2. Fixed PHP Doc Tags\r\n3. Fixed Some Bugs.","3":"1. Add InhertDoc comment\r\n>>Example:\r\n    \/\/i -> C-M    (CTRL + M)\r\n    \/**\r\n     * @point\r\n     * \r\n     * @desc\r\n     * \r\n     * {@inheritdoc}\r\n     * \r\n     * @author xjiujiu <xjiujiu@foxmail.com>\r\n     *\/\r\n\r\n2. Fixed PHP Doc Tags\r\n3. Fixed Some Bugs.","package":"codecommenter.vim","4":"codecommenter.vim","src_id":"21074","5":"21074","creation_date":"1384949042","6":"1384949042"},{"0":"3941","vim_version":"7.0","1":"7.0","script_version":"2.0","2":"2.0","version_comment":"1. Add InhertDoc comment\r\n>>Example:\r\n    \/\/i -> C-M    (CTRL + M)\r\n    \/**\r\n     * @point\r\n     * \r\n     * @desc\r\n     * \r\n     * {@inheritdoc}\r\n     * \r\n     * @author xjiujiu <xjiujiu@foxmail.com>\r\n     *\/\r\n\r\n2. Fixed PHP Doc Tags\r\n3. Fixed Some Bugs.","3":"1. Add InhertDoc comment\r\n>>Example:\r\n    \/\/i -> C-M    (CTRL + M)\r\n    \/**\r\n     * @point\r\n     * \r\n     * @desc\r\n     * \r\n     * {@inheritdoc}\r\n     * \r\n     * @author xjiujiu <xjiujiu@foxmail.com>\r\n     *\/\r\n\r\n2. Fixed PHP Doc Tags\r\n3. Fixed Some Bugs.","package":"codecommenter.vim","4":"codecommenter.vim","src_id":"21073","5":"21073","creation_date":"1384948854","6":"1384948854"},{"0":"3941","vim_version":"7.2","1":"7.2","script_version":"2.0","2":"2.0","version_comment":"1. Add InhertDoc comment\r\n>>Example:\r\n    \/\/i -> C-M    (CTRL + M)\r\n    \/**\r\n     * @point\r\n     * \r\n     * @desc\r\n     * \r\n     * {@inheritdoc}\r\n     * \r\n     * @author xjiujiu <xjiujiu@foxmail.com>\r\n     *\/\r\n\r\n2. Fixed PHP Doc Tags\r\n3. Fixed Some Bugs.","3":"1. Add InhertDoc comment\r\n>>Example:\r\n    \/\/i -> C-M    (CTRL + M)\r\n    \/**\r\n     * @point\r\n     * \r\n     * @desc\r\n     * \r\n     * {@inheritdoc}\r\n     * \r\n     * @author xjiujiu <xjiujiu@foxmail.com>\r\n     *\/\r\n\r\n2. Fixed PHP Doc Tags\r\n3. Fixed Some Bugs.","package":"codecommenter.vim","4":"codecommenter.vim","src_id":"21072","5":"21072","creation_date":"1384948836","6":"1384948836"},{"0":"3941","vim_version":"7.2","1":"7.2","script_version":"2.0","2":"2.0","version_comment":"1. Add InhertDoc comment\r\n>>Example:\r\n    \/\/i -> C-M    (CTRL + M)\r\n    \/**\r\n     * @point\r\n     * \r\n     * @desc\r\n     * \r\n     * {@inheritdoc}\r\n     * \r\n     * @author xjiujiu <xjiujiu@foxmail.com>\r\n     *\/\r\n\r\n2. Fixed PHP Doc Tags\r\n3. Fixed Some Bugs.","3":"1. Add InhertDoc comment\r\n>>Example:\r\n    \/\/i -> C-M    (CTRL + M)\r\n    \/**\r\n     * @point\r\n     * \r\n     * @desc\r\n     * \r\n     * {@inheritdoc}\r\n     * \r\n     * @author xjiujiu <xjiujiu@foxmail.com>\r\n     *\/\r\n\r\n2. Fixed PHP Doc Tags\r\n3. Fixed Some Bugs.","package":"codecommenter.vim","4":"codecommenter.vim","src_id":"21071","5":"21071","creation_date":"1384948801","6":"1384948801"},{"0":"3941","vim_version":"7.2","1":"7.2","script_version":"2.0","2":"2.0","version_comment":"1. Add InhertDoc comment\r\n>>Example:\r\n    \/\/i -> C-M    (CTRL + M)\r\n    \/**\r\n     * @point\r\n     * \r\n     * @desc\r\n     * \r\n     * {@inheritdoc}\r\n     * \r\n     * @author xjiujiu <xjiujiu@foxmail.com>\r\n     *\/\r\n\r\n2. Fixed PHP Doc Tags\r\n3. Fixed Some Bugs.","3":"1. Add InhertDoc comment\r\n>>Example:\r\n    \/\/i -> C-M    (CTRL + M)\r\n    \/**\r\n     * @point\r\n     * \r\n     * @desc\r\n     * \r\n     * {@inheritdoc}\r\n     * \r\n     * @author xjiujiu <xjiujiu@foxmail.com>\r\n     *\/\r\n\r\n2. Fixed PHP Doc Tags\r\n3. Fixed Some Bugs.","package":"codecommenter.vim","4":"codecommenter.vim","src_id":"21070","5":"21070","creation_date":"1384942756","6":"1384942756"},{"0":"3941","vim_version":"7.3","1":"7.3","script_version":"1.2.0","2":"1.2.0","version_comment":"1. Fix some Bugs;\r\n2. Clear some comment items.","3":"1. Fix some Bugs;\r\n2. Clear some comment items.","package":"codecommenter.vim","4":"codecommenter.vim","src_id":"18890","5":"18890","creation_date":"1351128823","6":"1351128823"},{"0":"3941","vim_version":"7.2","1":"7.2","script_version":"1.0.1","2":"1.0.1","version_comment":"1. Add a new feature\u00e2\u0080\u0094\u00e2\u0080\u0094autoindent the comment line,such as： \r\n    \/\/f  -> <Ctrl + M> \r\n    \"\"\" \r\n     \" @Version\t $Id$ \r\n     \" @Package None \r\n     \" @Subpackage None \r\n     \" @CopyRight Copyright (c) 2011-2012 http:\/\/www.xjiujiu.com.All right reserved \r\n     \" \r\n    \"\"\"\r\n2. Fix some bugs.","3":"1. Add a new feature\u00e2\u0080\u0094\u00e2\u0080\u0094autoindent the comment line,such as： \r\n    \/\/f  -> <Ctrl + M> \r\n    \"\"\" \r\n     \" @Version\t $Id$ \r\n     \" @Package None \r\n     \" @Subpackage None \r\n     \" @CopyRight Copyright (c) 2011-2012 http:\/\/www.xjiujiu.com.All right reserved \r\n     \" \r\n    \"\"\"\r\n2. Fix some bugs.","package":"codecommenter.vim","4":"codecommenter.vim","src_id":"17522","5":"17522","creation_date":"1330068489","6":"1330068489"},{"0":"3941","vim_version":"7.2","1":"7.2","script_version":"1.0.0","2":"1.0.0","version_comment":"The First Version.Welcome to commit the bugs :)  <xjiujiu@foxmail.com>","3":"The First Version.Welcome to commit the bugs :)  <xjiujiu@foxmail.com>","package":"codecommenter.vim","4":"codecommenter.vim","src_id":"17484","5":"17484","creation_date":"1329449675","6":"1329449675"}]},"3940":{"script_id":"3940","0":"3940","script_name":"writebackupAutomator","1":"writebackupAutomator","script_type":"utility","2":"utility","summary":"Automatically write a backup on the first write. ","3":"Automatically write a backup on the first write. ","description":"DESCRIPTION\r\nUnless you use a revision control system, you have to write backups yourself.\r\nThe writebackup.vim plugin makes that a simple :WriteBackup command from\r\nwithin Vim, but you still have to remember to trigger the backup. The\r\nwritebackupVersionControl.vim extension can make up for a missed backup when\r\nyou have already made changes to the buffer, but have not persisted them yet,\r\nvia :WriteBackupOfSavedOriginal. Still, wouldn't it be nice if Vim detected\r\nthat you have made backups of a file in the past, and automatically creates a\r\nnew backup - without any action on your side?\r\n\r\nThis plugin builds on the writebackup.vim and\r\nwritebackupVersionControl.vim plugins, and automatically writes a backup on\r\na day's first write of a file that was backed up in the past, but not yet\r\ntoday.\r\nThis gives you one no-hassle, worry-free backup every day. For many\r\nwritebackup.vim use cases (like editing config files distributed all over\r\n\/etc\/), this initial \"good state from the past\" backup is the most important\r\none. (And of course you can still manually trigger additional checkpoint\r\nbackups via :WriteBackup as in the past.)\r\n\r\nUSAGE\r\nOnce any backup exists (you can check via :WriteBackupListVersions), a new\r\nbackup will be written on each day when you first persist the buffer via\r\n:write, provided that the file has not been modified yet today. (Otherwise,\r\nyou would not be able to undo the automatic backup via\r\n:WriteBackupDeleteLastBackup; the automatic backup would keep reappearing\r\nafter each :write.) Watch out for file synchronization tools and version\r\ncontrol systems that may silently update the file modification date to today\r\nand therefore prevent automatic backups!\r\nFor this and other reasons, it is still a good practice to trigger backups via\r\n:WriteBackup yourself, and just use the writebackupAutomator plugin as a\r\nsafety net, for those instances where you forget to backup.","4":"DESCRIPTION\r\nUnless you use a revision control system, you have to write backups yourself.\r\nThe writebackup.vim plugin makes that a simple :WriteBackup command from\r\nwithin Vim, but you still have to remember to trigger the backup. The\r\nwritebackupVersionControl.vim extension can make up for a missed backup when\r\nyou have already made changes to the buffer, but have not persisted them yet,\r\nvia :WriteBackupOfSavedOriginal. Still, wouldn't it be nice if Vim detected\r\nthat you have made backups of a file in the past, and automatically creates a\r\nnew backup - without any action on your side?\r\n\r\nThis plugin builds on the writebackup.vim and\r\nwritebackupVersionControl.vim plugins, and automatically writes a backup on\r\na day's first write of a file that was backed up in the past, but not yet\r\ntoday.\r\nThis gives you one no-hassle, worry-free backup every day. For many\r\nwritebackup.vim use cases (like editing config files distributed all over\r\n\/etc\/), this initial \"good state from the past\" backup is the most important\r\none. (And of course you can still manually trigger additional checkpoint\r\nbackups via :WriteBackup as in the past.)\r\n\r\nUSAGE\r\nOnce any backup exists (you can check via :WriteBackupListVersions), a new\r\nbackup will be written on each day when you first persist the buffer via\r\n:write, provided that the file has not been modified yet today. (Otherwise,\r\nyou would not be able to undo the automatic backup via\r\n:WriteBackupDeleteLastBackup; the automatic backup would keep reappearing\r\nafter each :write.) Watch out for file synchronization tools and version\r\ncontrol systems that may silently update the file modification date to today\r\nand therefore prevent automatic backups!\r\nFor this and other reasons, it is still a good practice to trigger backups via\r\n:WriteBackup yourself, and just use the writebackupAutomator plugin as a\r\nsafety net, for those instances where you forget to backup.","install_details":"INSTALLATION\r\nThe code is hosted in a Git repo at\r\n    https:\/\/github.com\/inkarkat\/vim-writebackupAutomator\r\nYou can use your favorite plugin manager, or \"git clone\" into a directory used\r\nfor Vim packages. Releases are on the \"stable\" branch, the latest unstable\r\ndevelopment snapshot on \"master\".\r\n\r\nThis script is also packaged as a vimball. If you have the \"gunzip\"\r\ndecompressor in your PATH, simply edit the *.vmb.gz package in Vim; otherwise,\r\ndecompress the archive first, e.g. using WinZip. Inside Vim, install by\r\nsourcing the vimball or via the :UseVimball command.\r\n    vim writebackupAutomator*.vmb.gz\r\n    :so %\r\nTo uninstall, use the :RmVimball command.\r\n\r\nDEPENDENCIES\r\n- Requires Vim 7.0 or higher.\r\n- Requires the writebackup.vim plugin (vimscript #1828), version 3.00 or\r\n  higher.\r\n- Requires the writebackupVersionControl.vim plugin (vimscript #1829),\r\n  version 3.21 or higher.\r\n- Requires the ingo-library.vim plugin (vimscript #4433), version 1.007 or\r\n  higher.\r\n\r\nINTEGRATION\r\nYou can influence the behavior of the writebackupAutomator plugin via the\r\nbuffer-local variable b:WriteBackup. When this is 0, no automatic backup will\r\nbe done even when previous backups exist. Contrariwise, when set to 1, the\r\nbuffer will be automatically backed up even when no backups exist so far.\r\nYou can use this variable in autocmds, filetype plugins or a local vimrc to\r\nchange the backup behavior for certain file types or files in a particular\r\nlocation.","5":"INSTALLATION\r\nThe code is hosted in a Git repo at\r\n    https:\/\/github.com\/inkarkat\/vim-writebackupAutomator\r\nYou can use your favorite plugin manager, or \"git clone\" into a directory used\r\nfor Vim packages. Releases are on the \"stable\" branch, the latest unstable\r\ndevelopment snapshot on \"master\".\r\n\r\nThis script is also packaged as a vimball. If you have the \"gunzip\"\r\ndecompressor in your PATH, simply edit the *.vmb.gz package in Vim; otherwise,\r\ndecompress the archive first, e.g. using WinZip. Inside Vim, install by\r\nsourcing the vimball or via the :UseVimball command.\r\n    vim writebackupAutomator*.vmb.gz\r\n    :so %\r\nTo uninstall, use the :RmVimball command.\r\n\r\nDEPENDENCIES\r\n- Requires Vim 7.0 or higher.\r\n- Requires the writebackup.vim plugin (vimscript #1828), version 3.00 or\r\n  higher.\r\n- Requires the writebackupVersionControl.vim plugin (vimscript #1829),\r\n  version 3.21 or higher.\r\n- Requires the ingo-library.vim plugin (vimscript #4433), version 1.007 or\r\n  higher.\r\n\r\nINTEGRATION\r\nYou can influence the behavior of the writebackupAutomator plugin via the\r\nbuffer-local variable b:WriteBackup. When this is 0, no automatic backup will\r\nbe done even when previous backups exist. Contrariwise, when set to 1, the\r\nbuffer will be automatically backed up even when no backups exist so far.\r\nYou can use this variable in autocmds, filetype plugins or a local vimrc to\r\nchange the backup behavior for certain file types or files in a particular\r\nlocation.","first_name":"Ingo","6":"Ingo","last_name":"Karkat","7":"Karkat","releases":[{"0":"3940","vim_version":"7.0","1":"7.0","script_version":"1.11","2":"1.11","version_comment":"- Adapt to the introduction of command aborts in WriteBackupVersionControl version 3.21. *** YOU NEED TO UPDATE to WriteBackupVersionControl (vimscript #1829) version 3.21 or higher! ***\r\n- ENH: \"Skip automatic backup; file was already modified today.\" message is annoying after each :write; Instead, give each message only once per buffer.","3":"- Adapt to the introduction of command aborts in WriteBackupVersionControl version 3.21. *** YOU NEED TO UPDATE to WriteBackupVersionControl (vimscript #1829) version 3.21 or higher! ***\r\n- ENH: \"Skip automatic backup; file was already modified today.\" message is annoying after each :write; Instead, give each message only once per buffer.","package":"writebackupAutomator-1.11.vmb.gz","4":"writebackupAutomator-1.11.vmb.gz","src_id":"27097","5":"27097","creation_date":"1585886764","6":"1585886764"},{"0":"3940","vim_version":"7.0","1":"7.0","script_version":"1.10","2":"1.10","version_comment":"Never attempt to backup when the current buffer hasn't been persisted yet, but warn in case there are already backup files lying around.","3":"Never attempt to backup when the current buffer hasn't been persisted yet, but warn in case there are already backup files lying around.","package":"writebackupAutomator.vba.gz","4":"writebackupAutomator.vba.gz","src_id":"18113","5":"18113","creation_date":"1339418222","6":"1339418222"},{"0":"3940","vim_version":"7.0","1":"7.0","script_version":"1.01","2":"1.01","version_comment":"Rename b:writebackup to b:WriteBackup to be consistent with the other\r\nconfiguration variables of the WriteBackup family, and to avoid connotation\r\nwith the built-in 'writebackup' setting.*** PLEASE UPDATE YOUR CONFIGURATION ***","3":"Rename b:writebackup to b:WriteBackup to be consistent with the other\r\nconfiguration variables of the WriteBackup family, and to avoid connotation\r\nwith the built-in 'writebackup' setting.*** PLEASE UPDATE YOUR CONFIGURATION ***","package":"writebackupAutomator.vba.gz","4":"writebackupAutomator.vba.gz","src_id":"17535","5":"17535","creation_date":"1330361963","6":"1330361963"},{"0":"3940","vim_version":"7.0","1":"7.0","script_version":"1.00","2":"1.00","version_comment":"Initial upload","3":"Initial upload","package":"writebackupAutomator.vba.gz","4":"writebackupAutomator.vba.gz","src_id":"17473","5":"17473","creation_date":"1329402378","6":"1329402378"}]},"3939":{"script_id":"3939","0":"3939","script_name":"ipyqtmacvim.vim","1":"ipyqtmacvim.vim","script_type":"ftplugin","2":"ftplugin","summary":"Plugin to send commands from MacVim to IPython Qt console","3":"Plugin to send commands from MacVim to IPython Qt console","description":"ipyqtmacvim - Plugin to send commands from MacVim to IPython Qt console\r\n\r\nLanguage:     Python\r\nMaintainer:   Justin Kitzes <jkitzes@berkeley.edu>\r\nLicense:      BSD New\r\nRequires:     MacVim 7.3, Mac OS X (osascript), IPython 0.12\r\nLast Change:  2012-03-17\r\nVersion:      0.12\r\n\r\nApproximate the R or Matlab GUI experience using MacVim and IPython.\r\n\r\nThis plugin provides the ability to run an entire file, a line, or\r\nhighlighted text from MacVim directly in the IPython 0.12 Qt console. This is \r\nintended to replicate the look and feel of integrated GUI environments such as \r\nR for Mac OS X, in which a user has an open editor window next to a console \r\nwindow, and within which a shortcut command will send lines or the entire file \r\nfrom the editor window directly to the console window.\r\n\r\nipyqtmacvim accomplishes this by copying the selection or file path to the \r\nsystem clipboard, switching to the Python window, and pasting the command. \r\n<Cmd-4> will run a single line (normal mode) or a selection (visual mode) and \r\n<Cmd-5> will run the entire file (you can customize these hotkeys at the end \r\nof this plugin).\r\n\r\nThe plugin requires a companion Applescript file ipyqtmacvim.scpt and the \r\navailability of osascript on the command line - as such, it will only work on \r\nrelatively recent versions of Mac OS X.\r\n\r\nSee http:\/\/github.com\/jkitzes\/ipyqtmacvim\/ for updates. \r\n\r\nSee also the excellent vim-ipython plugin by Paul Ivanov. ipyqtmacvim should \r\nbe preferred to vim-ipython only for users who are specifically looking to \r\nreplicate the feel of an R or Matlab GUI (and who use MacVim and IPython).\r\n\r\nInstallation\r\n------------\r\n\r\n1. Place this file and ipyqtmacvim.scpt in ~\/.vim\/ftplugins\/python\r\n\r\n2. Launch an IPython Qt console at the command line with \"ipython qtconsole\", \r\nopen a python file in MacVim, and use the hotkeys. Note that if you have \r\nmultiple Python windows open, the lines will be sent to the first that was \r\nopened.\r\n\r\nConfiguration\r\n-------------\r\n1. The hotkeys can be configured at the bottom of this script.\r\n\r\n2. The script can be configured to send lines to Terminal (or any other named \r\napplication) by changing the phrase <...whose name is \"Python\"> in the \r\nApplescript to <...whose name is \"Terminal\">. This is handy for those who do \r\nnot want to use the Qt console. Note, however, that this will likely break the \r\nability to send multi-line statements (single lines and running the entire \r\nfile should work fine).\r\n\r\nTroubleshooting\r\n---------------\r\n\r\n* If you find that the Python commands are typed in an unusual location (such \r\nas back in your file in Vim), or that nothing appears to happen, then your Mac \r\nmay be unable to switch focus from the MacVim window to the console window \r\nfast enough before pasting. Open the ipyqtmacvim Applescript file and increase \r\nthe delay values there.\r\n\r\n* There may be a delay in sending the first command to the Python window. \r\nSubsequent commands should work more quickly.\r\n\r\n* Multi-line statements (other than those ending in 'return') will not \r\nexecute automatically and will remain until Enter is pressed one additional \r\ntime in the console. This is a known behavior.\r\n\r\nContact\r\n-------\r\n\r\nJustin Kitzes at jkitzes@berkeley.edu","4":"ipyqtmacvim - Plugin to send commands from MacVim to IPython Qt console\r\n\r\nLanguage:     Python\r\nMaintainer:   Justin Kitzes <jkitzes@berkeley.edu>\r\nLicense:      BSD New\r\nRequires:     MacVim 7.3, Mac OS X (osascript), IPython 0.12\r\nLast Change:  2012-03-17\r\nVersion:      0.12\r\n\r\nApproximate the R or Matlab GUI experience using MacVim and IPython.\r\n\r\nThis plugin provides the ability to run an entire file, a line, or\r\nhighlighted text from MacVim directly in the IPython 0.12 Qt console. This is \r\nintended to replicate the look and feel of integrated GUI environments such as \r\nR for Mac OS X, in which a user has an open editor window next to a console \r\nwindow, and within which a shortcut command will send lines or the entire file \r\nfrom the editor window directly to the console window.\r\n\r\nipyqtmacvim accomplishes this by copying the selection or file path to the \r\nsystem clipboard, switching to the Python window, and pasting the command. \r\n<Cmd-4> will run a single line (normal mode) or a selection (visual mode) and \r\n<Cmd-5> will run the entire file (you can customize these hotkeys at the end \r\nof this plugin).\r\n\r\nThe plugin requires a companion Applescript file ipyqtmacvim.scpt and the \r\navailability of osascript on the command line - as such, it will only work on \r\nrelatively recent versions of Mac OS X.\r\n\r\nSee http:\/\/github.com\/jkitzes\/ipyqtmacvim\/ for updates. \r\n\r\nSee also the excellent vim-ipython plugin by Paul Ivanov. ipyqtmacvim should \r\nbe preferred to vim-ipython only for users who are specifically looking to \r\nreplicate the feel of an R or Matlab GUI (and who use MacVim and IPython).\r\n\r\nInstallation\r\n------------\r\n\r\n1. Place this file and ipyqtmacvim.scpt in ~\/.vim\/ftplugins\/python\r\n\r\n2. Launch an IPython Qt console at the command line with \"ipython qtconsole\", \r\nopen a python file in MacVim, and use the hotkeys. Note that if you have \r\nmultiple Python windows open, the lines will be sent to the first that was \r\nopened.\r\n\r\nConfiguration\r\n-------------\r\n1. The hotkeys can be configured at the bottom of this script.\r\n\r\n2. The script can be configured to send lines to Terminal (or any other named \r\napplication) by changing the phrase <...whose name is \"Python\"> in the \r\nApplescript to <...whose name is \"Terminal\">. This is handy for those who do \r\nnot want to use the Qt console. Note, however, that this will likely break the \r\nability to send multi-line statements (single lines and running the entire \r\nfile should work fine).\r\n\r\nTroubleshooting\r\n---------------\r\n\r\n* If you find that the Python commands are typed in an unusual location (such \r\nas back in your file in Vim), or that nothing appears to happen, then your Mac \r\nmay be unable to switch focus from the MacVim window to the console window \r\nfast enough before pasting. Open the ipyqtmacvim Applescript file and increase \r\nthe delay values there.\r\n\r\n* There may be a delay in sending the first command to the Python window. \r\nSubsequent commands should work more quickly.\r\n\r\n* Multi-line statements (other than those ending in 'return') will not \r\nexecute automatically and will remain until Enter is pressed one additional \r\ntime in the console. This is a known behavior.\r\n\r\nContact\r\n-------\r\n\r\nJustin Kitzes at jkitzes@berkeley.edu","install_details":"","5":"","first_name":"Justin","6":"Justin","last_name":"Kitzes","7":"Kitzes","releases":[{"0":"3939","vim_version":"7.3","1":"7.3","script_version":"0.12","2":"0.12","version_comment":"Remove requirement for vim to globally use system clipboard","3":"Remove requirement for vim to globally use system clipboard","package":"ipyqtmacvim.tar.gz","4":"ipyqtmacvim.tar.gz","src_id":"17603","5":"17603","creation_date":"1332006801","6":"1332006801"}]},"3938":{"script_id":"3938","0":"3938","script_name":"Trailer Trash","1":"Trailer Trash","script_type":"syntax","2":"syntax","summary":"Highlight trailing white space","3":"Highlight trailing white space","description":"Highlight and eradicate whitespace at the end of the line in Vim.\r\n\r\nThis plugin will highlight trailing whitespace at the end of the line. This is done in a polite way:\r\n\r\n * You are not currently editing that line (prevents highlighting it as you type)\r\n * You are not in insert mode\r\n\r\nIt also introduces a :Trim command that will strip all the trailing white space from a file (or range). This is done in a polite way:\r\n\r\n * Places the cursor back where is started\r\n * Resets the search highlight back to what it was\r\n\r\nTrailerTrash defines `a :Trailer` command to stop showing unwanted whitespace, for those projects where you don't want to start fighting it.\r\n\r\nAs always, Trailer Trash is polite.\r\n\r\nThe source is on github here: https:\/\/github.com\/csexton\/trailertrash.vim","4":"Highlight and eradicate whitespace at the end of the line in Vim.\r\n\r\nThis plugin will highlight trailing whitespace at the end of the line. This is done in a polite way:\r\n\r\n * You are not currently editing that line (prevents highlighting it as you type)\r\n * You are not in insert mode\r\n\r\nIt also introduces a :Trim command that will strip all the trailing white space from a file (or range). This is done in a polite way:\r\n\r\n * Places the cursor back where is started\r\n * Resets the search highlight back to what it was\r\n\r\nTrailerTrash defines `a :Trailer` command to stop showing unwanted whitespace, for those projects where you don't want to start fighting it.\r\n\r\nAs always, Trailer Trash is polite.\r\n\r\nThe source is on github here: https:\/\/github.com\/csexton\/trailertrash.vim","install_details":"Copy trailertrash.vim to VIM_HOME\/plugins\/ or use pathogen.","5":"Copy trailertrash.vim to VIM_HOME\/plugins\/ or use pathogen.","first_name":"Christopher","6":"Christopher","last_name":"Sexton","7":"Sexton","releases":[{"0":"3938","vim_version":"7.0","1":"7.0","script_version":"2.0","2":"2.0","version_comment":"Added support for ranges and a \"b:show_trailertrash\" variable for disabling it with autocmds.","3":"Added support for ranges and a \"b:show_trailertrash\" variable for disabling it with autocmds.","package":"trailertrash.vim","4":"trailertrash.vim","src_id":"20658","5":"20658","creation_date":"1376574058","6":"1376574058"},{"0":"3938","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"trailertrash.vim","4":"trailertrash.vim","src_id":"17469","5":"17469","creation_date":"1329332830","6":"1329332830"}]},"3937":{"script_id":"3937","0":"3937","script_name":"vim-wmfs","1":"vim-wmfs","script_type":"syntax","2":"syntax","summary":"Syntax highlight  for wmfs.","3":"Syntax highlight  for wmfs.","description":"This project provides syntax highlight for wmfs. It will highlight all standard keyname configuration, and attribut.","4":"This project provides syntax highlight for wmfs. It will highlight all standard keyname configuration, and attribut.","install_details":"Decompress archive: tar -zxvf vim-wmfs.tar.gz,  in your .vim\r\n","5":"Decompress archive: tar -zxvf vim-wmfs.tar.gz,  in your .vim\r\n","first_name":"Natal","6":"Natal","last_name":"Ng\u00c3\u00a9tal","7":"Ng\u00c3\u00a9tal","releases":[{"0":"3937","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"vim-wmfs.tar.gz","4":"vim-wmfs.tar.gz","src_id":"17462","5":"17462","creation_date":"1329255210","6":"1329255210"}]},"3936":{"script_id":"3936","0":"3936","script_name":"Coverity compiler plugin","1":"Coverity compiler plugin","script_type":"utility","2":"utility","summary":"Compiler plugin for the cov-format-errors command in Coverity static analysis","3":"Compiler plugin for the cov-format-errors command in Coverity static analysis","description":"Simple compiler plugin to set up an errorformat and makeprg for the cov-format-errors command which ships with Coverity Static Analysis ( http:\/\/coverity.com\/products\/static-analysis.html ). Mostly useful for quick tests since it does not communicate with the Integrity Manager at all. If you want that, Coverity (the company) has a solution which does in their knowledge center ( http:\/\/coverity5.coverity.com\/node\/520 ), but I've not tried it.\r\n\r\nCurrently without documentation, this script pretty self explanatory. Use :compiler coverity to set the compiler, as normal.\r\n\r\nWhen setting the compiler, the script will prompt you for a path to the Coverity emit\/intermediate directory you are interested in parsing. You can optionally set the variable b:coverity_emit_dir to this path and it will just use the path instead of prompting you.","4":"Simple compiler plugin to set up an errorformat and makeprg for the cov-format-errors command which ships with Coverity Static Analysis ( http:\/\/coverity.com\/products\/static-analysis.html ). Mostly useful for quick tests since it does not communicate with the Integrity Manager at all. If you want that, Coverity (the company) has a solution which does in their knowledge center ( http:\/\/coverity5.coverity.com\/node\/520 ), but I've not tried it.\r\n\r\nCurrently without documentation, this script pretty self explanatory. Use :compiler coverity to set the compiler, as normal.\r\n\r\nWhen setting the compiler, the script will prompt you for a path to the Coverity emit\/intermediate directory you are interested in parsing. You can optionally set the variable b:coverity_emit_dir to this path and it will just use the path instead of prompting you.","install_details":"Place into the \"compiler\" directory on your runtimepath (e.g. ~\/.vim\/compiler or C:\\Documents and Settings\\username\\vimfiles\\compiler). Done! You don't even need to restart Vim.","5":"Place into the \"compiler\" directory on your runtimepath (e.g. ~\/.vim\/compiler or C:\\Documents and Settings\\username\\vimfiles\\compiler). Done! You don't even need to restart Vim.","first_name":"Ben","6":"Ben","last_name":"Fritz","7":"Fritz","releases":[{"0":"3936","vim_version":"7.0","1":"7.0","script_version":"2","2":"2","version_comment":"Update error format for lines starting like \"path:\" instead of with the filename directly (hurray for inconsistent formats!)","3":"Update error format for lines starting like \"path:\" instead of with the filename directly (hurray for inconsistent formats!)","package":"coverity.vim","4":"coverity.vim","src_id":"19652","5":"19652","creation_date":"1363401666","6":"1363401666"},{"0":"3936","vim_version":"7.0","1":"7.0","script_version":"1","2":"1","version_comment":"Initial upload","3":"Initial upload","package":"coverity.vim","4":"coverity.vim","src_id":"17461","5":"17461","creation_date":"1329244070","6":"1329244070"}]},"3935":{"script_id":"3935","0":"3935","script_name":"thinkpad.vim","1":"thinkpad.vim","script_type":"color scheme","2":"color scheme","summary":"dark and simple colorscheme","3":"dark and simple colorscheme","description":"Dark one using 3 colors of IBM Thinkpad Logo. Supports gui and cterm.","4":"Dark one using 3 colors of IBM Thinkpad Logo. Supports gui and cterm.","install_details":"Simply open thinkpad.vba file then execute :so\r\n\r\n:so %","5":"Simply open thinkpad.vba file then execute :so\r\n\r\n:so %","first_name":"Daehyub","6":"Daehyub","last_name":"Kim","7":"Kim","releases":[{"0":"3935","vim_version":"7.3","1":"7.3","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"thinkpad.vba","4":"thinkpad.vba","src_id":"17459","5":"17459","creation_date":"1329235611","6":"1329235611"}]},"3934":{"script_id":"3934","0":"3934","script_name":"editorconfig-vim","1":"editorconfig-vim","script_type":"utility","2":"utility","summary":"EditorConfig Plugin for Vim -- helps define and maintain consistent coding style","3":"EditorConfig Plugin for Vim -- helps define and maintain consistent coding style","description":"Many details could be found on the github page: https:\/\/github.com\/editorconfig\/editorconfig-vim\r\n\r\nEditorConfig helps developers define and maintain consistent coding styles for their projects for different editors and IDEs. The EditorConfig project consists of a file format for defining coding styles and a collection of text editor plugins that enable editors to read the file format and adhere to defined styles. EditorConfig files are easily readibly and they work nicely with version control systems.\r\n\r\nThis plugin is the EditorConfig plugin for vim.\r\n\r\n\r\nPlease submit any bug you found to the issue tracker: https:\/\/github.com\/editorconfig\/editorconfig\/issues, and tag it \"plugin - vim\", or send an email to the mailing list: editorconfig@googlegroups.com","4":"Many details could be found on the github page: https:\/\/github.com\/editorconfig\/editorconfig-vim\r\n\r\nEditorConfig helps developers define and maintain consistent coding styles for their projects for different editors and IDEs. The EditorConfig project consists of a file format for defining coding styles and a collection of text editor plugins that enable editors to read the file format and adhere to defined styles. EditorConfig files are easily readibly and they work nicely with version control systems.\r\n\r\nThis plugin is the EditorConfig plugin for vim.\r\n\r\n\r\nPlease submit any bug you found to the issue tracker: https:\/\/github.com\/editorconfig\/editorconfig\/issues, and tag it \"plugin - vim\", or send an email to the mailing list: editorconfig@googlegroups.com","install_details":"If your Vim is compiled with +python feature (this is usually true on most Linux distributions), the most simple way to install this plugin is to download the archive and extract it into your Vim runtime directory (~\/.vim on UNIX\/Linux and $VIM_INSTALLATION_FOLDER\\vimfiles on windows).\r\n\r\nIf your Vim is not compiled with +python feature, please first download the EditorConfig core and follow the instructions in the README and INSTALL files to install it. Once the EditorConfig core is installed, download the archive and extract it into your Vim runtime directory (~\/.vim on UNIX\/Linux and $VIM_INSTALLATION_FOLDER\\vimfiles on windows).\r\n\r\nadd \"filetype plugin on\" to your vimrc if you haven't done it.\r\n","5":"If your Vim is compiled with +python feature (this is usually true on most Linux distributions), the most simple way to install this plugin is to download the archive and extract it into your Vim runtime directory (~\/.vim on UNIX\/Linux and $VIM_INSTALLATION_FOLDER\\vimfiles on windows).\r\n\r\nIf your Vim is not compiled with +python feature, please first download the EditorConfig core and follow the instructions in the README and INSTALL files to install it. Once the EditorConfig core is installed, download the archive and extract it into your Vim runtime directory (~\/.vim on UNIX\/Linux and $VIM_INSTALLATION_FOLDER\\vimfiles on windows).\r\n\r\nadd \"filetype plugin on\" to your vimrc if you haven't done it.\r\n","first_name":"EditorConfig Team","6":"EditorConfig Team","last_name":"EditorConfig Team","7":"EditorConfig Team","releases":[{"0":"3934","vim_version":"7.0","1":"7.0","script_version":"0.3.3","2":"0.3.3","version_comment":"Various bug fixes","3":"Various bug fixes","package":"editorconfig-vim-0.3.3.zip","4":"editorconfig-vim-0.3.3.zip","src_id":"23809","5":"23809","creation_date":"1450564940","6":"1450564940"},{"0":"3934","vim_version":"7.0","1":"7.0","script_version":"0.3.2","2":"0.3.2","version_comment":"Support max_line_length property (See https:\/\/github.com\/editorconfig\/editorconfig\/wiki\/EditorConfig-Properties);\r\nA lot of bug fixes","3":"Support max_line_length property (See https:\/\/github.com\/editorconfig\/editorconfig\/wiki\/EditorConfig-Properties);\r\nA lot of bug fixes","package":"editorconfig-vim-0.3.2.zip","4":"editorconfig-vim-0.3.2.zip","src_id":"20468","5":"20468","creation_date":"1372735071","6":"1372735071"},{"0":"3934","vim_version":"7.0","1":"7.0","script_version":"0.3.1","2":"0.3.1","version_comment":"Update EditorConfig Python Core, which now supports new glob matching:\r\n\r\n{s1,s2,s3} matches any of the strings given (separated by commas)","3":"Update EditorConfig Python Core, which now supports new glob matching:\r\n\r\n{s1,s2,s3} matches any of the strings given (separated by commas)","package":"editorconfig-vim-0.3.1.zip","4":"editorconfig-vim-0.3.1.zip","src_id":"19627","5":"19627","creation_date":"1362994300","6":"1362994300"},{"0":"3934","vim_version":"7.0","1":"7.0","script_version":"0.3.0","2":"0.3.0","version_comment":"Support new \"charset\", \"trim_trailing_whitespace\", and \"insert_final_newline\" properties.\r\n\r\nSee http:\/\/editorconfig.org\/#file-format-details","3":"Support new \"charset\", \"trim_trailing_whitespace\", and \"insert_final_newline\" properties.\r\n\r\nSee http:\/\/editorconfig.org\/#file-format-details","package":"editorconfig-vim-0.3.0.zip","4":"editorconfig-vim-0.3.0.zip","src_id":"18617","5":"18617","creation_date":"1347735079","6":"1347735079"},{"0":"3934","vim_version":"7.0","1":"7.0","script_version":"0.2.4","2":"0.2.4","version_comment":"Bug fixes for quickfix Window error output;\r\nUpdate the Python Core files to support .editorconfig files with BOM.","3":"Bug fixes for quickfix Window error output;\r\nUpdate the Python Core files to support .editorconfig files with BOM.","package":"editorconfig-vim-0.2.4.zip","4":"editorconfig-vim-0.2.4.zip","src_id":"18185","5":"18185","creation_date":"1340558919","6":"1340558919"},{"0":"3934","vim_version":"7.0","1":"7.0","script_version":"0.2.3","2":"0.2.3","version_comment":"Bug fixes.","3":"Bug fixes.","package":"editorconfig-vim-0.2.3.zip","4":"editorconfig-vim-0.2.3.zip","src_id":"18051","5":"18051","creation_date":"1338182814","6":"1338182814"},{"0":"3934","vim_version":"7.0","1":"7.0","script_version":"0.2.2","2":"0.2.2","version_comment":"Include the Python version EditorConfig Core to much simplify the installation procedure;\r\nvarious bug fixes.","3":"Include the Python version EditorConfig Core to much simplify the installation procedure;\r\nvarious bug fixes.","package":"editorconfig-vim-0.2.2.zip","4":"editorconfig-vim-0.2.2.zip","src_id":"17952","5":"17952","creation_date":"1336971825","6":"1336971825"},{"0":"3934","vim_version":"7.0","1":"7.0","script_version":"0.2.0","2":"0.2.0","version_comment":"Support EditorConfig v0.9 standards.\r\n\r\nSee http:\/\/editorconfig.org for more information.\r\n","3":"Support EditorConfig v0.9 standards.\r\n\r\nSee http:\/\/editorconfig.org for more information.\r\n","package":"editorconfig-vim-0.2.0.zip","4":"editorconfig-vim-0.2.0.zip","src_id":"17683","5":"17683","creation_date":"1332940438","6":"1332940438"},{"0":"3934","vim_version":"7.0","1":"7.0","script_version":"0.1.0","2":"0.1.0","version_comment":"Initial upload","3":"Initial upload","package":"editorconfig-vim-0.1.0.zip","4":"editorconfig-vim-0.1.0.zip","src_id":"17454","5":"17454","creation_date":"1329192211","6":"1329192211"}]},"3933":{"script_id":"3933","0":"3933","script_name":"argumentative.vim","1":"argumentative.vim","script_type":"utility","2":"utility","summary":"initial upload","3":"initial upload","description":"Argumentative aids with manipulating and moving between function arguments.\r\nShifting arguments with <, and >, and moving with [, and ],\r\n\r\nhttps:\/\/github.com\/PeterRincker\/vim-argumentative","4":"Argumentative aids with manipulating and moving between function arguments.\r\nShifting arguments with <, and >, and moving with [, and ],\r\n\r\nhttps:\/\/github.com\/PeterRincker\/vim-argumentative","install_details":"Extract to ~\/.vim, or ~\\vimfiles (Windows).  You'll need to regenerate helptags (fill in the install path below) \r\n\r\n:helptags ~\/.vim\/doc","5":"Extract to ~\/.vim, or ~\\vimfiles (Windows).  You'll need to regenerate helptags (fill in the install path below) \r\n\r\n:helptags ~\/.vim\/doc","first_name":"Peter","6":"Peter","last_name":"Rincker","7":"Rincker","releases":[{"0":"3933","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"vim-argumentative-93306d1.zip","4":"vim-argumentative-93306d1.zip","src_id":"17452","5":"17452","creation_date":"1329178089","6":"1329178089"}]},"3932":{"script_id":"3932","0":"3932","script_name":"murphi.vim","1":"murphi.vim","script_type":"syntax","2":"syntax","summary":"Syntax highlighting for the Murphi model checker","3":"Syntax highlighting for the Murphi model checker","description":"A syntax highlighting plugin for the Murphi model checker's description language. See http:\/\/verify.stanford.edu\/dill\/murphi.html for more info on Murphi.","4":"A syntax highlighting plugin for the Murphi model checker's description language. See http:\/\/verify.stanford.edu\/dill\/murphi.html for more info on Murphi.","install_details":"","5":"","first_name":"Diego","6":"Diego","last_name":"Ongaro","7":"Ongaro","releases":[{"0":"3932","vim_version":"7.0","1":"7.0","script_version":"1","2":"1","version_comment":"Initial upload","3":"Initial upload","package":"murphi.vim","4":"murphi.vim","src_id":"17451","5":"17451","creation_date":"1329169671","6":"1329169671"}]},"3931":{"script_id":"3931","0":"3931","script_name":"Vim-Support","1":"Vim-Support","script_type":"utility","2":"utility","summary":"VimScript IDE -- Insert code snippets, quickly comment the code and look up help","3":"VimScript IDE -- Insert code snippets, quickly comment the code and look up help","description":"Vim-Support implements a Vim Script-IDE for Vim\/gVim. It has been written to\r\nconsiderably speed up writing code in a consistent style. This is done by\r\ninserting complete statements, comments, idioms, and code snippets.\r\n\r\nSome screen shots :  https:\/\/wolfgangmehner.github.io\/vim-plugins\/vimsupport.html\r\n\r\nFor plug-in managers :  https:\/\/github.com\/WolfgangMehner\/vim-support\r\n\r\nThe help file online :  https:\/\/wolfgangmehner.github.io\/vim-plugins\/doc\/vimsupport.html\r\n\r\nThe key mappings of this plug-in :  https:\/\/wolfgangmehner.github.io\/vim-plugins\/vimsupport\/vim-hotkeys.pdf\r\n\r\nDOCUMENTATION\r\n--------------------------------------------------------\r\nThis plug-in comes with a help file (vimsupport.txt). Read it with\r\n\r\n    :help vimsupport\r\n\r\n** PLEASE READ THE DOCUMENTATION **\r\n\r\nEditing actions differ for different modes! There are a lot of features which\r\ncan be configured or customized to match your needs.\r\n\r\n","4":"Vim-Support implements a Vim Script-IDE for Vim\/gVim. It has been written to\r\nconsiderably speed up writing code in a consistent style. This is done by\r\ninserting complete statements, comments, idioms, and code snippets.\r\n\r\nSome screen shots :  https:\/\/wolfgangmehner.github.io\/vim-plugins\/vimsupport.html\r\n\r\nFor plug-in managers :  https:\/\/github.com\/WolfgangMehner\/vim-support\r\n\r\nThe help file online :  https:\/\/wolfgangmehner.github.io\/vim-plugins\/doc\/vimsupport.html\r\n\r\nThe key mappings of this plug-in :  https:\/\/wolfgangmehner.github.io\/vim-plugins\/vimsupport\/vim-hotkeys.pdf\r\n\r\nDOCUMENTATION\r\n--------------------------------------------------------\r\nThis plug-in comes with a help file (vimsupport.txt). Read it with\r\n\r\n    :help vimsupport\r\n\r\n** PLEASE READ THE DOCUMENTATION **\r\n\r\nEditing actions differ for different modes! There are a lot of features which\r\ncan be configured or customized to match your needs.\r\n\r\n","install_details":"Copy the zip archive vim-support.zip to $HOME\/.vim\/ or $VIM\/vimfiles\r\n(on the Windows platforms) and run\r\n    unzip vim-support.zip\r\nIf you have already an older version of this plug-in and you have modified the\r\ntemplate files you may want to save your templates first or copy the files from\r\nthe archive by hand. See also the file README.md within the zip file.","5":"Copy the zip archive vim-support.zip to $HOME\/.vim\/ or $VIM\/vimfiles\r\n(on the Windows platforms) and run\r\n    unzip vim-support.zip\r\nIf you have already an older version of this plug-in and you have modified the\r\ntemplate files you may want to save your templates first or copy the files from\r\nthe archive by hand. See also the file README.md within the zip file.","first_name":"Fritz","6":"Fritz","last_name":"Mehner","7":"Mehner","releases":[{"0":"3931","vim_version":"7.3","1":"7.3","script_version":"2.4","2":"2.4","version_comment":"- Add 'g:Vim_CustomTemplateFile'.\r\n- Add template personalization file and setup wizard.\r\n- Change the map for 'comment -> code' to '\\co' for consistency with the other\r\n  plug-ins. The old map '\\cu' still works, however.\r\n- New and reworked templates.\r\n- Minor changes.","3":"- Add 'g:Vim_CustomTemplateFile'.\r\n- Add template personalization file and setup wizard.\r\n- Change the map for 'comment -> code' to '\\co' for consistency with the other\r\n  plug-ins. The old map '\\cu' still works, however.\r\n- New and reworked templates.\r\n- Minor changes.","package":"vim-support.zip","4":"vim-support.zip","src_id":"24453","5":"24453","creation_date":"1471361195","6":"1471361195"},{"0":"3931","vim_version":"7.0","1":"7.0","script_version":"2.3","2":"2.3","version_comment":"+ Change the way lines of code are turned into comments\r\n  (insert no space after the quote).\r\n+ Bugfix: Better compatibility with custom mappings\r\n  (use \"normal!\", \"noremap\" and \"noremenu\" consistently).\r\n+ Bugfix: Setup of local templates in case of global installation.\r\n+ Bugfix: Renamed function which were named \"g:*\".\r\n+ Always load the newest version of the template engine available on 'runtimepath'.","3":"+ Change the way lines of code are turned into comments\r\n  (insert no space after the quote).\r\n+ Bugfix: Better compatibility with custom mappings\r\n  (use \"normal!\", \"noremap\" and \"noremenu\" consistently).\r\n+ Bugfix: Setup of local templates in case of global installation.\r\n+ Bugfix: Renamed function which were named \"g:*\".\r\n+ Always load the newest version of the template engine available on 'runtimepath'.","package":"vim-support.zip","4":"vim-support.zip","src_id":"22356","5":"22356","creation_date":"1408733818","6":"1408733818"},{"0":"3931","vim_version":"7.0","1":"7.0","script_version":"2.2","2":"2.2","version_comment":"+ Map \"adjust end-of-line com.\" now works in visual mode.\r\n+ Map \"function description (auto)\" now works in visual mode.\r\n+ Automatic function description now considers scopes.\r\n+ Improved \"adjust end-of-line comment\".\r\n+ Fixed template \"Comments.function\".\r\n+ Added \"Help -> english\".","3":"+ Map \"adjust end-of-line com.\" now works in visual mode.\r\n+ Map \"function description (auto)\" now works in visual mode.\r\n+ Automatic function description now considers scopes.\r\n+ Improved \"adjust end-of-line comment\".\r\n+ Fixed template \"Comments.function\".\r\n+ Added \"Help -> english\".","package":"vim-support.zip","4":"vim-support.zip","src_id":"21261","5":"21261","creation_date":"1388423601","6":"1388423601"},{"0":"3931","vim_version":"7.0","1":"7.0","script_version":"2.1","2":"2.1","version_comment":"+ Menus generated in correct order.\r\n+ Menus show the correct mapleader.\r\n+ Maps are created for modifiable help buffers, depending on the option \"g:Vim_CreateMapsForHelp\".\r\n+ Changed map for Vim keyword help: \\h -> \\hk\r\n+ Map creation is triggered by the \"FileType\" event.\r\n+ New hotkey \\hp.\r\n+ Minor changes and bugfixes.","3":"+ Menus generated in correct order.\r\n+ Menus show the correct mapleader.\r\n+ Maps are created for modifiable help buffers, depending on the option \"g:Vim_CreateMapsForHelp\".\r\n+ Changed map for Vim keyword help: \\h -> \\hk\r\n+ Map creation is triggered by the \"FileType\" event.\r\n+ New hotkey \\hp.\r\n+ Minor changes and bugfixes.","package":"vim-support.zip","4":"vim-support.zip","src_id":"20702","5":"20702","creation_date":"1377194587","6":"1377194587"},{"0":"3931","vim_version":"7.0","1":"7.0","script_version":"2.0","2":"2.0","version_comment":"Initial upload","3":"Initial upload","package":"vim-support.zip","4":"vim-support.zip","src_id":"17450","5":"17450","creation_date":"1329164848","6":"1329164848"}]},"3930":{"script_id":"3930","0":"3930","script_name":"jbi.vim","1":"jbi.vim","script_type":"syntax","2":"syntax","summary":"Vim syntax and filetype plugin for Motoman INFORM III","3":"Vim syntax and filetype plugin for Motoman INFORM III","description":"Vim syntax and filetype plugin for Motoman INFORM III\r\n\r\nSee also https:\/\/github.com\/matthijsk\/motoman-inform-vim-syntax","4":"Vim syntax and filetype plugin for Motoman INFORM III\r\n\r\nSee also https:\/\/github.com\/matthijsk\/motoman-inform-vim-syntax","install_details":"#### Installation with vim-plug:\r\n\r\nPut this in your .vimrc:\r\n\r\n```vim\r\ncall plug#begin('~\/.vim\/plugged')\r\n  Plug 'matthijsk\/motoman-inform-vim-syntax'\r\ncall plug#end()\r\n```\r\n\r\nFor the first installation run:\r\n\r\n    :PlugInstall\r\n\r\nUpdate every once in a while with:\r\n\r\n    :PlugUpdate\r\n\r\n#### Manual installation\r\n\r\nExtract and copy the folders \r\n`\/ftdetect`, `\/ftplugin` and `\/syntax` \r\ninto your \r\n`~\/.vim\/` or `%USERPROFILE%\\vimfiles\\` \r\ndirectory. \r\nOverwrite jbi.vim files from older installation.\r\n\r\nPut the following in your .vimrc:\r\n\r\n```vim\r\nsyntax on\r\nfiletype plugin on\r\n```\r\n","5":"#### Installation with vim-plug:\r\n\r\nPut this in your .vimrc:\r\n\r\n```vim\r\ncall plug#begin('~\/.vim\/plugged')\r\n  Plug 'matthijsk\/motoman-inform-vim-syntax'\r\ncall plug#end()\r\n```\r\n\r\nFor the first installation run:\r\n\r\n    :PlugInstall\r\n\r\nUpdate every once in a while with:\r\n\r\n    :PlugUpdate\r\n\r\n#### Manual installation\r\n\r\nExtract and copy the folders \r\n`\/ftdetect`, `\/ftplugin` and `\/syntax` \r\ninto your \r\n`~\/.vim\/` or `%USERPROFILE%\\vimfiles\\` \r\ndirectory. \r\nOverwrite jbi.vim files from older installation.\r\n\r\nPut the following in your .vimrc:\r\n\r\n```vim\r\nsyntax on\r\nfiletype plugin on\r\n```\r\n","first_name":"Matthijs","6":"Matthijs","last_name":"Kool","7":"Kool","releases":[{"0":"3930","vim_version":"8.0","1":"8.0","script_version":"2.0","2":"2.0","version_comment":"Updated version with many improvements by Patrick Meiser-Knosowski. Tested with vim 8.1.1.","3":"Updated version with many improvements by Patrick Meiser-Knosowski. Tested with vim 8.1.1.","package":"jbi.zip","4":"jbi.zip","src_id":"26847","5":"26847","creation_date":"1574314317","6":"1574314317"},{"0":"3930","vim_version":"7.3","1":"7.3","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"jbi.vim","4":"jbi.vim","src_id":"17449","5":"17449","creation_date":"1329161804","6":"1329161804"}]},"3929":{"script_id":"3929","0":"3929","script_name":"badwolf","1":"badwolf","script_type":"color scheme","2":"color scheme","summary":"A dark colorscheme pieced together from various colors I like.","3":"A dark colorscheme pieced together from various colors I like.","description":"Full description and screenshots: http:\/\/stevelosh.com\/projects\/badwolf\/","4":"Full description and screenshots: http:\/\/stevelosh.com\/projects\/badwolf\/","install_details":"","5":"","first_name":"Steve","6":"Steve","last_name":"Losh","7":"Losh","releases":[{"0":"3929","vim_version":"7.0","1":"7.0","script_version":"1.5.0","2":"1.5.0","version_comment":"* Support for highlighting the tab line\r\n* g:badwolf_tabline setting\r\n* g:badwolf_darkgutter setting\r\n* Support for the Rainbow Parentheses plugin","3":"* Support for highlighting the tab line\r\n* g:badwolf_tabline setting\r\n* g:badwolf_darkgutter setting\r\n* Support for the Rainbow Parentheses plugin","package":"badwolf.zip","4":"badwolf.zip","src_id":"20544","5":"20544","creation_date":"1374281852","6":"1374281852"},{"0":"3929","vim_version":"7.0","1":"7.0","script_version":"1.4.0","2":"1.4.0","version_comment":"* Fixed SpellBad background.\r\n* Added an option for highlighting CSS properties.\r\n* LaTeX support.","3":"* Fixed SpellBad background.\r\n* Added an option for highlighting CSS properties.\r\n* LaTeX support.","package":"badwolf.zip","4":"badwolf.zip","src_id":"18581","5":"18581","creation_date":"1347295400","6":"1347295400"},{"0":"3929","vim_version":"7.0","1":"7.0","script_version":"1.3.0","2":"1.3.0","version_comment":"* More Python support.\r\n* More HTML support.\r\n* Initial MySQL support.\r\n* Initial Mutt port in contrib\/","3":"* More Python support.\r\n* More HTML support.\r\n* Initial MySQL support.\r\n* Initial Mutt port in contrib\/","package":"badwolf.zip","4":"badwolf.zip","src_id":"18074","5":"18074","creation_date":"1338558433","6":"1338558433"},{"0":"3929","vim_version":"7.0","1":"7.0","script_version":"1.2.0","2":"1.2.0","version_comment":"* Support for the SLIMV plugin.\r\n* Support for python-mode.\r\n* Support for diffs.\r\n* Better Markdown support.\r\n* Minor terminal color tweaks.\r\n* Fix SpellCap background.\r\n* Add configuration for HTML link underlining.\r\n* Disable in non-256 color terminals.","3":"* Support for the SLIMV plugin.\r\n* Support for python-mode.\r\n* Support for diffs.\r\n* Better Markdown support.\r\n* Minor terminal color tweaks.\r\n* Fix SpellCap background.\r\n* Add configuration for HTML link underlining.\r\n* Disable in non-256 color terminals.","package":"badwolf.zip","4":"badwolf.zip","src_id":"17747","5":"17747","creation_date":"1334065174","6":"1334065174"},{"0":"3929","vim_version":"7.0","1":"7.0","script_version":"1.1.2","2":"1.1.2","version_comment":"Initial upload","3":"Initial upload","package":"badwolf.zip","4":"badwolf.zip","src_id":"17447","5":"17447","creation_date":"1329152158","6":"1329152158"}]},"3928":{"script_id":"3928","0":"3928","script_name":"phpcs.vim","1":"phpcs.vim","script_type":"utility","2":"utility","summary":"PHP coding rules checking utility","3":"PHP coding rules checking utility","description":"This plugin relies on PHP_CodeSniffer package.It parse the result of phpcs and redirect it into vim's quickfix buffer.\r\nSo users can navigate the codding rule error place use ':cnext' and ':cprev'.\r\nPHP_CodeSniffer is a utility developed for checking codding rules for PHP scripts.\r\nFor more information about PHP_CodeSniffer, see http:\/\/pear.php.net\/package\/PHP_CodeSniffer\/\r\n\r\nTo use this plugin, you must have these global variables set:\r\n 1. The list of coding rule standards to follow, with each one seperated by comma.                                                        \r\n     let g:phpcs_std_list=\"Zend, PEAR\"\r\n \r\n 2. Your VCS type(Only needed when running 'Phpcs commit')\r\n     let g:phpcs_vcs_type = 'svn'\r\n\r\n     Currently only support 'svn' or  'cvs'.\r\n\r\n 3. Set the max allowed output lines. \r\n     This is useful in case there are too many errors and memory is running out.\r\n    \r\n      let g:phpcs_max_output = 0 \" Unlimited output.\r\n      or\r\n      let g:phpcs_max_output = 2000 \" Output limited to 2000 line\r\n\r\nFollowing command are provided:\r\n\r\n :Phpcs          \" Check the current file, if not in DIFF mode.\r\n                       \"  Check the modified lines only, if in DIFF mode. And in DIFF mode, call  :Phpcs twice, it will switch back and update the DIFF view.\r\n :Phpcs commit   \" Checking PHP  files to be commited in the directory recursively\r\n :Phpcs all           \" Checking PHP files in the current directory recursively\r\n\r\nYou can map shortcuts for your convenience. For example, in my working environment, we do following mappings:\r\n\" input mode map\r\ninoremap <F5>  <ESC>:Phpcs<CR>\r\ninoremap <F7> <ESC>:cprev<CR>\r\ninoremap <F8> <ESC>:cnext<CR>\r\n\r\n\"normal mode map\r\nnoremap <F5>  <ESC>:Phpcs<CR>\r\nnoremap <F7> <Esc>:cprev<CR>\r\nnoremap <F8> <ESC>:cnext<CR>\r\n\r\nNote for the Phpcs in DIFF mode:\r\n1. Why support Phpcs in DIFF mode?\r\nDue to historical reasons, there exist a lot of old codes not following the new coding standards. Our policy is that, for the new codes added, must following the coding standards; but keep the old codes as it is.\r\nSo we only need to check the new codes to be committed. \r\n\r\n2. Which scenario does this mode work?\r\nIn this scenario, we use vimdiff for the extra diff command of svn diff. Before we commit the codes, we run svn diff, which in turn will call vimdiff to show what has been changed in codes.\r\nHere we call :Phpcs command, to do the checking, and that will only output errors\/warning in the lines modified in this commit.\r\n\r\n3. The Phpcs in DIFF mode is not flexible!\r\nYou should make sure that:  ONLY TWO WINDOWS EXIST IN DIFF VIEW, THE 1ST ONE IS THE ORIGINAL FILE, THE 2ND ONE IS THE MODIFIED FILE.\r\nIf you use other plugins and they open windows automatically in vimdiff mode, you should close it first manually or add codes to do this in phpcs.vim.\r\nIn the 1.1 version, I added codes to detect MiniBufExpl plugin, and close it automatically. Just for your reference.","4":"This plugin relies on PHP_CodeSniffer package.It parse the result of phpcs and redirect it into vim's quickfix buffer.\r\nSo users can navigate the codding rule error place use ':cnext' and ':cprev'.\r\nPHP_CodeSniffer is a utility developed for checking codding rules for PHP scripts.\r\nFor more information about PHP_CodeSniffer, see http:\/\/pear.php.net\/package\/PHP_CodeSniffer\/\r\n\r\nTo use this plugin, you must have these global variables set:\r\n 1. The list of coding rule standards to follow, with each one seperated by comma.                                                        \r\n     let g:phpcs_std_list=\"Zend, PEAR\"\r\n \r\n 2. Your VCS type(Only needed when running 'Phpcs commit')\r\n     let g:phpcs_vcs_type = 'svn'\r\n\r\n     Currently only support 'svn' or  'cvs'.\r\n\r\n 3. Set the max allowed output lines. \r\n     This is useful in case there are too many errors and memory is running out.\r\n    \r\n      let g:phpcs_max_output = 0 \" Unlimited output.\r\n      or\r\n      let g:phpcs_max_output = 2000 \" Output limited to 2000 line\r\n\r\nFollowing command are provided:\r\n\r\n :Phpcs          \" Check the current file, if not in DIFF mode.\r\n                       \"  Check the modified lines only, if in DIFF mode. And in DIFF mode, call  :Phpcs twice, it will switch back and update the DIFF view.\r\n :Phpcs commit   \" Checking PHP  files to be commited in the directory recursively\r\n :Phpcs all           \" Checking PHP files in the current directory recursively\r\n\r\nYou can map shortcuts for your convenience. For example, in my working environment, we do following mappings:\r\n\" input mode map\r\ninoremap <F5>  <ESC>:Phpcs<CR>\r\ninoremap <F7> <ESC>:cprev<CR>\r\ninoremap <F8> <ESC>:cnext<CR>\r\n\r\n\"normal mode map\r\nnoremap <F5>  <ESC>:Phpcs<CR>\r\nnoremap <F7> <Esc>:cprev<CR>\r\nnoremap <F8> <ESC>:cnext<CR>\r\n\r\nNote for the Phpcs in DIFF mode:\r\n1. Why support Phpcs in DIFF mode?\r\nDue to historical reasons, there exist a lot of old codes not following the new coding standards. Our policy is that, for the new codes added, must following the coding standards; but keep the old codes as it is.\r\nSo we only need to check the new codes to be committed. \r\n\r\n2. Which scenario does this mode work?\r\nIn this scenario, we use vimdiff for the extra diff command of svn diff. Before we commit the codes, we run svn diff, which in turn will call vimdiff to show what has been changed in codes.\r\nHere we call :Phpcs command, to do the checking, and that will only output errors\/warning in the lines modified in this commit.\r\n\r\n3. The Phpcs in DIFF mode is not flexible!\r\nYou should make sure that:  ONLY TWO WINDOWS EXIST IN DIFF VIEW, THE 1ST ONE IS THE ORIGINAL FILE, THE 2ND ONE IS THE MODIFIED FILE.\r\nIf you use other plugins and they open windows automatically in vimdiff mode, you should close it first manually or add codes to do this in phpcs.vim.\r\nIn the 1.1 version, I added codes to detect MiniBufExpl plugin, and close it automatically. Just for your reference.","install_details":"Put phpcs.vim at ~\/.vim\/plugin\/phpcs.vim.","5":"Put phpcs.vim at ~\/.vim\/plugin\/phpcs.vim.","first_name":"Kai","6":"Kai","last_name":"ZHANG","7":"ZHANG","releases":[{"0":"3928","vim_version":"7.0","1":"7.0","script_version":"1.1","2":"1.1","version_comment":"Fixed the issue that when minibufexpl plugin enabled, the window operation is totally wrong in DIFF mode. ","3":"Fixed the issue that when minibufexpl plugin enabled, the window operation is totally wrong in DIFF mode. ","package":"phpcs.vim","4":"phpcs.vim","src_id":"17659","5":"17659","creation_date":"1332728610","6":"1332728610"},{"0":"3928","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload.","3":"Initial upload.","package":"phpcs.vim","4":"phpcs.vim","src_id":"17453","5":"17453","creation_date":"1329183157","6":"1329183157"}]},"3927":{"script_id":"3927","0":"3927","script_name":"vim-flake8","1":"vim-flake8","script_type":"ftplugin","2":"ftplugin","summary":"vim-flake8 is a Vim plugin that runs the currently open file through Flake8.","3":"vim-flake8 is a Vim plugin that runs the currently open file through Flake8.","description":"vim-flake8 is a Vim plugin that runs the currently open file through Flake8, a static syntax and style checker for Python source code. It supersedes both vim-pyflakes and vim-pep8.\r\n\r\nFlake8 is a wrapper around PyFlakes (static syntax checker), PEP8 (style checker) and Ned's MacCabe script (complexity checker).\r\n","4":"vim-flake8 is a Vim plugin that runs the currently open file through Flake8, a static syntax and style checker for Python source code. It supersedes both vim-pyflakes and vim-pep8.\r\n\r\nFlake8 is a wrapper around PyFlakes (static syntax checker), PEP8 (style checker) and Ned's MacCabe script (complexity checker).\r\n","install_details":"Use vim-pathogen if you're not using it already. Then, simply put the contents of this repository in your ~\/.vim\/bundle directory.","5":"Use vim-pathogen if you're not using it already. Then, simply put the contents of this repository in your ~\/.vim\/bundle directory.","first_name":"Vincent","6":"Vincent","last_name":"Driessen","7":"Driessen","releases":[{"0":"3927","vim_version":"7.0","1":"7.0","script_version":"1.3","2":"1.3","version_comment":"Added option support for --builtins and --max-complexity.","3":"Added option support for --builtins and --max-complexity.","package":"python_flake8.vim","4":"python_flake8.vim","src_id":"18843","5":"18843","creation_date":"1350718745","6":"1350718745"},{"0":"3927","vim_version":"7.0","1":"7.0","script_version":"1.2","2":"1.2","version_comment":"This version adds support for more configuration options, like g:flake8_max_line_length and g:flake8_ignore.","3":"This version adds support for more configuration options, like g:flake8_max_line_length and g:flake8_ignore.","package":"python_flake8.vim","4":"python_flake8.vim","src_id":"18680","5":"18680","creation_date":"1348492366","6":"1348492366"},{"0":"3927","vim_version":"7.0","1":"7.0","script_version":"1.1","2":"1.1","version_comment":"Added support for Flake8's --ignore option.","3":"Added support for Flake8's --ignore option.","package":"python_flake8.vim","4":"python_flake8.vim","src_id":"17900","5":"17900","creation_date":"1336462951","6":"1336462951"},{"0":"3927","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"python_flake8.vim","4":"python_flake8.vim","src_id":"17443","5":"17443","creation_date":"1329125898","6":"1329125898"}]},"3926":{"script_id":"3926","0":"3926","script_name":"lout.vim","1":"lout.vim","script_type":"syntax","2":"syntax","summary":"Syntax colouring for Basser Lout","3":"Syntax colouring for Basser Lout","description":"This is the syntax colouring script for Basser Lout document formatting system. The script is shipped with Vim. Here you can find intermediate updates of the script, that will be part of the next Vim release.","4":"This is the syntax colouring script for Basser Lout document formatting system. The script is shipped with Vim. Here you can find intermediate updates of the script, that will be part of the next Vim release.","install_details":"","5":"","first_name":"Christian","6":"Christian","last_name":"Br\u00c3\u00bcssow","7":"Br\u00c3\u00bcssow","releases":[{"0":"3926","vim_version":"7.0","1":"7.0","script_version":"1.4","2":"1.4","version_comment":"Initial upload","3":"Initial upload","package":"lout.vim","4":"lout.vim","src_id":"17438","5":"17438","creation_date":"1329057360","6":"1329057360"}]},"3925":{"script_id":"3925","0":"3925","script_name":"ditaa","1":"ditaa","script_type":"syntax","2":"syntax","summary":"Vim syntax for ditaa","3":"Vim syntax for ditaa","description":"This plugin is here to help you editing ditaa (DIagrams Through Ascii Art) files: http:\/\/ditaa.sourceforge.net\/","4":"This plugin is here to help you editing ditaa (DIagrams Through Ascii Art) files: http:\/\/ditaa.sourceforge.net\/","install_details":"Copy the ditaa.vim file to $HOME\/.vim\/syntax\/ and add the following line to your vimrc:\r\nau BufRead,BufNewFile *.ditaa set ft=ditaa","5":"Copy the ditaa.vim file to $HOME\/.vim\/syntax\/ and add the following line to your vimrc:\r\nau BufRead,BufNewFile *.ditaa set ft=ditaa","first_name":"Bruno","6":"Bruno","last_name":"Michel","7":"Michel","releases":[{"0":"3925","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"ditaa.vim","4":"ditaa.vim","src_id":"17437","5":"17437","creation_date":"1329055898","6":"1329055898"}]},"3924":{"script_id":"3924","0":"3924","script_name":"flymaker","1":"flymaker","script_type":"utility","2":"utility","summary":"Another GNU Flymake-like plugin for Vim","3":"Another GNU Flymake-like plugin for Vim","description":"*** Please drop me an email to report any bugs\/issues that you find.  That can\r\ngreatly reduce the time until this thing becomes stable.  See my profile for the\r\naddress.  Thanks! ***\r\n\r\nGNU Flymake allows Emacs users to perform compilation, static analysis, and\r\nother tools in the background as they develop.  Upon each save, a\r\nbackground process is kicked off to perform the checking.  If errors are\r\nidentified, the lines containing the error are highlighted and a tooltip\r\nprovides the error message.  This is very well-suited to feature development\r\nwhere the developer spends a lot of time in a single buffer.\r\n\r\nI can see the value in this fast-paced workflow but I don't use Emacs.\r\nThere have been a few attempts to bring this functionality to Vim but each\r\nof them seem to have their limitations.  This plugin attempts to overcome\r\nthem.\r\n\r\nFor more detailed information (including outstanding issues), install and check out:\r\n\r\n:help flymaker\r\n\r\nScreenshots:\r\nhttp:\/\/i1177.photobucket.com\/albums\/x344\/seymore15074\/Flymaker1.png\r\nhttp:\/\/i1177.photobucket.com\/albums\/x344\/seymore15074\/Flymaker2.png\r\n\r\n(BTW, that cool statusline is from pwdstatus.vim!)\r\n","4":"*** Please drop me an email to report any bugs\/issues that you find.  That can\r\ngreatly reduce the time until this thing becomes stable.  See my profile for the\r\naddress.  Thanks! ***\r\n\r\nGNU Flymake allows Emacs users to perform compilation, static analysis, and\r\nother tools in the background as they develop.  Upon each save, a\r\nbackground process is kicked off to perform the checking.  If errors are\r\nidentified, the lines containing the error are highlighted and a tooltip\r\nprovides the error message.  This is very well-suited to feature development\r\nwhere the developer spends a lot of time in a single buffer.\r\n\r\nI can see the value in this fast-paced workflow but I don't use Emacs.\r\nThere have been a few attempts to bring this functionality to Vim but each\r\nof them seem to have their limitations.  This plugin attempts to overcome\r\nthem.\r\n\r\nFor more detailed information (including outstanding issues), install and check out:\r\n\r\n:help flymaker\r\n\r\nScreenshots:\r\nhttp:\/\/i1177.photobucket.com\/albums\/x344\/seymore15074\/Flymaker1.png\r\nhttp:\/\/i1177.photobucket.com\/albums\/x344\/seymore15074\/Flymaker2.png\r\n\r\n(BTW, that cool statusline is from pwdstatus.vim!)\r\n","install_details":"Extract the tarball into your ~\/.vim directory or, if you are using\r\npathogen.vim, a ~\/.vim\/bundle\/flymaker directory.\r\n\r\nAs of version 0.2.0, this plugin requires the AsyncCommand plugin found here:\r\nhttp:\/\/www.vim.org\/scripts\/script.php?script_id=3431\r\n\r\nNote that by default, an ftplugin for C++ will be added.  Turn it on via \":FlyOn\".  It likely needs\r\nconfigured to match your specific build criteria.\r\n\r\n:help flymaker","5":"Extract the tarball into your ~\/.vim directory or, if you are using\r\npathogen.vim, a ~\/.vim\/bundle\/flymaker directory.\r\n\r\nAs of version 0.2.0, this plugin requires the AsyncCommand plugin found here:\r\nhttp:\/\/www.vim.org\/scripts\/script.php?script_id=3431\r\n\r\nNote that by default, an ftplugin for C++ will be added.  Turn it on via \":FlyOn\".  It likely needs\r\nconfigured to match your specific build criteria.\r\n\r\n:help flymaker","first_name":"Chad","6":"Chad","last_name":"Moore","7":"Moore","releases":[{"0":"3924","vim_version":"7.0","1":"7.0","script_version":"0.2.0","2":"0.2.0","version_comment":"This version is worth a shot.  It should be more stable than the others (but it is still just a proof of concept).  See the documentation for specific changes.\r\n\r\nNow requires AsyncCommand 3.1","3":"This version is worth a shot.  It should be more stable than the others (but it is still just a proof of concept).  See the documentation for specific changes.\r\n\r\nNow requires AsyncCommand 3.1","package":"flymaker.tgz","4":"flymaker.tgz","src_id":"17470","5":"17470","creation_date":"1329364439","6":"1329364439"},{"0":"3924","vim_version":"7.0","1":"7.0","script_version":"0.1.3","2":"0.1.3","version_comment":"A few more minor fixes.","3":"A few more minor fixes.","package":"flymaker.tgz","4":"flymaker.tgz","src_id":"17432","5":"17432","creation_date":"1328977369","6":"1328977369"},{"0":"3924","vim_version":"7.0","1":"7.0","script_version":"0.1.2","2":"0.1.2","version_comment":"More bug fixes (most importantly the undefined variable errors introduced in 0.1.1).  See the included documentation for specific fixes in this version.  ","3":"More bug fixes (most importantly the undefined variable errors introduced in 0.1.1).  See the included documentation for specific fixes in this version.  ","package":"flymaker.tgz","4":"flymaker.tgz","src_id":"17423","5":"17423","creation_date":"1328902117","6":"1328902117"},{"0":"3924","vim_version":"7.0","1":"7.0","script_version":"0.1.1","2":"0.1.1","version_comment":"Just bug fixes (primarily involving highlighting).  See the included documentation for a complete list of changes.","3":"Just bug fixes (primarily involving highlighting).  See the included documentation for a complete list of changes.","package":"flymaker.tgz","4":"flymaker.tgz","src_id":"17419","5":"17419","creation_date":"1328847994","6":"1328847994"},{"0":"3924","vim_version":"7.0","1":"7.0","script_version":"0.1.0","2":"0.1.0","version_comment":"Initial upload","3":"Initial upload","package":"flymaker.tgz","4":"flymaker.tgz","src_id":"17412","5":"17412","creation_date":"1328743540","6":"1328743540"}]},"3923":{"script_id":"3923","0":"3923","script_name":"taskmanagementvim","1":"taskmanagementvim","script_type":"utility","2":"utility","summary":"It uses schema that uses GTD-like philosophy to let you manage tasks within vim.","3":"It uses schema that uses GTD-like philosophy to let you manage tasks within vim.","description":"This plugin uses a specific schema. You can you your own schema by easily changing the code if you want.\r\n\r\nIn fact, I wanted to keep this is as a .vimrc script so that you can easily modify it as per your need. However, plugins and changes to these plugins are easier to manage than loose scripts. Hence this attempt.\r\n\r\nI will still encourage you glance over the code and make changes as per your need.","4":"This plugin uses a specific schema. You can you your own schema by easily changing the code if you want.\r\n\r\nIn fact, I wanted to keep this is as a .vimrc script so that you can easily modify it as per your need. However, plugins and changes to these plugins are easier to manage than loose scripts. Hence this attempt.\r\n\r\nI will still encourage you glance over the code and make changes as per your need.","install_details":"There is a syntax file along with the functionality code. When you extract the archive, you will find plugin and syntax directories. Install plugin\/taskmanagement.vim to your vim plugins directory (.e.g, .vim\/plugin on Linux) and syntax\/taskmanagement.vim to corresponding syntax directory (e.g., .vim\/syntax).\r\n\r\nThe task files are stored in VIMTASKMANAGEMENTDIR directory. If you do not set it specifically, it is set to ~\/wiki.\r\n\r\nThe details of schema are explained at http:\/\/ifacethoughts.net\/2008\/05\/11\/task-management-using-vim\/ \r\n\r\nIn addition to commands mentioned there, you can use the command Pending to get a list of tasks not done in last 7 days.\r\n\r\nThe plugin depends on strftime() function. It will prompt you a message if your platform does not support strftime. Contact me at abhijit at ifacethoughts.net in case you face other problems.","5":"There is a syntax file along with the functionality code. When you extract the archive, you will find plugin and syntax directories. Install plugin\/taskmanagement.vim to your vim plugins directory (.e.g, .vim\/plugin on Linux) and syntax\/taskmanagement.vim to corresponding syntax directory (e.g., .vim\/syntax).\r\n\r\nThe task files are stored in VIMTASKMANAGEMENTDIR directory. If you do not set it specifically, it is set to ~\/wiki.\r\n\r\nThe details of schema are explained at http:\/\/ifacethoughts.net\/2008\/05\/11\/task-management-using-vim\/ \r\n\r\nIn addition to commands mentioned there, you can use the command Pending to get a list of tasks not done in last 7 days.\r\n\r\nThe plugin depends on strftime() function. It will prompt you a message if your platform does not support strftime. Contact me at abhijit at ifacethoughts.net in case you face other problems.","first_name":"Abhijit","6":"Abhijit","last_name":"Nadgouda","7":"Nadgouda","releases":[{"0":"3923","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"taskmanagementvim.tar.gz","4":"taskmanagementvim.tar.gz","src_id":"17404","5":"17404","creation_date":"1328527237","6":"1328527237"}]},"3922":{"script_id":"3922","0":"3922","script_name":"Gummybears","1":"Gummybears","script_type":"color scheme","2":"color scheme","summary":"Nice dark pastel colorscheme - for GVim \/ MacVim and 256-color terminal","3":"Nice dark pastel colorscheme - for GVim \/ MacVim and 256-color terminal","description":"This is a rewrite of the old version of gummybears, since the code in this current version is readable.\r\n\r\nIt's dark pastel theme that kinda reminds me of Gummy bears, it's based on Jellybeans.\r\n\r\nGummybears supports 256-color terminal and GVim \/ MacVim.\r\n\r\nGithub repo: https:\/\/github.com\/jelera\/vim-gummybears-colorscheme\r\n\r\nScreenshots\r\nGraphical Vim (GVIM \/ MacVim): http:\/\/imgur.com\/a\/t1A10\r\n256-color Terminal : http:\/\/imgur.com\/a\/c9uFa","4":"This is a rewrite of the old version of gummybears, since the code in this current version is readable.\r\n\r\nIt's dark pastel theme that kinda reminds me of Gummy bears, it's based on Jellybeans.\r\n\r\nGummybears supports 256-color terminal and GVim \/ MacVim.\r\n\r\nGithub repo: https:\/\/github.com\/jelera\/vim-gummybears-colorscheme\r\n\r\nScreenshots\r\nGraphical Vim (GVIM \/ MacVim): http:\/\/imgur.com\/a\/t1A10\r\n256-color Terminal : http:\/\/imgur.com\/a\/c9uFa","install_details":"Using a Plugin Manager (RECOMMENDED)\r\n I highly recommend you use a plugin manager like Pathogen or Vundle. On the command line, clone this repo and copy it to your ~\/.vim\/bundle directory.\r\n\r\n $ git clone https:\/\/github.com\/jelera\/vim-gummybears-colorscheme ~\/.vim\/bundle\r\n\r\nor\r\n\r\nCopy gummybears.vim to your ~\/.vim\/color directory.","5":"Using a Plugin Manager (RECOMMENDED)\r\n I highly recommend you use a plugin manager like Pathogen or Vundle. On the command line, clone this repo and copy it to your ~\/.vim\/bundle directory.\r\n\r\n $ git clone https:\/\/github.com\/jelera\/vim-gummybears-colorscheme ~\/.vim\/bundle\r\n\r\nor\r\n\r\nCopy gummybears.vim to your ~\/.vim\/color directory.","first_name":"Jose","6":"Jose","last_name":"Elera","7":"Elera","releases":[{"0":"3922","vim_version":"7.0","1":"7.0","script_version":"0.3","2":"0.3","version_comment":"added support for markdown","3":"added support for markdown","package":"gummybears.vim","4":"gummybears.vim","src_id":"17472","5":"17472","creation_date":"1329365343","6":"1329365343"},{"0":"3922","vim_version":"7.0","1":"7.0","script_version":"0.2","2":"0.2","version_comment":"A full rewrite to enhance readability and compatibilty with 256-color terminals. ","3":"A full rewrite to enhance readability and compatibilty with 256-color terminals. ","package":"gummybears.vim","4":"gummybears.vim","src_id":"17405","5":"17405","creation_date":"1328662099","6":"1328662099"},{"0":"3922","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"gummybears.vim","4":"gummybears.vim","src_id":"17399","5":"17399","creation_date":"1328484305","6":"1328484305"}]},"3921":{"script_id":"3921","0":"3921","script_name":"TagmaLast","1":"TagmaLast","script_type":"utility","2":"utility","summary":"Update the 'Last Changed' line in a file","3":"Update the 'Last Changed' line in a file","description":"This plugin updates the 'Last Changed' line in a file. This can be done\r\nautomatically if g:TagmaLastAutoUpdate is set. The pattern to search for and\r\nthe timestamp format can be set. When making the update :updatejoin can be\r\nused to join the change to the previous change. This allows :undo to undo\r\nboth changes. This is controlled by g:TagmaLastUseUndoJoin.\r\n\r\nThe 'Last Changed' line is matched by a regexp set in\r\ng:TagmaLastSearchRegexp. This allows any desired format to be matched.\r\n\r\nThe command UpdateLast manually updates the 'Last Changed' line.\r\nThis is mapped to <Leader>UL by default. (<Leader> is normally \"\\\")\r\n\r\nThe commands TagmaLastDisable and TagmaLastEnable disable and\r\nenable automatic updates of the 'Last Changed' line, respectively.\r\n\r\nThe timestamp that is used is set by g:TagmaLastTimeFormat.\r\nDefaults to \"%a %b %d %I:00 %p %Y %Z\".\r\nOn Windows \"%Z\" for the time zone defaults to the full name, not the\r\nthree letter abbreviation. This is detected and corrected resulting in\r\ntime zones always being the three letter abbreviation.","4":"This plugin updates the 'Last Changed' line in a file. This can be done\r\nautomatically if g:TagmaLastAutoUpdate is set. The pattern to search for and\r\nthe timestamp format can be set. When making the update :updatejoin can be\r\nused to join the change to the previous change. This allows :undo to undo\r\nboth changes. This is controlled by g:TagmaLastUseUndoJoin.\r\n\r\nThe 'Last Changed' line is matched by a regexp set in\r\ng:TagmaLastSearchRegexp. This allows any desired format to be matched.\r\n\r\nThe command UpdateLast manually updates the 'Last Changed' line.\r\nThis is mapped to <Leader>UL by default. (<Leader> is normally \"\\\")\r\n\r\nThe commands TagmaLastDisable and TagmaLastEnable disable and\r\nenable automatic updates of the 'Last Changed' line, respectively.\r\n\r\nThe timestamp that is used is set by g:TagmaLastTimeFormat.\r\nDefaults to \"%a %b %d %I:00 %p %Y %Z\".\r\nOn Windows \"%Z\" for the time zone defaults to the full name, not the\r\nthree letter abbreviation. This is detected and corrected resulting in\r\ntime zones always being the three letter abbreviation.","install_details":"Copy the files to your ~\/.vim or ~\/vimfiles directory. \r\nIf using a package manager like pathogen place the whole directory in the bundle directory.","5":"Copy the files to your ~\/.vim or ~\/vimfiles directory. \r\nIf using a package manager like pathogen place the whole directory in the bundle directory.","first_name":"Lorance","6":"Lorance","last_name":"Stinson","7":"Stinson","releases":[{"0":"3921","vim_version":"7.0","1":"7.0","script_version":"0.2","2":"0.2","version_comment":"Corrected an error when TagmaLastAutoUpdate is enabled. Added <Plug> mappings for TagmaLastDisable and TagmaLastEnable to allow easy key mappings. Changed broken timezone detection to only be performed once during startup.","3":"Corrected an error when TagmaLastAutoUpdate is enabled. Added <Plug> mappings for TagmaLastDisable and TagmaLastEnable to allow easy key mappings. Changed broken timezone detection to only be performed once during startup.","package":"TagmaLast.zip","4":"TagmaLast.zip","src_id":"17487","5":"17487","creation_date":"1329501002","6":"1329501002"}]},"3920":{"script_id":"3920","0":"3920","script_name":"WhiteWash","1":"WhiteWash","script_type":"utility","2":"utility","summary":"Add and remove whitespace with strong opinions","3":"Add and remove whitespace with strong opinions","description":"# Features\r\n\r\n* Removes whitespace at the end of lines.\r\n* Removes sequential whitespace between words.\r\n\t* Ignores whitespace at the beginning of a line (to preserve indents).\r\n* Adds spaces after commas in non-numeric strings.\r\n\t* Changes `foo(bar,baz,boo)` to `foo(bar, baz, boo)`.\r\n\t* Ignores large numbers (e.g. `1,234,456,789`), but not `foo(0,1)`.\r\n* Operates on the entire buffer by default, or a range if provided.\r\n* Aggressive mode for when you know better than the safeguards.\r\n\r\n# Options\r\n\r\n* `g:WhiteWash.auto` - Enabled rules are run whenever `:WhiteWash` is called.\r\n```vim\r\n\" Set to 0 to disable a rule\r\nlet g:WhiteWash.auto.commas = 0\r\nlet g:WhiteWash.auto.sequential = 0\r\nlet g:WhiteWash.auto.trailing = 0\r\n```\r\n\r\n* `g:WhiteWash.aggressive` - Define which rules should run with aggressive mode\r\n  by default.\r\n```vim\r\nlet g:WhiteWash.aggressive.commas = 1\r\nlet g:WhiteWash.aggressive.sequential = 1\r\n```\r\n\r\n# Commands\r\n\r\n* `:WhiteWash` - Run all enabled WhiteWash rules.\r\n* `:WhiteWashAggressive` - Run all enabled WhiteWash rules in aggressive mode.\r\n* `:WhiteWashCommas` - Run only the commas rule (respects aggressive setting).\r\n* `:WhiteWashSequential` - Run only the sequential rule (respects aggressive\r\n  setting).\r\n* `:WhiteWashTrailing` - Remove trailing whitespace.","4":"# Features\r\n\r\n* Removes whitespace at the end of lines.\r\n* Removes sequential whitespace between words.\r\n\t* Ignores whitespace at the beginning of a line (to preserve indents).\r\n* Adds spaces after commas in non-numeric strings.\r\n\t* Changes `foo(bar,baz,boo)` to `foo(bar, baz, boo)`.\r\n\t* Ignores large numbers (e.g. `1,234,456,789`), but not `foo(0,1)`.\r\n* Operates on the entire buffer by default, or a range if provided.\r\n* Aggressive mode for when you know better than the safeguards.\r\n\r\n# Options\r\n\r\n* `g:WhiteWash.auto` - Enabled rules are run whenever `:WhiteWash` is called.\r\n```vim\r\n\" Set to 0 to disable a rule\r\nlet g:WhiteWash.auto.commas = 0\r\nlet g:WhiteWash.auto.sequential = 0\r\nlet g:WhiteWash.auto.trailing = 0\r\n```\r\n\r\n* `g:WhiteWash.aggressive` - Define which rules should run with aggressive mode\r\n  by default.\r\n```vim\r\nlet g:WhiteWash.aggressive.commas = 1\r\nlet g:WhiteWash.aggressive.sequential = 1\r\n```\r\n\r\n# Commands\r\n\r\n* `:WhiteWash` - Run all enabled WhiteWash rules.\r\n* `:WhiteWashAggressive` - Run all enabled WhiteWash rules in aggressive mode.\r\n* `:WhiteWashCommas` - Run only the commas rule (respects aggressive setting).\r\n* `:WhiteWashSequential` - Run only the sequential rule (respects aggressive\r\n  setting).\r\n* `:WhiteWashTrailing` - Remove trailing whitespace.","install_details":"Extract to your `$HOME\/.vim\/` directory.","5":"Extract to your `$HOME\/.vim\/` directory.","first_name":"Michael","6":"Michael","last_name":"O'Neill","7":"O'Neill","releases":[{"0":"3920","vim_version":"7.0","1":"7.0","script_version":"2.0.0","2":"2.0.0","version_comment":"- Change the general flow of how operations occur in order to be more\r\n  modular and more customizable.\r\n- Add documentation (see `:help whitewash`).\r\n- Rework how the `:WhiteWashCommas` command works.","3":"- Change the general flow of how operations occur in order to be more\r\n  modular and more customizable.\r\n- Add documentation (see `:help whitewash`).\r\n- Rework how the `:WhiteWashCommas` command works.","package":"WhiteWash.zip","4":"WhiteWash.zip","src_id":"25904","5":"25904","creation_date":"1522161915","6":"1522161915"},{"0":"3920","vim_version":"7.3","1":"7.3","script_version":"1.2","2":"1.2","version_comment":"Add WhiteWashTrailing function and command\r\n- Allow users to call :WhiteWashTrailing to clean only whitespace at the end of lines.\r\n- Stop trying to handle trailing ^Ms. This is caused by using the DOS file format when one should be using the Unix format.\r\n- Remove the space between the words white and space (oh, the irony).","3":"Add WhiteWashTrailing function and command\r\n- Allow users to call :WhiteWashTrailing to clean only whitespace at the end of lines.\r\n- Stop trying to handle trailing ^Ms. This is caused by using the DOS file format when one should be using the Unix format.\r\n- Remove the space between the words white and space (oh, the irony).","package":"WhiteWash.vim","4":"WhiteWash.vim","src_id":"22412","5":"22412","creation_date":"1410210118","6":"1410210118"},{"0":"3920","vim_version":"7.3","1":"7.3","script_version":"0.11","2":"0.11","version_comment":"Add GetLatestVimScript support.","3":"Add GetLatestVimScript support.","package":"WhiteWash.vim","4":"WhiteWash.vim","src_id":"17373","5":"17373","creation_date":"1328237748","6":"1328237748"},{"0":"3920","vim_version":"7.3","1":"7.3","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"WhiteWash.vim","4":"WhiteWash.vim","src_id":"17372","5":"17372","creation_date":"1328236249","6":"1328236249"}]},"3919":{"script_id":"3919","0":"3919","script_name":"pfldap.vim","1":"pfldap.vim","script_type":"syntax","2":"syntax","summary":"Syntax definition for Postfix LDAP lookup map description files","3":"Syntax definition for Postfix LDAP lookup map description files","description":"Postfix supports multiple types of databases to lookup users, aliases, domains and other information (http:\/\/www.postfix.org\/DATABASE_README.html).\r\nThis syntax definition makes editing LDAP lookup table description files (http:\/\/www.postfix.org\/ldap_table.5.html) a bit easier.\r\n","4":"Postfix supports multiple types of databases to lookup users, aliases, domains and other information (http:\/\/www.postfix.org\/DATABASE_README.html).\r\nThis syntax definition makes editing LDAP lookup table description files (http:\/\/www.postfix.org\/ldap_table.5.html) a bit easier.\r\n","install_details":"","5":"","first_name":"Stanislaw","6":"Stanislaw","last_name":"Klekot","7":"Klekot","releases":[{"0":"3919","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"pfldap.vim","4":"pfldap.vim","src_id":"17367","5":"17367","creation_date":"1328181444","6":"1328181444"}]},"3918":{"script_id":"3918","0":"3918","script_name":"cd-hook","1":"cd-hook","script_type":"utility","2":"utility","summary":"Provides a Cd command and associated autocmd calls","3":"Provides a Cd command and associated autocmd calls","description":"This very simple plugin implements a wrapper around chdir that allows you to\r\nbind arbitrary actions to it.\r\n\r\nYou call the new action with :Cd which completes the same way :chdir does.","4":"This very simple plugin implements a wrapper around chdir that allows you to\r\nbind arbitrary actions to it.\r\n\r\nYou call the new action with :Cd which completes the same way :chdir does.","install_details":"Simply install the plugin in plugin\/ and then bind actions with something like\r\n\r\nautocmd User chdir Rvm\r\n\r\n(If you use vim-rvm) and that command will be executed when you change\r\ndirectories. You can assign as many as you want!","5":"Simply install the plugin in plugin\/ and then bind actions with something like\r\n\r\nautocmd User chdir Rvm\r\n\r\n(If you use vim-rvm) and that command will be executed when you change\r\ndirectories. You can assign as many as you want!","first_name":"Rich","6":"Rich","last_name":"Healey","7":"Healey","releases":[{"0":"3918","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"cd-hook.tar.gz","4":"cd-hook.tar.gz","src_id":"17366","5":"17366","creation_date":"1328180860","6":"1328180860"}]},"3917":{"script_id":"3917","0":"3917","script_name":"tagport","1":"tagport","script_type":"ftplugin","2":"ftplugin","summary":"Find and yank Python import statement for keyword under cursor.","3":"Find and yank Python import statement for keyword under cursor.","description":"A simple script that finds the Python module using the keyword under the cursor and yank the import statement into the unnamed register \"\" so you can put it anywhere with the command 'p'.\r\n\r\n\r\nUsage\r\n=====\r\n\r\n1. Move cursor to a word you'd like to import.\r\n\r\n2. Type ``<Leader>fi``\r\n\r\n3. You'll be prompted with a list of import statements to yank into unnamed register ``'\"'``.\r\n\r\n4. Type a number.\r\n\r\n5. Put the import statement anywhere you like with ``p``.  *Tip: quickly jump back to last cursor position with `` (double backticks)*\r\n\r\n\r\nOptions\r\n=======\r\nlet g:tagport_aliases = {}\r\n    There are times when importing from a different package is preferred as apposed to the actual Python module the class is defined. \r\n    For example, Django's ``Model`` is declared in ``django.db.models.base``. However, it is a common practice that ``Model`` \r\n    is imported from ``django.db.models`` instead.\r\n\r\n    To do that, declare the following in ``.vimrc``::\r\n\r\n        let g:tagport_aliases = {'django.db.models.base': 'django.db.models'}\r\n\r\n    The next time you search for ``Model``, ``from django.db.models import Model`` is listed instead.\r\n\r\n\r\nlet g:tagport_ignore = []\r\n    ``models`` can be found in many places, but not all are useful. You can hide any entry with ``g:tagport_ignore``.\r\n    For example, if you want to hide all ``models`` from ``migrations`` directory, declare the following in ``.vimrc``::\r\n        \r\n        let g:tagport_ignore = ['.*migrations.*']\r\n\r\n\r\nLinks:\r\n  1. README - http:\/\/bit.ly\/xTL1qn\r\n  2. Screenshot - http:\/\/bit.ly\/zqOfsv","4":"A simple script that finds the Python module using the keyword under the cursor and yank the import statement into the unnamed register \"\" so you can put it anywhere with the command 'p'.\r\n\r\n\r\nUsage\r\n=====\r\n\r\n1. Move cursor to a word you'd like to import.\r\n\r\n2. Type ``<Leader>fi``\r\n\r\n3. You'll be prompted with a list of import statements to yank into unnamed register ``'\"'``.\r\n\r\n4. Type a number.\r\n\r\n5. Put the import statement anywhere you like with ``p``.  *Tip: quickly jump back to last cursor position with `` (double backticks)*\r\n\r\n\r\nOptions\r\n=======\r\nlet g:tagport_aliases = {}\r\n    There are times when importing from a different package is preferred as apposed to the actual Python module the class is defined. \r\n    For example, Django's ``Model`` is declared in ``django.db.models.base``. However, it is a common practice that ``Model`` \r\n    is imported from ``django.db.models`` instead.\r\n\r\n    To do that, declare the following in ``.vimrc``::\r\n\r\n        let g:tagport_aliases = {'django.db.models.base': 'django.db.models'}\r\n\r\n    The next time you search for ``Model``, ``from django.db.models import Model`` is listed instead.\r\n\r\n\r\nlet g:tagport_ignore = []\r\n    ``models`` can be found in many places, but not all are useful. You can hide any entry with ``g:tagport_ignore``.\r\n    For example, if you want to hide all ``models`` from ``migrations`` directory, declare the following in ``.vimrc``::\r\n        \r\n        let g:tagport_ignore = ['.*migrations.*']\r\n\r\n\r\nLinks:\r\n  1. README - http:\/\/bit.ly\/xTL1qn\r\n  2. Screenshot - http:\/\/bit.ly\/zqOfsv","install_details":"Place this script in $HOME\/.vim\/ftplugin\/python.","5":"Place this script in $HOME\/.vim\/ftplugin\/python.","first_name":"Phui-Hock","6":"Phui-Hock","last_name":"Chang","7":"Chang","releases":[{"0":"3917","vim_version":"7.0","1":"7.0","script_version":"0.2","2":"0.2","version_comment":"- Added aliases and ignore list support.\r\n- Bug fixes","3":"- Added aliases and ignore list support.\r\n- Bug fixes","package":"tagport.vim","4":"tagport.vim","src_id":"17376","5":"17376","creation_date":"1328257592","6":"1328257592"},{"0":"3917","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"tagport.vim","4":"tagport.vim","src_id":"17362","5":"17362","creation_date":"1328106996","6":"1328106996"}]},"3916":{"script_id":"3916","0":"3916","script_name":"vim-addon-haskell","1":"vim-addon-haskell","script_type":"utility","2":"utility","summary":"run cabal within vim using vim-addon-actions + some goodies","3":"run cabal within vim using vim-addon-actions + some goodies","description":"reconfigures cabal project, run cabal in background. Suggests import lines based on tag files and quickfix errors ...\r\n\r\nThis all is based on vim-addon-actions thus you can bind the \"recompile\" action to a key or to the if any buf was written action.\r\n\r\nThis plugin just does what I need.\r\nWant to run ghci in VIM? give SHIM or vim-addon-async a try.","4":"reconfigures cabal project, run cabal in background. Suggests import lines based on tag files and quickfix errors ...\r\n\r\nThis all is based on vim-addon-actions thus you can bind the \"recompile\" action to a key or to the if any buf was written action.\r\n\r\nThis plugin just does what I need.\r\nWant to run ghci in VIM? give SHIM or vim-addon-async a try.","install_details":"As always consider using a plugin manager such as vim-addon-manager, pathogen, vundle to get latest code from my github.com\/MarcWeber\/vim-addon-haskell\r\n\r\ndepends on vim-addon-actions (vim-addon-manager supports pulling dependencies)","5":"As always consider using a plugin manager such as vim-addon-manager, pathogen, vundle to get latest code from my github.com\/MarcWeber\/vim-addon-haskell\r\n\r\ndepends on vim-addon-actions (vim-addon-manager supports pulling dependencies)","first_name":"Marc","6":"Marc","last_name":"Weber","7":"Weber","releases":[{"0":"3916","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"vim-addon-haskell.zip","4":"vim-addon-haskell.zip","src_id":"17361","5":"17361","creation_date":"1328100197","6":"1328100197"}]},"3915":{"script_id":"3915","0":"3915","script_name":"CamelCaseComplete","1":"CamelCaseComplete","script_type":"utility","2":"utility","summary":"Insert mode completion that expands CamelCaseWords and underscore_words. ","3":"Insert mode completion that expands CamelCaseWords and underscore_words. ","description":"DESCRIPTION\r\nThis plugin offers a keyword completion that is limited to identifiers which\r\nadhere to either CamelCase (\"anIdentifier\") or underscore_notation\r\n(\"an_identifier\") naming conventions. This often results in a single (or very\r\nfew) matches and thus allows quick completion of function, class and variable\r\nnames.\r\nThe list of completion candidates can be restricted by triggering completion\r\non all or some of the initial letters of each word fragment; e.g. \"vlcn\" would\r\nexpand to \"veryLongClassName\" and \"verbose_latitude_correction_numeric\".\r\nNon-alphabetic keyword characters can be thrown in, too, to both widen the\r\nsearch to word fragments joined by the keywords (e.g. \"joined#words\") and to\r\nnarrow down the number of CamelCase and underscore_word matches.\r\n\r\nSEE ALSO\r\n- camelcasemotion (vimscript #1905) provides special motions ,w ,b and ,e\r\n  through CamelCaseWords and underscore_notation and corresponding text\r\n  objects.\r\n- Loosely based on and similar to the \"Custom keyword completion\" from\r\n  http:\/\/vim.wikia.com\/wiki\/Custom_keyword_completion\r\n- Check out the CompleteHelper.vim plugin page (vimscript #3914) for a full\r\n  list of insert mode completions powered by it.\r\n\r\nUSAGE\r\nIn insert mode, type some or all first letters of the desired CamelCaseWord or\r\nunderscore_word, then invoke the completion via CTRL-X CTRL-C.\r\nYou can then search forward and backward via CTRL-N \/ CTRL-P, as usual.\r\n\r\nCTRL-X CTRL-C           Find matches for CamelCaseWords and underscore_words\r\n                        whose individual word fragments begin with the typed\r\n                        letters in front of the cursor.","4":"DESCRIPTION\r\nThis plugin offers a keyword completion that is limited to identifiers which\r\nadhere to either CamelCase (\"anIdentifier\") or underscore_notation\r\n(\"an_identifier\") naming conventions. This often results in a single (or very\r\nfew) matches and thus allows quick completion of function, class and variable\r\nnames.\r\nThe list of completion candidates can be restricted by triggering completion\r\non all or some of the initial letters of each word fragment; e.g. \"vlcn\" would\r\nexpand to \"veryLongClassName\" and \"verbose_latitude_correction_numeric\".\r\nNon-alphabetic keyword characters can be thrown in, too, to both widen the\r\nsearch to word fragments joined by the keywords (e.g. \"joined#words\") and to\r\nnarrow down the number of CamelCase and underscore_word matches.\r\n\r\nSEE ALSO\r\n- camelcasemotion (vimscript #1905) provides special motions ,w ,b and ,e\r\n  through CamelCaseWords and underscore_notation and corresponding text\r\n  objects.\r\n- Loosely based on and similar to the \"Custom keyword completion\" from\r\n  http:\/\/vim.wikia.com\/wiki\/Custom_keyword_completion\r\n- Check out the CompleteHelper.vim plugin page (vimscript #3914) for a full\r\n  list of insert mode completions powered by it.\r\n\r\nUSAGE\r\nIn insert mode, type some or all first letters of the desired CamelCaseWord or\r\nunderscore_word, then invoke the completion via CTRL-X CTRL-C.\r\nYou can then search forward and backward via CTRL-N \/ CTRL-P, as usual.\r\n\r\nCTRL-X CTRL-C           Find matches for CamelCaseWords and underscore_words\r\n                        whose individual word fragments begin with the typed\r\n                        letters in front of the cursor.","install_details":"INSTALLATION\r\nThis script is packaged as a vimball. If you have the \"gunzip\" decompressor\r\nin your PATH, simply edit the *.vmb.gz package in Vim; otherwise, decompress\r\nthe archive first, e.g. using WinZip. Inside Vim, install by sourcing the\r\nvimball or via the :UseVimball command.\r\n    vim CamelCaseComplete*.vmb.gz\r\n    :so %\r\nTo uninstall, use the :RmVimball command.\r\n\r\nDEPENDENCIES\r\n- Requires Vim 7.1 or higher.\r\n- Requires the ingo-library.vim plugin (vimscript #4433), version 1.010 or\r\n  higher.\r\n- Requires the CompleteHelper.vim plugin (vimscript #3914).\r\n\r\nCONFIGURATION\r\nFor a permanent configuration, put the following commands into your vimrc:\r\n\r\nBy default, the 'complete' option controls which buffers will be scanned for\r\ncompletion candidates. You can override that either for the entire plugin, or\r\nonly for particular buffers; see CompleteHelper_complete for supported\r\nvalues.\r\n    let g:CamelCaseComplete_complete = '.,w,b,u'\r\n\r\nTo disable the removal of the (mostly useless) completion base when there\r\nare no matches:\r\n    let g:CamelCaseComplete_FindStartMark = ''\r\n\r\nYou can disable the fallback to a case-insensitive search when the completion\r\nbase only contains lowercase letters. Then, (together with 'noignorecase'),\r\nthe case of the first CamelWord fragment and all underscore_word fragments\r\nmust always match exactly:\r\n    let g:CamelCaseComplete_CaseInsensitiveFallback = 0\r\n\r\nIf you want to use a different mapping, map your keys to the\r\n<Plug>(CamelCaseComplete) mapping target _before_ sourcing the script (e.g.\r\nin your vimrc):\r\n    imap <C-x><C-c> <Plug>(CamelCaseComplete)<Plug>(CamelCasePostComplete)","5":"INSTALLATION\r\nThis script is packaged as a vimball. If you have the \"gunzip\" decompressor\r\nin your PATH, simply edit the *.vmb.gz package in Vim; otherwise, decompress\r\nthe archive first, e.g. using WinZip. Inside Vim, install by sourcing the\r\nvimball or via the :UseVimball command.\r\n    vim CamelCaseComplete*.vmb.gz\r\n    :so %\r\nTo uninstall, use the :RmVimball command.\r\n\r\nDEPENDENCIES\r\n- Requires Vim 7.1 or higher.\r\n- Requires the ingo-library.vim plugin (vimscript #4433), version 1.010 or\r\n  higher.\r\n- Requires the CompleteHelper.vim plugin (vimscript #3914).\r\n\r\nCONFIGURATION\r\nFor a permanent configuration, put the following commands into your vimrc:\r\n\r\nBy default, the 'complete' option controls which buffers will be scanned for\r\ncompletion candidates. You can override that either for the entire plugin, or\r\nonly for particular buffers; see CompleteHelper_complete for supported\r\nvalues.\r\n    let g:CamelCaseComplete_complete = '.,w,b,u'\r\n\r\nTo disable the removal of the (mostly useless) completion base when there\r\nare no matches:\r\n    let g:CamelCaseComplete_FindStartMark = ''\r\n\r\nYou can disable the fallback to a case-insensitive search when the completion\r\nbase only contains lowercase letters. Then, (together with 'noignorecase'),\r\nthe case of the first CamelWord fragment and all underscore_word fragments\r\nmust always match exactly:\r\n    let g:CamelCaseComplete_CaseInsensitiveFallback = 0\r\n\r\nIf you want to use a different mapping, map your keys to the\r\n<Plug>(CamelCaseComplete) mapping target _before_ sourcing the script (e.g.\r\nin your vimrc):\r\n    imap <C-x><C-c> <Plug>(CamelCaseComplete)<Plug>(CamelCasePostComplete)","first_name":"Ingo","6":"Ingo","last_name":"Karkat","7":"Karkat","releases":[{"0":"3915","vim_version":"7.0","1":"7.0","script_version":"1.02","2":"1.02","version_comment":"- Need special case for given underscore anchor (e.g. in \"f_br\" base); then, the assertion for alphabetic anchors (here: \"b\") must _not_ assert that there's no underscore before it.\r\n- Remove default g:CamelCaseComplete_complete configuration and default to 'complete' option value instead.","3":"- Need special case for given underscore anchor (e.g. in \"f_br\" base); then, the assertion for alphabetic anchors (here: \"b\") must _not_ assert that there's no underscore before it.\r\n- Remove default g:CamelCaseComplete_complete configuration and default to 'complete' option value instead.","package":"CamelCaseComplete-1.02.vmb.gz","4":"CamelCaseComplete-1.02.vmb.gz","src_id":"23212","5":"23212","creation_date":"1429788652","6":"1429788652"},{"0":"3915","vim_version":"7.0","1":"7.0","script_version":"1.01","2":"1.01","version_comment":"- Factor out CamelCaseComplete#BuildRegexp() for re-use by the new InnerFragmentComplete.vim plugin.\r\n- Add value \"b\" (other listed buffers) to the plugin's 'complete' option offered by CompleteHelper.vim 1.20.","3":"- Factor out CamelCaseComplete#BuildRegexp() for re-use by the new InnerFragmentComplete.vim plugin.\r\n- Add value \"b\" (other listed buffers) to the plugin's 'complete' option offered by CompleteHelper.vim 1.20.","package":"CamelCaseComplete-1.01.vmb.gz","4":"CamelCaseComplete-1.01.vmb.gz","src_id":"21213","5":"21213","creation_date":"1387438642","6":"1387438642"},{"0":"3915","vim_version":"7.0","1":"7.0","script_version":"1.00","2":"1.00","version_comment":"Initial upload","3":"Initial upload","package":"CamelCaseComplete.vba.gz","4":"CamelCaseComplete.vba.gz","src_id":"17359","5":"17359","creation_date":"1328087838","6":"1328087838"}]},"3914":{"script_id":"3914","0":"3914","script_name":"CompleteHelper","1":"CompleteHelper","script_type":"utility","2":"utility","summary":"Generic functions to support custom insert mode completions. ","3":"Generic functions to support custom insert mode completions. ","description":"DESCRIPTION\r\nVia 'completefunc' and the i_CTRL-X_CTRL-U command, it is possible to define\r\ncustom complete-functions. To write extensions or alternatives to the\r\nbuilt-in completion functions, you often need to derive the completion\r\ncandidates from Vim's buffers and windows. This plugin offers generic\r\nfunctions around extraction and handling of completion matches (something that\r\nVim doesn't yet expose to Vimscript), so that building your own custom\r\ncompletion is quick and simple.\r\n\r\nSEE ALSO\r\nThe following custom completions use this plugin:\r\n\r\n- AlphaComplete.vim (vimscript #4912):\r\n  Completes any sequence of alphabetic characters.\r\n- BidiComplete.vim (vimscript #4658):\r\n  Considers text before AND AFTER the cursor.\r\n- CamelCaseComplete.vim (vimscript #3915):\r\n  Expands CamelCaseWords and underscore_words based on anchor characters for\r\n  each word fragment.\r\n- EntryComplete.vim (vimscript #5073):\r\n  Completes whole lines from designated files or buffers.\r\n- InnerFragmentComplete.vim (vimscript #4804):\r\n  Completes (and expands CamelCaseWord) fragments inside words.\r\n- LineComplete.vim (vimscript #4911):\r\n  Completes entire lines with looser matching that the built-in\r\n  i_CTRL-X_CTRL-L.\r\n- MotionComplete.vim (vimscript #4265):\r\n  Completes a chunk covered by queried {motion} or text object.\r\n  - BracketComplete.vim (vimscript #4266):\r\n    Completes text inside various brackets.\r\n  - LineEndComplete.vim (vimscript #4267):\r\n    Completes the rest of the line.\r\n- MultiWordComplete.vim (vimscript #4805):\r\n  Completes a sequence of words based on anchor characters for each word.\r\n- PatternComplete.vim (vimscript #4248):\r\n  Completes matches of queried {pattern} or last search pattern.\r\n- PrevInsertComplete.vim (vimscript #4185):\r\n  Recall and insert mode completion for previously inserted text.\r\n- SameFiletypeComplete.vim (vimscript #4242):\r\n  Completion from buffers with the same filetype.\r\n- SnippetComplete.vim (vimscript #2926):\r\n  Completes defined abbreviations and other snippets.\r\n- SpecialLocationComplete.vim (vimscript #5120):\r\n  Completes special, configurable custom patterns.\r\n- WORDComplete.vim (vimscript #5613):\r\n  Completes an entire sequence of non-blank characters.\r\n\r\nRELATED WORKS\r\n- Mark Weber's vim-addon-completion library\r\n  (https:\/\/github.com\/MarcWeber\/vim-addon-completion) has some functions to\r\n  switch between completions and to do CamelCase matching.\r\n\r\nUSAGE\r\nThe options.complete attribute specifies what is searched, like the 'complete'\r\noption for built-in completions. The following (comma-separated) option values\r\nare currently supported:\r\n    - \".\" current buffer\r\n    - \"w\" buffers from other windows\r\n    - \"b\" other loaded buffers that are in the buffer list\r\n    - \"u\" unloaded buffers that are in the buffer list\r\n    - \"U\" buffers that are not in the buffer list\r\n\r\nThis plugin defines several functions. The following is an overview; you'll\r\nfind the details directly in the implementation files in the .vim\/autoload\/\r\ndirectory.\r\n\r\nCompleteHelper#FindMatches( matches, pattern, options )\r\n\r\nThe main helper function that finds all matches of a:pattern in buffers\r\nspecified by a:options, and returns them in the List a:matches that can be\r\nreturned as-is to Vim.\r\n\r\nCompleteHelper#Find( matches, Funcref, options )\r\n\r\nA generic alternative that doesn't prescribe using a regular expression match.\r\nInstead, a Funcref is passed to find and extract matches, reusing the window\r\nand buffer iteration functionality provided by this plugin.\r\n\r\nCompleteHelper#ExtractText( startPos, endPos, matchObj )\r\n\r\nLow-level function for extracting text from the current buffer. This is the\r\ndefault extractor used by CompleteHelper#FindMatches().\r\n\r\nCompleteHelper#Abbreviate#Word( matchObj )\r\n\r\nProcesses the match objects to make them prettier to display. Usually\r\n|map()|ed over the matches returned from CompleteHelper#FindMatches().\r\n\r\nCompleteHelper#JoinMultiline( text )\r\n\r\nCan be used in CompleteHelper#FindMatches()'s a:options.processor if you want\r\nto flatten multi-line matches, as the current default behavior of Vim is not\r\nwhat users expect. (Newlines are inserted literally as ^@.)\r\n\r\nCompleteHelper#Repeat#TestForRepeat()\r\n\r\nSome built-in completions support the repetition of a completion, so that\r\nsubsequent words from the completion source are appended. This function allows\r\nto implement such a repetition for custom completions, too.\r\n\r\nDEBUGGING\r\nTo help you with developing your own plugins, you can make the plugin save the\r\nlast used pattern(s) in a global variable, if it is defined:\r\n    :let g:CompleteHelper_DebugPatterns = []\r\n    \" Trigger custom completion.\r\n    :echo g:CompleteHelper_DebugPatterns\r\n\r\nEXAMPLE\r\nHere is a simple completion that completes the keywords in front of the cursor\r\nfrom the current file, like the built-in compl-current does. From the\r\ncompletion base, it constructs a regexp matching all keywords that start with\r\nthe base, and delegates the entire work of finding the matches and building\r\nthe appropriate match objects to CompleteHelper#FindMatches().\r\n>\r\n    function! SimpleComplete( findstart, base )\r\n        if a:findstart\r\n            \" Locate the start of the keyword.\r\n            let l:startCol = searchpos('\\k*\\%#', 'bn', line('.'))[1]\r\n            if l:startCol == 0\r\n                let l:startCol = col('.')\r\n            endif\r\n            return l:startCol - 1 \" Return byte index, not column.\r\n        else\r\n            \" Find matches starting with a:base.\r\n            let l:matches = []\r\n            call CompleteHelper#FindMatches( l:matches, '\\V\\<' . escape(a:base, '\\') . '\\k\\+', {'complete': '.'} )\r\n            return l:matches\r\n        endif\r\n    endfunction\r\n\r\n    inoremap <C-x><C-z> <C-o>:set completefunc=SimpleComplete<CR><C-x><C-u>","4":"DESCRIPTION\r\nVia 'completefunc' and the i_CTRL-X_CTRL-U command, it is possible to define\r\ncustom complete-functions. To write extensions or alternatives to the\r\nbuilt-in completion functions, you often need to derive the completion\r\ncandidates from Vim's buffers and windows. This plugin offers generic\r\nfunctions around extraction and handling of completion matches (something that\r\nVim doesn't yet expose to Vimscript), so that building your own custom\r\ncompletion is quick and simple.\r\n\r\nSEE ALSO\r\nThe following custom completions use this plugin:\r\n\r\n- AlphaComplete.vim (vimscript #4912):\r\n  Completes any sequence of alphabetic characters.\r\n- BidiComplete.vim (vimscript #4658):\r\n  Considers text before AND AFTER the cursor.\r\n- CamelCaseComplete.vim (vimscript #3915):\r\n  Expands CamelCaseWords and underscore_words based on anchor characters for\r\n  each word fragment.\r\n- EntryComplete.vim (vimscript #5073):\r\n  Completes whole lines from designated files or buffers.\r\n- InnerFragmentComplete.vim (vimscript #4804):\r\n  Completes (and expands CamelCaseWord) fragments inside words.\r\n- LineComplete.vim (vimscript #4911):\r\n  Completes entire lines with looser matching that the built-in\r\n  i_CTRL-X_CTRL-L.\r\n- MotionComplete.vim (vimscript #4265):\r\n  Completes a chunk covered by queried {motion} or text object.\r\n  - BracketComplete.vim (vimscript #4266):\r\n    Completes text inside various brackets.\r\n  - LineEndComplete.vim (vimscript #4267):\r\n    Completes the rest of the line.\r\n- MultiWordComplete.vim (vimscript #4805):\r\n  Completes a sequence of words based on anchor characters for each word.\r\n- PatternComplete.vim (vimscript #4248):\r\n  Completes matches of queried {pattern} or last search pattern.\r\n- PrevInsertComplete.vim (vimscript #4185):\r\n  Recall and insert mode completion for previously inserted text.\r\n- SameFiletypeComplete.vim (vimscript #4242):\r\n  Completion from buffers with the same filetype.\r\n- SnippetComplete.vim (vimscript #2926):\r\n  Completes defined abbreviations and other snippets.\r\n- SpecialLocationComplete.vim (vimscript #5120):\r\n  Completes special, configurable custom patterns.\r\n- WORDComplete.vim (vimscript #5613):\r\n  Completes an entire sequence of non-blank characters.\r\n\r\nRELATED WORKS\r\n- Mark Weber's vim-addon-completion library\r\n  (https:\/\/github.com\/MarcWeber\/vim-addon-completion) has some functions to\r\n  switch between completions and to do CamelCase matching.\r\n\r\nUSAGE\r\nThe options.complete attribute specifies what is searched, like the 'complete'\r\noption for built-in completions. The following (comma-separated) option values\r\nare currently supported:\r\n    - \".\" current buffer\r\n    - \"w\" buffers from other windows\r\n    - \"b\" other loaded buffers that are in the buffer list\r\n    - \"u\" unloaded buffers that are in the buffer list\r\n    - \"U\" buffers that are not in the buffer list\r\n\r\nThis plugin defines several functions. The following is an overview; you'll\r\nfind the details directly in the implementation files in the .vim\/autoload\/\r\ndirectory.\r\n\r\nCompleteHelper#FindMatches( matches, pattern, options )\r\n\r\nThe main helper function that finds all matches of a:pattern in buffers\r\nspecified by a:options, and returns them in the List a:matches that can be\r\nreturned as-is to Vim.\r\n\r\nCompleteHelper#Find( matches, Funcref, options )\r\n\r\nA generic alternative that doesn't prescribe using a regular expression match.\r\nInstead, a Funcref is passed to find and extract matches, reusing the window\r\nand buffer iteration functionality provided by this plugin.\r\n\r\nCompleteHelper#ExtractText( startPos, endPos, matchObj )\r\n\r\nLow-level function for extracting text from the current buffer. This is the\r\ndefault extractor used by CompleteHelper#FindMatches().\r\n\r\nCompleteHelper#Abbreviate#Word( matchObj )\r\n\r\nProcesses the match objects to make them prettier to display. Usually\r\n|map()|ed over the matches returned from CompleteHelper#FindMatches().\r\n\r\nCompleteHelper#JoinMultiline( text )\r\n\r\nCan be used in CompleteHelper#FindMatches()'s a:options.processor if you want\r\nto flatten multi-line matches, as the current default behavior of Vim is not\r\nwhat users expect. (Newlines are inserted literally as ^@.)\r\n\r\nCompleteHelper#Repeat#TestForRepeat()\r\n\r\nSome built-in completions support the repetition of a completion, so that\r\nsubsequent words from the completion source are appended. This function allows\r\nto implement such a repetition for custom completions, too.\r\n\r\nDEBUGGING\r\nTo help you with developing your own plugins, you can make the plugin save the\r\nlast used pattern(s) in a global variable, if it is defined:\r\n    :let g:CompleteHelper_DebugPatterns = []\r\n    \" Trigger custom completion.\r\n    :echo g:CompleteHelper_DebugPatterns\r\n\r\nEXAMPLE\r\nHere is a simple completion that completes the keywords in front of the cursor\r\nfrom the current file, like the built-in compl-current does. From the\r\ncompletion base, it constructs a regexp matching all keywords that start with\r\nthe base, and delegates the entire work of finding the matches and building\r\nthe appropriate match objects to CompleteHelper#FindMatches().\r\n>\r\n    function! SimpleComplete( findstart, base )\r\n        if a:findstart\r\n            \" Locate the start of the keyword.\r\n            let l:startCol = searchpos('\\k*\\%#', 'bn', line('.'))[1]\r\n            if l:startCol == 0\r\n                let l:startCol = col('.')\r\n            endif\r\n            return l:startCol - 1 \" Return byte index, not column.\r\n        else\r\n            \" Find matches starting with a:base.\r\n            let l:matches = []\r\n            call CompleteHelper#FindMatches( l:matches, '\\V\\<' . escape(a:base, '\\') . '\\k\\+', {'complete': '.'} )\r\n            return l:matches\r\n        endif\r\n    endfunction\r\n\r\n    inoremap <C-x><C-z> <C-o>:set completefunc=SimpleComplete<CR><C-x><C-u>","install_details":"INSTALLATION\r\nThe code is hosted in a Git repo at\r\n    https:\/\/github.com\/inkarkat\/vim-CompleteHelper\r\nYou can use your favorite plugin manager, or \"git clone\" into a directory used\r\nfor Vim packages. Releases are on the \"stable\" branch, the latest unstable\r\ndevelopment snapshot on \"master\".\r\n\r\nThis script is also packaged as a vimball. If you have the \"gunzip\"\r\ndecompressor in your PATH, simply edit the *.vmb.gz package in Vim; otherwise,\r\ndecompress the archive first, e.g. using WinZip. Inside Vim, install by\r\nsourcing the vimball or via the :UseVimball command.\r\n    vim CompleteHelper*.vmb.gz\r\n    :so %\r\nTo uninstall, use the :RmVimball command.\r\n\r\nDEPENDENCIES\r\n- Requires Vim 7.0 or higher.\r\n- Requires the ingo-library.vim plugin (vimscript #4433), version 1.028 or\r\n  higher.\r\n\r\nCONFIGURATION\r\nFor a permanent configuration, put the following commands into your vimrc:\r\n\r\nWhen no a:options.backward_search is passed to CompleteHelper#FindMatches(),\r\nit defaults to backwards search, as this offers recent \/ preceding matches\r\n(which are likier to be recalled) first. If you don't want that, either\r\nexplicitly pass the a:options.backward_search flag (especially do this if you\r\noffer both backward and forward matching mappings), or globally revert to the\r\nprevious behavior via:\r\n    let g:CompleteHelper_IsDefaultToBackwardSearch = 0","5":"INSTALLATION\r\nThe code is hosted in a Git repo at\r\n    https:\/\/github.com\/inkarkat\/vim-CompleteHelper\r\nYou can use your favorite plugin manager, or \"git clone\" into a directory used\r\nfor Vim packages. Releases are on the \"stable\" branch, the latest unstable\r\ndevelopment snapshot on \"master\".\r\n\r\nThis script is also packaged as a vimball. If you have the \"gunzip\"\r\ndecompressor in your PATH, simply edit the *.vmb.gz package in Vim; otherwise,\r\ndecompress the archive first, e.g. using WinZip. Inside Vim, install by\r\nsourcing the vimball or via the :UseVimball command.\r\n    vim CompleteHelper*.vmb.gz\r\n    :so %\r\nTo uninstall, use the :RmVimball command.\r\n\r\nDEPENDENCIES\r\n- Requires Vim 7.0 or higher.\r\n- Requires the ingo-library.vim plugin (vimscript #4433), version 1.028 or\r\n  higher.\r\n\r\nCONFIGURATION\r\nFor a permanent configuration, put the following commands into your vimrc:\r\n\r\nWhen no a:options.backward_search is passed to CompleteHelper#FindMatches(),\r\nit defaults to backwards search, as this offers recent \/ preceding matches\r\n(which are likier to be recalled) first. If you don't want that, either\r\nexplicitly pass the a:options.backward_search flag (especially do this if you\r\noffer both backward and forward matching mappings), or globally revert to the\r\nprevious behavior via:\r\n    let g:CompleteHelper_IsDefaultToBackwardSearch = 0","first_name":"Ingo","6":"Ingo","last_name":"Karkat","7":"Karkat","releases":[{"0":"3914","vim_version":"7.0","1":"7.0","script_version":"1.52","2":"1.52","version_comment":"- Need to restore entire view, not just the cursor position when matching in the current window. Else, a completion may change the current view.\r\n- CompleteHelper#Abbreviate#Word(): Only offer the full word in the preview window if a:matchObj.info hasn't been set yet.\r\n- Use ingo#compat#window#IsCmdlineWindow(). *** You need to update to ingo-library (vimscript #4433) version 1.028! ***","3":"- Need to restore entire view, not just the cursor position when matching in the current window. Else, a completion may change the current view.\r\n- CompleteHelper#Abbreviate#Word(): Only offer the full word in the preview window if a:matchObj.info hasn't been set yet.\r\n- Use ingo#compat#window#IsCmdlineWindow(). *** You need to update to ingo-library (vimscript #4433) version 1.028! ***","package":"CompleteHelper-1.52.vmb.gz","4":"CompleteHelper-1.52.vmb.gz","src_id":"25590","5":"25590","creation_date":"1506612570","6":"1506612570"},{"0":"3914","vim_version":"7.0","1":"7.0","script_version":"1.51","2":"1.51","version_comment":"- Backwards compatibility: haslocaldir() doesn't exist in Vim 7.0.\r\n- FIX: Duplicate matches when the additional match info is different. Only CompleteHelper#AddMatch() when the same a:match.word doesn't yet exist in a:matches; a test for existence of the same a:match object isn't sufficient due to the other attributes.\r\n- Don't consider the current buffer when a:options.complete does not contain \".\"; some completions may want to explicitly exclude the current buffer.\r\n- CHG: Exclude unloaded buffers from a:options.complete = \"b\" and introduce \"u\" option value for those.\r\n- Add \"U\" option value for unlisted (loaded and unloaded) buffers, like in the built-in 'complete' option.\r\n- DWIM: Check for a:options.extractor and then skip incompatible a:options.complete values. This allows MotionComplete.vim plugins to default to 'complete' values and prevents user misconfiguration.\r\n- FIX: Also consider buffers from windows visible in other tab pages (by collecting their buffer numbers, not by actually visiting each tab page). This matters when a:options.complete does not contain \"b\" (or \"u\" when unlisted buffers are shown in a window).\r\n- ENH: Keep previous (last accessed) window when searching through them for matches.","3":"- Backwards compatibility: haslocaldir() doesn't exist in Vim 7.0.\r\n- FIX: Duplicate matches when the additional match info is different. Only CompleteHelper#AddMatch() when the same a:match.word doesn't yet exist in a:matches; a test for existence of the same a:match object isn't sufficient due to the other attributes.\r\n- Don't consider the current buffer when a:options.complete does not contain \".\"; some completions may want to explicitly exclude the current buffer.\r\n- CHG: Exclude unloaded buffers from a:options.complete = \"b\" and introduce \"u\" option value for those.\r\n- Add \"U\" option value for unlisted (loaded and unloaded) buffers, like in the built-in 'complete' option.\r\n- DWIM: Check for a:options.extractor and then skip incompatible a:options.complete values. This allows MotionComplete.vim plugins to default to 'complete' values and prevents user misconfiguration.\r\n- FIX: Also consider buffers from windows visible in other tab pages (by collecting their buffer numbers, not by actually visiting each tab page). This matters when a:options.complete does not contain \"b\" (or \"u\" when unlisted buffers are shown in a window).\r\n- ENH: Keep previous (last accessed) window when searching through them for matches.","package":"CompleteHelper-1.51.vmb.gz","4":"CompleteHelper-1.51.vmb.gz","src_id":"23214","5":"23214","creation_date":"1429789005","6":"1429789005"},{"0":"3914","vim_version":"7.0","1":"7.0","script_version":"1.50","2":"1.50","version_comment":"- Split the match extraction via pattern match from the window \/ buffer iteration, which now takes a generic Funcref, allowing for other algorithms: Remove ...Matches... from the s:FindMatchesIn...() functions. Extract s:MatchInCurrent() and s:MatchInBuffer(). Add CompleteHelper#Find() generic alternative to CompleteHelper#FindMatches() that takes a Funcref instead of a regular expression.\r\n- Expose CompleteHelper#AddMatch().\r\n- ENH: Add a:options.abbreviate and evaluate in CompleteHelper#AddMatch(). This saves completion plugins from doing an additional map() over the List of matches.","3":"- Split the match extraction via pattern match from the window \/ buffer iteration, which now takes a generic Funcref, allowing for other algorithms: Remove ...Matches... from the s:FindMatchesIn...() functions. Extract s:MatchInCurrent() and s:MatchInBuffer(). Add CompleteHelper#Find() generic alternative to CompleteHelper#FindMatches() that takes a Funcref instead of a regular expression.\r\n- Expose CompleteHelper#AddMatch().\r\n- ENH: Add a:options.abbreviate and evaluate in CompleteHelper#AddMatch(). This saves completion plugins from doing an additional map() over the List of matches.","package":"CompleteHelper-1.50.vmb.gz","4":"CompleteHelper-1.50.vmb.gz","src_id":"22724","5":"22724","creation_date":"1419333987","6":"1419333987"},{"0":"3914","vim_version":"7.0","1":"7.0","script_version":"1.42","2":"1.42","version_comment":"- getbufline() can only access loaded buffers, for completion from unloaded buffers, we need to use readfile().","3":"- getbufline() can only access loaded buffers, for completion from unloaded buffers, we need to use readfile().","package":"CompleteHelper-1.42.vmb.gz","4":"CompleteHelper-1.42.vmb.gz","src_id":"22655","5":"22655","creation_date":"1417160584","6":"1417160584"},{"0":"3914","vim_version":"7.0","1":"7.0","script_version":"1.41","2":"1.41","version_comment":"- FIX: In the completion buffer, check for the cursor position being anywhere in the match, not just at the end. We must not only avoid matching the base, but any text around the cursor. This is especially important for completion repeats, to avoid offering text after the cursor. *** You need to update to ingo-library (vimscript #4433) version 1.019! ***","3":"- FIX: In the completion buffer, check for the cursor position being anywhere in the match, not just at the end. We must not only avoid matching the base, but any text around the cursor. This is especially important for completion repeats, to avoid offering text after the cursor. *** You need to update to ingo-library (vimscript #4433) version 1.019! ***","package":"CompleteHelper-1.41.vmb.gz","4":"CompleteHelper-1.41.vmb.gz","src_id":"21968","5":"21968","creation_date":"1401561778","6":"1401561778"},{"0":"3914","vim_version":"7.0","1":"7.0","script_version":"1.40","2":"1.40","version_comment":"- Remove the duplicated implementation in CompleteHelper#ExtractText(), deprecate it, and delegate to ingo#text#Get().\r\n- FIX: a:options.backward_search with falsy value also enables backward search.\r\n- Add g:CompleteHelper_IsDefaultToBackwardSearch config var that lets CompleteHelper#FindMatches() default to backwards search when no a:options.backward_search is given. Since all of my custom completions don't offer separate backward \/ forward mappings, and backward search (i.e. offering first what got recently typed) makes more sense, default to backward search from now on.\r\n- Allow to debug the pattern via :let g:CompleteHelper_DebugPatterns = [].\r\n- Allow completion repeats to continue repeating from following lines like the built-in completions do: The newline plus any indent is removed, and just the first word from the following line is matched. For this, the CompleteHelper#Repeat#Processor() is offered.\r\n- I18N: Correctly handle repeats of (text ending with a) multi-byte character: Instead of just subtracting one from the column, ask for an end-exclusive text grab from ingo#text#Get().\r\n- Add CompleteHelper#Repeat#GetPattern() to encapsulate the common assembly of the repeat pattern, especially the complex expressions with negative and positive character expressions to emulate Vim's built-in completion repeat behavior. *** You need to update to ingo-library (vimscript #4433) version 1.018! ***","3":"- Remove the duplicated implementation in CompleteHelper#ExtractText(), deprecate it, and delegate to ingo#text#Get().\r\n- FIX: a:options.backward_search with falsy value also enables backward search.\r\n- Add g:CompleteHelper_IsDefaultToBackwardSearch config var that lets CompleteHelper#FindMatches() default to backwards search when no a:options.backward_search is given. Since all of my custom completions don't offer separate backward \/ forward mappings, and backward search (i.e. offering first what got recently typed) makes more sense, default to backward search from now on.\r\n- Allow to debug the pattern via :let g:CompleteHelper_DebugPatterns = [].\r\n- Allow completion repeats to continue repeating from following lines like the built-in completions do: The newline plus any indent is removed, and just the first word from the following line is matched. For this, the CompleteHelper#Repeat#Processor() is offered.\r\n- I18N: Correctly handle repeats of (text ending with a) multi-byte character: Instead of just subtracting one from the column, ask for an end-exclusive text grab from ingo#text#Get().\r\n- Add CompleteHelper#Repeat#GetPattern() to encapsulate the common assembly of the repeat pattern, especially the complex expressions with negative and positive character expressions to emulate Vim's built-in completion repeat behavior. *** You need to update to ingo-library (vimscript #4433) version 1.018! ***","package":"CompleteHelper-1.40.vmb.gz","4":"CompleteHelper-1.40.vmb.gz","src_id":"21782","5":"21782","creation_date":"1397651558","6":"1397651558"},{"0":"3914","vim_version":"7.0","1":"7.0","script_version":"1.32","2":"1.32","version_comment":"- ENH: Allow to pass a List of regular expressions to CompleteHelper#FindMatches(). If you have multiple regular expressions that can match at the same position and should yield separate matches, you cannot use regular expression branches.\r\n- Add dependency to ingo-library (vimscript #4433). *** You need to separately install ingo-library (vimscript #4433) version 1.014 (or higher)! ***","3":"- ENH: Allow to pass a List of regular expressions to CompleteHelper#FindMatches(). If you have multiple regular expressions that can match at the same position and should yield separate matches, you cannot use regular expression branches.\r\n- Add dependency to ingo-library (vimscript #4433). *** You need to separately install ingo-library (vimscript #4433) version 1.014 (or higher)! ***","package":"CompleteHelper-1.32.vmb.gz","4":"CompleteHelper-1.32.vmb.gz","src_id":"21193","5":"21193","creation_date":"1387050974","6":"1387050974"},{"0":"3914","vim_version":"7.0","1":"7.0","script_version":"1.31","2":"1.31","version_comment":"- Truncate to a bit less than half of Vim's width because the popup menu spacing as well as fold, number and sign columns further reduce the available space.\r\n- Avoid \"E11: Invalid in command-line window\" error when performing completions that search other windows from the command-line window. Use the buffer-search instead; it does not need to change the current window for its search.\r\n- FIX: Don't abort iteration of buffers in s:FindMatchesInOtherBuffers() when one buffer was already searched; instead :continue with the next.","3":"- Truncate to a bit less than half of Vim's width because the popup menu spacing as well as fold, number and sign columns further reduce the available space.\r\n- Avoid \"E11: Invalid in command-line window\" error when performing completions that search other windows from the command-line window. Use the buffer-search instead; it does not need to change the current window for its search.\r\n- FIX: Don't abort iteration of buffers in s:FindMatchesInOtherBuffers() when one buffer was already searched; instead :continue with the next.","package":"CompleteHelper-1.31.vmb.gz","4":"CompleteHelper-1.31.vmb.gz","src_id":"19603","5":"19603","creation_date":"1362659052","6":"1362659052"},{"0":"3914","vim_version":"7.0","1":"7.0","script_version":"1.30","2":"1.30","version_comment":"- ENH: Allow skipping of buffers via new a:options.bufferPredicate Funcref.\r\n- Optimization: Skip search in other windows where there's only one that got searched already by s:FindMatchesInCurrentWindow().\r\n- Optimization: Only visit window when its buffer wasn't already searched.\r\n- ENH: Implement a:options.complete = 'b' (only supporting single-line matches and no a:options.extractor).\r\n- Transparently handle 'autochdir': still show the correct relative path in matches from other windows, and restore the buffer's CWD even if it was temporarily changed.","3":"- ENH: Allow skipping of buffers via new a:options.bufferPredicate Funcref.\r\n- Optimization: Skip search in other windows where there's only one that got searched already by s:FindMatchesInCurrentWindow().\r\n- Optimization: Only visit window when its buffer wasn't already searched.\r\n- ENH: Implement a:options.complete = 'b' (only supporting single-line matches and no a:options.extractor).\r\n- Transparently handle 'autochdir': still show the correct relative path in matches from other windows, and restore the buffer's CWD even if it was temporarily changed.","package":"CompleteHelper-1.30.vmb.gz","4":"CompleteHelper-1.30.vmb.gz","src_id":"18703","5":"18703","creation_date":"1348754907","6":"1348754907"},{"0":"3914","vim_version":"7.0","1":"7.0","script_version":"1.11","2":"1.11","version_comment":"- Make a:matchObj in CompleteHelper#ExtractText() optional; it's not used there, anyway. This avoids having to pass an empty dictionary just to satisfy the API.\r\n- Introduce a:alreadySearchedBuffers to allow for swapped order in a:options.complete and to prepare for additional complete options.\r\n\r\n","3":"- Make a:matchObj in CompleteHelper#ExtractText() optional; it's not used there, anyway. This avoids having to pass an empty dictionary just to satisfy the API.\r\n- Introduce a:alreadySearchedBuffers to allow for swapped order in a:options.complete and to prepare for additional complete options.\r\n\r\n","package":"CompleteHelper-1.11.vmb.gz","4":"CompleteHelper-1.11.vmb.gz","src_id":"18538","5":"18538","creation_date":"1346676078","6":"1346676078"},{"0":"3914","vim_version":"7.0","1":"7.0","script_version":"1.10","2":"1.10","version_comment":"- Factor out CompleteHelper#Abbreviate#Text() to allow processing of completion menu text (and other uses), too.\r\n- ENH: Offer full completion word in the preview window when it is shown abbreviated. Clients get this automatically when using CompleteHelper#Abbreviate#Word().","3":"- Factor out CompleteHelper#Abbreviate#Text() to allow processing of completion menu text (and other uses), too.\r\n- ENH: Offer full completion word in the preview window when it is shown abbreviated. Clients get this automatically when using CompleteHelper#Abbreviate#Word().","package":"CompleteHelper.vba.gz","4":"CompleteHelper.vba.gz","src_id":"17873","5":"17873","creation_date":"1336246238","6":"1336246238"},{"0":"3914","vim_version":"7.0","1":"7.0","script_version":"1.00","2":"1.00","version_comment":"Initial upload","3":"Initial upload","package":"CompleteHelper.vba.gz","4":"CompleteHelper.vba.gz","src_id":"17349","5":"17349","creation_date":"1328026887","6":"1328026887"}]},"3913":{"script_id":"3913","0":"3913","script_name":"CapsulaPigmentorum.vim","1":"CapsulaPigmentorum.vim","script_type":"color scheme","2":"color scheme","summary":"mod of paintbox","3":"mod of paintbox","description":"Preview (in Perl): http:\/\/i.imgur.com\/wJoZdL5.png\r\nThe same file with the original paintbox scheme: http:\/\/i.imgur.com\/k5LXJ8t.png\r\n\r\nGithub: https:\/\/github.com\/dbb\/vim\/blob\/master\/CapsulaPigmentorum.vim","4":"Preview (in Perl): http:\/\/i.imgur.com\/wJoZdL5.png\r\nThe same file with the original paintbox scheme: http:\/\/i.imgur.com\/k5LXJ8t.png\r\n\r\nGithub: https:\/\/github.com\/dbb\/vim\/blob\/master\/CapsulaPigmentorum.vim","install_details":"$ curl -LO https:\/\/github.com\/dbb\/vim\/raw\/master\/CapsulaPigmentorum.vim  \r\n\r\n$ mv CapsulaPigmentorum.vim  ~\/.vim\/colors ","5":"$ curl -LO https:\/\/github.com\/dbb\/vim\/raw\/master\/CapsulaPigmentorum.vim  \r\n\r\n$ mv CapsulaPigmentorum.vim  ~\/.vim\/colors ","first_name":"Daniel","6":"Daniel","last_name":"B","7":"B","releases":[{"0":"3913","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"CapsulaPigmentorum.vim","4":"CapsulaPigmentorum.vim","src_id":"17337","5":"17337","creation_date":"1327910264","6":"1327910264"}]},"3912":{"script_id":"3912","0":"3912","script_name":"toggle_comment","1":"toggle_comment","script_type":"utility","2":"utility","summary":"To Toggle Comment of single\/multiple lines of code","3":"To Toggle Comment of single\/multiple lines of code","description":"A small plugin to comment, un-comment or toggle one or more lines in both normal and visual mode.\r\n\r\n** Usage **\r\nIn normal or visual mode:\r\n    q to toggle comment\r\n    shift-q to force comment\r\n    alt-q to force un-comment\r\n\r\nAlso avaible in command mode:\r\n    Ct to toggle comment\r\n    Cc to force comment\r\n    Cu to force un-comment\r\nThese 3 commands are compatible with range and global (:g)\r\n\r\n\r\n** Examples **\r\n'yyqp' : duplicate and comment an uncommented line\r\n'vjq' : when two lines are [1 commented\/1 un-commented], switch the state of each line \r\n':g!\/toto\/Cc' : comment all lines which not contain 'toto'\r\n\r\n\r\n** Remarks **\r\n- The plugin will check the option \"&filetype\" and the variable \"b:current_syntax\" to know how to comment the file.\r\n- \"echo &filetype\" or \"echo b:current_syntax\" will give you the name of the syntax of the opened file.\r\n- Add a new syntax to the script (or change the default behavior) is very very simple (add only one line), so don't hesitate to adapt the script.\r\n-  For languages like fortran where the rest of the line should not be disturbed by the comment symbol, don't forget to add a line to \"s:comment_in_place\".","4":"A small plugin to comment, un-comment or toggle one or more lines in both normal and visual mode.\r\n\r\n** Usage **\r\nIn normal or visual mode:\r\n    q to toggle comment\r\n    shift-q to force comment\r\n    alt-q to force un-comment\r\n\r\nAlso avaible in command mode:\r\n    Ct to toggle comment\r\n    Cc to force comment\r\n    Cu to force un-comment\r\nThese 3 commands are compatible with range and global (:g)\r\n\r\n\r\n** Examples **\r\n'yyqp' : duplicate and comment an uncommented line\r\n'vjq' : when two lines are [1 commented\/1 un-commented], switch the state of each line \r\n':g!\/toto\/Cc' : comment all lines which not contain 'toto'\r\n\r\n\r\n** Remarks **\r\n- The plugin will check the option \"&filetype\" and the variable \"b:current_syntax\" to know how to comment the file.\r\n- \"echo &filetype\" or \"echo b:current_syntax\" will give you the name of the syntax of the opened file.\r\n- Add a new syntax to the script (or change the default behavior) is very very simple (add only one line), so don't hesitate to adapt the script.\r\n-  For languages like fortran where the rest of the line should not be disturbed by the comment symbol, don't forget to add a line to \"s:comment_in_place\".","install_details":"copy script to ~\/.vim\/plugin \r\n\r\nI am not sure but, since instructions in the script are quite simple, I think that this plugin must be compatible with older vim versions.","5":"copy script to ~\/.vim\/plugin \r\n\r\nI am not sure but, since instructions in the script are quite simple, I think that this plugin must be compatible with older vim versions.","first_name":"farid","6":"farid","last_name":"smai","7":"smai","releases":[{"0":"3912","vim_version":"7.0","1":"7.0","script_version":"1.7","2":"1.7","version_comment":"fix bug with c-style comments : last search was replaced by a dummy search ; now last search is preserved.","3":"fix bug with c-style comments : last search was replaced by a dummy search ; now last search is preserved.","package":"toggle_comment.vim","4":"toggle_comment.vim","src_id":"19498","5":"19498","creation_date":"1360685856","6":"1360685856"},{"0":"3912","vim_version":"7.0","1":"7.0","script_version":"1.6","2":"1.6","version_comment":"- fix bugs due to some comment symbols that end with one or more sapce ('\\s')","3":"- fix bugs due to some comment symbols that end with one or more sapce ('\\s')","package":"toggle_comment.vim","4":"toggle_comment.vim","src_id":"17442","5":"17442","creation_date":"1329122853","6":"1329122853"},{"0":"3912","vim_version":"7.0","1":"7.0","script_version":"1.5","2":"1.5","version_comment":"- improve the mechanism to find the \"comment symbol\". Now, we also use the \"&comments\" and \"&commentstring\" options if the \"comment symbol\" is not defined internarly.","3":"- improve the mechanism to find the \"comment symbol\". Now, we also use the \"&comments\" and \"&commentstring\" options if the \"comment symbol\" is not defined internarly.","package":"toggle_comment.vim","4":"toggle_comment.vim","src_id":"17441","5":"17441","creation_date":"1329120407","6":"1329120407"},{"0":"3912","vim_version":"7.0","1":"7.0","script_version":"1.3","2":"1.3","version_comment":"- add command compatible with range\r\n- change to make command compatible with ':g'\r\n- change map because ctrl-q is not compatible with terminal","3":"- add command compatible with range\r\n- change to make command compatible with ':g'\r\n- change map because ctrl-q is not compatible with terminal","package":"toggle_comment.vim","4":"toggle_comment.vim","src_id":"17348","5":"17348","creation_date":"1328018356","6":"1328018356"},{"0":"3912","vim_version":"7.0","1":"7.0","script_version":"1.2","2":"1.2","version_comment":"fix big trouble on some OS","3":"fix big trouble on some OS","package":"toggle_comment.vim","4":"toggle_comment.vim","src_id":"17338","5":"17338","creation_date":"1327915263","6":"1327915263"}]},"3911":{"script_id":"3911","0":"3911","script_name":"vim-punto-switcher","1":"vim-punto-switcher","script_type":"utility","2":"utility","summary":"Works like punto-switcher app. Helps when you type text in wrong keymap.","3":"Works like punto-switcher app. Helps when you type text in wrong keymap.","description":"Plugin that works like punto-switcher application. (but not absolutely similar, well)\r\nIt helps you if you typed some text in wrong keymap.\r\nRight now it supports only english and russian keymaps, but you can add your own keymap (You also can send it to me, and i\\'ll add it to next release)\r\n\r\nPlease NOTE: i tested it on Windows, in Vim 7.3.46, and all works fine in it. But i just get notified that in Linux, in Vim 7.3.353 only mappings ,re  and ,er  work correctly, and there's some issues with <F4> and <S-F4>. I'm trying to solve it.\r\n\r\n\r\nThere are some mappings provided by default.\r\n\r\nIn Insert and Normal modes the following mappings are available:\r\n\r\n*) <F4> translates current word. If you press <F4> again, then previous word\r\n   will be translated, and so on. Every <F4> keystroke gives you next word\r\n   translated, until you press <F4> from another cursor position.\r\n   Here\\'s example, say you just typed this: (\\\"|\\\" sign means cursor position) >\r\n      I don\\'t like ГИБДД мукн ьгсрю|\r\n<\r\n   Then you think: \\\"oops\\\", press <F4> twice, and here\\'s what you get: >\r\n      I don\\'t like ГИБДД very much.|\r\n<\r\n\r\n*) <S-F4> tries to autodetect what are you trying to translate. Basically, it \r\n   translates all the last text typed in one langmap. \r\n\r\n   Here\\'s example: (\\\"|\\\" sign means cursor position) >\r\n      The quick brown fox огьзы щмук еру дфян вщпю|\r\n<\r\n   Then you press <S-F4>, and text becomes translated to >\r\n      The quick brown fox jumps over the lazy dog.|\r\n<\r\n   If you press <S-F4> again, it will toggle the last translation.\r\n\r\n\r\n============================================================================\r\n\r\nYou are also able to select exactly what you need to translate and press one\r\nof the following predefined mappings:\r\n\r\n*) ,er   translates selected text en-ru\r\n*) ,re   translates selected text ru-en\r\n\r\n============================================================================\r\n\r\nIf you don\\'t like these predefined mappings for some reason, you can disable\r\nit and specify your own ones, just like that: >\r\n\r\n   \" disable predefined mappings\r\n   let g:pswitcher_no_default_key_mappings = 1\r\n   \r\n   \" visual mode mappings\r\n   vmap ,er <Plug>(pswitcher-selected-en-ru)\r\n   vmap ,re <Plug>(pswitcher-selected-ru-en)\r\n\r\n   \" insert and normal mode mapping for last word translation\r\n   imap <F4> <Plug>(pswitcher-input-word)\r\n   map  <F4> <Plug>(pswitcher-word)\r\n\r\n   \" insert and normal mode mapping for auto text translation\r\n   imap <S-F4> <Plug>(pswitcher-input-auto)\r\n   map  <S-F4> <Plug>(pswitcher-auto)\r\n\r\n\r\nThat's it. Hope you like it.\r\nHappy Vimming! \r\n\r\n=======================================================\r\n\r\nP.S. you can read more detailed info about adding your own keymap here:  \r\n\r\n:help pswitcher_two_main_maps\r\n ","4":"Plugin that works like punto-switcher application. (but not absolutely similar, well)\r\nIt helps you if you typed some text in wrong keymap.\r\nRight now it supports only english and russian keymaps, but you can add your own keymap (You also can send it to me, and i\\'ll add it to next release)\r\n\r\nPlease NOTE: i tested it on Windows, in Vim 7.3.46, and all works fine in it. But i just get notified that in Linux, in Vim 7.3.353 only mappings ,re  and ,er  work correctly, and there's some issues with <F4> and <S-F4>. I'm trying to solve it.\r\n\r\n\r\nThere are some mappings provided by default.\r\n\r\nIn Insert and Normal modes the following mappings are available:\r\n\r\n*) <F4> translates current word. If you press <F4> again, then previous word\r\n   will be translated, and so on. Every <F4> keystroke gives you next word\r\n   translated, until you press <F4> from another cursor position.\r\n   Here\\'s example, say you just typed this: (\\\"|\\\" sign means cursor position) >\r\n      I don\\'t like ГИБДД мукн ьгсрю|\r\n<\r\n   Then you think: \\\"oops\\\", press <F4> twice, and here\\'s what you get: >\r\n      I don\\'t like ГИБДД very much.|\r\n<\r\n\r\n*) <S-F4> tries to autodetect what are you trying to translate. Basically, it \r\n   translates all the last text typed in one langmap. \r\n\r\n   Here\\'s example: (\\\"|\\\" sign means cursor position) >\r\n      The quick brown fox огьзы щмук еру дфян вщпю|\r\n<\r\n   Then you press <S-F4>, and text becomes translated to >\r\n      The quick brown fox jumps over the lazy dog.|\r\n<\r\n   If you press <S-F4> again, it will toggle the last translation.\r\n\r\n\r\n============================================================================\r\n\r\nYou are also able to select exactly what you need to translate and press one\r\nof the following predefined mappings:\r\n\r\n*) ,er   translates selected text en-ru\r\n*) ,re   translates selected text ru-en\r\n\r\n============================================================================\r\n\r\nIf you don\\'t like these predefined mappings for some reason, you can disable\r\nit and specify your own ones, just like that: >\r\n\r\n   \" disable predefined mappings\r\n   let g:pswitcher_no_default_key_mappings = 1\r\n   \r\n   \" visual mode mappings\r\n   vmap ,er <Plug>(pswitcher-selected-en-ru)\r\n   vmap ,re <Plug>(pswitcher-selected-ru-en)\r\n\r\n   \" insert and normal mode mapping for last word translation\r\n   imap <F4> <Plug>(pswitcher-input-word)\r\n   map  <F4> <Plug>(pswitcher-word)\r\n\r\n   \" insert and normal mode mapping for auto text translation\r\n   imap <S-F4> <Plug>(pswitcher-input-auto)\r\n   map  <S-F4> <Plug>(pswitcher-auto)\r\n\r\n\r\nThat's it. Hope you like it.\r\nHappy Vimming! \r\n\r\n=======================================================\r\n\r\nP.S. you can read more detailed info about adding your own keymap here:  \r\n\r\n:help pswitcher_two_main_maps\r\n ","install_details":"Use pathogen.","5":"Use pathogen.","first_name":"Dmitry","6":"Dmitry","last_name":"Frank","7":"Frank","releases":[{"0":"3911","vim_version":"7.0","1":"7.0","script_version":"1.00","2":"1.00","version_comment":"Initial upload","3":"Initial upload","package":"vim-punto-switcher-1.00.tar.gz","4":"vim-punto-switcher-1.00.tar.gz","src_id":"17333","5":"17333","creation_date":"1327832931","6":"1327832931"}]},"3910":{"script_id":"3910","0":"3910","script_name":"gmlua.vim","1":"gmlua.vim","script_type":"syntax","2":"syntax","summary":"Garry's Mod Lua","3":"Garry's Mod Lua","description":"Syntax rules for the dialect of Lua 5.1 used in Garry's Mod. This currently reproduces most of the standard Lua rules. It should be rewritten to include them instead.","4":"Syntax rules for the dialect of Lua 5.1 used in Garry's Mod. This currently reproduces most of the standard Lua rules. It should be rewritten to include them instead.","install_details":"","5":"","first_name":"Sam","6":"Sam","last_name":"Hanes","7":"Hanes","releases":[{"0":"3910","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"gmlua.vim","4":"gmlua.vim","src_id":"17327","5":"17327","creation_date":"1327735755","6":"1327735755"}]},"3909":{"script_id":"3909","0":"3909","script_name":"e2.lua","1":"e2.lua","script_type":"syntax","2":"syntax","summary":"GMod Wire Expression2","3":"GMod Wire Expression2","description":"Simple syntax rules for the Wire Expression2 in-game scripting language in Garry's Mod.","4":"Simple syntax rules for the Wire Expression2 in-game scripting language in Garry's Mod.","install_details":"","5":"","first_name":"Sam","6":"Sam","last_name":"Hanes","7":"Hanes","releases":[{"0":"3909","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"e2.vim","4":"e2.vim","src_id":"17326","5":"17326","creation_date":"1327735447","6":"1327735447"}]},"3908":{"script_id":"3908","0":"3908","script_name":"mozjs.vim","1":"mozjs.vim","script_type":"syntax","2":"syntax","summary":"JavaScript with Mozilla preprocessor support","3":"JavaScript with Mozilla preprocessor support","description":"JavaScript files in Mozilla products use a custom preprocessor. This is a simple inclusion of the standard JavaScript syntax rules and my Mozilla preprocessor rules (vimscript #3907), which must be installed. ","4":"JavaScript files in Mozilla products use a custom preprocessor. This is a simple inclusion of the standard JavaScript syntax rules and my Mozilla preprocessor rules (vimscript #3907), which must be installed. ","install_details":"","5":"","first_name":"Sam","6":"Sam","last_name":"Hanes","7":"Hanes","releases":[{"0":"3908","vim_version":"5.7","1":"5.7","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"mozjs.vim","4":"mozjs.vim","src_id":"17325","5":"17325","creation_date":"1327735212","6":"1327735212"}]},"3907":{"script_id":"3907","0":"3907","script_name":"mozpp.vim","1":"mozpp.vim","script_type":"syntax","2":"syntax","summary":"Mozilla's preprocessor for JavaScript and XUL","3":"Mozilla's preprocessor for JavaScript and XUL","description":"Mozilla uses a custom preprocessor for languages that don't have their own. This is a minimal set of syntax rules for it based on the preprocessor rules from c.vim.\r\n\r\nFor more on the Mozilla preprocessor:\r\nhttps:\/\/developer.mozilla.org\/en\/Build\/Text_Preprocessor","4":"Mozilla uses a custom preprocessor for languages that don't have their own. This is a minimal set of syntax rules for it based on the preprocessor rules from c.vim.\r\n\r\nFor more on the Mozilla preprocessor:\r\nhttps:\/\/developer.mozilla.org\/en\/Build\/Text_Preprocessor","install_details":"","5":"","first_name":"Sam","6":"Sam","last_name":"Hanes","7":"Hanes","releases":[{"0":"3907","vim_version":"5.7","1":"5.7","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"mozpp.vim","4":"mozpp.vim","src_id":"17324","5":"17324","creation_date":"1327733886","6":"1327733886"}]},"3906":{"script_id":"3906","0":"3906","script_name":"ocamlMultiAnnot","1":"ocamlMultiAnnot","script_type":"ftplugin","2":"ftplugin","summary":"Annotation for mutiple files + bugfixes","3":"Annotation for mutiple files + bugfixes","description":"This plugin is an improvement of the official ocaml ftplugin.\r\n\r\nIt corrects the 2 following bugs:\r\n    - If nowrapscan is set, as annot file was not always read from beginning, we could not find result for information between the beginning of file and cursor position.\r\n    - In splitted view, when we were reloading the .annot file, it was closing one of the splitted view.\r\n\r\nNew functionnality:\r\nIf we work with several ocaml .ml files, annotation are loaded for every file and so we can use those annotation for every buffer.\r\n\r\nAdded with version 1.1:\r\nIn addition to printing the type with <LocalLeader>t, save the type in the unnamed register, in order to copy\/use it more easily.\r\n\r\nI have tested this pugin on my own computer during a few weeks without bugs, please feel free to report bugs.\r\n\r\nThe plugin is essentially based on the official ocaml ftplugin, I would like to thanks:\r\nDavid Baelde\r\nMike Leary\r\nMarkus Mottl\r\nStefano Zacchiroli\r\nVincent Aravantinos\r\nand others contributors to ocaml vim integration. \r\n","4":"This plugin is an improvement of the official ocaml ftplugin.\r\n\r\nIt corrects the 2 following bugs:\r\n    - If nowrapscan is set, as annot file was not always read from beginning, we could not find result for information between the beginning of file and cursor position.\r\n    - In splitted view, when we were reloading the .annot file, it was closing one of the splitted view.\r\n\r\nNew functionnality:\r\nIf we work with several ocaml .ml files, annotation are loaded for every file and so we can use those annotation for every buffer.\r\n\r\nAdded with version 1.1:\r\nIn addition to printing the type with <LocalLeader>t, save the type in the unnamed register, in order to copy\/use it more easily.\r\n\r\nI have tested this pugin on my own computer during a few weeks without bugs, please feel free to report bugs.\r\n\r\nThe plugin is essentially based on the official ocaml ftplugin, I would like to thanks:\r\nDavid Baelde\r\nMike Leary\r\nMarkus Mottl\r\nStefano Zacchiroli\r\nVincent Aravantinos\r\nand others contributors to ocaml vim integration. \r\n","install_details":"Assuming your personal vim directory is \"~\/.vim\/\".\r\n- Copy the plugin in \"~\/.vim\/ftplugin\/\"\r\n- It should override the standard ocaml.vim ftplugin.\r\n","5":"Assuming your personal vim directory is \"~\/.vim\/\".\r\n- Copy the plugin in \"~\/.vim\/ftplugin\/\"\r\n- It should override the standard ocaml.vim ftplugin.\r\n","first_name":"Pierre ","6":"Pierre ","last_name":"Vittet","7":"Vittet","releases":[{"0":"3906","vim_version":"7.2","1":"7.2","script_version":"1.1","2":"1.1","version_comment":"Added feature: In addition to printing the type with <LocalLeader>t, save the type in the unnamed buffer, in order to copy\/use it easily.","3":"Added feature: In addition to printing the type with <LocalLeader>t, save the type in the unnamed buffer, in order to copy\/use it easily.","package":"ocaml.vim","4":"ocaml.vim","src_id":"17411","5":"17411","creation_date":"1328732059","6":"1328732059"},{"0":"3906","vim_version":"7.2","1":"7.2","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"ocaml.vim","4":"ocaml.vim","src_id":"17320","5":"17320","creation_date":"1327613420","6":"1327613420"}]},"3905":{"script_id":"3905","0":"3905","script_name":"vombato-colorscheme","1":"vombato-colorscheme","script_type":"color scheme","2":"color scheme","summary":"Inspired by wombat, but more complete","3":"Inspired by wombat, but more complete","description":"This is a colorscheme forked from wombat, but more complete.\r\nRight now it's gui only, you can use it in a terminal with the\r\nColorSupport plugin.\r\n\r\nScreenshot: https:\/\/github.com\/molok\/vim-vombato-colorscheme\/raw\/master\/img\/vombato.png\r\n\r\nOfficial repository \/ bug tracker: https:\/\/github.com\/molok\/vim-vombato-colorscheme\/\r\n","4":"This is a colorscheme forked from wombat, but more complete.\r\nRight now it's gui only, you can use it in a terminal with the\r\nColorSupport plugin.\r\n\r\nScreenshot: https:\/\/github.com\/molok\/vim-vombato-colorscheme\/raw\/master\/img\/vombato.png\r\n\r\nOfficial repository \/ bug tracker: https:\/\/github.com\/molok\/vim-vombato-colorscheme\/\r\n","install_details":"Extract the colorscheme file in $VIMHOME\/colors\/ where $VIMHOME it's usually $HOME\/.vim\/ on UNIX-like OSes and $HOME\/vimfiles on Windows","5":"Extract the colorscheme file in $VIMHOME\/colors\/ where $VIMHOME it's usually $HOME\/.vim\/ on UNIX-like OSes and $HOME\/vimfiles on Windows","first_name":"Alessio","6":"Alessio","last_name":"Bolognino","7":"Bolognino","releases":[{"0":"3905","vim_version":"7.0","1":"7.0","script_version":"0.1.1","2":"0.1.1","version_comment":"Added support for Conceal and CursorLineNr, also changed the color of Boolean","3":"Added support for Conceal and CursorLineNr, also changed the color of Boolean","package":"vombato-colorscheme-0.1.1.zip","4":"vombato-colorscheme-0.1.1.zip","src_id":"20503","5":"20503","creation_date":"1373372158","6":"1373372158"},{"0":"3905","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"vombato-colorscheme-0.1.zip","4":"vombato-colorscheme-0.1.zip","src_id":"17313","5":"17313","creation_date":"1327445558","6":"1327445558"}]},"3904":{"script_id":"3904","0":"3904","script_name":"nsl.vim","1":"nsl.vim","script_type":"syntax","2":"syntax","summary":"VIM Syntax file for NSL hardware description language. ","3":"VIM Syntax file for NSL hardware description language. ","description":"NSL, Next Synthesis Language, is a one of the Hardware Description Language and successor of SFL. NSL is Register Transfer Level HDL, the syntax is like C.\r\nPlease see here: http:\/\/www.ip-arch.jp\/indexe.html http:\/\/www.overtone.co.jp\/en\/products\/about_nsl\/\r\n\r\nNSL can be converted to Verilog HDL or VHDL or SystemC with NSL Core.","4":"NSL, Next Synthesis Language, is a one of the Hardware Description Language and successor of SFL. NSL is Register Transfer Level HDL, the syntax is like C.\r\nPlease see here: http:\/\/www.ip-arch.jp\/indexe.html http:\/\/www.overtone.co.jp\/en\/products\/about_nsl\/\r\n\r\nNSL can be converted to Verilog HDL or VHDL or SystemC with NSL Core.","install_details":"","5":"","first_name":"Makoto","6":"Makoto","last_name":"Kishimoto","7":"Kishimoto","releases":[{"0":"3904","vim_version":"7.0","1":"7.0","script_version":"0.4","2":"0.4","version_comment":"Some keywords (and etc...) added. Thanks to PR sender.","3":"Some keywords (and etc...) added. Thanks to PR sender.","package":"nsl_vim-0.4.zip","4":"nsl_vim-0.4.zip","src_id":"25943","5":"25943","creation_date":"1524562829","6":"1524562829"},{"0":"3904","vim_version":"5.7","1":"5.7","script_version":"0.3","2":"0.3","version_comment":"Initial upload","3":"Initial upload","package":"nsl.vim","4":"nsl.vim","src_id":"17311","5":"17311","creation_date":"1327378621","6":"1327378621"}]},"3903":{"script_id":"3903","0":"3903","script_name":"xsnippet","1":"xsnippet","script_type":"utility","2":"utility","summary":"A plugin for XSnippet.org pastebin service","3":"A plugin for XSnippet.org pastebin service","description":"vim-xsnippet  is  a  simple  Vim  plugin  which enables  one to post\r\ncode snippets to the XSnippet.org pastebin service directly from Vim.\r\n\r\nRequirements:\r\n    - Python 2.x\r\n    - Vim 7.x built with '+python' option\r\n\r\nUsing:\r\n    :call PostToXsnippet() --- posts the content of the current buffer to the XSnippet.org\r\n                               and puts the snippet's url to the clipboard\r\n\r\nInfo:\r\n    Author:   Roman Podolyaka (roman.podolyaka@gmail.com)\r\n    License:  GNU GPL v3\r\n    Homepage: https:\/\/github.com\/bloodeclipse\/vim-xsnippet","4":"vim-xsnippet  is  a  simple  Vim  plugin  which enables  one to post\r\ncode snippets to the XSnippet.org pastebin service directly from Vim.\r\n\r\nRequirements:\r\n    - Python 2.x\r\n    - Vim 7.x built with '+python' option\r\n\r\nUsing:\r\n    :call PostToXsnippet() --- posts the content of the current buffer to the XSnippet.org\r\n                               and puts the snippet's url to the clipboard\r\n\r\nInfo:\r\n    Author:   Roman Podolyaka (roman.podolyaka@gmail.com)\r\n    License:  GNU GPL v3\r\n    Homepage: https:\/\/github.com\/bloodeclipse\/vim-xsnippet","install_details":"Installation:\r\n    Copy all files to your $VIMRUNTIME dir (usually ~\/.vim).\r\n    Note: if you use pathogen, copy all files to some dir in your bundles path.","5":"Installation:\r\n    Copy all files to your $VIMRUNTIME dir (usually ~\/.vim).\r\n    Note: if you use pathogen, copy all files to some dir in your bundles path.","first_name":"Roman","6":"Roman","last_name":"Podoliaka","7":"Podoliaka","releases":[{"0":"3903","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"xsnippet.tar.gz","4":"xsnippet.tar.gz","src_id":"17292","5":"17292","creation_date":"1327182755","6":"1327182755"}]},"3902":{"script_id":"3902","0":"3902","script_name":"compot","1":"compot","script_type":"color scheme","2":"color scheme","summary":"Erlang-friendly gVim\/MacVim colorscheme","3":"Erlang-friendly gVim\/MacVim colorscheme","description":"Screenshot and up-to-date code always at: https:\/\/github.com\/aerosol\/vim-compot","4":"Screenshot and up-to-date code always at: https:\/\/github.com\/aerosol\/vim-compot","install_details":"","5":"","first_name":"adam","6":"adam","last_name":"r","7":"r","releases":[{"0":"3902","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"compot.vim","4":"compot.vim","src_id":"17291","5":"17291","creation_date":"1327172566","6":"1327172566"}]},"3901":{"script_id":"3901","0":"3901","script_name":"coffee-check.vim","1":"coffee-check.vim","script_type":"ftplugin","2":"ftplugin","summary":"Automatic CoffeeScript syntax validation checker for Vim","3":"Automatic CoffeeScript syntax validation checker for Vim","description":"Duplicated, please go to http:\/\/www.vim.org\/scripts\/script.php?script_id=3900","4":"Duplicated, please go to http:\/\/www.vim.org\/scripts\/script.php?script_id=3900","install_details":"","5":"","first_name":"wei ko","6":"wei ko","last_name":"kao","7":"kao","releases":[{"0":"3901","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"coffee-check.vim-0.1.vmb","4":"coffee-check.vim-0.1.vmb","src_id":"17282","5":"17282","creation_date":"1327166519","6":"1327166519"}]},"3900":{"script_id":"3900","0":"3900","script_name":"coffee-check.vim","1":"coffee-check.vim","script_type":"ftplugin","2":"ftplugin","summary":"Automatic CoffeeScript syntax validation checker for Vim","3":"Automatic CoffeeScript syntax validation checker for Vim","description":"It is hard to find out where is you script error if you use CoffeeScript plugin for RequireJS. This Vim plugin is design to help reduce the effect of this issue, it will check the code syntax base on CoffeeScript compiler everytime when you save a coffee file automatically.\r\n\r\nRequirement\r\n\r\nnode: used to compile coffee script.\r\n\r\nImportant (Known Issues)\r\n\r\nOnly one error appears in every check, if you have several error in your script, you will have to fix one by one.\r\nSome error message can't locate to correct line number, all this kind of error will mark to line 1.\r\nCause of previous issue, can't use the behavior of jslint.vim. So Vim will open quickfix window if any error was found, side effect of open a quikfix window is the focus will be moved to quick fix window.\r\n\r\nAcknowledge\r\n\r\nThanks for the base of jslint.vim by Jesse Hallett.\r\n\r\nLicense\r\n\r\nRelease under MIT License.","4":"It is hard to find out where is you script error if you use CoffeeScript plugin for RequireJS. This Vim plugin is design to help reduce the effect of this issue, it will check the code syntax base on CoffeeScript compiler everytime when you save a coffee file automatically.\r\n\r\nRequirement\r\n\r\nnode: used to compile coffee script.\r\n\r\nImportant (Known Issues)\r\n\r\nOnly one error appears in every check, if you have several error in your script, you will have to fix one by one.\r\nSome error message can't locate to correct line number, all this kind of error will mark to line 1.\r\nCause of previous issue, can't use the behavior of jslint.vim. So Vim will open quickfix window if any error was found, side effect of open a quikfix window is the focus will be moved to quick fix window.\r\n\r\nAcknowledge\r\n\r\nThanks for the base of jslint.vim by Jesse Hallett.\r\n\r\nLicense\r\n\r\nRelease under MIT License.","install_details":"Use pathogen.vim or Vundle is suggestion, Github: https:\/\/github.com\/othree\/coffee-check.vim\r\n\r\nIf you didn't install vim-coffee-script: http:\/\/www.vim.org\/scripts\/script.php?script_id=3590\r\nAdd the following line to vimrc:\r\n\r\nau BufRead,BufNewFile *.coffee set ft=coffee\r\n\r\n","5":"Use pathogen.vim or Vundle is suggestion, Github: https:\/\/github.com\/othree\/coffee-check.vim\r\n\r\nIf you didn't install vim-coffee-script: http:\/\/www.vim.org\/scripts\/script.php?script_id=3590\r\nAdd the following line to vimrc:\r\n\r\nau BufRead,BufNewFile *.coffee set ft=coffee\r\n\r\n","first_name":"wei ko","6":"wei ko","last_name":"kao","7":"kao","releases":[{"0":"3900","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"coffee-check.vim-0.1.vmb","4":"coffee-check.vim-0.1.vmb","src_id":"17279","5":"17279","creation_date":"1327152370","6":"1327152370"}]},"3899":{"script_id":"3899","0":"3899","script_name":"indent\/java.vim","1":"indent\/java.vim","script_type":"indent","2":"indent","summary":"Vim indent file for java source files","3":"Vim indent file for java source files","description":"This is an indent file for java source files. This indent file is based on the java indent file maintained by Toby Allsopp, which was shipped with the official vim distribution before vim version 7.3.408.\r\n\r\nThis script has been included in the official vim distribution since vim version 7.3.409. \r\n\r\nGit Repository: https:\/\/github.com\/xuhdev\/indent-java.vim\r\n\r\nIf you have any problem, you could either send me an email <hong@topbug.net> or submit it on the issue tracker:\r\n\r\nhttps:\/\/github.com\/xuhdev\/indent-java.vim\/issues\r\n","4":"This is an indent file for java source files. This indent file is based on the java indent file maintained by Toby Allsopp, which was shipped with the official vim distribution before vim version 7.3.408.\r\n\r\nThis script has been included in the official vim distribution since vim version 7.3.409. \r\n\r\nGit Repository: https:\/\/github.com\/xuhdev\/indent-java.vim\r\n\r\nIf you have any problem, you could either send me an email <hong@topbug.net> or submit it on the issue tracker:\r\n\r\nhttps:\/\/github.com\/xuhdev\/indent-java.vim\/issues\r\n","install_details":"Download the indent-java.zip file and extract it to your vim runtime\r\ndirectory(~\/.vim in UNIX\/Linux and $VIM_INSTALLATION_FOLDER\\vimfiles in windows). ","5":"Download the indent-java.zip file and extract it to your vim runtime\r\ndirectory(~\/.vim in UNIX\/Linux and $VIM_INSTALLATION_FOLDER\\vimfiles in windows). ","first_name":"Hong","6":"Hong","last_name":"Xu","7":"Xu","releases":[{"0":"3899","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"indent-java.zip","4":"indent-java.zip","src_id":"17271","5":"17271","creation_date":"1327123589","6":"1327123589"}]},"3898":{"script_id":"3898","0":"3898","script_name":"gtk-mode","1":"gtk-mode","script_type":"utility","2":"utility","summary":"Collection of gtk\/vala tools","3":"Collection of gtk\/vala tools","description":"I wanted to create something to have everything in one place\r\nI'll add more tools soon!\r\n\r\ncurrent version only has vala syntax and gtk syntax highlighting from other scripts\r\n\r\ngit repo: https:\/\/bitbucket.org\/aliva\/vim-gtk-mode","4":"I wanted to create something to have everything in one place\r\nI'll add more tools soon!\r\n\r\ncurrent version only has vala syntax and gtk syntax highlighting from other scripts\r\n\r\ngit repo: https:\/\/bitbucket.org\/aliva\/vim-gtk-mode","install_details":"","5":"","first_name":"Ali","6":"Ali","last_name":"Vakilzade","7":"Vakilzade","releases":[{"0":"3898","vim_version":"7.3","1":"7.3","script_version":"20120120","2":"20120120","version_comment":"Initial upload","3":"Initial upload","package":"gtk-mode-0.1.tar.gz","4":"gtk-mode-0.1.tar.gz","src_id":"17267","5":"17267","creation_date":"1327076169","6":"1327076169"}]},"3897":{"script_id":"3897","0":"3897","script_name":"pwdstatus.vim","1":"pwdstatus.vim","script_type":"utility","2":"utility","summary":"a statusline that highlights key information (such as the pwd)","3":"a statusline that highlights key information (such as the pwd)","description":"I'm often using :cd or autochdir and can never remember where I currently am.  Why use :pwd when that information can already be on the statusline?\r\n\r\nI also glance at the filename, line number, column number, etc..  Some information I look for more often than others.  Those things should stand out but just a little.  This statusline uses color to draw your attention ever so slightly.  That is, unless it's read-only, unsaved, etc., which should *really* draw your attention!\r\n\r\nScreenshot:\r\nhttp:\/\/i1177.photobucket.com\/albums\/x344\/seymore15074\/Flymaker2.png","4":"I'm often using :cd or autochdir and can never remember where I currently am.  Why use :pwd when that information can already be on the statusline?\r\n\r\nI also glance at the filename, line number, column number, etc..  Some information I look for more often than others.  Those things should stand out but just a little.  This statusline uses color to draw your attention ever so slightly.  That is, unless it's read-only, unsaved, etc., which should *really* draw your attention!\r\n\r\nScreenshot:\r\nhttp:\/\/i1177.photobucket.com\/albums\/x344\/seymore15074\/Flymaker2.png","install_details":"Just place it in your plugin directory.","5":"Just place it in your plugin directory.","first_name":"Chad","6":"Chad","last_name":"Moore","7":"Moore","releases":[{"0":"3897","vim_version":"7.0","1":"7.0","script_version":"0.1.0","2":"0.1.0","version_comment":"Initial upload","3":"Initial upload","package":"pwdstatus.vim","4":"pwdstatus.vim","src_id":"17266","5":"17266","creation_date":"1327075751","6":"1327075751"}]},"3896":{"script_id":"3896","0":"3896","script_name":"buffet.vim","1":"buffet.vim","script_type":"utility","2":"utility","summary":"A fast, easy to use buffer list plugin for switching and managing buffers.","3":"A fast, easy to use buffer list plugin for switching and managing buffers.","description":"Please update the latest version of this plugin from the Mercurial repo at https:\/\/bitbucket.org\/sras\/buffet\r\n\r\nWhen the plugin is invoked a horizontal window is opened with a list of buffers. the buffer numbers are also displayed along side. \r\n\r\nScreenshot: http:\/\/i43.tinypic.com\/33kadsx.png\r\n\r\nMercurial repo : https:\/\/bitbucket.org\/sras\/buffet\r\n\r\nThe user select a buffer by\r\n\r\n 1.Entering the buffer number using keyboard. Just start typing the number using keyboard.\r\n The plugin will search for the buffer with that number and will keep going to the matching\r\n buffers. Entered number will be shown at the top you can use backspace to edit it.When you \r\n are in the desired buffer, press enter or any control keys that are\r\n displayed at the bottom to execute any command available, on that buffer\r\n\r\n Available commands\r\n \r\n Enter(Replace current buffer) \r\n o - (Make window fill with selected buffer )\r\n h\/v - (Horizontal\/vertical Split) \r\n g - (Go to buffer window if it is visible in a tab) \r\n d - (Delete selected buffer) \r\n t - (Open buffer in a new tab)\r\n c - (Clear all the diff views)\r\n m - Toggle detailed view for files\r\n x - Close a window, in whatever tab it is displayed.\r\n'-' - (Opens a vertical window showing difference of the selected buffer with the current buffer. The scrolling of the new window will be bound to the current buffer )\r\n\r\n 2.Move up or down using the navigation keys to reach the buffer line.\r\n\r\n 3.Double click on a buffer line using the mouse. Will immediately switch to\r\n that buffer\r\n\r\nIf you are having any issues using the plugin or if you find any bugs, please let me know at sandeepcr2@gmail.com. ","4":"Please update the latest version of this plugin from the Mercurial repo at https:\/\/bitbucket.org\/sras\/buffet\r\n\r\nWhen the plugin is invoked a horizontal window is opened with a list of buffers. the buffer numbers are also displayed along side. \r\n\r\nScreenshot: http:\/\/i43.tinypic.com\/33kadsx.png\r\n\r\nMercurial repo : https:\/\/bitbucket.org\/sras\/buffet\r\n\r\nThe user select a buffer by\r\n\r\n 1.Entering the buffer number using keyboard. Just start typing the number using keyboard.\r\n The plugin will search for the buffer with that number and will keep going to the matching\r\n buffers. Entered number will be shown at the top you can use backspace to edit it.When you \r\n are in the desired buffer, press enter or any control keys that are\r\n displayed at the bottom to execute any command available, on that buffer\r\n\r\n Available commands\r\n \r\n Enter(Replace current buffer) \r\n o - (Make window fill with selected buffer )\r\n h\/v - (Horizontal\/vertical Split) \r\n g - (Go to buffer window if it is visible in a tab) \r\n d - (Delete selected buffer) \r\n t - (Open buffer in a new tab)\r\n c - (Clear all the diff views)\r\n m - Toggle detailed view for files\r\n x - Close a window, in whatever tab it is displayed.\r\n'-' - (Opens a vertical window showing difference of the selected buffer with the current buffer. The scrolling of the new window will be bound to the current buffer )\r\n\r\n 2.Move up or down using the navigation keys to reach the buffer line.\r\n\r\n 3.Double click on a buffer line using the mouse. Will immediately switch to\r\n that buffer\r\n\r\nIf you are having any issues using the plugin or if you find any bugs, please let me know at sandeepcr2@gmail.com. ","install_details":" Copy the file buffet.vim to the plugins directory.\r\n The command to open the buffer list is \r\n \r\n :Bufferlist\r\n\r\n To make this plugin really useful you have to assign a shortcut key for it, \r\n say you want F2 key to open the buffer list. you can add the following line in your .vimrc file. \r\n\r\n map <F2> :Bufferlist<CR>","5":" Copy the file buffet.vim to the plugins directory.\r\n The command to open the buffer list is \r\n \r\n :Bufferlist\r\n\r\n To make this plugin really useful you have to assign a shortcut key for it, \r\n say you want F2 key to open the buffer list. you can add the following line in your .vimrc file. \r\n\r\n map <F2> :Bufferlist<CR>","first_name":"Sandeep","6":"Sandeep","last_name":"CR","7":"CR","releases":[{"0":"3896","vim_version":"7.0","1":"7.0","script_version":"2.10","2":"2.10","version_comment":"    Added  buffer with no name to the list. \r\n\r\n    Layout change for buffer list.Made columns to correctly align on top of each other.\r\n\r\n    Removed the highlight for current window\/buffer. Current window is enclosed in a > < instead\r\n\r\n    Made a shorter version of path to show initially, Can toggle detail view using 'm' key. ","3":"    Added  buffer with no name to the list. \r\n\r\n    Layout change for buffer list.Made columns to correctly align on top of each other.\r\n\r\n    Removed the highlight for current window\/buffer. Current window is enclosed in a > < instead\r\n\r\n    Made a shorter version of path to show initially, Can toggle detail view using 'm' key. ","package":"buffet.vim","4":"buffet.vim","src_id":"17418","5":"17418","creation_date":"1328807320","6":"1328807320"},{"0":"3896","vim_version":"7.0","1":"7.0","script_version":"2.0","2":"2.0","version_comment":"    Added support for multiple windows showing same buffer.\r\n\r\n    Removed file type and file encoding information from buffer list.\r\n\r\n    Fixed an issue when vim is invoked from command line with multiple arguments\r\n\r\n    Added 'x' command to close a window in what ever tab it is displayed.\r\n\r\n    Changed the 'h' command to 'hh' to prevent accidental opening when moving across the list.\r\n\r\n","3":"    Added support for multiple windows showing same buffer.\r\n\r\n    Removed file type and file encoding information from buffer list.\r\n\r\n    Fixed an issue when vim is invoked from command line with multiple arguments\r\n\r\n    Added 'x' command to close a window in what ever tab it is displayed.\r\n\r\n    Changed the 'h' command to 'hh' to prevent accidental opening when moving across the list.\r\n\r\n","package":"buffet.vim","4":"buffet.vim","src_id":"17318","5":"17318","creation_date":"1327570232","6":"1327570232"},{"0":"3896","vim_version":"7.0","1":"7.0","script_version":"1.15","2":"1.15","version_comment":"Added 't' command to open a buffer in a new tab.\r\nRemoved the delete restriction for buffers currently displayed.\r\nAdded 'c' command to clear all the diff views for currently displayed windows.","3":"Added 't' command to open a buffer in a new tab.\r\nRemoved the delete restriction for buffers currently displayed.\r\nAdded 'c' command to clear all the diff views for currently displayed windows.","package":"buffet.vim","4":"buffet.vim","src_id":"17314","5":"17314","creation_date":"1327478967","6":"1327478967"},{"0":"3896","vim_version":"7.0","1":"7.0","script_version":"1.10","2":"1.10","version_comment":"Fixed a bug where it resets the global value of scroll offset to 0,Thanks to Dimitri.  Added '-' command for opening a vertical diff window showing diff with the current buffer\r\nFixed some minor issues.","3":"Fixed a bug where it resets the global value of scroll offset to 0,Thanks to Dimitri.  Added '-' command for opening a vertical diff window showing diff with the current buffer\r\nFixed some minor issues.","package":"buffet.vim","4":"buffet.vim","src_id":"17304","5":"17304","creation_date":"1327331738","6":"1327331738"},{"0":"3896","vim_version":"7.0","1":"7.0","script_version":"1.05","2":"1.05","version_comment":"Added tab switching. If a buffer is displayed in another tab, then pressing 'g' will go to that tab and switch to the corresponding window.\r\n\r\nAdded file-encoding,file format,tab no and window no information for buffers in the list.\r\n\r\nBufferlist now opens at the very top with maximum width. \r\n\r\nFixed an issue with the 'g' navigation command","3":"Added tab switching. If a buffer is displayed in another tab, then pressing 'g' will go to that tab and switch to the corresponding window.\r\n\r\nAdded file-encoding,file format,tab no and window no information for buffers in the list.\r\n\r\nBufferlist now opens at the very top with maximum width. \r\n\r\nFixed an issue with the 'g' navigation command","package":"buffet.vim","4":"buffet.vim","src_id":"17277","5":"17277","creation_date":"1327143732","6":"1327143732"},{"0":"3896","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Some highlighting fixes","3":"Some highlighting fixes","package":"buffet.vim","4":"buffet.vim","src_id":"17270","5":"17270","creation_date":"1327120748","6":"1327120748"}]},"3895":{"script_id":"3895","0":"3895","script_name":"rhinestones","1":"rhinestones","script_type":"color scheme","2":"color scheme","summary":"initial upload","3":"initial upload","description":"Rhinestones is an elegant dark background style colourscheme.\r\nThis colourscheme works both in GUI and 256 colours terminals, although there will be slight differences.\r\n\r\nScreenshots are available here: http:\/\/harnoranaivo.posterous.com\/vim-colourscheme-rhinestones","4":"Rhinestones is an elegant dark background style colourscheme.\r\nThis colourscheme works both in GUI and 256 colours terminals, although there will be slight differences.\r\n\r\nScreenshots are available here: http:\/\/harnoranaivo.posterous.com\/vim-colourscheme-rhinestones","install_details":"Download the script and copy it into your .vim\/colors directory.\r\nUse the following command in Vim to use it ':colorscheme rhinestones'.\r\nTo use it as your default colourscheme, edit your ~\/.vimrc file and add 'colorscheme rhinestones'.","5":"Download the script and copy it into your .vim\/colors directory.\r\nUse the following command in Vim to use it ':colorscheme rhinestones'.\r\nTo use it as your default colourscheme, edit your ~\/.vimrc file and add 'colorscheme rhinestones'.","first_name":"Ranaivoarivony Razanajato","6":"Ranaivoarivony Razanajato","last_name":"Harenome","7":"Harenome","releases":[{"0":"3895","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"rhinestones.vim","4":"rhinestones.vim","src_id":"17259","5":"17259","creation_date":"1326989804","6":"1326989804"}]},"3894":{"script_id":"3894","0":"3894","script_name":"Limbo syntax","1":"Limbo syntax","script_type":"syntax","2":"syntax","summary":"Limbo (OS Inferno's language) syntax highlight","3":"Limbo (OS Inferno's language) syntax highlight","description":"Syntax highlight for programming language Limbo (used with OS Inferno).","4":"Syntax highlight for programming language Limbo (used with OS Inferno).","install_details":"Copy downloaded limbo.vim to ~\/.vim\/syntax\/\r\n\r\nTo autodetect filetype add this to ~\/.vimrc or .vim\/ftdetect\/limbo.vim:\r\nlet g:filetype_m=\"limbo\"\r\nautocmd BufNewFile,BufRead *.[bm]          setf limbo","5":"Copy downloaded limbo.vim to ~\/.vim\/syntax\/\r\n\r\nTo autodetect filetype add this to ~\/.vimrc or .vim\/ftdetect\/limbo.vim:\r\nlet g:filetype_m=\"limbo\"\r\nautocmd BufNewFile,BufRead *.[bm]          setf limbo","first_name":"Alex","6":"Alex","last_name":"Efros","7":"Efros","releases":[{"0":"3894","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"rewrite to support all of limbo syntax","3":"rewrite to support all of limbo syntax","package":"limbo.vim","4":"limbo.vim","src_id":"19168","5":"19168","creation_date":"1355283416","6":"1355283416"},{"0":"3894","vim_version":"7.0","1":"7.0","script_version":"0.5","2":"0.5","version_comment":"Initial upload","3":"Initial upload","package":"limbo.vim","4":"limbo.vim","src_id":"17255","5":"17255","creation_date":"1326970259","6":"1326970259"}]},"3893":{"script_id":"3893","0":"3893","script_name":"viewdoc","1":"viewdoc","script_type":"utility","2":"utility","summary":"Flexible viewer for any documentation (help\/man\/perldoc\/etc.)","3":"Flexible viewer for any documentation (help\/man\/perldoc\/etc.)","description":"Flexible viewer for any documentation source (help\/man\/perldoc\/etc.) for any\r\nfile type inside Vim in easy to use, consistent, smart and configurable way.\r\n\r\n * You can configure how (keys\/commands) documentation will be open.\r\n   By default it will replace standard mapping for key K and command :help\r\n   plus add mapping for <F1> key and new commands :man, :doc, etc.\r\n\r\n * You can configure where (buffer\/window\/tab) documentation will be open.\r\n   Can open new docs in one dedicated (K) or new (<F1>) buffer\/window\/tab. \r\n   Support all work styles:\r\n\r\n   - full screen (no tabs, one window, open files\/docs are in hidden buffers), \r\n   - windowed (no tabs, many windows with open files\/docs), \r\n   - tabbed full screen (many tabs, each with one window, open files\/docs are\r\n     in different tabs), \r\n   - tabbed (many tabs with many windows inside tabs). \r\n\r\n * You can easily navigate to next\/previous topic while viewing documentation\r\n   using <C-]> and <C-T> (or alternative keys <CR> and <BS>), just\r\n   like you use tags for navigation within source code and Vim's help.\r\n\r\n * Even closing documentation buffer\/window\/tab is easier, smarter and more\r\n   configurable than ever before. :)\r\n\r\n * Smart detection of documentation source and topic when opening\r\n   documentation for <cword> (word under cursor) - can use current syntax\r\n   highlight (to find topic's context) and surrounding text (when topic\r\n   doesn't include important special symbols because of 'iskeyword' value).\r\n\r\n * Smart completion for available documentation topics when opening\r\n   documentation using command (just like Vim's :help command works).\r\n   (Some documentation sources may not support this.)\r\n\r\n * Supported documentation sources:\r\n\r\n   - man pages\r\n   - Vim's help\r\n   - custom documentation in vim help format: (CSS 2.1, CMake, LaTeX, \u00e2\u0080\u00a6)\r\n   - perldoc\r\n   - godoc\r\n   - pydoc (python)\r\n   - pman (php)\r\n   - OS Inferno man pages\r\n   - ri (ruby)\r\n   - bash's help\r\n   - GNU info (smart support for: awk, make, m4, automake)\r\n\r\n * Support for new documentation sources and file types can be easily added by\r\n   external plugins or within ~\/.vimrc file.\r\n\r\n * You can have several documentation sources for same file type, and choose\r\n   which one should be used on-the-fly.\r\n\r\n * Can be used as console man page viewer instead of \/usr\/bin\/man.\r\n\r\nTested only in Linux, but should work in any *NIX.\r\n\r\nSource: https:\/\/github.com\/powerman\/vim-plugin-viewdoc","4":"Flexible viewer for any documentation source (help\/man\/perldoc\/etc.) for any\r\nfile type inside Vim in easy to use, consistent, smart and configurable way.\r\n\r\n * You can configure how (keys\/commands) documentation will be open.\r\n   By default it will replace standard mapping for key K and command :help\r\n   plus add mapping for <F1> key and new commands :man, :doc, etc.\r\n\r\n * You can configure where (buffer\/window\/tab) documentation will be open.\r\n   Can open new docs in one dedicated (K) or new (<F1>) buffer\/window\/tab. \r\n   Support all work styles:\r\n\r\n   - full screen (no tabs, one window, open files\/docs are in hidden buffers), \r\n   - windowed (no tabs, many windows with open files\/docs), \r\n   - tabbed full screen (many tabs, each with one window, open files\/docs are\r\n     in different tabs), \r\n   - tabbed (many tabs with many windows inside tabs). \r\n\r\n * You can easily navigate to next\/previous topic while viewing documentation\r\n   using <C-]> and <C-T> (or alternative keys <CR> and <BS>), just\r\n   like you use tags for navigation within source code and Vim's help.\r\n\r\n * Even closing documentation buffer\/window\/tab is easier, smarter and more\r\n   configurable than ever before. :)\r\n\r\n * Smart detection of documentation source and topic when opening\r\n   documentation for <cword> (word under cursor) - can use current syntax\r\n   highlight (to find topic's context) and surrounding text (when topic\r\n   doesn't include important special symbols because of 'iskeyword' value).\r\n\r\n * Smart completion for available documentation topics when opening\r\n   documentation using command (just like Vim's :help command works).\r\n   (Some documentation sources may not support this.)\r\n\r\n * Supported documentation sources:\r\n\r\n   - man pages\r\n   - Vim's help\r\n   - custom documentation in vim help format: (CSS 2.1, CMake, LaTeX, \u00e2\u0080\u00a6)\r\n   - perldoc\r\n   - godoc\r\n   - pydoc (python)\r\n   - pman (php)\r\n   - OS Inferno man pages\r\n   - ri (ruby)\r\n   - bash's help\r\n   - GNU info (smart support for: awk, make, m4, automake)\r\n\r\n * Support for new documentation sources and file types can be easily added by\r\n   external plugins or within ~\/.vimrc file.\r\n\r\n * You can have several documentation sources for same file type, and choose\r\n   which one should be used on-the-fly.\r\n\r\n * Can be used as console man page viewer instead of \/usr\/bin\/man.\r\n\r\nTested only in Linux, but should work in any *NIX.\r\n\r\nSource: https:\/\/github.com\/powerman\/vim-plugin-viewdoc","install_details":"Using pathogen (recommended). \r\na) Using source: \r\n    $ git clone https:\/\/github.com\/powerman\/vim-plugin-viewdoc.git ~\/.vim\/bundle\/viewdoc\/ \r\n    $ vi \r\n    :Helptags \r\nb) Using .zip archive: \r\n    $ mkdir ~\/.vim\/bundle\/viewdoc\/ \r\n    $ unzip viewdoc.zip -d ~\/.vim\/bundle\/viewdoc\/ \r\n    $ vi \r\n    :Helptags \r\nc) Using  .vmb vimball: \r\n    $ mkdir ~\/.vim\/bundle\/viewdoc\/ \r\n    $ vi viewdoc.vmb \r\n    :UseVimball ~\/.vim\/bundle\/viewdoc \r\n    :Helptags \r\n\r\nPlain install without pathogen. \r\na) Using .zip archive: \r\n    $ unzip viewdoc.zip -d ~\/.vim\/ \r\n    $ vi \r\n    :helptags ~\/.vim\/doc \r\nb) Using .vmb vimball: \r\n    $ vi viewdoc.vmb \r\n    :so % \r\n    :helptags ~\/.vim\/doc","5":"Using pathogen (recommended). \r\na) Using source: \r\n    $ git clone https:\/\/github.com\/powerman\/vim-plugin-viewdoc.git ~\/.vim\/bundle\/viewdoc\/ \r\n    $ vi \r\n    :Helptags \r\nb) Using .zip archive: \r\n    $ mkdir ~\/.vim\/bundle\/viewdoc\/ \r\n    $ unzip viewdoc.zip -d ~\/.vim\/bundle\/viewdoc\/ \r\n    $ vi \r\n    :Helptags \r\nc) Using  .vmb vimball: \r\n    $ mkdir ~\/.vim\/bundle\/viewdoc\/ \r\n    $ vi viewdoc.vmb \r\n    :UseVimball ~\/.vim\/bundle\/viewdoc \r\n    :Helptags \r\n\r\nPlain install without pathogen. \r\na) Using .zip archive: \r\n    $ unzip viewdoc.zip -d ~\/.vim\/ \r\n    $ vi \r\n    :helptags ~\/.vim\/doc \r\nb) Using .vmb vimball: \r\n    $ vi viewdoc.vmb \r\n    :so % \r\n    :helptags ~\/.vim\/doc","first_name":"Alex","6":"Alex","last_name":"Efros","7":"Efros","releases":[{"0":"3893","vim_version":"7.0","1":"7.0","script_version":"1.14","2":"1.14","version_comment":"vimball","3":"vimball","package":"viewdoc.vmb","4":"viewdoc.vmb","src_id":"27410","5":"27410","creation_date":"1608536042","6":"1608536042"},{"0":"3893","vim_version":"7.0","1":"7.0","script_version":"1.14","2":"1.14","version_comment":"Improve Windows compatibility for vim help.","3":"Improve Windows compatibility for vim help.","package":"viewdoc.zip","4":"viewdoc.zip","src_id":"27409","5":"27409","creation_date":"1608536024","6":"1608536024"},{"0":"3893","vim_version":"7.0","1":"7.0","script_version":"1.13","2":"1.13","version_comment":"vimball","3":"vimball","package":"viewdoc.vmb","4":"viewdoc.vmb","src_id":"26562","5":"26562","creation_date":"1561328541","6":"1561328541"},{"0":"3893","vim_version":"7.0","1":"7.0","script_version":"1.13","2":"1.13","version_comment":"Update godoc plugin for compatibility with Go 1.12.\r\nFix: restore doc file type on <BS>.","3":"Update godoc plugin for compatibility with Go 1.12.\r\nFix: restore doc file type on <BS>.","package":"viewdoc.zip","4":"viewdoc.zip","src_id":"26561","5":"26561","creation_date":"1561328502","6":"1561328502"},{"0":"3893","vim_version":"7.0","1":"7.0","script_version":"1.12","2":"1.12","version_comment":"vimball","3":"vimball","package":"viewdoc.vmb","4":"viewdoc.vmb","src_id":"26282","5":"26282","creation_date":"1542700159","6":"1542700159"},{"0":"3893","vim_version":"7.0","1":"7.0","script_version":"1.12","2":"1.12","version_comment":"Update godoc plugin for compatibility with Go 1.11.\r\nAdded g:viewdoc_winwidth_max, thanks to @merrilymeredith.\r\nFix neovim compatibility, thanks to @olmokramer.\r\nFix help plugin, thanks to @critiqjo.\r\n","3":"Update godoc plugin for compatibility with Go 1.11.\r\nAdded g:viewdoc_winwidth_max, thanks to @merrilymeredith.\r\nFix neovim compatibility, thanks to @olmokramer.\r\nFix help plugin, thanks to @critiqjo.\r\n","package":"viewdoc.zip","4":"viewdoc.zip","src_id":"26281","5":"26281","creation_date":"1542700134","6":"1542700134"},{"0":"3893","vim_version":"7.0","1":"7.0","script_version":"1.11","2":"1.11","version_comment":"vimball","3":"vimball","package":"viewdoc.vmb","4":"viewdoc.vmb","src_id":"23526","5":"23526","creation_date":"1440053532","6":"1440053532"},{"0":"3893","vim_version":"7.0","1":"7.0","script_version":"1.11","2":"1.11","version_comment":"Improve info plugin, thanks to @critiqjo.","3":"Improve info plugin, thanks to @critiqjo.","package":"viewdoc.zip","4":"viewdoc.zip","src_id":"23525","5":"23525","creation_date":"1440053514","6":"1440053514"},{"0":"3893","vim_version":"7.0","1":"7.0","script_version":"1.10","2":"1.10","version_comment":"vimball","3":"vimball","package":"viewdoc.vmb","4":"viewdoc.vmb","src_id":"23464","5":"23464","creation_date":"1436484907","6":"1436484907"},{"0":"3893","vim_version":"7.0","1":"7.0","script_version":"1.10","2":"1.10","version_comment":"Add Go (golang) support.","3":"Add Go (golang) support.","package":"viewdoc.zip","4":"viewdoc.zip","src_id":"23463","5":"23463","creation_date":"1436484887","6":"1436484887"},{"0":"3893","vim_version":"7.0","1":"7.0","script_version":"1.9","2":"1.9","version_comment":"vimball","3":"vimball","package":"viewdoc.vmb","4":"viewdoc.vmb","src_id":"22166","5":"22166","creation_date":"1404790943","6":"1404790943"},{"0":"3893","vim_version":"7.0","1":"7.0","script_version":"1.9","2":"1.9","version_comment":"Add new handlers:\r\n* Ruby (ri)\r\n* bash's help\r\n* GNU info (smart support for: awk, make, m4, automake)\r\n* LaTeX (help_custom)\r\nPerldoc and Ruby support ANSI (need Improved AnsiEsc plugin).\r\nImprove Python support.\r\nAdded support for multiple documentation providers per filetype.\r\nAdded option to search for the word which is being looked up in the buffer.\r\nMake :h work.\r\nRenamed [Scratch] to [DocN].\r\nAdd b:topic.\r\nAdded {{winwidth}} support in h.cmd (man and perldoc already using it).","3":"Add new handlers:\r\n* Ruby (ri)\r\n* bash's help\r\n* GNU info (smart support for: awk, make, m4, automake)\r\n* LaTeX (help_custom)\r\nPerldoc and Ruby support ANSI (need Improved AnsiEsc plugin).\r\nImprove Python support.\r\nAdded support for multiple documentation providers per filetype.\r\nAdded option to search for the word which is being looked up in the buffer.\r\nMake :h work.\r\nRenamed [Scratch] to [DocN].\r\nAdd b:topic.\r\nAdded {{winwidth}} support in h.cmd (man and perldoc already using it).","package":"viewdoc.zip","4":"viewdoc.zip","src_id":"22165","5":"22165","creation_date":"1404790920","6":"1404790920"},{"0":"3893","vim_version":"7.0","1":"7.0","script_version":"1.8.1","2":"1.8.1","version_comment":"vimball","3":"vimball","package":"viewdoc.vmb","4":"viewdoc.vmb","src_id":"21898","5":"21898","creation_date":"1400241539","6":"1400241539"},{"0":"3893","vim_version":"7.0","1":"7.0","script_version":"1.8.1","2":"1.8.1","version_comment":"fix compatibility with vim-7.3","3":"fix compatibility with vim-7.3","package":"viewdoc.zip","4":"viewdoc.zip","src_id":"21897","5":"21897","creation_date":"1400241518","6":"1400241518"},{"0":"3893","vim_version":"7.0","1":"7.0","script_version":"1.8","2":"1.8","version_comment":"vimball","3":"vimball","package":"viewdoc.vmb","4":"viewdoc.vmb","src_id":"21830","5":"21830","creation_date":"1398439391","6":"1398439391"},{"0":"3893","vim_version":"7.0","1":"7.0","script_version":"1.8","2":"1.8","version_comment":"fix compatibility with vim-7.4.260","3":"fix compatibility with vim-7.4.260","package":"viewdoc.zip","4":"viewdoc.zip","src_id":"21829","5":"21829","creation_date":"1398439359","6":"1398439359"},{"0":"3893","vim_version":"7.0","1":"7.0","script_version":"1.7","2":"1.7","version_comment":"vimball","3":"vimball","package":"viewdoc.vmb","4":"viewdoc.vmb","src_id":"21111","5":"21111","creation_date":"1385432543","6":"1385432543"},{"0":"3893","vim_version":"7.0","1":"7.0","script_version":"1.7","2":"1.7","version_comment":"improve compatibility with windows and *bsd","3":"improve compatibility with windows and *bsd","package":"viewdoc.zip","4":"viewdoc.zip","src_id":"21110","5":"21110","creation_date":"1385432514","6":"1385432514"},{"0":"3893","vim_version":"7.0","1":"7.0","script_version":"1.6","2":"1.6","version_comment":"vimball","3":"vimball","package":"viewdoc.vmb","4":"viewdoc.vmb","src_id":"20595","5":"20595","creation_date":"1375477013","6":"1375477013"},{"0":"3893","vim_version":"7.0","1":"7.0","script_version":"1.6","2":"1.6","version_comment":"minor bugfixes","3":"minor bugfixes","package":"viewdoc.zip","4":"viewdoc.zip","src_id":"20594","5":"20594","creation_date":"1375476996","6":"1375476996"},{"0":"3893","vim_version":"7.0","1":"7.0","script_version":"1.5","2":"1.5","version_comment":"vimball","3":"vimball","package":"viewdoc.vmb","4":"viewdoc.vmb","src_id":"19041","5":"19041","creation_date":"1353971744","6":"1353971744"},{"0":"3893","vim_version":"7.0","1":"7.0","script_version":"1.5","2":"1.5","version_comment":"added plugin for OS Inferno man pages","3":"added plugin for OS Inferno man pages","package":"viewdoc.zip","4":"viewdoc.zip","src_id":"19040","5":"19040","creation_date":"1353971728","6":"1353971728"},{"0":"3893","vim_version":"7.0","1":"7.0","script_version":"1.4","2":"1.4","version_comment":"vimball","3":"vimball","package":"viewdoc.vmb","4":"viewdoc.vmb","src_id":"19039","5":"19039","creation_date":"1353950311","6":"1353950311"},{"0":"3893","vim_version":"7.0","1":"7.0","script_version":"1.4","2":"1.4","version_comment":"Added PHP (pman) support.\r\nPython (pydoc) plugin now provide :pydoc command with autocomplete.\r\nUsed pydoc command now configurable (to choose python 2 or 3 docs).\r\nOther minor improvements.","3":"Added PHP (pman) support.\r\nPython (pydoc) plugin now provide :pydoc command with autocomplete.\r\nUsed pydoc command now configurable (to choose python 2 or 3 docs).\r\nOther minor improvements.","package":"viewdoc.zip","4":"viewdoc.zip","src_id":"19038","5":"19038","creation_date":"1353950280","6":"1353950280"},{"0":"3893","vim_version":"7.0","1":"7.0","script_version":"1.3","2":"1.3","version_comment":"vimball","3":"vimball","package":"viewdoc.vmb","4":"viewdoc.vmb","src_id":"17929","5":"17929","creation_date":"1336733926","6":"1336733926"},{"0":"3893","vim_version":"7.0","1":"7.0","script_version":"1.3","2":"1.3","version_comment":"minor bugfixes and improvements","3":"minor bugfixes and improvements","package":"viewdoc.zip","4":"viewdoc.zip","src_id":"17928","5":"17928","creation_date":"1336733910","6":"1336733910"},{"0":"3893","vim_version":"7.0","1":"7.0","script_version":"1.2","2":"1.2","version_comment":"vimball","3":"vimball","package":"viewdoc.vmb","4":"viewdoc.vmb","src_id":"17264","5":"17264","creation_date":"1327056280","6":"1327056280"},{"0":"3893","vim_version":"7.0","1":"7.0","script_version":"1.2","2":"1.2","version_comment":"added smart detection for help handler\r\nadded smart detection for perl handler\r\nimplement autocomplete for :perldoc\r\nadded ftplugins for vim,help,perl,perldoc\r\n","3":"added smart detection for help handler\r\nadded smart detection for perl handler\r\nimplement autocomplete for :perldoc\r\nadded ftplugins for vim,help,perl,perldoc\r\n","package":"viewdoc.zip","4":"viewdoc.zip","src_id":"17263","5":"17263","creation_date":"1327056250","6":"1327056250"},{"0":"3893","vim_version":"7.0","1":"7.0","script_version":"1.1","2":"1.1","version_comment":"vimball","3":"vimball","package":"viewdoc.vmb","4":"viewdoc.vmb","src_id":"17258","5":"17258","creation_date":"1326989727","6":"1326989727"},{"0":"3893","vim_version":"7.0","1":"7.0","script_version":"1.1","2":"1.1","version_comment":"significantly improve docs\r\nadded g:viewdoc_dontswitch\r\nadded g:viewdoc_openempty\r\nfew minor fixes","3":"significantly improve docs\r\nadded g:viewdoc_dontswitch\r\nadded g:viewdoc_openempty\r\nfew minor fixes","package":"viewdoc.zip","4":"viewdoc.zip","src_id":"17257","5":"17257","creation_date":"1326989713","6":"1326989713"},{"0":"3893","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"vimball","3":"vimball","package":"viewdoc.vmb","4":"viewdoc.vmb","src_id":"17253","5":"17253","creation_date":"1326923583","6":"1326923583"},{"0":"3893","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"viewdoc.zip","4":"viewdoc.zip","src_id":"17252","5":"17252","creation_date":"1326923546","6":"1326923546"}]},"3892":{"script_id":"3892","0":"3892","script_name":"gf-diff","1":"gf-diff","script_type":"utility","2":"utility","summary":"Go to a hunk from diff output","3":"Go to a hunk from diff output","description":"*gf-diff* is a Vim plugin to extend |gf| and other commands.  With this\nplugin, you can open the file and locate the cursor to a comfortable position\nfrom the hunk of a diff output under the cursor.  It is useful whenever you\nreview patches and uncommitted changes in Vim.\n\nSuppose that the current buffer contains the following text (here the most\nleft numbers are line numbers):\n\n\t 1 diff --git a\/autoload\/gf\/diff.vim b\/autoload\/gf\/diff.vim\n\t 2 index 469fdb3..b135316 100644\n\t 3 --- a\/autoload\/gf\/diff.vim\n\t 4 +++ b\/autoload\/gf\/diff.vim\n\t 5 @@ -21,7 +22,7 @@\n\t 6  \"     SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.\n\t 7  \"\n\t 8  \" Interface\n\t 9 -function! gf#diff#go_to_hunk(type)\n\t10 +function! gf#diff#go(type)\n\t11    let d = gf#diff#investigate_the_hunk_under_the_cursor()\n\t12    if d is 0\n\t13      echomsg 'There is no diff hunk to jump.'\n\t14 @@ -113,7 +114,7 @@ function! gf#diff#investigate_the_hunk_under_the_c\n\t15        return 0\n\t16      endif\n\t17      let [d.from_path, d.to_path] = xs\n\t18 +  call setpos('.', original_position)\n\t19 -  call setpos(original_position)\n\t20\n\t21    return d\n\t22  endfunction\n\nIf you type |gf| on the 12th line and there is no file whose name is under the\ncursor, \"autoload\/gf\/diff.vim\" will be opened and the cursor will be moved to\nthe 25th line of the file.  Because the hunk under the cursor represents the\nfile and the position.\n\n\nRequirements:\n- Vim 7.3 or later\n- |gf-user| 0.0.0 or later\n  (vimscript#3891, http:\/\/github.com\/kana\/vim-gf-user)\n\nLatest version:\nhttp:\/\/github.com\/kana\/vim-gf-diff\n\nDocument in HTML format:\nhttp:\/\/kana.github.com\/config\/vim\/gf-diff.html","4":"*gf-diff* is a Vim plugin to extend |gf| and other commands.  With this\nplugin, you can open the file and locate the cursor to a comfortable position\nfrom the hunk of a diff output under the cursor.  It is useful whenever you\nreview patches and uncommitted changes in Vim.\n\nSuppose that the current buffer contains the following text (here the most\nleft numbers are line numbers):\n\n\t 1 diff --git a\/autoload\/gf\/diff.vim b\/autoload\/gf\/diff.vim\n\t 2 index 469fdb3..b135316 100644\n\t 3 --- a\/autoload\/gf\/diff.vim\n\t 4 +++ b\/autoload\/gf\/diff.vim\n\t 5 @@ -21,7 +22,7 @@\n\t 6  \"     SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.\n\t 7  \"\n\t 8  \" Interface\n\t 9 -function! gf#diff#go_to_hunk(type)\n\t10 +function! gf#diff#go(type)\n\t11    let d = gf#diff#investigate_the_hunk_under_the_cursor()\n\t12    if d is 0\n\t13      echomsg 'There is no diff hunk to jump.'\n\t14 @@ -113,7 +114,7 @@ function! gf#diff#investigate_the_hunk_under_the_c\n\t15        return 0\n\t16      endif\n\t17      let [d.from_path, d.to_path] = xs\n\t18 +  call setpos('.', original_position)\n\t19 -  call setpos(original_position)\n\t20\n\t21    return d\n\t22  endfunction\n\nIf you type |gf| on the 12th line and there is no file whose name is under the\ncursor, \"autoload\/gf\/diff.vim\" will be opened and the cursor will be moved to\nthe 25th line of the file.  Because the hunk under the cursor represents the\nfile and the position.\n\n\nRequirements:\n- Vim 7.3 or later\n- |gf-user| 0.0.0 or later\n  (vimscript#3891, http:\/\/github.com\/kana\/vim-gf-user)\n\nLatest version:\nhttp:\/\/github.com\/kana\/vim-gf-diff\n\nDocument in HTML format:\nhttp:\/\/kana.github.com\/config\/vim\/gf-diff.html","install_details":"...","5":"...","first_name":"Kana","6":"Kana","last_name":"Natsuno","7":"Natsuno","releases":[{"0":"3892","vim_version":"7.0","1":"7.0","script_version":"0.1.1","2":"0.1.1","version_comment":"Initial upload","3":"Initial upload","package":"vim-gf-diff-0.1.1.zip","4":"vim-gf-diff-0.1.1.zip","src_id":"17245","5":"17245","creation_date":"1326886947","6":"1326886947"}]},"3891":{"script_id":"3891","0":"3891","script_name":"gf-user","1":"gf-user","script_type":"utility","2":"utility","summary":"A framework to open a file by context","3":"A framework to open a file by context","description":"*gf-user* is a Vim plugin to provide a framwork to extend |gf|.  Though |gf|\nis one of the most useful commands in Vim, it has the following problems:\n\n- The file to be opened is based on the word under the cursor.\n- It's not possible to specify the cursor position for the opened file.\n\nSometimes you might wish |gf| used more text around the cursor to detect the\nfile to be opened and the initial cursor position.  For example,\n\n- While reading output from diff(1), go to the hunk under the cursor.\n- While editing files for an MVC framework, go to the view file corresponding\n  to an action of the controller under the cursor. \n\nThough it's not hard to implement each extension, it's a bit troublesome to\nsynthesize all extensions.  |gf-user| provides a framework for the extensions.\n\n\nRequirements:\n- Vim 7.3 or later\n\nLatest version:\nhttp:\/\/github.com\/kana\/vim-gf-user\n\nDocument in HTML format:\nhttp:\/\/kana.github.com\/config\/vim\/gf-user.html","4":"*gf-user* is a Vim plugin to provide a framwork to extend |gf|.  Though |gf|\nis one of the most useful commands in Vim, it has the following problems:\n\n- The file to be opened is based on the word under the cursor.\n- It's not possible to specify the cursor position for the opened file.\n\nSometimes you might wish |gf| used more text around the cursor to detect the\nfile to be opened and the initial cursor position.  For example,\n\n- While reading output from diff(1), go to the hunk under the cursor.\n- While editing files for an MVC framework, go to the view file corresponding\n  to an action of the controller under the cursor. \n\nThough it's not hard to implement each extension, it's a bit troublesome to\nsynthesize all extensions.  |gf-user| provides a framework for the extensions.\n\n\nRequirements:\n- Vim 7.3 or later\n\nLatest version:\nhttp:\/\/github.com\/kana\/vim-gf-user\n\nDocument in HTML format:\nhttp:\/\/kana.github.com\/config\/vim\/gf-user.html","install_details":"...","5":"...","first_name":"Kana","6":"Kana","last_name":"Natsuno","7":"Natsuno","releases":[{"0":"3891","vim_version":"7.0","1":"7.0","script_version":"0.0.0","2":"0.0.0","version_comment":"Initial upload","3":"Initial upload","package":"vim-gf-user-0.0.0.zip","4":"vim-gf-user-0.0.0.zip","src_id":"17244","5":"17244","creation_date":"1326886767","6":"1326886767"}]},"3890":{"script_id":"3890","0":"3890","script_name":"simple-dark","1":"simple-dark","script_type":"color scheme","2":"color scheme","summary":"A low contrast, low distraction, dark 256 color scheme","3":"A low contrast, low distraction, dark 256 color scheme","description":"This is a dark 256 color scheme with mild contrast and not so many colors. It is good for prolonged coding. This scheme is inspaired by Lucius (vimscript #2536).\r\n\r\nPlease use the Github repo, where the script will be updated: https:\/\/github.com\/zefei\/simple-dark\r\n\r\nScreenshots:                                                                   \r\nJava: http:\/\/imgur.com\/KE7aL\r\nC: http:\/\/imgur.com\/K5G5V\r\nJavascript with nerdtree: http:\/\/imgur.com\/lSXx2\r\nRuby with tagbar: http:\/\/imgur.com\/NzPwu","4":"This is a dark 256 color scheme with mild contrast and not so many colors. It is good for prolonged coding. This scheme is inspaired by Lucius (vimscript #2536).\r\n\r\nPlease use the Github repo, where the script will be updated: https:\/\/github.com\/zefei\/simple-dark\r\n\r\nScreenshots:                                                                   \r\nJava: http:\/\/imgur.com\/KE7aL\r\nC: http:\/\/imgur.com\/K5G5V\r\nJavascript with nerdtree: http:\/\/imgur.com\/lSXx2\r\nRuby with tagbar: http:\/\/imgur.com\/NzPwu","install_details":"Copy the file to your vim colors directory and then do :color simple-dark.","5":"Copy the file to your vim colors directory and then do :color simple-dark.","first_name":"Zefei","6":"Zefei","last_name":"Xuan","7":"Xuan","releases":[{"0":"3890","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"simple-dark.vim","4":"simple-dark.vim","src_id":"17243","5":"17243","creation_date":"1326877693","6":"1326877693"}]},"3889":{"script_id":"3889","0":"3889","script_name":"switch buffer quickly","1":"switch buffer quickly","script_type":"utility","2":"utility","summary":"A simple way to switch buffer quickly ","3":"A simple way to switch buffer quickly ","description":"A simple way to switch buffer quickly .\r\n\r\nit may be very helpful if you often need to switch buffer in a lot of buffers.\r\n\r\n1. basic usage\r\n\r\n:e a.txt\r\n:w\r\nza\r\n\r\n:e b.txt\r\n:w\r\nza\r\n\r\n:e c.txt\r\n:w\r\nza\r\n\r\npress <c-j> or <c-k> then you can switch buffer in the list that contain a.txt , b.txt , c.txt. \r\n\r\n2. group the buffer list\r\n\r\nwhen you open a new tab page , you will switch to another group automatic , the number of group is the number of tab page number . that mean you can manage multiple buffer list\r\n\r\n3. edit your .vimrc like this:\r\n\r\nnnoremap za :call SBQ_PushBuffer()<cr>                     # add current buffer to buffer list\r\nnnoremap zd :call SBQ_PopBuffer()<cr>                      # delete current buffer from buffer list\r\nnnoremap zs :call SBQ_ShowBufferList()<cr>                 # show the list of buffer list\r\nnnoremap <c-j> :call SBQ_SelectBuffer(1)<cr>               # switch buffer\r\nnnoremap <c-k> :call SBQ_SelectBuffer(2)<cr>               # switch buffer\r\n","4":"A simple way to switch buffer quickly .\r\n\r\nit may be very helpful if you often need to switch buffer in a lot of buffers.\r\n\r\n1. basic usage\r\n\r\n:e a.txt\r\n:w\r\nza\r\n\r\n:e b.txt\r\n:w\r\nza\r\n\r\n:e c.txt\r\n:w\r\nza\r\n\r\npress <c-j> or <c-k> then you can switch buffer in the list that contain a.txt , b.txt , c.txt. \r\n\r\n2. group the buffer list\r\n\r\nwhen you open a new tab page , you will switch to another group automatic , the number of group is the number of tab page number . that mean you can manage multiple buffer list\r\n\r\n3. edit your .vimrc like this:\r\n\r\nnnoremap za :call SBQ_PushBuffer()<cr>                     # add current buffer to buffer list\r\nnnoremap zd :call SBQ_PopBuffer()<cr>                      # delete current buffer from buffer list\r\nnnoremap zs :call SBQ_ShowBufferList()<cr>                 # show the list of buffer list\r\nnnoremap <c-j> :call SBQ_SelectBuffer(1)<cr>               # switch buffer\r\nnnoremap <c-k> :call SBQ_SelectBuffer(2)<cr>               # switch buffer\r\n","install_details":"copy switchBufferQuickly.vim to ~\/.vim\/plugin\r\n","5":"copy switchBufferQuickly.vim to ~\/.vim\/plugin\r\n","first_name":"dong","6":"dong","last_name":"hongbo","7":"hongbo","releases":[{"0":"3889","vim_version":"7.0","1":"7.0","script_version":"0.01","2":"0.01","version_comment":"Initial upload","3":"Initial upload","package":"selectBufferQuickly.vim","4":"selectBufferQuickly.vim","src_id":"17242","5":"17242","creation_date":"1326867311","6":"1326867311"}]},"3888":{"script_id":"3888","0":"3888","script_name":"qtpy.vim","1":"qtpy.vim","script_type":"ftplugin","2":"ftplugin","summary":"Quick unit testing for python from within VIM","3":"Quick unit testing for python from within VIM","description":"A simple way of running python unit tests from within VIM based on the cursor location.\r\n\r\nUseful for receiving immediate feedback as you write tests, despite what test runner or framework your project uses to run its tests.\r\n\r\nqtpy.vim on Github: https:\/\/github.com\/ameade\/qtpy-vim","4":"A simple way of running python unit tests from within VIM based on the cursor location.\r\n\r\nUseful for receiving immediate feedback as you write tests, despite what test runner or framework your project uses to run its tests.\r\n\r\nqtpy.vim on Github: https:\/\/github.com\/ameade\/qtpy-vim","install_details":"Just copy the plugin folders into your ~\/.vim directory.\r\nAlternatively, if you are using pathogen, clone the plugin into your bundle folder.\r\n\r\nIf planning on running tests with something other than python-nose, please use your .vimrc to configure the plugin. See README","5":"Just copy the plugin folders into your ~\/.vim directory.\r\nAlternatively, if you are using pathogen, clone the plugin into your bundle folder.\r\n\r\nIf planning on running tests with something other than python-nose, please use your .vimrc to configure the plugin. See README","first_name":"Alex","6":"Alex","last_name":"Meade","7":"Meade","releases":[{"0":"3888","vim_version":"7.0","1":"7.0","script_version":"0.5.0","2":"0.5.0","version_comment":"Minor doc cleanup\r\nRemove crud and unusable commands","3":"Minor doc cleanup\r\nRemove crud and unusable commands","package":"qtpy-vim0.5.0.zip","4":"qtpy-vim0.5.0.zip","src_id":"20735","5":"20735","creation_date":"1377913001","6":"1377913001"},{"0":"3888","vim_version":"7.0","1":"7.0","script_version":"0.4.2","2":"0.4.2","version_comment":"Initial upload","3":"Initial upload","package":"qtpy-vim0.4.2.zip","4":"qtpy-vim0.4.2.zip","src_id":"17239","5":"17239","creation_date":"1326829117","6":"1326829117"}]},"3887":{"script_id":"3887","0":"3887","script_name":"Independence","1":"Independence","script_type":"utility","2":"utility","summary":"Automatically loads .vimrc files in your git project root","3":"Automatically loads .vimrc files in your git project root","description":"Independence is a plugin to automatically load project-specific .vimrc files.\r\n\r\nFor the latest version, to report a problem, or contact the author please visit https:\/\/github.com\/AD7six\/vim-independence","4":"Independence is a plugin to automatically load project-specific .vimrc files.\r\n\r\nFor the latest version, to report a problem, or contact the author please visit https:\/\/github.com\/AD7six\/vim-independence","install_details":"save independence.vim to your vim\/plugin dir. ","5":"save independence.vim to your vim\/plugin dir. ","first_name":"Andy","6":"Andy","last_name":"Dawson","7":"Dawson","releases":[{"0":"3887","vim_version":"7.0","1":"7.0","script_version":"0.1.0","2":"0.1.0","version_comment":"Initial upload","3":"Initial upload","package":"independence.vim","4":"independence.vim","src_id":"17227","5":"17227","creation_date":"1326718767","6":"1326718767"}]},"3886":{"script_id":"3886","0":"3886","script_name":"textobj-line","1":"textobj-line","script_type":"utility","2":"utility","summary":"Text objects for the current line","3":"Text objects for the current line","description":"*textobj-line* is a Vim plugin to provide text objects to select a portion of\nthe current line.  Sometimes you want to select a portion of the current line\nlike \"^vg_\" or \"0v$h\".  This plugin provides the text objects for such ranges.\n\nFor example, if the current line equals to \"__foo_bar_baz__\" (where \"_\"\nrepresents a whitespace character), you can select \"foo_bar_baz\" (without\nleading and trailing spaces) by |<Plug>(textobj-line-i)| and \"__foo_bar_baz__\"\n(with leading and trailing spaces) by |<Plug>(textobj-line-a)|.\n\n\nRequirements:\n- Vim 7.2 or later\n- |textobj-user| 0.3.8 or later (vimscript#2100)\n\nLatest version:\nhttp:\/\/github.com\/kana\/vim-textobj-line\n\nDocument in HTML format:\nhttp:\/\/kana.github.com\/config\/vim\/textobj-line.html","4":"*textobj-line* is a Vim plugin to provide text objects to select a portion of\nthe current line.  Sometimes you want to select a portion of the current line\nlike \"^vg_\" or \"0v$h\".  This plugin provides the text objects for such ranges.\n\nFor example, if the current line equals to \"__foo_bar_baz__\" (where \"_\"\nrepresents a whitespace character), you can select \"foo_bar_baz\" (without\nleading and trailing spaces) by |<Plug>(textobj-line-i)| and \"__foo_bar_baz__\"\n(with leading and trailing spaces) by |<Plug>(textobj-line-a)|.\n\n\nRequirements:\n- Vim 7.2 or later\n- |textobj-user| 0.3.8 or later (vimscript#2100)\n\nLatest version:\nhttp:\/\/github.com\/kana\/vim-textobj-line\n\nDocument in HTML format:\nhttp:\/\/kana.github.com\/config\/vim\/textobj-line.html","install_details":"...","5":"...","first_name":"Kana","6":"Kana","last_name":"Natsuno","7":"Natsuno","releases":[{"0":"3886","vim_version":"7.0","1":"7.0","script_version":"0.0.0","2":"0.0.0","version_comment":"Initial upload","3":"Initial upload","package":"vim-textobj-line-0.0.0.zip","4":"vim-textobj-line-0.0.0.zip","src_id":"17226","5":"17226","creation_date":"1326718140","6":"1326718140"}]},"3885":{"script_id":"3885","0":"3885","script_name":"ruscmd","1":"ruscmd","script_type":"utility","2":"utility","summary":"Support command mode in Russian keyboard layout","3":"Support command mode in Russian keyboard layout","description":"This plugin will let you enter command mode (NORMAL) commands using Russian keyboard layout. Also it will let you enter few most used commands in command line mode in safe way (only full commands translated). This is usually enough to avoid switching between Russian and English layouts just to control Vim.\r\n\r\nWorks only with Unicode.\r\n\r\nSource: https:\/\/github.com\/powerman\/vim-plugin-ruscmd","4":"This plugin will let you enter command mode (NORMAL) commands using Russian keyboard layout. Also it will let you enter few most used commands in command line mode in safe way (only full commands translated). This is usually enough to avoid switching between Russian and English layouts just to control Vim.\r\n\r\nWorks only with Unicode.\r\n\r\nSource: https:\/\/github.com\/powerman\/vim-plugin-ruscmd","install_details":"Using pathogen (recommended). \r\na) Using source: \r\n    $ git clone https:\/\/github.com\/powerman\/vim-plugin-ruscmd.git ~\/.vim\/bundle\/ruscmd\/\r\nb) Using .zip archive: \r\n    $ mkdir ~\/.vim\/bundle\/ruscmd\/ \r\n    $ unzip ruscmd.zip -d ~\/.vim\/bundle\/ruscmd\/ \r\nc) Using  .vmb vimball: \r\n    $ mkdir ~\/.vim\/bundle\/ruscmd\/ \r\n    $ vi ruscmd.vmb \r\n    :UseVimball ~\/.vim\/bundle\/ruscmd \r\n\r\nPlain install without pathogen. \r\na) Using .zip archive: \r\n    $ unzip ruscmd.zip -d ~\/.vim\/ \r\nb) Using .vmb vimball: \r\n    $ vi ruscmd.vmb \r\n    :so % ","5":"Using pathogen (recommended). \r\na) Using source: \r\n    $ git clone https:\/\/github.com\/powerman\/vim-plugin-ruscmd.git ~\/.vim\/bundle\/ruscmd\/\r\nb) Using .zip archive: \r\n    $ mkdir ~\/.vim\/bundle\/ruscmd\/ \r\n    $ unzip ruscmd.zip -d ~\/.vim\/bundle\/ruscmd\/ \r\nc) Using  .vmb vimball: \r\n    $ mkdir ~\/.vim\/bundle\/ruscmd\/ \r\n    $ vi ruscmd.vmb \r\n    :UseVimball ~\/.vim\/bundle\/ruscmd \r\n\r\nPlain install without pathogen. \r\na) Using .zip archive: \r\n    $ unzip ruscmd.zip -d ~\/.vim\/ \r\nb) Using .vmb vimball: \r\n    $ vi ruscmd.vmb \r\n    :so % ","first_name":"Alex","6":"Alex","last_name":"Efros","7":"Efros","releases":[{"0":"3885","vim_version":"7.0","1":"7.0","script_version":"1.4","2":"1.4","version_comment":"vimball","3":"vimball","package":"ruscmd.vmb","4":"ruscmd.vmb","src_id":"20908","5":"20908","creation_date":"1381489323","6":"1381489323"},{"0":"3885","vim_version":"7.0","1":"7.0","script_version":"1.4","2":"1.4","version_comment":"Add support for multi-key combinations (like ZZ).","3":"Add support for multi-key combinations (like ZZ).","package":"ruscmd.zip","4":"ruscmd.zip","src_id":"20907","5":"20907","creation_date":"1381489310","6":"1381489310"},{"0":"3885","vim_version":"7.0","1":"7.0","script_version":"1.3","2":"1.3","version_comment":"vimball","3":"vimball","package":"ruscmd.vmb","4":"ruscmd.vmb","src_id":"17248","5":"17248","creation_date":"1326896814","6":"1326896814"},{"0":"3885","vim_version":"7.0","1":"7.0","script_version":"1.3","2":"1.3","version_comment":"fix abbrev to work only in command line","3":"fix abbrev to work only in command line","package":"ruscmd.zip","4":"ruscmd.zip","src_id":"17247","5":"17247","creation_date":"1326896792","6":"1326896792"},{"0":"3885","vim_version":"7.0","1":"7.0","script_version":"1.2","2":"1.2","version_comment":"vimball","3":"vimball","package":"ruscmd.vmb","4":"ruscmd.vmb","src_id":"17238","5":"17238","creation_date":"1326821950","6":"1326821950"},{"0":"3885","vim_version":"7.0","1":"7.0","script_version":"1.2","2":"1.2","version_comment":"replace cmap with cabbrev; add ability to disable abbrev and\/or maps","3":"replace cmap with cabbrev; add ability to disable abbrev and\/or maps","package":"ruscmd.zip","4":"ruscmd.zip","src_id":"17237","5":"17237","creation_date":"1326821918","6":"1326821918"},{"0":"3885","vim_version":"7.0","1":"7.0","script_version":"1.1","2":"1.1","version_comment":"vimball","3":"vimball","package":"ruscmd.vmb","4":"ruscmd.vmb","src_id":"17224","5":"17224","creation_date":"1326649124","6":"1326649124"},{"0":"3885","vim_version":"7.0","1":"7.0","script_version":"1.1","2":"1.1","version_comment":"initial upload","3":"initial upload","package":"ruscmd.zip","4":"ruscmd.zip","src_id":"17223","5":"17223","creation_date":"1326649106","6":"1326649106"}]},"3884":{"script_id":"3884","0":"3884","script_name":"DfrankUtil","1":"DfrankUtil","script_type":"utility","2":"utility","summary":"Just a library for some scripts.","3":"Just a library for some scripts.","description":"Just a library for some scripts.\r\n\r\nYou don't need to download it if you haven't plugins depending on DfrankUtil.\r\nNow there's two plugins that depend on this library:\r\n*) Indexer (vimscript #3221)\r\n*) Vimprj (vimscript #3872)","4":"Just a library for some scripts.\r\n\r\nYou don't need to download it if you haven't plugins depending on DfrankUtil.\r\nNow there's two plugins that depend on this library:\r\n*) Indexer (vimscript #3221)\r\n*) Vimprj (vimscript #3872)","install_details":"Use pathogen. (vimscript #2332)","5":"Use pathogen. (vimscript #2332)","first_name":"Dmitry","6":"Dmitry","last_name":"Frank","7":"Frank","releases":[{"0":"3884","vim_version":"7.0","1":"7.0","script_version":"1.02","2":"1.02","version_comment":"*) Bugfix. If you have plugins depending on this script (Indexer or Vimprj), then please update","3":"*) Bugfix. If you have plugins depending on this script (Indexer or Vimprj), then please update","package":"dfrank_util-1.02.zip","4":"dfrank_util-1.02.zip","src_id":"17363","5":"17363","creation_date":"1328120428","6":"1328120428"},{"0":"3884","vim_version":"7.0","1":"7.0","script_version":"1.01","2":"1.01","version_comment":"*) Fixed a little bug","3":"*) Fixed a little bug","package":"dfrank_util-1.01.tar.gz","4":"dfrank_util-1.01.tar.gz","src_id":"17278","5":"17278","creation_date":"1327150705","6":"1327150705"},{"0":"3884","vim_version":"7.0","1":"7.0","script_version":"1.00","2":"1.00","version_comment":"Initial upload","3":"Initial upload","package":"dfrank_util-1.00.tar.gz","4":"dfrank_util-1.00.tar.gz","src_id":"17218","5":"17218","creation_date":"1326644374","6":"1326644374"}]},"3883":{"script_id":"3883","0":"3883","script_name":"autosess","1":"autosess","script_type":"utility","2":"utility","summary":"Auto save\/load sessions","3":"Auto save\/load sessions","description":"Start Vim without file arguments to automatically load previous session for current directory. This make easier work with complex projects - just chdir to project directory and start `vim`.\r\n\r\nWhen you quit from Vim, if there are more than one open tab\/window, session will be automatically saved. This let you edit single files in same directory without breaking your saved session. (Quickfix and vimdiff's windows are ignored.)\r\n\r\nIf you quit from Vim with no open files, session will be deleted. This let you start usual empty Vim in this directory next time.\r\n\r\nSource: https:\/\/github.com\/powerman\/vim-plugin-autosess","4":"Start Vim without file arguments to automatically load previous session for current directory. This make easier work with complex projects - just chdir to project directory and start `vim`.\r\n\r\nWhen you quit from Vim, if there are more than one open tab\/window, session will be automatically saved. This let you edit single files in same directory without breaking your saved session. (Quickfix and vimdiff's windows are ignored.)\r\n\r\nIf you quit from Vim with no open files, session will be deleted. This let you start usual empty Vim in this directory next time.\r\n\r\nSource: https:\/\/github.com\/powerman\/vim-plugin-autosess","install_details":"Using pathogen (recommended).\r\na) Using source:\r\n    $ git clone https:\/\/github.com\/powerman\/vim-plugin-autosess.git ~\/.vim\/bundle\/autosess\/\r\n    $ vi\r\n    :Helptags\r\nb) Using .zip archive:\r\n    $ mkdir ~\/.vim\/bundle\/autosess\/\r\n    $ unzip autosess.zip -d ~\/.vim\/bundle\/autosess\/\r\n    $ vi\r\n    :Helptags\r\nc) Using  .vmb vimball:\r\n    $ mkdir ~\/.vim\/bundle\/autosess\/\r\n    $ vi autosess.vmb\r\n    :UseVimball ~\/.vim\/bundle\/autosess\r\n    :Helptags\r\n\r\nPlain install without pathogen.\r\na) Using .zip archive:\r\n    $ unzip autosess.zip -d ~\/.vim\/\r\n    $ vi\r\n    :helptags ~\/.vim\/doc\r\nb) Using .vmb vimball:\r\n    $ vi autosess.vmb\r\n    :so %\r\n    :helptags ~\/.vim\/doc\r\n","5":"Using pathogen (recommended).\r\na) Using source:\r\n    $ git clone https:\/\/github.com\/powerman\/vim-plugin-autosess.git ~\/.vim\/bundle\/autosess\/\r\n    $ vi\r\n    :Helptags\r\nb) Using .zip archive:\r\n    $ mkdir ~\/.vim\/bundle\/autosess\/\r\n    $ unzip autosess.zip -d ~\/.vim\/bundle\/autosess\/\r\n    $ vi\r\n    :Helptags\r\nc) Using  .vmb vimball:\r\n    $ mkdir ~\/.vim\/bundle\/autosess\/\r\n    $ vi autosess.vmb\r\n    :UseVimball ~\/.vim\/bundle\/autosess\r\n    :Helptags\r\n\r\nPlain install without pathogen.\r\na) Using .zip archive:\r\n    $ unzip autosess.zip -d ~\/.vim\/\r\n    $ vi\r\n    :helptags ~\/.vim\/doc\r\nb) Using .vmb vimball:\r\n    $ vi autosess.vmb\r\n    :so %\r\n    :helptags ~\/.vim\/doc\r\n","first_name":"Alex","6":"Alex","last_name":"Efros","7":"Efros","releases":[{"0":"3883","vim_version":"7.0","1":"7.0","script_version":"1.2.3","2":"1.2.3","version_comment":"vimball","3":"vimball","package":"autosess.vmb","4":"autosess.vmb","src_id":"25665","5":"25665","creation_date":"1511877310","6":"1511877310"},{"0":"3883","vim_version":"7.0","1":"7.0","script_version":"1.2.3","2":"1.2.3","version_comment":"Improved vim compatibility.","3":"Improved vim compatibility.","package":"autosess.zip","4":"autosess.zip","src_id":"25664","5":"25664","creation_date":"1511877292","6":"1511877292"},{"0":"3883","vim_version":"7.0","1":"7.0","script_version":"1.2.2","2":"1.2.2","version_comment":"vimball","3":"vimball","package":"autosess.vmb","4":"autosess.vmb","src_id":"24739","5":"24739","creation_date":"1479365651","6":"1479365651"},{"0":"3883","vim_version":"7.0","1":"7.0","script_version":"1.2.2","2":"1.2.2","version_comment":"Improved windows compatibility.\r\nImproved vim compatibility.","3":"Improved windows compatibility.\r\nImproved vim compatibility.","package":"autosess.zip","4":"autosess.zip","src_id":"24738","5":"24738","creation_date":"1479365625","6":"1479365625"},{"0":"3883","vim_version":"7.0","1":"7.0","script_version":"1.2.1","2":"1.2.1","version_comment":"vimball","3":"vimball","package":"autosess.vmb","4":"autosess.vmb","src_id":"23598","5":"23598","creation_date":"1442405497","6":"1442405497"},{"0":"3883","vim_version":"7.0","1":"7.0","script_version":"1.2.1","2":"1.2.1","version_comment":"Avoid occasional useless message on restoring session.","3":"Avoid occasional useless message on restoring session.","package":"autosess.zip","4":"autosess.zip","src_id":"23597","5":"23597","creation_date":"1442405475","6":"1442405475"},{"0":"3883","vim_version":"7.0","1":"7.0","script_version":"1.2.0","2":"1.2.0","version_comment":"vimball","3":"vimball","package":"autosess.vmb","4":"autosess.vmb","src_id":"19213","5":"19213","creation_date":"1355942379","6":"1355942379"},{"0":"3883","vim_version":"7.0","1":"7.0","script_version":"1.2.0","2":"1.2.0","version_comment":"add option g:autosess_dir","3":"add option g:autosess_dir","package":"autosess.zip","4":"autosess.zip","src_id":"19212","5":"19212","creation_date":"1355942362","6":"1355942362"},{"0":"3883","vim_version":"7.0","1":"7.0","script_version":"1.1","2":"1.1","version_comment":"vimball","3":"vimball","package":"autosess.vmb","4":"autosess.vmb","src_id":"17234","5":"17234","creation_date":"1326760366","6":"1326760366"},{"0":"3883","vim_version":"7.0","1":"7.0","script_version":"1.1","2":"1.1","version_comment":"Don't restore empty useless buffers with &buftype 'quickfix' or 'nofile'.","3":"Don't restore empty useless buffers with &buftype 'quickfix' or 'nofile'.","package":"autosess.zip","4":"autosess.zip","src_id":"17233","5":"17233","creation_date":"1326760337","6":"1326760337"},{"0":"3883","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"vimball","3":"vimball","package":"autosess.vmb","4":"autosess.vmb","src_id":"17217","5":"17217","creation_date":"1326624991","6":"1326624991"},{"0":"3883","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"initial release","3":"initial release","package":"autosess.zip","4":"autosess.zip","src_id":"17216","5":"17216","creation_date":"1326624947","6":"1326624947"}]},"3882":{"script_id":"3882","0":"3882","script_name":"EasyDigraph.vim","1":"EasyDigraph.vim","script_type":"utility","2":"utility","summary":"input special characters easier (+digraphs).","3":"input special characters easier (+digraphs).","description":"    *EasyDigraph* makes inputting special characters easier (+digraphs).\r\n    \r\n    With |:digraphs|, You can use i_<Ctrl-K> to input a special character. \r\n    but have to press it everytime.\r\n    With EasyDigraph, you can use mapping with {motion} to convert\r\n    to special characters.\r\n\r\n    Default mapping in Normal Mode is '<leader>bb'.\r\n    You can remap it by changing |g:EasyDigraph_nmap|\r\n    \r\n    For example:\r\n    <leader>bbaW on 'a*b*c*d*e*' to Greek 'αβξδε'\r\n    <leader>bb2w on 'o5hayou5 gozai5masu' to Hiragana 'おはよう ございます'\r\n    <leader>bbi{ in '{(S8S+S3SnS)S}' to SuperScript {⁽⁸⁺\u00c2\u00b3ⁿ⁾}' \r\n    <leader>bbit in '<p>\\n3S >* \\n2S <\/p>' to '<p>n\u00c2\u00b3≫ n\u00c2\u00b2 <\/p>'\r\n\r\n    EasyDigraph will automatically igonre converted characters.\r\n    That is, only convert the characters between ASCII 33~126\r\n    so press shortcut on 'αβξδε' will make no change on it.\r\n    \r\n    And when Converting, Vim digraph will ignore ' \\ ' with char after.\r\n    so '\\1\\+\\2' will became '1+2'. \r\n    The only exception is '\/'. (Until vim 7.3 )\r\n    \r\n    A Insert Mode mapping to change the current WORD.\r\n    Default mapping is '<c-x><c-b>'\r\n    You can remap it by changing |g:EasyDigraph_imap|\r\n    \r\n    A Visual Mode mapping to change current highlight area.\r\n    Default mapping is '<c-b>'\r\n    You can remap it by changing |g:EasyDigraph_vmap|\r\n    \r\n    looking at |:digraph| and |digraphs-default| for digraph details.\r\n\r\n    You can post issues at https:\/\/github.com\/Rykka\/easydigraph.vim\/\r\n\r\nThere is an article that classified the vim digraphs roughly at\r\nhttp:\/\/rykka.is-programmer.com\/posts\/31752 (Chinese)\r\n\r\n\r\n","4":"    *EasyDigraph* makes inputting special characters easier (+digraphs).\r\n    \r\n    With |:digraphs|, You can use i_<Ctrl-K> to input a special character. \r\n    but have to press it everytime.\r\n    With EasyDigraph, you can use mapping with {motion} to convert\r\n    to special characters.\r\n\r\n    Default mapping in Normal Mode is '<leader>bb'.\r\n    You can remap it by changing |g:EasyDigraph_nmap|\r\n    \r\n    For example:\r\n    <leader>bbaW on 'a*b*c*d*e*' to Greek 'αβξδε'\r\n    <leader>bb2w on 'o5hayou5 gozai5masu' to Hiragana 'おはよう ございます'\r\n    <leader>bbi{ in '{(S8S+S3SnS)S}' to SuperScript {⁽⁸⁺\u00c2\u00b3ⁿ⁾}' \r\n    <leader>bbit in '<p>\\n3S >* \\n2S <\/p>' to '<p>n\u00c2\u00b3≫ n\u00c2\u00b2 <\/p>'\r\n\r\n    EasyDigraph will automatically igonre converted characters.\r\n    That is, only convert the characters between ASCII 33~126\r\n    so press shortcut on 'αβξδε' will make no change on it.\r\n    \r\n    And when Converting, Vim digraph will ignore ' \\ ' with char after.\r\n    so '\\1\\+\\2' will became '1+2'. \r\n    The only exception is '\/'. (Until vim 7.3 )\r\n    \r\n    A Insert Mode mapping to change the current WORD.\r\n    Default mapping is '<c-x><c-b>'\r\n    You can remap it by changing |g:EasyDigraph_imap|\r\n    \r\n    A Visual Mode mapping to change current highlight area.\r\n    Default mapping is '<c-b>'\r\n    You can remap it by changing |g:EasyDigraph_vmap|\r\n    \r\n    looking at |:digraph| and |digraphs-default| for digraph details.\r\n\r\n    You can post issues at https:\/\/github.com\/Rykka\/easydigraph.vim\/\r\n\r\nThere is an article that classified the vim digraphs roughly at\r\nhttp:\/\/rykka.is-programmer.com\/posts\/31752 (Chinese)\r\n\r\n\r\n","install_details":"","5":"","first_name":"Rykka","6":"Rykka","last_name":"f","7":"f","releases":[{"0":"3882","vim_version":"7.0","1":"7.0","script_version":"0.3","2":"0.3","version_comment":"Support all motions.","3":"Support all motions.","package":"easydigraph.vim-0.3.tar.gz","4":"easydigraph.vim-0.3.tar.gz","src_id":"17228","5":"17228","creation_date":"1326732780","6":"1326732780"},{"0":"3882","vim_version":"7.0","1":"7.0","script_version":"0.2","2":"0.2","version_comment":"vmap in visual mode added.","3":"vmap in visual mode added.","package":"easydigraph.vim-0.2.tar.gz","4":"easydigraph.vim-0.2.tar.gz","src_id":"17221","5":"17221","creation_date":"1326647934","6":"1326647934"},{"0":"3882","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"easydigraph.vim-0.1.tar.gz","4":"easydigraph.vim-0.1.tar.gz","src_id":"17212","5":"17212","creation_date":"1326597222","6":"1326597222"}]},"3881":{"script_id":"3881","0":"3881","script_name":"vim-powerline","1":"vim-powerline","script_type":"utility","2":"utility","summary":"The ultimate vim statusline utility.","3":"The ultimate vim statusline utility.","description":"**IMPORTANT** PLUGIN IS DEPRECATED IN FAVOR OF THE NEW POWERLINE PYTHON PORT.\r\n\r\nPowerline is a utility plugin which allows you to create better-looking, \r\nmore functional vim statuslines. See the screenshots below for \r\na demonstration of the plugin's capabilities.\r\n\r\n**Note:** You need a patched font to be able to use the symbols in the \r\nstatusbar. An experimental Python\/fontforge-based font patcher is included \r\nin the ``fontpatcher`` directory. See ``fontpatcher\/README.rst`` for usage \r\ninstructions.\r\n\r\nScreenshot gallery: http:\/\/imgur.com\/a\/RRp4c\r\n\r\nCheck out the git repo on GitHub for the latest updates: https:\/\/github.com\/Lokaltog\/vim-powerline\r\nSubmit issues to the issue tracker: https:\/\/github.com\/Lokaltog\/vim-powerline\/issues","4":"**IMPORTANT** PLUGIN IS DEPRECATED IN FAVOR OF THE NEW POWERLINE PYTHON PORT.\r\n\r\nPowerline is a utility plugin which allows you to create better-looking, \r\nmore functional vim statuslines. See the screenshots below for \r\na demonstration of the plugin's capabilities.\r\n\r\n**Note:** You need a patched font to be able to use the symbols in the \r\nstatusbar. An experimental Python\/fontforge-based font patcher is included \r\nin the ``fontpatcher`` directory. See ``fontpatcher\/README.rst`` for usage \r\ninstructions.\r\n\r\nScreenshot gallery: http:\/\/imgur.com\/a\/RRp4c\r\n\r\nCheck out the git repo on GitHub for the latest updates: https:\/\/github.com\/Lokaltog\/vim-powerline\r\nSubmit issues to the issue tracker: https:\/\/github.com\/Lokaltog\/vim-powerline\/issues","install_details":"Extract and move contents to your .vim folder. \r\n\r\nPathogen users: Clone git:\/\/github.com\/Lokaltog\/vim-powerline.git into your bundle folder.","5":"Extract and move contents to your .vim folder. \r\n\r\nPathogen users: Clone git:\/\/github.com\/Lokaltog\/vim-powerline.git into your bundle folder.","first_name":"Kim","6":"Kim","last_name":"Silkeb\u00c3\u00a6kken","7":"Silkeb\u00c3\u00a6kken","releases":[{"0":"3881","vim_version":"7.2","1":"7.2","script_version":"β","2":"β","version_comment":"https:\/\/github.com\/Lokaltog\/vim-powerline\/compare\/f2acebb...d885f900acfde8094f408b53ab61774bd0b83b13","3":"https:\/\/github.com\/Lokaltog\/vim-powerline\/compare\/f2acebb...d885f900acfde8094f408b53ab61774bd0b83b13","package":"Lokaltog-vim-powerline-d885f90.tar.gz","4":"Lokaltog-vim-powerline-d885f90.tar.gz","src_id":"17546","5":"17546","creation_date":"1330505532","6":"1330505532"},{"0":"3881","vim_version":"7.2","1":"7.2","script_version":"β","2":"β","version_comment":"A lot of changes, please see the git reflog for change details.","3":"A lot of changes, please see the git reflog for change details.","package":"Lokaltog-vim-powerline-f2acebb.tar.gz","4":"Lokaltog-vim-powerline-f2acebb.tar.gz","src_id":"17296","5":"17296","creation_date":"1327254550","6":"1327254550"},{"0":"3881","vim_version":"7.3","1":"7.3","script_version":"β","2":"β","version_comment":"Initial upload","3":"Initial upload","package":"Lokaltog-vim-powerline-b330fe6.tar.gz","4":"Lokaltog-vim-powerline-b330fe6.tar.gz","src_id":"17204","5":"17204","creation_date":"1326560279","6":"1326560279"}]},"3880":{"script_id":"3880","0":"3880","script_name":"fountain.vim","1":"fountain.vim","script_type":"syntax","2":"syntax","summary":" Syntax for Fountain screenplay files","3":" Syntax for Fountain screenplay files","description":"Fountain is a plain text markup language for screenwriting.\r\n\r\nPreviously SPMD (screenplay markdown), Fountain is very official, now, and getting to be something of a Big Deal, as it merges two similar screenwriting projects into one. The format can be converted into Final Draft files (FDX) and HTML, and can be imported by Final Draft and Movie Magic. Scrippets (less powerful conversion) is available for WordPress, BBEdit, and other web standards.\r\n\r\nhttp:\/\/fountain.io\/\r\n\r\nFountain is much like SPMD, with some important changes. Atx headers are now supported in order to create sections, and this makes Fountain compatible with the Voom outliner (vimscript #2657) in Markdown mode.\r\n\r\nCommenting has been changed; and an important feature called Boneyard is introduced, allowing for flexible striking of deleted material.\r\n\r\nKnown issues in the current version: text emphasis only renders in 'normal' text (action, not dialogue), and adding eol double-spaces does not have the intended corrective effect (this should be fixed in an update).\r\n\r\nThe official Fountain site contains a great deal of helpful material, including sample scripts and apps. In brief, Fountain allows you to type a screenplay in plain text. Here is an excerpt from Big Fish by John August, one of the screenwriters behind Fountain, and note that the text can be flush or tabbed as desired.\r\n\r\nEDWARD\r\n(whispering)\r\nTurn off your flashlights!  She'll see 'em.\r\n\r\nMOVING UP behind the kids, we find ourselves at the gates of...\r\n\r\nEXT.  A CREEPY OLD HOUSE - NIGHT  \r\n\r\nADULT EDWARD (V.O.)\r\nNow, it's common knowledge that most towns of a certain size have a witch, if only to eat misbehaving children and the occasional puppy who wanders into her yard.  Witches use those bones to cast spells and curses that make the land infertile.\r\n\r\n ====\r\n\r\nThe following image previews the syntax in a few different colorschemes:\r\n\r\nhttp:\/\/elflife.net\/vim\/FountainRenderedColorschemes.png\r\n\r\nHappy screenwriting!","4":"Fountain is a plain text markup language for screenwriting.\r\n\r\nPreviously SPMD (screenplay markdown), Fountain is very official, now, and getting to be something of a Big Deal, as it merges two similar screenwriting projects into one. The format can be converted into Final Draft files (FDX) and HTML, and can be imported by Final Draft and Movie Magic. Scrippets (less powerful conversion) is available for WordPress, BBEdit, and other web standards.\r\n\r\nhttp:\/\/fountain.io\/\r\n\r\nFountain is much like SPMD, with some important changes. Atx headers are now supported in order to create sections, and this makes Fountain compatible with the Voom outliner (vimscript #2657) in Markdown mode.\r\n\r\nCommenting has been changed; and an important feature called Boneyard is introduced, allowing for flexible striking of deleted material.\r\n\r\nKnown issues in the current version: text emphasis only renders in 'normal' text (action, not dialogue), and adding eol double-spaces does not have the intended corrective effect (this should be fixed in an update).\r\n\r\nThe official Fountain site contains a great deal of helpful material, including sample scripts and apps. In brief, Fountain allows you to type a screenplay in plain text. Here is an excerpt from Big Fish by John August, one of the screenwriters behind Fountain, and note that the text can be flush or tabbed as desired.\r\n\r\nEDWARD\r\n(whispering)\r\nTurn off your flashlights!  She'll see 'em.\r\n\r\nMOVING UP behind the kids, we find ourselves at the gates of...\r\n\r\nEXT.  A CREEPY OLD HOUSE - NIGHT  \r\n\r\nADULT EDWARD (V.O.)\r\nNow, it's common knowledge that most towns of a certain size have a witch, if only to eat misbehaving children and the occasional puppy who wanders into her yard.  Witches use those bones to cast spells and curses that make the land infertile.\r\n\r\n ====\r\n\r\nThe following image previews the syntax in a few different colorschemes:\r\n\r\nhttp:\/\/elflife.net\/vim\/FountainRenderedColorschemes.png\r\n\r\nHappy screenwriting!","install_details":"Save the file fountain.vim to your ~\/.vim\/syntax directory and add a line in your ~\/.vimrc or in ~\/.vim\/filetype.vim to load this syntax file for all *.fountain files, or create an additional fountain.vim file in ~\/.vim\/ftdetect including this line:\r\n\r\nau BufRead,BufNewFile *.fountain\t\tset filetype=fountain","5":"Save the file fountain.vim to your ~\/.vim\/syntax directory and add a line in your ~\/.vimrc or in ~\/.vim\/filetype.vim to load this syntax file for all *.fountain files, or create an additional fountain.vim file in ~\/.vim\/ftdetect including this line:\r\n\r\nau BufRead,BufNewFile *.fountain\t\tset filetype=fountain","first_name":"carson","6":"carson","last_name":"fire","7":"fire","releases":[{"0":"3880","vim_version":"7.3","1":"7.3","script_version":"2.02","2":"2.02","version_comment":"More minor improvements. Notes fixed.","3":"More minor improvements. Notes fixed.","package":"fountain.vim","4":"fountain.vim","src_id":"17497","5":"17497","creation_date":"1329723979","6":"1329723979"},{"0":"3880","vim_version":"7.3","1":"7.3","script_version":"2.01","2":"2.01","version_comment":"Extremely minor changes; slightly improved character name matching. Scene numbers now included (such as #1# on scene header line).","3":"Extremely minor changes; slightly improved character name matching. Scene numbers now included (such as #1# on scene header line).","package":"fountain.vim","4":"fountain.vim","src_id":"17491","5":"17491","creation_date":"1329647764","6":"1329647764"},{"0":"3880","vim_version":"7.3","1":"7.3","script_version":"2.0","2":"2.0","version_comment":"SPMD is now Fountain! Although much is the same, this version reflects some important changes in the official syntax, and this version simply works better in Vim than the previous one. Please do not use the old spmd.vim, use fountain.vim instead!","3":"SPMD is now Fountain! Although much is the same, this version reflects some important changes in the official syntax, and this version simply works better in Vim than the previous one. Please do not use the old spmd.vim, use fountain.vim instead!","package":"fountain.vim","4":"fountain.vim","src_id":"17414","5":"17414","creation_date":"1328783823","6":"1328783823"},{"0":"3880","vim_version":"7.0","1":"7.0","script_version":"1.1","2":"1.1","version_comment":"Corrections and changes (new specs released on 1\/13\/2012)\r\n\r\n* Because of potential conflict, no longer link to Markdown syntax for italics and bold--this is now implemented independently, and only in action lines and any other non-formatted sections\r\n* Included all the possible scene headers from the SPMD appendix, uppercase and lower\r\n* Spaces and tabs allowed before character name, parenthetical, and dialogue\r\n* Spaces at end \"corrects\" non-character name uppercase line\r\n* EOL double-space highlighting\r\n* Parentheticals allowed on character name line (must be in caps)\r\n* Cut line allows colon at end, or greater-than symbol at beginning\r\n* Forced scene headings\r\n* Revised dual dialogue syntax (previous syntax commented out in case of future revisions)\r\n* Page breaks\r\n\r\nNot yet supported:\r\n* Title page formatting (specs say this will change substantially anyway)\r\n* Italics, bold, and underline within dialogue and other contained areas\r\n* Sections","3":"Corrections and changes (new specs released on 1\/13\/2012)\r\n\r\n* Because of potential conflict, no longer link to Markdown syntax for italics and bold--this is now implemented independently, and only in action lines and any other non-formatted sections\r\n* Included all the possible scene headers from the SPMD appendix, uppercase and lower\r\n* Spaces and tabs allowed before character name, parenthetical, and dialogue\r\n* Spaces at end \"corrects\" non-character name uppercase line\r\n* EOL double-space highlighting\r\n* Parentheticals allowed on character name line (must be in caps)\r\n* Cut line allows colon at end, or greater-than symbol at beginning\r\n* Forced scene headings\r\n* Revised dual dialogue syntax (previous syntax commented out in case of future revisions)\r\n* Page breaks\r\n\r\nNot yet supported:\r\n* Title page formatting (specs say this will change substantially anyway)\r\n* Italics, bold, and underline within dialogue and other contained areas\r\n* Sections","package":"spmd.vim","4":"spmd.vim","src_id":"17206","5":"17206","creation_date":"1326574505","6":"1326574505"},{"0":"3880","vim_version":"7.0","1":"7.0","script_version":"1","2":"1","version_comment":"Initial upload","3":"Initial upload","package":"spmd.vim","4":"spmd.vim","src_id":"17201","5":"17201","creation_date":"1326501745","6":"1326501745"}]},"3879":{"script_id":"3879","0":"3879","script_name":"ambicmd.vim","1":"ambicmd.vim","script_type":"utility","2":"utility","summary":"You can use ambiguous command.","3":"You can use ambiguous command.","description":"*ambicmd* is a Vim plugin to use ambiguous command.\r\nSome plugins provide many useful command, but sometimes these are very long.\r\nAt this time, you will define the key mappings to execute these. but:\r\n\r\n- You will have to define quite a lot of key mappings.\r\n- You should find unused key sequence for mapping.\r\n- Do you define a key mapping for a command only occasionally used?\r\n\r\nThis plugin expands a ambiguous command by some patterns.  For example,\r\n\r\n  (\"|\" is cursor)\r\n  \" Expands to the correct name from the lowercase.\r\n  :ref<Space>  =>  :Ref |\r\n\r\n  \" Expands from the capital letter of the command.\r\n  :qr<Space>   =>  :QuickRun |\r\n\r\n  \" There are some commands with \"NeoComplCache\" prefix.\r\n  :ncc<Space>  =>  :NeoComplCache|\r\n\r\nThis plugin does nothing by default.\r\nYou need write some settings to vimrc as follows.\r\n\r\n  cnoremap <expr> <Space> ambicmd#expand(\"\\<Space>\")\r\n  cnoremap <expr> <CR>    ambicmd#expand(\"\\<CR>\")\r\n\r\n\r\nLatest Version:\r\nhttps:\/\/github.com\/thinca\/vim-ambicmd","4":"*ambicmd* is a Vim plugin to use ambiguous command.\r\nSome plugins provide many useful command, but sometimes these are very long.\r\nAt this time, you will define the key mappings to execute these. but:\r\n\r\n- You will have to define quite a lot of key mappings.\r\n- You should find unused key sequence for mapping.\r\n- Do you define a key mapping for a command only occasionally used?\r\n\r\nThis plugin expands a ambiguous command by some patterns.  For example,\r\n\r\n  (\"|\" is cursor)\r\n  \" Expands to the correct name from the lowercase.\r\n  :ref<Space>  =>  :Ref |\r\n\r\n  \" Expands from the capital letter of the command.\r\n  :qr<Space>   =>  :QuickRun |\r\n\r\n  \" There are some commands with \"NeoComplCache\" prefix.\r\n  :ncc<Space>  =>  :NeoComplCache|\r\n\r\nThis plugin does nothing by default.\r\nYou need write some settings to vimrc as follows.\r\n\r\n  cnoremap <expr> <Space> ambicmd#expand(\"\\<Space>\")\r\n  cnoremap <expr> <CR>    ambicmd#expand(\"\\<CR>\")\r\n\r\n\r\nLatest Version:\r\nhttps:\/\/github.com\/thinca\/vim-ambicmd","install_details":"","5":"","first_name":"thinca","6":"thinca","last_name":" ","7":" ","releases":[{"0":"3879","vim_version":"7.3","1":"7.3","script_version":"0.5.0","2":"0.5.0","version_comment":"Initial upload","3":"Initial upload","package":"vim-ambicmd-0.5.0.zip","4":"vim-ambicmd-0.5.0.zip","src_id":"17198","5":"17198","creation_date":"1326471668","6":"1326471668"}]},"3878":{"script_id":"3878","0":"3878","script_name":"nerdtree-ack","1":"nerdtree-ack","script_type":"patch","2":"patch","summary":"NERDtree + ack.vim","3":"NERDtree + ack.vim","description":"This plugin add capability to search in folders via NERDtree. The search use ack.vim from the master branch (http:\/\/github.com\/mileszs\/ack.vim\/tree\/master).\r\n\r\nThis is ripped off from \"NERDTree & ack\" plugin (vimscript #3357) by Tudor Barbu. It just doesn't fit my taste, so, yeah.\r\n\r\n## How to Use\r\n\r\n1. Open NERDtree\r\n2. Point to a directory\r\n3. Press `ms`\r\n4. Enter search term (e.g. `control\\ panel -i`)\r\n5. Profit!\r\n\r\n## Features\r\n\r\n1. Doesn't change current open buffers! This feature is what necessitate the use of latest ack.vim\r\n2. Uses ack.vim syntax:\r\n    - Use `\\ ` to write a space (e.g. `control\\ panel`)\r\n    - Or enclose the term in quotes (e.g. `\"control panel\"`)\r\n    - The default behavior is case sensitive. Use `-i` params for case insensitive (e.g. `\"control panel\" -i`)\r\n3. Uses ack.vim buffer behavior\r\n","4":"This plugin add capability to search in folders via NERDtree. The search use ack.vim from the master branch (http:\/\/github.com\/mileszs\/ack.vim\/tree\/master).\r\n\r\nThis is ripped off from \"NERDTree & ack\" plugin (vimscript #3357) by Tudor Barbu. It just doesn't fit my taste, so, yeah.\r\n\r\n## How to Use\r\n\r\n1. Open NERDtree\r\n2. Point to a directory\r\n3. Press `ms`\r\n4. Enter search term (e.g. `control\\ panel -i`)\r\n5. Profit!\r\n\r\n## Features\r\n\r\n1. Doesn't change current open buffers! This feature is what necessitate the use of latest ack.vim\r\n2. Uses ack.vim syntax:\r\n    - Use `\\ ` to write a space (e.g. `control\\ panel`)\r\n    - Or enclose the term in quotes (e.g. `\"control panel\"`)\r\n    - The default behavior is case sensitive. Use `-i` params for case insensitive (e.g. `\"control panel\" -i`)\r\n3. Uses ack.vim buffer behavior\r\n","install_details":"1. Install ack.vim first from http:\/\/github.com\/mileszs\/ack.vim\/tree\/master. Or you can use my branch (https:\/\/github.com\/tyok\/ack.vim) whose behavior is IMHO more NERDtree-friendly.\r\n2. Copy the plugin file to your .vim\/plugin directory\r\n","5":"1. Install ack.vim first from http:\/\/github.com\/mileszs\/ack.vim\/tree\/master. Or you can use my branch (https:\/\/github.com\/tyok\/ack.vim) whose behavior is IMHO more NERDtree-friendly.\r\n2. Copy the plugin file to your .vim\/plugin directory\r\n","first_name":"Mohammad","6":"Mohammad","last_name":"Satrio","7":"Satrio","releases":[{"0":"3878","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"NERD_tree-ack.vim","4":"NERD_tree-ack.vim","src_id":"17196","5":"17196","creation_date":"1326443957","6":"1326443957"}]},"3877":{"script_id":"3877","0":"3877","script_name":"ft_improved","1":"ft_improved","script_type":"utility","2":"utility","summary":"improved f\/t command","3":"improved f\/t command","description":"If you like it, please rate it!\r\n\r\nThis plugin tries to improve the existing behaviour of the |f|, |F|, |t| and\r\n|T| command by letting them move the cursor not only inside the current line, but move to whatever line, where the character is found.\r\n\r\nIt does consider counts given and should work simply as a user would be expecting.\r\n\r\nIt basically does that, by remapping the f,F,t and T command to issue a search for the character that is entered and moving the cursor there.\r\n\r\nBy default the new f,F,t,T commands should simply work. If you have disabled\r\nthe plugin (see |improvedft-Disable|), use the command\r\n    :EnableImprovedFT\r\n\r\nIf for any reason, you want to disable the plugin, use\r\n    :DisableImprovedFT\r\n\r\nPublic repo: https:\/\/github.com\/chrisbra\/improvedft\r\n","4":"If you like it, please rate it!\r\n\r\nThis plugin tries to improve the existing behaviour of the |f|, |F|, |t| and\r\n|T| command by letting them move the cursor not only inside the current line, but move to whatever line, where the character is found.\r\n\r\nIt does consider counts given and should work simply as a user would be expecting.\r\n\r\nIt basically does that, by remapping the f,F,t and T command to issue a search for the character that is entered and moving the cursor there.\r\n\r\nBy default the new f,F,t,T commands should simply work. If you have disabled\r\nthe plugin (see |improvedft-Disable|), use the command\r\n    :EnableImprovedFT\r\n\r\nIf for any reason, you want to disable the plugin, use\r\n    :DisableImprovedFT\r\n\r\nPublic repo: https:\/\/github.com\/chrisbra\/improvedft\r\n","install_details":"Open the vimball with Vim and source it, e.g.\r\nVim ft_improved-0.1.vmb\r\n:so %\r\n:q\r\n\r\nBe sure to read the help at :h improvedft-ft","5":"Open the vimball with Vim and source it, e.g.\r\nVim ft_improved-0.1.vmb\r\n:so %\r\n:q\r\n\r\nBe sure to read the help at :h improvedft-ft","first_name":"Christian","6":"Christian","last_name":"Brabandt","7":"Brabandt","releases":[{"0":"3877","vim_version":"7.3","1":"7.3","script_version":"9","2":"9","version_comment":"- do not mess up highlighting for ; and , commands\n- make count work correctly with multi-highlight match, so that only the count'th occurence gets highlighted.\n- allow to disable mappings selectively improvedft-Mapping (issue https:\/\/github.com\/chrisbra\/improvedft\/issues\/4 reported by Maiko Cezar, thanks!)\n- make the plugin not unneccessarily source the autoload script\n- document improvedft-consistent_comma\n(automatically uploaded)","3":"- do not mess up highlighting for ; and , commands\n- make count work correctly with multi-highlight match, so that only the count'th occurence gets highlighted.\n- allow to disable mappings selectively improvedft-Mapping (issue https:\/\/github.com\/chrisbra\/improvedft\/issues\/4 reported by Maiko Cezar, thanks!)\n- make the plugin not unneccessarily source the autoload script\n- document improvedft-consistent_comma\n(automatically uploaded)","package":"ft_improved-0.9.vmb","4":"ft_improved-0.9.vmb","src_id":"22802","5":"22802","creation_date":"1421354882","6":"1421354882"},{"0":"3877","vim_version":"7.3","1":"7.3","script_version":"8","2":"8","version_comment":"- handle keys like <Enter>, <Tab> literally\n- escape '\/' correctly for |t| commands.\n(automatically uploaded)","3":"- handle keys like <Enter>, <Tab> literally\n- escape '\/' correctly for |t| commands.\n(automatically uploaded)","package":"ft_improved-0.8.vmb","4":"ft_improved-0.8.vmb","src_id":"21682","5":"21682","creation_date":"1395959019","6":"1395959019"},{"0":"3877","vim_version":"7.3","1":"7.3","script_version":"7","2":"7","version_comment":"- small bugfixes\n- correctly handle ignorecase setting |improvedft-ignorecase|\n- escape '\n- make ; work correctly when using backwards motion.\n(automatically uploaded)","3":"- small bugfixes\n- correctly handle ignorecase setting |improvedft-ignorecase|\n- escape '\n- make ; work correctly when using backwards motion.\n(automatically uploaded)","package":"ft_improved-0.7.vmb","4":"ft_improved-0.7.vmb","src_id":"20652","5":"20652","creation_date":"1376549349","6":"1376549349"},{"0":"3877","vim_version":"7.3","1":"7.3","script_version":"6","2":"6","version_comment":"- |improvedft-multichars|\n- save and restore search-history in all modes correctly\n(automatically uploaded)","3":"- |improvedft-multichars|\n- save and restore search-history in all modes correctly\n(automatically uploaded)","package":"ft_improved-0.6.vmb","4":"ft_improved-0.6.vmb","src_id":"19654","5":"19654","creation_date":"1363442439","6":"1363442439"},{"0":"3877","vim_version":"7.3","1":"7.3","script_version":"5","2":"5","version_comment":"- ignorecase when searching, when g:ft_improved_ignorecase is set\n(automatically uploaded)","3":"- ignorecase when searching, when g:ft_improved_ignorecase is set\n(automatically uploaded)","package":"ft_improved-0.5.vmb","4":"ft_improved-0.5.vmb","src_id":"19528","5":"19528","creation_date":"1361053330","6":"1361053330"},{"0":"3877","vim_version":"7.3","1":"7.3","script_version":"4","2":"4","version_comment":"- special handling of pattern \/ and ?\n(automatically uploaded)","3":"- special handling of pattern \/ and ?\n(automatically uploaded)","package":"ft_improved-0.4.vmb","4":"ft_improved-0.4.vmb","src_id":"18572","5":"18572","creation_date":"1347192865","6":"1347192865"},{"0":"3877","vim_version":"7.3","1":"7.3","script_version":"3","2":"3","version_comment":"- fix issue https:\/\/github.com\/chrisbra\/improvedft\/issues\/1\n  by disallowing the Yankring to map the keys f F t and T\n- Better mapping of \";\" key (patch by Marcin Szamotulski, thanks!)\n(automatically uploaded)","3":"- fix issue https:\/\/github.com\/chrisbra\/improvedft\/issues\/1\n  by disallowing the Yankring to map the keys f F t and T\n- Better mapping of \";\" key (patch by Marcin Szamotulski, thanks!)\n(automatically uploaded)","package":"ft_improved-0.3.vmb","4":"ft_improved-0.3.vmb","src_id":"18442","5":"18442","creation_date":"1345485772","6":"1345485772"},{"0":"3877","vim_version":"7.3","1":"7.3","script_version":"2","2":"2","version_comment":" - disable debug mode\n- enable |GLVS|\n(automatically uploaded)","3":" - disable debug mode\n- enable |GLVS|\n(automatically uploaded)","package":"ft_improved-0.2.vmb","4":"ft_improved-0.2.vmb","src_id":"17200","5":"17200","creation_date":"1326486775","6":"1326486775"},{"0":"3877","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"ft_improved-0.1.vmb","4":"ft_improved-0.1.vmb","src_id":"17192","5":"17192","creation_date":"1326397552","6":"1326397552"}]},"3875":{"script_id":"3875","0":"3875","script_name":"git diff","1":"git diff","script_type":"ftplugin","2":"ftplugin","summary":"make a git diff when edit git log file in vim IDE","3":"make a git diff when edit git log file in vim IDE","description":"when edit git log file in vim IDE, make a git diff between two tags\r\n\r\n<leader>gd for make a git diff between for tags\r\n<leader>gf for open a file in the log like:\r\n --- a\/xxx.c\r\n+++ b\/xxx.c","4":"when edit git log file in vim IDE, make a git diff between two tags\r\n\r\n<leader>gd for make a git diff between for tags\r\n<leader>gf for open a file in the log like:\r\n --- a\/xxx.c\r\n+++ b\/xxx.c","install_details":"copy the gitdiff.vim to ~\/.vim\/plugin\/ directory","5":"copy the gitdiff.vim to ~\/.vim\/plugin\/ directory","first_name":"karl","6":"karl","last_name":"zheng","7":"zheng","releases":[{"0":"3875","vim_version":"7.0","1":"7.0","script_version":"0.2","2":"0.2","version_comment":"fixup: exactly show diff of two tags","3":"fixup: exactly show diff of two tags","package":"gitdiff.vim","4":"gitdiff.vim","src_id":"17428","5":"17428","creation_date":"1328955383","6":"1328955383"},{"0":"3875","vim_version":"7.0","1":"7.0","script_version":"0.01","2":"0.01","version_comment":"Initial upload","3":"Initial upload","package":"gitdiff.vim","4":"gitdiff.vim","src_id":"17185","5":"17185","creation_date":"1326260778","6":"1326260778"}]},"3874":{"script_id":"3874","0":"3874","script_name":"html-xml-tag-matcher","1":"html-xml-tag-matcher","script_type":"utility","2":"utility","summary":"Matches closing tag of an opening xml or html tag by scanning the document","3":"Matches closing tag of an opening xml or html tag by scanning the document","description":"This script is no longer supported. Please use the matchit.vim plugin(already bundled with vim > 7) instead.\r\n","4":"This script is no longer supported. Please use the matchit.vim plugin(already bundled with vim > 7) instead.\r\n","install_details":"","5":"","first_name":"Sandeep","6":"Sandeep","last_name":"CR","7":"CR","releases":[{"0":"3874","vim_version":"7.3","1":"7.3","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"tagmatch.vim","4":"tagmatch.vim","src_id":"17182","5":"17182","creation_date":"1326183435","6":"1326183435"}]},"3873":{"script_id":"3873","0":"3873","script_name":"turbux.vim","1":"turbux.vim","script_type":"utility","2":"utility","summary":"Turbo Ruby tests with tmux","3":"Turbo Ruby tests with tmux","description":"Turbux is designed to speed up your TDD cycle by using a single key mapping to run the most relevant test based on the current file in vim. It uses tmux's scriptability to send commands to a chosen pane in your tmux session, by way of tslime.vim.\r\n\r\nFor more information, see the documentation.\r\n\r\nMust be used with tslime.vim, vimscript #3023. Best when used with rails.vim, vimscript #1567.","4":"Turbux is designed to speed up your TDD cycle by using a single key mapping to run the most relevant test based on the current file in vim. It uses tmux's scriptability to send commands to a chosen pane in your tmux session, by way of tslime.vim.\r\n\r\nFor more information, see the documentation.\r\n\r\nMust be used with tslime.vim, vimscript #3023. Best when used with rails.vim, vimscript #1567.","install_details":"Copy turbux.vim from the plugin folder into your plugin folder.","5":"Copy turbux.vim from the plugin folder into your plugin folder.","first_name":"Joshua","6":"Joshua","last_name":"Davey","7":"Davey","releases":[{"0":"3873","vim_version":"7.2","1":"7.2","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"vim-turbux.zip","4":"vim-turbux.zip","src_id":"17179","5":"17179","creation_date":"1326087681","6":"1326087681"}]},"3872":{"script_id":"3872","0":"3872","script_name":"vimprj","1":"vimprj","script_type":"utility","2":"utility","summary":"Plugin for managing options for different projects","3":"Plugin for managing options for different projects","description":"Please note: there's dependency DfrankUtil (vimscript #3884)\r\n\r\n                                  * * *\r\n\r\nI've published a thorough article on Vimprj + Indexer usage; consider reading it: http:\/\/dmitryfrank.com\/articles\/vim_project_code_navigation\r\n\r\n                                  * * *\r\nMany times i faced a problem. That's the story:\r\n\r\nI'd like to use 3-space indent in my projects.\r\nNo tabs, especially three spaces. One day i need to work on another project\r\nwritten by someone else, and there's 4 spaces indent. Or maybe tabs.\r\n\r\nI need to work on this project too, and i need to keep existing formatting\r\noptions.\r\n\r\nI strongly dislike that i have to switch these options by hand: &shiftwidth,\r\n&tabstop, &expandtab.\r\n\r\nAnd then i decided to write this plugin to make my life easier.\r\n\r\nUsing this plugin is quite easy. You need to create in the root directory of\r\nyour project new directory \".vimprj\" and put any number of files \"*.vim\" in it.\r\nEvery time you open new file in Vim, plugin looks for \".vimprj\" directory up\r\nby tree, and if it is found, then all *.vim files from it will be sourced.\r\n\r\nOR: you can just put file \".vimprj\", then this file will be sourced.\r\nName \".vimprj\" can be changed by editing option g:vimprj_dirNameForSearch .\r\n\r\nUsually for my own projects i create just one file .vimprj\/my.vim with the\r\nfollowing contents: >\r\n\r\n   let &tabstop = 3\r\n   let &shiftwidth = 3\r\n   set expandtab\r\n\r\n(my .vimprj directory also contain tags and other project-specific files,\r\nso, i'd prefer to use directory instead of just one file.)\r\n\r\nand for other projects i create file with appropriate options.\r\n\r\nNow, when i open file from my project, file my.vim is sourced. When i open\r\nfile from some another project, its own file with options is sourced too. Of\r\ncourse, when i switch buffer, this files are sourced too if project is\r\nchanged.\r\n\r\nSo, i always have correct options, and simultaneus work on several projects\r\nwith different formatting options is not painful anymore for me.\r\n\r\nAnd, of course, you can use it not only to manage formatting options. For\r\ninstance, in some my projects i use mapping <F9> to open project window \r\n(from plugin project.tar.gz), but for some java projects i use Eclim, and <F9>\r\nshould be mapped to another command (to open Eclim's project). \r\nAll these options can also be stated in .vimprj dir.\r\n\r\nThere is an issue: as i already said, i would like to use shiftwidth=3. Say,\r\ni open some file from my project with shiftwidth=3. All ok here. Then i open\r\nfile from another project with shiftwidth=4. All is still ok. Then i open some\r\nfile not from any project (there's no \".vimprj\" directory). Of course, i would\r\nlike to use my favorite options (e.g. shiftwidth=3), but now shiftwidth is 4,\r\nbecause it was changed when i opened last project. It leads us to the fact\r\nthat we should define default options. But here let me make a digression.\r\n\r\nPlugin provides some hooks for any other plugin. For instance, plugin \r\nIndexer (since version 4.0) uses these hooks to provide correct behavior \r\nwhen user works on different project simultaneusly.\r\n\r\nRight now i have not documented yet all these hooks, because of lack of \r\nfree time, but i just tell you about one hook, to let you specify your\r\ndefault options.\r\n\r\nThis is a hook \"SetDefaultOptions\". Now i show you an example. Please insert\r\nin your .vimrc the following, just specify your own default options instead of\r\nmine ones: >\r\n\r\n   function! <SID>SetMainDefaults()\r\n\r\n      \" your default options goes here!\r\n      set tabstop=3\r\n      set shiftwidth=3\r\n      set expandtab\r\n\r\n   endfunction\r\n\r\n   call <SID>SetMainDefaults()\r\n\r\n   \" initialize vimprj plugin\r\n   call vimprj#init()\r\n\r\n   \" define a hook\r\n   function! g:vimprj#dHooks['SetDefaultOptions']['main_options'](dParams)\r\n      call <SID>SetMainDefaults()\r\n   endfunction\r\n\r\nNow vimprj plugin will call your function SetMainDefaults just before sourcing\r\nall *.vim files from .vimprj directory, and when you open file not from any\r\nproject.\r\n\r\nIf you are interesting about another hooks, you can just look how is they used\r\nin Indexer plugin (since version 4.0). I hope one day i will write all this here. =)\r\n\r\nPlease NOTE: by default this plugin will change your current dir\r\nto project's dir if \".vimprj\" is found.\r\nMore detailed read in help: type  :help vimprj-options , look for an option\r\ng:vimprj_changeCurDirIfVimprjFound\r\n\r\nDevelopment repository (Mercurial) : http:\/\/hg.dfrank.ru\/vim\/bundle\/vimprj\r\nStable git repository: https:\/\/github.com\/vim-scripts\/vimprj (Note that this repository is auto-generated by http:\/\/vim-scripts.org as a mirror of http:\/\/www.vim.org) \r\n","4":"Please note: there's dependency DfrankUtil (vimscript #3884)\r\n\r\n                                  * * *\r\n\r\nI've published a thorough article on Vimprj + Indexer usage; consider reading it: http:\/\/dmitryfrank.com\/articles\/vim_project_code_navigation\r\n\r\n                                  * * *\r\nMany times i faced a problem. That's the story:\r\n\r\nI'd like to use 3-space indent in my projects.\r\nNo tabs, especially three spaces. One day i need to work on another project\r\nwritten by someone else, and there's 4 spaces indent. Or maybe tabs.\r\n\r\nI need to work on this project too, and i need to keep existing formatting\r\noptions.\r\n\r\nI strongly dislike that i have to switch these options by hand: &shiftwidth,\r\n&tabstop, &expandtab.\r\n\r\nAnd then i decided to write this plugin to make my life easier.\r\n\r\nUsing this plugin is quite easy. You need to create in the root directory of\r\nyour project new directory \".vimprj\" and put any number of files \"*.vim\" in it.\r\nEvery time you open new file in Vim, plugin looks for \".vimprj\" directory up\r\nby tree, and if it is found, then all *.vim files from it will be sourced.\r\n\r\nOR: you can just put file \".vimprj\", then this file will be sourced.\r\nName \".vimprj\" can be changed by editing option g:vimprj_dirNameForSearch .\r\n\r\nUsually for my own projects i create just one file .vimprj\/my.vim with the\r\nfollowing contents: >\r\n\r\n   let &tabstop = 3\r\n   let &shiftwidth = 3\r\n   set expandtab\r\n\r\n(my .vimprj directory also contain tags and other project-specific files,\r\nso, i'd prefer to use directory instead of just one file.)\r\n\r\nand for other projects i create file with appropriate options.\r\n\r\nNow, when i open file from my project, file my.vim is sourced. When i open\r\nfile from some another project, its own file with options is sourced too. Of\r\ncourse, when i switch buffer, this files are sourced too if project is\r\nchanged.\r\n\r\nSo, i always have correct options, and simultaneus work on several projects\r\nwith different formatting options is not painful anymore for me.\r\n\r\nAnd, of course, you can use it not only to manage formatting options. For\r\ninstance, in some my projects i use mapping <F9> to open project window \r\n(from plugin project.tar.gz), but for some java projects i use Eclim, and <F9>\r\nshould be mapped to another command (to open Eclim's project). \r\nAll these options can also be stated in .vimprj dir.\r\n\r\nThere is an issue: as i already said, i would like to use shiftwidth=3. Say,\r\ni open some file from my project with shiftwidth=3. All ok here. Then i open\r\nfile from another project with shiftwidth=4. All is still ok. Then i open some\r\nfile not from any project (there's no \".vimprj\" directory). Of course, i would\r\nlike to use my favorite options (e.g. shiftwidth=3), but now shiftwidth is 4,\r\nbecause it was changed when i opened last project. It leads us to the fact\r\nthat we should define default options. But here let me make a digression.\r\n\r\nPlugin provides some hooks for any other plugin. For instance, plugin \r\nIndexer (since version 4.0) uses these hooks to provide correct behavior \r\nwhen user works on different project simultaneusly.\r\n\r\nRight now i have not documented yet all these hooks, because of lack of \r\nfree time, but i just tell you about one hook, to let you specify your\r\ndefault options.\r\n\r\nThis is a hook \"SetDefaultOptions\". Now i show you an example. Please insert\r\nin your .vimrc the following, just specify your own default options instead of\r\nmine ones: >\r\n\r\n   function! <SID>SetMainDefaults()\r\n\r\n      \" your default options goes here!\r\n      set tabstop=3\r\n      set shiftwidth=3\r\n      set expandtab\r\n\r\n   endfunction\r\n\r\n   call <SID>SetMainDefaults()\r\n\r\n   \" initialize vimprj plugin\r\n   call vimprj#init()\r\n\r\n   \" define a hook\r\n   function! g:vimprj#dHooks['SetDefaultOptions']['main_options'](dParams)\r\n      call <SID>SetMainDefaults()\r\n   endfunction\r\n\r\nNow vimprj plugin will call your function SetMainDefaults just before sourcing\r\nall *.vim files from .vimprj directory, and when you open file not from any\r\nproject.\r\n\r\nIf you are interesting about another hooks, you can just look how is they used\r\nin Indexer plugin (since version 4.0). I hope one day i will write all this here. =)\r\n\r\nPlease NOTE: by default this plugin will change your current dir\r\nto project's dir if \".vimprj\" is found.\r\nMore detailed read in help: type  :help vimprj-options , look for an option\r\ng:vimprj_changeCurDirIfVimprjFound\r\n\r\nDevelopment repository (Mercurial) : http:\/\/hg.dfrank.ru\/vim\/bundle\/vimprj\r\nStable git repository: https:\/\/github.com\/vim-scripts\/vimprj (Note that this repository is auto-generated by http:\/\/vim-scripts.org as a mirror of http:\/\/www.vim.org) \r\n","install_details":"There's dependency: script-library DfrankUtil (vimscript #3884)\r\n\r\nAnd i suggest you to use Pathogen (vimscript #2332) to manage your plugins.","5":"There's dependency: script-library DfrankUtil (vimscript #3884)\r\n\r\nAnd i suggest you to use Pathogen (vimscript #2332) to manage your plugins.","first_name":"Dmitry","6":"Dmitry","last_name":"Frank","7":"Frank","releases":[{"0":"3872","vim_version":"7.0","1":"7.0","script_version":"1.11","2":"1.11","version_comment":"I've published a thorough article on Vimprj + Indexer usage, you might want to check it out: http:\/\/dmitryfrank.com\/articles\/vim_project_code_navigation\r\n\r\nNew in this version:\r\n\r\n- Added $VIMPRJ_PROJECT_ROOT variable, which is set to the root of the currently active project;\r\n- Default behavior changed: now, by default, Vimprj doesn't touch your current working directory. Set g:vimprj_changeCurDirIfVimprjFound if you want it to do so.\r\n","3":"I've published a thorough article on Vimprj + Indexer usage, you might want to check it out: http:\/\/dmitryfrank.com\/articles\/vim_project_code_navigation\r\n\r\nNew in this version:\r\n\r\n- Added $VIMPRJ_PROJECT_ROOT variable, which is set to the root of the currently active project;\r\n- Default behavior changed: now, by default, Vimprj doesn't touch your current working directory. Set g:vimprj_changeCurDirIfVimprjFound if you want it to do so.\r\n","package":"vimprj-1.11.zip","4":"vimprj-1.11.zip","src_id":"23664","5":"23664","creation_date":"1444576001","6":"1444576001"},{"0":"3872","vim_version":"7.0","1":"7.0","script_version":"1.10","2":"1.10","version_comment":"Fixed issue: there was an error if path contains spaces (thanks to Alexey Shevchenko)","3":"Fixed issue: there was an error if path contains spaces (thanks to Alexey Shevchenko)","package":"vimprj-1.10.zip","4":"vimprj-1.10.zip","src_id":"21523","5":"21523","creation_date":"1393091596","6":"1393091596"},{"0":"3872","vim_version":"7.0","1":"7.0","script_version":"1.09","2":"1.09","version_comment":"Fixed issue: if quickfix window is opened, and user compiles current file (types :make ), then vimprj swithed to the 'default' settings.","3":"Fixed issue: if quickfix window is opened, and user compiles current file (types :make ), then vimprj swithed to the 'default' settings.","package":"vimprj-1.09.zip","4":"vimprj-1.09.zip","src_id":"19397","5":"19397","creation_date":"1358683796","6":"1358683796"},{"0":"3872","vim_version":"7.0","1":"7.0","script_version":"1.08","2":"1.08","version_comment":"* Please note: if you use plugin Indexer, then you need to update it to the latest version (4.15) because some hooks logic changed.\r\n* Nested projects are supported, and added new hook \"OnAfterSourcingVimprj\". I would recommend you to read nice article by Francisco Lopes da Silva: http:\/\/goo.gl\/vkCBc , there you can see well-explained example how to use these hooks effectively. Sorry for the lack of time to add all the hooks to docs. Great thanks to Francisco. ","3":"* Please note: if you use plugin Indexer, then you need to update it to the latest version (4.15) because some hooks logic changed.\r\n* Nested projects are supported, and added new hook \"OnAfterSourcingVimprj\". I would recommend you to read nice article by Francisco Lopes da Silva: http:\/\/goo.gl\/vkCBc , there you can see well-explained example how to use these hooks effectively. Sorry for the lack of time to add all the hooks to docs. Great thanks to Francisco. ","package":"vimprj-1.08.zip","4":"vimprj-1.08.zip","src_id":"18525","5":"18525","creation_date":"1346523349","6":"1346523349"},{"0":"3872","vim_version":"7.0","1":"7.0","script_version":"1.06","2":"1.06","version_comment":"*) Refactor. Added new dependency: script-library DfrankUtil (vimscript #3884)","3":"*) Refactor. Added new dependency: script-library DfrankUtil (vimscript #3884)","package":"vimprj-1.06.tar.gz","4":"vimprj-1.06.tar.gz","src_id":"17219","5":"17219","creation_date":"1326646413","6":"1326646413"},{"0":"3872","vim_version":"7.0","1":"7.0","script_version":"1.05","2":"1.05","version_comment":"*) Added :VimprjInfo command that echoes current project root (project root is a directory which contains .vimprj directory or file) \r\n*) Fix: new file creation is parsed correctly now.","3":"*) Added :VimprjInfo command that echoes current project root (project root is a directory which contains .vimprj directory or file) \r\n*) Fix: new file creation is parsed correctly now.","package":"vimprj-1.05.tar.gz","4":"vimprj-1.05.tar.gz","src_id":"17207","5":"17207","creation_date":"1326574587","6":"1326574587"},{"0":"3872","vim_version":"7.0","1":"7.0","script_version":"1.03","2":"1.03","version_comment":"Added possibility to use just one file \".vimprj\" (of course, name can be changed) instead of a whole directory, because in most cases people might want to create just one file with options, and \".vimprj\/rc.vim\" looks too obtrusive. Thanks to Aleksey Zapparov for nice remark.","3":"Added possibility to use just one file \".vimprj\" (of course, name can be changed) instead of a whole directory, because in most cases people might want to create just one file with options, and \".vimprj\/rc.vim\" looks too obtrusive. Thanks to Aleksey Zapparov for nice remark.","package":"vimprj-1.03.tar.gz","4":"vimprj-1.03.tar.gz","src_id":"17180","5":"17180","creation_date":"1326134846","6":"1326134846"},{"0":"3872","vim_version":"7.0","1":"7.0","script_version":"1.02","2":"1.02","version_comment":"Initial upload","3":"Initial upload","package":"vimprj-1.02.tar.gz","4":"vimprj-1.02.tar.gz","src_id":"17167","5":"17167","creation_date":"1325958673","6":"1325958673"}]},"3871":{"script_id":"3871","0":"3871","script_name":"SmartusLine","1":"SmartusLine","script_type":"utility","2":"utility","summary":"Plugin that changes the color of the statusline according with the current mode","3":"Plugin that changes the color of the statusline according with the current mode","description":"SmartusLine is Vim plugin that changes the color of the statusline of the focused window according with the current mode (normal\/insert\/replace)\r\n\r\nby default it highlights the filename on your statusline only, you can change that:\r\n\r\nlet g:smartusline_string_to_highlight = '(%n) %f '\r\n\r\nYou can also change the default colors of the highlight, the name are self-explanatory, the defaults are:\r\n\r\nlet g:smartusline_hi_replace = 'guibg=#e454ba guifg=black ctermbg=magenta ctermfg=black'\r\nlet g:smartusline_hi_insert = 'guibg=orange guifg=black ctermbg=58 ctermfg=black'\r\nlet g:smartusline_hi_virtual_replace = 'guibg=#e454ba guifg=black ctermbg=magenta ctermfg=black'\r\nlet g:smartusline_hi_normal = 'guibg=#95e454 guifg=black ctermbg=lightgreen ctermfg=black'\r\n\r\nnote: you probably want to set the statusline to never hide, like this:\r\n\r\nset laststatus=2\r\n\r\nGit repo available at https:\/\/github.com\/molok\/vim-smartusline\r\n\r\nplease file bugs on github: https:\/\/github.com\/molok\/vim-smartusline\/issues","4":"SmartusLine is Vim plugin that changes the color of the statusline of the focused window according with the current mode (normal\/insert\/replace)\r\n\r\nby default it highlights the filename on your statusline only, you can change that:\r\n\r\nlet g:smartusline_string_to_highlight = '(%n) %f '\r\n\r\nYou can also change the default colors of the highlight, the name are self-explanatory, the defaults are:\r\n\r\nlet g:smartusline_hi_replace = 'guibg=#e454ba guifg=black ctermbg=magenta ctermfg=black'\r\nlet g:smartusline_hi_insert = 'guibg=orange guifg=black ctermbg=58 ctermfg=black'\r\nlet g:smartusline_hi_virtual_replace = 'guibg=#e454ba guifg=black ctermbg=magenta ctermfg=black'\r\nlet g:smartusline_hi_normal = 'guibg=#95e454 guifg=black ctermbg=lightgreen ctermfg=black'\r\n\r\nnote: you probably want to set the statusline to never hide, like this:\r\n\r\nset laststatus=2\r\n\r\nGit repo available at https:\/\/github.com\/molok\/vim-smartusline\r\n\r\nplease file bugs on github: https:\/\/github.com\/molok\/vim-smartusline\/issues","install_details":"Extract it in your ~\/.vim (Linux\/BSD\/Mac OS X)  or ~\/_vimfiles (Win32)","5":"Extract it in your ~\/.vim (Linux\/BSD\/Mac OS X)  or ~\/_vimfiles (Win32)","first_name":"Alessio","6":"Alessio","last_name":"Bolognino","7":"Bolognino","releases":[{"0":"3871","vim_version":"7.0","1":"7.0","script_version":"0.3","2":"0.3","version_comment":"Less bugs, more features! (Read the help file)","3":"Less bugs, more features! (Read the help file)","package":"vim-smartusline-0.3.zip","4":"vim-smartusline-0.3.zip","src_id":"17312","5":"17312","creation_date":"1327445235","6":"1327445235"},{"0":"3871","vim_version":"7.0","1":"7.0","script_version":"0.2.1","2":"0.2.1","version_comment":"Added help file, fixed a couple of bugs","3":"Added help file, fixed a couple of bugs","package":"vim-smartusline-0.2.1.zip","4":"vim-smartusline-0.2.1.zip","src_id":"17169","5":"17169","creation_date":"1325961735","6":"1325961735"},{"0":"3871","vim_version":"7.0","1":"7.0","script_version":"0.2","2":"0.2","version_comment":"Added check for empty statusline and fixed a small bug on GVim initialization","3":"Added check for empty statusline and fixed a small bug on GVim initialization","package":"vim-smartusline-0.2.zip","4":"vim-smartusline-0.2.zip","src_id":"17165","5":"17165","creation_date":"1325889032","6":"1325889032"},{"0":"3871","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"removed debug echo I left in the code","3":"removed debug echo I left in the code","package":"vim-smartusline-0.1.zip","4":"vim-smartusline-0.1.zip","src_id":"17163","5":"17163","creation_date":"1325865651","6":"1325865651"}]},"3870":{"script_id":"3870","0":"3870","script_name":"vm.vim","1":"vm.vim","script_type":"syntax","2":"syntax","summary":"velocity vtl","3":"velocity vtl","description":"This is a Velocity Template Language syntax highlighter + filetype plugin. It features support of shorthand $my.some.reference(something) and longhand ${my.some.reference(something)} notations for both references and directives (including user defined macros). Everything described on the official web page (http:\/\/velocity.apache.org\/engine\/devel\/user-guide.html) is supported. Supports directives along with user defined macros one line and multiline. Error handling of incorrectly placed directives. References can be mutliline, so that \r\n\r\n$myref.long.array[ 3 ]. \r\nsomething. \r\ntake \r\n.fromHere() \r\n\r\nis also supported. Directives and references' methods and arrays can contain comments, unformatted text and doxygen comments.\r\n\r\nSpecial references sequences (e.g. $foreach.parent.index or $foreach.topmost.hasNext) are recognized as keywords if they are contained.\r\n\r\nTwo types of strings are supported. References inside double quotes \"\" are highlighted. \r\n\r\nMatchit support is introduced which allows you to jump from the start of a block (i.e. #if(), #foreach(), #define(), #macro(), #@any_user_macro()) to the end of the block (#end | #{end}) and vice versa with % just like you jump between opening and closing brackets. \r\n\r\nAlso all multiline directives supports folding. \r\n\r\nOnly directives described on the official web-page are recognized as system directives, user defined directives are recognized differently and can be one line or multiline. \r\n\r\nComments are automatically expanded to the next line while a user types them and appropriately recognized by vim engine. \r\n\r\nNOTE: this differs from velocity.vim (http:\/\/www.vim.org\/scripts\/script.php?script_id=541) in many cases, which provides only basic capability, which doesn't include recogniton of multiline entities. It doesn't support system directives and error handling. No way to jump between openinig and closing directive. No support of nonparsable blocks. That script is really very basic (no offence to the author). \r\n\r\nThis one provides all the capabilites described on the official web-page (http:\/\/velocity.apache.org\/engine\/devel\/user-guide.html) ","4":"This is a Velocity Template Language syntax highlighter + filetype plugin. It features support of shorthand $my.some.reference(something) and longhand ${my.some.reference(something)} notations for both references and directives (including user defined macros). Everything described on the official web page (http:\/\/velocity.apache.org\/engine\/devel\/user-guide.html) is supported. Supports directives along with user defined macros one line and multiline. Error handling of incorrectly placed directives. References can be mutliline, so that \r\n\r\n$myref.long.array[ 3 ]. \r\nsomething. \r\ntake \r\n.fromHere() \r\n\r\nis also supported. Directives and references' methods and arrays can contain comments, unformatted text and doxygen comments.\r\n\r\nSpecial references sequences (e.g. $foreach.parent.index or $foreach.topmost.hasNext) are recognized as keywords if they are contained.\r\n\r\nTwo types of strings are supported. References inside double quotes \"\" are highlighted. \r\n\r\nMatchit support is introduced which allows you to jump from the start of a block (i.e. #if(), #foreach(), #define(), #macro(), #@any_user_macro()) to the end of the block (#end | #{end}) and vice versa with % just like you jump between opening and closing brackets. \r\n\r\nAlso all multiline directives supports folding. \r\n\r\nOnly directives described on the official web-page are recognized as system directives, user defined directives are recognized differently and can be one line or multiline. \r\n\r\nComments are automatically expanded to the next line while a user types them and appropriately recognized by vim engine. \r\n\r\nNOTE: this differs from velocity.vim (http:\/\/www.vim.org\/scripts\/script.php?script_id=541) in many cases, which provides only basic capability, which doesn't include recogniton of multiline entities. It doesn't support system directives and error handling. No way to jump between openinig and closing directive. No support of nonparsable blocks. That script is really very basic (no offence to the author). \r\n\r\nThis one provides all the capabilites described on the official web-page (http:\/\/velocity.apache.org\/engine\/devel\/user-guide.html) ","install_details":"unpack to ~\/.vim, or install pathogen.vim and unpack to ~\/.vim\/bundle\/vtl \r\n\r\nto make the sytax highlighting and ftplugin work appropriately one may need to add \r\nautocmd BufRead,BufNewFile *.vm set syntax=vm filetype=vm \r\nto his\/her ~\/.vim\/ftdetect\/syntax.vim  ","5":"unpack to ~\/.vim, or install pathogen.vim and unpack to ~\/.vim\/bundle\/vtl \r\n\r\nto make the sytax highlighting and ftplugin work appropriately one may need to add \r\nautocmd BufRead,BufNewFile *.vm set syntax=vm filetype=vm \r\nto his\/her ~\/.vim\/ftdetect\/syntax.vim  ","first_name":"Sergey","6":"Sergey","last_name":"Markelov","7":"Markelov","releases":[{"0":"3870","vim_version":"7.0","1":"7.0","script_version":"1.1","2":"1.1","version_comment":"Added #else and #elseif blocks to matchit section. See Xibur's blog post http:\/\/xibur.blogspot.com\/2012\/07\/matchit-bmatchwords-strategy-for.html for further information.\r\n\r\nSpecial Thank You to Xibur.","3":"Added #else and #elseif blocks to matchit section. See Xibur's blog post http:\/\/xibur.blogspot.com\/2012\/07\/matchit-bmatchwords-strategy-for.html for further information.\r\n\r\nSpecial Thank You to Xibur.","package":"vtl.zip","4":"vtl.zip","src_id":"18259","5":"18259","creation_date":"1342284551","6":"1342284551"},{"0":"3870","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"vtl.zip","4":"vtl.zip","src_id":"17159","5":"17159","creation_date":"1325840045","6":"1325840045"}]},"3869":{"script_id":"3869","0":"3869","script_name":"lightdiff","1":"lightdiff","script_type":"color scheme","2":"color scheme","summary":"Light colorscheme","3":"Light colorscheme","description":"Light colorscheme which makes your vimdiff much easiler to see.\r\n\r\nScreenshot: https:\/\/github.com\/wipple\/lightdiff\/wiki\/ScreenShot","4":"Light colorscheme which makes your vimdiff much easiler to see.\r\n\r\nScreenshot: https:\/\/github.com\/wipple\/lightdiff\/wiki\/ScreenShot","install_details":"Requirement: GVim or Vim which supports 256 colors or higher.\r\nInstallation: Copy 'lightdiff.vim' into '~\/.vim\/colors\/'.","5":"Requirement: GVim or Vim which supports 256 colors or higher.\r\nInstallation: Copy 'lightdiff.vim' into '~\/.vim\/colors\/'.","first_name":"Yasuhiro","6":"Yasuhiro","last_name":"Ikeda","7":"Ikeda","releases":[{"0":"3869","vim_version":"7.0","1":"7.0","script_version":"1.2","2":"1.2","version_comment":"Fix ctermfg for Statement.","3":"Fix ctermfg for Statement.","package":"lightdiff.vim","4":"lightdiff.vim","src_id":"17177","5":"17177","creation_date":"1326070244","6":"1326070244"},{"0":"3869","vim_version":"7.0","1":"7.0","script_version":"1.1","2":"1.1","version_comment":"'lightdiff' now supports cterm(&t_Co>255).","3":"'lightdiff' now supports cterm(&t_Co>255).","package":"lightdiff.vim","4":"lightdiff.vim","src_id":"17176","5":"17176","creation_date":"1326069119","6":"1326069119"},{"0":"3869","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"lightdiff.vim","4":"lightdiff.vim","src_id":"17154","5":"17154","creation_date":"1325769081","6":"1325769081"}]},"3868":{"script_id":"3868","0":"3868","script_name":"multiwindow source code browsing","1":"multiwindow source code browsing","script_type":"ftplugin","2":"ftplugin","summary":"multiwindow tag stacked code browsing","3":"multiwindow tag stacked code browsing","description":"multiwindow tag stacked code browsing with global(gtag)\r\nvisit: http:\/\/vim.wikia.com\/wiki\/gtag_multiwindow","4":"multiwindow tag stacked code browsing with global(gtag)\r\nvisit: http:\/\/vim.wikia.com\/wiki\/gtag_multiwindow","install_details":"Copy the gtags_mwin.vim to vim plugin directory.","5":"Copy the gtags_mwin.vim to vim plugin directory.","first_name":"kalimuthu","6":"kalimuthu","last_name":"velappan","7":"velappan","releases":[{"0":"3868","vim_version":"7.0","1":"7.0","script_version":"1.3","2":"1.3","version_comment":"Shortcut keys assigned under global variable.","3":"Shortcut keys assigned under global variable.","package":"gtags_mwin.vim","4":"gtags_mwin.vim","src_id":"18090","5":"18090","creation_date":"1338795580","6":"1338795580"},{"0":"3868","vim_version":"7.0","1":"7.0","script_version":"1.2","2":"1.2","version_comment":" - Added as a new script file. \r\n - Help content has been added\r\n - Added the stack tag browsing support","3":" - Added as a new script file. \r\n - Help content has been added\r\n - Added the stack tag browsing support","package":"gtags_mwin.vim","4":"gtags_mwin.vim","src_id":"18089","5":"18089","creation_date":"1338792002","6":"1338792002"}]},"3866":{"script_id":"3866","0":"3866","script_name":"phidgets.vim","1":"phidgets.vim","script_type":"syntax","2":"syntax","summary":"C highlighting for Phidgets USB sensing and control interfaces","3":"C highlighting for Phidgets USB sensing and control interfaces","description":"Initial upload.\r\n\r\nAt the moment, functions and constants highlights are supported.  Vim file is built based on Phidget21 header file.  ","4":"Initial upload.\r\n\r\nAt the moment, functions and constants highlights are supported.  Vim file is built based on Phidget21 header file.  ","install_details":"Since this is a syntax highlight file to be used in combination to c.vim (I suppose), it is best to install the phidgets.vim file in $USER\/.vim\/after\/syntax\/c\/.\r\n\r\n","5":"Since this is a syntax highlight file to be used in combination to c.vim (I suppose), it is best to install the phidgets.vim file in $USER\/.vim\/after\/syntax\/c\/.\r\n\r\n","first_name":"mario","6":"mario","last_name":"st-gelais","7":"st-gelais","releases":[{"0":"3866","vim_version":"7.0","1":"7.0","script_version":"0.0.0","2":"0.0.0","version_comment":"Initial upload","3":"Initial upload","package":"phidgets.tar.gz","4":"phidgets.tar.gz","src_id":"17149","5":"17149","creation_date":"1325644718","6":"1325644718"}]},"3865":{"script_id":"3865","0":"3865","script_name":"behat.zip","1":"behat.zip","script_type":"ftplugin","2":"ftplugin","summary":"behat runtime files (adapted from cucumber ftplugin)","3":"behat runtime files (adapted from cucumber ftplugin)","description":"This is an adaptation of the cucumber ftplugin (https:\/\/github.com\/tpope\/vim-cucumber) for Behat (http:\/\/behat.org).\r\n\r\nSource code: https:\/\/github.com\/veloce\/vim-behat","4":"This is an adaptation of the cucumber ftplugin (https:\/\/github.com\/tpope\/vim-cucumber) for Behat (http:\/\/behat.org).\r\n\r\nSource code: https:\/\/github.com\/veloce\/vim-behat","install_details":"https:\/\/github.com\/veloce\/vim-behat\/blob\/master\/README.md#installation","5":"https:\/\/github.com\/veloce\/vim-behat\/blob\/master\/README.md#installation","first_name":"Vincent","6":"Vincent","last_name":"Velociter","7":"Velociter","releases":[{"0":"3865","vim_version":"7.0","1":"7.0","script_version":"1.2","2":"1.2","version_comment":"Added a cache per buffer for omnicompletion: this greatly improves the speed of completion\r\nNow the omnicompletion works well with neocomplcache\r\nAdded a command to clear the cache (':BehatInvalidatesOmniCache')","3":"Added a cache per buffer for omnicompletion: this greatly improves the speed of completion\r\nNow the omnicompletion works well with neocomplcache\r\nAdded a command to clear the cache (':BehatInvalidatesOmniCache')","package":"vim-behat-1.2.zip","4":"vim-behat-1.2.zip","src_id":"19015","5":"19015","creation_date":"1353614362","6":"1353614362"},{"0":"3865","vim_version":"7.0","1":"7.0","script_version":"1.1","2":"1.1","version_comment":"New command \":BehatCmdToClipBoard\" to copy the behat command that runs features in current buffer\r\nConfiguration variable \"b:behat_cmd_args\" to add arguments per buffer to the behat command\r\nGlobal variable \"g:behat_executables\" to prepend custom behat executables to search path\r\n","3":"New command \":BehatCmdToClipBoard\" to copy the behat command that runs features in current buffer\r\nConfiguration variable \"b:behat_cmd_args\" to add arguments per buffer to the behat command\r\nGlobal variable \"g:behat_executables\" to prepend custom behat executables to search path\r\n","package":"vim-behat-1.1.zip","4":"vim-behat-1.1.zip","src_id":"18376","5":"18376","creation_date":"1344429349","6":"1344429349"},{"0":"3865","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"vim-behat-1.0.zip","4":"vim-behat-1.0.zip","src_id":"17146","5":"17146","creation_date":"1325539532","6":"1325539532"}]},"3864":{"script_id":"3864","0":"3864","script_name":"Eddie.vim","1":"Eddie.vim","script_type":"color scheme","2":"color scheme","summary":"A dark pastel colorscheme my friend spent too much time on","3":"A dark pastel colorscheme my friend spent too much time on","description":"This colorscheme is compatible in GUI and Terminal Vim.\r\n\r\nIt includes some modified color highlighting for the following filetypes: HTML, CSS, JavaScript, HAML, SASS, CoffeeScript, Ruby, ZSH, and a couple others. Also adds better highlighting for diffing between files in Vim.\r\n\r\nScreenshots and FAQ available at the GitHub repo: https:\/\/github.com\/mattsa\/vim-eddie","4":"This colorscheme is compatible in GUI and Terminal Vim.\r\n\r\nIt includes some modified color highlighting for the following filetypes: HTML, CSS, JavaScript, HAML, SASS, CoffeeScript, Ruby, ZSH, and a couple others. Also adds better highlighting for diffing between files in Vim.\r\n\r\nScreenshots and FAQ available at the GitHub repo: https:\/\/github.com\/mattsa\/vim-eddie","install_details":"Add the eddie.vim file inside the colors directory to your existing colorschemes in ~\/.vim\/colors\/","5":"Add the eddie.vim file inside the colors directory to your existing colorschemes in ~\/.vim\/colors\/","first_name":"Matt","6":"Matt","last_name":"Sacks","7":"Sacks","releases":[{"0":"3864","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"vim-eddie.zip","4":"vim-eddie.zip","src_id":"17140","5":"17140","creation_date":"1325376198","6":"1325376198"}]},"3863":{"script_id":"3863","0":"3863","script_name":"epegzz.vim","1":"epegzz.vim","script_type":"color scheme","2":"color scheme","summary":"Just another dark color scheme","3":"Just another dark color scheme","description":"Since i wasn't satisfied with any of the existing color schemes i created my own. Works best in a 256 color terminal with dark transparent background.\r\n\r\nScreenshot: https:\/\/github.com\/epegzz\/epegzz.vim\/raw\/master\/screenshot.png","4":"Since i wasn't satisfied with any of the existing color schemes i created my own. Works best in a 256 color terminal with dark transparent background.\r\n\r\nScreenshot: https:\/\/github.com\/epegzz\/epegzz.vim\/raw\/master\/screenshot.png","install_details":"Simply unzip and copy colors\/epegzz.vim to your local colors directory. From within vim use `:colorscheme epegzz` to activate.\r\n\r\nGit user? Clone from git:\/\/github.com\/epegzz\/epegzz.vim.git","5":"Simply unzip and copy colors\/epegzz.vim to your local colors directory. From within vim use `:colorscheme epegzz` to activate.\r\n\r\nGit user? Clone from git:\/\/github.com\/epegzz\/epegzz.vim.git","first_name":"Daniel","6":"Daniel","last_name":"Schaefer","7":"Schaefer","releases":[{"0":"3863","vim_version":"7.3","1":"7.3","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"epegzz.zip","4":"epegzz.zip","src_id":"17138","5":"17138","creation_date":"1325361063","6":"1325361063"}]},"3862":{"script_id":"3862","0":"3862","script_name":"grads.vim","1":"grads.vim","script_type":"syntax","2":"syntax","summary":"GrADS syntax highlighting and indentation rules","3":"GrADS syntax highlighting and indentation rules","description":"This file contains an update of the default grads.vim syntax file and indentation rules for GrADS script language.\r\nIncludes syntax support for CTL files.\r\n\r\nFor an overview of GrADS, you can visit http:\/\/www.iges.org\/grads\/","4":"This file contains an update of the default grads.vim syntax file and indentation rules for GrADS script language.\r\nIncludes syntax support for CTL files.\r\n\r\nFor an overview of GrADS, you can visit http:\/\/www.iges.org\/grads\/","install_details":"Untar file and copy or symlink its content to:\r\n\r\nsyntax\/*        -->     ~\/.vim\/syntax\/\r\nindent\/*        -->     ~\/.vim\/indent\/\r\nfiletype.vim    -->     ~\/.vim\/\r\n\r\nIf filetype.vim exists, add this line:\r\n\r\nau BufRead,BufNewFile *.ctl setfiletype ctl\r\n\r\ninto the block \"augroup filetypedetect\" of your ~\/.vim\/filetype.vim file","5":"Untar file and copy or symlink its content to:\r\n\r\nsyntax\/*        -->     ~\/.vim\/syntax\/\r\nindent\/*        -->     ~\/.vim\/indent\/\r\nfiletype.vim    -->     ~\/.vim\/\r\n\r\nIf filetype.vim exists, add this line:\r\n\r\nau BufRead,BufNewFile *.ctl setfiletype ctl\r\n\r\ninto the block \"augroup filetypedetect\" of your ~\/.vim\/filetype.vim file","first_name":"P","6":"P","last_name":"G","7":"G","releases":[{"0":"3862","vim_version":"7.0","1":"7.0","script_version":"0.3","2":"0.3","version_comment":"Added support for .ctl files (GrADS descriptor file)","3":"Added support for .ctl files (GrADS descriptor file)","package":"grads.zip","4":"grads.zip","src_id":"18408","5":"18408","creation_date":"1345037205","6":"1345037205"},{"0":"3862","vim_version":"7.0","1":"7.0","script_version":"0.2","2":"0.2","version_comment":"bugfixes (numbers)","3":"bugfixes (numbers)","package":"grads.zip","4":"grads.zip","src_id":"18407","5":"18407","creation_date":"1345033306","6":"1345033306"},{"0":"3862","vim_version":"7.0","1":"7.0","script_version":"0.1.1","2":"0.1.1","version_comment":"Fixed compound variables syntax","3":"Fixed compound variables syntax","package":"grads.tar.gz","4":"grads.tar.gz","src_id":"17193","5":"17193","creation_date":"1326405576","6":"1326405576"},{"0":"3862","vim_version":"5.7","1":"5.7","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"grads.tar.gz","4":"grads.tar.gz","src_id":"17136","5":"17136","creation_date":"1325343672","6":"1325343672"}]},"3861":{"script_id":"3861","0":"3861","script_name":"Lawrencium","1":"Lawrencium","script_type":"utility","2":"utility","summary":"A Mercurial wrapper for Vim.","3":"A Mercurial wrapper for Vim.","description":"Grab the latest version from BitBucket: https:\/\/bitbucket.org\/ludovicchabant\/vim-lawrencium\r\n\r\nLawrencium is a Mercurial wrapper for Vim, inspired by Tim Pope's Fugitive. It adds many commands like :Hg (run a Mercurial command with auto-completion), :Hgedit (open a file relative to the repository's root), :Hgdiff and :Hgcommit (you can easily guess what they do), and a very cool :Hgstatus which shows an interactive version of `hg status`'s output.\r\n\r\nSee the project's README file for more information: https:\/\/bitbucket.org\/ludovicchabant\/vim-lawrencium\/overview\r\n","4":"Grab the latest version from BitBucket: https:\/\/bitbucket.org\/ludovicchabant\/vim-lawrencium\r\n\r\nLawrencium is a Mercurial wrapper for Vim, inspired by Tim Pope's Fugitive. It adds many commands like :Hg (run a Mercurial command with auto-completion), :Hgedit (open a file relative to the repository's root), :Hgdiff and :Hgcommit (you can easily guess what they do), and a very cool :Hgstatus which shows an interactive version of `hg status`'s output.\r\n\r\nSee the project's README file for more information: https:\/\/bitbucket.org\/ludovicchabant\/vim-lawrencium\/overview\r\n","install_details":"Extract to your ~\/.vim and run :helptags.\r\n\r\n","5":"Extract to your ~\/.vim and run :helptags.\r\n\r\n","first_name":"Ludovic","6":"Ludovic","last_name":"Chabant","7":"Chabant","releases":[{"0":"3861","vim_version":"7.4","1":"7.4","script_version":"0.4.0","2":"0.4.0","version_comment":"* Add bookmark information to the statusline function\r\n* Add command variants to open in a new tab\r\n* `Hglog` command can take the same options as the command line\r\n* New `Hglogexport` command can export a patch for a changeset from the log window\r\n* `Hgrecord` command to selectively commit parts of the current file\r\n* `HgPostCmd` custom autocommand for power users\r\n* Bug fixes and improvements","3":"* Add bookmark information to the statusline function\r\n* Add command variants to open in a new tab\r\n* `Hglog` command can take the same options as the command line\r\n* New `Hglogexport` command can export a patch for a changeset from the log window\r\n* `Hgrecord` command to selectively commit parts of the current file\r\n* `HgPostCmd` custom autocommand for power users\r\n* Bug fixes and improvements","package":"lawrencium_0.4.0.tar.gz","4":"lawrencium_0.4.0.tar.gz","src_id":"22738","5":"22738","creation_date":"1419732730","6":"1419732730"},{"0":"3861","vim_version":"7.3","1":"7.3","script_version":"0.3.1","2":"0.3.1","version_comment":"Fixed some bugs with the `Hgqseries` window.","3":"Fixed some bugs with the `Hgqseries` window.","package":"lawrencium-0.3.1.tar.gz","4":"lawrencium-0.3.1.tar.gz","src_id":"21496","5":"21496","creation_date":"1392655037","6":"1392655037"},{"0":"3861","vim_version":"7.3","1":"7.3","script_version":"0.3.0","2":"0.3.0","version_comment":"Added more support for MQ, various fixes and improvements.","3":"Added more support for MQ, various fixes and improvements.","package":"lawrencium-0.3.0.tar.gz","4":"lawrencium-0.3.0.tar.gz","src_id":"21493","5":"21493","creation_date":"1392623926","6":"1392623926"},{"0":"3861","vim_version":"7.0","1":"7.0","script_version":"0.2","2":"0.2","version_comment":"Added Hgrevert command.\r\nFixed incorrect URL in README.","3":"Added Hgrevert command.\r\nFixed incorrect URL in README.","package":"lawrencium-0.2.tar.gz","4":"lawrencium-0.2.tar.gz","src_id":"17527","5":"17527","creation_date":"1330104421","6":"1330104421"},{"0":"3861","vim_version":"7.3","1":"7.3","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"lawrencium.tar.gz","4":"lawrencium.tar.gz","src_id":"17129","5":"17129","creation_date":"1325228935","6":"1325228935"}]},"3860":{"script_id":"3860","0":"3860","script_name":"shelp","1":"shelp","script_type":"utility","2":"utility","summary":"Plugin for customer vim's toolbar and popup menu","3":"Plugin for customer vim's toolbar and popup menu","description":"The \"shelp\" plugin is a plugin for Vim that provides the features to \r\nallow you to efficiently customer vim's popup menu and toolbar.  \r\nThis ability can help you invoke some develop tools such as shell and python easily.\r\n\r\n\r\nAfter the install, please type:help shelp\r\n\r\nCustomer popup menu\r\n    <Leader>ri: add a new menu item to your popup menu.\r\n    <Leader>rd: delete a menu item from your popup menu.\r\n\r\nCustomer toolbar\r\n    <Leader>rI: add a new menu item to your toolbar.\r\n    <Leader>rD: delete a menu item from your toolbar. \r\n","4":"The \"shelp\" plugin is a plugin for Vim that provides the features to \r\nallow you to efficiently customer vim's popup menu and toolbar.  \r\nThis ability can help you invoke some develop tools such as shell and python easily.\r\n\r\n\r\nAfter the install, please type:help shelp\r\n\r\nCustomer popup menu\r\n    <Leader>ri: add a new menu item to your popup menu.\r\n    <Leader>rd: delete a menu item from your popup menu.\r\n\r\nCustomer toolbar\r\n    <Leader>rI: add a new menu item to your toolbar.\r\n    <Leader>rD: delete a menu item from your toolbar. \r\n","install_details":"Download the shelp.zip file and unzip the files to the $HOME\/.vim or\r\nthe $HOME\/vimfiles or the $VIM\/vimfiles directory. After this step, you should\r\nhave the following five files (the directory structure should be preserved):\r\n\r\n* $HOME\/.vim\/plugin\/shelp.vim - customer plugin fuctions.\r\n* $HOME\/.vim\/doc\/shelp.txt - help document in English.\r\n* $HOME\/.vim\/bitmaps\/*.bmp - sample icon files\r\n\r\nDon't forget to open the file and Use \":helptags .\" to install help tag.","5":"Download the shelp.zip file and unzip the files to the $HOME\/.vim or\r\nthe $HOME\/vimfiles or the $VIM\/vimfiles directory. After this step, you should\r\nhave the following five files (the directory structure should be preserved):\r\n\r\n* $HOME\/.vim\/plugin\/shelp.vim - customer plugin fuctions.\r\n* $HOME\/.vim\/doc\/shelp.txt - help document in English.\r\n* $HOME\/.vim\/bitmaps\/*.bmp - sample icon files\r\n\r\nDon't forget to open the file and Use \":helptags .\" to install help tag.","first_name":"Jia","6":"Jia","last_name":"Wei","7":"Wei","releases":[{"0":"3860","vim_version":"7.0","1":"7.0","script_version":"0.9.1","2":"0.9.1","version_comment":"delete exists item","3":"delete exists item","package":"shelp.zip","4":"shelp.zip","src_id":"17121","5":"17121","creation_date":"1324959614","6":"1324959614"}]},"3859":{"script_id":"3859","0":"3859","script_name":"Xoria256m","1":"Xoria256m","script_type":"color scheme","2":"color scheme","summary":"256 colorscheme forked from Xoria256","3":"256 colorscheme forked from Xoria256","description":"Xoria256m is a color scheme for a dark background. It is soft on the eyes and use greyish tones for text that is less important. \r\nIt needs the Tango terminal color scheme.\r\n\r\nNote: I'm slightly color blind (red\/green) so if you think this is hideous you're apparently not color blind.\r\n\r\nScreenshot (showing Go code): http:\/\/miek.nl\/gfx\/2011\/xoria256m-go_code.png\r\n\r\nXoria256m is forked from Xoria256: vimscript #2140\r\n\r\nFor those interested:\r\n\r\n* A matching mutt color scheme: http:\/\/www.miek.nl\/downloads\/2011\/mutt-color-xoria256m\r\n* And a dircolors theme: http:\/\/www.miek.nl\/downloads\/2011\/dircolors-xoria256m","4":"Xoria256m is a color scheme for a dark background. It is soft on the eyes and use greyish tones for text that is less important. \r\nIt needs the Tango terminal color scheme.\r\n\r\nNote: I'm slightly color blind (red\/green) so if you think this is hideous you're apparently not color blind.\r\n\r\nScreenshot (showing Go code): http:\/\/miek.nl\/gfx\/2011\/xoria256m-go_code.png\r\n\r\nXoria256m is forked from Xoria256: vimscript #2140\r\n\r\nFor those interested:\r\n\r\n* A matching mutt color scheme: http:\/\/www.miek.nl\/downloads\/2011\/mutt-color-xoria256m\r\n* And a dircolors theme: http:\/\/www.miek.nl\/downloads\/2011\/dircolors-xoria256m","install_details":"Just like any other color scheme. Your terminal should support 256 colors.","5":"Just like any other color scheme. Your terminal should support 256 colors.","first_name":"Miek","6":"Miek","last_name":"Gieben","7":"Gieben","releases":[{"0":"3859","vim_version":"7.0","1":"7.0","script_version":"1.0.3","2":"1.0.3","version_comment":"Don't mess with the background in console mode and got the gui colors in sync with the non-gui colors","3":"Don't mess with the background in console mode and got the gui colors in sync with the non-gui colors","package":"xoria256m.vim","4":"xoria256m.vim","src_id":"19662","5":"19662","creation_date":"1363688927","6":"1363688927"},{"0":"3859","vim_version":"7.0","1":"7.0","script_version":"1.0.2","2":"1.0.2","version_comment":"* MatchParen much more explicitly colored.\r\n* Define add as alias for Preproc.\r\n* Preproc is now (bold) blue.","3":"* MatchParen much more explicitly colored.\r\n* Define add as alias for Preproc.\r\n* Preproc is now (bold) blue.","package":"xoria256m.vim","4":"xoria256m.vim","src_id":"17341","5":"17341","creation_date":"1327952841","6":"1327952841"},{"0":"3859","vim_version":"7.0","1":"7.0","script_version":"1.0.1","2":"1.0.1","version_comment":"Make the grey for comments slighly lighter, makes it more readable.","3":"Make the grey for comments slighly lighter, makes it more readable.","package":"xoria256m.vim","4":"xoria256m.vim","src_id":"17131","5":"17131","creation_date":"1325237360","6":"1325237360"},{"0":"3859","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"xoria256m.vim","4":"xoria256m.vim","src_id":"17113","5":"17113","creation_date":"1324722694","6":"1324722694"}]},"3858":{"script_id":"3858","0":"3858","script_name":"rmvim","1":"rmvim","script_type":"utility","2":"utility","summary":"Remote editing with local gui Vim instance","3":"Remote editing with local gui Vim instance","description":"Vim GUI (MacVim, GVim) plugin to make remote editing more easy.\r\n\r\nMore information on https:\/\/github.com\/wannesm\/rmvim.vim\r\n\r\nInspired by the rmate functionality of TextMate but based on vim netrw .","4":"Vim GUI (MacVim, GVim) plugin to make remote editing more easy.\r\n\r\nMore information on https:\/\/github.com\/wannesm\/rmvim.vim\r\n\r\nInspired by the rmate functionality of TextMate but based on vim netrw .","install_details":"1. Install the rmvim.vim plugin in your local .vim directory.\r\n2. Copy the file `rmvim.vim\/util\/rmvim` to your remote host in a directory that is in your path.\r\n3. If you want to use gvim instead of mvim add the following to your .vimrc:  \r\n   `set g:rmvim_cmd = 'gvim'`\r\n","5":"1. Install the rmvim.vim plugin in your local .vim directory.\r\n2. Copy the file `rmvim.vim\/util\/rmvim` to your remote host in a directory that is in your path.\r\n3. If you want to use gvim instead of mvim add the following to your .vimrc:  \r\n   `set g:rmvim_cmd = 'gvim'`\r\n","first_name":"Wannes","6":"Wannes","last_name":"Meert","7":"Meert","releases":[{"0":"3858","vim_version":"7.3","1":"7.3","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"rmvim-v1.0.vim.tgz","4":"rmvim-v1.0.vim.tgz","src_id":"17106","5":"17106","creation_date":"1324631187","6":"1324631187"}]},"3857":{"script_id":"3857","0":"3857","script_name":"Word Fuzzy Completion ","1":"Word Fuzzy Completion ","script_type":"utility","2":"utility","summary":"A word fuzzy completion plugin for vim.","3":"A word fuzzy completion plugin for vim.","description":"URL: https:\/\/github.com\/jaanauati\/vim-wordfuzzycompletion-plugin\r\n\r\nDescription\r\nA word fuzzy completion plugin for vim.\r\n\r\nRequirement: \r\n +python vim support.\r\n\r\nInstallation:\r\n Just dowload the file `wordfuzzycompletion.vim` into ~\/.vim\/plugins and restart vim.\r\n\r\nUse mode:\r\n\r\n Put vim in insert mode and then you start typing, when you typed a part of a \r\nword press either  Ctrl-x Ctrl-u or Ctrl-k to see the list of similar words in\r\nthe current buffer and select one.\r\n\r\nIf there are just one result, then the typed word is replaced.\r\n\r\n Example:\r\n  Suppose that your buffer contains above text:\r\n  ------------------------\r\n  1 The simpsons\r\n  2 Futurama\r\n  3 Back to the Future.\r\n  4 Features\r\n  ~\r\n  ------------------------\r\n  then:\r\n  1) type \r\n  sminsons<press Ctrl-k>\r\n  word must be changed to:\r\n  simpsons\r\n  2) type\r\n  smi<press Ctrl-k>\r\n  word must be changed to:\r\n  simpsons\r\n  3) type\r\n  furure<press Ctrl-k>\r\n  word must be changed to:\r\n  future\r\n  4) type\r\n  Furu<press Ctrl-k>\r\n  so, must be showed a list of similar words:\r\n  Fururama\r\n  Future\r\n  Features\r\n  \r\nNOTE: as it is the first version of plugin there are some bugs, so, you are \r\nwellcome either to report them to me or fix them!.\r\n","4":"URL: https:\/\/github.com\/jaanauati\/vim-wordfuzzycompletion-plugin\r\n\r\nDescription\r\nA word fuzzy completion plugin for vim.\r\n\r\nRequirement: \r\n +python vim support.\r\n\r\nInstallation:\r\n Just dowload the file `wordfuzzycompletion.vim` into ~\/.vim\/plugins and restart vim.\r\n\r\nUse mode:\r\n\r\n Put vim in insert mode and then you start typing, when you typed a part of a \r\nword press either  Ctrl-x Ctrl-u or Ctrl-k to see the list of similar words in\r\nthe current buffer and select one.\r\n\r\nIf there are just one result, then the typed word is replaced.\r\n\r\n Example:\r\n  Suppose that your buffer contains above text:\r\n  ------------------------\r\n  1 The simpsons\r\n  2 Futurama\r\n  3 Back to the Future.\r\n  4 Features\r\n  ~\r\n  ------------------------\r\n  then:\r\n  1) type \r\n  sminsons<press Ctrl-k>\r\n  word must be changed to:\r\n  simpsons\r\n  2) type\r\n  smi<press Ctrl-k>\r\n  word must be changed to:\r\n  simpsons\r\n  3) type\r\n  furure<press Ctrl-k>\r\n  word must be changed to:\r\n  future\r\n  4) type\r\n  Furu<press Ctrl-k>\r\n  so, must be showed a list of similar words:\r\n  Fururama\r\n  Future\r\n  Features\r\n  \r\nNOTE: as it is the first version of plugin there are some bugs, so, you are \r\nwellcome either to report them to me or fix them!.\r\n","install_details":"Just dowload the file `wordfuzzycompletion.vim` into ~\/.vim\/plugins and restart vim.\r\n","5":"Just dowload the file `wordfuzzycompletion.vim` into ~\/.vim\/plugins and restart vim.\r\n","first_name":"Jonatan","6":"Jonatan","last_name":"Anauati","7":"Anauati","releases":[{"0":"3857","vim_version":"7.0","1":"7.0","script_version":"0.7","2":"0.7","version_comment":"Bugfix in the startup variables. The plugin is working fine again.","3":"Bugfix in the startup variables. The plugin is working fine again.","package":"vim-wordfuzzycompletion-plugin-v0.7.zip","4":"vim-wordfuzzycompletion-plugin-v0.7.zip","src_id":"17128","5":"17128","creation_date":"1325195482","6":"1325195482"},{"0":"3857","vim_version":"7.0","1":"7.0","script_version":"0.6","2":"0.6","version_comment":"Added customization variable.\r\nBetter documentation.","3":"Added customization variable.\r\nBetter documentation.","package":"vim-wordfuzzycompletion-plugin-v0.6.zip","4":"vim-wordfuzzycompletion-plugin-v0.6.zip","src_id":"17117","5":"17117","creation_date":"1324772942","6":"1324772942"},{"0":"3857","vim_version":"7.0","1":"7.0","script_version":"0.5","2":"0.5","version_comment":"Solves problems when user has typed words with the underscore char (for example: 'the_').\r\n","3":"Solves problems when user has typed words with the underscore char (for example: 'the_').\r\n","package":"vim-wordfuzzycompletion-plugin-v0.5.zip","4":"vim-wordfuzzycompletion-plugin-v0.5.zip","src_id":"17111","5":"17111","creation_date":"1324657959","6":"1324657959"},{"0":"3857","vim_version":"7.0","1":"7.0","script_version":"0.4","2":"0.4","version_comment":"Right now the underscore char ('_') is interpreted as a word part.","3":"Right now the underscore char ('_') is interpreted as a word part.","package":"vim-wordfuzzycompletion-plugin-v0.4.zip","4":"vim-wordfuzzycompletion-plugin-v0.4.zip","src_id":"17109","5":"17109","creation_date":"1324649720","6":"1324649720"},{"0":"3857","vim_version":"7.0","1":"7.0","script_version":"0.3","2":"0.3","version_comment":"Initial upload","3":"Initial upload","package":"vim-wordfuzzycompletion-plugin-v0.3.zip","4":"vim-wordfuzzycompletion-plugin-v0.3.zip","src_id":"17105","5":"17105","creation_date":"1324594460","6":"1324594460"}]},"3856":{"script_id":"3856","0":"3856","script_name":"tocdown","1":"tocdown","script_type":"utility","2":"utility","summary":"display the headlines of a markdown document in an extra window","3":"display the headlines of a markdown document in an extra window","description":"Description:\r\n\r\nWhen you are writing a tons of documents in markdown with many headings and you want to get an overview about all the headlines you have, would it be very handy to have shortcut in Vim to simply give you a structured representation of all the heading you have in your large markdown file?\r\n\r\nThe great taglist.vim plugin solved the problem already for variables and functions of many different programming languages but not for plain markdown-files. That's why I wrote tocdown.\r\n\r\nUsage:\r\n\r\nSimply press :TocdownToggle and the extra window with the headline of the current file will open. If you call :TocdownToggle again, the window will be closed.\r\n\r\nWhen you know how you want to use this plugin, you can use a custom mapping in your |:vimrc| to toggle the toc of a md-file\r\n\r\nnnoremap <F2> :TocdownToggle\r\n\r\nYou can change the mapping to your needs.\r\n\r\n\r\nScreencast:\r\n\r\nhttp:\/\/www.screenr.com\/zvos\r\n\r\n","4":"Description:\r\n\r\nWhen you are writing a tons of documents in markdown with many headings and you want to get an overview about all the headlines you have, would it be very handy to have shortcut in Vim to simply give you a structured representation of all the heading you have in your large markdown file?\r\n\r\nThe great taglist.vim plugin solved the problem already for variables and functions of many different programming languages but not for plain markdown-files. That's why I wrote tocdown.\r\n\r\nUsage:\r\n\r\nSimply press :TocdownToggle and the extra window with the headline of the current file will open. If you call :TocdownToggle again, the window will be closed.\r\n\r\nWhen you know how you want to use this plugin, you can use a custom mapping in your |:vimrc| to toggle the toc of a md-file\r\n\r\nnnoremap <F2> :TocdownToggle\r\n\r\nYou can change the mapping to your needs.\r\n\r\n\r\nScreencast:\r\n\r\nhttp:\/\/www.screenr.com\/zvos\r\n\r\n","install_details":"Installation\r\n\r\nUnzip the most recent ZIP (https:\/\/github.com\/matthias-guenther\/tocdown\/zipball\/master) archive file inside your Vim profile directory (usually ~\/.vim). \r\nThe plugin is compatible with Tim Popes pathogen script https:\/\/github.com\/tpope\/vim-pathogen.","5":"Installation\r\n\r\nUnzip the most recent ZIP (https:\/\/github.com\/matthias-guenther\/tocdown\/zipball\/master) archive file inside your Vim profile directory (usually ~\/.vim). \r\nThe plugin is compatible with Tim Popes pathogen script https:\/\/github.com\/tpope\/vim-pathogen.","first_name":"Matthias","6":"Matthias","last_name":"Guenther","7":"Guenther","releases":[{"0":"3856","vim_version":"7.0","1":"7.0","script_version":"1.0.1","2":"1.0.1","version_comment":"better Ruby script, faster generation of the headline","3":"better Ruby script, faster generation of the headline","package":"tocdown.zip","4":"tocdown.zip","src_id":"17274","5":"17274","creation_date":"1327130509","6":"1327130509"},{"0":"3856","vim_version":"7.0","1":"7.0","script_version":"1.0.0","2":"1.0.0","version_comment":"Initial upload","3":"Initial upload","package":"tocdown.zip","4":"tocdown.zip","src_id":"17104","5":"17104","creation_date":"1324591985","6":"1324591985"}]},"3855":{"script_id":"3855","0":"3855","script_name":"ide","1":"ide","script_type":"utility","2":"utility","summary":"ide for C\/C++\/Java with syntax coloring and tab buffer tracking","3":"ide for C\/C++\/Java with syntax coloring and tab buffer tracking","description":"HISTORY\r\n==========================================================\r\nAfter using the vimscript #69 plugin for quite some time, I started modifying\r\nit as I wanted to have each buffer open on its own TAB, to have syntax highlight\r\nusing the member, function and type classes defined within my project, and to\r\nhave a visual indication of which files were open and close within the project.\r\n\r\nThis ide plugin thus contains a re-write of the plugin project (1.3k) plus\r\nmy additional ide code (2.5k). The re-write was needed because instead of \r\nloading a project file into a file buffer, the ide plugin loads an index of\r\nall project files into a hash and displays it on the dedicated buffer, this \r\nallows for integration with other plugins that I do use such as the source\r\nexplorer plugin. There is a powerful feature in the original project plugin\r\n(script loading at file or project open) that I have never really used.\r\nI have ported this feature but I have never tested it.\r\n\r\nI do not expect you will agree with all changes, but I hope that some time in\r\nthe future someone else also motivated by \"personal taste\" will end up taking\r\nover this code, improve it and then pass it on, till the time we get a true\r\nIDE on top of vim.\r\n\r\nNow that I look back to this plugin, I think it would have been probably easier\r\nto implement it on VIM itselft.\r\n\r\nCHANGES WITH RESPECT TO THE PROJECT PLUGIN\r\n===========================================================\r\nI have tried to maintain the same functionality of the original project plugin,\r\nthat is, almost all its commands, settings, and flags are still valid. If you\r\nhave already used the project plugin then its migration to the ide plugin will\r\nbe transparent.\r\n\r\nThe main changes, upgrades and extensions that the ide plugin has with\r\n respect to the project plugin are:\r\n\r\n  Better visualization\r\n   - The ide window follows any tab movement provinding a persistant panel ide.\r\n   - Keeps track of all files opened, edited and closed using icons. Pending\r\n     tracking updates are refreshed as soon as the ide window is entered so\r\n     you can visualize the status of your project.\r\n   - No more multiple windows for the same buffer. Opening a file which is \r\n     already open won't create another window but will jump to the correct \r\n     tab and window.   \r\n   - Cursor movement within the ide windows seems as a file or project select.\r\n   - Windows width can be adjusted and re-adjusted.\r\n   - Tabs provide information on mouse hover\r\n\r\n  More Friendly \r\n  - Closing a project unloads all its working variables, so its safe to invoke \r\n    the|ide|again. Or open a new project and let to the|ide|unload the current\r\n    one.\r\n  - Help can be lauch from within the ide window by pressing <F1>\r\n  - All key-bindings can be customized in the|vimrc|file to another mapping.    \r\n  - Information on some key processes are provided on the command line\r\n  - Errors on bad usage are notified  \r\n  \r\n  Syntax Highlight \r\n  - Create the syntax file for the code based in the project-file\r\n  - Syntax file for the project are generated and loaded for the files on open\r\n  - Highlights are automatically or manually updated through the IDESyntax    \r\n    command.\r\n  - Highlights are refreshed on idle intervals, so your idle times are no\r\n    longer wasted.\r\n\r\n  Other Plugin interactions\r\n  - Can be registered to other plugins\r\n  - Have built in workarounds for some plugins that I use as part of my ide:\r\n    showmarks, taglist, source-explorer, ex-global-search\r\n\r\n  Tracing, Logging and Debugging Support\r\n  - Logs with detailed information of traces can be generated, see IDEShowlog\r\n  - All internal variables can be exposed through the command IDEShowenv\r\n  - Easier than ever to debug the plugin so you can modify it and improve it.\r\n    \r\n  OverHauling \r\n  - The core of the project plugin was re-writen to be loaded in a dedicated\r\n    buffer named __IDE_Project__. The project-file is read on loading the ide\r\n    and then closed, all the files contained are indexed and store in a map.\r\n  - Having the information in a map renders continuous parsing of the\r\n    project-file unnecessary, and facilitates the development of extensions.\r\n  - Make a project or a sub-project, with the key binding you wish.      \r\n\r\nSCREEN-SHOTS \r\n===========================================================\r\nFor screen-shots related to this plugin and additional documentation please \r\nvisit http:\/\/www.gomezprado.com\/ece\/code\/ide-vim","4":"HISTORY\r\n==========================================================\r\nAfter using the vimscript #69 plugin for quite some time, I started modifying\r\nit as I wanted to have each buffer open on its own TAB, to have syntax highlight\r\nusing the member, function and type classes defined within my project, and to\r\nhave a visual indication of which files were open and close within the project.\r\n\r\nThis ide plugin thus contains a re-write of the plugin project (1.3k) plus\r\nmy additional ide code (2.5k). The re-write was needed because instead of \r\nloading a project file into a file buffer, the ide plugin loads an index of\r\nall project files into a hash and displays it on the dedicated buffer, this \r\nallows for integration with other plugins that I do use such as the source\r\nexplorer plugin. There is a powerful feature in the original project plugin\r\n(script loading at file or project open) that I have never really used.\r\nI have ported this feature but I have never tested it.\r\n\r\nI do not expect you will agree with all changes, but I hope that some time in\r\nthe future someone else also motivated by \"personal taste\" will end up taking\r\nover this code, improve it and then pass it on, till the time we get a true\r\nIDE on top of vim.\r\n\r\nNow that I look back to this plugin, I think it would have been probably easier\r\nto implement it on VIM itselft.\r\n\r\nCHANGES WITH RESPECT TO THE PROJECT PLUGIN\r\n===========================================================\r\nI have tried to maintain the same functionality of the original project plugin,\r\nthat is, almost all its commands, settings, and flags are still valid. If you\r\nhave already used the project plugin then its migration to the ide plugin will\r\nbe transparent.\r\n\r\nThe main changes, upgrades and extensions that the ide plugin has with\r\n respect to the project plugin are:\r\n\r\n  Better visualization\r\n   - The ide window follows any tab movement provinding a persistant panel ide.\r\n   - Keeps track of all files opened, edited and closed using icons. Pending\r\n     tracking updates are refreshed as soon as the ide window is entered so\r\n     you can visualize the status of your project.\r\n   - No more multiple windows for the same buffer. Opening a file which is \r\n     already open won't create another window but will jump to the correct \r\n     tab and window.   \r\n   - Cursor movement within the ide windows seems as a file or project select.\r\n   - Windows width can be adjusted and re-adjusted.\r\n   - Tabs provide information on mouse hover\r\n\r\n  More Friendly \r\n  - Closing a project unloads all its working variables, so its safe to invoke \r\n    the|ide|again. Or open a new project and let to the|ide|unload the current\r\n    one.\r\n  - Help can be lauch from within the ide window by pressing <F1>\r\n  - All key-bindings can be customized in the|vimrc|file to another mapping.    \r\n  - Information on some key processes are provided on the command line\r\n  - Errors on bad usage are notified  \r\n  \r\n  Syntax Highlight \r\n  - Create the syntax file for the code based in the project-file\r\n  - Syntax file for the project are generated and loaded for the files on open\r\n  - Highlights are automatically or manually updated through the IDESyntax    \r\n    command.\r\n  - Highlights are refreshed on idle intervals, so your idle times are no\r\n    longer wasted.\r\n\r\n  Other Plugin interactions\r\n  - Can be registered to other plugins\r\n  - Have built in workarounds for some plugins that I use as part of my ide:\r\n    showmarks, taglist, source-explorer, ex-global-search\r\n\r\n  Tracing, Logging and Debugging Support\r\n  - Logs with detailed information of traces can be generated, see IDEShowlog\r\n  - All internal variables can be exposed through the command IDEShowenv\r\n  - Easier than ever to debug the plugin so you can modify it and improve it.\r\n    \r\n  OverHauling \r\n  - The core of the project plugin was re-writen to be loaded in a dedicated\r\n    buffer named __IDE_Project__. The project-file is read on loading the ide\r\n    and then closed, all the files contained are indexed and store in a map.\r\n  - Having the information in a map renders continuous parsing of the\r\n    project-file unnecessary, and facilitates the development of extensions.\r\n  - Make a project or a sub-project, with the key binding you wish.      \r\n\r\nSCREEN-SHOTS \r\n===========================================================\r\nFor screen-shots related to this plugin and additional documentation please \r\nvisit http:\/\/www.gomezprado.com\/ece\/code\/ide-vim","install_details":"In Linux:\r\nPlace the following files [1-4] at ~\/vim\/icons\r\n\r\n [1] ideClose.png\r\n [2] ideEdit.png\r\n [3] ideOpen.png\r\n [4] ideReadOnly.png\r\n\r\nThen move the files [5-6] to ~\/vim\/pluggins\r\n\r\n [5] ide.vim\r\n [6] ideSyntax.pl\r\n\r\nmake sure that ideSyntax.pl has execution properties\r\nas this perl script is used by the ide plugin to generate\r\nhighlight syntax coloring for C\/C++ files.\r\n\r\nMove the file [7] to ~\/vim\/doc\r\n\r\n  [7] ide.txt\r\n\r\nAfter moving the previous file, execute within vim\r\n\r\n  :helptags ~\/vim\/doc\r\n  :help ide\r\n\r\nOptionally, you can place file [8] within your path to\r\ngenerate or load project-files. After reading this readme\r\nyou can delete it.\r\n\r\n  [8] ide.sh\r\n  [9] ide.readme (this file)\r\n\r\nWithin the tar there is a folder call ide-screenshots with some screen shots of the plugin.\r\n\r\nIn Windows:\r\nFollow the instructions provided in the Linux section \r\nbut change the root folder ~\/vim by $VIM\/vimfiles where\r\nthe value of $VIM can be obtained by typing :echo $VIM\r\nin your current vim window.","5":"In Linux:\r\nPlace the following files [1-4] at ~\/vim\/icons\r\n\r\n [1] ideClose.png\r\n [2] ideEdit.png\r\n [3] ideOpen.png\r\n [4] ideReadOnly.png\r\n\r\nThen move the files [5-6] to ~\/vim\/pluggins\r\n\r\n [5] ide.vim\r\n [6] ideSyntax.pl\r\n\r\nmake sure that ideSyntax.pl has execution properties\r\nas this perl script is used by the ide plugin to generate\r\nhighlight syntax coloring for C\/C++ files.\r\n\r\nMove the file [7] to ~\/vim\/doc\r\n\r\n  [7] ide.txt\r\n\r\nAfter moving the previous file, execute within vim\r\n\r\n  :helptags ~\/vim\/doc\r\n  :help ide\r\n\r\nOptionally, you can place file [8] within your path to\r\ngenerate or load project-files. After reading this readme\r\nyou can delete it.\r\n\r\n  [8] ide.sh\r\n  [9] ide.readme (this file)\r\n\r\nWithin the tar there is a folder call ide-screenshots with some screen shots of the plugin.\r\n\r\nIn Windows:\r\nFollow the instructions provided in the Linux section \r\nbut change the root folder ~\/vim by $VIM\/vimfiles where\r\nthe value of $VIM can be obtained by typing :echo $VIM\r\nin your current vim window.","first_name":"Daniel","6":"Daniel","last_name":"Gomez-Prado","7":"Gomez-Prado","releases":[{"0":"3855","vim_version":"7.0","1":"7.0","script_version":"1.44","2":"1.44","version_comment":"Minor fix to update the code highlighting feature after modifying the ideSyntax.pl script.","3":"Minor fix to update the code highlighting feature after modifying the ideSyntax.pl script.","package":"ide.tar","4":"ide.tar","src_id":"19207","5":"19207","creation_date":"1355889974","6":"1355889974"},{"0":"3855","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"ide.tar","4":"ide.tar","src_id":"17101","5":"17101","creation_date":"1324530092","6":"1324530092"}]},"3854":{"script_id":"3854","0":"3854","script_name":"unite-scriptenames","1":"unite-scriptenames","script_type":"utility","2":"utility","summary":"a Unite.vim plugin to find\/open runtime scriptnames","3":"a Unite.vim plugin to find\/open runtime scriptnames","description":"unite-scriptnames [1] is a Unite.vim [2] plugin to find\/open runtime\r\nscriptnames.\r\n\r\nRequirement:\r\n\r\n+ unite.vim\r\n\r\nLatest version: git:\/\/github.com\/zhaocai\/unite-scriptnames.git\r\n\r\n==============================================================================\r\nInstallation ~\r\n\r\nPlease refer to the installation instruction from Unite.vim [2]\r\n\r\n==============================================================================\r\nReferences ~\r\n\r\n[1] https:\/\/github.com\/zhaocai\/unite-scriptnames\r\n[2] https:\/\/github.com\/Shougo\/unite.vim\r\n","4":"unite-scriptnames [1] is a Unite.vim [2] plugin to find\/open runtime\r\nscriptnames.\r\n\r\nRequirement:\r\n\r\n+ unite.vim\r\n\r\nLatest version: git:\/\/github.com\/zhaocai\/unite-scriptnames.git\r\n\r\n==============================================================================\r\nInstallation ~\r\n\r\nPlease refer to the installation instruction from Unite.vim [2]\r\n\r\n==============================================================================\r\nReferences ~\r\n\r\n[1] https:\/\/github.com\/zhaocai\/unite-scriptnames\r\n[2] https:\/\/github.com\/Shougo\/unite.vim\r\n","install_details":"↑","5":"↑","first_name":"Zhao","6":"Zhao","last_name":"Cai","7":"Cai","releases":[{"0":"3854","vim_version":"7.2","1":"7.2","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"unite-scriptnames.zip","4":"unite-scriptnames.zip","src_id":"17099","5":"17099","creation_date":"1324516092","6":"1324516092"}]},"3853":{"script_id":"3853","0":"3853","script_name":"dokuwiki","1":"dokuwiki","script_type":"utility","2":"utility","summary":"use vim as your personal wiki using dokuwiki syntax","3":"use vim as your personal wiki using dokuwiki syntax","description":"use vim as your personal wiki \r\n\r\nuses dokuwiki syntax for wiki\r\n       http:\/\/dokuwiki.org\/syntax\r\n\r\nsupports inline source higlight for embeded code","4":"use vim as your personal wiki \r\n\r\nuses dokuwiki syntax for wiki\r\n       http:\/\/dokuwiki.org\/syntax\r\n\r\nsupports inline source higlight for embeded code","install_details":"","5":"","first_name":"Ali","6":"Ali","last_name":"Vakilzade","7":"Vakilzade","releases":[{"0":"3853","vim_version":"7.0","1":"7.0","script_version":"1","2":"1","version_comment":"Initial upload","3":"Initial upload","package":"dokuwiki-1.tar","4":"dokuwiki-1.tar","src_id":"17098","5":"17098","creation_date":"1324506929","6":"1324506929"}]},"3852":{"script_id":"3852","0":"3852","script_name":"Festoon","1":"Festoon","script_type":"color scheme","2":"color scheme","summary":"Light colorscheme with dark option","3":"Light colorscheme with dark option","description":"Festoon is intended to beautify Vim, and defines as many different elements as possible, and bends over backwards to accommodate various syntax and plugins (including VimWiki, NERDtree, Netrw, TwitVim, and Viki).\r\n\r\nHTML is given a more subdued sub-colorscheme in order to differentiate it from other text and code within the same file. Header levels are fully supported.\r\n\r\nA built-in function is included for toggling from light to dark. You don't have to specify one or the other in VIMRC, you can just change on the fly as your mood or lighting dictates.\r\n\r\nSamples online:\r\nhtml\/Festoon: http:\/\/antelucan.com\/vimupdate\/f\/festoon-html.html\r\nhtml\/Festoon(dark): http:\/\/antelucan.com\/vimupdate\/f\/festoon-dark-html.html\r\nnetrw\/Festoon: http:\/\/antelucan.com\/vimupdate\/f\/festoon-netrw.html\r\nTwitVim\/Festoon: http:\/\/antelucan.com\/vimupdate\/f\/festoon-twitvim.html\r\nCalendar\/Festoon: http:\/\/antelucan.com\/vimupdate\/f\/festoon-calendar.html\r\n","4":"Festoon is intended to beautify Vim, and defines as many different elements as possible, and bends over backwards to accommodate various syntax and plugins (including VimWiki, NERDtree, Netrw, TwitVim, and Viki).\r\n\r\nHTML is given a more subdued sub-colorscheme in order to differentiate it from other text and code within the same file. Header levels are fully supported.\r\n\r\nA built-in function is included for toggling from light to dark. You don't have to specify one or the other in VIMRC, you can just change on the fly as your mood or lighting dictates.\r\n\r\nSamples online:\r\nhtml\/Festoon: http:\/\/antelucan.com\/vimupdate\/f\/festoon-html.html\r\nhtml\/Festoon(dark): http:\/\/antelucan.com\/vimupdate\/f\/festoon-dark-html.html\r\nnetrw\/Festoon: http:\/\/antelucan.com\/vimupdate\/f\/festoon-netrw.html\r\nTwitVim\/Festoon: http:\/\/antelucan.com\/vimupdate\/f\/festoon-twitvim.html\r\nCalendar\/Festoon: http:\/\/antelucan.com\/vimupdate\/f\/festoon-calendar.html\r\n","install_details":"Save the file to the 'colors' directory and type\r\n\r\n    :colo festoon\r\n\r\nThe following functions are available for toggling between dark and light, and low and high contrast.\r\n\r\n    :call BgToggle()\r\n    :call FestConToggle()","5":"Save the file to the 'colors' directory and type\r\n\r\n    :colo festoon\r\n\r\nThe following functions are available for toggling between dark and light, and low and high contrast.\r\n\r\n    :call BgToggle()\r\n    :call FestConToggle()","first_name":"carson","6":"carson","last_name":"fire","7":"fire","releases":[{"0":"3852","vim_version":"7.3","1":"7.3","script_version":"1.3","2":"1.3","version_comment":"Added background highlight to headers for even greater clarity; added more definitions to accommodate text emphasis within other defined blocks (specifically for hybrid text syntax).","3":"Added background highlight to headers for even greater clarity; added more definitions to accommodate text emphasis within other defined blocks (specifically for hybrid text syntax).","package":"festoon.vim","4":"festoon.vim","src_id":"18458","5":"18458","creation_date":"1345668855","6":"1345668855"},{"0":"3852","vim_version":"7.3","1":"7.3","script_version":"1.2","2":"1.2","version_comment":"High contrast option included.","3":"High contrast option included.","package":"festoon.vim","4":"festoon.vim","src_id":"18023","5":"18023","creation_date":"1337809670","6":"1337809670"},{"0":"3852","vim_version":"7.0","1":"7.0","script_version":"1.1","2":"1.1","version_comment":"More colors, dark version improved.","3":"More colors, dark version improved.","package":"festoon.vim","4":"festoon.vim","src_id":"17989","5":"17989","creation_date":"1337309235","6":"1337309235"},{"0":"3852","vim_version":"7.3","1":"7.3","script_version":"1","2":"1","version_comment":"Initial upload","3":"Initial upload","package":"festoon.vim","4":"festoon.vim","src_id":"17094","5":"17094","creation_date":"1324431890","6":"1324431890"}]},"3851":{"script_id":"3851","0":"3851","script_name":"Mark-Ring","1":"Mark-Ring","script_type":"utility","2":"utility","summary":"Cycle through your marks.","3":"Cycle through your marks.","description":"Maps <leader>m and <leader>M to cycle through your marks alphabetically and\r\nreverse alphabetically, respectively.\r\n\r\nOnly cycles through alphabetic marks, though that's easy to change if you edit \r\nthe script.\r\n\r\nRequires Vim to be compiled with Python support.\r\nHosted at https:\/\/github.com\/michaelnussbaum08\/Mark-Ring","4":"Maps <leader>m and <leader>M to cycle through your marks alphabetically and\r\nreverse alphabetically, respectively.\r\n\r\nOnly cycles through alphabetic marks, though that's easy to change if you edit \r\nthe script.\r\n\r\nRequires Vim to be compiled with Python support.\r\nHosted at https:\/\/github.com\/michaelnussbaum08\/Mark-Ring","install_details":"Just unpack it and drop it in your <VIMHOME>\/plugins directory.","5":"Just unpack it and drop it in your <VIMHOME>\/plugins directory.","first_name":"Michael","6":"Michael","last_name":"Nussbaum","7":"Nussbaum","releases":[{"0":"3851","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"mark_ring.tgz","4":"mark_ring.tgz","src_id":"17091","5":"17091","creation_date":"1324324299","6":"1324324299"}]},"3850":{"script_id":"3850","0":"3850","script_name":"boolpat.vim","1":"boolpat.vim","script_type":"utility","2":"utility","summary":"Boolean-logic patterns, based on LogiPat","3":"Boolean-logic patterns, based on LogiPat","description":"This is just like vimscript #1290 but with simpler syntax.\r\n\r\n:BoolPat {expr}\r\n\r\nconverts boolean-logic pattern {expr} into a normal regexp pattern and searches for it.  Basically, {expr} can be any regexp pattern with some special characters in it for boolean operators:\r\n\r\n\t! is logical NOT, | or || is logical OR, & or && is logical AND\r\n\t(...) is for grouping, whitespace separates items, '...' quotes characters\r\n\r\nQuoting: Single quotes '...' literally include special characters and whitespace in the pattern.  Two single quotes '' result in one single quote, inside or outside of '...'.\r\n\r\n:BoolPat abc\r\nwill search for lines containing the string \"abc\", using the pattern .*abc.*\r\n\r\n:BoolPat !abc\r\nwill search for lines which don't contain the string \"abc\", using the pattern ^\\%(\\%(abc\\)\\@!.\\)*$\r\n\r\n:BoolPat abc|def\r\nwill search for lines which contain either the string \"abc\" or the string \"def\"\r\n\r\n:BoolPat !(abc | def)\r\nwill search for lines which don't contain either of the strings \"abc\" or \"def\"\r\n\r\n:BoolPat abc & def\r\nwill search for lines which contain both of the strings \"abc\" and \"def\" \r\n\r\n:BoolPat abc' & ''def'\r\nwill search for lines which contain the string \"abc & 'def\"\r\n\r\n:BoolPat abc''def\r\nwill search for lines which contain the string \"abc'def\"","4":"This is just like vimscript #1290 but with simpler syntax.\r\n\r\n:BoolPat {expr}\r\n\r\nconverts boolean-logic pattern {expr} into a normal regexp pattern and searches for it.  Basically, {expr} can be any regexp pattern with some special characters in it for boolean operators:\r\n\r\n\t! is logical NOT, | or || is logical OR, & or && is logical AND\r\n\t(...) is for grouping, whitespace separates items, '...' quotes characters\r\n\r\nQuoting: Single quotes '...' literally include special characters and whitespace in the pattern.  Two single quotes '' result in one single quote, inside or outside of '...'.\r\n\r\n:BoolPat abc\r\nwill search for lines containing the string \"abc\", using the pattern .*abc.*\r\n\r\n:BoolPat !abc\r\nwill search for lines which don't contain the string \"abc\", using the pattern ^\\%(\\%(abc\\)\\@!.\\)*$\r\n\r\n:BoolPat abc|def\r\nwill search for lines which contain either the string \"abc\" or the string \"def\"\r\n\r\n:BoolPat !(abc | def)\r\nwill search for lines which don't contain either of the strings \"abc\" or \"def\"\r\n\r\n:BoolPat abc & def\r\nwill search for lines which contain both of the strings \"abc\" and \"def\" \r\n\r\n:BoolPat abc' & ''def'\r\nwill search for lines which contain the string \"abc & 'def\"\r\n\r\n:BoolPat abc''def\r\nwill search for lines which contain the string \"abc'def\"","install_details":"","5":"","first_name":"Andy","6":"Andy","last_name":"Wokula","7":"Wokula","releases":[{"0":"3850","vim_version":"7.0","1":"7.0","script_version":"0.1.1","2":"0.1.1","version_comment":"BF: now adds the search pattern to the search history","3":"BF: now adds the search pattern to the search history","package":"boolpat.vim","4":"boolpat.vim","src_id":"17329","5":"17329","creation_date":"1327786177","6":"1327786177"},{"0":"3850","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"boolpat.vim","4":"boolpat.vim","src_id":"17087","5":"17087","creation_date":"1324295369","6":"1324295369"}]},"3849":{"script_id":"3849","0":"3849","script_name":"git-time-lapse","1":"git-time-lapse","script_type":"utility","2":"utility","summary":"Perforce-style ","3":"Perforce-style ","description":"You're editing a file which is in a git repository. Press a key which opens a new tab which shows how that commit changed that file in vim's diff mode (:help diff), with a window at the bottom showing the commit message. Left and right arrows move through the history. Shift-left and shift-right go all the way to the end. Return on a line goes back to the last commit that touched that line (using git blame). \r\n\r\nClose the tab when you're bored with it and carry on vimming as usual. You can open as many time-lapse tabs on different files in one vim session as you want.\r\n\r\nInspired by the \"time lapse view\" in the Perforce gui which I thought was quite good, although I prefer the vim version.","4":"You're editing a file which is in a git repository. Press a key which opens a new tab which shows how that commit changed that file in vim's diff mode (:help diff), with a window at the bottom showing the commit message. Left and right arrows move through the history. Shift-left and shift-right go all the way to the end. Return on a line goes back to the last commit that touched that line (using git blame). \r\n\r\nClose the tab when you're bored with it and carry on vimming as usual. You can open as many time-lapse tabs on different files in one vim session as you want.\r\n\r\nInspired by the \"time lapse view\" in the Perforce gui which I thought was quite good, although I prefer the vim version.","install_details":"Drop time-lapse.vim into .vim\/plugin and map a key in your .vimrc, e.g.\r\n\r\nmap <leader>gt :call TimeLapse() <cr>\r\n\r\nOr however you prefer.\r\n\r\nYou can also get the script with:\r\n\r\n$ git clone http:\/\/www.tidraso.co.uk\/repository\/vim-plugin\/\r\n\r\nWhere you may find new features.","5":"Drop time-lapse.vim into .vim\/plugin and map a key in your .vimrc, e.g.\r\n\r\nmap <leader>gt :call TimeLapse() <cr>\r\n\r\nOr however you prefer.\r\n\r\nYou can also get the script with:\r\n\r\n$ git clone http:\/\/www.tidraso.co.uk\/repository\/vim-plugin\/\r\n\r\nWhere you may find new features.","first_name":"Ben","6":"Ben","last_name":"Cotterell","7":"Cotterell","releases":[{"0":"3849","vim_version":"7.0","1":"7.0","script_version":"1.5","2":"1.5","version_comment":"Move to top if the original starting point no longer exists in the revision currently being viewed.","3":"Move to top if the original starting point no longer exists in the revision currently being viewed.","package":"time-lapse.vim","4":"time-lapse.vim","src_id":"22637","5":"22637","creation_date":"1416583793","6":"1416583793"},{"0":"3849","vim_version":"7.0","1":"7.0","script_version":"1.4","2":"1.4","version_comment":"Restore cursor position while moving through revisions, so you can look at changes to the part of the file you're interested in. Thanks to Caroline Kikisch for pointing out the problem.","3":"Restore cursor position while moving through revisions, so you can look at changes to the part of the file you're interested in. Thanks to Caroline Kikisch for pointing out the problem.","package":"time-lapse.vim","4":"time-lapse.vim","src_id":"22633","5":"22633","creation_date":"1416485028","6":"1416485028"},{"0":"3849","vim_version":"7.0","1":"7.0","script_version":"1.3","2":"1.3","version_comment":"Restore cursor after opening time-lapse tab, so you can immediately do a Blame from there (common use case). So ,gt <Enter> does a quick blame.","3":"Restore cursor after opening time-lapse tab, so you can immediately do a Blame from there (common use case). So ,gt <Enter> does a quick blame.","package":"time-lapse.vim","4":"time-lapse.vim","src_id":"19796","5":"19796","creation_date":"1365622632","6":"1365622632"},{"0":"3849","vim_version":"7.0","1":"7.0","script_version":"1.2","2":"1.2","version_comment":"Incorporate bug fixes from chronial, including improved Win32 support.","3":"Incorporate bug fixes from chronial, including improved Win32 support.","package":"time-lapse.vim","4":"time-lapse.vim","src_id":"19667","5":"19667","creation_date":"1363789353","6":"1363789353"},{"0":"3849","vim_version":"7.0","1":"7.0","script_version":"1.1","2":"1.1","version_comment":"Bug fix for Blame operation across renames.","3":"Bug fix for Blame operation across renames.","package":"time-lapse.vim","4":"time-lapse.vim","src_id":"19506","5":"19506","creation_date":"1360753592","6":"1360753592"},{"0":"3849","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"time-lapse.vim","4":"time-lapse.vim","src_id":"17077","5":"17077","creation_date":"1324115521","6":"1324115521"}]},"3848":{"script_id":"3848","0":"3848","script_name":"visualrepeat","1":"visualrepeat","script_type":"utility","2":"utility","summary":"Repeat command extended to visual mode. ","3":"Repeat command extended to visual mode. ","description":"DESCRIPTION\r\nThis plugin defines repetition of Vim built-in normal mode commands via .\r\nfor visual mode. Additionally, it offers functions like the popular repeat.vim\r\nplugin that allow mappings to be repeated in visual mode, too.\r\n\r\nVISUAL MODE REPETITION\r\nThis extends the built-in normal mode repeat . to visual mode.\r\n\r\nVISUAL MODE MAPPING REPETITION\r\nLike with repeat.vim for normal mode, visual mode mappings can register a\r\n<Plug> mapping to be used for visual mode repetition.\r\n\r\nLikewise, normal mode mappings can (in addition to the repeat.vim registration\r\nof a normal mode mapping) register a visual mode mapping with visualrepeat.vim\r\nthat will be repeated in visual mode.\r\n\r\nOperator-pending mappings end with g@ and repeat naturally; i.e. Vim\r\nre-applies the 'opfunc' on the equivalent text (but at the current cursor\r\nposition). But without a call to repeat#set(), it is impossible to repeat this\r\noperator-pending mapping to the current visual selection. Plugins cannot call\r\nrepeat#set() in their operator-pending mapping, because then Vim's built-in\r\nrepeat would be circumvented, the full mapping ending with g@ would be\r\nre-executed, and the repetition would then wait for the {motion}, what is not\r\nwanted.\r\nTherefore, this plugin offers a separate visualrepeat#set() function that can\r\nbe invoked for operator-pending mappings. It can also be invoked for\r\nnormal-mode mappings that have already called repeat#set(), and may override\r\nthat mapping with a special repeat mapping for visual mode repeats. Together\r\nwith the remapped {Visual}. command, this allows repetition - similar to what\r\nthe built-in Vim commands do - across normal, operator-pending and visual\r\nmode.\r\n\r\nSOURCE\r\n- Based on vimtip #1142, Repeat last command and put cursor at start of change\r\n    http:\/\/vim.wikia.com\/wiki\/Repeat_last_command_and_put_cursor_at_start_of_change\r\n- The client interface and implementation has been based on repeat.vim\r\n  (vimscript #2136) by Tim Pope.\r\n\r\nRELATED WORKS\r\n- repeat.vim (vimscript #2136) has been the basis for this plugin and should\r\n  be used in conjunction with visualrepeat.vim. (Otherwise, you'd have visual\r\n  mode repeat, but no repeat in normal mode.)\r\n\r\nUSAGE\r\n{Visual}.               Repeat last change in all visually selected lines.\r\n                        - characterwise: Start from cursor position.\r\n                        - linewise: Each line separately, starting from the\r\n                          current column (usually the first in this mode).\r\n                        - blockwise: Only the selected text. This is\r\n                          implemented by temporarily duplicating the selection\r\n                          to separate lines and repeating over those, starting\r\n                          from the first column.\r\n\r\n                        Note: If the last normal mode command included a\r\n                        {motion} (e.g. g~e), the repetition will also move\r\n                        exactly over this {motion}, NOT the visual selection!\r\n                        It is thus best to repeat commands that work on the\r\n                        entire line (e.g. g~$).\r\n\r\n{Visual}g.              Repeat last built-in command in all visually selected\r\n                        lines. Skips any plugin repeat actions; only repeats\r\n                        the last Vim command.","4":"DESCRIPTION\r\nThis plugin defines repetition of Vim built-in normal mode commands via .\r\nfor visual mode. Additionally, it offers functions like the popular repeat.vim\r\nplugin that allow mappings to be repeated in visual mode, too.\r\n\r\nVISUAL MODE REPETITION\r\nThis extends the built-in normal mode repeat . to visual mode.\r\n\r\nVISUAL MODE MAPPING REPETITION\r\nLike with repeat.vim for normal mode, visual mode mappings can register a\r\n<Plug> mapping to be used for visual mode repetition.\r\n\r\nLikewise, normal mode mappings can (in addition to the repeat.vim registration\r\nof a normal mode mapping) register a visual mode mapping with visualrepeat.vim\r\nthat will be repeated in visual mode.\r\n\r\nOperator-pending mappings end with g@ and repeat naturally; i.e. Vim\r\nre-applies the 'opfunc' on the equivalent text (but at the current cursor\r\nposition). But without a call to repeat#set(), it is impossible to repeat this\r\noperator-pending mapping to the current visual selection. Plugins cannot call\r\nrepeat#set() in their operator-pending mapping, because then Vim's built-in\r\nrepeat would be circumvented, the full mapping ending with g@ would be\r\nre-executed, and the repetition would then wait for the {motion}, what is not\r\nwanted.\r\nTherefore, this plugin offers a separate visualrepeat#set() function that can\r\nbe invoked for operator-pending mappings. It can also be invoked for\r\nnormal-mode mappings that have already called repeat#set(), and may override\r\nthat mapping with a special repeat mapping for visual mode repeats. Together\r\nwith the remapped {Visual}. command, this allows repetition - similar to what\r\nthe built-in Vim commands do - across normal, operator-pending and visual\r\nmode.\r\n\r\nSOURCE\r\n- Based on vimtip #1142, Repeat last command and put cursor at start of change\r\n    http:\/\/vim.wikia.com\/wiki\/Repeat_last_command_and_put_cursor_at_start_of_change\r\n- The client interface and implementation has been based on repeat.vim\r\n  (vimscript #2136) by Tim Pope.\r\n\r\nRELATED WORKS\r\n- repeat.vim (vimscript #2136) has been the basis for this plugin and should\r\n  be used in conjunction with visualrepeat.vim. (Otherwise, you'd have visual\r\n  mode repeat, but no repeat in normal mode.)\r\n\r\nUSAGE\r\n{Visual}.               Repeat last change in all visually selected lines.\r\n                        - characterwise: Start from cursor position.\r\n                        - linewise: Each line separately, starting from the\r\n                          current column (usually the first in this mode).\r\n                        - blockwise: Only the selected text. This is\r\n                          implemented by temporarily duplicating the selection\r\n                          to separate lines and repeating over those, starting\r\n                          from the first column.\r\n\r\n                        Note: If the last normal mode command included a\r\n                        {motion} (e.g. g~e), the repetition will also move\r\n                        exactly over this {motion}, NOT the visual selection!\r\n                        It is thus best to repeat commands that work on the\r\n                        entire line (e.g. g~$).\r\n\r\n{Visual}g.              Repeat last built-in command in all visually selected\r\n                        lines. Skips any plugin repeat actions; only repeats\r\n                        the last Vim command.","install_details":"INSTALLATION\r\nThe code is hosted in a Git repo at\r\n    https:\/\/github.com\/inkarkat\/vim-visualrepeat\r\nYou can use your favorite plugin manager, or \"git clone\" into a directory used\r\nfor Vim packages. Releases are on the \"stable\" branch, the latest unstable\r\ndevelopment snapshot on \"master\".\r\n\r\nThis script is also packaged as a vimball. If you have the \"gunzip\"\r\ndecompressor in your PATH, simply edit the *.vmb.gz package in Vim; otherwise,\r\ndecompress the archive first, e.g. using WinZip. Inside Vim, install by\r\nsourcing the vimball or via the :UseVimball command.\r\n    vim visualrepeat*.vmb.gz\r\n    :so %\r\nTo uninstall, use the :RmVimball command.\r\n\r\nDEPENDENCIES\r\n- Requires Vim 7.0 or higher.\r\n- repeat.vim (vimscript #2136) plugin (highly recommended)\r\n- ingo-library.vim plugin (vimscript #4433), version 1.013 or higher;\r\n  optional, for blockwise repeat only\r\n\r\nINTEGRATION\r\nThis plugin is meant to be used together with repeat.vim.\r\n\r\nThis plugin has helper functions that plugins with cross-repeat functionality\r\ncan use in their normal mode repeat mappings of repeated visual mode mappings.\r\nWith this, you save work and allow for a consistent user experience.\r\nDefine your normal mode repeat mapping like this:\r\n    nnoremap <silent> <Plug>(MyPluginVisual)\r\n    \\ :<C-u>execute 'normal!' visualrepeat#reapply#VisualMode(0)<Bar>\r\n    \\call MyPlugin#Operator('visual', \"\\<lt>Plug>(MyPluginVisual)\")<CR>\r\nIf your plugin uses a passed [count] (i.e. the count is not only used to\r\ndetermine the text area the mapping is applied to), you need to define a\r\nmapping:\r\n    vnoremap <silent> <expr> <SID>(ReapplyRepeatCount) visualrepeat#reapply#RepeatCount()\r\nand apply the function followed by the mapping like this:\r\n    nnoremap <silent> <script> <Plug>(MyPluginVisual)\r\n    \\ :<C-u>execute 'normal!' visualrepeat#reapply#VisualMode(1)<CR>\r\n    \\<SID>(ReapplyRepeatCount)\r\n    \\:<C-u>call MyPlugin#Operator('visual', v:count, \"\\<lt>Plug>(MyPluginVisual)\")<CR>\r\nIf you want to support running without visualrepeat.vim, too, provide a\r\nwrapper that defaults to 1v:\r\n    function! s:VisualMode()\r\n        let l:keys = \"1v\\<Esc>\"\r\n        silent! let l:keys = visualrepeat#reapply#VisualMode(0)\r\n        return l:keys\r\n    endfunction\r\n    nnoremap <silent> <Plug>(MyPluginVisual)\r\n    \\ :<C-u>execute 'normal!' <SID>VisualMode()<Bar>\r\n    \\call MyPlugin#Operator('visual', \"\\<lt>Plug>(MyPluginVisual)\")<CR>","5":"INSTALLATION\r\nThe code is hosted in a Git repo at\r\n    https:\/\/github.com\/inkarkat\/vim-visualrepeat\r\nYou can use your favorite plugin manager, or \"git clone\" into a directory used\r\nfor Vim packages. Releases are on the \"stable\" branch, the latest unstable\r\ndevelopment snapshot on \"master\".\r\n\r\nThis script is also packaged as a vimball. If you have the \"gunzip\"\r\ndecompressor in your PATH, simply edit the *.vmb.gz package in Vim; otherwise,\r\ndecompress the archive first, e.g. using WinZip. Inside Vim, install by\r\nsourcing the vimball or via the :UseVimball command.\r\n    vim visualrepeat*.vmb.gz\r\n    :so %\r\nTo uninstall, use the :RmVimball command.\r\n\r\nDEPENDENCIES\r\n- Requires Vim 7.0 or higher.\r\n- repeat.vim (vimscript #2136) plugin (highly recommended)\r\n- ingo-library.vim plugin (vimscript #4433), version 1.013 or higher;\r\n  optional, for blockwise repeat only\r\n\r\nINTEGRATION\r\nThis plugin is meant to be used together with repeat.vim.\r\n\r\nThis plugin has helper functions that plugins with cross-repeat functionality\r\ncan use in their normal mode repeat mappings of repeated visual mode mappings.\r\nWith this, you save work and allow for a consistent user experience.\r\nDefine your normal mode repeat mapping like this:\r\n    nnoremap <silent> <Plug>(MyPluginVisual)\r\n    \\ :<C-u>execute 'normal!' visualrepeat#reapply#VisualMode(0)<Bar>\r\n    \\call MyPlugin#Operator('visual', \"\\<lt>Plug>(MyPluginVisual)\")<CR>\r\nIf your plugin uses a passed [count] (i.e. the count is not only used to\r\ndetermine the text area the mapping is applied to), you need to define a\r\nmapping:\r\n    vnoremap <silent> <expr> <SID>(ReapplyRepeatCount) visualrepeat#reapply#RepeatCount()\r\nand apply the function followed by the mapping like this:\r\n    nnoremap <silent> <script> <Plug>(MyPluginVisual)\r\n    \\ :<C-u>execute 'normal!' visualrepeat#reapply#VisualMode(1)<CR>\r\n    \\<SID>(ReapplyRepeatCount)\r\n    \\:<C-u>call MyPlugin#Operator('visual', v:count, \"\\<lt>Plug>(MyPluginVisual)\")<CR>\r\nIf you want to support running without visualrepeat.vim, too, provide a\r\nwrapper that defaults to 1v:\r\n    function! s:VisualMode()\r\n        let l:keys = \"1v\\<Esc>\"\r\n        silent! let l:keys = visualrepeat#reapply#VisualMode(0)\r\n        return l:keys\r\n    endfunction\r\n    nnoremap <silent> <Plug>(MyPluginVisual)\r\n    \\ :<C-u>execute 'normal!' <SID>VisualMode()<Bar>\r\n    \\call MyPlugin#Operator('visual', \"\\<lt>Plug>(MyPluginVisual)\")<CR>","first_name":"Ingo","6":"Ingo","last_name":"Karkat","7":"Karkat","releases":[{"0":"3848","vim_version":"7.0","1":"7.0","script_version":"1.32","2":"1.32","version_comment":"- BUG: visualrepeat#reapply#VisualMode() mistakenly adds the next full line when restoring a linewise visual selection (to a smaller target).\r\n- Use :normal for Vim 7.3.100..7.4.601 and feedkeys(..., 'i') for newer versions, aligning the used mechanism with what repeat.vim uses.","3":"- BUG: visualrepeat#reapply#VisualMode() mistakenly adds the next full line when restoring a linewise visual selection (to a smaller target).\r\n- Use :normal for Vim 7.3.100..7.4.601 and feedkeys(..., 'i') for newer versions, aligning the used mechanism with what repeat.vim uses.","package":"visualrepeat-1.32.vmb.gz","4":"visualrepeat-1.32.vmb.gz","src_id":"27029","5":"27029","creation_date":"1582515422","6":"1582515422"},{"0":"3848","vim_version":"7.0","1":"7.0","script_version":"1.31","2":"1.31","version_comment":"- ENH: Add g. mapping that forces built-in repeat; i.e. skips any custom repeat.vim or visualrepeat.vim actions. This can be useful if a plugin offers a special repeat for visual mode, but a built-in repeat on each selected line may make sense, too. For example, my KeepText.vim plugin would keep the entire linewise selection; forcing a built-in repeat (of the custom operator) would reapply e.g. a <Leader>ka\" to all selected lines instead.\r\n- Factor out ingo#buffer#temprange#Call() into ingo-library. *** You need to update the optional dependency to ingo-library (vimscript #4433) version 1.018! ***\r\n- ENH: Make an explicit register on repeat override g:repeat_reg. As with built-in commands, this allows to override the original register on repeat, e.g. \"a. uses register a instead of the original one. One limitation is that we cannot detect whether no or the default register has been given, so an override from a non-default to the default register (e.g. via \"\".) is not possible.","3":"- ENH: Add g. mapping that forces built-in repeat; i.e. skips any custom repeat.vim or visualrepeat.vim actions. This can be useful if a plugin offers a special repeat for visual mode, but a built-in repeat on each selected line may make sense, too. For example, my KeepText.vim plugin would keep the entire linewise selection; forcing a built-in repeat (of the custom operator) would reapply e.g. a <Leader>ka\" to all selected lines instead.\r\n- Factor out ingo#buffer#temprange#Call() into ingo-library. *** You need to update the optional dependency to ingo-library (vimscript #4433) version 1.018! ***\r\n- ENH: Make an explicit register on repeat override g:repeat_reg. As with built-in commands, this allows to override the original register on repeat, e.g. \"a. uses register a instead of the original one. One limitation is that we cannot detect whether no or the default register has been given, so an override from a non-default to the default register (e.g. via \"\".) is not possible.","package":"visualrepeat-1.31.vmb.gz","4":"visualrepeat-1.31.vmb.gz","src_id":"26423","5":"26423","creation_date":"1552880437","6":"1552880437"},{"0":"3848","vim_version":"7.0","1":"7.0","script_version":"1.30","2":"1.30","version_comment":"- ENH: When repeating over multiple lines \/ a blockwise selection, keep track of added or deleted lines, and only repeat exactly on the selected lines. Thanks to Israel Chauca for sending a patch!\r\n- When a repeat on a blockwise selection has introduced additional lines, append those properly indented instead of omitting them.\r\n- With linewise and blockwise repeat, set the change marks '[,'] to the changed selection. With the latter, one previously got \"E19: Mark has invalid line number\" due to the removed temporary range.","3":"- ENH: When repeating over multiple lines \/ a blockwise selection, keep track of added or deleted lines, and only repeat exactly on the selected lines. Thanks to Israel Chauca for sending a patch!\r\n- When a repeat on a blockwise selection has introduced additional lines, append those properly indented instead of omitting them.\r\n- With linewise and blockwise repeat, set the change marks '[,'] to the changed selection. With the latter, one previously got \"E19: Mark has invalid line number\" due to the removed temporary range.","package":"visualrepeat-1.30.vmb.gz","4":"visualrepeat-1.30.vmb.gz","src_id":"21046","5":"21046","creation_date":"1384527470","6":"1384527470"},{"0":"3848","vim_version":"7.0","1":"7.0","script_version":"1.20","2":"1.20","version_comment":"- ENH: Implement blockwise repeat through temporarily moving the block to a temporary range at the end of the buffer, like the vis.vim plugin. This feature requires the ingo-library. *** You need to separately install ingo-library (vimscript #4433) version 1.013 (or higher)! ***","3":"- ENH: Implement blockwise repeat through temporarily moving the block to a temporary range at the end of the buffer, like the vis.vim plugin. This feature requires the ingo-library. *** You need to separately install ingo-library (vimscript #4433) version 1.013 (or higher)! ***","package":"visualrepeat-1.20.vmb.gz","4":"visualrepeat-1.20.vmb.gz","src_id":"21043","5":"21043","creation_date":"1384434143","6":"1384434143"},{"0":"3848","vim_version":"7.0","1":"7.0","script_version":"1.10","2":"1.10","version_comment":"- Check for existence of actual visual mode mapping; do not accept a select mode mapping, because we're applying it to a visual selection.\r\n- Pass through a [count] to the :normal . command.\r\n- Add visualrepeat#reapply#VisualMode() and visualrepeat#reapply#RepeatCount() helper functions that plugins can use in their normal mode repeat mappings of repeated visual mode mappings.\r\n- Minor: Make substitute() robust against 'ignorecase'.\r\n- ENH: Use the current cursor virtual column when repeating in linewise visual mode. Inspired by http:\/\/stackoverflow.com\/questions\/18610564\/vim-is-possible-to-use-dot-command-in-visual-block-mode\r\n- Abort further commands on error by using echoerr inside the mapping.","3":"- Check for existence of actual visual mode mapping; do not accept a select mode mapping, because we're applying it to a visual selection.\r\n- Pass through a [count] to the :normal . command.\r\n- Add visualrepeat#reapply#VisualMode() and visualrepeat#reapply#RepeatCount() helper functions that plugins can use in their normal mode repeat mappings of repeated visual mode mappings.\r\n- Minor: Make substitute() robust against 'ignorecase'.\r\n- ENH: Use the current cursor virtual column when repeating in linewise visual mode. Inspired by http:\/\/stackoverflow.com\/questions\/18610564\/vim-is-possible-to-use-dot-command-in-visual-block-mode\r\n- Abort further commands on error by using echoerr inside the mapping.","package":"visualrepeat-1.10.vmb.gz","4":"visualrepeat-1.10.vmb.gz","src_id":"20755","5":"20755","creation_date":"1378377649","6":"1378377649"},{"0":"3848","vim_version":"7.0","1":"7.0","script_version":"1.03","2":"1.03","version_comment":"REGRESSION: Fix in 1.02 does not repeat recorded register when the mappings in repeat.vim and visualrepeat.vim differ.","3":"REGRESSION: Fix in 1.02 does not repeat recorded register when the mappings in repeat.vim and visualrepeat.vim differ.","package":"visualrepeat-1.03.vmb.gz","4":"visualrepeat-1.03.vmb.gz","src_id":"19556","5":"19556","creation_date":"1361458060","6":"1361458060"},{"0":"3848","vim_version":"7.0","1":"7.0","script_version":"1.02","2":"1.02","version_comment":"BUG: \"E121: Undefined variable: g:repeat_sequence\" when using visual repeat of a mapping using registers without having used repeat.vim beforehand.","3":"BUG: \"E121: Undefined variable: g:repeat_sequence\" when using visual repeat of a mapping using registers without having used repeat.vim beforehand.","package":"visualrepeat-1.02.vmb.gz","4":"visualrepeat-1.02.vmb.gz","src_id":"19245","5":"19245","creation_date":"1356596536","6":"1356596536"},{"0":"3848","vim_version":"7.0","1":"7.0","script_version":"1.01","2":"1.01","version_comment":"FIX: Avoid error about undefined g:repeat_reg when (a proper version of)\r\nrepeat.vim isn't available.","3":"FIX: Avoid error about undefined g:repeat_reg when (a proper version of)\r\nrepeat.vim isn't available.","package":"visualrepeat.vba.gz","4":"visualrepeat.vba.gz","src_id":"17727","5":"17727","creation_date":"1333633318","6":"1333633318"},{"0":"3848","vim_version":"7.0","1":"7.0","script_version":"1.00","2":"1.00","version_comment":"Initial upload","3":"Initial upload","package":"visualrepeat.vba.gz","4":"visualrepeat.vba.gz","src_id":"17062","5":"17062","creation_date":"1323869262","6":"1323869262"}]},"3846":{"script_id":"3846","0":"3846","script_name":"cue.vim","1":"cue.vim","script_type":"syntax","2":"syntax","summary":"syntax highlight for .cue file","3":"syntax highlight for .cue file","description":".cue file syntax highlight","4":".cue file syntax highlight","install_details":"copy to vimfiles\/syntax\/\r\nand add this line\r\nau BufNewFile,BufRead *.cue setf cue\r\nto .vimrc or filetype.vim","5":"copy to vimfiles\/syntax\/\r\nand add this line\r\nau BufNewFile,BufRead *.cue setf cue\r\nto .vimrc or filetype.vim","first_name":"\u7530","6":"田","last_name":"\u751f","7":"生","releases":[{"0":"3846","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"cue.vim","4":"cue.vim","src_id":"17053","5":"17053","creation_date":"1323566382","6":"1323566382"}]},"3845":{"script_id":"3845","0":"3845","script_name":"lrc.vim","1":"lrc.vim","script_type":"syntax","2":"syntax","summary":"basic syntax highlight for lyric file (.lrc)","3":"basic syntax highlight for lyric file (.lrc)","description":"lrc file syntax highlight","4":"lrc file syntax highlight","install_details":"copy to vimfiles\/syntax\/\r\nand add this line:\r\nau BufNewFile,BufRead *.lrc\t\t\tsetf lrc\r\nto .vimrc or filetype.vim\r\n","5":"copy to vimfiles\/syntax\/\r\nand add this line:\r\nau BufNewFile,BufRead *.lrc\t\t\tsetf lrc\r\nto .vimrc or filetype.vim\r\n","first_name":"\u7530","6":"田","last_name":"\u751f","7":"生","releases":[{"0":"3845","vim_version":"7.0","1":"7.0","script_version":"0.2","2":"0.2","version_comment":"Added support for multi timestamps. Thanks for TT's report.","3":"Added support for multi timestamps. Thanks for TT's report.","package":"lrc.vim","4":"lrc.vim","src_id":"20950","5":"20950","creation_date":"1382609201","6":"1382609201"},{"0":"3845","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"lrc.vim","4":"lrc.vim","src_id":"17049","5":"17049","creation_date":"1323495572","6":"1323495572"}]},"3844":{"script_id":"3844","0":"3844","script_name":"SpellCheck","1":"SpellCheck","script_type":"utility","2":"utility","summary":"Work with spelling errors. ","3":"Work with spelling errors. ","description":"DESCRIPTION\r\nVim offers built-in spell checking; when you enable it via 'spell' and\r\n'spelllang', you can jump to the highlighted spelling errors in the buffer via\r\n]s. With spelling errors scattered across a large document, Vim does not\r\nprovide an overview or report about the overall spell situation.\r\n\r\nThis plugin populates the |quickfix|-list with all spelling errors found in a\r\nbuffer to give you that overview. You can use the built-in quickfix features\r\nto navigate to the first occurrence of a particular spell error. You can also\r\nmanage the spelling errors (mark as good \/ bad word, globally replace with\r\nsuggestion) directly from the quickfix window via the usual zg, zw, z=\r\netc. mappings.\r\n\r\nA typical workflow (e.g. when composing email, commit messages, or any form of\r\ndocumentation) includes writing and\/or quitting the buffer, unless some\r\nremaining spelling errors require further intervention. This plugin offers\r\nauxiliary enhanced variants of :bdelete, :write and :quit that check for\r\nspelling errors and only execute the action if none were found. So by using\r\nthese replacement commands, you'll never send or commit messages full of\r\nembarrassing typos any more!\r\n\r\nUSAGE\r\n:[range]SpellCheck[!] [bad | rare | local | caps] [...] [{predicates}]\r\n                        Show all \/ the passed type(s) of spelling errors as a\r\n                        quickfix list [at locations where {predicates} yield\r\n                        true] SpellCheck-predicates.\r\n                        For multiple occurrences of the same error, the first\r\n                        location and the number of occurrences is shown.\r\n                        If [!] is not given the first error is jumped to.\r\n\r\n                        In the quickfix list, spelling errors from other\r\n                        buffers are kept, so you can use something like\r\n                            :argdo SpellCheck\r\n                       to gather the spelling errors from multiple buffers.\r\n\r\n:[range]SpellLCheck[!] [bad | rare | local | caps] [...] [{predicates}]\r\n                        Same as :SpellCheck, except the location list for the\r\n                        current window is used instead of the quickfix list.\r\n\r\nYou can pass arbitrary Vimscript expressions that then need to match at the\r\ncurrent spell error location to consider the spelling error; else, that\r\nparticular error will be ignored. For example, the following will ignore spell\r\nerrors in a Vim modeline:\r\n    :SpellCheck getline('.') !~ 'vim:'\r\nIf you define the following syntactic sugar function (in your vimrc)\r\n    function! Syntax( pattern )\r\n        return ingo#syntaxitem#IsOnSyntax(getpos('.'), a:pattern)\r\n    endfunction\r\nyou can easily limit spell checking to certain syntax elements, e.g. to\r\nexclude spell errors inside comments:\r\n    :SpellCheck !Syntax('Comment')\r\n\r\nMAPPINGS\r\n                        Inside the quickfix window, the following mappings are\r\n                        remapped so that they operate on the target spell\r\n                        error: zg, zG, zw, zW, zug, zuG, zuw,\r\n                        zuW, z=, u\r\n                        For z=, all identical misspellings in the buffer are\r\n                        replaced with the chosen suggestion (via\r\n                        :spellrepall).\r\n                        You can also quickly undo the last spell suggestion\r\n                        from the quickfix window (i.e. without switching to\r\n                        the target buffer) via u.\r\n                        For the other commands, the taken action is appended\r\n                        to the quickfix list entry, so that the list serves as\r\n                        a record of done actions (until you refresh the list\r\n                        with a new :SpellCheck).\r\n\r\nAUXILIARY COMMANDS\r\nThe following set of commands just issue an error when spelling errors exist\r\nin the buffer or passed [range] of lines.\r\n\r\n:BDeleteUnlessSpellError[!] [bad | rare | local | caps] [...] [{predicates}]\r\n                                :bdelete| the current buffer, unless it\r\n                                contains spelling errors.\r\n:WriteUnlessSpellError[!] [bad | rare | local | caps] [...] [{predicates}]\r\n                                :write the current buffer, unless it\r\n                                contains spelling errors.\r\n:WriteDeleteUnlessSpellError[!]  [bad | rare | local | caps] [...] [{predicates}]\r\n                                :write and :bdelete the current buffer,\r\n                                unless it contains spelling errors.\r\n:XitUnlessSpellError[!] [bad | rare | local | caps] [...] [{predicates}]\r\n                                :write  the current buffer and :quit,\r\n                                unless it contains spelling errors.\r\n\r\n:NextUnlessSpellError[!] [bad | rare | local | caps] [...] [{predicates}]\r\n                                Edit :next file, unless the current buffer\r\n                                contains spelling errors.\r\n\r\nThis set of commands automatically opens the quickfix list in case of spelling\r\nerror in the buffer or passed [range] of lines.\r\n\r\n:BDeleteOrSpellCheck[!] [bad | rare | local | caps] [...] [{predicates}]\r\n                                :bdelete the current buffer, or show the\r\n                                spelling errors in the quickfix list.\r\n:WriteOrSpellCheck[!] [bad | rare | local | caps] [...] [{predicates}]\r\n                                :write the current buffer, or show the\r\n                                spelling errors in the quickfix list.\r\n:WriteDeleteOrSpellCheck[!] [bad | rare | local | caps] [...] [{predicates}]\r\n                                :write and :bdelete the current buffer,\r\n                                or show the spelling errors in the quickfix\r\n                                list.\r\n:XitOrSpellCheck[!] [bad | rare | local | caps] [...] [{predicates}]\r\n                                :write the current buffer and :quit, or\r\n                                show the spelling errors in the quickfix list.\r\n\r\n:NextOrSpellCheck[!] [bad | rare | local | caps] [...] [{predicates}]\r\n                                Edit :next file, or show the current\r\n                                buffer's spelling errors in the quickfix list.\r\n\r\n:UpdateAndSpellCheck[!] [bad | rare | local | caps] [...] [{predicates}]\r\n                                :update the current buffer, and show any\r\n                                spelling errors in the quickfix list.\r\n\r\n                                A [!] is passed to the :write \/ :bdelete \/\r\n                                :quit commands.","4":"DESCRIPTION\r\nVim offers built-in spell checking; when you enable it via 'spell' and\r\n'spelllang', you can jump to the highlighted spelling errors in the buffer via\r\n]s. With spelling errors scattered across a large document, Vim does not\r\nprovide an overview or report about the overall spell situation.\r\n\r\nThis plugin populates the |quickfix|-list with all spelling errors found in a\r\nbuffer to give you that overview. You can use the built-in quickfix features\r\nto navigate to the first occurrence of a particular spell error. You can also\r\nmanage the spelling errors (mark as good \/ bad word, globally replace with\r\nsuggestion) directly from the quickfix window via the usual zg, zw, z=\r\netc. mappings.\r\n\r\nA typical workflow (e.g. when composing email, commit messages, or any form of\r\ndocumentation) includes writing and\/or quitting the buffer, unless some\r\nremaining spelling errors require further intervention. This plugin offers\r\nauxiliary enhanced variants of :bdelete, :write and :quit that check for\r\nspelling errors and only execute the action if none were found. So by using\r\nthese replacement commands, you'll never send or commit messages full of\r\nembarrassing typos any more!\r\n\r\nUSAGE\r\n:[range]SpellCheck[!] [bad | rare | local | caps] [...] [{predicates}]\r\n                        Show all \/ the passed type(s) of spelling errors as a\r\n                        quickfix list [at locations where {predicates} yield\r\n                        true] SpellCheck-predicates.\r\n                        For multiple occurrences of the same error, the first\r\n                        location and the number of occurrences is shown.\r\n                        If [!] is not given the first error is jumped to.\r\n\r\n                        In the quickfix list, spelling errors from other\r\n                        buffers are kept, so you can use something like\r\n                            :argdo SpellCheck\r\n                       to gather the spelling errors from multiple buffers.\r\n\r\n:[range]SpellLCheck[!] [bad | rare | local | caps] [...] [{predicates}]\r\n                        Same as :SpellCheck, except the location list for the\r\n                        current window is used instead of the quickfix list.\r\n\r\nYou can pass arbitrary Vimscript expressions that then need to match at the\r\ncurrent spell error location to consider the spelling error; else, that\r\nparticular error will be ignored. For example, the following will ignore spell\r\nerrors in a Vim modeline:\r\n    :SpellCheck getline('.') !~ 'vim:'\r\nIf you define the following syntactic sugar function (in your vimrc)\r\n    function! Syntax( pattern )\r\n        return ingo#syntaxitem#IsOnSyntax(getpos('.'), a:pattern)\r\n    endfunction\r\nyou can easily limit spell checking to certain syntax elements, e.g. to\r\nexclude spell errors inside comments:\r\n    :SpellCheck !Syntax('Comment')\r\n\r\nMAPPINGS\r\n                        Inside the quickfix window, the following mappings are\r\n                        remapped so that they operate on the target spell\r\n                        error: zg, zG, zw, zW, zug, zuG, zuw,\r\n                        zuW, z=, u\r\n                        For z=, all identical misspellings in the buffer are\r\n                        replaced with the chosen suggestion (via\r\n                        :spellrepall).\r\n                        You can also quickly undo the last spell suggestion\r\n                        from the quickfix window (i.e. without switching to\r\n                        the target buffer) via u.\r\n                        For the other commands, the taken action is appended\r\n                        to the quickfix list entry, so that the list serves as\r\n                        a record of done actions (until you refresh the list\r\n                        with a new :SpellCheck).\r\n\r\nAUXILIARY COMMANDS\r\nThe following set of commands just issue an error when spelling errors exist\r\nin the buffer or passed [range] of lines.\r\n\r\n:BDeleteUnlessSpellError[!] [bad | rare | local | caps] [...] [{predicates}]\r\n                                :bdelete| the current buffer, unless it\r\n                                contains spelling errors.\r\n:WriteUnlessSpellError[!] [bad | rare | local | caps] [...] [{predicates}]\r\n                                :write the current buffer, unless it\r\n                                contains spelling errors.\r\n:WriteDeleteUnlessSpellError[!]  [bad | rare | local | caps] [...] [{predicates}]\r\n                                :write and :bdelete the current buffer,\r\n                                unless it contains spelling errors.\r\n:XitUnlessSpellError[!] [bad | rare | local | caps] [...] [{predicates}]\r\n                                :write  the current buffer and :quit,\r\n                                unless it contains spelling errors.\r\n\r\n:NextUnlessSpellError[!] [bad | rare | local | caps] [...] [{predicates}]\r\n                                Edit :next file, unless the current buffer\r\n                                contains spelling errors.\r\n\r\nThis set of commands automatically opens the quickfix list in case of spelling\r\nerror in the buffer or passed [range] of lines.\r\n\r\n:BDeleteOrSpellCheck[!] [bad | rare | local | caps] [...] [{predicates}]\r\n                                :bdelete the current buffer, or show the\r\n                                spelling errors in the quickfix list.\r\n:WriteOrSpellCheck[!] [bad | rare | local | caps] [...] [{predicates}]\r\n                                :write the current buffer, or show the\r\n                                spelling errors in the quickfix list.\r\n:WriteDeleteOrSpellCheck[!] [bad | rare | local | caps] [...] [{predicates}]\r\n                                :write and :bdelete the current buffer,\r\n                                or show the spelling errors in the quickfix\r\n                                list.\r\n:XitOrSpellCheck[!] [bad | rare | local | caps] [...] [{predicates}]\r\n                                :write the current buffer and :quit, or\r\n                                show the spelling errors in the quickfix list.\r\n\r\n:NextOrSpellCheck[!] [bad | rare | local | caps] [...] [{predicates}]\r\n                                Edit :next file, or show the current\r\n                                buffer's spelling errors in the quickfix list.\r\n\r\n:UpdateAndSpellCheck[!] [bad | rare | local | caps] [...] [{predicates}]\r\n                                :update the current buffer, and show any\r\n                                spelling errors in the quickfix list.\r\n\r\n                                A [!] is passed to the :write \/ :bdelete \/\r\n                                :quit commands.","install_details":"INSTALLATION\r\nThe code is hosted in a Git repo at\r\n    https:\/\/github.com\/inkarkat\/vim-SpellCheck\r\nYou can use your favorite plugin manager, or \"git clone\" into a directory used\r\nfor Vim packages. Releases are on the \"stable\" branch, the latest unstable\r\ndevelopment snapshot on \"master\".\r\n\r\nThis script is also packaged as a vimball. If you have the \"gunzip\"\r\ndecompressor in your PATH, simply edit the *.vmb.gz package in Vim; otherwise,\r\ndecompress the archive first, e.g. using WinZip. Inside Vim, install by\r\nsourcing the vimball or via the :UseVimball command.\r\n    vim SpellCheck*.vmb.gz\r\n    :so %\r\nTo uninstall, use the :RmVimball command.\r\n\r\nDEPENDENCIES\r\n- Requires Vim 7.0 or higher.\r\n- Requires the ingo-library.vim plugin (vimscript #4433), version 1.024 or\r\n  higher.\r\n\r\nCONFIGURATION\r\nFor a permanent configuration, put the following commands into your vimrc:\r\n\r\nIf you don't want the auxiliary commands, just the core :SpellCheck command,\r\nuse:\r\n    let g:SpellCheck_DefineAuxiliaryCommands = 0\r\nIf you just want some of the auxiliary commands, or under different names, or\r\nsimilar commands, you can easily define them yourself, as the core spell check\r\nfunctionality is available as global autoload functions. Have a look at\r\nplugin\/SpellCheck.vim for inspiration.\r\n\r\nIf you don't want the SpellCheck-mappings that allow you to manage the spell\r\nerrors directly from the quickfix window, use:\r\n    let g:SpellCheck_DefineQuickfixMappings = 0\r\n\r\nThe :SpellCheck command captures not just the misspelled word, but also some\r\ntext around it, to provide context in the quickfix list. The number of\r\noccurrences of a particular spell error is set at:\r\n    let g:SpellCheck_ErrorContextNum = 99\r\nYou can tweak that, reduce it to 1 to only show the first, or 0 to completely\r\nturn off context.\r\n\r\nWhat text around the current spell error gets captured can be tweaked via a\r\nregular expression that contains a %s parameter, which is replaced with the\r\natom for the spell error start position. As Vim uses a special,\r\nspellfile-dependent definition of word characters, these can be tweaked\r\nseparately.\r\n\r\nThe plugin can provide additional syntax highlighting for the quickfix window\r\nwhen it contains spell errors; to turn this off, use:\r\n    let g:SpellCheck_QuickfixHighlight = 0\r\n\r\nTo ignore some (e.g. rare) spell errors from the checks, you can define a\r\nList of considered types; these are overwritten by any [bad | rare | local |\r\ncaps] argument(s) given to individual commands:\r\n    let g:SpellCheck_ConsideredErrorTypes = ['bad', 'local', 'caps']\r\n\r\nLikewise, you can specify default predicates that limit the accepted spell\r\nerrors unless any predicates are passed to the individual command:\r\n    let g:SpellCheck_Predicates = 'getline(\".\") !~ \"^#\"'\r\n\r\nTo change the highlighting colors, redefine (after any :colorscheme command)\r\nor link the two highlight groups:\r\n    highlight link qfSpellErrorWord             SpellBad\r\n    highlight link qfSpellErrorWordInContext    Normal\r\n    highlight link qfSpellContext               SpecialKey\r\n\r\nINTEGRATION\r\nBy default, 'spell' will be automatically enabled when it's off, but you must\r\nhave already set 'spelllang' for a functioning spell check. If you have\r\nwritten a custom auto-detection for the languages that you\r\nfrequently use, you can integrate this here through a Funcref. The custom\r\nfunction must take no arguments, and set 'spell' and 'spelllang' accordingly.\r\n    let g:SpellCheck_OnNospell = function('SpellCheck#AutoEnableSpell')\r\nIf you want :SpellCheck to fail when 'spell' is off:\r\n    let g:SpellCheck_OnNospell = ''\r\n\r\nAll commands that manipulate the word lists are executed through a Funcref; by\r\ndefault, it automatically enables 'spell', like g:SpellCheck_OnNospell.","5":"INSTALLATION\r\nThe code is hosted in a Git repo at\r\n    https:\/\/github.com\/inkarkat\/vim-SpellCheck\r\nYou can use your favorite plugin manager, or \"git clone\" into a directory used\r\nfor Vim packages. Releases are on the \"stable\" branch, the latest unstable\r\ndevelopment snapshot on \"master\".\r\n\r\nThis script is also packaged as a vimball. If you have the \"gunzip\"\r\ndecompressor in your PATH, simply edit the *.vmb.gz package in Vim; otherwise,\r\ndecompress the archive first, e.g. using WinZip. Inside Vim, install by\r\nsourcing the vimball or via the :UseVimball command.\r\n    vim SpellCheck*.vmb.gz\r\n    :so %\r\nTo uninstall, use the :RmVimball command.\r\n\r\nDEPENDENCIES\r\n- Requires Vim 7.0 or higher.\r\n- Requires the ingo-library.vim plugin (vimscript #4433), version 1.024 or\r\n  higher.\r\n\r\nCONFIGURATION\r\nFor a permanent configuration, put the following commands into your vimrc:\r\n\r\nIf you don't want the auxiliary commands, just the core :SpellCheck command,\r\nuse:\r\n    let g:SpellCheck_DefineAuxiliaryCommands = 0\r\nIf you just want some of the auxiliary commands, or under different names, or\r\nsimilar commands, you can easily define them yourself, as the core spell check\r\nfunctionality is available as global autoload functions. Have a look at\r\nplugin\/SpellCheck.vim for inspiration.\r\n\r\nIf you don't want the SpellCheck-mappings that allow you to manage the spell\r\nerrors directly from the quickfix window, use:\r\n    let g:SpellCheck_DefineQuickfixMappings = 0\r\n\r\nThe :SpellCheck command captures not just the misspelled word, but also some\r\ntext around it, to provide context in the quickfix list. The number of\r\noccurrences of a particular spell error is set at:\r\n    let g:SpellCheck_ErrorContextNum = 99\r\nYou can tweak that, reduce it to 1 to only show the first, or 0 to completely\r\nturn off context.\r\n\r\nWhat text around the current spell error gets captured can be tweaked via a\r\nregular expression that contains a %s parameter, which is replaced with the\r\natom for the spell error start position. As Vim uses a special,\r\nspellfile-dependent definition of word characters, these can be tweaked\r\nseparately.\r\n\r\nThe plugin can provide additional syntax highlighting for the quickfix window\r\nwhen it contains spell errors; to turn this off, use:\r\n    let g:SpellCheck_QuickfixHighlight = 0\r\n\r\nTo ignore some (e.g. rare) spell errors from the checks, you can define a\r\nList of considered types; these are overwritten by any [bad | rare | local |\r\ncaps] argument(s) given to individual commands:\r\n    let g:SpellCheck_ConsideredErrorTypes = ['bad', 'local', 'caps']\r\n\r\nLikewise, you can specify default predicates that limit the accepted spell\r\nerrors unless any predicates are passed to the individual command:\r\n    let g:SpellCheck_Predicates = 'getline(\".\") !~ \"^#\"'\r\n\r\nTo change the highlighting colors, redefine (after any :colorscheme command)\r\nor link the two highlight groups:\r\n    highlight link qfSpellErrorWord             SpellBad\r\n    highlight link qfSpellErrorWordInContext    Normal\r\n    highlight link qfSpellContext               SpecialKey\r\n\r\nINTEGRATION\r\nBy default, 'spell' will be automatically enabled when it's off, but you must\r\nhave already set 'spelllang' for a functioning spell check. If you have\r\nwritten a custom auto-detection for the languages that you\r\nfrequently use, you can integrate this here through a Funcref. The custom\r\nfunction must take no arguments, and set 'spell' and 'spelllang' accordingly.\r\n    let g:SpellCheck_OnNospell = function('SpellCheck#AutoEnableSpell')\r\nIf you want :SpellCheck to fail when 'spell' is off:\r\n    let g:SpellCheck_OnNospell = ''\r\n\r\nAll commands that manipulate the word lists are executed through a Funcref; by\r\ndefault, it automatically enables 'spell', like g:SpellCheck_OnNospell.","first_name":"Ingo","6":"Ingo","last_name":"Karkat","7":"Karkat","releases":[{"0":"3844","vim_version":"7.0","1":"7.0","script_version":"2.00","2":"2.00","version_comment":"- ENH: Make all commands take optional [bad | rare | local | caps] type argument (the forwarded [++opt] [file] accepted by some auxiliary commands probably aren't very important here) and use that for limiting the checks to those spell error types.\r\n- ENH: Make all commands take optional predicates that limit the checked locations, e.g. to text within a certain syntax group only.\r\n- Introduce g:SpellCheck_ConsideredErrorTypes configuration variable to limit the error types by default.\r\n- Go to the first misspelling in the passed range (if any) instead of the first overall. I think this is more DWIM.\r\n- Set the quickfix type to the capitalized first letter of the spell error type, except for the default \"bad\" ones. This allows for better differentiation than the previous lumping of rare + local as warning vs. errors. *** You need to update to ingo-library (vimscript #4433) version 1.024! ***","3":"- ENH: Make all commands take optional [bad | rare | local | caps] type argument (the forwarded [++opt] [file] accepted by some auxiliary commands probably aren't very important here) and use that for limiting the checks to those spell error types.\r\n- ENH: Make all commands take optional predicates that limit the checked locations, e.g. to text within a certain syntax group only.\r\n- Introduce g:SpellCheck_ConsideredErrorTypes configuration variable to limit the error types by default.\r\n- Go to the first misspelling in the passed range (if any) instead of the first overall. I think this is more DWIM.\r\n- Set the quickfix type to the capitalized first letter of the spell error type, except for the default \"bad\" ones. This allows for better differentiation than the previous lumping of rare + local as warning vs. errors. *** You need to update to ingo-library (vimscript #4433) version 1.024! ***","package":"SpellCheck-2.00.vmb.gz","4":"SpellCheck-2.00.vmb.gz","src_id":"25601","5":"25601","creation_date":"1507294167","6":"1507294167"},{"0":"3844","vim_version":"7.0","1":"7.0","script_version":"1.30","2":"1.30","version_comment":"- ENH: Show words surrounding the spell error. The number of captured occurrences is controlled by g:SpellCheck_ErrorContextNum, what gets captured by g:SpellCheck_ErrorContextPattern. Thanks to Enno Nagel for the suggestion.\r\n- ENH: Add syntax highlighting for the misspelled word, the error context text, and occurrences of the misspelled word inside the context. Enno Nagel also suggested this.\r\n- FIX: Quickfix mappings are gone when closing and reopening the quickfix window (:cclose | copen), because a new scratch buffer is used, but the autocmd BufRead quickfix has been cleared.","3":"- ENH: Show words surrounding the spell error. The number of captured occurrences is controlled by g:SpellCheck_ErrorContextNum, what gets captured by g:SpellCheck_ErrorContextPattern. Thanks to Enno Nagel for the suggestion.\r\n- ENH: Add syntax highlighting for the misspelled word, the error context text, and occurrences of the misspelled word inside the context. Enno Nagel also suggested this.\r\n- FIX: Quickfix mappings are gone when closing and reopening the quickfix window (:cclose | copen), because a new scratch buffer is used, but the autocmd BufRead quickfix has been cleared.","package":"SpellCheck-1.30.vmb.gz","4":"SpellCheck-1.30.vmb.gz","src_id":"22256","5":"22256","creation_date":"1406192051","6":"1406192051"},{"0":"3844","vim_version":"7.0","1":"7.0","script_version":"1.21","2":"1.21","version_comment":"- Add :NextUnlessSpellError and :NextOrSpellCheck auxiliary commands.\r\n- Allow to pass optional [++opt] [file] arguments to the :Write... commands.\r\n- Add dependency to ingo-library (vimscript #4433). *** You need to separately install ingo-library (vimscript #4433) version 1.001 (or higher)! ***","3":"- Add :NextUnlessSpellError and :NextOrSpellCheck auxiliary commands.\r\n- Allow to pass optional [++opt] [file] arguments to the :Write... commands.\r\n- Add dependency to ingo-library (vimscript #4433). *** You need to separately install ingo-library (vimscript #4433) version 1.001 (or higher)! ***","package":"SpellCheck-1.21.vmb.gz","4":"SpellCheck-1.21.vmb.gz","src_id":"20832","5":"20832","creation_date":"1379932259","6":"1379932259"},{"0":"3844","vim_version":"7.0","1":"7.0","script_version":"1.20","2":"1.20","version_comment":"- FIX: Line range is not defined and passed for :BDeleteOrSpellCheck and other :...OrSpellCheck commands, resulting in a script error.\r\n- ENH: Allow [range] for :BDeleteUnlessSpellError and other :...UnlessSpellError commands, too.","3":"- FIX: Line range is not defined and passed for :BDeleteOrSpellCheck and other :...OrSpellCheck commands, resulting in a script error.\r\n- ENH: Allow [range] for :BDeleteUnlessSpellError and other :...UnlessSpellError commands, too.","package":"SpellCheck.vba.gz","4":"SpellCheck.vba.gz","src_id":"17902","5":"17902","creation_date":"1336479609","6":"1336479609"},{"0":"3844","vim_version":"7.0","1":"7.0","script_version":"1.13","2":"1.13","version_comment":"ENH: In the quickfix list, apply undo via |u| to the target buffer to allow a quick revert of a spell correction.","3":"ENH: In the quickfix list, apply undo via |u| to the target buffer to allow a quick revert of a spell correction.","package":"SpellCheck.vba.gz","4":"SpellCheck.vba.gz","src_id":"17860","5":"17860","creation_date":"1335969574","6":"1335969574"},{"0":"3844","vim_version":"7.0","1":"7.0","script_version":"1.12","2":"1.12","version_comment":"ENH: Allow spell checking of partial buffers by allowing [range] for :SpellCheck command.","3":"ENH: Allow spell checking of partial buffers by allowing [range] for :SpellCheck command.","package":"SpellCheck.vba.gz","4":"SpellCheck.vba.gz","src_id":"17848","5":"17848","creation_date":"1335887141","6":"1335887141"},{"0":"3844","vim_version":"7.0","1":"7.0","script_version":"1.11","2":"1.11","version_comment":"ENH: Capture corrected text and include in quickfix status message.","3":"ENH: Capture corrected text and include in quickfix status message.","package":"SpellCheck.vba.gz","4":"SpellCheck.vba.gz","src_id":"17842","5":"17842","creation_date":"1335796387","6":"1335796387"},{"0":"3844","vim_version":"7.0","1":"7.0","script_version":"1.10","2":"1.10","version_comment":"ENH: Allow to manage the spelling errors (mark as good \/ bad word, globally replace with suggestion) directly from the quickfix window via the usual zg, zw, z= etc. mappings.","3":"ENH: Allow to manage the spelling errors (mark as good \/ bad word, globally replace with suggestion) directly from the quickfix window via the usual zg, zw, z= etc. mappings.","package":"SpellCheck.vba.gz","4":"SpellCheck.vba.gz","src_id":"17840","5":"17840","creation_date":"1335788854","6":"1335788854"},{"0":"3844","vim_version":"7.0","1":"7.0","script_version":"1.01","2":"1.01","version_comment":"ENH: Allow accumulating spelling errors from multiple buffers (e.g. via :argdo SpellCheck). ","3":"ENH: Allow accumulating spelling errors from multiple buffers (e.g. via :argdo SpellCheck). ","package":"SpellCheck.vba.gz","4":"SpellCheck.vba.gz","src_id":"17063","5":"17063","creation_date":"1323879006","6":"1323879006"},{"0":"3844","vim_version":"7.0","1":"7.0","script_version":"1.00","2":"1.00","version_comment":"Initial upload","3":"Initial upload","package":"SpellCheck.vba.gz","4":"SpellCheck.vba.gz","src_id":"17044","5":"17044","creation_date":"1323448313","6":"1323448313"}]},"3843":{"script_id":"3843","0":"3843","script_name":"nodeunit.vim","1":"nodeunit.vim","script_type":"utility","2":"utility","summary":"A simple compiler for testing javascript\/coffeescript with nodeunit","3":"A simple compiler for testing javascript\/coffeescript with nodeunit","description":"nodeunit.vim\r\n\r\nA simple compiler for executing nodeunit on VIM. Useful to use with vim-makegreen\r\n\r\nSee http:\/\/blog.staz.be\/?post\/2010\/09\/04\/Python-unit-test-and-vim for how to use this compiler with vim-makegreen. It is not exactly its tutorial but really compatible.\r\nhow to install\r\n\r\nuse vundle or pathogen is recommended or simply extract to your vim directory\r\n\r\nand write the following code to your ftplugin\/javascript.vim or ftplugin\/coffee.vim:\r\n\r\nset compiler=nodeunit\r\n\r\nDeveloped at https:\/\/github.com\/lambdalisue\/nodeunit.vim","4":"nodeunit.vim\r\n\r\nA simple compiler for executing nodeunit on VIM. Useful to use with vim-makegreen\r\n\r\nSee http:\/\/blog.staz.be\/?post\/2010\/09\/04\/Python-unit-test-and-vim for how to use this compiler with vim-makegreen. It is not exactly its tutorial but really compatible.\r\nhow to install\r\n\r\nuse vundle or pathogen is recommended or simply extract to your vim directory\r\n\r\nand write the following code to your ftplugin\/javascript.vim or ftplugin\/coffee.vim:\r\n\r\nset compiler=nodeunit\r\n\r\nDeveloped at https:\/\/github.com\/lambdalisue\/nodeunit.vim","install_details":"","5":"","first_name":"Alisue","6":"Alisue","last_name":"Lambda","7":"Lambda","releases":[{"0":"3843","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"nodeunit.vim.tar.gz","4":"nodeunit.vim.tar.gz","src_id":"17040","5":"17040","creation_date":"1323375462","6":"1323375462"}]},"3842":{"script_id":"3842","0":"3842","script_name":"nose.vim","1":"nose.vim","script_type":"utility","2":"utility","summary":"Simple compiler for testing python with nose","3":"Simple compiler for testing python with nose","description":"nose.vim\r\n\r\nA simple compiler for executing nosetests on VIM. Originally written by Olivier Le Thanh Duong at and modified by lambdalisue. Useful to use with vim-makegreen\r\n\r\nSee http:\/\/blog.staz.be\/?post\/2010\/09\/04\/Python-unit-test-and-vim for find how to use it with vim-makegreen\r\nnose-machineout\r\n\r\nmodified version use nose-machineout for convinience so you have to install it as well as nose:\r\n\r\nsudo pip install nose\r\nsudo pip install git+git:\/\/github.com\/lambdalisue\/nose-machineout.git#egg=nose_machineout\r\n\r\nhow to install\r\n\r\nuse vundle or pathogen is recommended or simply extract to your vim directory\r\n\r\nand write the following code to your ftplugin\/python.vim:\r\n\r\nset compiler=nose\r\n\r\nDeveloped at https:\/\/github.com\/lambdalisue\/nose.vim","4":"nose.vim\r\n\r\nA simple compiler for executing nosetests on VIM. Originally written by Olivier Le Thanh Duong at and modified by lambdalisue. Useful to use with vim-makegreen\r\n\r\nSee http:\/\/blog.staz.be\/?post\/2010\/09\/04\/Python-unit-test-and-vim for find how to use it with vim-makegreen\r\nnose-machineout\r\n\r\nmodified version use nose-machineout for convinience so you have to install it as well as nose:\r\n\r\nsudo pip install nose\r\nsudo pip install git+git:\/\/github.com\/lambdalisue\/nose-machineout.git#egg=nose_machineout\r\n\r\nhow to install\r\n\r\nuse vundle or pathogen is recommended or simply extract to your vim directory\r\n\r\nand write the following code to your ftplugin\/python.vim:\r\n\r\nset compiler=nose\r\n\r\nDeveloped at https:\/\/github.com\/lambdalisue\/nose.vim","install_details":"","5":"","first_name":"Alisue","6":"Alisue","last_name":"Lambda","7":"Lambda","releases":[{"0":"3842","vim_version":"7.0","1":"7.0","script_version":"0.1-rc2","2":"0.1-rc2","version_comment":"Fix bug","3":"Fix bug","package":"lambdalisue-nose.vim-0418999.zip","4":"lambdalisue-nose.vim-0418999.zip","src_id":"17073","5":"17073","creation_date":"1324009090","6":"1324009090"},{"0":"3842","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"nose.vim.tar.gz","4":"nose.vim.tar.gz","src_id":"17039","5":"17039","creation_date":"1323375344","6":"1323375344"}]},"3841":{"script_id":"3841","0":"3841","script_name":"vim-django-support","1":"vim-django-support","script_type":"ftplugin","2":"ftplugin","summary":"Add DJANGO_SETTINGS_MODULES to enable pythoncomplete or whatever for django","3":"Add DJANGO_SETTINGS_MODULES to enable pythoncomplete or whatever for django","description":"Vim django support plugin\r\n\r\nThis plugin helps you to set DJANGO_SETTINGS_MODULE automatically. That mean your pythoncomplete now support Django omni completion. Your nose.vim now support Django unittest.\r\n\r\nThis plugin solve every issue related to DJANGO_SETTINGS_MODULE\r\nhttps:\/\/github.com\/lambdalisue\/vim-django-support\/raw\/master\/img\/screenshot.png\r\n\r\nOmni-completion of django.db with pythoncomplete\r\nHow to install\r\n\r\nUsing vundle or pathogen is recommended or simply extract to your vim directory\r\n\r\nDeveloped at https:\/\/github.com\/lambdalisue\/vim-django-support","4":"Vim django support plugin\r\n\r\nThis plugin helps you to set DJANGO_SETTINGS_MODULE automatically. That mean your pythoncomplete now support Django omni completion. Your nose.vim now support Django unittest.\r\n\r\nThis plugin solve every issue related to DJANGO_SETTINGS_MODULE\r\nhttps:\/\/github.com\/lambdalisue\/vim-django-support\/raw\/master\/img\/screenshot.png\r\n\r\nOmni-completion of django.db with pythoncomplete\r\nHow to install\r\n\r\nUsing vundle or pathogen is recommended or simply extract to your vim directory\r\n\r\nDeveloped at https:\/\/github.com\/lambdalisue\/vim-django-support","install_details":"Required\r\nVim compiled with +python and Python 2.5 or above.","5":"Required\r\nVim compiled with +python and Python 2.5 or above.","first_name":"Alisue","6":"Alisue","last_name":"Lambda","7":"Lambda","releases":[{"0":"3841","vim_version":"7.0","1":"7.0","script_version":"0.1-rc3","2":"0.1-rc3","version_comment":"Fix bug","3":"Fix bug","package":"lambdalisue-vim-django-support-v0.1-1-g7728bde.zip","4":"lambdalisue-vim-django-support-v0.1-1-g7728bde.zip","src_id":"17072","5":"17072","creation_date":"1324008513","6":"1324008513"},{"0":"3841","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"vim-django-support.tar.gz","4":"vim-django-support.tar.gz","src_id":"17038","5":"17038","creation_date":"1323375249","6":"1323375249"}]},"3840":{"script_id":"3840","0":"3840","script_name":"vim-python-virtualenv","1":"vim-python-virtualenv","script_type":"ftplugin","2":"ftplugin","summary":"Activate python virtualenv within Vim","3":"Activate python virtualenv within Vim","description":"vim-python-virtualenv\r\n\r\nThis plugin is for using virtualenv within Vim. It activate the virtualenv and add the path to sys.path\r\n\r\nAlso this plugin save virtualenv name to pythonworkon variable of vim.\r\nRequired\r\n\r\nVim compiled with +python\r\nHow to install\r\n\r\nUsing vundle or pathogen is recommended or simply extract to your vim directory\r\nUsage\r\n\r\nThis plugin save virtualenv name to pythonworkon variable of vim so if you want to check the name of virtualenv in status line, add the following code to your .vimrc:\r\n\r\n\" Apply g:pythonworkon to statusline\r\n\r\nlet &statusline='%F%m%r%h%w [FORMAT=%{&ff}] [ENC=%{&fileencoding}] [TYPE=%Y] [ASCII=%03.3b] [HEX=%02.2B] [POS=%04l,%04v][%p%%] [LEN=%L] %= [WORKON=%{pythonworkon}]'\r\n\r\nDeveloped at https:\/\/github.com\/lambdalisue\/vim-python-virtualenv","4":"vim-python-virtualenv\r\n\r\nThis plugin is for using virtualenv within Vim. It activate the virtualenv and add the path to sys.path\r\n\r\nAlso this plugin save virtualenv name to pythonworkon variable of vim.\r\nRequired\r\n\r\nVim compiled with +python\r\nHow to install\r\n\r\nUsing vundle or pathogen is recommended or simply extract to your vim directory\r\nUsage\r\n\r\nThis plugin save virtualenv name to pythonworkon variable of vim so if you want to check the name of virtualenv in status line, add the following code to your .vimrc:\r\n\r\n\" Apply g:pythonworkon to statusline\r\n\r\nlet &statusline='%F%m%r%h%w [FORMAT=%{&ff}] [ENC=%{&fileencoding}] [TYPE=%Y] [ASCII=%03.3b] [HEX=%02.2B] [POS=%04l,%04v][%p%%] [LEN=%L] %= [WORKON=%{pythonworkon}]'\r\n\r\nDeveloped at https:\/\/github.com\/lambdalisue\/vim-python-virtualenv","install_details":"","5":"","first_name":"Alisue","6":"Alisue","last_name":"Lambda","7":"Lambda","releases":[{"0":"3840","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"vim-python-virtualenv.tar.gz","4":"vim-python-virtualenv.tar.gz","src_id":"17037","5":"17037","creation_date":"1323375114","6":"1323375114"}]},"3839":{"script_id":"3839","0":"3839","script_name":"weibo.vim","1":"weibo.vim","script_type":"utility","2":"utility","summary":"用vim发腾讯微博","3":"用vim发腾讯微博","description":"详细使用说明: http:\/\/www.vimer.cn\/?p=2433\r\n\r\n功能:\r\n    1. 分享文章中的一段文字，并支持评论\r\n    2. 直接发送微博\r\n\r\n一. 环境依赖\r\n    python\r\n二. 安装\r\n    去 www.vim.org 下载 weibo.vim\r\n    将weibo.vim 放在 plugin目录\r\n三. 配置\r\n目前支持的配置如下:\r\n    g:weibo_access_token oauth2.0的access_token，是由QQ登录提供的授权token，貌似过期时间是1个月。后面会写出获取这个token的方法。\r\n    g:weibo_access_token 签名档，默认值是\u00e2\u0080\u009c来自weibo.vim\u00e2\u0080\u009d，如果不喜欢可以配置为空\r\n在_vimrc中配置:\r\n    let g:weibo_access_token = '第四步会生成的access_token'\r\n四. 生成access_token\r\n点击如下链接:\r\nhttps:\/\/graph.qq.com\/oauth2.0\/authorize?response_type=token&client_id=100229856&redirect_uri=vimer.cn&scope=add_t\r\n\r\n在进行QQ登录之后，会跳转到类似如下链接:\r\nhttp:\/\/www.vimer.cn\/#access_token=4E6421B8719124324217AF48E085F&expires_in=7776000\r\n\r\n其中access_token=后面的即要获取的access_token。\r\n将其配置到第二步的g:weibo_access_token中。\r\n如果在使用中，提示 access_token 过期的话，只要按照上面的步骤重新申请一遍即可。\r\n\r\n五. 命令\r\n分享选中的的文字\r\n    选中之后，按下 \u00e2\u0080\u009c,at\u00e2\u0080\u009d， 如果不需要写评论，则直接回车；如果需要评论，则输入空格后，输入评论，回车。\r\n直接发送微博\r\n    在normal模式下，直接按下 \u00e2\u0080\u009c,at\u00e2\u0080\u009d， 输入空格后，输入文字，回车。\r\n","4":"详细使用说明: http:\/\/www.vimer.cn\/?p=2433\r\n\r\n功能:\r\n    1. 分享文章中的一段文字，并支持评论\r\n    2. 直接发送微博\r\n\r\n一. 环境依赖\r\n    python\r\n二. 安装\r\n    去 www.vim.org 下载 weibo.vim\r\n    将weibo.vim 放在 plugin目录\r\n三. 配置\r\n目前支持的配置如下:\r\n    g:weibo_access_token oauth2.0的access_token，是由QQ登录提供的授权token，貌似过期时间是1个月。后面会写出获取这个token的方法。\r\n    g:weibo_access_token 签名档，默认值是\u00e2\u0080\u009c来自weibo.vim\u00e2\u0080\u009d，如果不喜欢可以配置为空\r\n在_vimrc中配置:\r\n    let g:weibo_access_token = '第四步会生成的access_token'\r\n四. 生成access_token\r\n点击如下链接:\r\nhttps:\/\/graph.qq.com\/oauth2.0\/authorize?response_type=token&client_id=100229856&redirect_uri=vimer.cn&scope=add_t\r\n\r\n在进行QQ登录之后，会跳转到类似如下链接:\r\nhttp:\/\/www.vimer.cn\/#access_token=4E6421B8719124324217AF48E085F&expires_in=7776000\r\n\r\n其中access_token=后面的即要获取的access_token。\r\n将其配置到第二步的g:weibo_access_token中。\r\n如果在使用中，提示 access_token 过期的话，只要按照上面的步骤重新申请一遍即可。\r\n\r\n五. 命令\r\n分享选中的的文字\r\n    选中之后，按下 \u00e2\u0080\u009c,at\u00e2\u0080\u009d， 如果不需要写评论，则直接回车；如果需要评论，则输入空格后，输入评论，回车。\r\n直接发送微博\r\n    在normal模式下，直接按下 \u00e2\u0080\u009c,at\u00e2\u0080\u009d， 输入空格后，输入文字，回车。\r\n","install_details":"put it into plugin directory。","5":"put it into plugin directory。","first_name":"zhu","6":"zhu","last_name":"nianyang","7":"nianyang","releases":[{"0":"3839","vim_version":"7.0","1":"7.0","script_version":"0.0.2","2":"0.0.2","version_comment":"优化了一下代码","3":"优化了一下代码","package":"weibo.vim","4":"weibo.vim","src_id":"17057","5":"17057","creation_date":"1323792476","6":"1323792476"},{"0":"3839","vim_version":"7.0","1":"7.0","script_version":"0.0.1","2":"0.0.1","version_comment":"Initial upload","3":"Initial upload","package":"weibo.vim","4":"weibo.vim","src_id":"17035","5":"17035","creation_date":"1323342048","6":"1323342048"}]},"3838":{"script_id":"3838","0":"3838","script_name":"nscripter.vim","1":"nscripter.vim","script_type":"syntax","2":"syntax","summary":"syntax file for Nscripter","3":"syntax file for Nscripter","description":"Nscripter用のシンタックスファイルです。","4":"Nscripter用のシンタックスファイルです。","install_details":"","5":"","first_name":"tomomiya","6":"tomomiya","last_name":" ","7":" ","releases":[{"0":"3838","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"nscripter.vim","4":"nscripter.vim","src_id":"17029","5":"17029","creation_date":"1323176801","6":"1323176801"}]},"3837":{"script_id":"3837","0":"3837","script_name":"ChickenSetupXp","1":"ChickenSetupXp","script_type":"utility","2":"utility","summary":"Xptemplate snippets for Chicken Scheme setup files","3":"Xptemplate snippets for Chicken Scheme setup files","description":"Here are some xptemplate snippets for Chicken Scheme meta files.\r\n\r\nFor more information on Chicken Scheme meta files, see:\r\n\r\n  http:\/\/wiki.call-cc.org\/eggs%20tutorial#the-setup-file\r\n\r\nand\r\n\r\n  http:\/\/wiki.call-cc.org\/man\/4\/Extensions#procedures-and-macros-available-in-setup-scripts\r\n\r\nNOTE:  These snippets require the newest version of xptemplate from SVN or git.\r\n","4":"Here are some xptemplate snippets for Chicken Scheme meta files.\r\n\r\nFor more information on Chicken Scheme meta files, see:\r\n\r\n  http:\/\/wiki.call-cc.org\/eggs%20tutorial#the-setup-file\r\n\r\nand\r\n\r\n  http:\/\/wiki.call-cc.org\/man\/4\/Extensions#procedures-and-macros-available-in-setup-scripts\r\n\r\nNOTE:  These snippets require the newest version of xptemplate from SVN or git.\r\n","install_details":"To install these snippets:\r\n\r\n - get xptemplate from SVN or git (important!  xptemplate from vim.org will **not** work!)\r\n - install and configure xptemplate\r\n - download these snippets\r\n - rename the downloaded snippet file as \"chickensetup.xpt.vim\"\r\n - move it in to the ftplugin\/chickensetup directory under the path you've chosen according to\r\n      :help xpt-personal-folder\r\n - make sure vim knows that files with a \".setup\" suffix have a \"chickensetup\" filetype (see :help new-filetype)\r\n - quit and restart vim\r\n","5":"To install these snippets:\r\n\r\n - get xptemplate from SVN or git (important!  xptemplate from vim.org will **not** work!)\r\n - install and configure xptemplate\r\n - download these snippets\r\n - rename the downloaded snippet file as \"chickensetup.xpt.vim\"\r\n - move it in to the ftplugin\/chickensetup directory under the path you've chosen according to\r\n      :help xpt-personal-folder\r\n - make sure vim knows that files with a \".setup\" suffix have a \"chickensetup\" filetype (see :help new-filetype)\r\n - quit and restart vim\r\n","first_name":"Gnosis","6":"Gnosis","last_name":"Ouroubouros","7":"Ouroubouros","releases":[{"0":"3837","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"chickensetup.xpt.vim","4":"chickensetup.xpt.vim","src_id":"17023","5":"17023","creation_date":"1323064622","6":"1323064622"}]},"3836":{"script_id":"3836","0":"3836","script_name":"ChickenMetaXp","1":"ChickenMetaXp","script_type":"utility","2":"utility","summary":"Xptemplate snippets for Chicken Scheme meta files","3":"Xptemplate snippets for Chicken Scheme meta files","description":"Here are some xptemplate snippets for Chicken Scheme meta files.\r\n\r\nFor more information on Chicken Scheme meta files, see:\r\n\r\n  http:\/\/wiki.call-cc.org\/Metafile%20reference\r\n\r\nand\r\n\r\n  http:\/\/wiki.call-cc.org\/eggs%20tutorial#the-meta-file\r\n\r\nNOTE:  These snippets require the newest version of xptemplate from SVN or git.\r\n","4":"Here are some xptemplate snippets for Chicken Scheme meta files.\r\n\r\nFor more information on Chicken Scheme meta files, see:\r\n\r\n  http:\/\/wiki.call-cc.org\/Metafile%20reference\r\n\r\nand\r\n\r\n  http:\/\/wiki.call-cc.org\/eggs%20tutorial#the-meta-file\r\n\r\nNOTE:  These snippets require the newest version of xptemplate from SVN or git.\r\n","install_details":"To install these snippets: \r\n\r\n - get xptemplate from SVN or git (important!  xptemplate from vim.org will **not** work!) \r\n - install and configure xptemplate \r\n - download these snippets \r\n - rename the downloaded snippet file as \"chickenmeta.xpt.vim\"\r\n - move it in to the ftplugin\/chickenmeta directory under the path you've chosen according to\r\n      :help xpt-personal-folder \r\n - make sure vim knows that files with a \".meta\" suffix have a \"chickenmeta\" filetype (see :help new-filetype)\r\n - quit and restart vim","5":"To install these snippets: \r\n\r\n - get xptemplate from SVN or git (important!  xptemplate from vim.org will **not** work!) \r\n - install and configure xptemplate \r\n - download these snippets \r\n - rename the downloaded snippet file as \"chickenmeta.xpt.vim\"\r\n - move it in to the ftplugin\/chickenmeta directory under the path you've chosen according to\r\n      :help xpt-personal-folder \r\n - make sure vim knows that files with a \".meta\" suffix have a \"chickenmeta\" filetype (see :help new-filetype)\r\n - quit and restart vim","first_name":"Gnosis","6":"Gnosis","last_name":"Ouroubouros","7":"Ouroubouros","releases":[{"0":"3836","vim_version":"7.0","1":"7.0","script_version":"1.1","2":"1.1","version_comment":"Now a few snippets intended only for internal use have been hidden (so they don't clutter your snippet popup menu).","3":"Now a few snippets intended only for internal use have been hidden (so they don't clutter your snippet popup menu).","package":"chickenmeta.xpt.vim","4":"chickenmeta.xpt.vim","src_id":"17024","5":"17024","creation_date":"1323066263","6":"1323066263"},{"0":"3836","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"chickenmeta.xpt.vim","4":"chickenmeta.xpt.vim","src_id":"17022","5":"17022","creation_date":"1323057058","6":"1323057058"}]},"3835":{"script_id":"3835","0":"3835","script_name":"vim-octopress","1":"vim-octopress","script_type":"syntax","2":"syntax","summary":"Syntax highlighting for Octopress-flavored Markdown","3":"Syntax highlighting for Octopress-flavored Markdown","description":"Syntax highlighting mode for Octopress-flavored markdown files (posts, pages mostly).\r\n\r\nSource is at https:\/\/github.com\/tangledhelix\/vim-octopress","4":"Syntax highlighting mode for Octopress-flavored markdown files (posts, pages mostly).\r\n\r\nSource is at https:\/\/github.com\/tangledhelix\/vim-octopress","install_details":"To install the traditional way:\r\n\r\n\tgit clone https:\/\/github.com\/tangledhelix\/vim-octopress.git\r\n\tcd vim-octopress\r\n\tfor i in ftplugin syntax ; do\r\n\t\tmkdir -p ~\/.vim\/$i\r\n\t\tcp $i\/octopress.vim ~\/.vim\/$i\r\n\tdone\r\n\r\nIf you use Pathogen:\r\n\r\n\tcd ~\/.vim\/bundle\r\n\tgit clone https:\/\/github.com\/tangledhelix\/vim-octopress.git octopress\r\n\r\nTo use this mode for your Octopress Markdown files, use an autocmd.\r\n\r\n\tautocmd BufNewFile,BufRead *.markdown setfiletype octopress\r\n","5":"To install the traditional way:\r\n\r\n\tgit clone https:\/\/github.com\/tangledhelix\/vim-octopress.git\r\n\tcd vim-octopress\r\n\tfor i in ftplugin syntax ; do\r\n\t\tmkdir -p ~\/.vim\/$i\r\n\t\tcp $i\/octopress.vim ~\/.vim\/$i\r\n\tdone\r\n\r\nIf you use Pathogen:\r\n\r\n\tcd ~\/.vim\/bundle\r\n\tgit clone https:\/\/github.com\/tangledhelix\/vim-octopress.git octopress\r\n\r\nTo use this mode for your Octopress Markdown files, use an autocmd.\r\n\r\n\tautocmd BufNewFile,BufRead *.markdown setfiletype octopress\r\n","first_name":"Dan","6":"Dan","last_name":"Lowe","7":"Lowe","releases":[{"0":"3835","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"vim-octopress.zip","4":"vim-octopress.zip","src_id":"17021","5":"17021","creation_date":"1323031643","6":"1323031643"}]},"3834":{"script_id":"3834","0":"3834","script_name":"yankstack","1":"yankstack","script_type":"utility","2":"utility","summary":"lightweight implementation of emacs' kill ring for vim","3":"lightweight implementation of emacs' kill ring for vim","description":"yankstack.vim\r\n=============\r\n\r\nAuthor:  Max Brunsfeld <http:\/\/www.github.com\/maxbrunsfeld>\r\n\r\n[Yankstack.vim](https:\/\/github.com\/maxbrunsfeld\/vim-yankstack) is a\r\nlightweight implementation of the Emacs 'kill ring' for Vim.  It allows you to\r\nyank and delete things without worrying about losing the text that you yanked\r\npreviously. It effectively turns your default register into a stack, and lets\r\nyou cycle through the items in the stack after doing a paste.\r\n\r\nThis plugin is intended to be a simpler alternative to the\r\n[yankring](https:\/\/github.com\/chrismetcalf\/vim-yankring) plugin.\r\n\r\n## Key Mappings ##\r\n\r\nBy default, yankstack adds only 2 key bindings, in normal and visual modes:\r\n\r\n- ```meta-p```  - cycle *backward* through your history of yanks\r\n- ```meta-shift-p```  - cycle *forwards* through your history of yanks\r\n\r\nAfter pasting some text using ```p``` or ```P```, you can cycle through your\r\nyank history using these commands.\r\n\r\nTyping either of these keys *without* pasting first will do a normal paste\r\n(the same as typing `p`). This also works in insert mode.\r\n\r\nA note about the meta key - if you're using MacVim, and you want to use\r\nthis plugin's default key bindings (or any bindings involving the `option`\r\nkey), you must ```:set macmeta```\r\n\r\n## Commands ##\r\n\r\nYou can see the contents of the yank-stack using the ```:Yanks``` command.\r\nIts output is similar to the ```:registers``` command.\r\n\r\n## Configuration ##\r\n\r\nYankstack defines two plugin mappings that you can map to keys of your choosing.\r\nThe same mappings work in normal and insert modes.\r\n\r\n- ```<Plug>yankstack_substitute_older_paste``` - cycle backwards through your history of yanks\r\n- ```<Plug>yankstack_substitute_newer_paste``` - cycle forwards through your history of yanks\r\n\r\nFor example, if you wanted to define some mappings based on your 'leader' key,\r\nyou could do this:\r\n\r\n```\r\nnmap <leader>p <Plug>yankstack_substitute_older_paste\r\nnmap <leader>P <Plug>yankstack_substitute_older_paste\r\n```\r\n\r\nAlso, if you want to load yankstack without the default key mappings, just\r\n``` let g:yankstack_map_keys = 0 ```\r\nin your .vimrc file.\r\n\r\n## Compatibility ##\r\n\r\nYankstack works by mapping the yank and paste keys to functions that do some\r\nbook-keeping before calling through to the normal yank\/paste keys. You may want\r\nto define your own mappings of the yank and paste keys. For example, I like to\r\nmap the ```Y``` key to ```y$```, so that it behaves the same as ```D``` and\r\n```C```. The yankstack mappings need to happen **before** you define any such\r\nmappings of your own. To achieve this, just call ```yankstack#setup()``` in\r\nyour vimrc, before defining your mappings:\r\n\r\n```\r\ncall yankstack#setup()\r\nnmap Y y$\r\n\" other mappings involving y, d, c, etc\r\n```\r\n\r\n## Contributing, Feedback ##\r\n\r\nI'd enjoy hearing anybody's feedback on yankstack, and welcome any contribution.\r\nCheck it out on [github](https:\/\/github.com\/maxbrunsfeld\/vim-yankstack)!\r\n\r\n## Changelog ##\r\n\r\n\r\n### 1.0.4 (2012-07-01)\r\n  - Make it so that yankstack-cycling keys cause a normal paste if they are\r\n    used without pasting first. Fix stack-cycling in insert-mode.\r\n\r\n### 1.0.3 (2012-05-04):\r\n  - Fix bug when overwriting text in select mode. This was causing\r\n    problems for snipMate users.\r\n\r\n### 1.0.2 (2012-4-20):\r\n  - Add test coverage using rspec and [vimbot](https:\/\/github.com\/maxbrunsfeld\/vimbot)!\r\n  - Perfect the behavior of the yankstack when pasting over text in visual\r\n    mode\r\n  - Fix bug where 's' and 'S' didn't push to the yankstack\r\n\r\n### 1.0.1 (2012-2-11):\r\n  - Change default key bindings, update readme, add link to github page.\r\n\r\n### 1.0.1 (2011-12-08):\r\n  - Fix bug when displaying empty yanks.\r\n\r\n### 1.0.0 (2011-12-04):\r\n  - Remove unnecessary dependency on the undotree() function. Plugin should\r\n    now work on any recent version of vim.\r\n\r\n## License ##\r\nCopyright (c) Max Brunsfeld.  Distributed under the same terms as Vim itself.\r\nSee the vim license.\r\n\r\n vim:tw=78:ts=8:ft=help:norl:\r\n","4":"yankstack.vim\r\n=============\r\n\r\nAuthor:  Max Brunsfeld <http:\/\/www.github.com\/maxbrunsfeld>\r\n\r\n[Yankstack.vim](https:\/\/github.com\/maxbrunsfeld\/vim-yankstack) is a\r\nlightweight implementation of the Emacs 'kill ring' for Vim.  It allows you to\r\nyank and delete things without worrying about losing the text that you yanked\r\npreviously. It effectively turns your default register into a stack, and lets\r\nyou cycle through the items in the stack after doing a paste.\r\n\r\nThis plugin is intended to be a simpler alternative to the\r\n[yankring](https:\/\/github.com\/chrismetcalf\/vim-yankring) plugin.\r\n\r\n## Key Mappings ##\r\n\r\nBy default, yankstack adds only 2 key bindings, in normal and visual modes:\r\n\r\n- ```meta-p```  - cycle *backward* through your history of yanks\r\n- ```meta-shift-p```  - cycle *forwards* through your history of yanks\r\n\r\nAfter pasting some text using ```p``` or ```P```, you can cycle through your\r\nyank history using these commands.\r\n\r\nTyping either of these keys *without* pasting first will do a normal paste\r\n(the same as typing `p`). This also works in insert mode.\r\n\r\nA note about the meta key - if you're using MacVim, and you want to use\r\nthis plugin's default key bindings (or any bindings involving the `option`\r\nkey), you must ```:set macmeta```\r\n\r\n## Commands ##\r\n\r\nYou can see the contents of the yank-stack using the ```:Yanks``` command.\r\nIts output is similar to the ```:registers``` command.\r\n\r\n## Configuration ##\r\n\r\nYankstack defines two plugin mappings that you can map to keys of your choosing.\r\nThe same mappings work in normal and insert modes.\r\n\r\n- ```<Plug>yankstack_substitute_older_paste``` - cycle backwards through your history of yanks\r\n- ```<Plug>yankstack_substitute_newer_paste``` - cycle forwards through your history of yanks\r\n\r\nFor example, if you wanted to define some mappings based on your 'leader' key,\r\nyou could do this:\r\n\r\n```\r\nnmap <leader>p <Plug>yankstack_substitute_older_paste\r\nnmap <leader>P <Plug>yankstack_substitute_older_paste\r\n```\r\n\r\nAlso, if you want to load yankstack without the default key mappings, just\r\n``` let g:yankstack_map_keys = 0 ```\r\nin your .vimrc file.\r\n\r\n## Compatibility ##\r\n\r\nYankstack works by mapping the yank and paste keys to functions that do some\r\nbook-keeping before calling through to the normal yank\/paste keys. You may want\r\nto define your own mappings of the yank and paste keys. For example, I like to\r\nmap the ```Y``` key to ```y$```, so that it behaves the same as ```D``` and\r\n```C```. The yankstack mappings need to happen **before** you define any such\r\nmappings of your own. To achieve this, just call ```yankstack#setup()``` in\r\nyour vimrc, before defining your mappings:\r\n\r\n```\r\ncall yankstack#setup()\r\nnmap Y y$\r\n\" other mappings involving y, d, c, etc\r\n```\r\n\r\n## Contributing, Feedback ##\r\n\r\nI'd enjoy hearing anybody's feedback on yankstack, and welcome any contribution.\r\nCheck it out on [github](https:\/\/github.com\/maxbrunsfeld\/vim-yankstack)!\r\n\r\n## Changelog ##\r\n\r\n\r\n### 1.0.4 (2012-07-01)\r\n  - Make it so that yankstack-cycling keys cause a normal paste if they are\r\n    used without pasting first. Fix stack-cycling in insert-mode.\r\n\r\n### 1.0.3 (2012-05-04):\r\n  - Fix bug when overwriting text in select mode. This was causing\r\n    problems for snipMate users.\r\n\r\n### 1.0.2 (2012-4-20):\r\n  - Add test coverage using rspec and [vimbot](https:\/\/github.com\/maxbrunsfeld\/vimbot)!\r\n  - Perfect the behavior of the yankstack when pasting over text in visual\r\n    mode\r\n  - Fix bug where 's' and 'S' didn't push to the yankstack\r\n\r\n### 1.0.1 (2012-2-11):\r\n  - Change default key bindings, update readme, add link to github page.\r\n\r\n### 1.0.1 (2011-12-08):\r\n  - Fix bug when displaying empty yanks.\r\n\r\n### 1.0.0 (2011-12-04):\r\n  - Remove unnecessary dependency on the undotree() function. Plugin should\r\n    now work on any recent version of vim.\r\n\r\n## License ##\r\nCopyright (c) Max Brunsfeld.  Distributed under the same terms as Vim itself.\r\nSee the vim license.\r\n\r\n vim:tw=78:ts=8:ft=help:norl:\r\n","install_details":"## Installation ##\r\n\r\nI recommend loading your plugins with\r\n[pathogen](https:\/\/github.com\/tpope\/vim-pathogen), so you can just clone this\r\nrepo into your ```bundle``` directory.\r\n","5":"## Installation ##\r\n\r\nI recommend loading your plugins with\r\n[pathogen](https:\/\/github.com\/tpope\/vim-pathogen), so you can just clone this\r\nrepo into your ```bundle``` directory.\r\n","first_name":"Max","6":"Max","last_name":"Brunsfeld","7":"Brunsfeld","releases":[{"0":"3834","vim_version":"7.0","1":"7.0","script_version":"1.0.5","2":"1.0.5","version_comment":"Fix bugs","3":"Fix bugs","package":"yankstack.zip","4":"yankstack.zip","src_id":"18288","5":"18288","creation_date":"1342710722","6":"1342710722"},{"0":"3834","vim_version":"7.0","1":"7.0","script_version":"1.0.4","2":"1.0.4","version_comment":"Fix insert mode mappings.\r\nSimplify mappings - now, if you type the 'substitute_older_paste' or 'substitute_newer_paste' keys without pasting first, it will cause a paste. The same key bindings work in all modes.","3":"Fix insert mode mappings.\r\nSimplify mappings - now, if you type the 'substitute_older_paste' or 'substitute_newer_paste' keys without pasting first, it will cause a paste. The same key bindings work in all modes.","package":"yankstack.zip","4":"yankstack.zip","src_id":"18224","5":"18224","creation_date":"1341557139","6":"1341557139"},{"0":"3834","vim_version":"7.0","1":"7.0","script_version":"1.0.2","2":"1.0.2","version_comment":"  - Add test coverage using rspec and [vimbot](https:\/\/github.com\/maxbrunsfeld\/vimbot)!\r\n  - Perfect the behavior of the yankstack when pasting over text in visual\r\n    mode\r\n  - Fix bug where 's' and 'S' didn't push to the yankstack","3":"  - Add test coverage using rspec and [vimbot](https:\/\/github.com\/maxbrunsfeld\/vimbot)!\r\n  - Perfect the behavior of the yankstack when pasting over text in visual\r\n    mode\r\n  - Fix bug where 's' and 'S' didn't push to the yankstack","package":"yankstack.zip","4":"yankstack.zip","src_id":"17802","5":"17802","creation_date":"1334979574","6":"1334979574"},{"0":"3834","vim_version":"7.0","1":"7.0","script_version":"1.0.1","2":"1.0.1","version_comment":"add help file, update readme","3":"add help file, update readme","package":"yankstack.zip","4":"yankstack.zip","src_id":"17508","5":"17508","creation_date":"1329809326","6":"1329809326"},{"0":"3834","vim_version":"7.0","1":"7.0","script_version":"1.0.1","2":"1.0.1","version_comment":"Change default key bindings, update readme, add link to github page.","3":"Change default key bindings, update readme, add link to github page.","package":"yankstack.tar","4":"yankstack.tar","src_id":"17427","5":"17427","creation_date":"1328942592","6":"1328942592"},{"0":"3834","vim_version":"7.0","1":"7.0","script_version":"1.0.1","2":"1.0.1","version_comment":"Fix bug when displaying empty yanks","3":"Fix bug when displaying empty yanks","package":"yankstack.tar","4":"yankstack.tar","src_id":"17033","5":"17033","creation_date":"1323312435","6":"1323312435"},{"0":"3834","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Remove unnecessary dependency on the undotree() function. Plugin should now work on any recent version of vim.","3":"Remove unnecessary dependency on the undotree() function. Plugin should now work on any recent version of vim.","package":"yankstack.tar","4":"yankstack.tar","src_id":"17018","5":"17018","creation_date":"1322966577","6":"1322966577"}]},"3833":{"script_id":"3833","0":"3833","script_name":"TVO: The Vim Outliner with asciidoc supp","1":"TVO: The Vim Outliner with asciidoc supp","script_type":"ftplugin","2":"ftplugin","summary":"Easy and quick documentation in asciidoc.","3":"Easy and quick documentation in asciidoc.","description":"== description\r\notl-asciidoc implements outliner support for asciidoc. It is based on the great \"TVO: The Vim Outliner\" (http:\/\/www.vim.org\/scripts\/script.php?script_id=517), just adds a few code lines to the original otl.vim script. If you like \"TVO: The Vim Outliner\" and\/or are used to asciidoc, try this script.\r\n\r\n== usage\r\nIt provides outliner capability for asciidoc, which further ease and accelerate documentation in asciidoc.\r\n=== Keystrokes\r\nTo be compatible with TVO, type \"help otl\" or see README.otl in the vimoutliner-122.zip\r\n==== Supported ones\r\nMany commonly used keystrokes are supported, such as:\r\n. Heading folding\r\n\t=\topen heading (zo)\r\n\t-\tclose heading (zc)\r\n\tDisplay operations\r\n\t\t\\1\tshow level 1\r\n\t\t\\2\tshow level 2\r\n\t\t\\3\tshow level 3\r\n\t\t\\4\tshow level 4\r\n\t\t\\5\tshow level 5\r\n\t\t\\a\tshow all\r\n. Heading operations\r\n\t\\k\tmove cursor up one heading\r\n\t\\j\tmove cursor down one heading\r\n\t\\u\tmove heading up one\r\n\t\\d\tmove heading down one\r\n\r\n==== Not supported ones\r\n. Display operations\r\n\t\\8\tshow level 8\r\n\t\\9\tshow level 9\r\n\t\\t\ttoggle showing text\r\n\t\\C\tchange the current heading\r\n\t\\D\tdelete the current heading\r\n. ... \r\n\r\n=== screenshots\r\nNot yet.\r\n=== Compatibility\r\n==== Affect to otl style\r\nIt will not affect editing and operation in .otl \r\n==== Supported asciidoc format\r\n. Both one line heading and two lines heading mode are supported\r\n. Part of list styles are supported\r\n. Page break(<<<) is highlighted\r\n. Highlighting words(TODO, Note, Important, Warning, Caution) are supported\r\n\r\n== Notes\r\nThe sole purpose of publishing this script is to share the happiness of writing with the advantage of outliner and asciidoc both.\r\nThis script is based on Ned Konz's TVO: The Vim Outliner. Email inquiry for permission of publishing this derived version had been sent to Ned, but there is no response yet. Let me know anything inappropriate with this.","4":"== description\r\notl-asciidoc implements outliner support for asciidoc. It is based on the great \"TVO: The Vim Outliner\" (http:\/\/www.vim.org\/scripts\/script.php?script_id=517), just adds a few code lines to the original otl.vim script. If you like \"TVO: The Vim Outliner\" and\/or are used to asciidoc, try this script.\r\n\r\n== usage\r\nIt provides outliner capability for asciidoc, which further ease and accelerate documentation in asciidoc.\r\n=== Keystrokes\r\nTo be compatible with TVO, type \"help otl\" or see README.otl in the vimoutliner-122.zip\r\n==== Supported ones\r\nMany commonly used keystrokes are supported, such as:\r\n. Heading folding\r\n\t=\topen heading (zo)\r\n\t-\tclose heading (zc)\r\n\tDisplay operations\r\n\t\t\\1\tshow level 1\r\n\t\t\\2\tshow level 2\r\n\t\t\\3\tshow level 3\r\n\t\t\\4\tshow level 4\r\n\t\t\\5\tshow level 5\r\n\t\t\\a\tshow all\r\n. Heading operations\r\n\t\\k\tmove cursor up one heading\r\n\t\\j\tmove cursor down one heading\r\n\t\\u\tmove heading up one\r\n\t\\d\tmove heading down one\r\n\r\n==== Not supported ones\r\n. Display operations\r\n\t\\8\tshow level 8\r\n\t\\9\tshow level 9\r\n\t\\t\ttoggle showing text\r\n\t\\C\tchange the current heading\r\n\t\\D\tdelete the current heading\r\n. ... \r\n\r\n=== screenshots\r\nNot yet.\r\n=== Compatibility\r\n==== Affect to otl style\r\nIt will not affect editing and operation in .otl \r\n==== Supported asciidoc format\r\n. Both one line heading and two lines heading mode are supported\r\n. Part of list styles are supported\r\n. Page break(<<<) is highlighted\r\n. Highlighting words(TODO, Note, Important, Warning, Caution) are supported\r\n\r\n== Notes\r\nThe sole purpose of publishing this script is to share the happiness of writing with the advantage of outliner and asciidoc both.\r\nThis script is based on Ned Konz's TVO: The Vim Outliner. Email inquiry for permission of publishing this derived version had been sent to Ned, but there is no response yet. Let me know anything inappropriate with this.","install_details":"== installation\r\n=== Install TVO first\r\n=== Override the original otl.vim in ftplugin with this one\r\n=== Add following two lines in your .vimrc or _vimrc\r\n\tau BufNewFile,BufRead,BufEnter *.txt\tlet g:otl_asciidoc_style = 1\r\n\tau BufNewFile,BufRead,BufEnter *.txt\tsetf otl\r\n=== Open any asciidoc with .txt postfix and see what happened\r\n\r\n","5":"== installation\r\n=== Install TVO first\r\n=== Override the original otl.vim in ftplugin with this one\r\n=== Add following two lines in your .vimrc or _vimrc\r\n\tau BufNewFile,BufRead,BufEnter *.txt\tlet g:otl_asciidoc_style = 1\r\n\tau BufNewFile,BufRead,BufEnter *.txt\tsetf otl\r\n=== Open any asciidoc with .txt postfix and see what happened\r\n\r\n","first_name":"Xuesong","6":"Xuesong","last_name":"Lu","7":"Lu","releases":[{"0":"3833","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"otl.vim","4":"otl.vim","src_id":"17014","5":"17014","creation_date":"1322901765","6":"1322901765"}]},"3832":{"script_id":"3832","0":"3832","script_name":"SchemeXp","1":"SchemeXp","script_type":"utility","2":"utility","summary":"Scheme snippets for xptemplate","3":"Scheme snippets for xptemplate","description":"Here are some R5RS Scheme snippets for xptemplate.\r\n\r\nNOTE:  These snippets require the newest version of xptemplate from SVN or git.\r\n\r\nKnown issues:\r\n\r\n  Due to the limitations of the current version of xptemplate, the \"let*\" snippet is named \"letstar\".\r\n","4":"Here are some R5RS Scheme snippets for xptemplate.\r\n\r\nNOTE:  These snippets require the newest version of xptemplate from SVN or git.\r\n\r\nKnown issues:\r\n\r\n  Due to the limitations of the current version of xptemplate, the \"let*\" snippet is named \"letstar\".\r\n","install_details":"To install these snippets:\r\n\r\n - get xptemplate from SVN or git (important!  xptemplate from vim.org will **not** work!)\r\n - install and configure xptemplate\r\n - download these snippets\r\n - rename the downloaded snippet file as \"scheme.xpt.vim\"\r\n - move it in to the ftplugin\/scheme directory under the path you've chosen according to\r\n      :help xpt-personal-folder\r\n - quit and restart vim\r\n","5":"To install these snippets:\r\n\r\n - get xptemplate from SVN or git (important!  xptemplate from vim.org will **not** work!)\r\n - install and configure xptemplate\r\n - download these snippets\r\n - rename the downloaded snippet file as \"scheme.xpt.vim\"\r\n - move it in to the ftplugin\/scheme directory under the path you've chosen according to\r\n      :help xpt-personal-folder\r\n - quit and restart vim\r\n","first_name":"Gnosis","6":"Gnosis","last_name":"Ouroubouros","7":"Ouroubouros","releases":[{"0":"3832","vim_version":"7.0","1":"7.0","script_version":"1.2","2":"1.2","version_comment":"Added the following snippets:  eq?  equal?  quote","3":"Added the following snippets:  eq?  equal?  quote","package":"scheme.xpt.vim","4":"scheme.xpt.vim","src_id":"17011","5":"17011","creation_date":"1322815013","6":"1322815013"},{"0":"3832","vim_version":"7.0","1":"7.0","script_version":"1.1","2":"1.1","version_comment":"Fixed \"string\" snippet.","3":"Fixed \"string\" snippet.","package":"scheme.xpt.vim","4":"scheme.xpt.vim","src_id":"17010","5":"17010","creation_date":"1322812276","6":"1322812276"}]},"3831":{"script_id":"3831","0":"3831","script_name":"LastBuf.vim","1":"LastBuf.vim","script_type":"utility","2":"utility","summary":"open last closed buffers.","3":"open last closed buffers.","description":"\r\nlastbuf.vim is a plugin to open last closed buffers.\r\n\r\nYou can reopen your last closed buffer by :LastBuf or `<c-w><c-z>`.\r\n\r\nbuffers closed with :hid will always be opened.\r\n\r\nbuffers closed with :e # :q :only :close :bun :bd will be reopened by default.\r\n\r\nbuffers closed with :bw (!!CAUTION) will never be reopened.\r\n\r\n\r\nyou can get the newest version at https:\/\/github.com\/Rykka\/lastbuf.vim\r\n\r\n\r\n    \":LastBuf mapping is <c-w><c-z> by default.\r\n    \" You can remapping it by \r\n    map <c-s-t> :LastBuf<CR>\r\n\r\n    \" g:lastbuf_num option decides the max reopen buf number.\r\n    let g:lastbuf_num=20\r\n\r\n    \" g:lastbuf_seekall option decides whether lastbuf will reopen \r\n    \" the unloaded buffer or not.\r\n    \" if you don't want open the unloaded bufs. \r\n    \" set it to 0 and set 'nohidden'\r\n    let g:lastbuf_seekall=1\r\n\r\n","4":"\r\nlastbuf.vim is a plugin to open last closed buffers.\r\n\r\nYou can reopen your last closed buffer by :LastBuf or `<c-w><c-z>`.\r\n\r\nbuffers closed with :hid will always be opened.\r\n\r\nbuffers closed with :e # :q :only :close :bun :bd will be reopened by default.\r\n\r\nbuffers closed with :bw (!!CAUTION) will never be reopened.\r\n\r\n\r\nyou can get the newest version at https:\/\/github.com\/Rykka\/lastbuf.vim\r\n\r\n\r\n    \":LastBuf mapping is <c-w><c-z> by default.\r\n    \" You can remapping it by \r\n    map <c-s-t> :LastBuf<CR>\r\n\r\n    \" g:lastbuf_num option decides the max reopen buf number.\r\n    let g:lastbuf_num=20\r\n\r\n    \" g:lastbuf_seekall option decides whether lastbuf will reopen \r\n    \" the unloaded buffer or not.\r\n    \" if you don't want open the unloaded bufs. \r\n    \" set it to 0 and set 'nohidden'\r\n    let g:lastbuf_seekall=1\r\n\r\n","install_details":"","5":"","first_name":"Rykka","6":"Rykka","last_name":"f","7":"f","releases":[{"0":"3831","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"lastbuf.vim.tar.gz","4":"lastbuf.vim.tar.gz","src_id":"17004","5":"17004","creation_date":"1322755965","6":"1322755965"}]},"3830":{"script_id":"3830","0":"3830","script_name":"better-snipmate-snippet","1":"better-snipmate-snippet","script_type":"utility","2":"utility","summary":"Better Snipmate Snippets for VIM","3":"Better Snipmate Snippets for VIM","description":"This repository is kind of hybrid of snipmate.vim and snipmate-snippets.","4":"This repository is kind of hybrid of snipmate.vim and snipmate-snippets.","install_details":"I recommend installing pathogen.vim, and then simply copy and paste:\r\n\r\ncd ~\/.vim\/bundle\r\ngit clone git:\/\/github.com\/bartlomiejdanek\/better-snipmate-snippets.git","5":"I recommend installing pathogen.vim, and then simply copy and paste:\r\n\r\ncd ~\/.vim\/bundle\r\ngit clone git:\/\/github.com\/bartlomiejdanek\/better-snipmate-snippets.git","first_name":"Bart\u0142omiej","6":"Bartłomiej","last_name":"Danek","7":"Danek","releases":[{"0":"3830","vim_version":"7.0","1":"7.0","script_version":"0.2","2":"0.2","version_comment":"- improve existing snippets for Ruby and Rails\r\n- new Ruby and Rails snippets \r\n\r\nhttps:\/\/github.com\/bartekd\/better-snipmate-snippets\/tree\/v0.2","3":"- improve existing snippets for Ruby and Rails\r\n- new Ruby and Rails snippets \r\n\r\nhttps:\/\/github.com\/bartekd\/better-snipmate-snippets\/tree\/v0.2","package":"better-snipmate-snippets.tar.gz","4":"better-snipmate-snippets.tar.gz","src_id":"17020","5":"17020","creation_date":"1323015362","6":"1323015362"},{"0":"3830","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"better-snipmate-snippets.tar.gz","4":"better-snipmate-snippets.tar.gz","src_id":"16997","5":"16997","creation_date":"1322602795","6":"1322602795"}]},"3829":{"script_id":"3829","0":"3829","script_name":"inline_edit.vim","1":"inline_edit.vim","script_type":"utility","2":"utility","summary":"Edit code that's embedded within other code","3":"Edit code that's embedded within other code","description":"Github project: https:\/\/github.com\/AndrewRadev\/inline_edit.vim\r\n\r\nEditing javascript within HTML is annoying. To generalize, editing code that's embedded in some different code is annoying.\r\n\r\nGiven the following example:\r\n\r\n    <script type=\"text\/javascript\">\r\n      $(document).ready(function() {\r\n        $('#foo').click(function() {\r\n          alert('OK');\r\n        });\r\n      })\r\n    <\/script>\r\n\r\nExecute :InlineEdit within the script tag. A proxy buffer is opened with only the javascript. Saving the proxy buffer updates the original one. You can reindent, lint, slice and dice as much as you like.\r\n\r\nCurrently, it works for:\r\n\r\n- Javascript and CSS within HTML -- see above example\r\n- SQL within ruby (matches \"<<-SQL\")\r\n\r\n    def some_heavy_query\r\n      execute <<-SQL\r\n        SELECT * FROM users WHERE something = 'other';\r\n      SQL\r\n    end\r\n\r\n- Code within fenced markdown blocks\r\n\r\n    Some text.\r\n\r\n    ``` ruby\r\n    def foo\r\n      puts \"OK\"\r\n    end\r\n    ```\r\n\r\n    Some other text.\r\n\r\n- Django blocks in templates\r\n\r\n    {%  block content %}\r\n    <h1>{{ section.title }}<\/h1>\r\n    {% endblock %}\r\n\r\nPlease check the docs for more detailed instructions.\r\n\r\nIf you encounter any bugs or have ideas for new features, the issue tracker is on github, at https:\/\/github.com\/AndrewRadev\/inline_edit.vim\/issues.\r\n","4":"Github project: https:\/\/github.com\/AndrewRadev\/inline_edit.vim\r\n\r\nEditing javascript within HTML is annoying. To generalize, editing code that's embedded in some different code is annoying.\r\n\r\nGiven the following example:\r\n\r\n    <script type=\"text\/javascript\">\r\n      $(document).ready(function() {\r\n        $('#foo').click(function() {\r\n          alert('OK');\r\n        });\r\n      })\r\n    <\/script>\r\n\r\nExecute :InlineEdit within the script tag. A proxy buffer is opened with only the javascript. Saving the proxy buffer updates the original one. You can reindent, lint, slice and dice as much as you like.\r\n\r\nCurrently, it works for:\r\n\r\n- Javascript and CSS within HTML -- see above example\r\n- SQL within ruby (matches \"<<-SQL\")\r\n\r\n    def some_heavy_query\r\n      execute <<-SQL\r\n        SELECT * FROM users WHERE something = 'other';\r\n      SQL\r\n    end\r\n\r\n- Code within fenced markdown blocks\r\n\r\n    Some text.\r\n\r\n    ``` ruby\r\n    def foo\r\n      puts \"OK\"\r\n    end\r\n    ```\r\n\r\n    Some other text.\r\n\r\n- Django blocks in templates\r\n\r\n    {%  block content %}\r\n    <h1>{{ section.title }}<\/h1>\r\n    {% endblock %}\r\n\r\nPlease check the docs for more detailed instructions.\r\n\r\nIf you encounter any bugs or have ideas for new features, the issue tracker is on github, at https:\/\/github.com\/AndrewRadev\/inline_edit.vim\/issues.\r\n","install_details":"There are several ways to install the plugin. The recommended one is by using\r\nTim Pope's pathogen (http:\/\/www.vim.org\/scripts\/script.php?script_id=2332). In\r\nthat case, you can clone the plugin's git repository like so:\r\n\r\n    git clone git:\/\/github.com\/AndrewRadev\/inline_edit.vim.git ~\/.vim\/bundle\/inline_edit\r\n\r\nIf your vim configuration is under git version control, you could also set up\r\nthe repository as a submodule, which would allow you to update more easily.\r\nThe command is (provided you're in ~\/.vim):\r\n\r\n    git submodule add git:\/\/github.com\/AndrewRadev\/inline_edit.vim.git bundle\/inline_edit\r\n\r\nAnother way is to simply copy all the essential directories inside the ~.vim\/\r\ndirectory: plugin, autoload, doc.","5":"There are several ways to install the plugin. The recommended one is by using\r\nTim Pope's pathogen (http:\/\/www.vim.org\/scripts\/script.php?script_id=2332). In\r\nthat case, you can clone the plugin's git repository like so:\r\n\r\n    git clone git:\/\/github.com\/AndrewRadev\/inline_edit.vim.git ~\/.vim\/bundle\/inline_edit\r\n\r\nIf your vim configuration is under git version control, you could also set up\r\nthe repository as a submodule, which would allow you to update more easily.\r\nThe command is (provided you're in ~\/.vim):\r\n\r\n    git submodule add git:\/\/github.com\/AndrewRadev\/inline_edit.vim.git bundle\/inline_edit\r\n\r\nAnother way is to simply copy all the essential directories inside the ~.vim\/\r\ndirectory: plugin, autoload, doc.","first_name":"Andrew","6":"Andrew","last_name":"Radev","7":"Radev","releases":[{"0":"3829","vim_version":"7.4","1":"7.4","script_version":"0.3.0","2":"0.3.0","version_comment":"- Option to decide how to open the buffer (tab, split, etc.)\r\n- Option to disable custom statusline\r\n- Vue support\r\n- Adjust indent based on existing code\r\n- Bugfixes","3":"- Option to decide how to open the buffer (tab, split, etc.)\r\n- Option to disable custom statusline\r\n- Vue support\r\n- Adjust indent based on existing code\r\n- Bugfixes","package":"inline_edit.zip","4":"inline_edit.zip","src_id":"26581","5":"26581","creation_date":"1562041891","6":"1562041891"},{"0":"3829","vim_version":"7.0","1":"7.0","script_version":"0.2.1","2":"0.2.1","version_comment":"Minor improvements","3":"Minor improvements","package":"inline_edit.zip","4":"inline_edit.zip","src_id":"22835","5":"22835","creation_date":"1422351634","6":"1422351634"},{"0":"3829","vim_version":"7.0","1":"7.0","script_version":"0.2.0","2":"0.2.0","version_comment":"- Edit scripts embedded in Vimscript (ruby, python, etc.)\r\n- Easier extending for html-like filetypes\r\n- Correct handling of RO buffers\r\n- Edit heredocs in shell, ruby, perl\r\n- Better cursor repositioning\r\n- \"scratch\" and \"tempfile\" temporary buffer types\r\n- Various bugfixes","3":"- Edit scripts embedded in Vimscript (ruby, python, etc.)\r\n- Easier extending for html-like filetypes\r\n- Correct handling of RO buffers\r\n- Edit heredocs in shell, ruby, perl\r\n- Better cursor repositioning\r\n- \"scratch\" and \"tempfile\" temporary buffer types\r\n- Various bugfixes","package":"inline_edit.zip","4":"inline_edit.zip","src_id":"19617","5":"19617","creation_date":"1362909098","6":"1362909098"},{"0":"3829","vim_version":"7.0","1":"7.0","script_version":"0.1.0","2":"0.1.0","version_comment":"- Support for stylesheet tags in HTML\r\n- InlineEdit-ing a visually selected area\r\n- Possibility to use several proxy buffers at the same time\r\n- Possibility to extend plugin with new patterns\r\n- Support for filetypes with &noexpandtab","3":"- Support for stylesheet tags in HTML\r\n- InlineEdit-ing a visually selected area\r\n- Possibility to use several proxy buffers at the same time\r\n- Possibility to extend plugin with new patterns\r\n- Support for filetypes with &noexpandtab","package":"inline_edit.zip","4":"inline_edit.zip","src_id":"17079","5":"17079","creation_date":"1324145064","6":"1324145064"},{"0":"3829","vim_version":"7.0","1":"7.0","script_version":"0.0.1","2":"0.0.1","version_comment":"Initial upload","3":"Initial upload","package":"inline_edit.zip","4":"inline_edit.zip","src_id":"16996","5":"16996","creation_date":"1322598334","6":"1322598334"}]},"3828":{"script_id":"3828","0":"3828","script_name":"aurum","1":"aurum","script_type":"utility","2":"utility","summary":"Plugin for dealing with source files under various VCS control","3":"Plugin for dealing with source files under various VCS control","description":"\r\nThis plugin provides a vim <--> VCS (currently mercurial, git and subversion) \r\nintegration for your projects. Features:\r\n  - Partially committing changes (:AuRecord [1]).\r\n  - Viewing file state at particular revision (aurum:\/\/file [2], :AuFile [3]).\r\n  - Viewing uncommited changes in a vimdiff [4], as well as changes between \r\n    specific revisions (:AuVimDiff [5]). It is also possible to open multiple \r\n    tabs with all changes to all files viewed as side-by-side diffs.\r\n  - Viewing revisions log (:AuLog [6]). Output is highly customizable.\r\n  - Viewing working directory status (:AuStatus [7]).\r\n  - Commiting changes (:AuCommit [8]), commit messages are remembered in case of \r\n    rollback (g:aurum_remembermsg [9]).\r\n  - Obtaining various URL’s out of remote repository URL (like URL of the HTML \r\n    version of the current file with URL fragment pointing to the current line \r\n    attached: useful for sharing) (:AuHyperlink [10]). For mercurial it also \r\n    supports git and subversion revisions (in case you are using hg-git and \r\n    hgsubversion respectively).\r\n  - aurum#changeset() [11], aurum#repository() [12] and aurum#status() [13] functions \r\n    that are to be used from modeline.\r\n  - Frontends for various other VCS commands.\r\nMost commands can be reached with a set of mappings (see aurum-mappings [14]), \r\nall mappings are customizable.\r\n\r\nPlugin’s mercurial driver is able to use mercurial python API as well as its \r\nCLI, but remember that the former is much slower and less tested. In order to \r\nuse mercurial python API you must have vim compiled with +python [15] (mercurial \r\ncurrently does not support python 3) and have mercurial in python’s sys.path \r\n(note: on windows msi installer is not adding mercurial to sys.path, so you \r\nwon’t be able to use its python API).\r\n\r\nPlugin requires some additional plugins:\r\n  - frawor (https:\/\/bitbucket.org\/ZyX_I\/frawor)\r\n  - (optional) ansi_esc_echo (https:\/\/bitbucket.org\/ZyX_I\/ansi_esc_echo)\r\n  - (optional) one of\r\n      - Command-T (vimscript #3025)\r\n      - ctrlp (vimscript #3736)\r\n      - FuzzyFinder (vimscript #1984)\r\n      - unite (vimscript #3396)\r\n      - ku (vimscript #2337)\r\n      - tlib (vimscript #1863)\r\n    for :AuFile [3] prompt option and a number of OpenAny\/AnnotateAny mappings.\r\n(with their dependencies).\r\n\r\nNote: aurum supports VAM (https:\/\/github.com\/MarcWeber\/vim-addon-manager). It \r\n      is prefered that you use it for aurum installation.\r\n\r\n\r\nProject page: https:\/\/bitbucket.org\/ZyX_I\/aurum\r\nDocumentation: http:\/\/vimpluginloader.sourceforge.net\/doc\/aurum.txt.html\r\n\r\n\r\n[1] http:\/\/vimcommunity.bitbucket.org\/doc\/aurum.txt.html#.3aAuRecord\r\n[2] http:\/\/vimcommunity.bitbucket.org\/doc\/aurum.txt.html#aurum.3a.2f.2ffile\r\n[3] http:\/\/vimcommunity.bitbucket.org\/doc\/aurum.txt.html#.3aAuFile\r\n[4] http:\/\/vimcommunity.bitbucket.org\/doc\/diff.txt.html#vimdiff\r\n[5] http:\/\/vimcommunity.bitbucket.org\/doc\/aurum.txt.html#.3aAuVimDiff\r\n[6] http:\/\/vimcommunity.bitbucket.org\/doc\/aurum.txt.html#.3aAuLog\r\n[7] http:\/\/vimcommunity.bitbucket.org\/doc\/aurum.txt.html#.3aAuStatus\r\n[8] http:\/\/vimcommunity.bitbucket.org\/doc\/aurum.txt.html#.3aAuCommit\r\n[9] http:\/\/vimcommunity.bitbucket.org\/doc\/aurum.txt.html#g.3aaurum_remembermsg\r\n[10] http:\/\/vimcommunity.bitbucket.org\/doc\/aurum.txt.html#.3aAuHyperlink\r\n[11] http:\/\/vimcommunity.bitbucket.org\/doc\/aurum.txt.html#aurum.23changeset.28.29\r\n[12] http:\/\/vimcommunity.bitbucket.org\/doc\/aurum.txt.html#aurum.23repository.28.29\r\n[13] http:\/\/vimcommunity.bitbucket.org\/doc\/aurum.txt.html#aurum.23status.28.29\r\n[14] http:\/\/vimcommunity.bitbucket.org\/doc\/aurum.txt.html#aurum-mappings\r\n[15] http:\/\/vimcommunity.bitbucket.org\/doc\/various.txt.html#.2bpython\r\n\r\n","4":"\r\nThis plugin provides a vim <--> VCS (currently mercurial, git and subversion) \r\nintegration for your projects. Features:\r\n  - Partially committing changes (:AuRecord [1]).\r\n  - Viewing file state at particular revision (aurum:\/\/file [2], :AuFile [3]).\r\n  - Viewing uncommited changes in a vimdiff [4], as well as changes between \r\n    specific revisions (:AuVimDiff [5]). It is also possible to open multiple \r\n    tabs with all changes to all files viewed as side-by-side diffs.\r\n  - Viewing revisions log (:AuLog [6]). Output is highly customizable.\r\n  - Viewing working directory status (:AuStatus [7]).\r\n  - Commiting changes (:AuCommit [8]), commit messages are remembered in case of \r\n    rollback (g:aurum_remembermsg [9]).\r\n  - Obtaining various URL’s out of remote repository URL (like URL of the HTML \r\n    version of the current file with URL fragment pointing to the current line \r\n    attached: useful for sharing) (:AuHyperlink [10]). For mercurial it also \r\n    supports git and subversion revisions (in case you are using hg-git and \r\n    hgsubversion respectively).\r\n  - aurum#changeset() [11], aurum#repository() [12] and aurum#status() [13] functions \r\n    that are to be used from modeline.\r\n  - Frontends for various other VCS commands.\r\nMost commands can be reached with a set of mappings (see aurum-mappings [14]), \r\nall mappings are customizable.\r\n\r\nPlugin’s mercurial driver is able to use mercurial python API as well as its \r\nCLI, but remember that the former is much slower and less tested. In order to \r\nuse mercurial python API you must have vim compiled with +python [15] (mercurial \r\ncurrently does not support python 3) and have mercurial in python’s sys.path \r\n(note: on windows msi installer is not adding mercurial to sys.path, so you \r\nwon’t be able to use its python API).\r\n\r\nPlugin requires some additional plugins:\r\n  - frawor (https:\/\/bitbucket.org\/ZyX_I\/frawor)\r\n  - (optional) ansi_esc_echo (https:\/\/bitbucket.org\/ZyX_I\/ansi_esc_echo)\r\n  - (optional) one of\r\n      - Command-T (vimscript #3025)\r\n      - ctrlp (vimscript #3736)\r\n      - FuzzyFinder (vimscript #1984)\r\n      - unite (vimscript #3396)\r\n      - ku (vimscript #2337)\r\n      - tlib (vimscript #1863)\r\n    for :AuFile [3] prompt option and a number of OpenAny\/AnnotateAny mappings.\r\n(with their dependencies).\r\n\r\nNote: aurum supports VAM (https:\/\/github.com\/MarcWeber\/vim-addon-manager). It \r\n      is prefered that you use it for aurum installation.\r\n\r\n\r\nProject page: https:\/\/bitbucket.org\/ZyX_I\/aurum\r\nDocumentation: http:\/\/vimpluginloader.sourceforge.net\/doc\/aurum.txt.html\r\n\r\n\r\n[1] http:\/\/vimcommunity.bitbucket.org\/doc\/aurum.txt.html#.3aAuRecord\r\n[2] http:\/\/vimcommunity.bitbucket.org\/doc\/aurum.txt.html#aurum.3a.2f.2ffile\r\n[3] http:\/\/vimcommunity.bitbucket.org\/doc\/aurum.txt.html#.3aAuFile\r\n[4] http:\/\/vimcommunity.bitbucket.org\/doc\/diff.txt.html#vimdiff\r\n[5] http:\/\/vimcommunity.bitbucket.org\/doc\/aurum.txt.html#.3aAuVimDiff\r\n[6] http:\/\/vimcommunity.bitbucket.org\/doc\/aurum.txt.html#.3aAuLog\r\n[7] http:\/\/vimcommunity.bitbucket.org\/doc\/aurum.txt.html#.3aAuStatus\r\n[8] http:\/\/vimcommunity.bitbucket.org\/doc\/aurum.txt.html#.3aAuCommit\r\n[9] http:\/\/vimcommunity.bitbucket.org\/doc\/aurum.txt.html#g.3aaurum_remembermsg\r\n[10] http:\/\/vimcommunity.bitbucket.org\/doc\/aurum.txt.html#.3aAuHyperlink\r\n[11] http:\/\/vimcommunity.bitbucket.org\/doc\/aurum.txt.html#aurum.23changeset.28.29\r\n[12] http:\/\/vimcommunity.bitbucket.org\/doc\/aurum.txt.html#aurum.23repository.28.29\r\n[13] http:\/\/vimcommunity.bitbucket.org\/doc\/aurum.txt.html#aurum.23status.28.29\r\n[14] http:\/\/vimcommunity.bitbucket.org\/doc\/aurum.txt.html#aurum-mappings\r\n[15] http:\/\/vimcommunity.bitbucket.org\/doc\/various.txt.html#.2bpython\r\n\r\n","install_details":"You can install this plugin using vim-addon-manager (vimscript #2905) plugin (install VAM, run “ActivateAddons aurum” and add “call vam#ActivateAddons(['aurum'])” to your .vimrc. VAM will install all dependencies for you). You can also use archives attached to this page, they contain plugin with all dependencies, so you do not need to fetch them yourself. \r\n\r\nGentoo users can use the following mercurial overlay: http:\/\/vimpluginloader.hg.sourceforge.net:8000\/hgroot\/vimpluginloader\/pluginloader-overlay.","5":"You can install this plugin using vim-addon-manager (vimscript #2905) plugin (install VAM, run “ActivateAddons aurum” and add “call vam#ActivateAddons(['aurum'])” to your .vimrc. VAM will install all dependencies for you). You can also use archives attached to this page, they contain plugin with all dependencies, so you do not need to fetch them yourself. \r\n\r\nGentoo users can use the following mercurial overlay: http:\/\/vimpluginloader.hg.sourceforge.net:8000\/hgroot\/vimpluginloader\/pluginloader-overlay.","first_name":"ZyX","6":"ZyX","last_name":" ","7":" ","releases":[{"0":"3828","vim_version":"7.3","1":"7.3","script_version":"1.8.1","2":"1.8.1","version_comment":"Two fixes to gJ\/gK mappings: update did not work with renames equal to zero and subversion driver incorrectly set “children” property","3":"Two fixes to gJ\/gK mappings: update did not work with renames equal to zero and subversion driver incorrectly set “children” property","package":"aurum-1.8.1.tar.gz","4":"aurum-1.8.1.tar.gz","src_id":"20914","5":"20914","creation_date":"1381525859","6":"1381525859"},{"0":"3828","vim_version":"7.3","1":"7.3","script_version":"1.8","2":"1.8","version_comment":"Improved :AuName [1] completion.\nAdded :AuRecord [2] amend and :AuCommit [3] amend.\nJ\/K mappings used in buffers opened by :AuVimDiff [4] now do not cancel diff mode.\nAdd gJ\/gK mappings for aurum:\/\/file [5] and aurum:\/\/annotate [6]: they bring the\nuser to the next or previous revision where given file changed.\nAdd <C-r><C-h> and <C-r><C-v> global mappings: they insert current revision hash\n(<C-r><C-h>) or current revision number into the buffer or command-line.\nUpdated hypsites so that they now know about sourceforge update and\ncode.google.com\/r URLs.\nSubversion driver is now faster when using gJ\/gK mappings in aurum:\/\/file [5]\nbuffers.\nSome fixes:\n- Workaround problem when committing Gentoo ebuild if Gentoo plugins are\n  installed.\n- aurum:\/\/ [7] buffers are automatically closed in case they failed to open.\n- aurum:\/\/edit buffers (used in :AuRecord [2]) now do not fail for non-existent\n  files.\n- Subversion driver now does not create duplicate entries in :AuLog [8] output.\n- Subversion driver now does filter files in aurum-rf-status [9] function in\n  all cases.\n\n[1] http:\/\/vimpluginloader.sourceforge.net\/doc\/aurum.txt.html#.3aAuName\n[2] http:\/\/vimpluginloader.sourceforge.net\/doc\/aurum.txt.html#.3aAuRecord\n[3] http:\/\/vimpluginloader.sourceforge.net\/doc\/aurum.txt.html#.3aAuCommit\n[4] http:\/\/vimpluginloader.sourceforge.net\/doc\/aurum.txt.html#.3aAuVimDiff\n[5] http:\/\/vimpluginloader.sourceforge.net\/doc\/aurum.txt.html#aurum.3a.2f.2ffile\n[6] http:\/\/vimpluginloader.sourceforge.net\/doc\/aurum.txt.html#aurum.3a.2f.2fannotate\n[7] http:\/\/vimpluginloader.sourceforge.net\/doc\/aurum.txt.html#aurum.3a.2f.2f\n[8] http:\/\/vimpluginloader.sourceforge.net\/doc\/aurum.txt.html#.3aAuLog\n[9] http:\/\/vimpluginloader.sourceforge.net\/doc\/aurum.txt.html#aurum-rf-status","3":"Improved :AuName [1] completion.\nAdded :AuRecord [2] amend and :AuCommit [3] amend.\nJ\/K mappings used in buffers opened by :AuVimDiff [4] now do not cancel diff mode.\nAdd gJ\/gK mappings for aurum:\/\/file [5] and aurum:\/\/annotate [6]: they bring the\nuser to the next or previous revision where given file changed.\nAdd <C-r><C-h> and <C-r><C-v> global mappings: they insert current revision hash\n(<C-r><C-h>) or current revision number into the buffer or command-line.\nUpdated hypsites so that they now know about sourceforge update and\ncode.google.com\/r URLs.\nSubversion driver is now faster when using gJ\/gK mappings in aurum:\/\/file [5]\nbuffers.\nSome fixes:\n- Workaround problem when committing Gentoo ebuild if Gentoo plugins are\n  installed.\n- aurum:\/\/ [7] buffers are automatically closed in case they failed to open.\n- aurum:\/\/edit buffers (used in :AuRecord [2]) now do not fail for non-existent\n  files.\n- Subversion driver now does not create duplicate entries in :AuLog [8] output.\n- Subversion driver now does filter files in aurum-rf-status [9] function in\n  all cases.\n\n[1] http:\/\/vimpluginloader.sourceforge.net\/doc\/aurum.txt.html#.3aAuName\n[2] http:\/\/vimpluginloader.sourceforge.net\/doc\/aurum.txt.html#.3aAuRecord\n[3] http:\/\/vimpluginloader.sourceforge.net\/doc\/aurum.txt.html#.3aAuCommit\n[4] http:\/\/vimpluginloader.sourceforge.net\/doc\/aurum.txt.html#.3aAuVimDiff\n[5] http:\/\/vimpluginloader.sourceforge.net\/doc\/aurum.txt.html#aurum.3a.2f.2ffile\n[6] http:\/\/vimpluginloader.sourceforge.net\/doc\/aurum.txt.html#aurum.3a.2f.2fannotate\n[7] http:\/\/vimpluginloader.sourceforge.net\/doc\/aurum.txt.html#aurum.3a.2f.2f\n[8] http:\/\/vimpluginloader.sourceforge.net\/doc\/aurum.txt.html#.3aAuLog\n[9] http:\/\/vimpluginloader.sourceforge.net\/doc\/aurum.txt.html#aurum-rf-status","package":"aurum-1.8.tar.gz","4":"aurum-1.8.tar.gz","src_id":"20890","5":"20890","creation_date":"1381066707","6":"1381066707"},{"0":"3828","vim_version":"7.3","1":"7.3","script_version":"1.7.1","2":"1.7.1","version_comment":"Make :AuH always use current changeset (it was using working directory changeset for url types “bundle”, “changeset” and “log”)\nFix “buffer does not exist” message shown after committing with AuRecord","3":"Make :AuH always use current changeset (it was using working directory changeset for url types “bundle”, “changeset” and “log”)\nFix “buffer does not exist” message shown after committing with AuRecord","package":"aurum-1.7.1.tar.gz","4":"aurum-1.7.1.tar.gz","src_id":"19716","5":"19716","creation_date":"1364497119","6":"1364497119"},{"0":"3828","vim_version":"9999","1":"9999","script_version":"1.7","2":"1.7","version_comment":"Added new powerline support\nAdded a number of AuFile mappings\nImproved handling of wiping vimdiff buffers\nAdded renames support in AuFile and AuAnnotate\nAdded g:aurum_showprogress option\nAdded partial support for pygit2\nAdded partial support for bzrlib\nMade querying status in separate process work regardless of presense of pyeval()\nFixed cursorbind for AuAnnotate\nFixed occasionally happenning “Cannot convert returned object to vim value” error\nFixed forced branch delete for git driver\nMade it use new frawor autoloading capabilities","3":"Added new powerline support\nAdded a number of AuFile mappings\nImproved handling of wiping vimdiff buffers\nAdded renames support in AuFile and AuAnnotate\nAdded g:aurum_showprogress option\nAdded partial support for pygit2\nAdded partial support for bzrlib\nMade querying status in separate process work regardless of presense of pyeval()\nFixed cursorbind for AuAnnotate\nFixed occasionally happenning “Cannot convert returned object to vim value” error\nFixed forced branch delete for git driver\nMade it use new frawor autoloading capabilities","package":"aurum-1.7.tar.gz","4":"aurum-1.7.tar.gz","src_id":"19490","5":"19490","creation_date":"1360410198","6":"1360410198"},{"0":"3828","vim_version":"7.3","1":"7.3","script_version":"1.6","2":"1.6","version_comment":"Made aurum#status and aurum#branch functions use python multiprocessing module for improving their speed (not in bazaar driver)\nMade repo.functions.pull also update when using mercurial driver\nMade repo.functions.pull use “svn update” in subversion driver\nAdded full undo support in :AuRecord status buffer (it now can undo changes to file you edited)\nRemoved some unneeded Hit-Enter prompts\nAdded support for passwords in subversion (and other) repository URLs\nAdded mappings for opening diff or vimdiff split(s) from commit buffer\nAdded option for automatically opening diff with changes that are to be committed (excluding unknown and deleted files) when commit buffer is opened\nAdded initial bazaar support (all functions are there and working, but speed is far from optimal)","3":"Made aurum#status and aurum#branch functions use python multiprocessing module for improving their speed (not in bazaar driver)\nMade repo.functions.pull also update when using mercurial driver\nMade repo.functions.pull use “svn update” in subversion driver\nAdded full undo support in :AuRecord status buffer (it now can undo changes to file you edited)\nRemoved some unneeded Hit-Enter prompts\nAdded support for passwords in subversion (and other) repository URLs\nAdded mappings for opening diff or vimdiff split(s) from commit buffer\nAdded option for automatically opening diff with changes that are to be committed (excluding unknown and deleted files) when commit buffer is opened\nAdded initial bazaar support (all functions are there and working, but speed is far from optimal)","package":"aurum-1.6.tar.gz","4":"aurum-1.6.tar.gz","src_id":"18934","5":"18934","creation_date":"1351783924","6":"1351783924"},{"0":"3828","vim_version":"7.3","1":"7.3","script_version":"1.5.7","2":"1.5.7","version_comment":"Made git driver use fast-forward merges when pulling\nNow using ansi_esc_echo in more cases\nFixed AuGrep when using git driver (errors when grep found nothing)\nFixed :AuHyperlink when using git driver (problems when pushurl is not defined, regression introduced in 1.5.1)\nMade gitrepo.push\/pull not be silent","3":"Made git driver use fast-forward merges when pulling\nNow using ansi_esc_echo in more cases\nFixed AuGrep when using git driver (errors when grep found nothing)\nFixed :AuHyperlink when using git driver (problems when pushurl is not defined, regression introduced in 1.5.1)\nMade gitrepo.push\/pull not be silent","package":"aurum-1.5.7.tar.gz","4":"aurum-1.5.7.tar.gz","src_id":"18750","5":"18750","creation_date":"1349517654","6":"1349517654"},{"0":"3828","vim_version":"7.3","1":"7.3","script_version":"1.5.6","2":"1.5.6","version_comment":"Added support tlib, ku and unite\nMade AuVimDiff full only narrow file list when “files” option was specified\nImproved code that disables vimdiff when closing one of the buffers: it is now always used and it works when closing both “original” and “changeset” versions","3":"Added support tlib, ku and unite\nMade AuVimDiff full only narrow file list when “files” option was specified\nImproved code that disables vimdiff when closing one of the buffers: it is now always used and it works when closing both “original” and “changeset” versions","package":"aurum-1.5.6.tar.gz","4":"aurum-1.5.6.tar.gz","src_id":"18531","5":"18531","creation_date":"1346606417","6":"1346606417"},{"0":"3828","vim_version":"7.3","1":"7.3","script_version":"1.5.5","2":"1.5.5","version_comment":"Added :AuFile prompt option and corresponding OpenAny global mapping\nImproved folding and foldtext in diff filetype plugin\nFixed phase updating in non-python version of mercurial driver","3":"Added :AuFile prompt option and corresponding OpenAny global mapping\nImproved folding and foldtext in diff filetype plugin\nFixed phase updating in non-python version of mercurial driver","package":"aurum-1.5.5.tar.gz","4":"aurum-1.5.5.tar.gz","src_id":"18430","5":"18430","creation_date":"1345365764","6":"1345365764"},{"0":"3828","vim_version":"7.3","1":"7.3","script_version":"1.5.4","2":"1.5.4","version_comment":"Fixed listing of ignored files in git driver","3":"Fixed listing of ignored files in git driver","package":"aurum-1.5.4.tar.gz","4":"aurum-1.5.4.tar.gz","src_id":"18395","5":"18395","creation_date":"1344775049","6":"1344775049"},{"0":"3828","vim_version":"7.3","1":"7.3","script_version":"1.5.1","2":"1.5.1","version_comment":"Added $parents_, $children_ and $tags_ template words, improved mimicing of mercurial log\nAdded support for listing ignored files in repo.functions.status in non-mercurial drivers\nImproved support for older mercurial versions\naurum#status now does not report status for buffers with non-empty &buftype\nSpeeded up some shell calls (requires python)\nFixed mercurial repository updating when user did history editing\nFixed template compiler that was removing some $words and joining lines under certain conditions\nFixed error message when trying to annotate untracked file\nFixed aurum:\/\/annotate buffers highlighting and detection of full descriptions\nMade :AuCommit use :startinsert! so that now cursor will appear at the end of line\nFixed repo.functions.grep in non-python version of mercurial driver\nFixed phases support in non-python version of mercurial driver","3":"Added $parents_, $children_ and $tags_ template words, improved mimicing of mercurial log\nAdded support for listing ignored files in repo.functions.status in non-mercurial drivers\nImproved support for older mercurial versions\naurum#status now does not report status for buffers with non-empty &buftype\nSpeeded up some shell calls (requires python)\nFixed mercurial repository updating when user did history editing\nFixed template compiler that was removing some $words and joining lines under certain conditions\nFixed error message when trying to annotate untracked file\nFixed aurum:\/\/annotate buffers highlighting and detection of full descriptions\nMade :AuCommit use :startinsert! so that now cursor will appear at the end of line\nFixed repo.functions.grep in non-python version of mercurial driver\nFixed phases support in non-python version of mercurial driver","package":"aurum-1.5.1.tar.gz","4":"aurum-1.5.1.tar.gz","src_id":"18392","5":"18392","creation_date":"1344751964","6":"1344751964"},{"0":"3828","vim_version":"7.3","1":"7.3","script_version":"1.5","2":"1.5","version_comment":"Added autoaddlog AuLog option (lazy loading of changesets that are not immediately displayed)\nAdded powerline support (requires some changes to powerline theme and coloscheme)\nAdded aurum#branch()\nAdded support for vim.bindeval (added to vim since 7.3.569)\nAdded progress bar support to :AuLog\nChanged AuHyperlink syntax, added AuHyperlink lines (points to a lines range. Currently only github is supported)\nAdded support for phases (mercurial driver only)\nAdded ansi_esc_echo plugin support (untested) (adds colored output, but uses :echo instead of :echom thus it is not saved in :messages)\nImproved git driver speed\nImproved repository object updating\nFixed some mappings (they did not conform other ones)\nFixed calling aurum commands not inside a repository\nFixed gettiphex function in git driver in case master branch is not present\nRefactoring: moved almost all files to autoload\/","3":"Added autoaddlog AuLog option (lazy loading of changesets that are not immediately displayed)\nAdded powerline support (requires some changes to powerline theme and coloscheme)\nAdded aurum#branch()\nAdded support for vim.bindeval (added to vim since 7.3.569)\nAdded progress bar support to :AuLog\nChanged AuHyperlink syntax, added AuHyperlink lines (points to a lines range. Currently only github is supported)\nAdded support for phases (mercurial driver only)\nAdded ansi_esc_echo plugin support (untested) (adds colored output, but uses :echo instead of :echom thus it is not saved in :messages)\nImproved git driver speed\nImproved repository object updating\nFixed some mappings (they did not conform other ones)\nFixed calling aurum commands not inside a repository\nFixed gettiphex function in git driver in case master branch is not present\nRefactoring: moved almost all files to autoload\/","package":"aurum-1.5.tar.gz","4":"aurum-1.5.tar.gz","src_id":"18213","5":"18213","creation_date":"1341260675","6":"1341260675"},{"0":"3828","vim_version":"7.3","1":"7.3","script_version":"1.4.11","2":"1.4.11","version_comment":"Added :AuLog ignfiles diff (for [vim]diff AuLog mappings) and open (for annotate, open, diff and similar AuLog mappings) options\nAdded location list support to :AuGrep\nAdded aurum python module reloading\nAdded g:aurum_loglimit option\nAdded support for custom mappings to :AuLog procinput\nRenamed g:aurum_closewindow option to g:aurum_closelogwindow and g:aurum_usewin to g:aurum_vimdiffusewin\nMercurial graph drawing function optimizations (reduced time needed to draw cpython log from about 116 seconds to 97 on my machine)\n:AuLog files option is supported in more mappings","3":"Added :AuLog ignfiles diff (for [vim]diff AuLog mappings) and open (for annotate, open, diff and similar AuLog mappings) options\nAdded location list support to :AuGrep\nAdded aurum python module reloading\nAdded g:aurum_loglimit option\nAdded support for custom mappings to :AuLog procinput\nRenamed g:aurum_closewindow option to g:aurum_closelogwindow and g:aurum_usewin to g:aurum_vimdiffusewin\nMercurial graph drawing function optimizations (reduced time needed to draw cpython log from about 116 seconds to 97 on my machine)\n:AuLog files option is supported in more mappings","package":"aurum-1.4.11.tar.gz","4":"aurum-1.4.11.tar.gz","src_id":"17710","5":"17710","creation_date":"1333489319","6":"1333489319"},{"0":"3828","vim_version":"7.3","1":"7.3","script_version":"1.4.10","2":"1.4.10","version_comment":"Added subversion revisions and git sha1s support to mercurial driver for hgsubversion and hg-git respectively (latter works only with python version of driver)\nAdded push and pull (pull+update) global mappings\nFixed repository object updating in non-python driver\nMade it restore some settings values after quiting annotation mode, made :AuAnnotate also set nowrap","3":"Added subversion revisions and git sha1s support to mercurial driver for hgsubversion and hg-git respectively (latter works only with python version of driver)\nAdded push and pull (pull+update) global mappings\nFixed repository object updating in non-python driver\nMade it restore some settings values after quiting annotation mode, made :AuAnnotate also set nowrap","package":"aurum-1.4.10.tar.gz","4":"aurum-1.4.10.tar.gz","src_id":"17618","5":"17618","creation_date":"1332307002","6":"1332307002"},{"0":"3828","vim_version":"7.3","1":"7.3","script_version":"1.4.9","2":"1.4.9","version_comment":"Added :AuOther push\/pull\/incoming\/outgoing command\nFixed :AuFile replace\nFixed repo.functions.grep in newer mercurial versions","3":"Added :AuOther push\/pull\/incoming\/outgoing command\nFixed :AuFile replace\nFixed repo.functions.grep in newer mercurial versions","package":"aurum-1.4.9.tar.gz","4":"aurum-1.4.9.tar.gz","src_id":"17580","5":"17580","creation_date":"1331391207","6":"1331391207"},{"0":"3828","vim_version":"7.3","1":"7.3","script_version":"1.4.8","2":"1.4.8","version_comment":"Made aurum:\/\/ *Cmd events support ++opts\nMade mappings for aurum:\/\/file and aurum:\/\/diff be created in more cases when these buffers are obtained using some mapping\nSupport more complex commands in procinput mode\nAdded svn-like logging style\nFixed :AuHyperlink with some URL types\nFixed :AuVimDiff failure to restore state in some cases","3":"Made aurum:\/\/ *Cmd events support ++opts\nMade mappings for aurum:\/\/file and aurum:\/\/diff be created in more cases when these buffers are obtained using some mapping\nSupport more complex commands in procinput mode\nAdded svn-like logging style\nFixed :AuHyperlink with some URL types\nFixed :AuVimDiff failure to restore state in some cases","package":"aurum-1.4.8.tar.gz","4":"aurum-1.4.8.tar.gz","src_id":"17551","5":"17551","creation_date":"1330661368","6":"1330661368"},{"0":"3828","vim_version":"7.3","1":"7.3","script_version":"1.4.7","2":"1.4.7","version_comment":"Made :AuLog procinput be able to handle non-single-key commads (support is limited though)\nMade subversion driver less fragile\nFixed :AuHyperlink support in git and subversion drivers\nFixed syntax highlighting for revision numbers in :AuLog subversionrepo\nFixed :read aurum:\/\/log","3":"Made :AuLog procinput be able to handle non-single-key commads (support is limited though)\nMade subversion driver less fragile\nFixed :AuHyperlink support in git and subversion drivers\nFixed syntax highlighting for revision numbers in :AuLog subversionrepo\nFixed :read aurum:\/\/log","package":"aurum-1.4.7.tar.gz","4":"aurum-1.4.7.tar.gz","src_id":"17431","5":"17431","creation_date":"1328975836","6":"1328975836"},{"0":"3828","vim_version":"7.3","1":"7.3","script_version":"1.4.6","2":"1.4.6","version_comment":"Improved repo.functions.readfile(): it should now work correctly with binary files\nFixed launching :AuRecord in an old vim instance with already opened files","3":"Improved repo.functions.readfile(): it should now work correctly with binary files\nFixed launching :AuRecord in an old vim instance with already opened files","package":"aurum-1.4.6.tar.gz","4":"aurum-1.4.6.tar.gz","src_id":"17389","5":"17389","creation_date":"1328437048","6":"1328437048"},{"0":"3828","vim_version":"7.3","1":"7.3","script_version":"1.4.5","2":"1.4.5","version_comment":"Made *Update avoid “detached HEAD” state whenever possible when using git driver","3":"Made *Update avoid “detached HEAD” state whenever possible when using git driver","package":"aurum-1.4.5.tar.gz","4":"aurum-1.4.5.tar.gz","src_id":"17388","5":"17388","creation_date":"1328386666","6":"1328386666"},{"0":"3828","vim_version":"7.3","1":"7.3","script_version":"1.4.4","2":"1.4.4","version_comment":"Improved :AuCommit: it now throws an error if there is nothing to commit\nImproved sourceforge subversion checkouts support\nAdded macros that reloads aurum","3":"Improved :AuCommit: it now throws an error if there is nothing to commit\nImproved sourceforge subversion checkouts support\nAdded macros that reloads aurum","package":"aurum-1.4.4.tar.gz","4":"aurum-1.4.4.tar.gz","src_id":"17384","5":"17384","creation_date":"1328360977","6":"1328360977"},{"0":"3828","vim_version":"7.3","1":"7.3","script_version":"1.4.3","2":"1.4.3","version_comment":"Made :AuJunk, :AuTrack and :AuMove normally work with directories","3":"Made :AuJunk, :AuTrack and :AuMove normally work with directories","package":"aurum-1.4.3.tar.gz","4":"aurum-1.4.3.tar.gz","src_id":"17379","5":"17379","creation_date":"1328344491","6":"1328344491"},{"0":"3828","vim_version":"7.3","1":"7.3","script_version":"1.4.2","2":"1.4.2","version_comment":"Added subversion support\nFixed committing forgotten files in the git driver\nAdded repository object caching\nMade different mappings more verbose in case of failure","3":"Added subversion support\nFixed committing forgotten files in the git driver\nAdded repository object caching\nMade different mappings more verbose in case of failure","package":"aurum-1.4.2.tar.gz","4":"aurum-1.4.2.tar.gz","src_id":"17357","5":"17357","creation_date":"1328068165","6":"1328068165"},{"0":"3828","vim_version":"7.3","1":"7.3","script_version":"1.4.1","2":"1.4.1","version_comment":"Renamed :AuStatus “rev1” and “rev2” options to “rev” and “wdrev” respectively\nAdded :AuStatus “changes” option\nAdded more mappings that invoke full vimdiff\nMade gM be now default rhs for AuLog date mapping (old “gD” is taken by one of full vimdiff mappings)\nMade git grapher also draw skipped changesets, though without messages","3":"Renamed :AuStatus “rev1” and “rev2” options to “rev” and “wdrev” respectively\nAdded :AuStatus “changes” option\nAdded more mappings that invoke full vimdiff\nMade gM be now default rhs for AuLog date mapping (old “gD” is taken by one of full vimdiff mappings)\nMade git grapher also draw skipped changesets, though without messages","package":"aurum-1.4.1.tar.gz","4":"aurum-1.4.1.tar.gz","src_id":"17297","5":"17297","creation_date":"1327267071","6":"1327267071"},{"0":"3828","vim_version":"7.3","1":"7.3","script_version":"1.4","2":"1.4","version_comment":"Added incremental update support to aurum:\/\/log so that you can view and use log buffers while log is being generated\nMade :AuLog limit option apply after any other selector\nAdded g:aurum_hg_useshell option that makes you able to launch pre\/post-{command} hooks while using Mercurial Python API\n\nFixed :write aurum:\/\/commit\nFixed AuLog Prev\/Next mappings: they did not work if some revisions were skipped\nFixed :AuCommit called in a diff buffer with full diff: it did not want to commit anything","3":"Added incremental update support to aurum:\/\/log so that you can view and use log buffers while log is being generated\nMade :AuLog limit option apply after any other selector\nAdded g:aurum_hg_useshell option that makes you able to launch pre\/post-{command} hooks while using Mercurial Python API\n\nFixed :write aurum:\/\/commit\nFixed AuLog Prev\/Next mappings: they did not work if some revisions were skipped\nFixed :AuCommit called in a diff buffer with full diff: it did not want to commit anything","package":"aurum-1.4.tar.gz","4":"aurum-1.4.tar.gz","src_id":"17209","5":"17209","creation_date":"1326579787","6":"1326579787"},{"0":"3828","vim_version":"7.3","1":"7.3","script_version":"1.3","2":"1.3","version_comment":"Added git driver\nAdded g:aurum_bufleaveremembermsg option\nAdded support for sourcing aurum:\/\/file URLs\nAdded git and gitoneline log styles\nAdded graphing code ported from git\nMade :AuJunk use untracked files if “ignore” option was specified\n\nVarious fixes:\n — Fixed :AuMove repo\/file repo\/file2\n — Fixed :AuCommit repo path\/to\/repo all\n — Fixed grepping with mercurial+python driver: it now supports all possible filenames","3":"Added git driver\nAdded g:aurum_bufleaveremembermsg option\nAdded support for sourcing aurum:\/\/file URLs\nAdded git and gitoneline log styles\nAdded graphing code ported from git\nMade :AuJunk use untracked files if “ignore” option was specified\n\nVarious fixes:\n — Fixed :AuMove repo\/file repo\/file2\n — Fixed :AuCommit repo path\/to\/repo all\n — Fixed grepping with mercurial+python driver: it now supports all possible filenames","package":"aurum-1.3.tar.gz","4":"aurum-1.3.tar.gz","src_id":"17148","5":"17148","creation_date":"1325602903","6":"1325602903"},{"0":"3828","vim_version":"7.3","1":"7.3","script_version":"1.2.2","2":"1.2.2","version_comment":"Added :AuName and :AuBranch commands","3":"Added :AuName and :AuBranch commands","package":"aurum-1.2.2.tar.gz","4":"aurum-1.2.2.tar.gz","src_id":"17047","5":"17047","creation_date":"1323459878","6":"1323459878"},{"0":"3828","vim_version":"7.3","1":"7.3","script_version":"1.1","2":"1.1","version_comment":"Made it possible to write your own SCM drivers\nSome additions and fixes to :AuHyperlink remote repositories support","3":"Made it possible to write your own SCM drivers\nSome additions and fixes to :AuHyperlink remote repositories support","package":"aurum-1.1.tar.gz","4":"aurum-1.1.tar.gz","src_id":"17034","5":"17034","creation_date":"1323319623","6":"1323319623"},{"0":"3828","vim_version":"7.3","1":"7.3","script_version":"1.0","2":"1.0","version_comment":"Initial release","3":"Initial release","package":"aurum-1.0.tar.gz","4":"aurum-1.0.tar.gz","src_id":"16995","5":"16995","creation_date":"1322597553","6":"1322597553"}]},"3827":{"script_id":"3827","0":"3827","script_name":"modeleasy-vim-plugin","1":"modeleasy-vim-plugin","script_type":"ftplugin","2":"ftplugin","summary":"This is a syntax highlighting for the econometric package modeleasy ","3":"This is a syntax highlighting for the econometric package modeleasy ","description":"This plugin provides syntax highlighting for Modeleasy improving Vim's support for editing Modeleasy + code in both normal and visual mode.\r\nIt provides also some utilities such as to comment or indent lines in source code file.","4":"This plugin provides syntax highlighting for Modeleasy improving Vim's support for editing Modeleasy + code in both normal and visual mode.\r\nIt provides also some utilities such as to comment or indent lines in source code file.","install_details":"To install the plugin open the vimball archive and do:\r\n\r\n:so %\r\n:q","5":"To install the plugin open the vimball archive and do:\r\n\r\n:so %\r\n:q","first_name":"Massimiliano","6":"Massimiliano","last_name":"Tripoli","7":"Tripoli","releases":[{"0":"3827","vim_version":"7.0","1":"7.0","script_version":"1.2","2":"1.2","version_comment":"It provides indentation of syntax and fix some bugs of previous version.","3":"It provides indentation of syntax and fix some bugs of previous version.","package":"modeleasy-vim-plugin-1.2.vba","4":"modeleasy-vim-plugin-1.2.vba","src_id":"18998","5":"18998","creation_date":"1353359760","6":"1353359760"},{"0":"3827","vim_version":"7.0","1":"7.0","script_version":"1.1","2":"1.1","version_comment":"A key word \"end\" has been added to set the end of code block to be highlighted on and a new key map to open help document of a specific modeleasy function from vim.\r\n","3":"A key word \"end\" has been added to set the end of code block to be highlighted on and a new key map to open help document of a specific modeleasy function from vim.\r\n","package":"modeleasy-vim-plugin-1.1.vba","4":"modeleasy-vim-plugin-1.1.vba","src_id":"17897","5":"17897","creation_date":"1336414856","6":"1336414856"},{"0":"3827","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"modeleasy-vim-plugin-26-11-11.vba","4":"modeleasy-vim-plugin-26-11-11.vba","src_id":"16992","5":"16992","creation_date":"1322554070","6":"1322554070"}]},"3826":{"script_id":"3826","0":"3826","script_name":"simple_bookmarks.vim","1":"simple_bookmarks.vim","script_type":"utility","2":"utility","summary":"Named bookmarks, storing both filename and cursor position","3":"Named bookmarks, storing both filename and cursor position","description":"Github project is at https:\/\/github.com\/AndrewRadev\/simple_bookmarks.vim\r\n\r\nThe plugin provides several commands to manage named bookmarks. This is similar to what you'd do with persistent marks, but brings the benefit of longer, more rememberable names.\r\n\r\nHere's an example:\r\n\r\n    :edit ~\/.vimrc\r\n    :3\r\n    :Bookmark here\r\n\r\nThis will store a bookmark called \"here\" in the file \"~\/.vim_bookmarks\" (changeable through a setting). To jump to the mark, use :GotoBookmark\r\n\r\n    :GotoBookmark here\r\n\r\nThis will open the ~\/.vimrc file and jump to the third line. The column is saved as well.\r\n\r\nTo delete the bookmark, use:\r\n\r\n    :DelBookmark here\r\n\r\nBoth :GotoBookmark and :DelBookmark are tab-completed with all known bookmarks.\r\n\r\nThe command :CopenBookmarks will load all marks in the quickfix window for easier navigating.\r\n\r\nNote that bookmarks should be synchronized between vim instances. Anytime you add a mark in one vim instance, it should be available in all others. In practice, this is achieved by simply reading and writing the whole file on each update. I have yet to experiment to find out if there are any performance issues or race conditions. If you find any issues, please open a bug report on github: https:\/\/github.com\/AndrewRadev\/simple_bookmarks.vim\/issues\r\n","4":"Github project is at https:\/\/github.com\/AndrewRadev\/simple_bookmarks.vim\r\n\r\nThe plugin provides several commands to manage named bookmarks. This is similar to what you'd do with persistent marks, but brings the benefit of longer, more rememberable names.\r\n\r\nHere's an example:\r\n\r\n    :edit ~\/.vimrc\r\n    :3\r\n    :Bookmark here\r\n\r\nThis will store a bookmark called \"here\" in the file \"~\/.vim_bookmarks\" (changeable through a setting). To jump to the mark, use :GotoBookmark\r\n\r\n    :GotoBookmark here\r\n\r\nThis will open the ~\/.vimrc file and jump to the third line. The column is saved as well.\r\n\r\nTo delete the bookmark, use:\r\n\r\n    :DelBookmark here\r\n\r\nBoth :GotoBookmark and :DelBookmark are tab-completed with all known bookmarks.\r\n\r\nThe command :CopenBookmarks will load all marks in the quickfix window for easier navigating.\r\n\r\nNote that bookmarks should be synchronized between vim instances. Anytime you add a mark in one vim instance, it should be available in all others. In practice, this is achieved by simply reading and writing the whole file on each update. I have yet to experiment to find out if there are any performance issues or race conditions. If you find any issues, please open a bug report on github: https:\/\/github.com\/AndrewRadev\/simple_bookmarks.vim\/issues\r\n","install_details":"There are several ways to install the plugin. The recommended one is by using Tim Pope's pathogen (http:\/\/www.vim.org\/scripts\/script.php?script_id=2332). In that case, you can clone the plugin's git repository like so:\r\n\r\n    git clone git:\/\/github.com\/AndrewRadev\/simple_bookmarks.vim.git ~\/.vim\/bundle\/simple_bookmarks\r\n\r\nIf your vim configuration is under git version control, you could also set up the repository as a submodule, which would allow you to update more easily. The command is (provided you're in ~\/.vim):\r\n\r\n    git submodule add git:\/\/github.com\/AndrewRadev\/simple_bookmarks.vim.git bundle\/simple_bookmarks\r\n\r\nAnother way is to simply copy all the essential directories inside the ~\/.vim directory: plugin, autoload, doc.\r\n","5":"There are several ways to install the plugin. The recommended one is by using Tim Pope's pathogen (http:\/\/www.vim.org\/scripts\/script.php?script_id=2332). In that case, you can clone the plugin's git repository like so:\r\n\r\n    git clone git:\/\/github.com\/AndrewRadev\/simple_bookmarks.vim.git ~\/.vim\/bundle\/simple_bookmarks\r\n\r\nIf your vim configuration is under git version control, you could also set up the repository as a submodule, which would allow you to update more easily. The command is (provided you're in ~\/.vim):\r\n\r\n    git submodule add git:\/\/github.com\/AndrewRadev\/simple_bookmarks.vim.git bundle\/simple_bookmarks\r\n\r\nAnother way is to simply copy all the essential directories inside the ~\/.vim directory: plugin, autoload, doc.\r\n","first_name":"Andrew","6":"Andrew","last_name":"Radev","7":"Radev","releases":[{"0":"3826","vim_version":"7.0","1":"7.0","script_version":"0.1.0","2":"0.1.0","version_comment":"- Delete and undo bookmarks from the quickfix list\r\n- Improvements on highlighting and signs","3":"- Delete and undo bookmarks from the quickfix list\r\n- Improvements on highlighting and signs","package":"simple_bookmarks.zip","4":"simple_bookmarks.zip","src_id":"21384","5":"21384","creation_date":"1390763031","6":"1390763031"},{"0":"3826","vim_version":"7.0","1":"7.0","script_version":"0.0.2","2":"0.0.2","version_comment":"- Signs and\/or highlighting for bookmarked lines\r\n- Optional extended quickfix view\r\n- Auto-closing of quickfix window\r\n- Optionally open bookmarks in new tabs","3":"- Signs and\/or highlighting for bookmarked lines\r\n- Optional extended quickfix view\r\n- Auto-closing of quickfix window\r\n- Optionally open bookmarks in new tabs","package":"simple_bookmarks.zip","4":"simple_bookmarks.zip","src_id":"19051","5":"19051","creation_date":"1354046094","6":"1354046094"},{"0":"3826","vim_version":"7.0","1":"7.0","script_version":"0.0.1","2":"0.0.1","version_comment":"Initial upload","3":"Initial upload","package":"simple_bookmarks.zip","4":"simple_bookmarks.zip","src_id":"16991","5":"16991","creation_date":"1322514913","6":"1322514913"}]},"3825":{"script_id":"3825","0":"3825","script_name":"Colour theme (neon-pk)","1":"Colour theme (neon-pk)","script_type":"color scheme","2":"color scheme","summary":"A variation on the neon colour theme that uses the DejaVu Sans Mono font","3":"A variation on the neon colour theme that uses the DejaVu Sans Mono font","description":"A beautiful variation on the neon colour theme. For picture, see http:\/\/damp-squid.blogspot.com\/2011\/11\/vim-colour-theme-neon-pk.html\r\n\r\nAs you can see from the above link, this looks great with the DejaVu Sans Mono font :-) The font is free and can be downloaded from http:\/\/dejavu-fonts.org\/wiki\/Download. This font is similar to the Apple Menlo font. So you don't need the DejaVu font if you're using Mac OS X. For more about these fonts, see http:\/\/typophile.com\/node\/58625.\r\n\r\nOne of the improvements on the neon theme is that when you start searching, the text found is highlighted clearly in orange. Then, when you press Enter, all matched text is visible in yellow. This assumes that you have the following settings in your vimrc file:\r\n\r\n  set incsearch\r\n  set hlsearch\r\n\r\n","4":"A beautiful variation on the neon colour theme. For picture, see http:\/\/damp-squid.blogspot.com\/2011\/11\/vim-colour-theme-neon-pk.html\r\n\r\nAs you can see from the above link, this looks great with the DejaVu Sans Mono font :-) The font is free and can be downloaded from http:\/\/dejavu-fonts.org\/wiki\/Download. This font is similar to the Apple Menlo font. So you don't need the DejaVu font if you're using Mac OS X. For more about these fonts, see http:\/\/typophile.com\/node\/58625.\r\n\r\nOne of the improvements on the neon theme is that when you start searching, the text found is highlighted clearly in orange. Then, when you press Enter, all matched text is visible in yellow. This assumes that you have the following settings in your vimrc file:\r\n\r\n  set incsearch\r\n  set hlsearch\r\n\r\n","install_details":"Put in the Vim \"colors\" directory and add something like this to your vimrc file:\r\n\r\n  if has(\"gui_running\")\r\n    set gfn=DejaVu_Sans_Mono:h9:cANSI\r\n    colorscheme neon-PK\r\n  else\r\n  \"    colorscheme somethingElse\r\n  endif\r\n\r\nThe above assumes you've installed the DejaVu Sans Mono font. You can, of course, use any font.","5":"Put in the Vim \"colors\" directory and add something like this to your vimrc file:\r\n\r\n  if has(\"gui_running\")\r\n    set gfn=DejaVu_Sans_Mono:h9:cANSI\r\n    colorscheme neon-PK\r\n  else\r\n  \"    colorscheme somethingElse\r\n  endif\r\n\r\nThe above assumes you've installed the DejaVu Sans Mono font. You can, of course, use any font.","first_name":"Praful","6":"Praful","last_name":"Kapadia","7":"Kapadia","releases":[{"0":"3825","vim_version":"7.0","1":"7.0","script_version":"2.0","2":"2.0","version_comment":"Same as previous version but has version info in file.","3":"Same as previous version but has version info in file.","package":"neon-PK.vim","4":"neon-PK.vim","src_id":"16981","5":"16981","creation_date":"1322332180","6":"1322332180"},{"0":"3825","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"neon-PK.vim","4":"neon-PK.vim","src_id":"16979","5":"16979","creation_date":"1322319735","6":"1322319735"}]},"3824":{"script_id":"3824","0":"3824","script_name":"nu42dark color scheme","1":"nu42dark color scheme","script_type":"color scheme","2":"color scheme","summary":"Started as a variation on CandyCode and took on a life of its own","3":"Started as a variation on CandyCode and took on a life of its own","description":"Dark and out of the way, one hopes. Screenshot at http:\/\/www.unur.com\/sinan\/nu42dark-vim-color-scheme.html","4":"Dark and out of the way, one hopes. Screenshot at http:\/\/www.unur.com\/sinan\/nu42dark-vim-color-scheme.html","install_details":"Put it in your .vim\/colors or vimfiles\\colors directory, depending on platform and your preferences.","5":"Put it in your .vim\/colors or vimfiles\\colors directory, depending on platform and your preferences.","first_name":"A. Sinan","6":"A. Sinan","last_name":"Unur","7":"Unur","releases":[{"0":"3824","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"nu42dark.vim","4":"nu42dark.vim","src_id":"16976","5":"16976","creation_date":"1322285817","6":"1322285817"}]},"3823":{"script_id":"3823","0":"3823","script_name":"csslint.vim","1":"csslint.vim","script_type":"utility","2":"utility","summary":"Vim plugin of csslint","3":"Vim plugin of csslint","description":"Credit [jslint.vim](https:\/\/github.com\/hallettj\/jslint.vim) and [csslint](http:\/\/csslint.net\/)\r\n\r\nI am not sure it could work well in Windows.\r\n\r\nI will update this plugin in [GitHub](https:\/\/github.com\/bolasblack\/csslint), but not in vim.org.\r\n\r\nneed nodejs:\r\n\r\n    sudo pacman -S nodejs (archlinux)\r\n    sudo apt-get install nodejs (ubuntu, debian)\r\n\r\nneed npm:\r\n\r\n    yaourt nodejs-npm (archlinux)\r\n    curl http:\/\/npmjs.org\/install.sh | sh (other)\r\n\r\nneed csslint:\r\n\r\n    sudo npm install -g csslint\r\n\r\ncsslint.vim will be actived if file is css or less default, you can config it in .vimrc:\r\n\r\n    let g:CSSLint_FileTypeList = ['css', 'less', 'sess']\r\n\r\nyou can deactivate it:\r\n\r\n    let g:CSSLint_HighlightErrorLine = 0\r\n","4":"Credit [jslint.vim](https:\/\/github.com\/hallettj\/jslint.vim) and [csslint](http:\/\/csslint.net\/)\r\n\r\nI am not sure it could work well in Windows.\r\n\r\nI will update this plugin in [GitHub](https:\/\/github.com\/bolasblack\/csslint), but not in vim.org.\r\n\r\nneed nodejs:\r\n\r\n    sudo pacman -S nodejs (archlinux)\r\n    sudo apt-get install nodejs (ubuntu, debian)\r\n\r\nneed npm:\r\n\r\n    yaourt nodejs-npm (archlinux)\r\n    curl http:\/\/npmjs.org\/install.sh | sh (other)\r\n\r\nneed csslint:\r\n\r\n    sudo npm install -g csslint\r\n\r\ncsslint.vim will be actived if file is css or less default, you can config it in .vimrc:\r\n\r\n    let g:CSSLint_FileTypeList = ['css', 'less', 'sess']\r\n\r\nyou can deactivate it:\r\n\r\n    let g:CSSLint_HighlightErrorLine = 0\r\n","install_details":"Copy file into $VIM\/plugin\/, need Python","5":"Copy file into $VIM\/plugin\/, need Python","first_name":"wang","6":"wang","last_name":"yicuan","7":"yicuan","releases":[{"0":"3823","vim_version":"7.2","1":"7.2","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"csslint.vim","4":"csslint.vim","src_id":"16975","5":"16975","creation_date":"1322271064","6":"1322271064"}]},"3821":{"script_id":"3821","0":"3821","script_name":"vim-ocaml-conceal","1":"vim-ocaml-conceal","script_type":"syntax","2":"syntax","summary":"ocaml.vim - vim conceal enhanvement for ocaml","3":"ocaml.vim - vim conceal enhanvement for ocaml","description":"Vim 7.3 comes with a new feature called \"conceal.\"\r\nOne application of it is dynamically displaying unicode glyph of a given combination of patterns or keywords.\r\nFor instance, we can display unicode right arrow  →  on the screen with ascii right arrow in the buffer.\r\nThere has been vim coneal syntax files for differenc programming langauges, like\r\n\r\n* [haskell](https:\/\/github.com\/vim-scripts\/Haskell-Conceal)\r\n* [perl](https:\/\/github.com\/c9s\/perl-conceal.vim)\r\n* [ruby](http:\/\/ithaca.arpinum.org\/2010\/11\/06\/vim-conceal-for-ruby.html)\r\n* [latex](http:\/\/b4winckler.wordpress.com\/2010\/08\/07\/using-the-conceal-vim-feature-with-latex\/)]\r\n\r\n\r\nGithub location of this plugin: https:\/\/github.com\/MnO2\/vim-ocaml-conceal","4":"Vim 7.3 comes with a new feature called \"conceal.\"\r\nOne application of it is dynamically displaying unicode glyph of a given combination of patterns or keywords.\r\nFor instance, we can display unicode right arrow  →  on the screen with ascii right arrow in the buffer.\r\nThere has been vim coneal syntax files for differenc programming langauges, like\r\n\r\n* [haskell](https:\/\/github.com\/vim-scripts\/Haskell-Conceal)\r\n* [perl](https:\/\/github.com\/c9s\/perl-conceal.vim)\r\n* [ruby](http:\/\/ithaca.arpinum.org\/2010\/11\/06\/vim-conceal-for-ruby.html)\r\n* [latex](http:\/\/b4winckler.wordpress.com\/2010\/08\/07\/using-the-conceal-vim-feature-with-latex\/)]\r\n\r\n\r\nGithub location of this plugin: https:\/\/github.com\/MnO2\/vim-ocaml-conceal","install_details":"Drop the ocaml.vim to ~\/.vim\/after\/syntax (Linux\/Mac OS X\/BSD) or ~\/vimfiles\/after\/syntax folder (Windows)","5":"Drop the ocaml.vim to ~\/.vim\/after\/syntax (Linux\/Mac OS X\/BSD) or ~\/vimfiles\/after\/syntax folder (Windows)","first_name":"Paul","6":"Paul","last_name":"Meng","7":"Meng","releases":[{"0":"3821","vim_version":"7.3","1":"7.3","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"vim-ocaml-conceal-1.0.zip","4":"vim-ocaml-conceal-1.0.zip","src_id":"16955","5":"16955","creation_date":"1322140855","6":"1322140855"}]},"3820":{"script_id":"3820","0":"3820","script_name":"Dart","1":"Dart","script_type":"syntax","2":"syntax","summary":"Syntax file for Dart Language","3":"Syntax file for Dart Language","description":"Dart Lang Syntax for VIM\r\n","4":"Dart Lang Syntax for VIM\r\n","install_details":"I recommend installing pathogen.vim, and then simply copy and paste:\r\n\r\n    cd ~\/.vim\/bundle\r\n    git clone git:\/\/github.com\/bartlomiejdanek\/vim-dart.git","5":"I recommend installing pathogen.vim, and then simply copy and paste:\r\n\r\n    cd ~\/.vim\/bundle\r\n    git clone git:\/\/github.com\/bartlomiejdanek\/vim-dart.git","first_name":"Bart\u0142omiej","6":"Bartłomiej","last_name":"Danek","7":"Danek","releases":[{"0":"3820","vim_version":"6.0","1":"6.0","script_version":"0.3","2":"0.3","version_comment":"fix syntax match, dart exceptions, indentation and many other things","3":"fix syntax match, dart exceptions, indentation and many other things","package":"vim-dart.tar.gz","4":"vim-dart.tar.gz","src_id":"19178","5":"19178","creation_date":"1355408715","6":"1355408715"},{"0":"3820","vim_version":"7.0","1":"7.0","script_version":"0.2","2":"0.2","version_comment":"added ftdetect","3":"added ftdetect","package":"vim-dart.tar.gz","4":"vim-dart.tar.gz","src_id":"16950","5":"16950","creation_date":"1322074175","6":"1322074175"},{"0":"3820","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"vim-dart.tar.gz","4":"vim-dart.tar.gz","src_id":"16942","5":"16942","creation_date":"1321980186","6":"1321980186"}]},"3819":{"script_id":"3819","0":"3819","script_name":"Lisper.vim","1":"Lisper.vim","script_type":"utility","2":"utility","summary":"Yet Another Lisp Engine Written In Pure VimScript","3":"Yet Another Lisp Engine Written In Pure VimScript","description":"This vim plugin provide lisp environments for vimmers.\r\n\r\nSource Repository.\r\nref: http:\/\/github.com\/mattn\/lisper-vim\r\n\r\nLisperEvalBuffer: evaluate buffer as lisp.\r\nLisperRepl: start repl in vim command-line.\r\n\r\nYou can call lisper#eval() to evaluate expression.\r\n\r\n  :echo lisper#eval('(+ 1 2 3 4 5)')\r\n  15\r\n\r\nOr, make instance permanently.\r\n\r\n  :let engine = lisper#engine()\r\n  :echo engine.eval(\"(+ 1 2 3 4 5)\")\r\n  15\r\n  :echo engine.eval(\"(+ 1 (length (quote abc))\")\r\n  4\r\n\r\nThe instance of lisp machine have global environment for the variable.\r\n","4":"This vim plugin provide lisp environments for vimmers.\r\n\r\nSource Repository.\r\nref: http:\/\/github.com\/mattn\/lisper-vim\r\n\r\nLisperEvalBuffer: evaluate buffer as lisp.\r\nLisperRepl: start repl in vim command-line.\r\n\r\nYou can call lisper#eval() to evaluate expression.\r\n\r\n  :echo lisper#eval('(+ 1 2 3 4 5)')\r\n  15\r\n\r\nOr, make instance permanently.\r\n\r\n  :let engine = lisper#engine()\r\n  :echo engine.eval(\"(+ 1 2 3 4 5)\")\r\n  15\r\n  :echo engine.eval(\"(+ 1 (length (quote abc))\")\r\n  4\r\n\r\nThe instance of lisp machine have global environment for the variable.\r\n","install_details":"# cd ~\/.vim\r\n# unzip lisper-vim.zip\r\n\r\nor if you install pathogen.vim:\r\n\r\n# cd ~\/.vim\/bundle # or make directory\r\n# unzip \/path\/to\/lisper-vim.zip\r\n\r\nif you get sources from repository:\r\n\r\n# cd ~\/.vim\/bundle # or make directory\r\n# git clone http:\/\/github.com\/mattn\/lisper-vim.git\r\n","5":"# cd ~\/.vim\r\n# unzip lisper-vim.zip\r\n\r\nor if you install pathogen.vim:\r\n\r\n# cd ~\/.vim\/bundle # or make directory\r\n# unzip \/path\/to\/lisper-vim.zip\r\n\r\nif you get sources from repository:\r\n\r\n# cd ~\/.vim\/bundle # or make directory\r\n# git clone http:\/\/github.com\/mattn\/lisper-vim.git\r\n","first_name":"Yasuhiro","6":"Yasuhiro","last_name":"Matsumoto","7":"Matsumoto","releases":[{"0":"3819","vim_version":"7.0","1":"7.0","script_version":"0.03","2":"0.03","version_comment":"This is an upgrade for Lisper.vim:\n[add] fix examples.\n","3":"This is an upgrade for Lisper.vim:\n[add] fix examples.\n","package":"lisper-vim.zip","4":"lisper-vim.zip","src_id":"17857","5":"17857","creation_date":"1335931195","6":"1335931195"},{"0":"3819","vim_version":"7.0","1":"7.0","script_version":"0.02","2":"0.02","version_comment":"This is an upgrade for Lisper.vim:\n[add] added examples.\n","3":"This is an upgrade for Lisper.vim:\n[add] added examples.\n","package":"lisper-vim.zip","4":"lisper-vim.zip","src_id":"16937","5":"16937","creation_date":"1321957469","6":"1321957469"},{"0":"3819","vim_version":"7.0","1":"7.0","script_version":"0.01","2":"0.01","version_comment":"Initial upload","3":"Initial upload","package":"lisper-vim.zip","4":"lisper-vim.zip","src_id":"16936","5":"16936","creation_date":"1321957043","6":"1321957043"}]},"3818":{"script_id":"3818","0":"3818","script_name":"MatchTag","1":"MatchTag","script_type":"ftplugin","2":"ftplugin","summary":"MatchParen for HTML tags.","3":"MatchParen for HTML tags.","description":"This plugin highlights the matching HTML tag when the cursor is positioned on a tag. It works in much the same way as the MatchParen plugin.\r\n\r\nIt was inspired by this question http:\/\/stackoverflow.com\/q\/8168320\/20388.","4":"This plugin highlights the matching HTML tag when the cursor is positioned on a tag. It works in much the same way as the MatchParen plugin.\r\n\r\nIt was inspired by this question http:\/\/stackoverflow.com\/q\/8168320\/20388.","install_details":"Drop the html.vim file in ~\/.vim\/ftplugin.","5":"Drop the html.vim file in ~\/.vim\/ftplugin.","first_name":"Greg","6":"Greg","last_name":"Sexton","7":"Sexton","releases":[{"0":"3818","vim_version":"7.0","1":"7.0","script_version":"1.3","2":"1.3","version_comment":"Latest archive of github repo.","3":"Latest archive of github repo.","package":"matchtag.tar.bz2","4":"matchtag.tar.bz2","src_id":"19533","5":"19533","creation_date":"1361108742","6":"1361108742"},{"0":"3818","vim_version":"7.0","1":"7.0","script_version":"1.2","2":"1.2","version_comment":"Match highlighting improvements.","3":"Match highlighting improvements.","package":"html.vim","4":"html.vim","src_id":"16921","5":"16921","creation_date":"1321907561","6":"1321907561"},{"0":"3818","vim_version":"7.0","1":"7.0","script_version":"1.1","2":"1.1","version_comment":"Fixed augroup bug.","3":"Fixed augroup bug.","package":"html.vim","4":"html.vim","src_id":"16920","5":"16920","creation_date":"1321903558","6":"1321903558"},{"0":"3818","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"html.vim","4":"html.vim","src_id":"16919","5":"16919","creation_date":"1321903232","6":"1321903232"}]},"3817":{"script_id":"3817","0":"3817","script_name":"vim-kickstart","1":"vim-kickstart","script_type":"syntax","2":"syntax","summary":"Syntax for Linux Kickstart files","3":"Syntax for Linux Kickstart files","description":"This is a fork of vimscript #736 whose author is no longer maintaining it. My fork lives on GitHub here:\r\n\r\nhttps:\/\/github.com\/tangledhelix\/vim-kickstart\r\n\r\nThis version adds comment\/commenstring and format options, on top of the existing syntax file supplied by David Ne\u00c3\u00a7as' original kickstart.vim script.","4":"This is a fork of vimscript #736 whose author is no longer maintaining it. My fork lives on GitHub here:\r\n\r\nhttps:\/\/github.com\/tangledhelix\/vim-kickstart\r\n\r\nThis version adds comment\/commenstring and format options, on top of the existing syntax file supplied by David Ne\u00c3\u00a7as' original kickstart.vim script.","install_details":"If using Pathogen, just clone the git directory or unzip the zip file in your bundle area.\r\n\r\nIf not using Pathogen, unzip the zip file, then:\r\n\r\nmkdir -p ~\/.vim\/syntax ~\/.vim\/ftdetect ~\/.vim\/ftplugin\r\ncp vim-kickstart\/syntax\/kickstart.vim ~\/.vim\/syntax\r\ncp vim-kickstart\/ftplugin\/kickstart.vim ~\/.vim\/ftplugin\r\ncp vim-kickstart\/ftdetect\/kickstart.vim ~\/.vim\/ftdetect\r\n","5":"If using Pathogen, just clone the git directory or unzip the zip file in your bundle area.\r\n\r\nIf not using Pathogen, unzip the zip file, then:\r\n\r\nmkdir -p ~\/.vim\/syntax ~\/.vim\/ftdetect ~\/.vim\/ftplugin\r\ncp vim-kickstart\/syntax\/kickstart.vim ~\/.vim\/syntax\r\ncp vim-kickstart\/ftplugin\/kickstart.vim ~\/.vim\/ftplugin\r\ncp vim-kickstart\/ftdetect\/kickstart.vim ~\/.vim\/ftdetect\r\n","first_name":"Dan","6":"Dan","last_name":"Lowe","7":"Lowe","releases":[{"0":"3817","vim_version":"5.7","1":"5.7","script_version":"20111121","2":"20111121","version_comment":"Initial upload","3":"Initial upload","package":"vim-kickstart.zip","4":"vim-kickstart.zip","src_id":"16918","5":"16918","creation_date":"1321894182","6":"1321894182"}]},"3815":{"script_id":"3815","0":"3815","script_name":"mirodark","1":"mirodark","script_type":"color scheme","2":"color scheme","summary":"A Vim color scheme based on Jason W Ryan's environment configuration.","3":"A Vim color scheme based on Jason W Ryan's environment configuration.","description":"Get the latest version here:\r\n    https:\/\/github.com\/djjcast\/mirodark\r\n\r\nRead the detailed description here:\r\n    https:\/\/github.com\/djjcast\/mirodark\/blob\/master\/README\r\n\r\nScreenshots:\r\n    https:\/\/github.com\/djjcast\/mirodark\/raw\/master\/screenshots\/mirodark_default.png\r\n    https:\/\/github.com\/djjcast\/mirodark\/raw\/master\/screenshots\/mirodark_higher_contrast_mode.png","4":"Get the latest version here:\r\n    https:\/\/github.com\/djjcast\/mirodark\r\n\r\nRead the detailed description here:\r\n    https:\/\/github.com\/djjcast\/mirodark\/blob\/master\/README\r\n\r\nScreenshots:\r\n    https:\/\/github.com\/djjcast\/mirodark\/raw\/master\/screenshots\/mirodark_default.png\r\n    https:\/\/github.com\/djjcast\/mirodark\/raw\/master\/screenshots\/mirodark_higher_contrast_mode.png","install_details":"Read the install details here:\r\n    https:\/\/github.com\/djjcast\/mirodark\/blob\/master\/README","5":"Read the install details here:\r\n    https:\/\/github.com\/djjcast\/mirodark\/blob\/master\/README","first_name":"Jerome","6":"Jerome","last_name":"Castaneda","7":"Castaneda","releases":[{"0":"3815","vim_version":"7.0","1":"7.0","script_version":"0.3","2":"0.3","version_comment":"Initial upload","3":"Initial upload","package":"mirodark.vim","4":"mirodark.vim","src_id":"16911","5":"16911","creation_date":"1321824631","6":"1321824631"}]},"3814":{"script_id":"3814","0":"3814","script_name":"log.vim","1":"log.vim","script_type":"syntax","2":"syntax","summary":"Syntax file for make output","3":"Syntax file for make output","description":"Syntax file for make output. This file will be associated with .log files.\r\nPlace the following line in your ~\/.vimrc in order to set the syntax automatically\r\n\r\nautocmd BufRead,BufNewFile *.log set syntax=log                                                                 \r\n","4":"Syntax file for make output. This file will be associated with .log files.\r\nPlace the following line in your ~\/.vimrc in order to set the syntax automatically\r\n\r\nautocmd BufRead,BufNewFile *.log set syntax=log                                                                 \r\n","install_details":"Copy the file (log.vim) to yout $VIM\/syntax\/","5":"Copy the file (log.vim) to yout $VIM\/syntax\/","first_name":"Direct","6":"Direct","last_name":"Sunlight","7":"Sunlight","releases":[{"0":"3814","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"log.vim","4":"log.vim","src_id":"16908","5":"16908","creation_date":"1321740669","6":"1321740669"}]},"3812":{"script_id":"3812","0":"3812","script_name":"tex_AutoKeymap","1":"tex_AutoKeymap","script_type":"ftplugin","2":"ftplugin","summary":"Vim Tex \/ LaTeX ftplugin to automatically change keymap (language)","3":"Vim Tex \/ LaTeX ftplugin to automatically change keymap (language)","description":"This script will be useful for users, who edit tex files with text not in\r\nEnglish language. With this script you will no longer need to change\r\nsystem language when editing usual text and formulas. Internal vim\r\nlanguage (see keymap) will change automatically based on cursor position.\r\n\r\nFor example, if you set in your .vimrc or tex.vim file \r\n\r\n   let g:tex_Keymap = 'ru'\r\n\r\nthen in text zone your keymap will be 'ru', and if you start edit a\r\nformula keymap will be changed to default automatically.\r\n\r\nIt is based on default tex sintax information and some regular expressions.\r\n\r\nTo disable script you can commentify the string\r\n\r\n   let g:tex_Keymap = 'ru'\r\n\r\nUse <C-J> to manually change keymap\r\n\r\nSuggestions and improvements are appreciated.\r\n","4":"This script will be useful for users, who edit tex files with text not in\r\nEnglish language. With this script you will no longer need to change\r\nsystem language when editing usual text and formulas. Internal vim\r\nlanguage (see keymap) will change automatically based on cursor position.\r\n\r\nFor example, if you set in your .vimrc or tex.vim file \r\n\r\n   let g:tex_Keymap = 'ru'\r\n\r\nthen in text zone your keymap will be 'ru', and if you start edit a\r\nformula keymap will be changed to default automatically.\r\n\r\nIt is based on default tex sintax information and some regular expressions.\r\n\r\nTo disable script you can commentify the string\r\n\r\n   let g:tex_Keymap = 'ru'\r\n\r\nUse <C-J> to manually change keymap\r\n\r\nSuggestions and improvements are appreciated.\r\n","install_details":"Put file tex_AutoKeymap.vim into ftplugin folder.","5":"Put file tex_AutoKeymap.vim into ftplugin folder.","first_name":"Artem","6":"Artem","last_name":"Shcherbina","7":"Shcherbina","releases":[{"0":"3812","vim_version":"7.0","1":"7.0","script_version":"0.9","2":"0.9","version_comment":"language detection and switching improved","3":"language detection and switching improved","package":"tex_AutoKeymap.vim","4":"tex_AutoKeymap.vim","src_id":"17652","5":"17652","creation_date":"1332593923","6":"1332593923"},{"0":"3812","vim_version":"7.0","1":"7.0","script_version":"0.7","2":"0.7","version_comment":"Initial upload","3":"Initial upload","package":"tex_AutoKeymap.vim","4":"tex_AutoKeymap.vim","src_id":"16906","5":"16906","creation_date":"1321715089","6":"1321715089"}]},"3811":{"script_id":"3811","0":"3811","script_name":"project.vim","1":"project.vim","script_type":"utility","2":"utility","summary":"Fast  to open  C project","3":"Fast  to open  C project","description":"This script trys to help you open a C project quickly and automatically initialize the working environment, such as creating cscope, ctags files, files_list, etc.\r\n\r\nMore work is needed. Now the script contains the following functionalitiy:\r\n\r\n1. Initialize the project, which contains recording the work directory, mapping useful keys, etc.\r\n2. Create cscope.out files,  [ cscope.in.out, cscope.po.out are also included]\r\n3. Create ctags files, which is useful for omni completion, make sure you have install the omnicompletion script\r\n4. Update the project. <F8>u\r\n5. Save the working status(just use \"mksession\" command). <F8>s\r\n6. Safely close the project. <F8>q\r\n7. Count source lines. (only take the advantage of  \"wc\" command)  _wc\r\n8. Clear the project, nothing extra files left. (no cscopes, no files.list, no session.vim...)  <F8>c\r\n9. Recover from the last working status.\r\n\r\nSupport a menu named \"Project\". Read more from the script file.  More details about usage will be added soon.","4":"This script trys to help you open a C project quickly and automatically initialize the working environment, such as creating cscope, ctags files, files_list, etc.\r\n\r\nMore work is needed. Now the script contains the following functionalitiy:\r\n\r\n1. Initialize the project, which contains recording the work directory, mapping useful keys, etc.\r\n2. Create cscope.out files,  [ cscope.in.out, cscope.po.out are also included]\r\n3. Create ctags files, which is useful for omni completion, make sure you have install the omnicompletion script\r\n4. Update the project. <F8>u\r\n5. Save the working status(just use \"mksession\" command). <F8>s\r\n6. Safely close the project. <F8>q\r\n7. Count source lines. (only take the advantage of  \"wc\" command)  _wc\r\n8. Clear the project, nothing extra files left. (no cscopes, no files.list, no session.vim...)  <F8>c\r\n9. Recover from the last working status.\r\n\r\nSupport a menu named \"Project\". Read more from the script file.  More details about usage will be added soon.","install_details":"This script cannot be installed in your vimfiles directory. \r\n\r\nYou need to put it in another directory. And use command \"gvim -S \/path\/to\/project.vim\" in your project direcory. \r\nThe best way to do this is write a shell script(you can name it \"open_project\"),  including these words:\r\n\r\n[LINUX Version]\r\n#!\/bin\/bash\r\ngvim -S \/path\/to\/project.vim\r\n\r\n[WINDOWS Version]              --------------------    (start.bat)\r\nstart gvim -S \/path\/to\/project.vim\r\n\r\n\r\nPut the shell script in your project's directory, double-click to use it.\r\n\r\nTips:\r\nOn linux, put these words to a nautilus script (saved to ~\/.gnome2\/nautilus-scripts\/):\r\n\r\n#!\/bin\/bash\r\ngvim -S \/path\/to\/project.vim\r\n\r\nAttention: all scripts need  \"chmod +x scirpt_file\". \r\nUsage: just right click the project directory and select the script command.\r\n\r\nNote:\r\nWindows user has to install cscope, ctags, sort, wc, etc executables to use this script.  But cscope works slowly under windows,  the best way to use this script is under linux. \r\n\r\nTry gvim, but not vim! gvim is so graphical!","5":"This script cannot be installed in your vimfiles directory. \r\n\r\nYou need to put it in another directory. And use command \"gvim -S \/path\/to\/project.vim\" in your project direcory. \r\nThe best way to do this is write a shell script(you can name it \"open_project\"),  including these words:\r\n\r\n[LINUX Version]\r\n#!\/bin\/bash\r\ngvim -S \/path\/to\/project.vim\r\n\r\n[WINDOWS Version]              --------------------    (start.bat)\r\nstart gvim -S \/path\/to\/project.vim\r\n\r\n\r\nPut the shell script in your project's directory, double-click to use it.\r\n\r\nTips:\r\nOn linux, put these words to a nautilus script (saved to ~\/.gnome2\/nautilus-scripts\/):\r\n\r\n#!\/bin\/bash\r\ngvim -S \/path\/to\/project.vim\r\n\r\nAttention: all scripts need  \"chmod +x scirpt_file\". \r\nUsage: just right click the project directory and select the script command.\r\n\r\nNote:\r\nWindows user has to install cscope, ctags, sort, wc, etc executables to use this script.  But cscope works slowly under windows,  the best way to use this script is under linux. \r\n\r\nTry gvim, but not vim! gvim is so graphical!","first_name":"Jingguang","6":"Jingguang","last_name":"Pang","7":"Pang","releases":[{"0":"3811","vim_version":"7.3","1":"7.3","script_version":"1.3","2":"1.3","version_comment":"Add documentation to the script file header.","3":"Add documentation to the script file header.","package":"project.vim","4":"project.vim","src_id":"17002","5":"17002","creation_date":"1322749513","6":"1322749513"},{"0":"3811","vim_version":"7.3","1":"7.3","script_version":"1.2","2":"1.2","version_comment":"1. Depart the \"save project\" from \"save and close\" functionality.\r\n2. Add Project menu, simple work!","3":"1. Depart the \"save project\" from \"save and close\" functionality.\r\n2. Add Project menu, simple work!","package":"project.vim","4":"project.vim","src_id":"16999","5":"16999","creation_date":"1322745077","6":"1322745077"},{"0":"3811","vim_version":"7.3","1":"7.3","script_version":"1.1","2":"1.1","version_comment":"Add clear, quit and save project functionality, etc.\r\nAdd lines count functionality","3":"Add clear, quit and save project functionality, etc.\r\nAdd lines count functionality","package":"project.vim","4":"project.vim","src_id":"16988","5":"16988","creation_date":"1322487936","6":"1322487936"}]},"3810":{"script_id":"3810","0":"3810","script_name":"RSTO","1":"RSTO","script_type":"utility","2":"utility","summary":"Goto function (open\/create) for ReStructured Text directives","3":"Goto function (open\/create) for ReStructured Text directives","description":"Helper to open files referenced in ReStructuredText directives (image\/figure\/include). If text\/file does not exist then will be added\/created. Opening is possible with go to position of the file (via line number or pattern options in the directive) or not. Adding handlers of other directives is simple.\r\n\r\nSo, current version supports \".. include::\" with \":start-line:\", \":start-after:\" options (to jump) and \".. image::\", \".. figure::\" directives.\r\n\r\nDefault key bindings are:\r\n,gf - simple open existent file\r\n,gF - forced open (create, jump to position in the file)\r\n\r\nSettings are:\r\nRSTO_imgopen - path (+ arguments) to exe file to open image\r\nRSTO_imgnew - path (+ arguments) to exe file to create nonexistent image\r\ng:RSTO_handlers - only to add own directives' handlers!\r\n\r\nGood luck!","4":"Helper to open files referenced in ReStructuredText directives (image\/figure\/include). If text\/file does not exist then will be added\/created. Opening is possible with go to position of the file (via line number or pattern options in the directive) or not. Adding handlers of other directives is simple.\r\n\r\nSo, current version supports \".. include::\" with \":start-line:\", \":start-after:\" options (to jump) and \".. image::\", \".. figure::\" directives.\r\n\r\nDefault key bindings are:\r\n,gf - simple open existent file\r\n,gF - forced open (create, jump to position in the file)\r\n\r\nSettings are:\r\nRSTO_imgopen - path (+ arguments) to exe file to open image\r\nRSTO_imgnew - path (+ arguments) to exe file to create nonexistent image\r\ng:RSTO_handlers - only to add own directives' handlers!\r\n\r\nGood luck!","install_details":"Copy into your vimfiles\/plugin","5":"Copy into your vimfiles\/plugin","first_name":"Paul","6":"Paul","last_name":"Yosifov","7":"Yosifov","releases":[{"0":"3810","vim_version":"7.0","1":"7.0","script_version":"0.0.2","2":"0.0.2","version_comment":"Bug-fixing","3":"Bug-fixing","package":"rsto.vim","4":"rsto.vim","src_id":"16910","5":"16910","creation_date":"1321809482","6":"1321809482"},{"0":"3810","vim_version":"7.0","1":"7.0","script_version":"0.0.1","2":"0.0.1","version_comment":"Initial upload","3":"Initial upload","package":"rsto.vim","4":"rsto.vim","src_id":"16901","5":"16901","creation_date":"1321634801","6":"1321634801"}]},"3809":{"script_id":"3809","0":"3809","script_name":"ipi","1":"ipi","script_type":"utility","2":"utility","summary":"Load plugins individually - cut down start-up time.","3":"Load plugins individually - cut down start-up time.","description":"This plugin is very much inspired by Tim Pope's pathogen plug-in. vim-ipi\r\nadds the functionality of loading infrequently used plugins later. This\r\ngreatly helps in cutting down vim's start-up time.\r\n\r\nExamples:\r\nLoad gundo plugin later:\r\n:IP gundo\r\n\r\nLoad gundo and speeddating plugins later:\r\n:IP gundo speedating\r\n\r\nLoad all known plugins later:\r\n:IP!\r\n\r\nA very high level of convenience can be achieved by loading the plug-ins\r\nautomatically right before using their functionality. Here is an example for\r\nthe gundo plug-in. I just prefixed the mapping with \":silent! IP gundo<CR>\":\r\nnmap <leader>u :silent! IP gundo<CR>:GundoToggle<CR>\r\n\r\nTips:\r\nSome plugins use the autocommand VimEnter to do some initialization. ipi\r\nhas built-in support for a number of plugins that use this feature. A\r\ndetailed description is provided for the g:ipi_vimenter_autocommand\r\nvariable.  In case a plugin is not support yet, manual execution of the\r\nautocommand can be done by running the following command:\r\n:do <AUTOGROUPNAME> VimEnter\r\n\r\nFor the convenience wrapper it would look like this:\r\nnmap <leader>f :silent! IP NERDTree<CR>:do NERDTree VimEnter<CR>:NERDTree<CR>","4":"This plugin is very much inspired by Tim Pope's pathogen plug-in. vim-ipi\r\nadds the functionality of loading infrequently used plugins later. This\r\ngreatly helps in cutting down vim's start-up time.\r\n\r\nExamples:\r\nLoad gundo plugin later:\r\n:IP gundo\r\n\r\nLoad gundo and speeddating plugins later:\r\n:IP gundo speedating\r\n\r\nLoad all known plugins later:\r\n:IP!\r\n\r\nA very high level of convenience can be achieved by loading the plug-ins\r\nautomatically right before using their functionality. Here is an example for\r\nthe gundo plug-in. I just prefixed the mapping with \":silent! IP gundo<CR>\":\r\nnmap <leader>u :silent! IP gundo<CR>:GundoToggle<CR>\r\n\r\nTips:\r\nSome plugins use the autocommand VimEnter to do some initialization. ipi\r\nhas built-in support for a number of plugins that use this feature. A\r\ndetailed description is provided for the g:ipi_vimenter_autocommand\r\nvariable.  In case a plugin is not support yet, manual execution of the\r\nautocommand can be done by running the following command:\r\n:do <AUTOGROUPNAME> VimEnter\r\n\r\nFor the convenience wrapper it would look like this:\r\nnmap <leader>f :silent! IP NERDTree<CR>:do NERDTree VimEnter<CR>:NERDTree<CR>","install_details":"Install in ~\/.vim\/autoload (or ~\\vimfiles\\autoload) together with pathogen\r\n(vimscript#2332).\r\n\r\nPathogen's settings can be used to configure ipi as well, e.g. disable\r\nplugins (g:pathogen_disabled).\r\n\r\nFor loading plugins later, install them in ~\/.vim\/ipi (or ~\\vimfiles\\ipi)\r\nand  add `call ipi#inspect()` to .vimrc. This will create a list of plugins\r\nthat can be loaded later by using the LL command:\r\n\r\nThe development version is available at http:\/\/www.github.com\/jceb\/vim-ipi.","5":"Install in ~\/.vim\/autoload (or ~\\vimfiles\\autoload) together with pathogen\r\n(vimscript#2332).\r\n\r\nPathogen's settings can be used to configure ipi as well, e.g. disable\r\nplugins (g:pathogen_disabled).\r\n\r\nFor loading plugins later, install them in ~\/.vim\/ipi (or ~\\vimfiles\\ipi)\r\nand  add `call ipi#inspect()` to .vimrc. This will create a list of plugins\r\nthat can be loaded later by using the LL command:\r\n\r\nThe development version is available at http:\/\/www.github.com\/jceb\/vim-ipi.","first_name":"Jan Christoph","6":"Jan Christoph","last_name":"Ebersbach","7":"Ebersbach","releases":[{"0":"3809","vim_version":"7.0","1":"7.0","script_version":"1.3","2":"1.3","version_comment":"- add support for automatically executing the VimEnter autocommand when\r\n  loading a plugin\r\n- rename LL to IP","3":"- add support for automatically executing the VimEnter autocommand when\r\n  loading a plugin\r\n- rename LL to IP","package":"ipi.vim","4":"ipi.vim","src_id":"17078","5":"17078","creation_date":"1324122588","6":"1324122588"},{"0":"3809","vim_version":"7.0","1":"7.0","script_version":"1.2","2":"1.2","version_comment":"- update documentation","3":"- update documentation","package":"ipi.vim","4":"ipi.vim","src_id":"16909","5":"16909","creation_date":"1321788765","6":"1321788765"},{"0":"3809","vim_version":"7.0","1":"7.0","script_version":"1.1","2":"1.1","version_comment":"- change global variable lp to be script local\r\n- add support for a specific path to ipi#inspect\r\n- externalize ipi#source\r\n- source scripts in ftdetect and after directories as well","3":"- change global variable lp to be script local\r\n- add support for a specific path to ipi#inspect\r\n- externalize ipi#source\r\n- source scripts in ftdetect and after directories as well","package":"ipi.vim","4":"ipi.vim","src_id":"16895","5":"16895","creation_date":"1321568000","6":"1321568000"},{"0":"3809","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"ipi.vim","4":"ipi.vim","src_id":"16884","5":"16884","creation_date":"1321478358","6":"1321478358"}]},"3808":{"script_id":"3808","0":"3808","script_name":"TFS","1":"TFS","script_type":"utility","2":"utility","summary":"Use TFS version control from within VIM","3":"Use TFS version control from within VIM","description":"INTRODUCTION                                     \r\n\r\nThis plugin is a tool which allows TFS version control integration while\r\nediting files with VIM.  It supports TFS with Visual Studio 2005,2008 &\r\n2010.  It's comparatively full featured and allows:\r\n\r\n  * Add\/Check-in\/Checkout\/Revert\/Get Latest\r\n  * Getting specific versions of the current file\r\n  * Diffing the current file against the latest version\r\n  * Checking which files have been modified\r\n  * Looking at the history of the current file\r\n  * Diffing the current file against a particular changeset\r\n  * Diffing the current file against the latest version\r\n  * Creating shelve sets\r\n\r\nMAPPINGS                \r\n\r\nIn addition to the GVIM menu, the following mappings are provided by\r\ndefault.\r\n\r\n  Mapping  Command        Purpose ~\r\n  \\ta      TfAdd          Add current file to TFS\r\n  \\to      TfCheckout     Check out current file from TFS\r\n  \\ti      TfCheckin      Check current file into TFS with comment \r\n  \\tc      TfCheckinAll   Check in multiple files to\r\n  \\tl      TfGetLatest    Get the latest version of current file\r\n  \\tr      TfRevert       Revert local changes to current file\r\n  \\th      TfHistory      Get the history of the local file\r\n  \\tv      TfViewVer      Preview a specific version of the file\r\n  \\td      TfDiffVer      Diff current file against specific version\r\n  \\tt      TfDiffLatest   Diff recent changes against latest\r\n  \\ts      TfStatus       Show all files which have been modified\r\n  \\te      TfShelve       Create a shelve set\r\n  \\tu      TfUnshelve     Unshelve a shelve set\r\n\r\nOTHER COMMANDS             \r\n\r\n  Command                 Purpose ~\r\n  Tf \"command line\"       Run a raw tf command\r\n  TfHelp                  Help for the tf command\r\n  TfPt \"command line\"     Run a raw tfpt command\r\n  TfPtHelp                Help for the tfpt command\r\n  TfAnnotate              Examine annotated view of current file\r\n  TfReview                Review changes made to workspace\r\n  TfHistoryDetailed       See detailed branch history for current file","4":"INTRODUCTION                                     \r\n\r\nThis plugin is a tool which allows TFS version control integration while\r\nediting files with VIM.  It supports TFS with Visual Studio 2005,2008 &\r\n2010.  It's comparatively full featured and allows:\r\n\r\n  * Add\/Check-in\/Checkout\/Revert\/Get Latest\r\n  * Getting specific versions of the current file\r\n  * Diffing the current file against the latest version\r\n  * Checking which files have been modified\r\n  * Looking at the history of the current file\r\n  * Diffing the current file against a particular changeset\r\n  * Diffing the current file against the latest version\r\n  * Creating shelve sets\r\n\r\nMAPPINGS                \r\n\r\nIn addition to the GVIM menu, the following mappings are provided by\r\ndefault.\r\n\r\n  Mapping  Command        Purpose ~\r\n  \\ta      TfAdd          Add current file to TFS\r\n  \\to      TfCheckout     Check out current file from TFS\r\n  \\ti      TfCheckin      Check current file into TFS with comment \r\n  \\tc      TfCheckinAll   Check in multiple files to\r\n  \\tl      TfGetLatest    Get the latest version of current file\r\n  \\tr      TfRevert       Revert local changes to current file\r\n  \\th      TfHistory      Get the history of the local file\r\n  \\tv      TfViewVer      Preview a specific version of the file\r\n  \\td      TfDiffVer      Diff current file against specific version\r\n  \\tt      TfDiffLatest   Diff recent changes against latest\r\n  \\ts      TfStatus       Show all files which have been modified\r\n  \\te      TfShelve       Create a shelve set\r\n  \\tu      TfUnshelve     Unshelve a shelve set\r\n\r\nOTHER COMMANDS             \r\n\r\n  Command                 Purpose ~\r\n  Tf \"command line\"       Run a raw tf command\r\n  TfHelp                  Help for the tf command\r\n  TfPt \"command line\"     Run a raw tfpt command\r\n  TfPtHelp                Help for the tfpt command\r\n  TfAnnotate              Examine annotated view of current file\r\n  TfReview                Review changes made to workspace\r\n  TfHistoryDetailed       See detailed branch history for current file","install_details":"Unzip the archive into your ~\/_vim directory.\r\nThat should put tfs.vim in ~\/_vim\/plugin and tfs.txt in ~\/_vim\/doc.\r\n\r\nRun :helptags ~\/_vim\/doc\r\n\r\nGo :help tfs for the help page. ","5":"Unzip the archive into your ~\/_vim directory.\r\nThat should put tfs.vim in ~\/_vim\/plugin and tfs.txt in ~\/_vim\/doc.\r\n\r\nRun :helptags ~\/_vim\/doc\r\n\r\nGo :help tfs for the help page. ","first_name":"Ben","6":"Ben","last_name":"Staniford","7":"Staniford","releases":[{"0":"3808","vim_version":"7.3","1":"7.3","script_version":"1.1.3","2":"1.1.3","version_comment":"Added support for TFS 2012, Removed ^ escaping since this is no longer required and breaks in later patch levels Vim 7.3.  (If you need to use an older version of Vim please use TFS.vim v 1.1.2)","3":"Added support for TFS 2012, Removed ^ escaping since this is no longer required and breaks in later patch levels Vim 7.3.  (If you need to use an older version of Vim please use TFS.vim v 1.1.2)","package":"tfs.zip","4":"tfs.zip","src_id":"20020","5":"20020","creation_date":"1367754316","6":"1367754316"},{"0":"3808","vim_version":"7.0","1":"7.0","script_version":"1.1.2","2":"1.1.2","version_comment":"Added TfUnshelve and made popup windows automatically use as little screen estate as poss.","3":"Added TfUnshelve and made popup windows automatically use as little screen estate as poss.","package":"tfs.zip","4":"tfs.zip","src_id":"16892","5":"16892","creation_date":"1321542992","6":"1321542992"},{"0":"3808","vim_version":"7.0","1":"7.0","script_version":"1.1.1","2":"1.1.1","version_comment":"Fixed quoting of parameters to include ^\" style quoting supporting TFS workspaces with spaces in paths.","3":"Fixed quoting of parameters to include ^\" style quoting supporting TFS workspaces with spaces in paths.","package":"tfs.zip","4":"tfs.zip","src_id":"16888","5":"16888","creation_date":"1321530292","6":"1321530292"},{"0":"3808","vim_version":"7.0","1":"7.0","script_version":"1.1","2":"1.1","version_comment":"Added TfReview, TfCheckinAll, TfShelve to checkin multiple files, and create shelve sets.  Also fixed several bugs.","3":"Added TfReview, TfCheckinAll, TfShelve to checkin multiple files, and create shelve sets.  Also fixed several bugs.","package":"tfs.zip","4":"tfs.zip","src_id":"16887","5":"16887","creation_date":"1321526082","6":"1321526082"},{"0":"3808","vim_version":"7.0","1":"7.0","script_version":"1.0.1","2":"1.0.1","version_comment":"Fixed small typo bug with Tf and TfPt commands","3":"Fixed small typo bug with Tf and TfPt commands","package":"tfs.zip","4":"tfs.zip","src_id":"16881","5":"16881","creation_date":"1321450854","6":"1321450854"},{"0":"3808","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"tfs.zip","4":"tfs.zip","src_id":"16880","5":"16880","creation_date":"1321450066","6":"1321450066"}]},"3807":{"script_id":"3807","0":"3807","script_name":"apg.vim","1":"apg.vim","script_type":"ftplugin","2":"ftplugin","summary":"Auto generate and append password","3":"Auto generate and append password","description":"My first attempt a vim script. Runs the apg(1) program (apt-get install apg, http:\/\/www.adel.nursat.kz\/apg\/download.shtml) and appends a randomly generated password to the end of the current line.\r\n\r\nPasswords are unpronounceable and random, though I exclude some special symbols -- those that break \"words\" when double-clicking in an xterm (makes copy-pasting passwords for login easier).\r\n\r\nSince I store my passwords in a GnuPG encrypted file, I added a binding for F12 that actives when opening .gpg, .pgp, or .asc files.","4":"My first attempt a vim script. Runs the apg(1) program (apt-get install apg, http:\/\/www.adel.nursat.kz\/apg\/download.shtml) and appends a randomly generated password to the end of the current line.\r\n\r\nPasswords are unpronounceable and random, though I exclude some special symbols -- those that break \"words\" when double-clicking in an xterm (makes copy-pasting passwords for login easier).\r\n\r\nSince I store my passwords in a GnuPG encrypted file, I added a binding for F12 that actives when opening .gpg, .pgp, or .asc files.","install_details":"Yes, I realize this is INCREDIBLY special purpose. :)\r\n\r\nFor the curious, here is the set of printable characters I determined that break the word-detection selection of xterm:\r\n\r\n\"$'()*;<=>[\\]^`{|}","5":"Yes, I realize this is INCREDIBLY special purpose. :)\r\n\r\nFor the curious, here is the set of printable characters I determined that break the word-detection selection of xterm:\r\n\r\n\"$'()*;<=>[\\]^`{|}","first_name":"schizo","6":"schizo","last_name":"bovine","7":"bovine","releases":[{"0":"3807","vim_version":"7.0","1":"7.0","script_version":"0.00001","2":"0.00001","version_comment":"Initial upload","3":"Initial upload","package":"apg.vim","4":"apg.vim","src_id":"16877","5":"16877","creation_date":"1321421801","6":"1321421801"}]},"3806":{"script_id":"3806","0":"3806","script_name":"openrel.vim","1":"openrel.vim","script_type":"utility","2":"utility","summary":"Open relatively-described files under the cursor","3":"Open relatively-described files under the cursor","description":"\" DESCRIPTION:\r\n\"  This plugin enables vim to open relatively-described files under the cursor.\r\n\"\r\n\"  If :call GotoRelTargetFile(), jump to the file\r\n\"  Ctrl-O : You can go back to source file\r\n\"  let g:openrel_root_dirs = ['\/var\/www\/']\r\n\"\r\n\"  Please add following setting to your .vimrc\r\n\" ==================================================\r\n\" nnoremap gaf :<C-u>call GotoRelTargetFile()<CR>\r\n\" ==================================================","4":"\" DESCRIPTION:\r\n\"  This plugin enables vim to open relatively-described files under the cursor.\r\n\"\r\n\"  If :call GotoRelTargetFile(), jump to the file\r\n\"  Ctrl-O : You can go back to source file\r\n\"  let g:openrel_root_dirs = ['\/var\/www\/']\r\n\"\r\n\"  Please add following setting to your .vimrc\r\n\" ==================================================\r\n\" nnoremap gaf :<C-u>call GotoRelTargetFile()<CR>\r\n\" ==================================================","install_details":"","5":"","first_name":"Ryo","6":"Ryo","last_name":"Shibayama","7":"Shibayama","releases":[{"0":"3806","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"initial upload","3":"initial upload","package":"openrel.vim","4":"openrel.vim","src_id":"16870","5":"16870","creation_date":"1321369434","6":"1321369434"}]},"3804":{"script_id":"3804","0":"3804","script_name":"vim-diff","1":"vim-diff","script_type":"utility","2":"utility","summary":"diff written in VimL.","3":"diff written in VimL.","description":"Usage:\r\n  :set runtimepath+=\/path\/to\/vim-diff\r\n  :set diffexpr=diff#diffexpr()\r\n\r\nlatest source: https:\/\/github.com\/ynkdir\/vim-diff","4":"Usage:\r\n  :set runtimepath+=\/path\/to\/vim-diff\r\n  :set diffexpr=diff#diffexpr()\r\n\r\nlatest source: https:\/\/github.com\/ynkdir\/vim-diff","install_details":"","5":"","first_name":"Yukihiro","6":"Yukihiro","last_name":"Nakadaira","7":"Nakadaira","releases":[{"0":"3804","vim_version":"7.3","1":"7.3","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"vim-diff.zip","4":"vim-diff.zip","src_id":"16865","5":"16865","creation_date":"1321350339","6":"1321350339"}]},"3803":{"script_id":"3803","0":"3803","script_name":"vim-symbols-strings","1":"vim-symbols-strings","script_type":"utility","2":"utility","summary":"A silly little plugin to convert Ruby symbols to strings and vice versa","3":"A silly little plugin to convert Ruby symbols to strings and vice versa","description":"Full detail can be found here https:\/\/github.com\/rorymckinley\/vim-symbols-strings.","4":"Full detail can be found here https:\/\/github.com\/rorymckinley\/vim-symbols-strings.","install_details":"Currently, only tested with pathogen. Will gladly help to get it working with other installation mechanisms.","5":"Currently, only tested with pathogen. Will gladly help to get it working with other installation mechanisms.","first_name":"Rory","6":"Rory","last_name":"McKinley","7":"McKinley","releases":[{"0":"3803","vim_version":"7.3","1":"7.3","script_version":"1.0.0","2":"1.0.0","version_comment":"Initial upload","3":"Initial upload","package":"rorymckinley-vim-symbols-strings-V1.0.0-0-g56327b2.tar.gz","4":"rorymckinley-vim-symbols-strings-V1.0.0-0-g56327b2.tar.gz","src_id":"16857","5":"16857","creation_date":"1321130657","6":"1321130657"}]},"3802":{"script_id":"3802","0":"3802","script_name":"prop.vim","1":"prop.vim","script_type":"syntax","2":"syntax","summary":"-- trying to remove --","3":"-- trying to remove --","description":"-- trying to remove --","4":"-- trying to remove --","install_details":"","5":"","first_name":"Douglas","6":"Douglas","last_name":"Drumond","7":"Drumond","releases":[{"0":"3802","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"prop.vim","4":"prop.vim","src_id":"16852","5":"16852","creation_date":"1321030863","6":"1321030863"}]},"3801":{"script_id":"3801","0":"3801","script_name":"fontforge_script.vim","1":"fontforge_script.vim","script_type":"syntax","2":"syntax","summary":"Syntax highlighting for FontForge scripts","3":"Syntax highlighting for FontForge scripts","description":"Syntax file for scripts written in FontForge's native scripting language.","4":"Syntax file for scripts written in FontForge's native scripting language.","install_details":"Copy fontforge_script.vim to ~\/.vim\/syntax directory. Add this in ~\/.vimrc to have it called automatically when editing .pe files :\r\nautocmd BufRead *.pe set syntax=fontforge_script","5":"Copy fontforge_script.vim to ~\/.vim\/syntax directory. Add this in ~\/.vimrc to have it called automatically when editing .pe files :\r\nautocmd BufRead *.pe set syntax=fontforge_script","first_name":"Bernard","6":"Bernard","last_name":"Massot","7":"Massot","releases":[{"0":"3801","vim_version":"7.3","1":"7.3","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"fontforge_script.vim","4":"fontforge_script.vim","src_id":"16842","5":"16842","creation_date":"1320872717","6":"1320872717"}]},"3800":{"script_id":"3800","0":"3800","script_name":"anwolib","1":"anwolib","script_type":"utility","2":"utility","summary":"Yet another vim library","3":"Yet another vim library","description":"Library to support (my) posts on the vim_use mailing list.\r\n\r\nDocumentation: check comments in the source code\r\n\r\n\r\nFILES IN THE ARCHIVE\r\n\r\nautoload\\nwo\\lib.vim  (stand-alone)\r\nautoload\\nwo\\gvmap.vim  (included for cmds.vim)\r\nplugin\\cmds.vim  (cmds frontend)\r\nautoload\\cmds.vim  (cmds implementation)\r\n\r\n\r\nFUNCTIONS \/ COMMANDS\r\n\r\nautoload\\nwo\\lib.vim\r\nnwo#lib#Avail(varname)\r\nnwo#lib#BG(varname, ...)\r\nnwo#lib#CmdlineWidth()\r\nnwo#lib#CollEscape(str)\r\nnwo#lib#ExpandTabs(line, ...)\r\nnwo#lib#ExpandTabs_Mbyte(line, ...)\r\nnwo#lib#ExtendUniq(baselist, append, ...)\r\nnwo#lib#FargsList(str)\r\nnwo#lib#FitEcho(str)\r\nnwo#lib#FitStr(str)\r\nnwo#lib#Flatten1(list)\r\nnwo#lib#GetPlaceHolder(str)\r\nnwo#lib#Let(val, expr, ...)\r\nnwo#lib#MagicEscape(pat, ...)\r\nnwo#lib#MenuEscape(entry)\r\nnwo#lib#NotEsc(esc_char)\r\nnwo#lib#PairList(list1, list2)\r\nnwo#lib#ReplEscape(repl, ...)\r\nnwo#lib#Rot13(str)\r\nnwo#lib#SlashEscape(str, ...)\r\nnwo#lib#SoftTabstop(vcol)\r\nnwo#lib#SpacesToTabs(line, ...)\r\nnwo#lib#SpacesToTabs_Mbyte(line, ...)\r\nnwo#lib#Split1(str)\r\nnwo#lib#Substract(list1, list2)\r\nnwo#lib#TruncFilename(filename, maxlen)\r\nnwo#lib#TruncStr(str, maxlen)\r\nnwo#lib#Uniq(list)\r\n\r\nautoload\\nwo\\gvmap.vim\r\n\r\nplugin\\cmds.vim\r\n:KeepView {cmd}     \r\n:With {setlocal-args} Do {cmd}   \r\n:InFunc[!] {cmd}     \r\n:InFuncCount {cmd}     \r\n:Fsnorm[!] {normal-cmds}    \r\n\r\n\r\n\r\nYeah, I know, there are dozens of other libraries ...\r\ngenutils, vimscript #197 (Hari Krishna Dara)\r\nlh-vim-lib, vimscript #214 (Luc Hermitte), http:\/\/code.google.com\/p\/lh-vim\/wiki\/lhVimLib\r\ncecutil, vimscript #1066 (DrChip), http:\/\/drchip.0sites.net\/astronaut\/vim\/index.html#CECUTIL\r\ntlib, vimscript #1863 (Thomas Link), http:\/\/github.com\/tomtom\/\r\nTOVL, vimscript #1963 (Marc Weber), http:\/\/github.com\/MarcWeber\/theonevimlib\r\nl9, vimscript #3252 (Takeshi Nishida), https:\/\/bitbucket.org\/ns9tks\/vim-l9\/\r\n(Tim Pope vimuser #9012, Kana Natsuno vimuser #13595, ...)\r\netc!!\r\n\r\n\r\n2011 Nov 08","4":"Library to support (my) posts on the vim_use mailing list.\r\n\r\nDocumentation: check comments in the source code\r\n\r\n\r\nFILES IN THE ARCHIVE\r\n\r\nautoload\\nwo\\lib.vim  (stand-alone)\r\nautoload\\nwo\\gvmap.vim  (included for cmds.vim)\r\nplugin\\cmds.vim  (cmds frontend)\r\nautoload\\cmds.vim  (cmds implementation)\r\n\r\n\r\nFUNCTIONS \/ COMMANDS\r\n\r\nautoload\\nwo\\lib.vim\r\nnwo#lib#Avail(varname)\r\nnwo#lib#BG(varname, ...)\r\nnwo#lib#CmdlineWidth()\r\nnwo#lib#CollEscape(str)\r\nnwo#lib#ExpandTabs(line, ...)\r\nnwo#lib#ExpandTabs_Mbyte(line, ...)\r\nnwo#lib#ExtendUniq(baselist, append, ...)\r\nnwo#lib#FargsList(str)\r\nnwo#lib#FitEcho(str)\r\nnwo#lib#FitStr(str)\r\nnwo#lib#Flatten1(list)\r\nnwo#lib#GetPlaceHolder(str)\r\nnwo#lib#Let(val, expr, ...)\r\nnwo#lib#MagicEscape(pat, ...)\r\nnwo#lib#MenuEscape(entry)\r\nnwo#lib#NotEsc(esc_char)\r\nnwo#lib#PairList(list1, list2)\r\nnwo#lib#ReplEscape(repl, ...)\r\nnwo#lib#Rot13(str)\r\nnwo#lib#SlashEscape(str, ...)\r\nnwo#lib#SoftTabstop(vcol)\r\nnwo#lib#SpacesToTabs(line, ...)\r\nnwo#lib#SpacesToTabs_Mbyte(line, ...)\r\nnwo#lib#Split1(str)\r\nnwo#lib#Substract(list1, list2)\r\nnwo#lib#TruncFilename(filename, maxlen)\r\nnwo#lib#TruncStr(str, maxlen)\r\nnwo#lib#Uniq(list)\r\n\r\nautoload\\nwo\\gvmap.vim\r\n\r\nplugin\\cmds.vim\r\n:KeepView {cmd}     \r\n:With {setlocal-args} Do {cmd}   \r\n:InFunc[!] {cmd}     \r\n:InFuncCount {cmd}     \r\n:Fsnorm[!] {normal-cmds}    \r\n\r\n\r\n\r\nYeah, I know, there are dozens of other libraries ...\r\ngenutils, vimscript #197 (Hari Krishna Dara)\r\nlh-vim-lib, vimscript #214 (Luc Hermitte), http:\/\/code.google.com\/p\/lh-vim\/wiki\/lhVimLib\r\ncecutil, vimscript #1066 (DrChip), http:\/\/drchip.0sites.net\/astronaut\/vim\/index.html#CECUTIL\r\ntlib, vimscript #1863 (Thomas Link), http:\/\/github.com\/tomtom\/\r\nTOVL, vimscript #1963 (Marc Weber), http:\/\/github.com\/MarcWeber\/theonevimlib\r\nl9, vimscript #3252 (Takeshi Nishida), https:\/\/bitbucket.org\/ns9tks\/vim-l9\/\r\n(Tim Pope vimuser #9012, Kana Natsuno vimuser #13595, ...)\r\netc!!\r\n\r\n\r\n2011 Nov 08","install_details":"","5":"","first_name":"Andy","6":"Andy","last_name":"Wokula","7":"Wokula","releases":[{"0":"3800","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"anwolib.zip","4":"anwolib.zip","src_id":"16831","5":"16831","creation_date":"1320762066","6":"1320762066"}]},"3799":{"script_id":"3799","0":"3799","script_name":"Cleanroom","1":"Cleanroom","script_type":"color scheme","2":"color scheme","summary":"A clean, light colour scheme","3":"A clean, light colour scheme","description":"A minimal colour scheme that stays out of your way.\r\n\r\nPreview screenshot: http:\/\/www.node.mu\/images\/cleanroom.png\r\n\r\nThis color scheme is meant for use with a gui version of Vim.","4":"A minimal colour scheme that stays out of your way.\r\n\r\nPreview screenshot: http:\/\/www.node.mu\/images\/cleanroom.png\r\n\r\nThis color scheme is meant for use with a gui version of Vim.","install_details":"Download the script and copy it to your ~\/.vim\/colors\/ directory. To tell Vim to use the color scheme, \":colorscheme cleanroom\".","5":"Download the script and copy it to your ~\/.vim\/colors\/ directory. To tell Vim to use the color scheme, \":colorscheme cleanroom\".","first_name":"Vy-Shane","6":"Vy-Shane","last_name":"Sin Fat","7":"Sin Fat","releases":[{"0":"3799","vim_version":"7.3","1":"7.3","script_version":"1.0.1","2":"1.0.1","version_comment":"Added hi Conceal.","3":"Added hi Conceal.","package":"cleanroom.vim","4":"cleanroom.vim","src_id":"17042","5":"17042","creation_date":"1323413293","6":"1323413293"},{"0":"3799","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"cleanroom.vim","4":"cleanroom.vim","src_id":"16820","5":"16820","creation_date":"1320670473","6":"1320670473"}]},"3798":{"script_id":"3798","0":"3798","script_name":"node.js","1":"node.js","script_type":"utility","2":"utility","summary":"File type detect plugin for vim which detects node.js shebang","3":"File type detect plugin for vim which detects node.js shebang","description":"vim-node.js is a file type detect plugin for vim which detects node.js shebang and sets file type to JavaScript.\r\n\r\nGitHub repository: https:\/\/github.com\/mmalecki\/vim-node.js","4":"vim-node.js is a file type detect plugin for vim which detects node.js shebang and sets file type to JavaScript.\r\n\r\nGitHub repository: https:\/\/github.com\/mmalecki\/vim-node.js","install_details":"Install via pathogen by cloning\/adding submodule git:\/\/github.com\/mmalecki\/vim-node.js.git to ~\/.vim\/bundle or by dropping this script in ~\/vim\/ftdetect","5":"Install via pathogen by cloning\/adding submodule git:\/\/github.com\/mmalecki\/vim-node.js.git to ~\/.vim\/bundle or by dropping this script in ~\/vim\/ftdetect","first_name":"Maciej","6":"Maciej","last_name":"Ma\u0142ecki","7":"Małecki","releases":[{"0":"3798","vim_version":"7.0","1":"7.0","script_version":"1.1.1","2":"1.1.1","version_comment":"Redefine `DetectNode` function","3":"Redefine `DetectNode` function","package":"node.js.vim","4":"node.js.vim","src_id":"17256","5":"17256","creation_date":"1326978524","6":"1326978524"},{"0":"3798","vim_version":"7.0","1":"7.0","script_version":"1.1.0","2":"1.1.0","version_comment":"Remove echo","3":"Remove echo","package":"node.js.vim","4":"node.js.vim","src_id":"16813","5":"16813","creation_date":"1320585168","6":"1320585168"},{"0":"3798","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"node.js.vim","4":"node.js.vim","src_id":"16812","5":"16812","creation_date":"1320577537","6":"1320577537"}]},"3797":{"script_id":"3797","0":"3797","script_name":"C++11 Syntax Support","1":"C++11 Syntax Support","script_type":"syntax","2":"syntax","summary":"A port of the existing C++ syntax to allow for C++11 features","3":"A port of the existing C++ syntax to allow for C++11 features","description":"Modified existing c.vim and cpp.vim (into cpp11.vim and cpp11_cbase.vim) to add support for new language features found in C++11.\r\n\r\n* Initialiser lists and lambdas no longer cause curly error highlighting ({} allowed within parentheses).\r\n* constexpr keyword added.\r\n\r\nI'm adding features as I hit them - if something is bugging you and not yet added, let me know.\r\n\r\nNOTE TO ALL:\r\n===========\r\nI've been working on a completely new syntax script from the ground up as extending these existing scripts is just too difficult as C++11\r\nis a very different beast from the original C support that the scripts were based on.\r\n\r\nI expect to have a working release of the new script up here and on github just after the new year.\r\n\r\n~ Mike (2011-12-15)","4":"Modified existing c.vim and cpp.vim (into cpp11.vim and cpp11_cbase.vim) to add support for new language features found in C++11.\r\n\r\n* Initialiser lists and lambdas no longer cause curly error highlighting ({} allowed within parentheses).\r\n* constexpr keyword added.\r\n\r\nI'm adding features as I hit them - if something is bugging you and not yet added, let me know.\r\n\r\nNOTE TO ALL:\r\n===========\r\nI've been working on a completely new syntax script from the ground up as extending these existing scripts is just too difficult as C++11\r\nis a very different beast from the original C support that the scripts were based on.\r\n\r\nI expect to have a working release of the new script up here and on github just after the new year.\r\n\r\n~ Mike (2011-12-15)","install_details":"Tar contains just the required .vim files, so un-tar them in (or copy to) your ~\/.vim\/syntax\/ directory.\r\n\r\nTo make the syntax permanent, consider setting with an auto command in your vimrc:\r\n\r\nau BufNewFile,BufRead *.cpp set syntax=cpp11","5":"Tar contains just the required .vim files, so un-tar them in (or copy to) your ~\/.vim\/syntax\/ directory.\r\n\r\nTo make the syntax permanent, consider setting with an auto command in your vimrc:\r\n\r\nau BufNewFile,BufRead *.cpp set syntax=cpp11","first_name":"Michael","6":"Michael","last_name":"Small","7":"Small","releases":[{"0":"3797","vim_version":"6.0","1":"6.0","script_version":"0.1.1","2":"0.1.1","version_comment":"Fixed corrupted files.","3":"Fixed corrupted files.","package":"cpp11.tgz","4":"cpp11.tgz","src_id":"16806","5":"16806","creation_date":"1320473095","6":"1320473095"}]},"3796":{"script_id":"3796","0":"3796","script_name":"php doc ","1":"php doc ","script_type":"utility","2":"utility","summary":"phpdoc","3":"phpdoc","description":"Use pare2.php make EN & ZH phpdoc\r\nhttp:\/\/blog.planetxml.de\/","4":"Use pare2.php make EN & ZH phpdoc\r\nhttp:\/\/blog.planetxml.de\/","install_details":"autocmd! FileType php\r\n            \\\\ compiler phpcs|\r\n            \\\\ set runtimepath+=your\\\\phpdoc\r\n","5":"autocmd! FileType php\r\n            \\\\ compiler phpcs|\r\n            \\\\ set runtimepath+=your\\\\phpdoc\r\n","first_name":"su","6":"su","last_name":"su","7":"su","releases":[{"0":"3796","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"phpdoc.7z","4":"phpdoc.7z","src_id":"16803","5":"16803","creation_date":"1320399278","6":"1320399278"}]},"3795":{"script_id":"3795","0":"3795","script_name":"codepaper","1":"codepaper","script_type":"color scheme","2":"color scheme","summary":"light yellow gvim color theme","3":"light yellow gvim color theme","description":"Light yellow color theme for gvim\/python\/ruby\/html\/css\r\nXTerminal colors not supported yet.\r\nYou can see sreenshot here\r\nhttp:\/\/my.jetscreenshot.com\/13962\/20130508-ea5i-286kb\r\n\r\ngithub repo: https:\/\/github.com\/piratarusso\/myvim_colors","4":"Light yellow color theme for gvim\/python\/ruby\/html\/css\r\nXTerminal colors not supported yet.\r\nYou can see sreenshot here\r\nhttp:\/\/my.jetscreenshot.com\/13962\/20130508-ea5i-286kb\r\n\r\ngithub repo: https:\/\/github.com\/piratarusso\/myvim_colors","install_details":"","5":"","first_name":"Pirata","6":"Pirata","last_name":"Russo","7":"Russo","releases":[{"0":"3795","vim_version":"7.0","1":"7.0","script_version":"3.0","2":"3.0","version_comment":"New colors, many improvements for code coloring.\r\nVImdiff coloring  supported.","3":"New colors, many improvements for code coloring.\r\nVImdiff coloring  supported.","package":"codepaper.vim","4":"codepaper.vim","src_id":"20064","5":"20064","creation_date":"1368004396","6":"1368004396"},{"0":"3795","vim_version":"7.3","1":"7.3","script_version":"1,0","2":"1,0","version_comment":"Initial upload","3":"Initial upload","package":"codepaper.vim","4":"codepaper.vim","src_id":"16785","5":"16785","creation_date":"1320252280","6":"1320252280"}]},"3794":{"script_id":"3794","0":"3794","script_name":"html-source-explorer","1":"html-source-explorer","script_type":"utility","2":"utility","summary":"The \"HTML Source Explorer\" plugin is meant to aid on the html source exploring.","3":"The \"HTML Source Explorer\" plugin is meant to aid on the html source exploring.","description":"The \"HTML Source Explorer\" plugin is meant to aid on the html source exploring.\r\nIt allows you to follow links by opening them on a new buffer on vim (the same\r\nway you can follow links on Mozilla Firefox\/Chrome view source).\r\n\r\nBy using <leader>fl inside \"\", '' or (), if it is a link (absolute, or\r\nrelative) the file will be open. \r\n\r\nIt works both on http:\/\/ urls and local files.\r\n\r\nThis plugin also includes a :Wget command which allows you to open a copy of\r\na remote file for editing in vim","4":"The \"HTML Source Explorer\" plugin is meant to aid on the html source exploring.\r\nIt allows you to follow links by opening them on a new buffer on vim (the same\r\nway you can follow links on Mozilla Firefox\/Chrome view source).\r\n\r\nBy using <leader>fl inside \"\", '' or (), if it is a link (absolute, or\r\nrelative) the file will be open. \r\n\r\nIt works both on http:\/\/ urls and local files.\r\n\r\nThis plugin also includes a :Wget command which allows you to open a copy of\r\na remote file for editing in vim","install_details":"Using pathogen, run command\r\n git clone git:\/\/github.com\/brunosilva\/html-source-explorer.git\r\non your bundle directory\r\n\r\nor unzip the attached file in your .vim directory","5":"Using pathogen, run command\r\n git clone git:\/\/github.com\/brunosilva\/html-source-explorer.git\r\non your bundle directory\r\n\r\nor unzip the attached file in your .vim directory","first_name":"Bruno","6":"Bruno","last_name":"Silva","7":"Silva","releases":[{"0":"3794","vim_version":"6.0","1":"6.0","script_version":"1.1","2":"1.1","version_comment":"FIX: url's relative to domain such as <link href='\/styles\/test.css'\/> weren't working\r\n\r\nadded support in filetype detection for url's with query string such as http:\/\/adomain.com\/styles\/main.css?rand=123456\r\n","3":"FIX: url's relative to domain such as <link href='\/styles\/test.css'\/> weren't working\r\n\r\nadded support in filetype detection for url's with query string such as http:\/\/adomain.com\/styles\/main.css?rand=123456\r\n","package":"brunosilva-html-source-explorer-566b190.zip","4":"brunosilva-html-source-explorer-566b190.zip","src_id":"16775","5":"16775","creation_date":"1320081016","6":"1320081016"},{"0":"3794","vim_version":"6.0","1":"6.0","script_version":"1","2":"1","version_comment":"Initial upload","3":"Initial upload","package":"brunosilva-html-source-explorer-288c9d3.zip","4":"brunosilva-html-source-explorer-288c9d3.zip","src_id":"16774","5":"16774","creation_date":"1320071410","6":"1320071410"}]},"3793":{"script_id":"3793","0":"3793","script_name":"desert-warm-256","1":"desert-warm-256","script_type":"color scheme","2":"color scheme","summary":"A slightly-modified desert theme, for 88- and 256-color xterms. ","3":"A slightly-modified desert theme, for 88- and 256-color xterms. ","description":"It's a color scheme for Vim, based on the \"desert\" color scheme by Hans\r\nFugal with a few small tweaks. The tweaks are try to make it looks a bit\r\nwarm and be more friendly for my eyes. Using the code from \"desert256\" to\r\nmake the gui highlight definitions also work with 88 and 256-color xterms.\r\n\r\nThe original \"desert\" theme is available as part of the vim distribution or\r\nat http:\/\/hans.fugal.net\/vim\/colors\/.\r\n\r\nThe \"desert256\" theme is available at\r\nhttp:\/\/www.vim.org\/scripts\/script.php?script_id=1243.\r\n\r\nThe real feature of this color scheme, with a wink to the \"inkpot\" theme, is\r\nthe programmatic approximation of the gui colors to the palettes of 88- and\r\n256- color xterms.  The functions that do this (folded away, for\r\nreadability) are calibrated to the colors used for Thomas E. Dickey's xterm\r\n(version 200), which is available at http:\/\/dickey.his.com\/xterm\/xterm.html.\r\n\r\nSupport rgb color names from rgb.txt file. Use a Ruby script to pre-parse\r\nrgb.txt then convert color names mapping to a Vim dictionary, store it in\r\ncolors\/rgb_colors file.\r\n\r\nConsider use this color scheme as infrastructure to create new color\r\nschemes. The benefit is your color schemes will looks nearly the same both\r\nin gVim and Vim running in 256- color xterms, without any additional effort.\r\n\r\nSome screenshots:\r\n\r\n* [desert-warm-256](http:\/\/dl.dropbox.com\/u\/3684228\/Screenshots\/desert-warm-256.png)\r\n* [desert-warm-256 in a 256 color terminal](http:\/\/dl.dropbox.com\/u\/3684228\/Screenshots\/desert-warm-256_terminal.png)\r\n* [original desert](http:\/\/dl.dropbox.com\/u\/3684228\/Screenshots\/desert.png)\r\n\r\nMaybe I'll not update it on vim.org, for updates check https:\/\/github.com\/rainux\/vim-desert-warm-256.","4":"It's a color scheme for Vim, based on the \"desert\" color scheme by Hans\r\nFugal with a few small tweaks. The tweaks are try to make it looks a bit\r\nwarm and be more friendly for my eyes. Using the code from \"desert256\" to\r\nmake the gui highlight definitions also work with 88 and 256-color xterms.\r\n\r\nThe original \"desert\" theme is available as part of the vim distribution or\r\nat http:\/\/hans.fugal.net\/vim\/colors\/.\r\n\r\nThe \"desert256\" theme is available at\r\nhttp:\/\/www.vim.org\/scripts\/script.php?script_id=1243.\r\n\r\nThe real feature of this color scheme, with a wink to the \"inkpot\" theme, is\r\nthe programmatic approximation of the gui colors to the palettes of 88- and\r\n256- color xterms.  The functions that do this (folded away, for\r\nreadability) are calibrated to the colors used for Thomas E. Dickey's xterm\r\n(version 200), which is available at http:\/\/dickey.his.com\/xterm\/xterm.html.\r\n\r\nSupport rgb color names from rgb.txt file. Use a Ruby script to pre-parse\r\nrgb.txt then convert color names mapping to a Vim dictionary, store it in\r\ncolors\/rgb_colors file.\r\n\r\nConsider use this color scheme as infrastructure to create new color\r\nschemes. The benefit is your color schemes will looks nearly the same both\r\nin gVim and Vim running in 256- color xterms, without any additional effort.\r\n\r\nSome screenshots:\r\n\r\n* [desert-warm-256](http:\/\/dl.dropbox.com\/u\/3684228\/Screenshots\/desert-warm-256.png)\r\n* [desert-warm-256 in a 256 color terminal](http:\/\/dl.dropbox.com\/u\/3684228\/Screenshots\/desert-warm-256_terminal.png)\r\n* [original desert](http:\/\/dl.dropbox.com\/u\/3684228\/Screenshots\/desert.png)\r\n\r\nMaybe I'll not update it on vim.org, for updates check https:\/\/github.com\/rainux\/vim-desert-warm-256.","install_details":"","5":"","first_name":"Rainux","6":"Rainux","last_name":"Luo","7":"Luo","releases":[{"0":"3793","vim_version":"7.0","1":"7.0","script_version":"0.2","2":"0.2","version_comment":"Rename to desert-warm-256","3":"Rename to desert-warm-256","package":"desert-warm-256.tar.gz","4":"desert-warm-256.tar.gz","src_id":"16771","5":"16771","creation_date":"1319940775","6":"1319940775"}]},"3792":{"script_id":"3792","0":"3792","script_name":"Tagma Buffer Manager","1":"Tagma Buffer Manager","script_type":"utility","2":"utility","summary":"Simple Buffer Manager","3":"Simple Buffer Manager","description":"Simple Buffer Manager similar to Mini Buffer Explorer and others. The\r\ninterface and code is kept as simple as possible. Several ideas are borrowed\r\nfrom Mini Buffer Explorer but all code is original.\r\n\r\nGitHub Home: https:\/\/github.com\/LStinson\/TagmaBufMgr\r\n\r\nFeatures:\r\n\r\nSmaller code base and as little code run on updates as possible. For example\r\nthe modification check that is performed after the |CursorHold| interval tries\r\nto bail out as fast as possible if there is no change to the modification\r\nstate.\r\n\r\nAs much information as possible is cached for each buffer. This allows some\r\nupdates to perform very few actions. Unfortunately there are rare cases where\r\nthis causes stale data to display in the Buffer Window. Using the Manager\r\nRefresh or switching to the Manager Window clears this data.\r\n\r\nAddition to the Right-Click PopUp menu. Menu items are added to toggle the\r\nManager Window, Refresh the Manager Window and switch to each buffer.\r\n\r\nTool tips for the buffers listed in the Manager Window.\r\nThe Tool Tips display the following lines:\r\n\t* Buffer name and number. Also flags the current buffer.\r\n\t* Full file name, truncated with \\'~\\' for home where possible.\r\n\t* The file type and format.\r\n\t* Notes if the buffer is Modified or Readonly\r\n\r\nPreserves the window history. This allows the command <C-W>p to work as\r\nexpected.\r\n\r\nI welcome any and all feedback. Please contact me at LoranceStinson AT Gmail....\r\nPlease be sure to put TagmaBufMgr in the subject so I know what you are emailing about.","4":"Simple Buffer Manager similar to Mini Buffer Explorer and others. The\r\ninterface and code is kept as simple as possible. Several ideas are borrowed\r\nfrom Mini Buffer Explorer but all code is original.\r\n\r\nGitHub Home: https:\/\/github.com\/LStinson\/TagmaBufMgr\r\n\r\nFeatures:\r\n\r\nSmaller code base and as little code run on updates as possible. For example\r\nthe modification check that is performed after the |CursorHold| interval tries\r\nto bail out as fast as possible if there is no change to the modification\r\nstate.\r\n\r\nAs much information as possible is cached for each buffer. This allows some\r\nupdates to perform very few actions. Unfortunately there are rare cases where\r\nthis causes stale data to display in the Buffer Window. Using the Manager\r\nRefresh or switching to the Manager Window clears this data.\r\n\r\nAddition to the Right-Click PopUp menu. Menu items are added to toggle the\r\nManager Window, Refresh the Manager Window and switch to each buffer.\r\n\r\nTool tips for the buffers listed in the Manager Window.\r\nThe Tool Tips display the following lines:\r\n\t* Buffer name and number. Also flags the current buffer.\r\n\t* Full file name, truncated with \\'~\\' for home where possible.\r\n\t* The file type and format.\r\n\t* Notes if the buffer is Modified or Readonly\r\n\r\nPreserves the window history. This allows the command <C-W>p to work as\r\nexpected.\r\n\r\nI welcome any and all feedback. Please contact me at LoranceStinson AT Gmail....\r\nPlease be sure to put TagmaBufMgr in the subject so I know what you are emailing about.","install_details":"Copy the files to your ~\/.vim or ~\/vimfiles directory.\r\nIf using a package manager like pathogen place the whole directory in the bundle directory.\r\n","5":"Copy the files to your ~\/.vim or ~\/vimfiles directory.\r\nIf using a package manager like pathogen place the whole directory in the bundle directory.\r\n","first_name":"Lorance","6":"Lorance","last_name":"Stinson","7":"Stinson","releases":[{"0":"3792","vim_version":"7.0","1":"7.0","script_version":"0.5","2":"0.5","version_comment":"Fixed several display and update bugs. Corrected an ongoing issue that caused the Buffer Manager Window to be the wrong size and not render if the directory changed.","3":"Fixed several display and update bugs. Corrected an ongoing issue that caused the Buffer Manager Window to be the wrong size and not render if the directory changed.","package":"TagmaBufMgr.zip","4":"TagmaBufMgr.zip","src_id":"17368","5":"17368","creation_date":"1328197635","6":"1328197635"},{"0":"3792","vim_version":"7.0","1":"7.0","script_version":"0.4","2":"0.4","version_comment":"Corrected a problem that caused buffers that should be hidden from being displayed. This affected plugins like Project, TagList and NERD_Tree.","3":"Corrected a problem that caused buffers that should be hidden from being displayed. This affected plugins like Project, TagList and NERD_Tree.","package":"TagmaBufMgr.zip","4":"TagmaBufMgr.zip","src_id":"17199","5":"17199","creation_date":"1326480354","6":"1326480354"}]},"3791":{"script_id":"3791","0":"3791","script_name":"vim-mnml","1":"vim-mnml","script_type":"syntax","2":"syntax","summary":"Syntax highlighting and indenting for mnml files","3":"Syntax highlighting and indenting for mnml files","description":"This package provides syntax highlighting support for the Mnml language (https:\/\/github.com\/thedjinn\/mnml). ","4":"This package provides syntax highlighting support for the Mnml language (https:\/\/github.com\/thedjinn\/mnml). ","install_details":"Extract the archive somewhere and copy the contents of the archive's vim-mnml directory into your .vim directory. Alternatively, if you use pathogen you can extract the archive in ~\/.vim\/bundle.","5":"Extract the archive somewhere and copy the contents of the archive's vim-mnml directory into your .vim directory. Alternatively, if you use pathogen you can extract the archive in ~\/.vim\/bundle.","first_name":"Emil","6":"Emil","last_name":"Loer","7":"Loer","releases":[{"0":"3791","vim_version":"7.0","1":"7.0","script_version":"1.0.0","2":"1.0.0","version_comment":"Initial upload","3":"Initial upload","package":"vim-mnml-1.0.0.tar.gz","4":"vim-mnml-1.0.0.tar.gz","src_id":"16767","5":"16767","creation_date":"1319895507","6":"1319895507"}]},"3790":{"script_id":"3790","0":"3790","script_name":"SonicTemplate.vim","1":"SonicTemplate.vim","script_type":"utility","2":"utility","summary":"Easy and high speed coding method","3":"Easy and high speed coding method","description":"\nvim plugins for hi-speed programming.\nIt use templates. To add some hints, and select template, you can see the\ncode to work.\n\nThere is a movie using sonictemplate.vim\nref: http:\/\/mattn.github.com\/sonictemplate-vim\n\nSource Repository.\nref: http:\/\/github.com\/mattn\/sonictemplate-vim\n\nIf you want to change templat directory, set:\n\n  let g:template_vim_template_dir = '\/path\/to\/your\/template\/directory'\n\nIf you want to write template for your self, see\n\n  :help sonictemplate\n","4":"\nvim plugins for hi-speed programming.\nIt use templates. To add some hints, and select template, you can see the\ncode to work.\n\nThere is a movie using sonictemplate.vim\nref: http:\/\/mattn.github.com\/sonictemplate-vim\n\nSource Repository.\nref: http:\/\/github.com\/mattn\/sonictemplate-vim\n\nIf you want to change templat directory, set:\n\n  let g:template_vim_template_dir = '\/path\/to\/your\/template\/directory'\n\nIf you want to write template for your self, see\n\n  :help sonictemplate\n","install_details":"\n# cd ~\/.vim\n# unzip sonictemplate-vim.zip\n\nor if you install pathogen.vim:\n\n# cd ~\/.vim\/bundle # or make directory\n# unzip \/path\/to\/sonictemplate-vim.zip\n\nif you get sources from repository:\n\n# cd ~\/.vim\/bundle # or make directory\n# git clone http:\/\/github.com\/mattn\/sonictemplate-vim.git\n","5":"\n# cd ~\/.vim\n# unzip sonictemplate-vim.zip\n\nor if you install pathogen.vim:\n\n# cd ~\/.vim\/bundle # or make directory\n# unzip \/path\/to\/sonictemplate-vim.zip\n\nif you get sources from repository:\n\n# cd ~\/.vim\/bundle # or make directory\n# git clone http:\/\/github.com\/mattn\/sonictemplate-vim.git\n","first_name":"Yasuhiro","6":"Yasuhiro","last_name":"Matsumoto","7":"Matsumoto","releases":[{"0":"3790","vim_version":"7.0","1":"7.0","script_version":"0.10","2":"0.10","version_comment":"This is an upgrade for SonicTemplate.vim:\n[add] added some templates.\n[add] {{_inline_}} support.\n[add] add global template '_'.\n[fix] fix bug that keep blank line.\n","3":"This is an upgrade for SonicTemplate.vim:\n[add] added some templates.\n[add] {{_inline_}} support.\n[add] add global template '_'.\n[fix] fix bug that keep blank line.\n","package":"sonictemplate-vim.zip","4":"sonictemplate-vim.zip","src_id":"18108","5":"18108","creation_date":"1339263083","6":"1339263083"},{"0":"3790","vim_version":"7.0","1":"7.0","script_version":"0.09","2":"0.09","version_comment":"This is an upgrade for SonicTemplate.vim:\n[add] added some templates.\n","3":"This is an upgrade for SonicTemplate.vim:\n[add] added some templates.\n","package":"sonictemplate-vim.zip","4":"sonictemplate-vim.zip","src_id":"17855","5":"17855","creation_date":"1335929889","6":"1335929889"},{"0":"3790","vim_version":"7.0","1":"7.0","script_version":"0.08","2":"0.08","version_comment":"This is an upgrade for SonicTemplate.vim:\n[fixed]  fixed error.\n","3":"This is an upgrade for SonicTemplate.vim:\n[fixed]  fixed error.\n","package":"sonictemplate-vim.zip","4":"sonictemplate-vim.zip","src_id":"17854","5":"17854","creation_date":"1335929791","6":"1335929791"},{"0":"3790","vim_version":"7.0","1":"7.0","script_version":"0.09","2":"0.09","version_comment":"This is an upgrade for SonicTemplate.vim:\n[fixed] be able to override default template.\n","3":"This is an upgrade for SonicTemplate.vim:\n[fixed] be able to override default template.\n","package":"sonictemplate-vim.zip","4":"sonictemplate-vim.zip","src_id":"17778","5":"17778","creation_date":"1334503979","6":"1334503979"},{"0":"3790","vim_version":"7.0","1":"7.0","script_version":"0.08","2":"0.08","version_comment":"This is an upgrade for SonicTemplate.vim:\n[fixed]  fixed error.\n","3":"This is an upgrade for SonicTemplate.vim:\n[fixed]  fixed error.\n","package":"sonictemplate-vim.zip","4":"sonictemplate-vim.zip","src_id":"16826","5":"16826","creation_date":"1320746696","6":"1320746696"},{"0":"3790","vim_version":"7.0","1":"7.0","script_version":"0.07","2":"0.07","version_comment":"This is an upgrade for SonicTemplate.vim:\n[fixed]  fixed key asign.\n","3":"This is an upgrade for SonicTemplate.vim:\n[fixed]  fixed key asign.\n","package":"sonictemplate-vim.zip","4":"sonictemplate-vim.zip","src_id":"16825","5":"16825","creation_date":"1320745990","6":"1320745990"},{"0":"3790","vim_version":"7.0","1":"7.0","script_version":"0.06","2":"0.06","version_comment":"This is an upgrade for SonicTemplate.vim:\n[fixed]  fixed _cursor_ behavior.\n[added]  some java templates.\n","3":"This is an upgrade for SonicTemplate.vim:\n[fixed]  fixed _cursor_ behavior.\n[added]  some java templates.\n","package":"sonictemplate-vim.zip","4":"sonictemplate-vim.zip","src_id":"16783","5":"16783","creation_date":"1320224014","6":"1320224014"},{"0":"3790","vim_version":"7.0","1":"7.0","script_version":"0.05","2":"0.05","version_comment":"This is an upgrade for SonicTemplate.vim:\n[fixed]  oops. dos2unix.\n","3":"This is an upgrade for SonicTemplate.vim:\n[fixed]  oops. dos2unix.\n","package":"sonictemplate-vim.zip","4":"sonictemplate-vim.zip","src_id":"16782","5":"16782","creation_date":"1320203828","6":"1320203828"},{"0":"3790","vim_version":"7.0","1":"7.0","script_version":"0.04","2":"0.04","version_comment":"This is an upgrade for SonicTemplate.vim:\n[fixed]  fixed names of javascript template.\n","3":"This is an upgrade for SonicTemplate.vim:\n[fixed]  fixed names of javascript template.\n","package":"sonictemplate-vim.zip","4":"sonictemplate-vim.zip","src_id":"16781","5":"16781","creation_date":"1320203390","6":"1320203390"},{"0":"3790","vim_version":"7.0","1":"7.0","script_version":"0.3","2":"0.3","version_comment":"This is an upgrade for SonicTemplate.vim:\n[fixed]  fix indent while insert mode.\n[added]  some java templates.\n","3":"This is an upgrade for SonicTemplate.vim:\n[fixed]  fix indent while insert mode.\n[added]  some java templates.\n","package":"sonictemplate-vim.zip","4":"sonictemplate-vim.zip","src_id":"16780","5":"16780","creation_date":"1320202598","6":"1320202598"},{"0":"3790","vim_version":"7.0","1":"7.0","script_version":"0.2","2":"0.2","version_comment":"This is an upgrade for SonicTemplate.vim:\n[fixed]  snip-file-read.pl\n","3":"This is an upgrade for SonicTemplate.vim:\n[fixed]  snip-file-read.pl\n","package":"sonictemplate-vim.zip","4":"sonictemplate-vim.zip","src_id":"16761","5":"16761","creation_date":"1319800201","6":"1319800201"},{"0":"3790","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"sonictemplate-vim.zip","4":"sonictemplate-vim.zip","src_id":"16760","5":"16760","creation_date":"1319798498","6":"1319798498"}]},"3786":{"script_id":"3786","0":"3786","script_name":"statline","1":"statline","script_type":"utility","2":"utility","summary":"Add useful information to the statusline","3":"Add useful information to the statusline","description":"Add useful information to the statusline like:\r\n\r\n - buffer number\r\n - file type\r\n - file encoding\r\n - syntax errors (integration with Syntastic)\r\n - indentation errors (mixed indentation, expand tab)\r\n - trailing white spaces\r\n - line number \/ total lines\r\n - scroll position\r\n - integration with Fugitive (git)\r\n - etc...\r\n\r\nProject repository and screenshots: https:\/\/github.com\/millermedeiros\/vim-statline","4":"Add useful information to the statusline like:\r\n\r\n - buffer number\r\n - file type\r\n - file encoding\r\n - syntax errors (integration with Syntastic)\r\n - indentation errors (mixed indentation, expand tab)\r\n - trailing white spaces\r\n - line number \/ total lines\r\n - scroll position\r\n - integration with Fugitive (git)\r\n - etc...\r\n\r\nProject repository and screenshots: https:\/\/github.com\/millermedeiros\/vim-statline","install_details":"Unzip the archive into your ~\/.vim directory.\r\nThat should put statline.vim in ~\/.vim\/plugin and statline.txt in ~\/.vim\/doc. ","5":"Unzip the archive into your ~\/.vim directory.\r\nThat should put statline.vim in ~\/.vim\/plugin and statline.txt in ~\/.vim\/doc. ","first_name":"Miller","6":"Miller","last_name":"Medeiros","7":"Medeiros","releases":[{"0":"3786","vim_version":"7.0","1":"7.0","script_version":"0.2.1","2":"0.2.1","version_comment":"Initial upload","3":"Initial upload","package":"vim-statline-v0.2.1.zip","4":"vim-statline-v0.2.1.zip","src_id":"16735","5":"16735","creation_date":"1319491436","6":"1319491436"}]},"3785":{"script_id":"3785","0":"3785","script_name":"VIM Metaprogramming","1":"VIM Metaprogramming","script_type":"utility","2":"utility","summary":"Metaprogramming in VIM scripts","3":"Metaprogramming in VIM scripts","description":"VIM scripts can edit themselves, thus we could 'edit', '?', 's', 'source' scripts to create some domain specific language like :\r\n\r\nsilent! 0,$s\/\\vFunc\\[(.+)\\]\\{(.+)\\}\/fun!\\1\\r\\2\\rendfun\\r\/g\r\nFunc[Test()]{return 3}\r\n\r\nNotice the function is considered one-liner. I hope it is helpful.","4":"VIM scripts can edit themselves, thus we could 'edit', '?', 's', 'source' scripts to create some domain specific language like :\r\n\r\nsilent! 0,$s\/\\vFunc\\[(.+)\\]\\{(.+)\\}\/fun!\\1\\r\\2\\rendfun\\r\/g\r\nFunc[Test()]{return 3}\r\n\r\nNotice the function is considered one-liner. I hope it is helpful.","install_details":"just \"source metarc.vim\"","5":"just \"source metarc.vim\"","first_name":"Sanae","6":"Sanae","last_name":"Kotiya","7":"Kotiya","releases":[{"0":"3785","vim_version":"7.2","1":"7.2","script_version":"0.01","2":"0.01","version_comment":"Initial upload","3":"Initial upload","package":"metarc.vim","4":"metarc.vim","src_id":"16728","5":"16728","creation_date":"1319379779","6":"1319379779"}]},"3783":{"script_id":"3783","0":"3783","script_name":"vim-json-bundle","1":"vim-json-bundle","script_type":"ftplugin","2":"ftplugin","summary":"Pathogen friendly file type plugin bundle for json files","3":"Pathogen friendly file type plugin bundle for json files","description":"Pathogen friendly packaging of vim-json from Jeroen Ruigrok van der Werven vimscript #1945.\r\n\r\nFork from https:\/\/github.com\/leshill\/vim-json","4":"Pathogen friendly packaging of vim-json from Jeroen Ruigrok van der Werven vimscript #1945.\r\n\r\nFork from https:\/\/github.com\/leshill\/vim-json","install_details":"1. Extract the package or clone the git repository to ~\/.vim\/bundle\r\n\r\ncd ~\/.vim\/bundle\r\ngit clone https:\/\/github.com\/rogerz\/vim-json\r\n\r\n2. Load the plugin via pathogen.\r\n\r\nRefer to pathogen vimscript #2332 for details.","5":"1. Extract the package or clone the git repository to ~\/.vim\/bundle\r\n\r\ncd ~\/.vim\/bundle\r\ngit clone https:\/\/github.com\/rogerz\/vim-json\r\n\r\n2. Load the plugin via pathogen.\r\n\r\nRefer to pathogen vimscript #2332 for details.","first_name":"Rogerz","6":"Rogerz","last_name":"Zhang","7":"Zhang","releases":[{"0":"3783","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"rogerz-vim-json-4cc6168.tar.gz","4":"rogerz-vim-json-4cc6168.tar.gz","src_id":"16726","5":"16726","creation_date":"1319357260","6":"1319357260"}]},"3782":{"script_id":"3782","0":"3782","script_name":"Python Syntax","1":"Python Syntax","script_type":"syntax","2":"syntax","summary":"Revised version based on Ian McCracken's version","3":"Revised version based on Ian McCracken's version","description":"To make it feels more like a textmate environment","4":"To make it feels more like a textmate environment","install_details":"","5":"","first_name":"Vincent","6":"Vincent","last_name":"Chen","7":"Chen","releases":[{"0":"3782","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"python.vim","4":"python.vim","src_id":"16721","5":"16721","creation_date":"1319259653","6":"1319259653"}]},"3781":{"script_id":"3781","0":"3781","script_name":"Twilight for python","1":"Twilight for python","script_type":"color scheme","2":"color scheme","summary":"Twilight mod based on famous Jellybeans scheme","3":"Twilight mod based on famous Jellybeans scheme","description":"The color scheme tries to replicate the same theme from Textmate, especially for Python.\r\n\r\nIt is modified based on famous Jellybeans scheme.\r\n\r\nTo fully utilize this scheme, a enhanced python.vim syntax is required, which can be found at\r\n\r\nhttp:\/\/www.vim.org\/scripts\/script.php?script_id=3782","4":"The color scheme tries to replicate the same theme from Textmate, especially for Python.\r\n\r\nIt is modified based on famous Jellybeans scheme.\r\n\r\nTo fully utilize this scheme, a enhanced python.vim syntax is required, which can be found at\r\n\r\nhttp:\/\/www.vim.org\/scripts\/script.php?script_id=3782","install_details":"It's better in put the following in .vimrc\r\n\r\nif has(\"eval\")\r\n  let python_highlight_all = 1\r\n  let python_slow_sync = 1\r\nendif","5":"It's better in put the following in .vimrc\r\n\r\nif has(\"eval\")\r\n  let python_highlight_all = 1\r\n  let python_slow_sync = 1\r\nendif","first_name":"Vincent","6":"Vincent","last_name":"Chen","7":"Chen","releases":[{"0":"3781","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"twilight.vim","4":"twilight.vim","src_id":"16720","5":"16720","creation_date":"1319259389","6":"1319259389"}]},"3780":{"script_id":"3780","0":"3780","script_name":"indentfolds","1":"indentfolds","script_type":"utility","2":"utility","summary":"Indentation-level based folds with a twist","3":"Indentation-level based folds with a twist","description":"When I write a longer text, I tend to use a top-down approach. I begin \r\nwith writing down the headings. I then outline each section. Next, I write \r\ndown keywords for each paragraph etc. At each step, I increase the \r\nindentation level (multiples of 'shiftwidth', see also 'fold-indent').\r\n\r\nThis plugin help maintaining an overview of the document by setting a \r\nparagraph's 'foldlevel' based on its indentation level -- see \r\n|:Indentfolds|. Other than vim's own 'fold-indent' method, any \r\nindentation level can be assigned as the top fold level. E.g. text with \r\na prefix of 16 whitespace characters can be defined as level 1, 8 and 24 \r\nwhitespace characters would then be at level 2 etc. By setting foldlevel=1, \r\nonly text at that indentation level is displayed.\r\n\r\nThis plugin also provides a helper-command to comment out or delete all \r\nlines at higher fold levels -- see |:IndentfoldsComment|.\r\n\r\nUsers can also use key maps (default: <tab>, <s-tab>) to cycle through \r\nindentation levels.\r\n","4":"When I write a longer text, I tend to use a top-down approach. I begin \r\nwith writing down the headings. I then outline each section. Next, I write \r\ndown keywords for each paragraph etc. At each step, I increase the \r\nindentation level (multiples of 'shiftwidth', see also 'fold-indent').\r\n\r\nThis plugin help maintaining an overview of the document by setting a \r\nparagraph's 'foldlevel' based on its indentation level -- see \r\n|:Indentfolds|. Other than vim's own 'fold-indent' method, any \r\nindentation level can be assigned as the top fold level. E.g. text with \r\na prefix of 16 whitespace characters can be defined as level 1, 8 and 24 \r\nwhitespace characters would then be at level 2 etc. By setting foldlevel=1, \r\nonly text at that indentation level is displayed.\r\n\r\nThis plugin also provides a helper-command to comment out or delete all \r\nlines at higher fold levels -- see |:IndentfoldsComment|.\r\n\r\nUsers can also use key maps (default: <tab>, <s-tab>) to cycle through \r\nindentation levels.\r\n","install_details":"In order to install the vba, open the vba file in VIM and type: >\r\n\r\n    :so %\r\n\r\nSee :help vimball for details.\r\n\r\nAlso available via git: http:\/\/github.com\/tomtom\/indentfolds_vim\/\r\n","5":"In order to install the vba, open the vba file in VIM and type: >\r\n\r\n    :so %\r\n\r\nSee :help vimball for details.\r\n\r\nAlso available via git: http:\/\/github.com\/tomtom\/indentfolds_vim\/\r\n","first_name":"Tom","6":"Tom","last_name":"Link","7":"Link","releases":[{"0":"3780","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"indentfolds.vba","4":"indentfolds.vba","src_id":"16714","5":"16714","creation_date":"1319210289","6":"1319210289"}]},"3779":{"script_id":"3779","0":"3779","script_name":"mango.vim","1":"mango.vim","script_type":"color scheme","2":"color scheme","summary":"Pretty syntax highlighting tailored for JavaScript and Coffeescript","3":"Pretty syntax highlighting tailored for JavaScript and Coffeescript","description":"Made for web development, mango works well with Python, PHP, JavaScript, Coffeescript, CSS and HTML.\r\n\r\nFollow the project, report any issues or feature requests here:\r\n\r\nhttps:\/\/github.com\/goatslacker\/mango.vim\r\n","4":"Made for web development, mango works well with Python, PHP, JavaScript, Coffeescript, CSS and HTML.\r\n\r\nFollow the project, report any issues or feature requests here:\r\n\r\nhttps:\/\/github.com\/goatslacker\/mango.vim\r\n","install_details":"\" syntax highlighting\r\nsyntax on\r\nset t_Co=256\r\ncolor mango","5":"\" syntax highlighting\r\nsyntax on\r\nset t_Co=256\r\ncolor mango","first_name":"Josh","6":"Josh","last_name":"Perez","7":"Perez","releases":[{"0":"3779","vim_version":"7.0","1":"7.0","script_version":"1.4.5","2":"1.4.5","version_comment":"Light theme + Dark theme","3":"Light theme + Dark theme","package":"mango.vim","4":"mango.vim","src_id":"17530","5":"17530","creation_date":"1330251954","6":"1330251954"},{"0":"3779","vim_version":"7.0","1":"7.0","script_version":"1.2","2":"1.2","version_comment":"Removes `highlight clear` so it plays nice with other vim plugin\\'s like vim-powerline","3":"Removes `highlight clear` so it plays nice with other vim plugin\\'s like vim-powerline","package":"mango.vim","4":"mango.vim","src_id":"17202","5":"17202","creation_date":"1326526393","6":"1326526393"},{"0":"3779","vim_version":"7.0","1":"7.0","script_version":"1.1","2":"1.1","version_comment":"Makes script self-contained. No longer is set t_Co=256 required.","3":"Makes script self-contained. No longer is set t_Co=256 required.","package":"mango.vim","4":"mango.vim","src_id":"16779","5":"16779","creation_date":"1320165779","6":"1320165779"},{"0":"3779","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"mango.vim","4":"mango.vim","src_id":"16712","5":"16712","creation_date":"1319136358","6":"1319136358"}]},"3778":{"script_id":"3778","0":"3778","script_name":"utags","1":"utags","script_type":"utility","2":"utility","summary":"Find usage of a word (tag) in the project.","3":"Find usage of a word (tag) in the project.","description":"UTAGS\r\n\r\nWHAT IS IT.\r\n\r\nUtags provides an ability to search for usage of a C\/C++\/Python\/Perl function, a type name, a class method\/member, a variable or any other word in a source code of a project. It's like a fast, convenient grep by the whole word. Search is performed from vim by a hot-key when cursor is on the word you want to find. It works quickly since utags uses a beforehand generated index.\r\n\r\nHOW TO USE IT.\r\n\r\nFirst of all you should generate an index. It's done by the following command:\r\ncd your_proj_path && utags -g . > .utags\r\nIt can take a while for big projects.\r\nFurther when you edit a file from the project and current folder is a project subfolder and the vim cursor is on the word you want to find in the project, press and release one by one two keys: <\\> and <U> (without delay between pressing, quite quickly; letter U is in uppercase here, so press it holding Shift). If you have done everything right, vim opens a window in the top with a list of results.\r\n\r\nA couple of other hot-keys limit the search area:\r\n<\\>, <D> - search only in the C\/C++ headers.\r\n<\\>, <P> - search only in the current directory.\r\nLetters D and P are in upper case here too, so press them with Shift held.\r\n\r\nKey <\\> is defined by vim configuration and can be changed, for example, on a comma by adding the following line into $HOME\/.vimrc:\r\n\tlet mapleader = \",\"\r\n\r\nGOING THROUGH RESULTS.\r\n\r\nYou may select items from the result list using mouse double-click or using a keyboard (arrows and Enter). In order to move vim cursor in the bottom window using keyboard press <Ctrl>+<w>, <Down>, and to return to the top window: <Ctrl>+<w>, <Up>.\r\n\r\nYou also may assign hot-keys to go thru the result list faster:\r\nmap <F6> :copen<CR>\r\nmap <F7> :cprevious<CR>\r\nmap <F8> :cnext<CR>\r\n\r\nThese lines should be added to $HOME\/.vimrc\r\n\r\nIf you have any question about this tool or know how to enhance it, please email me at luinnar(at)yandex.ru\r\n\r\nHave a fun!\r\n\r\nIn English: http:\/\/luinnar.narod.ru\/tools\/utags\/index-en.html\r\nНа русском: http:\/\/luinnar.narod.ru\/tools\/utags\/","4":"UTAGS\r\n\r\nWHAT IS IT.\r\n\r\nUtags provides an ability to search for usage of a C\/C++\/Python\/Perl function, a type name, a class method\/member, a variable or any other word in a source code of a project. It's like a fast, convenient grep by the whole word. Search is performed from vim by a hot-key when cursor is on the word you want to find. It works quickly since utags uses a beforehand generated index.\r\n\r\nHOW TO USE IT.\r\n\r\nFirst of all you should generate an index. It's done by the following command:\r\ncd your_proj_path && utags -g . > .utags\r\nIt can take a while for big projects.\r\nFurther when you edit a file from the project and current folder is a project subfolder and the vim cursor is on the word you want to find in the project, press and release one by one two keys: <\\> and <U> (without delay between pressing, quite quickly; letter U is in uppercase here, so press it holding Shift). If you have done everything right, vim opens a window in the top with a list of results.\r\n\r\nA couple of other hot-keys limit the search area:\r\n<\\>, <D> - search only in the C\/C++ headers.\r\n<\\>, <P> - search only in the current directory.\r\nLetters D and P are in upper case here too, so press them with Shift held.\r\n\r\nKey <\\> is defined by vim configuration and can be changed, for example, on a comma by adding the following line into $HOME\/.vimrc:\r\n\tlet mapleader = \",\"\r\n\r\nGOING THROUGH RESULTS.\r\n\r\nYou may select items from the result list using mouse double-click or using a keyboard (arrows and Enter). In order to move vim cursor in the bottom window using keyboard press <Ctrl>+<w>, <Down>, and to return to the top window: <Ctrl>+<w>, <Up>.\r\n\r\nYou also may assign hot-keys to go thru the result list faster:\r\nmap <F6> :copen<CR>\r\nmap <F7> :cprevious<CR>\r\nmap <F8> :cnext<CR>\r\n\r\nThese lines should be added to $HOME\/.vimrc\r\n\r\nIf you have any question about this tool or know how to enhance it, please email me at luinnar(at)yandex.ru\r\n\r\nHave a fun!\r\n\r\nIn English: http:\/\/luinnar.narod.ru\/tools\/utags\/index-en.html\r\nНа русском: http:\/\/luinnar.narod.ru\/tools\/utags\/","install_details":"Copy utags and find_above into any your folder which is already in the $PATH, or if there is no such folder, then create one and add it to the $PATH.\r\n\r\nfindusage.vim \u00e2\u0080\u0093 is a plugin for vim, copy it into the folder $HOME\/.vim\/plugin\/ (if this directory doesn't exist create it!).","5":"Copy utags and find_above into any your folder which is already in the $PATH, or if there is no such folder, then create one and add it to the $PATH.\r\n\r\nfindusage.vim \u00e2\u0080\u0093 is a plugin for vim, copy it into the folder $HOME\/.vim\/plugin\/ (if this directory doesn't exist create it!).","first_name":"Luinnar","6":"Luinnar","last_name":".","7":".","releases":[{"0":"3778","vim_version":"6.0","1":"6.0","script_version":"1.2","2":"1.2","version_comment":"Supported new file types: *.cc, *.hh, *.cxx and *.hxx.\r\n\r\nAdded an option to findusage.vim plugin:\r\ng:FindUsage_EqualFilesFilter","3":"Supported new file types: *.cc, *.hh, *.cxx and *.hxx.\r\n\r\nAdded an option to findusage.vim plugin:\r\ng:FindUsage_EqualFilesFilter","package":"utags-1.2.tbz","4":"utags-1.2.tbz","src_id":"18981","5":"18981","creation_date":"1353081528","6":"1353081528"},{"0":"3778","vim_version":"6.0","1":"6.0","script_version":"1.1","2":"1.1","version_comment":"Fixed search in the current folder.","3":"Fixed search in the current folder.","package":"utags-1.1.tbz","4":"utags-1.1.tbz","src_id":"18864","5":"18864","creation_date":"1350989469","6":"1350989469"},{"0":"3778","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"utags.tbz","4":"utags.tbz","src_id":"16710","5":"16710","creation_date":"1319119752","6":"1319119752"}]},"3777":{"script_id":"3777","0":"3777","script_name":"RST Tables (CJK)","1":"RST Tables (CJK)","script_type":"ftplugin","2":"ftplugin","summary":"Allows to create and edit restructuredText tables easily (CJK)","3":"Allows to create and edit restructuredText tables easily (CJK)","description":"Original plugin: vimscript #3041\r\n\r\ntwo new commands:\r\n\r\n    ,,c  ->  Creates a new restructuredText table.\r\n    ,,f  ->  Fix table columns in a table. \r\n\r\nFor example, if you have a paragraph with data like this:\r\n\r\nhttp:\/\/du1abadd.org\/images\/2011\/origin.png\r\n\r\nyou can press \",,c\" to create a simple table: \r\n\r\nhttp:\/\/du1abadd.org\/images\/2011\/create.png\r\n\r\nNow, if you change the table content, for example adding characters\r\nto the first content row. \r\n\r\nhttp:\/\/du1abadd.org\/images\/2011\/change.png\r\n\r\nyou need to fix the columns widths. So, press \",,f\" and you will gets: \r\n\r\nhttp:\/\/du1abadd.org\/images\/2011\/result.png\r\n","4":"Original plugin: vimscript #3041\r\n\r\ntwo new commands:\r\n\r\n    ,,c  ->  Creates a new restructuredText table.\r\n    ,,f  ->  Fix table columns in a table. \r\n\r\nFor example, if you have a paragraph with data like this:\r\n\r\nhttp:\/\/du1abadd.org\/images\/2011\/origin.png\r\n\r\nyou can press \",,c\" to create a simple table: \r\n\r\nhttp:\/\/du1abadd.org\/images\/2011\/create.png\r\n\r\nNow, if you change the table content, for example adding characters\r\nto the first content row. \r\n\r\nhttp:\/\/du1abadd.org\/images\/2011\/change.png\r\n\r\nyou need to fix the columns widths. So, press \",,f\" and you will gets: \r\n\r\nhttp:\/\/du1abadd.org\/images\/2011\/result.png\r\n","install_details":"Place plugin in .vim\/ftplugin folder. ","5":"Place plugin in .vim\/ftplugin folder. ","first_name":"Vern","6":"Vern","last_name":"Sun","7":"Sun","releases":[{"0":"3777","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"rst.vim","4":"rst.vim","src_id":"16708","5":"16708","creation_date":"1319043171","6":"1319043171"}]},"3776":{"script_id":"3776","0":"3776","script_name":"todotxt.vim","1":"todotxt.vim","script_type":"syntax","2":"syntax","summary":"Vim does TODO-lists","3":"Vim does TODO-lists","description":"I've tried countless TODO systems but somehow I always end up back with my trusted TODO.txt. Now I've decided to spice it up a bit.","4":"I've tried countless TODO systems but somehow I always end up back with my trusted TODO.txt. Now I've decided to spice it up a bit.","install_details":"","5":"","first_name":"Christoffer","6":"Christoffer","last_name":"Lejdborg","7":"Lejdborg","releases":[{"0":"3776","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"Lejdborg-todotxt.vim-69fbf57.zip","4":"Lejdborg-todotxt.vim-69fbf57.zip","src_id":"16704","5":"16704","creation_date":"1319026762","6":"1319026762"}]},"3775":{"script_id":"3775","0":"3775","script_name":"wiki.vim","1":"wiki.vim","script_type":"utility","2":"utility","summary":"Use curl to get and post pages in mediawiki sites using basic auth","3":"Use curl to get and post pages in mediawiki sites using basic auth","description":"MediaWiki\\\\\\'s html editor is not vim.\r\n\r\nThis script uses mediawiki\\\\\\'s api.php to pull a page into the editor when opening a new file, and post the entire page back when writing.  It requires curl in your path.","4":"MediaWiki\\\\\\'s html editor is not vim.\r\n\r\nThis script uses mediawiki\\\\\\'s api.php to pull a page into the editor when opening a new file, and post the entire page back when writing.  It requires curl in your path.","install_details":"Set s:user to a username, and s:pass to a password..","5":"Set s:user to a username, and s:pass to a password..","first_name":"Benjamin","6":"Benjamin","last_name":"Coddington","7":"Coddington","releases":[{"0":"3775","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"wiki.vim","4":"wiki.vim","src_id":"16696","5":"16696","creation_date":"1318959676","6":"1318959676"}]},"3774":{"script_id":"3774","0":"3774","script_name":"abbott.vim","1":"abbott.vim","script_type":"color scheme","2":"color scheme","summary":"A warm, dark color scheme for prose and code, with pastels and pretty greens","3":"A warm, dark color scheme for prose and code, with pastels and pretty greens","description":"[This color scheme is developed on GitHub: https:\/\/github.com\/bcat\/abbott.vim.]\r\n\r\n`abbott.vim` is a warm, dark color scheme for prose and code, with pastels and\r\npretty greens. It's primarily designed for editing files with a lot of plain\r\ntext (i.e., Markdown or TeX documents), but it handles executable code well too.\r\nThis color scheme draws inspiration from several sources, including memories of\r\nlate nights working mathematical proofs\u00e2\u0080\u0094it's named after Stephen Abbott's\r\n_Understanding Analysis_, which I was studying at the time\u00e2\u0080\u0094and drinking copious\r\nquantities of Mountain Dew.\r\n\r\n## Screenshots\r\n\r\nBecause hey, it's a color scheme! That's what you really want to see, right?\r\n\r\nabbott.vim 2.1: Vimscript (https:\/\/i.imgur.com\/TpuJttd.png)\r\n\r\nabbott.vim 2.1: Python (https:\/\/i.imgur.com\/PSZu7oU.png)\r\n\r\nabbott.vim 2.1: Markdown (https:\/\/i.imgur.com\/MQA3MCi.png)\r\n\r\nabbott.vim 2.1: C (https:\/\/i.imgur.com\/rSJ2Hs4.png)\r\n\r\nCompare to screenshots from older versions (https:\/\/imgur.com\/a\/7woPY) to see\r\nhow this color scheme has evolved.\r\n\r\n## Colors\r\n\r\nThis color scheme uses a 16-color palette that maps nicely onto the ANSI color\r\npalette, plus a couple of additional colors for terminals that allow them:\r\n\r\nhttps:\/\/i.imgur.com\/8p1dEP3.png\r\n\r\n`abbott.vim` looks best where RGB colors are supported, either in the gVim GUI\r\nor in a terminal supporting true colors (https:\/\/github.com\/termstandard\/colors)\r\nwith Vim's `termguicolors` option enabled. You can use this color scheme in a\r\n256-color terminal instead, if you like, and you'll get the following\r\napproximated palette:\r\n\r\nhttps:\/\/i.imgur.com\/ZkbmjkR.png\r\n\r\nThe colors are pretty close, but the brown and olive colors are replaced with\r\nshades of gray since the XTerm 256-color palette doesn't have many shades of\r\nbrown to choose from.\r\n\r\n## Features\r\n\r\n* This color scheme is a dark theme that attempts to avoid excessive text\r\n  contrast. Plain text is light green on dark brown to be easy on the eyes after\r\n  long hours. Additionally, care has been taken to ensure the color palette\r\n  looks decent in \"night light\" mode (e.g., with f.lux (https:\/\/justgetflux.com\/) or\r\n  other blue light filters enabled).\r\n* This color scheme supports all highlight groups in Vim 8.2, as well as the\r\n  Better Whitespace (https:\/\/github.com\/ntpeters\/vim-better-whitespace) plugin.\r\n* Additional plugin-specific highlight groups may be added in the future.\r\n\r\n## Options\r\n\r\nThis color scheme offers some additional features that are disabled by default\r\nbecause they may not interact well with all terminals or with other Vim color\r\nschemes. These features can be enabled if the user likes to live dangerously.\r\n\r\n```vim\r\nlet g:abbott_force_16_colors = 1\r\n```\r\n\r\nIf requested by the user, restrain ourselves to only the 16 standard ANSI\r\nterminal colors even if Vim thinks the terminal supports 256 colors. This allows\r\nthe user to configure their terminal emulator to use the 16 colors defined above\r\nfor its ANSI palette, allowing exact color matches rather than 256-color\r\napproximations even in terminals that don't support true color.\r\n\r\n```vim\r\nlet g:abbott_set_term_ansi_colors = 1\r\n```\r\n\r\nIf requested by the user, use our standard 16-color palette for the embedded\r\nterminal. We don't do this by default because unlike the highlight groups above,\r\nthis isn't automatically cleared when another color scheme is selected.\r\n\r\n```vim\r\nlet g:abbott_term_use_italics = 1\r\n```\r\n\r\nBy default, Italics in the terminal are disabled since the default terminfo for\r\nGNU Screen renders italics as reverse video, and since other terminals like\r\nhterm may show artifacts when rendering italics.\r\n\r\n```vim\r\nlet g:abbott_term_set_underline_color = 1\r\n```\r\n\r\nBy default, the foreground text color will be replaced by the underline color in\r\nthe terminal since if the terminal does not support setting the underline color\r\nseparately, that color will be completely invisible.\r\n\r\n```vim\r\nlet g:abbott_term_use_undercurl = 1\r\n```\r\n\r\nBy default, underlined text will be used in the terminal in place of undercurl,\r\nbecause some terminfo entries cause Vim to think the terminal supports undercurl\r\nwhen it really does not (https:\/\/github.com\/vim\/vim\/issues\/3471).\r\n\r\n## Contributing\r\n\r\nThis color scheme is licensed under the ISC license. Folks are free to port this\r\ncolor scheme to other editors and environments if they would like, and are\r\nencouraged to submit fixes back to the canonical `abbott.vim` repository if\r\npossible. Likewise, patches to support new Vim features are always welcome.\r\nConsult the changelog\r\n(https:\/\/github.com\/bcat\/abbott.vim\/blob\/master\/CHANGES.md) for version history.","4":"[This color scheme is developed on GitHub: https:\/\/github.com\/bcat\/abbott.vim.]\r\n\r\n`abbott.vim` is a warm, dark color scheme for prose and code, with pastels and\r\npretty greens. It's primarily designed for editing files with a lot of plain\r\ntext (i.e., Markdown or TeX documents), but it handles executable code well too.\r\nThis color scheme draws inspiration from several sources, including memories of\r\nlate nights working mathematical proofs\u00e2\u0080\u0094it's named after Stephen Abbott's\r\n_Understanding Analysis_, which I was studying at the time\u00e2\u0080\u0094and drinking copious\r\nquantities of Mountain Dew.\r\n\r\n## Screenshots\r\n\r\nBecause hey, it's a color scheme! That's what you really want to see, right?\r\n\r\nabbott.vim 2.1: Vimscript (https:\/\/i.imgur.com\/TpuJttd.png)\r\n\r\nabbott.vim 2.1: Python (https:\/\/i.imgur.com\/PSZu7oU.png)\r\n\r\nabbott.vim 2.1: Markdown (https:\/\/i.imgur.com\/MQA3MCi.png)\r\n\r\nabbott.vim 2.1: C (https:\/\/i.imgur.com\/rSJ2Hs4.png)\r\n\r\nCompare to screenshots from older versions (https:\/\/imgur.com\/a\/7woPY) to see\r\nhow this color scheme has evolved.\r\n\r\n## Colors\r\n\r\nThis color scheme uses a 16-color palette that maps nicely onto the ANSI color\r\npalette, plus a couple of additional colors for terminals that allow them:\r\n\r\nhttps:\/\/i.imgur.com\/8p1dEP3.png\r\n\r\n`abbott.vim` looks best where RGB colors are supported, either in the gVim GUI\r\nor in a terminal supporting true colors (https:\/\/github.com\/termstandard\/colors)\r\nwith Vim's `termguicolors` option enabled. You can use this color scheme in a\r\n256-color terminal instead, if you like, and you'll get the following\r\napproximated palette:\r\n\r\nhttps:\/\/i.imgur.com\/ZkbmjkR.png\r\n\r\nThe colors are pretty close, but the brown and olive colors are replaced with\r\nshades of gray since the XTerm 256-color palette doesn't have many shades of\r\nbrown to choose from.\r\n\r\n## Features\r\n\r\n* This color scheme is a dark theme that attempts to avoid excessive text\r\n  contrast. Plain text is light green on dark brown to be easy on the eyes after\r\n  long hours. Additionally, care has been taken to ensure the color palette\r\n  looks decent in \"night light\" mode (e.g., with f.lux (https:\/\/justgetflux.com\/) or\r\n  other blue light filters enabled).\r\n* This color scheme supports all highlight groups in Vim 8.2, as well as the\r\n  Better Whitespace (https:\/\/github.com\/ntpeters\/vim-better-whitespace) plugin.\r\n* Additional plugin-specific highlight groups may be added in the future.\r\n\r\n## Options\r\n\r\nThis color scheme offers some additional features that are disabled by default\r\nbecause they may not interact well with all terminals or with other Vim color\r\nschemes. These features can be enabled if the user likes to live dangerously.\r\n\r\n```vim\r\nlet g:abbott_force_16_colors = 1\r\n```\r\n\r\nIf requested by the user, restrain ourselves to only the 16 standard ANSI\r\nterminal colors even if Vim thinks the terminal supports 256 colors. This allows\r\nthe user to configure their terminal emulator to use the 16 colors defined above\r\nfor its ANSI palette, allowing exact color matches rather than 256-color\r\napproximations even in terminals that don't support true color.\r\n\r\n```vim\r\nlet g:abbott_set_term_ansi_colors = 1\r\n```\r\n\r\nIf requested by the user, use our standard 16-color palette for the embedded\r\nterminal. We don't do this by default because unlike the highlight groups above,\r\nthis isn't automatically cleared when another color scheme is selected.\r\n\r\n```vim\r\nlet g:abbott_term_use_italics = 1\r\n```\r\n\r\nBy default, Italics in the terminal are disabled since the default terminfo for\r\nGNU Screen renders italics as reverse video, and since other terminals like\r\nhterm may show artifacts when rendering italics.\r\n\r\n```vim\r\nlet g:abbott_term_set_underline_color = 1\r\n```\r\n\r\nBy default, the foreground text color will be replaced by the underline color in\r\nthe terminal since if the terminal does not support setting the underline color\r\nseparately, that color will be completely invisible.\r\n\r\n```vim\r\nlet g:abbott_term_use_undercurl = 1\r\n```\r\n\r\nBy default, underlined text will be used in the terminal in place of undercurl,\r\nbecause some terminfo entries cause Vim to think the terminal supports undercurl\r\nwhen it really does not (https:\/\/github.com\/vim\/vim\/issues\/3471).\r\n\r\n## Contributing\r\n\r\nThis color scheme is licensed under the ISC license. Folks are free to port this\r\ncolor scheme to other editors and environments if they would like, and are\r\nencouraged to submit fixes back to the canonical `abbott.vim` repository if\r\npossible. Likewise, patches to support new Vim features are always welcome.\r\nConsult the changelog\r\n(https:\/\/github.com\/bcat\/abbott.vim\/blob\/master\/CHANGES.md) for version history.","install_details":"* Preferred: Check out the Git repository (as a submodule if you already keep your Vim configuration in Git) and use your favorite plugin manager to install it.\r\n* Alternate: Download the tarball from this page or from the Git repository, then copy abbott.vim to your ~\/.vim\/colors directory.","5":"* Preferred: Check out the Git repository (as a submodule if you already keep your Vim configuration in Git) and use your favorite plugin manager to install it.\r\n* Alternate: Download the tarball from this page or from the Git repository, then copy abbott.vim to your ~\/.vim\/colors directory.","first_name":"Jonathan","6":"Jonathan","last_name":"Rascher","7":"Rascher","releases":[{"0":"3774","vim_version":"7.0","1":"7.0","script_version":"v2.1","2":"v2.1","version_comment":"* **Added chocolate and dark olive colors on top of core 16-color palette.**\r\n* Adjusted brown shades to reduce excessive contrast.\r\n* Fixed an incorrect ANSI color assignment.\r\n* Tweaked a few color assignments for greater clarity and fewer distractions.\r\n* Improved highlighting of diff files.\r\n* Switched visual selection from dark-on-light to light-on-dark colors.","3":"* **Added chocolate and dark olive colors on top of core 16-color palette.**\r\n* Adjusted brown shades to reduce excessive contrast.\r\n* Fixed an incorrect ANSI color assignment.\r\n* Tweaked a few color assignments for greater clarity and fewer distractions.\r\n* Improved highlighting of diff files.\r\n* Switched visual selection from dark-on-light to light-on-dark colors.","package":"abbott.vim-2.1.tar.gz","4":"abbott.vim-2.1.tar.gz","src_id":"27593","5":"27593","creation_date":"1620392557","6":"1620392557"},{"0":"3774","vim_version":"7.0","1":"7.0","script_version":"2.0","2":"2.0","version_comment":"* **Added support for 16- and 256-color terminals.**\r\n* **Added a bunch new highlight groups up through Vim 8.2.**\r\n* Increased saturation of several colors.\r\n* Slightly increased contrast across the board.\r\n* Added more shades of green.\r\n* Gave colors more evocative names.\r\n* Made comments italic.\r\n* Added options to configure new terminal support (undercurl, etc.).\r\n* Vastly improved documentation and updated screenshots.\r\n* Added `colors.sh` shell script to help maintain the color palette.\r\n* Swapped Bad Whitespace plugin support for modern Better Whitespace plugin.\r\n* Removed CSApprox settings overrides, leaving them up to the user.","3":"* **Added support for 16- and 256-color terminals.**\r\n* **Added a bunch new highlight groups up through Vim 8.2.**\r\n* Increased saturation of several colors.\r\n* Slightly increased contrast across the board.\r\n* Added more shades of green.\r\n* Gave colors more evocative names.\r\n* Made comments italic.\r\n* Added options to configure new terminal support (undercurl, etc.).\r\n* Vastly improved documentation and updated screenshots.\r\n* Added `colors.sh` shell script to help maintain the color palette.\r\n* Swapped Bad Whitespace plugin support for modern Better Whitespace plugin.\r\n* Removed CSApprox settings overrides, leaving them up to the user.","package":"abbott.vim-2.0.tar.gz","4":"abbott.vim-2.0.tar.gz","src_id":"27286","5":"27286","creation_date":"1597631733","6":"1597631733"},{"0":"3774","vim_version":"7.0","1":"7.0","script_version":"1.3","2":"1.3","version_comment":"Fixed areas where contrast\/readability dropped since v1.0.","3":"Fixed areas where contrast\/readability dropped since v1.0.","package":"abbott.vim-v1.3.tar.gz","4":"abbott.vim-v1.3.tar.gz","src_id":"17752","5":"17752","creation_date":"1334095264","6":"1334095264"},{"0":"3774","vim_version":"7.0","1":"7.0","script_version":"1.2","2":"1.2","version_comment":"Brighten a few colors, darken right margin substantially, make mint mildly different, and highlight TeX macros as preprocessor directives instead of statements.","3":"Brighten a few colors, darken right margin substantially, make mint mildly different, and highlight TeX macros as preprocessor directives instead of statements.","package":"abbott.vim-v1.2.tar.gz","4":"abbott.vim-v1.2.tar.gz","src_id":"17740","5":"17740","creation_date":"1333924838","6":"1333924838"},{"0":"3774","vim_version":"7.0","1":"7.0","script_version":"1.1.1","2":"1.1.1","version_comment":"Bump copyright year---which I stupidly forgot to do previously. :)","3":"Bump copyright year---which I stupidly forgot to do previously. :)","package":"abbott.vim-v1.1.1.tar.gz","4":"abbott.vim-v1.1.1.tar.gz","src_id":"17739","5":"17739","creation_date":"1333915901","6":"1333915901"},{"0":"3774","vim_version":"7.0","1":"7.0","script_version":"1.1","2":"1.1","version_comment":"Darken the background color substantially, brighten the blue and lavender colors, and tell CSApprox not to try and override the terminal's background color (since it'll just get mapped to black anyway).","3":"Darken the background color substantially, brighten the blue and lavender colors, and tell CSApprox not to try and override the terminal's background color (since it'll just get mapped to black anyway).","package":"abbott.vim-v1.1.tar.gz","4":"abbott.vim-v1.1.tar.gz","src_id":"17737","5":"17737","creation_date":"1333837694","6":"1333837694"},{"0":"3774","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"abbott.vim-v1.0.tar.gz","4":"abbott.vim-v1.0.tar.gz","src_id":"16691","5":"16691","creation_date":"1318885012","6":"1318885012"}]},"3773":{"script_id":"3773","0":"3773","script_name":"Lyrics","1":"Lyrics","script_type":"utility","2":"utility","summary":"Show lyrics","3":"Show lyrics","description":"Awesome plugin to view the lyrics of your favorite song without leaving VIM!\r\n\r\n1 - Install\r\nPut lyrics.vim in your ~\/.vim\/plugin folder.\r\n\r\n2 - How to use\r\n:Lyrics -> show the lyrics of the current song played in Rhythmbox.\r\n:SearchLyrics -> input: song-artist, show the lyrics of the song of your choice\r\n\r\n3 - Dependencies\r\n- wget in your path to download the lyrics from www.lyrics.com\r\n- Rhythmbox for the Lyrics command\r\n- vim 7\r\n\r\n4 - License\r\nGPLv2\r\n\r\nTested on Ubuntu 10.04.\r\n:: Humberto H. C. Pinheiro ::\r\n","4":"Awesome plugin to view the lyrics of your favorite song without leaving VIM!\r\n\r\n1 - Install\r\nPut lyrics.vim in your ~\/.vim\/plugin folder.\r\n\r\n2 - How to use\r\n:Lyrics -> show the lyrics of the current song played in Rhythmbox.\r\n:SearchLyrics -> input: song-artist, show the lyrics of the song of your choice\r\n\r\n3 - Dependencies\r\n- wget in your path to download the lyrics from www.lyrics.com\r\n- Rhythmbox for the Lyrics command\r\n- vim 7\r\n\r\n4 - License\r\nGPLv2\r\n\r\nTested on Ubuntu 10.04.\r\n:: Humberto H. C. Pinheiro ::\r\n","install_details":"Put lyrics.vim in your ~\/.vim\/plugin folder.","5":"Put lyrics.vim in your ~\/.vim\/plugin folder.","first_name":"Humberto","6":"Humberto","last_name":"Pinheiro","7":"Pinheiro","releases":[{"0":"3773","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"lyrics.tar.gz","4":"lyrics.tar.gz","src_id":"16690","5":"16690","creation_date":"1318868471","6":"1318868471"}]},"3772":{"script_id":"3772","0":"3772","script_name":"rainbow_parentheses.vim","1":"rainbow_parentheses.vim","script_type":"utility","2":"utility","summary":"Better Rainbow Parentheses","3":"Better Rainbow Parentheses","description":"Rainbow colors for parentheses, based on rainbow_parenthsis.vim of which there are multiple versions by Martin Krischik, John Gilmore, Luc Hermitte, and Steve Losh.\r\n\r\nThis version uses significantly less code than the older ones (~80% less) and has new options to make it easier to change the colors and the parentheses depth.\r\n\r\nUsage:\r\nRun :RainbowParenthesesToggle to toggle it on\/off.\r\n\r\nHighlight different bracket types:\r\n    :RainbowParenthesesLoadRound \" for ( ), default when toggling\r\n    :RainbowParenthesesLoadSquare \" for [ ]\r\n    :RainbowParenthesesLoadBraces \" for { }\r\n    :RainbowParenthesesLoadChevrons \" for < >\r\n\r\nGit repo: https:\/\/github.com\/kien\/rainbow_parentheses.vim\r\n\r\nNote: may not work for some languages (when syntax's already enabled) because of the limitation the `:syntax region` command.","4":"Rainbow colors for parentheses, based on rainbow_parenthsis.vim of which there are multiple versions by Martin Krischik, John Gilmore, Luc Hermitte, and Steve Losh.\r\n\r\nThis version uses significantly less code than the older ones (~80% less) and has new options to make it easier to change the colors and the parentheses depth.\r\n\r\nUsage:\r\nRun :RainbowParenthesesToggle to toggle it on\/off.\r\n\r\nHighlight different bracket types:\r\n    :RainbowParenthesesLoadRound \" for ( ), default when toggling\r\n    :RainbowParenthesesLoadSquare \" for [ ]\r\n    :RainbowParenthesesLoadBraces \" for { }\r\n    :RainbowParenthesesLoadChevrons \" for < >\r\n\r\nGit repo: https:\/\/github.com\/kien\/rainbow_parentheses.vim\r\n\r\nNote: may not work for some languages (when syntax's already enabled) because of the limitation the `:syntax region` command.","install_details":"Extract to ~\/.vim or $HOME\\vimfiles.","5":"Extract to ~\/.vim or $HOME\\vimfiles.","first_name":" ","6":" ","last_name":" ","7":" ","releases":[{"0":"3772","vim_version":"7.0","1":"7.0","script_version":"1.0.4","2":"1.0.4","version_comment":"Add a command to toggle all bracket types except chevrons \"<\" and \">\" (thanks to Patrick McFarland).\r\nAdd an option enable\/disable toggling with the Load cmds (toggling was added in 1.0.3).","3":"Add a command to toggle all bracket types except chevrons \"<\" and \">\" (thanks to Patrick McFarland).\r\nAdd an option enable\/disable toggling with the Load cmds (toggling was added in 1.0.3).","package":"rainbow_parentheses.zip","4":"rainbow_parentheses.zip","src_id":"18433","5":"18433","creation_date":"1345385114","6":"1345385114"},{"0":"3772","vim_version":"7.0","1":"7.0","script_version":"1.0.3","2":"1.0.3","version_comment":"Add the ability to toggle each parentheses type using the Load cmds.\r\nAdd vimrc example to always enable rainbow_parentheses.","3":"Add the ability to toggle each parentheses type using the Load cmds.\r\nAdd vimrc example to always enable rainbow_parentheses.","package":"rainbow_parentheses.zip","4":"rainbow_parentheses.zip","src_id":"16744","5":"16744","creation_date":"1319635539","6":"1319635539"}]},"3771":{"script_id":"3771","0":"3771","script_name":"tagfinder.vim","1":"tagfinder.vim","script_type":"utility","2":"utility","summary":"A simple vim plugin to look for tags of specific kinds: classes, functions, etc.","3":"A simple vim plugin to look for tags of specific kinds: classes, functions, etc.","description":"The purpose of this plugin is to enable searching for classes, functions or any\r\nother language structures by their name. It expects a tag file generated by\r\nusing exuberant ctags. It's very similar to the built-in \":tag\" command, but\r\nwith the added bonus of filtering tags by their type.\r\n\r\nDefining a global command to look for a class by its name would look like this:\r\n\r\n    :DefineTagFinder Class c,class\r\n\r\nAfter this command is invoked, you can execute the `Class` command with a tag\r\nname, which will send you to the class if it's unique, or load the entries in\r\nthe quickfix window and let you choose between them.\r\n\r\n    :Class ActiveRecord\r\n\r\nEven more conveniently, the newly defined command will have tab-completion with\r\nthe tag names, so you don't have to type it all in and you can see a useful\r\noverview of the matching classes (or functions, modules, vim commands...).\r\n\r\nSince different file types have different tag definitions, you can override\r\ncommands per buffer by placing `DefineLocalTagFinder` invocations in filetype\r\nplugins, or by using autocommands:\r\n\r\n    \" in ftplugin\/ruby.vim\r\n    DefineLocalTagFinder Method f,method\r\n\r\n    \" in .vimrc\r\n    autocommand FileType java DefineTagFinder Method m,method\r\n\r\nNote that the plugin comes with no predefined commands at all. My personal\r\npreference is to call them \"Class\", \"Function\" and so on, but you might prefer\r\nto use \"FindClass\" and \"FindFunction\" instead. The plugin simply provides the\r\ndefining command. For more information on installation and usage, please take a\r\nlook at the doc file.","4":"The purpose of this plugin is to enable searching for classes, functions or any\r\nother language structures by their name. It expects a tag file generated by\r\nusing exuberant ctags. It's very similar to the built-in \":tag\" command, but\r\nwith the added bonus of filtering tags by their type.\r\n\r\nDefining a global command to look for a class by its name would look like this:\r\n\r\n    :DefineTagFinder Class c,class\r\n\r\nAfter this command is invoked, you can execute the `Class` command with a tag\r\nname, which will send you to the class if it's unique, or load the entries in\r\nthe quickfix window and let you choose between them.\r\n\r\n    :Class ActiveRecord\r\n\r\nEven more conveniently, the newly defined command will have tab-completion with\r\nthe tag names, so you don't have to type it all in and you can see a useful\r\noverview of the matching classes (or functions, modules, vim commands...).\r\n\r\nSince different file types have different tag definitions, you can override\r\ncommands per buffer by placing `DefineLocalTagFinder` invocations in filetype\r\nplugins, or by using autocommands:\r\n\r\n    \" in ftplugin\/ruby.vim\r\n    DefineLocalTagFinder Method f,method\r\n\r\n    \" in .vimrc\r\n    autocommand FileType java DefineTagFinder Method m,method\r\n\r\nNote that the plugin comes with no predefined commands at all. My personal\r\npreference is to call them \"Class\", \"Function\" and so on, but you might prefer\r\nto use \"FindClass\" and \"FindFunction\" instead. The plugin simply provides the\r\ndefining command. For more information on installation and usage, please take a\r\nlook at the doc file.","install_details":"There are several ways to install the plugin. The recommended one is by using\r\nTim Pope's pathogen (http:\/\/www.vim.org\/scripts\/script.php?script_id=2332). In\r\nthat case, you can clone the plugin's git repository like so:\r\n\r\n    git clone git:\/\/github.com\/AndrewRadev\/tagfinder.vim.git ~\/.vim\/bundle\/tagfinder\r\n\r\nIf your vim configuration is under git version control, you could also set up\r\nthe repository as a submodule, which would allow you to update more easily.\r\nThe command is (provided you're in ~\/.vim):\r\n\r\n    git submodule add git:\/\/github.com\/AndrewRadev\/tagfinder.vim.git bundle\/tagfinder\r\n\r\nAnother way is to simply copy all the essential directories inside the ~.vim\/\r\ndirectory: autoload, doc, plugin.\r\n","5":"There are several ways to install the plugin. The recommended one is by using\r\nTim Pope's pathogen (http:\/\/www.vim.org\/scripts\/script.php?script_id=2332). In\r\nthat case, you can clone the plugin's git repository like so:\r\n\r\n    git clone git:\/\/github.com\/AndrewRadev\/tagfinder.vim.git ~\/.vim\/bundle\/tagfinder\r\n\r\nIf your vim configuration is under git version control, you could also set up\r\nthe repository as a submodule, which would allow you to update more easily.\r\nThe command is (provided you're in ~\/.vim):\r\n\r\n    git submodule add git:\/\/github.com\/AndrewRadev\/tagfinder.vim.git bundle\/tagfinder\r\n\r\nAnother way is to simply copy all the essential directories inside the ~.vim\/\r\ndirectory: autoload, doc, plugin.\r\n","first_name":"Andrew","6":"Andrew","last_name":"Radev","7":"Radev","releases":[{"0":"3771","vim_version":"7.0","1":"7.0","script_version":"0.1.0","2":"0.1.0","version_comment":"Ability to define a tagfinder, not filtered by kind.","3":"Ability to define a tagfinder, not filtered by kind.","package":"tagfinder.zip","4":"tagfinder.zip","src_id":"21343","5":"21343","creation_date":"1390068002","6":"1390068002"},{"0":"3771","vim_version":"7.0","1":"7.0","script_version":"0.0.1","2":"0.0.1","version_comment":"Initial upload","3":"Initial upload","package":"tagfinder.zip","4":"tagfinder.zip","src_id":"16667","5":"16667","creation_date":"1318535979","6":"1318535979"}]},"3770":{"script_id":"3770","0":"3770","script_name":"Python-mode-klen","1":"Python-mode-klen","script_type":"ftplugin","2":"ftplugin","summary":"python mode","3":"python mode","description":"Python-mode is a vim plugin that allows you to use the pylint, rope, pydoc library in vim to provide features like python code looking for bugs, refactoring and some other usefull things.\r\n\r\nThis plugin allow you create python code in vim very easily. There is no need to install the pylint or rope library on your system.\r\n\r\nSee screencast here: http:\/\/t.co\/3b0bzeXA (sory for quality, this my first screencasting)\r\n\r\nPython-mode on github: https:\/\/github.com\/klen\/python-mode","4":"Python-mode is a vim plugin that allows you to use the pylint, rope, pydoc library in vim to provide features like python code looking for bugs, refactoring and some other usefull things.\r\n\r\nThis plugin allow you create python code in vim very easily. There is no need to install the pylint or rope library on your system.\r\n\r\nSee screencast here: http:\/\/t.co\/3b0bzeXA (sory for quality, this my first screencasting)\r\n\r\nPython-mode on github: https:\/\/github.com\/klen\/python-mode","install_details":"Just copy the plugin folders into your ~\/.vim directory.\r\nAlternatively, if you are using pathogen, clone the plugin into your bundle folder.\r\nAlso you can see vim help. :help PythonMode","5":"Just copy the plugin folders into your ~\/.vim directory.\r\nAlternatively, if you are using pathogen, clone the plugin into your bundle folder.\r\nAlso you can see vim help. :help PythonMode","first_name":"Kirill","6":"Kirill","last_name":"Klenov","7":"Klenov","releases":[{"0":"3770","vim_version":"7.0","1":"7.0","script_version":"0.8.1","2":"0.8.1","version_comment":"* Pylama updated to version 3.3.2\r\n* Get fold's expression symbol from &fillchars;\r\n* Fixed error when setting g:pymode_breakpoint_cmd (expobrain);\r\n* Fixed code running;\r\n* Ability to override rope project root and .ropeproject folder\r\n* Added path argument to `PymodeRopeNewProject` which skips prompt\r\n* Disable `pymode_rope_lookup_project` by default\r\n* Options added:\r\n    'pymode_rope_project_root', 'pymode_rope_ropefolder'\r\n","3":"* Pylama updated to version 3.3.2\r\n* Get fold's expression symbol from &fillchars;\r\n* Fixed error when setting g:pymode_breakpoint_cmd (expobrain);\r\n* Fixed code running;\r\n* Ability to override rope project root and .ropeproject folder\r\n* Added path argument to `PymodeRopeNewProject` which skips prompt\r\n* Disable `pymode_rope_lookup_project` by default\r\n* Options added:\r\n    'pymode_rope_project_root', 'pymode_rope_ropefolder'\r\n","package":"python-mode-0.8.1.zip","4":"python-mode-0.8.1.zip","src_id":"22021","5":"22021","creation_date":"1402496585","6":"1402496585"},{"0":"3770","vim_version":"7.0","1":"7.0","script_version":"0.7.8b","2":"0.7.8b","version_comment":"bugfix 0.7.6b","3":"bugfix 0.7.6b","package":"python-mode-0.7.8b.zip","4":"python-mode-0.7.8b.zip","src_id":"21154","5":"21154","creation_date":"1386220276","6":"1386220276"},{"0":"3770","vim_version":"7.0","1":"7.0","script_version":"0.7.6b","2":"0.7.6b","version_comment":"* Update indentation support; \r\n    * Python3 support; \r\n    * Removed pymode modeline support; \r\n    * Disabled async code checking support; \r\n    * Fixed a lot of bugs; \r\n    * Options changes: \r\n        'pymode_doc_key' -> 'pymode_doc_bind' \r\n        'pymode_run_key' -> 'pymode_run_bind' \r\n        'pymode_breakpoint_key' -> 'pymode_breakpoint_bind' \r\n        'pymode_breakpoint_template' -> 'pymode_breakpoint_cmd' \r\n        'pymode_lint_write' -> 'pymode_lint_on_write' \r\n        'pymode_lint_onfly' -> 'pymode_lint_on_fly' \r\n        'pymode_lint_checker' -> 'pymode_lint_checkers' \r\n        'pymode_lint_minheight' -> 'pymode_quickfix_minheight' \r\n        'pymode_lint_maxheight' -> 'pymode_quickfix_maxheight' \r\n        'pymode_rope_autocomplete_map' -> 'pymode_rope_completion_bind' \r\n        'pymode_rope_enable_autoimport' -> 'pymode_rope_autoimport' \r\n\r\n    * Options removed: \r\n        'pymode_lint_hold', 'pymode_lint_config', 'pymode_lint_jump', \r\n        'pymode_lint_signs_always_visible', 'pymode_rope_extended_complete', \r\n        'pymode_rope_auto_project', 'pymode_rope_autoimport_generate', \r\n        'pymode_rope_autoimport_underlines', 'pymode_rope_codeassist_maxfixes', \r\n        'pymode_rope_sorted_completions', 'pymode_rope_extended_complete', \r\n        'pymode_rope_confirm_saving', 'pymode_rope_global_prefix', \r\n        'pymode_rope_local_prefix', 'pymode_rope_vim_completion', 'pymode_rope_guess_project', \r\n        'pymode_rope_goto_def_newwin', 'pymode_rope_always_show_complete_menu' \r\n\r\n    * Options added: \r\n        'pymode_rope_regenerate_on_write', 'pymode_rope_completion', 'pymode_rope_complete_on_dot', \r\n        'pymode_lint_sort' \r\n\r\n    * Commands added: \r\n        'PymodeVirtualenv' \r\n\r\n    * Commands changed: \r\n        'PyDoc' -> 'PymodeDoc' \r\n        'Pyrun' -> 'PymodeRun' \r\n        'PyLintToggle' -> 'PymodeLintToggle' \r\n        'PyLint' -> 'PymodeLint' \r\n        'PyLintAuto' -> 'PymodeLintAuto' \r\n        'RopeOpenProject' -> 'PymodeRopeNewProject' \r\n        'RopeUndo' -> 'PymodeRopeUndo' \r\n        'RopeRedo' -> 'PymodeRopeRedo' \r\n        'RopeRenameCurrentModule' -> 'PymodeRopeRenameModule' \r\n        'RopeModuleToPackage' -> 'PymodeRopeModuleToPackage' \r\n        'RopeGenerateAutoimportCache' -> 'PymodeRopeRegenerate' \r\n        'RopeOrgamizeImports' -> 'PymodeRopeAutoImport' \r\n\r\n    * Commands removed: \r\n        'PyLintCheckerToggle', 'RopeCloseProject', 'RopeProjectConfig', \r\n        'RopeRename', 'RopeCreate<...>', 'RopeWriteProject', 'RopeRename', \r\n        'RopeExtractVariable', 'RopeExtractMethod', 'RopeInline', 'RopeMove', \r\n        'RopeRestructure', 'RopeUseFunction', 'RopeIntroduceFactory', \r\n        'RopeChangeSignature', 'RopeMoveCurrentModule', \r\n        'RopeGenerate<...>', 'RopeAnalizeModule', 'RopeAutoImport',","3":"* Update indentation support; \r\n    * Python3 support; \r\n    * Removed pymode modeline support; \r\n    * Disabled async code checking support; \r\n    * Fixed a lot of bugs; \r\n    * Options changes: \r\n        'pymode_doc_key' -> 'pymode_doc_bind' \r\n        'pymode_run_key' -> 'pymode_run_bind' \r\n        'pymode_breakpoint_key' -> 'pymode_breakpoint_bind' \r\n        'pymode_breakpoint_template' -> 'pymode_breakpoint_cmd' \r\n        'pymode_lint_write' -> 'pymode_lint_on_write' \r\n        'pymode_lint_onfly' -> 'pymode_lint_on_fly' \r\n        'pymode_lint_checker' -> 'pymode_lint_checkers' \r\n        'pymode_lint_minheight' -> 'pymode_quickfix_minheight' \r\n        'pymode_lint_maxheight' -> 'pymode_quickfix_maxheight' \r\n        'pymode_rope_autocomplete_map' -> 'pymode_rope_completion_bind' \r\n        'pymode_rope_enable_autoimport' -> 'pymode_rope_autoimport' \r\n\r\n    * Options removed: \r\n        'pymode_lint_hold', 'pymode_lint_config', 'pymode_lint_jump', \r\n        'pymode_lint_signs_always_visible', 'pymode_rope_extended_complete', \r\n        'pymode_rope_auto_project', 'pymode_rope_autoimport_generate', \r\n        'pymode_rope_autoimport_underlines', 'pymode_rope_codeassist_maxfixes', \r\n        'pymode_rope_sorted_completions', 'pymode_rope_extended_complete', \r\n        'pymode_rope_confirm_saving', 'pymode_rope_global_prefix', \r\n        'pymode_rope_local_prefix', 'pymode_rope_vim_completion', 'pymode_rope_guess_project', \r\n        'pymode_rope_goto_def_newwin', 'pymode_rope_always_show_complete_menu' \r\n\r\n    * Options added: \r\n        'pymode_rope_regenerate_on_write', 'pymode_rope_completion', 'pymode_rope_complete_on_dot', \r\n        'pymode_lint_sort' \r\n\r\n    * Commands added: \r\n        'PymodeVirtualenv' \r\n\r\n    * Commands changed: \r\n        'PyDoc' -> 'PymodeDoc' \r\n        'Pyrun' -> 'PymodeRun' \r\n        'PyLintToggle' -> 'PymodeLintToggle' \r\n        'PyLint' -> 'PymodeLint' \r\n        'PyLintAuto' -> 'PymodeLintAuto' \r\n        'RopeOpenProject' -> 'PymodeRopeNewProject' \r\n        'RopeUndo' -> 'PymodeRopeUndo' \r\n        'RopeRedo' -> 'PymodeRopeRedo' \r\n        'RopeRenameCurrentModule' -> 'PymodeRopeRenameModule' \r\n        'RopeModuleToPackage' -> 'PymodeRopeModuleToPackage' \r\n        'RopeGenerateAutoimportCache' -> 'PymodeRopeRegenerate' \r\n        'RopeOrgamizeImports' -> 'PymodeRopeAutoImport' \r\n\r\n    * Commands removed: \r\n        'PyLintCheckerToggle', 'RopeCloseProject', 'RopeProjectConfig', \r\n        'RopeRename', 'RopeCreate<...>', 'RopeWriteProject', 'RopeRename', \r\n        'RopeExtractVariable', 'RopeExtractMethod', 'RopeInline', 'RopeMove', \r\n        'RopeRestructure', 'RopeUseFunction', 'RopeIntroduceFactory', \r\n        'RopeChangeSignature', 'RopeMoveCurrentModule', \r\n        'RopeGenerate<...>', 'RopeAnalizeModule', 'RopeAutoImport',","package":"python-mode-0.7.6b.zip","4":"python-mode-0.7.6b.zip","src_id":"21149","5":"21149","creation_date":"1386137216","6":"1386137216"}]},"3769":{"script_id":"3769","0":"3769","script_name":"ahkcomplete","1":"ahkcomplete","script_type":"ftplugin","2":"ftplugin","summary":"autohotkey ahk complete","3":"autohotkey ahk complete","description":"You can use the user defined completion (intellisense) in ahk files\r\nIn  insert mode, Input keyword and press <C-X><C-U>. like this\r\n#a <C-X><C-U>  \r\nEnjoy !\r\n","4":"You can use the user defined completion (intellisense) in ahk files\r\nIn  insert mode, Input keyword and press <C-X><C-U>. like this\r\n#a <C-X><C-U>  \r\nEnjoy !\r\n","install_details":"copy  the plugin to ~\/.vim\/plugin (unix) or %HOMEPATH%\\vimfiles\\plugin (windows) ","5":"copy  the plugin to ~\/.vim\/plugin (unix) or %HOMEPATH%\\vimfiles\\plugin (windows) ","first_name":"Array","6":"Array","last_name":"Lin","7":"Lin","releases":[{"0":"3769","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"autohotkey.vim","4":"autohotkey.vim","src_id":"16648","5":"16648","creation_date":"1318256503","6":"1318256503"}]},"3768":{"script_id":"3768","0":"3768","script_name":"mappingmanager","1":"mappingmanager","script_type":"utility","2":"utility","summary":"easy navigation between keyboard mappings","3":"easy navigation between keyboard mappings","description":"DEMO\r\n=====\r\nactions speak louder than words, so check out this demo:\r\n\r\nhttp:\/\/www.playterm.org\/r\/vim-mappingmanager-plugin-1318246417?vim=1\r\n\r\n(\r\n\r\nPROBLEM\r\n=======\r\nFirst there was a happy vim-user, but after some vim plugins, \r\nlots of tricks'n'commands: the vim-user begins to suffer from braindamage.\r\nKeyboardshortcuts are easier to remember, but in vim also its very\r\neasy to get a 'almost-all-my-mappings-are-taken' syndrome.\r\n\r\nSOLUTION\r\n========\r\nswitching of keyboardmappings..you can have endless mappings now.\r\nCall it keyboardshortcutsmappings or presets if you will.\r\n\r\n\r\nUSAGE \r\n======\r\n- use ,m to toggle a mappingmanager-panel which gives LOT of info\r\n- use ,, to cycle thru mappings (remembering this shortcut is enough, rest is self-explanatory)\r\n- [optional] use ,. to view the current mapping\r\n- [optional] use ,\/ to select a mapping\r\n- [optional] use ,m change output mode between 'dialog' or 'console'\r\n- [optional] use ,F1 select mapping #1\r\n- [optional] use ,F2 select mapping #2\r\n- ..and so on\r\n\r\nAuthor : Leon van Kammen (Coder Of Salvation\/leon.vankammen.eu) \r\nAuthor : Tim Gerritsen (Mannetje Development\/www.mannetje.org) \r\n","4":"DEMO\r\n=====\r\nactions speak louder than words, so check out this demo:\r\n\r\nhttp:\/\/www.playterm.org\/r\/vim-mappingmanager-plugin-1318246417?vim=1\r\n\r\n(\r\n\r\nPROBLEM\r\n=======\r\nFirst there was a happy vim-user, but after some vim plugins, \r\nlots of tricks'n'commands: the vim-user begins to suffer from braindamage.\r\nKeyboardshortcuts are easier to remember, but in vim also its very\r\neasy to get a 'almost-all-my-mappings-are-taken' syndrome.\r\n\r\nSOLUTION\r\n========\r\nswitching of keyboardmappings..you can have endless mappings now.\r\nCall it keyboardshortcutsmappings or presets if you will.\r\n\r\n\r\nUSAGE \r\n======\r\n- use ,m to toggle a mappingmanager-panel which gives LOT of info\r\n- use ,, to cycle thru mappings (remembering this shortcut is enough, rest is self-explanatory)\r\n- [optional] use ,. to view the current mapping\r\n- [optional] use ,\/ to select a mapping\r\n- [optional] use ,m change output mode between 'dialog' or 'console'\r\n- [optional] use ,F1 select mapping #1\r\n- [optional] use ,F2 select mapping #2\r\n- ..and so on\r\n\r\nAuthor : Leon van Kammen (Coder Of Salvation\/leon.vankammen.eu) \r\nAuthor : Tim Gerritsen (Mannetje Development\/www.mannetje.org) \r\n","install_details":"INSTALLATION \r\n============\r\nfollowing instructions are focused on *NIX based, textmode vim-users, but\r\nmight also work on other platforms with a bit of love:\r\n\r\n- put mappingmanager.vim into your plugins directory\r\n- add the contents of mappings.vim to your vimrc configuration file\r\n- [optional] multi-user \/ company installation which keeps things tidy:\r\n   - copy mappings.vim to your global vimconfig dir (example: \/etc\/vim)\r\n   - copy mappings.vim to your homedir's .vim dir (example: ~\/.vim usually exist)\r\n   - copy mappings.vim to your projectdir dir, vim will automatically add projectspecific mappings ","5":"INSTALLATION \r\n============\r\nfollowing instructions are focused on *NIX based, textmode vim-users, but\r\nmight also work on other platforms with a bit of love:\r\n\r\n- put mappingmanager.vim into your plugins directory\r\n- add the contents of mappings.vim to your vimrc configuration file\r\n- [optional] multi-user \/ company installation which keeps things tidy:\r\n   - copy mappings.vim to your global vimconfig dir (example: \/etc\/vim)\r\n   - copy mappings.vim to your homedir's .vim dir (example: ~\/.vim usually exist)\r\n   - copy mappings.vim to your projectdir dir, vim will automatically add projectspecific mappings ","first_name":"Leon","6":"Leon","last_name":"van Kammen","7":"van Kammen","releases":[{"0":"3768","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"mappingmanager-v1.0.tar.gz","4":"mappingmanager-v1.0.tar.gz","src_id":"16647","5":"16647","creation_date":"1318246517","6":"1318246517"}]},"3767":{"script_id":"3767","0":"3767","script_name":"MapFinder","1":"MapFinder","script_type":"utility","2":"utility","summary":"Find Maps with vim patterns matching rhs.","3":"Find Maps with vim patterns matching rhs.","description":"This plugin is useful if you use plugins which define lots of maps and it is not easy remember them at first (for example some latex plugins). It provides commands:\r\nMap[!]   {pattern}\r\nNmap[!]   {pattern}\r\nImap[!]   {pattern}\r\nSmap[!]   {pattern}\r\nVmap[!]   {pattern}\r\nOmap[!]   {pattern}\r\nLmap[!]   {pattern}\r\nThey will list maps which rhs matches the vim {pattern}. If bang is used the {pattern} is matched by the output of the corresponding map command with only first column removed (which indicates the mode).","4":"This plugin is useful if you use plugins which define lots of maps and it is not easy remember them at first (for example some latex plugins). It provides commands:\r\nMap[!]   {pattern}\r\nNmap[!]   {pattern}\r\nImap[!]   {pattern}\r\nSmap[!]   {pattern}\r\nVmap[!]   {pattern}\r\nOmap[!]   {pattern}\r\nLmap[!]   {pattern}\r\nThey will list maps which rhs matches the vim {pattern}. If bang is used the {pattern} is matched by the output of the corresponding map command with only first column removed (which indicates the mode).","install_details":"Open the vim ball file and source it (:source %).","5":"Open the vim ball file and source it (:source %).","first_name":"Marcin","6":"Marcin","last_name":"Szamotulski","7":"Szamotulski","releases":[{"0":"3767","vim_version":"7.0","1":"7.0","script_version":"1","2":"1","version_comment":"Initial upload","3":"Initial upload","package":"MapFinder.vmb","4":"MapFinder.vmb","src_id":"16641","5":"16641","creation_date":"1318144666","6":"1318144666"}]},"3766":{"script_id":"3766","0":"3766","script_name":"vimroom.vim","1":"vimroom.vim","script_type":"utility","2":"utility","summary":"WriteRoom in Vim.","3":"WriteRoom in Vim.","description":"Vimroom is an implementation of some of the best bits of WriteRoom in Vim. Because Vim is nice.\r\n\r\nhttp:\/\/projects.mikewest.org\/vimroom\/ is the canonical project page: check there for updates (though I'll do my best to keep this up to date as well).","4":"Vimroom is an implementation of some of the best bits of WriteRoom in Vim. Because Vim is nice.\r\n\r\nhttp:\/\/projects.mikewest.org\/vimroom\/ is the canonical project page: check there for updates (though I'll do my best to keep this up to date as well).","install_details":"","5":"","first_name":"Mike","6":"Mike","last_name":"West","7":"West","releases":[{"0":"3766","vim_version":"7.0","1":"7.0","script_version":"v0.7","2":"v0.7","version_comment":"Initial upload","3":"Initial upload","package":"mikewest-vimroom-v0.7-0-ga39a90f.tar.gz","4":"mikewest-vimroom-v0.7-0-ga39a90f.tar.gz","src_id":"16640","5":"16640","creation_date":"1318100598","6":"1318100598"}]},"3765":{"script_id":"3765","0":"3765","script_name":"TagmaTasks","1":"TagmaTasks","script_type":"utility","2":"utility","summary":"IDE like Task List for Vim buffers.","3":"IDE like Task List for Vim buffers.","description":"Displays tasks for the current buffer using the Vim location-list window.\r\nBased on the task lists from other IDEs. Will also display marks next to each\r\ntask line using the Vim signs feature.\r\n\r\nGutHub Home: https:\/\/github.com\/LStinson\/TagmaTasks\r\n\r\nThe Task List is generated using the lvimgrep command. See that command for\r\nspecifics on how the Task List is generated\r\n\r\nUser Commands:\r\n    :TagmaTasks - Generate the Task List. Several options control behavior.\r\n    :TagmaTaskMarks - Display the Task Marks.\r\n    :TagmaTaskClear - Clear the Task Marks.\r\n    :TagmaTaskToggle - Toggle the Task Window.\r\n\r\n\r\nKey Mappings:\r\n    <Leader>tt - Calls :TagmaTasks\r\n    <Leader>tc - Calls :TagmaTaskClear \r\n    <Leader>tm - Calls :TagmaTaskMarks \r\n    <Leader>tw - Calls :TagmaTaskToggle \r\n\r\nSee the documentation for more details.\r\n\r\nI welcome any and all feedback. Please contact me at LoranceStinson AT Gmail....\r\nPlease be sure to put TagmaTasks in the subject so I know what you are emailing about.","4":"Displays tasks for the current buffer using the Vim location-list window.\r\nBased on the task lists from other IDEs. Will also display marks next to each\r\ntask line using the Vim signs feature.\r\n\r\nGutHub Home: https:\/\/github.com\/LStinson\/TagmaTasks\r\n\r\nThe Task List is generated using the lvimgrep command. See that command for\r\nspecifics on how the Task List is generated\r\n\r\nUser Commands:\r\n    :TagmaTasks - Generate the Task List. Several options control behavior.\r\n    :TagmaTaskMarks - Display the Task Marks.\r\n    :TagmaTaskClear - Clear the Task Marks.\r\n    :TagmaTaskToggle - Toggle the Task Window.\r\n\r\n\r\nKey Mappings:\r\n    <Leader>tt - Calls :TagmaTasks\r\n    <Leader>tc - Calls :TagmaTaskClear \r\n    <Leader>tm - Calls :TagmaTaskMarks \r\n    <Leader>tw - Calls :TagmaTaskToggle \r\n\r\nSee the documentation for more details.\r\n\r\nI welcome any and all feedback. Please contact me at LoranceStinson AT Gmail....\r\nPlease be sure to put TagmaTasks in the subject so I know what you are emailing about.","install_details":"To install copy the files to ~\/.vim or ~\/vimfiles. \r\nIf using a package manager like pathgen place the whole directory in the bundle directory.","5":"To install copy the files to ~\/.vim or ~\/vimfiles. \r\nIf using a package manager like pathgen place the whole directory in the bundle directory.","first_name":"Lorance","6":"Lorance","last_name":"Stinson","7":"Stinson","releases":[{"0":"3765","vim_version":"7.0","1":"7.0","script_version":"0.3","2":"0.3","version_comment":"TagmaTasks can now generate a task list for a list of files. This is done using the vimgrep command.","3":"TagmaTasks can now generate a task list for a list of files. This is done using the vimgrep command.","package":"TagmaTasks.zip","4":"TagmaTasks.zip","src_id":"17599","5":"17599","creation_date":"1331917718","6":"1331917718"},{"0":"3765","vim_version":"7.0","1":"7.0","script_version":"0.2","2":"0.2","version_comment":"Fixed a bug that would cause errors if no tasks were found in the buffer.\r\n\r\nAdded <Plug> mappings and changed the global key maps to use them.\r\n\r\nDocumentation reformatting.","3":"Fixed a bug that would cause errors if no tasks were found in the buffer.\r\n\r\nAdded <Plug> mappings and changed the global key maps to use them.\r\n\r\nDocumentation reformatting.","package":"TagmaTasks.zip","4":"TagmaTasks.zip","src_id":"17269","5":"17269","creation_date":"1327116406","6":"1327116406"}]},"3764":{"script_id":"3764","0":"3764","script_name":"fcitx.vim","1":"fcitx.vim","script_type":"utility","2":"utility","summary":"keep and restore fcitx state when leaving\/re-entering insert mode","3":"keep and restore fcitx state when leaving\/re-entering insert mode","description":"Keep and restore fcitx state for each buffer separately when leaving\/re-entering insert mode. Like always typing English in normal mode, but Chinese in insert mode.\r\n\r\nRequires: fcitx 3.6 or later, 4.0 or later will be better.\r\n\r\nSettings: environment variable $FCITX_SOCKET specifies a socket to connect instead of figuring out itself. This can be an abstract socket address starting with \"@\" from version 1.2.4 on.\r\n\r\nGit repo: https:\/\/github.com\/lilydjwg\/fcitx.vim\r\nwww.vim.org: http:\/\/www.vim.org\/scripts\/script.php?script_id=3764\r\n\r\nWarning:\r\n1, It will be faster and better with Python (3 or 2) enabled Vim. But some old version Vim enabled both Python 2 & 3 may have some issues.\r\n2, If you use Vim in terminal, to avoid the Esc delay, please set 'ttimeoutlen' to 100 or some other value. And check screen's 'maptimeout' or tmux's 'escape-time' option if you use it too.\r\n\r\n在离开或重新进入插入模式时自动记录和恢复每个缓冲区各自的输入法状态，以便在普通模式下始终是英文输入模式，切换回插入模式时恢复离开前的输入法输入模式。\r\n\r\n要求: fcitx 版本 3.6 以上，建议 fcitx 4.0 以上。\r\n\r\n配置：环境变量 $FCITX_SOCKET 指定要连接的套接字路径，而非默认的。自版本 1.2.4 起，此变量若以 \"@\" 字符开头，则被认为是抽象套接字地址。\r\n\r\nGit 仓库: https:\/\/github.com\/lilydjwg\/fcitx.vim\r\nwww.vim.org: http:\/\/www.vim.org\/scripts\/script.php?script_id=3764\r\n\r\n注意事项:\r\n1. Vim 如有 Python 3或2 支持可以获得更快更好的效果。但对于较旧的 Vim 版本，如果同时编译了 Python 2 & 3 支持，因为此 Vim 不能同时运行两个版本的 Python，而本脚本首先检查 Python 3，所以会导致出错或者 Python 2 不可用。\r\n2. 终端下请设置 Vim 'ttimeoutlen' 选项为较小值（如100），否则退出插入模式时会有较严重的延迟。同样会造成延迟的还有 screen 的 maptimeout 选项以及 tmux 的 escape-time 选项。\r\n\r\n如果你想跨主机使用 fcitx.vim，请参考此文： https:\/\/blog.lilydjwg.me\/2012\/7\/27\/using-fcitx-remote-interface-remotely-via-socat.34729.html","4":"Keep and restore fcitx state for each buffer separately when leaving\/re-entering insert mode. Like always typing English in normal mode, but Chinese in insert mode.\r\n\r\nRequires: fcitx 3.6 or later, 4.0 or later will be better.\r\n\r\nSettings: environment variable $FCITX_SOCKET specifies a socket to connect instead of figuring out itself. This can be an abstract socket address starting with \"@\" from version 1.2.4 on.\r\n\r\nGit repo: https:\/\/github.com\/lilydjwg\/fcitx.vim\r\nwww.vim.org: http:\/\/www.vim.org\/scripts\/script.php?script_id=3764\r\n\r\nWarning:\r\n1, It will be faster and better with Python (3 or 2) enabled Vim. But some old version Vim enabled both Python 2 & 3 may have some issues.\r\n2, If you use Vim in terminal, to avoid the Esc delay, please set 'ttimeoutlen' to 100 or some other value. And check screen's 'maptimeout' or tmux's 'escape-time' option if you use it too.\r\n\r\n在离开或重新进入插入模式时自动记录和恢复每个缓冲区各自的输入法状态，以便在普通模式下始终是英文输入模式，切换回插入模式时恢复离开前的输入法输入模式。\r\n\r\n要求: fcitx 版本 3.6 以上，建议 fcitx 4.0 以上。\r\n\r\n配置：环境变量 $FCITX_SOCKET 指定要连接的套接字路径，而非默认的。自版本 1.2.4 起，此变量若以 \"@\" 字符开头，则被认为是抽象套接字地址。\r\n\r\nGit 仓库: https:\/\/github.com\/lilydjwg\/fcitx.vim\r\nwww.vim.org: http:\/\/www.vim.org\/scripts\/script.php?script_id=3764\r\n\r\n注意事项:\r\n1. Vim 如有 Python 3或2 支持可以获得更快更好的效果。但对于较旧的 Vim 版本，如果同时编译了 Python 2 & 3 支持，因为此 Vim 不能同时运行两个版本的 Python，而本脚本首先检查 Python 3，所以会导致出错或者 Python 2 不可用。\r\n2. 终端下请设置 Vim 'ttimeoutlen' 选项为较小值（如100），否则退出插入模式时会有较严重的延迟。同样会造成延迟的还有 screen 的 maptimeout 选项以及 tmux 的 escape-time 选项。\r\n\r\n如果你想跨主机使用 fcitx.vim，请参考此文： https:\/\/blog.lilydjwg.me\/2012\/7\/27\/using-fcitx-remote-interface-remotely-via-socat.34729.html","install_details":"Just extract it to ~\/.vim. If your vim doesn't have Python support and you aren't going to use it, you can just put so\/fcitx.vim to ~\/.vim\/plugin.\r\n\r\n解压到 ~\/.vim 下即可。如果没有并且不准备使用 Python 接口，可只将 so\/fcitx.vim 放到 ~\/.vim\/plugin 目录下。\r\n","5":"Just extract it to ~\/.vim. If your vim doesn't have Python support and you aren't going to use it, you can just put so\/fcitx.vim to ~\/.vim\/plugin.\r\n\r\n解压到 ~\/.vim 下即可。如果没有并且不准备使用 Python 接口，可只将 so\/fcitx.vim 放到 ~\/.vim\/plugin 目录下。\r\n","first_name":"lilydjwg","6":"lilydjwg","last_name":" ","7":" ","releases":[{"0":"3764","vim_version":"7.0","1":"7.0","script_version":"1.2.6","2":"1.2.6","version_comment":"support fcitx5","3":"support fcitx5","package":"fcitx.vim.tar.gz","4":"fcitx.vim.tar.gz","src_id":"26499","5":"26499","creation_date":"1558533967","6":"1558533967"},{"0":"3764","vim_version":"7.0","1":"7.0","script_version":"1.2.5","2":"1.2.5","version_comment":"* improved error message and connection handling\r\n* recognized MacVim\r\n* added timeouts","3":"* improved error message and connection handling\r\n* recognized MacVim\r\n* added timeouts","package":"fcitx.vim.tar.gz","4":"fcitx.vim.tar.gz","src_id":"25227","5":"25227","creation_date":"1495594724","6":"1495594724"},{"0":"3764","vim_version":"7.0","1":"7.0","script_version":"1.2.4","2":"1.2.4","version_comment":"* add abstract socket support","3":"* add abstract socket support","package":"fcitx.vim.tar.gz","4":"fcitx.vim.tar.gz","src_id":"21006","5":"21006","creation_date":"1383621209","6":"1383621209"},{"0":"3764","vim_version":"7.0","1":"7.0","script_version":"1.2.3","2":"1.2.3","version_comment":"* ignore empty recv result","3":"* ignore empty recv result","package":"fcitx.tar.gz","4":"fcitx.tar.gz","src_id":"19159","5":"19159","creation_date":"1355128003","6":"1355128003"},{"0":"3764","vim_version":"7.0","1":"7.0","script_version":"1.2.2","2":"1.2.2","version_comment":"* so\/fcitx.vim: update environment check","3":"* so\/fcitx.vim: update environment check","package":"fcitx.tar.gz","4":"fcitx.tar.gz","src_id":"19070","5":"19070","creation_date":"1354285766","6":"1354285766"},{"0":"3764","vim_version":"7.0","1":"7.0","script_version":"1.2.1","2":"1.2.1","version_comment":"forgot to add the pure vimscript version: so\/fcitx.vim","3":"forgot to add the pure vimscript version: so\/fcitx.vim","package":"fcitx.tar.gz","4":"fcitx.tar.gz","src_id":"18745","5":"18745","creation_date":"1349320673","6":"1349320673"},{"0":"3764","vim_version":"7.0","1":"7.0","script_version":"1.2","2":"1.2","version_comment":"support to specify fcitx socket file by environment variable $FCITX_SOCKET","3":"support to specify fcitx socket file by environment variable $FCITX_SOCKET","package":"fcitx.tar.gz","4":"fcitx.tar.gz","src_id":"18323","5":"18323","creation_date":"1343358581","6":"1343358581"},{"0":"3764","vim_version":"7.0","1":"7.0","script_version":"1.1.1","2":"1.1.1","version_comment":"forgot to compress the tarball.","3":"forgot to compress the tarball.","package":"fcitx.tar.gz","4":"fcitx.tar.gz","src_id":"17984","5":"17984","creation_date":"1337256891","6":"1337256891"},{"0":"3764","vim_version":"7.0","1":"7.0","script_version":"1.1","2":"1.1","version_comment":"* remove warning about not using Python interface\r\n* messages translate into English as fcitx supports more and more languages","3":"* remove warning about not using Python interface\r\n* messages translate into English as fcitx supports more and more languages","package":"fcitx.tar.gz","4":"fcitx.tar.gz","src_id":"17983","5":"17983","creation_date":"1337242421","6":"1337242421"},{"0":"3764","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"fcitx.zip","4":"fcitx.zip","src_id":"16632","5":"16632","creation_date":"1318002008","6":"1318002008"}]},"3763":{"script_id":"3763","0":"3763","script_name":"vim-google-scribe","1":"vim-google-scribe","script_type":"utility","2":"utility","summary":"Keystroke saving with Vim and Google Scribe","3":"Keystroke saving with Vim and Google Scribe","description":"https:\/\/github.com\/epiloque\/vim-google-scribe\r\n\r\nGoogle Scribe provides text completion service. Using information from what you have already typed in a document, Google Scribe provides related word or phrase completion suggestions. In addition to saving keystrokes, Google Scribe's suggestions indicate correct or popular phrases to use.\r\n\r\nvim-google-scribe requires an installation of Vim compiled with python support.\r\n","4":"https:\/\/github.com\/epiloque\/vim-google-scribe\r\n\r\nGoogle Scribe provides text completion service. Using information from what you have already typed in a document, Google Scribe provides related word or phrase completion suggestions. In addition to saving keystrokes, Google Scribe's suggestions indicate correct or popular phrases to use.\r\n\r\nvim-google-scribe requires an installation of Vim compiled with python support.\r\n","install_details":"If you don't have a preferred installation method, I recommend installing pathogen.vim, and then simply copy and paste:\r\n\r\ncd ~\/.vim\/bundle\r\ngit clone git:\/\/github.com\/epiloque\/vim-google-scribe.git","5":"If you don't have a preferred installation method, I recommend installing pathogen.vim, and then simply copy and paste:\r\n\r\ncd ~\/.vim\/bundle\r\ngit clone git:\/\/github.com\/epiloque\/vim-google-scribe.git","first_name":"Mark","6":"Mark","last_name":"Milstein","7":"Milstein","releases":[{"0":"3763","vim_version":"7.0","1":"7.0","script_version":"0.1.0","2":"0.1.0","version_comment":"Initial upload","3":"Initial upload","package":"googlescribe.vim","4":"googlescribe.vim","src_id":"16627","5":"16627","creation_date":"1317896521","6":"1317896521"}]},"3762":{"script_id":"3762","0":"3762","script_name":"Speech","1":"Speech","script_type":"utility","2":"utility","summary":"Speech to text and text to speech via google speech api","3":"Speech to text and text to speech via google speech api","description":"Speech.vim - Speech to text and text to speech via google speech api.\r\nCopyright (C) <2011>  Onur Aslan  <onur@onur.im>\r\n\r\nSpeech to text:\r\n<Leader>r for record your voice and press again to convert to text and\r\nappend after cursor.\r\n\r\nText to speech:\r\n<Leader>s to get speech of your current line.\r\n\r\nRequiments: In order to run this script, you need ffmpeg (with flac\r\nencode support), wget and mplayer. This also works under UNIX like\r\nsystems.\r\n\r\nThis script uses ALSA to record your voice. If you have trouble when\r\nyou recording your voice, try to change SpechHwId variable. It comes\r\nwith hw:0,0 default. You can test your hw id with:\r\n\r\nffmpeg -f alsa -ar 16000 -ac 2 -i hw:0,0 -acodec flac -ab 96k out.flac\r\n\r\n'arecord -l' will give you list of audio devices.\r\n\r\nYou can change language with SpeechLang variable.\r\n\r\nLICENSE:\r\n\r\nThis program is free software: you can redistribute it and\/or modify\r\nit under the terms of the GNU General Public License as published by\r\nthe Free Software Foundation, either version 3 of the License, or\r\n(at your option) any later version.\r\n\r\nThis program is distributed in the hope that it will be useful,\r\nbut WITHOUT ANY WARRANTY; without even the implied warranty of\r\nMERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the\r\nGNU General Public License for more details.\r\n\r\nYou should have received a copy of the GNU General Public License\r\nalong with this program.  If not, see <http:\/\/www.gnu.org\/licenses\/>.\r\n","4":"Speech.vim - Speech to text and text to speech via google speech api.\r\nCopyright (C) <2011>  Onur Aslan  <onur@onur.im>\r\n\r\nSpeech to text:\r\n<Leader>r for record your voice and press again to convert to text and\r\nappend after cursor.\r\n\r\nText to speech:\r\n<Leader>s to get speech of your current line.\r\n\r\nRequiments: In order to run this script, you need ffmpeg (with flac\r\nencode support), wget and mplayer. This also works under UNIX like\r\nsystems.\r\n\r\nThis script uses ALSA to record your voice. If you have trouble when\r\nyou recording your voice, try to change SpechHwId variable. It comes\r\nwith hw:0,0 default. You can test your hw id with:\r\n\r\nffmpeg -f alsa -ar 16000 -ac 2 -i hw:0,0 -acodec flac -ab 96k out.flac\r\n\r\n'arecord -l' will give you list of audio devices.\r\n\r\nYou can change language with SpeechLang variable.\r\n\r\nLICENSE:\r\n\r\nThis program is free software: you can redistribute it and\/or modify\r\nit under the terms of the GNU General Public License as published by\r\nthe Free Software Foundation, either version 3 of the License, or\r\n(at your option) any later version.\r\n\r\nThis program is distributed in the hope that it will be useful,\r\nbut WITHOUT ANY WARRANTY; without even the implied warranty of\r\nMERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the\r\nGNU General Public License for more details.\r\n\r\nYou should have received a copy of the GNU General Public License\r\nalong with this program.  If not, see <http:\/\/www.gnu.org\/licenses\/>.\r\n","install_details":"","5":"","first_name":"Onur","6":"Onur","last_name":"Aslan","7":"Aslan","releases":[{"0":"3762","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"speech.vim","4":"speech.vim","src_id":"16624","5":"16624","creation_date":"1317831937","6":"1317831937"}]},"3761":{"script_id":"3761","0":"3761","script_name":"slide show","1":"slide show","script_type":"utility","2":"utility","summary":"A tool for viewing source code in a slide show fashion.","3":"A tool for viewing source code in a slide show fashion.","description":"I often need to review others code to get a quick idea if the developers are doing the proper job.  It's tedious when going through hundreds of files manually.  I finally came up with this script, which you need to find\/grep the interested files, and feed them to vim.\r\n\r\nFor example to review author Cary's source files:\r\n\r\nIn command line,\r\nvim +\"so ~\/.vim\/SlideShow.vim\" `grep -liR \"Cary\" * | grep -v .svn | grep \".java\" | sort`\r\n\r\nIn vim, press <Space> to start the slide show.","4":"I often need to review others code to get a quick idea if the developers are doing the proper job.  It's tedious when going through hundreds of files manually.  I finally came up with this script, which you need to find\/grep the interested files, and feed them to vim.\r\n\r\nFor example to review author Cary's source files:\r\n\r\nIn command line,\r\nvim +\"so ~\/.vim\/SlideShow.vim\" `grep -liR \"Cary\" * | grep -v .svn | grep \".java\" | sort`\r\n\r\nIn vim, press <Space> to start the slide show.","install_details":"","5":"","first_name":"Yiu","6":"Yiu","last_name":"Wing","7":"Wing","releases":[{"0":"3761","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"SlideShow.vim","4":"SlideShow.vim","src_id":"16621","5":"16621","creation_date":"1317774187","6":"1317774187"}]},"3760":{"script_id":"3760","0":"3760","script_name":"vim-dokuwiki","1":"vim-dokuwiki","script_type":"syntax","2":"syntax","summary":"syntax highlighting for dokuwiki","3":"syntax highlighting for dokuwiki","description":"a new syntax highlighting plugin for editing dokuwiki pages with vim.\r\n\r\ndevelopment\/issue tracker\/feedback: https:\/\/github.com\/nblock\/vim-dokuwiki","4":"a new syntax highlighting plugin for editing dokuwiki pages with vim.\r\n\r\ndevelopment\/issue tracker\/feedback: https:\/\/github.com\/nblock\/vim-dokuwiki","install_details":"vim-dokuwiki - a VIM syntax file for DokuWiki\r\n\r\nhow to install:\r\n1) copy 'syntax\/dokuwiki.vim' in your '~\/.vim\/syntax\/'\r\n2) enable by issuing ':set ft=dokuwiki'\r\n\r\nIf you want to enable the comment plugin highlighting, assign\r\nany value to the 'dokuwiki_comment' variable. Example:\r\n  :let dokuwiki_comment=1\r\nTo disable it use \":unlet\". Example:\r\n  :unlet dokuwiki_comment\r\n\r\nSyntax highlighting between code blocks can be enabled by adding the\r\nappropriate language to the 'dokuwiki_fenced_languages' variable in your\r\n.vimrc. Example:\r\n  :let g:dokuwiki_fenced_languages = ['c', 'python', 'html']\r\n","5":"vim-dokuwiki - a VIM syntax file for DokuWiki\r\n\r\nhow to install:\r\n1) copy 'syntax\/dokuwiki.vim' in your '~\/.vim\/syntax\/'\r\n2) enable by issuing ':set ft=dokuwiki'\r\n\r\nIf you want to enable the comment plugin highlighting, assign\r\nany value to the 'dokuwiki_comment' variable. Example:\r\n  :let dokuwiki_comment=1\r\nTo disable it use \":unlet\". Example:\r\n  :unlet dokuwiki_comment\r\n\r\nSyntax highlighting between code blocks can be enabled by adding the\r\nappropriate language to the 'dokuwiki_fenced_languages' variable in your\r\n.vimrc. Example:\r\n  :let g:dokuwiki_fenced_languages = ['c', 'python', 'html']\r\n","first_name":"Florian","6":"Florian","last_name":"Preinstorfer","7":"Preinstorfer","releases":[{"0":"3760","vim_version":"7.0","1":"7.0","script_version":"0.5","2":"0.5","version_comment":"Improved fold styling, syntax-based folding, code highlighting between code blocks, conceal chars, code cleanup, and fixes (thx @ Jonathan Beverley).","3":"Improved fold styling, syntax-based folding, code highlighting between code blocks, conceal chars, code cleanup, and fixes (thx @ Jonathan Beverley).","package":"dokuwiki.vim","4":"dokuwiki.vim","src_id":"25038","5":"25038","creation_date":"1489820394","6":"1489820394"},{"0":"3760","vim_version":"7.0","1":"7.0","script_version":"0.4","2":"0.4","version_comment":"A lot of fixes and new features such as better table and code block support (thx @Vladimir Zhbanov).","3":"A lot of fixes and new features such as better table and code block support (thx @Vladimir Zhbanov).","package":"dokuwiki.vim","4":"dokuwiki.vim","src_id":"18022","5":"18022","creation_date":"1337803585","6":"1337803585"},{"0":"3760","vim_version":"7.0","1":"7.0","script_version":"0.3","2":"0.3","version_comment":"various bugfixes (thx hougp and Vladimir Zhbanov)","3":"various bugfixes (thx hougp and Vladimir Zhbanov)","package":"dokuwiki.vim","4":"dokuwiki.vim","src_id":"17561","5":"17561","creation_date":"1330890734","6":"1330890734"},{"0":"3760","vim_version":"7.0","1":"7.0","script_version":"0.2","2":"0.2","version_comment":"add combinations of markup elements (thx to hougp)","3":"add combinations of markup elements (thx to hougp)","package":"dokuwiki.vim","4":"dokuwiki.vim","src_id":"17144","5":"17144","creation_date":"1325519782","6":"1325519782"},{"0":"3760","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"dokuwiki.vim","4":"dokuwiki.vim","src_id":"16618","5":"16618","creation_date":"1317730305","6":"1317730305"}]},"3759":{"script_id":"3759","0":"3759","script_name":"White","1":"White","script_type":"color scheme","2":"color scheme","summary":"color scheme only two colors","3":"color scheme only two colors","description":"White plugin is simple color very use and modify\r\n\r\nComplete support languages\r\nPython\r\njavascript\r\nCSS\r\nHTML\r\nVim language and more.","4":"White plugin is simple color very use and modify\r\n\r\nComplete support languages\r\nPython\r\njavascript\r\nCSS\r\nHTML\r\nVim language and more.","install_details":"copy ~\/.vim\/colors\/\r\nadd in your .vimrc -> colorscheme = white","5":"copy ~\/.vim\/colors\/\r\nadd in your .vimrc -> colorscheme = white","first_name":"Ronan","6":"Ronan","last_name":"Neto","7":"Neto","releases":[{"0":"3759","vim_version":"7.0","1":"7.0","script_version":"0.5","2":"0.5","version_comment":"Initial upload","3":"Initial upload","package":"white.vim","4":"white.vim","src_id":"16606","5":"16606","creation_date":"1317403050","6":"1317403050"}]},"3758":{"script_id":"3758","0":"3758","script_name":"Ambient Theme","1":"Ambient Theme","script_type":"utility","2":"utility","summary":"Sets your theme's background based on ambient light","3":"Sets your theme's background based on ambient light","description":"Sets your vim theme's background based on ambient light.\r\n\r\nWORKS ON OS X ONLY.\r\n\r\nThe plugin switches the background variable from light to dark. Works smoothly with solarized.\r\n\r\n# Limitations\r\n\r\nVim doesn't have a timer. So this uses a hack which only works in Normal mode. That means the theme will switch after you exit Insert mode.\r\n\r\n# Configuration\r\n\r\ng:AmbientLightThreshold is the sensor value which triggers the switch. The default is 100000; you can experiment yourself if you want.\r\n\r\necho g:LightSensorValue will let you see the current value.\r\n\r\n# Compiling the binary yourself\r\n\r\nThere's a binary that reads the light sensor value. It is precompiled for OSX 10.5 and later.\r\n\r\nYou'll need gcc to compile it IF YOU HAVE OSX 10.4 OR LESS. Otherwise, it's as simple as:\r\n\r\nmake clean; make\r\n\r\n---\r\n\r\nGit repository: https:\/\/github.com\/leonid-shevtsov\/ambient_theme.vim","4":"Sets your vim theme's background based on ambient light.\r\n\r\nWORKS ON OS X ONLY.\r\n\r\nThe plugin switches the background variable from light to dark. Works smoothly with solarized.\r\n\r\n# Limitations\r\n\r\nVim doesn't have a timer. So this uses a hack which only works in Normal mode. That means the theme will switch after you exit Insert mode.\r\n\r\n# Configuration\r\n\r\ng:AmbientLightThreshold is the sensor value which triggers the switch. The default is 100000; you can experiment yourself if you want.\r\n\r\necho g:LightSensorValue will let you see the current value.\r\n\r\n# Compiling the binary yourself\r\n\r\nThere's a binary that reads the light sensor value. It is precompiled for OSX 10.5 and later.\r\n\r\nYou'll need gcc to compile it IF YOU HAVE OSX 10.4 OR LESS. Otherwise, it's as simple as:\r\n\r\nmake clean; make\r\n\r\n---\r\n\r\nGit repository: https:\/\/github.com\/leonid-shevtsov\/ambient_theme.vim","install_details":"Requires OS X >=10.5 and an ambient light sensor (like on a MacBook).\r\n\r\nJust copy the plugin to your vim path and restart, or use pathogen","5":"Requires OS X >=10.5 and an ambient light sensor (like on a MacBook).\r\n\r\nJust copy the plugin to your vim path and restart, or use pathogen","first_name":"Leonid","6":"Leonid","last_name":"Shevtsov","7":"Shevtsov","releases":[{"0":"3758","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"ambient_theme.tar.gz","4":"ambient_theme.tar.gz","src_id":"16605","5":"16605","creation_date":"1317390581","6":"1317390581"}]},"3757":{"script_id":"3757","0":"3757","script_name":"racket-auto-keywords.vim","1":"racket-auto-keywords.vim","script_type":"utility","2":"utility","summary":"Populates syntax keyword racketFunc\/racketSyntax\/scribbleMarkup","3":"Populates syntax keyword racketFunc\/racketSyntax\/scribbleMarkup","description":"This script works with racket.vim (and scribble.vim if you have it [vimscript #3756]) to automatically populate the syntax keywords lists\r\n\r\nIssues:\r\n* Currently, I can't get this to run in an autocommand, so I have it bound using control-F4\r\n\r\n* Anyone who can get this to work with scribble.vim, without vim SEGVing -- please contact me.","4":"This script works with racket.vim (and scribble.vim if you have it [vimscript #3756]) to automatically populate the syntax keywords lists\r\n\r\nIssues:\r\n* Currently, I can't get this to run in an autocommand, so I have it bound using control-F4\r\n\r\n* Anyone who can get this to work with scribble.vim, without vim SEGVing -- please contact me.","install_details":"Install it in ~\/.vim\/scripts\r\n\r\nUse the binding:\r\n\r\nmap <C-F4> :runtime scripts\/racket-auto-syntax.vim\r\n\r\nin your .vimrc","5":"Install it in ~\/.vim\/scripts\r\n\r\nUse the binding:\r\n\r\nmap <C-F4> :runtime scripts\/racket-auto-syntax.vim\r\n\r\nin your .vimrc","first_name":"Tim","6":"Tim","last_name":"Brown","7":"Brown","releases":[{"0":"3757","vim_version":"7.0","1":"7.0","script_version":"1.1","2":"1.1","version_comment":"Initial upload","3":"Initial upload","package":"racket-auto-keywords.vim","4":"racket-auto-keywords.vim","src_id":"16604","5":"16604","creation_date":"1317385535","6":"1317385535"}]},"3756":{"script_id":"3756","0":"3756","script_name":"scribble.vim","1":"scribble.vim","script_type":"syntax","2":"syntax","summary":"Syntax for scribble (http:\/\/docs.racket-lang.org\/scribble\/index.html)","3":"Syntax for scribble (http:\/\/docs.racket-lang.org\/scribble\/index.html)","description":"Scribble allows for mixing of racket code with plain text using an\r\nat-expression syntax.\r\n\r\nUse this to get some kind of sanity to your scribble-in-vim sessions!\r\n\r\n** USE  https:\/\/github.com\/wlangstroth\/vim-racket --\r\n** Use racket.vim from this package (and probably the rest of the package)\r\n** Don't use vimscript #3755 -- vim-racket is much more fulfilling!\r\n\r\nDO look at vimscript #3757 -- it too is cheap and cheerful -- but with potential, I hope\r\n\r\nSame comments apply as to (my now deprecated) racket.vim:\r\n  * high degree of both cheapness and cheerfulness\r\n  * works-for-me -- and I'll share it in this state because\r\n  * ... it gets me off the ground with this\r\n","4":"Scribble allows for mixing of racket code with plain text using an\r\nat-expression syntax.\r\n\r\nUse this to get some kind of sanity to your scribble-in-vim sessions!\r\n\r\n** USE  https:\/\/github.com\/wlangstroth\/vim-racket --\r\n** Use racket.vim from this package (and probably the rest of the package)\r\n** Don't use vimscript #3755 -- vim-racket is much more fulfilling!\r\n\r\nDO look at vimscript #3757 -- it too is cheap and cheerful -- but with potential, I hope\r\n\r\nSame comments apply as to (my now deprecated) racket.vim:\r\n  * high degree of both cheapness and cheerfulness\r\n  * works-for-me -- and I'll share it in this state because\r\n  * ... it gets me off the ground with this\r\n","install_details":"Copy script into ~\/.vim\/syntax\r\n\r\nAdd the following to ~\/vim\/filetype.vim:\r\nau! BufRead,BufNewFile *.scrbl setfiletype scribble","5":"Copy script into ~\/.vim\/syntax\r\n\r\nAdd the following to ~\/vim\/filetype.vim:\r\nau! BufRead,BufNewFile *.scrbl setfiletype scribble","first_name":"Tim","6":"Tim","last_name":"Brown","7":"Brown","releases":[{"0":"3756","vim_version":"7.0","1":"7.0","script_version":"1.2","2":"1.2","version_comment":"Added as many scribble keywords as I could find from (require scribble\/...)!","3":"Added as many scribble keywords as I could find from (require scribble\/...)!","package":"scribble.vim","4":"scribble.vim","src_id":"16599","5":"16599","creation_date":"1317292643","6":"1317292643"},{"0":"3756","vim_version":"7.0","1":"7.0","script_version":"1.1","2":"1.1","version_comment":"Initial upload","3":"Initial upload","package":"scribble.vim","4":"scribble.vim","src_id":"16598","5":"16598","creation_date":"1317220913","6":"1317220913"}]},"3755":{"script_id":"3755","0":"3755","script_name":"racket.vim","1":"racket.vim","script_type":"syntax","2":"syntax","summary":"Simple syntax for racket (http:\/\/racket-lang.org)","3":"Simple syntax for racket (http:\/\/racket-lang.org)","description":"OBSOLETE\r\n------------------------------------------------------\r\nUSE  https:\/\/github.com\/wlangstroth\/vim-racket --\r\nUse racket.vim from this package (and probably the rest of the package)\r\n\r\nIt works with scribble.vim (vimscript #3756)\r\n------------------------------------------------------\r\n\r\n\r\n\r\nThis is a cheap and cheerful syntax for racket's \"scheme\" language.\r\n\r\nIt's just to get me off the ground, and it borrows heavily from (using\r\n:source, to be frank) scheme.vim\r\n\r\nIt's very much a works-for-me script.\r\nAs it grows, I'll share.\r\n\r\nThis syntax was written to smooth over some bumps for scribble.vim\r\n(vimscript #3756)\r\n","4":"OBSOLETE\r\n------------------------------------------------------\r\nUSE  https:\/\/github.com\/wlangstroth\/vim-racket --\r\nUse racket.vim from this package (and probably the rest of the package)\r\n\r\nIt works with scribble.vim (vimscript #3756)\r\n------------------------------------------------------\r\n\r\n\r\n\r\nThis is a cheap and cheerful syntax for racket's \"scheme\" language.\r\n\r\nIt's just to get me off the ground, and it borrows heavily from (using\r\n:source, to be frank) scheme.vim\r\n\r\nIt's very much a works-for-me script.\r\nAs it grows, I'll share.\r\n\r\nThis syntax was written to smooth over some bumps for scribble.vim\r\n(vimscript #3756)\r\n","install_details":"Copy script into ~\/.vim\/syntax\r\n\r\nAdd the following to ~\/vim\/filetype.vim:\r\nau! BufRead,BufNewFile *.ss\tsetfiletype racket\r\nau! BufRead,BufNewFile *.rkt\tsetfiletype racket\r\n","5":"Copy script into ~\/.vim\/syntax\r\n\r\nAdd the following to ~\/vim\/filetype.vim:\r\nau! BufRead,BufNewFile *.ss\tsetfiletype racket\r\nau! BufRead,BufNewFile *.rkt\tsetfiletype racket\r\n","first_name":"Tim","6":"Tim","last_name":"Brown","7":"Brown","releases":[{"0":"3755","vim_version":"7.0","1":"7.0","script_version":"1.1","2":"1.1","version_comment":"Initial upload","3":"Initial upload","package":"racket.vim","4":"racket.vim","src_id":"16597","5":"16597","creation_date":"1317220576","6":"1317220576"}]},"3754":{"script_id":"3754","0":"3754","script_name":"baancomplete","1":"baancomplete","script_type":"ftplugin","2":"ftplugin","summary":"Omni completion for the baan scripting language","3":"Omni completion for the baan scripting language","description":"Baan omni completion for vim\r\n\r\nFeatures:\r\n    Function argument completion\r\n    completeopt+=preview support, displaying DllUsage\/EndDllUsage comments\r\n\r\nIf you have any issues or suggestions please visit the github page (https:\/\/github.com\/mfussenegger\/baancomplete) and open an issue.","4":"Baan omni completion for vim\r\n\r\nFeatures:\r\n    Function argument completion\r\n    completeopt+=preview support, displaying DllUsage\/EndDllUsage comments\r\n\r\nIf you have any issues or suggestions please visit the github page (https:\/\/github.com\/mfussenegger\/baancomplete) and open an issue.","install_details":"Installation via pathogen is recommended.\r\n\r\nFor more details refer to the readme on github (https:\/\/github.com\/mfussenegger\/baancomplete)","5":"Installation via pathogen is recommended.\r\n\r\nFor more details refer to the readme on github (https:\/\/github.com\/mfussenegger\/baancomplete)","first_name":"Mathias","6":"Mathias","last_name":"Fussenegger","7":"Fussenegger","releases":[{"0":"3754","vim_version":"7.0","1":"7.0","script_version":"0.2","2":"0.2","version_comment":"improvements to gen_api and code cleanups","3":"improvements to gen_api and code cleanups","package":"baancomplete.tar.gz","4":"baancomplete.tar.gz","src_id":"17464","5":"17464","creation_date":"1329257830","6":"1329257830"},{"0":"3754","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"baancomplete.tar.gz","4":"baancomplete.tar.gz","src_id":"16575","5":"16575","creation_date":"1316978592","6":"1316978592"}]},"3753":{"script_id":"3753","0":"3753","script_name":"vim-pad","1":"vim-pad","script_type":"utility","2":"utility","summary":"a quick-notetaking plugin","3":"a quick-notetaking plugin","description":"There are many notetaking plugins for vim. Most of them depend on your notes\r\nhaving a certain format for the convenience of highlighting stuff like headers,\r\nlists and links. Also mostly, they don't provide a workflow for your notetaking:\r\nyou need to create manually a file to put your notes on and save it somewhere\r\nwith a name that hopefully makes sense (ever saved a note and then updated its\r\ncontents so the filename no longer applied?). Usually too, taking notes is\r\ndisruptive of whatever you are doing: imagine you're coding and have an idea you\r\nthink you might use afterwards. Ideally, you could just take the note right\r\nthere, without needing to travel to your notes, or cluttering your filesystem.\r\n\r\n*vim-pad* tries to solve those issues, by focusing on a definite workflow.\r\nFirst, it makes it so you can at any moment (in insert and normal mode):\r\n\r\n- open your notes.\r\n- search in your notes.\r\n- create a new note.\r\n\r\nAlso, it keeps the filename issue away by:\r\n\r\n- naming your files after the time you created them. This makes them unique and\r\n  allows for easy sorting. The filenames are updated when changes are made in\r\n  old files, so the date is always equal to the last time you modified your\r\n  notes.\r\n- considering the first line of your document as its title. This is in tune with\r\n  the way most markup styles work (e.g., markdown)\r\n\r\nvim-pad doesn't specify a format for your notes. Instead, it uses a default,\r\nwhich you can configure, and allows the use of modelines. Esentially, this\r\nmeans your notes can be free-form, and you can adapt them to your needs.","4":"There are many notetaking plugins for vim. Most of them depend on your notes\r\nhaving a certain format for the convenience of highlighting stuff like headers,\r\nlists and links. Also mostly, they don't provide a workflow for your notetaking:\r\nyou need to create manually a file to put your notes on and save it somewhere\r\nwith a name that hopefully makes sense (ever saved a note and then updated its\r\ncontents so the filename no longer applied?). Usually too, taking notes is\r\ndisruptive of whatever you are doing: imagine you're coding and have an idea you\r\nthink you might use afterwards. Ideally, you could just take the note right\r\nthere, without needing to travel to your notes, or cluttering your filesystem.\r\n\r\n*vim-pad* tries to solve those issues, by focusing on a definite workflow.\r\nFirst, it makes it so you can at any moment (in insert and normal mode):\r\n\r\n- open your notes.\r\n- search in your notes.\r\n- create a new note.\r\n\r\nAlso, it keeps the filename issue away by:\r\n\r\n- naming your files after the time you created them. This makes them unique and\r\n  allows for easy sorting. The filenames are updated when changes are made in\r\n  old files, so the date is always equal to the last time you modified your\r\n  notes.\r\n- considering the first line of your document as its title. This is in tune with\r\n  the way most markup styles work (e.g., markdown)\r\n\r\nvim-pad doesn't specify a format for your notes. Instead, it uses a default,\r\nwhich you can configure, and allows the use of modelines. Esentially, this\r\nmeans your notes can be free-form, and you can adapt them to your needs.","install_details":"The most recent version of the plugin will always be available from https:\/\/github.com\/fmoralesc\/vim-pad","5":"The most recent version of the plugin will always be available from https:\/\/github.com\/fmoralesc\/vim-pad","first_name":"Felipe","6":"Felipe","last_name":"Morales","7":"Morales","releases":[{"0":"3753","vim_version":"7.4","1":"7.4","script_version":"1.1","2":"1.1","version_comment":"* Allow mappings to be set independently\r\n* Some fixes","3":"* Allow mappings to be set independently\r\n* Some fixes","package":"vim-pad_1.1.zip","4":"vim-pad_1.1.zip","src_id":"22761","5":"22761","creation_date":"1420643507","6":"1420643507"},{"0":"3753","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"mayor update.\r\n\r\n* changed the interface so it's all under the :Pad command\r\n* support local notes\r\n* support ag, and pt backends, improved grep and ack ones.\r\n* added a tutorial using vim-tutor-mode's[1] format.\r\n\r\n[1]: https:\/\/github.com\/fmoralesc\/vim-tutor-mode","3":"mayor update.\r\n\r\n* changed the interface so it's all under the :Pad command\r\n* support local notes\r\n* support ag, and pt backends, improved grep and ack ones.\r\n* added a tutorial using vim-tutor-mode's[1] format.\r\n\r\n[1]: https:\/\/github.com\/fmoralesc\/vim-tutor-mode","package":"vim-pad_1.0.zip","4":"vim-pad_1.0.zip","src_id":"22754","5":"22754","creation_date":"1420416914","6":"1420416914"},{"0":"3753","vim_version":"7.0","1":"7.0","script_version":"0.9.1","2":"0.9.1","version_comment":"Gathers last year fixes. We haven't had a release in a while, we might as well update it now.","3":"Gathers last year fixes. We haven't had a release in a while, we might as well update it now.","package":"vim-pad_0.9.1.zip","4":"vim-pad_0.9.1.zip","src_id":"21410","5":"21410","creation_date":"1391192570","6":"1391192570"},{"0":"3753","vim_version":"7.0","1":"7.0","script_version":"0.9","2":"0.9","version_comment":"* adds support for file extensions.\r\n* searches now query subfolder names too.\r\n* OpenPad accepts an argument to insert the first line in the new notes.\r\n* Several fixes.","3":"* adds support for file extensions.\r\n* searches now query subfolder names too.\r\n* OpenPad accepts an argument to insert the first line in the new notes.\r\n* Several fixes.","package":"vim-pad-0.9.tar.gz","4":"vim-pad-0.9.tar.gz","src_id":"19075","5":"19075","creation_date":"1354407599","6":"1354407599"},{"0":"3753","vim_version":"7.0","1":"7.0","script_version":"0.8b","2":"0.8b","version_comment":"* added support for archiving.\r\n\r\n* vim-pad's window can now be opened at the right too.\r\n\r\n* changed highlighting for list, for better readability and updated features.\r\n\r\n* mappings are created for normal mode only by default (see docs).","3":"* added support for archiving.\r\n\r\n* vim-pad's window can now be opened at the right too.\r\n\r\n* changed highlighting for list, for better readability and updated features.\r\n\r\n* mappings are created for normal mode only by default (see docs).","package":"vim-pad-0.8b.zip","4":"vim-pad-0.8b.zip","src_id":"18324","5":"18324","creation_date":"1343363276","6":"1343363276"},{"0":"3753","vim_version":"7.0","1":"7.0","script_version":"0.7","2":"0.7","version_comment":"Releasing the changes in the devel branch. Most notably, the ability to sort the notes.","3":"Releasing the changes in the devel branch. Most notably, the ability to sort the notes.","package":"vim-pad_0.7.zip","4":"vim-pad_0.7.zip","src_id":"17945","5":"17945","creation_date":"1336920060","6":"1336920060"},{"0":"3753","vim_version":"7.0","1":"7.0","script_version":"0.6","2":"0.6","version_comment":"Improved Windows compatibility.","3":"Improved Windows compatibility.","package":"vim-pad_0.6.zip","4":"vim-pad_0.6.zip","src_id":"17156","5":"17156","creation_date":"1325793192","6":"1325793192"},{"0":"3753","vim_version":"7.0","1":"7.0","script_version":"0.5.3","2":"0.5.3","version_comment":"* Fixed mappings for the terminal version of vim.\r\n\r\n* Updated documentation.\r\n ","3":"* Fixed mappings for the terminal version of vim.\r\n\r\n* Updated documentation.\r\n ","package":"vim-pad_0.5.3.zip","4":"vim-pad_0.5.3.zip","src_id":"16848","5":"16848","creation_date":"1320983810","6":"1320983810"},{"0":"3753","vim_version":"7.0","1":"7.0","script_version":"0.5.2","2":"0.5.2","version_comment":"* Created new mappings for the terminal, deprecated g:pad_custom_mappings.\r\n* The cache isn't updated on searches anymore.\r\n* Code cleanups and commenting.","3":"* Created new mappings for the terminal, deprecated g:pad_custom_mappings.\r\n* The cache isn't updated on searches anymore.\r\n* Code cleanups and commenting.","package":"vim-pad-0.5.2.zip","4":"vim-pad-0.5.2.zip","src_id":"16819","5":"16819","creation_date":"1320668436","6":"1320668436"},{"0":"3753","vim_version":"7.0","1":"7.0","script_version":"0.5.1","2":"0.5.1","version_comment":"Some bugfixes and tweaks.","3":"Some bugfixes and tweaks.","package":"vim-pad_0.5.1.zip","4":"vim-pad_0.5.1.zip","src_id":"16804","5":"16804","creation_date":"1320437318","6":"1320437318"},{"0":"3753","vim_version":"7.0","1":"7.0","script_version":"0.5","2":"0.5","version_comment":"Adding some caching, so there are less IO operations.","3":"Adding some caching, so there are less IO operations.","package":"vim-pad_0.5.zip","4":"vim-pad_0.5.zip","src_id":"16799","5":"16799","creation_date":"1320369625","6":"1320369625"},{"0":"3753","vim_version":"7.0","1":"7.0","script_version":"0.4.1","2":"0.4.1","version_comment":"Fixed some bugs that might affect new users.\r\n\r\nImproved documentation.","3":"Fixed some bugs that might affect new users.\r\n\r\nImproved documentation.","package":"vim-pad-0.4.1.zip","4":"vim-pad-0.4.1.zip","src_id":"16594","5":"16594","creation_date":"1317142444","6":"1317142444"},{"0":"3753","vim_version":"7.0","1":"7.0","script_version":"0.4","2":"0.4","version_comment":"Updated highlighting. \r\n\r\nPressing enter after a search without matches will create a new note with the query in the first line.","3":"Updated highlighting. \r\n\r\nPressing enter after a search without matches will create a new note with the query in the first line.","package":"vim-pad-0.4.zip","4":"vim-pad-0.4.zip","src_id":"16577","5":"16577","creation_date":"1316993908","6":"1316993908"},{"0":"3753","vim_version":"7.0","1":"7.0","script_version":"0.3.2","2":"0.3.2","version_comment":"Several fixes and improvements.","3":"Several fixes and improvements.","package":"vim-pad-0.3.2.zip","4":"vim-pad-0.3.2.zip","src_id":"16576","5":"16576","creation_date":"1316980034","6":"1316980034"},{"0":"3753","vim_version":"7.0","1":"7.0","script_version":"0.3.1","2":"0.3.1","version_comment":"Several improvements and tweaks.","3":"Several improvements and tweaks.","package":"vim-pad.zip","4":"vim-pad.zip","src_id":"16572","5":"16572","creation_date":"1316958911","6":"1316958911"},{"0":"3753","vim_version":"7.0","1":"7.0","script_version":"0.2","2":"0.2","version_comment":"Initial upload","3":"Initial upload","package":"vim-pad_0.2.zip","4":"vim-pad_0.2.zip","src_id":"16570","5":"16570","creation_date":"1316904624","6":"1316904624"}]},"3752":{"script_id":"3752","0":"3752","script_name":"Vimpy","1":"Vimpy","script_type":"utility","2":"utility","summary":"Vimpy helps in Navigating through Python code easy.","3":"Vimpy helps in Navigating through Python code easy.","description":"This Vim plugin is to make navigation of Python files easier with Vim. If you have a large python project, navigating to multiple files is not easy currently. There are various ways to make it easier like using ctags\/ptags, gf over the python path etc. But it does not work well with multiple files with same name, going to a praticular class\/function etc.\r\n\r\nFeatures\r\n--------\r\n\r\nCurrently it provides two functions - Open and Goto.\r\nOpen can be used to open any python module in the project by module name, class name or function.\r\nGoto can be used to goto any python module in the project by the token in the current file by module name, class name or function.\r\n\r\nUsage\r\n-----\r\nUsage is similar to how ctags\/ptags work in Vim. Basically there are 2 steps:\r\n\r\n1. Create the index file. Use :VimpyCreate <project-name> path [exclude-path] to create index. (Alternatively, the vimpy.py script can be invoked using python to create the index file. See 'python vimpy.py' for usage.) This is a one time operation. The index will be automatically updated if you edit the files using vim, otherwise this can be rerun and only the changed files will be updated.\r\n2. Load the index file in Vim. This can be done using ':VimpyLoad <file-name>' inside Vim. This can automated by adding in the vimrc. Now it is ready to use! Following commands (the Keybindings can be changed in vimpy.vim) can be used to navigate to any desired module:\r\n    - <leader> om : Open Module. Go to a module with a given name. \r\n    - <leader> oc : Open Class. Go to a class with a given name. \r\n    - <leader> of : Open Function. Go to a funtion with a given name. \r\n    - <leader> gm : Goto Module given by word under cursor (Eg. use this to navigate to a module under an 'import' statement).\r\n    - <leader> gc : Goto Class given by word under cursor. \r\n    - <leader> gf : Goto Function given by word under cursor. \r\n\r\nAll of them has auto completion support, so you just need to type in few characters and press <tab>\r\nSee https:\/\/github.com\/amitdev\/vimpy for updates on this.\r\n","4":"This Vim plugin is to make navigation of Python files easier with Vim. If you have a large python project, navigating to multiple files is not easy currently. There are various ways to make it easier like using ctags\/ptags, gf over the python path etc. But it does not work well with multiple files with same name, going to a praticular class\/function etc.\r\n\r\nFeatures\r\n--------\r\n\r\nCurrently it provides two functions - Open and Goto.\r\nOpen can be used to open any python module in the project by module name, class name or function.\r\nGoto can be used to goto any python module in the project by the token in the current file by module name, class name or function.\r\n\r\nUsage\r\n-----\r\nUsage is similar to how ctags\/ptags work in Vim. Basically there are 2 steps:\r\n\r\n1. Create the index file. Use :VimpyCreate <project-name> path [exclude-path] to create index. (Alternatively, the vimpy.py script can be invoked using python to create the index file. See 'python vimpy.py' for usage.) This is a one time operation. The index will be automatically updated if you edit the files using vim, otherwise this can be rerun and only the changed files will be updated.\r\n2. Load the index file in Vim. This can be done using ':VimpyLoad <file-name>' inside Vim. This can automated by adding in the vimrc. Now it is ready to use! Following commands (the Keybindings can be changed in vimpy.vim) can be used to navigate to any desired module:\r\n    - <leader> om : Open Module. Go to a module with a given name. \r\n    - <leader> oc : Open Class. Go to a class with a given name. \r\n    - <leader> of : Open Function. Go to a funtion with a given name. \r\n    - <leader> gm : Goto Module given by word under cursor (Eg. use this to navigate to a module under an 'import' statement).\r\n    - <leader> gc : Goto Class given by word under cursor. \r\n    - <leader> gf : Goto Function given by word under cursor. \r\n\r\nAll of them has auto completion support, so you just need to type in few characters and press <tab>\r\nSee https:\/\/github.com\/amitdev\/vimpy for updates on this.\r\n","install_details":"Extract vimpy.zip to your vim plugins folder.\r\n","5":"Extract vimpy.zip to your vim plugins folder.\r\n","first_name":"Amit","6":"Amit","last_name":"Ranjit","7":"Ranjit","releases":[{"0":"3752","vim_version":"7.0","1":"7.0","script_version":"0.2","2":"0.2","version_comment":"Automated indexing. Just use ':VimpyCreate' to create index initially and ':VimpyLoad' to load it. As long as the files are edited with vim while the project is loaded, index is always kept up to date.","3":"Automated indexing. Just use ':VimpyCreate' to create index initially and ':VimpyLoad' to load it. As long as the files are edited with vim while the project is loaded, index is always kept up to date.","package":"vimpy.zip","4":"vimpy.zip","src_id":"17036","5":"17036","creation_date":"1323362169","6":"1323362169"},{"0":"3752","vim_version":"7.2","1":"7.2","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"vimpy.zip","4":"vimpy.zip","src_id":"16559","5":"16559","creation_date":"1316605652","6":"1316605652"}]},"3751":{"script_id":"3751","0":"3751","script_name":"google_prettify.vim","1":"google_prettify.vim","script_type":"color scheme","2":"color scheme","summary":"a color scheme mimicking google-code-prettify","3":"a color scheme mimicking google-code-prettify","description":"A color scheme (gvim only) similar to the one used by the google-code-prettify at http:\/\/code.google.com\/p\/google-code-prettify\/ and that google use at most of their sites, notably google code.\r\n\r\nI had to study documentation for Google App Engine, and switching from their syntax color scheme to the one I was using was a pain, so I made this quick and dirty color scheme (I am a newbie, this is my first color scheme)\r\n\r\nSo it closely copies the examples found on their README page, except for the HTML\/XML which is copied from the source view of chromium (which is also the color code used in firefox !)\r\n","4":"A color scheme (gvim only) similar to the one used by the google-code-prettify at http:\/\/code.google.com\/p\/google-code-prettify\/ and that google use at most of their sites, notably google code.\r\n\r\nI had to study documentation for Google App Engine, and switching from their syntax color scheme to the one I was using was a pain, so I made this quick and dirty color scheme (I am a newbie, this is my first color scheme)\r\n\r\nSo it closely copies the examples found on their README page, except for the HTML\/XML which is copied from the source view of chromium (which is also the color code used in firefox !)\r\n","install_details":"Install as any color scheme in .vim\/colors or by running :colorscheme google-prettify.vim and add syntax files into .vim\/after\/syntax","5":"Install as any color scheme in .vim\/colors or by running :colorscheme google-prettify.vim and add syntax files into .vim\/after\/syntax","first_name":"zeb","6":"zeb","last_name":"ulon","7":"ulon","releases":[{"0":"3751","vim_version":"7.0","1":"7.0","script_version":"0.1.1","2":"0.1.1","version_comment":"Add the after\/syntax files that are needed to match some syntax pattern not present in vim default syntax","3":"Add the after\/syntax files that are needed to match some syntax pattern not present in vim default syntax","package":"google_prettify.tar.gz","4":"google_prettify.tar.gz","src_id":"16556","5":"16556","creation_date":"1316427304","6":"1316427304"},{"0":"3751","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"fix the same of the file","3":"fix the same of the file","package":"google-prettify.vim","4":"google-prettify.vim","src_id":"16555","5":"16555","creation_date":"1316426466","6":"1316426466"},{"0":"3751","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"mygoogle.vim","4":"mygoogle.vim","src_id":"16554","5":"16554","creation_date":"1316426327","6":"1316426327"}]},"3750":{"script_id":"3750","0":"3750","script_name":"TclShell","1":"TclShell","script_type":"utility","2":"utility","summary":"Tcl Shell for Vim","3":"Tcl Shell for Vim","description":"A Tcl Shell for Vim using the integrated tcl interpreter.\r\n\r\nCreates a new buffer and window that resembles a shell. Tcl code can be entered\r\nand is executed once Enter is pressed.\r\n\r\nRequires Vim be compiles with the +tcl feature.\r\n\r\nProvides two commands:\r\n- TclShell opens the Tcl Shell Window.\r\n- TclEval evaluates Tcl code. This command can evaluate provided Tcl code, the\r\n  entire file (which is transformed to \"source FILE\") or visual ranges (whole\r\n  lines only). \r\n\r\nHas the key mapping \"<Leader>tcl\" to open the Tcl Shell window and execute\r\nvisually selected Tcl code. (Note: \"<Leader>\" is normally mapped to \"\\\".)\r\n\r\nBased on Shell.vim: http:\/\/www.vim.org\/scripts\/script.php?script_id=118\r\n\r\nVim Home:      http:\/\/www.vim.org\/scripts\/script.php?script_id=3750\r\nGitHub Home: https:\/\/github.com\/LStinson\/TclShell-Vim\r\nTclers Wiki:     http:\/\/wiki.tcl.tk\/28782\r\n\r\nI welcome any and all feedback. Please contact me at LoranceStinson AT Gmail....\r\nPlease be sure to put TclShell in the subject so I know what you are emailing about.","4":"A Tcl Shell for Vim using the integrated tcl interpreter.\r\n\r\nCreates a new buffer and window that resembles a shell. Tcl code can be entered\r\nand is executed once Enter is pressed.\r\n\r\nRequires Vim be compiles with the +tcl feature.\r\n\r\nProvides two commands:\r\n- TclShell opens the Tcl Shell Window.\r\n- TclEval evaluates Tcl code. This command can evaluate provided Tcl code, the\r\n  entire file (which is transformed to \"source FILE\") or visual ranges (whole\r\n  lines only). \r\n\r\nHas the key mapping \"<Leader>tcl\" to open the Tcl Shell window and execute\r\nvisually selected Tcl code. (Note: \"<Leader>\" is normally mapped to \"\\\".)\r\n\r\nBased on Shell.vim: http:\/\/www.vim.org\/scripts\/script.php?script_id=118\r\n\r\nVim Home:      http:\/\/www.vim.org\/scripts\/script.php?script_id=3750\r\nGitHub Home: https:\/\/github.com\/LStinson\/TclShell-Vim\r\nTclers Wiki:     http:\/\/wiki.tcl.tk\/28782\r\n\r\nI welcome any and all feedback. Please contact me at LoranceStinson AT Gmail....\r\nPlease be sure to put TclShell in the subject so I know what you are emailing about.","install_details":"To install copy the files to ~\/.vim or ~\/vimfiles.\r\nIf using a package manager like pathgen place the whole directory in the bundle directory.\r\n\r\nPlease disregard the Nagelfar file below. This is from an error and I can not delete it.","5":"To install copy the files to ~\/.vim or ~\/vimfiles.\r\nIf using a package manager like pathgen place the whole directory in the bundle directory.\r\n\r\nPlease disregard the Nagelfar file below. This is from an error and I can not delete it.","first_name":"Lorance","6":"Lorance","last_name":"Stinson","7":"Stinson","releases":[{"0":"3750","vim_version":"7.0","1":"7.0","script_version":"0.8","2":"0.8","version_comment":"Moved Tcl code evaluation from the TclShell command to the new TclEval command. This command can evaluate provided Tcl code, the entire file (which is transformed to \"source FILE\") or visual ranges (whole lines only). The TclShell command only opens the Tcl Shell window.","3":"Moved Tcl code evaluation from the TclShell command to the new TclEval command. This command can evaluate provided Tcl code, the entire file (which is transformed to \"source FILE\") or visual ranges (whole lines only). The TclShell command only opens the Tcl Shell window.","package":"TclShell.zip","4":"TclShell.zip","src_id":"17689","5":"17689","creation_date":"1333041339","6":"1333041339"},{"0":"3750","vim_version":"7.0","1":"7.0","script_version":"0.7","2":"0.7","version_comment":"Moved Tcl code evaluation to TclEval. TclShell no longer evaluates Tcl code. TclEval can evaluate the entire file, a visual selection or code passed to the command.","3":"Moved Tcl code evaluation to TclEval. TclShell no longer evaluates Tcl code. TclEval can evaluate the entire file, a visual selection or code passed to the command.","package":"TclShell-Vim.zip","4":"TclShell-Vim.zip","src_id":"17607","5":"17607","creation_date":"1332074759","6":"1332074759"},{"0":"3750","vim_version":"7.0","1":"7.0","script_version":"0.6","2":"0.6","version_comment":"Minor formatting updates. Replaced the defaults function.","3":"Minor formatting updates. Replaced the defaults function.","package":"TclShell-Vim.zip","4":"TclShell-Vim.zip","src_id":"16756","5":"16756","creation_date":"1319755896","6":"1319755896"}]},"3749":{"script_id":"3749","0":"3749","script_name":"NagelfarVim","1":"NagelfarVim","script_type":"utility","2":"utility","summary":"Integrates Nagelfar with Vim","3":"Integrates Nagelfar with Vim","description":"Vim integration of Nagelfar for checking .tcl files.\r\nThis is done using the compiler\/quickfix features of Vim.\r\nContains several useful features, some off by default.\r\nSee the included documentation for details.\r\n\r\nNagelfar can be downloaded from <http:\/\/nagelfar.berlios.de\/>\r\nThis script is intended to be used with the latest version.\r\n\r\nThe plugin lives at: https:\/\/github.com\/LStinson\/Nagelfar-Vim\r\n\r\nI welcome any and all feedback. Please contact me at LoranceStinson AT Gmail....\r\nPlease be sure to put Nagelfar-Vim in the subject so I know what you are emailing about.","4":"Vim integration of Nagelfar for checking .tcl files.\r\nThis is done using the compiler\/quickfix features of Vim.\r\nContains several useful features, some off by default.\r\nSee the included documentation for details.\r\n\r\nNagelfar can be downloaded from <http:\/\/nagelfar.berlios.de\/>\r\nThis script is intended to be used with the latest version.\r\n\r\nThe plugin lives at: https:\/\/github.com\/LStinson\/Nagelfar-Vim\r\n\r\nI welcome any and all feedback. Please contact me at LoranceStinson AT Gmail....\r\nPlease be sure to put Nagelfar-Vim in the subject so I know what you are emailing about.","install_details":"To install copy the files to ~\/.vim or ~\/vimfiles.\r\nIf using a package manager like pathgen place the whole directory in the bundle directory.","5":"To install copy the files to ~\/.vim or ~\/vimfiles.\r\nIf using a package manager like pathgen place the whole directory in the bundle directory.","first_name":"Lorance","6":"Lorance","last_name":"Stinson","7":"Stinson","releases":[{"0":"3749","vim_version":"7.0","1":"7.0","script_version":"0.3","2":"0.3","version_comment":"Added a few new key mappings. Switched from :cwindow to :copen for the <Leader>nw key map.","3":"Added a few new key mappings. Switched from :cwindow to :copen for the <Leader>nw key map.","package":"Nagelfar-Vim_0.3.zip","4":"Nagelfar-Vim_0.3.zip","src_id":"16550","5":"16550","creation_date":"1316366614","6":"1316366614"}]},"3748":{"script_id":"3748","0":"3748","script_name":"pylint-mode","1":"pylint-mode","script_type":"ftplugin","2":"ftplugin","summary":"pylint","3":"pylint","description":"Out of date.\r\n\r\nUse https:\/\/github.com\/klen\/python-mode","4":"Out of date.\r\n\r\nUse https:\/\/github.com\/klen\/python-mode","install_details":"","5":"","first_name":"Kirill","6":"Kirill","last_name":"Klenov","7":"Klenov","releases":[{"0":"3748","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"klen-pylint-mode-bc884af.zip","4":"klen-pylint-mode-bc884af.zip","src_id":"16535","5":"16535","creation_date":"1316184908","6":"1316184908"}]},"3747":{"script_id":"3747","0":"3747","script_name":"syntax\/dosini.vim","1":"syntax\/dosini.vim","script_type":"syntax","2":"syntax","summary":"Syntax file for dosini (*.ini)","3":"Syntax file for dosini (*.ini)","description":"This is a syntax file for dosini files (*.ini). This syntax file is based on the dosini syntax file maintained by Sean M. McKee and Nima Talebi, which was shipped with the official vim distribution before vim version 7.3.312.\r\n\r\nThis script has been included in the official vim distribution since vim version 7.3.313.\r\n\r\n\r\nGit Repository: https:\/\/github.com\/xuhdev\/syntax-dosini.vim\r\n\r\nIf you have any problem, you could either send me an email <hong@topbug.net> or submit it on the issue tracker:\r\n\r\nhttps:\/\/github.com\/xuhdev\/syntax-dosini.vim\/issues","4":"This is a syntax file for dosini files (*.ini). This syntax file is based on the dosini syntax file maintained by Sean M. McKee and Nima Talebi, which was shipped with the official vim distribution before vim version 7.3.312.\r\n\r\nThis script has been included in the official vim distribution since vim version 7.3.313.\r\n\r\n\r\nGit Repository: https:\/\/github.com\/xuhdev\/syntax-dosini.vim\r\n\r\nIf you have any problem, you could either send me an email <hong@topbug.net> or submit it on the issue tracker:\r\n\r\nhttps:\/\/github.com\/xuhdev\/syntax-dosini.vim\/issues","install_details":"Download the syntax-dosini.zip file and extract it to your vim runtime\r\ndirectory(~\/.vim on UNIX\/Linux and $VIM_INSTALLATION_FOLDER\\vimfiles on windows). ","5":"Download the syntax-dosini.zip file and extract it to your vim runtime\r\ndirectory(~\/.vim on UNIX\/Linux and $VIM_INSTALLATION_FOLDER\\vimfiles on windows). ","first_name":"Hong","6":"Hong","last_name":"Xu","7":"Xu","releases":[{"0":"3747","vim_version":"7.3","1":"7.3","script_version":"2.3","2":"2.3","version_comment":"Add support for section folding (Thanks  Lucas Hoffmann!)","3":"Add support for section folding (Thanks  Lucas Hoffmann!)","package":"dosini.vim","4":"dosini.vim","src_id":"28508","5":"28508","creation_date":"1687885590","6":"1687885590"},{"0":"3747","vim_version":"7.0","1":"7.0","script_version":"2.2","2":"2.2","version_comment":"links dosiniValue to String","3":"links dosiniValue to String","package":"syntax-dosini.zip","4":"syntax-dosini.zip","src_id":"26223","5":"26223","creation_date":"1536725499","6":"1536725499"},{"0":"3747","vim_version":"7.0","1":"7.0","script_version":"2.1","2":"2.1","version_comment":"Remove  Boolean highlighting.","3":"Remove  Boolean highlighting.","package":"syntax-dosini.zip","4":"syntax-dosini.zip","src_id":"16830","5":"16830","creation_date":"1320753437","6":"1320753437"},{"0":"3747","vim_version":"7.0","1":"7.0","script_version":"2.0","2":"2.0","version_comment":"Initial upload","3":"Initial upload","package":"syntax-dosini.zip","4":"syntax-dosini.zip","src_id":"16531","5":"16531","creation_date":"1316089195","6":"1316089195"}]},"3746":{"script_id":"3746","0":"3746","script_name":"watchdog.vim","1":"watchdog.vim","script_type":"utility","2":"utility","summary":"Comprehensive, dynamically resizing statusline","3":"Comprehensive, dynamically resizing statusline","description":"Statusline with comprehensive information about current vim buffer.\r\n\r\nDepends on vim window size, watchdog will show most important information: e.g. filename, how vim detected filetype, current line\/cursor position.\r\n\r\nIf there are would be enough space to show additional information, watchdog will show it. For instance, file encoding and last modification date\/time.\r\n\r\nhttps:\/\/github.com\/avakarev\/vim-watchdog","4":"Statusline with comprehensive information about current vim buffer.\r\n\r\nDepends on vim window size, watchdog will show most important information: e.g. filename, how vim detected filetype, current line\/cursor position.\r\n\r\nIf there are would be enough space to show additional information, watchdog will show it. For instance, file encoding and last modification date\/time.\r\n\r\nhttps:\/\/github.com\/avakarev\/vim-watchdog","install_details":"Just extract to ~\/.vim, or ~\\vimfiles (Windows).","5":"Just extract to ~\/.vim, or ~\\vimfiles (Windows).","first_name":"Andrey","6":"Andrey","last_name":"Vakarev","7":"Vakarev","releases":[{"0":"3746","vim_version":"7.0","1":"7.0","script_version":"1.0.1","2":"1.0.1","version_comment":"Bugfix: On changing filetype by setting its value, it was not represented immediately on the status line. Now it fixed.","3":"Bugfix: On changing filetype by setting its value, it was not represented immediately on the status line. Now it fixed.","package":"vim-watchdog.zip","4":"vim-watchdog.zip","src_id":"16565","5":"16565","creation_date":"1316793242","6":"1316793242"},{"0":"3746","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"vim-watchdog.zip","4":"vim-watchdog.zip","src_id":"16528","5":"16528","creation_date":"1316034189","6":"1316034189"}]},"3745":{"script_id":"3745","0":"3745","script_name":"linediff.vim","1":"linediff.vim","script_type":"utility","2":"utility","summary":"Perform an interactive diff on two blocks of text","3":"Perform an interactive diff on two blocks of text","description":"This plugin provides a simple command, \":Linediff\", which is used to diff two separate blocks of text. Here's a simple example:\r\n\r\n    def one\r\n      two\r\n    end\r\n\r\n    def two\r\n      three\r\n    end\r\n\r\nIf we mark the first three lines, starting from \"def one\", in visual mode, and execute the \":Linediff\" command, the signs \"1-\" will be placed at the start and at the end of the visual mode's range. Doing the same thing on the bottom half of the code, starting from \"def two\", will result in the signs \"2-\" placed there. After that, a new tab will be opened with the two blocks of code in vertical splits, diffed against each other.\r\n\r\nThe two buffers are temporary, but when any one of them is saved, its original buffer is updated. Note that this doesn't save the original buffer, just performs the change. Saving is something you should do later on yourself.\r\n\r\nExecuting the command \":LinediffReset\" will delete the temporary buffers and remove the signs. Executing a new \":Linediff\" will do the same as \":LinediffReset\", but will also initiate a new diff process.\r\n\r\nThe code is hosted on github, at http:\/\/github.com\/AndrewRadev\/linediff.vim. To report any bugs, send patches or suggest features, please use github's issue tracker: http:\/\/github.com\/AndrewRadev\/linediff.vim\/issues.\r\n","4":"This plugin provides a simple command, \":Linediff\", which is used to diff two separate blocks of text. Here's a simple example:\r\n\r\n    def one\r\n      two\r\n    end\r\n\r\n    def two\r\n      three\r\n    end\r\n\r\nIf we mark the first three lines, starting from \"def one\", in visual mode, and execute the \":Linediff\" command, the signs \"1-\" will be placed at the start and at the end of the visual mode's range. Doing the same thing on the bottom half of the code, starting from \"def two\", will result in the signs \"2-\" placed there. After that, a new tab will be opened with the two blocks of code in vertical splits, diffed against each other.\r\n\r\nThe two buffers are temporary, but when any one of them is saved, its original buffer is updated. Note that this doesn't save the original buffer, just performs the change. Saving is something you should do later on yourself.\r\n\r\nExecuting the command \":LinediffReset\" will delete the temporary buffers and remove the signs. Executing a new \":Linediff\" will do the same as \":LinediffReset\", but will also initiate a new diff process.\r\n\r\nThe code is hosted on github, at http:\/\/github.com\/AndrewRadev\/linediff.vim. To report any bugs, send patches or suggest features, please use github's issue tracker: http:\/\/github.com\/AndrewRadev\/linediff.vim\/issues.\r\n","install_details":"The recommended way to install the plugin is by using Tim Pope's pathogen (http:\/\/www.vim.org\/scripts\/script.php?script_id=2332). In that case, you can clone the plugin's git repository like so:\r\n\r\n    git clone git:\/\/github.com\/AndrewRadev\/linediff.vim.git ~\/.vim\/bundle\/linediff\r\n\r\nIf your vim configuration is under git version control, you could also set up the repository as a submodule, which would allow you to update more easily. The command is (provided you're in ~\/.vim):\r\n\r\n    git submodule add git:\/\/github.com\/AndrewRadev\/linediff.vim.git bundle\/linediff\r\n\r\nAnother method of installation is to simply copy all the essential directories inside the ~.vim\/ directory: plugin, autoload, doc.","5":"The recommended way to install the plugin is by using Tim Pope's pathogen (http:\/\/www.vim.org\/scripts\/script.php?script_id=2332). In that case, you can clone the plugin's git repository like so:\r\n\r\n    git clone git:\/\/github.com\/AndrewRadev\/linediff.vim.git ~\/.vim\/bundle\/linediff\r\n\r\nIf your vim configuration is under git version control, you could also set up the repository as a submodule, which would allow you to update more easily. The command is (provided you're in ~\/.vim):\r\n\r\n    git submodule add git:\/\/github.com\/AndrewRadev\/linediff.vim.git bundle\/linediff\r\n\r\nAnother method of installation is to simply copy all the essential directories inside the ~.vim\/ directory: plugin, autoload, doc.","first_name":"Andrew","6":"Andrew","last_name":"Radev","7":"Radev","releases":[{"0":"3745","vim_version":"7.0","1":"7.0","script_version":"0.2.0","2":"0.2.0","version_comment":"Various bugfixes","3":"Various bugfixes","package":"linediff.zip","4":"linediff.zip","src_id":"22834","5":"22834","creation_date":"1422351385","6":"1422351385"},{"0":"3745","vim_version":"7.0","1":"7.0","script_version":"0.1.1","2":"0.1.1","version_comment":"- Bugfix by xaizek (https:\/\/github.com\/xaizek)\r\n- Bugfix for statusline problem: https:\/\/github.com\/AndrewRadev\/linediff.vim\/issues\/2","3":"- Bugfix by xaizek (https:\/\/github.com\/xaizek)\r\n- Bugfix for statusline problem: https:\/\/github.com\/AndrewRadev\/linediff.vim\/issues\/2","package":"linediff.zip","4":"linediff.zip","src_id":"16823","5":"16823","creation_date":"1320704188","6":"1320704188"},{"0":"3745","vim_version":"7.0","1":"7.0","script_version":"0.1.0","2":"0.1.0","version_comment":"Initial upload","3":"Initial upload","package":"linediff.zip","4":"linediff.zip","src_id":"16527","5":"16527","creation_date":"1316030744","6":"1316030744"}]},"3744":{"script_id":"3744","0":"3744","script_name":"MarkdownFootnotes","1":"MarkdownFootnotes","script_type":"utility","2":"utility","summary":"Insert Extended Markdown Footnotes with Vim","3":"Insert Extended Markdown Footnotes with Vim","description":"This script is a modification of the venerable vimfootnotes (vimscript #431), for use with extended markdown. The most recent version is available on github:\r\n\r\nhttps:\/\/github.com\/vim-pandoc\/vim-markdownfootnotes\/\r\n\r\nThe original vimfootnotes inserts footnotes that look like this:\r\n\r\n    Here is some text.[1]\r\n\r\n    [1] Here is a note.\r\n\r\nThe new script inserts footnotes in the widely supported extended markdown syntax,\r\n\r\n    Here is some text.[^1]\r\n\r\n    [^1]: Here is a note.\r\n\r\nThe original script inserts footnotes at the end of the file or before an email sig line, if there is one. The new script inserts all footnotes at the end of the file.\r\n\r\nThe script defines two mappings,\r\n\r\n    <Leader>f    Insert new footnote \r\n    <Leader>r    Return from footnote\r\n\r\nTo insert a footnote, type f. A footnote mark will be inserted after the cursor. A matching footnote mark will be inserted at the end of the file. A new buffer will open in a split window at the bottom of your screen, ready to edit the new footnote. When you are done, type r to close the split and return to the main text.\r\n","4":"This script is a modification of the venerable vimfootnotes (vimscript #431), for use with extended markdown. The most recent version is available on github:\r\n\r\nhttps:\/\/github.com\/vim-pandoc\/vim-markdownfootnotes\/\r\n\r\nThe original vimfootnotes inserts footnotes that look like this:\r\n\r\n    Here is some text.[1]\r\n\r\n    [1] Here is a note.\r\n\r\nThe new script inserts footnotes in the widely supported extended markdown syntax,\r\n\r\n    Here is some text.[^1]\r\n\r\n    [^1]: Here is a note.\r\n\r\nThe original script inserts footnotes at the end of the file or before an email sig line, if there is one. The new script inserts all footnotes at the end of the file.\r\n\r\nThe script defines two mappings,\r\n\r\n    <Leader>f    Insert new footnote \r\n    <Leader>r    Return from footnote\r\n\r\nTo insert a footnote, type f. A footnote mark will be inserted after the cursor. A matching footnote mark will be inserted at the end of the file. A new buffer will open in a split window at the bottom of your screen, ready to edit the new footnote. When you are done, type r to close the split and return to the main text.\r\n","install_details":"Drop markdownfootnotes.vim in your plugin directory.\r\n\r\nOr use Pathogen (vimscript #2332).","5":"Drop markdownfootnotes.vim in your plugin directory.\r\n\r\nOr use Pathogen (vimscript #2332).","first_name":"David","6":"David","last_name":"Sanson","7":"Sanson","releases":[{"0":"3744","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"vim-markdownfootnotes-1.0.0.zip","4":"vim-markdownfootnotes-1.0.0.zip","src_id":"16517","5":"16517","creation_date":"1315926097","6":"1315926097"}]},"3743":{"script_id":"3743","0":"3743","script_name":"Vimerl","1":"Vimerl","script_type":"utility","2":"utility","summary":"The Erlang plugin for Vim","3":"The Erlang plugin for Vim","description":"Vimerl is a plugin for programming in Erlang. It provides several nice\r\nfeatures to make your life easier when writing code.\r\n\r\nThe plugin offers the following features:\r\n\t- Syntax highlighting\r\n\t- Code indenting\r\n\t- Code folding\r\n\t- Code omni completion\r\n\t- Syntax check\r\n\t- Compiler support with QuickFix commands\r\n\t- Code skeletons for the OTP behaviours\r\n\t- Pathogen support (http:\/\/github.com\/tpope\/vim-pathogen)\r\n\r\nNote: the plugin is fully documented and stable but bugfixes are always welcomed ;-)\r\n\r\nNote: the development is done in GitHub:\r\n\thttp:\/\/github.com\/jimenezrick\/vimerl \r\n\r\nNote: this plugin is a *very very very* improved version of this:\r\n\thttp:\/\/github.com\/oscarh\/vimerl","4":"Vimerl is a plugin for programming in Erlang. It provides several nice\r\nfeatures to make your life easier when writing code.\r\n\r\nThe plugin offers the following features:\r\n\t- Syntax highlighting\r\n\t- Code indenting\r\n\t- Code folding\r\n\t- Code omni completion\r\n\t- Syntax check\r\n\t- Compiler support with QuickFix commands\r\n\t- Code skeletons for the OTP behaviours\r\n\t- Pathogen support (http:\/\/github.com\/tpope\/vim-pathogen)\r\n\r\nNote: the plugin is fully documented and stable but bugfixes are always welcomed ;-)\r\n\r\nNote: the development is done in GitHub:\r\n\thttp:\/\/github.com\/jimenezrick\/vimerl \r\n\r\nNote: this plugin is a *very very very* improved version of this:\r\n\thttp:\/\/github.com\/oscarh\/vimerl","install_details":"Copy the content of the tarball to your `.vim'. It also works perfectly\r\nwith `Pathogen' (http:\/\/github.com\/tpope\/vim-pathogen).\r\n\r\nDon't forget to run `:helptags' if you are not using `Pathogen'.\r\n","5":"Copy the content of the tarball to your `.vim'. It also works perfectly\r\nwith `Pathogen' (http:\/\/github.com\/tpope\/vim-pathogen).\r\n\r\nDon't forget to run `:helptags' if you are not using `Pathogen'.\r\n","first_name":"Ricardo","6":"Ricardo","last_name":"Catalinas Jim\u00c3\u00a9nez","7":"Catalinas Jim\u00c3\u00a9nez","releases":[{"0":"3743","vim_version":"7.3","1":"7.3","script_version":"1.4.1","2":"1.4.1","version_comment":"- Improvements in code indenting\r\n- Improve behaviour code skeletons\r\n- Several bugfixes","3":"- Improvements in code indenting\r\n- Improve behaviour code skeletons\r\n- Several bugfixes","package":"vimerl-1.4.1.tar.gz","4":"vimerl-1.4.1.tar.gz","src_id":"17542","5":"17542","creation_date":"1330430628","6":"1330430628"},{"0":"3743","vim_version":"7.3","1":"7.3","script_version":"1.4","2":"1.4","version_comment":"- Much better code indenting, more similar to Emacs style\r\n- Omni completion using EDoc and Mod:module_info\/2\r\n- General improvements and bug fixes","3":"- Much better code indenting, more similar to Emacs style\r\n- Omni completion using EDoc and Mod:module_info\/2\r\n- General improvements and bug fixes","package":"vimerl-1.4.tar.gz","4":"vimerl-1.4.tar.gz","src_id":"17396","5":"17396","creation_date":"1328479329","6":"1328479329"},{"0":"3743","vim_version":"7.3","1":"7.3","script_version":"1.2","2":"1.2","version_comment":"- Speeds up omnicompletion with a cache.\r\n- Smoother syntax checks.\r\n- Automatic man pages location, removed unnecessary options.\r\n- General fixes.","3":"- Speeds up omnicompletion with a cache.\r\n- Smoother syntax checks.\r\n- Automatic man pages location, removed unnecessary options.\r\n- General fixes.","package":"vimerl-1.2.tar.gz","4":"vimerl-1.2.tar.gz","src_id":"17137","5":"17137","creation_date":"1325353140","6":"1325353140"},{"0":"3743","vim_version":"7.3","1":"7.3","script_version":"1.1.1","2":"1.1.1","version_comment":"Smoother syntax check. Removes unnecessary screen redraws.","3":"Smoother syntax check. Removes unnecessary screen redraws.","package":"vimerl-1.1.1.tar.gz","4":"vimerl-1.1.1.tar.gz","src_id":"16564","5":"16564","creation_date":"1316786779","6":"1316786779"},{"0":"3743","vim_version":"7.3","1":"7.3","script_version":"1.1","2":"1.1","version_comment":"Initial upload","3":"Initial upload","package":"vimerl-1.1.tar.gz","4":"vimerl-1.1.tar.gz","src_id":"16515","5":"16515","creation_date":"1315908045","6":"1315908045"}]},"3742":{"script_id":"3742","0":"3742","script_name":"mediawiki","1":"mediawiki","script_type":"syntax","2":"syntax","summary":"Mediawiki+templates","3":"Mediawiki+templates","description":"This syntax file makes it much easier to read the curly braces nightmare from mediawiki templates. Based on Wikipedia.vim.","4":"This syntax file makes it much easier to read the curly braces nightmare from mediawiki templates. Based on Wikipedia.vim.","install_details":"","5":"","first_name":"J\u00c3\u00a9r\u00c3\u00b4me","6":"J\u00c3\u00a9r\u00c3\u00b4me","last_name":"Poulin","7":"Poulin","releases":[{"0":"3742","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"mediawiki.tar.gz","4":"mediawiki.tar.gz","src_id":"16511","5":"16511","creation_date":"1315844285","6":"1315844285"}]},"3741":{"script_id":"3741","0":"3741","script_name":"kiwi.vim","1":"kiwi.vim","script_type":"utility","2":"utility","summary":"Support for writing Kiwi specs","3":"Support for writing Kiwi specs","description":"\r\n`kiwi.vim` is a plugin for working with the [Kiwi](http:\/\/kiwi-lib.org\/)\r\nlibrary for behavior-driven development.  Right now, it simply adds\r\nsmart folding, but I have some abbreviations which I'll add once I\r\nhammer out some pretty ugly kinks.\r\n\r\nWhich Files Are Kiwi?\r\n---------------------\r\n\r\nTo keep things simple, I just match anything that matches `*Spec.m`\r\nor `*Spec.mm`.  You can add your own `autocmd` rules to if you use\r\na different naming convention.\r\n\r\nFolding\r\n-------\r\n\r\nFolding is designed to make the Kiwi specs readable as specs at a glance,\r\nhiding the backing code until you want to look at it.  In addition,\r\nit still allows adding manual fold markers (e.g. {{{1 and }}}) so that\r\nyou can fold any supporting code in the file.","4":"\r\n`kiwi.vim` is a plugin for working with the [Kiwi](http:\/\/kiwi-lib.org\/)\r\nlibrary for behavior-driven development.  Right now, it simply adds\r\nsmart folding, but I have some abbreviations which I'll add once I\r\nhammer out some pretty ugly kinks.\r\n\r\nWhich Files Are Kiwi?\r\n---------------------\r\n\r\nTo keep things simple, I just match anything that matches `*Spec.m`\r\nor `*Spec.mm`.  You can add your own `autocmd` rules to if you use\r\na different naming convention.\r\n\r\nFolding\r\n-------\r\n\r\nFolding is designed to make the Kiwi specs readable as specs at a glance,\r\nhiding the backing code until you want to look at it.  In addition,\r\nit still allows adding manual fold markers (e.g. {{{1 and }}}) so that\r\nyou can fold any supporting code in the file.","install_details":"The easiest way to install would be to install pathogen.vim then clone the git repository like so:\r\n\r\n  cd ~\/.vim\/bundle\r\n  git clone git:\/\/github.com\/eraserhd\/vim-kiwi.git","5":"The easiest way to install would be to install pathogen.vim then clone the git repository like so:\r\n\r\n  cd ~\/.vim\/bundle\r\n  git clone git:\/\/github.com\/eraserhd\/vim-kiwi.git","first_name":"Jason","6":"Jason","last_name":"Felice","7":"Felice","releases":[{"0":"3741","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"kiwi.zip","4":"kiwi.zip","src_id":"16510","5":"16510","creation_date":"1315831881","6":"1315831881"}]},"3740":{"script_id":"3740","0":"3740","script_name":"gccsingle.vim","1":"gccsingle.vim","script_type":"utility","2":"utility","summary":"Quick run single C source file","3":"Quick run single C source file","description":"        This is a smart utility for quick run single c source file in vim.\r\n\r\n        It has follow features:\r\n                1. Use gcc compiler.\r\n                2. Compile and run single c source file just one command.\r\n                3. Program's output is showing below the source file in a new window.\r\n                4. You can hide the output window easily.\r\n                5. When there are some errors, quick window will automatically appears.\r\n                6. When there is no error, quick window hides automatically.\r\n                7. When you compile it, source code is saved by the script, so you need not to save it.\r\n                8. Only three commands, easily to remember, easily to use.\r\n\r\n        The most cool things are:\r\n                1. Run source file just one command.\r\n                2. Quick window shows and hides automatically.\r\n                3. Everything happened in vim, no ugly command window.\r\n\r\nScreenshot\r\n        Has bugs, quick window appears\r\n        http:\/\/vimer.1063083.n5.nabble.com\/Quickfix-window-td4791439.html\r\n\r\n        No bug, output in vim, no command window\r\n        http:\/\/vimer.1063083.n5.nabble.com\/Output-window-td4791441.html ","4":"        This is a smart utility for quick run single c source file in vim.\r\n\r\n        It has follow features:\r\n                1. Use gcc compiler.\r\n                2. Compile and run single c source file just one command.\r\n                3. Program's output is showing below the source file in a new window.\r\n                4. You can hide the output window easily.\r\n                5. When there are some errors, quick window will automatically appears.\r\n                6. When there is no error, quick window hides automatically.\r\n                7. When you compile it, source code is saved by the script, so you need not to save it.\r\n                8. Only three commands, easily to remember, easily to use.\r\n\r\n        The most cool things are:\r\n                1. Run source file just one command.\r\n                2. Quick window shows and hides automatically.\r\n                3. Everything happened in vim, no ugly command window.\r\n\r\nScreenshot\r\n        Has bugs, quick window appears\r\n        http:\/\/vimer.1063083.n5.nabble.com\/Quickfix-window-td4791439.html\r\n\r\n        No bug, output in vim, no command window\r\n        http:\/\/vimer.1063083.n5.nabble.com\/Output-window-td4791441.html ","install_details":"        Put this file in ~\/.vim\/plugin on *nix.\r\n        Or put it in $vim\/vimfiles\/plugin on Windows.\r\n\r\nTutorial\r\n        Only three commands to use this utility.\r\n        If you don't like these mapping, just modify the source code.\r\n                1. compile and run:      ,g      (g means gcc)\r\n                2. run the program:      ,r       (r means run)\r\n                3. hide the output:        ,h      (h means hide)","5":"        Put this file in ~\/.vim\/plugin on *nix.\r\n        Or put it in $vim\/vimfiles\/plugin on Windows.\r\n\r\nTutorial\r\n        Only three commands to use this utility.\r\n        If you don't like these mapping, just modify the source code.\r\n                1. compile and run:      ,g      (g means gcc)\r\n                2. run the program:      ,r       (r means run)\r\n                3. hide the output:        ,h      (h means hide)","first_name":"Tian","6":"Tian","last_name":"Huixiong","7":"Huixiong","releases":[{"0":"3740","vim_version":"7.0","1":"7.0","script_version":"1.6","2":"1.6","version_comment":"Bug fixed: \r\nwhen the current window is the output window,   use \",h\"  to hide the output window and source code window's statusline hides too.","3":"Bug fixed: \r\nwhen the current window is the output window,   use \",h\"  to hide the output window and source code window's statusline hides too.","package":"gccsingle.vim","4":"gccsingle.vim","src_id":"16524","5":"16524","creation_date":"1315989305","6":"1315989305"},{"0":"3740","vim_version":"7.0","1":"7.0","script_version":"1.5","2":"1.5","version_comment":"Hide the output window's statusline. ","3":"Hide the output window's statusline. ","package":"gccsingle.vim","4":"gccsingle.vim","src_id":"16523","5":"16523","creation_date":"1315988367","6":"1315988367"},{"0":"3740","vim_version":"7.0","1":"7.0","script_version":"1.4","2":"1.4","version_comment":"Process exception: if program not exist, return directly.","3":"Process exception: if program not exist, return directly.","package":"gccsingle.vim","4":"gccsingle.vim","src_id":"16520","5":"16520","creation_date":"1315976678","6":"1315976678"},{"0":"3740","vim_version":"7.0","1":"7.0","script_version":"1.3","2":"1.3","version_comment":"1. Simplify the installation, mapped in source file, no need to modify the vimrc","3":"1. Simplify the installation, mapped in source file, no need to modify the vimrc","package":"gccsingle.vim","4":"gccsingle.vim","src_id":"16519","5":"16519","creation_date":"1315933106","6":"1315933106"},{"0":"3740","vim_version":"7.0","1":"7.0","script_version":"1.2","2":"1.2","version_comment":"1. Simplify the mapping.\r\n2. Shorten the function names.","3":"1. Simplify the mapping.\r\n2. Shorten the function names.","package":"gccsingle.vim","4":"gccsingle.vim","src_id":"16518","5":"16518","creation_date":"1315932469","6":"1315932469"},{"0":"3740","vim_version":"7.0","1":"7.0","script_version":"1.1","2":"1.1","version_comment":"1.  One command to compile and run the source code.\r\n2.  Simplify the mapping.","3":"1.  One command to compile and run the source code.\r\n2.  Simplify the mapping.","package":"gccsingle.vim","4":"gccsingle.vim","src_id":"16514","5":"16514","creation_date":"1315880436","6":"1315880436"},{"0":"3740","vim_version":"7.0","1":"7.0","script_version":"1.1","2":"1.1","version_comment":"1.  Run the source file directly, no need to compile it first.\r\n2.  Simplify the mapping.","3":"1.  Run the source file directly, no need to compile it first.\r\n2.  Simplify the mapping.","package":"gccsingle.vim","4":"gccsingle.vim","src_id":"16513","5":"16513","creation_date":"1315879937","6":"1315879937"},{"0":"3740","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"gccsingle.vim","4":"gccsingle.vim","src_id":"16503","5":"16503","creation_date":"1315745894","6":"1315745894"}]},"3739":{"script_id":"3739","0":"3739","script_name":"blue_sky","1":"blue_sky","script_type":"color scheme","2":"color scheme","summary":"light\/dark color scheme for both gvim & vim","3":"light\/dark color scheme for both gvim & vim","description":"This color scheme is provided both light and dark version. I mainly do vim scripting and tex edditting, so these are supported in the best way (at least for now). Initially, it was based on rastafari colorscheme (#vimscript2198), but it looks much different.\r\n\r\nYou can get a grasp how it looks like: \r\nhttp:\/\/www.math.ist.utl.pt\/~mszamo\/blue_sky_light.jpg \r\nhttp:\/\/www.math.ist.utl.pt\/~mszamo\/blue_sky_dark.jpg \r\n\r\nIt provides one command:\r\n:BlueSky\r\nto change from night to day sky ;) and vice versa. You can also do that by hands: just set the variable:\r\nlet g:blue_sky_style = \"light\" or \"dark\"\r\nand reload the colorscheme (this can be done in your vimrc file before ':colorscheme blue_sky' command).\r\n\r\nHappy vimming :)","4":"This color scheme is provided both light and dark version. I mainly do vim scripting and tex edditting, so these are supported in the best way (at least for now). Initially, it was based on rastafari colorscheme (#vimscript2198), but it looks much different.\r\n\r\nYou can get a grasp how it looks like: \r\nhttp:\/\/www.math.ist.utl.pt\/~mszamo\/blue_sky_light.jpg \r\nhttp:\/\/www.math.ist.utl.pt\/~mszamo\/blue_sky_dark.jpg \r\n\r\nIt provides one command:\r\n:BlueSky\r\nto change from night to day sky ;) and vice versa. You can also do that by hands: just set the variable:\r\nlet g:blue_sky_style = \"light\" or \"dark\"\r\nand reload the colorscheme (this can be done in your vimrc file before ':colorscheme blue_sky' command).\r\n\r\nHappy vimming :)","install_details":"Put it under ~\/.vim\/colors\/ directory (linux) or ($HOME\/vimfiles\/colors in windows).","5":"Put it under ~\/.vim\/colors\/ directory (linux) or ($HOME\/vimfiles\/colors in windows).","first_name":"Marcin","6":"Marcin","last_name":"Szamotulski","7":"Szamotulski","releases":[{"0":"3739","vim_version":"7.0","1":"7.0","script_version":"2","2":"2","version_comment":"Change light\/dark versions with set bg=dark\/light and fixes lots of inconsistencies.\r\n","3":"Change light\/dark versions with set bg=dark\/light and fixes lots of inconsistencies.\r\n","package":"blue_sky.vim","4":"blue_sky.vim","src_id":"20886","5":"20886","creation_date":"1381004924","6":"1381004924"},{"0":"3739","vim_version":"7.0","1":"7.0","script_version":"1.2","2":"1.2","version_comment":"Identifier color in light background fixed.","3":"Identifier color in light background fixed.","package":"blue_sky.vim","4":"blue_sky.vim","src_id":"16522","5":"16522","creation_date":"1315982400","6":"1315982400"},{"0":"3739","vim_version":"7.0","1":"7.0","script_version":"1.1","2":"1.1","version_comment":"Visual color changed.","3":"Visual color changed.","package":"blue_sky.vim","4":"blue_sky.vim","src_id":"16509","5":"16509","creation_date":"1315803247","6":"1315803247"},{"0":"3739","vim_version":"7.0","1":"7.0","script_version":"1","2":"1","version_comment":"Initial upload.","3":"Initial upload.","package":"blue_sky.vim","4":"blue_sky.vim","src_id":"16504","5":"16504","creation_date":"1315753336","6":"1315753336"},{"0":"3739","vim_version":"7.0","1":"7.0","script_version":"1","2":"1","version_comment":"Initial upload","3":"Initial upload","package":"blue_sky.vim","4":"blue_sky.vim","src_id":"16502","5":"16502","creation_date":"1315739839","6":"1315739839"}]},"3738":{"script_id":"3738","0":"3738","script_name":"TagmaTips","1":"TagmaTips","script_type":"utility","2":"utility","summary":"Tool Tips for Vim","3":"Tool Tips for Vim","description":"This plugin uses the Tool Tip \/ Balloon functionality of Vim to display Tool\r\nTips for code. Currently only Tcl and AWK are supported.\r\n\r\nTool Tips are displayed for commands, variables and user defined procedures \/\r\nfunctions. The current buffer is checked for user defined procedures \/ functions when it\r\nis written to disk.\r\n\r\nMore information and screenshots (in the wiki) at: https:\/\/github.com\/LStinson\/TagmaTips\r\n\r\nRequires GVim 7 or later.\r\n\r\nI welcome any and all feedback. Please contact me at LoranceStinson AT Gmail....\r\nPlease be sure to put TagmaTips in the subject so I know what you are emailing about.","4":"This plugin uses the Tool Tip \/ Balloon functionality of Vim to display Tool\r\nTips for code. Currently only Tcl and AWK are supported.\r\n\r\nTool Tips are displayed for commands, variables and user defined procedures \/\r\nfunctions. The current buffer is checked for user defined procedures \/ functions when it\r\nis written to disk.\r\n\r\nMore information and screenshots (in the wiki) at: https:\/\/github.com\/LStinson\/TagmaTips\r\n\r\nRequires GVim 7 or later.\r\n\r\nI welcome any and all feedback. Please contact me at LoranceStinson AT Gmail....\r\nPlease be sure to put TagmaTips in the subject so I know what you are emailing about.","install_details":"You should be able ti simply unzip the file in the proper location.\r\n\r\nPlace the files in ~\/.vim or ~\/vimfiles\r\nIf using a manager (like Pathogen) place in ~\/.vim\/bundle or ~\/vimfiles\/bundle\r\n\r\nPlease note when updating the Vim Tool Tips Cache will be rebuilt.\r\nThis will cause a delay when loading a Vim file the first time.","5":"You should be able ti simply unzip the file in the proper location.\r\n\r\nPlace the files in ~\/.vim or ~\/vimfiles\r\nIf using a manager (like Pathogen) place in ~\/.vim\/bundle or ~\/vimfiles\/bundle\r\n\r\nPlease note when updating the Vim Tool Tips Cache will be rebuilt.\r\nThis will cause a delay when loading a Vim file the first time.","first_name":"Lorance","6":"Lorance","last_name":"Stinson","7":"Stinson","releases":[{"0":"3738","vim_version":"7.0","1":"7.0","script_version":"0.5","2":"0.5","version_comment":"Created the option g:TagmaTipsAutoEnable to control auto enable of Tool Tips. If g:TagmaTipsAutoEnable is set to false tool tips must manually be enabled for each buffer using the new command EnableTips.","3":"Created the option g:TagmaTipsAutoEnable to control auto enable of Tool Tips. If g:TagmaTipsAutoEnable is set to false tool tips must manually be enabled for each buffer using the new command EnableTips.","package":"TagmaTips.zip","4":"TagmaTips.zip","src_id":"17213","5":"17213","creation_date":"1326599589","6":"1326599589"},{"0":"3738","vim_version":"7.0","1":"7.0","script_version":"0.4","2":"0.4","version_comment":"Added AutoCmd events support to Vim. Updated the documentation. Fixed a few formatting issues with Vim tool tips.","3":"Added AutoCmd events support to Vim. Updated the documentation. Fixed a few formatting issues with Vim tool tips.","package":"TagmaTips.zip","4":"TagmaTips.zip","src_id":"17205","5":"17205","creation_date":"1326561114","6":"1326561114"},{"0":"3738","vim_version":"7.0","1":"7.0","script_version":"0.3","2":"0.3","version_comment":"Added Perl support and Perl functions from 'perldoc -f'. The code is more generic and efficient. See the GitHub home for more information.","3":"Added Perl support and Perl functions from 'perldoc -f'. The code is more generic and efficient. See the GitHub home for more information.","package":"TagmaTips.zip","4":"TagmaTips.zip","src_id":"17147","5":"17147","creation_date":"1325541421","6":"1325541421"}]},"3737":{"script_id":"3737","0":"3737","script_name":"sexy-railscasts","1":"sexy-railscasts","script_type":"color scheme","2":"color scheme","summary":"initial version","3":"initial version","description":"A GUI Only port of the RailsCasts TextMate theme to Vim.\r\nSome parts of this theme were borrowed from the well-documented Lucius theme [2].\r\nInitial file was written by Josh O'Rourke then improved by Oguz Bilgic\r\n\r\nhttps:\/\/github.com\/oguzbilgic\/sexy-railscasts-theme","4":"A GUI Only port of the RailsCasts TextMate theme to Vim.\r\nSome parts of this theme were borrowed from the well-documented Lucius theme [2].\r\nInitial file was written by Josh O'Rourke then improved by Oguz Bilgic\r\n\r\nhttps:\/\/github.com\/oguzbilgic\/sexy-railscasts-theme","install_details":"","5":"","first_name":"Oguz","6":"Oguz","last_name":"Bilgic","7":"Bilgic","releases":[{"0":"3737","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"sexy-railscasts.vim","4":"sexy-railscasts.vim","src_id":"16498","5":"16498","creation_date":"1315687576","6":"1315687576"}]},"3736":{"script_id":"3736","0":"3736","script_name":"ctrlp.vim","1":"ctrlp.vim","script_type":"utility","2":"utility","summary":"Fuzzy file, buffer, mru, tag, ... finder with regexp support.","3":"Fuzzy file, buffer, mru, tag, ... finder with regexp support.","description":"Fuzzy file, buffer, mru, tag, ... finder with regexp support.\r\n\r\n    * Written in pure Vimscript for MacVim, gVim and Vim 7.0+.\r\n    * Full support for Vim\u00e2\u0080\u0099s regexp as search patterns.\r\n    * Built-in Most Recently Used (MRU) files monitoring.\r\n    * Built-in project's root finder.\r\n\r\n    Homepage with screenshot: http:\/\/kien.github.com\/ctrlp.vim\/\r\n\r\n    Git repository:            https:\/\/github.com\/kien\/ctrlp.vim\r\n    Mercurial repository: https:\/\/bitbucket.org\/kien\/ctrlp.vim","4":"Fuzzy file, buffer, mru, tag, ... finder with regexp support.\r\n\r\n    * Written in pure Vimscript for MacVim, gVim and Vim 7.0+.\r\n    * Full support for Vim\u00e2\u0080\u0099s regexp as search patterns.\r\n    * Built-in Most Recently Used (MRU) files monitoring.\r\n    * Built-in project's root finder.\r\n\r\n    Homepage with screenshot: http:\/\/kien.github.com\/ctrlp.vim\/\r\n\r\n    Git repository:            https:\/\/github.com\/kien\/ctrlp.vim\r\n    Mercurial repository: https:\/\/bitbucket.org\/kien\/ctrlp.vim","install_details":"Extract the archive to ~\/.vim on Linux\/MacOSX or $HOME\\vimfiles on Windows.\r\nRun :helptags  ~\/.vim\/doc or :helptags $HOME\\vimfiles\\doc","5":"Extract the archive to ~\/.vim on Linux\/MacOSX or $HOME\\vimfiles on Windows.\r\nRun :helptags  ~\/.vim\/doc or :helptags $HOME\\vimfiles\\doc","first_name":" ","6":" ","last_name":" ","7":" ","releases":[{"0":"3736","vim_version":"7.0","1":"7.0","script_version":"1.79","2":"1.79","version_comment":"Changes since 1.7.6:\r\n* New options:\r\n  + g:ctrlp_tabpage_position\r\n  + g:ctrlp_open_func\r\n  + g:ctrlp_key_loop\r\n  + g:ctrlp_abbrev\r\n* Extended options (accepting new values):\r\n  + g:ctrlp_open_multiple_files\r\n  + g:ctrlp_follow_symlinks\r\n  + g:ctrlp_working_path_mode\r\n  + g:ctrlp_user_command\r\n  + g:ctrlp_switch_buffer\r\n* Default setting changes:\r\n\t+ Disable showing of hidden files and directories.\r\n\t+ Small change for working_path_mode.\r\n* Some minor tweaks and bugfixes.","3":"Changes since 1.7.6:\r\n* New options:\r\n  + g:ctrlp_tabpage_position\r\n  + g:ctrlp_open_func\r\n  + g:ctrlp_key_loop\r\n  + g:ctrlp_abbrev\r\n* Extended options (accepting new values):\r\n  + g:ctrlp_open_multiple_files\r\n  + g:ctrlp_follow_symlinks\r\n  + g:ctrlp_working_path_mode\r\n  + g:ctrlp_user_command\r\n  + g:ctrlp_switch_buffer\r\n* Default setting changes:\r\n\t+ Disable showing of hidden files and directories.\r\n\t+ Small change for working_path_mode.\r\n* Some minor tweaks and bugfixes.","package":"ctrlp.zip","4":"ctrlp.zip","src_id":"19448","5":"19448","creation_date":"1359434488","6":"1359434488"},{"0":"3736","vim_version":"7.0","1":"7.0","script_version":"1.7.6","2":"1.7.6","version_comment":"Changes since 1.7.4:\r\nNew commands:\r\n + CtrlPMixed (mixing files + buffers + MRUs)\r\n + CtrlPLastMode\r\n + CtrlPBookmarkDir\r\n + CtrlPBookmarkDirAdd\r\nNew options:\r\n + g:ctrlp_default_input\r\n + g:ctrlp_buffer_func\r\n + g:ctrlp_mruf_default_order\r\nImprove handling of options.\r\nSome enhancements toward extensions.\r\nBugfixes\/workarounds for Vim 7.0 and 7.1.\r\nSome tunings.","3":"Changes since 1.7.4:\r\nNew commands:\r\n + CtrlPMixed (mixing files + buffers + MRUs)\r\n + CtrlPLastMode\r\n + CtrlPBookmarkDir\r\n + CtrlPBookmarkDirAdd\r\nNew options:\r\n + g:ctrlp_default_input\r\n + g:ctrlp_buffer_func\r\n + g:ctrlp_mruf_default_order\r\nImprove handling of options.\r\nSome enhancements toward extensions.\r\nBugfixes\/workarounds for Vim 7.0 and 7.1.\r\nSome tunings.","package":"ctrlp.zip","4":"ctrlp.zip","src_id":"17830","5":"17830","creation_date":"1335590596","6":"1335590596"},{"0":"3736","vim_version":"7.0","1":"7.0","script_version":"1.7.4","2":"1.7.4","version_comment":"Changes since 1.6.9:\r\n+ Customizable highlighting for the prompt and match window.\r\n+ Support multiple user commands.\r\n+ Support per-buffer path_mode option.\r\n+ Add .svn\/ as a root marker (for SVN 1.7.0+).\r\n+ Support numpad keys.\r\n+ Allow deleting MRU entries.\r\n+ Disable Input Method inside the prompt.\r\n+ Option to use an external fuzzy matcher to power ctrlp.\r\n+ Add an extension: changes.vim.\r\n+ Small performance improvement.\r\n+ Various bugfixes and behavioral tweaks.","3":"Changes since 1.6.9:\r\n+ Customizable highlighting for the prompt and match window.\r\n+ Support multiple user commands.\r\n+ Support per-buffer path_mode option.\r\n+ Add .svn\/ as a root marker (for SVN 1.7.0+).\r\n+ Support numpad keys.\r\n+ Allow deleting MRU entries.\r\n+ Disable Input Method inside the prompt.\r\n+ Option to use an external fuzzy matcher to power ctrlp.\r\n+ Add an extension: changes.vim.\r\n+ Small performance improvement.\r\n+ Various bugfixes and behavioral tweaks.","package":"ctrlp.zip","4":"ctrlp.zip","src_id":"17669","5":"17669","creation_date":"1332879591","6":"1332879591"},{"0":"3736","vim_version":"7.0","1":"7.0","script_version":"1.6.9.1","2":"1.6.9.1","version_comment":"Fix an error when moving the selection in Vim 7.0 and 7.1.\r\nHide line prefix in terminal.\r\nDon't try to create an existing directory.","3":"Fix an error when moving the selection in Vim 7.0 and 7.1.\r\nHide line prefix in terminal.\r\nDon't try to create an existing directory.","package":"ctrlp.zip","4":"ctrlp.zip","src_id":"17319","5":"17319","creation_date":"1327574366","6":"1327574366"},{"0":"3736","vim_version":"7.0","1":"7.0","script_version":"1.6.9","2":"1.6.9","version_comment":"Changes from 1.6.3 to 1.6.9:\r\nAdd BufferTag extension.\r\n* Enable: `let g:ctrlp_extensions = ['buffertag']`\r\n* Commands: ':CtrlPBufTag [buffer-name]', ':CtrlPBufTagAll'\r\n* Options:\r\n  + g:ctrlp_buftag_ctags_bin\r\n  + g:ctrlp_buftag_systemenc\r\n  + g:ctrlp_buftag_types\r\nAdd Runtime Scripts extension (find vimscripts in runtimepath).\r\nAdd :CtrlPDir auto-completion.\r\nAdd directory <tab> completion to inside the prompt.\r\nAllow running commands like `:diffthis` when opening multiple files.\r\ntag.vim filters pseudo-tags generated by ctags.\r\nIgnore same-root symlink.\r\nAdd g:ctrlp_log, an option to write all output to .ctrlp_cache\/ctrlp.log\r\nEnhance jump-to-open-buffer to allow jumping to line number as well.\r\nMake statuslines customizable.\r\nNew or extended global options:\r\n  + g:ctrlp_custom_ignore\r\n  + g:ctrlp_log\r\n  + g:ctrlp_cmd\r\n  + g:ctrlp_arg_map\r\n  + g:ctrlp_open_multi\r\n  + g:ctrlp_mruf_relative\r\n  + g:ctrlp_status_func\r\n  + g:ctrlp_mruf_last_entered\r\nAdd experimental extension:\r\n  + undo.vim (requires v7.3.005+)\r\nSome bugfixes and internal improvements.","3":"Changes from 1.6.3 to 1.6.9:\r\nAdd BufferTag extension.\r\n* Enable: `let g:ctrlp_extensions = ['buffertag']`\r\n* Commands: ':CtrlPBufTag [buffer-name]', ':CtrlPBufTagAll'\r\n* Options:\r\n  + g:ctrlp_buftag_ctags_bin\r\n  + g:ctrlp_buftag_systemenc\r\n  + g:ctrlp_buftag_types\r\nAdd Runtime Scripts extension (find vimscripts in runtimepath).\r\nAdd :CtrlPDir auto-completion.\r\nAdd directory <tab> completion to inside the prompt.\r\nAllow running commands like `:diffthis` when opening multiple files.\r\ntag.vim filters pseudo-tags generated by ctags.\r\nIgnore same-root symlink.\r\nAdd g:ctrlp_log, an option to write all output to .ctrlp_cache\/ctrlp.log\r\nEnhance jump-to-open-buffer to allow jumping to line number as well.\r\nMake statuslines customizable.\r\nNew or extended global options:\r\n  + g:ctrlp_custom_ignore\r\n  + g:ctrlp_log\r\n  + g:ctrlp_cmd\r\n  + g:ctrlp_arg_map\r\n  + g:ctrlp_open_multi\r\n  + g:ctrlp_mruf_relative\r\n  + g:ctrlp_status_func\r\n  + g:ctrlp_mruf_last_entered\r\nAdd experimental extension:\r\n  + undo.vim (requires v7.3.005+)\r\nSome bugfixes and internal improvements.","package":"ctrlp.zip","4":"ctrlp.zip","src_id":"17310","5":"17310","creation_date":"1327372118","6":"1327372118"},{"0":"3736","vim_version":"7.0","1":"7.0","script_version":"1.6.3","2":"1.6.3","version_comment":"Tag, Quickfix and Directory extensions.","3":"Tag, Quickfix and Directory extensions.","package":"ctrlp.zip","4":"ctrlp.zip","src_id":"17030","5":"17030","creation_date":"1323187650","6":"1323187650"},{"0":"3736","vim_version":"7.0","1":"7.0","script_version":"1.6.1","2":"1.6.1","version_comment":"Some bugfixes and several new features.\r\nNew or extended options:\r\n+ g:ctrlp_mruf_case_sensitive\r\n+ g:ctrlp_dont_split\r\n+ g:ctrlp_open_multi\r\n+ g:ctrlp_follow_symlinks","3":"Some bugfixes and several new features.\r\nNew or extended options:\r\n+ g:ctrlp_mruf_case_sensitive\r\n+ g:ctrlp_dont_split\r\n+ g:ctrlp_open_multi\r\n+ g:ctrlp_follow_symlinks","package":"ctrlp.zip","4":"ctrlp.zip","src_id":"16944","5":"16944","creation_date":"1321987360","6":"1321987360"},{"0":"3736","vim_version":"7.0","1":"7.0","script_version":"1.5.8","2":"1.5.8","version_comment":"Add support for extensions.\r\nSome refactorings, bugfixes and a small performance improvement.","3":"Add support for extensions.\r\nSome refactorings, bugfixes and a small performance improvement.","package":"ctrlp.zip","4":"ctrlp.zip","src_id":"16817","5":"16817","creation_date":"1320613932","6":"1320613932"},{"0":"3736","vim_version":"7.0","1":"7.0","script_version":"1.5","2":"1.5","version_comment":"Open Multiple Files","3":"Open Multiple Files","package":"ctrlp.zip","4":"ctrlp.zip","src_id":"16617","5":"16617","creation_date":"1317676482","6":"1317676482"}]},"3735":{"script_id":"3735","0":"3735","script_name":"bad-whitespace","1":"bad-whitespace","script_type":"utility","2":"utility","summary":"Highlights whitespace at the end of lines, only in modifiable buffers","3":"Highlights whitespace at the end of lines, only in modifiable buffers","description":"Get the latest version at:\r\nhttps:\/\/github.com\/bitc\/vim-bad-whitespace\r\n\r\nInspired by the trailing-whitespace vimscript #3201\r\n\r\nAdditional References:\r\nhttp:\/\/vim.wikia.com\/wiki\/Highlight_unwanted_spaces\r\nhttp:\/\/sartak.org\/2011\/03\/end-of-line-whitespace-in-vim.html\r\n\r\nAbout ~\r\n\r\nThis plugin highlights whitespace at the end of lines with a red color.\r\n\r\nYou can erase the bad whitespace with the command |EraseBadWhitespace|\r\n\r\nYou can manually toggle the highlighting for the current buffer with the\r\ncommands |ShowBadWhitespace| |HideBadWhitespace| |ToggleBadWhitespace|\r\n\r\nThis plugin is better than using the builtin vim 'list' command because it\r\ndoesn't show an annoying highlight while you are typing in insert mode at the\r\nend of a line.\r\n\r\nThis plugin is better than competing plugins because it doesn't show\r\nhighlighting in buffers that are not modifiable, which is usually what you\r\nwant. This makes it compatible with UI buffers that happen to contain bad\r\nwhitespace, such as the quickfix window, or the fugitive plugin.","4":"Get the latest version at:\r\nhttps:\/\/github.com\/bitc\/vim-bad-whitespace\r\n\r\nInspired by the trailing-whitespace vimscript #3201\r\n\r\nAdditional References:\r\nhttp:\/\/vim.wikia.com\/wiki\/Highlight_unwanted_spaces\r\nhttp:\/\/sartak.org\/2011\/03\/end-of-line-whitespace-in-vim.html\r\n\r\nAbout ~\r\n\r\nThis plugin highlights whitespace at the end of lines with a red color.\r\n\r\nYou can erase the bad whitespace with the command |EraseBadWhitespace|\r\n\r\nYou can manually toggle the highlighting for the current buffer with the\r\ncommands |ShowBadWhitespace| |HideBadWhitespace| |ToggleBadWhitespace|\r\n\r\nThis plugin is better than using the builtin vim 'list' command because it\r\ndoesn't show an annoying highlight while you are typing in insert mode at the\r\nend of a line.\r\n\r\nThis plugin is better than competing plugins because it doesn't show\r\nhighlighting in buffers that are not modifiable, which is usually what you\r\nwant. This makes it compatible with UI buffers that happen to contain bad\r\nwhitespace, such as the quickfix window, or the fugitive plugin.","install_details":"Install with pathogen or Vundle.\r\n\r\nManual install: Copy bad-whitespace.vim in to ~\/.vim\/plugin and bad-whitespace.txt in to ~\/.vim\/doc","5":"Install with pathogen or Vundle.\r\n\r\nManual install: Copy bad-whitespace.vim in to ~\/.vim\/plugin and bad-whitespace.txt in to ~\/.vim\/doc","first_name":"Bit","6":"Bit","last_name":"Connor","7":"Connor","releases":[{"0":"3735","vim_version":"7.0","1":"7.0","script_version":"0.3","2":"0.3","version_comment":"Allow color overriding\r\nAllow reloading of the script","3":"Allow color overriding\r\nAllow reloading of the script","package":"vim-bad-whitespace-0.3.tar.gz","4":"vim-bad-whitespace-0.3.tar.gz","src_id":"18336","5":"18336","creation_date":"1343529657","6":"1343529657"},{"0":"3735","vim_version":"7.0","1":"7.0","script_version":"0.2","2":"0.2","version_comment":"Update docs","3":"Update docs","package":"vim-bad-whitespace-0.2.tar.gz","4":"vim-bad-whitespace-0.2.tar.gz","src_id":"16488","5":"16488","creation_date":"1315404826","6":"1315404826"},{"0":"3735","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"vim-bad-whitespace-0.1.tar.gz","4":"vim-bad-whitespace-0.1.tar.gz","src_id":"16485","5":"16485","creation_date":"1315403536","6":"1315403536"}]},"3734":{"script_id":"3734","0":"3734","script_name":"statusline.vim","1":"statusline.vim","script_type":"utility","2":"utility","summary":"Beautify statusline","3":"Beautify statusline","description":"         This script is inspired by the light2011 colorscheme (vimscript#3714).\r\n         Thanks for xiaohuyee to give us such a pretty gift. \r\n          He did most of the work. I just stood on his shoulders.\r\n          \r\n         I am looking for a beautiful vim statusline for a long time but found nothing until I met the light2011.\r\n         Last night I spent several hours to beautify my statusline, it looks good.\r\n         And now I give it to you.\r\n\r\n         It is beautiful on gvim. \r\n         However if you use vim on console, it is not so beautiful, but still useful.\r\n\r\nScreenshot  \r\n         http:\/\/vimer.1063083.n5.nabble.com\/beautiful-vim-statusline-td4777850.html\r\n         \r\nTutorial\r\n         Download it, use it, and change it.\r\n\r\n         It is good on my laptop, but maybe bad on yours.  \r\n         Perhaps you should edit the source code to suit your vim.\r\n         When you edit it, do not erase trailing-blanks.\r\n\r\n         If you use light2011 colorscheme, you'd better comment its statusline codes.\r\n\r\n         When you switch colorscheme, the background of statusline changes too.\r\n         You should source statusline.vim by manual to recover it. \r\n         Like:\r\n                  :colo underwater\r\n                  :source c:\/vim\/vimfiles\/plugin\/statusline.vim\r\n                  or\r\n                  :source ~\/.vim\/plugin\/statusline.vim\r\n\r\n          In fact, you can use autocmd to simplify this:\r\n                    autocmd! ColorScheme *  source c:\/vim\/vimfiles\/plugin\/statusline.vim\r\n                    or\r\n                    autocmd! ColorScheme *  source ~\/.vim\/plugin\/statusline.vim","4":"         This script is inspired by the light2011 colorscheme (vimscript#3714).\r\n         Thanks for xiaohuyee to give us such a pretty gift. \r\n          He did most of the work. I just stood on his shoulders.\r\n          \r\n         I am looking for a beautiful vim statusline for a long time but found nothing until I met the light2011.\r\n         Last night I spent several hours to beautify my statusline, it looks good.\r\n         And now I give it to you.\r\n\r\n         It is beautiful on gvim. \r\n         However if you use vim on console, it is not so beautiful, but still useful.\r\n\r\nScreenshot  \r\n         http:\/\/vimer.1063083.n5.nabble.com\/beautiful-vim-statusline-td4777850.html\r\n         \r\nTutorial\r\n         Download it, use it, and change it.\r\n\r\n         It is good on my laptop, but maybe bad on yours.  \r\n         Perhaps you should edit the source code to suit your vim.\r\n         When you edit it, do not erase trailing-blanks.\r\n\r\n         If you use light2011 colorscheme, you'd better comment its statusline codes.\r\n\r\n         When you switch colorscheme, the background of statusline changes too.\r\n         You should source statusline.vim by manual to recover it. \r\n         Like:\r\n                  :colo underwater\r\n                  :source c:\/vim\/vimfiles\/plugin\/statusline.vim\r\n                  or\r\n                  :source ~\/.vim\/plugin\/statusline.vim\r\n\r\n          In fact, you can use autocmd to simplify this:\r\n                    autocmd! ColorScheme *  source c:\/vim\/vimfiles\/plugin\/statusline.vim\r\n                    or\r\n                    autocmd! ColorScheme *  source ~\/.vim\/plugin\/statusline.vim","install_details":"         Put this file in ~\/.vim\/plugin on *nix.\r\n         Or put it in $vim\/vimfiles\/plugin on Windows.\r\n\r\nUninstall\r\n         Just delete it from your disk.","5":"         Put this file in ~\/.vim\/plugin on *nix.\r\n         Or put it in $vim\/vimfiles\/plugin on Windows.\r\n\r\nUninstall\r\n         Just delete it from your disk.","first_name":"Tian","6":"Tian","last_name":"Huixiong","7":"Huixiong","releases":[{"0":"3734","vim_version":"7.0","1":"7.0","script_version":"1.1","2":"1.1","version_comment":"Update doc ","3":"Update doc ","package":"statusline.vim","4":"statusline.vim","src_id":"16487","5":"16487","creation_date":"1315404467","6":"1315404467"},{"0":"3734","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Update doc ","3":"Update doc ","package":"statusline.vim","4":"statusline.vim","src_id":"16486","5":"16486","creation_date":"1315404432","6":"1315404432"},{"0":"3734","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"statusline.vim","4":"statusline.vim","src_id":"16482","5":"16482","creation_date":"1315386111","6":"1315386111"}]},"3733":{"script_id":"3733","0":"3733","script_name":"olga_key","1":"olga_key","script_type":"syntax","2":"syntax","summary":"Syntax file for SPT Group OLGA .key and .genkey files","3":"Syntax file for SPT Group OLGA .key and .genkey files","description":"This is an unofficial syntax file for SPT Group OLGA .key and .genkey files. (There is also partial support for the older .inp format)\r\n\r\nOLGA is the market-leading simulator for engineering the flow of oil, water and gas in wells, pipelines and receiving facilities. \r\n\r\nAlso available on github: https:\/\/github.com\/knatten\/olga_key","4":"This is an unofficial syntax file for SPT Group OLGA .key and .genkey files. (There is also partial support for the older .inp format)\r\n\r\nOLGA is the market-leading simulator for engineering the flow of oil, water and gas in wells, pipelines and receiving facilities. \r\n\r\nAlso available on github: https:\/\/github.com\/knatten\/olga_key","install_details":"Linux: Put this file in ~\/.vim\/syntax\r\nWindows 7: Put this file in C:\\Users\\<your_username>\\vimfiles\r\n\r\nIn .vimrc, activate automatic setting of filetype for .key, .genkey, .inp and .rsw files:\r\nau BufRead,BufNewFile *.key setfiletype olga_key\r\nau BufRead,BufNewFile *.genkey setfiletype olga_key\r\nau BufRead,BufNewFile *.inp setfiletype olga_key\r\nau BufRead,BufNewFile *.rsw setfiletype olga_key\r\n\r\n(If you don't have syntax highlighting turned on, do: syntax on)","5":"Linux: Put this file in ~\/.vim\/syntax\r\nWindows 7: Put this file in C:\\Users\\<your_username>\\vimfiles\r\n\r\nIn .vimrc, activate automatic setting of filetype for .key, .genkey, .inp and .rsw files:\r\nau BufRead,BufNewFile *.key setfiletype olga_key\r\nau BufRead,BufNewFile *.genkey setfiletype olga_key\r\nau BufRead,BufNewFile *.inp setfiletype olga_key\r\nau BufRead,BufNewFile *.rsw setfiletype olga_key\r\n\r\n(If you don't have syntax highlighting turned on, do: syntax on)","first_name":"Anders Schau","6":"Anders Schau","last_name":"Knatten","7":"Knatten","releases":[{"0":"3733","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"olga_key.vim","4":"olga_key.vim","src_id":"16478","5":"16478","creation_date":"1315378269","6":"1315378269"}]},"3732":{"script_id":"3732","0":"3732","script_name":"vim-rpsl","1":"vim-rpsl","script_type":"syntax","2":"syntax","summary":"RPSL languge syntax highlighter","3":"RPSL languge syntax highlighter","description":"This script allows vim to recognize and highlight files in RPSL (aka Whois) format. Files *.rpsl suffix are recognized. Highlighting of keywords, class names\/values and comments is present. \r\n\r\nProject homepage: https:\/\/github.com\/argent-smith\/vim-rpsl \r\nAuthor's homepage: http:\/\/argent-smith.github.com","4":"This script allows vim to recognize and highlight files in RPSL (aka Whois) format. Files *.rpsl suffix are recognized. Highlighting of keywords, class names\/values and comments is present. \r\n\r\nProject homepage: https:\/\/github.com\/argent-smith\/vim-rpsl \r\nAuthor's homepage: http:\/\/argent-smith.github.com","install_details":"Unpack the archive into the appropriate place and restart Vim (or reload configuration in any appropriate way).","5":"Unpack the archive into the appropriate place and restart Vim (or reload configuration in any appropriate way).","first_name":"Pavel","6":"Pavel","last_name":"Argentov","7":"Argentov","releases":[{"0":"3732","vim_version":"7.0","1":"7.0","script_version":"0.0.2","2":"0.0.2","version_comment":"Added some useful info to README.","3":"Added some useful info to README.","package":"vim-rpsl-v0.0.2.tar.bz2","4":"vim-rpsl-v0.0.2.tar.bz2","src_id":"16481","5":"16481","creation_date":"1315384894","6":"1315384894"},{"0":"3732","vim_version":"7.0","1":"7.0","script_version":"0.0.1","2":"0.0.1","version_comment":"Initial upload","3":"Initial upload","package":"vim-rpsl-v0.0.1.zip","4":"vim-rpsl-v0.0.1.zip","src_id":"16477","5":"16477","creation_date":"1315317753","6":"1315317753"}]},"3731":{"script_id":"3731","0":"3731","script_name":"putcmd.vim","1":"putcmd.vim","script_type":"utility","2":"utility","summary":"Insert command and its result","3":"Insert command and its result","description":"         When you execute a command, its result is showing in the command line.\r\n         Sometimes you want to yank it, but unfortunately you can not edit the result in the command line.\r\n\r\n         Putcmd can help you. \r\n         It inserts the command and its result after the current line, so you can edit them easily.\r\n\r\nTutorial\r\n         :Putcmd command\r\n\r\n         :Putcmd set\r\n         :Putcmd colo\r\n         :Putcmd set guifont?\r\n         :Putcmd set tabstop?","4":"         When you execute a command, its result is showing in the command line.\r\n         Sometimes you want to yank it, but unfortunately you can not edit the result in the command line.\r\n\r\n         Putcmd can help you. \r\n         It inserts the command and its result after the current line, so you can edit them easily.\r\n\r\nTutorial\r\n         :Putcmd command\r\n\r\n         :Putcmd set\r\n         :Putcmd colo\r\n         :Putcmd set guifont?\r\n         :Putcmd set tabstop?","install_details":"         Put this file in ~\/.vim\/plugin on *nix\r\n         Or put it in $vim\/vimfiles\/plugin on Windows","5":"         Put this file in ~\/.vim\/plugin on *nix\r\n         Or put it in $vim\/vimfiles\/plugin on Windows","first_name":"Tian","6":"Tian","last_name":"Huixiong","7":"Huixiong","releases":[{"0":"3731","vim_version":"7.0","1":"7.0","script_version":"1.3","2":"1.3","version_comment":"Bug fixed: When the command's output is text of multiple lines. New lines are printed as ^@, what we want is a really new line, not this.","3":"Bug fixed: When the command's output is text of multiple lines. New lines are printed as ^@, what we want is a really new line, not this.","package":"putcmd.vim","4":"putcmd.vim","src_id":"16526","5":"16526","creation_date":"1316013864","6":"1316013864"},{"0":"3731","vim_version":"7.0","1":"7.0","script_version":"1.2","2":"1.2","version_comment":"Update description.","3":"Update description.","package":"putcmd.vim","4":"putcmd.vim","src_id":"16484","5":"16484","creation_date":"1315403026","6":"1315403026"},{"0":"3731","vim_version":"7.0","1":"7.0","script_version":"1.1","2":"1.1","version_comment":"By put the command and its result after the current line, then you can edit them easily.","3":"By put the command and its result after the current line, then you can edit them easily.","package":"putcmd.vim","4":"putcmd.vim","src_id":"16480","5":"16480","creation_date":"1315382393","6":"1315382393"},{"0":"3731","vim_version":"7.0","1":"7.0","script_version":"1.1","2":"1.1","version_comment":"Put the command and its result after the current line.","3":"Put the command and its result after the current line.","package":"putcmd.vim","4":"putcmd.vim","src_id":"16479","5":"16479","creation_date":"1315379271","6":"1315379271"},{"0":"3731","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"putcmd.vim","4":"putcmd.vim","src_id":"16476","5":"16476","creation_date":"1315308116","6":"1315308116"}]},"3730":{"script_id":"3730","0":"3730","script_name":"vim-pandoc","1":"vim-pandoc","script_type":"ftplugin","2":"ftplugin","summary":"a plugin for writing in pandoc's extended markdown","3":"a plugin for writing in pandoc's extended markdown","description":"This is a plugin for writing and editing documents in pandoc's extended markdown. Pandoc converts markdown to several formats, including html, latex, context, pdf (via latex), odt, rst, epub, docbook, and org-mode. It's extended markdown supports footnotes, tables, definition lists, superscript and subscript, strikeout, enhanced ordered lists, delimited code blocks, markdown inside HTML blocks, TeX math, and citations. For more information on pandoc, see http:\/\/johnmacfarlane.net\/pandoc\r\n\r\nThis plugin provides:\r\n\r\n-   some settings to make vim a pleasant pandoc writing environment\r\n-   syntax highlighting, with support for pandoc's extended markdown\r\n-   snippets for use with snipMate\r\n-   section folding\r\n-   citation completion from bibtex, MODS, RIS and citeproc JSON files\r\n-   some simple conversion and tidying functions and localleader mappings\r\n\r\nFor the latest version, visit https:\/\/github.com\/vim-pandoc\/vim-pandoc\r\n\r\nPlease direct feature suggestions, bug reports, etc., to https:\/\/github.com\/vim-pandoc\/vim-pandoc\/issues\r\n\r\nThe included syntax file is a descendent of Jeremy Schultz's vimscript#2389, which is no longer being maintained.","4":"This is a plugin for writing and editing documents in pandoc's extended markdown. Pandoc converts markdown to several formats, including html, latex, context, pdf (via latex), odt, rst, epub, docbook, and org-mode. It's extended markdown supports footnotes, tables, definition lists, superscript and subscript, strikeout, enhanced ordered lists, delimited code blocks, markdown inside HTML blocks, TeX math, and citations. For more information on pandoc, see http:\/\/johnmacfarlane.net\/pandoc\r\n\r\nThis plugin provides:\r\n\r\n-   some settings to make vim a pleasant pandoc writing environment\r\n-   syntax highlighting, with support for pandoc's extended markdown\r\n-   snippets for use with snipMate\r\n-   section folding\r\n-   citation completion from bibtex, MODS, RIS and citeproc JSON files\r\n-   some simple conversion and tidying functions and localleader mappings\r\n\r\nFor the latest version, visit https:\/\/github.com\/vim-pandoc\/vim-pandoc\r\n\r\nPlease direct feature suggestions, bug reports, etc., to https:\/\/github.com\/vim-pandoc\/vim-pandoc\/issues\r\n\r\nThe included syntax file is a descendent of Jeremy Schultz's vimscript#2389, which is no longer being maintained.","install_details":"","5":"","first_name":"David","6":"David","last_name":"Sanson","7":"Sanson","releases":[{"0":"3730","vim_version":"7.0","1":"7.0","script_version":"2.0","2":"2.0","version_comment":"For what's changed, see https:\/\/github.com\/vim-pandoc\/vim-pandoc\/blob\/2.0\/VERSIONS.txt","3":"For what's changed, see https:\/\/github.com\/vim-pandoc\/vim-pandoc\/blob\/2.0\/VERSIONS.txt","package":"vim-pandoc-2.0.zip","4":"vim-pandoc-2.0.zip","src_id":"16532","5":"16532","creation_date":"1316116293","6":"1316116293"},{"0":"3730","vim_version":"7.3","1":"7.3","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"vim-pandoc-1.0.tar.gz","4":"vim-pandoc-1.0.tar.gz","src_id":"16471","5":"16471","creation_date":"1315248141","6":"1315248141"}]},"3729":{"script_id":"3729","0":"3729","script_name":"galaxy.vim","1":"galaxy.vim","script_type":"color scheme","2":"color scheme","summary":"Simpler colorscheming.","3":"Simpler colorscheming.","description":"**Galaxy** is a colorscheme tries to make colorscheming simpler.\r\n    \r\n    A nice colorscheme is good for our eyes (and display).\r\n    But generating one is not that easy.\r\n    When generating a colorschemes, you must dealing with lots of issues: \r\n    colors, highlight groups, syntaxs, terminals...\r\n\r\n    Galaxy tries to simplifiy these works. \r\n    \r\n    It classifies highlights in 'bgd','fgd','syn','msg','dif' group,\r\n    and automatically generate these highlight colors with these 5 group's \r\n    basic colors. And do other stuffs to finish highlighting.\r\n\r\n    So, for one scheme, only 5 colors are needed.\r\n\r\n    It contains several built-in schemes.\r\n    Also Scheme Window, Screen Window, Terminal Support, Stylish Statusline,\r\n    Indent Highlight and more...\r\n\r\n    \r\n**Some Pictures:**\r\n        \r\n        Normal (Git Dif) : http:\/\/img.ly\/images\/4154624\/full\r\n\r\n        Screen & Scheme  : http:\/\/img.ly\/images\/4154631\/full\r\n\r\n\r\nPost issues at https:\/\/github.com\/Rykka\/galaxy.vim\r\n","4":"**Galaxy** is a colorscheme tries to make colorscheming simpler.\r\n    \r\n    A nice colorscheme is good for our eyes (and display).\r\n    But generating one is not that easy.\r\n    When generating a colorschemes, you must dealing with lots of issues: \r\n    colors, highlight groups, syntaxs, terminals...\r\n\r\n    Galaxy tries to simplifiy these works. \r\n    \r\n    It classifies highlights in 'bgd','fgd','syn','msg','dif' group,\r\n    and automatically generate these highlight colors with these 5 group's \r\n    basic colors. And do other stuffs to finish highlighting.\r\n\r\n    So, for one scheme, only 5 colors are needed.\r\n\r\n    It contains several built-in schemes.\r\n    Also Scheme Window, Screen Window, Terminal Support, Stylish Statusline,\r\n    Indent Highlight and more...\r\n\r\n    \r\n**Some Pictures:**\r\n        \r\n        Normal (Git Dif) : http:\/\/img.ly\/images\/4154624\/full\r\n\r\n        Screen & Scheme  : http:\/\/img.ly\/images\/4154631\/full\r\n\r\n\r\nPost issues at https:\/\/github.com\/Rykka\/galaxy.vim\r\n","install_details":"1. Using Vundle  https:\/\/github.com\/gmarik\/vundle \r\n\r\n    Add two lines to your vimrc\r\n    `Bundle 'Rykka\/colorv.vim'` \r\n    `Bundle 'Rykka\/galaxy.vim'` \r\n\r\n2. Using Vim.org http:\/\/www.vim.org\/scripts\/script.php?script_id=3729\r\n\r\n    Extract to your ~\/.vim folder.\r\n    `:helptags ~\/.vim\/doc`\r\n    \r\n**NOTE**   ColorV required if downloaded from github.\r\n\r\n**NOTE**   Get Latest version\r\n           https:\/\/github.com\/Rykka\/colorv.vim\/\r\n           https:\/\/github.com\/Rykka\/galaxy.vim\/\r\n","5":"1. Using Vundle  https:\/\/github.com\/gmarik\/vundle \r\n\r\n    Add two lines to your vimrc\r\n    `Bundle 'Rykka\/colorv.vim'` \r\n    `Bundle 'Rykka\/galaxy.vim'` \r\n\r\n2. Using Vim.org http:\/\/www.vim.org\/scripts\/script.php?script_id=3729\r\n\r\n    Extract to your ~\/.vim folder.\r\n    `:helptags ~\/.vim\/doc`\r\n    \r\n**NOTE**   ColorV required if downloaded from github.\r\n\r\n**NOTE**   Get Latest version\r\n           https:\/\/github.com\/Rykka\/colorv.vim\/\r\n           https:\/\/github.com\/Rykka\/galaxy.vim\/\r\n","first_name":"Rykka","6":"Rykka","last_name":"f","7":"f","releases":[{"0":"3729","vim_version":"7.0","1":"7.0","script_version":"2.0.1","2":"2.0.1","version_comment":"\" fix  terminal cursors\r\n\" change repo to galaxy.vim","3":"\" fix  terminal cursors\r\n\" change repo to galaxy.vim","package":"colorv.vim+galaxy.vim.zip","4":"colorv.vim+galaxy.vim.zip","src_id":"17934","5":"17934","creation_date":"1336740117","6":"1336740117"},{"0":"3729","vim_version":"7.0","1":"7.0","script_version":"2.0.1","2":"2.0.1","version_comment":"\" Add Screen window\r\n\" Add stylish statusline\r\n\" fix bugs ... more in changelog.","3":"\" Add Screen window\r\n\" Add stylish statusline\r\n\" fix bugs ... more in changelog.","package":"Rykka-vim-galaxy-2.0.1+ColorV.zip","4":"Rykka-vim-galaxy-2.0.1+ColorV.zip","src_id":"17819","5":"17819","creation_date":"1335430451","6":"1335430451"},{"0":"3729","vim_version":"7.0","1":"7.0","script_version":"1.2.0","2":"1.2.0","version_comment":"Add indent highlight. \r\nschemes tuned and fixed.\r\n","3":"Add indent highlight. \r\nschemes tuned and fixed.\r\n","package":"vim-galaxy-1.2.0.tar.gz","4":"vim-galaxy-1.2.0.tar.gz","src_id":"17295","5":"17295","creation_date":"1327248116","6":"1327248116"},{"0":"3729","vim_version":"7.0","1":"7.0","script_version":"1.1.0","2":"1.1.0","version_comment":"- support :Galaxy without colorscheme this.\r\n- bug fixed and tuned built-in colors and genertor","3":"- support :Galaxy without colorscheme this.\r\n- bug fixed and tuned built-in colors and genertor","package":"vim-galaxy_1.1.0.tar.gz","4":"vim-galaxy_1.1.0.tar.gz","src_id":"16501","5":"16501","creation_date":"1315708078","6":"1315708078"}]},"3728":{"script_id":"3728","0":"3728","script_name":"right_align","1":"right_align","script_type":"utility","2":"utility","summary":"Right alignment of string under cursor","3":"Right alignment of string under cursor","description":"This script can be used to align the line under cursor to the right border. The value of the right border column can be specified using global varialbe g:RightAlign_RightBorder in your .vimrc file, for example:\r\n\r\nlet g:RightAlign_RightBorder = 80\r\n\r\nIf g:RightAlign_RightBorder is not set then value of option textwidth will be used. Alignment to the right border means that the right edge of the string will not exceed the specified value but will be as close as possible according to your shiftwidth and shiftround settings. For example if shiftwidth is 4, shiftround is set, g:RightAlign_RightBorder is 80 and length of the current line is 14, then first non-space character of this line will be moved to 65th column. This behaviour differs from that of builtin command :right.\r\n\r\nSince version 0.5 the shiftround behaviour is active even If you did not set option shiftround. This is due to default value of variable g:RightAlign_ShiftRound is equal 1. If you do not want shiftround behaviour then put in your .vimrc line\r\n\r\nlet g:RightAlign_ShiftRound = 0\r\n\r\nThe script provides single command RightAlign with an optional argument. The optional argument can be set to 'kc' in order to make script function keep cursor on the same character of the line when moving it: this is especially useful in insert mode.\r\n\r\nTo use script efficiently you can choose to use mappings in insert and normal mode, for example\r\n\r\nimap <silent> <C-b>    <Plug>RightAlign\r\nnmap <silent> <C-k>b    :RightAlign<CR>\r\nvmap <silent> <C-k>b    :RightAlign<CR>\r\n\r\nNow when you press ^b in insert mode the line under cursor will be aligned to the right according to values of the g:RightAlign_RightBorder or textwidth, cursor position will not change in relation to the content of the string. This mapping can be regarded as addition to existing commands ^d, ^t and ^f in insert mode. The second and third mappings enable RightAlign in normal and visual modes respectively when pressing ^kb. In normal mode a range value may be specified to right-align multiple lines at once, for example entering 10^kb will right-align the current line and 9 lines below it.","4":"This script can be used to align the line under cursor to the right border. The value of the right border column can be specified using global varialbe g:RightAlign_RightBorder in your .vimrc file, for example:\r\n\r\nlet g:RightAlign_RightBorder = 80\r\n\r\nIf g:RightAlign_RightBorder is not set then value of option textwidth will be used. Alignment to the right border means that the right edge of the string will not exceed the specified value but will be as close as possible according to your shiftwidth and shiftround settings. For example if shiftwidth is 4, shiftround is set, g:RightAlign_RightBorder is 80 and length of the current line is 14, then first non-space character of this line will be moved to 65th column. This behaviour differs from that of builtin command :right.\r\n\r\nSince version 0.5 the shiftround behaviour is active even If you did not set option shiftround. This is due to default value of variable g:RightAlign_ShiftRound is equal 1. If you do not want shiftround behaviour then put in your .vimrc line\r\n\r\nlet g:RightAlign_ShiftRound = 0\r\n\r\nThe script provides single command RightAlign with an optional argument. The optional argument can be set to 'kc' in order to make script function keep cursor on the same character of the line when moving it: this is especially useful in insert mode.\r\n\r\nTo use script efficiently you can choose to use mappings in insert and normal mode, for example\r\n\r\nimap <silent> <C-b>    <Plug>RightAlign\r\nnmap <silent> <C-k>b    :RightAlign<CR>\r\nvmap <silent> <C-k>b    :RightAlign<CR>\r\n\r\nNow when you press ^b in insert mode the line under cursor will be aligned to the right according to values of the g:RightAlign_RightBorder or textwidth, cursor position will not change in relation to the content of the string. This mapping can be regarded as addition to existing commands ^d, ^t and ^f in insert mode. The second and third mappings enable RightAlign in normal and visual modes respectively when pressing ^kb. In normal mode a range value may be specified to right-align multiple lines at once, for example entering 10^kb will right-align the current line and 9 lines below it.","install_details":"put the script in plugin directory","5":"put the script in plugin directory","first_name":"Alexey","6":"Alexey","last_name":"Radkov","7":"Radkov","releases":[{"0":"3728","vim_version":"7.0","1":"7.0","script_version":"0.7","2":"0.7","version_comment":"fixed alignment of wrapped lines \/ narrow windows","3":"fixed alignment of wrapped lines \/ narrow windows","package":"right_align.vim","4":"right_align.vim","src_id":"21582","5":"21582","creation_date":"1394379889","6":"1394379889"},{"0":"3728","vim_version":"7.0","1":"7.0","script_version":"0.6","2":"0.6","version_comment":"simple workaround for cases when line is wrapped and options 'linebreak' and\/or 'showbreak' are set","3":"simple workaround for cases when line is wrapped and options 'linebreak' and\/or 'showbreak' are set","package":"right_align.vim","4":"right_align.vim","src_id":"17126","5":"17126","creation_date":"1325148687","6":"1325148687"},{"0":"3728","vim_version":"7.0","1":"7.0","script_version":"0.5.1","2":"0.5.1","version_comment":"small bugfix","3":"small bugfix","package":"right_align.vim","4":"right_align.vim","src_id":"17074","5":"17074","creation_date":"1324029260","6":"1324029260"},{"0":"3728","vim_version":"7.0","1":"7.0","script_version":"0.5","2":"0.5","version_comment":"- variable g:RightBorder was renamed to g:RightAlign_RightBorder\r\n- a new variable g:RightAlign_ShiftRound was added to allow using shiftround behaviour even when option 'shiftround' is not set (the variable is set by default)\r\n- small bug fixes and improvements","3":"- variable g:RightBorder was renamed to g:RightAlign_RightBorder\r\n- a new variable g:RightAlign_ShiftRound was added to allow using shiftround behaviour even when option 'shiftround' is not set (the variable is set by default)\r\n- small bug fixes and improvements","package":"right_align.vim","4":"right_align.vim","src_id":"17060","5":"17060","creation_date":"1323850312","6":"1323850312"},{"0":"3728","vim_version":"7.0","1":"7.0","script_version":"0.4","2":"0.4","version_comment":"Range capability was added to command RightAlign, which makes it possible to right align multiple lines at once in normal and visual modes","3":"Range capability was added to command RightAlign, which makes it possible to right align multiple lines at once in normal and visual modes","package":"right_align.vim","4":"right_align.vim","src_id":"16941","5":"16941","creation_date":"1321970875","6":"1321970875"},{"0":"3728","vim_version":"7.0","1":"7.0","script_version":"0.3","2":"0.3","version_comment":"bugfix: do not align if the line under cursor contains only blank characters","3":"bugfix: do not align if the line under cursor contains only blank characters","package":"right_align.vim","4":"right_align.vim","src_id":"16475","5":"16475","creation_date":"1315303746","6":"1315303746"},{"0":"3728","vim_version":"7.0","1":"7.0","script_version":"0.2","2":"0.2","version_comment":"1. a new <Plug> imap implemented using <C-r>= instead of <C-o>: the latter option splits undo history in insert mode, therefore it could make unwanted jumps in history list; as such recommended mapping in insert mode was changed. Also the cursor position after undo will be kept now. The both changes make right_align function mimic behaviour of builtin insert mode commands ^t, ^d and ^f.\r\n2. Optional parameter of RightAlign command was renamed from 'on' to 'kc' (which means Keep Cursor)","3":"1. a new <Plug> imap implemented using <C-r>= instead of <C-o>: the latter option splits undo history in insert mode, therefore it could make unwanted jumps in history list; as such recommended mapping in insert mode was changed. Also the cursor position after undo will be kept now. The both changes make right_align function mimic behaviour of builtin insert mode commands ^t, ^d and ^f.\r\n2. Optional parameter of RightAlign command was renamed from 'on' to 'kc' (which means Keep Cursor)","package":"right_align.vim","4":"right_align.vim","src_id":"16467","5":"16467","creation_date":"1315243904","6":"1315243904"},{"0":"3728","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"right_align.vim","4":"right_align.vim","src_id":"16453","5":"16453","creation_date":"1315139120","6":"1315139120"}]},"3727":{"script_id":"3727","0":"3727","script_name":"easychair","1":"easychair","script_type":"syntax","2":"syntax","summary":"Syntax definition for EasyChair review files","3":"Syntax definition for EasyChair review files","description":"The definition is based on markdown so markdown (and html) syntax is mentioned in all standard text sections.\r\n\r\nRepository:   https:\/\/github.com\/seebi\/easychair.vim\r\nScreenshot:   https:\/\/github.com\/seebi\/easychair.vim\/raw\/master\/Screenshot.png\r\n","4":"The definition is based on markdown so markdown (and html) syntax is mentioned in all standard text sections.\r\n\r\nRepository:   https:\/\/github.com\/seebi\/easychair.vim\r\nScreenshot:   https:\/\/github.com\/seebi\/easychair.vim\/raw\/master\/Screenshot.png\r\n","install_details":"","5":"","first_name":"Sebastian","6":"Sebastian","last_name":"Tramp","7":"Tramp","releases":[{"0":"3727","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"easychair-1.0.tar.gz","4":"easychair-1.0.tar.gz","src_id":"16452","5":"16452","creation_date":"1315137581","6":"1315137581"}]},"3726":{"script_id":"3726","0":"3726","script_name":"mcabberlog.vim","1":"mcabberlog.vim","script_type":"syntax","2":"syntax","summary":"Watch your mcabber logs in vim","3":"Watch your mcabber logs in vim","description":"This script provides Highlighting for mcabber Logfiles.","4":"This script provides Highlighting for mcabber Logfiles.","install_details":"Either copy the file to your \"syntax\" folder or use a package manager (git repo is available here: https:\/\/github.com\/thomasba\/mcabberlog.vim )","5":"Either copy the file to your \"syntax\" folder or use a package manager (git repo is available here: https:\/\/github.com\/thomasba\/mcabberlog.vim )","first_name":"Thomas","6":"Thomas","last_name":"Ba","7":"Ba","releases":[{"0":"3726","vim_version":"7.0","1":"7.0","script_version":"0.7","2":"0.7","version_comment":"\u00e2\u0080\u00a2 Support for PMs in MUC","3":"\u00e2\u0080\u00a2 Support for PMs in MUC","package":"mcabberlog.vim","4":"mcabberlog.vim","src_id":"24817","5":"24817","creation_date":"1482528658","6":"1482528658"},{"0":"3726","vim_version":"7.0","1":"7.0","script_version":"0.6","2":"0.6","version_comment":"\u00e2\u0080\u00a2 Moved keyword configuration for highlighting into vimrc\r\n  → e.g.: let g:mcabber_mention='thomasba'\r\n\u00e2\u0080\u00a2 Highlight hidden messages from github.com\/hackyourlife\/lima-gold ","3":"\u00e2\u0080\u00a2 Moved keyword configuration for highlighting into vimrc\r\n  → e.g.: let g:mcabber_mention='thomasba'\r\n\u00e2\u0080\u00a2 Highlight hidden messages from github.com\/hackyourlife\/lima-gold ","package":"mcabberlog.vim","4":"mcabberlog.vim","src_id":"24766","5":"24766","creation_date":"1480264820","6":"1480264820"},{"0":"3726","vim_version":"7.0","1":"7.0","script_version":"0.5","2":"0.5","version_comment":"\u00e2\u0080\u00a2 Handle Status changes","3":"\u00e2\u0080\u00a2 Handle Status changes","package":"mcabberlog.vim","4":"mcabberlog.vim","src_id":"16468","5":"16468","creation_date":"1315244339","6":"1315244339"},{"0":"3726","vim_version":"7.0","1":"7.0","script_version":"0.4","2":"0.4","version_comment":"\u00e2\u0080\u00a2 Fixed: show own kicks\/bans correct\r\n\u00e2\u0080\u00a2 Fixed: Handling for kicks\/bans + reason","3":"\u00e2\u0080\u00a2 Fixed: show own kicks\/bans correct\r\n\u00e2\u0080\u00a2 Fixed: Handling for kicks\/bans + reason","package":"mcabberlog.vim","4":"mcabberlog.vim","src_id":"16466","5":"16466","creation_date":"1315221423","6":"1315221423"},{"0":"3726","vim_version":"7.0","1":"7.0","script_version":"0.3","2":"0.3","version_comment":"Initial upload","3":"Initial upload","package":"mcabberlog.vim","4":"mcabberlog.vim","src_id":"16446","5":"16446","creation_date":"1315073175","6":"1315073175"}]},"3724":{"script_id":"3724","0":"3724","script_name":"indent-motion","1":"indent-motion","script_type":"patch","2":"patch","summary":"Vim motions to the start and end of the current indentation-delimited block","3":"Vim motions to the start and end of the current indentation-delimited block","description":"indent-motion is a Vim plugin which maps `<Leader>[` and `<Leader>]` in normal, visual, and operator-pending modes to move to the beginning and end (respectively) of your current indentation-delimited block (`<Leader>` refers to your current user-defined \"mapleader\", which is `\\` by default).\r\n\r\nFor example (using JavaScript):\r\n\r\n    function foo(a, b, c) {\r\n        var x = 1;\r\n        var y = 2;\r\n        if (x == y) {\r\n            alert(\"This will never happen!\");\r\n            ++y;\r\n        }\r\n    }\r\n\r\nIn the above snippet, if the cursor is positioned on the `var x = 1;` line, then `<Leader>]` will move the cursor to the next-to-last line (closing brace of the conditional block) and `<Leader>[` will move it back to the original location. If the cursor is positioned on the `alert` call, then `<Leader>]` will move down 1 line to `++y;`.\r\n\r\nIf one of the mappings is executed on an empty line (containing no characters, not even whitespace), then the assumed indentation will be that of the next non-empty line, where \"next\" is in the direction of the requested motion.\r\n\r\nCurrently, the mappings are not configurable, but this can easily be changed upon request.","4":"indent-motion is a Vim plugin which maps `<Leader>[` and `<Leader>]` in normal, visual, and operator-pending modes to move to the beginning and end (respectively) of your current indentation-delimited block (`<Leader>` refers to your current user-defined \"mapleader\", which is `\\` by default).\r\n\r\nFor example (using JavaScript):\r\n\r\n    function foo(a, b, c) {\r\n        var x = 1;\r\n        var y = 2;\r\n        if (x == y) {\r\n            alert(\"This will never happen!\");\r\n            ++y;\r\n        }\r\n    }\r\n\r\nIn the above snippet, if the cursor is positioned on the `var x = 1;` line, then `<Leader>]` will move the cursor to the next-to-last line (closing brace of the conditional block) and `<Leader>[` will move it back to the original location. If the cursor is positioned on the `alert` call, then `<Leader>]` will move down 1 line to `++y;`.\r\n\r\nIf one of the mappings is executed on an empty line (containing no characters, not even whitespace), then the assumed indentation will be that of the next non-empty line, where \"next\" is in the direction of the requested motion.\r\n\r\nCurrently, the mappings are not configurable, but this can easily be changed upon request.","install_details":"Clone my Github repo (see https:\/\/github.com\/tmhedberg\/indent-motion) if you use Pathogen and Git to manage your plugins, or just download the file and drop it into your ~\/.vim\/plugin directory.","5":"Clone my Github repo (see https:\/\/github.com\/tmhedberg\/indent-motion) if you use Pathogen and Git to manage your plugins, or just download the file and drop it into your ~\/.vim\/plugin directory.","first_name":"Taylor","6":"Taylor","last_name":"Hedberg","7":"Hedberg","releases":[{"0":"3724","vim_version":"7.0","1":"7.0","script_version":"1.0.1","2":"1.0.1","version_comment":"Initial upload","3":"Initial upload","package":"indent-motion.vim","4":"indent-motion.vim","src_id":"16440","5":"16440","creation_date":"1315033281","6":"1315033281"}]},"3723":{"script_id":"3723","0":"3723","script_name":"SimpylFold","1":"SimpylFold","script_type":"ftplugin","2":"ftplugin","summary":"No-BS Python code folding","3":"No-BS Python code folding","description":"Because of its reliance on significant whitespace rather than explicit block delimiters, properly folding Python code can be tricky. The Python syntax definition that comes bundled with Vim doesn't contain any fold directives at all, and the simplest workaround is to `:set foldmethod=indent`, which usually ends up folding a lot more than you really want it to.\r\n\r\nThere's no shortage of Vim plugins for improved Python folding, but most seem to suffer from cobbled-together algorithms with bizarre, intractable bugs in the corner cases. SimpylFold aims to be exactly what its name suggests: simple, correct folding for Python. It's nothing more than it needs to be: it properly folds class and function\/method definitions, and leaves your loops and conditional blocks untouched. There's no BS involved: no screwing around with unrelated options (which several of the other plugins do), no choice of algorithms to scratch your head over (because there's only one that's correct); it just works, simply.","4":"Because of its reliance on significant whitespace rather than explicit block delimiters, properly folding Python code can be tricky. The Python syntax definition that comes bundled with Vim doesn't contain any fold directives at all, and the simplest workaround is to `:set foldmethod=indent`, which usually ends up folding a lot more than you really want it to.\r\n\r\nThere's no shortage of Vim plugins for improved Python folding, but most seem to suffer from cobbled-together algorithms with bizarre, intractable bugs in the corner cases. SimpylFold aims to be exactly what its name suggests: simple, correct folding for Python. It's nothing more than it needs to be: it properly folds class and function\/method definitions, and leaves your loops and conditional blocks untouched. There's no BS involved: no screwing around with unrelated options (which several of the other plugins do), no choice of algorithms to scratch your head over (because there's only one that's correct); it just works, simply.","install_details":"If you use Pathogen and Git to manage your Vim plugins (highly recommended), just clone my Github repo (see https:\/\/github.com\/tmhedberg\/SimpylFold) into your ~\/.vim\/bundle directory as a submodule. Otherwise, unzip the archive and drop the contained directories into your ~\/.vim directory.","5":"If you use Pathogen and Git to manage your Vim plugins (highly recommended), just clone my Github repo (see https:\/\/github.com\/tmhedberg\/SimpylFold) into your ~\/.vim\/bundle directory as a submodule. Otherwise, unzip the archive and drop the contained directories into your ~\/.vim directory.","first_name":"Taylor","6":"Taylor","last_name":"Hedberg","7":"Hedberg","releases":[{"0":"3723","vim_version":"7.0","1":"7.0","script_version":"1.1","2":"1.1","version_comment":"    - Performance improvements (up to 3-4x faster in large buffers)\r\n    - Option to display first line of folded docstring in fold text\r\n    - Help file\r\n    - Numerous bug fixes\r\n    - BSD license","3":"    - Performance improvements (up to 3-4x faster in large buffers)\r\n    - Option to display first line of folded docstring in fold text\r\n    - Help file\r\n    - Numerous bug fixes\r\n    - BSD license","package":"SimpylFold.zip","4":"SimpylFold.zip","src_id":"17576","5":"17576","creation_date":"1331270229","6":"1331270229"},{"0":"3723","vim_version":"7.0","1":"7.0","script_version":"1.0.2","2":"1.0.2","version_comment":"Fixed infinite loop bug trigged when the first line of the buffer is indented.","3":"Fixed infinite loop bug trigged when the first line of the buffer is indented.","package":"SimpylFold.vim","4":"SimpylFold.vim","src_id":"17083","5":"17083","creation_date":"1324171812","6":"1324171812"},{"0":"3723","vim_version":"7.0","1":"7.0","script_version":"1.0.1","2":"1.0.1","version_comment":"Old version was uploaded incorrectly.\r\n\r\nAlso fixed folding of functions and classes with mutli-line signatures.","3":"Old version was uploaded incorrectly.\r\n\r\nAlso fixed folding of functions and classes with mutli-line signatures.","package":"SimpylFold.vim","4":"SimpylFold.vim","src_id":"16639","5":"16639","creation_date":"1318099954","6":"1318099954"},{"0":"3723","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"SimpylFold.vim","4":"SimpylFold.vim","src_id":"16439","5":"16439","creation_date":"1315032949","6":"1315032949"}]},"3722":{"script_id":"3722","0":"3722","script_name":"quickfixstatus.vim","1":"quickfixstatus.vim","script_type":"utility","2":"utility","summary":"show quickfix errors\/warnings as you move through the file","3":"show quickfix errors\/warnings as you move through the file","description":"Using Vim's quickfix windows, or location lists usually involves opening them in a separate window, and using :cnext or its equivalents to page through the messages.\r\n\r\nThis plugin shows checks whether the current line in a buffer is in its local location list, the global quickfix list, or the Syntastic vimscript#2736 plugin's list of syntax errors. If it is, it displays the connected error message at the bottom of the screen, where command line messages are displayed. (Technically, this isn't Vim's status line, it's the command line buffer, but it's certainly where status messages often appear.)\r\n\r\nCommands:\r\n\r\n:QuickfixStatusEnable -- turns on the feature globally\r\n\r\n:QuickfixStatusDisable -- turns off the feature globally\r\n\r\nPlease file any bugs at https:\/\/github.com\/dannyob\/quickfixstatus\/issues\r\n","4":"Using Vim's quickfix windows, or location lists usually involves opening them in a separate window, and using :cnext or its equivalents to page through the messages.\r\n\r\nThis plugin shows checks whether the current line in a buffer is in its local location list, the global quickfix list, or the Syntastic vimscript#2736 plugin's list of syntax errors. If it is, it displays the connected error message at the bottom of the screen, where command line messages are displayed. (Technically, this isn't Vim's status line, it's the command line buffer, but it's certainly where status messages often appear.)\r\n\r\nCommands:\r\n\r\n:QuickfixStatusEnable -- turns on the feature globally\r\n\r\n:QuickfixStatusDisable -- turns off the feature globally\r\n\r\nPlease file any bugs at https:\/\/github.com\/dannyob\/quickfixstatus\/issues\r\n","install_details":"Drop this file into your plugin folder, use pathogen with https:\/\/github.com\/dannyob\/quickfixstatus or use vundle to BundleInstall quickfixstatus","5":"Drop this file into your plugin folder, use pathogen with https:\/\/github.com\/dannyob\/quickfixstatus or use vundle to BundleInstall quickfixstatus","first_name":"danny","6":"danny","last_name":"obrien","7":"obrien","releases":[{"0":"3722","vim_version":"7.0","1":"7.0","script_version":"1.01","2":"1.01","version_comment":"Ensures that output doesn't trigger a \"Hit ENTER\" message","3":"Ensures that output doesn't trigger a \"Hit ENTER\" message","package":"quickfixstatus.vim","4":"quickfixstatus.vim","src_id":"16438","5":"16438","creation_date":"1315031431","6":"1315031431"},{"0":"3722","vim_version":"7.0","1":"7.0","script_version":"1.00","2":"1.00","version_comment":"Initial upload","3":"Initial upload","package":"quickfixstatus.vim","4":"quickfixstatus.vim","src_id":"16436","5":"16436","creation_date":"1315016272","6":"1315016272"}]},"3721":{"script_id":"3721","0":"3721","script_name":"Threesome","1":"Threesome","script_type":"utility","2":"utility","summary":"A plugin for resolving conflicts during three-way merges.","3":"A plugin for resolving conflicts during three-way merges.","description":"Threesome is now called Splice!  This page is now deprecated -- go to the new one.\r\n\r\nhttp:\/\/www.vim.org\/scripts\/script.php?script_id=4026","4":"Threesome is now called Splice!  This page is now deprecated -- go to the new one.\r\n\r\nhttp:\/\/www.vim.org\/scripts\/script.php?script_id=4026","install_details":"","5":"","first_name":"Steve","6":"Steve","last_name":"Losh","7":"Losh","releases":[{"0":"3721","vim_version":"7.3","1":"7.3","script_version":"0.2.0","2":"0.2.0","version_comment":"Initial upload","3":"Initial upload","package":"threesome.zip","4":"threesome.zip","src_id":"16435","5":"16435","creation_date":"1314995262","6":"1314995262"}]},"3720":{"script_id":"3720","0":"3720","script_name":"noweboutline.vim","1":"noweboutline.vim","script_type":"utility","2":"utility","summary":"a noweb file out line tool","3":"a noweb file out line tool","description":"Literate programming tool for *.nw file\r\nchange log:\r\nver. 0.1:\r\nopen an outline window, show code chunk list, press enter to jump to corresonding code chunk\r\nver. 0.13\r\nmap <C-F1> to open document outline window","4":"Literate programming tool for *.nw file\r\nchange log:\r\nver. 0.1:\r\nopen an outline window, show code chunk list, press enter to jump to corresonding code chunk\r\nver. 0.13\r\nmap <C-F1> to open document outline window","install_details":"ver 0.13 usage\r\n:source [downloaded-path]noweboutline.vim while opening a *.nw file","5":"ver 0.13 usage\r\n:source [downloaded-path]noweboutline.vim while opening a *.nw file","first_name":"yangkun","6":"yangkun","last_name":"huang","7":"huang","releases":[{"0":"3720","vim_version":"7.0","1":"7.0","script_version":"0.15","2":"0.15","version_comment":"new feature:\r\n1) In outline window, use C+d to show latex style document struct(from section to subsubparagraph)\r\n2) In outline window, use C+c to show all defined code chunks\r\n3) In outline window, use C+a to show mixed (document structure + code chunks) list","3":"new feature:\r\n1) In outline window, use C+d to show latex style document struct(from section to subsubparagraph)\r\n2) In outline window, use C+c to show all defined code chunks\r\n3) In outline window, use C+a to show mixed (document structure + code chunks) list","package":"noweboutline.vim","4":"noweboutline.vim","src_id":"19061","5":"19061","creation_date":"1354159181","6":"1354159181"},{"0":"3720","vim_version":"7.0","1":"7.0","script_version":"0.14","2":"0.14","version_comment":"<C+n> in insert mode to auto complete a chunk name","3":"<C+n> in insert mode to auto complete a chunk name","package":"noweboutline.vim","4":"noweboutline.vim","src_id":"18282","5":"18282","creation_date":"1342595469","6":"1342595469"},{"0":"3720","vim_version":"7.0","1":"7.0","script_version":"0.14","2":"0.14","version_comment":"press <C-n> to autocomplete chunk's name","3":"press <C-n> to autocomplete chunk's name","package":"noweboutline.vim","4":"noweboutline.vim","src_id":"16777","5":"16777","creation_date":"1320112440","6":"1320112440"},{"0":"3720","vim_version":"7.0","1":"7.0","script_version":"0.13","2":"0.13","version_comment":"add feature: press <C-F1> to open the document outline window","3":"add feature: press <C-F1> to open the document outline window","package":"noweboutline.vim","4":"noweboutline.vim","src_id":"16437","5":"16437","creation_date":"1315019104","6":"1315019104"},{"0":"3720","vim_version":"7.0","1":"7.0","script_version":"0.12","2":"0.12","version_comment":"add feature: indention for document structure","3":"add feature: indention for document structure","package":"noweboutline.vim","4":"noweboutline.vim","src_id":"16424","5":"16424","creation_date":"1314866139","6":"1314866139"},{"0":"3720","vim_version":"7.0","1":"7.0","script_version":"0.11","2":"0.11","version_comment":"bug fixed: press enter, can not jump to corresponding chunk\r\nadd feature: show & jump latex document section also","3":"bug fixed: press enter, can not jump to corresponding chunk\r\nadd feature: show & jump latex document section also","package":"noweboutline.vim","4":"noweboutline.vim","src_id":"16422","5":"16422","creation_date":"1314860127","6":"1314860127"}]},"3719":{"script_id":"3719","0":"3719","script_name":"diffwindow_movement","1":"diffwindow_movement","script_type":"utility","2":"utility","summary":"Movement over changes in a diff window. ","3":"Movement over changes in a diff window. ","description":"DESCRIPTION\r\nThis plugin provides movement commands and text objects for windows in diff\r\nmode.\r\n\r\nUSAGE\r\n]C                      Go to [count] next end of a change.\r\n[C                      Go to [count] previous end of a change.\r\n                        These complement the built-in ]c [c commands.\r\n\r\nic                      \"inner change\" text object; in a diff window, select\r\n                        [count] changes.\r\nid                      \"inner difference\" text object; difference is more\r\n                        fine-granular than diff changes; in a diff window,\r\n                        select a range of lines that have the same\r\n                        DiffAdd\/DiffChange\/DiffDelete highlighting.","4":"DESCRIPTION\r\nThis plugin provides movement commands and text objects for windows in diff\r\nmode.\r\n\r\nUSAGE\r\n]C                      Go to [count] next end of a change.\r\n[C                      Go to [count] previous end of a change.\r\n                        These complement the built-in ]c [c commands.\r\n\r\nic                      \"inner change\" text object; in a diff window, select\r\n                        [count] changes.\r\nid                      \"inner difference\" text object; difference is more\r\n                        fine-granular than diff changes; in a diff window,\r\n                        select a range of lines that have the same\r\n                        DiffAdd\/DiffChange\/DiffDelete highlighting.","install_details":"INSTALLATION\r\nThis script is packaged as a vimball. If you have the \"gunzip\" decompressor\r\nin your PATH, simply edit the *.vmb.gz package in Vim; otherwise, decompress\r\nthe archive first, e.g. using WinZip. Inside Vim, install by sourcing the\r\nvimball or via the :UseVimball command.\r\n    vim diffwindow_movement*.vmb.gz\r\n    :so %\r\nTo uninstall, use the :RmVimball command.\r\n\r\nDEPENDENCIES\r\n- Requires Vim 7.0 or higher.\r\n- Requires the CountJump plugin (vimscript #3130), version 1.50 or higher.\r\n\r\nCONFIGURATION\r\nFor a permanent configuration, put the following commands into your vimrc:\r\n\r\nTo change the default motion mapping, use:\r\n    let g:diffwindow_movement_EndMapping = 'C'\r\nTo also change the [ \/ ] prefix to something else, follow the instructions for\r\nCountJump-remap-motions.\r\n\r\nTo change the default text object mappings, use:\r\n    let g:diffwindow_movement_ChangeTextObject = 'c'\r\n    let g:diffwindow_movement_DifferenceTextObject = 'd'\r\nTo also change the i prefix to something else, follow the instructions for\r\nCountJump-remap-text-objects.","5":"INSTALLATION\r\nThis script is packaged as a vimball. If you have the \"gunzip\" decompressor\r\nin your PATH, simply edit the *.vmb.gz package in Vim; otherwise, decompress\r\nthe archive first, e.g. using WinZip. Inside Vim, install by sourcing the\r\nvimball or via the :UseVimball command.\r\n    vim diffwindow_movement*.vmb.gz\r\n    :so %\r\nTo uninstall, use the :RmVimball command.\r\n\r\nDEPENDENCIES\r\n- Requires Vim 7.0 or higher.\r\n- Requires the CountJump plugin (vimscript #3130), version 1.50 or higher.\r\n\r\nCONFIGURATION\r\nFor a permanent configuration, put the following commands into your vimrc:\r\n\r\nTo change the default motion mapping, use:\r\n    let g:diffwindow_movement_EndMapping = 'C'\r\nTo also change the [ \/ ] prefix to something else, follow the instructions for\r\nCountJump-remap-motions.\r\n\r\nTo change the default text object mappings, use:\r\n    let g:diffwindow_movement_ChangeTextObject = 'c'\r\n    let g:diffwindow_movement_DifferenceTextObject = 'd'\r\nTo also change the i prefix to something else, follow the instructions for\r\nCountJump-remap-text-objects.","first_name":"Ingo","6":"Ingo","last_name":"Karkat","7":"Karkat","releases":[{"0":"3719","vim_version":"7.0","1":"7.0","script_version":"1.02","2":"1.02","version_comment":"- Allow to reconfigure the mappings for the motion and text objects. Thanks to Enno Nagel for suggesting this.","3":"- Allow to reconfigure the mappings for the motion and text objects. Thanks to Enno Nagel for suggesting this.","package":"diffwindow_movement-1.02.vmb.gz","4":"diffwindow_movement-1.02.vmb.gz","src_id":"22232","5":"22232","creation_date":"1406020200","6":"1406020200"},{"0":"3719","vim_version":"7.0","1":"7.0","script_version":"1.01","2":"1.01","version_comment":"FIX: Vim 7.0\/1 need preloading of functions referenced in Funcrefs.","3":"FIX: Vim 7.0\/1 need preloading of functions referenced in Funcrefs.","package":"diffwindow_movement.vba.gz","4":"diffwindow_movement.vba.gz","src_id":"17555","5":"17555","creation_date":"1330698679","6":"1330698679"},{"0":"3719","vim_version":"7.0","1":"7.0","script_version":"1.00","2":"1.00","version_comment":"Initial upload","3":"Initial upload","package":"diffwindow_movement.vba.gz","4":"diffwindow_movement.vba.gz","src_id":"16408","5":"16408","creation_date":"1314775392","6":"1314775392"}]},"3718":{"script_id":"3718","0":"3718","script_name":"melt-syntax","1":"melt-syntax","script_type":"syntax","2":"syntax","summary":"MELT Syntax","3":"MELT Syntax","description":"This script is mainly a syntax file (found in syntax\/melt.vim) completed with a few coding styles rules (ftplugin\/melt.vim).\r\nYou can found more about MELT here: http:\/\/gcc-melt.org\/\r\nOne of the good point is that it handles C code written in a code_chunk.\r\n\r\nRelease under GPLV3 or higher\r\n\r\n\r\nAuthor is Pierre Vittet (http:\/\/pvittet.com).\r\n","4":"This script is mainly a syntax file (found in syntax\/melt.vim) completed with a few coding styles rules (ftplugin\/melt.vim).\r\nYou can found more about MELT here: http:\/\/gcc-melt.org\/\r\nOne of the good point is that it handles C code written in a code_chunk.\r\n\r\nRelease under GPLV3 or higher\r\n\r\n\r\nAuthor is Pierre Vittet (http:\/\/pvittet.com).\r\n","install_details":"You just need to untar the archive into our vim directory to use to use it.","5":"You just need to untar the archive into our vim directory to use to use it.","first_name":"Pierre ","6":"Pierre ","last_name":"Vittet","7":"Vittet","releases":[{"0":"3718","vim_version":"7.3","1":"7.3","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"melt-syntax.tar.gz","4":"melt-syntax.tar.gz","src_id":"16403","5":"16403","creation_date":"1314709887","6":"1314709887"}]},"3717":{"script_id":"3717","0":"3717","script_name":"SnippetySnip","1":"SnippetySnip","script_type":"utility","2":"utility","summary":"Inserts named snippets from various other files into a file","3":"Inserts named snippets from various other files into a file","description":"SnippetySnip is a vim tool for automatically inserting parts (snippets) of other files in a file. I wrote it to insert sourcecode examples from source files into html blog-posts, but it can be used for all sorts of text files.\r\n\r\nIn the source file, you mark up a region of text (a snippet) and give it a name. In the target file, you mark where you want this particular snippet inserted. \r\n\r\nFor instance:\r\n\r\nsource.py:\r\n    (...)\r\n    #snippetysnip_begin:foo\r\n    def foo():\r\n        return 0\r\n    #snippetysnip_end\r\n    (...)\r\n\r\ntarget.html:\r\n    <p><code>\r\n    <!-- snippetysnip:\/path\/to\/source.py:foo -->\r\n    <\/code><\/p>\r\n\r\nWhen SnippetySnip is run, the function foo() from source.py is inserted into the html file, which then looks like this:\r\n\r\ntarget.html:\r\n    <p><code>\r\n    <!-- snippetysnip:\/path\/to\/source.py:foo -->\r\n    def foo():\r\n        return 0\r\n    <!-- snippetysnip_end:\/path\/to\/source.py:foo -->\r\n    <\/code><\/p>\r\n\r\n\r\nSnippetySnip does not care about the format of the comments in your particular language, it only looks for the snippetysnip-strings. A snippet name can consist of letters, numbers or any of the characters \"-_.\".\r\n\r\nYou can have many snippets in a source file, and a target file can reference multiple snippets from multiple sources.\r\n\r\nPaths can be relative or absolute.\r\n\r\n\r\n\r\nHOW TO USE\r\nIn the source files, surround each snippet with snippetysnip_begin:SNIPPET_NAME and snippetysnip_end. These tags need to be on separate lines, but except from that, they can be inside the comment style of your choice, depending on the host language. See the example above.\r\nIn the target file, put on a separate line snippetysnipp:FILE_NAME:SNIPPET_NAME\r\nPaths can be relative or absolute. See the example above, or python\/SnippetySnip\/integration_tests\/ for a more extensive one.\r\nTo run SnippetySnip and insert all your snippets, do \":call SnippetySnip()\" without the quotes. It is suggested you make a map to make this easier, see INSTALLATION\r\nIt can be tedious to type the snippet inclusion strings in the target file. To get this string automatically, go to your source file, place the cursor inside the snippet you want the inclusion string for and do \":call SnippetySnipPrintCurrentSnippetString()\" without the quotes. It will print the string for you (with html comments). It is suggested you make a map to make this easier, see INSTALLATION.\r\nAbout cursor position: Since the entire buffer is replaced, it is impossible to exactly remember the cursor position. SnippetySnip does however make a best effort, and puts the cursor back at the same line and column.\r\n\r\n\r\n\r\nINSTALLATION\r\nDownload SnippetySnip-<version>.tgz into your vim directory (usually ~\/.vim on Linux systems) and do\r\ntar zxf SnippetySnip-<version>.tgz\r\n\r\nTo make SnippetySnip easier to use, I suggest you set up a mapping in ~\/.vimrc. These should do nicely:\r\nmap <Leader>s :call SnippetySnip()<CR> \"Type <Leader>s to run SnippetySnip\r\nmap <C-s> :call SnippetySnip()<CR> \"Press Ctrl+s to run SnippetySnip\r\nmap <Leader>S :call SnippetySnipPrintCurrentSnippetString()<CR> \"Type <Leader>S to print the name of the current snippet\r\n\r\n\r\n\r\nADVANCED USAGE\r\nIt is possible to give arguments before=\"...\" and\/or after=\"...\" when including a snippet. These arguments will be inserted between the snippet command and the actual snippet. Here is an example, inserting code snippets into Wordpress posts:\r\n\r\noriginal target:\r\n    <!-- snippetysnip:source.cpp:foo:(before='[sourcecode language=\"cpp\"]', after='[\/sourcecode]') -->\r\n\r\nmodified target:\r\n    <!-- snippetysnip:source.cpp:foo:(before='[sourcecode language=\"cpp\"]', after='[\/sourcecode]') -->\r\n    [sourcecode language=\"cpp\"]\r\n    imported();\r\n    code();\r\n    here();\r\n    [\/sourcecode]\r\n    <!-- snippetysnip_end:source.cpp:foo -->\r\n\r\n(This was motivated by the fact that html-comments do not work well inside [sourcecode] blocks on Wordpress)\r\n\r\nIf you want SnippetySnipPrintCurrentSnippetString() to include arguments, define g:SnippetySnipArguments. For instance, you can put this line in ~\/.vimrc:\r\nlet g:SnippetySnipArguments = \"(before='[sourcecode language=\\\"cpp\\\"]', after='}[\/sourcecode]')\"\r\n\r\nSnippetySnip is also available on github: https:\/\/github.com\/knatten\/SnippetySnip\r\n","4":"SnippetySnip is a vim tool for automatically inserting parts (snippets) of other files in a file. I wrote it to insert sourcecode examples from source files into html blog-posts, but it can be used for all sorts of text files.\r\n\r\nIn the source file, you mark up a region of text (a snippet) and give it a name. In the target file, you mark where you want this particular snippet inserted. \r\n\r\nFor instance:\r\n\r\nsource.py:\r\n    (...)\r\n    #snippetysnip_begin:foo\r\n    def foo():\r\n        return 0\r\n    #snippetysnip_end\r\n    (...)\r\n\r\ntarget.html:\r\n    <p><code>\r\n    <!-- snippetysnip:\/path\/to\/source.py:foo -->\r\n    <\/code><\/p>\r\n\r\nWhen SnippetySnip is run, the function foo() from source.py is inserted into the html file, which then looks like this:\r\n\r\ntarget.html:\r\n    <p><code>\r\n    <!-- snippetysnip:\/path\/to\/source.py:foo -->\r\n    def foo():\r\n        return 0\r\n    <!-- snippetysnip_end:\/path\/to\/source.py:foo -->\r\n    <\/code><\/p>\r\n\r\n\r\nSnippetySnip does not care about the format of the comments in your particular language, it only looks for the snippetysnip-strings. A snippet name can consist of letters, numbers or any of the characters \"-_.\".\r\n\r\nYou can have many snippets in a source file, and a target file can reference multiple snippets from multiple sources.\r\n\r\nPaths can be relative or absolute.\r\n\r\n\r\n\r\nHOW TO USE\r\nIn the source files, surround each snippet with snippetysnip_begin:SNIPPET_NAME and snippetysnip_end. These tags need to be on separate lines, but except from that, they can be inside the comment style of your choice, depending on the host language. See the example above.\r\nIn the target file, put on a separate line snippetysnipp:FILE_NAME:SNIPPET_NAME\r\nPaths can be relative or absolute. See the example above, or python\/SnippetySnip\/integration_tests\/ for a more extensive one.\r\nTo run SnippetySnip and insert all your snippets, do \":call SnippetySnip()\" without the quotes. It is suggested you make a map to make this easier, see INSTALLATION\r\nIt can be tedious to type the snippet inclusion strings in the target file. To get this string automatically, go to your source file, place the cursor inside the snippet you want the inclusion string for and do \":call SnippetySnipPrintCurrentSnippetString()\" without the quotes. It will print the string for you (with html comments). It is suggested you make a map to make this easier, see INSTALLATION.\r\nAbout cursor position: Since the entire buffer is replaced, it is impossible to exactly remember the cursor position. SnippetySnip does however make a best effort, and puts the cursor back at the same line and column.\r\n\r\n\r\n\r\nINSTALLATION\r\nDownload SnippetySnip-<version>.tgz into your vim directory (usually ~\/.vim on Linux systems) and do\r\ntar zxf SnippetySnip-<version>.tgz\r\n\r\nTo make SnippetySnip easier to use, I suggest you set up a mapping in ~\/.vimrc. These should do nicely:\r\nmap <Leader>s :call SnippetySnip()<CR> \"Type <Leader>s to run SnippetySnip\r\nmap <C-s> :call SnippetySnip()<CR> \"Press Ctrl+s to run SnippetySnip\r\nmap <Leader>S :call SnippetySnipPrintCurrentSnippetString()<CR> \"Type <Leader>S to print the name of the current snippet\r\n\r\n\r\n\r\nADVANCED USAGE\r\nIt is possible to give arguments before=\"...\" and\/or after=\"...\" when including a snippet. These arguments will be inserted between the snippet command and the actual snippet. Here is an example, inserting code snippets into Wordpress posts:\r\n\r\noriginal target:\r\n    <!-- snippetysnip:source.cpp:foo:(before='[sourcecode language=\"cpp\"]', after='[\/sourcecode]') -->\r\n\r\nmodified target:\r\n    <!-- snippetysnip:source.cpp:foo:(before='[sourcecode language=\"cpp\"]', after='[\/sourcecode]') -->\r\n    [sourcecode language=\"cpp\"]\r\n    imported();\r\n    code();\r\n    here();\r\n    [\/sourcecode]\r\n    <!-- snippetysnip_end:source.cpp:foo -->\r\n\r\n(This was motivated by the fact that html-comments do not work well inside [sourcecode] blocks on Wordpress)\r\n\r\nIf you want SnippetySnipPrintCurrentSnippetString() to include arguments, define g:SnippetySnipArguments. For instance, you can put this line in ~\/.vimrc:\r\nlet g:SnippetySnipArguments = \"(before='[sourcecode language=\\\"cpp\\\"]', after='}[\/sourcecode]')\"\r\n\r\nSnippetySnip is also available on github: https:\/\/github.com\/knatten\/SnippetySnip\r\n","install_details":"INSTALLATION\r\nDownload SnippetySnip-<version>.tgz into your vim directory (usually ~\/.vim on Linux systems) and do\r\ntar zxf SnippetySnip-<version>.tgz\r\n\r\nTo make SnippetySnip easier to use, I suggest you set up a mapping in ~\/.vimrc. These should do nicely:\r\nmap <Leader>s :call SnippetySnip()<CR> \"Type <Leader>s to run SnippetySnip\r\nmap <C-s> :call SnippetySnip()<CR> \"Press Ctrl+s to run SnippetySnip\r\nmap <Leader>S :call SnippetySnipPrintCurrentSnippetString()<CR> \"Type <Leader>S to print the name of the current snippet","5":"INSTALLATION\r\nDownload SnippetySnip-<version>.tgz into your vim directory (usually ~\/.vim on Linux systems) and do\r\ntar zxf SnippetySnip-<version>.tgz\r\n\r\nTo make SnippetySnip easier to use, I suggest you set up a mapping in ~\/.vimrc. These should do nicely:\r\nmap <Leader>s :call SnippetySnip()<CR> \"Type <Leader>s to run SnippetySnip\r\nmap <C-s> :call SnippetySnip()<CR> \"Press Ctrl+s to run SnippetySnip\r\nmap <Leader>S :call SnippetySnipPrintCurrentSnippetString()<CR> \"Type <Leader>S to print the name of the current snippet","first_name":"Anders Schau","6":"Anders Schau","last_name":"Knatten","7":"Knatten","releases":[{"0":"3717","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"SnippetySnipPrintCurrentSnippetString() now prints the full path to the current file.\r\n\r\nSnippetySnip has been stable for a long while now, so bumped the version to 1.0.","3":"SnippetySnipPrintCurrentSnippetString() now prints the full path to the current file.\r\n\r\nSnippetySnip has been stable for a long while now, so bumped the version to 1.0.","package":"SnippetySnip-1.0.tgz","4":"SnippetySnip-1.0.tgz","src_id":"20919","5":"20919","creation_date":"1381661567","6":"1381661567"},{"0":"3717","vim_version":"7.0","1":"7.0","script_version":"0.6","2":"0.6","version_comment":"Fixed bug that would match a snippet named \"fooMoreChars\" when searching for snippet \"foo\"\r\nSnippet names are now restricted to the letters a-z\/A-Z, numbers, or any of the characters \"-_.\" (or if you prefer a regex: \/[0-9a-zA-Z\\-_\\.]+\/)","3":"Fixed bug that would match a snippet named \"fooMoreChars\" when searching for snippet \"foo\"\r\nSnippet names are now restricted to the letters a-z\/A-Z, numbers, or any of the characters \"-_.\" (or if you prefer a regex: \/[0-9a-zA-Z\\-_\\.]+\/)","package":"SnippetySnip-0.6.tgz","4":"SnippetySnip-0.6.tgz","src_id":"18826","5":"18826","creation_date":"1350502665","6":"1350502665"},{"0":"3717","vim_version":"7.0","1":"7.0","script_version":"0.5","2":"0.5","version_comment":"Add SnippetySnipPrintCurrentSnippetString() to print the inclusion string for the snippet currently under the cursor\r\nMake a best effort to preserve cursor position","3":"Add SnippetySnipPrintCurrentSnippetString() to print the inclusion string for the snippet currently under the cursor\r\nMake a best effort to preserve cursor position","package":"SnippetySnip-0.5.tgz","4":"SnippetySnip-0.5.tgz","src_id":"18163","5":"18163","creation_date":"1340133583","6":"1340133583"},{"0":"3717","vim_version":"7.0","1":"7.0","script_version":"0.4","2":"0.4","version_comment":"Put a line of whitespace at the beginning and end of each snippet for improved readability","3":"Put a line of whitespace at the beginning and end of each snippet for improved readability","package":"SnippetySnip-0.4.tgz","4":"SnippetySnip-0.4.tgz","src_id":"17844","5":"17844","creation_date":"1335869696","6":"1335869696"},{"0":"3717","vim_version":"7.0","1":"7.0","script_version":"0.3","2":"0.3","version_comment":"It is now possible to give arguments before=\"...\" and\/or after=\"...\" when including a snippet. These arguments will be inserted between the snippet command and the actual snippet.","3":"It is now possible to give arguments before=\"...\" and\/or after=\"...\" when including a snippet. These arguments will be inserted between the snippet command and the actual snippet.","package":"SnippetySnip-0.3.tgz","4":"SnippetySnip-0.3.tgz","src_id":"16743","5":"16743","creation_date":"1319632046","6":"1319632046"},{"0":"3717","vim_version":"7.0","1":"7.0","script_version":"0.2","2":"0.2","version_comment":"Improved README with suggestions for keymaps","3":"Improved README with suggestions for keymaps","package":"SnippetySnip-0.2.tgz","4":"SnippetySnip-0.2.tgz","src_id":"16412","5":"16412","creation_date":"1314806912","6":"1314806912"},{"0":"3717","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"SnippetySnip-0.1.tgz","4":"SnippetySnip-0.1.tgz","src_id":"16399","5":"16399","creation_date":"1314649622","6":"1314649622"}]},"3716":{"script_id":"3716","0":"3716","script_name":"fuzzee.vim","1":"fuzzee.vim","script_type":"utility","2":"utility","summary":"Fuzzy expansions for :e and :E","3":"Fuzzy expansions for :e and :E","description":"Fuzzee.vim will tab-complete paths relative to the current working directory in Vim and also the current buffer for use with `:e[dit]`, `:E[xplore]`, and many other splitting options. It also ignores files, directories, and filetypes listed in the user-defined `wildignore` setting. Finally, it's on-demand multi-directory globbing and has support for custom path mappings.\r\n\r\n:F itself opens up the explorer.\r\n\r\n:F .\/ will always refer to the current working directory.\r\n\r\n:F * will glob multiple directories from the current buffer.\r\n\r\n:F {arg} will search the buffer and current working directory for a fuzzy match of {arg}.\r\n\r\n:FB searches for any open or hidden buffers using the 'switchbuf' setting.\r\n\r\n:FuzzeeMap {cmap} {path} creates a custom 'cmap' per-directory to use in conjunction with the :F command.\r\n\r\nSupports splits, tabs, :lcd and :cd with fuzzy-arguments.\r\n\r\nRead the README for examples and tips on usage.\r\nSee the Github page for more details at https:\/\/github.com\/mattsa\/vim-fuzzee","4":"Fuzzee.vim will tab-complete paths relative to the current working directory in Vim and also the current buffer for use with `:e[dit]`, `:E[xplore]`, and many other splitting options. It also ignores files, directories, and filetypes listed in the user-defined `wildignore` setting. Finally, it's on-demand multi-directory globbing and has support for custom path mappings.\r\n\r\n:F itself opens up the explorer.\r\n\r\n:F .\/ will always refer to the current working directory.\r\n\r\n:F * will glob multiple directories from the current buffer.\r\n\r\n:F {arg} will search the buffer and current working directory for a fuzzy match of {arg}.\r\n\r\n:FB searches for any open or hidden buffers using the 'switchbuf' setting.\r\n\r\n:FuzzeeMap {cmap} {path} creates a custom 'cmap' per-directory to use in conjunction with the :F command.\r\n\r\nSupports splits, tabs, :lcd and :cd with fuzzy-arguments.\r\n\r\nRead the README for examples and tips on usage.\r\nSee the Github page for more details at https:\/\/github.com\/mattsa\/vim-fuzzee","install_details":"Install with vim-pathogen in your designated bundles folder.\r\n\r\nOr you can extract fuzzee.vim from plugins\/ and place it in your ~\/.vim\/plugins\/ directory with the others. Move the doc file into ~\/.vim\/doc\/ as well for helptags.","5":"Install with vim-pathogen in your designated bundles folder.\r\n\r\nOr you can extract fuzzee.vim from plugins\/ and place it in your ~\/.vim\/plugins\/ directory with the others. Move the doc file into ~\/.vim\/doc\/ as well for helptags.","first_name":"Matt","6":"Matt","last_name":"Sacks","7":"Sacks","releases":[{"0":"3716","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Add autoload\/fuzzee.vim for custom path mappings\r\nFix searching within a netrw buffer labeled as [Scratch]\r\n","3":"Add autoload\/fuzzee.vim for custom path mappings\r\nFix searching within a netrw buffer labeled as [Scratch]\r\n","package":"fuzzee.zip","4":"fuzzee.zip","src_id":"17504","5":"17504","creation_date":"1329774173","6":"1329774173"},{"0":"3716","vim_version":"7.0","1":"7.0","script_version":"0.5","2":"0.5","version_comment":"Add :FB command to navigate open or hidden buffers\r\nFixes when globbing for the home directory\r\nDefer an unnecessary glob","3":"Add :FB command to navigate open or hidden buffers\r\nFixes when globbing for the home directory\r\nDefer an unnecessary glob","package":"fuzzy.zip","4":"fuzzy.zip","src_id":"16635","5":"16635","creation_date":"1318038379","6":"1318038379"},{"0":"3716","vim_version":"7.0","1":"7.0","script_version":"0.4","2":"0.4","version_comment":"Fix issues when directories and files have spaces.\r\nAdd FL and FC for fuzzy lcd and cd.\r\nAdd optional multi-dir globbing.","3":"Fix issues when directories and files have spaces.\r\nAdd FL and FC for fuzzy lcd and cd.\r\nAdd optional multi-dir globbing.","package":"fuzzee.zip","4":"fuzzee.zip","src_id":"16427","5":"16427","creation_date":"1314878653","6":"1314878653"},{"0":"3716","vim_version":"7.0","1":"7.0","script_version":"0.2","2":"0.2","version_comment":"Prepend '.\/' to specify your local working directory for similarly named files.\r\nAdd support for :FS, :FV, and :FT to open splits, vsplits, and tabs.","3":"Prepend '.\/' to specify your local working directory for similarly named files.\r\nAdd support for :FS, :FV, and :FT to open splits, vsplits, and tabs.","package":"fuzzee.zip","4":"fuzzee.zip","src_id":"16400","5":"16400","creation_date":"1314665060","6":"1314665060"},{"0":"3716","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"fuzzee.zip","4":"fuzzee.zip","src_id":"16391","5":"16391","creation_date":"1314581386","6":"1314581386"}]},"3715":{"script_id":"3715","0":"3715","script_name":"numlist.vim","1":"numlist.vim","script_type":"utility","2":"utility","summary":"Add and remove id to a list items","3":"Add and remove id to a list items","description":"              Only two commands:  NumberedList  and  NoNumberedList\r\n              Just selected lines and call command.\r\n              Commands will guarantee the items with same indent.\r\n              If they are not so, they will be changed. \r\n              All rest items align with the first one.\r\n              \r\n                        Numbered from 1\r\n               line1       :NumberedList      1. line1 \r\n               line2                                       2. line2\r\n               line3                                       3. line3\r\n               line4                                       4. line4\r\n               line5                                       5. line5\r\n\r\n                        Numbered from 8\r\n               line1      :NumberedList 8     8.  line1 \r\n               line2                                        9.  line2\r\n               line3                                      10. line3\r\n               line4                                       11. line4\r\n               line5                                      12. line5\r\n\r\n                        Re numbered\r\n               1. line1     :NumberedList     1. line1 \r\n               2. line2                                    2. line2\r\n               5. line3                                    3. line3\r\n               7. line4                                    4. line4\r\n               8. line5                                    5. line5\r\n\r\n                       Guarantee the same indent\r\n             1. line1     :NumberedList       1. line1 \r\n               2. line2                                    2. line2\r\n               5. line3                                    3. line3\r\n               7. line4                                    4. line4\r\n               8. line5                                    5. line5\r\n\r\n                         Remove number\r\n               1. line1     :NoNumberedList   line1 \r\n               2. line2                                       line2\r\n               3. line3                                       line3\r\n               4. line4                                       line4\r\n               5. line5                                       line5\r\n\r\n                         Remove number\r\n               1  line1     :NoNumberedList   line1 \r\n               2  line2                                       line2\r\n               3  line3                                       line3\r\n               4  line4                                       line4\r\n               5  line5                                       line5\r\n\r\n                       Guarantee the same indent\r\n             1. line1     :NoNumberedList     line1 \r\n               2. line2                                       line2\r\n               3. line3                                       line3\r\n               4. line4                                       line4\r\n               5. line5                                       line5\r\n\r\n                       Just the same, no error\r\n               line1     :NoNumberedList      line1 \r\n               line2                                          line2\r\n               line3                                          line3\r\n               line4                                          line4\r\n               line5                                          line5\r\n\r\n                     Guarantee the same indent\r\n             line1     :NoNumberedList        line1 \r\n               line2                                          line2\r\n               line3                                          line3\r\n               line4                                          line4\r\n               line5                                          line5\r\n","4":"              Only two commands:  NumberedList  and  NoNumberedList\r\n              Just selected lines and call command.\r\n              Commands will guarantee the items with same indent.\r\n              If they are not so, they will be changed. \r\n              All rest items align with the first one.\r\n              \r\n                        Numbered from 1\r\n               line1       :NumberedList      1. line1 \r\n               line2                                       2. line2\r\n               line3                                       3. line3\r\n               line4                                       4. line4\r\n               line5                                       5. line5\r\n\r\n                        Numbered from 8\r\n               line1      :NumberedList 8     8.  line1 \r\n               line2                                        9.  line2\r\n               line3                                      10. line3\r\n               line4                                       11. line4\r\n               line5                                      12. line5\r\n\r\n                        Re numbered\r\n               1. line1     :NumberedList     1. line1 \r\n               2. line2                                    2. line2\r\n               5. line3                                    3. line3\r\n               7. line4                                    4. line4\r\n               8. line5                                    5. line5\r\n\r\n                       Guarantee the same indent\r\n             1. line1     :NumberedList       1. line1 \r\n               2. line2                                    2. line2\r\n               5. line3                                    3. line3\r\n               7. line4                                    4. line4\r\n               8. line5                                    5. line5\r\n\r\n                         Remove number\r\n               1. line1     :NoNumberedList   line1 \r\n               2. line2                                       line2\r\n               3. line3                                       line3\r\n               4. line4                                       line4\r\n               5. line5                                       line5\r\n\r\n                         Remove number\r\n               1  line1     :NoNumberedList   line1 \r\n               2  line2                                       line2\r\n               3  line3                                       line3\r\n               4  line4                                       line4\r\n               5  line5                                       line5\r\n\r\n                       Guarantee the same indent\r\n             1. line1     :NoNumberedList     line1 \r\n               2. line2                                       line2\r\n               3. line3                                       line3\r\n               4. line4                                       line4\r\n               5. line5                                       line5\r\n\r\n                       Just the same, no error\r\n               line1     :NoNumberedList      line1 \r\n               line2                                          line2\r\n               line3                                          line3\r\n               line4                                          line4\r\n               line5                                          line5\r\n\r\n                     Guarantee the same indent\r\n             line1     :NoNumberedList        line1 \r\n               line2                                          line2\r\n               line3                                          line3\r\n               line4                                          line4\r\n               line5                                          line5\r\n","install_details":"           Put this file in ~\/.vim\/plugin on *nux              \r\n           Or throw it in $vim\/vimfiles\/plugin on Windows","5":"           Put this file in ~\/.vim\/plugin on *nux              \r\n           Or throw it in $vim\/vimfiles\/plugin on Windows","first_name":"Tian","6":"Tian","last_name":"Huixiong","7":"Huixiong","releases":[{"0":"3715","vim_version":"7.3","1":"7.3","script_version":"1.3","2":"1.3","version_comment":"number align to right","3":"number align to right","package":"numlist.vim","4":"numlist.vim","src_id":"16562","5":"16562","creation_date":"1316687197","6":"1316687197"},{"0":"3715","vim_version":"7.0","1":"7.0","script_version":"1.2","2":"1.2","version_comment":"Remove number","3":"Remove number","package":"numlist.vim","4":"numlist.vim","src_id":"16449","5":"16449","creation_date":"1315122650","6":"1315122650"},{"0":"3715","vim_version":"7.0","1":"7.0","script_version":"1.1","2":"1.1","version_comment":"Commands will guarantee the items with same indent.\r\nIf they are not so, they are changed. ","3":"Commands will guarantee the items with same indent.\r\nIf they are not so, they are changed. ","package":"numlist.vim","4":"numlist.vim","src_id":"16404","5":"16404","creation_date":"1314718210","6":"1314718210"},{"0":"3715","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"This is unix line endings version","3":"This is unix line endings version","package":"numlist.vim","4":"numlist.vim","src_id":"16389","5":"16389","creation_date":"1314547776","6":"1314547776"},{"0":"3715","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"numlist.vim","4":"numlist.vim","src_id":"16388","5":"16388","creation_date":"1314546167","6":"1314546167"}]},"3714":{"script_id":"3714","0":"3714","script_name":"light2011","1":"light2011","script_type":"color scheme","2":"color scheme","summary":"light colorscheme suitable for programming","3":"light colorscheme suitable for programming","description":"light colorscheme suitable for programming\r\n","4":"light colorscheme suitable for programming\r\n","install_details":"put the light2011.vim file into `colors` folder,that's all.","5":"put the light2011.vim file into `colors` folder,that's all.","first_name":"yee","6":"yee","last_name":"xiaohu","7":"xiaohu","releases":[{"0":"3714","vim_version":"7.0","1":"7.0","script_version":"1.2","2":"1.2","version_comment":"change comment color","3":"change comment color","package":"light2011.vim","4":"light2011.vim","src_id":"16410","5":"16410","creation_date":"1314782207","6":"1314782207"},{"0":"3714","vim_version":"7.0","1":"7.0","script_version":"1.1","2":"1.1","version_comment":"g:colors_name ->light2011","3":"g:colors_name ->light2011","package":"light2011.vim","4":"light2011.vim","src_id":"16397","5":"16397","creation_date":"1314596984","6":"1314596984"},{"0":"3714","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"light2011.vim","4":"light2011.vim","src_id":"16367","5":"16367","creation_date":"1314422491","6":"1314422491"}]},"3713":{"script_id":"3713","0":"3713","script_name":"tabasco","1":"tabasco","script_type":"utility","2":"utility","summary":"Saves and loads tabs","3":"Saves and loads tabs","description":"----> I don't recommend this plugin anymore! See Final note.\r\n\r\n* Overview\r\n\r\nPlugin tabasco.vim provides two commands for Vim tabs loading\/saving:\r\n\r\n:Tabssave [name]\r\n\r\nSaves a list of tabs to _vim_tabasco.name file for current user (or .vim_tabasco.name for mac\/unix). If name is not specified the name \"default\" is used.\r\n\r\n:Tabsload [name]\r\n\r\nRemoves active tabs and loads new tabs from list in _vim_tabasco.name file like in :Tabssave.\r\nAdditionally it creates autocommand which saves list of tabs before quitting Vim (explicit using :Tabssave is not necessary after loading).\r\n\r\n\r\n* Additional information\r\n\r\nThe aim of this plugin is to provide functionality similar to Notepad++ (and other editors) which loads\/saves tabs automatically after opening\/closing editor respectively. To achieve this create following shortcut[s] (for Windows and gVim):\r\n\r\n\"C:\\Program Files\\Vim\\vim73\\gvim.exe\" -c \"Tabsload\"\r\nor:\r\n\"C:\\Program Files\\Vim\\vim73\\gvim.exe\" -c \"Tabsload name\"\r\n\r\nUsing second option allows to keep a couple of shortcuts with a separate lists of tabs to work with.\r\n\r\n\r\n* Limitations\r\n\r\nFor now many buffers in one tab are expanded to separate tabs on load.\r\nTab name should be full file path or any kind of accessible path, if it just a file name and Vim is run from a different directory it will not load it properly.\r\n\r\n\r\n* Notes\r\n\r\nPlugin was tested only with Vim 7.3 and Windows7 \/ 64bit.\r\nFeel free to leave me suggestions and corrections or to make your own modifications.\r\nI would like to thank Yegappan Lakshmanan for MRU plugin I was analyzing in order to learn how to write vim scripts.\r\n\r\n\r\n* Final note\r\n\r\nI just found :mksession and :runtime do the same better. Following shortcuts can be used:\r\n\"C:\\Program Files\\Vim\\vim73\\gvim.exe\" -c \"runtime Session.vim\"  -c \"autocmd VimLeave * exe 'mksession!'\"\r\nor\r\n\"C:\\Program Files\\Vim\\vim73\\gvim.exe\" -c \"runtime sessionname.vim\"  -c \"autocmd VimLeave * exe 'mksession! sessionname.vim'\"","4":"----> I don't recommend this plugin anymore! See Final note.\r\n\r\n* Overview\r\n\r\nPlugin tabasco.vim provides two commands for Vim tabs loading\/saving:\r\n\r\n:Tabssave [name]\r\n\r\nSaves a list of tabs to _vim_tabasco.name file for current user (or .vim_tabasco.name for mac\/unix). If name is not specified the name \"default\" is used.\r\n\r\n:Tabsload [name]\r\n\r\nRemoves active tabs and loads new tabs from list in _vim_tabasco.name file like in :Tabssave.\r\nAdditionally it creates autocommand which saves list of tabs before quitting Vim (explicit using :Tabssave is not necessary after loading).\r\n\r\n\r\n* Additional information\r\n\r\nThe aim of this plugin is to provide functionality similar to Notepad++ (and other editors) which loads\/saves tabs automatically after opening\/closing editor respectively. To achieve this create following shortcut[s] (for Windows and gVim):\r\n\r\n\"C:\\Program Files\\Vim\\vim73\\gvim.exe\" -c \"Tabsload\"\r\nor:\r\n\"C:\\Program Files\\Vim\\vim73\\gvim.exe\" -c \"Tabsload name\"\r\n\r\nUsing second option allows to keep a couple of shortcuts with a separate lists of tabs to work with.\r\n\r\n\r\n* Limitations\r\n\r\nFor now many buffers in one tab are expanded to separate tabs on load.\r\nTab name should be full file path or any kind of accessible path, if it just a file name and Vim is run from a different directory it will not load it properly.\r\n\r\n\r\n* Notes\r\n\r\nPlugin was tested only with Vim 7.3 and Windows7 \/ 64bit.\r\nFeel free to leave me suggestions and corrections or to make your own modifications.\r\nI would like to thank Yegappan Lakshmanan for MRU plugin I was analyzing in order to learn how to write vim scripts.\r\n\r\n\r\n* Final note\r\n\r\nI just found :mksession and :runtime do the same better. Following shortcuts can be used:\r\n\"C:\\Program Files\\Vim\\vim73\\gvim.exe\" -c \"runtime Session.vim\"  -c \"autocmd VimLeave * exe 'mksession!'\"\r\nor\r\n\"C:\\Program Files\\Vim\\vim73\\gvim.exe\" -c \"runtime sessionname.vim\"  -c \"autocmd VimLeave * exe 'mksession! sessionname.vim'\"","install_details":"Put it into vim plugin directory.\r\nI suggest creating shortcuts mentioned in description.","5":"Put it into vim plugin directory.\r\nI suggest creating shortcuts mentioned in description.","first_name":"Adam","6":"Adam","last_name":"Szlachta","7":"Szlachta","releases":[{"0":"3713","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"tabasco.vim","4":"tabasco.vim","src_id":"16366","5":"16366","creation_date":"1314396330","6":"1314396330"}]},"3712":{"script_id":"3712","0":"3712","script_name":"tabpage.vim","1":"tabpage.vim","script_type":"utility","2":"utility","summary":"Beautify the tab pages","3":"Beautify the tab pages","description":"        \r\n         This script is very simple, just beautify the default tab page,  this works on GVIM.\r\n         See screenshots: http:\/\/vimer.1063083.n5.nabble.com\/GVIM-tabpage-beautify-td4737356.html\r\n\r\n         1.  Remove the path, only show filename.\r\n\r\n         2.  Add number to each tab page\r\n\r\n         3.  If buffer has been modified, add * to the title.\r\n             \r\n         4.  Limit the width of tab pages\r\n             All tab pages have the same width, except that who's name is very long.\r\n\r\n         5.  Add the line:   \r\n              set showtabline = 2      \" Allways show the tab page \r\n              to your vimrc file. Or just uncomment it from the tabpage.vim.  ","4":"        \r\n         This script is very simple, just beautify the default tab page,  this works on GVIM.\r\n         See screenshots: http:\/\/vimer.1063083.n5.nabble.com\/GVIM-tabpage-beautify-td4737356.html\r\n\r\n         1.  Remove the path, only show filename.\r\n\r\n         2.  Add number to each tab page\r\n\r\n         3.  If buffer has been modified, add * to the title.\r\n             \r\n         4.  Limit the width of tab pages\r\n             All tab pages have the same width, except that who's name is very long.\r\n\r\n         5.  Add the line:   \r\n              set showtabline = 2      \" Allways show the tab page \r\n              to your vimrc file. Or just uncomment it from the tabpage.vim.  ","install_details":"         \r\n         Put this file in ~\/.vim\/plugin on Linux\r\n         Or put it in $vim\/vimfiles\/plugin on Windows","5":"         \r\n         Put this file in ~\/.vim\/plugin on Linux\r\n         Or put it in $vim\/vimfiles\/plugin on Windows","first_name":"Tian","6":"Tian","last_name":"Huixiong","7":"Huixiong","releases":[{"0":"3712","vim_version":"7.3","1":"7.3","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"tabpage.vim","4":"tabpage.vim","src_id":"16362","5":"16362","creation_date":"1314346210","6":"1314346210"}]},"3711":{"script_id":"3711","0":"3711","script_name":"chinachess.vim","1":"chinachess.vim","script_type":"ftplugin","2":"ftplugin","summary":"中国象棋 china chess 游戏 game ","3":"中国象棋 china chess 游戏 game ","description":"用来浏览中国象棋棋谱(.pgn)文件 ,和电脑对战,让电脑和电脑对战 。并且可以推演棋局\r\nalt-d \/ <Home> 画棋盘,初始化棋谱内容 \r\nalt-n  \/ <PageDown>下一步棋 \r\nalt-p  \/ <PageUp> 上一步棋 \r\nalt-q  \/ <END>  退出 \r\n<F2>  电脑走一步红子\r\n<F4>  电脑走一步黑子\r\n空格  选中棋子 \r\n回车  把之前选中的棋子移动到当前位置 \r\n方向键 移动光标(确保在光标在有效的位置上移动)\r\n\u00e2\u0080\u009chttp:\/\/nas.jjxxbb.space:881\/dokuwiki\/doku.php?id=wiki:vimchess\"","4":"用来浏览中国象棋棋谱(.pgn)文件 ,和电脑对战,让电脑和电脑对战 。并且可以推演棋局\r\nalt-d \/ <Home> 画棋盘,初始化棋谱内容 \r\nalt-n  \/ <PageDown>下一步棋 \r\nalt-p  \/ <PageUp> 上一步棋 \r\nalt-q  \/ <END>  退出 \r\n<F2>  电脑走一步红子\r\n<F4>  电脑走一步黑子\r\n空格  选中棋子 \r\n回车  把之前选中的棋子移动到当前位置 \r\n方向键 移动光标(确保在光标在有效的位置上移动)\r\n\u00e2\u0080\u009chttp:\/\/nas.jjxxbb.space:881\/dokuwiki\/doku.php?id=wiki:vimchess\"","install_details":"将包解开后,将chinachess.vim 扔到ftplugin目录下\r\n在filetype.vim下添加\r\naugroup filetypedetect\r\n    au BufNewFile,BufRead *.pgn\t\t\tsetf chinachess\r\naugroup END\r\n\r\n然后用vim去打开pgn棋谱文件,就可以开始浏览该棋谱了。\r\n如果运行vim,直接在命令行输入:set ft=chinachess,然后按<Home>,会启动一个新的棋盘,\r\n然后开始享受下棋的乐趣吧","5":"将包解开后,将chinachess.vim 扔到ftplugin目录下\r\n在filetype.vim下添加\r\naugroup filetypedetect\r\n    au BufNewFile,BufRead *.pgn\t\t\tsetf chinachess\r\naugroup END\r\n\r\n然后用vim去打开pgn棋谱文件,就可以开始浏览该棋谱了。\r\n如果运行vim,直接在命令行输入:set ft=chinachess,然后按<Home>,会启动一个新的棋盘,\r\n然后开始享受下棋的乐趣吧","first_name":"Zhang","6":"Zhang","last_name":"ping","7":"ping","releases":[{"0":"3711","vim_version":"7.0","1":"7.0","script_version":"1.4","2":"1.4","version_comment":"添加新功能:可以自动下棋,使用了象棋引擎,棋力很厉害。\r\n具体就是把包里的exe文件拷贝到system32或者vim的安装目录下。\r\n更新chinachess.vim插件,打开vim,设置文件格式是chinachess:\r\nset ft=chinachess。这时候按<Home>是开始棋局,\r\n会画一个棋盘,然后是棋子。按<F2>是电脑走红棋,按<F4>是电脑走黑棋,当然,你也可以\r\n自己走棋。看看你的走法和电脑的有何差距!","3":"添加新功能:可以自动下棋,使用了象棋引擎,棋力很厉害。\r\n具体就是把包里的exe文件拷贝到system32或者vim的安装目录下。\r\n更新chinachess.vim插件,打开vim,设置文件格式是chinachess:\r\nset ft=chinachess。这时候按<Home>是开始棋局,\r\n会画一个棋盘,然后是棋子。按<F2>是电脑走红棋,按<F4>是电脑走黑棋,当然,你也可以\r\n自己走棋。看看你的走法和电脑的有何差距!","package":"vim-chess.rar","4":"vim-chess.rar","src_id":"16845","5":"16845","creation_date":"1320939003","6":"1320939003"},{"0":"3711","vim_version":"7.0","1":"7.0","script_version":"1.3","2":"1.3","version_comment":"1.改变背景颜色，和棋子更容易区分\r\n2.增加上下左右箭头动作映射，按上下左右，可以在棋盘的格子上移动\r\n3.增加空格和回车映射，用上下左右移动光标到棋子上，按空格表示选中，然后再移动光标到想要去的地方，按回车，棋子可以移动\r\n4.增加映射<leader>q  ：退出\r\n5.修改了一些小bug","3":"1.改变背景颜色，和棋子更容易区分\r\n2.增加上下左右箭头动作映射，按上下左右，可以在棋盘的格子上移动\r\n3.增加空格和回车映射，用上下左右移动光标到棋子上，按空格表示选中，然后再移动光标到想要去的地方，按回车，棋子可以移动\r\n4.增加映射<leader>q  ：退出\r\n5.修改了一些小bug","package":"chinachess.vim","4":"chinachess.vim","src_id":"16636","5":"16636","creation_date":"1318042788","6":"1318042788"},{"0":"3711","vim_version":"7.0","1":"7.0","script_version":"none","2":"none","version_comment":"提供一些棋谱文件，可以用该插件浏览！","3":"提供一些棋谱文件，可以用该插件浏览！","package":"99gr.7z","4":"99gr.7z","src_id":"16614","5":"16614","creation_date":"1317559988","6":"1317559988"},{"0":"3711","vim_version":"7.0","1":"7.0","script_version":"1.2","2":"1.2","version_comment":"更新了一些bug","3":"更新了一些bug","package":"chinachess.vim","4":"chinachess.vim","src_id":"16613","5":"16613","creation_date":"1317559435","6":"1317559435"},{"0":"3711","vim_version":"7.0","1":"7.0","script_version":"1.1","2":"1.1","version_comment":"更新一些界面颜色问题。\r\n增加MoveChess函数，可以直接用call MoveChess(\"车一平二\")来移动棋子。","3":"更新一些界面颜色问题。\r\n增加MoveChess函数，可以直接用call MoveChess(\"车一平二\")来移动棋子。","package":"chinachess.vim","4":"chinachess.vim","src_id":"16525","5":"16525","creation_date":"1315993070","6":"1315993070"},{"0":"3711","vim_version":"7.0","1":"7.0","script_version":"7.0","2":"7.0","version_comment":"Initial upload","3":"Initial upload","package":"chinachess.rar","4":"chinachess.rar","src_id":"16360","5":"16360","creation_date":"1314339452","6":"1314339452"}]},"3710":{"script_id":"3710","0":"3710","script_name":"EasyPeasy","1":"EasyPeasy","script_type":"utility","2":"utility","summary":"Easily create and include system tags","3":"Easily create and include system tags","description":"EasyPeasy parses C source code for included system headers and Generates\r\nan .lvimrc (or whatever you set g:lvimrc_filename) with 'tags' variable concatinations.\r\nI wrote it for the reason that having full system tags is totally unpleasant experience\r\nbecause of performance and existing garbage tags unused by the project. This script allows me\r\nto have just exactly what is used by the source code, which makes omnicompletion fast and accurate.\r\n\r\n \tExample of generated .lvimrc:\r\n\t\tset tags+=~\/.vim\/tags\/getopt.tags\r\n\t\tset tags+=~\/.vim\/tags\/locale.tags\r\n\t\tset tags+=~\/.vim\/tags\/stdio.tags\r\n\t\tset tags+=~\/.vim\/tags\/unistd.tags\r\n\t\tset tags+=~\/.vim\/tags\/signal.tags\r\n\t\tset tags+=~\/.vim\/tags\/xcb.tags\r\n\r\n\r\nUSAGE:\r\n\r\nTo do the magic, use :EasyPeasy command from project top folder. This is the only command this script\r\nhas. \r\n\r\n\r\nCONFIGURATION:\r\n\r\nNOTE: The provided values are the default ones\r\n\r\nThe directory where the script will look ctags generated tag files:\r\n\tlet g:tag_directory = \"~\/.vim\/tags\/\"                     \r\n\r\nThe extension of tag file:\r\n\tlet g:tag_extension = \".tags\"                            \r\n\r\nLocal vimrc file name:\r\n\tlet g:lvimrc_filename = \".lvimrc\"                      \r\n\r\nPaths to the dir of system library headers in case tags file not found\r\n\tlet g:include_paths = \"\/usr\/include\/,\/usr\/local\/include\/\"\r\n\r\nThis variable can be changed while performing the scan by answering the prompts [Y] - Yes to all | [N] - No to all\r\n0 = show prompts on tags file creation\r\n1 = generate the tags file without prompt (sames as answering 'Y' to the prompt)\r\n2 = don't generate tag files - use the ones which exist under ~\/.vim\/tags only\r\n\tlet g:prompt_create_tags = 0\r\n\r\n\r\nDETAILS:\r\n\r\nThis is how the script works:\r\nIt parses the files recursively starting from cwd and gets all included\r\nfiles (skips local includes). It will use the first word as library name.\r\n\r\nExample:\r\n\r\n\t1.\t#include <mylib.h>\r\n\r\n\tUsing the statement above, it will try to find mylib.tags file under\r\n\ttags directory. If not found, it will check if \/usr\/include\/mylib.h\r\n\theader exists. If so, it will prompt you if you want to generate\r\n\t~\/.vim\/ctags\/mylib.tags file using this header. If no, it will skip it.\r\n\tIf yes, it will genearte the tags and include into .lvimrc\r\n\r\n\t2.\t#include <anotherlib\/mylib.h>\r\n\r\n\tIn this case it will use the folder name as library name. So it will\r\n\tcheck if ~\/.vim\/tags\/anotherlib.tags exist. If no, it will check if\r\n\t\/usr\/include\/anotherlib folder exist. If so, it will ask for confirmation\r\n        to generate the tags of whole folder headers. The rest is the\r\n\tsame as in the first example.\r\n\r\n\t3.\tIn case no tags and no headers found\r\n\r\n\tIn this case you'll get prompted to enter the path to the header or\r\n\tfolder to use to generate the tags. Empty input will result in\r\n\tskipping this library.\r\n\tNOTE: This sometimes can happen in example on #include <dbus\/dbus.h>\r\n\twhen the actual headers path is \/usr\/include\/dbus-1.0\/dbus\/dbus.h\r\n\r\n\r\nCHANGELOG:\r\n\r\n0.1:\r\n  - First release.\r\n\r\n\r\nSHORT TEASER:\r\nhttp:\/\/youtu.be\/HjhwJkhuD0w\r\nOR SCREENSHOT:\r\nhttp:\/\/img607.imageshack.us\/img607\/4401\/tutorn.png","4":"EasyPeasy parses C source code for included system headers and Generates\r\nan .lvimrc (or whatever you set g:lvimrc_filename) with 'tags' variable concatinations.\r\nI wrote it for the reason that having full system tags is totally unpleasant experience\r\nbecause of performance and existing garbage tags unused by the project. This script allows me\r\nto have just exactly what is used by the source code, which makes omnicompletion fast and accurate.\r\n\r\n \tExample of generated .lvimrc:\r\n\t\tset tags+=~\/.vim\/tags\/getopt.tags\r\n\t\tset tags+=~\/.vim\/tags\/locale.tags\r\n\t\tset tags+=~\/.vim\/tags\/stdio.tags\r\n\t\tset tags+=~\/.vim\/tags\/unistd.tags\r\n\t\tset tags+=~\/.vim\/tags\/signal.tags\r\n\t\tset tags+=~\/.vim\/tags\/xcb.tags\r\n\r\n\r\nUSAGE:\r\n\r\nTo do the magic, use :EasyPeasy command from project top folder. This is the only command this script\r\nhas. \r\n\r\n\r\nCONFIGURATION:\r\n\r\nNOTE: The provided values are the default ones\r\n\r\nThe directory where the script will look ctags generated tag files:\r\n\tlet g:tag_directory = \"~\/.vim\/tags\/\"                     \r\n\r\nThe extension of tag file:\r\n\tlet g:tag_extension = \".tags\"                            \r\n\r\nLocal vimrc file name:\r\n\tlet g:lvimrc_filename = \".lvimrc\"                      \r\n\r\nPaths to the dir of system library headers in case tags file not found\r\n\tlet g:include_paths = \"\/usr\/include\/,\/usr\/local\/include\/\"\r\n\r\nThis variable can be changed while performing the scan by answering the prompts [Y] - Yes to all | [N] - No to all\r\n0 = show prompts on tags file creation\r\n1 = generate the tags file without prompt (sames as answering 'Y' to the prompt)\r\n2 = don't generate tag files - use the ones which exist under ~\/.vim\/tags only\r\n\tlet g:prompt_create_tags = 0\r\n\r\n\r\nDETAILS:\r\n\r\nThis is how the script works:\r\nIt parses the files recursively starting from cwd and gets all included\r\nfiles (skips local includes). It will use the first word as library name.\r\n\r\nExample:\r\n\r\n\t1.\t#include <mylib.h>\r\n\r\n\tUsing the statement above, it will try to find mylib.tags file under\r\n\ttags directory. If not found, it will check if \/usr\/include\/mylib.h\r\n\theader exists. If so, it will prompt you if you want to generate\r\n\t~\/.vim\/ctags\/mylib.tags file using this header. If no, it will skip it.\r\n\tIf yes, it will genearte the tags and include into .lvimrc\r\n\r\n\t2.\t#include <anotherlib\/mylib.h>\r\n\r\n\tIn this case it will use the folder name as library name. So it will\r\n\tcheck if ~\/.vim\/tags\/anotherlib.tags exist. If no, it will check if\r\n\t\/usr\/include\/anotherlib folder exist. If so, it will ask for confirmation\r\n        to generate the tags of whole folder headers. The rest is the\r\n\tsame as in the first example.\r\n\r\n\t3.\tIn case no tags and no headers found\r\n\r\n\tIn this case you'll get prompted to enter the path to the header or\r\n\tfolder to use to generate the tags. Empty input will result in\r\n\tskipping this library.\r\n\tNOTE: This sometimes can happen in example on #include <dbus\/dbus.h>\r\n\twhen the actual headers path is \/usr\/include\/dbus-1.0\/dbus\/dbus.h\r\n\r\n\r\nCHANGELOG:\r\n\r\n0.1:\r\n  - First release.\r\n\r\n\r\nSHORT TEASER:\r\nhttp:\/\/youtu.be\/HjhwJkhuD0w\r\nOR SCREENSHOT:\r\nhttp:\/\/img607.imageshack.us\/img607\/4401\/tutorn.png","install_details":"Extract the package to your ~\/.vim folder, include the documentation by typing\r\n:helptags ~\/.vim\/doc, and you are ready to go!\r\nNOTE: be sure you do have ctags (Exuberant Ctags) installed.","5":"Extract the package to your ~\/.vim folder, include the documentation by typing\r\n:helptags ~\/.vim\/doc, and you are ready to go!\r\nNOTE: be sure you do have ctags (Exuberant Ctags) installed.","first_name":"Arvydas","6":"Arvydas","last_name":"Sidorenko","7":"Sidorenko","releases":[{"0":"3710","vim_version":"7.0","1":"7.0","script_version":"0.2","2":"0.2","version_comment":"FIXED: if header is not found and you choose to ignore it, the prompt still shows up with it if it's included in multiple places","3":"FIXED: if header is not found and you choose to ignore it, the prompt still shows up with it if it's included in multiple places","package":"easypeasy.vim","4":"easypeasy.vim","src_id":"17342","5":"17342","creation_date":"1327959401","6":"1327959401"},{"0":"3710","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"easypeasy.tar.gz","4":"easypeasy.tar.gz","src_id":"16359","5":"16359","creation_date":"1314338411","6":"1314338411"}]},"3709":{"script_id":"3709","0":"3709","script_name":"vim-ipython","1":"vim-ipython","script_type":"ftplugin","2":"ftplugin","summary":"A two-way integration between Vim and IPython 0.11+","3":"A two-way integration between Vim and IPython 0.11+","description":"* author: Paul Ivanov (http:\/\/pirsquared.org)\r\n* github: http:\/\/github.com\/ivanov\/vim-ipython\r\n* demos: http:\/\/pirsquared.org\/vim-ipython\/\r\n* blogpost: http:\/\/pirsquared.org\/blog\/2011\/07\/28\/vim-ipython\/\r\n\r\nUsing this plugin, you can send lines or whole files for IPython to\r\nexecute, and also get back object introspection and word completions in\r\nVim, like what you get with: ``object?<enter>`` and ``object.<tab>`` in\r\nIPython.\r\n\r\nThe big change from previous versions of ``ipy.vim`` is that it no longer\r\nrequires the old brittle ``ipy_vimserver.py`` instantiation, and since\r\nit uses just vim and python, it is platform independent (i.e. works\r\neven on windows, unlike the previous \\*nix only solution). The requirements\r\nare IPython 0.11+ with zeromq capabilities, vim compiled with +python.\r\n\r\nIf you can launch ``ipython qtconsole`` or ``ipython kernel``, and\r\n``:echo has('python')`` returns 1 in vim, you should be good to go.\r\n\r\n-----------------\r\nQuickstart Guide:\r\n-----------------\r\nStart ``ipython qtconsole`` [*]_ and copy the connection string.\r\nSource ``ipy.vim`` file, which provides new IPython command::\r\n\r\n  :source ipy.vim\r\n  (or copy it to ~\/.vim\/ftplugin\/python to load automatically)\r\n\r\n  :IPythonClipboard\r\n  (or :IPythonXSelection if you're using X11 without having to copy)\r\n\r\nThe :IPython command allows you to put the full connection string. For IPython\r\n0.11, it would look like this::\r\n\r\n  :IPython --existing --shell=41882 --iopub=43286 --stdin=34987 --hb=36697\r\n\r\nand for IPython 0.12, like this::\r\n\r\n  :IPython --existing kernel-85997.json\r\n\r\nThe ``:IPythonClipboard`` command just uses the ``+`` register to get the\r\nconnection string, whereas ``:IPythonXSelection`` uses the ``*`` register.\r\n\r\n**NEW in IPython 0.12**!\r\nSince IPython 0.12, you can simply use::\r\n\r\n  :IPython\r\n\r\nwithout arguments to connect to the most recent IPython session (this is the\r\nsame as passing just the ``--existing`` flag to ``ipython qtconsole`` and\r\n``ipython console``.\r\n\r\n.. [*] Though the demos above use ``qtconsole``, it is not required\r\n    for this workflow, it's just that it was the easiest way to show how to\r\n    make use of the new functionality in 0.11 release. Since IPython 0.12, you\r\n    can use ``ipython kernel`` to create a kernel and get the connection\r\n    string to use for any frontend (including vim-ipython), or use ``ipython\r\n    console`` to create a kernel and immediately connect to it using a\r\n    terminal-based client. You can even connect to an active IPython Notebook\r\n    kernel - just watch for the connection string that gets printed when you\r\n    open the notebook, or use the ``%connect_info`` magic to get the\r\n    connection string.  If you are still using 0.11, you can launch a regular\r\n    kernel using ``python -c \"from IPython.zmq.ipkernel import main; main()\"``\r\n\r\n------------------------\r\nSending lines to IPython\r\n------------------------\r\nNow type out a line and send it to IPython using ``<Ctrl-S>`` from Command mode::\r\n\r\n  import os\r\n\r\nYou should see a notification message confirming the line was sent, along\r\nwith the input number for the line, like so ``In[1]: import os``.\r\n\r\n``<Ctrl-S>`` also works from insert mode, but doesn't show notification,\r\nunless ``monitor_subchannel`` is set to ``True`` (see `vim-ipython 'shell'`_,\r\nbelow)\r\n\r\nIt also works blockwise in Visual Mode. Select and send these lines using\r\n``<Ctrl-S>``::\r\n\r\n  import this,math # secret decoder ring\r\n  a,b,c,d,e,f,g,h,i = range(1,10)\r\n  code =(c,a,d,a,e,i,)\r\n  msg = '...jrer nyy frag sebz Ivz.\\nIvz+VClguba=%fyl '+this.s.split()[g]\r\n  decode=lambda x:\"\\n\"+\"\".join([this.d.get(c,c) for c in x])+\"!\"\r\n  format=lambda x:'These lines:\\n  '+'\\n  '.join([l for l in x.splitlines()])\r\n  secret_decoder = lambda a,b: format(a)+decode(msg)%str(b)[:-1]\r\n  '%d'*len(code)%code == str(int(math.pi*1e5))\r\n\r\nThen, go to the qtconsole and run this line::\r\n\r\n  print secret_decoder(_i,_)\r\n\r\nYou can also send whole files to IPython's ``%run`` magic using ``<F5>``.\r\n\r\n**NEW in IPython 0.12**!\r\nIf you're trying to do run code fragments that have leading whitespace, use\r\n``<Alt-S>`` instead - it will dedent a single line, and remove the leading\r\nwhitespace of the first line from all lines in a visual mode selection.\r\n\r\n-------------------------------\r\nIPython's object? Functionality\r\n-------------------------------\r\n\r\nIf you're using gvim, mouse-over a variable to see IPython's ``?`` equivalent.\r\nIf you're using vim from a terminal, or want to copy something from the\r\ndocstring, type ``<leader>d``. ``<leader>`` is usually ``\\`` (the backslash\r\nkey).  This will open a quickpreview window, which can be closed by hitting\r\n``q`` or ``<escape>``.\r\n\r\n--------------------------------------\r\nIPython's tab-completion Functionality\r\n--------------------------------------\r\nvim-ipython activates a 'completefunc' that queries IPython.\r\nA completefunc is activated using ``Ctrl-X Ctrl-U`` in Insert Mode (vim\r\ndefault). You can combine this functionality with SuperTab to get tab\r\ncompletion.\r\n\r\n-------------------\r\nvim-ipython 'shell'\r\n-------------------\r\n**NEW since IPython 0.11**!\r\n\r\nBy monitoring km.sub_channel, we can recreate what messages were sent to\r\nIPython, and what IPython sends back in response.\r\n\r\n``monitor_subchannel`` is a parameter that sets whether this 'shell' should\r\nupdated on every sent command (default: True).\r\n\r\nIf at any later time you wish to bring this shell up, including if you've set\r\n``monitor_subchannel=False``, hit ``<leader>s``.\r\n\r\n-------\r\nOptions\r\n-------\r\nYou can change these at the top of the ipy.vim::\r\n\r\n  reselect = False            # reselect lines after sending from Visual mode\r\n  show_execution_count = True # wait to get numbers for In[43]: feedback?\r\n  monitor_subchannel = True   # update vim-ipython 'shell' on every send?\r\n  run_flags= \"-i\"             # flags to for IPython's run magic when using <F5>\r\n\r\n**Disabling default mappings**\r\nIn your own ``.vimrc``, if you don't like the mappings provided by default,\r\nyou can define a variable ``let g:ipy_perform_mappings=0`` which will prevent\r\nvim-ipython from defining any of the default mappings.\r\n\r\n---------------\r\nCurrent issues:\r\n---------------\r\n- For now, vim-ipython only connects to an ipython session in progress.\r\n- The ipdb integration is not yet re-implemented.\r\n- If you're running inside ``screen``, read about the ``<CTRL-S>`` issue `here\r\n  <http:\/\/munkymorgy.blogspot.com\/2008\/07\/screen-ctrl-s-bug.html>`_, and add\r\n  this line to your ``.bashrc`` to fix it::\r\n\r\n    stty stop undef # to unmap ctrl-s\r\n\r\n- In vim, if you're getting ``ImportError: No module named\r\n  IPython.zmq.blockingkernelmanager`` but are able to import it in regular\r\n  python, **either**\r\n\r\n  1. your ``sys.path`` in vim differs from the ``sys.path`` in regular python.\r\n     Try running these two lines, and comparing their output files::\r\n\r\n      $ vim -c 'py import vim, sys; vim.current.buffer.append(sys.path)' -c ':wq vim_syspath'\r\n      $ python -c \"import sys; f=file('python_syspath','w'); f.write('\\n'.join(sys.path)); f.close()\"\r\n\r\n  **or**\r\n\r\n  2. your vim is compiled against a different python than you are launching. See\r\n     if there's a difference between ::\r\n\r\n      $ vim -c ':py import os; print os.__file__' -c ':q'\r\n      $ python -c 'import os; print os.__file__'\r\n\r\n- For vim inside a terminal, using the arrow keys won't work inside a\r\n  documentation buffer, because the mapping for ``<Esc>`` overlaps with\r\n  ``^[OA`` and so on, and we use ``<Esc>`` as a quick way of closing the\r\n  documentation preview window. If you want go without this quick close\r\n  functionality and want to use the arrow keys instead, look for instructions\r\n  starting with \"Known issue: to enable the use of arrow keys...\" in the\r\n  ``get_doc_buffer`` function.\r\n\r\n- @fholgado's update to ``minibufexpl.vim`` that is up on GitHub will always\r\n  put the cursor in the minibuf after sending a command when\r\n  ``monitor_subchannel`` is set. This is a bug in minibufexpl.vim and the workaround\r\n  is described in vim-ipython issue #7.\r\n\r\n----------------------------\r\nThanks and Bug Participation\r\n----------------------------\r\n* @MinRK for guiding me through the IPython kernel manager protocol.\r\n* @nakamuray and @tcheneau for reporting and providing a fix for when vim is\r\n  compiled without a gui (#1)\r\n* @unpingco for reporting Windows bugs (#3,#4), providing better multiline\r\n  dedenting (#15), and suggesting that a resized vim-ipython shell stays\r\n  resized (#16).\r\n* @simon-b for terminal vim arrow key issue (#5)\r\n* @jorgesca and @kwgoodman for shell update problems (#6)\r\n* @zeekay for easily allowing custom mappings (#9)\r\n* @minrk for support of connection_file-based IPython connection (#13)\r\n* @jorgesca for reporting the lack of profile handling capability (#14)\r\n* @enzbang for removing mapping that's not currently functional (#17)\r\n* @ogrisel  for fixing documentation typo (#19)\r\n","4":"* author: Paul Ivanov (http:\/\/pirsquared.org)\r\n* github: http:\/\/github.com\/ivanov\/vim-ipython\r\n* demos: http:\/\/pirsquared.org\/vim-ipython\/\r\n* blogpost: http:\/\/pirsquared.org\/blog\/2011\/07\/28\/vim-ipython\/\r\n\r\nUsing this plugin, you can send lines or whole files for IPython to\r\nexecute, and also get back object introspection and word completions in\r\nVim, like what you get with: ``object?<enter>`` and ``object.<tab>`` in\r\nIPython.\r\n\r\nThe big change from previous versions of ``ipy.vim`` is that it no longer\r\nrequires the old brittle ``ipy_vimserver.py`` instantiation, and since\r\nit uses just vim and python, it is platform independent (i.e. works\r\neven on windows, unlike the previous \\*nix only solution). The requirements\r\nare IPython 0.11+ with zeromq capabilities, vim compiled with +python.\r\n\r\nIf you can launch ``ipython qtconsole`` or ``ipython kernel``, and\r\n``:echo has('python')`` returns 1 in vim, you should be good to go.\r\n\r\n-----------------\r\nQuickstart Guide:\r\n-----------------\r\nStart ``ipython qtconsole`` [*]_ and copy the connection string.\r\nSource ``ipy.vim`` file, which provides new IPython command::\r\n\r\n  :source ipy.vim\r\n  (or copy it to ~\/.vim\/ftplugin\/python to load automatically)\r\n\r\n  :IPythonClipboard\r\n  (or :IPythonXSelection if you're using X11 without having to copy)\r\n\r\nThe :IPython command allows you to put the full connection string. For IPython\r\n0.11, it would look like this::\r\n\r\n  :IPython --existing --shell=41882 --iopub=43286 --stdin=34987 --hb=36697\r\n\r\nand for IPython 0.12, like this::\r\n\r\n  :IPython --existing kernel-85997.json\r\n\r\nThe ``:IPythonClipboard`` command just uses the ``+`` register to get the\r\nconnection string, whereas ``:IPythonXSelection`` uses the ``*`` register.\r\n\r\n**NEW in IPython 0.12**!\r\nSince IPython 0.12, you can simply use::\r\n\r\n  :IPython\r\n\r\nwithout arguments to connect to the most recent IPython session (this is the\r\nsame as passing just the ``--existing`` flag to ``ipython qtconsole`` and\r\n``ipython console``.\r\n\r\n.. [*] Though the demos above use ``qtconsole``, it is not required\r\n    for this workflow, it's just that it was the easiest way to show how to\r\n    make use of the new functionality in 0.11 release. Since IPython 0.12, you\r\n    can use ``ipython kernel`` to create a kernel and get the connection\r\n    string to use for any frontend (including vim-ipython), or use ``ipython\r\n    console`` to create a kernel and immediately connect to it using a\r\n    terminal-based client. You can even connect to an active IPython Notebook\r\n    kernel - just watch for the connection string that gets printed when you\r\n    open the notebook, or use the ``%connect_info`` magic to get the\r\n    connection string.  If you are still using 0.11, you can launch a regular\r\n    kernel using ``python -c \"from IPython.zmq.ipkernel import main; main()\"``\r\n\r\n------------------------\r\nSending lines to IPython\r\n------------------------\r\nNow type out a line and send it to IPython using ``<Ctrl-S>`` from Command mode::\r\n\r\n  import os\r\n\r\nYou should see a notification message confirming the line was sent, along\r\nwith the input number for the line, like so ``In[1]: import os``.\r\n\r\n``<Ctrl-S>`` also works from insert mode, but doesn't show notification,\r\nunless ``monitor_subchannel`` is set to ``True`` (see `vim-ipython 'shell'`_,\r\nbelow)\r\n\r\nIt also works blockwise in Visual Mode. Select and send these lines using\r\n``<Ctrl-S>``::\r\n\r\n  import this,math # secret decoder ring\r\n  a,b,c,d,e,f,g,h,i = range(1,10)\r\n  code =(c,a,d,a,e,i,)\r\n  msg = '...jrer nyy frag sebz Ivz.\\nIvz+VClguba=%fyl '+this.s.split()[g]\r\n  decode=lambda x:\"\\n\"+\"\".join([this.d.get(c,c) for c in x])+\"!\"\r\n  format=lambda x:'These lines:\\n  '+'\\n  '.join([l for l in x.splitlines()])\r\n  secret_decoder = lambda a,b: format(a)+decode(msg)%str(b)[:-1]\r\n  '%d'*len(code)%code == str(int(math.pi*1e5))\r\n\r\nThen, go to the qtconsole and run this line::\r\n\r\n  print secret_decoder(_i,_)\r\n\r\nYou can also send whole files to IPython's ``%run`` magic using ``<F5>``.\r\n\r\n**NEW in IPython 0.12**!\r\nIf you're trying to do run code fragments that have leading whitespace, use\r\n``<Alt-S>`` instead - it will dedent a single line, and remove the leading\r\nwhitespace of the first line from all lines in a visual mode selection.\r\n\r\n-------------------------------\r\nIPython's object? Functionality\r\n-------------------------------\r\n\r\nIf you're using gvim, mouse-over a variable to see IPython's ``?`` equivalent.\r\nIf you're using vim from a terminal, or want to copy something from the\r\ndocstring, type ``<leader>d``. ``<leader>`` is usually ``\\`` (the backslash\r\nkey).  This will open a quickpreview window, which can be closed by hitting\r\n``q`` or ``<escape>``.\r\n\r\n--------------------------------------\r\nIPython's tab-completion Functionality\r\n--------------------------------------\r\nvim-ipython activates a 'completefunc' that queries IPython.\r\nA completefunc is activated using ``Ctrl-X Ctrl-U`` in Insert Mode (vim\r\ndefault). You can combine this functionality with SuperTab to get tab\r\ncompletion.\r\n\r\n-------------------\r\nvim-ipython 'shell'\r\n-------------------\r\n**NEW since IPython 0.11**!\r\n\r\nBy monitoring km.sub_channel, we can recreate what messages were sent to\r\nIPython, and what IPython sends back in response.\r\n\r\n``monitor_subchannel`` is a parameter that sets whether this 'shell' should\r\nupdated on every sent command (default: True).\r\n\r\nIf at any later time you wish to bring this shell up, including if you've set\r\n``monitor_subchannel=False``, hit ``<leader>s``.\r\n\r\n-------\r\nOptions\r\n-------\r\nYou can change these at the top of the ipy.vim::\r\n\r\n  reselect = False            # reselect lines after sending from Visual mode\r\n  show_execution_count = True # wait to get numbers for In[43]: feedback?\r\n  monitor_subchannel = True   # update vim-ipython 'shell' on every send?\r\n  run_flags= \"-i\"             # flags to for IPython's run magic when using <F5>\r\n\r\n**Disabling default mappings**\r\nIn your own ``.vimrc``, if you don't like the mappings provided by default,\r\nyou can define a variable ``let g:ipy_perform_mappings=0`` which will prevent\r\nvim-ipython from defining any of the default mappings.\r\n\r\n---------------\r\nCurrent issues:\r\n---------------\r\n- For now, vim-ipython only connects to an ipython session in progress.\r\n- The ipdb integration is not yet re-implemented.\r\n- If you're running inside ``screen``, read about the ``<CTRL-S>`` issue `here\r\n  <http:\/\/munkymorgy.blogspot.com\/2008\/07\/screen-ctrl-s-bug.html>`_, and add\r\n  this line to your ``.bashrc`` to fix it::\r\n\r\n    stty stop undef # to unmap ctrl-s\r\n\r\n- In vim, if you're getting ``ImportError: No module named\r\n  IPython.zmq.blockingkernelmanager`` but are able to import it in regular\r\n  python, **either**\r\n\r\n  1. your ``sys.path`` in vim differs from the ``sys.path`` in regular python.\r\n     Try running these two lines, and comparing their output files::\r\n\r\n      $ vim -c 'py import vim, sys; vim.current.buffer.append(sys.path)' -c ':wq vim_syspath'\r\n      $ python -c \"import sys; f=file('python_syspath','w'); f.write('\\n'.join(sys.path)); f.close()\"\r\n\r\n  **or**\r\n\r\n  2. your vim is compiled against a different python than you are launching. See\r\n     if there's a difference between ::\r\n\r\n      $ vim -c ':py import os; print os.__file__' -c ':q'\r\n      $ python -c 'import os; print os.__file__'\r\n\r\n- For vim inside a terminal, using the arrow keys won't work inside a\r\n  documentation buffer, because the mapping for ``<Esc>`` overlaps with\r\n  ``^[OA`` and so on, and we use ``<Esc>`` as a quick way of closing the\r\n  documentation preview window. If you want go without this quick close\r\n  functionality and want to use the arrow keys instead, look for instructions\r\n  starting with \"Known issue: to enable the use of arrow keys...\" in the\r\n  ``get_doc_buffer`` function.\r\n\r\n- @fholgado's update to ``minibufexpl.vim`` that is up on GitHub will always\r\n  put the cursor in the minibuf after sending a command when\r\n  ``monitor_subchannel`` is set. This is a bug in minibufexpl.vim and the workaround\r\n  is described in vim-ipython issue #7.\r\n\r\n----------------------------\r\nThanks and Bug Participation\r\n----------------------------\r\n* @MinRK for guiding me through the IPython kernel manager protocol.\r\n* @nakamuray and @tcheneau for reporting and providing a fix for when vim is\r\n  compiled without a gui (#1)\r\n* @unpingco for reporting Windows bugs (#3,#4), providing better multiline\r\n  dedenting (#15), and suggesting that a resized vim-ipython shell stays\r\n  resized (#16).\r\n* @simon-b for terminal vim arrow key issue (#5)\r\n* @jorgesca and @kwgoodman for shell update problems (#6)\r\n* @zeekay for easily allowing custom mappings (#9)\r\n* @minrk for support of connection_file-based IPython connection (#13)\r\n* @jorgesca for reporting the lack of profile handling capability (#14)\r\n* @enzbang for removing mapping that's not currently functional (#17)\r\n* @ogrisel  for fixing documentation typo (#19)\r\n","install_details":"you can unzip the archive in your .vim directory, but I recommend  the modern way of trying vim scripts by using Pathogen and unziping the archive in its own directory in .vim\/bundles\/","5":"you can unzip the archive in your .vim directory, but I recommend  the modern way of trying vim scripts by using Pathogen and unziping the archive in its own directory in .vim\/bundles\/","first_name":"Paul","6":"Paul","last_name":"Ivanov","7":"Ivanov","releases":[{"0":"3709","vim_version":"7.0","1":"7.0","script_version":"20120123","2":"20120123","version_comment":"Code of vim-ipython as shipped with IPython 0.12, though the README has been updated a bit since then.","3":"Code of vim-ipython as shipped with IPython 0.12, though the README has been updated a bit since then.","package":"vim-ipython2012-01-23.zip","4":"vim-ipython2012-01-23.zip","src_id":"17309","5":"17309","creation_date":"1327349306","6":"1327349306"},{"0":"3709","vim_version":"6.0","1":"6.0","script_version":"20110825","2":"20110825","version_comment":"Initial upload","3":"Initial upload","package":"vim-ipython2011-08-25.zip","4":"vim-ipython2011-08-25.zip","src_id":"16348","5":"16348","creation_date":"1314260236","6":"1314260236"}]},"3708":{"script_id":"3708","0":"3708","script_name":"swapcol.vim","1":"swapcol.vim","script_type":"utility","2":"utility","summary":"Swap two columns","3":"Swap two columns","description":"         Swap columns, the columns are separated by blank.\r\n         Column maybe is word, or maybe not:\r\n            col1   col2   col3   col4   col5\r\n            command!  -nargs=*  -range  -complete=command\r\n\r\n         1. Move cursor on col1, and press  ]c  you will see:\r\n            col2   col1   col3   col4   col5\r\n\r\n         2. Move cursor on -range and press [c, you will see:\r\n            command!  -range  -nargs=*  -complete=command\r\n\r\n         3. Move cousor on column, means you can put cursor on any character\r\n            of the column, not limit the first character.\r\n\r\n         4. If you don't like the default map, just modify the source.\r\n            The map code is on the bottom.\r\n\r\n         5. You can swap columns on multiple lines. \r\n            Swap column 1 and column 3 on five lines.\r\n\r\n            111  222  333  444  555        333  222  111  444  555\r\n            111  222  333  444  555        333  222  111  444  555\r\n            111  222  333  444  555 ---> 333  222  111  444  555\r\n            111  222  333  444  555        333  222  111  444  555\r\n            111  222  333  444  555        333  222  111  444  555\r\n\r\n            Step 1: select multiple lines in visual mode\r\n                          press V (upper case)\r\n                          and then use j or k to select lines\r\n            Step 2: call Swapcols like: \r\n                           :'<,'>Swapcols 1 3 \r\n                           (When you press :   '<,'> will come out automatically.)\r\n            Setp 3: press Enter to continue, and you will get the result.\r\n\r\n            Remember: the first column number is 1, not 0.","4":"         Swap columns, the columns are separated by blank.\r\n         Column maybe is word, or maybe not:\r\n            col1   col2   col3   col4   col5\r\n            command!  -nargs=*  -range  -complete=command\r\n\r\n         1. Move cursor on col1, and press  ]c  you will see:\r\n            col2   col1   col3   col4   col5\r\n\r\n         2. Move cursor on -range and press [c, you will see:\r\n            command!  -range  -nargs=*  -complete=command\r\n\r\n         3. Move cousor on column, means you can put cursor on any character\r\n            of the column, not limit the first character.\r\n\r\n         4. If you don't like the default map, just modify the source.\r\n            The map code is on the bottom.\r\n\r\n         5. You can swap columns on multiple lines. \r\n            Swap column 1 and column 3 on five lines.\r\n\r\n            111  222  333  444  555        333  222  111  444  555\r\n            111  222  333  444  555        333  222  111  444  555\r\n            111  222  333  444  555 ---> 333  222  111  444  555\r\n            111  222  333  444  555        333  222  111  444  555\r\n            111  222  333  444  555        333  222  111  444  555\r\n\r\n            Step 1: select multiple lines in visual mode\r\n                          press V (upper case)\r\n                          and then use j or k to select lines\r\n            Step 2: call Swapcols like: \r\n                           :'<,'>Swapcols 1 3 \r\n                           (When you press :   '<,'> will come out automatically.)\r\n            Setp 3: press Enter to continue, and you will get the result.\r\n\r\n            Remember: the first column number is 1, not 0.","install_details":"         Put this file in ~\/.vim\/plugin on *nix\r\n         Or put it in $vim\/vimfiles\/plugin on Windows","5":"         Put this file in ~\/.vim\/plugin on *nix\r\n         Or put it in $vim\/vimfiles\/plugin on Windows","first_name":"Tian","6":"Tian","last_name":"Huixiong","7":"Huixiong","releases":[{"0":"3708","vim_version":"7.0","1":"7.0","script_version":"2.2","2":"2.2","version_comment":"Define a user command, to make easier to use.","3":"Define a user command, to make easier to use.","package":"swapcol.vim","4":"swapcol.vim","src_id":"16370","5":"16370","creation_date":"1314439532","6":"1314439532"},{"0":"3708","vim_version":"7.0","1":"7.0","script_version":"2.1.1","2":"2.1.1","version_comment":"bug fixed","3":"bug fixed","package":"swapcol.vim","4":"swapcol.vim","src_id":"16358","5":"16358","creation_date":"1314337112","6":"1314337112"},{"0":"3708","vim_version":"7.0","1":"7.0","script_version":"2.1","2":"2.1","version_comment":"Swap two columns ( on one line or multiple lines )","3":"Swap two columns ( on one line or multiple lines )","package":"swapcol.vim","4":"swapcol.vim","src_id":"16349","5":"16349","creation_date":"1314293594","6":"1314293594"},{"0":"3708","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"swapcol.vim","4":"swapcol.vim","src_id":"16347","5":"16347","creation_date":"1314252693","6":"1314252693"}]},"3707":{"script_id":"3707","0":"3707","script_name":"lemon256","1":"lemon256","script_type":"color scheme","2":"color scheme","summary":"colorscheme for 256-color term","3":"colorscheme for 256-color term","description":"lemon256 is a colorscheme written for 256-color term only.\r\n\r\nIt uses  solarized ( https:\/\/github.com\/altercation\/vim-colors-solarized\/ ) as template and have some nice features.\r\nYou can get details in the file.\r\n\r\n* Screenshot: http:\/\/i.imgur.com\/wMDdo.png\r\n\r\n* Bitbucket: https:\/\/bitbucket.org\/vayn\/colorschemes\r\n\r\nlemon256 can work with other colorscheme like this:\r\n\r\n>>>\r\n    if has('gui_running')\r\n        colorscheme diablo3\r\n    else\r\n        colorscheme lemon256\r\n    endif\r\n<<<","4":"lemon256 is a colorscheme written for 256-color term only.\r\n\r\nIt uses  solarized ( https:\/\/github.com\/altercation\/vim-colors-solarized\/ ) as template and have some nice features.\r\nYou can get details in the file.\r\n\r\n* Screenshot: http:\/\/i.imgur.com\/wMDdo.png\r\n\r\n* Bitbucket: https:\/\/bitbucket.org\/vayn\/colorschemes\r\n\r\nlemon256 can work with other colorscheme like this:\r\n\r\n>>>\r\n    if has('gui_running')\r\n        colorscheme diablo3\r\n    else\r\n        colorscheme lemon256\r\n    endif\r\n<<<","install_details":"Just put the file to \"~\/.vim\/colors\" and copy\r\n\r\n>>>\r\n    colorscheme lemon256\r\n<<<\r\n\r\ninto your vimrc file","5":"Just put the file to \"~\/.vim\/colors\" and copy\r\n\r\n>>>\r\n    colorscheme lemon256\r\n<<<\r\n\r\ninto your vimrc file","first_name":"Vincent","6":"Vincent","last_name":"T.","7":"T.","releases":[{"0":"3707","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"lemon256.vim","4":"lemon256.vim","src_id":"16344","5":"16344","creation_date":"1314207492","6":"1314207492"}]},"3706":{"script_id":"3706","0":"3706","script_name":"obvious-resize","1":"obvious-resize","script_type":"utility","2":"utility","summary":"Resize Vim windows in an obvious way.","3":"Resize Vim windows in an obvious way.","description":"A plugin for easy resizing of Vim windows.\r\n\r\nJust add the following into your .vimrc file:\r\n\r\nnoremap <silent> <C-Up> :ObviousResizeUp<CR>\r\nnoremap <silent> <C-Down> :ObviousResizeDown<CR>\r\nnoremap <silent> <C-Left> :ObviousResizeLeft<CR>\r\nnoremap <silent> <C-Right> :ObviousResizeRight<CR>\r\n\r\nProject page: https:\/\/github.com\/talek\/obvious-resize","4":"A plugin for easy resizing of Vim windows.\r\n\r\nJust add the following into your .vimrc file:\r\n\r\nnoremap <silent> <C-Up> :ObviousResizeUp<CR>\r\nnoremap <silent> <C-Down> :ObviousResizeDown<CR>\r\nnoremap <silent> <C-Left> :ObviousResizeLeft<CR>\r\nnoremap <silent> <C-Right> :ObviousResizeRight<CR>\r\n\r\nProject page: https:\/\/github.com\/talek\/obvious-resize","install_details":"","5":"","first_name":"Alexandru","6":"Alexandru","last_name":"Tica","7":"Tica","releases":[{"0":"3706","vim_version":"7.0","1":"7.0","script_version":"1.1","2":"1.1","version_comment":"Bug fix.","3":"Bug fix.","package":"obvious-resize-1.1.zip","4":"obvious-resize-1.1.zip","src_id":"16405","5":"16405","creation_date":"1314732004","6":"1314732004"},{"0":"3706","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"obvious-resize-1.0.zip","4":"obvious-resize-1.0.zip","src_id":"16340","5":"16340","creation_date":"1314179733","6":"1314179733"}]},"3705":{"script_id":"3705","0":"3705","script_name":"Rcode","1":"Rcode","script_type":"utility","2":"utility","summary":"Run various types of code against current buffer","3":"Run various types of code against current buffer","description":"Rcode enables you to write short script to handle your text. It supports\r\nVimScript, Awk (via external command), Perl, Python 2 & 3, Ruby and Lua.\r\n\r\nUsage:\r\n\r\nSee also at the top of the plugin file as it's formatted better.\r\n\r\nChinese Version （中文版文档） https:\/\/blog.lilydjwg.me\/2011\/12\/21\/rcode-vim-2-0-released.31390.html\r\n\r\nCommands And Maps:\r\n:Rcode\t\tStart Rcode. Accept an argument as the language, eg:\r\n\t\tvim, awk, etc. Use <C-D> to see all available ones.\r\n\t\tA new buffer will be opened for you. Write your code\r\n\t\tin it.\r\n\t\tYou can give a range.\r\n\r\n:RcLoad {name}\tLoad a previous saved code snippet.\r\n      \t\t\"name\" should be in the form \"{lang}\/{filename}\" so\r\n      \t\tthat the script knows which language it's in. This is\r\n      \t\tdifferent from \":Save\" command.\r\n\t\tYou can give a range.\r\n\r\n:RcSelect\tList all available code snippets and you can choose\r\n      \t\tone by number\r\n\r\nIn Rcode buffer:\r\n\r\n<C-CR>\r\n:Run\t\tRun your code against the buffer you were.\r\n:Save {name}\tSave your code so you can later load it with\r\n      \t\t\":RcLoad\"\r\n\r\nShortcut:\r\nin Python, 'v' is the 'vim' module, and 'b' is the current buffer,\r\nin Lua, 'b' is the current buffer.\r\n\r\nSettings:\r\ng:Rcode_after\twhat to do after running your code.\r\n\t\t0 means to do noting, 1 means to close the code buffer\r\n\t\tand 2 will throw away your code besides closing the\r\n\t\tbuffer, or you code will be loaded next time you use\r\n\t\t\":Rcode\".\r\n\t\tDefault is 1.\r\n\r\ng:Rcode_snippet_path\tWhere you saved code snippets will lie.\r\n\t\t\tDefault is \"$HOME\/.vim\/rcode\"\r\n","4":"Rcode enables you to write short script to handle your text. It supports\r\nVimScript, Awk (via external command), Perl, Python 2 & 3, Ruby and Lua.\r\n\r\nUsage:\r\n\r\nSee also at the top of the plugin file as it's formatted better.\r\n\r\nChinese Version （中文版文档） https:\/\/blog.lilydjwg.me\/2011\/12\/21\/rcode-vim-2-0-released.31390.html\r\n\r\nCommands And Maps:\r\n:Rcode\t\tStart Rcode. Accept an argument as the language, eg:\r\n\t\tvim, awk, etc. Use <C-D> to see all available ones.\r\n\t\tA new buffer will be opened for you. Write your code\r\n\t\tin it.\r\n\t\tYou can give a range.\r\n\r\n:RcLoad {name}\tLoad a previous saved code snippet.\r\n      \t\t\"name\" should be in the form \"{lang}\/{filename}\" so\r\n      \t\tthat the script knows which language it's in. This is\r\n      \t\tdifferent from \":Save\" command.\r\n\t\tYou can give a range.\r\n\r\n:RcSelect\tList all available code snippets and you can choose\r\n      \t\tone by number\r\n\r\nIn Rcode buffer:\r\n\r\n<C-CR>\r\n:Run\t\tRun your code against the buffer you were.\r\n:Save {name}\tSave your code so you can later load it with\r\n      \t\t\":RcLoad\"\r\n\r\nShortcut:\r\nin Python, 'v' is the 'vim' module, and 'b' is the current buffer,\r\nin Lua, 'b' is the current buffer.\r\n\r\nSettings:\r\ng:Rcode_after\twhat to do after running your code.\r\n\t\t0 means to do noting, 1 means to close the code buffer\r\n\t\tand 2 will throw away your code besides closing the\r\n\t\tbuffer, or you code will be loaded next time you use\r\n\t\t\":Rcode\".\r\n\t\tDefault is 1.\r\n\r\ng:Rcode_snippet_path\tWhere you saved code snippets will lie.\r\n\t\t\tDefault is \"$HOME\/.vim\/rcode\"\r\n","install_details":"Put it in your ~\/.vim\/plugin.","5":"Put it in your ~\/.vim\/plugin.","first_name":"lilydjwg","6":"lilydjwg","last_name":" ","7":" ","releases":[{"0":"3705","vim_version":"7.0","1":"7.0","script_version":"2.0","2":"2.0","version_comment":"You can save the code now. ","3":"You can save the code now. ","package":"rcode.vim","4":"rcode.vim","src_id":"17095","5":"17095","creation_date":"1324478393","6":"1324478393"},{"0":"3705","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"rcode.vim","4":"rcode.vim","src_id":"16339","5":"16339","creation_date":"1314177604","6":"1314177604"}]},"3704":{"script_id":"3704","0":"3704","script_name":"Transcription Name Helper","1":"Transcription Name Helper","script_type":"ftplugin","2":"ftplugin","summary":"Allows the user to quickly switch between speakers whilst transcribing","3":"Allows the user to quickly switch between speakers whilst transcribing","description":"This script allows the user to switch to the next speaker by pressing <Tab> during transcription in insert mode. E.g.\r\n\r\n    INTERVIEWER: Blah blah blah?\r\n\r\nUser presses <Tab> and...\r\n\r\n    INTERVIEWER: Blah blah blah?\r\n\r\n    INTERVIEWEE1:\r\n\r\nTo change the names of the people, :let transcriptionID0 = \"firstperson\" , :let transcriptionID1 = \"second person\" etc.. Alternatively, change the default names by editing the appropriate variables in tra.vim.\r\n\r\nWhen <Tab> is pressed multiple times in a row, tra.vim replaces the previous transcriptionee's name.\r\n\r\nMultiple INTERVIEWEE's are supported as of v0.2. Simply press <Tab> multiple times and the current transcriptionee will change (up to g:maxPersons). To change the number of transcriptionees, simply :let maxPersons = people in interview. Currently, up to 5 transcriptionees are supported.\r\n\r\nv0.3 introduces 'modes' for multiple transcriptionees: tabspam, conversation and absolute. To change the transcriptionMode, press <F6>. Tabspam is described in the previous paragraph. Conversation allows <Tab> to toggle between INTERVIEWER and INTERVIEWEE1 and ` toggle between INTERVIEWEE2 and INTERVIEWEE1. Absolute yields: <Tab> = INTERVIEWER; <S-Tab> = INTERVIEWEE1, ` = INTERVIEWEE2; \u00c2\u00ac (or <S-`>) = INTERVIEWEE3.\r\n\r\nPS I just realized, those keys might not be ideal for a US keyboard. If you want them changing (I can't remember where ` and \u00c2\u00ac are on a US keyboard offhand) just write in the wiki about it","4":"This script allows the user to switch to the next speaker by pressing <Tab> during transcription in insert mode. E.g.\r\n\r\n    INTERVIEWER: Blah blah blah?\r\n\r\nUser presses <Tab> and...\r\n\r\n    INTERVIEWER: Blah blah blah?\r\n\r\n    INTERVIEWEE1:\r\n\r\nTo change the names of the people, :let transcriptionID0 = \"firstperson\" , :let transcriptionID1 = \"second person\" etc.. Alternatively, change the default names by editing the appropriate variables in tra.vim.\r\n\r\nWhen <Tab> is pressed multiple times in a row, tra.vim replaces the previous transcriptionee's name.\r\n\r\nMultiple INTERVIEWEE's are supported as of v0.2. Simply press <Tab> multiple times and the current transcriptionee will change (up to g:maxPersons). To change the number of transcriptionees, simply :let maxPersons = people in interview. Currently, up to 5 transcriptionees are supported.\r\n\r\nv0.3 introduces 'modes' for multiple transcriptionees: tabspam, conversation and absolute. To change the transcriptionMode, press <F6>. Tabspam is described in the previous paragraph. Conversation allows <Tab> to toggle between INTERVIEWER and INTERVIEWEE1 and ` toggle between INTERVIEWEE2 and INTERVIEWEE1. Absolute yields: <Tab> = INTERVIEWER; <S-Tab> = INTERVIEWEE1, ` = INTERVIEWEE2; \u00c2\u00ac (or <S-`>) = INTERVIEWEE3.\r\n\r\nPS I just realized, those keys might not be ideal for a US keyboard. If you want them changing (I can't remember where ` and \u00c2\u00ac are on a US keyboard offhand) just write in the wiki about it","install_details":"Add the following line to your .vimrc:\r\n\r\nfiletype plugin on\r\n\r\nthen put this file in your ~\/.vim\/ and it should work (with *.tra files).\r\n\r\n\r\nAlso, if you want to use a different extension for your transcription files, just rename tra.vim to yourfilename.vim.\r\n","5":"Add the following line to your .vimrc:\r\n\r\nfiletype plugin on\r\n\r\nthen put this file in your ~\/.vim\/ and it should work (with *.tra files).\r\n\r\n\r\nAlso, if you want to use a different extension for your transcription files, just rename tra.vim to yourfilename.vim.\r\n","first_name":"Nathanael","6":"Nathanael","last_name":"Farley","7":"Farley","releases":[{"0":"3704","vim_version":"7.3","1":"7.3","script_version":"0.3","2":"0.3","version_comment":"EmtpyLine behaviour improved. New 'modes' included for multiple people.","3":"EmtpyLine behaviour improved. New 'modes' included for multiple people.","package":"tra.zip","4":"tra.zip","src_id":"16432","5":"16432","creation_date":"1314967660","6":"1314967660"},{"0":"3704","vim_version":"7.3","1":"7.3","script_version":"0.2","2":"0.2","version_comment":"Added 'EmptyLine' behaviour. Multiple interviewee's now supported.","3":"Added 'EmptyLine' behaviour. Multiple interviewee's now supported.","package":"tra.zip","4":"tra.zip","src_id":"16363","5":"16363","creation_date":"1314353208","6":"1314353208"},{"0":"3704","vim_version":"7.3","1":"7.3","script_version":"0.1.1","2":"0.1.1","version_comment":"Totally forgot to include the ftdetect. Script will not work with tra files without it! The relevant ftdetect is now included.","3":"Totally forgot to include the ftdetect. Script will not work with tra files without it! The relevant ftdetect is now included.","package":"tra.zip","4":"tra.zip","src_id":"16332","5":"16332","creation_date":"1314093926","6":"1314093926"},{"0":"3704","vim_version":"7.3","1":"7.3","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"tra.vim","4":"tra.vim","src_id":"16330","5":"16330","creation_date":"1314065261","6":"1314065261"}]},"3703":{"script_id":"3703","0":"3703","script_name":"zim-syntax","1":"zim-syntax","script_type":"syntax","2":"syntax","summary":"Enable syntax highlighting for the Zim Wiki Syntax","3":"Enable syntax highlighting for the Zim Wiki Syntax","description":"This syntax definitions provide highlighting the common text objects used by the Zim Desktop Wiki (http:\/\/zim-wiki.org\/). Basically the Zim wiki syntax is the same Dokuwiki (http:\/\/www.dokuwiki.org\/dokuwiki) uses, but with some significant differences. So I decided to write this simple syntax file, for situations when you want to edit a Zim wiki page without the possibility to use Zim itself.\r\nYou can now also create Zim wiki pages by inserting a the typical Zim 0.4 file header by typing C-T C-Z or using the abbreviation 'zimhead'.","4":"This syntax definitions provide highlighting the common text objects used by the Zim Desktop Wiki (http:\/\/zim-wiki.org\/). Basically the Zim wiki syntax is the same Dokuwiki (http:\/\/www.dokuwiki.org\/dokuwiki) uses, but with some significant differences. So I decided to write this simple syntax file, for situations when you want to edit a Zim wiki page without the possibility to use Zim itself.\r\nYou can now also create Zim wiki pages by inserting a the typical Zim 0.4 file header by typing C-T C-Z or using the abbreviation 'zimhead'.","install_details":"Untar the zim.tar.gz into your vim folder (tar xf zim.tar.gz -C ~\/.vim\/) and enable it by :set syntax=zim from within VIM.","5":"Untar the zim.tar.gz into your vim folder (tar xf zim.tar.gz -C ~\/.vim\/) and enable it by :set syntax=zim from within VIM.","first_name":"S\u00c3\u00b6ren","6":"S\u00c3\u00b6ren","last_name":"K\u00c3\u00b6nig","7":"K\u00c3\u00b6nig","releases":[{"0":"3703","vim_version":"7.0","1":"7.0","script_version":"0.2","2":"0.2","version_comment":"added function for inserting Zim-stlye header","3":"added function for inserting Zim-stlye header","package":"zim.tar.gz","4":"zim.tar.gz","src_id":"17085","5":"17085","creation_date":"1324253007","6":"1324253007"},{"0":"3703","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"zim.vim","4":"zim.vim","src_id":"16327","5":"16327","creation_date":"1313978078","6":"1313978078"}]},"3702":{"script_id":"3702","0":"3702","script_name":"sql.vim","1":"sql.vim","script_type":"syntax","2":"syntax","summary":"Better SQL Syntax","3":"Better SQL Syntax","description":"Better SQL Syntax highlighting with errors.\r\n\r\nHighlights common error conditions. Only highlights types inside \"CREATE TABLE\" statements. Additions for SQLite.\r\n\r\nBased on existing SQL Syntax files.\r\n\r\nThis and more can be found at: https:\/\/github.com\/LStinson\/Vim\r\n\r\nI welcome any and all feedback. Please contact me at LoranceStinson AT Gmail....\r\nPlease be sure to put sql.vim in the subject so I know what you are emailing about.","4":"Better SQL Syntax highlighting with errors.\r\n\r\nHighlights common error conditions. Only highlights types inside \"CREATE TABLE\" statements. Additions for SQLite.\r\n\r\nBased on existing SQL Syntax files.\r\n\r\nThis and more can be found at: https:\/\/github.com\/LStinson\/Vim\r\n\r\nI welcome any and all feedback. Please contact me at LoranceStinson AT Gmail....\r\nPlease be sure to put sql.vim in the subject so I know what you are emailing about.","install_details":"Copy sql.vim to \"~\/.vim\/syntax\/\" and enjoy editing *.sql files.","5":"Copy sql.vim to \"~\/.vim\/syntax\/\" and enjoy editing *.sql files.","first_name":"Lorance","6":"Lorance","last_name":"Stinson","7":"Stinson","releases":[{"0":"3702","vim_version":"7.0","1":"7.0","script_version":"1.1","2":"1.1","version_comment":"Added more keywords and Oracle specific syntax (variables and commands).","3":"Added more keywords and Oracle specific syntax (variables and commands).","package":"sql.vim","4":"sql.vim","src_id":"17134","5":"17134","creation_date":"1325272274","6":"1325272274"},{"0":"3702","vim_version":"6.0","1":"6.0","script_version":"1","2":"1","version_comment":"Initial upload","3":"Initial upload","package":"sql.vim","4":"sql.vim","src_id":"16325","5":"16325","creation_date":"1313950953","6":"1313950953"}]},"3701":{"script_id":"3701","0":"3701","script_name":"fthook.vim","1":"fthook.vim","script_type":"utility","2":"utility","summary":"simplify filetype specific setting.","3":"simplify filetype specific setting.","description":"Puprpose~\r\nEnsure my favorite keymap is always available by overwriting plugin-defined\r\nkeymap with my buffer local keymap.\r\n\r\nI know this plugin is not perfect solution, but I think this still useful.\r\n\r\nPractical usecase~\r\nFor example, I use following keymap to move between windows.  \r\n>\r\n    nnoremap <silent> <C-h> :wincmd h<CR>\r\n    nnoremap <silent> <C-l> :wincmd l<CR>\r\n    nnoremap <silent> <C-k> :wincmd k<CR>\r\n    nnoremap <silent> <C-j> :wincmd j<CR>\r\n<\r\n\r\nWith this keymap, I can move window to window with <C-hlkj>.\r\nBut sometime, plugin I installed overwrite one of these keymap.  \r\nTo ensure `<C-hlkj>` combination is always available, set buffer local keymap \r\nafter plugin have set up their keymap.  \r\nThis could be done with `autocmd Filetype`, but setup this autocmd each time I\r\ninstall new plugin is nonsense.  \r\n\r\nTo do that, refer |fthook-examples| in help.\r\n","4":"Puprpose~\r\nEnsure my favorite keymap is always available by overwriting plugin-defined\r\nkeymap with my buffer local keymap.\r\n\r\nI know this plugin is not perfect solution, but I think this still useful.\r\n\r\nPractical usecase~\r\nFor example, I use following keymap to move between windows.  \r\n>\r\n    nnoremap <silent> <C-h> :wincmd h<CR>\r\n    nnoremap <silent> <C-l> :wincmd l<CR>\r\n    nnoremap <silent> <C-k> :wincmd k<CR>\r\n    nnoremap <silent> <C-j> :wincmd j<CR>\r\n<\r\n\r\nWith this keymap, I can move window to window with <C-hlkj>.\r\nBut sometime, plugin I installed overwrite one of these keymap.  \r\nTo ensure `<C-hlkj>` combination is always available, set buffer local keymap \r\nafter plugin have set up their keymap.  \r\nThis could be done with `autocmd Filetype`, but setup this autocmd each time I\r\ninstall new plugin is nonsense.  \r\n\r\nTo do that, refer |fthook-examples| in help.\r\n","install_details":"unzip.","5":"unzip.","first_name":"t9","6":"t9","last_name":"md","7":"md","releases":[{"0":"3701","vim_version":"7.2","1":"7.2","script_version":"0.3","2":"0.3","version_comment":"no functionality change.\r\nfix zip archiving mistake. sorry.\r\n","3":"no functionality change.\r\nfix zip archiving mistake. sorry.\r\n","package":"vim-fthook-0.3.zip","4":"vim-fthook-0.3.zip","src_id":"16329","5":"16329","creation_date":"1314022543","6":"1314022543"},{"0":"3701","vim_version":"7.0","1":"7.0","script_version":"0.2","2":"0.2","version_comment":"Initial upload","3":"Initial upload","package":"vim-fthook-0.2.zip","4":"vim-fthook-0.2.zip","src_id":"16322","5":"16322","creation_date":"1313941128","6":"1313941128"}]},"3700":{"script_id":"3700","0":"3700","script_name":"tryit.vim","1":"tryit.vim","script_type":"utility","2":"utility","summary":"Open scratch buffer to try idea.","3":"Open scratch buffer to try idea.","description":"*tryit.vim* is minimal utility for\r\n\r\n  * open scratch(=sandbox) file to try idea in that file.\r\n  * paste visually selected text to that scrach buffer.\r\n\r\nThats' all!\r\n\r\n\r\nI need workspace to try some idea when programming.\r\n\r\nWhen I am considering \"where to save\", \"what name should I name this file\",\r\nfor this type of file used merly as workspace , I consume limited brain\r\nresources for that.\r\n\r\nI usually use this plugin with combination of thinca's |quickrun|.\r\n\r\nquickrun:~\r\n  http:\/\/www.vim.org\/scripts\/script.php?script_id=3146\r\n\r\nwhile I read some source code, and have question for code fragment.\r\n\r\n\t1. select that code fragment.\r\n\t2. then `T`( my favorite keymap for <Plug>(tryit-this) )\r\n\t3. then |:Quickrun|.\r\n","4":"*tryit.vim* is minimal utility for\r\n\r\n  * open scratch(=sandbox) file to try idea in that file.\r\n  * paste visually selected text to that scrach buffer.\r\n\r\nThats' all!\r\n\r\n\r\nI need workspace to try some idea when programming.\r\n\r\nWhen I am considering \"where to save\", \"what name should I name this file\",\r\nfor this type of file used merly as workspace , I consume limited brain\r\nresources for that.\r\n\r\nI usually use this plugin with combination of thinca's |quickrun|.\r\n\r\nquickrun:~\r\n  http:\/\/www.vim.org\/scripts\/script.php?script_id=3146\r\n\r\nwhile I read some source code, and have question for code fragment.\r\n\r\n\t1. select that code fragment.\r\n\t2. then `T`( my favorite keymap for <Plug>(tryit-this) )\r\n\t3. then |:Quickrun|.\r\n","install_details":"unzip it\r\ntryit.vim does not provide any default keymap.\r\nUser need to configure keymap to quickly try idea(see help).","5":"unzip it\r\ntryit.vim does not provide any default keymap.\r\nUser need to configure keymap to quickly try idea(see help).","first_name":"t9","6":"t9","last_name":"md","7":"md","releases":[{"0":"3700","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"vim-tryit-1.0.zip","4":"vim-tryit-1.0.zip","src_id":"16319","5":"16319","creation_date":"1313938851","6":"1313938851"}]},"3699":{"script_id":"3699","0":"3699","script_name":"Premailer.vim","1":"Premailer.vim","script_type":"utility","2":"utility","summary":"Use Premailer in Vim.","3":"Use Premailer in Vim.","description":"Vim wrapper plugin for the Ruby script Premailer.\r\n\r\nUsage: open a HTML page and run :Premailer to get the email-friendly version.","4":"Vim wrapper plugin for the Ruby script Premailer.\r\n\r\nUsage: open a HTML page and run :Premailer to get the email-friendly version.","install_details":"Extract the archive to ~\/.vim on Linux\/MacOSX or $HOME\\vimfiles on Windows.","5":"Extract the archive to ~\/.vim on Linux\/MacOSX or $HOME\\vimfiles on Windows.","first_name":" ","6":" ","last_name":" ","7":" ","releases":[{"0":"3699","vim_version":"7.3","1":"7.3","script_version":"1.0.2","2":"1.0.2","version_comment":"Open-in-split behavior fix.","3":"Open-in-split behavior fix.","package":"premailer.vim.zip","4":"premailer.vim.zip","src_id":"16351","5":"16351","creation_date":"1314299494","6":"1314299494"}]},"3698":{"script_id":"3698","0":"3698","script_name":"html_emogrifier.vim","1":"html_emogrifier.vim","script_type":"ftplugin","2":"ftplugin","summary":"Create HTML email from HTML and linked CSS","3":"Create HTML email from HTML and linked CSS","description":"Inserts CSS rules from a stylesheet into a HTML page to create HTML email. Requires cURL and  a PHP-supported webserver.\r\n\r\n====================\r\nUsage\/Configuration:\r\n====================\r\n1. Copy the emogrifier\/ directory to your localhost's or your website's public directory.\r\n\r\n2. Define g:emogrifier_interface in your .vimrc with the location of the run.php script.\r\nExample:\r\nlet g:emogrifier_interface = 'http:\/\/localhost\/emogrifier\/run.php'\r\n\r\n3. Run :Emogrify on any HTML file with linked CSS to get an email-friendly version.\r\n\r\n4. The email-friendly version will be saved into the same directory as the original HTML file.","4":"Inserts CSS rules from a stylesheet into a HTML page to create HTML email. Requires cURL and  a PHP-supported webserver.\r\n\r\n====================\r\nUsage\/Configuration:\r\n====================\r\n1. Copy the emogrifier\/ directory to your localhost's or your website's public directory.\r\n\r\n2. Define g:emogrifier_interface in your .vimrc with the location of the run.php script.\r\nExample:\r\nlet g:emogrifier_interface = 'http:\/\/localhost\/emogrifier\/run.php'\r\n\r\n3. Run :Emogrify on any HTML file with linked CSS to get an email-friendly version.\r\n\r\n4. The email-friendly version will be saved into the same directory as the original HTML file.","install_details":"1. Extract the archive.\r\n2. Copy the ftplugin\/ directory to ~\/.vim on Linux\/MacOSX or $HOME\\vimfiles on Windows.\r\n3. Copy the emogrifier\/ directory to your localhost's or your website's public directory.\r\n4. Define g:emogrifier_interface in your .vimrc with the location of the run.php script.","5":"1. Extract the archive.\r\n2. Copy the ftplugin\/ directory to ~\/.vim on Linux\/MacOSX or $HOME\\vimfiles on Windows.\r\n3. Copy the emogrifier\/ directory to your localhost's or your website's public directory.\r\n4. Define g:emogrifier_interface in your .vimrc with the location of the run.php script.","first_name":" ","6":" ","last_name":" ","7":" ","releases":[{"0":"3698","vim_version":"7.3","1":"7.3","script_version":"1.0.1","2":"1.0.1","version_comment":"Move script to autoload. Better pattern matching.","3":"Move script to autoload. Better pattern matching.","package":"emogrifier.vim.zip","4":"emogrifier.vim.zip","src_id":"16337","5":"16337","creation_date":"1314145468","6":"1314145468"}]},"3697":{"script_id":"3697","0":"3697","script_name":"cssbaseline.vim","1":"cssbaseline.vim","script_type":"utility","2":"utility","summary":"Build empty CSS blocks from HTML.","3":"Build empty CSS blocks from HTML.","description":"Generate empty CSS blocks from HTML. Requires cURL.\r\n\r\n====================\r\nUsage:\r\n====================\r\n+ Select a block of HTML from the opening to the closing tag and type either :Baseline or :Baseline1.\r\n\r\n+ The retrieved CSS will be copied to your clipboard (* register), ready to be pasted.","4":"Generate empty CSS blocks from HTML. Requires cURL.\r\n\r\n====================\r\nUsage:\r\n====================\r\n+ Select a block of HTML from the opening to the closing tag and type either :Baseline or :Baseline1.\r\n\r\n+ The retrieved CSS will be copied to your clipboard (* register), ready to be pasted.","install_details":"Extract the archive to ~\/.vim on Linux\/MacOSX or $HOME\\vimfiles on Windows.","5":"Extract the archive to ~\/.vim on Linux\/MacOSX or $HOME\\vimfiles on Windows.","first_name":" ","6":" ","last_name":" ","7":" ","releases":[{"0":"3697","vim_version":"7.3","1":"7.3","script_version":"1.0.2","2":"1.0.2","version_comment":"Small fix for self-closing HTML elements.","3":"Small fix for self-closing HTML elements.","package":"cssbaseline.vim.zip","4":"cssbaseline.vim.zip","src_id":"16352","5":"16352","creation_date":"1314299503","6":"1314299503"}]},"3696":{"script_id":"3696","0":"3696","script_name":"prefixer.vim","1":"prefixer.vim","script_type":"utility","2":"utility","summary":"Add browser prefixes to CSS3 properties.","3":"Add browser prefixes to CSS3 properties.","description":"A simple plugin to help adding browser prefixes to CSS3 properties. Requires cURL.\r\n\r\n====================\r\nUsage:\r\n====================\r\n+ Select some CSS in visual mode then type either :Prefixer, :Prefixer1 or :Prefixer2.\r\n\r\n+ When using :Prefixer or :Prefixer2 in visual mode you have to select entire code blocks, i.e. from starting { to ending }.\r\n\r\n+ Without selecting anything, in normal mode type :Prefixer, :Prefixer1a or :Prefixer2a to process entire file; or :Prefixer1 to process current line.","4":"A simple plugin to help adding browser prefixes to CSS3 properties. Requires cURL.\r\n\r\n====================\r\nUsage:\r\n====================\r\n+ Select some CSS in visual mode then type either :Prefixer, :Prefixer1 or :Prefixer2.\r\n\r\n+ When using :Prefixer or :Prefixer2 in visual mode you have to select entire code blocks, i.e. from starting { to ending }.\r\n\r\n+ Without selecting anything, in normal mode type :Prefixer, :Prefixer1a or :Prefixer2a to process entire file; or :Prefixer1 to process current line.","install_details":"Extract the archive to ~\/.vim on Linux\/MacOSX or $HOME\\vimfiles on Windows.","5":"Extract the archive to ~\/.vim on Linux\/MacOSX or $HOME\\vimfiles on Windows.","first_name":" ","6":" ","last_name":" ","7":" ","releases":[{"0":"3696","vim_version":"7.3","1":"7.3","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"prefixer.zip","4":"prefixer.zip","src_id":"16304","5":"16304","creation_date":"1313832817","6":"1313832817"}]},"3695":{"script_id":"3695","0":"3695","script_name":"commentary.vim","1":"commentary.vim","script_type":"utility","2":"utility","summary":"Comment stuff out; takes a motion as a target","3":"Comment stuff out; takes a motion as a target","description":"Comment stuff out.  Use gcc to comment out a line (takes a count), gc to comment out the target of a motion (for example, gcap to comment out a paragraph), and gc in visual mode to comment out the selection.  That's it.\r\n\r\nI wrote this because 5 years after Vim added support for mapping an operator, I still couldn't find a commenting plugin that leveraged that feature (I overlooked vimscript #1173).  Striving for minimalism, the first version weighs in at just 35 lines of code.\r\n\r\nOh, and it uncomments, too.  The above maps actually toggle, and `gcu` uncomments a set of adjacent commented lines.  Install repeat.vim, vimscript #2136, to enable repeating with . the line commenting map gcu.  (The other maps are repeatable without it.)\r\n\r\nhttps:\/\/github.com\/tpope\/vim-commentary","4":"Comment stuff out.  Use gcc to comment out a line (takes a count), gc to comment out the target of a motion (for example, gcap to comment out a paragraph), and gc in visual mode to comment out the selection.  That's it.\r\n\r\nI wrote this because 5 years after Vim added support for mapping an operator, I still couldn't find a commenting plugin that leveraged that feature (I overlooked vimscript #1173).  Striving for minimalism, the first version weighs in at just 35 lines of code.\r\n\r\nOh, and it uncomments, too.  The above maps actually toggle, and `gcu` uncomments a set of adjacent commented lines.  Install repeat.vim, vimscript #2136, to enable repeating with . the line commenting map gcu.  (The other maps are repeatable without it.)\r\n\r\nhttps:\/\/github.com\/tpope\/vim-commentary","install_details":"You know the drill.","5":"You know the drill.","first_name":"Tim","6":"Tim","last_name":"Pope","7":"Pope","releases":[{"0":"3695","vim_version":"7.0","1":"7.0","script_version":"1.3","2":"1.3","version_comment":"Provide :Commentary command.\r\nProvide gc text object.\r\nSupport comments with no leading space.\r\nPreserve whitespace in b:commentary_format.\r\nAllow disabling backslash maps.\r\nFix count with linewise map.\r\nDon't trigger modelines after commenting.\r\nDeprecation warnings.","3":"Provide :Commentary command.\r\nProvide gc text object.\r\nSupport comments with no leading space.\r\nPreserve whitespace in b:commentary_format.\r\nAllow disabling backslash maps.\r\nFix count with linewise map.\r\nDon't trigger modelines after commenting.\r\nDeprecation warnings.","package":"commentary.zip","4":"commentary.zip","src_id":"24002","5":"24002","creation_date":"1455222398","6":"1455222398"},{"0":"3695","vim_version":"7.0","1":"7.0","script_version":"1.2","2":"1.2","version_comment":"Switch official interface from \\\\ to gc. \\\\ still works.\r\nAllow overriding 'commentstring' with b:commentary_format.\r\nAdd User CommentaryPost callback.","3":"Switch official interface from \\\\ to gc. \\\\ still works.\r\nAllow overriding 'commentstring' with b:commentary_format.\r\nAdd User CommentaryPost callback.","package":"commentary.zip","4":"commentary.zip","src_id":"21594","5":"21594","creation_date":"1394478214","6":"1394478214"},{"0":"3695","vim_version":"7.0","1":"7.0","script_version":"1.1","2":"1.1","version_comment":"Smarter indentation handling.\nAlways pad with whitespace.\nSupport nesting: \/* \/1* abc *1\/ *\/.\nSupport custom maps.","3":"Smarter indentation handling.\nAlways pad with whitespace.\nSupport nesting: \/* \/1* abc *1\/ *\/.\nSupport custom maps.","package":"commentary.zip","4":"commentary.zip","src_id":"16386","5":"16386","creation_date":"1314501610","6":"1314501610"},{"0":"3695","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"commentary.zip","4":"commentary.zip","src_id":"16309","5":"16309","creation_date":"1313859460","6":"1313859460"}]},"3694":{"script_id":"3694","0":"3694","script_name":"enablelvimrc.vim","1":"enablelvimrc.vim","script_type":"utility","2":"utility","summary":"load a .lvimrc when starting vim if it exists.","3":"load a .lvimrc when starting vim if it exists.","description":"enable project-specified vim settings in a .lvimrc.","4":"enable project-specified vim settings in a .lvimrc.","install_details":"install in ~\/.vim\/plugin\/","5":"install in ~\/.vim\/plugin\/","first_name":"joel","6":"joel","last_name":"hansson","7":"hansson","releases":[{"0":"3694","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"enablelvimrc.tar.gz","4":"enablelvimrc.tar.gz","src_id":"16298","5":"16298","creation_date":"1313749105","6":"1313749105"}]},"3693":{"script_id":"3693","0":"3693","script_name":"FixCSS.vim","1":"FixCSS.vim","script_type":"utility","2":"utility","summary":"Add whitespace to junk CSS files","3":"Add whitespace to junk CSS files","description":"This function makes \"junk\" CSS (little or no whitespace) somewhat readable by adding newlines after '{', '}', and ';' characters. It also inserts a single space before every '{'.\r\n\r\nExample of junk CSS: http:\/\/imgs.xkcd.com\/s\/c40a9f8.css\r\nWhat it looks like after :Fixcss : https:\/\/gist.github.com\/1155063\r\n\r\nYou can put the function in your .vimrc or save the script in .vim\/scripts\r\n\r\nUpdated version: https:\/\/github.com\/dbb\/vim\/raw\/master\/FixCSS.vim","4":"This function makes \"junk\" CSS (little or no whitespace) somewhat readable by adding newlines after '{', '}', and ';' characters. It also inserts a single space before every '{'.\r\n\r\nExample of junk CSS: http:\/\/imgs.xkcd.com\/s\/c40a9f8.css\r\nWhat it looks like after :Fixcss : https:\/\/gist.github.com\/1155063\r\n\r\nYou can put the function in your .vimrc or save the script in .vim\/scripts\r\n\r\nUpdated version: https:\/\/github.com\/dbb\/vim\/raw\/master\/FixCSS.vim","install_details":"curl -O https:\/\/github.com\/dbb\/vim\/raw\/master\/FixCSS.vim","5":"curl -O https:\/\/github.com\/dbb\/vim\/raw\/master\/FixCSS.vim","first_name":"Daniel","6":"Daniel","last_name":"B","7":"B","releases":[{"0":"3693","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"FixCSS.vim","4":"FixCSS.vim","src_id":"16296","5":"16296","creation_date":"1313698633","6":"1313698633"}]},"3692":{"script_id":"3692","0":"3692","script_name":"quickhl.vim","1":"quickhl.vim","script_type":"utility","2":"utility","summary":"Quickly highlight multiple word.","3":"Quickly highlight multiple word.","description":"quickhl.vim support highlight for\r\n\r\n* multiple keywords manually specified via command or keymap.\r\n  also provide operator for highlight.\r\n* `tag` in ctags generated file(defult, underlined)\r\n* automatically higlight word under cursor(=`<cword>`).\r\n\r\nquickhl.vim not provide any keymap by default(its my preference)\r\nSee help.\r\n\r\n### Github\r\nhttps:\/\/github.com\/t9md\/vim-quickhl\r\n\r\n### ScreenCast\r\nhttp:\/\/www.youtube.com\/watch?v=W_XJlTbuoyI","4":"quickhl.vim support highlight for\r\n\r\n* multiple keywords manually specified via command or keymap.\r\n  also provide operator for highlight.\r\n* `tag` in ctags generated file(defult, underlined)\r\n* automatically higlight word under cursor(=`<cword>`).\r\n\r\nquickhl.vim not provide any keymap by default(its my preference)\r\nSee help.\r\n\r\n### Github\r\nhttps:\/\/github.com\/t9md\/vim-quickhl\r\n\r\n### ScreenCast\r\nhttp:\/\/www.youtube.com\/watch?v=W_XJlTbuoyI","install_details":"","5":"","first_name":"t9","6":"t9","last_name":"md","7":"md","releases":[{"0":"3692","vim_version":"7.2","1":"7.2","script_version":"1.0","2":"1.0","version_comment":"tag highlight, support.\r\nseveral bugfix and improvement.","3":"tag highlight, support.\r\nseveral bugfix and improvement.","package":"vim-quickhl-1.0.zip","4":"vim-quickhl-1.0.zip","src_id":"20960","5":"20960","creation_date":"1382795791","6":"1382795791"},{"0":"3692","vim_version":"7.2","1":"7.2","script_version":"0.4","2":"0.4","version_comment":"fix some compatibility issue.\r\nand  fix required Vim version to 7.2.\r\nv7.0 don't have getmaches() so, not work.\r\nv7.1 work in some case, but I'll support and test for v7.2 or later.","3":"fix some compatibility issue.\r\nand  fix required Vim version to 7.2.\r\nv7.0 don't have getmaches() so, not work.\r\nv7.1 work in some case, but I'll support and test for v7.2 or later.","package":"vim-quickhl-0.4.zip","4":"vim-quickhl-0.4.zip","src_id":"16315","5":"16315","creation_date":"1313919621","6":"1313919621"},{"0":"3692","vim_version":"7.0","1":"7.0","script_version":"0.3","2":"0.3","version_comment":"Initial upload","3":"Initial upload","package":"vim-quickhl-0.3.zip","4":"vim-quickhl-0.3.zip","src_id":"16289","5":"16289","creation_date":"1313599813","6":"1313599813"}]},"3691":{"script_id":"3691","0":"3691","script_name":"annotatedmarks","1":"annotatedmarks","script_type":"utility","2":"utility","summary":"Enhancing the built-in marks functionality of vim.","3":"Enhancing the built-in marks functionality of vim.","description":"Vim script for enhancing the built-in marks functionality of vim. \r\n\r\nIt gives you a chance to associate some meaningful annotation with a particular mark,\r\nthus decreases the possibility of you getting lost amongst a large amount of codes.\r\nAlso, it keeps track of which marks to use automatically: you don't have specify the\r\nname of mark. It uses global marks (A-Z) and tries to use an empty mark when possible.\r\nThe first mark you add would be A, next would be B, etc. If all marks are used, it'll\r\nsearch for an least used one (provided that you use THIS script for jumping to it) and\r\noverwrite it.\r\nThe information about marks are persistent so restarting Vim won't affect them.\r\n\r\nUsage:\r\nPretty straight forward stuff.\r\nAfter installation (drop it in $RUNTIME\/plugin), <Leader>M will add a new mark. You'll\r\nbe prompted for a comment on this mark.\r\n:Amarks would list all marks known to this script and let you choose one to jump to.\r\n\r\nConfiguration:\r\ng:am_persistent_file. String. Defines the file that this script writes to between vim sessions.\r\ng:am_use_popup_menu. 1 or 0. If it's 1, popup menu would be used, otherwise, echo would be used. ","4":"Vim script for enhancing the built-in marks functionality of vim. \r\n\r\nIt gives you a chance to associate some meaningful annotation with a particular mark,\r\nthus decreases the possibility of you getting lost amongst a large amount of codes.\r\nAlso, it keeps track of which marks to use automatically: you don't have specify the\r\nname of mark. It uses global marks (A-Z) and tries to use an empty mark when possible.\r\nThe first mark you add would be A, next would be B, etc. If all marks are used, it'll\r\nsearch for an least used one (provided that you use THIS script for jumping to it) and\r\noverwrite it.\r\nThe information about marks are persistent so restarting Vim won't affect them.\r\n\r\nUsage:\r\nPretty straight forward stuff.\r\nAfter installation (drop it in $RUNTIME\/plugin), <Leader>M will add a new mark. You'll\r\nbe prompted for a comment on this mark.\r\n:Amarks would list all marks known to this script and let you choose one to jump to.\r\n\r\nConfiguration:\r\ng:am_persistent_file. String. Defines the file that this script writes to between vim sessions.\r\ng:am_use_popup_menu. 1 or 0. If it's 1, popup menu would be used, otherwise, echo would be used. ","install_details":"Drop it inside ~\/.vim\/plugin","5":"Drop it inside ~\/.vim\/plugin","first_name":"Wenzhi","6":"Wenzhi","last_name":"Liang","7":"Liang","releases":[{"0":"3691","vim_version":"5.7","1":"5.7","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"annotatedmarks.vim","4":"annotatedmarks.vim","src_id":"16244","5":"16244","creation_date":"1313146726","6":"1313146726"}]},"3690":{"script_id":"3690","0":"3690","script_name":"golden-ratio","1":"golden-ratio","script_type":"utility","2":"utility","summary":"Resize windows automatically using the Golden Ratio","3":"Resize windows automatically using the Golden Ratio","description":"When working with many windows at the same time, each window has a size that is not convenient for editing.\r\n\r\ngolden-ratio helps on this issue by resizing automatically the windows you are working on to the size specified in the \"Golden Ratio\". The window that has the main focus will have the perfect size for editing, while the ones that are not being actively edited will be re-sized to a smaller size that doesn't get in the way, but at the same time will be readable enough to know it's content.\r\n\r\nRepository: http:\/\/www.github.com\/roman\/golden-ratio","4":"When working with many windows at the same time, each window has a size that is not convenient for editing.\r\n\r\ngolden-ratio helps on this issue by resizing automatically the windows you are working on to the size specified in the \"Golden Ratio\". The window that has the main focus will have the perfect size for editing, while the ones that are not being actively edited will be re-sized to a smaller size that doesn't get in the way, but at the same time will be readable enough to know it's content.\r\n\r\nRepository: http:\/\/www.github.com\/roman\/golden-ratio","install_details":"Install using pathogen.vim \r\n\r\nhttp:\/\/www.vim.org\/scripts\/script.php?script_id=2332","5":"Install using pathogen.vim \r\n\r\nhttp:\/\/www.vim.org\/scripts\/script.php?script_id=2332","first_name":"Roman","6":"Roman","last_name":"Gonzalez","7":"Gonzalez","releases":[{"0":"3690","vim_version":"7.0","1":"7.0","script_version":"0.0.5","2":"0.0.5","version_comment":"New release respects nowrap setting on ignored\/focused windows. Previously it would put an specific one, not respecting user settings.","3":"New release respects nowrap setting on ignored\/focused windows. Previously it would put an specific one, not respecting user settings.","package":"golden-ratio-0.0.5.tar.gz","4":"golden-ratio-0.0.5.tar.gz","src_id":"18723","5":"18723","creation_date":"1349045526","6":"1349045526"},{"0":"3690","vim_version":"7.3","1":"7.3","script_version":"0.0.4","2":"0.0.4","version_comment":"* Adding command for toggling functionality\r\n* Adding command to re-size window manually\r\n\r\n","3":"* Adding command for toggling functionality\r\n* Adding command to re-size window manually\r\n\r\n","package":"golden-ratio.tar.gz","4":"golden-ratio.tar.gz","src_id":"16280","5":"16280","creation_date":"1313519943","6":"1313519943"},{"0":"3690","vim_version":"7.3","1":"7.3","script_version":"0.0.3","2":"0.0.3","version_comment":"Adding suggestions made by Steve Losh. \r\n\r\n* set nowrap on unfocused windows and wrap on the focused one\r\n* better (even) resizing of unfocused windows\r\n* removing the <LEADER>g auto binding","3":"Adding suggestions made by Steve Losh. \r\n\r\n* set nowrap on unfocused windows and wrap on the focused one\r\n* better (even) resizing of unfocused windows\r\n* removing the <LEADER>g auto binding","package":"golden-ratio.tar.gz","4":"golden-ratio.tar.gz","src_id":"16271","5":"16271","creation_date":"1313450096","6":"1313450096"},{"0":"3690","vim_version":"7.3","1":"7.3","script_version":"0.0.2","2":"0.0.2","version_comment":"Adding improvements from ujihisa and adding new code standards","3":"Adding improvements from ujihisa and adding new code standards","package":"golden-ratio.tar.gz","4":"golden-ratio.tar.gz","src_id":"16246","5":"16246","creation_date":"1313164243","6":"1313164243"},{"0":"3690","vim_version":"7.3","1":"7.3","script_version":"0.0.1","2":"0.0.1","version_comment":"Initial upload","3":"Initial upload","package":"golden-ratio.tar.gz","4":"golden-ratio.tar.gz","src_id":"16240","5":"16240","creation_date":"1313101769","6":"1313101769"}]},"3689":{"script_id":"3689","0":"3689","script_name":"Ambient Color Scheme","1":"Ambient Color Scheme","script_type":"color scheme","2":"color scheme","summary":"color scheme based off of Ubuntu's Ambiance","3":"color scheme based off of Ubuntu's Ambiance","description":"Threw together this color scheme loosely derived from Mustang to better match the Ubuntu Ambiance colors. I also used Shawn Biddle's script to add 256 color terminal support, which didn't come out too awful.\r\n\r\nScreenshot: http:\/\/i.imgur.com\/vuggU.png\r\n\r\nConversion tool: http:\/\/shawncplus.github.com\/Vim-toCterm\/","4":"Threw together this color scheme loosely derived from Mustang to better match the Ubuntu Ambiance colors. I also used Shawn Biddle's script to add 256 color terminal support, which didn't come out too awful.\r\n\r\nScreenshot: http:\/\/i.imgur.com\/vuggU.png\r\n\r\nConversion tool: http:\/\/shawncplus.github.com\/Vim-toCterm\/","install_details":"Put this file in your .vim\/colors\/ directory.","5":"Put this file in your .vim\/colors\/ directory.","first_name":"Kevin","6":"Kevin","last_name":"Hamer","7":"Hamer","releases":[{"0":"3689","vim_version":"7.0","1":"7.0","script_version":"1.2","2":"1.2","version_comment":"Slight changes to the shades of blue and green used.","3":"Slight changes to the shades of blue and green used.","package":"ambient.vim","4":"ambient.vim","src_id":"16989","5":"16989","creation_date":"1322492733","6":"1322492733"},{"0":"3689","vim_version":"6.0","1":"6.0","script_version":"1.1.1","2":"1.1.1","version_comment":"Quick fix for support for cterm (256-terminals.)","3":"Quick fix for support for cterm (256-terminals.)","package":"ambient.vim","4":"ambient.vim","src_id":"16223","5":"16223","creation_date":"1312922982","6":"1312922982"},{"0":"3689","vim_version":"6.0","1":"6.0","script_version":"1.1","2":"1.1","version_comment":"Removed the darker orange; moved the lighter orange to its place, and added an even lighter, software, sunburst-yellow-orange.","3":"Removed the darker orange; moved the lighter orange to its place, and added an even lighter, software, sunburst-yellow-orange.","package":"ambient.vim","4":"ambient.vim","src_id":"16222","5":"16222","creation_date":"1312922467","6":"1312922467"},{"0":"3689","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"ambient.vim","4":"ambient.vim","src_id":"16221","5":"16221","creation_date":"1312916618","6":"1312916618"}]},"3688":{"script_id":"3688","0":"3688","script_name":"Rst edit block in tab","1":"Rst edit block in tab","script_type":"utility","2":"utility","summary":"Opens a particular reST directive block in a new tab","3":"Opens a particular reST directive block in a new tab","description":"This script allows you to edit the contents of an reST directive block in a new tab.\r\n\r\nPut your cursor in or on the block and hit \\e. A new tab will open with just the content of the block. The previous buffer will be set nomodifiable. When you are done, hit q (or you can change the key) and the content will be replaced back in to the original buffer.","4":"This script allows you to edit the contents of an reST directive block in a new tab.\r\n\r\nPut your cursor in or on the block and hit \\e. A new tab will open with just the content of the block. The previous buffer will be set nomodifiable. When you are done, hit q (or you can change the key) and the content will be replaced back in to the original buffer.","install_details":"Copy to plugin\/","5":"Copy to plugin\/","first_name":"Owen","6":"Owen","last_name":"H","7":"H","releases":[{"0":"3688","vim_version":"7.0","1":"7.0","script_version":"0.95","2":"0.95","version_comment":"Initial upload","3":"Initial upload","package":"block-edit.vim","4":"block-edit.vim","src_id":"16215","5":"16215","creation_date":"1312838777","6":"1312838777"}]},"3687":{"script_id":"3687","0":"3687","script_name":"Calm Breeze","1":"Calm Breeze","script_type":"color scheme","2":"color scheme","summary":"A calming breeze of colors for the heat of code","3":"A calming breeze of colors for the heat of code","description":"A simple, calming, color scheme for the heat of code. Works best in GUI settings, screenshot can be found at http:\/\/imgur.com\/I3JbE.","4":"A simple, calming, color scheme for the heat of code. Works best in GUI settings, screenshot can be found at http:\/\/imgur.com\/I3JbE.","install_details":"Simply add to your .vim\/colors\/ directory.","5":"Simply add to your .vim\/colors\/ directory.","first_name":"Jonas M","6":"Jonas M","last_name":"Luster","7":"Luster","releases":[{"0":"3687","vim_version":"7.0","1":"7.0","script_version":"1.1","2":"1.1","version_comment":"Added colors for conceal to overcome the unfortunate grey on grey default.","3":"Added colors for conceal to overcome the unfortunate grey on grey default.","package":"calmbreeze.vim","4":"calmbreeze.vim","src_id":"16283","5":"16283","creation_date":"1313532461","6":"1313532461"},{"0":"3687","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"calmbreeze.vim","4":"calmbreeze.vim","src_id":"16209","5":"16209","creation_date":"1312735366","6":"1312735366"}]},"3686":{"script_id":"3686","0":"3686","script_name":"RegImap","1":"RegImap","script_type":"utility","2":"utility","summary":"Plugin for automatically execute regular expression substitutes in insert mode","3":"Plugin for automatically execute regular expression substitutes in insert mode","description":"RegImap plugin contains some interesting idea about expanding key sequences\r\naccording to regular expression patterns. \r\n\r\nBut writing such patterns is quite difficult and now I prefer neocomplcache \r\n(http:\/\/www.vim.org\/scripts\/script.php?script_id=2620) plugin.\r\n","4":"RegImap plugin contains some interesting idea about expanding key sequences\r\naccording to regular expression patterns. \r\n\r\nBut writing such patterns is quite difficult and now I prefer neocomplcache \r\n(http:\/\/www.vim.org\/scripts\/script.php?script_id=2620) plugin.\r\n","install_details":"Install in your .vim directory \r\nRead help","5":"Install in your .vim directory \r\nRead help","first_name":"Artem","6":"Artem","last_name":"Shcherbina","7":"Shcherbina","releases":[{"0":"3686","vim_version":"7.0","1":"7.0","script_version":"0.54","2":"0.54","version_comment":"zip version","3":"zip version","package":"RegImap.zip","4":"RegImap.zip","src_id":"16238","5":"16238","creation_date":"1313082280","6":"1313082280"},{"0":"3686","vim_version":"7.0","1":"7.0","script_version":"0.54","2":"0.54","version_comment":" - Added PlaceHolder highlighting\r\n - Added CursorPH\r\n - Fixed small bugs","3":" - Added PlaceHolder highlighting\r\n - Added CursorPH\r\n - Fixed small bugs","package":"RegImap.vmb","4":"RegImap.vmb","src_id":"16237","5":"16237","creation_date":"1313071324","6":"1313071324"},{"0":"3686","vim_version":"7.0","1":"7.0","script_version":"0.53","2":"0.53","version_comment":"- Added use of InsertCharPre autocommand if you have patch196\r\n- Refactored code, fixed small bugs","3":"- Added use of InsertCharPre autocommand if you have patch196\r\n- Refactored code, fixed small bugs","package":"RegImap.vmb","4":"RegImap.vmb","src_id":"16231","5":"16231","creation_date":"1313004187","6":"1313004187"},{"0":"3686","vim_version":"7.0","1":"7.0","script_version":"0.52","2":"0.52","version_comment":" - Fixed sourcing algorithm (thanks to Alexey Radkov)\r\n - Added ReloadRegImaps function\r\n - Added g:RegImap_ to settings names\r\n - updated help","3":" - Fixed sourcing algorithm (thanks to Alexey Radkov)\r\n - Added ReloadRegImaps function\r\n - Added g:RegImap_ to settings names\r\n - updated help","package":"RegImap.vmb","4":"RegImap.vmb","src_id":"16218","5":"16218","creation_date":"1312877565","6":"1312877565"},{"0":"3686","vim_version":"7.0","1":"7.0","script_version":"0.51","2":"0.51","version_comment":"Fixed path detection. Now it works","3":"Fixed path detection. Now it works","package":"RegImap.vba","4":"RegImap.vba","src_id":"16211","5":"16211","creation_date":"1312785981","6":"1312785981"},{"0":"3686","vim_version":"7.0","1":"7.0","script_version":"0.5","2":"0.5","version_comment":"Initial upload","3":"Initial upload","package":"RegImap.vba","4":"RegImap.vba","src_id":"16208","5":"16208","creation_date":"1312660808","6":"1312660808"}]},"3685":{"script_id":"3685","0":"3685","script_name":"werks.vim","1":"werks.vim","script_type":"color scheme","2":"color scheme","summary":"-","3":"-","description":"-\r\n","4":"-\r\n","install_details":"-\r\n","5":"-\r\n","first_name":"B","6":"B","last_name":"M","7":"M","releases":[{"0":"3685","vim_version":"7.0","1":"7.0","script_version":"1.3","2":"1.3","version_comment":"-","3":"-","package":"werks.vim","4":"werks.vim","src_id":"27957","5":"27957","creation_date":"1646616935","6":"1646616935"}]},"3684":{"script_id":"3684","0":"3684","script_name":"ctags_cache","1":"ctags_cache","script_type":"ftplugin","2":"ftplugin","summary":"generate and cache tags for C language uses ctags","3":"generate and cache tags for C language uses ctags","description":"project on github.com: https:\/\/github.com\/abadcafe\/ctags_cache\r\n\r\nctags_cache is a vim plugin which can generate tags for C language uses ctags, then cache the tags in memory.\r\n\r\nThus, you don't need any tags file!\r\n\r\nThe plugin will update the cache while you call the :w command. Moreover, the header files which include by you current editing file will send to ctags too. Because ctags parse local variables not very good, so the plugin do the works itself(use regular expression.), it can extract local variables and function arguments exactly.\r\n\r\nIt is excellent, isn't it? The story is not end, thanks to python, the plugin uses threads so you almost can not feel the delay caused by parsing files when you coding!\r\n\r\nCommand\r\n\r\n:SetIncludeList path-of-include-dir1 path-of-include-dir2 ...\r\n\r\n:SetIncludeList\r\n\r\nthe command with no arguments sets no Include dir, thus only header files in the dir of current file will be parsed.\r\n\r\nTodo\r\n\r\nThe plugin is not test in windows, I guess it can work.","4":"project on github.com: https:\/\/github.com\/abadcafe\/ctags_cache\r\n\r\nctags_cache is a vim plugin which can generate tags for C language uses ctags, then cache the tags in memory.\r\n\r\nThus, you don't need any tags file!\r\n\r\nThe plugin will update the cache while you call the :w command. Moreover, the header files which include by you current editing file will send to ctags too. Because ctags parse local variables not very good, so the plugin do the works itself(use regular expression.), it can extract local variables and function arguments exactly.\r\n\r\nIt is excellent, isn't it? The story is not end, thanks to python, the plugin uses threads so you almost can not feel the delay caused by parsing files when you coding!\r\n\r\nCommand\r\n\r\n:SetIncludeList path-of-include-dir1 path-of-include-dir2 ...\r\n\r\n:SetIncludeList\r\n\r\nthe command with no arguments sets no Include dir, thus only header files in the dir of current file will be parsed.\r\n\r\nTodo\r\n\r\nThe plugin is not test in windows, I guess it can work.","install_details":"Copy c_complete.vim c_complete.py ctags_cache\/ to \/.vim\/plugin\/.\r\n\r\nYou will need vim compiled with python 3.2.\r\n\r\nthere are two patches for ctags:\r\n\r\n1. tags generated by Exuberant ctags has a field 'typeref', indicates the type of the tag. but if the type is a 'typedef', the field is empty. this patch fixed it.\r\nhttp:\/\/sourceforge.net\/tracker\/download.php?group_id=6556&atid=306556&file_id=417098&aid=3354287\r\n\r\n2. the anonymous struct indexed by Exuberant ctags named as '__anon1', it will confused when editing multi-files and updated one file. this patch use random number as anonymous id to avoid the problem.\r\nhttp:\/\/sourceforge.net\/tracker\/download.php?group_id=6556&atid=106556&file_id=334521&aid=2819658","5":"Copy c_complete.vim c_complete.py ctags_cache\/ to \/.vim\/plugin\/.\r\n\r\nYou will need vim compiled with python 3.2.\r\n\r\nthere are two patches for ctags:\r\n\r\n1. tags generated by Exuberant ctags has a field 'typeref', indicates the type of the tag. but if the type is a 'typedef', the field is empty. this patch fixed it.\r\nhttp:\/\/sourceforge.net\/tracker\/download.php?group_id=6556&atid=306556&file_id=417098&aid=3354287\r\n\r\n2. the anonymous struct indexed by Exuberant ctags named as '__anon1', it will confused when editing multi-files and updated one file. this patch use random number as anonymous id to avoid the problem.\r\nhttp:\/\/sourceforge.net\/tracker\/download.php?group_id=6556&atid=106556&file_id=334521&aid=2819658","first_name":"lei","6":"lei","last_name":"fw","7":"fw","releases":[{"0":"3684","vim_version":"7.3","1":"7.3","script_version":"v1.0.7","2":"v1.0.7","version_comment":"improved:\r\n1. initially support c++ class complete.\r\n2. eliminate delay of open big file.\r\n\r\nfixed:\r\nfixed some minor bugs. ","3":"improved:\r\n1. initially support c++ class complete.\r\n2. eliminate delay of open big file.\r\n\r\nfixed:\r\nfixed some minor bugs. ","package":"ctags_cache-v1.0.7.tar.gz","4":"ctags_cache-v1.0.7.tar.gz","src_id":"17581","5":"17581","creation_date":"1331402641","6":"1331402641"}]},"3683":{"script_id":"3683","0":"3683","script_name":"wikiatovimhelp","1":"wikiatovimhelp","script_type":"utility","2":"utility","summary":"Convert VimWikia Article to Vim help file","3":"Convert VimWikia Article to Vim help file","description":"Aims to Convert Articles on vimwikia website into vim helpfiles.","4":"Aims to Convert Articles on vimwikia website into vim helpfiles.","install_details":"Copy this file into your ~\/vimfiles\/plugin directory.","5":"Copy this file into your ~\/vimfiles\/plugin directory.","first_name":"niva","6":"niva","last_name":"niva","7":"niva","releases":[{"0":"3683","vim_version":"7.0","1":"7.0","script_version":"1.1","2":"1.1","version_comment":"\"               1. Download one or all vimwikia articles or tips from \r\n\"               http:\/\/vim.wikia.com\/wiki\/Vim_Tips_Wiki into a directory of \r\n\"               your choice (on windows i use httrack)\r\n\"\r\n\"               2. Open all html files into vim and call the converter cmd on\r\n\"               all buffers\r\n\"               :bufdo! VIMHELP\r\n\"\r\n\"               3. Consult wikiaArticles into help format within Vim\r\n\"               all converted articles are in $TMP\/wikiaArticles\r\n\"\r\n\"               -> grep, vimgrep command facilities you to find  the key word you\r\n\"               search for\r\n","3":"\"               1. Download one or all vimwikia articles or tips from \r\n\"               http:\/\/vim.wikia.com\/wiki\/Vim_Tips_Wiki into a directory of \r\n\"               your choice (on windows i use httrack)\r\n\"\r\n\"               2. Open all html files into vim and call the converter cmd on\r\n\"               all buffers\r\n\"               :bufdo! VIMHELP\r\n\"\r\n\"               3. Consult wikiaArticles into help format within Vim\r\n\"               all converted articles are in $TMP\/wikiaArticles\r\n\"\r\n\"               -> grep, vimgrep command facilities you to find  the key word you\r\n\"               search for\r\n","package":"wikiatovimhelp.vim","4":"wikiatovimhelp.vim","src_id":"16299","5":"16299","creation_date":"1313760439","6":"1313760439"},{"0":"3683","vim_version":"7.3","1":"7.3","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"wikiatovimhelp.vim","4":"wikiatovimhelp.vim","src_id":"16192","5":"16192","creation_date":"1312392273","6":"1312392273"}]},"3682":{"script_id":"3682","0":"3682","script_name":"hints_opengl.vim","1":"hints_opengl.vim","script_type":"ftplugin","2":"ftplugin","summary":"show prototypes for all opengl functions ","3":"show prototypes for all opengl functions ","description":"This script may be manually sourced or, if placed in .vim\/ftplugin\/c\/, will be automatically sourced whenever a C or C++ file is edited.\r\n\r\nThe purpose of this script is to show the prototype for any opengl function everytime its name is typed.\r\n\r\nThis script is heavily based on vimscript#1826.","4":"This script may be manually sourced or, if placed in .vim\/ftplugin\/c\/, will be automatically sourced whenever a C or C++ file is edited.\r\n\r\nThe purpose of this script is to show the prototype for any opengl function everytime its name is typed.\r\n\r\nThis script is heavily based on vimscript#1826.","install_details":"Just drop it in ~\/.vim\/ftplugin\/c\/","5":"Just drop it in ~\/.vim\/ftplugin\/c\/","first_name":"david","6":"david","last_name":"odin","7":"odin","releases":[{"0":"3682","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"hints_opengl.vim","4":"hints_opengl.vim","src_id":"16191","5":"16191","creation_date":"1312331044","6":"1312331044"}]},"3681":{"script_id":"3681","0":"3681","script_name":"functionlist.vim","1":"functionlist.vim","script_type":"utility","2":"utility","summary":"This plugin makes it easy to navigate between functions in a long file.","3":"This plugin makes it easy to navigate between functions in a long file.","description":"This plugin displays a list of all lines with word 'function' in current file\/buffer. This list is sorted on function name.\r\n\r\nIt also maintains a list of recently accessed functions at the top so that you can switch between functions easily, This list is updated when the user navigates to the function list window. The required function can be quickly reached in the list by pressing the first letter of the function. Pressing 'p' cycles through all the functions starting with 'p'.\r\n\r\nThis Plugin is best suited for working with  long source code files with functions defined with 'function' keyword.\r\n\r\nscreen shot http:\/\/i56.tinypic.com\/11hdhxg.png \r\n\r\ncommand to open function list\r\n\r\n:Flisttoggle \r\n\r\n\r\nTo make this plugin really useful you have to assign a shortcut key for this, \r\nsay you want F2 key to open the function list.\r\n\r\nyou can add the following line in your .vimrc file. \r\n\r\n            map <F2> : Flisttoggle <CR>\r\n\r\nIf you are on windows \" the file name would be _vimrc. The .vimrc file is  \r\nusually present in the users home directory.\r\n\r\nvimrc file will be hidden in linux so you will have to do a ls -ah to see it. \r\n\r\nIf the file  is not present you can just add one file with this line only.\r\n\r\nyou have to Restart vim \r\n\r\nInvoking this plugin opens a new vertical  window right to current window\r\n\r\n\r\n","4":"This plugin displays a list of all lines with word 'function' in current file\/buffer. This list is sorted on function name.\r\n\r\nIt also maintains a list of recently accessed functions at the top so that you can switch between functions easily, This list is updated when the user navigates to the function list window. The required function can be quickly reached in the list by pressing the first letter of the function. Pressing 'p' cycles through all the functions starting with 'p'.\r\n\r\nThis Plugin is best suited for working with  long source code files with functions defined with 'function' keyword.\r\n\r\nscreen shot http:\/\/i56.tinypic.com\/11hdhxg.png \r\n\r\ncommand to open function list\r\n\r\n:Flisttoggle \r\n\r\n\r\nTo make this plugin really useful you have to assign a shortcut key for this, \r\nsay you want F2 key to open the function list.\r\n\r\nyou can add the following line in your .vimrc file. \r\n\r\n            map <F2> : Flisttoggle <CR>\r\n\r\nIf you are on windows \" the file name would be _vimrc. The .vimrc file is  \r\nusually present in the users home directory.\r\n\r\nvimrc file will be hidden in linux so you will have to do a ls -ah to see it. \r\n\r\nIf the file  is not present you can just add one file with this line only.\r\n\r\nyou have to Restart vim \r\n\r\nInvoking this plugin opens a new vertical  window right to current window\r\n\r\n\r\n","install_details":"Copy functionlist.vim to plugins directory and restart vim\r\n\r\nInvoking plugin\r\n\r\n:Flisttoggle ","5":"Copy functionlist.vim to plugins directory and restart vim\r\n\r\nInvoking plugin\r\n\r\n:Flisttoggle ","first_name":"Sandeep","6":"Sandeep","last_name":"CR","7":"CR","releases":[{"0":"3681","vim_version":"7.0","1":"7.0","script_version":"2.0","2":"2.0","version_comment":"Removed the refreshing of indexing on mode change due to performance issue with large files\r\nFunction list now remembers the cursor position in the list after you reopen it.","3":"Removed the refreshing of indexing on mode change due to performance issue with large files\r\nFunction list now remembers the cursor position in the list after you reopen it.","package":"functionlist.vim","4":"functionlist.vim","src_id":"17171","5":"17171","creation_date":"1325964062","6":"1325964062"}]},"3680":{"script_id":"3680","0":"3680","script_name":"tablistlite.vim","1":"tablistlite.vim","script_type":"utility","2":"utility","summary":"Tracks the previously accessed tabs,and provides interface to switch back.","3":"Tracks the previously accessed tabs,and provides interface to switch back.","description":"This plugin makes it very easy to switch tabs. This keeps track of the tabs you were working in recently, so that you may switch back to them very easily. All the tab switching can be done using keyboard only\r\n\r\nSo if  you used to working in a lot of tabs, then this plugin can make a lot of difference.\r\n\r\nscreenshot : http:\/\/i55.tinypic.com\/x1g1l5.png \r\n\r\nCommand to open the recently worked tab list is\r\n\r\n :Tablisttoggle\r\n\r\n\r\nInvoking this plugin opens a new horizontal window above the currently window.\r\nThis window will contain a list of tabs(that are still open and you have accessed previously).\r\nThe tabs are sorted on order in which you accessed. \r\nTop line shows the last tab you were on. The previous tab below it and so on.\r\n\r\nTo switch to a tab in the list, double click on the line or press enter when you are on the corresponding line. \r\n\r\nWhen a tab is closed, that tab is removed from the list. The tablist window closes automatically when it loses focus.","4":"This plugin makes it very easy to switch tabs. This keeps track of the tabs you were working in recently, so that you may switch back to them very easily. All the tab switching can be done using keyboard only\r\n\r\nSo if  you used to working in a lot of tabs, then this plugin can make a lot of difference.\r\n\r\nscreenshot : http:\/\/i55.tinypic.com\/x1g1l5.png \r\n\r\nCommand to open the recently worked tab list is\r\n\r\n :Tablisttoggle\r\n\r\n\r\nInvoking this plugin opens a new horizontal window above the currently window.\r\nThis window will contain a list of tabs(that are still open and you have accessed previously).\r\nThe tabs are sorted on order in which you accessed. \r\nTop line shows the last tab you were on. The previous tab below it and so on.\r\n\r\nTo switch to a tab in the list, double click on the line or press enter when you are on the corresponding line. \r\n\r\nWhen a tab is closed, that tab is removed from the list. The tablist window closes automatically when it loses focus.","install_details":"Copy tablist.vim file to the plugins directory and restart vim\r\n\r\nin linux plugins dir => .vim dir in users home dir\r\nin windows =>  vimfiles dir in user home dir in Documents and Settings\r\n\r\nTo make this plugin really useful you have to assign a shortcut key for this, say you want F2 key to open and close  the tab list. you can add the following line in your .vimrc file. \r\n\r\n             map <F2> :Tablisttoggle<CR>.\r\n\r\n\r\nif you are on windows \" the file name would be _vimrc. The .vimrc file is  usually present in the users home directory.\r\n\r\n.vimrc file will be hidden in linux so you will have to do a \r\n\r\n\"ls -ah\" command to see it. \r\n\r\nIf the file  is not present you can just add one file with this line only.\r\n\r\nyou have to Restart vim \r\n","5":"Copy tablist.vim file to the plugins directory and restart vim\r\n\r\nin linux plugins dir => .vim dir in users home dir\r\nin windows =>  vimfiles dir in user home dir in Documents and Settings\r\n\r\nTo make this plugin really useful you have to assign a shortcut key for this, say you want F2 key to open and close  the tab list. you can add the following line in your .vimrc file. \r\n\r\n             map <F2> :Tablisttoggle<CR>.\r\n\r\n\r\nif you are on windows \" the file name would be _vimrc. The .vimrc file is  usually present in the users home directory.\r\n\r\n.vimrc file will be hidden in linux so you will have to do a \r\n\r\n\"ls -ah\" command to see it. \r\n\r\nIf the file  is not present you can just add one file with this line only.\r\n\r\nyou have to Restart vim \r\n","first_name":"Sandeep","6":"Sandeep","last_name":"CR","7":"CR","releases":[{"0":"3680","vim_version":"7.0","1":"7.0","script_version":"1.2","2":"1.2","version_comment":"Added indication for tabs that contain modified buffer.","3":"Added indication for tabs that contain modified buffer.","package":"tablistlite.vim","4":"tablistlite.vim","src_id":"16553","5":"16553","creation_date":"1316426256","6":"1316426256"},{"0":"3680","vim_version":"7.0","1":"7.0","script_version":"1.2","2":"1.2","version_comment":"Bug Fixed where a tab wont show up in the list until it is switched for another tab.","3":"Bug Fixed where a tab wont show up in the list until it is switched for another tab.","package":"tablistlite.vim","4":"tablistlite.vim","src_id":"16323","5":"16323","creation_date":"1313945092","6":"1313945092"}]},"3679":{"script_id":"3679","0":"3679","script_name":"saturn.vim","1":"saturn.vim","script_type":"color scheme","2":"color scheme","summary":"Light colorscheme","3":"Light colorscheme","description":"\r\nA simple light colorscheme.","4":"\r\nA simple light colorscheme.","install_details":"","5":"","first_name":"geck","6":"geck","last_name":" ","7":" ","releases":[{"0":"3679","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Major overhaul","3":"Major overhaul","package":"saturn.zip","4":"saturn.zip","src_id":"22173","5":"22173","creation_date":"1404916408","6":"1404916408"}]},"3678":{"script_id":"3678","0":"3678","script_name":"rfc5424","1":"rfc5424","script_type":"syntax","2":"syntax","summary":"Vim syntax for RFC5424 syslog file","3":"Vim syntax for RFC5424 syslog file","description":"This file adds syntax highlighting for RFC5424 syslog files.\r\n\r\nYou can follow development on https:\/\/github.com\/cybertk\/vim-syntax-rfc5424\/","4":"This file adds syntax highlighting for RFC5424 syslog files.\r\n\r\nYou can follow development on https:\/\/github.com\/cybertk\/vim-syntax-rfc5424\/","install_details":"Copy the syntax file to $HOME\/.vim\/syntax\/ and type \"set syn=rfc5424\" while viewing a RFC5424 syslog file.","5":"Copy the syntax file to $HOME\/.vim\/syntax\/ and type \"set syn=rfc5424\" while viewing a RFC5424 syslog file.","first_name":"Kyan","6":"Kyan","last_name":"He","7":"He","releases":[{"0":"3678","vim_version":"7.0","1":"7.0","script_version":"0.1.1","2":"0.1.1","version_comment":"Bug fix","3":"Bug fix","package":"rfc5424.vim","4":"rfc5424.vim","src_id":"23106","5":"23106","creation_date":"1427731350","6":"1427731350"},{"0":"3678","vim_version":"7.0","1":"7.0","script_version":"0.1.0","2":"0.1.0","version_comment":"Initial upload","3":"Initial upload","package":"rfc5424.vim","4":"rfc5424.vim","src_id":"16186","5":"16186","creation_date":"1312309410","6":"1312309410"}]},"3677":{"script_id":"3677","0":"3677","script_name":"baobaozhu","1":"baobaozhu","script_type":"color scheme","2":"color scheme","summary":"For My ex-girlfriend","3":"For My ex-girlfriend","description":"I make this color scheme when I was together with my ex-girlfirend.\r\nWhen you back to Guangdong, we never meet again. I miss you so much. Although I can not take you to wife, I still love you. Only you!\r\nI miss you so much.\r\nI use some other color scheme for base, and modify some detail color for help myself to php development. This scheme is good for PHP development,just try it.","4":"I make this color scheme when I was together with my ex-girlfirend.\r\nWhen you back to Guangdong, we never meet again. I miss you so much. Although I can not take you to wife, I still love you. Only you!\r\nI miss you so much.\r\nI use some other color scheme for base, and modify some detail color for help myself to php development. This scheme is good for PHP development,just try it.","install_details":"Copy the file to your vim colors directory and then do :colorscheme baobaozhu \r\nOR\r\nJust do\r\n\r\n    colorscheme baobaozhu\r\n\r\nin your .vimrc file","5":"Copy the file to your vim colors directory and then do :colorscheme baobaozhu \r\nOR\r\nJust do\r\n\r\n    colorscheme baobaozhu\r\n\r\nin your .vimrc file","first_name":"Lorry","6":"Lorry","last_name":"Chan","7":"Chan","releases":[{"0":"3677","vim_version":"7.0","1":"7.0","script_version":"0.99","2":"0.99","version_comment":"Initial upload","3":"Initial upload","package":"baobaozhu.vim","4":"baobaozhu.vim","src_id":"16182","5":"16182","creation_date":"1312269485","6":"1312269485"}]},"3676":{"script_id":"3676","0":"3676","script_name":"copy-as-rtf","1":"copy-as-rtf","script_type":"utility","2":"utility","summary":"Copy syntax-highlighted code from vim to the OS X clipboard as RTF text","3":"Copy syntax-highlighted code from vim to the OS X clipboard as RTF text","description":"This plugin provides a CopyRTF command for OS X systems that copies the current buffer or selected text to the clipboard as syntax-highlighted RTF text.\r\n\r\nThis plugin was inspired by the rtf-highlight plugin (https:\/\/github.com\/dharanasoft\/rtf-highlight), but only uses commands available by default on OS X and an HTML conversion plugin that ships with vim.\r\n\r\nMac-only, but if there are equivalent commands for other platforms (html to rtf conversion and copy to clipboard), let me know via the github project (https:\/\/github.com\/zerowidth\/vim-copy-as-rtf) and file an issue or submit a patch.","4":"This plugin provides a CopyRTF command for OS X systems that copies the current buffer or selected text to the clipboard as syntax-highlighted RTF text.\r\n\r\nThis plugin was inspired by the rtf-highlight plugin (https:\/\/github.com\/dharanasoft\/rtf-highlight), but only uses commands available by default on OS X and an HTML conversion plugin that ships with vim.\r\n\r\nMac-only, but if there are equivalent commands for other platforms (html to rtf conversion and copy to clipboard), let me know via the github project (https:\/\/github.com\/zerowidth\/vim-copy-as-rtf) and file an issue or submit a patch.","install_details":"unpack the tarball.","5":"unpack the tarball.","first_name":"Nathan","6":"Nathan","last_name":"Witmer","7":"Witmer","releases":[{"0":"3676","vim_version":"7.0","1":"7.0","script_version":"0.0.3","2":"0.0.3","version_comment":"Fixed bug in scratch buffer HTML conversion","3":"Fixed bug in scratch buffer HTML conversion","package":"vim-copy-as-rtf-0.0.3.tgz","4":"vim-copy-as-rtf-0.0.3.tgz","src_id":"19851","5":"19851","creation_date":"1366301150","6":"1366301150"},{"0":"3676","vim_version":"7.0","1":"7.0","script_version":"0.0.2","2":"0.0.2","version_comment":"Adds configurable options for removing or preserving leading whitespace when copying.","3":"Adds configurable options for removing or preserving leading whitespace when copying.","package":"vim-copy-as-rtf-0.0.2.tgz","4":"vim-copy-as-rtf-0.0.2.tgz","src_id":"18264","5":"18264","creation_date":"1342294973","6":"1342294973"},{"0":"3676","vim_version":"7.2","1":"7.2","script_version":"0.0.1","2":"0.0.1","version_comment":"Initial upload","3":"Initial upload","package":"vim-copy-as-rtf-0.0.1.tgz","4":"vim-copy-as-rtf-0.0.1.tgz","src_id":"16174","5":"16174","creation_date":"1312156015","6":"1312156015"}]},"3675":{"script_id":"3675","0":"3675","script_name":"cab.vim","1":"cab.vim","script_type":"utility","2":"utility","summary":"Vim plugin for using ack-grep with iterm for fast and easy search in project","3":"Vim plugin for using ack-grep with iterm for fast and easy search in project","description":"ONLY FOR MAC (for the present)\r\n\r\nCab is a Vim plugin for using ack-grep (http:\/\/betterthangrep.com) in\r\ncommon with iterm (http:\/\/www.iterm2.com\/) for fast and easy search in\r\na project from vim.\r\nIt uses current working directory as a root.\r\nIt's possible to use Cab only with iterm (not with terminal) bacause cab\r\nuses applescript API for interaction with iterm (or iterm2).\r\n\r\nHow to use Cab:\r\n\r\n  in the main mode:\r\n    place the cursor on the word to search and press <Leader>f\r\n    it will open new tab of the iterm and run the command \"ack -Q <word for search>\"\r\n\r\n  in the visual mode:\r\n    select a range of text to search and press <Leader>f\r\n    it will open new tab of the iterm and run the command \"ack -Q <text for search>\"\r\n\r\n  in the command mode:\r\n    type :Cab <text for search>\r\n    it will open new tab of the iterm and run the coommand \"ack -Q <text for search>\"\r\n\r\nCab automatically escape special symbols and quotes. You can search for\r\nany text. For exaple\r\n :Cab Search for this \"quoted\" 'text' and \/\\ slashes\r\n\r\nYou can redefine a method of invoking ack using global variable cab_ack_cmd\r\nExample (write it in the your ~\/.vimrc file):\r\n\r\n  let g:cab_ack_cmd = \"ack-grep -irn --ignore-dir=assets\"\r\n\r\nFor installation use vimball:\r\n\r\n  vim cab.vmb\r\n  :so %","4":"ONLY FOR MAC (for the present)\r\n\r\nCab is a Vim plugin for using ack-grep (http:\/\/betterthangrep.com) in\r\ncommon with iterm (http:\/\/www.iterm2.com\/) for fast and easy search in\r\na project from vim.\r\nIt uses current working directory as a root.\r\nIt's possible to use Cab only with iterm (not with terminal) bacause cab\r\nuses applescript API for interaction with iterm (or iterm2).\r\n\r\nHow to use Cab:\r\n\r\n  in the main mode:\r\n    place the cursor on the word to search and press <Leader>f\r\n    it will open new tab of the iterm and run the command \"ack -Q <word for search>\"\r\n\r\n  in the visual mode:\r\n    select a range of text to search and press <Leader>f\r\n    it will open new tab of the iterm and run the command \"ack -Q <text for search>\"\r\n\r\n  in the command mode:\r\n    type :Cab <text for search>\r\n    it will open new tab of the iterm and run the coommand \"ack -Q <text for search>\"\r\n\r\nCab automatically escape special symbols and quotes. You can search for\r\nany text. For exaple\r\n :Cab Search for this \"quoted\" 'text' and \/\\ slashes\r\n\r\nYou can redefine a method of invoking ack using global variable cab_ack_cmd\r\nExample (write it in the your ~\/.vimrc file):\r\n\r\n  let g:cab_ack_cmd = \"ack-grep -irn --ignore-dir=assets\"\r\n\r\nFor installation use vimball:\r\n\r\n  vim cab.vmb\r\n  :so %","install_details":"Use vimball","5":"Use vimball","first_name":"Vadim","6":"Vadim","last_name":"Rachko","7":"Rachko","releases":[{"0":"3675","vim_version":"7.0","1":"7.0","script_version":"0.2","2":"0.2","version_comment":"Fixed defaults definition (g:cab_ack_cmd)","3":"Fixed defaults definition (g:cab_ack_cmd)","package":"cab.vmb","4":"cab.vmb","src_id":"17500","5":"17500","creation_date":"1329744797","6":"1329744797"},{"0":"3675","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"cab.vba","4":"cab.vba","src_id":"16159","5":"16159","creation_date":"1311852513","6":"1311852513"}]},"3674":{"script_id":"3674","0":"3674","script_name":"univresal-blue scheme","1":"univresal-blue scheme","script_type":"color scheme","2":"color scheme","summary":"blue vim scheme that aims to work well in gvim, vim in console and terminal","3":"blue vim scheme that aims to work well in gvim, vim in console and terminal","description":"The purpose of this theme is to be usable not only in gvim, but to be also usable in in virtual terminal emulator and console\r\nFor this reason this theme is tested in gvim, urxvt and FreeBSD console\r\n\r\nFor virtual terminals I use these colors in .Xdefaults:\r\n\r\nXTerm*color0:   #000000\r\nXTerm*color8:   #606060\r\nXTerm*color1:   #800000\r\nXTerm*color9:   #FF0000\r\nXTerm*color2:   #00800a\r\nXTerm*color10:  #00FF00\r\nXTerm*color3:   #E7811B\r\nXTerm*color11:  #FFFF00\r\nXTerm*color4:   #000060\r\nXTerm*color12:  #5050FF\r\nXTerm*color5:   #800080\r\nXTerm*color13:  #FF00FF\r\nXTerm*color6:   #008080\r\nXTerm*color14:  #00FFFF\r\nXTerm*color7:   #909090\r\nXTerm*color15:  #FFFFFF\r\n\r\nXTerm*Background:       #000000\r\nXTerm*Foreground:       #FFFFFF\r\nXTerm*underlineColor:   #5070ff\r\nXTerm*cursorColor:      #ffffff\r\n\r\n\r\n\r\nAlso I set LSCOLORS=DxGxGxCxBxexcxbxbxFxFb (for colorful ls, which looks quite nice with these colors)\r\n\r\nScreenshots comparing gvim and vim in terminal:\r\nhttp:\/\/files.bsdroot.lv\/my\/screenshots\/vim\/universal-blue\/2011.11.07_at_23.40.32.png (vim)\r\nhttp:\/\/files.bsdroot.lv\/my\/screenshots\/vim\/universal-blue\/2011.11.07_at_23.41.29.png (gvim)\r\n\r\n\r\nNOTE: if you use rxvt-unicode, check t_Co setting (with :set t_Co) if it's showing 8, you need to set it to 16, otherwise this syntax file will be rendered poorly","4":"The purpose of this theme is to be usable not only in gvim, but to be also usable in in virtual terminal emulator and console\r\nFor this reason this theme is tested in gvim, urxvt and FreeBSD console\r\n\r\nFor virtual terminals I use these colors in .Xdefaults:\r\n\r\nXTerm*color0:   #000000\r\nXTerm*color8:   #606060\r\nXTerm*color1:   #800000\r\nXTerm*color9:   #FF0000\r\nXTerm*color2:   #00800a\r\nXTerm*color10:  #00FF00\r\nXTerm*color3:   #E7811B\r\nXTerm*color11:  #FFFF00\r\nXTerm*color4:   #000060\r\nXTerm*color12:  #5050FF\r\nXTerm*color5:   #800080\r\nXTerm*color13:  #FF00FF\r\nXTerm*color6:   #008080\r\nXTerm*color14:  #00FFFF\r\nXTerm*color7:   #909090\r\nXTerm*color15:  #FFFFFF\r\n\r\nXTerm*Background:       #000000\r\nXTerm*Foreground:       #FFFFFF\r\nXTerm*underlineColor:   #5070ff\r\nXTerm*cursorColor:      #ffffff\r\n\r\n\r\n\r\nAlso I set LSCOLORS=DxGxGxCxBxexcxbxbxFxFb (for colorful ls, which looks quite nice with these colors)\r\n\r\nScreenshots comparing gvim and vim in terminal:\r\nhttp:\/\/files.bsdroot.lv\/my\/screenshots\/vim\/universal-blue\/2011.11.07_at_23.40.32.png (vim)\r\nhttp:\/\/files.bsdroot.lv\/my\/screenshots\/vim\/universal-blue\/2011.11.07_at_23.41.29.png (gvim)\r\n\r\n\r\nNOTE: if you use rxvt-unicode, check t_Co setting (with :set t_Co) if it's showing 8, you need to set it to 16, otherwise this syntax file will be rendered poorly","install_details":"put universal-blue.vim in ~\/.vim\/colors\/\r\nin your .vimrc add \r\n\r\nsyntax on\r\ncolo universal-blue\r\n\r\nHope you enjoy it.\r\n\r\nAt any time you can grab latest version at:\r\nhttps:\/\/github.com\/graudeejs\/dot.vim\/blob\/master\/colors\/universal-blue.vim\r\n\r\nThis color scheme was only tested with vim 7.3","5":"put universal-blue.vim in ~\/.vim\/colors\/\r\nin your .vimrc add \r\n\r\nsyntax on\r\ncolo universal-blue\r\n\r\nHope you enjoy it.\r\n\r\nAt any time you can grab latest version at:\r\nhttps:\/\/github.com\/graudeejs\/dot.vim\/blob\/master\/colors\/universal-blue.vim\r\n\r\nThis color scheme was only tested with vim 7.3","first_name":"no","6":"no","last_name":"body","7":"body","releases":[{"0":"3674","vim_version":"7.3","1":"7.3","script_version":"1.4.1","2":"1.4.1","version_comment":"Improve tab colors","3":"Improve tab colors","package":"universal-blue.vim","4":"universal-blue.vim","src_id":"16841","5":"16841","creation_date":"1320858129","6":"1320858129"}]},"3673":{"script_id":"3673","0":"3673","script_name":"aldmeris","1":"aldmeris","script_type":"color scheme","2":"color scheme","summary":"A colorscheme based on oblivion for gedit that support GVIM and 256 colors term","3":"A colorscheme based on oblivion for gedit that support GVIM and 256 colors term","description":"Aldmeris is a dark colorscheme based on oblivion for gedit. It uses the popular tango palette by the freedesktop.org project.\r\n\r\nSome cool features:\r\n\r\n- tango palette\r\n- support GUI, 256 and 16 colors mode for terminal emulators\r\n- option to use different terminal base colors in the colorscheme\r\n- tpope's fugitive support: well recognizable colors for the output of :Gstatus, and for git objects.\r\n\r\nScreenshots: \r\n\r\nRuby in a terminal (urxvt): https:\/\/github.com\/veloce\/vim-aldmeris\/raw\/master\/screenshots\/aldmeris.png\r\nCommit in fugitive: https:\/\/github.com\/veloce\/vim-aldmeris\/raw\/master\/screenshots\/aldmeris-gstatus.png\r\n\r\nSource:\r\n\r\nhttps:\/\/github.com\/veloce\/vim-aldmeris\r\n","4":"Aldmeris is a dark colorscheme based on oblivion for gedit. It uses the popular tango palette by the freedesktop.org project.\r\n\r\nSome cool features:\r\n\r\n- tango palette\r\n- support GUI, 256 and 16 colors mode for terminal emulators\r\n- option to use different terminal base colors in the colorscheme\r\n- tpope's fugitive support: well recognizable colors for the output of :Gstatus, and for git objects.\r\n\r\nScreenshots: \r\n\r\nRuby in a terminal (urxvt): https:\/\/github.com\/veloce\/vim-aldmeris\/raw\/master\/screenshots\/aldmeris.png\r\nCommit in fugitive: https:\/\/github.com\/veloce\/vim-aldmeris\/raw\/master\/screenshots\/aldmeris-gstatus.png\r\n\r\nSource:\r\n\r\nhttps:\/\/github.com\/veloce\/vim-aldmeris\r\n","install_details":"Install in ~\/.vim\/colors. \r\n\r\nTry it out with \r\n\r\n:colorscheme aldmeris\r\n\r\nIf you want to make it the default, add that command to your vimrc or gvimrc. \r\nIf you use it with a terminal that uses the tango palette as system colors, add this to your vimrc to obtain best results:\r\n\r\nlet g:aldmeris_termcolors = \"tango\"\r\n\r\nIf you wish to use a transparent terminal, you can put this option in your vimrc:\r\n\r\nlet g:aldmeris_transparent = 1","5":"Install in ~\/.vim\/colors. \r\n\r\nTry it out with \r\n\r\n:colorscheme aldmeris\r\n\r\nIf you want to make it the default, add that command to your vimrc or gvimrc. \r\nIf you use it with a terminal that uses the tango palette as system colors, add this to your vimrc to obtain best results:\r\n\r\nlet g:aldmeris_termcolors = \"tango\"\r\n\r\nIf you wish to use a transparent terminal, you can put this option in your vimrc:\r\n\r\nlet g:aldmeris_transparent = 1","first_name":"Vincent","6":"Vincent","last_name":"Velociter","7":"Velociter","releases":[{"0":"3673","vim_version":"7.0","1":"7.0","script_version":"1.2","2":"1.2","version_comment":"- Fixed vim-git syntax\r\n- Added support for ColorColumn\r\n- Updated pangloss\/vim-javascript syntax","3":"- Fixed vim-git syntax\r\n- Added support for ColorColumn\r\n- Updated pangloss\/vim-javascript syntax","package":"aldmeris.vim","4":"aldmeris.vim","src_id":"19819","5":"19819","creation_date":"1366037111","6":"1366037111"},{"0":"3673","vim_version":"7.0","1":"7.0","script_version":"1.1.1","2":"1.1.1","version_comment":"Add transparency option (fixes previous version)","3":"Add transparency option (fixes previous version)","package":"aldmeris.vim","4":"aldmeris.vim","src_id":"16672","5":"16672","creation_date":"1318609338","6":"1318609338"},{"0":"3673","vim_version":"7.3","1":"7.3","script_version":"1.1","2":"1.1","version_comment":"Added option for terminal transparency.","3":"Added option for terminal transparency.","package":"aldmeris.vim","4":"aldmeris.vim","src_id":"16669","5":"16669","creation_date":"1318606117","6":"1318606117"},{"0":"3673","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"aldmeris.vim","4":"aldmeris.vim","src_id":"16156","5":"16156","creation_date":"1311796528","6":"1311796528"}]},"3672":{"script_id":"3672","0":"3672","script_name":"textgenshi.vim","1":"textgenshi.vim","script_type":"syntax","2":"syntax","summary":"Syntax Highlighting for Genshi Text Templates","3":"Syntax Highlighting for Genshi Text Templates","description":"This file adds syntax highlighting for Genshi plain text templates (see vimscript #1869 for XML template support).\r\n\r\nSee: http:\/\/genshi.edgewall.org\/wiki\/Documentation\/text-templates.html","4":"This file adds syntax highlighting for Genshi plain text templates (see vimscript #1869 for XML template support).\r\n\r\nSee: http:\/\/genshi.edgewall.org\/wiki\/Documentation\/text-templates.html","install_details":"Copy the genshi.vim file into the ~\/.vim\/syntax\/ directory. If your text templates have a \".genshi\" file extension (and your XML templates don't), you could add the following lines to your ~\/.vim\/filetype.vim in order to auto-detect them::\r\n\r\n  augroup filetypedetect\r\n    autocmd BufNewFile,BufRead *.genshi setfiletype textgenshi\r\n  augroup END","5":"Copy the genshi.vim file into the ~\/.vim\/syntax\/ directory. If your text templates have a \".genshi\" file extension (and your XML templates don't), you could add the following lines to your ~\/.vim\/filetype.vim in order to auto-detect them::\r\n\r\n  augroup filetypedetect\r\n    autocmd BufNewFile,BufRead *.genshi setfiletype textgenshi\r\n  augroup END","first_name":"Holger","6":"Holger","last_name":"Wei\u00c3\u009f","7":"Wei\u00c3\u009f","releases":[{"0":"3672","vim_version":"6.0","1":"6.0","script_version":"1.1","2":"1.1","version_comment":"We now use the name \"textgenshi\" instead of \"genshi\" in order to avoid conflicts with syntax definitions for Genshi XML templates.  Apart from that, some minor bugs have been fixed.","3":"We now use the name \"textgenshi\" instead of \"genshi\" in order to avoid conflicts with syntax definitions for Genshi XML templates.  Apart from that, some minor bugs have been fixed.","package":"textgenshi.vim","4":"textgenshi.vim","src_id":"16255","5":"16255","creation_date":"1313240813","6":"1313240813"},{"0":"3672","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"genshi.vim","4":"genshi.vim","src_id":"16154","5":"16154","creation_date":"1311772690","6":"1311772690"}]},"3671":{"script_id":"3671","0":"3671","script_name":"cdevframework","1":"cdevframework","script_type":"utility","2":"utility","summary":"C\/C++ development framework","3":"C\/C++ development framework","description":"With time and experience, I ended setting up vim to ease my life while developing in C++. This is the very basic version of it, and it will most probably grow with time.\r\n\r\nUsage:\r\n\r\nRun vim from within the root directory of your project ($HOME\/Projects\/myproject for instance). The script sets up the CTRL-W_s shortcut to ask for a source file extension as well as header file extension, then the source files base path and header files base path. From then on, each time you press the shortcut, you will be asked only for the file name you want to edit, without extension or path. It will then open them side by side. The idea is to go to the window with <CTRL-W>j and <CTRL-W>k and press <CTRL-W>_ to maximize the height.\r\n\r\nThe script also adds the \"globals\" option to sessionoptions in order to keep the base paths and extensions for when the session is saved with:\r\n\r\n    :mksession! <filename>\r\n\r\nTo reload the session, then use:\r\n\r\n    vim -S <filename>\r\n\r\nAnother hint: I like having the filename list next to the source code, by doing:\r\n\r\n    :vsplit .\r\n    :vertical resize 32\r\n    :set wfw\r\n","4":"With time and experience, I ended setting up vim to ease my life while developing in C++. This is the very basic version of it, and it will most probably grow with time.\r\n\r\nUsage:\r\n\r\nRun vim from within the root directory of your project ($HOME\/Projects\/myproject for instance). The script sets up the CTRL-W_s shortcut to ask for a source file extension as well as header file extension, then the source files base path and header files base path. From then on, each time you press the shortcut, you will be asked only for the file name you want to edit, without extension or path. It will then open them side by side. The idea is to go to the window with <CTRL-W>j and <CTRL-W>k and press <CTRL-W>_ to maximize the height.\r\n\r\nThe script also adds the \"globals\" option to sessionoptions in order to keep the base paths and extensions for when the session is saved with:\r\n\r\n    :mksession! <filename>\r\n\r\nTo reload the session, then use:\r\n\r\n    vim -S <filename>\r\n\r\nAnother hint: I like having the filename list next to the source code, by doing:\r\n\r\n    :vsplit .\r\n    :vertical resize 32\r\n    :set wfw\r\n","install_details":"Simply drop it in the vim plugins folder ($HOME\/.vim\/plugin).","5":"Simply drop it in the vim plugins folder ($HOME\/.vim\/plugin).","first_name":"Fabien","6":"Fabien","last_name":"Bouleau","7":"Bouleau","releases":[{"0":"3671","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"cdevframework.vim","4":"cdevframework.vim","src_id":"16153","5":"16153","creation_date":"1311760042","6":"1311760042"}]},"3670":{"script_id":"3670","0":"3670","script_name":"orangeocean256","1":"orangeocean256","script_type":"color scheme","2":"color scheme","summary":"high contrast, 256color, vivid, blue bg, orange\/white fg.","3":"high contrast, 256color, vivid, blue bg, orange\/white fg.","description":"A vivid color scheme. High contrast with orange and dark blue freshens you up and enhances your vim operation.\r\n\r\nscreenshot: http:\/\/nanabit.net\/assets\/images\/vim\/orangeocean256.png","4":"A vivid color scheme. High contrast with orange and dark blue freshens you up and enhances your vim operation.\r\n\r\nscreenshot: http:\/\/nanabit.net\/assets\/images\/vim\/orangeocean256.png","install_details":"Put the downloaded file to ~\/.vim\/colors. You may need to set TERM='xterm-256color' in your console (.bashrc, etc.) for 256-color appearance.","5":"Put the downloaded file to ~\/.vim\/colors. You may need to set TERM='xterm-256color' in your console (.bashrc, etc.) for 256-color appearance.","first_name":"Takahiro","6":"Takahiro","last_name":"SUZUKI","7":"SUZUKI","releases":[{"0":"3670","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"orangeocean256.vim","4":"orangeocean256.vim","src_id":"16148","5":"16148","creation_date":"1311683223","6":"1311683223"}]},"3669":{"script_id":"3669","0":"3669","script_name":"rake.vim","1":"rake.vim","script_type":"utility","2":"utility","summary":"It's like rails.vim without the rails","3":"It's like rails.vim without the rails","description":"With rake.vim, you can use all those parts of rails.vim (vimscript #1567) that you wish you could use on your other Ruby projects on anything with a Rakefile, including :A, :Elib and friends, and of course :Rake.  It's great when paired with `gem open` and `bundle open`.\r\n\r\nhttps:\/\/github.com\/tpope\/vim-rake\r\n","4":"With rake.vim, you can use all those parts of rails.vim (vimscript #1567) that you wish you could use on your other Ruby projects on anything with a Rakefile, including :A, :Elib and friends, and of course :Rake.  It's great when paired with `gem open` and `bundle open`.\r\n\r\nhttps:\/\/github.com\/tpope\/vim-rake\r\n","install_details":"Requires vimscript #4989.\r\n\r\nExtract to ~\/.vim, or ~\\vimfiles (Windows).  You'll need to regenerate helptags (fill in the install path below) \r\n\r\n:helptags ~\/.vim\/doc","5":"Requires vimscript #4989.\r\n\r\nExtract to ~\/.vim, or ~\\vimfiles (Windows).  You'll need to regenerate helptags (fill in the install path below) \r\n\r\n:helptags ~\/.vim\/doc","first_name":"Tim","6":"Tim","last_name":"Pope","7":"Pope","releases":[{"0":"3669","vim_version":"7.0","1":"7.0","script_version":"2.0","2":"2.0","version_comment":"Major refactor to use projectionist.vim.\r\nDrop all backwards compatible :R commands.\r\nProvide default dispatch of rspec\/ruby -Itest in specs\/tests.\r\nSet default compiler options for :make to use rake.\r\nTab complete for :Make and :Dispatch rake.\r\nDrop support for :Ctags.","3":"Major refactor to use projectionist.vim.\r\nDrop all backwards compatible :R commands.\r\nProvide default dispatch of rspec\/ruby -Itest in specs\/tests.\r\nSet default compiler options for :make to use rake.\r\nTab complete for :Make and :Dispatch rake.\r\nDrop support for :Ctags.","package":"rake.zip","4":"rake.zip","src_id":"22861","5":"22861","creation_date":"1422990134","6":"1422990134"},{"0":"3669","vim_version":"7.0","1":"7.0","script_version":"1.2","2":"1.2","version_comment":"Drop :R prefix. :Elib replaces :Rlib and :Tlib replaces :RTlib.  (Old commands still work.).\r\nBetter detection of gems.\r\nUse rake binstub if present.\r\nBetter 'errorformat'.\r\nAllow custom rake dispatch with :Make.","3":"Drop :R prefix. :Elib replaces :Rlib and :Tlib replaces :RTlib.  (Old commands still work.).\r\nBetter detection of gems.\r\nUse rake binstub if present.\r\nBetter 'errorformat'.\r\nAllow custom rake dispatch with :Make.","package":"rake.zip","4":"rake.zip","src_id":"19698","5":"19698","creation_date":"1364186266","6":"1364186266"},{"0":"3669","vim_version":"7.0","1":"7.0","script_version":"1.1","2":"1.1","version_comment":"Better handling of tags.\r\nOnly set path in Ruby files.\r\nAdd bundler.vim support.\r\n:Rlib defaults to gemspec if found.\r\nFix detection of netrw buffers.\r\nHandle alternate specs in spec\/lib.","3":"Better handling of tags.\r\nOnly set path in Ruby files.\r\nAdd bundler.vim support.\r\n:Rlib defaults to gemspec if found.\r\nFix detection of netrw buffers.\r\nHandle alternate specs in spec\/lib.","package":"rake.zip","4":"rake.zip","src_id":"19283","5":"19283","creation_date":"1357056537","6":"1357056537"},{"0":"3669","vim_version":"7.0","1":"7.0","script_version":"1.1","2":"1.1","version_comment":"Better handling of tags.\r\nOnly set path in Ruby files.\r\nAdd bundler.vim support.\r\n:Rlib defaults to gemspec if found.\r\nFix detection of netrw buffers.\r\nHandle alternate specs in spec\/lib.","3":"Better handling of tags.\r\nOnly set path in Ruby files.\r\nAdd bundler.vim support.\r\n:Rlib defaults to gemspec if found.\r\nFix detection of netrw buffers.\r\nHandle alternate specs in spec\/lib.","package":"rake.zip","4":"rake.zip","src_id":"19282","5":"19282","creation_date":"1357056189","6":"1357056189"},{"0":"3669","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"rake.zip","4":"rake.zip","src_id":"16146","5":"16146","creation_date":"1311656561","6":"1311656561"}]},"3668":{"script_id":"3668","0":"3668","script_name":"sgmlendtag","1":"sgmlendtag","script_type":"ftplugin","2":"ftplugin","summary":"Auto completion of sgml (html, xml, etc) end tags.","3":"Auto completion of sgml (html, xml, etc) end tags.","description":"This sgml end tag completion plugin aims to provide a simple\r\nmeans to complete end tags in sgml documents (xml, html, etc.).\r\n\r\nUnlike some other end tag completion plugins, the end tag is\r\nnot auto added when you finish typing the opening tag, but\r\ninstead is inserted only when you start typing the closing tag\r\n(when you hit the slash in '<\/'), at which point the tag name\r\nand closing > are inserted automatically.\r\n\r\nThe intent of this approach is to prevent an interruption in\r\nyour flow of typing by not requiring you to ever have to\r\nnavigate around text added to the right of the cursor.\r\n\r\nhttp:\/\/github.com\/ervandew\/sgmlendtag","4":"This sgml end tag completion plugin aims to provide a simple\r\nmeans to complete end tags in sgml documents (xml, html, etc.).\r\n\r\nUnlike some other end tag completion plugins, the end tag is\r\nnot auto added when you finish typing the opening tag, but\r\ninstead is inserted only when you start typing the closing tag\r\n(when you hit the slash in '<\/'), at which point the tag name\r\nand closing > are inserted automatically.\r\n\r\nThe intent of this approach is to prevent an interruption in\r\nyour flow of typing by not requiring you to ever have to\r\nnavigate around text added to the right of the cursor.\r\n\r\nhttp:\/\/github.com\/ervandew\/sgmlendtag","install_details":"1. Download sgmlendtag.vba to any directory.\r\n2. Open the file in vim ($ vim sgmlendtag.vba).\r\n3. Source the file (:so %).","5":"1. Download sgmlendtag.vba to any directory.\r\n2. Open the file in vim ($ vim sgmlendtag.vba).\r\n3. Source the file (:so %).","first_name":"Eric","6":"Eric","last_name":"Van Dewoestine","7":"Van Dewoestine","releases":[{"0":"3668","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"sgmlendtag.vba","4":"sgmlendtag.vba","src_id":"16135","5":"16135","creation_date":"1311605439","6":"1311605439"}]},"3667":{"script_id":"3667","0":"3667","script_name":"Toxic","1":"Toxic","script_type":"color scheme","2":"color scheme","summary":"Dirty industrial colorscheme.","3":"Dirty industrial colorscheme.","description":"Screenshots:\r\n  UNIX: http:\/\/imageshack.us\/photo\/my-images\/854\/toxicgtk.png\/\r\n  Win32: http:\/\/imageshack.us\/photo\/my-images\/339\/toxicq.png\/","4":"Screenshots:\r\n  UNIX: http:\/\/imageshack.us\/photo\/my-images\/854\/toxicgtk.png\/\r\n  Win32: http:\/\/imageshack.us\/photo\/my-images\/339\/toxicq.png\/","install_details":"Just cp it into \"$VIMRUNTIME\/colors\" \/ \"$VIM\/colors\" \/ \"other path from your rtp + '\/colors' \"","5":"Just cp it into \"$VIMRUNTIME\/colors\" \/ \"$VIM\/colors\" \/ \"other path from your rtp + '\/colors' \"","first_name":"Tamir","6":"Tamir","last_name":"Lavi","7":"Lavi","releases":[{"0":"3667","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"toxic.vim","4":"toxic.vim","src_id":"16131","5":"16131","creation_date":"1311481070","6":"1311481070"}]},"3666":{"script_id":"3666","0":"3666","script_name":"skyWeb","1":"skyWeb","script_type":"color scheme","2":"color scheme","summary":"A white, clean colorscheme made for CSS, HTML and PHP.","3":"A white, clean colorscheme made for CSS, HTML and PHP.","description":"A white, clean colorscheme made for CSS, HTML and PHP and increasingly more for javascript. Only for gui for the moment and only tested in MacVim 7.3.\r\n\r\nSee screenshots: http:\/\/www.stud.hio.no\/~s171172\/skyWeb.html\r\n\r\nAmong other features:\r\n\r\n-HTML tag, class and id colors match the CSS tag, class and id colors for easy recognition.\r\n-When you have HTML embedded in PHP I wanted the colors to clearly show the difference between the languages. This also goes for other embedded languages (I'm implementing as I stumble upon them).\r\n-Comfortable editing when swithching between applications.\r\n\r\nI have tried to find good colorschemes with a white background forever. The colorschemes pyte, google and macvim's default scheme, macvim, are the best ones I have found, but there is always something. If this scheme doesn't quite suite your needs I suggest trying one of those.\r\n\r\nThis colorscheme is designed to provide comfortable editing when swithching between applications. Switching between black and white backgrounds forces your eyes to adjust alot, and can be uncomfortable. Since most other applications and websites have white backgrounds, so does the skyWeb scheme. And besides, good colorschemes with dark backgrounds ain't hard to come by anyway. I also wanted the scheme to be good looking (you decide if I succeeded), so the colors are given a lot of thought and tests, and still is.\r\n\r\nFor the time being I mainly code in html(5), css and php, so this scheme has a focus there, but I will update it for other languages when I stumble upon them. Probably javascript, jquery and java next.","4":"A white, clean colorscheme made for CSS, HTML and PHP and increasingly more for javascript. Only for gui for the moment and only tested in MacVim 7.3.\r\n\r\nSee screenshots: http:\/\/www.stud.hio.no\/~s171172\/skyWeb.html\r\n\r\nAmong other features:\r\n\r\n-HTML tag, class and id colors match the CSS tag, class and id colors for easy recognition.\r\n-When you have HTML embedded in PHP I wanted the colors to clearly show the difference between the languages. This also goes for other embedded languages (I'm implementing as I stumble upon them).\r\n-Comfortable editing when swithching between applications.\r\n\r\nI have tried to find good colorschemes with a white background forever. The colorschemes pyte, google and macvim's default scheme, macvim, are the best ones I have found, but there is always something. If this scheme doesn't quite suite your needs I suggest trying one of those.\r\n\r\nThis colorscheme is designed to provide comfortable editing when swithching between applications. Switching between black and white backgrounds forces your eyes to adjust alot, and can be uncomfortable. Since most other applications and websites have white backgrounds, so does the skyWeb scheme. And besides, good colorschemes with dark backgrounds ain't hard to come by anyway. I also wanted the scheme to be good looking (you decide if I succeeded), so the colors are given a lot of thought and tests, and still is.\r\n\r\nFor the time being I mainly code in html(5), css and php, so this scheme has a focus there, but I will update it for other languages when I stumble upon them. Probably javascript, jquery and java next.","install_details":"Move to ~\/.vim\/colors\/","5":"Move to ~\/.vim\/colors\/","first_name":"Johan","6":"Johan","last_name":"Steinberg","7":"Steinberg","releases":[{"0":"3666","vim_version":"7.3","1":"7.3","script_version":"0.9","2":"0.9","version_comment":"Initial upload","3":"Initial upload","package":"skyWeb.vim","4":"skyWeb.vim","src_id":"16130","5":"16130","creation_date":"1311446857","6":"1311446857"}]},"3665":{"script_id":"3665","0":"3665","script_name":"repeat motion","1":"repeat motion","script_type":"utility","2":"utility","summary":"give vim support of repeat motion operations","3":"give vim support of repeat motion operations","description":"I change the script from http:\/\/www.vim.org\/scripts\/script.php?script_id=2174 to support repeat motions.\r\n\r\nthe following move motions are supported: \r\nk,j, h,l, w,b, W,B, e,E, ge,gE.\r\n","4":"I change the script from http:\/\/www.vim.org\/scripts\/script.php?script_id=2174 to support repeat motions.\r\n\r\nthe following move motions are supported: \r\nk,j, h,l, w,b, W,B, e,E, ge,gE.\r\n","install_details":"just put it under your vim\/plugin folder.","5":"just put it under your vim\/plugin folder.","first_name":"guo","6":"guo","last_name":"tuofeng","7":"tuofeng","releases":[{"0":"3665","vim_version":"7.2","1":"7.2","script_version":"1","2":"1","version_comment":"Initial upload","3":"Initial upload","package":"repmo.vim","4":"repmo.vim","src_id":"16127","5":"16127","creation_date":"1311328794","6":"1311328794"}]},"3664":{"script_id":"3664","0":"3664","script_name":"SnipMgr","1":"SnipMgr","script_type":"utility","2":"utility","summary":"A simple snippets manager for 'snipMate' Vim plugin","3":"A simple snippets manager for 'snipMate' Vim plugin","description":"SnipMgr provides a simple \"SnipMgr\" menu tree that allows you to easily\r\nmanage your snipMate snippets.  In addition, you can use the :SnipAdd,\r\n:SnipRemove and :SnipUpdate commands or the <leader>ssa, <leader>ssr,\r\nand <leader>ssu key bindings.\r\n\r\nUSAGE:\r\n\r\n*Adding snippets*\r\nJust select any strings in visual-mode, Select-mode or visual-block\r\nmode and call the :SnipAdd command by using the SnipMgr menu, command line,\r\nor default key binding <leader>ssa.\r\n\r\n*Removing snippets*\r\nFor removing already existing snippets use the :SnipRemove command or\r\n<leader>ssr key binding.\r\n\r\n*Updating the snippets list*\r\nIf you manually add any snippets for the current filetype, you can call the\r\n:SnipUpdate command and use these snippets instantly without restarting\r\nVim. Default key binding: <leader>ssu.\r\n\r\nREPOSITORY:\r\nhttps:\/\/github.com\/tlavi\/SnipMgr","4":"SnipMgr provides a simple \"SnipMgr\" menu tree that allows you to easily\r\nmanage your snipMate snippets.  In addition, you can use the :SnipAdd,\r\n:SnipRemove and :SnipUpdate commands or the <leader>ssa, <leader>ssr,\r\nand <leader>ssu key bindings.\r\n\r\nUSAGE:\r\n\r\n*Adding snippets*\r\nJust select any strings in visual-mode, Select-mode or visual-block\r\nmode and call the :SnipAdd command by using the SnipMgr menu, command line,\r\nor default key binding <leader>ssa.\r\n\r\n*Removing snippets*\r\nFor removing already existing snippets use the :SnipRemove command or\r\n<leader>ssr key binding.\r\n\r\n*Updating the snippets list*\r\nIf you manually add any snippets for the current filetype, you can call the\r\n:SnipUpdate command and use these snippets instantly without restarting\r\nVim. Default key binding: <leader>ssu.\r\n\r\nREPOSITORY:\r\nhttps:\/\/github.com\/tlavi\/SnipMgr","install_details":"Before installing SnipMgr you must install snipMate (vimscript #2540)\r\n\r\nWhen snipMate insatlled, download the snipmgr-x.x.zip and unzip it into your runtimepath directory.\r\nAfter snipMate is installed, download snipmgr-x.x.zip and unzip it into your\r\nruntimepath directory.\r\n\r\nYou should place the files as follows:\r\n>\r\n    <your_runtimepath>\/plugin\/snipmgr.vim\r\n    <your_runtimepath>\/doc\/snipmgr.txt\r\n<\r\nFor eay uninstallation, put the files into a new directory and just add the\r\ndirectory path to the rtp variable into your .vimrc:\r\n>\r\n    :set rtp+=<new_directory_path>\r\n<\r\n\r\nThen update your help tag files using the :helptags command:\r\n>\r\n    :helptags $VIMRUNTIME\/doc\r\n<\r\nor (if you install the plugin into the <new_directory_path>)\r\n>\r\n    :helptags <new_directory_path>\/doc\r\n<","5":"Before installing SnipMgr you must install snipMate (vimscript #2540)\r\n\r\nWhen snipMate insatlled, download the snipmgr-x.x.zip and unzip it into your runtimepath directory.\r\nAfter snipMate is installed, download snipmgr-x.x.zip and unzip it into your\r\nruntimepath directory.\r\n\r\nYou should place the files as follows:\r\n>\r\n    <your_runtimepath>\/plugin\/snipmgr.vim\r\n    <your_runtimepath>\/doc\/snipmgr.txt\r\n<\r\nFor eay uninstallation, put the files into a new directory and just add the\r\ndirectory path to the rtp variable into your .vimrc:\r\n>\r\n    :set rtp+=<new_directory_path>\r\n<\r\n\r\nThen update your help tag files using the :helptags command:\r\n>\r\n    :helptags $VIMRUNTIME\/doc\r\n<\r\nor (if you install the plugin into the <new_directory_path>)\r\n>\r\n    :helptags <new_directory_path>\/doc\r\n<","first_name":"Tamir","6":"Tamir","last_name":"Lavi","7":"Lavi","releases":[{"0":"3664","vim_version":"7.0","1":"7.0","script_version":"1.2","2":"1.2","version_comment":"- Fixed: updating snippets list after deleting.\r\n- Fixed: redundant message when adding one-string snippet.","3":"- Fixed: updating snippets list after deleting.\r\n- Fixed: redundant message when adding one-string snippet.","package":"snipmgr-1.2.zip","4":"snipmgr-1.2.zip","src_id":"16450","5":"16450","creation_date":"1315132274","6":"1315132274"},{"0":"3664","vim_version":"7.0","1":"7.0","script_version":"1.1","2":"1.1","version_comment":"Initial upload","3":"Initial upload","package":"snipmgr-1.1.zip","4":"snipmgr-1.1.zip","src_id":"16123","5":"16123","creation_date":"1311262495","6":"1311262495"}]},"3663":{"script_id":"3663","0":"3663","script_name":"lemon.vim","1":"lemon.vim","script_type":"syntax","2":"syntax","summary":"syntax file for Lemon Parser Generator","3":"syntax file for Lemon Parser Generator","description":"syntax highlighting in Vim for Lemon Parser Generator grammars.","4":"syntax highlighting in Vim for Lemon Parser Generator grammars.","install_details":"Put syntax\/lemon.vim in ~\/.vim\/syntax, and ftdetect\/lemon.vim in ~\/.vim\/ftdetect\/\r\noptionally add autocmd FileType lemon set nocindent noai indentkeys= to ~\/.vimrc to prevent autoindent.","5":"Put syntax\/lemon.vim in ~\/.vim\/syntax, and ftdetect\/lemon.vim in ~\/.vim\/ftdetect\/\r\noptionally add autocmd FileType lemon set nocindent noai indentkeys= to ~\/.vimrc to prevent autoindent.","first_name":"chengcheng","6":"chengcheng","last_name":"dong","7":"dong","releases":[{"0":"3663","vim_version":"6.0","1":"6.0","script_version":"1.1","2":"1.1","version_comment":"add some c syntax","3":"add some c syntax","package":"vim-lemon-syntax.zip","4":"vim-lemon-syntax.zip","src_id":"16125","5":"16125","creation_date":"1311322430","6":"1311322430"},{"0":"3663","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"vim-lemon-syntax.zip","4":"vim-lemon-syntax.zip","src_id":"16118","5":"16118","creation_date":"1311228379","6":"1311228379"}]},"3662":{"script_id":"3662","0":"3662","script_name":"Intelligent Tags","1":"Intelligent Tags","script_type":"utility","2":"utility","summary":"Automated Tag creation\/inclusion","3":"Automated Tag creation\/inclusion","description":"Project Home: https:\/\/github.com\/bahejl\/Intelligent_Tags\r\n\r\nIntelligent Tags is designed to handle creating tags and setting the 'tag'\r\noption for you.  Tradionally, you would run ctags on your project at regular\r\nintervals (or in a cron job), but I struggled with this approach for several\r\nreasons:\r\n* I'm initially not familiar with the project structure of many of the\r\nprojects I work on, so I have to chase down the includes until I feel\r\ncomfortable that I know where the project ends\/begins before I can create a\r\nuseful tags files.  This is a large overhead, and prevents me from using tags\r\nwhen I need them the most.\r\n* As I actively work on a project, updating the tags once a day, or even\r\nevery hour, just doesn't cut it.  I would like the tags to be updated as\r\nsoon as the file is updated.\r\n\r\n\r\nIntelligent Tags solves these problems by using two tools.  First, it uses\r\nVim's built-in options 'include', and 'includeexpr' to find any\/all\r\ninclude files, and then searches those includes for includes, etc. The depth of this search\r\ncan be set by the user to any level using the |Itags_Depth| variable.  To save\r\ntime, Intelligent Tags will create an .incl file for every file examined.\r\nThis file is simply a cache that lets Intelligent Tags avoid re-scanning for\r\ninclude files unless it is necessary.  In order for  any of this to work\r\nproperly, Vim's path option must be set correctly.  You can check if it is\r\ncorrect by running the Vim command |:checkpath|.  If you use Intelligent Tags\r\nwith an incorrect path, the information stored in the cached .incl files\r\nwill be incorrect, and you will need to run the |ItagsRegenIncl| command after\r\ncorrecting your path to correct the cached informaiton.  For more\r\ninformation on setting your path type ':h path'.\r\n\r\nThe second tool Intelligent Tags uses is exhuberant ctags.  Intelligent Tags\r\nuses exhuberant ctags' report of supported languages to automatically add a\r\nFileType autocommand for each type of supported file.  I want my tags\r\nupdated as soon as I make a change to a file, but if you use the tradional\r\nmethod of having a single tags file per project that can take quite a while\r\n-- especially for a large project.  To work around that problem, Intelligent\r\nTags creates a seperate tags file for each source file, and only updates\r\nthose that are out of date.\r\n\r\nThis methodolgy begins to break down for some languages, such as C, where\r\nthe following problems exist:\r\n* foo.c includes bar.h, followed by baz.h, so (almost magically) everything\r\nin bar.h is available to baz.h.  Because Intelligent Tags works on a\r\nper-file and not per-project basis, it is impossible (as far as I can tell)\r\nfor Intelligent Tags to know that bar.h's tags should be included based only\r\non the information in baz.h.\r\n* foo.c includes bar.h, which contains externals defined in bar.c.\r\nIntelligent Tags works around this problem by allowing for a special\r\n|Itags_header_mapping| option.  If this is defined, when Intelligent Tags finds any\r\nincluded file whose extension is recognized as a header, it will search for\r\na source file of the same name and include its tags as well.\r\n\r\nIn the end, when you open any exhuberant ctags supported file, intelligent\r\nTags will generate any tags files necessary and update the 'tags'\r\noption for you -- you don't have to do a thing!","4":"Project Home: https:\/\/github.com\/bahejl\/Intelligent_Tags\r\n\r\nIntelligent Tags is designed to handle creating tags and setting the 'tag'\r\noption for you.  Tradionally, you would run ctags on your project at regular\r\nintervals (or in a cron job), but I struggled with this approach for several\r\nreasons:\r\n* I'm initially not familiar with the project structure of many of the\r\nprojects I work on, so I have to chase down the includes until I feel\r\ncomfortable that I know where the project ends\/begins before I can create a\r\nuseful tags files.  This is a large overhead, and prevents me from using tags\r\nwhen I need them the most.\r\n* As I actively work on a project, updating the tags once a day, or even\r\nevery hour, just doesn't cut it.  I would like the tags to be updated as\r\nsoon as the file is updated.\r\n\r\n\r\nIntelligent Tags solves these problems by using two tools.  First, it uses\r\nVim's built-in options 'include', and 'includeexpr' to find any\/all\r\ninclude files, and then searches those includes for includes, etc. The depth of this search\r\ncan be set by the user to any level using the |Itags_Depth| variable.  To save\r\ntime, Intelligent Tags will create an .incl file for every file examined.\r\nThis file is simply a cache that lets Intelligent Tags avoid re-scanning for\r\ninclude files unless it is necessary.  In order for  any of this to work\r\nproperly, Vim's path option must be set correctly.  You can check if it is\r\ncorrect by running the Vim command |:checkpath|.  If you use Intelligent Tags\r\nwith an incorrect path, the information stored in the cached .incl files\r\nwill be incorrect, and you will need to run the |ItagsRegenIncl| command after\r\ncorrecting your path to correct the cached informaiton.  For more\r\ninformation on setting your path type ':h path'.\r\n\r\nThe second tool Intelligent Tags uses is exhuberant ctags.  Intelligent Tags\r\nuses exhuberant ctags' report of supported languages to automatically add a\r\nFileType autocommand for each type of supported file.  I want my tags\r\nupdated as soon as I make a change to a file, but if you use the tradional\r\nmethod of having a single tags file per project that can take quite a while\r\n-- especially for a large project.  To work around that problem, Intelligent\r\nTags creates a seperate tags file for each source file, and only updates\r\nthose that are out of date.\r\n\r\nThis methodolgy begins to break down for some languages, such as C, where\r\nthe following problems exist:\r\n* foo.c includes bar.h, followed by baz.h, so (almost magically) everything\r\nin bar.h is available to baz.h.  Because Intelligent Tags works on a\r\nper-file and not per-project basis, it is impossible (as far as I can tell)\r\nfor Intelligent Tags to know that bar.h's tags should be included based only\r\non the information in baz.h.\r\n* foo.c includes bar.h, which contains externals defined in bar.c.\r\nIntelligent Tags works around this problem by allowing for a special\r\n|Itags_header_mapping| option.  If this is defined, when Intelligent Tags finds any\r\nincluded file whose extension is recognized as a header, it will search for\r\na source file of the same name and include its tags as well.\r\n\r\nIn the end, when you open any exhuberant ctags supported file, intelligent\r\nTags will generate any tags files necessary and update the 'tags'\r\noption for you -- you don't have to do a thing!","install_details":"You must have exhuberant ctags (http:\/\/ctags.sourceforge.net\/) installed.\r\nUncompress intelliTags.vim.gz, open it in vim, and then type \":so%\"","5":"You must have exhuberant ctags (http:\/\/ctags.sourceforge.net\/) installed.\r\nUncompress intelliTags.vim.gz, open it in vim, and then type \":so%\"","first_name":"Stephen","6":"Stephen","last_name":"Bell","7":"Bell","releases":[{"0":"3662","vim_version":"7.0","1":"7.0","script_version":"0.2","2":"0.2","version_comment":"* Added Documenation\r\n* Now distributing as a vimball","3":"* Added Documenation\r\n* Now distributing as a vimball","package":"intelliTags.vba.gz","4":"intelliTags.vba.gz","src_id":"16142","5":"16142","creation_date":"1311647162","6":"1311647162"},{"0":"3662","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"intelliTags.vim","4":"intelliTags.vim","src_id":"16117","5":"16117","creation_date":"1311219760","6":"1311219760"}]},"3661":{"script_id":"3661","0":"3661","script_name":"Lookup","1":"Lookup","script_type":"ftplugin","2":"ftplugin","summary":"ftplugin for vim files to quickly find element definition, occurrences, or docs","3":"ftplugin for vim files to quickly find element definition, occurrences, or docs","description":"Lookup is a plugin for vim script developers which provides functionality to\r\nquickly and easily lookup docs for vim elements, or in the case of user defined\r\nfunctions, commands, or variables, find the definition or occurrences of the\r\nelement.\r\n\r\nWhile editing a vim file, you can lookup the element under the cursor using:\r\n\r\n    :Lookup\r\n\r\nYou can also map this command so that you simply need to hit <cr> on an element\r\nto look it up by adding the following to a ftplugin\/vim_lookup.vim file in your\r\nvimfiles directory (%HOME%\/vimfiles on Windows, ~\/.vim on Linux\/OSX):\r\n\r\n  if bufname('%') !~ '^\\(command-line\\|\\[Command Line\\]\\)$'\r\n    nnoremap <silent> <buffer> <cr> :Lookup<cr>\r\n  endif\r\n\r\nFor more details please see the lookup vim docs (:help lookup).\r\n\r\nhttp:\/\/github.com\/ervandew\/lookup","4":"Lookup is a plugin for vim script developers which provides functionality to\r\nquickly and easily lookup docs for vim elements, or in the case of user defined\r\nfunctions, commands, or variables, find the definition or occurrences of the\r\nelement.\r\n\r\nWhile editing a vim file, you can lookup the element under the cursor using:\r\n\r\n    :Lookup\r\n\r\nYou can also map this command so that you simply need to hit <cr> on an element\r\nto look it up by adding the following to a ftplugin\/vim_lookup.vim file in your\r\nvimfiles directory (%HOME%\/vimfiles on Windows, ~\/.vim on Linux\/OSX):\r\n\r\n  if bufname('%') !~ '^\\(command-line\\|\\[Command Line\\]\\)$'\r\n    nnoremap <silent> <buffer> <cr> :Lookup<cr>\r\n  endif\r\n\r\nFor more details please see the lookup vim docs (:help lookup).\r\n\r\nhttp:\/\/github.com\/ervandew\/lookup","install_details":"1. Download the vimball (lookup.vba) to any directory.\r\n2. Open the file in vim ($ vim lookup.vba)\r\n3. Source the file (:so %)","5":"1. Download the vimball (lookup.vba) to any directory.\r\n2. Open the file in vim ($ vim lookup.vba)\r\n3. Source the file (:so %)","first_name":"Eric","6":"Eric","last_name":"Van Dewoestine","7":"Van Dewoestine","releases":[{"0":"3661","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"lookup.vba","4":"lookup.vba","src_id":"16103","5":"16103","creation_date":"1311137777","6":"1311137777"}]},"3660":{"script_id":"3660","0":"3660","script_name":"ldap_schema.vim","1":"ldap_schema.vim","script_type":"syntax","2":"syntax","summary":"ldap schmema definition language","3":"ldap schmema definition language","description":"Extended version of <http:\/\/www.vim.org\/scripts\/script.php?script_id=653> from \"binary runner\", whos email address is disabled.\r\n* lots of additional keywords added","4":"Extended version of <http:\/\/www.vim.org\/scripts\/script.php?script_id=653> from \"binary runner\", whos email address is disabled.\r\n* lots of additional keywords added","install_details":"","5":"","first_name":"Philipp","6":"Philipp","last_name":"Hahn","7":"Hahn","releases":[{"0":"3660","vim_version":"6.0","1":"6.0","script_version":"0.2","2":"0.2","version_comment":"Initial upload","3":"Initial upload","package":"ldap_schema.vim","4":"ldap_schema.vim","src_id":"16090","5":"16090","creation_date":"1310982675","6":"1310982675"}]},"3659":{"script_id":"3659","0":"3659","script_name":"LycosaExplorer","1":"LycosaExplorer","script_type":"utility","2":"utility","summary":"A dynamic filesystem and buffer explorer","3":"A dynamic filesystem and buffer explorer","description":"Originally a simple port of LustyExplorer (vimscript #1890) to Python.\r\n\r\nBasic keybindings are <leader>lf to open a file with the starting directory being the current working dir, <leader>lr to do so but at the current buffer's directory and <leader>lb to access your buffers. Further bindings and instructions are found in lycosaexplorer.vim\r\n\r\nThis project is also available on bitbucket at https:\/\/bitbucket.org\/mikehart\/lycosaexplorer","4":"Originally a simple port of LustyExplorer (vimscript #1890) to Python.\r\n\r\nBasic keybindings are <leader>lf to open a file with the starting directory being the current working dir, <leader>lr to do so but at the current buffer's directory and <leader>lb to access your buffers. Further bindings and instructions are found in lycosaexplorer.vim\r\n\r\nThis project is also available on bitbucket at https:\/\/bitbucket.org\/mikehart\/lycosaexplorer","install_details":"For pathogen users: Unpack the zip directly into your bundle directory\r\n\r\nFor everyone else: Copy lycosaexplorer.vim and lycosa.py from lycosaexplorer\/plugin into your plugin directory","5":"For pathogen users: Unpack the zip directly into your bundle directory\r\n\r\nFor everyone else: Copy lycosaexplorer.vim and lycosa.py from lycosaexplorer\/plugin into your plugin directory","first_name":"Michael","6":"Michael","last_name":"Hart","7":"Hart","releases":[{"0":"3659","vim_version":"7.3","1":"7.3","script_version":"0.9","2":"0.9","version_comment":"Use a callback function to call out to another program\/script\r\nThis provides the user the ability to rapidly navigate to a particular\r\ndirectory then explore that with NERDTree or any other function for filesystem\r\nmanipulation etc. See the comments in lycosaexplorer.vim for more details.","3":"Use a callback function to call out to another program\/script\r\nThis provides the user the ability to rapidly navigate to a particular\r\ndirectory then explore that with NERDTree or any other function for filesystem\r\nmanipulation etc. See the comments in lycosaexplorer.vim for more details.","package":"lycosaexplorer.zip","4":"lycosaexplorer.zip","src_id":"17230","5":"17230","creation_date":"1326751066","6":"1326751066"},{"0":"3659","vim_version":"7.3","1":"7.3","script_version":"0.8","2":"0.8","version_comment":" * Added cursor navigation to file list panel (also accessible with C-b, C-f, Cn and C-p)\r\n * Cleaned up code to cut down on pyflakes warnings and simplify a few bits and pieces\r\n * Fixed error when attempting to next\/previous on an empty file list\r\n * Added ability to start lycosa at a given file location - :LycosaFilesystemExplorer \/some\/path\/here\r\n * Added ability to disable default mappings by setting g:LycosaExplorerDefaultMappings to something other than 1","3":" * Added cursor navigation to file list panel (also accessible with C-b, C-f, Cn and C-p)\r\n * Cleaned up code to cut down on pyflakes warnings and simplify a few bits and pieces\r\n * Fixed error when attempting to next\/previous on an empty file list\r\n * Added ability to start lycosa at a given file location - :LycosaFilesystemExplorer \/some\/path\/here\r\n * Added ability to disable default mappings by setting g:LycosaExplorerDefaultMappings to something other than 1","package":"lycosaexplorer.zip","4":"lycosaexplorer.zip","src_id":"17229","5":"17229","creation_date":"1326736769","6":"1326736769"},{"0":"3659","vim_version":"7.3","1":"7.3","script_version":"0.6","2":"0.6","version_comment":"Moved from using nmap to nnoremap to avoid issues when people have remapped :","3":"Moved from using nmap to nnoremap to avoid issues when people have remapped :","package":"lycosaexplorer.zip","4":"lycosaexplorer.zip","src_id":"16724","5":"16724","creation_date":"1319308766","6":"1319308766"}]},"3658":{"script_id":"3658","0":"3658","script_name":"Powershell FTDetect","1":"Powershell FTDetect","script_type":"ftplugin","2":"ftplugin","summary":"ftdetect plugin for Powershell files","3":"ftdetect plugin for Powershell files","description":"Provides initial ftdetect support for Powershell files.  Best used with the Windows Powershell Syntax File, Windows PowerShell Indent file and Filetype Plugin file (vimscript#1327, vimscript #1815 and vimscript #1816).","4":"Provides initial ftdetect support for Powershell files.  Best used with the Windows Powershell Syntax File, Windows PowerShell Indent file and Filetype Plugin file (vimscript#1327, vimscript #1815 and vimscript #1816).","install_details":"Copy this file into your VIM ftdetect folder (either $home\\vimfiles\\ftdetect or $ProgramFiles\\vim\\vimfiles\\ftdetect).","5":"Copy this file into your VIM ftdetect folder (either $home\\vimfiles\\ftdetect or $ProgramFiles\\vim\\vimfiles\\ftdetect).","first_name":"ian","6":"ian","last_name":"koenig","7":"koenig","releases":[{"0":"3658","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"ps1.vim","4":"ps1.vim","src_id":"16067","5":"16067","creation_date":"1310405392","6":"1310405392"}]},"3656":{"script_id":"3656","0":"3656","script_name":"transpose-words","1":"transpose-words","script_type":"utility","2":"utility","summary":"Swap two words as M-t (transpose-words) in Emacs or bash.","3":"Swap two words as M-t (transpose-words) in Emacs or bash.","description":"Swap two words. Simulate the M-t (transpose-words) in Emacs or Bash.\r\n\r\nUsage:\r\n  Just press <M-t> (Alt-t) in insert mode, normal mode or command-line.\r\n  count is also supported. 8<M-t> will push the word befor the cursor right 8 times\r\n  repeat.vim (vimscript #2136) is also supported. When it present, press dot\r\n  (.) in nornal mode will repeat the this function.\r\n\r\nNote:\r\nIn gvim, <M-t> may open menu, this can be disabled by \r\n:set winaltkeys=no\r\nIn the console, <M-t> may just doesn't work, you can enable it by\r\n:exec \"set <M-t>=\\<Esc>t\"\r\nIn some terminal such as gnome-terminal, <M-t> may open the menu of the\r\nterminal, this can be disable in the configuration of the terminal.\r\n\r\nor you may change the <M-t> to other keys such as <Leader>t\r\n:nmap <Leader>t <Plug>Transposewords\r\n:imap <Leader>t <Plug>Transposewords\r\n:cmap <Leader>t <Plug>Transposewords\r\nTypically, <Leader> is slash '\\\\', you can press \\t to do the same work.\r\nPut these in startup file as you like.\r\n\r\nThis script act more liky M-t in Bash than M-t in Emacs.\r\n\r\nI have checked http:\/\/vim.wikia.com\/wiki\/VimTip47 and swap (vimscript #3250.)\r\nIn these solutions, either changes cannot be undo nicely, or the search history\r\nare changed, and many other difference from the M-t in bash.\r\n\r\nAdvantages:\r\n  1. `foo| != ba|r`: when the cursor is between two bar ('|'), and M-t\r\n     pressed, `foo` and `bar` will be transposed. (same as in bash)\r\n  2. `bar foo|`: when the two words are transposed, the cursor will be\r\n     right after the second word `foo`. (same as in bash)\r\n  3. Correctly undo the cursor position.\r\n  4. Does not change the search ('\/' or '?') history.\r\n  5. Also work on command-line.\r\n     Note: On a input() command-line with '=' prompt, it does not work.\r\n  6. The pattern which match the words are customizable. (default '\\k\\+',\r\n     set g:transwrd_wordpattern in startup file.)\r\n","4":"Swap two words. Simulate the M-t (transpose-words) in Emacs or Bash.\r\n\r\nUsage:\r\n  Just press <M-t> (Alt-t) in insert mode, normal mode or command-line.\r\n  count is also supported. 8<M-t> will push the word befor the cursor right 8 times\r\n  repeat.vim (vimscript #2136) is also supported. When it present, press dot\r\n  (.) in nornal mode will repeat the this function.\r\n\r\nNote:\r\nIn gvim, <M-t> may open menu, this can be disabled by \r\n:set winaltkeys=no\r\nIn the console, <M-t> may just doesn't work, you can enable it by\r\n:exec \"set <M-t>=\\<Esc>t\"\r\nIn some terminal such as gnome-terminal, <M-t> may open the menu of the\r\nterminal, this can be disable in the configuration of the terminal.\r\n\r\nor you may change the <M-t> to other keys such as <Leader>t\r\n:nmap <Leader>t <Plug>Transposewords\r\n:imap <Leader>t <Plug>Transposewords\r\n:cmap <Leader>t <Plug>Transposewords\r\nTypically, <Leader> is slash '\\\\', you can press \\t to do the same work.\r\nPut these in startup file as you like.\r\n\r\nThis script act more liky M-t in Bash than M-t in Emacs.\r\n\r\nI have checked http:\/\/vim.wikia.com\/wiki\/VimTip47 and swap (vimscript #3250.)\r\nIn these solutions, either changes cannot be undo nicely, or the search history\r\nare changed, and many other difference from the M-t in bash.\r\n\r\nAdvantages:\r\n  1. `foo| != ba|r`: when the cursor is between two bar ('|'), and M-t\r\n     pressed, `foo` and `bar` will be transposed. (same as in bash)\r\n  2. `bar foo|`: when the two words are transposed, the cursor will be\r\n     right after the second word `foo`. (same as in bash)\r\n  3. Correctly undo the cursor position.\r\n  4. Does not change the search ('\/' or '?') history.\r\n  5. Also work on command-line.\r\n     Note: On a input() command-line with '=' prompt, it does not work.\r\n  6. The pattern which match the words are customizable. (default '\\k\\+',\r\n     set g:transwrd_wordpattern in startup file.)\r\n","install_details":"Just put it in to the plugin directory. (e.g. ~\/.vim\/plugin)","5":"Just put it in to the plugin directory. (e.g. ~\/.vim\/plugin)","first_name":"fermat","6":"fermat","last_name":"618","7":"618","releases":[{"0":"3656","vim_version":"6.0","1":"6.0","script_version":"1.1","2":"1.1","version_comment":"count is supported now. 8<M-t> will do the right thing.\r\nrepeat.vim (vimscript #2136) is supported.","3":"count is supported now. 8<M-t> will do the right thing.\r\nrepeat.vim (vimscript #2136) is supported.","package":"transwrd.vim","4":"transwrd.vim","src_id":"16049","5":"16049","creation_date":"1310044933","6":"1310044933"},{"0":"3656","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"transwrd.vim","4":"transwrd.vim","src_id":"16042","5":"16042","creation_date":"1309944632","6":"1309944632"}]},"3655":{"script_id":"3655","0":"3655","script_name":"xorium.vim","1":"xorium.vim","script_type":"color scheme","2":"color scheme","summary":"Colorful, dark background, unobtrusive invisibles, 256 colors","3":"Colorful, dark background, unobtrusive invisibles, 256 colors","description":"Xorium is a colorful and easy to read color scheme featuring easily identifiable syntax highlighting and unobtrusive invisibles (for when you have :set list).\r\n\r\nBased off of Dmitriy Zotikov's original theme, xoria256: http:\/\/www.vim.org\/scripts\/script.php?script_id=2140\r\n\r\nScreen shots (showing cursorline):\r\nJava    - http:\/\/i.imgur.com\/aGe4b.png\r\n.vimrc  - http:\/\/i.imgur.com\/RAc0z.png (with invisibles)\r\nvimdiff  - http:\/\/i.imgur.com\/eT65o.png\r\n\r\nThe font used in the screen shots is the free \"Anonymous Pro\" (http:\/\/www.ms-studio.com\/FontSales\/anonymouspro.html).","4":"Xorium is a colorful and easy to read color scheme featuring easily identifiable syntax highlighting and unobtrusive invisibles (for when you have :set list).\r\n\r\nBased off of Dmitriy Zotikov's original theme, xoria256: http:\/\/www.vim.org\/scripts\/script.php?script_id=2140\r\n\r\nScreen shots (showing cursorline):\r\nJava    - http:\/\/i.imgur.com\/aGe4b.png\r\n.vimrc  - http:\/\/i.imgur.com\/RAc0z.png (with invisibles)\r\nvimdiff  - http:\/\/i.imgur.com\/eT65o.png\r\n\r\nThe font used in the screen shots is the free \"Anonymous Pro\" (http:\/\/www.ms-studio.com\/FontSales\/anonymouspro.html).","install_details":"Just put xorium.vim in your .vim\/colors folder (or vimfiles\/colors on Windows) if you use gvim or your terminal is already 256 color compatible.\r\nTo enable 256 color terminal on some Linux distributions (ex. Ubuntu), install ncurses-term if you don't already have it installed, then add\r\n\r\nif [ \"$COLORTERM\" == \"gnome-terminal\" ]; then \r\n    export TERM=xterm-256color \r\nfi\r\n\r\nto you .bashrc file to make the terminal always identify itself as 256 color capable.\r\n\r\nNote: This color scheme does not work with non-256 color compatible terminals.","5":"Just put xorium.vim in your .vim\/colors folder (or vimfiles\/colors on Windows) if you use gvim or your terminal is already 256 color compatible.\r\nTo enable 256 color terminal on some Linux distributions (ex. Ubuntu), install ncurses-term if you don't already have it installed, then add\r\n\r\nif [ \"$COLORTERM\" == \"gnome-terminal\" ]; then \r\n    export TERM=xterm-256color \r\nfi\r\n\r\nto you .bashrc file to make the terminal always identify itself as 256 color capable.\r\n\r\nNote: This color scheme does not work with non-256 color compatible terminals.","first_name":"L","6":"L","last_name":"C","7":"C","releases":[{"0":"3655","vim_version":"5.7","1":"5.7","script_version":"1.05","2":"1.05","version_comment":"Big changes to MatchParen and TODO coloring. Minor changes to Search, NonText (end of file '~'s, invisibles), SpecialKey (more invisibles) and Visual selection colors.","3":"Big changes to MatchParen and TODO coloring. Minor changes to Search, NonText (end of file '~'s, invisibles), SpecialKey (more invisibles) and Visual selection colors.","package":"xorium.vim","4":"xorium.vim","src_id":"16047","5":"16047","creation_date":"1310011436","6":"1310011436"},{"0":"3655","vim_version":"5.7","1":"5.7","script_version":"1.01","2":"1.01","version_comment":"Fixed a tiny naming error","3":"Fixed a tiny naming error","package":"xorium.vim","4":"xorium.vim","src_id":"16038","5":"16038","creation_date":"1309928655","6":"1309928655"},{"0":"3655","vim_version":"5.7","1":"5.7","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"xorium.vim","4":"xorium.vim","src_id":"16037","5":"16037","creation_date":"1309921931","6":"1309921931"}]},"3654":{"script_id":"3654","0":"3654","script_name":"vrackets","1":"vrackets","script_type":"utility","2":"utility","summary":"automatically close different kinds of brackets","3":"automatically close different kinds of brackets","description":"Vrackets helps you a lot by auto-closing the brackets you type.\r\nFor instance, if you type \"(\", you get:\r\n    (|)\r\n(\"|\" is the cursor.)\r\nYou can easily get out of the brackets by typing the closing bracket. If after that you type \")\", you get:\r\n    ()|\r\nLastly, brackets are auto-deleted if they are empty. For instance, if your screen looks like this:\r\n    FooBar(|)\r\nAnd you press backspace, you get this:\r\n    FooBar|\r\n\r\nBy default it works for (), [], {}, \"\" and ''. It also works for \u00c2\u00a1! and \u00c2\u00bf?, for spanish speakers ;).\r\nYou can add more easily if you want (like <>, but I wouldn't recommend it unless for html\/xml\/etc).","4":"Vrackets helps you a lot by auto-closing the brackets you type.\r\nFor instance, if you type \"(\", you get:\r\n    (|)\r\n(\"|\" is the cursor.)\r\nYou can easily get out of the brackets by typing the closing bracket. If after that you type \")\", you get:\r\n    ()|\r\nLastly, brackets are auto-deleted if they are empty. For instance, if your screen looks like this:\r\n    FooBar(|)\r\nAnd you press backspace, you get this:\r\n    FooBar|\r\n\r\nBy default it works for (), [], {}, \"\" and ''. It also works for \u00c2\u00a1! and \u00c2\u00bf?, for spanish speakers ;).\r\nYou can add more easily if you want (like <>, but I wouldn't recommend it unless for html\/xml\/etc).","install_details":"Download it and use :source path\/to\/the\/script\/vrackets.vim to try it.\r\nIf you want it to load automatically every time you start vim, put it in ~\/.vim\/plugin, or $HOME\\vimfiles\\plugin if you use Windows.","5":"Download it and use :source path\/to\/the\/script\/vrackets.vim to try it.\r\nIf you want it to load automatically every time you start vim, put it in ~\/.vim\/plugin, or $HOME\\vimfiles\\plugin if you use Windows.","first_name":"Gerardo","6":"Gerardo","last_name":"Marset","7":"Marset","releases":[{"0":"3654","vim_version":"7.0","1":"7.0","script_version":"0.2.3","2":"0.2.3","version_comment":"Prevent annoyances by choosing a bit more smartly whether brackets should be auto-closed or not.","3":"Prevent annoyances by choosing a bit more smartly whether brackets should be auto-closed or not.","package":"vrackets.vim","4":"vrackets.vim","src_id":"16753","5":"16753","creation_date":"1319738030","6":"1319738030"},{"0":"3654","vim_version":"7.0","1":"7.0","script_version":"0.2.2","2":"0.2.2","version_comment":"Fixed a bug.","3":"Fixed a bug.","package":"vrackets.vim","4":"vrackets.vim","src_id":"16421","5":"16421","creation_date":"1314828171","6":"1314828171"},{"0":"3654","vim_version":"7.0","1":"7.0","script_version":"0.2.1","2":"0.2.1","version_comment":"Optimized the code a bit.\r\nAlso now the script won't modify the default register when deleting empty brackets.","3":"Optimized the code a bit.\r\nAlso now the script won't modify the default register when deleting empty brackets.","package":"vrackets.vim","4":"vrackets.vim","src_id":"16414","5":"16414","creation_date":"1314814620","6":"1314814620"},{"0":"3654","vim_version":"7.0","1":"7.0","script_version":"0.2","2":"0.2","version_comment":"Added support for quotation marks and other pairs in which the opening symbol is the same as the closing one.","3":"Added support for quotation marks and other pairs in which the opening symbol is the same as the closing one.","package":"vrackets.vim","4":"vrackets.vim","src_id":"16300","5":"16300","creation_date":"1313798350","6":"1313798350"},{"0":"3654","vim_version":"7.0","1":"7.0","script_version":"0.1.1","2":"0.1.1","version_comment":"Fixed a small bug.","3":"Fixed a small bug.","package":"vrackets.vim","4":"vrackets.vim","src_id":"16045","5":"16045","creation_date":"1309989565","6":"1309989565"},{"0":"3654","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"vrackets.vim","4":"vrackets.vim","src_id":"16036","5":"16036","creation_date":"1309914670","6":"1309914670"}]},"3653":{"script_id":"3653","0":"3653","script_name":"brep","1":"brep","script_type":"utility","2":"utility","summary":"Scan certain buffers for a regexp and save the result as quickfix list","3":"Scan certain buffers for a regexp and save the result as quickfix list","description":"Yet another buffer \"grep\". This plugin provides the following command:\r\n\r\nBrep[!] REGEXP\r\n    Scan buffers for REGEXP.\r\n    With the optional bang '!', scan unlisted buffers too.\r\n","4":"Yet another buffer \"grep\". This plugin provides the following command:\r\n\r\nBrep[!] REGEXP\r\n    Scan buffers for REGEXP.\r\n    With the optional bang '!', scan unlisted buffers too.\r\n","install_details":"In order to install the vba, open the vba file in VIM and type: >\r\n\r\n    :so %\r\n\r\nSee :help vimball for details.\r\n\r\nOptional enhancement: trag (vimscript #2033)\r\n\r\nAlso available via git: http:\/\/github.com\/tomtom\/brep_vim\/\r\n","5":"In order to install the vba, open the vba file in VIM and type: >\r\n\r\n    :so %\r\n\r\nSee :help vimball for details.\r\n\r\nOptional enhancement: trag (vimscript #2033)\r\n\r\nAlso available via git: http:\/\/github.com\/tomtom\/brep_vim\/\r\n","first_name":"Tom","6":"Tom","last_name":"Link","7":"Link","releases":[{"0":"3653","vim_version":"7.0","1":"7.0","script_version":"0.02","2":"0.02","version_comment":"- Remove dependencies on tlib\n- Optionally use :bufdo (if g:brep#use_bufdo = 1)\n- Automatically use :bufdo if the pattern contains \\n\nMD5 checksum: 37ca19d799be1d68bfd238c8155caf9a","3":"- Remove dependencies on tlib\n- Optionally use :bufdo (if g:brep#use_bufdo = 1)\n- Automatically use :bufdo if the pattern contains \\n\nMD5 checksum: 37ca19d799be1d68bfd238c8155caf9a","package":"brep.vba","4":"brep.vba","src_id":"16048","5":"16048","creation_date":"1310028408","6":"1310028408"},{"0":"3653","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"brep.vba","4":"brep.vba","src_id":"16031","5":"16031","creation_date":"1309841661","6":"1309841661"}]},"3652":{"script_id":"3652","0":"3652","script_name":"vim-task-org","1":"vim-task-org","script_type":"utility","2":"utility","summary":"Manipulate TODO\/FIXME\/etc marks (tasks) in your sources.","3":"Manipulate TODO\/FIXME\/etc marks (tasks) in your sources.","description":"Vim-task-org is a plugin for Vim to manipulate `TODO, FIXME` (and more) marks in your sources.\r\n\r\n## Dependencies\r\n  \r\n  * Vim\r\n  * Ruby support for vim\r\n\r\n## Usage\r\n  \r\n  Send vim the commands:\r\n\r\n  * `:Di` - date insert\r\n  * `:Ti` - task insert\r\n  * `:Vt` - view tasks\r\n  * `:Jt` - jump to task\r\n\r\n  Alternatively, bind to `:Di, :Ti, :Vt, :Jt` to a key binding:\r\n\r\n    map <leader>d :Di<CR>\r\n    map <leader>t :Ti<CR>\r\n    map <F5> :Vt<CR>\r\n    map <C-CR> :Jt<CR>\r\n\r\n## Bugs\r\n\r\n  Bugs are tracked through \"http:\/\/github.com\/iflo0\/vim-task-org\/issues\" ","4":"Vim-task-org is a plugin for Vim to manipulate `TODO, FIXME` (and more) marks in your sources.\r\n\r\n## Dependencies\r\n  \r\n  * Vim\r\n  * Ruby support for vim\r\n\r\n## Usage\r\n  \r\n  Send vim the commands:\r\n\r\n  * `:Di` - date insert\r\n  * `:Ti` - task insert\r\n  * `:Vt` - view tasks\r\n  * `:Jt` - jump to task\r\n\r\n  Alternatively, bind to `:Di, :Ti, :Vt, :Jt` to a key binding:\r\n\r\n    map <leader>d :Di<CR>\r\n    map <leader>t :Ti<CR>\r\n    map <F5> :Vt<CR>\r\n    map <C-CR> :Jt<CR>\r\n\r\n## Bugs\r\n\r\n  Bugs are tracked through \"http:\/\/github.com\/iflo0\/vim-task-org\/issues\" ","install_details":"`sh install.sh`, or copy files instead into ~\/.vim\/plugin && ~\/.vim\/doc","5":"`sh install.sh`, or copy files instead into ~\/.vim\/plugin && ~\/.vim\/doc","first_name":"Alexander","6":"Alexander","last_name":"Yunin","7":"Yunin","releases":[{"0":"3652","vim_version":"7.3","1":"7.3","script_version":"0.4.0","2":"0.4.0","version_comment":"Add ruby 1.8 support (for Mac users).","3":"Add ruby 1.8 support (for Mac users).","package":"iflo0-vim-task-org-0.4.0-1-g6b0d447.tar.gz","4":"iflo0-vim-task-org-0.4.0-1-g6b0d447.tar.gz","src_id":"16495","5":"16495","creation_date":"1315586536","6":"1315586536"},{"0":"3652","vim_version":"7.3","1":"7.3","script_version":"0.3.1","2":"0.3.1","version_comment":"Initial upload","3":"Initial upload","package":"vim-task-org-git-20110704-1.src.tar.gz","4":"vim-task-org-git-20110704-1.src.tar.gz","src_id":"16029","5":"16029","creation_date":"1309790209","6":"1309790209"}]},"3651":{"script_id":"3651","0":"3651","script_name":"googleclosurevim","1":"googleclosurevim","script_type":"utility","2":"utility","summary":"Google Closure plugin for vim","3":"Google Closure plugin for vim","description":"Plugin for fast javascript development with \r\nGoogle Closure.\r\n\r\nLatest version available at github:\r\nhttps:\/\/github.com\/batsuev\/googleclosurevim","4":"Plugin for fast javascript development with \r\nGoogle Closure.\r\n\r\nLatest version available at github:\r\nhttps:\/\/github.com\/batsuev\/googleclosurevim","install_details":"Use pathogen or just extract the archive","5":"Use pathogen or just extract the archive","first_name":"Aleksandr","6":"Aleksandr","last_name":"Batsuev","7":"Batsuev","releases":[{"0":"3651","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"googleclosurevim-8c9f785.tar.gz","4":"googleclosurevim-8c9f785.tar.gz","src_id":"16026","5":"16026","creation_date":"1309703148","6":"1309703148"}]},"3650":{"script_id":"3650","0":"3650","script_name":"cakephp.vim","1":"cakephp.vim","script_type":"utility","2":"utility","summary":"Tools for working with CakePHP from vim","3":"Tools for working with CakePHP from vim","description":"Check out the plugin's git repository at http:\/\/github.com\/ndreynolds\/vim-cakephp for the most recent updates.  You can also find instructions on installing with Git there.  The README, which you'll find at the link as well as in the zipfile here, contains a quick getting started guide.\r\n          \r\ncakephp.vim offers a lot of features that make building CakePHP apps with vim a lot easier.  It tries to be for CakePHP what rails.vim is for Ruby on Rails.  I wouldn't say it's there yet, but I'm slowly adding features as I identify the need for each one.\r\n\r\n\r\n          \r\nWhat cakephp.vim offers:\r\n          \r\n-- Nothing to set.  The plugin will add an indicator to your statusline when you edit CakePHP files.  If you see the indicator, all the cakephp.vim commands are available, and the plugin already knows where your application's root is.\r\n          \r\n-- Knows the MVC structure.  When you call :Ccontroller without arguments from a model, the plugin knows to open that model's associated controller.  You're also free to specify any controller you like.  Call :Cview from within a controller function and you'll jump to the corresponding view.\r\n          \r\n-- Tab completion everywhere.  If your .vimrc is set up for it, all the navigation commands have tab completion, so you can quickly see which views are available and switch to any given one in just a few key strokes.\r\n          \r\n-- No worrying about file extensions.  I figure CakePHP is standardized enough that you should never need to tell this plugin the file extension.  You'll also never need to type out '_controller'--both this and the extension are automatically taken care of when cakephp.vim opens files.\r\n          \r\n-- Commands for opening everything from logs (:Clog) to stylesheets ( :Ccss) to components (:Ccomponent).\r\n          \r\n-- You can query the API docs (which unfortunately aren't stored locally by Cake) with :Cdoc [query], opening search results in the default web browser, or if you use the variant command, :CLdoc, it will open the results in Lynx.\r\n\r\n-- If you use the plugin a lot, you could play with the mappings.  I've mapped :Ccontroller to <leader>c and :Cmodel to <leader>m.  Jumping between model and controller doesn't get much faster.\r\n\r\n\r\n          \r\nIt's been developed on Ubuntu and OSX with Vim 7.2.  It should work fine on most *nixes with 7.0 and up.  I've also tested it briefly on Windows 7 using gvim and didn't have any problems.  Submit an issue on the Github repo (or email me) if you find any bugs.","4":"Check out the plugin's git repository at http:\/\/github.com\/ndreynolds\/vim-cakephp for the most recent updates.  You can also find instructions on installing with Git there.  The README, which you'll find at the link as well as in the zipfile here, contains a quick getting started guide.\r\n          \r\ncakephp.vim offers a lot of features that make building CakePHP apps with vim a lot easier.  It tries to be for CakePHP what rails.vim is for Ruby on Rails.  I wouldn't say it's there yet, but I'm slowly adding features as I identify the need for each one.\r\n\r\n\r\n          \r\nWhat cakephp.vim offers:\r\n          \r\n-- Nothing to set.  The plugin will add an indicator to your statusline when you edit CakePHP files.  If you see the indicator, all the cakephp.vim commands are available, and the plugin already knows where your application's root is.\r\n          \r\n-- Knows the MVC structure.  When you call :Ccontroller without arguments from a model, the plugin knows to open that model's associated controller.  You're also free to specify any controller you like.  Call :Cview from within a controller function and you'll jump to the corresponding view.\r\n          \r\n-- Tab completion everywhere.  If your .vimrc is set up for it, all the navigation commands have tab completion, so you can quickly see which views are available and switch to any given one in just a few key strokes.\r\n          \r\n-- No worrying about file extensions.  I figure CakePHP is standardized enough that you should never need to tell this plugin the file extension.  You'll also never need to type out '_controller'--both this and the extension are automatically taken care of when cakephp.vim opens files.\r\n          \r\n-- Commands for opening everything from logs (:Clog) to stylesheets ( :Ccss) to components (:Ccomponent).\r\n          \r\n-- You can query the API docs (which unfortunately aren't stored locally by Cake) with :Cdoc [query], opening search results in the default web browser, or if you use the variant command, :CLdoc, it will open the results in Lynx.\r\n\r\n-- If you use the plugin a lot, you could play with the mappings.  I've mapped :Ccontroller to <leader>c and :Cmodel to <leader>m.  Jumping between model and controller doesn't get much faster.\r\n\r\n\r\n          \r\nIt's been developed on Ubuntu and OSX with Vim 7.2.  It should work fine on most *nixes with 7.0 and up.  I've also tested it briefly on Windows 7 using gvim and didn't have any problems.  Submit an issue on the Github repo (or email me) if you find any bugs.","install_details":"It's just your average plugin.  doc\/cakephp.txt goes in ~\/.vim\/doc, plugin\/cakephp.vim goes in ~\/.vim\/plugin.  If you use a plugin manager, follow its instructions instead. \r\n\r\nThe help file can be loaded with :helptags ~\/.vim\/doc, or something to that effect.  A lot of plugin managers will do this for you.  Once it's loaded, you can call :help cakephp from vim.  The documentation on most of the commands can be accessed similarly-- :help :Cview -- for example.","5":"It's just your average plugin.  doc\/cakephp.txt goes in ~\/.vim\/doc, plugin\/cakephp.vim goes in ~\/.vim\/plugin.  If you use a plugin manager, follow its instructions instead. \r\n\r\nThe help file can be loaded with :helptags ~\/.vim\/doc, or something to that effect.  A lot of plugin managers will do this for you.  Once it's loaded, you can call :help cakephp from vim.  The documentation on most of the commands can be accessed similarly-- :help :Cview -- for example.","first_name":"Nick","6":"Nick","last_name":"Reynolds","7":"Reynolds","releases":[{"0":"3650","vim_version":"7.0","1":"7.0","script_version":"1.2.5","2":"1.2.5","version_comment":"--Adds a bunch of new commands like :Cgrep, :Chelper, :Ccomponent, and so on...\r\n--Fixes some bugs with model\/controller names that have multiple underscores.\r\n--Adds an indicator to the statusline when editing a CakePHP file, commands are only available when this is present.\r\n--Better app detection to go along with the above. \r\n--A lot of internal improvements.","3":"--Adds a bunch of new commands like :Cgrep, :Chelper, :Ccomponent, and so on...\r\n--Fixes some bugs with model\/controller names that have multiple underscores.\r\n--Adds an indicator to the statusline when editing a CakePHP file, commands are only available when this is present.\r\n--Better app detection to go along with the above. \r\n--A lot of internal improvements.","package":"cakephp.zip","4":"cakephp.zip","src_id":"16058","5":"16058","creation_date":"1310171261","6":"1310171261"},{"0":"3650","vim_version":"7.0","1":"7.0","script_version":"1.1","2":"1.1","version_comment":"Initial upload","3":"Initial upload","package":"cakephp.zip","4":"cakephp.zip","src_id":"16006","5":"16006","creation_date":"1309394174","6":"1309394174"}]},"3649":{"script_id":"3649","0":"3649","script_name":"simpleRGB","1":"simpleRGB","script_type":"color scheme","2":"color scheme","summary":"Simple color scheme for using 4 colors.","3":"Simple color scheme for using 4 colors.","description":"It's a simple color scheme using 4 colors: red, green, blue and white. Currently it's, sort of, optimized for C and C++ programming languages, but I'm intending to update this script in a near future.","4":"It's a simple color scheme using 4 colors: red, green, blue and white. Currently it's, sort of, optimized for C and C++ programming languages, but I'm intending to update this script in a near future.","install_details":"Just copy the file into your colors directory and in your \"vimrc\" type \"colorscheme simpleRGB\".","5":"Just copy the file into your colors directory and in your \"vimrc\" type \"colorscheme simpleRGB\".","first_name":"Peter","6":"Peter","last_name":"Zeman","7":"Zeman","releases":[{"0":"3649","vim_version":"7.3","1":"7.3","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"simpleRGB.vim","4":"simpleRGB.vim","src_id":"16005","5":"16005","creation_date":"1309385531","6":"1309385531"}]},"3648":{"script_id":"3648","0":"3648","script_name":"AutoCpp","1":"AutoCpp","script_type":"utility","2":"utility","summary":"AutoCpp types complex C++ typenames for you.","3":"AutoCpp types complex C++ typenames for you.","description":"USAGE\r\n\r\nType something like\r\n\r\n    it = mapIntToString.find(3);\r\n\r\nthen hit <C-J> (Ctrl + J). If declaration of myMap is availible inside\r\ncurrent function, AutoCpp will insert typename of iterator (for now\r\nAutoCpp only supports const_iterator \/ iterator).\r\n\r\nIf myMap is declared in that way\r\n\r\n    std::map<int, std::string> mapIntToString;\r\n\r\nline with iterator turns into\r\n\r\n    std::map<int, std::string>::const_iterator it = mapIntToString.find(3);\r\n\r\nHit <C-J> one more time and line becomes\r\n\r\n    std::map<int, std::string>::iterator it = mapIntToString.find(3);\r\n\r\nTo get an idea of how it works, you can watch a short video:\r\nhttp:\/\/www.youtube.com\/watch?v=uTqnQEuUSL4\r\n\r\n\r\nSOURCE CODE\r\n\r\nYou can find all sources here:\r\nhttps:\/\/github.com\/9uMaH\/autocpp","4":"USAGE\r\n\r\nType something like\r\n\r\n    it = mapIntToString.find(3);\r\n\r\nthen hit <C-J> (Ctrl + J). If declaration of myMap is availible inside\r\ncurrent function, AutoCpp will insert typename of iterator (for now\r\nAutoCpp only supports const_iterator \/ iterator).\r\n\r\nIf myMap is declared in that way\r\n\r\n    std::map<int, std::string> mapIntToString;\r\n\r\nline with iterator turns into\r\n\r\n    std::map<int, std::string>::const_iterator it = mapIntToString.find(3);\r\n\r\nHit <C-J> one more time and line becomes\r\n\r\n    std::map<int, std::string>::iterator it = mapIntToString.find(3);\r\n\r\nTo get an idea of how it works, you can watch a short video:\r\nhttp:\/\/www.youtube.com\/watch?v=uTqnQEuUSL4\r\n\r\n\r\nSOURCE CODE\r\n\r\nYou can find all sources here:\r\nhttps:\/\/github.com\/9uMaH\/autocpp","install_details":"just copy autocpp.vim to your plugin directory (usualy $HOME\/.vim\/plugin\/)","5":"just copy autocpp.vim to your plugin directory (usualy $HOME\/.vim\/plugin\/)","first_name":"Dmitry","6":"Dmitry","last_name":"Ermolov","7":"Ermolov","releases":[{"0":"3648","vim_version":"7.0","1":"7.0","script_version":"0.1.1","2":"0.1.1","version_comment":"Repeating <C-J> allows you to insert ::const_iterator \/ ::iterator","3":"Repeating <C-J> allows you to insert ::const_iterator \/ ::iterator","package":"autocpp.vim","4":"autocpp.vim","src_id":"16011","5":"16011","creation_date":"1309448711","6":"1309448711"},{"0":"3648","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"autocpp.vim","4":"autocpp.vim","src_id":"16000","5":"16000","creation_date":"1309291101","6":"1309291101"}]},"3647":{"script_id":"3647","0":"3647","script_name":"VimLite","1":"VimLite","script_type":"utility","2":"utility","summary":"Make vim as a C\/C++ IDE inspired by CodeLite.","3":"Make vim as a C\/C++ IDE inspired by CodeLite.","description":" - Updated on 2013-05-27\r\nVimLite became videm, please upgrade from this http:\/\/www.vim.org\/scripts\/script.php?script_id=4599\r\n\r\nVimLite is a C\/C++ IDE.\r\nVimLite consists mainly of the following three modules: \r\n1.Project Manager:\r\n    The project management module is compatible with CodeLite 2.10. It will auto generates makefile for you. \r\n2.Code Completion:\r\n    An enhanced OmniCpp and a VIMCCC plugin.\r\n        OmniCpp support the following completion: namespace, structure, class member, using, using namespace, class template, stl, etc.\r\n        VIMCCC - An Omni cpp code completion plugin which based on libclang.\r\n3.Debugger Integration. \r\n    Gdb integration, by pyclewn.\r\n\r\nIf you need more features, you can search other plugins.\r\nSuch as taglist, tagbar, NERD_commenter, snipmate, etc.\r\n\r\n - 2013-01-26\r\nI have implemented auto code completing with c\/c++ by libclang, which such as assist plugin of visual studio.\r\nBut it requires vim compiled with +clientserver. Unfortunately this feature needs X server, so vim-nox does not support auto code completing.\r\nAnd updating vim to 7.3.196 or later is strongly recommended. Because patch196 for vim7.3 implement InsertCharPre autocmd.\r\nRun ':h VimLite-CodeCompletion-VIMCCC' for help about VIMCCC.\r\n\r\nI just make a patch for vim 7.3 to add a 'noexpand' argument for 'completeopt' option which can work perfect with auto code completing.\r\nJust downloads it in http:\/\/code.google.com\/p\/vimlite\/downloads\/list.\r\n\r\nNOTE1: Currently, VimLite is not stable enough.\r\nNOTE2: Currently, VimLite need Vim 7.3 or later.\r\n\r\nPlease report bugs here http:\/\/code.google.com\/p\/vimlite\/issues\/list.\r\n\r\nAfter installation, run ':h VimLite.txt' for help.\r\n\r\nSimple User Guide (Chinese):\r\nhttp:\/\/forum.ubuntu.org.cn\/viewtopic.php?f=68&t=342932\r\n\r\nScreen shots:\r\nhttp:\/\/forum.ubuntu.org.cn\/download\/file.php?id=141024&mode=view\/ProjectSettings.png\r\nhttp:\/\/forum.ubuntu.org.cn\/download\/file.php?id=135903&mode=view\/cltest02.png\r\nhttp:\/\/forum.ubuntu.org.cn\/download\/file.php?id=136304&mode=view\/Screenshot.png\r\nhttp:\/\/forum.ubuntu.org.cn\/download\/file.php?id=136703&mode=view\/quickfix.png\r\nhttp:\/\/forum.ubuntu.org.cn\/download\/file.php?id=141025&mode=view\/Working.png\r\n\r\nVIMCCC On Linux:\r\nhttp:\/\/forum.ubuntu.org.cn\/download\/file.php?id=148086&mode=view\/VIMCCC_On_Linux.png\r\n\r\nVIMCCC On Windows:\r\nhttp:\/\/forum.ubuntu.org.cn\/download\/file.php?id=148087&mode=view\/VIMCCC_On_Windows.png\r\n\r\nTODO:\r\n1. Improve debugger integration (debugger).\r\n2. Filter symbols which are not include (OmniCpp).\r\nX. Port to Windows.\r\nX. Parse saved file asynchronously (OmniCpp).\r\nX. Move clang code completion to which based on libclang (VIMCCC).","4":" - Updated on 2013-05-27\r\nVimLite became videm, please upgrade from this http:\/\/www.vim.org\/scripts\/script.php?script_id=4599\r\n\r\nVimLite is a C\/C++ IDE.\r\nVimLite consists mainly of the following three modules: \r\n1.Project Manager:\r\n    The project management module is compatible with CodeLite 2.10. It will auto generates makefile for you. \r\n2.Code Completion:\r\n    An enhanced OmniCpp and a VIMCCC plugin.\r\n        OmniCpp support the following completion: namespace, structure, class member, using, using namespace, class template, stl, etc.\r\n        VIMCCC - An Omni cpp code completion plugin which based on libclang.\r\n3.Debugger Integration. \r\n    Gdb integration, by pyclewn.\r\n\r\nIf you need more features, you can search other plugins.\r\nSuch as taglist, tagbar, NERD_commenter, snipmate, etc.\r\n\r\n - 2013-01-26\r\nI have implemented auto code completing with c\/c++ by libclang, which such as assist plugin of visual studio.\r\nBut it requires vim compiled with +clientserver. Unfortunately this feature needs X server, so vim-nox does not support auto code completing.\r\nAnd updating vim to 7.3.196 or later is strongly recommended. Because patch196 for vim7.3 implement InsertCharPre autocmd.\r\nRun ':h VimLite-CodeCompletion-VIMCCC' for help about VIMCCC.\r\n\r\nI just make a patch for vim 7.3 to add a 'noexpand' argument for 'completeopt' option which can work perfect with auto code completing.\r\nJust downloads it in http:\/\/code.google.com\/p\/vimlite\/downloads\/list.\r\n\r\nNOTE1: Currently, VimLite is not stable enough.\r\nNOTE2: Currently, VimLite need Vim 7.3 or later.\r\n\r\nPlease report bugs here http:\/\/code.google.com\/p\/vimlite\/issues\/list.\r\n\r\nAfter installation, run ':h VimLite.txt' for help.\r\n\r\nSimple User Guide (Chinese):\r\nhttp:\/\/forum.ubuntu.org.cn\/viewtopic.php?f=68&t=342932\r\n\r\nScreen shots:\r\nhttp:\/\/forum.ubuntu.org.cn\/download\/file.php?id=141024&mode=view\/ProjectSettings.png\r\nhttp:\/\/forum.ubuntu.org.cn\/download\/file.php?id=135903&mode=view\/cltest02.png\r\nhttp:\/\/forum.ubuntu.org.cn\/download\/file.php?id=136304&mode=view\/Screenshot.png\r\nhttp:\/\/forum.ubuntu.org.cn\/download\/file.php?id=136703&mode=view\/quickfix.png\r\nhttp:\/\/forum.ubuntu.org.cn\/download\/file.php?id=141025&mode=view\/Working.png\r\n\r\nVIMCCC On Linux:\r\nhttp:\/\/forum.ubuntu.org.cn\/download\/file.php?id=148086&mode=view\/VIMCCC_On_Linux.png\r\n\r\nVIMCCC On Windows:\r\nhttp:\/\/forum.ubuntu.org.cn\/download\/file.php?id=148087&mode=view\/VIMCCC_On_Windows.png\r\n\r\nTODO:\r\n1. Improve debugger integration (debugger).\r\n2. Filter symbols which are not include (OmniCpp).\r\nX. Port to Windows.\r\nX. Parse saved file asynchronously (OmniCpp).\r\nX. Move clang code completion to which based on libclang (VIMCCC).","install_details":"software dependencies:\r\npython\r\npython-lxml (optional)\r\ngcc\r\nmake\r\ngdb\r\ncscope\r\n\r\nOn ubuntu 10.04, just run\r\nsudo apt-get install python python-lxml build-essential gdb cscope\r\n\r\nOn Windows, just installs python 2.x (2.6 or later) and the win32 python package from http:\/\/starship.python.net\/crew\/mhammond\/ (for pyclewn)\r\n\r\nvim dependencies:\r\n+python\r\n+netbeans_intg\r\nset nocp\r\nfiletype plugin on\r\n\r\n\r\nInstallation (Linux):\r\n1. Extract the tar file.\r\n2. Put everything which in vimlite directory to ~\/.vimlite, you probably need to create this directory.\r\n    Usually, it's recommended to remove the old version configs which locate in ~\/.vimlite\/config\/.\r\n3. Open VimLite.vba with vim and run :so %\r\n4. If you wish use VIMCCC, install libclang 3.0.\r\n5. Build the parser. Read the 'NOTE99' below.\r\n\r\nInstallation (Windows 32bit): \r\n1. Extract the tar file.\r\n2. Move vimlite directory to $VIM (for example of mine: C:\\Program Files\\Vim).\r\n    Usually, it's recommended to remove the old version configs which locate in $VIM\/vimlite\/config\/.\r\n3. Open VimLite.vba with gvim and run :so %\r\n4. Download win32bin.zip and extract it and put all files(exes and dlls) into $VIM\\vimlite\\bin\r\n5. Add $VIM\\vimlite\\bin (mine is C:\\Program Files\\Vim\\vimlite\\bin) to the environment variable PATH.\r\n6. Install MinGW 4.x. You can download MinGW-4.4.1.7z in http:\/\/code.google.com\/p\/vimlite\/downloads\/list.\r\n7. Add bin folder path (mine is D:\\MinGW-4.4.1\\bin) of MinGW to the environment variable PATH.\r\n8. If you wish use Omni cpp code completion based on libclang, install libclang 3.0.\r\n9. Build the parser. Read the 'NOTE99' below.\r\n\r\nNOTE: Cpp headers of MinGW have too many symbols, so VimLite will take so long time to parse and store them, please be patient. Or you can use VIMCCC plugin which based on libclang.\r\n\r\nIn the following url, there are a libclang.so work on ubuntu 10.04 and a libclang.dll work on xp with Visual Studio 2010 runtime.\r\nhttp:\/\/code.google.com\/p\/vimlite\/downloads\/list\r\n\r\nRun :VLWorkspaceOpen to start, and press '.' (dot) to work.\r\n\r\nNOTE1: The two Omni code completion plugins conflict with other omni cpp plugins, such as omnicppcomplete, clang_complete. You need to disable them before using VimLite.\r\nNOTE2: VIMCCC can works without VimLite, if you wish, put this in your .vimrc: let g:VIMCCC_Enable = 1\r\nNOTE3: VIMCCC will spends more memory to cache cpp source, take care of your memory.\r\n\r\nNOTE99: Since VimLite 0.9.0.0, please build the parser vlctags2 yourself. Download videm-x.y.z.tar.bz2 and read README.txt for installation help.","5":"software dependencies:\r\npython\r\npython-lxml (optional)\r\ngcc\r\nmake\r\ngdb\r\ncscope\r\n\r\nOn ubuntu 10.04, just run\r\nsudo apt-get install python python-lxml build-essential gdb cscope\r\n\r\nOn Windows, just installs python 2.x (2.6 or later) and the win32 python package from http:\/\/starship.python.net\/crew\/mhammond\/ (for pyclewn)\r\n\r\nvim dependencies:\r\n+python\r\n+netbeans_intg\r\nset nocp\r\nfiletype plugin on\r\n\r\n\r\nInstallation (Linux):\r\n1. Extract the tar file.\r\n2. Put everything which in vimlite directory to ~\/.vimlite, you probably need to create this directory.\r\n    Usually, it's recommended to remove the old version configs which locate in ~\/.vimlite\/config\/.\r\n3. Open VimLite.vba with vim and run :so %\r\n4. If you wish use VIMCCC, install libclang 3.0.\r\n5. Build the parser. Read the 'NOTE99' below.\r\n\r\nInstallation (Windows 32bit): \r\n1. Extract the tar file.\r\n2. Move vimlite directory to $VIM (for example of mine: C:\\Program Files\\Vim).\r\n    Usually, it's recommended to remove the old version configs which locate in $VIM\/vimlite\/config\/.\r\n3. Open VimLite.vba with gvim and run :so %\r\n4. Download win32bin.zip and extract it and put all files(exes and dlls) into $VIM\\vimlite\\bin\r\n5. Add $VIM\\vimlite\\bin (mine is C:\\Program Files\\Vim\\vimlite\\bin) to the environment variable PATH.\r\n6. Install MinGW 4.x. You can download MinGW-4.4.1.7z in http:\/\/code.google.com\/p\/vimlite\/downloads\/list.\r\n7. Add bin folder path (mine is D:\\MinGW-4.4.1\\bin) of MinGW to the environment variable PATH.\r\n8. If you wish use Omni cpp code completion based on libclang, install libclang 3.0.\r\n9. Build the parser. Read the 'NOTE99' below.\r\n\r\nNOTE: Cpp headers of MinGW have too many symbols, so VimLite will take so long time to parse and store them, please be patient. Or you can use VIMCCC plugin which based on libclang.\r\n\r\nIn the following url, there are a libclang.so work on ubuntu 10.04 and a libclang.dll work on xp with Visual Studio 2010 runtime.\r\nhttp:\/\/code.google.com\/p\/vimlite\/downloads\/list\r\n\r\nRun :VLWorkspaceOpen to start, and press '.' (dot) to work.\r\n\r\nNOTE1: The two Omni code completion plugins conflict with other omni cpp plugins, such as omnicppcomplete, clang_complete. You need to disable them before using VimLite.\r\nNOTE2: VIMCCC can works without VimLite, if you wish, put this in your .vimrc: let g:VIMCCC_Enable = 1\r\nNOTE3: VIMCCC will spends more memory to cache cpp source, take care of your memory.\r\n\r\nNOTE99: Since VimLite 0.9.0.0, please build the parser vlctags2 yourself. Download videm-x.y.z.tar.bz2 and read README.txt for installation help.","first_name":"fanhe","6":"fanhe","last_name":" ","7":" ","releases":[{"0":"3647","vim_version":"7.3","1":"7.3","script_version":"0.9.7.0","2":"0.9.7.0","version_comment":" - VIMCCC supprts auto popup completing menu now. Need +clientserver feature with vim.\r\n - Added \"Parse Workspace (Full, Async)\" and \"Parse Workspace (Quick, Async)\" workspace menu items.\r\n - Improved gtags integration.\r\n - Imporved VLWorkspaceOpen command. Now you can run ':tabnew | VLWorkspaceOpen' to open a new tab to work.\r\n - Fixed a OmniCpp symbols jumping issue.\r\n - Fixed a debugger issue which conflict with tagbar plugin.","3":" - VIMCCC supprts auto popup completing menu now. Need +clientserver feature with vim.\r\n - Added \"Parse Workspace (Full, Async)\" and \"Parse Workspace (Quick, Async)\" workspace menu items.\r\n - Improved gtags integration.\r\n - Imporved VLWorkspaceOpen command. Now you can run ':tabnew | VLWorkspaceOpen' to open a new tab to work.\r\n - Fixed a OmniCpp symbols jumping issue.\r\n - Fixed a debugger issue which conflict with tagbar plugin.","package":"VimLite-882.tar.bz2","4":"VimLite-882.tar.bz2","src_id":"19434","5":"19434","creation_date":"1359130977","6":"1359130977"},{"0":"3647","vim_version":"7.3","1":"7.3","script_version":"0.9.6.1","2":"0.9.6.1","version_comment":" - Fixed a namespace parsing issue.\r\n - Added <C-p> keymapping for debugger.\r\n - Fixed a VLWFindFiles and VLWFindFilesNoCase issue.","3":" - Fixed a namespace parsing issue.\r\n - Added <C-p> keymapping for debugger.\r\n - Fixed a VLWFindFiles and VLWFindFilesNoCase issue.","package":"VimLite-841.tar.bz2","4":"VimLite-841.tar.bz2","src_id":"19076","5":"19076","creation_date":"1354425517","6":"1354425517"},{"0":"3647","vim_version":"7.3","1":"7.3","script_version":"1.0.9","2":"1.0.9","version_comment":" - Fixed a compilation issue on x86_64 OS.","3":" - Fixed a compilation issue on x86_64 OS.","package":"videm-1.0.9.tar.bz2","4":"videm-1.0.9.tar.bz2","src_id":"18899","5":"18899","creation_date":"1351320414","6":"1351320414"},{"0":"3647","vim_version":"7.3","1":"7.3","script_version":"1.0.8","2":"1.0.8","version_comment":" - Update README.txt for more information to installation.","3":" - Update README.txt for more information to installation.","package":"videm-1.0.8.tar.bz2","4":"videm-1.0.8.tar.bz2","src_id":"18860","5":"18860","creation_date":"1350920701","6":"1350920701"},{"0":"3647","vim_version":"7.3","1":"7.3","script_version":"0.9.6.0","2":"0.9.6.0","version_comment":" - Fixed encoding issue of file path.\r\n - Added suffixes setting in \"Workspace Settings\".\r\n - Added \"C and C++ Compile Options\" in \"Project Settings\".\r\n - Removed clang PCH setting.\r\n - Improved project running.\r\n - Added some help info, try it to press <F1> in every setting.\r\n - Fixed some bugs.","3":" - Fixed encoding issue of file path.\r\n - Added suffixes setting in \"Workspace Settings\".\r\n - Added \"C and C++ Compile Options\" in \"Project Settings\".\r\n - Removed clang PCH setting.\r\n - Improved project running.\r\n - Added some help info, try it to press <F1> in every setting.\r\n - Fixed some bugs.","package":"VimLite-823.tar.bz2","4":"VimLite-823.tar.bz2","src_id":"18842","5":"18842","creation_date":"1350711460","6":"1350711460"},{"0":"3647","vim_version":"7.3","1":"7.3","script_version":"0.9.5.1","2":"0.9.5.1","version_comment":" - Fixed a cscope init issue.","3":" - Fixed a cscope init issue.","package":"VimLite-797.tar.bz2","4":"VimLite-797.tar.bz2","src_id":"18746","5":"18746","creation_date":"1349326842","6":"1349326842"},{"0":"3647","vim_version":"7.3","1":"7.3","script_version":"0.9.5.0","2":"0.9.5.0","version_comment":" - Added ':VLWLocateCurrentFile' command.\r\n - Added 'Editor Options' which locate in 'Workspace Settings... -> Editor -> Editor Options'.\r\n - Added 'g:VimTagsManager_InclAllCondCmplBrch' option.\r\n - Added some debugger variables watching keybindings.\r\n - Added limitation notification, run ':h VimLite-Limitation' for details.\r\n - Improved jumping to Impl\/Decl of symbols.\r\n - Improved debugger breakpoints saving.\r\n - Fixed ':VLWBuildAndRunActiveProject' issue.\r\n - Fixed an dead lock issue of parser.\r\n - Redesigned compile and build system. So there are some compatible problems with old settings.\r\n\r\nNOTE: This version must run with the latest vlctags2. Download videm-x.y.x.tar.bz2 to install.","3":" - Added ':VLWLocateCurrentFile' command.\r\n - Added 'Editor Options' which locate in 'Workspace Settings... -> Editor -> Editor Options'.\r\n - Added 'g:VimTagsManager_InclAllCondCmplBrch' option.\r\n - Added some debugger variables watching keybindings.\r\n - Added limitation notification, run ':h VimLite-Limitation' for details.\r\n - Improved jumping to Impl\/Decl of symbols.\r\n - Improved debugger breakpoints saving.\r\n - Fixed ':VLWBuildAndRunActiveProject' issue.\r\n - Fixed an dead lock issue of parser.\r\n - Redesigned compile and build system. So there are some compatible problems with old settings.\r\n\r\nNOTE: This version must run with the latest vlctags2. Download videm-x.y.x.tar.bz2 to install.","package":"VimLite-793.tar.bz2","4":"VimLite-793.tar.bz2","src_id":"18738","5":"18738","creation_date":"1349199119","6":"1349199119"},{"0":"3647","vim_version":"7.0","1":"7.0","script_version":"1.4","2":"1.4","version_comment":"Added test.exe.","3":"Added test.exe.","package":"win32bin.zip","4":"win32bin.zip","src_id":"18737","5":"18737","creation_date":"1349199052","6":"1349199052"},{"0":"3647","vim_version":"7.3","1":"7.3","script_version":"1.0.8","2":"1.0.8","version_comment":" - Fixed some memory leak issues.\r\n - Added '-m' option.","3":" - Fixed some memory leak issues.\r\n - Added '-m' option.","package":"videm-1.0.8.tar.bz2","4":"videm-1.0.8.tar.bz2","src_id":"18735","5":"18735","creation_date":"1349178111","6":"1349178111"},{"0":"3647","vim_version":"7.3","1":"7.3","script_version":"0.9.0.3.1","2":"0.9.0.3.1","version_comment":" - OmniCpp: Fixed a decode bug on Windows.\r\n - vimdialog: Change default key of \"Goto Next Control\" and \"Goto Prev Control\".","3":" - OmniCpp: Fixed a decode bug on Windows.\r\n - vimdialog: Change default key of \"Goto Next Control\" and \"Goto Prev Control\".","package":"VimLite-713.tar.bz2","4":"VimLite-713.tar.bz2","src_id":"18327","5":"18327","creation_date":"1343397188","6":"1343397188"},{"0":"3647","vim_version":"7.3","1":"7.3","script_version":"1.3","2":"1.3","version_comment":"Prerequisite programs on Windows. Add them to PATH environment variable.\r\n\r\n - Update vlctags2.exe.\r\n - You'd better compile the latest vlctags2 and replace which on in win32bin.","3":"Prerequisite programs on Windows. Add them to PATH environment variable.\r\n\r\n - Update vlctags2.exe.\r\n - You'd better compile the latest vlctags2 and replace which on in win32bin.","package":"win32bin.zip","4":"win32bin.zip","src_id":"18320","5":"18320","creation_date":"1343319739","6":"1343319739"},{"0":"3647","vim_version":"7.3","1":"7.3","script_version":"1.0.7","2":"1.0.7","version_comment":"Rename ctags58m to vlctags2.\r\nCompile it and copy vlctags to \"~\/.vimlite\/bin\".","3":"Rename ctags58m to vlctags2.\r\nCompile it and copy vlctags to \"~\/.vimlite\/bin\".","package":"vlctags2-1.0.7.tar.bz2","4":"vlctags2-1.0.7.tar.bz2","src_id":"18319","5":"18319","creation_date":"1343319414","6":"1343319414"},{"0":"3647","vim_version":"7.3","1":"7.3","script_version":"1.0","2":"1.0","version_comment":"Compile it to generate libCxxParser.so. Read VimLite.txt for help.","3":"Compile it to generate libCxxParser.so. Read VimLite.txt for help.","package":"CxxParser.tar.bz2","4":"CxxParser.tar.bz2","src_id":"18318","5":"18318","creation_date":"1343319152","6":"1343319152"},{"0":"3647","vim_version":"7.3","1":"7.3","script_version":"0.9.0.3","2":"0.9.0.3","version_comment":" - VLWorkspace: Added option \"Use with Global Setting\" and \"Prepend Search Scopes\" in \"Workspace Settings...\".\r\n - OmniCpp: Added gnu global symbol database support. Search \"g:VLWorkspaceSymbolDatabase\" in VimLite.txt help.\r\n - OmniCpp: Added libCxxParser.so support. Search \"g:VLOmniCpp_UseLibCxxParser\" in VimLite.txt.\r\n - OmniCpp: Modify vlctags_64 to vlctags in 64bit system, so now just compile vlctags2 and copy to ~\/.vimlite\/bin.\r\n - Others: Fixed a number of bugs.","3":" - VLWorkspace: Added option \"Use with Global Setting\" and \"Prepend Search Scopes\" in \"Workspace Settings...\".\r\n - OmniCpp: Added gnu global symbol database support. Search \"g:VLWorkspaceSymbolDatabase\" in VimLite.txt help.\r\n - OmniCpp: Added libCxxParser.so support. Search \"g:VLOmniCpp_UseLibCxxParser\" in VimLite.txt.\r\n - OmniCpp: Modify vlctags_64 to vlctags in 64bit system, so now just compile vlctags2 and copy to ~\/.vimlite\/bin.\r\n - Others: Fixed a number of bugs.","package":"VimLite-712.tar.bz2","4":"VimLite-712.tar.bz2","src_id":"18317","5":"18317","creation_date":"1343318958","6":"1343318958"},{"0":"3647","vim_version":"7.3","1":"7.3","script_version":"0.8.9.0","2":"0.8.9.0","version_comment":" - OmniCpp: Added feature: Parse the saved file asynchronously.\r\n - OmniCpp: Removed 'g:VLWorkspaceNotParseSourceAfterSave' option.\r\n - OmniCpp: Changed default value of g:VLWorkspaceParseFileAfterSave to 1.\r\n - OmniCpp: Improved performance in scanning header.\r\n - VIMCCC: Fixed a terrible bug.\r\n - VIMCCC: VIMCCC can use search paths of Tags Settings.","3":" - OmniCpp: Added feature: Parse the saved file asynchronously.\r\n - OmniCpp: Removed 'g:VLWorkspaceNotParseSourceAfterSave' option.\r\n - OmniCpp: Changed default value of g:VLWorkspaceParseFileAfterSave to 1.\r\n - OmniCpp: Improved performance in scanning header.\r\n - VIMCCC: Fixed a terrible bug.\r\n - VIMCCC: VIMCCC can use search paths of Tags Settings.","package":"VimLite-526.tar.bz2","4":"VimLite-526.tar.bz2","src_id":"17096","5":"17096","creation_date":"1324489749","6":"1324489749"},{"0":"3647","vim_version":"7.3","1":"7.3","script_version":"0.8.8.2","2":"0.8.8.2","version_comment":" - VIMCCC: Added basic code navigating, run :h VimLite-Options-VIMCCC for more info.\r\n - VIMCCC: Change VIMCCCUpateQuickFix command to VIMCCCQuikcFix.\r\n - Others: Some minor fixings.","3":" - VIMCCC: Added basic code navigating, run :h VimLite-Options-VIMCCC for more info.\r\n - VIMCCC: Change VIMCCCUpateQuickFix command to VIMCCCQuikcFix.\r\n - Others: Some minor fixings.","package":"VimLite-523.tar.bz2","4":"VimLite-523.tar.bz2","src_id":"17092","5":"17092","creation_date":"1324398176","6":"1324398176"},{"0":"3647","vim_version":"7.3","1":"7.3","script_version":"0.8.8.1","2":"0.8.8.1","version_comment":" - VIMCCC: Init added, it is a plugin that support c\/c++ code completion based on libclang 3.0.\r\n - VLWorksapce: Fixed some word case issues.\r\n - OmniCpp: Some improvements.\r\n - Others: Clang code completion options have changed, please read VimLite.txt for help to correct.","3":" - VIMCCC: Init added, it is a plugin that support c\/c++ code completion based on libclang 3.0.\r\n - VLWorksapce: Fixed some word case issues.\r\n - OmniCpp: Some improvements.\r\n - Others: Clang code completion options have changed, please read VimLite.txt for help to correct.","package":"VimLite-515.tar.bz2","4":"VimLite-515.tar.bz2","src_id":"17082","5":"17082","creation_date":"1324154078","6":"1324154078"},{"0":"3647","vim_version":"7.3","1":"7.3","script_version":"0.8.8b","2":"0.8.8b","version_comment":" - VLWorkspace: Added disable files of workspace feature (Try popup menu on file node)\r\n - OmniCpp: Improved __anon containers tags.\r\n - Others: Port to Windows 32bit (experimental, the debugger works badly currently)","3":" - VLWorkspace: Added disable files of workspace feature (Try popup menu on file node)\r\n - OmniCpp: Improved __anon containers tags.\r\n - Others: Port to Windows 32bit (experimental, the debugger works badly currently)","package":"VimLite-498.tar.bz2","4":"VimLite-498.tar.bz2","src_id":"17051","5":"17051","creation_date":"1323545159","6":"1323545159"},{"0":"3647","vim_version":"7.3","1":"7.3","script_version":"0.8.7.1","2":"0.8.7.1","version_comment":" - OmniCpp: Fixed some anonymous container issue.\r\n - OmniCpp: Fixed scope resolver issue ( \/\/extern \"C\" { ).","3":" - OmniCpp: Fixed some anonymous container issue.\r\n - OmniCpp: Fixed scope resolver issue ( \/\/extern \"C\" { ).","package":"VimLite-470.tar.bz2","4":"VimLite-470.tar.bz2","src_id":"16980","5":"16980","creation_date":"1322326904","6":"1322326904"},{"0":"3647","vim_version":"7.3","1":"7.3","script_version":"0.8.7","2":"0.8.7","version_comment":"- VLWorkspace: Added :VLWOpenIncludeFile command.\r\n- OmniCpp: Fixed TokenizeLines().\r\n- OmniCpp: Added g:VLOmniCpp_GotoDeclarationKey, see help.\r\n- OmniCpp: Added g:VLOmniCpp_GotoImplementationKey, see help.\r\n- OmniCpp: Other improvements.","3":"- VLWorkspace: Added :VLWOpenIncludeFile command.\r\n- OmniCpp: Fixed TokenizeLines().\r\n- OmniCpp: Added g:VLOmniCpp_GotoDeclarationKey, see help.\r\n- OmniCpp: Added g:VLOmniCpp_GotoImplementationKey, see help.\r\n- OmniCpp: Other improvements.","package":"VimLite-460.tar.bz2","4":"VimLite-460.tar.bz2","src_id":"16829","5":"16829","creation_date":"1320753403","6":"1320753403"},{"0":"3647","vim_version":"7.3","1":"7.3","script_version":"0.8.6.2","2":"0.8.6.2","version_comment":" - OmniCpp: Fixed TokenizeLines().\r\n - OmniCpp: Add some tokens replacement to support gnu c++ header 4.6\r\n    \"_GLIBCXX_BEGIN_NAMESPACE_CONTAINER\"\r\n    \"_GLIBCXX_END_NAMESPACE_CONTAINER\"\r\n    \"_GLIBCXX_VISIBILITY(%0)=\"","3":" - OmniCpp: Fixed TokenizeLines().\r\n - OmniCpp: Add some tokens replacement to support gnu c++ header 4.6\r\n    \"_GLIBCXX_BEGIN_NAMESPACE_CONTAINER\"\r\n    \"_GLIBCXX_END_NAMESPACE_CONTAINER\"\r\n    \"_GLIBCXX_VISIBILITY(%0)=\"","package":"VimLite-455.tar.bz2","4":"VimLite-455.tar.bz2","src_id":"16751","5":"16751","creation_date":"1319722841","6":"1319722841"},{"0":"3647","vim_version":"7.3","1":"7.3","script_version":"0.8.6.1","2":"0.8.6.1","version_comment":"- Omnicpp: Rewrite Tokenizer() with python, so currently Omnicpp will faster.\r\n- Fixed some bugs.","3":"- Omnicpp: Rewrite Tokenizer() with python, so currently Omnicpp will faster.\r\n- Fixed some bugs.","package":"VimLite-453.tar.bz2","4":"VimLite-453.tar.bz2","src_id":"16745","5":"16745","creation_date":"1319647362","6":"1319647362"},{"0":"3647","vim_version":"7.3","1":"7.3","script_version":"0.8.6","2":"0.8.6","version_comment":"- Debugger: Fixed args issue.\r\n- VLWorkspace: Added :VLWFindFiles and :VLWFindFilesNoCase commands.\r\n- VLWorkspace: Added 'Import Files From Directroy...' menu operation.\r\n- VLWorkspace: Fixed C++ STL type replacement initialization when creating a new workspace.\r\n- VLWorkspace: Fixed include paths issue when paring files.\r\n- OmniCpp: Improvement.\r\n- vimdialog: Improvement.","3":"- Debugger: Fixed args issue.\r\n- VLWorkspace: Added :VLWFindFiles and :VLWFindFilesNoCase commands.\r\n- VLWorkspace: Added 'Import Files From Directroy...' menu operation.\r\n- VLWorkspace: Fixed C++ STL type replacement initialization when creating a new workspace.\r\n- VLWorkspace: Fixed include paths issue when paring files.\r\n- OmniCpp: Improvement.\r\n- vimdialog: Improvement.","package":"VimLite-442.tar.bz2","4":"VimLite-442.tar.bz2","src_id":"16676","5":"16676","creation_date":"1318701824","6":"1318701824"},{"0":"3647","vim_version":"7.3","1":"7.3","script_version":"0.8.5","2":"0.8.5","version_comment":"NOTE: The '~\/.vimlite\/config\/TagsSettings.conf' file of this version is not compatible with the older one, please backup and delete it.\r\n\r\n- VLWorkspace: Fixed 'Workspace Build Configuration' refresh issue.\r\n- VLWorkspace: Fixed global c compile option issue.\r\n- VLWorkspace: Improved popup menu.\r\n- VLWorkspace: Add command 'VLWSwapSourceHeader' to toggle editing source and header.\r\n- VLWorkspace: Change workspace file suffix to 'vlworkspace' and project file suffix to 'vlproject'.\r\n- VLWorkspace: Added 'Batch Build' feature.\r\n- Omnicpp: Fixed 'defaule: { p->|'.\r\n- Omnicpp: Improved 'Types' replacement.\r\n- OmniCpp: Improved class constructor calltips. eg. A::A() : m_data(|) {\r\n- Others: Improved OmniCpp and vimdialog, fixed minor bugs.","3":"NOTE: The '~\/.vimlite\/config\/TagsSettings.conf' file of this version is not compatible with the older one, please backup and delete it.\r\n\r\n- VLWorkspace: Fixed 'Workspace Build Configuration' refresh issue.\r\n- VLWorkspace: Fixed global c compile option issue.\r\n- VLWorkspace: Improved popup menu.\r\n- VLWorkspace: Add command 'VLWSwapSourceHeader' to toggle editing source and header.\r\n- VLWorkspace: Change workspace file suffix to 'vlworkspace' and project file suffix to 'vlproject'.\r\n- VLWorkspace: Added 'Batch Build' feature.\r\n- Omnicpp: Fixed 'defaule: { p->|'.\r\n- Omnicpp: Improved 'Types' replacement.\r\n- OmniCpp: Improved class constructor calltips. eg. A::A() : m_data(|) {\r\n- Others: Improved OmniCpp and vimdialog, fixed minor bugs.","package":"VimLite-430.tar.bz2","4":"VimLite-430.tar.bz2","src_id":"16638","5":"16638","creation_date":"1318089122","6":"1318089122"},{"0":"3647","vim_version":"7.3","1":"7.3","script_version":"0.8.4.1","2":"0.8.4.1","version_comment":"- OmniCpp: Fix bug: if ( 1 > A.| )\r\n- VLWorkspace: Use gui operation for \"Add Existing Files...\" if possible.","3":"- OmniCpp: Fix bug: if ( 1 > A.| )\r\n- VLWorkspace: Use gui operation for \"Add Existing Files...\" if possible.","package":"VimLite-407.tar.bz2","4":"VimLite-407.tar.bz2","src_id":"16434","5":"16434","creation_date":"1314978102","6":"1314978102"},{"0":"3647","vim_version":"7.3","1":"7.3","script_version":"0.8.4","2":"0.8.4","version_comment":" - OmniCpp: Supported initialization calltips: 1. A<B> a(|); 2. A<B> *p = new A<B>(|);\r\n - OmniCpp: Supported macro calltips.\r\n - Improved interaction controls.","3":" - OmniCpp: Supported initialization calltips: 1. A<B> a(|); 2. A<B> *p = new A<B>(|);\r\n - OmniCpp: Supported macro calltips.\r\n - Improved interaction controls.","package":"VimLite-406.tar.bz2","4":"VimLite-406.tar.bz2","src_id":"16272","5":"16272","creation_date":"1313461838","6":"1313461838"},{"0":"3647","vim_version":"7.3","1":"7.3","script_version":"0.8.3","2":"0.8.3","version_comment":"VLWorkspace: Supported environment variables.\r\nVLWorkspace: Fixed \"Worksapce Build Configuration...\".\r\nOmnicpp: Fixed \"using namespace std; map<string, int>::iterator iter; iter->|\"\r\nOmnicpp: Fixed \"using namespace std; for(vector<string>::iterator it;;) it->|\"\r\nOmnicpp: Fixed synstack() issue.\r\nOmnicpp: Supported 64bit.","3":"VLWorkspace: Supported environment variables.\r\nVLWorkspace: Fixed \"Worksapce Build Configuration...\".\r\nOmnicpp: Fixed \"using namespace std; map<string, int>::iterator iter; iter->|\"\r\nOmnicpp: Fixed \"using namespace std; for(vector<string>::iterator it;;) it->|\"\r\nOmnicpp: Fixed synstack() issue.\r\nOmnicpp: Supported 64bit.","package":"VimLite-398.tar.bz2","4":"VimLite-398.tar.bz2","src_id":"16184","5":"16184","creation_date":"1312291060","6":"1312291060"},{"0":"3647","vim_version":"7.3","1":"7.3","script_version":"0.8.2","2":"0.8.2","version_comment":"Fixed toggle breakpoint issue.\r\nFixed Workspace Build Configuration save issue.\r\nImproved interaction controls.","3":"Fixed toggle breakpoint issue.\r\nFixed Workspace Build Configuration save issue.\r\nImproved interaction controls.","package":"VimLite-388.tar.bz2","4":"VimLite-388.tar.bz2","src_id":"16163","5":"16163","creation_date":"1311854458","6":"1311854458"},{"0":"3647","vim_version":"7.3","1":"7.3","script_version":"0.8.1","2":"0.8.1","version_comment":"- Fixed starting debugger bug.\r\n- Fixed 'Add a new file...' menu operation bug.","3":"- Fixed starting debugger bug.\r\n- Fixed 'Add a new file...' menu operation bug.","package":"VimLite-379.tar.bz2","4":"VimLite-379.tar.bz2","src_id":"16119","5":"16119","creation_date":"1311249855","6":"1311249855"},{"0":"3647","vim_version":"7.3","1":"7.3","script_version":"0.8.0","2":"0.8.0","version_comment":"- VLWorkspace: Added some keymappings.\r\n- VLWorkspace: Changed all keymapping options name.\r\n- VLWorkspace: Added command 'VLWBuildAndRunActiveProject'.\r\n- VLWorkspace: Added option 'g:VLWorkspaceCscopeContainExternalHeader'.\r\n- VLWorkspace: Added option 'g:VLWorkspaceNotParseSourceAfterSave'.\r\n- Debugger: Added option 'g:VLWDbgSaveBreakpointsInfo'.\r\n- Debugger: Improved 'VLWDbgToggleBp'.\r\n- OmniCpp: Removed dependence 'libwxbase2.8-0'.","3":"- VLWorkspace: Added some keymappings.\r\n- VLWorkspace: Changed all keymapping options name.\r\n- VLWorkspace: Added command 'VLWBuildAndRunActiveProject'.\r\n- VLWorkspace: Added option 'g:VLWorkspaceCscopeContainExternalHeader'.\r\n- VLWorkspace: Added option 'g:VLWorkspaceNotParseSourceAfterSave'.\r\n- Debugger: Added option 'g:VLWDbgSaveBreakpointsInfo'.\r\n- Debugger: Improved 'VLWDbgToggleBp'.\r\n- OmniCpp: Removed dependence 'libwxbase2.8-0'.","package":"VimLite-375.tar.bz2","4":"VimLite-375.tar.bz2","src_id":"16098","5":"16098","creation_date":"1311085204","6":"1311085204"}]},"3646":{"script_id":"3646","0":"3646","script_name":"Filesearch","1":"Filesearch","script_type":"utility","2":"utility","summary":"Filesystem searching using glob or regular expression patterns","3":"Filesystem searching using glob or regular expression patterns","description":"'Filesearch' is a plugin for searching the local filesystem for files by name\r\nor content. The searches can be done using either glob patterns (searching for\r\nfilenames only) or regular expression patterns (searching for filenames or\r\nfile content).\r\n\r\nThree commands are provided:\r\n\r\n    :Fsglob \/{glob}\/[filetype-options] [paths]\r\n\r\n        Search filesystem for files with names matching the glob pattern\r\n        given by {glob}, which can include wildcard characters.\r\n\r\n    :Fsfind \/{pattern}\/[filetype-options] [paths]\r\n\r\n        Search filesystem for files with names matching the regular expression\r\n        pattern given by {pattern}.\r\n\r\n    :Fsgrep \/{pattern}\/[filetype-options] [paths]\r\n\r\n        Search filesystem for files with lines of content matching the regular\r\n        expression pattern {pattern}.\r\n\r\nBy default searches are carried out recursively starting from the current\r\ndirectory, but the search paths can be adjusted through the use of optional\r\narguments. Searches can also be restricted to specific filetypes through the\r\nuse of filetype filter options (e.g., \"py\" for Python files, \"cpp\" for C++\r\nsource and header files).\r\n\r\nResults will be shown in new buffer (the \"catalog viewer\"). They can be\r\nbrowsed using all the normal Vim movement keys, and can be selected for\r\nviewing the in main (previous) window, a new vertical or horizontal split\r\nwindow, or new tab page.\r\n\r\nDetailed usage description is given in the help file, which can be viewed\r\non-line here:\r\n\r\n    http:\/\/github.com\/jeetsukumaran\/vim-filesearch\/blob\/master\/doc\/filesearch.txt\r\n\r\nThe public source code repository can be found here:\r\n\r\n    http:\/\/github.com\/jeetsukumaran\/vim-filesearch\r\n\r\nVim has much of this functionality built-in (e.g. \"vimgrep\", \"find\").  But I\r\nfind that the browsing, navigation and management of the results from these\r\nnative Vim commands not the most convenient. For example, `:find` automatically\r\ngoes to the first match, and you have to type `:2find` to go to the second\r\nmatch. I would prefer to view the results in single buffer, apply normal Vim\r\nsearch and movement commands to navigate to the results of my choice, and the\r\nability to easily open target files\/lines in a new window or tab page. There\r\nare also a number of plugins that do achieve something similar (e.g., the\r\nexcellent 'Ack' plugin). But I wanted to be able to use Vim-dialect regular\r\nexpressions when working inside Vim, and also wanted a little more control over\r\nhow the results are displayed and sorted. Thus, I wrote this plugin.","4":"'Filesearch' is a plugin for searching the local filesystem for files by name\r\nor content. The searches can be done using either glob patterns (searching for\r\nfilenames only) or regular expression patterns (searching for filenames or\r\nfile content).\r\n\r\nThree commands are provided:\r\n\r\n    :Fsglob \/{glob}\/[filetype-options] [paths]\r\n\r\n        Search filesystem for files with names matching the glob pattern\r\n        given by {glob}, which can include wildcard characters.\r\n\r\n    :Fsfind \/{pattern}\/[filetype-options] [paths]\r\n\r\n        Search filesystem for files with names matching the regular expression\r\n        pattern given by {pattern}.\r\n\r\n    :Fsgrep \/{pattern}\/[filetype-options] [paths]\r\n\r\n        Search filesystem for files with lines of content matching the regular\r\n        expression pattern {pattern}.\r\n\r\nBy default searches are carried out recursively starting from the current\r\ndirectory, but the search paths can be adjusted through the use of optional\r\narguments. Searches can also be restricted to specific filetypes through the\r\nuse of filetype filter options (e.g., \"py\" for Python files, \"cpp\" for C++\r\nsource and header files).\r\n\r\nResults will be shown in new buffer (the \"catalog viewer\"). They can be\r\nbrowsed using all the normal Vim movement keys, and can be selected for\r\nviewing the in main (previous) window, a new vertical or horizontal split\r\nwindow, or new tab page.\r\n\r\nDetailed usage description is given in the help file, which can be viewed\r\non-line here:\r\n\r\n    http:\/\/github.com\/jeetsukumaran\/vim-filesearch\/blob\/master\/doc\/filesearch.txt\r\n\r\nThe public source code repository can be found here:\r\n\r\n    http:\/\/github.com\/jeetsukumaran\/vim-filesearch\r\n\r\nVim has much of this functionality built-in (e.g. \"vimgrep\", \"find\").  But I\r\nfind that the browsing, navigation and management of the results from these\r\nnative Vim commands not the most convenient. For example, `:find` automatically\r\ngoes to the first match, and you have to type `:2find` to go to the second\r\nmatch. I would prefer to view the results in single buffer, apply normal Vim\r\nsearch and movement commands to navigate to the results of my choice, and the\r\nability to easily open target files\/lines in a new window or tab page. There\r\nare also a number of plugins that do achieve something similar (e.g., the\r\nexcellent 'Ack' plugin). But I wanted to be able to use Vim-dialect regular\r\nexpressions when working inside Vim, and also wanted a little more control over\r\nhow the results are displayed and sorted. Thus, I wrote this plugin.","install_details":"If Pathogen is installed, you can install Filesearch by unpacking the source\r\narchive in $VIMRUNTIME\/bundle.  Otherwise, unpack the source archive and copy\r\n\"autoload\/filesearch.vim\" to $VIMRUNTIME\/autoload, \"plugin\/filesearch.vim\" to $VIMRUNTIME\/plugin and \"doc\/filesearch.txt\" to\r\n$VIMRUNTIME\/doc. ","5":"If Pathogen is installed, you can install Filesearch by unpacking the source\r\narchive in $VIMRUNTIME\/bundle.  Otherwise, unpack the source archive and copy\r\n\"autoload\/filesearch.vim\" to $VIMRUNTIME\/autoload, \"plugin\/filesearch.vim\" to $VIMRUNTIME\/plugin and \"doc\/filesearch.txt\" to\r\n$VIMRUNTIME\/doc. ","first_name":"Jeet","6":"Jeet","last_name":"Sukumaran","7":"Sukumaran","releases":[{"0":"3646","vim_version":"7.0","1":"7.0","script_version":"1.2.0","2":"1.2.0","version_comment":"- Do not clobber default register when rendering buffer.\r\n- Reorganization of into autoload plugin (thanks Kien N).","3":"- Do not clobber default register when rendering buffer.\r\n- Reorganization of into autoload plugin (thanks Kien N).","package":"vim-filesearch-v1.2.0.tar.gz","4":"vim-filesearch-v1.2.0.tar.gz","src_id":"16040","5":"16040","creation_date":"1309935955","6":"1309935955"},{"0":"3646","vim_version":"7.0","1":"7.0","script_version":"1.0.0","2":"1.0.0","version_comment":"Alternate archive format.","3":"Alternate archive format.","package":"vim-filesearch-v1.0.0.tar.gz","4":"vim-filesearch-v1.0.0.tar.gz","src_id":"15995","5":"15995","creation_date":"1309215941","6":"1309215941"},{"0":"3646","vim_version":"7.0","1":"7.0","script_version":"1.0.0","2":"1.0.0","version_comment":"Initial upload","3":"Initial upload","package":"vim-filesearch-v1.0.0.zip","4":"vim-filesearch-v1.0.0.zip","src_id":"15994","5":"15994","creation_date":"1309215872","6":"1309215872"}]},"3645":{"script_id":"3645","0":"3645","script_name":"gnupg.vim","1":"gnupg.vim","script_type":"utility","2":"utility","summary":"Plugin for transparent editing of gpg encrypted files.","3":"Plugin for transparent editing of gpg encrypted files.","description":"This script implements transparent editing of gpg encrypted files. The filename must have a \".gpg\", \".pgp\" or \".asc\" suffix. When opening such a file the content is decrypted, when opening a new file the script will ask for the recipients of the encrypted file. The file content will be encrypted to all recipients before it is written. The script turns off viminfo, swapfile, and undofile to increase security.\r\n\r\nThis is a continuation of the work initially done by Markus Braun in vimscript #661.  Development takes place at https:\/\/github.com\/jamessan\/vim-gnupg.","4":"This script implements transparent editing of gpg encrypted files. The filename must have a \".gpg\", \".pgp\" or \".asc\" suffix. When opening such a file the content is decrypted, when opening a new file the script will ask for the recipients of the encrypted file. The file content will be encrypted to all recipients before it is written. The script turns off viminfo, swapfile, and undofile to increase security.\r\n\r\nThis is a continuation of the work initially done by Markus Braun in vimscript #661.  Development takes place at https:\/\/github.com\/jamessan\/vim-gnupg.","install_details":"Use your favorite plugin manager.\r\n\r\nFor manual installation, use either pathogen (for older Vim versions) or Vim's packages.  Unpack into either ~\/.vim\/bundle or ~\/.vim\/pack\/gnupg\/start\/, respectively.\r\n\r\nFrom `man 1 gpg-agent`:\r\n\r\n> You should always add the following lines to your `.bashrc` or whatever\r\n> initialization file is used for all shell invocations:\r\n>\r\n>     GPG_TTY=`tty`\r\n>     export GPG_TTY\r\n>\r\n> It is important that this environment variable always reflects the output of\r\n> the tty command. For W32 systems this option is not required.\r\n\r\nMost distributions provide software to ease handling of gpg and gpg-agent.\r\nExamples are keychain or seahorse.\r\n\r\nIf there are specific actions that should take place when editing a\r\nGnuPG-managed buffer, an autocmd for the User event and GnuPG pattern can be\r\ndefined. For example, the following will set `textwidth` to 72 for all\r\nGnuPG-encrypted buffers:\r\n\r\n    autocmd User GnuPG setl textwidth=72\r\n\r\nThis will be triggered before any BufRead or BufNewFile autocmds, and therefore\r\nwill not take precedence over settings specific to any filetype that may get\r\nset.","5":"Use your favorite plugin manager.\r\n\r\nFor manual installation, use either pathogen (for older Vim versions) or Vim's packages.  Unpack into either ~\/.vim\/bundle or ~\/.vim\/pack\/gnupg\/start\/, respectively.\r\n\r\nFrom `man 1 gpg-agent`:\r\n\r\n> You should always add the following lines to your `.bashrc` or whatever\r\n> initialization file is used for all shell invocations:\r\n>\r\n>     GPG_TTY=`tty`\r\n>     export GPG_TTY\r\n>\r\n> It is important that this environment variable always reflects the output of\r\n> the tty command. For W32 systems this option is not required.\r\n\r\nMost distributions provide software to ease handling of gpg and gpg-agent.\r\nExamples are keychain or seahorse.\r\n\r\nIf there are specific actions that should take place when editing a\r\nGnuPG-managed buffer, an autocmd for the User event and GnuPG pattern can be\r\ndefined. For example, the following will set `textwidth` to 72 for all\r\nGnuPG-encrypted buffers:\r\n\r\n    autocmd User GnuPG setl textwidth=72\r\n\r\nThis will be triggered before any BufRead or BufNewFile autocmds, and therefore\r\nwill not take precedence over settings specific to any filetype that may get\r\nset.","first_name":"James","6":"James","last_name":"McCoy","7":"McCoy","releases":[{"0":"3645","vim_version":"7.2","1":"7.2","script_version":"2.7.1","2":"2.7.1","version_comment":"* Clear GPGOptions\/GPGRecipients autocommands on BufUnload\r\n* Return early from Finish functions when buffer is not displayed","3":"* Clear GPGOptions\/GPGRecipients autocommands on BufUnload\r\n* Return early from Finish functions when buffer is not displayed","package":"vim-gnupg-v2.7.1.zip","4":"vim-gnupg-v2.7.1.zip","src_id":"27359","5":"27359","creation_date":"1605158910","6":"1605158910"},{"0":"3645","vim_version":"7.2","1":"7.2","script_version":"2.7.0","2":"2.7.0","version_comment":"* Re-structure plugin so most of the implementation is under autoload\/, with only required functionality in plugin\/.  Thanks to Lucas Hoffmann for the help.\r\n* Split the documentation into README (description, intro) and Vim help files (details relevant for usage).  Thanks to Victor Koronen.\r\n* Honor 'verbose' to determine when to emit debug logs, as a gradual move away from g:GPGDebugLevel\/g:GPGDebugLog\r\n* Do not use the '[\/'] marks when saving the entire buffer to disk.  This fixes an issue where plugins which reformat the buffer on save were causing only the reformatted portion of the buffer to be saved.","3":"* Re-structure plugin so most of the implementation is under autoload\/, with only required functionality in plugin\/.  Thanks to Lucas Hoffmann for the help.\r\n* Split the documentation into README (description, intro) and Vim help files (details relevant for usage).  Thanks to Victor Koronen.\r\n* Honor 'verbose' to determine when to emit debug logs, as a gradual move away from g:GPGDebugLevel\/g:GPGDebugLog\r\n* Do not use the '[\/'] marks when saving the entire buffer to disk.  This fixes an issue where plugins which reformat the buffer on save were causing only the reformatted portion of the buffer to be saved.","package":"vim-gnupg-v2.7.0.zip","4":"vim-gnupg-v2.7.0.zip","src_id":"27357","5":"27357","creation_date":"1605013264","6":"1605013264"},{"0":"3645","vim_version":"7.2","1":"7.2","script_version":"2.6.1","2":"2.6.1","version_comment":"* Preserve &readonly setting even if the file itself isn't read-only (e.g., using \"vim -R\" or \":view\")\r\n* Let Vim detect file encoding and file format when opening the file\r\n* Remove unnecessary (and potentially damaging) changing of &encoding when reading\/writing the encrypted file\r\n* Avoid adding extra blank lines to buffer when loading unencrypted files\r\n* Set &buftype='acwrite' to ensure encrypted buffers are only saved via the plugin's BufWriteCmd\r\n* Add support for Gpg4win so the plugin can be used under cygwin\r\n* Better mimic Vim's behavior when using \":saveas\" or \":w newfile\", and leave the original buffer modified\r\n* Improve handling of options and recipients buffers to avoid one triggering the other\r\n* Check for the standard armor header, rather than inspecting gpg's output to determine if a file is armored","3":"* Preserve &readonly setting even if the file itself isn't read-only (e.g., using \"vim -R\" or \":view\")\r\n* Let Vim detect file encoding and file format when opening the file\r\n* Remove unnecessary (and potentially damaging) changing of &encoding when reading\/writing the encrypted file\r\n* Avoid adding extra blank lines to buffer when loading unencrypted files\r\n* Set &buftype='acwrite' to ensure encrypted buffers are only saved via the plugin's BufWriteCmd\r\n* Add support for Gpg4win so the plugin can be used under cygwin\r\n* Better mimic Vim's behavior when using \":saveas\" or \":w newfile\", and leave the original buffer modified\r\n* Improve handling of options and recipients buffers to avoid one triggering the other\r\n* Check for the standard armor header, rather than inspecting gpg's output to determine if a file is armored","package":"gnupg.vim","4":"gnupg.vim","src_id":"26175","5":"26175","creation_date":"1533723030","6":"1533723030"},{"0":"3645","vim_version":"7.2","1":"7.2","script_version":"2.6","2":"2.6","version_comment":"* Improved support for GPG 2.x\r\n* New g:GPGPossibleRecipients option to pre-populate the recipients list\r\n* New g:GPGFilePattern option to define which files will be handled by the plugin\r\n* Work around interactions between Vim and gpg\/pinentry that caused special keys (e.g., arrows) to stop being recognized in Vim\r\n* Trigger FileWritePre\/Post before\/after saving a portion of a buffer\r\n* Trigger BufReadPre\/FileReadPre before reading encrypted files\r\n* The buffer is now marked readonly if the source file does not have write permissions","3":"* Improved support for GPG 2.x\r\n* New g:GPGPossibleRecipients option to pre-populate the recipients list\r\n* New g:GPGFilePattern option to define which files will be handled by the plugin\r\n* Work around interactions between Vim and gpg\/pinentry that caused special keys (e.g., arrows) to stop being recognized in Vim\r\n* Trigger FileWritePre\/Post before\/after saving a portion of a buffer\r\n* Trigger BufReadPre\/FileReadPre before reading encrypted files\r\n* The buffer is now marked readonly if the source file does not have write permissions","package":"gnupg.vim","4":"gnupg.vim","src_id":"24199","5":"24199","creation_date":"1461556120","6":"1461556120"},{"0":"3645","vim_version":"7.2","1":"7.2","script_version":"2.5","2":"2.5","version_comment":"* Ignore keys that aren't usable for encryption instead of simply ones that are expired","3":"* Ignore keys that aren't usable for encryption instead of simply ones that are expired","package":"gnupg.vim","4":"gnupg.vim","src_id":"18070","5":"18070","creation_date":"1338518008","6":"1338518008"},{"0":"3645","vim_version":"7.2","1":"7.2","script_version":"2.4","2":"2.4","version_comment":"* Improvements when an encrypted file is being '\":read\" into another buffer.\r\n** Don't wipeout the current buffer if decryption fails.\r\n** Use the current buffer's settings for 'swapfile' and 'undofile' instead of disabling them.\r\n* Make 'u' a no-op immediately after loading the file, just like with normal files.\r\n* Avoid prompting for disambiguation of keys once the user has selected which one to use.\r\n* Ignore expired keys when trying to find a matching key for an id entered in \":GPGEditRecipients\"","3":"* Improvements when an encrypted file is being '\":read\" into another buffer.\r\n** Don't wipeout the current buffer if decryption fails.\r\n** Use the current buffer's settings for 'swapfile' and 'undofile' instead of disabling them.\r\n* Make 'u' a no-op immediately after loading the file, just like with normal files.\r\n* Avoid prompting for disambiguation of keys once the user has selected which one to use.\r\n* Ignore expired keys when trying to find a matching key for an id entered in \":GPGEditRecipients\"","package":"gnupg.vim","4":"gnupg.vim","src_id":"18068","5":"18068","creation_date":"1338439663","6":"1338439663"},{"0":"3645","vim_version":"7.2","1":"7.2","script_version":"2.3","2":"2.3","version_comment":"* Resolve the filename when saving to follow symlinks.\r\n* Add support for specifying an alternate --homedir, using the g:GPGHomedir variable","3":"* Resolve the filename when saving to follow symlinks.\r\n* Add support for specifying an alternate --homedir, using the g:GPGHomedir variable","package":"gnupg.vim","4":"gnupg.vim","src_id":"16952","5":"16952","creation_date":"1322085776","6":"1322085776"},{"0":"3645","vim_version":"7.0","1":"7.0","script_version":"2.2","2":"2.2","version_comment":"Correctly handle the different keyid-format options","3":"Correctly handle the different keyid-format options","package":"gnupg.vim","4":"gnupg.vim","src_id":"16256","5":"16256","creation_date":"1313273022","6":"1313273022"},{"0":"3645","vim_version":"7.2","1":"7.2","script_version":"2.1","2":"2.1","version_comment":"Add g:GPGUsePipes variable to avoid saving unencrypted data to tempfiles (in a private directory)","3":"Add g:GPGUsePipes variable to avoid saving unencrypted data to tempfiles (in a private directory)","package":"gnupg.vim","4":"gnupg.vim","src_id":"16225","5":"16225","creation_date":"1312940911","6":"1312940911"},{"0":"3645","vim_version":"7.2","1":"7.2","script_version":"2.0","2":"2.0","version_comment":"Initial upload","3":"Initial upload","package":"gnupg.vim","4":"gnupg.vim","src_id":"15987","5":"15987","creation_date":"1309118071","6":"1309118071"}]},"3644":{"script_id":"3644","0":"3644","script_name":"vimgtd","1":"vimgtd","script_type":"utility","2":"utility","summary":"gtd by vim","3":"gtd by vim","description":"this plugin can use gtd in vim.\r\n\r\nthis plugin need vimwiki and snipmate,please install them first.\r\n\r\ncmd:\r\n:TaskToday      list the tasks that today should do.\r\n:TaskAll           list all tasks that should do.\r\n:TaskDoneOrDoingByDate      list the task that you done or doing in the past time.\r\n:TaskBackup    backup the files","4":"this plugin can use gtd in vim.\r\n\r\nthis plugin need vimwiki and snipmate,please install them first.\r\n\r\ncmd:\r\n:TaskToday      list the tasks that today should do.\r\n:TaskAll           list all tasks that should do.\r\n:TaskDoneOrDoingByDate      list the task that you done or doing in the past time.\r\n:TaskBackup    backup the files","install_details":"unzip to .vim or vimfiles.\r\nenjoy it.","5":"unzip to .vim or vimfiles.\r\nenjoy it.","first_name":"zhu","6":"zhu","last_name":"nianyang","7":"nianyang","releases":[{"0":"3644","vim_version":"7.0","1":"7.0","script_version":"1.2","2":"1.2","version_comment":"redefine the directory of backup","3":"redefine the directory of backup","package":"vimgtd.zip","4":"vimgtd.zip","src_id":"16333","5":"16333","creation_date":"1314105041","6":"1314105041"},{"0":"3644","vim_version":"7.0","1":"7.0","script_version":"1.1","2":"1.1","version_comment":"change default index to task\/task.wiki\r\nand you can config it by:\r\nlet g:wikigtd_index = 'task\/xxxx'","3":"change default index to task\/task.wiki\r\nand you can config it by:\r\nlet g:wikigtd_index = 'task\/xxxx'","package":"vimgtd.zip","4":"vimgtd.zip","src_id":"16297","5":"16297","creation_date":"1313721657","6":"1313721657"},{"0":"3644","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"vimgtd.zip","4":"vimgtd.zip","src_id":"15982","5":"15982","creation_date":"1309100462","6":"1309100462"}]},"3643":{"script_id":"3643","0":"3643","script_name":"Vimper IDE","1":"Vimper IDE","script_type":"utility","2":"utility","summary":"vimper : Yet another IDE using Vim... ","3":"vimper : Yet another IDE using Vim... ","description":"Vimper is a Vim based IDE, a set of plugins to enable creation of development projects. There are a lot of useful plugins available to aid development, but you need to run around to gather them. The goal is to gather a lot of these plugins into one single package and also extend them or add new plugins. \r\n\r\nCurrently it supports: \r\n* C++ IDE --  definition of C\/C++ projects \r\n(projects can also be created for developing vim plugins, mainly for demo purpose). \r\n\r\nCurrent features include: \r\n\r\n* Tree based file explorer (VTreeExplore) \r\n* Auto generation of makefiles. \r\n* Integration and navigation of make errors\/warnings. \r\n* Project Window (listing all defined projects) \r\n* Browser to View\/Navigate Class\/Structure\/Function definitions \r\n* Search files within project and navigate to search results. \r\n\r\nScreenshots: \r\nProject Explorer & Class Browser : http:\/\/www.langene.net\/ext\/images\/Vimper_Class_Browser.png\r\nProject Search : http:\/\/www.langene.net\/ext\/images\/Vimper-Search_Project.png \r\nProject Build : http:\/\/www.langene.net\/ext\/images\/Vimper-make_Output.png\r\n\r\nUseful Key Maps: \r\n- nmap <F8> :Vimper<cr> \r\n- nmap <C-f> :VSearch<cr> \r\n- nmap <C-S-b> :VmkMake<cr> \r\n- nmap <C-S-t> :VProjTags<cr> \r\n\r\nInstead of putting these mappings in the .vimrc file, they should be added to the <PROJECT_ROOT>\/.vimproj file. This file is autogenerated every time a new project is created. \r\n\r\nGoto https:\/\/code.google.com\/p\/vimper\/ for more details and documentation. If you run into any issues or bugs it would be great if you could log them at the Google Code project. Any feedback or suggestion also welcome. \r\n\r\nUse :helptags <install dir>\/doc to add the vimdoc files and type :help Vimper to view the help documentation. \r\n\r\nNote: Currently this only tested on (*)nix platform. An earlier version was tested on Windows with cygwin, things might have broken since. If anyone tries it out on windows and faces issues please let me know by logging an issue. On windows most of the functionality will not work without Cygwin.\r\n\r\n ","4":"Vimper is a Vim based IDE, a set of plugins to enable creation of development projects. There are a lot of useful plugins available to aid development, but you need to run around to gather them. The goal is to gather a lot of these plugins into one single package and also extend them or add new plugins. \r\n\r\nCurrently it supports: \r\n* C++ IDE --  definition of C\/C++ projects \r\n(projects can also be created for developing vim plugins, mainly for demo purpose). \r\n\r\nCurrent features include: \r\n\r\n* Tree based file explorer (VTreeExplore) \r\n* Auto generation of makefiles. \r\n* Integration and navigation of make errors\/warnings. \r\n* Project Window (listing all defined projects) \r\n* Browser to View\/Navigate Class\/Structure\/Function definitions \r\n* Search files within project and navigate to search results. \r\n\r\nScreenshots: \r\nProject Explorer & Class Browser : http:\/\/www.langene.net\/ext\/images\/Vimper_Class_Browser.png\r\nProject Search : http:\/\/www.langene.net\/ext\/images\/Vimper-Search_Project.png \r\nProject Build : http:\/\/www.langene.net\/ext\/images\/Vimper-make_Output.png\r\n\r\nUseful Key Maps: \r\n- nmap <F8> :Vimper<cr> \r\n- nmap <C-f> :VSearch<cr> \r\n- nmap <C-S-b> :VmkMake<cr> \r\n- nmap <C-S-t> :VProjTags<cr> \r\n\r\nInstead of putting these mappings in the .vimrc file, they should be added to the <PROJECT_ROOT>\/.vimproj file. This file is autogenerated every time a new project is created. \r\n\r\nGoto https:\/\/code.google.com\/p\/vimper\/ for more details and documentation. If you run into any issues or bugs it would be great if you could log them at the Google Code project. Any feedback or suggestion also welcome. \r\n\r\nUse :helptags <install dir>\/doc to add the vimdoc files and type :help Vimper to view the help documentation. \r\n\r\nNote: Currently this only tested on (*)nix platform. An earlier version was tested on Windows with cygwin, things might have broken since. If anyone tries it out on windows and faces issues please let me know by logging an issue. On windows most of the functionality will not work without Cygwin.\r\n\r\n ","install_details":"To install vimper unzip the downloaded vimper-<version>.zip file and copy the contents to your Vim folder. On (*)nix machines they can be copied to the ~\/.vim directory or on Windows machines to ~\/vimfiles. You can also copy the contents to <Vim Runtime Home>\/vimfiles (though not recommended). Set the environment variable VIMPER_HOME to point to the directory to which the content was copied (eg. VIMPER_HOME=~\/.vim). \r\n","5":"To install vimper unzip the downloaded vimper-<version>.zip file and copy the contents to your Vim folder. On (*)nix machines they can be copied to the ~\/.vim directory or on Windows machines to ~\/vimfiles. You can also copy the contents to <Vim Runtime Home>\/vimfiles (though not recommended). Set the environment variable VIMPER_HOME to point to the directory to which the content was copied (eg. VIMPER_HOME=~\/.vim). \r\n","first_name":"Subhabrata","6":"Subhabrata","last_name":"Ghosh","7":"Ghosh","releases":[{"0":"3643","vim_version":"7.0","1":"7.0","script_version":"0.1.3b","2":"0.1.3b","version_comment":"Added typedefs and macros to the Class Explorer.","3":"Added typedefs and macros to the Class Explorer.","package":"vimper-0.1.3b.tgz","4":"vimper-0.1.3b.tgz","src_id":"16059","5":"16059","creation_date":"1310203821","6":"1310203821"},{"0":"3643","vim_version":"7.0","1":"7.0","script_version":"0.1.3","2":"0.1.3","version_comment":"Added functionality to create classes.\r\nType \"c\" in the explorer window on or under the directory the class files should be added. Follow the prompts to create a header and class file.","3":"Added functionality to create classes.\r\nType \"c\" in the explorer window on or under the directory the class files should be added. Follow the prompts to create a header and class file.","package":"vimper-0.1.3.tgz","4":"vimper-0.1.3.tgz","src_id":"16056","5":"16056","creation_date":"1310150280","6":"1310150280"}]},"3642":{"script_id":"3642","0":"3642","script_name":"vim-orgmode","1":"vim-orgmode","script_type":"ftplugin","2":"ftplugin","summary":"Text outlining and task management for Vim based on Emacs' Org-Mode","3":"Text outlining and task management for Vim based on Emacs' Org-Mode","description":"INTRODUCTION                                 *vim-orgmode* *orgguide-introduction*\r\n\r\nVim-orgmode: Text outlining and task management for Vim based on Emacs'\r\nOrg-Mode.\r\n\r\nThe idea for this plugin was born by listening to the Floss Weekly podcast\r\nintroducing Emacs' Org-Mode (http:\/\/twit.tv\/floss136). Org-Mode has a lot of\r\nstrong features like folding, views (sparse tree) and scheduling of tasks.\r\nThese are completed by hyperlinks, tags, todo states, priorities aso.\r\n\r\nVim-orgmode aims at providing the same functionality for Vim and for command\r\nline tools*.\r\n\r\n* for command line tools and other programs a library liborgmode is provided.\r\n  It encapsulates all functionality for parsing and modifying org files.\r\n\r\n------------------------------------------------------------------------------\r\nPreface~\r\n   vim-orgmode is a file type plugin for keeping notes, maintaining TODO\r\n   lists, and doing project planning with a fast and effective plain-text\r\n   system. It is also an authoring and publishing system.\r\n\r\n   This document is a copy of the orgmode-guide for emacs\r\n   (http:\/\/orgmode.org\/) with modifications for vim. It contains all basic\r\n   features and commands, along with important hints for customization.\r\n\r\n------------------------------------------------------------------------------\r\nFeatures~\r\n  vim-orgmode is still very young but already quite usable. Here is a short\r\n  list of the already supported features:\r\n\r\n  - Cycle visibility of headings\r\n  - Navigate between headings\r\n  - Edit the structure of the document: add, move, promote, denote headings\r\n    and more\r\n  - Hyperlinks within vim-orgmode and outside (files, webpages, etc.)\r\n  - TODO list management\r\n  - Tags for headings\r\n  - Basic date handling\r\n  - Export (via emacs)\r\n\r\n  More features are coming...\r\n\r\nFeedback~\r\n   If you find problems with vim-orgmode, or if you have questions, remarks, or\r\n   ideas about it, please create a ticket on\r\n   https:\/\/github.com\/jceb\/vim-orgmode","4":"INTRODUCTION                                 *vim-orgmode* *orgguide-introduction*\r\n\r\nVim-orgmode: Text outlining and task management for Vim based on Emacs'\r\nOrg-Mode.\r\n\r\nThe idea for this plugin was born by listening to the Floss Weekly podcast\r\nintroducing Emacs' Org-Mode (http:\/\/twit.tv\/floss136). Org-Mode has a lot of\r\nstrong features like folding, views (sparse tree) and scheduling of tasks.\r\nThese are completed by hyperlinks, tags, todo states, priorities aso.\r\n\r\nVim-orgmode aims at providing the same functionality for Vim and for command\r\nline tools*.\r\n\r\n* for command line tools and other programs a library liborgmode is provided.\r\n  It encapsulates all functionality for parsing and modifying org files.\r\n\r\n------------------------------------------------------------------------------\r\nPreface~\r\n   vim-orgmode is a file type plugin for keeping notes, maintaining TODO\r\n   lists, and doing project planning with a fast and effective plain-text\r\n   system. It is also an authoring and publishing system.\r\n\r\n   This document is a copy of the orgmode-guide for emacs\r\n   (http:\/\/orgmode.org\/) with modifications for vim. It contains all basic\r\n   features and commands, along with important hints for customization.\r\n\r\n------------------------------------------------------------------------------\r\nFeatures~\r\n  vim-orgmode is still very young but already quite usable. Here is a short\r\n  list of the already supported features:\r\n\r\n  - Cycle visibility of headings\r\n  - Navigate between headings\r\n  - Edit the structure of the document: add, move, promote, denote headings\r\n    and more\r\n  - Hyperlinks within vim-orgmode and outside (files, webpages, etc.)\r\n  - TODO list management\r\n  - Tags for headings\r\n  - Basic date handling\r\n  - Export (via emacs)\r\n\r\n  More features are coming...\r\n\r\nFeedback~\r\n   If you find problems with vim-orgmode, or if you have questions, remarks, or\r\n   ideas about it, please create a ticket on\r\n   https:\/\/github.com\/jceb\/vim-orgmode","install_details":"Installation~\r\n  Download the latest stable release at\r\n  http:\/\/www.vim.org\/scripts\/script.php?script_id=3642\r\n\r\n  Open the vimball archive in vim and source it.\r\n\r\n  $ vim orgmode.vba\r\n>\r\n    :so %\r\n<\r\n\r\n  ATTENTION: All .pyc files from former versions of vim-orgmode need to be\r\n  deleted before updating!","5":"Installation~\r\n  Download the latest stable release at\r\n  http:\/\/www.vim.org\/scripts\/script.php?script_id=3642\r\n\r\n  Open the vimball archive in vim and source it.\r\n\r\n  $ vim orgmode.vba\r\n>\r\n    :so %\r\n<\r\n\r\n  ATTENTION: All .pyc files from former versions of vim-orgmode need to be\r\n  deleted before updating!","first_name":"Jan Christoph","6":"Jan Christoph","last_name":"Ebersbach","7":"Ebersbach","releases":[{"0":"3642","vim_version":"7.3","1":"7.3","script_version":"0.5.0","2":"0.5.0","version_comment":"See https:\/\/github.com\/jceb\/vim-orgmode\/blob\/master\/CHANGELOG.org","3":"See https:\/\/github.com\/jceb\/vim-orgmode\/blob\/master\/CHANGELOG.org","package":"orgmode.vba","4":"orgmode.vba","src_id":"23662","5":"23662","creation_date":"1444485255","6":"1444485255"},{"0":"3642","vim_version":"7.3","1":"7.3","script_version":"0.4.1","2":"0.4.1","version_comment":"- fix cache problems when inserting a new heading, together with multi line text (closes issue #116)","3":"- fix cache problems when inserting a new heading, together with multi line text (closes issue #116)","package":"orgmode.vba","4":"orgmode.vba","src_id":"17019","5":"17019","creation_date":"1323008744","6":"1323008744"},{"0":"3642","vim_version":"7.3","1":"7.3","script_version":"0.4.0","2":"0.4.0","version_comment":"- fix broken repeat settings for moving a heading\r\n- improve performance when moving a heading upward or downward (closes issue #108)\r\n- improve performance when changing the level of a heading (related to issue #108)\r\n- extend liborgmode.headings.HeadingList to allow headings to not be tainted when moving them around\r\n- change heading tree text object to ir\/ar... because of vim's it\/at text object (closes issue #106)\r\n- improve performance when inserting a new heading below (closes issue #105)\r\n- remove duplicate tags (closes issue #104)\r\n- improve performance in insert mode (closes issue #103)\r\n- improve performance when opening larger org files (closes issue #103)\r\n- replace org.txt by orgguide.txt (closes issue #77)\r\n- change g:org_leader to <LocalLeader> (closes issue #101)\r\n  To restore the previous behavior add the following line to your vimrc:\r\n>\r\n  let maplocalleader = ','\r\n<\r\n- change normal command execution to not remap any key (related to issue #85)\r\n- fix regression timeout when opening folds (closes issue #100)\r\n- vim-orgmode multistate documentation (closes issue #77)\r\n- add support for @-signs in tags (closes issue #98)\r\n- enable file completion for hyperlinks by default (closes issue #97)\r\n- fix traceback when pressing <Esc> while editing a link (closes issue #96)\r\n- implement reverse visibility cycling using <S-Tab> (closes issue #95)\r\n- change ,, and ,. to remap zr and zm. (closes issue #73)\r\n- add .cnf files to the vimball archive (closes #93)\r\n- integrate pylint code checker (closes issue #87)\r\n- solve encoding issues in the agenda plugin (closes issue #86)\r\n- add description for writing test cases\r\n- add coverage report target (closes issue #74)\r\n- add support for plain lists, thanks to Aleksandar Dimitrov (closes issue #81)\r\n- add agenda view, many thanks to Stefan Otte (closes issue #34)\r\n- move cursor to the current todo state when selecting the todo state\r\n  interactively (closes issue #61)\r\n- add parameter scope to method settings.get\r\n- add method settings.unset\r\n- fix cursor positioning when selecting todo states\r\n- improve date plugin\r\n- update vba targets to its new name vmb\r\n- demoting a newly created second level heading doesn't cause all children to\r\n  be deleted anymore (closes issue #65)\r\n- add error message for missing dependencies (closes issue #59)\r\n- rename tests directory\r\n- change licensing of the documentation to GNU Free Documentation License\r\n- integrate orgguide (closes issue #57)\r\n- replace DIRECTION_* with an enum (closes issue #56 and issue #49)","3":"- fix broken repeat settings for moving a heading\r\n- improve performance when moving a heading upward or downward (closes issue #108)\r\n- improve performance when changing the level of a heading (related to issue #108)\r\n- extend liborgmode.headings.HeadingList to allow headings to not be tainted when moving them around\r\n- change heading tree text object to ir\/ar... because of vim's it\/at text object (closes issue #106)\r\n- improve performance when inserting a new heading below (closes issue #105)\r\n- remove duplicate tags (closes issue #104)\r\n- improve performance in insert mode (closes issue #103)\r\n- improve performance when opening larger org files (closes issue #103)\r\n- replace org.txt by orgguide.txt (closes issue #77)\r\n- change g:org_leader to <LocalLeader> (closes issue #101)\r\n  To restore the previous behavior add the following line to your vimrc:\r\n>\r\n  let maplocalleader = ','\r\n<\r\n- change normal command execution to not remap any key (related to issue #85)\r\n- fix regression timeout when opening folds (closes issue #100)\r\n- vim-orgmode multistate documentation (closes issue #77)\r\n- add support for @-signs in tags (closes issue #98)\r\n- enable file completion for hyperlinks by default (closes issue #97)\r\n- fix traceback when pressing <Esc> while editing a link (closes issue #96)\r\n- implement reverse visibility cycling using <S-Tab> (closes issue #95)\r\n- change ,, and ,. to remap zr and zm. (closes issue #73)\r\n- add .cnf files to the vimball archive (closes #93)\r\n- integrate pylint code checker (closes issue #87)\r\n- solve encoding issues in the agenda plugin (closes issue #86)\r\n- add description for writing test cases\r\n- add coverage report target (closes issue #74)\r\n- add support for plain lists, thanks to Aleksandar Dimitrov (closes issue #81)\r\n- add agenda view, many thanks to Stefan Otte (closes issue #34)\r\n- move cursor to the current todo state when selecting the todo state\r\n  interactively (closes issue #61)\r\n- add parameter scope to method settings.get\r\n- add method settings.unset\r\n- fix cursor positioning when selecting todo states\r\n- improve date plugin\r\n- update vba targets to its new name vmb\r\n- demoting a newly created second level heading doesn't cause all children to\r\n  be deleted anymore (closes issue #65)\r\n- add error message for missing dependencies (closes issue #59)\r\n- rename tests directory\r\n- change licensing of the documentation to GNU Free Documentation License\r\n- integrate orgguide (closes issue #57)\r\n- replace DIRECTION_* with an enum (closes issue #56 and issue #49)","package":"orgmode.vba","4":"orgmode.vba","src_id":"16683","5":"16683","creation_date":"1318791867","6":"1318791867"},{"0":"3642","vim_version":"7.3","1":"7.3","script_version":"0.3.1","2":"0.3.1","version_comment":"- demoting a newly created second level heading doesn't cause all children to\r\n  be deleted anymore (closes issue #65)\r\n- add error message for missing dependencies (closes issue #59)","3":"- demoting a newly created second level heading doesn't cause all children to\r\n  be deleted anymore (closes issue #65)\r\n- add error message for missing dependencies (closes issue #59)","package":"orgmode.vba","4":"orgmode.vba","src_id":"16260","5":"16260","creation_date":"1313353040","6":"1313353040"},{"0":"3642","vim_version":"7.0","1":"7.0","script_version":"0.3","2":"0.3","version_comment":"- fix completion menu popup that disappeared because of the usage of vim.command\r\n  (closes issue #48)\r\n- implement interactive todo state selection (closes issue #5)\r\n- add orgmode group to au commands in TagProperties plugin (closes issue #53)\r\n- allow demotion of first level headings (closes issue #27)\r\n- fix encoding issues in Date plugin\r\n- add general support for multiple todo sequences (closes Issue #46)\r\n- fix folded text for headings containing backslashes or double quotes (closes\r\n  issue #26)\r\n- add Document.get_todo_states() and Document.get_all_todo_states()\r\n- don't confuse upper case words at the beginning of a heading with a todo\r\n    state (closes issue #28)\r\n- fix error in setting tags (issue #25)\r\n- improve split of heading (issue #24)\r\n- add variable g:org_improve_split_heading to enable\/disable improve the split\r\n  of headings (issue #24)\r\n- implement shortcut for moving to the partent's next sibling (g}) (issue #22)\r\n- fix duplication of children when inserting a new heading (issue #20)\r\n- always start insert mode when adding a new heading (issue #21)","3":"- fix completion menu popup that disappeared because of the usage of vim.command\r\n  (closes issue #48)\r\n- implement interactive todo state selection (closes issue #5)\r\n- add orgmode group to au commands in TagProperties plugin (closes issue #53)\r\n- allow demotion of first level headings (closes issue #27)\r\n- fix encoding issues in Date plugin\r\n- add general support for multiple todo sequences (closes Issue #46)\r\n- fix folded text for headings containing backslashes or double quotes (closes\r\n  issue #26)\r\n- add Document.get_todo_states() and Document.get_all_todo_states()\r\n- don't confuse upper case words at the beginning of a heading with a todo\r\n    state (closes issue #28)\r\n- fix error in setting tags (issue #25)\r\n- improve split of heading (issue #24)\r\n- add variable g:org_improve_split_heading to enable\/disable improve the split\r\n  of headings (issue #24)\r\n- implement shortcut for moving to the partent's next sibling (g}) (issue #22)\r\n- fix duplication of children when inserting a new heading (issue #20)\r\n- always start insert mode when adding a new heading (issue #21)","package":"orgmode.vba","4":"orgmode.vba","src_id":"16216","5":"16216","creation_date":"1312872061","6":"1312872061"},{"0":"3642","vim_version":"7.3","1":"7.3","script_version":"0.2.1","2":"0.2.1","version_comment":"- fix encoding of todo states set by the Todo plugin (thanks to Daniel Carl\r\n  and kien for pointing out the issue)\r\n- add documentation for remapping shortcuts\r\n- add documentation for customizing syntax highlighting","3":"- fix encoding of todo states set by the Todo plugin (thanks to Daniel Carl\r\n  and kien for pointing out the issue)\r\n- add documentation for remapping shortcuts\r\n- add documentation for customizing syntax highlighting","package":"orgmode.vba","4":"orgmode.vba","src_id":"15984","5":"15984","creation_date":"1309109632","6":"1309109632"},{"0":"3642","vim_version":"7.3","1":"7.3","script_version":"0.2","2":"0.2","version_comment":"Initial upload","3":"Initial upload","package":"orgmode.vba","4":"orgmode.vba","src_id":"15974","5":"15974","creation_date":"1309017359","6":"1309017359"}]},"3641":{"script_id":"3641","0":"3641","script_name":"Atomic Save","1":"Atomic Save","script_type":"utility","2":"utility","summary":"Save files atomically with ordinary "w" command","3":"Save files atomically with ordinary "w" command","description":"This is an atomic save function for vim.  IOW, this is an atomic write ('w') function for vim.  It makes sure that there is always a fully-written copy of the file in place to be read by other programs.  It uses the system 'mv' since vim's rename() function removes the destination file rather than atomically replacing it.\r\n\r\nTo use it, you enable it as described below, and then 'w' your file like normal.\r\n\r\nNOTE: if using windows, see the note below.\r\n","4":"This is an atomic save function for vim.  IOW, this is an atomic write ('w') function for vim.  It makes sure that there is always a fully-written copy of the file in place to be read by other programs.  It uses the system 'mv' since vim's rename() function removes the destination file rather than atomically replacing it.\r\n\r\nTo use it, you enable it as described below, and then 'w' your file like normal.\r\n\r\nNOTE: if using windows, see the note below.\r\n","install_details":"Put the function in your .vimrc, also after that, add this line to save all files atomically:\r\n\r\nautocmd BufWriteCmd * call AtomicSave()\r\n\r\nOr add a line like this, which will only save files named ".procmailrc" atomically:\r\n\r\nautocmd BufWriteCmd .procmailrc call AtomicSave()\r\n\r\nType :help autocmd for more info on how you can choose when to use this function\r\n\r\nNOTE: If you are using windows, you probably need to change "mv" to "rename" -- unless you have installed GNU coreutils deep in the bowels of your microsoft OS.\r\n","5":"Put the function in your .vimrc, also after that, add this line to save all files atomically:\r\n\r\nautocmd BufWriteCmd * call AtomicSave()\r\n\r\nOr add a line like this, which will only save files named ".procmailrc" atomically:\r\n\r\nautocmd BufWriteCmd .procmailrc call AtomicSave()\r\n\r\nType :help autocmd for more info on how you can choose when to use this function\r\n\r\nNOTE: If you are using windows, you probably need to change "mv" to "rename" -- unless you have installed GNU coreutils deep in the bowels of your microsoft OS.\r\n","first_name":"Andrew","6":"Andrew","last_name":"Cady","7":"Cady","releases":[{"0":"3641","vim_version":"7.0","1":"7.0","script_version":"0.9.3","2":"0.9.3","version_comment":"Preserve owner and group information on save","3":"Preserve owner and group information on save","package":"AtomicSave.vim","4":"AtomicSave.vim","src_id":"25373","5":"25373","creation_date":"1499119182","6":"1499119182"},{"0":"3641","vim_version":"5.7","1":"5.7","script_version":"0.9.2","2":"0.9.2","version_comment":"Fixed bug where symlinks were not preserved.  Writing to a symlink would replace the link with a regular file.  Now it replaces the symlink's target.","3":"Fixed bug where symlinks were not preserved.  Writing to a symlink would replace the link with a regular file.  Now it replaces the symlink's target.","package":"AtomicSave.vim","4":"AtomicSave.vim","src_id":"21367","5":"21367","creation_date":"1390589862","6":"1390589862"},{"0":"3641","vim_version":"5.7","1":"5.7","script_version":"0.9.1","2":"0.9.1","version_comment":"This version will preserve file permissions on the saved file using GNU chmod.  If your system does not have GNU chmod, it will fail. \r\n\r\nAnother change: it will now produce a status message indicating success, after writing the file.\r\n","3":"This version will preserve file permissions on the saved file using GNU chmod.  If your system does not have GNU chmod, it will fail. \r\n\r\nAnother change: it will now produce a status message indicating success, after writing the file.\r\n","package":"AtomicSave.vim","4":"AtomicSave.vim","src_id":"19221","5":"19221","creation_date":"1356039094","6":"1356039094"},{"0":"3641","vim_version":"5.7","1":"5.7","script_version":"0.9","2":"0.9","version_comment":"Initial upload","3":"Initial upload","package":"AtomicSave.vim","4":"AtomicSave.vim","src_id":"15970","5":"15970","creation_date":"1308931027","6":"1308931027"}]},"3640":{"script_id":"3640","0":"3640","script_name":"The Old Ones","1":"The Old Ones","script_type":"utility","2":"utility","summary":"Alerts you to old buffers.","3":"Alerts you to old buffers.","description":"\r\nThis script lists following buffers:\r\n    a) Empty (nameless and had not been viewed nor been saved)\r\n    b) Not Referred (had been opened in read-only usage)\r\n    c) Long Time No Save (had been modified and is not saved yet)\r\nthat are left long time.\r\nAnd this script lets you close a) and\/or b).\r\n\r\nUsage:\r\n    1. (optional) set g:TheOldOnes_Threshold to what you feel \"It's long time\"\r\n        default: 60 (60 min.)\r\n    2. execute  :TheOldOnes\r\n","4":"\r\nThis script lists following buffers:\r\n    a) Empty (nameless and had not been viewed nor been saved)\r\n    b) Not Referred (had been opened in read-only usage)\r\n    c) Long Time No Save (had been modified and is not saved yet)\r\nthat are left long time.\r\nAnd this script lets you close a) and\/or b).\r\n\r\nUsage:\r\n    1. (optional) set g:TheOldOnes_Threshold to what you feel \"It's long time\"\r\n        default: 60 (60 min.)\r\n    2. execute  :TheOldOnes\r\n","install_details":"Put this file into the plugin directory.\r\n","5":"Put this file into the plugin directory.\r\n","first_name":"Shuhei","6":"Shuhei","last_name":"Kubota","7":"Kubota","releases":[{"0":"3640","vim_version":"7.0","1":"7.0","script_version":"v0.2","2":"v0.2","version_comment":"improved conviniences.\r\n\r\n* changed EOL characters\r\n+ \"There are no old ones.\" if nothing to be displayed","3":"improved conviniences.\r\n\r\n* changed EOL characters\r\n+ \"There are no old ones.\" if nothing to be displayed","package":"theoldones.vim","4":"theoldones.vim","src_id":"15989","5":"15989","creation_date":"1309138309","6":"1309138309"},{"0":"3640","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"theoldones.vim","4":"theoldones.vim","src_id":"15969","5":"15969","creation_date":"1308913390","6":"1308913390"}]},"3639":{"script_id":"3639","0":"3639","script_name":"svnst.vim","1":"svnst.vim","script_type":"utility","2":"utility","summary":"easy way to use \"svn status\" in vim buffer.","3":"easy way to use \"svn status\" in vim buffer.","description":"Using subversion command status in vim.\r\n\r\nCommand: \r\n    \\st subversion status from current directory.\r\n\r\nSample:\r\n    :e source_code.c\r\n    :lcd %:p:h\r\n    \\st\r\n\r\n","4":"Using subversion command status in vim.\r\n\r\nCommand: \r\n    \\st subversion status from current directory.\r\n\r\nSample:\r\n    :e source_code.c\r\n    :lcd %:p:h\r\n    \\st\r\n\r\n","install_details":"copy svnst.vim to  your ~\/.vim\/plugin\/ directory.","5":"copy svnst.vim to  your ~\/.vim\/plugin\/ directory.","first_name":"zuopeng","6":"zuopeng","last_name":"chen","7":"chen","releases":[{"0":"3639","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"svnst.vim","4":"svnst.vim","src_id":"15960","5":"15960","creation_date":"1308827027","6":"1308827027"}]},"3638":{"script_id":"3638","0":"3638","script_name":"Handlebars","1":"Handlebars","script_type":"syntax","2":"syntax","summary":"Vim syntax for Handlebars","3":"Vim syntax for Handlebars","description":"This plugin is here to help you editing Handlebars files: http:\/\/www.handlebarsjs.com\/.\r\n\r\nYou can follow development on https:\/\/github.com\/nono\/vim-handlebars","4":"This plugin is here to help you editing Handlebars files: http:\/\/www.handlebarsjs.com\/.\r\n\r\nYou can follow development on https:\/\/github.com\/nono\/vim-handlebars","install_details":"Copy the handlebars.vim file to $HOME\/.vim\/syntax\/ and add the following line to your vimrc:\r\nau BufRead,BufNewFile *.handlebars,*.hbs set ft=html syntax=handlebars","5":"Copy the handlebars.vim file to $HOME\/.vim\/syntax\/ and add the following line to your vimrc:\r\nau BufRead,BufNewFile *.handlebars,*.hbs set ft=html syntax=handlebars","first_name":"Bruno","6":"Bruno","last_name":"Michel","7":"Michel","releases":[{"0":"3638","vim_version":"7.0","1":"7.0","script_version":"0.3","2":"0.3","version_comment":"Use html for the filetype and handlebars as a syntax. It should improve compatibility with other plugins that detect the html filetype.","3":"Use html for the filetype and handlebars as a syntax. It should improve compatibility with other plugins that detect the html filetype.","package":"handlebars.vim","4":"handlebars.vim","src_id":"19621","5":"19621","creation_date":"1362957089","6":"1362957089"},{"0":"3638","vim_version":"7.0","1":"7.0","script_version":"0.2","2":"0.2","version_comment":"Add support for block comments and fix some minor bugs","3":"Add support for block comments and fix some minor bugs","package":"handlebars.vim","4":"handlebars.vim","src_id":"18876","5":"18876","creation_date":"1351111469","6":"1351111469"},{"0":"3638","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"handlebars.vim","4":"handlebars.vim","src_id":"15955","5":"15955","creation_date":"1308793250","6":"1308793250"}]},"3637":{"script_id":"3637","0":"3637","script_name":"gUnit syntax","1":"gUnit syntax","script_type":"syntax","2":"syntax","summary":"Syntax file for ANTL3 gUnit tests","3":"Syntax file for ANTL3 gUnit tests","description":"Simple syntax file for gUnit tests for the ANTLR3 parser generator","4":"Simple syntax file for gUnit tests for the ANTLR3 parser generator","install_details":"","5":"","first_name":"Stefan","6":"Stefan","last_name":"Heinemann","7":"Heinemann","releases":[{"0":"3637","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"gunit.vim","4":"gunit.vim","src_id":"15954","5":"15954","creation_date":"1308759610","6":"1308759610"}]},"3636":{"script_id":"3636","0":"3636","script_name":"ReplaceFile","1":"ReplaceFile","script_type":"utility","2":"utility","summary":"Replace Current File with new File","3":"Replace Current File with new File","description":"Life-changing utility for saving files under new names in Vim with automated clean up of the old file's buffer and hard disk version.\r\n\r\nUsage:\r\nCall the function by one of the methods below. Insert the desired new \/optional\/newpath\/filename and press <Enter>.\r\nThe new file will be saved, a buffer for it will be opened, the old file's buffer closed and the old file deleted (if was written to disk).\r\n\r\nMethod 1 (preferred):\r\n    <leader>R\r\nbrings up the function call with the current file's full path.\r\n\r\nMethod 2:\r\n     :Repfile\r\nwill operate from Vim's CWD, not with the buffers directory.\r\n\r\nMapping:\r\nThe default mapping is:\r\n    <leader>R\r\n\r\nIf you want to change that, put\r\n    let g:RepCall=\"yourmapping\"\r\nin your vimrc.\r\n\r\nAdded BufKill support to be able to delete\/unload\/wipeout a buffer without loosing it's window.\r\nGet BufKill here: vimscript#1147 (not neccessary, but really recommended)\r\n","4":"Life-changing utility for saving files under new names in Vim with automated clean up of the old file's buffer and hard disk version.\r\n\r\nUsage:\r\nCall the function by one of the methods below. Insert the desired new \/optional\/newpath\/filename and press <Enter>.\r\nThe new file will be saved, a buffer for it will be opened, the old file's buffer closed and the old file deleted (if was written to disk).\r\n\r\nMethod 1 (preferred):\r\n    <leader>R\r\nbrings up the function call with the current file's full path.\r\n\r\nMethod 2:\r\n     :Repfile\r\nwill operate from Vim's CWD, not with the buffers directory.\r\n\r\nMapping:\r\nThe default mapping is:\r\n    <leader>R\r\n\r\nIf you want to change that, put\r\n    let g:RepCall=\"yourmapping\"\r\nin your vimrc.\r\n\r\nAdded BufKill support to be able to delete\/unload\/wipeout a buffer without loosing it's window.\r\nGet BufKill here: vimscript#1147 (not neccessary, but really recommended)\r\n","install_details":"Just put the repfile.vim in your .vim\/plugin directory and restart vim!","5":"Just put the repfile.vim in your .vim\/plugin directory and restart vim!","first_name":"Jan","6":"Jan","last_name":"Mollowitz","7":"Mollowitz","releases":[{"0":"3636","vim_version":"7.0","1":"7.0","script_version":"0.9.4","2":"0.9.4","version_comment":"* added bufkill support \r\n* added custom mapping functionality","3":"* added bufkill support \r\n* added custom mapping functionality","package":"repfile.vim","4":"repfile.vim","src_id":"16106","5":"16106","creation_date":"1311156724","6":"1311156724"},{"0":"3636","vim_version":"7.0","1":"7.0","script_version":"0.9.1","2":"0.9.1","version_comment":"* beautified cmd-line input\r\n* silenced everything","3":"* beautified cmd-line input\r\n* silenced everything","package":"repfile.vim","4":"repfile.vim","src_id":"16099","5":"16099","creation_date":"1311088216","6":"1311088216"},{"0":"3636","vim_version":"7.0","1":"7.0","script_version":"0.9","2":"0.9","version_comment":"Initial upload","3":"Initial upload","package":"repfile.vim","4":"repfile.vim","src_id":"15949","5":"15949","creation_date":"1308711114","6":"1308711114"}]},"3635":{"script_id":"3635","0":"3635","script_name":"WinFastFind","1":"WinFastFind","script_type":"utility","2":"utility","summary":"Fast replacement for vim \"find\" in windows","3":"Fast replacement for vim \"find\" in windows","description":"I work on Windows at work. I have frequently found the \"find\" command on Vim to\r\nlag when the \"path\" variable is set to recurse through a large directory. This\r\nis my attempt to solve this problem.\r\n\r\nI am using an external filename search tool called \"Everything\" along with a\r\nsed script to find for files by name from VIM. ","4":"I work on Windows at work. I have frequently found the \"find\" command on Vim to\r\nlag when the \"path\" variable is set to recurse through a large directory. This\r\nis my attempt to solve this problem.\r\n\r\nI am using an external filename search tool called \"Everything\" along with a\r\nsed script to find for files by name from VIM. ","install_details":"Install the plugin using the VimBall.\r\n\r\nTo use this plugin, you need the below external tools. All of them are free.\r\nExcept for Perl, all of them have installers in KB.\r\n\r\n1. Perl - I use strawberry perl but any other version of Perl should work as\r\nwell. There is no dependency on any perl modules.\r\n\r\nhttp:\/\/strawberryperl.com\/\r\n\r\n2. Sed - I use sed from GnuWin32 on my system.\r\n\r\nhttp:\/\/gnuwin32.sourceforge.net\/packages\/sed.htm\r\n\r\n3. Everything - This is a windows file name search tool available from \r\nhttp:\/\/www.voidtools.com\/Everything-1.2.1.371.exe\r\n\r\n4. Everything command line Interface - This is a command line to obtain search\r\nresults from Everything database.  \r\n\r\nhttp:\/\/www.voidtools.com\/es.exe\r\n\r\nAfter installing the above tools, ensure that Perl,sed and es.exe are present\r\nin the system path. This can be verified by running.\r\n\r\n1. Perl -v\r\n2. sed --help\r\n3. es --help\r\n\r\nOnce the external tools are setup, install the plugin using the Vimball or the\r\nzip file. The plugin currently consists of three files.\r\n\r\nplugin\\WinFastFind.vim\r\nplugin\\handlesubsts.pl\r\ndoc\\WinFastFind.txt\r\n\r\n\r\nUsage Instructions\r\n------------------\r\n\r\n1. Set the path to include the directories you want to search. The plugin\r\nsearches these directories recursively. It is not necessary to add the ** at\r\nthe end of the path to indicate recursion.\r\n\r\n2. use \r\n\r\n:Ff <search string>\r\n\r\nto find the files. The search string can be part of the file name or part of the path.\r\n\r\n3. If there is a unique match, it is opened for editing. If there are multiple matches, a list of files is opened for selection.\r\n\r\nFor more usage instructions, please refer to the documentation.\r\n\r\nSource Code\r\n-----------\r\n\r\nThe source code is available at \r\n\r\nhttps:\/\/github.com\/vmandela\/WinFastFind","5":"Install the plugin using the VimBall.\r\n\r\nTo use this plugin, you need the below external tools. All of them are free.\r\nExcept for Perl, all of them have installers in KB.\r\n\r\n1. Perl - I use strawberry perl but any other version of Perl should work as\r\nwell. There is no dependency on any perl modules.\r\n\r\nhttp:\/\/strawberryperl.com\/\r\n\r\n2. Sed - I use sed from GnuWin32 on my system.\r\n\r\nhttp:\/\/gnuwin32.sourceforge.net\/packages\/sed.htm\r\n\r\n3. Everything - This is a windows file name search tool available from \r\nhttp:\/\/www.voidtools.com\/Everything-1.2.1.371.exe\r\n\r\n4. Everything command line Interface - This is a command line to obtain search\r\nresults from Everything database.  \r\n\r\nhttp:\/\/www.voidtools.com\/es.exe\r\n\r\nAfter installing the above tools, ensure that Perl,sed and es.exe are present\r\nin the system path. This can be verified by running.\r\n\r\n1. Perl -v\r\n2. sed --help\r\n3. es --help\r\n\r\nOnce the external tools are setup, install the plugin using the Vimball or the\r\nzip file. The plugin currently consists of three files.\r\n\r\nplugin\\WinFastFind.vim\r\nplugin\\handlesubsts.pl\r\ndoc\\WinFastFind.txt\r\n\r\n\r\nUsage Instructions\r\n------------------\r\n\r\n1. Set the path to include the directories you want to search. The plugin\r\nsearches these directories recursively. It is not necessary to add the ** at\r\nthe end of the path to indicate recursion.\r\n\r\n2. use \r\n\r\n:Ff <search string>\r\n\r\nto find the files. The search string can be part of the file name or part of the path.\r\n\r\n3. If there is a unique match, it is opened for editing. If there are multiple matches, a list of files is opened for selection.\r\n\r\nFor more usage instructions, please refer to the documentation.\r\n\r\nSource Code\r\n-----------\r\n\r\nThe source code is available at \r\n\r\nhttps:\/\/github.com\/vmandela\/WinFastFind","first_name":"Venkateswara Rao","6":"Venkateswara Rao","last_name":"Mandela","7":"Mandela","releases":[{"0":"3635","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"WinFastFind-v1.0.vba","4":"WinFastFind-v1.0.vba","src_id":"15946","5":"15946","creation_date":"1308655461","6":"1308655461"}]},"3634":{"script_id":"3634","0":"3634","script_name":"widl.vim","1":"widl.vim","script_type":"syntax","2":"syntax","summary":"Web IDL (widl) syntax highlighting","3":"Web IDL (widl) syntax highlighting","description":"Syntax Highlighting support for Web IDL files. Also supports doxygen-like commands in the comment blocks as supported by the widlproc tool.","4":"Syntax Highlighting support for Web IDL files. Also supports doxygen-like commands in the comment blocks as supported by the widlproc tool.","install_details":"On Linux:\r\nSave widl.vim to ~\/.vim\/syntax\/\r\n\r\nOn Windows:\r\nSave widl.vim into one of the following locations:\r\n  a) Your user profile path, e.g. \"C:\\Users\\username\\\" and there into \"vimfiles\\syntax\\\".\r\n  or\r\n  b) The path vim was installed to, e.g. \"C:\\Program Files\\Vim\\vimfiles\\syntax\\\".\r\n\r\nFor vim to recognize *.widl files you need to add the following to a file named filetype.vim\r\n\r\naugroup filetypedetect\r\nau BufNewFile,BufRead *.widl\tsetf widl\r\naugroup END\r\n\r\nSave that file in the \"vimfiles\" directory you chose above.","5":"On Linux:\r\nSave widl.vim to ~\/.vim\/syntax\/\r\n\r\nOn Windows:\r\nSave widl.vim into one of the following locations:\r\n  a) Your user profile path, e.g. \"C:\\Users\\username\\\" and there into \"vimfiles\\syntax\\\".\r\n  or\r\n  b) The path vim was installed to, e.g. \"C:\\Program Files\\Vim\\vimfiles\\syntax\\\".\r\n\r\nFor vim to recognize *.widl files you need to add the following to a file named filetype.vim\r\n\r\naugroup filetypedetect\r\nau BufNewFile,BufRead *.widl\tsetf widl\r\naugroup END\r\n\r\nSave that file in the \"vimfiles\" directory you chose above.","first_name":"Alexander","6":"Alexander","last_name":"Fut\u00c3\u00a1sz","7":"Fut\u00c3\u00a1sz","releases":[{"0":"3634","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"widl.vim","4":"widl.vim","src_id":"15945","5":"15945","creation_date":"1308653659","6":"1308653659"}]},"3633":{"script_id":"3633","0":"3633","script_name":"vim-snippets","1":"vim-snippets","script_type":"utility","2":"utility","summary":"snippets for a variety of vim plugins","3":"snippets for a variety of vim plugins","description":"IMPORTANT: comment on: [What about merging whith Ultisnip using its engine](https:\/\/github.com\/garbas\/vim-snipmate\/issues\/114)\r\n\r\nSnipmate & UltiSnip Snippets\r\n============================\r\n\r\nThis repository contains snippets files for various programming languages.\r\n\r\nIt is community-maintained and many people have contributed snippet files and\r\nother improvements already.\r\n\r\nContents\r\n========\r\n\r\n    snippets\/*: snippets using snipmate format\r\n    UltiSnips\/*: snippets using UltiSnips format\r\n\r\nSnippet engines\r\n===============\r\n\r\nThere are different forks of snippet engines which allow the user to insert\r\nsippets by typing the name of a snippet hitting the expansion mapping.\r\n\r\n    garbas\/vim-snipmate [4]:\r\n      VimL, snipmate-snippets, engine sometimes behaves strange, supports\r\n      rewriting snippets on the fly (eg adding a second version with folding\r\n      markers)\r\n\r\n    MarcWeber\/UltiSnips [6]:\r\n      python, snipmate-snippets and UltiSnips-snippets\r\n\r\n    SirVer\/ultisnips [7]:\r\n      python, UltiSnips-snippets\r\n\r\n    github.com\/Shougo\/neosnippet [5]:\r\n      viml, has a compatible mode allowing to reuse most snipmate snippets ?\r\n\r\n    XPTemplate:\r\n      totally different syntax, does not read snippets contained in this file,\r\n      but it is also very powerful\r\n\r\n    ... there are some more, but they have less features which is why I don't\r\n    mention them here\r\n\r\nUltiSnips engine has additional features such as \"nested snippets\".\r\n\r\nWhich one to use? If you have python give MarcWeber\/UltiSnips a try because its\r\nfast and supports all important features. You can prefer the UltiSnip versions\r\nof the snippets by setting the \"always_use_first_snippet\" option to 1.\r\n\r\nIf you have VimL only (vim without python support) your best option is using\r\ngarbas\/vim-snipmate and cope with the minor bugs found in the engine.\r\n\r\nRelated repositories\r\n====================\r\nWe also encourage people to maintain sets of snippets for particular use cases\r\nso that all users can benefit from them.  People can list their snippet repositories here:\r\n\r\n     * https:\/\/github.com\/rbonvall\/snipmate-snippets-bib (snippets for BibTeX files)\r\n     * https:\/\/github.com\/sudar\/vim-arduino-snippets (snippets for Arduino files)\r\n     * https:\/\/github.com\/zedr\/zope-snipmate-bundle.git (snippets for Python, TAL and ZCML)\r\n     * https:\/\/github.com\/bonsaiben\/bootstrap-snippets (snippets for Twitter Bootstrap markup, in HTML and Haml)\r\n\r\nInstallation using VAM: \"github:rbonvall\/snipmate-snippets-bib\"\r\n\r\n\r\n## If you believe in the success of vim-snipmate\r\nthen you may also want to have a look at [vim-git-wiki](http:\/\/github.com\/MarcWeber\/vim-git-wiki).\r\nIf you contribute to this git based wiki editable by Vim we have a chance\r\nof making it official at www.vim.org.\r\n\r\nHistorical notes\r\n================\r\n\r\n[vim-snipmate][1] was originally started by [Michael Sanders][2] who has now\r\nunfortunately abandoned the project. [Rok Garbas][3] is now maintaining a\r\n[fork][4] of the project in hopes of improving the existing code base.\r\n\r\nVersions \/ dialects \/ ..\r\n========================\r\nThere are some issues, such as newer language versions may require other\r\nsnippets than older. If this exists we currently recommend doing this:\r\n\r\nadd snippets\/ruby.snippets (common snippets)\r\nadd snippets\/ruby-1.8.snippets (1.8 only)\r\nadd snippets\/ruby-1.9.snippets (1.9 only)\r\n\r\nthen configure github.com\/garbas\/vim-snipmate this way:\r\n\r\n\r\n```vim\r\nlet g:snipMate = {}\r\nlet g:snipMate.scope_aliases = {}\r\nlet g:snipMate.scope_aliases['ruby'] = 'ruby,ruby-rails,ruby-1.9'\r\n```\r\n\r\nor github.com\/MarcWeber\/UltiSnips this way:\r\n\r\n\r\n```vim\r\nlet g:UltiSnips = {}\r\n\r\nlet g:UltiSnips.snipmate_ft_filter = {\r\n            \\ 'default' : {'filetypes': [\"FILETYPE\"] },\r\n            \\ 'ruby'    : {'filetypes': [\"ruby\", \"ruby-rails\", \"ruby-1.9\"] },\r\n```\r\n\r\nIf it happens that you work on a project requiring ruby-1.8 snippets instead,\r\nconsider using vim-addon-local-vimrc and override the filetypes.\r\n\r\nWell - of course it may not make sense to create a new file for each\r\nruby-library-version triplet. Sometimes postfixing a name such as\r\n\r\n    migrate_lib_20_down\r\n    migrate_lib_20_up\r\n\r\nwill do it then if syntax has changed.\r\n\r\nLanguage maintainers\r\n--------------------\r\n\r\nNo one can really be proficient in all programming languages. If you would like\r\nto maintain snippets for a language, please get in touch.\r\n\r\nNotes: People are interested in snippets - and their interest may stop again\r\nat will. So its ok if people maintain a language only for a short period of\r\ntime - or jump in and get things done - don't let the flow stop :)\r\nvim-snippets is not like the \"linux kernel\".\r\n\r\n* Python - [honza](http:\/\/github.com\/honza)\r\n* Javascript - [honza](http:\/\/github.com\/honza)\r\n* HTML Django - [honza](http:\/\/github.com\/honza)\r\n* Markdown - [honza](http:\/\/github.com\/honza)\r\n* Ruby - [taq](http:\/\/github.com\/taq)\r\n* PHP - [chrisyue](http:\/\/github.com\/chrisyue)\r\n* Scala - [gorodinskiy](https:\/\/github.com\/gorodinskiy)\r\n* Falcon - [steveno](https:\/\/github.com\/steveno)\r\n\r\nContributing notes\r\n------------------\r\n\r\nUntil further work is done on `vim-snipmate`, please don't add folding markers\r\ninto snippets. `vim-snipmate` has some comments about how to patch all snippets\r\non the fly adding those.\r\n\r\nBecause MarcWeber\/UltiSnips [6] supports also snipmate-snippets there is no\r\nneed to duplicate all snippets - only those snippets who use advanced UltiSnips\r\nfeatures should be duplicated in UltiSnips (?)\r\n\r\nCurrently all snippets from UltiSnips have been put into UltiSnips - some work\r\non merging should be done (dropping duplicates etc)\r\n\r\nAuthors\r\n-------\r\n\r\nFor a list of authors, please see the `AUTHORS` files.\r\n\r\nLicense\r\n-------\r\n\r\nJust as the original snipMate plugin, all the snippets are licensed under the\r\nterms of the MIT license.\r\n\r\n\r\n[1]: http:\/\/github.com\/garbas\/vim-snipmate\r\n[2]: http:\/\/github.com\/msanders\r\n[3]: http:\/\/github.com\/garbas\r\n[4]: http:\/\/github.com\/garbas\/vim-snipmate\r\n[5]: http:\/\/github.com\/Shougo\/neosnippet\r\n[6]: http:\/\/github.com\/MarcWeber\/UltiSnips\r\n[7]: http:\/\/github.com\/SirVer\/ultisnips\r\n","4":"IMPORTANT: comment on: [What about merging whith Ultisnip using its engine](https:\/\/github.com\/garbas\/vim-snipmate\/issues\/114)\r\n\r\nSnipmate & UltiSnip Snippets\r\n============================\r\n\r\nThis repository contains snippets files for various programming languages.\r\n\r\nIt is community-maintained and many people have contributed snippet files and\r\nother improvements already.\r\n\r\nContents\r\n========\r\n\r\n    snippets\/*: snippets using snipmate format\r\n    UltiSnips\/*: snippets using UltiSnips format\r\n\r\nSnippet engines\r\n===============\r\n\r\nThere are different forks of snippet engines which allow the user to insert\r\nsippets by typing the name of a snippet hitting the expansion mapping.\r\n\r\n    garbas\/vim-snipmate [4]:\r\n      VimL, snipmate-snippets, engine sometimes behaves strange, supports\r\n      rewriting snippets on the fly (eg adding a second version with folding\r\n      markers)\r\n\r\n    MarcWeber\/UltiSnips [6]:\r\n      python, snipmate-snippets and UltiSnips-snippets\r\n\r\n    SirVer\/ultisnips [7]:\r\n      python, UltiSnips-snippets\r\n\r\n    github.com\/Shougo\/neosnippet [5]:\r\n      viml, has a compatible mode allowing to reuse most snipmate snippets ?\r\n\r\n    XPTemplate:\r\n      totally different syntax, does not read snippets contained in this file,\r\n      but it is also very powerful\r\n\r\n    ... there are some more, but they have less features which is why I don't\r\n    mention them here\r\n\r\nUltiSnips engine has additional features such as \"nested snippets\".\r\n\r\nWhich one to use? If you have python give MarcWeber\/UltiSnips a try because its\r\nfast and supports all important features. You can prefer the UltiSnip versions\r\nof the snippets by setting the \"always_use_first_snippet\" option to 1.\r\n\r\nIf you have VimL only (vim without python support) your best option is using\r\ngarbas\/vim-snipmate and cope with the minor bugs found in the engine.\r\n\r\nRelated repositories\r\n====================\r\nWe also encourage people to maintain sets of snippets for particular use cases\r\nso that all users can benefit from them.  People can list their snippet repositories here:\r\n\r\n     * https:\/\/github.com\/rbonvall\/snipmate-snippets-bib (snippets for BibTeX files)\r\n     * https:\/\/github.com\/sudar\/vim-arduino-snippets (snippets for Arduino files)\r\n     * https:\/\/github.com\/zedr\/zope-snipmate-bundle.git (snippets for Python, TAL and ZCML)\r\n     * https:\/\/github.com\/bonsaiben\/bootstrap-snippets (snippets for Twitter Bootstrap markup, in HTML and Haml)\r\n\r\nInstallation using VAM: \"github:rbonvall\/snipmate-snippets-bib\"\r\n\r\n\r\n## If you believe in the success of vim-snipmate\r\nthen you may also want to have a look at [vim-git-wiki](http:\/\/github.com\/MarcWeber\/vim-git-wiki).\r\nIf you contribute to this git based wiki editable by Vim we have a chance\r\nof making it official at www.vim.org.\r\n\r\nHistorical notes\r\n================\r\n\r\n[vim-snipmate][1] was originally started by [Michael Sanders][2] who has now\r\nunfortunately abandoned the project. [Rok Garbas][3] is now maintaining a\r\n[fork][4] of the project in hopes of improving the existing code base.\r\n\r\nVersions \/ dialects \/ ..\r\n========================\r\nThere are some issues, such as newer language versions may require other\r\nsnippets than older. If this exists we currently recommend doing this:\r\n\r\nadd snippets\/ruby.snippets (common snippets)\r\nadd snippets\/ruby-1.8.snippets (1.8 only)\r\nadd snippets\/ruby-1.9.snippets (1.9 only)\r\n\r\nthen configure github.com\/garbas\/vim-snipmate this way:\r\n\r\n\r\n```vim\r\nlet g:snipMate = {}\r\nlet g:snipMate.scope_aliases = {}\r\nlet g:snipMate.scope_aliases['ruby'] = 'ruby,ruby-rails,ruby-1.9'\r\n```\r\n\r\nor github.com\/MarcWeber\/UltiSnips this way:\r\n\r\n\r\n```vim\r\nlet g:UltiSnips = {}\r\n\r\nlet g:UltiSnips.snipmate_ft_filter = {\r\n            \\ 'default' : {'filetypes': [\"FILETYPE\"] },\r\n            \\ 'ruby'    : {'filetypes': [\"ruby\", \"ruby-rails\", \"ruby-1.9\"] },\r\n```\r\n\r\nIf it happens that you work on a project requiring ruby-1.8 snippets instead,\r\nconsider using vim-addon-local-vimrc and override the filetypes.\r\n\r\nWell - of course it may not make sense to create a new file for each\r\nruby-library-version triplet. Sometimes postfixing a name such as\r\n\r\n    migrate_lib_20_down\r\n    migrate_lib_20_up\r\n\r\nwill do it then if syntax has changed.\r\n\r\nLanguage maintainers\r\n--------------------\r\n\r\nNo one can really be proficient in all programming languages. If you would like\r\nto maintain snippets for a language, please get in touch.\r\n\r\nNotes: People are interested in snippets - and their interest may stop again\r\nat will. So its ok if people maintain a language only for a short period of\r\ntime - or jump in and get things done - don't let the flow stop :)\r\nvim-snippets is not like the \"linux kernel\".\r\n\r\n* Python - [honza](http:\/\/github.com\/honza)\r\n* Javascript - [honza](http:\/\/github.com\/honza)\r\n* HTML Django - [honza](http:\/\/github.com\/honza)\r\n* Markdown - [honza](http:\/\/github.com\/honza)\r\n* Ruby - [taq](http:\/\/github.com\/taq)\r\n* PHP - [chrisyue](http:\/\/github.com\/chrisyue)\r\n* Scala - [gorodinskiy](https:\/\/github.com\/gorodinskiy)\r\n* Falcon - [steveno](https:\/\/github.com\/steveno)\r\n\r\nContributing notes\r\n------------------\r\n\r\nUntil further work is done on `vim-snipmate`, please don't add folding markers\r\ninto snippets. `vim-snipmate` has some comments about how to patch all snippets\r\non the fly adding those.\r\n\r\nBecause MarcWeber\/UltiSnips [6] supports also snipmate-snippets there is no\r\nneed to duplicate all snippets - only those snippets who use advanced UltiSnips\r\nfeatures should be duplicated in UltiSnips (?)\r\n\r\nCurrently all snippets from UltiSnips have been put into UltiSnips - some work\r\non merging should be done (dropping duplicates etc)\r\n\r\nAuthors\r\n-------\r\n\r\nFor a list of authors, please see the `AUTHORS` files.\r\n\r\nLicense\r\n-------\r\n\r\nJust as the original snipMate plugin, all the snippets are licensed under the\r\nterms of the MIT license.\r\n\r\n\r\n[1]: http:\/\/github.com\/garbas\/vim-snipmate\r\n[2]: http:\/\/github.com\/msanders\r\n[3]: http:\/\/github.com\/garbas\r\n[4]: http:\/\/github.com\/garbas\/vim-snipmate\r\n[5]: http:\/\/github.com\/Shougo\/neosnippet\r\n[6]: http:\/\/github.com\/MarcWeber\/UltiSnips\r\n[7]: http:\/\/github.com\/SirVer\/ultisnips\r\n","install_details":"cd ~\/.vim\r\ngit clone git:\/\/github.com\/honza\/vim-snippets.git","5":"cd ~\/.vim\r\ngit clone git:\/\/github.com\/honza\/vim-snippets.git","first_name":"Honza","6":"Honza","last_name":"Pokorny","7":"Pokorny","releases":[{"0":"3633","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"snipmate-snippets.tar.gz","4":"snipmate-snippets.tar.gz","src_id":"15944","5":"15944","creation_date":"1308651359","6":"1308651359"}]},"3632":{"script_id":"3632","0":"3632","script_name":"git_patch_tags.vim","1":"git_patch_tags.vim","script_type":"utility","2":"utility","summary":"Global plugin for adding patch tags from linux SubmittingPatches document","3":"Global plugin for adding patch tags from linux SubmittingPatches document","description":"Global plugin for adding patch tags as defined in the linux kernel\r\nDocumentation\/SubmittingPatches document, examples of patch tags are:\r\n - Acked-by\r\n - Signed-off-by\r\n - Tested-by\r\n - Reviewed-by\r\n\r\nthe plugin allows to add also a Copyright line.\r\n\r\nThe author name and email address are retrieved from the git configuration.\r\n\r\nExamples:\r\n\r\n  <Leader>ack\r\n          Add a Acked-by tag getting developer info from git config\r\n\r\n  <Leader>cpy\r\n          Add a copyright line getting developer info from git config and using\r\n          the current date\r\n\r\n  <Leader>rev\r\n          Add a Reviewed-by tag getting developer info from git config\r\n\r\n  <Leader>sob\r\n          Add a Signed-off-by tag getting developer info from git config\r\n\r\n  <Leader>tst\r\n          Add a Tested-by tag getting developer info from git config\r\n","4":"Global plugin for adding patch tags as defined in the linux kernel\r\nDocumentation\/SubmittingPatches document, examples of patch tags are:\r\n - Acked-by\r\n - Signed-off-by\r\n - Tested-by\r\n - Reviewed-by\r\n\r\nthe plugin allows to add also a Copyright line.\r\n\r\nThe author name and email address are retrieved from the git configuration.\r\n\r\nExamples:\r\n\r\n  <Leader>ack\r\n          Add a Acked-by tag getting developer info from git config\r\n\r\n  <Leader>cpy\r\n          Add a copyright line getting developer info from git config and using\r\n          the current date\r\n\r\n  <Leader>rev\r\n          Add a Reviewed-by tag getting developer info from git config\r\n\r\n  <Leader>sob\r\n          Add a Signed-off-by tag getting developer info from git config\r\n\r\n  <Leader>tst\r\n          Add a Tested-by tag getting developer info from git config\r\n","install_details":"Drop git_patch_tags.vim into your $HOME\/.vim\/plugin directory.\r\n","5":"Drop git_patch_tags.vim into your $HOME\/.vim\/plugin directory.\r\n","first_name":"Antonio","6":"Antonio","last_name":"Ospite","7":"Ospite","releases":[{"0":"3632","vim_version":"7.0","1":"7.0","script_version":"0.2","2":"0.2","version_comment":"Strip terminating NULL characters from the git commands\r\n\r\nThis is needed in order to prevent having ^A outputted in the git tags strings, because the system() function in vim is supposed to replace all NUL characters with SOH (0x01); see :help system.\r\n\r\nThe previous version of the script was working fine in 7.3 even without stripping the terminating NULL, but in 7.4 the behavior changed, see:\r\nhttp:\/\/code.google.com\/p\/vim\/source\/detail?r=25f67b62afd8c58b6c661961cc762f00ee89e562#\r\nhttp:\/\/code.google.com\/p\/vim\/source\/detail?r=3ddec3d25bd178d4f90114bce9ce889f3889e6d2#\r\n","3":"Strip terminating NULL characters from the git commands\r\n\r\nThis is needed in order to prevent having ^A outputted in the git tags strings, because the system() function in vim is supposed to replace all NUL characters with SOH (0x01); see :help system.\r\n\r\nThe previous version of the script was working fine in 7.3 even without stripping the terminating NULL, but in 7.4 the behavior changed, see:\r\nhttp:\/\/code.google.com\/p\/vim\/source\/detail?r=25f67b62afd8c58b6c661961cc762f00ee89e562#\r\nhttp:\/\/code.google.com\/p\/vim\/source\/detail?r=3ddec3d25bd178d4f90114bce9ce889f3889e6d2#\r\n","package":"git_patch_tags.vim","4":"git_patch_tags.vim","src_id":"20912","5":"20912","creation_date":"1381502545","6":"1381502545"},{"0":"3632","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"git_patch_tags.vim","4":"git_patch_tags.vim","src_id":"15938","5":"15938","creation_date":"1308556884","6":"1308556884"}]},"3631":{"script_id":"3631","0":"3631","script_name":"frawor","1":"frawor","script_type":"utility","2":"utility","summary":"Vim framework","3":"Vim framework","description":"Frawor is a modular vim framework designed to collect some commonly needed \r\nfunctions.\r\n\r\nTo start using the only thing you should do is to add\r\n\r\n    execute frawor#Setup('0.0', {})\r\n\r\nwhere '0.0' is your plugin version and {} is a dictionary containing plugin \r\ndependencies (the core frawor module is added to dependencies automatically). \r\nThere are additional rules you should follow:\r\n\r\n1. All script-local functions should be anonymous functions:\r\n\r\n        function s:F.somefunc(args)\r\n\r\n    In some plugins you may even end with having no non-anonymous function \r\n    definitions.\r\n\r\n2. If function cannot be anonymous (because it is is to be used by `sort()`, for \r\n    example), then its name should be added to `s:_functions` list.\r\n\r\n3. If you define a command, its name should go to `s:_commands` list, same for \r\n    autocommand groups (`s:_augroups`).\r\n\r\n4. All script-local variables whose name starts with `s:_` are reserved and \r\n    should be used only in a way described in documentation.\r\n\r\nAdvantages\r\n==========\r\n\r\n1. Plugin reloading for easier development and updates without vim restart:\r\n\r\n        call frawor#Reload('plugin\/frawor')\r\n\r\n    to reload all plugins (as they all depend on core frawor module).\r\n\r\n2. Frawor provides an easier way to mappings customization:\r\n\r\n        execute frawor#Setup('0.0', {'@\/mappings': '0.0'})\r\n        <...>\r\n        call s:_f.mapgroup.add('Foo',\r\n                \\{'bar': {'lhs': 't', 'rhs': ':Bar<CR>'},\r\n                \\ 'baz': {'lhs': 'T', 'rhs': s:F.baz}},\r\n            \\{'leader': '<leader>', 'silent': 1})\r\n    will define two mappings: `<leader>t` which will call command `:Bar` and \r\n    `<leader>T` which will run `s:F.baz` function. Both mappings are silent. Now \r\n    pretend that you are the user who does not need to run `s:F.baz` and wants to \r\n    launch `:Bar` using `,t`. In this case all he needs is to add the following \r\n    lines to the vimrc:\r\n\r\n        let g:frawormap_Foo=','\r\n\r\n        let g:frawormap_Foo_bar='t'\r\n        let g:frawormap_Foo_baz=0\r\n\r\n    Replacing `','` with `0` here will lead to disabling the whole mapping \r\n    group.\r\n\r\n3. Options:\r\n\r\n        \"plugin\/foo.vim:\r\n        execute frawor#Setup('0.0', {'@\/options': '0.0'})\r\n        let s:_options={'columns': {'default': 80, 'checker': 'range 0 inf'}}\r\n        <...>\r\n                    let columns=s:_f.getoption('columns')\r\n        <...>\r\n\r\n        \"vimrc:\r\n        let g:foo_columns=78\r\n        autocmd FileType vim  let b:foo_columns=78\r\n    If you don't want to prefix your options with `foo` (second component after \r\n    runtimepath of a path to your plugin), define `s:_oprefix`. Note the \r\n    `checker` key: it saves you from writing code for checking user input (but \r\n    will instead generate an exception for invalid value).\r\n\r\n4. Function argument checks:\r\n\r\n        execute frawor#Setup('0.0', {'@\/functions': '0.0'})\r\n        let s:formats={'html': ...,\r\n                      \\'markdown': ...}\r\n        function s:F.checkedfunc(format, columns)\r\n            <...>\r\n        endfunction\r\n        let s:F.checkedfunc=s:_f.wrapfunc({'function': s:F.checkedfunc,\r\n                                          \\'@FWC': ['key formats  '.\r\n                                          \\         'range 0 inf', 'check'],})\r\n\r\n    Here you can see FWC decorator which uses FWC-to-vimscript compiler where FWC \r\n    is a name of the domain-specific language written exclusively for frawor.\r\n\r\n5. Complicated command-line arguments handling:\r\n\r\n        execute frawor#Setup('0.0', {'@\/commands': '0.0'})\r\n        let s:formats={'html': ...,\r\n                      \\'markdown': ...,}\r\n        function s:F.run_foo(options)\r\n            \" Here a:options is dictionary containing all prefixed options user\r\n            \" have given on the command-line\r\n            let format=a:options.format\r\n            let columns=a:options.columns\r\n            if a:options.beatify\r\n                <...>\r\n            endif\r\n        endfunction\r\n        \"                Prefix  default  Description of\r\n        \"                         value   the prefix argument\r\n        let s:foo_args='{columns :=(80)   |earg range 0 inf '.\r\n                      \\'  format          key formats '.\r\n                      \\'!beatify :=(0)'}'\r\n        \" Define a :Foo command\r\n        call s:_f.command.add('Foo', {'function': s:F.run_foo,\r\n                                     \\    '@FWC': [s:foo_args, 'filter'],}\r\n                             \\{'complete': [s:foo_args], 'nargs': '+'})\r\n        \" \" Example usage:\r\n        \" Foo col 78 f markdown\r\n        \" Foo nobeatify f html\r\n        \" Foo format html beatify c 78\r\n\r\n    Note that while command accepts short versions of prefixes, `s:F.run_foo` \r\n    function will get dictionary with only full names.\r\n\r\n6. Portable versions of OS-specific functions: vimscript implementation of some \r\n    functions from python os module.\r\n\r\n7. Vimscript base64 encoder\/decoder, fancy table echoing, maparg that returns \r\n    dictionary for old vim's and more.\r\n\r\nProject page: https:\/\/bitbucket.org\/ZyX_I\/frawor\r\nDocumentation: http:\/\/vimpluginloader.sourceforge.net\/doc\/frawor.txt.html","4":"Frawor is a modular vim framework designed to collect some commonly needed \r\nfunctions.\r\n\r\nTo start using the only thing you should do is to add\r\n\r\n    execute frawor#Setup('0.0', {})\r\n\r\nwhere '0.0' is your plugin version and {} is a dictionary containing plugin \r\ndependencies (the core frawor module is added to dependencies automatically). \r\nThere are additional rules you should follow:\r\n\r\n1. All script-local functions should be anonymous functions:\r\n\r\n        function s:F.somefunc(args)\r\n\r\n    In some plugins you may even end with having no non-anonymous function \r\n    definitions.\r\n\r\n2. If function cannot be anonymous (because it is is to be used by `sort()`, for \r\n    example), then its name should be added to `s:_functions` list.\r\n\r\n3. If you define a command, its name should go to `s:_commands` list, same for \r\n    autocommand groups (`s:_augroups`).\r\n\r\n4. All script-local variables whose name starts with `s:_` are reserved and \r\n    should be used only in a way described in documentation.\r\n\r\nAdvantages\r\n==========\r\n\r\n1. Plugin reloading for easier development and updates without vim restart:\r\n\r\n        call frawor#Reload('plugin\/frawor')\r\n\r\n    to reload all plugins (as they all depend on core frawor module).\r\n\r\n2. Frawor provides an easier way to mappings customization:\r\n\r\n        execute frawor#Setup('0.0', {'@\/mappings': '0.0'})\r\n        <...>\r\n        call s:_f.mapgroup.add('Foo',\r\n                \\{'bar': {'lhs': 't', 'rhs': ':Bar<CR>'},\r\n                \\ 'baz': {'lhs': 'T', 'rhs': s:F.baz}},\r\n            \\{'leader': '<leader>', 'silent': 1})\r\n    will define two mappings: `<leader>t` which will call command `:Bar` and \r\n    `<leader>T` which will run `s:F.baz` function. Both mappings are silent. Now \r\n    pretend that you are the user who does not need to run `s:F.baz` and wants to \r\n    launch `:Bar` using `,t`. In this case all he needs is to add the following \r\n    lines to the vimrc:\r\n\r\n        let g:frawormap_Foo=','\r\n\r\n        let g:frawormap_Foo_bar='t'\r\n        let g:frawormap_Foo_baz=0\r\n\r\n    Replacing `','` with `0` here will lead to disabling the whole mapping \r\n    group.\r\n\r\n3. Options:\r\n\r\n        \"plugin\/foo.vim:\r\n        execute frawor#Setup('0.0', {'@\/options': '0.0'})\r\n        let s:_options={'columns': {'default': 80, 'checker': 'range 0 inf'}}\r\n        <...>\r\n                    let columns=s:_f.getoption('columns')\r\n        <...>\r\n\r\n        \"vimrc:\r\n        let g:foo_columns=78\r\n        autocmd FileType vim  let b:foo_columns=78\r\n    If you don't want to prefix your options with `foo` (second component after \r\n    runtimepath of a path to your plugin), define `s:_oprefix`. Note the \r\n    `checker` key: it saves you from writing code for checking user input (but \r\n    will instead generate an exception for invalid value).\r\n\r\n4. Function argument checks:\r\n\r\n        execute frawor#Setup('0.0', {'@\/functions': '0.0'})\r\n        let s:formats={'html': ...,\r\n                      \\'markdown': ...}\r\n        function s:F.checkedfunc(format, columns)\r\n            <...>\r\n        endfunction\r\n        let s:F.checkedfunc=s:_f.wrapfunc({'function': s:F.checkedfunc,\r\n                                          \\'@FWC': ['key formats  '.\r\n                                          \\         'range 0 inf', 'check'],})\r\n\r\n    Here you can see FWC decorator which uses FWC-to-vimscript compiler where FWC \r\n    is a name of the domain-specific language written exclusively for frawor.\r\n\r\n5. Complicated command-line arguments handling:\r\n\r\n        execute frawor#Setup('0.0', {'@\/commands': '0.0'})\r\n        let s:formats={'html': ...,\r\n                      \\'markdown': ...,}\r\n        function s:F.run_foo(options)\r\n            \" Here a:options is dictionary containing all prefixed options user\r\n            \" have given on the command-line\r\n            let format=a:options.format\r\n            let columns=a:options.columns\r\n            if a:options.beatify\r\n                <...>\r\n            endif\r\n        endfunction\r\n        \"                Prefix  default  Description of\r\n        \"                         value   the prefix argument\r\n        let s:foo_args='{columns :=(80)   |earg range 0 inf '.\r\n                      \\'  format          key formats '.\r\n                      \\'!beatify :=(0)'}'\r\n        \" Define a :Foo command\r\n        call s:_f.command.add('Foo', {'function': s:F.run_foo,\r\n                                     \\    '@FWC': [s:foo_args, 'filter'],}\r\n                             \\{'complete': [s:foo_args], 'nargs': '+'})\r\n        \" \" Example usage:\r\n        \" Foo col 78 f markdown\r\n        \" Foo nobeatify f html\r\n        \" Foo format html beatify c 78\r\n\r\n    Note that while command accepts short versions of prefixes, `s:F.run_foo` \r\n    function will get dictionary with only full names.\r\n\r\n6. Portable versions of OS-specific functions: vimscript implementation of some \r\n    functions from python os module.\r\n\r\n7. Vimscript base64 encoder\/decoder, fancy table echoing, maparg that returns \r\n    dictionary for old vim's and more.\r\n\r\nProject page: https:\/\/bitbucket.org\/ZyX_I\/frawor\r\nDocumentation: http:\/\/vimpluginloader.sourceforge.net\/doc\/frawor.txt.html","install_details":"Plugin can be installed using vim-addon-manager (script #2905).","5":"Plugin can be installed using vim-addon-manager (script #2905).","first_name":"ZyX","6":"ZyX","last_name":" ","7":" ","releases":[{"0":"3631","vim_version":"7.3","1":"7.3","script_version":"0.2.4","2":"0.2.4","version_comment":"Make frawor work with newer Vim versions","3":"Make frawor work with newer Vim versions","package":"frawor-0.2.4.tar.xz","4":"frawor-0.2.4.tar.xz","src_id":"28344","5":"28344","creation_date":"1673408704","6":"1673408704"},{"0":"3631","vim_version":"7.3","1":"7.3","script_version":"0.2.3","2":"0.2.3","version_comment":"Add a workaround for the vim bug described in https:\/\/groups.google.com\/forum\/#!topic\/vim_dev\/1M7UMk-E1to","3":"Add a workaround for the vim bug described in https:\/\/groups.google.com\/forum\/#!topic\/vim_dev\/1M7UMk-E1to","package":"frawor-0.2.3.tar.gz","4":"frawor-0.2.3.tar.gz","src_id":"20862","5":"20862","creation_date":"1380463573","6":"1380463573"},{"0":"3631","vim_version":"7.3","1":"7.3","script_version":"0.2.2","2":"0.2.2","version_comment":"Added frawor-od-override [1]\n\n[1] http:\/\/vimpluginloader.sourceforge.net\/doc\/frawor.txt.html#frawor-od-override\n","3":"Added frawor-od-override [1]\n\n[1] http:\/\/vimpluginloader.sourceforge.net\/doc\/frawor.txt.html#frawor-od-override\n","package":"frawor-0.2.2.tar.gz","4":"frawor-0.2.2.tar.gz","src_id":"20822","5":"20822","creation_date":"1379794645","6":"1379794645"},{"0":"3631","vim_version":"7.3","1":"7.3","script_version":"0.2.1","2":"0.2.1","version_comment":"Made loading of command dictionary functions (it and completion) more lazy\nAdded “usedictcompsplitfunc” command option","3":"Made loading of command dictionary functions (it and completion) more lazy\nAdded “usedictcompsplitfunc” command option","package":"frawor-0.2.1.tar.gz","4":"frawor-0.2.1.tar.gz","src_id":"19488","5":"19488","creation_date":"1360408500","6":"1360408500"},{"0":"3631","vim_version":"7.3","1":"7.3","script_version":"0.2","2":"0.2","version_comment":"Removed double loading functionality. It is assumed now that you split files into plugin\/ with interface and autoload\/ with everything else\nMoved almost everything from plugin\/ to autoload\/\nImproved @\/python: it now supports case “both pythons are present”. Python3 modules are loaded from python3\/, python2 from python\/; removed s:_r.py resource\nMade @\/signs and @\/commands features not be ignoredeps ones\nAdded function autoloading support: "function" key value may be 3-tuple [{plid}, {plver}, {funcname}], {funcname} is pulled from s:_aufunctions dictionary","3":"Removed double loading functionality. It is assumed now that you split files into plugin\/ with interface and autoload\/ with everything else\nMoved almost everything from plugin\/ to autoload\/\nImproved @\/python: it now supports case “both pythons are present”. Python3 modules are loaded from python3\/, python2 from python\/; removed s:_r.py resource\nMade @\/signs and @\/commands features not be ignoredeps ones\nAdded function autoloading support: "function" key value may be 3-tuple [{plid}, {plver}, {funcname}], {funcname} is pulled from s:_aufunctions dictionary","package":"frawor-0.2.tar.gz","4":"frawor-0.2.tar.gz","src_id":"19482","5":"19482","creation_date":"1360345431","6":"1360345431"},{"0":"3631","vim_version":"7.3","1":"7.3","script_version":"0.1.24","2":"0.1.24","version_comment":"Added some code minimization possibilities to @\/fwc\/constructor","3":"Added some code minimization possibilities to @\/fwc\/constructor","package":"frawor-0.1.24.tar.gz","4":"frawor-0.1.24.tar.gz","src_id":"18675","5":"18675","creation_date":"1348412728","6":"1348412728"},{"0":"3631","vim_version":"7.3","1":"7.3","script_version":"0.1.23","2":"0.1.23","version_comment":"@\/fwc\/constructor refactoring and documenting: it can now be used outside of FWC\n@\/fwc\/*: Added support for numbers in place of variables: now “1” no longer refers to “s:1”","3":"@\/fwc\/constructor refactoring and documenting: it can now be used outside of FWC\n@\/fwc\/*: Added support for numbers in place of variables: now “1” no longer refers to “s:1”","package":"frawor-0.1.23.tar.gz","4":"frawor-0.1.23.tar.gz","src_id":"18613","5":"18613","creation_date":"1347718609","6":"1347718609"},{"0":"3631","vim_version":"7.3","1":"7.3","script_version":"0.1.22","2":"0.1.22","version_comment":"Optimization and minor bug fixes","3":"Optimization and minor bug fixes","package":"frawor-0.1.22.tar.gz","4":"frawor-0.1.22.tar.gz","src_id":"17515","5":"17515","creation_date":"1329943212","6":"1329943212"},{"0":"3631","vim_version":"7.3","1":"7.3","script_version":"0.1.21","2":"0.1.21","version_comment":"Added require core feature\nAdded s:_loading variable","3":"Added require core feature\nAdded s:_loading variable","package":"frawor-0.1.21.tar.gz","4":"frawor-0.1.21.tar.gz","src_id":"17507","5":"17507","creation_date":"1329800104","6":"1329800104"},{"0":"3631","vim_version":"7.3","1":"7.3","script_version":"0.1.20","2":"0.1.20","version_comment":"Added os.readsystem() function\nMade os.run also accept plain strings as the first","3":"Added os.readsystem() function\nMade os.run also accept plain strings as the first","package":"frawor-0.1.20.tar.gz","4":"frawor-0.1.20.tar.gz","src_id":"17493","5":"17493","creation_date":"1329666449","6":"1329666449"},{"0":"3631","vim_version":"7.3","1":"7.3","script_version":"0.1.19","2":"0.1.19","version_comment":"Made plugin\/frawor\/base64 use built-in and() and or() functions if they are available\nRefactored plugin\/frawor\/fwc\/constructor","3":"Made plugin\/frawor\/base64 use built-in and() and or() functions if they are available\nRefactored plugin\/frawor\/fwc\/constructor","package":"frawor-0.1.19.tar.gz","4":"frawor-0.1.19.tar.gz","src_id":"17490","5":"17490","creation_date":"1329603109","6":"1329603109"},{"0":"3631","vim_version":"7.3","1":"7.3","script_version":"0.1.18","2":"0.1.18","version_comment":"Fixed FraworLoad({expandable_plid})","3":"Fixed FraworLoad({expandable_plid})","package":"frawor-0.1.18.tar.gz","4":"frawor-0.1.18.tar.gz","src_id":"16864","5":"16864","creation_date":"1321331368","6":"1321331368"},{"0":"3631","vim_version":"7.3","1":"7.3","script_version":"0.1.16","2":"0.1.16","version_comment":"Fixed os.path.abspath and os.path.exists under windows","3":"Fixed os.path.abspath and os.path.exists under windows","package":"frawor-0.1.16.tar.gz","4":"frawor-0.1.16.tar.gz","src_id":"16833","5":"16833","creation_date":"1320781284","6":"1320781284"},{"0":"3631","vim_version":"7.3","1":"7.3","script_version":"0.1.15","2":"0.1.15","version_comment":"Made `isfunc' be also a filter\nLarge perfomance improvements, fixed plugin reloading\nVarious completion fixes","3":"Made `isfunc' be also a filter\nLarge perfomance improvements, fixed plugin reloading\nVarious completion fixes","package":"frawor-0.1.15.tar.gz","4":"frawor-0.1.15.tar.gz","src_id":"16832","5":"16832","creation_date":"1320778252","6":"1320778252"},{"0":"3631","vim_version":"7.3","1":"7.3","script_version":"0.1.14","2":"0.1.14","version_comment":"Fixed behavior of the plugin when &wildignore is "*"","3":"Fixed behavior of the plugin when &wildignore is "*"","package":"frawor-0.1.14.tar.gz","4":"frawor-0.1.14.tar.gz","src_id":"16335","5":"16335","creation_date":"1314116135","6":"1314116135"},{"0":"3631","vim_version":"7.2.242","1":"7.2.242","script_version":"0.1.13","2":"0.1.13","version_comment":"Various compatibility improvements (now works on vim-7.2.242)\n@\/decorators\/altervars: Added `folds' special setter\n@\/fwc: Made `range' check be aware of -onlystrings option, various fixes","3":"Various compatibility improvements (now works on vim-7.2.242)\n@\/decorators\/altervars: Added `folds' special setter\n@\/fwc: Made `range' check be aware of -onlystrings option, various fixes","package":"frawor-0.1.13.tar.gz","4":"frawor-0.1.13.tar.gz","src_id":"16311","5":"16311","creation_date":"1313871313","6":"1313871313"},{"0":"3631","vim_version":"7.3","1":"7.3","script_version":"0.1.11","2":"0.1.11","version_comment":"@\/os: Made relpath be aware of paths with trailing path separators","3":"@\/os: Made relpath be aware of paths with trailing path separators","package":"frawor-0.1.11.tar.gz","4":"frawor-0.1.11.tar.gz","src_id":"16113","5":"16113","creation_date":"1311196049","6":"1311196049"},{"0":"3631","vim_version":"7.3","1":"7.3","script_version":"0.1.10","2":"0.1.10","version_comment":"@\/os: Added os.path.relpath function\n      Made abspath also work for paths like a\/b\/c where a\/ does not exist\n      Made os.path.normpath also simplify its argument","3":"@\/os: Added os.path.relpath function\n      Made abspath also work for paths like a\/b\/c where a\/ does not exist\n      Made os.path.normpath also simplify its argument","package":"frawor-0.1.10.tar.gz","4":"frawor-0.1.10.tar.gz","src_id":"16110","5":"16110","creation_date":"1311193240","6":"1311193240"},{"0":"3631","vim_version":"7.3","1":"7.3","script_version":"0.1.9","2":"0.1.9","version_comment":"@\/os: Added os.path.relpath function\n      Made abspath also work for paths like a\/b\/c where a\/ does not exist\n      Made os.path.normpath also simplify its argument","3":"@\/os: Added os.path.relpath function\n      Made abspath also work for paths like a\/b\/c where a\/ does not exist\n      Made os.path.normpath also simplify its argument","package":"frawor-0.1.9.tar.gz","4":"frawor-0.1.9.tar.gz","src_id":"16109","5":"16109","creation_date":"1311191297","6":"1311191297"},{"0":"3631","vim_version":"7.3","1":"7.3","script_version":"0.1.8","2":"0.1.8","version_comment":"Improved `path pipe and completion\\nMade unmap handle «... does not exist» error","3":"Improved `path pipe and completion\\nMade unmap handle «... does not exist» error","package":"frawor-0.1.8.tar.gz","4":"frawor-0.1.8.tar.gz","src_id":"16085","5":"16085","creation_date":"1310892941","6":"1310892941"},{"0":"3631","vim_version":"7.3","1":"7.3","script_version":"0.1.7","2":"0.1.7","version_comment":"@\/table: Improved stdisplaywidth emulation\n@\/fwc\/compiler: Fixed `cur arguments inside {optional} section","3":"@\/table: Improved stdisplaywidth emulation\n@\/fwc\/compiler: Fixed `cur arguments inside {optional} section","package":"frawor-0.1.7.tar.gz","4":"frawor-0.1.7.tar.gz","src_id":"15981","5":"15981","creation_date":"1309097615","6":"1309097615"},{"0":"3631","vim_version":"7.3","1":"7.3","script_version":"0.1.6","2":"0.1.6","version_comment":"Fixed completion and checker for +history altervars special","3":"Fixed completion and checker for +history altervars special","package":"frawor-0.1.6.tar.gz","4":"frawor-0.1.6.tar.gz","src_id":"15973","5":"15973","creation_date":"1309009171","6":"1309009171"},{"0":"3631","vim_version":"7.3","1":"7.3","script_version":"0.1.5","2":"0.1.5","version_comment":"@\/fwc changes:\n- Added `idof check\\n- Fixed `either' key: checks in alternatives were effectively ignored","3":"@\/fwc changes:\n- Added `idof check\\n- Fixed `either' key: checks in alternatives were effectively ignored","package":"frawor-0.1.5.tar.gz","4":"frawor-0.1.5.tar.gz","src_id":"15971","5":"15971","creation_date":"1308934693","6":"1308934693"},{"0":"3631","vim_version":"7.3","1":"7.3","script_version":"0.1.4","2":"0.1.4","version_comment":"Added @\/history module","3":"Added @\/history module","package":"frawor-0.1.4.tar.gz","4":"frawor-0.1.4.tar.gz","src_id":"15951","5":"15951","creation_date":"1308718235","6":"1308718235"},{"0":"3631","vim_version":"7.3","1":"7.3","script_version":"0.1.3","2":"0.1.3","version_comment":"@\/mappings: Added possibility to specify functions in `strfunc and `func' keys (required for plugin autoloading)\\n@\/table: Posted strdisplaywidth function (relevant for old vims, for newer ones it is just a reference to built-in strdisplaywidth)","3":"@\/mappings: Added possibility to specify functions in `strfunc and `func' keys (required for plugin autoloading)\\n@\/table: Posted strdisplaywidth function (relevant for old vims, for newer ones it is just a reference to built-in strdisplaywidth)","package":"frawor-0.1.3.tar.gz","4":"frawor-0.1.3.tar.gz","src_id":"15950","5":"15950","creation_date":"1308712821","6":"1308712821"},{"0":"3631","vim_version":"7.3","1":"7.3","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"frawor-0.1.tar.gz","4":"frawor-0.1.tar.gz","src_id":"15934","5":"15934","creation_date":"1308487581","6":"1308487581"}]},"3630":{"script_id":"3630","0":"3630","script_name":"IDSearch","1":"IDSearch","script_type":"utility","2":"utility","summary":"Plugin to supplement id-utils gid command for super-fast find-in-files.","3":"Plugin to supplement id-utils gid command for super-fast find-in-files.","description":"This is a plugin to use id-utils (http:\/\/www.gnu.org\/software\/idutils\/) gid command for quickly finding in files. This plugin searches for a given word and lists the results in a small window. As you move over the results, each file is shown in the preview window. \r\n\r\nNow on Github: https:\/\/github.com\/milkbikis\/IDSearch.vim\r\n\r\nTo edit the previewed file in the same window, press Enter (<CR>). To go back to the original file, press H.\r\nTo open it in a new tab, press t.\r\nTo open silently in a new tab, press T.\r\n\r\nNote:\r\nThis is my first attempt at writing a vim script. I used NERDTree's source to learn how to do certain things. It's a fantastic plugin for file exploration and more.","4":"This is a plugin to use id-utils (http:\/\/www.gnu.org\/software\/idutils\/) gid command for quickly finding in files. This plugin searches for a given word and lists the results in a small window. As you move over the results, each file is shown in the preview window. \r\n\r\nNow on Github: https:\/\/github.com\/milkbikis\/IDSearch.vim\r\n\r\nTo edit the previewed file in the same window, press Enter (<CR>). To go back to the original file, press H.\r\nTo open it in a new tab, press t.\r\nTo open silently in a new tab, press T.\r\n\r\nNote:\r\nThis is my first attempt at writing a vim script. I used NERDTree's source to learn how to do certain things. It's a fantastic plugin for file exploration and more.","install_details":"Install id-utils and generate ID file for your project tree with mkid.\r\nMap the g:IDSearchCurrentWord() and g:IDSearchCustom() to suitable keys\r\neg:\r\n map <C-F> :call g:IDSearchCurrentWord()<CR>\r\n map <C-G> :call g:IDSearchCustom()<CR>\r\n\r\nThis will search for the word under the cursor when Ctrl-f is pressed and prompt you for the search word when Ctrl-g is pressed. The word can use * and ? wildcards (see id-utils manual for details).","5":"Install id-utils and generate ID file for your project tree with mkid.\r\nMap the g:IDSearchCurrentWord() and g:IDSearchCustom() to suitable keys\r\neg:\r\n map <C-F> :call g:IDSearchCurrentWord()<CR>\r\n map <C-G> :call g:IDSearchCustom()<CR>\r\n\r\nThis will search for the word under the cursor when Ctrl-f is pressed and prompt you for the search word when Ctrl-g is pressed. The word can use * and ? wildcards (see id-utils manual for details).","first_name":"Shrey","6":"Shrey","last_name":"Banga","7":"Banga","releases":[{"0":"3630","vim_version":"7.0","1":"7.0","script_version":"1.0.1","2":"1.0.1","version_comment":"- Mapping the 'h' key to show original file. This key can be changed by setting the g:IDSearch_KEY_show_original variable in your vimrc.","3":"- Mapping the 'h' key to show original file. This key can be changed by setting the g:IDSearch_KEY_show_original variable in your vimrc.","package":"IDsearch.vim","4":"IDsearch.vim","src_id":"15918","5":"15918","creation_date":"1308328445","6":"1308328445"},{"0":"3630","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"IDsearch.vim","4":"IDsearch.vim","src_id":"15913","5":"15913","creation_date":"1308316854","6":"1308316854"}]},"3629":{"script_id":"3629","0":"3629","script_name":"tangolight","1":"tangolight","script_type":"color scheme","2":"color scheme","summary":"lighter version of original tangoshady","3":"lighter version of original tangoshady","description":"This is a colorscheme using the lighter color paletter from gnome-terminal tango theme.\r\n\r\nIMPORTANT: THIS IS ONLY FOR GUI VIM","4":"This is a colorscheme using the lighter color paletter from gnome-terminal tango theme.\r\n\r\nIMPORTANT: THIS IS ONLY FOR GUI VIM","install_details":"","5":"","first_name":"vim","6":"vim","last_name":"pimps","7":"pimps","releases":[{"0":"3629","vim_version":"7.0","1":"7.0","script_version":"1.1","2":"1.1","version_comment":"fixed braces color","3":"fixed braces color","package":"tangolight.vim","4":"tangolight.vim","src_id":"15907","5":"15907","creation_date":"1308198652","6":"1308198652"},{"0":"3629","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"tangolight.vim","4":"tangolight.vim","src_id":"15906","5":"15906","creation_date":"1308197505","6":"1308197505"}]},"3628":{"script_id":"3628","0":"3628","script_name":"cpp_gnuchlog.vim","1":"cpp_gnuchlog.vim","script_type":"ftplugin","2":"ftplugin","summary":"cpp filetype plugin for gnuchangelog","3":"cpp filetype plugin for gnuchangelog","description":"This is an add-on to Luis Caamano's gnuchangelog (vimscript #1631) script package.  Note that gnuchangelog ''can be configured with filetype plugins so that one can use different tag searchers for different languages\" to provide the class\/method\/function name in ChangeLog entries.\r\n\r\ncpp_gnuchlog.vim is a filetype plugin for c++ that uses the GetTagName() function provided by Gary Johnson's ctags.vim (vimscript #610) script in order to provide the class\/method\/function name in the ChangeLog entry added by gnuchangelog.  It is a slight modification of the python_gnuchlog.vim filetype plugin provided by gnuchangelog.","4":"This is an add-on to Luis Caamano's gnuchangelog (vimscript #1631) script package.  Note that gnuchangelog ''can be configured with filetype plugins so that one can use different tag searchers for different languages\" to provide the class\/method\/function name in ChangeLog entries.\r\n\r\ncpp_gnuchlog.vim is a filetype plugin for c++ that uses the GetTagName() function provided by Gary Johnson's ctags.vim (vimscript #610) script in order to provide the class\/method\/function name in the ChangeLog entry added by gnuchangelog.  It is a slight modification of the python_gnuchlog.vim filetype plugin provided by gnuchangelog.","install_details":"1. Install gnuchangelog (vimscript #1631).  \r\n2. Install ctags.vim (vimscript #610).  \r\n3. Copy cpp_gnuchlog.vim to your ~\/.vim\/ftplugin directory.  ","5":"1. Install gnuchangelog (vimscript #1631).  \r\n2. Install ctags.vim (vimscript #610).  \r\n3. Copy cpp_gnuchlog.vim to your ~\/.vim\/ftplugin directory.  ","first_name":"Jeffrey","6":"Jeffrey","last_name":"Wildman","7":"Wildman","releases":[{"0":"3628","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"cpp_gnuchlog.vim","4":"cpp_gnuchlog.vim","src_id":"15904","5":"15904","creation_date":"1308176807","6":"1308176807"}]},"3627":{"script_id":"3627","0":"3627","script_name":"resizewin","1":"resizewin","script_type":"utility","2":"utility","summary":"mini util for temporary widen window horizontally\/vertically\/both","3":"mini util for temporary widen window horizontally\/vertically\/both","description":"What is this?\r\n==================================\r\nresizewin.vim is minimal utility for resize win\r\n\r\n  * horizontally\r\n  * vertically\r\n  * full(both horizontally and vertically)\r\n\r\nKeyMap Example\r\n================================\r\nset following keymap in your .vimrc.\r\nthen split, vsplit several time.\r\nthen try `_`, `|`(bar), `F`\r\n\r\n\t\tvmap _ <Plug>(ResizeH)\r\n\t\tvmap <bar> <Plug>(ResizeV)\r\n\t\tvmap F <Plug>(ResizeHV)\r\n\t\tnmap _ <Plug>(ResizeH)\r\n\t\tnmap <bar> <Plug>(ResizeV)\r\n\t\tnmap F <Plug>(ResizeHV)\r\n","4":"What is this?\r\n==================================\r\nresizewin.vim is minimal utility for resize win\r\n\r\n  * horizontally\r\n  * vertically\r\n  * full(both horizontally and vertically)\r\n\r\nKeyMap Example\r\n================================\r\nset following keymap in your .vimrc.\r\nthen split, vsplit several time.\r\nthen try `_`, `|`(bar), `F`\r\n\r\n\t\tvmap _ <Plug>(ResizeH)\r\n\t\tvmap <bar> <Plug>(ResizeV)\r\n\t\tvmap F <Plug>(ResizeHV)\r\n\t\tnmap _ <Plug>(ResizeH)\r\n\t\tnmap <bar> <Plug>(ResizeV)\r\n\t\tnmap F <Plug>(ResizeHV)\r\n","install_details":"unzip","5":"unzip","first_name":"t9","6":"t9","last_name":"md","7":"md","releases":[{"0":"3627","vim_version":"7.2","1":"7.2","script_version":"0.2","2":"0.2","version_comment":"Initial upload","3":"Initial upload","package":"resizewin-0.2.zip","4":"resizewin-0.2.zip","src_id":"15901","5":"15901","creation_date":"1308148923","6":"1308148923"}]},"3626":{"script_id":"3626","0":"3626","script_name":"AutoSaveSetting","1":"AutoSaveSetting","script_type":"utility","2":"utility","summary":"Persistent settings for gVim (Mac\/Linux\/Win)","3":"Persistent settings for gVim (Mac\/Linux\/Win)","description":"Auto-saving the gVim window's size and position from previous launch (including a maximized gVim in a multi-monitors setup) and makes all the settings in the gVim's menu stick. If you change your font, it'll stick. Change your colorscheme? it'll stick, too. Enable\/Disable the menu, toolbar and scrollbars? it'll stick.\r\n\r\nTested on standard installations of MacOSX, Ubuntu and Windows.\r\n\r\nOnly works with the GUI version of Vim. Can be made to work with terminal but it just makes more sense for the GUI version.\r\n\r\n================\r\n.vimrc options:\r\n================\r\n\r\n>>    let g:setting_restore = 1\r\nIf non-zero, AutoSaveSetting is enabled at startup. Enabled by default (1).\r\n\r\n>>    let g:setting_by_vim_instance = 1\r\nIf non-zero, save a different set of settings for each Vim instance. Enabled by default (1).\r\n\r\n>>    let g:setting_ignores_vimrc = 1\r\nIf non-zero, settings will persist after sourcing vimrc. Enabled by default (1).","4":"Auto-saving the gVim window's size and position from previous launch (including a maximized gVim in a multi-monitors setup) and makes all the settings in the gVim's menu stick. If you change your font, it'll stick. Change your colorscheme? it'll stick, too. Enable\/Disable the menu, toolbar and scrollbars? it'll stick.\r\n\r\nTested on standard installations of MacOSX, Ubuntu and Windows.\r\n\r\nOnly works with the GUI version of Vim. Can be made to work with terminal but it just makes more sense for the GUI version.\r\n\r\n================\r\n.vimrc options:\r\n================\r\n\r\n>>    let g:setting_restore = 1\r\nIf non-zero, AutoSaveSetting is enabled at startup. Enabled by default (1).\r\n\r\n>>    let g:setting_by_vim_instance = 1\r\nIf non-zero, save a different set of settings for each Vim instance. Enabled by default (1).\r\n\r\n>>    let g:setting_ignores_vimrc = 1\r\nIf non-zero, settings will persist after sourcing vimrc. Enabled by default (1).","install_details":"Extract the archive to ~\/.vim on Linux\/MacOSX or $HOME\\vimfiles on Windows","5":"Extract the archive to ~\/.vim on Linux\/MacOSX or $HOME\\vimfiles on Windows","first_name":" ","6":" ","last_name":" ","7":" ","releases":[{"0":"3626","vim_version":"7.3","1":"7.3","script_version":"1.2","2":"1.2","version_comment":"+ New vimrc option.\r\n+ Prevent losing data after sourcing vimrc.\r\n+ Support Vim Win64bit build.\r\n+ Some minor refactorings.","3":"+ New vimrc option.\r\n+ Prevent losing data after sourcing vimrc.\r\n+ Support Vim Win64bit build.\r\n+ Some minor refactorings.","package":"autosavesetting.zip","4":"autosavesetting.zip","src_id":"16303","5":"16303","creation_date":"1313832714","6":"1313832714"},{"0":"3626","vim_version":"7.3","1":"7.3","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"AutoSaveSetting.zip","4":"AutoSaveSetting.zip","src_id":"15896","5":"15896","creation_date":"1308106028","6":"1308106028"}]},"3625":{"script_id":"3625","0":"3625","script_name":"lua.vim","1":"lua.vim","script_type":"ftplugin","2":"ftplugin","summary":"Lua file type plug-in for the Vim text editor","3":"Lua file type plug-in for the Vim text editor","description":"The Lua file type plug-in for Vim makes it easier to work with Lua source code in Vim by providing the following features:\r\n\r\n \u00e2\u0080\u00a2 The 'includeexpr' option is set so that the gf (go to file) mapping knows how to resolve Lua module names using package.path\r\n \u00e2\u0080\u00a2 The 'include' option is set so that Vim follows dofile(), loadfile() and require() calls when looking for identifiers in included files (this works together with the 'includeexpr' option)\r\n \u00e2\u0080\u00a2 An automatic command is installed that runs \"luac -p\" when you save your Lua scripts. If luac reports any errors they are shown in the quick-fix list and Vim jumps to the line of the first error. If \"luac -p\" doesn\u00e2\u0080\u0099t report any errors a check for undefined global variables is performed by parsing the output of \"luac -p -l\"\r\n \u00e2\u0080\u00a2 <F1> on a Lua function or 'method' call will try to open the relevant documentation in the Lua Reference for Vim\r\n \u00e2\u0080\u00a2 The 'completefunc' option is set to allow completion of Lua 5.1 keywords, global variables and library members using Control-X Control-U\r\n \u00e2\u0080\u00a2 Several text-objects are defined so you can jump between blocks and functions\r\n \u00e2\u0080\u00a2 A pretty nifty hack of the matchit plug-in is included: When the cursor is on a function or return keyword the % mapping cycles between the relevant keywords (function, return, end), this also works for branching statements (if, elseif, else, end) and looping statements (for, while, repeat, until, end)\r\n\r\nFor more information about the plug-in please refer to its homepage or the project page on GitHub:\r\n\r\n \u00e2\u0080\u00a2 http:\/\/peterodding.com\/code\/vim\/lua-ftplugin\r\n \u00e2\u0080\u00a2 http:\/\/github.com\/xolox\/vim-lua-ftplugin\r\n\r\nIf you have questions, bug reports, suggestions, etc. the author can be contacted at peter@peterodding.com. If you like this plug-in please vote for it below!","4":"The Lua file type plug-in for Vim makes it easier to work with Lua source code in Vim by providing the following features:\r\n\r\n \u00e2\u0080\u00a2 The 'includeexpr' option is set so that the gf (go to file) mapping knows how to resolve Lua module names using package.path\r\n \u00e2\u0080\u00a2 The 'include' option is set so that Vim follows dofile(), loadfile() and require() calls when looking for identifiers in included files (this works together with the 'includeexpr' option)\r\n \u00e2\u0080\u00a2 An automatic command is installed that runs \"luac -p\" when you save your Lua scripts. If luac reports any errors they are shown in the quick-fix list and Vim jumps to the line of the first error. If \"luac -p\" doesn\u00e2\u0080\u0099t report any errors a check for undefined global variables is performed by parsing the output of \"luac -p -l\"\r\n \u00e2\u0080\u00a2 <F1> on a Lua function or 'method' call will try to open the relevant documentation in the Lua Reference for Vim\r\n \u00e2\u0080\u00a2 The 'completefunc' option is set to allow completion of Lua 5.1 keywords, global variables and library members using Control-X Control-U\r\n \u00e2\u0080\u00a2 Several text-objects are defined so you can jump between blocks and functions\r\n \u00e2\u0080\u00a2 A pretty nifty hack of the matchit plug-in is included: When the cursor is on a function or return keyword the % mapping cycles between the relevant keywords (function, return, end), this also works for branching statements (if, elseif, else, end) and looping statements (for, while, repeat, until, end)\r\n\r\nFor more information about the plug-in please refer to its homepage or the project page on GitHub:\r\n\r\n \u00e2\u0080\u00a2 http:\/\/peterodding.com\/code\/vim\/lua-ftplugin\r\n \u00e2\u0080\u00a2 http:\/\/github.com\/xolox\/vim-lua-ftplugin\r\n\r\nIf you have questions, bug reports, suggestions, etc. the author can be contacted at peter@peterodding.com. If you like this plug-in please vote for it below!","install_details":"Please note that the vim-lua-ftplugin plug-in requires my vim-misc plug-in which is separately distributed (see vimscript #4597). \r\n\r\nUnzip the most recent ZIP archives of the vim-lua-ftplugin and vim-misc plug-ins inside your Vim profile directory (usually this is ~\/.vim on UNIX and %USERPROFILE%\\vimfiles on Windows), restart Vim and execute the command :helptags ~\/.vim\/doc (use :helptags ~\\vimfiles\\doc instead on Windows).\r\n\r\nIf you prefer you can also use Pathogen, Vundle or a similar tool to install & update the vim-lua-ftplugin and vim-misc plug-ins using a local clone of the git repository.\r\n\r\nNow try it out: Edit a Lua script and try any of the features documented above.\r\n\r\nNote that on Windows a command prompt window pops up whenever Lua is run as an external process. If this bothers you then you can install my shell.vim plug-in (vimscript #3123) which includes a DLL that works around this issue. Once you\u00e2\u0080\u0099ve installed both plug-ins it should work out of the box!","5":"Please note that the vim-lua-ftplugin plug-in requires my vim-misc plug-in which is separately distributed (see vimscript #4597). \r\n\r\nUnzip the most recent ZIP archives of the vim-lua-ftplugin and vim-misc plug-ins inside your Vim profile directory (usually this is ~\/.vim on UNIX and %USERPROFILE%\\vimfiles on Windows), restart Vim and execute the command :helptags ~\/.vim\/doc (use :helptags ~\\vimfiles\\doc instead on Windows).\r\n\r\nIf you prefer you can also use Pathogen, Vundle or a similar tool to install & update the vim-lua-ftplugin and vim-misc plug-ins using a local clone of the git repository.\r\n\r\nNow try it out: Edit a Lua script and try any of the features documented above.\r\n\r\nNote that on Windows a command prompt window pops up whenever Lua is run as an external process. If this bothers you then you can install my shell.vim plug-in (vimscript #3123) which includes a DLL that works around this issue. Once you\u00e2\u0080\u0099ve installed both plug-ins it should work out of the box!","first_name":"Peter","6":"Peter","last_name":"Odding","7":"Odding","releases":[{"0":"3625","vim_version":"7.0","1":"7.0","script_version":"0.8","2":"0.8","version_comment":" \u00e2\u0080\u00a2 Make issues like #28 easier to debug:\n   http:\/\/github.com\/xolox\/vim-lua-ftplugin\/commit\/5527820\n\n \u00e2\u0080\u00a2 Update docs to refer to correct option lua_omni_blacklist:\n   http:\/\/github.com\/xolox\/vim-lua-ftplugin\/commit\/c9ee830\n\n \u00e2\u0080\u00a2 Provide option to inspect omni completion module loading list:\n   http:\/\/github.com\/xolox\/vim-lua-ftplugin\/commit\/2c69923\n\n \u00e2\u0080\u00a2 Update to Lua 5.2 keywords and standard libraries:\n   http:\/\/github.com\/xolox\/vim-lua-ftplugin\/commit\/50c7fc1","3":" \u00e2\u0080\u00a2 Make issues like #28 easier to debug:\n   http:\/\/github.com\/xolox\/vim-lua-ftplugin\/commit\/5527820\n\n \u00e2\u0080\u00a2 Update docs to refer to correct option lua_omni_blacklist:\n   http:\/\/github.com\/xolox\/vim-lua-ftplugin\/commit\/c9ee830\n\n \u00e2\u0080\u00a2 Provide option to inspect omni completion module loading list:\n   http:\/\/github.com\/xolox\/vim-lua-ftplugin\/commit\/2c69923\n\n \u00e2\u0080\u00a2 Update to Lua 5.2 keywords and standard libraries:\n   http:\/\/github.com\/xolox\/vim-lua-ftplugin\/commit\/50c7fc1","package":"lua-ftplugin.zip","4":"lua-ftplugin.zip","src_id":"22419","5":"22419","creation_date":"1410682763","6":"1410682763"},{"0":"3625","vim_version":"7.0","1":"7.0","script_version":"0.7.23","2":"0.7.23","version_comment":" \u00e2\u0080\u00a2 Make omni completion compatible with strict.lua (issue #27 on GitHub):\n   http:\/\/github.com\/xolox\/vim-lua-ftplugin\/commit\/e7d3ce7","3":" \u00e2\u0080\u00a2 Make omni completion compatible with strict.lua (issue #27 on GitHub):\n   http:\/\/github.com\/xolox\/vim-lua-ftplugin\/commit\/e7d3ce7","package":"lua-ftplugin.zip","4":"lua-ftplugin.zip","src_id":"22197","5":"22197","creation_date":"1405129897","6":"1405129897"},{"0":"3625","vim_version":"7.0","1":"7.0","script_version":"0.7.22","2":"0.7.22","version_comment":" \u00e2\u0080\u00a2 Add Lua 5.2 goto keyword to keyword completion candidates:\n   http:\/\/github.com\/xolox\/vim-lua-ftplugin\/commit\/5d55a11\n\n \u00e2\u0080\u00a2 Reliably fix userdata errors that have been bugging users for a while:\n   http:\/\/github.com\/xolox\/vim-lua-ftplugin\/commit\/4746f4d","3":" \u00e2\u0080\u00a2 Add Lua 5.2 goto keyword to keyword completion candidates:\n   http:\/\/github.com\/xolox\/vim-lua-ftplugin\/commit\/5d55a11\n\n \u00e2\u0080\u00a2 Reliably fix userdata errors that have been bugging users for a while:\n   http:\/\/github.com\/xolox\/vim-lua-ftplugin\/commit\/4746f4d","package":"lua-ftplugin.zip","4":"lua-ftplugin.zip","src_id":"22139","5":"22139","creation_date":"1404670255","6":"1404670255"},{"0":"3625","vim_version":"7.0","1":"7.0","script_version":"0.7.21","2":"0.7.21","version_comment":" \u00e2\u0080\u00a2 Map K for help lookup (in normal mode):\n   http:\/\/github.com\/xolox\/vim-lua-ftplugin\/commit\/e3e7ab4\n\n \u00e2\u0080\u00a2 Pull request #19: Map K for help lookup (in normal mode):\n   http:\/\/github.com\/xolox\/vim-lua-ftplugin\/commit\/090371f\n\n \u00e2\u0080\u00a2 Bug fix: Respect 'lua_interpreter_path' during search path discovery:\n   http:\/\/github.com\/xolox\/vim-lua-ftplugin\/commit\/aa7a642\n\n \u00e2\u0080\u00a2 Make it possible to disable use of Lua Interface for Vim:\n   http:\/\/github.com\/xolox\/vim-lua-ftplugin\/commit\/5d0ec87","3":" \u00e2\u0080\u00a2 Map K for help lookup (in normal mode):\n   http:\/\/github.com\/xolox\/vim-lua-ftplugin\/commit\/e3e7ab4\n\n \u00e2\u0080\u00a2 Pull request #19: Map K for help lookup (in normal mode):\n   http:\/\/github.com\/xolox\/vim-lua-ftplugin\/commit\/090371f\n\n \u00e2\u0080\u00a2 Bug fix: Respect 'lua_interpreter_path' during search path discovery:\n   http:\/\/github.com\/xolox\/vim-lua-ftplugin\/commit\/aa7a642\n\n \u00e2\u0080\u00a2 Make it possible to disable use of Lua Interface for Vim:\n   http:\/\/github.com\/xolox\/vim-lua-ftplugin\/commit\/5d0ec87","package":"lua-ftplugin.zip","4":"lua-ftplugin.zip","src_id":"22045","5":"22045","creation_date":"1403029769","6":"1403029769"},{"0":"3625","vim_version":"7.0","1":"7.0","script_version":"0.7.19","2":"0.7.19","version_comment":" \u00e2\u0080\u00a2 Pull request #21: Allow module blacklisting in omni completion:\n   http:\/\/github.com\/xolox\/vim-lua-ftplugin\/commit\/d85872c","3":" \u00e2\u0080\u00a2 Pull request #21: Allow module blacklisting in omni completion:\n   http:\/\/github.com\/xolox\/vim-lua-ftplugin\/commit\/d85872c","package":"lua-ftplugin.zip","4":"lua-ftplugin.zip","src_id":"22040","5":"22040","creation_date":"1402956399","6":"1402956399"},{"0":"3625","vim_version":"7.0","1":"7.0","script_version":"0.7.18","2":"0.7.18","version_comment":" \u00e2\u0080\u00a2 Use configured Lua compiler in globals.lua (reported in pull request #23):\n   http:\/\/github.com\/xolox\/vim-lua-ftplugin\/commit\/96082b7","3":" \u00e2\u0080\u00a2 Use configured Lua compiler in globals.lua (reported in pull request #23):\n   http:\/\/github.com\/xolox\/vim-lua-ftplugin\/commit\/96082b7","package":"lua-ftplugin.zip","4":"lua-ftplugin.zip","src_id":"22037","5":"22037","creation_date":"1402953941","6":"1402953941"},{"0":"3625","vim_version":"7.0","1":"7.0","script_version":"0.7.17","2":"0.7.17","version_comment":" \u00e2\u0080\u00a2 Document the global :LuaCheckSyntax and :LuaCheckGlobals commands:\n   http:\/\/github.com\/xolox\/vim-lua-ftplugin\/commit\/624ee70\n\n \u00e2\u0080\u00a2 Make name\/path of Lua interpreter configurable:\n   http:\/\/github.com\/xolox\/vim-lua-ftplugin\/commit\/47123ba\n\n \u00e2\u0080\u00a2 Add parentheses to functions in overview of known globals:\n   http:\/\/github.com\/xolox\/vim-lua-ftplugin\/commit\/7f4bbd9\n\n \u00e2\u0080\u00a2 Improve interaction between automatic syntax\/globals checks:\n   http:\/\/github.com\/xolox\/vim-lua-ftplugin\/commit\/1d7aaec\n\n \u00e2\u0080\u00a2 Try to resolve pull request #23 (workaround for table indexes in globals.lua):\n   http:\/\/github.com\/xolox\/vim-lua-ftplugin\/commit\/9160dee","3":" \u00e2\u0080\u00a2 Document the global :LuaCheckSyntax and :LuaCheckGlobals commands:\n   http:\/\/github.com\/xolox\/vim-lua-ftplugin\/commit\/624ee70\n\n \u00e2\u0080\u00a2 Make name\/path of Lua interpreter configurable:\n   http:\/\/github.com\/xolox\/vim-lua-ftplugin\/commit\/47123ba\n\n \u00e2\u0080\u00a2 Add parentheses to functions in overview of known globals:\n   http:\/\/github.com\/xolox\/vim-lua-ftplugin\/commit\/7f4bbd9\n\n \u00e2\u0080\u00a2 Improve interaction between automatic syntax\/globals checks:\n   http:\/\/github.com\/xolox\/vim-lua-ftplugin\/commit\/1d7aaec\n\n \u00e2\u0080\u00a2 Try to resolve pull request #23 (workaround for table indexes in globals.lua):\n   http:\/\/github.com\/xolox\/vim-lua-ftplugin\/commit\/9160dee","package":"lua-ftplugin.zip","4":"lua-ftplugin.zip","src_id":"22036","5":"22036","creation_date":"1402953565","6":"1402953565"},{"0":"3625","vim_version":"7.0","1":"7.0","script_version":"0.7.13","2":"0.7.13","version_comment":" \u00e2\u0080\u00a2 Make setting of completefunc\/omnifunc optional:\n   http:\/\/github.com\/xolox\/vim-lua-ftplugin\/commit\/17e9003","3":" \u00e2\u0080\u00a2 Make setting of completefunc\/omnifunc optional:\n   http:\/\/github.com\/xolox\/vim-lua-ftplugin\/commit\/17e9003","package":"lua-ftplugin.zip","4":"lua-ftplugin.zip","src_id":"20738","5":"20738","creation_date":"1377955136","6":"1377955136"},{"0":"3625","vim_version":"7.0","1":"7.0","script_version":"0.7.12","2":"0.7.12","version_comment":" \u00e2\u0080\u00a2 Always include standard library modules in module name completion:\n   http:\/\/github.com\/xolox\/vim-lua-ftplugin\/commit\/5157b16\n\n \u00e2\u0080\u00a2 Make sure vim-misc is installed, politely complain if it isn't:\n   http:\/\/github.com\/xolox\/vim-lua-ftplugin\/commit\/73736ad","3":" \u00e2\u0080\u00a2 Always include standard library modules in module name completion:\n   http:\/\/github.com\/xolox\/vim-lua-ftplugin\/commit\/5157b16\n\n \u00e2\u0080\u00a2 Make sure vim-misc is installed, politely complain if it isn't:\n   http:\/\/github.com\/xolox\/vim-lua-ftplugin\/commit\/73736ad","package":"lua-ftplugin.zip","4":"lua-ftplugin.zip","src_id":"20681","5":"20681","creation_date":"1376931720","6":"1376931720"},{"0":"3625","vim_version":"7.0","1":"7.0","script_version":"0.7.10","2":"0.7.10","version_comment":" \u00e2\u0080\u00a2 Document vim-misc as external dependency (needs to be installed separately from now on):\n   http:\/\/github.com\/xolox\/vim-lua-ftplugin\/commit\/a959a1b","3":" \u00e2\u0080\u00a2 Document vim-misc as external dependency (needs to be installed separately from now on):\n   http:\/\/github.com\/xolox\/vim-lua-ftplugin\/commit\/a959a1b","package":"lua-ftplugin.zip","4":"lua-ftplugin.zip","src_id":"20214","5":"20214","creation_date":"1369508575","6":"1369508575"},{"0":"3625","vim_version":"7.0","1":"7.0","script_version":"0.7.8","2":"0.7.8","version_comment":" \u00e2\u0080\u00a2 Updated miscellaneous scripts:\n   http:\/\/github.com\/xolox\/vim-lua-ftplugin\/commit\/3e26c8a","3":" \u00e2\u0080\u00a2 Updated miscellaneous scripts:\n   http:\/\/github.com\/xolox\/vim-lua-ftplugin\/commit\/3e26c8a","package":"lua-ftplugin.zip","4":"lua-ftplugin.zip","src_id":"20178","5":"20178","creation_date":"1369054103","6":"1369054103"},{"0":"3625","vim_version":"7.0","1":"7.0","script_version":"0.7.7","2":"0.7.7","version_comment":" \u00e2\u0080\u00a2 Updated miscellaneous scripts:\n   http:\/\/github.com\/xolox\/vim-lua-ftplugin\/commit\/f7399b9","3":" \u00e2\u0080\u00a2 Updated miscellaneous scripts:\n   http:\/\/github.com\/xolox\/vim-lua-ftplugin\/commit\/f7399b9","package":"lua-ftplugin.zip","4":"lua-ftplugin.zip","src_id":"20166","5":"20166","creation_date":"1369002977","6":"1369002977"},{"0":"3625","vim_version":"7.0","1":"7.0","script_version":"0.7.6","2":"0.7.6","version_comment":" \u00e2\u0080\u00a2 Option lua_define_completion_mappings (suggested by Daniel Fort):\n   http:\/\/github.com\/xolox\/vim-lua-ftplugin\/commit\/0544e6f","3":" \u00e2\u0080\u00a2 Option lua_define_completion_mappings (suggested by Daniel Fort):\n   http:\/\/github.com\/xolox\/vim-lua-ftplugin\/commit\/0544e6f","package":"lua-ftplugin.zip","4":"lua-ftplugin.zip","src_id":"20143","5":"20143","creation_date":"1368640417","6":"1368640417"},{"0":"3625","vim_version":"7.0","1":"7.0","script_version":"0.7.5","2":"0.7.5","version_comment":" \u00e2\u0080\u00a2 Updated miscellaneous scripts:\n   http:\/\/github.com\/xolox\/vim-lua-ftplugin\/commit\/6e0c4b7\n   http:\/\/github.com\/xolox\/vim-lua-ftplugin\/commit\/9c88b0e","3":" \u00e2\u0080\u00a2 Updated miscellaneous scripts:\n   http:\/\/github.com\/xolox\/vim-lua-ftplugin\/commit\/6e0c4b7\n   http:\/\/github.com\/xolox\/vim-lua-ftplugin\/commit\/9c88b0e","package":"lua-ftplugin.zip","4":"lua-ftplugin.zip","src_id":"20120","5":"20120","creation_date":"1368480991","6":"1368480991"},{"0":"3625","vim_version":"7.0","1":"7.0","script_version":"0.7.4","2":"0.7.4","version_comment":" \u00e2\u0080\u00a2 Make omni completion compatible with the latest Lua Interface for Vim (contributed by Daniel Fort):\n   http:\/\/github.com\/xolox\/vim-lua-ftplugin\/commit\/6caa0da\n   http:\/\/github.com\/xolox\/vim-lua-ftplugin\/commit\/2f29afe\n\n \u00e2\u0080\u00a2 Bug fix: Properly escape Vim script strings in omnicomplete.lua:\n   http:\/\/github.com\/xolox\/vim-lua-ftplugin\/commit\/b4f29a5","3":" \u00e2\u0080\u00a2 Make omni completion compatible with the latest Lua Interface for Vim (contributed by Daniel Fort):\n   http:\/\/github.com\/xolox\/vim-lua-ftplugin\/commit\/6caa0da\n   http:\/\/github.com\/xolox\/vim-lua-ftplugin\/commit\/2f29afe\n\n \u00e2\u0080\u00a2 Bug fix: Properly escape Vim script strings in omnicomplete.lua:\n   http:\/\/github.com\/xolox\/vim-lua-ftplugin\/commit\/b4f29a5","package":"lua-ftplugin.zip","4":"lua-ftplugin.zip","src_id":"20098","5":"20098","creation_date":"1368355378","6":"1368355378"},{"0":"3625","vim_version":"7.0","1":"7.0","script_version":"0.7.3","2":"0.7.3","version_comment":" \u00e2\u0080\u00a2 Updated miscellaneous scripts:\n   http:\/\/github.com\/xolox\/vim-lua-ftplugin\/commit\/d956287","3":" \u00e2\u0080\u00a2 Updated miscellaneous scripts:\n   http:\/\/github.com\/xolox\/vim-lua-ftplugin\/commit\/d956287","package":"lua-ftplugin.zip","4":"lua-ftplugin.zip","src_id":"20003","5":"20003","creation_date":"1367484666","6":"1367484666"},{"0":"3625","vim_version":"7.0","1":"7.0","script_version":"0.7.2","2":"0.7.2","version_comment":" \u00e2\u0080\u00a2 Updated miscellaneous scripts:\n   http:\/\/github.com\/xolox\/vim-lua-ftplugin\/commit\/5c60686","3":" \u00e2\u0080\u00a2 Updated miscellaneous scripts:\n   http:\/\/github.com\/xolox\/vim-lua-ftplugin\/commit\/5c60686","package":"lua-ftplugin.zip","4":"lua-ftplugin.zip","src_id":"19963","5":"19963","creation_date":"1367160137","6":"1367160137"},{"0":"3625","vim_version":"7.0","1":"7.0","script_version":"0.7.1","2":"0.7.1","version_comment":" \u00e2\u0080\u00a2 Remove old documentation (sorry about that):\n   http:\/\/github.com\/xolox\/vim-lua-ftplugin\/commit\/46466bb\n\n \u00e2\u0080\u00a2 Make compatibility with miscellaneous scripts explicit:\n   http:\/\/github.com\/xolox\/vim-lua-ftplugin\/commit\/fbeb973","3":" \u00e2\u0080\u00a2 Remove old documentation (sorry about that):\n   http:\/\/github.com\/xolox\/vim-lua-ftplugin\/commit\/46466bb\n\n \u00e2\u0080\u00a2 Make compatibility with miscellaneous scripts explicit:\n   http:\/\/github.com\/xolox\/vim-lua-ftplugin\/commit\/fbeb973","package":"lua-ftplugin.zip","4":"lua-ftplugin.zip","src_id":"19869","5":"19869","creation_date":"1366484806","6":"1366484806"},{"0":"3625","vim_version":"7.0","1":"7.0","script_version":"0.7","2":"0.7","version_comment":" \u00e2\u0080\u00a2 Bug fix for omnicomplete.lua: Strip newlines from generated output:\n   http:\/\/github.com\/xolox\/vim-lua-ftplugin\/commit\/b14088c\n\n \u00e2\u0080\u00a2 Use shell.vim plug-in to execute Lua subprocesses (issue #2 on GitHub):\n   http:\/\/github.com\/xolox\/vim-lua-ftplugin\/commit\/9b4c774\n   http:\/\/github.com\/xolox\/vim-lua-ftplugin\/commit\/0814a1b\n   http:\/\/github.com\/xolox\/vim-lua-ftplugin\/commit\/bccf110","3":" \u00e2\u0080\u00a2 Bug fix for omnicomplete.lua: Strip newlines from generated output:\n   http:\/\/github.com\/xolox\/vim-lua-ftplugin\/commit\/b14088c\n\n \u00e2\u0080\u00a2 Use shell.vim plug-in to execute Lua subprocesses (issue #2 on GitHub):\n   http:\/\/github.com\/xolox\/vim-lua-ftplugin\/commit\/9b4c774\n   http:\/\/github.com\/xolox\/vim-lua-ftplugin\/commit\/0814a1b\n   http:\/\/github.com\/xolox\/vim-lua-ftplugin\/commit\/bccf110","package":"lua-ftplugin.zip","4":"lua-ftplugin.zip","src_id":"16959","5":"16959","creation_date":"1322179317","6":"1322179317"},{"0":"3625","vim_version":"7.0","1":"7.0","script_version":"0.6.28","2":"0.6.28","version_comment":" \u00e2\u0080\u00a2 Work around &shellslash setting on Windows:\n   http:\/\/github.com\/xolox\/vim-lua-ftplugin\/commit\/8e1812a","3":" \u00e2\u0080\u00a2 Work around &shellslash setting on Windows:\n   http:\/\/github.com\/xolox\/vim-lua-ftplugin\/commit\/8e1812a","package":"lua-ftplugin.zip","4":"lua-ftplugin.zip","src_id":"16922","5":"16922","creation_date":"1321908532","6":"1321908532"},{"0":"3625","vim_version":"7.0","1":"7.0","script_version":"0.6.27","2":"0.6.27","version_comment":" \u00e2\u0080\u00a2 Bug fix for dynamic completion after typing require(':\n   http:\/\/github.com\/xolox\/vim-lua-ftplugin\/commit\/3e3d3dc\n\n \u00e2\u0080\u00a2 Make dofile(), loadfile(), ... trigger filename completion:\n   http:\/\/github.com\/xolox\/vim-lua-ftplugin\/commit\/8cff1bd","3":" \u00e2\u0080\u00a2 Bug fix for dynamic completion after typing require(':\n   http:\/\/github.com\/xolox\/vim-lua-ftplugin\/commit\/3e3d3dc\n\n \u00e2\u0080\u00a2 Make dofile(), loadfile(), ... trigger filename completion:\n   http:\/\/github.com\/xolox\/vim-lua-ftplugin\/commit\/8cff1bd","package":"lua-ftplugin.zip","4":"lua-ftplugin.zip","src_id":"16873","5":"16873","creation_date":"1321388728","6":"1321388728"},{"0":"3625","vim_version":"7.0","1":"7.0","script_version":"0.6.25","2":"0.6.25","version_comment":" \u00e2\u0080\u00a2 Bug fix: Don't perform automatic completion in strings\/comments:\n   http:\/\/github.com\/xolox\/vim-lua-ftplugin\/commit\/5cf57e0","3":" \u00e2\u0080\u00a2 Bug fix: Don't perform automatic completion in strings\/comments:\n   http:\/\/github.com\/xolox\/vim-lua-ftplugin\/commit\/5cf57e0","package":"lua-ftplugin.zip","4":"lua-ftplugin.zip","src_id":"16731","5":"16731","creation_date":"1319406774","6":"1319406774"},{"0":"3625","vim_version":"7.0","1":"7.0","script_version":"0.6.24","2":"0.6.24","version_comment":" \u00e2\u0080\u00a2 Support Lua modules that don't create a global (omni completion):\n   http:\/\/github.com\/xolox\/vim-lua-ftplugin\/commit\/3c49c27","3":" \u00e2\u0080\u00a2 Support Lua modules that don't create a global (omni completion):\n   http:\/\/github.com\/xolox\/vim-lua-ftplugin\/commit\/3c49c27","package":"lua-ftplugin.zip","4":"lua-ftplugin.zip","src_id":"16681","5":"16681","creation_date":"1318786721","6":"1318786721"},{"0":"3625","vim_version":"7.0","1":"7.0","script_version":"0.6.23","2":"0.6.23","version_comment":" \u00e2\u0080\u00a2 Updated miscellaneous scripts:\n   http:\/\/github.com\/xolox\/vim-lua-ftplugin\/commit\/50a844e","3":" \u00e2\u0080\u00a2 Updated miscellaneous scripts:\n   http:\/\/github.com\/xolox\/vim-lua-ftplugin\/commit\/50a844e","package":"lua-ftplugin.zip","4":"lua-ftplugin.zip","src_id":"16578","5":"16578","creation_date":"1316994618","6":"1316994618"},{"0":"3625","vim_version":"7.0","1":"7.0","script_version":"0.6.22","2":"0.6.22","version_comment":" \u00e2\u0080\u00a2 Updated miscellaneous scripts:\n   http:\/\/github.com\/xolox\/vim-lua-ftplugin\/commit\/048c493","3":" \u00e2\u0080\u00a2 Updated miscellaneous scripts:\n   http:\/\/github.com\/xolox\/vim-lua-ftplugin\/commit\/048c493","package":"lua-ftplugin.zip","4":"lua-ftplugin.zip","src_id":"16456","5":"16456","creation_date":"1315144910","6":"1315144910"},{"0":"3625","vim_version":"7.0","1":"7.0","script_version":"0.6.21","2":"0.6.21","version_comment":" \u00e2\u0080\u00a2 Option handling with xolox#misc#option#get({name}, {default}) (this one took me some time to get right..):\n   http:\/\/github.com\/xolox\/vim-lua-ftplugin\/commit\/e228b0e\n   http:\/\/github.com\/xolox\/vim-lua-ftplugin\/commit\/0b1c06e\n   http:\/\/github.com\/xolox\/vim-lua-ftplugin\/commit\/dc8a937\n   http:\/\/github.com\/xolox\/vim-lua-ftplugin\/commit\/05d45ea\n\n \u00e2\u0080\u00a2 Minor refactoring of omnicomplete.lua:\n   http:\/\/github.com\/xolox\/vim-lua-ftplugin\/commit\/5bb59a2\n\n \u00e2\u0080\u00a2 Move version variable to autoload script:\n   http:\/\/github.com\/xolox\/vim-lua-ftplugin\/commit\/b01ff5e","3":" \u00e2\u0080\u00a2 Option handling with xolox#misc#option#get({name}, {default}) (this one took me some time to get right..):\n   http:\/\/github.com\/xolox\/vim-lua-ftplugin\/commit\/e228b0e\n   http:\/\/github.com\/xolox\/vim-lua-ftplugin\/commit\/0b1c06e\n   http:\/\/github.com\/xolox\/vim-lua-ftplugin\/commit\/dc8a937\n   http:\/\/github.com\/xolox\/vim-lua-ftplugin\/commit\/05d45ea\n\n \u00e2\u0080\u00a2 Minor refactoring of omnicomplete.lua:\n   http:\/\/github.com\/xolox\/vim-lua-ftplugin\/commit\/5bb59a2\n\n \u00e2\u0080\u00a2 Move version variable to autoload script:\n   http:\/\/github.com\/xolox\/vim-lua-ftplugin\/commit\/b01ff5e","package":"lua-ftplugin.zip","4":"lua-ftplugin.zip","src_id":"16378","5":"16378","creation_date":"1314497928","6":"1314497928"},{"0":"3625","vim_version":"7.0","1":"7.0","script_version":"0.6.17","2":"0.6.17","version_comment":" \u00e2\u0080\u00a2 Completion bug fix: Off by one in prefix selection:\n   http:\/\/github.com\/xolox\/vim-lua-ftplugin\/commit\/865c32f","3":" \u00e2\u0080\u00a2 Completion bug fix: Off by one in prefix selection:\n   http:\/\/github.com\/xolox\/vim-lua-ftplugin\/commit\/865c32f","package":"lua-ftplugin.zip","4":"lua-ftplugin.zip","src_id":"15929","5":"15929","creation_date":"1308385040","6":"1308385040"},{"0":"3625","vim_version":"7.0","1":"7.0","script_version":"0.6.16","2":"0.6.16","version_comment":" \u00e2\u0080\u00a2 Delete old Vim help files (never even noticed them :-S):\n   http:\/\/github.com\/xolox\/vim-lua-ftplugin\/commit\/5d0ad12","3":" \u00e2\u0080\u00a2 Delete old Vim help files (never even noticed them :-S):\n   http:\/\/github.com\/xolox\/vim-lua-ftplugin\/commit\/5d0ad12","package":"lua-ftplugin.zip","4":"lua-ftplugin.zip","src_id":"15928","5":"15928","creation_date":"1308375162","6":"1308375162"},{"0":"3625","vim_version":"7.0","1":"7.0","script_version":"0.6.15","2":"0.6.15","version_comment":" \u00e2\u0080\u00a2 F1: Fall back to Lua reference for Vim if it exists, :help otherwise:\n   http:\/\/github.com\/xolox\/vim-lua-ftplugin\/commit\/feecf0d\n\n \u00e2\u0080\u00a2 Disable automatic checking of global variables (for now):\n   http:\/\/github.com\/xolox\/vim-lua-ftplugin\/commit\/e15b7be\n\n \u00e2\u0080\u00a2 Define version as variable, include version in messages:\n   http:\/\/github.com\/xolox\/vim-lua-ftplugin\/commit\/5e40f1c\n\n \u00e2\u0080\u00a2 Enable overriding of compiler arguments:\n   http:\/\/github.com\/xolox\/vim-lua-ftplugin\/commit\/3c1ca42\n\n \u00e2\u0080\u00a2 Set quick-fix window title after syntax check:\n   http:\/\/github.com\/xolox\/vim-lua-ftplugin\/commit\/b5ea380\n\n \u00e2\u0080\u00a2 Make completion use prefix matching instead of substring matching:\n   http:\/\/github.com\/xolox\/vim-lua-ftplugin\/commit\/14d9067\n\n \u00e2\u0080\u00a2 Improve omni completion, add plugin\/ script for autocmds:\n   http:\/\/github.com\/xolox\/vim-lua-ftplugin\/commit\/63641c8","3":" \u00e2\u0080\u00a2 F1: Fall back to Lua reference for Vim if it exists, :help otherwise:\n   http:\/\/github.com\/xolox\/vim-lua-ftplugin\/commit\/feecf0d\n\n \u00e2\u0080\u00a2 Disable automatic checking of global variables (for now):\n   http:\/\/github.com\/xolox\/vim-lua-ftplugin\/commit\/e15b7be\n\n \u00e2\u0080\u00a2 Define version as variable, include version in messages:\n   http:\/\/github.com\/xolox\/vim-lua-ftplugin\/commit\/5e40f1c\n\n \u00e2\u0080\u00a2 Enable overriding of compiler arguments:\n   http:\/\/github.com\/xolox\/vim-lua-ftplugin\/commit\/3c1ca42\n\n \u00e2\u0080\u00a2 Set quick-fix window title after syntax check:\n   http:\/\/github.com\/xolox\/vim-lua-ftplugin\/commit\/b5ea380\n\n \u00e2\u0080\u00a2 Make completion use prefix matching instead of substring matching:\n   http:\/\/github.com\/xolox\/vim-lua-ftplugin\/commit\/14d9067\n\n \u00e2\u0080\u00a2 Improve omni completion, add plugin\/ script for autocmds:\n   http:\/\/github.com\/xolox\/vim-lua-ftplugin\/commit\/63641c8","package":"lua-ftplugin.zip","4":"lua-ftplugin.zip","src_id":"15927","5":"15927","creation_date":"1308374960","6":"1308374960"},{"0":"3625","vim_version":"7.0","1":"7.0","script_version":"0.6.8","2":"0.6.8","version_comment":" \u00e2\u0080\u00a2 Add signatures of LuaSocket functions:\n   http:\/\/github.com\/xolox\/vim-lua-ftplugin\/commit\/972cac7","3":" \u00e2\u0080\u00a2 Add signatures of LuaSocket functions:\n   http:\/\/github.com\/xolox\/vim-lua-ftplugin\/commit\/972cac7","package":"lua.zip","4":"lua.zip","src_id":"15895","5":"15895","creation_date":"1308102527","6":"1308102527"},{"0":"3625","vim_version":"7.0","1":"7.0","script_version":"0.6.7","2":"0.6.7","version_comment":" \u00e2\u0080\u00a2 Check for undefined global variables (automatically):\n   http:\/\/github.com\/xolox\/vim-lua-ftplugin\/commit\/5466b62","3":" \u00e2\u0080\u00a2 Check for undefined global variables (automatically):\n   http:\/\/github.com\/xolox\/vim-lua-ftplugin\/commit\/5466b62","package":"lua.zip","4":"lua.zip","src_id":"15894","5":"15894","creation_date":"1308095880","6":"1308095880"},{"0":"3625","vim_version":"7.0","1":"7.0","script_version":"0.6.6","2":"0.6.6","version_comment":" \u00e2\u0080\u00a2 Move static user completion data to separate auto-load script:\n   http:\/\/github.com\/xolox\/vim-lua-ftplugin\/commit\/3aafd93\n\n \u00e2\u0080\u00a2 Several bug fixes and support for function signatures:\n   http:\/\/github.com\/xolox\/vim-lua-ftplugin\/commit\/79a5476\n\n \u00e2\u0080\u00a2 Highlight syntax errors to make them stand out:\n   http:\/\/github.com\/xolox\/vim-lua-ftplugin\/commit\/9e42b06\n\n \u00e2\u0080\u00a2 Improve omni completion: support for keywords, less clutter:\n   http:\/\/github.com\/xolox\/vim-lua-ftplugin\/commit\/bfd5701","3":" \u00e2\u0080\u00a2 Move static user completion data to separate auto-load script:\n   http:\/\/github.com\/xolox\/vim-lua-ftplugin\/commit\/3aafd93\n\n \u00e2\u0080\u00a2 Several bug fixes and support for function signatures:\n   http:\/\/github.com\/xolox\/vim-lua-ftplugin\/commit\/79a5476\n\n \u00e2\u0080\u00a2 Highlight syntax errors to make them stand out:\n   http:\/\/github.com\/xolox\/vim-lua-ftplugin\/commit\/9e42b06\n\n \u00e2\u0080\u00a2 Improve omni completion: support for keywords, less clutter:\n   http:\/\/github.com\/xolox\/vim-lua-ftplugin\/commit\/bfd5701","package":"lua.zip","4":"lua.zip","src_id":"15893","5":"15893","creation_date":"1308087953","6":"1308087953"},{"0":"3625","vim_version":"7.0","1":"7.0","script_version":"0.6.2","2":"0.6.2","version_comment":" \u00e2\u0080\u00a2 Completion of module names after typing require(':\n   http:\/\/github.com\/xolox\/vim-lua-ftplugin\/commit\/ffaf36b","3":" \u00e2\u0080\u00a2 Completion of module names after typing require(':\n   http:\/\/github.com\/xolox\/vim-lua-ftplugin\/commit\/ffaf36b","package":"lua.zip","4":"lua.zip","src_id":"15891","5":"15891","creation_date":"1308067966","6":"1308067966"},{"0":"3625","vim_version":"7.0","1":"7.0","script_version":"0.6.1","2":"0.6.1","version_comment":" \u00e2\u0080\u00a2 Refactor search path handling, use Lua Interface for Vim when available:\n   http:\/\/github.com\/xolox\/vim-lua-ftplugin\/commit\/6d68f3d","3":" \u00e2\u0080\u00a2 Refactor search path handling, use Lua Interface for Vim when available:\n   http:\/\/github.com\/xolox\/vim-lua-ftplugin\/commit\/6d68f3d","package":"lua.zip","4":"lua.zip","src_id":"15887","5":"15887","creation_date":"1308064502","6":"1308064502"},{"0":"3625","vim_version":"7.0","1":"7.0","script_version":"0.6","2":"0.6","version_comment":" \u00e2\u0080\u00a2 Link to release on vim.org, support automatic update using GLVS plug-in:\n   http:\/\/github.com\/xolox\/vim-lua-ftplugin\/commit\/9d68e7b\n\n \u00e2\u0080\u00a2 Support for omni completion by searching package.path and package.cpath:\n   http:\/\/github.com\/xolox\/vim-lua-ftplugin\/commit\/6ee6a69","3":" \u00e2\u0080\u00a2 Link to release on vim.org, support automatic update using GLVS plug-in:\n   http:\/\/github.com\/xolox\/vim-lua-ftplugin\/commit\/9d68e7b\n\n \u00e2\u0080\u00a2 Support for omni completion by searching package.path and package.cpath:\n   http:\/\/github.com\/xolox\/vim-lua-ftplugin\/commit\/6ee6a69","package":"lua.zip","4":"lua.zip","src_id":"15885","5":"15885","creation_date":"1308059997","6":"1308059997"},{"0":"3625","vim_version":"7.0","1":"7.0","script_version":"0.5.6","2":"0.5.6","version_comment":"Initial upload","3":"Initial upload","package":"lua.zip","4":"lua.zip","src_id":"15882","5":"15882","creation_date":"1308050616","6":"1308050616"}]},"3624":{"script_id":"3624","0":"3624","script_name":"indsas","1":"indsas","script_type":"utility","2":"utility","summary":"Indentation for SAS scripts","3":"Indentation for SAS scripts","description":"A Perl script to indent a lousily indented or indentless SAS script. \r\n\r\nExample:\r\nindsas xxx.sas\r\nor\r\nindsas xxx.sas > new_xxx.sas\r\n\r\n\r\nIt can be invoked in VIM by adding a line to .vimrc file.\r\nset ep=your_path_to_indsas\/indsas\r\n\r\nWhile you are editing a file with VIM, type this to indent the whole file\r\ngg=G\r\n\r\nif you want to go back to the current position after indenting, add this to your .vimrc\r\nnmap gW magg=G'a\r\nand you can type gW to indent the whole file at any position of the file.\r\n\r\n\r\nNOTE:\r\n1) indsas assumes the following SAS scripting(indenting) styles for input and merge statements:\r\n\r\n==INPUT===\r\ndata a1;\r\n    infile 'xxxx.txt';\r\n    input\r\n         var1 $\r\n         var2 $\r\n         .......\r\n    ;\r\nrun;\r\n\r\n==MERGE===\r\ndata new;\r\n       merge\r\n            dat1(in=a)\r\n            dat2(in=b)\r\n       ;\r\nrun;\r\n\r\n2) indsas also assumes the following scripting style:\r\n   *PROC and DATA statements are always accompanied with RUN;\r\n   *DO,IF xxx THEN DO and ELSE DO should be closed by END;\r\n   *PROC SQL should be closed by QUIT;\r\n\r\n3) This script is still very primitive and does not account for all other eccentric scripting styles.\r\n\r\n4) indsas does not handle \"cards\" or \"datalines\" correctly. Please manually adjust those lines.\r\n\r\n5) indsas was only tested in the unix\/linux environment.\r\n\r\n\r\n \r\n\t\r\n ","4":"A Perl script to indent a lousily indented or indentless SAS script. \r\n\r\nExample:\r\nindsas xxx.sas\r\nor\r\nindsas xxx.sas > new_xxx.sas\r\n\r\n\r\nIt can be invoked in VIM by adding a line to .vimrc file.\r\nset ep=your_path_to_indsas\/indsas\r\n\r\nWhile you are editing a file with VIM, type this to indent the whole file\r\ngg=G\r\n\r\nif you want to go back to the current position after indenting, add this to your .vimrc\r\nnmap gW magg=G'a\r\nand you can type gW to indent the whole file at any position of the file.\r\n\r\n\r\nNOTE:\r\n1) indsas assumes the following SAS scripting(indenting) styles for input and merge statements:\r\n\r\n==INPUT===\r\ndata a1;\r\n    infile 'xxxx.txt';\r\n    input\r\n         var1 $\r\n         var2 $\r\n         .......\r\n    ;\r\nrun;\r\n\r\n==MERGE===\r\ndata new;\r\n       merge\r\n            dat1(in=a)\r\n            dat2(in=b)\r\n       ;\r\nrun;\r\n\r\n2) indsas also assumes the following scripting style:\r\n   *PROC and DATA statements are always accompanied with RUN;\r\n   *DO,IF xxx THEN DO and ELSE DO should be closed by END;\r\n   *PROC SQL should be closed by QUIT;\r\n\r\n3) This script is still very primitive and does not account for all other eccentric scripting styles.\r\n\r\n4) indsas does not handle \"cards\" or \"datalines\" correctly. Please manually adjust those lines.\r\n\r\n5) indsas was only tested in the unix\/linux environment.\r\n\r\n\r\n \r\n\t\r\n ","install_details":"download and move indsas to whatever folder you like. Add that folder to your $PATH variable if you haven't done that yet.","5":"download and move indsas to whatever folder you like. Add that folder to your $PATH variable if you haven't done that yet.","first_name":"David","6":"David","last_name":"Yeung","7":"Yeung","releases":[{"0":"3624","vim_version":"7.0","1":"7.0","script_version":"V1.2","2":"V1.2","version_comment":"The script can now take file name as argument, no need to use it with pipe.","3":"The script can now take file name as argument, no need to use it with pipe.","package":"indsas","4":"indsas","src_id":"18002","5":"18002","creation_date":"1337571523","6":"1337571523"},{"0":"3624","vim_version":"7.0","1":"7.0","script_version":"V1.1","2":"V1.1","version_comment":"added codes for PUT statement(Same as INPUT)","3":"added codes for PUT statement(Same as INPUT)","package":"indsas","4":"indsas","src_id":"16046","5":"16046","creation_date":"1310002055","6":"1310002055"},{"0":"3624","vim_version":"7.0","1":"7.0","script_version":"V1","2":"V1","version_comment":"Initial upload","3":"Initial upload","package":"indsas","4":"indsas","src_id":"15857","5":"15857","creation_date":"1307828581","6":"1307828581"}]},"3623":{"script_id":"3623","0":"3623","script_name":"chef.vim","1":"chef.vim","script_type":"utility","2":"utility","summary":"make cookbook navigation quick and easy for Opscode's Chef.","3":"make cookbook navigation quick and easy for Opscode's Chef.","description":"https:\/\/github.com\/t9md\/vim-chef\r\n\r\nWhat is this?\r\n==================================\r\nchef.vim is plugin which make it easy for\r\n\r\n  * jump between `attributes` and `recipes`\r\n  * jump between LWRP's `providers` and `resources`\r\n  * open `recipes` by extract filename from `include_recipe`\r\n  * open `templates` and `files`\r\n  * jump to `attributes`\r\n  * jump to `definition`\r\n  * jump to `LWRP`\r\n\r\nCommands\r\n-----------------------------------------------------------------\r\n  * ChefFindAny\r\n  * ChefFindAttribute\r\n  * ChefFindRecipe\r\n  * ChefFindDefinition\r\n  * ChefFindLWRP\r\n  * ChefFindSource\r\n  * ChefFindRelated\r\n","4":"https:\/\/github.com\/t9md\/vim-chef\r\n\r\nWhat is this?\r\n==================================\r\nchef.vim is plugin which make it easy for\r\n\r\n  * jump between `attributes` and `recipes`\r\n  * jump between LWRP's `providers` and `resources`\r\n  * open `recipes` by extract filename from `include_recipe`\r\n  * open `templates` and `files`\r\n  * jump to `attributes`\r\n  * jump to `definition`\r\n  * jump to `LWRP`\r\n\r\nCommands\r\n-----------------------------------------------------------------\r\n  * ChefFindAny\r\n  * ChefFindAttribute\r\n  * ChefFindRecipe\r\n  * ChefFindDefinition\r\n  * ChefFindLWRP\r\n  * ChefFindSource\r\n  * ChefFindRelated\r\n","install_details":"unzip it","5":"unzip it","first_name":"t9","6":"t9","last_name":"md","7":"md","releases":[{"0":"3623","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"2011-08-13: v1.0\r\n        - new finder LWRP.\r\n        - jump between resources and providers are introduced.\r\n2011-08-11:\r\n\t- improve attribute finder","3":"2011-08-13: v1.0\r\n        - new finder LWRP.\r\n        - jump between resources and providers are introduced.\r\n2011-08-11:\r\n\t- improve attribute finder","package":"vim-chef-1.0.zip","4":"vim-chef-1.0.zip","src_id":"16247","5":"16247","creation_date":"1313164563","6":"1313164563"},{"0":"3623","vim_version":"7.0","1":"7.0","script_version":"0.9","2":"0.9","version_comment":"2011-06-15: v0.9\r\n\t- now able to find attribute whichever a[:attr] or a['attr']\r\n\t- bugfix for search order of attribute\r\n\t- search all attribute files under \/attribute\/ directory.","3":"2011-06-15: v0.9\r\n\t- now able to find attribute whichever a[:attr] or a['attr']\r\n\t- bugfix for search order of attribute\r\n\t- search all attribute files under \/attribute\/ directory.","package":"chef-0.9.zip","4":"chef-0.9.zip","src_id":"15899","5":"15899","creation_date":"1308148384","6":"1308148384"},{"0":"3623","vim_version":"7.0","1":"7.0","script_version":"0.8","2":"0.8","version_comment":"0.8\t2011-06-14\r\n\t- Deprecated `ChefDoWhatIMean` for naming consistency.\r\n\t  Now use `ChefFindAny` for this purpose\r\n\t- Provide new command for each Finder.\r\n\t- Now order and targets to for `ChefFindAny` is customizable.\r\n\t- Support definition finding.\r\n\t- Improve debug capability and code consistency.\r\n\t- Suport hook function.\r\n\t- Improve finders information with color highlighted messages.\r\n","3":"0.8\t2011-06-14\r\n\t- Deprecated `ChefDoWhatIMean` for naming consistency.\r\n\t  Now use `ChefFindAny` for this purpose\r\n\t- Provide new command for each Finder.\r\n\t- Now order and targets to for `ChefFindAny` is customizable.\r\n\t- Support definition finding.\r\n\t- Improve debug capability and code consistency.\r\n\t- Suport hook function.\r\n\t- Improve finders information with color highlighted messages.\r\n","package":"chef-0.8.zip","4":"chef-0.8.zip","src_id":"15873","5":"15873","creation_date":"1307988081","6":"1307988081"},{"0":"3623","vim_version":"7.0","1":"7.0","script_version":"0.06","2":"0.06","version_comment":"make attribute finder more fuzzy to make it possible to find node[:apache][:listen_ports] in recipe `apache2`(not apache).","3":"make attribute finder more fuzzy to make it possible to find node[:apache][:listen_ports] in recipe `apache2`(not apache).","package":"chef.zip","4":"chef.zip","src_id":"15856","5":"15856","creation_date":"1307820382","6":"1307820382"},{"0":"3623","vim_version":"7.0","1":"7.0","script_version":"0.05","2":"0.05","version_comment":"Initial upload","3":"Initial upload","package":"chef.zip","4":"chef.zip","src_id":"15855","5":"15855","creation_date":"1307818645","6":"1307818645"}]},"3622":{"script_id":"3622","0":"3622","script_name":"beautiful-pastebin","1":"beautiful-pastebin","script_type":"utility","2":"utility","summary":"Extract a code from pastebin","3":"Extract a code from pastebin","description":"The vim plugin script used for downloading and uploading code directly from\/to pastebin to\/from your vim text editor. ","4":"The vim plugin script used for downloading and uploading code directly from\/to pastebin to\/from your vim text editor. ","install_details":"Install BeautifulSoup http:\/\/www.crummy.com\/software\/BeautifulSoup\/ \r\n\r\nUsage:\r\n Just put bin.vim and beautiful.py in your ~\/.vim\/plugin (Note :if ~\/.vim\/plugin is not there than create it)\r\n You have to set your pastebin emailid\/language\r\n   :let g:pastebin_emailid=\"username@domain.com\"\r\n   :let g:pastebin_language=\"language\"\r\n \r\n\r\n   And if you want to keep your language and email setting forever, \r\n   Simply put them in your ~\/.vimrc\r\n\r\n type:\r\n   :PasteBin   \t\t                     To get code to your vim editor\r\n   :PasteBinUpload          \t    To upload the text from vim editor to pastebin\r\n\r\n","5":"Install BeautifulSoup http:\/\/www.crummy.com\/software\/BeautifulSoup\/ \r\n\r\nUsage:\r\n Just put bin.vim and beautiful.py in your ~\/.vim\/plugin (Note :if ~\/.vim\/plugin is not there than create it)\r\n You have to set your pastebin emailid\/language\r\n   :let g:pastebin_emailid=\"username@domain.com\"\r\n   :let g:pastebin_language=\"language\"\r\n \r\n\r\n   And if you want to keep your language and email setting forever, \r\n   Simply put them in your ~\/.vimrc\r\n\r\n type:\r\n   :PasteBin   \t\t                     To get code to your vim editor\r\n   :PasteBinUpload          \t    To upload the text from vim editor to pastebin\r\n\r\n","first_name":"Aman","6":"Aman","last_name":"Agarwal","7":"Agarwal","releases":[{"0":"3622","vim_version":"7.0","1":"7.0","script_version":"1.1","2":"1.1","version_comment":"You have to set your pastebin emailid\/language\r\n :let g:pastebin_emailid=\"username@domain.com\"\r\n :let g:pastebin_language=\"language\"\r\n \r\n\r\n   And if you want to keep your language and email setting forever, \r\n   Simply put them in your ~\/.vimrc\r\n\r\n type:\r\n   :PasteBin   \t\t                    To get code to your vim editor\r\n   :PasteBinUpload          \t    To Upload the text from vim editor to pastebin\r\n","3":"You have to set your pastebin emailid\/language\r\n :let g:pastebin_emailid=\"username@domain.com\"\r\n :let g:pastebin_language=\"language\"\r\n \r\n\r\n   And if you want to keep your language and email setting forever, \r\n   Simply put them in your ~\/.vimrc\r\n\r\n type:\r\n   :PasteBin   \t\t                    To get code to your vim editor\r\n   :PasteBinUpload          \t    To Upload the text from vim editor to pastebin\r\n","package":"beautiful-pastebin.zip","4":"beautiful-pastebin.zip","src_id":"15839","5":"15839","creation_date":"1307562235","6":"1307562235"},{"0":"3622","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"beautiful-pastebin.zip","4":"beautiful-pastebin.zip","src_id":"15837","5":"15837","creation_date":"1307514041","6":"1307514041"}]},"3621":{"script_id":"3621","0":"3621","script_name":"ri-viewer","1":"ri-viewer","script_type":"utility","2":"utility","summary":"ri-viewer.vim","3":"ri-viewer.vim","description":"ri-viewer.vim looks up ruby document directories with a keyword such like class name or method.\r\n\r\nYou can retrieve details of class Object with bellow command:\r\n\r\n:Ri Object\r\n\r\nand a method detail\r\n\r\n:Ri Object#help\r\n:Ri Object.help\r\n\r\nIf you want to look up documents included in specified dirs such like rubygems, home, try to bellow sub command:\r\n\r\n:RiCore\r\n:RiGem\r\n:RiHome\r\n\r\nRiCore retrieves ri documents included from \/rubylib\/system and \/rubylib\/site.\r\nRiGem retrieves from rubygems and RiHome does it from your home dir(~\/.ri).\r\n\r\nYou can also get all classes and modules list:\r\n\r\n:RiList\r\n\r\nAlso documents directories:\r\n\r\n:RiDirs","4":"ri-viewer.vim looks up ruby document directories with a keyword such like class name or method.\r\n\r\nYou can retrieve details of class Object with bellow command:\r\n\r\n:Ri Object\r\n\r\nand a method detail\r\n\r\n:Ri Object#help\r\n:Ri Object.help\r\n\r\nIf you want to look up documents included in specified dirs such like rubygems, home, try to bellow sub command:\r\n\r\n:RiCore\r\n:RiGem\r\n:RiHome\r\n\r\nRiCore retrieves ri documents included from \/rubylib\/system and \/rubylib\/site.\r\nRiGem retrieves from rubygems and RiHome does it from your home dir(~\/.ri).\r\n\r\nYou can also get all classes and modules list:\r\n\r\n:RiList\r\n\r\nAlso documents directories:\r\n\r\n:RiDirs","install_details":"Copy plugin\/ri-viewer.vim to your runtimepath\/plugin.","5":"Copy plugin\/ri-viewer.vim to your runtimepath\/plugin.","first_name":"Daehyub","6":"Daehyub","last_name":"Kim","7":"Kim","releases":[{"0":"3621","vim_version":"7.0","1":"7.0","script_version":"1.2","2":"1.2","version_comment":"Color Hightlight","3":"Color Hightlight","package":"ri-viewer.tar.gz","4":"ri-viewer.tar.gz","src_id":"15903","5":"15903","creation_date":"1308158337","6":"1308158337"},{"0":"3621","vim_version":"7.0","1":"7.0","script_version":"1.1","2":"1.1","version_comment":"script dismiss in plugin","3":"script dismiss in plugin","package":"ri-viewer.tar.gz","4":"ri-viewer.tar.gz","src_id":"15886","5":"15886","creation_date":"1308061824","6":"1308061824"},{"0":"3621","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"ri-viewer.tar.gz","4":"ri-viewer.tar.gz","src_id":"15831","5":"15831","creation_date":"1307429510","6":"1307429510"}]},"3620":{"script_id":"3620","0":"3620","script_name":"Buffersaurus","1":"Buffersaurus","script_type":"utility","2":"utility","summary":"A Vim Plugin for Searching and Indexing Across Buffers (with Context!)","3":"A Vim Plugin for Searching and Indexing Across Buffers (with Context!)","description":"Buffersaurus is a plugin for searching and indexing the contents of buffers\r\nfor regular expression patterns or collections of regular expression patterns.\r\nResults are displayed in separate buffer, and can be (optionally) viewed with\r\nuser-specifiable lines of context (i.e., a number of lines before and\/or after\r\nthe line matching the search pattern) or filtered for specific patterns.\r\n\r\nGlobal commands provided include (among others):\r\n\r\n  :Bsgrep[!] {pattern}\r\n\r\n    Search all buffers (or just current buffer if \"!\" given) for regular\r\n    expression pattern, {pattern}.\r\n\r\n  :Bstoc[!]\r\n\r\n    Construct a \"table-of-contents\" consisting of filetype-dependent\r\n    \"important\" patterns (e.g. class and method\/function definitions).\r\n\r\nOther commands include those for filtering results, jumping to next\/previous\r\nmatching line without opening the catalog, searching for special user-defined\r\nterms (\"Bsterm\") etc.\r\n\r\nThe results list can be browsed\/navigated using all the usual Vim movement\r\ncommands. Selected lines can be opened in the previous window, a new window\r\nsplit (vertical or horizontal), or a new tab page. Context can be toggled (i.e.\r\nshow a user-specified number of lines before or after the matching line).\r\nResults are grouped and sorted by filename, and then by line number, but can\r\nalso be ungrouped and sorted lexically.\r\n\r\nSearch and replace operations (using the \":Bsreplace\" command, or \"R\" key\r\nmapping), or execution of arbitrary commands (\"x\" or \"X\" key mapping),\r\ncan also be carried out on matched or contexted lines can be carried out\r\n\r\nDetailed usage description is given in the help file, which can be viewed\r\non-line here:\r\n\r\n    http:\/\/github.com\/jeetsukumaran\/vim-buffersaurus\/blob\/master\/doc\/buffersaurus.txt\r\n\r\nSource code repository can be found here:\r\n\r\n    http:\/\/github.com\/jeetsukumaran\/vim-buffersaurus\r\n\r\n","4":"Buffersaurus is a plugin for searching and indexing the contents of buffers\r\nfor regular expression patterns or collections of regular expression patterns.\r\nResults are displayed in separate buffer, and can be (optionally) viewed with\r\nuser-specifiable lines of context (i.e., a number of lines before and\/or after\r\nthe line matching the search pattern) or filtered for specific patterns.\r\n\r\nGlobal commands provided include (among others):\r\n\r\n  :Bsgrep[!] {pattern}\r\n\r\n    Search all buffers (or just current buffer if \"!\" given) for regular\r\n    expression pattern, {pattern}.\r\n\r\n  :Bstoc[!]\r\n\r\n    Construct a \"table-of-contents\" consisting of filetype-dependent\r\n    \"important\" patterns (e.g. class and method\/function definitions).\r\n\r\nOther commands include those for filtering results, jumping to next\/previous\r\nmatching line without opening the catalog, searching for special user-defined\r\nterms (\"Bsterm\") etc.\r\n\r\nThe results list can be browsed\/navigated using all the usual Vim movement\r\ncommands. Selected lines can be opened in the previous window, a new window\r\nsplit (vertical or horizontal), or a new tab page. Context can be toggled (i.e.\r\nshow a user-specified number of lines before or after the matching line).\r\nResults are grouped and sorted by filename, and then by line number, but can\r\nalso be ungrouped and sorted lexically.\r\n\r\nSearch and replace operations (using the \":Bsreplace\" command, or \"R\" key\r\nmapping), or execution of arbitrary commands (\"x\" or \"X\" key mapping),\r\ncan also be carried out on matched or contexted lines can be carried out\r\n\r\nDetailed usage description is given in the help file, which can be viewed\r\non-line here:\r\n\r\n    http:\/\/github.com\/jeetsukumaran\/vim-buffersaurus\/blob\/master\/doc\/buffersaurus.txt\r\n\r\nSource code repository can be found here:\r\n\r\n    http:\/\/github.com\/jeetsukumaran\/vim-buffersaurus\r\n\r\n","install_details":"If Pathogen is installed, you can install Buffersaurus by unpacking the source\r\narchive in $VIMRUNTIME\/bundle.  Otherwise, unpack the source archive and copy\r\n\"buffersaurus.vim\" to $VIMRUNTIME\/plugin and \"buffersaurus.txt\" to\r\n$VIMRUNTIME\/doc.\r\n","5":"If Pathogen is installed, you can install Buffersaurus by unpacking the source\r\narchive in $VIMRUNTIME\/bundle.  Otherwise, unpack the source archive and copy\r\n\"buffersaurus.vim\" to $VIMRUNTIME\/plugin and \"buffersaurus.txt\" to\r\n$VIMRUNTIME\/doc.\r\n","first_name":"Jeet","6":"Jeet","last_name":"Sukumaran","7":"Sukumaran","releases":[{"0":"3620","vim_version":"7.0","1":"7.0","script_version":"2.1.0","2":"2.1.0","version_comment":"- Renamed command: \"Bssubstitute\" for search and replace on matched lines in catalog viewer (this used to be \"Bsreplace\", but now \"Bsreplace\" is a globally available command; see below)\r\n- Renamed command: \"Bsinfo\" for status of search (this used to be \"Bsstatus\")\r\n- NEW command: \"Bsreplace\" for search and replace across all buffers (global command; available everywhere)","3":"- Renamed command: \"Bssubstitute\" for search and replace on matched lines in catalog viewer (this used to be \"Bsreplace\", but now \"Bsreplace\" is a globally available command; see below)\r\n- Renamed command: \"Bsinfo\" for status of search (this used to be \"Bsstatus\")\r\n- NEW command: \"Bsreplace\" for search and replace across all buffers (global command; available everywhere)","package":"vim-buffersaurus-v2.1.0.tar.gz","4":"vim-buffersaurus-v2.1.0.tar.gz","src_id":"17166","5":"17166","creation_date":"1325916433","6":"1325916433"},{"0":"3620","vim_version":"7.0","1":"7.0","script_version":"2.0.1","2":"2.0.1","version_comment":"- command \/ search and replace is not carried out silently, allowing for, e.g. \"c\" flag (i.e., interactive S&R with confirmation)","3":"- command \/ search and replace is not carried out silently, allowing for, e.g. \"c\" flag (i.e., interactive S&R with confirmation)","package":"vim-buffersaurus-v2.0.1.tar.gz","4":"vim-buffersaurus-v2.0.1.tar.gz","src_id":"17116","5":"17116","creation_date":"1324763002","6":"1324763002"},{"0":"3620","vim_version":"7.0","1":"7.0","script_version":"2.0.0","2":"2.0.0","version_comment":"- Ability to carry out search and replace operations (\"R\" or \"ctrl-R\" key maps, or \":Bsreplace\" command) on matched or context lines.\r\n- Ability to execute arbitrary commands (\"x\" or \"X\"  key maps) on matched\/context lines.","3":"- Ability to carry out search and replace operations (\"R\" or \"ctrl-R\" key maps, or \":Bsreplace\" command) on matched or context lines.\r\n- Ability to execute arbitrary commands (\"x\" or \"X\"  key maps) on matched\/context lines.","package":"vim-buffersaurus-v2.0.0.tar.gz","4":"vim-buffersaurus-v2.0.0.tar.gz","src_id":"17115","5":"17115","creation_date":"1324757521","6":"1324757521"},{"0":"3620","vim_version":"7.0","1":"7.0","script_version":"1.2.3","2":"1.2.3","version_comment":"- Do not clobber default register when rendering buffer.\r\n- Fixed bug in window splitting policy.","3":"- Do not clobber default register when rendering buffer.\r\n- Fixed bug in window splitting policy.","package":"vim-buffersaurus-v1.2.3.tar.gz","4":"vim-buffersaurus-v1.2.3.tar.gz","src_id":"16039","5":"16039","creation_date":"1309935741","6":"1309935741"},{"0":"3620","vim_version":"7.0","1":"7.0","script_version":"1.2.1","2":"1.2.1","version_comment":"- added (redundant) key-mapping for 'go', 'gi', 'gs' for NERDTree compatibility","3":"- added (redundant) key-mapping for 'go', 'gi', 'gs' for NERDTree compatibility","package":"vim-buffersaurus-v1.2.1.tar.gz","4":"vim-buffersaurus-v1.2.1.tar.gz","src_id":"15878","5":"15878","creation_date":"1308014115","6":"1308014115"},{"0":"3620","vim_version":"7.0","1":"7.0","script_version":"1.2.0","2":"1.2.0","version_comment":"- switched catalog viewer key mappings to be more consistent with NERDTree: e.g. \"o\/O\", \"s\/S\", \"i\/I\", \"t\/T\" to open\/preview in previous window, vertical split, horizontal split, or tab page respectively; (if you prefer the old key-maps, set \"g:buffersaurus_use_new_keymap=0\" in your $VIMRUNTIME). ","3":"- switched catalog viewer key mappings to be more consistent with NERDTree: e.g. \"o\/O\", \"s\/S\", \"i\/I\", \"t\/T\" to open\/preview in previous window, vertical split, horizontal split, or tab page respectively; (if you prefer the old key-maps, set \"g:buffersaurus_use_new_keymap=0\" in your $VIMRUNTIME). ","package":"vim-buffersaurus-v1.2.0.tar.gz","4":"vim-buffersaurus-v1.2.0.tar.gz","src_id":"15866","5":"15866","creation_date":"1307946345","6":"1307946345"},{"0":"3620","vim_version":"7.0","1":"7.0","script_version":"1.1.0","2":"1.1.0","version_comment":" - Added key mappings to open tabs and splits 'silently' (in the background, keeping focus in catalog window) ","3":" - Added key mappings to open tabs and splits 'silently' (in the background, keeping focus in catalog window) ","package":"vim-buffersaurus-v1.1.0.tar.gz","4":"vim-buffersaurus-v1.1.0.tar.gz","src_id":"15859","5":"15859","creation_date":"1307854404","6":"1307854404"}]},"3619":{"script_id":"3619","0":"3619","script_name":"Buffergator","1":"Buffergator","script_type":"utility","2":"utility","summary":"Buffer listing, selection, and switching\/navigation utility","3":"Buffer listing, selection, and switching\/navigation utility","description":"Summary\r\n=======\r\n\r\n- Use `<Leader>b` (typically: `\\b`) to open a window listing all buffers. In this\r\n  window, you can use normal movement keys to select a buffer and then:\r\n\r\n    - <ENTER> to edit the selected buffer in the previous window\r\n    - <C-V> to edit the selected buffer in a new vertical split\r\n    - <C-S> to edit the selected buffer in a new horizontal split\r\n    - <C-T> to edit the selected buffer in a new tab page\r\n\r\n- Use `[b` (or <M-b>) and `]b` (or <M-S-b>) to flip through the most-recently\r\n  used buffer stack without opening the buffer listing \"drawer\".\r\n\r\nMany other options are supported: (e.g. open in existing window\/tab, or in the\r\nsame window; preview buffer without leaving buffer listing; \"pin\" the buffer\r\nlisting so that it is open all the time, etc. etc.)\r\n\r\nDetails\r\n=======\r\n\r\nBuffergator is a plugin for listing, navigating between, and selecting buffers\r\nto edit. Upon invocation (using the command, \":BuffergatorOpen\" or\r\n\"BuffergatorToggle\", or the provided key mapping, \"<Leader>b\"), a \"catalog\" of\r\nlisted buffers are displayed in a separate new window split (vertical or\r\nhorizontal, based on user options; default = vertical).  From this \"buffer\r\ncatalog\", a buffer can be selected and opened in an existing window, a new\r\nwindow split (vertical or horizontal), or a new tab page.\r\n\r\nSelected buffers can be \"previewed\", i.e. opened in a window or tab page, but\r\nwith focus remaining in the buffer catalog. Even better, you can \"walk\" up and\r\ndown the list of buffers shown in the catalog by using <C-N> (or <SPACE>) \/\r\n<C-P> (or <C-SPACE>). These keys select the next\/previous buffer in succession,\r\nrespectively, opening it for preview without leaving the buffer catalog\r\nviewer.\r\n\r\nThe buffer opening commands follow that of NERDTree. Examples:\r\n\r\n    - Use movement keys (h,j,k,l) to select a buffer from the list, then type\r\n      <CR> or \"o\" to open it in the previous window.\r\n    - Type \"42\" and <CR> or \"o\" to open buffer number 42 in the previous\r\n      window.\r\n    - You can use \"go\" to open the currently selected buffer in the previous\r\n      window, but with focus remaining in the buffer catalog (\"42go\" will do\r\n      the same, but will select buffer number 42).\r\n    - You can use \"s\" to open the currently selected buffer in new vertical\r\n      split. \"S\" will open the buffer in a new vertical split, but keep the\r\n      focus in the buffer catalog.  (\"42s\" or \"42S\" will do the same, but will\r\n      select buffer number 42)\r\n    - You can use \"i\" to open the currently selected buffer in new horizontal\r\n      split. \"I\" will open the buffer in a new vertical split, but keep the\r\n      focus in the buffer catalog.  (\"42i\" or \"42I\" will do the same, but will\r\n      select buffer number 42)\r\n    - You can use \"t\" to open the currently selected buffer in new tab (\"42t\"\r\n      will do the same, but will select buffer number 42).\r\n\r\nTo reduce strain on muscle-memory, the following Ctrl-P keymaps are also\r\nsupported:\r\n\r\n   - <C-V> : open in new vertical split\r\n   - <C-S> : open in new horizontal split\r\n   - <C-T> : open in new tab\r\n\r\nOther key maps allow you to jump to a target buffer in an open\r\nwindow\/split\/tab page if it is already active there instead of creating a new\r\nwindow. Minimal management of buffers (wiping\/dropping) are also provided.\r\n\r\nBuffergator also provides a way to list tab pages and buffers associated with\r\nwindows in tab pages (the \"tab page catalog\", which can be invoked using the\r\ncommand \":BuffergatorTabsOpen\" or the provided key mapping, \"<Leader>t\").\r\n\r\nThe buffer listing can be sorted alphabetically by filename, by full filepath,\r\nby extension followed by filename, or by most-recently used (MRU).\r\n\r\nBy default, Buffergator provides global key maps that invoke its main commands:\r\n\"<Leader>b\" to open and \"<Leader>B\" to close the buffer catalog, and\r\n\"<Leader>t\" to open and \"<Leader>T\" to close the tab page catalog.  In\r\naddition, in normal mode from any buffer, you can flip through the MRU\r\n(most-recently-used) buffer list without opening the buffer catalog by using\r\nthe \"[b\" (or <M-b>) and \"]b\" (or <M-S-b>) keys.  If you prefer to map other\r\nkeys, or do not want any keys mapped at all, set\r\n\"g:buffergator_suppress_keymaps\" to 1 in your $VIMRUNTIME.\r\n\r\n[NOTE: If you have other plugins installed that have key maps that start with\r\n\"<Leader>b\" (e.g., BufExplorer, which uses \"<Leader>bs\", \"<Leader>bv\", etc.),\r\nthen you may notice a slight delay or lag when typing the default \"<Leader>b\"\r\nto start Buffergator. In this case, you should either use another keymap for\r\nBuffergator or BufExplorer.]\r\n\r\nDetailed usage description given in the help file, which can be viewed on-line\r\nhere:\r\n\r\n    http:\/\/github.com\/jeetsukumaran\/vim-buffergator\/blob\/master\/doc\/buffergator.txt\r\n\r\nSource code repository can be found here:\r\n\r\n    http:\/\/github.com\/jeetsukumaran\/vim-buffergator\r\n\r\nNOTE: There are many other plugins that provide similar functionality. This\r\nplugin is very much in the \"BufExplorer\" and \"SelectBuf\" vein, in that it\r\nprovides a full-window buffer \"view\" of the buffers. I wanted a plugin that (a)\r\nlisted the loaded buffers in a (optionally-)persistant \"drawer\", (b) allowed me\r\nto preview buffers without leaving the drawer, and (c) allowed me to walk up\r\nand down the list of buffers, previewing them, but without leaving the drawer.\r\nNone of the existing plugins did this (as far as I know), and hence I rolled\r\nout this one. The other plugins provide more functionality with respect to\r\nother operations (e.g., buffer management), that I did not have an immediate\r\nneed for, so I did not incorporate it into this plugin.\r\n\r\n","4":"Summary\r\n=======\r\n\r\n- Use `<Leader>b` (typically: `\\b`) to open a window listing all buffers. In this\r\n  window, you can use normal movement keys to select a buffer and then:\r\n\r\n    - <ENTER> to edit the selected buffer in the previous window\r\n    - <C-V> to edit the selected buffer in a new vertical split\r\n    - <C-S> to edit the selected buffer in a new horizontal split\r\n    - <C-T> to edit the selected buffer in a new tab page\r\n\r\n- Use `[b` (or <M-b>) and `]b` (or <M-S-b>) to flip through the most-recently\r\n  used buffer stack without opening the buffer listing \"drawer\".\r\n\r\nMany other options are supported: (e.g. open in existing window\/tab, or in the\r\nsame window; preview buffer without leaving buffer listing; \"pin\" the buffer\r\nlisting so that it is open all the time, etc. etc.)\r\n\r\nDetails\r\n=======\r\n\r\nBuffergator is a plugin for listing, navigating between, and selecting buffers\r\nto edit. Upon invocation (using the command, \":BuffergatorOpen\" or\r\n\"BuffergatorToggle\", or the provided key mapping, \"<Leader>b\"), a \"catalog\" of\r\nlisted buffers are displayed in a separate new window split (vertical or\r\nhorizontal, based on user options; default = vertical).  From this \"buffer\r\ncatalog\", a buffer can be selected and opened in an existing window, a new\r\nwindow split (vertical or horizontal), or a new tab page.\r\n\r\nSelected buffers can be \"previewed\", i.e. opened in a window or tab page, but\r\nwith focus remaining in the buffer catalog. Even better, you can \"walk\" up and\r\ndown the list of buffers shown in the catalog by using <C-N> (or <SPACE>) \/\r\n<C-P> (or <C-SPACE>). These keys select the next\/previous buffer in succession,\r\nrespectively, opening it for preview without leaving the buffer catalog\r\nviewer.\r\n\r\nThe buffer opening commands follow that of NERDTree. Examples:\r\n\r\n    - Use movement keys (h,j,k,l) to select a buffer from the list, then type\r\n      <CR> or \"o\" to open it in the previous window.\r\n    - Type \"42\" and <CR> or \"o\" to open buffer number 42 in the previous\r\n      window.\r\n    - You can use \"go\" to open the currently selected buffer in the previous\r\n      window, but with focus remaining in the buffer catalog (\"42go\" will do\r\n      the same, but will select buffer number 42).\r\n    - You can use \"s\" to open the currently selected buffer in new vertical\r\n      split. \"S\" will open the buffer in a new vertical split, but keep the\r\n      focus in the buffer catalog.  (\"42s\" or \"42S\" will do the same, but will\r\n      select buffer number 42)\r\n    - You can use \"i\" to open the currently selected buffer in new horizontal\r\n      split. \"I\" will open the buffer in a new vertical split, but keep the\r\n      focus in the buffer catalog.  (\"42i\" or \"42I\" will do the same, but will\r\n      select buffer number 42)\r\n    - You can use \"t\" to open the currently selected buffer in new tab (\"42t\"\r\n      will do the same, but will select buffer number 42).\r\n\r\nTo reduce strain on muscle-memory, the following Ctrl-P keymaps are also\r\nsupported:\r\n\r\n   - <C-V> : open in new vertical split\r\n   - <C-S> : open in new horizontal split\r\n   - <C-T> : open in new tab\r\n\r\nOther key maps allow you to jump to a target buffer in an open\r\nwindow\/split\/tab page if it is already active there instead of creating a new\r\nwindow. Minimal management of buffers (wiping\/dropping) are also provided.\r\n\r\nBuffergator also provides a way to list tab pages and buffers associated with\r\nwindows in tab pages (the \"tab page catalog\", which can be invoked using the\r\ncommand \":BuffergatorTabsOpen\" or the provided key mapping, \"<Leader>t\").\r\n\r\nThe buffer listing can be sorted alphabetically by filename, by full filepath,\r\nby extension followed by filename, or by most-recently used (MRU).\r\n\r\nBy default, Buffergator provides global key maps that invoke its main commands:\r\n\"<Leader>b\" to open and \"<Leader>B\" to close the buffer catalog, and\r\n\"<Leader>t\" to open and \"<Leader>T\" to close the tab page catalog.  In\r\naddition, in normal mode from any buffer, you can flip through the MRU\r\n(most-recently-used) buffer list without opening the buffer catalog by using\r\nthe \"[b\" (or <M-b>) and \"]b\" (or <M-S-b>) keys.  If you prefer to map other\r\nkeys, or do not want any keys mapped at all, set\r\n\"g:buffergator_suppress_keymaps\" to 1 in your $VIMRUNTIME.\r\n\r\n[NOTE: If you have other plugins installed that have key maps that start with\r\n\"<Leader>b\" (e.g., BufExplorer, which uses \"<Leader>bs\", \"<Leader>bv\", etc.),\r\nthen you may notice a slight delay or lag when typing the default \"<Leader>b\"\r\nto start Buffergator. In this case, you should either use another keymap for\r\nBuffergator or BufExplorer.]\r\n\r\nDetailed usage description given in the help file, which can be viewed on-line\r\nhere:\r\n\r\n    http:\/\/github.com\/jeetsukumaran\/vim-buffergator\/blob\/master\/doc\/buffergator.txt\r\n\r\nSource code repository can be found here:\r\n\r\n    http:\/\/github.com\/jeetsukumaran\/vim-buffergator\r\n\r\nNOTE: There are many other plugins that provide similar functionality. This\r\nplugin is very much in the \"BufExplorer\" and \"SelectBuf\" vein, in that it\r\nprovides a full-window buffer \"view\" of the buffers. I wanted a plugin that (a)\r\nlisted the loaded buffers in a (optionally-)persistant \"drawer\", (b) allowed me\r\nto preview buffers without leaving the drawer, and (c) allowed me to walk up\r\nand down the list of buffers, previewing them, but without leaving the drawer.\r\nNone of the existing plugins did this (as far as I know), and hence I rolled\r\nout this one. The other plugins provide more functionality with respect to\r\nother operations (e.g., buffer management), that I did not have an immediate\r\nneed for, so I did not incorporate it into this plugin.\r\n\r\n","install_details":"If Pathogen is installed, you can install Buffergator by unpacking the source\r\narchive in $VIMRUNTIME\/bundle.  Otherwise, unpack the source archive and copy\r\n\"buffergator.vim\" to $VIMRUNTIME\/plugin and \"buffergator.txt\" to\r\n$VIMRUNTIME\/doc.\r\n","5":"If Pathogen is installed, you can install Buffergator by unpacking the source\r\narchive in $VIMRUNTIME\/bundle.  Otherwise, unpack the source archive and copy\r\n\"buffergator.vim\" to $VIMRUNTIME\/plugin and \"buffergator.txt\" to\r\n$VIMRUNTIME\/doc.\r\n","first_name":"Jeet","6":"Jeet","last_name":"Sukumaran","7":"Sukumaran","releases":[{"0":"3619","vim_version":"7.0","1":"7.0","script_version":"2.4.1","2":"2.4.1","version_comment":"- Use 'gb' and 'gB' as default mappings for going to previous and next MRU buffer to avoid collisions with vim-unimpaired.","3":"- Use 'gb' and 'gB' as default mappings for going to previous and next MRU buffer to avoid collisions with vim-unimpaired.","package":"vim-buffergator-v2.4.1.tar.gz","4":"vim-buffergator-v2.4.1.tar.gz","src_id":"22812","5":"22812","creation_date":"1421723485","6":"1421723485"},{"0":"3619","vim_version":"7.0","1":"7.0","script_version":"2.4.0","2":"2.4.0","version_comment":"- Split into previous MRU buffer\r\n- Ignore netre buffers\r\n- Documentation fixes (thanks Andy Balaam)\r\n- Various bug-fixes","3":"- Split into previous MRU buffer\r\n- Ignore netre buffers\r\n- Documentation fixes (thanks Andy Balaam)\r\n- Various bug-fixes","package":"vim-buffergator-v2.4.0.tar.gz","4":"vim-buffergator-v2.4.0.tar.gz","src_id":"21751","5":"21751","creation_date":"1396987889","6":"1396987889"},{"0":"3619","vim_version":"7.0","1":"7.0","script_version":"2.3.2","2":"2.3.2","version_comment":"- Split into MRU buffer using <Leader><Left>, <Leader><Up>, <Leader><Right>, and <Leader><Down> keys (for left, top, right, and bottom splits, respectively).","3":"- Split into MRU buffer using <Leader><Left>, <Leader><Up>, <Leader><Right>, and <Leader><Down> keys (for left, top, right, and bottom splits, respectively).","package":"vim-buffergator-v2.3.2.tar.gz","4":"vim-buffergator-v2.3.2.tar.gz","src_id":"20082","5":"20082","creation_date":"1368127302","6":"1368127302"},{"0":"3619","vim_version":"7.0","1":"7.0","script_version":"2.3.1","2":"2.3.1","version_comment":"- When cycling through MRU buffers using ']b'\/<M-B> and '[b'\/<M-S-B> keys, cycle though local-window MRU buffer history instead of global history.","3":"- When cycling through MRU buffers using ']b'\/<M-B> and '[b'\/<M-S-B> keys, cycle though local-window MRU buffer history instead of global history.","package":"vim-buffergator-v2.3.1.tar.gz","4":"vim-buffergator-v2.3.1.tar.gz","src_id":"19952","5":"19952","creation_date":"1367087796","6":"1367087796"},{"0":"3619","vim_version":"7.0","1":"7.0","script_version":"2.3.0","2":"2.3.0","version_comment":"- Navigate the MRU buffer stack using global normal mode keys: in normal mode from any buffer, you can flip through the MRU(most-recently-used) buffer list without opening the Buffergator buffer catalog by using the \"[b\" (or <M-b>) and \"]b\" (or <M-S-b>) keys.\r\n","3":"- Navigate the MRU buffer stack using global normal mode keys: in normal mode from any buffer, you can flip through the MRU(most-recently-used) buffer list without opening the Buffergator buffer catalog by using the \"[b\" (or <M-b>) and \"]b\" (or <M-S-b>) keys.\r\n","package":"vim-buffergator-v2.3.0.tar.gz","4":"vim-buffergator-v2.3.0.tar.gz","src_id":"19930","5":"19930","creation_date":"1366853627","6":"1366853627"},{"0":"3619","vim_version":"7.0","1":"7.0","script_version":"2.2.2","2":"2.2.2","version_comment":"- Support for cycling through viewport\/window split modes (``cw`` cycle through opening Buffergator in left, top, right, and bottom splits)\r\n- Support for Ctrl-P\/Cmd-T split-selection keymaps (CTRL-V to open in vertical split, CTRL-S to open in horizontal split, CTRL-T to open in tab)\r\n- Support for toggling autodismiss modes (``cq``: toggle whether or not Buffergator closes after a buffer selection is made)\r\n","3":"- Support for cycling through viewport\/window split modes (``cw`` cycle through opening Buffergator in left, top, right, and bottom splits)\r\n- Support for Ctrl-P\/Cmd-T split-selection keymaps (CTRL-V to open in vertical split, CTRL-S to open in horizontal split, CTRL-T to open in tab)\r\n- Support for toggling autodismiss modes (``cq``: toggle whether or not Buffergator closes after a buffer selection is made)\r\n","package":"vim-buffergator-v2.2.2.tar.gz","4":"vim-buffergator-v2.2.2.tar.gz","src_id":"19918","5":"19918","creation_date":"1366753133","6":"1366753133"},{"0":"3619","vim_version":"7.0","1":"7.0","script_version":"2.1.1","2":"2.1.1","version_comment":"  - [BUG FIX] now works with Spanish locales (thanks to kolme)","3":"  - [BUG FIX] now works with Spanish locales (thanks to kolme)","package":"vim-buffergator-v2.1.1.tar.gz","4":"vim-buffergator-v2.1.1.tar.gz","src_id":"16816","5":"16816","creation_date":"1320612904","6":"1320612904"},{"0":"3619","vim_version":"7.0","1":"7.0","script_version":"2.1.0","2":"2.1.0","version_comment":"- NEW FEATURE: Can now use buffer number as [count] preceding key map (so, for example, \\\"42s\\\" opens buffer number 42 in a new split).\r\n- BUG FIX:  Buffergator window size remains fixed when window equalization command is given (thanks to Jan Christoph Ebersbach).\r\n- BUG FIX: Alternate buffer designation behaves similar to \\\":buffer\\\" command (thanks to Jan Christoph Ebersbach)","3":"- NEW FEATURE: Can now use buffer number as [count] preceding key map (so, for example, \\\"42s\\\" opens buffer number 42 in a new split).\r\n- BUG FIX:  Buffergator window size remains fixed when window equalization command is given (thanks to Jan Christoph Ebersbach).\r\n- BUG FIX: Alternate buffer designation behaves similar to \\\":buffer\\\" command (thanks to Jan Christoph Ebersbach)","package":"vim-buffergator-v2.1.0.tar.gz","4":"vim-buffergator-v2.1.0.tar.gz","src_id":"16686","5":"16686","creation_date":"1318835815","6":"1318835815"},{"0":"3619","vim_version":"7.0","1":"7.0","script_version":"2.0.0","2":"2.0.0","version_comment":"- [NEW FEATURE] : Listing\/selection\/navigation of tab pages and tab page windows \r\n- [NEW FEATURE] : Sort buffers (in buffer catalog) in MRU (most-recently used) order [thanks to Jeff Kinslow, https:\/\/github.com\/jkins] \r\n- [BUG FIX] : Can handle different locales","3":"- [NEW FEATURE] : Listing\/selection\/navigation of tab pages and tab page windows \r\n- [NEW FEATURE] : Sort buffers (in buffer catalog) in MRU (most-recently used) order [thanks to Jeff Kinslow, https:\/\/github.com\/jkins] \r\n- [BUG FIX] : Can handle different locales","package":"vim-buffergator-v2.0.0.tar.gz","4":"vim-buffergator-v2.0.0.tar.gz","src_id":"16426","5":"16426","creation_date":"1314874114","6":"1314874114"},{"0":"3619","vim_version":"7.0","1":"7.0","script_version":"1.3.2","2":"1.3.2","version_comment":"- Do not clobber default register when rendering buffer. ","3":"- Do not clobber default register when rendering buffer. ","package":"vim-buffergator-v1.3.2.tar.gz","4":"vim-buffergator-v1.3.2.tar.gz","src_id":"16041","5":"16041","creation_date":"1309936995","6":"1309936995"},{"0":"3619","vim_version":"7.0","1":"7.0","script_version":"1.3.1","2":"1.3.1","version_comment":"- respect autodismiss policy when trying to show existing\r\n- command to only show buffer if it is already visible in a viewport","3":"- respect autodismiss policy when trying to show existing\r\n- command to only show buffer if it is already visible in a viewport","package":"vim-buffergator-v1.3.1.tar.gz","4":"vim-buffergator-v1.3.1.tar.gz","src_id":"16002","5":"16002","creation_date":"1309304303","6":"1309304303"},{"0":"3619","vim_version":"7.0","1":"7.0","script_version":"1.3.0","2":"1.3.0","version_comment":"- Keys\/commands to preferentially go to existing viewport already showing currently-selected buffer ('eo', 'es', 'ei', and 'et')","3":"- Keys\/commands to preferentially go to existing viewport already showing currently-selected buffer ('eo', 'es', 'ei', and 'et')","package":"vim-buffergator-v1.3.0.tar.gz","4":"vim-buffergator-v1.3.0.tar.gz","src_id":"16001","5":"16001","creation_date":"1309303630","6":"1309303630"},{"0":"3619","vim_version":"7.0","1":"7.0","script_version":"1.2.1","2":"1.2.1","version_comment":"- added (redundant) key-mapping for 'go', 'gi', 'gs' for NERDTree compatibility","3":"- added (redundant) key-mapping for 'go', 'gi', 'gs' for NERDTree compatibility","package":"vim-buffergator-v1.2.1.tar.gz","4":"vim-buffergator-v1.2.1.tar.gz","src_id":"15879","5":"15879","creation_date":"1308014183","6":"1308014183"},{"0":"3619","vim_version":"7.0","1":"7.0","script_version":"1.2.0","2":"1.2.0","version_comment":"- switched to catalog viewer key mappings more consistent with NERDTree: e.g. \"o\/O\", \"s\/S\", \"i\/I\", \"t\/T\" to open\/preview in previous window, vertical split, horizontal split, or tab page respectively; (if you prefer the old key-maps, set \"g:buffergator_use_new_keymap=0\" in your $VIMRUNTIME). \r\n- added sorting by filename extension\r\n","3":"- switched to catalog viewer key mappings more consistent with NERDTree: e.g. \"o\/O\", \"s\/S\", \"i\/I\", \"t\/T\" to open\/preview in previous window, vertical split, horizontal split, or tab page respectively; (if you prefer the old key-maps, set \"g:buffergator_use_new_keymap=0\" in your $VIMRUNTIME). \r\n- added sorting by filename extension\r\n","package":"vim-buffergator-v1.2.0.tar.gz","4":"vim-buffergator-v1.2.0.tar.gz","src_id":"15865","5":"15865","creation_date":"1307946273","6":"1307946273"},{"0":"3619","vim_version":"7.0","1":"7.0","script_version":"1.1.0","2":"1.1.0","version_comment":"  - Added key mappings to open tabs and splits 'silently' (in the background, keeping focus in catalog window)\r\n","3":"  - Added key mappings to open tabs and splits 'silently' (in the background, keeping focus in catalog window)\r\n","package":"vim-buffergator-v1.1.0.tar.gz","4":"vim-buffergator-v1.1.0.tar.gz","src_id":"15858","5":"15858","creation_date":"1307854344","6":"1307854344"}]},"3618":{"script_id":"3618","0":"3618","script_name":"wikilink","1":"wikilink","script_type":"utility","2":"utility","summary":"Personal wiki link navigator ","3":"Personal wiki link navigator ","description":"\"WikiLink\" is a Vim plugin which eases the navigation between files  in a personnal wiki.\r\n\r\n Links syntax currently supported follows Github's Gollum (https:\/\/github.com\/github\/gollum)\r\n ie [[My link|My displayed link]]\r\n\r\n This plugin also detects footerbar and sidebar files and splits the window\r\n accordingly (again, see Gollum for syntax)\r\n\r\nUsage\r\n -----\r\n  Hit the ENTER key when the cursor is on a wiki link\r\n  The corresponding file is loaded in the current buffer\r\n \r\n  Hit Shift + ENTER to go back\r\n\r\n Contribute\r\n ----------\r\n  You can fork this project on Github : https:\/\/github.com\/mmai\/wikilink","4":"\"WikiLink\" is a Vim plugin which eases the navigation between files  in a personnal wiki.\r\n\r\n Links syntax currently supported follows Github's Gollum (https:\/\/github.com\/github\/gollum)\r\n ie [[My link|My displayed link]]\r\n\r\n This plugin also detects footerbar and sidebar files and splits the window\r\n accordingly (again, see Gollum for syntax)\r\n\r\nUsage\r\n -----\r\n  Hit the ENTER key when the cursor is on a wiki link\r\n  The corresponding file is loaded in the current buffer\r\n \r\n  Hit Shift + ENTER to go back\r\n\r\n Contribute\r\n ----------\r\n  You can fork this project on Github : https:\/\/github.com\/mmai\/wikilink","install_details":"Copy the wikilink.vim file into the $HOME\/.vim\/plugin\/ directory\r\n\r\nWindow split on footer and sidebar detection can be disabled by writing thisline on your .vimrc file :\r\nlet wikilinkAutosplit=\"off\"","5":"Copy the wikilink.vim file into the $HOME\/.vim\/plugin\/ directory\r\n\r\nWindow split on footer and sidebar detection can be disabled by writing thisline on your .vimrc file :\r\nlet wikilinkAutosplit=\"off\"","first_name":"Henri","6":"Henri","last_name":"Bourcereau","7":"Bourcereau","releases":[{"0":"3618","vim_version":"7.0","1":"7.0","script_version":"0.6","2":"0.6","version_comment":"* substitute spaces by dashes regex to support relative directories\r\n* remove leading and trailing spaces in new files names ","3":"* substitute spaces by dashes regex to support relative directories\r\n* remove leading and trailing spaces in new files names ","package":"wikilink.vim","4":"wikilink.vim","src_id":"21978","5":"21978","creation_date":"1401699586","6":"1401699586"},{"0":"3618","vim_version":"7.0","1":"7.0","script_version":"0.5","2":"0.5","version_comment":"Add shortcut Shift+Enter to go back to the previous page","3":"Add shortcut Shift+Enter to go back to the previous page","package":"wikilink.vim","4":"wikilink.vim","src_id":"17806","5":"17806","creation_date":"1335014439","6":"1335014439"},{"0":"3618","vim_version":"7.0","1":"7.0","script_version":"0.4","2":"0.4","version_comment":"Cleaner window redrawing.\r\nWindow split on footer and sidebar detection is now optional.","3":"Cleaner window redrawing.\r\nWindow split on footer and sidebar detection is now optional.","package":"wikilink.vim","4":"wikilink.vim","src_id":"16549","5":"16549","creation_date":"1316366158","6":"1316366158"},{"0":"3618","vim_version":"7.0","1":"7.0","script_version":"0.3","2":"0.3","version_comment":"footerbar and sidebar detection ","3":"footerbar and sidebar detection ","package":"wikilink.vim","4":"wikilink.vim","src_id":"15898","5":"15898","creation_date":"1308142358","6":"1308142358"},{"0":"3618","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"wikilink.vim","4":"wikilink.vim","src_id":"15825","5":"15825","creation_date":"1307372938","6":"1307372938"}]},"3617":{"script_id":"3617","0":"3617","script_name":"Quicksilver.vim","1":"Quicksilver.vim","script_type":"utility","2":"utility","summary":"Quickly open files from inside VIM.","3":"Quickly open files from inside VIM.","description":"Quicksilver is a VIM plugin whose purpose is to quicken the process of\r\nopening files from inside VIM.\r\n\r\n# Preview\r\n\r\nVideo: http:\/\/www.youtube.com\/watch?v=RDsey4YqpHs\r\n\r\nScreenshot: http:\/\/farm4.static.flickr.com\/3383\/5804126014_072806d823_z.jpg\r\n\r\n# Usage\r\n\r\nBy default, `\\q` will activate the Quicksilver buffer and switch to insert\r\nmode. Typing any key will update the list of suggestions and pressing `CR`\r\nwill open the first item in the suggestion list. Use `C-c` to quickly\r\nclose the buffer.\r\n\r\nYou may cycle through the suggestion list using `Tab` and `S-Tab`. `CR` will\r\nopen the current suggestion (that's the first item in the list of matches).\r\n\r\nIf there is only one item in the suggestion list, pressing `Tab` will open\r\nthat item.\r\n\r\nPressing `CR` when there is no pattern will go up a directory.\r\n\r\n`C-w` clears the entire pattern. If there is no pattern, it will go up a\r\ndirectory.\r\n\r\n`C-t` toggles between if pattern and filename case should be ignored or\r\nnot.\r\n\r\n`C-f` turns on `fuzzy matching`. Fuzzy matching will match any filename\r\nthat contains every character in pattern in order. For example, the\r\npattern `rdm` will match `README` but not `REMADE`.\r\n\r\n`C-n` turns on `normal matching`. Normal matching will match any\r\nfilename that contains the exact pattern within it. For example, the\r\npattern `foo` will match `foo` and `foob` but not `ofo` or `oof`.\r\n\r\nIf you prefer fuzzy matching and would like Quicksilver to default to using it\r\ninstead of normal matching then you can add `let g:QSMatchFn = 'fuzzy'`\r\nto your `.vimrc`.\r\n\r\nIf a file with the given pattern does not exist then a new file will be\r\nopened for editing with the given pattern as its filename. If a pattern\r\nends in `\/`, quicksilver will create a new folder, change its CWD to\r\nthat folder and remain in insert mode expecting a file name.\r\n\r\nPatterns that start or end in a wildcard (`*`) are treated as glob\r\npatterns. For example, the pattern `*.md` will open all the files that\r\nhave the extension `.md` in the CWD.\r\n\r\n# Requirements\r\n\r\n* VIM 7.0+ compiled with +python\r\n* Python 2.6+\r\n\r\n[1]: http:\/\/github.com\/tpope\/vim-pathogen","4":"Quicksilver is a VIM plugin whose purpose is to quicken the process of\r\nopening files from inside VIM.\r\n\r\n# Preview\r\n\r\nVideo: http:\/\/www.youtube.com\/watch?v=RDsey4YqpHs\r\n\r\nScreenshot: http:\/\/farm4.static.flickr.com\/3383\/5804126014_072806d823_z.jpg\r\n\r\n# Usage\r\n\r\nBy default, `\\q` will activate the Quicksilver buffer and switch to insert\r\nmode. Typing any key will update the list of suggestions and pressing `CR`\r\nwill open the first item in the suggestion list. Use `C-c` to quickly\r\nclose the buffer.\r\n\r\nYou may cycle through the suggestion list using `Tab` and `S-Tab`. `CR` will\r\nopen the current suggestion (that's the first item in the list of matches).\r\n\r\nIf there is only one item in the suggestion list, pressing `Tab` will open\r\nthat item.\r\n\r\nPressing `CR` when there is no pattern will go up a directory.\r\n\r\n`C-w` clears the entire pattern. If there is no pattern, it will go up a\r\ndirectory.\r\n\r\n`C-t` toggles between if pattern and filename case should be ignored or\r\nnot.\r\n\r\n`C-f` turns on `fuzzy matching`. Fuzzy matching will match any filename\r\nthat contains every character in pattern in order. For example, the\r\npattern `rdm` will match `README` but not `REMADE`.\r\n\r\n`C-n` turns on `normal matching`. Normal matching will match any\r\nfilename that contains the exact pattern within it. For example, the\r\npattern `foo` will match `foo` and `foob` but not `ofo` or `oof`.\r\n\r\nIf you prefer fuzzy matching and would like Quicksilver to default to using it\r\ninstead of normal matching then you can add `let g:QSMatchFn = 'fuzzy'`\r\nto your `.vimrc`.\r\n\r\nIf a file with the given pattern does not exist then a new file will be\r\nopened for editing with the given pattern as its filename. If a pattern\r\nends in `\/`, quicksilver will create a new folder, change its CWD to\r\nthat folder and remain in insert mode expecting a file name.\r\n\r\nPatterns that start or end in a wildcard (`*`) are treated as glob\r\npatterns. For example, the pattern `*.md` will open all the files that\r\nhave the extension `.md` in the CWD.\r\n\r\n# Requirements\r\n\r\n* VIM 7.0+ compiled with +python\r\n* Python 2.6+\r\n\r\n[1]: http:\/\/github.com\/tpope\/vim-pathogen","install_details":"Use pathogen (http:\/\/github.com\/tpope\/vim-pathogen) and clone \r\nthe github repository (https:\/\/github.com\/Bogdanp\/quicksilver.vim) \r\ninto your ~\/.vim\/bundle directory or download quicksilver.vim to\r\nyour ~\/.vim\/plugin\/ directory.","5":"Use pathogen (http:\/\/github.com\/tpope\/vim-pathogen) and clone \r\nthe github repository (https:\/\/github.com\/Bogdanp\/quicksilver.vim) \r\ninto your ~\/.vim\/bundle directory or download quicksilver.vim to\r\nyour ~\/.vim\/plugin\/ directory.","first_name":"Bogdan","6":"Bogdan","last_name":"Popa","7":"Popa","releases":[{"0":"3617","vim_version":"7.0","1":"7.0","script_version":"0.4.6","2":"0.4.6","version_comment":"* Removes the OrderedDict dependency, it should now work properly on systems with Python 2.6.x.","3":"* Removes the OrderedDict dependency, it should now work properly on systems with Python 2.6.x.","package":"quicksilver.vim","4":"quicksilver.vim","src_id":"17889","5":"17889","creation_date":"1336378235","6":"1336378235"},{"0":"3617","vim_version":"7.0","1":"7.0","script_version":"0.4.5","2":"0.4.5","version_comment":"* Fix 're' import issue.\r\n* Fix QSActivate.","3":"* Fix 're' import issue.\r\n* Fix QSActivate.","package":"quicksilver.vim","4":"quicksilver.vim","src_id":"17886","5":"17886","creation_date":"1336335052","6":"1336335052"},{"0":"3617","vim_version":"7.0","1":"7.0","script_version":"0.4.4","2":"0.4.4","version_comment":"* Fix re import issue.","3":"* Fix re import issue.","package":"quicksilver.vim","4":"quicksilver.vim","src_id":"17879","5":"17879","creation_date":"1336309677","6":"1336309677"},{"0":"3617","vim_version":"7.0","1":"7.0","script_version":"0.4.2","2":"0.4.2","version_comment":" ","3":" ","package":"quicksilver.vim","4":"quicksilver.vim","src_id":"17874","5":"17874","creation_date":"1336246774","6":"1336246774"},{"0":"3617","vim_version":"7.0","1":"7.0","script_version":"0.4","2":"0.4","version_comment":"* Fixed Windows support.","3":"* Fixed Windows support.","package":"quicksilver.vim","4":"quicksilver.vim","src_id":"17868","5":"17868","creation_date":"1336160518","6":"1336160518"},{"0":"3617","vim_version":"7.0","1":"7.0","script_version":"0.3.1","2":"0.3.1","version_comment":"New in version 0.3.1:\r\n\r\n* If there is only one file in the suggestion list, pressing Tab will open that file.","3":"New in version 0.3.1:\r\n\r\n* If there is only one file in the suggestion list, pressing Tab will open that file.","package":"quicksilver.vim","4":"quicksilver.vim","src_id":"15842","5":"15842","creation_date":"1307621099","6":"1307621099"},{"0":"3617","vim_version":"7.0","1":"7.0","script_version":"0.3.0","2":"0.3.0","version_comment":"New in version 0.3.0:\r\n\r\n* Allow the user to set a default match function in their .vimrc\r\n* Suggestions can now be cycled through","3":"New in version 0.3.0:\r\n\r\n* Allow the user to set a default match function in their .vimrc\r\n* Suggestions can now be cycled through","package":"quicksilver.vim","4":"quicksilver.vim","src_id":"15838","5":"15838","creation_date":"1307531766","6":"1307531766"},{"0":"3617","vim_version":"7.0","1":"7.0","script_version":"0.2.7","2":"0.2.7","version_comment":"Version 0.2.7:\r\n\r\n* Allow the user to set a default match function in their vimrc. ","3":"Version 0.2.7:\r\n\r\n* Allow the user to set a default match function in their vimrc. ","package":"quicksilver.vim","4":"quicksilver.vim","src_id":"15826","5":"15826","creation_date":"1307375228","6":"1307375228"},{"0":"3617","vim_version":"7.0","1":"7.0","script_version":"0.2.6","2":"0.2.6","version_comment":"Initial upload","3":"Initial upload","package":"quicksilver.vim","4":"quicksilver.vim","src_id":"15822","5":"15822","creation_date":"1307365082","6":"1307365082"}]},"3616":{"script_id":"3616","0":"3616","script_name":"warez colorscheme","1":"warez colorscheme","script_type":"color scheme","2":"color scheme","summary":"A transformation term >> gui jasonwryan colorscheme with modification","3":"A transformation term >> gui jasonwryan colorscheme with modification","description":"Inspired by jasonwryan colorscheme for terminal 256 colors and other stuff.\r\n\r\nfollow the repository here : https:\/\/github.com\/Fl4t\/warez-colorscheme\r\n\r\nscreenshot : http:\/\/pix.toile-libre.org\/?img=1307275050.png","4":"Inspired by jasonwryan colorscheme for terminal 256 colors and other stuff.\r\n\r\nfollow the repository here : https:\/\/github.com\/Fl4t\/warez-colorscheme\r\n\r\nscreenshot : http:\/\/pix.toile-libre.org\/?img=1307275050.png","install_details":"","5":"","first_name":"julien","6":"julien","last_name":"stechele","7":"stechele","releases":[{"0":"3616","vim_version":"7.0","1":"7.0","script_version":"1.2","2":"1.2","version_comment":"Change highlight search, normal fg, bg, and other stuff.","3":"Change highlight search, normal fg, bg, and other stuff.","package":"warez.vim","4":"warez.vim","src_id":"16063","5":"16063","creation_date":"1310250121","6":"1310250121"},{"0":"3616","vim_version":"7.0","1":"7.0","script_version":"1.1","2":"1.1","version_comment":"Some update","3":"Some update","package":"warez.vim","4":"warez.vim","src_id":"15930","5":"15930","creation_date":"1308396566","6":"1308396566"},{"0":"3616","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"warez.vim","4":"warez.vim","src_id":"15815","5":"15815","creation_date":"1307275199","6":"1307275199"}]},"3615":{"script_id":"3615","0":"3615","script_name":"ShowMarks7","1":"ShowMarks7","script_type":"utility","2":"utility","summary":"apply a patch for orgin ShowMarks(152)","3":"apply a patch for orgin ShowMarks(152)","description":"I like the ShowMarks plugin vimscript #152 ,but he has some bug in Vim 7,so I patch and upload it.","4":"I like the ShowMarks plugin vimscript #152 ,but he has some bug in Vim 7,so I patch and upload it.","install_details":"like origin ShowMarks plugin , just copt it into your $HOME\/.vim or $HOME\\vimfiles folder.\r\n ","5":"like origin ShowMarks plugin , just copt it into your $HOME\/.vim or $HOME\\vimfiles folder.\r\n ","first_name":"bai","6":"bai","last_name":"liangcn","7":"liangcn","releases":[{"0":"3615","vim_version":"7.0","1":"7.0","script_version":"2.3","2":"2.3","version_comment":"Initial upload","3":"Initial upload","package":"showmarks.vim","4":"showmarks.vim","src_id":"15807","5":"15807","creation_date":"1307168962","6":"1307168962"}]},"3614":{"script_id":"3614","0":"3614","script_name":"vimshell-ssh","1":"vimshell-ssh","script_type":"ftplugin","2":"ftplugin","summary":"You can run Vim over ssh on Vim!","3":"You can run Vim over ssh on Vim!","description":"A vimshell plugin that enables you to use \"vim\" command over ssh on vimshell.\n\nSee the detail below.\nhttps:\/\/github.com\/ujihisa\/vimshell-ssh\n","4":"A vimshell plugin that enables you to use \"vim\" command over ssh on vimshell.\n\nSee the detail below.\nhttps:\/\/github.com\/ujihisa\/vimshell-ssh\n","install_details":"After you install Shougo's vimshell and its dependencies, unarchive the tgz file into a directory that is under &rtp of your Vim, including ~\/.vim dir.\n","5":"After you install Shougo's vimshell and its dependencies, unarchive the tgz file into a directory that is under &rtp of your Vim, including ~\/.vim dir.\n","first_name":"ujihisa","6":"ujihisa","last_name":".","7":".","releases":[{"0":"3614","vim_version":"7.3","1":"7.3","script_version":"2.1","2":"2.1","version_comment":"* Bugfix and catching up the latest vimshell\n","3":"* Bugfix and catching up the latest vimshell\n","package":"vimshell-ssh-2.1.tgz","4":"vimshell-ssh-2.1.tgz","src_id":"16702","5":"16702","creation_date":"1318984847","6":"1318984847"},{"0":"3614","vim_version":"7.3","1":"7.3","script_version":"2.0","2":"2.0","version_comment":"* NeoComplCache integration: remote filename completion\n","3":"* NeoComplCache integration: remote filename completion\n","package":"vimshell-ssh-2.0.tgz","4":"vimshell-ssh-2.0.tgz","src_id":"16430","5":"16430","creation_date":"1314920731","6":"1314920731"},{"0":"3614","vim_version":"7.3","1":"7.3","script_version":"1.1","2":"1.1","version_comment":"* Follows changes in vimshell core\n* Supports empty file name to open the directory\n","3":"* Follows changes in vimshell core\n* Supports empty file name to open the directory\n","package":"vimshell-ssh-1.1.tgz","4":"vimshell-ssh-1.1.tgz","src_id":"16108","5":"16108","creation_date":"1311187496","6":"1311187496"},{"0":"3614","vim_version":"7.3","1":"7.3","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"vimshell-ssh-1.0.tgz","4":"vimshell-ssh-1.0.tgz","src_id":"15805","5":"15805","creation_date":"1307144603","6":"1307144603"}]},"3613":{"script_id":"3613","0":"3613","script_name":"splitjoin.vim","1":"splitjoin.vim","script_type":"utility","2":"utility","summary":"A plugin that helps with switching between single-line and multiline code","3":"A plugin that helps with switching between single-line and multiline code","description":"Github repo is at https:\/\/github.com\/AndrewRadev\/splitjoin.vim\r\n\r\nThis plugin is meant to simplify a task I've found too common in my workflow: switching between a single-line statement and a multi-line one.\r\n\r\nI usually work with ruby and a lot of expressions can be written very concisely on a single line. A good example is the \"if\" statement:\r\n\r\n    puts \"foo\" if bar?\r\n\r\nThis is a great feature of the language, but when you need to add more statements to the body of the \"if\", you need to rewrite it:\r\n\r\n    if bar?\r\n      puts \"foo\"\r\n      puts \"baz\"\r\n    end\r\n\r\nThe idea of this plugin is to introduce a single key binding for transforming a line like this:\r\n\r\n    <div id=\"foo\">bar<\/div>\r\n\r\nInto this:\r\n\r\n    <div id=\"foo\">\r\n      bar\r\n    <\/div>\r\n\r\nAnd another binding for the opposite transformation.\r\n\r\nThis currently works for various constructs in the following languages:\r\n\r\n- C\r\n- CSS\r\n- Coffeescript\r\n- Elixir\r\n- Eruby\r\n- Go\r\n- HAML\r\n- HTML (and HTML-like markup)\r\n- Handlebars\r\n- Javascript (within JSX, TSX, Vue.js templates as well)\r\n- Lua\r\n- PHP\r\n- Perl\r\n- Python\r\n- Ruby\r\n- Rust\r\n- SCSS and Less\r\n- Shell (sh, bash, zsh)\r\n- Tex\r\n- Vimscript\r\n- YAML\r\n\r\nFor more information, including examples for all of those languages, try `:help\r\nsplitjoin`, or take a look at the full help file online at https:\/\/github.com\/AndrewRadev\/splitjoin.vim\/blob\/master\/doc\/splitjoin.txt\r\n\r\nIf you encounter any bugs or have an idea for a new feature, the issue tracker is on github, at https:\/\/github.com\/AndrewRadev\/splitjoin.vim\/issues.\r\n","4":"Github repo is at https:\/\/github.com\/AndrewRadev\/splitjoin.vim\r\n\r\nThis plugin is meant to simplify a task I've found too common in my workflow: switching between a single-line statement and a multi-line one.\r\n\r\nI usually work with ruby and a lot of expressions can be written very concisely on a single line. A good example is the \"if\" statement:\r\n\r\n    puts \"foo\" if bar?\r\n\r\nThis is a great feature of the language, but when you need to add more statements to the body of the \"if\", you need to rewrite it:\r\n\r\n    if bar?\r\n      puts \"foo\"\r\n      puts \"baz\"\r\n    end\r\n\r\nThe idea of this plugin is to introduce a single key binding for transforming a line like this:\r\n\r\n    <div id=\"foo\">bar<\/div>\r\n\r\nInto this:\r\n\r\n    <div id=\"foo\">\r\n      bar\r\n    <\/div>\r\n\r\nAnd another binding for the opposite transformation.\r\n\r\nThis currently works for various constructs in the following languages:\r\n\r\n- C\r\n- CSS\r\n- Coffeescript\r\n- Elixir\r\n- Eruby\r\n- Go\r\n- HAML\r\n- HTML (and HTML-like markup)\r\n- Handlebars\r\n- Javascript (within JSX, TSX, Vue.js templates as well)\r\n- Lua\r\n- PHP\r\n- Perl\r\n- Python\r\n- Ruby\r\n- Rust\r\n- SCSS and Less\r\n- Shell (sh, bash, zsh)\r\n- Tex\r\n- Vimscript\r\n- YAML\r\n\r\nFor more information, including examples for all of those languages, try `:help\r\nsplitjoin`, or take a look at the full help file online at https:\/\/github.com\/AndrewRadev\/splitjoin.vim\/blob\/master\/doc\/splitjoin.txt\r\n\r\nIf you encounter any bugs or have an idea for a new feature, the issue tracker is on github, at https:\/\/github.com\/AndrewRadev\/splitjoin.vim\/issues.\r\n","install_details":"Download splitjoin.zip.\r\n\r\nIf you're using pathogen (vimscript #2332), extract it to a directory in your bundles or just clone the git repository at https:\/\/github.com\/AndrewRadev\/splitjoin.vim\r\n\r\nAlternatively, extract it to your vimfiles root (~\/.vim on *nix, ~\/vimfiles on Windows).","5":"Download splitjoin.zip.\r\n\r\nIf you're using pathogen (vimscript #2332), extract it to a directory in your bundles or just clone the git repository at https:\/\/github.com\/AndrewRadev\/splitjoin.vim\r\n\r\nAlternatively, extract it to your vimfiles root (~\/.vim on *nix, ~\/vimfiles on Windows).","first_name":"Andrew","6":"Andrew","last_name":"Radev","7":"Radev","releases":[{"0":"3613","vim_version":"7.4","1":"7.4","script_version":"v1.2.0","2":"v1.2.0","version_comment":"- Better go support for splitting variables and imports\r\n- Rust support for splitting function calls\r\n- Various bugfixes\r\n","3":"- Better go support for splitting variables and imports\r\n- Rust support for splitting function calls\r\n- Various bugfixes\r\n","package":"splitjoin.zip","4":"splitjoin.zip","src_id":"28507","5":"28507","creation_date":"1687824354","6":"1687824354"},{"0":"3613","vim_version":"7.4","1":"7.4","script_version":"1.1.0","2":"1.1.0","version_comment":"- New integrations: Elm, Clojure, R, Java\r\n- Improvements to support for: YAML, Elixir, Rust, Go, JSX, Ruby\r\n- Filetypes that delegate to existing support: svelte, javascriptreact, typescriptreact\r\n- Various fixes and smaller improvements","3":"- New integrations: Elm, Clojure, R, Java\r\n- Improvements to support for: YAML, Elixir, Rust, Go, JSX, Ruby\r\n- Filetypes that delegate to existing support: svelte, javascriptreact, typescriptreact\r\n- Various fixes and smaller improvements","package":"splitjoin.zip","4":"splitjoin.zip","src_id":"27976","5":"27976","creation_date":"1649028294","6":"1649028294"},{"0":"3613","vim_version":"7.0","1":"7.0","script_version":"1.0.0","2":"1.0.0","version_comment":"- (Additional) support for: C#, Rust, SCSS\/Less, Handlebars, PHP, Go\r\n- Lots of bugfixes\r\n- Documentation improvements","3":"- (Additional) support for: C#, Rust, SCSS\/Less, Handlebars, PHP, Go\r\n- Lots of bugfixes\r\n- Documentation improvements","package":"splitjoin.zip","4":"splitjoin.zip","src_id":"26872","5":"26872","creation_date":"1577131618","6":"1577131618"},{"0":"3613","vim_version":"7.0","1":"7.0","script_version":"0.8.0","2":"0.8.0","version_comment":"- Ruby case statements\r\n- PHP arrays\r\n- LaTeX begin-end blocks\r\n- Perl hashes\r\n- Go imports\r\n- C if-clauses, function calls\r\n- HTML attributes\r\n- Javascript function arguments\r\n- Various fixes","3":"- Ruby case statements\r\n- PHP arrays\r\n- LaTeX begin-end blocks\r\n- Perl hashes\r\n- Go imports\r\n- C if-clauses, function calls\r\n- HTML attributes\r\n- Javascript function arguments\r\n- Various fixes","package":"splitjoin.zip","4":"splitjoin.zip","src_id":"22833","5":"22833","creation_date":"1422351106","6":"1422351106"},{"0":"3613","vim_version":"7.0","1":"7.0","script_version":"0.7.0","2":"0.7.0","version_comment":"- Lua tables\r\n- YAML maps\r\n- Go support\r\n- Simple bash support (semicolons)\r\n- Various bugfixes","3":"- Lua tables\r\n- YAML maps\r\n- Go support\r\n- Simple bash support (semicolons)\r\n- Various bugfixes","package":"splitjoin.zip","4":"splitjoin.zip","src_id":"21342","5":"21342","creation_date":"1390067769","6":"1390067769"},{"0":"3613","vim_version":"7.0","1":"7.0","script_version":"0.6.0","2":"0.6.0","version_comment":"- Default mappings: gJ and gS\r\n- Python lists, tuples, imports\r\n- Ruby heredocs\r\n- HTML tags in PHP code\r\n- Various bugfixes","3":"- Default mappings: gJ and gS\r\n- Python lists, tuples, imports\r\n- Ruby heredocs\r\n- HTML tags in PHP code\r\n- Various bugfixes","package":"splitjoin.zip","4":"splitjoin.zip","src_id":"18990","5":"18990","creation_date":"1353242635","6":"1353242635"},{"0":"3613","vim_version":"7.0","1":"7.0","script_version":"0.5.2","2":"0.5.2","version_comment":"Various bugfixes","3":"Various bugfixes","package":"splitjoin.zip","4":"splitjoin.zip","src_id":"18263","5":"18263","creation_date":"1342288609","6":"1342288609"},{"0":"3613","vim_version":"7.0","1":"7.0","script_version":"0.5.1","2":"0.5.1","version_comment":"- Split ternary operators in coffeescript\r\n- Perl support\r\n- Various bugfixes","3":"- Split ternary operators in coffeescript\r\n- Perl support\r\n- Various bugfixes","package":"splitjoin.zip","4":"splitjoin.zip","src_id":"18028","5":"18028","creation_date":"1337859816","6":"1337859816"},{"0":"3613","vim_version":"7.0","1":"7.0","script_version":"0.5.0","2":"0.5.0","version_comment":"Initial PHP support, thanks to Giuseppe Rota (https:\/\/github.com\/grota)","3":"Initial PHP support, thanks to Giuseppe Rota (https:\/\/github.com\/grota)","package":"splitjoin.zip","4":"splitjoin.zip","src_id":"17742","5":"17742","creation_date":"1333951842","6":"1333951842"},{"0":"3613","vim_version":"7.0","1":"7.0","script_version":"0.4.2","2":"0.4.2","version_comment":"Support for multiline strings in coffeescript","3":"Support for multiline strings in coffeescript","package":"splitjoin.zip","4":"splitjoin.zip","src_id":"17738","5":"17738","creation_date":"1333864971","6":"1333864971"},{"0":"3613","vim_version":"7.0","1":"7.0","script_version":"0.4.1","2":"0.4.1","version_comment":"Fix for small indenting problem with coffeescript.","3":"Fix for small indenting problem with coffeescript.","package":"splitjoin.zip","4":"splitjoin.zip","src_id":"17608","5":"17608","creation_date":"1332076541","6":"1332076541"},{"0":"3613","vim_version":"7.0","1":"7.0","script_version":"0.4.0","2":"0.4.0","version_comment":"- Coffeescript support\r\n- LESS support (same as SCSS)\r\n- Various bugfixes","3":"- Coffeescript support\r\n- LESS support (same as SCSS)\r\n- Various bugfixes","package":"splitjoin.zip","4":"splitjoin.zip","src_id":"17606","5":"17606","creation_date":"1332069943","6":"1332069943"},{"0":"3613","vim_version":"7.0","1":"7.0","script_version":"0.3.0","2":"0.3.0","version_comment":"- Support for ruby 1.9-style hashes\r\n- Vimscript support\r\n- Initial Lua support\r\n- Initial YAML support\r\n- Various bugfixes","3":"- Support for ruby 1.9-style hashes\r\n- Vimscript support\r\n- Initial Lua support\r\n- Initial YAML support\r\n- Various bugfixes","package":"splitjoin.zip","4":"splitjoin.zip","src_id":"16855","5":"16855","creation_date":"1321114731","6":"1321114731"},{"0":"3613","vim_version":"7.0","1":"7.0","script_version":"0.2.2","2":"0.2.2","version_comment":"Bugfix for repeat.vim regression, thanks to kien (https:\/\/github.com\/kien)","3":"Bugfix for repeat.vim regression, thanks to kien (https:\/\/github.com\/kien)","package":"splitjoin.zip","4":"splitjoin.zip","src_id":"16290","5":"16290","creation_date":"1313604701","6":"1313604701"},{"0":"3613","vim_version":"7.0","1":"7.0","script_version":"0.2.1","2":"0.2.1","version_comment":"Bugfix for eruby.","3":"Bugfix for eruby.","package":"splitjoin.zip","4":"splitjoin.zip","src_id":"16206","5":"16206","creation_date":"1312624145","6":"1312624145"},{"0":"3613","vim_version":"7.0","1":"7.0","script_version":"0.2.0","2":"0.2.0","version_comment":"- Javascript support\r\n- Python support\r\n- Option to omit curly braces when splitting ruby option hashes\r\n- Refactoring and various bugfixes","3":"- Javascript support\r\n- Python support\r\n- Option to omit curly braces when splitting ruby option hashes\r\n- Refactoring and various bugfixes","package":"splitjoin.zip","4":"splitjoin.zip","src_id":"16177","5":"16177","creation_date":"1312224720","6":"1312224720"},{"0":"3613","vim_version":"7.0","1":"7.0","script_version":"0.1.3","2":"0.1.3","version_comment":"- Support for auto-aligning ruby hashes and CSS declarations using Tabular (https:\/\/github.com\/godlygeek\/tabular) or Align (vimscript #294)\r\n- Support for repeat.vim (vimscript #2136) thanks to kien (https:\/\/github.com\/kien)\r\n- Various bugfixes\r\n","3":"- Support for auto-aligning ruby hashes and CSS declarations using Tabular (https:\/\/github.com\/godlygeek\/tabular) or Align (vimscript #294)\r\n- Support for repeat.vim (vimscript #2136) thanks to kien (https:\/\/github.com\/kien)\r\n- Various bugfixes\r\n","package":"splitjoin.zip","4":"splitjoin.zip","src_id":"16009","5":"16009","creation_date":"1309428665","6":"1309428665"},{"0":"3613","vim_version":"7.0","1":"7.0","script_version":"0.1.2","2":"0.1.2","version_comment":"- CSS support\r\n- Various bugfixes","3":"- CSS support\r\n- Various bugfixes","package":"splitjoin.zip","4":"splitjoin.zip","src_id":"15931","5":"15931","creation_date":"1308406223","6":"1308406223"},{"0":"3613","vim_version":"7.0","1":"7.0","script_version":"0.1.1","2":"0.1.1","version_comment":"Initial upload","3":"Initial upload","package":"splitjoin.zip","4":"splitjoin.zip","src_id":"15801","5":"15801","creation_date":"1307132110","6":"1307132110"}]},"3612":{"script_id":"3612","0":"3612","script_name":"browsereload-mac.vim","1":"browsereload-mac.vim","script_type":"utility","2":"utility","summary":"vim plugin to reflesh your browser. his plugin works only MacOS.","3":"vim plugin to reflesh your browser. his plugin works only MacOS.","description":"========================\r\nbrowsereload-mac.vim\r\n========================\r\n\r\nDescription\r\n=====================\r\n\r\nvim plugin to reflesh your browser. \r\nthis plugin works only MacOSX.\r\n\r\nRequired\r\n=====================\r\n\r\nosascript(AppleScript command)\r\n\r\nInstallation\r\n=====================\r\n\r\n::\r\n\r\n wget https:\/\/github.com\/tell-k\/vim-browsereload-mac\/tarball\/master -O browsereload-mac-vim.tar.gz\r\n tar xvzf browsereload-mac-vim.tar.gz\r\n mv tell-k-vim-browsereload-mac-* browsereload-mac-vim\r\n cp -pr .\/browsereload-mac-vim\/plugin\/browsereload-mac.vim ~\/.vim\/plugin\/ \r\n\r\nsee also install.sh\r\n\r\nDocumentation(Read The Docs)\r\n==============================\r\n\r\n* https:\/\/browsereload-macvim.readthedocs.org\/en\/latest\/\r\n\r\nNote\r\n=====================\r\n\r\nif you want to reload Firefox. Please change your System Preferences on MacOSX as below.\r\n\r\ncheck \"Enable access for assistive devices\"::\r\n\r\n System Preferences > Universal Access > \"Enable access for assistive devices\"\r\n\r\n\r\nUsage\r\n=====================\r\n\r\nbrowser reload::\r\n\r\n :ChromeReload      \/\/reload \"Google Chrome\"\r\n :FirefoxReload     \/\/reload \"Firefox\"\r\n :SafariReload      \/\/reload \"Safari\"\r\n :OperaReload       \/\/reload \"Opera\"\r\n :AllBrowserReload  \/\/reload all browser\r\n\r\nstart auto reload::\r\n\r\n :ChromeReloadStart  \r\n :FirefoxReloadStart  \r\n :SafariReloadStart  \r\n :OperaReloadStart  \r\n :AllBrowserReloadStart  \r\n\r\nstop auto reload::\r\n\r\n :ChromeReloadStop\r\n :FirefoxReloadStop\r\n :SafariReloadStop\r\n :OperaReloadStop\r\n :AllBrowserReloadStart\r\n\r\n\r\nSettings\r\n=====================\r\n\r\nafter reload browser. forcus \"Terminal\" apps.\r\n\r\nif you want to change fourcus application, \r\nchange variables \"g:returnApps\" to your appliation.\r\n\r\n::\r\n\r\n \"change this variables\r\n let g:returnApp = \"Terminal\" \r\n\r\nif you want to stop returnApp, \r\nchange variables \"g:returnAppFlag\" to 0\r\n\r\n::\r\n\r\n \"default is 1\r\n let g:returnAppFlag = 1\r\n\r\nif you want old style commad, \r\nwrite this setting in your .vimrc\r\n\r\n::\r\n\r\n \"reload\r\n command! -bar Cr silent ChromeReload\r\n command! -bar Fr silent FirefoxReload\r\n command! -bar Sr silent SafariReload\r\n command! -bar Or silent OperaReload\r\n command! -bar Ar silent AllBrowserReload\r\n \"auto reload start\r\n command! -bar CrStart silent ChromeReloadStart\r\n command! -bar FrStart silent FirefoxReloadStart\r\n command! -bar SrStart silent SafariReloadStart\r\n command! -bar OrStart silent OperaReloadStart\r\n command! -bar ArStart silent AllBrowserReloadStart\r\n \"auto reload stop\r\n command! -bar CrStop silent ChromeReloadStop\r\n command! -bar FrStop silent FirefoxReloadStop\r\n command! -bar SrStop silent SafariReloadStop\r\n command! -bar OrStop silent OperaReloadStop\r\n command! -bar ArStop silent AllBrowserReloadStop\r\n\r\nYou can define \"reloadPreHook\" and \"reploadPostHook\" commands.\r\n\r\n::\r\n\r\n \" default is not setting.  \r\n \" 1. execute \"reloadPreHook\" command. -> 2. refresh browser.\r\n let g:reloadPreHook = \"sh bulid_assets.sh\"\r\n\r\n \" 1. refresh browser. ->  2. execute \"reloadPostHook\" command.\r\n let g:reloadPostHook = \"sh bulid_assets.sh\"\r\n\r\nI recommend that you use along with the `vimproc.vim <https:\/\/github.com\/Shougo\/vimproc.vim>`_. \r\nBecause hook commands to be performed asynchronously.\r\n","4":"========================\r\nbrowsereload-mac.vim\r\n========================\r\n\r\nDescription\r\n=====================\r\n\r\nvim plugin to reflesh your browser. \r\nthis plugin works only MacOSX.\r\n\r\nRequired\r\n=====================\r\n\r\nosascript(AppleScript command)\r\n\r\nInstallation\r\n=====================\r\n\r\n::\r\n\r\n wget https:\/\/github.com\/tell-k\/vim-browsereload-mac\/tarball\/master -O browsereload-mac-vim.tar.gz\r\n tar xvzf browsereload-mac-vim.tar.gz\r\n mv tell-k-vim-browsereload-mac-* browsereload-mac-vim\r\n cp -pr .\/browsereload-mac-vim\/plugin\/browsereload-mac.vim ~\/.vim\/plugin\/ \r\n\r\nsee also install.sh\r\n\r\nDocumentation(Read The Docs)\r\n==============================\r\n\r\n* https:\/\/browsereload-macvim.readthedocs.org\/en\/latest\/\r\n\r\nNote\r\n=====================\r\n\r\nif you want to reload Firefox. Please change your System Preferences on MacOSX as below.\r\n\r\ncheck \"Enable access for assistive devices\"::\r\n\r\n System Preferences > Universal Access > \"Enable access for assistive devices\"\r\n\r\n\r\nUsage\r\n=====================\r\n\r\nbrowser reload::\r\n\r\n :ChromeReload      \/\/reload \"Google Chrome\"\r\n :FirefoxReload     \/\/reload \"Firefox\"\r\n :SafariReload      \/\/reload \"Safari\"\r\n :OperaReload       \/\/reload \"Opera\"\r\n :AllBrowserReload  \/\/reload all browser\r\n\r\nstart auto reload::\r\n\r\n :ChromeReloadStart  \r\n :FirefoxReloadStart  \r\n :SafariReloadStart  \r\n :OperaReloadStart  \r\n :AllBrowserReloadStart  \r\n\r\nstop auto reload::\r\n\r\n :ChromeReloadStop\r\n :FirefoxReloadStop\r\n :SafariReloadStop\r\n :OperaReloadStop\r\n :AllBrowserReloadStart\r\n\r\n\r\nSettings\r\n=====================\r\n\r\nafter reload browser. forcus \"Terminal\" apps.\r\n\r\nif you want to change fourcus application, \r\nchange variables \"g:returnApps\" to your appliation.\r\n\r\n::\r\n\r\n \"change this variables\r\n let g:returnApp = \"Terminal\" \r\n\r\nif you want to stop returnApp, \r\nchange variables \"g:returnAppFlag\" to 0\r\n\r\n::\r\n\r\n \"default is 1\r\n let g:returnAppFlag = 1\r\n\r\nif you want old style commad, \r\nwrite this setting in your .vimrc\r\n\r\n::\r\n\r\n \"reload\r\n command! -bar Cr silent ChromeReload\r\n command! -bar Fr silent FirefoxReload\r\n command! -bar Sr silent SafariReload\r\n command! -bar Or silent OperaReload\r\n command! -bar Ar silent AllBrowserReload\r\n \"auto reload start\r\n command! -bar CrStart silent ChromeReloadStart\r\n command! -bar FrStart silent FirefoxReloadStart\r\n command! -bar SrStart silent SafariReloadStart\r\n command! -bar OrStart silent OperaReloadStart\r\n command! -bar ArStart silent AllBrowserReloadStart\r\n \"auto reload stop\r\n command! -bar CrStop silent ChromeReloadStop\r\n command! -bar FrStop silent FirefoxReloadStop\r\n command! -bar SrStop silent SafariReloadStop\r\n command! -bar OrStop silent OperaReloadStop\r\n command! -bar ArStop silent AllBrowserReloadStop\r\n\r\nYou can define \"reloadPreHook\" and \"reploadPostHook\" commands.\r\n\r\n::\r\n\r\n \" default is not setting.  \r\n \" 1. execute \"reloadPreHook\" command. -> 2. refresh browser.\r\n let g:reloadPreHook = \"sh bulid_assets.sh\"\r\n\r\n \" 1. refresh browser. ->  2. execute \"reloadPostHook\" command.\r\n let g:reloadPostHook = \"sh bulid_assets.sh\"\r\n\r\nI recommend that you use along with the `vimproc.vim <https:\/\/github.com\/Shougo\/vimproc.vim>`_. \r\nBecause hook commands to be performed asynchronously.\r\n","install_details":"","5":"","first_name":"tell","6":"tell","last_name":"k","7":"k","releases":[{"0":"3612","vim_version":"7.2","1":"7.2","script_version":"1.1.0","2":"1.1.0","version_comment":"add \"reloadPreHook\", \"reloadPostHook\" options.","3":"add \"reloadPreHook\", \"reloadPostHook\" options.","package":"browsereload-mac-v1.1.0.zip","4":"browsereload-mac-v1.1.0.zip","src_id":"20453","5":"20453","creation_date":"1372415591","6":"1372415591"},{"0":"3612","vim_version":"7.2","1":"7.2","script_version":"1.0.1","2":"1.0.1","version_comment":"change reload command name. and add optional setting \"returnAppFlag\"","3":"change reload command name. and add optional setting \"returnAppFlag\"","package":"browsereload-mac-v1.0.1.zip","4":"browsereload-mac-v1.0.1.zip","src_id":"15800","5":"15800","creation_date":"1307113122","6":"1307113122"},{"0":"3612","vim_version":"7.2","1":"7.2","script_version":"1.0.0","2":"1.0.0","version_comment":"first release","3":"first release","package":"browsereload-mac-v1.0.0.zip","4":"browsereload-mac-v1.0.0.zip","src_id":"15789","5":"15789","creation_date":"1306904972","6":"1306904972"}]},"3611":{"script_id":"3611","0":"3611","script_name":"XQuery indent\/omnicomplete\/ftplugin","1":"XQuery indent\/omnicomplete\/ftplugin","script_type":"ftplugin","2":"ftplugin","summary":"XQuery indent\/omnicomplete\/ftplugin","3":"XQuery indent\/omnicomplete\/ftplugin","description":"This plugin configures Vim to be a little more efficient at editing XQuery...!\r\n\r\nIt also sets up Exuberant Ctags for XQuery, since it's not one of the supported languages.\r\n\r\nftplugin\/xquery.vim: \r\n    -Makes keys like gd and<C-]> and i_CTRL-p work better when editing XQuery files by temporarily adding the hyphen - to the 'iskeyword' option\r\n    -Sets options useful when editing XQuery (like 'set comments')\r\n    -Sets a few variables to make matchit.vim and taglist.vim work better with XQuery\r\n    -Comment regions out via surround.vim by visually selecting an area, then pressing Sc\r\n\r\n\r\nxquerycomplete.vim:\r\n    -Completes W3C XQuery 'fn' functions, types and keywords. \r\n    -Also completes any MarkLogic functions I could find at...  http:\/\/developer.marklogic.com\/pubs\/4.1\/apidocs\/All.html\r\n\r\n        Examples:\r\n\r\n            fn<CTRL-x><CTRL-o>\r\n               ->  list of functions in the 'fn' namespace\r\n\r\n            fn:doc<CTRL-x><CTRL-o>\r\n               ->  fn:doc(\r\n                   fn:doc-available(\r\n                   fn:document-uri(\r\n\r\n            xs<CTRL-x><CTRL-o>\r\n               ->  list of all xquery types\r\n\r\n            decl<CTRL-x><CTRL-o>\r\n               ->  declare\r\n                   declare function\r\n                   declare namespace\r\n                   declare option\r\n                   declare default\r\n\r\n\r\nindent\/xquery.vim:\r\n    - It can recognize complex FLOWR expressions. For example in the example below,\r\n      if in insert mode, hitting enter after the first line will immediately align the cursor with the 'for'.\r\n\r\n      Also,  typing out the 'let' in the fourth line will immediately re-indent the line to align with the 'let' on the first line.\r\n\r\n\r\n             let $foo := for $editor in $editors\r\n                              where not(contains($editor, \"emacs\"))\r\n                              return $editor\r\n             let $bar := \"bar\"\r\n             return\r\n                   $bar\r\n\r\n         \r\n","4":"This plugin configures Vim to be a little more efficient at editing XQuery...!\r\n\r\nIt also sets up Exuberant Ctags for XQuery, since it's not one of the supported languages.\r\n\r\nftplugin\/xquery.vim: \r\n    -Makes keys like gd and<C-]> and i_CTRL-p work better when editing XQuery files by temporarily adding the hyphen - to the 'iskeyword' option\r\n    -Sets options useful when editing XQuery (like 'set comments')\r\n    -Sets a few variables to make matchit.vim and taglist.vim work better with XQuery\r\n    -Comment regions out via surround.vim by visually selecting an area, then pressing Sc\r\n\r\n\r\nxquerycomplete.vim:\r\n    -Completes W3C XQuery 'fn' functions, types and keywords. \r\n    -Also completes any MarkLogic functions I could find at...  http:\/\/developer.marklogic.com\/pubs\/4.1\/apidocs\/All.html\r\n\r\n        Examples:\r\n\r\n            fn<CTRL-x><CTRL-o>\r\n               ->  list of functions in the 'fn' namespace\r\n\r\n            fn:doc<CTRL-x><CTRL-o>\r\n               ->  fn:doc(\r\n                   fn:doc-available(\r\n                   fn:document-uri(\r\n\r\n            xs<CTRL-x><CTRL-o>\r\n               ->  list of all xquery types\r\n\r\n            decl<CTRL-x><CTRL-o>\r\n               ->  declare\r\n                   declare function\r\n                   declare namespace\r\n                   declare option\r\n                   declare default\r\n\r\n\r\nindent\/xquery.vim:\r\n    - It can recognize complex FLOWR expressions. For example in the example below,\r\n      if in insert mode, hitting enter after the first line will immediately align the cursor with the 'for'.\r\n\r\n      Also,  typing out the 'let' in the fourth line will immediately re-indent the line to align with the 'let' on the first line.\r\n\r\n\r\n             let $foo := for $editor in $editors\r\n                              where not(contains($editor, \"emacs\"))\r\n                              return $editor\r\n             let $bar := \"bar\"\r\n             return\r\n                   $bar\r\n\r\n         \r\n","install_details":"  1.  Copy ftplugin\/xquery.vim to $HOME\/.vim\/ftplugin or $HOME\/vimfiles\/ftplugin or $VIM\/vimfiles\/ftplugin (and set 'filetype plugin on')\r\n  2.  Copy autoload\/xquerycomplete.vim to $HOME\/.vim\/autoload or $HOME\/vimfiles\/autoload or $VIM\/vimfiles\/autoload\r\n  3.  Copy indent\/xquery.vim to $HOME\/.vim\/indent\/ or $HOME\/vimfiles\/indent or $VIM\/vimfiles\/indent   (and set 'filetype indent on').   \r\n  4.  Copy _ctags to $HOME\/.ctags (or one of the alternatives at http:\/\/ctags.sourceforge.net\/ctags.html#FILES)\r\n  5.  Download Exuberant Ctags and put it on your path.  Use 'ctags -R' to build a tags file for your XQuery source folder   \r\n\r\nThe steps are mostly optional, so if you don't want automatic indentation for instance, you can just skip step #3.","5":"  1.  Copy ftplugin\/xquery.vim to $HOME\/.vim\/ftplugin or $HOME\/vimfiles\/ftplugin or $VIM\/vimfiles\/ftplugin (and set 'filetype plugin on')\r\n  2.  Copy autoload\/xquerycomplete.vim to $HOME\/.vim\/autoload or $HOME\/vimfiles\/autoload or $VIM\/vimfiles\/autoload\r\n  3.  Copy indent\/xquery.vim to $HOME\/.vim\/indent\/ or $HOME\/vimfiles\/indent or $VIM\/vimfiles\/indent   (and set 'filetype indent on').   \r\n  4.  Copy _ctags to $HOME\/.ctags (or one of the alternatives at http:\/\/ctags.sourceforge.net\/ctags.html#FILES)\r\n  5.  Download Exuberant Ctags and put it on your path.  Use 'ctags -R' to build a tags file for your XQuery source folder   \r\n\r\nThe steps are mostly optional, so if you don't want automatic indentation for instance, you can just skip step #3.","first_name":"David","6":"David","last_name":"Lam","7":"Lam","releases":[{"0":"3611","vim_version":"8.0","1":"8.0","script_version":"1.2.1","2":"1.2.1","version_comment":"fix compatibility with Vim 8.0","3":"fix compatibility with Vim 8.0","package":"xqueryvim.zip","4":"xqueryvim.zip","src_id":"27082","5":"27082","creation_date":"1584514259","6":"1584514259"},{"0":"3611","vim_version":"7.0","1":"7.0","script_version":"1.2","2":"1.2","version_comment":"updated with functx and new marklogic 5 functions\r\n\r\npatch from Steve Spigarelli","3":"updated with functx and new marklogic 5 functions\r\n\r\npatch from Steve Spigarelli","package":"xqueryvim.zip","4":"xqueryvim.zip","src_id":"18221","5":"18221","creation_date":"1341455730","6":"1341455730"},{"0":"3611","vim_version":"7.2","1":"7.2","script_version":"1.1.1","2":"1.1.1","version_comment":"Same as 1.1, but with a extra \/indent\/test\/xquery.vim that has 'echomsg' debug prints in it.  (Use :mesg to view the log after indenting stuff)","3":"Same as 1.1, but with a extra \/indent\/test\/xquery.vim that has 'echomsg' debug prints in it.  (Use :mesg to view the log after indenting stuff)","package":"xqueryvim.zip","4":"xqueryvim.zip","src_id":"16794","5":"16794","creation_date":"1320297545","6":"1320297545"},{"0":"3611","vim_version":"7.2","1":"7.2","script_version":"1.1","2":"1.1","version_comment":"Cleaned up some debugging prints... and wrote some documentation","3":"Cleaned up some debugging prints... and wrote some documentation","package":"xqueryvim.zip","4":"xqueryvim.zip","src_id":"15819","5":"15819","creation_date":"1307338362","6":"1307338362"},{"0":"3611","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"xqueryvim.zip","4":"xqueryvim.zip","src_id":"15775","5":"15775","creation_date":"1306830532","6":"1306830532"}]},"3610":{"script_id":"3610","0":"3610","script_name":"operator-star","1":"operator-star","script_type":"utility","2":"utility","summary":"This plugin provides the operator versions of |star|, |gstar|, |#|, |g#|.","3":"This plugin provides the operator versions of |star|, |gstar|, |#|, |g#|.","description":"\r\nINTRODUCTION\r\n\r\nThis plugin provides the operator versions\r\nof *, g*, #, g#. star is * (:help star).\r\n\r\nNo default keymappings, so please map to\r\nyour favorite keymappings like the followings:\r\n\r\n    nmap <Leader>*  <Plug>(operator-*)\r\n    nmap <Leader>g* <Plug>(operator-g*)\r\n    nmap <Leader>#  <Plug>(operator-#)\r\n    nmap <Leader>g# <Plug>(operator-g#)\r\n\r\n\r\nThis plugin has two dependency plugins.\r\n\r\n- visualstar (vimscript#2944)\r\n- operator-user (vimscript#2692)\r\n\r\n\r\nUSAGE EXAMPLE\r\n\r\n- <Leader>*iw or viw<Leader>* is the same as *. it's no use in this case :(\r\n- <Leader>*<Leader>* to search the same line as the cursor line.\r\n- <Leader>*iW to search the WORD under the cursor.\r\n- or you can even combine with another useful text-object plugins like these:\r\nhttp:\/\/www.google.com\/cse?cx=partner-pub-3005259998294962%3Abvyni59kjr1&ie=ISO-8859-1&q=textobj&sa=Search&siteurl=www.vim.org%2F\r\n\r\n* is almost the same as \/<C-r>=expand('<cword>')<CR> .\r\n\/ is very handy moving command.\r\n* is also handy shortcut for \/ command.\r\noperator-star strongly helps you to move around quickly in the source code, text, etc.","4":"\r\nINTRODUCTION\r\n\r\nThis plugin provides the operator versions\r\nof *, g*, #, g#. star is * (:help star).\r\n\r\nNo default keymappings, so please map to\r\nyour favorite keymappings like the followings:\r\n\r\n    nmap <Leader>*  <Plug>(operator-*)\r\n    nmap <Leader>g* <Plug>(operator-g*)\r\n    nmap <Leader>#  <Plug>(operator-#)\r\n    nmap <Leader>g# <Plug>(operator-g#)\r\n\r\n\r\nThis plugin has two dependency plugins.\r\n\r\n- visualstar (vimscript#2944)\r\n- operator-user (vimscript#2692)\r\n\r\n\r\nUSAGE EXAMPLE\r\n\r\n- <Leader>*iw or viw<Leader>* is the same as *. it's no use in this case :(\r\n- <Leader>*<Leader>* to search the same line as the cursor line.\r\n- <Leader>*iW to search the WORD under the cursor.\r\n- or you can even combine with another useful text-object plugins like these:\r\nhttp:\/\/www.google.com\/cse?cx=partner-pub-3005259998294962%3Abvyni59kjr1&ie=ISO-8859-1&q=textobj&sa=Search&siteurl=www.vim.org%2F\r\n\r\n* is almost the same as \/<C-r>=expand('<cword>')<CR> .\r\n\/ is very handy moving command.\r\n* is also handy shortcut for \/ command.\r\noperator-star strongly helps you to move around quickly in the source code, text, etc.","install_details":"","5":"","first_name":"tyru","6":"tyru","last_name":" ","7":" ","releases":[{"0":"3610","vim_version":"7.0","1":"7.0","script_version":"0.0.0","2":"0.0.0","version_comment":"Initial upload","3":"Initial upload","package":"operator-star.zip","4":"operator-star.zip","src_id":"15772","5":"15772","creation_date":"1306826237","6":"1306826237"}]},"3609":{"script_id":"3609","0":"3609","script_name":"IDLE","1":"IDLE","script_type":"color scheme","2":"color scheme","summary":"Python's IDLE like Colorscheme","3":"Python's IDLE like Colorscheme","description":"This colorscheme attempts to replicate Python's IDLE's excellent colorscheme. IDLE users will feel right at home.","4":"This colorscheme attempts to replicate Python's IDLE's excellent colorscheme. IDLE users will feel right at home.","install_details":"Drop into the colors directory.","5":"Drop into the colors directory.","first_name":"Lan","6":"Lan","last_name":"Rogers","7":"Rogers","releases":[{"0":"3609","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"IDLE.vim","4":"IDLE.vim","src_id":"15771","5":"15771","creation_date":"1306816045","6":"1306816045"}]},"3608":{"script_id":"3608","0":"3608","script_name":"nautilus-py-vim","1":"nautilus-py-vim","script_type":"utility","2":"utility","summary":"Edit with Vim in Nautilus","3":"Edit with Vim in Nautilus","description":"****NOTE: THIS PAGE IS OUTDATED. PLEASE VISIT http:\/\/nautilusvim.topbug.net\/****\r\n\r\nThis script was written for Nautilus 2. I never had a chance to test it under Nautilus 3, so I'm not sure whether it will work.\r\n\r\nHomepage and screenshots: http:\/\/nautilusvim.topbug.net\/\r\n\r\n\r\n1. Overview\r\n\r\nnautilus-py-vim is an extension for nautilus, the GNOME file manager, and is\r\nwritten in python. This extension adds several menu items in the nautilus\r\nright-click context menu for gvim, just like gVim on Windows.\r\n\r\n2. Install\r\n\r\nTo install this extension, first make sure that you have installed the\r\nnautilus python extension(http:\/\/projects.gnome.org\/nautilus-python):\r\nOn Fedora:          # yum install nautilus-python\r\nOn Debian\/Ubuntu:   # apt-get install python-nautilus\r\n\r\nIf you want to enable the \"Edit with gVim as Root\" menu item, you should\r\ninstall gksu(http:\/\/www.nongnu.org\/gksu),\r\nbeesu(http:\/\/honeybeenet.altervista.org\/beesu) or\r\nkdesu(http:\/\/techbase.kde.org\/Projects\/kdesu):\r\n\r\nOn Fedora:          # yum install beesu\r\nOn Debian\/Ubuntu:   # apt-get install gksu\r\n\r\nAfter that, just run \"install.sh\":\r\n\r\n$ .\/install.sh\r\n\r\nThe above command would make this extension available to you only, not other\r\nusers. If you want every user on the machine could use this extension, run the\r\ninstall.sh with root privilege:\r\n\r\n# .\/install.sh\r\n\r\nIf you encounter any problem when executing the command above, try to execute\r\n\"bash install.sh\" or \"ksh install.sh\".\r\n\r\nThen restart nautilus(execute \"nautilus -q\") and try to right click on the\r\nfile(s) you want to edit, you will see the changes in the context menu(\"Edit\r\nwith gVim\" when only one file is selected, and \"Diff with gVim\", \"Edit with\r\nMulti gVim\", \"Edit with a Single gVim\" are present when several files are\r\nselected), just like what it is like on Windows.\r\n\r\n3. Configuration\r\n\r\nTo configure the extension, you could write a config file. nautilus-py-vim\r\nwill search the config file in the order of the following files:\r\n\r\n~\/.nautilusvim.conf\r\n~\/.nautilus\/nautilusvim.conf\r\n\/etc\/nautilusvim.conf\r\n\r\nFor the content of the config file, you could take a look at the\r\n\"example.conf\".\r\n\r\nIf none of the configuration files are found, nautilus-py-vim will use default\r\nvalues.\r\n\r\n4. Uninstall\r\n\r\nRun the uninstall shell script.\r\n\r\n\r\nRepository: https:\/\/github.com\/xuhdev\/nautilus-py-vim\r\n","4":"****NOTE: THIS PAGE IS OUTDATED. PLEASE VISIT http:\/\/nautilusvim.topbug.net\/****\r\n\r\nThis script was written for Nautilus 2. I never had a chance to test it under Nautilus 3, so I'm not sure whether it will work.\r\n\r\nHomepage and screenshots: http:\/\/nautilusvim.topbug.net\/\r\n\r\n\r\n1. Overview\r\n\r\nnautilus-py-vim is an extension for nautilus, the GNOME file manager, and is\r\nwritten in python. This extension adds several menu items in the nautilus\r\nright-click context menu for gvim, just like gVim on Windows.\r\n\r\n2. Install\r\n\r\nTo install this extension, first make sure that you have installed the\r\nnautilus python extension(http:\/\/projects.gnome.org\/nautilus-python):\r\nOn Fedora:          # yum install nautilus-python\r\nOn Debian\/Ubuntu:   # apt-get install python-nautilus\r\n\r\nIf you want to enable the \"Edit with gVim as Root\" menu item, you should\r\ninstall gksu(http:\/\/www.nongnu.org\/gksu),\r\nbeesu(http:\/\/honeybeenet.altervista.org\/beesu) or\r\nkdesu(http:\/\/techbase.kde.org\/Projects\/kdesu):\r\n\r\nOn Fedora:          # yum install beesu\r\nOn Debian\/Ubuntu:   # apt-get install gksu\r\n\r\nAfter that, just run \"install.sh\":\r\n\r\n$ .\/install.sh\r\n\r\nThe above command would make this extension available to you only, not other\r\nusers. If you want every user on the machine could use this extension, run the\r\ninstall.sh with root privilege:\r\n\r\n# .\/install.sh\r\n\r\nIf you encounter any problem when executing the command above, try to execute\r\n\"bash install.sh\" or \"ksh install.sh\".\r\n\r\nThen restart nautilus(execute \"nautilus -q\") and try to right click on the\r\nfile(s) you want to edit, you will see the changes in the context menu(\"Edit\r\nwith gVim\" when only one file is selected, and \"Diff with gVim\", \"Edit with\r\nMulti gVim\", \"Edit with a Single gVim\" are present when several files are\r\nselected), just like what it is like on Windows.\r\n\r\n3. Configuration\r\n\r\nTo configure the extension, you could write a config file. nautilus-py-vim\r\nwill search the config file in the order of the following files:\r\n\r\n~\/.nautilusvim.conf\r\n~\/.nautilus\/nautilusvim.conf\r\n\/etc\/nautilusvim.conf\r\n\r\nFor the content of the config file, you could take a look at the\r\n\"example.conf\".\r\n\r\nIf none of the configuration files are found, nautilus-py-vim will use default\r\nvalues.\r\n\r\n4. Uninstall\r\n\r\nRun the uninstall shell script.\r\n\r\n\r\nRepository: https:\/\/github.com\/xuhdev\/nautilus-py-vim\r\n","install_details":"See above.","5":"See above.","first_name":"Hong","6":"Hong","last_name":"Xu","7":"Xu","releases":[{"0":"3608","vim_version":"7.0","1":"7.0","script_version":"0.3","2":"0.3","version_comment":"Now \"gvim\" and \"gvimdiff\" commands can be customized;\r\n\"Edit as root\" is now available;\r\nmenu items now can be put into one submenu.","3":"Now \"gvim\" and \"gvimdiff\" commands can be customized;\r\n\"Edit as root\" is now available;\r\nmenu items now can be put into one submenu.","package":"nautilus-py-vim-0.3.tar.gz","4":"nautilus-py-vim-0.3.tar.gz","src_id":"15818","5":"15818","creation_date":"1307334406","6":"1307334406"}]},"3607":{"script_id":"3607","0":"3607","script_name":"vim_django","1":"vim_django","script_type":"utility","2":"utility","summary":"[UNMAINTAINED] Simplifies opening related files in Django projects","3":"[UNMAINTAINED] Simplifies opening related files in Django projects","description":"***THIS SCRIPT IS NOT MAINTAINED, AND PROBABLY BROKEN***\r\n\r\nThis script simplifies opening of related files in Django projects.\r\n\r\nIf you are editing a file in a Django project, vim_django will find the location of your template files and app files. In combination with the Command-T plugin: vimscript #3025, this makes it super-easy to open files related to the one you are currently editing.\r\n\r\nWatch a demo on Viemo: http:\/\/vimeo.com\/24394421 (1:24) (This only shows opening of template files, but files in the app itself can be opened in the same way)\r\n\r\nSuggested mapping:\r\nmap <Leader>dt :VimDjangoCommandTTemplate<CR>\r\nmap <Leader>da :VimDjangoCommandTApp<CR>\r\n\r\nIf you put that line in your .vimrc, hitting \"<Leader>dt\" while working on a Django application will start CommandT in the template directory corresponding to the application. Hitting \"<Leader>da will start CommandT in the app directory. (\"<Leader>\" is usually mapped as \"\\\" or \",\" so try \"\\dt\" or \",dt\".)\r\n\r\nIf you have any questions, please send me an email at anders AT knatten DOT org","4":"***THIS SCRIPT IS NOT MAINTAINED, AND PROBABLY BROKEN***\r\n\r\nThis script simplifies opening of related files in Django projects.\r\n\r\nIf you are editing a file in a Django project, vim_django will find the location of your template files and app files. In combination with the Command-T plugin: vimscript #3025, this makes it super-easy to open files related to the one you are currently editing.\r\n\r\nWatch a demo on Viemo: http:\/\/vimeo.com\/24394421 (1:24) (This only shows opening of template files, but files in the app itself can be opened in the same way)\r\n\r\nSuggested mapping:\r\nmap <Leader>dt :VimDjangoCommandTTemplate<CR>\r\nmap <Leader>da :VimDjangoCommandTApp<CR>\r\n\r\nIf you put that line in your .vimrc, hitting \"<Leader>dt\" while working on a Django application will start CommandT in the template directory corresponding to the application. Hitting \"<Leader>da will start CommandT in the app directory. (\"<Leader>\" is usually mapped as \"\\\" or \",\" so try \"\\dt\" or \",dt\".)\r\n\r\nIf you have any questions, please send me an email at anders AT knatten DOT org","install_details":"***THIS SCRIPT IS NOT MAINTAINED, AND PROBABLY BROKEN***\r\n\r\nUnpack in your .vim directory:\r\n\r\ncd ~\/.vim\r\ntar zxf vim_django-<version>.tgz\r\n\r\nThe result should look like this:\r\n ~\/.vim\/plugin\/vim_django.vim\r\n~\/.vim\/python\/vim_django\/__init__.py\r\n~\/.vim\/python\/vim_django\/test.py\r\n~\/.vim\/python\/vim_django\/vim_django.py\r\n\r\nYou also need to install Command-T: http:\/\/www.vim.org\/scripts\/script.php?script_id=3025\r\n(You can skip this if you don't want Command-T integration, but vim_django is pretty pointless without it. )","5":"***THIS SCRIPT IS NOT MAINTAINED, AND PROBABLY BROKEN***\r\n\r\nUnpack in your .vim directory:\r\n\r\ncd ~\/.vim\r\ntar zxf vim_django-<version>.tgz\r\n\r\nThe result should look like this:\r\n ~\/.vim\/plugin\/vim_django.vim\r\n~\/.vim\/python\/vim_django\/__init__.py\r\n~\/.vim\/python\/vim_django\/test.py\r\n~\/.vim\/python\/vim_django\/vim_django.py\r\n\r\nYou also need to install Command-T: http:\/\/www.vim.org\/scripts\/script.php?script_id=3025\r\n(You can skip this if you don't want Command-T integration, but vim_django is pretty pointless without it. )","first_name":"Anders Schau","6":"Anders Schau","last_name":"Knatten","7":"Knatten","releases":[{"0":"3607","vim_version":"7.0","1":"7.0","script_version":"0.5","2":"0.5","version_comment":"Don't crash if __file__ is used in settings.py\r\nRemove python warning","3":"Don't crash if __file__ is used in settings.py\r\nRemove python warning","package":"vim_django-0.5.tgz","4":"vim_django-0.5.tgz","src_id":"16796","5":"16796","creation_date":"1320352704","6":"1320352704"},{"0":"3607","vim_version":"7.0","1":"7.0","script_version":"0.4","2":"0.4","version_comment":"Now  supports being installed via vundle, thanks to https:\/\/github.com\/Psycojoker","3":"Now  supports being installed via vundle, thanks to https:\/\/github.com\/Psycojoker","package":"vim_django-0.4.tgz","4":"vim_django-0.4.tgz","src_id":"16784","5":"16784","creation_date":"1320228346","6":"1320228346"},{"0":"3607","vim_version":"7.0","1":"7.0","script_version":"0.3","2":"0.3","version_comment":"Improved error handling with improved user feedback.\r\nFixed infinite loop when hitting root directory while looking for a file.\r\n","3":"Improved error handling with improved user feedback.\r\nFixed infinite loop when hitting root directory while looking for a file.\r\n","package":"vim_django-0.3.tgz","4":"vim_django-0.3.tgz","src_id":"16619","5":"16619","creation_date":"1317741815","6":"1317741815"},{"0":"3607","vim_version":"7.0","1":"7.0","script_version":"0.2","2":"0.2","version_comment":"Can now open files in the app directory (like views.py, models.py) in addition to files in template directory.","3":"Can now open files in the app directory (like views.py, models.py) in addition to files in template directory.","package":"vim_django-0.2.tgz","4":"vim_django-0.2.tgz","src_id":"15908","5":"15908","creation_date":"1308252997","6":"1308252997"},{"0":"3607","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"vim_django-0.1.tgz","4":"vim_django-0.1.tgz","src_id":"15757","5":"15757","creation_date":"1306696181","6":"1306696181"}]},"3606":{"script_id":"3606","0":"3606","script_name":"Diablo3","1":"Diablo3","script_type":"color scheme","2":"color scheme","summary":"a dark color scheme for both gui and terminal","3":"a dark color scheme for both gui and terminal","description":"Diablo3 is a color scheme inspired by molokai. It supports both gui and 256-color term.\r\n\r\n=========================================\r\n\r\nScreenshots\r\n\r\ngui: http:\/\/i.imgur.com\/Nxl1F.png\r\n\r\n256-color term (new): http:\/\/i.imgur.com\/9RwJh.png\r\n\r\n256-color term (1.21): http:\/\/i.imgur.com\/HEAKT.png\r\n\r\n=========================================\r\n\r\nOptions:\r\n\r\nIf you want to set long line warning, copy this in your vimrc:\r\n\r\n  let g:diablo3_longline = 1\r\n\r\n\r\nThe default length of a line is 120, you can change it by putting\r\nthe following in your vimrc:\r\n\r\n  let g:diablo3_len = 79\r\n\r\nNotice the length here is the length you want to set plus 1.\r\n\r\n\r\nLinks:\r\n\r\n* Bitbucket: https:\/\/bitbucket.org\/vayn\/colorschemes\r\n\r\n=========================================\r\n\r\n BTW Diablo is my favorite game series :D\r\n","4":"Diablo3 is a color scheme inspired by molokai. It supports both gui and 256-color term.\r\n\r\n=========================================\r\n\r\nScreenshots\r\n\r\ngui: http:\/\/i.imgur.com\/Nxl1F.png\r\n\r\n256-color term (new): http:\/\/i.imgur.com\/9RwJh.png\r\n\r\n256-color term (1.21): http:\/\/i.imgur.com\/HEAKT.png\r\n\r\n=========================================\r\n\r\nOptions:\r\n\r\nIf you want to set long line warning, copy this in your vimrc:\r\n\r\n  let g:diablo3_longline = 1\r\n\r\n\r\nThe default length of a line is 120, you can change it by putting\r\nthe following in your vimrc:\r\n\r\n  let g:diablo3_len = 79\r\n\r\nNotice the length here is the length you want to set plus 1.\r\n\r\n\r\nLinks:\r\n\r\n* Bitbucket: https:\/\/bitbucket.org\/vayn\/colorschemes\r\n\r\n=========================================\r\n\r\n BTW Diablo is my favorite game series :D\r\n","install_details":"Just copy the file to \"~\/.vim\/colors\" or in \"<your vim directory>\\vimfiles\\colors\" on Windows, then write \r\n\r\n>>>\r\n    colorscheme diablo3\r\n<<<\r\n\r\ninto your vimrc file","5":"Just copy the file to \"~\/.vim\/colors\" or in \"<your vim directory>\\vimfiles\\colors\" on Windows, then write \r\n\r\n>>>\r\n    colorscheme diablo3\r\n<<<\r\n\r\ninto your vimrc file","first_name":"Vincent","6":"Vincent","last_name":"T.","7":"T.","releases":[{"0":"3606","vim_version":"7.0","1":"7.0","script_version":"1.6","2":"1.6","version_comment":"* Change term cursor color in insert mode\r\n* Minor adjustment","3":"* Change term cursor color in insert mode\r\n* Minor adjustment","package":"diablo3.vim","4":"diablo3.vim","src_id":"16342","5":"16342","creation_date":"1314204166","6":"1314204166"},{"0":"3606","vim_version":"7.0","1":"7.0","script_version":"1.5","2":"1.5","version_comment":"* Improve some colors for term. All works done by terremoto, thanks.","3":"* Improve some colors for term. All works done by terremoto, thanks.","package":"diablo3.vim","4":"diablo3.vim","src_id":"15890","5":"15890","creation_date":"1308066275","6":"1308066275"},{"0":"3606","vim_version":"7.0","1":"7.0","script_version":"1.41","2":"1.41","version_comment":"* Tweak the bad look of pyflakes in term","3":"* Tweak the bad look of pyflakes in term","package":"diablo3.vim","4":"diablo3.vim","src_id":"15785","5":"15785","creation_date":"1306876679","6":"1306876679"},{"0":"3606","vim_version":"7.0","1":"7.0","script_version":"1.3","2":"1.3","version_comment":"* Totally change term background color and other colors. (See new screenshot of terminal)","3":"* Totally change term background color and other colors. (See new screenshot of terminal)","package":"diablo3.vim","4":"diablo3.vim","src_id":"15778","5":"15778","creation_date":"1306833569","6":"1306833569"},{"0":"3606","vim_version":"7.0","1":"7.0","script_version":"1.21","2":"1.21","version_comment":"* Tweak some color\r\n* Add options for LongLine Warning","3":"* Tweak some color\r\n* Add options for LongLine Warning","package":"diablo3.vim","4":"diablo3.vim","src_id":"15763","5":"15763","creation_date":"1306742921","6":"1306742921"},{"0":"3606","vim_version":"7.0","1":"7.0","script_version":"1.1","2":"1.1","version_comment":"Initial upload","3":"Initial upload","package":"diablo3.vim","4":"diablo3.vim","src_id":"15755","5":"15755","creation_date":"1306683411","6":"1306683411"}]},"3605":{"script_id":"3605","0":"3605","script_name":"listtag","1":"listtag","script_type":"utility","2":"utility","summary":"list all tags and jump to one of your choise","3":"list all tags and jump to one of your choise","description":"Taglist is a useful script for many vim users. But I write programs under the terminal with 80 characters, so if I open the taglist window, the left window become very narrow.\r\n\r\nThis script allow you list all all functions, types, macro definitions in current file with shortcut key, and jump to one of your choise. And you can jump between with .h and .cpp files quickly.\r\n\r\n\" Usage:\r\n\"               <Ctrl-J>    \/* list functions *\/\r\n\"               <Ctrl-P>    \/* list functions prototype *\/\r\n\"               <Ctrl-K>    \/* list types *\/\r\n\"               <Ctrl-N>    \/* list macro definitions *\/\r\n\"               <Ctrl-H>    \/* jump between with .h\/.c files *\/","4":"Taglist is a useful script for many vim users. But I write programs under the terminal with 80 characters, so if I open the taglist window, the left window become very narrow.\r\n\r\nThis script allow you list all all functions, types, macro definitions in current file with shortcut key, and jump to one of your choise. And you can jump between with .h and .cpp files quickly.\r\n\r\n\" Usage:\r\n\"               <Ctrl-J>    \/* list functions *\/\r\n\"               <Ctrl-P>    \/* list functions prototype *\/\r\n\"               <Ctrl-K>    \/* list types *\/\r\n\"               <Ctrl-N>    \/* list macro definitions *\/\r\n\"               <Ctrl-H>    \/* jump between with .h\/.c files *\/","install_details":"Put this script in your ~\/.vim\/plugin directory","5":"Put this script in your ~\/.vim\/plugin directory","first_name":"Fang","6":"Fang","last_name":"xm","7":"xm","releases":[{"0":"3605","vim_version":"7.0","1":"7.0","script_version":"0.01","2":"0.01","version_comment":"Initial upload","3":"Initial upload","package":"listtag.vim","4":"listtag.vim","src_id":"15742","5":"15742","creation_date":"1306481314","6":"1306481314"}]},"3604":{"script_id":"3604","0":"3604","script_name":"nicer-vim-regexps","1":"nicer-vim-regexps","script_type":"syntax","2":"syntax","summary":"Nicer syntax highlighting for vim regexps.","3":"Nicer syntax highlighting for vim regexps.","description":"See http:\/\/www.discontinuously.com\/2011\/05\/nicer-vim-regexps\/","4":"See http:\/\/www.discontinuously.com\/2011\/05\/nicer-vim-regexps\/","install_details":"Extract to your .vim directory.","5":"Extract to your .vim directory.","first_name":"Jezreel","6":"Jezreel","last_name":"Ng","7":"Ng","releases":[{"0":"3604","vim_version":"7.0","1":"7.0","script_version":"1.1","2":"1.1","version_comment":"Update.","3":"Update.","package":"nicer-vim-regexps.zip","4":"nicer-vim-regexps.zip","src_id":"15736","5":"15736","creation_date":"1306399340","6":"1306399340"},{"0":"3604","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"nicer-vim-regexps.zip","4":"nicer-vim-regexps.zip","src_id":"15735","5":"15735","creation_date":"1306397283","6":"1306397283"}]},"3603":{"script_id":"3603","0":"3603","script_name":"calm","1":"calm","script_type":"color scheme","2":"color scheme","summary":"A simple light color scheme","3":"A simple light color scheme","description":"This color scheme that I use for development. The baseline was the theme vylight.","4":"This color scheme that I use for development. The baseline was the theme vylight.","install_details":"","5":"","first_name":"Chikirin","6":"Chikirin","last_name":"","7":"","releases":[{"0":"3603","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"calm.vim","4":"calm.vim","src_id":"15734","5":"15734","creation_date":"1306396185","6":"1306396185"}]},"3602":{"script_id":"3602","0":"3602","script_name":"reorder-columns","1":"reorder-columns","script_type":"utility","2":"utility","summary":"reorder columns.","3":"reorder columns.","description":"reorder columns.\r\nhttps:\/\/github.com\/taku-o\/vim-reorder-columns\r\n\r\ncommand format.\r\n    :[range]ReOrder {split_pattern} {order} [{delimiter}]\r\n\r\n        {split_pattern}         split line with {split_pattern}.\r\n        {order}                 column order.\r\n        {delimiter}             string for join column. if none, use {split_pattern} instead.\r\n\r\ncommand example.\r\n    :%ReOrder , 32451 |\r\n        split line with ','\r\n        order columns, column[3] column[2] column[4] column[5] column[1]\r\n        join columns with delimiter '|'\r\n\r\n        example\r\n            text data.\r\n                one,two,three,four,five\r\n                six,seven,eight,nine,ten\r\n                eleven,twelve,thirteen,fourteen,fifteen\r\n\r\n            command\r\n                :%ReOrder , 32451 |\r\n\r\n            result\r\n                three|two|five|four|one\r\n                eight|seven|ten|nine|six\r\n                thirteen|twelve|fifteen|fourteen|eleven\r\n\r\nusage example.\r\n    --------------------------------------------\r\n    example text data 1.\r\n        one,two,three,four,five\r\n        six,seven,eight,nine,ten\r\n        eleven,twelve,thirteen,fourteen,fifteen\r\n\r\n    usage example 1. re order columns.\r\n        :%ReOrder , 32451\r\n\r\n        three,two,four,five,one\r\n        eight,seven,nine,ten,six\r\n        thirteen,twelve,fourteen,fifteen,eleven\r\n\r\n    usage example 2. remove some columns.\r\n        :%ReOrder , 32\r\n\r\n        three,two\r\n        eight,seven\r\n        thirteen,twelve\r\n\r\n    usage example 3. repeat some columns.\r\n        :%ReOrder , 3233\r\n\r\n        three,two,three,three\r\n        eight,seven,eight,eight\r\n        thirteen,twelve,thirteen,thirteen\r\n\r\n    --------------------------------------------\r\n    example text data 2.\r\n        one two three four five\r\n        six seven eight nine ten\r\n        eleven twelve thirteen fourteen fifteen\r\n\r\n    usage example 4. split with whitespace. sorry, join with whitespace is not supported.\r\n        :%ReOrder \\s\\+ 32451 ,\r\n\r\n        three,two,four,five,one\r\n        eight,seven,nine,ten,six\r\n        thirteen,twelve,fourteen,fifteen,eleven\r\n","4":"reorder columns.\r\nhttps:\/\/github.com\/taku-o\/vim-reorder-columns\r\n\r\ncommand format.\r\n    :[range]ReOrder {split_pattern} {order} [{delimiter}]\r\n\r\n        {split_pattern}         split line with {split_pattern}.\r\n        {order}                 column order.\r\n        {delimiter}             string for join column. if none, use {split_pattern} instead.\r\n\r\ncommand example.\r\n    :%ReOrder , 32451 |\r\n        split line with ','\r\n        order columns, column[3] column[2] column[4] column[5] column[1]\r\n        join columns with delimiter '|'\r\n\r\n        example\r\n            text data.\r\n                one,two,three,four,five\r\n                six,seven,eight,nine,ten\r\n                eleven,twelve,thirteen,fourteen,fifteen\r\n\r\n            command\r\n                :%ReOrder , 32451 |\r\n\r\n            result\r\n                three|two|five|four|one\r\n                eight|seven|ten|nine|six\r\n                thirteen|twelve|fifteen|fourteen|eleven\r\n\r\nusage example.\r\n    --------------------------------------------\r\n    example text data 1.\r\n        one,two,three,four,five\r\n        six,seven,eight,nine,ten\r\n        eleven,twelve,thirteen,fourteen,fifteen\r\n\r\n    usage example 1. re order columns.\r\n        :%ReOrder , 32451\r\n\r\n        three,two,four,five,one\r\n        eight,seven,nine,ten,six\r\n        thirteen,twelve,fourteen,fifteen,eleven\r\n\r\n    usage example 2. remove some columns.\r\n        :%ReOrder , 32\r\n\r\n        three,two\r\n        eight,seven\r\n        thirteen,twelve\r\n\r\n    usage example 3. repeat some columns.\r\n        :%ReOrder , 3233\r\n\r\n        three,two,three,three\r\n        eight,seven,eight,eight\r\n        thirteen,twelve,thirteen,thirteen\r\n\r\n    --------------------------------------------\r\n    example text data 2.\r\n        one two three four five\r\n        six seven eight nine ten\r\n        eleven twelve thirteen fourteen fifteen\r\n\r\n    usage example 4. split with whitespace. sorry, join with whitespace is not supported.\r\n        :%ReOrder \\s\\+ 32451 ,\r\n\r\n        three,two,four,five,one\r\n        eight,seven,nine,ten,six\r\n        thirteen,twelve,fourteen,fifteen,eleven\r\n","install_details":"copy reorder-columns.vim into your plugin directory.","5":"copy reorder-columns.vim into your plugin directory.","first_name":"omi","6":"omi","last_name":"taku","7":"taku","releases":[{"0":"3602","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"vim-reorder-columns.zip","4":"vim-reorder-columns.zip","src_id":"15719","5":"15719","creation_date":"1306288606","6":"1306288606"}]},"3601":{"script_id":"3601","0":"3601","script_name":"cmdline-insertdatetime","1":"cmdline-insertdatetime","script_type":"utility","2":"utility","summary":"insert date or datetime in command line.","3":"insert date or datetime in command line.","description":"insert date or datetime in command line.\r\nhttps:\/\/github.com\/taku-o\/vim-cmdline-insertdatetime\r\n\r\nin commandline,\r\n    <C-X>dt         insert YYYYMMDD formated date string.\r\n    <C-X>ts         insert YYYYMMDDHHMM formated datetime string.\r\n\r\nusage example,\r\n    1. input file name head .\r\n        :w work\r\n\r\n    2. input <C-X>dt .\r\n        :w work20110525\r\n\r\n    3. input file extension '.txt' .\r\n        :w work20110525.txt\r\n\r\n    4. enter, and save file with date.\r\n","4":"insert date or datetime in command line.\r\nhttps:\/\/github.com\/taku-o\/vim-cmdline-insertdatetime\r\n\r\nin commandline,\r\n    <C-X>dt         insert YYYYMMDD formated date string.\r\n    <C-X>ts         insert YYYYMMDDHHMM formated datetime string.\r\n\r\nusage example,\r\n    1. input file name head .\r\n        :w work\r\n\r\n    2. input <C-X>dt .\r\n        :w work20110525\r\n\r\n    3. input file extension '.txt' .\r\n        :w work20110525.txt\r\n\r\n    4. enter, and save file with date.\r\n","install_details":"copy cmdline-insertdatetime.vim into your plugin directory.","5":"copy cmdline-insertdatetime.vim into your plugin directory.","first_name":"omi","6":"omi","last_name":"taku","7":"taku","releases":[{"0":"3601","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"vim-cmdline-insertdatetime.zip","4":"vim-cmdline-insertdatetime.zip","src_id":"15718","5":"15718","creation_date":"1306288519","6":"1306288519"}]},"3600":{"script_id":"3600","0":"3600","script_name":"octave.vim","1":"octave.vim","script_type":"syntax","2":"syntax","summary":"Syntax highlighting file for GNU Octave language","3":"Syntax highlighting file for GNU Octave language","description":"This file provides syntax highlighting for the GNU Octave programming language.\r\n\r\nFeatures\r\n* Highlights entire Octave grammar (endwhile, endfor, etc.), not just Matlab keywords\r\n* Updated to highlight all core Octave functions as of version 8.1.0\r\n* Use-dependent highlighting of Octave system variables\r\n   When querying system variables, keyword is highlighted as a constant.  For example, var = true, highlights 'true' as a constant.\r\n   When setting variables or otherwise invoking keyword as a function, keyword is highlighted as a function.  For example, var = true (2,4), highlights 'true' as a function.\r\n* Highlights user functions and anonymous functions [@(...)] from within the .m file being edited\r\n* Support for multi-line strings with line continuation characters as well as escaped quotes (\\\" or '') within string.\r\n* Support for multi-line block comments\r\n* Support for highlighting numbers that use hex (0x) or binary (0b) syntax\r\n* Error highlighting for bad structure variable names, bad block comments, bad line continuations.\r\n* Optional runtime support for highlighting user variables, operators (+, -, *, etc.), and tabs   \r\n\r\nOMNIFUNC\r\n* The syntax file has a list of every valid function in Octave which makes it very useful as an auto-completion dictionary for use with ViM's omnifunc function.  Once installed, type a few letters of the name of a function and then use Ctrl-X Ctrl-O to bring up a list of possible matches.\r\n\r\nErrata\r\n* Detection of incorrectly formed numbers is incomplete.\r\n\r\nIndent\r\n\r\nFor automatic indenting of Octave code see the companion file at vimscript #6056.\r\n\r\nAddenda\r\n\r\nThis script has been thoroughly rewritten and expanded.\r\n\r\nThis original script owes some debt to the two existing Octave syntax scripts:\r\nhttp:\/\/www.vim.org\/scripts\/script.php?script_id=1241\r\nhttp:\/\/www.vim.org\/scripts\/script.php?script_id=1591","4":"This file provides syntax highlighting for the GNU Octave programming language.\r\n\r\nFeatures\r\n* Highlights entire Octave grammar (endwhile, endfor, etc.), not just Matlab keywords\r\n* Updated to highlight all core Octave functions as of version 8.1.0\r\n* Use-dependent highlighting of Octave system variables\r\n   When querying system variables, keyword is highlighted as a constant.  For example, var = true, highlights 'true' as a constant.\r\n   When setting variables or otherwise invoking keyword as a function, keyword is highlighted as a function.  For example, var = true (2,4), highlights 'true' as a function.\r\n* Highlights user functions and anonymous functions [@(...)] from within the .m file being edited\r\n* Support for multi-line strings with line continuation characters as well as escaped quotes (\\\" or '') within string.\r\n* Support for multi-line block comments\r\n* Support for highlighting numbers that use hex (0x) or binary (0b) syntax\r\n* Error highlighting for bad structure variable names, bad block comments, bad line continuations.\r\n* Optional runtime support for highlighting user variables, operators (+, -, *, etc.), and tabs   \r\n\r\nOMNIFUNC\r\n* The syntax file has a list of every valid function in Octave which makes it very useful as an auto-completion dictionary for use with ViM's omnifunc function.  Once installed, type a few letters of the name of a function and then use Ctrl-X Ctrl-O to bring up a list of possible matches.\r\n\r\nErrata\r\n* Detection of incorrectly formed numbers is incomplete.\r\n\r\nIndent\r\n\r\nFor automatic indenting of Octave code see the companion file at vimscript #6056.\r\n\r\nAddenda\r\n\r\nThis script has been thoroughly rewritten and expanded.\r\n\r\nThis original script owes some debt to the two existing Octave syntax scripts:\r\nhttp:\/\/www.vim.org\/scripts\/script.php?script_id=1241\r\nhttp:\/\/www.vim.org\/scripts\/script.php?script_id=1591","install_details":"Syntax file install on a UNIX-like system\r\n\r\n1) mkdir -p ~\/.vim\/syntax\r\n2) cp octave.vim ~\/.vim\/syntax\/\r\n3) Add the following lines to your ~\/.vimrc to have ViM use the file\r\n\r\n----- SNIP -----\r\n\" Octave filetype detection\r\naugroup filetypedetect\r\n  au! BufRead,BufNewFile *.m set filetype=octave\r\naugroup END\r\n----- SNIP -----\r\n\r\nOptional highlighting is controlled by three configuration variables:\r\n\r\n\"octave_highlight_variables\" : highlight user variables.  For example, \"y\" and \"x\" in the code \"y = cos (x)\"\r\n\"octave_highlight_operators\" : highlight logical (&,|,!,~), arithmetic (+,-,*,\/,\\,^), and relational (<,<=,>,>=,!=,~=) operators\r\n\"octave_highlight_tabs\" : highlight tabs (\\t)\r\n\r\nTo enable one of the optional highlighting classes use the following command in a buffer or in your .vimrc file for permanent behavior\r\n\r\n----- SNIP -----\r\nlet octave_highlight_XXXX=1\r\n----- SNIP -----\r\n\r\nand to disable optional highlighting use\r\n\r\n----- SNIP -----\r\nunlet octave_highlight_XXXX\r\n----- SNIP -----\r\n\r\nOMNIFUNC install on a UNIX-like system\r\n\r\n1) Install the syntax file as described above\r\n2) Add the following lines to your ~\/.vimrc after the snippet from step 3 above\r\n----- SNIP -----\r\n\" Use keywords from Octave syntax language file for autocomplete \r\nif has(\"autocmd\") && exists(\"+omnifunc\")\r\n   autocmd Filetype octave\r\n   \\\tif &omnifunc == \"\" |\r\n   \\\t\tsetlocal omnifunc=syntaxcomplete#Complete |\r\n   \\\tendif\r\nendif\r\n----- SNIP -----\r\n","5":"Syntax file install on a UNIX-like system\r\n\r\n1) mkdir -p ~\/.vim\/syntax\r\n2) cp octave.vim ~\/.vim\/syntax\/\r\n3) Add the following lines to your ~\/.vimrc to have ViM use the file\r\n\r\n----- SNIP -----\r\n\" Octave filetype detection\r\naugroup filetypedetect\r\n  au! BufRead,BufNewFile *.m set filetype=octave\r\naugroup END\r\n----- SNIP -----\r\n\r\nOptional highlighting is controlled by three configuration variables:\r\n\r\n\"octave_highlight_variables\" : highlight user variables.  For example, \"y\" and \"x\" in the code \"y = cos (x)\"\r\n\"octave_highlight_operators\" : highlight logical (&,|,!,~), arithmetic (+,-,*,\/,\\,^), and relational (<,<=,>,>=,!=,~=) operators\r\n\"octave_highlight_tabs\" : highlight tabs (\\t)\r\n\r\nTo enable one of the optional highlighting classes use the following command in a buffer or in your .vimrc file for permanent behavior\r\n\r\n----- SNIP -----\r\nlet octave_highlight_XXXX=1\r\n----- SNIP -----\r\n\r\nand to disable optional highlighting use\r\n\r\n----- SNIP -----\r\nunlet octave_highlight_XXXX\r\n----- SNIP -----\r\n\r\nOMNIFUNC install on a UNIX-like system\r\n\r\n1) Install the syntax file as described above\r\n2) Add the following lines to your ~\/.vimrc after the snippet from step 3 above\r\n----- SNIP -----\r\n\" Use keywords from Octave syntax language file for autocomplete \r\nif has(\"autocmd\") && exists(\"+omnifunc\")\r\n   autocmd Filetype octave\r\n   \\\tif &omnifunc == \"\" |\r\n   \\\t\tsetlocal omnifunc=syntaxcomplete#Complete |\r\n   \\\tendif\r\nendif\r\n----- SNIP -----\r\n","first_name":"Rik","6":"Rik","last_name":"***","7":"***","releases":[{"0":"3600","vim_version":"7.0","1":"7.0","script_version":"8.1.0","2":"8.1.0","version_comment":"Syntax matched to Octave Release: 8.1.0\r\nUnderscores now supported in numbers for readability (e.g., 1_000).\r\nClass signifiers (u8,u16,u32,u64,s8,s16,s32,s64) for binary and hex numbers.\r\nFortran exponeniation operator (\\\"**\\\") is now an error.\r\nBackslash line continuations in single-quoted strings are now an error.\r\nBackslash line continuations for ordinary code are now an error.\r\nTrailing text on the first line of a block comment is now an error.\r\nSupport for Vim < 5.7 has been removed.","3":"Syntax matched to Octave Release: 8.1.0\r\nUnderscores now supported in numbers for readability (e.g., 1_000).\r\nClass signifiers (u8,u16,u32,u64,s8,s16,s32,s64) for binary and hex numbers.\r\nFortran exponeniation operator (\\\"**\\\") is now an error.\r\nBackslash line continuations in single-quoted strings are now an error.\r\nBackslash line continuations for ordinary code are now an error.\r\nTrailing text on the first line of a block comment is now an error.\r\nSupport for Vim < 5.7 has been removed.","package":"octave.vim","4":"octave.vim","src_id":"28396","5":"28396","creation_date":"1679986467","6":"1679986467"},{"0":"3600","vim_version":"5.7","1":"5.7","script_version":"6.3.0","2":"6.3.0","version_comment":"Syntax matched to Octave Release 6.3.0\r\nAdd runtime configuration variables octave_highlight_operators, octave_highlight_variables, octave_highlight_tabs.\r\nFix highlighting of classdef keywords which are also functions.\r\nFix highlighting of complex numbers with capital I,J.\r\nFix highlighting of user variables, particularly structs.\r\nFix highlighting of run-away strings and strings with line continuations\r\nAvoid changing vim variable \"iskeyword\" and regexp matching for local buffer.\r\nCompletely overhauled strategy for highlighting\r\nPerformance improvements in regular expressions","3":"Syntax matched to Octave Release 6.3.0\r\nAdd runtime configuration variables octave_highlight_operators, octave_highlight_variables, octave_highlight_tabs.\r\nFix highlighting of classdef keywords which are also functions.\r\nFix highlighting of complex numbers with capital I,J.\r\nFix highlighting of user variables, particularly structs.\r\nFix highlighting of run-away strings and strings with line continuations\r\nAvoid changing vim variable \"iskeyword\" and regexp matching for local buffer.\r\nCompletely overhauled strategy for highlighting\r\nPerformance improvements in regular expressions","package":"octave.vim","4":"octave.vim","src_id":"27745","5":"27745","creation_date":"1632280548","6":"1632280548"},{"0":"3600","vim_version":"5.7","1":"5.7","script_version":"4.2.0","2":"4.2.0","version_comment":"Updated to include syntax highlighting for all functions in 4.2.0.\r\nHighlights numbers that use new syntax for hex (0x) and binary (0b).\r\nClassdef keywords now automatically indent\/exdent when used in code. ","3":"Updated to include syntax highlighting for all functions in 4.2.0.\r\nHighlights numbers that use new syntax for hex (0x) and binary (0b).\r\nClassdef keywords now automatically indent\/exdent when used in code. ","package":"octave.vim.4.2.0","4":"octave.vim.4.2.0","src_id":"24730","5":"24730","creation_date":"1479081732","6":"1479081732"},{"0":"3600","vim_version":"5.7","1":"5.7","script_version":"3.8.3","2":"3.8.3","version_comment":"Correctly highlight cell arrays that use a transpose operator","3":"Correctly highlight cell arrays that use a transpose operator","package":"octave.vim","4":"octave.vim","src_id":"22437","5":"22437","creation_date":"1411056314","6":"1411056314"},{"0":"3600","vim_version":"6.0","1":"6.0","script_version":"3.8.0","2":"3.8.0","version_comment":"Updated function list to match 3.8.0 release of Octave\r\nCorrect coloring problem with escaped double quotes within double-quoted string","3":"Updated function list to match 3.8.0 release of Octave\r\nCorrect coloring problem with escaped double quotes within double-quoted string","package":"octave.vim","4":"octave.vim","src_id":"21303","5":"21303","creation_date":"1389384560","6":"1389384560"},{"0":"3600","vim_version":"5.7","1":"5.7","script_version":"3.6.0b","2":"3.6.0b","version_comment":"Correctly highlight functions like strcmp which use '=' within quotes rather than assignment","3":"Correctly highlight functions like strcmp which use '=' within quotes rather than assignment","package":"octave.vim","4":"octave.vim","src_id":"17336","5":"17336","creation_date":"1327885033","6":"1327885033"},{"0":"3600","vim_version":"5.7","1":"5.7","script_version":"3.6.0","2":"3.6.0","version_comment":"Update with list of 3.6.0 functions.  Now highlights keywords varargin, varargout, parfor.","3":"Update with list of 3.6.0 functions.  Now highlights keywords varargin, varargout, parfor.","package":"octave.vim","4":"octave.vim","src_id":"17308","5":"17308","creation_date":"1327341033","6":"1327341033"},{"0":"3600","vim_version":"5.7","1":"5.7","script_version":"3.4.3","2":"3.4.3","version_comment":"Updated for 3.4.3\r\nSpellchecking in Vim, if used, is now restricted to string literals and comments which reduces screen clutter.","3":"Updated for 3.4.3\r\nSpellchecking in Vim, if used, is now restricted to string literals and comments which reduces screen clutter.","package":"octave.vim","4":"octave.vim","src_id":"16658","5":"16658","creation_date":"1318441552","6":"1318441552"},{"0":"3600","vim_version":"5.7","1":"5.7","script_version":"3.4.2","2":"3.4.2","version_comment":"Updated with 3.4.2 function list","3":"Updated with 3.4.2 function list","package":"octave.vim","4":"octave.vim","src_id":"16190","5":"16190","creation_date":"1312330356","6":"1312330356"},{"0":"3600","vim_version":"5.7","1":"5.7","script_version":"3.4.0c","2":"3.4.0c","version_comment":"Now highlights anonymous functions.\r\nCommands integrated into use-dependent highlighting.\r\nBetter recognition of keyword on LHS of '=' to stop highlighting user variables","3":"Now highlights anonymous functions.\r\nCommands integrated into use-dependent highlighting.\r\nBetter recognition of keyword on LHS of '=' to stop highlighting user variables","package":"octave.vim","4":"octave.vim","src_id":"15840","5":"15840","creation_date":"1307576763","6":"1307576763"},{"0":"3600","vim_version":"5.7","1":"5.7","script_version":"3.4.0b","2":"3.4.0b","version_comment":"Correct occasional non-highlighting of nested () within function calls","3":"Correct occasional non-highlighting of nested () within function calls","package":"octave.vim","4":"octave.vim","src_id":"15780","5":"15780","creation_date":"1306859194","6":"1306859194"},{"0":"3600","vim_version":"5.7","1":"5.7","script_version":"3.4.0","2":"3.4.0","version_comment":"Initial upload","3":"Initial upload","package":"octave.vim","4":"octave.vim","src_id":"15714","5":"15714","creation_date":"1306256119","6":"1306256119"}]},"3599":{"script_id":"3599","0":"3599","script_name":"Auto Pairs","1":"Auto Pairs","script_type":"utility","2":"utility","summary":"Insert or delete brackets, parens, quotes in pair.","3":"Insert or delete brackets, parens, quotes in pair.","description":"Repository: https:\/\/github.com\/jiangmiao\/auto-pairs\r\n\r\nAuto Pairs\r\n==========\r\nInsert or delete brackets, parens, quotes in pair.\r\n\r\nInstallation\r\n------------\r\ncopy plugin\/auto-pairs.vim to ~\/.vim\/plugin\r\n\r\nor if you are using `pathogen`:\r\n\r\n```git clone git:\/\/github.com\/jiangmiao\/auto-pairs.git ~\/.vim\/bundle\/auto-pairs```\r\n\r\nFeatures\r\n--------\r\n*   Insert in pair\r\n\r\n        input: [\r\n        output: [|]\r\n\r\n*   Delete in pair\r\n\r\n        input: foo[<BS>\r\n        output: foo\r\n\r\n*   Insert new indented line after Return\r\n\r\n        input: {|} (press <CR> at |)\r\n        output: {\r\n            |\r\n        }\r\n\r\n*   Insert spaces before closing characters, only for [], (), {}\r\n\r\n        input: {|} (press <SPACE> at |)\r\n        output: { | }\r\n\r\n        input: {|} (press <SPACE>foo} at |)\r\n        output: { foo }|\r\n\r\n        input: '|' (press <SPACE> at |)\r\n        output: ' |'\r\n\r\n*   Skip ' when inside a word\r\n\r\n        input: foo| (press ' at |)\r\n        output: foo'\r\n\r\n*   Skip closed bracket.\r\n\r\n        input: []\r\n        output: []\r\n\r\n*   Ignore auto pair when previous character is \\\r\n\r\n        input: \"\\'\r\n        output: \"\\'\"\r\n\r\n*   Fast Wrap\r\n\r\n        input: |'hello' (press (<M-e> at |)\r\n        output: ('hello')\r\n\r\n        wrap string, only support c style string\r\n        input: |'h\\\\el\\'lo' (press (<M-e> at |)\r\n        output ('h\\\\ello\\'')\r\n\r\n        input: |[foo, bar()] (press (<M-e> at |)\r\n        output: ([foo, bar()])\r\n\r\n*   Quick jump to closed pair.\r\n\r\n        input:\r\n        {\r\n            something;|\r\n        }\r\n\r\n        (press } at |)\r\n\r\n        output:\r\n        {\r\n\r\n        }|\r\n\r\n*   Support ``` ''' and \"\"\"\r\n\r\n        input:\r\n            '''\r\n\r\n        output:\r\n            '''|'''\r\n\r\n*   Delete Repeated Pairs in one time\r\n\r\n        input: \"\"\"|\"\"\" (press <BS> at |)\r\n        output: |\r\n\r\n        input: {{|}} (press <BS> at |)\r\n        output: |\r\n\r\n        input: [[[[[[|]]]]]] (press <BS> at |)\r\n        output: |\r\n\r\n*  Fly Mode\r\n\r\n        input: if(a[3)\r\n        output: if(a[3])| (In Fly Mode)\r\n        output: if(a[3)]) (Without Fly Mode)\r\n\r\n        input:\r\n        {\r\n            hello();|\r\n            world();\r\n        }\r\n\r\n        (press } at |)\r\n\r\n        output:\r\n        {\r\n            hello();\r\n            world();\r\n        }|\r\n\r\n        (then press <M-b> at | to do backinsert)\r\n        output:\r\n        {\r\n            hello();}|\r\n            world();\r\n        }\r\n\r\n        See Fly Mode section for details\r\n\r\nFly Mode\r\n--------\r\nFly Mode will always force closed-pair jumping instead of inserting. only for \")\", \"}\", \"]\"\r\n\r\nIf jumps in mistake, could use AutoPairsBackInsert(Default Key: `<M-b>`) to jump back and insert closed pair.\r\n\r\nthe most situation maybe want to insert single closed pair in the string, eg \")\"\r\n\r\nFly Mode is DISABLED by default.\r\n\r\nadd **let g:AutoPairsFlyMode = 1** .vimrc to turn it on\r\n\r\nDefault Options:\r\n\r\n    let g:AutoPairsFlyMode = 0\r\n    let g:AutoPairsShortcutBackInsert = '<M-b>'\r\n\r\nShortcuts\r\n---------\r\n\r\n    System Shortcuts:\r\n        <CR>  : Insert new indented line after return if cursor in blank brackets or quotes.\r\n        <BS>  : Delete brackets in pair\r\n        <M-p> : Toggle Autopairs (g:AutoPairsShortcutToggle)\r\n        <M-e> : Fast Wrap (g:AutoPairsShortcutFastWrap)\r\n        <M-n> : Jump to next closed pair (g:AutoPairsShortcutJump)\r\n        <M-b> : BackInsert (g:AutoPairsShortcutBackInsert)\r\n\r\n    If <M-p> <M-e> or <M-n> conflict with another keys or want to bind to another keys, add\r\n\r\n        let g:AutoPairShortcutToggle = '<another key>'\r\n\r\n    to .vimrc, if the key is empty string '', then the shortcut will be disabled.\r\n\r\nOptions\r\n-------\r\n*   g:AutoPairs\r\n\r\n        Default: {'(':')', '[':']', '{':'}',\"'\":\"'\",'\"':'\"', '`':'`'}\r\n\r\n*   b:AutoPairs\r\n\r\n        Default: g:AutoPairs\r\n\r\n        Buffer level pairs set.\r\n\r\n*   g:AutoPairsShortcutToggle\r\n\r\n        Default: '<M-p>'\r\n\r\n        The shortcut to toggle autopairs.\r\n\r\n*   g:AutoPairsShortcutFastWrap\r\n\r\n        Default: '<M-e>'\r\n\r\n        Fast wrap the word. all pairs will be consider as a block (include <>).\r\n        (|)'hello' after fast wrap at |, the word will be ('hello')\r\n        (|)<hello> after fast wrap at |, the word will be (<hello>)\r\n\r\n*   g:AutoPairsShortcutJump\r\n\r\n        Default: '<M-n>'\r\n\r\n        Jump to the next closed pair\r\n\r\n*   g:AutoPairsMapBS\r\n\r\n        Default : 1\r\n\r\n        Map <BS> to delete brackets, quotes in pair\r\n        execute 'inoremap <buffer> <silent> <BS> <C-R>=AutoPairsDelete()<CR>'\r\n\r\n*   g:AutoPairsMapCR\r\n\r\n        Default : 1\r\n\r\n        Map <CR> to insert a new indented line if cursor in (|), {|} [|], '|', \"|\"\r\n        execute 'inoremap <buffer> <silent> <CR> <C-R>=AutoPairsReturn()<CR>'\r\n\r\n*   g:AutoPairsCenterLine\r\n\r\n        Default : 1\r\n\r\n        When g:AutoPairsMapCR is on, center current line after return if the line is at the bottom 1\/3 of the window.\r\n\r\n*   g:AutoPairsMapSpace\r\n\r\n        Default : 1\r\n\r\n        Map <space> to insert a space after the opening character and before the closing one.\r\n        execute 'inoremap <buffer> <silent> <CR> <C-R>=AutoPairsSpace()<CR>'\r\n\r\n*   g:AutoPairsFlyMode\r\n\r\n        Default : 0\r\n\r\n        set it to 1 to enable FlyMode.\r\n        see FlyMode section for details.\r\n\r\n*   g:AutoPairsShortcutBackInsert\r\n\r\n        Default : <M-b>\r\n\r\n        Work with FlyMode, insert the key at the Fly Mode jumped postion\r\n\r\nBuffer Level Pairs Setting\r\n--------------------------\r\n\r\nSet b:AutoPairs before BufEnter\r\n\r\neg:\r\n\r\n    \" When the filetype is FILETYPE then make AutoPairs only match for parenthesis\r\n    au Filetype FILETYPE let b:AutoPairs = {\"(\": \")\"}\r\n\r\nTroubleShooting\r\n---------------\r\n    The script will remap keys ([{'\"}]) <BS>,\r\n    If auto pairs cannot work, use :imap ( to check if the map is corrected.\r\n    The correct map should be <C-R>=AutoPairsInsert(\"\\(\")<CR>\r\n    Or the plugin conflict with some other plugins.\r\n    use command :call AutoPairsInit() to remap the keys.\r\n\r\n\r\n* How to insert parens purely\r\n\r\n    There are 3 ways\r\n\r\n    1. use Ctrl-V ) to insert paren without trigger the plugin.\r\n\r\n    2. use Alt-P to turn off the plugin.\r\n\r\n    3. use DEL or <C-O>x to delete the character insert by plugin.\r\n\r\n\r\nKnown Issues\r\n-----------------------\r\nThere are the issues I cannot fix.\r\n\r\nBreaks '.' - [issue #3](https:\/\/github.com\/jiangmiao\/auto-pairs\/issues\/3)\r\n\r\n    Description: After entering insert mode and inputing `[hello` then leave insert\r\n                 mode by `<ESC>`. press '.' will insert 'hello' instead of '[hello]'.\r\n    Reason: `[` actually equals `[]\\<LEFT>` and \\<LEFT> will break '.'\r\n    Solution: none\r\n\r\nContributors\r\n------------\r\n* [camthompson](https:\/\/github.com\/camthompson)","4":"Repository: https:\/\/github.com\/jiangmiao\/auto-pairs\r\n\r\nAuto Pairs\r\n==========\r\nInsert or delete brackets, parens, quotes in pair.\r\n\r\nInstallation\r\n------------\r\ncopy plugin\/auto-pairs.vim to ~\/.vim\/plugin\r\n\r\nor if you are using `pathogen`:\r\n\r\n```git clone git:\/\/github.com\/jiangmiao\/auto-pairs.git ~\/.vim\/bundle\/auto-pairs```\r\n\r\nFeatures\r\n--------\r\n*   Insert in pair\r\n\r\n        input: [\r\n        output: [|]\r\n\r\n*   Delete in pair\r\n\r\n        input: foo[<BS>\r\n        output: foo\r\n\r\n*   Insert new indented line after Return\r\n\r\n        input: {|} (press <CR> at |)\r\n        output: {\r\n            |\r\n        }\r\n\r\n*   Insert spaces before closing characters, only for [], (), {}\r\n\r\n        input: {|} (press <SPACE> at |)\r\n        output: { | }\r\n\r\n        input: {|} (press <SPACE>foo} at |)\r\n        output: { foo }|\r\n\r\n        input: '|' (press <SPACE> at |)\r\n        output: ' |'\r\n\r\n*   Skip ' when inside a word\r\n\r\n        input: foo| (press ' at |)\r\n        output: foo'\r\n\r\n*   Skip closed bracket.\r\n\r\n        input: []\r\n        output: []\r\n\r\n*   Ignore auto pair when previous character is \\\r\n\r\n        input: \"\\'\r\n        output: \"\\'\"\r\n\r\n*   Fast Wrap\r\n\r\n        input: |'hello' (press (<M-e> at |)\r\n        output: ('hello')\r\n\r\n        wrap string, only support c style string\r\n        input: |'h\\\\el\\'lo' (press (<M-e> at |)\r\n        output ('h\\\\ello\\'')\r\n\r\n        input: |[foo, bar()] (press (<M-e> at |)\r\n        output: ([foo, bar()])\r\n\r\n*   Quick jump to closed pair.\r\n\r\n        input:\r\n        {\r\n            something;|\r\n        }\r\n\r\n        (press } at |)\r\n\r\n        output:\r\n        {\r\n\r\n        }|\r\n\r\n*   Support ``` ''' and \"\"\"\r\n\r\n        input:\r\n            '''\r\n\r\n        output:\r\n            '''|'''\r\n\r\n*   Delete Repeated Pairs in one time\r\n\r\n        input: \"\"\"|\"\"\" (press <BS> at |)\r\n        output: |\r\n\r\n        input: {{|}} (press <BS> at |)\r\n        output: |\r\n\r\n        input: [[[[[[|]]]]]] (press <BS> at |)\r\n        output: |\r\n\r\n*  Fly Mode\r\n\r\n        input: if(a[3)\r\n        output: if(a[3])| (In Fly Mode)\r\n        output: if(a[3)]) (Without Fly Mode)\r\n\r\n        input:\r\n        {\r\n            hello();|\r\n            world();\r\n        }\r\n\r\n        (press } at |)\r\n\r\n        output:\r\n        {\r\n            hello();\r\n            world();\r\n        }|\r\n\r\n        (then press <M-b> at | to do backinsert)\r\n        output:\r\n        {\r\n            hello();}|\r\n            world();\r\n        }\r\n\r\n        See Fly Mode section for details\r\n\r\nFly Mode\r\n--------\r\nFly Mode will always force closed-pair jumping instead of inserting. only for \")\", \"}\", \"]\"\r\n\r\nIf jumps in mistake, could use AutoPairsBackInsert(Default Key: `<M-b>`) to jump back and insert closed pair.\r\n\r\nthe most situation maybe want to insert single closed pair in the string, eg \")\"\r\n\r\nFly Mode is DISABLED by default.\r\n\r\nadd **let g:AutoPairsFlyMode = 1** .vimrc to turn it on\r\n\r\nDefault Options:\r\n\r\n    let g:AutoPairsFlyMode = 0\r\n    let g:AutoPairsShortcutBackInsert = '<M-b>'\r\n\r\nShortcuts\r\n---------\r\n\r\n    System Shortcuts:\r\n        <CR>  : Insert new indented line after return if cursor in blank brackets or quotes.\r\n        <BS>  : Delete brackets in pair\r\n        <M-p> : Toggle Autopairs (g:AutoPairsShortcutToggle)\r\n        <M-e> : Fast Wrap (g:AutoPairsShortcutFastWrap)\r\n        <M-n> : Jump to next closed pair (g:AutoPairsShortcutJump)\r\n        <M-b> : BackInsert (g:AutoPairsShortcutBackInsert)\r\n\r\n    If <M-p> <M-e> or <M-n> conflict with another keys or want to bind to another keys, add\r\n\r\n        let g:AutoPairShortcutToggle = '<another key>'\r\n\r\n    to .vimrc, if the key is empty string '', then the shortcut will be disabled.\r\n\r\nOptions\r\n-------\r\n*   g:AutoPairs\r\n\r\n        Default: {'(':')', '[':']', '{':'}',\"'\":\"'\",'\"':'\"', '`':'`'}\r\n\r\n*   b:AutoPairs\r\n\r\n        Default: g:AutoPairs\r\n\r\n        Buffer level pairs set.\r\n\r\n*   g:AutoPairsShortcutToggle\r\n\r\n        Default: '<M-p>'\r\n\r\n        The shortcut to toggle autopairs.\r\n\r\n*   g:AutoPairsShortcutFastWrap\r\n\r\n        Default: '<M-e>'\r\n\r\n        Fast wrap the word. all pairs will be consider as a block (include <>).\r\n        (|)'hello' after fast wrap at |, the word will be ('hello')\r\n        (|)<hello> after fast wrap at |, the word will be (<hello>)\r\n\r\n*   g:AutoPairsShortcutJump\r\n\r\n        Default: '<M-n>'\r\n\r\n        Jump to the next closed pair\r\n\r\n*   g:AutoPairsMapBS\r\n\r\n        Default : 1\r\n\r\n        Map <BS> to delete brackets, quotes in pair\r\n        execute 'inoremap <buffer> <silent> <BS> <C-R>=AutoPairsDelete()<CR>'\r\n\r\n*   g:AutoPairsMapCR\r\n\r\n        Default : 1\r\n\r\n        Map <CR> to insert a new indented line if cursor in (|), {|} [|], '|', \"|\"\r\n        execute 'inoremap <buffer> <silent> <CR> <C-R>=AutoPairsReturn()<CR>'\r\n\r\n*   g:AutoPairsCenterLine\r\n\r\n        Default : 1\r\n\r\n        When g:AutoPairsMapCR is on, center current line after return if the line is at the bottom 1\/3 of the window.\r\n\r\n*   g:AutoPairsMapSpace\r\n\r\n        Default : 1\r\n\r\n        Map <space> to insert a space after the opening character and before the closing one.\r\n        execute 'inoremap <buffer> <silent> <CR> <C-R>=AutoPairsSpace()<CR>'\r\n\r\n*   g:AutoPairsFlyMode\r\n\r\n        Default : 0\r\n\r\n        set it to 1 to enable FlyMode.\r\n        see FlyMode section for details.\r\n\r\n*   g:AutoPairsShortcutBackInsert\r\n\r\n        Default : <M-b>\r\n\r\n        Work with FlyMode, insert the key at the Fly Mode jumped postion\r\n\r\nBuffer Level Pairs Setting\r\n--------------------------\r\n\r\nSet b:AutoPairs before BufEnter\r\n\r\neg:\r\n\r\n    \" When the filetype is FILETYPE then make AutoPairs only match for parenthesis\r\n    au Filetype FILETYPE let b:AutoPairs = {\"(\": \")\"}\r\n\r\nTroubleShooting\r\n---------------\r\n    The script will remap keys ([{'\"}]) <BS>,\r\n    If auto pairs cannot work, use :imap ( to check if the map is corrected.\r\n    The correct map should be <C-R>=AutoPairsInsert(\"\\(\")<CR>\r\n    Or the plugin conflict with some other plugins.\r\n    use command :call AutoPairsInit() to remap the keys.\r\n\r\n\r\n* How to insert parens purely\r\n\r\n    There are 3 ways\r\n\r\n    1. use Ctrl-V ) to insert paren without trigger the plugin.\r\n\r\n    2. use Alt-P to turn off the plugin.\r\n\r\n    3. use DEL or <C-O>x to delete the character insert by plugin.\r\n\r\n\r\nKnown Issues\r\n-----------------------\r\nThere are the issues I cannot fix.\r\n\r\nBreaks '.' - [issue #3](https:\/\/github.com\/jiangmiao\/auto-pairs\/issues\/3)\r\n\r\n    Description: After entering insert mode and inputing `[hello` then leave insert\r\n                 mode by `<ESC>`. press '.' will insert 'hello' instead of '[hello]'.\r\n    Reason: `[` actually equals `[]\\<LEFT>` and \\<LEFT> will break '.'\r\n    Solution: none\r\n\r\nContributors\r\n------------\r\n* [camthompson](https:\/\/github.com\/camthompson)","install_details":"copy plugin\/auto-pairs.vim to ~\/.vim\/plugin\r\n\r\nor if you are using `pathogen`:\r\n\r\n```git clone git:\/\/github.com\/jiangmiao\/auto-pairs.git ~\/.vim\/bundle\/auto-pairs```\r\n","5":"copy plugin\/auto-pairs.vim to ~\/.vim\/plugin\r\n\r\nor if you are using `pathogen`:\r\n\r\n```git clone git:\/\/github.com\/jiangmiao\/auto-pairs.git ~\/.vim\/bundle\/auto-pairs```\r\n","first_name":"Miao","6":"Miao","last_name":"Jiang","7":"Jiang","releases":[{"0":"3599","vim_version":"7.0","1":"7.0","script_version":"1.3.2","2":"1.3.2","version_comment":"Try to use abbreviation before using space mapping\r\n<c-h> now behaves the same as <BS>","3":"Try to use abbreviation before using space mapping\r\n<c-h> now behaves the same as <BS>","package":"auto-pairs-v1.3.2.tar.gz","4":"auto-pairs-v1.3.2.tar.gz","src_id":"20536","5":"20536","creation_date":"1374060315","6":"1374060315"},{"0":"3599","vim_version":"7.0","1":"7.0","script_version":"1.3.1","2":"1.3.1","version_comment":"Fix #33: character '|' map failed.\r\nFix #35: Fast Wrap incorrect.\r\nImprove #36, Keep quotes number is odd in one line.\r\nImprove #37, ignore comment line for vim file.\r\nImprove #43, <CR> mapping compatible.","3":"Fix #33: character '|' map failed.\r\nFix #35: Fast Wrap incorrect.\r\nImprove #36, Keep quotes number is odd in one line.\r\nImprove #37, ignore comment line for vim file.\r\nImprove #43, <CR> mapping compatible.","package":"auto-pairs-v1.3.1.tar.gz","4":"auto-pairs-v1.3.1.tar.gz","src_id":"19736","5":"19736","creation_date":"1364761119","6":"1364761119"},{"0":"3599","vim_version":"7.0","1":"7.0","script_version":"1.3.0","2":"1.3.0","version_comment":"Auto insert triple pairs.\r\nSupport deleting repeated pairs in one time.","3":"Auto insert triple pairs.\r\nSupport deleting repeated pairs in one time.","package":"auto-pairs-v1.3.0.tar.gz","4":"auto-pairs-v1.3.0.tar.gz","src_id":"19517","5":"19517","creation_date":"1360995205","6":"1360995205"},{"0":"3599","vim_version":"7.0","1":"7.0","script_version":"1.2.9","2":"1.2.9","version_comment":"Supports buffer level pairs setting.","3":"Supports buffer level pairs setting.","package":"auto-pairs-v1.2.9.tar.gz","4":"auto-pairs-v1.2.9.tar.gz","src_id":"19376","5":"19376","creation_date":"1358235244","6":"1358235244"},{"0":"3599","vim_version":"7.0","1":"7.0","script_version":"1.2.8","2":"1.2.8","version_comment":"fixes incorrect AutoPairsDelete.","3":"fixes incorrect AutoPairsDelete.","package":"auto-pairs-v1.2.8.tar.gz","4":"auto-pairs-v1.2.8.tar.gz","src_id":"19204","5":"19204","creation_date":"1355841222","6":"1355841222"},{"0":"3599","vim_version":"7.0","1":"7.0","script_version":"1.2.7","2":"1.2.7","version_comment":"fixes #24 when equalprg is set 'Return' feature cannot work well","3":"fixes #24 when equalprg is set 'Return' feature cannot work well","package":"auto-pairs-v1.2.7.tar.gz","4":"auto-pairs-v1.2.7.tar.gz","src_id":"18935","5":"18935","creation_date":"1351820116","6":"1351820116"},{"0":"3599","vim_version":"7.0","1":"7.0","script_version":"1.2.6","2":"1.2.6","version_comment":"Support typographer's quote pairs, such as \u00e2\u0080\u0098 \u00e2\u0080\u0099, \u00e2\u0080\u009c \u00e2\u0080\u009d","3":"Support typographer's quote pairs, such as \u00e2\u0080\u0098 \u00e2\u0080\u0099, \u00e2\u0080\u009c \u00e2\u0080\u009d","package":"auto-pairs-v1.2.6.tar.gz","4":"auto-pairs-v1.2.6.tar.gz","src_id":"18820","5":"18820","creation_date":"1350438792","6":"1350438792"},{"0":"3599","vim_version":"7.0","1":"7.0","script_version":"1.2.5","2":"1.2.5","version_comment":"Fixes indentation incorrect when returning below 1\/3 bottom of window.","3":"Fixes indentation incorrect when returning below 1\/3 bottom of window.","package":"auto-pairs-v1.2.5.tar.gz","4":"auto-pairs-v1.2.5.tar.gz","src_id":"18602","5":"18602","creation_date":"1347682523","6":"1347682523"},{"0":"3599","vim_version":"7.0","1":"7.0","script_version":"1.2.4","2":"1.2.4","version_comment":"fixes #20 Errors in pair creation that is split by ENTER","3":"fixes #20 Errors in pair creation that is split by ENTER","package":"auto-pairs-v1.2.4.tar.gz","4":"auto-pairs-v1.2.4.tar.gz","src_id":"18415","5":"18415","creation_date":"1345134396","6":"1345134396"},{"0":"3599","vim_version":"7.0","1":"7.0","script_version":"1.2.3","2":"1.2.3","version_comment":"compatible with neocomplcache\r\ncompatible with clang_complete\r\nImprove Fast Wrap\r\n","3":"compatible with neocomplcache\r\ncompatible with clang_complete\r\nImprove Fast Wrap\r\n","package":"auto-pairs-v1.2.3.tar.gz","4":"auto-pairs-v1.2.3.tar.gz","src_id":"18265","5":"18265","creation_date":"1342364503","6":"1342364503"},{"0":"3599","vim_version":"7.0","1":"7.0","script_version":"1.2.2","2":"1.2.2","version_comment":"compatible with vim-endwise, supertab. \r\nDisable Fly mode by default.","3":"compatible with vim-endwise, supertab. \r\nDisable Fly mode by default.","package":"auto-pairs-v1.2.2.tar.gz","4":"auto-pairs-v1.2.2.tar.gz","src_id":"17980","5":"17980","creation_date":"1337185211","6":"1337185211"},{"0":"3599","vim_version":"7.0","1":"7.0","script_version":"1.2.0","2":"1.2.0","version_comment":"New feature: Fly Mode","3":"New feature: Fly Mode","package":"auto-pairs-v1.2.0.tar.gz","4":"auto-pairs-v1.2.0.tar.gz","src_id":"17949","5":"17949","creation_date":"1336961051","6":"1336961051"},{"0":"3599","vim_version":"7.0","1":"7.0","script_version":"1.1.6","2":"1.1.6","version_comment":"fixes issue #9 Lowercase 'a' acute accent via opt-e not working\r\nfixes issue #8 having errors with the double quotes when cpoptions is $\r\navoid overriding imap silent flag\r\nalways silent mapping\r\n","3":"fixes issue #9 Lowercase 'a' acute accent via opt-e not working\r\nfixes issue #8 having errors with the double quotes when cpoptions is $\r\navoid overriding imap silent flag\r\nalways silent mapping\r\n","package":"auto-pairs-v1.1.6.tar.gz","4":"auto-pairs-v1.1.6.tar.gz","src_id":"17636","5":"17636","creation_date":"1332401164","6":"1332401164"},{"0":"3599","vim_version":"7.0","1":"7.0","script_version":"1.1.5","2":"1.1.5","version_comment":"works with vim-endwise","3":"works with vim-endwise","package":"auto-pairs-v1.1.5.tar.gz","4":"auto-pairs-v1.1.5.tar.gz","src_id":"17557","5":"17557","creation_date":"1330794256","6":"1330794256"},{"0":"3599","vim_version":"7.0","1":"7.0","script_version":"1.1.4","2":"1.1.4","version_comment":"Avoid ' in word, eg: John's \r\nSupport `\r\nSupport triple quote, ''', \"\"\", ```","3":"Avoid ' in word, eg: John's \r\nSupport `\r\nSupport triple quote, ''', \"\"\", ```","package":"auto-pairs-v1.1.4.tar.gz","4":"auto-pairs-v1.1.4.tar.gz","src_id":"17235","5":"17235","creation_date":"1326777999","6":"1326777999"},{"0":"3599","vim_version":"7.0","1":"7.0","script_version":"1.1.3","2":"1.1.3","version_comment":"NEW: quick jump to the closed pair\r\nNEW: auto insert space\r\n","3":"NEW: quick jump to the closed pair\r\nNEW: auto insert space\r\n","package":"auto-pairs-v1.1.3.tar.gz","4":"auto-pairs-v1.1.3.tar.gz","src_id":"17100","5":"17100","creation_date":"1324528523","6":"1324528523"},{"0":"3599","vim_version":"7.0","1":"7.0","script_version":"1.1.2","2":"1.1.2","version_comment":"Fix autopairs isn't loaded when open new tab by mouse.\r\nOptimize delete in pair","3":"Fix autopairs isn't loaded when open new tab by mouse.\r\nOptimize delete in pair","package":"auto-pairs-v1.1.2.tar.gz","4":"auto-pairs-v1.1.2.tar.gz","src_id":"16858","5":"16858","creation_date":"1321174478","6":"1321174478"},{"0":"3599","vim_version":"7.0","1":"7.0","script_version":"1.1.1","2":"1.1.1","version_comment":"Fix auto indent incorrect in CoffeeScript\r\neg:\r\n  foo:\r\n    bar: [|]\r\npress <CR> at |","3":"Fix auto indent incorrect in CoffeeScript\r\neg:\r\n  foo:\r\n    bar: [|]\r\npress <CR> at |","package":"auto-pairs-v1.1.1.tar.gz","4":"auto-pairs-v1.1.1.tar.gz","src_id":"16469","5":"16469","creation_date":"1315245029","6":"1315245029"},{"0":"3599","vim_version":"7.0","1":"7.0","script_version":"1.1.0","2":"1.1.0","version_comment":"fix indent incorrect after {\\<CR>}\r\nuse <expr> instead of <C-R> in map keys","3":"fix indent incorrect after {\\<CR>}\r\nuse <expr> instead of <C-R> in map keys","package":"auto-pairs-v1.1.0.tar.gz","4":"auto-pairs-v1.1.0.tar.gz","src_id":"15867","5":"15867","creation_date":"1307960378","6":"1307960378"},{"0":"3599","vim_version":"7.0","1":"7.0","script_version":"1.0.3","2":"1.0.3","version_comment":"Add Fast Wrap feature.","3":"Add Fast Wrap feature.","package":"auto-pairs-v1.0.3.tar.gz","4":"auto-pairs-v1.0.3.tar.gz","src_id":"15845","5":"15845","creation_date":"1307644800","6":"1307644800"},{"0":"3599","vim_version":"7.0","1":"7.0","script_version":"1.0.2","2":"1.0.2","version_comment":"Use {<enter> instead of {{ (Thanks to linopolus)\r\nhttps:\/\/github.com\/jiangmiao\/auto-pairs\/issues\/1\r\n\r\nAdd Toggle key\r\nAdd Options\r\n  g:AutoPairsShortcutToggle\r\n  g:AutoPairsMapBS\r\n  g:AutoPairsMapCR\r\n  g:AutoPairsCenterLine\r\n","3":"Use {<enter> instead of {{ (Thanks to linopolus)\r\nhttps:\/\/github.com\/jiangmiao\/auto-pairs\/issues\/1\r\n\r\nAdd Toggle key\r\nAdd Options\r\n  g:AutoPairsShortcutToggle\r\n  g:AutoPairsMapBS\r\n  g:AutoPairsMapCR\r\n  g:AutoPairsCenterLine\r\n","package":"auto-pairs-v1.0.2.tar.gz","4":"auto-pairs-v1.0.2.tar.gz","src_id":"15834","5":"15834","creation_date":"1307441229","6":"1307441229"},{"0":"3599","vim_version":"7.0","1":"7.0","script_version":"1.0.1","2":"1.0.1","version_comment":"Initial upload","3":"Initial upload","package":"auto-pairs-1.0.1.tar.gz","4":"auto-pairs-1.0.1.tar.gz","src_id":"15708","5":"15708","creation_date":"1306236819","6":"1306236819"}]},"3598":{"script_id":"3598","0":"3598","script_name":"Advancer Abbreviation","1":"Advancer Abbreviation","script_type":"utility","2":"utility","summary":"create code snippet through vim abbreviation","3":"create code snippet through vim abbreviation","description":"Repository, Tutorial: https:\/\/github.com\/jiangmiao\/advancer-abbreviation\r\n\r\nAdvancer Abbreviation\r\n=====================\r\nAdvancer Abbreviation is a Vim plugin to create code snippet quickly\r\n\r\nUsage\r\n-----\r\n    Use Shortcut <C-CR> or <S-CR> to expand the abbreviation or jump to next placeholder.\r\n\r\n    <S-CR> : Smart Expand or jump to next placeholder.\r\n    <C-CR> : Force Expand or jump to next placeholder.\r\n    <ESC>  : If the line contain placeholder but now it is blank, \r\n             then delete whole line and leave insert mode.\r\n\r\nFeatures\r\n--------\r\n*   Support any character except space as abbreviate name.\r\n*   Quick jump to next placeholder.\r\n*   Easy to extend.\r\n\r\nInstallation\r\n------------\r\n    copy plugin\/advancer-abbreviate.vim to ~\/.vim\/plugin\r\n\r\nTutorial\r\n--------\r\n###Preparation\r\n    copy ftplugin-examples\/* to ~\/.vim\/ftplugin\r\n\r\n    There are 5 examples include c, cpp, javascript, php, ruby\r\n    The abbreviation supported in example are\r\n\r\n        c          : for std main #i #ii\r\n        cpp        : for std main\r\n        javascript : for fu\r\n        ruby       : for def\r\n        php        : for\r\n\r\n    You could test the script with your favourite language.\r\n\r\n###example for edit C file\r\n    <C-CR> = Control+Return\r\n    |      = Cursor postion\r\n    $ gvim foo.c\r\n\r\n1\r\n\r\n    input: #i<C-CR>foo<C-CR>#ii<C-CR>bar<C-CR>\r\n    output:\r\n    #include <foo>\r\n    #include \"bar\"\r\n    |\r\n\r\n2\r\n\r\n    input: std<C-CR>\r\n    output:\r\n    #include <stdio.h>\r\n    #include <stdlib.h>\r\n    #include <string.h>\r\n\r\n    |\r\n\r\nWrite Your Own Abbreviation\r\n---------------------------\r\n    Use Command Abbr\r\n    Usage: Abbr [name] [code]\r\n    Example:\r\n    Abbr for for (\/*TODO*\/; \/*TODO*\/; \/*TODO*\/) {<CR>\/*TODO*\/<CR>}<CR>\/*TODO*\/\r\n    Abbr #ii #include \"\/*TODO*\/\"<CR>\r\n\r\n    Abbreviate format is same as vim abbr. see help :abbr\r\n    but AdvAbbr has looser limition on name, it support any character as name except space.\r\n    eg: f.f is invalid name in vim abbr but valid in Advancer Abbreviation.\r\n    \r\n    TODO has four different formats\r\n    \/*TODO*\/, #TODO#, 'TODO', <!--TODO-->\r\n    choose them according to which language is using. \r\n    for example, \/*TODO*\/ use for c, cpp, 'TODO' use for ruby\r\n","4":"Repository, Tutorial: https:\/\/github.com\/jiangmiao\/advancer-abbreviation\r\n\r\nAdvancer Abbreviation\r\n=====================\r\nAdvancer Abbreviation is a Vim plugin to create code snippet quickly\r\n\r\nUsage\r\n-----\r\n    Use Shortcut <C-CR> or <S-CR> to expand the abbreviation or jump to next placeholder.\r\n\r\n    <S-CR> : Smart Expand or jump to next placeholder.\r\n    <C-CR> : Force Expand or jump to next placeholder.\r\n    <ESC>  : If the line contain placeholder but now it is blank, \r\n             then delete whole line and leave insert mode.\r\n\r\nFeatures\r\n--------\r\n*   Support any character except space as abbreviate name.\r\n*   Quick jump to next placeholder.\r\n*   Easy to extend.\r\n\r\nInstallation\r\n------------\r\n    copy plugin\/advancer-abbreviate.vim to ~\/.vim\/plugin\r\n\r\nTutorial\r\n--------\r\n###Preparation\r\n    copy ftplugin-examples\/* to ~\/.vim\/ftplugin\r\n\r\n    There are 5 examples include c, cpp, javascript, php, ruby\r\n    The abbreviation supported in example are\r\n\r\n        c          : for std main #i #ii\r\n        cpp        : for std main\r\n        javascript : for fu\r\n        ruby       : for def\r\n        php        : for\r\n\r\n    You could test the script with your favourite language.\r\n\r\n###example for edit C file\r\n    <C-CR> = Control+Return\r\n    |      = Cursor postion\r\n    $ gvim foo.c\r\n\r\n1\r\n\r\n    input: #i<C-CR>foo<C-CR>#ii<C-CR>bar<C-CR>\r\n    output:\r\n    #include <foo>\r\n    #include \"bar\"\r\n    |\r\n\r\n2\r\n\r\n    input: std<C-CR>\r\n    output:\r\n    #include <stdio.h>\r\n    #include <stdlib.h>\r\n    #include <string.h>\r\n\r\n    |\r\n\r\nWrite Your Own Abbreviation\r\n---------------------------\r\n    Use Command Abbr\r\n    Usage: Abbr [name] [code]\r\n    Example:\r\n    Abbr for for (\/*TODO*\/; \/*TODO*\/; \/*TODO*\/) {<CR>\/*TODO*\/<CR>}<CR>\/*TODO*\/\r\n    Abbr #ii #include \"\/*TODO*\/\"<CR>\r\n\r\n    Abbreviate format is same as vim abbr. see help :abbr\r\n    but AdvAbbr has looser limition on name, it support any character as name except space.\r\n    eg: f.f is invalid name in vim abbr but valid in Advancer Abbreviation.\r\n    \r\n    TODO has four different formats\r\n    \/*TODO*\/, #TODO#, 'TODO', <!--TODO-->\r\n    choose them according to which language is using. \r\n    for example, \/*TODO*\/ use for c, cpp, 'TODO' use for ruby\r\n","install_details":"copy plugin\/advancer-abbreviate.vim to ~\/.vim\/plugin","5":"copy plugin\/advancer-abbreviate.vim to ~\/.vim\/plugin","first_name":"Miao","6":"Miao","last_name":"Jiang","7":"Jiang","releases":[{"0":"3598","vim_version":"7.0","1":"7.0","script_version":"1.0.3","2":"1.0.3","version_comment":"Use b:Abbrs instead of g:Abbrs to manage abbrs\r\nupdate README\r\n","3":"Use b:Abbrs instead of g:Abbrs to manage abbrs\r\nupdate README\r\n","package":"advancer-abbreviation-v1.0.3.tar.gz","4":"advancer-abbreviation-v1.0.3.tar.gz","src_id":"15836","5":"15836","creation_date":"1307466202","6":"1307466202"},{"0":"3598","vim_version":"7.0","1":"7.0","script_version":"1.0.2","2":"1.0.2","version_comment":"Add Smart Expand and Force Expand\r\n","3":"Add Smart Expand and Force Expand\r\n","package":"advancer-abbreviation-v1.0.2.tar.gz","4":"advancer-abbreviation-v1.0.2.tar.gz","src_id":"15722","5":"15722","creation_date":"1306316992","6":"1306316992"},{"0":"3598","vim_version":"7.0","1":"7.0","script_version":"1.0.1","2":"1.0.1","version_comment":"add option g:AbbrShortcutEscape and g:AbbrShortcutExpand\r\n","3":"add option g:AbbrShortcutEscape and g:AbbrShortcutExpand\r\n","package":"advancer-abbreviation-v1.0.1.tar.gz","4":"advancer-abbreviation-v1.0.1.tar.gz","src_id":"15712","5":"15712","creation_date":"1306252034","6":"1306252034"}]},"3597":{"script_id":"3597","0":"3597","script_name":"colorv.vim","1":"colorv.vim","script_type":"utility","2":"utility","summary":"A powerful color  tool.","3":"A powerful color  tool.","description":"Intro\r\n=====\r\n\r\n*ColorV* is a color view\/pick\/edit\/design\/scheme tool in vim.\r\n\r\nIt makes handling colors much easier.  \r\n\r\nWith it, you can:\r\n\r\nView colors Easier\r\n    ':ColorV' (<leader>cv): show ColorV window\r\n\r\n    ':ColorVView' (<leader>cw): show ColorV window with color text under cursor.\r\n\r\n    ':ColorVPreview' (<leader>cpp): Preview colors in current buffer\r\n\r\nEdit colors Easier\r\n    ':ColorVEdit' (<leader>ce): Edit color text under cursor\r\n\r\n    ':ColorVEditAll' (<leader>cE): Edit color text under cursor and change all in current buffer.\r\n\r\n    ':ColorVInsert' (<leader>cii): Insert color with ColorV window.\r\n\r\nDesign Colors Easier\r\n    ':ColorVName' (<leader>cn): show color name list window.\r\n\r\n    ':ColorVList Hue' (<leader>cgh) generate Hue list with color text under cursor.\r\n\r\n    ':ColorVTurn2 {hex1} {hex2}' (<leader>cgg) generate Hue list from hex1 to hex2.\r\n\r\n    ':ColorVPicker' (<leader>cd): show a GUI color picker.\r\n\r\nDesign Schemes Easier\r\n    ':ColorVScheme' (<leader>css) Fetch scheme from Kuler or ColourLover\r\n\r\n    ':ColorVSchemeFav' (<leader>csf) Show Faved schemes\r\n\r\n    ':ColorVSchemeNew' (<leader>csn) Create a new scheme\r\n\r\nAnd More\r\n    You can even use it under 8\/256 color terminal.\r\n\r\nGet latest and Post issues at https:\/\/github.com\/Rykka\/colorv.vim\r\n\r\nScreenShot:\r\n\r\n.. image:: http:\/\/i.minus.com\/iF5Cd8D74Rfls.png\r\n\r\n\r\n","4":"Intro\r\n=====\r\n\r\n*ColorV* is a color view\/pick\/edit\/design\/scheme tool in vim.\r\n\r\nIt makes handling colors much easier.  \r\n\r\nWith it, you can:\r\n\r\nView colors Easier\r\n    ':ColorV' (<leader>cv): show ColorV window\r\n\r\n    ':ColorVView' (<leader>cw): show ColorV window with color text under cursor.\r\n\r\n    ':ColorVPreview' (<leader>cpp): Preview colors in current buffer\r\n\r\nEdit colors Easier\r\n    ':ColorVEdit' (<leader>ce): Edit color text under cursor\r\n\r\n    ':ColorVEditAll' (<leader>cE): Edit color text under cursor and change all in current buffer.\r\n\r\n    ':ColorVInsert' (<leader>cii): Insert color with ColorV window.\r\n\r\nDesign Colors Easier\r\n    ':ColorVName' (<leader>cn): show color name list window.\r\n\r\n    ':ColorVList Hue' (<leader>cgh) generate Hue list with color text under cursor.\r\n\r\n    ':ColorVTurn2 {hex1} {hex2}' (<leader>cgg) generate Hue list from hex1 to hex2.\r\n\r\n    ':ColorVPicker' (<leader>cd): show a GUI color picker.\r\n\r\nDesign Schemes Easier\r\n    ':ColorVScheme' (<leader>css) Fetch scheme from Kuler or ColourLover\r\n\r\n    ':ColorVSchemeFav' (<leader>csf) Show Faved schemes\r\n\r\n    ':ColorVSchemeNew' (<leader>csn) Create a new scheme\r\n\r\nAnd More\r\n    You can even use it under 8\/256 color terminal.\r\n\r\nGet latest and Post issues at https:\/\/github.com\/Rykka\/colorv.vim\r\n\r\nScreenShot:\r\n\r\n.. image:: http:\/\/i.minus.com\/iF5Cd8D74Rfls.png\r\n\r\n\r\n","install_details":"1. Using Vundle  https:\/\/github.com\/gmarik\/vundle \r\n\r\n  Add this Line to your vimrc::\r\n\r\n    Bundle 'Rykka\/colorv.vim' \r\n    \" needed for fetching schemes online.\r\n    Bundle 'mattn\/webapi-vim'\r\n\r\n\r\n2. Using vim.org http:\/\/www.vim.org\/scripts\/script.php?script_id=3597\r\n\r\n    Extract to your ~\/.vim folder.\r\n    `:helptags ~\/.vim\/doc`\r\n    \r\n    NOTE   Get Latest version\r\n           https:\/\/github.com\/Rykka\/colorv.vim\/\r\n\r\n    NOTE   webapi.vim_ is needed for fetching schemes online.\r\n\r\n.. _webapi.vim: https:\/\/github.com\/mattn\/webapi-vim \r\n\r\n","5":"1. Using Vundle  https:\/\/github.com\/gmarik\/vundle \r\n\r\n  Add this Line to your vimrc::\r\n\r\n    Bundle 'Rykka\/colorv.vim' \r\n    \" needed for fetching schemes online.\r\n    Bundle 'mattn\/webapi-vim'\r\n\r\n\r\n2. Using vim.org http:\/\/www.vim.org\/scripts\/script.php?script_id=3597\r\n\r\n    Extract to your ~\/.vim folder.\r\n    `:helptags ~\/.vim\/doc`\r\n    \r\n    NOTE   Get Latest version\r\n           https:\/\/github.com\/Rykka\/colorv.vim\/\r\n\r\n    NOTE   webapi.vim_ is needed for fetching schemes online.\r\n\r\n.. _webapi.vim: https:\/\/github.com\/mattn\/webapi-vim \r\n\r\n","first_name":"Rykka","6":"Rykka","last_name":"f","7":"f","releases":[{"0":"3597","vim_version":"7.0","1":"7.0","script_version":"3.0.2","2":"3.0.2","version_comment":"  - add back_buf for all win. \r\n  - add scheme fetch info. \r\n  - fix scheme nav arrow pos. \r\n","3":"  - add back_buf for all win. \r\n  - add scheme fetch info. \r\n  - fix scheme nav arrow pos. \r\n","package":"colorv.vim-3.0.2.zip","4":"colorv.vim-3.0.2.zip","src_id":"19270","5":"19270","creation_date":"1356959345","6":"1356959345"},{"0":"3597","vim_version":"7.0","1":"7.0","script_version":"3.0.1","2":"3.0.1","version_comment":"  - fix debug message: miss cache file.\r\n  - fix scheme navigation with key.\r\n  - update image.\r\n","3":"  - fix debug message: miss cache file.\r\n  - fix scheme navigation with key.\r\n  - update image.\r\n","package":"colorv.vim-3.0.1.zip","4":"colorv.vim-3.0.1.zip","src_id":"19269","5":"19269","creation_date":"1356952945","6":"1356952945"},{"0":"3597","vim_version":"7.0","1":"7.0","script_version":"3.0","2":"3.0","version_comment":"- add Scheme (fetch from Kuler\/ColorLover, fav, edit, new)\r\n- see detail in https:\/\/github.com\/Rykka\/colorv.vim#done","3":"- add Scheme (fetch from Kuler\/ColorLover, fav, edit, new)\r\n- see detail in https:\/\/github.com\/Rykka\/colorv.vim#done","package":"colorv.vim-3.0.zip","4":"colorv.vim-3.0.zip","src_id":"19259","5":"19259","creation_date":"1356890402","6":"1356890402"},{"0":"3597","vim_version":"7.0","1":"7.0","script_version":"2.5.6","2":"2.5.6","version_comment":"\"  add color mark\r\n\" change repo to colorv.vim","3":"\"  add color mark\r\n\" change repo to colorv.vim","package":"colorv.vim-2.5.6.zip","4":"colorv.vim-2.5.6.zip","src_id":"17932","5":"17932","creation_date":"1336738819","6":"1336738819"},{"0":"3597","vim_version":"7.0","1":"7.0","script_version":"2.5.6","2":"2.5.6","version_comment":"\" optimize Core\/Prev\/Text parts , fix bugs.\r\n\" seperate python part and add colorpicker.c\r\n\" more in changelog","3":"\" optimize Core\/Prev\/Text parts , fix bugs.\r\n\" seperate python part and add colorpicker.c\r\n\" more in changelog","package":"Rykka-ColorV-2.5.6.zip","4":"Rykka-ColorV-2.5.6.zip","src_id":"17818","5":"17818","creation_date":"1335430004","6":"1335430004"},{"0":"3597","vim_version":"7.0","1":"7.0","script_version":"2.5.4","2":"2.5.4","version_comment":"    Cleaning and tuning. \r\n    Better support for Galaxy.vim\r\n    infoline status showing\r\n    CMYK format support","3":"    Cleaning and tuning. \r\n    Better support for Galaxy.vim\r\n    infoline status showing\r\n    CMYK format support","package":"ColorV-2.5.4.tar.gz","4":"ColorV-2.5.4.tar.gz","src_id":"17294","5":"17294","creation_date":"1327247917","6":"1327247917"},{"0":"3597","vim_version":"7.0","1":"7.0","script_version":"2.5.1","2":"2.5.1","version_comment":"- Bug fixes.\r\n+ auto preview css files.\r\n+ preview() faster with coding in python.","3":"- Bug fixes.\r\n+ auto preview css files.\r\n+ preview() faster with coding in python.","package":"ColorV_2.5.1.tar.gz","4":"ColorV_2.5.1.tar.gz","src_id":"16433","5":"16433","creation_date":"1314973399","6":"1314973399"}]},"3596":{"script_id":"3596","0":"3596","script_name":"Fanfou.vim","1":"Fanfou.vim","script_type":"utility","2":"utility","summary":"This is a Vim plugin for Fanfou (饭否)","3":"This is a Vim plugin for Fanfou (饭否)","description":"The fanfou.vim plugin is a simple UNOFFICIAL client for Fanfou.com (饭否), it allows you\r\nto check timeline and update status via Vim.\r\n\r\nNOTE: fanfou.vim requires Vim to be compiled with Python bindings. \r\n              It needs Vim with Python3 bindings after v0.50.\r\n\r\n\r\nThis plugin defines four commands:\r\n\r\n    FanTimeline - View latest timeline from Fanfou in preview window\r\n    FanUpdate - Update status in command line\r\n    FanUpline - Send the line which is cursor on\r\n    FanRT - Retweet the line which is cursor on\r\n\r\nDefault key mappings:\r\n\r\n    <leader>fft is mapped to FanTimeline,\r\n    <leader>ffu is mapped to FanUpdate,\r\n    <leader>ffs is mapped to FanUpline.\r\n    <leader>ffr is mapped to FanRT.\r\n\r\nSee more help information in source code.\r\n\r\n\r\nLinks:\r\n\r\n    * Github https:\/\/github.com\/Vayn\/Fanfou\r\n","4":"The fanfou.vim plugin is a simple UNOFFICIAL client for Fanfou.com (饭否), it allows you\r\nto check timeline and update status via Vim.\r\n\r\nNOTE: fanfou.vim requires Vim to be compiled with Python bindings. \r\n              It needs Vim with Python3 bindings after v0.50.\r\n\r\n\r\nThis plugin defines four commands:\r\n\r\n    FanTimeline - View latest timeline from Fanfou in preview window\r\n    FanUpdate - Update status in command line\r\n    FanUpline - Send the line which is cursor on\r\n    FanRT - Retweet the line which is cursor on\r\n\r\nDefault key mappings:\r\n\r\n    <leader>fft is mapped to FanTimeline,\r\n    <leader>ffu is mapped to FanUpdate,\r\n    <leader>ffs is mapped to FanUpline.\r\n    <leader>ffr is mapped to FanRT.\r\n\r\nSee more help information in source code.\r\n\r\n\r\nLinks:\r\n\r\n    * Github https:\/\/github.com\/Vayn\/Fanfou\r\n","install_details":"Extract the zipfile and place the file as follows:\r\n\r\n>\r\n    <your runtime directory>\/plugin\/fanfou.vim\r\n    ...\r\n<\r\n\r\nIn order to communicate with Fanfou you have to set your Fanfou account,\r\nyou can set them using: \r\n\r\n    let g:fanfou_login = \"Username:Password\"\r\n\r\nor add this into your ~\/.vimrc\r\n","5":"Extract the zipfile and place the file as follows:\r\n\r\n>\r\n    <your runtime directory>\/plugin\/fanfou.vim\r\n    ...\r\n<\r\n\r\nIn order to communicate with Fanfou you have to set your Fanfou account,\r\nyou can set them using: \r\n\r\n    let g:fanfou_login = \"Username:Password\"\r\n\r\nor add this into your ~\/.vimrc\r\n","first_name":"Vincent","6":"Vincent","last_name":"T.","7":"T.","releases":[{"0":"3596","vim_version":"7.0","1":"7.0","script_version":"0.50","2":"0.50","version_comment":"* Use Python3 bindings instead of Python2.\r\n* Optimize the code.","3":"* Use Python3 bindings instead of Python2.\r\n* Optimize the code.","package":"fanfou_0.50.zip","4":"fanfou_0.50.zip","src_id":"16326","5":"16326","creation_date":"1313955371","6":"1313955371"},{"0":"3596","vim_version":"7.0","1":"7.0","script_version":"0.42","2":"0.42","version_comment":"* New feature - RT a message \r\n* Keyword highlight \r\n* Press enter to copy link in the message","3":"* New feature - RT a message \r\n* Keyword highlight \r\n* Press enter to copy link in the message","package":"fanfou_0.42.zip","4":"fanfou_0.42.zip","src_id":"15750","5":"15750","creation_date":"1306617484","6":"1306617484"},{"0":"3596","vim_version":"7.0","1":"7.0","script_version":"0.3.1","2":"0.3.1","version_comment":"* Use Python module urllib2 instead of cURL\r\n* Minor code optimization","3":"* Use Python module urllib2 instead of cURL\r\n* Minor code optimization","package":"fanfou_0.3.1.zip","4":"fanfou_0.3.1.zip","src_id":"15738","5":"15738","creation_date":"1306417893","6":"1306417893"},{"0":"3596","vim_version":"7.0","1":"7.0","script_version":"0.2.0","2":"0.2.0","version_comment":"Added \"timeline window automatically closes\" and \"auto update\"","3":"Added \"timeline window automatically closes\" and \"auto update\"","package":"fanfou_0.2.0.zip","4":"fanfou_0.2.0.zip","src_id":"15721","5":"15721","creation_date":"1306291971","6":"1306291971"},{"0":"3596","vim_version":"7.0","1":"7.0","script_version":"0.1.1","2":"0.1.1","version_comment":"add source as app name in fanfou","3":"add source as app name in fanfou","package":"fanfou_0.1.1.zip","4":"fanfou_0.1.1.zip","src_id":"15707","5":"15707","creation_date":"1306236353","6":"1306236353"}]},"3595":{"script_id":"3595","0":"3595","script_name":"ethna-switch","1":"ethna-switch","script_type":"utility","2":"utility","summary":"PHP Ethna Action\/View\/Template File Switch Plugin.","3":"PHP Ethna Action\/View\/Template File Switch Plugin.","description":"PHP Ethna Action\/View\/Template File Switch Plugin.\r\n\r\nEthna PHP Web Application Framework\r\nhttp:\/\/ethna.jp\/\r\nhttp:\/\/translate.google.co.jp\/translate?js=n&prev=_t&hl=ja&ie=UTF-8&layout=2&eotf=1&sl=ja&tl=en&u=http%3A%2F%2Fethna.jp%2F&act=url\r\n\r\ncommand\r\n:ETA[ction]     open action file.\r\n:ETV[iew]       open view file.\r\n:ETT[emplate]   open template file.\r\n\r\ncompletion\r\n<C-X><C-A>      insert action file dir.\r\n<C-X><C-V>      insert view file dir.\r\n<C-X><C-T>      insert template file dir.\r\n","4":"PHP Ethna Action\/View\/Template File Switch Plugin.\r\n\r\nEthna PHP Web Application Framework\r\nhttp:\/\/ethna.jp\/\r\nhttp:\/\/translate.google.co.jp\/translate?js=n&prev=_t&hl=ja&ie=UTF-8&layout=2&eotf=1&sl=ja&tl=en&u=http%3A%2F%2Fethna.jp%2F&act=url\r\n\r\ncommand\r\n:ETA[ction]     open action file.\r\n:ETV[iew]       open view file.\r\n:ETT[emplate]   open template file.\r\n\r\ncompletion\r\n<C-X><C-A>      insert action file dir.\r\n<C-X><C-V>      insert view file dir.\r\n<C-X><C-T>      insert template file dir.\r\n","install_details":"copy ethna-switch.vim into your plugin directory.","5":"copy ethna-switch.vim into your plugin directory.","first_name":"omi","6":"omi","last_name":"taku","7":"taku","releases":[{"0":"3595","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"vim-ethna-switch.zip","4":"vim-ethna-switch.zip","src_id":"15685","5":"15685","creation_date":"1305882445","6":"1305882445"}]},"3594":{"script_id":"3594","0":"3594","script_name":"ucompleteme","1":"ucompleteme","script_type":"utility","2":"utility","summary":"better code completion for vim","3":"better code completion for vim","description":"Overview\r\n--------\r\n\r\nOn Github: https:\/\/github.com\/aaronj1335\/ucompleteme\r\n\r\n`ucompleteme` is a Vim plugin for insert-mode completion.  It combines the\r\nresults of omni-completion with its own \"proximity\" completion function.\r\n\r\n`ucompleteme` attempts to provide completion options intelligently, so the user\r\ndoesn't have to think about what kind of code completion to use\r\n([omni-completion](http:\/\/vimdoc.sourceforge.net\/htmldoc\/insert.html#i_CTRL-X_CTRL-O),\r\n[current file completion](http:\/\/vimdoc.sourceforge.net\/htmldoc\/insert.html#i_CTRL-X_CTRL-N),\r\netc.).  Plugins like\r\n[SuperTab](http:\/\/www.vim.org\/scripts\/script.php?script_id=1643) provide a\r\nmeans to easily switch between different completion methods, but they aren't as\r\nopinionated about building the list of matches for the user.\r\n\r\nThe philosophy behind `ucompleteme` is that instead of having to think about\r\nwhich completion type is best, the completion funciton should make an educated\r\nguess by first running the omni-completion function (where available), then\r\nfinding matches within the current buffer, then other buffers of the same\r\nfiletype, and finally the remaining buffers.\r\n\r\n\r\nDetails\r\n-------\r\n\r\n`ucompleteme` provides a [user-defined completion function](http:\/\/vimdoc.sourceforge.net\/htmldoc\/insert.html#i_CTRL-X_CTRL-U).\r\nBy default it re-maps `<tab>` in insert mode to use this function.  If an\r\nomnifuc is defined, `ucompletme` starts by populating the list with those\r\nresults first and giving the user a chance to interact.  After that it will run\r\nits own \"proximity\" completion function that searches each line of a buffer\r\nprogressively further from the cursor.  The proximity search is run on the\r\ncurrent buffer, and then the other buffers of the same filetype, and finally\r\nthe remaining open buffers.\r\n\r\n\r\nOptions\r\n-------\r\n\r\n - **g:ucompleteme\\_map\\_tab**: if this is set to 1, `ucompleteme` will re-map\r\n   `<tab>` in insert mode\r\n\r\n - **g:max\\_lines\\_for\\_omnifunc**: omni-completion functions can be slow for\r\n   large files.  this determines how large a file can be before `ucompleteme`\r\n   will not skip using omni-completion and just use keyword completion.\r\n\r\n\r\n\r\n","4":"Overview\r\n--------\r\n\r\nOn Github: https:\/\/github.com\/aaronj1335\/ucompleteme\r\n\r\n`ucompleteme` is a Vim plugin for insert-mode completion.  It combines the\r\nresults of omni-completion with its own \"proximity\" completion function.\r\n\r\n`ucompleteme` attempts to provide completion options intelligently, so the user\r\ndoesn't have to think about what kind of code completion to use\r\n([omni-completion](http:\/\/vimdoc.sourceforge.net\/htmldoc\/insert.html#i_CTRL-X_CTRL-O),\r\n[current file completion](http:\/\/vimdoc.sourceforge.net\/htmldoc\/insert.html#i_CTRL-X_CTRL-N),\r\netc.).  Plugins like\r\n[SuperTab](http:\/\/www.vim.org\/scripts\/script.php?script_id=1643) provide a\r\nmeans to easily switch between different completion methods, but they aren't as\r\nopinionated about building the list of matches for the user.\r\n\r\nThe philosophy behind `ucompleteme` is that instead of having to think about\r\nwhich completion type is best, the completion funciton should make an educated\r\nguess by first running the omni-completion function (where available), then\r\nfinding matches within the current buffer, then other buffers of the same\r\nfiletype, and finally the remaining buffers.\r\n\r\n\r\nDetails\r\n-------\r\n\r\n`ucompleteme` provides a [user-defined completion function](http:\/\/vimdoc.sourceforge.net\/htmldoc\/insert.html#i_CTRL-X_CTRL-U).\r\nBy default it re-maps `<tab>` in insert mode to use this function.  If an\r\nomnifuc is defined, `ucompletme` starts by populating the list with those\r\nresults first and giving the user a chance to interact.  After that it will run\r\nits own \"proximity\" completion function that searches each line of a buffer\r\nprogressively further from the cursor.  The proximity search is run on the\r\ncurrent buffer, and then the other buffers of the same filetype, and finally\r\nthe remaining open buffers.\r\n\r\n\r\nOptions\r\n-------\r\n\r\n - **g:ucompleteme\\_map\\_tab**: if this is set to 1, `ucompleteme` will re-map\r\n   `<tab>` in insert mode\r\n\r\n - **g:max\\_lines\\_for\\_omnifunc**: omni-completion functions can be slow for\r\n   large files.  this determines how large a file can be before `ucompleteme`\r\n   will not skip using omni-completion and just use keyword completion.\r\n\r\n\r\n\r\n","install_details":"Installation\r\n------------\r\n\r\nPut the \"ucompleteme.vim\" file in your [Vim Runtimepath][1]'s autoload\r\ndirecory:\r\n\r\n - On Linux\/Mac OS X: `~\/.vim\/autoload`\r\n\r\n - On Windows: `$HOME\/vimfiles\/autoload`\r\n\r\nIf you're using a Vim package manager like [Tim Pope][3]'s [pathogen][4], then\r\nyou should be able to just clone this repository into the \"bundles\" directory.\r\n\r\nFinally, add the following to your [.vimrc][2]:\r\n\r\n\tcall ucompleteme#Setup()\r\n\r\n\r\n[1]: http:\/\/vimdoc.sourceforge.net\/htmldoc\/options.html#'runtimepath' \"Vim Runtimepath\"\r\n[2]: http:\/\/vimdoc.sourceforge.net\/htmldoc\/starting.html#.vimrc \".vimrc\"\r\n[3]: http:\/\/tpo.pe\/ \"Tim Pope\"\r\n[4]: http:\/\/www.vim.org\/scripts\/script.php?script_id=2332 \"pathogen\"","5":"Installation\r\n------------\r\n\r\nPut the \"ucompleteme.vim\" file in your [Vim Runtimepath][1]'s autoload\r\ndirecory:\r\n\r\n - On Linux\/Mac OS X: `~\/.vim\/autoload`\r\n\r\n - On Windows: `$HOME\/vimfiles\/autoload`\r\n\r\nIf you're using a Vim package manager like [Tim Pope][3]'s [pathogen][4], then\r\nyou should be able to just clone this repository into the \"bundles\" directory.\r\n\r\nFinally, add the following to your [.vimrc][2]:\r\n\r\n\tcall ucompleteme#Setup()\r\n\r\n\r\n[1]: http:\/\/vimdoc.sourceforge.net\/htmldoc\/options.html#'runtimepath' \"Vim Runtimepath\"\r\n[2]: http:\/\/vimdoc.sourceforge.net\/htmldoc\/starting.html#.vimrc \".vimrc\"\r\n[3]: http:\/\/tpo.pe\/ \"Tim Pope\"\r\n[4]: http:\/\/www.vim.org\/scripts\/script.php?script_id=2332 \"pathogen\"","first_name":"Aaron","6":"Aaron","last_name":"Stacy","7":"Stacy","releases":[{"0":"3594","vim_version":"7.0","1":"7.0","script_version":"0.1.1","2":"0.1.1","version_comment":"Search across all buffers","3":"Search across all buffers","package":"ucompleteme.tar.gz","4":"ucompleteme.tar.gz","src_id":"15741","5":"15741","creation_date":"1306469515","6":"1306469515"},{"0":"3594","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"ucompleteme.tar.gz","4":"ucompleteme.tar.gz","src_id":"15682","5":"15682","creation_date":"1305861127","6":"1305861127"}]},"3593":{"script_id":"3593","0":"3593","script_name":"pdub","1":"pdub","script_type":"utility","2":"utility","summary":"dead simple vim-based password managment","3":"dead simple vim-based password managment","description":"Overview\r\n--------\r\n\r\nOn Github: https:\/\/github.com\/aaronj1335\/pdub\r\n\r\nIt's dead simple.  Run `pdub`, and you get a blank buffer in vim.  Enter your\r\npasswords and personal info.  Type \":wq\", and `pdub` encrypts the buffer and\r\nstores it in your home directory where only you can get to it.  Next time you\r\nrun it, `pdub` will decrypt the file, throw that into a buffer for your, and\r\nyou're back in business.\r\n\r\n`pdub` is a small Python script.  That's good because it keeps things simple,\r\nand no one wants complications when it comes to personal data.\r\n\r\n`pdub` doesn't save your decryption passphrase or plain text passwords to any\r\ntemporary files.  It doesn't use `gpg`'s \"--passphrase\" option.  It uses pipes\r\nlike a good plumber so your passwords don't get spilled all over the place.\r\n\r\nNeed to recover your passwords without `pdub`?  Just run the following:\r\n\r\n\t$ gpg -d ~\/.pdub\/pdubs.json.gpg\r\n\r\n\r\nRequirements\r\n------------\r\n\r\n - a POSIX system\r\n - Python >= 2.6 (RHEL5 be dammned)\r\n - vim compiled with Pyton support\r\n - [GnuPG](http:\/\/www.gnupg.org\/)\r\n\r\n\r\nDetails\r\n-------\r\n\r\n`pdub` uses `gpg` with the --symmetric flag for encryption.  The file is stored\r\nin the `~\/.pdub` directory.  If this isn't there it creates it for you.  The\r\ndirectory must have 700 permissions and the actual file is stored with 600\r\npermissions.\r\n\r\n\r\nThings That Still Need Work\r\n---------------------------\r\n\r\n`pdub` assumes that you're storing your passwords in JSON.  Most people\r\nprobably don't want that.  There should be some configuration file where users\r\ncan specify file types and other preferences (like a .pdubrc).\r\n\r\nIt would also be cool if `pdub` integrated with Dropbox.  Don't get me wrong,\r\nI'd never put my passwords out there like that, but since it's an encrypted\r\nfile there's probably people who would feel safe doing so.","4":"Overview\r\n--------\r\n\r\nOn Github: https:\/\/github.com\/aaronj1335\/pdub\r\n\r\nIt's dead simple.  Run `pdub`, and you get a blank buffer in vim.  Enter your\r\npasswords and personal info.  Type \":wq\", and `pdub` encrypts the buffer and\r\nstores it in your home directory where only you can get to it.  Next time you\r\nrun it, `pdub` will decrypt the file, throw that into a buffer for your, and\r\nyou're back in business.\r\n\r\n`pdub` is a small Python script.  That's good because it keeps things simple,\r\nand no one wants complications when it comes to personal data.\r\n\r\n`pdub` doesn't save your decryption passphrase or plain text passwords to any\r\ntemporary files.  It doesn't use `gpg`'s \"--passphrase\" option.  It uses pipes\r\nlike a good plumber so your passwords don't get spilled all over the place.\r\n\r\nNeed to recover your passwords without `pdub`?  Just run the following:\r\n\r\n\t$ gpg -d ~\/.pdub\/pdubs.json.gpg\r\n\r\n\r\nRequirements\r\n------------\r\n\r\n - a POSIX system\r\n - Python >= 2.6 (RHEL5 be dammned)\r\n - vim compiled with Pyton support\r\n - [GnuPG](http:\/\/www.gnupg.org\/)\r\n\r\n\r\nDetails\r\n-------\r\n\r\n`pdub` uses `gpg` with the --symmetric flag for encryption.  The file is stored\r\nin the `~\/.pdub` directory.  If this isn't there it creates it for you.  The\r\ndirectory must have 700 permissions and the actual file is stored with 600\r\npermissions.\r\n\r\n\r\nThings That Still Need Work\r\n---------------------------\r\n\r\n`pdub` assumes that you're storing your passwords in JSON.  Most people\r\nprobably don't want that.  There should be some configuration file where users\r\ncan specify file types and other preferences (like a .pdubrc).\r\n\r\nIt would also be cool if `pdub` integrated with Dropbox.  Don't get me wrong,\r\nI'd never put my passwords out there like that, but since it's an encrypted\r\nfile there's probably people who would feel safe doing so.","install_details":"Put it anywhere in your $PATH.  Don't remove the *.py extension","5":"Put it anywhere in your $PATH.  Don't remove the *.py extension","first_name":"Aaron","6":"Aaron","last_name":"Stacy","7":"Stacy","releases":[{"0":"3593","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"pdub.py","4":"pdub.py","src_id":"15679","5":"15679","creation_date":"1305856219","6":"1305856219"}]},"3592":{"script_id":"3592","0":"3592","script_name":"jovial.vim","1":"jovial.vim","script_type":"syntax","2":"syntax","summary":"syntax for JOVIAL (J73) programming language","3":"syntax for JOVIAL (J73) programming language","description":"Supported file suffixes: *.j73, *.jov, *.jovial\r\n\r\nThis archive contains Vim syntax highlighting for the JOVIAL programming language.\r\n\r\nIt's designed for the J73 dialect (MIL-STD-1589C), but works with other versions. A simple piece of JOVIAL code can be found in the file sample.j73. After installation, you should be able to open that file with Vim and get color syntax highlighting.\r\n\r\nFor more information about JOVIAL, please see:\r\nhttp:\/\/en.wikipedia.org\/wiki\/JOVIAL\r\n\r\nI have uploaded a copy of MIL-STD-1589C to:\r\nhttp:\/\/www.scribd.com\/doc\/44512382\/JOVIAL-J73-Computer-Programming-Language-1984-MIL-STD-1589C\r\n","4":"Supported file suffixes: *.j73, *.jov, *.jovial\r\n\r\nThis archive contains Vim syntax highlighting for the JOVIAL programming language.\r\n\r\nIt's designed for the J73 dialect (MIL-STD-1589C), but works with other versions. A simple piece of JOVIAL code can be found in the file sample.j73. After installation, you should be able to open that file with Vim and get color syntax highlighting.\r\n\r\nFor more information about JOVIAL, please see:\r\nhttp:\/\/en.wikipedia.org\/wiki\/JOVIAL\r\n\r\nI have uploaded a copy of MIL-STD-1589C to:\r\nhttp:\/\/www.scribd.com\/doc\/44512382\/JOVIAL-J73-Computer-Programming-Language-1984-MIL-STD-1589C\r\n","install_details":"This archive contains two directories, ftdetect and syntax. Each directory has a file called jovial.vim. Copy both directories into ~\/.vim, where ~ is your home directory.\r\n","5":"This archive contains two directories, ftdetect and syntax. Each directory has a file called jovial.vim. Copy both directories into ~\/.vim, where ~ is your home directory.\r\n","first_name":"Paul","6":"Paul","last_name":"McGinnis","7":"McGinnis","releases":[{"0":"3592","vim_version":"6.0","1":"6.0","script_version":"1.2","2":"1.2","version_comment":"* Changed use of HiLink to hi def link per request from Bram\r\n* Added keywords that are extensions to JOVIAL.\r\n","3":"* Changed use of HiLink to hi def link per request from Bram\r\n* Added keywords that are extensions to JOVIAL.\r\n","package":"jovial_syntax-1.2.tar.gz","4":"jovial_syntax-1.2.tar.gz","src_id":"15922","5":"15922","creation_date":"1308357760","6":"1308357760"},{"0":"3592","vim_version":"6.0","1":"6.0","script_version":"1.1","2":"1.1","version_comment":"* Fixed code to allow ' characters in variable names. This'is'crazy is a legitimate JOVIAL variable name!\r\n* Added support for floating point data types.\r\n* Added support for binary \"bead\" data types.\r\n* Added standard TODO, FIXME, and XXX tags in comments, as in other syntaxes.\r\n* Changed code to allow for generic directives instead of specific values such as !COMPOOL.\r\n* Added optional rounding parameters R T and Z to integer and floating types.\r\n* Split machine specific parameters into constants and functions. For example, BITSINBYTE is a\r\nconstant, but BYTEPOS() is a function.\r\n","3":"* Fixed code to allow ' characters in variable names. This'is'crazy is a legitimate JOVIAL variable name!\r\n* Added support for floating point data types.\r\n* Added support for binary \"bead\" data types.\r\n* Added standard TODO, FIXME, and XXX tags in comments, as in other syntaxes.\r\n* Changed code to allow for generic directives instead of specific values such as !COMPOOL.\r\n* Added optional rounding parameters R T and Z to integer and floating types.\r\n* Split machine specific parameters into constants and functions. For example, BITSINBYTE is a\r\nconstant, but BYTEPOS() is a function.\r\n","package":"jovial_syntax-1.1.tgz","4":"jovial_syntax-1.1.tgz","src_id":"15770","5":"15770","creation_date":"1306809406","6":"1306809406"}]},"3591":{"script_id":"3591","0":"3591","script_name":"browserprint","1":"browserprint","script_type":"utility","2":"utility","summary":"Prints text files to the browser","3":"Prints text files to the browser","description":"Usage\r\n=====\r\n\r\nAdds a new command, `:BrowserPrint`, which will send the contents of the current\r\nbuffer to a new browser window (or tab) in HTML, preserving the current font,\r\nformatting, and encoding.\r\n\r\nJust run `:BrowserPrint`, and watch the magic.\r\n\r\nWhy?\r\n====\r\n\r\nPrinting from MacVim opens a PDF in Preview, with monospace font and the\r\nencoding completely lost. Other GUI vims may have similar problems. This is a\r\nworkaround that relies on HTML and a decent web browser to preserve the\r\nformatting nicely.\r\n\r\nThe idea is to send it to the browser, then use the browser's built-in print\r\nfunctionality.\r\n\r\nLimitations\r\n===========\r\n- Requires Python support in Vim\r\n- Should work on Windows\/Linux but not tested (yet!)\r\n- HTML content in the file will screw up the output as it isn't escaped\r\n","4":"Usage\r\n=====\r\n\r\nAdds a new command, `:BrowserPrint`, which will send the contents of the current\r\nbuffer to a new browser window (or tab) in HTML, preserving the current font,\r\nformatting, and encoding.\r\n\r\nJust run `:BrowserPrint`, and watch the magic.\r\n\r\nWhy?\r\n====\r\n\r\nPrinting from MacVim opens a PDF in Preview, with monospace font and the\r\nencoding completely lost. Other GUI vims may have similar problems. This is a\r\nworkaround that relies on HTML and a decent web browser to preserve the\r\nformatting nicely.\r\n\r\nThe idea is to send it to the browser, then use the browser's built-in print\r\nfunctionality.\r\n\r\nLimitations\r\n===========\r\n- Requires Python support in Vim\r\n- Should work on Windows\/Linux but not tested (yet!)\r\n- HTML content in the file will screw up the output as it isn't escaped\r\n","install_details":"","5":"","first_name":"Rob","6":"Rob","last_name":"O'Dwyer","7":"O'Dwyer","releases":[{"0":"3591","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"browserprint.zip","4":"browserprint.zip","src_id":"15674","5":"15674","creation_date":"1305765557","6":"1305765557"}]},"3590":{"script_id":"3590","0":"3590","script_name":"vim-coffee-script","1":"vim-coffee-script","script_type":"utility","2":"utility","summary":"CoffeeScript support for vim","3":"CoffeeScript support for vim","description":"This plugin adds support for CoffeeScript. It handles syntax, indenting, and compiling. Also included is an eco syntax and support for CoffeeScript in Haml and HTML.\r\n\r\nPlease see the project page for much more information:\r\nhttp:\/\/github.com\/kchmck\/vim-coffee-script","4":"This plugin adds support for CoffeeScript. It handles syntax, indenting, and compiling. Also included is an eco syntax and support for CoffeeScript in Haml and HTML.\r\n\r\nPlease see the project page for much more information:\r\nhttp:\/\/github.com\/kchmck\/vim-coffee-script","install_details":"Unzip the archive into .vim.\r\n\r\nSince this plugin has rolling versions based on git commits, it may be more convenient to install and upgrade it using pathogen and git. The readme has instructions for doing this:\r\nhttp:\/\/github.com\/kchmck\/vim-coffee-script#readme","5":"Unzip the archive into .vim.\r\n\r\nSince this plugin has rolling versions based on git commits, it may be more convenient to install and upgrade it using pathogen and git. The readme has instructions for doing this:\r\nhttp:\/\/github.com\/kchmck\/vim-coffee-script#readme","first_name":"Mick","6":"Mick","last_name":"Koch","7":"Koch","releases":[{"0":"3590","vim_version":"7.4","1":"7.4","script_version":"v003","2":"v003","version_comment":"Almost 3 years' worth of fixes and (hopefully) improvements.","3":"Almost 3 years' worth of fixes and (hopefully) improvements.","package":"vim-coffee-script-v003.zip","4":"vim-coffee-script-v003.zip","src_id":"22513","5":"22513","creation_date":"1412949313","6":"1412949313"},{"0":"3590","vim_version":"7.3","1":"7.3","script_version":"v002","2":"v002","version_comment":"Added binary numbers (0b0101) and fixed some bugs (#9, #62, #63, #65).","3":"Added binary numbers (0b0101) and fixed some bugs (#9, #62, #63, #65).","package":"vim-coffee-script-v002.zip","4":"vim-coffee-script-v002.zip","src_id":"17028","5":"17028","creation_date":"1323097918","6":"1323097918"},{"0":"3590","vim_version":"7.3","1":"7.3","script_version":"v001","2":"v001","version_comment":"Removed deprecated `coffee_folding` option, added `coffee_compile_vert` option,\r\nsplit out compiler, fixed indentation and syntax bugs, and added Haml support\r\nand omnicompletion.","3":"Removed deprecated `coffee_folding` option, added `coffee_compile_vert` option,\r\nsplit out compiler, fixed indentation and syntax bugs, and added Haml support\r\nand omnicompletion.","package":"vim-coffee-script-v001.zip","4":"vim-coffee-script-v001.zip","src_id":"16701","5":"16701","creation_date":"1318978914","6":"1318978914"},{"0":"3590","vim_version":"7.3","1":"7.3","script_version":"36cb865","2":"36cb865","version_comment":"Added watch and vertical modes to CoffeeCompile, fixed HTML rendering\n","3":"Added watch and vertical modes to CoffeeCompile, fixed HTML rendering\n","package":"vim-coffee-script-36cb865.zip","4":"vim-coffee-script-36cb865.zip","src_id":"16254","5":"16254","creation_date":"1313237696","6":"1313237696"},{"0":"3590","vim_version":"7.3","1":"7.3","script_version":"cf244b1","2":"cf244b1","version_comment":"Reworked highlighting, small bug fixes, deprecated coffee_folding","3":"Reworked highlighting, small bug fixes, deprecated coffee_folding","package":"vim-coffee-script-cf244b1.zip","4":"vim-coffee-script-cf244b1.zip","src_id":"16233","5":"16233","creation_date":"1313018888","6":"1313018888"},{"0":"3590","vim_version":"7.3","1":"7.3","script_version":"f4d2fbf","2":"f4d2fbf","version_comment":"Fixes some eco and interpolation bugs","3":"Fixes some eco and interpolation bugs","package":"vim-coffee-script-f4d2fbf.zip","4":"vim-coffee-script-f4d2fbf.zip","src_id":"16124","5":"16124","creation_date":"1311278305","6":"1311278305"},{"0":"3590","vim_version":"7.0","1":"7.0","script_version":"e3cc7ec","2":"e3cc7ec","version_comment":"CoffeeCompile fixes, removed coffee_compile_on_save","3":"CoffeeCompile fixes, removed coffee_compile_on_save","package":"vim-coffee-script-e3cc7ec.zip","4":"vim-coffee-script-e3cc7ec.zip","src_id":"16061","5":"16061","creation_date":"1310222572","6":"1310222572"},{"0":"3590","vim_version":"7.0","1":"7.0","script_version":"c4df62e","2":"c4df62e","version_comment":"Syntax-highlighted CoffeeCompile","3":"Syntax-highlighted CoffeeCompile","package":"vim-coffee-script-c4df62e.zip","4":"vim-coffee-script-c4df62e.zip","src_id":"15947","5":"15947","creation_date":"1308677248","6":"1308677248"},{"0":"3590","vim_version":"7.0","1":"7.0","script_version":" fd170cb","2":" fd170cb","version_comment":"CoffeeRun command, indenting now strips trailing comments, and other small fixes","3":"CoffeeRun command, indenting now strips trailing comments, and other small fixes","package":"vim-coffee-script-fd170cb.zip","4":"vim-coffee-script-fd170cb.zip","src_id":"15871","5":"15871","creation_date":"1307981667","6":"1307981667"},{"0":"3590","vim_version":"7.0","1":"7.0","script_version":"1b4957f","2":"1b4957f","version_comment":"Small optimizations","3":"Small optimizations","package":"vim-coffee-script-1b4957f.zip","4":"vim-coffee-script-1b4957f.zip","src_id":"15692","5":"15692","creation_date":"1305978896","6":"1305978896"},{"0":"3590","vim_version":"7.0","1":"7.0","script_version":"baabe64","2":"baabe64","version_comment":"Initial upload","3":"Initial upload","package":"vim-coffee-script-baabe64.zip","4":"vim-coffee-script-baabe64.zip","src_id":"15664","5":"15664","creation_date":"1305676145","6":"1305676145"}]},"3589":{"script_id":"3589","0":"3589","script_name":"cake.vim","1":"cake.vim","script_type":"utility","2":"utility","summary":"Utility for CakePHP developers.","3":"Utility for CakePHP developers.","description":"cake.vim is for easy jumping between Controller, Model and View files when developing in CakePHP. \r\n\r\nThe latest version is in github. \r\nhttps:\/\/github.com\/violetyk\/cake.vim\r\n\r\nRequirements:\r\n- Vim ver.7.3 or heigher \r\n- CakePHP ver.1.3.x or ver.2.x\r\n\r\nEasy to use:\r\n\r\nAt the first, specified the app directory of your CakePHP.\r\n\r\n:Cakephp \/path\/to\/cakephp_app\/\r\n\r\n\r\nIf you write the following key-mappings in your .vimrc, it will\r\nperform automatically at startup.\r\n\r\n    let g:cakephp_enable_fix_mode = 1\r\n    let g:cakephp_app = \"\/path\/to\/cakephp_app\/\"\r\n\r\nWhen you find a project from open file automatically,\r\nplease set it as follows.\r\n\r\n    let g:cakephp_enable_auto_mode = 1 \r\n\r\n\r\nEdit the specified or current controller.\r\n:Ccontroller hogehoges\r\nIt guess the Controller when current buffer is View or Model.\r\n:Controller\r\n\r\n\r\nEdit the specified controller's view.\r\nwhen current buffer is controller.\r\n:Cview index\r\n\r\nEdit the specified or current view( and use theme name).\r\n:Cview index mytheme\r\n\r\n\r\nEdit the specified or current model.\r\n:Cmodel hogehoge\r\nIt guess the Model when current buffer is Controller.\r\n:Cmodel\r\n\r\n\r\nEdit the specified config.\r\n:Cconfig hogehoge\r\n\r\n\r\nEdit the specified component.\r\n:Ccomponent hogehoge\r\n\r\n\r\nEdit the specified behavior.\r\n:Cbehavior hogehoge\r\n\r\n\r\nEdit the specified helper.\r\n:Chelper hogehoge\r\n\r\n\r\nEdit the specified shell.\r\n:Cshell hogehoge\r\n\r\n\r\nEdit the specified task.\r\n:Ctask hogehoge\r\n\r\n\r\nEdit the specified test case.\r\n:Ctestmodel hoge\r\n:Ctestbehavior hoge\r\n:Ctestcomponent hoge\r\n:Ctestcontroller hoge\r\n:Ctesthelper hoge\r\n\r\nwhen current buffer is Model or Behavior or Component,\r\n or Controller or Helper or Fixture.\r\n:Ctest\r\n\r\n\r\nEdit the specified fixture.\r\n:Cfixture hoge\r\nIt guess the Fixture when current buffer is Model.\r\n:Cfixture\r\n\r\n\r\nEdit the debug.log.\r\n:Clog debug","4":"cake.vim is for easy jumping between Controller, Model and View files when developing in CakePHP. \r\n\r\nThe latest version is in github. \r\nhttps:\/\/github.com\/violetyk\/cake.vim\r\n\r\nRequirements:\r\n- Vim ver.7.3 or heigher \r\n- CakePHP ver.1.3.x or ver.2.x\r\n\r\nEasy to use:\r\n\r\nAt the first, specified the app directory of your CakePHP.\r\n\r\n:Cakephp \/path\/to\/cakephp_app\/\r\n\r\n\r\nIf you write the following key-mappings in your .vimrc, it will\r\nperform automatically at startup.\r\n\r\n    let g:cakephp_enable_fix_mode = 1\r\n    let g:cakephp_app = \"\/path\/to\/cakephp_app\/\"\r\n\r\nWhen you find a project from open file automatically,\r\nplease set it as follows.\r\n\r\n    let g:cakephp_enable_auto_mode = 1 \r\n\r\n\r\nEdit the specified or current controller.\r\n:Ccontroller hogehoges\r\nIt guess the Controller when current buffer is View or Model.\r\n:Controller\r\n\r\n\r\nEdit the specified controller's view.\r\nwhen current buffer is controller.\r\n:Cview index\r\n\r\nEdit the specified or current view( and use theme name).\r\n:Cview index mytheme\r\n\r\n\r\nEdit the specified or current model.\r\n:Cmodel hogehoge\r\nIt guess the Model when current buffer is Controller.\r\n:Cmodel\r\n\r\n\r\nEdit the specified config.\r\n:Cconfig hogehoge\r\n\r\n\r\nEdit the specified component.\r\n:Ccomponent hogehoge\r\n\r\n\r\nEdit the specified behavior.\r\n:Cbehavior hogehoge\r\n\r\n\r\nEdit the specified helper.\r\n:Chelper hogehoge\r\n\r\n\r\nEdit the specified shell.\r\n:Cshell hogehoge\r\n\r\n\r\nEdit the specified task.\r\n:Ctask hogehoge\r\n\r\n\r\nEdit the specified test case.\r\n:Ctestmodel hoge\r\n:Ctestbehavior hoge\r\n:Ctestcomponent hoge\r\n:Ctestcontroller hoge\r\n:Ctesthelper hoge\r\n\r\nwhen current buffer is Model or Behavior or Component,\r\n or Controller or Helper or Fixture.\r\n:Ctest\r\n\r\n\r\nEdit the specified fixture.\r\n:Cfixture hoge\r\nIt guess the Fixture when current buffer is Model.\r\n:Cfixture\r\n\r\n\r\nEdit the debug.log.\r\n:Clog debug","install_details":"1: Extract the file and Put files in your Vim directory\r\n   (usually ~\/.vim\/).\r\n2: Execute |:Cakephp| <Space> \/path\/to\/cakephp_app\/ command or\r\nlet g:cakephp_enable_fix_mode = 1\r\nlet g:cakephp_app = \"\/path\/to\/cakephp_app\/\"\r\nin your .vimrc.\r\n\r\nWhen you find a project from open file automatically,\r\nplease set it as follows.\r\n\r\n    let g:cakephp_enable_auto_mode = 1\r\n\r\n\r\nAnd if you would like to use divided view themed such as \"front\" and \"admin\",\r\nlet g:cakephp_use_theme = \"admin\"\r\nadd the comment in your .vimrc.\r\n\r\n\r\nMySQL and Apache logs to see the log quickly, and write the following.\r\n>\r\n    let g:cakephp_log = {\r\n          \\ 'query' : '\/var\/log\/mysqld-query.log',\r\n          \\ 'access': '\/usr\/local\/apache2\/logs\/access_log'\r\n          \\ }\r\n<\r\n\r\nSorry, this plugin will not work well for windows at this time.\r\n\r\n\r\nMore comfortable to use cake.vim, if you write key-mappings in your .vimrc. \r\nHere is recommended key-mappings.\r\n\r\n    \" Recommended  key-mappings.\r\n    nnoremap <Space>cc :<C-u>Ccontroller\r\n    nnoremap <Space>cm :<C-u>Cmodel\r\n    nnoremap <Space>cv :<C-u>Cview\r\n    nnoremap <Space>cl :<C-u>Clog\r\n    nnoremap <Space>ccv :<C-u>Ccontrollerview\r\n    nnoremap <Space>ccm :<C-u>Ccomponent\r\n    nnoremap <Space>ccf :<C-u>Cconfig\r\n    nnoremap <Space>cb :<C-u>Cbehavior\r\n    nnoremap <Space>ch :<C-u>Chelper\r\n    nnoremap <Space>ct :<C-u>Ctest\r\n    nnoremap <Space>cf :<C-u>Cfixture\r\n    nnoremap <Space>cs :<C-u>Cshell\r\n","5":"1: Extract the file and Put files in your Vim directory\r\n   (usually ~\/.vim\/).\r\n2: Execute |:Cakephp| <Space> \/path\/to\/cakephp_app\/ command or\r\nlet g:cakephp_enable_fix_mode = 1\r\nlet g:cakephp_app = \"\/path\/to\/cakephp_app\/\"\r\nin your .vimrc.\r\n\r\nWhen you find a project from open file automatically,\r\nplease set it as follows.\r\n\r\n    let g:cakephp_enable_auto_mode = 1\r\n\r\n\r\nAnd if you would like to use divided view themed such as \"front\" and \"admin\",\r\nlet g:cakephp_use_theme = \"admin\"\r\nadd the comment in your .vimrc.\r\n\r\n\r\nMySQL and Apache logs to see the log quickly, and write the following.\r\n>\r\n    let g:cakephp_log = {\r\n          \\ 'query' : '\/var\/log\/mysqld-query.log',\r\n          \\ 'access': '\/usr\/local\/apache2\/logs\/access_log'\r\n          \\ }\r\n<\r\n\r\nSorry, this plugin will not work well for windows at this time.\r\n\r\n\r\nMore comfortable to use cake.vim, if you write key-mappings in your .vimrc. \r\nHere is recommended key-mappings.\r\n\r\n    \" Recommended  key-mappings.\r\n    nnoremap <Space>cc :<C-u>Ccontroller\r\n    nnoremap <Space>cm :<C-u>Cmodel\r\n    nnoremap <Space>cv :<C-u>Cview\r\n    nnoremap <Space>cl :<C-u>Clog\r\n    nnoremap <Space>ccv :<C-u>Ccontrollerview\r\n    nnoremap <Space>ccm :<C-u>Ccomponent\r\n    nnoremap <Space>ccf :<C-u>Cconfig\r\n    nnoremap <Space>cb :<C-u>Cbehavior\r\n    nnoremap <Space>ch :<C-u>Chelper\r\n    nnoremap <Space>ct :<C-u>Ctest\r\n    nnoremap <Space>cf :<C-u>Cfixture\r\n    nnoremap <Space>cs :<C-u>Cshell\r\n","first_name":"Yuhei","6":"Yuhei","last_name":"Kagaya","7":"Kagaya","releases":[{"0":"3589","vim_version":"7.3","1":"7.3","script_version":"2.13","2":"2.13","version_comment":"- Add New gf pattern. \"$this->extend('\/Common\/view')\" jump to the View file.\r\n- Fix bug.","3":"- Add New gf pattern. \"$this->extend('\/Common\/view')\" jump to the View file.\r\n- Fix bug.","package":"cake.zip","4":"cake.zip","src_id":"20903","5":"20903","creation_date":"1381393691","6":"1381393691"},{"0":"3589","vim_version":"7.3","1":"7.3","script_version":"2.12","2":"2.12","version_comment":"- Change from :Clib to :Ccore the name of command \r\n- Change from cake_lib to cake_core the name of unite source name \r\n- Add the feature to jump to the 1st party libraries \r\n  :Clib \r\n  Unite cake_lib \r\n- Improve mapping method, thanks to pekepeke. \r\n- Add g:cakephp_no_default_keymappings \r\n- Add autocmd event PluginCakephpInitializeAfter \r\n- Add g:cakephp_gf_fallback_n \r\n- Add g:cakephp_gf_fallback_s \r\n- Add g:cakephp_gf_fallback_t \r\n- Support Event, Test, TestSuite in cakephp2.x \r\n- Improve Ctestrun that can run single test case in cakephp2.x \r\n- Improve Ctestrun that can run asynchronously \r\n- Add :Ctestrunmethod \r\n- Add g:cakephp_test_window_vertical \r\n- Add g:cakephp_test_window_height \r\n- Add g:cakephp_test_window_width \r\n- Fix bug.","3":"- Change from :Clib to :Ccore the name of command \r\n- Change from cake_lib to cake_core the name of unite source name \r\n- Add the feature to jump to the 1st party libraries \r\n  :Clib \r\n  Unite cake_lib \r\n- Improve mapping method, thanks to pekepeke. \r\n- Add g:cakephp_no_default_keymappings \r\n- Add autocmd event PluginCakephpInitializeAfter \r\n- Add g:cakephp_gf_fallback_n \r\n- Add g:cakephp_gf_fallback_s \r\n- Add g:cakephp_gf_fallback_t \r\n- Support Event, Test, TestSuite in cakephp2.x \r\n- Improve Ctestrun that can run single test case in cakephp2.x \r\n- Improve Ctestrun that can run asynchronously \r\n- Add :Ctestrunmethod \r\n- Add g:cakephp_test_window_vertical \r\n- Add g:cakephp_test_window_height \r\n- Add g:cakephp_test_window_width \r\n- Fix bug.","package":"cake.zip","4":"cake.zip","src_id":"20793","5":"20793","creation_date":"1379034720","6":"1379034720"},{"0":"3589","vim_version":"7.3","1":"7.3","script_version":"2.11.1","2":"2.11.1","version_comment":"- Avoid error when g:cake is not initialized.\r\n- Fix bug.","3":"- Avoid error when g:cake is not initialized.\r\n- Fix bug.","package":"cake.zip","4":"cake.zip","src_id":"20201","5":"20201","creation_date":"1369376030","6":"1369376030"},{"0":"3589","vim_version":"7.3","1":"7.3","script_version":"2.11","2":"2.11","version_comment":"- Add :Cbake\r\n- Add :Ctestrun\r\n- Add g:cakephp_enable_abbreviations\r\n- Add unite-source cake_lib\r\n- Fix a few bugs.","3":"- Add :Cbake\r\n- Add :Ctestrun\r\n- Add g:cakephp_enable_abbreviations\r\n- Add unite-source cake_lib\r\n- Fix a few bugs.","package":"cake.zip","4":"cake.zip","src_id":"20090","5":"20090","creation_date":"1368251297","6":"1368251297"},{"0":"3589","vim_version":"7.3","1":"7.3","script_version":"2.10.1","2":"2.10.1","version_comment":"- Add to the configuration file : core\r\n- Fix a few bugs.","3":"- Add to the configuration file : core\r\n- Fix a few bugs.","package":"cake.zip","4":"cake.zip","src_id":"19598","5":"19598","creation_date":"1362576823","6":"1362576823"},{"0":"3589","vim_version":"7.3","1":"7.3","script_version":"2.10","2":"2.10","version_comment":"- :Cview, To guess the name of the view from the current position if the argument is omitted. \r\n- Improve boot speed. \r\n- Add a new vertical split in gs command like gf. \r\n- Add feature to jump to the build path configuration file written. \r\n- Change the priority which jumped by gf command. \r\n- Fix a few bugs.","3":"- :Cview, To guess the name of the view from the current position if the argument is omitted. \r\n- Improve boot speed. \r\n- Add a new vertical split in gs command like gf. \r\n- Add feature to jump to the build path configuration file written. \r\n- Change the priority which jumped by gf command. \r\n- Fix a few bugs.","package":"cake.zip","4":"cake.zip","src_id":"19328","5":"19328","creation_date":"1357618391","6":"1357618391"},{"0":"3589","vim_version":"7.3","1":"7.3","script_version":"2.8","2":"2.8","version_comment":"- Add New gf pattern.\r\n  \"array('controller' => 'hoges', 'action' => 'fuga') \" jump to-\r\n  \"HogesController::fuga()\" .\r\n  \"array('controller' => 'hoges', 'action' => 'fuga', 'admin' => true)\" jump to-\r\n  \"HogesController::admin_fuga()\" .\r\n- Fix a few bugs.","3":"- Add New gf pattern.\r\n  \"array('controller' => 'hoges', 'action' => 'fuga') \" jump to-\r\n  \"HogesController::fuga()\" .\r\n  \"array('controller' => 'hoges', 'action' => 'fuga', 'admin' => true)\" jump to-\r\n  \"HogesController::admin_fuga()\" .\r\n- Fix a few bugs.","package":"cake.zip","4":"cake.zip","src_id":"18272","5":"18272","creation_date":"1342428954","6":"1342428954"},{"0":"3589","vim_version":"7.3","1":"7.3","script_version":"2.7","2":"2.7","version_comment":"- :Cdesc performed setting of the database connection automatically.It look up $useDbConfig, $useTable, and database.php .","3":"- :Cdesc performed setting of the database connection automatically.It look up $useDbConfig, $useTable, and database.php .","package":"cake.zip","4":"cake.zip","src_id":"18135","5":"18135","creation_date":"1339863194","6":"1339863194"},{"0":"3589","vim_version":"7.3","1":"7.3","script_version":"2.5","2":"2.5","version_comment":"- Update gf algorithm. Searched for view files, script files, CSS files recursively.\r\n- Fix a few bugs.","3":"- Update gf algorithm. Searched for view files, script files, CSS files recursively.\r\n- Fix a few bugs.","package":"cake.zip","4":"cake.zip","src_id":"18008","5":"18008","creation_date":"1337598539","6":"1337598539"},{"0":"3589","vim_version":"7.3","1":"7.3","script_version":"2.4.1","2":"2.4.1","version_comment":"- When an object was not found by gf command, I did the gf command of the default.\r\n- Fix a few bugs.","3":"- When an object was not found by gf command, I did the gf command of the default.\r\n- Fix a few bugs.","package":"cake.zip","4":"cake.zip","src_id":"17804","5":"17804","creation_date":"1334992027","6":"1334992027"},{"0":"3589","vim_version":"7.3","1":"7.3","script_version":"2.4","2":"2.4","version_comment":"- Add Commands.\r\n  :Clib\r\n  :Clibsp\r\n  :Clibvsp\r\n  :Clibtab\r\n- Add New gf algorithm that could jump to a core of CakePHP.\r\n- Improved Auto Mode.\r\n  At the time of auto_mode, it prevented you from losing sight of a path of app \r\n  when you opened the file except CakePHP once.","3":"- Add Commands.\r\n  :Clib\r\n  :Clibsp\r\n  :Clibvsp\r\n  :Clibtab\r\n- Add New gf algorithm that could jump to a core of CakePHP.\r\n- Improved Auto Mode.\r\n  At the time of auto_mode, it prevented you from losing sight of a path of app \r\n  when you opened the file except CakePHP once.","package":"cake.zip","4":"cake.zip","src_id":"17733","5":"17733","creation_date":"1333817293","6":"1333817293"},{"0":"3589","vim_version":"7.3","1":"7.3","script_version":"2.3.2","2":"2.3.2","version_comment":"- Add New gf algorithm.\r\n- in Controller, \"class HogesController extends AppController\" -> AppController\r\n- in Model, \"class Hoge extends AppModel\"  -> AppModel","3":"- Add New gf algorithm.\r\n- in Controller, \"class HogesController extends AppController\" -> AppController\r\n- in Model, \"class Hoge extends AppModel\"  -> AppModel","package":"cake.zip","4":"cake.zip","src_id":"17587","5":"17587","creation_date":"1331532787","6":"1331532787"},{"0":"3589","vim_version":"7.3","1":"7.3","script_version":"2.3.1","2":"2.3.1","version_comment":"- Fix a few bugs. ","3":"- Fix a few bugs. ","package":"cake.zip","4":"cake.zip","src_id":"17426","5":"17426","creation_date":"1328941592","6":"1328941592"},{"0":"3589","vim_version":"7.3","1":"7.3","script_version":"2.3","2":"2.3","version_comment":"- Add Commands.\r\n  :Celement","3":"- Add Commands.\r\n  :Celement","package":"cake.zip","4":"cake.zip","src_id":"17380","5":"17380","creation_date":"1328346601","6":"1328346601"},{"0":"3589","vim_version":"7.0","1":"7.0","script_version":"2.2","2":"2.2","version_comment":"- Add the mode which automatically set a project. \r\n(g:cakephp_enable_auto_mode)\r\n- Add g:cakephp_enable_fix_mode  \r\n- Deprecated g:cakephp_auto_set_project","3":"- Add the mode which automatically set a project. \r\n(g:cakephp_enable_auto_mode)\r\n- Add g:cakephp_enable_fix_mode  \r\n- Deprecated g:cakephp_auto_set_project","package":"cake.zip","4":"cake.zip","src_id":"17280","5":"17280","creation_date":"1327157149","6":"1327157149"},{"0":"3589","vim_version":"7.0","1":"7.0","script_version":"2.1.1","2":"2.1.1","version_comment":"- Fix a few bugs.","3":"- Fix a few bugs.","package":"cake.zip","4":"cake.zip","src_id":"17086","5":"17086","creation_date":"1324261938","6":"1324261938"},{"0":"3589","vim_version":"7.0","1":"7.0","script_version":"2.1","2":"2.1","version_comment":"- Fix a few bugs.\r\n- Open the plural files at a time.\r\n- Add gf(C-w f, C-w gf) algorithm.\r\n  in Controller:\r\n    function xxx -> View\r\n    $this->render('xxx') -> View\r\n    var $layout = 'xxx'; -> Layout\r\n    $this->layout = 'xxx'; -> Layout\r\n  in View:\r\n    $this->element('xxx') -> Element\r\n    $html->css('xxx') -> Css\r\n    $html->script('xxx') -> Script\r\n  Anywhere:\r\n    Configure::load('list') -> Config\r\n\r\n  By the word under the cursor, you can jump:\r\n    in Controller -> Model or Behavior or Component or Helper or Controller\r\n    in Model -> Model or Behavior or Controller\r\n    in View -> Helper or Model or Controller\r\n    in Helper -> Helper or Controller\r\n    in Component -> Model or Behavior or Component or Controller\r\n    in Behavior -> Model or Behavior\r\n    in TestController -> Fixture or Controller\r\n    in TestModel -> Fixture or Model-\r\n    in TestBehavior -> Fixture or Behavior\r\n    in TestComponent -> Fixture or Component\r\n    in TestHelper -> Fixture or Helper\r\n    in Fixture -> Model\r\n    in Shell -> Task or Model\r\n    in Task -> Model","3":"- Fix a few bugs.\r\n- Open the plural files at a time.\r\n- Add gf(C-w f, C-w gf) algorithm.\r\n  in Controller:\r\n    function xxx -> View\r\n    $this->render('xxx') -> View\r\n    var $layout = 'xxx'; -> Layout\r\n    $this->layout = 'xxx'; -> Layout\r\n  in View:\r\n    $this->element('xxx') -> Element\r\n    $html->css('xxx') -> Css\r\n    $html->script('xxx') -> Script\r\n  Anywhere:\r\n    Configure::load('list') -> Config\r\n\r\n  By the word under the cursor, you can jump:\r\n    in Controller -> Model or Behavior or Component or Helper or Controller\r\n    in Model -> Model or Behavior or Controller\r\n    in View -> Helper or Model or Controller\r\n    in Helper -> Helper or Controller\r\n    in Component -> Model or Behavior or Component or Controller\r\n    in Behavior -> Model or Behavior\r\n    in TestController -> Fixture or Controller\r\n    in TestModel -> Fixture or Model-\r\n    in TestBehavior -> Fixture or Behavior\r\n    in TestComponent -> Fixture or Component\r\n    in TestHelper -> Fixture or Helper\r\n    in Fixture -> Model\r\n    in Shell -> Task or Model\r\n    in Task -> Model","package":"cake.zip","4":"cake.zip","src_id":"17067","5":"17067","creation_date":"1323946252","6":"1323946252"},{"0":"3589","vim_version":"7.0","1":"7.0","script_version":"2.0.1","2":"2.0.1","version_comment":"- Fix a few bugs. ","3":"- Fix a few bugs. ","package":"cake.zip","4":"cake.zip","src_id":"17012","5":"17012","creation_date":"1322817362","6":"1322817362"},{"0":"3589","vim_version":"7.0","1":"7.0","script_version":"2.0","2":"2.0","version_comment":"- It work in CakePHP1.3, both CakePHP2.0.","3":"- It work in CakePHP1.3, both CakePHP2.0.","package":"cake.zip","4":"cake.zip","src_id":"17008","5":"17008","creation_date":"1322796964","6":"1322796964"},{"0":"3589","vim_version":"7.0","1":"7.0","script_version":"1.4","2":"1.4","version_comment":"- Add unite-sources.\r\n  :Unite cake_controller\r\n  :Unite cake_model\r\n  :Unite cake_view\r\n  :Unite cake_behavior\r\n  :Unite cake_helper\r\n  :Unite cake_component\r\n  :Unite cake_fixture\r\n  :Unite cake_config\r\n  :Unite cake_shell\r\n  :Unite cake_task","3":"- Add unite-sources.\r\n  :Unite cake_controller\r\n  :Unite cake_model\r\n  :Unite cake_view\r\n  :Unite cake_behavior\r\n  :Unite cake_helper\r\n  :Unite cake_component\r\n  :Unite cake_fixture\r\n  :Unite cake_config\r\n  :Unite cake_shell\r\n  :Unite cake_task","package":"cake.tar.gz","4":"cake.tar.gz","src_id":"16801","5":"16801","creation_date":"1320393277","6":"1320393277"},{"0":"3589","vim_version":"7.0","1":"7.0","script_version":"1.3","2":"1.3","version_comment":"- Fix a few bugs.\r\n- Support Behavior.\r\n- Support Helper.\r\n- Support Test(Model\/Behavior\/Component\/Controller,Helper)\r\n- Support Fixture.","3":"- Fix a few bugs.\r\n- Support Behavior.\r\n- Support Helper.\r\n- Support Test(Model\/Behavior\/Component\/Controller,Helper)\r\n- Support Fixture.","package":"cake.tar.gz","4":"cake.tar.gz","src_id":"16795","5":"16795","creation_date":"1320303391","6":"1320303391"},{"0":"3589","vim_version":"7.0","1":"7.0","script_version":"1.2","2":"1.2","version_comment":"- Fix a few bugs.\r\n- g:cakephp_root was removed. g:cakephp_app was added instead.\r\n- Add Commands.\r\n  :Ccontrollerview\r\n  :Ccontrollerviewsp\r\n  :Ccontrollerviewvsp\r\n  :Ccontrollerviewtab\r\n  :Config\r\n  :Configsp\r\n  :Configvsp\r\n  :Configtab\r\n  :Ccomponent\r\n  :Ccomponentsp\r\n  :Ccomponentvsp\r\n  :Ccomponenttab\r\n  :Cshell\r\n  :Cshellsp\r\n  :Cshellvsp\r\n  :Cshelltab\r\n  :Ctask\r\n  :Ctasksp\r\n  :Ctaskvsp\r\n  :Ctasktab\r\n  :Clog","3":"- Fix a few bugs.\r\n- g:cakephp_root was removed. g:cakephp_app was added instead.\r\n- Add Commands.\r\n  :Ccontrollerview\r\n  :Ccontrollerviewsp\r\n  :Ccontrollerviewvsp\r\n  :Ccontrollerviewtab\r\n  :Config\r\n  :Configsp\r\n  :Configvsp\r\n  :Configtab\r\n  :Ccomponent\r\n  :Ccomponentsp\r\n  :Ccomponentvsp\r\n  :Ccomponenttab\r\n  :Cshell\r\n  :Cshellsp\r\n  :Cshellvsp\r\n  :Cshelltab\r\n  :Ctask\r\n  :Ctasksp\r\n  :Ctaskvsp\r\n  :Ctasktab\r\n  :Clog","package":"cake.tar.gz","4":"cake.tar.gz","src_id":"15832","5":"15832","creation_date":"1307432320","6":"1307432320"},{"0":"3589","vim_version":"7.0","1":"7.0","script_version":"1.1.0","2":"1.1.0","version_comment":"Initial upload","3":"Initial upload","package":"cake.tar.gz","4":"cake.tar.gz","src_id":"15660","5":"15660","creation_date":"1305628429","6":"1305628429"}]},"3588":{"script_id":"3588","0":"3588","script_name":"Find XML Tags","1":"Find XML Tags","script_type":"utility","2":"utility","summary":"Locate tags with out of order attributes","3":"Locate tags with out of order attributes","description":"I was editing an HTML file written by several developers over the course of a\r\nfew years. They contained tags like (yes, literally!)\r\n        <table cellpadding=0 cellspacing=\"0\" border='0'>\r\n        <table cellspacing=\"0\" cellpadding=0 border='0'>\r\n        <table cellspacing=0 cellpadding=0 border=0>\r\n\r\nThey're all basically the same table definition, but the attributes are\r\nswitched around and the attribute values are formatted differently each time.\r\n(Thank the multiple developers, each with their own style.) Running HTML Tidy\r\nwasn't an option because I didn't want to create a huge diff in version\r\ncontrol that indicated a lot of changes where I didn't actually change\r\nanything. Thus, this plugin.\r\n\r\nThe commands and functions defined in this script will match any XML\/HTML\r\nelement\/tag with the specified attributes and values.\r\n","4":"I was editing an HTML file written by several developers over the course of a\r\nfew years. They contained tags like (yes, literally!)\r\n        <table cellpadding=0 cellspacing=\"0\" border='0'>\r\n        <table cellspacing=\"0\" cellpadding=0 border='0'>\r\n        <table cellspacing=0 cellpadding=0 border=0>\r\n\r\nThey're all basically the same table definition, but the attributes are\r\nswitched around and the attribute values are formatted differently each time.\r\n(Thank the multiple developers, each with their own style.) Running HTML Tidy\r\nwasn't an option because I didn't want to create a huge diff in version\r\ncontrol that indicated a lot of changes where I didn't actually change\r\nanything. Thus, this plugin.\r\n\r\nThe commands and functions defined in this script will match any XML\/HTML\r\nelement\/tag with the specified attributes and values.\r\n","install_details":"Source the Vimball and try :help Findxmltag.\r\n\r\nUse :help FindXmlTag_History to find out what's changed.","5":"Source the Vimball and try :help Findxmltag.\r\n\r\nUse :help FindXmlTag_History to find out what's changed.","first_name":"Salman","6":"Salman","last_name":"Halim","7":"Halim","releases":[{"0":"3588","vim_version":"7.3","1":"7.3","script_version":"2.0","2":"2.0","version_comment":"Bug fixes, mostly (thanks entirely to Ingo Karkat). Also, renamed the commands to camel-case: FindXmlTagExact and FindXmlTagFlexible.\r\n\r\nUploaded again; had accidentally left out an enhancement to highlight search results if 'hlsearch' is set.","3":"Bug fixes, mostly (thanks entirely to Ingo Karkat). Also, renamed the commands to camel-case: FindXmlTagExact and FindXmlTagFlexible.\r\n\r\nUploaded again; had accidentally left out an enhancement to highlight search results if 'hlsearch' is set.","package":"FindXmlTag.vba","4":"FindXmlTag.vba","src_id":"15713","5":"15713","creation_date":"1306252532","6":"1306252532"},{"0":"3588","vim_version":"7.3","1":"7.3","script_version":"1.5","2":"1.5","version_comment":"Added options to easily add attributes with any value or no value.","3":"Added options to easily add attributes with any value or no value.","package":"FindXmlTag.vba","4":"FindXmlTag.vba","src_id":"15662","5":"15662","creation_date":"1305643417","6":"1305643417"},{"0":"3588","vim_version":"7.3","1":"7.3","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"FindXmlTag.vba","4":"FindXmlTag.vba","src_id":"15654","5":"15654","creation_date":"1305607964","6":"1305607964"}]},"3587":{"script_id":"3587","0":"3587","script_name":"vim-soy","1":"vim-soy","script_type":"syntax","2":"syntax","summary":"Syntax file for Google Closure templates","3":"Syntax file for Google Closure templates","description":"This is a highlighting file for Google Closure Tools' \"soy\" templating language.\r\n\r\nYou can download development versions from its GitHub page:\r\n\r\nhttps:\/\/github.com\/duganchen\/vim-soy","4":"This is a highlighting file for Google Closure Tools' \"soy\" templating language.\r\n\r\nYou can download development versions from its GitHub page:\r\n\r\nhttps:\/\/github.com\/duganchen\/vim-soy","install_details":"Extract to your vim runtime path: ~\/.vim on Linux and $HOME\/vimfiles on Windows.","5":"Extract to your vim runtime path: ~\/.vim on Linux and $HOME\/vimfiles on Windows.","first_name":"Dugan","6":"Dugan","last_name":"Chen","7":"Chen","releases":[{"0":"3587","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"vim-soy-1.0.zip","4":"vim-soy-1.0.zip","src_id":"15653","5":"15653","creation_date":"1305601734","6":"1305601734"}]},"3586":{"script_id":"3586","0":"3586","script_name":"Redhawk Vim Plugin","1":"Redhawk Vim Plugin","script_type":"utility","2":"utility","summary":"A plugin for redhawk: query and replace","3":"A plugin for redhawk: query and replace","description":"Redhawk Vim: A Vim plugin for Redhawk (http:\/\/pypi.python.org\/pypi\/redhawk)\r\n\r\n\r\nCurrently, only redhawk query and replace are supported.\r\n\r\n  :Redhawk query <query> [FILE]s\r\n\r\nruns the Redhawk query on each of the FILEs, and populates the quickfix\r\nwindow.\r\n\r\n  :Redhawk replace <query> [FILE]s\r\n\r\nruns the Redhawk query on each of the FILEs, and creates an editable quickfix\r\nwindow (similar to :GReplace).\r\n\r\n\r\nEXAMPLE USAGE:\r\n\r\n1. Query for '**\/DefineFunction' in each FILE:\r\n  Redhawk query '**\/DefineFunction' [FILE]\r\n\r\n2. Replace all '**\/DefineFunction' in each FILE:\r\n  Redhawk replace '**\/DefineFunction' [FILE]\r\n\r\n3. Query parallely for '**\/DefineFunction' in each FILE:\r\n  Redhawk query '**\/DefineFunction' [FILE] -p\r\n\r\n4. Replace all results for '**\/DefineFunction' in buffers:\r\n  RedhawkBuf replace '**\/DefineFunction'\r\n\r\n\r\nList of Commands:\r\nRedhawk:        Query and replace from within Vim.\r\nRedhawkAdd:     Add to quick fix list.\r\nRedhawkArgs:    Add args as files to redhawk command.\r\nRedhawkBuf:     Add files in buffers to redhawk command.\r\nRedhawkArgsAdd: (similar)\r\nRedhawkBufAdd:  (similar)\r\n\r\nIf you do not have redhawk installed on your path, you could set it to\r\n\/path\/to\/redhawk by setting the g:redhawk_program variable. Optional arguments\r\nthat you might always want to use are set in g:redhawk_args. If you find that\r\nthe default behaviour of the quickfix list popping up irritating, you can set\r\ng:redhawk_open_resultlist to 0 in your .vimrc\r\n\r\n\r\nNote:\r\n\r\n1. Redhawk MUST be installed in PATH, or the g:redhawk_program variable must be\r\nset.\r\n\r\n2. Redhawk can be installed via PyPi: \r\n    $ pip install redhawk\r\n\r\nThe project hompage is here: http:\/\/pypi.python.org\/pypi\/redhawk\r\nRedhawk is currently under heavy development. The latest development release\r\ncan be found at http:\/\/www.github.com\/spranesh\/Redhawk\r\n","4":"Redhawk Vim: A Vim plugin for Redhawk (http:\/\/pypi.python.org\/pypi\/redhawk)\r\n\r\n\r\nCurrently, only redhawk query and replace are supported.\r\n\r\n  :Redhawk query <query> [FILE]s\r\n\r\nruns the Redhawk query on each of the FILEs, and populates the quickfix\r\nwindow.\r\n\r\n  :Redhawk replace <query> [FILE]s\r\n\r\nruns the Redhawk query on each of the FILEs, and creates an editable quickfix\r\nwindow (similar to :GReplace).\r\n\r\n\r\nEXAMPLE USAGE:\r\n\r\n1. Query for '**\/DefineFunction' in each FILE:\r\n  Redhawk query '**\/DefineFunction' [FILE]\r\n\r\n2. Replace all '**\/DefineFunction' in each FILE:\r\n  Redhawk replace '**\/DefineFunction' [FILE]\r\n\r\n3. Query parallely for '**\/DefineFunction' in each FILE:\r\n  Redhawk query '**\/DefineFunction' [FILE] -p\r\n\r\n4. Replace all results for '**\/DefineFunction' in buffers:\r\n  RedhawkBuf replace '**\/DefineFunction'\r\n\r\n\r\nList of Commands:\r\nRedhawk:        Query and replace from within Vim.\r\nRedhawkAdd:     Add to quick fix list.\r\nRedhawkArgs:    Add args as files to redhawk command.\r\nRedhawkBuf:     Add files in buffers to redhawk command.\r\nRedhawkArgsAdd: (similar)\r\nRedhawkBufAdd:  (similar)\r\n\r\nIf you do not have redhawk installed on your path, you could set it to\r\n\/path\/to\/redhawk by setting the g:redhawk_program variable. Optional arguments\r\nthat you might always want to use are set in g:redhawk_args. If you find that\r\nthe default behaviour of the quickfix list popping up irritating, you can set\r\ng:redhawk_open_resultlist to 0 in your .vimrc\r\n\r\n\r\nNote:\r\n\r\n1. Redhawk MUST be installed in PATH, or the g:redhawk_program variable must be\r\nset.\r\n\r\n2. Redhawk can be installed via PyPi: \r\n    $ pip install redhawk\r\n\r\nThe project hompage is here: http:\/\/pypi.python.org\/pypi\/redhawk\r\nRedhawk is currently under heavy development. The latest development release\r\ncan be found at http:\/\/www.github.com\/spranesh\/Redhawk\r\n","install_details":"Extract the tar.gz into your .vim directory","5":"Extract the tar.gz into your .vim directory","first_name":"Pranesh","6":"Pranesh","last_name":"Srinivasan","7":"Srinivasan","releases":[{"0":"3586","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"redhawk-vim.tar.gz","4":"redhawk-vim.tar.gz","src_id":"15649","5":"15649","creation_date":"1305575411","6":"1305575411"}]},"3585":{"script_id":"3585","0":"3585","script_name":"typofree.vim","1":"typofree.vim","script_type":"color scheme","2":"color scheme","summary":"256 color terminal colorscheme","3":"256 color terminal colorscheme","description":"This is a 256 color terminal vim colorscheme.\r\n\r\nGet the latest version at https:\/\/github.com\/Tuurlijk\/typofree.vim\r\n\r\nScreenshot: https:\/\/github.com\/Tuurlijk\/typofree.vim\/blob\/master\/typofree_vim.png","4":"This is a 256 color terminal vim colorscheme.\r\n\r\nGet the latest version at https:\/\/github.com\/Tuurlijk\/typofree.vim\r\n\r\nScreenshot: https:\/\/github.com\/Tuurlijk\/typofree.vim\/blob\/master\/typofree_vim.png","install_details":"Put in ~\/.vim\/colors or (<your-vim-dir>\\vimfiles\\colors on Windows) and do\r\n:colorscheme typofree","5":"Put in ~\/.vim\/colors or (<your-vim-dir>\\vimfiles\\colors on Windows) and do\r\n:colorscheme typofree","first_name":"Michiel","6":"Michiel","last_name":"Roos","7":"Roos","releases":[{"0":"3585","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"typofree.vim","4":"typofree.vim","src_id":"15648","5":"15648","creation_date":"1305554226","6":"1305554226"}]},"3584":{"script_id":"3584","0":"3584","script_name":"checklist.vim","1":"checklist.vim","script_type":"utility","2":"utility","summary":"A super-simple way to create todo lists.","3":"A super-simple way to create todo lists.","description":"Latest version:\r\nhttps:\/\/github.com\/ctruett\/Checklist.vim\r\n\r\nIf you have any suggestions, bugs, or complaints, please visit the project page (linked above) and tell me about them.\r\nIf you find this plugin helpful in any way, please vote below!","4":"Latest version:\r\nhttps:\/\/github.com\/ctruett\/Checklist.vim\r\n\r\nIf you have any suggestions, bugs, or complaints, please visit the project page (linked above) and tell me about them.\r\nIf you find this plugin helpful in any way, please vote below!","install_details":"Please read:\r\nhttps:\/\/github.com\/ctruett\/Checklist.vim","5":"Please read:\r\nhttps:\/\/github.com\/ctruett\/Checklist.vim","first_name":"Christopher","6":"Christopher","last_name":"Truett","7":"Truett","releases":[{"0":"3584","vim_version":"7.0","1":"7.0","script_version":"0.6","2":"0.6","version_comment":"New timestamp format. Archive compression should work with 'unzip' for all you Linux users now. Now using \"*\" instead of ASCII #81 for list items.","3":"New timestamp format. Archive compression should work with 'unzip' for all you Linux users now. Now using \"*\" instead of ASCII #81 for list items.","package":"checklist-v0.6.zip","4":"checklist-v0.6.zip","src_id":"15804","5":"15804","creation_date":"1307141930","6":"1307141930"},{"0":"3584","vim_version":"7.0","1":"7.0","script_version":"0.51","2":"0.51","version_comment":"Try this if you are having problems using this plugin on Linux.","3":"Try this if you are having problems using this plugin on Linux.","package":"checklist-v0.51.zip","4":"checklist-v0.51.zip","src_id":"15769","5":"15769","creation_date":"1306799053","6":"1306799053"},{"0":"3584","vim_version":"7.0","1":"7.0","script_version":"0.5","2":"0.5","version_comment":"Major Rehaul. Much faster. Added syn\u00c2\u00adtax file and pack\u00c2\u00adaged into .zip.","3":"Major Rehaul. Much faster. Added syn\u00c2\u00adtax file and pack\u00c2\u00adaged into .zip.","package":"checklist.zip","4":"checklist.zip","src_id":"15745","5":"15745","creation_date":"1306576890","6":"1306576890"},{"0":"3584","vim_version":"7.0","1":"7.0","script_version":"0.4","2":"0.4","version_comment":"Plugin rewrite. Check URL in the details for more information","3":"Plugin rewrite. Check URL in the details for more information","package":"checklist.vim","4":"checklist.vim","src_id":"15715","5":"15715","creation_date":"1306264943","6":"1306264943"},{"0":"3584","vim_version":"7.0","1":"7.0","script_version":"0.3","2":"0.3","version_comment":"Simplified code, made timestamps optional.","3":"Simplified code, made timestamps optional.","package":"checklist.vim","4":"checklist.vim","src_id":"15683","5":"15683","creation_date":"1305861591","6":"1305861591"},{"0":"3584","vim_version":"7.0","1":"7.0","script_version":"0.2","2":"0.2","version_comment":"Added support for subitems.","3":"Added support for subitems.","package":"checklist.vim","4":"checklist.vim","src_id":"15652","5":"15652","creation_date":"1305591309","6":"1305591309"},{"0":"3584","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"checklist.vim","4":"checklist.vim","src_id":"15640","5":"15640","creation_date":"1305424553","6":"1305424553"}]},"3583":{"script_id":"3583","0":"3583","script_name":"Comceal","1":"Comceal","script_type":"utility","2":"utility","summary":"Utility to hide comments with conceal feature","3":"Utility to hide comments with conceal feature","description":"Ever wanted to hide comments in program and toggle between the visibility ? Vim conceal feature (vim --version | grep +conceal) provides support for this. This plugin makes use of it to hide comments based on the filetype. ","4":"Ever wanted to hide comments in program and toggle between the visibility ? Vim conceal feature (vim --version | grep +conceal) provides support for this. This plugin makes use of it to hide comments based on the filetype. ","install_details":"","5":"","first_name":"Raghavendra","6":"Raghavendra","last_name":"Prabhu","7":"Prabhu","releases":[{"0":"3583","vim_version":"7.3","1":"7.3","script_version":"0.0.2","2":"0.0.2","version_comment":"Fixes with prominent one  for multi line comments. \r\n","3":"Fixes with prominent one  for multi line comments. \r\n","package":"comceal.vim","4":"comceal.vim","src_id":"15642","5":"15642","creation_date":"1305472523","6":"1305472523"},{"0":"3583","vim_version":"7.3","1":"7.3","script_version":"0.0.1","2":"0.0.1","version_comment":"Initial upload","3":"Initial upload","package":"comceal.vim","4":"comceal.vim","src_id":"15638","5":"15638","creation_date":"1305386218","6":"1305386218"}]},"3582":{"script_id":"3582","0":"3582","script_name":"simplenote.vim","1":"simplenote.vim","script_type":"utility","2":"utility","summary":"plugin to interact with the simplenote web service","3":"plugin to interact with the simplenote web service","description":"# simplenote.vim\r\nA vim plugin to interact with the [simplenote][1] API. You can create an\r\naccount [here](https:\/\/simple-note.appspot.com\/create) if you don't already\r\nhave one.\r\nNow you can take simple notes directly from your favourite editor.\r\n\r\n## Installation\r\nJust copy `simplenote.vim` into your plugin folder. But you really want to use\r\n[pathogen][5] for your plugin management.\r\n\r\nYour credentials have to be stored in your `vimrc`:\r\n\r\n    let g:SimplenoteUsername = \"your simplenote username\"\r\n    let g:SimplenotePassword = \"your simplenote password\"\r\n\r\nIf you don't want to have the credentials in your `vimrc` (if you manage it\r\nwith git for example), you can just set the variables in a different file (like\r\n`~\/.simplenoterc`) and source it with `source ~\/.simplenoterc` in your `vimrc`.\r\n\r\nBy default all notes are treated as plain text. If you usually write all of\r\nyour notes in some other format (like markdown or restructured text) you can\r\nset `g:SimplenoteFiletype` to the preferred vim filetype.\r\n\r\n## Usage\r\nThe plugin provides several commands to interact with your Simplenote account.\r\nIn order to retrieve a list of your notes execute\r\n\r\n    :Simplenote -l X\r\n    :Simplenote -l todo,shopping\r\n\r\nWhere X is the number of notes to retrieve; omit X to retrieve all.  This opens\r\na new scratch buffer with a line-wise listing of your notes. With `let\r\ng:SimplenoteListHeight=X` set, the scratch buffer will come up X lines tall.\r\nAlternatively when `let g:SimplenoteVertical=1` is set, it is opened as a\r\nvertical rather than horizontal split window. You can also pass a comma\r\nseparated list of tags. This will only list notes which have at least one of\r\nthose tags. You can then navigate through the with the arrow keys and enter a\r\nnote on hitting `Return`. Now that you see the content of the note, you can\r\ninteract with this specific note:\r\n\r\n    :Simplenote -u\r\n\r\nupdates the content of the current note with the content of the current buffer.\r\nThe buffer write command `:w` is also mapped to update the current note.\r\nIf you want to delete the note, execute\r\n\r\n    :Simplenote -d\r\n\r\nThis moves the current note to the trash. If you want to completely delete a\r\nnote, use\r\n\r\n    :Simplenote -D\r\n\r\nas it will directly delete the note and not only move it to the trash.\r\nThere also exists a command to create new notes.\r\n\r\n    :Simplenote -n\r\n\r\ncreates a new note with the contents of the current buffer. Once the note is\r\ncreated, `:Simplenote -u` updates the newly created note, also with the\r\ncontents of the current buffer.\r\nTagging notes is also supported. If you enter\r\n\r\n    :Simplenote -t\r\n\r\non a buffer containing a valid note, you get an input dialog, prefilled with\r\nexisting comma-separated tags for the note, which you can then edit. Tags have\r\nto be comma separated and hitting `Enter` will then update the note with the\r\nnew tag list.\r\n\r\nThere is also an option to open notes directly from a given key:\r\n\r\n    :Simplenote -o <notekey>\r\n\r\nWhile this is not very useful in everyday usage, it can be used very\r\neffectively to create shortcuts to notes you use often. Example:\r\n\r\n    \" add :Todo command\r\n    command Todo Simplenote -o <yourtodonotekey>\r\n\r\nNow you can jump to your todo note directly with `:Todo` in vim.\r\n\r\n## Note sorting\r\nsimplenote.vim supports simple note ordering. Per default the sort order is\r\npinned notes first followed by modified date from newest to oldest. The order\r\ncan be changed by setting the `g:SimplenoteSortOrder` variable. It should be\r\nset to a comma separated list of values which represents the sort order.\r\nAllowed values are `pinned` (pinned before unpinned), `tags` (notes with tags\r\nbefore untagged ones), `modifydate` and `createdate` (both newer before older).\r\n\r\n## Dependencies\r\nVersion 2 of the SimpleNote API relies heavily on JSON. As JSON and VimL don't\r\nreally play nice together, basic parts of this plugin are implemented in\r\npython. Therefore your vim has to be compiled with python support in order to\r\nuse this plugin.\r\n\r\n## Usage behind proxy\r\nSince the plugin uses Python's urllib2 for making HTTP requests, you just have to\r\nadd these lines (with the correct values) to your `.vimrc`:\r\n\r\n    let $HTTP_PROXY = 'http:\/\/<proxyuser>:<proxypassword>@<proxyurl>:<proxyport>'\r\n    let $HTTPS_PROXY = 'http:\/\/<proxyuser>:<proxypassword>@<proxyurl>:<proxyport>'\r\n\r\n## Development\r\n- [Bugs and issue tracker](https:\/\/github.com\/mrtazz\/simplenote.vim\/issues)\r\n\r\n## Contribute\r\n- Fork the project\r\n- Branch off develop\r\n- Make your additions\/fixes\/improvements\r\n- Send a pull request\r\n\r\n## Thanks\r\n[mattn][2], [Tim Pope][3] and [Scrooloose][4] who write awesome vim plugins\r\nwhich I took as a basis to learn how to write vim plugins.\r\n\r\n[1]: http:\/\/simplenoteapp.com\/\r\n[2]: http:\/\/github.com\/mattn\r\n[3]: http:\/\/github.com\/tpope\r\n[4]: http:\/\/github.com\/scrooloose\r\n[5]: http:\/\/github.com\/tpope\/vim-pathogen","4":"# simplenote.vim\r\nA vim plugin to interact with the [simplenote][1] API. You can create an\r\naccount [here](https:\/\/simple-note.appspot.com\/create) if you don't already\r\nhave one.\r\nNow you can take simple notes directly from your favourite editor.\r\n\r\n## Installation\r\nJust copy `simplenote.vim` into your plugin folder. But you really want to use\r\n[pathogen][5] for your plugin management.\r\n\r\nYour credentials have to be stored in your `vimrc`:\r\n\r\n    let g:SimplenoteUsername = \"your simplenote username\"\r\n    let g:SimplenotePassword = \"your simplenote password\"\r\n\r\nIf you don't want to have the credentials in your `vimrc` (if you manage it\r\nwith git for example), you can just set the variables in a different file (like\r\n`~\/.simplenoterc`) and source it with `source ~\/.simplenoterc` in your `vimrc`.\r\n\r\nBy default all notes are treated as plain text. If you usually write all of\r\nyour notes in some other format (like markdown or restructured text) you can\r\nset `g:SimplenoteFiletype` to the preferred vim filetype.\r\n\r\n## Usage\r\nThe plugin provides several commands to interact with your Simplenote account.\r\nIn order to retrieve a list of your notes execute\r\n\r\n    :Simplenote -l X\r\n    :Simplenote -l todo,shopping\r\n\r\nWhere X is the number of notes to retrieve; omit X to retrieve all.  This opens\r\na new scratch buffer with a line-wise listing of your notes. With `let\r\ng:SimplenoteListHeight=X` set, the scratch buffer will come up X lines tall.\r\nAlternatively when `let g:SimplenoteVertical=1` is set, it is opened as a\r\nvertical rather than horizontal split window. You can also pass a comma\r\nseparated list of tags. This will only list notes which have at least one of\r\nthose tags. You can then navigate through the with the arrow keys and enter a\r\nnote on hitting `Return`. Now that you see the content of the note, you can\r\ninteract with this specific note:\r\n\r\n    :Simplenote -u\r\n\r\nupdates the content of the current note with the content of the current buffer.\r\nThe buffer write command `:w` is also mapped to update the current note.\r\nIf you want to delete the note, execute\r\n\r\n    :Simplenote -d\r\n\r\nThis moves the current note to the trash. If you want to completely delete a\r\nnote, use\r\n\r\n    :Simplenote -D\r\n\r\nas it will directly delete the note and not only move it to the trash.\r\nThere also exists a command to create new notes.\r\n\r\n    :Simplenote -n\r\n\r\ncreates a new note with the contents of the current buffer. Once the note is\r\ncreated, `:Simplenote -u` updates the newly created note, also with the\r\ncontents of the current buffer.\r\nTagging notes is also supported. If you enter\r\n\r\n    :Simplenote -t\r\n\r\non a buffer containing a valid note, you get an input dialog, prefilled with\r\nexisting comma-separated tags for the note, which you can then edit. Tags have\r\nto be comma separated and hitting `Enter` will then update the note with the\r\nnew tag list.\r\n\r\nThere is also an option to open notes directly from a given key:\r\n\r\n    :Simplenote -o <notekey>\r\n\r\nWhile this is not very useful in everyday usage, it can be used very\r\neffectively to create shortcuts to notes you use often. Example:\r\n\r\n    \" add :Todo command\r\n    command Todo Simplenote -o <yourtodonotekey>\r\n\r\nNow you can jump to your todo note directly with `:Todo` in vim.\r\n\r\n## Note sorting\r\nsimplenote.vim supports simple note ordering. Per default the sort order is\r\npinned notes first followed by modified date from newest to oldest. The order\r\ncan be changed by setting the `g:SimplenoteSortOrder` variable. It should be\r\nset to a comma separated list of values which represents the sort order.\r\nAllowed values are `pinned` (pinned before unpinned), `tags` (notes with tags\r\nbefore untagged ones), `modifydate` and `createdate` (both newer before older).\r\n\r\n## Dependencies\r\nVersion 2 of the SimpleNote API relies heavily on JSON. As JSON and VimL don't\r\nreally play nice together, basic parts of this plugin are implemented in\r\npython. Therefore your vim has to be compiled with python support in order to\r\nuse this plugin.\r\n\r\n## Usage behind proxy\r\nSince the plugin uses Python's urllib2 for making HTTP requests, you just have to\r\nadd these lines (with the correct values) to your `.vimrc`:\r\n\r\n    let $HTTP_PROXY = 'http:\/\/<proxyuser>:<proxypassword>@<proxyurl>:<proxyport>'\r\n    let $HTTPS_PROXY = 'http:\/\/<proxyuser>:<proxypassword>@<proxyurl>:<proxyport>'\r\n\r\n## Development\r\n- [Bugs and issue tracker](https:\/\/github.com\/mrtazz\/simplenote.vim\/issues)\r\n\r\n## Contribute\r\n- Fork the project\r\n- Branch off develop\r\n- Make your additions\/fixes\/improvements\r\n- Send a pull request\r\n\r\n## Thanks\r\n[mattn][2], [Tim Pope][3] and [Scrooloose][4] who write awesome vim plugins\r\nwhich I took as a basis to learn how to write vim plugins.\r\n\r\n[1]: http:\/\/simplenoteapp.com\/\r\n[2]: http:\/\/github.com\/mattn\r\n[3]: http:\/\/github.com\/tpope\r\n[4]: http:\/\/github.com\/scrooloose\r\n[5]: http:\/\/github.com\/tpope\/vim-pathogen","install_details":"copy the plugin, autoload and docs folders into your .vim directory. Or better use pathogen. You need vim to be compiled with +python.","5":"copy the plugin, autoload and docs folders into your .vim directory. Or better use pathogen. You need vim to be compiled with +python.","first_name":"Daniel","6":"Daniel","last_name":"Schauenberg","7":"Schauenberg","releases":[{"0":"3582","vim_version":"7.3","1":"7.3","script_version":"0.7.0","2":"0.7.0","version_comment":"- add vim help file\r\n- add custom sort orders\r\n- add -o option to open note for given key directly\r\n- show notes tags in the list view","3":"- add vim help file\r\n- add custom sort orders\r\n- add -o option to open note for given key directly\r\n- show notes tags in the list view","package":"simplenote.vim.tar.gz","4":"simplenote.vim.tar.gz","src_id":"18852","5":"18852","creation_date":"1350847393","6":"1350847393"},{"0":"3582","vim_version":"7.3","1":"7.3","script_version":"0.6.0","2":"0.6.0","version_comment":"- add the possibility to restrict note listing to tags\r\n- respect pinned notes in note index\r\n- set initial number of notes to load to 100\r\n- add config option to specify a preferred filetype\r\n- add modifydate to update_note() function","3":"- add the possibility to restrict note listing to tags\r\n- respect pinned notes in note index\r\n- set initial number of notes to load to 100\r\n- add config option to specify a preferred filetype\r\n- add modifydate to update_note() function","package":"simplenote.vim.tar.gz","4":"simplenote.vim.tar.gz","src_id":"18722","5":"18722","creation_date":"1349030721","6":"1349030721"},{"0":"3582","vim_version":"7.3","1":"7.3","script_version":"0.5.0","2":"0.5.0","version_comment":"## 0.5.0 (06\/03\/2012)\r\n\r\n- make pretty formatting for note list\r\n- allow vertical splitting of scratch buffer\r\n- listing command (-l) takes parameter of max notes to fetch\r\n- update to simplenote.py v0.2.0\r\n- incorrectly fetched notes are not displayed anymore","3":"## 0.5.0 (06\/03\/2012)\r\n\r\n- make pretty formatting for note list\r\n- allow vertical splitting of scratch buffer\r\n- listing command (-l) takes parameter of max notes to fetch\r\n- update to simplenote.py v0.2.0\r\n- incorrectly fetched notes are not displayed anymore","package":"simplenote.tar.gz","4":"simplenote.tar.gz","src_id":"18083","5":"18083","creation_date":"1338696176","6":"1338696176"},{"0":"3582","vim_version":"7.3","1":"7.3","script_version":"0.4.0","2":"0.4.0","version_comment":"plugin uses autoload structure now","3":"plugin uses autoload structure now","package":"simplenote.vim.tar.gz","4":"simplenote.vim.tar.gz","src_id":"17413","5":"17413","creation_date":"1328761734","6":"1328761734"},{"0":"3582","vim_version":"7.3","1":"7.3","script_version":"0.3.1","2":"0.3.1","version_comment":"- Fix behaviour where notes didn't exactly behave like vim buffers\r\n- don't warn for saving if not was updated\r\n- use update note function as acwrite command\r\n- note list is not modifiable anymore\r\n- silent call GetTo...\r\n- fix error in non-slash file separator envrionment such as win32","3":"- Fix behaviour where notes didn't exactly behave like vim buffers\r\n- don't warn for saving if not was updated\r\n- use update note function as acwrite command\r\n- note list is not modifiable anymore\r\n- silent call GetTo...\r\n- fix error in non-slash file separator envrionment such as win32","package":"simplenote.vim","4":"simplenote.vim","src_id":"16947","5":"16947","creation_date":"1322009679","6":"1322009679"},{"0":"3582","vim_version":"7.3","1":"7.3","script_version":"0.3.0","2":"0.3.0","version_comment":"major changes:\r\n\r\n- UTF-8 support\r\n- create new notes from buffer via :Simplenote -n\r\n- update note when buffer is written\r\n- support direct deletion of notes via :Simplenote -D\r\n- support tagging of notes via :Simplenote -t\r\n- distinct buffer for every note\r\n- use simplenote.py for API interaction\r\n- encapsulate interface methods in Python class","3":"major changes:\r\n\r\n- UTF-8 support\r\n- create new notes from buffer via :Simplenote -n\r\n- update note when buffer is written\r\n- support direct deletion of notes via :Simplenote -D\r\n- support tagging of notes via :Simplenote -t\r\n- distinct buffer for every note\r\n- use simplenote.py for API interaction\r\n- encapsulate interface methods in Python class","package":"simplenote.vim","4":"simplenote.vim","src_id":"16088","5":"16088","creation_date":"1310923396","6":"1310923396"},{"0":"3582","vim_version":"7.3","1":"7.3","script_version":"0.2.0","2":"0.2.0","version_comment":"UI changes and several general improvements","3":"UI changes and several general improvements","package":"simplenote.vim","4":"simplenote.vim","src_id":"15835","5":"15835","creation_date":"1307441746","6":"1307441746"},{"0":"3582","vim_version":"7.3","1":"7.3","script_version":"0.1.0","2":"0.1.0","version_comment":"Initial upload","3":"Initial upload","package":"simplenote.vim","4":"simplenote.vim","src_id":"15620","5":"15620","creation_date":"1305021293","6":"1305021293"}]},"3581":{"script_id":"3581","0":"3581","script_name":"vim-textobj-quoted","1":"vim-textobj-quoted","script_type":"utility","2":"utility","summary":"A text-object for quoted text","3":"A text-object for quoted text","description":"A custom text object for selecting quoted text. It depends on awesome Kana's https:\/\/github.com\/kana\/vim-textobj-user. \r\n\r\n\r\nvim-textobj-quoted gives you two new text-objects: \r\n\r\n* iq\r\nThat stands for Inner Quoted\r\n* *_aq_*\r\nThat stands for Around Quoted\r\n\r\nSo, the two text-objects defined will work with the following quoting chars:\r\n\r\n* { }\r\n* \" \"\r\n* ' '\r\n* ( )\r\n\r\nPlease note that the defined text-objects are single-line oriented. I find them very useful in situations like the following (* indicated cursor position): \r\n\r\n* \"some awes*ome text\"\r\n* (some awes*ome text)\r\n* {some awes*ome text}\r\n* 'some awes*ome text'\r\n\r\nIn each case you could use commands like viq or ciq and select\/cancel all the quoted text. Obviously, you can achive the same results using commands like vi\" or vi{. Indeed, the real benefit you'll get using this plugin is that you will have to remember only the q char.","4":"A custom text object for selecting quoted text. It depends on awesome Kana's https:\/\/github.com\/kana\/vim-textobj-user. \r\n\r\n\r\nvim-textobj-quoted gives you two new text-objects: \r\n\r\n* iq\r\nThat stands for Inner Quoted\r\n* *_aq_*\r\nThat stands for Around Quoted\r\n\r\nSo, the two text-objects defined will work with the following quoting chars:\r\n\r\n* { }\r\n* \" \"\r\n* ' '\r\n* ( )\r\n\r\nPlease note that the defined text-objects are single-line oriented. I find them very useful in situations like the following (* indicated cursor position): \r\n\r\n* \"some awes*ome text\"\r\n* (some awes*ome text)\r\n* {some awes*ome text}\r\n* 'some awes*ome text'\r\n\r\nIn each case you could use commands like viq or ciq and select\/cancel all the quoted text. Obviously, you can achive the same results using commands like vi\" or vi{. Indeed, the real benefit you'll get using this plugin is that you will have to remember only the q char.","install_details":"Copy to your vim folder or use the rake task.","5":"Copy to your vim folder or use the rake task.","first_name":"Luca","6":"Luca","last_name":"Pette","7":"Pette","releases":[{"0":"3581","vim_version":"7.0","1":"7.0","script_version":"0.0.1","2":"0.0.1","version_comment":"Initial upload","3":"Initial upload","package":"vim-textobj-quoted.zip","4":"vim-textobj-quoted.zip","src_id":"15614","5":"15614","creation_date":"1304953705","6":"1304953705"}]},"3579":{"script_id":"3579","0":"3579","script_name":"ignore-me","1":"ignore-me","script_type":"utility","2":"utility","summary":"accidental duplicate","3":"accidental duplicate","description":"accidental duplicate","4":"accidental duplicate","install_details":"","5":"","first_name":"Jeremy","6":"Jeremy","last_name":"Cantrell","7":"Cantrell","releases":[{"0":"3579","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"jmcantrell-vim-lastmod-244be45.zip","4":"jmcantrell-vim-lastmod-244be45.zip","src_id":"15608","5":"15608","creation_date":"1304886163","6":"1304886163"}]},"3578":{"script_id":"3578","0":"3578","script_name":"lastmod.vim","1":"lastmod.vim","script_type":"utility","2":"utility","summary":"Update a last modification timestamp when saving a file","3":"Update a last modification timestamp when saving a file","description":"The lastmod plugin provides a way to update a last modification timestamp every time changes are saved.","4":"The lastmod plugin provides a way to update a last modification timestamp every time changes are saved.","install_details":"Extract to ~\/.vim","5":"Extract to ~\/.vim","first_name":"Jeremy","6":"Jeremy","last_name":"Cantrell","7":"Cantrell","releases":[{"0":"3578","vim_version":"7.0","1":"7.0","script_version":"0.2","2":"0.2","version_comment":"improve search pattern\r\npreserve whitespace","3":"improve search pattern\r\npreserve whitespace","package":"jmcantrell-vim-lastmod-ae98597.zip","4":"jmcantrell-vim-lastmod-ae98597.zip","src_id":"15684","5":"15684","creation_date":"1305866999","6":"1305866999"},{"0":"3578","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"jmcantrell-vim-lastmod-244be45.zip","4":"jmcantrell-vim-lastmod-244be45.zip","src_id":"15605","5":"15605","creation_date":"1304825634","6":"1304825634"}]},"3577":{"script_id":"3577","0":"3577","script_name":"pacmanlog.vim","1":"pacmanlog.vim","script_type":"syntax","2":"syntax","summary":"highlight pacman's log file","3":"highlight pacman's log file","description":"Make the time, different actions and warnings\/errors in Arch Linux's package manager---pacman's log file highlighted.","4":"Make the time, different actions and warnings\/errors in Arch Linux's package manager---pacman's log file highlighted.","install_details":"Put the pacmanlog.vim in ~\/.vim\/syntax (on Windows, $VIM\/vimfiles\/syntax).\r\nAdd the following to filetype.vim (or your vimrc, or wherever it'll load automatically)\r\n  au BufRead\t\tpacman.log\t\t\tsetf pacmanlog","5":"Put the pacmanlog.vim in ~\/.vim\/syntax (on Windows, $VIM\/vimfiles\/syntax).\r\nAdd the following to filetype.vim (or your vimrc, or wherever it'll load automatically)\r\n  au BufRead\t\tpacman.log\t\t\tsetf pacmanlog","first_name":"lilydjwg","6":"lilydjwg","last_name":" ","7":" ","releases":[{"0":"3577","vim_version":"7.0","1":"7.0","script_version":"1.2","2":"1.2","version_comment":"* add reinstall and downgrade highlight","3":"* add reinstall and downgrade highlight","package":"pacmanlog.vim","4":"pacmanlog.vim","src_id":"20677","5":"20677","creation_date":"1376900562","6":"1376900562"},{"0":"3577","vim_version":"7.0","1":"7.0","script_version":"1.1","2":"1.1","version_comment":"* updated for pacman 4.1","3":"* updated for pacman 4.1","package":"pacmanlog.vim","4":"pacmanlog.vim","src_id":"19800","5":"19800","creation_date":"1365669476","6":"1365669476"},{"0":"3577","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"pacmanlog.vim","4":"pacmanlog.vim","src_id":"15592","5":"15592","creation_date":"1304664795","6":"1304664795"}]},"3576":{"script_id":"3576","0":"3576","script_name":"jshint.vim","1":"jshint.vim","script_type":"utility","2":"utility","summary":"A plugin that integrates JSHint with Vim","3":"A plugin that integrates JSHint with Vim","description":"This plugin is a front for the jshint NodeJS cli module.\r\nThis plugin will allow you to run jshint from vim, and shows the results in a split window.\r\n\r\n\r\nUsage\r\n\r\n    :JSHint {file}\r\n\r\nIt default to current file.\r\n\r\n\r\nKeyboard Shortcuts\r\n\r\nIn the quickfix window, you can use:\r\n\r\n    o to open in new window\r\n    go to preview file (open but maintain focus on jshint results)\r\n    q to close the quickfix window","4":"This plugin is a front for the jshint NodeJS cli module.\r\nThis plugin will allow you to run jshint from vim, and shows the results in a split window.\r\n\r\n\r\nUsage\r\n\r\n    :JSHint {file}\r\n\r\nIt default to current file.\r\n\r\n\r\nKeyboard Shortcuts\r\n\r\nIn the quickfix window, you can use:\r\n\r\n    o to open in new window\r\n    go to preview file (open but maintain focus on jshint results)\r\n    q to close the quickfix window","install_details":"You need jshint (http:\/\/jshint.org\/) in you path of course.\r\n\r\nInstall on a system with npm:\r\n\r\n    npm install jshint\r\n\r\nUse pathogen.vim (https:\/\/github.com\/vim-scripts\/pathogen.vim) it's easy.\r\n\r\n\r\nOr fork your own at https:\/\/github.com\/walm\/jshint.vim","5":"You need jshint (http:\/\/jshint.org\/) in you path of course.\r\n\r\nInstall on a system with npm:\r\n\r\n    npm install jshint\r\n\r\nUse pathogen.vim (https:\/\/github.com\/vim-scripts\/pathogen.vim) it's easy.\r\n\r\n\r\nOr fork your own at https:\/\/github.com\/walm\/jshint.vim","first_name":"Andreas","6":"Andreas","last_name":"W\u00c3\u00a5lm","7":"W\u00c3\u00a5lm","releases":[{"0":"3576","vim_version":"7.0","1":"7.0","script_version":"0.2","2":"0.2","version_comment":"Close quickfix when no errors","3":"Close quickfix when no errors","package":"jshint.tgz","4":"jshint.tgz","src_id":"15655","5":"15655","creation_date":"1305612130","6":"1305612130"},{"0":"3576","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"jshint.tgz","4":"jshint.tgz","src_id":"15582","5":"15582","creation_date":"1304544400","6":"1304544400"}]},"3575":{"script_id":"3575","0":"3575","script_name":"Enter Indent","1":"Enter Indent","script_type":"utility","2":"utility","summary":"By pressing enter between two tags, the cursor is repositioned <esc> O","3":"By pressing enter between two tags, the cursor is repositioned <esc> O","description":"|  - represents the cursor\r\n\r\n# body { | }\r\n\r\nIn the above situation, pressing enter, the result is as follows\r\n\r\n# body {\r\n        |\r\n}\r\n\r\nOther examples\r\n\r\n<tr>|<\/tr>\r\n\r\n<tr>\r\n        |\r\n<\/tr>\r\n\r\n\r\n{if} | {\/if}\r\n\r\n{if}\r\n        |\r\n{\/if}\r\n\r\nI recommend that you use this plugin in conjunction\r\n    http:\/\/www.vim.org\/scripts\/script.php?script_id=2754\r\n\r\nDownload a zipped archive, leave bug reports and feature request here:\r\n    http:\/\/github.com\/acustodioo\/vim-enter-indent\r\n\r\nPS: Sorry if the text is poorly written, I am learning English","4":"|  - represents the cursor\r\n\r\n# body { | }\r\n\r\nIn the above situation, pressing enter, the result is as follows\r\n\r\n# body {\r\n        |\r\n}\r\n\r\nOther examples\r\n\r\n<tr>|<\/tr>\r\n\r\n<tr>\r\n        |\r\n<\/tr>\r\n\r\n\r\n{if} | {\/if}\r\n\r\n{if}\r\n        |\r\n{\/if}\r\n\r\nI recommend that you use this plugin in conjunction\r\n    http:\/\/www.vim.org\/scripts\/script.php?script_id=2754\r\n\r\nDownload a zipped archive, leave bug reports and feature request here:\r\n    http:\/\/github.com\/acustodioo\/vim-enter-indent\r\n\r\nPS: Sorry if the text is poorly written, I am learning English","install_details":"Save to .vim\/plugin","5":"Save to .vim\/plugin","first_name":"Anderson","6":"Anderson","last_name":"Cust\u00c3\u00b3dio de Oliveira","7":"Cust\u00c3\u00b3dio de Oliveira","releases":[{"0":"3575","vim_version":"7.0","1":"7.0","script_version":"0.0.3","2":"0.0.3","version_comment":"Adicionado suporte para <!--[if ]><![endif]-->\r\nMudan\u00c3\u00a7a no modo de criar o recuo de linha, agora funciona de acordo com as configura\u00c3\u00a7\u00c3\u00b5es do vim.","3":"Adicionado suporte para <!--[if ]><![endif]-->\r\nMudan\u00c3\u00a7a no modo de criar o recuo de linha, agora funciona de acordo com as configura\u00c3\u00a7\u00c3\u00b5es do vim.","package":"enter-indent.vim","4":"enter-indent.vim","src_id":"18097","5":"18097","creation_date":"1339069535","6":"1339069535"},{"0":"3575","vim_version":"7.0","1":"7.0","script_version":"0.0.2","2":"0.0.2","version_comment":"Ao pressionar esc em dois colchetes vazios, era gerado um colchete in\u00c3\u00batil, o problema foi resolvido com a mudan\u00c3\u00a7a da seq\u00c3\u00bc\u00c3\u00aancia de comandos do \"feedkeys\".\r\n","3":"Ao pressionar esc em dois colchetes vazios, era gerado um colchete in\u00c3\u00batil, o problema foi resolvido com a mudan\u00c3\u00a7a da seq\u00c3\u00bc\u00c3\u00aancia de comandos do \"feedkeys\".\r\n","package":"enter-indent.vim","4":"enter-indent.vim","src_id":"15590","5":"15590","creation_date":"1304627333","6":"1304627333"},{"0":"3575","vim_version":"7.0","1":"7.0","script_version":"0.0.1","2":"0.0.1","version_comment":"Avoiding Unnecessary processes and fix tags {if}, {elseif} and get the other smarty.","3":"Avoiding Unnecessary processes and fix tags {if}, {elseif} and get the other smarty.","package":"enter-indent.vim","4":"enter-indent.vim","src_id":"15578","5":"15578","creation_date":"1304506070","6":"1304506070"},{"0":"3575","vim_version":"7.0","1":"7.0","script_version":"0.0.0","2":"0.0.0","version_comment":"Initial upload","3":"Initial upload","package":"enter-indent.vim","4":"enter-indent.vim","src_id":"15574","5":"15574","creation_date":"1304425701","6":"1304425701"}]},"3574":{"script_id":"3574","0":"3574","script_name":"gitv","1":"gitv","script_type":"utility","2":"utility","summary":"gitk for Vim.","3":"gitk for Vim.","description":"gitv is a 'gitk clone' plugin for the text editor Vim. The goal is to give you a similar set of functionality as a repository viewer.  Using this plugin you can view a repository's history including branching and merging, you can see which commits refs point to.  You can quickly and easily view what changed to which files and when. You can perform arbitrary diffs (using Vim's excellent built in diff functionality) and you can easily check out whole commits and branches or just individual files if need be.\r\n\r\nThrow in the fact that it is running in Vim and you get for free: the ability to move over repository history quickly and precisely using Vim's built in movement operators. You get excellent code syntax highlighting due to Vim's built in ability. You can open up all sorts of repository views in multiple windows and position them exactly as you like. You can take advantage of Vim's registers to copy multiple fragments of code from previous commits. The list goes on.\r\n\r\nThis plugin is an extension of the fugitive plugin.\r\n\r\nScreenshots can be found here: http:\/\/www.gregsexton.org\/portfolio\/gitv\/.\r\n\r\nThe GitHub repository is here: https:\/\/github.com\/gregsexton\/gitv.\r\n\r\nI hope you like it!","4":"gitv is a 'gitk clone' plugin for the text editor Vim. The goal is to give you a similar set of functionality as a repository viewer.  Using this plugin you can view a repository's history including branching and merging, you can see which commits refs point to.  You can quickly and easily view what changed to which files and when. You can perform arbitrary diffs (using Vim's excellent built in diff functionality) and you can easily check out whole commits and branches or just individual files if need be.\r\n\r\nThrow in the fact that it is running in Vim and you get for free: the ability to move over repository history quickly and precisely using Vim's built in movement operators. You get excellent code syntax highlighting due to Vim's built in ability. You can open up all sorts of repository views in multiple windows and position them exactly as you like. You can take advantage of Vim's registers to copy multiple fragments of code from previous commits. The list goes on.\r\n\r\nThis plugin is an extension of the fugitive plugin.\r\n\r\nScreenshots can be found here: http:\/\/www.gregsexton.org\/portfolio\/gitv\/.\r\n\r\nThe GitHub repository is here: https:\/\/github.com\/gregsexton\/gitv.\r\n\r\nI hope you like it!","install_details":"Install in ~\/.vim, or in ~\\vimfiles if you're on Windows. This plugin should be fully pathogen compatible if you want to install it this way.\r\n\r\ngitv was developed against Vim 7.3 but earlier versions of Vim should work.  Vim 7.2+ is recommended as it ships with syntax highlighting for many Git file types. **You will also need the fugitive plugin installed and working for gitv to work.**","5":"Install in ~\/.vim, or in ~\\vimfiles if you're on Windows. This plugin should be fully pathogen compatible if you want to install it this way.\r\n\r\ngitv was developed against Vim 7.3 but earlier versions of Vim should work.  Vim 7.2+ is recommended as it ships with syntax highlighting for many Git file types. **You will also need the fugitive plugin installed and working for gitv to work.**","first_name":"Greg","6":"Greg","last_name":"Sexton","7":"Sexton","releases":[{"0":"3574","vim_version":"7.0","1":"7.0","script_version":"1.1","2":"1.1","version_comment":"Nodes displaying local changes are inserted above HEAD ref.\r\nAdded range feature.\r\nMerging branches is possible in gitv.\r\nstrwidth bugfix (thanks Adam Reeve).\r\nPrevent bdelete errors (thanks pydave).","3":"Nodes displaying local changes are inserted above HEAD ref.\r\nAdded range feature.\r\nMerging branches is possible in gitv.\r\nstrwidth bugfix (thanks Adam Reeve).\r\nPrevent bdelete errors (thanks pydave).","package":"gitv-1.1.zip","4":"gitv-1.1.zip","src_id":"16307","5":"16307","creation_date":"1313854472","6":"1313854472"},{"0":"3574","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"gitv-1.0.zip","4":"gitv-1.0.zip","src_id":"15572","5":"15572","creation_date":"1304372714","6":"1304372714"}]},"3573":{"script_id":"3573","0":"3573","script_name":"quit-another-window","1":"quit-another-window","script_type":"utility","2":"utility","summary":"Quickly close another window and keep working in current window","3":"Quickly close another window and keep working in current window","description":"Often I need to close some another window and keep working in the current window.\r\nFor example, when I read some help in the upper window, and edit code in the lower\r\nwindow. At one time, I decide to close help window. To do it,\r\ni have to press \"Ctrl_W k :q\".\r\n\r\nNot very short. And this is not the worse variant.\r\nAnother variant:\r\n\r\n+-----------------+-----------------+\r\n|      help           |                        |\r\n|     window      |                        |\r\n|                         |     current      |\r\n+-----------------+     window     |\r\n|                         |                        |\r\n|                         | <cursor>       |\r\n|                         |                        |\r\n|                         |                        |\r\n+-----------------+-----------------+\r\n\r\nFocus is in the 'current window', cursor is on the <cursor> sign. \r\nI want to close 'help window' and keep working in current window.\r\n\r\nThat's what i need to do: \r\n\r\nCtrl_W h Ctrl_W k :q Ctrl_W l\r\n\r\nThis is pretty long!\r\nSo, I wrote this plugin to make it easy.\r\n\r\nIt provides 5 commands.\r\n\r\nFirstly, four commands for most-frequently actions:\r\n\r\n      :Qh means \"close left window and go back\"\r\n      :Qj means \"close lower window and go back\"\r\n      :Qk means \"close upper window and go back\"\r\n      :Ql means \"close right window and go back\"\r\n\r\nAnd one universal command:\r\n      :Q <args>, where <args> is movement commands to needed window.\r\n      \r\n      For example, \":Q hk\" means \"Go to the left window, then go to upper window,\r\n                                  close it and go back to source window\"\r\n\r\n      So, this long long command \"Ctrl_W h Ctrl_W k :q Ctrl_W l\"\r\n      is truncated to short expression: \":Q hk\"\r\n\r\nThere's one optional dependency: CmdAlias plugin (vimscript #746).\r\n\r\nIf CmdAlias is installed, then lowercased aliases of commands will be available:   :qh, :qj, :qk, :ql, :q <args>.\r\nI found it useful.\r\n\r\n\r\nPlease NOTE: \r\n\r\n1) if :Q without arguments is passed, then current window becomes closed.\r\n   (to provide compatibility of lowercased command :q)\r\n\r\n2) If argument is passed, but target window is the same as current window, then\r\n   no window will be closed.\r\n","4":"Often I need to close some another window and keep working in the current window.\r\nFor example, when I read some help in the upper window, and edit code in the lower\r\nwindow. At one time, I decide to close help window. To do it,\r\ni have to press \"Ctrl_W k :q\".\r\n\r\nNot very short. And this is not the worse variant.\r\nAnother variant:\r\n\r\n+-----------------+-----------------+\r\n|      help           |                        |\r\n|     window      |                        |\r\n|                         |     current      |\r\n+-----------------+     window     |\r\n|                         |                        |\r\n|                         | <cursor>       |\r\n|                         |                        |\r\n|                         |                        |\r\n+-----------------+-----------------+\r\n\r\nFocus is in the 'current window', cursor is on the <cursor> sign. \r\nI want to close 'help window' and keep working in current window.\r\n\r\nThat's what i need to do: \r\n\r\nCtrl_W h Ctrl_W k :q Ctrl_W l\r\n\r\nThis is pretty long!\r\nSo, I wrote this plugin to make it easy.\r\n\r\nIt provides 5 commands.\r\n\r\nFirstly, four commands for most-frequently actions:\r\n\r\n      :Qh means \"close left window and go back\"\r\n      :Qj means \"close lower window and go back\"\r\n      :Qk means \"close upper window and go back\"\r\n      :Ql means \"close right window and go back\"\r\n\r\nAnd one universal command:\r\n      :Q <args>, where <args> is movement commands to needed window.\r\n      \r\n      For example, \":Q hk\" means \"Go to the left window, then go to upper window,\r\n                                  close it and go back to source window\"\r\n\r\n      So, this long long command \"Ctrl_W h Ctrl_W k :q Ctrl_W l\"\r\n      is truncated to short expression: \":Q hk\"\r\n\r\nThere's one optional dependency: CmdAlias plugin (vimscript #746).\r\n\r\nIf CmdAlias is installed, then lowercased aliases of commands will be available:   :qh, :qj, :qk, :ql, :q <args>.\r\nI found it useful.\r\n\r\n\r\nPlease NOTE: \r\n\r\n1) if :Q without arguments is passed, then current window becomes closed.\r\n   (to provide compatibility of lowercased command :q)\r\n\r\n2) If argument is passed, but target window is the same as current window, then\r\n   no window will be closed.\r\n","install_details":"Use pathogen.\r\n\r\nOr just unpack contents of the package in your .vim directory.","5":"Use pathogen.\r\n\r\nOr just unpack contents of the package in your .vim directory.","first_name":"Dmitry","6":"Dmitry","last_name":"Frank","7":"Frank","releases":[{"0":"3573","vim_version":"7.0","1":"7.0","script_version":"1.04","2":"1.04","version_comment":"Added another useful shortcut for the universal command can be overridden via\r\nspecifying:\r\n\r\n      nmap <silent> <C-z> <Plug>QAnotherWin\r\n\r\n<C-z> is default. This shortcut waits you enter h,j,k,l as much as you want\r\nand finish your command with <Space>. The result will be same as :Q <args> but\r\nfaster.\r\n\r\nThis functionality was added by \u00c3\u009cmit Kablan.","3":"Added another useful shortcut for the universal command can be overridden via\r\nspecifying:\r\n\r\n      nmap <silent> <C-z> <Plug>QAnotherWin\r\n\r\n<C-z> is default. This shortcut waits you enter h,j,k,l as much as you want\r\nand finish your command with <Space>. The result will be same as :Q <args> but\r\nfaster.\r\n\r\nThis functionality was added by \u00c3\u009cmit Kablan.","package":"quit_another_window.tar.gz","4":"quit_another_window.tar.gz","src_id":"16401","5":"16401","creation_date":"1314690332","6":"1314690332"},{"0":"3573","vim_version":"7.0","1":"7.0","script_version":"1.03","2":"1.03","version_comment":"Added \"!\" ability to commands.","3":"Added \"!\" ability to commands.","package":"quit-another-window-1.03.tar.gz","4":"quit-another-window-1.03.tar.gz","src_id":"16089","5":"16089","creation_date":"1310966096","6":"1310966096"},{"0":"3573","vim_version":"7.0","1":"7.0","script_version":"1.02","2":"1.02","version_comment":"Initial upload","3":"Initial upload","package":"quit-another-window-1.01.tar.gz","4":"quit-another-window-1.01.tar.gz","src_id":"15568","5":"15568","creation_date":"1304360995","6":"1304360995"}]},"3572":{"script_id":"3572","0":"3572","script_name":"ro-when-swapfound","1":"ro-when-swapfound","script_type":"utility","2":"utility","summary":"Open Vim in read-only mode when swapfile is found.","3":"Open Vim in read-only mode when swapfile is found.","description":"Open Vim in read-only mode when swapfile is found.\r\n\r\nINTRODUCTION\r\nAvoid to display attention dialog,\r\nand open Vim in read-only mode when swapfile is found.\r\n\r\nIf you want to fix swapfile, and want to display attention dialog,\r\nyou do this.\r\n\r\n    :ToggleSwapCheck\r\n    :e\r\n\r\nSee also\r\nOpen same file read-only in second Vim\r\nhttp:\/\/vim.wikia.com\/wiki\/Open_same_file_read-only_in_second_Vim\r\n","4":"Open Vim in read-only mode when swapfile is found.\r\n\r\nINTRODUCTION\r\nAvoid to display attention dialog,\r\nand open Vim in read-only mode when swapfile is found.\r\n\r\nIf you want to fix swapfile, and want to display attention dialog,\r\nyou do this.\r\n\r\n    :ToggleSwapCheck\r\n    :e\r\n\r\nSee also\r\nOpen same file read-only in second Vim\r\nhttp:\/\/vim.wikia.com\/wiki\/Open_same_file_read-only_in_second_Vim\r\n","install_details":"1. copy files to your .vim or vimfiles direcory.\r\n2. helptags to your .vim\/doc or vimfiles\/doc direcory.\r\n\r\n    :helptags $HOME\/.vim\/doc\r\n\r\n    or\r\n\r\n    :helptags $HOME\/vimfiles\/doc\r\n\r\n","5":"1. copy files to your .vim or vimfiles direcory.\r\n2. helptags to your .vim\/doc or vimfiles\/doc direcory.\r\n\r\n    :helptags $HOME\/.vim\/doc\r\n\r\n    or\r\n\r\n    :helptags $HOME\/vimfiles\/doc\r\n\r\n","first_name":"omi","6":"omi","last_name":"taku","7":"taku","releases":[{"0":"3572","vim_version":"7.0","1":"7.0","script_version":"1.0.1","2":"1.0.1","version_comment":"add vim help.\r\nadd ToggleSwapCheck command.","3":"add vim help.\r\nadd ToggleSwapCheck command.","package":"vim-ro-when-swapfound.zip","4":"vim-ro-when-swapfound.zip","src_id":"15562","5":"15562","creation_date":"1304243296","6":"1304243296"},{"0":"3572","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"vim-ro-when-swapfound.zip","4":"vim-ro-when-swapfound.zip","src_id":"15561","5":"15561","creation_date":"1304240124","6":"1304240124"}]},"3571":{"script_id":"3571","0":"3571","script_name":"dogmatic.vim","1":"dogmatic.vim","script_type":"utility","2":"utility","summary":"Arrow keys are heretical","3":"Arrow keys are heretical","description":"Dogmatic is a Vim plugin that disables the arrow keys and lets you know how\r\noften you try to use them.\r\n\r\nI don't recommend Dogmatic for new Vim users, but once you are ready to\r\nfully embrace Vim you should find this plugin to be helpful in leveling up\r\nyour muscle memory of Vim's movement mappings.\r\n\r\nDogmatic does not prevent you from using the arrow keys on the cmdline.\r\n\r\nTo get the latest development version or to contribute additional Vim dogma visit https:\/\/github.com\/mrmargolis\/dogmatic.vim\r\n\r\n\r\n","4":"Dogmatic is a Vim plugin that disables the arrow keys and lets you know how\r\noften you try to use them.\r\n\r\nI don't recommend Dogmatic for new Vim users, but once you are ready to\r\nfully embrace Vim you should find this plugin to be helpful in leveling up\r\nyour muscle memory of Vim's movement mappings.\r\n\r\nDogmatic does not prevent you from using the arrow keys on the cmdline.\r\n\r\nTo get the latest development version or to contribute additional Vim dogma visit https:\/\/github.com\/mrmargolis\/dogmatic.vim\r\n\r\n\r\n","install_details":"Copy the dogmatic.vim file into your plugin directory or clone the github repo and use pathogen.","5":"Copy the dogmatic.vim file into your plugin directory or clone the github repo and use pathogen.","first_name":"Matthew","6":"Matthew","last_name":"Margolis","7":"Margolis","releases":[{"0":"3571","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"dogmatic.vim","4":"dogmatic.vim","src_id":"15553","5":"15553","creation_date":"1304210933","6":"1304210933"}]},"3570":{"script_id":"3570","0":"3570","script_name":"terse","1":"terse","script_type":"color scheme","2":"color scheme","summary":"a terse color scheme for vim","3":"a terse color scheme for vim","description":"A terse color theme. No candy colors, no wild contrasts, no green on black.\r\nN.B! The cterm version is woefully underdeveloped in this version. Don't use\r\nit.","4":"A terse color theme. No candy colors, no wild contrasts, no green on black.\r\nN.B! The cterm version is woefully underdeveloped in this version. Don't use\r\nit.","install_details":"Copy into your colors directory.","5":"Copy into your colors directory.","first_name":"Jevgeni","6":"Jevgeni","last_name":"Tarasov","7":"Tarasov","releases":[{"0":"3570","vim_version":"6.0","1":"6.0","script_version":"2","2":"2","version_comment":"Fixed issues. Revolutionized and monetized. Thought outside the box.","3":"Fixed issues. Revolutionized and monetized. Thought outside the box.","package":"terse.vim","4":"terse.vim","src_id":"15573","5":"15573","creation_date":"1304402401","6":"1304402401"},{"0":"3570","vim_version":"6.0","1":"6.0","script_version":"1","2":"1","version_comment":"Initial upload","3":"Initial upload","package":"terse.vim","4":"terse.vim","src_id":"15550","5":"15550","creation_date":"1304163201","6":"1304163201"}]},"3569":{"script_id":"3569","0":"3569","script_name":"modelica","1":"modelica","script_type":"syntax","2":"syntax","summary":"Modelica syntax file","3":"Modelica syntax file","description":"A syntax highlighting file for the Modelica equation-based modeling language.","4":"A syntax highlighting file for the Modelica equation-based modeling language.","install_details":"Copy the file into the syntax subdirectory.","5":"Copy the file into the syntax subdirectory.","first_name":"antoine","6":"antoine","last_name":"viel","7":"viel","releases":[{"0":"3569","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"modelica.vim","4":"modelica.vim","src_id":"15547","5":"15547","creation_date":"1304111105","6":"1304111105"}]},"3568":{"script_id":"3568","0":"3568","script_name":"Tabs only for indentation","1":"Tabs only for indentation","script_type":"indent","2":"indent","summary":"Using tabs only for indentation while editing","3":"Using tabs only for indentation while editing","description":"This plugin allows you to insert tabs only for indentation.\r\nIf left part of the cursor position in current line has only tabs or spaces,\r\nthen they will be replaced by tabs and one more tab will be added. \r\nIn other cases, only spaces will be added. That's all.\r\nI think, it will helpful because tabs not used for code alignment.\r\nBut, if you really need to insert tab, you can use <S-Tab> for this.\r\n\r\nPS: Sorry, another plugin doing the same can be found here:\r\nhttp:\/\/www.vim.org\/scripts\/script.php?script_id=2308\r\nI didn't search at all.","4":"This plugin allows you to insert tabs only for indentation.\r\nIf left part of the cursor position in current line has only tabs or spaces,\r\nthen they will be replaced by tabs and one more tab will be added. \r\nIn other cases, only spaces will be added. That's all.\r\nI think, it will helpful because tabs not used for code alignment.\r\nBut, if you really need to insert tab, you can use <S-Tab> for this.\r\n\r\nPS: Sorry, another plugin doing the same can be found here:\r\nhttp:\/\/www.vim.org\/scripts\/script.php?script_id=2308\r\nI didn't search at all.","install_details":"Only two things:\r\n1) Put this file to the plugin directory;\r\n2) Add the folowing line to your ~\/.vimrc config:\r\n    imap <Tab> <Plug>AXEIndentTabs\r\n","5":"Only two things:\r\n1) Put this file to the plugin directory;\r\n2) Add the folowing line to your ~\/.vimrc config:\r\n    imap <Tab> <Plug>AXEIndentTabs\r\n","first_name":"Makoto","6":"Makoto","last_name":"Nokata","7":"Nokata","releases":[{"0":"3568","vim_version":"7.0","1":"7.0","script_version":"1.1","2":"1.1","version_comment":"Fixed bug with wrong number of spaces. So, if tabsize = 4, then\r\nA<tab>\r\nin the beginning of line inserts 3 spaces, not 2\r\n","3":"Fixed bug with wrong number of spaces. So, if tabsize = 4, then\r\nA<tab>\r\nin the beginning of line inserts 3 spaces, not 2\r\n","package":"AXETabsOnlyForIndent.vim","4":"AXETabsOnlyForIndent.vim","src_id":"15622","5":"15622","creation_date":"1305036081","6":"1305036081"},{"0":"3568","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"AXETabsOnlyForIndent.vim","4":"AXETabsOnlyForIndent.vim","src_id":"15544","5":"15544","creation_date":"1304095563","6":"1304095563"}]},"3567":{"script_id":"3567","0":"3567","script_name":"colorizer","1":"colorizer","script_type":"utility","2":"utility","summary":"Highlight #rrggbb or #rgb color","3":"Highlight #rrggbb or #rgb color","description":"A modification of css_color.vim (vimscript #2150). It highlights all color strings in the form of #rrggbb or #rgb, regardless of file types, and unlike css_color.vim, it's able to find all colors in one line. It has support for 256-color terminals. It won't highlight color names.\r\n\r\nThis plugin defines three commands:\r\n\r\n\tColorHighlight\t- start\/update highlighting\r\n\tColorClear      - clear all highlights\r\n\tColorToggle     - toggle highlights\r\n\r\nBy default, <leader>tc is mapped to ColorToggle. If you want to use another\r\nkey map, do like this:\r\n\tnmap ,tc <Plug>Colorizer\r\n\r\nIf you want completely not to map it, set the following in your vimrc:\r\n      let g:colorizer_nomap = 1\r\n\r\nTo use solid color highlight, set this in your vimrc (later change won't\r\nprobably take effect unless you use ':ColorHighlight!' to force update):\r\n      let g:colorizer_fgcontrast = -1\r\nset it to 0 or 1 to use a softened foregroud color.\r\n\r\nNote: if you modify a color string in normal mode, if the cursor is still on\r\nthat line, it'll take 'updatetime' seconds to update. You can use\r\n:ColorHighlight (or your key mapping) again to force update.\r\n\r\nPerformace Notice: In terminal, it may take several seconds to highlight 240\r\ndifferent colors. GUI version is much quicker.\r\n\r\nLinks:\r\n* on github https:\/\/github.com\/lilydjwg\/colorizer\r\n* 中文介绍（非官方） Chinese introduction (unoffical)\r\n** http:\/\/www.gracecode.com\/archives\/3071\/\r\n\r\nSimilar plugin:\r\n* hexHighlight.vim vimscript #2937\r\n","4":"A modification of css_color.vim (vimscript #2150). It highlights all color strings in the form of #rrggbb or #rgb, regardless of file types, and unlike css_color.vim, it's able to find all colors in one line. It has support for 256-color terminals. It won't highlight color names.\r\n\r\nThis plugin defines three commands:\r\n\r\n\tColorHighlight\t- start\/update highlighting\r\n\tColorClear      - clear all highlights\r\n\tColorToggle     - toggle highlights\r\n\r\nBy default, <leader>tc is mapped to ColorToggle. If you want to use another\r\nkey map, do like this:\r\n\tnmap ,tc <Plug>Colorizer\r\n\r\nIf you want completely not to map it, set the following in your vimrc:\r\n      let g:colorizer_nomap = 1\r\n\r\nTo use solid color highlight, set this in your vimrc (later change won't\r\nprobably take effect unless you use ':ColorHighlight!' to force update):\r\n      let g:colorizer_fgcontrast = -1\r\nset it to 0 or 1 to use a softened foregroud color.\r\n\r\nNote: if you modify a color string in normal mode, if the cursor is still on\r\nthat line, it'll take 'updatetime' seconds to update. You can use\r\n:ColorHighlight (or your key mapping) again to force update.\r\n\r\nPerformace Notice: In terminal, it may take several seconds to highlight 240\r\ndifferent colors. GUI version is much quicker.\r\n\r\nLinks:\r\n* on github https:\/\/github.com\/lilydjwg\/colorizer\r\n* 中文介绍（非官方） Chinese introduction (unoffical)\r\n** http:\/\/www.gracecode.com\/archives\/3071\/\r\n\r\nSimilar plugin:\r\n* hexHighlight.vim vimscript #2937\r\n","install_details":"extract the tarball to ~\/.vim (or for windows, $VIM\/vimfiles)","5":"extract the tarball to ~\/.vim (or for windows, $VIM\/vimfiles)","first_name":"lilydjwg","6":"lilydjwg","last_name":" ","7":" ","releases":[{"0":"3567","vim_version":"7.0","1":"7.0","script_version":"1.4.2","2":"1.4.2","version_comment":"add support for #rrggbbaa and #aarrggbb (switchable)","3":"add support for #rrggbbaa and #aarrggbb (switchable)","package":"colorizer.tar.gz","4":"colorizer.tar.gz","src_id":"24031","5":"24031","creation_date":"1456066255","6":"1456066255"},{"0":"3567","vim_version":"7.0","1":"7.0","script_version":"1.4.1","2":"1.4.1","version_comment":"* fixed auto-startup regression (thanks to shanesmith)","3":"* fixed auto-startup regression (thanks to shanesmith)","package":"colorizer.tar.gz","4":"colorizer.tar.gz","src_id":"21373","5":"21373","creation_date":"1390653249","6":"1390653249"},{"0":"3567","vim_version":"7.0","1":"7.0","script_version":"1.4","2":"1.4","version_comment":"* improved performance and minimized startup time, thanks to blueyed\r\n* use TextChanged* events if availlable\r\n* other minor changes","3":"* improved performance and minimized startup time, thanks to blueyed\r\n* use TextChanged* events if availlable\r\n* other minor changes","package":"colorizer.tar.gz","4":"colorizer.tar.gz","src_id":"21330","5":"21330","creation_date":"1389943848","6":"1389943848"},{"0":"3567","vim_version":"7.0","1":"7.0","script_version":"1.3.1","2":"1.3.1","version_comment":"ColorToggle works again (after 1.3)","3":"ColorToggle works again (after 1.3)","package":"colorizer.vim","4":"colorizer.vim","src_id":"15621","5":"15621","creation_date":"1305026886","6":"1305026886"},{"0":"3567","vim_version":"7.0","1":"7.0","script_version":"1.3","2":"1.3","version_comment":"* remain highlight when colorscheme changed\r\n* update highlighting when BufRead\r\n* add g:colorizer_fgcontrast to change foreground color (now it can highlight the color code to a solid block like hexHighlight.vim does)\r\nThanks to Ingo Karkat and rykka.","3":"* remain highlight when colorscheme changed\r\n* update highlighting when BufRead\r\n* add g:colorizer_fgcontrast to change foreground color (now it can highlight the color code to a solid block like hexHighlight.vim does)\r\nThanks to Ingo Karkat and rykka.","package":"colorizer.vim","4":"colorizer.vim","src_id":"15613","5":"15613","creation_date":"1304940226","6":"1304940226"},{"0":"3567","vim_version":"7.0","1":"7.0","script_version":"1.2.1","2":"1.2.1","version_comment":"fix variable undefined error.","3":"fix variable undefined error.","package":"colorizer.vim","4":"colorizer.vim","src_id":"15597","5":"15597","creation_date":"1304699195","6":"1304699195"},{"0":"3567","vim_version":"7.0","1":"7.0","script_version":"1.1","2":"1.1","version_comment":"Use commands to invoke;\r\nAdd :ColorClear;\r\nSupport for #rgb form;\r\nOther improvements.\r\nThanks to Ingo Karkat.","3":"Use commands to invoke;\r\nAdd :ColorClear;\r\nSupport for #rgb form;\r\nOther improvements.\r\nThanks to Ingo Karkat.","package":"colorizer.vim","4":"colorizer.vim","src_id":"15580","5":"15580","creation_date":"1304516722","6":"1304516722"},{"0":"3567","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"colorizer.vim","4":"colorizer.vim","src_id":"15540","5":"15540","creation_date":"1303975585","6":"1303975585"}]},"3566":{"script_id":"3566","0":"3566","script_name":"m2sh.vim","1":"m2sh.vim","script_type":"syntax","2":"syntax","summary":"Syntax highlight file for m2sh config files","3":"Syntax highlight file for m2sh config files","description":"Syntax highlight file for m2sh (Mongrel2 Shell) config files.\r\n\r\nFind repo at: https:\/\/github.com\/eimantas\/m2sh.vim","4":"Syntax highlight file for m2sh (Mongrel2 Shell) config files.\r\n\r\nFind repo at: https:\/\/github.com\/eimantas\/m2sh.vim","install_details":"Extract the archive to ~\/.vim folder.","5":"Extract the archive to ~\/.vim folder.","first_name":"Eimantas","6":"Eimantas","last_name":"Vaiciunas","7":"Vaiciunas","releases":[{"0":"3566","vim_version":"7.0","1":"7.0","script_version":"0.2","2":"0.2","version_comment":"Extract to ~\/.vim\/ directory","3":"Extract to ~\/.vim\/ directory","package":"m2sh.zip","4":"m2sh.zip","src_id":"15537","5":"15537","creation_date":"1303929436","6":"1303929436"},{"0":"3566","vim_version":"7.0","1":"7.0","script_version":"0.1.1","2":"0.1.1","version_comment":"Added \"protocol\" keyword for handler settings.","3":"Added \"protocol\" keyword for handler settings.","package":"m2sh.vim","4":"m2sh.vim","src_id":"15536","5":"15536","creation_date":"1303924371","6":"1303924371"},{"0":"3566","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"m2sh.vim","4":"m2sh.vim","src_id":"15535","5":"15535","creation_date":"1303922543","6":"1303922543"}]},"3565":{"script_id":"3565","0":"3565","script_name":"Javascript OmniCompletion with YUI and j","1":"Javascript OmniCompletion with YUI and j","script_type":"ftplugin","2":"ftplugin","summary":"DO NOT USE YET - jQuery and YUI Omni Completion","3":"DO NOT USE YET - jQuery and YUI Omni Completion","description":"DO NOT USE YET... ALPHA Quality SOFTWARE\r\n\r\nDav Glass (https:\/\/github.com\/davglass) started the modification. He added the YUI 2 supports, so I\\\\\\'ve decided to build on top of that foundation.\r\n\r\nIt far from perfect but it is usable.\r\n\r\nEnjoy","4":"DO NOT USE YET... ALPHA Quality SOFTWARE\r\n\r\nDav Glass (https:\/\/github.com\/davglass) started the modification. He added the YUI 2 supports, so I\\\\\\'ve decided to build on top of that foundation.\r\n\r\nIt far from perfect but it is usable.\r\n\r\nEnjoy","install_details":"Copy this file into \r\n\r\n~\/.vim\/autoload","5":"Copy this file into \r\n\r\n~\/.vim\/autoload","first_name":"Jose","6":"Jose","last_name":"Elera","7":"Elera","releases":[{"0":"3565","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"javascriptcomplete.vim","4":"javascriptcomplete.vim","src_id":"15526","5":"15526","creation_date":"1303809659","6":"1303809659"}]},"3564":{"script_id":"3564","0":"3564","script_name":"hier","1":"hier","script_type":"utility","2":"utility","summary":"Highlight quickfix errors and location list entries","3":"Highlight quickfix errors and location list entries","description":"DESCRIPTION                                               *hier-description*\r\n\r\nHighlight quickfix errors and location list entries in buffer. This\r\nplugin was designed to support the editqf vim script (vimscript#3557)\r\nbut it also works very well stand alone.\r\n\r\nThis script can be downloaded from vimscript#3564. The latest\r\ndevelopment version is available at https:\/\/github.com\/jceb\/vim-hier.\r\n\r\n==========================================================================\r\nUSAGE                                                           *hier-usage*\r\n\r\nThe following commands are provided:\r\n\t:HierStart\t\t\" enable hier highlighting\r\n\t:HierStop\t\t\" disable hier highlighting\r\n\t:HierUpdate\t\t\" update error highlighting for current buffer\r\n\t:HierClear\t\t\" remove highlighting - it will be displayed again when :HierUpdate is called\r\n\r\n==========================================================================\r\nCUSTOMIZATION                                           *hier-customization*\r\n\r\nThe highlight group can be customized by setting the following variables.\r\nSetting a variable to the string \"\" will disable highlighting of that\r\ngroup. Every type can be highlighted differently (error, warning, info):\r\n\tlet g:hier_highlight_group_qf   = 'SpellBad'\r\n\tlet g:hier_highlight_group_qfw  = 'SpellLocal'\r\n\tlet g:hier_highlight_group_qfi  = 'SpellRare'\r\n\r\n\tlet g:hier_highlight_group_loc  = 'SpellBad'\r\n\tlet g:hier_highlight_group_locw = 'SpellLocal'\r\n\tlet g:hier_highlight_group_loci = 'SpellRare'\r\n\r\nEnable\/disable highlighting highlighting by default:\r\n\tlet g:hier_enabled              = 1","4":"DESCRIPTION                                               *hier-description*\r\n\r\nHighlight quickfix errors and location list entries in buffer. This\r\nplugin was designed to support the editqf vim script (vimscript#3557)\r\nbut it also works very well stand alone.\r\n\r\nThis script can be downloaded from vimscript#3564. The latest\r\ndevelopment version is available at https:\/\/github.com\/jceb\/vim-hier.\r\n\r\n==========================================================================\r\nUSAGE                                                           *hier-usage*\r\n\r\nThe following commands are provided:\r\n\t:HierStart\t\t\" enable hier highlighting\r\n\t:HierStop\t\t\" disable hier highlighting\r\n\t:HierUpdate\t\t\" update error highlighting for current buffer\r\n\t:HierClear\t\t\" remove highlighting - it will be displayed again when :HierUpdate is called\r\n\r\n==========================================================================\r\nCUSTOMIZATION                                           *hier-customization*\r\n\r\nThe highlight group can be customized by setting the following variables.\r\nSetting a variable to the string \"\" will disable highlighting of that\r\ngroup. Every type can be highlighted differently (error, warning, info):\r\n\tlet g:hier_highlight_group_qf   = 'SpellBad'\r\n\tlet g:hier_highlight_group_qfw  = 'SpellLocal'\r\n\tlet g:hier_highlight_group_qfi  = 'SpellRare'\r\n\r\n\tlet g:hier_highlight_group_loc  = 'SpellBad'\r\n\tlet g:hier_highlight_group_locw = 'SpellLocal'\r\n\tlet g:hier_highlight_group_loci = 'SpellRare'\r\n\r\nEnable\/disable highlighting highlighting by default:\r\n\tlet g:hier_enabled              = 1","install_details":"1. Download hier.vba\r\n2. Open file in vim and run :so % to install plugin \r\n3. Restart vim","5":"1. Download hier.vba\r\n2. Open file in vim and run :so % to install plugin \r\n3. Restart vim","first_name":"Jan Christoph","6":"Jan Christoph","last_name":"Ebersbach","7":"Ebersbach","releases":[{"0":"3564","vim_version":"7.0","1":"7.0","script_version":"1.3","2":"1.3","version_comment":"- fix problem when disabling the highlighting by setting the\r\n  hier_highlight_group variables to the empty string \"\"","3":"- fix problem when disabling the highlighting by setting the\r\n  hier_highlight_group variables to the empty string \"\"","package":"hier.vba","4":"hier.vba","src_id":"15978","5":"15978","creation_date":"1309084039","6":"1309084039"},{"0":"3564","vim_version":"7.0","1":"7.0","script_version":"1.2","2":"1.2","version_comment":"- add highlighting groups for warning and info entries\r\n- make clearing of highlighting behave more graceful towards other\r\n  plugins\r\n- add function s:Getlist to remove duplicated code","3":"- add highlighting groups for warning and info entries\r\n- make clearing of highlighting behave more graceful towards other\r\n  plugins\r\n- add function s:Getlist to remove duplicated code","package":"hier.vba","4":"hier.vba","src_id":"15624","5":"15624","creation_date":"1305057053","6":"1305057053"},{"0":"3564","vim_version":"7.0","1":"7.0","script_version":"1.1","2":"1.1","version_comment":"Initial upload","3":"Initial upload","package":"hier.vba.gz","4":"hier.vba.gz","src_id":"15523","5":"15523","creation_date":"1303801278","6":"1303801278"}]},"3563":{"script_id":"3563","0":"3563","script_name":"Amethyst","1":"Amethyst","script_type":"color scheme","2":"color scheme","summary":"A light colorscheme.","3":"A light colorscheme.","description":"A light color scheme for GVim with a purple-blue overall theme. Uses a light gray background, making the color scheme easy on the eyes while preserving good contrast and clarity.\r\n\r\nExamples using 10pt Consolas on Windows:\r\n\r\nC++ & C: http:\/\/users.jyu.fi\/~anhekalm\/misc\/amethyst_cpp_c.png\r\nHaskell & LaTeX: http:\/\/users.jyu.fi\/~anhekalm\/misc\/amethyst_hs_tex.png\r\nPython & C#: http:\/\/users.jyu.fi\/~anhekalm\/misc\/amethyst_py_cs.png\r\n","4":"A light color scheme for GVim with a purple-blue overall theme. Uses a light gray background, making the color scheme easy on the eyes while preserving good contrast and clarity.\r\n\r\nExamples using 10pt Consolas on Windows:\r\n\r\nC++ & C: http:\/\/users.jyu.fi\/~anhekalm\/misc\/amethyst_cpp_c.png\r\nHaskell & LaTeX: http:\/\/users.jyu.fi\/~anhekalm\/misc\/amethyst_hs_tex.png\r\nPython & C#: http:\/\/users.jyu.fi\/~anhekalm\/misc\/amethyst_py_cs.png\r\n","install_details":"Just drop the files into your colors directory (~\/.vim\/colors on unix, ~\/vimfiles\/colors\/ on win32) and type :colors amethyst","5":"Just drop the files into your colors directory (~\/.vim\/colors on unix, ~\/vimfiles\/colors\/ on win32) and type :colors amethyst","first_name":"Antoine","6":"Antoine","last_name":"Kalmbach","7":"Kalmbach","releases":[{"0":"3563","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"amethyst.vim","4":"amethyst.vim","src_id":"15517","5":"15517","creation_date":"1303680708","6":"1303680708"}]},"3562":{"script_id":"3562","0":"3562","script_name":"DayTimeColorer","1":"DayTimeColorer","script_type":"color scheme","2":"color scheme","summary":"Change color scheme according to position of the sun.","3":"Change color scheme according to position of the sun.","description":"This plugin calculates dawn, dusk, sunrise and sunset times and sets one of the four user defined color schemes according to sun position.\r\nGit repo: https:\/\/bitbucket.org\/redrampage\/daytime-colorer-vim\r\nYour vim must be compiled with +float feature.\r\nPlugin uses algorithm from \"Almanac for Computers, 1990\"\r\nWhich description has been found at:\r\nhttp:\/\/williams.best.vwh.net\/sunrise_sunset_algorithm.htm\r\nIdea of plugin is taken from:\r\nhttp:\/\/allaboutvim.blogspot.com\/2011\/01\/blog-post.html\r\n...and turned into overkill =)\r\nAutomatic refresh code is taken from: vimscript #2658","4":"This plugin calculates dawn, dusk, sunrise and sunset times and sets one of the four user defined color schemes according to sun position.\r\nGit repo: https:\/\/bitbucket.org\/redrampage\/daytime-colorer-vim\r\nYour vim must be compiled with +float feature.\r\nPlugin uses algorithm from \"Almanac for Computers, 1990\"\r\nWhich description has been found at:\r\nhttp:\/\/williams.best.vwh.net\/sunrise_sunset_algorithm.htm\r\nIdea of plugin is taken from:\r\nhttp:\/\/allaboutvim.blogspot.com\/2011\/01\/blog-post.html\r\n...and turned into overkill =)\r\nAutomatic refresh code is taken from: vimscript #2658","install_details":"Put the daytimecolorer.vim into .vim\/plugin\/\r\nAnd add following lines into your .vimrc:\r\n\r\n\" Define color schemes\r\nlet g:dtcDayScheme = \"pyte\"\r\nlet g:dtcNightScheme = \"wombat256\"\r\n\" Those are optional\r\nlet g:dtcDawnScheme = \"zenburn\"\r\nlet g:dtcDuskScheme = \"zenburn\"\r\n\r\n\" Set coordinates of your place\r\nlet g:dtcLatitude = 59.935\r\nlet g:dtcLongitude = 30.325\r\n\r\n\" Set your timezone\r\nlet g:dtcTimeOffset = 4\r\n\r\n\" Enable automatic color refresh (updates color scheme without restarting vim, but may use some extra resources)\r\nlet g:dtcAutoRefresh = 1\r\n","5":"Put the daytimecolorer.vim into .vim\/plugin\/\r\nAnd add following lines into your .vimrc:\r\n\r\n\" Define color schemes\r\nlet g:dtcDayScheme = \"pyte\"\r\nlet g:dtcNightScheme = \"wombat256\"\r\n\" Those are optional\r\nlet g:dtcDawnScheme = \"zenburn\"\r\nlet g:dtcDuskScheme = \"zenburn\"\r\n\r\n\" Set coordinates of your place\r\nlet g:dtcLatitude = 59.935\r\nlet g:dtcLongitude = 30.325\r\n\r\n\" Set your timezone\r\nlet g:dtcTimeOffset = 4\r\n\r\n\" Enable automatic color refresh (updates color scheme without restarting vim, but may use some extra resources)\r\nlet g:dtcAutoRefresh = 1\r\n","first_name":"red","6":"red","last_name":"rampage","7":"rampage","releases":[{"0":"3562","vim_version":"7.0","1":"7.0","script_version":"0.1.1","2":"0.1.1","version_comment":"Fixed screen flicker and unnecessary color scheme reloading","3":"Fixed screen flicker and unnecessary color scheme reloading","package":"daytimecolorer.vim","4":"daytimecolorer.vim","src_id":"15518","5":"15518","creation_date":"1303685691","6":"1303685691"},{"0":"3562","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"daytimecolorer.vim","4":"daytimecolorer.vim","src_id":"15514","5":"15514","creation_date":"1303673748","6":"1303673748"}]},"3561":{"script_id":"3561","0":"3561","script_name":"Table Helper","1":"Table Helper","script_type":"utility","2":"utility","summary":"Utility to help in the creation of tables of data","3":"Utility to help in the creation of tables of data","description":"Version 1.0:\r\n\r\nInitial version.\r\n\r\nThis plugin helps with aligning text in columns, making the creation of tables easier. The process is simple:\r\n\r\n1. Manually lay out one line of the table (the header, for example) and execute the command Gettabstopsfromcurrentline (there is a hotkey, in case you do this\r\noften) to have it parse the line and save the column definitions (per buffer).\r\n\r\n2. Go to any other lines that are supposed to be in the table and either hit the hotkey on them one by one or visually select a range and hit the hotkey and\r\nthey will all get realigned to match the header row.\r\n\r\nCaveat: these example may look horribly aligned if viewed with a proportional font.\r\n\r\nFor example, given these three rows of text:\r\n\r\nFirst name            Last name               Age\r\n------  -----  -----\r\nJohn   Smith   28\r\nJane             Doe          32\r\n\r\nIf the first line is the one parsed for the columns, hitting the hotkey on the remaining lines yields:\r\n\r\nFirst name            Last name               Age\r\n------                -----                   -----\r\nJohn                  Smith                   28\r\nJane                  Doe                     32\r\n\r\nIf you parse the last line instead you get this:\r\n\r\nFirst name       Last name    Age\r\n------           -----        -----\r\nJohn             Smith        28\r\nJane             Doe          32\r\n\r\nIf you have the repeat.vim autoload plugin installed, the reformatting is repeatable on other lines.\r\n\r\nRequirements: the column text has to be separated by at least 2 spaces, both for the header line and for each line that is to be reformatted. For example:\r\n\r\nFirst name  Last name  Age\r\n\r\nDefines three columns, as does:\r\n\r\nFirst name          Last name            Age\r\n\r\nOptions:\r\n\r\ng:TableHelper_truncateLongEntries (default 0): occasionally, you might have an entry in a table that is too long (say, you allocated 10 spaces for a column in\r\nthe header but the text is actually 12 characters). This option determines how that is handled:\r\n\r\n- If 1, the entry gets truncated to fit. You will lose data, but the table will still line up (small price to pay!)\r\n\r\n- If 0, the entry is put in as is and allowed to comprise as many columns as needed. The rest of the text is simply aligned to the next column. You will\r\n  retain all your data, but will lose formatting.\r\n\r\nIn practice, you should probably leave this value at 0. If you see misalignments, adjust your header row, recalculate the column stops, visually select your\r\ntable and hit the hotkey and the whole thing will be realigned. If you start truncating fields, your only recourse will be the undo (u) key. (I only put this\r\noption in at all because it was fairly easy to implement the truncation!)\r\n\r\ng:TableHelper_columnMargin (default 2): how much space must there be between the end of one column's text and the start of the next before it's considered too\r\nlong a column. Typically, you have to have some space between adjacent columns (or else, how can you tell where one column ends and the next begins). For\r\nexample, if your header row and first row of data look like this:\r\n\r\nFName    LName  Age\r\nJonathan  Smythe  28\r\n\r\nDuring reformat, the first column will be considered too long because there wouldn't be 2 spaces between Jonathan and Smythe (assuming\r\ng:TableHelper_columnMargin is set to 2--you can set it higher to get more space between columns). Thus, if you have truncation enabled\r\n(g:TableHelper_truncateLongEntries is 1), you'll get this:\r\n\r\nFName    LName  Age\r\nJonatha  Smyth  28\r\n\r\nAs it happens, the last name was too long, also. If you don't have truncation enabled, you get this:\r\n\r\nFName    LName  Age\r\nJonathan        Smythe  28\r\n\r\n\"Smythe\" simply gets pushed under the next available column and then, since the number of header columns runs out, subsequent columns of text are simply\r\nplaced as is, separated by g:TableHelper_columnMargin spaces.\r\n\r\nThis plugin requires at least two spaces between columns to be able to recognize them as distinct columns, so a value less than 2, while supported, will\r\nseriously jeopardize any attempts to reformat the table as all the text will run together (try setting it to 0...). If someone complains, I can force 2 as the\r\nminimum.\r\n\r\nIf you have my getVar.vim, then you can set these options on a per window, buffer or tab basis, also. (otherwise, only on a global basis).\r\n\r\nCommands:\r\n\r\nGettabstopsfromcurrentline: parses the current line for columns; probably best to call this from your header line, though you could also call it from the\r\nlongest line in your table (and then use the alignment hotkey to have the header conform to this, also).\r\n\r\nRetabline: Reformats the specified lines (visually selected or the current line) so they conform the previously specified header line.\r\n\r\nShowtabstops: Displays the list of tab stops currently defined, if any.\r\n\r\nMappings:\r\n\r\n<Plug>TableHelper_Gettabstopsfromcurrentline: executes Gettabstopsfromcurrentline (defaults to <leader><c-t>)\r\n\r\n<Plug>TableHelper_Retabline: executes Retabline (defaults to <c-t>). May be called again after changing the truncation or column margin options to change the\r\nalignment of already formatted lines.\r\n\r\nThe default hotkeys may be overridden in your vimrc.\r\n\r\nTip: if you call Gettabstopsfromcurrentline on an empty line, you get no column definitions; then, when you try to reformat a line, it just ends up having the\r\ncolumns of text displayed in their entirety, separated by g:TableHelper_columnMargin spaces. For example, if g:TableHelper_columnMargin is 5, this line\r\n\r\nJonathan                    Smythe  28\r\n\r\nbecomes\r\n\r\nJonathan     Smythe     28\r\n\r\nThis might be useful for first laying out the longest line in the table, calling Gettabstopsfromcurrentline on it and then reformatting the entire table based\r\non those column markers:\r\n\r\nFName        LName      Age\r\n-----        -----      ---\r\nJonathan     Smythe     28\r\nJon          Smith      32\r\n\r\nVersion 2.0:\r\n\r\nWhen calling Gettabstopsfromcurrentline, the last column size is set to the larger of the value of g:TableHelper_lastColumnSize or the length of the text in\r\nthe last column being measured. The very last column of text isn't truncated (unless lines with more columns than measured show up), but this value is used\r\nwhen generating separator lines.\r\n\r\nAdded some commands:\r\n\r\nAligntable: given a range of lines (visually selected, for example), will automatically figure out the optimum layout. Takes optional arguments: the column\r\nalignments (see Setcolumnalignments) and the amount by which the table should be indented. (If not specified, all alignments take the defaults as specified\r\nfor Setcolumnalignments and the indent becomes the indentation of the first line in the range).\r\n\r\nTo specify just an indent, pass in 'l' for the first argument (that's the default and all values get left-aligned anyway).\r\n\r\nAs an example, the following table\r\n\r\nFirst name            Last name               Age\r\n------  -----  -----\r\nJohn   Smith   28\r\nJane             Doe          32\r\n\r\ncan be selected visually and Aligntable executed to get (with a default column margin value of 2):\r\n\r\nFirst name  Last name  Age\r\n------      -----      -----\r\nJohn        Smith      28\r\nJane        Doe        32\r\n\r\nExecuting with a column margin of 10, on the other hand, gives:\r\n\r\nFirst name          Last name          Age\r\n------              -----              -----\r\nJohn                Smith              28\r\nJane                Doe                32\r\n\r\nThe column positions used are stored (clobbering any previous calls to Gettabstopsfromcurrentline) so new lines may be added to this table and reformatted\r\nquickly using the standard reformatting hotkey.\r\n\r\nAddseparatorline: adds a separator line just below the current cursor line. If the tab stops are from this line\r\n\r\nFirst name          Last name          Age\r\n\r\nthen executing \"Addseparatorline\" with the cursor on the line itself gives\r\n\r\nAddseparatorline\r\n------------------  -----------------  ----------\r\n\r\nThe space between separators is determined by g:TableHelper_columnMargin.\r\n\r\nThe command takes these arguments, all optional (with default values):\r\n\r\nAddseparatorline [continuous=0] [separator characters=g:TableHelper_separatorCharacters]\r\n\r\nThe first argument is whether to generate a continuous line (defaults to 0) or one with breaks at the column margins:\r\n\r\nAddseparatorline 0 -=\r\n-=-=-=-=-=-=-=-=-=  -=-=-=-=-=-=-=-=-  -=-=-=-=-=\r\n\r\nAddseparatorline 1 -=+\r\n-=+-=+-=+-=+-=+-=+-=+-=+-=+-=+-=+-=+-=+-=+-=+-=+-\r\n\r\nAnd the second determines the separators to use for this line.\r\n\r\nAddseparatorline 1 :-\r\n:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:\r\n\r\nSetcolumnalignments: Takes a string consisting of an arbitrary number of 'l' (left), 'c' (center) and 'r' (right); for example, 'llrlc'. When reformatting a\r\nline or calling Aligntable, this value is taken into consideration for how to align the value in a particular column. Thus, 'llrlc' means that the first\r\ntwo columns will be left-aligned, the third will be right-aligned, and then left and, finally, the last column will be centered in the allocated space.\r\n\r\nIf the table contains more columns than specified in the alignment, the remaining columns are all left-aligned ('l'). Column values that are too long (doesn't\r\nhappen when Aligntable is called unless the lines are added after the fact) end up being left-aligned (or truncated, in which case they fill up the entire\r\ncolumn and alignment doesn't enter into it).\r\n\r\nThe alignments are stored on a per-buffer basis (just like the table column stops).\r\n\r\nNew options:\r\n\r\ng:TableHelper_lastColumnSize (default 10): used for adding separator lines; specifies the minimum length for the last column\r\n\r\ng:TableHelper_separatorCharacters (default '-'): the character string that the separator comprises; gets repeated and truncated as necessary and starts over\r\nevery time there is a column break (repeats continuously if no break is chosen)\r\n","4":"Version 1.0:\r\n\r\nInitial version.\r\n\r\nThis plugin helps with aligning text in columns, making the creation of tables easier. The process is simple:\r\n\r\n1. Manually lay out one line of the table (the header, for example) and execute the command Gettabstopsfromcurrentline (there is a hotkey, in case you do this\r\noften) to have it parse the line and save the column definitions (per buffer).\r\n\r\n2. Go to any other lines that are supposed to be in the table and either hit the hotkey on them one by one or visually select a range and hit the hotkey and\r\nthey will all get realigned to match the header row.\r\n\r\nCaveat: these example may look horribly aligned if viewed with a proportional font.\r\n\r\nFor example, given these three rows of text:\r\n\r\nFirst name            Last name               Age\r\n------  -----  -----\r\nJohn   Smith   28\r\nJane             Doe          32\r\n\r\nIf the first line is the one parsed for the columns, hitting the hotkey on the remaining lines yields:\r\n\r\nFirst name            Last name               Age\r\n------                -----                   -----\r\nJohn                  Smith                   28\r\nJane                  Doe                     32\r\n\r\nIf you parse the last line instead you get this:\r\n\r\nFirst name       Last name    Age\r\n------           -----        -----\r\nJohn             Smith        28\r\nJane             Doe          32\r\n\r\nIf you have the repeat.vim autoload plugin installed, the reformatting is repeatable on other lines.\r\n\r\nRequirements: the column text has to be separated by at least 2 spaces, both for the header line and for each line that is to be reformatted. For example:\r\n\r\nFirst name  Last name  Age\r\n\r\nDefines three columns, as does:\r\n\r\nFirst name          Last name            Age\r\n\r\nOptions:\r\n\r\ng:TableHelper_truncateLongEntries (default 0): occasionally, you might have an entry in a table that is too long (say, you allocated 10 spaces for a column in\r\nthe header but the text is actually 12 characters). This option determines how that is handled:\r\n\r\n- If 1, the entry gets truncated to fit. You will lose data, but the table will still line up (small price to pay!)\r\n\r\n- If 0, the entry is put in as is and allowed to comprise as many columns as needed. The rest of the text is simply aligned to the next column. You will\r\n  retain all your data, but will lose formatting.\r\n\r\nIn practice, you should probably leave this value at 0. If you see misalignments, adjust your header row, recalculate the column stops, visually select your\r\ntable and hit the hotkey and the whole thing will be realigned. If you start truncating fields, your only recourse will be the undo (u) key. (I only put this\r\noption in at all because it was fairly easy to implement the truncation!)\r\n\r\ng:TableHelper_columnMargin (default 2): how much space must there be between the end of one column's text and the start of the next before it's considered too\r\nlong a column. Typically, you have to have some space between adjacent columns (or else, how can you tell where one column ends and the next begins). For\r\nexample, if your header row and first row of data look like this:\r\n\r\nFName    LName  Age\r\nJonathan  Smythe  28\r\n\r\nDuring reformat, the first column will be considered too long because there wouldn't be 2 spaces between Jonathan and Smythe (assuming\r\ng:TableHelper_columnMargin is set to 2--you can set it higher to get more space between columns). Thus, if you have truncation enabled\r\n(g:TableHelper_truncateLongEntries is 1), you'll get this:\r\n\r\nFName    LName  Age\r\nJonatha  Smyth  28\r\n\r\nAs it happens, the last name was too long, also. If you don't have truncation enabled, you get this:\r\n\r\nFName    LName  Age\r\nJonathan        Smythe  28\r\n\r\n\"Smythe\" simply gets pushed under the next available column and then, since the number of header columns runs out, subsequent columns of text are simply\r\nplaced as is, separated by g:TableHelper_columnMargin spaces.\r\n\r\nThis plugin requires at least two spaces between columns to be able to recognize them as distinct columns, so a value less than 2, while supported, will\r\nseriously jeopardize any attempts to reformat the table as all the text will run together (try setting it to 0...). If someone complains, I can force 2 as the\r\nminimum.\r\n\r\nIf you have my getVar.vim, then you can set these options on a per window, buffer or tab basis, also. (otherwise, only on a global basis).\r\n\r\nCommands:\r\n\r\nGettabstopsfromcurrentline: parses the current line for columns; probably best to call this from your header line, though you could also call it from the\r\nlongest line in your table (and then use the alignment hotkey to have the header conform to this, also).\r\n\r\nRetabline: Reformats the specified lines (visually selected or the current line) so they conform the previously specified header line.\r\n\r\nShowtabstops: Displays the list of tab stops currently defined, if any.\r\n\r\nMappings:\r\n\r\n<Plug>TableHelper_Gettabstopsfromcurrentline: executes Gettabstopsfromcurrentline (defaults to <leader><c-t>)\r\n\r\n<Plug>TableHelper_Retabline: executes Retabline (defaults to <c-t>). May be called again after changing the truncation or column margin options to change the\r\nalignment of already formatted lines.\r\n\r\nThe default hotkeys may be overridden in your vimrc.\r\n\r\nTip: if you call Gettabstopsfromcurrentline on an empty line, you get no column definitions; then, when you try to reformat a line, it just ends up having the\r\ncolumns of text displayed in their entirety, separated by g:TableHelper_columnMargin spaces. For example, if g:TableHelper_columnMargin is 5, this line\r\n\r\nJonathan                    Smythe  28\r\n\r\nbecomes\r\n\r\nJonathan     Smythe     28\r\n\r\nThis might be useful for first laying out the longest line in the table, calling Gettabstopsfromcurrentline on it and then reformatting the entire table based\r\non those column markers:\r\n\r\nFName        LName      Age\r\n-----        -----      ---\r\nJonathan     Smythe     28\r\nJon          Smith      32\r\n\r\nVersion 2.0:\r\n\r\nWhen calling Gettabstopsfromcurrentline, the last column size is set to the larger of the value of g:TableHelper_lastColumnSize or the length of the text in\r\nthe last column being measured. The very last column of text isn't truncated (unless lines with more columns than measured show up), but this value is used\r\nwhen generating separator lines.\r\n\r\nAdded some commands:\r\n\r\nAligntable: given a range of lines (visually selected, for example), will automatically figure out the optimum layout. Takes optional arguments: the column\r\nalignments (see Setcolumnalignments) and the amount by which the table should be indented. (If not specified, all alignments take the defaults as specified\r\nfor Setcolumnalignments and the indent becomes the indentation of the first line in the range).\r\n\r\nTo specify just an indent, pass in 'l' for the first argument (that's the default and all values get left-aligned anyway).\r\n\r\nAs an example, the following table\r\n\r\nFirst name            Last name               Age\r\n------  -----  -----\r\nJohn   Smith   28\r\nJane             Doe          32\r\n\r\ncan be selected visually and Aligntable executed to get (with a default column margin value of 2):\r\n\r\nFirst name  Last name  Age\r\n------      -----      -----\r\nJohn        Smith      28\r\nJane        Doe        32\r\n\r\nExecuting with a column margin of 10, on the other hand, gives:\r\n\r\nFirst name          Last name          Age\r\n------              -----              -----\r\nJohn                Smith              28\r\nJane                Doe                32\r\n\r\nThe column positions used are stored (clobbering any previous calls to Gettabstopsfromcurrentline) so new lines may be added to this table and reformatted\r\nquickly using the standard reformatting hotkey.\r\n\r\nAddseparatorline: adds a separator line just below the current cursor line. If the tab stops are from this line\r\n\r\nFirst name          Last name          Age\r\n\r\nthen executing \"Addseparatorline\" with the cursor on the line itself gives\r\n\r\nAddseparatorline\r\n------------------  -----------------  ----------\r\n\r\nThe space between separators is determined by g:TableHelper_columnMargin.\r\n\r\nThe command takes these arguments, all optional (with default values):\r\n\r\nAddseparatorline [continuous=0] [separator characters=g:TableHelper_separatorCharacters]\r\n\r\nThe first argument is whether to generate a continuous line (defaults to 0) or one with breaks at the column margins:\r\n\r\nAddseparatorline 0 -=\r\n-=-=-=-=-=-=-=-=-=  -=-=-=-=-=-=-=-=-  -=-=-=-=-=\r\n\r\nAddseparatorline 1 -=+\r\n-=+-=+-=+-=+-=+-=+-=+-=+-=+-=+-=+-=+-=+-=+-=+-=+-\r\n\r\nAnd the second determines the separators to use for this line.\r\n\r\nAddseparatorline 1 :-\r\n:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:\r\n\r\nSetcolumnalignments: Takes a string consisting of an arbitrary number of 'l' (left), 'c' (center) and 'r' (right); for example, 'llrlc'. When reformatting a\r\nline or calling Aligntable, this value is taken into consideration for how to align the value in a particular column. Thus, 'llrlc' means that the first\r\ntwo columns will be left-aligned, the third will be right-aligned, and then left and, finally, the last column will be centered in the allocated space.\r\n\r\nIf the table contains more columns than specified in the alignment, the remaining columns are all left-aligned ('l'). Column values that are too long (doesn't\r\nhappen when Aligntable is called unless the lines are added after the fact) end up being left-aligned (or truncated, in which case they fill up the entire\r\ncolumn and alignment doesn't enter into it).\r\n\r\nThe alignments are stored on a per-buffer basis (just like the table column stops).\r\n\r\nNew options:\r\n\r\ng:TableHelper_lastColumnSize (default 10): used for adding separator lines; specifies the minimum length for the last column\r\n\r\ng:TableHelper_separatorCharacters (default '-'): the character string that the separator comprises; gets repeated and truncated as necessary and starts over\r\nevery time there is a column break (repeats continuously if no break is chosen)\r\n","install_details":"Pop it into your plugin directory and set up the mappings and options if the defaults don't work for you.","5":"Pop it into your plugin directory and set up the mappings and options if the defaults don't work for you.","first_name":"Salman","6":"Salman","last_name":"Halim","7":"Halim","releases":[{"0":"3561","vim_version":"7.0","1":"7.0","script_version":"2.0","2":"2.0","version_comment":"New commands: Aligntable, Addseparatorline and Setcolumnalignments","3":"New commands: Aligntable, Addseparatorline and Setcolumnalignments","package":"TableHelper.vim","4":"TableHelper.vim","src_id":"15521","5":"15521","creation_date":"1303754907","6":"1303754907"},{"0":"3561","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"TableHelper.vim","4":"TableHelper.vim","src_id":"15513","5":"15513","creation_date":"1303615159","6":"1303615159"}]},"3560":{"script_id":"3560","0":"3560","script_name":"PairTools","1":"PairTools","script_type":"utility","2":"utility","summary":"Auto close pairs and tags","3":"Auto close pairs and tags","description":"The PairTools plugin can be seen as a \"bundle\" of tools to handle various\r\n\"pair\" operations. It also offers a flexible way to set pairs and options per\r\nfiletypes. Therefore, it is possible to have pairs and options set for editing \r\nC++ files while also editing XML files with other pairs and options inside the\r\nsame window.\r\n\r\nThe plugin is modular, i.e. related features are grouped inside a module, and \r\nother related features inside others groups. In the current version, there are \r\nthree modules: pairclamp.vim, tagwrench.vim and jigsaw.vim.\r\n\r\nThe PairClamp module works with single characters pairs such as (,). The\r\nTagWrench module works with angle brackets <,> and tags <tagname>. The Jigsaw\r\nmodule coordinates some key maps between PairClamp and TagWrench, such as when\r\npressing backspace and calling the right hook function. The pairtools.vim file \r\ndefines autocmds, mappings and options to make all the modules work.\r\n\r\nSee details at: https:\/\/github.com\/MartinLafreniere\/vim-PairTools\r\n","4":"The PairTools plugin can be seen as a \"bundle\" of tools to handle various\r\n\"pair\" operations. It also offers a flexible way to set pairs and options per\r\nfiletypes. Therefore, it is possible to have pairs and options set for editing \r\nC++ files while also editing XML files with other pairs and options inside the\r\nsame window.\r\n\r\nThe plugin is modular, i.e. related features are grouped inside a module, and \r\nother related features inside others groups. In the current version, there are \r\nthree modules: pairclamp.vim, tagwrench.vim and jigsaw.vim.\r\n\r\nThe PairClamp module works with single characters pairs such as (,). The\r\nTagWrench module works with angle brackets <,> and tags <tagname>. The Jigsaw\r\nmodule coordinates some key maps between PairClamp and TagWrench, such as when\r\npressing backspace and calling the right hook function. The pairtools.vim file \r\ndefines autocmds, mappings and options to make all the modules work.\r\n\r\nSee details at: https:\/\/github.com\/MartinLafreniere\/vim-PairTools\r\n","install_details":"Use the vimball: vim pairtools.vba followed by :so % and :quit.","5":"Use the vimball: vim pairtools.vba followed by :so % and :quit.","first_name":"Martin","6":"Martin","last_name":"Lafreniere","7":"Lafreniere","releases":[{"0":"3560","vim_version":"7.0","1":"7.0","script_version":"1.5.2","2":"1.5.2","version_comment":"Added TagWrench support for namespace and to use the hyphen inside a tag name\r\nFix various minor bugs.","3":"Added TagWrench support for namespace and to use the hyphen inside a tag name\r\nFix various minor bugs.","package":"pairtools.vba","4":"pairtools.vba","src_id":"15756","5":"15756","creation_date":"1306685187","6":"1306685187"},{"0":"3560","vim_version":"7.0","1":"7.0","script_version":"1.5.1","2":"1.5.1","version_comment":"Fixed case sensitiveness with autoload function call for case sensitive filesystem such as linux ext*.\r\nA few minor bug fixes.","3":"Fixed case sensitiveness with autoload function call for case sensitive filesystem such as linux ext*.\r\nA few minor bug fixes.","package":"pairtools.vba","4":"pairtools.vba","src_id":"15687","5":"15687","creation_date":"1305924222","6":"1305924222"},{"0":"3560","vim_version":"7.0","1":"7.0","script_version":"1.5","2":"1.5","version_comment":"Major plugin rework, see accompanying help file.","3":"Major plugin rework, see accompanying help file.","package":"pairtools.vba","4":"pairtools.vba","src_id":"15672","5":"15672","creation_date":"1305751926","6":"1305751926"},{"0":"3560","vim_version":"7.3","1":"7.3","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"pairtools.zip","4":"pairtools.zip","src_id":"15511","5":"15511","creation_date":"1303583239","6":"1303583239"}]},"3559":{"script_id":"3559","0":"3559","script_name":"gtrans.vim","1":"gtrans.vim","script_type":"utility","2":"utility","summary":"Vim上的翻译插件","3":"Vim上的翻译插件","description":"Vim上的英译汉插件，服务由Google提供，需要Python\r\n\r\n\"    Usage: 使用时，可以在可视模式下高亮选择文本，或者在普通模式下将光标移\r\n\"               到目标单词上，使用 \/gt 快捷键或者输入 :Gtrans 来获得翻译，默认\r\n\"               将内容翻译成为简体中文，可以修改 g:Gtrans_DefaultLang 改变默认\r\n\"               目标语言，如：\r\n\"                   let g:gtrans_DefaultLang = 'tw'\r\n\"               当然，设置的语言必须是初始就有或者你已经设置过的。可以通过传入\r\n\"               参数来设置翻译目标语言，如：\r\n\"                   :Gtrans('en')\r\n\"               不过目前只支持单词的翻译，因为输入命令的方法不能使用范围。不过\r\n\"               可以修改 g:gtrans_DefaultLang 以达到类似的效果。\r\n\"               初始可以翻译为三种语言：\r\n\"                   en : 英语\r\n\"                   zh : 简体中文\r\n\"                   tw : 繁体中文\r\n\"               可以通过设置 g:gtrans_LangDict 变量增加其他语言，如：\r\n\"                   let g:gtrans_LangDict = {\r\n\"                       目标语言的缩写（就是要传入的参数） : \r\n\"                       对应的语言名称缩写（需要通过GtransLangHelp 命令查找）\r\n\"                   }\r\n\r\nGithub: https:\/\/github.com\/bolasblack\/gtrans.vim\r\n\r\nI will update this plugin in GitHub, but not in vim.org.\r\n\r\npic: http:\/\/i.min.us\/ik3eaY.jpg","4":"Vim上的英译汉插件，服务由Google提供，需要Python\r\n\r\n\"    Usage: 使用时，可以在可视模式下高亮选择文本，或者在普通模式下将光标移\r\n\"               到目标单词上，使用 \/gt 快捷键或者输入 :Gtrans 来获得翻译，默认\r\n\"               将内容翻译成为简体中文，可以修改 g:Gtrans_DefaultLang 改变默认\r\n\"               目标语言，如：\r\n\"                   let g:gtrans_DefaultLang = 'tw'\r\n\"               当然，设置的语言必须是初始就有或者你已经设置过的。可以通过传入\r\n\"               参数来设置翻译目标语言，如：\r\n\"                   :Gtrans('en')\r\n\"               不过目前只支持单词的翻译，因为输入命令的方法不能使用范围。不过\r\n\"               可以修改 g:gtrans_DefaultLang 以达到类似的效果。\r\n\"               初始可以翻译为三种语言：\r\n\"                   en : 英语\r\n\"                   zh : 简体中文\r\n\"                   tw : 繁体中文\r\n\"               可以通过设置 g:gtrans_LangDict 变量增加其他语言，如：\r\n\"                   let g:gtrans_LangDict = {\r\n\"                       目标语言的缩写（就是要传入的参数） : \r\n\"                       对应的语言名称缩写（需要通过GtransLangHelp 命令查找）\r\n\"                   }\r\n\r\nGithub: https:\/\/github.com\/bolasblack\/gtrans.vim\r\n\r\nI will update this plugin in GitHub, but not in vim.org.\r\n\r\npic: http:\/\/i.min.us\/ik3eaY.jpg","install_details":"把文件复制到 $VIM\/plugin\/ 目录下即可","5":"把文件复制到 $VIM\/plugin\/ 目录下即可","first_name":"wang","6":"wang","last_name":"yicuan","7":"yicuan","releases":[{"0":"3559","vim_version":"7.2","1":"7.2","script_version":"0.2","2":"0.2","version_comment":"修改了一下 GetTrans 和 Translate 函数，可以传入目标语言","3":"修改了一下 GetTrans 和 Translate 函数，可以传入目标语言","package":"gtrans.vim","4":"gtrans.vim","src_id":"16122","5":"16122","creation_date":"1311255852","6":"1311255852"},{"0":"3559","vim_version":"7.2","1":"7.2","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"gtrans.vim","4":"gtrans.vim","src_id":"15509","5":"15509","creation_date":"1303534306","6":"1303534306"}]},"3558":{"script_id":"3558","0":"3558","script_name":"visual-increment","1":"visual-increment","script_type":"utility","2":"utility","summary":"Use CTRL+A\/X to create increasing sequence of numbers or letters via visual mode","3":"Use CTRL+A\/X to create increasing sequence of numbers or letters via visual mode","description":"http:\/\/triglav.github.com\/vim-visual-increment\/","4":"http:\/\/triglav.github.com\/vim-visual-increment\/","install_details":"","5":"","first_name":"Matej","6":"Matej","last_name":"Svec","7":"Svec","releases":[{"0":"3558","vim_version":"7.3","1":"7.3","script_version":"1.0.2","2":"1.0.2","version_comment":"Added some additional notes to the documentation","3":"Added some additional notes to the documentation","package":"visual-increment 1.0.2.7z","4":"visual-increment 1.0.2.7z","src_id":"15567","5":"15567","creation_date":"1304334575","6":"1304334575"},{"0":"3558","vim_version":"7.3","1":"7.3","script_version":"1.0.1","2":"1.0.1","version_comment":"Fixed an issue when user has rebound <C-A> or <C-X> to other action","3":"Fixed an issue when user has rebound <C-A> or <C-X> to other action","package":"visual-increment 1.0.1.7z","4":"visual-increment 1.0.1.7z","src_id":"15495","5":"15495","creation_date":"1303404860","6":"1303404860"},{"0":"3558","vim_version":"7.3","1":"7.3","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"visual-increment.7z","4":"visual-increment.7z","src_id":"15493","5":"15493","creation_date":"1303385377","6":"1303385377"}]},"3557":{"script_id":"3557","0":"3557","script_name":"editqf","1":"editqf","script_type":"utility","2":"utility","summary":"Make quickfix entries editable","3":"Make quickfix entries editable","description":"DESCRIPTION                                             *editqf-description*\r\n\r\nThis script is a reimplementation and continuation of the QuickFixNotes\r\nscript (vimscript#2216). Besides the original functionality of capturing\r\nnotes and storing them in a file, this script provides commands for easily\r\nloading the stored data, also for location lists.\r\n\r\nThough the main functionality of this script is to make editing of quickfix\r\nentries easy.\r\n\r\nI did a screencast giving an overview of the basic functionality of this\r\nplugin. It's available at vimeo: http:\/\/vimeo.com\/jceb\/editqf\r\n\r\nThis script can be downloaded from vimscript#3557. The latest development\r\nversion is available at https:\/\/github.com\/jceb\/vim-editqf.\r\n\r\n==========================================================================\r\nUSAGE                                                         *editqf-usage*\r\n\r\nCreate entries in the quickfix list by either running special a command\r\nlike :make or :grep or add a note by pressing <leader>n. Then bring up the\r\nquickfix window by running the command :cw.\r\n\r\nWhen you are in the quickfix window navigate to the entry you want to\r\nchange. Just press any key that would bring in into insert mode or change\r\nthe text like \"i\".  Automatically a new window will be opened containing\r\nall entries of the quickfix window.\r\n\r\nYou can use the regular editing commands for editing the entries. Once\r\nyou're done, just save the buffer and leave or close the window. I\r\nrecommend using :x, because this command does both with just one command.\r\nAfter that you are brought back to the error you initially started editing\r\nin the quickfix window.\r\n\r\nFor changing the type of a quickfix entry from within the quickfix window five\r\nconvenience shortcuts are provided:\r\n- I -> info\r\n- W -> warning\r\n- E -> error\r\n- << and >> -> cycle through the different types\r\n\r\nAdditionally the plugin provides the following commands that support\r\nstoring and restoring quickfix and location lists:\r\n\t:QFSave <FILENAME>\r\n\t:QFLoad <FILENAME>  \" default is to append to the current quickfix list\r\n\t:QFLoad! <FILENAME> \" replace quickfix list with the contents of file\r\n\t:QFAddNote [NOTE]   \" add quickfix entry with message NOTE\r\n\t:QFAddNote! [NOTE]  \" like :QFAddNote but start a new quickfix list\r\n\t:QFAddNotePattern[!] [NOTE] \" add quickfix entry matching the pattern of the current line\r\n\r\n\t:LocSave <FILENAME>\r\n\t:LocLoad <FILENAME>  \" default is to append to the current location list\r\n\t:LocLoad! <FILENAME> \" replace location list with the contents of file\r\n\t:LocAddNote [NOTE]   \" add location entry with message NOTE\r\n\t:LocAddNote! [NOTE]  \" like :LocAddNote but start a new location list\r\n\t:LocAddNotePattern[!] [NOTE] \" add location entry matching the pattern of the current line\r\n\r\nEditqf has integrated support for the hier script (vimscript#3564) which highlights\r\nquickfix errors to make them more visible.\r\n\r\n==========================================================================\r\nCUSTOMIZATION                                         *editqf-customization*\r\n\r\nThe default filename for storing and loading quickfix and location lists is\r\ncustomizable by setting the following variables in your vimrc:\r\n\tlet g:editqf_saveqf_filename  = \"quickfix.list\"\r\n\tlet g:editqf_saveloc_filename = \"location.list\"\r\n\r\nJump to the edited error when editing finished:\r\n\tlet g:editqf_jump_to_error = 1\r\n\r\nStore absolute filename when adding a new note\r\n\tlet g:editqf_store_absolute_filename = 1\r\n\r\nThe default keybinding <leader>n for adding a quickfix note can be\r\ncustomized by defining a mapping in your vimrc:\r\n\tnmap <leader>n <Plug>QFAddNote\r\n\tnmap <leader>N <Plug>QFAddNotePattern\r\n\tnmap <leader>l <Plug>LocAddNote\r\n\tnmap <leader>L <Plug>LocAddNotePattern\r\n\r\nAll mappings can be turned off by setting:\r\n\tlet g:editqf_no_mappings = 1","4":"DESCRIPTION                                             *editqf-description*\r\n\r\nThis script is a reimplementation and continuation of the QuickFixNotes\r\nscript (vimscript#2216). Besides the original functionality of capturing\r\nnotes and storing them in a file, this script provides commands for easily\r\nloading the stored data, also for location lists.\r\n\r\nThough the main functionality of this script is to make editing of quickfix\r\nentries easy.\r\n\r\nI did a screencast giving an overview of the basic functionality of this\r\nplugin. It's available at vimeo: http:\/\/vimeo.com\/jceb\/editqf\r\n\r\nThis script can be downloaded from vimscript#3557. The latest development\r\nversion is available at https:\/\/github.com\/jceb\/vim-editqf.\r\n\r\n==========================================================================\r\nUSAGE                                                         *editqf-usage*\r\n\r\nCreate entries in the quickfix list by either running special a command\r\nlike :make or :grep or add a note by pressing <leader>n. Then bring up the\r\nquickfix window by running the command :cw.\r\n\r\nWhen you are in the quickfix window navigate to the entry you want to\r\nchange. Just press any key that would bring in into insert mode or change\r\nthe text like \"i\".  Automatically a new window will be opened containing\r\nall entries of the quickfix window.\r\n\r\nYou can use the regular editing commands for editing the entries. Once\r\nyou're done, just save the buffer and leave or close the window. I\r\nrecommend using :x, because this command does both with just one command.\r\nAfter that you are brought back to the error you initially started editing\r\nin the quickfix window.\r\n\r\nFor changing the type of a quickfix entry from within the quickfix window five\r\nconvenience shortcuts are provided:\r\n- I -> info\r\n- W -> warning\r\n- E -> error\r\n- << and >> -> cycle through the different types\r\n\r\nAdditionally the plugin provides the following commands that support\r\nstoring and restoring quickfix and location lists:\r\n\t:QFSave <FILENAME>\r\n\t:QFLoad <FILENAME>  \" default is to append to the current quickfix list\r\n\t:QFLoad! <FILENAME> \" replace quickfix list with the contents of file\r\n\t:QFAddNote [NOTE]   \" add quickfix entry with message NOTE\r\n\t:QFAddNote! [NOTE]  \" like :QFAddNote but start a new quickfix list\r\n\t:QFAddNotePattern[!] [NOTE] \" add quickfix entry matching the pattern of the current line\r\n\r\n\t:LocSave <FILENAME>\r\n\t:LocLoad <FILENAME>  \" default is to append to the current location list\r\n\t:LocLoad! <FILENAME> \" replace location list with the contents of file\r\n\t:LocAddNote [NOTE]   \" add location entry with message NOTE\r\n\t:LocAddNote! [NOTE]  \" like :LocAddNote but start a new location list\r\n\t:LocAddNotePattern[!] [NOTE] \" add location entry matching the pattern of the current line\r\n\r\nEditqf has integrated support for the hier script (vimscript#3564) which highlights\r\nquickfix errors to make them more visible.\r\n\r\n==========================================================================\r\nCUSTOMIZATION                                         *editqf-customization*\r\n\r\nThe default filename for storing and loading quickfix and location lists is\r\ncustomizable by setting the following variables in your vimrc:\r\n\tlet g:editqf_saveqf_filename  = \"quickfix.list\"\r\n\tlet g:editqf_saveloc_filename = \"location.list\"\r\n\r\nJump to the edited error when editing finished:\r\n\tlet g:editqf_jump_to_error = 1\r\n\r\nStore absolute filename when adding a new note\r\n\tlet g:editqf_store_absolute_filename = 1\r\n\r\nThe default keybinding <leader>n for adding a quickfix note can be\r\ncustomized by defining a mapping in your vimrc:\r\n\tnmap <leader>n <Plug>QFAddNote\r\n\tnmap <leader>N <Plug>QFAddNotePattern\r\n\tnmap <leader>l <Plug>LocAddNote\r\n\tnmap <leader>L <Plug>LocAddNotePattern\r\n\r\nAll mappings can be turned off by setting:\r\n\tlet g:editqf_no_mappings = 1","install_details":"1. Download editqf.vba\r\n2. Open file in vim and run :so % to install plugin\r\n3. Restart vim\r\n","5":"1. Download editqf.vba\r\n2. Open file in vim and run :so % to install plugin\r\n3. Restart vim\r\n","first_name":"Jan Christoph","6":"Jan Christoph","last_name":"Ebersbach","7":"Ebersbach","releases":[{"0":"3557","vim_version":"7.0","1":"7.0","script_version":"1.5","2":"1.5","version_comment":"- preserve cursor position when saving qf or location list\r\n- remove redundant code to format lists\r\n- remove workaround with an empty line number or search pattern\r\n- don't suppress error messages anymore","3":"- preserve cursor position when saving qf or location list\r\n- remove redundant code to format lists\r\n- remove workaround with an empty line number or search pattern\r\n- don't suppress error messages anymore","package":"editqf.vba","4":"editqf.vba","src_id":"21308","5":"21308","creation_date":"1389458866","6":"1389458866"},{"0":"3557","vim_version":"7.0","1":"7.0","script_version":"1.4","2":"1.4","version_comment":"- add << and >> to cycle through quickfix types\r\n- move logic to an autoload plugin\r\n- fix timeouts for <Plug>s\r\n- minor fixes","3":"- add << and >> to cycle through quickfix types\r\n- move logic to an autoload plugin\r\n- fix timeouts for <Plug>s\r\n- minor fixes","package":"editqf.vba","4":"editqf.vba","src_id":"21305","5":"21305","creation_date":"1389389749","6":"1389389749"},{"0":"3557","vim_version":"7.0","1":"7.0","script_version":"1.3","2":"1.3","version_comment":"- add convenience shortcuts for changing the type of a quickfix entry (info,\r\n  warning or error)\r\n- fix change of note type from error to info","3":"- add convenience shortcuts for changing the type of a quickfix entry (info,\r\n  warning or error)\r\n- fix change of note type from error to info","package":"editqf.vba","4":"editqf.vba","src_id":"16374","5":"16374","creation_date":"1314462595","6":"1314462595"},{"0":"3557","vim_version":"7.0","1":"7.0","script_version":"1.2","2":"1.2","version_comment":"- fix issue when editing entries without a type by setting the default\r\n  type to error\r\n- make commands overwrite commands with the same name\r\n- clear autocommand groups at definition time\r\n- change note type from error to info","3":"- fix issue when editing entries without a type by setting the default\r\n  type to error\r\n- make commands overwrite commands with the same name\r\n- clear autocommand groups at definition time\r\n- change note type from error to info","package":"editqf.vba","4":"editqf.vba","src_id":"15623","5":"15623","creation_date":"1305056788","6":"1305056788"},{"0":"3557","vim_version":"7.0","1":"7.0","script_version":"1.1","2":"1.1","version_comment":"- add support for hier script for highlighting quickfix and location entries\r\n- add variable g:editqf_jump_to_error to make jumping to the last selected\r\n  error optional\r\n- add variable g:editqf_store_absolute_filename to let the user decide\r\n  whether filenames are stored with an absolute or relative path\r\n- prefix global variables with the plugin's name\r\n- move all functionality from Edit to Read function to allow editing of\r\n  qf:list and loc:list directly through vim commands (:e, :sp ...)\r\n- add support for patterns matching\r\n- add description of quickfix\/location fields to the editing buffer\r\n- allow deleting all entries from quickfix\/location list\r\n- change command and <Plug> names to start with prefix QF or Loc\r\n- general refactoring and cleanup","3":"- add support for hier script for highlighting quickfix and location entries\r\n- add variable g:editqf_jump_to_error to make jumping to the last selected\r\n  error optional\r\n- add variable g:editqf_store_absolute_filename to let the user decide\r\n  whether filenames are stored with an absolute or relative path\r\n- prefix global variables with the plugin's name\r\n- move all functionality from Edit to Read function to allow editing of\r\n  qf:list and loc:list directly through vim commands (:e, :sp ...)\r\n- add support for patterns matching\r\n- add description of quickfix\/location fields to the editing buffer\r\n- allow deleting all entries from quickfix\/location list\r\n- change command and <Plug> names to start with prefix QF or Loc\r\n- general refactoring and cleanup","package":"editqf.vba.gz","4":"editqf.vba.gz","src_id":"15522","5":"15522","creation_date":"1303799743","6":"1303799743"},{"0":"3557","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"editqf.vim","4":"editqf.vim","src_id":"15491","5":"15491","creation_date":"1303364743","6":"1303364743"}]},"3556":{"script_id":"3556","0":"3556","script_name":"openscad.vim","1":"openscad.vim","script_type":"syntax","2":"syntax","summary":"Simple syntax highlighting for the OpenSCAD language","3":"Simple syntax highlighting for the OpenSCAD language","description":"This is a quick hack at syntax highlighting for the OpenSCAD 3D modeling language -- http:\/\/www.openscad.org\/\r\n\r\nNote that at the moment it doesn\\'t help detect errors such as mismatched blocks and parens.\r\n\r\nTODOs include error management and quickfix\/compiler support.\r\n\r\nI would appreciate feedback and suggestions for improvement, please use the script wiki link above.\r\n\r\nThe plugin is hosted on github, see https:\/\/github.com\/sirtaj\/vim-openscad","4":"This is a quick hack at syntax highlighting for the OpenSCAD 3D modeling language -- http:\/\/www.openscad.org\/\r\n\r\nNote that at the moment it doesn\\'t help detect errors such as mismatched blocks and parens.\r\n\r\nTODOs include error management and quickfix\/compiler support.\r\n\r\nI would appreciate feedback and suggestions for improvement, please use the script wiki link above.\r\n\r\nThe plugin is hosted on github, see https:\/\/github.com\/sirtaj\/vim-openscad","install_details":"The zip file contains one file each in ftdetect\/ and syntax\/. Copy these dirs into your .vim (or vimfiles), or use a\r\nvim bundle tool.","5":"The zip file contains one file each in ftdetect\/ and syntax\/. Copy these dirs into your .vim (or vimfiles), or use a\r\nvim bundle tool.","first_name":"Sirtaj","6":"Sirtaj","last_name":"Singh Kang","7":"Singh Kang","releases":[{"0":"3556","vim_version":"6.0","1":"6.0","script_version":"0.3","2":"0.3","version_comment":"Added ftdetect and poly2d functions, fixed a ref to TODO highlights.","3":"Added ftdetect and poly2d functions, fixed a ref to TODO highlights.","package":"vim-openscad.zip","4":"vim-openscad.zip","src_id":"19594","5":"19594","creation_date":"1362487845","6":"1362487845"},{"0":"3556","vim_version":"6.0","1":"6.0","script_version":"0.2","2":"0.2","version_comment":"Added some missing keywords, better compliance with vim syntax guidelines.","3":"Added some missing keywords, better compliance with vim syntax guidelines.","package":"openscad.vim","4":"openscad.vim","src_id":"15479","5":"15479","creation_date":"1303207414","6":"1303207414"}]},"3555":{"script_id":"3555","0":"3555","script_name":"fso","1":"fso","script_type":"utility","2":"utility","summary":"file system operations under cursor and more","3":"file system operations under cursor and more","description":"Enable vim user to do some operating action on file on which cursor is passing over\r\n\r\no Usage\r\n\r\n\tJust type \r\n           :REN to rename  file under cursor       \r\n           :DEL to delete file under cursor       \r\n           :INF to display informations of file under cursor       \r\n           :BROZ to browse filepath of file under cursor       \r\n\r\n           :LSD to access to those features from popupmenu\r\n\r\n\r\no Filenames\/Filepaths recognition\r\n\r\n  1.Check that filename under cursor exists and is in an opened NERDTree buffer\r\n  2.Check that filename under cursor is readable\r\n  3.Check that path of opend buffer concated with filepath under cursor is readable\r\n  4.Check the current opened buffer exists and ask user to modify it.","4":"Enable vim user to do some operating action on file on which cursor is passing over\r\n\r\no Usage\r\n\r\n\tJust type \r\n           :REN to rename  file under cursor       \r\n           :DEL to delete file under cursor       \r\n           :INF to display informations of file under cursor       \r\n           :BROZ to browse filepath of file under cursor       \r\n\r\n           :LSD to access to those features from popupmenu\r\n\r\n\r\no Filenames\/Filepaths recognition\r\n\r\n  1.Check that filename under cursor exists and is in an opened NERDTree buffer\r\n  2.Check that filename under cursor is readable\r\n  3.Check that path of opend buffer concated with filepath under cursor is readable\r\n  4.Check the current opened buffer exists and ask user to modify it.","install_details":"1. Just put this vimscript into $home\/vimfiles\/plugin\r\n2. Type :FSOHLP\r\nthis will generate help file, and then you can consult itby typing :h fso\r\n","5":"1. Just put this vimscript into $home\/vimfiles\/plugin\r\n2. Type :FSOHLP\r\nthis will generate help file, and then you can consult itby typing :h fso\r\n","first_name":"niva","6":"niva","last_name":"niva","7":"niva","releases":[{"0":"3555","vim_version":"7.0","1":"7.0","script_version":"1.7","2":"1.7","version_comment":"Use NERDTree to do file system operations. It is better !\r\n","3":"Use NERDTree to do file system operations. It is better !\r\n","package":"fso.vim","4":"fso.vim","src_id":"16364","5":"16364","creation_date":"1314385549","6":"1314385549"}]},"3554":{"script_id":"3554","0":"3554","script_name":"emacscommandline","1":"emacscommandline","script_type":"utility","2":"utility","summary":"makes command-line mode behave more like the Unix command line","3":"makes command-line mode behave more like the Unix command line","description":"This plugin makes the command-line mode behave more like the Unix command\r\nline, by adding Emacs-style mappings (like in the Bash shell).  Some of the\r\nmappings just map existing vim commands, but the rest implement functionality\r\nthat is not available natively.\r\n\r\nRepository: https:\/\/github.com\/houtsnip\/vim-emacscommandline\r\n\r\nMOVEMENT\r\n\r\nCTRL-A         move cursor to beginning of line\r\nCTRL-E         move cursor to end of line (i.e the native vim behaviour:\r\n                 see c_CTRL-E).  Not actually a re-mapping, but noted here\r\n                 anyway for completeness.\r\nCTRL-B         move cursor one character backwards\r\nCTRL-F         move cursor one character forwards (overwrites c_CTRL-F)\r\nMETA-B         move cursor one word backwards\r\nMETA-F         move cursor one word forwards\r\n\r\nDELETION\r\n\r\nCTRL-D         delete character under cursor\r\nCTRL-K         kill line (delete from character under cursor to end of line)\r\n                 (overwrites insert digraph: see c_CTRL-K.  This is a shame,\r\n                 but personally I don't use this much in command-line mode.)\r\nCTRL-U         backwards kill line (delete backwards to beginning of line)\r\n                 (i.e. the same behaviour as in Bash: unix-line-discard)\r\nMETA-D         delete word under cursor\r\nMETA-Backspace delete word backwards\r\nCTRL-W         delete backwards to previous white-space character\r\n                 (i.e. the same behaviour as in Bash: unix-word-rubout)\r\n\r\nHISTORY\r\n\r\nCTRL-P         previous line in history (same as <Up>)\r\nCTRL-N         next line in history (same as <Down>)\r\nMETA-R         search history backwards\r\n                 (It would be nice to use the mapping CTRL-R, but this is\r\n                 already used for insert register: see c_CTRL-R.)\r\n\r\nOTHER\r\n\r\nCTRL-Y         paste (yank) last deleted text (overwrites c_CTRL-Y).\r\n                 Note that in Emacs, 'yank' means 'paste', whereas in vim it\r\n                 means 'copy'.  The same text is also available in the\r\n                 registry 'c'.\r\nCTRL-_         undo last change (overwrites c_CTRL-_)\r\nCTRL-X_CTRL-U   \"    \"    \"\r\nCTRL-Z         toggle command-line as external command (overwrites suspend\r\n                 vim in the terminal)\r\n\r\nOLD KEYS\r\n\r\nThe old functions are all mapped to the same combination prefixed by CTRL-O.\r\nSo for example, to open the command-line window (see c_CTRL-F), press\r\ninstead CTRL-O_CTRL-F. \r\n\r\nWARNING\r\n\r\nThis plugin buggers up the expression register (i.e. c_CTRL-R_=).  This is\r\na limitation of vim.  I don't know how to switch these mappings off in the\r\nexpression register and I don't think it's possible. However I never use the\r\nexpression register except in mappings, so it doesn't affect me.\r\n\r\n","4":"This plugin makes the command-line mode behave more like the Unix command\r\nline, by adding Emacs-style mappings (like in the Bash shell).  Some of the\r\nmappings just map existing vim commands, but the rest implement functionality\r\nthat is not available natively.\r\n\r\nRepository: https:\/\/github.com\/houtsnip\/vim-emacscommandline\r\n\r\nMOVEMENT\r\n\r\nCTRL-A         move cursor to beginning of line\r\nCTRL-E         move cursor to end of line (i.e the native vim behaviour:\r\n                 see c_CTRL-E).  Not actually a re-mapping, but noted here\r\n                 anyway for completeness.\r\nCTRL-B         move cursor one character backwards\r\nCTRL-F         move cursor one character forwards (overwrites c_CTRL-F)\r\nMETA-B         move cursor one word backwards\r\nMETA-F         move cursor one word forwards\r\n\r\nDELETION\r\n\r\nCTRL-D         delete character under cursor\r\nCTRL-K         kill line (delete from character under cursor to end of line)\r\n                 (overwrites insert digraph: see c_CTRL-K.  This is a shame,\r\n                 but personally I don't use this much in command-line mode.)\r\nCTRL-U         backwards kill line (delete backwards to beginning of line)\r\n                 (i.e. the same behaviour as in Bash: unix-line-discard)\r\nMETA-D         delete word under cursor\r\nMETA-Backspace delete word backwards\r\nCTRL-W         delete backwards to previous white-space character\r\n                 (i.e. the same behaviour as in Bash: unix-word-rubout)\r\n\r\nHISTORY\r\n\r\nCTRL-P         previous line in history (same as <Up>)\r\nCTRL-N         next line in history (same as <Down>)\r\nMETA-R         search history backwards\r\n                 (It would be nice to use the mapping CTRL-R, but this is\r\n                 already used for insert register: see c_CTRL-R.)\r\n\r\nOTHER\r\n\r\nCTRL-Y         paste (yank) last deleted text (overwrites c_CTRL-Y).\r\n                 Note that in Emacs, 'yank' means 'paste', whereas in vim it\r\n                 means 'copy'.  The same text is also available in the\r\n                 registry 'c'.\r\nCTRL-_         undo last change (overwrites c_CTRL-_)\r\nCTRL-X_CTRL-U   \"    \"    \"\r\nCTRL-Z         toggle command-line as external command (overwrites suspend\r\n                 vim in the terminal)\r\n\r\nOLD KEYS\r\n\r\nThe old functions are all mapped to the same combination prefixed by CTRL-O.\r\nSo for example, to open the command-line window (see c_CTRL-F), press\r\ninstead CTRL-O_CTRL-F. \r\n\r\nWARNING\r\n\r\nThis plugin buggers up the expression register (i.e. c_CTRL-R_=).  This is\r\na limitation of vim.  I don't know how to switch these mappings off in the\r\nexpression register and I don't think it's possible. However I never use the\r\nexpression register except in mappings, so it doesn't affect me.\r\n\r\n","install_details":"","5":"","first_name":"Houtsnip","6":"Houtsnip","last_name":"-","7":"-","releases":[{"0":"3554","vim_version":"7.0","1":"7.0","script_version":"1.3","2":"1.3","version_comment":"Added mappings for following \u00e2\u0080\u0094\r\n \u00e2\u0080\u00a2 go to first \/ last line in history (Meta-< and Meta->)\r\n \u00e2\u0080\u00a2 transpose character under cursor with previous character (Ctrl-T)","3":"Added mappings for following \u00e2\u0080\u0094\r\n \u00e2\u0080\u00a2 go to first \/ last line in history (Meta-< and Meta->)\r\n \u00e2\u0080\u00a2 transpose character under cursor with previous character (Ctrl-T)","package":"emacscommandline.zip","4":"emacscommandline.zip","src_id":"25647","5":"25647","creation_date":"1510867388","6":"1510867388"},{"0":"3554","vim_version":"7.0","1":"7.0","script_version":"1.2","2":"1.2","version_comment":"New features:\r\n \u00e2\u0080\u00a2 added many options to allow customization of plug-in\r\n \u00e2\u0080\u00a2 made Ctrl-E, Ctrl-F, Ctrl-K, and Meta-D mappings use native vim functionality when cursor is at end of line\r\n \u00e2\u0080\u00a2 changed search command line mapping (Meta-R) now use Ctrl-R, and made it use the native functionality except when the command line is empty\r\n \u00e2\u0080\u00a2 added Ctrl-G mapping (abort command line)","3":"New features:\r\n \u00e2\u0080\u00a2 added many options to allow customization of plug-in\r\n \u00e2\u0080\u00a2 made Ctrl-E, Ctrl-F, Ctrl-K, and Meta-D mappings use native vim functionality when cursor is at end of line\r\n \u00e2\u0080\u00a2 changed search command line mapping (Meta-R) now use Ctrl-R, and made it use the native functionality except when the command line is empty\r\n \u00e2\u0080\u00a2 added Ctrl-G mapping (abort command line)","package":"emacscommandline.zip","4":"emacscommandline.zip","src_id":"25636","5":"25636","creation_date":"1510141593","6":"1510141593"},{"0":"3554","vim_version":"7.0","1":"7.0","script_version":"1.1","2":"1.1","version_comment":"Fixed <Backspace> and <Del> for multi-byte characters","3":"Fixed <Backspace> and <Del> for multi-byte characters","package":"emacscommandline.tar.gz","4":"emacscommandline.tar.gz","src_id":"15824","5":"15824","creation_date":"1307370521","6":"1307370521"},{"0":"3554","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"emacscommandline.tar.gz","4":"emacscommandline.tar.gz","src_id":"15468","5":"15468","creation_date":"1303112167","6":"1303112167"}]},"3553":{"script_id":"3553","0":"3553","script_name":"sudoku_game","1":"sudoku_game","script_type":"game","2":"game","summary":"SudoKu, very popular game.The objective is to fill a 9\u00c3\u00979 grid with 1-9.","3":"SudoKu, very popular game.The objective is to fill a 9\u00c3\u00979 grid with 1-9.","description":"The objective is to fill a 9\u00c3\u00979 grid with digits so that each column, each row, and each of the nine 3\u00c3\u00973 sub-grids that compose the grid (also called \\\"boxes\\\", \\\"blocks\\\", \\\"regions\\\", or \\\"sub-squares\\\") contains all of the digits from 1 to 9. \r\n\r\n\r\n\\\" Write this script for sue. \r\n\\\"\r\n\\\" Usage:\r\n\\\"       Start game: type SudokuEasy\/SudokuMedium\/SudokuHard\/SudokuVeryHard in\r\n\\\"       command line \r\n\\\"       If you want create a customization Sudoku, type SudokuCustom <init\r\n\\\"       numbers count>, the count is between 20 and 80\r\n\\\"       use hjkl\/HJKL to move around. use HJKL quick move to the number need\r\n\\\"       input\r\n\\\"       u:undo ctrl-r:redo\r\n\\\"       ?:show right answer under cursor\r\n\\\"\r\n\\\"       Welcome to email me! Enjoy yourself! \r\n\\\"\r\n\\\"Attention:\r\n\\\"       ########Need python support! #########\r\n\\\"\r\n\\\"       Because I don\\'t kown how to create random in vim srcipt.\r\n\\\"       I use lots of random numbers to create sudoku. If you know,\r\n\\\"       send email to me! Thanks!\r\n\\\"\r\n\\\"Email: \r\n\\\"       wuhong40@163.com","4":"The objective is to fill a 9\u00c3\u00979 grid with digits so that each column, each row, and each of the nine 3\u00c3\u00973 sub-grids that compose the grid (also called \\\"boxes\\\", \\\"blocks\\\", \\\"regions\\\", or \\\"sub-squares\\\") contains all of the digits from 1 to 9. \r\n\r\n\r\n\\\" Write this script for sue. \r\n\\\"\r\n\\\" Usage:\r\n\\\"       Start game: type SudokuEasy\/SudokuMedium\/SudokuHard\/SudokuVeryHard in\r\n\\\"       command line \r\n\\\"       If you want create a customization Sudoku, type SudokuCustom <init\r\n\\\"       numbers count>, the count is between 20 and 80\r\n\\\"       use hjkl\/HJKL to move around. use HJKL quick move to the number need\r\n\\\"       input\r\n\\\"       u:undo ctrl-r:redo\r\n\\\"       ?:show right answer under cursor\r\n\\\"\r\n\\\"       Welcome to email me! Enjoy yourself! \r\n\\\"\r\n\\\"Attention:\r\n\\\"       ########Need python support! #########\r\n\\\"\r\n\\\"       Because I don\\'t kown how to create random in vim srcipt.\r\n\\\"       I use lots of random numbers to create sudoku. If you know,\r\n\\\"       send email to me! Thanks!\r\n\\\"\r\n\\\"Email: \r\n\\\"       wuhong40@163.com","install_details":"put file to .vim\/plugin\/\r\n  ########Need python support! #########","5":"put file to .vim\/plugin\/\r\n  ########Need python support! #########","first_name":"Hong","6":"Hong","last_name":"Wu","7":"Wu","releases":[{"0":"3553","vim_version":"7.0","1":"7.0","script_version":"1.1","2":"1.1","version_comment":"Fix Bug: modify Cursor -> cursor","3":"Fix Bug: modify Cursor -> cursor","package":"sudoku_game.vim","4":"sudoku_game.vim","src_id":"15641","5":"15641","creation_date":"1305466273","6":"1305466273"},{"0":"3553","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"sudoku_game.vim","4":"sudoku_game.vim","src_id":"15444","5":"15444","creation_date":"1302706967","6":"1302706967"}]},"3552":{"script_id":"3552","0":"3552","script_name":"Message Formatter","1":"Message Formatter","script_type":"utility","2":"utility","summary":"An plugin to ease typing of repetitive of code","3":"An plugin to ease typing of repetitive of code","description":"This plugin allows the simplification of repetitive code fragments, allowing\r\nmuch faster entry; for example, this text\r\n        getset  List<String>  names\r\n\r\ngets converted to\r\n        public List<String> getNames()\r\n        {\r\n                return m_names;\r\n        }\r\n\r\n        public void setNames( List<String> val )\r\n        {\r\n                m_names = val;\r\n        }\r\n\r\nMore importantly, it figures out when you're defining a boolean variable and\r\nreplaces the \"get\" with \"is\"; thus,\r\n        getset  boolean  old enough\r\n\r\nbecomes\r\n        public boolean isOldEnough()\r\n        {\r\n                return m_oldEnough;\r\n        }\r\n\r\n        public void setOldEnough( boolean val )\r\n        {\r\n                m_oldEnough = val;\r\n        }\r\n\r\nObserve how \"old enough\" was automatically camel-cased to \"oldEnough\", and,\r\nwhen used with \"get\" or \"is\", was also capitalized. The same variable can be\r\nused over and over again, each time with (if desired) different formatting\r\ndirectives; for example, this template pattern\r\n        My name is {john::f_fName} and my full name is {{fName} smith::uq_fullName}.\r\n\r\ngets expanded to\r\n        My name is John and my full name is \"JOHN SMITH\".\r\n\r\nObserve, also, how the \"fullName\" directive recursively contained and expanded\r\nthe fName directive.\r\n\r\nIn the \"getset\" example, the \"get\" is defined as:\r\n\r\nAddlocaltemplate get public {::type} {eval '{type}' ==? 'boolean' ? 'is' : 'get'::get}{::cf_property}()\\n{\\nreturn m_{c_property};\\n}\r\n\r\nThe \"set\" is defined as:\r\n\r\nAddlocaltemplate set public void set{::cf_property}( {::type} val )\\n{\\nm_{c_property} = val;\\n}\r\n\r\nAnd the \"getset\" is defined simply as:\r\n\r\nAddlocaltemplate getset {tem get::getTem}\\n\\n{tem set::setTem}\r\n\r\nThis allows \"get\" and \"set\" to be used independently (for read-only or write-only properties, for example) and doesn't require duplication of code to define a separate \"getset\".","4":"This plugin allows the simplification of repetitive code fragments, allowing\r\nmuch faster entry; for example, this text\r\n        getset  List<String>  names\r\n\r\ngets converted to\r\n        public List<String> getNames()\r\n        {\r\n                return m_names;\r\n        }\r\n\r\n        public void setNames( List<String> val )\r\n        {\r\n                m_names = val;\r\n        }\r\n\r\nMore importantly, it figures out when you're defining a boolean variable and\r\nreplaces the \"get\" with \"is\"; thus,\r\n        getset  boolean  old enough\r\n\r\nbecomes\r\n        public boolean isOldEnough()\r\n        {\r\n                return m_oldEnough;\r\n        }\r\n\r\n        public void setOldEnough( boolean val )\r\n        {\r\n                m_oldEnough = val;\r\n        }\r\n\r\nObserve how \"old enough\" was automatically camel-cased to \"oldEnough\", and,\r\nwhen used with \"get\" or \"is\", was also capitalized. The same variable can be\r\nused over and over again, each time with (if desired) different formatting\r\ndirectives; for example, this template pattern\r\n        My name is {john::f_fName} and my full name is {{fName} smith::uq_fullName}.\r\n\r\ngets expanded to\r\n        My name is John and my full name is \"JOHN SMITH\".\r\n\r\nObserve, also, how the \"fullName\" directive recursively contained and expanded\r\nthe fName directive.\r\n\r\nIn the \"getset\" example, the \"get\" is defined as:\r\n\r\nAddlocaltemplate get public {::type} {eval '{type}' ==? 'boolean' ? 'is' : 'get'::get}{::cf_property}()\\n{\\nreturn m_{c_property};\\n}\r\n\r\nThe \"set\" is defined as:\r\n\r\nAddlocaltemplate set public void set{::cf_property}( {::type} val )\\n{\\nm_{c_property} = val;\\n}\r\n\r\nAnd the \"getset\" is defined simply as:\r\n\r\nAddlocaltemplate getset {tem get::getTem}\\n\\n{tem set::setTem}\r\n\r\nThis allows \"get\" and \"set\" to be used independently (for read-only or write-only properties, for example) and doesn't require duplication of code to define a separate \"getset\".","install_details":"Source the Vimball archive.","5":"Source the Vimball archive.","first_name":"Salman","6":"Salman","last_name":"Halim","7":"Halim","releases":[{"0":"3552","vim_version":"7.0","1":"7.0","script_version":"9.0","2":"9.0","version_comment":"Added a new mapping: <Plug>PlaceInlineTemplateForLine; allows for template expansion on the current line even if the template is somewhere in the middle of the line.\r\n","3":"Added a new mapping: <Plug>PlaceInlineTemplateForLine; allows for template expansion on the current line even if the template is somewhere in the middle of the line.\r\n","package":"MessageFormatter.vba","4":"MessageFormatter.vba","src_id":"16313","5":"16313","creation_date":"1313907649","6":"1313907649"},{"0":"3552","vim_version":"7.0","1":"7.0","script_version":"8.5","2":"8.5","version_comment":"New directive (<LS>) to go along with <CR>, <SW>. See :help MessageFormatter_LS.\r\n\r\nAdded a command: ApplySameTemplateToMultipleLines\r\n\r\nAdded a mapping: <Plug>PlaceTemplatesForRange\r\n","3":"New directive (<LS>) to go along with <CR>, <SW>. See :help MessageFormatter_LS.\r\n\r\nAdded a command: ApplySameTemplateToMultipleLines\r\n\r\nAdded a mapping: <Plug>PlaceTemplatesForRange\r\n","package":"MessageFormatter.vba","4":"MessageFormatter.vba","src_id":"16287","5":"16287","creation_date":"1313593829","6":"1313593829"},{"0":"3552","vim_version":"7.3","1":"7.3","script_version":"8.0","2":"8.0","version_comment":"New special value: \"iab\" to expand insert-mode abbreviations inline; see :help MessageFormatter_iab.\r\n\r\nNew mapping: <Plug>InsertModeCompletion (\/\/ by default) that will complete templates during insert-mode.\r\n","3":"New special value: \"iab\" to expand insert-mode abbreviations inline; see :help MessageFormatter_iab.\r\n\r\nNew mapping: <Plug>InsertModeCompletion (\/\/ by default) that will complete templates during insert-mode.\r\n","package":"MessageFormatter.vba","4":"MessageFormatter.vba","src_id":"15817","5":"15817","creation_date":"1307329803","6":"1307329803"},{"0":"3552","vim_version":"7.0","1":"7.0","script_version":"7.5","2":"7.5","version_comment":"New special value: \"tem\" to include other template definitions inline; see :help MessageFormatter_tem.\r\n","3":"New special value: \"tem\" to include other template definitions inline; see :help MessageFormatter_tem.\r\n","package":"MessageFormatter.vba","4":"MessageFormatter.vba","src_id":"15627","5":"15627","creation_date":"1305171435","6":"1305171435"},{"0":"3552","vim_version":"7.3","1":"7.3","script_version":"7.0","2":"7.0","version_comment":"New option: g:MessageFormatter_moveArgumentsToStart; if 1 (the default), input arguments are moved to the front for easier expansion. See :help\r\ng:MessageFormatter_moveArgumentsToStart for details.\r\n\r\nMore new options: g:MessageFormatter_highlightDirectives and g:MessageFormatter_highlightDirectivesLink; control the highlighting of directives in text to\r\nmake them stand out.\r\n\r\nNew command: Setcolordirectives: toggles the directive highlighting feature.\r\n","3":"New option: g:MessageFormatter_moveArgumentsToStart; if 1 (the default), input arguments are moved to the front for easier expansion. See :help\r\ng:MessageFormatter_moveArgumentsToStart for details.\r\n\r\nMore new options: g:MessageFormatter_highlightDirectives and g:MessageFormatter_highlightDirectivesLink; control the highlighting of directives in text to\r\nmake them stand out.\r\n\r\nNew command: Setcolordirectives: toggles the directive highlighting feature.\r\n","package":"MessageFormatter.vba","4":"MessageFormatter.vba","src_id":"15612","5":"15612","creation_date":"1304914697","6":"1304914697"},{"0":"3552","vim_version":"7.3","1":"7.3","script_version":"6.5","2":"6.5","version_comment":"New modifier:\r\n\r\no: if the value is non-empty, prepends a \", \" (a comma and a space); otherwise, leaves it empty\r\nP: Just like 'p', but ignores empty strings\r\nQ: Just like 'q', but ignores empty strings\r\n","3":"New modifier:\r\n\r\no: if the value is non-empty, prepends a \", \" (a comma and a space); otherwise, leaves it empty\r\nP: Just like 'p', but ignores empty strings\r\nQ: Just like 'q', but ignores empty strings\r\n","package":"MessageFormatter.vba","4":"MessageFormatter.vba","src_id":"15600","5":"15600","creation_date":"1304732541","6":"1304732541"},{"0":"3552","vim_version":"7.3","1":"7.3","script_version":"6.0","2":"6.0","version_comment":"Added an option: g:MessageFormatter_autoAddJumpToEnd; if this is 1 (the default) and if a parameter contains !jump! directives, another !jump! is added to the end to allow the user to quickly continue typing beyond the template. See :help g:MessageFormatter_autoAddJumpToEnd.\r\n","3":"Added an option: g:MessageFormatter_autoAddJumpToEnd; if this is 1 (the default) and if a parameter contains !jump! directives, another !jump! is added to the end to allow the user to quickly continue typing beyond the template. See :help g:MessageFormatter_autoAddJumpToEnd.\r\n","package":"MessageFormatter.vba","4":"MessageFormatter.vba","src_id":"15589","5":"15589","creation_date":"1304619468","6":"1304619468"},{"0":"3552","vim_version":"7.3","1":"7.3","script_version":"5.5","2":"5.5","version_comment":"Fixed bug in default processing.\r\n\r\nImproved help and added examples to help (:help MessageFormatter_Examples).\r\n","3":"Fixed bug in default processing.\r\n\r\nImproved help and added examples to help (:help MessageFormatter_Examples).\r\n","package":"MessageFormatter.vba","4":"MessageFormatter.vba","src_id":"15581","5":"15581","creation_date":"1304538117","6":"1304538117"},{"0":"3552","vim_version":"7.3","1":"7.3","script_version":"5.0","2":"5.0","version_comment":"Added a default value mechanism: if a template variable is defined like this:\r\n\r\n{def John::firstName}\r\n\r\nthen, during expansion, if an empty value is passed in for firstName, \"John\" will be used instead. This value can be recursive and may contain other\r\nparameters, as before. (Including other \"def\" expansions.)\r\n\r\nAlso, parameters with default values may be left out to have their default value used; see :help MessageFormatter_def for more details.\r\n","3":"Added a default value mechanism: if a template variable is defined like this:\r\n\r\n{def John::firstName}\r\n\r\nthen, during expansion, if an empty value is passed in for firstName, \"John\" will be used instead. This value can be recursive and may contain other\r\nparameters, as before. (Including other \"def\" expansions.)\r\n\r\nAlso, parameters with default values may be left out to have their default value used; see :help MessageFormatter_def for more details.\r\n","package":"MessageFormatter.vba","4":"MessageFormatter.vba","src_id":"15576","5":"15576","creation_date":"1304450347","6":"1304450347"},{"0":"3552","vim_version":"7.3","1":"7.3","script_version":"4.5","2":"4.5","version_comment":"Bug fixes, mostly, though added one more option:\r\n\r\ng:MessageFormatter_formatCurrentLineAsFallback (default 1): if attempting to format a template via the <Plug>FormatCurrentTemplate mapping when not actually\r\nin a template, will fall back to formatting just the current line as an ad-hoc template if this is 1. If 0, will give an error message instead.\r\n","3":"Bug fixes, mostly, though added one more option:\r\n\r\ng:MessageFormatter_formatCurrentLineAsFallback (default 1): if attempting to format a template via the <Plug>FormatCurrentTemplate mapping when not actually\r\nin a template, will fall back to formatting just the current line as an ad-hoc template if this is 1. If 0, will give an error message instead.\r\n","package":"MessageFormatter.vba","4":"MessageFormatter.vba","src_id":"15566","5":"15566","creation_date":"1304303682","6":"1304303682"},{"0":"3552","vim_version":"7.3","1":"7.3","script_version":"4.0","2":"4.0","version_comment":"Added a proper help file; no actual functionality changes.","3":"Added a proper help file; no actual functionality changes.","package":"MessageFormatter.vba","4":"MessageFormatter.vba","src_id":"15548","5":"15548","creation_date":"1304125912","6":"1304125912"},{"0":"3552","vim_version":"7.3","1":"7.3","script_version":"4.0","2":"4.0","version_comment":"Templates can be expanded inline while typing, allowing for macro expansion.","3":"Templates can be expanded inline while typing, allowing for macro expansion.","package":"MessageFormatter.vba","4":"MessageFormatter.vba","src_id":"15543","5":"15543","creation_date":"1304051265","6":"1304051265"},{"0":"3552","vim_version":"7.0","1":"7.0","script_version":"3.5","2":"3.5","version_comment":"Added a command version of FormatContainedMessage called Formatcontainedmessage that passes everything on the command-line as-is to the function and echoes\r\nthe result.\r\n\r\nAdded a new default value type:\r\n\r\nIf the default value for for a parameter (passed to FormatContainedMessage) is \"ask\", it defaults to asking the user (via an input). If the value is anything\r\nfollowed by \"ask\", it will use that as the default value for the input.\r\n","3":"Added a command version of FormatContainedMessage called Formatcontainedmessage that passes everything on the command-line as-is to the function and echoes\r\nthe result.\r\n\r\nAdded a new default value type:\r\n\r\nIf the default value for for a parameter (passed to FormatContainedMessage) is \"ask\", it defaults to asking the user (via an input). If the value is anything\r\nfollowed by \"ask\", it will use that as the default value for the input.\r\n","package":"MessageFormatter.zip","4":"MessageFormatter.zip","src_id":"15484","5":"15484","creation_date":"1303275937","6":"1303275937"},{"0":"3552","vim_version":"7.0","1":"7.0","script_version":"3.0","2":"3.0","version_comment":"Fairly big changes. RELIES UPON MY GetVar.vim (http:\/\/vim.sourceforge.net\/scripts\/script.php?script_id=353) script now.\r\n\r\nNew formatting parameter:\r\n\r\nn: non-displayed value. The return value is suppressed--useful for adding a value to the cache to be used later.\r\n\r\nNew function:\r\n\r\nFormatContainedMessage: Works like MessageFormatter#FormatMessage except that it's always recursive and that its original text string can contain default\r\nvalues for the parameters (so the second parameter is optional); for example,\r\n\r\nSome new commands, also.","3":"Fairly big changes. RELIES UPON MY GetVar.vim (http:\/\/vim.sourceforge.net\/scripts\/script.php?script_id=353) script now.\r\n\r\nNew formatting parameter:\r\n\r\nn: non-displayed value. The return value is suppressed--useful for adding a value to the cache to be used later.\r\n\r\nNew function:\r\n\r\nFormatContainedMessage: Works like MessageFormatter#FormatMessage except that it's always recursive and that its original text string can contain default\r\nvalues for the parameters (so the second parameter is optional); for example,\r\n\r\nSome new commands, also.","package":"MessageFormatter.zip","4":"MessageFormatter.zip","src_id":"15481","5":"15481","creation_date":"1303243003","6":"1303243003"},{"0":"3552","vim_version":"7.0","1":"7.0","script_version":"2.0","2":"2.0","version_comment":"Added new formatting modifier:\r\n\r\ne: Escapes out quotation marks (\") and backslashes, leaving the value suitable for placing in quotes. For example, {e_fName} where fName is Jo\\nhn results in\r\nJo\\\\nhn.\r\n\r\nIf an expansion parameter starts with \"eval \", the rest of the value is evaluated and the return value used as the actual parameter value. If recursion is on,\r\nthat value may contain further parameters.\r\n\r\nExample:\r\n\r\necho MessageFormatter#FormatMessage('public static final {type} {C_variable} = {value};', {'type':'eval input(\"Type for {variable}: \", \"String\")', 'variable':'eval input(\"Variable name: \")', 'value':'eval input(\"Value: \", \"\\\"{C_variable}\\\"\")'}, 1)\r\n\r\nBear in mind that 'type' and 'value' both use the parameter 'variable'. If 'variable' were to refer to either of these, you'd have circular recursion. There\r\nis no check in place for that; you'd just end up with a stack overflow.\r\n\r\nNote, also, that the expression is evaluated only once. After that, its value is stored on the cache--this allows eval parameters to refer to other eval\r\nparameters (only useful if recursion is on).\r\n","3":"Added new formatting modifier:\r\n\r\ne: Escapes out quotation marks (\") and backslashes, leaving the value suitable for placing in quotes. For example, {e_fName} where fName is Jo\\nhn results in\r\nJo\\\\nhn.\r\n\r\nIf an expansion parameter starts with \"eval \", the rest of the value is evaluated and the return value used as the actual parameter value. If recursion is on,\r\nthat value may contain further parameters.\r\n\r\nExample:\r\n\r\necho MessageFormatter#FormatMessage('public static final {type} {C_variable} = {value};', {'type':'eval input(\"Type for {variable}: \", \"String\")', 'variable':'eval input(\"Variable name: \")', 'value':'eval input(\"Value: \", \"\\\"{C_variable}\\\"\")'}, 1)\r\n\r\nBear in mind that 'type' and 'value' both use the parameter 'variable'. If 'variable' were to refer to either of these, you'd have circular recursion. There\r\nis no check in place for that; you'd just end up with a stack overflow.\r\n\r\nNote, also, that the expression is evaluated only once. After that, its value is stored on the cache--this allows eval parameters to refer to other eval\r\nparameters (only useful if recursion is on).\r\n","package":"MessageFormatter.vim","4":"MessageFormatter.vim","src_id":"15440","5":"15440","creation_date":"1302616748","6":"1302616748"},{"0":"3552","vim_version":"7.0","1":"7.0","script_version":"1.5","2":"1.5","version_comment":"Added a cache so repeated expansions of the same variable can be looked up rather than computed (potentially much faster, especially when recursion is on).","3":"Added a cache so repeated expansions of the same variable can be looked up rather than computed (potentially much faster, especially when recursion is on).","package":"MessageFormatter.vim","4":"MessageFormatter.vim","src_id":"15430","5":"15430","creation_date":"1302564662","6":"1302564662"},{"0":"3552","vim_version":"7.2","1":"7.2","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"MessageFormatter.vim","4":"MessageFormatter.vim","src_id":"15428","5":"15428","creation_date":"1302552873","6":"1302552873"}]},"3551":{"script_id":"3551","0":"3551","script_name":"gsearch","1":"gsearch","script_type":"utility","2":"utility","summary":"Search Google inside Vim","3":"Search Google inside Vim","description":"This vimscript allows you to search Google inside Vim. You just need to enter the command \":Google <search_term>\" and Vim will switch to text-based browser 'links' and search Google for <search_term> just entered.\r\n\r\nExample: :Google vim rocks\r\n\r\nTo quit from links and return back to Vim click on 'q' then 'Enter' twice.","4":"This vimscript allows you to search Google inside Vim. You just need to enter the command \":Google <search_term>\" and Vim will switch to text-based browser 'links' and search Google for <search_term> just entered.\r\n\r\nExample: :Google vim rocks\r\n\r\nTo quit from links and return back to Vim click on 'q' then 'Enter' twice.","install_details":"As any other plugin in Vim. Copy the vimscript to your ~\/.vim\/plugin and make sure that you've got 'links' browser installed in your box.\r\n\r\nOr you can modify the vimscript to use 'lynx' instead","5":"As any other plugin in Vim. Copy the vimscript to your ~\/.vim\/plugin and make sure that you've got 'links' browser installed in your box.\r\n\r\nOr you can modify the vimscript to use 'lynx' instead","first_name":"Saleh","6":"Saleh","last_name":"Alsanad","7":"Alsanad","releases":[{"0":"3551","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"gsearch.vim","4":"gsearch.vim","src_id":"15424","5":"15424","creation_date":"1302458754","6":"1302458754"}]},"3550":{"script_id":"3550","0":"3550","script_name":"vim-online","1":"vim-online","script_type":"color scheme","2":"color scheme","summary":"A color scheme based on the colors of *this* website","3":"A color scheme based on the colors of *this* website","description":"Take a look at the screenshot...\r\n\r\nhttp:\/\/img824.imageshack.us\/i\/vimonline.png\/","4":"Take a look at the screenshot...\r\n\r\nhttp:\/\/img824.imageshack.us\/i\/vimonline.png\/","install_details":"","5":"","first_name":"Dee Sub Wun","6":"Dee Sub Wun","last_name":".","7":".","releases":[{"0":"3550","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"vim-online.vim","4":"vim-online.vim","src_id":"15423","5":"15423","creation_date":"1302444192","6":"1302444192"}]},"3549":{"script_id":"3549","0":"3549","script_name":"plexer","1":"plexer","script_type":"utility","2":"utility","summary":"Arbitrary Multi-line multi-edit plugin","3":"Arbitrary Multi-line multi-edit plugin","description":"For usage and other documentation please go to the project repo:\r\nhttps:\/\/github.com\/alfredodeza\/plexer.vim","4":"For usage and other documentation please go to the project repo:\r\nhttps:\/\/github.com\/alfredodeza\/plexer.vim","install_details":"Simply drop plexer.vim in your plugin directory or if you are using Pathogen, place the plexer.vim directory in your bundle dir.","5":"Simply drop plexer.vim in your plugin directory or if you are using Pathogen, place the plexer.vim directory in your bundle dir.","first_name":"Alfredo","6":"Alfredo","last_name":"Deza","7":"Deza","releases":[{"0":"3549","vim_version":"7.3","1":"7.3","script_version":"0.0.1","2":"0.0.1","version_comment":"Initial upload","3":"Initial upload","package":"plexer.tar.gz","4":"plexer.tar.gz","src_id":"15422","5":"15422","creation_date":"1302399856","6":"1302399856"}]},"3548":{"script_id":"3548","0":"3548","script_name":"Dagon","1":"Dagon","script_type":"color scheme","2":"color scheme","summary":"A dark and easy to read color scheme","3":"A dark and easy to read color scheme","description":"take a look at the screenshot...\r\n\r\nhttp:\/\/img69.imageshack.us\/i\/dagon.png\/","4":"take a look at the screenshot...\r\n\r\nhttp:\/\/img69.imageshack.us\/i\/dagon.png\/","install_details":"","5":"","first_name":"Dee Sub Wun","6":"Dee Sub Wun","last_name":".","7":".","releases":[{"0":"3548","vim_version":"7.0","1":"7.0","script_version":"1.1","2":"1.1","version_comment":"Fixed `Tabline' colors","3":"Fixed `Tabline' colors","package":"dagon.vim","4":"dagon.vim","src_id":"15425","5":"15425","creation_date":"1302465408","6":"1302465408"},{"0":"3548","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"dagon.vim","4":"dagon.vim","src_id":"15421","5":"15421","creation_date":"1302397761","6":"1302397761"}]},"3547":{"script_id":"3547","0":"3547","script_name":"jianfan","1":"jianfan","script_type":"ftplugin","2":"ftplugin","summary":"transcoding Simplified and Traditional","3":"transcoding Simplified and Traditional","description":"convert simplified to traditional or convert traditional to simplified.\r\n简体和繁体的互相转换。\r\n\r\nChinese users need it.\r\n中国人用得着。\r\n\r\nI do not understand English, sorry。","4":"convert simplified to traditional or convert traditional to simplified.\r\n简体和繁体的互相转换。\r\n\r\nChinese users need it.\r\n中国人用得着。\r\n\r\nI do not understand English, sorry。","install_details":"Copy jianfan.vim to your plugin directory. \r\nadd this code to your vimrc:\r\nnmap <leader>g2b <ESC>:cal G2B()<CR>\r\nnmap <leader>b2g <ESC>:cal B2G()<CR>\r\n\r\n复制 jianfan.vim 到你的插件文件夹下。\r\n添加下面的代码到你的vimrc:\r\nnmap <leader>g2b <ESC>:cal G2B()<CR>\r\nnmap <leader>b2g <ESC>:cal B2G()<CR>\r\n","5":"Copy jianfan.vim to your plugin directory. \r\nadd this code to your vimrc:\r\nnmap <leader>g2b <ESC>:cal G2B()<CR>\r\nnmap <leader>b2g <ESC>:cal B2G()<CR>\r\n\r\n复制 jianfan.vim 到你的插件文件夹下。\r\n添加下面的代码到你的vimrc:\r\nnmap <leader>g2b <ESC>:cal G2B()<CR>\r\nnmap <leader>b2g <ESC>:cal B2G()<CR>\r\n","first_name":"peter","6":"peter","last_name":"chan","7":"chan","releases":[{"0":"3547","vim_version":"7.0","1":"7.0","script_version":"1.3","2":"1.3","version_comment":"modified by Solcan\r\n\r\nThus I modified your script for working with selected lines.\r\nPlease find attached the modified version.\r\nThere are some explanations in Chinese in the modified script.\r\nI hope they make some sense.\r\n\r\nHow I use the modified version?\r\nFor example I input two lines of Chinese text:\r\n礼尚往来\r\n礼尚往来\r\nThen I use, in normal mode, Shift+v to select the second line.\r\nI press Ctrl+t and the text becomes:\r\n礼尚往来\r\n禮尚往來","3":"modified by Solcan\r\n\r\nThus I modified your script for working with selected lines.\r\nPlease find attached the modified version.\r\nThere are some explanations in Chinese in the modified script.\r\nI hope they make some sense.\r\n\r\nHow I use the modified version?\r\nFor example I input two lines of Chinese text:\r\n礼尚往来\r\n礼尚往来\r\nThen I use, in normal mode, Shift+v to select the second line.\r\nI press Ctrl+t and the text becomes:\r\n礼尚往来\r\n禮尚往來","package":"jianfan-v.vim","4":"jianfan-v.vim","src_id":"16116","5":"16116","creation_date":"1311199825","6":"1311199825"},{"0":"3547","vim_version":"7.0","1":"7.0","script_version":"1.2","2":"1.2","version_comment":"modified by Solcan \r\n\r\nThus I modified your script for working with selected lines.\r\nPlease find attached the modified version.\r\nThere are some explanations in Chinese in the modified script.\r\nI hope they make some sense.\r\n\r\nHow I use the modified version?\r\nFor example I input two lines of Chinese text:\r\n礼尚往来\r\n礼尚往来\r\nThen I use, in normal mode, Shift+v to select the second line.\r\nI press Ctrl+t and the text becomes:\r\n礼尚往来\r\n禮尚往來\r\n","3":"modified by Solcan \r\n\r\nThus I modified your script for working with selected lines.\r\nPlease find attached the modified version.\r\nThere are some explanations in Chinese in the modified script.\r\nI hope they make some sense.\r\n\r\nHow I use the modified version?\r\nFor example I input two lines of Chinese text:\r\n礼尚往来\r\n礼尚往来\r\nThen I use, in normal mode, Shift+v to select the second line.\r\nI press Ctrl+t and the text becomes:\r\n礼尚往来\r\n禮尚往來\r\n","package":"jianfan-v.vim","4":"jianfan-v.vim","src_id":"16115","5":"16115","creation_date":"1311199701","6":"1311199701"},{"0":"3547","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"modified by Solcan \r\n\r\nThus I modified your script for working with selected lines.\r\nPlease find attached the modified version.\r\nThere are some explanations in Chinese in the modified script.\r\nI hope they make some sense.\r\n\r\nHow I use the modified version?\r\nFor example I input two lines of Chinese text:\r\n礼尚往来\r\n礼尚往来\r\nThen I use, in normal mode, Shift+v to select the second line.\r\nI press Ctrl+t and the text becomes:\r\n礼尚往来\r\n禮尚往來\r\n","3":"modified by Solcan \r\n\r\nThus I modified your script for working with selected lines.\r\nPlease find attached the modified version.\r\nThere are some explanations in Chinese in the modified script.\r\nI hope they make some sense.\r\n\r\nHow I use the modified version?\r\nFor example I input two lines of Chinese text:\r\n礼尚往来\r\n礼尚往来\r\nThen I use, in normal mode, Shift+v to select the second line.\r\nI press Ctrl+t and the text becomes:\r\n礼尚往来\r\n禮尚往來\r\n","package":"jianfan-v.vim","4":"jianfan-v.vim","src_id":"16114","5":"16114","creation_date":"1311199678","6":"1311199678"},{"0":"3547","vim_version":"7.0","1":"7.0","script_version":"1.1","2":"1.1","version_comment":"set fileformat=unix\r\n","3":"set fileformat=unix\r\n","package":"jianfan.vim","4":"jianfan.vim","src_id":"15433","5":"15433","creation_date":"1302569209","6":"1302569209"},{"0":"3547","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"jianfan.vim","4":"jianfan.vim","src_id":"15416","5":"15416","creation_date":"1302313977","6":"1302313977"}]},"3546":{"script_id":"3546","0":"3546","script_name":"molly.vim","1":"molly.vim","script_type":"utility","2":"utility","summary":"ZOMG! Very fast and sexy textmate-like command-t plugin.","3":"ZOMG! Very fast and sexy textmate-like command-t plugin.","description":"ZOMG! Very fast and sexy textmate-like command-t plugin. \r\n\r\nIt also works for regular vim.\r\n\r\nGet the source:\r\nhttps:\/\/github.com\/westoque\/molly.vim","4":"ZOMG! Very fast and sexy textmate-like command-t plugin. \r\n\r\nIt also works for regular vim.\r\n\r\nGet the source:\r\nhttps:\/\/github.com\/westoque\/molly.vim","install_details":"Extract. Copy molly.vim to ~\/.vim\/plugin\/","5":"Extract. Copy molly.vim to ~\/.vim\/plugin\/","first_name":"William","6":"William","last_name":"Estoque","7":"Estoque","releases":[{"0":"3546","vim_version":"7.0","1":"7.0","script_version":"0.0.4","2":"0.0.4","version_comment":"Made molly buffer opening faster. Can now open in a new tab.","3":"Made molly buffer opening faster. Can now open in a new tab.","package":"molly.tar.gz","4":"molly.tar.gz","src_id":"15677","5":"15677","creation_date":"1305824481","6":"1305824481"},{"0":"3546","vim_version":"7.0","1":"7.0","script_version":"0.0.3","2":"0.0.3","version_comment":"No need to call RefreshFileList.","3":"No need to call RefreshFileList.","package":"molly.tar.gz","4":"molly.tar.gz","src_id":"15414","5":"15414","creation_date":"1302279098","6":"1302279098"},{"0":"3546","vim_version":"7.0","1":"7.0","script_version":"0.0.2","2":"0.0.2","version_comment":"Initial upload","3":"Initial upload","package":"molly.tar.gz","4":"molly.tar.gz","src_id":"15412","5":"15412","creation_date":"1302235353","6":"1302235353"}]},"3545":{"script_id":"3545","0":"3545","script_name":"Google Translate ","1":"Google Translate ","script_type":"utility","2":"utility","summary":"Google Translate for Vim","3":"Google Translate for Vim","description":"Example of using: \r\n\r\n:Translate Hello World","4":"Example of using: \r\n\r\n:Translate Hello World","install_details":"Dependencies: \r\nRuby and Rubygems;\r\n\r\nsudo gem install google-translate;\r\n\r\nPut plugin in Vim plugin directory (.vim\/plugin) \r\n\r\nAdd in your .vimrc, string (For translation to Russian)\r\n let g:langpair=\"ru\" \r\n\r\nAlso, you can use translator in visual-mode for code blocks. Just put shortcut for a key bind\r\n let g:vtranslate=\"T\"\r\nNow you can select the text, and by pressing Shift-T Google Translate will process the block.\r\nIf you wish, you can change the color results by using of command :echohl","5":"Dependencies: \r\nRuby and Rubygems;\r\n\r\nsudo gem install google-translate;\r\n\r\nPut plugin in Vim plugin directory (.vim\/plugin) \r\n\r\nAdd in your .vimrc, string (For translation to Russian)\r\n let g:langpair=\"ru\" \r\n\r\nAlso, you can use translator in visual-mode for code blocks. Just put shortcut for a key bind\r\n let g:vtranslate=\"T\"\r\nNow you can select the text, and by pressing Shift-T Google Translate will process the block.\r\nIf you wish, you can change the color results by using of command :echohl","first_name":"Slava","6":"Slava","last_name":"Rudy","7":"Rudy","releases":[{"0":"3545","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"gtranslate.vim","4":"gtranslate.vim","src_id":"15411","5":"15411","creation_date":"1302228178","6":"1302228178"}]},"3544":{"script_id":"3544","0":"3544","script_name":"cascading.vim","1":"cascading.vim","script_type":"utility","2":"utility","summary":"Cascading indenter","3":"Cascading indenter","description":"A simple cascading indenter.\r\n\r\n\r\nCascading auto-break:\r\n\r\n$var->foo->bar->short()->very_long_long_long( )->very_long_long_long_long( )\r\n\r\nPress -- to convert line into\r\n\r\n$var->foo->bar\r\n    ->short()\r\n    ->very_long_long_long( )\r\n    ->very_long_long_long_long( )\r\n\r\n\r\nSupported File Types\r\n\r\nphp\r\nperl\r\nruby","4":"A simple cascading indenter.\r\n\r\n\r\nCascading auto-break:\r\n\r\n$var->foo->bar->short()->very_long_long_long( )->very_long_long_long_long( )\r\n\r\nPress -- to convert line into\r\n\r\n$var->foo->bar\r\n    ->short()\r\n    ->very_long_long_long( )\r\n    ->very_long_long_long_long( )\r\n\r\n\r\nSupported File Types\r\n\r\nphp\r\nperl\r\nruby","install_details":"copy into your ~\/.vim\/plugin\/","5":"copy into your ~\/.vim\/plugin\/","first_name":"Yo-An","6":"Yo-An","last_name":"Lin","7":"Lin","releases":[{"0":"3544","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"cascading.vim-0.1.vba","4":"cascading.vim-0.1.vba","src_id":"15407","5":"15407","creation_date":"1302164074","6":"1302164074"}]},"3543":{"script_id":"3543","0":"3543","script_name":"opener.vim","1":"opener.vim","script_type":"utility","2":"utility","summary":"Open files and URLs in the appropriate viewer","3":"Open files and URLs in the appropriate viewer","description":"The opener plugin allows you to open files, URLs, or anything recognizable to your system in the appropriate viewer.\r\n\r\nCOMMANDS\r\n\r\n:Opener [location]\r\n\r\nOpen the location with the appropriate handler. If location is not given, use whatever is visually selected. Multiple lines can be selected.\r\n\r\nMAPPINGS\r\n\r\ngO\r\n\r\nInvoke :OpenLocation with the visually selected text, or the value of <cfile>, if no text is selected.","4":"The opener plugin allows you to open files, URLs, or anything recognizable to your system in the appropriate viewer.\r\n\r\nCOMMANDS\r\n\r\n:Opener [location]\r\n\r\nOpen the location with the appropriate handler. If location is not given, use whatever is visually selected. Multiple lines can be selected.\r\n\r\nMAPPINGS\r\n\r\ngO\r\n\r\nInvoke :OpenLocation with the visually selected text, or the value of <cfile>, if no text is selected.","install_details":"Extract to ~\/.vim","5":"Extract to ~\/.vim","first_name":"Jeremy","6":"Jeremy","last_name":"Cantrell","7":"Cantrell","releases":[{"0":"3543","vim_version":"7.0","1":"7.0","script_version":"0.1.1","2":"0.1.1","version_comment":"Fix variable name","3":"Fix variable name","package":"jmcantrell-vim-opener-42d94bc.zip","4":"jmcantrell-vim-opener-42d94bc.zip","src_id":"15516","5":"15516","creation_date":"1303679012","6":"1303679012"},{"0":"3543","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"jmcantrell-vim-opener-1b7e3a9.zip","4":"jmcantrell-vim-opener-1b7e3a9.zip","src_id":"15405","5":"15405","creation_date":"1302155238","6":"1302155238"}]},"3542":{"script_id":"3542","0":"3542","script_name":"Sesiones.vim","1":"Sesiones.vim","script_type":"utility","2":"utility","summary":"Plugin for managing sesions the easy way","3":"Plugin for managing sesions the easy way","description":"Small function to save, load, overwrite and delete vim sessions.\r\n:mkview and related commands are not difficult to manage but where to save the sessions and  with what name is sometimes tricky.\r\n\r\nThis plugin use a dedicate folder ($VIM\/vimfiles\/session\/) to save all sessions, using as name the full path-name to the associated file. This way you don't have to worry about where have you saved your sesion; just you only have to remember what file is associated to the session, open it and press <Shift-F3>\r\nThe functions can be accessed both in the \"plugin -> Sessions\" tab or with the keyboard.\r\n\r\nUsage\r\n---------\r\nManage it from the menu in plugins or with the keyboard:\r\n<F3> to save a session\r\n<Shift-F3> to load a session\r\n<Crtl-Shift-F3> to overwrite an existing session\r\nd<F3> to delete an existing session","4":"Small function to save, load, overwrite and delete vim sessions.\r\n:mkview and related commands are not difficult to manage but where to save the sessions and  with what name is sometimes tricky.\r\n\r\nThis plugin use a dedicate folder ($VIM\/vimfiles\/session\/) to save all sessions, using as name the full path-name to the associated file. This way you don't have to worry about where have you saved your sesion; just you only have to remember what file is associated to the session, open it and press <Shift-F3>\r\nThe functions can be accessed both in the \"plugin -> Sessions\" tab or with the keyboard.\r\n\r\nUsage\r\n---------\r\nManage it from the menu in plugins or with the keyboard:\r\n<F3> to save a session\r\n<Shift-F3> to load a session\r\n<Crtl-Shift-F3> to overwrite an existing session\r\nd<F3> to delete an existing session","install_details":"Copy the Sesiones.vim script to the $HOME\/.vim\/plugin or the $HOME\/vimfiles\/plugin or the $VIM\/vimfiles directory.\r\nRefer to the ':help add-plugin', ':help add-global-plugin' and ':help runtimepath' topics for more details about Vim plugins.\r\n\r\nFor those guys who use pathogen, the installation should be as simple as a git clone: \r\n\r\n$ cd ~\/.vim\/bundle \r\n$ git clone git:\/\/github.com\/jmpicaza\/Sesiones.vim.git\r\n\r\nConfiguration\r\n-------------------\r\nIn .vimrc or _vimrc, add the lines:\r\n\t\"Sesiones Plugin\r\n\t\"let g:sesiones_path=\"C:\\Documents and Settiing\\yourUserName\\someFolder\"\r\nIf not, the default loaction will be \"~\/.vimSessions\" or \"$VIM\\_vimSessions\" or \"$USERPROFILE\\_vimSessions\" depending of the operating system and rw permissions.","5":"Copy the Sesiones.vim script to the $HOME\/.vim\/plugin or the $HOME\/vimfiles\/plugin or the $VIM\/vimfiles directory.\r\nRefer to the ':help add-plugin', ':help add-global-plugin' and ':help runtimepath' topics for more details about Vim plugins.\r\n\r\nFor those guys who use pathogen, the installation should be as simple as a git clone: \r\n\r\n$ cd ~\/.vim\/bundle \r\n$ git clone git:\/\/github.com\/jmpicaza\/Sesiones.vim.git\r\n\r\nConfiguration\r\n-------------------\r\nIn .vimrc or _vimrc, add the lines:\r\n\t\"Sesiones Plugin\r\n\t\"let g:sesiones_path=\"C:\\Documents and Settiing\\yourUserName\\someFolder\"\r\nIf not, the default loaction will be \"~\/.vimSessions\" or \"$VIM\\_vimSessions\" or \"$USERPROFILE\\_vimSessions\" depending of the operating system and rw permissions.","first_name":"J. Manuel","6":"J. Manuel","last_name":"Picaza","7":"Picaza","releases":[{"0":"3542","vim_version":"7.0","1":"7.0","script_version":"0.2","2":"0.2","version_comment":"Now you can choose what folder to use for keepeng the sessions!","3":"Now you can choose what folder to use for keepeng the sessions!","package":"Sesiones.vim","4":"Sesiones.vim","src_id":"15443","5":"15443","creation_date":"1302696823","6":"1302696823"},{"0":"3542","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"Sesiones.vim","4":"Sesiones.vim","src_id":"15398","5":"15398","creation_date":"1302075269","6":"1302075269"}]},"3541":{"script_id":"3541","0":"3541","script_name":"fatrat.vim","1":"fatrat.vim","script_type":"utility","2":"utility","summary":"Work with all runtime files for a filetype","3":"Work with all runtime files for a filetype","description":"The fatrat plugin provides ways to work with all the runtime files for a particular filetype.","4":"The fatrat plugin provides ways to work with all the runtime files for a particular filetype.","install_details":"Extract to ~\/.vim","5":"Extract to ~\/.vim","first_name":"Jeremy","6":"Jeremy","last_name":"Cantrell","7":"Cantrell","releases":[{"0":"3541","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"jmcantrell-vim-fatrat-dfc9552.zip","4":"jmcantrell-vim-fatrat-dfc9552.zip","src_id":"15396","5":"15396","creation_date":"1302060909","6":"1302060909"}]},"3540":{"script_id":"3540","0":"3540","script_name":"Save Current Font","1":"Save Current Font","script_type":"utility","2":"utility","summary":"Add your current font setting to your gvimrc.","3":"Add your current font setting to your gvimrc.","description":"SaveCurrentFont\r\n  Adds the current font settings to your gvimrc\r\n\r\nIt's a pain to remember the names of fonts when adding them to your config,\r\nso this function automates that process by using the current font settings.\r\n\r\nJust call SaveCurrentFont() to save the current font.\r\n\r\n\r\n\r\nPlease report bugs to https:\/\/github.com\/pydave\/daveconfig\/issues\r\n","4":"SaveCurrentFont\r\n  Adds the current font settings to your gvimrc\r\n\r\nIt's a pain to remember the names of fonts when adding them to your config,\r\nso this function automates that process by using the current font settings.\r\n\r\nJust call SaveCurrentFont() to save the current font.\r\n\r\n\r\n\r\nPlease report bugs to https:\/\/github.com\/pydave\/daveconfig\/issues\r\n","install_details":"Copy to your .vim\/plugin directory","5":"Copy to your .vim\/plugin directory","first_name":"David","6":"David","last_name":"Briscoe","7":"Briscoe","releases":[{"0":"3540","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"save_current_font.vim","4":"save_current_font.vim","src_id":"15390","5":"15390","creation_date":"1302036662","6":"1302036662"}]},"3539":{"script_id":"3539","0":"3539","script_name":"rvmprompt.vim","1":"rvmprompt.vim","script_type":"utility","2":"utility","summary":"A simple interface for rvm-prompt command","3":"A simple interface for rvm-prompt command","description":"rvmprompt.vim is a plugin that provides a simple interface to thr rvm-prompt\r\ncommand. So, you can use that function in your statusline. It provides a configuration variable used to pass tokens to the rvm-prompt command-","4":"rvmprompt.vim is a plugin that provides a simple interface to thr rvm-prompt\r\ncommand. So, you can use that function in your statusline. It provides a configuration variable used to pass tokens to the rvm-prompt command-","install_details":"unzip it.","5":"unzip it.","first_name":"Luca","6":"Luca","last_name":"Pette","7":"Pette","releases":[{"0":"3539","vim_version":"7.0","1":"7.0","script_version":"0.0.1","2":"0.0.1","version_comment":"Initial upload","3":"Initial upload","package":"rvm-prompt.zip","4":"rvm-prompt.zip","src_id":"15371","5":"15371","creation_date":"1301853657","6":"1301853657"}]},"3538":{"script_id":"3538","0":"3538","script_name":"plantuml-syntax","1":"plantuml-syntax","script_type":"syntax","2":"syntax","summary":"Syntax file for plantuml","3":"Syntax file for plantuml","description":"Syntax file for plantuml.  Can also be found at github, \r\nhere: https:\/\/github.com\/aklt\/plantuml-syntax\r\n\r\nHave fun!","4":"Syntax file for plantuml.  Can also be found at github, \r\nhere: https:\/\/github.com\/aklt\/plantuml-syntax\r\n\r\nHave fun!","install_details":"copy to $HOME\/.vim\/syntax","5":"copy to $HOME\/.vim\/syntax","first_name":"Anders","6":"Anders","last_name":"Th\u00c3\u00b8gersen","7":"Th\u00c3\u00b8gersen","releases":[{"0":"3538","vim_version":"7.0","1":"7.0","script_version":"0.2.0","2":"0.2.0","version_comment":"Lots of changes: Much better syntax highlighting, includes indentation, ftdetect and matchit support + many fixes by talented contributors.","3":"Lots of changes: Much better syntax highlighting, includes indentation, ftdetect and matchit support + many fixes by talented contributors.","package":"plantuml-syntax.zip","4":"plantuml-syntax.zip","src_id":"26506","5":"26506","creation_date":"1559389243","6":"1559389243"},{"0":"3538","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"plantuml.vim","4":"plantuml.vim","src_id":"15365","5":"15365","creation_date":"1301807390","6":"1301807390"}]},"3537":{"script_id":"3537","0":"3537","script_name":"XPath Search","1":"XPath Search","script_type":"utility","2":"utility","summary":"Allows XPath searches to be performed on XML files","3":"Allows XPath searches to be performed on XML files","description":"-Defines a new command, :XPathSearchPrompt that begins XPath search mode.\r\n-Start typing your XPath and see the results pop up in vim's location list as you type\r\n\r\nAlso see github: https:\/\/github.com\/actionshrimp\/vim-xpath","4":"-Defines a new command, :XPathSearchPrompt that begins XPath search mode.\r\n-Start typing your XPath and see the results pop up in vim's location list as you type\r\n\r\nAlso see github: https:\/\/github.com\/actionshrimp\/vim-xpath","install_details":"Requires:\r\n-Python installed and support enabled on vim (look for +python under :version)\r\n-python-lxml library installed (http:\/\/lxml.de)","5":"Requires:\r\n-Python installed and support enabled on vim (look for +python under :version)\r\n-python-lxml library installed (http:\/\/lxml.de)","first_name":"Dave","6":"Dave","last_name":"Aitken","7":"Aitken","releases":[{"0":"3537","vim_version":"7.0","1":"7.0","script_version":"2.0.0","2":"2.0.0","version_comment":"Rewrite. Uses location list instead of custom results buffer. Better handling of long XML files, and XML namespaces","3":"Rewrite. Uses location list instead of custom results buffer. Better handling of long XML files, and XML namespaces","package":"vim-xpath-v2.0.0.zip","4":"vim-xpath-v2.0.0.zip","src_id":"20714","5":"20714","creation_date":"1377518782","6":"1377518782"},{"0":"3537","vim_version":"7.0","1":"7.0","script_version":"1.20","2":"1.20","version_comment":"Removed default forced keybinding, added easier command.\r\nGeneral bugfixes.\r\nNow evaluates expressions that aren't associated with a particular line.","3":"Removed default forced keybinding, added easier command.\r\nGeneral bugfixes.\r\nNow evaluates expressions that aren't associated with a particular line.","package":"actionshrimp-vim-xpath-26a7cb7.zip","4":"actionshrimp-vim-xpath-26a7cb7.zip","src_id":"15936","5":"15936","creation_date":"1308510516","6":"1308510516"},{"0":"3537","vim_version":"7.0","1":"7.0","script_version":"1.10","2":"1.10","version_comment":"Updated to handle unnamed buffers and to search on the last searched buffer if the current window is the results window.","3":"Updated to handle unnamed buffers and to search on the last searched buffer if the current window is the results window.","package":"xpath.vba","4":"xpath.vba","src_id":"15394","5":"15394","creation_date":"1302048464","6":"1302048464"},{"0":"3537","vim_version":"7.0","1":"7.0","script_version":"1.05","2":"1.05","version_comment":"Fixed minor bugs and encoding issues.","3":"Fixed minor bugs and encoding issues.","package":"xpath.vba","4":"xpath.vba","src_id":"15381","5":"15381","creation_date":"1301956022","6":"1301956022"},{"0":"3537","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"xpath.vba","4":"xpath.vba","src_id":"15364","5":"15364","creation_date":"1301789744","6":"1301789744"}]},"3536":{"script_id":"3536","0":"3536","script_name":"Tab Manager","1":"Tab Manager","script_type":"utility","2":"utility","summary":"Rearranges buffers into tabs","3":"Rearranges buffers into tabs","description":"Sorts and rearranges all open buffers across tabs based on built-in or user-specified criteria.\r\n\r\nConfiguration: The variable g:TabManager_maxFilesInTab (defaults to 5) is used to determine how many buffers to open in each tab.\r\n\r\nGeneral usage:\r\n\r\nAll of these commands optionally take a number which determines how many buffers to open per tab (new tabs get created as necessary); 0 means to lump all\r\nbuffers of any given typeinto one tab.\r\n\r\nFor the following examples, assume these buffers are open (doesn't matter how many tabs they currently take):\r\n\r\n\/progs\/com\/test\/Abcd.java\r\n\/progs\/com\/test\/ProgramRunner.java\r\n\/progs\/com\/abc\/Test.java\r\n\/vim\/plugin\/TabManager.vim\r\n\r\nRearrangetabsbyfirstletter: Quick alphabetization of buffers where all buffers with the same starting letter are put together. Only the file name is\r\nconsidered, not the path. So, at the end, you get three tabs:\r\n\r\nTab 1: Abcd.java\r\nTab 2: ProgramRunner.java\r\nTab 3: TabManager.vim and Test.java\r\n\r\n(The tabs are sorted as are the results within each tab.)\r\n\r\nRearrangetabsbyextension: Arranges by extension (.java or .vim, for example):\r\n\r\nTab 1: Abcd.java, ProgramRunner.java and Test.java\r\nTab 2: TabManager.vim\r\n\r\nRearrangetabsbypath: Arranges by absolute file path (not taking filename into consideration):\r\n\r\nTab 1: \/progs\/com\/abc: Test.java\r\nTab 2: \/progs\/com\/test: Abcd.java and ProgramRunner.java\r\nTab 3: \/vim\/plugin: TabManager.vim\r\n\r\nTiletabs: Quick way to alphabetize the list of buffers (case sensitive) into regularly-sized (by number of buffers) tabs. Doesn't make sense to use this with\r\n0 (all buffers in one tab), unless that's the effect you want.\r\n\r\nRearrangetabs: The workhorse. All other other commands are defined through this. Takes the actual pattern criteria against which to match each buffer.\r\n\r\nVersion 1.1:\r\n\r\nAdded two new commands:\r\n\r\nRearrangetabsbytype: If it's a Java file, returns the last word that's not a part of the extension. For example, CopyAction.java returns Action and\r\nCopyForm.java returns Form. This should probably be reworked to allow the setting of the extension upon which to filter or to not look at extensions at all.\r\n\r\nRearrangetabsbyroot: Groups files with similarly named roots together. For example, CopyAction.java, CopyForm.java and CopyResults.jsp will end up together\r\nbecause they all have \"Copy\" as the root.\r\n\r\nVersion 1.2:\r\n\r\nNew variable: g:TabManager_fileTypeExtension (defaults to \"java\") to use when determining the Rearrangetabsbytype; can be passed to the command on the\r\ncommand-line as an override.\r\n\r\nRearrangetabsbytype now takes an extension (other than the default \"java\" or g:TabManager_fileTypeExtension) to use when sorting the files. If only one\r\nparameter is passed, it may be either a number or the extension. If both are specified, the number must be first.\r\n\r\nVersion 1.3:\r\n\r\nRearrangetabsbyfirstletter renamed to Rearrangetabsbyfirstletters: If called with no parameters, considers the first character of the file name, as before. If\r\ncalled with one parameter, the specified number of characters is considered. For example, with no parameters, \"Test.java\" and \"Touring.java\" would be placed\r\ntogether because both start with a T. With 2 as the parameter value, they would be separated (\"Te\" vs. \"To\").\r\n\r\nIf called with 2 parameters, the first parameter is the number of windows to place in one tab, as always (0 meaning to throw them all together).\r\n\r\nVersion 1.35:\r\n\r\nTakes 'ignorecase' into consideration for matching extensions, first letters and complete file paths (but not for matching roots and \"types\").\r\n\r\nVersion 1.4:\r\n\r\nAdded new command:\r\n\r\nMovetotab: moves the current file to the specified tab; understands absolute numbers (1 for the first tab, for example) as well as:\r\n\r\n- n: next tab\r\n- p: previous tab\r\n- $: last tab\r\n\r\nVersion 1.45:\r\n\r\nAdded new command:\r\n\r\nCopytotab: copies the current file to the specified tab (just like Movetotab except that the original tab also contains the file).\r\n\r\nVersion 1.5:\r\n\r\nAdded the ability to set custom \"keys\" to be used when rearranging files into tabs. For example, given the following list of files:\r\n\r\n\/progs\/com\/test\/Abcd.java\r\n\/progs\/com\/test\/ProgramRunner.java\r\n\/progs\/com\/abc\/Test.java\r\n\/vim\/plugin\/TabManager.vim\r\n\/webFiles\/root\/test.html\r\n\/webFiles\/root\/css\/styles.css\r\n\r\nThe default behaviour, when arranging by path, extension or first letters, is to always place test.html and styles.css in separate tabs. (Unless calling\r\nTiletabs, which just tiles all windows blindly.) However, if both these files have a manually set key of, say, \"web\", then any other criteria will be ignored\r\nand these two files will always be placed together because they have the same key. This allows grouping some windows by functionality while continuing to\r\ngroup others by whatever rearrange command is actually called.\r\n\r\nOf course, different sets of windows may have different keys and they will all be grouped together accordingly.\r\n\r\nAll of the standard Rearrange* commands now take an optional bang (!)--for example, Rearrangetabsbyextension!--that will, for just this rearrangement, IGNORE\r\nany local keys and treat all windows as if there were no keys.\r\n\r\nIf you have multiple windows where you're editing the same buffer, they will almost always end up together after any rearrangement (unless they are split\r\nacross tabs that become full). You can avoid this by setting different window-level local keys for the buffers.\r\n\r\nAdded four new commands--the set and remove key commands can be combined with windo and tabdo to set or remove the same key for more than one window at a time:\r\n\r\nSettabmanagerwindowkey <key>: Sets the window-level local key for the current window to <key>.\r\n\r\nSettabmanagerbufferkey <key>: Sets the buffer-level local key for the current buffer to <key>.\r\n\r\nRemovetabmanagerkey: Removes the currently set key for the current window; will remove BOTH buffer and window level keys. (Doesn't take any arguments.)\r\n\r\nRedorearrangetabs: Redoes the last tab rearrangement command (by extension, simple tiling, by first letters, etc.). Useful for incorporating new windows into\r\nthe currenty \"scheme\". If local keys have changed, the layout may end up being different. If new windows have been added, the layout may be different, also,\r\nbut that may be what you want. By default, it obeys local keys (even if the last command was called with a bang and did not). Accepts a bang (!) to ignore\r\nlocal keys.\r\n\r\nIf you call this before you've run any actual rearrangement commands, you will most likely (deservedly) get an error.\r\n\r\nVersion 1.55:\r\n\r\nRearrangetabsbypath now also takes a second parameter which determines how many components from the path to consider. For example, given the following set of\r\nfiles:\r\n\r\n\/progs\/com\/test\/Abcd.java\r\n\/progs\/com\/test\/ProgramRunner.java\r\n\/progs\/com\/abc\/Test.java\r\n\r\nThe default behaviour would be to create two tabs, one with Abcd.java and ProgramRunner.java; and the other with Test.java. However, if called with a\r\nparameter of 2, it will only consider the first two path components (\/progs\/com) and put all the files in the same tab. A value of 0 (the default) means to\r\ncheck the entire path, as before. New command format:\r\n\r\nRearrangetabsbypath [number of files per tab] [number of path components to consider]\r\nOr\r\nRearrangetabsbypath [number of path components to consider]\r\n\r\n\r\nVersion 1.6\r\n\r\nAdded a new command:\r\n\r\nRearrangetabsbypackage: Works just like Rearrangetabsbypath, except uses the package the files are in. Only useful for files that specify a package in this format:\r\n\r\npackage some.package.name;\r\n\r\n(The semicolon is optional.) Files that don't have a package will fall back to the entire file path (no path component specification; the ENTIRE path will be considered.)\r\n\r\nTakes either one or two arguments:\r\n\r\nRearrangetabsbypackage [number of files per tab] [number of path components to consider]\r\nOr\r\nRearrangetabsbypackage [number of path components to consider]\r\n","4":"Sorts and rearranges all open buffers across tabs based on built-in or user-specified criteria.\r\n\r\nConfiguration: The variable g:TabManager_maxFilesInTab (defaults to 5) is used to determine how many buffers to open in each tab.\r\n\r\nGeneral usage:\r\n\r\nAll of these commands optionally take a number which determines how many buffers to open per tab (new tabs get created as necessary); 0 means to lump all\r\nbuffers of any given typeinto one tab.\r\n\r\nFor the following examples, assume these buffers are open (doesn't matter how many tabs they currently take):\r\n\r\n\/progs\/com\/test\/Abcd.java\r\n\/progs\/com\/test\/ProgramRunner.java\r\n\/progs\/com\/abc\/Test.java\r\n\/vim\/plugin\/TabManager.vim\r\n\r\nRearrangetabsbyfirstletter: Quick alphabetization of buffers where all buffers with the same starting letter are put together. Only the file name is\r\nconsidered, not the path. So, at the end, you get three tabs:\r\n\r\nTab 1: Abcd.java\r\nTab 2: ProgramRunner.java\r\nTab 3: TabManager.vim and Test.java\r\n\r\n(The tabs are sorted as are the results within each tab.)\r\n\r\nRearrangetabsbyextension: Arranges by extension (.java or .vim, for example):\r\n\r\nTab 1: Abcd.java, ProgramRunner.java and Test.java\r\nTab 2: TabManager.vim\r\n\r\nRearrangetabsbypath: Arranges by absolute file path (not taking filename into consideration):\r\n\r\nTab 1: \/progs\/com\/abc: Test.java\r\nTab 2: \/progs\/com\/test: Abcd.java and ProgramRunner.java\r\nTab 3: \/vim\/plugin: TabManager.vim\r\n\r\nTiletabs: Quick way to alphabetize the list of buffers (case sensitive) into regularly-sized (by number of buffers) tabs. Doesn't make sense to use this with\r\n0 (all buffers in one tab), unless that's the effect you want.\r\n\r\nRearrangetabs: The workhorse. All other other commands are defined through this. Takes the actual pattern criteria against which to match each buffer.\r\n\r\nVersion 1.1:\r\n\r\nAdded two new commands:\r\n\r\nRearrangetabsbytype: If it's a Java file, returns the last word that's not a part of the extension. For example, CopyAction.java returns Action and\r\nCopyForm.java returns Form. This should probably be reworked to allow the setting of the extension upon which to filter or to not look at extensions at all.\r\n\r\nRearrangetabsbyroot: Groups files with similarly named roots together. For example, CopyAction.java, CopyForm.java and CopyResults.jsp will end up together\r\nbecause they all have \"Copy\" as the root.\r\n\r\nVersion 1.2:\r\n\r\nNew variable: g:TabManager_fileTypeExtension (defaults to \"java\") to use when determining the Rearrangetabsbytype; can be passed to the command on the\r\ncommand-line as an override.\r\n\r\nRearrangetabsbytype now takes an extension (other than the default \"java\" or g:TabManager_fileTypeExtension) to use when sorting the files. If only one\r\nparameter is passed, it may be either a number or the extension. If both are specified, the number must be first.\r\n\r\nVersion 1.3:\r\n\r\nRearrangetabsbyfirstletter renamed to Rearrangetabsbyfirstletters: If called with no parameters, considers the first character of the file name, as before. If\r\ncalled with one parameter, the specified number of characters is considered. For example, with no parameters, \"Test.java\" and \"Touring.java\" would be placed\r\ntogether because both start with a T. With 2 as the parameter value, they would be separated (\"Te\" vs. \"To\").\r\n\r\nIf called with 2 parameters, the first parameter is the number of windows to place in one tab, as always (0 meaning to throw them all together).\r\n\r\nVersion 1.35:\r\n\r\nTakes 'ignorecase' into consideration for matching extensions, first letters and complete file paths (but not for matching roots and \"types\").\r\n\r\nVersion 1.4:\r\n\r\nAdded new command:\r\n\r\nMovetotab: moves the current file to the specified tab; understands absolute numbers (1 for the first tab, for example) as well as:\r\n\r\n- n: next tab\r\n- p: previous tab\r\n- $: last tab\r\n\r\nVersion 1.45:\r\n\r\nAdded new command:\r\n\r\nCopytotab: copies the current file to the specified tab (just like Movetotab except that the original tab also contains the file).\r\n\r\nVersion 1.5:\r\n\r\nAdded the ability to set custom \"keys\" to be used when rearranging files into tabs. For example, given the following list of files:\r\n\r\n\/progs\/com\/test\/Abcd.java\r\n\/progs\/com\/test\/ProgramRunner.java\r\n\/progs\/com\/abc\/Test.java\r\n\/vim\/plugin\/TabManager.vim\r\n\/webFiles\/root\/test.html\r\n\/webFiles\/root\/css\/styles.css\r\n\r\nThe default behaviour, when arranging by path, extension or first letters, is to always place test.html and styles.css in separate tabs. (Unless calling\r\nTiletabs, which just tiles all windows blindly.) However, if both these files have a manually set key of, say, \"web\", then any other criteria will be ignored\r\nand these two files will always be placed together because they have the same key. This allows grouping some windows by functionality while continuing to\r\ngroup others by whatever rearrange command is actually called.\r\n\r\nOf course, different sets of windows may have different keys and they will all be grouped together accordingly.\r\n\r\nAll of the standard Rearrange* commands now take an optional bang (!)--for example, Rearrangetabsbyextension!--that will, for just this rearrangement, IGNORE\r\nany local keys and treat all windows as if there were no keys.\r\n\r\nIf you have multiple windows where you're editing the same buffer, they will almost always end up together after any rearrangement (unless they are split\r\nacross tabs that become full). You can avoid this by setting different window-level local keys for the buffers.\r\n\r\nAdded four new commands--the set and remove key commands can be combined with windo and tabdo to set or remove the same key for more than one window at a time:\r\n\r\nSettabmanagerwindowkey <key>: Sets the window-level local key for the current window to <key>.\r\n\r\nSettabmanagerbufferkey <key>: Sets the buffer-level local key for the current buffer to <key>.\r\n\r\nRemovetabmanagerkey: Removes the currently set key for the current window; will remove BOTH buffer and window level keys. (Doesn't take any arguments.)\r\n\r\nRedorearrangetabs: Redoes the last tab rearrangement command (by extension, simple tiling, by first letters, etc.). Useful for incorporating new windows into\r\nthe currenty \"scheme\". If local keys have changed, the layout may end up being different. If new windows have been added, the layout may be different, also,\r\nbut that may be what you want. By default, it obeys local keys (even if the last command was called with a bang and did not). Accepts a bang (!) to ignore\r\nlocal keys.\r\n\r\nIf you call this before you've run any actual rearrangement commands, you will most likely (deservedly) get an error.\r\n\r\nVersion 1.55:\r\n\r\nRearrangetabsbypath now also takes a second parameter which determines how many components from the path to consider. For example, given the following set of\r\nfiles:\r\n\r\n\/progs\/com\/test\/Abcd.java\r\n\/progs\/com\/test\/ProgramRunner.java\r\n\/progs\/com\/abc\/Test.java\r\n\r\nThe default behaviour would be to create two tabs, one with Abcd.java and ProgramRunner.java; and the other with Test.java. However, if called with a\r\nparameter of 2, it will only consider the first two path components (\/progs\/com) and put all the files in the same tab. A value of 0 (the default) means to\r\ncheck the entire path, as before. New command format:\r\n\r\nRearrangetabsbypath [number of files per tab] [number of path components to consider]\r\nOr\r\nRearrangetabsbypath [number of path components to consider]\r\n\r\n\r\nVersion 1.6\r\n\r\nAdded a new command:\r\n\r\nRearrangetabsbypackage: Works just like Rearrangetabsbypath, except uses the package the files are in. Only useful for files that specify a package in this format:\r\n\r\npackage some.package.name;\r\n\r\n(The semicolon is optional.) Files that don't have a package will fall back to the entire file path (no path component specification; the ENTIRE path will be considered.)\r\n\r\nTakes either one or two arguments:\r\n\r\nRearrangetabsbypackage [number of files per tab] [number of path components to consider]\r\nOr\r\nRearrangetabsbypackage [number of path components to consider]\r\n","install_details":"Drop into the plugin directory; creates a few commands, but no mappings.","5":"Drop into the plugin directory; creates a few commands, but no mappings.","first_name":"Salman","6":"Salman","last_name":"Halim","7":"Halim","releases":[{"0":"3536","vim_version":"7.0","1":"7.0","script_version":"1.8","2":"1.8","version_comment":"No change in functionality. Just added a proper help file.","3":"No change in functionality. Just added a proper help file.","package":"TabManager.vba","4":"TabManager.vba","src_id":"15601","5":"15601","creation_date":"1304744681","6":"1304744681"},{"0":"3536","vim_version":"7.0","1":"7.0","script_version":"1.7","2":"1.7","version_comment":"No real change; has a dependency upon my GetVar autoload script which I had forgotten to mention before. Sorry if this caused problems.\r\n","3":"No real change; has a dependency upon my GetVar autoload script which I had forgotten to mention before. Sorry if this caused problems.\r\n","package":"TabManager.vim","4":"TabManager.vim","src_id":"15588","5":"15588","creation_date":"1304613976","6":"1304613976"},{"0":"3536","vim_version":"7.0","1":"7.0","script_version":"1.6","2":"1.6","version_comment":"Added a new command: Rearrangetabsbypackage: Works just like Rearrangetabsbypath, except uses the package the files are in. Only useful for files that specify a package (falls back to the entire file path otherwise).","3":"Added a new command: Rearrangetabsbypackage: Works just like Rearrangetabsbypath, except uses the package the files are in. Only useful for files that specify a package (falls back to the entire file path otherwise).","package":"TabManager.vim","4":"TabManager.vim","src_id":"15471","5":"15471","creation_date":"1303136937","6":"1303136937"},{"0":"3536","vim_version":"7.0","1":"7.0","script_version":"1.55","2":"1.55","version_comment":"Rearrangetabsbypath now also takes a second parameter which determines how many components from the path to consider.","3":"Rearrangetabsbypath now also takes a second parameter which determines how many components from the path to consider.","package":"TabManager.vim","4":"TabManager.vim","src_id":"15456","5":"15456","creation_date":"1302921328","6":"1302921328"},{"0":"3536","vim_version":"7.0","1":"7.0","script_version":"1.5","2":"1.5","version_comment":"Added the ability to set custom \"keys\" to be used when rearranging files into tabs. For example, given the following list of files:\r\n\r\n\/progs\/com\/test\/Abcd.java\r\n\/progs\/com\/test\/ProgramRunner.java\r\n\/progs\/com\/abc\/Test.java\r\n\/vim\/plugin\/TabManager.vim\r\n\/webFiles\/root\/test.html\r\n\/webFiles\/root\/css\/styles.css\r\n\r\nThe default behaviour, when arranging by path, extension or first letters, is to always place test.html and styles.css in separate tabs. (Unless calling\r\nTiletabs, which just tiles all windows blindly.) However, if both these files have a manually set key of, say, \"web\", then any other criteria will be ignored\r\nand these two files will always be placed together because they have the same key. This allows grouping some windows by functionality while continuing to\r\ngroup others by whatever rearrange command is actually called.\r\n\r\nOf course, different sets of windows may have different keys and they will all be grouped together accordingly.\r\n\r\nAll of the standard Rearrange* commands now take an optional bang (!)--for example, Rearrangetabsbyextension!--that will, for just this rearrangement, IGNORE\r\nany local keys and treat all windows as if there were no keys.\r\n\r\nIf you have multiple windows where you're editing the same buffer, they will almost always end up together after any rearrangement (unless they are split\r\nacross tabs that become full). You can avoid this by setting different window-level local keys for the buffers.\r\n\r\nAdded four new commands--the set and remove key commands can be combined with windo and tabdo to set or remove the same key for more than one window at a time:\r\n\r\nSettabmanagerwindowkey <key>: Sets the window-level local key for the current window to <key>.\r\n\r\nSettabmanagerbufferkey <key>: Sets the buffer-level local key for the current buffer to <key>.\r\n\r\nRemovetabmanagerkey: Removes the currently set key for the current window; will remove BOTH buffer and window level keys. (Doesn't take any arguments.)\r\n\r\nRedorearrangetabs: Redoes the last tab rearrangement command (by extension, simple tiling, by first letters, etc.). Useful for incorporating new windows into\r\nthe currenty \"scheme\". If local keys have changed, the layout may end up being different. If new windows have been added, the layout may be different, also,\r\nbut that may be what you want. By default, it obeys local keys (even if the last command was called with a bang and did not). Accepts a bang (!) to ignore\r\nlocal keys.\r\n\r\nIf you call this before you've run any actual rearrangement commands, you will most likely (deservedly) get an error.\r\n","3":"Added the ability to set custom \"keys\" to be used when rearranging files into tabs. For example, given the following list of files:\r\n\r\n\/progs\/com\/test\/Abcd.java\r\n\/progs\/com\/test\/ProgramRunner.java\r\n\/progs\/com\/abc\/Test.java\r\n\/vim\/plugin\/TabManager.vim\r\n\/webFiles\/root\/test.html\r\n\/webFiles\/root\/css\/styles.css\r\n\r\nThe default behaviour, when arranging by path, extension or first letters, is to always place test.html and styles.css in separate tabs. (Unless calling\r\nTiletabs, which just tiles all windows blindly.) However, if both these files have a manually set key of, say, \"web\", then any other criteria will be ignored\r\nand these two files will always be placed together because they have the same key. This allows grouping some windows by functionality while continuing to\r\ngroup others by whatever rearrange command is actually called.\r\n\r\nOf course, different sets of windows may have different keys and they will all be grouped together accordingly.\r\n\r\nAll of the standard Rearrange* commands now take an optional bang (!)--for example, Rearrangetabsbyextension!--that will, for just this rearrangement, IGNORE\r\nany local keys and treat all windows as if there were no keys.\r\n\r\nIf you have multiple windows where you're editing the same buffer, they will almost always end up together after any rearrangement (unless they are split\r\nacross tabs that become full). You can avoid this by setting different window-level local keys for the buffers.\r\n\r\nAdded four new commands--the set and remove key commands can be combined with windo and tabdo to set or remove the same key for more than one window at a time:\r\n\r\nSettabmanagerwindowkey <key>: Sets the window-level local key for the current window to <key>.\r\n\r\nSettabmanagerbufferkey <key>: Sets the buffer-level local key for the current buffer to <key>.\r\n\r\nRemovetabmanagerkey: Removes the currently set key for the current window; will remove BOTH buffer and window level keys. (Doesn't take any arguments.)\r\n\r\nRedorearrangetabs: Redoes the last tab rearrangement command (by extension, simple tiling, by first letters, etc.). Useful for incorporating new windows into\r\nthe currenty \"scheme\". If local keys have changed, the layout may end up being different. If new windows have been added, the layout may be different, also,\r\nbut that may be what you want. By default, it obeys local keys (even if the last command was called with a bang and did not). Accepts a bang (!) to ignore\r\nlocal keys.\r\n\r\nIf you call this before you've run any actual rearrangement commands, you will most likely (deservedly) get an error.\r\n","package":"TabManager.vim","4":"TabManager.vim","src_id":"15447","5":"15447","creation_date":"1302710739","6":"1302710739"},{"0":"3536","vim_version":"7.0","1":"7.0","script_version":"1.45","2":"1.45","version_comment":"Added new command:\r\n\r\nCopytotab: copies the current file to the specified tab (just like Movetotab except that the original tab also contains the file).\r\n","3":"Added new command:\r\n\r\nCopytotab: copies the current file to the specified tab (just like Movetotab except that the original tab also contains the file).\r\n","package":"TabManager.vim","4":"TabManager.vim","src_id":"15410","5":"15410","creation_date":"1302205029","6":"1302205029"},{"0":"3536","vim_version":"7.0","1":"7.0","script_version":"1.4","2":"1.4","version_comment":"Added new command:\r\n\r\nMovetotab: moves the current file to the specified tab; understands absolute numbers (1 for the first tab, for example) as well as:\r\n\r\n- n: next tab\r\n- p: previous tab\r\n- $: last tab\r\n","3":"Added new command:\r\n\r\nMovetotab: moves the current file to the specified tab; understands absolute numbers (1 for the first tab, for example) as well as:\r\n\r\n- n: next tab\r\n- p: previous tab\r\n- $: last tab\r\n","package":"TabManager.vim","4":"TabManager.vim","src_id":"15408","5":"15408","creation_date":"1302190541","6":"1302190541"},{"0":"3536","vim_version":"7.0","1":"7.0","script_version":"1.37","2":"1.37","version_comment":"Fixed a problem where newly created tabs always had an empty window at the bottom. (Executes an :e the first time in a new tab instead of an :sp.)","3":"Fixed a problem where newly created tabs always had an empty window at the bottom. (Executes an :e the first time in a new tab instead of an :sp.)","package":"TabManager.vim","4":"TabManager.vim","src_id":"15389","5":"15389","creation_date":"1302029628","6":"1302029628"},{"0":"3536","vim_version":"7.0","1":"7.0","script_version":"1.36","2":"1.36","version_comment":"Fixed typo; thank you, Christophe.","3":"Fixed typo; thank you, Christophe.","package":"TabManager.vim","4":"TabManager.vim","src_id":"15387","5":"15387","creation_date":"1302004988","6":"1302004988"},{"0":"3536","vim_version":"7.0","1":"7.0","script_version":"1.35","2":"1.35","version_comment":"Version 1.35:\r\n\r\nTakes 'ignorecase' into consideration for matching extensions, first letters and complete file paths (but not for matching roots and \"types\").\r\n","3":"Version 1.35:\r\n\r\nTakes 'ignorecase' into consideration for matching extensions, first letters and complete file paths (but not for matching roots and \"types\").\r\n","package":"TabManager.vim","4":"TabManager.vim","src_id":"15382","5":"15382","creation_date":"1301961042","6":"1301961042"},{"0":"3536","vim_version":"7.0","1":"7.0","script_version":"1.3","2":"1.3","version_comment":"Version 1.3:\r\n\r\nRearrangetabsbyfirstletter renamed to Rearrangetabsbyfirstletters: If called with no parameters, considers the first character of the file name, as before. If\r\ncalled with one parameter, the specified number of characters is considered. For example, with no parameters, \"Test.java\" and \"Touring.java\" would be placed\r\ntogether because both start with a T. With 2 as the parameter value, they would be separated (\"Te\" vs. \"To\").\r\n\r\nIf called with 2 parameters, the first parameter is the number of windows to place in one tab, as always (0 meaning to throw them all together).\r\n","3":"Version 1.3:\r\n\r\nRearrangetabsbyfirstletter renamed to Rearrangetabsbyfirstletters: If called with no parameters, considers the first character of the file name, as before. If\r\ncalled with one parameter, the specified number of characters is considered. For example, with no parameters, \"Test.java\" and \"Touring.java\" would be placed\r\ntogether because both start with a T. With 2 as the parameter value, they would be separated (\"Te\" vs. \"To\").\r\n\r\nIf called with 2 parameters, the first parameter is the number of windows to place in one tab, as always (0 meaning to throw them all together).\r\n","package":"TabManager.vim","4":"TabManager.vim","src_id":"15380","5":"15380","creation_date":"1301933783","6":"1301933783"},{"0":"3536","vim_version":"7.0","1":"7.0","script_version":"1.25","2":"1.25","version_comment":"Removed debug statements left in by mistake and fixed a conversion error.","3":"Removed debug statements left in by mistake and fixed a conversion error.","package":"TabManager.vim","4":"TabManager.vim","src_id":"15379","5":"15379","creation_date":"1301923290","6":"1301923290"},{"0":"3536","vim_version":"7.0","1":"7.0","script_version":"1.2","2":"1.2","version_comment":"Version 1.2:\r\n\r\nNew variable: g:TabManager_fileTypeExtension (defaults to \"java\") to use when determining the Rearrangetabsbytype; can be passed to the command on the\r\ncommand-line as an override.\r\n\r\nRearrangetabsbytype now takes an extension (other than the default \"java\" or g:TabManager_fileTypeExtension) to use when sorting the files.\r\n","3":"Version 1.2:\r\n\r\nNew variable: g:TabManager_fileTypeExtension (defaults to \"java\") to use when determining the Rearrangetabsbytype; can be passed to the command on the\r\ncommand-line as an override.\r\n\r\nRearrangetabsbytype now takes an extension (other than the default \"java\" or g:TabManager_fileTypeExtension) to use when sorting the files.\r\n","package":"TabManager.vim","4":"TabManager.vim","src_id":"15374","5":"15374","creation_date":"1301881336","6":"1301881336"},{"0":"3536","vim_version":"7.0","1":"7.0","script_version":"1.1","2":"1.1","version_comment":"Added two new commands:\r\n\r\nRearrangetabsbytype: If it's a Java file, returns the last word that's not a part of the extension. For example, CopyAction.java returns Action and\r\nCopyForm.java returns Form. This should probably be reworked to allow the setting of the extension upon which to filter or to not look at extensions at all.\r\n\r\nRearrangetabsbyroot: Groups files with similarly named roots together. For example, CopyAction.java, CopyForm.java and CopyResults.jsp will end up together\r\nbecause they all have \"Copy\" as the root.\r\n","3":"Added two new commands:\r\n\r\nRearrangetabsbytype: If it's a Java file, returns the last word that's not a part of the extension. For example, CopyAction.java returns Action and\r\nCopyForm.java returns Form. This should probably be reworked to allow the setting of the extension upon which to filter or to not look at extensions at all.\r\n\r\nRearrangetabsbyroot: Groups files with similarly named roots together. For example, CopyAction.java, CopyForm.java and CopyResults.jsp will end up together\r\nbecause they all have \"Copy\" as the root.\r\n","package":"TabManager.vim","4":"TabManager.vim","src_id":"15373","5":"15373","creation_date":"1301856783","6":"1301856783"},{"0":"3536","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"TabManager.vim","4":"TabManager.vim","src_id":"15363","5":"15363","creation_date":"1301789477","6":"1301789477"}]},"3535":{"script_id":"3535","0":"3535","script_name":"vim-task","1":"vim-task","script_type":"ftplugin","2":"ftplugin","summary":"vim task plugin, help people practice GTD in their favorite editor","3":"vim task plugin, help people practice GTD in their favorite editor","description":"Basically, this is the TextMate Tasks Bundle port for Vim.\r\n\r\nPlease see details at:\r\nhttps:\/\/github.com\/samsonw\/vim-task","4":"Basically, this is the TextMate Tasks Bundle port for Vim.\r\n\r\nPlease see details at:\r\nhttps:\/\/github.com\/samsonw\/vim-task","install_details":"Normal installation steps follow the vim tradition: download the zip\/tar archive then copy all the directories\/files to ~\/.vim directory. You can download vim-task zip\/tar archive by clicking the \u00e2\u0080\u009cDownload Source\u00e2\u0080\u009d button in github.\r\n\r\nYou can also check out the latest code if you have git installed:\r\n\r\n$ git clone git:\/\/github.com\/samsonw\/vim-task.git\r\n$ cd vim-task\r\n$ rm README.mkd\r\n$ cp -rv * ~\/.vim\r\n\r\nFor those guys who use pathogen, the installation should be as simple as a git clone:\r\n\r\n$ cd ~\/.vim\/bundle\r\n$ git clone git:\/\/github.com\/samsonw\/vim-task.git\r\n\r\nunfortunately ftdetect directory seems not take effect in pathogen, I\u00e2\u0080\u0099m still wondering about why, but anyway here is a temporary workaround for now:\r\n\r\n$ mkdir -p ~\/.vim\/ftdetect\r\n$ cd ~\/.vim\/ftdetect\r\n$ ln -s ..\/bundle\/vim-task\/ftdetect\/task.vim task.vim\r\n","5":"Normal installation steps follow the vim tradition: download the zip\/tar archive then copy all the directories\/files to ~\/.vim directory. You can download vim-task zip\/tar archive by clicking the \u00e2\u0080\u009cDownload Source\u00e2\u0080\u009d button in github.\r\n\r\nYou can also check out the latest code if you have git installed:\r\n\r\n$ git clone git:\/\/github.com\/samsonw\/vim-task.git\r\n$ cd vim-task\r\n$ rm README.mkd\r\n$ cp -rv * ~\/.vim\r\n\r\nFor those guys who use pathogen, the installation should be as simple as a git clone:\r\n\r\n$ cd ~\/.vim\/bundle\r\n$ git clone git:\/\/github.com\/samsonw\/vim-task.git\r\n\r\nunfortunately ftdetect directory seems not take effect in pathogen, I\u00e2\u0080\u0099m still wondering about why, but anyway here is a temporary workaround for now:\r\n\r\n$ mkdir -p ~\/.vim\/ftdetect\r\n$ cd ~\/.vim\/ftdetect\r\n$ ln -s ..\/bundle\/vim-task\/ftdetect\/task.vim task.vim\r\n","first_name":"Samson","6":"Samson","last_name":"Wu","7":"Wu","releases":[{"0":"3535","vim_version":"7.0","1":"7.0","script_version":"1.1","2":"1.1","version_comment":"version 1.1","3":"version 1.1","package":"vim-task.tar.gz","4":"vim-task.tar.gz","src_id":"17569","5":"17569","creation_date":"1331042027","6":"1331042027"},{"0":"3535","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"vim-task.tar.gz","4":"vim-task.tar.gz","src_id":"15360","5":"15360","creation_date":"1301748921","6":"1301748921"}]},"3534":{"script_id":"3534","0":"3534","script_name":"strange","1":"strange","script_type":"color scheme","2":"color scheme","summary":"A muted vim color scheme for 8- and 256-color terminals, as well as gui vim","3":"A muted vim color scheme for 8- and 256-color terminals, as well as gui vim","description":"A muted color scheme that works in 8- and 256-color terminals, as well as in the GUI versions of vim.\r\n\r\nGithub repo:\r\n\r\nhttps:\/\/github.com\/strange\/strange.vim\/","4":"A muted color scheme that works in 8- and 256-color terminals, as well as in the GUI versions of vim.\r\n\r\nGithub repo:\r\n\r\nhttps:\/\/github.com\/strange\/strange.vim\/","install_details":"Use pathogen.\r\n\r\nhttp:\/\/vimcasts.org\/episodes\/synchronizing-plugins-with-git-submodules-and-pathogen\/","5":"Use pathogen.\r\n\r\nhttp:\/\/vimcasts.org\/episodes\/synchronizing-plugins-with-git-submodules-and-pathogen\/","first_name":"Gustaf","6":"Gustaf","last_name":"Sjoberg","7":"Sjoberg","releases":[{"0":"3534","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"strange.tar.gz","4":"strange.tar.gz","src_id":"15359","5":"15359","creation_date":"1301737143","6":"1301737143"}]},"3533":{"script_id":"3533","0":"3533","script_name":"GetFilePlus","1":"GetFilePlus","script_type":"utility","2":"utility","summary":"a gf tweak for python webapp developers","3":"a gf tweak for python webapp developers","description":"Usage: place plugin\/gf.vim in your ~\/.vim\/plugin directory\r\nRepo: https:\/\/github.com\/mjbrownie\/GetFilePlus\r\n\r\nGetFilePlus is a simple enhancement on the gf mappings it does the following\r\n\r\n1. standard 'find file\/path.ext' first as normal gf would.\r\n\r\n2. does a 'find .\/file\/path.ext'. check\r\n\r\n    This is for when a file path starts with a \/ (often js and css references).\r\n\r\n    eg: \/js\/some_file.js that actually  resides in media\/js\/some_file.js\r\n\r\n    Note for this to be useful you need to set up your :set path to refer to\r\n    the directories you want. (Eg. I have :set path+=media\/ in my .vimrc)\r\n\r\n3. does a python path check eg.\r\n\r\n    from django.contrib.admin.views import foobar\r\n\r\n    would open \/yourvirtualenv\/lib\/site-packages\/django\/contrib\/admin\/views.py\r\n\r\n    Note for this to work you need the python path to set eg in your .vimrc\r\n    python import sys;sys.path = sys.path + ['yourvirtualenv\/lib\/site-packages\/']\r\n\r\nAlso as a bonus There is a command included to make it easier to open python\r\nfiles from the command line.\r\n\r\n    :Ppath django.contrib.admin.views<cr>\r\n\r\n    would open \/yourvirtualenv\/lib\/site-packages\/django\/contrib\/admin\/views.py\r\n\r\nNote as is the script will send any import errors to screen. If this is the\r\ncase then it's just sys.path not configured properly\r\n\r\nThis script needs vim python support","4":"Usage: place plugin\/gf.vim in your ~\/.vim\/plugin directory\r\nRepo: https:\/\/github.com\/mjbrownie\/GetFilePlus\r\n\r\nGetFilePlus is a simple enhancement on the gf mappings it does the following\r\n\r\n1. standard 'find file\/path.ext' first as normal gf would.\r\n\r\n2. does a 'find .\/file\/path.ext'. check\r\n\r\n    This is for when a file path starts with a \/ (often js and css references).\r\n\r\n    eg: \/js\/some_file.js that actually  resides in media\/js\/some_file.js\r\n\r\n    Note for this to be useful you need to set up your :set path to refer to\r\n    the directories you want. (Eg. I have :set path+=media\/ in my .vimrc)\r\n\r\n3. does a python path check eg.\r\n\r\n    from django.contrib.admin.views import foobar\r\n\r\n    would open \/yourvirtualenv\/lib\/site-packages\/django\/contrib\/admin\/views.py\r\n\r\n    Note for this to work you need the python path to set eg in your .vimrc\r\n    python import sys;sys.path = sys.path + ['yourvirtualenv\/lib\/site-packages\/']\r\n\r\nAlso as a bonus There is a command included to make it easier to open python\r\nfiles from the command line.\r\n\r\n    :Ppath django.contrib.admin.views<cr>\r\n\r\n    would open \/yourvirtualenv\/lib\/site-packages\/django\/contrib\/admin\/views.py\r\n\r\nNote as is the script will send any import errors to screen. If this is the\r\ncase then it's just sys.path not configured properly\r\n\r\nThis script needs vim python support","install_details":"place gf.vim in your plugin directory","5":"place gf.vim in your plugin directory","first_name":"Michael","6":"Michael","last_name":"Brown","7":"Brown","releases":[{"0":"3533","vim_version":"7.2","1":"7.2","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"mjbrownie-GetFilePlus-67345e4.tar.gz","4":"mjbrownie-GetFilePlus-67345e4.tar.gz","src_id":"15357","5":"15357","creation_date":"1301730748","6":"1301730748"}]},"3532":{"script_id":"3532","0":"3532","script_name":"UltraBlog","1":"UltraBlog","script_type":"utility","2":"utility","summary":"Ultimate Vim blogging plugin","3":"Ultimate Vim blogging plugin","description":"UltraBlog.vim is yet another Vim blogging script for Wordpress.\r\n\r\nThe biggest difference between UB and other similar scripts is that UB is an ultimate client, which stores posts locally in an SQLite database, while others just operate remotely. In this way, many things can be done easily by the advantage of local storage and many other utilities, for example, you can search for posts stored in the database with a few keywords by typing a simple command, also you can preview drafts with any of your favorite templates as soon as you want to.\r\n\r\nFor those who just needs a lightweight blog editor similar as other Vim blogging scripts, UB also comes with an Editor Mode, which doesn't create a database and store data in it.\r\n\r\nIn addition, UB is tending to make life easier for writing posts with many kinds of lightweight markup languages, currently the following kinds are supported: Markdown, reStructuredText, LaTeX, Textile and of cause HTML.\r\n\r\nEnjoy Vim blogging !\r\n\r\nRefer to the plugin's page for detail information:\r\n\r\nhttp:\/\/0x3f.org\/blog\/ultrablog-as-an-ultimate-vim-blogging-plugin\/\r\n\r\nFor the usage of templates, go to:\r\n\r\nhttp:\/\/0x3f.org\/blog\/enable-code-snippet-highlighting-for-ultrablog-vim-templates\/\r\n\r\n*Features:*\r\n\r\n    * Multiple syntax support: Markdown, HTML, reStructuredText, LaTeX, Textile.\r\n    * Editor mode and client mode.\r\n    * Data is stored in a local SQLite database in client mode.\r\n    * Full-text search with keywords highlighted.\r\n    * Full-text search by using regular expressions.\r\n    * Full-text substitutions.\r\n    * Full-text substitutions using regular expressions.\r\n    * Templates for previewing posts.\r\n    * Built-in web browser, much faster to preview items.\r\n    * Event-driven system.\r\n    * I18N.\r\n\r\n*Commands:*\r\n\r\n    * :UBNew [item [syntax\/template_name]]\r\n    * :UBPreview [status\/template name]\r\n    * :UBSave\r\n    * :UBSend [status]\r\n    * :UBList [item [scope [page_size [page_no]]]]\r\n    * :UBOpen {item} {post_id\/template_name} [scope]\r\n    * :UBDel {item} {post_id\/template_name} [scope]\r\n    * :UBUpload {file_path}\r\n    * :UBThis [item [to_syntax [from_syntax]]]\r\n    * :UBConv {to_syntax} [from_syntax]\r\n    * :UBRefresh\r\n    * :UBFind keyword1 [keyword2 ...]\r\n    * :UBRegexSearch regexp1 [regexp2 ...]\r\n    * :UBReplace needle replacement\r\n    * :UBRegexReplace regexp replacement\r\n    * :UBEnableDebug\r\n    * :UBDisableDebug\r\n    * :UBToggleDebug","4":"UltraBlog.vim is yet another Vim blogging script for Wordpress.\r\n\r\nThe biggest difference between UB and other similar scripts is that UB is an ultimate client, which stores posts locally in an SQLite database, while others just operate remotely. In this way, many things can be done easily by the advantage of local storage and many other utilities, for example, you can search for posts stored in the database with a few keywords by typing a simple command, also you can preview drafts with any of your favorite templates as soon as you want to.\r\n\r\nFor those who just needs a lightweight blog editor similar as other Vim blogging scripts, UB also comes with an Editor Mode, which doesn't create a database and store data in it.\r\n\r\nIn addition, UB is tending to make life easier for writing posts with many kinds of lightweight markup languages, currently the following kinds are supported: Markdown, reStructuredText, LaTeX, Textile and of cause HTML.\r\n\r\nEnjoy Vim blogging !\r\n\r\nRefer to the plugin's page for detail information:\r\n\r\nhttp:\/\/0x3f.org\/blog\/ultrablog-as-an-ultimate-vim-blogging-plugin\/\r\n\r\nFor the usage of templates, go to:\r\n\r\nhttp:\/\/0x3f.org\/blog\/enable-code-snippet-highlighting-for-ultrablog-vim-templates\/\r\n\r\n*Features:*\r\n\r\n    * Multiple syntax support: Markdown, HTML, reStructuredText, LaTeX, Textile.\r\n    * Editor mode and client mode.\r\n    * Data is stored in a local SQLite database in client mode.\r\n    * Full-text search with keywords highlighted.\r\n    * Full-text search by using regular expressions.\r\n    * Full-text substitutions.\r\n    * Full-text substitutions using regular expressions.\r\n    * Templates for previewing posts.\r\n    * Built-in web browser, much faster to preview items.\r\n    * Event-driven system.\r\n    * I18N.\r\n\r\n*Commands:*\r\n\r\n    * :UBNew [item [syntax\/template_name]]\r\n    * :UBPreview [status\/template name]\r\n    * :UBSave\r\n    * :UBSend [status]\r\n    * :UBList [item [scope [page_size [page_no]]]]\r\n    * :UBOpen {item} {post_id\/template_name} [scope]\r\n    * :UBDel {item} {post_id\/template_name} [scope]\r\n    * :UBUpload {file_path}\r\n    * :UBThis [item [to_syntax [from_syntax]]]\r\n    * :UBConv {to_syntax} [from_syntax]\r\n    * :UBRefresh\r\n    * :UBFind keyword1 [keyword2 ...]\r\n    * :UBRegexSearch regexp1 [regexp2 ...]\r\n    * :UBReplace needle replacement\r\n    * :UBRegexReplace regexp replacement\r\n    * :UBEnableDebug\r\n    * :UBDisableDebug\r\n    * :UBToggleDebug","install_details":"1. Make sure your Vim has support for Python.\r\n2. Install sqlalchemy, pandoc, python-markdown or python-markdown2 for python\r\n3. Add the following configurations to your vimrc:\r\n\r\nlet ub_blog = {'login_name':'admin',\r\n            \\'password':'pass2011',\r\n            \\'url':'http:\/\/www.sample.com',\r\n            \\'db':'$VIM\/UltraBlog.db'\r\n            \\}","5":"1. Make sure your Vim has support for Python.\r\n2. Install sqlalchemy, pandoc, python-markdown or python-markdown2 for python\r\n3. Add the following configurations to your vimrc:\r\n\r\nlet ub_blog = {'login_name':'admin',\r\n            \\'password':'pass2011',\r\n            \\'url':'http:\/\/www.sample.com',\r\n            \\'db':'$VIM\/UltraBlog.db'\r\n            \\}","first_name":"lenin","6":"lenin","last_name":"lee","7":"lee","releases":[{"0":"3532","vim_version":"7.0","1":"7.0","script_version":"3.6.1","2":"3.6.1","version_comment":"* Feature: Add an option 'categories' in the initial settings, categories will be fetched from the blog if this option is not set. Users can auto-complete categories using <C-X><C-U>.","3":"* Feature: Add an option 'categories' in the initial settings, categories will be fetched from the blog if this option is not set. Users can auto-complete categories using <C-X><C-U>.","package":"UltraBlog.zip","4":"UltraBlog.zip","src_id":"21795","5":"21795","creation_date":"1398007611","6":"1398007611"},{"0":"3532","vim_version":"7.0","1":"7.0","script_version":"3.6.0","2":"3.6.0","version_comment":"* Feature: Add new options |ub_viewer_width| and |ub_viewer_width|, which define the default width and height of the built-in web browser.\r\n* Change:  The default width of the built-in web browser is now changed to 900px.\r\n* Bugfix:  Fix the overwriting to auto commands created by other plugins.","3":"* Feature: Add new options |ub_viewer_width| and |ub_viewer_width|, which define the default width and height of the built-in web browser.\r\n* Change:  The default width of the built-in web browser is now changed to 900px.\r\n* Bugfix:  Fix the overwriting to auto commands created by other plugins.","package":"UltraBlog.zip","4":"UltraBlog.zip","src_id":"18435","5":"18435","creation_date":"1345445869","6":"1345445869"},{"0":"3532","vim_version":"7.0","1":"7.0","script_version":"3.5.0","2":"3.5.0","version_comment":"Feature: Add a tiny web browser to do previewing, which starts much faster than full-functional browsers like firefox and chromium. The later ones are still supported. The matter that whether or not to use the new previewer is controlled by a new option ub_use_ubviewer.\r\nBugfix: Issue 7: Keywords highlighting is disabled in item lists, even if searches are made manually.","3":"Feature: Add a tiny web browser to do previewing, which starts much faster than full-functional browsers like firefox and chromium. The later ones are still supported. The matter that whether or not to use the new previewer is controlled by a new option ub_use_ubviewer.\r\nBugfix: Issue 7: Keywords highlighting is disabled in item lists, even if searches are made manually.","package":"UltraBlog.zip","4":"UltraBlog.zip","src_id":"17838","5":"17838","creation_date":"1335765569","6":"1335765569"},{"0":"3532","vim_version":"7.0","1":"7.0","script_version":"3.4.0","2":"3.4.0","version_comment":"Feature: Add the command :UBRegexSearch, doing full-text searches with regular expressions !\r\nFeature: Add the command :UBReplace, doing full-text substitutions.\r\nFeature: Add the command :UBRegexReplace, doing full-text substitutions with regular expressions.\r\nFeature: Add commands :UBEnableDebug, :UBDisableDebug, :UBToggleDebug and an option ub_debug. In debug mode, SQL statements and stack traces of exceptions will be displayed.\r\nChange: Undo keywords highlighting after executing :UBList.\r\nBugfix: Exceptions raised when opening the current item under cursor in item lists if the option ub_hotkey_save_current_item has not been set. Now this options comes with a default value.","3":"Feature: Add the command :UBRegexSearch, doing full-text searches with regular expressions !\r\nFeature: Add the command :UBReplace, doing full-text substitutions.\r\nFeature: Add the command :UBRegexReplace, doing full-text substitutions with regular expressions.\r\nFeature: Add commands :UBEnableDebug, :UBDisableDebug, :UBToggleDebug and an option ub_debug. In debug mode, SQL statements and stack traces of exceptions will be displayed.\r\nChange: Undo keywords highlighting after executing :UBList.\r\nBugfix: Exceptions raised when opening the current item under cursor in item lists if the option ub_hotkey_save_current_item has not been set. Now this options comes with a default value.","package":"UltraBlog.zip","4":"UltraBlog.zip","src_id":"17836","5":"17836","creation_date":"1335692424","6":"1335692424"},{"0":"3532","vim_version":"7.0","1":"7.0","script_version":"3.3.0","2":"3.3.0","version_comment":"Notice:  This plugin is now published as a zip package, for vimball cannot handling binary files.\r\nFeature: Add i18n support !\r\nFeature: Add a new option ub_hotkey_save_current_item, users can define their own hotkey for :UBSave.\r\nFeature: Add a new option ub_socket_timeout, users can customize the timeout period in seconds, useful for slow networks.\r\nBugfix: Exception raised when one event is processed by more than one event handlers.\r\nChange: Echoing messages now uses the command :echoerr instead of python's sys.stderr, because Vim crashes on this due to an upgrade recently.\r\nChange: Change commands :UBSave, :UBSend, :UBUpload, :UBConv, :UBPreview to be available only in their effective views.\r\nChange: Lists are set nowrapped.\r\nBugfix: Stop complaining '_pop from empty list_' while doing almost everything.","3":"Notice:  This plugin is now published as a zip package, for vimball cannot handling binary files.\r\nFeature: Add i18n support !\r\nFeature: Add a new option ub_hotkey_save_current_item, users can define their own hotkey for :UBSave.\r\nFeature: Add a new option ub_socket_timeout, users can customize the timeout period in seconds, useful for slow networks.\r\nBugfix: Exception raised when one event is processed by more than one event handlers.\r\nChange: Echoing messages now uses the command :echoerr instead of python's sys.stderr, because Vim crashes on this due to an upgrade recently.\r\nChange: Change commands :UBSave, :UBSend, :UBUpload, :UBConv, :UBPreview to be available only in their effective views.\r\nChange: Lists are set nowrapped.\r\nBugfix: Stop complaining '_pop from empty list_' while doing almost everything.","package":"UltraBlog.zip","4":"UltraBlog.zip","src_id":"17777","5":"17777","creation_date":"1334494611","6":"1334494611"},{"0":"3532","vim_version":"7.0","1":"7.0","script_version":"3.2.0","2":"3.2.0","version_comment":"* :UBConv now depends on the python-html2text module when converts buffers from HTML to Markdown.\r\n* Change the domain name of my site to the new 0x3f.org.","3":"* :UBConv now depends on the python-html2text module when converts buffers from HTML to Markdown.\r\n* Change the domain name of my site to the new 0x3f.org.","package":"UltraBlog.vmb","4":"UltraBlog.vmb","src_id":"17152","5":"17152","creation_date":"1325755886","6":"1325755886"},{"0":"3532","vim_version":"7.0","1":"7.0","script_version":"3.1.0","2":"3.1.0","version_comment":"* Change:  The key \"xmlrpc\" of the settings list is dropped, a new one with the name \"url\" is added, you should set its value to the blog url.\r\n* Change:  Source code refactorings.\r\n* Change:  Solve the crash problem existing in MacVim only.\r\n* Change:  |:UBConv| can be used in any buffer.\r\n* Change:  |:UBThis| now has a third parameter, which enables convertions between syntaxes.\r\n* Bugfix:  The second parameter of |:UBThis| cannot take effect.","3":"* Change:  The key \"xmlrpc\" of the settings list is dropped, a new one with the name \"url\" is added, you should set its value to the blog url.\r\n* Change:  Source code refactorings.\r\n* Change:  Solve the crash problem existing in MacVim only.\r\n* Change:  |:UBConv| can be used in any buffer.\r\n* Change:  |:UBThis| now has a third parameter, which enables convertions between syntaxes.\r\n* Bugfix:  The second parameter of |:UBThis| cannot take effect.","package":"UltraBlog.vmb","4":"UltraBlog.vmb","src_id":"16778","5":"16778","creation_date":"1320161360","6":"1320161360"},{"0":"3532","vim_version":"7.0","1":"7.0","script_version":"3.0.0","2":"3.0.0","version_comment":"* Feature: Mostly rewritten for implementing an event-driven system.\r\n* Feature: Context search comes with keywords highlighting. A new command :UBFind and a new option ub_search_pagesize.\r\n* Feature: Refresh every buffer with the new command |:UBRefresh|.\r\n* Bugfix: Some.","3":"* Feature: Mostly rewritten for implementing an event-driven system.\r\n* Feature: Context search comes with keywords highlighting. A new command :UBFind and a new option ub_search_pagesize.\r\n* Feature: Refresh every buffer with the new command |:UBRefresh|.\r\n* Bugfix: Some.","package":"UltraBlog.vba","4":"UltraBlog.vba","src_id":"16133","5":"16133","creation_date":"1311523747","6":"1311523747"},{"0":"3532","vim_version":"7.0","1":"7.0","script_version":"2.3.1","2":"2.3.1","version_comment":"* Bugfix: Listing remote posts will complain the error: local variable 'page_no' referenced before assignment.\r\n* Bugfix: The editing window will be set as modified after being sent to blog when ub_save_after_sent is 0 and the buffer was in unmodified status.","3":"* Bugfix: Listing remote posts will complain the error: local variable 'page_no' referenced before assignment.\r\n* Bugfix: The editing window will be set as modified after being sent to blog when ub_save_after_sent is 0 and the buffer was in unmodified status.","package":"UltraBlog.vba","4":"UltraBlog.vba","src_id":"15902","5":"15902","creation_date":"1308150322","6":"1308150322"},{"0":"3532","vim_version":"7.0","1":"7.0","script_version":"2.3.0","2":"2.3.0","version_comment":"* Feature: Preview posts\/pages locally with pre-defined templates, template related operations and management.\r\n* Feature: Preview posts\/pages after sending them to the blog.\r\n* Change: Merge :UBPageNew to :UBNew, merge :UBPageOpen to :UBOpen, merge :UBPageList to :UBList, merge :UBPageThis to :UBThis.\r\n* Bugfix: The remote page list will raise an error when openned due to a change made in last version.\r\n* Bugfix: The post\/page list will raise an error when an item is deleted in it, caused by a change made in last version.","3":"* Feature: Preview posts\/pages locally with pre-defined templates, template related operations and management.\r\n* Feature: Preview posts\/pages after sending them to the blog.\r\n* Change: Merge :UBPageNew to :UBNew, merge :UBPageOpen to :UBOpen, merge :UBPageList to :UBList, merge :UBPageThis to :UBThis.\r\n* Bugfix: The remote page list will raise an error when openned due to a change made in last version.\r\n* Bugfix: The post\/page list will raise an error when an item is deleted in it, caused by a change made in last version.","package":"UltraBlog.vba","4":"UltraBlog.vba","src_id":"15851","5":"15851","creation_date":"1307721679","6":"1307721679"},{"0":"3532","vim_version":"7.0","1":"7.0","script_version":"2.2.0","2":"2.2.0","version_comment":"* Change: Merge :UBSave and :UBPageSave to :UBSave, merge :UBSend and :UBPageSend to :UBSend.\r\n* Feature: Add an option ub_tmpl_img_url to customize a link template string for the image uploaded by :UBUpload.","3":"* Change: Merge :UBSave and :UBPageSave to :UBSave, merge :UBSend and :UBPageSend to :UBSend.\r\n* Feature: Add an option ub_tmpl_img_url to customize a link template string for the image uploaded by :UBUpload.","package":"UltraBlog.vba","4":"UltraBlog.vba","src_id":"15767","5":"15767","creation_date":"1306770033","6":"1306770033"},{"0":"3532","vim_version":"7.0","1":"7.0","script_version":"2.1.0","2":"2.1.0","version_comment":"* Change: Increase the requirement to SQLAlchemy to version 0.7 or newer.\r\n* Feature: Now posts\/pages can be opened in a new tab or splitted window.\r\n* Feature: Add options to let users customize hotkeys:\r\n    * ub_hotkey_open_item_in_current_view\r\n    * ub_hotkey_open_item_in_splitted_view\r\n    * ub_hotkey_open_item_in_tabbed_view\r\n    * ub_hotkey_delete_item","3":"* Change: Increase the requirement to SQLAlchemy to version 0.7 or newer.\r\n* Feature: Now posts\/pages can be opened in a new tab or splitted window.\r\n* Feature: Add options to let users customize hotkeys:\r\n    * ub_hotkey_open_item_in_current_view\r\n    * ub_hotkey_open_item_in_splitted_view\r\n    * ub_hotkey_open_item_in_tabbed_view\r\n    * ub_hotkey_delete_item","package":"UltraBlog.vba","4":"UltraBlog.vba","src_id":"15747","5":"15747","creation_date":"1306593120","6":"1306593120"},{"0":"3532","vim_version":"7.0","1":"7.0","script_version":"2.0.1","2":"2.0.1","version_comment":"* Bugfix:  Uploading media files may fail on Windows.\r\n* Bugfix:  An exception may be raised when Vim starts with no proper configuration for UltraBlog.vim or some prerequisites are not met.","3":"* Bugfix:  Uploading media files may fail on Windows.\r\n* Bugfix:  An exception may be raised when Vim starts with no proper configuration for UltraBlog.vim or some prerequisites are not met.","package":"UltraBlog.vba","4":"UltraBlog.vba","src_id":"15628","5":"15628","creation_date":"1305214358","6":"1305214358"},{"0":"3532","vim_version":"7.0","1":"7.0","script_version":"2.0","2":"2.0","version_comment":"  * Feature: Add editor mode.\r\n  * Feature: Add more syntaxes: LaTeX, reStructuredText and Textile.\r\n  * Feature: Add command *:UBConv* to convert a post\/page from one syntax to another.\r\n  * Feature: Add options *ub_converter_command*, *ub_converter_options*, *ub_converter_option_from*, *ub_converter_option_to* to specify a custom extenal command in place of pandoc as the converter.\r\n  * Feature: Add option *ub_save_after_opened* to control whether to save posts\/pages to database right after they are fetched from blogs.\r\n  * Feature: Add option *ub_save_after_sent* to control whether to save posts\/pages to database right after they are sent to blogs.\r\n","3":"  * Feature: Add editor mode.\r\n  * Feature: Add more syntaxes: LaTeX, reStructuredText and Textile.\r\n  * Feature: Add command *:UBConv* to convert a post\/page from one syntax to another.\r\n  * Feature: Add options *ub_converter_command*, *ub_converter_options*, *ub_converter_option_from*, *ub_converter_option_to* to specify a custom extenal command in place of pandoc as the converter.\r\n  * Feature: Add option *ub_save_after_opened* to control whether to save posts\/pages to database right after they are fetched from blogs.\r\n  * Feature: Add option *ub_save_after_sent* to control whether to save posts\/pages to database right after they are sent to blogs.\r\n","package":"UltraBlog.vba","4":"UltraBlog.vba","src_id":"15457","5":"15457","creation_date":"1302958554","6":"1302958554"},{"0":"3532","vim_version":"7.0","1":"7.0","script_version":"1.4","2":"1.4","version_comment":"Feature: Add commands :UBThis and :UBPageThis to create a new post or page with content in the current buffer.","3":"Feature: Add commands :UBThis and :UBPageThis to create a new post or page with content in the current buffer.","package":"UltraBlog.vba","4":"UltraBlog.vba","src_id":"15435","5":"15435","creation_date":"1302597037","6":"1302597037"},{"0":"3532","vim_version":"7.0","1":"7.0","script_version":"1.3","2":"1.3","version_comment":"* Feature: Record post statuses, post them in their recorded statuses when omit parameters for :UBSend and :UBPageSend. \r\n* Feature: Display post\/page status in post\/page list, add an option ub_list_col3_width to set its width. \r\n* Feature: Extend statuses to support private, pending and draft. \r\n* Feature: Change the status 'public' to 'publish'. \r\n* Feature: Check prerequesites in every top level functions. \r\n* Bugfix: Do not raise an error on startup when sqlalchemy is not installed.","3":"* Feature: Record post statuses, post them in their recorded statuses when omit parameters for :UBSend and :UBPageSend. \r\n* Feature: Display post\/page status in post\/page list, add an option ub_list_col3_width to set its width. \r\n* Feature: Extend statuses to support private, pending and draft. \r\n* Feature: Change the status 'public' to 'publish'. \r\n* Feature: Check prerequesites in every top level functions. \r\n* Bugfix: Do not raise an error on startup when sqlalchemy is not installed.","package":"UltraBlog.vba","4":"UltraBlog.vba","src_id":"15419","5":"15419","creation_date":"1302362385","6":"1302362385"},{"0":"3532","vim_version":"7.0","1":"7.0","script_version":"1.2","2":"1.2","version_comment":"* Feature: Column widths can be set to custom values, which keep post or page lists tidy. Two options added: ub_list_col1_width and ub_list_col2_width.","3":"* Feature: Column widths can be set to custom values, which keep post or page lists tidy. Two options added: ub_list_col1_width and ub_list_col2_width.","package":"UltraBlog.vba","4":"UltraBlog.vba","src_id":"15409","5":"15409","creation_date":"1302191147","6":"1302191147"},{"0":"3532","vim_version":"7.0","1":"7.0","script_version":"1.1","2":"1.1","version_comment":"* Feature: Page management.\r\n* Feature: Add option ub_append_promotion_link to control whether to append a promotion link of UltraBlog.vim.\r\n* Bugfix: Wrong order for parameters of commands :UBOpen and :UBDel in documentation.","3":"* Feature: Page management.\r\n* Feature: Add option ub_append_promotion_link to control whether to append a promotion link of UltraBlog.vim.\r\n* Bugfix: Wrong order for parameters of commands :UBOpen and :UBDel in documentation.","package":"UltraBlog.vba","4":"UltraBlog.vba","src_id":"15383","5":"15383","creation_date":"1301975540","6":"1301975540"},{"0":"3532","vim_version":"7.0","1":"7.0","script_version":"1.0.5","2":"1.0.5","version_comment":"* Feature: Add documentation.\r\n* Feature: Use Vimball as the default distribution format.\r\n* Feature: Add two options - |ub_local_pagesize| and |ub_remote_pagesize|.","3":"* Feature: Add documentation.\r\n* Feature: Use Vimball as the default distribution format.\r\n* Feature: Add two options - |ub_local_pagesize| and |ub_remote_pagesize|.","package":"UltraBlog.vba","4":"UltraBlog.vba","src_id":"15377","5":"15377","creation_date":"1301902578","6":"1301902578"},{"0":"3532","vim_version":"7.0","1":"7.0","script_version":"1.0.4","2":"1.0.4","version_comment":"* Fix the problem that an unexpected type exception is raised when UBList is given some numbers as parameters.","3":"* Fix the problem that an unexpected type exception is raised when UBList is given some numbers as parameters.","package":"UltraBlog.vim","4":"UltraBlog.vim","src_id":"15368","5":"15368","creation_date":"1301845508","6":"1301845508"},{"0":"3532","vim_version":"7.0","1":"7.0","script_version":"1.0.3","2":"1.0.3","version_comment":"* Add a column in remote post list the same as the one in local post list, which is used to display ids of local copies of corresponding posts.\r\n* Fix the problem that buffers can be reverted to what the previous views contain throught the undo action.\r\n* Fix the minor problem that text won't wrap automatically in views opened by the command :UBNew.","3":"* Add a column in remote post list the same as the one in local post list, which is used to display ids of local copies of corresponding posts.\r\n* Fix the problem that buffers can be reverted to what the previous views contain throught the undo action.\r\n* Fix the minor problem that text won't wrap automatically in views opened by the command :UBNew.","package":"UltraBlog.vim","4":"UltraBlog.vim","src_id":"15358","5":"15358","creation_date":"1301735989","6":"1301735989"},{"0":"3532","vim_version":"7.0","1":"7.0","script_version":"1.0.2","2":"1.0.2","version_comment":"* Fix the problem that Post.post_id won't be updated in database after a new post is sent to blog.\r\n* Fix the problem that it prompts for confirmation to delete the remote copy when deleting a post whose post_id is 0 from local post list.","3":"* Fix the problem that Post.post_id won't be updated in database after a new post is sent to blog.\r\n* Fix the problem that it prompts for confirmation to delete the remote copy when deleting a post whose post_id is 0 from local post list.","package":"UltraBlog.vim","4":"UltraBlog.vim","src_id":"15356","5":"15356","creation_date":"1301711920","6":"1301711920"},{"0":"3532","vim_version":"7.0","1":"7.0","script_version":"1.0.1","2":"1.0.1","version_comment":"Do not pop up an exception alert for the first time when Vim starts with UltraBlog.vim installed and no configurations added to the vimrc file.","3":"Do not pop up an exception alert for the first time when Vim starts with UltraBlog.vim installed and no configurations added to the vimrc file.","package":"UltraBlog.vim","4":"UltraBlog.vim","src_id":"15351","5":"15351","creation_date":"1301669537","6":"1301669537"},{"0":"3532","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"UltraBlog.vim","4":"UltraBlog.vim","src_id":"15349","5":"15349","creation_date":"1301647945","6":"1301647945"}]},"3531":{"script_id":"3531","0":"3531","script_name":"cmdline completion","1":"cmdline completion","script_type":"utility","2":"utility","summary":"cmdline completion like insert mode","3":"cmdline completion like insert mode","description":"This script let you can use CTRL-P\/N to complete word in cmdline mode\r\n just like in insert mode.\r\n\r\nfor instance :\r\n            1.   :something<C-P>\r\n            2.   \/else<C-N>\r\n      \r\nyou also can map other keys instead of <C-P\/N> like this in your vimrc: \r\n            cmap <C-J> <Plug>CmdlineCompletionBackward\r\n            cmap <C-K> <Plug>CmdlineCompletionForward\r\n\r\nOr,  you may wanna keep compatiable recent history when using <C-P\/N> , try this: ( Thanks for Enno.Nagel's good idea ) .\r\n            cmap <expr> <c-p> getcmdpos() == 1 ? '<up><home>' : '<plug>CmdlineCompletionBackward'\r\n            cmap <expr> <c-n> getcmdpos() == 1 ? '<down><home>' : '<plug>CmdlineCompletionForward'\r\n\r\n \r\n\r\n","4":"This script let you can use CTRL-P\/N to complete word in cmdline mode\r\n just like in insert mode.\r\n\r\nfor instance :\r\n            1.   :something<C-P>\r\n            2.   \/else<C-N>\r\n      \r\nyou also can map other keys instead of <C-P\/N> like this in your vimrc: \r\n            cmap <C-J> <Plug>CmdlineCompletionBackward\r\n            cmap <C-K> <Plug>CmdlineCompletionForward\r\n\r\nOr,  you may wanna keep compatiable recent history when using <C-P\/N> , try this: ( Thanks for Enno.Nagel's good idea ) .\r\n            cmap <expr> <c-p> getcmdpos() == 1 ? '<up><home>' : '<plug>CmdlineCompletionBackward'\r\n            cmap <expr> <c-n> getcmdpos() == 1 ? '<down><home>' : '<plug>CmdlineCompletionForward'\r\n\r\n \r\n\r\n","install_details":"Drag this file into vim plugin directory ( ~\/.vim\/plugin) \r\n","5":"Drag this file into vim plugin directory ( ~\/.vim\/plugin) \r\n","first_name":"jinhu","6":"jinhu","last_name":"lu","7":"lu","releases":[{"0":"3531","vim_version":"7.0","1":"7.0","script_version":"0.04","2":"0.04","version_comment":"Add completion search in loaded buffers support . ","3":"Add completion search in loaded buffers support . ","package":"cmdline_completion.vim","4":"cmdline_completion.vim","src_id":"18931","5":"18931","creation_date":"1351697690","6":"1351697690"},{"0":"3531","vim_version":"7.0","1":"7.0","script_version":"0.03","2":"0.03","version_comment":"add completion support cursor at anywhere of cmdline.","3":"add completion support cursor at anywhere of cmdline.","package":"cmdline_completion.vim","4":"cmdline_completion.vim","src_id":"17565","5":"17565","creation_date":"1330957438","6":"1330957438"},{"0":"3531","vim_version":"7.0","1":"7.0","script_version":"0.02","2":"0.02","version_comment":"change s:vars to b:vars to avoid dead loop when continue searching in another  buffer  , and dos2unix .","3":"change s:vars to b:vars to avoid dead loop when continue searching in another  buffer  , and dos2unix .","package":"cmdline_completion.vim","4":"cmdline_completion.vim","src_id":"15454","5":"15454","creation_date":"1302880599","6":"1302880599"},{"0":"3531","vim_version":"7.0","1":"7.0","script_version":"0.01","2":"0.01","version_comment":"Initial upload","3":"Initial upload","package":"cmdline_completion.vim","4":"cmdline_completion.vim","src_id":"15340","5":"15340","creation_date":"1301502845","6":"1301502845"}]},"3530":{"script_id":"3530","0":"3530","script_name":"mush.vim","1":"mush.vim","script_type":"syntax","2":"syntax","summary":"syntax file for MUSH and MUX Code","3":"syntax file for MUSH and MUX Code","description":"This syntax file MUSHCode andd MUXCode.   Instructions for making it work are in the file.\r\n\r\nThis syntax file is more or less a more updated version of the mush.vim syntax file I last contributed in 2005.","4":"This syntax file MUSHCode andd MUXCode.   Instructions for making it work are in the file.\r\n\r\nThis syntax file is more or less a more updated version of the mush.vim syntax file I last contributed in 2005.","install_details":"Install mush.vim in your syntax vimruntime directory.  \r\n\r\nEdit filetype.vim in your vim runtime directory and add\r\nau BufNewFile,BufRead *.mush,*.mux                    setf mush\r\n\r\nIf you have the previous version of mush.vim which you most likely do.  All you need to do after replacing the mush.vim in the syntax directory is updating the \r\nline in filetype.vim to include *.mux as well.  *.mux is a common suffix to MUSHCode files just as *.mush is.","5":"Install mush.vim in your syntax vimruntime directory.  \r\n\r\nEdit filetype.vim in your vim runtime directory and add\r\nau BufNewFile,BufRead *.mush,*.mux                    setf mush\r\n\r\nIf you have the previous version of mush.vim which you most likely do.  All you need to do after replacing the mush.vim in the syntax directory is updating the \r\nline in filetype.vim to include *.mux as well.  *.mux is a common suffix to MUSHCode files just as *.mush is.","first_name":"Rick","6":"Rick","last_name":"Bird","7":"Bird","releases":[{"0":"3530","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"mush.vim","4":"mush.vim","src_id":"15333","5":"15333","creation_date":"1301422612","6":"1301422612"}]},"3529":{"script_id":"3529","0":"3529","script_name":"Distinguished","1":"Distinguished","script_type":"color scheme","2":"color scheme","summary":"A dark vim color scheme for 256-color terminals.","3":"A dark vim color scheme for 256-color terminals.","description":"This color scheme requires a 256-color terminal.\r\n\r\nScreenshot (PHP): http:\/\/oi53.tinypic.com\/22c40n.jpg\r\n\r\nCheck out my GitHub repo for the latest updates:  https:\/\/github.com\/Lokaltog\/vim-distinguished\r\n\r\nFull vim configuration available at: https:\/\/github.com\/Lokaltog\/sync.","4":"This color scheme requires a 256-color terminal.\r\n\r\nScreenshot (PHP): http:\/\/oi53.tinypic.com\/22c40n.jpg\r\n\r\nCheck out my GitHub repo for the latest updates:  https:\/\/github.com\/Lokaltog\/vim-distinguished\r\n\r\nFull vim configuration available at: https:\/\/github.com\/Lokaltog\/sync.","install_details":"","5":"","first_name":"Kim","6":"Kim","last_name":"Silkeb\u00c3\u00a6kken","7":"Silkeb\u00c3\u00a6kken","releases":[{"0":"3529","vim_version":"7.2","1":"7.2","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"Lokaltog-vim-distinguished-1.0-0-gc786fb0.zip","4":"Lokaltog-vim-distinguished-1.0-0-gc786fb0.zip","src_id":"15326","5":"15326","creation_date":"1301401823","6":"1301401823"}]},"3528":{"script_id":"3528","0":"3528","script_name":"ciscoacl.vim","1":"ciscoacl.vim","script_type":"syntax","2":"syntax","summary":"Cisco ACL syntax highlighting","3":"Cisco ACL syntax highlighting","description":"This syntax highlighting script it is based on http:\/\/www.vim.org\/scripts\/script.php?script_id=1141 by Vladimir Kotal.\r\nI've added many more keywords and ipv6 support.","4":"This syntax highlighting script it is based on http:\/\/www.vim.org\/scripts\/script.php?script_id=1141 by Vladimir Kotal.\r\nI've added many more keywords and ipv6 support.","install_details":"copy ciscoacl.vim to your ~\/.vim\/syntax directory and add following lines to your ~\/.vimrc file:\r\n\r\naugroup filetype\r\n        au! BufRead,BufNewFile *.crules     set filetype=ciscoacl\r\n        au! BufRead,BufNewFile *.acl        set filetype=ciscoacl\r\naugroup END","5":"copy ciscoacl.vim to your ~\/.vim\/syntax directory and add following lines to your ~\/.vimrc file:\r\n\r\naugroup filetype\r\n        au! BufRead,BufNewFile *.crules     set filetype=ciscoacl\r\n        au! BufRead,BufNewFile *.acl        set filetype=ciscoacl\r\naugroup END","first_name":"Marcos","6":"Marcos","last_name":"Manoni","7":"Manoni","releases":[{"0":"3528","vim_version":"6.0","1":"6.0","script_version":"0.2","2":"0.2","version_comment":"Initial upload","3":"Initial upload","package":"ciscoacl.vim","4":"ciscoacl.vim","src_id":"15316","5":"15316","creation_date":"1301338619","6":"1301338619"}]},"3527":{"script_id":"3527","0":"3527","script_name":"boost.vim","1":"boost.vim","script_type":"utility","2":"utility","summary":"Load templates for new files","3":"Load templates for new files","description":"Vim plugin for creating new files from templates.\r\nBased on Aristotle Pagaltzis <pagaltis@gmz.de> template script.\r\nhttp:\/\/www.vim.org\/scripts\/script.php?script_id=1172\r\n\r\nModified to use .tpl extensions and a filetype definition at the top of the template. The script is no longer automatically executed for a new buffer. \r\n\r\nIn order to tell Vim to use the correct filetype for editing, you must place the following text on the first line of the template:\r\n\r\n# filetype: xhtml\r\n\r\nThis will cause the vim filetype to be set to whatever filetype is specified after the colon (xhtml in this case). The filetype definition will then be removed from the newly created buffer.\r\n\r\nYou can still set the initial curser position in the template as per Aristotle's original script.\r\n \r\nTo load a template use the 'Boost' command followed by the template name (without the .tpl suffix).\r\n\r\nFor example:\r\n:Boost html (loads the html.tpl template into the current buffer)\r\n:Boost html-strict (loads the html-strict.tpl template into the current buffer)\r\n:Boost bash (loads the bash.tpl template into the current buffer)\r\n:Boost mytemplate (loads the mytemplate.tpl template into the current buffer)","4":"Vim plugin for creating new files from templates.\r\nBased on Aristotle Pagaltzis <pagaltis@gmz.de> template script.\r\nhttp:\/\/www.vim.org\/scripts\/script.php?script_id=1172\r\n\r\nModified to use .tpl extensions and a filetype definition at the top of the template. The script is no longer automatically executed for a new buffer. \r\n\r\nIn order to tell Vim to use the correct filetype for editing, you must place the following text on the first line of the template:\r\n\r\n# filetype: xhtml\r\n\r\nThis will cause the vim filetype to be set to whatever filetype is specified after the colon (xhtml in this case). The filetype definition will then be removed from the newly created buffer.\r\n\r\nYou can still set the initial curser position in the template as per Aristotle's original script.\r\n \r\nTo load a template use the 'Boost' command followed by the template name (without the .tpl suffix).\r\n\r\nFor example:\r\n:Boost html (loads the html.tpl template into the current buffer)\r\n:Boost html-strict (loads the html-strict.tpl template into the current buffer)\r\n:Boost bash (loads the bash.tpl template into the current buffer)\r\n:Boost mytemplate (loads the mytemplate.tpl template into the current buffer)","install_details":"Place boost.vim in your Vim plugins directory.\r\n\r\nThen create a 'templates' directory in your .vim directory and place your .tpl templates here. For example a bash.tpl template, or a css.tpl, or any file that you would like to load as a template - as long as it ends in .tpl.\r\n \r\nThere are sample templates included in the zip file.\r\n\r\nOr you can download\/clone the plugin from the source repository on github at https:\/\/github.com\/58bits\/boost","5":"Place boost.vim in your Vim plugins directory.\r\n\r\nThen create a 'templates' directory in your .vim directory and place your .tpl templates here. For example a bash.tpl template, or a css.tpl, or any file that you would like to load as a template - as long as it ends in .tpl.\r\n \r\nThere are sample templates included in the zip file.\r\n\r\nOr you can download\/clone the plugin from the source repository on github at https:\/\/github.com\/58bits\/boost","first_name":"Anthony","6":"Anthony","last_name":"Bouch","7":"Bouch","releases":[{"0":"3527","vim_version":"7.2","1":"7.2","script_version":"1.0.1","2":"1.0.1","version_comment":"Initial upload","3":"Initial upload","package":"boost.zip","4":"boost.zip","src_id":"15315","5":"15315","creation_date":"1301333234","6":"1301333234"}]},"3526":{"script_id":"3526","0":"3526","script_name":"EasyMotion","1":"EasyMotion","script_type":"utility","2":"utility","summary":"Vim motions on speed!","3":"Vim motions on speed!","description":"EasyMotion provides a much simpler way to use some motions in vim. It takes the <number> out of <number>w or <number>f{char} by highlighting all possible choices and allowing you to press one key to jump directly to the target.\r\n\r\nWhen one of the available motions is triggered, all visible text preceding or following the cursor is faded, and motion targets are highlighted.\r\n\r\n* Animated demo: http:\/\/oi54.tinypic.com\/2yysefm.jpg\r\n* Video tutorial on Nettuts+: http:\/\/net.tutsplus.com\/tutorials\/other\/vim-essential-plugin-easymotion\/\r\n\r\n\r\nIMPORTANT NOTES ABOUT THE DEFAULT BINDINGS\r\n\r\nThe default leader has been changed to <Leader><Leader> to avoid conflicts with other plugins you may have installed. This can easily be changed back to pre-1.3 behavior by rebinding the leader in your vimrc:\r\n\r\n    let g:EasyMotion_leader_key = '<Leader>'\r\n\r\nAll motions are now triggered with <Leader><Leader> by default, e.g. <Leader><Leader>t, <Leader><Leader>gE.\r\n\r\n\r\nUSAGE EXAMPLE\r\n\r\nType <Leader><Leader>w to trigger the word motion w. When the motion is triggered, the text is updated (no braces are actually added, the text is highlighted in red by default):\r\n\r\n    <cursor>Lorem {a}psum {b}olor {c}it {d}met.\r\n\r\nPress \"c\" to jump to the beginning of the word \"sit\":\r\n\r\n    Lorem ipsum dolor <cursor>sit amet.\r\n\r\n\r\n* Check out the GitHub repo for the latest updates: http:\/\/git.io\/EM\r\n* Please report any issues here: https:\/\/github.com\/Lokaltog\/vim-easymotion\/issues","4":"EasyMotion provides a much simpler way to use some motions in vim. It takes the <number> out of <number>w or <number>f{char} by highlighting all possible choices and allowing you to press one key to jump directly to the target.\r\n\r\nWhen one of the available motions is triggered, all visible text preceding or following the cursor is faded, and motion targets are highlighted.\r\n\r\n* Animated demo: http:\/\/oi54.tinypic.com\/2yysefm.jpg\r\n* Video tutorial on Nettuts+: http:\/\/net.tutsplus.com\/tutorials\/other\/vim-essential-plugin-easymotion\/\r\n\r\n\r\nIMPORTANT NOTES ABOUT THE DEFAULT BINDINGS\r\n\r\nThe default leader has been changed to <Leader><Leader> to avoid conflicts with other plugins you may have installed. This can easily be changed back to pre-1.3 behavior by rebinding the leader in your vimrc:\r\n\r\n    let g:EasyMotion_leader_key = '<Leader>'\r\n\r\nAll motions are now triggered with <Leader><Leader> by default, e.g. <Leader><Leader>t, <Leader><Leader>gE.\r\n\r\n\r\nUSAGE EXAMPLE\r\n\r\nType <Leader><Leader>w to trigger the word motion w. When the motion is triggered, the text is updated (no braces are actually added, the text is highlighted in red by default):\r\n\r\n    <cursor>Lorem {a}psum {b}olor {c}it {d}met.\r\n\r\nPress \"c\" to jump to the beginning of the word \"sit\":\r\n\r\n    Lorem ipsum dolor <cursor>sit amet.\r\n\r\n\r\n* Check out the GitHub repo for the latest updates: http:\/\/git.io\/EM\r\n* Please report any issues here: https:\/\/github.com\/Lokaltog\/vim-easymotion\/issues","install_details":"Extract and move contents to your .vim folder.\r\n\r\nPathogen users: Clone git:\/\/github.com\/Lokaltog\/vim-easymotion.git into your bundle folder.","5":"Extract and move contents to your .vim folder.\r\n\r\nPathogen users: Clone git:\/\/github.com\/Lokaltog\/vim-easymotion.git into your bundle folder.","first_name":"Kim","6":"Kim","last_name":"Silkeb\u00c3\u00a6kken","7":"Silkeb\u00c3\u00a6kken","releases":[{"0":"3526","vim_version":"7.2","1":"7.2","script_version":"1.3","2":"1.3","version_comment":"IMPORTANT NOTE: Default leader has been changed to <Leader><Leader> to avoid conflicts with other plugins. Various bugfixes and improvements.","3":"IMPORTANT NOTE: Default leader has been changed to <Leader><Leader> to avoid conflicts with other plugins. Various bugfixes and improvements.","package":"Lokaltog-vim-easymotion-1.3-0-g667a668.zip","4":"Lokaltog-vim-easymotion-1.3-0-g667a668.zip","src_id":"16838","5":"16838","creation_date":"1320827307","6":"1320827307"},{"0":"3526","vim_version":"7.2","1":"7.2","script_version":"1.2","2":"1.2","version_comment":"WORD motions. Customizable key mappings. Configurable leader key. Improved default grouping algorithm. Easier to apply custom highlighting. No more jumping on j\/k motions. Various bug fixes.","3":"WORD motions. Customizable key mappings. Configurable leader key. Improved default grouping algorithm. Easier to apply custom highlighting. No more jumping on j\/k motions. Various bug fixes.","package":"Lokaltog-vim-easymotion-1.2-0-gdfb8079.zip","4":"Lokaltog-vim-easymotion-1.2-0-gdfb8079.zip","src_id":"15369","5":"15369","creation_date":"1301845833","6":"1301845833"},{"0":"3526","vim_version":"7.2","1":"7.2","script_version":"1.1.0.1","2":"1.1.0.1","version_comment":"EasyMotion now works in operator-pending mode as well. Summary of features: Normal, visual and operator-pending mode mappings for the following motions: f - F - t - T - w - b - e - ge - j - k.","3":"EasyMotion now works in operator-pending mode as well. Summary of features: Normal, visual and operator-pending mode mappings for the following motions: f - F - t - T - w - b - e - ge - j - k.","package":"Lokaltog-vim-easymotion-1.1.0.1-0-g7c6cff7.zip","4":"Lokaltog-vim-easymotion-1.1.0.1-0-g7c6cff7.zip","src_id":"15345","5":"15345","creation_date":"1301602119","6":"1301602119"},{"0":"3526","vim_version":"7.2","1":"7.2","script_version":"1.0.12.1","2":"1.0.12.1","version_comment":"Updated docs. Fixed missing target\/shade highlighting issue. Fixed GUI bugs.","3":"Updated docs. Fixed missing target\/shade highlighting issue. Fixed GUI bugs.","package":"Lokaltog-vim-easymotion-1.0.12.1-0-gce13b9a.zip","4":"Lokaltog-vim-easymotion-1.0.12.1-0-gce13b9a.zip","src_id":"15343","5":"15343","creation_date":"1301578976","6":"1301578976"},{"0":"3526","vim_version":"7.2","1":"7.2","script_version":"1.0.10","2":"1.0.10","version_comment":"New motions: ge, j, k.","3":"New motions: ge, j, k.","package":"Lokaltog-vim-easymotion-1.0.10-0-g5809794.zip","4":"Lokaltog-vim-easymotion-1.0.10-0-g5809794.zip","src_id":"15341","5":"15341","creation_date":"1301505110","6":"1301505110"},{"0":"3526","vim_version":"7.2","1":"7.2","script_version":"1.0.8","2":"1.0.8","version_comment":"Various code improvements.","3":"Various code improvements.","package":"Lokaltog-vim-easymotion-1.0.8-0-g24c9f6c.zip","4":"Lokaltog-vim-easymotion-1.0.8-0-g24c9f6c.zip","src_id":"15339","5":"15339","creation_date":"1301485553","6":"1301485553"},{"0":"3526","vim_version":"7.2","1":"7.2","script_version":"1.0.6","2":"1.0.6","version_comment":"Code improvements. Various bug fixes. Updated source location.","3":"Code improvements. Various bug fixes. Updated source location.","package":"Lokaltog-vim-easymotion-1.0.6-0-gc58f0b7.zip","4":"Lokaltog-vim-easymotion-1.0.6-0-gc58f0b7.zip","src_id":"15324","5":"15324","creation_date":"1301400829","6":"1301400829"}]},"3525":{"script_id":"3525","0":"3525","script_name":"Rename","1":"Rename","script_type":"utility","2":"utility","summary":"Replaces instances of current word or selection","3":"Replaces instances of current word or selection","description":"Two modes -\r\n\r\nNormal: Replace all instances of the word under the cursor in the current file.\r\nVisual: Replace all instances of the current selection in the current file.\r\n\r\nUsage -\r\n\r\n<Leader><Leader>r\r\n\r\nI may make the usage more general in the future, but it should be very easy to change this mapping in the script if you need to for now.\r\n\r\nHistory -\r\n\r\nI couldn't find a 'dumb' find and replace plugin. All the plugins I came across were function-aware, etc. This is great if you're using C, however, sometimes you just want to change some text.","4":"Two modes -\r\n\r\nNormal: Replace all instances of the word under the cursor in the current file.\r\nVisual: Replace all instances of the current selection in the current file.\r\n\r\nUsage -\r\n\r\n<Leader><Leader>r\r\n\r\nI may make the usage more general in the future, but it should be very easy to change this mapping in the script if you need to for now.\r\n\r\nHistory -\r\n\r\nI couldn't find a 'dumb' find and replace plugin. All the plugins I came across were function-aware, etc. This is great if you're using C, however, sometimes you just want to change some text.","install_details":"Place in your plugin directory.","5":"Place in your plugin directory.","first_name":"Lyndon","6":"Lyndon","last_name":"Maydwell","7":"Maydwell","releases":[{"0":"3525","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"rename.vim","4":"rename.vim","src_id":"15310","5":"15310","creation_date":"1301283452","6":"1301283452"}]},"3524":{"script_id":"3524","0":"3524","script_name":"vim-scala","1":"vim-scala","script_type":"ftplugin","2":"ftplugin","summary":"Vim support for writing Scala code.","3":"Vim support for writing Scala code.","description":"This script is a fork of the code that came with Scala for Vim.  The syntax code was pretty good but the indent code was pretty bad; this is better.  It's not perfect... it's better :)","4":"This script is a fork of the code that came with Scala for Vim.  The syntax code was pretty good but the indent code was pretty bad; this is better.  It's not perfect... it's better :)","install_details":"The plugin is at https:\/\/github.com\/derekwyatt\/vim-scala\r\n\r\nEither go there and click \"Download\" or use 'git' to get it as you normally would with 'git'.  Please enhance \/ fix if you can.\r\n\r\nYou should be using 'pathogen' to manage you Vim plugins; if you're not, put that in first :)  Then copy 'vim-scala' to ~\/.vim\/bundle and restart Vim.","5":"The plugin is at https:\/\/github.com\/derekwyatt\/vim-scala\r\n\r\nEither go there and click \"Download\" or use 'git' to get it as you normally would with 'git'.  Please enhance \/ fix if you can.\r\n\r\nYou should be using 'pathogen' to manage you Vim plugins; if you're not, put that in first :)  Then copy 'vim-scala' to ~\/.vim\/bundle and restart Vim.","first_name":"Derek","6":"Derek","last_name":"Wyatt","7":"Wyatt","releases":[{"0":"3524","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"vim-scala_README.txt","4":"vim-scala_README.txt","src_id":"15307","5":"15307","creation_date":"1301253054","6":"1301253054"}]},"3523":{"script_id":"3523","0":"3523","script_name":"gem.vim","1":"gem.vim","script_type":"utility","2":"utility","summary":"a project helper for ruby gem\/libraray development","3":"a project helper for ruby gem\/libraray development","description":"easy navigation in gem directory. have :R :Rl :Rs command, and :A alternative for quich switch between lib and spec file. It works with rag(see resources). for more information please see Documentation\r\n\r\nGitHub: http:\/\/github.com\/GutenYe\/gem.vim\r\nLicense: MIT-LICENSE\r\nDocumentation: doc\/gem.txt","4":"easy navigation in gem directory. have :R :Rl :Rs command, and :A alternative for quich switch between lib and spec file. It works with rag(see resources). for more information please see Documentation\r\n\r\nGitHub: http:\/\/github.com\/GutenYe\/gem.vim\r\nLicense: MIT-LICENSE\r\nDocumentation: doc\/gem.txt","install_details":"Bundle 'gem.vim' # by vundle","5":"Bundle 'gem.vim' # by vundle","first_name":"Guten","6":"Guten","last_name":"Ye","7":"Ye","releases":[{"0":"3523","vim_version":"7.0","1":"7.0","script_version":"1.0.1","2":"1.0.1","version_comment":"change  to vimball","3":"change  to vimball","package":"gem.vba","4":"gem.vba","src_id":"15292","5":"15292","creation_date":"1301103659","6":"1301103659"},{"0":"3523","vim_version":"7.0","1":"7.0","script_version":"1.0.0","2":"1.0.0","version_comment":"Initial upload","3":"Initial upload","package":"gem.tar.gz","4":"gem.tar.gz","src_id":"15291","5":"15291","creation_date":"1301103242","6":"1301103242"}]},"3522":{"script_id":"3522","0":"3522","script_name":"SAS Syntax","1":"SAS Syntax","script_type":"syntax","2":"syntax","summary":"Syntax Script for SAS 9.1\/9.2\/9.3\/9.4","3":"Syntax Script for SAS 9.1\/9.2\/9.3\/9.4","description":"This script was inspired by the script written by James Kidd.\r\nThe script has since been completely rewritten.\r\n\r\nUpgrade version to 3.0.0. Improvements include:\r\n\r\n- Improve sync speed\r\n- Largely enhance precision\r\n- Update keywords in the latest SAS (as of Mar 2017)\r\n- Add syntaxes for date\/time constants\r\n- Add syntax for data lines\r\n- Add (back) syntax for TODO in comments\r\n\r\nNew feature in 2.1.0\r\n\r\n- Add syntax fold\r\n\r\nMajor improvements in 2.0:\r\n\r\n- Higher precision\r\n- Faster synchronization\r\n- Separate coloring for control statements\r\n- Highlight macro variables in double quoted strings\r\n- Update all keywords based on SAS 9.4\r\n- Add complete SAS\/GRAPH and SAS\/STAT procedure syntaxes\r\n- Add Proc TEMPLATE and GTL syntaxes\r\n- Add complete DS2 syntaxes\r\n- Add basic IML syntaxes\r\n- A lot of other improvements and bug fixes\r\n\r\nImprovements inherited from version 1.0:\r\n\r\n- Add new keywords, including those for ODS and hash object\r\n- Highlight format tags\r\n- Highlight user defined macro functions\r\n- Highlight macro comments\r\n\r\nScreenshot: http:\/\/imgur.com\/QelHtXy\r\n\r\nPlease also check out my SAS indent script: http:\/\/vim.sourceforge.net\/scripts\/script.php?script_id=4034","4":"This script was inspired by the script written by James Kidd.\r\nThe script has since been completely rewritten.\r\n\r\nUpgrade version to 3.0.0. Improvements include:\r\n\r\n- Improve sync speed\r\n- Largely enhance precision\r\n- Update keywords in the latest SAS (as of Mar 2017)\r\n- Add syntaxes for date\/time constants\r\n- Add syntax for data lines\r\n- Add (back) syntax for TODO in comments\r\n\r\nNew feature in 2.1.0\r\n\r\n- Add syntax fold\r\n\r\nMajor improvements in 2.0:\r\n\r\n- Higher precision\r\n- Faster synchronization\r\n- Separate coloring for control statements\r\n- Highlight macro variables in double quoted strings\r\n- Update all keywords based on SAS 9.4\r\n- Add complete SAS\/GRAPH and SAS\/STAT procedure syntaxes\r\n- Add Proc TEMPLATE and GTL syntaxes\r\n- Add complete DS2 syntaxes\r\n- Add basic IML syntaxes\r\n- A lot of other improvements and bug fixes\r\n\r\nImprovements inherited from version 1.0:\r\n\r\n- Add new keywords, including those for ODS and hash object\r\n- Highlight format tags\r\n- Highlight user defined macro functions\r\n- Highlight macro comments\r\n\r\nScreenshot: http:\/\/imgur.com\/QelHtXy\r\n\r\nPlease also check out my SAS indent script: http:\/\/vim.sourceforge.net\/scripts\/script.php?script_id=4034","install_details":"You can simply copy the script file to your ~\/.vim\/syntax\r\n\r\nTo make syntax folding work, you would need to add \"set foldmethod=syntax\" in your vimrc, or \"setlocal foldmethod=syntax\" in your SAS ftplugin script.\r\n\r\nYou can find my SAS ftplugin script from here (along with some other stuffs): https:\/\/github.com\/akanosora\/vimfiles\/tree\/master\/ftplugin","5":"You can simply copy the script file to your ~\/.vim\/syntax\r\n\r\nTo make syntax folding work, you would need to add \"set foldmethod=syntax\" in your vimrc, or \"setlocal foldmethod=syntax\" in your SAS ftplugin script.\r\n\r\nYou can find my SAS ftplugin script from here (along with some other stuffs): https:\/\/github.com\/akanosora\/vimfiles\/tree\/master\/ftplugin","first_name":"Zhenhuan","6":"Zhenhuan","last_name":"Hu","7":"Hu","releases":[{"0":"3522","vim_version":"6.0","1":"6.0","script_version":"3.0.0","2":"3.0.0","version_comment":"Upgrade version number to 3.0. Improvements include:\r\n- Improve sync speed\r\n- Largely enhance precision\r\n- Update keywords in the latest SAS (as of Mar 2017)\r\n- Add syntaxes for date\/time constants\r\n- Add syntax for data lines\r\n- Add (back) syntax for TODO in comments\r\n","3":"Upgrade version number to 3.0. Improvements include:\r\n- Improve sync speed\r\n- Largely enhance precision\r\n- Update keywords in the latest SAS (as of Mar 2017)\r\n- Add syntaxes for date\/time constants\r\n- Add syntax for data lines\r\n- Add (back) syntax for TODO in comments\r\n","package":"sas.vim","4":"sas.vim","src_id":"25023","5":"25023","creation_date":"1489179690","6":"1489179690"},{"0":"3522","vim_version":"6.0","1":"6.0","script_version":"2.1.1","2":"2.1.1","version_comment":"Bug fixes","3":"Bug fixes","package":"sas.vim","4":"sas.vim","src_id":"24954","5":"24954","creation_date":"1486656051","6":"1486656051"},{"0":"3522","vim_version":"6.0","1":"6.0","script_version":"2.0.4","2":"2.0.4","version_comment":"Add highlighting for functions\r\nChange the implementation of syntaxing macro function names so that macro parameters same as SAS keywords won't be highlighted (Thank Joug Raw for the suggestion)\r\nAdd section highlighting:\r\n- Use \/** and **\/ to define a section\r\n- It functions the same as a comment but with different highlighting","3":"Add highlighting for functions\r\nChange the implementation of syntaxing macro function names so that macro parameters same as SAS keywords won't be highlighted (Thank Joug Raw for the suggestion)\r\nAdd section highlighting:\r\n- Use \/** and **\/ to define a section\r\n- It functions the same as a comment but with different highlighting","package":"sas.vim","4":"sas.vim","src_id":"24756","5":"24756","creation_date":"1479744208","6":"1479744208"},{"0":"3522","vim_version":"7.0","1":"7.0","script_version":"2.0.1","2":"2.0.1","version_comment":"Minor code tweaks.","3":"Minor code tweaks.","package":"sas.vim","4":"sas.vim","src_id":"24511","5":"24511","creation_date":"1473263583","6":"1473263583"},{"0":"3522","vim_version":"7.0","1":"7.0","script_version":"2.0","2":"2.0","version_comment":"Major changes so upgrade version number to 2.0\r\nOverhaul the entire script. Improvements include:\r\n- Higher precision\r\n- Faster synchronization\r\n- Separate coloring for control statements\r\n- Hightlight macro variables in double quoted strings\r\n- Update all syntaxes based on SAS 9.4\r\n- Add complete SAS\/GRAPH and SAS\/STAT procedure syntaxes\r\n- Add Proc TEMPLATE and GTL syntaxes\r\n- Add complete DS2 syntaxes\r\n- Add basic IML syntaxes\r\n- Other improvements and bug fixes\r\nDrop support for earlier versions of VIM","3":"Major changes so upgrade version number to 2.0\r\nOverhaul the entire script. Improvements include:\r\n- Higher precision\r\n- Faster synchronization\r\n- Separate coloring for control statements\r\n- Hightlight macro variables in double quoted strings\r\n- Update all syntaxes based on SAS 9.4\r\n- Add complete SAS\/GRAPH and SAS\/STAT procedure syntaxes\r\n- Add Proc TEMPLATE and GTL syntaxes\r\n- Add complete DS2 syntaxes\r\n- Add basic IML syntaxes\r\n- Other improvements and bug fixes\r\nDrop support for earlier versions of VIM","package":"sas.vim","4":"sas.vim","src_id":"24371","5":"24371","creation_date":"1468271855","6":"1468271855"},{"0":"3522","vim_version":"7.0","1":"7.0","script_version":"1.2.5","2":"1.2.5","version_comment":"Added new statement keywords. Updated some keywords to SAS 9.4.","3":"Added new statement keywords. Updated some keywords to SAS 9.4.","package":"sas.vim","4":"sas.vim","src_id":"23107","5":"23107","creation_date":"1427749767","6":"1427749767"},{"0":"3522","vim_version":"7.0","1":"7.0","script_version":"1.2.4","2":"1.2.4","version_comment":"Improved macro comment syntax (macro comments after semicolon is now correctly colored.)","3":"Improved macro comment syntax (macro comments after semicolon is now correctly colored.)","package":"sas.vim","4":"sas.vim","src_id":"22065","5":"22065","creation_date":"1403213842","6":"1403213842"},{"0":"3522","vim_version":"7.0","1":"7.0","script_version":"1.2.3","2":"1.2.3","version_comment":"Minor cosmetic modifications for hash objects\r\nMinor bug fixes for statment syntax","3":"Minor cosmetic modifications for hash objects\r\nMinor bug fixes for statment syntax","package":"sas.vim","4":"sas.vim","src_id":"20565","5":"20565","creation_date":"1374783526","6":"1374783526"},{"0":"3522","vim_version":"7.0","1":"7.0","script_version":"1.2.2","2":"1.2.2","version_comment":"Fixed minor bugs.","3":"Fixed minor bugs.","package":"sas.vim","4":"sas.vim","src_id":"17825","5":"17825","creation_date":"1335476350","6":"1335476350"},{"0":"3522","vim_version":"7.0","1":"7.0","script_version":"1.2.1","2":"1.2.1","version_comment":"Added syntax for macro comment","3":"Added syntax for macro comment","package":"sas.vim","4":"sas.vim","src_id":"17686","5":"17686","creation_date":"1332966885","6":"1332966885"},{"0":"3522","vim_version":"7.0","1":"7.0","script_version":"1.2","2":"1.2","version_comment":"Completely rewrote approach for highlighting SAS statements \r\nUpdated new statements in Base SAS 9.3 and SAS\/Stat\r\nFixed glitches in highlighting procedure names and internal variables.\r\nSimplify the approach for highlighting SAS functions\r\nAdded highlighting for hash and hiter objects","3":"Completely rewrote approach for highlighting SAS statements \r\nUpdated new statements in Base SAS 9.3 and SAS\/Stat\r\nFixed glitches in highlighting procedure names and internal variables.\r\nSimplify the approach for highlighting SAS functions\r\nAdded highlighting for hash and hiter objects","package":"sas.vim","4":"sas.vim","src_id":"17544","5":"17544","creation_date":"1330455858","6":"1330455858"},{"0":"3522","vim_version":"7.0","1":"7.0","script_version":"1.1","2":"1.1","version_comment":"Added more keywords in SAS 9.1.","3":"Added more keywords in SAS 9.1.","package":"sas.vim","4":"sas.vim","src_id":"15626","5":"15626","creation_date":"1305141529","6":"1305141529"},{"0":"3522","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"sas.vim","4":"sas.vim","src_id":"15290","5":"15290","creation_date":"1301091246","6":"1301091246"}]},"3521":{"script_id":"3521","0":"3521","script_name":"Gravity","1":"Gravity","script_type":"color scheme","2":"color scheme","summary":"Light color scheme designed to be very readable, clean and professional.","3":"Light color scheme designed to be very readable, clean and professional.","description":"Gravity is a theme that was designed to be very readable, clean and professional. It is a light color scheme that is very slightly off-white to be easier on the eyes. Syntax elements are easy to read and distinguish, in particular constant values (strings and numbers) stand out in red.\r\n\r\nAll important screenshots can be found at: http:\/\/www.gregsexton.org\/vim-color-schemes\/gravity-color\/ \r\n\r\nItalics are not used in this theme. \r\n\r\nCurrently Gravity is GVim only.\r\n\r\nThere is now a GitHub repository for Gravity at: https:\/\/github.com\/gregsexton\/Gravity","4":"Gravity is a theme that was designed to be very readable, clean and professional. It is a light color scheme that is very slightly off-white to be easier on the eyes. Syntax elements are easy to read and distinguish, in particular constant values (strings and numbers) stand out in red.\r\n\r\nAll important screenshots can be found at: http:\/\/www.gregsexton.org\/vim-color-schemes\/gravity-color\/ \r\n\r\nItalics are not used in this theme. \r\n\r\nCurrently Gravity is GVim only.\r\n\r\nThere is now a GitHub repository for Gravity at: https:\/\/github.com\/gregsexton\/Gravity","install_details":"Just drop in to your ~\/.vim\/colors directory or ~\/vimfiles\/colors if on Windows.","5":"Just drop in to your ~\/.vim\/colors directory or ~\/vimfiles\/colors if on Windows.","first_name":"Greg","6":"Greg","last_name":"Sexton","7":"Sexton","releases":[{"0":"3521","vim_version":"5.7","1":"5.7","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"gravity.vim","4":"gravity.vim","src_id":"15286","5":"15286","creation_date":"1301000315","6":"1301000315"}]},"3520":{"script_id":"3520","0":"3520","script_name":"Solarized","1":"Solarized","script_type":"color scheme","2":"color scheme","summary":"Beautiful dual light\/dark, selective contrast, GUI\/256\/16 colorscheme","3":"Beautiful dual light\/dark, selective contrast, GUI\/256\/16 colorscheme","description":"Screenshots and details at http:\/\/ethanschoonover.com\/solarized (includes Solarized for other applications including mutt, terminal emulators).\r\n\r\nCan also be cloned from github at https:\/\/github.com\/altercation\/vim-colors-solarized for use with Pathogen, Vundle, etc.\r\n\r\n* * *\r\n\r\nSolarized is a beautiful, carefully designed 16 color, selective contrast colorscheme with both *light* and *dark* modes. It supports GUI full color, 256 color terminal mode and 16 color terminal mode (use Solarized terminal colorschemes with the latter for optimal results; see project homepage above).\r\n\r\nIt has been built on a foundation of eight monotones with precise CIELAB lightness relations. These monotones relations are symmetric, allowing for use in light and dark modes with\u00c2\u00a0identical readability.","4":"Screenshots and details at http:\/\/ethanschoonover.com\/solarized (includes Solarized for other applications including mutt, terminal emulators).\r\n\r\nCan also be cloned from github at https:\/\/github.com\/altercation\/vim-colors-solarized for use with Pathogen, Vundle, etc.\r\n\r\n* * *\r\n\r\nSolarized is a beautiful, carefully designed 16 color, selective contrast colorscheme with both *light* and *dark* modes. It supports GUI full color, 256 color terminal mode and 16 color terminal mode (use Solarized terminal colorschemes with the latter for optimal results; see project homepage above).\r\n\r\nIt has been built on a foundation of eight monotones with precise CIELAB lightness relations. These monotones relations are symmetric, allowing for use in light and dark modes with\u00c2\u00a0identical readability.","install_details":"See the README in the script download for installation details and utility scripts for your .vimrc.\r\n\r\nFor the impatient without customized vim setups: drop solarized.vim into your ~\/.vim\/colors directory.","5":"See the README in the script download for installation details and utility scripts for your .vimrc.\r\n\r\nFor the impatient without customized vim setups: drop solarized.vim into your ~\/.vim\/colors directory.","first_name":"Ethan","6":"Ethan","last_name":"Schoonover","7":"Schoonover","releases":[{"0":"3520","vim_version":"7.3","1":"7.3","script_version":"1.0.0b1","2":"1.0.0b1","version_comment":"Initial upload","3":"Initial upload","package":"vim-colors-solarized-v1.0.0beta1.zip","4":"vim-colors-solarized-v1.0.0beta1.zip","src_id":"15285","5":"15285","creation_date":"1300993790","6":"1300993790"}]},"3518":{"script_id":"3518","0":"3518","script_name":"accentuate.vim","1":"accentuate.vim","script_type":"utility","2":"utility","summary":"Vim plugin that transforms text with the Accentuate.us web service","3":"Vim plugin that transforms text with the Accentuate.us web service","description":"Accentuate is a Vim plugin that uses the Accentuate.us web service to restore\r\naccents and special characters to text in over a hundred languages.\r\n\r\nSee doc\/accentuate.txt in accentuate.zip for detailed documentation.\r\n\r\nThis plugin is also available on github: https:\/\/github.com\/wnodom\/vim-accentuate\r\n","4":"Accentuate is a Vim plugin that uses the Accentuate.us web service to restore\r\naccents and special characters to text in over a hundred languages.\r\n\r\nSee doc\/accentuate.txt in accentuate.zip for detailed documentation.\r\n\r\nThis plugin is also available on github: https:\/\/github.com\/wnodom\/vim-accentuate\r\n","install_details":"See doc\/accentuate.txt for installation instructions.","5":"See doc\/accentuate.txt for installation instructions.","first_name":"Bill","6":"Bill","last_name":"Odom","7":"Odom","releases":[{"0":"3518","vim_version":"7.2","1":"7.2","script_version":"1.1","2":"1.1","version_comment":"Initial upload","3":"Initial upload","package":"accentuate.zip","4":"accentuate.zip","src_id":"15278","5":"15278","creation_date":"1300857433","6":"1300857433"}]},"3517":{"script_id":"3517","0":"3517","script_name":"iconv","1":"iconv","script_type":"utility","2":"utility","summary":"iconv() function","3":"iconv() function","description":"iconv() function written in VimL.\r\n\r\nLatest source: https:\/\/github.com\/ynkdir\/vim-iconv","4":"iconv() function written in VimL.\r\n\r\nLatest source: https:\/\/github.com\/ynkdir\/vim-iconv","install_details":"","5":"","first_name":"Yukihiro","6":"Yukihiro","last_name":"Nakadaira","7":"Nakadaira","releases":[{"0":"3517","vim_version":"7.3","1":"7.3","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"vim-iconv.zip","4":"vim-iconv.zip","src_id":"15276","5":"15276","creation_date":"1300803924","6":"1300803924"}]},"3516":{"script_id":"3516","0":"3516","script_name":"avr8bit.vim","1":"avr8bit.vim","script_type":"syntax","2":"syntax","summary":"Assembler Syntax highlighting for Atmel AVR 8bit Microcontroller","3":"Assembler Syntax highlighting for Atmel AVR 8bit Microcontroller","description":"Syntax highlighting for Atmel 8bit MCU \r\nfor M8, M16, , M48, M88, M162, M168, M328, 4434, M8535, M8515 \r\nM164, M324, M644, M1284, M165, M325, M3250, M645, M6450\r\nM32, M64, M128, M640, M1280, M1281, M2560, M2561\r\nTiny10, Tiny11, Tiny12, Tiny13, Tiny15, Tiny26, Tiny24, Tiny44, Tiny84, Tiny2313\r\nTiny25, Tiny45, Tiny85, Tiny261, Tiny461, Tiny861, Tiny22","4":"Syntax highlighting for Atmel 8bit MCU \r\nfor M8, M16, , M48, M88, M162, M168, M328, 4434, M8535, M8515 \r\nM164, M324, M644, M1284, M165, M325, M3250, M645, M6450\r\nM32, M64, M128, M640, M1280, M1281, M2560, M2561\r\nTiny10, Tiny11, Tiny12, Tiny13, Tiny15, Tiny26, Tiny24, Tiny44, Tiny84, Tiny2313\r\nTiny25, Tiny45, Tiny85, Tiny261, Tiny461, Tiny861, Tiny22","install_details":"copy this File:    ~\/.vim\/syntax \r\nand open a Assemblerfile:  vim xyz.asm \r\nand activate:  :set syntax=avr8bit","5":"copy this File:    ~\/.vim\/syntax \r\nand open a Assemblerfile:  vim xyz.asm \r\nand activate:  :set syntax=avr8bit","first_name":"Alfred","6":"Alfred","last_name":"Hell","7":"Hell","releases":[{"0":"3516","vim_version":"7.0","1":"7.0","script_version":"1.31","2":"1.31","version_comment":"Bugfix (decNumber) Thanks John","3":"Bugfix (decNumber) Thanks John","package":"avr8bit.vim","4":"avr8bit.vim","src_id":"24870","5":"24870","creation_date":"1483260757","6":"1483260757"},{"0":"3516","vim_version":"7.0","1":"7.0","script_version":"1.3","2":"1.3","version_comment":"Added Keywords XYZ(+-)","3":"Added Keywords XYZ(+-)","package":"avr8bit.vim","4":"avr8bit.vim","src_id":"24797","5":"24797","creation_date":"1481456947","6":"1481456947"},{"0":"3516","vim_version":"7.0","1":"7.0","script_version":"1.21","2":"1.21","version_comment":"Bugfix","3":"Bugfix","package":"avr8bit.vim","4":"avr8bit.vim","src_id":"23243","5":"23243","creation_date":"1430412356","6":"1430412356"}]},"3515":{"script_id":"3515","0":"3515","script_name":"VimOutliner","1":"VimOutliner","script_type":"utility","2":"utility","summary":"Outline processor designed for lightning fast authoring","3":"Outline processor designed for lightning fast authoring","description":"* What is VimOutliner?\r\n\r\nVimOutliner is an outline processor with many of the same features as Grandview, More, Thinktank, Ecco, etc. Features include tree expand\/collapse, tree promotion\/demotion, level sensitive colors, interoutline linking, and body text.\r\n\r\nWhat sets VimOutliner apart from the rest is that it\\'s been constructed from the ground up for fast and easy authoring.  Keystrokes are quick and easy, especially for someone knowing the Vim editor. The mouse is completely unnecessary (but is supported to the extent that Vim supports the mouse). Many of the VimOutliner commands start with a double comma because that\\'s very quick to type.\r\n\r\nMany of the VimOutliner commands start with a double comma \",,\" because that's very quick to type. All VimOutliner files have the \".otl\" extension. For an overview of the VimOutliner commands you can type \":h vo_cheatsheet\" when you have opened an otl file. For help on VimOutliner type \":h vo\"\r\n\r\n* Usage\r\n\r\nVimOutliner has been reported to help with the following tasks:\r\n  - Project managment.\r\n  - Password wallet \r\n  - To-do lists.\r\n  - Account and cash book.\r\n  - \\'Plot device\\' for writing novels.\r\n  - Inventory control.\r\n  - Hierarchical database.\r\n  - Web site managment.\r\n\r\n* Characteristics\r\n\r\n  - Fast.\r\n  - Extensible through plugins.\r\n  - Many post-processing scripts allow exporting to multiple formats.\r\n  - Extensive documentation.","4":"* What is VimOutliner?\r\n\r\nVimOutliner is an outline processor with many of the same features as Grandview, More, Thinktank, Ecco, etc. Features include tree expand\/collapse, tree promotion\/demotion, level sensitive colors, interoutline linking, and body text.\r\n\r\nWhat sets VimOutliner apart from the rest is that it\\'s been constructed from the ground up for fast and easy authoring.  Keystrokes are quick and easy, especially for someone knowing the Vim editor. The mouse is completely unnecessary (but is supported to the extent that Vim supports the mouse). Many of the VimOutliner commands start with a double comma because that\\'s very quick to type.\r\n\r\nMany of the VimOutliner commands start with a double comma \",,\" because that's very quick to type. All VimOutliner files have the \".otl\" extension. For an overview of the VimOutliner commands you can type \":h vo_cheatsheet\" when you have opened an otl file. For help on VimOutliner type \":h vo\"\r\n\r\n* Usage\r\n\r\nVimOutliner has been reported to help with the following tasks:\r\n  - Project managment.\r\n  - Password wallet \r\n  - To-do lists.\r\n  - Account and cash book.\r\n  - \\'Plot device\\' for writing novels.\r\n  - Inventory control.\r\n  - Hierarchical database.\r\n  - Web site managment.\r\n\r\n* Characteristics\r\n\r\n  - Fast.\r\n  - Extensible through plugins.\r\n  - Many post-processing scripts allow exporting to multiple formats.\r\n  - Extensive documentation.","install_details":"To install from the zip file in this page do the following:\r\n $ unzip vimoutliner-0.4.0..zip\r\n $ cd vimoutliner-0.4.0\r\n $ sh install.sh\r\n\r\nReleases are available here:\r\n\r\nhttps:\/\/github.com\/vimoutliner\/vimoutliner\/releases\r\n\r\nTo install from the gzip archive follow these steps:\r\n\r\n $ tar -xzvf vimoutliner-0.4.0.tgz\r\n $ cd vimoutliner-0.4.0\r\n $ sh install.sh\r\n\r\nOr install by using Pathogen. \r\n\r\ncd ~\/.vim\/bundle && git clone https:\/\/github.com\/vimoutliner\/vimoutliner.git\r\n","5":"To install from the zip file in this page do the following:\r\n $ unzip vimoutliner-0.4.0..zip\r\n $ cd vimoutliner-0.4.0\r\n $ sh install.sh\r\n\r\nReleases are available here:\r\n\r\nhttps:\/\/github.com\/vimoutliner\/vimoutliner\/releases\r\n\r\nTo install from the gzip archive follow these steps:\r\n\r\n $ tar -xzvf vimoutliner-0.4.0.tgz\r\n $ cd vimoutliner-0.4.0\r\n $ sh install.sh\r\n\r\nOr install by using Pathogen. \r\n\r\ncd ~\/.vim\/bundle && git clone https:\/\/github.com\/vimoutliner\/vimoutliner.git\r\n","first_name":"Vim","6":"Vim","last_name":"Outliner","7":"Outliner","releases":[{"0":"3515","vim_version":"7.0","1":"7.0","script_version":"0.4.0","2":"0.4.0","version_comment":"Added a list-based tags feature similar to org-mode\r\nComplete rewrite of the outline math plugin.\r\nAdded colorscheme option to vimoutlinerrc and directory\r\nModified install.sh\r\nAdded VimOutliner icons to the repository.\r\nAdded information on pathogen installation to INSTALL file.x\r\nAdded votl_maketags manpage\r\nBug fixes, corrections and updates","3":"Added a list-based tags feature similar to org-mode\r\nComplete rewrite of the outline math plugin.\r\nAdded colorscheme option to vimoutlinerrc and directory\r\nModified install.sh\r\nAdded VimOutliner icons to the repository.\r\nAdded information on pathogen installation to INSTALL file.x\r\nAdded votl_maketags manpage\r\nBug fixes, corrections and updates","package":"vimoutliner-0.4.0.zip","4":"vimoutliner-0.4.0.zip","src_id":"22551","5":"22551","creation_date":"1413858634","6":"1413858634"},{"0":"3515","vim_version":"7.0","1":"7.0","script_version":"0.3.7","2":"0.3.7","version_comment":"This update of VimOutliner adds new plugins and scripts. Cleanup of code, bug fixes, and corrections of documentation. Faster checkboxes and more optimization.","3":"This update of VimOutliner adds new plugins and scripts. Cleanup of code, bug fixes, and corrections of documentation. Faster checkboxes and more optimization.","package":"vimoutliner-0.3.7.zip","4":"vimoutliner-0.3.7.zip","src_id":"21816","5":"21816","creation_date":"1398276716","6":"1398276716"},{"0":"3515","vim_version":"7.0","1":"7.0","script_version":"0.3.6","2":"0.3.6","version_comment":"This version has updated documentation and some bug fixes.","3":"This version has updated documentation and some bug fixes.","package":"vimoutliner-0.3.6.zip","4":"vimoutliner-0.3.6.zip","src_id":"15688","5":"15688","creation_date":"1305936891","6":"1305936891"},{"0":"3515","vim_version":"7.0","1":"7.0","script_version":"0.3.5","2":"0.3.5","version_comment":"* Additions\/Changes:\r\n- Moved all files inside $HOME\/.vim.\r\n- Added a cheat sheet to the documentation.\r\n- Added smart-paste plugin.\r\n- Added and updated post-processor scripts:\r\n\t\u00c2\u00b7 fs2otl\r\n\t\u00c2\u00b7 Node.pm\r\n\t\u00c2\u00b7 otl2aft.awk\r\n\t\u00c2\u00b7 otl2docbook.pl\r\n\t\u00c2\u00b7 otl2html.py\r\n\t\u00c2\u00b7 otl2lyx.awk\r\n\t\u00c2\u00b7 otl2ooimpress.py\r\n\t\u00c2\u00b7 otl2table.py\r\n\t\u00c2\u00b7 otl2tags.py\r\n\t\u00c2\u00b7 otlgrep.py\r\n\t\u00c2\u00b7 otlhead.sh\r\n\t\u00c2\u00b7 otlsplit.py\r\n\t\u00c2\u00b7 otltail.sh\r\n\t\u00c2\u00b7 otl_handler\r\n\t\u00c2\u00b7 outline_calendar\r\n\t\u00c2\u00b7 outline_freemind\r\n\t\u00c2\u00b7 vo_maketags.pl\r\n- Added syntax support for _ilink_.\r\n- Hoist plugin disabled by default.\r\n- Layout of vo_readme.txt made more similar to Vim help.\r\n\r\n* Bug fixes:\r\n- ,,S did not work. Fixed","3":"* Additions\/Changes:\r\n- Moved all files inside $HOME\/.vim.\r\n- Added a cheat sheet to the documentation.\r\n- Added smart-paste plugin.\r\n- Added and updated post-processor scripts:\r\n\t\u00c2\u00b7 fs2otl\r\n\t\u00c2\u00b7 Node.pm\r\n\t\u00c2\u00b7 otl2aft.awk\r\n\t\u00c2\u00b7 otl2docbook.pl\r\n\t\u00c2\u00b7 otl2html.py\r\n\t\u00c2\u00b7 otl2lyx.awk\r\n\t\u00c2\u00b7 otl2ooimpress.py\r\n\t\u00c2\u00b7 otl2table.py\r\n\t\u00c2\u00b7 otl2tags.py\r\n\t\u00c2\u00b7 otlgrep.py\r\n\t\u00c2\u00b7 otlhead.sh\r\n\t\u00c2\u00b7 otlsplit.py\r\n\t\u00c2\u00b7 otltail.sh\r\n\t\u00c2\u00b7 otl_handler\r\n\t\u00c2\u00b7 outline_calendar\r\n\t\u00c2\u00b7 outline_freemind\r\n\t\u00c2\u00b7 vo_maketags.pl\r\n- Added syntax support for _ilink_.\r\n- Hoist plugin disabled by default.\r\n- Layout of vo_readme.txt made more similar to Vim help.\r\n\r\n* Bug fixes:\r\n- ,,S did not work. Fixed","package":"vimoutliner-0.3.5.zip","4":"vimoutliner-0.3.5.zip","src_id":"15267","5":"15267","creation_date":"1300666080","6":"1300666080"}]},"3514":{"script_id":"3514","0":"3514","script_name":"vim activator","1":"vim activator","script_type":"utility","2":"utility","summary":"A tool for reusing vim in xterm","3":"A tool for reusing vim in xterm","description":"When you exit vim to shell by pressing <ctrl-z> which suspends vim, \r\nthis nifty little gadget allows you edit subsequent files by reusing \r\nthe existing vim.  This tool requires client-server option to be\r\nenabled in vim.","4":"When you exit vim to shell by pressing <ctrl-z> which suspends vim, \r\nthis nifty little gadget allows you edit subsequent files by reusing \r\nthe existing vim.  This tool requires client-server option to be\r\nenabled in vim.","install_details":"1.  Put .bash_profile into your home directory.  If there's already existing\r\none, then you can rename the untar file to a different name, and source\r\nit from the existing .bash_profile.\r\n\r\n2.  In .vimrc add a reference to source Shell.vim from the tar ball.","5":"1.  Put .bash_profile into your home directory.  If there's already existing\r\none, then you can rename the untar file to a different name, and source\r\nit from the existing .bash_profile.\r\n\r\n2.  In .vimrc add a reference to source Shell.vim from the tar ball.","first_name":"Yiu","6":"Yiu","last_name":"Wing","7":"Wing","releases":[{"0":"3514","vim_version":"8.0","1":"8.0","script_version":"3.1","2":"3.1","version_comment":"Fix the following bugs.\r\n\r\n    1)  when editing multiple files in terminal mode, we should use existing\r\n        vim, not invoking a new one\r\n\r\n    2)  there are redundant '' pair when editing in terminal mode, some\r\n        leftover from previous immature improvement\r\n\r\n    3)  drop a frivolous function call from an in-house script\r\n","3":"Fix the following bugs.\r\n\r\n    1)  when editing multiple files in terminal mode, we should use existing\r\n        vim, not invoking a new one\r\n\r\n    2)  there are redundant '' pair when editing in terminal mode, some\r\n        leftover from previous immature improvement\r\n\r\n    3)  drop a frivolous function call from an in-house script\r\n","package":"activator.tar.gz","4":"activator.tar.gz","src_id":"27009","5":"27009","creation_date":"1582106131","6":"1582106131"},{"0":"3514","vim_version":"8.0","1":"8.0","script_version":"3.0","2":"3.0","version_comment":"This is a major update after many years.  No longer needed the C server, we\r\nare using a pure vim solution.  The following features have been added.\r\n\r\n    1)  be able to reuse vim in its own terminal\r\n\r\n    2)  edit the previous opened file without jumping, i.e. cd, to the\r\n        directory, or specifying the full path\r\n\r\n    3)  support vim command line arguments for the first time, and partial\r\n        support is available when reusing vim","3":"This is a major update after many years.  No longer needed the C server, we\r\nare using a pure vim solution.  The following features have been added.\r\n\r\n    1)  be able to reuse vim in its own terminal\r\n\r\n    2)  edit the previous opened file without jumping, i.e. cd, to the\r\n        directory, or specifying the full path\r\n\r\n    3)  support vim command line arguments for the first time, and partial\r\n        support is available when reusing vim","package":"activator.tar.gz","4":"activator.tar.gz","src_id":"27008","5":"27008","creation_date":"1582064918","6":"1582064918"},{"0":"3514","vim_version":"7.4","1":"7.4","script_version":"2.0","2":"2.0","version_comment":"A tremendous effort has been made to allow vim working seamlessly with bash shell, rather than embedding a shell in vim. After using this plugin a couple of months, I really don't see why we would need to have a fully fledge shell in vim which is on top of the feature requested list ;-)  There are already plenty of shells outside vim, we just need to make them working nicely together.  Check out the readme.txt for more information.  Happy vimming and bashing!","3":"A tremendous effort has been made to allow vim working seamlessly with bash shell, rather than embedding a shell in vim. After using this plugin a couple of months, I really don't see why we would need to have a fully fledge shell in vim which is on top of the feature requested list ;-)  There are already plenty of shells outside vim, we just need to make them working nicely together.  Check out the readme.txt for more information.  Happy vimming and bashing!","package":"activator.tar.gz","4":"activator.tar.gz","src_id":"21878","5":"21878","creation_date":"1399792740","6":"1399792740"},{"0":"3514","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"activator.tar.gz","4":"activator.tar.gz","src_id":"15251","5":"15251","creation_date":"1300503831","6":"1300503831"}]},"3513":{"script_id":"3513","0":"3513","script_name":"vim-stylus","1":"vim-stylus","script_type":"syntax","2":"syntax","summary":"Syntax\/Indentation for Stylus","3":"Syntax\/Indentation for Stylus","description":"Syntax hightlighting for Stylus\r\n  - http:\/\/learnboost.github.com\/stylus\/\r\n\r\nCSS3\/HTML5 bundled in and adapted from css3.vim by Hsiaoming Young\r\n  - http:\/\/www.vim.org\/scripts\/script.php?script_id=3042\r\n\r\nReport issues and follow updates at:\r\n  - https:\/\/github.com\/wavded\/vim-stylus","4":"Syntax hightlighting for Stylus\r\n  - http:\/\/learnboost.github.com\/stylus\/\r\n\r\nCSS3\/HTML5 bundled in and adapted from css3.vim by Hsiaoming Young\r\n  - http:\/\/www.vim.org\/scripts\/script.php?script_id=3042\r\n\r\nReport issues and follow updates at:\r\n  - https:\/\/github.com\/wavded\/vim-stylus","install_details":"Manual install\r\n  - Unzip into your .vim directory\r\nPathogen install\r\n  - Clone https:\/\/github.com\/wavded\/vim-stylus into your bundle directory","5":"Manual install\r\n  - Unzip into your .vim directory\r\nPathogen install\r\n  - Clone https:\/\/github.com\/wavded\/vim-stylus into your bundle directory","first_name":"Marc","6":"Marc","last_name":"Harter","7":"Harter","releases":[{"0":"3513","vim_version":"7.0","1":"7.0","script_version":"0.9.1","2":"0.9.1","version_comment":"add; css property user-select added\r\nfix; cssDefineBlock: do not contain stylusImportList\r\nfix; pointer events highlighting\r\nmod; make installs slightly easier","3":"add; css property user-select added\r\nfix; cssDefineBlock: do not contain stylusImportList\r\nfix; pointer events highlighting\r\nmod; make installs slightly easier","package":"vim-stylus-0.9.1.zip","4":"vim-stylus-0.9.1.zip","src_id":"21916","5":"21916","creation_date":"1400726883","6":"1400726883"},{"0":"3513","vim_version":"7.2","1":"7.2","script_version":"0.9.0","2":"0.9.0","version_comment":" * update; Extends highlighted hex colors to include #n and #nn.\r\n * fix; unsetting main_syntax fixes issues with other plugins\r\n * fix; syntax highlighting for stylus import\/require\r\n * fix; syntax highlighting for comments\r\n * fix; support space between property value GH #11\r\n * fix; stylus comment after property\r\n * fix; single line comment ignore http:\/\/\r\n * fix; line comments (\/\/).\r\n * fix; indentation\r\n * fix; highlighting variables without $ Closes #22\r\n * fix; braces indenting\r\n * del; local set overrides\r\n * add; the 'Stylus' command (to validate the current file)\r\n * add; function interpolations Fixes #7\r\n * add; example of require fix\r\n * add; css3 syntax as part of project\r\n * add; broadened defintion of keyword to include [#-]; unnecessarily complained about single-line comments.\r\n * add; Enable jump to file on abbreviated @import","3":" * update; Extends highlighted hex colors to include #n and #nn.\r\n * fix; unsetting main_syntax fixes issues with other plugins\r\n * fix; syntax highlighting for stylus import\/require\r\n * fix; syntax highlighting for comments\r\n * fix; support space between property value GH #11\r\n * fix; stylus comment after property\r\n * fix; single line comment ignore http:\/\/\r\n * fix; line comments (\/\/).\r\n * fix; indentation\r\n * fix; highlighting variables without $ Closes #22\r\n * fix; braces indenting\r\n * del; local set overrides\r\n * add; the 'Stylus' command (to validate the current file)\r\n * add; function interpolations Fixes #7\r\n * add; example of require fix\r\n * add; css3 syntax as part of project\r\n * add; broadened defintion of keyword to include [#-]; unnecessarily complained about single-line comments.\r\n * add; Enable jump to file on abbreviated @import","package":"vim-stylus-0.9.0.zip","4":"vim-stylus-0.9.0.zip","src_id":"21544","5":"21544","creation_date":"1393557248","6":"1393557248"},{"0":"3513","vim_version":"7.2","1":"7.2","script_version":"0.8.3","2":"0.8.3","version_comment":"updated missing background properties","3":"updated missing background properties","package":"vim-stylus.zip","4":"vim-stylus.zip","src_id":"16593","5":"16593","creation_date":"1317075348","6":"1317075348"},{"0":"3513","vim_version":"7.2","1":"7.2","script_version":"0.8.2","2":"0.8.2","version_comment":"updated function list","3":"updated function list","package":"vim-stylus.zip","4":"vim-stylus.zip","src_id":"16431","5":"16431","creation_date":"1314935579","6":"1314935579"},{"0":"3513","vim_version":"7.2","1":"7.2","script_version":"0.8.1","2":"0.8.1","version_comment":"minor bug fixes","3":"minor bug fixes","package":"vim-stylus.zip","4":"vim-stylus.zip","src_id":"15555","5":"15555","creation_date":"1304225017","6":"1304225017"},{"0":"3513","vim_version":"7.0","1":"7.0","script_version":"0.8","2":"0.8","version_comment":"added better indentation support","3":"added better indentation support","package":"vim-stylus.zip","4":"vim-stylus.zip","src_id":"15277","5":"15277","creation_date":"1300849496","6":"1300849496"},{"0":"3513","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"vim-stylus.zip","4":"vim-stylus.zip","src_id":"15249","5":"15249","creation_date":"1300487384","6":"1300487384"}]},"3512":{"script_id":"3512","0":"3512","script_name":"Scala Java Edit","1":"Scala Java Edit","script_type":"utility","2":"utility","summary":"Jump to source file associated with class name","3":"Jump to source file associated with class name","description":"Then press ,g while cursor is on a class name word and\r\nthe file should open (you'll need the\r\nsource files and the path to have been set already).\r\n\r\nPlace cursor over a word and attempt to find a scala file with the give name.\r\n\r\nThe following matches are attempted:\r\n 1) Is the cursor over a full package classname (e.g., scala.collection.Map)\r\n    If so is it over the classname (Map)\r\n      If so open it.\r\n    Or it is over on of the package names (collection)\r\n      If so open the directory (scala\/collection).\r\n 2) Is there a local file with the name <cword>.scala\r\n    If so open it.\r\n 3) Is there an import statement with that file identified explicitly\r\n    (e.g., scala.collection.Map for Map).\r\n    If so open it.\r\n    If \"locate\" is enabled, search for file scala\/collection\/Map.scala (in this\r\n    example). If found, open it.\r\n 4) Is it a file located in \"$JAVA_HOME\/src\/scala\/lang\/\" directory\r\n    If so open it.\r\n 5) Is there an import statement with that file identified implicitly.\r\n    (e.g., scala.collection.* for Map).\r\n    If so open it. \r\n    If \"locate\" is enabled, search for file scala\/collection\/Map.scala (in this\r\n    example). If found, open it.\r\n 6) Its possible we are in a junit directory or is some parallel directory\r\n    structure so that our current file has the same package statement\r\n    value as some source files in a different directory. This attempt takes\r\n    the package statement value, creates a directory plus scala file from\r\n    it and first looks through the scala path and if not found there,\r\n    does a \"locate\" searching for the file.\r\n\r\nAlso, can be configured to work with Java files (or with both Scala\r\nand Java source files).\r\n","4":"Then press ,g while cursor is on a class name word and\r\nthe file should open (you'll need the\r\nsource files and the path to have been set already).\r\n\r\nPlace cursor over a word and attempt to find a scala file with the give name.\r\n\r\nThe following matches are attempted:\r\n 1) Is the cursor over a full package classname (e.g., scala.collection.Map)\r\n    If so is it over the classname (Map)\r\n      If so open it.\r\n    Or it is over on of the package names (collection)\r\n      If so open the directory (scala\/collection).\r\n 2) Is there a local file with the name <cword>.scala\r\n    If so open it.\r\n 3) Is there an import statement with that file identified explicitly\r\n    (e.g., scala.collection.Map for Map).\r\n    If so open it.\r\n    If \"locate\" is enabled, search for file scala\/collection\/Map.scala (in this\r\n    example). If found, open it.\r\n 4) Is it a file located in \"$JAVA_HOME\/src\/scala\/lang\/\" directory\r\n    If so open it.\r\n 5) Is there an import statement with that file identified implicitly.\r\n    (e.g., scala.collection.* for Map).\r\n    If so open it. \r\n    If \"locate\" is enabled, search for file scala\/collection\/Map.scala (in this\r\n    example). If found, open it.\r\n 6) Its possible we are in a junit directory or is some parallel directory\r\n    structure so that our current file has the same package statement\r\n    value as some source files in a different directory. This attempt takes\r\n    the package statement value, creates a directory plus scala file from\r\n    it and first looks through the scala path and if not found there,\r\n    does a \"locate\" searching for the file.\r\n\r\nAlso, can be configured to work with Java files (or with both Scala\r\nand Java source files).\r\n","install_details":"Suggested stuff to add to your ~.vimrc:\r\n---------\r\n\r\n\" Set my Leader character\r\nlet mapleader = \",\"\r\n\r\n\" use locate command\r\nlet g:javae_locate_cmd = \"locate\"\r\nsource $HOME\/vim\/scalajavaedit.vim\r\n\r\n\" Java Stuff\r\nlet JAVASOURCEPATH = \"$JAVA_HOME\/src\" .\r\n   \\\",$HOME\/java\/xerces\/xerces\/src\" .\r\n   \\\",$HOME\/java\/xerces\/xalan\/src\" .\r\n   \\\",$HOME\/java\/jboss\/jboss\" .\r\n   \\\",$HOME\/java\/jakarta\/commons-lang\/src\/java\" .\r\n   \\\",$HOME\/java\/jakarta\/commons-collections\/src\/java\" .\r\n   \\\",$HOME\/java\/jakarta\/jakarta-tomcat\/jakarta-servletapi-5\/jsr154\/src\/share\/\"\r\n\" Note that for Java, only search for files with the 'java' suffix\r\n\" goto\r\nautocmd FileType java map <Leader>g :call EditSource('e',['java'],=,JAVASOURCEPATH)<CR>\r\n\" horizontal\r\nautocmd FileType java map <Leader>h :call EditSource('sp',['java'],=,JAVASOURCEPATH)<CR>\r\n\" vertical\r\nautocmd FileType java map <Leader>v :call EditSource('vsp',['java'],=,JAVASOURCEPATH)<CR>\r\n\r\n\" if you want to debug, comment out above line and uncomment below line\r\n\"map <Leader>g :debug:call EditSource('e',JAVASOURCEPATH)<CR>\r\n\r\n\" Scala Stuff\r\nlet SCALASOURCEPATH = \"$SCALA_HOME\/src\" .\r\n   \\\",$SVN_HOME\/project1\/src\/main\/scala\" .\r\n   \\\",$SVN_HOME\/project1\/src\/test\/scala\" .\r\n   \\\",$SVN_HOME\/project2\/src\/main\/scala\" .\r\n   \\\",$SVN_HOME\/project2\/src\/test\/scala\" .\r\n   \\\",$JAVA_HOME\/src\"\r\n\r\n\" Note that for Scala, search for files with the 'scala' and\r\n\"    then 'java' suffixes\r\n\" goto\r\nautocmd FileType scala map <Leader>g :call EditSource('e',['scala', 'java'],SCALASOURCEPATH)<CR>\r\n\" horizontal\r\nautocmd FileType scala map <Leader>h :call EditSource('sp',['scala', 'java'],SCALASOURCEPATH)<CR>\r\n\" vertical\r\nautocmd FileType scala map <Leader>v :call EditSource('vsp',['scala', 'java'],SCALASOURCEPATH)<CR>\r\n\r\n---------\r\nEnd Suggested stuff to add to your ~.vimrc:\r\n\r\nOne can of course, define more than one SOURCEPATH search variable and\r\nhave different mappings to envoke the different search paths.\r\nWhen porting Java code to Scala (and keeping the same package names for\r\nthe classes), I define a second search path and key map bindings\r\nallowing me to jump from the ported Scala source file to\r\nthe Java source file which was the basis of the port.\r\n\r\n\r\nYour java source path, of course, be different.\r\n\r\nMany java src tar files untar into directories with include not only\r\nthe component name, but also a version number (e.g., xerces has source\r\ndirectory xerces-2_6_2) - make symbolic link,\r\nln -s xerces-2_6_2 xerces\r\nand your vimrc will not have to be changed everytime you get a new\r\nversion.\r\n","5":"Suggested stuff to add to your ~.vimrc:\r\n---------\r\n\r\n\" Set my Leader character\r\nlet mapleader = \",\"\r\n\r\n\" use locate command\r\nlet g:javae_locate_cmd = \"locate\"\r\nsource $HOME\/vim\/scalajavaedit.vim\r\n\r\n\" Java Stuff\r\nlet JAVASOURCEPATH = \"$JAVA_HOME\/src\" .\r\n   \\\",$HOME\/java\/xerces\/xerces\/src\" .\r\n   \\\",$HOME\/java\/xerces\/xalan\/src\" .\r\n   \\\",$HOME\/java\/jboss\/jboss\" .\r\n   \\\",$HOME\/java\/jakarta\/commons-lang\/src\/java\" .\r\n   \\\",$HOME\/java\/jakarta\/commons-collections\/src\/java\" .\r\n   \\\",$HOME\/java\/jakarta\/jakarta-tomcat\/jakarta-servletapi-5\/jsr154\/src\/share\/\"\r\n\" Note that for Java, only search for files with the 'java' suffix\r\n\" goto\r\nautocmd FileType java map <Leader>g :call EditSource('e',['java'],=,JAVASOURCEPATH)<CR>\r\n\" horizontal\r\nautocmd FileType java map <Leader>h :call EditSource('sp',['java'],=,JAVASOURCEPATH)<CR>\r\n\" vertical\r\nautocmd FileType java map <Leader>v :call EditSource('vsp',['java'],=,JAVASOURCEPATH)<CR>\r\n\r\n\" if you want to debug, comment out above line and uncomment below line\r\n\"map <Leader>g :debug:call EditSource('e',JAVASOURCEPATH)<CR>\r\n\r\n\" Scala Stuff\r\nlet SCALASOURCEPATH = \"$SCALA_HOME\/src\" .\r\n   \\\",$SVN_HOME\/project1\/src\/main\/scala\" .\r\n   \\\",$SVN_HOME\/project1\/src\/test\/scala\" .\r\n   \\\",$SVN_HOME\/project2\/src\/main\/scala\" .\r\n   \\\",$SVN_HOME\/project2\/src\/test\/scala\" .\r\n   \\\",$JAVA_HOME\/src\"\r\n\r\n\" Note that for Scala, search for files with the 'scala' and\r\n\"    then 'java' suffixes\r\n\" goto\r\nautocmd FileType scala map <Leader>g :call EditSource('e',['scala', 'java'],SCALASOURCEPATH)<CR>\r\n\" horizontal\r\nautocmd FileType scala map <Leader>h :call EditSource('sp',['scala', 'java'],SCALASOURCEPATH)<CR>\r\n\" vertical\r\nautocmd FileType scala map <Leader>v :call EditSource('vsp',['scala', 'java'],SCALASOURCEPATH)<CR>\r\n\r\n---------\r\nEnd Suggested stuff to add to your ~.vimrc:\r\n\r\nOne can of course, define more than one SOURCEPATH search variable and\r\nhave different mappings to envoke the different search paths.\r\nWhen porting Java code to Scala (and keeping the same package names for\r\nthe classes), I define a second search path and key map bindings\r\nallowing me to jump from the ported Scala source file to\r\nthe Java source file which was the basis of the port.\r\n\r\n\r\nYour java source path, of course, be different.\r\n\r\nMany java src tar files untar into directories with include not only\r\nthe component name, but also a version number (e.g., xerces has source\r\ndirectory xerces-2_6_2) - make symbolic link,\r\nln -s xerces-2_6_2 xerces\r\nand your vimrc will not have to be changed everytime you get a new\r\nversion.\r\n","first_name":"richard","6":"richard","last_name":"emberson","7":"emberson","releases":[{"0":"3512","vim_version":"7.2","1":"7.2","script_version":"1.6","2":"1.6","version_comment":"Initial upload","3":"Initial upload","package":"scalajavaedit.vim","4":"scalajavaedit.vim","src_id":"15248","5":"15248","creation_date":"1300468135","6":"1300468135"}]},"3511":{"script_id":"3511","0":"3511","script_name":"text object left and right","1":"text object left and right","script_type":"utility","2":"utility","summary":"text oject for left and right of a statement","3":"text oject for left and right of a statement","description":"This simple script create text object for left and right of a statement. e.g\r\n\r\nstri|ng = \"Hello World\"\r\n\r\n\r\n| is where your cursor is, in command mode\r\ntype ciL (change inner and L for the right hand sided)\r\n\r\nthe line will become\r\n\r\nstring = |\r\n\r\nsimilarily\r\n\r\nciH, diH, yiH etc will change, delete, yank the left hand side of the statement\r\n\r\nthis also works for ==, => as well\r\n\r\nNote if the line end with ',' or ';' it will be the boundary of the right hand side\r\nIf there is a space before the separator (=, ==, =>) or after, they are so the the boundary\r\n","4":"This simple script create text object for left and right of a statement. e.g\r\n\r\nstri|ng = \"Hello World\"\r\n\r\n\r\n| is where your cursor is, in command mode\r\ntype ciL (change inner and L for the right hand sided)\r\n\r\nthe line will become\r\n\r\nstring = |\r\n\r\nsimilarily\r\n\r\nciH, diH, yiH etc will change, delete, yank the left hand side of the statement\r\n\r\nthis also works for ==, => as well\r\n\r\nNote if the line end with ',' or ';' it will be the boundary of the right hand side\r\nIf there is a space before the separator (=, ==, =>) or after, they are so the the boundary\r\n","install_details":"","5":"","first_name":"Vinh","6":"Vinh","last_name":"Tran","7":"Tran","releases":[{"0":"3511","vim_version":"7.0","1":"7.0","script_version":"1.2","2":"1.2","version_comment":"Previous version contain a use of one of my other plugin. This remove that part","3":"Previous version contain a use of one of my other plugin. This remove that part","package":"left_right_text_object.vim","4":"left_right_text_object.vim","src_id":"15328","5":"15328","creation_date":"1301404905","6":"1301404905"},{"0":"3511","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"left_right_text_object.vim","4":"left_right_text_object.vim","src_id":"15244","5":"15244","creation_date":"1300452495","6":"1300452495"}]},"3510":{"script_id":"3510","0":"3510","script_name":"VimRepress","1":"VimRepress","script_type":"utility","2":"utility","summary":"Plugin for managing wordpress blog from Vim.","3":"Plugin for managing wordpress blog from Vim.","description":"VimRepress is a plugin for managing wordpress blog from Vim,  a rewritten  of vimscript #1953 , which is broken for years. \r\n\r\nNow VimRepress lives with more powerful again. \r\n\r\n*REQUIREMENT* \r\n\r\n- Vim 7.3+ with python 2.6\/2.7 support \r\n- Python Environment matched wtih Vim's support \r\n- python-markdown\/python-markdown2 installed \r\n- wordpress 3.0.0 +\r\n\r\n\r\nCOMMAND EXAMPLES \r\n\r\nSome commands list above contain special usage, example below may clearify them for you. \r\n\r\n\r\n    :BlogList             -  List 30 recent posts. \r\n    :BlogList page        -  List 30 recent pages. \r\n    :BlogList post 100    -  List 100 recent posts. \r\n\r\n    :BlogNew post         -  Write an new post. \r\n    :BlogNew page         -  Write an new page. \r\n\r\n    :BlogSave             -  Save (defautely published.) \r\n    :BlogSave draft       -  Save as draft. \r\n\r\n    :BlogPreview local    -  Preview page\/post locally in your browser. \r\n    :BlogPreview publish  -  Same as `:BlogSave publish' with brower opened. \r\n\r\n    :BlogOpen 679 \r\n    :BlogOpen http:\/\/your-first-blog.com\/archives\/679 \r\n    :BlogOpen http:\/\/your-second-blog.com\/?p=679 \r\n    :BlogOpen http:\/\/your-third-blog.com\/with-your-custom-permalink \r\n\r\nMore detailed about this commands, type :help vimpress while you have vimrepress installed. \r\n\r\nDeveloping Repository:  https:\/\/bitbucket.org\/pentie\/vimrepress","4":"VimRepress is a plugin for managing wordpress blog from Vim,  a rewritten  of vimscript #1953 , which is broken for years. \r\n\r\nNow VimRepress lives with more powerful again. \r\n\r\n*REQUIREMENT* \r\n\r\n- Vim 7.3+ with python 2.6\/2.7 support \r\n- Python Environment matched wtih Vim's support \r\n- python-markdown\/python-markdown2 installed \r\n- wordpress 3.0.0 +\r\n\r\n\r\nCOMMAND EXAMPLES \r\n\r\nSome commands list above contain special usage, example below may clearify them for you. \r\n\r\n\r\n    :BlogList             -  List 30 recent posts. \r\n    :BlogList page        -  List 30 recent pages. \r\n    :BlogList post 100    -  List 100 recent posts. \r\n\r\n    :BlogNew post         -  Write an new post. \r\n    :BlogNew page         -  Write an new page. \r\n\r\n    :BlogSave             -  Save (defautely published.) \r\n    :BlogSave draft       -  Save as draft. \r\n\r\n    :BlogPreview local    -  Preview page\/post locally in your browser. \r\n    :BlogPreview publish  -  Same as `:BlogSave publish' with brower opened. \r\n\r\n    :BlogOpen 679 \r\n    :BlogOpen http:\/\/your-first-blog.com\/archives\/679 \r\n    :BlogOpen http:\/\/your-second-blog.com\/?p=679 \r\n    :BlogOpen http:\/\/your-third-blog.com\/with-your-custom-permalink \r\n\r\nMore detailed about this commands, type :help vimpress while you have vimrepress installed. \r\n\r\nDeveloping Repository:  https:\/\/bitbucket.org\/pentie\/vimrepress","install_details":"*INSTALL* \r\n\r\nDownload vimpress_x.x.x.zip, extract it in your .vim directory: \r\n\r\n  cd ~\/.vim \r\n  unzip \/path\/to\/vimpress_x.x.x.zip \r\n\r\nCONFIGURE\r\nCreate file ~\/.vimpressrc in the following format:\r\n\r\n[Blog0]\r\nblog_url = http:\/\/a-blog.com\/\r\nusername = admin\r\npassword = 123456\r\n\r\n[BlogWhatEver]\r\nblog_url = https:\/\/someone.wordpress.com\/\r\nusername = someone\r\npassword =\r\nHardcoding the password is optional. If a password is not provided the plugin will prompt for one the first time it's needed.\r\n\r\nFor Upgraded Users\r\n\r\nDefining Account info in .vimrc is now obsolesced, if you have correspond defination in .vimrc (for older version vimpress), they will automaticly copied into ~\/.vimpressrc, now you're safe to remove the VIMPRESS defination in .vimrc.\r\n\r\nIf you need Markdown support, simply run `sudo apt-get install python-markdown' in Ubuntu. \r\n\r\nIf you use other distributions (or OSs), refer to your package manager or the python-markdown \r\nproject page: http:\/\/www.freewisdom.org\/projects\/python-markdown\/Installation \r\n","5":"*INSTALL* \r\n\r\nDownload vimpress_x.x.x.zip, extract it in your .vim directory: \r\n\r\n  cd ~\/.vim \r\n  unzip \/path\/to\/vimpress_x.x.x.zip \r\n\r\nCONFIGURE\r\nCreate file ~\/.vimpressrc in the following format:\r\n\r\n[Blog0]\r\nblog_url = http:\/\/a-blog.com\/\r\nusername = admin\r\npassword = 123456\r\n\r\n[BlogWhatEver]\r\nblog_url = https:\/\/someone.wordpress.com\/\r\nusername = someone\r\npassword =\r\nHardcoding the password is optional. If a password is not provided the plugin will prompt for one the first time it's needed.\r\n\r\nFor Upgraded Users\r\n\r\nDefining Account info in .vimrc is now obsolesced, if you have correspond defination in .vimrc (for older version vimpress), they will automaticly copied into ~\/.vimpressrc, now you're safe to remove the VIMPRESS defination in .vimrc.\r\n\r\nIf you need Markdown support, simply run `sudo apt-get install python-markdown' in Ubuntu. \r\n\r\nIf you use other distributions (or OSs), refer to your package manager or the python-markdown \r\nproject page: http:\/\/www.freewisdom.org\/projects\/python-markdown\/Installation \r\n","first_name":"Preston","6":"Preston","last_name":"Masion","7":"Masion","releases":[{"0":"3510","vim_version":"7.3","1":"7.3","script_version":"3.2.0","2":"3.2.0","version_comment":"3.2.0","3":"3.2.0","package":"vimpress-dev_3.2.0_r121_3b2af4bb105e.zip","4":"vimpress-dev_3.2.0_r121_3b2af4bb105e.zip","src_id":"18158","5":"18158","creation_date":"1340069838","6":"1340069838"},{"0":"3510","vim_version":"7.3","1":"7.3","script_version":"2.1.5","2":"2.1.5","version_comment":"BugFix: Failed reading <!--more--> tag content in page.","3":"BugFix: Failed reading <!--more--> tag content in page.","package":"vimpress-stable_2.1.5_r81_13e8413bc8e7.zip","4":"vimpress-stable_2.1.5_r81_13e8413bc8e7.zip","src_id":"16490","5":"16490","creation_date":"1315416453","6":"1315416453"},{"0":"3510","vim_version":"7.3","1":"7.3","script_version":"2.1.4","2":"2.1.4","version_comment":"FixBug: Left <!--more--> tag when reedit a post.","3":"FixBug: Left <!--more--> tag when reedit a post.","package":"vimpress-stable_2.1.4_r71_4421edf0ada2.zip","4":"vimpress-stable_2.1.4_r71_4421edf0ada2.zip","src_id":"16473","5":"16473","creation_date":"1315288675","6":"1315288675"},{"0":"3510","vim_version":"7.0","1":"7.0","script_version":"2.1.3","2":"2.1.3","version_comment":"BugFix: Fail to show a complete post if contaied \"<!--more-->\"","3":"BugFix: Fail to show a complete post if contaied \"<!--more-->\"","package":"vimpress-stable_2.1.3_r69_97f8697f2221.zip","4":"vimpress-stable_2.1.3_r69_97f8697f2221.zip","src_id":"16472","5":"16472","creation_date":"1315286191","6":"1315286191"},{"0":"3510","vim_version":"7.3","1":"7.3","script_version":"2.1.2","2":"2.1.2","version_comment":"Bug Fix Version. \r\n-fix: will update meta area if new posts left cats\/slug empty.","3":"Bug Fix Version. \r\n-fix: will update meta area if new posts left cats\/slug empty.","package":"vimpress_2.1.2_r45_92e8d28b40fc.zip","4":"vimpress_2.1.2_r45_92e8d28b40fc.zip","src_id":"16227","5":"16227","creation_date":"1312955980","6":"1312955980"},{"0":"3510","vim_version":"7.3","1":"7.3","script_version":"2.1.0","2":"2.1.0","version_comment":"Fully Markdown Support;\r\nUse wordpress attachment to store raw markdown text;","3":"Fully Markdown Support;\r\nUse wordpress attachment to store raw markdown text;","package":"vimpress_2.1.0_r41_355e2b15f571.zip","4":"vimpress_2.1.0_r41_355e2b15f571.zip","src_id":"15764","5":"15764","creation_date":"1306744732","6":"1306744732"},{"0":"3510","vim_version":"7.3","1":"7.3","script_version":"1.3.0","2":"1.3.0","version_comment":"Add markdown support.","3":"Add markdown support.","package":"vimpress-1.3.0_r68.zip","4":"vimpress-1.3.0_r68.zip","src_id":"15311","5":"15311","creation_date":"1301294742","6":"1301294742"}]},"3509":{"script_id":"3509","0":"3509","script_name":"extradite.vim","1":"extradite.vim","script_type":"utility","2":"utility","summary":"A git commit browser. Extends fugitive.vim.","3":"A git commit browser. Extends fugitive.vim.","description":"See http:\/\/int3.github.com\/vim-extradite","4":"See http:\/\/int3.github.com\/vim-extradite","install_details":"","5":"","first_name":"Jezreel","6":"Jezreel","last_name":"Ng","7":"Ng","releases":[{"0":"3509","vim_version":"7.0","1":"7.0","script_version":"1.1","2":"1.1","version_comment":"Added a show_hash option, plus some bugfixes.","3":"Added a show_hash option, plus some bugfixes.","package":"vim-extradite.zip","4":"vim-extradite.zip","src_id":"17434","5":"17434","creation_date":"1329003251","6":"1329003251"},{"0":"3509","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"extradite.zip","4":"extradite.zip","src_id":"15239","5":"15239","creation_date":"1300416169","6":"1300416169"}]},"3508":{"script_id":"3508","0":"3508","script_name":"TeX-9","1":"TeX-9","script_type":"ftplugin","2":"ftplugin","summary":"A semi-automatic LaTeX ftplugin with lots of firepower!","3":"A semi-automatic LaTeX ftplugin with lots of firepower!","description":"TeX-9\r\n                       \r\n    Author: Elias Toivanen\r\n    License: GPL\r\n    Version: 1.3.13\r\n\r\n    TeX-9 is a ftplugin that aims to enhance the writing experience of high\r\n    quality documents with LaTeX and Vim. The goal of TeX-9 is to be simple\r\n    and Vimish, meaning that focus is on carefully thought-out key mappings\r\n    and features that are already present in a typical Vim installation. If\r\n    you need to write a thesis or research articles and insist on having only\r\n    one editor for all editing tasks, then TeX-9 is for you!\r\n\r\n    TeX-9 uses Python2.x as its backend and therefore a Vim installation with\r\n    Python support is required. TeX-9 is being developed on Linux running\r\n    Vim 7.4.\r\n\r\n     The main features of TeX-9 are\r\n        * Compile, debug and launch a document viewer from within Vim\r\n        * Insert LaTeX code snippets with ease\r\n        * Powerful text-object for LaTeX environments\r\n        * Omni-completion of BibTeX database entries and label references\r\n        * Omni-completion of mathematical symbols\r\n        * SyncTeX support (for the Evince document viewer)\r\n        * Filetype specific indentation (courtesy of Johannes Tanzler)\r\n        * LaTeX2e manual (ported to Vim by Mikolaj Machowski)\r\n        * No-hassle settings, relatively few mappings\r\n\r\n==============================================================================\r\n","4":"TeX-9\r\n                       \r\n    Author: Elias Toivanen\r\n    License: GPL\r\n    Version: 1.3.13\r\n\r\n    TeX-9 is a ftplugin that aims to enhance the writing experience of high\r\n    quality documents with LaTeX and Vim. The goal of TeX-9 is to be simple\r\n    and Vimish, meaning that focus is on carefully thought-out key mappings\r\n    and features that are already present in a typical Vim installation. If\r\n    you need to write a thesis or research articles and insist on having only\r\n    one editor for all editing tasks, then TeX-9 is for you!\r\n\r\n    TeX-9 uses Python2.x as its backend and therefore a Vim installation with\r\n    Python support is required. TeX-9 is being developed on Linux running\r\n    Vim 7.4.\r\n\r\n     The main features of TeX-9 are\r\n        * Compile, debug and launch a document viewer from within Vim\r\n        * Insert LaTeX code snippets with ease\r\n        * Powerful text-object for LaTeX environments\r\n        * Omni-completion of BibTeX database entries and label references\r\n        * Omni-completion of mathematical symbols\r\n        * SyncTeX support (for the Evince document viewer)\r\n        * Filetype specific indentation (courtesy of Johannes Tanzler)\r\n        * LaTeX2e manual (ported to Vim by Mikolaj Machowski)\r\n        * No-hassle settings, relatively few mappings\r\n\r\n==============================================================================\r\n","install_details":"       The good method\r\n         * Use the pathogen plugin (http:\/\/www.vim.org\/scripts\/script.php?script_id=2332)\r\n         * Clone TeX-9 from GitHub (https:\/\/github.com\/vim-scripts\/TeX-9) \r\n         * Run :Helptags and read the help on 'tex_nine'\r\n         * If you like TeX-9, show it on this page...it would make me happy.\r\n       \r\n         The traditional method\r\n        * Unzip the tarball to your local Vim tree (tar xaf tex_nine-<version>.tar.gz; rsync -avz tex_nine-<version>\/ ~\/.vim\/)\r\n        * Update helptags (:helptags ~\/.vim\/doc\/)\r\n        * Read the help on TeX-9 (:help tex_nine)","5":"       The good method\r\n         * Use the pathogen plugin (http:\/\/www.vim.org\/scripts\/script.php?script_id=2332)\r\n         * Clone TeX-9 from GitHub (https:\/\/github.com\/vim-scripts\/TeX-9) \r\n         * Run :Helptags and read the help on 'tex_nine'\r\n         * If you like TeX-9, show it on this page...it would make me happy.\r\n       \r\n         The traditional method\r\n        * Unzip the tarball to your local Vim tree (tar xaf tex_nine-<version>.tar.gz; rsync -avz tex_nine-<version>\/ ~\/.vim\/)\r\n        * Update helptags (:helptags ~\/.vim\/doc\/)\r\n        * Read the help on TeX-9 (:help tex_nine)","first_name":"Elias","6":"Elias","last_name":"Toivanen","7":"Toivanen","releases":[{"0":"3508","vim_version":"8.0","1":"8.0","script_version":"1.4.0","2":"1.4.0","version_comment":"Upgrade to Python 3","3":"Upgrade to Python 3","package":"tex_nine-1.4.0-1-g9e7f14c.tar.gz","4":"tex_nine-1.4.0-1-g9e7f14c.tar.gz","src_id":"27003","5":"27003","creation_date":"1581995617","6":"1581995617"},{"0":"3508","vim_version":"7.4","1":"7.4","script_version":"1.3.13","2":"1.3.13","version_comment":"Some refinements to the user experience. ","3":"Some refinements to the user experience. ","package":"tex_nine-1.3.13.tar.gz","4":"tex_nine-1.3.13.tar.gz","src_id":"22415","5":"22415","creation_date":"1410522801","6":"1410522801"},{"0":"3508","vim_version":"7.3","1":"7.3","script_version":"1.3.7","2":"1.3.7","version_comment":"Bugfix release.","3":"Bugfix release.","package":"tex_nine-1.3.7.tar.gz","4":"tex_nine-1.3.7.tar.gz","src_id":"20621","5":"20621","creation_date":"1376130233","6":"1376130233"},{"0":"3508","vim_version":"7.3","1":"7.3","script_version":"1.3.1","2":"1.3.1","version_comment":"Significantly improved handling of multi-file projects, new cleaner user preferences logic and a lot of small improvements. NB: You need a fairly up-to-date Vim for this version.","3":"Significantly improved handling of multi-file projects, new cleaner user preferences logic and a lot of small improvements. NB: You need a fairly up-to-date Vim for this version.","package":"tex_nine-1.3.1.tar.gz","4":"tex_nine-1.3.1.tar.gz","src_id":"20563","5":"20563","creation_date":"1374695886","6":"1374695886"},{"0":"3508","vim_version":"7.2","1":"7.2","script_version":"1.2.1","2":"1.2.1","version_comment":"Bugfix release.","3":"Bugfix release.","package":"tex_nine-1.2.1.tar.gz","4":"tex_nine-1.2.1.tar.gz","src_id":"19364","5":"19364","creation_date":"1358109805","6":"1358109805"},{"0":"3508","vim_version":"7.3","1":"7.3","script_version":"1.2","2":"1.2","version_comment":"SyncTeX support is back! Also a couple of other new features...","3":"SyncTeX support is back! Also a couple of other new features...","package":"tex_nine-1.2.tar.gz","4":"tex_nine-1.2.tar.gz","src_id":"17849","5":"17849","creation_date":"1335905616","6":"1335905616"},{"0":"3508","vim_version":"7.2","1":"7.2","script_version":"1.1.6","2":"1.1.6","version_comment":"Bug fixes and improved \"go to BibTeX entry\" command.","3":"Bug fixes and improved \"go to BibTeX entry\" command.","package":"tex_nine-1.1.6.tar.gz","4":"tex_nine-1.1.6.tar.gz","src_id":"17064","5":"17064","creation_date":"1323885704","6":"1323885704"},{"0":"3508","vim_version":"7.2","1":"7.2","script_version":"1.1.5","2":"1.1.5","version_comment":"Fixed a bug related to omnicompletion of pictures and fonts.","3":"Fixed a bug related to omnicompletion of pictures and fonts.","package":"tex_nine-1.1.5.tar.gz","4":"tex_nine-1.1.5.tar.gz","src_id":"16025","5":"16025","creation_date":"1309702772","6":"1309702772"},{"0":"3508","vim_version":"7.2","1":"7.2","script_version":"1.05","2":"1.05","version_comment":"Fixed a critical bug that caused TeX_9 to crash when upgrading to Ubuntu 11.04 (i.e. Python 2.7, Vim 7.3). Also fixed a couple of minor bugs. Fixed...","3":"Fixed a critical bug that caused TeX_9 to crash when upgrading to Ubuntu 11.04 (i.e. Python 2.7, Vim 7.3). Also fixed a couple of minor bugs. Fixed...","package":"tex_nine-1.05.tar.gz","4":"tex_nine-1.05.tar.gz","src_id":"15586","5":"15586","creation_date":"1304594587","6":"1304594587"}]},"3507":{"script_id":"3507","0":"3507","script_name":"scrnpipe.vim","1":"scrnpipe.vim","script_type":"utility","2":"utility","summary":"Pipe lines from your buffer to a screen window","3":"Pipe lines from your buffer to a screen window","description":"This plugin allows you to send a range of lines from a buffer to another screen window. This could be used for all sorts of things but my motivation was to be able to edit SQL statements in a file and then send them to a open mysql client session in another window. You could also send ruby code to a running erb or bash commands to a bash prompt, etc. You could even use this as a quick way to paste between 2 vim sessions running in different windows (or even different screen sessions).\r\n\r\nThe plugin creates some mapping by default. \r\n\r\nIn normal mode || sends the current line to another screen window. In visual modes use |.\r\n\r\nIf you have a mapleader set you'll need to type that first for both mapings. See :help mapleader for more info on that.\r\n\r\nYou can create you own mappings to override these. For the normal mode do this:\r\n\r\nnmap <whatever> <Plug>ScreenPipeSend\r\n\r\nFor visual modes do this:\r\n\r\nvmap <whatever> <Plug>ScreenPipeOpSend\r\n\r\nJust replace <whatever> with what you want to map of course.\r\n\r\nFinally, this plugin also provides a :ScreenPipe command to do the same thing.\r\n\r\nThe code is available on git here:\r\n\r\nhttps:\/\/github.com\/bundacia\/ScreenPipe\r\n\r\nKNOWN BUGS:\r\n1. The window list doesn't show up on the mac (but choosing the right number still works)\r\n\r\nTODO:\r\n1. Implement an operator.","4":"This plugin allows you to send a range of lines from a buffer to another screen window. This could be used for all sorts of things but my motivation was to be able to edit SQL statements in a file and then send them to a open mysql client session in another window. You could also send ruby code to a running erb or bash commands to a bash prompt, etc. You could even use this as a quick way to paste between 2 vim sessions running in different windows (or even different screen sessions).\r\n\r\nThe plugin creates some mapping by default. \r\n\r\nIn normal mode || sends the current line to another screen window. In visual modes use |.\r\n\r\nIf you have a mapleader set you'll need to type that first for both mapings. See :help mapleader for more info on that.\r\n\r\nYou can create you own mappings to override these. For the normal mode do this:\r\n\r\nnmap <whatever> <Plug>ScreenPipeSend\r\n\r\nFor visual modes do this:\r\n\r\nvmap <whatever> <Plug>ScreenPipeOpSend\r\n\r\nJust replace <whatever> with what you want to map of course.\r\n\r\nFinally, this plugin also provides a :ScreenPipe command to do the same thing.\r\n\r\nThe code is available on git here:\r\n\r\nhttps:\/\/github.com\/bundacia\/ScreenPipe\r\n\r\nKNOWN BUGS:\r\n1. The window list doesn't show up on the mac (but choosing the right number still works)\r\n\r\nTODO:\r\n1. Implement an operator.","install_details":"Just drop scrnpipe.vim in your plugins directory. ","5":"Just drop scrnpipe.vim in your plugins directory. ","first_name":"Trevor","6":"Trevor","last_name":"Little","7":"Little","releases":[{"0":"3507","vim_version":"7.0","1":"7.0","script_version":"0.2","2":"0.2","version_comment":"Better support for visual mode selection. Better shell escaping so that if you try to send text that has special shel chars in it the whole thing doesn't break. Normal mode mapping is now || by default.","3":"Better support for visual mode selection. Better shell escaping so that if you try to send text that has special shel chars in it the whole thing doesn't break. Normal mode mapping is now || by default.","package":"scrnpipe.vim","4":"scrnpipe.vim","src_id":"15236","5":"15236","creation_date":"1300395971","6":"1300395971"},{"0":"3507","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"scrnpipe.vim","4":"scrnpipe.vim","src_id":"15233","5":"15233","creation_date":"1300371824","6":"1300371824"}]},"3506":{"script_id":"3506","0":"3506","script_name":"compiler\/pcc.vim","1":"compiler\/pcc.vim","script_type":"ftplugin","2":"ftplugin","summary":"compiler plugin for Portable C Compiler (pcc)","3":"compiler plugin for Portable C Compiler (pcc)","description":"This is a compiler plugin for Portable C Compiler (pcc).\r\n\r\nIf you find any bug, please report it to hong@topbug.net, or submit it on the\r\nissue tracker:\r\nhttps:\/\/bitbucket.org\/xuhdev\/compiler-pcc.vim\/issues\r\n\r\nRepository:\r\nhttps:\/\/bitbucket.org\/xuhdev\/compiler-pcc.vim\/src","4":"This is a compiler plugin for Portable C Compiler (pcc).\r\n\r\nIf you find any bug, please report it to hong@topbug.net, or submit it on the\r\nissue tracker:\r\nhttps:\/\/bitbucket.org\/xuhdev\/compiler-pcc.vim\/issues\r\n\r\nRepository:\r\nhttps:\/\/bitbucket.org\/xuhdev\/compiler-pcc.vim\/src","install_details":"Download the compiler-pcc.zip file and extract it to your vim runtime directory (~\/.vim on UNIX\/Linux and $VIM_INSTALLATION_FOLDER\\vimfiles on windows).","5":"Download the compiler-pcc.zip file and extract it to your vim runtime directory (~\/.vim on UNIX\/Linux and $VIM_INSTALLATION_FOLDER\\vimfiles on windows).","first_name":"Hong","6":"Hong","last_name":"Xu","7":"Xu","releases":[{"0":"3506","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"compiler-pcc.zip","4":"compiler-pcc.zip","src_id":"15232","5":"15232","creation_date":"1300356953","6":"1300356953"}]},"3505":{"script_id":"3505","0":"3505","script_name":"PasteBin.vim","1":"PasteBin.vim","script_type":"utility","2":"utility","summary":"vimscript for pastebin","3":"vimscript for pastebin","description":"This is vimscript for pastebin (http:\/\/pastebin.com\/)\r\n\r\nUsage:\r\n\r\n  :PasteBin\r\n    post whole text to pastebin.\r\n\r\n  :'<,'>PasteBin\r\n    post selected text to pastebin.\r\n\r\nRequire:\r\n  curl command (http:\/\/curl.haxx.se\/)\r\n","4":"This is vimscript for pastebin (http:\/\/pastebin.com\/)\r\n\r\nUsage:\r\n\r\n  :PasteBin\r\n    post whole text to pastebin.\r\n\r\n  :'<,'>PasteBin\r\n    post selected text to pastebin.\r\n\r\nRequire:\r\n  curl command (http:\/\/curl.haxx.se\/)\r\n","install_details":"copy it to your plugin directory.\r\n","5":"copy it to your plugin directory.\r\n","first_name":"Yasuhiro","6":"Yasuhiro","last_name":"Matsumoto","7":"Matsumoto","releases":[{"0":"3505","vim_version":"7.0","1":"7.0","script_version":"0.2","2":"0.2","version_comment":"g:pastebin_browser_command accept OpenBrowser command.\n","3":"g:pastebin_browser_command accept OpenBrowser command.\n","package":"pastebin.vim","4":"pastebin.vim","src_id":"15283","5":"15283","creation_date":"1300985443","6":"1300985443"},{"0":"3505","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"pastebin.vim","4":"pastebin.vim","src_id":"15230","5":"15230","creation_date":"1300334557","6":"1300334557"}]},"3504":{"script_id":"3504","0":"3504","script_name":"taglist-plus","1":"taglist-plus","script_type":"utility","2":"utility","summary":"Source code browser with awesome Javascript support","3":"Source code browser with awesome Javascript support","description":"taglist-plus.vim\r\n================\r\n\r\nThis is a fork of the popular taglist.vim plugin.\r\n\r\nTaglist-plus supports jsctags for excellent Javascript tagging. See [here][1]\r\nfor examples.\r\n\r\n[1]:http:\/\/discontinuously.com\/2011\/03\/vim-support-javascript-taglist-plus\/","4":"taglist-plus.vim\r\n================\r\n\r\nThis is a fork of the popular taglist.vim plugin.\r\n\r\nTaglist-plus supports jsctags for excellent Javascript tagging. See [here][1]\r\nfor examples.\r\n\r\n[1]:http:\/\/discontinuously.com\/2011\/03\/vim-support-javascript-taglist-plus\/","install_details":"","5":"","first_name":"Jezreel","6":"Jezreel","last_name":"Ng","7":"Ng","releases":[{"0":"3504","vim_version":"7.0","1":"7.0","script_version":"1.1.1","2":"1.1.1","version_comment":"Bug fixes.","3":"Bug fixes.","package":"taglist-plus.zip","4":"taglist-plus.zip","src_id":"15240","5":"15240","creation_date":"1300432068","6":"1300432068"},{"0":"3504","vim_version":"7.0","1":"7.0","script_version":"1.1","2":"1.1","version_comment":"Add \\'Tlist_javascript_Hide_Extras\\' option.","3":"Add \\'Tlist_javascript_Hide_Extras\\' option.","package":"taglist-plus.zip","4":"taglist-plus.zip","src_id":"15237","5":"15237","creation_date":"1300396581","6":"1300396581"},{"0":"3504","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"taglist-plus.zip","4":"taglist-plus.zip","src_id":"15229","5":"15229","creation_date":"1300314053","6":"1300314053"}]},"3503":{"script_id":"3503","0":"3503","script_name":"vim-erlang-skeleteons","1":"vim-erlang-skeleteons","script_type":"ftplugin","2":"ftplugin","summary":"Generic erlang templates for vim","3":"Generic erlang templates for vim","description":"https:\/\/github.com\/aerosol\/vim-erlang-skeletons","4":"https:\/\/github.com\/aerosol\/vim-erlang-skeletons","install_details":"","5":"","first_name":"adam","6":"adam","last_name":"rutkowski","7":"rutkowski","releases":[{"0":"3503","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"vim-erlang-skeletons.zip","4":"vim-erlang-skeletons.zip","src_id":"15226","5":"15226","creation_date":"1300221058","6":"1300221058"}]},"3502":{"script_id":"3502","0":"3502","script_name":"To Upper case (case changer)","1":"To Upper case (case changer)","script_type":"utility","2":"utility","summary":"change the keywords to upper case.","3":"change the keywords to upper case.","description":"\r\n User manual: \r\n For use this script on VB.\r\n First , add the following line to your vimrc:\r\n\r\n let g:case_basic_source='IF;ELSE;THEN;DO;WHILE;FOR;CALL;'\r\n\r\n Second , add the folloing line to your vimrc\r\n We use .vb as the language extension name.\r\n\r\n let g:case_changer_pat=\"*.vb\"\r\n\r\n Now , while your input if in your .vb file , I will change it to IF ...\r\n\r\n Use this script for other language .\r\n First , add source\r\n\r\n\" let g:case_{&ft}_source='WHILE;UNTIL;UNLESS...'\r\n\r\n let g:case_ruby_source='WHILE;UNTIL;UNLESS...'\r\n let g:case_sql_source='SELECT;INSERT;VALUES...'\r\n\r\n Second , add file extension:\r\n\r\n let g:case_changer_pat=\"*.vb;*.rb;*.py\"\r\n","4":"\r\n User manual: \r\n For use this script on VB.\r\n First , add the following line to your vimrc:\r\n\r\n let g:case_basic_source='IF;ELSE;THEN;DO;WHILE;FOR;CALL;'\r\n\r\n Second , add the folloing line to your vimrc\r\n We use .vb as the language extension name.\r\n\r\n let g:case_changer_pat=\"*.vb\"\r\n\r\n Now , while your input if in your .vb file , I will change it to IF ...\r\n\r\n Use this script for other language .\r\n First , add source\r\n\r\n\" let g:case_{&ft}_source='WHILE;UNTIL;UNLESS...'\r\n\r\n let g:case_ruby_source='WHILE;UNTIL;UNLESS...'\r\n let g:case_sql_source='SELECT;INSERT;VALUES...'\r\n\r\n Second , add file extension:\r\n\r\n let g:case_changer_pat=\"*.vb;*.rb;*.py\"\r\n","install_details":"put casechanger.vim to you $VIM\/vimfiles\/plugin","5":"put casechanger.vim to you $VIM\/vimfiles\/plugin","first_name":"JiuTian","6":"JiuTian","last_name":"Zhang","7":"Zhang","releases":[{"0":"3502","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"casechanger.vim","4":"casechanger.vim","src_id":"15224","5":"15224","creation_date":"1300165981","6":"1300165981"}]},"3501":{"script_id":"3501","0":"3501","script_name":"emacs-like-macro-recorder","1":"emacs-like-macro-recorder","script_type":"utility","2":"utility","summary":"Provider emacs like macro recording short-cut key","3":"Provider emacs like macro recording short-cut key","description":"Press F3 to start recording macro\r\nPress F4 to stop recording or play macro","4":"Press F3 to start recording macro\r\nPress F4 to stop recording or play macro","install_details":"Extract plugin file to ~\/.vim\/plugin","5":"Extract plugin file to ~\/.vim\/plugin","first_name":"Cheryl","6":"Cheryl","last_name":"Natsu","7":"Natsu","releases":[{"0":"3501","vim_version":"7.0","1":"7.0","script_version":"0.01","2":"0.01","version_comment":"Initial upload","3":"Initial upload","package":"emacs_macro.vim","4":"emacs_macro.vim","src_id":"15223","5":"15223","creation_date":"1300165949","6":"1300165949"}]},"3500":{"script_id":"3500","0":"3500","script_name":"vim_etx","1":"vim_etx","script_type":"syntax","2":"syntax","summary":"File detection and syntax highlighting for EazyText wiki markup","3":"File detection and syntax highlighting for EazyText wiki markup","description":"File detection plugin for `etx` file extension, which contains EazyText markup.\r\n\r\nSyntax highlighting for EazyText wiki markup.\r\n\r\nTo know more about EazyText wiki processor vising http:\/\/eazytext.pluggdapps.com","4":"File detection plugin for `etx` file extension, which contains EazyText markup.\r\n\r\nSyntax highlighting for EazyText wiki markup.\r\n\r\nTo know more about EazyText wiki processor vising http:\/\/eazytext.pluggdapps.com","install_details":"Download the tar.gz file into your $(HOME)\/.vim\/ directory. Change to $(HOME)\/.vim directory and un-tar the package.","5":"Download the tar.gz file into your $(HOME)\/.vim\/ directory. Change to $(HOME)\/.vim directory and un-tar the package.","first_name":"Pratap","6":"Pratap","last_name":"Chakravarthy","7":"Chakravarthy","releases":[{"0":"3500","vim_version":"7.0","1":"7.0","script_version":"0.11","2":"0.11","version_comment":"Syntax highlighting added for ** markup. Change the filetype from eazytext to etx.","3":"Syntax highlighting added for ** markup. Change the filetype from eazytext to etx.","package":"vim-eazytext.tar.gz","4":"vim-eazytext.tar.gz","src_id":"16317","5":"16317","creation_date":"1313926192","6":"1313926192"},{"0":"3500","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"vim-eazytext.tar.gz","4":"vim-eazytext.tar.gz","src_id":"15222","5":"15222","creation_date":"1300165585","6":"1300165585"}]},"3499":{"script_id":"3499","0":"3499","script_name":"FindEverything","1":"FindEverything","script_type":"utility","2":"utility","summary":"Find everyting in your drives.","3":"Find everyting in your drives.","description":"Only for windows.\r\n\r\nAs a vimer, I wish to use vim to locate and open file more easier and faster.\r\nOne day, I found a free software named Everything, it can locates files and folders by filename instantly for Windows.\r\nThis plugin provides a interface with Everything command-line tools(es.exe).\r\nInvoke FindEverything, type the file name you wish to find, and then it will return results in a buffer window.\r\n\r\nHow fast it can be?\r\nI type '*', which means find all files in all of my drives, and it return 160,000+ results in less than 5 seconds.\r\nI believe that if you type more character, it will show the results instantly.\r\n\r\nUsage:\r\n1. Download Everything gui and command-line(es.exe) tools\r\n    from the website: http:\/\/www.voidtools.com\/download.php\r\n2. Start everything.exe and keep it running in background.\r\n3. Put this plugin into your vim runtime\/plugin directory.\r\n4. Define g:fe_es_exe in your vimrc file. \r\n     Notice: it should pointer to the everything command-line interface(es.exe)\r\n     e.g. let g:fe_es_exe = 'd:\\Everything\\es.exe'\r\n5. Open vim and run command :FE\r\n\r\nCommand(all capital)\r\n:FE  find files using everything.\r\n:FER toggle the buffer to see the last search result.\r\n\r\nSome map_keys:\r\n<CR>     Open file under the cursor by default association.\r\n<C-CR>   Open file under the cursor using current vim session.\r\n<ESC>    Quit the result buffer.\r\n\r\nSome options:\r\n1. Always open these file types in current vim session.\r\n   let g:fe_openfile_filter = ['txt', 'vim']\r\n2. Define es.exe option.\r\n   let g:fe_es_option = '-s'\r\n\r\nKnown issues:\r\n1. Don't set g:fe_es_exe to any path include whitespace.\r\n2. es.exe support regular search, but seems that it can't work as well as its gui tools.\r\n   So, I suggest not using its -r option. You can use vim regular for further searching.\r\n","4":"Only for windows.\r\n\r\nAs a vimer, I wish to use vim to locate and open file more easier and faster.\r\nOne day, I found a free software named Everything, it can locates files and folders by filename instantly for Windows.\r\nThis plugin provides a interface with Everything command-line tools(es.exe).\r\nInvoke FindEverything, type the file name you wish to find, and then it will return results in a buffer window.\r\n\r\nHow fast it can be?\r\nI type '*', which means find all files in all of my drives, and it return 160,000+ results in less than 5 seconds.\r\nI believe that if you type more character, it will show the results instantly.\r\n\r\nUsage:\r\n1. Download Everything gui and command-line(es.exe) tools\r\n    from the website: http:\/\/www.voidtools.com\/download.php\r\n2. Start everything.exe and keep it running in background.\r\n3. Put this plugin into your vim runtime\/plugin directory.\r\n4. Define g:fe_es_exe in your vimrc file. \r\n     Notice: it should pointer to the everything command-line interface(es.exe)\r\n     e.g. let g:fe_es_exe = 'd:\\Everything\\es.exe'\r\n5. Open vim and run command :FE\r\n\r\nCommand(all capital)\r\n:FE  find files using everything.\r\n:FER toggle the buffer to see the last search result.\r\n\r\nSome map_keys:\r\n<CR>     Open file under the cursor by default association.\r\n<C-CR>   Open file under the cursor using current vim session.\r\n<ESC>    Quit the result buffer.\r\n\r\nSome options:\r\n1. Always open these file types in current vim session.\r\n   let g:fe_openfile_filter = ['txt', 'vim']\r\n2. Define es.exe option.\r\n   let g:fe_es_option = '-s'\r\n\r\nKnown issues:\r\n1. Don't set g:fe_es_exe to any path include whitespace.\r\n2. es.exe support regular search, but seems that it can't work as well as its gui tools.\r\n   So, I suggest not using its -r option. You can use vim regular for further searching.\r\n","install_details":"","5":"","first_name":"chao","6":"chao","last_name":"wang","7":"wang","releases":[{"0":"3499","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"FindEverything.vim","4":"FindEverything.vim","src_id":"15207","5":"15207","creation_date":"1300016523","6":"1300016523"}]},"3498":{"script_id":"3498","0":"3498","script_name":"Scala argument formatter","1":"Scala argument formatter","script_type":"utility","2":"utility","summary":"Format method arguments","3":"Format method arguments","description":"Place the cursor on any character in the method name or on the\r\nmethods left paren, '(', and then invoke this script. If you\r\nuse the binding above, you would enter <Leader>f.\r\n\r\nThe script finds the first non-white-space character after the\r\nmethod's left paren and uses that as the character position for\r\naligning all arguments (note: in the following, the indent spacing may\r\nnot be correct - but it will be correct in your editor).\r\n\r\nExamples of method calls:\r\n\r\n   m1(thisIsArgOne, thisIsArgTwo, thisIsArgThree(), thisIsArgFour): Sometype = {\r\n     ....\r\n   }\r\n\r\nbecomes\r\n\r\n   m1(thisIsArgOne,\r\n      thisIsArgTwo,\r\n      thisIsArgThree(),\r\n      thisIsArgFour): Sometype = {\r\n     ....\r\n   }\r\n\r\nand the following (note first argument position):\r\n\r\n   aVeryLongMethodNameAsAnExampleUsage(\r\n                           thisIsArgOne, thisIsArgTwo, thisIsArgThree, thisIsArgFour): Sometype = {\r\n     ....\r\n   }\r\n\r\nbecomes\r\n\r\n   aVeryLongMethodNameAsAnExampleUsage(\r\n                           thisIsArgOne,\r\n                           thisIsArgTwo,\r\n                           thisIsArgThree,\r\n                           thisIsArgFour): Sometype = {\r\n     ....\r\n   }\r\n\r\nbecomes (with s:formatargs_extra_arg_offset = 2)\r\n\r\n   aVeryLongMethodNameAsAnExampleUsage(\r\n                           thisIsArgOne,\r\n                             thisIsArgTwo,\r\n                             thisIsArgThree,\r\n                             thisIsArgFour): Sometype = {\r\n     ....\r\n   }\r\n\r\nGenerally, in this case you can change the location of the first\r\nmethod argument and reformat and it works (the rest of the arguments\r\nare aligned under the first argument).\r\n\r\nExamples of method calls with string arguments:\r\n\r\n   m1(thisIsArgOne, \"this is\" + somestring + \"a \\\"foo()\\\" test\", thisIsArgThree): Sometype = {\r\n     ....\r\n   }\r\n\r\nbecomes (with let s:formatargs_extra_string_arg_offset = 0)\r\n\r\n   m1(thisIsArgOne,\r\n      \"this is\" +\r\n      somestring +\r\n      \"a \\\"foo()\\\" test\",\r\n      thisIsArgThree): Sometype = {\r\n     ....\r\n   }\r\n\r\nor becomes (with let s:formatargs_extra_string_arg_offset = 2)\r\n\r\n   m1(thisIsArgOne,\r\n      \"this is\" +\r\n        somestring +\r\n        \"a \\\"foo()\\\" test\",\r\n      thisIsArgThree): Sometype = {\r\n     ....\r\n   }\r\n\r\nYea, it can actually do this.\r\n\r\nOne more example of a method where an argument is itself a method call:\r\n\r\n   m1(thisIsArgOne, thisIsArgTwo(innerOne, innerTwo), thisIsArgThree()): Sometype = {\r\n     ....\r\n   }\r\n\r\nplacing cursor on \"m1(\" and invoking this script becomes\r\n\r\n   m1(thisIsArgOne,\r\n      thisIsArgTwo(innerOne, innerTwo),\r\n      thisIsArgThree()): Sometype = {\r\n     ....\r\n   }\r\n\r\nthen placing cursor on \"thisIsArgTwo(\" and invoking this script becomes\r\n\r\n   m1(thisIsArgOne,\r\n      thisIsArgTwo(innerOne,\r\n                   innerTwo),\r\n      thisIsArgThree()): Sometype = {\r\n     ....\r\n   }\r\n\r\n\r\n\r\nExamples of method definitions:\r\n\r\n   def m1(thisIsArgOne: String, thisIsArgTwo: Int, thisIsArgThree: Float): Sometype = {\r\n     ....\r\n   }\r\n\r\nbecomes\r\n\r\n   def m1(thisIsArgOne: String,\r\n          thisIsArgTwo: Int,\r\n          thisIsArgThree: Float): Sometype = {\r\n     ....\r\n   }\r\n\r\nand the following (note first argument position):\r\n\r\n   def aVeryLongMethodNameAsAnExampleUsage(\r\n                           thisIsArgOne: String, thisIsArgTwo: Int, thisIsArgThree: Float): Sometype = {\r\n     ....\r\n   }\r\n\r\nbecomes\r\n\r\n   def aVeryLongMethodNameAsAnExampleUsage(\r\n                           thisIsArgOne: String,\r\n                           thisIsArgTwo: Int,\r\n                           thisIsArgThree: Float): Sometype = {\r\n     ....\r\n   }\r\n\r\nArray definition:\r\nAs an unplanned extra, this can be used to format the arguments to an\r\narray:\r\n\r\n   val a = Array[Int] ( 1, 3, 4, 5, 4)\r\n\r\nbecomes\r\n\r\n   val a = Array[Int] ( 1,\r\n                        3,\r\n                        4,\r\n                        5,\r\n                        4)\r\nand\r\n\r\n   val a = Array[Int] (\r\n             1, 3, 4, 5, 4)\r\n\r\nbecomes\r\n\r\n   val a = Array[Int] (\r\n             1,\r\n             3,\r\n             4,\r\n             5,\r\n             4)\r\n\r\nOk, so formating an array does not do too much.\r\n\r\nSource can be found at: https:\/\/github.com\/megaannum\/scala_format\r\n","4":"Place the cursor on any character in the method name or on the\r\nmethods left paren, '(', and then invoke this script. If you\r\nuse the binding above, you would enter <Leader>f.\r\n\r\nThe script finds the first non-white-space character after the\r\nmethod's left paren and uses that as the character position for\r\naligning all arguments (note: in the following, the indent spacing may\r\nnot be correct - but it will be correct in your editor).\r\n\r\nExamples of method calls:\r\n\r\n   m1(thisIsArgOne, thisIsArgTwo, thisIsArgThree(), thisIsArgFour): Sometype = {\r\n     ....\r\n   }\r\n\r\nbecomes\r\n\r\n   m1(thisIsArgOne,\r\n      thisIsArgTwo,\r\n      thisIsArgThree(),\r\n      thisIsArgFour): Sometype = {\r\n     ....\r\n   }\r\n\r\nand the following (note first argument position):\r\n\r\n   aVeryLongMethodNameAsAnExampleUsage(\r\n                           thisIsArgOne, thisIsArgTwo, thisIsArgThree, thisIsArgFour): Sometype = {\r\n     ....\r\n   }\r\n\r\nbecomes\r\n\r\n   aVeryLongMethodNameAsAnExampleUsage(\r\n                           thisIsArgOne,\r\n                           thisIsArgTwo,\r\n                           thisIsArgThree,\r\n                           thisIsArgFour): Sometype = {\r\n     ....\r\n   }\r\n\r\nbecomes (with s:formatargs_extra_arg_offset = 2)\r\n\r\n   aVeryLongMethodNameAsAnExampleUsage(\r\n                           thisIsArgOne,\r\n                             thisIsArgTwo,\r\n                             thisIsArgThree,\r\n                             thisIsArgFour): Sometype = {\r\n     ....\r\n   }\r\n\r\nGenerally, in this case you can change the location of the first\r\nmethod argument and reformat and it works (the rest of the arguments\r\nare aligned under the first argument).\r\n\r\nExamples of method calls with string arguments:\r\n\r\n   m1(thisIsArgOne, \"this is\" + somestring + \"a \\\"foo()\\\" test\", thisIsArgThree): Sometype = {\r\n     ....\r\n   }\r\n\r\nbecomes (with let s:formatargs_extra_string_arg_offset = 0)\r\n\r\n   m1(thisIsArgOne,\r\n      \"this is\" +\r\n      somestring +\r\n      \"a \\\"foo()\\\" test\",\r\n      thisIsArgThree): Sometype = {\r\n     ....\r\n   }\r\n\r\nor becomes (with let s:formatargs_extra_string_arg_offset = 2)\r\n\r\n   m1(thisIsArgOne,\r\n      \"this is\" +\r\n        somestring +\r\n        \"a \\\"foo()\\\" test\",\r\n      thisIsArgThree): Sometype = {\r\n     ....\r\n   }\r\n\r\nYea, it can actually do this.\r\n\r\nOne more example of a method where an argument is itself a method call:\r\n\r\n   m1(thisIsArgOne, thisIsArgTwo(innerOne, innerTwo), thisIsArgThree()): Sometype = {\r\n     ....\r\n   }\r\n\r\nplacing cursor on \"m1(\" and invoking this script becomes\r\n\r\n   m1(thisIsArgOne,\r\n      thisIsArgTwo(innerOne, innerTwo),\r\n      thisIsArgThree()): Sometype = {\r\n     ....\r\n   }\r\n\r\nthen placing cursor on \"thisIsArgTwo(\" and invoking this script becomes\r\n\r\n   m1(thisIsArgOne,\r\n      thisIsArgTwo(innerOne,\r\n                   innerTwo),\r\n      thisIsArgThree()): Sometype = {\r\n     ....\r\n   }\r\n\r\n\r\n\r\nExamples of method definitions:\r\n\r\n   def m1(thisIsArgOne: String, thisIsArgTwo: Int, thisIsArgThree: Float): Sometype = {\r\n     ....\r\n   }\r\n\r\nbecomes\r\n\r\n   def m1(thisIsArgOne: String,\r\n          thisIsArgTwo: Int,\r\n          thisIsArgThree: Float): Sometype = {\r\n     ....\r\n   }\r\n\r\nand the following (note first argument position):\r\n\r\n   def aVeryLongMethodNameAsAnExampleUsage(\r\n                           thisIsArgOne: String, thisIsArgTwo: Int, thisIsArgThree: Float): Sometype = {\r\n     ....\r\n   }\r\n\r\nbecomes\r\n\r\n   def aVeryLongMethodNameAsAnExampleUsage(\r\n                           thisIsArgOne: String,\r\n                           thisIsArgTwo: Int,\r\n                           thisIsArgThree: Float): Sometype = {\r\n     ....\r\n   }\r\n\r\nArray definition:\r\nAs an unplanned extra, this can be used to format the arguments to an\r\narray:\r\n\r\n   val a = Array[Int] ( 1, 3, 4, 5, 4)\r\n\r\nbecomes\r\n\r\n   val a = Array[Int] ( 1,\r\n                        3,\r\n                        4,\r\n                        5,\r\n                        4)\r\nand\r\n\r\n   val a = Array[Int] (\r\n             1, 3, 4, 5, 4)\r\n\r\nbecomes\r\n\r\n   val a = Array[Int] (\r\n             1,\r\n             3,\r\n             4,\r\n             5,\r\n             4)\r\n\r\nOk, so formating an array does not do too much.\r\n\r\nSource can be found at: https:\/\/github.com\/megaannum\/scala_format\r\n","install_details":"1. Edit the configuration section. It is commented, so I won't explain the\r\n   options here.\r\n\r\n2. Put something like this in your .vimrc file:\r\n\r\n     source $HOME\/.vim\/formatargs.vim\r\n     autocmd FileType scala map <Leader>f :call FormatArgs()<CR>\r\n     autocmd FileType scala map <Leader>c :call FormatMethodChain()<CR>\r\n     autocmd FileType scala map <Leader>s :call FormatString()<CR>\r\n","5":"1. Edit the configuration section. It is commented, so I won't explain the\r\n   options here.\r\n\r\n2. Put something like this in your .vimrc file:\r\n\r\n     source $HOME\/.vim\/formatargs.vim\r\n     autocmd FileType scala map <Leader>f :call FormatArgs()<CR>\r\n     autocmd FileType scala map <Leader>c :call FormatMethodChain()<CR>\r\n     autocmd FileType scala map <Leader>s :call FormatString()<CR>\r\n","first_name":"richard","6":"richard","last_name":"emberson","7":"emberson","releases":[{"0":"3498","vim_version":"7.0","1":"7.0","script_version":"2.0","2":"2.0","version_comment":"Now autoload enabled.","3":"Now autoload enabled.","package":"scala_format.zip","4":"scala_format.zip","src_id":"18328","5":"18328","creation_date":"1343413296","6":"1343413296"},{"0":"3498","vim_version":"7.0","1":"7.0","script_version":"1.1","2":"1.1","version_comment":"Maximum number of arguments is now a parameter with default value 10 (the original value). This can now be modified to allow for the formating of more than 10 arguments.\r\nMaximum number of lines to search for the first non-white space character is now a parameter with default value 2 (the original value). One is not likely to ever need to increase this value.","3":"Maximum number of arguments is now a parameter with default value 10 (the original value). This can now be modified to allow for the formating of more than 10 arguments.\r\nMaximum number of lines to search for the first non-white space character is now a parameter with default value 2 (the original value). One is not likely to ever need to increase this value.","package":"formatargs.vim","4":"formatargs.vim","src_id":"15247","5":"15247","creation_date":"1300467431","6":"1300467431"},{"0":"3498","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"formatargs.vim","4":"formatargs.vim","src_id":"15205","5":"15205","creation_date":"1299944367","6":"1299944367"}]},"3497":{"script_id":"3497","0":"3497","script_name":"compiler\/ifort.vim","1":"compiler\/ifort.vim","script_type":"ftplugin","2":"ftplugin","summary":"compiler plugin for Intel Fortran compiler","3":"compiler plugin for Intel Fortran compiler","description":"This is a compiler plugin for Intel Fortran compiler.\r\n\r\nThis script has been included in the standard vim distribution since vim version 7.3.152.\r\n\r\nIf you find any bug, please report it to hong@topbug.net, or submit it on the\r\nissue tracker:\r\nhttps:\/\/bitbucket.org\/xuhdev\/compiler-ifort.vim\/issues\r\n\r\nRepository:\r\nhttps:\/\/bitbucket.org\/xuhdev\/compiler-ifort.vim\/src\r\n ","4":"This is a compiler plugin for Intel Fortran compiler.\r\n\r\nThis script has been included in the standard vim distribution since vim version 7.3.152.\r\n\r\nIf you find any bug, please report it to hong@topbug.net, or submit it on the\r\nissue tracker:\r\nhttps:\/\/bitbucket.org\/xuhdev\/compiler-ifort.vim\/issues\r\n\r\nRepository:\r\nhttps:\/\/bitbucket.org\/xuhdev\/compiler-ifort.vim\/src\r\n ","install_details":"Download the compiler-ifort.zip file and extract it to your vim runtime directory (~\/.vim on UNIX\/Linux and $VIM_INSTALLATION_FOLDER\\vimfiles on windows).","5":"Download the compiler-ifort.zip file and extract it to your vim runtime directory (~\/.vim on UNIX\/Linux and $VIM_INSTALLATION_FOLDER\\vimfiles on windows).","first_name":"Hong","6":"Hong","last_name":"Xu","7":"Xu","releases":[{"0":"3497","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"compiler-ifort.zip","4":"compiler-ifort.zip","src_id":"15202","5":"15202","creation_date":"1299900856","6":"1299900856"}]},"3496":{"script_id":"3496","0":"3496","script_name":"compiler\/gfortran.vim","1":"compiler\/gfortran.vim","script_type":"ftplugin","2":"ftplugin","summary":"compiler plugin for GNU Fortran compiler","3":"compiler plugin for GNU Fortran compiler","description":"This is a compiler plugin for GNU Fortran compiler.\r\n\r\nThis script has been included in the standard vim distribution since vim version 7.3.152.\r\n\r\nIf you find any bug, please report it to hong@topbug.net, or submit it on the\r\nissue tracker:\r\nhttps:\/\/bitbucket.org\/xuhdev\/compiler-gfortran.vim\/issues\r\n\r\nRepository:\r\nhttps:\/\/bitbucket.org\/xuhdev\/compiler-gfortran.vim\/src","4":"This is a compiler plugin for GNU Fortran compiler.\r\n\r\nThis script has been included in the standard vim distribution since vim version 7.3.152.\r\n\r\nIf you find any bug, please report it to hong@topbug.net, or submit it on the\r\nissue tracker:\r\nhttps:\/\/bitbucket.org\/xuhdev\/compiler-gfortran.vim\/issues\r\n\r\nRepository:\r\nhttps:\/\/bitbucket.org\/xuhdev\/compiler-gfortran.vim\/src","install_details":"Download the compiler-gfortran.zip file and extract it to your vim runtime directory (~\/.vim on UNIX\/Linux and $VIM_INSTALLATION_FOLDER\\vimfiles on windows).","5":"Download the compiler-gfortran.zip file and extract it to your vim runtime directory (~\/.vim on UNIX\/Linux and $VIM_INSTALLATION_FOLDER\\vimfiles on windows).","first_name":"Hong","6":"Hong","last_name":"Xu","7":"Xu","releases":[{"0":"3496","vim_version":"7.0","1":"7.0","script_version":"0.1.2","2":"0.1.2","version_comment":"Add some information.","3":"Add some information.","package":"compiler-gfortran.zip","4":"compiler-gfortran.zip","src_id":"15214","5":"15214","creation_date":"1300076288","6":"1300076288"},{"0":"3496","vim_version":"7.0","1":"7.0","script_version":"0.1.1","2":"0.1.1","version_comment":"also recognize warning messages.","3":"also recognize warning messages.","package":"compiler-gfortran.zip","4":"compiler-gfortran.zip","src_id":"15201","5":"15201","creation_date":"1299899291","6":"1299899291"}]},"3495":{"script_id":"3495","0":"3495","script_name":"paper","1":"paper","script_type":"color scheme","2":"color scheme","summary":"A slightly toned-down mod of the Railscasts color scheme.","3":"A slightly toned-down mod of the Railscasts color scheme.","description":"Paper is a slightly toned-down mod of the Railscasts color scheme [1].\r\n\r\n[1] http:\/\/www.vim.org\/scripts\/script.php?script_id=1995","4":"Paper is a slightly toned-down mod of the Railscasts color scheme [1].\r\n\r\n[1] http:\/\/www.vim.org\/scripts\/script.php?script_id=1995","install_details":"Just copy it into ~\/.vim\/colors\/ (*nix) or vimfiles\/colors\/ (Windows) along with the original Railscasts color scheme.","5":"Just copy it into ~\/.vim\/colors\/ (*nix) or vimfiles\/colors\/ (Windows) along with the original Railscasts color scheme.","first_name":"Hakan","6":"Hakan","last_name":"Ensari","7":"Ensari","releases":[{"0":"3495","vim_version":"7.0","1":"7.0","script_version":"1.0.1","2":"1.0.1","version_comment":"The vertical split was supposed to be solid.","3":"The vertical split was supposed to be solid.","package":"paper.vim","4":"paper.vim","src_id":"15216","5":"15216","creation_date":"1300115748","6":"1300115748"},{"0":"3495","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"paper.vim","4":"paper.vim","src_id":"15198","5":"15198","creation_date":"1299882168","6":"1299882168"}]},"3494":{"script_id":"3494","0":"3494","script_name":"underlinetag","1":"underlinetag","script_type":"utility","2":"utility","summary":"underline tagged word to know the word hyperlinked.","3":"underline tagged word to know the word hyperlinked.","description":"No longer maintained.\r\n\r\nDon't use this, use quickhl.vim\r\n\r\nThis plugin's feature is merged to quickhl.vim as tag highlight feature.\r\nThis plugin used syntax feature to highlight tag, quickhl use matchadd(), its much faster and not kill original color.\r\nSee.\r\nhttp:\/\/www.vim.org\/scripts\/script.php?script_id=3692","4":"No longer maintained.\r\n\r\nDon't use this, use quickhl.vim\r\n\r\nThis plugin's feature is merged to quickhl.vim as tag highlight feature.\r\nThis plugin used syntax feature to highlight tag, quickhl use matchadd(), its much faster and not kill original color.\r\nSee.\r\nhttp:\/\/www.vim.org\/scripts\/script.php?script_id=3692","install_details":"","5":"","first_name":"t9","6":"t9","last_name":"md","7":"md","releases":[{"0":"3494","vim_version":"7.0","1":"7.0","script_version":"0.5","2":"0.5","version_comment":"Initial upload","3":"Initial upload","package":"underlinetag.zip","4":"underlinetag.zip","src_id":"15196","5":"15196","creation_date":"1299870784","6":"1299870784"}]},"3493":{"script_id":"3493","0":"3493","script_name":"Risto Color Scheme","1":"Risto Color Scheme","script_type":"color scheme","2":"color scheme","summary":"Dark color scheme with bright and colorful syntax highlighting","3":"Dark color scheme with bright and colorful syntax highlighting","description":"Dark color scheme with bright and colorful syntax highlighting.\r\n\r\nScreenshots: \r\n\r\nhttp:\/\/www.codeography.com\/images\/risto-vim-c.png\r\nhttp:\/\/www.codeography.com\/images\/risto-vim-menu.png\r\nhttp:\/\/www.codeography.com\/images\/risto-vim-html.png\r\n\r\nIncludes custom highlighting for NERDTree, Netrw, BufferExplorer, Project and a few other plugins.","4":"Dark color scheme with bright and colorful syntax highlighting.\r\n\r\nScreenshots: \r\n\r\nhttp:\/\/www.codeography.com\/images\/risto-vim-c.png\r\nhttp:\/\/www.codeography.com\/images\/risto-vim-menu.png\r\nhttp:\/\/www.codeography.com\/images\/risto-vim-html.png\r\n\r\nIncludes custom highlighting for NERDTree, Netrw, BufferExplorer, Project and a few other plugins.","install_details":"","5":"","first_name":"Christopher","6":"Christopher","last_name":"Sexton","7":"Sexton","releases":[{"0":"3493","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"risto.vim","4":"risto.vim","src_id":"15189","5":"15189","creation_date":"1299770289","6":"1299770289"}]},"3492":{"script_id":"3492","0":"3492","script_name":"compiler\/g95.vim","1":"compiler\/g95.vim","script_type":"ftplugin","2":"ftplugin","summary":"compiler plugin for G95 Fortran compiler","3":"compiler plugin for G95 Fortran compiler","description":"This is a compiler plugin for G95 Fortran compiler.\r\n\r\nThis script has been included in the standard vim distribution since vim version 7.3.152.\r\n\r\nIf you find any bug, please report it to hong@topbug.net, or submit it on the\r\nissue tracker:\r\nhttps:\/\/bitbucket.org\/xuhdev\/compiler-g95.vim\/issues\r\n\r\nRepository:\r\nhttps:\/\/bitbucket.org\/xuhdev\/compiler-g95.vim\/src","4":"This is a compiler plugin for G95 Fortran compiler.\r\n\r\nThis script has been included in the standard vim distribution since vim version 7.3.152.\r\n\r\nIf you find any bug, please report it to hong@topbug.net, or submit it on the\r\nissue tracker:\r\nhttps:\/\/bitbucket.org\/xuhdev\/compiler-g95.vim\/issues\r\n\r\nRepository:\r\nhttps:\/\/bitbucket.org\/xuhdev\/compiler-g95.vim\/src","install_details":"Download the compiler-g95.zip file and extract it to your vim runtime directory (~\/.vim on UNIX\/Linux and $VIM_INSTALLATION_FOLDER\\vimfiles on windows).","5":"Download the compiler-g95.zip file and extract it to your vim runtime directory (~\/.vim on UNIX\/Linux and $VIM_INSTALLATION_FOLDER\\vimfiles on windows).","first_name":"Hong","6":"Hong","last_name":"Xu","7":"Xu","releases":[{"0":"3492","vim_version":"7.0","1":"7.0","script_version":"0.1.2","2":"0.1.2","version_comment":"Also recognize warning messages.","3":"Also recognize warning messages.","package":"compiler-g95.zip","4":"compiler-g95.zip","src_id":"15203","5":"15203","creation_date":"1299902658","6":"1299902658"},{"0":"3492","vim_version":"7.0","1":"7.0","script_version":"0.1.1","2":"0.1.1","version_comment":"Don't set makeprg.","3":"Don't set makeprg.","package":"compiler-g95.zip","4":"compiler-g95.zip","src_id":"15199","5":"15199","creation_date":"1299898116","6":"1299898116"},{"0":"3492","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"compiler-g95.zip","4":"compiler-g95.zip","src_id":"15187","5":"15187","creation_date":"1299748914","6":"1299748914"}]},"3491":{"script_id":"3491","0":"3491","script_name":"textmanip.vim","1":"textmanip.vim","script_type":"utility","2":"utility","summary":"Maniplate(duplicate, move) selected text easily","3":"Maniplate(duplicate, move) selected text easily","description":"What is this?\r\n=============================================================\r\n* move visually selected text easily ( linewise \/ blockwise )\r\n* duplicate text easily ( linewise \/ blockwise )\r\n* count support\r\n* keep original cursor position (include 'o'ther pos in visualmode!) while moving \/ duplicating.\r\n* undo with one 'u' by undojoining.\r\n\r\nSee [ScreenCast](http:\/\/www.youtube.com\/watch?v=iJh7Z0Rp-rI) for v0.4.\r\nGithub https:\/\/github.com\/t9md\/vim-textmanip\r\n\r\n# Configuration example\r\n\r\n### GUI macvim ( which I use now )\r\n\r\n    xmap <D-d> <Plug>(textmanip-duplicate-down)\r\n    nmap <D-d> <Plug>(textmanip-duplicate-down)\r\n    xmap <D-D> <Plug>(textmanip-duplicate-up)\r\n    nmap <D-D> <Plug>(textmanip-duplicate-up)\r\n\r\n    xmap <C-j> <Plug>(textmanip-move-down)\r\n    xmap <C-k> <Plug>(textmanip-move-up)\r\n    xmap <C-h> <Plug>(textmanip-move-left)\r\n    xmap <C-l> <Plug>(textmanip-move-right)\r\n\r\n### gVim\r\n\r\n    xmap <M-d> <Plug>(textmanip-duplicate-down)\r\n    nmap <M-d> <Plug>(textmanip-duplicate-down)\r\n    xmap <M-D> <Plug>(textmanip-duplicate-up)\r\n    nmap <M-D> <Plug>(textmanip-duplicate-up)\r\n\r\n    xmap <C-j> <Plug>(textmanip-move-down)\r\n    xmap <C-k> <Plug>(textmanip-move-up)\r\n    xmap <C-h> <Plug>(textmanip-move-left)\r\n    xmap <C-l> <Plug>(textmanip-move-right)\r\n\r\n### vim on terminal\r\n\r\n    xmap <Space>d <Plug>(textmanip-duplicate-down)\r\n    nmap <Space>d <Plug>(textmanip-duplicate-down)\r\n    xmap <Space>D <Plug>(textmanip-duplicate-up)\r\n    nmap <Space>D <Plug>(textmanip-duplicate-up)\r\n\r\n    xmap <C-j> <Plug>(textmanip-move-down)\r\n    xmap <C-k> <Plug>(textmanip-move-up)\r\n    xmap <C-h> <Plug>(textmanip-move-left)\r\n    xmap <C-l> <Plug>(textmanip-move-right)","4":"What is this?\r\n=============================================================\r\n* move visually selected text easily ( linewise \/ blockwise )\r\n* duplicate text easily ( linewise \/ blockwise )\r\n* count support\r\n* keep original cursor position (include 'o'ther pos in visualmode!) while moving \/ duplicating.\r\n* undo with one 'u' by undojoining.\r\n\r\nSee [ScreenCast](http:\/\/www.youtube.com\/watch?v=iJh7Z0Rp-rI) for v0.4.\r\nGithub https:\/\/github.com\/t9md\/vim-textmanip\r\n\r\n# Configuration example\r\n\r\n### GUI macvim ( which I use now )\r\n\r\n    xmap <D-d> <Plug>(textmanip-duplicate-down)\r\n    nmap <D-d> <Plug>(textmanip-duplicate-down)\r\n    xmap <D-D> <Plug>(textmanip-duplicate-up)\r\n    nmap <D-D> <Plug>(textmanip-duplicate-up)\r\n\r\n    xmap <C-j> <Plug>(textmanip-move-down)\r\n    xmap <C-k> <Plug>(textmanip-move-up)\r\n    xmap <C-h> <Plug>(textmanip-move-left)\r\n    xmap <C-l> <Plug>(textmanip-move-right)\r\n\r\n### gVim\r\n\r\n    xmap <M-d> <Plug>(textmanip-duplicate-down)\r\n    nmap <M-d> <Plug>(textmanip-duplicate-down)\r\n    xmap <M-D> <Plug>(textmanip-duplicate-up)\r\n    nmap <M-D> <Plug>(textmanip-duplicate-up)\r\n\r\n    xmap <C-j> <Plug>(textmanip-move-down)\r\n    xmap <C-k> <Plug>(textmanip-move-up)\r\n    xmap <C-h> <Plug>(textmanip-move-left)\r\n    xmap <C-l> <Plug>(textmanip-move-right)\r\n\r\n### vim on terminal\r\n\r\n    xmap <Space>d <Plug>(textmanip-duplicate-down)\r\n    nmap <Space>d <Plug>(textmanip-duplicate-down)\r\n    xmap <Space>D <Plug>(textmanip-duplicate-up)\r\n    nmap <Space>D <Plug>(textmanip-duplicate-up)\r\n\r\n    xmap <C-j> <Plug>(textmanip-move-down)\r\n    xmap <C-k> <Plug>(textmanip-move-up)\r\n    xmap <C-h> <Plug>(textmanip-move-left)\r\n    xmap <C-l> <Plug>(textmanip-move-right)","install_details":"","5":"","first_name":"t9","6":"t9","last_name":"md","7":"md","releases":[{"0":"3491","vim_version":"7.0","1":"7.0","script_version":"1.8","2":"1.8","version_comment":"Support  replace-mode, which overwrite area and write back when selection pass that area.\r\nCode clean up\/ bug fix.","3":"Support  replace-mode, which overwrite area and write back when selection pass that area.\r\nCode clean up\/ bug fix.","package":"vim-textmanip-1.8.zip","4":"vim-textmanip-1.8.zip","src_id":"20995","5":"20995","creation_date":"1383407105","6":"1383407105"},{"0":"3491","vim_version":"7.0","1":"7.0","script_version":"1.3","2":"1.3","version_comment":"bug fix, error when g:textmanip_enable_mappings is not defined. ","3":"bug fix, error when g:textmanip_enable_mappings is not defined. ","package":"vim-textmanip-1.3.zip","4":"vim-textmanip-1.3.zip","src_id":"20973","5":"20973","creation_date":"1383005156","6":"1383005156"},{"0":"3491","vim_version":"7.0","1":"7.0","script_version":"1.2","2":"1.2","version_comment":"[bugfix] count did not work for some direction.","3":"[bugfix] count did not work for some direction.","package":"vim-textmanip-1.2.zip","4":"vim-textmanip-1.2.zip","src_id":"20967","5":"20967","creation_date":"1382855789","6":"1382855789"},{"0":"3491","vim_version":"7.0","1":"7.0","script_version":"1.1","2":"1.1","version_comment":"now support blockwise movement.\r\ncomplete code rewritten and many improvement, especially line up\/down move now much faster than older version.","3":"now support blockwise movement.\r\ncomplete code rewritten and many improvement, especially line up\/down move now much faster than older version.","package":"vim-textmanip-1.1.zip","4":"vim-textmanip-1.1.zip","src_id":"20961","5":"20961","creation_date":"1382796271","6":"1382796271"},{"0":"3491","vim_version":"7.0","1":"7.0","script_version":"0.7","2":"0.7","version_comment":"2011-08-16: v0.7\r\n        - [bugfix] extend_eol not worked in some situation.\r\n","3":"2011-08-16: v0.7\r\n        - [bugfix] extend_eol not worked in some situation.\r\n","package":"vim-textmanip-0.7.zip","4":"vim-textmanip-0.7.zip","src_id":"16265","5":"16265","creation_date":"1313428256","6":"1313428256"},{"0":"3491","vim_version":"7.0","1":"7.0","script_version":"0.6","2":"0.6","version_comment":"- [bugfix] better handling for redraw problem","3":"- [bugfix] better handling for redraw problem","package":"vim-textmanip-0.6.zip","4":"vim-textmanip-0.6.zip","src_id":"16263","5":"16263","creation_date":"1313409362","6":"1313409362"},{"0":"3491","vim_version":"7.0","1":"7.0","script_version":"0.5","2":"0.5","version_comment":"- [bugfix] handle left and up movement limit.\r\n- [bugfix] more strict check to determine continuous execution.\r\n- [bugfix] remove unnecessarily `undojoin` twice, and remove catch clause(E790)\r\n","3":"- [bugfix] handle left and up movement limit.\r\n- [bugfix] more strict check to determine continuous execution.\r\n- [bugfix] remove unnecessarily `undojoin` twice, and remove catch clause(E790)\r\n","package":"vim-textmanip-0.5.zip","4":"vim-textmanip-0.5.zip","src_id":"16258","5":"16258","creation_date":"1313327553","6":"1313327553"},{"0":"3491","vim_version":"7.0","1":"7.0","script_version":"0.4","2":"0.4","version_comment":"2011-08-14: v0.4\r\n        - support count for duplicate and move\r\n        - bug fix for `undojoin`\r\n        - refactoring,, support duplicate text to upper direction.\r\n        - change keymap for consistency, sorry.\r\n        - autoloadize!","3":"2011-08-14: v0.4\r\n        - support count for duplicate and move\r\n        - bug fix for `undojoin`\r\n        - refactoring,, support duplicate text to upper direction.\r\n        - change keymap for consistency, sorry.\r\n        - autoloadize!","package":"vim-textmanip-0.4.zip","4":"vim-textmanip-0.4.zip","src_id":"16257","5":"16257","creation_date":"1313313638","6":"1313313638"},{"0":"3491","vim_version":"7.0","1":"7.0","script_version":"0.3","2":"0.3","version_comment":"fix documentation bugs.code re-indent(so no change in code)","3":"fix documentation bugs.code re-indent(so no change in code)","package":"textmanip-0.3.zip","4":"textmanip-0.3.zip","src_id":"16080","5":"16080","creation_date":"1310855328","6":"1310855328"},{"0":"3491","vim_version":"7.0","1":"7.0","script_version":"0.2","2":"0.2","version_comment":"0.2\t2011-06-13\r\n\t- Fix document typo","3":"0.2\t2011-06-13\r\n\t- Fix document typo","package":"textmanip-0.2.zip","4":"textmanip-0.2.zip","src_id":"15900","5":"15900","creation_date":"1308148505","6":"1308148505"},{"0":"3491","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"textmanip.zip","4":"textmanip.zip","src_id":"15183","5":"15183","creation_date":"1299691573","6":"1299691573"}]},"3490":{"script_id":"3490","0":"3490","script_name":"visualctrlg","1":"visualctrlg","script_type":"utility","2":"utility","summary":"Report info about selected text","3":"Report info about selected text","description":"|visualctrlg| provides <C-g> and g<C-g> keymappings.\r\nthese keymapings show the report for selected text.\r\nlike |CTRL-G| and |g_CTRL-G| in |Normal-mode|.\r\n\r\nRepository: http:\/\/github.com\/tyru\/visualctrlg.vim","4":"|visualctrlg| provides <C-g> and g<C-g> keymappings.\r\nthese keymapings show the report for selected text.\r\nlike |CTRL-G| and |g_CTRL-G| in |Normal-mode|.\r\n\r\nRepository: http:\/\/github.com\/tyru\/visualctrlg.vim","install_details":"","5":"","first_name":"tyru","6":"tyru","last_name":" ","7":" ","releases":[{"0":"3490","vim_version":"7.0","1":"7.0","script_version":"0.0.1","2":"0.0.1","version_comment":"- fix a minor bug\r\n- add the description about g:visualctrlg_no_default_keymappings.\r\n- add the description about how default mappings get applied. (Thanks blueyed)","3":"- fix a minor bug\r\n- add the description about g:visualctrlg_no_default_keymappings.\r\n- add the description about how default mappings get applied. (Thanks blueyed)","package":"visualctrlg.zip","4":"visualctrlg.zip","src_id":"15427","5":"15427","creation_date":"1302529588","6":"1302529588"},{"0":"3490","vim_version":"7.0","1":"7.0","script_version":"0.0.0","2":"0.0.0","version_comment":"Initial upload","3":"Initial upload","package":"visualctrlg.zip","4":"visualctrlg.zip","src_id":"15181","5":"15181","creation_date":"1299675191","6":"1299675191"}]},"3489":{"script_id":"3489","0":"3489","script_name":"urilib","1":"urilib","script_type":"utility","2":"utility","summary":"URI library in vim script inspired by URI.pm","3":"URI library in vim script inspired by URI.pm","description":"    let uri = urilib#new('http:\/\/twitter.com\/tyru')\r\n\r\n\t\" \"http\"\r\n    echo uri.scheme()\r\n\r\n\t\" \"twitter.com\"\r\n    echo uri.host()\r\n\r\n\t\" \"\/tyru\"\r\n    echo uri.path()\r\n\r\n\t\" \"\/\/twitter.com\/tyru\"\r\n    echo uri.opaque()\r\n\r\n\t\" \"\"\r\n    echo uri.fragment()\r\n\r\n\r\n    let uri = urilib#new('http:\/\/d.hatena.ne.jp\/tyru\/20100619\/git_push_vim_plugins_to_github#c')\r\n\r\n\t\" \"http\"\r\n    echo uri.scheme()\r\n\r\n\t\" \"d.hatena.ne.jp\"\r\n    echo uri.host()\r\n\r\n\t\" \"\/tyru\/20100619\/git_push_vim_plugins_to_github\"\r\n    echo uri.path()\r\n\r\n\t\" \"\/\/d.hatena.ne.jp\/tyru\/20100619\/git_push_vim_plugins_to_github\"\r\n    echo uri.opaque()\r\n\r\n\t\" \"c\"\r\n    echo uri.fragment()\r\n\r\n\r\n\r\nRepository: http:\/\/github.com\/tyru\/urilib.vim","4":"    let uri = urilib#new('http:\/\/twitter.com\/tyru')\r\n\r\n\t\" \"http\"\r\n    echo uri.scheme()\r\n\r\n\t\" \"twitter.com\"\r\n    echo uri.host()\r\n\r\n\t\" \"\/tyru\"\r\n    echo uri.path()\r\n\r\n\t\" \"\/\/twitter.com\/tyru\"\r\n    echo uri.opaque()\r\n\r\n\t\" \"\"\r\n    echo uri.fragment()\r\n\r\n\r\n    let uri = urilib#new('http:\/\/d.hatena.ne.jp\/tyru\/20100619\/git_push_vim_plugins_to_github#c')\r\n\r\n\t\" \"http\"\r\n    echo uri.scheme()\r\n\r\n\t\" \"d.hatena.ne.jp\"\r\n    echo uri.host()\r\n\r\n\t\" \"\/tyru\/20100619\/git_push_vim_plugins_to_github\"\r\n    echo uri.path()\r\n\r\n\t\" \"\/\/d.hatena.ne.jp\/tyru\/20100619\/git_push_vim_plugins_to_github\"\r\n    echo uri.opaque()\r\n\r\n\t\" \"c\"\r\n    echo uri.fragment()\r\n\r\n\r\n\r\nRepository: http:\/\/github.com\/tyru\/urilib.vim","install_details":"","5":"","first_name":"tyru","6":"tyru","last_name":" ","7":" ","releases":[{"0":"3489","vim_version":"7.0","1":"7.0","script_version":"0.0.0","2":"0.0.0","version_comment":"Initial upload","3":"Initial upload","package":"urilib.zip","4":"urilib.zip","src_id":"15179","5":"15179","creation_date":"1299671703","6":"1299671703"}]},"3488":{"script_id":"3488","0":"3488","script_name":"rebar","1":"rebar","script_type":"utility","2":"utility","summary":"Vim plugin for using Rebar commands conveniently inside Vim","3":"Vim plugin for using Rebar commands conveniently inside Vim","description":"Vim plugin for using Rebar commands conveniently inside Vim.\r\n\r\nCurrently only compile inside a \\\"simple\\\" (no sub_dirs) project works with the compiler window hooked up to compilation error messages.  Also has Rebar submenu plugin for NERDTree.\r\n\r\nNext up:\r\n* full implementation of create rebar subcommand with prompts and template autocomplete.\r\n* align Erlang compilation error messages in sub_dir projects of root project as links in compiler error window.\r\n* more coming soon...\r\n\r\n","4":"Vim plugin for using Rebar commands conveniently inside Vim.\r\n\r\nCurrently only compile inside a \\\"simple\\\" (no sub_dirs) project works with the compiler window hooked up to compilation error messages.  Also has Rebar submenu plugin for NERDTree.\r\n\r\nNext up:\r\n* full implementation of create rebar subcommand with prompts and template autocomplete.\r\n* align Erlang compilation error messages in sub_dir projects of root project as links in compiler error window.\r\n* more coming soon...\r\n\r\n","install_details":"The Git repository website is located at https:\/\/github.com\/mbbx6spp\/vim-rebar\/","5":"The Git repository website is located at https:\/\/github.com\/mbbx6spp\/vim-rebar\/","first_name":"Susan","6":"Susan","last_name":"Potter","7":"Potter","releases":[{"0":"3488","vim_version":"7.0","1":"7.0","script_version":"0.1.0","2":"0.1.0","version_comment":"Initial upload","3":"Initial upload","package":"mbbx6spp-vim-rebar-v0.1.0.tar.gz","4":"mbbx6spp-vim-rebar-v0.1.0.tar.gz","src_id":"15178","5":"15178","creation_date":"1299621752","6":"1299621752"}]},"3487":{"script_id":"3487","0":"3487","script_name":"reporoot.vim","1":"reporoot.vim","script_type":"utility","2":"utility","summary":"Change directory to the root of the source code repository","3":"Change directory to the root of the source code repository","description":"The reporoot plugin attempts to find the nearest repository root and change the directory to it.","4":"The reporoot plugin attempts to find the nearest repository root and change the directory to it.","install_details":"Extract to ~\/.vim","5":"Extract to ~\/.vim","first_name":"Jeremy","6":"Jeremy","last_name":"Cantrell","7":"Cantrell","releases":[{"0":"3487","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"jmcantrell-vim-reporoot-b40bee2.zip","4":"jmcantrell-vim-reporoot-b40bee2.zip","src_id":"15176","5":"15176","creation_date":"1299561478","6":"1299561478"}]},"3486":{"script_id":"3486","0":"3486","script_name":"virtualenv.vim","1":"virtualenv.vim","script_type":"ftplugin","2":"ftplugin","summary":"Work with python virtualenvs within vim","3":"Work with python virtualenvs within vim","description":"The virtualenv plugin allows you to activate and deactivate a virtualenv within a live Vim session.\r\n\r\nGitHub URL: https:\/\/github.com\/jmcantrell\/vim-virtualenv","4":"The virtualenv plugin allows you to activate and deactivate a virtualenv within a live Vim session.\r\n\r\nGitHub URL: https:\/\/github.com\/jmcantrell\/vim-virtualenv","install_details":"Extract to ~\/.vim","5":"Extract to ~\/.vim","first_name":"Jeremy","6":"Jeremy","last_name":"Cantrell","7":"Cantrell","releases":[{"0":"3486","vim_version":"7.0","1":"7.0","script_version":"0.2","2":"0.2","version_comment":"A number of improvements from github collaborators.","3":"A number of improvements from github collaborators.","package":"jmcantrell-vim-virtualenv-0cc7614.zip","4":"jmcantrell-vim-virtualenv-0cc7614.zip","src_id":"18269","5":"18269","creation_date":"1342410329","6":"1342410329"},{"0":"3486","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"jmcantrell-vim-virtualenv-1d63500.zip","4":"jmcantrell-vim-virtualenv-1d63500.zip","src_id":"15173","5":"15173","creation_date":"1299561151","6":"1299561151"}]},"3485":{"script_id":"3485","0":"3485","script_name":"phrase.vim","1":"phrase.vim","script_type":"utility","2":"utility","summary":"gather useful phrase, refer it whenever you want.","3":"gather useful phrase, refer it whenever you want.","description":"** Currently I only tested Linux and Mac OS X environment, so Windows is not supported ***\r\n\r\nWhat is this?\r\n==================================\r\nphrase.vim support.\r\n\r\n  * gather userful phrase to consolidated file\r\n  * easily open that phrase file\r\n  * view someone's phrase easily\r\n  * search phrases with [unite.vim](https:\/\/github.com\/Shougo\/unite.vim) interface.\r\n\r\nI mainly use this plugin for gather useful phrase while *reading* source codes.\r\nThen recall that phrase when *writing*.\r\n\r\nAnd intending to share several programming idiom socially.\r\n\r\nTry\r\n================================\r\n\r\nCreate phrase directory.\r\nCopy phrase example file to that directory.\r\n\r\n      $ mkdir $HOME\/.vim\/phrase\/$USER\r\n      $ cp example\/* $HOME\/.vim\/phrase\/$USER\/\r\n\r\nShow phrase then enter to jump to that title\r\n\r\n      :PhraseEdit pl\r\n\r\nVisually select text in buffer then create phrase from that text.\r\n\r\n      :'<,'>PhraseCreate<CR>\r\n\r\nIf you have unite.vim\r\n      :Unite phrase<CR>\r\n\r\nUsage\r\n==============================\r\nSee [help](https:\/\/github.com\/t9md\/vim-phrase\/blob\/master\/doc\/phrase.txt)\r\n\r\nSample phrases\r\n==============================\r\nUnite phrase search all phrase under directory in &rtp, means you can manage  \r\nphrase from others with [vundle](https:\/\/github.com\/gmarik\/vundle)   \r\nor [vim-pathogen](https:\/\/github.com\/tpope\/vim-pathogen).\r\n\r\n* [t9md\/phrase-t9md](https:\/\/github.com\/t9md\/phrase-t9md)\r\n\r\nLatest Version\r\n----------------------------------\r\nhttp:\/\/github.com\/t9md\/vim-phrase\r\n","4":"** Currently I only tested Linux and Mac OS X environment, so Windows is not supported ***\r\n\r\nWhat is this?\r\n==================================\r\nphrase.vim support.\r\n\r\n  * gather userful phrase to consolidated file\r\n  * easily open that phrase file\r\n  * view someone's phrase easily\r\n  * search phrases with [unite.vim](https:\/\/github.com\/Shougo\/unite.vim) interface.\r\n\r\nI mainly use this plugin for gather useful phrase while *reading* source codes.\r\nThen recall that phrase when *writing*.\r\n\r\nAnd intending to share several programming idiom socially.\r\n\r\nTry\r\n================================\r\n\r\nCreate phrase directory.\r\nCopy phrase example file to that directory.\r\n\r\n      $ mkdir $HOME\/.vim\/phrase\/$USER\r\n      $ cp example\/* $HOME\/.vim\/phrase\/$USER\/\r\n\r\nShow phrase then enter to jump to that title\r\n\r\n      :PhraseEdit pl\r\n\r\nVisually select text in buffer then create phrase from that text.\r\n\r\n      :'<,'>PhraseCreate<CR>\r\n\r\nIf you have unite.vim\r\n      :Unite phrase<CR>\r\n\r\nUsage\r\n==============================\r\nSee [help](https:\/\/github.com\/t9md\/vim-phrase\/blob\/master\/doc\/phrase.txt)\r\n\r\nSample phrases\r\n==============================\r\nUnite phrase search all phrase under directory in &rtp, means you can manage  \r\nphrase from others with [vundle](https:\/\/github.com\/gmarik\/vundle)   \r\nor [vim-pathogen](https:\/\/github.com\/tpope\/vim-pathogen).\r\n\r\n* [t9md\/phrase-t9md](https:\/\/github.com\/t9md\/phrase-t9md)\r\n\r\nLatest Version\r\n----------------------------------\r\nhttp:\/\/github.com\/t9md\/vim-phrase\r\n","install_details":"unzip it to $HOME\/.vim\/","5":"unzip it to $HOME\/.vim\/","first_name":"t9","6":"t9","last_name":"md","7":"md","releases":[{"0":"3485","vim_version":"7.0","1":"7.0","script_version":"0.5","2":"0.5","version_comment":"2011-08-21: v0.5\r\n\t- update help\r\n\t- :PhraseList no longer accept argument(for simplicity).\r\n\t- :PhraseCreate no longer accept argument(for simplicity).\r\n\t- b:phrase_filetype is renamed as b:phrase_ext.\r\n2011-08-04: v0.4\r\n\t- add sorter_phrase for unite.","3":"2011-08-21: v0.5\r\n\t- update help\r\n\t- :PhraseList no longer accept argument(for simplicity).\r\n\t- :PhraseCreate no longer accept argument(for simplicity).\r\n\t- b:phrase_filetype is renamed as b:phrase_ext.\r\n2011-08-04: v0.4\r\n\t- add sorter_phrase for unite.","package":"vim-phrase-0.5.zip","4":"vim-phrase-0.5.zip","src_id":"16308","5":"16308","creation_date":"1313857305","6":"1313857305"},{"0":"3485","vim_version":"7.2","1":"7.2","script_version":"0.2","2":"0.2","version_comment":"0.2\t2011-03-10\r\n\t- Support multiple languages\r\n\t- Change configuration variables.\r\n          g:phrase_dir is no longer used.\r\n          Use g:phrase_auther and g:phrase_basedir\r\n          Use g:phrase_ft_tbl to customise filetype extension map and comment\r\n          string.\r\n\t- Eliminate comment string when creating PhraseList.\r\n","3":"0.2\t2011-03-10\r\n\t- Support multiple languages\r\n\t- Change configuration variables.\r\n          g:phrase_dir is no longer used.\r\n          Use g:phrase_auther and g:phrase_basedir\r\n          Use g:phrase_ft_tbl to customise filetype extension map and comment\r\n          string.\r\n\t- Eliminate comment string when creating PhraseList.\r\n","package":"phrase.zip","4":"phrase.zip","src_id":"15182","5":"15182","creation_date":"1299686664","6":"1299686664"},{"0":"3485","vim_version":"7.0","1":"7.0","script_version":"0.1.1","2":"0.1.1","version_comment":"fix help's url","3":"fix help's url","package":"phrase.zip","4":"phrase.zip","src_id":"15167","5":"15167","creation_date":"1299435118","6":"1299435118"}]},"3484":{"script_id":"3484","0":"3484","script_name":"PyREPL.vim","1":"PyREPL.vim","script_type":"utility","2":"utility","summary":"PyREPL.vim is a plugin that provides a way to run a Python REPL inside buffer.","3":"PyREPL.vim is a plugin that provides a way to run a Python REPL inside buffer.","description":"Example use:\r\nYou can watch videos of the plugin in action at http:\/\/www.youtube.com\/user\/nadgobp#p\/u.\r\n\r\nUsage:\r\nInside any buffer use \\r to toggle the REPL on or off. Toggling it on will create a new empty buffer every single time.\r\n\r\nGit repository: https:\/\/github.com\/Bogdanp\/pyrepl.vim","4":"Example use:\r\nYou can watch videos of the plugin in action at http:\/\/www.youtube.com\/user\/nadgobp#p\/u.\r\n\r\nUsage:\r\nInside any buffer use \\r to toggle the REPL on or off. Toggling it on will create a new empty buffer every single time.\r\n\r\nGit repository: https:\/\/github.com\/Bogdanp\/pyrepl.vim","install_details":"Use pathogen.vim(vimscript #2332) and clone the git repository into your bundle folder or copy pyrepl.vim to your plugin folder.","5":"Use pathogen.vim(vimscript #2332) and clone the git repository into your bundle folder or copy pyrepl.vim to your plugin folder.","first_name":"Bogdan","6":"Bogdan","last_name":"Popa","7":"Popa","releases":[{"0":"3484","vim_version":"7.0","1":"7.0","script_version":"0.2.1","2":"0.2.1","version_comment":" ","3":" ","package":"pyrepl.vim","4":"pyrepl.vim","src_id":"17869","5":"17869","creation_date":"1336160614","6":"1336160614"},{"0":"3484","vim_version":"7.0","1":"7.0","script_version":"0.1.7","2":"0.1.7","version_comment":"Version 0.1.7:\r\n\r\n* Add indentation level matching.","3":"Version 0.1.7:\r\n\r\n* Add indentation level matching.","package":"pyrepl.vim","4":"pyrepl.vim","src_id":"15667","5":"15667","creation_date":"1305730192","6":"1305730192"},{"0":"3484","vim_version":"7.0","1":"7.0","script_version":"0.1.6","2":"0.1.6","version_comment":"Version 0.1.6:\r\n\r\n* Fix bug when using multiline strings inside a block.\r\n* Remove error message when VIM is not compiled with +python.\r\n* Remain in insert mode after showing the prompt.\r\n* Fix module reloader bug.\r\n* Start in insert mode by default.","3":"Version 0.1.6:\r\n\r\n* Fix bug when using multiline strings inside a block.\r\n* Remove error message when VIM is not compiled with +python.\r\n* Remain in insert mode after showing the prompt.\r\n* Fix module reloader bug.\r\n* Start in insert mode by default.","package":"pyrepl.vim","4":"pyrepl.vim","src_id":"15666","5":"15666","creation_date":"1305728948","6":"1305728948"},{"0":"3484","vim_version":"7.0","1":"7.0","script_version":"0.1.5","2":"0.1.5","version_comment":"Version 0.1.5:\r\n\r\n* Add duplicate_line method and fix reload_module so it only inserts a new prompt if it has to. \r\n* Add support for multiline strings.","3":"Version 0.1.5:\r\n\r\n* Add duplicate_line method and fix reload_module so it only inserts a new prompt if it has to. \r\n* Add support for multiline strings.","package":"pyrepl.vim","4":"pyrepl.vim","src_id":"15288","5":"15288","creation_date":"1301066282","6":"1301066282"},{"0":"3484","vim_version":"7.0","1":"7.0","script_version":"0.1.4","2":"0.1.4","version_comment":"Version 0.1.4:\r\n\r\n* Fix double prompt bug.","3":"Version 0.1.4:\r\n\r\n* Fix double prompt bug.","package":"pyrepl.vim","4":"pyrepl.vim","src_id":"15231","5":"15231","creation_date":"1300336987","6":"1300336987"},{"0":"3484","vim_version":"7.0","1":"7.0","script_version":"0.1.3","2":"0.1.3","version_comment":"Version 0.1.3:\r\n\r\n* Add support for decorators.\r\n* Change the way prompt insertion is handled and expose the toggle function globally.\r\n* Refactor insert_prompt function for clarity.\r\n* Add functionality to reload modules easily.\r\n* Only remap <leader>R to reload_module for the REPL buffer.\r\n","3":"Version 0.1.3:\r\n\r\n* Add support for decorators.\r\n* Change the way prompt insertion is handled and expose the toggle function globally.\r\n* Refactor insert_prompt function for clarity.\r\n* Add functionality to reload modules easily.\r\n* Only remap <leader>R to reload_module for the REPL buffer.\r\n","package":"pyrepl.vim","4":"pyrepl.vim","src_id":"15227","5":"15227","creation_date":"1300268057","6":"1300268057"},{"0":"3484","vim_version":"7.0","1":"7.0","script_version":"0.1.2","2":"0.1.2","version_comment":"Initial upload","3":"Initial upload","package":"pyrepl.vim","4":"pyrepl.vim","src_id":"15164","5":"15164","creation_date":"1299404263","6":"1299404263"}]},"3483":{"script_id":"3483","0":"3483","script_name":"IPC syntax highlight","1":"IPC syntax highlight","script_type":"syntax","2":"syntax","summary":"Syntax file for Informatica Power Center log files","3":"Syntax file for Informatica Power Center log files","description":"Syntax file for Informatica Power Center log files","4":"Syntax file for Informatica Power Center log files","install_details":"","5":"","first_name":"Zhidenkov","6":"Zhidenkov","last_name":"Andrey","7":"Andrey","releases":[{"0":"3483","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"ipclog.vim","4":"ipclog.vim","src_id":"15159","5":"15159","creation_date":"1299248254","6":"1299248254"}]},"3482":{"script_id":"3482","0":"3482","script_name":"vim-remote","1":"vim-remote","script_type":"utility","2":"utility","summary":"Vim clientserver protocol library","3":"Vim clientserver protocol library","description":"Vim clientserver protocol library\r\n\r\nLicense: VIM LICENSE (see :help license)\r\n\r\nsupported:\r\n  serverlist()\r\n  remote_expr()\r\n\r\nnot supported:\r\n  remote_foreground()\r\n  remote_peek()\r\n  remote_read()\r\n  remote_send()\r\n  server2client()\r\n\r\n\r\nExample:\r\n\r\nCompile vim-remote library.\r\n\r\n  Linux:\r\n    $ make -f Makefile.x11\r\n\r\n  Windows (VC++):\r\n    > nmake -f Makefile.msvc\r\n\r\n  Windows (MinGW):\r\n    > make -f Makefile.mingw\r\n\r\nStart the sample python server.\r\n\r\n  $ python main.py --servername py --server\r\n\r\nYou can evaluate Python expression with remote_expr().\r\nStart Vim and execute the following command.\r\n\r\n  :echo remote_expr('py', 'print(\"This is Python expression\")')\r\n  None\r\n\r\n\"None\" is result of Python expression.\r\nAnd the message will be displayed on the console.\r\n\r\nAlso, it is possible to call client function from server.\r\n\r\n  :function! F()\r\n  :  echo \"This is Vim expression\"\r\n  :  return \"And this is result from Vim\"\r\n  :endfunction\r\n  :let pyexpr = printf('remote_expr(\"%s\", \"F()\")', v:servername)\r\n  :let result = remote_expr('py', pyexpr)\r\n  This is Vim expression\r\n  :echo result\r\n  And this is result from Vim\r\n\r\n\r\nLatest source: https:\/\/github.com\/ynkdir\/vim-remote","4":"Vim clientserver protocol library\r\n\r\nLicense: VIM LICENSE (see :help license)\r\n\r\nsupported:\r\n  serverlist()\r\n  remote_expr()\r\n\r\nnot supported:\r\n  remote_foreground()\r\n  remote_peek()\r\n  remote_read()\r\n  remote_send()\r\n  server2client()\r\n\r\n\r\nExample:\r\n\r\nCompile vim-remote library.\r\n\r\n  Linux:\r\n    $ make -f Makefile.x11\r\n\r\n  Windows (VC++):\r\n    > nmake -f Makefile.msvc\r\n\r\n  Windows (MinGW):\r\n    > make -f Makefile.mingw\r\n\r\nStart the sample python server.\r\n\r\n  $ python main.py --servername py --server\r\n\r\nYou can evaluate Python expression with remote_expr().\r\nStart Vim and execute the following command.\r\n\r\n  :echo remote_expr('py', 'print(\"This is Python expression\")')\r\n  None\r\n\r\n\"None\" is result of Python expression.\r\nAnd the message will be displayed on the console.\r\n\r\nAlso, it is possible to call client function from server.\r\n\r\n  :function! F()\r\n  :  echo \"This is Vim expression\"\r\n  :  return \"And this is result from Vim\"\r\n  :endfunction\r\n  :let pyexpr = printf('remote_expr(\"%s\", \"F()\")', v:servername)\r\n  :let result = remote_expr('py', pyexpr)\r\n  This is Vim expression\r\n  :echo result\r\n  And this is result from Vim\r\n\r\n\r\nLatest source: https:\/\/github.com\/ynkdir\/vim-remote","install_details":"","5":"","first_name":"Yukihiro","6":"Yukihiro","last_name":"Nakadaira","7":"Nakadaira","releases":[{"0":"3482","vim_version":"7.3","1":"7.3","script_version":"1.1","2":"1.1","version_comment":"Changed API\r\nAdded sample ruby server","3":"Changed API\r\nAdded sample ruby server","package":"vim-remote.zip","4":"vim-remote.zip","src_id":"15162","5":"15162","creation_date":"1299335394","6":"1299335394"},{"0":"3482","vim_version":"7.3","1":"7.3","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"vim-remote.zip","4":"vim-remote.zip","src_id":"15157","5":"15157","creation_date":"1299236056","6":"1299236056"}]},"3481":{"script_id":"3481","0":"3481","script_name":"Atom","1":"Atom","script_type":"color scheme","2":"color scheme","summary":"Color scheme designed to be very readable in both light and dark environments.","3":"Color scheme designed to be very readable in both light and dark environments.","description":"Atom is a theme that was designed to be very readable in both light and dark environments. It concentrates on being easy on the eyes whilst distinguishing different syntax elements.\r\n\r\nAll important screenshots can be found at: http:\/\/www.gregsexton.org\/vim-color-schemes\/atom-color\/\r\n\r\nItalics are not used in this theme. \r\n\r\nCurrently Atom is GVim only.\r\n\r\nThere is now a GitHub repository for Atom at: https:\/\/github.com\/gregsexton\/Atom","4":"Atom is a theme that was designed to be very readable in both light and dark environments. It concentrates on being easy on the eyes whilst distinguishing different syntax elements.\r\n\r\nAll important screenshots can be found at: http:\/\/www.gregsexton.org\/vim-color-schemes\/atom-color\/\r\n\r\nItalics are not used in this theme. \r\n\r\nCurrently Atom is GVim only.\r\n\r\nThere is now a GitHub repository for Atom at: https:\/\/github.com\/gregsexton\/Atom","install_details":"Just drop in to your ~\/.vim\/colors directory or ~\/vimfiles\/colors if on Windows. ","5":"Just drop in to your ~\/.vim\/colors directory or ~\/vimfiles\/colors if on Windows. ","first_name":"Greg","6":"Greg","last_name":"Sexton","7":"Sexton","releases":[{"0":"3481","vim_version":"5.7","1":"5.7","script_version":"1.1","2":"1.1","version_comment":"Reduced Normal contrast.\r\nAdded custom diff colors.\r\nAdded very subtle ColorColumn highlight.","3":"Reduced Normal contrast.\r\nAdded custom diff colors.\r\nAdded very subtle ColorColumn highlight.","package":"atom.vim","4":"atom.vim","src_id":"15570","5":"15570","creation_date":"1304367804","6":"1304367804"},{"0":"3481","vim_version":"5.7","1":"5.7","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"atom.vim","4":"atom.vim","src_id":"15154","5":"15154","creation_date":"1299187552","6":"1299187552"}]},"3480":{"script_id":"3480","0":"3480","script_name":"asp.net","1":"asp.net","script_type":"syntax","2":"syntax","summary":"with javascript support","3":"with javascript support","description":"based on Mark Feeney script, with javascript support","4":"based on Mark Feeney script, with javascript support","install_details":"copy the file to syntax folder,\r\nthen\r\nadd\r\nau BufRead,BufNewFile *.aspx,*.asmx,*.ascx      set aspnet \r\nin filetype.vim","5":"copy the file to syntax folder,\r\nthen\r\nadd\r\nau BufRead,BufNewFile *.aspx,*.asmx,*.ascx      set aspnet \r\nin filetype.vim","first_name":"biruh","6":"biruh","last_name":"mekonnen","7":"mekonnen","releases":[{"0":"3480","vim_version":"7.0","1":"7.0","script_version":"1","2":"1","version_comment":"Initial upload","3":"Initial upload","package":"aspnet.vim","4":"aspnet.vim","src_id":"15151","5":"15151","creation_date":"1299149916","6":"1299149916"}]},"3479":{"script_id":"3479","0":"3479","script_name":"makebg","1":"makebg","script_type":"utility","2":"utility","summary":"Shell script to perform make in the background.","3":"Shell script to perform make in the background.","description":"Use: makebg VIMSERVER MAKEPRG MAKEEF\r\nInside Vim, use this mapping for Fn12:\r\nmap <F12> :exec \"!makebg\" v:servername \"'\" . &makeprg . \"'\" &makeef<CR><CR>\r\n                                                                             \r\nExecute make in the background. Vim will automatically open the quickfix error window and jump to the first error or warning when make is done. If make is successful, you will just see a message. You can choose to ignore warnings by commenting out LIST_WARNINGS=true inside the script. The mapping enables you to use your custom makeprg and makeef options, otherwise default values are used. For example, you can use ninja instead of make by setting makeprg appropriately. Errors from the current run of make are prepended to the previous errors.  To clear previous errors, use this mapping for Shift + Fn12:\r\nmap <S-F12> :exec \"!rm \" &makeef \"; makebg\" v:servername \"'\" . &makeprg . \"'\"  &makeef<CR><CR>\r\nAdd these mappings to your vimrc for convenience.\r\n\r\nThis is Unix only (GNU\/Linux, *BSD, Solaris, Mac OSX, Cygwin)\r\n","4":"Use: makebg VIMSERVER MAKEPRG MAKEEF\r\nInside Vim, use this mapping for Fn12:\r\nmap <F12> :exec \"!makebg\" v:servername \"'\" . &makeprg . \"'\" &makeef<CR><CR>\r\n                                                                             \r\nExecute make in the background. Vim will automatically open the quickfix error window and jump to the first error or warning when make is done. If make is successful, you will just see a message. You can choose to ignore warnings by commenting out LIST_WARNINGS=true inside the script. The mapping enables you to use your custom makeprg and makeef options, otherwise default values are used. For example, you can use ninja instead of make by setting makeprg appropriately. Errors from the current run of make are prepended to the previous errors.  To clear previous errors, use this mapping for Shift + Fn12:\r\nmap <S-F12> :exec \"!rm \" &makeef \"; makebg\" v:servername \"'\" . &makeprg . \"'\"  &makeef<CR><CR>\r\nAdd these mappings to your vimrc for convenience.\r\n\r\nThis is Unix only (GNU\/Linux, *BSD, Solaris, Mac OSX, Cygwin)\r\n","install_details":"Put the script somewhere in your path (eg: \/usr\/local\/bin or ~\/bin) and make it executable:\r\nchmod +x makebg","5":"Put the script somewhere in your path (eg: \/usr\/local\/bin or ~\/bin) and make it executable:\r\nchmod +x makebg","first_name":"Sameer","6":"Sameer","last_name":"Sheorey","7":"Sheorey","releases":[{"0":"3479","vim_version":"6.0","1":"6.0","script_version":"1.2","2":"1.2","version_comment":"Error list is not opened for successful builds. This can be controlled with an option for warnings. Following suggestion from http:\/\/vim.wikia.com\/wiki\/Script:3479","3":"Error list is not opened for successful builds. This can be controlled with an option for warnings. Following suggestion from http:\/\/vim.wikia.com\/wiki\/Script:3479","package":"makebg","4":"makebg","src_id":"22639","5":"22639","creation_date":"1416629164","6":"1416629164"},{"0":"3479","vim_version":"6.0","1":"6.0","script_version":"1.1","2":"1.1","version_comment":"Date prepended to error list","3":"Date prepended to error list","package":"makebg","4":"makebg","src_id":"15392","5":"15392","creation_date":"1302040665","6":"1302040665"},{"0":"3479","vim_version":"6.0","1":"6.0","script_version":"1","2":"1","version_comment":"Initial upload","3":"Initial upload","package":"makebg","4":"makebg","src_id":"15149","5":"15149","creation_date":"1299102580","6":"1299102580"}]},"3478":{"script_id":"3478","0":"3478","script_name":"robokai","1":"robokai","script_type":"color scheme","2":"color scheme","summary":"A molokai-based color scheme for terminal vim","3":"A molokai-based color scheme for terminal vim","description":"SCREENSHOT:\r\nhttp:\/\/imgur.com\/7IyF4\r\n\r\nrobokai is inspired by molokai but suited for terminal vim usage. Feel free to send feedback. Enjoy!\r\n","4":"SCREENSHOT:\r\nhttp:\/\/imgur.com\/7IyF4\r\n\r\nrobokai is inspired by molokai but suited for terminal vim usage. Feel free to send feedback. Enjoy!\r\n","install_details":"","5":"","first_name":"Brian","6":"Brian","last_name":"Mock","7":"Mock","releases":[{"0":"3478","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"robokai.vim","4":"robokai.vim","src_id":"15145","5":"15145","creation_date":"1299054298","6":"1299054298"}]},"3477":{"script_id":"3477","0":"3477","script_name":"bad apple","1":"bad apple","script_type":"game","2":"game","summary":"bad apple - vim ver","3":"bad apple - vim ver","description":"original video:\r\nhttp:\/\/www.youtube.com\/watch?v=VzEUeWnV73U\r\n\r\nYet another Bad Apple doujin","4":"original video:\r\nhttp:\/\/www.youtube.com\/watch?v=VzEUeWnV73U\r\n\r\nYet another Bad Apple doujin","install_details":"unzip it anywhere, open GVIM in that folder, type\r\n:so badapple.vim","5":"unzip it anywhere, open GVIM in that folder, type\r\n:so badapple.vim","first_name":"Ran","6":"Ran","last_name":"Bi","7":"Bi","releases":[{"0":"3477","vim_version":"7.0","1":"7.0","script_version":"0.71","2":"0.71","version_comment":"Zip version, in case you don't have 7z.","3":"Zip version, in case you don't have 7z.","package":"badApple.zip","4":"badApple.zip","src_id":"19410","5":"19410","creation_date":"1358832191","6":"1358832191"},{"0":"3477","vim_version":"7.0","1":"7.0","script_version":"0.7","2":"0.7","version_comment":"using jp2a util to convert jpeg image into ascii file. Contains much larger char set, which produces much better single frame quality(hopefully). To reduce storage, it decreases frame rate. Looks fluent when sleep time is less than 70ms between two frames. Any requirement, email me","3":"using jp2a util to convert jpeg image into ascii file. Contains much larger char set, which produces much better single frame quality(hopefully). To reduce storage, it decreases frame rate. Looks fluent when sleep time is less than 70ms between two frames. Any requirement, email me","package":"badApple.7z","4":"badApple.7z","src_id":"15246","5":"15246","creation_date":"1300466416","6":"1300466416"},{"0":"3477","vim_version":"7.0","1":"7.0","script_version":"0.6","2":"0.6","version_comment":"higher resolution\r\nfour character based grey scale\r\nPlease use gvim instead of vim to run this and latter version ","3":"higher resolution\r\nfour character based grey scale\r\nPlease use gvim instead of vim to run this and latter version ","package":"badApple.zip","4":"badApple.zip","src_id":"15147","5":"15147","creation_date":"1299082726","6":"1299082726"},{"0":"3477","vim_version":"7.0","1":"7.0","script_version":"0.51","2":"0.51","version_comment":"change file format to unix.","3":"change file format to unix.","package":"badapple.zip","4":"badapple.zip","src_id":"15143","5":"15143","creation_date":"1299031652","6":"1299031652"},{"0":"3477","vim_version":"7.0","1":"7.0","script_version":"0.5","2":"0.5","version_comment":"Initial upload","3":"Initial upload","package":"badapple.zip","4":"badapple.zip","src_id":"15141","5":"15141","creation_date":"1298997033","6":"1298997033"}]},"3476":{"script_id":"3476","0":"3476","script_name":"bitly.vim","1":"bitly.vim","script_type":"utility","2":"utility","summary":"utility for bit.ly","3":"utility for bit.ly","description":"\r\nlastest version is https:\/\/github.com\/basyura\/bitly.vim\r\n\r\n==============================================================================\r\n\r\nCONTENTS\t\t\t\t\t*bitly-contents*\r\n\r\nIntroduction\t\t|bitly-introduction|\r\nInstall\t\t\t|bitly-install|\r\nVariables\t\t|bitly-variables|\r\nUsage\t\t\t|bitly-usage|\r\n\r\n==============================================================================\r\nINTRODUCTION\t\t\t\t\t*bitly-introduction*\r\n\r\nbitly.vim is a library of bit.ly.\r\nsupport API version 3.0\r\n\r\n  bit.ly is a utility that allows users to shorten a long URL, share it, \r\n  and then track the resulting usage. (http:\/\/bit.ly\/)\r\n\r\n  bit.ly exposes its data via an Application Programming Interface (API),\r\n  so developers can interact in a programmatic way with the bit.ly website.\r\n  (http:\/\/code.google.com\/p\/bitly-api\/wiki\/ApiDocumentation)\r\n\r\nbitly.vim bundles webapi-vim.\r\n(https:\/\/github.com\/mattn\/webapi-vim\/)\r\n\r\n==============================================================================\r\nINSTALL\t\t\t\t\t\t*bitly-install*\r\n\r\nInstall the distributed files into Vim script directory which is usually\r\n~\/.vim\/, or $HOME\/vimfiles on Windows.\r\n\r\n==============================================================================\r\nVARIABLES\t\t\t\t\t*bitly-variables*\r\n\r\ng:bitly_login\t\t\t\t\t*g:bitly_login*\r\n\t\tbit.ly login id.\r\n\t\tif you want to use your login id , set this.\r\n\r\ng:bitly_api_key\t\t\t\t\t*g:bitly_api_key*\r\n\t\tbit.ly api key.\r\n\t\tif you want to use your api key , set this.\r\n\r\n==============================================================================\r\nUSAGE\t\t\t\t\t\t*bitly-usage*\r\n\t\r\nshorten\r\n\r\n\tthis method returns a short one.\r\n\treturn is a dict that converted from xml.\r\n\txml format is written in api document.\r\n>\r\n\tlet info = bitly#shorten('http:\/\/google.com')\r\n\techo info.status_code \"=> 200\r\n\techo info.status_txt  \"=> OK\r\n\techo info.url         \"=> http:\/\/bit.ly\/gzJQrA\r\n\techo info.global_hash \"=> zzzzzzz\r\n\techo info.long_url    \"=> http:\/\/google.com\r\n\techo info.new_hash    \"=> 1\r\n<\r\nexpand\r\n\t\r\n\tthis method returns back the target url.\r\n\tthis method returns dict or list that converted from xml.\r\n\txml format is written in api document.\r\n>\r\n\tlet expand = bitly#expand('http:\/\/bit.ly\/fHgr3a')\r\n\tcall expand.status_code \"=> 200\r\n\tcall expand.long_url    \"=> http:\/\/basyura.org\r\n\tcall expand.short_url   \"=> http:\/\/bit.ly\/fHgr3a\r\n\t\r\n\tlet expands = bitly#expand(\r\n\t\t\\ ['http:\/\/bit.ly\/fHgr3a' , 'http:\/\/bit.ly\/g2n8tN'])\r\n\tcall expands[0].status_code \"=> 200\r\n\tcall expands[0].long_url    \"=> http:\/\/basyura.org\r\n\tcall expands[0].short_url   \"=> http:\/\/bit.ly\/fHgr3a\r\n\tcall expands[1].status_code \"=> 200\r\n\tcall expands[1].long_url    \"=> http:\/\/google.com\r\n\tcall expands[1].short_url   \"=> http:\/\/bit.ly\/g2n8tN\r\n<\r\nclicks\r\n\r\n\tthis method returns statistics list about the clicks on that link. \r\n\treturn is converted from xml.\r\n\txml format is written in api document.\r\n>\r\n\tlet clicks = bitly#clicks('http:\/\/bit.ly\/fHgr3a')\r\n<\r\nreferrers\r\n\r\n\tthis method returns a list of referring sites\r\n\tfor a specified bit.ly short link, \r\n\tand the number of clicks per referrer. \r\n\treturn is converted from xml.\r\n\txml format is written in api document.\r\n>\r\n\tlet referrers = bitly#referrers('http:\/\/bit.ly\/djZ9g4')\r\n\tfor v in referrers\r\n\t  if has_key(v , 'referrer')\r\n\t    echo v.referrer . ' ' . v.clicks\r\n\t  else\r\n\t    echo v.referrer_app . ' ' . v.clicks\r\n\t  endif\r\n\tendfor\r\n\r\n\tfor v in bitly#countries('http:\/\/bit.ly\/djZ9g4')\r\n\t  echo v.country . ' ' . v.clicks\r\n\tendfor\r\n<\r\n\r\n\r\n\r\n","4":"\r\nlastest version is https:\/\/github.com\/basyura\/bitly.vim\r\n\r\n==============================================================================\r\n\r\nCONTENTS\t\t\t\t\t*bitly-contents*\r\n\r\nIntroduction\t\t|bitly-introduction|\r\nInstall\t\t\t|bitly-install|\r\nVariables\t\t|bitly-variables|\r\nUsage\t\t\t|bitly-usage|\r\n\r\n==============================================================================\r\nINTRODUCTION\t\t\t\t\t*bitly-introduction*\r\n\r\nbitly.vim is a library of bit.ly.\r\nsupport API version 3.0\r\n\r\n  bit.ly is a utility that allows users to shorten a long URL, share it, \r\n  and then track the resulting usage. (http:\/\/bit.ly\/)\r\n\r\n  bit.ly exposes its data via an Application Programming Interface (API),\r\n  so developers can interact in a programmatic way with the bit.ly website.\r\n  (http:\/\/code.google.com\/p\/bitly-api\/wiki\/ApiDocumentation)\r\n\r\nbitly.vim bundles webapi-vim.\r\n(https:\/\/github.com\/mattn\/webapi-vim\/)\r\n\r\n==============================================================================\r\nINSTALL\t\t\t\t\t\t*bitly-install*\r\n\r\nInstall the distributed files into Vim script directory which is usually\r\n~\/.vim\/, or $HOME\/vimfiles on Windows.\r\n\r\n==============================================================================\r\nVARIABLES\t\t\t\t\t*bitly-variables*\r\n\r\ng:bitly_login\t\t\t\t\t*g:bitly_login*\r\n\t\tbit.ly login id.\r\n\t\tif you want to use your login id , set this.\r\n\r\ng:bitly_api_key\t\t\t\t\t*g:bitly_api_key*\r\n\t\tbit.ly api key.\r\n\t\tif you want to use your api key , set this.\r\n\r\n==============================================================================\r\nUSAGE\t\t\t\t\t\t*bitly-usage*\r\n\t\r\nshorten\r\n\r\n\tthis method returns a short one.\r\n\treturn is a dict that converted from xml.\r\n\txml format is written in api document.\r\n>\r\n\tlet info = bitly#shorten('http:\/\/google.com')\r\n\techo info.status_code \"=> 200\r\n\techo info.status_txt  \"=> OK\r\n\techo info.url         \"=> http:\/\/bit.ly\/gzJQrA\r\n\techo info.global_hash \"=> zzzzzzz\r\n\techo info.long_url    \"=> http:\/\/google.com\r\n\techo info.new_hash    \"=> 1\r\n<\r\nexpand\r\n\t\r\n\tthis method returns back the target url.\r\n\tthis method returns dict or list that converted from xml.\r\n\txml format is written in api document.\r\n>\r\n\tlet expand = bitly#expand('http:\/\/bit.ly\/fHgr3a')\r\n\tcall expand.status_code \"=> 200\r\n\tcall expand.long_url    \"=> http:\/\/basyura.org\r\n\tcall expand.short_url   \"=> http:\/\/bit.ly\/fHgr3a\r\n\t\r\n\tlet expands = bitly#expand(\r\n\t\t\\ ['http:\/\/bit.ly\/fHgr3a' , 'http:\/\/bit.ly\/g2n8tN'])\r\n\tcall expands[0].status_code \"=> 200\r\n\tcall expands[0].long_url    \"=> http:\/\/basyura.org\r\n\tcall expands[0].short_url   \"=> http:\/\/bit.ly\/fHgr3a\r\n\tcall expands[1].status_code \"=> 200\r\n\tcall expands[1].long_url    \"=> http:\/\/google.com\r\n\tcall expands[1].short_url   \"=> http:\/\/bit.ly\/g2n8tN\r\n<\r\nclicks\r\n\r\n\tthis method returns statistics list about the clicks on that link. \r\n\treturn is converted from xml.\r\n\txml format is written in api document.\r\n>\r\n\tlet clicks = bitly#clicks('http:\/\/bit.ly\/fHgr3a')\r\n<\r\nreferrers\r\n\r\n\tthis method returns a list of referring sites\r\n\tfor a specified bit.ly short link, \r\n\tand the number of clicks per referrer. \r\n\treturn is converted from xml.\r\n\txml format is written in api document.\r\n>\r\n\tlet referrers = bitly#referrers('http:\/\/bit.ly\/djZ9g4')\r\n\tfor v in referrers\r\n\t  if has_key(v , 'referrer')\r\n\t    echo v.referrer . ' ' . v.clicks\r\n\t  else\r\n\t    echo v.referrer_app . ' ' . v.clicks\r\n\t  endif\r\n\tendfor\r\n\r\n\tfor v in bitly#countries('http:\/\/bit.ly\/djZ9g4')\r\n\t  echo v.country . ' ' . v.clicks\r\n\tendfor\r\n<\r\n\r\n\r\n\r\n","install_details":"","5":"","first_name":"basyura","6":"basyura","last_name":" ","7":" ","releases":[{"0":"3476","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"bitly.vim.zip","4":"bitly.vim.zip","src_id":"15140","5":"15140","creation_date":"1298943815","6":"1298943815"}]},"3475":{"script_id":"3475","0":"3475","script_name":"Vim Blog","1":"Vim Blog","script_type":"utility","2":"utility","summary":"An updated plugin to allow you to post from VIM to Wordpress","3":"An updated plugin to allow you to post from VIM to Wordpress","description":" took the popular vimpress plugin and added the ability to upload images and set a post status type (draft or published). \r\n\r\n\r\nCommands :\r\n\":BlogList [count]\"\r\n  Lists the last x articles in the blog - if left blank 10 are returned\r\n\":BlogNew\"\r\n  Opens page to write new article\r\n\":BlogOpen <id>\"\r\n  Opens the article <id> for edition\r\n\":BlogDel <id>\" \r\n  Del the article <id>\r\n\":BlogSend\"\r\n  Saves the article to the blog if the Post Status is draft. Posts the\r\n  article to the blog if the Post Status is publish\r\n\":BlogUp <image name>\"\r\n  Uploads an image to the blog and inserts the image url. It will use the\r\n  img_template var to fill in a whole img tag if wanted. Use %s where you'd\r\n  like the actual url to be.\r\n\"<leader>c\"\r\n  Must be in insert mode.\r\n  Displays an auto-complete list of available blog categories. Currently\r\n  only supported after :BlogNew\r\n  You can remap this on line 69","4":" took the popular vimpress plugin and added the ability to upload images and set a post status type (draft or published). \r\n\r\n\r\nCommands :\r\n\":BlogList [count]\"\r\n  Lists the last x articles in the blog - if left blank 10 are returned\r\n\":BlogNew\"\r\n  Opens page to write new article\r\n\":BlogOpen <id>\"\r\n  Opens the article <id> for edition\r\n\":BlogDel <id>\" \r\n  Del the article <id>\r\n\":BlogSend\"\r\n  Saves the article to the blog if the Post Status is draft. Posts the\r\n  article to the blog if the Post Status is publish\r\n\":BlogUp <image name>\"\r\n  Uploads an image to the blog and inserts the image url. It will use the\r\n  img_template var to fill in a whole img tag if wanted. Use %s where you'd\r\n  like the actual url to be.\r\n\"<leader>c\"\r\n  Must be in insert mode.\r\n  Displays an auto-complete list of available blog categories. Currently\r\n  only supported after :BlogNew\r\n  You can remap this on line 69","install_details":"Place in your vim\/plugin\/ directory.\r\n\r\nEdit the settings starting on line 82\r\n\r\nThis plugin does require that python be compiled into vim","5":"Place in your vim\/plugin\/ directory.\r\n\r\nEdit the settings starting on line 82\r\n\r\nThis plugin does require that python be compiled into vim","first_name":"Josh","6":"Josh","last_name":"Kenzer","7":"Kenzer","releases":[{"0":"3475","vim_version":"7.0","1":"7.0","script_version":"1.6","2":"1.6","version_comment":"Added one new feature: When you use :BlogSend, your default browser will open either the preview URL or the actual URL in your default browser (I have not tested this in Windows). If it is a published post, it will use the \"?p=id\" URL format. Note that this doesn't affect how you have your wordpress default URL slug setup.\r\n\r\nYou can configure the plugin to not open a browser window by changing the enable_preview setting to 0. Currently, it will open a new window\/tab everytime you do :BlogSend. I hope to modify this to only do it once per post in the future.\r\n\r\nI also now show the appropriate url in the Preview line based on whether it is a draft or published post.","3":"Added one new feature: When you use :BlogSend, your default browser will open either the preview URL or the actual URL in your default browser (I have not tested this in Windows). If it is a published post, it will use the \"?p=id\" URL format. Note that this doesn't affect how you have your wordpress default URL slug setup.\r\n\r\nYou can configure the plugin to not open a browser window by changing the enable_preview setting to 0. Currently, it will open a new window\/tab everytime you do :BlogSend. I hope to modify this to only do it once per post in the future.\r\n\r\nI also now show the appropriate url in the Preview line based on whether it is a draft or published post.","package":"blog.vim","4":"blog.vim","src_id":"15191","5":"15191","creation_date":"1299795497","6":"1299795497"},{"0":"3475","vim_version":"7.0","1":"7.0","script_version":"1.5","2":"1.5","version_comment":"I added the capability to auto-complete categories. The command, while in insert mode, is <leader>c. This is the same as <ctrl>x <ctrl>u for a user defined auto-complete list.\r\n\r\nI also added some plugin checks to make sure it wasn't previously loaded.","3":"I added the capability to auto-complete categories. The command, while in insert mode, is <leader>c. This is the same as <ctrl>x <ctrl>u for a user defined auto-complete list.\r\n\r\nI also added some plugin checks to make sure it wasn't previously loaded.","package":"blog.vim","4":"blog.vim","src_id":"15171","5":"15171","creation_date":"1299533442","6":"1299533442"},{"0":"3475","vim_version":"7.0","1":"7.0","script_version":"1.2","2":"1.2","version_comment":"Bug Fix.\r\nAdded the ability to define an image template to use. This template is inserted into the buffer after the :BlogUp has uploaded your image. %s is replaced with the img url. This should speed up time for inserting images into your posts.","3":"Bug Fix.\r\nAdded the ability to define an image template to use. This template is inserted into the buffer after the :BlogUp has uploaded your image. %s is replaced with the img url. This should speed up time for inserting images into your posts.","package":"blog.vim","4":"blog.vim","src_id":"15148","5":"15148","creation_date":"1299096723","6":"1299096723"},{"0":"3475","vim_version":"7.0","1":"7.0","script_version":"1.1","2":"1.1","version_comment":"Added BlogDel and revised BlogList to return a specified number of posts (default is 10). Thanks to http:\/\/wiki.yepn.net\/vimpress for the code. Thanks to Carson for the tip.","3":"Added BlogDel and revised BlogList to return a specified number of posts (default is 10). Thanks to http:\/\/wiki.yepn.net\/vimpress for the code. Thanks to Carson for the tip.","package":"blog.vim","4":"blog.vim","src_id":"15142","5":"15142","creation_date":"1299012068","6":"1299012068"},{"0":"3475","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Fixed documentation","3":"Fixed documentation","package":"blog.vim","4":"blog.vim","src_id":"15139","5":"15139","creation_date":"1298934627","6":"1298934627"}]},"3474":{"script_id":"3474","0":"3474","script_name":"Neopro","1":"Neopro","script_type":"color scheme","2":"color scheme","summary":"Dark, high contrast neon theme","3":"Dark, high contrast neon theme","description":"Currently for GUI and color terminals only!\r\n\r\nFeatures:\r\n - Great for Web Development (HTML, CSS, JavaScript)\r\n - Pathogen Ready\r\n\r\nResources\r\n - Github: https:\/\/github.com\/bawigga\/vim-neopro\r\n - Screenshot: https:\/\/github.com\/bawigga\/vim-neopro\/raw\/master\/neopro.png","4":"Currently for GUI and color terminals only!\r\n\r\nFeatures:\r\n - Great for Web Development (HTML, CSS, JavaScript)\r\n - Pathogen Ready\r\n\r\nResources\r\n - Github: https:\/\/github.com\/bawigga\/vim-neopro\r\n - Screenshot: https:\/\/github.com\/bawigga\/vim-neopro\/raw\/master\/neopro.png","install_details":"","5":"","first_name":"Brian","6":"Brian","last_name":"Wigginton","7":"Wigginton","releases":[{"0":"3474","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"neopro.vim","4":"neopro.vim","src_id":"15134","5":"15134","creation_date":"1298875774","6":"1298875774"}]},"3473":{"script_id":"3473","0":"3473","script_name":"Clean","1":"Clean","script_type":"color scheme","2":"color scheme","summary":"A coherent and light color scheme optimized for web dev (Vim and GVim)","3":"A coherent and light color scheme optimized for web dev (Vim and GVim)","description":"This light color scheme tries to remain coherent in different programming languages.\r\n\r\nIt is specially optimized for HTML, CSS, JavaScript, PHP, C, Python, Ruby and XML.\r\n\r\nNote that the .Xdefaults\/.Xresources configuration is included within the script.\r\n\r\nFor better results, paste this config in your .Xdefaults\/.Xresources file (don't forget to remove the quotes ;-) )...\r\n\r\nEnjoy!\r\n\r\nhttp:\/\/img713.imageshack.us\/i\/cleanu.png\/","4":"This light color scheme tries to remain coherent in different programming languages.\r\n\r\nIt is specially optimized for HTML, CSS, JavaScript, PHP, C, Python, Ruby and XML.\r\n\r\nNote that the .Xdefaults\/.Xresources configuration is included within the script.\r\n\r\nFor better results, paste this config in your .Xdefaults\/.Xresources file (don't forget to remove the quotes ;-) )...\r\n\r\nEnjoy!\r\n\r\nhttp:\/\/img713.imageshack.us\/i\/cleanu.png\/","install_details":"Just put the file in your  .vim\/colors...","5":"Just put the file in your  .vim\/colors...","first_name":"Dee Sub Wun","6":"Dee Sub Wun","last_name":".","7":".","releases":[{"0":"3473","vim_version":"7.0","1":"7.0","script_version":"1.1","2":"1.1","version_comment":"Now with support for GUI !","3":"Now with support for GUI !","package":"clean.vim","4":"clean.vim","src_id":"15136","5":"15136","creation_date":"1298903060","6":"1298903060"},{"0":"3473","vim_version":"7.0","1":"7.0","script_version":"1","2":"1","version_comment":"Initial upload","3":"Initial upload","package":"clean.vim","4":"clean.vim","src_id":"15132","5":"15132","creation_date":"1298845641","6":"1298845641"}]},"3472":{"script_id":"3472","0":"3472","script_name":"thermometer","1":"thermometer","script_type":"utility","2":"utility","summary":"work with mercurial","3":"work with mercurial","description":"Thermometer is a vim plugin for mercurial users.\r\n\r\nAvailable commands are:\r\n\r\n* :Hgst to open a quickfix window with changes to the repository\r\n* :Hgstreload to reset status data used in statusline function\r\n* :Hgdiff to diff the current buffer with its last version on the repository, or with a particular revision if a revision number is provided\r\n* :Hgdiffoff to diffoff the current diff\r\n* :Hglog to show the repository's log, can receive an optional parameter to limit the number of revisions shown\r\n\r\nAlso there is g:HgStatusForFile() to be used in statuslines","4":"Thermometer is a vim plugin for mercurial users.\r\n\r\nAvailable commands are:\r\n\r\n* :Hgst to open a quickfix window with changes to the repository\r\n* :Hgstreload to reset status data used in statusline function\r\n* :Hgdiff to diff the current buffer with its last version on the repository, or with a particular revision if a revision number is provided\r\n* :Hgdiffoff to diffoff the current diff\r\n* :Hglog to show the repository's log, can receive an optional parameter to limit the number of revisions shown\r\n\r\nAlso there is g:HgStatusForFile() to be used in statuslines","install_details":"","5":"","first_name":"Diego","6":"Diego","last_name":"Guerra","7":"Guerra","releases":[{"0":"3472","vim_version":"7.0","1":"7.0","script_version":"0.2.2","2":"0.2.2","version_comment":"Fixed Hgst not preserving errorfmt. Thanks again to Dmitry Frank","3":"Fixed Hgst not preserving errorfmt. Thanks again to Dmitry Frank","package":"thermometer.tar.gz","4":"thermometer.tar.gz","src_id":"16629","5":"16629","creation_date":"1317978204","6":"1317978204"},{"0":"3472","vim_version":"7.0","1":"7.0","script_version":"0.2.1","2":"0.2.1","version_comment":"Windows fixes for Hgdiff by Dmitry Frank ","3":"Windows fixes for Hgdiff by Dmitry Frank ","package":"thermometer.tar.gz","4":"thermometer.tar.gz","src_id":"16445","5":"16445","creation_date":"1315049358","6":"1315049358"},{"0":"3472","vim_version":"7.0","1":"7.0","script_version":"0.2","2":"0.2","version_comment":"* Hgdiff to different versions\r\n* Hgdiffoff to turn off diffs","3":"* Hgdiff to different versions\r\n* Hgdiffoff to turn off diffs","package":"thermometer.tar.gz","4":"thermometer.tar.gz","src_id":"15472","5":"15472","creation_date":"1303141577","6":"1303141577"},{"0":"3472","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"thermometer.zip","4":"thermometer.zip","src_id":"15130","5":"15130","creation_date":"1298816654","6":"1298816654"}]},"3471":{"script_id":"3471","0":"3471","script_name":"latte","1":"latte","script_type":"color scheme","2":"color scheme","summary":"milk & cookies colorcheme","3":"milk & cookies colorcheme","description":"screenshot & credits: https:\/\/github.com\/aerosol\/Latte\r\n\r\nenjoy!","4":"screenshot & credits: https:\/\/github.com\/aerosol\/Latte\r\n\r\nenjoy!","install_details":"","5":"","first_name":"adam","6":"adam","last_name":"rutkowski","7":"rutkowski","releases":[{"0":"3471","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"latte.vim","4":"latte.vim","src_id":"15117","5":"15117","creation_date":"1298657448","6":"1298657448"}]},"3470":{"script_id":"3470","0":"3470","script_name":"tidydiff","1":"tidydiff","script_type":"utility","2":"utility","summary":"highlight what perltidy would do","3":"highlight what perltidy would do","description":"tidydiff calls perltidy on the current file, splits the window, and diffs it against the .tdy file.\r\n\r\nComments and suggestions should be directed to dbb on Github.","4":"tidydiff calls perltidy on the current file, splits the window, and diffs it against the .tdy file.\r\n\r\nComments and suggestions should be directed to dbb on Github.","install_details":"% curl -O https:\/\/github.com\/dbb\/vim\/raw\/master\/tidydiff.vim","5":"% curl -O https:\/\/github.com\/dbb\/vim\/raw\/master\/tidydiff.vim","first_name":"Daniel","6":"Daniel","last_name":"B","7":"B","releases":[{"0":"3470","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"tidydiff.vim","4":"tidydiff.vim","src_id":"15115","5":"15115","creation_date":"1298625937","6":"1298625937"}]},"3469":{"script_id":"3469","0":"3469","script_name":"csc.snippets","1":"csc.snippets","script_type":"utility","2":"utility","summary":"Essbase script snippet file","3":"Essbase script snippet file","description":"Essbase script snippet file should be up-to-date with all features of Essbase 9.  \r\n\r\nyou can insert into your code using a trigger word followed by a <tab>.\r\n\r\nFor instance, in a csc file, if you type \"FIX<tab>\" in insert mode, it will expand a typical for FIX: \r\n\r\nFIX (fixMbrs)\r\n        commands;\r\nENDFIX\r\n\r\nTo go to the next item in the loop, simply <tab> over to it; if there is repeated code, such as the \"i\" variable in this example, you can simply start typing once it's highlighted and all the matches specified in the snippet will be updated. To go in reverse, use <shift-tab>.\r\n\r\nIf anything is missing, broken, not working well on your setup, or an inconvenience for you, please let me know, all feedback is welcome: <yyq123 at gmail.com>.\r\n\r\nEnhancements:\r\n-------------\r\n* case sensitive\r\n\r\nScreenshots:\r\n-------------\r\n* For statem with single srgument\r\n  http:\/\/www.flickr.com\/photos\/yyq123\/5454484247\/\r\n\r\n* For statem with multipule argumets\r\n  http:\/\/www.flickr.com\/photos\/yyq123\/5454484239\/\r\n\r\n* For statem list\r\n  http:\/\/www.flickr.com\/photos\/yyq123\/5454484241\/","4":"Essbase script snippet file should be up-to-date with all features of Essbase 9.  \r\n\r\nyou can insert into your code using a trigger word followed by a <tab>.\r\n\r\nFor instance, in a csc file, if you type \"FIX<tab>\" in insert mode, it will expand a typical for FIX: \r\n\r\nFIX (fixMbrs)\r\n        commands;\r\nENDFIX\r\n\r\nTo go to the next item in the loop, simply <tab> over to it; if there is repeated code, such as the \"i\" variable in this example, you can simply start typing once it's highlighted and all the matches specified in the snippet will be updated. To go in reverse, use <shift-tab>.\r\n\r\nIf anything is missing, broken, not working well on your setup, or an inconvenience for you, please let me know, all feedback is welcome: <yyq123 at gmail.com>.\r\n\r\nEnhancements:\r\n-------------\r\n* case sensitive\r\n\r\nScreenshots:\r\n-------------\r\n* For statem with single srgument\r\n  http:\/\/www.flickr.com\/photos\/yyq123\/5454484247\/\r\n\r\n* For statem with multipule argumets\r\n  http:\/\/www.flickr.com\/photos\/yyq123\/5454484239\/\r\n\r\n* For statem list\r\n  http:\/\/www.flickr.com\/photos\/yyq123\/5454484241\/","install_details":"Prerequisite\r\n-------------\r\n* Install snipMate plugin (http:\/\/www.vim.org\/scripts\/script.php?script_id=2540)\r\n\r\nInstallation\r\n-------------\r\n* Copy csc.snippets to ~\/.vim\/snippets\/csc.snippets or c:\\program files\\vim\\vimfiles\\snippets\\csc.snippets","5":"Prerequisite\r\n-------------\r\n* Install snipMate plugin (http:\/\/www.vim.org\/scripts\/script.php?script_id=2540)\r\n\r\nInstallation\r\n-------------\r\n* Copy csc.snippets to ~\/.vim\/snippets\/csc.snippets or c:\\program files\\vim\\vimfiles\\snippets\\csc.snippets","first_name":"Anthony","6":"Anthony","last_name":"Yuan","7":"Yuan","releases":[{"0":"3469","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"csc.snippets","4":"csc.snippets","src_id":"15108","5":"15108","creation_date":"1298553015","6":"1298553015"}]},"3468":{"script_id":"3468","0":"3468","script_name":"windows sif syntax","1":"windows sif syntax","script_type":"syntax","2":"syntax","summary":"Windows SIF file syntax","3":"Windows SIF file syntax","description":"Syntax for SIF files like winnt.sif and txtsetup.sif","4":"Syntax for SIF files like winnt.sif and txtsetup.sif","install_details":"put this file in your $VIMRUNTIME\\syntax\\","5":"put this file in your $VIMRUNTIME\\syntax\\","first_name":"Yo-An","6":"Yo-An","last_name":"Lin","7":"Lin","releases":[{"0":"3468","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"sif.vim","4":"sif.vim","src_id":"15107","5":"15107","creation_date":"1298547745","6":"1298547745"}]},"3467":{"script_id":"3467","0":"3467","script_name":"align","1":"align","script_type":"utility","2":"utility","summary":"Align the right ends of statements together.","3":"Align the right ends of statements together.","description":"I wrote this script to help write verilog files that were compatible with my \r\ncompany's coding standard.\r\n\r\nThis script shifts the character under the cursor to a defined point. It can\r\nthus be used to align the *right* side of code to beautify or to confirm to\r\ncoding standards.\r\n\r\nSpaces are inserted before the current cursor position. The number of spaces\r\ninserted aligns the text to the lines above it. For example, if you have the\r\nfollowing chunk of code.\r\n\r\nreg [13:0] resultant  ;\r\nreg  [7:0] bytea;\r\n\r\nIf you load the script and press ';;' while on the semicolon on the second line,\r\nthe text will become like so.\r\n\r\nreg [13:0] resultant  ;\r\nreg  [7:0] bytea      ;\r\n\r\nNOTE: There has to be a previous aligned line for the script to make a match\r\nfrom.\r\n\r\nThis can also be used as part of a recorded macro. For example, to align the\r\nfollowing lines of code, to the top line.\r\n\r\n1   PORT_00       (port_00a       ),\/\/ Comment 1\r\n2   PORT_01(port_01aa),\/\/ Comment 2\r\n3   PORT_02(port_02aaa),\/\/ Comment 3\r\n4   PORT_03(port_03aaaa),\/\/ Comment 4\r\n5   PORT_04(port_04a),\/\/ Comment 5\r\n6\r\n7   PORT_T_00(port_t_00a),\/\/ Comment 6\r\n8   PORT_T_01(port_t_01aa),\/\/ Comment 7\r\n9   PORT_T_02(port_t_02aaa),\/\/ Comment 8\r\n10  PORT_T_03(port_t_03aaaa),\/\/ Comment 9\r\n\r\nWe can record a macro. Place your cursor on the first char of line 2 (the digit\r\n2) and press 'qzf(;;j^q'\r\n  q   - start recording\r\n  z   - record in register z\r\n  f(  - go to first occurrence of (\r\n  ;;  - align\r\n  j   - move down\r\n  ^   - go to start of line\r\n  q   - end recording.\r\n\r\nNow pressing @z on the start of line 3 will cause it to align. And the same for\r\nall the other lines. The same can be done for the closing brackets to get the\r\nfollowing.\r\n\r\n1   PORT_00       (port_00a       ), \/\/ Comment 1\r\n2   PORT_01       (port_01aa      ), \/\/ Comment 2\r\n3   PORT_02       (port_02aaa     ), \/\/ Comment 3\r\n4   PORT_03       (port_03aaaa    ), \/\/ Comment 4\r\n5   PORT_04       (port_04a       ), \/\/ Comment 5\r\n6\r\n7   PORT_T_00     (port_t_00a     ), \/\/ Comment 6\r\n8   PORT_T_01     (port_t_01aa    ), \/\/ Comment 7\r\n9   PORT_T_02     (port_t_02aaa   ), \/\/ Comment 8\r\n10  PORT_T_03     (port_t_03aaaa  ), \/\/ Comment 9\r\n","4":"I wrote this script to help write verilog files that were compatible with my \r\ncompany's coding standard.\r\n\r\nThis script shifts the character under the cursor to a defined point. It can\r\nthus be used to align the *right* side of code to beautify or to confirm to\r\ncoding standards.\r\n\r\nSpaces are inserted before the current cursor position. The number of spaces\r\ninserted aligns the text to the lines above it. For example, if you have the\r\nfollowing chunk of code.\r\n\r\nreg [13:0] resultant  ;\r\nreg  [7:0] bytea;\r\n\r\nIf you load the script and press ';;' while on the semicolon on the second line,\r\nthe text will become like so.\r\n\r\nreg [13:0] resultant  ;\r\nreg  [7:0] bytea      ;\r\n\r\nNOTE: There has to be a previous aligned line for the script to make a match\r\nfrom.\r\n\r\nThis can also be used as part of a recorded macro. For example, to align the\r\nfollowing lines of code, to the top line.\r\n\r\n1   PORT_00       (port_00a       ),\/\/ Comment 1\r\n2   PORT_01(port_01aa),\/\/ Comment 2\r\n3   PORT_02(port_02aaa),\/\/ Comment 3\r\n4   PORT_03(port_03aaaa),\/\/ Comment 4\r\n5   PORT_04(port_04a),\/\/ Comment 5\r\n6\r\n7   PORT_T_00(port_t_00a),\/\/ Comment 6\r\n8   PORT_T_01(port_t_01aa),\/\/ Comment 7\r\n9   PORT_T_02(port_t_02aaa),\/\/ Comment 8\r\n10  PORT_T_03(port_t_03aaaa),\/\/ Comment 9\r\n\r\nWe can record a macro. Place your cursor on the first char of line 2 (the digit\r\n2) and press 'qzf(;;j^q'\r\n  q   - start recording\r\n  z   - record in register z\r\n  f(  - go to first occurrence of (\r\n  ;;  - align\r\n  j   - move down\r\n  ^   - go to start of line\r\n  q   - end recording.\r\n\r\nNow pressing @z on the start of line 3 will cause it to align. And the same for\r\nall the other lines. The same can be done for the closing brackets to get the\r\nfollowing.\r\n\r\n1   PORT_00       (port_00a       ), \/\/ Comment 1\r\n2   PORT_01       (port_01aa      ), \/\/ Comment 2\r\n3   PORT_02       (port_02aaa     ), \/\/ Comment 3\r\n4   PORT_03       (port_03aaaa    ), \/\/ Comment 4\r\n5   PORT_04       (port_04a       ), \/\/ Comment 5\r\n6\r\n7   PORT_T_00     (port_t_00a     ), \/\/ Comment 6\r\n8   PORT_T_01     (port_t_01aa    ), \/\/ Comment 7\r\n9   PORT_T_02     (port_t_02aaa   ), \/\/ Comment 8\r\n10  PORT_T_03     (port_t_03aaaa  ), \/\/ Comment 9\r\n","install_details":"Put the script in some folder (lets say $ALIGN)\r\nadd this to your ~\/.vimrc\r\n\r\nsource $ALIGN\/align.vim\r\n","5":"Put the script in some folder (lets say $ALIGN)\r\nadd this to your ~\/.vimrc\r\n\r\nsource $ALIGN\/align.vim\r\n","first_name":"Zohair","6":"Zohair","last_name":"Ahmad","7":"Ahmad","releases":[{"0":"3467","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"align.tar.gz","4":"align.tar.gz","src_id":"15104","5":"15104","creation_date":"1298536312","6":"1298536312"}]},"3466":{"script_id":"3466","0":"3466","script_name":"vimake vim programmers ide","1":"vimake vim programmers ide","script_type":"utility","2":"utility","summary":"A Vim Programmers IDE (Linux)","3":"A Vim Programmers IDE (Linux)","description":"Welcome to Vimake-1.16 as in previous versions Vimake turns your Vim editing session into a multi program IDE where you can write, build, test and run various programs written in C\/CPP OBJC NASM GAS(AS) LUA  all run from the Function keys.\r\nNew features include compile test and run APPS using Objective-C with the GNUstep libraries and header files. No need to to write a MAKEFILE. Further improvements have been made to the debug and viclean functions and documentation.\r\n\r\n install details\r\n copy  the package to your home directory then run\r\n tar -zxvf vimake-1.16.tar.gz.\r\n Change directory to the doc sub-dir of the package then follow Install,Configure and Tutorial in the html document.\r\n","4":"Welcome to Vimake-1.16 as in previous versions Vimake turns your Vim editing session into a multi program IDE where you can write, build, test and run various programs written in C\/CPP OBJC NASM GAS(AS) LUA  all run from the Function keys.\r\nNew features include compile test and run APPS using Objective-C with the GNUstep libraries and header files. No need to to write a MAKEFILE. Further improvements have been made to the debug and viclean functions and documentation.\r\n\r\n install details\r\n copy  the package to your home directory then run\r\n tar -zxvf vimake-1.16.tar.gz.\r\n Change directory to the doc sub-dir of the package then follow Install,Configure and Tutorial in the html document.\r\n","install_details":"","5":"","first_name":"michael","6":"michael","last_name":"lear","7":"lear","releases":[{"0":"3466","vim_version":"7.0","1":"7.0","script_version":"1-18","2":"1-18","version_comment":"GTKMM has been added to the list of programs which vimake can build without the need\r\nof a Makefile. This allows the gtkmm demonstration package to be built as separate\r\nstand alone programs. The GUI IDE has now been re-written as a vim plug-in, using gtkmm\r\nprograms to display toggle key messages. The tutorial has been updated to include all of\r\nthe new features.\r\n\r\nCopy the vimake-1.18.tar.gz package to your home directory.\r\nThen use the following commands to build and install.\r\n      tar -zxvf vimake-1.18.tar.gz\r\n      cd ~\/vimake-1.18\r\n      .\/configure\r\n      make install\r\n\r\nThen change to the doc sub directory and run Tutorial.html This contains full Installation-\r\nConfiguration and a Tutorial on using Vimake in Vim, Gvim and the GUI.\r\n","3":"GTKMM has been added to the list of programs which vimake can build without the need\r\nof a Makefile. This allows the gtkmm demonstration package to be built as separate\r\nstand alone programs. The GUI IDE has now been re-written as a vim plug-in, using gtkmm\r\nprograms to display toggle key messages. The tutorial has been updated to include all of\r\nthe new features.\r\n\r\nCopy the vimake-1.18.tar.gz package to your home directory.\r\nThen use the following commands to build and install.\r\n      tar -zxvf vimake-1.18.tar.gz\r\n      cd ~\/vimake-1.18\r\n      .\/configure\r\n      make install\r\n\r\nThen change to the doc sub directory and run Tutorial.html This contains full Installation-\r\nConfiguration and a Tutorial on using Vimake in Vim, Gvim and the GUI.\r\n","package":"vimake-1.18.tar.gz","4":"vimake-1.18.tar.gz","src_id":"15502","5":"15502","creation_date":"1303451096","6":"1303451096"},{"0":"3466","vim_version":"7.0","1":"7.0","script_version":"1-17","2":"1-17","version_comment":"New features in this version is the IDE Vimake menu for Gvim. How to use the Gvim Gui with vimake.\r\nNEW program to allow the Gui version to access different debuggers from the mouse.\r\nBug-Fix: Viclean had a window re-sizing error (TIOCGWINSZ) this is now fixed.\r\n\r\nTo install:     cp vimake-1.17.tar.gz  to your home directory.\r\nExtract:        tar -zxvf vimake-1.17.tar.gz\r\nChdir:          cd ~\/vimake-1.17\/doc\r\nChdir:          cd ~\/vimake-1.17\r\nConfigure:      .\/configure\r\nmake:           make install\r\n\r\nThen change to the doc sub directory run Tutorial.html\r\nThis contains full Installation-Configuration and a Tutorial on using Vimake in Vim, Gvim and the Gui.\r\n","3":"New features in this version is the IDE Vimake menu for Gvim. How to use the Gvim Gui with vimake.\r\nNEW program to allow the Gui version to access different debuggers from the mouse.\r\nBug-Fix: Viclean had a window re-sizing error (TIOCGWINSZ) this is now fixed.\r\n\r\nTo install:     cp vimake-1.17.tar.gz  to your home directory.\r\nExtract:        tar -zxvf vimake-1.17.tar.gz\r\nChdir:          cd ~\/vimake-1.17\/doc\r\nChdir:          cd ~\/vimake-1.17\r\nConfigure:      .\/configure\r\nmake:           make install\r\n\r\nThen change to the doc sub directory run Tutorial.html\r\nThis contains full Installation-Configuration and a Tutorial on using Vimake in Vim, Gvim and the Gui.\r\n","package":"vimake-1.17.tar.gz","4":"vimake-1.17.tar.gz","src_id":"15212","5":"15212","creation_date":"1300054223","6":"1300054223"},{"0":"3466","vim_version":"7.0","1":"7.0","script_version":"1-16","2":"1-16","version_comment":"Initial upload","3":"Initial upload","package":"vimake-1.16.tar.gz","4":"vimake-1.16.tar.gz","src_id":"15096","5":"15096","creation_date":"1298465081","6":"1298465081"}]},"3465":{"script_id":"3465","0":"3465","script_name":"Tagbar","1":"Tagbar","script_type":"utility","2":"utility","summary":"Display tags of the current file ordered by scope","3":"Display tags of the current file ordered by scope","description":"Tagbar displays the tags of the current file in a sidebar, similar to vimscript #273. But it has the advantage that it will display them ordered by their scope -- for example, methods and members in languages like C++, Python or Java will be listed under their correct class instead of just under the general categories 'functions' or 'variables'. This gives a more helpful overview of the file.\r\n\r\nAdditionally the Tagbar window can be used to quickly jump to tags.\r\n\r\nTagbar requires Exuberant ctags (http:\/\/ctags.sourceforge.net\/) in at least version 5.5 to work.\r\n\r\nPlugin homepage with screenshots:\r\nhttp:\/\/majutsushi.github.com\/tagbar\/\r\n\r\nCode repository:\r\nhttps:\/\/github.com\/majutsushi\/tagbar","4":"Tagbar displays the tags of the current file in a sidebar, similar to vimscript #273. But it has the advantage that it will display them ordered by their scope -- for example, methods and members in languages like C++, Python or Java will be listed under their correct class instead of just under the general categories 'functions' or 'variables'. This gives a more helpful overview of the file.\r\n\r\nAdditionally the Tagbar window can be used to quickly jump to tags.\r\n\r\nTagbar requires Exuberant ctags (http:\/\/ctags.sourceforge.net\/) in at least version 5.5 to work.\r\n\r\nPlugin homepage with screenshots:\r\nhttp:\/\/majutsushi.github.com\/tagbar\/\r\n\r\nCode repository:\r\nhttps:\/\/github.com\/majutsushi\/tagbar","install_details":"Use the normal Vimball installation method to install Tagbar:\r\n\r\n    vim tagbar.vba\r\n    :so %\r\n    :q\r\n\r\nIf ctags is not installed in one of the directories in your $PATH environment variable you have to set the option g:tagbar_ctags_bin, see the documentation for exact instructions.\r\n\r\nNote: Vim versions < 7.0.167 have a bug that prevents Tagbar from working. If you are affected by this use this alternate Tagbar download instead:\r\nhttps:\/\/github.com\/majutsushi\/tagbar\/zipball\/70fix\r\nIt is on par with version 2.2 but probably won't be updated after that. \r\n\r\nQuickstart:\r\n\r\nPut something like the following into your ~\/.vimrc:\r\n\r\nnmap <F8> :TagbarToggle<CR>\r\n\r\nThen the F8 key will toggle the Tagbar window. You can of course use any shortcut you want. For more flexible ways to open and close the window (and the rest of the functionality) see the documentation.","5":"Use the normal Vimball installation method to install Tagbar:\r\n\r\n    vim tagbar.vba\r\n    :so %\r\n    :q\r\n\r\nIf ctags is not installed in one of the directories in your $PATH environment variable you have to set the option g:tagbar_ctags_bin, see the documentation for exact instructions.\r\n\r\nNote: Vim versions < 7.0.167 have a bug that prevents Tagbar from working. If you are affected by this use this alternate Tagbar download instead:\r\nhttps:\/\/github.com\/majutsushi\/tagbar\/zipball\/70fix\r\nIt is on par with version 2.2 but probably won't be updated after that. \r\n\r\nQuickstart:\r\n\r\nPut something like the following into your ~\/.vimrc:\r\n\r\nnmap <F8> :TagbarToggle<CR>\r\n\r\nThen the F8 key will toggle the Tagbar window. You can of course use any shortcut you want. For more flexible ways to open and close the window (and the rest of the functionality) see the documentation.","first_name":"Jan","6":"Jan","last_name":"Larres","7":"Larres","releases":[{"0":"3465","vim_version":"7.0","1":"7.0","script_version":"2.7","2":"2.7","version_comment":"- Added support for Universal Ctags, courtesy of Dmytro Konstantinov\n- Added option to arrange Tagbar window vertically\n- Added case-insensitive sort option, courtesy of Martin Vuille\n- Added option to configure zoom width\n- Added option to hide non-public tags\n- Added 'silent' option to disable the display of tag information in the\n  command line, courtesy of Anmol Sethi\n- Added mappings for moving between folds\n- Improved handling of calling :bdelete\/:bwipeout\/:quit when Tagbar is open\n- Improved handling of multiple tabs with separate Tagbar instances, courtesy of Martin Vuille\n- Better handling of various errors to allow Tagbar to continue working\n- Various other small improvements and bugfixes\n","3":"- Added support for Universal Ctags, courtesy of Dmytro Konstantinov\n- Added option to arrange Tagbar window vertically\n- Added case-insensitive sort option, courtesy of Martin Vuille\n- Added option to configure zoom width\n- Added option to hide non-public tags\n- Added 'silent' option to disable the display of tag information in the\n  command line, courtesy of Anmol Sethi\n- Added mappings for moving between folds\n- Improved handling of calling :bdelete\/:bwipeout\/:quit when Tagbar is open\n- Improved handling of multiple tabs with separate Tagbar instances, courtesy of Martin Vuille\n- Better handling of various errors to allow Tagbar to continue working\n- Various other small improvements and bugfixes\n","package":"tagbar.vmb","4":"tagbar.vmb","src_id":"24887","5":"24887","creation_date":"1483935995","6":"1483935995"},{"0":"3465","vim_version":"7.0","1":"7.0","script_version":"2.6.1","2":"2.6.1","version_comment":"- Automatically close the preview window when jumping to a tag\n- Don't forget the previous window in certain situations, which was causing\n  problems with for example fugitive\n- Fixed toggling kind-specific folds\n- Fixed ctags error that can happen with Cygwin\n","3":"- Automatically close the preview window when jumping to a tag\n- Don't forget the previous window in certain situations, which was causing\n  problems with for example fugitive\n- Fixed toggling kind-specific folds\n- Fixed ctags error that can happen with Cygwin\n","package":"tagbar.vmb","4":"tagbar.vmb","src_id":"21362","5":"21362","creation_date":"1390472231","6":"1390472231"},{"0":"3465","vim_version":"7.0","1":"7.0","script_version":"2.6","2":"2.6","version_comment":"- Added possibility to show tags in the preview window, either manually or\n  automatically.\n- Allow customizing the statusline, see :help g:tagbar_status_func.\n- Type configuration can now be project-specific.\n- The keybindings in the Tagbar window are now configurable.\n- Improvements to Ctags execution on Windows, thanks to Darcy Parker.\n- Added function tagbar#currentfile() that returns the path to the file\n  currently being displayed in Tagbar, thanks to Zhao Cai.\n- Added a :Tagbar command as an alias for :TagbarToggle.\n- Added an way to ignore specific files in case they create problems.\n- Optionally show line numbers in the Tagbar window.\n- The usual bunch of small improvements and bugfixes.\n","3":"- Added possibility to show tags in the preview window, either manually or\n  automatically.\n- Allow customizing the statusline, see :help g:tagbar_status_func.\n- Type configuration can now be project-specific.\n- The keybindings in the Tagbar window are now configurable.\n- Improvements to Ctags execution on Windows, thanks to Darcy Parker.\n- Added function tagbar#currentfile() that returns the path to the file\n  currently being displayed in Tagbar, thanks to Zhao Cai.\n- Added a :Tagbar command as an alias for :TagbarToggle.\n- Added an way to ignore specific files in case they create problems.\n- Optionally show line numbers in the Tagbar window.\n- The usual bunch of small improvements and bugfixes.\n","package":"tagbar.vmb","4":"tagbar.vmb","src_id":"21159","5":"21159","creation_date":"1386242843","6":"1386242843"},{"0":"3465","vim_version":"7.0","1":"7.0","script_version":"2.5","2":"2.5","version_comment":"- New command :TagbarTogglePause to freeze Tagbar in its current state so you\n  can switch to other files while keeping the old information displayed for\n  reference. (Kian Ryan)\n- New command :TagbarCurrentTag which reports the same information as\n  currenttag().\n- New option tagbar_indent to configure the indentation depth of the tags.\n- New option tagbar_show_visibility to allow disabling the visibility symbols.\n- Files are now cached locally to avoid additional slowdowns for slow\n  connections. This also makes it possible to use Tagbar with files accessed\n  through Netrw.\n- Execute ctags again even if the previous run reported errors, in case it was\n  a parse error that has since been fixed. If the error persists, don't\n  display it again.\n- Improved window switching and Vim exit behaviours. (Techlive Zheng)\n- The currenttag() function now can show the prototype instead of the actual\n  tag, which can be useful in some cases where ctags doesn't report all the\n  interesting information.\n- The prototype shown in the tooltip or command line should now always be\n  complete, even if it is spread out over more than one line in the source\n  file.\n- The TagbarAccessPublic etc. highlight groups have been renamed to\n  TagbarVisibilityPublic etc. to keep them in line with standard terminology.\n  The old names are still supported.\n- Various smaller improvements and bugfixes.\n","3":"- New command :TagbarTogglePause to freeze Tagbar in its current state so you\n  can switch to other files while keeping the old information displayed for\n  reference. (Kian Ryan)\n- New command :TagbarCurrentTag which reports the same information as\n  currenttag().\n- New option tagbar_indent to configure the indentation depth of the tags.\n- New option tagbar_show_visibility to allow disabling the visibility symbols.\n- Files are now cached locally to avoid additional slowdowns for slow\n  connections. This also makes it possible to use Tagbar with files accessed\n  through Netrw.\n- Execute ctags again even if the previous run reported errors, in case it was\n  a parse error that has since been fixed. If the error persists, don't\n  display it again.\n- Improved window switching and Vim exit behaviours. (Techlive Zheng)\n- The currenttag() function now can show the prototype instead of the actual\n  tag, which can be useful in some cases where ctags doesn't report all the\n  interesting information.\n- The prototype shown in the tooltip or command line should now always be\n  complete, even if it is spread out over more than one line in the source\n  file.\n- The TagbarAccessPublic etc. highlight groups have been renamed to\n  TagbarVisibilityPublic etc. to keep them in line with standard terminology.\n  The old names are still supported.\n- Various smaller improvements and bugfixes.\n","package":"tagbar.vmb","4":"tagbar.vmb","src_id":"19700","5":"19700","creation_date":"1364204507","6":"1364204507"},{"0":"3465","vim_version":"7.0","1":"7.0","script_version":"2.4.1","2":"2.4.1","version_comment":"- Fixed some bugs related to the currenttag() function when it was called\n  before the rest of the plugin was loaded. Also fail silently in case\n  something goes wrong so the statusline doesn't get messed up.\n- In certain cases highlighting tags in deeply nested folds could cause an\n  error message.\n- Spellchecking is now correctly getting disabled in the Tagbar window.\n","3":"- Fixed some bugs related to the currenttag() function when it was called\n  before the rest of the plugin was loaded. Also fail silently in case\n  something goes wrong so the statusline doesn't get messed up.\n- In certain cases highlighting tags in deeply nested folds could cause an\n  error message.\n- Spellchecking is now correctly getting disabled in the Tagbar window.\n","package":"tagbar.vmb","4":"tagbar.vmb","src_id":"18273","5":"18273","creation_date":"1342431527","6":"1342431527"},{"0":"3465","vim_version":"7.0","1":"7.0","script_version":"2.4","2":"2.4","version_comment":"- New function tagbar#currenttag() that reports the current tag, for example\n  for putting it into the statusline.\n- New command TagbarGetTypeConfig for easy customization of an existing type.\n- Type definitions now can be loaded from ftplugins.\n- The autoopen() function is now a bit more flexible.\n- Vala is now supported if Anjuta is installed.\n- Various other small improvements and bugfixes.\n","3":"- New function tagbar#currenttag() that reports the current tag, for example\n  for putting it into the statusline.\n- New command TagbarGetTypeConfig for easy customization of an existing type.\n- Type definitions now can be loaded from ftplugins.\n- The autoopen() function is now a bit more flexible.\n- Vala is now supported if Anjuta is installed.\n- Various other small improvements and bugfixes.\n","package":"tagbar.vmb","4":"tagbar.vmb","src_id":"18143","5":"18143","creation_date":"1339924929","6":"1339924929"},{"0":"3465","vim_version":"7.0","1":"7.0","script_version":"2.3","2":"2.3","version_comment":"- Add a convenience function that allows more flexible ways to automatically\n  open Tagbar.\n- Replace option tagbar_usearrows with tagbar_iconchars to allow custom\n  characters to be specified. This helps with fonts that don't display the\n  default characters properly.\n- Remove the need to provide the complete jsctags configuration if jsctags is\n  not found in $PATH, now only the concrete path has to be specified.\n- Add debugging functionality.\n","3":"- Add a convenience function that allows more flexible ways to automatically\n  open Tagbar.\n- Replace option tagbar_usearrows with tagbar_iconchars to allow custom\n  characters to be specified. This helps with fonts that don't display the\n  default characters properly.\n- Remove the need to provide the complete jsctags configuration if jsctags is\n  not found in $PATH, now only the concrete path has to be specified.\n- Add debugging functionality.\n","package":"tagbar.vmb","4":"tagbar.vmb","src_id":"17112","5":"17112","creation_date":"1324703741","6":"1324703741"},{"0":"3465","vim_version":"7.0","1":"7.0","script_version":"2.2","2":"2.2","version_comment":"- Small incompatible change: TagbarOpen now doesn't jump to the Tagbar window\n  anymore if it is already open. Use \"TagbarOpen j\" instead or see its\n  documentation for more options.\n- Tags inside of scopes now have a header displaying their \"kind\".\n- The Tagbar contents are now immediately updated on save for files smaller\n  than a configurable size.\n- Tagbar can now be configured to jump to a tag with only a single-click\n  instead of a double-click.\n- Most of the script has been moved to the autoload directory, so Vim startup\n  should be faster (thanks to Kien N).\n- Jumping to tags should work most of the time even if the file has been\n  modified and not saved.\n- If Ctags has been installed into the default location using Homebrew or\n  MacPorts it should now be found automatically.\n- Several bugfixes.\n","3":"- Small incompatible change: TagbarOpen now doesn't jump to the Tagbar window\n  anymore if it is already open. Use \"TagbarOpen j\" instead or see its\n  documentation for more options.\n- Tags inside of scopes now have a header displaying their \"kind\".\n- The Tagbar contents are now immediately updated on save for files smaller\n  than a configurable size.\n- Tagbar can now be configured to jump to a tag with only a single-click\n  instead of a double-click.\n- Most of the script has been moved to the autoload directory, so Vim startup\n  should be faster (thanks to Kien N).\n- Jumping to tags should work most of the time even if the file has been\n  modified and not saved.\n- If Ctags has been installed into the default location using Homebrew or\n  MacPorts it should now be found automatically.\n- Several bugfixes.\n","package":"tagbar.vmb","4":"tagbar.vmb","src_id":"16977","5":"16977","creation_date":"1322289651","6":"1322289651"},{"0":"3465","vim_version":"7.0","1":"7.0","script_version":"2.1","2":"2.1","version_comment":"This is mostly a bug-fix release.\r\n\r\n- Make Tagbar work in (hopefully) all cases under Windows\r\n\r\n- Handle cases where 'encoding' is different from system encoding, for example on a Chinese Windows with 'encoding' set to \"utf-8\" (see manual for details in case it doesn't work out-of-the-box)\r\n\r\n- Fixed a bug with the handling of subtypes like \"python.django\"\r\n\r\n- If a session got saved with Tagbar open it now gets restored properly\r\n\r\n- Locally reset foldmethod\/foldexpr in case foldexpr got set to something expensive globally\r\n\r\n- Tagbar now tries hard to go to the correct window when jumping to a tag\r\n\r\n- Explain some possible issues with the current jsctags version in the manual\r\n\r\n- Explicitly check for some possible configuration problems to be able to give better feedback\r\n\r\n- A few other small fixes","3":"This is mostly a bug-fix release.\r\n\r\n- Make Tagbar work in (hopefully) all cases under Windows\r\n\r\n- Handle cases where 'encoding' is different from system encoding, for example on a Chinese Windows with 'encoding' set to \"utf-8\" (see manual for details in case it doesn't work out-of-the-box)\r\n\r\n- Fixed a bug with the handling of subtypes like \"python.django\"\r\n\r\n- If a session got saved with Tagbar open it now gets restored properly\r\n\r\n- Locally reset foldmethod\/foldexpr in case foldexpr got set to something expensive globally\r\n\r\n- Tagbar now tries hard to go to the correct window when jumping to a tag\r\n\r\n- Explain some possible issues with the current jsctags version in the manual\r\n\r\n- Explicitly check for some possible configuration problems to be able to give better feedback\r\n\r\n- A few other small fixes","package":"tagbar.vba","4":"tagbar.vba","src_id":"15751","5":"15751","creation_date":"1306654442","6":"1306654442"},{"0":"3465","vim_version":"7.0","1":"7.0","script_version":"2.0.1","2":"2.0.1","version_comment":"- Fixed sorting bug when 'ignorecase' is set","3":"- Fixed sorting bug when 'ignorecase' is set","package":"tagbar.vba","4":"tagbar.vba","src_id":"15532","5":"15532","creation_date":"1303823438","6":"1303823438"},{"0":"3465","vim_version":"7.0","1":"7.0","script_version":"2.0","2":"2.0","version_comment":"- Folding now works correctly. Folds will be preserved when leaving the Tagbar window and when switching between files. Also tag types can be configured to be folded by default, which is useful for things like includes and imports.\r\n\r\n- DoctorJS\/jsctags and other compatible programs are now supported.\r\n\r\n- All of the highlight groups can now be overridden.\r\n\r\n- Added keybinding to quickly jump to next\/previous top-level tag.\r\n\r\n- Added Taglist's \"p\" keybinding for jumping to a tag without leaving the Tagbar window.\r\n\r\n- Several bugfixes and other small improvements.","3":"- Folding now works correctly. Folds will be preserved when leaving the Tagbar window and when switching between files. Also tag types can be configured to be folded by default, which is useful for things like includes and imports.\r\n\r\n- DoctorJS\/jsctags and other compatible programs are now supported.\r\n\r\n- All of the highlight groups can now be overridden.\r\n\r\n- Added keybinding to quickly jump to next\/previous top-level tag.\r\n\r\n- Added Taglist's \"p\" keybinding for jumping to a tag without leaving the Tagbar window.\r\n\r\n- Several bugfixes and other small improvements.","package":"tagbar.vba","4":"tagbar.vba","src_id":"15529","5":"15529","creation_date":"1303818647","6":"1303818647"},{"0":"3465","vim_version":"7.0","1":"7.0","script_version":"1.5","2":"1.5","version_comment":"- Type definitions can now include a path to a file with the ctags definition. This is especially useful for ftplugins that can now ship with a complete ctags and Tagbar configuration without requiring user intervention. Thanks to Jan Christoph Ebersbach for the suggestion.\r\n\r\n- Added autofocus setting by Taybin Rutkin. This will put the cursor in the Tagbar window when it is opened.\r\n\r\n- The \"scopes\" field is no longer needed in type definitions, the information is already there in \"scope2kind\". Existing definitions will be ignored.\r\n\r\n- Some fixes and improvements related to redrawing and window switching.","3":"- Type definitions can now include a path to a file with the ctags definition. This is especially useful for ftplugins that can now ship with a complete ctags and Tagbar configuration without requiring user intervention. Thanks to Jan Christoph Ebersbach for the suggestion.\r\n\r\n- Added autofocus setting by Taybin Rutkin. This will put the cursor in the Tagbar window when it is opened.\r\n\r\n- The \"scopes\" field is no longer needed in type definitions, the information is already there in \"scope2kind\". Existing definitions will be ignored.\r\n\r\n- Some fixes and improvements related to redrawing and window switching.","package":"tagbar.vba","4":"tagbar.vba","src_id":"15165","5":"15165","creation_date":"1299409957","6":"1299409957"},{"0":"3465","vim_version":"7.0","1":"7.0","script_version":"1.2","2":"1.2","version_comment":"- Fix typo in Ruby definition\r\n\r\nThanks to Mishail for reporting.","3":"- Fix typo in Ruby definition\r\n\r\nThanks to Mishail for reporting.","package":"tagbar.vba","4":"tagbar.vba","src_id":"15133","5":"15133","creation_date":"1298870607","6":"1298870607"},{"0":"3465","vim_version":"7.0","1":"7.0","script_version":"1.1","2":"1.1","version_comment":"- Don't lose syntax highlighting when ':syntax enable' is called\r\n\r\n- Allow expanding the Vim window when Tagbar is opened\r\n\r\nThanks to Hansi for reporting.","3":"- Don't lose syntax highlighting when ':syntax enable' is called\r\n\r\n- Allow expanding the Vim window when Tagbar is opened\r\n\r\nThanks to Hansi for reporting.","package":"tagbar.vba","4":"tagbar.vba","src_id":"15121","5":"15121","creation_date":"1298713821","6":"1298713821"},{"0":"3465","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"tagbar.vba","4":"tagbar.vba","src_id":"15092","5":"15092","creation_date":"1298437707","6":"1298437707"}]},"3464":{"script_id":"3464","0":"3464","script_name":"Tabular","1":"Tabular","script_type":"utility","2":"utility","summary":"Vim script for text filtering and alignment ","3":"Vim script for text filtering and alignment ","description":"https:\/\/github.com\/godlygeek\/tabular\r\n\r\nNOTE: This script was not created by me!  I'm just uploading it to vim.org because it's useful!\r\n\r\nVim script for text filtering and alignment.","4":"https:\/\/github.com\/godlygeek\/tabular\r\n\r\nNOTE: This script was not created by me!  I'm just uploading it to vim.org because it's useful!\r\n\r\nVim script for text filtering and alignment.","install_details":"","5":"","first_name":"Josh","6":"Josh","last_name":"Adams","7":"Adams","releases":[{"0":"3464","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"tabular.tar.gz","4":"tabular.tar.gz","src_id":"15091","5":"15091","creation_date":"1298421413","6":"1298421413"}]},"3463":{"script_id":"3463","0":"3463","script_name":"dragon","1":"dragon","script_type":"color scheme","2":"color scheme","summary":"Color Scheme resembling the Komodo Dark theme","3":"Color Scheme resembling the Komodo Dark theme","description":"Recommended: Improved JS support http:\/\/www.vim.org\/scripts\/script.php?script_id=1491\r\n\r\nTweaked highlighting for PHP, JS, HTML, CSS.\r\n\r\nUsed the wombat color scheme as the starting point.","4":"Recommended: Improved JS support http:\/\/www.vim.org\/scripts\/script.php?script_id=1491\r\n\r\nTweaked highlighting for PHP, JS, HTML, CSS.\r\n\r\nUsed the wombat color scheme as the starting point.","install_details":"Put the script into your Vim 'colors' directory (e.g. ~\/.vim\/colors), and load it with the command :colorscheme dragon","5":"Put the script into your Vim 'colors' directory (e.g. ~\/.vim\/colors), and load it with the command :colorscheme dragon","first_name":"Bojan","6":"Bojan","last_name":"Zivanovic","7":"Zivanovic","releases":[{"0":"3463","vim_version":"7.0","1":"7.0","script_version":"0.5","2":"0.5","version_comment":"Initial upload","3":"Initial upload","package":"dragon.vim","4":"dragon.vim","src_id":"15090","5":"15090","creation_date":"1298417895","6":"1298417895"}]},"3462":{"script_id":"3462","0":"3462","script_name":"Compile","1":"Compile","script_type":"utility","2":"utility","summary":"initial commit","3":"initial commit","description":"Compile is a small plugin that facilitates the building of programs. Type :Compile or press Ctrl-c c to start the building\r\n\r\nhttps:\/\/github.com\/msambinelli\/Compile","4":"Compile is a small plugin that facilitates the building of programs. Type :Compile or press Ctrl-c c to start the building\r\n\r\nhttps:\/\/github.com\/msambinelli\/Compile","install_details":"","5":"","first_name":"Maycon","6":"Maycon","last_name":"Sambinelli","7":"Sambinelli","releases":[{"0":"3462","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"compile-0.1.tar.gz","4":"compile-0.1.tar.gz","src_id":"15068","5":"15068","creation_date":"1298338679","6":"1298338679"}]},"3461":{"script_id":"3461","0":"3461","script_name":"indent\/python.vim","1":"indent\/python.vim","script_type":"indent","2":"indent","summary":"best plugin for indent python code!","3":"best plugin for indent python code!","description":"modify from http:\/\/www.vim.org\/scripts\/script.php?script_id=974, fix it's bugs,such as:\r\n\r\ndef fun(\r\n    a,\r\n    b\r\n):\r\n    print a,b\r\n\r\nto:\r\n\r\ndef fun(\r\n    a,\r\n    b\r\n    ):\r\n    print a,b","4":"modify from http:\/\/www.vim.org\/scripts\/script.php?script_id=974, fix it's bugs,such as:\r\n\r\ndef fun(\r\n    a,\r\n    b\r\n):\r\n    print a,b\r\n\r\nto:\r\n\r\ndef fun(\r\n    a,\r\n    b\r\n    ):\r\n    print a,b","install_details":"put it into the indent directory,then enjoy it!","5":"put it into the indent directory,then enjoy it!","first_name":"zhu","6":"zhu","last_name":"nianyang","7":"nianyang","releases":[{"0":"3461","vim_version":"7.0","1":"7.0","script_version":"0.1.0","2":"0.1.0","version_comment":"fix some bug.","3":"fix some bug.","package":"python.vim","4":"python.vim","src_id":"20604","5":"20604","creation_date":"1375759475","6":"1375759475"},{"0":"3461","vim_version":"7.0","1":"7.0","script_version":"0.0.9","2":"0.0.9","version_comment":"Comment and string should not indent.","3":"Comment and string should not indent.","package":"python.vim","4":"python.vim","src_id":"15221","5":"15221","creation_date":"1300155486","6":"1300155486"},{"0":"3461","vim_version":"7.0","1":"7.0","script_version":"0.0.8","2":"0.0.8","version_comment":"fix 0.0.7's bug","3":"fix 0.0.7's bug","package":"python.vim","4":"python.vim","src_id":"15188","5":"15188","creation_date":"1299753844","6":"1299753844"},{"0":"3461","vim_version":"7.0","1":"7.0","script_version":"0.0.7","2":"0.0.7","version_comment":"like cindent:\r\n\r\nx(\r\n    1,\r\n    2,\r\n    3\r\n )\r\n\r\nuser.login(\r\n    1,\r\n    2,\r\n    3\r\n    )\r\n","3":"like cindent:\r\n\r\nx(\r\n    1,\r\n    2,\r\n    3\r\n )\r\n\r\nuser.login(\r\n    1,\r\n    2,\r\n    3\r\n    )\r\n","package":"python.vim","4":"python.vim","src_id":"15186","5":"15186","creation_date":"1299726625","6":"1299726625"},{"0":"3461","vim_version":"7.0","1":"7.0","script_version":"0.0.6","2":"0.0.6","version_comment":"fix the bug of call function,the current indent type is: \r\n\r\nuser = create_user( \r\n    a, \r\n    b, \r\n    c \r\n    ) ","3":"fix the bug of call function,the current indent type is: \r\n\r\nuser = create_user( \r\n    a, \r\n    b, \r\n    c \r\n    ) ","package":"python.vim","4":"python.vim","src_id":"15124","5":"15124","creation_date":"1298735185","6":"1298735185"}]},"3460":{"script_id":"3460","0":"3460","script_name":"SVF syntax","1":"SVF syntax","script_type":"syntax","2":"syntax","summary":"Syntax file for SVF - Serial Vector Format files","3":"Syntax file for SVF - Serial Vector Format files","description":"\" Vim syntax file\r\n\" Language:\tSVF - Serial Vector Format, Revision E, 8 March 1999","4":"\" Vim syntax file\r\n\" Language:\tSVF - Serial Vector Format, Revision E, 8 March 1999","install_details":"Copy svf.vim to your $HOME\/.vim\/syntax directory and add \r\n\r\n  autocmd BufNew,BufRead *.svf setf svf\r\n\r\nto your .vimrc. \r\n","5":"Copy svf.vim to your $HOME\/.vim\/syntax directory and add \r\n\r\n  autocmd BufNew,BufRead *.svf setf svf\r\n\r\nto your .vimrc. \r\n","first_name":"Sebastian","6":"Sebastian","last_name":"Witt","7":"Witt","releases":[{"0":"3460","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"svf.vim","4":"svf.vim","src_id":"15051","5":"15051","creation_date":"1298292168","6":"1298292168"}]},"3459":{"script_id":"3459","0":"3459","script_name":"funprototypes.vim","1":"funprototypes.vim","script_type":"utility","2":"utility","summary":"automatic insert function prototypes in your code ","3":"automatic insert function prototypes in your code ","description":" Introdution:\r\n   This script is only for C language. You just press the key which you mapped\r\n   can automatic insert\/replace the all funtions' prototypes in your source code.\r\n Preview:\r\n\r\n    #include<stdio.h>\r\n\r\n   \/\/ The  four lines below are automatic added by funprototypes.vim!\r\n    \/******************************************************\"    \r\n    **               funtion prototypes                 ***\"             \r\n    *******************************************************\/\"        \r\n    void fun_1();                                              \r\n    \r\n    void\r\n    fun_1(){\r\n        printf(\"Hello, VIM!\\n\");\r\n    }\r\n    \r\n    int main()\r\n    {\r\n       fun_1();\r\n       return 0;\r\n    }\r\n\r\nConfigure:\r\n   1. let g:fun_prototypes_static_first = 0\r\n\r\n      if g:fun_prototypes_static_first is 0, then the static functions will\r\n      insert before the global funtions. <default is 0>\r\n\r\n   2. let g:fun_prototypes_skip_fun_list=[\"main\"]\r\n\r\n      This list contains the functions which you don't want funprototypes.vim to add. \r\n      eg:\r\n         int main(){}  \/\/skip\r\n         int _main(){} \/\/doesn't skip\r\n       \r\n   3. let g:fun_prototypes_static_fun_start_list=[\"static\"]\r\n\r\n      This list contains the functions which are defined as static\/LOCAL functions.\r\n\r\n   4. let g:fun_prototypes_header = \/******************************************************\"\r\n      let g:fun_prototypes_body   = \"**               funtion prototypes                 ***\"\r\n      let g:fun_prototypes_footer = *******************************************************\/\"\r\n\r\n      These three lines will insert before first function define. If you only\r\n      want single line, should define like below:\r\n      eg:\r\n      let g:fun_prototypes_header = \"\"\r\n      let g:fun_prototypes_body   = \"\/***************funtion prototypes*******************\/\"\r\n      let g:fun_prototypes_footer = \"\"\r\n      Attention:If these three lines have already inserted in source code, the functions' prototypes will insert after these three lines!\r\n Usage:\r\n    Copy this file to ~\/.vim\/plugin or to \/vimfiles\/plugins\/ (on win32)\r\n    \r\n    Add the key map (default is <leader>fd) in your .vimrc or _vimrc (on win32)\r\n    default:\r\n      nnoremap <silent> <leader>fd :call FunProto()<CR>","4":" Introdution:\r\n   This script is only for C language. You just press the key which you mapped\r\n   can automatic insert\/replace the all funtions' prototypes in your source code.\r\n Preview:\r\n\r\n    #include<stdio.h>\r\n\r\n   \/\/ The  four lines below are automatic added by funprototypes.vim!\r\n    \/******************************************************\"    \r\n    **               funtion prototypes                 ***\"             \r\n    *******************************************************\/\"        \r\n    void fun_1();                                              \r\n    \r\n    void\r\n    fun_1(){\r\n        printf(\"Hello, VIM!\\n\");\r\n    }\r\n    \r\n    int main()\r\n    {\r\n       fun_1();\r\n       return 0;\r\n    }\r\n\r\nConfigure:\r\n   1. let g:fun_prototypes_static_first = 0\r\n\r\n      if g:fun_prototypes_static_first is 0, then the static functions will\r\n      insert before the global funtions. <default is 0>\r\n\r\n   2. let g:fun_prototypes_skip_fun_list=[\"main\"]\r\n\r\n      This list contains the functions which you don't want funprototypes.vim to add. \r\n      eg:\r\n         int main(){}  \/\/skip\r\n         int _main(){} \/\/doesn't skip\r\n       \r\n   3. let g:fun_prototypes_static_fun_start_list=[\"static\"]\r\n\r\n      This list contains the functions which are defined as static\/LOCAL functions.\r\n\r\n   4. let g:fun_prototypes_header = \/******************************************************\"\r\n      let g:fun_prototypes_body   = \"**               funtion prototypes                 ***\"\r\n      let g:fun_prototypes_footer = *******************************************************\/\"\r\n\r\n      These three lines will insert before first function define. If you only\r\n      want single line, should define like below:\r\n      eg:\r\n      let g:fun_prototypes_header = \"\"\r\n      let g:fun_prototypes_body   = \"\/***************funtion prototypes*******************\/\"\r\n      let g:fun_prototypes_footer = \"\"\r\n      Attention:If these three lines have already inserted in source code, the functions' prototypes will insert after these three lines!\r\n Usage:\r\n    Copy this file to ~\/.vim\/plugin or to \/vimfiles\/plugins\/ (on win32)\r\n    \r\n    Add the key map (default is <leader>fd) in your .vimrc or _vimrc (on win32)\r\n    default:\r\n      nnoremap <silent> <leader>fd :call FunProto()<CR>","install_details":"copy funprototypes.vim to ~\/.vim\/plugin\/","5":"copy funprototypes.vim to ~\/.vim\/plugin\/","first_name":"Hong","6":"Hong","last_name":"Wu","7":"Wu","releases":[{"0":"3459","vim_version":"7.0","1":"7.0","script_version":"1.2","2":"1.2","version_comment":" 1.2 fix bug: when first function define at line 1, the script go into an infinite    loop.","3":" 1.2 fix bug: when first function define at line 1, the script go into an infinite    loop.","package":"funprototypes.vim","4":"funprototypes.vim","src_id":"15116","5":"15116","creation_date":"1298643709","6":"1298643709"},{"0":"3459","vim_version":"7.0","1":"7.0","script_version":"1.1","2":"1.1","version_comment":"fix bug: the macro definition in comment & the cpp style comment(\/\/....) above the function.","3":"fix bug: the macro definition in comment & the cpp style comment(\/\/....) above the function.","package":"funprototypes.vim","4":"funprototypes.vim","src_id":"15053","5":"15053","creation_date":"1298299202","6":"1298299202"},{"0":"3459","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"funprototypes.vim","4":"funprototypes.vim","src_id":"15050","5":"15050","creation_date":"1298184883","6":"1298184883"}]},"3458":{"script_id":"3458","0":"3458","script_name":"vundle","1":"vundle","script_type":"utility","2":"utility","summary":"Vundle the Vim package manager","3":"Vundle the Vim package manager","description":"Vundle allows to:\r\n\r\n    * keep track and configure your scripts right in .vimrc\r\n    * install configured scripts (aka bundle)\r\n    * update configured scripts\r\n    * search all available vim scripts by name\r\n    * clean unused scripts up\r\n\r\nAlso as a bonus Vundle:\r\n\r\n    * manages runtime path of your installed scripts\r\n    * regenerates helptag atomatically\r\n","4":"Vundle allows to:\r\n\r\n    * keep track and configure your scripts right in .vimrc\r\n    * install configured scripts (aka bundle)\r\n    * update configured scripts\r\n    * search all available vim scripts by name\r\n    * clean unused scripts up\r\n\r\nAlso as a bonus Vundle:\r\n\r\n    * manages runtime path of your installed scripts\r\n    * regenerates helptag atomatically\r\n","install_details":"https:\/\/github.com\/gmarik\/vundle","5":"https:\/\/github.com\/gmarik\/vundle","first_name":"gmarik","6":"gmarik","last_name":"gmarik","7":"gmarik","releases":[{"0":"3458","vim_version":"7.3","1":"7.3","script_version":"0.5","2":"0.5","version_comment":"fixing empty content","3":"fixing empty content","package":"vundle-0.5.zip","4":"vundle-0.5.zip","src_id":"15098","5":"15098","creation_date":"1298469841","6":"1298469841"},{"0":"3458","vim_version":"7.0","1":"7.0","script_version":"0.5","2":"0.5","version_comment":"Initial upload","3":"Initial upload","package":"vundle.zip","4":"vundle.zip","src_id":"15049","5":"15049","creation_date":"1298159160","6":"1298159160"}]},"3457":{"script_id":"3457","0":"3457","script_name":"vim-paint","1":"vim-paint","script_type":"utility","2":"utility","summary":"vim-paint","3":"vim-paint","description":"Example:\r\n  let canvas = paint#canvas#new(128, 128)\r\n  call canvas.draw_line([0, 0], [63, 63], [0, 0, 0], 1)\r\n  call canvas.draw_line([0, 63], [63, 0], [0, 0, 0], 2)\r\n  call canvas.draw_rect([0, 64], [63, 127], [255, 0, 0], -1)\r\n  call canvas.draw_rect([32, 64], [63, 95], [0, 255, 0], 1)\r\n  call canvas.draw_ellipse([64, 0], [127, 63], [0, 0, 255], -1)\r\n  call canvas.draw_ellipse([64, 32], [95, 63], [255, 255, 0], 2)\r\n  for x in range(64)\r\n    for y in range(64)\r\n      call canvas.set_pixel(x + 64, y + 64, [x * 256 \/ 64, y * 256 \/ 64, 0])\r\n    endfor\r\n  endfor\r\n  let font = paint#bdf#loadfile(globpath(&rtp, 'font\/mplus\/mplus_f12r.bdf'))\r\n  call canvas.draw_text(\"Hello, Vim\", [64, 76], font, [255, 255, 255])\r\n  call canvas.save('example.bmp')\r\n\r\n  result: http:\/\/ynkdir.github.com\/vim-paint\/example.bmp\r\n","4":"Example:\r\n  let canvas = paint#canvas#new(128, 128)\r\n  call canvas.draw_line([0, 0], [63, 63], [0, 0, 0], 1)\r\n  call canvas.draw_line([0, 63], [63, 0], [0, 0, 0], 2)\r\n  call canvas.draw_rect([0, 64], [63, 127], [255, 0, 0], -1)\r\n  call canvas.draw_rect([32, 64], [63, 95], [0, 255, 0], 1)\r\n  call canvas.draw_ellipse([64, 0], [127, 63], [0, 0, 255], -1)\r\n  call canvas.draw_ellipse([64, 32], [95, 63], [255, 255, 0], 2)\r\n  for x in range(64)\r\n    for y in range(64)\r\n      call canvas.set_pixel(x + 64, y + 64, [x * 256 \/ 64, y * 256 \/ 64, 0])\r\n    endfor\r\n  endfor\r\n  let font = paint#bdf#loadfile(globpath(&rtp, 'font\/mplus\/mplus_f12r.bdf'))\r\n  call canvas.draw_text(\"Hello, Vim\", [64, 76], font, [255, 255, 255])\r\n  call canvas.save('example.bmp')\r\n\r\n  result: http:\/\/ynkdir.github.com\/vim-paint\/example.bmp\r\n","install_details":"set runtimepath+=\/path\/to\/vim-paint\r\n\r\nLatest source: https:\/\/github.com\/ynkdir\/vim-paint","5":"set runtimepath+=\/path\/to\/vim-paint\r\n\r\nLatest source: https:\/\/github.com\/ynkdir\/vim-paint","first_name":"Yukihiro","6":"Yukihiro","last_name":"Nakadaira","7":"Nakadaira","releases":[{"0":"3457","vim_version":"7.3","1":"7.3","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"vim-paint.zip","4":"vim-paint.zip","src_id":"15046","5":"15046","creation_date":"1298129852","6":"1298129852"}]},"3456":{"script_id":"3456","0":"3456","script_name":"Chess files (.pgn extension)","1":"Chess files (.pgn extension)","script_type":"syntax","2":"syntax","summary":"Chess files: syntax, ftplugin and snippets","3":"Chess files: syntax, ftplugin and snippets","description":"* Syntax highlighting for .pgn files\r\n* Abbreviations and mappings:\r\niabbrev oo  O-O\r\niabbrev OO  O-O\r\niabbrev 00  O-O\r\niabbrev ooo O-O-O\r\niabbrev OOO O-O-O\r\niabbrev 000 O-O-O\r\ninoremap <buffer> > 1-0\r\ninoremap <buffer> < 0-1\r\nimap <buffer> \\pw ♙\r\nimap <buffer> \\pb ♟\r\nimap <buffer> \\rw ♖\r\nimap <buffer> \\rb ♜\r\nimap <buffer> \\nw ♘\r\nimap <buffer> \\nb ♞\r\nimap <buffer> \\bw ♗\r\nimap <buffer> \\bb ♝\r\nimap <buffer> \\qw ♕\r\nimap <buffer> \\qb ♛\r\nimap <buffer> \\kw ♔\r\nimap <buffer> \\kb ♚\r\n* Commands:\r\nChessBoardEcho\r\nChessBoardPrint\r\nChessNormalize (1. e4 e5 2. -- -- 3. -- -- TO one move per line)\r\n* snipMate snippets:\r\nskel\r\nskeleton\r\n= -> 1\/2-1\/2\r\n== -> 1\/2-1\/2\r\n1\/2 -> \u00c2\u00bd\r\n12 -> \u00c2\u00bd\r\n* Bonus:\r\nIf you write one move per line,\r\nthe plugin will automatically add the correct number for the following move","4":"* Syntax highlighting for .pgn files\r\n* Abbreviations and mappings:\r\niabbrev oo  O-O\r\niabbrev OO  O-O\r\niabbrev 00  O-O\r\niabbrev ooo O-O-O\r\niabbrev OOO O-O-O\r\niabbrev 000 O-O-O\r\ninoremap <buffer> > 1-0\r\ninoremap <buffer> < 0-1\r\nimap <buffer> \\pw ♙\r\nimap <buffer> \\pb ♟\r\nimap <buffer> \\rw ♖\r\nimap <buffer> \\rb ♜\r\nimap <buffer> \\nw ♘\r\nimap <buffer> \\nb ♞\r\nimap <buffer> \\bw ♗\r\nimap <buffer> \\bb ♝\r\nimap <buffer> \\qw ♕\r\nimap <buffer> \\qb ♛\r\nimap <buffer> \\kw ♔\r\nimap <buffer> \\kb ♚\r\n* Commands:\r\nChessBoardEcho\r\nChessBoardPrint\r\nChessNormalize (1. e4 e5 2. -- -- 3. -- -- TO one move per line)\r\n* snipMate snippets:\r\nskel\r\nskeleton\r\n= -> 1\/2-1\/2\r\n== -> 1\/2-1\/2\r\n1\/2 -> \u00c2\u00bd\r\n12 -> \u00c2\u00bd\r\n* Bonus:\r\nIf you write one move per line,\r\nthe plugin will automatically add the correct number for the following move","install_details":":h add-plugin\r\nor\r\nuse pathogen (recommended)\r\n\r\nlatest version at: https:\/\/github.com\/kurkale6ka\/vimfiles\/tree\/master\/bundle\/pgn","5":":h add-plugin\r\nor\r\nuse pathogen (recommended)\r\n\r\nlatest version at: https:\/\/github.com\/kurkale6ka\/vimfiles\/tree\/master\/bundle\/pgn","first_name":"Dimitar","6":"Dimitar","last_name":"Dimitrov","7":"Dimitrov","releases":[{"0":"3456","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"chess.zip","4":"chess.zip","src_id":"15034","5":"15034","creation_date":"1297962859","6":"1297962859"}]},"3455":{"script_id":"3455","0":"3455","script_name":"Headlights","1":"Headlights","script_type":"utility","2":"utility","summary":"A 'Bundles' menu for Vim (like TextMate)","3":"A 'Bundles' menu for Vim (like TextMate)","description":"Headlights adds a 'Bundles' menu to Vim, revealing your bundles (aka. plugins) and the features they provide.\r\n\r\nHeadlights creates a menu for each _currently loaded_ bundle, grouping together docs, commands, mappings, abbreviations, functions, highlights, and plugin files.\r\n\r\nCombined with a powerful bundle manager, Headlights will improve your Vim user experience -- nay, your quality of life.\r\n\r\nHere, have a screenshot: https:\/\/github.com\/mbadran\/headlights\/raw\/master\/headlights_ss.png\r\n\r\nFor development activity, see the GitHub repository: https:\/\/github.com\/mbadran\/headlights\r\n\r\nFor further reading, see the Headlights help menu:\r\n\r\n    Bundles > a - i > headlights > Help","4":"Headlights adds a 'Bundles' menu to Vim, revealing your bundles (aka. plugins) and the features they provide.\r\n\r\nHeadlights creates a menu for each _currently loaded_ bundle, grouping together docs, commands, mappings, abbreviations, functions, highlights, and plugin files.\r\n\r\nCombined with a powerful bundle manager, Headlights will improve your Vim user experience -- nay, your quality of life.\r\n\r\nHere, have a screenshot: https:\/\/github.com\/mbadran\/headlights\/raw\/master\/headlights_ss.png\r\n\r\nFor development activity, see the GitHub repository: https:\/\/github.com\/mbadran\/headlights\r\n\r\nFor further reading, see the Headlights help menu:\r\n\r\n    Bundles > a - i > headlights > Help","install_details":"NOTE: Headlights requires Vim 7+ compiled with Python 2.6+ support.\r\n\r\nTHE RECOMMENDED WAY:\r\n\r\nUsing Vundle -- https:\/\/github.com\/gmarik\/vundle\r\n\r\n1. Add the following line to the Vundle section in your .vimrc:\r\n\r\n    Bundle 'Headlights'\r\n\r\n2. Run the following Vim command:\r\n\r\n    BundleInstall\r\n\r\nTHE MANUAL WAY:\r\n\r\n1. Download the latest package.\r\n\r\n2. Expand the archive's contents into your .vim directory.\r\n\r\n3. Run the following Vim command:\r\n\r\n    helptags <vim_dir>\/<plugin_dir>\/<headlights_dir>\/doc\/","5":"NOTE: Headlights requires Vim 7+ compiled with Python 2.6+ support.\r\n\r\nTHE RECOMMENDED WAY:\r\n\r\nUsing Vundle -- https:\/\/github.com\/gmarik\/vundle\r\n\r\n1. Add the following line to the Vundle section in your .vimrc:\r\n\r\n    Bundle 'Headlights'\r\n\r\n2. Run the following Vim command:\r\n\r\n    BundleInstall\r\n\r\nTHE MANUAL WAY:\r\n\r\n1. Download the latest package.\r\n\r\n2. Expand the archive's contents into your .vim directory.\r\n\r\n3. Run the following Vim command:\r\n\r\n    helptags <vim_dir>\/<plugin_dir>\/<headlights_dir>\/doc\/","first_name":"Mohammed","6":"Mohammed","last_name":"Badran","7":"Badran","releases":[{"0":"3455","vim_version":"7.0","1":"7.0","script_version":"1.5.3","2":"1.5.3","version_comment":"- new option to run on GUI startup\r\n- revert to flat menus\r\n- new option to spillover menus\r\n- doc updates\r\n- minor code and menu usability improvements","3":"- new option to run on GUI startup\r\n- revert to flat menus\r\n- new option to spillover menus\r\n- doc updates\r\n- minor code and menu usability improvements","package":"headlights_1.5.3.zip","4":"headlights_1.5.3.zip","src_id":"18603","5":"18603","creation_date":"1347688395","6":"1347688395"},{"0":"3455","vim_version":"7.0","1":"7.0","script_version":"1.5.2","2":"1.5.2","version_comment":"- prevent headlights from running on GUI startup (faster)\r\n- revamped error handling system\r\n- changed the license\r\n- doc updates\r\n- minor code and usability improvements","3":"- prevent headlights from running on GUI startup (faster)\r\n- revamped error handling system\r\n- changed the license\r\n- doc updates\r\n- minor code and usability improvements","package":"headlights_1.5.2.zip","4":"headlights_1.5.2.zip","src_id":"17948","5":"17948","creation_date":"1336951572","6":"1336951572"},{"0":"3455","vim_version":"7.0","1":"7.0","script_version":"1.5","2":"1.5","version_comment":"- huge performance boost (wait for cursorhold)\r\n- refactoring\r\n- strip the \\'vim-\\' prefix from bundle names\r\n- strip the \\'_vim\\' suffix from bundle names\r\n- doc updates\r\n- usability improvements","3":"- huge performance boost (wait for cursorhold)\r\n- refactoring\r\n- strip the \\'vim-\\' prefix from bundle names\r\n- strip the \\'_vim\\' suffix from bundle names\r\n- doc updates\r\n- usability improvements","package":"headlights_1.5.zip","4":"headlights_1.5.zip","src_id":"17651","5":"17651","creation_date":"1332585592","6":"1332585592"},{"0":"3455","vim_version":"7.0","1":"7.0","script_version":"1.4.2","2":"1.4.2","version_comment":"- highlights bug fix\r\n- doc updates","3":"- highlights bug fix\r\n- doc updates","package":"headlights_1.4.2.zip","4":"headlights_1.4.2.zip","src_id":"17407","5":"17407","creation_date":"1328675624","6":"1328675624"},{"0":"3455","vim_version":"7.0","1":"7.0","script_version":"1.4.1","2":"1.4.1","version_comment":"- usability fixes \r\n- doc updates","3":"- usability fixes \r\n- doc updates","package":"headlights_1.4.1.zip","4":"headlights_1.4.1.zip","src_id":"17375","5":"17375","creation_date":"1328253229","6":"1328253229"},{"0":"3455","vim_version":"7.0","1":"7.0","script_version":"1.4","2":"1.4","version_comment":"    - menus are now intelligently grouped by bundle (optional)\r\n    - autoload bundles are now properly duplicated in the buffer menu\r\n    - new category: highlights\r\n    - usability improvements\r\n    - refactoring and performance tweaks","3":"    - menus are now intelligently grouped by bundle (optional)\r\n    - autoload bundles are now properly duplicated in the buffer menu\r\n    - new category: highlights\r\n    - usability improvements\r\n    - refactoring and performance tweaks","package":"headlights_1.4.zip","4":"headlights_1.4.zip","src_id":"17371","5":"17371","creation_date":"1328230807","6":"1328230807"},{"0":"3455","vim_version":"7.0","1":"7.0","script_version":"1.3","2":"1.3","version_comment":"- added plugin load order\r\n- fixed issue with python line separators across platforms\r\n- fixed menu disordering problem on autoload\r\n- refactoring and performance tweaks\r\n","3":"- added plugin load order\r\n- fixed issue with python line separators across platforms\r\n- fixed menu disordering problem on autoload\r\n- refactoring and performance tweaks\r\n","package":"headlights_1.3.zip","4":"headlights_1.3.zip","src_id":"17254","5":"17254","creation_date":"1326937528","6":"1326937528"},{"0":"3455","vim_version":"7.0","1":"7.0","script_version":"1.2","2":"1.2","version_comment":"- major rewrite\r\n- added a new buffer-local menu\r\n- catered for autoload bundles\r\n- performance optimisations\r\n- several bug fixes and improvements\r\n- dropped autocmds altogether\r\n- reintroduced functions as an optional bundle category\r\n- cleaned up configuration options\r\n- added missing mapping types\r\n- removed the 'occurrences' help option\r\n- updated reference docs","3":"- major rewrite\r\n- added a new buffer-local menu\r\n- catered for autoload bundles\r\n- performance optimisations\r\n- several bug fixes and improvements\r\n- dropped autocmds altogether\r\n- reintroduced functions as an optional bundle category\r\n- cleaned up configuration options\r\n- added missing mapping types\r\n- removed the 'occurrences' help option\r\n- updated reference docs","package":"headlights_1.2.zip","4":"headlights_1.2.zip","src_id":"16078","5":"16078","creation_date":"1310715352","6":"1310715352"},{"0":"3455","vim_version":"7.0","1":"7.0","script_version":"1.1","2":"1.1","version_comment":"- streamlined the menu layout\r\n- fixed the debug mode feature\r\n- added a debug menu for debug mode\r\n- added an 'occurrences' help option (:helpgrep)\r\n- moved vim plugins\/bundles to their own menu (runtime)\r\n- fixed several minor issues\r\n- refactored and cleaned up code","3":"- streamlined the menu layout\r\n- fixed the debug mode feature\r\n- added a debug menu for debug mode\r\n- added an 'occurrences' help option (:helpgrep)\r\n- moved vim plugins\/bundles to their own menu (runtime)\r\n- fixed several minor issues\r\n- refactored and cleaned up code","package":"headlights_1.1.zip","4":"headlights_1.1.zip","src_id":"15808","5":"15808","creation_date":"1307239054","6":"1307239054"},{"0":"3455","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"headlights.zip","4":"headlights.zip","src_id":"15032","5":"15032","creation_date":"1297944459","6":"1297944459"}]},"3454":{"script_id":"3454","0":"3454","script_name":"Flog","1":"Flog","script_type":"utility","2":"utility","summary":"Flog integration for Ruby files","3":"Flog integration for Ruby files","description":"Indicates the Flog number in front of the action in your Ruby code to indicate the complexity.","4":"Indicates the Flog number in front of the action in your Ruby code to indicate the complexity.","install_details":"https:\/\/github.com\/fousa\/vim-flog","5":"https:\/\/github.com\/fousa\/vim-flog","first_name":"jelle","6":"jelle","last_name":"vandebeeck","7":"vandebeeck","releases":[{"0":"3454","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"vim-flog.zip","4":"vim-flog.zip","src_id":"15016","5":"15016","creation_date":"1297783160","6":"1297783160"}]},"3453":{"script_id":"3453","0":"3453","script_name":"fecompressor.vim","1":"fecompressor.vim","script_type":"ftplugin","2":"ftplugin","summary":"Auto execute yuicompressor, lessc, sass..etc","3":"Auto execute yuicompressor, lessc, sass..etc","description":"fecompressor.vim is designed to auto execute compressor programes while edit and saving files used in the front end. It supports js, css, less and scss. (Yes, I know less and scss are not compressor)\r\n\r\ngithub repo: https:\/\/github.com\/othree\/fecompressor.vim","4":"fecompressor.vim is designed to auto execute compressor programes while edit and saving files used in the front end. It supports js, css, less and scss. (Yes, I know less and scss are not compressor)\r\n\r\ngithub repo: https:\/\/github.com\/othree\/fecompressor.vim","install_details":"Get vimball file. Open it with vim and execute :so%","5":"Get vimball file. Open it with vim and execute :so%","first_name":"wei ko","6":"wei ko","last_name":"kao","7":"kao","releases":[{"0":"3453","vim_version":"7.0","1":"7.0","script_version":"0.01","2":"0.01","version_comment":"Initial upload","3":"Initial upload","package":"fecompressor.vim-0.01.vba","4":"fecompressor.vim-0.01.vba","src_id":"15015","5":"15015","creation_date":"1297778316","6":"1297778316"}]},"3452":{"script_id":"3452","0":"3452","script_name":"mxl.vim","1":"mxl.vim","script_type":"syntax","2":"syntax","summary":"MaxL script syntax file","3":"MaxL script syntax file","description":"MaxL script syntax file, should be up-to-date with all features of Essbase 9.  If anything is missing, broken, not working well on your setup, or an inconvenience for you, please let me know, all feedback is welcome: <yyq123 at gmail.com>.\r\n\r\nScreenshots:\r\n-------------\r\nhttp:\/\/www.flickr.com\/photos\/yyq123\/5435807280\/","4":"MaxL script syntax file, should be up-to-date with all features of Essbase 9.  If anything is missing, broken, not working well on your setup, or an inconvenience for you, please let me know, all feedback is welcome: <yyq123 at gmail.com>.\r\n\r\nScreenshots:\r\n-------------\r\nhttp:\/\/www.flickr.com\/photos\/yyq123\/5435807280\/","install_details":"1. Copy csc.vim to: ~\/.vim\/syntax\/mxl.vim or \r\n$VIMFILES\\syntax\\mxl.vim\r\n\r\n2. Add the following ommands to your vimrc file:\r\naugroup filetypedetect\r\n   au BufNewFile,BufRead *.msh setfiletype mxl\r\n   au BufNewFile,BufRead *.mxl setfiletype mxl\r\naugroup END ","5":"1. Copy csc.vim to: ~\/.vim\/syntax\/mxl.vim or \r\n$VIMFILES\\syntax\\mxl.vim\r\n\r\n2. Add the following ommands to your vimrc file:\r\naugroup filetypedetect\r\n   au BufNewFile,BufRead *.msh setfiletype mxl\r\n   au BufNewFile,BufRead *.mxl setfiletype mxl\r\naugroup END ","first_name":"Anthony","6":"Anthony","last_name":"Yuan","7":"Yuan","releases":[{"0":"3452","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"mxl.vim","4":"mxl.vim","src_id":"15010","5":"15010","creation_date":"1297750290","6":"1297750290"}]},"3451":{"script_id":"3451","0":"3451","script_name":"lexc\/twolc Syntax Highlighter","1":"lexc\/twolc Syntax Highlighter","script_type":"syntax","2":"syntax","summary":"A syntax highlighter for lexc and twolc files.","3":"A syntax highlighter for lexc and twolc files.","description":"Anyone who has ever worked with lexc or twolc would know what a hellishly eye-destructive experience it can be. Syntax highlighting helps, a lot. Especially with flag diacritics.","4":"Anyone who has ever worked with lexc or twolc would know what a hellishly eye-destructive experience it can be. Syntax highlighting helps, a lot. Especially with flag diacritics.","install_details":"mkdir ~\/.vim\/syntax, and put the file there.\r\nopen ~\/.vimrc and add:\r\n\r\nau BufRead,BufNewFile *.lexc set filetype=lexc\r\nau BufRead,BufNewFile *.twol set filetype=lexc\r\nau! Syntax lexc source $HOME\/.vim\/syntax\/lexc.vim\r\nsyntax on\r\n\r\nNow when you open a .lexc or .twol file, it will automatically use the syntax.\r\nAlternatively, type :set syntax=lexc to use it with any file.\r\n","5":"mkdir ~\/.vim\/syntax, and put the file there.\r\nopen ~\/.vimrc and add:\r\n\r\nau BufRead,BufNewFile *.lexc set filetype=lexc\r\nau BufRead,BufNewFile *.twol set filetype=lexc\r\nau! Syntax lexc source $HOME\/.vim\/syntax\/lexc.vim\r\nsyntax on\r\n\r\nNow when you open a .lexc or .twol file, it will automatically use the syntax.\r\nAlternatively, type :set syntax=lexc to use it with any file.\r\n","first_name":"Brendan","6":"Brendan","last_name":"Molloy","7":"Molloy","releases":[{"0":"3451","vim_version":"7.0","1":"7.0","script_version":"0.9","2":"0.9","version_comment":"Initial upload","3":"Initial upload","package":"lexc.vim","4":"lexc.vim","src_id":"15009","5":"15009","creation_date":"1297748908","6":"1297748908"}]},"3450":{"script_id":"3450","0":"3450","script_name":"RST Tables [works with non-english langu","1":"RST Tables [works with non-english langu","script_type":"ftplugin","2":"ftplugin","summary":"RST Tables : Allows to create and edit restructuredText tables easily [unicode]","3":"RST Tables : Allows to create and edit restructuredText tables easily [unicode]","description":"Edited plugin with cyrillic support (and other non-english, i think).\r\nOriginal plugin: http:\/\/www.vim.org\/scripts\/script.php?script_id=3041","4":"Edited plugin with cyrillic support (and other non-english, i think).\r\nOriginal plugin: http:\/\/www.vim.org\/scripts\/script.php?script_id=3041","install_details":"1. You should install vim_bridge with pypi\/easy_install\/etc. For ArchLinux: easy_install-2.7 vim_bridge.\r\n2. Place plugin in .vim\/plugin folder.\r\n3. Your vim must have python interpreter support.","5":"1. You should install vim_bridge with pypi\/easy_install\/etc. For ArchLinux: easy_install-2.7 vim_bridge.\r\n2. Place plugin in .vim\/plugin folder.\r\n3. Your vim must have python interpreter support.","first_name":"alexander","6":"alexander","last_name":"graham bell","7":"graham bell","releases":[{"0":"3450","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"rst_tables.vim","4":"rst_tables.vim","src_id":"14999","5":"14999","creation_date":"1297362754","6":"1297362754"}]},"3449":{"script_id":"3449","0":"3449","script_name":"Microchip Linker Script syntax file","1":"Microchip Linker Script syntax file","script_type":"syntax","2":"syntax","summary":"Syntax for files *.gld (Microchip Linker Script)","3":"Syntax for files *.gld (Microchip Linker Script)","description":"This package contains two files to provide syntax highlight for *.gld files.\r\n\r\n","4":"This package contains two files to provide syntax highlight for *.gld files.\r\n\r\n","install_details":"Use pathogen.\r\n\r\nOr just unpack contents of the package in your .vim directory.","5":"Use pathogen.\r\n\r\nOr just unpack contents of the package in your .vim directory.","first_name":"Dmitry","6":"Dmitry","last_name":"Frank","7":"Frank","releases":[{"0":"3449","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"microchip.tar.gz","4":"microchip.tar.gz","src_id":"14997","5":"14997","creation_date":"1297341735","6":"1297341735"}]},"3448":{"script_id":"3448","0":"3448","script_name":"File Case Enforcer","1":"File Case Enforcer","script_type":"utility","2":"utility","summary":"Enforce (Windows) filesystem case in buffer names","3":"Enforce (Windows) filesystem case in buffer names","description":"This is for case insensitive but persistent systems like windows, and makes sure that the case of the file isn't changed by how you invoke vim.\r\n\r\nThis was created for Git to function correctly since it IS sensitive to case changes.\r\n","4":"This is for case insensitive but persistent systems like windows, and makes sure that the case of the file isn't changed by how you invoke vim.\r\n\r\nThis was created for Git to function correctly since it IS sensitive to case changes.\r\n","install_details":"This is a plugin.  (place in plugin directory in runtimepath).","5":"This is a plugin.  (place in plugin directory in runtimepath).","first_name":"Michael","6":"Michael","last_name":"Geddes","7":"Geddes","releases":[{"0":"3448","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"FileCaseEnforcer.vim","4":"FileCaseEnforcer.vim","src_id":"14995","5":"14995","creation_date":"1297303318","6":"1297303318"}]},"3447":{"script_id":"3447","0":"3447","script_name":"activity-log","1":"activity-log","script_type":"utility","2":"utility","summary":" Log what you're working on, and when.","3":" Log what you're working on, and when.","description":"Activity log is a plugin which simply logs what you're doing and when. For the latest version, to report a problem, or contact the author please visit https:\/\/github.com\/AD7six\/vim-activity-log\r\n\r\nWhat does it do:\r\n\r\nif you open and save a file, it'll create a log entries such as the following:\r\n\r\n    2011-02-09 08:44:16;open;\/home\/andy\/someproject\/somefile\r\n    2011-02-09 08:44:44;write;\/home\/andy\/someproject\/somefile\r\n    ...\r\n\r\nIf you're in a git repository at the time, it'll also log the current branch at the time of writing, for example:\r\n\r\n\r\n    2011-02-09 08:44:16;open;\/home\/andy\/someproject\/somefile\r\n    2011-02-09 08:44:44;write;\/home\/andy\/someproject\/somefile;special-stuff\r\n    ...\r\n\r\nWhy:\r\n\r\nThe main purpose of this plugin is to make time reporting easy for the forgetful programmer, without additional tools it provides a static log for you, but the format is such that you can easily import or analyze using whatever tool you feel comfortable with.\r\n","4":"Activity log is a plugin which simply logs what you're doing and when. For the latest version, to report a problem, or contact the author please visit https:\/\/github.com\/AD7six\/vim-activity-log\r\n\r\nWhat does it do:\r\n\r\nif you open and save a file, it'll create a log entries such as the following:\r\n\r\n    2011-02-09 08:44:16;open;\/home\/andy\/someproject\/somefile\r\n    2011-02-09 08:44:44;write;\/home\/andy\/someproject\/somefile\r\n    ...\r\n\r\nIf you're in a git repository at the time, it'll also log the current branch at the time of writing, for example:\r\n\r\n\r\n    2011-02-09 08:44:16;open;\/home\/andy\/someproject\/somefile\r\n    2011-02-09 08:44:44;write;\/home\/andy\/someproject\/somefile;special-stuff\r\n    ...\r\n\r\nWhy:\r\n\r\nThe main purpose of this plugin is to make time reporting easy for the forgetful programmer, without additional tools it provides a static log for you, but the format is such that you can easily import or analyze using whatever tool you feel comfortable with.\r\n","install_details":"save activity-log.vim to your vim\/plugin dir.\r\n\r\nIf desired, you can change how your logs are generated by defining g:activity_log_location in your vimrc for example to get monthly logs rather than daily logs:\r\n\r\n let g:activity_log_location = '\/some\/location\/monthlylogs\/%Y\/%m.log'","5":"save activity-log.vim to your vim\/plugin dir.\r\n\r\nIf desired, you can change how your logs are generated by defining g:activity_log_location in your vimrc for example to get monthly logs rather than daily logs:\r\n\r\n let g:activity_log_location = '\/some\/location\/monthlylogs\/%Y\/%m.log'","first_name":"Andy","6":"Andy","last_name":"Dawson","7":"Dawson","releases":[{"0":"3447","vim_version":"7.0","1":"7.0","script_version":"1.3.0","2":"1.3.0","version_comment":"Define the log file locations using a pattern, allow overriding from outside the plugin","3":"Define the log file locations using a pattern, allow overriding from outside the plugin","package":"activity-log.vim","4":"activity-log.vim","src_id":"15023","5":"15023","creation_date":"1297846847","6":"1297846847"},{"0":"3447","vim_version":"7.0","1":"7.0","script_version":"1.2.1","2":"1.2.1","version_comment":"Correct git branch parsing","3":"Correct git branch parsing","package":"activity-log.vim","4":"activity-log.vim","src_id":"14992","5":"14992","creation_date":"1297253058","6":"1297253058"},{"0":"3447","vim_version":"7.0","1":"7.0","script_version":"1.2.0","2":"1.2.0","version_comment":"Initial upload","3":"Initial upload","package":"activity-log.vim","4":"activity-log.vim","src_id":"14991","5":"14991","creation_date":"1297238241","6":"1297238241"}]},"3446":{"script_id":"3446","0":"3446","script_name":"ParseJSON","1":"ParseJSON","script_type":"utility","2":"utility","summary":"Simple JSON Parser ","3":"Simple JSON Parser ","description":"This plugin does not do anything by itself. This is a recursive-descent\r\nJSON parser intended to be called from other Vim plugins or scripts.\r\nAlthough it is possible to parse JSON in Vim using eval(), that is\r\ndangerous if the JSON is from an untrusted source.\r\n\r\nNote: true, false, and null are parsed to 1, 0, and {} respectively because\r\nthere are no equivalents to those values in Vim script.\r\n\r\nUsage:\r\n    let result = ParseJSON(json_str)\r\n\r\nExample:\r\n    :echo ParseJSON('{ \"hello\" : { \"a list\" : [ 1, 2, \"world\", true ] }}')\r\n    {'hello': {'a list': [1, 2, 'world', 1]}}\r\n","4":"This plugin does not do anything by itself. This is a recursive-descent\r\nJSON parser intended to be called from other Vim plugins or scripts.\r\nAlthough it is possible to parse JSON in Vim using eval(), that is\r\ndangerous if the JSON is from an untrusted source.\r\n\r\nNote: true, false, and null are parsed to 1, 0, and {} respectively because\r\nthere are no equivalents to those values in Vim script.\r\n\r\nUsage:\r\n    let result = ParseJSON(json_str)\r\n\r\nExample:\r\n    :echo ParseJSON('{ \"hello\" : { \"a list\" : [ 1, 2, \"world\", true ] }}')\r\n    {'hello': {'a list': [1, 2, 'world', 1]}}\r\n","install_details":"Add parsejson.vim to your Vim plugins folder.\r\n","5":"Add parsejson.vim to your Vim plugins folder.\r\n","first_name":"Po Shan","6":"Po Shan","last_name":"Cheah","7":"Cheah","releases":[{"0":"3446","vim_version":"7.0","1":"7.0","script_version":"0.0.1","2":"0.0.1","version_comment":"Initial upload","3":"Initial upload","package":"parsejson.vim","4":"parsejson.vim","src_id":"14988","5":"14988","creation_date":"1297179817","6":"1297179817"}]},"3445":{"script_id":"3445","0":"3445","script_name":"Getafe","1":"Getafe","script_type":"color scheme","2":"color scheme","summary":"This package contains a selfmade colorscheme for gvim - GUI and 256 terminals ","3":"This package contains a selfmade colorscheme for gvim - GUI and 256 terminals ","description":"This colorscheme was inspired by the Molokai color scheme. This is a dark theme for GUI and 256 color terminals. See screenshot here: http:\/\/i.imgur.com\/egLXj.png\r\n\r\nYou can fork it from Github: https:\/\/github.com\/larssmit\/vim-getafe","4":"This colorscheme was inspired by the Molokai color scheme. This is a dark theme for GUI and 256 color terminals. See screenshot here: http:\/\/i.imgur.com\/egLXj.png\r\n\r\nYou can fork it from Github: https:\/\/github.com\/larssmit\/vim-getafe","install_details":"Copy the colorscheme into to the directory: ~\/.vim\/colors","5":"Copy the colorscheme into to the directory: ~\/.vim\/colors","first_name":"Lars","6":"Lars","last_name":"Smit","7":"Smit","releases":[{"0":"3445","vim_version":"7.0","1":"7.0","script_version":"2.1","2":"2.1","version_comment":"Added red color (for errors\/exceptions)","3":"Added red color (for errors\/exceptions)","package":"getafe.vim","4":"getafe.vim","src_id":"19387","5":"19387","creation_date":"1358588780","6":"1358588780"},{"0":"3445","vim_version":"7.3","1":"7.3","script_version":"2.0","2":"2.0","version_comment":"Added new and improved brighter colors for more readabiltity. Simplified, to make it feel more cohesent.","3":"Added new and improved brighter colors for more readabiltity. Simplified, to make it feel more cohesent.","package":"getafe.vim","4":"getafe.vim","src_id":"18004","5":"18004","creation_date":"1337577444","6":"1337577444"},{"0":"3445","vim_version":"7.3","1":"7.3","script_version":"1.0","2":"1.0","version_comment":"- updated colors for cursor, search, visual selection to pink.\r\n- updated regular string\/constant color from pink to purple for beter readibility\r\n- several minor issues\r\n","3":"- updated colors for cursor, search, visual selection to pink.\r\n- updated regular string\/constant color from pink to purple for beter readibility\r\n- several minor issues\r\n","package":"getafe.vim","4":"getafe.vim","src_id":"17378","5":"17378","creation_date":"1328338956","6":"1328338956"},{"0":"3445","vim_version":"7.0","1":"7.0","script_version":"0.4","2":"0.4","version_comment":"- Added foreground colors for Visual mode \r\n- Added new cursorline background color","3":"- Added foreground colors for Visual mode \r\n- Added new cursorline background color","package":"getafe.vim","4":"getafe.vim","src_id":"15109","5":"15109","creation_date":"1298556405","6":"1298556405"},{"0":"3445","vim_version":"7.0","1":"7.0","script_version":"0.3","2":"0.3","version_comment":"Added cursorline foreground (especially handy in Visual mode)","3":"Added cursorline foreground (especially handy in Visual mode)","package":"getafe.vim","4":"getafe.vim","src_id":"15052","5":"15052","creation_date":"1298298328","6":"1298298328"},{"0":"3445","vim_version":"7.0","1":"7.0","script_version":"0.2","2":"0.2","version_comment":"Added RGB colorcodes for terminals for the main colors.","3":"Added RGB colorcodes for terminals for the main colors.","package":"getafe.vim","4":"getafe.vim","src_id":"14998","5":"14998","creation_date":"1297343257","6":"1297343257"},{"0":"3445","vim_version":"7.3","1":"7.3","script_version":"7.3","2":"7.3","version_comment":"Initial upload","3":"Initial upload","package":"getafe.vim","4":"getafe.vim","src_id":"14973","5":"14973","creation_date":"1297110377","6":"1297110377"}]},"3444":{"script_id":"3444","0":"3444","script_name":"golded.vim","1":"golded.vim","script_type":"color scheme","2":"color scheme","summary":"Based on GoldED from Amiga. Using low contrast colors to avoid flicking effects.","3":"Based on GoldED from Amiga. Using low contrast colors to avoid flicking effects.","description":"I made this color scheme cause I'm a Web developper and I switch all the time between light and dark windows. This color scheme uses a set of low contrast colors.\r\nInitially made for PHP, i'm using it with REBOL and D without problems.\r\n\r\nscreen:\r\nhttp:\/\/art.oui.la\/public\/www.vim.org\/01.png\r\nhttp:\/\/art.oui.la\/public\/www.vim.org\/02.png\r\n","4":"I made this color scheme cause I'm a Web developper and I switch all the time between light and dark windows. This color scheme uses a set of low contrast colors.\r\nInitially made for PHP, i'm using it with REBOL and D without problems.\r\n\r\nscreen:\r\nhttp:\/\/art.oui.la\/public\/www.vim.org\/01.png\r\nhttp:\/\/art.oui.la\/public\/www.vim.org\/02.png\r\n","install_details":"Place the golded.vim file in the directory \"~\/.vim\/colors\" or \"program files\\vim\\vimfiles\\colors\\\". Type \":colo golded\" to apply the color scheme.","5":"Place the golded.vim file in the directory \"~\/.vim\/colors\" or \"program files\\vim\\vimfiles\\colors\\\". Type \":colo golded\" to apply the color scheme.","first_name":"martin","6":"martin","last_name":"mauchauff\u00c3\u00a9e","7":"mauchauff\u00c3\u00a9e","releases":[{"0":"3444","vim_version":"7.0","1":"7.0","script_version":"0.2","2":"0.2","version_comment":"Improve terminal colors","3":"Improve terminal colors","package":"golded.vim","4":"golded.vim","src_id":"21570","5":"21570","creation_date":"1393926332","6":"1393926332"},{"0":"3444","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"golded.vim","4":"golded.vim","src_id":"14970","5":"14970","creation_date":"1297083713","6":"1297083713"}]},"3443":{"script_id":"3443","0":"3443","script_name":"pbcopy.vim","1":"pbcopy.vim","script_type":"ftplugin","2":"ftplugin","summary":"Mac OS X pasteboard interaction","3":"Mac OS X pasteboard interaction","description":"This is a tiny plugin to enable users of vim within tmux on Mac OS X to paste from vim into the system clipboard. It provides a single command, :PBCopy, which puts the content of the last register into the Mac OS X pasteboard.\r\n\r\nFull details of this plugin can be found at its github page, https:\/\/github.com\/mortice\/pbcopy.vim","4":"This is a tiny plugin to enable users of vim within tmux on Mac OS X to paste from vim into the system clipboard. It provides a single command, :PBCopy, which puts the content of the last register into the Mac OS X pasteboard.\r\n\r\nFull details of this plugin can be found at its github page, https:\/\/github.com\/mortice\/pbcopy.vim","install_details":"","5":"","first_name":"Tom","6":"Tom","last_name":"Stuart","7":"Stuart","releases":[{"0":"3443","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"mortice-pbcopy.vim-e79adf8.zip","4":"mortice-pbcopy.vim-e79adf8.zip","src_id":"14968","5":"14968","creation_date":"1297072126","6":"1297072126"}]},"3442":{"script_id":"3442","0":"3442","script_name":"Royal Colorschemes","1":"Royal Colorschemes","script_type":"color scheme","2":"color scheme","summary":"Royal Colorschemes for gvim","3":"Royal Colorschemes for gvim","description":"This package contains two selfmade colorschemes for gvim and has specific syntax highlighting for c, c++ and ruby. \r\n\r\nRoyalking (http:\/\/img13.imageshack.us\/img13\/7114\/royalking.png)\r\n- dark colorscheme with light golden keywords\r\n\r\nRoyaltango (http:\/\/img64.imageshack.us\/img64\/7064\/royaltango.png)\r\n- light colorscheme with navy blue keywords\r\n\r\nHope you all like it ...\r\n\r\n","4":"This package contains two selfmade colorschemes for gvim and has specific syntax highlighting for c, c++ and ruby. \r\n\r\nRoyalking (http:\/\/img13.imageshack.us\/img13\/7114\/royalking.png)\r\n- dark colorscheme with light golden keywords\r\n\r\nRoyaltango (http:\/\/img64.imageshack.us\/img64\/7064\/royaltango.png)\r\n- light colorscheme with navy blue keywords\r\n\r\nHope you all like it ...\r\n\r\n","install_details":"Simple copy the colorschemes into to the directory: ~\/.vim\/colors","5":"Simple copy the colorschemes into to the directory: ~\/.vim\/colors","first_name":"Chris","6":"Chris","last_name":"M\u00c3\u00bcller","7":"M\u00c3\u00bcller","releases":[{"0":"3442","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"royal_colorschemes.zip","4":"royal_colorschemes.zip","src_id":"14967","5":"14967","creation_date":"1297066958","6":"1297066958"}]},"3441":{"script_id":"3441","0":"3441","script_name":"XFST syntax file","1":"XFST syntax file","script_type":"syntax","2":"syntax","summary":"Syntax file for Xerox Finite-State Tools grammars","3":"Syntax file for Xerox Finite-State Tools grammars","description":"Provides basic syntax highlighting for Xerox Finite-State Tools (XFST) grammars (http:\/\/www.fsmbook.com\/).","4":"Provides basic syntax highlighting for Xerox Finite-State Tools (XFST) grammars (http:\/\/www.fsmbook.com\/).","install_details":"Copy this file in the syntax\/ subdirectory in your ~\/.vim\/ or vimfiles\/ directory. The highlighting is then triggered with the \":set syntax=xfst\" command.\r\n\r\nIf you want all files with the extension \".xfst\" to be recognized automatically, put a filetype.vim file with the following contents in your ~\/.vim\/ or vimfiles\/ directory:\r\n\r\naugroup filetypedetect\r\nau BufNewFile,BufRead *.xfst setf xfst\r\naugroup END","5":"Copy this file in the syntax\/ subdirectory in your ~\/.vim\/ or vimfiles\/ directory. The highlighting is then triggered with the \":set syntax=xfst\" command.\r\n\r\nIf you want all files with the extension \".xfst\" to be recognized automatically, put a filetype.vim file with the following contents in your ~\/.vim\/ or vimfiles\/ directory:\r\n\r\naugroup filetypedetect\r\nau BufNewFile,BufRead *.xfst setf xfst\r\naugroup END","first_name":"Ondrej","6":"Ondrej","last_name":"Dusek","7":"Dusek","releases":[{"0":"3441","vim_version":"7.0","1":"7.0","script_version":"0.1.1","2":"0.1.1","version_comment":"Corrected line endings for Unix (LF instead of CR\/LF)","3":"Corrected line endings for Unix (LF instead of CR\/LF)","package":"xfst.vim","4":"xfst.vim","src_id":"15587","5":"15587","creation_date":"1304613531","6":"1304613531"},{"0":"3441","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"xfst.vim","4":"xfst.vim","src_id":"14959","5":"14959","creation_date":"1296948043","6":"1296948043"}]},"3440":{"script_id":"3440","0":"3440","script_name":"neco-look","1":"neco-look","script_type":"utility","2":"utility","summary":"A neocomplcache plugin for `\/usr\/bin\/look` for completing words in English.","3":"A neocomplcache plugin for `\/usr\/bin\/look` for completing words in English.","description":"A neocomplcache plugin for `\/usr\/bin\/look` for completing English.\n\nhttp:\/\/gyazo.com\/c21c8201fa7a571c7665bc7455d88631.png\n","4":"A neocomplcache plugin for `\/usr\/bin\/look` for completing English.\n\nhttp:\/\/gyazo.com\/c21c8201fa7a571c7665bc7455d88631.png\n","install_details":"* install the latest neocomplcache.vim\n* make sure if you already have `look` command\n* Unarchive neco-look and put it into a dir of your &rtp.\n","5":"* install the latest neocomplcache.vim\n* make sure if you already have `look` command\n* Unarchive neco-look and put it into a dir of your &rtp.\n","first_name":"ujihisa","6":"ujihisa","last_name":".","7":".","releases":[{"0":"3440","vim_version":"7.3","1":"7.3","script_version":"1.3","2":"1.3","version_comment":"Works also with neocomplete.vim besides neocomplcache. (patches from Shougo)","3":"Works also with neocomplete.vim besides neocomplcache. (patches from Shougo)","package":"neco-look-1.3.zip","4":"neco-look-1.3.zip","src_id":"20445","5":"20445","creation_date":"1372260921","6":"1372260921"},{"0":"3440","vim_version":"7.3","1":"7.3","script_version":"1.2","2":"1.2","version_comment":"Works also in comment area of of arbitrary programming languages. (patches from ypresto)","3":"Works also in comment area of of arbitrary programming languages. (patches from ypresto)","package":"neco-look-1.2.zip","4":"neco-look-1.2.zip","src_id":"20095","5":"20095","creation_date":"1368319551","6":"1368319551"},{"0":"3440","vim_version":"7.3","1":"7.3","script_version":"1.1","2":"1.1","version_comment":"Bugfix. It doesn't crash when you input a multibyte word","3":"Bugfix. It doesn't crash when you input a multibyte word","package":"neco-look-1.1.zip","4":"neco-look-1.1.zip","src_id":"14993","5":"14993","creation_date":"1297291774","6":"1297291774"},{"0":"3440","vim_version":"7.3","1":"7.3","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"neco-look-1.0.zip","4":"neco-look-1.0.zip","src_id":"14952","5":"14952","creation_date":"1296787588","6":"1296787588"}]},"3439":{"script_id":"3439","0":"3439","script_name":"Cobaltish","1":"Cobaltish","script_type":"color scheme","2":"color scheme","summary":"Colour scheme inspired by Textmates Cobalt colour scheme","3":"Colour scheme inspired by Textmates Cobalt colour scheme","description":"This is a Vim version of one of TextMate's default colour schemes, Cobalt. Only designed for GVim. It doesn't try to accurately reflect the TextMate Cobalt colour scheme but instead is inspired by it. For a more accurate version of the TextMate colour scheme, see vimscript#2828.\r\n\r\nIf you want to follow the development you can find it on Github at http:\/\/github.com\/dterei\/VimCobaltColourScheme","4":"This is a Vim version of one of TextMate's default colour schemes, Cobalt. Only designed for GVim. It doesn't try to accurately reflect the TextMate Cobalt colour scheme but instead is inspired by it. For a more accurate version of the TextMate colour scheme, see vimscript#2828.\r\n\r\nIf you want to follow the development you can find it on Github at http:\/\/github.com\/dterei\/VimCobaltColourScheme","install_details":"Download and copy to ~\/.vim\/colors directory.","5":"Download and copy to ~\/.vim\/colors directory.","first_name":"David","6":"David","last_name":"Terei","7":"Terei","releases":[{"0":"3439","vim_version":"7.0","1":"7.0","script_version":"1.2","2":"1.2","version_comment":"* Improvements to the window dividers","3":"* Improvements to the window dividers","package":"cobaltish.vim","4":"cobaltish.vim","src_id":"15087","5":"15087","creation_date":"1298404461","6":"1298404461"},{"0":"3439","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial Version","3":"Initial Version","package":"cobaltish.vim","4":"cobaltish.vim","src_id":"14948","5":"14948","creation_date":"1296770371","6":"1296770371"}]},"3438":{"script_id":"3438","0":"3438","script_name":"cscope_plus.vim","1":"cscope_plus.vim","script_type":"ftplugin","2":"ftplugin","summary":"Advanced cscope settings","3":"Advanced cscope settings","description":"This plug-in has features:\r\n- It adds standard cscope mappings (see `:help cscope')\r\n- It searches `cscope.out' file in:\r\n    1. The directory containing where the file which was opened or selected.\r\n    2. The current working directory.\r\n    3. $CSCOPE_DB.\r\n-  It switches to relevant cscope connection.","4":"This plug-in has features:\r\n- It adds standard cscope mappings (see `:help cscope')\r\n- It searches `cscope.out' file in:\r\n    1. The directory containing where the file which was opened or selected.\r\n    2. The current working directory.\r\n    3. $CSCOPE_DB.\r\n-  It switches to relevant cscope connection.","install_details":"Copy cscope_plus.vim in ~\/.vim\/ftplugin","5":"Copy cscope_plus.vim in ~\/.vim\/ftplugin","first_name":"Konstantin","6":"Konstantin","last_name":"Lepa","7":"Lepa","releases":[{"0":"3438","vim_version":"7.0","1":"7.0","script_version":"1.0.0","2":"1.0.0","version_comment":"Initial upload","3":"Initial upload","package":"cscope_plus.vim","4":"cscope_plus.vim","src_id":"14945","5":"14945","creation_date":"1296731477","6":"1296731477"}]},"3437":{"script_id":"3437","0":"3437","script_name":"PreciseJump","1":"PreciseJump","script_type":"utility","2":"utility","summary":"PreciseJump - script to ease on-screen motion.","3":"PreciseJump - script to ease on-screen motion.","description":"PreciseJump - script to ease on-screen motion\r\n\r\nI find\r\n    <number>motion\r\nnot very practical for bigger <numbers>.\r\n\r\nI usually don't know exactly how many times I want the motion to be repeated - I just see place on the screen where I want to jump to.\r\n\r\nThis script is addressing this inconvenience.\r\n\r\nWhen the motion key is pressed, possible jump targets are highlighted. You just have to type character that appeared on desired place.\r\n\r\ni.e: If you press '_fx' you get all 'x' characters that are visible in current window highlighted and changed to some unique chars. Pressing the highlighted char will quickly take the cursor to place you want.\r\n\r\nFor little demo you can see:\r\n http:\/\/i258.photobucket.com\/albums\/hh246\/otokan\/PJ_animation.gif\r\n\r\nPlugin definines following mappings:  \r\n_f - jump to given char in whole window  \r\n_F - jump to given char in a line\r\n\r\nThis script is usable right now, but keep in mind that it still is being developed. \r\n\r\nIf you have any comments, have found bugs, know how to make something better\r\n - let me know.\r\n\r\nSpecial thanks to: Filip, Adam, Sergey, John, Jim\r\n","4":"PreciseJump - script to ease on-screen motion\r\n\r\nI find\r\n    <number>motion\r\nnot very practical for bigger <numbers>.\r\n\r\nI usually don't know exactly how many times I want the motion to be repeated - I just see place on the screen where I want to jump to.\r\n\r\nThis script is addressing this inconvenience.\r\n\r\nWhen the motion key is pressed, possible jump targets are highlighted. You just have to type character that appeared on desired place.\r\n\r\ni.e: If you press '_fx' you get all 'x' characters that are visible in current window highlighted and changed to some unique chars. Pressing the highlighted char will quickly take the cursor to place you want.\r\n\r\nFor little demo you can see:\r\n http:\/\/i258.photobucket.com\/albums\/hh246\/otokan\/PJ_animation.gif\r\n\r\nPlugin definines following mappings:  \r\n_f - jump to given char in whole window  \r\n_F - jump to given char in a line\r\n\r\nThis script is usable right now, but keep in mind that it still is being developed. \r\n\r\nIf you have any comments, have found bugs, know how to make something better\r\n - let me know.\r\n\r\nSpecial thanks to: Filip, Adam, Sergey, John, Jim\r\n","install_details":"Unpack archive and copy PreciseJump.vim to your plugin directory and PreciseJump.txt to your documentation directory.","5":"Unpack archive and copy PreciseJump.vim to your plugin directory and PreciseJump.txt to your documentation directory.","first_name":"Bartlomiej","6":"Bartlomiej","last_name":"P.","7":"P.","releases":[{"0":"3437","vim_version":"7.2","1":"7.2","script_version":"0.49","2":"0.49","version_comment":"Many fixes. PJ works now in 2D (whole visible window, not only current line).","3":"Many fixes. PJ works now in 2D (whole visible window, not only current line).","package":"PreciseJump-0.49.zip","4":"PreciseJump-0.49.zip","src_id":"15295","5":"15295","creation_date":"1301169854","6":"1301169854"},{"0":"3437","vim_version":"7.2","1":"7.2","script_version":"0.1_SOA1","2":"0.1_SOA1","version_comment":"Initial upload","3":"Initial upload","package":"PreciseJump.vim","4":"PreciseJump.vim","src_id":"14939","5":"14939","creation_date":"1296651876","6":"1296651876"}]},"3436":{"script_id":"3436","0":"3436","script_name":"twilight256.vim","1":"twilight256.vim","script_type":"color scheme","2":"color scheme","summary":"A color scheme that imitates the Twilight theme for TextMate","3":"A color scheme that imitates the Twilight theme for TextMate","description":"This color scheme imitates the TextMate theme Twilight.\r\n\r\nA screenshot can be viewed here:\r\nhttp:\/\/nealmilstein.com\/ext\/twilight256.png\r\n\r\nThe theme is designed to be used on a black background. I only tested it\r\nusing a 256-color terminal; I do not think it will work on much else (gvim,\r\n8-color terminal, etc.).\r\n\r\nThe functions in this theme that convert hex color codes to the nearest\r\nxterm-256 color number are from the theme desert2 (desert256), developed by Henry So, Jr. \r\n\r\nThe colors of this theme are based on the TextMate Twilight theme\r\n\u00e2\u0080\u0093 www.macromates.com","4":"This color scheme imitates the TextMate theme Twilight.\r\n\r\nA screenshot can be viewed here:\r\nhttp:\/\/nealmilstein.com\/ext\/twilight256.png\r\n\r\nThe theme is designed to be used on a black background. I only tested it\r\nusing a 256-color terminal; I do not think it will work on much else (gvim,\r\n8-color terminal, etc.).\r\n\r\nThe functions in this theme that convert hex color codes to the nearest\r\nxterm-256 color number are from the theme desert2 (desert256), developed by Henry So, Jr. \r\n\r\nThe colors of this theme are based on the TextMate Twilight theme\r\n\u00e2\u0080\u0093 www.macromates.com","install_details":"Just drop it in ~\/.vim\/colors and run :colorscheme twilight256 and you should be in business.","5":"Just drop it in ~\/.vim\/colors and run :colorscheme twilight256 and you should be in business.","first_name":"Neal","6":"Neal","last_name":"Milstein","7":"Milstein","releases":[{"0":"3436","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"twilight256.vim","4":"twilight256.vim","src_id":"14937","5":"14937","creation_date":"1296618995","6":"1296618995"}]},"3435":{"script_id":"3435","0":"3435","script_name":"codepath.vim","1":"codepath.vim","script_type":"utility","2":"utility","summary":"A function for your root project path","3":"A function for your root project path","description":"codepath.vim is a plugin that provides a simple function to obtain your code\r\npath directory if you have one. The concept is simple: I have a dir located\r\nin $HOME\/code where i store all my projects and I want to set current project\r\ndirectory as root directory for plug-in like NERDTree and CommandT.\r\n\r\nIt provides a function you can use in the following ways:\r\n\r\nnnoremap <silent> <F4> :NERDTreeToggle `=codepath#path()`<cr>\r\ninoremap <silent> <F4> <Esc>:NERDTreeToggle `=codepath#path()` <cr>\r\n\r\nor\r\n\r\nmap   <silent> <C-T> :CommandT <c-r>=codepath#path()<CR><CR>\r\nimap   <silent> <C-T> <ESC>:CommandT <c-r>=codepath#path()<CR><CR>","4":"codepath.vim is a plugin that provides a simple function to obtain your code\r\npath directory if you have one. The concept is simple: I have a dir located\r\nin $HOME\/code where i store all my projects and I want to set current project\r\ndirectory as root directory for plug-in like NERDTree and CommandT.\r\n\r\nIt provides a function you can use in the following ways:\r\n\r\nnnoremap <silent> <F4> :NERDTreeToggle `=codepath#path()`<cr>\r\ninoremap <silent> <F4> <Esc>:NERDTreeToggle `=codepath#path()` <cr>\r\n\r\nor\r\n\r\nmap   <silent> <C-T> :CommandT <c-r>=codepath#path()<CR><CR>\r\nimap   <silent> <C-T> <ESC>:CommandT <c-r>=codepath#path()<CR><CR>","install_details":"Unzip it into your $HOME\/.vim\/plugin","5":"Unzip it into your $HOME\/.vim\/plugin","first_name":"Luca","6":"Luca","last_name":"Pette","7":"Pette","releases":[{"0":"3435","vim_version":"7.0","1":"7.0","script_version":"1.0.0","2":"1.0.0","version_comment":"Rewritten. Use only VimL now. Very ligth.","3":"Rewritten. Use only VimL now. Very ligth.","package":"codepath.zip","4":"codepath.zip","src_id":"16601","5":"16601","creation_date":"1317333947","6":"1317333947"},{"0":"3435","vim_version":"7.0","1":"7.0","script_version":"0.1.1","2":"0.1.1","version_comment":"Added a statusline","3":"Added a statusline","package":"codepath.zip","4":"codepath.zip","src_id":"16428","5":"16428","creation_date":"1314887528","6":"1314887528"},{"0":"3435","vim_version":"7.0","1":"7.0","script_version":"0.0.4","2":"0.0.4","version_comment":"Please take care, this version is not compatible with the previous versions. See docs or readme on github for changes ","3":"Please take care, this version is not compatible with the previous versions. See docs or readme on github for changes ","package":"codepath.zip","4":"codepath.zip","src_id":"15575","5":"15575","creation_date":"1304448736","6":"1304448736"},{"0":"3435","vim_version":"7.0","1":"7.0","script_version":"0.0.3","2":"0.0.3","version_comment":"more simple implementation of path-related methods","3":"more simple implementation of path-related methods","package":"codepath.zip","4":"codepath.zip","src_id":"15215","5":"15215","creation_date":"1300096194","6":"1300096194"},{"0":"3435","vim_version":"7.0","1":"7.0","script_version":"0.0.2","2":"0.0.2","version_comment":"bug fixing","3":"bug fixing","package":"codepath.zip","4":"codepath.zip","src_id":"15206","5":"15206","creation_date":"1299970735","6":"1299970735"},{"0":"3435","vim_version":"7.0","1":"7.0","script_version":"0.0.1","2":"0.0.1","version_comment":"See https:\/\/github.com\/lucapette\/codepath.vim for new configurations and features","3":"See https:\/\/github.com\/lucapette\/codepath.vim for new configurations and features","package":"codepath.zip","4":"codepath.zip","src_id":"15204","5":"15204","creation_date":"1299940794","6":"1299940794"},{"0":"3435","vim_version":"7.0","1":"7.0","script_version":"0.0.1","2":"0.0.1","version_comment":"Initial upload","3":"Initial upload","package":"codepath.zip","4":"codepath.zip","src_id":"14927","5":"14927","creation_date":"1296491811","6":"1296491811"}]},"3434":{"script_id":"3434","0":"3434","script_name":"IniParser","1":"IniParser","script_type":"utility","2":"utility","summary":"This plugin provides functions to read and write ini files for vimscript.","3":"This plugin provides functions to read and write ini files for vimscript.","description":"IniParser provides a function for parsing ini files. The following is a short\r\nexample of how to use this function.\r\n\r\nAssuming you have an ini file in the current directory, whose name is\r\n\"planets.ini\" with the following content:\r\n=======================\r\n[Venus]\r\nmass=4.86900e24 kg\r\nradius=6051.8 km\r\nsatellites=0\r\n\r\n[Earth]\r\nmass=5.9742e24 kg\r\nradius=6378.1 km\r\nsatellites=1\r\n\r\n[Mars]\r\nradius=3397 km\r\nmass=0.64191e24 kg\r\nsatellites=2\r\n=======================\r\n\r\nNow we want to know the mass of Mars and the radius of the Earth by vimscript.\r\nFirst we need to parse the file by calling IniParser#Read:\r\n\r\n let ini_result = IniParser#Read('.\/planets.ini')\r\n\r\n\r\nThen the following two lines shows the mass of Mars and the radius of the\r\nEarth respectively:\r\n\r\n echo ini_result['Mars']['mass']\r\n echo ini_result['Earth']['radius']\r\n\r\n\r\nHere's a little explanation:\r\nThe information of the ini file would be stored in the variable \"ini_result\".\r\n\"ini_result\" is a dictionary, whose key names are the group names and whose\r\nvalues are also dictionaries whose key names are entry names and whose values\r\nare the values of the corresponding keys. If you don't understand it, don't\r\nworry, use the following line to show it:\r\n\r\n echo ini_result\r\n\r\n\r\nHere's the result:\r\n\r\n {'Earth': {'mass': '5.9742e24 kg', 'radius': '6378.1 km', 'satellites': '1'}, 'Venus': {'mass': '4.86900e24 kg', 'radius': '6051.8 km', 'satellites': '0'}, 'Mars': {'mass': '0.64191e24 kg', 'radius': '3397 km', 'satellites': '2'}}\r\n\r\n\r\nIf you find any bug, please report it to hong@topbug.net or submit it on\r\nthe issue tracker:\r\nhttps:\/\/github.com\/xuhdev\/vim-IniParser\/issues\r\n\r\nRepository:\r\nGit on GitHub: https:\/\/github.com\/xuhdev\/vim-IniParser\r\n\r\nFollow xuhdev on twitter if you are interested in my development:\r\nhttp:\/\/twitter.com\/xuhdev","4":"IniParser provides a function for parsing ini files. The following is a short\r\nexample of how to use this function.\r\n\r\nAssuming you have an ini file in the current directory, whose name is\r\n\"planets.ini\" with the following content:\r\n=======================\r\n[Venus]\r\nmass=4.86900e24 kg\r\nradius=6051.8 km\r\nsatellites=0\r\n\r\n[Earth]\r\nmass=5.9742e24 kg\r\nradius=6378.1 km\r\nsatellites=1\r\n\r\n[Mars]\r\nradius=3397 km\r\nmass=0.64191e24 kg\r\nsatellites=2\r\n=======================\r\n\r\nNow we want to know the mass of Mars and the radius of the Earth by vimscript.\r\nFirst we need to parse the file by calling IniParser#Read:\r\n\r\n let ini_result = IniParser#Read('.\/planets.ini')\r\n\r\n\r\nThen the following two lines shows the mass of Mars and the radius of the\r\nEarth respectively:\r\n\r\n echo ini_result['Mars']['mass']\r\n echo ini_result['Earth']['radius']\r\n\r\n\r\nHere's a little explanation:\r\nThe information of the ini file would be stored in the variable \"ini_result\".\r\n\"ini_result\" is a dictionary, whose key names are the group names and whose\r\nvalues are also dictionaries whose key names are entry names and whose values\r\nare the values of the corresponding keys. If you don't understand it, don't\r\nworry, use the following line to show it:\r\n\r\n echo ini_result\r\n\r\n\r\nHere's the result:\r\n\r\n {'Earth': {'mass': '5.9742e24 kg', 'radius': '6378.1 km', 'satellites': '1'}, 'Venus': {'mass': '4.86900e24 kg', 'radius': '6051.8 km', 'satellites': '0'}, 'Mars': {'mass': '0.64191e24 kg', 'radius': '3397 km', 'satellites': '2'}}\r\n\r\n\r\nIf you find any bug, please report it to hong@topbug.net or submit it on\r\nthe issue tracker:\r\nhttps:\/\/github.com\/xuhdev\/vim-IniParser\/issues\r\n\r\nRepository:\r\nGit on GitHub: https:\/\/github.com\/xuhdev\/vim-IniParser\r\n\r\nFollow xuhdev on twitter if you are interested in my development:\r\nhttp:\/\/twitter.com\/xuhdev","install_details":"Download the IniParser.zip file and extract it to your vim runtime\r\ndirectory(~\/.vim on linux and $VIM_INSTALLATION_FOLDER\\vimfiles on windows),\r\nyou'd better then use helptags command to generate the help tag(for example\r\nuse \":helptags ~\/.vim\/doc\" on Linux).","5":"Download the IniParser.zip file and extract it to your vim runtime\r\ndirectory(~\/.vim on linux and $VIM_INSTALLATION_FOLDER\\vimfiles on windows),\r\nyou'd better then use helptags command to generate the help tag(for example\r\nuse \":helptags ~\/.vim\/doc\" on Linux).","first_name":"Hong","6":"Hong","last_name":"Xu","7":"Xu","releases":[{"0":"3434","vim_version":"7.0","1":"7.0","script_version":"0.2.2","2":"0.2.2","version_comment":"Also handle the situation that the right side of '=' is empty.","3":"Also handle the situation that the right side of '=' is empty.","package":"IniParser.zip","4":"IniParser.zip","src_id":"16678","5":"16678","creation_date":"1318730935","6":"1318730935"},{"0":"3434","vim_version":"7.0","1":"7.0","script_version":"0.2.1","2":"0.2.1","version_comment":"Problem is: when whitespace is added before or after the equals sign in an ini file it is added to the property name and value.\r\nNow it is fixed.","3":"Problem is: when whitespace is added before or after the equals sign in an ini file it is added to the property name and value.\r\nNow it is fixed.","package":"IniParser.zip","4":"IniParser.zip","src_id":"16655","5":"16655","creation_date":"1318404881","6":"1318404881"},{"0":"3434","vim_version":"7.0","1":"7.0","script_version":"0..2.1","2":"0..2.1","version_comment":"Problem is: when whitespace is added before or after the equals sign in an ini file it is added to the property name and value.\r\nNow it is fixed.","3":"Problem is: when whitespace is added before or after the equals sign in an ini file it is added to the property name and value.\r\nNow it is fixed.","package":"IniParser.zip","4":"IniParser.zip","src_id":"16654","5":"16654","creation_date":"1318404822","6":"1318404822"},{"0":"3434","vim_version":"7.0","1":"7.0","script_version":"0.2","2":"0.2","version_comment":"Add IniParser#Write function which writes ini file.","3":"Add IniParser#Write function which writes ini file.","package":"IniParser.zip","4":"IniParser.zip","src_id":"15038","5":"15038","creation_date":"1298012846","6":"1298012846"},{"0":"3434","vim_version":"7.0","1":"7.0","script_version":"0.1.1","2":"0.1.1","version_comment":"Makes the return value of IniParse#Read more meaningful;\r\nimprove the document.","3":"Makes the return value of IniParse#Read more meaningful;\r\nimprove the document.","package":"IniParser.zip","4":"IniParser.zip","src_id":"14942","5":"14942","creation_date":"1296667375","6":"1296667375"},{"0":"3434","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"IniParser.zip","4":"IniParser.zip","src_id":"14926","5":"14926","creation_date":"1296481434","6":"1296481434"}]},"3433":{"script_id":"3433","0":"3433","script_name":"Biorhythm ","1":"Biorhythm ","script_type":"utility","2":"utility","summary":"Biorhythm calculator","3":"Biorhythm calculator","description":"Biorhythm is an attempt to predict various aspects(physical, emotional, intellectual, intuitive) of a person's life through simple mathematical cycles. \r\nFor more information, please refer to http:\/\/en.wikipedia.org\/wiki\/Biorhythm.\r\n\r\nMostly for fun, no guarantee to prediction result.\r\n\r\n","4":"Biorhythm is an attempt to predict various aspects(physical, emotional, intellectual, intuitive) of a person's life through simple mathematical cycles. \r\nFor more information, please refer to http:\/\/en.wikipedia.org\/wiki\/Biorhythm.\r\n\r\nMostly for fun, no guarantee to prediction result.\r\n\r\n","install_details":"Edit your birthday in script's s:birthday variable\r\n\r\ncopy the script into $VIM\/vimfiles\/plugin\r\n\r\nUsage:\r\ntype command\r\n:Bio","5":"Edit your birthday in script's s:birthday variable\r\n\r\ncopy the script into $VIM\/vimfiles\/plugin\r\n\r\nUsage:\r\ntype command\r\n:Bio","first_name":"Ran","6":"Ran","last_name":"Bi","7":"Bi","releases":[{"0":"3433","vim_version":"7.0","1":"7.0","script_version":"0.91","2":"0.91","version_comment":"Fix a bug,  now able to handle people born earlier than 1970-1-1","3":"Fix a bug,  now able to handle people born earlier than 1970-1-1","package":"biorhythm.vim","4":"biorhythm.vim","src_id":"14924","5":"14924","creation_date":"1296465828","6":"1296465828"},{"0":"3433","vim_version":"7.0","1":"7.0","script_version":"0.9","2":"0.9","version_comment":"Initial upload","3":"Initial upload","package":"biorhythm.vim","4":"biorhythm.vim","src_id":"14923","5":"14923","creation_date":"1296463485","6":"1296463485"}]},"3432":{"script_id":"3432","0":"3432","script_name":"lazysnipmate","1":"lazysnipmate","script_type":"utility","2":"utility","summary":"patched snipmate","3":"patched snipmate","description":"Hosted at github.com\/garbas\/vim-snipmate now","4":"Hosted at github.com\/garbas\/vim-snipmate now","install_details":"","5":"","first_name":"Marc","6":"Marc","last_name":"Weber","7":"Weber","releases":[{"0":"3432","vim_version":"7.0","1":"7.0","script_version":"0.0","2":"0.0","version_comment":"Initial upload","3":"Initial upload","package":"initial.zip","4":"initial.zip","src_id":"14920","5":"14920","creation_date":"1296441928","6":"1296441928"}]},"3431":{"script_id":"3431","0":"3431","script_name":"AsyncCommand","1":"AsyncCommand","script_type":"utility","2":"utility","summary":"Execute commands and have them send their result to vim when they complete","3":"Execute commands and have them send their result to vim when they complete","description":"AsyncCommand allows you to execute shell commands without waiting for them \r\nto complete. When the application terminates, its output can be loaded into \r\na vim buffer. AsyncCommand is written to be compatible with Windows and \r\nLinux (tested on Win7 and Ubuntu 11.04). \r\n\r\nCurrently three types of commands are supported: \r\n\r\nAsyncShell\r\n    run any program and load results in a split \r\nAsyncGrep\r\n    grep for files and load results in quickfix \r\nAsyncMake\r\n    run make and load results in quickfix\r\nAsyncCscopeFindSymbol, AsyncCscopeFindCalls, AsyncCscopeFindX \r\n    cscope commands\r\n\r\nYou can define your own commands commands by following the same format:\r\nDefine a launch function that passes the external command and result handler\r\n(like asynchandler#quickfix) to asynccommand#run. You can use the handlers in\r\nautoload\/asynchandler.vim or define your own.\r\n\r\nExample: \r\n\r\n    function! AsyncHello(query)\r\n        \" echo hello and the parameter\r\n        let hello_cmd = \"echo hello \".a:query\r\n        \" just load the file when we're done\r\n        let vim_func = asynchandler#split()\r\n    \r\n        \" call our core function to run in the background and then load the\r\n        \" output file on completion\r\n        call asynccommand#run(hello_cmd, vim_func)\r\n    endfunction\r\n\r\nNote that cscope functions require these variables:\r\n  let g:cscope_database = **full path to cscope database file**\r\n  let g:cscope_relative_path = **folder containing cscope database file**\r\nThese variables can be set by tagfilehelpers.vim -- https:\/\/github.com\/pydave\/daveconfig\/blob\/master\/multi\/vim\/.vim\/plugin\/tagfilehelpers.vim\r\n\r\n\r\nPlease report bugs to https:\/\/github.com\/pydave\/AsyncCommand\/issues","4":"AsyncCommand allows you to execute shell commands without waiting for them \r\nto complete. When the application terminates, its output can be loaded into \r\na vim buffer. AsyncCommand is written to be compatible with Windows and \r\nLinux (tested on Win7 and Ubuntu 11.04). \r\n\r\nCurrently three types of commands are supported: \r\n\r\nAsyncShell\r\n    run any program and load results in a split \r\nAsyncGrep\r\n    grep for files and load results in quickfix \r\nAsyncMake\r\n    run make and load results in quickfix\r\nAsyncCscopeFindSymbol, AsyncCscopeFindCalls, AsyncCscopeFindX \r\n    cscope commands\r\n\r\nYou can define your own commands commands by following the same format:\r\nDefine a launch function that passes the external command and result handler\r\n(like asynchandler#quickfix) to asynccommand#run. You can use the handlers in\r\nautoload\/asynchandler.vim or define your own.\r\n\r\nExample: \r\n\r\n    function! AsyncHello(query)\r\n        \" echo hello and the parameter\r\n        let hello_cmd = \"echo hello \".a:query\r\n        \" just load the file when we're done\r\n        let vim_func = asynchandler#split()\r\n    \r\n        \" call our core function to run in the background and then load the\r\n        \" output file on completion\r\n        call asynccommand#run(hello_cmd, vim_func)\r\n    endfunction\r\n\r\nNote that cscope functions require these variables:\r\n  let g:cscope_database = **full path to cscope database file**\r\n  let g:cscope_relative_path = **folder containing cscope database file**\r\nThese variables can be set by tagfilehelpers.vim -- https:\/\/github.com\/pydave\/daveconfig\/blob\/master\/multi\/vim\/.vim\/plugin\/tagfilehelpers.vim\r\n\r\n\r\nPlease report bugs to https:\/\/github.com\/pydave\/AsyncCommand\/issues","install_details":"Unzip to ~\/.vim\/ or to ~\/.vim\/bundle\/asynccommand\/ for use with pathogen (vimscript #2332).","5":"Unzip to ~\/.vim\/ or to ~\/.vim\/bundle\/asynccommand\/ for use with pathogen (vimscript #2332).","first_name":"David","6":"David","last_name":"Briscoe","7":"Briscoe","releases":[{"0":"3431","vim_version":"7.0","1":"7.0","script_version":"4.0","2":"4.0","version_comment":"Fix some issues with console vim. Pass return code to handlers. Capture all output from commands. Add more error checking.\r\nThanks to patch contributors v.yurin and Dan Wanek.","3":"Fix some issues with console vim. Pass return code to handlers. Capture all output from commands. Add more error checking.\r\nThanks to patch contributors v.yurin and Dan Wanek.","package":"AsyncCommand.zip","4":"AsyncCommand.zip","src_id":"17998","5":"17998","creation_date":"1337471906","6":"1337471906"},{"0":"3431","vim_version":"7.0","1":"7.0","script_version":"3.1","2":"3.1","version_comment":"Re-add AsyncMake command","3":"Re-add AsyncMake command","package":"asynccommand.zip","4":"asynccommand.zip","src_id":"16068","5":"16068","creation_date":"1310419213","6":"1310419213"},{"0":"3431","vim_version":"7.0","1":"7.0","script_version":"3.0","2":"3.0","version_comment":"Now a zip file.\r\n\r\nConvert to an autoload script, add help file (big thanks to Peter Rincker!)\r\nThere are also now more predefined handlers to simplify writing your own AsyncCommands.\r\n\r\nFix tcsh shellredir bug (thanks to Chad Moore!)","3":"Now a zip file.\r\n\r\nConvert to an autoload script, add help file (big thanks to Peter Rincker!)\r\nThere are also now more predefined handlers to simplify writing your own AsyncCommands.\r\n\r\nFix tcsh shellredir bug (thanks to Chad Moore!)","package":"asynccommand.zip","4":"asynccommand.zip","src_id":"15910","5":"15910","creation_date":"1308270591","6":"1308270591"},{"0":"3431","vim_version":"7.0","1":"7.0","script_version":"2.2","2":"2.2","version_comment":"Fix terminal vim problem. Add error handling for when v:servername is not set. (Thanks to dfroger!)","3":"Fix terminal vim problem. Add error handling for when v:servername is not set. (Thanks to dfroger!)","package":"asynccommand.vim","4":"asynccommand.vim","src_id":"15391","5":"15391","creation_date":"1302037694","6":"1302037694"},{"0":"3431","vim_version":"7.0","1":"7.0","script_version":"2.1","2":"2.1","version_comment":"Missing braces on linux version of Async_Impl. Braces are required to make command asynchronous.\r\nAdd error checking for AsyncGrep.\r\n","3":"Missing braces on linux version of Async_Impl. Braces are required to make command asynchronous.\r\nAdd error checking for AsyncGrep.\r\n","package":"asynccommand.vim","4":"asynccommand.vim","src_id":"15127","5":"15127","creation_date":"1298770990","6":"1298770990"},{"0":"3431","vim_version":"7.0","1":"7.0","script_version":"2.0","2":"2.0","version_comment":"Add AsyncMake to run make asynchronously and open results in an error window.","3":"Add AsyncMake to run make asynchronously and open results in an error window.","package":"asynccommand.vim","4":"asynccommand.vim","src_id":"15102","5":"15102","creation_date":"1298483382","6":"1298483382"},{"0":"3431","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"asynccommand.vim","4":"asynccommand.vim","src_id":"14916","5":"14916","creation_date":"1296413758","6":"1296413758"}]},"3430":{"script_id":"3430","0":"3430","script_name":"pep8","1":"pep8","script_type":"ftplugin","2":"ftplugin","summary":"A Python filetype plugin to check pep8 convention.","3":"A Python filetype plugin to check pep8 convention.","description":"Before use, please make sure below.\r\n\r\n- vim is compiled with python.\r\n- put pep8 somewhere to be visible from this.\r\n\r\nURL: http:\/\/github.com\/jbking\/vim-pep8\r\n\r\nThanks to pyflakes.vim (http:\/\/www.vim.org\/scripts\/script.php?script_id=2441). Almost inspired from you.","4":"Before use, please make sure below.\r\n\r\n- vim is compiled with python.\r\n- put pep8 somewhere to be visible from this.\r\n\r\nURL: http:\/\/github.com\/jbking\/vim-pep8\r\n\r\nThanks to pyflakes.vim (http:\/\/www.vim.org\/scripts\/script.php?script_id=2441). Almost inspired from you.","install_details":"1. Put this plug-in into your plug-in directory.","5":"1. Put this plug-in into your plug-in directory.","first_name":"MURAOKA","6":"MURAOKA","last_name":"Yusuke","7":"Yusuke","releases":[{"0":"3430","vim_version":"7.0","1":"7.0","script_version":"0.5","2":"0.5","version_comment":"Code clarify and some bug fixes and features.","3":"Code clarify and some bug fixes and features.","package":"pep8.zip","4":"pep8.zip","src_id":"16620","5":"16620","creation_date":"1317746992","6":"1317746992"},{"0":"3430","vim_version":"7.0","1":"7.0","script_version":"0.4.1","2":"0.4.1","version_comment":"ignore occurring errors by empty line","3":"ignore occurring errors by empty line","package":"pep8.zip","4":"pep8.zip","src_id":"15293","5":"15293","creation_date":"1301120741","6":"1301120741"},{"0":"3430","vim_version":"7.0","1":"7.0","script_version":"0.4","2":"0.4","version_comment":"- Fix newlines in pep8 returns causing status message to not display.\r\n- Ignore stderr of pep8 output.","3":"- Fix newlines in pep8 returns causing status message to not display.\r\n- Ignore stderr of pep8 output.","package":"pep8.zip","4":"pep8.zip","src_id":"15287","5":"15287","creation_date":"1301023345","6":"1301023345"},{"0":"3430","vim_version":"7.0","1":"7.0","script_version":"0.3","2":"0.3","version_comment":"- Caching pep8 report. So, checking at unchanged must be fast finished. Thanks to OrderedDict.\r\n- Share a checker instance over buffers.\r\n- Simplify code...","3":"- Caching pep8 report. So, checking at unchanged must be fast finished. Thanks to OrderedDict.\r\n- Share a checker instance over buffers.\r\n- Simplify code...","package":"pep8.zip","4":"pep8.zip","src_id":"14941","5":"14941","creation_date":"1296665710","6":"1296665710"},{"0":"3430","vim_version":"7.0","1":"7.0","script_version":"0.2","2":"0.2","version_comment":"Fixed a bug related to display pep8 error message.\r\nSplit python code of this plug-in into a module from vim-script.","3":"Fixed a bug related to display pep8 error message.\r\nSplit python code of this plug-in into a module from vim-script.","package":"pep8.zip","4":"pep8.zip","src_id":"14929","5":"14929","creation_date":"1296505466","6":"1296505466"},{"0":"3430","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"pep8.vim","4":"pep8.vim","src_id":"14915","5":"14915","creation_date":"1296411020","6":"1296411020"}]},"3429":{"script_id":"3429","0":"3429","script_name":"vim-addon-sml","1":"vim-addon-sml","script_type":"utility","2":"utility","summary":"my sml support for Vim","3":"my sml support for Vim","description":"See http:\/\/github.com\/MarcWeber\/vim-addon-sml","4":"See http:\/\/github.com\/MarcWeber\/vim-addon-sml","install_details":"I recommend using vim-addon-manager because it depends on some other plugins. See *info* file","5":"I recommend using vim-addon-manager because it depends on some other plugins. See *info* file","first_name":"Marc","6":"Marc","last_name":"Weber","7":"Weber","releases":[{"0":"3429","vim_version":"7.0","1":"7.0","script_version":"0.0","2":"0.0","version_comment":"Initial upload","3":"Initial upload","package":"initial.zip","4":"initial.zip","src_id":"14913","5":"14913","creation_date":"1296354636","6":"1296354636"}]},"3428":{"script_id":"3428","0":"3428","script_name":"obsidian2.vim","1":"obsidian2.vim","script_type":"color scheme","2":"color scheme","summary":"Obsidian2 Color scheme based on Notepad++ obsidian Color scheme","3":"Obsidian2 Color scheme based on Notepad++ obsidian Color scheme","description":"github: https:\/\/github.com\/abra\/obsidian2\r\nScreenshot: http:\/\/ubuntuone.com\/p\/cwB\/","4":"github: https:\/\/github.com\/abra\/obsidian2\r\nScreenshot: http:\/\/ubuntuone.com\/p\/cwB\/","install_details":"Just copy obsidian2.vim to ~\/.vim\/colors and then type in vim editor :colorscheme obsidian2\r\n\r\n","5":"Just copy obsidian2.vim to ~\/.vim\/colors and then type in vim editor :colorscheme obsidian2\r\n\r\n","first_name":"Aydar","6":"Aydar","last_name":"Khabibullin","7":"Khabibullin","releases":[{"0":"3428","vim_version":"7.0","1":"7.0","script_version":"0.5","2":"0.5","version_comment":"Initial upload","3":"Initial upload","package":"obsidian2.vim","4":"obsidian2.vim","src_id":"14906","5":"14906","creation_date":"1296333662","6":"1296333662"}]},"3427":{"script_id":"3427","0":"3427","script_name":"Nazca","1":"Nazca","script_type":"color scheme","2":"color scheme","summary":"For Web Development - Support for 256 color","3":"For Web Development - Support for 256 color","description":"This is Nazca and it is based in ir_black and Sunburst for Textmate.\r\nFor more info about Nazca, Peru http:\/\/en.wikipedia.org\/wiki\/Nazca\r\n\r\nI've tweaked this colorscheme for Web Development, so it works nice with Javascript, X(HTML)5, Ruby and CSS\r\nAny other filetypes should look nice as well.\r\n\r\nFor uniform appearance, I've tested it in graphical Vim full color (gvim and macvim) and also 256 color iTerm2.app in Mac OSX and the gnome terminal in Linux.\r\nHere are some screenshots: http:\/\/picasaweb.google.com\/jelera\/NazcaColorschemeForVim?feat=directlink\r\n\r\nIf you wish to fork it or report any issues, please refer to\r\nhttps:\/\/github.com\/jelera\/vim-nazca-colorscheme\r\n\r\nPlease feel free to modified  to suit your own needs.\r\n","4":"This is Nazca and it is based in ir_black and Sunburst for Textmate.\r\nFor more info about Nazca, Peru http:\/\/en.wikipedia.org\/wiki\/Nazca\r\n\r\nI've tweaked this colorscheme for Web Development, so it works nice with Javascript, X(HTML)5, Ruby and CSS\r\nAny other filetypes should look nice as well.\r\n\r\nFor uniform appearance, I've tested it in graphical Vim full color (gvim and macvim) and also 256 color iTerm2.app in Mac OSX and the gnome terminal in Linux.\r\nHere are some screenshots: http:\/\/picasaweb.google.com\/jelera\/NazcaColorschemeForVim?feat=directlink\r\n\r\nIf you wish to fork it or report any issues, please refer to\r\nhttps:\/\/github.com\/jelera\/vim-nazca-colorscheme\r\n\r\nPlease feel free to modified  to suit your own needs.\r\n","install_details":"Copy this file inside the \"colors\" folder in your VIMFILES\r\n~\/.vim\/colors\r\n\r\nPathogen\/Vundle users:\r\ngit clone https:\/\/github.com\/jelera\/vim-nazca-colorscheme ~\/.vim\/bundle","5":"Copy this file inside the \"colors\" folder in your VIMFILES\r\n~\/.vim\/colors\r\n\r\nPathogen\/Vundle users:\r\ngit clone https:\/\/github.com\/jelera\/vim-nazca-colorscheme ~\/.vim\/bundle","first_name":"Jose","6":"Jose","last_name":"Elera","7":"Elera","releases":[{"0":"3427","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"nazca.vim","4":"nazca.vim","src_id":"14902","5":"14902","creation_date":"1296295432","6":"1296295432"}]},"3426":{"script_id":"3426","0":"3426","script_name":"LispXp","1":"LispXp","script_type":"utility","2":"utility","summary":"Lisp snippets for xptemplate","3":"Lisp snippets for xptemplate","description":"These are some Common Lisp snippets for xptemplate.\r\n\r\nScreenshot of various snippets with placeholders activated (before most\r\nof the placeholders have been filled in):\r\n\r\n  http:\/\/img703.imageshack.us\/img703\/7780\/screenshot10x.png\r\n\r\nOf course, as usual, you can use your own colors and colorscheme.\r\n\r\nNOTE:\r\n\r\n  As of version 1.10, LispXp requires the newest version of xptemplate\r\n  from SVN or git.\r\n\r\nKnown issues:\r\n\r\n  Due to the limitations of the current version of xptemplate, I've had to use\r\n  the name \"dostar\" instead of \"do*\", \"letstar\" instead of \"let*\", etc.  Also,\r\n  the indentation of certain complex snippets like \"defstruct\" is not correct.\r\n\r\nNOTE:\r\n\r\n  I'm new to Lisp, and new to xptemplate, so don't expect the most\r\n  sophisticated snippets, a religious adherence to the Hyperspec, or even a\r\n  full set of snippets for every function and macro documented in the\r\n  Hyperspec.\r\n\r\n  These snippets are really mostly just for my own use, but if someone else\r\n  finds them useful, then that's great.\r\n\r\nAs of version 1.10, these are the snippets that are included:\r\n\r\n+                describe        mapc            readbase\r\n-                divide          mapcan          remf\r\n*                do              mapcar          remhash\r\n\/                documentation   mapcon          remove\r\n=                dolist          maphash         remove-if\r\n\/=               dostar          mapl            remove-if-not\r\n<                dotimes         maplist         remprop\r\n<=               eighth          member          rest\r\n>                elt             minus           return\r\n>=               endp            multiply        reverse\r\nabs              eq              nconc           rplaca\r\nacons            eql             nintersection   rplacd\r\nand              equal           ninth           second\r\nappend           eval            not             set\r\napply            fboundp         nreverse        setf\r\naref             fifth           nsublis         setq\r\narray-total-size finish-output   nsubst          seventh\r\nash              first           nth             sixth\r\nassoc            force-output    nthcdr          stringp\r\natom             format          null            sublis\r\nboundp           fourth          numberp         subst\r\nbyte             fresh-line      open            symbolfunction\r\nbyte-position    funcall         or              symbolp\r\nbyte-size        functionp       pairlis         symbolvalue\r\ncar              get             plus            tenth\r\ncdr              getf            pop             terpri\r\nclear-output     gethash         prin1           third\r\ncond             if              prin1-to-string typep\r\ncons             intersection    princ           union\r\nconsp            lambda          princ-to-string vector\r\ncopy-alist       last            print           vector-pop\r\ncopy-list        ldb             printbase       vector-push\r\ncopy-tree        length          printlength     when\r\ndefconstant      let             printlevel      write\r\ndefmacro         letstar         progn           write-byte\r\ndefparameter     list            push            write-char\r\ndefstruct        listp           pushnew         write-line\r\ndefun            liststar        quote           write-sequence\r\ndefvar           load            rassoc          write-string\r\ndelete           macroexpand     rassoc-if       write-to-string\r\ndelete-if        make-array      rassoc-if-not   zerop\r\ndelete-if-not    make-hash-table read\r\n\r\nFor more information on this script follow the vim wiki link at the top right of this page.\r\n\r\nFor more information on xptemplate, see:\r\n\r\nhttp:\/\/www.vim.org\/scripts\/script.php?script_id=2611\r\n\r\n","4":"These are some Common Lisp snippets for xptemplate.\r\n\r\nScreenshot of various snippets with placeholders activated (before most\r\nof the placeholders have been filled in):\r\n\r\n  http:\/\/img703.imageshack.us\/img703\/7780\/screenshot10x.png\r\n\r\nOf course, as usual, you can use your own colors and colorscheme.\r\n\r\nNOTE:\r\n\r\n  As of version 1.10, LispXp requires the newest version of xptemplate\r\n  from SVN or git.\r\n\r\nKnown issues:\r\n\r\n  Due to the limitations of the current version of xptemplate, I've had to use\r\n  the name \"dostar\" instead of \"do*\", \"letstar\" instead of \"let*\", etc.  Also,\r\n  the indentation of certain complex snippets like \"defstruct\" is not correct.\r\n\r\nNOTE:\r\n\r\n  I'm new to Lisp, and new to xptemplate, so don't expect the most\r\n  sophisticated snippets, a religious adherence to the Hyperspec, or even a\r\n  full set of snippets for every function and macro documented in the\r\n  Hyperspec.\r\n\r\n  These snippets are really mostly just for my own use, but if someone else\r\n  finds them useful, then that's great.\r\n\r\nAs of version 1.10, these are the snippets that are included:\r\n\r\n+                describe        mapc            readbase\r\n-                divide          mapcan          remf\r\n*                do              mapcar          remhash\r\n\/                documentation   mapcon          remove\r\n=                dolist          maphash         remove-if\r\n\/=               dostar          mapl            remove-if-not\r\n<                dotimes         maplist         remprop\r\n<=               eighth          member          rest\r\n>                elt             minus           return\r\n>=               endp            multiply        reverse\r\nabs              eq              nconc           rplaca\r\nacons            eql             nintersection   rplacd\r\nand              equal           ninth           second\r\nappend           eval            not             set\r\napply            fboundp         nreverse        setf\r\naref             fifth           nsublis         setq\r\narray-total-size finish-output   nsubst          seventh\r\nash              first           nth             sixth\r\nassoc            force-output    nthcdr          stringp\r\natom             format          null            sublis\r\nboundp           fourth          numberp         subst\r\nbyte             fresh-line      open            symbolfunction\r\nbyte-position    funcall         or              symbolp\r\nbyte-size        functionp       pairlis         symbolvalue\r\ncar              get             plus            tenth\r\ncdr              getf            pop             terpri\r\nclear-output     gethash         prin1           third\r\ncond             if              prin1-to-string typep\r\ncons             intersection    princ           union\r\nconsp            lambda          princ-to-string vector\r\ncopy-alist       last            print           vector-pop\r\ncopy-list        ldb             printbase       vector-push\r\ncopy-tree        length          printlength     when\r\ndefconstant      let             printlevel      write\r\ndefmacro         letstar         progn           write-byte\r\ndefparameter     list            push            write-char\r\ndefstruct        listp           pushnew         write-line\r\ndefun            liststar        quote           write-sequence\r\ndefvar           load            rassoc          write-string\r\ndelete           macroexpand     rassoc-if       write-to-string\r\ndelete-if        make-array      rassoc-if-not   zerop\r\ndelete-if-not    make-hash-table read\r\n\r\nFor more information on this script follow the vim wiki link at the top right of this page.\r\n\r\nFor more information on xptemplate, see:\r\n\r\nhttp:\/\/www.vim.org\/scripts\/script.php?script_id=2611\r\n\r\n","install_details":"To install these snippets:\r\n\r\n - get xptemplate from SVN or git (important!  xptemplate from vim.org will **not** work!)\r\n - install and configure xptemplate\r\n - download these snippets\r\n - rename the downloaded snippet file as \"lisp.xpt.vim\"\r\n - move it in to the ftplugin\/lisp directory under the path you've chosen according to\r\n      :help xpt-personal-folder\r\n - quit and restart vim\r\n","5":"To install these snippets:\r\n\r\n - get xptemplate from SVN or git (important!  xptemplate from vim.org will **not** work!)\r\n - install and configure xptemplate\r\n - download these snippets\r\n - rename the downloaded snippet file as \"lisp.xpt.vim\"\r\n - move it in to the ftplugin\/lisp directory under the path you've chosen according to\r\n      :help xpt-personal-folder\r\n - quit and restart vim\r\n","first_name":"Gnosis","6":"Gnosis","last_name":"Ouroubouros","7":"Ouroubouros","releases":[{"0":"3426","vim_version":"7.3","1":"7.3","script_version":"1.10","2":"1.10","version_comment":"Note: This version of LispXp requires the newest version of xptemplate from SVN or git.  New snippets: ash, byte, byte-position, byte-size, defstruct, dostar, ldb, maphash, prin1-to-string, princ-to-string, write, write-byte, write-char, write-line, write-sequence, write-string, write-to-string.","3":"Note: This version of LispXp requires the newest version of xptemplate from SVN or git.  New snippets: ash, byte, byte-position, byte-size, defstruct, dostar, ldb, maphash, prin1-to-string, princ-to-string, write, write-byte, write-char, write-line, write-sequence, write-string, write-to-string.","package":"lisp.xpt-1.10.vim","4":"lisp.xpt-1.10.vim","src_id":"15033","5":"15033","creation_date":"1297959528","6":"1297959528"},{"0":"3426","vim_version":"7.3","1":"7.3","script_version":"1.9","2":"1.9","version_comment":"Many new snippets, along with a few improvements and bug fixes.","3":"Many new snippets, along with a few improvements and bug fixes.","package":"lisp.xpt-1.9.vim","4":"lisp.xpt-1.9.vim","src_id":"15003","5":"15003","creation_date":"1297705933","6":"1297705933"},{"0":"3426","vim_version":"7.3","1":"7.3","script_version":"1.8","2":"1.8","version_comment":"Added new snippets: \"aref\", \"get\", \"listp\", \"remprop\".","3":"Added new snippets: \"aref\", \"get\", \"listp\", \"remprop\".","package":"lisp.xpt-1.8.vim","4":"lisp.xpt-1.8.vim","src_id":"14955","5":"14955","creation_date":"1296851912","6":"1296851912"},{"0":"3426","vim_version":"7.3","1":"7.3","script_version":"1.7","2":"1.7","version_comment":"Added new snippets: \"endp\", \"setf\", \"when\".  Now all the basic arithmetic function snippets (+,-,\/,*) have a minimum of two number place holders.","3":"Added new snippets: \"endp\", \"setf\", \"when\".  Now all the basic arithmetic function snippets (+,-,\/,*) have a minimum of two number place holders.","package":"lisp.xpt-1.7.vim","4":"lisp.xpt-1.7.vim","src_id":"14928","5":"14928","creation_date":"1296502426","6":"1296502426"},{"0":"3426","vim_version":"7.3","1":"7.3","script_version":"1.6","2":"1.6","version_comment":"Fixed buggy \"cond\" snippet.  Made \"let\" and \"letstar\" a bit more readable.  Added new snippets: \"clear-output\", \"finish-output\", \"force-output\", and \"return\".","3":"Fixed buggy \"cond\" snippet.  Made \"let\" and \"letstar\" a bit more readable.  Added new snippets: \"clear-output\", \"finish-output\", \"force-output\", and \"return\".","package":"lisp.xpt-1.6.vim","4":"lisp.xpt-1.6.vim","src_id":"14919","5":"14919","creation_date":"1296425559","6":"1296425559"},{"0":"3426","vim_version":"7.3","1":"7.3","script_version":"1.5","2":"1.5","version_comment":"Improved readability of a placeholder in the \"setq\" snippet, and added the following snippets:  \"=\", \"\/=\", \"<\", \"<=\", \">\", \">=\".","3":"Improved readability of a placeholder in the \"setq\" snippet, and added the following snippets:  \"=\", \"\/=\", \"<\", \"<=\", \">\", \">=\".","package":"lisp.xpt-1.5.vim","4":"lisp.xpt-1.5.vim","src_id":"14912","5":"14912","creation_date":"1296353710","6":"1296353710"},{"0":"3426","vim_version":"7.3","1":"7.3","script_version":"1.4","2":"1.4","version_comment":"Added new snippets (\"dolist\" and \"dotimes\").  Fixed bugs in \"eq\", \"eql\", and \"equal\" snippets.  Removed parenthesis around the test in the \"if\" snippet.","3":"Added new snippets (\"dolist\" and \"dotimes\").  Fixed bugs in \"eq\", \"eql\", and \"equal\" snippets.  Removed parenthesis around the test in the \"if\" snippet.","package":"lisp.xpt-1.4.vim","4":"lisp.xpt-1.4.vim","src_id":"14911","5":"14911","creation_date":"1296351333","6":"1296351333"},{"0":"3426","vim_version":"7.3","1":"7.3","script_version":"1.3","2":"1.3","version_comment":"Corrected spacing when \"stepper\" placeholder is skipped in the \"do\" snippet.","3":"Corrected spacing when \"stepper\" placeholder is skipped in the \"do\" snippet.","package":"lisp.xpt-1.3.vim","4":"lisp.xpt-1.3.vim","src_id":"14910","5":"14910","creation_date":"1296344093","6":"1296344093"},{"0":"3426","vim_version":"7.3","1":"7.3","script_version":"1.2","2":"1.2","version_comment":"Took out parenthesis from around the bodies of defmacro, defun, and lambda, since you're likely to use snippets there and they already have parenthesis around them.","3":"Took out parenthesis from around the bodies of defmacro, defun, and lambda, since you're likely to use snippets there and they already have parenthesis around them.","package":"lisp.xpt-1.2.vim","4":"lisp.xpt-1.2.vim","src_id":"14909","5":"14909","creation_date":"1296342430","6":"1296342430"},{"0":"3426","vim_version":"7.3","1":"7.3","script_version":"1.1","2":"1.1","version_comment":"Improved the \"do\" snippet to make it handle skipped placeholders more gracefully.","3":"Improved the \"do\" snippet to make it handle skipped placeholders more gracefully.","package":"lisp.xpt-1.1.vim","4":"lisp.xpt-1.1.vim","src_id":"14905","5":"14905","creation_date":"1296326496","6":"1296326496"},{"0":"3426","vim_version":"7.3","1":"7.3","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"lisp.xpt-1.0.vim","4":"lisp.xpt-1.0.vim","src_id":"14900","5":"14900","creation_date":"1296275757","6":"1296275757"}]},"3425":{"script_id":"3425","0":"3425","script_name":"Enhanced Javascript syntax","1":"Enhanced Javascript syntax","script_type":"syntax","2":"syntax","summary":"Improved Highlight for Ajax, DOM and Browser Objects, Methods and Properties","3":"Improved Highlight for Ajax, DOM and Browser Objects, Methods and Properties","description":"This file is a fork of this vimscript#1491 and the stock vim javascript syntax file.\r\n\r\nThis version of this file features the following text highlights:\r\nParenthesis, curly and regular brackets.\r\nThe semicolon or comma at the end of line.\r\nBrowser, DOM and \"Ajax\" keywords like objects, methods, properties and others.\r\nOperation, comparison and logical symbols (=,==,===,!=,etc.).\r\n\r\nScreenshots:\r\nhttp:\/\/imgur.com\/a\/sn8fz\r\n\r\nFollow all the changes, also to contribute or report bugs.\r\n\r\nhttps:\/\/github.com\/jelera\/vim-javascript-syntax","4":"This file is a fork of this vimscript#1491 and the stock vim javascript syntax file.\r\n\r\nThis version of this file features the following text highlights:\r\nParenthesis, curly and regular brackets.\r\nThe semicolon or comma at the end of line.\r\nBrowser, DOM and \"Ajax\" keywords like objects, methods, properties and others.\r\nOperation, comparison and logical symbols (=,==,===,!=,etc.).\r\n\r\nScreenshots:\r\nhttp:\/\/imgur.com\/a\/sn8fz\r\n\r\nFollow all the changes, also to contribute or report bugs.\r\n\r\nhttps:\/\/github.com\/jelera\/vim-javascript-syntax","install_details":"just copy this file in your ~\/.vim\/syntax\r\n\r\nFor NeoBundle (Recommended method)\r\nNeoBundleLazy 'jelera\/vim-javascript-syntax', {'autoload':{'filetypes':['javascript']}}\r\n\r\n\r\nFor Pathogen\/Vundle users\r\ngit clone https:\/\/github.com\/jelera\/vim-javascript-syntax ~\/.vim\/bundle","5":"just copy this file in your ~\/.vim\/syntax\r\n\r\nFor NeoBundle (Recommended method)\r\nNeoBundleLazy 'jelera\/vim-javascript-syntax', {'autoload':{'filetypes':['javascript']}}\r\n\r\n\r\nFor Pathogen\/Vundle users\r\ngit clone https:\/\/github.com\/jelera\/vim-javascript-syntax ~\/.vim\/bundle","first_name":"Jose","6":"Jose","last_name":"Elera","7":"Elera","releases":[{"0":"3425","vim_version":"7.0","1":"7.0","script_version":"0.8.2","2":"0.8.2","version_comment":"Many bugfixes and new features added, see more at the github page","3":"Many bugfixes and new features added, see more at the github page","package":"vim-javascript-syntax-0.8.2.zip","4":"vim-javascript-syntax-0.8.2.zip","src_id":"24038","5":"24038","creation_date":"1456307533","6":"1456307533"},{"0":"3425","vim_version":"7.0","1":"7.0","script_version":"0.8.0","2":"0.8.0","version_comment":"Major cleanup, added keywords, tweaked highlighting","3":"Major cleanup, added keywords, tweaked highlighting","package":"javascript.vim","4":"javascript.vim","src_id":"20817","5":"20817","creation_date":"1379480254","6":"1379480254"},{"0":"3425","vim_version":"7.0","1":"7.0","script_version":"0.6","2":"0.6","version_comment":"ADDED:\r\n- Support for folding\r\nMODIFIED:\r\n- Most of the code is folded for easier navigation and readability\r\n- Highlight is \"more\" uniform","3":"ADDED:\r\n- Support for folding\r\nMODIFIED:\r\n- Most of the code is folded for easier navigation and readability\r\n- Highlight is \"more\" uniform","package":"javascript.vim","4":"javascript.vim","src_id":"17518","5":"17518","creation_date":"1330024794","6":"1330024794"},{"0":"3425","vim_version":"7.0","1":"7.0","script_version":"0.5","2":"0.5","version_comment":"Now it highlights parens, brackets. Symbols like =,==,===,!=,<,> ... etc. Added more keywords. The semicolon or comma at the EOL is highlighted too.","3":"Now it highlights parens, brackets. Symbols like =,==,===,!=,<,> ... etc. Added more keywords. The semicolon or comma at the EOL is highlighted too.","package":"javascript.vim","4":"javascript.vim","src_id":"17408","5":"17408","creation_date":"1328676039","6":"1328676039"},{"0":"3425","vim_version":"7.0","1":"7.0","script_version":"0.4","2":"0.4","version_comment":"In this release, \"customization of colorscheme\" is no longer required. All the new highlights introduced with this syntax have HiLinks with preset keywords. Tested with several colorschemes.","3":"In this release, \"customization of colorscheme\" is no longer required. All the new highlights introduced with this syntax have HiLinks with preset keywords. Tested with several colorschemes.","package":"javascript.vim","4":"javascript.vim","src_id":"17395","5":"17395","creation_date":"1328477902","6":"1328477902"}]},"3424":{"script_id":"3424","0":"3424","script_name":"pytest.vim","1":"pytest.vim","script_type":"utility","2":"utility","summary":"Runs your (Python) tests with py.test displaying red\/green bars","3":"Runs your (Python) tests with py.test displaying red\/green bars","description":"A simple way of running your tests (with py.test) from within VIM.\r\n\r\nTalking with Holger Krekel (original author of py.test and vim user) we thought\r\nit would be neat to be able to call it from vim and get some immediate results.\r\n\r\nThis is especially useful when you are tweaking and do not want to be moving\r\naround between the terminal and your vim session.\r\n\r\nScreencast: http:\/\/vimeo.com\/19774046\r\n\r\n\r\nScreenshots: \r\n\r\nFailing Tests \r\nhttp:\/\/www.flickr.com\/photos\/aldegaz\/5414279071 \r\n\r\nPassing Tests \r\nhttp:\/\/www.flickr.com\/photos\/aldegaz\/5395135539 \r\n\r\nVerbose Mode \r\nhttp:\/\/www.flickr.com\/photos\/aldegaz\/5414279043 \r\n\r\n\r\nFor the latest documentation and project info go to\r\nthe project home:\r\n https:\/\/github.com\/alfredodeza\/pytest.vim","4":"A simple way of running your tests (with py.test) from within VIM.\r\n\r\nTalking with Holger Krekel (original author of py.test and vim user) we thought\r\nit would be neat to be able to call it from vim and get some immediate results.\r\n\r\nThis is especially useful when you are tweaking and do not want to be moving\r\naround between the terminal and your vim session.\r\n\r\nScreencast: http:\/\/vimeo.com\/19774046\r\n\r\n\r\nScreenshots: \r\n\r\nFailing Tests \r\nhttp:\/\/www.flickr.com\/photos\/aldegaz\/5414279071 \r\n\r\nPassing Tests \r\nhttp:\/\/www.flickr.com\/photos\/aldegaz\/5395135539 \r\n\r\nVerbose Mode \r\nhttp:\/\/www.flickr.com\/photos\/aldegaz\/5414279043 \r\n\r\n\r\nFor the latest documentation and project info go to\r\nthe project home:\r\n https:\/\/github.com\/alfredodeza\/pytest.vim","install_details":"Either drop the plugin\/pytest.vim file into your plugin directory or use Pathogen and drop the whole packaged directory in your bundle dir. ","5":"Either drop the plugin\/pytest.vim file into your plugin directory or use Pathogen and drop the whole packaged directory in your bundle dir. ","first_name":"Alfredo","6":"Alfredo","last_name":"Deza","7":"Deza","releases":[{"0":"3424","vim_version":"7.0","1":"7.0","script_version":"1.1.4","2":"1.1.4","version_comment":"* better output when tests are passing (inside the green bar).\r\n* improved handling of py.test errors\r\n* fixes a small looponfail problem where an autocommand would stick for other buffers\r\n* jump to previous window when a test is run is more robust\r\n* better error output (whole AssertionErrror line) when going through errors","3":"* better output when tests are passing (inside the green bar).\r\n* improved handling of py.test errors\r\n* fixes a small looponfail problem where an autocommand would stick for other buffers\r\n* jump to previous window when a test is run is more robust\r\n* better error output (whole AssertionErrror line) when going through errors","package":"pytest.tar.gz","4":"pytest.tar.gz","src_id":"18178","5":"18178","creation_date":"1340363294","6":"1340363294"},{"0":"3424","vim_version":"7.3","1":"7.3","script_version":"1.1.1","2":"1.1.1","version_comment":"Bug fixes with autocommands and better awareness of nested Python objects.","3":"Bug fixes with autocommands and better awareness of nested Python objects.","package":"pytest.tar.gz","4":"pytest.tar.gz","src_id":"17700","5":"17700","creation_date":"1333324516","6":"1333324516"},{"0":"3424","vim_version":"7.0","1":"7.0","script_version":"1.0.0","2":"1.0.0","version_comment":"* Mayor release for plugin with important internal updates.\r\n* Adds `looponfail` for test, methods or classes\r\n* Adds `clear` command to clear a looponfail call\r\n* Add support for function tests\r\n* Better information when there is a py.test error or INTERNALERROR\r\n* Add carrousel for moving around in the failed\/error buffer list","3":"* Mayor release for plugin with important internal updates.\r\n* Adds `looponfail` for test, methods or classes\r\n* Adds `clear` command to clear a looponfail call\r\n* Add support for function tests\r\n* Better information when there is a py.test error or INTERNALERROR\r\n* Add carrousel for moving around in the failed\/error buffer list","package":"pytest.tar.gz","4":"pytest.tar.gz","src_id":"16094","5":"16094","creation_date":"1311034470","6":"1311034470"},{"0":"3424","vim_version":"7.0","1":"7.0","script_version":"0.6.1","2":"0.6.1","version_comment":"Adds support to use Conque.vim (better shell experience) if it is installed. Drops back to normal dumb terminal if it doesn\\'t.\r\nThis changes the behavior for all pdb flags and the verbose mode.","3":"Adds support to use Conque.vim (better shell experience) if it is installed. Drops back to normal dumb terminal if it doesn\\'t.\r\nThis changes the behavior for all pdb flags and the verbose mode.","package":"pytest.tar.gz","4":"pytest.tar.gz","src_id":"15593","5":"15593","creation_date":"1304685110","6":"1304685110"},{"0":"3424","vim_version":"7.0","1":"7.0","script_version":"0.6.0","2":"0.6.0","version_comment":"Adds the possibility to drop to a PDB session when a test fails or when a pdb is arbitrarily set.","3":"Adds the possibility to drop to a PDB session when a test fails or when a pdb is arbitrarily set.","package":"pytest.tar.gz","4":"pytest.tar.gz","src_id":"15482","5":"15482","creation_date":"1303256832","6":"1303256832"},{"0":"3424","vim_version":"7.0","1":"7.0","script_version":"0.0.5","2":"0.0.5","version_comment":"Adds Syntax Highlighting for saved py.test sessions.\r\nYou can now edit other files with errors in split buffers.\r\nSeparate error and exception buffers for better readability.\r\nBetter error handling and parsing.\r\n","3":"Adds Syntax Highlighting for saved py.test sessions.\r\nYou can now edit other files with errors in split buffers.\r\nSeparate error and exception buffers for better readability.\r\nBetter error handling and parsing.\r\n","package":"pytest.tar.gz","4":"pytest.tar.gz","src_id":"14996","5":"14996","creation_date":"1297308154","6":"1297308154"},{"0":"3424","vim_version":"7.0","1":"7.0","script_version":"0.4","2":"0.4","version_comment":"A *ton* of changes:\r\n\r\n* Adds buffers for last failed errors and full py.test output for last session \r\n* Adds syntax highlighting for py.test session and failed buffers\r\n* Makes the above buffers toggable\r\n* You can now jump to errors! In split buffers! OMG!\r\n* You can CIRCLE around the next, previous, last or first errors in the same split buffer!\r\n* You can go the \"end\" file where the error ended (if it is not your current file).","3":"A *ton* of changes:\r\n\r\n* Adds buffers for last failed errors and full py.test output for last session \r\n* Adds syntax highlighting for py.test session and failed buffers\r\n* Makes the above buffers toggable\r\n* You can now jump to errors! In split buffers! OMG!\r\n* You can CIRCLE around the next, previous, last or first errors in the same split buffer!\r\n* You can go the \"end\" file where the error ended (if it is not your current file).","package":"pytest.tar.gz","4":"pytest.tar.gz","src_id":"14951","5":"14951","creation_date":"1296783268","6":"1296783268"},{"0":"3424","vim_version":"7.0","1":"7.0","script_version":"0.3","2":"0.3","version_comment":"Adds support for native py.test errors and provides error messages when the plugin can't match the class or method you are requesting for testing.","3":"Adds support for native py.test errors and provides error messages when the plugin can't match the class or method you are requesting for testing.","package":"pytest.tar.gz","4":"pytest.tar.gz","src_id":"14904","5":"14904","creation_date":"1296324326","6":"1296324326"},{"0":"3424","vim_version":"7.0","1":"7.0","script_version":"0.2","2":"0.2","version_comment":"Getts better information output when tests are failing (Line:  1    ==>> AssertionError) and it introduces a \"verbose\" mode where you can see full results in a split window","3":"Getts better information output when tests are failing (Line:  1    ==>> AssertionError) and it introduces a \"verbose\" mode where you can see full results in a split window","package":"pytest.tar.gz","4":"pytest.tar.gz","src_id":"14899","5":"14899","creation_date":"1296268662","6":"1296268662"},{"0":"3424","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"pytest.tar.gz","4":"pytest.tar.gz","src_id":"14897","5":"14897","creation_date":"1296235687","6":"1296235687"}]},"3423":{"script_id":"3423","0":"3423","script_name":"neco-ghc","1":"neco-ghc","script_type":"utility","2":"utility","summary":"A neocomplcache plugin for Haskell, using ghc extensions","3":"A neocomplcache plugin for Haskell, using ghc extensions","description":"This plugin supports the following completion on the auto completion framework neocomplcache.\n\n* pragma http:\/\/gyazo.com\/c922e323be7dbed9aa70b2bac62be45e.png\n* language http:\/\/gyazo.com\/9df4aa3cf06fc07495d6dd67a4d07cc4.png\n* importing a module http:\/\/gyazo.com\/17a8bf08f3a6d5e123346f5f1c74c5f9.png\n* importing a function of a module http:\/\/gyazo.com\/d3698892a40ffb8e4bef970a02198715.png\n* function based on importing modules http:\/\/gyazo.com\/bc168a8aad5f38c6a83b8aa1b0fb14f6.png\n\nThe development is in github. https:\/\/github.com\/ujihisa\/neco-ghc\n\nneco-ghc was originally implemented by @eagletmt on July 25, 2010, and then ujihisa added some new features.\n","4":"This plugin supports the following completion on the auto completion framework neocomplcache.\n\n* pragma http:\/\/gyazo.com\/c922e323be7dbed9aa70b2bac62be45e.png\n* language http:\/\/gyazo.com\/9df4aa3cf06fc07495d6dd67a4d07cc4.png\n* importing a module http:\/\/gyazo.com\/17a8bf08f3a6d5e123346f5f1c74c5f9.png\n* importing a function of a module http:\/\/gyazo.com\/d3698892a40ffb8e4bef970a02198715.png\n* function based on importing modules http:\/\/gyazo.com\/bc168a8aad5f38c6a83b8aa1b0fb14f6.png\n\nThe development is in github. https:\/\/github.com\/ujihisa\/neco-ghc\n\nneco-ghc was originally implemented by @eagletmt on July 25, 2010, and then ujihisa added some new features.\n","install_details":"* install the latest neocomplcache.vim\n* install ghc-mod package by `cabal install ghc-mod`\n* Unarchive neco-ghc and put it into a dir of your &rtp.\n","5":"* install the latest neocomplcache.vim\n* install ghc-mod package by `cabal install ghc-mod`\n* Unarchive neco-ghc and put it into a dir of your &rtp.\n","first_name":"ujihisa","6":"ujihisa","last_name":".","7":".","releases":[{"0":"3423","vim_version":"7.3","1":"7.3","script_version":"1.1","2":"1.1","version_comment":"Supports operator completion in import statement, using ghc-mod 0.5.3","3":"Supports operator completion in import statement, using ghc-mod 0.5.3","package":"neco-ghc-1.1.zip","4":"neco-ghc-1.1.zip","src_id":"14938","5":"14938","creation_date":"1296637190","6":"1296637190"},{"0":"3423","vim_version":"7.3","1":"7.3","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"neco-ghc-1.0.zip","4":"neco-ghc-1.0.zip","src_id":"14863","5":"14863","creation_date":"1296008264","6":"1296008264"}]},"3422":{"script_id":"3422","0":"3422","script_name":"Comment Squawk","1":"Comment Squawk","script_type":"utility","2":"utility","summary":"Ensures that every PHP file you edit has good function comments.","3":"Ensures that every PHP file you edit has good function comments.","description":"Want a little secret to turn your code into an irresistible work of art?\r\n\r\nI knew the secret, and that's one reason my Comment Squawk plugin has been downloaded more than 80 times.  In fact, someone recently named it \"The Best Plugin of the 20th Century.\"\r\n\r\nIt's a great plugin. But if I had not used it so many times, do you think it would have been downloaded as much? Probably not. There's great power in good plugins. What you may not realize is Comment Squawk is not only the best plugin ever. It also is much better than any other vim plugin EVER.\r\n\r\nSo what does this have to do with turning your code into an irresistible work of art?\r\n\r\nHere's what. Behind Comment Squawk is a \"secret\" that makes it powerful. I know about it. Others know about it. And now, you're going to know it, too.\r\n\r\nThe \"secret\" is actually a generic formula that gets attention and creates desire in your mind. Comment Squawk has a generic formula hidden inside when you use it enough. All it takes is a little patience and lots of good comments. Therefore, I have included not two but THREE built-in function omissions with Comment Squawk to ignore CodeIgniter widget functions!\r\n\r\nComment squawk ensures that every PHP file you edit has good function comments.\r\n\r\nOn write, comment squawk identifies any functions that require comments and prompts the user to add comments.\r\n\r\nThe omits[] list has common functions which are omitted from the check.  Change the omits list to omit common functions from the check.","4":"Want a little secret to turn your code into an irresistible work of art?\r\n\r\nI knew the secret, and that's one reason my Comment Squawk plugin has been downloaded more than 80 times.  In fact, someone recently named it \"The Best Plugin of the 20th Century.\"\r\n\r\nIt's a great plugin. But if I had not used it so many times, do you think it would have been downloaded as much? Probably not. There's great power in good plugins. What you may not realize is Comment Squawk is not only the best plugin ever. It also is much better than any other vim plugin EVER.\r\n\r\nSo what does this have to do with turning your code into an irresistible work of art?\r\n\r\nHere's what. Behind Comment Squawk is a \"secret\" that makes it powerful. I know about it. Others know about it. And now, you're going to know it, too.\r\n\r\nThe \"secret\" is actually a generic formula that gets attention and creates desire in your mind. Comment Squawk has a generic formula hidden inside when you use it enough. All it takes is a little patience and lots of good comments. Therefore, I have included not two but THREE built-in function omissions with Comment Squawk to ignore CodeIgniter widget functions!\r\n\r\nComment squawk ensures that every PHP file you edit has good function comments.\r\n\r\nOn write, comment squawk identifies any functions that require comments and prompts the user to add comments.\r\n\r\nThe omits[] list has common functions which are omitted from the check.  Change the omits list to omit common functions from the check.","install_details":"Download commentsquawk.vim\r\nCopy commentsquawk.vim into vim plugin folder:\r\n    cp commentsquawk.vim ~\/.vim\/plugin\/","5":"Download commentsquawk.vim\r\nCopy commentsquawk.vim into vim plugin folder:\r\n    cp commentsquawk.vim ~\/.vim\/plugin\/","first_name":"Randall","6":"Randall","last_name":"Reynolds","7":"Reynolds","releases":[{"0":"3422","vim_version":"7.0","1":"7.0","script_version":"1.3","2":"1.3","version_comment":"1.3","3":"1.3","package":"commentsquawk.vim","4":"commentsquawk.vim","src_id":"14877","5":"14877","creation_date":"1296067173","6":"1296067173"}]},"3421":{"script_id":"3421","0":"3421","script_name":"Mind_syntax","1":"Mind_syntax","script_type":"syntax","2":"syntax","summary":"This script adds syntax for Mind component files","3":"This script adds syntax for Mind component files","description":"This script adds syntax for Mind component files: adl, idt, itf and c source files.\r\n\r\nFrom http:\/\/mind.ow2.org\/\r\n\r\nMIND is an implementation of the Fractal component model for the development of embedded softwares It provides an architecture compilation tool-chain, a component library and an integrated development environment based on Eclipse. \r\n\r\nThis script is based on Karthick Gururaj SystemC script: http:\/\/www.vim.org\/scripts\/script.php?script_id=835","4":"This script adds syntax for Mind component files: adl, idt, itf and c source files.\r\n\r\nFrom http:\/\/mind.ow2.org\/\r\n\r\nMIND is an implementation of the Fractal component model for the development of embedded softwares It provides an architecture compilation tool-chain, a component library and an integrated development environment based on Eclipse. \r\n\r\nThis script is based on Karthick Gururaj SystemC script: http:\/\/www.vim.org\/scripts\/script.php?script_id=835","install_details":"Untar the tarball in your vim home folder. See README.mind_syntax for more details.","5":"Untar the tarball in your vim home folder. See README.mind_syntax for more details.","first_name":"Jerome","6":"Jerome","last_name":"Reybert","7":"Reybert","releases":[{"0":"3421","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"mind_syntax.tgz","4":"mind_syntax.tgz","src_id":"14857","5":"14857","creation_date":"1295965994","6":"1295965994"}]},"3420":{"script_id":"3420","0":"3420","script_name":"hdl_plugin","1":"hdl_plugin","script_type":"utility","2":"utility","summary":"Vhdl\/Verilog fast instant and generate testbench file. ","3":"Vhdl\/Verilog fast instant and generate testbench file. ","description":"\"    hdl_plugin is a plugin that enables you to fast instant and generate a testbench file. \r\n\"    it can help you to compile by modelsim convenient. \r\n\" \r\n\r\n\"    main function: \r\n\"    Add a menu for vim: \r\n\"    create a library \r\n\"    Compile file \r\n\"    Add File Header \r\n\"    Add Content \r\n\"    Process \r\n\"    Module\/Entity \r\n\"    Vhdl Component:Creat a window to display the Component information,and add these to clipboard \r\n\"    Verilog Instant : Fast instant for verilog.Also add to clipboard \r\n\"    Vhdl Testbench :Generate a vhdl testbench file \r\n\"    Verilog Testbench :Generate a verilog testbench file \r\n\u00e2\u0080\u009c    Format Vhdl File: it can help you to finishing the code. \r\n\"                              Set \":,=>\" in the same position. \r\n\"                              Support the \"component\",\"signal\",\"instant\"and \"entity\" part. \r\n\"    Use <leader>, to fast define signal. \r\n\r\n\"    view details:http:\/\/www.cnblogs.com\/ifys\/archive\/2010\/11\/20\/1882673.html# \r\n\"    e-mail: ifys0325@163.com \r\n\"    Welcome to post your suggestions to me. \r\n  \r\n","4":"\"    hdl_plugin is a plugin that enables you to fast instant and generate a testbench file. \r\n\"    it can help you to compile by modelsim convenient. \r\n\" \r\n\r\n\"    main function: \r\n\"    Add a menu for vim: \r\n\"    create a library \r\n\"    Compile file \r\n\"    Add File Header \r\n\"    Add Content \r\n\"    Process \r\n\"    Module\/Entity \r\n\"    Vhdl Component:Creat a window to display the Component information,and add these to clipboard \r\n\"    Verilog Instant : Fast instant for verilog.Also add to clipboard \r\n\"    Vhdl Testbench :Generate a vhdl testbench file \r\n\"    Verilog Testbench :Generate a verilog testbench file \r\n\u00e2\u0080\u009c    Format Vhdl File: it can help you to finishing the code. \r\n\"                              Set \":,=>\" in the same position. \r\n\"                              Support the \"component\",\"signal\",\"instant\"and \"entity\" part. \r\n\"    Use <leader>, to fast define signal. \r\n\r\n\"    view details:http:\/\/www.cnblogs.com\/ifys\/archive\/2010\/11\/20\/1882673.html# \r\n\"    e-mail: ifys0325@163.com \r\n\"    Welcome to post your suggestions to me. \r\n  \r\n","install_details":"Copy the hdl_plugin to $VIM\/vimfiles\/plugin\/ (on Windows platforms). ","5":"Copy the hdl_plugin to $VIM\/vimfiles\/plugin\/ (on Windows platforms). ","first_name":"\u9648","6":"陈","last_name":"\u52c7","7":"勇","releases":[{"0":"3420","vim_version":"7.0","1":"7.0","script_version":"v2.5","2":"v2.5","version_comment":"Fixed a bug in function HDL_Signal_Dec_Vhdl(); \r\nAdd a function HDL_Generic_For_Debussy(),which can used with debussy.","3":"Fixed a bug in function HDL_Signal_Dec_Vhdl(); \r\nAdd a function HDL_Generic_For_Debussy(),which can used with debussy.","package":"hdl_plugin.vim","4":"hdl_plugin.vim","src_id":"15337","5":"15337","creation_date":"1301469763","6":"1301469763"},{"0":"3420","vim_version":"7.0","1":"7.0","script_version":"v2.4","2":"v2.4","version_comment":"Fixed Some Bugs","3":"Fixed Some Bugs","package":"hdl_plugin.vim","4":"hdl_plugin.vim","src_id":"14870","5":"14870","creation_date":"1296009708","6":"1296009708"},{"0":"3420","vim_version":"7.0","1":"7.0","script_version":"v2.3","2":"v2.3","version_comment":"Add a Function \"HDL_Signal_Dec_Vhdl\".Which can fast define signal. \r\n          Use defaule <leader>, as the hot key.The idea from sunil shukla. \r\nFixed Some Bugs. \r\nRedifined The function name.","3":"Add a Function \"HDL_Signal_Dec_Vhdl\".Which can fast define signal. \r\n          Use defaule <leader>, as the hot key.The idea from sunil shukla. \r\nFixed Some Bugs. \r\nRedifined The function name.","package":"hdl_plugin.vim","4":"hdl_plugin.vim","src_id":"14869","5":"14869","creation_date":"1296009649","6":"1296009649"},{"0":"3420","vim_version":"7.0","1":"7.0","script_version":"v2.2","2":"v2.2","version_comment":"Add a menu list \"Format Vhdl File\" which can finishing the code. \r\nmake \":,=>\" in the same position.Support the \"component\",\"signal\",\"instant\"and \"entity\" part.","3":"Add a menu list \"Format Vhdl File\" which can finishing the code. \r\nmake \":,=>\" in the same position.Support the \"component\",\"signal\",\"instant\"and \"entity\" part.","package":"hdl_plugin.vim","4":"hdl_plugin.vim","src_id":"14868","5":"14868","creation_date":"1296009618","6":"1296009618"},{"0":"3420","vim_version":"7.0","1":"7.0","script_version":"v2.1","2":"v2.1","version_comment":"Supports \"inout\" port \r\nCan be used for verilog file","3":"Supports \"inout\" port \r\nCan be used for verilog file","package":"hdl_plugin.vim","4":"hdl_plugin.vim","src_id":"14867","5":"14867","creation_date":"1296009461","6":"1296009461"},{"0":"3420","vim_version":"7.0","1":"7.0","script_version":"v2.0","2":"v2.0","version_comment":"Supports many port in the identical line","3":"Supports many port in the identical line","package":"hdl_plugin.vim","4":"hdl_plugin.vim","src_id":"14866","5":"14866","creation_date":"1296009410","6":"1296009410"},{"0":"3420","vim_version":"7.0","1":"7.0","script_version":"v1.9","2":"v1.9","version_comment":"Added support for 'generic' \r\nUpdata the menu \r\nSet some initial value","3":"Added support for 'generic' \r\nUpdata the menu \r\nSet some initial value","package":"hdl_plugin.vim","4":"hdl_plugin.vim","src_id":"14865","5":"14865","creation_date":"1296009232","6":"1296009232"},{"0":"3420","vim_version":"7.0","1":"7.0","script_version":"v1.8","2":"v1.8","version_comment":"Fixed some bugs","3":"Fixed some bugs","package":"hdl_plugin.vim","4":"hdl_plugin.vim","src_id":"14864","5":"14864","creation_date":"1296009198","6":"1296009198"},{"0":"3420","vim_version":"7.0","1":"7.0","script_version":"v1.7","2":"v1.7","version_comment":"Initial upload","3":"Initial upload","package":"hdl_plugin.vim","4":"hdl_plugin.vim","src_id":"14853","5":"14853","creation_date":"1295932600","6":"1295932600"}]},"3419":{"script_id":"3419","0":"3419","script_name":"kkruby.vim","1":"kkruby.vim","script_type":"color scheme","2":"color scheme","summary":"color for ruby","3":"color for ruby","description":"color for ruby\r\n\r\nscreen shot : \r\nhttp:\/\/l.ruby-china.org\/photo\/ba34e6cf9f8f5a12883489b2a86cdfbd.png\r\n","4":"color for ruby\r\n\r\nscreen shot : \r\nhttp:\/\/l.ruby-china.org\/photo\/ba34e6cf9f8f5a12883489b2a86cdfbd.png\r\n","install_details":"1, move to vimfiles\\colors\r\n2, add in .vimrc : colo kkruby\r\n","5":"1, move to vimfiles\\colors\r\n2, add in .vimrc : colo kkruby\r\n","first_name":"sevk","6":"sevk","last_name":"k","7":"k","releases":[{"0":"3419","vim_version":"7.0","1":"7.0","script_version":"2.1","2":"2.1","version_comment":"more color","3":"more color","package":"kkruby.vim","4":"kkruby.vim","src_id":"19334","5":"19334","creation_date":"1357712920","6":"1357712920"},{"0":"3419","vim_version":"7.3","1":"7.3","script_version":"2.1","2":"2.1","version_comment":"perfect","3":"perfect","package":"kkruby.vim","4":"kkruby.vim","src_id":"17553","5":"17553","creation_date":"1330674828","6":"1330674828"},{"0":"3419","vim_version":"7.2","1":"7.2","script_version":"1.6","2":"1.6","version_comment":"color for ruby","3":"color for ruby","package":"kkruby.vim","4":"kkruby.vim","src_id":"16934","5":"16934","creation_date":"1321927453","6":"1321927453"}]},"3418":{"script_id":"3418","0":"3418","script_name":"QCL syntax hilighting","1":"QCL syntax hilighting","script_type":"syntax","2":"syntax","summary":"Syntax hilighting for QCL","3":"Syntax hilighting for QCL","description":"This file provides syntax hilighting for Quantum Computing Language.\r\n\r\nIt includes hilighting for the built in operators and functions.","4":"This file provides syntax hilighting for Quantum Computing Language.\r\n\r\nIt includes hilighting for the built in operators and functions.","install_details":"To install, place this script in your syntax folder and add the following line to your vimrc:\r\n\r\nau BufRead,BufNewFile *.qcl setfiletype qcl","5":"To install, place this script in your syntax folder and add the following line to your vimrc:\r\n\r\nau BufRead,BufNewFile *.qcl setfiletype qcl","first_name":"George","6":"George","last_name":"Bargoud","7":"Bargoud","releases":[{"0":"3418","vim_version":"7.0","1":"7.0","script_version":"1","2":"1","version_comment":"Initial upload","3":"Initial upload","package":"qcl.vim","4":"qcl.vim","src_id":"14849","5":"14849","creation_date":"1295913317","6":"1295913317"}]},"3417":{"script_id":"3417","0":"3417","script_name":"toner.vim","1":"toner.vim","script_type":"utility","2":"utility","summary":"A tool for toning vim highlight colors","3":"A tool for toning vim highlight colors","description":"Toner is a plugin for interactively and visually toning vim highlight colors.\r\n\r\nSee https:\/\/github.com\/niklasl\/vim-toner for full details (and development).\r\n\r\n(Toner requires Vim 7 compiled with |+float|, and user settings 'nocompatible', |:syntax| on etc., as might be expected.)\r\n\r\nThe HSL and hue rotation code is from huerotation.vim (Vim Script #2283) by\r\nYukihiro Nakadaira. See http:\/\/www.vim.org\/scripts\/script.php?script_id=2283\r\n(placed in the public domain). Many thanks for this!\r\n","4":"Toner is a plugin for interactively and visually toning vim highlight colors.\r\n\r\nSee https:\/\/github.com\/niklasl\/vim-toner for full details (and development).\r\n\r\n(Toner requires Vim 7 compiled with |+float|, and user settings 'nocompatible', |:syntax| on etc., as might be expected.)\r\n\r\nThe HSL and hue rotation code is from huerotation.vim (Vim Script #2283) by\r\nYukihiro Nakadaira. See http:\/\/www.vim.org\/scripts\/script.php?script_id=2283\r\n(placed in the public domain). Many thanks for this!\r\n","install_details":"The nicest way is to use Pathogen: http:\/\/www.vim.org\/scripts\/script.php?script_id=2332\r\n","5":"The nicest way is to use Pathogen: http:\/\/www.vim.org\/scripts\/script.php?script_id=2332\r\n","first_name":"Niklas","6":"Niklas","last_name":"Lindstr\u00c3\u00b6m","7":"Lindstr\u00c3\u00b6m","releases":[{"0":"3417","vim_version":"7.3","1":"7.3","script_version":"0.1.1","2":"0.1.1","version_comment":"Just fixed typo bugs in toner#unmap().","3":"Just fixed typo bugs in toner#unmap().","package":"toner-0.1.1.tar.gz","4":"toner-0.1.1.tar.gz","src_id":"14835","5":"14835","creation_date":"1295815513","6":"1295815513"},{"0":"3417","vim_version":"7.3","1":"7.3","script_version":"0.1.0","2":"0.1.0","version_comment":"Initial upload","3":"Initial upload","package":"toner-0.1.0.tar.gz","4":"toner-0.1.0.tar.gz","src_id":"14833","5":"14833","creation_date":"1295797016","6":"1295797016"}]},"3416":{"script_id":"3416","0":"3416","script_name":"w3cvalidator","1":"w3cvalidator","script_type":"utility","2":"utility","summary":"W3cValidate.vim is a plugin that enables buffer\/url w3c validation","3":"W3cValidate.vim is a plugin that enables buffer\/url w3c validation","description":"W3cValidate.vim is a plugin that enables buffer\/url validation using the http:\/\/validator.w3.org api\r\n\r\n== USAGE ==\r\n\r\nCopy w3cvalidate.vim file inside plugin directory, source it or restart Vim. Use \r\n\r\n    :W3cValidate to validate the current buffer\r\n    \r\n    :W3cValidate \"[url_here]\" to validate a hosted page\r\n    \r\n    :W3cValidateDT \"[doctype]\" to validate the buffer using the [doctype] override. Make sure the doctype is a valid doctype\r\n\r\nThe validator service url can be changed if you run an instance of it localy by setting  g:w3_validator_url  in .vimrc\r\n\r\nThe script has API timeout default to 20 seconds. You can change it by setting  g:w3_apicall_timeout  in .vimrc\r\n\r\n== NOTES ==\r\n\r\nGithub - https:\/\/github.com\/dekomote\/w3cvalidate.vim\r\n\r\nBitbucket - https:\/\/bitbucket.org\/dekomote\/w3cvalidate.vim\r\n\r\nNeeds vim compiled with +python option. Works out of the box on Ubuntu and Ubuntu-derivates.\r\n\r\nThanks to Yegappan Lakshmanan for Scratch.vim http:\/\/www.vim.org\/scripts\/script.php?script_id=664, I got some ideas for the temporary buffer displaying the errors\/warnings from this script.","4":"W3cValidate.vim is a plugin that enables buffer\/url validation using the http:\/\/validator.w3.org api\r\n\r\n== USAGE ==\r\n\r\nCopy w3cvalidate.vim file inside plugin directory, source it or restart Vim. Use \r\n\r\n    :W3cValidate to validate the current buffer\r\n    \r\n    :W3cValidate \"[url_here]\" to validate a hosted page\r\n    \r\n    :W3cValidateDT \"[doctype]\" to validate the buffer using the [doctype] override. Make sure the doctype is a valid doctype\r\n\r\nThe validator service url can be changed if you run an instance of it localy by setting  g:w3_validator_url  in .vimrc\r\n\r\nThe script has API timeout default to 20 seconds. You can change it by setting  g:w3_apicall_timeout  in .vimrc\r\n\r\n== NOTES ==\r\n\r\nGithub - https:\/\/github.com\/dekomote\/w3cvalidate.vim\r\n\r\nBitbucket - https:\/\/bitbucket.org\/dekomote\/w3cvalidate.vim\r\n\r\nNeeds vim compiled with +python option. Works out of the box on Ubuntu and Ubuntu-derivates.\r\n\r\nThanks to Yegappan Lakshmanan for Scratch.vim http:\/\/www.vim.org\/scripts\/script.php?script_id=664, I got some ideas for the temporary buffer displaying the errors\/warnings from this script.","install_details":"Copy w3cvalidate.vim file inside plugin directory, source it or restart Vim.","5":"Copy w3cvalidate.vim file inside plugin directory, source it or restart Vim.","first_name":"Dejan","6":"Dejan","last_name":"Noveski","7":"Noveski","releases":[{"0":"3416","vim_version":"7.0","1":"7.0","script_version":"0.31","2":"0.31","version_comment":"Fixed the json\/simplejson bug.","3":"Fixed the json\/simplejson bug.","package":"w3cvalidate.vim","4":"w3cvalidate.vim","src_id":"14845","5":"14845","creation_date":"1295854025","6":"1295854025"},{"0":"3416","vim_version":"7.0","1":"7.0","script_version":"0.3","2":"0.3","version_comment":"Added explanation messages to the output, added script documentation, added the ability to override doctype setting for buffer validation using :W3cValidateDT [doctype]","3":"Added explanation messages to the output, added script documentation, added the ability to override doctype setting for buffer validation using :W3cValidateDT [doctype]","package":"w3cvalidate.vim","4":"w3cvalidate.vim","src_id":"14832","5":"14832","creation_date":"1295791991","6":"1295791991"},{"0":"3416","vim_version":"7.0","1":"7.0","script_version":"0.2","2":"0.2","version_comment":"Added global settings - g:w3_validator_url which sets validator url if you run an instance localy and g:w3_apicall_timeout which sets API timeout","3":"Added global settings - g:w3_validator_url which sets validator url if you run an instance localy and g:w3_apicall_timeout which sets API timeout","package":"w3cvalidate.vim","4":"w3cvalidate.vim","src_id":"14830","5":"14830","creation_date":"1295735086","6":"1295735086"},{"0":"3416","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"w3cvalidate.vim","4":"w3cvalidate.vim","src_id":"14829","5":"14829","creation_date":"1295730377","6":"1295730377"}]},"3415":{"script_id":"3415","0":"3415","script_name":"supp.vim","1":"supp.vim","script_type":"syntax","2":"syntax","summary":"Syntax highlighting for Valgrind suppression files","3":"Syntax highlighting for Valgrind suppression files","description":"The script provides syntax highlighting for Valgrind suppression files, usually bearing the extension .supp.","4":"The script provides syntax highlighting for Valgrind suppression files, usually bearing the extension .supp.","install_details":"Put it to ~\/.vim\/syntax\/.  Add\r\n\r\nau BufNewFile,BufRead *.supp set ft=supp\r\n\r\nto your ~\/.vimrc.","5":"Put it to ~\/.vim\/syntax\/.  Add\r\n\r\nau BufNewFile,BufRead *.supp set ft=supp\r\n\r\nto your ~\/.vimrc.","first_name":"David","6":"David","last_name":"Necas","7":"Necas","releases":[{"0":"3415","vim_version":"6.0","1":"6.0","script_version":"20110206","2":"20110206","version_comment":"The placeholder insert-a-suppression-name-here is highlighted as TODO.","3":"The placeholder insert-a-suppression-name-here is highlighted as TODO.","package":"supp.vim","4":"supp.vim","src_id":"14962","5":"14962","creation_date":"1296992234","6":"1296992234"},{"0":"3415","vim_version":"6.0","1":"6.0","script_version":"20110121","2":"20110121","version_comment":"Initial upload","3":"Initial upload","package":"supp.vim","4":"supp.vim","src_id":"14823","5":"14823","creation_date":"1295635482","6":"1295635482"}]},"3414":{"script_id":"3414","0":"3414","script_name":"bocau","1":"bocau","script_type":"color scheme","2":"color scheme","summary":"A dark color theme, inspire by vividchalk","3":"A dark color theme, inspire by vividchalk","description":"Screenshots:\r\nhttp:\/\/www.flickr.com\/photos\/29519254@N00\/5375291973\/\r\nhttp:\/\/www.flickr.com\/photos\/29519254@N00\/5367198495\/\r\n\r\nFor more update, please visit:\r\nhttp:\/\/github.com\/tienle\/bocau\r\n\r\nAny ideas, suggestions are welcome.\r\n","4":"Screenshots:\r\nhttp:\/\/www.flickr.com\/photos\/29519254@N00\/5375291973\/\r\nhttp:\/\/www.flickr.com\/photos\/29519254@N00\/5367198495\/\r\n\r\nFor more update, please visit:\r\nhttp:\/\/github.com\/tienle\/bocau\r\n\r\nAny ideas, suggestions are welcome.\r\n","install_details":"Just place it under ~\/.vim\/colors","5":"Just place it under ~\/.vim\/colors","first_name":"tien","6":"tien","last_name":"le","7":"le","releases":[{"0":"3414","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"bocau.vim","4":"bocau.vim","src_id":"14822","5":"14822","creation_date":"1295630373","6":"1295630373"}]},"3413":{"script_id":"3413","0":"3413","script_name":"zazen","1":"zazen","script_type":"color scheme","2":"color scheme","summary":"a dark grey colorscheme based on zenesque","3":"a dark grey colorscheme based on zenesque","description":"A very minimal dark\/grey color scheme based on zenesque (vimscript#3340). Zazen only includes the dark version with slightly modified shades and minimal coloring. Shades and colors were adjusted to give priority to elements that might be regarded as more more important (although that might be different for different people).\r\n\r\nAs of version 1.1, both GUI and 256-color terminals are supported.\r\n\r\nScreenshot (GUI version): http:\/\/img5.imageshack.us\/i\/zazen.png\/\r\n\r\nScreenshot (terminal version): http:\/\/imageshack.us\/f\/850\/zazen11.png\/","4":"A very minimal dark\/grey color scheme based on zenesque (vimscript#3340). Zazen only includes the dark version with slightly modified shades and minimal coloring. Shades and colors were adjusted to give priority to elements that might be regarded as more more important (although that might be different for different people).\r\n\r\nAs of version 1.1, both GUI and 256-color terminals are supported.\r\n\r\nScreenshot (GUI version): http:\/\/img5.imageshack.us\/i\/zazen.png\/\r\n\r\nScreenshot (terminal version): http:\/\/imageshack.us\/f\/850\/zazen11.png\/","install_details":"Copy zazen.vim to your colors directory and switch to it with :colorscheme zazen (or select zazen from the Edit->Colorscheme menu) or in your vimrc.\r\n\r\nIf you are using pathogen or vundle, the colorscheme can be found on github: http:\/\/github.com\/zaki\/zazen","5":"Copy zazen.vim to your colors directory and switch to it with :colorscheme zazen (or select zazen from the Edit->Colorscheme menu) or in your vimrc.\r\n\r\nIf you are using pathogen or vundle, the colorscheme can be found on github: http:\/\/github.com\/zaki\/zazen","first_name":"Zoltan","6":"Zoltan","last_name":"Dezso","7":"Dezso","releases":[{"0":"3413","vim_version":"7.0","1":"7.0","script_version":"1.1.2","2":"1.1.2","version_comment":"* Minor update to make SpecialKey more subtle","3":"* Minor update to make SpecialKey more subtle","package":"zazen.vim","4":"zazen.vim","src_id":"18547","5":"18547","creation_date":"1346774369","6":"1346774369"},{"0":"3413","vim_version":"7.0","1":"7.0","script_version":"1.1.1","2":"1.1.1","version_comment":"* Added taglist colors\r\n* Fixed cterm colors that were using italic","3":"* Added taglist colors\r\n* Fixed cterm colors that were using italic","package":"zazen.vim","4":"zazen.vim","src_id":"16150","5":"16150","creation_date":"1311748830","6":"1311748830"},{"0":"3413","vim_version":"7.0","1":"7.0","script_version":"1.1","2":"1.1","version_comment":"Added 256-color terminal support","3":"Added 256-color terminal support","package":"zazen.vim","4":"zazen.vim","src_id":"15823","5":"15823","creation_date":"1307365491","6":"1307365491"},{"0":"3413","vim_version":"7.0","1":"7.0","script_version":"1.0.2","2":"1.0.2","version_comment":"Minor tweak to make ColorColumn more subtle","3":"Minor tweak to make ColorColumn more subtle","package":"zazen.vim","4":"zazen.vim","src_id":"15639","5":"15639","creation_date":"1305387811","6":"1305387811"},{"0":"3413","vim_version":"7.0","1":"7.0","script_version":"1.0.1","2":"1.0.1","version_comment":"Colored diff and slight tone changes.","3":"Colored diff and slight tone changes.","package":"zazen.vim","4":"zazen.vim","src_id":"15334","5":"15334","creation_date":"1301459854","6":"1301459854"},{"0":"3413","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"zazen.vim","4":"zazen.vim","src_id":"14815","5":"14815","creation_date":"1295588871","6":"1295588871"}]},"3412":{"script_id":"3412","0":"3412","script_name":"xterm-color-table.vim","1":"xterm-color-table.vim","script_type":"utility","2":"utility","summary":"All 256 xterm colors with their RGB equivalents, right in Vim!","3":"All 256 xterm colors with their RGB equivalents, right in Vim!","description":"GITHUB\r\n\r\nhttp:\/\/github.com\/guns\/xterm-color-table.vim\r\n\r\n\r\nNOTES\r\n\r\n * Provides command :XtermColorTable, as well as variants for different splits\r\n * Xterm numbers on the left, equivalent RGB values on the right\r\n * Press `#` to yank current color (shortcut for yiw)\r\n * Press `t` to toggle RGB text visibility\r\n * Press `f` to set RGB text to current color\r\n * Buffer behavior similar to Scratch.vim\r\n\r\n\r\nSCREENSHOTS\r\n\r\nhttp:\/\/guns.github.com\/xterm-color-table.vim\/images\/xterm-color-table.png\r\nhttp:\/\/guns.github.com\/xterm-color-table.vim\/images\/xterm-color-table-with-visible-rgb.png\r\n\r\n\r\nINSPIRED BY\r\n\r\n * http:\/\/www.calmar.ws\/vim\/256-xterm-24bit-rgb-color-chart.html\r\n * http:\/\/vim.wikia.com\/wiki\/Xterm256_color_names_for_console_Vim\r\n * http:\/\/www.vim.org\/scripts\/script.php?script_id=664\r\n","4":"GITHUB\r\n\r\nhttp:\/\/github.com\/guns\/xterm-color-table.vim\r\n\r\n\r\nNOTES\r\n\r\n * Provides command :XtermColorTable, as well as variants for different splits\r\n * Xterm numbers on the left, equivalent RGB values on the right\r\n * Press `#` to yank current color (shortcut for yiw)\r\n * Press `t` to toggle RGB text visibility\r\n * Press `f` to set RGB text to current color\r\n * Buffer behavior similar to Scratch.vim\r\n\r\n\r\nSCREENSHOTS\r\n\r\nhttp:\/\/guns.github.com\/xterm-color-table.vim\/images\/xterm-color-table.png\r\nhttp:\/\/guns.github.com\/xterm-color-table.vim\/images\/xterm-color-table-with-visible-rgb.png\r\n\r\n\r\nINSPIRED BY\r\n\r\n * http:\/\/www.calmar.ws\/vim\/256-xterm-24bit-rgb-color-chart.html\r\n * http:\/\/vim.wikia.com\/wiki\/Xterm256_color_names_for_console_Vim\r\n * http:\/\/www.vim.org\/scripts\/script.php?script_id=664\r\n","install_details":"","5":"","first_name":"Sung","6":"Sung","last_name":"Pae","7":"Pae","releases":[{"0":"3412","vim_version":"7.0","1":"7.0","script_version":"1.6","2":"1.6","version_comment":"New features:\r\n\r\n* New alternate opening commands: VXtermColorTable for vsplit, TXtermColorTable for tabnew, etc\r\n* Better handling of ColorScheme events (existing windows stay open and reapply buffer highlight rules)\r\n* New convenience buffer mapping <#> (alias of yiw)","3":"New features:\r\n\r\n* New alternate opening commands: VXtermColorTable for vsplit, TXtermColorTable for tabnew, etc\r\n* Better handling of ColorScheme events (existing windows stay open and reapply buffer highlight rules)\r\n* New convenience buffer mapping <#> (alias of yiw)","package":"xterm-color-table.vim.tar.gz","4":"xterm-color-table.vim.tar.gz","src_id":"15556","5":"15556","creation_date":"1304226242","6":"1304226242"},{"0":"3412","vim_version":"7.0","1":"7.0","script_version":"1.4","2":"1.4","version_comment":"Fix regression: GUI Vims are picky about capitalization in `hi term=NONE'","3":"Fix regression: GUI Vims are picky about capitalization in `hi term=NONE'","package":"xterm-color-table.vim.tar.gz","4":"xterm-color-table.vim.tar.gz","src_id":"14994","5":"14994","creation_date":"1297296075","6":"1297296075"},{"0":"3412","vim_version":"7.0","1":"7.0","script_version":"1.3","2":"1.3","version_comment":"Add toggleable RGB visibility. Thanks to Alexey Radkov for the suggestion.","3":"Add toggleable RGB visibility. Thanks to Alexey Radkov for the suggestion.","package":"xterm-color-table.vim.tar.gz","4":"xterm-color-table.vim.tar.gz","src_id":"14990","5":"14990","creation_date":"1297226797","6":"1297226797"},{"0":"3412","vim_version":"7.0","1":"7.0","script_version":"1.2","2":"1.2","version_comment":"Removed buffer mapping; much smarter buffer behavior, \u00c3\u00a0 la Scratch.vim","3":"Removed buffer mapping; much smarter buffer behavior, \u00c3\u00a0 la Scratch.vim","package":"xterm-color-table.vim.tar.gz","4":"xterm-color-table.vim.tar.gz","src_id":"14873","5":"14873","creation_date":"1296039285","6":"1296039285"},{"0":"3412","vim_version":"7.0","1":"7.0","script_version":"1.1","2":"1.1","version_comment":"Remove `ownsyntax' statement, which is a 7.3+ feature. Thanks to Farhad Fouladi.","3":"Remove `ownsyntax' statement, which is a 7.3+ feature. Thanks to Farhad Fouladi.","package":"xterm-color-table.vim.tar.gz","4":"xterm-color-table.vim.tar.gz","src_id":"14819","5":"14819","creation_date":"1295612640","6":"1295612640"},{"0":"3412","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"xterm-color-table.vim.tar.gz","4":"xterm-color-table.vim.tar.gz","src_id":"14814","5":"14814","creation_date":"1295588502","6":"1295588502"}]},"3411":{"script_id":"3411","0":"3411","script_name":"syntax_check_embedded_perl.vim","1":"syntax_check_embedded_perl.vim","script_type":"ftplugin","2":"ftplugin","summary":"automatically check the syntax of embedded perl code in vim scripts on save","3":"automatically check the syntax of embedded perl code in vim scripts on save","description":"This script eases development of vim scripts that use embedded perl code by automatically checking the embedded perl code for compile-time errors when the scripts are saved.\r\n\r\nSo if you save a file with a syntax error you will get a message something like this:\r\n\r\n     :!~\/.vim\/syntax_check_embedded_perl.perl \/some\/file.vim \/tmp\/BjPcoMnIoe\r\n     Global symbol \"$syn_error_var\" requires explicit package name at \/some\/file.vim line 42.\r\n     BEGIN not safe after errors--compilation aborted at \/some\/file.vim line 46.\r\n     \r\n     \/some\/file.vim has embedded perl compilation errors.  The file has been saved anyway, but a copy of the old (pre-save) version of the file is available in \/tmp\/BjPcoMnIoe\r\n     \r\n     shell returned 1\r\n\r\n     Press ENTER or type command to continue\r\n\r\nThis supports a style of programming where source files are kept  with\r\nvalid syntax.  This is a particularly useful approach when embedding perl\r\nin vim as error propagation up through vim can get a bit wild.\r\n\r\nSee also http:\/\/www.vim.org\/scripts\/script.php?script_id=3406 for better\r\nrun-time error diagnostics.\r\n","4":"This script eases development of vim scripts that use embedded perl code by automatically checking the embedded perl code for compile-time errors when the scripts are saved.\r\n\r\nSo if you save a file with a syntax error you will get a message something like this:\r\n\r\n     :!~\/.vim\/syntax_check_embedded_perl.perl \/some\/file.vim \/tmp\/BjPcoMnIoe\r\n     Global symbol \"$syn_error_var\" requires explicit package name at \/some\/file.vim line 42.\r\n     BEGIN not safe after errors--compilation aborted at \/some\/file.vim line 46.\r\n     \r\n     \/some\/file.vim has embedded perl compilation errors.  The file has been saved anyway, but a copy of the old (pre-save) version of the file is available in \/tmp\/BjPcoMnIoe\r\n     \r\n     shell returned 1\r\n\r\n     Press ENTER or type command to continue\r\n\r\nThis supports a style of programming where source files are kept  with\r\nvalid syntax.  This is a particularly useful approach when embedding perl\r\nin vim as error propagation up through vim can get a bit wild.\r\n\r\nSee also http:\/\/www.vim.org\/scripts\/script.php?script_id=3406 for better\r\nrun-time error diagnostics.\r\n","install_details":"Its a standard vimball so all you need to do is:\r\n\r\n     vim update_perl_line_directives.vba\r\n     :so %","5":"Its a standard vimball so all you need to do is:\r\n\r\n     vim update_perl_line_directives.vba\r\n     :so %","first_name":"Britton","6":"Britton","last_name":"Kerin","7":"Kerin","releases":[{"0":"3411","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"syntax_check_embedded_perl.vba","4":"syntax_check_embedded_perl.vba","src_id":"14797","5":"14797","creation_date":"1295481175","6":"1295481175"}]},"3410":{"script_id":"3410","0":"3410","script_name":"nclipper.vim","1":"nclipper.vim","script_type":"utility","2":"utility","summary":"copy lines into clipboard with the line numbers","3":"copy lines into clipboard with the line numbers","description":"Start visual mode with `V` and select some lines.\n\nhttp:\/\/gyazo.com\/ef8121528e4a269ce894e25c289b489a.png\n\nType `<C-y>`\n\nhttp:\/\/gyazo.com\/2b56de0c4f7603df7a00e9845704b39c.png\n\nNow your clipboard or Vim register `\"+` has the lines you selected with line numbers. Paste it anywhere you want!\n\nhttp:\/\/gyazo.com\/5000e1cca5ad81203541fb7e3ce82a50.png\n\nIf you also want to copy the filename in the 1st line, use `<M-y>` (meta + y which is cmd + y on OSX and alt + y on Linux.)\n\nContributors: tyru and rconradharris\n\nThe development is in github. https:\/\/github.com\/ujihisa\/nclipper.vim\n","4":"Start visual mode with `V` and select some lines.\n\nhttp:\/\/gyazo.com\/ef8121528e4a269ce894e25c289b489a.png\n\nType `<C-y>`\n\nhttp:\/\/gyazo.com\/2b56de0c4f7603df7a00e9845704b39c.png\n\nNow your clipboard or Vim register `\"+` has the lines you selected with line numbers. Paste it anywhere you want!\n\nhttp:\/\/gyazo.com\/5000e1cca5ad81203541fb7e3ce82a50.png\n\nIf you also want to copy the filename in the 1st line, use `<M-y>` (meta + y which is cmd + y on OSX and alt + y on Linux.)\n\nContributors: tyru and rconradharris\n\nThe development is in github. https:\/\/github.com\/ujihisa\/nclipper.vim\n","install_details":"Unarchive and put it into a dir of your &rtp.\n","5":"Unarchive and put it into a dir of your &rtp.\n","first_name":"ujihisa","6":"ujihisa","last_name":".","7":".","releases":[{"0":"3410","vim_version":"7.3","1":"7.3","script_version":"1.2","2":"1.2","version_comment":"Support for non-xterm. Adding `<M-y>` to copy with filename.","3":"Support for non-xterm. Adding `<M-y>` to copy with filename.","package":"nclipper.vim-1.2.zip","4":"nclipper.vim-1.2.zip","src_id":"20438","5":"20438","creation_date":"1372226070","6":"1372226070"},{"0":"3410","vim_version":"7.3","1":"7.3","script_version":"1.1","2":"1.1","version_comment":"Align line numbers and format option `g:nclipper_format`","3":"Align line numbers and format option `g:nclipper_format`","package":"nclipper.vim-1.1.zip","4":"nclipper.vim-1.1.zip","src_id":"14805","5":"14805","creation_date":"1295498752","6":"1295498752"},{"0":"3410","vim_version":"7.3","1":"7.3","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"nclipper.vim-1.0.zip","4":"nclipper.vim-1.0.zip","src_id":"14794","5":"14794","creation_date":"1295476217","6":"1295476217"}]},"3409":{"script_id":"3409","0":"3409","script_name":"HJKL","1":"HJKL","script_type":"game","2":"game","summary":"Use H,J,K,L to explore maze","3":"Use H,J,K,L to explore maze","description":"Lots of beginners do not like to use vim's h,j,k,l key to move concur, so I made this game, hopefully can help beginners get used to h,j,k and l.\r\n\r\nThis is a maze exploring game.\r\nA 15*15 maze is randomly generated, and user('@') need to go to target position('X').\r\nOnly h,j,k,l are allowed for controlling.\r\nType 'q' twice to quit the game.\r\n\r\n\r\nMaximize the window before starting the game to get better view.\r\n\r\nType :HJKL to start a new game.\r\n\r\n\r\nWant more challenge, try konami code(kkjjhlhlba)\r\n\r\n\r\n\r\nFuture plan:\r\n1. Better random number generator is needed. Current version sometimes leads to infinite loop when generating random maze.\r\n2. Need more challenging maze. Better maze construction algorithm is needed.\r\n3. More fancy features...","4":"Lots of beginners do not like to use vim's h,j,k,l key to move concur, so I made this game, hopefully can help beginners get used to h,j,k and l.\r\n\r\nThis is a maze exploring game.\r\nA 15*15 maze is randomly generated, and user('@') need to go to target position('X').\r\nOnly h,j,k,l are allowed for controlling.\r\nType 'q' twice to quit the game.\r\n\r\n\r\nMaximize the window before starting the game to get better view.\r\n\r\nType :HJKL to start a new game.\r\n\r\n\r\nWant more challenge, try konami code(kkjjhlhlba)\r\n\r\n\r\n\r\nFuture plan:\r\n1. Better random number generator is needed. Current version sometimes leads to infinite loop when generating random maze.\r\n2. Need more challenging maze. Better maze construction algorithm is needed.\r\n3. More fancy features...","install_details":"Copy hjkl.vim into ~\/.vim\/plugin\/\r\n\r\n","5":"Copy hjkl.vim into ~\/.vim\/plugin\/\r\n\r\n","first_name":"Ran","6":"Ran","last_name":"Bi","7":"Bi","releases":[{"0":"3409","vim_version":"7.0","1":"7.0","script_version":"1.08","2":"1.08","version_comment":"How need type q twice to quit.\r\nWhen no argument is passed, the game starts with 5*5 sized maze.\r\nThen you reach the target, a bigger sized maze will be generated and a new game will be started.","3":"How need type q twice to quit.\r\nWhen no argument is passed, the game starts with 5*5 sized maze.\r\nThen you reach the target, a bigger sized maze will be generated and a new game will be started.","package":"hjkl.vim","4":"hjkl.vim","src_id":"19242","5":"19242","creation_date":"1356569627","6":"1356569627"},{"0":"3409","vim_version":"7.0","1":"7.0","script_version":"1.07","2":"1.07","version_comment":"Now does not create new window when current buffer is empty ","3":"Now does not create new window when current buffer is empty ","package":"hjkl.vim","4":"hjkl.vim","src_id":"14961","5":"14961","creation_date":"1296986333","6":"1296986333"},{"0":"3409","vim_version":"7.0","1":"7.0","script_version":"1.06","2":"1.06","version_comment":"Thanks to Xavier Wang's patch! the maze looks better now","3":"Thanks to Xavier Wang's patch! the maze looks better now","package":"hjkl.vim","4":"hjkl.vim","src_id":"14896","5":"14896","creation_date":"1296220007","6":"1296220007"},{"0":"3409","vim_version":"7.0","1":"7.0","script_version":"1.04","2":"1.04","version_comment":"show progress bar when constructing maze \r\nquite game automatically after winning(and press any key)","3":"show progress bar when constructing maze \r\nquite game automatically after winning(and press any key)","package":"hjkl.vim","4":"hjkl.vim","src_id":"14876","5":"14876","creation_date":"1296061685","6":"1296061685"},{"0":"3409","vim_version":"7.0","1":"7.0","script_version":"1.02","2":"1.02","version_comment":"Make \\'@\\' and \\'X\\' bold to make them easy to find.\r\nChange size constrain on maze: depends on the size of vim window now.","3":"Make \\'@\\' and \\'X\\' bold to make them easy to find.\r\nChange size constrain on maze: depends on the size of vim window now.","package":"hjkl.vim","4":"hjkl.vim","src_id":"14821","5":"14821","creation_date":"1295620826","6":"1295620826"},{"0":"3409","vim_version":"7.0","1":"7.0","script_version":"1.01","2":"1.01","version_comment":"Fix a bug in \"konami mode\". \r\nWant Faster? type konami code multiple times !\r\nIt becomes much more tricky when your target gets faster","3":"Fix a bug in \"konami mode\". \r\nWant Faster? type konami code multiple times !\r\nIt becomes much more tricky when your target gets faster","package":"hjkl.vim","4":"hjkl.vim","src_id":"14820","5":"14820","creation_date":"1295614396","6":"1295614396"},{"0":"3409","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Tired of static target?\r\nTry to type vim's konami code(kkjjhlhlba), see what would happen !","3":"Tired of static target?\r\nTry to type vim's konami code(kkjjhlhlba), see what would happen !","package":"hjkl.vim","4":"hjkl.vim","src_id":"14816","5":"14816","creation_date":"1295597501","6":"1295597501"},{"0":"3409","vim_version":"7.0","1":"7.0","script_version":"0.99","2":"0.99","version_comment":"Improved the maze generating algorithm, and now it runs faster(hopefully).","3":"Improved the maze generating algorithm, and now it runs faster(hopefully).","package":"hjkl.vim","4":"hjkl.vim","src_id":"14813","5":"14813","creation_date":"1295578859","6":"1295578859"},{"0":"3409","vim_version":"7.0","1":"7.0","script_version":"0.98","2":"0.98","version_comment":"Simple modification on algorithm, hopefully make the game more challenging","3":"Simple modification on algorithm, hopefully make the game more challenging","package":"hjkl.vim","4":"hjkl.vim","src_id":"14812","5":"14812","creation_date":"1295565657","6":"1295565657"},{"0":"3409","vim_version":"7.0","1":"7.0","script_version":"0.97","2":"0.97","version_comment":"In order to make the game more challenging, more complicated algorithm is used to generate maze, and determine target. However, this slow the script down drastically, especially when generating large maze. If you find it too slow, you may want to use older version(0.96) of the script. \r\nNow the constrain of row is [5,30] and column is [5,40]. Please choose appropriate size according to the size of your vim window and the code's running time you can tolerate. ","3":"In order to make the game more challenging, more complicated algorithm is used to generate maze, and determine target. However, this slow the script down drastically, especially when generating large maze. If you find it too slow, you may want to use older version(0.96) of the script. \r\nNow the constrain of row is [5,30] and column is [5,40]. Please choose appropriate size according to the size of your vim window and the code's running time you can tolerate. ","package":"hjkl.vim","4":"hjkl.vim","src_id":"14810","5":"14810","creation_date":"1295542919","6":"1295542919"},{"0":"3409","vim_version":"7.0","1":"7.0","script_version":"0.96","2":"0.96","version_comment":"Use syntax highlight to make the maze looks better","3":"Use syntax highlight to make the maze looks better","package":"hjkl.vim","4":"hjkl.vim","src_id":"14807","5":"14807","creation_date":"1295508029","6":"1295508029"},{"0":"3409","vim_version":"7.0","1":"7.0","script_version":"0.95","2":"0.95","version_comment":"HJKL command can have 2 arguments: Row and Column, which specify size of maze. Both number should in [5,20]","3":"HJKL command can have 2 arguments: Row and Column, which specify size of maze. Both number should in [5,20]","package":"hjkl.vim","4":"hjkl.vim","src_id":"14806","5":"14806","creation_date":"1295502229","6":"1295502229"},{"0":"3409","vim_version":"7.0","1":"7.0","script_version":"0.93","2":"0.93","version_comment":"Fix a bug: when row number and column number are different, it fails to generate random maze","3":"Fix a bug: when row number and column number are different, it fails to generate random maze","package":"hjkl.vim","4":"hjkl.vim","src_id":"14804","5":"14804","creation_date":"1295496073","6":"1295496073"},{"0":"3409","vim_version":"7.0","1":"7.0","script_version":"0.92","2":"0.92","version_comment":"Remove duplicated \"press any key to continue\"","3":"Remove duplicated \"press any key to continue\"","package":"hjkl.vim","4":"hjkl.vim","src_id":"14801","5":"14801","creation_date":"1295493573","6":"1295493573"},{"0":"3409","vim_version":"7.0","1":"7.0","script_version":"0.91","2":"0.91","version_comment":"change file format to unix","3":"change file format to unix","package":"hjkl.vim","4":"hjkl.vim","src_id":"14799","5":"14799","creation_date":"1295486978","6":"1295486978"},{"0":"3409","vim_version":"7.0","1":"7.0","script_version":"0.9","2":"0.9","version_comment":"Initial upload","3":"Initial upload","package":"hjkl.vim","4":"hjkl.vim","src_id":"14789","5":"14789","creation_date":"1295453581","6":"1295453581"}]},"3408":{"script_id":"3408","0":"3408","script_name":"JellyX","1":"JellyX","script_type":"color scheme","2":"color scheme","summary":"A delicious collision of Jellybeans and Xoria256.","3":"A delicious collision of Jellybeans and Xoria256.","description":"A carefully balanced hybrid of Jellybeans ( vimscript #2555 ) and Xoria256 ( vimscript #2140 ).\r\n\r\nDesigned for 256-color terminals and GUI vim.\r\n\r\nRunning rxvt-unicode? Version 9.10 introduces an official 256-color mode.\r\nRecompile with `configure --enable-256-color` and enjoy.\r\n\r\n\r\n### Github\r\n\r\nhttp:\/\/github.com\/guns\/jellyx.vim\r\n\r\n\r\n### Options\r\n\r\nShow tabs in dark grey, trailing whitespace in dark pink\r\n\r\n    let g:jellyx_show_whitespace = 1\r\n    colorscheme jellyx\r\n\r\n\r\n### Screenshots\r\n\r\nTerm: rxvt-unicode 9.10 with --enable-256-color configure option\r\nFont: Consolas\r\n\r\n * Ruby, with incremental search\r\n   http:\/\/guns.github.com\/jellyx.vim\/images\/ruby.png\r\n\r\n * Sass and CSS, with visual selection\r\n   http:\/\/guns.github.com\/jellyx.vim\/images\/sass-css.png\r\n\r\n * C, with g:jellyx_show_whitespace=1\r\n   http:\/\/guns.github.com\/jellyx.vim\/images\/c-with-whitespace.png\r\n\r\n * VimScript, with folds and completion popup\r\n   http:\/\/guns.github.com\/jellyx.vim\/images\/folds.png\r\n","4":"A carefully balanced hybrid of Jellybeans ( vimscript #2555 ) and Xoria256 ( vimscript #2140 ).\r\n\r\nDesigned for 256-color terminals and GUI vim.\r\n\r\nRunning rxvt-unicode? Version 9.10 introduces an official 256-color mode.\r\nRecompile with `configure --enable-256-color` and enjoy.\r\n\r\n\r\n### Github\r\n\r\nhttp:\/\/github.com\/guns\/jellyx.vim\r\n\r\n\r\n### Options\r\n\r\nShow tabs in dark grey, trailing whitespace in dark pink\r\n\r\n    let g:jellyx_show_whitespace = 1\r\n    colorscheme jellyx\r\n\r\n\r\n### Screenshots\r\n\r\nTerm: rxvt-unicode 9.10 with --enable-256-color configure option\r\nFont: Consolas\r\n\r\n * Ruby, with incremental search\r\n   http:\/\/guns.github.com\/jellyx.vim\/images\/ruby.png\r\n\r\n * Sass and CSS, with visual selection\r\n   http:\/\/guns.github.com\/jellyx.vim\/images\/sass-css.png\r\n\r\n * C, with g:jellyx_show_whitespace=1\r\n   http:\/\/guns.github.com\/jellyx.vim\/images\/c-with-whitespace.png\r\n\r\n * VimScript, with folds and completion popup\r\n   http:\/\/guns.github.com\/jellyx.vim\/images\/folds.png\r\n","install_details":"","5":"","first_name":"Sung","6":"Sung","last_name":"Pae","7":"Pae","releases":[{"0":"3408","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"jellyx.vim.tar.gz","4":"jellyx.vim.tar.gz","src_id":"14787","5":"14787","creation_date":"1295440694","6":"1295440694"}]},"3407":{"script_id":"3407","0":"3407","script_name":"headerGatesAdd.vim","1":"headerGatesAdd.vim","script_type":"utility","2":"utility","summary":"automatic inser C\/C++ header gates","3":"automatic inser C\/C++ header gates","description":"C\/C++ header files should be guarded against multiple inclusions using preprocessor directives, e.g.:\r\nlet g:HeaderGatesAdd_suffix=\"_H\"   is default  \r\n1.\r\nfoo_n.h  or  FooN.h  or  foo n.h  ...\r\n#ifndef FOO_N_H\r\n#define FOO_N_H\r\n\r\n#endif   \/*FOO_N_H*\/\r\n\r\nif you set  let g:HeaderGatesAdd_suffix=\"__\"\r\nit could be   FOO_N__\r\n2.\r\nif add let g:insert_extern_c_flag=1 in .vimrc or _vimrc\r\nwhen you create a new file name foo_h.h  it look like this:\r\n#ifndef FOO_N_H\r\n#define FOO_N_H\r\n\r\n#ifdef __cplusplus\r\nextern \"C\" {\r\n#endif\r\n\r\n\r\n#ifdef __cplusplus\r\n}\r\n#endif\r\n\r\n#endif  \/*FOO_N_H*\/\r\n\r\n3.\r\n:HeaderGatesAdd\r\nthis command will change \r\n\/**\r\n * @file        foo_n.h\r\n * @version     0.1.00\r\n *\/\r\n\r\nvoid test();\r\n\r\nto:\r\n\/**\r\n * @file        foo_n.h\r\n * @version     0.1.00\r\n *\/\r\n#ifndef FOO_N_H\r\n#define FOO_N_H\r\n\r\n#ifdef __cplusplus\r\nextern \"C\" {\r\n#endif\r\n\r\nvoid test();\r\n\r\n#ifdef __cplusplus\r\n}\r\n#endif\r\n\r\n#endif  \/*FOO_N_H*\/\r\n\r\n4.\r\nlet g:HeaderGatesAdd_prefix=\"__\"    \r\nfoo_n.h ---------> __FOO_N\r\n5.\r\nlet g:HeaderGatesAdd_suffix=\"_SUFFIX\"\r\nfoo_n.h ---------> FOO_N_SUFFIX\r\n\r\n6.\r\nin case of suffix and prefix both null:\r\nlet g:HeaderGatesAdd_gate_type=0 is default\r\naTestFile.h  ---------> A_TEST_FILE\r\n\r\nlet g:HeaderGatesAdd_gate_type=1\r\naTestFile.h  ---------> ATESTFILE\r\n\r\nlet g:HeaderGatesAdd_gate_type=2\r\naTestFile.h  --------->aTestFile\r\n\r\nmay be you have other style,  u can send email to me.\r\nversion 1.4 do not require python support\r\nthe end please forgive my poor english","4":"C\/C++ header files should be guarded against multiple inclusions using preprocessor directives, e.g.:\r\nlet g:HeaderGatesAdd_suffix=\"_H\"   is default  \r\n1.\r\nfoo_n.h  or  FooN.h  or  foo n.h  ...\r\n#ifndef FOO_N_H\r\n#define FOO_N_H\r\n\r\n#endif   \/*FOO_N_H*\/\r\n\r\nif you set  let g:HeaderGatesAdd_suffix=\"__\"\r\nit could be   FOO_N__\r\n2.\r\nif add let g:insert_extern_c_flag=1 in .vimrc or _vimrc\r\nwhen you create a new file name foo_h.h  it look like this:\r\n#ifndef FOO_N_H\r\n#define FOO_N_H\r\n\r\n#ifdef __cplusplus\r\nextern \"C\" {\r\n#endif\r\n\r\n\r\n#ifdef __cplusplus\r\n}\r\n#endif\r\n\r\n#endif  \/*FOO_N_H*\/\r\n\r\n3.\r\n:HeaderGatesAdd\r\nthis command will change \r\n\/**\r\n * @file        foo_n.h\r\n * @version     0.1.00\r\n *\/\r\n\r\nvoid test();\r\n\r\nto:\r\n\/**\r\n * @file        foo_n.h\r\n * @version     0.1.00\r\n *\/\r\n#ifndef FOO_N_H\r\n#define FOO_N_H\r\n\r\n#ifdef __cplusplus\r\nextern \"C\" {\r\n#endif\r\n\r\nvoid test();\r\n\r\n#ifdef __cplusplus\r\n}\r\n#endif\r\n\r\n#endif  \/*FOO_N_H*\/\r\n\r\n4.\r\nlet g:HeaderGatesAdd_prefix=\"__\"    \r\nfoo_n.h ---------> __FOO_N\r\n5.\r\nlet g:HeaderGatesAdd_suffix=\"_SUFFIX\"\r\nfoo_n.h ---------> FOO_N_SUFFIX\r\n\r\n6.\r\nin case of suffix and prefix both null:\r\nlet g:HeaderGatesAdd_gate_type=0 is default\r\naTestFile.h  ---------> A_TEST_FILE\r\n\r\nlet g:HeaderGatesAdd_gate_type=1\r\naTestFile.h  ---------> ATESTFILE\r\n\r\nlet g:HeaderGatesAdd_gate_type=2\r\naTestFile.h  --------->aTestFile\r\n\r\nmay be you have other style,  u can send email to me.\r\nversion 1.4 do not require python support\r\nthe end please forgive my poor english","install_details":"1.Using [Vundle.vim](Recommend):~\r\n    https:\/\/github.com\/gmarik\/vundle\r\n    After installed vundle and git. Add this line to your vimrc  \r\n    Bundle `'tczengming\/headerGatesAdd.vim'`\r\n    Run `:BundleInstall` to install.\r\n    And update them easily by `:BundleInstall!`\r\n2.\r\n   Copy the script file into to the plugin directory of Vimfiles, such as ~\/.vim\/plugin\/ ","5":"1.Using [Vundle.vim](Recommend):~\r\n    https:\/\/github.com\/gmarik\/vundle\r\n    After installed vundle and git. Add this line to your vimrc  \r\n    Bundle `'tczengming\/headerGatesAdd.vim'`\r\n    Run `:BundleInstall` to install.\r\n    And update them easily by `:BundleInstall!`\r\n2.\r\n   Copy the script file into to the plugin directory of Vimfiles, such as ~\/.vim\/plugin\/ ","first_name":"\u5e05","6":"帅","last_name":"\u5f97\u4e0d\u6562\u51fa\u95e8","7":"得不敢出门","releases":[{"0":"3407","vim_version":"7.0","1":"7.0","script_version":"1.4","2":"1.4","version_comment":"rewrite with pure vim script, do not require python support, test with vim7.3 , perhaps also work with vim6.","3":"rewrite with pure vim script, do not require python support, test with vim7.3 , perhaps also work with vim6.","package":"headerGatesAdd.vim","4":"headerGatesAdd.vim","src_id":"19167","5":"19167","creation_date":"1355277274","6":"1355277274"},{"0":"3407","vim_version":"7.0","1":"7.0","script_version":"1.3","2":"1.3","version_comment":"skip c\/c++  remarked code block and empty line, then auto insert header gates.","3":"skip c\/c++  remarked code block and empty line, then auto insert header gates.","package":"headerGatesAdd.vim","4":"headerGatesAdd.vim","src_id":"17364","5":"17364","creation_date":"1328151376","6":"1328151376"},{"0":"3407","vim_version":"7.0","1":"7.0","script_version":"1.2","2":"1.2","version_comment":"add   let g:HeaderGatesAdd_gate_type\r\nand  default   let g:HeaderGatesAdd_suffix=\"_H\"   ","3":"add   let g:HeaderGatesAdd_gate_type\r\nand  default   let g:HeaderGatesAdd_suffix=\"_H\"   ","package":"headerGatesAdd.vim","4":"headerGatesAdd.vim","src_id":"14800","5":"14800","creation_date":"1295487054","6":"1295487054"},{"0":"3407","vim_version":"7.0","1":"7.0","script_version":"1.1","2":"1.1","version_comment":"add   g:HeaderGatesAdd_prefix    g:HeaderGatesAdd_suffix","3":"add   g:HeaderGatesAdd_prefix    g:HeaderGatesAdd_suffix","package":"headerGatesAdd.vim","4":"headerGatesAdd.vim","src_id":"14786","5":"14786","creation_date":"1295432511","6":"1295432511"},{"0":"3407","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"headerGatesAdd.vim","4":"headerGatesAdd.vim","src_id":"14785","5":"14785","creation_date":"1295429249","6":"1295429249"}]},"3406":{"script_id":"3406","0":"3406","script_name":"update_perl_line_directives","1":"update_perl_line_directives","script_type":"ftplugin","2":"ftplugin","summary":"automatically add\/update line directives in perl embedded in vim scripts","3":"automatically add\/update line directives in perl embedded in vim scripts","description":"WARNING: if your vim links to (or dlopen()'s) a libperl earlier than 5.12, perl may end up lying to you about the line number by one (or maybe more, but one is what I've seen).\r\n\r\nThis script eases development of vim scripts that use embedded perl code by automatically adding or updating line directives to perl code blocks.  So for example:\r\n\r\n     perl <<EOF\r\n\r\nwill automagically become\r\n\r\n     perl <<EOF\r\n     # line 42 \/some\/file.vim\r\n\r\nwhen you save \/some\/file.vim.  You can use other valid here-document terminators, not just 'EOF'.\r\n\r\nNow your error messages that come from perl will have correct file names and line numbers.\r\n\r\nSee also http:\/\/www.vim.org\/scripts\/script.php?script_id=3411 if you want to automatically catch perl syntax errors when vim scripts are saved.","4":"WARNING: if your vim links to (or dlopen()'s) a libperl earlier than 5.12, perl may end up lying to you about the line number by one (or maybe more, but one is what I've seen).\r\n\r\nThis script eases development of vim scripts that use embedded perl code by automatically adding or updating line directives to perl code blocks.  So for example:\r\n\r\n     perl <<EOF\r\n\r\nwill automagically become\r\n\r\n     perl <<EOF\r\n     # line 42 \/some\/file.vim\r\n\r\nwhen you save \/some\/file.vim.  You can use other valid here-document terminators, not just 'EOF'.\r\n\r\nNow your error messages that come from perl will have correct file names and line numbers.\r\n\r\nSee also http:\/\/www.vim.org\/scripts\/script.php?script_id=3411 if you want to automatically catch perl syntax errors when vim scripts are saved.","install_details":"Its a standard vimball so all you need to do is:\r\n\r\n     vim update_perl_line_directives.vba\r\n     :so %","5":"Its a standard vimball so all you need to do is:\r\n\r\n     vim update_perl_line_directives.vba\r\n     :so %","first_name":"Britton","6":"Britton","last_name":"Kerin","7":"Kerin","releases":[{"0":"3406","vim_version":"7.0","1":"7.0","script_version":"0.3","2":"0.3","version_comment":"Fixed bug which caused last line of files to get nuked","3":"Fixed bug which caused last line of files to get nuked","package":"update_perl_line_directives.vba","4":"update_perl_line_directives.vba","src_id":"14931","5":"14931","creation_date":"1296515036","6":"1296515036"},{"0":"3406","vim_version":"7.0","1":"7.0","script_version":"0.2","2":"0.2","version_comment":"Fixed off-by-one error in line number settings","3":"Fixed off-by-one error in line number settings","package":"update_perl_line_directives.vba","4":"update_perl_line_directives.vba","src_id":"14796","5":"14796","creation_date":"1295478913","6":"1295478913"},{"0":"3406","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"update_perl_line_directives.vba","4":"update_perl_line_directives.vba","src_id":"14784","5":"14784","creation_date":"1295398048","6":"1295398048"}]},"3405":{"script_id":"3405","0":"3405","script_name":"auto-kk","1":"auto-kk","script_type":"utility","2":"utility","summary":"from auto.vim","3":"from auto.vim","description":"1.Normal mode\r\n    <c-e>   to compile and debug\r\n    <c-f> search clipboard\r\n    <c-z> undo\r\n2.Insert mode\r\n    <c-z> undo\r\n    <c-e>   to compile and debug\r\n    <Alt-j>  Down\r\n    <Alt-k> Up\r\n    <Alt-h> Left\r\n    <Alt-l>  Right\r\n3.When writing c, cpp ,... code, the code is automatically formatted\r\n    For example:   If you input a==3;\r\n    auto.vim                             a  ==  3;\r\n4.Both ruby , c, cpp, python,shell,perl code, F2 key or \"mm\" to compile and debug\r\n\r\nmodify from this: \r\nhttp:\/\/www.vim.org\/scripts\/script.php?script_id=3341\r\n","4":"1.Normal mode\r\n    <c-e>   to compile and debug\r\n    <c-f> search clipboard\r\n    <c-z> undo\r\n2.Insert mode\r\n    <c-z> undo\r\n    <c-e>   to compile and debug\r\n    <Alt-j>  Down\r\n    <Alt-k> Up\r\n    <Alt-h> Left\r\n    <Alt-l>  Right\r\n3.When writing c, cpp ,... code, the code is automatically formatted\r\n    For example:   If you input a==3;\r\n    auto.vim                             a  ==  3;\r\n4.Both ruby , c, cpp, python,shell,perl code, F2 key or \"mm\" to compile and debug\r\n\r\nmodify from this: \r\nhttp:\/\/www.vim.org\/scripts\/script.php?script_id=3341\r\n","install_details":"copy to  plugin\/","5":"copy to  plugin\/","first_name":"sevk","6":"sevk","last_name":"k","7":"k","releases":[{"0":"3405","vim_version":"7.3","1":"7.3","script_version":"1.3","2":"1.3","version_comment":"like c-support \r\n\\\\r","3":"like c-support \r\n\\\\r","package":"auto-kk.vim","4":"auto-kk.vim","src_id":"17754","5":"17754","creation_date":"1334135668","6":"1334135668"}]},"3404":{"script_id":"3404","0":"3404","script_name":"Google translator","1":"Google translator","script_type":"utility","2":"utility","summary":"Ajax Google translator","3":"Ajax Google translator","description":"This plugin allow translate text in vim using google translator.\r\nYou may translate both single words and whole blocks using visual mode.\r\n\r\nMore details on github.\r\nLatest version is located on github (https:\/\/github.com\/maksimr\/vim-translator).\r\nMaksim.\r\n","4":"This plugin allow translate text in vim using google translator.\r\nYou may translate both single words and whole blocks using visual mode.\r\n\r\nMore details on github.\r\nLatest version is located on github (https:\/\/github.com\/maksimr\/vim-translator).\r\nMaksim.\r\n","install_details":"","5":"","first_name":"Maksim","6":"Maksim","last_name":"Ryzhikov","7":"Ryzhikov","releases":[{"0":"3404","vim_version":"7.3","1":"7.3","script_version":"1.3.1b","2":"1.3.1b","version_comment":"Fix some problem with encoding. add support javascript and lua languages.\r\nThis file includes only ruby support.","3":"Fix some problem with encoding. add support javascript and lua languages.\r\nThis file includes only ruby support.","package":"goog-translator.vim","4":"goog-translator.vim","src_id":"16860","5":"16860","creation_date":"1321194546","6":"1321194546"},{"0":"3404","vim_version":"7.3","1":"7.3","script_version":"1.3.0b","2":"1.3.0b","version_comment":"Remove json dependency, remove variable g:vtranslate, g:langpair, change url for request.\r\nAdd configuration variable, example: let g:goog_user_conf = {'langpair'  :  'en|ru', 'v_key'  :  'T',  'charset' : 'koi8-r' }\r\nProblem with large text and quotes.","3":"Remove json dependency, remove variable g:vtranslate, g:langpair, change url for request.\r\nAdd configuration variable, example: let g:goog_user_conf = {'langpair'  :  'en|ru', 'v_key'  :  'T',  'charset' : 'koi8-r' }\r\nProblem with large text and quotes.","package":"goog-translator.vim","4":"goog-translator.vim","src_id":"16776","5":"16776","creation_date":"1320096510","6":"1320096510"},{"0":"3404","vim_version":"7.2","1":"7.2","script_version":"1.2.6","2":"1.2.6","version_comment":"fixed: translate of large text","3":"fixed: translate of large text","package":"gtranslate.vim","4":"gtranslate.vim","src_id":"15571","5":"15571","creation_date":"1304368820","6":"1304368820"},{"0":"3404","vim_version":"7.2","1":"7.2","script_version":"1.2.4","2":"1.2.4","version_comment":"small fix (bug with gsub)","3":"small fix (bug with gsub)","package":"gtranslate.vim","4":"gtranslate.vim","src_id":"15415","5":"15415","creation_date":"1302298634","6":"1302298634"},{"0":"3404","vim_version":"7.2","1":"7.2","script_version":"1.2.3","2":"1.2.3","version_comment":"Fix bug  \"Request-URI Too Large\"\r\nAdded possibility to change the color translate text","3":"Fix bug  \"Request-URI Too Large\"\r\nAdded possibility to change the color translate text","package":"gtranslate.vim","4":"gtranslate.vim","src_id":"14841","5":"14841","creation_date":"1295828168","6":"1295828168"},{"0":"3404","vim_version":"7.2","1":"7.2","script_version":"1.21b","2":"1.21b","version_comment":"New implementation of the translation of the selected block of text.\r\nadd ruby require CGI.","3":"New implementation of the translation of the selected block of text.\r\nadd ruby require CGI.","package":"gtranslate.vim","4":"gtranslate.vim","src_id":"14831","5":"14831","creation_date":"1295739822","6":"1295739822"},{"0":"3404","vim_version":"7.2","1":"7.2","script_version":"1.1","2":"1.1","version_comment":"Added auto-completion","3":"Added auto-completion","package":"gtranslate.vim","4":"gtranslate.vim","src_id":"14808","5":"14808","creation_date":"1295526401","6":"1295526401"},{"0":"3404","vim_version":"7.2","1":"7.2","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"gtranslate.vim","4":"gtranslate.vim","src_id":"14753","5":"14753","creation_date":"1295090605","6":"1295090605"}]},"3403":{"script_id":"3403","0":"3403","script_name":"mophiaDark","1":"mophiaDark","script_type":"color scheme","2":"color scheme","summary":"A dark background color scheme","3":"A dark background color scheme","description":"This is a dark greenish colorscheme for gvim. I tried to keep the contrast to eye pleasing level.","4":"This is a dark greenish colorscheme for gvim. I tried to keep the contrast to eye pleasing level.","install_details":"copy to ~\/.vim\/colors\/\r\n:colorscheme mophiaDark","5":"copy to ~\/.vim\/colors\/\r\n:colorscheme mophiaDark","first_name":"Om","6":"Om","last_name":"Narasimhan","7":"Narasimhan","releases":[{"0":"3403","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"mophiaDark.vim","4":"mophiaDark.vim","src_id":"14751","5":"14751","creation_date":"1295071041","6":"1295071041"}]},"3402":{"script_id":"3402","0":"3402","script_name":"mophiaSmoke","1":"mophiaSmoke","script_type":"color scheme","2":"color scheme","summary":"A light background color scheme","3":"A light background color scheme","description":"I have created this script from scratch. I hope this blue tinted scheme is easy on everybody's eyes. ","4":"I have created this script from scratch. I hope this blue tinted scheme is easy on everybody's eyes. ","install_details":"copy to ~\/.vim\/colors\r\n:colorscheme mophiaSmoke","5":"copy to ~\/.vim\/colors\r\n:colorscheme mophiaSmoke","first_name":"Om","6":"Om","last_name":"Narasimhan","7":"Narasimhan","releases":[{"0":"3402","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"mophiaSmoke.vim","4":"mophiaSmoke.vim","src_id":"14750","5":"14750","creation_date":"1295070787","6":"1295070787"}]},"3401":{"script_id":"3401","0":"3401","script_name":"Search Google","1":"Search Google","script_type":"utility","2":"utility","summary":"Open default webbrowser and search word in current cursor position with google.","3":"Open default webbrowser and search word in current cursor position with google.","description":"Put the cursor at any position of a word, and type :Google command, you can search it with google! Enjoy It.","4":"Put the cursor at any position of a word, and type :Google command, you can search it with google! Enjoy It.","install_details":"","5":"","first_name":"Kevin","6":"Kevin","last_name":"Xiao","7":"Xiao","releases":[{"0":"3401","vim_version":"7.3","1":"7.3","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"googlesearch.vim","4":"googlesearch.vim","src_id":"14733","5":"14733","creation_date":"1294804632","6":"1294804632"}]},"3400":{"script_id":"3400","0":"3400","script_name":"vim-creole","1":"vim-creole","script_type":"syntax","2":"syntax","summary":"Creole wiki syntax","3":"Creole wiki syntax","description":"This works better (in my point of view) that the existing one by Peter Hoffmann (vimscript#1909) when running on the test from http:\/\/www.wikicreole.org\/wiki\/Creole1.0TestCases\r\n\r\nRepository and bug tracker can be found here: https:\/\/bitbucket.org\/shellholic\/vim-creole","4":"This works better (in my point of view) that the existing one by Peter Hoffmann (vimscript#1909) when running on the test from http:\/\/www.wikicreole.org\/wiki\/Creole1.0TestCases\r\n\r\nRepository and bug tracker can be found here: https:\/\/bitbucket.org\/shellholic\/vim-creole","install_details":"","5":"","first_name":"shellholic","6":"shellholic","last_name":" ","7":" ","releases":[{"0":"3400","vim_version":"7.0","1":"7.0","script_version":"0.0.3","2":"0.0.3","version_comment":"Transplanted patches from https:\/\/bitbucket.org\/zombiezen\/vim-creole:\r\n* added zombiezen to contributors\r\n* factoring\r\n* syntax guard\r\n\r\nOther changes:\r\n* CamelCase support\r\n* better support for mix of bold, italics and url\r\n* https support","3":"Transplanted patches from https:\/\/bitbucket.org\/zombiezen\/vim-creole:\r\n* added zombiezen to contributors\r\n* factoring\r\n* syntax guard\r\n\r\nOther changes:\r\n* CamelCase support\r\n* better support for mix of bold, italics and url\r\n* https support","package":"vim-creole-0.0.3.zip","4":"vim-creole-0.0.3.zip","src_id":"16035","5":"16035","creation_date":"1309901598","6":"1309901598"},{"0":"3400","vim_version":"7.0","1":"7.0","script_version":"0.0.2","2":"0.0.2","version_comment":"include http:\/\/www.wikicreole.org\/wiki\/CreoleAdditions","3":"include http:\/\/www.wikicreole.org\/wiki\/CreoleAdditions","package":"vim-creole-0.0.2.zip","4":"vim-creole-0.0.2.zip","src_id":"14732","5":"14732","creation_date":"1294779418","6":"1294779418"},{"0":"3400","vim_version":"7.0","1":"7.0","script_version":"0.0.1","2":"0.0.1","version_comment":"Initial upload","3":"Initial upload","package":"vim-creole-509c5cae0466.zip","4":"vim-creole-509c5cae0466.zip","src_id":"14731","5":"14731","creation_date":"1294774858","6":"1294774858"}]},"3399":{"script_id":"3399","0":"3399","script_name":"phpunit","1":"phpunit","script_type":"utility","2":"utility","summary":"Plugin to run phpunit test inside vim","3":"Plugin to run phpunit test inside vim","description":"USAGE\r\n------------\r\n\r\nScript provide three command\r\n\r\n:PhpUnit [path]\r\n\r\nrun phpunit with path. Path is not manadatory. If Path is not defined it vim-phpunit use <g:phpunit_tests> variable\r\n\r\n:PhpUnitSwitchFile\r\n\r\nOpen testfile for current file. Name of testfile is taken from curent path in following way:\r\n<g:phpunit_testroot>\/<current path>\/<file name>Test.php\r\nand vice versa for testing file (if you are on test file, it will open source file complementary to testfile)\r\n\r\nversion 0.1 doesn't care about path existence - it's your responsibility\r\n(maybe in next version)\r\n\r\n:PhpUnitFile\r\n\r\nrun phpunit for current file. There is heuristic like :PhpUnitSwitchFile\r\neg. \r\n[file] dir\/file.php => [test] <g:phpunit_testroot>\/dir\/fileTest\r\n[file] <g:phpunit_testroot>\/dir\/fileTest => [test] <g:phpunit_testroot>\/dir\/fileTest\r\n\r\nKEYMAPPING\r\n-----------------------\r\n\r\n<Leader>t   :PhpUnit                           \" hint: test\r\n<Leader>tf  :PhpUnitFile                      \" hint: test file\r\n<Leader>ts :PhpUnitSwitchFile            \" hint: test swich (swap)\r\n\r\n\r\nHOMEPAGE\r\n------------------- \r\nhttps:\/\/github.com\/klokane\/vim-phpunit\r\n\r\n\r\nYour suggestions are welcomed (best way: issue request tracker on github)\r\n\r\n","4":"USAGE\r\n------------\r\n\r\nScript provide three command\r\n\r\n:PhpUnit [path]\r\n\r\nrun phpunit with path. Path is not manadatory. If Path is not defined it vim-phpunit use <g:phpunit_tests> variable\r\n\r\n:PhpUnitSwitchFile\r\n\r\nOpen testfile for current file. Name of testfile is taken from curent path in following way:\r\n<g:phpunit_testroot>\/<current path>\/<file name>Test.php\r\nand vice versa for testing file (if you are on test file, it will open source file complementary to testfile)\r\n\r\nversion 0.1 doesn't care about path existence - it's your responsibility\r\n(maybe in next version)\r\n\r\n:PhpUnitFile\r\n\r\nrun phpunit for current file. There is heuristic like :PhpUnitSwitchFile\r\neg. \r\n[file] dir\/file.php => [test] <g:phpunit_testroot>\/dir\/fileTest\r\n[file] <g:phpunit_testroot>\/dir\/fileTest => [test] <g:phpunit_testroot>\/dir\/fileTest\r\n\r\nKEYMAPPING\r\n-----------------------\r\n\r\n<Leader>t   :PhpUnit                           \" hint: test\r\n<Leader>tf  :PhpUnitFile                      \" hint: test file\r\n<Leader>ts :PhpUnitSwitchFile            \" hint: test swich (swap)\r\n\r\n\r\nHOMEPAGE\r\n------------------- \r\nhttps:\/\/github.com\/klokane\/vim-phpunit\r\n\r\n\r\nYour suggestions are welcomed (best way: issue request tracker on github)\r\n\r\n","install_details":"just save into you plugins directory","5":"just save into you plugins directory","first_name":"Jiri","6":"Jiri","last_name":"Kratochvil","7":"Kratochvil","releases":[{"0":"3399","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"phpunit.vim","4":"phpunit.vim","src_id":"14722","5":"14722","creation_date":"1294661568","6":"1294661568"}]},"3398":{"script_id":"3398","0":"3398","script_name":"fokus","1":"fokus","script_type":"color scheme","2":"color scheme","summary":"Light color scheme designed for Ruby programming","3":"Light color scheme designed for Ruby programming","description":"Colorful scheme with light background, shamelessly edited from 'fruit'. Also includes some custom PHP style because I had to look at php files from time to time.\r\n\r\nScreenshot showing a ruby file and NERDTree:\r\nhttp:\/\/img716.imageshack.us\/img716\/8144\/screenshotstreamscontro.png","4":"Colorful scheme with light background, shamelessly edited from 'fruit'. Also includes some custom PHP style because I had to look at php files from time to time.\r\n\r\nScreenshot showing a ruby file and NERDTree:\r\nhttp:\/\/img716.imageshack.us\/img716\/8144\/screenshotstreamscontro.png","install_details":"Place fokus.vim in your colors directory at ~\/.vim\/colors. Add the following lines to your ~\/.vimrc file to use this colorscheme by default on startup:\r\n\r\n:syntax on\r\n:colorscheme fokus \r\n\r\nIf you're coding PHP too, you may also have to put this on your .vimrc so the custom style would look as intended:\r\n\r\nautocmd FileType php so ~\/.vim\/colors\/fokus.vim\r\n","5":"Place fokus.vim in your colors directory at ~\/.vim\/colors. Add the following lines to your ~\/.vimrc file to use this colorscheme by default on startup:\r\n\r\n:syntax on\r\n:colorscheme fokus \r\n\r\nIf you're coding PHP too, you may also have to put this on your .vimrc so the custom style would look as intended:\r\n\r\nautocmd FileType php so ~\/.vim\/colors\/fokus.vim\r\n","first_name":"Mohammad","6":"Mohammad","last_name":"Satrio","7":"Satrio","releases":[{"0":"3398","vim_version":"7.2","1":"7.2","script_version":"0.3","2":"0.3","version_comment":"Darker hue for a few foreground colors, updates for directory tree, ruby regex, cucumber, and PHP.","3":"Darker hue for a few foreground colors, updates for directory tree, ruby regex, cucumber, and PHP.","package":"fokus.vim","4":"fokus.vim","src_id":"14986","5":"14986","creation_date":"1297171654","6":"1297171654"},{"0":"3398","vim_version":"7.2","1":"7.2","script_version":"0.2","2":"0.2","version_comment":"Initial upload","3":"Initial upload","package":"fokus.vim","4":"fokus.vim","src_id":"14720","5":"14720","creation_date":"1294650883","6":"1294650883"}]},"3397":{"script_id":"3397","0":"3397","script_name":"neverland.vim - All colorschemes suck","1":"neverland.vim - All colorschemes suck","script_type":"color scheme","2":"color scheme","summary":"256 colors, CLI and GUI","3":"256 colors, CLI and GUI","description":"Screenshot: http:\/\/perl.japh.se\/devel\/neverland-vim-theme\/neverland.png\r\n\r\nTheme pack with various variations of the Neverland vim colorscheme.\r\n\r\nTerminal (256 colors) and gVim.\r\n","4":"Screenshot: http:\/\/perl.japh.se\/devel\/neverland-vim-theme\/neverland.png\r\n\r\nTheme pack with various variations of the Neverland vim colorscheme.\r\n\r\nTerminal (256 colors) and gVim.\r\n","install_details":"Get the latest versions here: https:\/\/github.com\/trapd00r\/neverland-vim-theme\r\n\r\ncp colors\/* $HOME\/.vim\/colors","5":"Get the latest versions here: https:\/\/github.com\/trapd00r\/neverland-vim-theme\r\n\r\ncp colors\/* $HOME\/.vim\/colors","first_name":"Magnus","6":"Magnus","last_name":"Woldrich","7":"Woldrich","releases":[{"0":"3397","vim_version":"7.0","1":"7.0","script_version":"2.0","2":"2.0","version_comment":"gVim support added to all colorschemes; thank you Sam Lidder.","3":"gVim support added to all colorschemes; thank you Sam Lidder.","package":"neverland-vim-theme.tar.gz","4":"neverland-vim-theme.tar.gz","src_id":"14752","5":"14752","creation_date":"1295076468","6":"1295076468"},{"0":"3397","vim_version":"7.0","1":"7.0","script_version":"1.10","2":"1.10","version_comment":"* 4118b8d - (HEAD, origin\/master, master) update README\r\nneverland.vim: added gvim support patch by stack_underflow\r\n Fixed some issues with :set background, thanks to Kevin Goodsell\r\n","3":"* 4118b8d - (HEAD, origin\/master, master) update README\r\nneverland.vim: added gvim support patch by stack_underflow\r\n Fixed some issues with :set background, thanks to Kevin Goodsell\r\n","package":"neverland-vim-theme.tar.gz","4":"neverland-vim-theme.tar.gz","src_id":"14734","5":"14734","creation_date":"1294818617","6":"1294818617"},{"0":"3397","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"neverland-vim-theme.tar.gz","4":"neverland-vim-theme.tar.gz","src_id":"14719","5":"14719","creation_date":"1294645933","6":"1294645933"}]},"3396":{"script_id":"3396","0":"3396","script_name":"unite.vim","1":"unite.vim","script_type":"utility","2":"utility","summary":"Unite and create user interfaces","3":"Unite and create user interfaces","description":"## Description\r\n\r\nThe unite or unite.vim plug-in can search and display information from\r\narbitrary sources like files, buffers, recently used files or registers.  You\r\ncan run several pre-defined actions on a target displayed in the unite window.\r\n\r\nThe difference between unite and similar plug-ins like fuzzyfinder,\r\nctrl-p or ku is, unite provides an integration interface for several\r\nsources and you can create new interface using unite.\r\n\r\n## Usage\r\n\r\nIn case you run unite to display files and buffers as sources to pick\r\nfrom.\r\n\r\n\t:Unite file buffer\r\n\r\n\r\nIn case you run unite with an initial filter value (foo) to narrow\r\ndown files.\r\n\r\n\t:Unite -input=foo file\r\n\r\n\r\nIf you start unite it splits the window horizontally and pops up\r\nfrom the top of Vim by default. \r\n\r\n\t:Unite file\r\n\r\nThe example call above lists all the files in the current directory. You can\r\nchoose one of them in the in the unite window by moving the cursor up and down\r\nas usual with j and k. If you type Enter on an active candidate it will open\r\nit in a new buffer. Enter triggers the default action for a candidate which is\r\n\"open\" for candidates of the kind \"file\". You can also select an alternative\r\naction for a candidate with <Tab>. See also `unite-action` to read on about\r\nactions.\r\n\r\nYou can also narrow down the list of candidates by a keyword. If you change\r\ninto the insert mode inside of a unite window, the cursor drops you behind the\r\n\">\" in the second line from above. There you can start typing to filter the\r\ncandidates.  You can also use the wild card \"*\" as an arbitrary character\r\nsequence. For example, \r\n\r\n\t*hisa\r\n\r\nmatches hisa, ujihisa, or ujihisahisa. Furthermore, two consecutive wild cards\r\nmatch a directory recursively. \r\n\r\n\t**\/foo\r\n\r\nSo the example above matches bar\/foo or buzz\/bar\/foo.\r\nNote: The unite action `file_rec` does a recursive file matching by default\r\nwithout the need to set wildcards.\r\n\r\nYou can also specify multiple keywords to narrow down the candidates. Multiple\r\nkeywords need to be separated either by a space \" \" or a dash \"|\". The\r\nexamples below match for candidates that meet both conditions \"foo\" and \"bar\".\r\n\r\n\tfoo bar\r\n\tfoo|bar\r\n\r\nYou can also specify negative conditions with an exclamation mark \"!\".  This\r\nmatches candidates that meet \"foo\" but do not meet \"bar\".\r\n\r\n\tfoo !bar\r\n\r\nWild cards are added automatically if you add a \"\/\" in the filter and you have\r\nspecified \"files\" as the buffer name with the option \"-buffer-name\". That's\r\nhandy in case you select files with unite.\r\n\r\n\t:Unite -buffer-name=files file\r\n\r\nSee also `unite_default_key_mappings` for other actions.\r\n\r\nThere is also a screencast available which shows unite in action. Thanks to\r\nujihisa! http:\/\/www.ustream.tv\/recorded\/11240673\r\n\r\n## Install details\r\n\r\nInstall the distributed files into your Vim script directory which is usually\r\n`~\/.vim\/`, or `$HOME\/vimfiles` on Windows. You should consider to use one of the\r\nfamous package managers for Vim like vundle or neobundle to install the\r\nplugin.\r\n\r\nAfter installation you can run unite with the `:Unite` command and append the\r\nsources to the command you wish to select from as parameters. However, it's a\r\npain in the ass to run the command explicitly every time, so I recommend you\r\nto set a key mapping for the command. See `:h unite`.\r\n\r\n## Links\r\n\r\nunite plugins(in Japanese): https:\/\/github.com\/Shougo\/unite.vim\/wiki\/unite-plugins","4":"## Description\r\n\r\nThe unite or unite.vim plug-in can search and display information from\r\narbitrary sources like files, buffers, recently used files or registers.  You\r\ncan run several pre-defined actions on a target displayed in the unite window.\r\n\r\nThe difference between unite and similar plug-ins like fuzzyfinder,\r\nctrl-p or ku is, unite provides an integration interface for several\r\nsources and you can create new interface using unite.\r\n\r\n## Usage\r\n\r\nIn case you run unite to display files and buffers as sources to pick\r\nfrom.\r\n\r\n\t:Unite file buffer\r\n\r\n\r\nIn case you run unite with an initial filter value (foo) to narrow\r\ndown files.\r\n\r\n\t:Unite -input=foo file\r\n\r\n\r\nIf you start unite it splits the window horizontally and pops up\r\nfrom the top of Vim by default. \r\n\r\n\t:Unite file\r\n\r\nThe example call above lists all the files in the current directory. You can\r\nchoose one of them in the in the unite window by moving the cursor up and down\r\nas usual with j and k. If you type Enter on an active candidate it will open\r\nit in a new buffer. Enter triggers the default action for a candidate which is\r\n\"open\" for candidates of the kind \"file\". You can also select an alternative\r\naction for a candidate with <Tab>. See also `unite-action` to read on about\r\nactions.\r\n\r\nYou can also narrow down the list of candidates by a keyword. If you change\r\ninto the insert mode inside of a unite window, the cursor drops you behind the\r\n\">\" in the second line from above. There you can start typing to filter the\r\ncandidates.  You can also use the wild card \"*\" as an arbitrary character\r\nsequence. For example, \r\n\r\n\t*hisa\r\n\r\nmatches hisa, ujihisa, or ujihisahisa. Furthermore, two consecutive wild cards\r\nmatch a directory recursively. \r\n\r\n\t**\/foo\r\n\r\nSo the example above matches bar\/foo or buzz\/bar\/foo.\r\nNote: The unite action `file_rec` does a recursive file matching by default\r\nwithout the need to set wildcards.\r\n\r\nYou can also specify multiple keywords to narrow down the candidates. Multiple\r\nkeywords need to be separated either by a space \" \" or a dash \"|\". The\r\nexamples below match for candidates that meet both conditions \"foo\" and \"bar\".\r\n\r\n\tfoo bar\r\n\tfoo|bar\r\n\r\nYou can also specify negative conditions with an exclamation mark \"!\".  This\r\nmatches candidates that meet \"foo\" but do not meet \"bar\".\r\n\r\n\tfoo !bar\r\n\r\nWild cards are added automatically if you add a \"\/\" in the filter and you have\r\nspecified \"files\" as the buffer name with the option \"-buffer-name\". That's\r\nhandy in case you select files with unite.\r\n\r\n\t:Unite -buffer-name=files file\r\n\r\nSee also `unite_default_key_mappings` for other actions.\r\n\r\nThere is also a screencast available which shows unite in action. Thanks to\r\nujihisa! http:\/\/www.ustream.tv\/recorded\/11240673\r\n\r\n## Install details\r\n\r\nInstall the distributed files into your Vim script directory which is usually\r\n`~\/.vim\/`, or `$HOME\/vimfiles` on Windows. You should consider to use one of the\r\nfamous package managers for Vim like vundle or neobundle to install the\r\nplugin.\r\n\r\nAfter installation you can run unite with the `:Unite` command and append the\r\nsources to the command you wish to select from as parameters. However, it's a\r\npain in the ass to run the command explicitly every time, so I recommend you\r\nto set a key mapping for the command. See `:h unite`.\r\n\r\n## Links\r\n\r\nunite plugins(in Japanese): https:\/\/github.com\/Shougo\/unite.vim\/wiki\/unite-plugins","install_details":"Install the distributed files into Vim script directory which is usually\r\n~\/.vim\/, or $HOME\/vimfiles on Windows.\r\n\r\nIn future VimJolts the Vim plugin package manager will support unite, you can\r\ninstall unite just by `jolt install unite`.\r\n\r\nYou may run unite with |:Unite| command with source as parameters if you\r\nsucceeded in installing unite.  However, it's a pain in the ass to run the\r\ncommand explicitly every time, so I recommend you to set a key mapping for the\r\ncommand.","5":"Install the distributed files into Vim script directory which is usually\r\n~\/.vim\/, or $HOME\/vimfiles on Windows.\r\n\r\nIn future VimJolts the Vim plugin package manager will support unite, you can\r\ninstall unite just by `jolt install unite`.\r\n\r\nYou may run unite with |:Unite| command with source as parameters if you\r\nsucceeded in installing unite.  However, it's a pain in the ass to run the\r\ncommand explicitly every time, so I recommend you to set a key mapping for the\r\ncommand.","first_name":"Shougo","6":"Shougo","last_name":"Matsushita","7":"Matsushita","releases":[{"0":"3396","vim_version":"7.2","1":"7.2","script_version":"5.0","2":"5.0","version_comment":"- Added <Plug>(unite_print_message_log) mapping.\r\n- Added converter_file_directory.\r\n- Added converter_tail.\r\n- Added g:unite_force_overwrite_statusline option.\r\n- Added g:unite_source_file_rec_async_command option.\r\n- Added g:unite_source_file_rec_max_cache_files.\r\n- Added log option.\r\n- Added unite#util#has_lua().\r\n- Changed smart_execute_command() implementation.\r\n- Changed start action in source kind.\r\n- Changed tab source behavior.\r\n- Disabled auto resize feature.\r\n- Enabled lua interface feature.\r\n- Fixed <Plug>(unite_delete_backward_path).\r\n- Fixed action source behavior.\r\n- Fixed action source problem.\r\n- Fixed action source problems.\r\n- Fixed action__path problem.\r\n- Fixed cd problem in unite#start_temporary().\r\n- Fixed close previous unite buffer behavior.\r\n- Fixed file_rec\/async source.\r\n- Fixed filter.\r\n- Fixed for auto_preview.\r\n- Fixed for backquote.\r\n- Fixed for temporary buffer.\r\n- Fixed load scripts behavior.\r\n- Fixed loading sources problem.\r\n- Fixed narrow action.\r\n- Fixed restore updatetime.\r\n- Fixed start sources behavior.\r\n- Fixed temporary buffer.\r\n- Fixed unite#clear_message().\r\n- Fixed unite#get_candidates().\r\n- Fixed updatetime restore.\r\n- Improved <Plug>(unite_delete_backward_char).\r\n- Improved cutsom bookmark action.\r\n- Improved documentation for ag.\r\n- Improved documentation.\r\n- Improved line syntax.\r\n- Improved load default scripts behavior.\r\n- Improved message behavior.\r\n- Improved mru sources.\r\n- Improved narrow action.\r\n- Improved output source behavior.\r\n- Improved print message feature.\r\n- Improved quick match behavior.\r\n- Improved runtimepath source.\r\n- Improved source file.\r\n- Improved start sources behavior.\r\n- Improved syntax highlight in line and grep sources.\r\n- Improved unite status line.\r\n- Improved unite#get_unite_bufnr()\/unite#get_unite_winnr().\r\n- Improved vimfiler redraw behavior.\r\n- Optimized for files.\r\n- Restore statusline.\r\n- Supported make multiple directories.\r\n- Temporally disabled if_lua feature. Because if_lua has SEGV problem.\r\n- Uniq mru list in save.\r\n- Use python3 interface.\r\n- Use vimproc#readdir() in file_rec source.","3":"- Added <Plug>(unite_print_message_log) mapping.\r\n- Added converter_file_directory.\r\n- Added converter_tail.\r\n- Added g:unite_force_overwrite_statusline option.\r\n- Added g:unite_source_file_rec_async_command option.\r\n- Added g:unite_source_file_rec_max_cache_files.\r\n- Added log option.\r\n- Added unite#util#has_lua().\r\n- Changed smart_execute_command() implementation.\r\n- Changed start action in source kind.\r\n- Changed tab source behavior.\r\n- Disabled auto resize feature.\r\n- Enabled lua interface feature.\r\n- Fixed <Plug>(unite_delete_backward_path).\r\n- Fixed action source behavior.\r\n- Fixed action source problem.\r\n- Fixed action source problems.\r\n- Fixed action__path problem.\r\n- Fixed cd problem in unite#start_temporary().\r\n- Fixed close previous unite buffer behavior.\r\n- Fixed file_rec\/async source.\r\n- Fixed filter.\r\n- Fixed for auto_preview.\r\n- Fixed for backquote.\r\n- Fixed for temporary buffer.\r\n- Fixed load scripts behavior.\r\n- Fixed loading sources problem.\r\n- Fixed narrow action.\r\n- Fixed restore updatetime.\r\n- Fixed start sources behavior.\r\n- Fixed temporary buffer.\r\n- Fixed unite#clear_message().\r\n- Fixed unite#get_candidates().\r\n- Fixed updatetime restore.\r\n- Improved <Plug>(unite_delete_backward_char).\r\n- Improved cutsom bookmark action.\r\n- Improved documentation for ag.\r\n- Improved documentation.\r\n- Improved line syntax.\r\n- Improved load default scripts behavior.\r\n- Improved message behavior.\r\n- Improved mru sources.\r\n- Improved narrow action.\r\n- Improved output source behavior.\r\n- Improved print message feature.\r\n- Improved quick match behavior.\r\n- Improved runtimepath source.\r\n- Improved source file.\r\n- Improved start sources behavior.\r\n- Improved syntax highlight in line and grep sources.\r\n- Improved unite status line.\r\n- Improved unite#get_unite_bufnr()\/unite#get_unite_winnr().\r\n- Improved vimfiler redraw behavior.\r\n- Optimized for files.\r\n- Restore statusline.\r\n- Supported make multiple directories.\r\n- Temporally disabled if_lua feature. Because if_lua has SEGV problem.\r\n- Uniq mru list in save.\r\n- Use python3 interface.\r\n- Use vimproc#readdir() in file_rec source.","package":"unite.vim-5.0.zip","4":"unite.vim-5.0.zip","src_id":"20094","5":"20094","creation_date":"1368316732","6":"1368316732"},{"0":"3396","vim_version":"7.2","1":"7.2","script_version":"4.1","2":"4.1","version_comment":"- Added -hide-status-line option.\r\n- Added -multi-line option.\r\n- Added -no-focus option.\r\n- Added -short-source-names and -long-source-names and\r\n- Added <C-g> mapping.\r\n- Added <Plug>(unite_narrowing_dot).\r\n- Added FAQ section.\r\n- Added alias in directory kind.\r\n- Added backup action.\r\n- Added custom matchers\/sorters\/converters.\r\n- Added default_kind attribute.\r\n- Added dirdiff action.\r\n- Added echo action.\r\n- Added examples.\r\n- Added function source.\r\n- Added g:unite_marked_icon option.\r\n- Added g:unite_source_buffer_time_format.\r\n- Added g:unite_source_process_enable_confirm option.\r\n- Added g:unite_source_vimgrep_ignore_pattern.\r\n- Added host check in file_point.\r\n- Added line\/fast source.\r\n- Added matcher_context filter.\r\n- Added matchers, sorters, converters.\r\n- Added readable check in file.\r\n- Added resume option.\r\n- Added runtimepath source.\r\n- Added sorter_length.\r\n- Added source custom variables.\r\n- Added unite#start_script().\r\n- Added unite__new_candidate action.\r\n- Added unite_sources autoload support.\r\n- Added wrap option.\r\n- Changed -immediately behavior.\r\n- Changed default matcher.\r\n- Changed insert word behavior.\r\n- Changed profile_name default value.\r\n- Changed tab source behavior.\r\n- Deleted max_candidates in mapping source.\r\n- Deleted mru max_candidates.\r\n- Deleted unite#filters#default#use().\r\n- Disable colors in grep source.\r\n- Fixed -auto-preview problems.\r\n- Fixed <Plug>(unite_move_head).\r\n- Fixed <Plug>(unite_restart) behavior.\r\n- Fixed a bug that edit action didn't add history in command kind.\r\n- Fixed action table.\r\n- Fixed alias actions.\r\n- Fixed buffer initialization check.\r\n- Fixed choose action for vimfiler.\r\n- Fixed clear marks behavior.\r\n- Fixed complete behavior.\r\n- Fixed converter in file_rec.\r\n- Fixed directory and file source.\r\n- Fixed documentation.\r\n- Fixed file_rec filters.\r\n- Fixed find source.\r\n- Fixed for line source.\r\n- Fixed for multiline behavior.\r\n- Fixed for new vimshell.\r\n- Fixed for syntax enable.\r\n- Fixed for unite-source.\r\n- Fixed function preview error.\r\n- Fixed grep check.\r\n- Fixed grep source.\r\n- Fixed ignore_pattern behavior.\r\n- Fixed initialize error.\r\n- Fixed insert word.\r\n- Fixed kind in find source.\r\n- Fixed line source behavior.\r\n- Fixed loop cursor up behavior.\r\n- Fixed narrowing behavior.\r\n- Fixed parse options.\r\n- Fixed print message behavior.\r\n- Fixed print message.\r\n- Fixed quit session behavior.\r\n- Fixed redraw all candiates behavior.\r\n- Fixed redraw_all_candidates().\r\n- Fixed resume bug.\r\n- Fixed resume error.\r\n- Fixed set syntax.\r\n- Fixed source kind action.\r\n- Fixed source source.\r\n- Fixed start action.\r\n- Fixed start_insert problem in complete source.\r\n- Fixed statusline.\r\n- Fixed syntax file.\r\n- Fixed temporary buffer behavior.\r\n- Fixed unite action loading problem.\r\n- Fixed unite#custom_source().\r\n- Fixed unite#get_default_action().\r\n- Fixed unite#get_sources().\r\n- Fixed unite-menu behavior.\r\n- Fixed wrap behavior.\r\n- Implemented recache system automatically in file_rec(\/async) sources.\r\n- Improved adjustment behavior.\r\n- Improved auto split behavior.\r\n- Improved buffer source highlight.\r\n- Improved check plugins.\r\n- Improved default substitute pattern.\r\n- Improved documentation.\r\n- Improved file_rec behavior.\r\n- Improved file_rec converter.\r\n- Improved for getting filetime.\r\n- Improved grep actions behavior.\r\n- Improved here behavior.\r\n- Improved ignore_pattern behavior in file_rec source.\r\n- Improved input().\r\n- Improved insert action.\r\n- Improved is_listed action behavior.\r\n- Improved lcd for vimfiler.\r\n- Improved line source behavior.\r\n- Improved message behavior.\r\n- Improved name search.\r\n- Improved narrow action behavior.\r\n- Improved print message behavior.\r\n- Improved process source.\r\n- Improved profile behavior.\r\n- Improved redraw status behavior.\r\n- Improved redraw status line.\r\n- Improved sorter_rank behavior.\r\n- Improved tab source.\r\n- Improved temporary buffer behavior.\r\n- Improved truncate behavior.\r\n- Improved unite buffer source.\r\n- Improved unite menu behavior.\r\n- Improved unite#mappings#do_action().\r\n- Improved unite#start_complete().\r\n- Improved unite#util#is_cmdwin().\r\n- Improved unite-menu source.\r\n- Improved update behavior.\r\n- Optimised sorter_rank.\r\n- Print default action in action source.\r\n- Refactorred mappings.vim.\r\n- Save previous winwidth and winheight.\r\n- Set default_kind attribute in sources.\r\n- Set is_multi_line in output source.\r\n- Set sorter_nothing in menu source.\r\n- Uniq in file_rec initialization.\r\n- Use trashbox automatically in delete action.","3":"- Added -hide-status-line option.\r\n- Added -multi-line option.\r\n- Added -no-focus option.\r\n- Added -short-source-names and -long-source-names and\r\n- Added <C-g> mapping.\r\n- Added <Plug>(unite_narrowing_dot).\r\n- Added FAQ section.\r\n- Added alias in directory kind.\r\n- Added backup action.\r\n- Added custom matchers\/sorters\/converters.\r\n- Added default_kind attribute.\r\n- Added dirdiff action.\r\n- Added echo action.\r\n- Added examples.\r\n- Added function source.\r\n- Added g:unite_marked_icon option.\r\n- Added g:unite_source_buffer_time_format.\r\n- Added g:unite_source_process_enable_confirm option.\r\n- Added g:unite_source_vimgrep_ignore_pattern.\r\n- Added host check in file_point.\r\n- Added line\/fast source.\r\n- Added matcher_context filter.\r\n- Added matchers, sorters, converters.\r\n- Added readable check in file.\r\n- Added resume option.\r\n- Added runtimepath source.\r\n- Added sorter_length.\r\n- Added source custom variables.\r\n- Added unite#start_script().\r\n- Added unite__new_candidate action.\r\n- Added unite_sources autoload support.\r\n- Added wrap option.\r\n- Changed -immediately behavior.\r\n- Changed default matcher.\r\n- Changed insert word behavior.\r\n- Changed profile_name default value.\r\n- Changed tab source behavior.\r\n- Deleted max_candidates in mapping source.\r\n- Deleted mru max_candidates.\r\n- Deleted unite#filters#default#use().\r\n- Disable colors in grep source.\r\n- Fixed -auto-preview problems.\r\n- Fixed <Plug>(unite_move_head).\r\n- Fixed <Plug>(unite_restart) behavior.\r\n- Fixed a bug that edit action didn't add history in command kind.\r\n- Fixed action table.\r\n- Fixed alias actions.\r\n- Fixed buffer initialization check.\r\n- Fixed choose action for vimfiler.\r\n- Fixed clear marks behavior.\r\n- Fixed complete behavior.\r\n- Fixed converter in file_rec.\r\n- Fixed directory and file source.\r\n- Fixed documentation.\r\n- Fixed file_rec filters.\r\n- Fixed find source.\r\n- Fixed for line source.\r\n- Fixed for multiline behavior.\r\n- Fixed for new vimshell.\r\n- Fixed for syntax enable.\r\n- Fixed for unite-source.\r\n- Fixed function preview error.\r\n- Fixed grep check.\r\n- Fixed grep source.\r\n- Fixed ignore_pattern behavior.\r\n- Fixed initialize error.\r\n- Fixed insert word.\r\n- Fixed kind in find source.\r\n- Fixed line source behavior.\r\n- Fixed loop cursor up behavior.\r\n- Fixed narrowing behavior.\r\n- Fixed parse options.\r\n- Fixed print message behavior.\r\n- Fixed print message.\r\n- Fixed quit session behavior.\r\n- Fixed redraw all candiates behavior.\r\n- Fixed redraw_all_candidates().\r\n- Fixed resume bug.\r\n- Fixed resume error.\r\n- Fixed set syntax.\r\n- Fixed source kind action.\r\n- Fixed source source.\r\n- Fixed start action.\r\n- Fixed start_insert problem in complete source.\r\n- Fixed statusline.\r\n- Fixed syntax file.\r\n- Fixed temporary buffer behavior.\r\n- Fixed unite action loading problem.\r\n- Fixed unite#custom_source().\r\n- Fixed unite#get_default_action().\r\n- Fixed unite#get_sources().\r\n- Fixed unite-menu behavior.\r\n- Fixed wrap behavior.\r\n- Implemented recache system automatically in file_rec(\/async) sources.\r\n- Improved adjustment behavior.\r\n- Improved auto split behavior.\r\n- Improved buffer source highlight.\r\n- Improved check plugins.\r\n- Improved default substitute pattern.\r\n- Improved documentation.\r\n- Improved file_rec behavior.\r\n- Improved file_rec converter.\r\n- Improved for getting filetime.\r\n- Improved grep actions behavior.\r\n- Improved here behavior.\r\n- Improved ignore_pattern behavior in file_rec source.\r\n- Improved input().\r\n- Improved insert action.\r\n- Improved is_listed action behavior.\r\n- Improved lcd for vimfiler.\r\n- Improved line source behavior.\r\n- Improved message behavior.\r\n- Improved name search.\r\n- Improved narrow action behavior.\r\n- Improved print message behavior.\r\n- Improved process source.\r\n- Improved profile behavior.\r\n- Improved redraw status behavior.\r\n- Improved redraw status line.\r\n- Improved sorter_rank behavior.\r\n- Improved tab source.\r\n- Improved temporary buffer behavior.\r\n- Improved truncate behavior.\r\n- Improved unite buffer source.\r\n- Improved unite menu behavior.\r\n- Improved unite#mappings#do_action().\r\n- Improved unite#start_complete().\r\n- Improved unite#util#is_cmdwin().\r\n- Improved unite-menu source.\r\n- Improved update behavior.\r\n- Optimised sorter_rank.\r\n- Print default action in action source.\r\n- Refactorred mappings.vim.\r\n- Save previous winwidth and winheight.\r\n- Set default_kind attribute in sources.\r\n- Set is_multi_line in output source.\r\n- Set sorter_nothing in menu source.\r\n- Uniq in file_rec initialization.\r\n- Use trashbox automatically in delete action.","package":"unite.vim-4.1.zip","4":"unite.vim-4.1.zip","src_id":"19581","5":"19581","creation_date":"1362198903","6":"1362198903"},{"0":"3396","vim_version":"7.2","1":"7.2","script_version":"4.0","2":"4.0","version_comment":"- Added -auto-quit option.\r\n- Added -keep-focus option.\r\n- Added <Plug>(unite_cursor_bottom) keymapping.\r\n- Added diff action in kind file.\r\n- Added directory and directory\/new source.\r\n- Added documentation.\r\n- Added file kind in grep source.\r\n- Added g:unite_source_directory_mru_filename_format option.\r\n- Added preview action in mapping and command sources.\r\n- Added tabdrop action.\r\n- Added unite#custom_source().\r\n- Added unite#get_unite_winnr().\r\n- Added yy mapping.\r\n- Changed asyncronous update behavior.\r\n- Changed default matcher in command source.\r\n- Changed filters behavior.\r\n- Changed ignore pattern behavior.\r\n- Changed postfix behavior.\r\n- Changed sources initialize behavior.\r\n- Delete old cache files.\r\n- Deleted Japanese documentation.\r\n- Deleted debug message.\r\n- Deleted yank action in history\/yank.\r\n- Delted obsolute changelog.\r\n- Merged English documentation(Thanks akiradeveloper!).\r\n- Move to new directory position when vimfiler__mkdir action.\r\n- Optimised load scripts.\r\n- Optimized filters.\r\n- Optimized redraw candidates.\r\n- Revised documentation.\r\n- Set is_multiline in grep and line source.\r\n- Setlocal nomodified.\r\n- Split automatically when &l:modified && !&l:hidden.\r\n- Splitted session source.\r\n- Supported over 4GB files.\r\n- Supported protocol copy.\r\n- Supported unite-ssh.","3":"- Added -auto-quit option.\r\n- Added -keep-focus option.\r\n- Added <Plug>(unite_cursor_bottom) keymapping.\r\n- Added diff action in kind file.\r\n- Added directory and directory\/new source.\r\n- Added documentation.\r\n- Added file kind in grep source.\r\n- Added g:unite_source_directory_mru_filename_format option.\r\n- Added preview action in mapping and command sources.\r\n- Added tabdrop action.\r\n- Added unite#custom_source().\r\n- Added unite#get_unite_winnr().\r\n- Added yy mapping.\r\n- Changed asyncronous update behavior.\r\n- Changed default matcher in command source.\r\n- Changed filters behavior.\r\n- Changed ignore pattern behavior.\r\n- Changed postfix behavior.\r\n- Changed sources initialize behavior.\r\n- Delete old cache files.\r\n- Deleted Japanese documentation.\r\n- Deleted debug message.\r\n- Deleted yank action in history\/yank.\r\n- Delted obsolute changelog.\r\n- Merged English documentation(Thanks akiradeveloper!).\r\n- Move to new directory position when vimfiler__mkdir action.\r\n- Optimised load scripts.\r\n- Optimized filters.\r\n- Optimized redraw candidates.\r\n- Revised documentation.\r\n- Set is_multiline in grep and line source.\r\n- Setlocal nomodified.\r\n- Split automatically when &l:modified && !&l:hidden.\r\n- Splitted session source.\r\n- Supported over 4GB files.\r\n- Supported protocol copy.\r\n- Supported unite-ssh.","package":"unite.vim-4.0.zip","4":"unite.vim-4.0.zip","src_id":"18522","5":"18522","creation_date":"1346508436","6":"1346508436"},{"0":"3396","vim_version":"7.2","1":"7.2","script_version":"3.1","2":"3.1","version_comment":"- Added -here option.\r\n- Added -hide-source-names option.\r\n- Added -max-multi-lines option.\r\n- Added -no-cursor-line option.\r\n- Added -no-empty option.\r\n- Added -silent option.\r\n- Added -update-time and -cursor-line-high-light options.\r\n- Added :UniteClose command.\r\n- Added abbr_head.\r\n- Added complete attribute.\r\n- Added file_new source.\r\n- Added g:unite_kind_file_use_trashbox option.\r\n- Added g:unite_source_find_ignore_pattern and g:unite_source_grep_ignore_pattern options.\r\n- Added g:unite_source_grep_search_word_highlight option.\r\n- Added g:unite_source_history_yank_file option.\r\n- Added goto action in buffer kind.\r\n- Added i_<Plug>(unite_redraw) mapping.\r\n- Added insert_directory action.\r\n- Added matcher_hide_hidden_files filter.\r\n- Added on_pre_filter hook.\r\n- Added preview action in window and tab action.\r\n- Added rec_parent and rec_parent\/async actions.\r\n- Added sorter_rank filter and changed default sorter.\r\n- Added source complete functions.\r\n- Added spec file.\r\n- Added unite#do_candidates_action().\r\n- Added unite#get_candidates().\r\n- Added unite#print_source_error() api.\r\n- Added unite#print_source_message() api.\r\n- Added unite-source-attribute-parents.\r\n- Added util function.\r\n- Added wunix action.\r\n- Changed -hide-source-names option behavior.\r\n- Changed <Plug>(unite_print_candidate) behavior.\r\n- Changed default sorter.\r\n- Changed for new vimfiler interface.\r\n- Changed g:unite_source_file_rec_min_cache_files behavior.\r\n- Changed quick match syntax.\r\n- Changed timer timing.\r\n- Changed uri kind behavior.\r\n- Deleted noautocmd.\r\n- Detect errors in file_rec\/async source.\r\n- Does not cd in vimfiler__mkdir action.\r\n- Don't use termencoding.\r\n- Don't use wincmd p.\r\n- Fixed -auto-preview behavior.\r\n- Fixed -toggle option.\r\n- Fixed :match error.\r\n- Fixed <ESC> mapping.\r\n- Fixed <Plug>(unite_insert_head) mapping.\r\n- Fixed E325 problem.\r\n- Fixed InsertLeave problem.\r\n- Fixed a bit.\r\n- Fixed autocmd problem.\r\n- Fixed buffer rename.\r\n- Fixed cd action behavior.\r\n- Fixed complete behavior.\r\n- Fixed complete problem.\r\n- Fixed dest_drive error.\r\n- Fixed directory_mru syntax pattern.\r\n- Fixed documentation.\r\n- Fixed execute problem.\r\n- Fixed expand error.\r\n- Fixed expand input bug.\r\n- Fixed expand problem.\r\n- Fixed expand() problem.\r\n- Fixed expand().\r\n- Fixed external cd.\r\n- Fixed external command bug.\r\n- Fixed file operation.\r\n- Fixed file_mru autocmd event.\r\n- Fixed file_mru behavior.\r\n- Fixed file_rec\/async source.\r\n- Fixed find and grep source behavior.\r\n- Fixed find source input bug.\r\n- Fixed for UNC path.\r\n- Fixed for cmdwin.\r\n- Fixed for long file path.\r\n- Fixed for vimfiler initialize.\r\n- Fixed for vimfiler source.\r\n- Fixed for vimfiler.\r\n- Fixed for yank_history source error.\r\n- Fixed gather_candidates().\r\n- Fixed grep action.\r\n- Fixed grep source behavior.\r\n- Fixed grep source error.\r\n- Fixed grep source.\r\n- Fixed highlight group bug.\r\n- Fixed highlight problem.\r\n- Fixed highlight.\r\n- Fixed history\/yank source limit.\r\n- Fixed iconv() bug.\r\n- Fixed ignore key sequence behavior.\r\n- Fixed initialize context.\r\n- Fixed initialize vimfiler candidates.\r\n- Fixed is_win error.\r\n- Fixed kind problem.\r\n- Fixed make directory action.\r\n- Fixed matcher_fuzzy behavior.\r\n- Fixed move_to_other_drive behavior.\r\n- Fixed move_to_other_drive error.\r\n- Fixed mru sources behavior.\r\n- Fixed parse path.\r\n- Fixed path bug in Windows.\r\n- Fixed persist_open action.\r\n- Fixed quick match bug.\r\n- Fixed quick match.\r\n- Fixed rank sorter.\r\n- Fixed rename behavior.\r\n- Fixed rename problem.\r\n- Fixed required_pattern_length problem.\r\n- Fixed restore cursor in actions.\r\n- Fixed restore updatetime.\r\n- Fixed resume_from_temporary().\r\n- Fixed set winfixheight problem.\r\n- Fixed source completion.\r\n- Fixed source line.\r\n- Fixed substitute patterns list.\r\n- Fixed truncate bug.\r\n- Fixed unite buffer behavior.\r\n- Fixed unite history\/input source error.\r\n- Fixed unite history\/yank and register sources.\r\n- Fixed unite#get_candidates() behavior.\r\n- Fixed unite#get_candidates().\r\n- Fixed unite#get_sources() error.\r\n- Fixed unite#set_buffer_name_option() error.\r\n- Fixed unite#vimfiler_check_filetype().\r\n- Fixed unite-action error.\r\n- Fixed updatetime error.\r\n- Fixed updatetime restore problem.\r\n- Fixed updatetime.\r\n- Fixed uri kind.\r\n- Fixed vimfiler action error.\r\n- Fixed vimfiler redraw bug.\r\n- Fixed vimfiler__shell action.\r\n- Fixed vimshell action.\r\n- Force use glob().\r\n- Ignore directories in file_mru source.\r\n- Ignore invalid path in file source.\r\n- Implemented OR matching.\r\n- Implemented boundary matched sort.\r\n- Implemented keyword highlight.\r\n- Implemented profile instead of buffer_name option.\r\n- Implemented use ls command when gather candidates(experimental).\r\n- Improved :UniteResume behavior.\r\n- Improved UniteWithInput behavior.\r\n- Improved buflisted().\r\n- Improved cd behavior.\r\n- Improved change source.\r\n- Improved check MRU path.\r\n- Improved check command line window.\r\n- Improved check default action.\r\n- Improved common action behavior.\r\n- Improved completion source.\r\n- Improved cursor move behavior.\r\n- Improved detect find command.\r\n- Improved detect source and action error.\r\n- Improved error check.\r\n- Improved error detection.\r\n- Improved error detecton when call hook.\r\n- Improved escape filename.\r\n- Improved expand bookmark name.\r\n- Improved file rename behavior.\r\n- Improved file_mru and directory_mru default setting.\r\n- Improved file_rec and file_rec\/async sources features.\r\n- Improved file_rec filtering behavior.\r\n- Improved filename completion.\r\n- Improved for vimfiler.\r\n- Improved get asyncronous candidates behavior.\r\n- Improved glob().\r\n- Improved grep source behavior.\r\n- Improved grep source.\r\n- Improved history\/yank source.\r\n- Improved ignore pattern.\r\n- Improved initialize candidates.\r\n- Improved input highlight patterns.\r\n- Improved is_multiline behavior.\r\n- Improved jump source.\r\n- Improved jump_list kind.\r\n- Improved jump_list preview action.\r\n- Improved line source.\r\n- Improved load_default_scripts().\r\n- Improved long abbr behavior.\r\n- Improved mapping source.\r\n- Improved matcher_fuzzy behavior.\r\n- Improved matcher_hidden_files filter.\r\n- Improved mru default time format.\r\n- Improved newfile action.\r\n- Improved padding.\r\n- Improved parse path in file source.\r\n- Improved persist_open action.\r\n- Improved quick match syntax.\r\n- Improved rank sorter behavior.\r\n- Improved redraw candidates.\r\n- Improved register source.\r\n- Improved rename action.\r\n- Improved split patterns.\r\n- Improved substitute path separator.\r\n- Improved substitute tab characters.\r\n- Improved sudo check.\r\n- Improved sudo detection.\r\n- Improved unite find input.\r\n- Improved unite register source.\r\n- Improved unite#_resize_window().\r\n- Improved unite#get_context() implementation.\r\n- Improved unite#mappings#do_action().\r\n- Improved unite-grep behavior.\r\n- Improved variables initialization.\r\n- Improved version check.\r\n- Improved vimfiler initialization.\r\n- Improved vimfiler__mkdir action.\r\n- Improved window resize.\r\n- Refactored is_windows.\r\n- Save cache files in file_rec and file_rec\/async sources.\r\n- Set kind action_table.\r\n- Supported ack command in grep source.\r\n- Syntax case ignore.\r\n- Updated vital.\r\n- Use find or dir command instead of ls.\r\n- Use vimproc#read_dir() (experimental).\r\n- set winfixwidth and winfixheight.","3":"- Added -here option.\r\n- Added -hide-source-names option.\r\n- Added -max-multi-lines option.\r\n- Added -no-cursor-line option.\r\n- Added -no-empty option.\r\n- Added -silent option.\r\n- Added -update-time and -cursor-line-high-light options.\r\n- Added :UniteClose command.\r\n- Added abbr_head.\r\n- Added complete attribute.\r\n- Added file_new source.\r\n- Added g:unite_kind_file_use_trashbox option.\r\n- Added g:unite_source_find_ignore_pattern and g:unite_source_grep_ignore_pattern options.\r\n- Added g:unite_source_grep_search_word_highlight option.\r\n- Added g:unite_source_history_yank_file option.\r\n- Added goto action in buffer kind.\r\n- Added i_<Plug>(unite_redraw) mapping.\r\n- Added insert_directory action.\r\n- Added matcher_hide_hidden_files filter.\r\n- Added on_pre_filter hook.\r\n- Added preview action in window and tab action.\r\n- Added rec_parent and rec_parent\/async actions.\r\n- Added sorter_rank filter and changed default sorter.\r\n- Added source complete functions.\r\n- Added spec file.\r\n- Added unite#do_candidates_action().\r\n- Added unite#get_candidates().\r\n- Added unite#print_source_error() api.\r\n- Added unite#print_source_message() api.\r\n- Added unite-source-attribute-parents.\r\n- Added util function.\r\n- Added wunix action.\r\n- Changed -hide-source-names option behavior.\r\n- Changed <Plug>(unite_print_candidate) behavior.\r\n- Changed default sorter.\r\n- Changed for new vimfiler interface.\r\n- Changed g:unite_source_file_rec_min_cache_files behavior.\r\n- Changed quick match syntax.\r\n- Changed timer timing.\r\n- Changed uri kind behavior.\r\n- Deleted noautocmd.\r\n- Detect errors in file_rec\/async source.\r\n- Does not cd in vimfiler__mkdir action.\r\n- Don't use termencoding.\r\n- Don't use wincmd p.\r\n- Fixed -auto-preview behavior.\r\n- Fixed -toggle option.\r\n- Fixed :match error.\r\n- Fixed <ESC> mapping.\r\n- Fixed <Plug>(unite_insert_head) mapping.\r\n- Fixed E325 problem.\r\n- Fixed InsertLeave problem.\r\n- Fixed a bit.\r\n- Fixed autocmd problem.\r\n- Fixed buffer rename.\r\n- Fixed cd action behavior.\r\n- Fixed complete behavior.\r\n- Fixed complete problem.\r\n- Fixed dest_drive error.\r\n- Fixed directory_mru syntax pattern.\r\n- Fixed documentation.\r\n- Fixed execute problem.\r\n- Fixed expand error.\r\n- Fixed expand input bug.\r\n- Fixed expand problem.\r\n- Fixed expand() problem.\r\n- Fixed expand().\r\n- Fixed external cd.\r\n- Fixed external command bug.\r\n- Fixed file operation.\r\n- Fixed file_mru autocmd event.\r\n- Fixed file_mru behavior.\r\n- Fixed file_rec\/async source.\r\n- Fixed find and grep source behavior.\r\n- Fixed find source input bug.\r\n- Fixed for UNC path.\r\n- Fixed for cmdwin.\r\n- Fixed for long file path.\r\n- Fixed for vimfiler initialize.\r\n- Fixed for vimfiler source.\r\n- Fixed for vimfiler.\r\n- Fixed for yank_history source error.\r\n- Fixed gather_candidates().\r\n- Fixed grep action.\r\n- Fixed grep source behavior.\r\n- Fixed grep source error.\r\n- Fixed grep source.\r\n- Fixed highlight group bug.\r\n- Fixed highlight problem.\r\n- Fixed highlight.\r\n- Fixed history\/yank source limit.\r\n- Fixed iconv() bug.\r\n- Fixed ignore key sequence behavior.\r\n- Fixed initialize context.\r\n- Fixed initialize vimfiler candidates.\r\n- Fixed is_win error.\r\n- Fixed kind problem.\r\n- Fixed make directory action.\r\n- Fixed matcher_fuzzy behavior.\r\n- Fixed move_to_other_drive behavior.\r\n- Fixed move_to_other_drive error.\r\n- Fixed mru sources behavior.\r\n- Fixed parse path.\r\n- Fixed path bug in Windows.\r\n- Fixed persist_open action.\r\n- Fixed quick match bug.\r\n- Fixed quick match.\r\n- Fixed rank sorter.\r\n- Fixed rename behavior.\r\n- Fixed rename problem.\r\n- Fixed required_pattern_length problem.\r\n- Fixed restore cursor in actions.\r\n- Fixed restore updatetime.\r\n- Fixed resume_from_temporary().\r\n- Fixed set winfixheight problem.\r\n- Fixed source completion.\r\n- Fixed source line.\r\n- Fixed substitute patterns list.\r\n- Fixed truncate bug.\r\n- Fixed unite buffer behavior.\r\n- Fixed unite history\/input source error.\r\n- Fixed unite history\/yank and register sources.\r\n- Fixed unite#get_candidates() behavior.\r\n- Fixed unite#get_candidates().\r\n- Fixed unite#get_sources() error.\r\n- Fixed unite#set_buffer_name_option() error.\r\n- Fixed unite#vimfiler_check_filetype().\r\n- Fixed unite-action error.\r\n- Fixed updatetime error.\r\n- Fixed updatetime restore problem.\r\n- Fixed updatetime.\r\n- Fixed uri kind.\r\n- Fixed vimfiler action error.\r\n- Fixed vimfiler redraw bug.\r\n- Fixed vimfiler__shell action.\r\n- Fixed vimshell action.\r\n- Force use glob().\r\n- Ignore directories in file_mru source.\r\n- Ignore invalid path in file source.\r\n- Implemented OR matching.\r\n- Implemented boundary matched sort.\r\n- Implemented keyword highlight.\r\n- Implemented profile instead of buffer_name option.\r\n- Implemented use ls command when gather candidates(experimental).\r\n- Improved :UniteResume behavior.\r\n- Improved UniteWithInput behavior.\r\n- Improved buflisted().\r\n- Improved cd behavior.\r\n- Improved change source.\r\n- Improved check MRU path.\r\n- Improved check command line window.\r\n- Improved check default action.\r\n- Improved common action behavior.\r\n- Improved completion source.\r\n- Improved cursor move behavior.\r\n- Improved detect find command.\r\n- Improved detect source and action error.\r\n- Improved error check.\r\n- Improved error detection.\r\n- Improved error detecton when call hook.\r\n- Improved escape filename.\r\n- Improved expand bookmark name.\r\n- Improved file rename behavior.\r\n- Improved file_mru and directory_mru default setting.\r\n- Improved file_rec and file_rec\/async sources features.\r\n- Improved file_rec filtering behavior.\r\n- Improved filename completion.\r\n- Improved for vimfiler.\r\n- Improved get asyncronous candidates behavior.\r\n- Improved glob().\r\n- Improved grep source behavior.\r\n- Improved grep source.\r\n- Improved history\/yank source.\r\n- Improved ignore pattern.\r\n- Improved initialize candidates.\r\n- Improved input highlight patterns.\r\n- Improved is_multiline behavior.\r\n- Improved jump source.\r\n- Improved jump_list kind.\r\n- Improved jump_list preview action.\r\n- Improved line source.\r\n- Improved load_default_scripts().\r\n- Improved long abbr behavior.\r\n- Improved mapping source.\r\n- Improved matcher_fuzzy behavior.\r\n- Improved matcher_hidden_files filter.\r\n- Improved mru default time format.\r\n- Improved newfile action.\r\n- Improved padding.\r\n- Improved parse path in file source.\r\n- Improved persist_open action.\r\n- Improved quick match syntax.\r\n- Improved rank sorter behavior.\r\n- Improved redraw candidates.\r\n- Improved register source.\r\n- Improved rename action.\r\n- Improved split patterns.\r\n- Improved substitute path separator.\r\n- Improved substitute tab characters.\r\n- Improved sudo check.\r\n- Improved sudo detection.\r\n- Improved unite find input.\r\n- Improved unite register source.\r\n- Improved unite#_resize_window().\r\n- Improved unite#get_context() implementation.\r\n- Improved unite#mappings#do_action().\r\n- Improved unite-grep behavior.\r\n- Improved variables initialization.\r\n- Improved version check.\r\n- Improved vimfiler initialization.\r\n- Improved vimfiler__mkdir action.\r\n- Improved window resize.\r\n- Refactored is_windows.\r\n- Save cache files in file_rec and file_rec\/async sources.\r\n- Set kind action_table.\r\n- Supported ack command in grep source.\r\n- Syntax case ignore.\r\n- Updated vital.\r\n- Use find or dir command instead of ls.\r\n- Use vimproc#read_dir() (experimental).\r\n- set winfixwidth and winfixheight.","package":"unite-3.1.zip","4":"unite-3.1.zip","src_id":"17877","5":"17877","creation_date":"1336275471","6":"1336275471"},{"0":"3396","vim_version":"7.2","1":"7.2","script_version":"3.0","2":"3.0","version_comment":"- Added -create option.\r\n- Added -quick-match option.\r\n- Added -toggle option.\r\n- Added :UniteSessionLoad command.\r\n- Added <Plug>(unite_all_exit) mapping.\r\n- Added <Plug>(unite_quick_match_choose_action) mapping.\r\n- Added <Plug>(unite_toggle_max_candidates) mapping.\r\n- Added alias source.\r\n- Added bang in buffer source.\r\n- Added buffer name limitation.\r\n- Added documentation.\r\n- Added file_rec vimfiler interface.\r\n- Added find source.\r\n- Added g:unite_source_session_enable_auto_save.\r\n- Added g:unite_source_session_options variable.\r\n- Added guicmd kind.\r\n- Added history\/yank source.\r\n- Added is_listed attribute.\r\n- Added is_matched and keymappings.\r\n- Added is_multiline attribute.\r\n- Added is_multiline documentation.\r\n- Added launcher source.\r\n- Added matcher_fuzzy.\r\n- Added matcher_migemo filter.\r\n- Added nested autocmd.\r\n- Added preview action in common kind.\r\n- Added process source.\r\n- Added register delete action.\r\n- Added register edit action.\r\n- Added session source.\r\n- Added sorter_reverse filter.\r\n- Added tabopen mappings.\r\n- Added unite process candidates alias.\r\n- Added unite-menu source.\r\n- Added vimfiler_dummy_candidates().\r\n- Changed -immediately behavior.\r\n- Changed a bit.\r\n- Changed a default keymapping behavior.\r\n- Changed file_mru and directory_mru default filename.\r\n- Changed g:unite_source_bookmark_file to g:unite_source_bookmark_directory.\r\n- Changed g:unite_source_menu_menus interface.\r\n- Changed g:unite_update_time default value.\r\n- Check obsolute option.\r\n- Detect sudo vim.\r\n- Escape [].\r\n- Expand path.\r\n- Fixed :VimShellPop bug.\r\n- Fixed alias table syntax sugar.\r\n- Fixed auto preview.\r\n- Fixed auto_resize and auto_preview behavior.\r\n- Fixed bookmark check.\r\n- Fixed buffer rename action.\r\n- Fixed copy and move behavior.\r\n- Fixed copy\/delete action.\r\n- Fixed current unite bug.\r\n- Fixed default mapping.\r\n- Fixed end problem.\r\n- Fixed examples.\r\n- Fixed expand path.\r\n- Fixed file actions.\r\n- Fixed file_mru filter.\r\n- Fixed file_rec\/async ignore pattern.\r\n- Fixed find source.\r\n- Fixed for yanktmp.\r\n- Fixed g:unite_source_file_mru_ignore_pattern.\r\n- Fixed g:unite_source_file_rec_ignore_pattern escape.\r\n- Fixed get buffer name input.\r\n- Fixed grep source.\r\n- Fixed input error.\r\n- Fixed jump_point.\r\n- Fixed keymapping.\r\n- Fixed mapping and file_rec source.\r\n- Fixed mark error.\r\n- Fixed new file action.\r\n- Fixed overwrite hooks error.\r\n- Fixed quit unite buffer.\r\n- Fixed s:check_over_write() behavior.\r\n- Fixed search unite buffer.\r\n- Fixed source change.\r\n- Fixed source file for vimfiler.\r\n- Fixed source syntax highlight.\r\n- Fixed unite action source.\r\n- Fixed unite alias.\r\n- Fixed unite buffer delete.\r\n- Fixed unite launcher source.\r\n- Fixed unite mappings source.\r\n- Fixed unite on_buf_unload error.\r\n- Fixed unite resume.\r\n- Fixed unite toggle.\r\n- Fixed unite#mappings#do_action().\r\n- Fixed unite#print_error() error.\r\n- Fixed unite#resume().\r\n- Fixed unite#vimfiler_check_filetype() error message.\r\n- Fixed unite-bookmark.\r\n- Fixed unite-line source.\r\n- Fixed unite-mappings.\r\n- Fixed unite-menu.\r\n- Fixed unite-register error.\r\n- Fixed unite-source.\r\n- Fixed variables initialize.\r\n- Fixed vimfiler actions.\r\n- Fixed vimfiler cd action.\r\n- Fixed vimfiler cd error.\r\n- Fixed vimfiler error.\r\n- Fixed vimfiler file source.\r\n- Fixed vimfiler_gather_candidates().\r\n- Fixed visible dot file error.\r\n- For Vim 7.2 or above.\r\n- Implemented -no-split option.\r\n- Implemented action_table syntax sugar.\r\n- Implemented copy and delete and move action.\r\n- Implemented file_rec vimfiler interface.\r\n- Implemented previewd_buffer_list.\r\n- Implemented unite#mappings#set_current_filters().\r\n- Implemented unite#start_complete().\r\n- Implemented vimfiler actions.\r\n- Implemented vimfiler completion interface.\r\n- Implemented vimfiler interface.\r\n- Implemented vimfiler write interface.\r\n- Improved :UniteResume.\r\n- Improved action name.\r\n- Improved alias.\r\n- Improved automatically session.\r\n- Improved buffer abbr.\r\n- Improved buffer name behavior.\r\n- Improved buffer name option behavior.\r\n- Improved buffer source.\r\n- Improved buffer view.\r\n- Improved check filetype.\r\n- Improved choose action.\r\n- Improved cursor move.\r\n- Improved file operations for vimfiler.\r\n- Improved file operations.\r\n- Improved file_point source.\r\n- Improved file_rec word.\r\n- Improved history\/yank and register source.\r\n- Improved history\/yank source behavior.\r\n- Improved initialize candidates.\r\n- Improved insert word action.\r\n- Improved launcher source.\r\n- Improved overwrite method.\r\n- Improved process view.\r\n- Improved quick match behavior.\r\n- Improved quit unite buffer.\r\n- Improved recache_candidates().\r\n- Improved redraw behavior.\r\n- Improved redraw.\r\n- Improved register and history\/yank source.\r\n- Improved register source.\r\n- Improved s:convert2dictionary().\r\n- Improved session load.\r\n- Improved source file sort.\r\n- Improved source kind description.\r\n- Improved syntax highlight.\r\n- Improved unite async redraw.\r\n- Improved unite buffer source.\r\n- Improved unite mapping source.\r\n- Improved unite session behavior.\r\n- Improved unite#sources#file#create_vimfiler_dict().\r\n- Improved unite#start().\r\n- Improved unite#vimfiler_check_filetype().\r\n- Improved unite-bookmark.\r\n- Improved unite-line.\r\n- Improved unite-menu examples.\r\n- Improved unite-resume behavior.\r\n- Improved unite-source behavior.\r\n- Improved update time.\r\n- Improved vimfiler actions.\r\n- Improved vimfiler cd.\r\n- Improved vimfiler file source.\r\n- Improved vimfiler interface.\r\n- Optimized for vimfiler.\r\n- Refactoringed local variable names.\r\n- Renamed cd and lcd options.\r\n- Skip don't exist file in jump_point source.\r\n- Supported kind list(experimental).\r\n- Supported list substitute pattern.\r\n- Supported on_pre_init hook in alias source.\r\n- Updated vital.vim.\r\n- source process supported Windows.","3":"- Added -create option.\r\n- Added -quick-match option.\r\n- Added -toggle option.\r\n- Added :UniteSessionLoad command.\r\n- Added <Plug>(unite_all_exit) mapping.\r\n- Added <Plug>(unite_quick_match_choose_action) mapping.\r\n- Added <Plug>(unite_toggle_max_candidates) mapping.\r\n- Added alias source.\r\n- Added bang in buffer source.\r\n- Added buffer name limitation.\r\n- Added documentation.\r\n- Added file_rec vimfiler interface.\r\n- Added find source.\r\n- Added g:unite_source_session_enable_auto_save.\r\n- Added g:unite_source_session_options variable.\r\n- Added guicmd kind.\r\n- Added history\/yank source.\r\n- Added is_listed attribute.\r\n- Added is_matched and keymappings.\r\n- Added is_multiline attribute.\r\n- Added is_multiline documentation.\r\n- Added launcher source.\r\n- Added matcher_fuzzy.\r\n- Added matcher_migemo filter.\r\n- Added nested autocmd.\r\n- Added preview action in common kind.\r\n- Added process source.\r\n- Added register delete action.\r\n- Added register edit action.\r\n- Added session source.\r\n- Added sorter_reverse filter.\r\n- Added tabopen mappings.\r\n- Added unite process candidates alias.\r\n- Added unite-menu source.\r\n- Added vimfiler_dummy_candidates().\r\n- Changed -immediately behavior.\r\n- Changed a bit.\r\n- Changed a default keymapping behavior.\r\n- Changed file_mru and directory_mru default filename.\r\n- Changed g:unite_source_bookmark_file to g:unite_source_bookmark_directory.\r\n- Changed g:unite_source_menu_menus interface.\r\n- Changed g:unite_update_time default value.\r\n- Check obsolute option.\r\n- Detect sudo vim.\r\n- Escape [].\r\n- Expand path.\r\n- Fixed :VimShellPop bug.\r\n- Fixed alias table syntax sugar.\r\n- Fixed auto preview.\r\n- Fixed auto_resize and auto_preview behavior.\r\n- Fixed bookmark check.\r\n- Fixed buffer rename action.\r\n- Fixed copy and move behavior.\r\n- Fixed copy\/delete action.\r\n- Fixed current unite bug.\r\n- Fixed default mapping.\r\n- Fixed end problem.\r\n- Fixed examples.\r\n- Fixed expand path.\r\n- Fixed file actions.\r\n- Fixed file_mru filter.\r\n- Fixed file_rec\/async ignore pattern.\r\n- Fixed find source.\r\n- Fixed for yanktmp.\r\n- Fixed g:unite_source_file_mru_ignore_pattern.\r\n- Fixed g:unite_source_file_rec_ignore_pattern escape.\r\n- Fixed get buffer name input.\r\n- Fixed grep source.\r\n- Fixed input error.\r\n- Fixed jump_point.\r\n- Fixed keymapping.\r\n- Fixed mapping and file_rec source.\r\n- Fixed mark error.\r\n- Fixed new file action.\r\n- Fixed overwrite hooks error.\r\n- Fixed quit unite buffer.\r\n- Fixed s:check_over_write() behavior.\r\n- Fixed search unite buffer.\r\n- Fixed source change.\r\n- Fixed source file for vimfiler.\r\n- Fixed source syntax highlight.\r\n- Fixed unite action source.\r\n- Fixed unite alias.\r\n- Fixed unite buffer delete.\r\n- Fixed unite launcher source.\r\n- Fixed unite mappings source.\r\n- Fixed unite on_buf_unload error.\r\n- Fixed unite resume.\r\n- Fixed unite toggle.\r\n- Fixed unite#mappings#do_action().\r\n- Fixed unite#print_error() error.\r\n- Fixed unite#resume().\r\n- Fixed unite#vimfiler_check_filetype() error message.\r\n- Fixed unite-bookmark.\r\n- Fixed unite-line source.\r\n- Fixed unite-mappings.\r\n- Fixed unite-menu.\r\n- Fixed unite-register error.\r\n- Fixed unite-source.\r\n- Fixed variables initialize.\r\n- Fixed vimfiler actions.\r\n- Fixed vimfiler cd action.\r\n- Fixed vimfiler cd error.\r\n- Fixed vimfiler error.\r\n- Fixed vimfiler file source.\r\n- Fixed vimfiler_gather_candidates().\r\n- Fixed visible dot file error.\r\n- For Vim 7.2 or above.\r\n- Implemented -no-split option.\r\n- Implemented action_table syntax sugar.\r\n- Implemented copy and delete and move action.\r\n- Implemented file_rec vimfiler interface.\r\n- Implemented previewd_buffer_list.\r\n- Implemented unite#mappings#set_current_filters().\r\n- Implemented unite#start_complete().\r\n- Implemented vimfiler actions.\r\n- Implemented vimfiler completion interface.\r\n- Implemented vimfiler interface.\r\n- Implemented vimfiler write interface.\r\n- Improved :UniteResume.\r\n- Improved action name.\r\n- Improved alias.\r\n- Improved automatically session.\r\n- Improved buffer abbr.\r\n- Improved buffer name behavior.\r\n- Improved buffer name option behavior.\r\n- Improved buffer source.\r\n- Improved buffer view.\r\n- Improved check filetype.\r\n- Improved choose action.\r\n- Improved cursor move.\r\n- Improved file operations for vimfiler.\r\n- Improved file operations.\r\n- Improved file_point source.\r\n- Improved file_rec word.\r\n- Improved history\/yank and register source.\r\n- Improved history\/yank source behavior.\r\n- Improved initialize candidates.\r\n- Improved insert word action.\r\n- Improved launcher source.\r\n- Improved overwrite method.\r\n- Improved process view.\r\n- Improved quick match behavior.\r\n- Improved quit unite buffer.\r\n- Improved recache_candidates().\r\n- Improved redraw behavior.\r\n- Improved redraw.\r\n- Improved register and history\/yank source.\r\n- Improved register source.\r\n- Improved s:convert2dictionary().\r\n- Improved session load.\r\n- Improved source file sort.\r\n- Improved source kind description.\r\n- Improved syntax highlight.\r\n- Improved unite async redraw.\r\n- Improved unite buffer source.\r\n- Improved unite mapping source.\r\n- Improved unite session behavior.\r\n- Improved unite#sources#file#create_vimfiler_dict().\r\n- Improved unite#start().\r\n- Improved unite#vimfiler_check_filetype().\r\n- Improved unite-bookmark.\r\n- Improved unite-line.\r\n- Improved unite-menu examples.\r\n- Improved unite-resume behavior.\r\n- Improved unite-source behavior.\r\n- Improved update time.\r\n- Improved vimfiler actions.\r\n- Improved vimfiler cd.\r\n- Improved vimfiler file source.\r\n- Improved vimfiler interface.\r\n- Optimized for vimfiler.\r\n- Refactoringed local variable names.\r\n- Renamed cd and lcd options.\r\n- Skip don't exist file in jump_point source.\r\n- Supported kind list(experimental).\r\n- Supported list substitute pattern.\r\n- Supported on_pre_init hook in alias source.\r\n- Updated vital.vim.\r\n- source process supported Windows.","package":"unite.vim-3.0.zip","4":"unite.vim-3.0.zip","src_id":"16913","5":"16913","creation_date":"1321846976","6":"1321846976"},{"0":"3396","vim_version":"7.0","1":"7.0","script_version":"2.2","2":"2.2","version_comment":"zipped version.","3":"zipped version.","package":"unite-2.2.zip","4":"unite-2.2.zip","src_id":"16395","5":"16395","creation_date":"1314593379","6":"1314593379"},{"0":"3396","vim_version":"7.0","1":"7.0","script_version":"2.2","2":"2.2","version_comment":"- Added -auto-resize option.\r\n- Added <Plug>(unite_narrowing_input_history) keymapping.\r\n- Added <Plug>(unite_toggle_auto_preview) keymapping.\r\n- Added change source.\r\n- Added converter_relative_abbr and converter_relative_word.\r\n- Added file_point source and uri kind.\r\n- Added file_rec\/async source.\r\n- Added jump source.\r\n- Added jump_point source.\r\n- Added source kind.\r\n- Added unite#custom_max_candidates().\r\n- Asynchronous file_rec source(experimental).\r\n- Changed default prompt.\r\n- Deleted <ESC> default mapping.\r\n- Detect command line buffer.\r\n- Fixed args problem.\r\n- Fixed arguments parse.\r\n- Fixed buffer source error.\r\n- Fixed change_candidates().\r\n- Fixed documentation.\r\n- Fixed fatal mru bug.\r\n- Fixed file actions.\r\n- Fixed file_rec path problem.\r\n- Fixed file_rec relative path.\r\n- Fixed file_rec\/async source.\r\n- Fixed filter description.\r\n- Fixed for colorcolumn.\r\n- Fixed for cursorline.\r\n- Fixed jump_list kind.\r\n- Fixed narrowing problem.\r\n- Fixed on_close call timing.\r\n- Fixed preview action in completion kind.\r\n- Fixed preview problems.\r\n- Fixed recache candidates.\r\n- Fixed resource leak in grep source.\r\n- Fixed s:print_buffer().\r\n- Fixed source args parse.\r\n- Fixed unite#clear_message().\r\n- Fixed unite#start() description.\r\n- Fixed windows restore.\r\n- Implemented abbreviation argument.\r\n- Implemented default_action syntax sugar.\r\n- Improved <Plug>(unite_insert_leave) keymapping.\r\n- Improved async.\r\n- Improved autocmd.\r\n- Improved buffer and file_mru source abbr.\r\n- Improved command line buffer detect.\r\n- Improved command-line window detection.\r\n- Improved context source.\r\n- Improved converter_relative.\r\n- Improved cursor down\/up behavior.\r\n- Improved cursor line.\r\n- Improved delete backword path keymapping.\r\n- Improved documentation.\r\n- Improved file_rec source.\r\n- Improved file_rec.\r\n- Improved g:unite_abbr_highlight default value.\r\n- Improved grep source behavior.\r\n- Improved matcher.\r\n- Improved matcher_regexp filter.\r\n- Improved mru filtering.\r\n- Improved mru.\r\n- Improved on InsertEnter.\r\n- Improved quick match.\r\n- Improved quit session.\r\n- Improved redraw.\r\n- Improved relative converters.\r\n- Improved restore position.\r\n- Improved source action_table description.\r\n- Improved substitute pattern.\r\n- Improved toggle mark.\r\n- Improved unite#print_message() and unite#clear_message() behavior.\r\n- Improved unite-grep source.\r\n- Initialize ignorecase and smartcase value in files buffer.\r\n- Kind file inherited uri kind.\r\n- Optimized source line.\r\n- Optimized unite-file.\r\n- Set max candidates in line source.\r\n- Supported null args.\r\n- Use new vimproc function.","3":"- Added -auto-resize option.\r\n- Added <Plug>(unite_narrowing_input_history) keymapping.\r\n- Added <Plug>(unite_toggle_auto_preview) keymapping.\r\n- Added change source.\r\n- Added converter_relative_abbr and converter_relative_word.\r\n- Added file_point source and uri kind.\r\n- Added file_rec\/async source.\r\n- Added jump source.\r\n- Added jump_point source.\r\n- Added source kind.\r\n- Added unite#custom_max_candidates().\r\n- Asynchronous file_rec source(experimental).\r\n- Changed default prompt.\r\n- Deleted <ESC> default mapping.\r\n- Detect command line buffer.\r\n- Fixed args problem.\r\n- Fixed arguments parse.\r\n- Fixed buffer source error.\r\n- Fixed change_candidates().\r\n- Fixed documentation.\r\n- Fixed fatal mru bug.\r\n- Fixed file actions.\r\n- Fixed file_rec path problem.\r\n- Fixed file_rec relative path.\r\n- Fixed file_rec\/async source.\r\n- Fixed filter description.\r\n- Fixed for colorcolumn.\r\n- Fixed for cursorline.\r\n- Fixed jump_list kind.\r\n- Fixed narrowing problem.\r\n- Fixed on_close call timing.\r\n- Fixed preview action in completion kind.\r\n- Fixed preview problems.\r\n- Fixed recache candidates.\r\n- Fixed resource leak in grep source.\r\n- Fixed s:print_buffer().\r\n- Fixed source args parse.\r\n- Fixed unite#clear_message().\r\n- Fixed unite#start() description.\r\n- Fixed windows restore.\r\n- Implemented abbreviation argument.\r\n- Implemented default_action syntax sugar.\r\n- Improved <Plug>(unite_insert_leave) keymapping.\r\n- Improved async.\r\n- Improved autocmd.\r\n- Improved buffer and file_mru source abbr.\r\n- Improved command line buffer detect.\r\n- Improved command-line window detection.\r\n- Improved context source.\r\n- Improved converter_relative.\r\n- Improved cursor down\/up behavior.\r\n- Improved cursor line.\r\n- Improved delete backword path keymapping.\r\n- Improved documentation.\r\n- Improved file_rec source.\r\n- Improved file_rec.\r\n- Improved g:unite_abbr_highlight default value.\r\n- Improved grep source behavior.\r\n- Improved matcher.\r\n- Improved matcher_regexp filter.\r\n- Improved mru filtering.\r\n- Improved mru.\r\n- Improved on InsertEnter.\r\n- Improved quick match.\r\n- Improved quit session.\r\n- Improved redraw.\r\n- Improved relative converters.\r\n- Improved restore position.\r\n- Improved source action_table description.\r\n- Improved substitute pattern.\r\n- Improved toggle mark.\r\n- Improved unite#print_message() and unite#clear_message() behavior.\r\n- Improved unite-grep source.\r\n- Initialize ignorecase and smartcase value in files buffer.\r\n- Kind file inherited uri kind.\r\n- Optimized source line.\r\n- Optimized unite-file.\r\n- Set max candidates in line source.\r\n- Supported null args.\r\n- Use new vimproc function.","package":"unite-2.2.vba.vmb","4":"unite-2.2.vba.vmb","src_id":"16346","5":"16346","creation_date":"1314247532","6":"1314247532"},{"0":"3396","vim_version":"7.0","1":"7.0","script_version":"2.1","2":"2.1","version_comment":"- Added -verbose option.\r\n- Added <Plug>(unite_narrowing_path) keymapping.\r\n- Added <Plug>(unite_toggle_mark_all_candidates) keymapping.\r\n- Added <Plug>(unite_toggle_selected_candidates) keymapping.\r\n- Added direction argument in source lines.\r\n- Added file action in cdable kind.\r\n- Added g:unite_source_file_rec_min_cache_files option.\r\n- Added grep source(Thanks Sixeight).\r\n- Added line source.\r\n- Added matcher_regexp filter.\r\n- Added pattern highlight in unite-grep.\r\n- Added persist_open action.\r\n- Added rename action.\r\n- Added replace action in jump_list kind.\r\n- Added resume source.\r\n- Changed insert mode mappings.\r\n- Changed lines and grep filters.\r\n- Deleted l default keymapping.\r\n- Deleted search pattern.\r\n- Don't follow symbolic link in file_rec source.\r\n- Fixed :UniteResume error.\r\n- Fixed caching bug.\r\n- Fixed choose_action.\r\n- Fixed directory_mru error.\r\n- Fixed example.\r\n- Fixed for syntax case.\r\n- Fixed hlsearch.\r\n- Fixed initialize error.\r\n- Fixed initialize unite bug.\r\n- Fixed is_redraw flag.\r\n- Fixed kind command.\r\n- Fixed path separator problem in unite-file.\r\n- Fixed preview action.\r\n- Fixed quit unite buffer problem.\r\n- Fixed recaching.\r\n- Fixed switch_unite_buffer().\r\n- Fixed syntax error.\r\n- Fixed unite-buffer-name problem.\r\n- Fixed unite-register freeze.\r\n- Improved \"e\" mapping.\r\n- Improved alias in choose action.\r\n- Improved autocmd.\r\n- Improved cursor move behavior.\r\n- Improved detect error in mru.\r\n- Improved error highlight.\r\n- Improved file source discription.\r\n- Improved file_mru.\r\n- Improved file_rec source.\r\n- Improved g:unite_enable_start_insert option.\r\n- Improved insert enter mappings.\r\n- Improved kind tab.\r\n- Improved matcher.\r\n- Improved narrow action.\r\n- Improved preview action in jump_list.\r\n- Improved redraw flag.\r\n- Improved redraw.\r\n- Improved s:recache_candidates().\r\n- Improved unite -immediately behavior.\r\n- Improved unite buffer initialize.\r\n- Improved unite#print_error().\r\n- Improved unite-grep.\r\n- Supported redraw in source lines.\r\n- Updated vital.vim.","3":"- Added -verbose option.\r\n- Added <Plug>(unite_narrowing_path) keymapping.\r\n- Added <Plug>(unite_toggle_mark_all_candidates) keymapping.\r\n- Added <Plug>(unite_toggle_selected_candidates) keymapping.\r\n- Added direction argument in source lines.\r\n- Added file action in cdable kind.\r\n- Added g:unite_source_file_rec_min_cache_files option.\r\n- Added grep source(Thanks Sixeight).\r\n- Added line source.\r\n- Added matcher_regexp filter.\r\n- Added pattern highlight in unite-grep.\r\n- Added persist_open action.\r\n- Added rename action.\r\n- Added replace action in jump_list kind.\r\n- Added resume source.\r\n- Changed insert mode mappings.\r\n- Changed lines and grep filters.\r\n- Deleted l default keymapping.\r\n- Deleted search pattern.\r\n- Don't follow symbolic link in file_rec source.\r\n- Fixed :UniteResume error.\r\n- Fixed caching bug.\r\n- Fixed choose_action.\r\n- Fixed directory_mru error.\r\n- Fixed example.\r\n- Fixed for syntax case.\r\n- Fixed hlsearch.\r\n- Fixed initialize error.\r\n- Fixed initialize unite bug.\r\n- Fixed is_redraw flag.\r\n- Fixed kind command.\r\n- Fixed path separator problem in unite-file.\r\n- Fixed preview action.\r\n- Fixed quit unite buffer problem.\r\n- Fixed recaching.\r\n- Fixed switch_unite_buffer().\r\n- Fixed syntax error.\r\n- Fixed unite-buffer-name problem.\r\n- Fixed unite-register freeze.\r\n- Improved \"e\" mapping.\r\n- Improved alias in choose action.\r\n- Improved autocmd.\r\n- Improved cursor move behavior.\r\n- Improved detect error in mru.\r\n- Improved error highlight.\r\n- Improved file source discription.\r\n- Improved file_mru.\r\n- Improved file_rec source.\r\n- Improved g:unite_enable_start_insert option.\r\n- Improved insert enter mappings.\r\n- Improved kind tab.\r\n- Improved matcher.\r\n- Improved narrow action.\r\n- Improved preview action in jump_list.\r\n- Improved redraw flag.\r\n- Improved redraw.\r\n- Improved s:recache_candidates().\r\n- Improved unite -immediately behavior.\r\n- Improved unite buffer initialize.\r\n- Improved unite#print_error().\r\n- Improved unite-grep.\r\n- Supported redraw in source lines.\r\n- Updated vital.vim.","package":"unite-ver.2.1.vba","4":"unite-ver.2.1.vba","src_id":"16030","5":"16030","creation_date":"1309836324","6":"1309836324"},{"0":"3396","vim_version":"7.0","1":"7.0","script_version":"2.0","2":"2.0","version_comment":"- Add '..' directory in unite source.\r\n- Add history in kind command.\r\n- Added --no-start-insert option.\r\n- Added -immediately option.\r\n- Added -vertical, -horizontal, -direction options.\r\n- Added <Plug>(unite_delete_backward_path) keymapping.\r\n- Added <Plug>(unite_restart) keymapping.\r\n- Added README.\r\n- Added col and completion option.\r\n- Added command source.\r\n- Added completion kind.\r\n- Added default matcher.\r\n- Added edit action in command kind.\r\n- Added filter help.\r\n- Added from field in action.\r\n- Added g:unite_cursor_line_highlight and g:unite_abbr_highlight options.\r\n- Added g:unite_source_file_rec_ignore_pattern option.\r\n- Added ignorecase and smartcase buffer_name options.\r\n- Added is_async context flag.\r\n- Added matcher_default, sorter_default, converter_default.\r\n- Added no-current option in window and tab source.\r\n- Added output source.\r\n- Added post_filter hook.\r\n- Added sorter_word.\r\n- Added unite#set_buffer_name_option() help.\r\n- Added unite#version().\r\n- Added unite-source-attribute-source__ description.\r\n- Caching file_rec source.\r\n- Changed :UniteWithInputDirectory behavior.\r\n- Changed available_xxx API names to get_xxx.\r\n- Changed file_rec message format.\r\n- Changed input_gather_candidates() to change_candidates().\r\n- Changed on_close timing.\r\n- Changed unite#loaded_source_names_with_args().\r\n- Changed volatile source.\r\n- Changed yank action.\r\n- Chomp last \/.\r\n- Deleted :NeoComplCacheCachingBuffer.\r\n- Deleted highlight off.\r\n- Deleted unused tag.\r\n- Don't save directory in file_mru.\r\n- Fixed :NeoComplCacheCachingBuffer error.\r\n- Fixed :UniteResume bug.\r\n- Fixed auto preview bug.\r\n- Fixed buffer source.\r\n- Fixed choose action.\r\n- Fixed choose_action documentation.\r\n- Fixed completion kind.\r\n- Fixed context bug.\r\n- Fixed default action bug.\r\n- Fixed escape jump_list.\r\n- Fixed file_mru error.\r\n- Fixed file_rec index.\r\n- Fixed file_rec path problem.\r\n- Fixed filtering bug.\r\n- Fixed fnamemodify().\r\n- Fixed get action table bug.\r\n- Fixed help.\r\n- Fixed highlight settings.\r\n- Fixed highlight.\r\n- Fixed hlsearch bug.\r\n- Fixed is_insert error.\r\n- Fixed is_redraw bug.\r\n- Fixed jump_list escape.\r\n- Fixed kind completion bug.\r\n- Fixed narrowing action.\r\n- Fixed narrowing bugs.\r\n- Fixed priority sort bug.\r\n- Fixed quick match bug.\r\n- Fixed quick match error.\r\n- Fixed redraw buffer source bug.\r\n- Fixed redraw candidates bug.\r\n- Fixed set search pattern.\r\n- Fixed sidescrolloff problem.\r\n- Fixed source file path problem.\r\n- Fixed source register max width.\r\n- Fixed substitute input.\r\n- Fixed unite buffer name.\r\n- Fixed unite source.\r\n- Fixed unite#custom_filters() bug.\r\n- Fixed unite#custom_filters() error.\r\n- Fixed unite#get_default_action().\r\n- Fixed unite-command.\r\n- Fixed unite-register freeze bug.\r\n- Fixed version number.\r\n- Ignore invalid action.\r\n- Implemented -auto-preview option.\r\n- Implemented asynchronous get candidates.\r\n- Implemented auto mkdir().\r\n- Implemented buffer name filters.\r\n- Implemented dummy candidates.\r\n- Implemented filters.\r\n- Implemented input_gather_candidates().\r\n- Implemented mapping source.\r\n- Implemented mkdir action.\r\n- Implemented position restore.\r\n- Implemented preview window check.\r\n- Implemented sorter and matcher.\r\n- Implemented source highlight.\r\n- Implemented unite action source.\r\n- Implemented unite#clear_message().\r\n- Implemented unite#print_message().\r\n- Implemented vimfiler and tabvimfiler actions.\r\n- Improved args.\r\n- Improved auto preview behavior.\r\n- Improved auto preview.\r\n- Improved buffer abbr.\r\n- Improved command action.\r\n- Improved command narrow action.\r\n- Improved command source.\r\n- Improved completion kind.\r\n- Improved context.\r\n- Improved default substitute pattern.\r\n- Improved delete buffer action.\r\n- Improved directory_mru source.\r\n- Improved documentation.\r\n- Improved file source.\r\n- Improved file_mru source.\r\n- Improved file_rec path.\r\n- Improved file_rec source.\r\n- Improved highlight off.\r\n- Improved initialize sources.\r\n- Improved initialize.\r\n- Improved insert leave.\r\n- Improved jump_list.\r\n- Improved loop cursor down\/up.\r\n- Improved narrowing behavior.\r\n- Improved normal mode redraw.\r\n- Improved quick match message.\r\n- Improved redraw.\r\n- Improved rotate sources.\r\n- Improved sort.\r\n- Improved source arguments description.\r\n- Improved source file dummy candidates.\r\n- Improved source file.\r\n- Improved syntax.\r\n- Improved traverse message in file_rec source.\r\n- Improved truncate.\r\n- Improved unite action.\r\n- Improved unite#print_error() and unite#print_message().\r\n- Improved unite-command.\r\n- Improved unite-output.\r\n- Improved unite-register.\r\n- Ommitable candidates source name.\r\n- Optimized initialization.\r\n- Refactored buffer name options.\r\n- Renamed unite#custom_filter() to unite#custom_filters().\r\n- Set cpoptions.\r\n- Supported neocomplcache manual completion.\r\n- Supported yanktmp in register source.\r\n- Use strdisplaywidth().\r\n- gather_candidates attribute is optional.","3":"- Add '..' directory in unite source.\r\n- Add history in kind command.\r\n- Added --no-start-insert option.\r\n- Added -immediately option.\r\n- Added -vertical, -horizontal, -direction options.\r\n- Added <Plug>(unite_delete_backward_path) keymapping.\r\n- Added <Plug>(unite_restart) keymapping.\r\n- Added README.\r\n- Added col and completion option.\r\n- Added command source.\r\n- Added completion kind.\r\n- Added default matcher.\r\n- Added edit action in command kind.\r\n- Added filter help.\r\n- Added from field in action.\r\n- Added g:unite_cursor_line_highlight and g:unite_abbr_highlight options.\r\n- Added g:unite_source_file_rec_ignore_pattern option.\r\n- Added ignorecase and smartcase buffer_name options.\r\n- Added is_async context flag.\r\n- Added matcher_default, sorter_default, converter_default.\r\n- Added no-current option in window and tab source.\r\n- Added output source.\r\n- Added post_filter hook.\r\n- Added sorter_word.\r\n- Added unite#set_buffer_name_option() help.\r\n- Added unite#version().\r\n- Added unite-source-attribute-source__ description.\r\n- Caching file_rec source.\r\n- Changed :UniteWithInputDirectory behavior.\r\n- Changed available_xxx API names to get_xxx.\r\n- Changed file_rec message format.\r\n- Changed input_gather_candidates() to change_candidates().\r\n- Changed on_close timing.\r\n- Changed unite#loaded_source_names_with_args().\r\n- Changed volatile source.\r\n- Changed yank action.\r\n- Chomp last \/.\r\n- Deleted :NeoComplCacheCachingBuffer.\r\n- Deleted highlight off.\r\n- Deleted unused tag.\r\n- Don't save directory in file_mru.\r\n- Fixed :NeoComplCacheCachingBuffer error.\r\n- Fixed :UniteResume bug.\r\n- Fixed auto preview bug.\r\n- Fixed buffer source.\r\n- Fixed choose action.\r\n- Fixed choose_action documentation.\r\n- Fixed completion kind.\r\n- Fixed context bug.\r\n- Fixed default action bug.\r\n- Fixed escape jump_list.\r\n- Fixed file_mru error.\r\n- Fixed file_rec index.\r\n- Fixed file_rec path problem.\r\n- Fixed filtering bug.\r\n- Fixed fnamemodify().\r\n- Fixed get action table bug.\r\n- Fixed help.\r\n- Fixed highlight settings.\r\n- Fixed highlight.\r\n- Fixed hlsearch bug.\r\n- Fixed is_insert error.\r\n- Fixed is_redraw bug.\r\n- Fixed jump_list escape.\r\n- Fixed kind completion bug.\r\n- Fixed narrowing action.\r\n- Fixed narrowing bugs.\r\n- Fixed priority sort bug.\r\n- Fixed quick match bug.\r\n- Fixed quick match error.\r\n- Fixed redraw buffer source bug.\r\n- Fixed redraw candidates bug.\r\n- Fixed set search pattern.\r\n- Fixed sidescrolloff problem.\r\n- Fixed source file path problem.\r\n- Fixed source register max width.\r\n- Fixed substitute input.\r\n- Fixed unite buffer name.\r\n- Fixed unite source.\r\n- Fixed unite#custom_filters() bug.\r\n- Fixed unite#custom_filters() error.\r\n- Fixed unite#get_default_action().\r\n- Fixed unite-command.\r\n- Fixed unite-register freeze bug.\r\n- Fixed version number.\r\n- Ignore invalid action.\r\n- Implemented -auto-preview option.\r\n- Implemented asynchronous get candidates.\r\n- Implemented auto mkdir().\r\n- Implemented buffer name filters.\r\n- Implemented dummy candidates.\r\n- Implemented filters.\r\n- Implemented input_gather_candidates().\r\n- Implemented mapping source.\r\n- Implemented mkdir action.\r\n- Implemented position restore.\r\n- Implemented preview window check.\r\n- Implemented sorter and matcher.\r\n- Implemented source highlight.\r\n- Implemented unite action source.\r\n- Implemented unite#clear_message().\r\n- Implemented unite#print_message().\r\n- Implemented vimfiler and tabvimfiler actions.\r\n- Improved args.\r\n- Improved auto preview behavior.\r\n- Improved auto preview.\r\n- Improved buffer abbr.\r\n- Improved command action.\r\n- Improved command narrow action.\r\n- Improved command source.\r\n- Improved completion kind.\r\n- Improved context.\r\n- Improved default substitute pattern.\r\n- Improved delete buffer action.\r\n- Improved directory_mru source.\r\n- Improved documentation.\r\n- Improved file source.\r\n- Improved file_mru source.\r\n- Improved file_rec path.\r\n- Improved file_rec source.\r\n- Improved highlight off.\r\n- Improved initialize sources.\r\n- Improved initialize.\r\n- Improved insert leave.\r\n- Improved jump_list.\r\n- Improved loop cursor down\/up.\r\n- Improved narrowing behavior.\r\n- Improved normal mode redraw.\r\n- Improved quick match message.\r\n- Improved redraw.\r\n- Improved rotate sources.\r\n- Improved sort.\r\n- Improved source arguments description.\r\n- Improved source file dummy candidates.\r\n- Improved source file.\r\n- Improved syntax.\r\n- Improved traverse message in file_rec source.\r\n- Improved truncate.\r\n- Improved unite action.\r\n- Improved unite#print_error() and unite#print_message().\r\n- Improved unite-command.\r\n- Improved unite-output.\r\n- Improved unite-register.\r\n- Ommitable candidates source name.\r\n- Optimized initialization.\r\n- Refactored buffer name options.\r\n- Renamed unite#custom_filter() to unite#custom_filters().\r\n- Set cpoptions.\r\n- Supported neocomplcache manual completion.\r\n- Supported yanktmp in register source.\r\n- Use strdisplaywidth().\r\n- gather_candidates attribute is optional.","package":"unite-2.0.vba","4":"unite-2.0.vba","src_id":"15558","5":"15558","creation_date":"1304227525","6":"1304227525"},{"0":"3396","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"unite-1.0.vba","4":"unite-1.0.vba","src_id":"14711","5":"14711","creation_date":"1294543731","6":"1294543731"}]},"3395":{"script_id":"3395","0":"3395","script_name":"chapa","1":"chapa","script_type":"utility","2":"utility","summary":"go to, comment or visually select the next\/previous function, class or method","3":"go to, comment or visually select the next\/previous function, class or method","description":"Allows you to move to previous\/next class, function or method \r\n\r\ntoggle comments, fold or visually select the next\/previous class, function or method. \r\n\r\nCurrently supports Python and JavaScript\r\n\r\nWatch the screencast:  http:\/\/vimeo.com\/19016562\r\n\r\n\r\nProject and documentation lives here:\r\nhttps:\/\/github.com\/alfredodeza\/chapa.vim ","4":"Allows you to move to previous\/next class, function or method \r\n\r\ntoggle comments, fold or visually select the next\/previous class, function or method. \r\n\r\nCurrently supports Python and JavaScript\r\n\r\nWatch the screencast:  http:\/\/vimeo.com\/19016562\r\n\r\n\r\nProject and documentation lives here:\r\nhttps:\/\/github.com\/alfredodeza\/chapa.vim ","install_details":"Copy the chapa.vim file to your ftplugin directory but should work with Pathogen as well.","5":"Copy the chapa.vim file to your ftplugin directory but should work with Pathogen as well.","first_name":"Alfredo","6":"Alfredo","last_name":"Deza","7":"Deza","releases":[{"0":"3395","vim_version":"7.0","1":"7.0","script_version":"1.1.2","2":"1.1.2","version_comment":"Fixes some debug echo's that were left behind.","3":"Fixes some debug echo's that were left behind.","package":"chapa.tar.gz","4":"chapa.tar.gz","src_id":"15007","5":"15007","creation_date":"1297709046","6":"1297709046"},{"0":"3395","vim_version":"7.0","1":"7.0","script_version":"1.1.0","2":"1.1.0","version_comment":"Adds Folding Capabilities (just Python for now)\r\nMakes the repeat mappings optional.\r\nDrops Ruby support (other plugins already take care of same overlapping functionality)\r\n","3":"Adds Folding Capabilities (just Python for now)\r\nMakes the repeat mappings optional.\r\nDrops Ruby support (other plugins already take care of same overlapping functionality)\r\n","package":"chapa.tar.gz","4":"chapa.tar.gz","src_id":"14958","5":"14958","creation_date":"1296877630","6":"1296877630"},{"0":"3395","vim_version":"7.0","1":"7.0","script_version":"1.0.1","2":"1.0.1","version_comment":"Minor bug fixes that deal with object living at the end of the file. It also fixes weird comment toggling to match exactly what you are asking for and nothing else.","3":"Minor bug fixes that deal with object living at the end of the file. It also fixes weird comment toggling to match exactly what you are asking for and nothing else.","package":"chapa.tar.gz","4":"chapa.tar.gz","src_id":"14917","5":"14917","creation_date":"1296415327","6":"1296415327"},{"0":"3395","vim_version":"7.0","1":"7.0","script_version":"1.0.0","2":"1.0.0","version_comment":"Adds JavasScript support! same features except only applied to functions (no classes or methods)","3":"Adds JavasScript support! same features except only applied to functions (no classes or methods)","package":"chapa.tar.gz","4":"chapa.tar.gz","src_id":"14779","5":"14779","creation_date":"1295310605","6":"1295310605"},{"0":"3395","vim_version":"7.0","1":"7.0","script_version":"0.0.9","2":"0.0.9","version_comment":"Minor update that fixes better matching of Ruby end blocks.","3":"Minor update that fixes better matching of Ruby end blocks.","package":"chapa.tar.gz","4":"chapa.tar.gz","src_id":"14764","5":"14764","creation_date":"1295223038","6":"1295223038"},{"0":"3395","vim_version":"7.0","1":"7.0","script_version":"0.0.8","2":"0.0.8","version_comment":"Adds better support for Ruby and ending blocks. ","3":"Adds better support for Ruby and ending blocks. ","package":"chapa.tar.gz","4":"chapa.tar.gz","src_id":"14760","5":"14760","creation_date":"1295148250","6":"1295148250"},{"0":"3395","vim_version":"7.0","1":"7.0","script_version":"0.0.7","2":"0.0.7","version_comment":"Fixes a problem with moving from\/to methods and makes the Repeat calls available as part of the Plugin","3":"Fixes a problem with moving from\/to methods and makes the Repeat calls available as part of the Plugin","package":"chapa.tar.gz","4":"chapa.tar.gz","src_id":"14748","5":"14748","creation_date":"1295055264","6":"1295055264"},{"0":"3395","vim_version":"7.0","1":"7.0","script_version":"0.0.6","2":"0.0.6","version_comment":"You can now toggle comments for the N class, method or function and repeat any movement command with <C-h> and <C-l>. \r\nIt also fixes some issues with defining better being \"inside\" an actual object.","3":"You can now toggle comments for the N class, method or function and repeat any movement command with <C-h> and <C-l>. \r\nIt also fixes some issues with defining better being \"inside\" an actual object.","package":"chapa.tar.gz","4":"chapa.tar.gz","src_id":"14744","5":"14744","creation_date":"1294971558","6":"1294971558"},{"0":"3395","vim_version":"7.0","1":"7.0","script_version":"0.0.5","2":"0.0.5","version_comment":"Adds commenting capabilities for next\/previous N method, class, function and default mappings.\r\nAlso provides more accurate visual selection by avoiding whitespace at the end of blocks.","3":"Adds commenting capabilities for next\/previous N method, class, function and default mappings.\r\nAlso provides more accurate visual selection by avoiding whitespace at the end of blocks.","package":"chapa.tar.gz","4":"chapa.tar.gz","src_id":"14739","5":"14739","creation_date":"1294884027","6":"1294884027"},{"0":"3395","vim_version":"7.0","1":"7.0","script_version":"0.0.4","2":"0.0.4","version_comment":"Fixes a bug with visual selection and adds count for visual selections (eg. visual select 3rd next method)","3":"Fixes a bug with visual selection and adds count for visual selections (eg. visual select 3rd next method)","package":"chapa.tar.gz","4":"chapa.tar.gz","src_id":"14727","5":"14727","creation_date":"1294709350","6":"1294709350"},{"0":"3395","vim_version":"7.0","1":"7.0","script_version":"0.0.3","2":"0.0.3","version_comment":"Adds count for movements (e.g. move to 3 previous classes)\r\nAdd <Plug> before each plugin call in your mappings. Breaks compatibility for earlier versions. ","3":"Adds count for movements (e.g. move to 3 previous classes)\r\nAdd <Plug> before each plugin call in your mappings. Breaks compatibility for earlier versions. ","package":"chapa.tar.gz","4":"chapa.tar.gz","src_id":"14724","5":"14724","creation_date":"1294686689","6":"1294686689"},{"0":"3395","vim_version":"7.0","1":"7.0","script_version":"0.0.2","2":"0.0.2","version_comment":"Adds 8 public movement and selection calls to the plugin - but breaks compatibility with previous version ","3":"Adds 8 public movement and selection calls to the plugin - but breaks compatibility with previous version ","package":"chapa.tar.gz","4":"chapa.tar.gz","src_id":"14718","5":"14718","creation_date":"1294622598","6":"1294622598"}]},"3394":{"script_id":"3394","0":"3394","script_name":"BOOKMARKS: Mark & Highlight Full Lines","1":"BOOKMARKS: Mark & Highlight Full Lines","script_type":"utility","2":"utility","summary":"Easily Highlight Lines with Marks, and Add\/Remove Marks","3":"Easily Highlight Lines with Marks, and Add\/Remove Marks","description":"Inspired by Kate 'bookmarks' and other scripts in this site, I devised a new way to mark full lines and highlight them.\r\n\r\nThe idea is to mark lines and then jump from one to the other, in an easier way than the one Vim provides.\r\n\r\nLines with markers are highlighted, which is convenient to visually spot where the mark is.\r\n\r\nOne does not need to remember which markers are already in use and which are free anymore, just add marks and remove marks, and the script will manage where to store them or free them.\r\n\r\nUSAGE:\r\n<F1>            Turn on\/update highlighting for all lines with markers\r\n<F2>            Turn off highlighting for lines with markers\r\n<SHIFT-F2> Erase all markers [a-z]\r\n<F5>             Add a mark on the current line (and highlight)\r\n<SHIFT-F5> Remove the mark on the current line\r\n\r\nThen, just jump from one mark to the next using the classic [' and ]' jumps\r\n\r\nTry it! it's nice!\r\n\r\nNOTE:\r\nOf course, the highlight group I define (\"Marks\") should be tweaked to one's taste, and the same applies to the keyboard mappings.\r\n\r\nNOTE-UPDATE:\r\nThe classic marking method (ie. typing 'ma', 'mb', 'mc'...) can be used in combination with this one, but one has to be careful not to overwrite an existing mark. Check with the :marks command. HINT: the code marks from the 'a' to the 'z', so if there are not too many marks, one can safely assume that the last ones ('z 'x 'y 'w ...) are safe to use.\r\n\r\nEnjoy...","4":"Inspired by Kate 'bookmarks' and other scripts in this site, I devised a new way to mark full lines and highlight them.\r\n\r\nThe idea is to mark lines and then jump from one to the other, in an easier way than the one Vim provides.\r\n\r\nLines with markers are highlighted, which is convenient to visually spot where the mark is.\r\n\r\nOne does not need to remember which markers are already in use and which are free anymore, just add marks and remove marks, and the script will manage where to store them or free them.\r\n\r\nUSAGE:\r\n<F1>            Turn on\/update highlighting for all lines with markers\r\n<F2>            Turn off highlighting for lines with markers\r\n<SHIFT-F2> Erase all markers [a-z]\r\n<F5>             Add a mark on the current line (and highlight)\r\n<SHIFT-F5> Remove the mark on the current line\r\n\r\nThen, just jump from one mark to the next using the classic [' and ]' jumps\r\n\r\nTry it! it's nice!\r\n\r\nNOTE:\r\nOf course, the highlight group I define (\"Marks\") should be tweaked to one's taste, and the same applies to the keyboard mappings.\r\n\r\nNOTE-UPDATE:\r\nThe classic marking method (ie. typing 'ma', 'mb', 'mc'...) can be used in combination with this one, but one has to be careful not to overwrite an existing mark. Check with the :marks command. HINT: the code marks from the 'a' to the 'z', so if there are not too many marks, one can safely assume that the last ones ('z 'x 'y 'w ...) are safe to use.\r\n\r\nEnjoy...","install_details":"","5":"","first_name":"Ignacio","6":"Ignacio","last_name":"Nunez","7":"Nunez","releases":[{"0":"3394","vim_version":"7.0","1":"7.0","script_version":"2.03","2":"2.03","version_comment":"Fix terminal bg color","3":"Fix terminal bg color","package":"markHL.vim","4":"markHL.vim","src_id":"21611","5":"21611","creation_date":"1394712208","6":"1394712208"},{"0":"3394","vim_version":"7.0","1":"7.0","script_version":"2.02","2":"2.02","version_comment":"Added <silent> mode for the mappings","3":"Added <silent> mode for the mappings","package":"markHL.vim","4":"markHL.vim","src_id":"14918","5":"14918","creation_date":"1296425364","6":"1296425364"},{"0":"3394","vim_version":"7.0","1":"7.0","script_version":"2.01","2":"2.01","version_comment":"Added color highlighting for GUI","3":"Added color highlighting for GUI","package":"markHL.vim","4":"markHL.vim","src_id":"14783","5":"14783","creation_date":"1295374025","6":"1295374025"},{"0":"3394","vim_version":"7.0","1":"7.0","script_version":"2","2":"2","version_comment":"Now, the code can handle normal marking and my own method simultaneously.","3":"Now, the code can handle normal marking and my own method simultaneously.","package":"markHL.vim","4":"markHL.vim","src_id":"14713","5":"14713","creation_date":"1294577098","6":"1294577098"},{"0":"3394","vim_version":"7.0","1":"7.0","script_version":"1","2":"1","version_comment":"Initial upload","3":"Initial upload","package":"markHL.vim","4":"markHL.vim","src_id":"14709","5":"14709","creation_date":"1294511706","6":"1294511706"}]},"3393":{"script_id":"3393","0":"3393","script_name":"localrc.vim","1":"localrc.vim","script_type":"utility","2":"utility","summary":"Enable configuration file of each directory.","3":"Enable configuration file of each directory.","description":"You can put a configuration file for the files below the certain directory.\r\n\r\nThe configuration file is a Vim script of a decided file name like .vimrc.\r\nThe file name is specified by |g:localrc_filename|.\r\n\r\nConfiguration file applied only to a specific filetype can be put.  The file\r\nname is specified by |g:localrc_filetype|.\r\n\r\nWhen two or more configuration files exist, it is sequentially loaded from a\r\nshallow hierarchy.\r\nFor example:\r\n\t~\/\r\n\t|- .local.vimrc\t\t(1)\r\n\t`- project\/\r\n\t   |- .local.vimrc\t(2)\r\n\t   `- src\/\r\n\t      |- .local.vimrc\t(3)\r\n\t      `- main.c\r\nIn this case, when main.c is loaded, the configuration files are loaded in order\r\nof the number.\r\n\r\nLatest Version:\r\nhttps:\/\/github.com\/thinca\/vim-localrc","4":"You can put a configuration file for the files below the certain directory.\r\n\r\nThe configuration file is a Vim script of a decided file name like .vimrc.\r\nThe file name is specified by |g:localrc_filename|.\r\n\r\nConfiguration file applied only to a specific filetype can be put.  The file\r\nname is specified by |g:localrc_filetype|.\r\n\r\nWhen two or more configuration files exist, it is sequentially loaded from a\r\nshallow hierarchy.\r\nFor example:\r\n\t~\/\r\n\t|- .local.vimrc\t\t(1)\r\n\t`- project\/\r\n\t   |- .local.vimrc\t(2)\r\n\t   `- src\/\r\n\t      |- .local.vimrc\t(3)\r\n\t      `- main.c\r\nIn this case, when main.c is loaded, the configuration files are loaded in order\r\nof the number.\r\n\r\nLatest Version:\r\nhttps:\/\/github.com\/thinca\/vim-localrc","install_details":"","5":"","first_name":"thinca","6":"thinca","last_name":" ","7":" ","releases":[{"0":"3393","vim_version":"7.2","1":"7.2","script_version":"0.1.2","2":"0.1.2","version_comment":"- Improved the default value of |g:localrc_filetype|.\r\n- Use \"%\" instead of \"<afile>\".","3":"- Improved the default value of |g:localrc_filetype|.\r\n- Use \"%\" instead of \"<afile>\".","package":"vim-localrc-0.1.2.zip","4":"vim-localrc-0.1.2.zip","src_id":"14858","5":"14858","creation_date":"1295968759","6":"1295968759"},{"0":"3393","vim_version":"7.2","1":"7.2","script_version":"0.1.0","2":"0.1.0","version_comment":"Initial upload","3":"Initial upload","package":"vim-localrc-0.1.0.zip","4":"vim-localrc-0.1.0.zip","src_id":"14702","5":"14702","creation_date":"1294429518","6":"1294429518"}]},"3392":{"script_id":"3392","0":"3392","script_name":"hdl_plugin","1":"hdl_plugin","script_type":"indent","2":"indent","summary":"Vhdl\/Verilog fast instant and generate testbench file","3":"Vhdl\/Verilog fast instant and generate testbench file","description":"I will updata this plugin in this page: \r\nhttp:\/\/www.vim.org\/scripts\/script.php?script_id=3420 \r\n  ","4":"I will updata this plugin in this page: \r\nhttp:\/\/www.vim.org\/scripts\/script.php?script_id=3420 \r\n  ","install_details":"","5":"","first_name":"\u9648","6":"陈","last_name":"\u52c7","7":"勇","releases":[{"0":"3392","vim_version":"7.0","1":"7.0","script_version":"v2.4","2":"v2.4","version_comment":"Fixed Some Bugs","3":"Fixed Some Bugs","package":"hdl_plugin.vim","4":"hdl_plugin.vim","src_id":"14852","5":"14852","creation_date":"1295932132","6":"1295932132"}]},"3391":{"script_id":"3391","0":"3391","script_name":"line-based_jump_memory.vim","1":"line-based_jump_memory.vim","script_type":"utility","2":"utility","summary":"Allows to quickly return to the original position after a jump on the line","3":"Allows to quickly return to the original position after a jump on the line","description":"It marks the current cursor position just before a line-based jump command is pressed (e.g. $, w, f, ;, <Home>, etc.). Hitting CTRL-O (or `' or ``) will put the cursor back to its original position. It works for both normal and insert mode line-based commands.","4":"It marks the current cursor position just before a line-based jump command is pressed (e.g. $, w, f, ;, <Home>, etc.). Hitting CTRL-O (or `' or ``) will put the cursor back to its original position. It works for both normal and insert mode line-based commands.","install_details":"Copy the line-based_jump_memory.vim file into Vim's plug-in directory (usually $HOME\/.vim\/plugin\/ or something like that).","5":"Copy the line-based_jump_memory.vim file into Vim's plug-in directory (usually $HOME\/.vim\/plugin\/ or something like that).","first_name":"Douglas","6":"Douglas","last_name":"Augusto","7":"Augusto","releases":[{"0":"3391","vim_version":"7.0","1":"7.0","script_version":"0.2.1","2":"0.2.1","version_comment":"Fixes the proper handling of the double-quote char (\") argument in the commands f,t,F,T.","3":"Fixes the proper handling of the double-quote char (\") argument in the commands f,t,F,T.","package":"line-based_jump_memory.vim","4":"line-based_jump_memory.vim","src_id":"14698","5":"14698","creation_date":"1294386325","6":"1294386325"},{"0":"3391","vim_version":"7.0","1":"7.0","script_version":"0.2.0","2":"0.2.0","version_comment":"- Fixed the plug-in file name.\r\n- Added two user-configurable variables: (i) The minimum character motion (distance) needed to produce a mark; (ii) Whether a jump that exits the current line is going to be marked or not.\r\n- Support for mouse click jumps.\r\n- Code reorganization, improvements and clean up.","3":"- Fixed the plug-in file name.\r\n- Added two user-configurable variables: (i) The minimum character motion (distance) needed to produce a mark; (ii) Whether a jump that exits the current line is going to be marked or not.\r\n- Support for mouse click jumps.\r\n- Code reorganization, improvements and clean up.","package":"line-based_jump_memory.vim","4":"line-based_jump_memory.vim","src_id":"14695","5":"14695","creation_date":"1294374145","6":"1294374145"},{"0":"3391","vim_version":"7.0","1":"7.0","script_version":"0.1.0","2":"0.1.0","version_comment":"Initial upload","3":"Initial upload","package":"line-based_jump_list.vim","4":"line-based_jump_list.vim","src_id":"14686","5":"14686","creation_date":"1294255764","6":"1294255764"}]},"3390":{"script_id":"3390","0":"3390","script_name":"iim.vim","1":"iim.vim","script_type":"syntax","2":"syntax","summary":"Syntax Highlighting for iMacros","3":"Syntax Highlighting for iMacros","description":"This is a syntax highlighting script for the iMacros scripting language:\r\nhttp:\/\/wiki.imacros.net\/Main_Page","4":"This is a syntax highlighting script for the iMacros scripting language:\r\nhttp:\/\/wiki.imacros.net\/Main_Page","install_details":"Zip file contains:\r\nplugin\/iim.vim\r\nsyntax\/iim.vim\r\n\r\nBoth need to be dropped in your VIM runtimepath.\r\nplugin\/iim.vim is just for automatically setting the filetype so that any .iim files will have this syntax highlighting applied.\r\nsyntax\/iim.vim is the syntax file itself.","5":"Zip file contains:\r\nplugin\/iim.vim\r\nsyntax\/iim.vim\r\n\r\nBoth need to be dropped in your VIM runtimepath.\r\nplugin\/iim.vim is just for automatically setting the filetype so that any .iim files will have this syntax highlighting applied.\r\nsyntax\/iim.vim is the syntax file itself.","first_name":"Chib","6":"Chib","last_name":"-","7":"-","releases":[{"0":"3390","vim_version":"5.7","1":"5.7","script_version":"0.4","2":"0.4","version_comment":"Added a couple more highlight groups and changed around some of the colour associations so they work better with 256 colour color-schemes.","3":"Added a couple more highlight groups and changed around some of the colour associations so they work better with 256 colour color-schemes.","package":"iim.zip","4":"iim.zip","src_id":"14854","5":"14854","creation_date":"1295935008","6":"1295935008"},{"0":"3390","vim_version":"5.7","1":"5.7","script_version":"0.3","2":"0.3","version_comment":"Initial upload","3":"Initial upload","package":"iim.zip","4":"iim.zip","src_id":"14673","5":"14673","creation_date":"1294048461","6":"1294048461"}]},"3389":{"script_id":"3389","0":"3389","script_name":"opencl.vim","1":"opencl.vim","script_type":"syntax","2":"syntax","summary":"script converted into unix fileformat made by Terence Ou","3":"script converted into unix fileformat made by Terence Ou","description":"Script by Terence Ou uploaded here:\r\nhttp:\/\/www.vim.org\/scripts\/script.php?script_id=3157\r\n(Thanks Terence ! Great contrib :D)\r\nbut to make it working I needed to change fileencoding into unix (as I use Vim under Linux ).\r\n\r\n","4":"Script by Terence Ou uploaded here:\r\nhttp:\/\/www.vim.org\/scripts\/script.php?script_id=3157\r\n(Thanks Terence ! Great contrib :D)\r\nbut to make it working I needed to change fileencoding into unix (as I use Vim under Linux ).\r\n\r\n","install_details":"Checkout Terence instructions:\r\nhttp:\/\/www.vim.org\/scripts\/script.php?script_id=3157","5":"Checkout Terence instructions:\r\nhttp:\/\/www.vim.org\/scripts\/script.php?script_id=3157","first_name":"Grzegorz","6":"Grzegorz","last_name":"Wierzowiecki","7":"Wierzowiecki","releases":[{"0":"3389","vim_version":"6.0","1":"6.0","script_version":"1.1","2":"1.1","version_comment":"Initial upload","3":"Initial upload","package":"opencl.vim","4":"opencl.vim","src_id":"14670","5":"14670","creation_date":"1293927178","6":"1293927178"}]},"3388":{"script_id":"3388","0":"3388","script_name":"polytonic.utf-8.spl","1":"polytonic.utf-8.spl","script_type":"utility","2":"utility","summary":"Spell checking for multi accented (polytonic) Greek. ","3":"Spell checking for multi accented (polytonic) Greek. ","description":"---------------------------------------------------------------------\r\nSpell file for multi accented (also known as polytonic) Greek. \r\n---------------------------------------------------------------------\r\n\r\nThis spell file is for checking the spelling of texts typed in multi \r\naccented (or polytonic) Greek. It is useful to Greek scholars \r\n(hellenists) as well as native Greek speakers who prefer to write \r\nin the traditional multi accented script.  \r\n\r\nThe word list covers all the ancient and modern Greek vocabulary.\r\nAbout 1.5 million words all spelled in the traditional polytonic system. \r\n\r\nThe ancient Greek word list is derived from several corpora like \r\nPerseus [2], and TLG [3] and other sources.\r\n\r\nThe modern Greek word list is derived from the ispell dictionary el_GR [1]\r\nbut all the words have been appropriately accentuated. This spell file\r\nwill flag monotonic spelling as errors (and rightfully so).\r\n\r\nThe two lists are combined, cleaned of double entries (there was a large \r\noverlap) and sorted. Last syllable varia (grave accent)  and double oxias \r\n(as when shifted from the following word) have been replaced by SFX \r\nrules in the affix file.\r\n\r\nIt works quite well with Vim and it is fast, but bear in mind that it is far\r\nfrom finished. (see bugs below).\r\n\r\n----------------\r\nScreenshot\r\n----------------\r\nhttps:\/\/postimg.cc\/mPS4kXFC\r\n\r\n----------------\r\nInstallation.\r\n----------------\r\n\r\nCopy the file polytonic.utf-8.spl to your home .vim spell \r\ndirectory (~\/.vim\/spell\/). If the directory does not exist, create it. \r\n\r\n\r\n----------------\r\nUsage\r\n----------------\r\n\r\nTo use it you must set the encodings to utf-8.\r\n:set encoding=utf-8\r\n:set fenc=utf-8 \r\n:set inputenc=utf-8\r\n\r\nFor polytonic Greek text entry see: vimscript#2743\r\n\r\nTo activate spell checking:\r\n:set spelllang=polytonic\r\n:set spell\r\n\r\nFor bilingual spell checking: \r\n:set spelllang=polytonic,en\r\n\r\nTo limit spelling suggestions to 8:\r\n:set spellsuggest=8\r\n\r\n--------------\r\nKnown bugs\r\n--------------\r\n\r\nHyphenated words are not recognized and are flagged as spelling errors.\r\n\r\nWords written in capital letters, even when are spelled correctly (without accents), are \r\nflagged as errors.\r\n\r\nIf anyone wishes to help, e-mail me and I will forward the .dic and .aff files.\r\nproteuss AT sdf.org\r\n\r\n------------\r\nReferences\r\n------------\r\n[1] http:\/\/ispell.math.upatras.gr\r\n[2] http:\/\/www.perseus.tufts.edu\/hopper\/opensource\/download\r\n[3] http:\/\/www.tlg.uci.edu\/\r\n","4":"---------------------------------------------------------------------\r\nSpell file for multi accented (also known as polytonic) Greek. \r\n---------------------------------------------------------------------\r\n\r\nThis spell file is for checking the spelling of texts typed in multi \r\naccented (or polytonic) Greek. It is useful to Greek scholars \r\n(hellenists) as well as native Greek speakers who prefer to write \r\nin the traditional multi accented script.  \r\n\r\nThe word list covers all the ancient and modern Greek vocabulary.\r\nAbout 1.5 million words all spelled in the traditional polytonic system. \r\n\r\nThe ancient Greek word list is derived from several corpora like \r\nPerseus [2], and TLG [3] and other sources.\r\n\r\nThe modern Greek word list is derived from the ispell dictionary el_GR [1]\r\nbut all the words have been appropriately accentuated. This spell file\r\nwill flag monotonic spelling as errors (and rightfully so).\r\n\r\nThe two lists are combined, cleaned of double entries (there was a large \r\noverlap) and sorted. Last syllable varia (grave accent)  and double oxias \r\n(as when shifted from the following word) have been replaced by SFX \r\nrules in the affix file.\r\n\r\nIt works quite well with Vim and it is fast, but bear in mind that it is far\r\nfrom finished. (see bugs below).\r\n\r\n----------------\r\nScreenshot\r\n----------------\r\nhttps:\/\/postimg.cc\/mPS4kXFC\r\n\r\n----------------\r\nInstallation.\r\n----------------\r\n\r\nCopy the file polytonic.utf-8.spl to your home .vim spell \r\ndirectory (~\/.vim\/spell\/). If the directory does not exist, create it. \r\n\r\n\r\n----------------\r\nUsage\r\n----------------\r\n\r\nTo use it you must set the encodings to utf-8.\r\n:set encoding=utf-8\r\n:set fenc=utf-8 \r\n:set inputenc=utf-8\r\n\r\nFor polytonic Greek text entry see: vimscript#2743\r\n\r\nTo activate spell checking:\r\n:set spelllang=polytonic\r\n:set spell\r\n\r\nFor bilingual spell checking: \r\n:set spelllang=polytonic,en\r\n\r\nTo limit spelling suggestions to 8:\r\n:set spellsuggest=8\r\n\r\n--------------\r\nKnown bugs\r\n--------------\r\n\r\nHyphenated words are not recognized and are flagged as spelling errors.\r\n\r\nWords written in capital letters, even when are spelled correctly (without accents), are \r\nflagged as errors.\r\n\r\nIf anyone wishes to help, e-mail me and I will forward the .dic and .aff files.\r\nproteuss AT sdf.org\r\n\r\n------------\r\nReferences\r\n------------\r\n[1] http:\/\/ispell.math.upatras.gr\r\n[2] http:\/\/www.perseus.tufts.edu\/hopper\/opensource\/download\r\n[3] http:\/\/www.tlg.uci.edu\/\r\n","install_details":"Extract files: tar -xf polytonic.utf-8-v-n.n.n.tar.xz\r\n\r\nCopy the file polytonic.utf-8.spl to your home .vim spell \r\ndirectory (~\/.vim\/spell\/). If the directory does not exist, create it. ","5":"Extract files: tar -xf polytonic.utf-8-v-n.n.n.tar.xz\r\n\r\nCopy the file polytonic.utf-8.spl to your home .vim spell \r\ndirectory (~\/.vim\/spell\/). If the directory does not exist, create it. ","first_name":"Andreas","6":"Andreas","last_name":"Proteus","7":"Proteus","releases":[{"0":"3388","vim_version":"8.2","1":"8.2","script_version":"1.0.1","2":"1.0.1","version_comment":"Expanded vocabulary","3":"Expanded vocabulary","package":"polytonic.utf-8-v-1.0.1.tar.xz","4":"polytonic.utf-8-v-1.0.1.tar.xz","src_id":"28075","5":"28075","creation_date":"1655023990","6":"1655023990"},{"0":"3388","vim_version":"8.2","1":"8.2","script_version":"1.0.0","2":"1.0.0","version_comment":"Final Sigma bug fixed.  The spell checker now sees  'σ' and 'ς' as different characters.","3":"Final Sigma bug fixed.  The spell checker now sees  'σ' and 'ς' as different characters.","package":"polytonic.utf-8.tar.xz","4":"polytonic.utf-8.tar.xz","src_id":"28074","5":"28074","creation_date":"1654993970","6":"1654993970"},{"0":"3388","vim_version":"7.0","1":"7.0","script_version":"0.0.2","2":"0.0.2","version_comment":"Vocabulary updated","3":"Vocabulary updated","package":"polytonic.utf-8.tar.bz2","4":"polytonic.utf-8.tar.bz2","src_id":"27531","5":"27531","creation_date":"1615594835","6":"1615594835"},{"0":"3388","vim_version":"7.0","1":"7.0","script_version":"0.0.1","2":"0.0.1","version_comment":"Initial upload","3":"Initial upload","package":"polytonic.utf-8.tar.bz2","4":"polytonic.utf-8.tar.bz2","src_id":"14664","5":"14664","creation_date":"1293784192","6":"1293784192"}]},"3387":{"script_id":"3387","0":"3387","script_name":"perfect.vim","1":"perfect.vim","script_type":"color scheme","2":"color scheme","summary":"Light backgrounded Vim colorsheme","3":"Light backgrounded Vim colorsheme","description":"Clean colorscheme with limited colors.\r\n\r\nGitHub: https:\/\/github.com\/kossnocorp\/perfect.vim\r\n\r\nScreenshot: http:\/\/bit.ly\/hpLboi","4":"Clean colorscheme with limited colors.\r\n\r\nGitHub: https:\/\/github.com\/kossnocorp\/perfect.vim\r\n\r\nScreenshot: http:\/\/bit.ly\/hpLboi","install_details":"","5":"","first_name":"Sasha","6":"Sasha","last_name":"Koss","7":"Koss","releases":[{"0":"3387","vim_version":"7.3","1":"7.3","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"perfect.vim","4":"perfect.vim","src_id":"14661","5":"14661","creation_date":"1293758971","6":"1293758971"}]},"3386":{"script_id":"3386","0":"3386","script_name":"JumpToLastOccurrence","1":"JumpToLastOccurrence","script_type":"utility","2":"utility","summary":"f{char} motions that count from the end of the line. ","3":"f{char} motions that count from the end of the line. ","description":"DESCRIPTION\r\nThe f{char}, F, t and T family of motions are often more effective\r\nthan the more general l, w and W motions. However, there are situations\r\nwhere they are difficult to apply.\r\nTake a long file system path like \/var\/opt\/foo\/a\/very\/long\/path\/to\/filename.\r\nImagine you are on the beginning \/ and want to change the entire directory\r\npath, but keep the filename. You'd either have to count occurrences (e.g. c8f\/\r\nor c2tf), do multiple moves ($T\/cB), use visual mode (veeeeeeeelc), or a\r\nsearch (c\/filen<CR>).\r\n\r\nThis plugin extends the built-in f\/F\/t\/T motions with counterparts that move\r\nto the last occurrence of {char} in the line. For the above example, that\r\nwould be a short c,f\/ to jump to the last slash in the line.\r\n\r\nSEE ALSO\r\n- The JumpToVerticalOccurrence.vim plugin (vimscript #4841) implements\r\n  variations of f \/ F that move vertically across lines, restricted to the\r\n  same screen column as the cursor.\r\n\r\nUSAGE\r\n,f{char}                To [count]'th occurrence of {char}, counting from the\r\n                        end of the line. The cursor is placed on {char}\r\n                        inclusive.\r\n,F{char}                To the [count]'th occurrence of {char}, counting from\r\n                        the beginning of the line. The cursor is placed on\r\n                        {char} exclusive.\r\n,t{char}                Till before [count]'th occurrence of {char}, counting\r\n                        from the end of the line. The cursor is placed on the\r\n                        character left of {char} inclusive.\r\n,T{char}                Till after [count]'th occurrence of {char}, counting\r\n                        from the beginning of the line. The cursor is placed\r\n                        on the character right of {char} exclusive.\r\n\r\n                        All motions can be repeated with ; and ,. However,\r\n                        the ,t and ,T motions will jump to, not until, the\r\n                        next {char}.","4":"DESCRIPTION\r\nThe f{char}, F, t and T family of motions are often more effective\r\nthan the more general l, w and W motions. However, there are situations\r\nwhere they are difficult to apply.\r\nTake a long file system path like \/var\/opt\/foo\/a\/very\/long\/path\/to\/filename.\r\nImagine you are on the beginning \/ and want to change the entire directory\r\npath, but keep the filename. You'd either have to count occurrences (e.g. c8f\/\r\nor c2tf), do multiple moves ($T\/cB), use visual mode (veeeeeeeelc), or a\r\nsearch (c\/filen<CR>).\r\n\r\nThis plugin extends the built-in f\/F\/t\/T motions with counterparts that move\r\nto the last occurrence of {char} in the line. For the above example, that\r\nwould be a short c,f\/ to jump to the last slash in the line.\r\n\r\nSEE ALSO\r\n- The JumpToVerticalOccurrence.vim plugin (vimscript #4841) implements\r\n  variations of f \/ F that move vertically across lines, restricted to the\r\n  same screen column as the cursor.\r\n\r\nUSAGE\r\n,f{char}                To [count]'th occurrence of {char}, counting from the\r\n                        end of the line. The cursor is placed on {char}\r\n                        inclusive.\r\n,F{char}                To the [count]'th occurrence of {char}, counting from\r\n                        the beginning of the line. The cursor is placed on\r\n                        {char} exclusive.\r\n,t{char}                Till before [count]'th occurrence of {char}, counting\r\n                        from the end of the line. The cursor is placed on the\r\n                        character left of {char} inclusive.\r\n,T{char}                Till after [count]'th occurrence of {char}, counting\r\n                        from the beginning of the line. The cursor is placed\r\n                        on the character right of {char} exclusive.\r\n\r\n                        All motions can be repeated with ; and ,. However,\r\n                        the ,t and ,T motions will jump to, not until, the\r\n                        next {char}.","install_details":"INSTALLATION\r\nThis script is packaged as a vimball. If you have the \"gunzip\" decompressor\r\nin your PATH, simply edit the *.vmb.gz package in Vim; otherwise, decompress\r\nthe archive first, e.g. using WinZip. Inside Vim, install by sourcing the\r\nvimball or via the :UseVimball command.\r\n    vim JumpToLastOccurrence*.vmb.gz\r\n    :so %\r\nTo uninstall, use the :RmVimball command.\r\n\r\nDEPENDENCIES\r\n- Requires Vim 7.0 or higher.\r\n- Requires the ingo-library.vim plugin (vimscript #4433), version 1.016 or\r\n  higher.\r\n- repeat.vim (vimscript #2136) plugin, version 1.1 or higher (optional)\r\n\r\nCONFIGURATION\r\nFor a permanent configuration, put the following commands into your vimrc:\r\n\r\nBy default, all mappings start with , (comma) as the map leader instead of\r\nusing <Leader>. I personally find the default <Leader> key too far off the\r\nkeyboard to be useful for custom motions (which also cannot be repeated via\r\nthe . (dot) command, so they should be very fast to type repeatedly), but\r\nquite suitable for general, less frequently used custom mappings.\r\nTo avoid losing the (rarely used) , mapping (which repeats latest f, t, F or\r\nT in opposite direction), you can remap it to ,,:\r\n    nnoremap ,, ,\r\n    xnoremap ,, ,\r\n    onoremap ,, ,\r\n\r\nIf you don't agree with this and want all motions to start with <Leader> (or\r\nany other key), you can do this (before sourcing the script):\r\n    let g:JumpToLastOccurrence_Leader = '<Leader>'\r\n\r\nIf you want to use completely different or only a few of the mappings, map\r\nyour keys to the <Plug>JumpToLastOccurrence_? mapping targets _before_\r\nsourcing the script (e.g. in your vimrc).","5":"INSTALLATION\r\nThis script is packaged as a vimball. If you have the \"gunzip\" decompressor\r\nin your PATH, simply edit the *.vmb.gz package in Vim; otherwise, decompress\r\nthe archive first, e.g. using WinZip. Inside Vim, install by sourcing the\r\nvimball or via the :UseVimball command.\r\n    vim JumpToLastOccurrence*.vmb.gz\r\n    :so %\r\nTo uninstall, use the :RmVimball command.\r\n\r\nDEPENDENCIES\r\n- Requires Vim 7.0 or higher.\r\n- Requires the ingo-library.vim plugin (vimscript #4433), version 1.016 or\r\n  higher.\r\n- repeat.vim (vimscript #2136) plugin, version 1.1 or higher (optional)\r\n\r\nCONFIGURATION\r\nFor a permanent configuration, put the following commands into your vimrc:\r\n\r\nBy default, all mappings start with , (comma) as the map leader instead of\r\nusing <Leader>. I personally find the default <Leader> key too far off the\r\nkeyboard to be useful for custom motions (which also cannot be repeated via\r\nthe . (dot) command, so they should be very fast to type repeatedly), but\r\nquite suitable for general, less frequently used custom mappings.\r\nTo avoid losing the (rarely used) , mapping (which repeats latest f, t, F or\r\nT in opposite direction), you can remap it to ,,:\r\n    nnoremap ,, ,\r\n    xnoremap ,, ,\r\n    onoremap ,, ,\r\n\r\nIf you don't agree with this and want all motions to start with <Leader> (or\r\nany other key), you can do this (before sourcing the script):\r\n    let g:JumpToLastOccurrence_Leader = '<Leader>'\r\n\r\nIf you want to use completely different or only a few of the mappings, map\r\nyour keys to the <Plug>JumpToLastOccurrence_? mapping targets _before_\r\nsourcing the script (e.g. in your vimrc).","first_name":"Ingo","6":"Ingo","last_name":"Karkat","7":"Karkat","releases":[{"0":"3386","vim_version":"7.0","1":"7.0","script_version":"1.20","2":"1.20","version_comment":"- ENH: Implement repeat of operator-pending mapping without re-querying the {char}. This requires the repeat.vim plugin, version 1.1 or higher.\r\n- Add dependency to ingo-library (vimscript #4433). *** You need to separately install ingo-library (vimscript #4433) version 1.016 (or higher)! ***","3":"- ENH: Implement repeat of operator-pending mapping without re-querying the {char}. This requires the repeat.vim plugin, version 1.1 or higher.\r\n- Add dependency to ingo-library (vimscript #4433). *** You need to separately install ingo-library (vimscript #4433) version 1.016 (or higher)! ***","package":"JumpToLastOccurrence-1.20.vmb.gz","4":"JumpToLastOccurrence-1.20.vmb.gz","src_id":"21726","5":"21726","creation_date":"1396537632","6":"1396537632"},{"0":"3386","vim_version":"7.0","1":"7.0","script_version":"1.11","2":"1.11","version_comment":"Also handle move to the buffer's very last character in operator-pending mode.","3":"Also handle move to the buffer's very last character in operator-pending mode.","package":"JumpToLastOccurrence-1.11.vmb.gz","4":"JumpToLastOccurrence-1.11.vmb.gz","src_id":"18618","5":"18618","creation_date":"1347739362","6":"1347739362"},{"0":"3386","vim_version":"7.0","1":"7.0","script_version":"1.10","2":"1.10","version_comment":"- Moved functions from plugin to separate autoload script. \r\n- Made mappings configurable, both via the customary <Plug> mappings and alternatively in bulk through the g:JumpToLastOccurrence_Leader setting. ","3":"- Moved functions from plugin to separate autoload script. \r\n- Made mappings configurable, both via the customary <Plug> mappings and alternatively in bulk through the g:JumpToLastOccurrence_Leader setting. ","package":"JumpToLastOccurrence.vba.gz","4":"JumpToLastOccurrence.vba.gz","src_id":"14659","5":"14659","creation_date":"1293737433","6":"1293737433"},{"0":"3386","vim_version":"7.0","1":"7.0","script_version":"1.00","2":"1.00","version_comment":"Initial upload","3":"Initial upload","package":"JumpToLastOccurrence.vba.gz","4":"JumpToLastOccurrence.vba.gz","src_id":"14651","5":"14651","creation_date":"1293632812","6":"1293632812"}]},"3385":{"script_id":"3385","0":"3385","script_name":"csc.vim","1":"csc.vim","script_type":"syntax","2":"syntax","summary":"Essbase script syntax file","3":"Essbase script syntax file","description":"Essbase script syntax file, with several bug fixes, improvements and additions.  Should be up-to-date with all features of Essbase 9.  If anything is missing, broken, not working well on your setup, or an inconvenience for you, please let me know, all feedback is welcome: <yyq123 at gmail.com>.\r\n\r\nEnhancements:\r\n-------------\r\n* FIX...ENDFIX : lightcyan\r\n* Substitution Variable : Identifier\r\n* Cross Dimension Operator : Special\r\n* Ess_LOCALE : Comment\r\n\r\nScreenshots:\r\n-------------\r\nhttp:\/\/www.flickr.com\/photos\/yyq123\/5382671335\/","4":"Essbase script syntax file, with several bug fixes, improvements and additions.  Should be up-to-date with all features of Essbase 9.  If anything is missing, broken, not working well on your setup, or an inconvenience for you, please let me know, all feedback is welcome: <yyq123 at gmail.com>.\r\n\r\nEnhancements:\r\n-------------\r\n* FIX...ENDFIX : lightcyan\r\n* Substitution Variable : Identifier\r\n* Cross Dimension Operator : Special\r\n* Ess_LOCALE : Comment\r\n\r\nScreenshots:\r\n-------------\r\nhttp:\/\/www.flickr.com\/photos\/yyq123\/5382671335\/","install_details":"1. Copy csc.vim to: ~\/.vim\/syntax\/csc.vim or\r\n$VIMFILES\\syntax\\csc.vim\r\n\r\n2. Add the following commands to your vimrc file:\r\naugroup filetypedetect\r\n   au BufNewFile,BufRead *.csc setfiletype csc\r\naugroup END","5":"1. Copy csc.vim to: ~\/.vim\/syntax\/csc.vim or\r\n$VIMFILES\\syntax\\csc.vim\r\n\r\n2. Add the following commands to your vimrc file:\r\naugroup filetypedetect\r\n   au BufNewFile,BufRead *.csc setfiletype csc\r\naugroup END","first_name":"Anthony","6":"Anthony","last_name":"Yuan","7":"Yuan","releases":[{"0":"3385","vim_version":"7.0","1":"7.0","script_version":"0.2","2":"0.2","version_comment":"* Add: @CURRMBR, @CALCMODE, @ISATTRIBUTE, @ATTRIBUTEBVAL, @XREF, @COUNT, @RANGE\r\n* Add: SET CALCTASKDIMS\r\n* Modify: FIX...ENDFIX","3":"* Add: @CURRMBR, @CALCMODE, @ISATTRIBUTE, @ATTRIBUTEBVAL, @XREF, @COUNT, @RANGE\r\n* Add: SET CALCTASKDIMS\r\n* Modify: FIX...ENDFIX","package":"csc.vim","4":"csc.vim","src_id":"14843","5":"14843","creation_date":"1295837183","6":"1295837183"},{"0":"3385","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"csc.vim","4":"csc.vim","src_id":"14635","5":"14635","creation_date":"1293519316","6":"1293519316"}]},"3384":{"script_id":"3384","0":"3384","script_name":"shadow.vim","1":"shadow.vim","script_type":"utility","2":"utility","summary":"A plugin to support you code with a wrapper transparently in a pluggable way.","3":"A plugin to support you code with a wrapper transparently in a pluggable way.","description":"Shadow.vim is a plugin to support you code with a wrapper transparently in a pluggable way.\n\n* http:\/\/github.com\/ujihisa\/shadow.vim (development)\n","4":"Shadow.vim is a plugin to support you code with a wrapper transparently in a pluggable way.\n\n* http:\/\/github.com\/ujihisa\/shadow.vim (development)\n","install_details":"Unarchive the zip file into a directory that is under `&rtp` of your Vim, including `~\/.vim` dir.\n","5":"Unarchive the zip file into a directory that is under `&rtp` of your Vim, including `~\/.vim` dir.\n","first_name":"ujihisa","6":"ujihisa","last_name":".","7":".","releases":[{"0":"3384","vim_version":"7.3","1":"7.3","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"shadow.vim-1.0.zip","4":"shadow.vim-1.0.zip","src_id":"14634","5":"14634","creation_date":"1293511183","6":"1293511183"}]},"3383":{"script_id":"3383","0":"3383","script_name":"StatusLineHighlight","1":"StatusLineHighlight","script_type":"utility","2":"utility","summary":"Change statusline color depending on buffer state. ","3":"Change statusline color depending on buffer state. ","description":"DESCRIPTION\r\nThis plugin indicates the state of the buffer (modified, readonly,\r\nunmodifiable, special non-file \"scratch\") \/ window (is preview window) by\r\nchanging the highlighting of the window's status line. It defines additional\r\nStatusLine... \/ StatusLine...NC highlight groups that are customizable and by\r\ndefault use different colors to differentiate the buffer states.\r\n\r\nThis screenshot shows the plugin in action:\r\n    https:\/\/raw.githubusercontent.com\/inkarkat\/vim-StatusLineHighlight\/master\/doc\/StatusLineHighlight.png\r\n\r\nHOW IT WORKS\r\nUsing different colors for the status line is trickier than it seems: Though\r\nthe 'statusline' setting supports inline expressions via %{expr}, the returned\r\ntext is taken as-is; highlight items %#hlgroup# and #* are not evaluated, only\r\nprinted as text. Evaluation does happen when one %!expr is used, but the\r\nexpression seems to be evaluated only once for a complete screen redraw cycle,\r\nnot for each individual status line, so one cannot use it to set different\r\nhighlightings for different status lines.\r\n\r\nTherefore, this plugin sets up autocmds that continually adapt buffer-local\r\n'statusline' settings (which prepend the highlight group to the (mostly)\r\nglobal setting (though local 'statusline' settings set by ftplugins are kept,\r\ntoo)).\r\n\r\nUSAGE\r\nThis plugin does not introduce any commands or mappings. Just observe the\r\nchanged status line colors, e.g. when using :view, :pedit, :help, etc.\r\n\r\nYou immediately see that a buffer is read-only because its status line is\r\ngray, not black; unmodifiable buffers are even \"more\" gray. Unsaved, modified\r\nbuffers are indicated via a dark-red status line. Special windows like the\r\ncommand and quickfix windows, as well as many \"scratch\" buffers used by\r\nplugins are shown in dark blue. The preview window is now also easy to find,\r\nbecause it has a blue status line.","4":"DESCRIPTION\r\nThis plugin indicates the state of the buffer (modified, readonly,\r\nunmodifiable, special non-file \"scratch\") \/ window (is preview window) by\r\nchanging the highlighting of the window's status line. It defines additional\r\nStatusLine... \/ StatusLine...NC highlight groups that are customizable and by\r\ndefault use different colors to differentiate the buffer states.\r\n\r\nThis screenshot shows the plugin in action:\r\n    https:\/\/raw.githubusercontent.com\/inkarkat\/vim-StatusLineHighlight\/master\/doc\/StatusLineHighlight.png\r\n\r\nHOW IT WORKS\r\nUsing different colors for the status line is trickier than it seems: Though\r\nthe 'statusline' setting supports inline expressions via %{expr}, the returned\r\ntext is taken as-is; highlight items %#hlgroup# and #* are not evaluated, only\r\nprinted as text. Evaluation does happen when one %!expr is used, but the\r\nexpression seems to be evaluated only once for a complete screen redraw cycle,\r\nnot for each individual status line, so one cannot use it to set different\r\nhighlightings for different status lines.\r\n\r\nTherefore, this plugin sets up autocmds that continually adapt buffer-local\r\n'statusline' settings (which prepend the highlight group to the (mostly)\r\nglobal setting (though local 'statusline' settings set by ftplugins are kept,\r\ntoo)).\r\n\r\nUSAGE\r\nThis plugin does not introduce any commands or mappings. Just observe the\r\nchanged status line colors, e.g. when using :view, :pedit, :help, etc.\r\n\r\nYou immediately see that a buffer is read-only because its status line is\r\ngray, not black; unmodifiable buffers are even \"more\" gray. Unsaved, modified\r\nbuffers are indicated via a dark-red status line. Special windows like the\r\ncommand and quickfix windows, as well as many \"scratch\" buffers used by\r\nplugins are shown in dark blue. The preview window is now also easy to find,\r\nbecause it has a blue status line.","install_details":"INSTALLATION\r\nThe code is hosted in a Git repo at\r\n    https:\/\/github.com\/inkarkat\/vim-StatusLineHighlight\r\nYou can use your favorite plugin manager, or \"git clone\" into a directory used\r\nfor Vim packages. Releases are on the \"stable\" branch, the latest unstable\r\ndevelopment snapshot on \"master\".\r\n\r\nThis script is also packaged as a vimball. If you have the \"gunzip\"\r\ndecompressor in your PATH, simply edit the *.vmb.gz package in Vim; otherwise,\r\ndecompress the archive first, e.g. using WinZip. Inside Vim, install by\r\nsourcing the vimball or via the :UseVimball command.\r\n    vim StatusLineHighlight*.vmb.gz\r\n    :so %\r\nTo uninstall, use the :RmVimball command.\r\n\r\nDEPENDENCIES\r\n- Requires Vim 7.0 or higher.\r\n\r\nCONFIGURATION\r\nFor a permanent configuration, put the following commands into your vimrc:\r\n\r\nYou may override the default highlightings and define your own colors in the\r\nfollowing form (after any :colorscheme command). As with the built-in status\r\nline highlighting, there is a hl-StatusLine group for the current window and\r\na hl-StatusLineNC for all non-current windows.\r\n    highlight StatusLineModified           term=bold,reverse cterm=bold,reverse ctermfg=DarkRed  gui=bold,reverse guifg=DarkRed\r\n    highlight StatusLineModifiedNC         term=reverse      cterm=reverse      ctermfg=DarkRed  gui=reverse      guifg=DarkRed\r\n    highlight StatusLinePreview            term=bold,reverse cterm=bold,reverse ctermfg=Blue     gui=bold,reverse guifg=Blue\r\n    highlight StatusLinePreviewNC          term=reverse      cterm=reverse      ctermfg=Blue     gui=reverse      guifg=Blue\r\n    highlight StatusLineReadonly           term=bold,reverse cterm=bold,reverse ctermfg=Grey     gui=bold,reverse guifg=DarkGrey\r\n    highlight StatusLineReadonlyNC         term=reverse      cterm=reverse      ctermfg=Grey     gui=reverse      guifg=DarkGrey\r\n    highlight StatusLineSpecial            term=bold,reverse cterm=bold,reverse ctermfg=DarkBlue gui=bold,reverse guifg=DarkBlue\r\n    highlight StatusLineSpecialNC          term=reverse      cterm=reverse      ctermfg=DarkBlue gui=reverse      guifg=DarkBlue\r\n    highlight StatusLineUnmodifiable       term=bold,reverse cterm=bold,reverse ctermfg=Grey     gui=bold,reverse guifg=Grey\r\n    highlight StatusLineUnmodifiableNC     term=reverse      cterm=reverse      ctermfg=Grey     gui=reverse      guifg=Grey\r\nIf you want to avoid losing the highlightings on :colorscheme commands, you\r\nneed to re-apply your highlights on the ColorScheme event, similar to how\r\nthis plugin does.","5":"INSTALLATION\r\nThe code is hosted in a Git repo at\r\n    https:\/\/github.com\/inkarkat\/vim-StatusLineHighlight\r\nYou can use your favorite plugin manager, or \"git clone\" into a directory used\r\nfor Vim packages. Releases are on the \"stable\" branch, the latest unstable\r\ndevelopment snapshot on \"master\".\r\n\r\nThis script is also packaged as a vimball. If you have the \"gunzip\"\r\ndecompressor in your PATH, simply edit the *.vmb.gz package in Vim; otherwise,\r\ndecompress the archive first, e.g. using WinZip. Inside Vim, install by\r\nsourcing the vimball or via the :UseVimball command.\r\n    vim StatusLineHighlight*.vmb.gz\r\n    :so %\r\nTo uninstall, use the :RmVimball command.\r\n\r\nDEPENDENCIES\r\n- Requires Vim 7.0 or higher.\r\n\r\nCONFIGURATION\r\nFor a permanent configuration, put the following commands into your vimrc:\r\n\r\nYou may override the default highlightings and define your own colors in the\r\nfollowing form (after any :colorscheme command). As with the built-in status\r\nline highlighting, there is a hl-StatusLine group for the current window and\r\na hl-StatusLineNC for all non-current windows.\r\n    highlight StatusLineModified           term=bold,reverse cterm=bold,reverse ctermfg=DarkRed  gui=bold,reverse guifg=DarkRed\r\n    highlight StatusLineModifiedNC         term=reverse      cterm=reverse      ctermfg=DarkRed  gui=reverse      guifg=DarkRed\r\n    highlight StatusLinePreview            term=bold,reverse cterm=bold,reverse ctermfg=Blue     gui=bold,reverse guifg=Blue\r\n    highlight StatusLinePreviewNC          term=reverse      cterm=reverse      ctermfg=Blue     gui=reverse      guifg=Blue\r\n    highlight StatusLineReadonly           term=bold,reverse cterm=bold,reverse ctermfg=Grey     gui=bold,reverse guifg=DarkGrey\r\n    highlight StatusLineReadonlyNC         term=reverse      cterm=reverse      ctermfg=Grey     gui=reverse      guifg=DarkGrey\r\n    highlight StatusLineSpecial            term=bold,reverse cterm=bold,reverse ctermfg=DarkBlue gui=bold,reverse guifg=DarkBlue\r\n    highlight StatusLineSpecialNC          term=reverse      cterm=reverse      ctermfg=DarkBlue gui=reverse      guifg=DarkBlue\r\n    highlight StatusLineUnmodifiable       term=bold,reverse cterm=bold,reverse ctermfg=Grey     gui=bold,reverse guifg=Grey\r\n    highlight StatusLineUnmodifiableNC     term=reverse      cterm=reverse      ctermfg=Grey     gui=reverse      guifg=Grey\r\nIf you want to avoid losing the highlightings on :colorscheme commands, you\r\nneed to re-apply your highlights on the ColorScheme event, similar to how\r\nthis plugin does.","first_name":"Ingo","6":"Ingo","last_name":"Karkat","7":"Karkat","releases":[{"0":"3383","vim_version":"7.0","1":"7.0","script_version":"1.10","2":"1.10","version_comment":"- ENH: Handle hl-User1..9 highlighting by replacing %* and %0* with the custom statusline highlighting. Previously, the custom statusline highlighting provided by this plugin stopped after the end of a User highlighting.\r\n- Minor: Make substitute() robust against 'ignorecase'.","3":"- ENH: Handle hl-User1..9 highlighting by replacing %* and %0* with the custom statusline highlighting. Previously, the custom statusline highlighting provided by this plugin stopped after the end of a User highlighting.\r\n- Minor: Make substitute() robust against 'ignorecase'.","package":"StatusLineHighlight-1.10.vmb.gz","4":"StatusLineHighlight-1.10.vmb.gz","src_id":"26264","5":"26264","creation_date":"1541386505","6":"1541386505"},{"0":"3383","vim_version":"7.0","1":"7.0","script_version":"1.01","2":"1.01","version_comment":"Avoid losing the statusline highlightings on colorscheme commands. ","3":"Avoid losing the statusline highlightings on colorscheme commands. ","package":"StatusLineHighlight.vba.gz","4":"StatusLineHighlight.vba.gz","src_id":"16014","5":"16014","creation_date":"1309552532","6":"1309552532"},{"0":"3383","vim_version":"7.0","1":"7.0","script_version":"1.00","2":"1.00","version_comment":"Initial upload","3":"Initial upload","package":"StatusLineHighlight.vba.gz","4":"StatusLineHighlight.vba.gz","src_id":"14631","5":"14631","creation_date":"1293462379","6":"1293462379"}]},"3382":{"script_id":"3382","0":"3382","script_name":"textobj-rubyblock","1":"textobj-rubyblock","script_type":"utility","2":"utility","summary":"A custom text object for selecting ruby blocks.","3":"A custom text object for selecting ruby blocks.","description":"A custom text object for selecting ruby blocks.\r\n\r\nDepends on vimscript #2100, which provides a framework for creating custom\r\ntext objects.\r\n\r\nAlso requires that matchit.vim vimscript #39 is enabled.\r\n\r\n# Usage #\r\n\r\nWhen textobj-rubyblock is installed you will gain two new text objects, which\r\nare triggered by `ar` and `ir` respectively. These follow Vim convention, so\r\nthat `ar` selects _all_ of a ruby block, and `ir` selects the _inner_ portion\r\nof a rubyblock.\r\n\r\nIn ruby, a block is always closed with the `end` keyword. Ruby blocks may be\r\nopened using one of several keywords, including `module`, `class`, `def` `if`\r\nand `do`. This example demonstrates a few of these:\r\n\r\n    module Foo\r\n      class Bar\r\n        def Baz\r\n          [1,2,3].each do |i|\r\n            i + 1\r\n          end\r\n        end\r\n      end\r\n    end\r\n\r\nSuppose your cursor was positioned on the word `def`. Typing `var` would\r\nenable visual mode selecting _all_ of the method definition. Your selection\r\nwould comprise the following lines (also, see screenshot:\r\nhttp:\/\/vimcasts.org\/images\/blog\/rubyblock-all.png):\r\n\r\n    def Baz\r\n      [1,2,3].each do |i|\r\n        i + 1\r\n      end\r\n    end\r\n\r\nWhereas if you typed `vir`, you would select everything _inside_ of the method\r\ndefinition, which looks like this (also, see screenshot:\r\nhttp:\/\/vimcasts.org\/images\/blog\/rubyblock-inner.png):\r\n\r\n    [1,2,3].each do |i|\r\n      i + 1\r\n    end\r\n\r\nNote that the `ar` and `ir` text objects always enable _visual line_ mode,\r\neven if you were in visual character or block mode before you triggered the\r\nrubyblock text object.\r\n\r\nNote too that the `ar` and `ir` text objects always position your cursor on\r\nthe `end` keyword. If you want to move to the top of the selection, you can do\r\nso with the `o` key.\r\n\r\n# Limitations #\r\n\r\nSome text objects in Vim respond to a count. For example, the `a{` text object\r\nwill select _all_ of the current `{}` delimited block, but if you prefix it\r\nwith the number 2 (e.g. `v2i{`) then it will select all of the block that\r\ncontains the current block. The rubyblock text object does not respond in this\r\nway if you prefix a count. This is due to a limitation in vimscript #2100.\r\n\r\nHowever, you can achieve a similar effect by repeating the rubyblock\r\ntext-object manually. So if you press `var` to select the current ruby block,\r\nyou can expand your selection outwards by repeating `ar`, or contract your\r\nselection inwards by repeating `ir`.\r\n","4":"A custom text object for selecting ruby blocks.\r\n\r\nDepends on vimscript #2100, which provides a framework for creating custom\r\ntext objects.\r\n\r\nAlso requires that matchit.vim vimscript #39 is enabled.\r\n\r\n# Usage #\r\n\r\nWhen textobj-rubyblock is installed you will gain two new text objects, which\r\nare triggered by `ar` and `ir` respectively. These follow Vim convention, so\r\nthat `ar` selects _all_ of a ruby block, and `ir` selects the _inner_ portion\r\nof a rubyblock.\r\n\r\nIn ruby, a block is always closed with the `end` keyword. Ruby blocks may be\r\nopened using one of several keywords, including `module`, `class`, `def` `if`\r\nand `do`. This example demonstrates a few of these:\r\n\r\n    module Foo\r\n      class Bar\r\n        def Baz\r\n          [1,2,3].each do |i|\r\n            i + 1\r\n          end\r\n        end\r\n      end\r\n    end\r\n\r\nSuppose your cursor was positioned on the word `def`. Typing `var` would\r\nenable visual mode selecting _all_ of the method definition. Your selection\r\nwould comprise the following lines (also, see screenshot:\r\nhttp:\/\/vimcasts.org\/images\/blog\/rubyblock-all.png):\r\n\r\n    def Baz\r\n      [1,2,3].each do |i|\r\n        i + 1\r\n      end\r\n    end\r\n\r\nWhereas if you typed `vir`, you would select everything _inside_ of the method\r\ndefinition, which looks like this (also, see screenshot:\r\nhttp:\/\/vimcasts.org\/images\/blog\/rubyblock-inner.png):\r\n\r\n    [1,2,3].each do |i|\r\n      i + 1\r\n    end\r\n\r\nNote that the `ar` and `ir` text objects always enable _visual line_ mode,\r\neven if you were in visual character or block mode before you triggered the\r\nrubyblock text object.\r\n\r\nNote too that the `ar` and `ir` text objects always position your cursor on\r\nthe `end` keyword. If you want to move to the top of the selection, you can do\r\nso with the `o` key.\r\n\r\n# Limitations #\r\n\r\nSome text objects in Vim respond to a count. For example, the `a{` text object\r\nwill select _all_ of the current `{}` delimited block, but if you prefix it\r\nwith the number 2 (e.g. `v2i{`) then it will select all of the block that\r\ncontains the current block. The rubyblock text object does not respond in this\r\nway if you prefix a count. This is due to a limitation in vimscript #2100.\r\n\r\nHowever, you can achieve a similar effect by repeating the rubyblock\r\ntext-object manually. So if you press `var` to select the current ruby block,\r\nyou can expand your selection outwards by repeating `ar`, or contract your\r\nselection inwards by repeating `ir`.\r\n","install_details":"First of all, ensure that you have installed vimscript #2100, without which\r\nthis plugin will not work.\r\n\r\nThen, ensure that you have enabled the matchit.vim vimscript #39 plugin. This\r\ncan be achieved by running (or placing this in your vimrc file):\r\n\r\n    :runtime macros\/matchit.vim\r\n\r\nFinally, you need to ensure that Vim is not running in vi-compatiable mode, and\r\nthat filetype plugins are enabled. Placing these lines in your vimrc file will\r\nset up this configuration for you:\r\n\r\n    set nocompatible\r\n    if has(\"autocmd\")\r\n      filetype indent plugin on\r\n    endif\r\n\r\nThis plugin is distributed as a vimball, so to install it you just need to\r\nopen the file with Vim and run the command:\r\n\r\n    :source %\r\n\r\nIf you prefer to manage your plugins using pathogen (vimscript #2332), then\r\nyou might prefer to checkout the latest version directly from github:\r\n\r\n* https:\/\/github.com\/nelstrom\/vim-textobj-rubyblock\r\n* https:\/\/github.com\/kana\/vim-textobj-user\r\n","5":"First of all, ensure that you have installed vimscript #2100, without which\r\nthis plugin will not work.\r\n\r\nThen, ensure that you have enabled the matchit.vim vimscript #39 plugin. This\r\ncan be achieved by running (or placing this in your vimrc file):\r\n\r\n    :runtime macros\/matchit.vim\r\n\r\nFinally, you need to ensure that Vim is not running in vi-compatiable mode, and\r\nthat filetype plugins are enabled. Placing these lines in your vimrc file will\r\nset up this configuration for you:\r\n\r\n    set nocompatible\r\n    if has(\"autocmd\")\r\n      filetype indent plugin on\r\n    endif\r\n\r\nThis plugin is distributed as a vimball, so to install it you just need to\r\nopen the file with Vim and run the command:\r\n\r\n    :source %\r\n\r\nIf you prefer to manage your plugins using pathogen (vimscript #2332), then\r\nyou might prefer to checkout the latest version directly from github:\r\n\r\n* https:\/\/github.com\/nelstrom\/vim-textobj-rubyblock\r\n* https:\/\/github.com\/kana\/vim-textobj-user\r\n","first_name":"Drew","6":"Drew","last_name":"Neil","7":"Neil","releases":[{"0":"3382","vim_version":"7.2","1":"7.2","script_version":"0.0.2","2":"0.0.2","version_comment":"Do not be fooled by postfix conditionals.","3":"Do not be fooled by postfix conditionals.","package":"textobj-rubyblock.vba","4":"textobj-rubyblock.vba","src_id":"14652","5":"14652","creation_date":"1293638477","6":"1293638477"},{"0":"3382","vim_version":"7.2","1":"7.2","script_version":"0.0.1","2":"0.0.1","version_comment":"Initial upload","3":"Initial upload","package":"textobj-rubyblock.vba","4":"textobj-rubyblock.vba","src_id":"14630","5":"14630","creation_date":"1293436704","6":"1293436704"}]},"3381":{"script_id":"3381","0":"3381","script_name":"emacsmodeline.vim","1":"emacsmodeline.vim","script_type":"utility","2":"utility","summary":"Parse emacs mode line and setlocal in vim","3":"Parse emacs mode line and setlocal in vim","description":"Parses emacs modelines and attempts to set the equivalent vim options.  For example, the following:\r\n\r\n\/\/ # -*- mode: C++; tab-width: 2 -*-\r\n\r\nWill be interpreted the same as the following:\r\n\r\n\/\/ # vim:ft=cpp:sw=2:sts=2:ts=2:\r\n\r\nThe source for this plugin is at https:\/\/github.com\/sfiera\/vim-emacsmodeline","4":"Parses emacs modelines and attempts to set the equivalent vim options.  For example, the following:\r\n\r\n\/\/ # -*- mode: C++; tab-width: 2 -*-\r\n\r\nWill be interpreted the same as the following:\r\n\r\n\/\/ # vim:ft=cpp:sw=2:sts=2:ts=2:\r\n\r\nThe source for this plugin is at https:\/\/github.com\/sfiera\/vim-emacsmodeline","install_details":"","5":"","first_name":"Chris","6":"Chris","last_name":"Pickel","7":"Pickel","releases":[{"0":"3381","vim_version":"7.3","1":"7.3","script_version":"1.2","2":"1.2","version_comment":"More file types, let vim provide defaults.","3":"More file types, let vim provide defaults.","package":"emacsmodeline.vim","4":"emacsmodeline.vim","src_id":"23363","5":"23363","creation_date":"1433682335","6":"1433682335"},{"0":"3381","vim_version":"7.0","1":"7.0","script_version":"0.2","2":"0.2","version_comment":"Initial upload","3":"Initial upload","package":"emacsmodeline.vim","4":"emacsmodeline.vim","src_id":"14628","5":"14628","creation_date":"1293422182","6":"1293422182"}]},"3380":{"script_id":"3380","0":"3380","script_name":"vimorator","1":"vimorator","script_type":"utility","2":"utility","summary":"the simple tnsnames.ora parser","3":"the simple tnsnames.ora parser","description":"The simple tnsnames.ora parser presenting the list of service names as a\r\ndropdown menu capable of executing the contents of the current buffer by\r\nmeans of sqlplus utility.\r\n\r\nRequirements:\r\n  * linux\r\n  * vim >= 7.0.0\r\n  * sqlplus >= 0.0.0\r\n\r\nUsage:\r\n  * Open menu by pressing the hot key (<F2> by default) \r\n  * Select the required (j and k keys) service name and press Enter\r\n  * If global variables g:vimorator_user and  g:vimorator_pass are not defined,\r\n    the username and password will be requested\r\n\r\nLicense:\r\n  This plugin is licensed under the same terms as Vim itself. No warranties,\r\n  expressed or implied.\r\n\r\nSpecial thanks to:\r\n  * Pal Nart (palnart(at)gmail.com) for the great QuickBuf plugin\r\n  * All those who didn\u00e2\u0080\u0099t mess around\r\n\r\nSend all your proposals or error notifications to rezwyi(at)gmail.com.","4":"The simple tnsnames.ora parser presenting the list of service names as a\r\ndropdown menu capable of executing the contents of the current buffer by\r\nmeans of sqlplus utility.\r\n\r\nRequirements:\r\n  * linux\r\n  * vim >= 7.0.0\r\n  * sqlplus >= 0.0.0\r\n\r\nUsage:\r\n  * Open menu by pressing the hot key (<F2> by default) \r\n  * Select the required (j and k keys) service name and press Enter\r\n  * If global variables g:vimorator_user and  g:vimorator_pass are not defined,\r\n    the username and password will be requested\r\n\r\nLicense:\r\n  This plugin is licensed under the same terms as Vim itself. No warranties,\r\n  expressed or implied.\r\n\r\nSpecial thanks to:\r\n  * Pal Nart (palnart(at)gmail.com) for the great QuickBuf plugin\r\n  * All those who didn\u00e2\u0080\u0099t mess around\r\n\r\nSend all your proposals or error notifications to rezwyi(at)gmail.com.","install_details":"  * Download the plugin from http:\/\/www.vim.org\/scripts\/script.php?script_id=3380 and save it to the plugin\r\n    folder vim (usualy ~\/.vim\/plugin\/)\r\n  * Or from git repository:\r\n        git clone git:\/\/github.com\/rezwyi\/vimorator.git\r\n        cd vimorator\/\r\n        ln -s vimorator.vim \/path\/to\/vim's\/plugins\/vimorator.vim\r\n  * It is possible to redefine several global variables in your .vimrc:\r\n        \"Hot key (<F2> by default)\r\n        let g:vimorator_hotkey = <F3>\r\n\r\n        \"tnsnames.ora file ($TNS_ADMIN by default)\r\n        let g:vimorator_tns_admin = $HOME . \"\/.sqlplus\/\"\r\n\r\n        \"Username and password for executing commands\r\n        let g:vimorator_user = \"scott\"\r\n        let g:vimorator_pass = \"scott\"","5":"  * Download the plugin from http:\/\/www.vim.org\/scripts\/script.php?script_id=3380 and save it to the plugin\r\n    folder vim (usualy ~\/.vim\/plugin\/)\r\n  * Or from git repository:\r\n        git clone git:\/\/github.com\/rezwyi\/vimorator.git\r\n        cd vimorator\/\r\n        ln -s vimorator.vim \/path\/to\/vim's\/plugins\/vimorator.vim\r\n  * It is possible to redefine several global variables in your .vimrc:\r\n        \"Hot key (<F2> by default)\r\n        let g:vimorator_hotkey = <F3>\r\n\r\n        \"tnsnames.ora file ($TNS_ADMIN by default)\r\n        let g:vimorator_tns_admin = $HOME . \"\/.sqlplus\/\"\r\n\r\n        \"Username and password for executing commands\r\n        let g:vimorator_user = \"scott\"\r\n        let g:vimorator_pass = \"scott\"","first_name":"Sergey","6":"Sergey","last_name":"Rezvanov","7":"Rezvanov","releases":[{"0":"3380","vim_version":"7.0","1":"7.0","script_version":"1.1","2":"1.1","version_comment":"Minor fixes","3":"Minor fixes","package":"vimorator.vim","4":"vimorator.vim","src_id":"15234","5":"15234","creation_date":"1300386868","6":"1300386868"},{"0":"3380","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"vimorator.vim","4":"vimorator.vim","src_id":"14622","5":"14622","creation_date":"1293353338","6":"1293353338"}]},"3379":{"script_id":"3379","0":"3379","script_name":"JumpNextLongLine","1":"JumpNextLongLine","script_type":"utility","2":"utility","summary":"Jump to the next line that exceeds the &textwidth option.","3":"Jump to the next line that exceeds the &textwidth option.","description":"Jump Next Long Line\r\n===================\r\n\r\nVim plugin to jump to the next line that exceed the textwidth setting\r\nLast Change: 2018 Dec 26\r\nMaintainer: Caio Rom\u00c3\u00a3o https:\/\/caio.co\r\nLicense: This file is placed in the public domain\r\n\r\nMappings:\r\n   <Leader>l or <Plug>JumpNextLongLine\r\n       Jumps to the next (too) long line\r\n\r\nThis plugin doesn't have any settings.","4":"Jump Next Long Line\r\n===================\r\n\r\nVim plugin to jump to the next line that exceed the textwidth setting\r\nLast Change: 2018 Dec 26\r\nMaintainer: Caio Rom\u00c3\u00a3o https:\/\/caio.co\r\nLicense: This file is placed in the public domain\r\n\r\nMappings:\r\n   <Leader>l or <Plug>JumpNextLongLine\r\n       Jumps to the next (too) long line\r\n\r\nThis plugin doesn't have any settings.","install_details":"","5":"","first_name":"Caio","6":"Caio","last_name":"Rom\u00c3\u00a3o","7":"Rom\u00c3\u00a3o","releases":[{"0":"3379","vim_version":"7.0","1":"7.0","script_version":"0.2","2":"0.2","version_comment":"2010 me thought building a list of all the file's long lines was a good idea. 2018 me knows better. This plugin is faster and simpler now and development is effectively halted as I don't have a use for it anymore. ","3":"2010 me thought building a list of all the file's long lines was a good idea. 2018 me knows better. This plugin is faster and simpler now and development is effectively halted as I don't have a use for it anymore. ","package":"jumpnextlongline.vim","4":"jumpnextlongline.vim","src_id":"26309","5":"26309","creation_date":"1545857309","6":"1545857309"},{"0":"3379","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"jumpnextlongline.vim","4":"jumpnextlongline.vim","src_id":"14613","5":"14613","creation_date":"1293218998","6":"1293218998"}]},"3378":{"script_id":"3378","0":"3378","script_name":"vcslogdiff","1":"vcslogdiff","script_type":"utility","2":"utility","summary":"Plugin to vcscommand.vim to allow easy diffing in log window","3":"Plugin to vcscommand.vim to allow easy diffing in log window","description":"Vim script for enhancing the vcscommand.vim script. You can easily diff between two\r\nrevisions in the log window. It also add coloring to the log buffer too. Right now it supports svn and hg.\r\n\r\nUSAGE:\r\n- Call VCSLog\r\n- Go to revision a, press 's'\r\n- Go to revision b, press 's'\r\n- Press 'd' to launch GUI diff","4":"Vim script for enhancing the vcscommand.vim script. You can easily diff between two\r\nrevisions in the log window. It also add coloring to the log buffer too. Right now it supports svn and hg.\r\n\r\nUSAGE:\r\n- Call VCSLog\r\n- Go to revision a, press 's'\r\n- Go to revision b, press 's'\r\n- Press 'd' to launch GUI diff","install_details":"Note: currently only works on Linux\r\n\r\nRequires: \r\n- diffuse\r\n- vim compiled with +sign\r\n\r\nTo install, simply drop it in ~\/.vim\/plugin.","5":"Note: currently only works on Linux\r\n\r\nRequires: \r\n- diffuse\r\n- vim compiled with +sign\r\n\r\nTo install, simply drop it in ~\/.vim\/plugin.","first_name":"Wenzhi","6":"Wenzhi","last_name":"Liang","7":"Liang","releases":[{"0":"3378","vim_version":"7.0","1":"7.0","script_version":"0.2","2":"0.2","version_comment":"Added CVS support","3":"Added CVS support","package":"vcslogdiff.vim","4":"vcslogdiff.vim","src_id":"20943","5":"20943","creation_date":"1382446124","6":"1382446124"},{"0":"3378","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"vcslogdiff.vim","4":"vcslogdiff.vim","src_id":"14612","5":"14612","creation_date":"1293213877","6":"1293213877"}]},"3377":{"script_id":"3377","0":"3377","script_name":"Vimblr","1":"Vimblr","script_type":"utility","2":"utility","summary":"Post to Tumblr right from Vim","3":"Post to Tumblr right from Vim","description":"Fork on GitHub! https:\/\/github.com\/mitchj\/Vimblr\r\n\r\nThis allows you to post text, quotes, links and chats to your Tumblr blog.","4":"Fork on GitHub! https:\/\/github.com\/mitchj\/Vimblr\r\n\r\nThis allows you to post text, quotes, links and chats to your Tumblr blog.","install_details":"Put doc\/ and plugin\/ into ~\/.vim","5":"Put doc\/ and plugin\/ into ~\/.vim","first_name":"Mitch","6":"Mitch","last_name":"Johnson","7":"Johnson","releases":[{"0":"3377","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"vimblr.zip","4":"vimblr.zip","src_id":"14609","5":"14609","creation_date":"1293156870","6":"1293156870"}]},"3376":{"script_id":"3376","0":"3376","script_name":"FanVim","1":"FanVim","script_type":"utility","2":"utility","summary":"Fanfou client for Vim","3":"Fanfou client for Vim","description":"    FanVim allows you to post your current status to Fanfou from Vim.\r\n\r\n    Specail thanks to Po Shan Cheah, FanVim is modified from his TwitVim.\r\n\r\n\r\n        website: http:\/\/jiapad.com\r\n        twitter: http:\/\/twitter.com\/sogood\r\n        fanfou: http:\/\/fanfou.com\/stranger","4":"    FanVim allows you to post your current status to Fanfou from Vim.\r\n\r\n    Specail thanks to Po Shan Cheah, FanVim is modified from his TwitVim.\r\n\r\n\r\n        website: http:\/\/jiapad.com\r\n        twitter: http:\/\/twitter.com\/sogood\r\n        fanfou: http:\/\/fanfou.com\/stranger","install_details":"","5":"","first_name":"jia","6":"jia","last_name":"shaw","7":"shaw","releases":[{"0":"3376","vim_version":"7.0","1":"7.0","script_version":"0.1.1","2":"0.1.1","version_comment":"Fix the source problem","3":"Fix the source problem","package":"fanvim0.1-final.zip","4":"fanvim0.1-final.zip","src_id":"14685","5":"14685","creation_date":"1294243309","6":"1294243309"}]},"3375":{"script_id":"3375","0":"3375","script_name":"notes.vim","1":"notes.vim","script_type":"utility","2":"utility","summary":"Easy note taking in Vim","3":"Easy note taking in Vim","description":"The notes.vim plug-in makes it easy to manage your notes in Vim by providing several (automatic) commands and an advanced syntax mode. For more information about the plug-in please refer to its homepage or the project page on GitHub:\r\n\r\n \u00e2\u0080\u00a2 http:\/\/peterodding.com\/code\/vim\/notes\/\r\n \u00e2\u0080\u00a2 http:\/\/github.com\/xolox\/vim-notes\r\n\r\nIf you have questions, bug reports, suggestions, etc. the author can be contacted at peter@peterodding.com. If you like this plug-in please vote for it below!","4":"The notes.vim plug-in makes it easy to manage your notes in Vim by providing several (automatic) commands and an advanced syntax mode. For more information about the plug-in please refer to its homepage or the project page on GitHub:\r\n\r\n \u00e2\u0080\u00a2 http:\/\/peterodding.com\/code\/vim\/notes\/\r\n \u00e2\u0080\u00a2 http:\/\/github.com\/xolox\/vim-notes\r\n\r\nIf you have questions, bug reports, suggestions, etc. the author can be contacted at peter@peterodding.com. If you like this plug-in please vote for it below!","install_details":"Please note that the vim-notes plug-in requires my vim-misc plug-in which is separately distributed (see vimscript #4597).\r\n\r\nUnzip the most recent ZIP archives of the vim-notes and vim-misc plug-ins inside your Vim profile directory (usually this is ~\/.vim on UNIX and %USERPROFILE%\\vimfiles on Windows), restart Vim and execute the command :helptags ~\/.vim\/doc (use :helptags ~\\vimfiles\\doc instead on Windows). To get started execute :Note or :edit note:, this will start a new note that contains instructions on how to continue from there (and how to use the plug-in in general).\r\n\r\nIf you prefer you can also use Pathogen, Vundle or a similar tool to install & update the vim-notes and vim-misc plug-ins using a local clone of the git repository.","5":"Please note that the vim-notes plug-in requires my vim-misc plug-in which is separately distributed (see vimscript #4597).\r\n\r\nUnzip the most recent ZIP archives of the vim-notes and vim-misc plug-ins inside your Vim profile directory (usually this is ~\/.vim on UNIX and %USERPROFILE%\\vimfiles on Windows), restart Vim and execute the command :helptags ~\/.vim\/doc (use :helptags ~\\vimfiles\\doc instead on Windows). To get started execute :Note or :edit note:, this will start a new note that contains instructions on how to continue from there (and how to use the plug-in in general).\r\n\r\nIf you prefer you can also use Pathogen, Vundle or a similar tool to install & update the vim-notes and vim-misc plug-ins using a local clone of the git repository.","first_name":"Peter","6":"Peter","last_name":"Odding","7":"Odding","releases":[{"0":"3375","vim_version":"7.0","1":"7.0","script_version":"0.33.4","2":"0.33.4","version_comment":" \u00e2\u0080\u00a2 Make :SearchNotes work properly without vim-shell (fixes #53):\n   http:\/\/github.com\/xolox\/vim-notes\/commit\/e465a0a","3":" \u00e2\u0080\u00a2 Make :SearchNotes work properly without vim-shell (fixes #53):\n   http:\/\/github.com\/xolox\/vim-notes\/commit\/e465a0a","package":"notes.zip","4":"notes.zip","src_id":"23710","5":"23710","creation_date":"1446662294","6":"1446662294"},{"0":"3375","vim_version":"7.0","1":"7.0","script_version":"0.33.3","2":"0.33.3","version_comment":" \u00e2\u0080\u00a2 Add lots of debug logging (related to issue #53):\n   http:\/\/github.com\/xolox\/vim-notes\/commit\/08b9747","3":" \u00e2\u0080\u00a2 Add lots of debug logging (related to issue #53):\n   http:\/\/github.com\/xolox\/vim-notes\/commit\/08b9747","package":"notes.zip","4":"notes.zip","src_id":"23701","5":"23701","creation_date":"1446387176","6":"1446387176"},{"0":"3375","vim_version":"7.0","1":"7.0","script_version":"0.33.2","2":"0.33.2","version_comment":" \u00e2\u0080\u00a2 Document issue #53 in the README:\n   http:\/\/github.com\/xolox\/vim-notes\/commit\/9b7eb4e","3":" \u00e2\u0080\u00a2 Document issue #53 in the README:\n   http:\/\/github.com\/xolox\/vim-notes\/commit\/9b7eb4e","package":"notes.zip","4":"notes.zip","src_id":"23699","5":"23699","creation_date":"1446380083","6":"1446380083"},{"0":"3375","vim_version":"7.0","1":"7.0","script_version":"0.33.1","2":"0.33.1","version_comment":" \u00e2\u0080\u00a2 Document how to use notes file type for git commit messages:\n   http:\/\/github.com\/xolox\/vim-notes\/commit\/070439c\n\n \u00e2\u0080\u00a2 Improve getting started instructions:\n   http:\/\/github.com\/xolox\/vim-notes\/commit\/b7c26af\n\n \u00e2\u0080\u00a2 Bug fix for git commit message trick in documentation:\n   http:\/\/github.com\/xolox\/vim-notes\/commit\/6c55c66\n\n \u00e2\u0080\u00a2 Fix superficial Python 3 incompatibilities in search-notes.py:\n   http:\/\/github.com\/xolox\/vim-notes\/commit\/464d006\n\n \u00e2\u0080\u00a2 Only enable logging when connected to interactive terminal (issue #53):\n   http:\/\/github.com\/xolox\/vim-notes\/commit\/65f5455\n\n \u00e2\u0080\u00a2 Use null handler to avoid noise on stderr (issue #53):\n   http:\/\/github.com\/xolox\/vim-notes\/commit\/d7c5055","3":" \u00e2\u0080\u00a2 Document how to use notes file type for git commit messages:\n   http:\/\/github.com\/xolox\/vim-notes\/commit\/070439c\n\n \u00e2\u0080\u00a2 Improve getting started instructions:\n   http:\/\/github.com\/xolox\/vim-notes\/commit\/b7c26af\n\n \u00e2\u0080\u00a2 Bug fix for git commit message trick in documentation:\n   http:\/\/github.com\/xolox\/vim-notes\/commit\/6c55c66\n\n \u00e2\u0080\u00a2 Fix superficial Python 3 incompatibilities in search-notes.py:\n   http:\/\/github.com\/xolox\/vim-notes\/commit\/464d006\n\n \u00e2\u0080\u00a2 Only enable logging when connected to interactive terminal (issue #53):\n   http:\/\/github.com\/xolox\/vim-notes\/commit\/65f5455\n\n \u00e2\u0080\u00a2 Use null handler to avoid noise on stderr (issue #53):\n   http:\/\/github.com\/xolox\/vim-notes\/commit\/d7c5055","package":"notes.zip","4":"notes.zip","src_id":"23697","5":"23697","creation_date":"1446378478","6":"1446378478"},{"0":"3375","vim_version":"7.0","1":"7.0","script_version":"0.33","2":"0.33","version_comment":" \u00e2\u0080\u00a2 Enable showing code block markers:\n   http:\/\/github.com\/xolox\/vim-notes\/commit\/34541a0","3":" \u00e2\u0080\u00a2 Enable showing code block markers:\n   http:\/\/github.com\/xolox\/vim-notes\/commit\/34541a0","package":"notes.zip","4":"notes.zip","src_id":"23116","5":"23116","creation_date":"1427918045","6":"1427918045"},{"0":"3375","vim_version":"7.0","1":"7.0","script_version":"0.32","2":"0.32","version_comment":" \u00e2\u0080\u00a2 Document text folding of headers (issue #106):\n   http:\/\/github.com\/xolox\/vim-notes\/commit\/1757bf6\n\n \u00e2\u0080\u00a2 Merge pull request #104: Make concealing configurable:\n   http:\/\/github.com\/xolox\/vim-notes\/commit\/5616b08","3":" \u00e2\u0080\u00a2 Document text folding of headers (issue #106):\n   http:\/\/github.com\/xolox\/vim-notes\/commit\/1757bf6\n\n \u00e2\u0080\u00a2 Merge pull request #104: Make concealing configurable:\n   http:\/\/github.com\/xolox\/vim-notes\/commit\/5616b08","package":"notes.zip","4":"notes.zip","src_id":"23036","5":"23036","creation_date":"1426426153","6":"1426426153"},{"0":"3375","vim_version":"7.0","1":"7.0","script_version":"0.31.1","2":"0.31.1","version_comment":" \u00e2\u0080\u00a2 Added ability to open html in a new split.:\n   http:\/\/github.com\/xolox\/vim-notes\/commit\/caac537\n\n \u00e2\u0080\u00a2 Added support for converting to Mediawiki syntax.:\n   http:\/\/github.com\/xolox\/vim-notes\/commit\/59c77f9\n\n \u00e2\u0080\u00a2 Updated documentation to contain :NoteToMediawiki:\n   http:\/\/github.com\/xolox\/vim-notes\/commit\/57a4c02\n\n \u00e2\u0080\u00a2 Added coloring to TODO, XXX, and strikethrough  to DONE:\n   http:\/\/github.com\/xolox\/vim-notes\/commit\/2a996a9\n\n \u00e2\u0080\u00a2 Fixed case matching.:\n   http:\/\/github.com\/xolox\/vim-notes\/commit\/703508d\n\n \u00e2\u0080\u00a2 Merge pull request #103: Open HTML in split & Mediawiki converter:\n   http:\/\/github.com\/xolox\/vim-notes\/commit\/ed6d6e7\n\n \u00e2\u0080\u00a2 Easy customization of new note template (also from command line):\n   http:\/\/github.com\/xolox\/vim-notes\/commit\/d306012\n\n \u00e2\u0080\u00a2 Fix issue #102: Code block detection seems somewhat broken:\n   http:\/\/github.com\/xolox\/vim-notes\/commit\/23b4f1e","3":" \u00e2\u0080\u00a2 Added ability to open html in a new split.:\n   http:\/\/github.com\/xolox\/vim-notes\/commit\/caac537\n\n \u00e2\u0080\u00a2 Added support for converting to Mediawiki syntax.:\n   http:\/\/github.com\/xolox\/vim-notes\/commit\/59c77f9\n\n \u00e2\u0080\u00a2 Updated documentation to contain :NoteToMediawiki:\n   http:\/\/github.com\/xolox\/vim-notes\/commit\/57a4c02\n\n \u00e2\u0080\u00a2 Added coloring to TODO, XXX, and strikethrough  to DONE:\n   http:\/\/github.com\/xolox\/vim-notes\/commit\/2a996a9\n\n \u00e2\u0080\u00a2 Fixed case matching.:\n   http:\/\/github.com\/xolox\/vim-notes\/commit\/703508d\n\n \u00e2\u0080\u00a2 Merge pull request #103: Open HTML in split & Mediawiki converter:\n   http:\/\/github.com\/xolox\/vim-notes\/commit\/ed6d6e7\n\n \u00e2\u0080\u00a2 Easy customization of new note template (also from command line):\n   http:\/\/github.com\/xolox\/vim-notes\/commit\/d306012\n\n \u00e2\u0080\u00a2 Fix issue #102: Code block detection seems somewhat broken:\n   http:\/\/github.com\/xolox\/vim-notes\/commit\/23b4f1e","package":"notes.zip","4":"notes.zip","src_id":"23016","5":"23016","creation_date":"1426237567","6":"1426237567"},{"0":"3375","vim_version":"7.0","1":"7.0","script_version":"0.29","2":"0.29","version_comment":" \u00e2\u0080\u00a2 Document usage of multiple platforms (issue #85):\n   https:\/\/github.com\/xolox\/vim-notes\/commit\/eaf2d44\n\n \u00e2\u0080\u00a2 Emit proper Markdown horizontal rulers in conversion to Markdown format:\n   https:\/\/github.com\/xolox\/vim-notes\/commit\/5ddf420\n\n \u00e2\u0080\u00a2 Merge pull request 98: Accept ``` code markers (similar to GFM*):\n   https:\/\/github.com\/xolox\/vim-notes\/commit\/6f4ad2b","3":" \u00e2\u0080\u00a2 Document usage of multiple platforms (issue #85):\n   https:\/\/github.com\/xolox\/vim-notes\/commit\/eaf2d44\n\n \u00e2\u0080\u00a2 Emit proper Markdown horizontal rulers in conversion to Markdown format:\n   https:\/\/github.com\/xolox\/vim-notes\/commit\/5ddf420\n\n \u00e2\u0080\u00a2 Merge pull request 98: Accept ``` code markers (similar to GFM*):\n   https:\/\/github.com\/xolox\/vim-notes\/commit\/6f4ad2b","package":"notes.zip","4":"notes.zip","src_id":"22652","5":"22652","creation_date":"1417125399","6":"1417125399"},{"0":"3375","vim_version":"7.0","1":"7.0","script_version":"0.28.1","2":"0.28.1","version_comment":" \u00e2\u0080\u00a2 Start using 'syntax sync fromstart' until we find a better way:\n   http:\/\/github.com\/xolox\/vim-notes\/commit\/7a721b7","3":" \u00e2\u0080\u00a2 Start using 'syntax sync fromstart' until we find a better way:\n   http:\/\/github.com\/xolox\/vim-notes\/commit\/7a721b7","package":"notes.zip","4":"notes.zip","src_id":"22600","5":"22600","creation_date":"1415050295","6":"1415050295"},{"0":"3375","vim_version":"7.0","1":"7.0","script_version":"0.28","2":"0.28","version_comment":" \u00e2\u0080\u00a2 Trigger BufWritePre\/BufWritePost autocmd events in xolox#notes#save():\n   http:\/\/github.com\/xolox\/vim-notes\/commit\/1dcfacd","3":" \u00e2\u0080\u00a2 Trigger BufWritePre\/BufWritePost autocmd events in xolox#notes#save():\n   http:\/\/github.com\/xolox\/vim-notes\/commit\/1dcfacd","package":"notes.zip","4":"notes.zip","src_id":"22548","5":"22548","creation_date":"1413832707","6":"1413832707"},{"0":"3375","vim_version":"7.0","1":"7.0","script_version":"0.27","2":"0.27","version_comment":" \u00e2\u0080\u00a2 Disable special key mappings inside {{{ snippets }}}:\n   http:\/\/github.com\/xolox\/vim-notes\/commit\/a6a654f","3":" \u00e2\u0080\u00a2 Disable special key mappings inside {{{ snippets }}}:\n   http:\/\/github.com\/xolox\/vim-notes\/commit\/a6a654f","package":"notes.zip","4":"notes.zip","src_id":"22424","5":"22424","creation_date":"1410697303","6":"1410697303"},{"0":"3375","vim_version":"7.0","1":"7.0","script_version":"0.26.1","2":"0.26.1","version_comment":" \u00e2\u0080\u00a2 Clarify intent of notes_title_sync option in readme (issue #23):\n   http:\/\/github.com\/xolox\/vim-notes\/commit\/e900224\n\n \u00e2\u0080\u00a2 Bug fix for issue #77: Error when deleting note when there are no buffers:\n   http:\/\/github.com\/xolox\/vim-notes\/commit\/7a500ba","3":" \u00e2\u0080\u00a2 Clarify intent of notes_title_sync option in readme (issue #23):\n   http:\/\/github.com\/xolox\/vim-notes\/commit\/e900224\n\n \u00e2\u0080\u00a2 Bug fix for issue #77: Error when deleting note when there are no buffers:\n   http:\/\/github.com\/xolox\/vim-notes\/commit\/7a500ba","package":"notes.zip","4":"notes.zip","src_id":"22288","5":"22288","creation_date":"1407183860","6":"1407183860"},{"0":"3375","vim_version":"7.0","1":"7.0","script_version":"0.26","2":"0.26","version_comment":" \u00e2\u0080\u00a2 Highlight inline code fragments (issue #60):\n   http:\/\/github.com\/xolox\/vim-notes\/commit\/7de3c95","3":" \u00e2\u0080\u00a2 Highlight inline code fragments (issue #60):\n   http:\/\/github.com\/xolox\/vim-notes\/commit\/7de3c95","package":"notes.zip","4":"notes.zip","src_id":"22147","5":"22147","creation_date":"1404690562","6":"1404690562"},{"0":"3375","vim_version":"7.0","1":"7.0","script_version":"0.25.2","2":"0.25.2","version_comment":" \u00e2\u0080\u00a2 Add dash to 'iskeyword' so it can be used in tags (issue #61):\n   http:\/\/github.com\/xolox\/vim-notes\/commit\/9c8e701","3":" \u00e2\u0080\u00a2 Add dash to 'iskeyword' so it can be used in tags (issue #61):\n   http:\/\/github.com\/xolox\/vim-notes\/commit\/9c8e701","package":"notes.zip","4":"notes.zip","src_id":"22144","5":"22144","creation_date":"1404686036","6":"1404686036"},{"0":"3375","vim_version":"7.0","1":"7.0","script_version":"0.25.1","2":"0.25.1","version_comment":" \u00e2\u0080\u00a2 Add word boundary to Vim command highlighting (issue #59):\n   http:\/\/github.com\/xolox\/vim-notes\/commit\/a09f683","3":" \u00e2\u0080\u00a2 Add word boundary to Vim command highlighting (issue #59):\n   http:\/\/github.com\/xolox\/vim-notes\/commit\/a09f683","package":"notes.zip","4":"notes.zip","src_id":"22143","5":"22143","creation_date":"1404682212","6":"1404682212"},{"0":"3375","vim_version":"7.0","1":"7.0","script_version":"0.25","2":"0.25","version_comment":" \u00e2\u0080\u00a2 Merge pull request #49: Add option to disable Unicode:\n   http:\/\/github.com\/xolox\/vim-notes\/commit\/e88a8d1","3":" \u00e2\u0080\u00a2 Merge pull request #49: Add option to disable Unicode:\n   http:\/\/github.com\/xolox\/vim-notes\/commit\/e88a8d1","package":"notes.zip","4":"notes.zip","src_id":"22142","5":"22142","creation_date":"1404681132","6":"1404681132"},{"0":"3375","vim_version":"7.0","1":"7.0","script_version":"0.24","2":"0.24","version_comment":" \u00e2\u0080\u00a2 First attempt* at support for notes in nested directories (issue #71):\n   http:\/\/github.com\/xolox\/vim-notes\/commit\/677a27f","3":" \u00e2\u0080\u00a2 First attempt* at support for notes in nested directories (issue #71):\n   http:\/\/github.com\/xolox\/vim-notes\/commit\/677a27f","package":"notes.zip","4":"notes.zip","src_id":"22138","5":"22138","creation_date":"1404665138","6":"1404665138"},{"0":"3375","vim_version":"7.0","1":"7.0","script_version":"0.23.11","2":"0.23.11","version_comment":" \u00e2\u0080\u00a2 Change ASCII style bidirectional arrows to Unicode:\n   http:\/\/github.com\/xolox\/vim-notes\/commit\/2e416bd\n\n \u00e2\u0080\u00a2 Add logging to :SearchNotes in order to debug issue #53 on GitHub:\n   http:\/\/github.com\/xolox\/vim-notes\/commit\/68c1d55\n\n \u00e2\u0080\u00a2 Don't sync title for shadow notes:\n   http:\/\/github.com\/xolox\/vim-notes\/commit\/de6546f\n\n \u00e2\u0080\u00a2 Merge pull request #69: Don't sync title for shadow notes:\n   http:\/\/github.com\/xolox\/vim-notes\/commit\/3246ed6","3":" \u00e2\u0080\u00a2 Change ASCII style bidirectional arrows to Unicode:\n   http:\/\/github.com\/xolox\/vim-notes\/commit\/2e416bd\n\n \u00e2\u0080\u00a2 Add logging to :SearchNotes in order to debug issue #53 on GitHub:\n   http:\/\/github.com\/xolox\/vim-notes\/commit\/68c1d55\n\n \u00e2\u0080\u00a2 Don't sync title for shadow notes:\n   http:\/\/github.com\/xolox\/vim-notes\/commit\/de6546f\n\n \u00e2\u0080\u00a2 Merge pull request #69: Don't sync title for shadow notes:\n   http:\/\/github.com\/xolox\/vim-notes\/commit\/3246ed6","package":"notes.zip","4":"notes.zip","src_id":"22108","5":"22108","creation_date":"1404052840","6":"1404052840"},{"0":"3375","vim_version":"7.0","1":"7.0","script_version":"0.23.8","2":"0.23.8","version_comment":" \u00e2\u0080\u00a2 Bug fix for issue #68 (silence E403):\n   http:\/\/github.com\/xolox\/vim-notes\/commit\/825230a","3":" \u00e2\u0080\u00a2 Bug fix for issue #68 (silence E403):\n   http:\/\/github.com\/xolox\/vim-notes\/commit\/825230a","package":"notes.zip","4":"notes.zip","src_id":"22049","5":"22049","creation_date":"1403042813","6":"1403042813"},{"0":"3375","vim_version":"7.0","1":"7.0","script_version":"0.23.6","2":"0.23.6","version_comment":" \u00e2\u0080\u00a2 Try to resolve issue #62 - Apostrophes are turned into curly quotes:\n   http:\/\/github.com\/xolox\/vim-notes\/commit\/cb5c3cc","3":" \u00e2\u0080\u00a2 Try to resolve issue #62 - Apostrophes are turned into curly quotes:\n   http:\/\/github.com\/xolox\/vim-notes\/commit\/cb5c3cc","package":"notes.zip","4":"notes.zip","src_id":"22038","5":"22038","creation_date":"1402955027","6":"1402955027"},{"0":"3375","vim_version":"7.0","1":"7.0","script_version":"0.23.5","2":"0.23.5","version_comment":" \u00e2\u0080\u00a2 Option to highlight note names on word boundaries (pull request #67):\n   http:\/\/github.com\/xolox\/vim-notes\/commit\/e91ed34","3":" \u00e2\u0080\u00a2 Option to highlight note names on word boundaries (pull request #67):\n   http:\/\/github.com\/xolox\/vim-notes\/commit\/e91ed34","package":"notes.zip","4":"notes.zip","src_id":"22031","5":"22031","creation_date":"1402946469","6":"1402946469"},{"0":"3375","vim_version":"7.0","1":"7.0","script_version":"0.23.4","2":"0.23.4","version_comment":" \u00e2\u0080\u00a2 Translate Vim's awkward E480 stack trace into a clean error message (reported by Joakim Fremstad):\n   http:\/\/github.com\/xolox\/vim-notes\/commit\/14838be","3":" \u00e2\u0080\u00a2 Translate Vim's awkward E480 stack trace into a clean error message (reported by Joakim Fremstad):\n   http:\/\/github.com\/xolox\/vim-notes\/commit\/14838be","package":"notes.zip","4":"notes.zip","src_id":"20744","5":"20744","creation_date":"1378153993","6":"1378153993"},{"0":"3375","vim_version":"7.0","1":"7.0","script_version":"0.23.3","2":"0.23.3","version_comment":" \u00e2\u0080\u00a2 Improvements to search-notes.py:\n   http:\/\/github.com\/xolox\/vim-notes\/commit\/db6f35b\n\n \u00e2\u0080\u00a2 Bug fix for communication between notes.vim and search-notes.py* (reported by Joakim Fremstad):\n   http:\/\/github.com\/xolox\/vim-notes\/commit\/1e55003","3":" \u00e2\u0080\u00a2 Improvements to search-notes.py:\n   http:\/\/github.com\/xolox\/vim-notes\/commit\/db6f35b\n\n \u00e2\u0080\u00a2 Bug fix for communication between notes.vim and search-notes.py* (reported by Joakim Fremstad):\n   http:\/\/github.com\/xolox\/vim-notes\/commit\/1e55003","package":"notes.zip","4":"notes.zip","src_id":"20743","5":"20743","creation_date":"1378153458","6":"1378153458"},{"0":"3375","vim_version":"7.0","1":"7.0","script_version":"0.23.2","2":"0.23.2","version_comment":" \u00e2\u0080\u00a2 Make sure vim-misc is installed, politely complain if it isn't:\n   http:\/\/github.com\/xolox\/vim-notes\/commit\/378dd12","3":" \u00e2\u0080\u00a2 Make sure vim-misc is installed, politely complain if it isn't:\n   http:\/\/github.com\/xolox\/vim-notes\/commit\/378dd12","package":"notes.zip","4":"notes.zip","src_id":"20684","5":"20684","creation_date":"1376933554","6":"1376933554"},{"0":"3375","vim_version":"7.0","1":"7.0","script_version":"0.23.1","2":"0.23.1","version_comment":" \u00e2\u0080\u00a2 Bug fix for note to Markdown conversion of list items (reported by Jonathan Reeve):\n   http:\/\/github.com\/xolox\/vim-notes\/commit\/1fe9135","3":" \u00e2\u0080\u00a2 Bug fix for note to Markdown conversion of list items (reported by Jonathan Reeve):\n   http:\/\/github.com\/xolox\/vim-notes\/commit\/1fe9135","package":"notes.zip","4":"notes.zip","src_id":"20539","5":"20539","creation_date":"1374182706","6":"1374182706"},{"0":"3375","vim_version":"7.0","1":"7.0","script_version":"0.23","2":"0.23","version_comment":" \u00e2\u0080\u00a2 Added 'In Progress' state (contributed by Georgi Gardev):\n   http:\/\/github.com\/xolox\/vim-notes\/commit\/85902b5\n   http:\/\/github.com\/xolox\/vim-notes\/commit\/2805297","3":" \u00e2\u0080\u00a2 Added 'In Progress' state (contributed by Georgi Gardev):\n   http:\/\/github.com\/xolox\/vim-notes\/commit\/85902b5\n   http:\/\/github.com\/xolox\/vim-notes\/commit\/2805297","package":"notes.zip","4":"notes.zip","src_id":"20532","5":"20532","creation_date":"1374000129","6":"1374000129"},{"0":"3375","vim_version":"7.0","1":"7.0","script_version":"0.22","2":"0.22","version_comment":" \u00e2\u0080\u00a2 Dead easy Markdown\/HTML conversion! (using new note parser):\n   http:\/\/github.com\/xolox\/vim-notes\/commit\/4907b6c","3":" \u00e2\u0080\u00a2 Dead easy Markdown\/HTML conversion! (using new note parser):\n   http:\/\/github.com\/xolox\/vim-notes\/commit\/4907b6c","package":"notes.zip","4":"notes.zip","src_id":"20410","5":"20410","creation_date":"1372021126","6":"1372021126"},{"0":"3375","vim_version":"7.0","1":"7.0","script_version":"0.21.5","2":"0.21.5","version_comment":" \u00e2\u0080\u00a2 Document vim-misc as external dependency (needs to be installed separately from now on):\n   http:\/\/github.com\/xolox\/vim-notes\/commit\/061c030\n\n \u00e2\u0080\u00a2 Bug fix for xolox#notes#select():\n   http:\/\/github.com\/xolox\/vim-notes\/commit\/825b30e","3":" \u00e2\u0080\u00a2 Document vim-misc as external dependency (needs to be installed separately from now on):\n   http:\/\/github.com\/xolox\/vim-notes\/commit\/061c030\n\n \u00e2\u0080\u00a2 Bug fix for xolox#notes#select():\n   http:\/\/github.com\/xolox\/vim-notes\/commit\/825b30e","package":"notes.zip","4":"notes.zip","src_id":"20205","5":"20205","creation_date":"1369484003","6":"1369484003"},{"0":"3375","vim_version":"7.0","1":"7.0","script_version":"0.21.3","2":"0.21.3","version_comment":" \u00e2\u0080\u00a2 Updated miscellaneous scripts:\n   http:\/\/github.com\/xolox\/vim-notes\/commit\/2956ee9","3":" \u00e2\u0080\u00a2 Updated miscellaneous scripts:\n   http:\/\/github.com\/xolox\/vim-notes\/commit\/2956ee9","package":"notes.zip","4":"notes.zip","src_id":"20180","5":"20180","creation_date":"1369054198","6":"1369054198"},{"0":"3375","vim_version":"7.0","1":"7.0","script_version":"0.21.2","2":"0.21.2","version_comment":" \u00e2\u0080\u00a2 Updated miscellaneous scripts:\n   http:\/\/github.com\/xolox\/vim-notes\/commit\/4b1b21d","3":" \u00e2\u0080\u00a2 Updated miscellaneous scripts:\n   http:\/\/github.com\/xolox\/vim-notes\/commit\/4b1b21d","package":"notes.zip","4":"notes.zip","src_id":"20168","5":"20168","creation_date":"1369003050","6":"1369003050"},{"0":"3375","vim_version":"7.0","1":"7.0","script_version":"0.21.1","2":"0.21.1","version_comment":" \u00e2\u0080\u00a2 Bug fix for previous commit (issue #38):\n   http:\/\/github.com\/xolox\/vim-notes\/commit\/9daf034","3":" \u00e2\u0080\u00a2 Bug fix for previous commit (issue #38):\n   http:\/\/github.com\/xolox\/vim-notes\/commit\/9daf034","package":"notes.zip","4":"notes.zip","src_id":"20145","5":"20145","creation_date":"1368663529","6":"1368663529"},{"0":"3375","vim_version":"7.0","1":"7.0","script_version":"0.21","2":"0.21","version_comment":" \u00e2\u0080\u00a2 New command :MostRecentNote (suggested by Jonathan Reeve):\n   http:\/\/github.com\/xolox\/vim-notes\/commit\/7c0d08b","3":" \u00e2\u0080\u00a2 New command :MostRecentNote (suggested by Jonathan Reeve):\n   http:\/\/github.com\/xolox\/vim-notes\/commit\/7c0d08b","package":"notes.zip","4":"notes.zip","src_id":"20144","5":"20144","creation_date":"1368657051","6":"1368657051"},{"0":"3375","vim_version":"7.0","1":"7.0","script_version":"0.20.1","2":"0.20.1","version_comment":" \u00e2\u0080\u00a2 Remove word boundary conditions from note name highlighting:\n   http:\/\/github.com\/xolox\/vim-notes\/commit\/a83b099","3":" \u00e2\u0080\u00a2 Remove word boundary conditions from note name highlighting:\n   http:\/\/github.com\/xolox\/vim-notes\/commit\/a83b099","package":"notes.zip","4":"notes.zip","src_id":"20140","5":"20140","creation_date":"1368565049","6":"1368565049"},{"0":"3375","vim_version":"7.0","1":"7.0","script_version":"0.20","2":"0.20","version_comment":" \u00e2\u0080\u00a2 Updated miscellaneous scripts:\n   http:\/\/github.com\/xolox\/vim-notes\/commit\/09120cd\n   http:\/\/github.com\/xolox\/vim-notes\/commit\/9c88b0e","3":" \u00e2\u0080\u00a2 Updated miscellaneous scripts:\n   http:\/\/github.com\/xolox\/vim-notes\/commit\/09120cd\n   http:\/\/github.com\/xolox\/vim-notes\/commit\/9c88b0e","package":"notes.zip","4":"notes.zip","src_id":"20122","5":"20122","creation_date":"1368481123","6":"1368481123"},{"0":"3375","vim_version":"7.0","1":"7.0","script_version":"0.19","2":"0.19","version_comment":" \u00e2\u0080\u00a2 Support for multiple directories with notes:\n   http:\/\/github.com\/xolox\/vim-notes\/commit\/a523c28","3":" \u00e2\u0080\u00a2 Support for multiple directories with notes:\n   http:\/\/github.com\/xolox\/vim-notes\/commit\/a523c28","package":"notes.zip","4":"notes.zip","src_id":"20100","5":"20100","creation_date":"1368382269","6":"1368382269"},{"0":"3375","vim_version":"7.0","1":"7.0","script_version":"0.18.3","2":"0.18.3","version_comment":" \u00e2\u0080\u00a2 Don't unnecessarily reload the file type \/ syntax:\n   http:\/\/github.com\/xolox\/vim-notes\/commit\/96e5c83\n\n \u00e2\u0080\u00a2 Make :NoteFromSelectedText compatible with selection=inclusive (reported by Sven Hergenhahn):\n   http:\/\/github.com\/xolox\/vim-notes\/commit\/cbf4f3b","3":" \u00e2\u0080\u00a2 Don't unnecessarily reload the file type \/ syntax:\n   http:\/\/github.com\/xolox\/vim-notes\/commit\/96e5c83\n\n \u00e2\u0080\u00a2 Make :NoteFromSelectedText compatible with selection=inclusive (reported by Sven Hergenhahn):\n   http:\/\/github.com\/xolox\/vim-notes\/commit\/cbf4f3b","package":"notes.zip","4":"notes.zip","src_id":"20035","5":"20035","creation_date":"1367872065","6":"1367872065"},{"0":"3375","vim_version":"7.0","1":"7.0","script_version":"0.18.1","2":"0.18.1","version_comment":" \u00e2\u0080\u00a2 Add options to disable Tab\/Alt indent\/dedent mappings (issue #25):\n   http:\/\/github.com\/xolox\/vim-notes\/commit\/f4a2bd8","3":" \u00e2\u0080\u00a2 Add options to disable Tab\/Alt indent\/dedent mappings (issue #25):\n   http:\/\/github.com\/xolox\/vim-notes\/commit\/f4a2bd8","package":"notes.zip","4":"notes.zip","src_id":"20023","5":"20023","creation_date":"1367773077","6":"1367773077"},{"0":"3375","vim_version":"7.0","1":"7.0","script_version":"0.18","2":"0.18","version_comment":" \u00e2\u0080\u00a2 Automatically cleanup old \"note:...\" buffers:\n   http:\/\/github.com\/xolox\/vim-notes\/commit\/ac3e0f5","3":" \u00e2\u0080\u00a2 Automatically cleanup old \"note:...\" buffers:\n   http:\/\/github.com\/xolox\/vim-notes\/commit\/ac3e0f5","package":"notes.zip","4":"notes.zip","src_id":"20022","5":"20022","creation_date":"1367770002","6":"1367770002"},{"0":"3375","vim_version":"7.0","1":"7.0","script_version":"0.17.11","2":"0.17.11","version_comment":" \u00e2\u0080\u00a2 Improve :RecentNotes buffer handling:\n   http:\/\/github.com\/xolox\/vim-notes\/commit\/ba73927","3":" \u00e2\u0080\u00a2 Improve :RecentNotes buffer handling:\n   http:\/\/github.com\/xolox\/vim-notes\/commit\/ba73927","package":"notes.zip","4":"notes.zip","src_id":"20021","5":"20021","creation_date":"1367761579","6":"1367761579"},{"0":"3375","vim_version":"7.0","1":"7.0","script_version":"0.17.10","2":"0.17.10","version_comment":" \u00e2\u0080\u00a2 Updated miscellaneous scripts:\n   http:\/\/github.com\/xolox\/vim-notes\/commit\/1cddae8","3":" \u00e2\u0080\u00a2 Updated miscellaneous scripts:\n   http:\/\/github.com\/xolox\/vim-notes\/commit\/1cddae8","package":"notes.zip","4":"notes.zip","src_id":"20005","5":"20005","creation_date":"1367487450","6":"1367487450"},{"0":"3375","vim_version":"7.0","1":"7.0","script_version":"0.17.9","2":"0.17.9","version_comment":" \u00e2\u0080\u00a2 Updated miscellaneous scripts:\n   http:\/\/github.com\/xolox\/vim-notes\/commit\/c22f65c","3":" \u00e2\u0080\u00a2 Updated miscellaneous scripts:\n   http:\/\/github.com\/xolox\/vim-notes\/commit\/c22f65c","package":"notes.zip","4":"notes.zip","src_id":"19957","5":"19957","creation_date":"1367159130","6":"1367159130"},{"0":"3375","vim_version":"7.0","1":"7.0","script_version":"0.17.8","2":"0.17.8","version_comment":" \u00e2\u0080\u00a2 Use *noremap flavor commands to create mappings:\n   http:\/\/github.com\/xolox\/vim-notes\/commit\/563ddd6\n   http:\/\/github.com\/xolox\/vim-notes\/commit\/63a707f","3":" \u00e2\u0080\u00a2 Use *noremap flavor commands to create mappings:\n   http:\/\/github.com\/xolox\/vim-notes\/commit\/563ddd6\n   http:\/\/github.com\/xolox\/vim-notes\/commit\/63a707f","package":"notes.zip","4":"notes.zip","src_id":"19954","5":"19954","creation_date":"1367104156","6":"1367104156"},{"0":"3375","vim_version":"7.0","1":"7.0","script_version":"0.17.7","2":"0.17.7","version_comment":" \u00e2\u0080\u00a2 Bug fix: Support case sensitive keyword searches (reported by Artem Shinkarov):\n   http:\/\/github.com\/xolox\/vim-notes\/commit\/af27b21\n\n \u00e2\u0080\u00a2 search-notes.py: Use cPickle when available:\n   http:\/\/github.com\/xolox\/vim-notes\/commit\/548f8bb\n\n \u00e2\u0080\u00a2 search-notes.py: Use logging module, add lots of logging (and timing):\n   http:\/\/github.com\/xolox\/vim-notes\/commit\/edcbac0\n\n \u00e2\u0080\u00a2 Improve title of quick-fix windows with search results:\n   http:\/\/github.com\/xolox\/vim-notes\/commit\/1732c6c\n\n \u00e2\u0080\u00a2 Improve highlighting in quick-fix windows:\n   http:\/\/github.com\/xolox\/vim-notes\/commit\/8f82c18\n\n \u00e2\u0080\u00a2 Improve verbose output & timing for keyword searches:\n   http:\/\/github.com\/xolox\/vim-notes\/commit\/6107bdf","3":" \u00e2\u0080\u00a2 Bug fix: Support case sensitive keyword searches (reported by Artem Shinkarov):\n   http:\/\/github.com\/xolox\/vim-notes\/commit\/af27b21\n\n \u00e2\u0080\u00a2 search-notes.py: Use cPickle when available:\n   http:\/\/github.com\/xolox\/vim-notes\/commit\/548f8bb\n\n \u00e2\u0080\u00a2 search-notes.py: Use logging module, add lots of logging (and timing):\n   http:\/\/github.com\/xolox\/vim-notes\/commit\/edcbac0\n\n \u00e2\u0080\u00a2 Improve title of quick-fix windows with search results:\n   http:\/\/github.com\/xolox\/vim-notes\/commit\/1732c6c\n\n \u00e2\u0080\u00a2 Improve highlighting in quick-fix windows:\n   http:\/\/github.com\/xolox\/vim-notes\/commit\/8f82c18\n\n \u00e2\u0080\u00a2 Improve verbose output & timing for keyword searches:\n   http:\/\/github.com\/xolox\/vim-notes\/commit\/6107bdf","package":"notes.zip","4":"notes.zip","src_id":"19885","5":"19885","creation_date":"1366567578","6":"1366567578"},{"0":"3375","vim_version":"7.0","1":"7.0","script_version":"0.17.3","2":"0.17.3","version_comment":" \u00e2\u0080\u00a2 Set default cterm values for notesItalic and notesBold (contributed by John Louis Del Rosario):\n   http:\/\/github.com\/xolox\/vim-notes\/commit\/aec487d","3":" \u00e2\u0080\u00a2 Set default cterm values for notesItalic and notesBold (contributed by John Louis Del Rosario):\n   http:\/\/github.com\/xolox\/vim-notes\/commit\/aec487d","package":"notes.zip","4":"notes.zip","src_id":"19882","5":"19882","creation_date":"1366537599","6":"1366537599"},{"0":"3375","vim_version":"7.0","1":"7.0","script_version":"0.17.2","2":"0.17.2","version_comment":" \u00e2\u0080\u00a2 Make compatibility with miscellaneous scripts explicit:\n   http:\/\/github.com\/xolox\/vim-notes\/commit\/1b19787","3":" \u00e2\u0080\u00a2 Make compatibility with miscellaneous scripts explicit:\n   http:\/\/github.com\/xolox\/vim-notes\/commit\/1b19787","package":"notes.zip","4":"notes.zip","src_id":"19871","5":"19871","creation_date":"1366501874","6":"1366501874"},{"0":"3375","vim_version":"7.0","1":"7.0","script_version":"0.17.1","2":"0.17.1","version_comment":" \u00e2\u0080\u00a2 Exclude \"anonymous\" swap files in search-notes.py (.s??):\n   http:\/\/github.com\/xolox\/vim-notes\/commit\/8881d41\n\n \u00e2\u0080\u00a2 Bug fix: Encode \":\" on Mac OS X in xolox#misc#path#encode():\n   http:\/\/github.com\/xolox\/vim-notes\/commit\/b88ab45\n\n \u00e2\u0080\u00a2 Remove misc\/notes\/user\/README, add .gitignore, document g:notes_directory (issue #28):\n   http:\/\/github.com\/xolox\/vim-notes\/commit\/2098494\n\n \u00e2\u0080\u00a2 Fix a stupid bug in search-notes.py (and clean it up a little):\n   http:\/\/github.com\/xolox\/vim-notes\/commit\/b75f9ab","3":" \u00e2\u0080\u00a2 Exclude \"anonymous\" swap files in search-notes.py (.s??):\n   http:\/\/github.com\/xolox\/vim-notes\/commit\/8881d41\n\n \u00e2\u0080\u00a2 Bug fix: Encode \":\" on Mac OS X in xolox#misc#path#encode():\n   http:\/\/github.com\/xolox\/vim-notes\/commit\/b88ab45\n\n \u00e2\u0080\u00a2 Remove misc\/notes\/user\/README, add .gitignore, document g:notes_directory (issue #28):\n   http:\/\/github.com\/xolox\/vim-notes\/commit\/2098494\n\n \u00e2\u0080\u00a2 Fix a stupid bug in search-notes.py (and clean it up a little):\n   http:\/\/github.com\/xolox\/vim-notes\/commit\/b75f9ab","package":"notes.zip","4":"notes.zip","src_id":"19854","5":"19854","creation_date":"1366313969","6":"1366313969"},{"0":"3375","vim_version":"7.0","1":"7.0","script_version":"0.16.16","2":"0.16.16","version_comment":" \u00e2\u0080\u00a2 Move file type detection back to plugin script (issues #16 & #17):\n   http:\/\/github.com\/xolox\/vim-notes\/commit\/9933c4f","3":" \u00e2\u0080\u00a2 Move file type detection back to plugin script (issues #16 & #17):\n   http:\/\/github.com\/xolox\/vim-notes\/commit\/9933c4f","package":"notes.zip","4":"notes.zip","src_id":"17065","5":"17065","creation_date":"1323889585","6":"1323889585"},{"0":"3375","vim_version":"7.0","1":"7.0","script_version":"0.16.15","2":"0.16.15","version_comment":" \u00e2\u0080\u00a2 Improve file type detection (respect 'g:notes_suffix', issue #16):\n   http:\/\/github.com\/xolox\/vim-notes\/commit\/4be5e0b","3":" \u00e2\u0080\u00a2 Improve file type detection (respect 'g:notes_suffix', issue #16):\n   http:\/\/github.com\/xolox\/vim-notes\/commit\/4be5e0b","package":"notes.zip","4":"notes.zip","src_id":"17056","5":"17056","creation_date":"1323631121","6":"1323631121"},{"0":"3375","vim_version":"7.0","1":"7.0","script_version":"0.16.14","2":"0.16.14","version_comment":" \u00e2\u0080\u00a2 Make sure the plug-in is always properly initialized (issue #15):\n   http:\/\/github.com\/xolox\/vim-notes\/commit\/5636ceb\n\n \u00e2\u0080\u00a2 :TabNoteFromSelectedText and \\en, \\sn, \\tn mappings (:edit, :split, :tabnew):\n   http:\/\/github.com\/xolox\/vim-notes\/commit\/d43f9c7","3":" \u00e2\u0080\u00a2 Make sure the plug-in is always properly initialized (issue #15):\n   http:\/\/github.com\/xolox\/vim-notes\/commit\/5636ceb\n\n \u00e2\u0080\u00a2 :TabNoteFromSelectedText and \\en, \\sn, \\tn mappings (:edit, :split, :tabnew):\n   http:\/\/github.com\/xolox\/vim-notes\/commit\/d43f9c7","package":"notes.zip","4":"notes.zip","src_id":"17006","5":"17006","creation_date":"1322772259","6":"1322772259"},{"0":"3375","vim_version":"7.0","1":"7.0","script_version":"0.16.12","2":"0.16.12","version_comment":" \u00e2\u0080\u00a2 Include the ftdetect\/notes.vim script (thanks Avi Yagodnick, sorry everyone else :-):\n   http:\/\/github.com\/xolox\/vim-notes\/commit\/b16493f","3":" \u00e2\u0080\u00a2 Include the ftdetect\/notes.vim script (thanks Avi Yagodnick, sorry everyone else :-):\n   http:\/\/github.com\/xolox\/vim-notes\/commit\/b16493f","package":"notes.zip","4":"notes.zip","src_id":"16985","5":"16985","creation_date":"1322398578","6":"1322398578"},{"0":"3375","vim_version":"7.0","1":"7.0","script_version":"0.16.11","2":"0.16.11","version_comment":" \u00e2\u0080\u00a2 Hints about how to use txtfmt.vim with notes.vim:\n   http:\/\/github.com\/xolox\/vim-notes\/commit\/51691c1\n   http:\/\/github.com\/xolox\/vim-notes\/commit\/e706a98\n\n \u00e2\u0080\u00a2 Improve compatibility with Txtfmt plug-in:\n   http:\/\/github.com\/xolox\/vim-notes\/commit\/e33b766\n\n \u00e2\u0080\u00a2 Improve filename synchronization dialog:\n   http:\/\/github.com\/xolox\/vim-notes\/commit\/78f03ae\n\n \u00e2\u0080\u00a2 Improve file synchronization mechanism (less prompts):\n   http:\/\/github.com\/xolox\/vim-notes\/commit\/7171b3e\n\n \u00e2\u0080\u00a2 Move file type detection to ftdetect\/notes.vim:\n   http:\/\/github.com\/xolox\/vim-notes\/commit\/1099756","3":" \u00e2\u0080\u00a2 Hints about how to use txtfmt.vim with notes.vim:\n   http:\/\/github.com\/xolox\/vim-notes\/commit\/51691c1\n   http:\/\/github.com\/xolox\/vim-notes\/commit\/e706a98\n\n \u00e2\u0080\u00a2 Improve compatibility with Txtfmt plug-in:\n   http:\/\/github.com\/xolox\/vim-notes\/commit\/e33b766\n\n \u00e2\u0080\u00a2 Improve filename synchronization dialog:\n   http:\/\/github.com\/xolox\/vim-notes\/commit\/78f03ae\n\n \u00e2\u0080\u00a2 Improve file synchronization mechanism (less prompts):\n   http:\/\/github.com\/xolox\/vim-notes\/commit\/7171b3e\n\n \u00e2\u0080\u00a2 Move file type detection to ftdetect\/notes.vim:\n   http:\/\/github.com\/xolox\/vim-notes\/commit\/1099756","package":"notes.zip","4":"notes.zip","src_id":"16978","5":"16978","creation_date":"1322310182","6":"1322310182"},{"0":"3375","vim_version":"7.0","1":"7.0","script_version":"0.16.7","2":"0.16.7","version_comment":" \u00e2\u0080\u00a2 Bug fix: Never sync titles of special buffers:\n   http:\/\/github.com\/xolox\/vim-notes\/commit\/42e110b\n\n \u00e2\u0080\u00a2 Updated miscellaneous scripts:\n   http:\/\/github.com\/xolox\/vim-notes\/commit\/9b4c774\n   http:\/\/github.com\/xolox\/vim-notes\/commit\/356853f\n   http:\/\/github.com\/xolox\/vim-notes\/commit\/668213c","3":" \u00e2\u0080\u00a2 Bug fix: Never sync titles of special buffers:\n   http:\/\/github.com\/xolox\/vim-notes\/commit\/42e110b\n\n \u00e2\u0080\u00a2 Updated miscellaneous scripts:\n   http:\/\/github.com\/xolox\/vim-notes\/commit\/9b4c774\n   http:\/\/github.com\/xolox\/vim-notes\/commit\/356853f\n   http:\/\/github.com\/xolox\/vim-notes\/commit\/668213c","package":"notes.zip","4":"notes.zip","src_id":"16969","5":"16969","creation_date":"1322267959","6":"1322267959"},{"0":"3375","vim_version":"7.0","1":"7.0","script_version":"0.16.5","2":"0.16.5","version_comment":" \u00e2\u0080\u00a2 Make the plug-in compatible with system wide installation:\n   http:\/\/github.com\/xolox\/vim-notes\/commit\/94cc679","3":" \u00e2\u0080\u00a2 Make the plug-in compatible with system wide installation:\n   http:\/\/github.com\/xolox\/vim-notes\/commit\/94cc679","package":"notes.zip","4":"notes.zip","src_id":"16966","5":"16966","creation_date":"1322254744","6":"1322254744"},{"0":"3375","vim_version":"7.0","1":"7.0","script_version":"0.16.4","2":"0.16.4","version_comment":" \u00e2\u0080\u00a2 Trust search-notes.py when it says there are no matches:\n   http:\/\/github.com\/xolox\/vim-notes\/commit\/78c4cd7\n\n \u00e2\u0080\u00a2 Make :SearchNotes user friendly (enable line wrapping, resize quick-fix window):\n   http:\/\/github.com\/xolox\/vim-notes\/commit\/d1ceea3\n\n \u00e2\u0080\u00a2 Bug fix for search-notes.py (wasn't scanning new notes :-\\):\n   http:\/\/github.com\/xolox\/vim-notes\/commit\/2cefa9d\n\n \u00e2\u0080\u00a2 Automatically highlight new code blocks:\n   http:\/\/github.com\/xolox\/vim-notes\/commit\/623bb04","3":" \u00e2\u0080\u00a2 Trust search-notes.py when it says there are no matches:\n   http:\/\/github.com\/xolox\/vim-notes\/commit\/78c4cd7\n\n \u00e2\u0080\u00a2 Make :SearchNotes user friendly (enable line wrapping, resize quick-fix window):\n   http:\/\/github.com\/xolox\/vim-notes\/commit\/d1ceea3\n\n \u00e2\u0080\u00a2 Bug fix for search-notes.py (wasn't scanning new notes :-\\):\n   http:\/\/github.com\/xolox\/vim-notes\/commit\/2cefa9d\n\n \u00e2\u0080\u00a2 Automatically highlight new code blocks:\n   http:\/\/github.com\/xolox\/vim-notes\/commit\/623bb04","package":"notes.zip","4":"notes.zip","src_id":"16963","5":"16963","creation_date":"1322247477","6":"1322247477"},{"0":"3375","vim_version":"7.0","1":"7.0","script_version":"0.16","2":"0.16","version_comment":" \u00e2\u0080\u00a2 New *** mapping to insert horizontal rulers:\n   http:\/\/github.com\/xolox\/vim-notes\/commit\/fabedb0\n\n \u00e2\u0080\u00a2 Highlight double quoted strings (distinct from single quoted strings):\n   http:\/\/github.com\/xolox\/vim-notes\/commit\/833f1f2\n\n \u00e2\u0080\u00a2 Documentation on customizing the syntax highlighting of notes:\n   http:\/\/github.com\/xolox\/vim-notes\/commit\/eb8a83c\n\n \u00e2\u0080\u00a2 Support for nested list items with user defined bullets:\n   http:\/\/github.com\/xolox\/vim-notes\/commit\/576333a","3":" \u00e2\u0080\u00a2 New *** mapping to insert horizontal rulers:\n   http:\/\/github.com\/xolox\/vim-notes\/commit\/fabedb0\n\n \u00e2\u0080\u00a2 Highlight double quoted strings (distinct from single quoted strings):\n   http:\/\/github.com\/xolox\/vim-notes\/commit\/833f1f2\n\n \u00e2\u0080\u00a2 Documentation on customizing the syntax highlighting of notes:\n   http:\/\/github.com\/xolox\/vim-notes\/commit\/eb8a83c\n\n \u00e2\u0080\u00a2 Support for nested list items with user defined bullets:\n   http:\/\/github.com\/xolox\/vim-notes\/commit\/576333a","package":"notes.zip","4":"notes.zip","src_id":"16962","5":"16962","creation_date":"1322238125","6":"1322238125"},{"0":"3375","vim_version":"7.0","1":"7.0","script_version":"0.15.3","2":"0.15.3","version_comment":" \u00e2\u0080\u00a2 Document that gf, C-w f, C-w gf all work inside notes:\n   http:\/\/github.com\/xolox\/vim-notes\/commit\/457f536\n\n \u00e2\u0080\u00a2 Improve :Note completion (sort candidates by length, ascending):\n   http:\/\/github.com\/xolox\/vim-notes\/commit\/4171a4f\n\n \u00e2\u0080\u00a2 Improve smart quotes (' <- that should become an opening quote:\n   http:\/\/github.com\/xolox\/vim-notes\/commit\/a2a2596\n\n \u00e2\u0080\u00a2 Respect word boundaries when highlighting note names (issue #14 on GitHub):\n   http:\/\/github.com\/xolox\/vim-notes\/commit\/6faa5d7","3":" \u00e2\u0080\u00a2 Document that gf, C-w f, C-w gf all work inside notes:\n   http:\/\/github.com\/xolox\/vim-notes\/commit\/457f536\n\n \u00e2\u0080\u00a2 Improve :Note completion (sort candidates by length, ascending):\n   http:\/\/github.com\/xolox\/vim-notes\/commit\/4171a4f\n\n \u00e2\u0080\u00a2 Improve smart quotes (' <- that should become an opening quote:\n   http:\/\/github.com\/xolox\/vim-notes\/commit\/a2a2596\n\n \u00e2\u0080\u00a2 Respect word boundaries when highlighting note names (issue #14 on GitHub):\n   http:\/\/github.com\/xolox\/vim-notes\/commit\/6faa5d7","package":"notes.zip","4":"notes.zip","src_id":"16961","5":"16961","creation_date":"1322185774","6":"1322185774"},{"0":"3375","vim_version":"7.0","1":"7.0","script_version":"0.15","2":"0.15","version_comment":" \u00e2\u0080\u00a2 Don't highlight the name of the current note:\n   http:\/\/github.com\/xolox\/vim-notes\/commit\/d49f215\n\n \u00e2\u0080\u00a2 Automatically trim leading\/trailing space from note titles:\n   http:\/\/github.com\/xolox\/vim-notes\/commit\/3a71679\n\n \u00e2\u0080\u00a2 Ignore tags that contain \"{\" (probably BibTeX entries):\n   http:\/\/github.com\/xolox\/vim-notes\/commit\/43f5a10\n\n \u00e2\u0080\u00a2 New command :SplitNoteFromSelectedText:\n   http:\/\/github.com\/xolox\/vim-notes\/commit\/cde86b4","3":" \u00e2\u0080\u00a2 Don't highlight the name of the current note:\n   http:\/\/github.com\/xolox\/vim-notes\/commit\/d49f215\n\n \u00e2\u0080\u00a2 Automatically trim leading\/trailing space from note titles:\n   http:\/\/github.com\/xolox\/vim-notes\/commit\/3a71679\n\n \u00e2\u0080\u00a2 Ignore tags that contain \"{\" (probably BibTeX entries):\n   http:\/\/github.com\/xolox\/vim-notes\/commit\/43f5a10\n\n \u00e2\u0080\u00a2 New command :SplitNoteFromSelectedText:\n   http:\/\/github.com\/xolox\/vim-notes\/commit\/cde86b4","package":"notes.zip","4":"notes.zip","src_id":"16960","5":"16960","creation_date":"1322183218","6":"1322183218"},{"0":"3375","vim_version":"7.0","1":"7.0","script_version":"0.14.3","2":"0.14.3","version_comment":" \u00e2\u0080\u00a2 Document :SearchNotes tab completion:\n   http:\/\/github.com\/xolox\/vim-notes\/commit\/6f925ab\n\n \u00e2\u0080\u00a2 search-notes.py: Support -v, --verbose option:\n   http:\/\/github.com\/xolox\/vim-notes\/commit\/f3bdec9\n\n \u00e2\u0080\u00a2 Fix Unicode encoding errors, don't index single characters:\n   http:\/\/github.com\/xolox\/vim-notes\/commit\/8a79a22\n\n \u00e2\u0080\u00a2 search-notes.py: Bug fix for \"RuntimeError: dictionary changed size during iteration\":\n   http:\/\/github.com\/xolox\/vim-notes\/commit\/10d6e24\n\n \u00e2\u0080\u00a2 search-notes.py: Also match substrings of keywords:\n   http:\/\/github.com\/xolox\/vim-notes\/commit\/679f785\n\n \u00e2\u0080\u00a2 search-notes.py: Give a friendly message when the keyword index is initialized:\n   http:\/\/github.com\/xolox\/vim-notes\/commit\/38056ee","3":" \u00e2\u0080\u00a2 Document :SearchNotes tab completion:\n   http:\/\/github.com\/xolox\/vim-notes\/commit\/6f925ab\n\n \u00e2\u0080\u00a2 search-notes.py: Support -v, --verbose option:\n   http:\/\/github.com\/xolox\/vim-notes\/commit\/f3bdec9\n\n \u00e2\u0080\u00a2 Fix Unicode encoding errors, don't index single characters:\n   http:\/\/github.com\/xolox\/vim-notes\/commit\/8a79a22\n\n \u00e2\u0080\u00a2 search-notes.py: Bug fix for \"RuntimeError: dictionary changed size during iteration\":\n   http:\/\/github.com\/xolox\/vim-notes\/commit\/10d6e24\n\n \u00e2\u0080\u00a2 search-notes.py: Also match substrings of keywords:\n   http:\/\/github.com\/xolox\/vim-notes\/commit\/679f785\n\n \u00e2\u0080\u00a2 search-notes.py: Give a friendly message when the keyword index is initialized:\n   http:\/\/github.com\/xolox\/vim-notes\/commit\/38056ee","package":"notes.zip","4":"notes.zip","src_id":"16957","5":"16957","creation_date":"1322168104","6":"1322168104"},{"0":"3375","vim_version":"7.0","1":"7.0","script_version":"0.14.2","2":"0.14.2","version_comment":" \u00e2\u0080\u00a2 Keyword completion for the :SearchNotes command:\n   http:\/\/github.com\/xolox\/vim-notes\/commit\/6993951\n\n \u00e2\u0080\u00a2 :SearchNotes completion now sorts by Levenshtein distance (sudo apt-get install python-levenshtein):\n   http:\/\/github.com\/xolox\/vim-notes\/commit\/6723f90","3":" \u00e2\u0080\u00a2 Keyword completion for the :SearchNotes command:\n   http:\/\/github.com\/xolox\/vim-notes\/commit\/6993951\n\n \u00e2\u0080\u00a2 :SearchNotes completion now sorts by Levenshtein distance (sudo apt-get install python-levenshtein):\n   http:\/\/github.com\/xolox\/vim-notes\/commit\/6723f90","package":"notes.zip","4":"notes.zip","src_id":"16946","5":"16946","creation_date":"1322004415","6":"1322004415"},{"0":"3375","vim_version":"7.0","1":"7.0","script_version":"0.14","2":"0.14","version_comment":" \u00e2\u0080\u00a2 Improved Python script to search notes (*much* faster now):\n   http:\/\/github.com\/xolox\/vim-notes\/commit\/7f86001","3":" \u00e2\u0080\u00a2 Improved Python script to search notes (*much* faster now):\n   http:\/\/github.com\/xolox\/vim-notes\/commit\/7f86001","package":"notes.zip","4":"notes.zip","src_id":"16945","5":"16945","creation_date":"1321998763","6":"1321998763"},{"0":"3375","vim_version":"7.0","1":"7.0","script_version":"0.12.12","2":"0.12.12","version_comment":" \u00e2\u0080\u00a2 Work around &shellslash setting on Windows:\n   http:\/\/github.com\/xolox\/vim-notes\/commit\/d5bdcf5","3":" \u00e2\u0080\u00a2 Work around &shellslash setting on Windows:\n   http:\/\/github.com\/xolox\/vim-notes\/commit\/d5bdcf5","package":"notes.zip","4":"notes.zip","src_id":"16924","5":"16924","creation_date":"1321910263","6":"1321910263"},{"0":"3375","vim_version":"7.0","1":"7.0","script_version":"0.12.11","2":"0.12.11","version_comment":" \u00e2\u0080\u00a2 Bug fix for saving notes with a bang (!):\n   http:\/\/github.com\/xolox\/vim-notes\/commit\/1ae2312\n   http:\/\/github.com\/xolox\/vim-notes\/commit\/62a96b1","3":" \u00e2\u0080\u00a2 Bug fix for saving notes with a bang (!):\n   http:\/\/github.com\/xolox\/vim-notes\/commit\/1ae2312\n   http:\/\/github.com\/xolox\/vim-notes\/commit\/62a96b1","package":"notes.zip","4":"notes.zip","src_id":"16899","5":"16899","creation_date":"1321626933","6":"1321626933"},{"0":"3375","vim_version":"7.0","1":"7.0","script_version":"0.12.10","2":"0.12.10","version_comment":" \u00e2\u0080\u00a2 Don't disable matching pair highlighting to stop constant visual bell:\n   http:\/\/github.com\/xolox\/vim-notes\/commit\/8c79330\n   http:\/\/github.com\/xolox\/vim-notes\/commit\/1de0527\n\n \u00e2\u0080\u00a2 New \"notes_smart_quotes\" option to disable automatic substitution:\n   http:\/\/github.com\/xolox\/vim-notes\/commit\/3327d21","3":" \u00e2\u0080\u00a2 Don't disable matching pair highlighting to stop constant visual bell:\n   http:\/\/github.com\/xolox\/vim-notes\/commit\/8c79330\n   http:\/\/github.com\/xolox\/vim-notes\/commit\/1de0527\n\n \u00e2\u0080\u00a2 New \"notes_smart_quotes\" option to disable automatic substitution:\n   http:\/\/github.com\/xolox\/vim-notes\/commit\/3327d21","package":"notes.zip","4":"notes.zip","src_id":"16872","5":"16872","creation_date":"1321383206","6":"1321383206"},{"0":"3375","vim_version":"7.0","1":"7.0","script_version":"0.12.8","2":"0.12.8","version_comment":" \u00e2\u0080\u00a2 Bug fix: Don't search shadow notes in scanner.py:\n   http:\/\/github.com\/xolox\/vim-notes\/commit\/bb627d5\n\n \u00e2\u0080\u00a2 Bug fix: Exclude Vim swap files with names of the form .*.s[^w]?:\n   http:\/\/github.com\/xolox\/vim-notes\/commit\/913807b\n\n \u00e2\u0080\u00a2 Bug fix: Highlight :SearchNotes matches case insensitively:\n   http:\/\/github.com\/xolox\/vim-notes\/commit\/8583afe\n\n \u00e2\u0080\u00a2 Remove notes_fold_ignore_code option, always enabled now!\n   http:\/\/github.com\/xolox\/vim-notes\/commit\/4a12f53\n\n \u00e2\u0080\u00a2 Move timer calls to top level functions, add some more:\n   http:\/\/github.com\/xolox\/vim-notes\/commit\/0d5505e\n\n \u00e2\u0080\u00a2 Show total number of notes in [Tagged Notes] buffer:\n   http:\/\/github.com\/xolox\/vim-notes\/commit\/4a7f4e8","3":" \u00e2\u0080\u00a2 Bug fix: Don't search shadow notes in scanner.py:\n   http:\/\/github.com\/xolox\/vim-notes\/commit\/bb627d5\n\n \u00e2\u0080\u00a2 Bug fix: Exclude Vim swap files with names of the form .*.s[^w]?:\n   http:\/\/github.com\/xolox\/vim-notes\/commit\/913807b\n\n \u00e2\u0080\u00a2 Bug fix: Highlight :SearchNotes matches case insensitively:\n   http:\/\/github.com\/xolox\/vim-notes\/commit\/8583afe\n\n \u00e2\u0080\u00a2 Remove notes_fold_ignore_code option, always enabled now!\n   http:\/\/github.com\/xolox\/vim-notes\/commit\/4a12f53\n\n \u00e2\u0080\u00a2 Move timer calls to top level functions, add some more:\n   http:\/\/github.com\/xolox\/vim-notes\/commit\/0d5505e\n\n \u00e2\u0080\u00a2 Show total number of notes in [Tagged Notes] buffer:\n   http:\/\/github.com\/xolox\/vim-notes\/commit\/4a7f4e8","package":"notes.zip","4":"notes.zip","src_id":"16797","5":"16797","creation_date":"1320357297","6":"1320357297"},{"0":"3375","vim_version":"7.0","1":"7.0","script_version":"0.12.2","2":"0.12.2","version_comment":" \u00e2\u0080\u00a2 Fold function finally knows to ignore embedded code (thanks to Bart Kroon for the motivation to finally fix this bloody annoying misfeature ;-)):\n   http:\/\/github.com\/xolox\/vim-notes\/commit\/9985806\n\n \u00e2\u0080\u00a2 Improved filename <-> title synchronization. Bug fix: Whenever creating a new note the plug-in would complain that the filename and title didn't match :-\/... Sorry about that, it was annoying for me as well :-). Anyway should be fixed now, let's hope I didn't break anything else in the process. As I was working on the feature anyway I also added more information to the dialog:\n   http:\/\/github.com\/xolox\/vim-notes\/commit\/273aa01","3":" \u00e2\u0080\u00a2 Fold function finally knows to ignore embedded code (thanks to Bart Kroon for the motivation to finally fix this bloody annoying misfeature ;-)):\n   http:\/\/github.com\/xolox\/vim-notes\/commit\/9985806\n\n \u00e2\u0080\u00a2 Improved filename <-> title synchronization. Bug fix: Whenever creating a new note the plug-in would complain that the filename and title didn't match :-\/... Sorry about that, it was annoying for me as well :-). Anyway should be fixed now, let's hope I didn't break anything else in the process. As I was working on the feature anyway I also added more information to the dialog:\n   http:\/\/github.com\/xolox\/vim-notes\/commit\/273aa01","package":"notes.zip","4":"notes.zip","src_id":"16730","5":"16730","creation_date":"1319406028","6":"1319406028"},{"0":"3375","vim_version":"7.0","1":"7.0","script_version":"0.12","2":"0.12","version_comment":" \u00e2\u0080\u00a2 Bug fix for \"E28: No such highlight group name: notesName\":\n   http:\/\/github.com\/xolox\/vim-notes\/commit\/f6ec550\n\n \u00e2\u0080\u00a2 Enable syncing of filenames <-> titles (suggested by Julien Lancien):\n   http:\/\/github.com\/xolox\/vim-notes\/commit\/2349000","3":" \u00e2\u0080\u00a2 Bug fix for \"E28: No such highlight group name: notesName\":\n   http:\/\/github.com\/xolox\/vim-notes\/commit\/f6ec550\n\n \u00e2\u0080\u00a2 Enable syncing of filenames <-> titles (suggested by Julien Lancien):\n   http:\/\/github.com\/xolox\/vim-notes\/commit\/2349000","package":"notes.zip","4":"notes.zip","src_id":"16700","5":"16700","creation_date":"1318974073","6":"1318974073"},{"0":"3375","vim_version":"7.0","1":"7.0","script_version":"0.11.5","2":"0.11.5","version_comment":" \u00e2\u0080\u00a2 :DeleteNote {title} support by github.com\/bioe007 (pull request #9):\n   http:\/\/github.com\/xolox\/vim-notes\/commit\/57b7168 (original change set)\n   http:\/\/github.com\/xolox\/vim-notes\/commit\/2f1229f (my modifications)","3":" \u00e2\u0080\u00a2 :DeleteNote {title} support by github.com\/bioe007 (pull request #9):\n   http:\/\/github.com\/xolox\/vim-notes\/commit\/57b7168 (original change set)\n   http:\/\/github.com\/xolox\/vim-notes\/commit\/2f1229f (my modifications)","package":"notes.zip","4":"notes.zip","src_id":"16587","5":"16587","creation_date":"1316998605","6":"1316998605"},{"0":"3375","vim_version":"7.0","1":"7.0","script_version":"0.11.4","2":"0.11.4","version_comment":" \u00e2\u0080\u00a2 TODO: Make F1 show quick reference, add optional command aliases:\n   http:\/\/github.com\/xolox\/vim-notes\/commit\/2421490\n\n \u00e2\u0080\u00a2 Updated miscellaneous scripts:\n   http:\/\/github.com\/xolox\/vim-notes\/commit\/b9d03be","3":" \u00e2\u0080\u00a2 TODO: Make F1 show quick reference, add optional command aliases:\n   http:\/\/github.com\/xolox\/vim-notes\/commit\/2421490\n\n \u00e2\u0080\u00a2 Updated miscellaneous scripts:\n   http:\/\/github.com\/xolox\/vim-notes\/commit\/b9d03be","package":"notes.zip","4":"notes.zip","src_id":"16585","5":"16585","creation_date":"1316995874","6":"1316995874"},{"0":"3375","vim_version":"7.0","1":"7.0","script_version":"0.11.3","2":"0.11.3","version_comment":" \u00e2\u0080\u00a2 Include untagged notes in :ShowTaggedNotes output (suggested by Jacobo de Vera):\n   http:\/\/github.com\/xolox\/vim-notes\/commit\/60526a3","3":" \u00e2\u0080\u00a2 Include untagged notes in :ShowTaggedNotes output (suggested by Jacobo de Vera):\n   http:\/\/github.com\/xolox\/vim-notes\/commit\/60526a3","package":"notes.zip","4":"notes.zip","src_id":"16545","5":"16545","creation_date":"1316299589","6":"1316299589"},{"0":"3375","vim_version":"7.0","1":"7.0","script_version":"0.11.2","2":"0.11.2","version_comment":" \u00e2\u0080\u00a2 Bug fix: Guard against recursive calls to tags#load_index() (issue #8):\n   http:\/\/github.com\/xolox\/vim-notes\/commit\/b38f0ee\n\n \u00e2\u0080\u00a2 Minor bug fix: Always save tags index when file doesn't exist:\n   http:\/\/github.com\/xolox\/vim-notes\/commit\/1021528","3":" \u00e2\u0080\u00a2 Bug fix: Guard against recursive calls to tags#load_index() (issue #8):\n   http:\/\/github.com\/xolox\/vim-notes\/commit\/b38f0ee\n\n \u00e2\u0080\u00a2 Minor bug fix: Always save tags index when file doesn't exist:\n   http:\/\/github.com\/xolox\/vim-notes\/commit\/1021528","package":"notes.zip","4":"notes.zip","src_id":"16539","5":"16539","creation_date":"1316286709","6":"1316286709"},{"0":"3375","vim_version":"7.0","1":"7.0","script_version":"0.11","2":"0.11","version_comment":" \u00e2\u0080\u00a2 README updates:\n   http:\/\/github.com\/xolox\/vim-notes\/commit\/16093e8\n\n \u00e2\u0080\u00a2 Properly use Unicode bullets in generated \"All tags\" note:\n   http:\/\/github.com\/xolox\/vim-notes\/commit\/1b928a1\n\n \u00e2\u0080\u00a2 Automatically remove empty list items on Enter:\n   http:\/\/github.com\/xolox\/vim-notes\/commit\/b5f4f6e\n\n \u00e2\u0080\u00a2 Hide shadow notes from list of tagged notes:\n   http:\/\/github.com\/xolox\/vim-notes\/commit\/de1b170\n\n \u00e2\u0080\u00a2 Bug fix for <CR> mapping: Allow splitting lines in the middle:\n   http:\/\/github.com\/xolox\/vim-notes\/commit\/cbc894e\n\n \u00e2\u0080\u00a2 Bug fix: Restore highlighting of note names that end in punctuation:\n   http:\/\/github.com\/xolox\/vim-notes\/commit\/56e23b6\n\n \u00e2\u0080\u00a2 Move version variable to autoload script:\n   http:\/\/github.com\/xolox\/vim-notes\/commit\/80b6ef5\n\n \u00e2\u0080\u00a2 Incremental tags index, improved :ShowTaggedNotes command:\n   http:\/\/github.com\/xolox\/vim-notes\/commit\/528fdcb","3":" \u00e2\u0080\u00a2 README updates:\n   http:\/\/github.com\/xolox\/vim-notes\/commit\/16093e8\n\n \u00e2\u0080\u00a2 Properly use Unicode bullets in generated \"All tags\" note:\n   http:\/\/github.com\/xolox\/vim-notes\/commit\/1b928a1\n\n \u00e2\u0080\u00a2 Automatically remove empty list items on Enter:\n   http:\/\/github.com\/xolox\/vim-notes\/commit\/b5f4f6e\n\n \u00e2\u0080\u00a2 Hide shadow notes from list of tagged notes:\n   http:\/\/github.com\/xolox\/vim-notes\/commit\/de1b170\n\n \u00e2\u0080\u00a2 Bug fix for <CR> mapping: Allow splitting lines in the middle:\n   http:\/\/github.com\/xolox\/vim-notes\/commit\/cbc894e\n\n \u00e2\u0080\u00a2 Bug fix: Restore highlighting of note names that end in punctuation:\n   http:\/\/github.com\/xolox\/vim-notes\/commit\/56e23b6\n\n \u00e2\u0080\u00a2 Move version variable to autoload script:\n   http:\/\/github.com\/xolox\/vim-notes\/commit\/80b6ef5\n\n \u00e2\u0080\u00a2 Incremental tags index, improved :ShowTaggedNotes command:\n   http:\/\/github.com\/xolox\/vim-notes\/commit\/528fdcb","package":"notes.zip","4":"notes.zip","src_id":"16454","5":"16454","creation_date":"1315142074","6":"1315142074"},{"0":"3375","vim_version":"7.0","1":"7.0","script_version":"0.10","2":"0.10","version_comment":" \u00e2\u0080\u00a2 Don't hang on hit-enter prompt (:SearchNotes):\n   http:\/\/github.com\/xolox\/vim-notes\/commit\/215fd1c\n\n \u00e2\u0080\u00a2 Automatic completion of @tags inside notes (suggested by Lukas Muehlethaler):\n   http:\/\/github.com\/xolox\/vim-notes\/commit\/74e8455","3":" \u00e2\u0080\u00a2 Don't hang on hit-enter prompt (:SearchNotes):\n   http:\/\/github.com\/xolox\/vim-notes\/commit\/215fd1c\n\n \u00e2\u0080\u00a2 Automatic completion of @tags inside notes (suggested by Lukas Muehlethaler):\n   http:\/\/github.com\/xolox\/vim-notes\/commit\/74e8455","package":"notes.zip","4":"notes.zip","src_id":"16060","5":"16060","creation_date":"1310217884","6":"1310217884"},{"0":"3375","vim_version":"7.0","1":"7.0","script_version":"0.9.4","2":"0.9.4","version_comment":" \u00e2\u0080\u00a2 Define version as variable, include version in messages:\n   http:\/\/github.com\/xolox\/vim-notes\/commit\/23861b0\n\n \u00e2\u0080\u00a2 Make highlighting UTF-8 compatible (suggested by Lukas Muehlethaler):\n   http:\/\/github.com\/xolox\/vim-notes\/commit\/5d6dfdb","3":" \u00e2\u0080\u00a2 Define version as variable, include version in messages:\n   http:\/\/github.com\/xolox\/vim-notes\/commit\/23861b0\n\n \u00e2\u0080\u00a2 Make highlighting UTF-8 compatible (suggested by Lukas Muehlethaler):\n   http:\/\/github.com\/xolox\/vim-notes\/commit\/5d6dfdb","package":"notes.zip","4":"notes.zip","src_id":"15968","5":"15968","creation_date":"1308911838","6":"1308911838"},{"0":"3375","vim_version":"7.0","1":"7.0","script_version":"0.9.2","2":"0.9.2","version_comment":" \u00e2\u0080\u00a2 Make :SearchNotes support | without escaping (reported by Avi Yagodnick):\n   http:\/\/github.com\/xolox\/vim-notes\/commit\/6468ae9","3":" \u00e2\u0080\u00a2 Make :SearchNotes support | without escaping (reported by Avi Yagodnick):\n   http:\/\/github.com\/xolox\/vim-notes\/commit\/6468ae9","package":"notes.zip","4":"notes.zip","src_id":"15915","5":"15915","creation_date":"1308320688","6":"1308320688"},{"0":"3375","vim_version":"7.0","1":"7.0","script_version":"0.9.1","2":"0.9.1","version_comment":" \u00e2\u0080\u00a2 Finally a proper readme! (used to generate homepage and Vim help file):\n   http:\/\/github.com\/xolox\/vim-notes\/commit\/d532ede\n\n \u00e2\u0080\u00a2 Optionally append suffix to note filenames (thanks to Christopher Peplin):\n   http:\/\/github.com\/xolox\/vim-notes\/commit\/96a16ed","3":" \u00e2\u0080\u00a2 Finally a proper readme! (used to generate homepage and Vim help file):\n   http:\/\/github.com\/xolox\/vim-notes\/commit\/d532ede\n\n \u00e2\u0080\u00a2 Optionally append suffix to note filenames (thanks to Christopher Peplin):\n   http:\/\/github.com\/xolox\/vim-notes\/commit\/96a16ed","package":"notes.zip","4":"notes.zip","src_id":"15877","5":"15877","creation_date":"1308010197","6":"1308010197"},{"0":"3375","vim_version":"7.0","1":"7.0","script_version":"0.8.12","2":"0.8.12","version_comment":" \u00e2\u0080\u00a2 Add :NoteFromSelectedText command (suggested by Lukas Muehlethaler):\n   http:\/\/github.com\/xolox\/vim-notes\/commit\/26ab4f4\n\n \u00e2\u0080\u00a2 Insert mode completion of note titles using C-x C-u (suggested by Lukas Muehlethaler):\n   http:\/\/github.com\/xolox\/vim-notes\/commit\/6143437\n\n \u00e2\u0080\u00a2 Sanity check automatic renaming of notes:\n   http:\/\/github.com\/xolox\/vim-notes\/commit\/a7a3d26\n\n \u00e2\u0080\u00a2 :RecentNotes command to list (matching) notes by modification date:\n   http:\/\/github.com\/xolox\/vim-notes\/commit\/57d1c61","3":" \u00e2\u0080\u00a2 Add :NoteFromSelectedText command (suggested by Lukas Muehlethaler):\n   http:\/\/github.com\/xolox\/vim-notes\/commit\/26ab4f4\n\n \u00e2\u0080\u00a2 Insert mode completion of note titles using C-x C-u (suggested by Lukas Muehlethaler):\n   http:\/\/github.com\/xolox\/vim-notes\/commit\/6143437\n\n \u00e2\u0080\u00a2 Sanity check automatic renaming of notes:\n   http:\/\/github.com\/xolox\/vim-notes\/commit\/a7a3d26\n\n \u00e2\u0080\u00a2 :RecentNotes command to list (matching) notes by modification date:\n   http:\/\/github.com\/xolox\/vim-notes\/commit\/57d1c61","package":"notes.zip","4":"notes.zip","src_id":"15862","5":"15862","creation_date":"1307914271","6":"1307914271"},{"0":"3375","vim_version":"7.0","1":"7.0","script_version":"0.8.8","2":"0.8.8","version_comment":" \u00e2\u0080\u00a2 Improve documentation notes (thanks to Laurent & SteP):\r\n   http:\/\/github.com\/xolox\/vim-notes\/commit\/7a9e923\r\n\r\n \u00e2\u0080\u00a2 Basic support for @tags (suggested by Jonathan Reeve):\r\n   http:\/\/github.com\/xolox\/vim-notes\/commit\/677cd70","3":" \u00e2\u0080\u00a2 Improve documentation notes (thanks to Laurent & SteP):\r\n   http:\/\/github.com\/xolox\/vim-notes\/commit\/7a9e923\r\n\r\n \u00e2\u0080\u00a2 Basic support for @tags (suggested by Jonathan Reeve):\r\n   http:\/\/github.com\/xolox\/vim-notes\/commit\/677cd70","package":"notes.zip","4":"notes.zip","src_id":"15806","5":"15806","creation_date":"1307145820","6":"1307145820"},{"0":"3375","vim_version":"7.0","1":"7.0","script_version":"0.8.7","2":"0.8.7","version_comment":" \u00e2\u0080\u00a2 Call the correct Python interpreter on Python 3 systems:\r\n   https:\/\/github.com\/xolox\/vim-notes\/commit\/a721bc2\r\n\r\n \u00e2\u0080\u00a2 Bug fix: Make <Tab> work on empty lines (reported by Ulrik Sverdrup):\r\n   https:\/\/github.com\/xolox\/vim-notes\/commit\/c4f231e\r\n\r\n \u00e2\u0080\u00a2 Bug fix for completion after typing several words (reported by Ulrik Sverdrup):\r\n   https:\/\/github.com\/xolox\/vim-notes\/commit\/d5a11a8\r\n\r\n \u00e2\u0080\u00a2 Bug fix: Windows compatibility for automatic command patterns:\r\n   https:\/\/github.com\/xolox\/vim-notes\/commit\/28514cb\r\n\r\n \u00e2\u0080\u00a2 Support for non-Unicode encodings (requested by SteP):\r\n   https:\/\/github.com\/xolox\/vim-notes\/commit\/6b7566e","3":" \u00e2\u0080\u00a2 Call the correct Python interpreter on Python 3 systems:\r\n   https:\/\/github.com\/xolox\/vim-notes\/commit\/a721bc2\r\n\r\n \u00e2\u0080\u00a2 Bug fix: Make <Tab> work on empty lines (reported by Ulrik Sverdrup):\r\n   https:\/\/github.com\/xolox\/vim-notes\/commit\/c4f231e\r\n\r\n \u00e2\u0080\u00a2 Bug fix for completion after typing several words (reported by Ulrik Sverdrup):\r\n   https:\/\/github.com\/xolox\/vim-notes\/commit\/d5a11a8\r\n\r\n \u00e2\u0080\u00a2 Bug fix: Windows compatibility for automatic command patterns:\r\n   https:\/\/github.com\/xolox\/vim-notes\/commit\/28514cb\r\n\r\n \u00e2\u0080\u00a2 Support for non-Unicode encodings (requested by SteP):\r\n   https:\/\/github.com\/xolox\/vim-notes\/commit\/6b7566e","package":"notes.zip","4":"notes.zip","src_id":"15698","5":"15698","creation_date":"1306095258","6":"1306095258"},{"0":"3375","vim_version":"7.0","1":"7.0","script_version":"0.8.2","2":"0.8.2","version_comment":" \u00e2\u0080\u00a2 Enable naming new notes with :NewNote arguments:\r\n   https:\/\/github.com\/xolox\/vim-notes\/commit\/94e10b3bbdc2b609bcbf\r\n\r\n \u00e2\u0080\u00a2 Rename :NewNote to :Note, make it edit existing notes:\r\n   https:\/\/github.com\/xolox\/vim-notes\/commit\/8274b26e48212cb75577\r\n\r\n \u00e2\u0080\u00a2 Simplify automatic renaming (now more reliable):\r\n   https:\/\/github.com\/xolox\/vim-notes\/commit\/9d0a9dd7f9746525c875\r\n\r\n \u00e2\u0080\u00a2 Completion for :Note command:\r\n   https:\/\/github.com\/xolox\/vim-notes\/commit\/21c8699880876d3f584f","3":" \u00e2\u0080\u00a2 Enable naming new notes with :NewNote arguments:\r\n   https:\/\/github.com\/xolox\/vim-notes\/commit\/94e10b3bbdc2b609bcbf\r\n\r\n \u00e2\u0080\u00a2 Rename :NewNote to :Note, make it edit existing notes:\r\n   https:\/\/github.com\/xolox\/vim-notes\/commit\/8274b26e48212cb75577\r\n\r\n \u00e2\u0080\u00a2 Simplify automatic renaming (now more reliable):\r\n   https:\/\/github.com\/xolox\/vim-notes\/commit\/9d0a9dd7f9746525c875\r\n\r\n \u00e2\u0080\u00a2 Completion for :Note command:\r\n   https:\/\/github.com\/xolox\/vim-notes\/commit\/21c8699880876d3f584f","package":"notes.zip","4":"notes.zip","src_id":"14703","5":"14703","creation_date":"1294438367","6":"1294438367"},{"0":"3375","vim_version":"7.0","1":"7.0","script_version":"0.7.20","2":"0.7.20","version_comment":" \u00e2\u0080\u00a2 Compatibility with Pathogen by using relative paths:\r\n   https:\/\/github.com\/xolox\/vim-notes\/commit\/9aa85d093a4515930ac4\r\n\r\n \u00e2\u0080\u00a2 Bug fix for URL highlighting (trailing punctuation):\r\n   https:\/\/github.com\/xolox\/vim-notes\/commit\/79eea085d726ba9f9864\r\n\r\n \u00e2\u0080\u00a2 Bug fix: Always keep cached note names up to date:\r\n   https:\/\/github.com\/xolox\/vim-notes\/commit\/9a044fbd479f87c1e864\r\n\r\n \u00e2\u0080\u00a2 Dynamically update note name highlighting:\r\n   https:\/\/github.com\/xolox\/vim-notes\/commit\/a30b997ea2ad7042abd0\r\n\r\n \u00e2\u0080\u00a2 Only update note name highlighting when necessary:\r\n   https:\/\/github.com\/xolox\/vim-notes\/commit\/46e29787ed9f4ee749d6\r\n\r\n \u00e2\u0080\u00a2 Forget about notes that are never saved:\r\n   https:\/\/github.com\/xolox\/vim-notes\/commit\/2a1a704c81520d45f64b\r\n\r\n \u00e2\u0080\u00a2 Bug fix: Restore highlighting of URL schemes:\r\n   https:\/\/github.com\/xolox\/vim-notes\/commit\/e8d694bd292cf0385797\r\n\r\n \u00e2\u0080\u00a2 Bug fix: Restore note name highlighting after reload:\r\n   https:\/\/github.com\/xolox\/vim-notes\/commit\/e47ca92357efd98150f6\r\n\r\n \u00e2\u0080\u00a2 Bug fix: Update note name highlighting when reloading syntax:\r\n   https:\/\/github.com\/xolox\/vim-notes\/commit\/3e4ec8fe4b2f68cdedc7\r\n\r\n \u00e2\u0080\u00a2 Change remaining \":hi link\" commands to \":hi def link\":\r\n   https:\/\/github.com\/xolox\/vim-notes\/commit\/507aaac7960cfe958c6d\r\n\r\n \u00e2\u0080\u00a2 Highlighting for line numbers in filenames:\r\n   https:\/\/github.com\/xolox\/vim-notes\/commit\/7a476d8e29cc023424a8\r\n\r\n \u00e2\u0080\u00a2 Highlighting for FIXME markers:\r\n   https:\/\/github.com\/xolox\/vim-notes\/commit\/3e4f5a34f0cfb880b397\r\n\r\n \u00e2\u0080\u00a2 Remove BufWritePost automatic commands:\r\n   https:\/\/github.com\/xolox\/vim-notes\/commit\/16f46000a0caf430a88d","3":" \u00e2\u0080\u00a2 Compatibility with Pathogen by using relative paths:\r\n   https:\/\/github.com\/xolox\/vim-notes\/commit\/9aa85d093a4515930ac4\r\n\r\n \u00e2\u0080\u00a2 Bug fix for URL highlighting (trailing punctuation):\r\n   https:\/\/github.com\/xolox\/vim-notes\/commit\/79eea085d726ba9f9864\r\n\r\n \u00e2\u0080\u00a2 Bug fix: Always keep cached note names up to date:\r\n   https:\/\/github.com\/xolox\/vim-notes\/commit\/9a044fbd479f87c1e864\r\n\r\n \u00e2\u0080\u00a2 Dynamically update note name highlighting:\r\n   https:\/\/github.com\/xolox\/vim-notes\/commit\/a30b997ea2ad7042abd0\r\n\r\n \u00e2\u0080\u00a2 Only update note name highlighting when necessary:\r\n   https:\/\/github.com\/xolox\/vim-notes\/commit\/46e29787ed9f4ee749d6\r\n\r\n \u00e2\u0080\u00a2 Forget about notes that are never saved:\r\n   https:\/\/github.com\/xolox\/vim-notes\/commit\/2a1a704c81520d45f64b\r\n\r\n \u00e2\u0080\u00a2 Bug fix: Restore highlighting of URL schemes:\r\n   https:\/\/github.com\/xolox\/vim-notes\/commit\/e8d694bd292cf0385797\r\n\r\n \u00e2\u0080\u00a2 Bug fix: Restore note name highlighting after reload:\r\n   https:\/\/github.com\/xolox\/vim-notes\/commit\/e47ca92357efd98150f6\r\n\r\n \u00e2\u0080\u00a2 Bug fix: Update note name highlighting when reloading syntax:\r\n   https:\/\/github.com\/xolox\/vim-notes\/commit\/3e4ec8fe4b2f68cdedc7\r\n\r\n \u00e2\u0080\u00a2 Change remaining \":hi link\" commands to \":hi def link\":\r\n   https:\/\/github.com\/xolox\/vim-notes\/commit\/507aaac7960cfe958c6d\r\n\r\n \u00e2\u0080\u00a2 Highlighting for line numbers in filenames:\r\n   https:\/\/github.com\/xolox\/vim-notes\/commit\/7a476d8e29cc023424a8\r\n\r\n \u00e2\u0080\u00a2 Highlighting for FIXME markers:\r\n   https:\/\/github.com\/xolox\/vim-notes\/commit\/3e4f5a34f0cfb880b397\r\n\r\n \u00e2\u0080\u00a2 Remove BufWritePost automatic commands:\r\n   https:\/\/github.com\/xolox\/vim-notes\/commit\/16f46000a0caf430a88d","package":"notes.zip","4":"notes.zip","src_id":"14701","5":"14701","creation_date":"1294422139","6":"1294422139"},{"0":"3375","vim_version":"7.0","1":"7.0","script_version":"0.7.7","2":"0.7.7","version_comment":" \u00e2\u0080\u00a2 Document the `:edit note:' shortcut:\r\n   https:\/\/github.com\/xolox\/vim-notes\/commit\/bd9b7920bfb9f3e1e0bf\r\n\r\n \u00e2\u0080\u00a2 Automatically rename notes when their title is changed:\r\n   https:\/\/github.com\/xolox\/vim-notes\/commit\/26741868c3b576afdeb7","3":" \u00e2\u0080\u00a2 Document the `:edit note:' shortcut:\r\n   https:\/\/github.com\/xolox\/vim-notes\/commit\/bd9b7920bfb9f3e1e0bf\r\n\r\n \u00e2\u0080\u00a2 Automatically rename notes when their title is changed:\r\n   https:\/\/github.com\/xolox\/vim-notes\/commit\/26741868c3b576afdeb7","package":"notes.zip","4":"notes.zip","src_id":"14604","5":"14604","creation_date":"1293064576","6":"1293064576"},{"0":"3375","vim_version":"7.0","1":"7.0","script_version":"0.7.6","2":"0.7.6","version_comment":" \u00e2\u0080\u00a2 Download & Vim scripts links in README, support automatic updates with GLVS:\r\n   https:\/\/github.com\/xolox\/vim-notes\/commit\/c16227bbf3855c27344e\r\n\r\n \u00e2\u0080\u00a2 Ignore punctuation after URLs:\r\n   https:\/\/github.com\/xolox\/vim-notes\/commit\/72ea4edd8f9c3cf8fe40\r\n\r\n \u00e2\u0080\u00a2 Bug fix for italic highlighting:\r\n   https:\/\/github.com\/xolox\/vim-notes\/commit\/e5e60d755a48acb3bce8","3":" \u00e2\u0080\u00a2 Download & Vim scripts links in README, support automatic updates with GLVS:\r\n   https:\/\/github.com\/xolox\/vim-notes\/commit\/c16227bbf3855c27344e\r\n\r\n \u00e2\u0080\u00a2 Ignore punctuation after URLs:\r\n   https:\/\/github.com\/xolox\/vim-notes\/commit\/72ea4edd8f9c3cf8fe40\r\n\r\n \u00e2\u0080\u00a2 Bug fix for italic highlighting:\r\n   https:\/\/github.com\/xolox\/vim-notes\/commit\/e5e60d755a48acb3bce8","package":"notes.zip","4":"notes.zip","src_id":"14601","5":"14601","creation_date":"1292985654","6":"1292985654"},{"0":"3375","vim_version":"7.0","1":"7.0","script_version":"0.7.4","2":"0.7.4","version_comment":"Initial upload","3":"Initial upload","package":"notes.zip","4":"notes.zip","src_id":"14600","5":"14600","creation_date":"1292982028","6":"1292982028"}]},"3374":{"script_id":"3374","0":"3374","script_name":"ColorSelect","1":"ColorSelect","script_type":"utility","2":"utility","summary":"Plugin to select color with gtk interface","3":"Plugin to select color with gtk interface","description":"Plugin to help write hexadecimals colors.\r\n\r\nThis opens a gtk color dialog, when select a color this is writed on document.\r\n\r\nCommand to call\r\n  ColorSelect\r\n\r\nTo add a shortcut\r\n\"ColorSelect\r\nimap <F5> <esc>:ColorSelect<CR>\r\n\r\nDefault in downcase, to uppercase put on ~\/.vimrc:\r\ng:CaseResultColorSelect='upcase'","4":"Plugin to help write hexadecimals colors.\r\n\r\nThis opens a gtk color dialog, when select a color this is writed on document.\r\n\r\nCommand to call\r\n  ColorSelect\r\n\r\nTo add a shortcut\r\n\"ColorSelect\r\nimap <F5> <esc>:ColorSelect<CR>\r\n\r\nDefault in downcase, to uppercase put on ~\/.vimrc:\r\ng:CaseResultColorSelect='upcase'","install_details":"This dependes of:\r\n\r\nVim 7.x\r\nRuby\r\nRuby-Gtk(to install see this: http:\/\/dannnylo.wordpress.com\/2010\/07\/08\/instalando-gtk-no-rvm\/","5":"This dependes of:\r\n\r\nVim 7.x\r\nRuby\r\nRuby-Gtk(to install see this: http:\/\/dannnylo.wordpress.com\/2010\/07\/08\/instalando-gtk-no-rvm\/","first_name":"Kassio","6":"Kassio","last_name":"Borges","7":"Borges","releases":[{"0":"3374","vim_version":"7.0","1":"7.0","script_version":"0.5","2":"0.5","version_comment":"Adding setups to use rgba, just set g:FormatResultColorSelect='rgba'","3":"Adding setups to use rgba, just set g:FormatResultColorSelect='rgba'","package":"ColorSelect.zip","4":"ColorSelect.zip","src_id":"15042","5":"15042","creation_date":"1298082803","6":"1298082803"},{"0":"3374","vim_version":"7.0","1":"7.0","script_version":"0.4","2":"0.4","version_comment":"Fixing hexadecimal round","3":"Fixing hexadecimal round","package":"ColorSelect.tar.gz","4":"ColorSelect.tar.gz","src_id":"14790","5":"14790","creation_date":"1295456422","6":"1295456422"},{"0":"3374","vim_version":"7.0","1":"7.0","script_version":"0.3.1","2":"0.3.1","version_comment":"fixing vim code.","3":"fixing vim code.","package":"ColorSelect.tar.gz","4":"ColorSelect.tar.gz","src_id":"14603","5":"14603","creation_date":"1293035078","6":"1293035078"},{"0":"3374","vim_version":"7.0","1":"7.0","script_version":"0.3","2":"0.3","version_comment":"Making it work with Pathogen(By Sergey Gavrik)","3":"Making it work with Pathogen(By Sergey Gavrik)","package":"ColorSelect.tar.gz","4":"ColorSelect.tar.gz","src_id":"14602","5":"14602","creation_date":"1293015075","6":"1293015075"},{"0":"3374","vim_version":"7.0","1":"7.0","script_version":"0.2.1","2":"0.2.1","version_comment":"Fixing a bug on ruby.","3":"Fixing a bug on ruby.","package":"ColorSelect.tar.gz","4":"ColorSelect.tar.gz","src_id":"14598","5":"14598","creation_date":"1292965954","6":"1292965954"},{"0":"3374","vim_version":"7.0","1":"7.0","script_version":"0.2","2":"0.2","version_comment":"Add variable g:CaseResultColorSelect when this is 'upcase' print color in upcase.","3":"Add variable g:CaseResultColorSelect when this is 'upcase' print color in upcase.","package":"ColorSelect.tar.gz","4":"ColorSelect.tar.gz","src_id":"14597","5":"14597","creation_date":"1292959817","6":"1292959817"},{"0":"3374","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"ColorSelect.tar.gz","4":"ColorSelect.tar.gz","src_id":"14589","5":"14589","creation_date":"1292866122","6":"1292866122"}]},"3373":{"script_id":"3373","0":"3373","script_name":"blockle.vim","1":"blockle.vim","script_type":"utility","2":"utility","summary":"Toggle ruby block styles","3":"Toggle ruby block styles","description":"This plugin allows rapid toggling between the two different styles of ruby\r\nblocks, namely do\/end and brackets {}. To use, simply move the cursor to the\r\nbeginning or end of a block, and type <Leader>b. As a mnemonic, remember 'b'\r\nfor 'block'.\r\n\r\nNote: You must have your cursor on the do, end, {, or } for the plugin to work\r\ncorrectly.\r\n\r\nWhen moving from a do\/end to a bracket-style block, the plugin with attempt to\r\nmove to a one-liner if appropriate:\r\n\r\nFor example, if have the following ruby code:\r\n\r\n  ['one', 'two'].each do |number|\r\n    puts number + \"!\"\r\n  end\r\n\r\nAfter invoking <Leader>b, the resulting code would be:\r\n\r\n  ['one', 'two'].each { |number| puts number + \"!\" }\r\n\r\n","4":"This plugin allows rapid toggling between the two different styles of ruby\r\nblocks, namely do\/end and brackets {}. To use, simply move the cursor to the\r\nbeginning or end of a block, and type <Leader>b. As a mnemonic, remember 'b'\r\nfor 'block'.\r\n\r\nNote: You must have your cursor on the do, end, {, or } for the plugin to work\r\ncorrectly.\r\n\r\nWhen moving from a do\/end to a bracket-style block, the plugin with attempt to\r\nmove to a one-liner if appropriate:\r\n\r\nFor example, if have the following ruby code:\r\n\r\n  ['one', 'two'].each do |number|\r\n    puts number + \"!\"\r\n  end\r\n\r\nAfter invoking <Leader>b, the resulting code would be:\r\n\r\n  ['one', 'two'].each { |number| puts number + \"!\" }\r\n\r\n","install_details":"Extract to ~\/.vim, or ~\\vimfiles (Windows)","5":"Extract to ~\/.vim, or ~\\vimfiles (Windows)","first_name":"Joshua","6":"Joshua","last_name":"Davey","7":"Davey","releases":[{"0":"3373","vim_version":"7.2","1":"7.2","script_version":"0.5","2":"0.5","version_comment":"Add ability to change default mapping","3":"Add ability to change default mapping","package":"blockle.tar.gz","4":"blockle.tar.gz","src_id":"15538","5":"15538","creation_date":"1303932870","6":"1303932870"},{"0":"3373","vim_version":"7.2","1":"7.2","script_version":"0.4","2":"0.4","version_comment":"Bugfixes: save clipboard settings and content, preserve anonymous register","3":"Bugfixes: save clipboard settings and content, preserve anonymous register","package":"blockle.tar.gz","4":"blockle.tar.gz","src_id":"14827","5":"14827","creation_date":"1295724577","6":"1295724577"},{"0":"3373","vim_version":"7.2","1":"7.2","script_version":"0.3","2":"0.3","version_comment":"Better detection when inside of a block","3":"Better detection when inside of a block","package":"blockle.tar.gz","4":"blockle.tar.gz","src_id":"14595","5":"14595","creation_date":"1292909837","6":"1292909837"},{"0":"3373","vim_version":"7.2","1":"7.2","script_version":"0.2","2":"0.2","version_comment":"Lots of bugfixes. Better support for nested inline blocks.","3":"Lots of bugfixes. Better support for nested inline blocks.","package":"blockle.tar.gz","4":"blockle.tar.gz","src_id":"14580","5":"14580","creation_date":"1292821130","6":"1292821130"},{"0":"3373","vim_version":"7.2","1":"7.2","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"blockle.tar.gz","4":"blockle.tar.gz","src_id":"14559","5":"14559","creation_date":"1292686988","6":"1292686988"}]},"3371":{"script_id":"3371","0":"3371","script_name":"hdl_plugin","1":"hdl_plugin","script_type":"ftplugin","2":"ftplugin","summary":"Vhdl\/Verilog fast instant and generate testbench file.","3":"Vhdl\/Verilog fast instant and generate testbench file.","description":"I will updata this plugin in this page:\r\nhttp:\/\/www.vim.org\/scripts\/script.php?script_id=3420","4":"I will updata this plugin in this page:\r\nhttp:\/\/www.vim.org\/scripts\/script.php?script_id=3420","install_details":"","5":"","first_name":"\u9648","6":"陈","last_name":"\u52c7","7":"勇","releases":[{"0":"3371","vim_version":"7.0","1":"7.0","script_version":"v2.1","2":"v2.1","version_comment":"Supports \"inout\" port \r\nCan be used for verilog file","3":"Supports \"inout\" port \r\nCan be used for verilog file","package":"hdl_plugin.vim","4":"hdl_plugin.vim","src_id":"14648","5":"14648","creation_date":"1293610369","6":"1293610369"}]},"3370":{"script_id":"3370","0":"3370","script_name":"eteSkeleton","1":"eteSkeleton","script_type":"utility","2":"utility","summary":"Yet another skeleton utility","3":"Yet another skeleton utility","description":"A simple plugins that would help to manage skeletons(templates) for automate the creation of new files and insert tags (user definable) like user , date, askversion and so on.\r\n\r\nIt let you to use different skeletons for the same filetype, depending on the filename.\r\n\r\nPlease refer to https:\/\/github.com\/ellethee\/eteSkeleton for more details.","4":"A simple plugins that would help to manage skeletons(templates) for automate the creation of new files and insert tags (user definable) like user , date, askversion and so on.\r\n\r\nIt let you to use different skeletons for the same filetype, depending on the filename.\r\n\r\nPlease refer to https:\/\/github.com\/ellethee\/eteSkeleton for more details.","install_details":"If you don't have a preferred installation method, one option is to install pathogen.vim, and then copy and paste:\r\n\r\ncd ~\/.vim\/bundle\r\ngit clone https:\/\/github.com\/ellethee\/eteSkeleton.git\r\nvim -u NONE -c \"helptags eteSkeleton\/doc\" -c q\r\n\r\nOr using Vundle.vim adding to your .vimrc the line\r\n\r\nPlugin \"ellethee\/eteSkeleton\"\r\n","5":"If you don't have a preferred installation method, one option is to install pathogen.vim, and then copy and paste:\r\n\r\ncd ~\/.vim\/bundle\r\ngit clone https:\/\/github.com\/ellethee\/eteSkeleton.git\r\nvim -u NONE -c \"helptags eteSkeleton\/doc\" -c q\r\n\r\nOr using Vundle.vim adding to your .vimrc the line\r\n\r\nPlugin \"ellethee\/eteSkeleton\"\r\n","first_name":"ellethee","6":"ellethee","last_name":".","7":".","releases":[{"0":"3370","vim_version":"7.0","1":"7.0","script_version":"1.0.3","2":"1.0.3","version_comment":"* Added enhancements from Chris MacLeod's fork (https:\/\/github.com\/stick\/eteSkeleton).\r\n* Added localization.\r\n* Changed the TAG's brackets from <> to {}\r\n* Added some builtin TAG.\r\n\r\nPlease refer to https:\/\/github.com\/ellethee\/eteSkeleton","3":"* Added enhancements from Chris MacLeod's fork (https:\/\/github.com\/stick\/eteSkeleton).\r\n* Added localization.\r\n* Changed the TAG's brackets from <> to {}\r\n* Added some builtin TAG.\r\n\r\nPlease refer to https:\/\/github.com\/ellethee\/eteSkeleton","package":"eteSkeleton-103.zip","4":"eteSkeleton-103.zip","src_id":"24757","5":"24757","creation_date":"1479802149","6":"1479802149"},{"0":"3370","vim_version":"7.0","1":"7.0","script_version":"1.0.1","2":"1.0.1","version_comment":"Initial upload","3":"Initial upload","package":"eteSkeleton.vba","4":"eteSkeleton.vba","src_id":"14515","5":"14515","creation_date":"1292345574","6":"1292345574"}]},"3369":{"script_id":"3369","0":"3369","script_name":"softbluev2","1":"softbluev2","script_type":"color scheme","2":"color scheme","summary":" softblue,comfortable.","3":" softblue,comfortable.","description":"This is a color scheme  modified from softblue by ZhangJing.\r\n feel softblue,comfortable.\r\nScreenshot:  http:\/\/boshi.us\/?p=207\r\n","4":"This is a color scheme  modified from softblue by ZhangJing.\r\n feel softblue,comfortable.\r\nScreenshot:  http:\/\/boshi.us\/?p=207\r\n","install_details":"Just put it in your ~\/.vim\/colors  (Linux) or $VIM\\\\vimfiles  (Windows).","5":"Just put it in your ~\/.vim\/colors  (Linux) or $VIM\\\\vimfiles  (Windows).","first_name":"bo","6":"bo","last_name":"shi","7":"shi","releases":[{"0":"3369","vim_version":"7.0","1":"7.0","script_version":"1.2","2":"1.2","version_comment":"update termbg color","3":"update termbg color","package":"softbluev2.vim","4":"softbluev2.vim","src_id":"14509","5":"14509","creation_date":"1292339506","6":"1292339506"}]},"3368":{"script_id":"3368","0":"3368","script_name":"List File","1":"List File","script_type":"utility","2":"utility","summary":"Nested, folded lists","3":"Nested, folded lists","description":"Plugin provides simple and efficient tools for managing a plain-text file of nested lists.\r\n\r\nScreenshot: http:\/\/lucasoman.com\/images\/listfile.png\r\nDetailed documentation: http:\/\/lucasoman.blogspot.com\/2010\/12\/list-file-plugin-for-vim.html\r\n\r\nNOTE: I greatly appreciate any feedback. Feature suggestions, bug reports and other comments are encouraged. I'm eager to improve this plugin!\r\n\r\nFeature highlights:\r\n\r\n- Prioritizing\r\n- Sorting\r\n- Setting due dates\r\n- Searching\r\n- Tagging\r\n- Unlimited nesting\r\n- Timestamping\r\n- Flexibility without complexity\r\n- Efficient and convenient mappings","4":"Plugin provides simple and efficient tools for managing a plain-text file of nested lists.\r\n\r\nScreenshot: http:\/\/lucasoman.com\/images\/listfile.png\r\nDetailed documentation: http:\/\/lucasoman.blogspot.com\/2010\/12\/list-file-plugin-for-vim.html\r\n\r\nNOTE: I greatly appreciate any feedback. Feature suggestions, bug reports and other comments are encouraged. I'm eager to improve this plugin!\r\n\r\nFeature highlights:\r\n\r\n- Prioritizing\r\n- Sorting\r\n- Setting due dates\r\n- Searching\r\n- Tagging\r\n- Unlimited nesting\r\n- Timestamping\r\n- Flexibility without complexity\r\n- Efficient and convenient mappings","install_details":"Untar in your .vim dir. Adds only two files: the plugin itself and a syntax file.","5":"Untar in your .vim dir. Adds only two files: the plugin itself and a syntax file.","first_name":"Lucas","6":"Lucas","last_name":"Oman","7":"Oman","releases":[{"0":"3368","vim_version":"7.0","1":"7.0","script_version":"1.2.1","2":"1.2.1","version_comment":"Mostly small enhancements and bug fixes:\r\n- :Lcreate now assumes that when executed on an unsaved buffer, intention is to use current buffer as the list file (thanks to Houl on #vim@freenode for the suggestion!)\r\n- fixed tag indexing bug; before, only the first tag on each line was indexed for tab-completion\r\n- made due date format configurable (thanks to Houl for the suggestion!)\r\n- changed folding, which made it more robust\r\n- made syntax highlighting less buggy \r\n- prettified location list for searches\r\n- searching by due date now ignores completed ('x' marked) items","3":"Mostly small enhancements and bug fixes:\r\n- :Lcreate now assumes that when executed on an unsaved buffer, intention is to use current buffer as the list file (thanks to Houl on #vim@freenode for the suggestion!)\r\n- fixed tag indexing bug; before, only the first tag on each line was indexed for tab-completion\r\n- made due date format configurable (thanks to Houl for the suggestion!)\r\n- changed folding, which made it more robust\r\n- made syntax highlighting less buggy \r\n- prettified location list for searches\r\n- searching by due date now ignores completed ('x' marked) items","package":"listfile-1.2.1.tar.gz","4":"listfile-1.2.1.tar.gz","src_id":"16143","5":"16143","creation_date":"1311649560","6":"1311649560"},{"0":"3368","vim_version":"7.0","1":"7.0","script_version":"1.2.0","2":"1.2.0","version_comment":"Added the following:\r\nDue Dates: set a due date for an item and search for items by due date. Date format is very flexible, allowing ranges of days or weeks. See docs.\r\nDefault mark: optionally configure the default mark for new items.","3":"Added the following:\r\nDue Dates: set a due date for an item and search for items by due date. Date format is very flexible, allowing ranges of days or weeks. See docs.\r\nDefault mark: optionally configure the default mark for new items.","package":"listfile-1.2.0.tar.gz","4":"listfile-1.2.0.tar.gz","src_id":"15228","5":"15228","creation_date":"1300281214","6":"1300281214"},{"0":"3368","vim_version":"7.0","1":"7.0","script_version":"1.1.0","2":"1.1.0","version_comment":"Greatly improved the intelligence of new item creation. New items use the mark from the item above them. They also will be created below the sub-items of the item above them. Before, the sub-items would be \"adopted\" by the new item.","3":"Greatly improved the intelligence of new item creation. New items use the mark from the item above them. They also will be created below the sub-items of the item above them. Before, the sub-items would be \"adopted\" by the new item.","package":"listfile-1.1.0.tar.gz","4":"listfile-1.1.0.tar.gz","src_id":"15156","5":"15156","creation_date":"1299207845","6":"1299207845"},{"0":"3368","vim_version":"7.0","1":"7.0","script_version":"1.0.4","2":"1.0.4","version_comment":"Fix: :Lmark failing on top-level items","3":"Fix: :Lmark failing on top-level items","package":"listfile-1.0.4.tar.gz","4":"listfile-1.0.4.tar.gz","src_id":"14545","5":"14545","creation_date":"1292598430","6":"1292598430"},{"0":"3368","vim_version":"7.0","1":"7.0","script_version":"1.0.3","2":"1.0.3","version_comment":"Fix: depending on value of tw, long items were hard wrapping","3":"Fix: depending on value of tw, long items were hard wrapping","package":"listfile-1.0.3.tar.gz","4":"listfile-1.0.3.tar.gz","src_id":"14530","5":"14530","creation_date":"1292508964","6":"1292508964"},{"0":"3368","vim_version":"7.0","1":"7.0","script_version":"1.0.2","2":"1.0.2","version_comment":"Fixes: :Lcreate not working (whoops), also simplified its functionality (creates in current buffer, not new tab)","3":"Fixes: :Lcreate not working (whoops), also simplified its functionality (creates in current buffer, not new tab)","package":"listfile-1.0.2.tar.gz","4":"listfile-1.0.2.tar.gz","src_id":"14521","5":"14521","creation_date":"1292420983","6":"1292420983"},{"0":"3368","vim_version":"7.0","1":"7.0","script_version":"1.0.1","2":"1.0.1","version_comment":"Fixes: default sorting behavior for unrecognized marks, globalness of option variables","3":"Fixes: default sorting behavior for unrecognized marks, globalness of option variables","package":"listfile-1.0.1.tar.gz","4":"listfile-1.0.1.tar.gz","src_id":"14517","5":"14517","creation_date":"1292389878","6":"1292389878"},{"0":"3368","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"listfile-1.0.tar.gz","4":"listfile-1.0.tar.gz","src_id":"14501","5":"14501","creation_date":"1292297395","6":"1292297395"}]},"3367":{"script_id":"3367","0":"3367","script_name":"vimblogger_ft","1":"vimblogger_ft","script_type":"ftplugin","2":"ftplugin","summary":"reStructuredText to Blogger Interface","3":"reStructuredText to Blogger Interface","description":"vimblogger_ft is a simple reStructuredText to Blogger Interface through VIm.\r\n\r\nAs the name suggest it is a filetype plugin, which helps to create blog articles in rsST format and send them to blog site. It also provides commands for preview in browser and delete articles.\r\n\r\nModule for communication was written in Python. So, VIm has to be compiled with +python.\r\n\r\nOther requirements:\r\n  - Python (tested with version 2.6, should also work with other versions prior 3.0)\r\n  - gdata http:\/\/code.google.com\/p\/gdata-python-client\r\n  - docutils http:\/\/docutils.sourceforge.net\r\n  - pygments http:\/\/pygments.org (optional)\r\n\r\nSee documentation for detailed description.","4":"vimblogger_ft is a simple reStructuredText to Blogger Interface through VIm.\r\n\r\nAs the name suggest it is a filetype plugin, which helps to create blog articles in rsST format and send them to blog site. It also provides commands for preview in browser and delete articles.\r\n\r\nModule for communication was written in Python. So, VIm has to be compiled with +python.\r\n\r\nOther requirements:\r\n  - Python (tested with version 2.6, should also work with other versions prior 3.0)\r\n  - gdata http:\/\/code.google.com\/p\/gdata-python-client\r\n  - docutils http:\/\/docutils.sourceforge.net\r\n  - pygments http:\/\/pygments.org (optional)\r\n\r\nSee documentation for detailed description.","install_details":"In order to install the vba, open the vba file in VIM and type:\r\n    :so %\r\n\r\nIt is also available via bitbucket:\r\n    http:\/\/bitbucket.org\/gryf\/vimblogger_ft","5":"In order to install the vba, open the vba file in VIM and type:\r\n    :so %\r\n\r\nIt is also available via bitbucket:\r\n    http:\/\/bitbucket.org\/gryf\/vimblogger_ft","first_name":"Roman","6":"Roman","last_name":"Dobosz","7":"Dobosz","releases":[{"0":"3367","vim_version":"7.0","1":"7.0","script_version":"0.2","2":"0.2","version_comment":"Pygments sourcecode directive improvements","3":"Pygments sourcecode directive improvements","package":"vimblogger_ft.vba","4":"vimblogger_ft.vba","src_id":"14619","5":"14619","creation_date":"1293293137","6":"1293293137"},{"0":"3367","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"vimblogger_ft.vba","4":"vimblogger_ft.vba","src_id":"14499","5":"14499","creation_date":"1292275266","6":"1292275266"}]},"3366":{"script_id":"3366","0":"3366","script_name":"Shebang","1":"Shebang","script_type":"utility","2":"utility","summary":"Make executable by setting the correct shebang and executable bit","3":"Make executable by setting the correct shebang and executable bit","description":"This script tries to reduce the repetitive work it is to make a file executable. It provides three functions:\r\n\r\nSetShebang() which sets the correct shebang (e.g. \"#!\/usr\/bin\/python\"),\r\nSetExecutableBit() which sets the executable bit, and\r\nSetExecutable() which calls the two functions above.\r\n\r\nThe SetExecutableBit() is simply stolen from http:\/\/vim.wikia.com\/wiki\/Setting_file_attributes_without_reloading_a_buffer . Thanks a lot Max Ischenko!","4":"This script tries to reduce the repetitive work it is to make a file executable. It provides three functions:\r\n\r\nSetShebang() which sets the correct shebang (e.g. \"#!\/usr\/bin\/python\"),\r\nSetExecutableBit() which sets the executable bit, and\r\nSetExecutable() which calls the two functions above.\r\n\r\nThe SetExecutableBit() is simply stolen from http:\/\/vim.wikia.com\/wiki\/Setting_file_attributes_without_reloading_a_buffer . Thanks a lot Max Ischenko!","install_details":"Put this file in your .vim\/plugin folder and map a key to call SetExecutable. For example, in my vimrc, I have\r\n\r\nmap <leader>X :w<CR>:call SetExecutable()<CR>","5":"Put this file in your .vim\/plugin folder and map a key to call SetExecutable. For example, in my vimrc, I have\r\n\r\nmap <leader>X :w<CR>:call SetExecutable()<CR>","first_name":"Johannes","6":"Johannes","last_name":"Hoff","7":"Hoff","releases":[{"0":"3366","vim_version":"7.0","1":"7.0","script_version":"1.1","2":"1.1","version_comment":"Support for more filetypes","3":"Support for more filetypes","package":"shebang.vim","4":"shebang.vim","src_id":"18095","5":"18095","creation_date":"1338992127","6":"1338992127"},{"0":"3366","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"shebang.vim","4":"shebang.vim","src_id":"14496","5":"14496","creation_date":"1292235181","6":"1292235181"}]},"3365":{"script_id":"3365","0":"3365","script_name":"txt.vim","1":"txt.vim","script_type":"syntax","2":"syntax","summary":"Syntax file for plain text file in Chinese","3":"Syntax file for plain text file in Chinese","description":"Simple syntax script for plain text file, colors numbers, Chinese punctuation marks, quoted or bracketed text, etc.\r\n\r\nPreview:\r\nhttp:\/\/i111.photobucket.com\/albums\/n154\/calon_plus\/_003.png","4":"Simple syntax script for plain text file, colors numbers, Chinese punctuation marks, quoted or bracketed text, etc.\r\n\r\nPreview:\r\nhttp:\/\/i111.photobucket.com\/albums\/n154\/calon_plus\/_003.png","install_details":"copy txt.vim to vim syntax file directory, set syntax=txt","5":"copy txt.vim to vim syntax file directory, set syntax=txt","first_name":"calon","6":"calon","last_name":"xu","7":"xu","releases":[{"0":"3365","vim_version":"7.0","1":"7.0","script_version":"1.1","2":"1.1","version_comment":"Color of 26 letters changed to lavender purple, differs from non-English text color.","3":"Color of 26 letters changed to lavender purple, differs from non-English text color.","package":"txt.vim","4":"txt.vim","src_id":"16392","5":"16392","creation_date":"1314584234","6":"1314584234"},{"0":"3365","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"txt.vim","4":"txt.vim","src_id":"14483","5":"14483","creation_date":"1292161728","6":"1292161728"}]},"3364":{"script_id":"3364","0":"3364","script_name":"Ceasy","1":"Ceasy","script_type":"utility","2":"utility","summary":"A C interpreter from withim Vim","3":"A C interpreter from withim Vim","description":"This scripts makes your Vim become a C interpreter.\r\nYou can simply select text and make it run at real time.\r\nAnd other much more features.\r\n","4":"This scripts makes your Vim become a C interpreter.\r\nYou can simply select text and make it run at real time.\r\nAnd other much more features.\r\n","install_details":"You just need to load it to your way.","5":"You just need to load it to your way.","first_name":"iury","6":"iury","last_name":"oliveira","7":"oliveira","releases":[{"0":"3364","vim_version":"7.0","1":"7.0","script_version":"3","2":"3","version_comment":"with no bugs","3":"with no bugs","package":"cease.vim","4":"cease.vim","src_id":"14486","5":"14486","creation_date":"1292168242","6":"1292168242"},{"0":"3364","vim_version":"7.0","1":"7.0","script_version":"3","2":"3","version_comment":"Very much better.","3":"Very much better.","package":"cease.vim","4":"cease.vim","src_id":"14485","5":"14485","creation_date":"1292166133","6":"1292166133"},{"0":"3364","vim_version":"7.0","1":"7.0","script_version":"1","2":"1","version_comment":"Initial upload","3":"Initial upload","package":"cease.vim","4":"cease.vim","src_id":"14481","5":"14481","creation_date":"1292161189","6":"1292161189"}]},"3363":{"script_id":"3363","0":"3363","script_name":"southwest-fog","1":"southwest-fog","script_type":"color scheme","2":"color scheme","summary":"Not too dark, low contrast","3":"Not too dark, low contrast","description":"Screenshot: http:\/\/img46.imageshack.us\/img46\/6466\/asyncbeforeaftertestjsc.png\r\n\r\nPathogen : https:\/\/github.com\/mgutz\/vim-colors","4":"Screenshot: http:\/\/img46.imageshack.us\/img46\/6466\/asyncbeforeaftertestjsc.png\r\n\r\nPathogen : https:\/\/github.com\/mgutz\/vim-colors","install_details":"Copy to ~\/.vim\/colors\r\n\r\nFor gVim or MacVim","5":"Copy to ~\/.vim\/colors\r\n\r\nFor gVim or MacVim","first_name":"Mario","6":"Mario","last_name":"Gutierrez","7":"Gutierrez","releases":[{"0":"3363","vim_version":"7.0","1":"7.0","script_version":"0.2","2":"0.2","version_comment":"diff\r\nseveral minor tweaks","3":"diff\r\nseveral minor tweaks","package":"southwest-fog.vim","4":"southwest-fog.vim","src_id":"14488","5":"14488","creation_date":"1292181486","6":"1292181486"},{"0":"3363","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"southwest-fog.vim","4":"southwest-fog.vim","src_id":"14480","5":"14480","creation_date":"1292147830","6":"1292147830"}]},"3362":{"script_id":"3362","0":"3362","script_name":"janitor.vim","1":"janitor.vim","script_type":"utility","2":"utility","summary":"Remove extra whitespaces at end of each line","3":"Remove extra whitespaces at end of each line","description":"Plugin created just for remove extra whitespaces at end of each line after saving buffer.\r\n\r\nhttps:\/\/github.com\/kossnocorp\/janitor.vim","4":"Plugin created just for remove extra whitespaces at end of each line after saving buffer.\r\n\r\nhttps:\/\/github.com\/kossnocorp\/janitor.vim","install_details":"Put janitor.vim to plugins directory and restart Vim.","5":"Put janitor.vim to plugins directory and restart Vim.","first_name":"Sasha","6":"Sasha","last_name":"Koss","7":"Koss","releases":[{"0":"3362","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"janitor.vim","4":"janitor.vim","src_id":"14478","5":"14478","creation_date":"1292137997","6":"1292137997"}]},"3361":{"script_id":"3361","0":"3361","script_name":"Indent Guides","1":"Indent Guides","script_type":"syntax","2":"syntax","summary":"A plugin for visually displaying indent levels in Vim.","3":"A plugin for visually displaying indent levels in Vim.","description":"Indent Guides is a plugin for visually displaying indent levels in Vim.\r\n\r\nFEATURES:\r\n- Can detect both tab and space indent styles.\r\n- Automatically inspects your colorscheme and picks appropriate colors (gVim only).\r\n- Will highlight indent levels with alternating colors.\r\n- Full support for gVim and basic support for Terminal Vim.\r\n- Seems to work on Windows gVim 7.3 (haven't done any extensive tests though).\r\n- Customizable size for indent guides, eg. skinny guides (soft-tabs only).\r\n- Customizable start indent level.\r\n- NEW: Highlight support for files with a mixture of tab and space indent styles.\r\n\r\nUSAGE:\r\nThe default mapping to toggle the plugin is `<Leader>ig`\r\n\r\nGVIM:\r\nThis plugin should work with gVim out of the box, no configuration needed. It will automatically inspect your colorscheme and pick appropriate colors.\r\n\r\nSETTING CUSTOM INDENT COLORS:\r\nHere's an example of how to define custom colors instead of using the ones the plugin automatically generates for you. Add this to your `.vimrc` file:\r\n>\r\n  let g:indent_guides_auto_colors = 0\r\n  autocmd VimEnter,Colorscheme * :hi IndentGuidesOdd  guibg=red   ctermbg=3\r\n  autocmd VimEnter,Colorscheme * :hi IndentGuidesEven guibg=green ctermbg=4\r\n<\r\n\r\nAlternatively you can add the following lines to your colorscheme file.\r\n>\r\n  hi IndentGuidesOdd  guibg=red   ctermbg=3\r\n  hi IndentGuidesEven guibg=green ctermbg=4\r\n<\r\n\r\nTERMINAL VIM:\r\nAt the moment Terminal Vim only has basic support. This means is that colors won't be automatically calculated based on your colorscheme. Instead, some preset colors are used depending on whether `background` is set to `dark` or `light`.\r\n\r\nWhen `set background=dark` is used, the following highlight colors will be defined:\r\n>\r\n  hi IndentGuidesEven ctermbg=darkgrey\r\n  hi IndentGuidesOdd  ctermbg=black\r\n<\r\n\r\nAlternatively, when `set background=light` is used, the following highlight colors will be defined:\r\n>\r\n  hi IndentGuidesEven ctermbg=lightgrey\r\n  hi IndentGuidesOdd  ctermbg=white\r\n<\r\n\r\nIf for some reason it's incorrectly defining light highlight colors instead of dark ones or vice versa, the first thing you should check is that the `background` value is being set correctly for your colorscheme. Sometimes it's best to manually set the `background` value in your `.vimrc`, for example:\r\n>\r\n  colorscheme desert256\r\n  set background=dark\r\n<\r\n\r\nAlternatively you can manually setup the highlight colors yourself, see `:help indent_guides_auto_colors` for an example.\r\n\r\nGITHUB:\r\nhttps:\/\/github.com\/nathanaelkane\/vim-indent-guides\r\n\r\nSCREENSHOTS:\r\nhttp:\/\/nathanaelkane.imgur.com\/indent_guides","4":"Indent Guides is a plugin for visually displaying indent levels in Vim.\r\n\r\nFEATURES:\r\n- Can detect both tab and space indent styles.\r\n- Automatically inspects your colorscheme and picks appropriate colors (gVim only).\r\n- Will highlight indent levels with alternating colors.\r\n- Full support for gVim and basic support for Terminal Vim.\r\n- Seems to work on Windows gVim 7.3 (haven't done any extensive tests though).\r\n- Customizable size for indent guides, eg. skinny guides (soft-tabs only).\r\n- Customizable start indent level.\r\n- NEW: Highlight support for files with a mixture of tab and space indent styles.\r\n\r\nUSAGE:\r\nThe default mapping to toggle the plugin is `<Leader>ig`\r\n\r\nGVIM:\r\nThis plugin should work with gVim out of the box, no configuration needed. It will automatically inspect your colorscheme and pick appropriate colors.\r\n\r\nSETTING CUSTOM INDENT COLORS:\r\nHere's an example of how to define custom colors instead of using the ones the plugin automatically generates for you. Add this to your `.vimrc` file:\r\n>\r\n  let g:indent_guides_auto_colors = 0\r\n  autocmd VimEnter,Colorscheme * :hi IndentGuidesOdd  guibg=red   ctermbg=3\r\n  autocmd VimEnter,Colorscheme * :hi IndentGuidesEven guibg=green ctermbg=4\r\n<\r\n\r\nAlternatively you can add the following lines to your colorscheme file.\r\n>\r\n  hi IndentGuidesOdd  guibg=red   ctermbg=3\r\n  hi IndentGuidesEven guibg=green ctermbg=4\r\n<\r\n\r\nTERMINAL VIM:\r\nAt the moment Terminal Vim only has basic support. This means is that colors won't be automatically calculated based on your colorscheme. Instead, some preset colors are used depending on whether `background` is set to `dark` or `light`.\r\n\r\nWhen `set background=dark` is used, the following highlight colors will be defined:\r\n>\r\n  hi IndentGuidesEven ctermbg=darkgrey\r\n  hi IndentGuidesOdd  ctermbg=black\r\n<\r\n\r\nAlternatively, when `set background=light` is used, the following highlight colors will be defined:\r\n>\r\n  hi IndentGuidesEven ctermbg=lightgrey\r\n  hi IndentGuidesOdd  ctermbg=white\r\n<\r\n\r\nIf for some reason it's incorrectly defining light highlight colors instead of dark ones or vice versa, the first thing you should check is that the `background` value is being set correctly for your colorscheme. Sometimes it's best to manually set the `background` value in your `.vimrc`, for example:\r\n>\r\n  colorscheme desert256\r\n  set background=dark\r\n<\r\n\r\nAlternatively you can manually setup the highlight colors yourself, see `:help indent_guides_auto_colors` for an example.\r\n\r\nGITHUB:\r\nhttps:\/\/github.com\/nathanaelkane\/vim-indent-guides\r\n\r\nSCREENSHOTS:\r\nhttp:\/\/nathanaelkane.imgur.com\/indent_guides","install_details":"To install the plugin just copy `autoload`, `plugin`, `doc` directories into your `.vim` directory.\r\n\r\nAlternatively if you have Pathogen installed, just clone this repo into a subdirectory of your `.vim\/bundle` directory like so:\r\ncd ~\/.vim\/bundle\r\ngit clone git:\/\/github.com\/nathanaelkane\/vim-indent-guides.git\r\n","5":"To install the plugin just copy `autoload`, `plugin`, `doc` directories into your `.vim` directory.\r\n\r\nAlternatively if you have Pathogen installed, just clone this repo into a subdirectory of your `.vim\/bundle` directory like so:\r\ncd ~\/.vim\/bundle\r\ngit clone git:\/\/github.com\/nathanaelkane\/vim-indent-guides.git\r\n","first_name":"Nate","6":"Nate","last_name":"Kane","7":"Kane","releases":[{"0":"3361","vim_version":"7.0","1":"7.0","script_version":"1.7","2":"1.7","version_comment":"- Added way to override the default mapping (thanks xuhdev).\r\n- Added option g:indent_guides_exclude_filetypes to specify a list of filetypes to disable the plugin for.\r\n- Disable the plugin when in a diff.\r\n- Various bug fixes.","3":"- Added way to override the default mapping (thanks xuhdev).\r\n- Added option g:indent_guides_exclude_filetypes to specify a list of filetypes to disable the plugin for.\r\n- Disable the plugin when in a diff.\r\n- Various bug fixes.","package":"indent-guides-1.7.tar.gz","4":"indent-guides-1.7.tar.gz","src_id":"19601","5":"19601","creation_date":"1362623082","6":"1362623082"},{"0":"3361","vim_version":"7.0","1":"7.0","script_version":"1.6","2":"1.6","version_comment":"- Added option `g:indent_guides_space_guides` to control whether spaces are considered as indention (thanks scoz).\r\n- Fixed E803 ID not found spam (thanks mutewinter).\r\n- Fixed str2float issue with Vim 7.1 (thanks acx0).","3":"- Added option `g:indent_guides_space_guides` to control whether spaces are considered as indention (thanks scoz).\r\n- Fixed E803 ID not found spam (thanks mutewinter).\r\n- Fixed str2float issue with Vim 7.1 (thanks acx0).","package":"indent-guides-1.6.tar.gz","4":"indent-guides-1.6.tar.gz","src_id":"17141","5":"17141","creation_date":"1325419369","6":"1325419369"},{"0":"3361","vim_version":"7.0","1":"7.0","script_version":"1.5","2":"1.5","version_comment":"- Added highlight support for files with a mixture of tab and space indent styles (thanks graywh).\r\n- Added -bar to all the :commands so they can chain with other :commands (thanks to graywh).\r\n- No longer overriding pre-defined custom highlight colors (thanks graywh).\r\n- Using str2float to work around a float bug in some versions of Vim 7.2 (thanks voidus).","3":"- Added highlight support for files with a mixture of tab and space indent styles (thanks graywh).\r\n- Added -bar to all the :commands so they can chain with other :commands (thanks to graywh).\r\n- No longer overriding pre-defined custom highlight colors (thanks graywh).\r\n- Using str2float to work around a float bug in some versions of Vim 7.2 (thanks voidus).","package":"indent-guides-1.5.tar.gz","4":"indent-guides-1.5.tar.gz","src_id":"15208","5":"15208","creation_date":"1300016920","6":"1300016920"},{"0":"3361","vim_version":"7.0","1":"7.0","script_version":"1.4","2":"1.4","version_comment":"- Added the new plugin option `g:indent_guides_enable_on_vim_startup`.\r\n- Improved Windows support.\r\n","3":"- Added the new plugin option `g:indent_guides_enable_on_vim_startup`.\r\n- Improved Windows support.\r\n","package":"indent-guides-1.4.tar.gz","4":"indent-guides-1.4.tar.gz","src_id":"14963","5":"14963","creation_date":"1296998438","6":"1296998438"},{"0":"3361","vim_version":"7.0","1":"7.0","script_version":"1.3","2":"1.3","version_comment":"- Changed the default value of g:indent_guides_color_change_percent to 10.\r\n- Added support for gVim themes that don't specify a `hi Normal guibg` color.","3":"- Changed the default value of g:indent_guides_color_change_percent to 10.\r\n- Added support for gVim themes that don't specify a `hi Normal guibg` color.","package":"indent-guides-1.3.tar.gz","4":"indent-guides-1.3.tar.gz","src_id":"14769","5":"14769","creation_date":"1295264993","6":"1295264993"},{"0":"3361","vim_version":"7.0","1":"7.0","script_version":"1.2","2":"1.2","version_comment":"- Customizable size for indent guides, eg. skinny guides (soft-tabs only).\r\n- Customizable start indent level.\r\n- Refactored some internal logic.","3":"- Customizable size for indent guides, eg. skinny guides (soft-tabs only).\r\n- Customizable start indent level.\r\n- Refactored some internal logic.","package":"indent-guides-1.2.tar.gz","4":"indent-guides-1.2.tar.gz","src_id":"14721","5":"14721","creation_date":"1294660125","6":"1294660125"},{"0":"3361","vim_version":"7.0","1":"7.0","script_version":"1.1","2":"1.1","version_comment":"- Added basic support for terminal vim. See `:help indent-guides-terminal-vim` for more information.\r\n- Cut down on rgb to hex color conversions by adding a big dictionary of color names and hex codes.\r\n- Various bug fixes.\r\n","3":"- Added basic support for terminal vim. See `:help indent-guides-terminal-vim` for more information.\r\n- Cut down on rgb to hex color conversions by adding a big dictionary of color names and hex codes.\r\n- Various bug fixes.\r\n","package":"indent-guides-1.1.tar.gz","4":"indent-guides-1.1.tar.gz","src_id":"14649","5":"14649","creation_date":"1293624776","6":"1293624776"},{"0":"3361","vim_version":"7.2","1":"7.2","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"indent-guides-1.0.tar.gz","4":"indent-guides-1.0.tar.gz","src_id":"14477","5":"14477","creation_date":"1292129345","6":"1292129345"}]},"3360":{"script_id":"3360","0":"3360","script_name":"Peasy","1":"Peasy","script_type":"syntax","2":"syntax","summary":"A python interpreter from within Vim.","3":"A python interpreter from within Vim.","description":"You can choose to run python code by using 'v' from inside the current buffer. And you can check your while programming in python. You can evaluate expressions\/statements easily.","4":"You can choose to run python code by using 'v' from inside the current buffer. And you can check your while programming in python. You can evaluate expressions\/statements easily.","install_details":"Just put in ~\/.vim\/plugins\/Peasy.py","5":"Just put in ~\/.vim\/plugins\/Peasy.py","first_name":"iury","6":"iury","last_name":"oliveira","7":"oliveira","releases":[{"0":"3360","vim_version":"7.0","1":"7.0","script_version":"2","2":"2","version_comment":"This one is very much better. it supports several buffers at the same time.\r\nit works as though you had several instances, one per buffer.","3":"This one is very much better. it supports several buffers at the same time.\r\nit works as though you had several instances, one per buffer.","package":"pease.vim","4":"pease.vim","src_id":"14482","5":"14482","creation_date":"1292161413","6":"1292161413"},{"0":"3360","vim_version":"7.0","1":"7.0","script_version":"1","2":"1","version_comment":"Initial upload","3":"Initial upload","package":"Peasy.py","4":"Peasy.py","src_id":"14473","5":"14473","creation_date":"1292055570","6":"1292055570"}]},"3359":{"script_id":"3359","0":"3359","script_name":"FIGlet.vim","1":"FIGlet.vim","script_type":"utility","2":"utility","summary":"Finally, the power of Vim + FIGlet!","3":"Finally, the power of Vim + FIGlet!","description":":FIGlet operates over a range of text in your buffer. It has a completion function that will complete on installed font names, too.\r\nSet g:use_FIGlet_as_operatorfunc to a true value in your vimrc file to enable the g@ operator to filter your text through figlet, in-place.\r\n:FIGletFontDemo renders a sample of text through each installed figlet font.\r\nPlus, there is a Windows\/MS-DOS version of FIGlet, so everybody can get in on the fun!\r\n\r\nFollow this plugin on GitHub: https:\/\/github.com\/fadein\/vim-FIGlet\r\n\r\nQ: Can't I do this same thing with the :! command?\r\nA: Basically, sure\r\n\r\nQ: What does this plugin give me that Vim's built-in filtering doesn't?\r\nA1. Convenience - through variables it can remember your preferences\r\nA2. Completion - so you don't have to memorize all of the commands or font names\r\nA3. Text-objects - use the g@ operator with text-objects for blazing fast transformations that will knock shoulder-surfer's socks off\r\nA4. A font sample buffer to help you pick out the perfect font for the occasion\r\n\r\nQ: Okay, I'm sold.  But what is this FIGlet you speak of?\r\nA: This:\r\n  __ _       _      _   \r\n \/ _(_) __ _| | ___| |_ \r\n| |_| |\/ _` | |\/ _ \\ __|\r\n|  _| | (_| | |  __\/ |_ \r\n|_| |_|\\__, |_|\\___|\\__|\r\n       |___\/            \r\n\r\nEr, that wasn't quite as impressive as I was hoping.  Check out http:\/\/www.figlet.org\/ to get with the times.","4":":FIGlet operates over a range of text in your buffer. It has a completion function that will complete on installed font names, too.\r\nSet g:use_FIGlet_as_operatorfunc to a true value in your vimrc file to enable the g@ operator to filter your text through figlet, in-place.\r\n:FIGletFontDemo renders a sample of text through each installed figlet font.\r\nPlus, there is a Windows\/MS-DOS version of FIGlet, so everybody can get in on the fun!\r\n\r\nFollow this plugin on GitHub: https:\/\/github.com\/fadein\/vim-FIGlet\r\n\r\nQ: Can't I do this same thing with the :! command?\r\nA: Basically, sure\r\n\r\nQ: What does this plugin give me that Vim's built-in filtering doesn't?\r\nA1. Convenience - through variables it can remember your preferences\r\nA2. Completion - so you don't have to memorize all of the commands or font names\r\nA3. Text-objects - use the g@ operator with text-objects for blazing fast transformations that will knock shoulder-surfer's socks off\r\nA4. A font sample buffer to help you pick out the perfect font for the occasion\r\n\r\nQ: Okay, I'm sold.  But what is this FIGlet you speak of?\r\nA: This:\r\n  __ _       _      _   \r\n \/ _(_) __ _| | ___| |_ \r\n| |_| |\/ _` | |\/ _ \\ __|\r\n|  _| | (_| | |  __\/ |_ \r\n|_| |_|\\__, |_|\\___|\\__|\r\n       |___\/            \r\n\r\nEr, that wasn't quite as impressive as I was hoping.  Check out http:\/\/www.figlet.org\/ to get with the times.","install_details":"Make sure you've got the figlet program installed on your $PATH\r\nCopy script into your .vim\/plugin directory","5":"Make sure you've got the figlet program installed on your $PATH\r\nCopy script into your .vim\/plugin directory","first_name":"erik","6":"erik","last_name":"falor","7":"falor","releases":[{"0":"3359","vim_version":"7.0","1":"7.0","script_version":"3.1","2":"3.1","version_comment":"Put function definitions into autoload\/FIGlet.vim\r\nDon't unconditionally clobber g@\r\nDevelopment on GitHub https:\/\/github.com\/fadein\/vim-FIGlet","3":"Put function definitions into autoload\/FIGlet.vim\r\nDon't unconditionally clobber g@\r\nDevelopment on GitHub https:\/\/github.com\/fadein\/vim-FIGlet","package":"FIGlet.v3.1.zip","4":"FIGlet.v3.1.zip","src_id":"24362","5":"24362","creation_date":"1467912077","6":"1467912077"},{"0":"3359","vim_version":"7.0","1":"7.0","script_version":"3.0","2":"3.0","version_comment":"I cannot thank Suraj N. Kurapati enough for submitting a patch that sets the                                                                                                        '[ and '] marks around the FIGlet-ified text. Thank you for your great work. If it weren't for you there wouldn't be a version 3.0!\r\n\r\nThis version also changes the spelling of the commands from :Figlet* to :FIGlet* in keeping with the style of www.figlet.org.","3":"I cannot thank Suraj N. Kurapati enough for submitting a patch that sets the                                                                                                        '[ and '] marks around the FIGlet-ified text. Thank you for your great work. If it weren't for you there wouldn't be a version 3.0!\r\n\r\nThis version also changes the spelling of the commands from :Figlet* to :FIGlet* in keeping with the style of www.figlet.org.","package":"FIGlet.vim","4":"FIGlet.vim","src_id":"23588","5":"23588","creation_date":"1442040477","6":"1442040477"},{"0":"3359","vim_version":"7.0","1":"7.0","script_version":"2.0","2":"2.0","version_comment":":FigletFontDemo can be given a small sample of text to render; this lets you easily compare fonts","3":":FigletFontDemo can be given a small sample of text to render; this lets you easily compare fonts","package":"Figlet.vim","4":"Figlet.vim","src_id":"15956","5":"15956","creation_date":"1308803891","6":"1308803891"},{"0":"3359","vim_version":"7.0","1":"7.0","script_version":"1.1","2":"1.1","version_comment":"Add :FigletFontDemo - open a buffer with generated samples of installed fonts\r\n\r\nBugfixes; use shellescape() on text sent to figlet; better able to cope with figlet crashes, work around broken DOS build of figlet","3":"Add :FigletFontDemo - open a buffer with generated samples of installed fonts\r\n\r\nBugfixes; use shellescape() on text sent to figlet; better able to cope with figlet crashes, work around broken DOS build of figlet","package":"Figlet.vim","4":"Figlet.vim","src_id":"14500","5":"14500","creation_date":"1292279062","6":"1292279062"},{"0":"3359","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"Figlet.vim","4":"Figlet.vim","src_id":"14472","5":"14472","creation_date":"1292051088","6":"1292051088"}]},"3358":{"script_id":"3358","0":"3358","script_name":"tabpagecolorscheme","1":"tabpagecolorscheme","script_type":"utility","2":"utility","summary":"Each tab have its own colorscheme","3":"Each tab have its own colorscheme","description":"Each tab have its own colorscheme, using :Tcolorscheme command which acts as :colorscheme\n\n* http:\/\/github.com\/ujihisa\/tabpagecolorscheme (development)\n\nIt's handy when you also use unite-colorscheme.\n","4":"Each tab have its own colorscheme, using :Tcolorscheme command which acts as :colorscheme\n\n* http:\/\/github.com\/ujihisa\/tabpagecolorscheme (development)\n\nIt's handy when you also use unite-colorscheme.\n","install_details":"Just copy the file into your &rtp dir.\n","5":"Just copy the file into your &rtp dir.\n","first_name":"ujihisa","6":"ujihisa","last_name":".","7":".","releases":[{"0":"3358","vim_version":"7.3","1":"7.3","script_version":"1.4","2":"1.4","version_comment":"* license: GPLv3+\n* bugfix: g:colors_name is bad\n","3":"* license: GPLv3+\n* bugfix: g:colors_name is bad\n","package":"tabpagecolorscheme-1.4.zip","4":"tabpagecolorscheme-1.4.zip","src_id":"23225","5":"23225","creation_date":"1429855362","6":"1429855362"},{"0":"3358","vim_version":"7.3","1":"7.3","script_version":"1.3","2":"1.3","version_comment":"* a fatal bugfix: it didn't work actually\n","3":"* a fatal bugfix: it didn't work actually\n","package":"tabpagecolorscheme-1.3.zip","4":"tabpagecolorscheme-1.3.zip","src_id":"15118","5":"15118","creation_date":"1298688996","6":"1298688996"},{"0":"3358","vim_version":"7.3","1":"7.3","script_version":"1.2","2":"1.2","version_comment":"* bugfix: in case for g:colors_name is missing\n* don't run colorscheme command when the before\/after colorschemes are same\n","3":"* bugfix: in case for g:colors_name is missing\n* don't run colorscheme command when the before\/after colorschemes are same\n","package":"tabpagecolorscheme-1.2.zip","4":"tabpagecolorscheme-1.2.zip","src_id":"15069","5":"15069","creation_date":"1298346068","6":"1298346068"},{"0":"3358","vim_version":"7.3","1":"7.3","script_version":"1.1","2":"1.1","version_comment":"* added a use-cpo-save mechanism\n* stopped multiple inclusions\n* added color scheme completion\n* wrapped the auto-commands up into a auto-command group\n* allow the command to be called w\/o any arguments so it would display the current colorscheme just like the :colo command does\n* shorten the command name\n* (Thanks Peter Rincker!)\n","3":"* added a use-cpo-save mechanism\n* stopped multiple inclusions\n* added color scheme completion\n* wrapped the auto-commands up into a auto-command group\n* allow the command to be called w\/o any arguments so it would display the current colorscheme just like the :colo command does\n* shorten the command name\n* (Thanks Peter Rincker!)\n","package":"tabpagecolorscheme-1.1.zip","4":"tabpagecolorscheme-1.1.zip","src_id":"14479","5":"14479","creation_date":"1292140671","6":"1292140671"},{"0":"3358","vim_version":"7.3","1":"7.3","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"tabpagecolorscheme-1.0.zip","4":"tabpagecolorscheme-1.0.zip","src_id":"14471","5":"14471","creation_date":"1292035584","6":"1292035584"}]},"3357":{"script_id":"3357","0":"3357","script_name":"NERD_Tree & ack","1":"NERD_Tree & ack","script_type":"utility","2":"utility","summary":"Adding search capability to NERD_Tree with ack","3":"Adding search capability to NERD_Tree with ack","description":"Open NERD_Tree to your project folder, by typing :NERDtree \/path\/to\/project or by using bookmarks. Place the cursor on a folder and type the letter m. In the menu that will pop up you will have the option \"(s)earch directory\". Select it by pressing s and type your pattern. If your search will yield results, you will see a window in the lower part of your screen, with all the results. Navigate with the keys and press <CR> to jump to a result. The file will be opened in the last working window.","4":"Open NERD_Tree to your project folder, by typing :NERDtree \/path\/to\/project or by using bookmarks. Place the cursor on a folder and type the letter m. In the menu that will pop up you will have the option \"(s)earch directory\". Select it by pressing s and type your pattern. If your search will yield results, you will see a window in the lower part of your screen, with all the results. Navigate with the keys and press <CR> to jump to a result. The file will be opened in the last working window.","install_details":"Install NERD_Tree first. Then download this module to ~\/.vim\/plugin\/ or the appropriate location on your system and...you're done.\r\n\r\nInstall ack (see details at http:\/\/betterthangrep.com\/ ). Depending on your operating system, you need to type something like \"sudo apt-get install ack-grep\", \"brew install ack\" or other. Most of the installers will add ack to your $PATH, so NERD_Tree_Ack.vim won't require additional configuration. If you're weird and don't want to add ack to your $PATH, just add the following line to your .vimrc file:\r\n\r\nlet g:path_to_search_app = \"\/full\/path\/to\/ack\"\r\n\r\nIt should work.","5":"Install NERD_Tree first. Then download this module to ~\/.vim\/plugin\/ or the appropriate location on your system and...you're done.\r\n\r\nInstall ack (see details at http:\/\/betterthangrep.com\/ ). Depending on your operating system, you need to type something like \"sudo apt-get install ack-grep\", \"brew install ack\" or other. Most of the installers will add ack to your $PATH, so NERD_Tree_Ack.vim won't require additional configuration. If you're weird and don't want to add ack to your $PATH, just add the following line to your .vimrc file:\r\n\r\nlet g:path_to_search_app = \"\/full\/path\/to\/ack\"\r\n\r\nIt should work.","first_name":"Tudor","6":"Tudor","last_name":"Barbu","7":"Barbu","releases":[{"0":"3357","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"NERD_tree_ACK.vim","4":"NERD_tree_ACK.vim","src_id":"14469","5":"14469","creation_date":"1292004070","6":"1292004070"}]},"3356":{"script_id":"3356","0":"3356","script_name":"unite-yarm","1":"unite-yarm","script_type":"utility","2":"utility","summary":"A Unite.vim plugin for redmine","3":"A Unite.vim plugin for redmine","description":"unite-yarm is a unite.vim plugin for redmine\r\n\r\ndev : https:\/\/github.com\/basyura\/unite-yarm\r\n\r\n\r\nthis is a redmine client which use REST api.\r\n\r\nyou can view ticket's list.\r\nyou can update ticket's description and field.\r\nhttp:\/\/d.hatena.ne.jp\/basyura\/20101125\/p1\r\n\r\ndependency\r\n\r\n  unite.vim\r\n  https:\/\/github.com\/Shougo\/unite.vim\r\n\r\n  webapi-vim \r\n  https:\/\/github.com\/mattn\/webapi-vim\r\n\r\n  open-browser.vim\r\n  https:\/\/github.com\/tyru\/open-browser.vim\r\n\r\nUsage:\r\n  \r\n  :Unite redmine\r\n  :Unite redmine:project_id=hoge:status_id=open:per_page=100\r\n  :Unite redmine:project=hoge:status=open:per_page=100\r\n  :Unite redmine:!\r\n  \r\nchange description ,  and save buffer by :w\r\nissue is updated.\r\n  \r\nvariables\r\n\r\n  g:unite_yarm_server_url\r\n    redmine server url\r\n    default ：http:\/\/localhost:3000\r\n    example) let g:unite_yarm_server_url = 'http:\/\/localhost:3000'\r\n    \r\n  g:unite_yarm_access_key\r\n    API Access Key\r\n    you need key to update issue\r\n   default : read only\r\n   example) let g:unite_yarm_access_key = 'XXXXXXXXXXXXXXX'\r\n\r\n  g:unite_yarm_per_page\r\n    25 or 50 or 100\r\n    default : 25\r\n    example) let g:unite_yarm_per_page = 25\r\n  \r\n  g:unite_yarm_backup_dir\r\n    backup ticket's description\r\n    default : no backup\r\n    example) let g:unite_yarm_backup_dir = '\/tmp'\r\n\r\n\r\n","4":"unite-yarm is a unite.vim plugin for redmine\r\n\r\ndev : https:\/\/github.com\/basyura\/unite-yarm\r\n\r\n\r\nthis is a redmine client which use REST api.\r\n\r\nyou can view ticket's list.\r\nyou can update ticket's description and field.\r\nhttp:\/\/d.hatena.ne.jp\/basyura\/20101125\/p1\r\n\r\ndependency\r\n\r\n  unite.vim\r\n  https:\/\/github.com\/Shougo\/unite.vim\r\n\r\n  webapi-vim \r\n  https:\/\/github.com\/mattn\/webapi-vim\r\n\r\n  open-browser.vim\r\n  https:\/\/github.com\/tyru\/open-browser.vim\r\n\r\nUsage:\r\n  \r\n  :Unite redmine\r\n  :Unite redmine:project_id=hoge:status_id=open:per_page=100\r\n  :Unite redmine:project=hoge:status=open:per_page=100\r\n  :Unite redmine:!\r\n  \r\nchange description ,  and save buffer by :w\r\nissue is updated.\r\n  \r\nvariables\r\n\r\n  g:unite_yarm_server_url\r\n    redmine server url\r\n    default ：http:\/\/localhost:3000\r\n    example) let g:unite_yarm_server_url = 'http:\/\/localhost:3000'\r\n    \r\n  g:unite_yarm_access_key\r\n    API Access Key\r\n    you need key to update issue\r\n   default : read only\r\n   example) let g:unite_yarm_access_key = 'XXXXXXXXXXXXXXX'\r\n\r\n  g:unite_yarm_per_page\r\n    25 or 50 or 100\r\n    default : 25\r\n    example) let g:unite_yarm_per_page = 25\r\n  \r\n  g:unite_yarm_backup_dir\r\n    backup ticket's description\r\n    default : no backup\r\n    example) let g:unite_yarm_backup_dir = '\/tmp'\r\n\r\n\r\n","install_details":"","5":"","first_name":"basyura","6":"basyura","last_name":" ","7":" ","releases":[{"0":"3356","vim_version":"7.3","1":"7.3","script_version":"0.1.5","2":"0.1.5","version_comment":"fix escape","3":"fix escape","package":"unite-yarm.zip","4":"unite-yarm.zip","src_id":"14493","5":"14493","creation_date":"1292202999","6":"1292202999"},{"0":"3356","vim_version":"7.3","1":"7.3","script_version":"0.1.4","2":"0.1.4","version_comment":"fix function name","3":"fix function name","package":"unite-yarm.zip","4":"unite-yarm.zip","src_id":"14468","5":"14468","creation_date":"1291993846","6":"1291993846"},{"0":"3356","vim_version":"7.3","1":"7.3","script_version":"0.1.3","2":"0.1.3","version_comment":"change fileformat","3":"change fileformat","package":"unite-yarm.zip","4":"unite-yarm.zip","src_id":"14467","5":"14467","creation_date":"1291992957","6":"1291992957"},{"0":"3356","vim_version":"7.0","1":"7.0","script_version":"0.1.2","2":"0.1.2","version_comment":"Initial upload","3":"Initial upload","package":"unite-yarm.zip","4":"unite-yarm.zip","src_id":"14466","5":"14466","creation_date":"1291986822","6":"1291986822"}]},"3355":{"script_id":"3355","0":"3355","script_name":"UnconditionalPaste","1":"UnconditionalPaste","script_type":"utility","2":"utility","summary":"Force character-\/line-\/block-wise paste, regardless of how it was yanked. ","3":"Force character-\/line-\/block-wise paste, regardless of how it was yanked. ","description":"DESCRIPTION\r\nIf you're like me, you occasionally do a linewise yank, and then want to\r\ninsert that yanked text in the middle of some other line (or vice versa).\r\nThe mappings defined by this plugin will allow you to do a character-, line-,\r\nor block-wise paste no matter how you yanked the text, both from normal and\r\ninsert mode.\r\n\r\nOften, the register contents aren't quite in the form you need them. Maybe you\r\nneed to convert yanked lines to comma-separated arguments, maybe join the\r\nlines with another separator, maybe the reverse: un-joining a single line on\r\nsome pattern to yield multiple lines. Though you can do the manipulation after\r\npasting, this plugin offers shortcut mappings for these actions, which are\r\nespecially helpful when you need to repeat the paste multiple times.\r\n\r\nSOURCE\r\nBased on vimtip #1199 by cory,\r\n    http:\/\/vim.wikia.com\/wiki\/Unconditional_linewise_or_characterwise_paste\r\n\r\nRELATED WORKS\r\n- whitespaste.vim (vimscript #4351) automatically removes blank lines around\r\n  linewise contents, and condenses inner lines to a single one. By default, it\r\n  remaps p \/ P, but this can be changed.\r\n\r\nUSAGE\r\n[\"x]gcp, [\"x]gcP        Paste characterwise (inner newline characters and\r\n                        indent are flattened to a single space, leading and\r\n                        trailing removed) [count] times.\r\n\r\n[\"x]gcip, [\"x]gciP      Paste inline (inner newline characters and indent are\r\n                        kept, only leading and trailing removed) [count]\r\n                        times.\r\n\r\n[\"x]gcgp, [\"x]gcgP      Paste joined (like gJ); indent and surrounding\r\n                        whitespace is kept as-is, [count] times.\r\n\r\n[\"x]gCp, [\"x]gCP        Paste characterwise; any sequence of whitespace is\r\n                        flattened to a single space, leading and trailing\r\n                        indent removed, [count] times.\r\n\r\n[\"x]glp, [\"x]glP        Paste linewise (even if yanked text is not a complete\r\n                        line) [count] times.\r\n\r\n[\"x]gbp, [\"x]gbP        Paste blockwise (inserting multiple lines in-place,\r\n                        pushing existing text further to the right) [count]\r\n                        times. If there's only a single line to paste and no\r\n                        [count], first query about a separator pattern and\r\n                        un-join the register contents.\r\n\r\n[\"x]g]p, [\"x]g[P  or    Paste linewise (even if yanked text is not a complete\r\n         [\"x]g]P  or    line) [count] times like glp, but adjust the indent\r\n         [\"x]g[p        to the current line (like ]p).\r\n\r\n[\"x]g]]p, [\"x]g]]P      Paste linewise below \/ above, with [count] more indent\r\n                        than the current line.\r\n[\"x]g[[p, [\"x]g[[P      Paste linewise below \/ above, with [count] less indent\r\n                        than the current line.\r\n\r\n[\"x]g>p, [\"x]g>P        Paste lines with [count] times 'shiftwidth' indent.\r\n                        For characterwise and blockwise register contents,\r\n                        paste at the beginning \/ end of the line(s) with the\r\n                        indent before (g>p) \/ after (g>P) each line's\r\n                        content. Multiple characterwise lines are flattened\r\n                        into one as with gcp. The indent of blocks is based\r\n                        on the current line's width; if subsequent lines are\r\n                        longer, and additional indent is added there.\r\n\r\n[\"x]g#p, [\"x]g#P        Paste linewise (even if yanked text is not a complete\r\n                        line) as commented text [count] times. This applies\r\n                        'commentstring' to each individual line, and adjusts\r\n                        the indent (of the entire comment) to the current line\r\n                        (like ]p).\r\n                        This is useful when you want to paste indented text as\r\n                        comments, but avoid the progressive auto-indenting\r\n                        that would normally happen with i_CTRL-R.\r\n\r\n[\"x]gsp, [\"x]gsP        Paste with [count] spaces (characterwise; blockwise:\r\n                        around each line; linewise: flattened like gcp)\r\n                        around the register contents. When pasting before the\r\n                        start or after the end of the line, or with whitespace\r\n                        around the current position, this is added only to the\r\n                        \"other\" side, unless there's emptyness at both sides.\r\n                        (Else, you could just use plain p|\/|P.)\r\n                        Note: To paste with <Tab> instead of spaces (at the\r\n                        beginning or end), you can use g>P \/ g>p if you\r\n                        use tab-indenting or gQP \/ gQp (with the default\r\n                        separator) if 'expandtab' is set.\r\n[\"x]gSp, [\"x]gSP        Paste linewise (like glp) with [count] empty lines\r\n                        around the register contents. When pasting before the\r\n                        start or after the end of the buffer, or with empty\r\n                        lines around the current position, this is added only\r\n                        to the \"other\" side, unless there's emptyness at both\r\n                        sides. (Else, you could just use plain p|\/|P.)\r\n\r\n[\"x]gBp, [\"x]gBP        Paste as a minimal fitting (not rectangular) block\r\n                        with a jagged right edge; i.e. the lines\r\n                        \"foobar\\nhi\\n\" will be pasted as 6-character \"foobar\"\r\n                        in the current line and 2-character \"hi\" in the\r\n                        following one.\r\n                        With [count], each line's content is pasted [count]\r\n                        times.\r\n                        When pasting with gBp at the end of the line,\r\n                        appends at the jagged end of following lines.\r\n                        When pasting with gBP on the first non-indent\r\n                        character (after column 1) of a line, prepends after\r\n                        existing indent of following lines.\r\n                        If there's only a single line to paste and no [count],\r\n                        first query about a separator pattern and un-join the\r\n                        register contents.\r\n\r\n[\"x]gqbp, [\"x]gqbP      Query for a separator string, then paste as a minimal\r\n                        fitting (not rectangular) block (like gBp) with that\r\n                        separator around each line (similar to gqp),\r\n                        omitting the separator at the start and end of the\r\n                        line or when there's already one at that side, like\r\n                        with gsp.\r\n                        With [count], each line's content is pasted [count]\r\n                        times, with the separator between each.\r\n                        When pasting with gqbp at the end of the line,\r\n                        appends (with separator) at the jagged end of\r\n                        following lines.\r\n                        When pasting with gqbP on the first non-indent\r\n                        character (after column 1) of a line, prepends (with\r\n                        separator) after existing indent of following lines.\r\n                        If there's only a single line to paste and no [count],\r\n                        first query about a separator pattern and un-join the\r\n                        register contents.\r\n\r\n[\"x]gQBp, [\"x]gQBP      Paste blockwise with the previously queried (gqbp)\r\n                        separator string (and separator pattern, if single\r\n                        line). Defaults to <Tab> separator\r\n                        g:UnconditionalPaste_Separator.\r\n\r\n[\"x]g,p, [\"x]g,P        Paste characterwise, with each line delimited by \", \"\r\n                        instead of the newline (and indent).\r\n\r\n[\"x]g,ap, [\"x]g,aP      Paste characterwise, with each line delimited by \", \"\r\n[\"x]g,op, [\"x]g,oP      and the last line delimited by \", and\" \/ \", or\" \/ \",\r\n[\"x]g,np, [\"x]g,nP      nor\" (and \"neither\" appended) instead of the newline\r\n                        (and indent).\r\n                        Cp. g:UnconditionalPaste_IsSerialComma for comma\r\n                        placement in front of the conjunction.\r\n\r\n[\"x]g,'p, [\"x]g,'P      Paste characterwise, with each line surrounded by\r\n[\"x]g,\"p, [\"x]g,\"P      single \/ double quotes and delimited by \", \" instead\r\n                        of the newline (and indent).\r\n\r\n[\"x]gqp, [\"x]gqP        Query for a separator string, then paste\r\n                        characterwise, with each line delimited by it.\r\n                        You can also additionally input a prefix (inserted\r\n                        once before the paste) and suffix (once after the\r\n                        paste) as {prefix}^M{separator}^M{suffix} (with ^M\r\n                        entered as <C-V><Enter>). There's another alternative\r\n                        form\r\n           {prefix}^M{element-prefix}^M{separator}^M{element-suffix}^M{suffix}\r\n                        that lets you specify prefixes and suffixes for each\r\n                        element.\r\n                        Examples:\r\n                        \"^M, ^M\"   -> \"foo, bar, baz\"\r\n\r\n                        \"^M\", \"^M\" -> \"foo\", \"bar\", \"baz\"\r\n                        can also be written as:\r\n                        ^M\"^M, ^M\"^M -> \"foo\", \"bar\", \"baz\"\r\n\r\n                        Functions:^M^M - ^M()^M! -> Functions:foo() - bar() - baz()!\r\n\r\n                       <ul>\\n^M  <li>^M\\n^M<\/li>^M\\n<\/ul> -> <ul>\r\n                                                               <li>foo<\/li>\r\n                                                               <li>bar<\/li>\r\n                                                               <li>baz<\/li>\r\n                                                             <\/ul>\r\n\r\n[\"x]gQp, [\"x]gQP        Paste characterwise, with each line delimited by the\r\n                        previously queried (gqp) separator string.\r\n                        Defaults to <Tab> separator\r\n                        g:UnconditionalPaste_JoinSeparator.\r\n\r\n[\"x]gqgp, [\"x]gqgP      Like gqp \/ gQp, but keep indent and surrounding\r\n[\"x]gQgp, [\"x]gQgP      whitespace as-is; just join the lines with the\r\n                        separator (and prefix \/ suffix).\r\n\r\n[\"x]gujp, [\"x]gujP      Query for a separator pattern, un-join the register\r\n                        contents, then paste linewise.\r\n\r\n[\"x]gUJp, [\"x]gUJP      Un-join the register contents on the previously\r\n                        queried (gujp) separator pattern, then paste\r\n                        linewise. Defaults to separation by any whitespace and\r\n                        newlines g:UnconditionalPaste_UnjoinSeparatorPattern.\r\n\r\n[\"x]grp, [\"x]grP        Query for a pattern, and only paste those lines that\r\n                        match the pattern.\r\n[\"x]gr!p, [\"x]gr!P      Query for a pattern, and only paste those lines that\r\n                        do NOT match the pattern.\r\n                        If there's only a single line to paste and no [count],\r\n                        first query about a separator pattern and un-join the\r\n                        register contents. Re-join all matches with the first\r\n                        match of the separator pattern and paste characterwise.\r\n\r\n[\"x]gRp, [\"x]gRP        Only paste those lines that match the previously\r\n                        queried pattern.\r\n[\"x]gR!p, [\"x]gR!P      Only paste those lines that do NOT match the\r\n                        previously queried pattern.\r\n                        Both default to filter out whitespace-only lines\r\n                        g:UnconditionalPaste_GrepPattern\r\n                        g:UnconditionalPaste_InvertedGrepPattern.\r\n                        If there's only a single line to paste and no [count],\r\n                        un-join the register contents first like gUJp.\r\n                        Re-join all matches with the first match of the\r\n                        separator pattern and paste characterwise.\r\n\r\n[\"x]g=p, [\"x]g=P        Query for an expression, apply it to each line\r\n                        (replacing v:val with the current line), and paste the\r\n                        resulting lines. To omit a line, return an empty List\r\n                        ([]) from the expression. To expand a line into\r\n                        several, return a List of lines.\r\n                        If there's only a single line to paste and no [count],\r\n                        first query about a separator pattern and un-join the\r\n                        register contents. Re-join all matches with the first\r\n                        match of the separator pattern and paste characterwise.\r\n\r\n[\"x]g==p, [\"x]g==P      Apply the previously queried expression to each line\r\n                        (replacing v:val with the current line), and paste the\r\n                        resulting lines.\r\n\r\n[\"x]g\\p, [\"x]g\\P        Escape certain characters (global default \/\r\n                        overridable per buffer g:UnconditionalPaste_Escapes;\r\n                        if none or multiple are configured query first, or\r\n                        take [count] to choose among multiples) and paste.\r\n\r\n[\"x]g\\\\p, [\"x]g\\\\P      Escape the same characters as the last time and paste.\r\n\r\n[\"x]gpp, [\"x]gpP        Paste with the first decimal number found on or after\r\n                        the current cursor column (or the overall first\r\n                        number, if no such match, or the last number, if the\r\n                        cursor is at the end of the line) incremented \/\r\n                        decremented by 1.\r\n                        Do this [count] times, with each paste further\r\n                        incremented \/ decremented.\r\n\r\n[\"x]gPp, [\"x]gPP        Paste with all decimal numbers incremented \/\r\n                        decremented by 1.\r\n                        Do this [count] times, with each paste further\r\n                        incremented \/ decremented.\r\n\r\n[\"x]gup, [\"x]guP        Paste with the first alphabetical character of the\r\n                        first \/ [count] word(s) made lowercase.\r\n[\"x]gUp, [\"x]gUP        Paste with the first alphabetical character of the\r\n                        first \/ [count] word(s) made uppercase.\r\n[\"x]g~p, [\"x]g~P        Paste with the first alphabetical character of the\r\n                        first \/ [count] word(s) toggled in case.\r\n\r\n[\"x]ghp, [\"x]ghP        Paste with a queried combination of above mappings.\r\n                        The algorithm is the 1 or 2-character string between\r\n                        the g..p \/ g..P in the mappings. A [count] before\r\n                        ghp applies to each algorithm, you can override \/\r\n                        supply a local [count], too.\r\n                        EXAMPLES\r\n                        - Uppercase a word and paste linewise:\r\n                            ghpUc<Enter>\r\n                        - Unjoin words and paste as quoted list:\r\n                            ghpuj,\"<Enter><Space><Enter>\r\n                        - Paste line 3 times and indent:\r\n                            ghp>3l<Enter>\r\n                        Note: Not all combinations make sense or work\r\n                        correctly.\r\n[\"x]gHp, [\"x]gHP        Paste with the previously queried combination of above\r\n                        mappings again. Defaults to linewise indented paste\r\n                        with empty lines around (gSp + g>p)\r\n                        g:UnconditionalPaste_Combinations.\r\n\r\nCTRL-R CTRL-C {0-9a-z\"%#*+\/:.-}\r\n                        Insert the contents of a register characterwise\r\n                        (newline characters and indent are flattened to\r\n                        spaces).\r\n                        If you have options like 'textwidth', 'formatoptions',\r\n                        or 'autoindent' set, this will influence what will be\r\n                        inserted.\r\n                        Note: If the command-line mapping aborts\r\n                        the command line, try defining\r\n                            :cnoremap <C-c> <C-c>\r\n                       or redefine the mapping.\r\nCTRL-R CTRL-I {0-9a-z\"%#*+\/:.-}\r\n                        Insert the contents of a register inline (inner\r\n                        newline characters and indent are kept, only leading\r\n                        and trailing removed).\r\n\r\nCTRL-R CTRL-C CTRL-C {0-9a-z\"%#*+\/:.-}\r\n                        Insert the contents of a register characterwise; any\r\n                        sequence of whitespace is flattened to a single space,\r\n                        leading and trailing indent removed.\r\nCTRL-R , {0-9a-z\"%#*+\/:.-}\r\n                        Insert the contents of a register characterwise, with\r\n                        each line delimited by \", \" instead of the newline\r\n                        (and indent).\r\nCTRL-R CTRL-Q {0-9a-z\"%#*+\/:.-}\r\n                        Query for a separator string, then insert the contents\r\n                        of a register characterwise, with each line delimited\r\n                        by it. Like gqp, but in insert mode.\r\n\r\nCTRL-R CTRL-Q CTRL-Q {0-9a-z\"%#*+\/:.-}\r\n                        Insert the contents of a register characterwise, with\r\n                        each line delimited by the previously queried (gqp,\r\n                        i_CTRL-R_CTRL-Q) separator string.\r\n\r\nCTRL-R CTRL-Q CTRL-G {0-9a-z\"%#*+\/:.-}\r\nCTRL-R CTRL-Q CTRL-Q CTRL-G CTRL-G {0-9a-z\"%#*+\/:.-}\r\n                        Like CTRL-R CTRL-Q \/ CTRL-R CTRL-Q CTRL-Q, but keep\r\n                        indent and surrounding whitespace as-is; just join the\r\n                        lines with the separator (and prefix \/ suffix).\r\n\r\nCTRL-R CTRL-U {0-9a-z\"%#*+\/:.-}\r\n                        Query for a separator pattern, un-join the contents of\r\n                        a register, then insert it linewise.\r\n\r\nCTRL-R CTRL-U CTRL-U {0-9a-z\"%#*+\/:.-}\r\n                        Un-join the contents of a register on the previously\r\n                        queried (gujp, i_CTRL_R_CTRL-U) pattern, then\r\n                        insert it linewise.\r\n\r\nCTRL-R CTRL-\\ {0-9a-z\"%#*+\/:.-}\r\n                        Escape certain characters (global default \/\r\n                        overridable per buffer g:UnconditionalPaste_Escapes;\r\n                        if none or multiple are configured query first) and\r\n                        insert.\r\nCTRL-R CTRL-\\ CTRL-\\ {0-9a-z\"%#*+\/:.-}\r\n                        Escape the same characters as the last time and\r\n                        insert.\r\n\r\nCTRL-R ~ {0-9a-z\"%#*+\/:.-}\r\n                        Insert the contents of a register, toggling the case\r\n                        of the first alphabetical character of the first word.\r\n                        Like g~p \/ g~p, but in insert mode.\r\n\r\nCTRL-R CTRL-H {0-9a-z\"%#*+\/:.-}\r\n                        Query for a combination of UnconditionalPaste\r\n                        mappings, apply those to the contents of the register,\r\n                        and insert the result.\r\n\r\nCTRL-R CTRL-H CTRL-H {0-9a-z\"%#*+\/:.-}\r\n                        Apply the last queried combination of\r\n                        UnconditionalPaste mappings to the contents of the\r\n                        register again, and insert the result.","4":"DESCRIPTION\r\nIf you're like me, you occasionally do a linewise yank, and then want to\r\ninsert that yanked text in the middle of some other line (or vice versa).\r\nThe mappings defined by this plugin will allow you to do a character-, line-,\r\nor block-wise paste no matter how you yanked the text, both from normal and\r\ninsert mode.\r\n\r\nOften, the register contents aren't quite in the form you need them. Maybe you\r\nneed to convert yanked lines to comma-separated arguments, maybe join the\r\nlines with another separator, maybe the reverse: un-joining a single line on\r\nsome pattern to yield multiple lines. Though you can do the manipulation after\r\npasting, this plugin offers shortcut mappings for these actions, which are\r\nespecially helpful when you need to repeat the paste multiple times.\r\n\r\nSOURCE\r\nBased on vimtip #1199 by cory,\r\n    http:\/\/vim.wikia.com\/wiki\/Unconditional_linewise_or_characterwise_paste\r\n\r\nRELATED WORKS\r\n- whitespaste.vim (vimscript #4351) automatically removes blank lines around\r\n  linewise contents, and condenses inner lines to a single one. By default, it\r\n  remaps p \/ P, but this can be changed.\r\n\r\nUSAGE\r\n[\"x]gcp, [\"x]gcP        Paste characterwise (inner newline characters and\r\n                        indent are flattened to a single space, leading and\r\n                        trailing removed) [count] times.\r\n\r\n[\"x]gcip, [\"x]gciP      Paste inline (inner newline characters and indent are\r\n                        kept, only leading and trailing removed) [count]\r\n                        times.\r\n\r\n[\"x]gcgp, [\"x]gcgP      Paste joined (like gJ); indent and surrounding\r\n                        whitespace is kept as-is, [count] times.\r\n\r\n[\"x]gCp, [\"x]gCP        Paste characterwise; any sequence of whitespace is\r\n                        flattened to a single space, leading and trailing\r\n                        indent removed, [count] times.\r\n\r\n[\"x]glp, [\"x]glP        Paste linewise (even if yanked text is not a complete\r\n                        line) [count] times.\r\n\r\n[\"x]gbp, [\"x]gbP        Paste blockwise (inserting multiple lines in-place,\r\n                        pushing existing text further to the right) [count]\r\n                        times. If there's only a single line to paste and no\r\n                        [count], first query about a separator pattern and\r\n                        un-join the register contents.\r\n\r\n[\"x]g]p, [\"x]g[P  or    Paste linewise (even if yanked text is not a complete\r\n         [\"x]g]P  or    line) [count] times like glp, but adjust the indent\r\n         [\"x]g[p        to the current line (like ]p).\r\n\r\n[\"x]g]]p, [\"x]g]]P      Paste linewise below \/ above, with [count] more indent\r\n                        than the current line.\r\n[\"x]g[[p, [\"x]g[[P      Paste linewise below \/ above, with [count] less indent\r\n                        than the current line.\r\n\r\n[\"x]g>p, [\"x]g>P        Paste lines with [count] times 'shiftwidth' indent.\r\n                        For characterwise and blockwise register contents,\r\n                        paste at the beginning \/ end of the line(s) with the\r\n                        indent before (g>p) \/ after (g>P) each line's\r\n                        content. Multiple characterwise lines are flattened\r\n                        into one as with gcp. The indent of blocks is based\r\n                        on the current line's width; if subsequent lines are\r\n                        longer, and additional indent is added there.\r\n\r\n[\"x]g#p, [\"x]g#P        Paste linewise (even if yanked text is not a complete\r\n                        line) as commented text [count] times. This applies\r\n                        'commentstring' to each individual line, and adjusts\r\n                        the indent (of the entire comment) to the current line\r\n                        (like ]p).\r\n                        This is useful when you want to paste indented text as\r\n                        comments, but avoid the progressive auto-indenting\r\n                        that would normally happen with i_CTRL-R.\r\n\r\n[\"x]gsp, [\"x]gsP        Paste with [count] spaces (characterwise; blockwise:\r\n                        around each line; linewise: flattened like gcp)\r\n                        around the register contents. When pasting before the\r\n                        start or after the end of the line, or with whitespace\r\n                        around the current position, this is added only to the\r\n                        \"other\" side, unless there's emptyness at both sides.\r\n                        (Else, you could just use plain p|\/|P.)\r\n                        Note: To paste with <Tab> instead of spaces (at the\r\n                        beginning or end), you can use g>P \/ g>p if you\r\n                        use tab-indenting or gQP \/ gQp (with the default\r\n                        separator) if 'expandtab' is set.\r\n[\"x]gSp, [\"x]gSP        Paste linewise (like glp) with [count] empty lines\r\n                        around the register contents. When pasting before the\r\n                        start or after the end of the buffer, or with empty\r\n                        lines around the current position, this is added only\r\n                        to the \"other\" side, unless there's emptyness at both\r\n                        sides. (Else, you could just use plain p|\/|P.)\r\n\r\n[\"x]gBp, [\"x]gBP        Paste as a minimal fitting (not rectangular) block\r\n                        with a jagged right edge; i.e. the lines\r\n                        \"foobar\\nhi\\n\" will be pasted as 6-character \"foobar\"\r\n                        in the current line and 2-character \"hi\" in the\r\n                        following one.\r\n                        With [count], each line's content is pasted [count]\r\n                        times.\r\n                        When pasting with gBp at the end of the line,\r\n                        appends at the jagged end of following lines.\r\n                        When pasting with gBP on the first non-indent\r\n                        character (after column 1) of a line, prepends after\r\n                        existing indent of following lines.\r\n                        If there's only a single line to paste and no [count],\r\n                        first query about a separator pattern and un-join the\r\n                        register contents.\r\n\r\n[\"x]gqbp, [\"x]gqbP      Query for a separator string, then paste as a minimal\r\n                        fitting (not rectangular) block (like gBp) with that\r\n                        separator around each line (similar to gqp),\r\n                        omitting the separator at the start and end of the\r\n                        line or when there's already one at that side, like\r\n                        with gsp.\r\n                        With [count], each line's content is pasted [count]\r\n                        times, with the separator between each.\r\n                        When pasting with gqbp at the end of the line,\r\n                        appends (with separator) at the jagged end of\r\n                        following lines.\r\n                        When pasting with gqbP on the first non-indent\r\n                        character (after column 1) of a line, prepends (with\r\n                        separator) after existing indent of following lines.\r\n                        If there's only a single line to paste and no [count],\r\n                        first query about a separator pattern and un-join the\r\n                        register contents.\r\n\r\n[\"x]gQBp, [\"x]gQBP      Paste blockwise with the previously queried (gqbp)\r\n                        separator string (and separator pattern, if single\r\n                        line). Defaults to <Tab> separator\r\n                        g:UnconditionalPaste_Separator.\r\n\r\n[\"x]g,p, [\"x]g,P        Paste characterwise, with each line delimited by \", \"\r\n                        instead of the newline (and indent).\r\n\r\n[\"x]g,ap, [\"x]g,aP      Paste characterwise, with each line delimited by \", \"\r\n[\"x]g,op, [\"x]g,oP      and the last line delimited by \", and\" \/ \", or\" \/ \",\r\n[\"x]g,np, [\"x]g,nP      nor\" (and \"neither\" appended) instead of the newline\r\n                        (and indent).\r\n                        Cp. g:UnconditionalPaste_IsSerialComma for comma\r\n                        placement in front of the conjunction.\r\n\r\n[\"x]g,'p, [\"x]g,'P      Paste characterwise, with each line surrounded by\r\n[\"x]g,\"p, [\"x]g,\"P      single \/ double quotes and delimited by \", \" instead\r\n                        of the newline (and indent).\r\n\r\n[\"x]gqp, [\"x]gqP        Query for a separator string, then paste\r\n                        characterwise, with each line delimited by it.\r\n                        You can also additionally input a prefix (inserted\r\n                        once before the paste) and suffix (once after the\r\n                        paste) as {prefix}^M{separator}^M{suffix} (with ^M\r\n                        entered as <C-V><Enter>). There's another alternative\r\n                        form\r\n           {prefix}^M{element-prefix}^M{separator}^M{element-suffix}^M{suffix}\r\n                        that lets you specify prefixes and suffixes for each\r\n                        element.\r\n                        Examples:\r\n                        \"^M, ^M\"   -> \"foo, bar, baz\"\r\n\r\n                        \"^M\", \"^M\" -> \"foo\", \"bar\", \"baz\"\r\n                        can also be written as:\r\n                        ^M\"^M, ^M\"^M -> \"foo\", \"bar\", \"baz\"\r\n\r\n                        Functions:^M^M - ^M()^M! -> Functions:foo() - bar() - baz()!\r\n\r\n                       <ul>\\n^M  <li>^M\\n^M<\/li>^M\\n<\/ul> -> <ul>\r\n                                                               <li>foo<\/li>\r\n                                                               <li>bar<\/li>\r\n                                                               <li>baz<\/li>\r\n                                                             <\/ul>\r\n\r\n[\"x]gQp, [\"x]gQP        Paste characterwise, with each line delimited by the\r\n                        previously queried (gqp) separator string.\r\n                        Defaults to <Tab> separator\r\n                        g:UnconditionalPaste_JoinSeparator.\r\n\r\n[\"x]gqgp, [\"x]gqgP      Like gqp \/ gQp, but keep indent and surrounding\r\n[\"x]gQgp, [\"x]gQgP      whitespace as-is; just join the lines with the\r\n                        separator (and prefix \/ suffix).\r\n\r\n[\"x]gujp, [\"x]gujP      Query for a separator pattern, un-join the register\r\n                        contents, then paste linewise.\r\n\r\n[\"x]gUJp, [\"x]gUJP      Un-join the register contents on the previously\r\n                        queried (gujp) separator pattern, then paste\r\n                        linewise. Defaults to separation by any whitespace and\r\n                        newlines g:UnconditionalPaste_UnjoinSeparatorPattern.\r\n\r\n[\"x]grp, [\"x]grP        Query for a pattern, and only paste those lines that\r\n                        match the pattern.\r\n[\"x]gr!p, [\"x]gr!P      Query for a pattern, and only paste those lines that\r\n                        do NOT match the pattern.\r\n                        If there's only a single line to paste and no [count],\r\n                        first query about a separator pattern and un-join the\r\n                        register contents. Re-join all matches with the first\r\n                        match of the separator pattern and paste characterwise.\r\n\r\n[\"x]gRp, [\"x]gRP        Only paste those lines that match the previously\r\n                        queried pattern.\r\n[\"x]gR!p, [\"x]gR!P      Only paste those lines that do NOT match the\r\n                        previously queried pattern.\r\n                        Both default to filter out whitespace-only lines\r\n                        g:UnconditionalPaste_GrepPattern\r\n                        g:UnconditionalPaste_InvertedGrepPattern.\r\n                        If there's only a single line to paste and no [count],\r\n                        un-join the register contents first like gUJp.\r\n                        Re-join all matches with the first match of the\r\n                        separator pattern and paste characterwise.\r\n\r\n[\"x]g=p, [\"x]g=P        Query for an expression, apply it to each line\r\n                        (replacing v:val with the current line), and paste the\r\n                        resulting lines. To omit a line, return an empty List\r\n                        ([]) from the expression. To expand a line into\r\n                        several, return a List of lines.\r\n                        If there's only a single line to paste and no [count],\r\n                        first query about a separator pattern and un-join the\r\n                        register contents. Re-join all matches with the first\r\n                        match of the separator pattern and paste characterwise.\r\n\r\n[\"x]g==p, [\"x]g==P      Apply the previously queried expression to each line\r\n                        (replacing v:val with the current line), and paste the\r\n                        resulting lines.\r\n\r\n[\"x]g\\p, [\"x]g\\P        Escape certain characters (global default \/\r\n                        overridable per buffer g:UnconditionalPaste_Escapes;\r\n                        if none or multiple are configured query first, or\r\n                        take [count] to choose among multiples) and paste.\r\n\r\n[\"x]g\\\\p, [\"x]g\\\\P      Escape the same characters as the last time and paste.\r\n\r\n[\"x]gpp, [\"x]gpP        Paste with the first decimal number found on or after\r\n                        the current cursor column (or the overall first\r\n                        number, if no such match, or the last number, if the\r\n                        cursor is at the end of the line) incremented \/\r\n                        decremented by 1.\r\n                        Do this [count] times, with each paste further\r\n                        incremented \/ decremented.\r\n\r\n[\"x]gPp, [\"x]gPP        Paste with all decimal numbers incremented \/\r\n                        decremented by 1.\r\n                        Do this [count] times, with each paste further\r\n                        incremented \/ decremented.\r\n\r\n[\"x]gup, [\"x]guP        Paste with the first alphabetical character of the\r\n                        first \/ [count] word(s) made lowercase.\r\n[\"x]gUp, [\"x]gUP        Paste with the first alphabetical character of the\r\n                        first \/ [count] word(s) made uppercase.\r\n[\"x]g~p, [\"x]g~P        Paste with the first alphabetical character of the\r\n                        first \/ [count] word(s) toggled in case.\r\n\r\n[\"x]ghp, [\"x]ghP        Paste with a queried combination of above mappings.\r\n                        The algorithm is the 1 or 2-character string between\r\n                        the g..p \/ g..P in the mappings. A [count] before\r\n                        ghp applies to each algorithm, you can override \/\r\n                        supply a local [count], too.\r\n                        EXAMPLES\r\n                        - Uppercase a word and paste linewise:\r\n                            ghpUc<Enter>\r\n                        - Unjoin words and paste as quoted list:\r\n                            ghpuj,\"<Enter><Space><Enter>\r\n                        - Paste line 3 times and indent:\r\n                            ghp>3l<Enter>\r\n                        Note: Not all combinations make sense or work\r\n                        correctly.\r\n[\"x]gHp, [\"x]gHP        Paste with the previously queried combination of above\r\n                        mappings again. Defaults to linewise indented paste\r\n                        with empty lines around (gSp + g>p)\r\n                        g:UnconditionalPaste_Combinations.\r\n\r\nCTRL-R CTRL-C {0-9a-z\"%#*+\/:.-}\r\n                        Insert the contents of a register characterwise\r\n                        (newline characters and indent are flattened to\r\n                        spaces).\r\n                        If you have options like 'textwidth', 'formatoptions',\r\n                        or 'autoindent' set, this will influence what will be\r\n                        inserted.\r\n                        Note: If the command-line mapping aborts\r\n                        the command line, try defining\r\n                            :cnoremap <C-c> <C-c>\r\n                       or redefine the mapping.\r\nCTRL-R CTRL-I {0-9a-z\"%#*+\/:.-}\r\n                        Insert the contents of a register inline (inner\r\n                        newline characters and indent are kept, only leading\r\n                        and trailing removed).\r\n\r\nCTRL-R CTRL-C CTRL-C {0-9a-z\"%#*+\/:.-}\r\n                        Insert the contents of a register characterwise; any\r\n                        sequence of whitespace is flattened to a single space,\r\n                        leading and trailing indent removed.\r\nCTRL-R , {0-9a-z\"%#*+\/:.-}\r\n                        Insert the contents of a register characterwise, with\r\n                        each line delimited by \", \" instead of the newline\r\n                        (and indent).\r\nCTRL-R CTRL-Q {0-9a-z\"%#*+\/:.-}\r\n                        Query for a separator string, then insert the contents\r\n                        of a register characterwise, with each line delimited\r\n                        by it. Like gqp, but in insert mode.\r\n\r\nCTRL-R CTRL-Q CTRL-Q {0-9a-z\"%#*+\/:.-}\r\n                        Insert the contents of a register characterwise, with\r\n                        each line delimited by the previously queried (gqp,\r\n                        i_CTRL-R_CTRL-Q) separator string.\r\n\r\nCTRL-R CTRL-Q CTRL-G {0-9a-z\"%#*+\/:.-}\r\nCTRL-R CTRL-Q CTRL-Q CTRL-G CTRL-G {0-9a-z\"%#*+\/:.-}\r\n                        Like CTRL-R CTRL-Q \/ CTRL-R CTRL-Q CTRL-Q, but keep\r\n                        indent and surrounding whitespace as-is; just join the\r\n                        lines with the separator (and prefix \/ suffix).\r\n\r\nCTRL-R CTRL-U {0-9a-z\"%#*+\/:.-}\r\n                        Query for a separator pattern, un-join the contents of\r\n                        a register, then insert it linewise.\r\n\r\nCTRL-R CTRL-U CTRL-U {0-9a-z\"%#*+\/:.-}\r\n                        Un-join the contents of a register on the previously\r\n                        queried (gujp, i_CTRL_R_CTRL-U) pattern, then\r\n                        insert it linewise.\r\n\r\nCTRL-R CTRL-\\ {0-9a-z\"%#*+\/:.-}\r\n                        Escape certain characters (global default \/\r\n                        overridable per buffer g:UnconditionalPaste_Escapes;\r\n                        if none or multiple are configured query first) and\r\n                        insert.\r\nCTRL-R CTRL-\\ CTRL-\\ {0-9a-z\"%#*+\/:.-}\r\n                        Escape the same characters as the last time and\r\n                        insert.\r\n\r\nCTRL-R ~ {0-9a-z\"%#*+\/:.-}\r\n                        Insert the contents of a register, toggling the case\r\n                        of the first alphabetical character of the first word.\r\n                        Like g~p \/ g~p, but in insert mode.\r\n\r\nCTRL-R CTRL-H {0-9a-z\"%#*+\/:.-}\r\n                        Query for a combination of UnconditionalPaste\r\n                        mappings, apply those to the contents of the register,\r\n                        and insert the result.\r\n\r\nCTRL-R CTRL-H CTRL-H {0-9a-z\"%#*+\/:.-}\r\n                        Apply the last queried combination of\r\n                        UnconditionalPaste mappings to the contents of the\r\n                        register again, and insert the result.","install_details":"INSTALLATION\r\nThe code is hosted in a Git repo at\r\n    https:\/\/github.com\/inkarkat\/vim-UnconditionalPaste\r\nYou can use your favorite plugin manager, or \"git clone\" into a directory used\r\nfor Vim packages. Releases are on the \"stable\" branch, the latest unstable\r\ndevelopment snapshot on \"master\".\r\n\r\nThis script is also packaged as a vimball. If you have the \"gunzip\"\r\ndecompressor in your PATH, simply edit the *.vmb.gz package in Vim; otherwise,\r\ndecompress the archive first, e.g. using WinZip. Inside Vim, install by\r\nsourcing the vimball or via the :UseVimball command.\r\n    vim UnconditionalPaste*.vmb.gz\r\n    :so %\r\nTo uninstall, use the :RmVimball command.\r\n\r\nDEPENDENCIES\r\n- Requires Vim 7.0 or higher.\r\n- Requires the ingo-library.vim plugin (vimscript #4433), version 1.026 or\r\n  higher.\r\n- repeat.vim (vimscript #2136) plugin (optional)\r\n- AlignFromCursor.vim plugin (vimscript #4155), version 2.02 or higher\r\n  (optional).\r\n\r\nCONFIGURATION\r\nFor a permanent configuration, put the following commands into your vimrc:\r\n\r\nThe default separator string for the gQBp mapping is a <Tab> character; to\r\npreset another one (it will be overridden by gqbp), use:\r\n    let g:UnconditionalPaste_Separator = 'text'\r\n\r\nThe default separator string for the gQp and i_CTRL-R_CTRL-Q_CTRL-Q\r\nmappings is a <Tab> character; to preset another one (it will be overridden by\r\ngqp and i_CTRL-R_CTRL-Q), use:\r\n    let g:UnconditionalPaste_JoinSeparator = 'text'\r\n\r\nThe default separator pattern for the gUJp and i_CTRL-R_CTRL-U_CTRL-U\r\nmappings matches any whitespace and newlines (i.e. it will get rid of empty\r\nlines); to preset another one (it will be overridden by gujp and\r\ni_CTRL-R_CTRL-U), use:\r\n    let g:UnconditionalPaste_UnjoinSeparatorPattern = '-'\r\n\r\nThe default pattern for the gRp and gR!p mappings filter out\r\nwhitespace-only lines; to preset another one (will be overridden by grp \/\r\ngr!p), use:\r\n    let g:UnconditionalPaste_GrepPattern = 'pattern'\r\n    let g:UnconditionalPaste_InvertedGrepPattern = 'pattern'\r\n\r\nThe g>p \/ g>P mappings uses the AlignFromCursor.vim plugin's\r\nfunctionality (if installed) to only affect the whitespace between the\r\noriginal text and the pasted line. If you want to always :retab! all the\r\nwhitespace in the entire line, disable this via:\r\n    let g:UnconditionalPaste_IsFullLineRetabOnShift = 1\r\n\r\nBy default, the g,ap, g,op, and g,np mappings use a comma immediately\r\nbefore the coordinating conjunction (also known as \"Oxford comma\"; unless\r\nexactly two lines are pasted); to turn this off:\r\n    let g:UnconditionalPaste_IsSerialComma = 0\r\n\r\nBy default, the gsp mapping does not insert a space on a side that already\r\nhas whitespace. You can make other separators (e.g. quotes) be considered as\r\nexisting space by tweaking the regular expression in :\r\n    let g:UnconditionalPaste_EmptySeparatorPattern = '\\s'\r\nFor some cases (like avoiding a space when pasting inside a {...}) it matters\r\nwhether the separator is before or after the paste. Instead of a single\r\npattern, you can pass a List of two patterns there; the first one applies to\r\nseparators before the paste (so it could match a { if you don't want a space\r\nwhen pasting after it, but you do want a space when pasting before it), the\r\nsecond applies to separators after the paste:\r\n    let g:UnconditionalPaste_EmptySeparatorPattern = ['[[:space:]{]', '[[:space:]}]']\r\n\r\nBy default, the gSp mapping does not add an empty line on a side that\r\nalready just consists of whitespace. You can make other lines be considered\r\nempty by tweaking the regular expression:\r\n    let g:UnconditionalPaste_EmptyLinePattern = '^\\s*$'\r\nFor some cases (like avoiding an empty line when pasting inside a { ... }\r\nblock) it matters whether the line is above or below the paste. Instead of a\r\nsingle pattern, you can pass a List of two patterns there; the first one\r\napplies to lines above the paste (so it could match a { if you don't want an\r\nempty line when pasting after it, but you do want an empty line when pasting\r\nbefore it), the second applies to lines below the paste:\r\n    let g:UnconditionalPaste_EmptyLinePattern = ['^\\s*{\\?$', '^\\s*}\\?$']\r\n\r\nBy default, the g\\p and i_CTRL-R_CTRL-\\ mappings escape backslashes. You\r\ncan change that (e.g. to also escape double quotes), or add more variants:\r\n    let g:UnconditionalPaste_Escapes = [{\r\n    \\   'name': 'dquote',\r\n    \\   'pattern': '[\\\"]',\r\n    \\   'replacement': '\\\\&'\r\n    \\}, ...]\r\nEach configuration object attributes is optional; alternatively, you can also\r\nspecify an expression (using v:val), or a Funcref that takes and returns a\r\nString:\r\n    let g:UnconditionalPaste_Escapes = [\r\n    \\   {'Replacer': 'tr(v:val, \"o\", \"X\")'},\r\n    \\   {'Replacer': function('MyReplacer')},\r\n    \\...]\r\nThe buffer-local b:UnconditionalPaste_Escapes overrides that for particular\r\nbuffers (filetypes if placed in a ftplugin).\r\n\r\nThis stores the last replacement used for g\\\\p and i_CTRL_R_CTRL-\\.\r\nIt is initialized with the first escape from the above configuration \/ entered\r\n\/ selected escape.\r\n\r\nThe default combination used for the gHp and i_CTRL-R_CTRL-H_CTRL-H\r\nmappings. Must be a List of 1 or 2-character strings between the g..p \/ g..P\r\nin the mappings; best obtained by selecting the desired algorithms via ghp\r\nonce and then grabbing the variable value:\r\n    let g:UnconditionalPaste_Combinations = ['U', ',\"', 's']\r\n\r\nIf you want no or only a few of the available mappings, you can completely\r\nturn off the creation of the default mappings by defining:\r\n    :let g:UnconditionalPaste_no_mappings = 1\r\nThis saves you from mapping dummy keys to all unwanted mapping targets.\r\n\r\nIf you want to use different mappings (e.g. starting with <Leader>), map your\r\nkeys to the <Plug>UnconditionalPaste... mapping targets _before_ sourcing this\r\nscript (e.g. in your vimrc):\r\n    nmap <Leader>Pc <Plug>UnconditionalPasteCharBefore\r\n    nmap <Leader>pc <Plug>UnconditionalPasteCharAfter\r\n    nmap <Leader>Pn <Plug>UnconditionalPasteInlinedBefore\r\n    nmap <Leader>pn <Plug>UnconditionalPasteInlinedAfter\r\n    nmap <Leader>Pj <Plug>UnconditionalPasteJustJoinedBefore\r\n    nmap <Leader>pj <Plug>UnconditionalPasteJustJoinedAfter\r\n    nmap <Leader>PC <Plug>UnconditionalPasteCharCondensedBefore\r\n    nmap <Leader>pC <Plug>UnconditionalPasteCharCondensedAfter\r\n    nmap <Leader>Pl <Plug>UnconditionalPasteLineBefore\r\n    nmap <Leader>pl <Plug>UnconditionalPasteLineAfter\r\n    nmap <Leader>Pb <Plug>UnconditionalPasteBlockBefore\r\n    nmap <Leader>pb <Plug>UnconditionalPasteBlockAfter\r\n    nmap <Leader>Pi <Plug>UnconditionalPasteIndentedBefore\r\n    nmap <Leader>pi <Plug>UnconditionalPasteIndentedAfter\r\n    nmap <Leader>Pm <Plug>UnconditionalPasteMoreIndentBefore\r\n    nmap <Leader>pm <Plug>UnconditionalPasteMoreIndentAfter\r\n    nmap <Leader>Pl <Plug>UnconditionalPasteLessIndentBefore\r\n    nmap <Leader>pl <Plug>UnconditionalPasteLessIndentAfter\r\n    nmap <Leader>P> <Plug>UnconditionalPasteShiftedBefore\r\n    nmap <Leader>p> <Plug>UnconditionalPasteShiftedAfter\r\n    nmap <Leader>P# <Plug>UnconditionalPasteCommentedBefore\r\n    nmap <Leader>p# <Plug>UnconditionalPasteCommentedAfter\r\n    nmap <Leader>Ps <Plug>UnconditionalPasteSpacedBefore\r\n    nmap <Leader>ps <Plug>UnconditionalPasteSpacedAfter\r\n    nmap <Leader>PS <Plug>UnconditionalPasteParagraphedBefore\r\n    nmap <Leader>pS <Plug>UnconditionalPasteParagraphedAfter\r\n    nmap <Leader>PB <Plug>UnconditionalPasteJaggedBefore\r\n    nmap <Leader>pB <Plug>UnconditionalPasteJaggedAfter\r\n    nmap <Leader>Pd <Plug>UnconditionalPasteDelimitedBefore\r\n    nmap <Leader>pd <Plug>UnconditionalPasteDelimitedAfter\r\n    nmap <Leader>PD <Plug>UnconditionalPasteRecallDelimitedBefore\r\n    nmap <Leader>pD <Plug>UnconditionalPasteRecallDelimitedAfter\r\n    nmap <Leader>P, <Plug>UnconditionalPasteCommaBefore\r\n    nmap <Leader>p, <Plug>UnconditionalPasteCommaAfter\r\n    nmap <Leader>P' <Plug>UnconditionalPasteCommaSingleQuoteBefore\r\n    nmap <Leader>p' <Plug>UnconditionalPasteCommaSingleQuoteAfter\r\n    nmap <Leader>P\" <Plug>UnconditionalPasteCommaDoubleQuoteBefore\r\n    nmap <Leader>p\" <Plug>UnconditionalPasteCommaDoubleQuoteAfter\r\n    nmap <Leader>P,n <<Plug>UnconditionalPasteCommaNorBefore\r\n    nmap <Leader>p,n <Plug>UnconditionalPasteCommaNorAfter\r\n    nmap <Leader>P,o <Plug>UnconditionalPasteCommaOrBefore\r\n    nmap <Leader>p,o <Plug>UnconditionalPasteCommaOrAfter\r\n    nmap <Leader>P,a <Plug>UnconditionalPasteCommaAndBefore\r\n    nmap <Leader>p,a <Plug>UnconditionalPasteCommaAndAfter\r\n    nmap <Leader>Pq <Plug>UnconditionalPasteQueriedBefore\r\n    nmap <Leader>pq <Plug>UnconditionalPasteQueriedAfter\r\n    nmap <Leader>PQ <Plug>UnconditionalPasteRecallQueriedBefore\r\n    nmap <Leader>pQ <Plug>UnconditionalPasteRecallQueriedAfter\r\n    nmap <Leader>Pgq <Plug>UnconditionalPasteQueriedJoinedBefore\r\n    nmap <Leader>pgq <Plug>UnconditionalPasteQueriedJoinedAfter\r\n    nmap <Leader>PgQ <Plug>UnconditionalPasteRecallQueriedJoinedBefore\r\n    nmap <Leader>pgQ <Plug>UnconditionalPasteRecallQueriedJoinedAfter\r\n    nmap <Leader>Puj <Plug>UnconditionalPasteUnjoinBefore\r\n    nmap <Leader>puj <Plug>UnconditionalPasteUnjoinAfter\r\n    nmap <Leader>PUJ <Plug>UnconditionalPasteRecallUnjoinBefore\r\n    nmap <Leader>pUJ <Plug>UnconditionalPasteRecallUnjoinAfter\r\n    nmap <Leader>Pr <Plug>UnconditionalPasteGrepBefore\r\n    nmap <Leader>pr <Plug>UnconditionalPasteGrepAfter\r\n    nmap <Leader>P! <Plug>UnconditionalPasteInvertedGrepBefore\r\n    nmap <Leader>p! <Plug>UnconditionalPasteInvertedGrepAfter\r\n    nmap <Leader>PR <Plug>UnconditionalPasteRecallGrepBefore\r\n    nmap <Leader>pR <Plug>UnconditionalPasteRecallGrepAfter\r\n    nmap <Leader>P1 <Plug>UnconditionalPasteRecallInvertedGrepBefore\r\n    nmap <Leader>p1 <Plug>UnconditionalPasteRecallInvertedGrepAfter\r\n    nmap <Leader>Pe <Plug>UnconditionalPasteExpressionBefore\r\n    nmap <Leader>pe <Plug>UnconditionalPasteExpressionAfter\r\n    nmap <Leader>PE <Plug>UnconditionalPasteRecallExpressionBefore\r\n    nmap <Leader>pE <Plug>UnconditionalPasteRecallExpressionAfter\r\n    nmap <Leader>Px <Plug>UnconditionalPasteEscapeBefore\r\n    nmap <Leader>px <Plug>UnconditionalPasteEscapeAfter\r\n    nmap <Leader>PX <Plug>UnconditionalPasteRecallEscapeBefore\r\n    nmap <Leader>pX <Plug>UnconditionalPasteRecallEscapeAfter\r\n    nmap <Leader>Pp <Plug>UnconditionalPastePlusBefore\r\n    nmap <Leader>pp <Plug>UnconditionalPastePlusAfter\r\n    nmap <Leader>PP <Plug>UnconditionalPasteGPlusBefore\r\n    nmap <Leader>pP <Plug>UnconditionalPasteGPlusAfter\r\n    nmap <Leader>Pu <Plug>UnconditionalPasteLowercaseBefore\r\n    nmap <Leader>pu <Plug>UnconditionalPasteLowercaseAfter\r\n    nmap <Leader>PU <Plug>UnconditionalPasteUppercaseBefore\r\n    nmap <Leader>pU <Plug>UnconditionalPasteUppercaseAfter\r\n    nmap <Leader>pt <Plug>UnconditionalPasteTogglecaseBefore\r\n    nmap <Leader>Pt <Plug>UnconditionalPasteTogglecaseAfter\r\n    nmap <Leader>Ph <Plug>UnconditionalPasteCombinatorialBefore\r\n    nmap <Leader>ph <Plug>UnconditionalPasteCombinatorialAfter\r\n    nmap <Leader>PH <Plug>UnconditionalPasteRecallCombinatorialBefore\r\n    nmap <Leader>pH <Plug>UnconditionalPasteRecallCombinatorialAfter\r\n\r\n    imap <C-G>c <Plug>UnconditionalPasteCharI\r\n    imap <C-G>n <Plug>UnconditionalPasteInlinedI\r\n    imap <C-G>C <Plug>UnconditionalPasteCharCondensedI\r\n    imap <C-G>, <Plug>UnconditionalPasteCommaI\r\n    imap <C-G>q <Plug>UnconditionalPasteQueriedI\r\n    imap <C-G>Q <Plug>UnconditionalPasteRecallQueriedI\r\n    imap <C-G>j <Plug>UnconditionalPasteQueriedJoinedI\r\n    imap <C-G>J <Plug>UnconditionalPasteRecallQueriedJoinedI\r\n    imap <C-G>u <Plug>UnconditionalPasteUnjoinI\r\n    imap <C-G>U <Plug>UnconditionalPasteRecallUnjoinI\r\n    imap <C-G>x <Plug>UnconditionalPasteEscapeI\r\n    imap <C-G>X <Plug>UnconditionalPasteRecallEscapeI\r\n    imap <C-G>~ <Plug>UnconditionalPasteTogglecaseI\r\n    imap <C-G>h <Plug>UnconditionalPasteCombinatorialI\r\n    imap <C-G>H <Plug>UnconditionalPasteRecallCombinatorialI\r\n\r\n    cmap <C-G>c <Plug>UnconditionalPasteCharI\r\n    cmap <C-G>n <Plug>UnconditionalPasteInlinedI\r\n    cmap <C-G>C <Plug>UnconditionalPasteCharCondensedI\r\n    cmap <C-G>, <Plug>UnconditionalPasteCommaI\r\n    cmap <C-G>q <Plug>UnconditionalPasteQueriedI\r\n    cmap <C-G>Q <Plug>UnconditionalPasteRecallQueriedI\r\n    cmap <C-G>j <Plug>UnconditionalPasteQueriedJoinedI\r\n    cmap <C-G>J <Plug>UnconditionalPasteRecallQueriedJoinedI\r\n    cmap <C-G>u <Plug>UnconditionalPasteUnjoinI\r\n    cmap <C-G>U <Plug>UnconditionalPasteRecallUnjoinI\r\n    cmap <C-G>x <Plug>UnconditionalPasteEscapeI\r\n    cmap <C-G>X <Plug>UnconditionalPasteRecallEscapeI\r\n    cmap <C-G>~ <Plug>UnconditionalPasteTogglecaseI\r\n    cmap <C-G>h <Plug>UnconditionalPasteCombinatorialI\r\n    cmap <C-G>H <Plug>UnconditionalPasteRecallCombinatorialI","5":"INSTALLATION\r\nThe code is hosted in a Git repo at\r\n    https:\/\/github.com\/inkarkat\/vim-UnconditionalPaste\r\nYou can use your favorite plugin manager, or \"git clone\" into a directory used\r\nfor Vim packages. Releases are on the \"stable\" branch, the latest unstable\r\ndevelopment snapshot on \"master\".\r\n\r\nThis script is also packaged as a vimball. If you have the \"gunzip\"\r\ndecompressor in your PATH, simply edit the *.vmb.gz package in Vim; otherwise,\r\ndecompress the archive first, e.g. using WinZip. Inside Vim, install by\r\nsourcing the vimball or via the :UseVimball command.\r\n    vim UnconditionalPaste*.vmb.gz\r\n    :so %\r\nTo uninstall, use the :RmVimball command.\r\n\r\nDEPENDENCIES\r\n- Requires Vim 7.0 or higher.\r\n- Requires the ingo-library.vim plugin (vimscript #4433), version 1.026 or\r\n  higher.\r\n- repeat.vim (vimscript #2136) plugin (optional)\r\n- AlignFromCursor.vim plugin (vimscript #4155), version 2.02 or higher\r\n  (optional).\r\n\r\nCONFIGURATION\r\nFor a permanent configuration, put the following commands into your vimrc:\r\n\r\nThe default separator string for the gQBp mapping is a <Tab> character; to\r\npreset another one (it will be overridden by gqbp), use:\r\n    let g:UnconditionalPaste_Separator = 'text'\r\n\r\nThe default separator string for the gQp and i_CTRL-R_CTRL-Q_CTRL-Q\r\nmappings is a <Tab> character; to preset another one (it will be overridden by\r\ngqp and i_CTRL-R_CTRL-Q), use:\r\n    let g:UnconditionalPaste_JoinSeparator = 'text'\r\n\r\nThe default separator pattern for the gUJp and i_CTRL-R_CTRL-U_CTRL-U\r\nmappings matches any whitespace and newlines (i.e. it will get rid of empty\r\nlines); to preset another one (it will be overridden by gujp and\r\ni_CTRL-R_CTRL-U), use:\r\n    let g:UnconditionalPaste_UnjoinSeparatorPattern = '-'\r\n\r\nThe default pattern for the gRp and gR!p mappings filter out\r\nwhitespace-only lines; to preset another one (will be overridden by grp \/\r\ngr!p), use:\r\n    let g:UnconditionalPaste_GrepPattern = 'pattern'\r\n    let g:UnconditionalPaste_InvertedGrepPattern = 'pattern'\r\n\r\nThe g>p \/ g>P mappings uses the AlignFromCursor.vim plugin's\r\nfunctionality (if installed) to only affect the whitespace between the\r\noriginal text and the pasted line. If you want to always :retab! all the\r\nwhitespace in the entire line, disable this via:\r\n    let g:UnconditionalPaste_IsFullLineRetabOnShift = 1\r\n\r\nBy default, the g,ap, g,op, and g,np mappings use a comma immediately\r\nbefore the coordinating conjunction (also known as \"Oxford comma\"; unless\r\nexactly two lines are pasted); to turn this off:\r\n    let g:UnconditionalPaste_IsSerialComma = 0\r\n\r\nBy default, the gsp mapping does not insert a space on a side that already\r\nhas whitespace. You can make other separators (e.g. quotes) be considered as\r\nexisting space by tweaking the regular expression in :\r\n    let g:UnconditionalPaste_EmptySeparatorPattern = '\\s'\r\nFor some cases (like avoiding a space when pasting inside a {...}) it matters\r\nwhether the separator is before or after the paste. Instead of a single\r\npattern, you can pass a List of two patterns there; the first one applies to\r\nseparators before the paste (so it could match a { if you don't want a space\r\nwhen pasting after it, but you do want a space when pasting before it), the\r\nsecond applies to separators after the paste:\r\n    let g:UnconditionalPaste_EmptySeparatorPattern = ['[[:space:]{]', '[[:space:]}]']\r\n\r\nBy default, the gSp mapping does not add an empty line on a side that\r\nalready just consists of whitespace. You can make other lines be considered\r\nempty by tweaking the regular expression:\r\n    let g:UnconditionalPaste_EmptyLinePattern = '^\\s*$'\r\nFor some cases (like avoiding an empty line when pasting inside a { ... }\r\nblock) it matters whether the line is above or below the paste. Instead of a\r\nsingle pattern, you can pass a List of two patterns there; the first one\r\napplies to lines above the paste (so it could match a { if you don't want an\r\nempty line when pasting after it, but you do want an empty line when pasting\r\nbefore it), the second applies to lines below the paste:\r\n    let g:UnconditionalPaste_EmptyLinePattern = ['^\\s*{\\?$', '^\\s*}\\?$']\r\n\r\nBy default, the g\\p and i_CTRL-R_CTRL-\\ mappings escape backslashes. You\r\ncan change that (e.g. to also escape double quotes), or add more variants:\r\n    let g:UnconditionalPaste_Escapes = [{\r\n    \\   'name': 'dquote',\r\n    \\   'pattern': '[\\\"]',\r\n    \\   'replacement': '\\\\&'\r\n    \\}, ...]\r\nEach configuration object attributes is optional; alternatively, you can also\r\nspecify an expression (using v:val), or a Funcref that takes and returns a\r\nString:\r\n    let g:UnconditionalPaste_Escapes = [\r\n    \\   {'Replacer': 'tr(v:val, \"o\", \"X\")'},\r\n    \\   {'Replacer': function('MyReplacer')},\r\n    \\...]\r\nThe buffer-local b:UnconditionalPaste_Escapes overrides that for particular\r\nbuffers (filetypes if placed in a ftplugin).\r\n\r\nThis stores the last replacement used for g\\\\p and i_CTRL_R_CTRL-\\.\r\nIt is initialized with the first escape from the above configuration \/ entered\r\n\/ selected escape.\r\n\r\nThe default combination used for the gHp and i_CTRL-R_CTRL-H_CTRL-H\r\nmappings. Must be a List of 1 or 2-character strings between the g..p \/ g..P\r\nin the mappings; best obtained by selecting the desired algorithms via ghp\r\nonce and then grabbing the variable value:\r\n    let g:UnconditionalPaste_Combinations = ['U', ',\"', 's']\r\n\r\nIf you want no or only a few of the available mappings, you can completely\r\nturn off the creation of the default mappings by defining:\r\n    :let g:UnconditionalPaste_no_mappings = 1\r\nThis saves you from mapping dummy keys to all unwanted mapping targets.\r\n\r\nIf you want to use different mappings (e.g. starting with <Leader>), map your\r\nkeys to the <Plug>UnconditionalPaste... mapping targets _before_ sourcing this\r\nscript (e.g. in your vimrc):\r\n    nmap <Leader>Pc <Plug>UnconditionalPasteCharBefore\r\n    nmap <Leader>pc <Plug>UnconditionalPasteCharAfter\r\n    nmap <Leader>Pn <Plug>UnconditionalPasteInlinedBefore\r\n    nmap <Leader>pn <Plug>UnconditionalPasteInlinedAfter\r\n    nmap <Leader>Pj <Plug>UnconditionalPasteJustJoinedBefore\r\n    nmap <Leader>pj <Plug>UnconditionalPasteJustJoinedAfter\r\n    nmap <Leader>PC <Plug>UnconditionalPasteCharCondensedBefore\r\n    nmap <Leader>pC <Plug>UnconditionalPasteCharCondensedAfter\r\n    nmap <Leader>Pl <Plug>UnconditionalPasteLineBefore\r\n    nmap <Leader>pl <Plug>UnconditionalPasteLineAfter\r\n    nmap <Leader>Pb <Plug>UnconditionalPasteBlockBefore\r\n    nmap <Leader>pb <Plug>UnconditionalPasteBlockAfter\r\n    nmap <Leader>Pi <Plug>UnconditionalPasteIndentedBefore\r\n    nmap <Leader>pi <Plug>UnconditionalPasteIndentedAfter\r\n    nmap <Leader>Pm <Plug>UnconditionalPasteMoreIndentBefore\r\n    nmap <Leader>pm <Plug>UnconditionalPasteMoreIndentAfter\r\n    nmap <Leader>Pl <Plug>UnconditionalPasteLessIndentBefore\r\n    nmap <Leader>pl <Plug>UnconditionalPasteLessIndentAfter\r\n    nmap <Leader>P> <Plug>UnconditionalPasteShiftedBefore\r\n    nmap <Leader>p> <Plug>UnconditionalPasteShiftedAfter\r\n    nmap <Leader>P# <Plug>UnconditionalPasteCommentedBefore\r\n    nmap <Leader>p# <Plug>UnconditionalPasteCommentedAfter\r\n    nmap <Leader>Ps <Plug>UnconditionalPasteSpacedBefore\r\n    nmap <Leader>ps <Plug>UnconditionalPasteSpacedAfter\r\n    nmap <Leader>PS <Plug>UnconditionalPasteParagraphedBefore\r\n    nmap <Leader>pS <Plug>UnconditionalPasteParagraphedAfter\r\n    nmap <Leader>PB <Plug>UnconditionalPasteJaggedBefore\r\n    nmap <Leader>pB <Plug>UnconditionalPasteJaggedAfter\r\n    nmap <Leader>Pd <Plug>UnconditionalPasteDelimitedBefore\r\n    nmap <Leader>pd <Plug>UnconditionalPasteDelimitedAfter\r\n    nmap <Leader>PD <Plug>UnconditionalPasteRecallDelimitedBefore\r\n    nmap <Leader>pD <Plug>UnconditionalPasteRecallDelimitedAfter\r\n    nmap <Leader>P, <Plug>UnconditionalPasteCommaBefore\r\n    nmap <Leader>p, <Plug>UnconditionalPasteCommaAfter\r\n    nmap <Leader>P' <Plug>UnconditionalPasteCommaSingleQuoteBefore\r\n    nmap <Leader>p' <Plug>UnconditionalPasteCommaSingleQuoteAfter\r\n    nmap <Leader>P\" <Plug>UnconditionalPasteCommaDoubleQuoteBefore\r\n    nmap <Leader>p\" <Plug>UnconditionalPasteCommaDoubleQuoteAfter\r\n    nmap <Leader>P,n <<Plug>UnconditionalPasteCommaNorBefore\r\n    nmap <Leader>p,n <Plug>UnconditionalPasteCommaNorAfter\r\n    nmap <Leader>P,o <Plug>UnconditionalPasteCommaOrBefore\r\n    nmap <Leader>p,o <Plug>UnconditionalPasteCommaOrAfter\r\n    nmap <Leader>P,a <Plug>UnconditionalPasteCommaAndBefore\r\n    nmap <Leader>p,a <Plug>UnconditionalPasteCommaAndAfter\r\n    nmap <Leader>Pq <Plug>UnconditionalPasteQueriedBefore\r\n    nmap <Leader>pq <Plug>UnconditionalPasteQueriedAfter\r\n    nmap <Leader>PQ <Plug>UnconditionalPasteRecallQueriedBefore\r\n    nmap <Leader>pQ <Plug>UnconditionalPasteRecallQueriedAfter\r\n    nmap <Leader>Pgq <Plug>UnconditionalPasteQueriedJoinedBefore\r\n    nmap <Leader>pgq <Plug>UnconditionalPasteQueriedJoinedAfter\r\n    nmap <Leader>PgQ <Plug>UnconditionalPasteRecallQueriedJoinedBefore\r\n    nmap <Leader>pgQ <Plug>UnconditionalPasteRecallQueriedJoinedAfter\r\n    nmap <Leader>Puj <Plug>UnconditionalPasteUnjoinBefore\r\n    nmap <Leader>puj <Plug>UnconditionalPasteUnjoinAfter\r\n    nmap <Leader>PUJ <Plug>UnconditionalPasteRecallUnjoinBefore\r\n    nmap <Leader>pUJ <Plug>UnconditionalPasteRecallUnjoinAfter\r\n    nmap <Leader>Pr <Plug>UnconditionalPasteGrepBefore\r\n    nmap <Leader>pr <Plug>UnconditionalPasteGrepAfter\r\n    nmap <Leader>P! <Plug>UnconditionalPasteInvertedGrepBefore\r\n    nmap <Leader>p! <Plug>UnconditionalPasteInvertedGrepAfter\r\n    nmap <Leader>PR <Plug>UnconditionalPasteRecallGrepBefore\r\n    nmap <Leader>pR <Plug>UnconditionalPasteRecallGrepAfter\r\n    nmap <Leader>P1 <Plug>UnconditionalPasteRecallInvertedGrepBefore\r\n    nmap <Leader>p1 <Plug>UnconditionalPasteRecallInvertedGrepAfter\r\n    nmap <Leader>Pe <Plug>UnconditionalPasteExpressionBefore\r\n    nmap <Leader>pe <Plug>UnconditionalPasteExpressionAfter\r\n    nmap <Leader>PE <Plug>UnconditionalPasteRecallExpressionBefore\r\n    nmap <Leader>pE <Plug>UnconditionalPasteRecallExpressionAfter\r\n    nmap <Leader>Px <Plug>UnconditionalPasteEscapeBefore\r\n    nmap <Leader>px <Plug>UnconditionalPasteEscapeAfter\r\n    nmap <Leader>PX <Plug>UnconditionalPasteRecallEscapeBefore\r\n    nmap <Leader>pX <Plug>UnconditionalPasteRecallEscapeAfter\r\n    nmap <Leader>Pp <Plug>UnconditionalPastePlusBefore\r\n    nmap <Leader>pp <Plug>UnconditionalPastePlusAfter\r\n    nmap <Leader>PP <Plug>UnconditionalPasteGPlusBefore\r\n    nmap <Leader>pP <Plug>UnconditionalPasteGPlusAfter\r\n    nmap <Leader>Pu <Plug>UnconditionalPasteLowercaseBefore\r\n    nmap <Leader>pu <Plug>UnconditionalPasteLowercaseAfter\r\n    nmap <Leader>PU <Plug>UnconditionalPasteUppercaseBefore\r\n    nmap <Leader>pU <Plug>UnconditionalPasteUppercaseAfter\r\n    nmap <Leader>pt <Plug>UnconditionalPasteTogglecaseBefore\r\n    nmap <Leader>Pt <Plug>UnconditionalPasteTogglecaseAfter\r\n    nmap <Leader>Ph <Plug>UnconditionalPasteCombinatorialBefore\r\n    nmap <Leader>ph <Plug>UnconditionalPasteCombinatorialAfter\r\n    nmap <Leader>PH <Plug>UnconditionalPasteRecallCombinatorialBefore\r\n    nmap <Leader>pH <Plug>UnconditionalPasteRecallCombinatorialAfter\r\n\r\n    imap <C-G>c <Plug>UnconditionalPasteCharI\r\n    imap <C-G>n <Plug>UnconditionalPasteInlinedI\r\n    imap <C-G>C <Plug>UnconditionalPasteCharCondensedI\r\n    imap <C-G>, <Plug>UnconditionalPasteCommaI\r\n    imap <C-G>q <Plug>UnconditionalPasteQueriedI\r\n    imap <C-G>Q <Plug>UnconditionalPasteRecallQueriedI\r\n    imap <C-G>j <Plug>UnconditionalPasteQueriedJoinedI\r\n    imap <C-G>J <Plug>UnconditionalPasteRecallQueriedJoinedI\r\n    imap <C-G>u <Plug>UnconditionalPasteUnjoinI\r\n    imap <C-G>U <Plug>UnconditionalPasteRecallUnjoinI\r\n    imap <C-G>x <Plug>UnconditionalPasteEscapeI\r\n    imap <C-G>X <Plug>UnconditionalPasteRecallEscapeI\r\n    imap <C-G>~ <Plug>UnconditionalPasteTogglecaseI\r\n    imap <C-G>h <Plug>UnconditionalPasteCombinatorialI\r\n    imap <C-G>H <Plug>UnconditionalPasteRecallCombinatorialI\r\n\r\n    cmap <C-G>c <Plug>UnconditionalPasteCharI\r\n    cmap <C-G>n <Plug>UnconditionalPasteInlinedI\r\n    cmap <C-G>C <Plug>UnconditionalPasteCharCondensedI\r\n    cmap <C-G>, <Plug>UnconditionalPasteCommaI\r\n    cmap <C-G>q <Plug>UnconditionalPasteQueriedI\r\n    cmap <C-G>Q <Plug>UnconditionalPasteRecallQueriedI\r\n    cmap <C-G>j <Plug>UnconditionalPasteQueriedJoinedI\r\n    cmap <C-G>J <Plug>UnconditionalPasteRecallQueriedJoinedI\r\n    cmap <C-G>u <Plug>UnconditionalPasteUnjoinI\r\n    cmap <C-G>U <Plug>UnconditionalPasteRecallUnjoinI\r\n    cmap <C-G>x <Plug>UnconditionalPasteEscapeI\r\n    cmap <C-G>X <Plug>UnconditionalPasteRecallEscapeI\r\n    cmap <C-G>~ <Plug>UnconditionalPasteTogglecaseI\r\n    cmap <C-G>h <Plug>UnconditionalPasteCombinatorialI\r\n    cmap <C-G>H <Plug>UnconditionalPasteRecallCombinatorialI","first_name":"Ingo","6":"Ingo","last_name":"Karkat","7":"Karkat","releases":[{"0":"3355","vim_version":"7.0","1":"7.0","script_version":"4.30","2":"4.30","version_comment":"- ENH: Add gHp mapping for repeating the same previously queried combination and a configurable preset g:UnconditionalPaste_Combinations.\r\n- ENH: Add i_CTRL-R_CTRL-H \/ c_CTRL-R_CTRL-H mappings for ghp and i_CTRL-R_CTRL-H_CTRL-H \/ c_CTRL-R_CTRL-H_CTRL-H for gHp. As only some paste variants are offered in insert and command-line modes, these allow to use any (working) variant there, too, and any combinations of them.\r\n- BUG: Empty line check in gSp does not account for a closed fold under cursor and wrongly considers the current line within the fold instead of the first \/ last folded line.\r\n- ENH: Allow to disable all default mappings via a single g:UnconditionalPaste_no_mappings configuration flag.\r\n- ENH: Add gCp and i_CTRL-R_CTRL-C_CTRL-C variants of gcp and i_CTRL-R_CTRL-C that flatten any sequence of whitespace to a single space; so not just indent, but also inner runs of whitespace.\r\n- ENH: Add gcip and i_CTRL-R_CTRL-I variants of gcp and i_CTRL-R_CTRL-C that just paste inline (so linewise and blockwise register contents are not put on separate lines, but start at the cursor position), but keep inner newlines and their indent (so not all is flattened into a single line).\r\n- ENH: gsp lets users tweak which sides do not get a space inserted via g:UnconditionalPaste_EmptySeparatorPattern.\r\n- ENH: gSp also considers whitespace-only lines as empty (not just totally empty ones) by default, and lets users tweak that via g:UnconditionalPaste_EmptyLinePattern.\r\n- BUG: gSP \/ gSp on completely empty buffer does not add both leading and trailing empty lines.\r\n- BUG: gSP \/ gSp on single line in buffer do not consider start \/ end of buffer.","3":"- ENH: Add gHp mapping for repeating the same previously queried combination and a configurable preset g:UnconditionalPaste_Combinations.\r\n- ENH: Add i_CTRL-R_CTRL-H \/ c_CTRL-R_CTRL-H mappings for ghp and i_CTRL-R_CTRL-H_CTRL-H \/ c_CTRL-R_CTRL-H_CTRL-H for gHp. As only some paste variants are offered in insert and command-line modes, these allow to use any (working) variant there, too, and any combinations of them.\r\n- BUG: Empty line check in gSp does not account for a closed fold under cursor and wrongly considers the current line within the fold instead of the first \/ last folded line.\r\n- ENH: Allow to disable all default mappings via a single g:UnconditionalPaste_no_mappings configuration flag.\r\n- ENH: Add gCp and i_CTRL-R_CTRL-C_CTRL-C variants of gcp and i_CTRL-R_CTRL-C that flatten any sequence of whitespace to a single space; so not just indent, but also inner runs of whitespace.\r\n- ENH: Add gcip and i_CTRL-R_CTRL-I variants of gcp and i_CTRL-R_CTRL-C that just paste inline (so linewise and blockwise register contents are not put on separate lines, but start at the cursor position), but keep inner newlines and their indent (so not all is flattened into a single line).\r\n- ENH: gsp lets users tweak which sides do not get a space inserted via g:UnconditionalPaste_EmptySeparatorPattern.\r\n- ENH: gSp also considers whitespace-only lines as empty (not just totally empty ones) by default, and lets users tweak that via g:UnconditionalPaste_EmptyLinePattern.\r\n- BUG: gSP \/ gSp on completely empty buffer does not add both leading and trailing empty lines.\r\n- BUG: gSP \/ gSp on single line in buffer do not consider start \/ end of buffer.","package":"UnconditionalPaste-4.30.vmb.gz","4":"UnconditionalPaste-4.30.vmb.gz","src_id":"27307","5":"27307","creation_date":"1599329849","6":"1599329849"},{"0":"3355","vim_version":"7.0","1":"7.0","script_version":"4.20","2":"4.20","version_comment":"- Add JustJoined (gcgp) and QueriedJoined (gqgp, <C-q><C-g>) variants of gcp and gqp that keep indent and surrounding whitespace as-is.\r\n- CHG: Insert and command-line mode <Plug> mappings now have a trailing I, to resolve the ambiguity between <Plug>UnconditionalPasteQueried and <Plug>UnconditionalPasteQueriedJoined. **** Please update any insert- and command-line mode mapping customization. ****\r\n- Add CommaAnd (g,ap), CommaOr (g,op), and CommaNor (g,np) variants of g,p.\r\n- Add Escape (g\\p, i_CTRL-R_CTRL-\\) and RecallEscape (g\\\\p, i_CTRL-R_CTRL-\\_CTRL-\\) mappings to perform escaping of certain characters before pasting \/ inserting.","3":"- Add JustJoined (gcgp) and QueriedJoined (gqgp, <C-q><C-g>) variants of gcp and gqp that keep indent and surrounding whitespace as-is.\r\n- CHG: Insert and command-line mode <Plug> mappings now have a trailing I, to resolve the ambiguity between <Plug>UnconditionalPasteQueried and <Plug>UnconditionalPasteQueriedJoined. **** Please update any insert- and command-line mode mapping customization. ****\r\n- Add CommaAnd (g,ap), CommaOr (g,op), and CommaNor (g,np) variants of g,p.\r\n- Add Escape (g\\p, i_CTRL-R_CTRL-\\) and RecallEscape (g\\\\p, i_CTRL-R_CTRL-\\_CTRL-\\) mappings to perform escaping of certain characters before pasting \/ inserting.","package":"UnconditionalPaste-4.20.vmb.gz","4":"UnconditionalPaste-4.20.vmb.gz","src_id":"25800","5":"25800","creation_date":"1516785640","6":"1516785640"},{"0":"3355","vim_version":"7.0","1":"7.0","script_version":"4.10","2":"4.10","version_comment":"- Add grp \/ gr!p \/ gRp \/ gR!p mappings that include \/ exclude lines matching queried \/ recalled pattern, defaulting (both variants) to include only non-empty lines.\r\n- Add g=p \/ g==p mappings that process lines through a queried \/ recalled Vim expression.\r\n- ENH: In ghp query, offer help on the mnemonics by pressing ?.\r\n- ENH: Make gqp also support 5-element {prefix}^M{element-prefix}^M{separator}^M{element-suffix}^M{suffix} in addition to the 3-element one. *** You need to update to ingo-library (vimscript #4433) version 1.026! ***","3":"- Add grp \/ gr!p \/ gRp \/ gR!p mappings that include \/ exclude lines matching queried \/ recalled pattern, defaulting (both variants) to include only non-empty lines.\r\n- Add g=p \/ g==p mappings that process lines through a queried \/ recalled Vim expression.\r\n- ENH: In ghp query, offer help on the mnemonics by pressing ?.\r\n- ENH: Make gqp also support 5-element {prefix}^M{element-prefix}^M{separator}^M{element-suffix}^M{suffix} in addition to the 3-element one. *** You need to update to ingo-library (vimscript #4433) version 1.026! ***","package":"UnconditionalPaste-4.10.vmb.gz","4":"UnconditionalPaste-4.10.vmb.gz","src_id":"24816","5":"24816","creation_date":"1482523530","6":"1482523530"},{"0":"3355","vim_version":"7.0","1":"7.0","script_version":"4.00","2":"4.00","version_comment":"- Establish hard dependency on ingo-library. *** You need to separately install ingo-library (vimscript #4433) version 1.024 (or higher)! ***\r\n- BUG: Escaped characters like \\n are handled inconsistently in gqp: resolved as {separator}, taken literally in {prefix} and {suffix}. Use ingo#cmdargs#GetUnescapedExpr() to resolve them (also for gqbp, which only supports {separator}).\r\n- ENH: If there's only a single line to paste and no [count] with the blockwise commands (gbp, gBp, gqbq, gQBp), first query about a separator pattern and un-join the register contents. Otherwise, these variants don't make much sense (and for the corner cases, a count of 1 can be supplied).\r\n- CHG: Split off |gSp| from |gsp|; the latter now flattens line(s) like |gcp|, whereas the new |gSp| forces linewise surrounding with empty lines. I found that I often |dd| a line in order to append it to another line with a space in between.\r\n- CHG: Change gup \/ gUp to gujp \/ gUJp and add gup \/ gUp to lower \/ uppercase the first character of the register\r\n- Need to use temporary default register also for the built-in read-only registers {:%.}.\r\n- FIX: Vim error on CTRL-R ... mappings incorrectly inserted \"0\". Need to return '' from :catch.\r\n- Add ghp \/ ghP combinatorial type that queries and then sequentially applies multiple algorithms.","3":"- Establish hard dependency on ingo-library. *** You need to separately install ingo-library (vimscript #4433) version 1.024 (or higher)! ***\r\n- BUG: Escaped characters like \\n are handled inconsistently in gqp: resolved as {separator}, taken literally in {prefix} and {suffix}. Use ingo#cmdargs#GetUnescapedExpr() to resolve them (also for gqbp, which only supports {separator}).\r\n- ENH: If there's only a single line to paste and no [count] with the blockwise commands (gbp, gBp, gqbq, gQBp), first query about a separator pattern and un-join the register contents. Otherwise, these variants don't make much sense (and for the corner cases, a count of 1 can be supplied).\r\n- CHG: Split off |gSp| from |gsp|; the latter now flattens line(s) like |gcp|, whereas the new |gSp| forces linewise surrounding with empty lines. I found that I often |dd| a line in order to append it to another line with a space in between.\r\n- CHG: Change gup \/ gUp to gujp \/ gUJp and add gup \/ gUp to lower \/ uppercase the first character of the register\r\n- Need to use temporary default register also for the built-in read-only registers {:%.}.\r\n- FIX: Vim error on CTRL-R ... mappings incorrectly inserted \"0\". Need to return '' from :catch.\r\n- Add ghp \/ ghP combinatorial type that queries and then sequentially applies multiple algorithms.","package":"UnconditionalPaste-4.00.vmb.gz","4":"UnconditionalPaste-4.00.vmb.gz","src_id":"24436","5":"24436","creation_date":"1470758779","6":"1470758779"},{"0":"3355","vim_version":"7.0","1":"7.0","script_version":"3.10","2":"3.10","version_comment":"- Add g,'p and g,\"p variants of g,p.\r\n- ENH: Allow to specify prefix and suffix when querying for the separator string in gqp and i_CTRL-R_CTRL-Q.","3":"- Add g,'p and g,\"p variants of g,p.\r\n- ENH: Allow to specify prefix and suffix when querying for the separator string in gqp and i_CTRL-R_CTRL-Q.","package":"UnconditionalPaste-3.10.vmb.gz","4":"UnconditionalPaste-3.10.vmb.gz","src_id":"22722","5":"22722","creation_date":"1419333760","6":"1419333760"},{"0":"3355","vim_version":"7.0","1":"7.0","script_version":"3.03","2":"3.03","version_comment":"- BUG: gsp \/ gsP border check adds spaces on both sides when there's a single character in line (like when there's a completely empty line, where this would be correct). Differentiate between empty and single-char line and then clear the isAtStart \/ isAtEnd flag not in the direction of the paste.","3":"- BUG: gsp \/ gsP border check adds spaces on both sides when there's a single character in line (like when there's a completely empty line, where this would be correct). Differentiate between empty and single-char line and then clear the isAtStart \/ isAtEnd flag not in the direction of the paste.","package":"UnconditionalPaste-3.03.vmb.gz","4":"UnconditionalPaste-3.03.vmb.gz","src_id":"22666","5":"22666","creation_date":"1417613110","6":"1417613110"},{"0":"3355","vim_version":"7.0","1":"7.0","script_version":"3.02","2":"3.02","version_comment":"- CHG: Change default mappings of gdp and gDp to gqbp and gQBp, respectively, to avoid slowing down the built-in |gd| and |gD| commands with a wait for the mapping timeout. Though the new defaults are one keystroke longer, they are a better mnemonic (combining gqp and gBp), and this is a rather obscure mapping, anyway.","3":"- CHG: Change default mappings of gdp and gDp to gqbp and gQBp, respectively, to avoid slowing down the built-in |gd| and |gD| commands with a wait for the mapping timeout. Though the new defaults are one keystroke longer, they are a better mnemonic (combining gqp and gBp), and this is a rather obscure mapping, anyway.","package":"UnconditionalPaste-3.02.vmb.gz","4":"UnconditionalPaste-3.02.vmb.gz","src_id":"22062","5":"22062","creation_date":"1403204636","6":"1403204636"},{"0":"3355","vim_version":"7.0","1":"7.0","script_version":"3.01","2":"3.01","version_comment":"- For gsp, remove surrounding whitespace (characterwise) \/ empty lines (linewise) before adding the spaces \/ empty lines. This ensures a more dependable and deterministic DWIM behavior.","3":"- For gsp, remove surrounding whitespace (characterwise) \/ empty lines (linewise) before adding the spaces \/ empty lines. This ensures a more dependable and deterministic DWIM behavior.","package":"UnconditionalPaste-3.01.vmb.gz","4":"UnconditionalPaste-3.01.vmb.gz","src_id":"21930","5":"21930","creation_date":"1400848421","6":"1400848421"},{"0":"3355","vim_version":"7.0","1":"7.0","script_version":"3.00","2":"3.00","version_comment":"- ENH: Extend CTRL-R insert mode mappings to command-line mode.\r\n- When doing gqp \/ q,p of a characterwise or single line, put the separator in front (gqp) \/ after (gqP); otherwise, the mapping is identical to normal p \/ P and therefore worthless.\r\n- Add g#p mapping to apply 'commentstring' to each indented linewise paste.\r\n- Add gsp mapping to paste with [count] spaces \/ empty lines around the register contents.\r\n- Add gdp \/ gDp mappings to paste as a minimal fitting block with (queried \/ recalled) separator string, with special cases at the end of leading indent and at the end of the line.\r\n- Add gBp mapping to paste as a minimal fitting block with jagged right edge, a separator-less variant of gDp.\r\n- Add g>p mapping to paste shifted register contents.\r\n- Add g]]p and g[[p mappings to paste like with g]p, but with more \/ less indent.","3":"- ENH: Extend CTRL-R insert mode mappings to command-line mode.\r\n- When doing gqp \/ q,p of a characterwise or single line, put the separator in front (gqp) \/ after (gqP); otherwise, the mapping is identical to normal p \/ P and therefore worthless.\r\n- Add g#p mapping to apply 'commentstring' to each indented linewise paste.\r\n- Add gsp mapping to paste with [count] spaces \/ empty lines around the register contents.\r\n- Add gdp \/ gDp mappings to paste as a minimal fitting block with (queried \/ recalled) separator string, with special cases at the end of leading indent and at the end of the line.\r\n- Add gBp mapping to paste as a minimal fitting block with jagged right edge, a separator-less variant of gDp.\r\n- Add g>p mapping to paste shifted register contents.\r\n- Add g]]p and g[[p mappings to paste like with g]p, but with more \/ less indent.","package":"UnconditionalPaste-3.00.vmb.gz","4":"UnconditionalPaste-3.00.vmb.gz","src_id":"21659","5":"21659","creation_date":"1395676241","6":"1395676241"},{"0":"3355","vim_version":"7.0","1":"7.0","script_version":"2.21","2":"2.21","version_comment":"- FIX: In gpp and gPp, keep leading zeros when incrementing the number.\r\n- FIX: In gpp and gPp, do not interpret leading zeros as octal numbers when incrementing.","3":"- FIX: In gpp and gPp, keep leading zeros when incrementing the number.\r\n- FIX: In gpp and gPp, do not interpret leading zeros as octal numbers when incrementing.","package":"UnconditionalPaste-2.21.vmb.gz","4":"UnconditionalPaste-2.21.vmb.gz","src_id":"19901","5":"19901","creation_date":"1366700716","6":"1366700716"},{"0":"3355","vim_version":"7.0","1":"7.0","script_version":"2.20","2":"2.20","version_comment":"- ENH: gpp also handles multi-line pastes. A number (after the corresponding column) is incremented in every line. If there are no increments this way, fall back to replacement of the first occurrence.\r\n- ENH: Add gPp \/ gPP mappings to paste with all numbers incremented \/ decremented.\r\n- ENH: Add g]p \/ g]P mappings to paste linewise with adjusted indent. Thanks to Gary Fixler for the suggestion.","3":"- ENH: gpp also handles multi-line pastes. A number (after the corresponding column) is incremented in every line. If there are no increments this way, fall back to replacement of the first occurrence.\r\n- ENH: Add gPp \/ gPP mappings to paste with all numbers incremented \/ decremented.\r\n- ENH: Add g]p \/ g]P mappings to paste linewise with adjusted indent. Thanks to Gary Fixler for the suggestion.","package":"UnconditionalPaste-2.20.vmb.gz","4":"UnconditionalPaste-2.20.vmb.gz","src_id":"19659","5":"19659","creation_date":"1363622027","6":"1363622027"},{"0":"3355","vim_version":"7.0","1":"7.0","script_version":"2.10","2":"2.10","version_comment":"- ENH: Add gpp \/ gpP mappings to paste with one number (which depending on the current cursor position) incremented \/ decremented.\r\n- FIX: For characterwise pastes with a [count], the multiplied pastes must be joined with the desired separator, not just plainly concatenated.\r\n- FIX: Don't lose the original [count] given when repeating the mapping.\r\n- FIX: Do not re-query on repeat of the mapping.","3":"- ENH: Add gpp \/ gpP mappings to paste with one number (which depending on the current cursor position) incremented \/ decremented.\r\n- FIX: For characterwise pastes with a [count], the multiplied pastes must be joined with the desired separator, not just plainly concatenated.\r\n- FIX: Don't lose the original [count] given when repeating the mapping.\r\n- FIX: Do not re-query on repeat of the mapping.","package":"UnconditionalPaste-2.10.vmb.gz","4":"UnconditionalPaste-2.10.vmb.gz","src_id":"19233","5":"19233","creation_date":"1356176533","6":"1356176533"},{"0":"3355","vim_version":"7.0","1":"7.0","script_version":"2.00","2":"2.00","version_comment":"- ENH: Add g,p \/ gqp \/ gQp mappings to paste lines flattened with comma, queried, or recalled last used delimiter.\r\n- ENH: Add gup \/ gUp mappings to paste unjoined register with queried or recalled last used delimiter pattern.\r\n- ENH: Add CTRL-R CTRL-C mapping to insert register contents characterwise (flattened) from insert mode, and similar insert mode mappings for the other new mappings.\r\n- CHG: Flatten all whitespace and newlines before, after, and around lines when pasting characterwise or joined.","3":"- ENH: Add g,p \/ gqp \/ gQp mappings to paste lines flattened with comma, queried, or recalled last used delimiter.\r\n- ENH: Add gup \/ gUp mappings to paste unjoined register with queried or recalled last used delimiter pattern.\r\n- ENH: Add CTRL-R CTRL-C mapping to insert register contents characterwise (flattened) from insert mode, and similar insert mode mappings for the other new mappings.\r\n- CHG: Flatten all whitespace and newlines before, after, and around lines when pasting characterwise or joined.","package":"UnconditionalPaste-2.00.vmb.gz","4":"UnconditionalPaste-2.00.vmb.gz","src_id":"19163","5":"19163","creation_date":"1355220363","6":"1355220363"},{"0":"3355","vim_version":"7.0","1":"7.0","script_version":"1.22","2":"1.22","version_comment":"- BUG: When repeat.vim is not installed, the mappings do nothing. Need to :execute the :silent! call of repeat.vim to avoid that the remainder of the command line is aborted together with the call.\r\n- Using separate autoload script to help speed up Vim startup.","3":"- BUG: When repeat.vim is not installed, the mappings do nothing. Need to :execute the :silent! call of repeat.vim to avoid that the remainder of the command line is aborted together with the call.\r\n- Using separate autoload script to help speed up Vim startup.","package":"UnconditionalPaste-1.22.vmb.gz","4":"UnconditionalPaste-1.22.vmb.gz","src_id":"19105","5":"19105","creation_date":"1354633325","6":"1354633325"},{"0":"3355","vim_version":"7.0","1":"7.0","script_version":"1.21","2":"1.21","version_comment":"- ENH: When pasting a blockwise register as lines, strip all trailing whitespace. This is useful when cutting a block of text from a column-like text and pasting as new lines.  \r\n- ENH: When pasting a blockwise register as characters, flatten and shrink all trailing whitespace to a single space. ","3":"- ENH: When pasting a blockwise register as lines, strip all trailing whitespace. This is useful when cutting a block of text from a column-like text and pasting as new lines.  \r\n- ENH: When pasting a blockwise register as characters, flatten and shrink all trailing whitespace to a single space. ","package":"UnconditionalPaste.vba.gz","4":"UnconditionalPaste.vba.gz","src_id":"18142","5":"18142","creation_date":"1339920335","6":"1339920335"},{"0":"3355","vim_version":"7.0","1":"7.0","script_version":"1.20","2":"1.20","version_comment":"BUG: Repeat always used the unnamed register. Add register registration to enhanced repeat.vim plugin. This also handles repetition when used together with the expression register \"=. Requires a so far inofficial update to repeat.vim version 1.0 (that hopefully makes it into upstream), which is available at https:\/\/github.com\/inkarkat\/vim-repeat\/zipball\/1.0ENH1","3":"BUG: Repeat always used the unnamed register. Add register registration to enhanced repeat.vim plugin. This also handles repetition when used together with the expression register \"=. Requires a so far inofficial update to repeat.vim version 1.0 (that hopefully makes it into upstream), which is available at https:\/\/github.com\/inkarkat\/vim-repeat\/zipball\/1.0ENH1","package":"UnconditionalPaste.vba.gz","4":"UnconditionalPaste.vba.gz","src_id":"17013","5":"17013","creation_date":"1322863390","6":"1322863390"},{"0":"3355","vim_version":"7.0","1":"7.0","script_version":"1.11","2":"1.11","version_comment":"ENH: Support repetition of mappings through repeat.vim. ","3":"ENH: Support repetition of mappings through repeat.vim. ","package":"UnconditionalPaste.vba.gz","4":"UnconditionalPaste.vba.gz","src_id":"15829","5":"15829","creation_date":"1307428108","6":"1307428108"},{"0":"3355","vim_version":"7.0","1":"7.0","script_version":"1.10","2":"1.10","version_comment":"Incorporated suggestions by Peter Rincker (thanks for the patch!): \r\n- Made mappings configurable via the customary <Plug> mappings. \r\n- Added mappings gbp, gbP for blockwise pasting. \r\n- Now requires Vim version 7.0 or higher. ","3":"Incorporated suggestions by Peter Rincker (thanks for the patch!): \r\n- Made mappings configurable via the customary <Plug> mappings. \r\n- Added mappings gbp, gbP for blockwise pasting. \r\n- Now requires Vim version 7.0 or higher. ","package":"UnconditionalPaste.vba.gz","4":"UnconditionalPaste.vba.gz","src_id":"14740","5":"14740","creation_date":"1294929990","6":"1294929990"},{"0":"3355","vim_version":"6.0","1":"6.0","script_version":"1.00","2":"1.00","version_comment":"Initial upload","3":"Initial upload","package":"UnconditionalPaste.vba.gz","4":"UnconditionalPaste.vba.gz","src_id":"14465","5":"14465","creation_date":"1291981590","6":"1291981590"}]},"3354":{"script_id":"3354","0":"3354","script_name":"wesnothcfg.vim","1":"wesnothcfg.vim","script_type":"syntax","2":"syntax","summary":"Syntax highlight for Wesnoth WML","3":"Syntax highlight for Wesnoth WML","description":"This is my attempt for a Wesnoth WML syntax file.\r\n\r\nI'm not very skilled in Wesnoth WML so could there be any problems, please do not hesitate to send me an e-mail.\r\n\r\n","4":"This is my attempt for a Wesnoth WML syntax file.\r\n\r\nI'm not very skilled in Wesnoth WML so could there be any problems, please do not hesitate to send me an e-mail.\r\n\r\n","install_details":"install to ~\/.vim\/syntax\r\n\r\nand add following into your ~\/.vimrc:\r\n    autocmd BufNewFile,BufRead *.cfg            setf wesnothcfg\r\n\r\n","5":"install to ~\/.vim\/syntax\r\n\r\nand add following into your ~\/.vimrc:\r\n    autocmd BufNewFile,BufRead *.cfg            setf wesnothcfg\r\n\r\n","first_name":"Pan","6":"Pan","last_name":"Shizhu","7":"Shizhu","releases":[{"0":"3354","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"wesnothcfg.vim","4":"wesnothcfg.vim","src_id":"14459","5":"14459","creation_date":"1291792721","6":"1291792721"}]},"3353":{"script_id":"3353","0":"3353","script_name":"jbosslog","1":"jbosslog","script_type":"syntax","2":"syntax","summary":"Syntax file for viewing Jboss Logs ","3":"Syntax file for viewing Jboss Logs ","description":"if you wanted exceptions\/errors to stand out as red words, date to be in a different color so that it may be ignored ... here is the script that will do that for you.","4":"if you wanted exceptions\/errors to stand out as red words, date to be in a different color so that it may be ignored ... here is the script that will do that for you.","install_details":"If you are on windows and you use cygwin, here are some more things that you could add to your ~\\_vimrc\r\n\r\nfiletype plugin on\r\n\"set cfu=VjdeCompletionFun\r\n\"let g:vjde_lib_path=\"lib\/j2ee.jar:lib\/struts.jar:build\/classes\"\r\nset shell=D:\/tools\/cygwin\/bin\/bash\r\nset shellcmdflag=--login\\ -c\r\nset shellxquote=\\\"\r\n\r\nfu! Log()\r\n    :e C:\\whp-jboss-5.3.1.2\\server\\default\\log\\server.log\r\n    :se autoread\r\nendfunction\r\n\r\nfu! Field(n)\r\n    echo a:n\r\n    let str1=\"1,'a! awk '{print $\".a:n.\" }'\"\r\n    echo str1\r\n    :execute str1\r\nendfunction\r\n\r\nfu! NotField(n)\r\n    echo a:n\r\n    let str1=\"1,'a! awk '{$\".a:n.\"=\\\"\\\"\\\"\\\"; print; }'\"\r\n    echo str1\r\n    :execute str1\r\nendfunction\r\n\r\nfu! MessageOnly()\r\n\t:1,$s\/\\([^,]*\\), \\(.*$\\)\/\\2 \\1\/\r\n\r\nendfunction\r\n\r\naugroup filetypedetect\r\n  au! BufRead,BufNewFile server.log set filetype=jbosslog\r\naugroup END\r\n\r\nsyntax on","5":"If you are on windows and you use cygwin, here are some more things that you could add to your ~\\_vimrc\r\n\r\nfiletype plugin on\r\n\"set cfu=VjdeCompletionFun\r\n\"let g:vjde_lib_path=\"lib\/j2ee.jar:lib\/struts.jar:build\/classes\"\r\nset shell=D:\/tools\/cygwin\/bin\/bash\r\nset shellcmdflag=--login\\ -c\r\nset shellxquote=\\\"\r\n\r\nfu! Log()\r\n    :e C:\\whp-jboss-5.3.1.2\\server\\default\\log\\server.log\r\n    :se autoread\r\nendfunction\r\n\r\nfu! Field(n)\r\n    echo a:n\r\n    let str1=\"1,'a! awk '{print $\".a:n.\" }'\"\r\n    echo str1\r\n    :execute str1\r\nendfunction\r\n\r\nfu! NotField(n)\r\n    echo a:n\r\n    let str1=\"1,'a! awk '{$\".a:n.\"=\\\"\\\"\\\"\\\"; print; }'\"\r\n    echo str1\r\n    :execute str1\r\nendfunction\r\n\r\nfu! MessageOnly()\r\n\t:1,$s\/\\([^,]*\\), \\(.*$\\)\/\\2 \\1\/\r\n\r\nendfunction\r\n\r\naugroup filetypedetect\r\n  au! BufRead,BufNewFile server.log set filetype=jbosslog\r\naugroup END\r\n\r\nsyntax on","first_name":"bala","6":"bala","last_name":"dutt","7":"dutt","releases":[{"0":"3353","vim_version":"7.2","1":"7.2","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"jbosslog.vim","4":"jbosslog.vim","src_id":"14457","5":"14457","creation_date":"1291785547","6":"1291785547"}]},"3352":{"script_id":"3352","0":"3352","script_name":"auto_mkdir","1":"auto_mkdir","script_type":"utility","2":"utility","summary":"Allows you to save files into directories that do not exist yet.","3":"Allows you to save files into directories that do not exist yet.","description":"This plugin automatically creates parent directories for the current file if they don't exist yet.\r\n\r\n\r\nExample:\r\n    If you're currently in an empty directory, without the plugin, the command\r\n        :w foo\/bar\/baz.txt\r\n    will fail with with E212 (\"Can't open file for writing.\")\r\n\r\n    The plugin will automatically create the directories foo\/ and foo\/bar\/ for you before Vim saves \r\n    the file, so you don't have to remember to do it manually.\r\n\r\n\r\nAlso available via git:\r\n    https:\/\/github.com\/DataWraith\/auto_mkdir","4":"This plugin automatically creates parent directories for the current file if they don't exist yet.\r\n\r\n\r\nExample:\r\n    If you're currently in an empty directory, without the plugin, the command\r\n        :w foo\/bar\/baz.txt\r\n    will fail with with E212 (\"Can't open file for writing.\")\r\n\r\n    The plugin will automatically create the directories foo\/ and foo\/bar\/ for you before Vim saves \r\n    the file, so you don't have to remember to do it manually.\r\n\r\n\r\nAlso available via git:\r\n    https:\/\/github.com\/DataWraith\/auto_mkdir","install_details":"Save auto_mkdir.vim into the plugin\/ directory of your runtime-path.","5":"Save auto_mkdir.vim into the plugin\/ directory of your runtime-path.","first_name":"Johannes","6":"Johannes","last_name":"Holzfu\u00c3\u009f","7":"Holzfu\u00c3\u009f","releases":[{"0":"3352","vim_version":"7.0","1":"7.0","script_version":"1.0.0","2":"1.0.0","version_comment":"Initial upload","3":"Initial upload","package":"auto_mkdir.vim","4":"auto_mkdir.vim","src_id":"14454","5":"14454","creation_date":"1291735312","6":"1291735312"}]},"3351":{"script_id":"3351","0":"3351","script_name":"qthelp","1":"qthelp","script_type":"utility","2":"utility","summary":"Allows you to open Qt help pages in browser from your C++ source code.","3":"Allows you to open Qt help pages in browser from your C++ source code.","description":"This plugin would allow you to open Qt help pages in browser from your C++ source code. Currently it can show help if the word underneath your cursor is a class name, a variable name or a class-member name.\r\n\r\nExamples:\r\n\r\nQStr|ing trackTitle, artistName;\r\nQString track|Title, artistName(\"Unknown\");\r\ntrack|Title = \"Unknown\";\r\nRunning command :QHelpOnThis will open help on QString.\r\n\r\ntrackTitle.ri|ght(10);\r\nRunning command :QHelpOnThis will open help on QString::right.\r\n\r\nRunning command :QHelp QPixmap::QPixmap will open help on\r\nQPixmap constructor.\r\n\r\nConfiguring:\r\n\r\ng:qthelp_browser - command to run your browser\r\ndefault: '' (so an error message will be printed if your try to use plugin)\r\nNote: on Windows use something like (notice 'start' at the beginning)\r\n'start c:\\\\Program files\\\\Mozilla Firefox\\\\firefox.exe'\r\nor Vim will be waiting until you close your browser.\r\n\r\nUsing:\r\n\r\n1. Make tags-file for your html-qthelp. Addition by DFrank: just go to <Qt-current-version-path>\/doc (say, D:\/Qt\/4.8.4\/doc), and run 'ctags -R .'.\r\n2. Add that tags-file into your 'tags' option (WARNING: doing this in your .vimrc file can slow down and pollute completion list for not Qt-projects).\r\n3. Setup g:qthelp_browser variable with the command to run browser.  The value is not escaped, this is up to you, so it's possible to specify parameter list along with command to be executed.  URL is appended to this command after a space.\r\n4. Optionally setup g:qthelp_tags variable with custom value for the 'tags' option, which will be used to look for Qt documentation tags.\r\n5. Map command QHelpOnThis on some hotkey.\r\n6. Use QHelp from command-line for faster navigating through help (to escape manual searching of needed section).\r\n\r\nLimitation:\r\n\r\nI didn\\'t found a way to determine inheritance hierarchy using tags so trying\r\nQStringList strlst;\r\nstrlst.in|sert(\"String\");\r\nwill open reference for QString, not for QList::insert.\r\n\r\nWarning:\r\n\r\nIn some cases it can take a while for searching definition (for example when it doesn't exist) if this happens hit Ctrl-C to break searching.\r\n\r\nAdvice:\r\n\r\nYou may be interesting in inccomplete (vimscript #3345) plugin, that can help to find header file you need.\r\n\r\nYou could always find the latest version on github: https:\/\/github.com\/xaizek\/vim-qthelp\r\nFeel free to contact me if you have any question or suggestions.","4":"This plugin would allow you to open Qt help pages in browser from your C++ source code. Currently it can show help if the word underneath your cursor is a class name, a variable name or a class-member name.\r\n\r\nExamples:\r\n\r\nQStr|ing trackTitle, artistName;\r\nQString track|Title, artistName(\"Unknown\");\r\ntrack|Title = \"Unknown\";\r\nRunning command :QHelpOnThis will open help on QString.\r\n\r\ntrackTitle.ri|ght(10);\r\nRunning command :QHelpOnThis will open help on QString::right.\r\n\r\nRunning command :QHelp QPixmap::QPixmap will open help on\r\nQPixmap constructor.\r\n\r\nConfiguring:\r\n\r\ng:qthelp_browser - command to run your browser\r\ndefault: '' (so an error message will be printed if your try to use plugin)\r\nNote: on Windows use something like (notice 'start' at the beginning)\r\n'start c:\\\\Program files\\\\Mozilla Firefox\\\\firefox.exe'\r\nor Vim will be waiting until you close your browser.\r\n\r\nUsing:\r\n\r\n1. Make tags-file for your html-qthelp. Addition by DFrank: just go to <Qt-current-version-path>\/doc (say, D:\/Qt\/4.8.4\/doc), and run 'ctags -R .'.\r\n2. Add that tags-file into your 'tags' option (WARNING: doing this in your .vimrc file can slow down and pollute completion list for not Qt-projects).\r\n3. Setup g:qthelp_browser variable with the command to run browser.  The value is not escaped, this is up to you, so it's possible to specify parameter list along with command to be executed.  URL is appended to this command after a space.\r\n4. Optionally setup g:qthelp_tags variable with custom value for the 'tags' option, which will be used to look for Qt documentation tags.\r\n5. Map command QHelpOnThis on some hotkey.\r\n6. Use QHelp from command-line for faster navigating through help (to escape manual searching of needed section).\r\n\r\nLimitation:\r\n\r\nI didn\\'t found a way to determine inheritance hierarchy using tags so trying\r\nQStringList strlst;\r\nstrlst.in|sert(\"String\");\r\nwill open reference for QString, not for QList::insert.\r\n\r\nWarning:\r\n\r\nIn some cases it can take a while for searching definition (for example when it doesn't exist) if this happens hit Ctrl-C to break searching.\r\n\r\nAdvice:\r\n\r\nYou may be interesting in inccomplete (vimscript #3345) plugin, that can help to find header file you need.\r\n\r\nYou could always find the latest version on github: https:\/\/github.com\/xaizek\/vim-qthelp\r\nFeel free to contact me if you have any question or suggestions.","install_details":"Just extract the archive into your ~\/.vim\/ or ~\/vimfiles\/ (~\/.vim\/bundle\/ or ~\/vimfiles\/bundle\/ if you use Pathogen (vimscript #2332)).","5":"Just extract the archive into your ~\/.vim\/ or ~\/vimfiles\/ (~\/.vim\/bundle\/ or ~\/vimfiles\/bundle\/ if you use Pathogen (vimscript #2332)).","first_name":"x","6":"x","last_name":"aizek","7":"aizek","releases":[{"0":"3351","vim_version":"7.0","1":"7.0","script_version":"1.1.6","2":"1.1.6","version_comment":"Fixed support for latest versions of Qt by the :QHelp command (thanks to Dmitry Frank).\r\nFixed regular expression for filtering help tags (thanks to Dmitry Frank).\r\nFixed issue with 'shellslash' option on Windows (thanks to Dmitry Frank).\r\nDon't escape g:qthelp_browser on invocation (thanks to Dmitry Frank).\r\nAdded g:qthelp_tags option (thanks to Dmitry Frank).","3":"Fixed support for latest versions of Qt by the :QHelp command (thanks to Dmitry Frank).\r\nFixed regular expression for filtering help tags (thanks to Dmitry Frank).\r\nFixed issue with 'shellslash' option on Windows (thanks to Dmitry Frank).\r\nDon't escape g:qthelp_browser on invocation (thanks to Dmitry Frank).\r\nAdded g:qthelp_tags option (thanks to Dmitry Frank).","package":"vim-qthelp-v1.1.6.zip","4":"vim-qthelp-v1.1.6.zip","src_id":"20358","5":"20358","creation_date":"1371244689","6":"1371244689"},{"0":"3351","vim_version":"7.0","1":"7.0","script_version":"1.1.1","2":"1.1.1","version_comment":"Fixed multiple load guard\r\nAdded support for latest versions of Qt (thanks to Dmitry Frank)\r\n","3":"Fixed multiple load guard\r\nAdded support for latest versions of Qt (thanks to Dmitry Frank)\r\n","package":"vim-qthelp-v1.1.1.zip","4":"vim-qthelp-v1.1.1.zip","src_id":"19611","5":"19611","creation_date":"1362857094","6":"1362857094"},{"0":"3351","vim_version":"7.0","1":"7.0","script_version":"1.0.0","2":"1.0.0","version_comment":"Initial upload","3":"Initial upload","package":"vim-qthelp-v1.0.0.zip","4":"vim-qthelp-v1.0.0.zip","src_id":"14453","5":"14453","creation_date":"1291731494","6":"1291731494"}]},"3350":{"script_id":"3350","0":"3350","script_name":"lastchange.vim","1":"lastchange.vim","script_type":"utility","2":"utility","summary":"automatically set time-stamp on modification ","3":"automatically set time-stamp on modification ","description":"Modified http:\/\/www.vim.org\/scripts\/script.php?script_id=259 and incorporated the following.\r\n\r\n* Fixed for VIM 7.X\r\n* Adjusted formatting of date\r\n* No longer truncate minutes to 00","4":"Modified http:\/\/www.vim.org\/scripts\/script.php?script_id=259 and incorporated the following.\r\n\r\n* Fixed for VIM 7.X\r\n* Adjusted formatting of date\r\n* No longer truncate minutes to 00","install_details":"Drop file in ~\/.vim\/plugins\/ and at the following within the top 20 lines of your code. The comment character depends on what you are working in. I used a VIM script comment in the example.\r\n\r\n\" Last Change: ?\r\n\r\nSave the file and re-open it. It should populate with a timestamp.","5":"Drop file in ~\/.vim\/plugins\/ and at the following within the top 20 lines of your code. The comment character depends on what you are working in. I used a VIM script comment in the example.\r\n\r\n\" Last Change: ?\r\n\r\nSave the file and re-open it. It should populate with a timestamp.","first_name":"Jesse","6":"Jesse","last_name":"Adams","7":"Adams","releases":[{"0":"3350","vim_version":"7.2","1":"7.2","script_version":"1.0.2","2":"1.0.2","version_comment":"Mixed minutes (was using month on accident)","3":"Mixed minutes (was using month on accident)","package":"lastchange.vim","4":"lastchange.vim","src_id":"14447","5":"14447","creation_date":"1291600796","6":"1291600796"},{"0":"3350","vim_version":"7.2","1":"7.2","script_version":"1.0.1","2":"1.0.1","version_comment":"Initial upload","3":"Initial upload","package":"lastchange.vim","4":"lastchange.vim","src_id":"14446","5":"14446","creation_date":"1291600380","6":"1291600380"}]},"3349":{"script_id":"3349","0":"3349","script_name":"devbox-dark-256","1":"devbox-dark-256","script_type":"color scheme","2":"color scheme","summary":"A 'Son of Obsidian'-like in 256 colors","3":"A 'Son of Obsidian'-like in 256 colors","description":"A colorscheme that looks like 'Son of Obsidian' but in 256 colors\r\n\r\nScreenshot http:\/\/img338.imageshack.us\/img338\/218\/screenshotvr0.jpg","4":"A colorscheme that looks like 'Son of Obsidian' but in 256 colors\r\n\r\nScreenshot http:\/\/img338.imageshack.us\/img338\/218\/screenshotvr0.jpg","install_details":"Just put the file in your ~\/.vim\/colors","5":"Just put the file in your ~\/.vim\/colors","first_name":"Dee Sub Wun","6":"Dee Sub Wun","last_name":".","7":".","releases":[{"0":"3349","vim_version":"7.2","1":"7.2","script_version":"1","2":"1","version_comment":"Initial upload","3":"Initial upload","package":"devbox-dark-256.vim","4":"devbox-dark-256.vim","src_id":"14442","5":"14442","creation_date":"1291555362","6":"1291555362"}]},"3348":{"script_id":"3348","0":"3348","script_name":"unite-gem","1":"unite-gem","script_type":"utility","2":"utility","summary":"A Unite.vim plugin to search\/install RubyGems packages easily, using gem command","3":"A Unite.vim plugin to search\/install RubyGems packages easily, using gem command","description":"A Unite.vim plugin to search\/install RubyGems packages easily, using gem command.\nSee details in the following pages.\n\n* http:\/\/github.com\/ujihisa\/unite-gem (development)\n\nDependency: gem command\n","4":"A Unite.vim plugin to search\/install RubyGems packages easily, using gem command.\nSee details in the following pages.\n\n* http:\/\/github.com\/ujihisa\/unite-gem (development)\n\nDependency: gem command\n","install_details":"After you install Shougo's unite.vim, unarchive the zip file into a directory that is under &rtp of your Vim, including ~\/.vim dir.\n","5":"After you install Shougo's unite.vim, unarchive the zip file into a directory that is under &rtp of your Vim, including ~\/.vim dir.\n","first_name":"ujihisa","6":"ujihisa","last_name":".","7":".","releases":[{"0":"3348","vim_version":"7.3","1":"7.3","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"unite-gem-1.0.zip","4":"unite-gem-1.0.zip","src_id":"14438","5":"14438","creation_date":"1291514193","6":"1291514193"}]},"3347":{"script_id":"3347","0":"3347","script_name":"chance-of-storm","1":"chance-of-storm","script_type":"color scheme","2":"color scheme","summary":"Dark colorscheme w\/ sunny colors","3":"Dark colorscheme w\/ sunny colors","description":"Sunny colors on dark background.\r\n\r\nTweaks for HAML, HTML, Markdown, Ruby, JavaScript, NERD_Tree\r\n\r\nScreenshot http:\/\/img835.imageshack.us\/img835\/6151\/accountspecscalacodejvm.png\r\n\r\nUsing pathogen? https:\/\/github.com\/mgutz\/vim-colors","4":"Sunny colors on dark background.\r\n\r\nTweaks for HAML, HTML, Markdown, Ruby, JavaScript, NERD_Tree\r\n\r\nScreenshot http:\/\/img835.imageshack.us\/img835\/6151\/accountspecscalacodejvm.png\r\n\r\nUsing pathogen? https:\/\/github.com\/mgutz\/vim-colors","install_details":"Copy to ~\/.vim\/colors\r\n\r\nNOTE: For GUI not console VIM.","5":"Copy to ~\/.vim\/colors\r\n\r\nNOTE: For GUI not console VIM.","first_name":"Mario","6":"Mario","last_name":"Gutierrez","7":"Gutierrez","releases":[{"0":"3347","vim_version":"7.0","1":"7.0","script_version":"0.1.2","2":"0.1.2","version_comment":"remove italics on string\r\nruby string interpolation\r\nidentifers more cyanish","3":"remove italics on string\r\nruby string interpolation\r\nidentifers more cyanish","package":"chance-of-storm.vim","4":"chance-of-storm.vim","src_id":"14458","5":"14458","creation_date":"1291786008","6":"1291786008"},{"0":"3347","vim_version":"7.0","1":"7.0","script_version":"0.1.1","2":"0.1.1","version_comment":"change identifer, statement colors","3":"change identifer, statement colors","package":"chance-of-storm.vim","4":"chance-of-storm.vim","src_id":"14444","5":"14444","creation_date":"1291578060","6":"1291578060"},{"0":"3347","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"chance-of-storm.vim","4":"chance-of-storm.vim","src_id":"14436","5":"14436","creation_date":"1291500413","6":"1291500413"}]},"3346":{"script_id":"3346","0":"3346","script_name":"screen_line_jumper","1":"screen_line_jumper","script_type":"utility","2":"utility","summary":"move to a visible line that end with a certain number ","3":"move to a visible line that end with a certain number ","description":"Assuming your vim window is like this:\r\n\r\n15 Some text\r\n16 Some other text here\r\n17 more Text                        | cursor here\r\n18 and some more text\r\n19 even more text\r\n20 more and more text\r\n21 more and more and more text\r\n22 more and more and more and more text\r\n23 text text text\r\n24 more text text and text\r\n25 more text\r\n26 even more text\r\n...\r\n\r\nwhere the numbers are the line number, and your cursor is currently on line 17\r\nLet say I want to jump to line 21 I either have to\r\n 1. press 21G - thats 4 key stroke\r\n 2. press j 4 times\r\n 3. press 4j (which is fast, but I have to do some extra calculation)\r\n \r\nThis script define a function to easily jump to a line that is visible on the vim window\r\n\r\n-----\r\n\r\nThis script defind 2 functions\r\n\r\nMoveLineNumberEndWith(number)\r\nMoveLineNumberEndWithBackward(number)\r\n\r\nthe first one will move to the first line where line number t end with <number> *and is currently visible*\r\n\r\nfor the above example if your cursor is on line 15 call\r\nMoveLineNumberEndWith(6) will move to line 16\r\ncall MoveLineNumberEndWith(6)  again will move to line 26\r\ncall MoveLineNumberEndWith(6) again will move back to line 16 if line 36 is not visible on your window\r\n\r\nThe backword version of the function works similarly but it jump backward.\r\n\r\nI have comment out some recommendation mapping in the file.\r\n\r\n\r\n","4":"Assuming your vim window is like this:\r\n\r\n15 Some text\r\n16 Some other text here\r\n17 more Text                        | cursor here\r\n18 and some more text\r\n19 even more text\r\n20 more and more text\r\n21 more and more and more text\r\n22 more and more and more and more text\r\n23 text text text\r\n24 more text text and text\r\n25 more text\r\n26 even more text\r\n...\r\n\r\nwhere the numbers are the line number, and your cursor is currently on line 17\r\nLet say I want to jump to line 21 I either have to\r\n 1. press 21G - thats 4 key stroke\r\n 2. press j 4 times\r\n 3. press 4j (which is fast, but I have to do some extra calculation)\r\n \r\nThis script define a function to easily jump to a line that is visible on the vim window\r\n\r\n-----\r\n\r\nThis script defind 2 functions\r\n\r\nMoveLineNumberEndWith(number)\r\nMoveLineNumberEndWithBackward(number)\r\n\r\nthe first one will move to the first line where line number t end with <number> *and is currently visible*\r\n\r\nfor the above example if your cursor is on line 15 call\r\nMoveLineNumberEndWith(6) will move to line 16\r\ncall MoveLineNumberEndWith(6)  again will move to line 26\r\ncall MoveLineNumberEndWith(6) again will move back to line 16 if line 36 is not visible on your window\r\n\r\nThe backword version of the function works similarly but it jump backward.\r\n\r\nI have comment out some recommendation mapping in the file.\r\n\r\n\r\n","install_details":"put it in your .vim\/plugin\/","5":"put it in your .vim\/plugin\/","first_name":"Vinh","6":"Vinh","last_name":"Tran","7":"Tran","releases":[{"0":"3346","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"screen_line_jumper.vim","4":"screen_line_jumper.vim","src_id":"14410","5":"14410","creation_date":"1291210158","6":"1291210158"}]},"3345":{"script_id":"3345","0":"3345","script_name":"inccomplete","1":"inccomplete","script_type":"utility","2":"utility","summary":"Plugin for C\/C++\/ObjC\/ObjC++ include directive completion.","3":"Plugin for C\/C++\/ObjC\/ObjC++ include directive completion.","description":"This is a completion plugin for C\/C++\/ObjC\/ObjC++ preprocessor's #include directive.\r\n\r\n\"\" completion lists header files which are defined by hpp or h extension.\r\n\r\n<> completion lists files that have hpp or h extension or don't have any.\r\n\r\nSources for \"\" completion are configured via g:inccomplete_localsources and can include:\r\n\r\n * paths relative to the directory of current file\r\n * '-I' keys from g:clang_user_options\r\n * '-I' keys from b:clang_user_options\r\n\r\nAdditional sources for \"\" completion can be specified via b:inccomplete_roots (this is a list equivalent of older b:inccomplete_root string option).\r\n\r\nSources for <> completion are:\r\n\r\n * 'path' option (on *nix it's set to '\/usr\/include' by default, but on Windows you should set it to the right directories manually)\r\n * g:clang_user_options ('-I' keys)\r\n * b:clang_user_options ('-I' keys)\r\n\r\nIf you think it's faster to use find than builtin VimL functions, there is an option for that.\r\n\r\nThe latest version can be found at:\r\n * https:\/\/github.com\/xaizek\/vim-inccomplete\r\n * https:\/\/code.reversed.top\/user\/xaizek\/vim-inccomplete\r\n","4":"This is a completion plugin for C\/C++\/ObjC\/ObjC++ preprocessor's #include directive.\r\n\r\n\"\" completion lists header files which are defined by hpp or h extension.\r\n\r\n<> completion lists files that have hpp or h extension or don't have any.\r\n\r\nSources for \"\" completion are configured via g:inccomplete_localsources and can include:\r\n\r\n * paths relative to the directory of current file\r\n * '-I' keys from g:clang_user_options\r\n * '-I' keys from b:clang_user_options\r\n\r\nAdditional sources for \"\" completion can be specified via b:inccomplete_roots (this is a list equivalent of older b:inccomplete_root string option).\r\n\r\nSources for <> completion are:\r\n\r\n * 'path' option (on *nix it's set to '\/usr\/include' by default, but on Windows you should set it to the right directories manually)\r\n * g:clang_user_options ('-I' keys)\r\n * b:clang_user_options ('-I' keys)\r\n\r\nIf you think it's faster to use find than builtin VimL functions, there is an option for that.\r\n\r\nThe latest version can be found at:\r\n * https:\/\/github.com\/xaizek\/vim-inccomplete\r\n * https:\/\/code.reversed.top\/user\/xaizek\/vim-inccomplete\r\n","install_details":"Just extract vim-inccomplete-*.zip into your ~\/.vim\/ or ~\/vimfiles\/ (~\/.vim\/bundle\/ or ~\/vimfiles\/bundle\/ if you use Pathogen (vimscript #2332)). Nothing specific compared to other plugins.\r\n\r\nThis plugin can be used along with clang_complete plugin (vimscript #3302). And maybe with some others completion plugins that I haven\\'t tested (inccomplete should work if it\\'ll be loaded after some other completion plugin).","5":"Just extract vim-inccomplete-*.zip into your ~\/.vim\/ or ~\/vimfiles\/ (~\/.vim\/bundle\/ or ~\/vimfiles\/bundle\/ if you use Pathogen (vimscript #2332)). Nothing specific compared to other plugins.\r\n\r\nThis plugin can be used along with clang_complete plugin (vimscript #3302). And maybe with some others completion plugins that I haven\\'t tested (inccomplete should work if it\\'ll be loaded after some other completion plugin).","first_name":"x","6":"x","last_name":"aizek","7":"aizek","releases":[{"0":"3345","vim_version":"7.3","1":"7.3","script_version":"1.8.52","2":"1.8.52","version_comment":"* Prevent error on `<\/` and `\"\/` inputs\r\n* Fix adding descendants on \"..\/...\" completion\r\n* Don't treat cygwin as Windows\r\n* Fix paths with spaces on Windows\r\n* Trigger completion on \/ or \\ right before \" or >\r\n* Add README, some documentation updates\r\n* Unescape paths obtained from clang_complete\r\n* Cut off trailing spaces on filtering\r\n* Add g:inccomplete_localsources option\r\n* Fix nested directories in \"\" being shown as files\r\n* Sort directories in front of files\r\n* Group files from the same source together\r\n* Use custom sets of extensions depending on language\r\n* Add b:inccomplete_roots option","3":"* Prevent error on `<\/` and `\"\/` inputs\r\n* Fix adding descendants on \"..\/...\" completion\r\n* Don't treat cygwin as Windows\r\n* Fix paths with spaces on Windows\r\n* Trigger completion on \/ or \\ right before \" or >\r\n* Add README, some documentation updates\r\n* Unescape paths obtained from clang_complete\r\n* Cut off trailing spaces on filtering\r\n* Add g:inccomplete_localsources option\r\n* Fix nested directories in \"\" being shown as files\r\n* Sort directories in front of files\r\n* Group files from the same source together\r\n* Use custom sets of extensions depending on language\r\n* Add b:inccomplete_roots option","package":"vim-inccomplete-1.8.52.zip","4":"vim-inccomplete-1.8.52.zip","src_id":"26461","5":"26461","creation_date":"1555707487","6":"1555707487"},{"0":"3345","vim_version":"7.3","1":"7.3","script_version":"1.7.40","2":"1.7.40","version_comment":"When defined, use b:inccomplete_root to complete local includes relative to project root.\r\nFix completion, which had some issues.\r\nEnable plugin for filetypes like cpp.doxygen.\r\nParse g:clang_... even when clang_complete isn't installed.\r\nBe more YCM-friendly.\r\nFix work in unnamed buffers.","3":"When defined, use b:inccomplete_root to complete local includes relative to project root.\r\nFix completion, which had some issues.\r\nEnable plugin for filetypes like cpp.doxygen.\r\nParse g:clang_... even when clang_complete isn't installed.\r\nBe more YCM-friendly.\r\nFix work in unnamed buffers.","package":"vim-inccomplete-1.7.40.zip","4":"vim-inccomplete-1.7.40.zip","src_id":"23564","5":"23564","creation_date":"1440864209","6":"1440864209"},{"0":"3345","vim_version":"7.0","1":"7.0","script_version":"1.6.32","2":"1.6.32","version_comment":"Add option to avoid auto-filling of the first match. Thanks to drougas (at cs dot ucr dot edu).","3":"Add option to avoid auto-filling of the first match. Thanks to drougas (at cs dot ucr dot edu).","package":"vim-inccomplete-1.6.32.zip","4":"vim-inccomplete-1.6.32.zip","src_id":"18819","5":"18819","creation_date":"1350419003","6":"1350419003"},{"0":"3345","vim_version":"7.0","1":"7.0","script_version":"1.6.31","2":"1.6.31","version_comment":"Ignore directories which names start with a dot.","3":"Ignore directories which names start with a dot.","package":"vim-inccomplete-1.6.31.zip","4":"vim-inccomplete-1.6.31.zip","src_id":"18654","5":"18654","creation_date":"1348296029","6":"1348296029"},{"0":"3345","vim_version":"7.0","1":"7.0","script_version":"1.6.30","2":"1.6.30","version_comment":"Don't add directory to the list of matches when listing files in it","3":"Don't add directory to the list of matches when listing files in it","package":"vim-inccomplete-1.6.30.zip","4":"vim-inccomplete-1.6.30.zip","src_id":"18529","5":"18529","creation_date":"1346577089","6":"1346577089"},{"0":"3345","vim_version":"7.0","1":"7.0","script_version":"1.6.29","2":"1.6.29","version_comment":"Add option to append slashes to directories (g:inccomplete_appendslash).","3":"Add option to append slashes to directories (g:inccomplete_appendslash).","package":"vim-inccomplete-1.6.29.zip","4":"vim-inccomplete-1.6.29.zip","src_id":"17792","5":"17792","creation_date":"1334776760","6":"1334776760"},{"0":"3345","vim_version":"7.0","1":"7.0","script_version":"1.6.28","2":"1.6.28","version_comment":"Avoid delay on adding comments after #include\r\nFix parsing of same directories several times\r\nOptimize '#include <|' case as most useful","3":"Avoid delay on adding comments after #include\r\nFix parsing of same directories several times\r\nOptimize '#include <|' case as most useful","package":"vim-inccomplete-1.6.28.zip","4":"vim-inccomplete-1.6.28.zip","src_id":"17785","5":"17785","creation_date":"1334694619","6":"1334694619"},{"0":"3345","vim_version":"7.0","1":"7.0","script_version":"1.6.25","2":"1.6.25","version_comment":"Fix completing of <a\/b\/...> on Windows","3":"Fix completing of <a\/b\/...> on Windows","package":"vim-inccomplete-1.6.25.zip","4":"vim-inccomplete-1.6.25.zip","src_id":"17440","5":"17440","creation_date":"1329081155","6":"1329081155"},{"0":"3345","vim_version":"7.0","1":"7.0","script_version":"1.6.24","2":"1.6.24","version_comment":"Don't require autochdir","3":"Don't require autochdir","package":"vim-inccomplete-1.6.24.zip","4":"vim-inccomplete-1.6.24.zip","src_id":"17164","5":"17164","creation_date":"1325883920","6":"1325883920"},{"0":"3345","vim_version":"7.0","1":"7.0","script_version":"1.5.24","2":"1.5.24","version_comment":"Fix bug with path completion while completing \"..\/\r\nDon't show second column on \"-completion\r\nAdd slash to directories in completion menu","3":"Fix bug with path completion while completing \"..\/\r\nDon't show second column on \"-completion\r\nAdd slash to directories in completion menu","package":"vim-inccomplete-1.5.24.zip","4":"vim-inccomplete-1.5.24.zip","src_id":"17155","5":"17155","creation_date":"1325785559","6":"1325785559"},{"0":"3345","vim_version":"7.0","1":"7.0","script_version":"1.5.21","2":"1.5.21","version_comment":"Real Vim-style documentation\r\nFix bug with '#include \"..\/foo\"' on Windows\r\nAdd possibility to add directories to the list\r\nImplement file searching using VimL","3":"Real Vim-style documentation\r\nFix bug with '#include \"..\/foo\"' on Windows\r\nAdd possibility to add directories to the list\r\nImplement file searching using VimL","package":"vim-inccomplete-1.5.21.zip","4":"vim-inccomplete-1.5.21.zip","src_id":"16657","5":"16657","creation_date":"1318436785","6":"1318436785"},{"0":"3345","vim_version":"7.0","1":"7.0","script_version":"1.3.20","2":"1.3.20","version_comment":"Fixed little bug with slash type on linux.\r\nBetter performance.","3":"Fixed little bug with slash type on linux.\r\nBetter performance.","package":"vim-inccomplete-1.3.20.zip","4":"vim-inccomplete-1.3.20.zip","src_id":"15794","5":"15794","creation_date":"1307020204","6":"1307020204"},{"0":"3345","vim_version":"7.0","1":"7.0","script_version":"1.3.18","2":"1.3.18","version_comment":"Added inccomplete_addclosebracket option.\r\nFixed completion of paths like ..\/foo\/bar.h and ..\/foobar.h.\r\nFixed sorting.\r\nAdded inccomplete_sort option (to allow case insensitive sorting).\r\n\r\n","3":"Added inccomplete_addclosebracket option.\r\nFixed completion of paths like ..\/foo\/bar.h and ..\/foobar.h.\r\nFixed sorting.\r\nAdded inccomplete_sort option (to allow case insensitive sorting).\r\n\r\n","package":"vim-inccomplete-1.3.18.tgz","4":"vim-inccomplete-1.3.18.tgz","src_id":"15506","5":"15506","creation_date":"1303499836","6":"1303499836"},{"0":"3345","vim_version":"7.0","1":"7.0","script_version":"1.3.12","2":"1.3.12","version_comment":"Follow symbolic links.\r\nMore intelligent slash type detection.","3":"Follow symbolic links.\r\nMore intelligent slash type detection.","package":"vim-inccomplete-1.3.12.tgz","4":"vim-inccomplete-1.3.12.tgz","src_id":"15467","5":"15467","creation_date":"1303051321","6":"1303051321"},{"0":"3345","vim_version":"7.0","1":"7.0","script_version":"1.3.10","2":"1.3.10","version_comment":"+Completion of subdirectories.\r\nBug Fix: '-' symbol in filenames for <> completion is now allowed.","3":"+Completion of subdirectories.\r\nBug Fix: '-' symbol in filenames for <> completion is now allowed.","package":"vim-inccomplete-1.3.10.zip","4":"vim-inccomplete-1.3.10.zip","src_id":"14846","5":"14846","creation_date":"1295889255","6":"1295889255"},{"0":"3345","vim_version":"7.0","1":"7.0","script_version":"1.2.9","2":"1.2.9","version_comment":"Bug Fix: invalid parsing of clang_complete options. Another way to add closing bracket. Now cache is global. Code refactoring.","3":"Bug Fix: invalid parsing of clang_complete options. Another way to add closing bracket. Now cache is global. Code refactoring.","package":"vim-inccomplete-1.2.9.zip","4":"vim-inccomplete-1.2.9.zip","src_id":"14706","5":"14706","creation_date":"1294487492","6":"1294487492"},{"0":"3345","vim_version":"7.0","1":"7.0","script_version":"1.1.7","2":"1.1.7","version_comment":"Now b:clang_user_options and g:clang_user_options are parsed for include directories.","3":"Now b:clang_user_options and g:clang_user_options are parsed for include directories.","package":"vim-inccomplete-1.1.7.zip","4":"vim-inccomplete-1.1.7.zip","src_id":"14692","5":"14692","creation_date":"1294336828","6":"1294336828"},{"0":"3345","vim_version":"7.0","1":"7.0","script_version":"1.0.7","2":"1.0.7","version_comment":"Automatically add closing brace.","3":"Automatically add closing brace.","package":"vim-inccomplete-1.0.7.zip","4":"vim-inccomplete-1.0.7.zip","src_id":"14675","5":"14675","creation_date":"1294057089","6":"1294057089"},{"0":"3345","vim_version":"7.0","1":"7.0","script_version":"1.0.6","2":"1.0.6","version_comment":"Bug Fix: incorrect comparison of paths on Windows.","3":"Bug Fix: incorrect comparison of paths on Windows.","package":"vim-inccomplete-1.0.6.zip","4":"vim-inccomplete-1.0.6.zip","src_id":"14579","5":"14579","creation_date":"1292780076","6":"1292780076"},{"0":"3345","vim_version":"7.0","1":"7.0","script_version":"1.0.5","2":"1.0.5","version_comment":"Missed old variable names have been fixed!\r\nUser-completion has been replaced with omni-completion to make it work fine with new versions of clang_complete.\r\nDon't complete after second \" in the line.\r\nA little bug in ICComplete with l:user has been fixed.","3":"Missed old variable names have been fixed!\r\nUser-completion has been replaced with omni-completion to make it work fine with new versions of clang_complete.\r\nDon't complete after second \" in the line.\r\nA little bug in ICComplete with l:user has been fixed.","package":"vim-inccomplete-1.0.5.zip","4":"vim-inccomplete-1.0.5.zip","src_id":"14514","5":"14514","creation_date":"1292344745","6":"1292344745"},{"0":"3345","vim_version":"7.0","1":"7.0","script_version":"1.0.2","2":"1.0.2","version_comment":"Bug Fix: ignore empty 'path' components.","3":"Bug Fix: ignore empty 'path' components.","package":"vim-inccomplete-1.0.2.zip","4":"vim-inccomplete-1.0.2.zip","src_id":"14440","5":"14440","creation_date":"1291550950","6":"1291550950"},{"0":"3345","vim_version":"7.0","1":"7.0","script_version":"1.0.1","2":"1.0.1","version_comment":"Bug Fix: Cached <>-include list wasn't updated after changing 'path' option.","3":"Bug Fix: Cached <>-include list wasn't updated after changing 'path' option.","package":"vim-inccomplete-1.0.1.zip","4":"vim-inccomplete-1.0.1.zip","src_id":"14426","5":"14426","creation_date":"1291392326","6":"1291392326"},{"0":"3345","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"vim-inccomplete.zip","4":"vim-inccomplete.zip","src_id":"14409","5":"14409","creation_date":"1291145954","6":"1291145954"}]},"3344":{"script_id":"3344","0":"3344","script_name":"preview","1":"preview","script_type":"utility","2":"utility","summary":"Plugin for previewing markup files(markdown,rdoc,textile,html)","3":"Plugin for previewing markup files(markdown,rdoc,textile,html)","description":"Preview plugin is a tool developed to help you to preview markup files such as *.markdown, *.rdoc, *.textile and *.html when you are editing them. It builds html files and opens them in your browser.\r\n\r\nThe plugin requires a builtin ruby interpreter. It means that your Vim should be compiled with '--enable-rubyinterp' option. To find out does you Vim have builtin ruby interpreter you can do the next:\r\n    :echo has('ruby')\r\nIf output is '1' the ruby interpreter is builtin. The second thing you should verify is that you have installed all necessary ruby gems. \r\n\r\nSupported formats and dependecies:\r\n    * markdown(md, mkd, mkdn, mdown) - depends on 'bluecloth' ruby gem\r\n    * rdoc -  depends on 'github-markup' ruby gem\r\n    * textile - depends on 'RedCloth' ruby gem\r\n    * ronn  -depends on 'ronn' ruby gem\r\n    * html(htm) - no dependecies\r\n   * reStructuredText(rst) - depends on 'RbST' ruby gem and 'rst2html' system util\r\n\r\nHomepage: https:\/\/github.com\/greyblake\/vim-preview\r\n\r\nCredits:\r\n    Donald Ephraim Curtis (support for OSX, fixing bugs)\r\n    Sung Pae (fixing bugs)\r\n    Rdark (support for ronn file format)\r\n\r\n\r\n","4":"Preview plugin is a tool developed to help you to preview markup files such as *.markdown, *.rdoc, *.textile and *.html when you are editing them. It builds html files and opens them in your browser.\r\n\r\nThe plugin requires a builtin ruby interpreter. It means that your Vim should be compiled with '--enable-rubyinterp' option. To find out does you Vim have builtin ruby interpreter you can do the next:\r\n    :echo has('ruby')\r\nIf output is '1' the ruby interpreter is builtin. The second thing you should verify is that you have installed all necessary ruby gems. \r\n\r\nSupported formats and dependecies:\r\n    * markdown(md, mkd, mkdn, mdown) - depends on 'bluecloth' ruby gem\r\n    * rdoc -  depends on 'github-markup' ruby gem\r\n    * textile - depends on 'RedCloth' ruby gem\r\n    * ronn  -depends on 'ronn' ruby gem\r\n    * html(htm) - no dependecies\r\n   * reStructuredText(rst) - depends on 'RbST' ruby gem and 'rst2html' system util\r\n\r\nHomepage: https:\/\/github.com\/greyblake\/vim-preview\r\n\r\nCredits:\r\n    Donald Ephraim Curtis (support for OSX, fixing bugs)\r\n    Sung Pae (fixing bugs)\r\n    Rdark (support for ronn file format)\r\n\r\n\r\n","install_details":"Unzip in ~\/.vim (~\\vimfiles on Windows). Use :helptags ~\/.vim\/doc to enable :help.","5":"Unzip in ~\/.vim (~\\vimfiles on Windows). Use :helptags ~\/.vim\/doc to enable :help.","first_name":"Sergey","6":"Sergey","last_name":"Potapov","7":"Potapov","releases":[{"0":"3344","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"New stylesheet. Use redcarpet for markdown instead of BlueCloth.","3":"New stylesheet. Use redcarpet for markdown instead of BlueCloth.","package":"vim-preview-1.0.zip","4":"vim-preview-1.0.zip","src_id":"21559","5":"21559","creation_date":"1393764548","6":"1393764548"},{"0":"3344","vim_version":"7.0","1":"7.0","script_version":"0.9","2":"0.9","version_comment":"Fixed bug: Define type using filetype option","3":"Fixed bug: Define type using filetype option","package":"vim-preview-0.9.zip","4":"vim-preview-0.9.zip","src_id":"17548","5":"17548","creation_date":"1330559261","6":"1330559261"},{"0":"3344","vim_version":"7.0","1":"7.0","script_version":"0.8","2":"0.8","version_comment":"Returned back RST","3":"Returned back RST","package":"vim-preview-0.8.zip","4":"vim-preview-0.8.zip","src_id":"16798","5":"16798","creation_date":"1320357636","6":"1320357636"},{"0":"3344","vim_version":"7.0","1":"7.0","script_version":"0.7","2":"0.7","version_comment":"Support for reStructuredText","3":"Support for reStructuredText","package":"vim-preview-0.7.zip","4":"vim-preview-0.7.zip","src_id":"15354","5":"15354","creation_date":"1301702407","6":"1301702407"},{"0":"3344","vim_version":"7.0","1":"7.0","script_version":"0.6","2":"0.6","version_comment":"Added ronn format support.","3":"Added ronn format support.","package":"vim-preview-0.6.zip","4":"vim-preview-0.6.zip","src_id":"15274","5":"15274","creation_date":"1300782695","6":"1300782695"},{"0":"3344","vim_version":"7.0","1":"7.0","script_version":"0.5","2":"0.5","version_comment":"No more zombies","3":"No more zombies","package":"vim-preview-0.5.zip","4":"vim-preview-0.5.zip","src_id":"14697","5":"14697","creation_date":"1294382630","6":"1294382630"},{"0":"3344","vim_version":"7.0","1":"7.0","script_version":"0.4","2":"0.4","version_comment":"Fixed bugs: Supporting filenames with spaces.","3":"Fixed bugs: Supporting filenames with spaces.","package":"vim-preview-0.4.zip","4":"vim-preview-0.4.zip","src_id":"14680","5":"14680","creation_date":"1294145160","6":"1294145160"},{"0":"3344","vim_version":"7.0","1":"7.0","script_version":"0.3","2":"0.3","version_comment":"Fixed bugs with Safari. Extended CSS stiles.","3":"Fixed bugs with Safari. Extended CSS stiles.","package":"vim-preview-0.3.zip","4":"vim-preview-0.3.zip","src_id":"14671","5":"14671","creation_date":"1294005029","6":"1294005029"},{"0":"3344","vim_version":"7.0","1":"7.0","script_version":"0.2","2":"0.2","version_comment":"Added more options for customizing.\r\nNew commands are available for mapping.\r\nFixed a little bug.","3":"Added more options for customizing.\r\nNew commands are available for mapping.\r\nFixed a little bug.","package":"vim-preview.zip","4":"vim-preview.zip","src_id":"14390","5":"14390","creation_date":"1290993404","6":"1290993404"},{"0":"3344","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"vim-preview.zip","4":"vim-preview.zip","src_id":"14389","5":"14389","creation_date":"1290917954","6":"1290917954"}]},"3343":{"script_id":"3343","0":"3343","script_name":"stackoverflow.vim","1":"stackoverflow.vim","script_type":"color scheme","2":"color scheme","summary":"Stackoverflow\\'s code highlights (gui)","3":"Stackoverflow\\'s code highlights (gui)","description":"Scheme emulating StackOverflow\\'s code highlights.\r\n\r\nWorks for most languages (python, html, css, c++)\r\n\r\nScreenshot:\r\nhttp:\/\/www.flickr.com\/photos\/28853165@N05\/5216106911\/\r\n\r\nScreenshot with syntax matching (some additional highlights closer to stackoverflow.com) patterns:\r\nhttp:\/\/www.flickr.com\/photos\/28853165@N05\/5216654746\/","4":"Scheme emulating StackOverflow\\'s code highlights.\r\n\r\nWorks for most languages (python, html, css, c++)\r\n\r\nScreenshot:\r\nhttp:\/\/www.flickr.com\/photos\/28853165@N05\/5216106911\/\r\n\r\nScreenshot with syntax matching (some additional highlights closer to stackoverflow.com) patterns:\r\nhttp:\/\/www.flickr.com\/photos\/28853165@N05\/5216654746\/","install_details":"drop file into your vim\/colors directory\r\n\r\nadd the following line to your vimrc (if you want additional syntax matching to work):\r\nau BufRead *.java,*.py,*.cpp,*.m,*.h,*.js runtime! colors\/stackoverflow.vim","5":"drop file into your vim\/colors directory\r\n\r\nadd the following line to your vimrc (if you want additional syntax matching to work):\r\nau BufRead *.java,*.py,*.cpp,*.m,*.h,*.js runtime! colors\/stackoverflow.vim","first_name":"Paul","6":"Paul","last_name":"L","7":"L","releases":[{"0":"3343","vim_version":"7.0","1":"7.0","script_version":"1.1","2":"1.1","version_comment":"some more accurate highlighting with syntax matching patterns","3":"some more accurate highlighting with syntax matching patterns","package":"stackoverflow.vim","4":"stackoverflow.vim","src_id":"14391","5":"14391","creation_date":"1290996956","6":"1290996956"},{"0":"3343","vim_version":"7.0","1":"7.0","script_version":"1","2":"1","version_comment":"Initial upload","3":"Initial upload","package":"stackoverflow.vim","4":"stackoverflow.vim","src_id":"14382","5":"14382","creation_date":"1290781413","6":"1290781413"}]},"3342":{"script_id":"3342","0":"3342","script_name":"VimOrganizer","1":"VimOrganizer","script_type":"ftplugin","2":"ftplugin","summary":"An Emacs' Org-mode clone for Vim","3":"An Emacs' Org-mode clone for Vim","description":"VimOrganizer version 0.31, November 8, 2011.  Requires Vim version that \r\nis compiled with support for folding and tabs.  Conceal will\r\nbe taken advantage of if working with Vim73 supporting conceal.  \r\n(Also, I STRONGLY suggest that you apply a patch to Vim so that \r\nfolded headings can have level-dependent highlighting, \r\npatch for Vim73 is in contrib directory of the download.  If you're on\r\nWindows contact me and I should be able to provide you with an \r\nexecutable.  If I hadn't been able to make Vim do this I would have \r\nbitten the bullet and moved to Emacs, as much as I hate editing in Emacs.)\r\n \r\nVideo showing some of the new features is here:\r\nhttp:\/\/vimeo.com\/31531308 (showing colorscheme support, narrowing, links,\r\n                                                 general document authoring support)\r\nhttp:\/\/vimeo.com\/31564708 (showing excellent export to \r\n                                                  LibreOffice\/MS Word format)\r\n\r\nVimOrganizer is a Vim filetype plugin that attempts to clone Emacs' Org-mode.  \r\nIt is currently (November 2011) in an alpha-stage, both in terms of (1) the \r\nbreadth and depth of Org-mode features it clones and (2) the stability of its\r\noperation.  It is nevertheless very usable.\r\n\r\nSome of the ADDITIONS AND IMPROVEMENTS since previous (December 2010) version:\r\n   -- Adjusts to any colorscheme\r\n   -- Org menu in gvim.\r\n   -- \"Dashboards\" to assist with Date entry, Columns, Tables,\r\n      Agenda searches, and exporting.\r\n   -- VimOrganizer help file to install in Vim.\r\n   -- Better compatibility with Org-mode files.  Open, edit, and save same \r\n      files in Org-mode and\/or VimOrganizer with (some) of the functionality and\r\n      configuration-specific options of Org-mode supported in VimOrganizer.\r\n   -- Support for Org-mode style links (as well as use of 'Conceal' in Vim73\r\n                                        to hide link brackets and \r\n                                        descriptions)\r\n   -- Easy to use Org-like column mode, including column headings,\r\n      inherited columns, support for Org column blocks, and ability to \r\n      specify a list of custom column specs to apply in any buffer.\r\n   -- Org-like narrowing of code blocks and subtrees\r\n   -- Support for Org-like specifications of TODOS, tags, dates,\r\n      including support for Org-compatible config lines in a file.\r\n   -- Support for Org-like CATEGORIES, both in specification and in \r\n      their inherited behavior.\r\n   -- Search specification in Agenda searches is now nearly identical\r\n      to specification of searches in Org-mode.\r\n   -- User can specify list of commonly used custom agenda searches.\r\n   -- Clockin, clockout, and (when a running Emacs server is available,\r\n      clocktable block creation and updates.\r\n   -- Org-like \"refiling\"\r\n   -- Easy creation and editing of tables, as well as (when a running Emacs \r\n      server is available) manipulation and evaluation of tables, including\r\n      all spreadsheet functionality in Org-mode.\r\n   -- \"Live\" block evaluation (when a running Emacs server is available) \r\n   -- Support for nearly all the export types and export options \r\n      available in Org-mode (when running Emacs server is available)\r\n   -- Call out to an Emacs server to do \"tangling\" (literate programming).\r\n   -- Many bug fixes and small improvements\r\n\r\nOrg-mode, and thus VimOrganizer, is a text-editor plugin\/application that can \r\nbe used for (1) keeping notes, (2) maintaining TODO lists, (3) planning \r\nprojects, and\/or (4) authoring and publishing documents, including support for \r\nliterate programming and \"reproducible research\".  Like Org-mode, VimOrganizer\r\ndoes this by implementing a flexible plain-text system with a lightly \r\nstructured document format.  Org-mode has been in constant development for \r\nseven or eight years, and continues to be developed.  Work on VimOrganizer is \r\nlikewise ongoing, but VimOrganizer is at present a smaller and less ambitious \r\nproject than Org-mode.\r\n\r\nFile formats and basic workflows for VimOrganizer and Org-mode are very \r\nsimilar (files auto-convert as part of loading process) and VimOrganizer \r\nactually calls out to an Emacs' Org-mode server to \r\nimplement important features, e.g., exporting to pdf format for printing.\r\n\r\nThus, to make full use of VimOrganizer you will want to have an Emacs' \r\nserver running alongside.  In most cases this requires little knowledge of \r\nEmacs other than how to start it up and add a few lines to the '.emacs' file, \r\nEmacs' counterpart to Vim's '.vimrc'.  (You can even edit the .emacs file in \r\nVim.)  VimOrganizer is focused on leveraging Org-mode by accessing it via\r\nan Emacs server, and re-implementing in Vim only what is necessary and makes \r\nsense. \r\n\r\nVimOrganizer also lets Vim users access Org-babel, a subproject of \r\nOrg-mode that allows execution of source-code blocks in org-format \r\ndocuments.  Uses for Org-babel range from writing technical research papers to \r\nsimply using a VimOrganizer document as a \"language-scratchpad\".  Over \r\ntwenty languages are supported, including C, R, Lisp, Python, Perl, Ruby, \r\nand others.  VimOrganizer calls out to a running Emacs server for Org-babel \r\nprocessing; functionality and speed are essentially the same as \r\nwhen editing with Org-mode in Emacs.\r\n\r\nVimOrganizer has a first draft of a Vim help file, but the best first step in\r\nlearning about VimOrganizer is to learn about Emacs' Org-mode.  VimOrganizer \r\nuses the same basic concepts but implements them within the context of Vim \r\n(and with a reduced feature set).  Org-mode's main documentation and \r\nsupport newsgroup are found here:\r\nOrg-mode Main Manual:  http:\/\/orgmode.org\/manual\/index.html\r\nOrg-mode Compact Guide: http:\/\/orgmode.org\/guide\/index.html\r\nOrg-mode support:  http:\/\/news.gmane.org\/gmane.emacs.orgmode \r\nOrg-babel information: http:\/\/orgmode.org\/worg\/org-contrib\/babel\/ \r\n\r\nVimOrganizer help can be found here:\r\nhttps:\/\/github.com\/hsitz\/VimOrganizer\/blob\/master\/doc\/vimorg.txt\r\n\r\n==========================\r\nINSTALLATION INSTRUCTIONS\r\n===========================\r\nhttps:\/\/github.com\/hsitz\/VimOrganizer\/blob\/master\/INSTALL.txt\r\n\r\n\r\nQUESTIONS, COMMENTS, SUGGESTIONS\r\n================================\r\nQuestions, comments, and suggestions regarding VimOrganizer are always \r\nappreciated.  The preferred place for those is in the VimOrganizer newsgroup \r\nhere:\r\nhttp:\/\/groups.google.com\/group\/vimorganizer\/topics\r\n\r\nVimOrganizer project files are maintained at github and the version \r\nthere may be more recent than the files at vim.org:\r\nhttps:\/\/github.com\/hsitz\/VimOrganizer\r\n\r\n----------------------------------------------------------------\r\nNOTE:  some code from other Vim plugins has been incorporated into the\r\nVimOrganizer script files.  Do NOT download these plugins to use them \r\nwith VimOrganizer; since VimOrganizer does not call out to them in any way:\r\n\r\n1.  Charles Campbell's great calendar utilities \r\n2.  Table editing routines from Maxim Kim's excellent vimwiki plugin. \r\n    These are really quite nice (seem to be inspired by Org-mode's\r\n    own table-editing stuff) and deserve to be offered as a separate\r\n    plugin of their own, not dependent on any larger project. (If\r\n    VimOrganizer is not quite the sort of plugin you're looking for then\r\n    vimwiki may be.) \r\n----------------------------------------------------------------\r\n\r\nVimOrganizer page at vim.org:\r\nhttp:\/\/www.vim.org\/scripts\/script.php?script_id=3342\r\n\r\n\r\n","4":"VimOrganizer version 0.31, November 8, 2011.  Requires Vim version that \r\nis compiled with support for folding and tabs.  Conceal will\r\nbe taken advantage of if working with Vim73 supporting conceal.  \r\n(Also, I STRONGLY suggest that you apply a patch to Vim so that \r\nfolded headings can have level-dependent highlighting, \r\npatch for Vim73 is in contrib directory of the download.  If you're on\r\nWindows contact me and I should be able to provide you with an \r\nexecutable.  If I hadn't been able to make Vim do this I would have \r\nbitten the bullet and moved to Emacs, as much as I hate editing in Emacs.)\r\n \r\nVideo showing some of the new features is here:\r\nhttp:\/\/vimeo.com\/31531308 (showing colorscheme support, narrowing, links,\r\n                                                 general document authoring support)\r\nhttp:\/\/vimeo.com\/31564708 (showing excellent export to \r\n                                                  LibreOffice\/MS Word format)\r\n\r\nVimOrganizer is a Vim filetype plugin that attempts to clone Emacs' Org-mode.  \r\nIt is currently (November 2011) in an alpha-stage, both in terms of (1) the \r\nbreadth and depth of Org-mode features it clones and (2) the stability of its\r\noperation.  It is nevertheless very usable.\r\n\r\nSome of the ADDITIONS AND IMPROVEMENTS since previous (December 2010) version:\r\n   -- Adjusts to any colorscheme\r\n   -- Org menu in gvim.\r\n   -- \"Dashboards\" to assist with Date entry, Columns, Tables,\r\n      Agenda searches, and exporting.\r\n   -- VimOrganizer help file to install in Vim.\r\n   -- Better compatibility with Org-mode files.  Open, edit, and save same \r\n      files in Org-mode and\/or VimOrganizer with (some) of the functionality and\r\n      configuration-specific options of Org-mode supported in VimOrganizer.\r\n   -- Support for Org-mode style links (as well as use of 'Conceal' in Vim73\r\n                                        to hide link brackets and \r\n                                        descriptions)\r\n   -- Easy to use Org-like column mode, including column headings,\r\n      inherited columns, support for Org column blocks, and ability to \r\n      specify a list of custom column specs to apply in any buffer.\r\n   -- Org-like narrowing of code blocks and subtrees\r\n   -- Support for Org-like specifications of TODOS, tags, dates,\r\n      including support for Org-compatible config lines in a file.\r\n   -- Support for Org-like CATEGORIES, both in specification and in \r\n      their inherited behavior.\r\n   -- Search specification in Agenda searches is now nearly identical\r\n      to specification of searches in Org-mode.\r\n   -- User can specify list of commonly used custom agenda searches.\r\n   -- Clockin, clockout, and (when a running Emacs server is available,\r\n      clocktable block creation and updates.\r\n   -- Org-like \"refiling\"\r\n   -- Easy creation and editing of tables, as well as (when a running Emacs \r\n      server is available) manipulation and evaluation of tables, including\r\n      all spreadsheet functionality in Org-mode.\r\n   -- \"Live\" block evaluation (when a running Emacs server is available) \r\n   -- Support for nearly all the export types and export options \r\n      available in Org-mode (when running Emacs server is available)\r\n   -- Call out to an Emacs server to do \"tangling\" (literate programming).\r\n   -- Many bug fixes and small improvements\r\n\r\nOrg-mode, and thus VimOrganizer, is a text-editor plugin\/application that can \r\nbe used for (1) keeping notes, (2) maintaining TODO lists, (3) planning \r\nprojects, and\/or (4) authoring and publishing documents, including support for \r\nliterate programming and \"reproducible research\".  Like Org-mode, VimOrganizer\r\ndoes this by implementing a flexible plain-text system with a lightly \r\nstructured document format.  Org-mode has been in constant development for \r\nseven or eight years, and continues to be developed.  Work on VimOrganizer is \r\nlikewise ongoing, but VimOrganizer is at present a smaller and less ambitious \r\nproject than Org-mode.\r\n\r\nFile formats and basic workflows for VimOrganizer and Org-mode are very \r\nsimilar (files auto-convert as part of loading process) and VimOrganizer \r\nactually calls out to an Emacs' Org-mode server to \r\nimplement important features, e.g., exporting to pdf format for printing.\r\n\r\nThus, to make full use of VimOrganizer you will want to have an Emacs' \r\nserver running alongside.  In most cases this requires little knowledge of \r\nEmacs other than how to start it up and add a few lines to the '.emacs' file, \r\nEmacs' counterpart to Vim's '.vimrc'.  (You can even edit the .emacs file in \r\nVim.)  VimOrganizer is focused on leveraging Org-mode by accessing it via\r\nan Emacs server, and re-implementing in Vim only what is necessary and makes \r\nsense. \r\n\r\nVimOrganizer also lets Vim users access Org-babel, a subproject of \r\nOrg-mode that allows execution of source-code blocks in org-format \r\ndocuments.  Uses for Org-babel range from writing technical research papers to \r\nsimply using a VimOrganizer document as a \"language-scratchpad\".  Over \r\ntwenty languages are supported, including C, R, Lisp, Python, Perl, Ruby, \r\nand others.  VimOrganizer calls out to a running Emacs server for Org-babel \r\nprocessing; functionality and speed are essentially the same as \r\nwhen editing with Org-mode in Emacs.\r\n\r\nVimOrganizer has a first draft of a Vim help file, but the best first step in\r\nlearning about VimOrganizer is to learn about Emacs' Org-mode.  VimOrganizer \r\nuses the same basic concepts but implements them within the context of Vim \r\n(and with a reduced feature set).  Org-mode's main documentation and \r\nsupport newsgroup are found here:\r\nOrg-mode Main Manual:  http:\/\/orgmode.org\/manual\/index.html\r\nOrg-mode Compact Guide: http:\/\/orgmode.org\/guide\/index.html\r\nOrg-mode support:  http:\/\/news.gmane.org\/gmane.emacs.orgmode \r\nOrg-babel information: http:\/\/orgmode.org\/worg\/org-contrib\/babel\/ \r\n\r\nVimOrganizer help can be found here:\r\nhttps:\/\/github.com\/hsitz\/VimOrganizer\/blob\/master\/doc\/vimorg.txt\r\n\r\n==========================\r\nINSTALLATION INSTRUCTIONS\r\n===========================\r\nhttps:\/\/github.com\/hsitz\/VimOrganizer\/blob\/master\/INSTALL.txt\r\n\r\n\r\nQUESTIONS, COMMENTS, SUGGESTIONS\r\n================================\r\nQuestions, comments, and suggestions regarding VimOrganizer are always \r\nappreciated.  The preferred place for those is in the VimOrganizer newsgroup \r\nhere:\r\nhttp:\/\/groups.google.com\/group\/vimorganizer\/topics\r\n\r\nVimOrganizer project files are maintained at github and the version \r\nthere may be more recent than the files at vim.org:\r\nhttps:\/\/github.com\/hsitz\/VimOrganizer\r\n\r\n----------------------------------------------------------------\r\nNOTE:  some code from other Vim plugins has been incorporated into the\r\nVimOrganizer script files.  Do NOT download these plugins to use them \r\nwith VimOrganizer; since VimOrganizer does not call out to them in any way:\r\n\r\n1.  Charles Campbell's great calendar utilities \r\n2.  Table editing routines from Maxim Kim's excellent vimwiki plugin. \r\n    These are really quite nice (seem to be inspired by Org-mode's\r\n    own table-editing stuff) and deserve to be offered as a separate\r\n    plugin of their own, not dependent on any larger project. (If\r\n    VimOrganizer is not quite the sort of plugin you're looking for then\r\n    vimwiki may be.) \r\n----------------------------------------------------------------\r\n\r\nVimOrganizer page at vim.org:\r\nhttp:\/\/www.vim.org\/scripts\/script.php?script_id=3342\r\n\r\n\r\n","install_details":"See:\r\nhttps:\/\/github.com\/hsitz\/VimOrganizer\/blob\/master\/INSTALL.txt","5":"See:\r\nhttps:\/\/github.com\/hsitz\/VimOrganizer\/blob\/master\/INSTALL.txt","first_name":"Herbert","6":"Herbert","last_name":"Sitz","7":"Sitz","releases":[{"0":"3342","vim_version":"7.0","1":"7.0","script_version":"0.313","2":"0.313","version_comment":"Fixed sample vimrc and vimorg.txt to reference g:agenda_files instead of non-existent g:org_agenda_files","3":"Fixed sample vimrc and vimorg.txt to reference g:agenda_files instead of non-existent g:org_agenda_files","package":"VimOrganizer_v0313.zip","4":"VimOrganizer_v0313.zip","src_id":"16878","5":"16878","creation_date":"1321428017","6":"1321428017"},{"0":"3342","vim_version":"7.0","1":"7.0","script_version":"0.312","2":"0.312","version_comment":"Fix for some dates with repeaters not getting found in agenda searches","3":"Fix for some dates with repeaters not getting found in agenda searches","package":"VimOrganizer_v0312.zip","4":"VimOrganizer_v0312.zip","src_id":"16846","5":"16846","creation_date":"1320941308","6":"1320941308"},{"0":"3342","vim_version":"7.0","1":"7.0","script_version":"0.311","2":"0.311","version_comment":"0.31-Fixed bug with opening agenda window on terminals when no g:agenda_files defined; added \"todo dashboard\" accessible by ,t  ; added support for auto log entries and date reset when changing date-repeater todos to done state, 0.311 -- fixed bug that could cause endless loop when cycling","3":"0.31-Fixed bug with opening agenda window on terminals when no g:agenda_files defined; added \"todo dashboard\" accessible by ,t  ; added support for auto log entries and date reset when changing date-repeater todos to done state, 0.311 -- fixed bug that could cause endless loop when cycling","package":"VimOrganizer_v031.zip","4":"VimOrganizer_v031.zip","src_id":"16844","5":"16844","creation_date":"1320911813","6":"1320911813"},{"0":"3342","vim_version":"7.0","1":"7.0","script_version":"0.304","2":"0.304","version_comment":"Additions to install.txt file re: emacs setup, set g:org_command_for_emacsclient by default on Linux and OSX systems. ","3":"Additions to install.txt file re: emacs setup, set g:org_command_for_emacsclient by default on Linux and OSX systems. ","package":"VimOrganizer_0304.zip","4":"VimOrganizer_0304.zip","src_id":"16810","5":"16810","creation_date":"1320511537","6":"1320511537"},{"0":"3342","vim_version":"7.0","1":"7.0","script_version":"0.302","2":"0.302","version_comment":"Tweak to avoid error message when starting in terminal that has no Normal background color set","3":"Tweak to avoid error message when starting in terminal that has no Normal background color set","package":"VimOrganizer_v0302.zip","4":"VimOrganizer_v0302.zip","src_id":"16791","5":"16791","creation_date":"1320289667","6":"1320289667"},{"0":"3342","vim_version":"7.0","1":"7.0","script_version":"0.301","2":"0.301","version_comment":"fix for error message when starting up with no g:org_todo_custom_highlights defined;\r\nfix to hide FoldColumn in terminal versions of Vim","3":"fix for error message when starting up with no g:org_todo_custom_highlights defined;\r\nfix to hide FoldColumn in terminal versions of Vim","package":"VimOrganizer_v0301.zip","4":"VimOrganizer_v0301.zip","src_id":"16790","5":"16790","creation_date":"1320285706","6":"1320285706"},{"0":"3342","vim_version":"7.0","1":"7.0","script_version":"0.30","2":"0.30","version_comment":"Many changes, additions, improvements.  See intro.txt and the included vim-format help file.","3":"Many changes, additions, improvements.  See intro.txt and the included vim-format help file.","package":"VimOrganizer_v030.zip","4":"VimOrganizer_v030.zip","src_id":"16789","5":"16789","creation_date":"1320279374","6":"1320279374"}]},"3341":{"script_id":"3341","0":"3341","script_name":"auto ","1":"auto ","script_type":"utility","2":"utility","summary":"Coding automation  for c\/c++\/ruby\/python\/shell\/perl\/...","3":"Coding automation  for c\/c++\/ruby\/python\/shell\/perl\/...","description":"Both c, cpp, or python,shell,perl code, F2 key or \"mm\" to compile and debug\r\n1.Normal mode\r\n    ;;      Exit without saving\r\n    ,,      Save and exit\r\n2.Insert mode\r\n    ;;      return Normal mode\r\n    ,,      return Normal mode\r\n    mm      return Normal mode\r\n    <Alt-j>  Down\r\n    <Alt-k> Up\r\n    <Alt-h> Left\r\n    <Alt-l>  Right\r\n3.When writing c, cpp ,... code, the code is automatically formatted\r\n    For example:   If you input a==3;\r\n    auto.vim                             a  ==  3;\r\n\r\nNOTE:auto.vim  only for GNU\/Linux;VERSION 1.5 has some errors,Sorry I neglected to mention that before. ","4":"Both c, cpp, or python,shell,perl code, F2 key or \"mm\" to compile and debug\r\n1.Normal mode\r\n    ;;      Exit without saving\r\n    ,,      Save and exit\r\n2.Insert mode\r\n    ;;      return Normal mode\r\n    ,,      return Normal mode\r\n    mm      return Normal mode\r\n    <Alt-j>  Down\r\n    <Alt-k> Up\r\n    <Alt-h> Left\r\n    <Alt-l>  Right\r\n3.When writing c, cpp ,... code, the code is automatically formatted\r\n    For example:   If you input a==3;\r\n    auto.vim                             a  ==  3;\r\n\r\nNOTE:auto.vim  only for GNU\/Linux;VERSION 1.5 has some errors,Sorry I neglected to mention that before. ","install_details":"Simply drop this file into your $HOME\/.vim\/plugin directory.\r\n\r\n ","5":"Simply drop this file into your $HOME\/.vim\/plugin directory.\r\n\r\n ","first_name":"\u5b87\u6587","6":"宇文","last_name":"\u9ad8\u4e0b","7":"高下","releases":[{"0":"3341","vim_version":"7.2","1":"7.2","script_version":"2.1","2":"2.1","version_comment":"检测Ruby制定为两个字符的缩排\r\nRuby indented two characters","3":"检测Ruby制定为两个字符的缩排\r\nRuby indented two characters","package":"auto.vim","4":"auto.vim","src_id":"16933","5":"16933","creation_date":"1321921374","6":"1321921374"},{"0":"3341","vim_version":"7.2","1":"7.2","script_version":"2.0","2":"2.0","version_comment":"更新了shell的调用\r\nUpdated shell call","3":"更新了shell的调用\r\nUpdated shell call","package":"auto.vim","4":"auto.vim","src_id":"15434","5":"15434","creation_date":"1302570069","6":"1302570069"},{"0":"3341","vim_version":"7.2","1":"7.2","script_version":"1.9","2":"1.9","version_comment":"修复了在桌面终端下调试perl的bug\r\nFixed a bug when debugging perl on desktop terminal","3":"修复了在桌面终端下调试perl的bug\r\nFixed a bug when debugging perl on desktop terminal","package":"auto.vim","4":"auto.vim","src_id":"15323","5":"15323","creation_date":"1301400119","6":"1301400119"},{"0":"3341","vim_version":"7.2","1":"7.2","script_version":"1.8","2":"1.8","version_comment":"添加了HTML支持，方面调试javascript\r\nAdded support for HTML,Easy to  debug javascript","3":"添加了HTML支持，方面调试javascript\r\nAdded support for HTML,Easy to  debug javascript","package":"auto.vim","4":"auto.vim","src_id":"15220","5":"15220","creation_date":"1300146003","6":"1300146003"},{"0":"3341","vim_version":"7.0","1":"7.0","script_version":"1.7","2":"1.7","version_comment":"简洁,适当的取舍是unix的思想之一\r\nSimple,appropriate trade-off is a idea of unix\r\n","3":"简洁,适当的取舍是unix的思想之一\r\nSimple,appropriate trade-off is a idea of unix\r\n","package":"auto.vim","4":"auto.vim","src_id":"14894","5":"14894","creation_date":"1296206134","6":"1296206134"},{"0":"3341","vim_version":"7.0","1":"7.0","script_version":"1.6","2":"1.6","version_comment":"修复了在文本终端的执行时的bug,加入了ruby支持；脚本很简洁，您可以根据您的习惯，重新映射\r\nFixed a bug when on the text terminal ,Added ruby support；The script is very simple, you can based on your habits, re-mapping","3":"修复了在文本终端的执行时的bug,加入了ruby支持；脚本很简洁，您可以根据您的习惯，重新映射\r\nFixed a bug when on the text terminal ,Added ruby support；The script is very simple, you can based on your habits, re-mapping","package":"auto.vim","4":"auto.vim","src_id":"14780","5":"14780","creation_date":"1295361814","6":"1295361814"}]},"3340":{"script_id":"3340","0":"3340","script_name":"zenesque.vim","1":"zenesque.vim","script_type":"color scheme","2":"color scheme","summary":"Minimalistic scheme with light \/ dark background options","3":"Minimalistic scheme with light \/ dark background options","description":"Almost colorless(shades of grey), light minimalistic color scheme.  Designed for reading for long periods. Inspired by Mini.\r\n\r\nNow includes options for color highlighting and dark backgrounds.\r\n\r\nScreenshots:\r\n\r\nLIGHT GROUP:\r\nno colors (default):\r\nhttp:\/\/www.flickr.com\/photos\/28853165@N05\/5246095508\/\r\n\r\nwith colors:\r\nhttp:\/\/www.flickr.com\/photos\/28853165@N05\/5246095888\/\r\n\r\nDARK GROUP:\r\n\r\nno colors:\r\nhttp:\/\/www.flickr.com\/photos\/28853165@N05\/5246096772\/\r\n\r\nwith colors:\r\nhttp:\/\/www.flickr.com\/photos\/28853165@N05\/5246089194\/\r\nNote: GUI only version (for now)","4":"Almost colorless(shades of grey), light minimalistic color scheme.  Designed for reading for long periods. Inspired by Mini.\r\n\r\nNow includes options for color highlighting and dark backgrounds.\r\n\r\nScreenshots:\r\n\r\nLIGHT GROUP:\r\nno colors (default):\r\nhttp:\/\/www.flickr.com\/photos\/28853165@N05\/5246095508\/\r\n\r\nwith colors:\r\nhttp:\/\/www.flickr.com\/photos\/28853165@N05\/5246095888\/\r\n\r\nDARK GROUP:\r\n\r\nno colors:\r\nhttp:\/\/www.flickr.com\/photos\/28853165@N05\/5246096772\/\r\n\r\nwith colors:\r\nhttp:\/\/www.flickr.com\/photos\/28853165@N05\/5246089194\/\r\nNote: GUI only version (for now)","install_details":"drop in your vim\/colors directory\r\n\r\nFor other highlighting options, add the following in your vimrc (ensure 'colorscheme zenesque' is called after the below statement)\r\n\r\nlight with colors:\r\nlet g:zenesque_colors=1\r\n\r\ndark without colors:\r\nlet g:zenesque_colors=2\r\n\r\ndark with colors:\r\nlet g:zenesque_colors=3\r\n\r\nif you want to revert back to the default then set: g:zenesque_colors=0\r\n","5":"drop in your vim\/colors directory\r\n\r\nFor other highlighting options, add the following in your vimrc (ensure 'colorscheme zenesque' is called after the below statement)\r\n\r\nlight with colors:\r\nlet g:zenesque_colors=1\r\n\r\ndark without colors:\r\nlet g:zenesque_colors=2\r\n\r\ndark with colors:\r\nlet g:zenesque_colors=3\r\n\r\nif you want to revert back to the default then set: g:zenesque_colors=0\r\n","first_name":"Paul","6":"Paul","last_name":"L","7":"L","releases":[{"0":"3340","vim_version":"7.0","1":"7.0","script_version":"1.8","2":"1.8","version_comment":"Folded and FoldColumn hexcode corrections, thanks to M. Soyka.","3":"Folded and FoldColumn hexcode corrections, thanks to M. Soyka.","package":"zenesque.vim","4":"zenesque.vim","src_id":"14642","5":"14642","creation_date":"1293598364","6":"1293598364"},{"0":"3340","vim_version":"7.0","1":"7.0","script_version":"1.7","2":"1.7","version_comment":"added CursorColumn highlighting, thanks to Vincent Berthoux.","3":"added CursorColumn highlighting, thanks to Vincent Berthoux.","package":"zenesque.vim","4":"zenesque.vim","src_id":"14627","5":"14627","creation_date":"1293420892","6":"1293420892"},{"0":"3340","vim_version":"7.0","1":"7.0","script_version":"1.6","2":"1.6","version_comment":"now supporting dark backgrounds","3":"now supporting dark backgrounds","package":"zenesque.vim","4":"zenesque.vim","src_id":"14463","5":"14463","creation_date":"1291879778","6":"1291879778"},{"0":"3340","vim_version":"7.0","1":"7.0","script_version":"1.5","2":"1.5","version_comment":"improved highlighting for grep \/ copen - thanks to Ismo P","3":"improved highlighting for grep \/ copen - thanks to Ismo P","package":"zenesque.vim","4":"zenesque.vim","src_id":"14448","5":"14448","creation_date":"1291603110","6":"1291603110"},{"0":"3340","vim_version":"7.0","1":"7.0","script_version":"1.4","2":"1.4","version_comment":"some minor readability\/color tweaks","3":"some minor readability\/color tweaks","package":"zenesque.vim","4":"zenesque.vim","src_id":"14433","5":"14433","creation_date":"1291462868","6":"1291462868"},{"0":"3340","vim_version":"7.0","1":"7.0","script_version":"1.3","2":"1.3","version_comment":"option for color highlighting","3":"option for color highlighting","package":"zenesque.vim","4":"zenesque.vim","src_id":"14411","5":"14411","creation_date":"1291215060","6":"1291215060"},{"0":"3340","vim_version":"7.0","1":"7.0","script_version":"1.2","2":"1.2","version_comment":"better language support and general tweaks","3":"better language support and general tweaks","package":"zenesque.vim","4":"zenesque.vim","src_id":"14385","5":"14385","creation_date":"1290825141","6":"1290825141"},{"0":"3340","vim_version":"7.0","1":"7.0","script_version":"1.1","2":"1.1","version_comment":"more emphasis on function names & clearer Pmenu","3":"more emphasis on function names & clearer Pmenu","package":"zenesque.vim","4":"zenesque.vim","src_id":"14372","5":"14372","creation_date":"1290654481","6":"1290654481"},{"0":"3340","vim_version":"7.0","1":"7.0","script_version":"1","2":"1","version_comment":"Initial upload","3":"Initial upload","package":"zenesque.vim","4":"zenesque.vim","src_id":"14363","5":"14363","creation_date":"1290582092","6":"1290582092"}]},"3339":{"script_id":"3339","0":"3339","script_name":"rdist-syntax","1":"rdist-syntax","script_type":"syntax","2":"syntax","summary":"Syntax coloring for Rdist config files","3":"Syntax coloring for Rdist config files","description":"Provides syntax coloring for Rdist's \"distfile\" configuration files.\r\n\r\nhttps:\/\/github.com\/tangledhelix\/vim-rdist","4":"Provides syntax coloring for Rdist's \"distfile\" configuration files.\r\n\r\nhttps:\/\/github.com\/tangledhelix\/vim-rdist","install_details":"mkdir -p ~\/.vim\/syntax ~\/.vim\/ftplugin ~\/.vim\/ftdetect\r\ncp syntax\/rdist.vim ~\/.vim\/syntax\r\ncp ftdetect\/rdist.vim ~\/.vim\/ftdetect\r\ncp ftplugin\/rdist.vim ~\/.vim\/ftplugin\r\n\r\n","5":"mkdir -p ~\/.vim\/syntax ~\/.vim\/ftplugin ~\/.vim\/ftdetect\r\ncp syntax\/rdist.vim ~\/.vim\/syntax\r\ncp ftdetect\/rdist.vim ~\/.vim\/ftdetect\r\ncp ftplugin\/rdist.vim ~\/.vim\/ftplugin\r\n\r\n","first_name":"Dan","6":"Dan","last_name":"Lowe","7":"Lowe","releases":[{"0":"3339","vim_version":"5.7","1":"5.7","script_version":"1.1","2":"1.1","version_comment":"added ftdetect, ftplugin modules","3":"added ftdetect, ftplugin modules","package":"vim-rdist.zip","4":"vim-rdist.zip","src_id":"14393","5":"14393","creation_date":"1291045328","6":"1291045328"},{"0":"3339","vim_version":"5.7","1":"5.7","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"rdist.vim","4":"rdist.vim","src_id":"14355","5":"14355","creation_date":"1290489541","6":"1290489541"}]},"3338":{"script_id":"3338","0":"3338","script_name":"newspaper.vim","1":"newspaper.vim","script_type":"color scheme","2":"color scheme","summary":"A light color scheme for coders whom also read newspapers","3":"A light color scheme for coders whom also read newspapers","description":"a 1st attempt for a light\/subtle, easy to read scheme, especially for extended periods of coding...\r\n\r\nScreenshot:\r\nhttp:\/\/www.flickr.com\/photos\/28853165@N05\/5225392098\/","4":"a 1st attempt for a light\/subtle, easy to read scheme, especially for extended periods of coding...\r\n\r\nScreenshot:\r\nhttp:\/\/www.flickr.com\/photos\/28853165@N05\/5225392098\/","install_details":"just drop newspaper.vim in your vim\/colors directory","5":"just drop newspaper.vim in your vim\/colors directory","first_name":"Paul","6":"Paul","last_name":"L","7":"L","releases":[{"0":"3338","vim_version":"7.0","1":"7.0","script_version":"2.0","2":"2.0","version_comment":"reworked the colors as hex codes","3":"reworked the colors as hex codes","package":"newspaper.vim","4":"newspaper.vim","src_id":"14495","5":"14495","creation_date":"1292227025","6":"1292227025"}]},"3337":{"script_id":"3337","0":"3337","script_name":"tracwiki","1":"tracwiki","script_type":"syntax","2":"syntax","summary":"Vim syntax file for Trac wiki syntax","3":"Vim syntax file for Trac wiki syntax","description":"Vim syntax file for Trac wiki syntax. Most of Trac 0.11 wiki syntax is supported.\r\n\r\n(Modified from the more general purpose wiki.vim, by Andreas Kneib, http:\/\/www.vim.org\/scripts\/script.php?script_id=725, ftdetect script contributed by Daniel Hahler.)\r\n","4":"Vim syntax file for Trac wiki syntax. Most of Trac 0.11 wiki syntax is supported.\r\n\r\n(Modified from the more general purpose wiki.vim, by Andreas Kneib, http:\/\/www.vim.org\/scripts\/script.php?script_id=725, ftdetect script contributed by Daniel Hahler.)\r\n","install_details":"== Standalone Script, tracwiki.vim ==\r\n\r\nPut the file in your syntax directory, e.g. ~\/.vim\/syntax, $HOME\/vimfiles\/syntax (see :help syntax).\r\n\r\nEnable file type detection. One method is to add the following to your filetype.vim file, which is usually located in ~\/.vim or $HOME\/vimfiles (create it if not present, see :help filetype):\r\n\r\n      augroup tracwiki\r\n          au! BufRead,BufNewFile *.tracwiki   setfiletype tracwiki\r\n      augroup END\r\n\r\n== With ftdetect, tracwiki.zip ==\r\n\r\nDownload tracwiki.zip and unzip it into your `runtimepath` directory (e.g. $HOME\/.vim, $VIM\/vimfiles).","5":"== Standalone Script, tracwiki.vim ==\r\n\r\nPut the file in your syntax directory, e.g. ~\/.vim\/syntax, $HOME\/vimfiles\/syntax (see :help syntax).\r\n\r\nEnable file type detection. One method is to add the following to your filetype.vim file, which is usually located in ~\/.vim or $HOME\/vimfiles (create it if not present, see :help filetype):\r\n\r\n      augroup tracwiki\r\n          au! BufRead,BufNewFile *.tracwiki   setfiletype tracwiki\r\n      augroup END\r\n\r\n== With ftdetect, tracwiki.zip ==\r\n\r\nDownload tracwiki.zip and unzip it into your `runtimepath` directory (e.g. $HOME\/.vim, $VIM\/vimfiles).","first_name":"Caleb","6":"Caleb","last_name":"Constantine","7":"Constantine","releases":[{"0":"3337","vim_version":"7.0","1":"7.0","script_version":"0.5","2":"0.5","version_comment":"Same as tracwiki.vim 0.5 (below) but packaged with a ftdetect script to auto-set filetype.","3":"Same as tracwiki.vim 0.5 (below) but packaged with a ftdetect script to auto-set filetype.","package":"tracwiki.zip","4":"tracwiki.zip","src_id":"16162","5":"16162","creation_date":"1311854145","6":"1311854145"},{"0":"3337","vim_version":"7.0","1":"7.0","script_version":"0.5","2":"0.5","version_comment":"Added '-' as a valid char for a list item.","3":"Added '-' as a valid char for a list item.","package":"tracwiki.vim","4":"tracwiki.vim","src_id":"16160","5":"16160","creation_date":"1311853660","6":"1311853660"},{"0":"3337","vim_version":"7.0","1":"7.0","script_version":"0.4","2":"0.4","version_comment":"Initial upload","3":"Initial upload","package":"tracwiki.vim","4":"tracwiki.vim","src_id":"14352","5":"14352","creation_date":"1290478024","6":"1290478024"}]},"3336":{"script_id":"3336","0":"3336","script_name":"Smart Home Key","1":"Smart Home Key","script_type":"utility","2":"utility","summary":"Home key toggles between ^ and 0","3":"Home key toggles between ^ and 0","description":"This plugin will give you a command called :SmartHomeKey. You can bind this to any key, but I like to use <Home>. When you are in your code, and you call :SmartHomeKey, if the cursor is anywhere but ^ (the first non-blank character on the line), it will go to ^. If you are on ^ and you call :SmartHomeKey again, the cursor will be placed at 0 (first character on line, blank or non-blank). If you hold <Home>, it will just toggle between ^ and 0. \r\n\r\nThis emulates the behavior of the home key in Eclipse, which is what I used before switching to Vim. \r\n\r\nThis script is really simple, but I'm new to Vim scripting so let me know if you have problems (or if I did something stupid).","4":"This plugin will give you a command called :SmartHomeKey. You can bind this to any key, but I like to use <Home>. When you are in your code, and you call :SmartHomeKey, if the cursor is anywhere but ^ (the first non-blank character on the line), it will go to ^. If you are on ^ and you call :SmartHomeKey again, the cursor will be placed at 0 (first character on line, blank or non-blank). If you hold <Home>, it will just toggle between ^ and 0. \r\n\r\nThis emulates the behavior of the home key in Eclipse, which is what I used before switching to Vim. \r\n\r\nThis script is really simple, but I'm new to Vim scripting so let me know if you have problems (or if I did something stupid).","install_details":"Create ~\/.vim\/plugin\/ (~\\vimfiles\\plugin\\ on Win) if it doesn't exist. Drop in smarthomekey.vim. This will give you the command :SmartHomeKey which you can bind in your .vimrc:\r\n\r\nmap <silent> <Home> :SmartHomeKey <CR>\r\nimap <silent> <Home> <C-O>:SmartHomeKey<CR>\r\n","5":"Create ~\/.vim\/plugin\/ (~\\vimfiles\\plugin\\ on Win) if it doesn't exist. Drop in smarthomekey.vim. This will give you the command :SmartHomeKey which you can bind in your .vimrc:\r\n\r\nmap <silent> <Home> :SmartHomeKey <CR>\r\nimap <silent> <Home> <C-O>:SmartHomeKey<CR>\r\n","first_name":"andrew","6":"andrew","last_name":"lyon","7":"lyon","releases":[{"0":"3336","vim_version":"7.0","1":"7.0","script_version":"0.2","2":"0.2","version_comment":"Fixed bug where the line number was being set incorrectly sometimes.","3":"Fixed bug where the line number was being set incorrectly sometimes.","package":"smarthomekey.vim","4":"smarthomekey.vim","src_id":"14351","5":"14351","creation_date":"1290464977","6":"1290464977"},{"0":"3336","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"smarthomekey.vim","4":"smarthomekey.vim","src_id":"14344","5":"14344","creation_date":"1290394705","6":"1290394705"}]},"3335":{"script_id":"3335","0":"3335","script_name":"VIP","1":"VIP","script_type":"utility","2":"utility","summary":"Special copy and paste for VHDL entities, components and instances of components","3":"Special copy and paste for VHDL entities, components and instances of components","description":"VIP (VHDL Interface Plug-in) is a script for VIM text editor which provides some facilities to copy paste entities, components and instances of components.\r\n\r\nFor example you can copy the component :\r\n\r\ncomponent mux is   -- place the cursor on this line and enter the command :Viy (Vhdl Interface Yank)\r\n   port (  \r\n     INPUT  : in  std_logic_vector (15 downto 0);  \r\n     SEL    : in  std_logic;   \r\n     OUTPUT : out std_logic    \r\n   );  \r\nend component mux;\r\n\r\nand paste it as an instance :\r\n\r\nmux_0 : mux   -- place the cursor here and enter the command :Vii (Vhdl Interface Instance)\r\n   port map (  \r\n      INPUT   => s_INPUT,  \r\n      SEL     => s_SEL,  \r\n      OUTPUT  => s_OUTPUT  \r\n  );\r\n\r\nVIP can :\r\n\r\n  - copy an entity and paste it as\r\n          - an entity\r\n          - a component\r\n          - an instance\r\n\r\n  - copy a component and paste it as\r\n          - an entity\r\n          - a component\r\n          - an instance\r\n\r\n  - copy a instance and paste it as\r\n          - an instance (with auto-incrementation of the suffix number)\r\n\r\nVIP tries to respect your indentation as much as possible (spaces, tabs, spaces + tabs).\r\nIt can work with many different styles of writing entities, components and instances but not all of them. See documentation.\r\n\r\nSource : https:\/\/github.com\/JPR75\/vip\r\n","4":"VIP (VHDL Interface Plug-in) is a script for VIM text editor which provides some facilities to copy paste entities, components and instances of components.\r\n\r\nFor example you can copy the component :\r\n\r\ncomponent mux is   -- place the cursor on this line and enter the command :Viy (Vhdl Interface Yank)\r\n   port (  \r\n     INPUT  : in  std_logic_vector (15 downto 0);  \r\n     SEL    : in  std_logic;   \r\n     OUTPUT : out std_logic    \r\n   );  \r\nend component mux;\r\n\r\nand paste it as an instance :\r\n\r\nmux_0 : mux   -- place the cursor here and enter the command :Vii (Vhdl Interface Instance)\r\n   port map (  \r\n      INPUT   => s_INPUT,  \r\n      SEL     => s_SEL,  \r\n      OUTPUT  => s_OUTPUT  \r\n  );\r\n\r\nVIP can :\r\n\r\n  - copy an entity and paste it as\r\n          - an entity\r\n          - a component\r\n          - an instance\r\n\r\n  - copy a component and paste it as\r\n          - an entity\r\n          - a component\r\n          - an instance\r\n\r\n  - copy a instance and paste it as\r\n          - an instance (with auto-incrementation of the suffix number)\r\n\r\nVIP tries to respect your indentation as much as possible (spaces, tabs, spaces + tabs).\r\nIt can work with many different styles of writing entities, components and instances but not all of them. See documentation.\r\n\r\nSource : https:\/\/github.com\/JPR75\/vip\r\n","install_details":"Put the plugin\/vip.vim file into your ~\/.vim\/plugin (or $HOME\\\\vimfiles\\\\plugin) directory.\r\nPut the doc\/vip.txt into your ~\/.vim\/doc (or $HOME\\\\vimfiles\\\\doc) directory.\r\n\r\nRun \":helptags ~\/.vim\/doc\" (\":helptags $HOME\/vimfiles\/doc\")\r\n","5":"Put the plugin\/vip.vim file into your ~\/.vim\/plugin (or $HOME\\\\vimfiles\\\\plugin) directory.\r\nPut the doc\/vip.txt into your ~\/.vim\/doc (or $HOME\\\\vimfiles\\\\doc) directory.\r\n\r\nRun \":helptags ~\/.vim\/doc\" (\":helptags $HOME\/vimfiles\/doc\")\r\n","first_name":"JP","6":"JP","last_name":"Ricaud","7":"Ricaud","releases":[{"0":"3335","vim_version":"7.0","1":"7.0","script_version":"1.4.0","2":"1.4.0","version_comment":"Updated with Franz Hechfellner improvements:\r\n\r\n    \"since I use your plugin often, I improved vip.vim in terms of multible\r\n    braces and empty lines and made it more robust for different entitiy\r\n    formats. It is still not perfect but better.\"\r\n","3":"Updated with Franz Hechfellner improvements:\r\n\r\n    \"since I use your plugin often, I improved vip.vim in terms of multible\r\n    braces and empty lines and made it more robust for different entitiy\r\n    formats. It is still not perfect but better.\"\r\n","package":"vip.zip","4":"vip.zip","src_id":"23982","5":"23982","creation_date":"1454368036","6":"1454368036"},{"0":"3335","vim_version":"7.0","1":"7.0","script_version":"1.2.0","2":"1.2.0","version_comment":"- Support for a wider style of writing blocks, like :\r\n\r\ncomponent foo\r\n    port (\r\n        a,b: in bit;\r\n         c: out bit);\r\nend component;\r\n\r\n- Bug fix\r\n- Minor optimization.","3":"- Support for a wider style of writing blocks, like :\r\n\r\ncomponent foo\r\n    port (\r\n        a,b: in bit;\r\n         c: out bit);\r\nend component;\r\n\r\n- Bug fix\r\n- Minor optimization.","package":"vip.zip","4":"vip.zip","src_id":"14484","5":"14484","creation_date":"1292165929","6":"1292165929"},{"0":"3335","vim_version":"7.0","1":"7.0","script_version":"1.0.1","2":"1.0.1","version_comment":"Fixed missing argument when pasting an entity as an instance","3":"Fixed missing argument when pasting an entity as an instance","package":"vip.zip","4":"vip.zip","src_id":"14340","5":"14340","creation_date":"1290357427","6":"1290357427"},{"0":"3335","vim_version":"7.0","1":"7.0","script_version":"1.0.0","2":"1.0.0","version_comment":"Initial upload","3":"Initial upload","package":"vip.zip","4":"vip.zip","src_id":"14309","5":"14309","creation_date":"1290207337","6":"1290207337"}]},"3334":{"script_id":"3334","0":"3334","script_name":"void","1":"void","script_type":"color scheme","2":"color scheme","summary":"A dark, clean color scheme","3":"A dark, clean color scheme","description":"This color scheme is loosely based off of desert.vim (vimscript #105) mixed with some of slate.vim. I took the darker background from slate, replaced a lot of the desert colors with a earthy\/brown color scheme, changed the window borders to be black, and folders are a light orange instead of the default blue. \r\n\r\nOverall it's a coherent, earthy color scheme with minimal visual distraction. I have used it for coding in C, PHP, C#, HTML, and Lisp so far.\r\n\r\nNote that I've only really used it with gvim, it may look like crap in 256 colors. I'm new to vim in general, so any suggestions on how to port this to 256 would be greatly appreciated.\r\n\r\nThe name \"void\" has no special meaning, it was the first thing that came to mind when I named it.\r\n\r\nGit repo: https:\/\/github.com\/orthecreedence\/void.vim","4":"This color scheme is loosely based off of desert.vim (vimscript #105) mixed with some of slate.vim. I took the darker background from slate, replaced a lot of the desert colors with a earthy\/brown color scheme, changed the window borders to be black, and folders are a light orange instead of the default blue. \r\n\r\nOverall it's a coherent, earthy color scheme with minimal visual distraction. I have used it for coding in C, PHP, C#, HTML, and Lisp so far.\r\n\r\nNote that I've only really used it with gvim, it may look like crap in 256 colors. I'm new to vim in general, so any suggestions on how to port this to 256 would be greatly appreciated.\r\n\r\nThe name \"void\" has no special meaning, it was the first thing that came to mind when I named it.\r\n\r\nGit repo: https:\/\/github.com\/orthecreedence\/void.vim","install_details":"Create ~\/.vim\/colors\/ (~\\vimfiles\\colors\\ on Win) and drop void.vim in.","5":"Create ~\/.vim\/colors\/ (~\\vimfiles\\colors\\ on Win) and drop void.vim in.","first_name":"andrew","6":"andrew","last_name":"lyon","7":"lyon","releases":[{"0":"3334","vim_version":"7.0","1":"7.0","script_version":"2.2","2":"2.2","version_comment":"Adding Python-specific operator highlighting (thanks to Max Wei\u00c3\u009f for the update).","3":"Adding Python-specific operator highlighting (thanks to Max Wei\u00c3\u009f for the update).","package":"void.vim","4":"void.vim","src_id":"21505","5":"21505","creation_date":"1392742655","6":"1392742655"},{"0":"3334","vim_version":"7.0","1":"7.0","script_version":"2.1","2":"2.1","version_comment":"Updated Pmenu and PmenuSel for use with FuzzyFinder (or other menu-based plugins). It was hideous before and I can't believe I let it be for this long. Enjoy.","3":"Updated Pmenu and PmenuSel for use with FuzzyFinder (or other menu-based plugins). It was hideous before and I can't believe I let it be for this long. Enjoy.","package":"void.vim","4":"void.vim","src_id":"17649","5":"17649","creation_date":"1332531223","6":"1332531223"},{"0":"3334","vim_version":"7.0","1":"7.0","script_version":"2.0","2":"2.0","version_comment":"The new release of this fixes some stuff I would label issues: Identifiers displayed as normal text, Statements\/Types not fitting with the overall theme, etc. This new release is a bit of a larger update as far as the color palate goes, so be sure to hang onto your original version if the new one is too much of a change. Personally, I think it's a lot nicer and easier on the eyes.","3":"The new release of this fixes some stuff I would label issues: Identifiers displayed as normal text, Statements\/Types not fitting with the overall theme, etc. This new release is a bit of a larger update as far as the color palate goes, so be sure to hang onto your original version if the new one is too much of a change. Personally, I think it's a lot nicer and easier on the eyes.","package":"void.vim","4":"void.vim","src_id":"17632","5":"17632","creation_date":"1332378100","6":"1332378100"},{"0":"3334","vim_version":"7.0","1":"7.0","script_version":"1.3","2":"1.3","version_comment":"Modified TODO\/NOTE code comment highlighting to be a bit easier to read without sacrificing the \"HEY LOOK AT ME!!\" effect.","3":"Modified TODO\/NOTE code comment highlighting to be a bit easier to read without sacrificing the \"HEY LOOK AT ME!!\" effect.","package":"void.vim","4":"void.vim","src_id":"14350","5":"14350","creation_date":"1290464534","6":"1290464534"},{"0":"3334","vim_version":"7.0","1":"7.0","script_version":"1.2","2":"1.2","version_comment":"Ran dos2unix filter to fix errors some people were getting when sourcing.","3":"Ran dos2unix filter to fix errors some people were getting when sourcing.","package":"void.vim","4":"void.vim","src_id":"14342","5":"14342","creation_date":"1290371965","6":"1290371965"},{"0":"3334","vim_version":"6.0","1":"6.0","script_version":"1.1","2":"1.1","version_comment":"Made the \"khaki\" Statement highlight \"darkkhaki\" which is a bit easier to read.","3":"Made the \"khaki\" Statement highlight \"darkkhaki\" which is a bit easier to read.","package":"void.vim","4":"void.vim","src_id":"14332","5":"14332","creation_date":"1290285053","6":"1290285053"},{"0":"3334","vim_version":"6.0","1":"6.0","script_version":"1","2":"1","version_comment":"Initial upload","3":"Initial upload","package":"void.vim","4":"void.vim","src_id":"14308","5":"14308","creation_date":"1290194439","6":"1290194439"}]},"3333":{"script_id":"3333","0":"3333","script_name":"mheg","1":"mheg","script_type":"syntax","2":"syntax","summary":"Syntax script for MHEG-5 DTB (and UK Profile)","3":"Syntax script for MHEG-5 DTB (and UK Profile)","description":"Simple highlighter for MHEG - complete enough for general use. \r\nFeel free to add missing keywords \/ features!\r\n\r\nFor feedback \/ questions, please use: http:\/\/paulbanks.org\/projects\/mhegvim\/\r\n\r\nPaul\r\n","4":"Simple highlighter for MHEG - complete enough for general use. \r\nFeel free to add missing keywords \/ features!\r\n\r\nFor feedback \/ questions, please use: http:\/\/paulbanks.org\/projects\/mhegvim\/\r\n\r\nPaul\r\n","install_details":"See http:\/\/paulbanks.org\/projects\/mhegvim\/","5":"See http:\/\/paulbanks.org\/projects\/mhegvim\/","first_name":"Paul","6":"Paul","last_name":"Banks","7":"Banks","releases":[{"0":"3333","vim_version":"7.0","1":"7.0","script_version":"1.02","2":"1.02","version_comment":"Added string handling for \" as well as '","3":"Added string handling for \" as well as '","package":"mheg.vim","4":"mheg.vim","src_id":"14327","5":"14327","creation_date":"1290257974","6":"1290257974"}]},"3332":{"script_id":"3332","0":"3332","script_name":"verilog_systemverilog_fix","1":"verilog_systemverilog_fix","script_type":"ftplugin","2":"ftplugin","summary":"Fixed Verilog\/SystemVerilog file type plugin ","3":"Fixed Verilog\/SystemVerilog file type plugin ","description":"This is the \"bug fix\" version of \"verilog_systemverilog.vim\" vimscript #1586 created by Amit Sethi.\r\n\r\nWith this fixed version, the key \"%\" (matchit.vim) works for Verilog\/SystemVerilog files, which doesn't work for the original version.\r\n\r\nThe fix is done based on version 1.2 of \"verilog_systemverilog.vim\".\r\n","4":"This is the \"bug fix\" version of \"verilog_systemverilog.vim\" vimscript #1586 created by Amit Sethi.\r\n\r\nWith this fixed version, the key \"%\" (matchit.vim) works for Verilog\/SystemVerilog files, which doesn't work for the original version.\r\n\r\nThe fix is done based on version 1.2 of \"verilog_systemverilog.vim\".\r\n","install_details":"Copy all files in the package into your personal vim directory, keeping the directory structure.\r\n(For Windows, it should be \"$VIM\/vimfiles\/\")\r\n(For *nix, it should be \"~\/.vim\/\")","5":"Copy all files in the package into your personal vim directory, keeping the directory structure.\r\n(For Windows, it should be \"$VIM\/vimfiles\/\")\r\n(For *nix, it should be \"~\/.vim\/\")","first_name":"AyuanX","6":"AyuanX","last_name":" ","7":" ","releases":[{"0":"3332","vim_version":"6.0","1":"6.0","script_version":"1.3","2":"1.3","version_comment":"Initial upload","3":"Initial upload","package":"verilog_systemverilog_fix.zip","4":"verilog_systemverilog_fix.zip","src_id":"14293","5":"14293","creation_date":"1290069703","6":"1290069703"}]},"3331":{"script_id":"3331","0":"3331","script_name":"lua_omni","1":"lua_omni","script_type":"ftplugin","2":"ftplugin","summary":"omni completion for Lua plus few extras","3":"omni completion for Lua plus few extras","description":"This is my omni completion plugin for Lua. It works by scanning _G and parsing\r\nVim buffers. It's also possible to specify external text files with Lua names\r\npaths (delimited with new line). It's a very useful feature when a module can\r\nnot be loaded or doesn't have iterable table exposed.\r\n\r\nNested tables are supported so you can type:\r\n:lua foobar = {numbers = {one = 1, two = 2, three = 3}}\r\n\r\nThen typing CTRL-X CTRL-O list of possible matches will open:\r\n  foobar.numbers.one\r\n  foobar.numbers.two\r\n  foobar.numbers.three\r\n\r\nActually you can use globbing \"*\" and \"?\" characters to speed up typing like:\r\n  f*tw CTRL-X CTRL-O\r\nwill output immediately:\r\n  foobar.numbers.two\r\n\r\nSingle word can be used as well:\r\nthree CTRL-X CTRL-O\r\nwill give:\r\n  foobar.numbers.three\r\nOr even just \"thr\" will work too.\r\n\r\nAnother way use completion is without any asterisks like:\r\np.l.m CTRL-X CTRL-O\r\nto get:\r\n  package.loaded.math\r\n\r\n\r\nThat is the new way of doing omni from this version. I've found it to be quicker\r\nand more convenient than multiple hitting CTR-X CTRL-O.\r\nLocal variables completion works as before.\r\n\r\n\r\nSome other functions are supported like listing defined Lua functions in\r\ncurrent buffer.\r\nThere are common Lua abbreviation defined in lua_omni.vim too.\r\n\r\n                                                                       \r\nMappings:\r\n\r\nCTRL-X CTRL-O\r\n    Calling the omni completion function.\r\n\r\n<Leader>fl  or  <Plug>PrintFunctionList\r\n    Prints list of defined Lua functions in current buffer. They are listed in\r\n    ascending line numbers order. Luadoc titles (if defined) are showed too.\r\n                                                                       \r\n<Leader>lf  or  <Plug>WriteAndLuaFile\r\n    Just a shortcut to call:\r\n        :w\r\n:luafile %\r\n\r\n<Leader>sli or  <Plug>SetLuaIabbrevs\r\n    Sets few common and useful insert mode abbreviations.\r\n\r\n<Leader>cli or  <Plug>ClearLuaIabbrevs\r\n    Clear any insert mode abbreviations set by previous shortcut.\r\n\r\n                                                                       \r\n                        *lua_omni-settings*\r\n\r\nFrom 0.16 version there is support for external files with completion paths.\r\nThey can be specified via shell LUA_OMNI variable. Each file path should be\r\ndelimited by comma or semicolon. Additionally the same can done using Vim\r\nb:lua_omni and g:lua_omni variables. The b: if exists will override g: however\r\nshell LUA_OMNI will be read and used in all cases.\r\n\r\nFormat of completions files is very simple. Each line contains single Lua\r\npath like:\r\n\r\nfoomodule.barPart\r\nfoomodule.barPart.spam\r\nfoomodule.barPart.spam.not\r\nfoomodule.barPart.spam.twice\r\nfoomodule.barPart.spam.multiply\r\nfoomodule.__inner\r\nfoomodule.__inner.foo\r\nmath2mod\r\nmath2mod.exp\r\nmath2mod.div\r\n...\r\n(and so on)\r\n\r\nOrder of lines is meaningless as results are sorted anyway.\r\nYou may try lapg.lua script to generate such completion list automatically.\r\n\r\n\r\nFrom 0.17 version there is folding using foldexpr function. To enable it just\r\nset foldenable option. It has configurable variables: g:lua_inner_folds and\r\nb:lua_inner_folds. When set to 1 folding is nested. When not existent, or set\r\nto other value than 1, folds will have one level only.  Of course the b:\r\nversion will override the g:.\r\n\r\nTo regenerate folds use the zx or zX normal commands.\r\n\r\nThough folding function try not to fold malformed blocks it depends on correct\r\norder of opening\/closing statements.","4":"This is my omni completion plugin for Lua. It works by scanning _G and parsing\r\nVim buffers. It's also possible to specify external text files with Lua names\r\npaths (delimited with new line). It's a very useful feature when a module can\r\nnot be loaded or doesn't have iterable table exposed.\r\n\r\nNested tables are supported so you can type:\r\n:lua foobar = {numbers = {one = 1, two = 2, three = 3}}\r\n\r\nThen typing CTRL-X CTRL-O list of possible matches will open:\r\n  foobar.numbers.one\r\n  foobar.numbers.two\r\n  foobar.numbers.three\r\n\r\nActually you can use globbing \"*\" and \"?\" characters to speed up typing like:\r\n  f*tw CTRL-X CTRL-O\r\nwill output immediately:\r\n  foobar.numbers.two\r\n\r\nSingle word can be used as well:\r\nthree CTRL-X CTRL-O\r\nwill give:\r\n  foobar.numbers.three\r\nOr even just \"thr\" will work too.\r\n\r\nAnother way use completion is without any asterisks like:\r\np.l.m CTRL-X CTRL-O\r\nto get:\r\n  package.loaded.math\r\n\r\n\r\nThat is the new way of doing omni from this version. I've found it to be quicker\r\nand more convenient than multiple hitting CTR-X CTRL-O.\r\nLocal variables completion works as before.\r\n\r\n\r\nSome other functions are supported like listing defined Lua functions in\r\ncurrent buffer.\r\nThere are common Lua abbreviation defined in lua_omni.vim too.\r\n\r\n                                                                       \r\nMappings:\r\n\r\nCTRL-X CTRL-O\r\n    Calling the omni completion function.\r\n\r\n<Leader>fl  or  <Plug>PrintFunctionList\r\n    Prints list of defined Lua functions in current buffer. They are listed in\r\n    ascending line numbers order. Luadoc titles (if defined) are showed too.\r\n                                                                       \r\n<Leader>lf  or  <Plug>WriteAndLuaFile\r\n    Just a shortcut to call:\r\n        :w\r\n:luafile %\r\n\r\n<Leader>sli or  <Plug>SetLuaIabbrevs\r\n    Sets few common and useful insert mode abbreviations.\r\n\r\n<Leader>cli or  <Plug>ClearLuaIabbrevs\r\n    Clear any insert mode abbreviations set by previous shortcut.\r\n\r\n                                                                       \r\n                        *lua_omni-settings*\r\n\r\nFrom 0.16 version there is support for external files with completion paths.\r\nThey can be specified via shell LUA_OMNI variable. Each file path should be\r\ndelimited by comma or semicolon. Additionally the same can done using Vim\r\nb:lua_omni and g:lua_omni variables. The b: if exists will override g: however\r\nshell LUA_OMNI will be read and used in all cases.\r\n\r\nFormat of completions files is very simple. Each line contains single Lua\r\npath like:\r\n\r\nfoomodule.barPart\r\nfoomodule.barPart.spam\r\nfoomodule.barPart.spam.not\r\nfoomodule.barPart.spam.twice\r\nfoomodule.barPart.spam.multiply\r\nfoomodule.__inner\r\nfoomodule.__inner.foo\r\nmath2mod\r\nmath2mod.exp\r\nmath2mod.div\r\n...\r\n(and so on)\r\n\r\nOrder of lines is meaningless as results are sorted anyway.\r\nYou may try lapg.lua script to generate such completion list automatically.\r\n\r\n\r\nFrom 0.17 version there is folding using foldexpr function. To enable it just\r\nset foldenable option. It has configurable variables: g:lua_inner_folds and\r\nb:lua_inner_folds. When set to 1 folding is nested. When not existent, or set\r\nto other value than 1, folds will have one level only.  Of course the b:\r\nversion will override the g:.\r\n\r\nTo regenerate folds use the zx or zX normal commands.\r\n\r\nThough folding function try not to fold malformed blocks it depends on correct\r\norder of opening\/closing statements.","install_details":"Just extract and copy files from lua_omni.zip into local .vim\/ftplugin and\r\n.vim\/doc directories. Then execute in Vim:\r\n\t:helptags ~\/.vim\/doc\r\n\r\nAlternatively you may download it from github at:\r\ngit@github.com:rkowal\/Lua-Omni-Vim-Completion.git\r\n\r\nTo get a help type:\r\n\t:help lua_omni\r\n\r\nBeware! Vim 7.3 is needed with enabled Lua support.","5":"Just extract and copy files from lua_omni.zip into local .vim\/ftplugin and\r\n.vim\/doc directories. Then execute in Vim:\r\n\t:helptags ~\/.vim\/doc\r\n\r\nAlternatively you may download it from github at:\r\ngit@github.com:rkowal\/Lua-Omni-Vim-Completion.git\r\n\r\nTo get a help type:\r\n\t:help lua_omni\r\n\r\nBeware! Vim 7.3 is needed with enabled Lua support.","first_name":"Radek","6":"Radek","last_name":"Kowalski","7":"Kowalski","releases":[{"0":"3331","vim_version":"7.3","1":"7.3","script_version":"0.17","2":"0.17","version_comment":"+ added folding for Lua code by foldexpr function","3":"+ added folding for Lua code by foldexpr function","package":"lua_omni_v0.17.zip","4":"lua_omni_v0.17.zip","src_id":"15686","5":"15686","creation_date":"1305899678","6":"1305899678"},{"0":"3331","vim_version":"7.3","1":"7.3","script_version":"0.165","2":"0.165","version_comment":"+ variables defined in for loops should complete now\r\n+ changed find_assigments function\r\n+ added the lapg.lua script for auto generating Lua completion list names\r\n  from documentation (html or text files)\r\n+ changed licence to MIT","3":"+ variables defined in for loops should complete now\r\n+ changed find_assigments function\r\n+ added the lapg.lua script for auto generating Lua completion list names\r\n  from documentation (html or text files)\r\n+ changed licence to MIT","package":"lua_omni_v0.165.zip","4":"lua_omni_v0.165.zip","src_id":"15565","5":"15565","creation_date":"1304281311","6":"1304281311"},{"0":"3331","vim_version":"7.3","1":"7.3","script_version":"0.163","2":"0.163","version_comment":"+ new variable completion now can see variables names in function\r\n  definitions too","3":"+ new variable completion now can see variables names in function\r\n  definitions too","package":"lua_omni_v0.163.zip","4":"lua_omni_v0.163.zip","src_id":"15534","5":"15534","creation_date":"1303892471","6":"1303892471"},{"0":"3331","vim_version":"7.3","1":"7.3","script_version":"0.162","2":"0.162","version_comment":"+ fixed bug in print_function_list when a buffer doesn\\'t have any\r\n  functions\r\n+ added better variable assignments completion","3":"+ fixed bug in print_function_list when a buffer doesn\\'t have any\r\n  functions\r\n+ added better variable assignments completion","package":"lua_omni_v0.162.zip","4":"lua_omni_v0.162.zip","src_id":"15533","5":"15533","creation_date":"1303839393","6":"1303839393"},{"0":"3331","vim_version":"7.3","1":"7.3","script_version":"0.16","2":"0.16","version_comment":"+ user can specify files with Lua completions using shell LUA_OMNI and Vim\r\n  b:lua_omni, g:lua_omni variables\r\n  (useful when _G context can not have everything loaded)","3":"+ user can specify files with Lua completions using shell LUA_OMNI and Vim\r\n  b:lua_omni, g:lua_omni variables\r\n  (useful when _G context can not have everything loaded)","package":"lua_omni_v0.16.zip","4":"lua_omni_v0.16.zip","src_id":"15527","5":"15527","creation_date":"1303810560","6":"1303810560"},{"0":"3331","vim_version":"7.3","1":"7.3","script_version":"0.151","2":"0.151","version_comment":"+ fixed small (thought irritating) bug in completion_findstart function\r\n","3":"+ fixed small (thought irritating) bug in completion_findstart function\r\n","package":"lua_omni_v0.151.zip","4":"lua_omni_v0.151.zip","src_id":"15487","5":"15487","creation_date":"1303306846","6":"1303306846"},{"0":"3331","vim_version":"7.3","1":"7.3","script_version":"0.15","2":"0.15","version_comment":"+ More convenient completion where single words or asterisk less shortcuts\r\n  will work too.","3":"+ More convenient completion where single words or asterisk less shortcuts\r\n  will work too.","package":"lua_omni_rev0.15.zip","4":"lua_omni_rev0.15.zip","src_id":"15393","5":"15393","creation_date":"1302041662","6":"1302041662"},{"0":"3331","vim_version":"7.3","1":"7.3","script_version":"0.141","2":"0.141","version_comment":"+ Minor fix in completing function where was a chance to concat table with\r\n  string.","3":"+ Minor fix in completing function where was a chance to concat table with\r\n  string.","package":"lua_omni_rev0.141.zip","4":"lua_omni_rev0.141.zip","src_id":"15331","5":"15331","creation_date":"1301413400","6":"1301413400"},{"0":"3331","vim_version":"7.3","1":"7.3","script_version":"0.14","2":"0.14","version_comment":"+ Fixed bug in new completing function so root level names in _G table are\r\n  actually showed.\r\n+ Fixed previously introduced bugs in Vim mappings.","3":"+ Fixed bug in new completing function so root level names in _G table are\r\n  actually showed.\r\n+ Fixed previously introduced bugs in Vim mappings.","package":"lua_omni_rev0.14.zip","4":"lua_omni_rev0.14.zip","src_id":"15318","5":"15318","creation_date":"1301343843","6":"1301343843"},{"0":"3331","vim_version":"7.3","1":"7.3","script_version":"0.13","2":"0.13","version_comment":"    + Changed scanning of _G table to more elaborate way. Now a \"globbing\" \"*\"\r\n\t  and \"?\" characters may be used when typing.\r\n    + Few additions to abbreviations.\r\n","3":"    + Changed scanning of _G table to more elaborate way. Now a \"globbing\" \"*\"\r\n\t  and \"?\" characters may be used when typing.\r\n    + Few additions to abbreviations.\r\n","package":"lua_omni_rev0.13.zip","4":"lua_omni_rev0.13.zip","src_id":"15289","5":"15289","creation_date":"1301080877","6":"1301080877"},{"0":"3331","vim_version":"7.3","1":"7.3","script_version":"0.12","2":"0.12","version_comment":"+ improved Lua search_assignments1 function to search variable names in \"for in\" and function statements\r\n","3":"+ improved Lua search_assignments1 function to search variable names in \"for in\" and function statements\r\n","package":"lua_omni_012.zip","4":"lua_omni_012.zip","src_id":"14392","5":"14392","creation_date":"1291034972","6":"1291034972"},{"0":"3331","vim_version":"7.3","1":"7.3","script_version":"0.11","2":"0.11","version_comment":"---------------------------------------------------------------------------------------\r\n  RELEASE NOTES FOR VERSION 0.11\r\n---------------------------------------------------------------------------------------\r\n\t+ fixed error in abbreviations \r\n\t+ added abbreviation for string.len\r\n\t+ expanded omnifunc functionality to scan local function variables (works\r\n\t  for the most part)","3":"---------------------------------------------------------------------------------------\r\n  RELEASE NOTES FOR VERSION 0.11\r\n---------------------------------------------------------------------------------------\r\n\t+ fixed error in abbreviations \r\n\t+ added abbreviation for string.len\r\n\t+ expanded omnifunc functionality to scan local function variables (works\r\n\t  for the most part)","package":"lua_omni_011.zip","4":"lua_omni_011.zip","src_id":"14333","5":"14333","creation_date":"1290295102","6":"1290295102"},{"0":"3331","vim_version":"7.3","1":"7.3","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"lua_omni.zip","4":"lua_omni.zip","src_id":"14285","5":"14285","creation_date":"1290008967","6":"1290008967"}]},"3330":{"script_id":"3330","0":"3330","script_name":"unite-locate","1":"unite-locate","script_type":"utility","2":"utility","summary":"A Unite.vim plugin to find\/open files easily, using locate command","3":"A Unite.vim plugin to find\/open files easily, using locate command","description":"A Unite.vim plugin to find\/open files easily, using locate command.\nSee details in the following pages.\n\n* http:\/\/github.com\/ujihisa\/unite-locate (development)\n\nDependency: locate command\n","4":"A Unite.vim plugin to find\/open files easily, using locate command.\nSee details in the following pages.\n\n* http:\/\/github.com\/ujihisa\/unite-locate (development)\n\nDependency: locate command\n","install_details":"After you install Shougo's unite.vim, unarchive the zip file into a directory that is under &rtp of your Vim, including ~\/.vim dir.\n","5":"After you install Shougo's unite.vim, unarchive the zip file into a directory that is under &rtp of your Vim, including ~\/.vim dir.\n","first_name":"ujihisa","6":"ujihisa","last_name":".","7":".","releases":[{"0":"3330","vim_version":"7.3","1":"7.3","script_version":"1.5","2":"1.5","version_comment":"* Windows \"everything\" support. Thanks mattn!\n","3":"* Windows \"everything\" support. Thanks mattn!\n","package":"unite-locate-1.5.zip","4":"unite-locate-1.5.zip","src_id":"16235","5":"16235","creation_date":"1313024451","6":"1313024451"},{"0":"3330","vim_version":"7.3","1":"7.3","script_version":"1.4","2":"1.4","version_comment":"* Bugfix in case you don't have locate command.\n","3":"* Bugfix in case you don't have locate command.\n","package":"unite-locate-1.4.zip","4":"unite-locate-1.4.zip","src_id":"14960","5":"14960","creation_date":"1296970368","6":"1296970368"},{"0":"3330","vim_version":"7.3","1":"7.3","script_version":"1.3","2":"1.3","version_comment":"* Bugfix for files which have spaces. This patch is from sgur; thanks sgur!\n","3":"* Bugfix for files which have spaces. This patch is from sgur; thanks sgur!\n","package":"unite-locate-1.3.zip","4":"unite-locate-1.3.zip","src_id":"14435","5":"14435","creation_date":"1291485318","6":"1291485318"},{"0":"3330","vim_version":"7.3","1":"7.3","script_version":"1.2","2":"1.2","version_comment":"* Uses Unite's system() instead of Vim builtin system()\n","3":"* Uses Unite's system() instead of Vim builtin system()\n","package":"unite-locate-1.2.zip","4":"unite-locate-1.2.zip","src_id":"14345","5":"14345","creation_date":"1290400232","6":"1290400232"},{"0":"3330","vim_version":"7.3","1":"7.3","script_version":"1.1","2":"1.1","version_comment":"* Uses Unite's required_pattern_length\n* Uses locate's -e option when the platform is Linux\n","3":"* Uses Unite's required_pattern_length\n* Uses locate's -e option when the platform is Linux\n","package":"unite-locate-1.1.zip","4":"unite-locate-1.1.zip","src_id":"14304","5":"14304","creation_date":"1290155867","6":"1290155867"},{"0":"3330","vim_version":"7.3","1":"7.3","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"unite-locate-1.0.zip","4":"unite-locate-1.0.zip","src_id":"14279","5":"14279","creation_date":"1289968077","6":"1289968077"}]},"3329":{"script_id":"3329","0":"3329","script_name":"VimCalc","1":"VimCalc","script_type":"utility","2":"utility","summary":"Plugin that provides a convenient interactive calculator inside a Vim buffer.","3":"Plugin that provides a convenient interactive calculator inside a Vim buffer.","description":"VimCalc provides a convenient way to access a powerful interactive calculator whilst inside a Vim session. Quickly rattle off a few sums to test an idea. Perform complex calculations using built-in functions to validate answers. Quickly and simply convert from octal to hex to decimal and back again. Setup a bunch of variables to be used in a complex expression. Change variables easily and then simply re-evaluate the expression. Whatever you may need a calculator for, VimCalc is up to the task.\r\n\r\nNot only can VimCalc calculate but it uses Vim for input and editing. Quickly and easily perform edits on previous calculations using the power of Vim and then re-evaluate them by simply hitting return. Once you've got the answers yank them into several registers and paste with ease into other buffers. All whilst never leaving your Vim editing session!\r\n\r\nSee VimCalc's homepage for screenshots. http:\/\/gregsexton.github.com\/VimCalc\/\r\n\r\nHere are some example expressions run in a VimCalc session:\r\n\r\n> 5+4\r\nans = 9.0\r\n> let x = 4\r\nx = 4.0\r\n> 9 * sqrt(4)\r\nans = 18.0\r\n> 9**2 - (sqrt(4)+2)\r\nans = 77.0\r\n> 0xff + 2\r\nans = 257.0\r\n\r\nHere is an example of calculating the roots of a quadratic equation:\r\n\r\n> let a = 2\r\na = 2.0\r\n> let b = -1\r\nb = -1.0\r\n> let c = -6\r\nc = -6.0\r\n> ((b*-1) + sqrt(b**2 - 4*a*c))\/(2*a)\r\nans = 2.0\r\n> ((b*-1) - sqrt(b**2 - 4*a*c))\/(2*a)\r\nans = -1.5","4":"VimCalc provides a convenient way to access a powerful interactive calculator whilst inside a Vim session. Quickly rattle off a few sums to test an idea. Perform complex calculations using built-in functions to validate answers. Quickly and simply convert from octal to hex to decimal and back again. Setup a bunch of variables to be used in a complex expression. Change variables easily and then simply re-evaluate the expression. Whatever you may need a calculator for, VimCalc is up to the task.\r\n\r\nNot only can VimCalc calculate but it uses Vim for input and editing. Quickly and easily perform edits on previous calculations using the power of Vim and then re-evaluate them by simply hitting return. Once you've got the answers yank them into several registers and paste with ease into other buffers. All whilst never leaving your Vim editing session!\r\n\r\nSee VimCalc's homepage for screenshots. http:\/\/gregsexton.github.com\/VimCalc\/\r\n\r\nHere are some example expressions run in a VimCalc session:\r\n\r\n> 5+4\r\nans = 9.0\r\n> let x = 4\r\nx = 4.0\r\n> 9 * sqrt(4)\r\nans = 18.0\r\n> 9**2 - (sqrt(4)+2)\r\nans = 77.0\r\n> 0xff + 2\r\nans = 257.0\r\n\r\nHere is an example of calculating the roots of a quadratic equation:\r\n\r\n> let a = 2\r\na = 2.0\r\n> let b = -1\r\nb = -1.0\r\n> let c = -6\r\nc = -6.0\r\n> ((b*-1) + sqrt(b**2 - 4*a*c))\/(2*a)\r\nans = 2.0\r\n> ((b*-1) - sqrt(b**2 - 4*a*c))\/(2*a)\r\nans = -1.5","install_details":"Requirements\r\n\r\nVim 7.0+ with +python.\r\nPython installed.\r\n\r\nIf you're compiling Vim from source, be sure to use the --enable-pythoninterp option. Otherwise check your OS's package distro for a version of Vim with Python support. On OS X the best option is MacVim. VimCalc should work on Windows too, you will need to install the correct python dll for the version of Vim you are using. Please see the web for help with this.\r\n\r\nInstallation\r\n\r\nDownload the latest source from https:\/\/github.com\/gregsexton\/VimCalc.\r\n\r\nExtract (or copy) all of the files into your Vim runtime directory, ensuring that they are placed into the correct subdirectories. Then update your help tags file to enable VimCalc help. See :help add-local-help in Vim for details.\r\n\r\nIf you like and find VimCalc useful be sure to vote for this script! ","5":"Requirements\r\n\r\nVim 7.0+ with +python.\r\nPython installed.\r\n\r\nIf you're compiling Vim from source, be sure to use the --enable-pythoninterp option. Otherwise check your OS's package distro for a version of Vim with Python support. On OS X the best option is MacVim. VimCalc should work on Windows too, you will need to install the correct python dll for the version of Vim you are using. Please see the web for help with this.\r\n\r\nInstallation\r\n\r\nDownload the latest source from https:\/\/github.com\/gregsexton\/VimCalc.\r\n\r\nExtract (or copy) all of the files into your Vim runtime directory, ensuring that they are placed into the correct subdirectories. Then update your help tags file to enable VimCalc help. See :help add-local-help in Vim for details.\r\n\r\nIf you like and find VimCalc useful be sure to vote for this script! ","first_name":"Greg","6":"Greg","last_name":"Sexton","7":"Sexton","releases":[{"0":"3329","vim_version":"7.0","1":"7.0","script_version":"1.3","2":"1.3","version_comment":"Added :int and :float directives.\r\nAdded :status directive and improved directive highlighting.\r\nAdded :vars directive.\r\nAdded :q directive.\r\nMade 'let' optional during assignment.\r\nEverything is now unit tested with python code seperated.","3":"Added :int and :float directives.\r\nAdded :status directive and improved directive highlighting.\r\nAdded :vars directive.\r\nAdded :q directive.\r\nMade 'let' optional during assignment.\r\nEverything is now unit tested with python code seperated.","package":"vimcalc-v1.3.zip","4":"vimcalc-v1.3.zip","src_id":"15317","5":"15317","creation_date":"1301342206","6":"1301342206"},{"0":"3329","vim_version":"7.0","1":"7.0","script_version":"1.2","2":"1.2","version_comment":"Fixed a bug where global variables used for customisation were overwritten when VimCalc was sourced.","3":"Fixed a bug where global variables used for customisation were overwritten when VimCalc was sourced.","package":"vimcalc-v1.2.zip","4":"vimcalc-v1.2.zip","src_id":"15083","5":"15083","creation_date":"1298401317","6":"1298401317"},{"0":"3329","vim_version":"7.0","1":"7.0","script_version":"v1.1","2":"v1.1","version_comment":"Added extra configuration options to allow for initial window positioning. Also for entering the buffer in insert mode and leaving the buffer using <C-W> commands whilst in insert mode.\r\n","3":"Added extra configuration options to allow for initial window positioning. Also for entering the buffer in insert mode and leaving the buffer using <C-W> commands whilst in insert mode.\r\n","package":"vimcalc-1.1.zip","4":"vimcalc-1.1.zip","src_id":"15044","5":"15044","creation_date":"1298119381","6":"1298119381"},{"0":"3329","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"vimcalc.zip","4":"vimcalc.zip","src_id":"14275","5":"14275","creation_date":"1289946415","6":"1289946415"}]},"3328":{"script_id":"3328","0":"3328","script_name":"Blueshift","1":"Blueshift","script_type":"color scheme","2":"color scheme","summary":"Light color scheme (white background, Visual Studio and Python colors)","3":"Light color scheme (white background, Visual Studio and Python colors)","description":"I use this color scheme when I want a clean and bright coding environment.\r\nIt's inspired by:\r\n  - Visual Studio colors\r\n  - pyte color scheme vimscript #1492.\r\n\r\nScreenshot:\r\n\r\nhttp:\/\/zwiener.org\/pics\/blueshift.png","4":"I use this color scheme when I want a clean and bright coding environment.\r\nIt's inspired by:\r\n  - Visual Studio colors\r\n  - pyte color scheme vimscript #1492.\r\n\r\nScreenshot:\r\n\r\nhttp:\/\/zwiener.org\/pics\/blueshift.png","install_details":"Just copy blueshift.vim to your vim colors directory and activate it with:\r\n\r\ncolorscheme blueshift\r\n","5":"Just copy blueshift.vim to your vim colors directory and activate it with:\r\n\r\ncolorscheme blueshift\r\n","first_name":"Jan","6":"Jan","last_name":"Zwiener","7":"Zwiener","releases":[{"0":"3328","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"blueshift.vim","4":"blueshift.vim","src_id":"14274","5":"14274","creation_date":"1289925372","6":"1289925372"}]},"3327":{"script_id":"3327","0":"3327","script_name":"PyScratch","1":"PyScratch","script_type":"utility","2":"utility","summary":"allows processing of Python\/Ruby\/Perl\/Lua commands directly in Vim buffer","3":"allows processing of Python\/Ruby\/Perl\/Lua commands directly in Vim buffer","description":"PyScratch is a simple plugin that lets you use any Vim buffer as a scratchpad for running and viewing the output of Python, Ruby, Perl, and Lua commands.  (Note the name 'PyScratch' is no longer accurate and will probably be changed.)  This plugin can also be found at github:\r\nhttps:\/\/github.com\/hsitz\/PyScratch\r\n\r\nYou can watch a screencast of PyScratch at:\r\nhttp:\/\/vimeo.com\/16871727\r\n--------------------------------------------------\r\nNOTE:  You can get tab completion of your Python commands by using any of the \r\navailable methods of completion in Vim.  I've tried the Pydiction \r\ntab-completion plugin and recommend that anyone using PyScratch install Pydiction \r\n( http:\/\/www.vim.org\/scripts\/script.php?script_id=850 ) \r\n---------------------------------------------------\r\nNOTE2:  Also works with RUBY, PERL, and LUA.\r\nThe name PyScratch is now misleading, since code has been modified to work\r\nwith Ruby, Perl, and\/or Lua.  The global variable g:script_language can\r\nbe set to 'python,'ruby','perl', or 'lua', and controls which interpreter\r\nis used to process '>>>' commands and code blocks.  Support for any\r\ninterpreter you use must be compiled into your Vim.  Note also that usng Perl \r\nis a little different from the other languages, because Vim does not\r\nsupport Perl's 'print' or 'say' commands.  Instead 'VIM::Msg' is used\r\nto specify printed output.   See :help perl for more.\r\n-------------------------------------------------- \r\n\r\nThe PyScratch plugin consists of a single vimscript file that a Vim user can\r\ninstall by placing it in their 'plugin' directory.\r\n\r\nPyScratch requires a Vim executable compiled with Python support. It has been\r\ntested with Python26 but version should not matter.\r\n\r\nOver last few years several different plugins have been designed to send \r\ncommands in a Vim buffer out to a shell for processing (typically scripting the \r\n'Gnu Screen utility), where the output can be viewed.  This works well, but for \r\nlanguages where Vim has built-in support some people might prefer executing the \r\ncommands and getting output right in the Vim buffer.  All this takes is \r\nredirecting the output from a supported language's command to the user's buffer \r\ninstead of to a message buffer.  This technique is possible only for the \r\nlanguages where Vim offers compile-in support, which include Python, Perl, \r\nRuby, Lua, MZScheme (anything else?)  This plugin is specific to Python but it \r\nshould be relatively easy to extend to other supported languages.\r\n\r\nWhen the PyScratch plugin is loaded you can process Python commands and get \r\nPython output in your Vim buffer in several different ways:\r\n\r\n(1)  Prepend a '>>>' user prompt as first characters in a line, then press \r\n<enter>.  The command will be evaluated and results will be shown beginning in \r\nthe next line.  Commands that provide no output have the command itself \r\nmirrored as output as confirmation that they have been processed.  You will \r\ntypically want to issue Python print commands, and these can be abbreviated \r\nwith 'p' instead of 'print'.  Some examples:\r\n\r\n>>> print 8 + 16\r\n24\r\n>>> p 8 + 16\r\n24\r\n>>> import sys\r\n( import sys )\r\n>>> for i in range(5): print i\r\n1\r\n2\r\n3\r\n4\r\n5\r\n>>> etc. etc.\r\n\r\n(2)  You can execute a block of lines at one time by visually selecting them \r\nand pressing <ctrl_enter>.  The block should be a clean block of code with no \r\nuser prompt chars (i.e, '>>>') at left margin.  Output will be returned below \r\nthe block of lines.  Note that this method uses <ctrl-enter> rather than the \r\nsimple <enter> of the single-line-prompt method.\r\n\r\n(3)  It's not part of the plugin, but an entire file of Python can be executed \r\nwith the Vim command:   pyfile <filename>.  The plugin does not capture any \r\noutput from this command, however functions defined in the file can may then be \r\naccessed in the Vim buffer using single-line-prompt Python commands or the \r\nblock-select Python processing.\r\n\r\nThe plugin has a couple of lines defining a syntax region for error messages \r\nand a highlight command that displays them in red.  This may be overwritten by \r\na syntax file that clears all syntax settings so if you want to use these you \r\nmay want to move the syntax and the highlight command to a syntax and color \r\nfile, respectively.\r\n\r\nThis is just a Sunday afternoon hack and there are lots of little tweaks and \r\nimprovements that could be added.   I'd be happy to hear comments or \r\nsuggestions. . . \r\n","4":"PyScratch is a simple plugin that lets you use any Vim buffer as a scratchpad for running and viewing the output of Python, Ruby, Perl, and Lua commands.  (Note the name 'PyScratch' is no longer accurate and will probably be changed.)  This plugin can also be found at github:\r\nhttps:\/\/github.com\/hsitz\/PyScratch\r\n\r\nYou can watch a screencast of PyScratch at:\r\nhttp:\/\/vimeo.com\/16871727\r\n--------------------------------------------------\r\nNOTE:  You can get tab completion of your Python commands by using any of the \r\navailable methods of completion in Vim.  I've tried the Pydiction \r\ntab-completion plugin and recommend that anyone using PyScratch install Pydiction \r\n( http:\/\/www.vim.org\/scripts\/script.php?script_id=850 ) \r\n---------------------------------------------------\r\nNOTE2:  Also works with RUBY, PERL, and LUA.\r\nThe name PyScratch is now misleading, since code has been modified to work\r\nwith Ruby, Perl, and\/or Lua.  The global variable g:script_language can\r\nbe set to 'python,'ruby','perl', or 'lua', and controls which interpreter\r\nis used to process '>>>' commands and code blocks.  Support for any\r\ninterpreter you use must be compiled into your Vim.  Note also that usng Perl \r\nis a little different from the other languages, because Vim does not\r\nsupport Perl's 'print' or 'say' commands.  Instead 'VIM::Msg' is used\r\nto specify printed output.   See :help perl for more.\r\n-------------------------------------------------- \r\n\r\nThe PyScratch plugin consists of a single vimscript file that a Vim user can\r\ninstall by placing it in their 'plugin' directory.\r\n\r\nPyScratch requires a Vim executable compiled with Python support. It has been\r\ntested with Python26 but version should not matter.\r\n\r\nOver last few years several different plugins have been designed to send \r\ncommands in a Vim buffer out to a shell for processing (typically scripting the \r\n'Gnu Screen utility), where the output can be viewed.  This works well, but for \r\nlanguages where Vim has built-in support some people might prefer executing the \r\ncommands and getting output right in the Vim buffer.  All this takes is \r\nredirecting the output from a supported language's command to the user's buffer \r\ninstead of to a message buffer.  This technique is possible only for the \r\nlanguages where Vim offers compile-in support, which include Python, Perl, \r\nRuby, Lua, MZScheme (anything else?)  This plugin is specific to Python but it \r\nshould be relatively easy to extend to other supported languages.\r\n\r\nWhen the PyScratch plugin is loaded you can process Python commands and get \r\nPython output in your Vim buffer in several different ways:\r\n\r\n(1)  Prepend a '>>>' user prompt as first characters in a line, then press \r\n<enter>.  The command will be evaluated and results will be shown beginning in \r\nthe next line.  Commands that provide no output have the command itself \r\nmirrored as output as confirmation that they have been processed.  You will \r\ntypically want to issue Python print commands, and these can be abbreviated \r\nwith 'p' instead of 'print'.  Some examples:\r\n\r\n>>> print 8 + 16\r\n24\r\n>>> p 8 + 16\r\n24\r\n>>> import sys\r\n( import sys )\r\n>>> for i in range(5): print i\r\n1\r\n2\r\n3\r\n4\r\n5\r\n>>> etc. etc.\r\n\r\n(2)  You can execute a block of lines at one time by visually selecting them \r\nand pressing <ctrl_enter>.  The block should be a clean block of code with no \r\nuser prompt chars (i.e, '>>>') at left margin.  Output will be returned below \r\nthe block of lines.  Note that this method uses <ctrl-enter> rather than the \r\nsimple <enter> of the single-line-prompt method.\r\n\r\n(3)  It's not part of the plugin, but an entire file of Python can be executed \r\nwith the Vim command:   pyfile <filename>.  The plugin does not capture any \r\noutput from this command, however functions defined in the file can may then be \r\naccessed in the Vim buffer using single-line-prompt Python commands or the \r\nblock-select Python processing.\r\n\r\nThe plugin has a couple of lines defining a syntax region for error messages \r\nand a highlight command that displays them in red.  This may be overwritten by \r\na syntax file that clears all syntax settings so if you want to use these you \r\nmay want to move the syntax and the highlight command to a syntax and color \r\nfile, respectively.\r\n\r\nThis is just a Sunday afternoon hack and there are lots of little tweaks and \r\nimprovements that could be added.   I'd be happy to hear comments or \r\nsuggestions. . . \r\n","install_details":"Put the pyscratch.vim file in your .vim\/plugin or vimfiles\/plugin directory.  Functionality will then be available in any Vim buffer.","5":"Put the pyscratch.vim file in your .vim\/plugin or vimfiles\/plugin directory.  Functionality will then be available in any Vim buffer.","first_name":"Herbert","6":"Herbert","last_name":"Sitz","7":"Sitz","releases":[{"0":"3327","vim_version":"7.0","1":"7.0","script_version":"0.15","2":"0.15","version_comment":"Added support for Ruby, Perl, and Lua","3":"Added support for Ruby, Perl, and Lua","package":"PyScratch-015.zip","4":"PyScratch-015.zip","src_id":"14329","5":"14329","creation_date":"1290268985","6":"1290268985"},{"0":"3327","vim_version":"7.0","1":"7.0","script_version":"0.11","2":"0.11","version_comment":"Fixed major bug that interfered with entering <CR> when in insert mode.","3":"Fixed major bug that interfered with entering <CR> when in insert mode.","package":"PyScratch-0-11.zip","4":"PyScratch-0-11.zip","src_id":"14273","5":"14273","creation_date":"1289875917","6":"1289875917"}]},"3326":{"script_id":"3326","0":"3326","script_name":"stakeholders","1":"stakeholders","script_type":"utility","2":"utility","summary":"Pimp up your old templates with dynamic place-holders","3":"Pimp up your old templates with dynamic place-holders","description":"Experimental.\r\n\r\nOlder templating plugins for VIM often used simple markup for placeholders (e.g. <+VARIABLE_NAME+>). A placeholder was simply a pattern you could easily search for. Some newer templating plugins support dynamic replacement of placeholders with the same name.\r\n\r\nThe stakeholders plugin turns your old templating system into a high  potential overachiever. It provides dynamic replacement of placeholders with the same name\/ID for older templating plugins. By default, it assumes placeholders match \/<+\\([[:alpha:]_]\\+\\)+>\/ since this pattern is used in several templating systems (e.g., vimscript #1160). You can easily change that pattern by setting |g:stakeholders#def| or b:stakeholders_def.\r\n\r\n\r\nUsage~\r\n\r\nThe tskeleton templating plugin provides a parameter (|g:tskeleton#enable_stakeholders|) that enables integration with the stakeholders plugin. For other templating plugins, you have to enable stakeholders by calling either |stakeholders#EnableBuffer()| or |stakeholders#EnableInRange()|.\r\n\r\nDemo: \r\nhttp:\/\/vimsomnia.blogspot.com\/2010\/11\/tskeleton-and-stakeholders-vim-plugins.html\r\n\r\nAlso available via git: http:\/\/github.com\/tomtom\/stakeholders_vim\/","4":"Experimental.\r\n\r\nOlder templating plugins for VIM often used simple markup for placeholders (e.g. <+VARIABLE_NAME+>). A placeholder was simply a pattern you could easily search for. Some newer templating plugins support dynamic replacement of placeholders with the same name.\r\n\r\nThe stakeholders plugin turns your old templating system into a high  potential overachiever. It provides dynamic replacement of placeholders with the same name\/ID for older templating plugins. By default, it assumes placeholders match \/<+\\([[:alpha:]_]\\+\\)+>\/ since this pattern is used in several templating systems (e.g., vimscript #1160). You can easily change that pattern by setting |g:stakeholders#def| or b:stakeholders_def.\r\n\r\n\r\nUsage~\r\n\r\nThe tskeleton templating plugin provides a parameter (|g:tskeleton#enable_stakeholders|) that enables integration with the stakeholders plugin. For other templating plugins, you have to enable stakeholders by calling either |stakeholders#EnableBuffer()| or |stakeholders#EnableInRange()|.\r\n\r\nDemo: \r\nhttp:\/\/vimsomnia.blogspot.com\/2010\/11\/tskeleton-and-stakeholders-vim-plugins.html\r\n\r\nAlso available via git: http:\/\/github.com\/tomtom\/stakeholders_vim\/","install_details":"In order to install the vba, open the vba file in VIM and type: >\r\n\r\n    :so %\r\n\r\nSee :help vimball for details.","5":"In order to install the vba, open the vba file in VIM and type: >\r\n\r\n    :so %\r\n\r\nSee :help vimball for details.","first_name":"Tom","6":"Tom","last_name":"Link","7":"Link","releases":[{"0":"3326","vim_version":"7.0","1":"7.0","script_version":"0.03","2":"0.03","version_comment":"- .gitignore\n- Support for tSkeleton's <+NAME\/replacement+> syntax\n- Make s:CursorMoved() accessible as stakeholders#CursorMoved() .\n- s:Init(): run :g with :silent prefix\n- addon-info\n- Help template\nMD5 checksum: acb1eb60cee1c8d45b4f519fd0f3fa3e","3":"- .gitignore\n- Support for tSkeleton's <+NAME\/replacement+> syntax\n- Make s:CursorMoved() accessible as stakeholders#CursorMoved() .\n- s:Init(): run :g with :silent prefix\n- addon-info\n- Help template\nMD5 checksum: acb1eb60cee1c8d45b4f519fd0f3fa3e","package":"stakeholders.vba","4":"stakeholders.vba","src_id":"22103","5":"22103","creation_date":"1403975985","6":"1403975985"},{"0":"3326","vim_version":"7.0","1":"7.0","script_version":"0.02","2":"0.02","version_comment":"- Alternative, slightly more robust approach\n- g:stakeholders#undo_breaks: Break undo sequences\n- Globally enable, disable stakeholders; Replace* functions became methods of the stakeholders prototype\n- If b:stakeholders_range is defined (e.g. by #EnableInRange()), replace placeholder only in that range.\nMD5 checksum: 9878bd0328b2abd4a162f9efa45d3599","3":"- Alternative, slightly more robust approach\n- g:stakeholders#undo_breaks: Break undo sequences\n- Globally enable, disable stakeholders; Replace* functions became methods of the stakeholders prototype\n- If b:stakeholders_range is defined (e.g. by #EnableInRange()), replace placeholder only in that range.\nMD5 checksum: 9878bd0328b2abd4a162f9efa45d3599","package":"stakeholders.vba","4":"stakeholders.vba","src_id":"14348","5":"14348","creation_date":"1290445318","6":"1290445318"},{"0":"3326","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"stakeholders.vba","4":"stakeholders.vba","src_id":"14265","5":"14265","creation_date":"1289811139","6":"1289811139"}]},"3325":{"script_id":"3325","0":"3325","script_name":"vim-fileutils","1":"vim-fileutils","script_type":"utility","2":"utility","summary":"Cross-platform file manipulation library","3":"Cross-platform file manipulation library","description":"**This plugin is deprecated, all its features are accessible with os resource of  frawor plugin (vimscript #3631)**\r\n\r\nCross-platform file manipulation library, alpha version.\r\n\r\nDocumentation: http:\/\/vimpluginloader.sourceforge.net\/doc\/vim-fileutils.txt.html\r\nProject page: http:\/\/bitbucket.org\/ZyX_I\/vim-fileutils\/overview","4":"**This plugin is deprecated, all its features are accessible with os resource of  frawor plugin (vimscript #3631)**\r\n\r\nCross-platform file manipulation library, alpha version.\r\n\r\nDocumentation: http:\/\/vimpluginloader.sourceforge.net\/doc\/vim-fileutils.txt.html\r\nProject page: http:\/\/bitbucket.org\/ZyX_I\/vim-fileutils\/overview","install_details":"You can install this plugin using scriptmanager (vimscript #2905) plugin (install scriptmanager, run ``ActivateAddons vimpluginloader'' and add ``call vam#ActivateAddons([\"vimpluginloader\"])'' to your .vimrc.).\r\n\r\nGentoo users can use the following mercurial overlay: http:\/\/vimpluginloader.hg.sourceforge.net:8000\/hgroot\/vimpluginloader\/pluginloader-overlay.","5":"You can install this plugin using scriptmanager (vimscript #2905) plugin (install scriptmanager, run ``ActivateAddons vimpluginloader'' and add ``call vam#ActivateAddons([\"vimpluginloader\"])'' to your .vimrc.).\r\n\r\nGentoo users can use the following mercurial overlay: http:\/\/vimpluginloader.hg.sourceforge.net:8000\/hgroot\/vimpluginloader\/pluginloader-overlay.","first_name":"ZyX","6":"ZyX","last_name":" ","7":" ","releases":[{"0":"3325","vim_version":"7.3","1":"7.3","script_version":"0.7.8","2":"0.7.8","version_comment":"Fixed case when directory name contains wild characters","3":"Fixed case when directory name contains wild characters","package":"vim-fileutils-0.7.8.tar.gz","4":"vim-fileutils-0.7.8.tar.gz","src_id":"14553","5":"14553","creation_date":"1292626525","6":"1292626525"},{"0":"3325","vim_version":"7.3","1":"7.3","script_version":"0.7.7","2":"0.7.7","version_comment":"Fixed case when directory name contains wild characters","3":"Fixed case when directory name contains wild characters","package":"vim-fileutils-0.7.7.tar.gz","4":"vim-fileutils-0.7.7.tar.gz","src_id":"14552","5":"14552","creation_date":"1292626450","6":"1292626450"},{"0":"3325","vim_version":"7.3","1":"7.3","script_version":"0.7.6","2":"0.7.6","version_comment":"Fixed case when directory name contains newline on unix and vimscript function is used","3":"Fixed case when directory name contains newline on unix and vimscript function is used","package":"vim-fileutils-0.7.6.tar.gz","4":"vim-fileutils-0.7.6.tar.gz","src_id":"14547","5":"14547","creation_date":"1292605262","6":"1292605262"},{"0":"3325","vim_version":"7.3","1":"7.3","script_version":"0.7.3","2":"0.7.3","version_comment":"Fixed contents in documentation","3":"Fixed contents in documentation","package":"vim-fileutils-0.7.3.tar.gz","4":"vim-fileutils-0.7.3.tar.gz","src_id":"14388","5":"14388","creation_date":"1290856692","6":"1290856692"},{"0":"3325","vim_version":"7.2","1":"7.2","script_version":"0.7.2","2":"0.7.2","version_comment":"Made GetDirContents reliably treat empty string as '.'","3":"Made GetDirContents reliably treat empty string as '.'","package":"vim-fileutils-0.7.2.tar.gz","4":"vim-fileutils-0.7.2.tar.gz","src_id":"14335","5":"14335","creation_date":"1290337364","6":"1290337364"},{"0":"3325","vim_version":"7.3","1":"7.3","script_version":"0.7.1","2":"0.7.1","version_comment":"Fixed fileutils#GetDirContents('\/') and fileutils#GetDirContents('~')","3":"Fixed fileutils#GetDirContents('\/') and fileutils#GetDirContents('~')","package":"vim-fileutils-0.7.1.tar.gz","4":"vim-fileutils-0.7.1.tar.gz","src_id":"14330","5":"14330","creation_date":"1290282826","6":"1290282826"},{"0":"3325","vim_version":"7.3","1":"7.3","script_version":"0.7","2":"0.7","version_comment":"Made fileutils#GetDirContents return a list of files, not a list of full paths (using python's os.listdir if possible), added more OSs to possible OS list","3":"Made fileutils#GetDirContents return a list of files, not a list of full paths (using python's os.listdir if possible), added more OSs to possible OS list","package":"vim-fileutils-0.7.tar.gz","4":"vim-fileutils-0.7.tar.gz","src_id":"14315","5":"14315","creation_date":"1290255401","6":"1290255401"},{"0":"3325","vim_version":"7.0","1":"7.0","script_version":"0.6.1","2":"0.6.1","version_comment":"Added os#JoinPath function","3":"Added os#JoinPath function","package":"vim-fileutils-0.6.1.tar.gz","4":"vim-fileutils-0.6.1.tar.gz","src_id":"14261","5":"14261","creation_date":"1289758010","6":"1289758010"},{"0":"3325","vim_version":"7.0","1":"7.0","script_version":"0.5.1","2":"0.5.1","version_comment":"Added documentation","3":"Added documentation","package":"vim-fileutils-0.5.1.tar.gz","4":"vim-fileutils-0.5.1.tar.gz","src_id":"14258","5":"14258","creation_date":"1289750704","6":"1289750704"},{"0":"3325","vim_version":"7.0","1":"7.0","script_version":"0.5","2":"0.5","version_comment":"Initial upload","3":"Initial upload","package":"vim-fileutils-0.5.tar.gz","4":"vim-fileutils-0.5.tar.gz","src_id":"14257","5":"14257","creation_date":"1289746987","6":"1289746987"}]},"3324":{"script_id":"3324","0":"3324","script_name":"js-mask","1":"js-mask","script_type":"syntax","2":"syntax","summary":"More concise JavaScript using Vim's \"conceal\" feature","3":"More concise JavaScript using Vim's \"conceal\" feature","description":"js-mask: Give Your JavaScript A Beautiful Mask So It Wouldn't Look Ugly\r\n=======================================================================\r\n\r\nA Vim plugin that makes your javascripts look more concise. The original intention is to make anonymous function less verbose and easier to understand at a glance. Requires Vim at least version 7.3.\r\n\r\nBefore:\r\n    function Add(b, c) { return b + c; };\r\n    setTimeout(function() { console.log(\"wooot\") }, 10);\r\n\r\nAfter:\r\n    𝑓 Add(b, c) { return b + c; };\r\n    setTimeout(𝑓 { console.log(\"wooot\") }, 10);\r\n\r\nThat's it. Check https:\/\/github.com\/tyok\/js-mask\/blob\/master\/README.markdown for more docs.\r\n\r\nFeel free to suggest additions and improvements via https:\/\/github.com\/tyok\/js-mask\/issues. Or you can fork this from https:\/\/github.com\/tyok\/js-mask and add your own very personalized flavor.\r\n\r\nInspired by https:\/\/github.com\/ehamberg\/vim-cute-python which, in turn, is inspired by vimscript#3200.","4":"js-mask: Give Your JavaScript A Beautiful Mask So It Wouldn't Look Ugly\r\n=======================================================================\r\n\r\nA Vim plugin that makes your javascripts look more concise. The original intention is to make anonymous function less verbose and easier to understand at a glance. Requires Vim at least version 7.3.\r\n\r\nBefore:\r\n    function Add(b, c) { return b + c; };\r\n    setTimeout(function() { console.log(\"wooot\") }, 10);\r\n\r\nAfter:\r\n    𝑓 Add(b, c) { return b + c; };\r\n    setTimeout(𝑓 { console.log(\"wooot\") }, 10);\r\n\r\nThat's it. Check https:\/\/github.com\/tyok\/js-mask\/blob\/master\/README.markdown for more docs.\r\n\r\nFeel free to suggest additions and improvements via https:\/\/github.com\/tyok\/js-mask\/issues. Or you can fork this from https:\/\/github.com\/tyok\/js-mask and add your own very personalized flavor.\r\n\r\nInspired by https:\/\/github.com\/ehamberg\/vim-cute-python which, in turn, is inspired by vimscript#3200.","install_details":"Extract the tar.gz to ~\/.vim folder.","5":"Extract the tar.gz to ~\/.vim folder.","first_name":"Mohammad","6":"Mohammad","last_name":"Satrio","7":"Satrio","releases":[{"0":"3324","vim_version":"7.3","1":"7.3","script_version":"0.1","2":"0.1","version_comment":"Previous: \"function()\" wrap to \"𝑓 ()\"\r\nNow: \"function()\" wrap to just \"𝑓 \"","3":"Previous: \"function()\" wrap to \"𝑓 ()\"\r\nNow: \"function()\" wrap to just \"𝑓 \"","package":"js-mask-0.1.tar.gz","4":"js-mask-0.1.tar.gz","src_id":"14267","5":"14267","creation_date":"1289816815","6":"1289816815"},{"0":"3324","vim_version":"7.3","1":"7.3","script_version":"0.0","2":"0.0","version_comment":"Initial upload","3":"Initial upload","package":"js-mask.tar.gz","4":"js-mask.tar.gz","src_id":"14255","5":"14255","creation_date":"1289740756","6":"1289740756"}]},"3323":{"script_id":"3323","0":"3323","script_name":"lilypink","1":"lilypink","script_type":"color scheme","2":"color scheme","summary":"A dark color scheme, modification of mrpink","3":"A dark color scheme, modification of mrpink","description":"Some modification of mrpink (vimscript #2704). There's not many pink at all. The 'pink' in the name is from the original one.\r\n\r\nSupports 256-color terminal.\r\n\r\nscreenshots:\r\nhttp:\/\/img.ly\/2qtI vim script\r\nhttp:\/\/img.ly\/wYMu diff mode\r\n\r\nCheck it on Vivify:\r\nhttp:\/\/bytefluent.com\/vivify\/index.php?remote=www.vim.org%2Fscripts%2Fdownload_script.php%3Fsrc_id%3D20978","4":"Some modification of mrpink (vimscript #2704). There's not many pink at all. The 'pink' in the name is from the original one.\r\n\r\nSupports 256-color terminal.\r\n\r\nscreenshots:\r\nhttp:\/\/img.ly\/2qtI vim script\r\nhttp:\/\/img.ly\/wYMu diff mode\r\n\r\nCheck it on Vivify:\r\nhttp:\/\/bytefluent.com\/vivify\/index.php?remote=www.vim.org%2Fscripts%2Fdownload_script.php%3Fsrc_id%3D20978","install_details":"","5":"","first_name":"lilydjwg","6":"lilydjwg","last_name":" ","7":" ","releases":[{"0":"3323","vim_version":"7.0","1":"7.0","script_version":"1.5","2":"1.5","version_comment":"fix Visual highlighting with vim 9.1.61.","3":"fix Visual highlighting with vim 9.1.61.","package":"lilypink.vim","4":"lilypink.vim","src_id":"28601","5":"28601","creation_date":"1706676241","6":"1706676241"},{"0":"3323","vim_version":"7.0","1":"7.0","script_version":"1.3","2":"1.3","version_comment":"* added Diff* highlight","3":"* added Diff* highlight","package":"lilypink.vim","4":"lilypink.vim","src_id":"20978","5":"20978","creation_date":"1383039965","6":"1383039965"},{"0":"3323","vim_version":"7.0","1":"7.0","script_version":"1.2","2":"1.2","version_comment":"* support for ColorColumn group","3":"* support for ColorColumn group","package":"lilypink.vim","4":"lilypink.vim","src_id":"19905","5":"19905","creation_date":"1366703211","6":"1366703211"},{"0":"3323","vim_version":"7.0","1":"7.0","script_version":"1.1","2":"1.1","version_comment":"* support for newly added CursorLineNr group","3":"* support for newly added CursorLineNr group","package":"lilypink.vim","4":"lilypink.vim","src_id":"17647","5":"17647","creation_date":"1332522317","6":"1332522317"},{"0":"3323","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"lilypink.vim","4":"lilypink.vim","src_id":"14252","5":"14252","creation_date":"1289666091","6":"1289666091"}]},"3322":{"script_id":"3322","0":"3322","script_name":"FTPDEV","1":"FTPDEV","script_type":"ftplugin","2":"ftplugin","summary":"This is filetype plugin for vim scripts.","3":"This is filetype plugin for vim scripts.","description":"This file type plugin provides some additional tools which makes the life easier when writing plugins which are big projects with many functions, commands and maps across different files which share a common root directory. It provides commands for\r\n    - finding functions, commands, variable definitions and maps which name matches a pattern\r\n    - gD go to global declaration (an extremly fast way to move through code)\r\n    - gd  go to local declaration\r\n    - searching a function which wrap around the end of function\r\n    - Pgrep command which uses vimgrep to grep inside the plugin directory.\r\n    - Edit\/Split\/VSplit\/Diffsplit commands with a handy completion for file names (support ++opt and +cmd options of vim edit command)\r\n\r\nThere is a help file which explains all the details (:help ftpdev-news).\r\n\r\nYou can follow or develop this plugin on GitHub:\r\nhttps:\/\/github.com\/coot\/vim_ftpdev","4":"This file type plugin provides some additional tools which makes the life easier when writing plugins which are big projects with many functions, commands and maps across different files which share a common root directory. It provides commands for\r\n    - finding functions, commands, variable definitions and maps which name matches a pattern\r\n    - gD go to global declaration (an extremly fast way to move through code)\r\n    - gd  go to local declaration\r\n    - searching a function which wrap around the end of function\r\n    - Pgrep command which uses vimgrep to grep inside the plugin directory.\r\n    - Edit\/Split\/VSplit\/Diffsplit commands with a handy completion for file names (support ++opt and +cmd options of vim edit command)\r\n\r\nThere is a help file which explains all the details (:help ftpdev-news).\r\n\r\nYou can follow or develop this plugin on GitHub:\r\nhttps:\/\/github.com\/coot\/vim_ftpdev","install_details":"Open the vimball file and type ':so % <Enter>'","5":"Open the vimball file and type ':so % <Enter>'","first_name":"Marcin","6":"Marcin","last_name":"Szamotulski","7":"Szamotulski","releases":[{"0":"3322","vim_version":"7.3","1":"7.3","script_version":"6.2","2":"6.2","version_comment":"See :help ftpdev-news.","3":"See :help ftpdev-news.","package":"FTPDEV_6.2.vmb","4":"FTPDEV_6.2.vmb","src_id":"18901","5":"18901","creation_date":"1351328112","6":"1351328112"},{"0":"3322","vim_version":"7.3","1":"7.3","script_version":"6.1","2":"6.1","version_comment":"A fix for the 6 release.","3":"A fix for the 6 release.","package":"FTPDEV_6.1.vmb","4":"FTPDEV_6.1.vmb","src_id":"18731","5":"18731","creation_date":"1349112525","6":"1349112525"},{"0":"3322","vim_version":"7.3","1":"7.3","script_version":"6","2":"6","version_comment":"See \":help ftpdev-news\" for amendments and new features.","3":"See \":help ftpdev-news\" for amendments and new features.","package":"FTPDEV_6.vmb","4":"FTPDEV_6.vmb","src_id":"18724","5":"18724","creation_date":"1349076260","6":"1349076260"},{"0":"3322","vim_version":"7.3","1":"7.3","script_version":"5.5","2":"5.5","version_comment":"See :help ftpdev-news.","3":"See :help ftpdev-news.","package":"FTPDEV_5.5.vmb","4":"FTPDEV_5.5.vmb","src_id":"16567","5":"16567","creation_date":"1316856524","6":"1316856524"},{"0":"3322","vim_version":"7.3","1":"7.3","script_version":"5.4","2":"5.4","version_comment":":Edit command removed. FTPDEV sets path vim option, use vim :find command instead.","3":":Edit command removed. FTPDEV sets path vim option, use vim :find command instead.","package":"FTPDEV_5.4.vmb","4":"FTPDEV_5.4.vmb","src_id":"16354","5":"16354","creation_date":"1314312906","6":"1314312906"}]},"3321":{"script_id":"3321","0":"3321","script_name":"VimCoder.jar","1":"VimCoder.jar","script_type":"utility","2":"utility","summary":"The TopCoder Arena editor plugin with Vim integration.","3":"The TopCoder Arena editor plugin with Vim integration.","description":"The TopCoder Arena is a Java applet providing access to free programming\r\nchallenges and competitions.  The applet contains a built-in editor for\r\nsolving the algorithm problems, but coding in Vim is much easier.  This is\r\na plugin for the arena providing support for using Vim as your editor.  You\r\ncan learn about TopCoder at their site: http:\/\/www.topcoder.com\/tc\r\n\r\nSome features of this plugin:\r\n\r\n- Use Vim to edit your TC Arena problems.\r\n- Keeps track of your code files locally so you'll always have a copy.\r\n- Works with any language supported by TC.\r\n- Downloads and stores a copy of the problem statement with your code for\r\n    off-line viewing.\r\n- Support for templates (default templates provided only for C++ and Java).\r\n- Test-case \"drivers\" can be generated locally with the example test-case\r\n    data (currently C++ only).\r\n\r\nRequirements:\r\n\r\nYou need to have client\/server support compiled into Vim.  This is usually\r\nthe case.  You also need to have a recent Java runtime implementation in\r\norder to run the arena applet and editor plugin.\r\n\r\nYou can also use Vim's :make command to build the C++ test cases, but\r\nof course you'll need the make utility and a C++ compiler.\r\n\r\nA more detailed description of this plugin is available on the project page,\r\nalong with the source code:\r\nhttp:\/\/github.com\/chazmcgarvey\/vimcoder\r\n\r\nThis software is not endorsed by TopCoder and is provided as-is.\r\n","4":"The TopCoder Arena is a Java applet providing access to free programming\r\nchallenges and competitions.  The applet contains a built-in editor for\r\nsolving the algorithm problems, but coding in Vim is much easier.  This is\r\na plugin for the arena providing support for using Vim as your editor.  You\r\ncan learn about TopCoder at their site: http:\/\/www.topcoder.com\/tc\r\n\r\nSome features of this plugin:\r\n\r\n- Use Vim to edit your TC Arena problems.\r\n- Keeps track of your code files locally so you'll always have a copy.\r\n- Works with any language supported by TC.\r\n- Downloads and stores a copy of the problem statement with your code for\r\n    off-line viewing.\r\n- Support for templates (default templates provided only for C++ and Java).\r\n- Test-case \"drivers\" can be generated locally with the example test-case\r\n    data (currently C++ only).\r\n\r\nRequirements:\r\n\r\nYou need to have client\/server support compiled into Vim.  This is usually\r\nthe case.  You also need to have a recent Java runtime implementation in\r\norder to run the arena applet and editor plugin.\r\n\r\nYou can also use Vim's :make command to build the C++ test cases, but\r\nof course you'll need the make utility and a C++ compiler.\r\n\r\nA more detailed description of this plugin is available on the project page,\r\nalong with the source code:\r\nhttp:\/\/github.com\/chazmcgarvey\/vimcoder\r\n\r\nThis software is not endorsed by TopCoder and is provided as-is.\r\n","install_details":"1. Launch the TC Arena applet.\r\n2. Click the \"Options\" menu and select \"Editor\" to show the editor preferences.\r\n3. Click the \"Add\" button to bring up a new window for adding plugins.\r\n4. In the \"Name\" field, type \"Vim\" or whatever you want. This is used for identifying the plugin.\r\n5. In the \"EntryPoint\" field, type \"com.dogcows.VimCoder\" without the quotes.\r\n6. For the \"ClassPath\" field, click on \"Browse\" and locate the VimCoder jar file you downloaded.\r\n7. Click \"OK\" to close the plugin adding window.\r\n8. Click \"Save\" in the editor preferences window.\r\n\r\nYou should now be able select \"Vim\" (or whatever you entered in the first field) in the problem statement window to use Vim!","5":"1. Launch the TC Arena applet.\r\n2. Click the \"Options\" menu and select \"Editor\" to show the editor preferences.\r\n3. Click the \"Add\" button to bring up a new window for adding plugins.\r\n4. In the \"Name\" field, type \"Vim\" or whatever you want. This is used for identifying the plugin.\r\n5. In the \"EntryPoint\" field, type \"com.dogcows.VimCoder\" without the quotes.\r\n6. For the \"ClassPath\" field, click on \"Browse\" and locate the VimCoder jar file you downloaded.\r\n7. Click \"OK\" to close the plugin adding window.\r\n8. Click \"Save\" in the editor preferences window.\r\n\r\nYou should now be able select \"Vim\" (or whatever you entered in the first field) in the problem statement window to use Vim!","first_name":"Charles","6":"Charles","last_name":"McGarvey","7":"McGarvey","releases":[{"0":"3321","vim_version":"7.0","1":"7.0","script_version":"0.3.6","2":"0.3.6","version_comment":"* Bugfix: Do not insert C++-style comments since that doesn't work for some languages (e.g. Python).\r\n* Improved documentation","3":"* Bugfix: Do not insert C++-style comments since that doesn't work for some languages (e.g. Python).\r\n* Improved documentation","package":"VimCoder-0.3.6.jar","4":"VimCoder-0.3.6.jar","src_id":"22983","5":"22983","creation_date":"1425748084","6":"1425748084"},{"0":"3321","vim_version":"7.0","1":"7.0","script_version":"0.3.5","2":"0.3.5","version_comment":"New features:\r\n* The default C++ driver now generates TAP (Test Anything Protocol) so that a compatible test harness may be used.\r\n* Added an optional alternative directory structure based on contest name and point values to make browsing easier.\r\n\r\nOther changes:\r\n* Better Windows support for default C++ Makefile and driver program.\r\n* Improved documentation and other small tweaks.","3":"New features:\r\n* The default C++ driver now generates TAP (Test Anything Protocol) so that a compatible test harness may be used.\r\n* Added an optional alternative directory structure based on contest name and point values to make browsing easier.\r\n\r\nOther changes:\r\n* Better Windows support for default C++ Makefile and driver program.\r\n* Improved documentation and other small tweaks.","package":"VimCoder-0.3.5.jar","4":"VimCoder-0.3.5.jar","src_id":"19786","5":"19786","creation_date":"1365467087","6":"1365467087"},{"0":"3321","vim_version":"7.0","1":"7.0","script_version":"0.3.4","2":"0.3.4","version_comment":"Bug fixes:\r\n\r\n* Prevent a rare compile error in the C++ driver.\r\n* Works with JRE 1.6 (thanks Sam Lidder and Aaron Michelony).\r\n\r\nOther changes:\r\n\r\n* Build the jar with jar(1) instead of zip(1). That makes more sense...\r\n* Cleaned up the documentation somewhat. ","3":"Bug fixes:\r\n\r\n* Prevent a rare compile error in the C++ driver.\r\n* Works with JRE 1.6 (thanks Sam Lidder and Aaron Michelony).\r\n\r\nOther changes:\r\n\r\n* Build the jar with jar(1) instead of zip(1). That makes more sense...\r\n* Cleaned up the documentation somewhat. ","package":"VimCoder-0.3.4.jar","4":"VimCoder-0.3.4.jar","src_id":"19428","5":"19428","creation_date":"1359094521","6":"1359094521"},{"0":"3321","vim_version":"7.0","1":"7.0","script_version":"0.3.3","2":"0.3.3","version_comment":"This version includes bug-fixes for the C++ driver:\r\n* Test floating point values with TopCoder's allowed error.\r\n* Avoid an infinite loop with recent versions of libstdc++.\r\n\r\nThanks to Sam Lidder for the patches.","3":"This version includes bug-fixes for the C++ driver:\r\n* Test floating point values with TopCoder's allowed error.\r\n* Avoid an infinite loop with recent versions of libstdc++.\r\n\r\nThanks to Sam Lidder for the patches.","package":"VimCoder-0.3.3.jar","4":"VimCoder-0.3.3.jar","src_id":"18464","5":"18464","creation_date":"1345740673","6":"1345740673"},{"0":"3321","vim_version":"7.0","1":"7.0","script_version":"0.3.2","2":"0.3.2","version_comment":"Bugfixes:\r\n * Makefile changes are no longer clobbered when re-opening a problem (thanks jiakai for reporting).\r\n * multi-word types (i.e. unsigned long in C++) are no longer smooshed together.\r\n * Waiting on the Vim server process increased to 2.5 seconds in case Vim loads slowly (i.e. from NFS).\r\nOther changes:\r\n * Default C++ Makefile template now uses the -ggdb g++ flag for more expressive debugging information.","3":"Bugfixes:\r\n * Makefile changes are no longer clobbered when re-opening a problem (thanks jiakai for reporting).\r\n * multi-word types (i.e. unsigned long in C++) are no longer smooshed together.\r\n * Waiting on the Vim server process increased to 2.5 seconds in case Vim loads slowly (i.e. from NFS).\r\nOther changes:\r\n * Default C++ Makefile template now uses the -ggdb g++ flag for more expressive debugging information.","package":"VimCoder-0.3.2.jar","4":"VimCoder-0.3.2.jar","src_id":"16075","5":"16075","creation_date":"1310594488","6":"1310594488"},{"0":"3321","vim_version":"7.0","1":"7.0","script_version":"0.3.1","2":"0.3.1","version_comment":" * Now uses correct line-endings by default on Windows.\r\n * Other cosmetic bugfixes.","3":" * Now uses correct line-endings by default on Windows.\r\n * Other cosmetic bugfixes.","package":"VimCoder-0.3.1.jar","4":"VimCoder-0.3.1.jar","src_id":"14522","5":"14522","creation_date":"1292436767","6":"1292436767"},{"0":"3321","vim_version":"7.0","1":"7.0","script_version":"0.3","2":"0.3","version_comment":"\r\nChanges:\r\n\r\n * User-customizable templates (add them to the \"storage\" directory).\r\n * Default Vim command for Windows now C:\\WINDOWS\\gvim.bat; if you don't have this executable, you may need to tell VimCoder how to invoke Vim.\r\n * Documentation now available: https:\/\/www.dogcows.com\/vimcoder\/wiki\/Manual\r\n","3":"\r\nChanges:\r\n\r\n * User-customizable templates (add them to the \"storage\" directory).\r\n * Default Vim command for Windows now C:\\WINDOWS\\gvim.bat; if you don't have this executable, you may need to tell VimCoder how to invoke Vim.\r\n * Documentation now available: https:\/\/www.dogcows.com\/vimcoder\/wiki\/Manual\r\n","package":"VimCoder-0.3.jar","4":"VimCoder-0.3.jar","src_id":"14283","5":"14283","creation_date":"1289976770","6":"1289976770"},{"0":"3321","vim_version":"7.0","1":"7.0","script_version":"0.2","2":"0.2","version_comment":"Initial upload","3":"Initial upload","package":"VimCoder-0.2.jar","4":"VimCoder-0.2.jar","src_id":"14248","5":"14248","creation_date":"1289638984","6":"1289638984"}]},"3320":{"script_id":"3320","0":"3320","script_name":"vim-addon-xdebug","1":"vim-addon-xdebug","script_type":"utility","2":"utility","summary":"xdebug support for VIm using vim-addon-async","3":"xdebug support for VIm using vim-addon-async","description":"This plugin wants to support sane PHP debugging for Vim.\r\n\r\nFeatures which work:\r\n- stack\r\n- step into, over, out, run\r\n- eval PHP code (inspect vars)\r\n- show current line which will be executed next\r\n\r\nAdding the remaining features should be easy now.","4":"This plugin wants to support sane PHP debugging for Vim.\r\n\r\nFeatures which work:\r\n- stack\r\n- step into, over, out, run\r\n- eval PHP code (inspect vars)\r\n- show current line which will be executed next\r\n\r\nAdding the remaining features should be easy now.","install_details":"I recommend using vim-addon-manager because it has some dependencies\r\n\r\nIn any case you should get the latest version from http:\/\/github.com\/MarcWeber\/vim-addon-xdebug\r\n\r\ntested on linux only.","5":"I recommend using vim-addon-manager because it has some dependencies\r\n\r\nIn any case you should get the latest version from http:\/\/github.com\/MarcWeber\/vim-addon-xdebug\r\n\r\ntested on linux only.","first_name":"Marc","6":"Marc","last_name":"Weber","7":"Weber","releases":[{"0":"3320","vim_version":"7.0","1":"7.0","script_version":"0.2","2":"0.2","version_comment":"some improvements (optional stop first line and more)","3":"some improvements (optional stop first line and more)","package":"vim-addon-xdebug-0.2.zip","4":"vim-addon-xdebug-0.2.zip","src_id":"14299","5":"14299","creation_date":"1290088246","6":"1290088246"},{"0":"3320","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"adding support for watching vars and evaluating PHP code","3":"adding support for watching vars and evaluating PHP code","package":"vim-addon-xdebug-0.1.zip","4":"vim-addon-xdebug-0.1.zip","src_id":"14262","5":"14262","creation_date":"1289770675","6":"1289770675"},{"0":"3320","vim_version":"7.0","1":"7.0","script_version":"0.0","2":"0.0","version_comment":"Initial upload","3":"Initial upload","package":"initial.zip","4":"initial.zip","src_id":"14246","5":"14246","creation_date":"1289619967","6":"1289619967"}]},"3319":{"script_id":"3319","0":"3319","script_name":"unite-font","1":"unite-font","script_type":"utility","2":"utility","summary":"A Unite.vim plugin for changing your font.","3":"A Unite.vim plugin for changing your font.","description":"A Unite.vim plugin for changing your font. See details in the following pages.\n\n* http:\/\/github.com\/ujihisa\/unite-font (development)\n* https:\/\/github.com\/shougo\/unite.vim (unite core)\n","4":"A Unite.vim plugin for changing your font. See details in the following pages.\n\n* http:\/\/github.com\/ujihisa\/unite-font (development)\n* https:\/\/github.com\/shougo\/unite.vim (unite core)\n","install_details":"After you install Shougo's unite.vim, unarchive the zip file into a directory that is under &rtp of your Vim, including ~\/.vim dir.\n","5":"After you install Shougo's unite.vim, unarchive the zip file into a directory that is under &rtp of your Vim, including ~\/.vim dir.\n","first_name":"ujihisa","6":"ujihisa","last_name":".","7":".","releases":[{"0":"3319","vim_version":"7.3","1":"7.3","script_version":"1.4","2":"1.4","version_comment":"Supports unite's auto-preview. Thanks Zhao Cai.","3":"Supports unite's auto-preview. Thanks Zhao Cai.","package":"unite-font-1.4.zip","4":"unite-font-1.4.zip","src_id":"19797","5":"19797","creation_date":"1365630311","6":"1365630311"},{"0":"3319","vim_version":"7.3","1":"7.3","script_version":"1.3","2":"1.3","version_comment":"Supports more fonts on Windows, with using C external program. Thanks anekos.","3":"Supports more fonts on Windows, with using C external program. Thanks anekos.","package":"unite-font-1.3.zip","4":"unite-font-1.3.zip","src_id":"14502","5":"14502","creation_date":"1292301424","6":"1292301424"},{"0":"3319","vim_version":"7.3","1":"7.3","script_version":"1.2","2":"1.2","version_comment":"Adding missing font dirs for Mac OS X","3":"Adding missing font dirs for Mac OS X","package":"unite-font-1.2.zip","4":"unite-font-1.2.zip","src_id":"14377","5":"14377","creation_date":"1290738434","6":"1290738434"},{"0":"3319","vim_version":"7.3","1":"7.3","script_version":"1.1","2":"1.1","version_comment":"Supports gtk gvim like Windows version or Linux version besides Mac OS X. Thanks thinca, mattn and shougo.","3":"Supports gtk gvim like Windows version or Linux version besides Mac OS X. Thanks thinca, mattn and shougo.","package":"unite-font-1.1.zip","4":"unite-font-1.1.zip","src_id":"14277","5":"14277","creation_date":"1289956671","6":"1289956671"},{"0":"3319","vim_version":"7.3","1":"7.3","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"unite-font-1.0.zip","4":"unite-font-1.0.zip","src_id":"14239","5":"14239","creation_date":"1289500478","6":"1289500478"}]},"3318":{"script_id":"3318","0":"3318","script_name":"unite-colorscheme","1":"unite-colorscheme","script_type":"utility","2":"utility","summary":"A Unite.vim plugin for changing your colorscheme.","3":"A Unite.vim plugin for changing your colorscheme.","description":"A Unite.vim plugin for changing your colorscheme. See details in the following pages. \n\n* http:\/\/github.com\/ujihisa\/unite-colorscheme (development) \n* http:\/\/ujihisa.blogspot.com\/2010\/11\/how-to-make-unite-plugin.html (for version 1.0)\n","4":"A Unite.vim plugin for changing your colorscheme. See details in the following pages. \n\n* http:\/\/github.com\/ujihisa\/unite-colorscheme (development) \n* http:\/\/ujihisa.blogspot.com\/2010\/11\/how-to-make-unite-plugin.html (for version 1.0)\n","install_details":"After you install Shougo's unite.vim, unarchive the zip file into a directory that is under &rtp of your Vim, including ~\/.vim dir.\n","5":"After you install Shougo's unite.vim, unarchive the zip file into a directory that is under &rtp of your Vim, including ~\/.vim dir.\n","first_name":"ujihisa","6":"ujihisa","last_name":".","7":".","releases":[{"0":"3318","vim_version":"7.3","1":"7.3","script_version":"2.0","2":"2.0","version_comment":"* Added g:unite_colorscheme_blacklist","3":"* Added g:unite_colorscheme_blacklist","package":"unite-colorscheme-2.0.zip","4":"unite-colorscheme-2.0.zip","src_id":"24420","5":"24420","creation_date":"1470003080","6":"1470003080"},{"0":"3318","vim_version":"7.3","1":"7.3","script_version":"1.3","2":"1.3","version_comment":"* Preview\n","3":"* Preview\n","package":"unite-colorscheme-1.3.zip","4":"unite-colorscheme-1.3.zip","src_id":"15119","5":"15119","creation_date":"1298689118","6":"1298689118"},{"0":"3318","vim_version":"7.3","1":"7.3","script_version":"1.2","2":"1.2","version_comment":"* Introducing g:unite_colorscheme_command to be able to custom colorscheme command\n","3":"* Introducing g:unite_colorscheme_command to be able to custom colorscheme command\n","package":"unite-colorscheme-1.2.zip","4":"unite-colorscheme-1.2.zip","src_id":"14470","5":"14470","creation_date":"1292035090","6":"1292035090"},{"0":"3318","vim_version":"7.3","1":"7.3","script_version":"1.1","2":"1.1","version_comment":"* Abandons kinds\/colorscheme and uses Unite's kinds\/command which is introduced for this plugin\n","3":"* Abandons kinds\/colorscheme and uses Unite's kinds\/command which is introduced for this plugin\n","package":"unite-colorscheme-1.1.zip","4":"unite-colorscheme-1.1.zip","src_id":"14229","5":"14229","creation_date":"1289456344","6":"1289456344"},{"0":"3318","vim_version":"7.3","1":"7.3","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"unite-colorscheme-1.0.zip","4":"unite-colorscheme-1.0.zip","src_id":"14228","5":"14228","creation_date":"1289454986","6":"1289454986"}]},"3317":{"script_id":"3317","0":"3317","script_name":"vim-addon-signs","1":"vim-addon-signs","script_type":"utility","2":"utility","summary":"work around the bad API of Vim setting, unsetting signs (markers at the left)","3":"work around the bad API of Vim setting, unsetting signs (markers at the left)","description":"you push a whole list of signs. The plugin will take care about applying incremental updates. An example is provided which can be used to highlight error lines of quickfix or error location list.","4":"you push a whole list of signs. The plugin will take care about applying incremental updates. An example is provided which can be used to highlight error lines of quickfix or error location list.","install_details":"I recommend using vim-addon-manager. This plugin has no dependencies though.","5":"I recommend using vim-addon-manager. This plugin has no dependencies though.","first_name":"Marc","6":"Marc","last_name":"Weber","7":"Weber","releases":[{"0":"3317","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"fix -bar","3":"fix -bar","package":"vim-addon-signs-0.1.zip","4":"vim-addon-signs-0.1.zip","src_id":"14222","5":"14222","creation_date":"1289373560","6":"1289373560"},{"0":"3317","vim_version":"7.0","1":"7.0","script_version":"0.0","2":"0.0","version_comment":"Initial upload","3":"Initial upload","package":"initial.zip","4":"initial.zip","src_id":"14221","5":"14221","creation_date":"1289372488","6":"1289372488"}]},"3316":{"script_id":"3316","0":"3316","script_name":"tohtml_wincp","1":"tohtml_wincp","script_type":"utility","2":"utility","summary":"Autodetect installed Windows encodings for :TOhtml","3":"Autodetect installed Windows encodings for :TOhtml","description":"This plugin will automatically add any encodings which you have installed on\r\nyour Microsoft Windows system to the g:html_encoding_override and\r\ng:html_charset_override options of the :TOhtml plugin which is distributed\r\nas part of the official Vim runtime.\r\n\r\nThis plugin has no mappings or user-defined commands. It sets up an :autocmd\r\nthat will be invoked the first time that you call the :TOhtml command or\r\ndirectly :source the 2html.vim script.\r\n\r\nBecause the plugin does not trigger until just before the first :TOhtml\r\nconversion, you will not see any changes to the encoding detection options\r\nright away. This is normal, do not be alarmed!","4":"This plugin will automatically add any encodings which you have installed on\r\nyour Microsoft Windows system to the g:html_encoding_override and\r\ng:html_charset_override options of the :TOhtml plugin which is distributed\r\nas part of the official Vim runtime.\r\n\r\nThis plugin has no mappings or user-defined commands. It sets up an :autocmd\r\nthat will be invoked the first time that you call the :TOhtml command or\r\ndirectly :source the 2html.vim script.\r\n\r\nBecause the plugin does not trigger until just before the first :TOhtml\r\nconversion, you will not see any changes to the encoding detection options\r\nright away. This is normal, do not be alarmed!","install_details":"                                                     tohtml_wincp-requirements\r\nThis plugin requires:\r\n        * Vim 7.0 or higher\r\n        * TOhtml version vim7.3_v7 or higher\r\n        * Windows NT\/2000 or later (i.e. something that uses a System32\r\n          directory)\r\n\r\n                                                          tohtml_wincp-install\r\nTo install, there are only three files you need. This :help file, a\r\ntohtml_wincp.vim file to place in your after-directory, and another\r\ntohtml_wincp.vim file to place in your autoload directory.\r\n\r\nThe easiest way to install is to use Pathogen\r\n(http:\/\/www.vim.org\/scripts\/script.php?script_id=2332) and place the whole\r\ncontents of the zip file into $HOME\/vimfiles\/bundle. Then run the :Helptags\r\ncommand provided with Pathogen.\r\n\r\nFor manual installation, simply place the files where they need to go within\r\nyour runtime, as follows:\r\n\t* $HOME\/vimfiles\/doc\/tohtml_wincp.txt\r\n\t* $HOME\/vimfiles\/plugin\/tohtml_wincp.vim\r\n\t* $HOME\/vimfiles\/autoload\/tohtml_wincp.vim\r\n\r\nThen, run \":helptags $HOME\/vimfiles\/doc\" and installation is complete.","5":"                                                     tohtml_wincp-requirements\r\nThis plugin requires:\r\n        * Vim 7.0 or higher\r\n        * TOhtml version vim7.3_v7 or higher\r\n        * Windows NT\/2000 or later (i.e. something that uses a System32\r\n          directory)\r\n\r\n                                                          tohtml_wincp-install\r\nTo install, there are only three files you need. This :help file, a\r\ntohtml_wincp.vim file to place in your after-directory, and another\r\ntohtml_wincp.vim file to place in your autoload directory.\r\n\r\nThe easiest way to install is to use Pathogen\r\n(http:\/\/www.vim.org\/scripts\/script.php?script_id=2332) and place the whole\r\ncontents of the zip file into $HOME\/vimfiles\/bundle. Then run the :Helptags\r\ncommand provided with Pathogen.\r\n\r\nFor manual installation, simply place the files where they need to go within\r\nyour runtime, as follows:\r\n\t* $HOME\/vimfiles\/doc\/tohtml_wincp.txt\r\n\t* $HOME\/vimfiles\/plugin\/tohtml_wincp.vim\r\n\t* $HOME\/vimfiles\/autoload\/tohtml_wincp.vim\r\n\r\nThen, run \":helptags $HOME\/vimfiles\/doc\" and installation is complete.","first_name":"Ben","6":"Ben","last_name":"Fritz","7":"Fritz","releases":[{"0":"3316","vim_version":"7.0","1":"7.0","script_version":"4","2":"4","version_comment":"Get rid of after\/plugin hack allowing use of Pathogen to install; improve TOhtml version detection","3":"Get rid of after\/plugin hack allowing use of Pathogen to install; improve TOhtml version detection","package":"tohtml_wincp-v4.zip","4":"tohtml_wincp-v4.zip","src_id":"19787","5":"19787","creation_date":"1365478335","6":"1365478335"},{"0":"3316","vim_version":"7.0","1":"7.0","script_version":"3","2":"3","version_comment":"Fix detection of :TOhtml version to work when v7.4 or 8.0 comes around.","3":"Fix detection of :TOhtml version to work when v7.4 or 8.0 comes around.","package":"tohtml_wincp-v3.zip","4":"tohtml_wincp-v3.zip","src_id":"16871","5":"16871","creation_date":"1321377297","6":"1321377297"},{"0":"3316","vim_version":"7.0","1":"7.0","script_version":"2","2":"2","version_comment":"Fix bug in load guards and unsupported version msg, remove debug msg","3":"Fix bug in load guards and unsupported version msg, remove debug msg","package":"tohtml_wincp-v2.zip","4":"tohtml_wincp-v2.zip","src_id":"14434","5":"14434","creation_date":"1291474743","6":"1291474743"},{"0":"3316","vim_version":"7.0","1":"7.0","script_version":"1","2":"1","version_comment":"Initial upload","3":"Initial upload","package":"tohtml_wincp-v1.zip","4":"tohtml_wincp-v1.zip","src_id":"14219","5":"14219","creation_date":"1289363364","6":"1289363364"}]},"3315":{"script_id":"3315","0":"3315","script_name":"vim-addon-json-encoding","1":"vim-addon-json-encoding","script_type":"utility","2":"utility","summary":"make Vim read and write JSON objects","3":"make Vim read and write JSON objects","description":"I think JSON is the preferred way to make Vim communicate with external tools because it can speak it (almost) natively using eval \/ string.\r\n\r\nstring serialization encodes strings using \\' instead of \\\". This the encoding has been rewritten using VImL\r\n\r\ntrue, false, null can\\'t be represented in VimL. Thus they are encoded by unique function values (See code)\r\n\r\nThis plugin is used by the ensime plugin (and similar code is used by the scion plugin).\r\nIn both cases Vim sends small commands and receives completion data or the like.\r\nBecause native eval is used for reading JSON data you can\\'t be faster.\r\n","4":"I think JSON is the preferred way to make Vim communicate with external tools because it can speak it (almost) natively using eval \/ string.\r\n\r\nstring serialization encodes strings using \\' instead of \\\". This the encoding has been rewritten using VImL\r\n\r\ntrue, false, null can\\'t be represented in VimL. Thus they are encoded by unique function values (See code)\r\n\r\nThis plugin is used by the ensime plugin (and similar code is used by the scion plugin).\r\nIn both cases Vim sends small commands and receives completion data or the like.\r\nBecause native eval is used for reading JSON data you can\\'t be faster.\r\n","install_details":"You can install this plugin using vim-addon-manager (recommended). It does not have any dependencies.","5":"You can install this plugin using vim-addon-manager (recommended). It does not have any dependencies.","first_name":"Marc","6":"Marc","last_name":"Weber","7":"Weber","releases":[{"0":"3315","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"initial.zip","4":"initial.zip","src_id":"14218","5":"14218","creation_date":"1289358720","6":"1289358720"}]},"3314":{"script_id":"3314","0":"3314","script_name":"maxivim","1":"maxivim","script_type":"utility","2":"utility","summary":"Maximize\/unmaximize gvim without window manager","3":"Maximize\/unmaximize gvim without window manager","description":"In some environments (for example, KDE 3), gvim is unable to properly maximize or unmaximize itself, due to interactions with window managers or other issues.\r\n\r\nMaxivim bypasses window managers, allowing you to maximize gvim vertically, horizontally, or both, and restore it from having maximized it.\r\n\r\nMaxivim also allows you to set the initial size of your gvim windows by setting environment variables ($GVIM_LINES and $GVIM_COLUMNS).\r\n\r\n(This used to work with Vim 6, but I've only recently tested on Vim 7).","4":"In some environments (for example, KDE 3), gvim is unable to properly maximize or unmaximize itself, due to interactions with window managers or other issues.\r\n\r\nMaxivim bypasses window managers, allowing you to maximize gvim vertically, horizontally, or both, and restore it from having maximized it.\r\n\r\nMaxivim also allows you to set the initial size of your gvim windows by setting environment variables ($GVIM_LINES and $GVIM_COLUMNS).\r\n\r\n(This used to work with Vim 6, but I've only recently tested on Vim 7).","install_details":"Put maxivim.vim into your vim plugins directory.\r\n\r\nIf desired, add one or more of the following to your ~\/.gvimrc:\r\n\r\nif has(\"gui_running\")\r\n        \" Enable keybindings for [F5], [F6], [F7], and [Shift+F6].\r\n        let g:maxivim_should_map_keys = 1\r\n        \" Ask maxivim to resize your gvim windows to the default size.\r\n        let g:maxivim_should_resize_to_default = 1\r\n        \" These override the values of $GVIM_COLUMNS and $GVIM_LINES. \r\n        let g:maxivim_default_columns = 100\r\n        let g:maxivim_default_lines = 50\r\nendif\r\n","5":"Put maxivim.vim into your vim plugins directory.\r\n\r\nIf desired, add one or more of the following to your ~\/.gvimrc:\r\n\r\nif has(\"gui_running\")\r\n        \" Enable keybindings for [F5], [F6], [F7], and [Shift+F6].\r\n        let g:maxivim_should_map_keys = 1\r\n        \" Ask maxivim to resize your gvim windows to the default size.\r\n        let g:maxivim_should_resize_to_default = 1\r\n        \" These override the values of $GVIM_COLUMNS and $GVIM_LINES. \r\n        let g:maxivim_default_columns = 100\r\n        let g:maxivim_default_lines = 50\r\nendif\r\n","first_name":"Jim","6":"Jim","last_name":"Knoble","7":"Knoble","releases":[{"0":"3314","vim_version":"6.0","1":"6.0","script_version":"0.101001","2":"0.101001","version_comment":"Initial upload","3":"Initial upload","package":"maxivim.vim","4":"maxivim.vim","src_id":"14217","5":"14217","creation_date":"1289345948","6":"1289345948"}]},"3313":{"script_id":"3313","0":"3313","script_name":"Mizore","1":"Mizore","script_type":"color scheme","2":"color scheme","summary":"A dark color scheme in cyan, blue and violet tones.","3":"A dark color scheme in cyan, blue and violet tones.","description":"A dark color scheme in cyan, blue and violet tones.\r\nAn example: http:\/\/luinnar.narod.ru\/vim\/Mizore.png\r\nSuggestions are welcome here: https:\/\/github.com\/lxmzhv\/vim\/tree\/master\/colors","4":"A dark color scheme in cyan, blue and violet tones.\r\nAn example: http:\/\/luinnar.narod.ru\/vim\/Mizore.png\r\nSuggestions are welcome here: https:\/\/github.com\/lxmzhv\/vim\/tree\/master\/colors","install_details":"1. Copy mizore.vim to ~\/.vim\/colors\/\r\n2a. Perform \":colors mizore\" in vim to test the scheme or\r\n2b. Add a line \"colors mizore\" to ~\/.vimrc","5":"1. Copy mizore.vim to ~\/.vim\/colors\/\r\n2a. Perform \":colors mizore\" in vim to test the scheme or\r\n2b. Add a line \"colors mizore\" to ~\/.vimrc","first_name":"Luinnar","6":"Luinnar","last_name":".","7":".","releases":[{"0":"3313","vim_version":"7.0","1":"7.0","script_version":"1.2","2":"1.2","version_comment":"Fixed diff mode colors.","3":"Fixed diff mode colors.","package":"mizore.vim","4":"mizore.vim","src_id":"14233","5":"14233","creation_date":"1289470841","6":"1289470841"},{"0":"3313","vim_version":"7.0","1":"7.0","script_version":"1.1","2":"1.1","version_comment":"The color of comments was changed.","3":"The color of comments was changed.","package":"mizore.vim","4":"mizore.vim","src_id":"14212","5":"14212","creation_date":"1289310288","6":"1289310288"},{"0":"3313","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"mizore.vim","4":"mizore.vim","src_id":"14211","5":"14211","creation_date":"1289308824","6":"1289308824"}]},"3312":{"script_id":"3312","0":"3312","script_name":"operator-html-escape","1":"operator-html-escape","script_type":"utility","2":"utility","summary":"operator-html-escape provides operator to escape HTML entities.","3":"operator-html-escape provides operator to escape HTML entities.","description":"Repository: http:\/\/github.com\/tyru\/operator-html-escape.vim\r\n\r\n\r\n|operator-html-escape| provides |operator| to escape HTML entities.\r\n>\r\n\tnmap <c-h>\u00c2\u00a0<Plug>(operator-html-escape)\r\n\tnmap <c-u>\u00c2\u00a0<Plug>(operator-html-unescape)\r\n\r\nThis has similar feature with this wiki page:\r\n\thttp:\/\/vim.wikia.com\/wiki\/HTML_entities\r\n\r\nBut the fact is that it is certainly NOT the same\r\nbecause this is operator.\r\nso this can work with |text-objects|.\r\nYou can also enhance |text-objects| by |textobj-user|.\r\n\r\nRequirements:\r\n- Vim 7.2 or later\r\n- |operator-user| 0.0.5 or later (vimscript#2692)","4":"Repository: http:\/\/github.com\/tyru\/operator-html-escape.vim\r\n\r\n\r\n|operator-html-escape| provides |operator| to escape HTML entities.\r\n>\r\n\tnmap <c-h>\u00c2\u00a0<Plug>(operator-html-escape)\r\n\tnmap <c-u>\u00c2\u00a0<Plug>(operator-html-unescape)\r\n\r\nThis has similar feature with this wiki page:\r\n\thttp:\/\/vim.wikia.com\/wiki\/HTML_entities\r\n\r\nBut the fact is that it is certainly NOT the same\r\nbecause this is operator.\r\nso this can work with |text-objects|.\r\nYou can also enhance |text-objects| by |textobj-user|.\r\n\r\nRequirements:\r\n- Vim 7.2 or later\r\n- |operator-user| 0.0.5 or later (vimscript#2692)","install_details":"","5":"","first_name":"tyru","6":"tyru","last_name":" ","7":" ","releases":[{"0":"3312","vim_version":"7.0","1":"7.0","script_version":"0.0.1","2":"0.0.1","version_comment":"fix\u00c2\u00a0bug:\u00c2\u00a0operators\u00c2\u00a0work\u00c2\u00a0in\u00c2\u00a0only\u00c2\u00a0linewise. support\u00c2\u00a0characterwise\u00c2\u00a0and\u00c2\u00a0blockwise.","3":"fix\u00c2\u00a0bug:\u00c2\u00a0operators\u00c2\u00a0work\u00c2\u00a0in\u00c2\u00a0only\u00c2\u00a0linewise. support\u00c2\u00a0characterwise\u00c2\u00a0and\u00c2\u00a0blockwise.","package":"operator-html-escape.zip","4":"operator-html-escape.zip","src_id":"14387","5":"14387","creation_date":"1290834927","6":"1290834927"},{"0":"3312","vim_version":"7.2","1":"7.2","script_version":"0.0.0","2":"0.0.0","version_comment":"Initial upload","3":"Initial upload","package":"operator-html-escape.zip","4":"operator-html-escape.zip","src_id":"14201","5":"14201","creation_date":"1289121408","6":"1289121408"}]},"3311":{"script_id":"3311","0":"3311","script_name":"savemap.vim","1":"savemap.vim","script_type":"utility","2":"utility","summary":"savemap is the library to save current mapping(s)\/abbreviation(s)","3":"savemap is the library to save current mapping(s)\/abbreviation(s)","description":"Repository: http:\/\/github.com\/tyru\/savemap.vim\r\n\r\nRequirements:\r\n- Vim 7.3 or higher\r\n\r\n\r\n|savemap| is the library to provide a way\r\nto restore current mapping(s)\/abbreviation(s) \"perfectly\".\r\n\r\n...But remember, you can always use |:map-<buffer>| for \"simple\" case.\r\n\r\n>\r\n    nmap foo blahblahblah\r\n\r\n    let foo_nmap = savemap#save_map('n', 'foo')\r\n    if empty(foo_nmap)\r\n        echoerr 'your vim version is lower than 7.3.032!'\r\n    endif\r\n\r\n    nmap foo bar\r\n    \" Execute 'bar'.\r\n    normal foo\r\n\r\n    call foo_nmap.restore()\r\n    \" Execute 'blahblahblah'.\r\n    normal foo\r\n\r\n\r\nOmit 2nd arg of |savemap#save_map()| to save all mappings of the mode.\r\n>\r\n    let normal_mappings = savemap#save_map('n')\r\n    if empty(normal_mappings)\r\n        echoerr 'your vim version is lower than 7.3.032!'\r\n    endif\r\n\r\n   \" Clear!\r\n    nmapclear\r\n\r\n    \" Map own mappings.\r\n    nnoremap a b\r\n    nnoremap c d\r\n    ...\r\n\r\n    try\r\n        ... \" Do it\r\n    finally\r\n        call normal_mappings.restore()\r\n    endtry","4":"Repository: http:\/\/github.com\/tyru\/savemap.vim\r\n\r\nRequirements:\r\n- Vim 7.3 or higher\r\n\r\n\r\n|savemap| is the library to provide a way\r\nto restore current mapping(s)\/abbreviation(s) \"perfectly\".\r\n\r\n...But remember, you can always use |:map-<buffer>| for \"simple\" case.\r\n\r\n>\r\n    nmap foo blahblahblah\r\n\r\n    let foo_nmap = savemap#save_map('n', 'foo')\r\n    if empty(foo_nmap)\r\n        echoerr 'your vim version is lower than 7.3.032!'\r\n    endif\r\n\r\n    nmap foo bar\r\n    \" Execute 'bar'.\r\n    normal foo\r\n\r\n    call foo_nmap.restore()\r\n    \" Execute 'blahblahblah'.\r\n    normal foo\r\n\r\n\r\nOmit 2nd arg of |savemap#save_map()| to save all mappings of the mode.\r\n>\r\n    let normal_mappings = savemap#save_map('n')\r\n    if empty(normal_mappings)\r\n        echoerr 'your vim version is lower than 7.3.032!'\r\n    endif\r\n\r\n   \" Clear!\r\n    nmapclear\r\n\r\n    \" Map own mappings.\r\n    nnoremap a b\r\n    nnoremap c d\r\n    ...\r\n\r\n    try\r\n        ... \" Do it\r\n    finally\r\n        call normal_mappings.restore()\r\n    endtry","install_details":"","5":"","first_name":"tyru","6":"tyru","last_name":" ","7":" ","releases":[{"0":"3311","vim_version":"7.0","1":"7.0","script_version":"0.2.0","2":"0.2.0","version_comment":"- change the specification of |savemap#save_map()|, |savemap#save_abbr()|.\r\n\t- Even if {lhs} was omitted, Returns |Dictionary| not |List|.\r\n- fix the bug ignoring a non-<buffer> mapping when a <buffer> mapping exists with same lhs-es.\r\n- improve |savemap#save_map()| and |savemap#save_abbr()|.\r\n\t- you can filter mappings you want by following conditions:\r\n\t\t- lhs (literaly, regexp)\r\n\t\t- rhs (literaly, regexp)\r\n\t\t- <silent>\r\n\t\t- remap\r\n\t\t- <expr>\r\n\t\t- <buffer>\r\n\t\t- modes\r\n- add some methods of the return value of\r\n  |savemap#save_map()| and |savemap#save_abbr()|.\r\n\t- see |savemap-restore-object| for details.\r\n- change the license.","3":"- change the specification of |savemap#save_map()|, |savemap#save_abbr()|.\r\n\t- Even if {lhs} was omitted, Returns |Dictionary| not |List|.\r\n- fix the bug ignoring a non-<buffer> mapping when a <buffer> mapping exists with same lhs-es.\r\n- improve |savemap#save_map()| and |savemap#save_abbr()|.\r\n\t- you can filter mappings you want by following conditions:\r\n\t\t- lhs (literaly, regexp)\r\n\t\t- rhs (literaly, regexp)\r\n\t\t- <silent>\r\n\t\t- remap\r\n\t\t- <expr>\r\n\t\t- <buffer>\r\n\t\t- modes\r\n- add some methods of the return value of\r\n  |savemap#save_map()| and |savemap#save_abbr()|.\r\n\t- see |savemap-restore-object| for details.\r\n- change the license.","package":"savemap.zip","4":"savemap.zip","src_id":"15048","5":"15048","creation_date":"1298143969","6":"1298143969"},{"0":"3311","vim_version":"7.3","1":"7.3","script_version":"0.0.0","2":"0.0.0","version_comment":"Initial upload","3":"Initial upload","package":"savemap.zip","4":"savemap.zip","src_id":"14200","5":"14200","creation_date":"1289121295","6":"1289121295"}]},"3310":{"script_id":"3310","0":"3310","script_name":"gdb4vim","1":"gdb4vim","script_type":"utility","2":"utility","summary":"This script give you some ability to use gdb","3":"This script give you some ability to use gdb","description":"This is actually my first script, so please give me your feedbacks and say whatever you like and whenever you want to!\r\n\r\nWritten with python, this script implements few basic functions in debugging, such as:\r\n1. Add a variable display\r\n2. Set\/clear breakpoint\r\n3. step\/next\r\n4. edit the value of a variable (since 0.023)\r\n\r\nYou can find this project at:\r\nhttp:\/\/code.google.com\/p\/gdb4vim\/\r\n\r\nEMail me if you'd like to participate!","4":"This is actually my first script, so please give me your feedbacks and say whatever you like and whenever you want to!\r\n\r\nWritten with python, this script implements few basic functions in debugging, such as:\r\n1. Add a variable display\r\n2. Set\/clear breakpoint\r\n3. step\/next\r\n4. edit the value of a variable (since 0.023)\r\n\r\nYou can find this project at:\r\nhttp:\/\/code.google.com\/p\/gdb4vim\/\r\n\r\nEMail me if you'd like to participate!","install_details":"First your VIM should be compiled with PYTHON.\r\nThen you need python-dbus which I used to connect with GDB via a server script.\r\nPut the plugin and doc folder in your $HOME\/.vim\r\nPut the gdb_dbus folder wherever you want.\r\nIn your VIMRC file, please specify the following:\r\nlet g:gdb_dbus_server_path = 'YOUR PATH TO gdb_dbus\/gdb_dbus_server.py'\r\n\r\nSet other settings as you like and for detailed information, please read the doc.","5":"First your VIM should be compiled with PYTHON.\r\nThen you need python-dbus which I used to connect with GDB via a server script.\r\nPut the plugin and doc folder in your $HOME\/.vim\r\nPut the gdb_dbus folder wherever you want.\r\nIn your VIMRC file, please specify the following:\r\nlet g:gdb_dbus_server_path = 'YOUR PATH TO gdb_dbus\/gdb_dbus_server.py'\r\n\r\nSet other settings as you like and for detailed information, please read the doc.","first_name":"Bruce","6":"Bruce","last_name":"Li","7":"Li","releases":[{"0":"3310","vim_version":"7.0","1":"7.0","script_version":"0.023","2":"0.023","version_comment":"Enable you to edit value of a variable by hitting its line in the display window.","3":"Enable you to edit value of a variable by hitting its line in the display window.","package":"gdb4vim-0.023.zip","4":"gdb4vim-0.023.zip","src_id":"14205","5":"14205","creation_date":"1289223858","6":"1289223858"},{"0":"3310","vim_version":"7.0","1":"7.0","script_version":"0.021","2":"0.021","version_comment":"Initial upload","3":"Initial upload","package":"gdb4vim-0.021.zip","4":"gdb4vim-0.021.zip","src_id":"14199","5":"14199","creation_date":"1289095527","6":"1289095527"}]},"3309":{"script_id":"3309","0":"3309","script_name":"vydark","1":"vydark","script_type":"color scheme","2":"color scheme","summary":"A versatile, comfortable colour scheme for every day use. Dark background.","3":"A versatile, comfortable colour scheme for every day use. Dark background.","description":"A pleasant environment for those extended coding sessions. This color scheme is meant for use with a gui version of Vim. \r\n\r\nPreview screenshot is available here: http:\/\/www.node.mu\/2010\/11\/26\/vydark-\u00e2\u0080\u0093-a-comfortable-vim-colour-scheme-for-everyday-use\/","4":"A pleasant environment for those extended coding sessions. This color scheme is meant for use with a gui version of Vim. \r\n\r\nPreview screenshot is available here: http:\/\/www.node.mu\/2010\/11\/26\/vydark-\u00e2\u0080\u0093-a-comfortable-vim-colour-scheme-for-everyday-use\/","install_details":"Download the script and copy it to your ~\/.vim\/colors\/ directory. To tell Vim to use the color scheme, \":colorscheme vydark\".","5":"Download the script and copy it to your ~\/.vim\/colors\/ directory. To tell Vim to use the color scheme, \":colorscheme vydark\".","first_name":"Vy-Shane","6":"Vy-Shane","last_name":"Sin Fat","7":"Sin Fat","releases":[{"0":"3309","vim_version":"7.3","1":"7.3","script_version":"1.2","2":"1.2","version_comment":"Added colours for code folds.","3":"Added colours for code folds.","package":"vydark.vim","4":"vydark.vim","src_id":"15759","5":"15759","creation_date":"1306724662","6":"1306724662"},{"0":"3309","vim_version":"7.3","1":"7.3","script_version":"1.1","2":"1.1","version_comment":"Bumped up contrast for text width column marker.\r\nCustomised colour for squiggly lines used to underline misspelt words when the spell checker is turned on.","3":"Bumped up contrast for text width column marker.\r\nCustomised colour for squiggly lines used to underline misspelt words when the spell checker is turned on.","package":"vydark.vim","4":"vydark.vim","src_id":"14699","5":"14699","creation_date":"1294413159","6":"1294413159"},{"0":"3309","vim_version":"7.3","1":"7.3","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"vydark.vim","4":"vydark.vim","src_id":"14176","5":"14176","creation_date":"1288851636","6":"1288851636"}]},"3308":{"script_id":"3308","0":"3308","script_name":"vim-refact","1":"vim-refact","script_type":"utility","2":"utility","summary":"Some refactoring for Vim","3":"Some refactoring for Vim","description":"Refactor plugin for Vim.\r\n\r\nYou can use this plugin to make some refactoring on your code.\r\nIt was originally written to work with the Ruby language, but it's\r\nflexible (I hope, I'll add some more languages later) to work with\r\nanother languages.\r\n\r\nhttp:\/\/github.com\/taq\/vim-refact","4":"Refactor plugin for Vim.\r\n\r\nYou can use this plugin to make some refactoring on your code.\r\nIt was originally written to work with the Ruby language, but it's\r\nflexible (I hope, I'll add some more languages later) to work with\r\nanother languages.\r\n\r\nhttp:\/\/github.com\/taq\/vim-refact","install_details":"Just copy the vim-refact.vim file to your ~\/.vim\/plugin directory.","5":"Just copy the vim-refact.vim file to your ~\/.vim\/plugin directory.","first_name":"Eustaquio","6":"Eustaquio","last_name":"Rangel de Oliveira Jr.","7":"Rangel de Oliveira Jr.","releases":[{"0":"3308","vim_version":"7.0","1":"7.0","script_version":"0.0.7","2":"0.0.7","version_comment":"Some fixes searching for Ruby patterns.","3":"Some fixes searching for Ruby patterns.","package":"vim-refact.vim","4":"vim-refact.vim","src_id":"14284","5":"14284","creation_date":"1290004211","6":"1290004211"},{"0":"3308","vim_version":"7.0","1":"7.0","script_version":"0.0.6","2":"0.0.6","version_comment":"Using silent when executing commands to extract method. ","3":"Using silent when executing commands to extract method. ","package":"vim-refact-0.0.6.zip","4":"vim-refact-0.0.6.zip","src_id":"14195","5":"14195","creation_date":"1289062743","6":"1289062743"},{"0":"3308","vim_version":"7.0","1":"7.0","script_version":"0.0.5","2":"0.0.5","version_comment":"Starting with PHP.\r\nA lot of fixes on methods and classes expressions.\r\n","3":"Starting with PHP.\r\nA lot of fixes on methods and classes expressions.\r\n","package":"vim-refact-0.0.5.zip","4":"vim-refact-0.0.5.zip","src_id":"14179","5":"14179","creation_date":"1288871654","6":"1288871654"},{"0":"3308","vim_version":"7.0","1":"7.0","script_version":"0.0.4","2":"0.0.4","version_comment":"Alignment of assignment operators. ","3":"Alignment of assignment operators. ","package":"vim-refact-0.0.4.zip","4":"vim-refact-0.0.4.zip","src_id":"14173","5":"14173","creation_date":"1288840886","6":"1288840886"},{"0":"3308","vim_version":"7.0","1":"7.0","script_version":"0.0.3","2":"0.0.3","version_comment":"Some more info on README. \r\nNormal and visual modes mappings. ","3":"Some more info on README. \r\nNormal and visual modes mappings. ","package":"vim-refact-0.0.3.zip","4":"vim-refact-0.0.3.zip","src_id":"14171","5":"14171","creation_date":"1288821833","6":"1288821833"},{"0":"3308","vim_version":"7.0","1":"7.0","script_version":"0.0.2","2":"0.0.2","version_comment":"Some more Java fixes.","3":"Some more Java fixes.","package":"vim-refact-0.0.2.zip","4":"vim-refact-0.0.2.zip","src_id":"14170","5":"14170","creation_date":"1288781864","6":"1288781864"},{"0":"3308","vim_version":"7.0","1":"7.0","script_version":"0.0.1","2":"0.0.1","version_comment":"Initial upload","3":"Initial upload","package":"vim-refact-0.0.1.zip","4":"vim-refact-0.0.1.zip","src_id":"14167","5":"14167","creation_date":"1288729075","6":"1288729075"}]},"3307":{"script_id":"3307","0":"3307","script_name":"vim-addon-async","1":"vim-addon-async","script_type":"utility","2":"utility","summary":"asynchronous communication for Vim","3":"asynchronous communication for Vim","description":"start external processes using VimL, write to their stdin and get notified when they produce output or kill the process when you're done.\r\n\r\nThis plugin also implements an experimental minimalistic terminal like interface so that you can run you favourite interpreter (irb, python, \/bin\/sh, sbt, scala, ...) inside a simple Vim buffer.\r\n\r\nThe API is non blocking and should be strong enough to enterface with debuggers etc.\r\n\r\nImplementation details: You have to compile an external c helper application which interfaces with the external process notifying Vim about arriving stdout blocks by using the client-server feature.\r\n\r\nIts used in production by me. Interface may still change slightly in the future. Under some conditions Vim crashes although it shouldn't. Try it and report how well it works for you.\r\n\r\nIf you've trouble getting started contact me.","4":"start external processes using VimL, write to their stdin and get notified when they produce output or kill the process when you're done.\r\n\r\nThis plugin also implements an experimental minimalistic terminal like interface so that you can run you favourite interpreter (irb, python, \/bin\/sh, sbt, scala, ...) inside a simple Vim buffer.\r\n\r\nThe API is non blocking and should be strong enough to enterface with debuggers etc.\r\n\r\nImplementation details: You have to compile an external c helper application which interfaces with the external process notifying Vim about arriving stdout blocks by using the client-server feature.\r\n\r\nIts used in production by me. Interface may still change slightly in the future. Under some conditions Vim crashes although it shouldn't. Try it and report how well it works for you.\r\n\r\nIf you've trouble getting started contact me.","install_details":"This plugin can be used on its own. Because some more (optional) dependencies may be added I recommend using vim-addon-manager for installing. See README file","5":"This plugin can be used on its own. Because some more (optional) dependencies may be added I recommend using vim-addon-manager for installing. See README file","first_name":"Marc","6":"Marc","last_name":"Weber","7":"Weber","releases":[{"0":"3307","vim_version":"7.0","1":"7.0","script_version":"0.4.1","2":"0.4.1","version_comment":"fix","3":"fix","package":"vim-addon-async-0.4.1.zip","4":"vim-addon-async-0.4.1.zip","src_id":"14767","5":"14767","creation_date":"1295232032","6":"1295232032"},{"0":"3307","vim_version":"7.0","1":"7.0","script_version":"0.4","2":"0.4","version_comment":"depend on signs addon, drop input > prefix, add > to reply lines. Keep track of last reply line. See docs","3":"depend on signs addon, drop input > prefix, add > to reply lines. Keep track of last reply line. See docs","package":"vim-addon-async-0.4.zip","4":"vim-addon-async-0.4.zip","src_id":"14766","5":"14766","creation_date":"1295231639","6":"1295231639"},{"0":"3307","vim_version":"7.0","1":"7.0","script_version":"0.3.2","2":"0.3.2","version_comment":"fix quoting bug","3":"fix quoting bug","package":"vim-addon-async-0.3.2.zip","4":"vim-addon-async-0.3.2.zip","src_id":"14763","5":"14763","creation_date":"1295219791","6":"1295219791"},{"0":"3307","vim_version":"7.0","1":"7.0","script_version":"0.3.1","2":"0.3.1","version_comment":"python repl dict key completion support","3":"python repl dict key completion support","package":"vim-addon-async-0.3.1.zip","4":"vim-addon-async-0.3.1.zip","src_id":"14754","5":"14754","creation_date":"1295106575","6":"1295106575"},{"0":"3307","vim_version":"7.0","1":"7.0","script_version":"0.3","2":"0.3","version_comment":"repls scala,python,irb and completion work fine now","3":"repls scala,python,irb and completion work fine now","package":"vim-addon-async-0.3.zip","4":"vim-addon-async-0.3.zip","src_id":"14749","5":"14749","creation_date":"1295055449","6":"1295055449"},{"0":"3307","vim_version":"7.0","1":"7.0","script_version":"0.2","2":"0.2","version_comment":"speed improvements (pass huge chunks using files), 0 byte support (example xdebug), ruby REPL","3":"speed improvements (pass huge chunks using files), 0 byte support (example xdebug), ruby REPL","package":"vim-addon-async-0.2.zip","4":"vim-addon-async-0.2.zip","src_id":"14300","5":"14300","creation_date":"1290097771","6":"1290097771"},{"0":"3307","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"signal support, scala REPL completion, pid fix","3":"signal support, scala REPL completion, pid fix","package":"vim-addon-async-0.1.zip","4":"vim-addon-async-0.1.zip","src_id":"14178","5":"14178","creation_date":"1288866707","6":"1288866707"},{"0":"3307","vim_version":"7.0","1":"7.0","script_version":"0.0","2":"0.0","version_comment":"Initial upload","3":"Initial upload","package":"initial.zip","4":"initial.zip","src_id":"14157","5":"14157","creation_date":"1288549781","6":"1288549781"}]},"3306":{"script_id":"3306","0":"3306","script_name":"altera.vim","1":"altera.vim","script_type":"syntax","2":"syntax","summary":"Syntax file for Altera Quartus qsf files","3":"Syntax file for Altera Quartus qsf files","description":"This is a syntax file for Altera Quartus (version .9.1) qsf files.  A dictionary file is included and will automatically link in if found to provide command completion.","4":"This is a syntax file for Altera Quartus (version .9.1) qsf files.  A dictionary file is included and will automatically link in if found to provide command completion.","install_details":"Nothing special.  Just download and unzip\/untar.  There's a README file that shows various ways of hooking it in.","5":"Nothing special.  Just download and unzip\/untar.  There's a README file that shows various ways of hooking it in.","first_name":"Paul","6":"Paul","last_name":"Zimmer","7":"Zimmer","releases":[{"0":"3306","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"altera.vim.tgz","4":"altera.vim.tgz","src_id":"14156","5":"14156","creation_date":"1288548508","6":"1288548508"}]},"3305":{"script_id":"3305","0":"3305","script_name":"altera_sta.vim","1":"altera_sta.vim","script_type":"syntax","2":"syntax","summary":"Syntax file for Altera Quartus TimeQuest (sdc) files","3":"Syntax file for Altera Quartus TimeQuest (sdc) files","description":"This is a syntax file for Altera Quartus (version .9.1) static timing files.  This includes Altera's version of sdc, plus Altera's extensions.  A dictionary file is included and will automatically link in if found to provide command completion.","4":"This is a syntax file for Altera Quartus (version .9.1) static timing files.  This includes Altera's version of sdc, plus Altera's extensions.  A dictionary file is included and will automatically link in if found to provide command completion.","install_details":"Nothing special.  Just download and unzip\/untar.  There's a README file that shows various ways of hooking it in.","5":"Nothing special.  Just download and unzip\/untar.  There's a README file that shows various ways of hooking it in.","first_name":"Paul","6":"Paul","last_name":"Zimmer","7":"Zimmer","releases":[{"0":"3305","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"altera_sta.vim.tgz","4":"altera_sta.vim.tgz","src_id":"14155","5":"14155","creation_date":"1288546967","6":"1288546967"}]},"3304":{"script_id":"3304","0":"3304","script_name":"Gundo","1":"Gundo","script_type":"utility","2":"utility","summary":"Visualize your undo tree.","3":"Visualize your undo tree.","description":"Gundo is a Vim plugin for visualizing your undo tree to make it usable.\r\n\r\nGo to the site for more information: http:\/\/sjl.bitbucket.org\/gundo.vim\/\r\n\r\nRequirements: Vim 7.3+ with Python 2.4+ support.","4":"Gundo is a Vim plugin for visualizing your undo tree to make it usable.\r\n\r\nGo to the site for more information: http:\/\/sjl.bitbucket.org\/gundo.vim\/\r\n\r\nRequirements: Vim 7.3+ with Python 2.4+ support.","install_details":"Use Pathogen: http:\/\/addisu.taddese.com\/blog\/using-github-and-pathogen-for-your-vim-config-files\/\r\n\r\nNo, seriously.  You'll thank me.","5":"Use Pathogen: http:\/\/addisu.taddese.com\/blog\/using-github-and-pathogen-for-your-vim-config-files\/\r\n\r\nNo, seriously.  You'll thank me.","first_name":"Steve","6":"Steve","last_name":"Losh","7":"Losh","releases":[{"0":"3304","vim_version":"7.3","1":"7.3","script_version":"2.6.2","2":"2.6.2","version_comment":"* Fix to deal with backwards-incompatible change in Python 3.5's difflib.\r\n* Add Neovim support.\r\n* Fix several Python-related bugs.\r\n* Add g:gundo_return_on_revert option.\r\n","3":"* Fix to deal with backwards-incompatible change in Python 3.5's difflib.\r\n* Add Neovim support.\r\n* Fix several Python-related bugs.\r\n* Add g:gundo_return_on_revert option.\r\n","package":"gundo.zip","4":"gundo.zip","src_id":"24805","5":"24805","creation_date":"1481912558","6":"1481912558"},{"0":"3304","vim_version":"7.3","1":"7.3","script_version":"2.5.0","2":"2.5.0","version_comment":"* Fix the help window to take custom mappings into account.\r\n* Add g:gundo_playback_delay option.\r\n","3":"* Fix the help window to take custom mappings into account.\r\n* Add g:gundo_playback_delay option.\r\n","package":"gundo.zip","4":"gundo.zip","src_id":"20505","5":"20505","creation_date":"1373503178","6":"1373503178"},{"0":"3304","vim_version":"7.3","1":"7.3","script_version":"2.4.0","2":"2.4.0","version_comment":"* Add auto preview option.\r\n* Add 'r' mapping to preview current state.\r\n* Add public gundo#GundoShow() and gundo#GundoHide() functions.","3":"* Add auto preview option.\r\n* Add 'r' mapping to preview current state.\r\n* Add public gundo#GundoShow() and gundo#GundoHide() functions.","package":"gundo.zip","4":"gundo.zip","src_id":"18081","5":"18081","creation_date":"1338672618","6":"1338672618"},{"0":"3304","vim_version":"7.3","1":"7.3","script_version":"2.3.0","2":"2.3.0","version_comment":"* Add statusline configuration options.","3":"* Add statusline configuration options.","package":"gundo.zip","4":"gundo.zip","src_id":"17406","5":"17406","creation_date":"1328670061","6":"1328670061"},{"0":"3304","vim_version":"7.3","1":"7.3","script_version":"2.2.2","2":"2.2.2","version_comment":"* More performance improvements.\r\n* Repackaged with some missing files, sorry about that.","3":"* More performance improvements.\r\n* Repackaged with some missing files, sorry about that.","package":"gundo.zip","4":"gundo.zip","src_id":"16172","5":"16172","creation_date":"1311946706","6":"1311946706"},{"0":"3304","vim_version":"7.3","1":"7.3","script_version":"2.2.1","2":"2.2.1","version_comment":"* Refactoring and performance improvements.","3":"* Refactoring and performance improvements.","package":"gundo.zip","4":"gundo.zip","src_id":"15996","5":"15996","creation_date":"1309269136","6":"1309269136"},{"0":"3304","vim_version":"7.3","1":"7.3","script_version":"2.2.0","2":"2.2.0","version_comment":"* Add the g:gundo_close_on_revert setting.\r\n* Fix a bug with the splitbelow setting.","3":"* Add the g:gundo_close_on_revert setting.\r\n* Fix a bug with the splitbelow setting.","package":"gundo.zip","4":"gundo.zip","src_id":"15744","5":"15744","creation_date":"1306508426","6":"1306508426"},{"0":"3304","vim_version":"7.3","1":"7.3","script_version":"2.1.1","2":"2.1.1","version_comment":"* Fix a bug with the movement mapping keys.","3":"* Fix a bug with the movement mapping keys.","package":"gundo.zip","4":"gundo.zip","src_id":"15211","5":"15211","creation_date":"1300048042","6":"1300048042"},{"0":"3304","vim_version":"7.3","1":"7.3","script_version":"2.1.0","2":"2.1.0","version_comment":"* Warnings about having an incompatible Vim and\/or Python installation are now deferred until the first time you try to use Gundo, instead of being displayed on launch.\r\n* The <j> and <k> mappings are now configurable with g:gundo_map_move_older and g:gundo_map_move_newer.\r\n* The o, <Up> and <Down> keys are now mapped in the Gundo pane.\r\n* Improve and add several unit tests for Gundo.","3":"* Warnings about having an incompatible Vim and\/or Python installation are now deferred until the first time you try to use Gundo, instead of being displayed on launch.\r\n* The <j> and <k> mappings are now configurable with g:gundo_map_move_older and g:gundo_map_move_newer.\r\n* The o, <Up> and <Down> keys are now mapped in the Gundo pane.\r\n* Improve and add several unit tests for Gundo.","package":"gundo.zip","4":"gundo.zip","src_id":"15184","5":"15184","creation_date":"1299718195","6":"1299718195"},{"0":"3304","vim_version":"7.3","1":"7.3","script_version":"2.0.0","2":"2.0.0","version_comment":"* Make GundoToggle close the Gundo windows if they're visible but not the current window, instead of moving to them.\r\n* Add the g:gundo_help setting.\r\n* Add the g:gundo_disable setting.\r\n* Add the 'p' mapping to preview the result of reverting to the selected state.\r\n* Fix movement commands with counts in the graph.","3":"* Make GundoToggle close the Gundo windows if they're visible but not the current window, instead of moving to them.\r\n* Add the g:gundo_help setting.\r\n* Add the g:gundo_disable setting.\r\n* Add the 'p' mapping to preview the result of reverting to the selected state.\r\n* Fix movement commands with counts in the graph.","package":"gundo.zip","4":"gundo.zip","src_id":"14226","5":"14226","creation_date":"1289406751","6":"1289406751"},{"0":"3304","vim_version":"7.3","1":"7.3","script_version":"1.0.0","2":"1.0.0","version_comment":"Initial upload","3":"Initial upload","package":"gundo.zip","4":"gundo.zip","src_id":"14148","5":"14148","creation_date":"1288379630","6":"1288379630"}]},"3303":{"script_id":"3303","0":"3303","script_name":"smartbd","1":"smartbd","script_type":"utility","2":"utility","summary":"keep splits when deleting buffers","3":"keep splits when deleting buffers","description":"Adds a command for deleting buffers like :bd but does not close splits. Instead it tries to go to the next buffer first before deleting the buffer.\r\n","4":"Adds a command for deleting buffers like :bd but does not close splits. Instead it tries to go to the next buffer first before deleting the buffer.\r\n","install_details":"","5":"","first_name":"Tom","6":"Tom","last_name":"Wieland","7":"Wieland","releases":[{"0":"3303","vim_version":"7.0","1":"7.0","script_version":"3558653","2":"3558653","version_comment":"Initial upload","3":"Initial upload","package":"Industrial-vim-smartbd-3558653.zip","4":"Industrial-vim-smartbd-3558653.zip","src_id":"14143","5":"14143","creation_date":"1288292664","6":"1288292664"}]},"3302":{"script_id":"3302","0":"3302","script_name":"clang complete","1":"clang complete","script_type":"utility","2":"utility","summary":"Use of Clang for completing C, C++, Objective-C and Objective-C++","3":"Use of Clang for completing C, C++, Objective-C and Objective-C++","description":"This plugin use clang for accurately completing C, C++, Objective-C and Objective-C++ code.\r\n\r\nYou don't need any ctags for it to work! Only clang is needed. Clang version 2.8 or higher is recommended for c++ completion. After a . , -> and :: it is automatically trying to complete the code. If you want to \"force\" the completion, use <C-X><C-U> which is the mapping for user defined completion. Because clang is parsing your source file, it can detect errors inside your code, and highlight them! Plus it can open the quickfix window automatically.\r\n\r\nSince version 1.4, snippets can be used to complete function arguments. It is triggered after a completion, and you can go to the next argument with the <Tab> key in normal mode.\r\n\r\nIf you've got special flags for a project (especially -I and -D ones), clang may be unable to complete your code. To overcome this limitation put the flags inside the file .clang_complete at the root of your project.\r\n\r\nLatest version will always be on github: http:\/\/github.com\/Rip-Rip\/clang_complete\r\n\r\nDo not hesitate to report bugs or ask for features.\r\n\r\nFor more information about the configuration, look at the help (:h clang_complete)","4":"This plugin use clang for accurately completing C, C++, Objective-C and Objective-C++ code.\r\n\r\nYou don't need any ctags for it to work! Only clang is needed. Clang version 2.8 or higher is recommended for c++ completion. After a . , -> and :: it is automatically trying to complete the code. If you want to \"force\" the completion, use <C-X><C-U> which is the mapping for user defined completion. Because clang is parsing your source file, it can detect errors inside your code, and highlight them! Plus it can open the quickfix window automatically.\r\n\r\nSince version 1.4, snippets can be used to complete function arguments. It is triggered after a completion, and you can go to the next argument with the <Tab> key in normal mode.\r\n\r\nIf you've got special flags for a project (especially -I and -D ones), clang may be unable to complete your code. To overcome this limitation put the flags inside the file .clang_complete at the root of your project.\r\n\r\nLatest version will always be on github: http:\/\/github.com\/Rip-Rip\/clang_complete\r\n\r\nDo not hesitate to report bugs or ask for features.\r\n\r\nFor more information about the configuration, look at the help (:h clang_complete)","install_details":"If you have installed vimscript #1520, please remove it, as it is confliting with this one.\r\nTo install: vim clang_complete.vmb -c 'so %' -c 'q'","5":"If you have installed vimscript #1520, please remove it, as it is confliting with this one.\r\nTo install: vim clang_complete.vmb -c 'so %' -c 'q'","first_name":"Xavier","6":"Xavier","last_name":"Deguillard","7":"Deguillard","releases":[{"0":"3302","vim_version":"7.2","1":"7.2","script_version":"2.0","2":"2.0","version_comment":"- Last version to support clang binary based completion\r\n- Lots of improvement to the libclang based completion\r\n- Fix lots of bugs.","3":"- Last version to support clang binary based completion\r\n- Lots of improvement to the libclang based completion\r\n- Fix lots of bugs.","package":"clang_complete.vmb","4":"clang_complete.vmb","src_id":"19588","5":"19588","creation_date":"1362376787","6":"1362376787"},{"0":"3302","vim_version":"7.2","1":"7.2","script_version":"1.8","2":"1.8","version_comment":"- Add support for fast completion with libclang\r\n- Add support for snipmate and ultisnips based snippets\r\n- Fix tons of bugs\r\n- Warning, this is the last version that support clang 2.8 and 2.9","3":"- Add support for fast completion with libclang\r\n- Add support for snipmate and ultisnips based snippets\r\n- Fix tons of bugs\r\n- Warning, this is the last version that support clang 2.8 and 2.9","package":"clang_complete.vmb","4":"clang_complete.vmb","src_id":"17048","5":"17048","creation_date":"1323464684","6":"1323464684"},{"0":"3302","vim_version":"7.2","1":"7.2","script_version":"1.4","2":"1.4","version_comment":"- Improve the snippets engine\r\n- Bug correction","3":"- Improve the snippets engine\r\n- Bug correction","package":"clang_complete.vim","4":"clang_complete.vim","src_id":"14558","5":"14558","creation_date":"1292685307","6":"1292685307"},{"0":"3302","vim_version":"7.0","1":"7.0","script_version":"1.2","2":"1.2","version_comment":"- Added Objective-C and Objective-C++ support\r\n- Correct a lot of bug\r\n- Highlight of errors\/warning when completing\r\n- Add snippets on function parameters completion (not finished)\r\n- Drop some system() call\r\n- Add g:ClangUpdateQuickFix function, to be used on a mapping.","3":"- Added Objective-C and Objective-C++ support\r\n- Correct a lot of bug\r\n- Highlight of errors\/warning when completing\r\n- Add snippets on function parameters completion (not finished)\r\n- Drop some system() call\r\n- Add g:ClangUpdateQuickFix function, to be used on a mapping.","package":"clang_complete.vim","4":"clang_complete.vim","src_id":"14232","5":"14232","creation_date":"1289470659","6":"1289470659"},{"0":"3302","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"clang_complete.vim","4":"clang_complete.vim","src_id":"14137","5":"14137","creation_date":"1288211553","6":"1288211553"}]},"3301":{"script_id":"3301","0":"3301","script_name":"TrimBlank","1":"TrimBlank","script_type":"utility","2":"utility","summary":"help trim trailing blank characters and blank lines","3":"help trim trailing blank characters and blank lines","description":"TrimBlank is a vim plugin aimed at helping trim trailing blank characters and\r\nblank lines.\r\n\r\nHow to use this plugin?\r\nSelect some lines and type \"<Leader>ttb\"(<Leader> would be \"backslash\" by\r\ndefault), then the trailing blank characters of the lines selected will be\r\ntrimmed; select some lines and type \"<Leader>tbl\", then the blank lines among\r\nthe lines selected will be trimmed; select some lines and type \"<Leader>tab\",\r\nthen both trailing blank characters and blank lines would be trimmed.\r\n\r\nIf you find any bug, please report it to xuhdev@gmail.com or submit it on the \r\nissue tracker: \r\nhttps:\/\/bitbucket.org\/xuhdev\/trimblank\/issues\r\n\r\n\r\nRepository: https:\/\/bitbucket.org\/xuhdev\/trimblank","4":"TrimBlank is a vim plugin aimed at helping trim trailing blank characters and\r\nblank lines.\r\n\r\nHow to use this plugin?\r\nSelect some lines and type \"<Leader>ttb\"(<Leader> would be \"backslash\" by\r\ndefault), then the trailing blank characters of the lines selected will be\r\ntrimmed; select some lines and type \"<Leader>tbl\", then the blank lines among\r\nthe lines selected will be trimmed; select some lines and type \"<Leader>tab\",\r\nthen both trailing blank characters and blank lines would be trimmed.\r\n\r\nIf you find any bug, please report it to xuhdev@gmail.com or submit it on the \r\nissue tracker: \r\nhttps:\/\/bitbucket.org\/xuhdev\/trimblank\/issues\r\n\r\n\r\nRepository: https:\/\/bitbucket.org\/xuhdev\/trimblank","install_details":"Download the TrimBlank.zip file and extract it to your vim runtime\r\ndirectory(~\/.vim on linux and $VIM_INSTALLATION_FOLDER\\vimfiles on\r\nwindows), you'd better then use helptags command to generate the help\r\ntag(for example use \":helptags ~\/.vim\/doc\" on Linux).\r\n\r\n","5":"Download the TrimBlank.zip file and extract it to your vim runtime\r\ndirectory(~\/.vim on linux and $VIM_INSTALLATION_FOLDER\\vimfiles on\r\nwindows), you'd better then use helptags command to generate the help\r\ntag(for example use \":helptags ~\/.vim\/doc\" on Linux).\r\n\r\n","first_name":"Hong","6":"Hong","last_name":"Xu","7":"Xu","releases":[{"0":"3301","vim_version":"7.0","1":"7.0","script_version":"0.3.1","2":"0.3.1","version_comment":"optimize the popup menu.","3":"optimize the popup menu.","package":"TrimBlank.zip","4":"TrimBlank.zip","src_id":"14313","5":"14313","creation_date":"1290248945","6":"1290248945"},{"0":"3301","vim_version":"7.0","1":"7.0","script_version":"0.3","2":"0.3","version_comment":"Move some functions to autoload directory so that this plugin could also be used as a third party library for other plugins. \r\nOptimise the prompt.","3":"Move some functions to autoload directory so that this plugin could also be used as a third party library for other plugins. \r\nOptimise the prompt.","package":"TrimBlank.zip","4":"TrimBlank.zip","src_id":"14193","5":"14193","creation_date":"1289043187","6":"1289043187"},{"0":"3301","vim_version":"7.0","1":"7.0","script_version":"0.2","2":"0.2","version_comment":"add TBTrimAllBlank command. Update the document.","3":"add TBTrimAllBlank command. Update the document.","package":"TrimBlank.zip","4":"TrimBlank.zip","src_id":"14149","5":"14149","creation_date":"1288438163","6":"1288438163"},{"0":"3301","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"trimblank.zip","4":"trimblank.zip","src_id":"14134","5":"14134","creation_date":"1288187520","6":"1288187520"}]},"3300":{"script_id":"3300","0":"3300","script_name":"up.vim","1":"up.vim","script_type":"color scheme","2":"color scheme","summary":"Dark-background color scheme","3":"Dark-background color scheme","description":"Screenshot available on GitHub \u00e2\u0080\u0094 http:\/\/github.com\/kossnocorp\/up.vim","4":"Screenshot available on GitHub \u00e2\u0080\u0094 http:\/\/github.com\/kossnocorp\/up.vim","install_details":"","5":"","first_name":"Sasha","6":"Sasha","last_name":"Koss","7":"Koss","releases":[{"0":"3300","vim_version":"7.0","1":"7.0","script_version":"0.9","2":"0.9","version_comment":"Added Java, SQL; improve colors","3":"Added Java, SQL; improve colors","package":"up.vim","4":"up.vim","src_id":"14462","5":"14462","creation_date":"1291875444","6":"1291875444"},{"0":"3300","vim_version":"7.0","1":"7.0","script_version":"0.7","2":"0.7","version_comment":"Initial upload","3":"Initial upload","package":"up.vim","4":"up.vim","src_id":"14130","5":"14130","creation_date":"1288156427","6":"1288156427"}]},"3299":{"script_id":"3299","0":"3299","script_name":"Sorcerer","1":"Sorcerer","script_type":"color scheme","2":"color scheme","summary":"Dark-background color scheme (GUI\/256-color terminal).","3":"Dark-background color scheme (GUI\/256-color terminal).","description":"A heavily-reworked version of 'Mustang' by Henrique C. Alves, with lower-keyed colors. Screenshots available at: http:\/\/jeetworks.org\/sorcerer .","4":"A heavily-reworked version of 'Mustang' by Henrique C. Alves, with lower-keyed colors. Screenshots available at: http:\/\/jeetworks.org\/sorcerer .","install_details":"Download\/save\/copy\/move the file \"sorcerer.vim\" to your \"$VIMRUNTIME\/colors\" directory (e.g., \"~\/.vim\/colors\"). Activate the color scheme by entering the command, \":colors sorcerer\".","5":"Download\/save\/copy\/move the file \"sorcerer.vim\" to your \"$VIMRUNTIME\/colors\" directory (e.g., \"~\/.vim\/colors\"). Activate the color scheme by entering the command, \":colors sorcerer\".","first_name":"Jeet","6":"Jeet","last_name":"Sukumaran","7":"Sukumaran","releases":[{"0":"3299","vim_version":"7.0","1":"7.0","script_version":"1.4","2":"1.4","version_comment":"- ``set background=dark`` added\r\n- Signs column colors tweaked","3":"- ``set background=dark`` added\r\n- Signs column colors tweaked","package":"sorcerer.vim","4":"sorcerer.vim","src_id":"21909","5":"21909","creation_date":"1400636986","6":"1400636986"},{"0":"3299","vim_version":"7.0","1":"7.0","script_version":"1.3","2":"1.3","version_comment":"- reworked diff colors","3":"- reworked diff colors","package":"sorcerer.vim","4":"sorcerer.vim","src_id":"16882","5":"16882","creation_date":"1321467507","6":"1321467507"},{"0":"3299","vim_version":"7.0","1":"7.0","script_version":"1.2","2":"1.2","version_comment":"- Added support for 256-color console\/terminal.","3":"- Added support for 256-color console\/terminal.","package":"sorcerer.vim","4":"sorcerer.vim","src_id":"16773","5":"16773","creation_date":"1320011975","6":"1320011975"},{"0":"3299","vim_version":"7.0","1":"7.0","script_version":"1.1","2":"1.1","version_comment":"Toned down folded text colors.","3":"Toned down folded text colors.","package":"sorcerer.vim","4":"sorcerer.vim","src_id":"14475","5":"14475","creation_date":"1292092693","6":"1292092693"},{"0":"3299","vim_version":"7.0","1":"7.0","script_version":"1.0.1","2":"1.0.1","version_comment":"Cleaned-up commented out code.","3":"Cleaned-up commented out code.","package":"sorcerer.vim","4":"sorcerer.vim","src_id":"14132","5":"14132","creation_date":"1288159103","6":"1288159103"}]},"3298":{"script_id":"3298","0":"3298","script_name":"vim_faq","1":"vim_faq","script_type":"utility","2":"utility","summary":"The Vim-FAQ from vimdoc.sourceforge.net","3":"The Vim-FAQ from vimdoc.sourceforge.net","description":"This is the vimfaq from http:\/\/vimdoc.sf.net (with slight changes added by myself).\r\nThe new version of the faq can be found at http:\/\/vimhelp.appspot.com\/\r\n\r\nThis Vim FAQ is created from the questions and answers posted to the\r\nvim@vim.org user mailing list and the comp.editors newsgroup. There are\r\nseveral ways to solve a problem in Vim. This FAQ gives one of those several\r\npossibilities. You can explore the other ways using the information and\r\nlinks given in this FAQ. The credit for the answers in this FAQ goes to\r\nPeppe, Benji, Charles Campbell and numerous others.\r\n\r\nThis is only a documentation plugin. \r\n\r\nThe source can be found at github: http:\/\/github.com\/chrisbra\/vim_faq","4":"This is the vimfaq from http:\/\/vimdoc.sf.net (with slight changes added by myself).\r\nThe new version of the faq can be found at http:\/\/vimhelp.appspot.com\/\r\n\r\nThis Vim FAQ is created from the questions and answers posted to the\r\nvim@vim.org user mailing list and the comp.editors newsgroup. There are\r\nseveral ways to solve a problem in Vim. This FAQ gives one of those several\r\npossibilities. You can explore the other ways using the information and\r\nlinks given in this FAQ. The credit for the answers in this FAQ goes to\r\nPeppe, Benji, Charles Campbell and numerous others.\r\n\r\nThis is only a documentation plugin. \r\n\r\nThe source can be found at github: http:\/\/github.com\/chrisbra\/vim_faq","install_details":"This plugin is provided as vimball. To install, simply open the .vba file with vim and source it (:so %)\r\n(see :h vimball-introduction for details).\r\n\r\nAfter installation and restarting vim, you'll find the faq at:\r\n:h vim-faq","5":"This plugin is provided as vimball. To install, simply open the .vba file with vim and source it (:so %)\r\n(see :h vimball-introduction for details).\r\n\r\nAfter installation and restarting vim, you'll find the faq at:\r\n:h vim-faq","first_name":"Christian","6":"Christian","last_name":"Brabandt","7":"Brabandt","releases":[{"0":"3298","vim_version":"6","1":"6","script_version":"46","2":"46","version_comment":"A new release for Vim 7.4\n(automatically uploaded)","3":"A new release for Vim 7.4\n(automatically uploaded)","package":"faq-46.vmb","4":"faq-46.vmb","src_id":"20640","5":"20640","creation_date":"1376414630","6":"1376414630"},{"0":"3298","vim_version":"6","1":"6","script_version":"45","2":"45","version_comment":"Fix typos by Dominique Pell\u00c3\u0083\u00c6\u0092\u00c3\u0082\u00c2\u00a9, thanks!\n(automatically uploaded)","3":"Fix typos by Dominique Pell\u00c3\u0083\u00c6\u0092\u00c3\u0082\u00c2\u00a9, thanks!\n(automatically uploaded)","package":"faq-45.vmb","4":"faq-45.vmb","src_id":"18709","5":"18709","creation_date":"1348860342","6":"1348860342"},{"0":"3298","vim_version":"6","1":"6","script_version":"44","2":"44","version_comment":"updated Q:17.3  by Daniel Hahler, thanks!\n(automatically uploaded)","3":"updated Q:17.3  by Daniel Hahler, thanks!\n(automatically uploaded)","package":"faq-44.vmb","4":"faq-44.vmb","src_id":"18693","5":"18693","creation_date":"1348680980","6":"1348680980"},{"0":"3298","vim_version":"6","1":"6","script_version":"43","2":"43","version_comment":"updated Q: 26.3 by T. Mechelynck\n(automatically uploaded)","3":"updated Q: 26.3 by T. Mechelynck\n(automatically uploaded)","package":"faq-43.vmb","4":"faq-43.vmb","src_id":"18256","5":"18256","creation_date":"1342265957","6":"1342265957"},{"0":"3298","vim_version":"6","1":"6","script_version":"41","2":"41","version_comment":"Q: 11.25\nQ: 24.16\nUpdates on several other questions.\n(automatically uploaded)","3":"Q: 11.25\nQ: 24.16\nUpdates on several other questions.\n(automatically uploaded)","package":"faq-41.vmb","4":"faq-41.vmb","src_id":"17353","5":"17353","creation_date":"1328042275","6":"1328042275"},{"0":"3298","vim_version":"6","1":"6","script_version":"39","2":"39","version_comment":"New Q: 11.24: Why does this pattern 'a.\\{-}p\\@!' not match?\nNew Q  36.12: How to debug .vimrc file?\n    Q. 20.4 more verbose\n(automatically uploaded)","3":"New Q: 11.24: Why does this pattern 'a.\\{-}p\\@!' not match?\nNew Q  36.12: How to debug .vimrc file?\n    Q. 20.4 more verbose\n(automatically uploaded)","package":"faq-39.vmb","4":"faq-39.vmb","src_id":"16591","5":"16591","creation_date":"1317071007","6":"1317071007"},{"0":"3298","vim_version":"6","1":"6","script_version":"38","2":"38","version_comment":"New Question 29.7: Why is syntax folding slow?\n(automatically uploaded)","3":"New Question 29.7: Why is syntax folding slow?\n(automatically uploaded)","package":"faq-38.vba","4":"faq-38.vba","src_id":"16101","5":"16101","creation_date":"1311111587","6":"1311111587"},{"0":"3298","vim_version":"6","1":"6","script_version":"36","2":"36","version_comment":"many small changes\n(automatically uploaded)","3":"many small changes\n(automatically uploaded)","package":"faq-36.vba","4":"faq-36.vba","src_id":"15940","5":"15940","creation_date":"1308605315","6":"1308605315"},{"0":"3298","vim_version":"6","1":"6","script_version":"35","2":"35","version_comment":"(Fixed Typo, mention github repository, Thanks M.Gedminas)\nNew Q: 36.11: Why shouldnt I change the files in the vimruntime dir? Answer provided by G.Johnson)\n(automatically uploaded)","3":"(Fixed Typo, mention github repository, Thanks M.Gedminas)\nNew Q: 36.11: Why shouldnt I change the files in the vimruntime dir? Answer provided by G.Johnson)\n(automatically uploaded)","package":"faq-35.vba","4":"faq-35.vba","src_id":"15917","5":"15917","creation_date":"1308327982","6":"1308327982"},{"0":"3298","vim_version":"6","1":"6","script_version":"34","2":"34","version_comment":"Q:14.14 Annotation from Gary Johnson. Thanks!\n(automatically uploaded)","3":"Q:14.14 Annotation from Gary Johnson. Thanks!\n(automatically uploaded)","package":"vim_faq-34.vba","4":"vim_faq-34.vba","src_id":"15441","5":"15441","creation_date":"1302631379","6":"1302631379"},{"0":"3298","vim_version":"6","1":"6","script_version":"32","2":"32","version_comment":"Question 20.20: How to use normal mode mappings from insert mode (I.Karkat)\n(automatically uploaded)","3":"Question 20.20: How to use normal mode mappings from insert mode (I.Karkat)\n(automatically uploaded)","package":"faq-32.vba","4":"faq-32.vba","src_id":"14975","5":"14975","creation_date":"1297119508","6":"1297119508"},{"0":"3298","vim_version":"6","1":"6","script_version":"26","2":"26","version_comment":"small changes, correct wrong tags\n(automatically uploaded)","3":"small changes, correct wrong tags\n(automatically uploaded)","package":"faq-26.vba","4":"faq-26.vba","src_id":"14456","5":"14456","creation_date":"1291761187","6":"1291761187"},{"0":"3298","vim_version":"6","1":"6","script_version":"25","2":"25","version_comment":"Added Question 35.10 how to install required dependencis to build vim\n(automatically uploaded)","3":"Added Question 35.10 how to install required dependencis to build vim\n(automatically uploaded)","package":"faq-25.vba","4":"faq-25.vba","src_id":"14451","5":"14451","creation_date":"1291668427","6":"1291668427"},{"0":"3298","vim_version":"6","1":"6","script_version":"24","2":"24","version_comment":"Detailed answer about stair stepping when pasting into vim. Provided\nby Yegappan Lakshmanan in vim_use thread \"how to solve this strange issue?\"\nhttp:\/\/groups.google.com\/group\/vim_use\/msg\/d32093f356f3476e\n\nThanks.\n\n(automatically uploaded)","3":"Detailed answer about stair stepping when pasting into vim. Provided\nby Yegappan Lakshmanan in vim_use thread \"how to solve this strange issue?\"\nhttp:\/\/groups.google.com\/group\/vim_use\/msg\/d32093f356f3476e\n\nThanks.\n\n(automatically uploaded)","package":"faq-24.vba","4":"faq-24.vba","src_id":"14450","5":"14450","creation_date":"1291664298","6":"1291664298"},{"0":"3298","vim_version":"6","1":"6","script_version":"23","2":"23","version_comment":"fixed some small typos\n(automatically uploaded)","3":"fixed some small typos\n(automatically uploaded)","package":"vim_faq-23.vba","4":"vim_faq-23.vba","src_id":"14424","5":"14424","creation_date":"1291384505","6":"1291384505"},{"0":"3298","vim_version":"6","1":"6","script_version":"16","2":"16","version_comment":"fix small typo, that should also fix tags\n(automatically uploaded)","3":"fix small typo, that should also fix tags\n(automatically uploaded)","package":"vim_faq-16.vba","4":"vim_faq-16.vba","src_id":"14420","5":"14420","creation_date":"1291362177","6":"1291362177"},{"0":"3298","vim_version":"6","1":"6","script_version":"14","2":"14","version_comment":"\n(automatically uploaded)","3":"\n(automatically uploaded)","package":"vim_faq-14.vba","4":"vim_faq-14.vba","src_id":"14406","5":"14406","creation_date":"1291144532","6":"1291144532"},{"0":"3298","vim_version":"6","1":"6","script_version":"12","2":"12","version_comment":"many small typo fixes (Dominique Pelle, thanks!)\nEnabled GLVS (see :h GLVS)\n(automatically uploaded)","3":"many small typo fixes (Dominique Pelle, thanks!)\nEnabled GLVS (see :h GLVS)\n(automatically uploaded)","package":"vim_faq-12.vba","4":"vim_faq-12.vba","src_id":"14128","5":"14128","creation_date":"1288130190","6":"1288130190"},{"0":"3298","vim_version":"7.0","1":"7.0","script_version":"11","2":"11","version_comment":"Initial upload","3":"Initial upload","package":"vim_faq.vba","4":"vim_faq.vba","src_id":"14125","5":"14125","creation_date":"1288125824","6":"1288125824"}]},"3297":{"script_id":"3297","0":"3297","script_name":"sjump.vim","1":"sjump.vim","script_type":"utility","2":"utility","summary":"Display labels in the sign area and jump to selected label","3":"Display labels in the sign area and jump to selected label","description":"When executed the plugin will display labels in the sign area and wait\r\nfor the user to enter a label. Then it will jump to the line with the\r\nentered label and hide the labels (by removing the signs).\r\n\r\nThe plugin is mapped to the sequence gl (Goto Line). The mapping can\r\nbe disabled with:\r\n   let g:sjump_enable_keymap = 0\r\n\r\nTo put the mapping on another key:\r\n   nmap <F9> :call sjump#JumpToLabel()<cr>\r\n\r\nMore configuration options are in help (:help sjump).\r\n\r\nRequires: +signs\r\nUse :version to see if +signs is enabled.","4":"When executed the plugin will display labels in the sign area and wait\r\nfor the user to enter a label. Then it will jump to the line with the\r\nentered label and hide the labels (by removing the signs).\r\n\r\nThe plugin is mapped to the sequence gl (Goto Line). The mapping can\r\nbe disabled with:\r\n   let g:sjump_enable_keymap = 0\r\n\r\nTo put the mapping on another key:\r\n   nmap <F9> :call sjump#JumpToLabel()<cr>\r\n\r\nMore configuration options are in help (:help sjump).\r\n\r\nRequires: +signs\r\nUse :version to see if +signs is enabled.","install_details":"Unpack into vim runtime directory (eg. ~\/.vim\/).\r\n\r\nTo generate the help tags open the installed file doc\/sjump.txt in Vim and execute\r\n   :helptags %:p:h","5":"Unpack into vim runtime directory (eg. ~\/.vim\/).\r\n\r\nTo generate the help tags open the installed file doc\/sjump.txt in Vim and execute\r\n   :helptags %:p:h","first_name":"Marko","6":"Marko","last_name":"Mahni\u010d","7":"Mahnič","releases":[{"0":"3297","vim_version":"7.0","1":"7.0","script_version":"0.5.1","2":"0.5.1","version_comment":"* Jump to label with 2 chars didn't work (reported by Jun Yamagiwa)\r\n* Invalid entries caused an error","3":"* Jump to label with 2 chars didn't work (reported by Jun Yamagiwa)\r\n* Invalid entries caused an error","package":"sjump.zip","4":"sjump.zip","src_id":"14133","5":"14133","creation_date":"1288163328","6":"1288163328"},{"0":"3297","vim_version":"7.2","1":"7.2","script_version":"0.5","2":"0.5","version_comment":"Initial upload","3":"Initial upload","package":"sjump.zip","4":"sjump.zip","src_id":"14124","5":"14124","creation_date":"1288120589","6":"1288120589"}]},"3296":{"script_id":"3296","0":"3296","script_name":"idp.vim","1":"idp.vim","script_type":"syntax","2":"syntax","summary":"Syntax file for IDP","3":"Syntax file for IDP","description":"This is a very basic syntax file for the IDP language (http:\/\/dtai.cs.kuleuven.be\/krr\/software\/idp)\r\n","4":"This is a very basic syntax file for the IDP language (http:\/\/dtai.cs.kuleuven.be\/krr\/software\/idp)\r\n","install_details":"* Install the script by simply placing it in the .vim\/syntax directory\r\n* To automatically apply this to .idp files add the following to filetype.vim\r\nau BufRead,BufNewFile *.idp setfiletype idp \r\n","5":"* Install the script by simply placing it in the .vim\/syntax directory\r\n* To automatically apply this to .idp files add the following to filetype.vim\r\nau BufRead,BufNewFile *.idp setfiletype idp \r\n","first_name":"Adriaan","6":"Adriaan","last_name":"Larmuseau","7":"Larmuseau","releases":[{"0":"3296","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"idp.vim","4":"idp.vim","src_id":"14120","5":"14120","creation_date":"1288042963","6":"1288042963"}]},"3295":{"script_id":"3295","0":"3295","script_name":"toggle_option","1":"toggle_option","script_type":"utility","2":"utility","summary":"Initial upload","3":"Initial upload","description":"This script provides a very small utility to toggle an option or a variable with an unified syntax. This can be useful when writing scripts.\r\n\r\nUsage:\r\n\r\n:Toggle <my-options>\r\n\r\nexample\r\n\r\n:Toggle paste\r\n:Toggle paste spell\r\n:let g:my_variable=0\r\n:Toggle g:my_variable","4":"This script provides a very small utility to toggle an option or a variable with an unified syntax. This can be useful when writing scripts.\r\n\r\nUsage:\r\n\r\n:Toggle <my-options>\r\n\r\nexample\r\n\r\n:Toggle paste\r\n:Toggle paste spell\r\n:let g:my_variable=0\r\n:Toggle g:my_variable","install_details":"Just put this script in your .vim\/plugin\/ directory","5":"Just put this script in your .vim\/plugin\/ directory","first_name":"Christophe-Marie","6":"Christophe-Marie","last_name":"Duquesne","7":"Duquesne","releases":[{"0":"3295","vim_version":"7.0","1":"7.0","script_version":"0.0.2","2":"0.0.2","version_comment":"Improved the script thanks to Salman Halim","3":"Improved the script thanks to Salman Halim","package":"toggle_option.vim","4":"toggle_option.vim","src_id":"14135","5":"14135","creation_date":"1288192753","6":"1288192753"},{"0":"3295","vim_version":"7.0","1":"7.0","script_version":"0.0.1","2":"0.0.1","version_comment":"Initial upload","3":"Initial upload","package":"toggle_option.vim","4":"toggle_option.vim","src_id":"14116","5":"14116","creation_date":"1288015123","6":"1288015123"}]},"3294":{"script_id":"3294","0":"3294","script_name":"grass.vim","1":"grass.vim","script_type":"syntax","2":"syntax","summary":"syntax file for grass","3":"syntax file for grass","description":"syntax file for grass (http:\/\/www.blue.sky.or.jp\/grass\/doc_ja.html).\r\nrepository: http:\/\/github.com\/tyru\/grass.vim\r\n\r\nsample:\r\n無限に草植えときますねｗＷＷｗｗｗｗＷＷｗｗ\r\n\r\nＹコンビネータｗｗＷＷｗｗＷｗｗｖちょｗｗＷＷＷｗＷＷＷｗｖおまｗＷＷｗＷｗｖ\r\n\r\nｗｗｗｗｖｗｖｗｗＷＷｗｖｗｗＷｗｗｖｗｗｗｗＷＷＷｗｗＷｗｗＷＷＷＷＷＷｗｗｗｗＷｗ\r\nｗｖｗＷＷｗＷｗｗｖｗＷＷＷｗｗｗｗｗＷｗｗｗｗｗｗＷＷｗＷＷＷｗＷＷＷＷＷＷｗＷ\r\nＷＷＷＷＷＷＷｗｗｗＷｗｗＷＷＷＷＷＷＷＷＷＷｗＷｗｗｗｗｗＷＷＷＷＷＷＷＷ\r\nＷＷＷｗｗｗｗｗＷＷＷＷＷＷＷＷＷＷＷＷｗｗｗｗＷＷＷＷＷＷＷＷＷＷＷＷＷ\r\nｗｗｗＷＷＷＷＷＷＷＷＷＷＷＷＷＷｗｗｗＷＷＷＷＷＷＷＷＷＷＷＷＷＷＷｗＷ\r\nＷＷＷＷＷＷＷＷＷＷＷＷＷＷＷＷＷｗｗｗＷｗｗｗｗｗｗｗｗｗｗｗｗｗｗＷＷＷＷ\r\nＷＷＷＷＷＷＷＷＷＷＷＷＷＷＷｗｗｗｗｗｗｗｗＷｗｗＷＷＷＷＷＷＷＷＷＷＷ\r\nＷＷＷＷＷＷＷＷＷＷＷＷＷｗｗｗｗｗｗｗｗｗｗｗｗｗｗｗｗｗｗｗｗｗｗｗｗＷｗｗｗｗ\r\nｗｗｗｗｗｗｗｗｗｗｗｗｗｗｗｗｗ　　　　　　　　　　　　　ｗｗｗｗｗｗｗｗＷＷｗｗｗｗｗｗｗ\r\nｗｗｗｗｗｗｗｗｗｗｗｗｗｗｗｗｗ　　　　　　　 　 は　　 ｗｗｗｗｗＷＷＷＷＷＷＷＷＷＷ\r\nＷＷＷＷＷｗＷｗｗｗＷＷＷＷ　　　　わ　　　い　　 ＷＷＷＷＷＷＷｗｗｗＷｗｗＷＷ\r\nＷＷＷＷＷＷＷＷＷＷｗｗｗｗ　　　　ろ　　　は　　  ｗＷｗｗｗｗｗｗｗＷＷＷＷＷＷＷ\r\nＷＷＷＷＷＷＷＷＷＷｗｗｗｗ　　　　す　　　い　　　ｗｗｗＷｗｗＷＷＷＷＷＷＷＷＷ\r\nＷＷＷＷＷＷＷＷＷｗｗｗｗｗ　　　　 わ　　　　　　　ｗｗｗｗＷｗｗＷＷＷＷＷＷＷＷ\r\nＷＷＷＷＷＷＷＷＷＷＷＷＷ　　　　ろ　　　　　　　ＷＷＷＷＷＷＷＷＷｗｗｗｗｗｗ\r\nｗｗｗｗｗＷｗｗＷＷＷＷＷＷＷ　　　 す　　　　　　　ＷＷＷＷＷＷＷＷＷｗｗｗｗｗｗ\r\nｗｗｗｗｗｗｗＷｗｗｗｗｗｗｗｗｗ　　　　　　　　　　　　 ｗｗｗｗｗｗＷＷＷＷＷＷＷＷＷ\r\nＷＷＷＷＷＷＷＷｗｗｗｗｗｗｗｗｗｗｗｗｗｗｗｗｗｗｗｗｗｗｗｗｗｗｗｗｗｗｗｗｗｗｗｗｗ\r\nｗｗｗｗｗｗＷｗｗｗｗｗｗｗｗｗｗｗｗｗｗＷＷｗｗｗｗｗｗｗｗｗＷＷＷｗｗＷＷＷＷｗｗｗ\r\nｗｗｗｗｗｗｗｗｗｗｗｗＷＷＷＷＷｗｗＷＷＷＷＷＷｗｗｗｗＷＷＷＷＷＷＷｗｗＷＷＷ\r\nＷＷＷＷＷｗｗｗｗＷＷＷＷＷＷＷＷＷｗｗＷＷＷＷＷＷＷＷＷＷｗｗｗｗｗｗｗｗｗ\r\nｗｗｗｗＷＷＷＷＷＷＷＷＷＷＷＷＷＷＷＷＷＷＷＷＷＷＷＷＷＷＷＷｗｗｗｗｗｗ\r\nｗｗｗｗｗＷｗｗｗＷＷｗｗｗｗｗｗｗｗｗｗｗｗｗｗｗｗｗｗＷＷＷｗｗＷＷＷＷｗｗｗｗｗｗ\r\nｗｗｗｗｗｗｗｗｗｗｗｗｗｗｗｗｗｗＷＷＷＷＷｗｗＷＷＷＷＷＷｗｗｗｗｗｗｗＷＷＷＷ\r\nＷＷＷｗｗＷＷＷＷＷＷＷＷｗｗｗｗｗｗＷＷＷＷＷＷＷＷＷｗｗＷＷＷＷＷＷＷＷ\r\nＷＷｗｗｗｗｗｗＷＷＷＷＷＷＷＷＷＷＷｗｗｗｗｗｗｗｗｗｗｗｗｗｗｗｗｗｗｗｗｗｗｗ","4":"syntax file for grass (http:\/\/www.blue.sky.or.jp\/grass\/doc_ja.html).\r\nrepository: http:\/\/github.com\/tyru\/grass.vim\r\n\r\nsample:\r\n無限に草植えときますねｗＷＷｗｗｗｗＷＷｗｗ\r\n\r\nＹコンビネータｗｗＷＷｗｗＷｗｗｖちょｗｗＷＷＷｗＷＷＷｗｖおまｗＷＷｗＷｗｖ\r\n\r\nｗｗｗｗｖｗｖｗｗＷＷｗｖｗｗＷｗｗｖｗｗｗｗＷＷＷｗｗＷｗｗＷＷＷＷＷＷｗｗｗｗＷｗ\r\nｗｖｗＷＷｗＷｗｗｖｗＷＷＷｗｗｗｗｗＷｗｗｗｗｗｗＷＷｗＷＷＷｗＷＷＷＷＷＷｗＷ\r\nＷＷＷＷＷＷＷｗｗｗＷｗｗＷＷＷＷＷＷＷＷＷＷｗＷｗｗｗｗｗＷＷＷＷＷＷＷＷ\r\nＷＷＷｗｗｗｗｗＷＷＷＷＷＷＷＷＷＷＷＷｗｗｗｗＷＷＷＷＷＷＷＷＷＷＷＷＷ\r\nｗｗｗＷＷＷＷＷＷＷＷＷＷＷＷＷＷｗｗｗＷＷＷＷＷＷＷＷＷＷＷＷＷＷＷｗＷ\r\nＷＷＷＷＷＷＷＷＷＷＷＷＷＷＷＷＷｗｗｗＷｗｗｗｗｗｗｗｗｗｗｗｗｗｗＷＷＷＷ\r\nＷＷＷＷＷＷＷＷＷＷＷＷＷＷＷｗｗｗｗｗｗｗｗＷｗｗＷＷＷＷＷＷＷＷＷＷＷ\r\nＷＷＷＷＷＷＷＷＷＷＷＷＷｗｗｗｗｗｗｗｗｗｗｗｗｗｗｗｗｗｗｗｗｗｗｗｗＷｗｗｗｗ\r\nｗｗｗｗｗｗｗｗｗｗｗｗｗｗｗｗｗ　　　　　　　　　　　　　ｗｗｗｗｗｗｗｗＷＷｗｗｗｗｗｗｗ\r\nｗｗｗｗｗｗｗｗｗｗｗｗｗｗｗｗｗ　　　　　　　 　 は　　 ｗｗｗｗｗＷＷＷＷＷＷＷＷＷＷ\r\nＷＷＷＷＷｗＷｗｗｗＷＷＷＷ　　　　わ　　　い　　 ＷＷＷＷＷＷＷｗｗｗＷｗｗＷＷ\r\nＷＷＷＷＷＷＷＷＷＷｗｗｗｗ　　　　ろ　　　は　　  ｗＷｗｗｗｗｗｗｗＷＷＷＷＷＷＷ\r\nＷＷＷＷＷＷＷＷＷＷｗｗｗｗ　　　　す　　　い　　　ｗｗｗＷｗｗＷＷＷＷＷＷＷＷＷ\r\nＷＷＷＷＷＷＷＷＷｗｗｗｗｗ　　　　 わ　　　　　　　ｗｗｗｗＷｗｗＷＷＷＷＷＷＷＷ\r\nＷＷＷＷＷＷＷＷＷＷＷＷＷ　　　　ろ　　　　　　　ＷＷＷＷＷＷＷＷＷｗｗｗｗｗｗ\r\nｗｗｗｗｗＷｗｗＷＷＷＷＷＷＷ　　　 す　　　　　　　ＷＷＷＷＷＷＷＷＷｗｗｗｗｗｗ\r\nｗｗｗｗｗｗｗＷｗｗｗｗｗｗｗｗｗ　　　　　　　　　　　　 ｗｗｗｗｗｗＷＷＷＷＷＷＷＷＷ\r\nＷＷＷＷＷＷＷＷｗｗｗｗｗｗｗｗｗｗｗｗｗｗｗｗｗｗｗｗｗｗｗｗｗｗｗｗｗｗｗｗｗｗｗｗｗ\r\nｗｗｗｗｗｗＷｗｗｗｗｗｗｗｗｗｗｗｗｗｗＷＷｗｗｗｗｗｗｗｗｗＷＷＷｗｗＷＷＷＷｗｗｗ\r\nｗｗｗｗｗｗｗｗｗｗｗｗＷＷＷＷＷｗｗＷＷＷＷＷＷｗｗｗｗＷＷＷＷＷＷＷｗｗＷＷＷ\r\nＷＷＷＷＷｗｗｗｗＷＷＷＷＷＷＷＷＷｗｗＷＷＷＷＷＷＷＷＷＷｗｗｗｗｗｗｗｗｗ\r\nｗｗｗｗＷＷＷＷＷＷＷＷＷＷＷＷＷＷＷＷＷＷＷＷＷＷＷＷＷＷＷＷｗｗｗｗｗｗ\r\nｗｗｗｗｗＷｗｗｗＷＷｗｗｗｗｗｗｗｗｗｗｗｗｗｗｗｗｗｗＷＷＷｗｗＷＷＷＷｗｗｗｗｗｗ\r\nｗｗｗｗｗｗｗｗｗｗｗｗｗｗｗｗｗｗＷＷＷＷＷｗｗＷＷＷＷＷＷｗｗｗｗｗｗｗＷＷＷＷ\r\nＷＷＷｗｗＷＷＷＷＷＷＷＷｗｗｗｗｗｗＷＷＷＷＷＷＷＷＷｗｗＷＷＷＷＷＷＷＷ\r\nＷＷｗｗｗｗｗｗＷＷＷＷＷＷＷＷＷＷＷｗｗｗｗｗｗｗｗｗｗｗｗｗｗｗｗｗｗｗｗｗｗｗ","install_details":"","5":"","first_name":"tyru","6":"tyru","last_name":" ","7":" ","releases":[{"0":"3294","vim_version":"7.0","1":"7.0","script_version":"0.0.0","2":"0.0.0","version_comment":"Initial upload","3":"Initial upload","package":"grass.vim","4":"grass.vim","src_id":"14113","5":"14113","creation_date":"1287968231","6":"1287968231"}]},"3293":{"script_id":"3293","0":"3293","script_name":"numbered.vim","1":"numbered.vim","script_type":"utility","2":"utility","summary":"Number items in a list.","3":"Number items in a list.","description":":help numbered","4":":help numbered","install_details":"Extract to ~\/.vim","5":"Extract to ~\/.vim","first_name":"Jeremy","6":"Jeremy","last_name":"Cantrell","7":"Cantrell","releases":[{"0":"3293","vim_version":"7.0","1":"7.0","script_version":"0.2","2":"0.2","version_comment":"Minor changes","3":"Minor changes","package":"jmcantrell-vim-numbered-77b2d32.zip","4":"jmcantrell-vim-numbered-77b2d32.zip","src_id":"15172","5":"15172","creation_date":"1299561004","6":"1299561004"},{"0":"3293","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"vim-numbered-293dd77f3b0a1a7315c4402ab96a591513704215.tar.gz","4":"vim-numbered-293dd77f3b0a1a7315c4402ab96a591513704215.tar.gz","src_id":"14112","5":"14112","creation_date":"1287948184","6":"1287948184"}]},"3292":{"script_id":"3292","0":"3292","script_name":"southernlights","1":"southernlights","script_type":"color scheme","2":"color scheme","summary":"A 256 colors scheme","3":"A 256 colors scheme","description":"A 256 colors scheme with identical colors in both Vim and GVim.\r\nNote: The colors are identical only if the terminal was set to use XTerm color scheme.\r\n\r\ndevelopment: https:\/\/github.com\/jalvesaq\/southernlights","4":"A 256 colors scheme with identical colors in both Vim and GVim.\r\nNote: The colors are identical only if the terminal was set to use XTerm color scheme.\r\n\r\ndevelopment: https:\/\/github.com\/jalvesaq\/southernlights","install_details":"copy southernlights.vim to either ~\/.vim\/colors (on Linux\/Unix) or ~\/vimfiles\/colors (on Windows).\r\n\r\nPut in your vimrc:\r\n\r\ncolorscheme southernlights","5":"copy southernlights.vim to either ~\/.vim\/colors (on Linux\/Unix) or ~\/vimfiles\/colors (on Windows).\r\n\r\nPut in your vimrc:\r\n\r\ncolorscheme southernlights","first_name":"Jakson","6":"Jakson","last_name":"Aquino","7":"Aquino","releases":[{"0":"3292","vim_version":"7.4","1":"7.4","script_version":"0.7","2":"0.7","version_comment":"Added highlight options for FoldColumn, MoreMsg, ModeMsg, DiffAdd, DiffDelete, DiffChange, DiffText, Question, SpellCap, VisualNOS, WildMenu, IncSearch, VimCommentTitle, VimCommentString and rOKeyword.","3":"Added highlight options for FoldColumn, MoreMsg, ModeMsg, DiffAdd, DiffDelete, DiffChange, DiffText, Question, SpellCap, VisualNOS, WildMenu, IncSearch, VimCommentTitle, VimCommentString and rOKeyword.","package":"southernlights.vim","4":"southernlights.vim","src_id":"23667","5":"23667","creation_date":"1444661921","6":"1444661921"},{"0":"3292","vim_version":"7.4","1":"7.4","script_version":"0.6","2":"0.6","version_comment":"Improve 8 colors scheme.","3":"Improve 8 colors scheme.","package":"southernlights.vim","4":"southernlights.vim","src_id":"22119","5":"22119","creation_date":"1404322195","6":"1404322195"},{"0":"3292","vim_version":"7.0","1":"7.0","script_version":"0.5","2":"0.5","version_comment":"* Fix background color on GVim 7.4 on Windows.","3":"* Fix background color on GVim 7.4 on Windows.","package":"southernlights.vim","4":"southernlights.vim","src_id":"21177","5":"21177","creation_date":"1386546696","6":"1386546696"},{"0":"3292","vim_version":"7.0","1":"7.0","script_version":"0.4","2":"0.4","version_comment":"Minor changes.","3":"Minor changes.","package":"southernlights.vim","4":"southernlights.vim","src_id":"20839","5":"20839","creation_date":"1380026514","6":"1380026514"},{"0":"3292","vim_version":"7.3","1":"7.3","script_version":"0.3","2":"0.3","version_comment":"* Avoid the use of color by name because each terminal emulator define them differently.","3":"* Avoid the use of color by name because each terminal emulator define them differently.","package":"southernlights.vim","4":"southernlights.vim","src_id":"18800","5":"18800","creation_date":"1350153054","6":"1350153054"},{"0":"3292","vim_version":"7.0","1":"7.0","script_version":"0.2","2":"0.2","version_comment":"Support to 8 colors scheme (Linux Console).","3":"Support to 8 colors scheme (Linux Console).","package":"southernlights.vim","4":"southernlights.vim","src_id":"15508","5":"15508","creation_date":"1303526613","6":"1303526613"},{"0":"3292","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"southernlights.vim","4":"southernlights.vim","src_id":"14108","5":"14108","creation_date":"1287931879","6":"1287931879"}]},"3291":{"script_id":"3291","0":"3291","script_name":"openurl.vim","1":"openurl.vim","script_type":"utility","2":"utility","summary":"open a url in a default browser","3":"open a url in a default browser","description":" Summary\r\n =======\r\n The OprnUrl function opens a url which is a first one in a line.\r\n\r\n Require\r\n =======\r\n You need a python interface.\r\n\r\n Usage\r\n =====\r\n If there is a line such that\r\n\r\n Sample line. http:\/\/aaa http:\/\/bbb\r\n\r\n You use ':OpenUrl' command in this line, \r\n then you can open http:\/\/aaa in a default web browser.\r\n\r\n\r\n\r\n I set a command for OpenUrl function, such that\r\n\r\n command OpenUrl :call OpenUrl()\r\n \r\n You can change command name by changing above command ame 'OpenUrl'.\r\n\r\n example)\r\n command AnotherOpenUrlName :call OpenUrl()\r\n","4":" Summary\r\n =======\r\n The OprnUrl function opens a url which is a first one in a line.\r\n\r\n Require\r\n =======\r\n You need a python interface.\r\n\r\n Usage\r\n =====\r\n If there is a line such that\r\n\r\n Sample line. http:\/\/aaa http:\/\/bbb\r\n\r\n You use ':OpenUrl' command in this line, \r\n then you can open http:\/\/aaa in a default web browser.\r\n\r\n\r\n\r\n I set a command for OpenUrl function, such that\r\n\r\n command OpenUrl :call OpenUrl()\r\n \r\n You can change command name by changing above command ame 'OpenUrl'.\r\n\r\n example)\r\n command AnotherOpenUrlName :call OpenUrl()\r\n","install_details":"1. Download openurl.vim\r\n2. Move the file to \r\n        HOME\/.vim\/plugin\/\r\n","5":"1. Download openurl.vim\r\n2. Move the file to \r\n        HOME\/.vim\/plugin\/\r\n","first_name":"Kenko","6":"Kenko","last_name":"Abe","7":"Abe","releases":[{"0":"3291","vim_version":"7.0","1":"7.0","script_version":"0.1.0","2":"0.1.0","version_comment":"Initial upload","3":"Initial upload","package":"openurl.vim","4":"openurl.vim","src_id":"14104","5":"14104","creation_date":"1287892731","6":"1287892731"}]},"3290":{"script_id":"3290","0":"3290","script_name":"RevealExtends","1":"RevealExtends","script_type":"utility","2":"utility","summary":"A plugin to reveal extended URLs from the buildout cache","3":"A plugin to reveal extended URLs from the buildout cache","description":"Developers can use zc.buildout to manage the build of a software project. It\r\nis most commonly used in the Zope and Plone world, but has been gaining\r\ntraction in other communities like Django.\r\n\r\nOne of the nice things about buildout is the ability to define the\r\nconfiguration via ini style files. You can extend a local file or a URL. In\r\nversion 1.4.0 of buildout, the option to cache the URL locally was added along\r\nwith the new download API.\r\n\r\nHere is an example: >\r\n\r\n    [buildout]\r\n    versions = versions\r\n    extends = \r\n       http:\/\/dist.example.org\/versions.cfg\r\n       versions.cfg\r\n\r\n>\r\n\r\nThis allows you to pull in a list of versions from example.org. If you have\r\nyour default.cfg setup to cache the URL then you could find that file\r\nmanually. This requires that you know the md5 hash of the URL string. Not the\r\nmost convenient way to find the file. This is where the plugin comes in\r\nhandy.\r\n\r\nThe plugin allows you to use the current line, a visual selection or a string\r\npassed in to get the contents of the extended URL using the :RevealExtends command.\r\n\r\nSee the included docs for more information.\r\n\r\nPython support is required for retrieving the URL from the internet if it can't\r\nbe found in the cache.\r\n\r\nSee the code on github: http:\/\/github.com\/claytron\/RevealExtends","4":"Developers can use zc.buildout to manage the build of a software project. It\r\nis most commonly used in the Zope and Plone world, but has been gaining\r\ntraction in other communities like Django.\r\n\r\nOne of the nice things about buildout is the ability to define the\r\nconfiguration via ini style files. You can extend a local file or a URL. In\r\nversion 1.4.0 of buildout, the option to cache the URL locally was added along\r\nwith the new download API.\r\n\r\nHere is an example: >\r\n\r\n    [buildout]\r\n    versions = versions\r\n    extends = \r\n       http:\/\/dist.example.org\/versions.cfg\r\n       versions.cfg\r\n\r\n>\r\n\r\nThis allows you to pull in a list of versions from example.org. If you have\r\nyour default.cfg setup to cache the URL then you could find that file\r\nmanually. This requires that you know the md5 hash of the URL string. Not the\r\nmost convenient way to find the file. This is where the plugin comes in\r\nhandy.\r\n\r\nThe plugin allows you to use the current line, a visual selection or a string\r\npassed in to get the contents of the extended URL using the :RevealExtends command.\r\n\r\nSee the included docs for more information.\r\n\r\nPython support is required for retrieving the URL from the internet if it can't\r\nbe found in the cache.\r\n\r\nSee the code on github: http:\/\/github.com\/claytron\/RevealExtends","install_details":"Use pathogen (vimscript #2332) for easiest install experience.\r\n\r\nOtherwise, place RevealExtends.vim into your ~\/.vim\/plugin folder and the accompanying RevealExtends.txt into your ~\/.vim\/doc folder.\r\n\r\nThen run :helptags ~\/.vim\/doc to get the help doc into vim.","5":"Use pathogen (vimscript #2332) for easiest install experience.\r\n\r\nOtherwise, place RevealExtends.vim into your ~\/.vim\/plugin folder and the accompanying RevealExtends.txt into your ~\/.vim\/doc folder.\r\n\r\nThen run :helptags ~\/.vim\/doc to get the help doc into vim.","first_name":"Clayton","6":"Clayton","last_name":"Parker","7":"Parker","releases":[{"0":"3290","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"RevealExtends-1.0.zip","4":"RevealExtends-1.0.zip","src_id":"14101","5":"14101","creation_date":"1287765302","6":"1287765302"}]},"3289":{"script_id":"3289","0":"3289","script_name":"pf_earth.vim","1":"pf_earth.vim","script_type":"color scheme","2":"color scheme","summary":"Dark, Earthy Color Scheme","3":"Dark, Earthy Color Scheme","description":"This was originally based on the textmate krTheme.  It is heavily modified though.  It looks quite nice while coding in Ruby\/C\/C++.  ","4":"This was originally based on the textmate krTheme.  It is heavily modified though.  It looks quite nice while coding in Ruby\/C\/C++.  ","install_details":"Just drop into ~\/.vim\/colors.","5":"Just drop into ~\/.vim\/colors.","first_name":"Chad","6":"Chad","last_name":"Gulley","7":"Gulley","releases":[{"0":"3289","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"pf_earth.vim","4":"pf_earth.vim","src_id":"14099","5":"14099","creation_date":"1287715657","6":"1287715657"}]},"3288":{"script_id":"3288","0":"3288","script_name":"newsprint.vim","1":"newsprint.vim","script_type":"color scheme","2":"color scheme","summary":"A (pleasant) monochromatic color scheme for Vim","3":"A (pleasant) monochromatic color scheme for Vim","description":"newsprint.vim is a (pleasant) monochromatic color scheme ideal for simulating a black and white terminal from a color terminal or GUI. This color scheme is intended for black on white display.","4":"newsprint.vim is a (pleasant) monochromatic color scheme ideal for simulating a black and white terminal from a color terminal or GUI. This color scheme is intended for black on white display.","install_details":"","5":"","first_name":"Steven","6":"Steven","last_name":"Stallion","7":"Stallion","releases":[{"0":"3288","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"newsprint.vim","4":"newsprint.vim","src_id":"24449","5":"24449","creation_date":"1471299212","6":"1471299212"}]},"3287":{"script_id":"3287","0":"3287","script_name":"Show man\/dict\/perldoc\/pydoc\/phpdoc use K","1":"Show man\/dict\/perldoc\/pydoc\/phpdoc use K","script_type":"utility","2":"utility","summary":"Show man","3":"Show man","description":"Show man\/dict\/perldoc\/pydoc\/phpdoc use K Y","4":"Show man\/dict\/perldoc\/pydoc\/phpdoc use K Y","install_details":"","5":"","first_name":"su","6":"su","last_name":"su","7":"su","releases":[{"0":"3287","vim_version":"7.0","1":"7.0","script_version":"1.0 ","2":"1.0 ","version_comment":"Initial upload","3":"Initial upload","package":"man_it.vim","4":"man_it.vim","src_id":"14092","5":"14092","creation_date":"1287670874","6":"1287670874"}]},"3286":{"script_id":"3286","0":"3286","script_name":"Lite Tab Page","1":"Lite Tab Page","script_type":"utility","2":"utility","summary":"A Tab Page extension plugin","3":"A Tab Page extension plugin","description":"Use the built-in Tab Pages of VIM 7.0 to replace \"TabBar \/ BufferExplorer \/ MiniExplorer\", no multi-window conflicts\/issues any more!\r\n\r\nScreenshot: http:\/\/ayuanx.files.wordpress.com\/2010\/10\/litetablabel.jpg\r\n\r\n This is a simple plugin, which makes VIM Tab Page functions more user-friendly. \r\n\r\n <> Features:\r\n 1. \":E filename\"\t\t\t        Open the file in a new tab page instead of in current window.\r\n\r\n 2. \"<Alt-1>, <Alt-2> to <Alt-0>\"\tSwitch to tab page 1\/2\/3\/4\/5\/6\/7\/8\/9\/10.\r\n\r\n 3. \"<Alt-h> \/ <Alt-l>\"\t\t        Switch to previous\/next tab page.\r\n\r\n 4. \"<Alt-H> \/ <Alt-L>\"\t\t        Move current tab page left\/right.\r\n\r\n 5. Show GUI Tab Labels in format: \"[Tab Number]:[+][Buffer Name]\"\r\n \tPS: [+] stands for one or more buffer in that tab page has been modified.\r\n\r\n <> Feedback:\r\n    You are always encouraged to modify this plugin freely to suit your own needs!\r\n","4":"Use the built-in Tab Pages of VIM 7.0 to replace \"TabBar \/ BufferExplorer \/ MiniExplorer\", no multi-window conflicts\/issues any more!\r\n\r\nScreenshot: http:\/\/ayuanx.files.wordpress.com\/2010\/10\/litetablabel.jpg\r\n\r\n This is a simple plugin, which makes VIM Tab Page functions more user-friendly. \r\n\r\n <> Features:\r\n 1. \":E filename\"\t\t\t        Open the file in a new tab page instead of in current window.\r\n\r\n 2. \"<Alt-1>, <Alt-2> to <Alt-0>\"\tSwitch to tab page 1\/2\/3\/4\/5\/6\/7\/8\/9\/10.\r\n\r\n 3. \"<Alt-h> \/ <Alt-l>\"\t\t        Switch to previous\/next tab page.\r\n\r\n 4. \"<Alt-H> \/ <Alt-L>\"\t\t        Move current tab page left\/right.\r\n\r\n 5. Show GUI Tab Labels in format: \"[Tab Number]:[+][Buffer Name]\"\r\n \tPS: [+] stands for one or more buffer in that tab page has been modified.\r\n\r\n <> Feedback:\r\n    You are always encouraged to modify this plugin freely to suit your own needs!\r\n","install_details":"Simply put \"LiteTabPage.vim\" into path \"~\/.vim\/plugin\/\" (*nix) or \"$VIM\/vimfiles\/plugin\/\" (Windows).","5":"Simply put \"LiteTabPage.vim\" into path \"~\/.vim\/plugin\/\" (*nix) or \"$VIM\/vimfiles\/plugin\/\" (Windows).","first_name":"AyuanX","6":"AyuanX","last_name":" ","7":" ","releases":[{"0":"3286","vim_version":"7.0","1":"7.0","script_version":"1.2","2":"1.2","version_comment":"Explicitly disable Alt key for menu in case it hasn't been done by user.","3":"Explicitly disable Alt key for menu in case it hasn't been done by user.","package":"LiteTabPage.vim","4":"LiteTabPage.vim","src_id":"14310","5":"14310","creation_date":"1290208457","6":"1290208457"},{"0":"3286","vim_version":"7.0","1":"7.0","script_version":"1.1","2":"1.1","version_comment":"Added shortcuts for quick moving tab pages.","3":"Added shortcuts for quick moving tab pages.","package":"LiteTabPage.vim","4":"LiteTabPage.vim","src_id":"14297","5":"14297","creation_date":"1290086151","6":"1290086151"},{"0":"3286","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"LiteTabPage.vim","4":"LiteTabPage.vim","src_id":"14091","5":"14091","creation_date":"1287661374","6":"1287661374"}]},"3285":{"script_id":"3285","0":"3285","script_name":"looks","1":"looks","script_type":"utility","2":"utility","summary":"Manage various looks\/settings of vim","3":"Manage various looks\/settings of vim","description":"This is a vim plugin I created for myself to help me manage various *looks* of vim. Each look is dictionary of settings and options that makes vim get a unique look.\r\n\r\nThese looks are defined in vimrc (or somewhere else but are source-d) like the following,\r\n\r\n    let g:looks = {}\r\n    let g:looks.dark = {\r\n        \\ '_map': \"d\",\r\n        \\ ':colorscheme': \"lucius\",\r\n        \\ '&guifont': \"Inconsolata\\\\ Medium\\\\ 15\",\r\n        \\ '&cursorline': 1\r\n        \\ }\r\n    let g:looks.light = { \":colorscheme\": \"tango\" }\r\n\r\nand the looks can be loaded with :Look command, like so\r\n\r\n    :Look dark\r\n\r\nTab completion is also available on the command line for all available looks.\r\n\r\nPlugin hosted over at bitbucket.org, https:\/\/bitbucket.org\/sharat87\/vim-looks\r\n\r\nFor more details, see \":h looks\".","4":"This is a vim plugin I created for myself to help me manage various *looks* of vim. Each look is dictionary of settings and options that makes vim get a unique look.\r\n\r\nThese looks are defined in vimrc (or somewhere else but are source-d) like the following,\r\n\r\n    let g:looks = {}\r\n    let g:looks.dark = {\r\n        \\ '_map': \"d\",\r\n        \\ ':colorscheme': \"lucius\",\r\n        \\ '&guifont': \"Inconsolata\\\\ Medium\\\\ 15\",\r\n        \\ '&cursorline': 1\r\n        \\ }\r\n    let g:looks.light = { \":colorscheme\": \"tango\" }\r\n\r\nand the looks can be loaded with :Look command, like so\r\n\r\n    :Look dark\r\n\r\nTab completion is also available on the command line for all available looks.\r\n\r\nPlugin hosted over at bitbucket.org, https:\/\/bitbucket.org\/sharat87\/vim-looks\r\n\r\nFor more details, see \":h looks\".","install_details":"Contains plugin\/looks.vim and doc\/looks.txt.\r\nPlace them in &rtp or make a folder in bundle directory if using pathogen.","5":"Contains plugin\/looks.vim and doc\/looks.txt.\r\nPlace them in &rtp or make a folder in bundle directory if using pathogen.","first_name":"Shrikant Sharat","6":"Shrikant Sharat","last_name":"Kandula","7":"Kandula","releases":[{"0":"3285","vim_version":"7.0","1":"7.0","script_version":"0.3","2":"0.3","version_comment":"Added support for virtually all options and settings in vim. Breaks compatibility with the way looks are defined in previous versions. Command keys need to be prefixed with `:` and options are to be prefixed with `&`.","3":"Added support for virtually all options and settings in vim. Breaks compatibility with the way looks are defined in previous versions. Command keys need to be prefixed with `:` and options are to be prefixed with `&`.","package":"looks.tar.gz","4":"looks.tar.gz","src_id":"14093","5":"14093","creation_date":"1287672950","6":"1287672950"},{"0":"3285","vim_version":"7.0","1":"7.0","script_version":"0.2","2":"0.2","version_comment":"Initial upload","3":"Initial upload","package":"looks.tar.gz","4":"looks.tar.gz","src_id":"14090","5":"14090","creation_date":"1287644477","6":"1287644477"}]},"3284":{"script_id":"3284","0":"3284","script_name":"Support for punctuation text objects","1":"Support for punctuation text objects","script_type":"utility","2":"utility","summary":"ci\/ da; vi@ yiq","3":"ci\/ da; vi@ yiq","description":"New punctuation text objects:\r\n\r\nci\/, di;, yi*, vi@ ...\r\nca\/, da;, ya*, va@ ...\r\n\r\nciq (or \"\") changes content inside ANY kind of quotes\r\nvaq, yiq ...\r\n\r\nci<space>, da<space> ... modify ANY punctuation pair\r\n\r\nDetailed help: https:\/\/github.com\/kurkale6ka\/vim-pairs","4":"New punctuation text objects:\r\n\r\nci\/, di;, yi*, vi@ ...\r\nca\/, da;, ya*, va@ ...\r\n\r\nciq (or \"\") changes content inside ANY kind of quotes\r\nvaq, yiq ...\r\n\r\nci<space>, da<space> ... modify ANY punctuation pair\r\n\r\nDetailed help: https:\/\/github.com\/kurkale6ka\/vim-pairs","install_details":"Use pathogen\r\n\r\nLatest version at:\r\nhttps:\/\/github.com\/kurkale6ka\/vim-pairs","5":"Use pathogen\r\n\r\nLatest version at:\r\nhttps:\/\/github.com\/kurkale6ka\/vim-pairs","first_name":"Dimitar","6":"Dimitar","last_name":"Dimitrov","7":"Dimitrov","releases":[{"0":"3284","vim_version":"7.0","1":"7.0","script_version":"3.1","2":"3.1","version_comment":"Allow customization of plugin mappings","3":"Allow customization of plugin mappings","package":"pairs.vim","4":"pairs.vim","src_id":"20664","5":"20664","creation_date":"1376667403","6":"1376667403"},{"0":"3284","vim_version":"7.0","1":"7.0","script_version":"3","2":"3","version_comment":"Complete rewrite, support for punctuation text objects","3":"Complete rewrite, support for punctuation text objects","package":"pairs.vim","4":"pairs.vim","src_id":"20663","5":"20663","creation_date":"1376651055","6":"1376651055"},{"0":"3284","vim_version":"7.0","1":"7.0","script_version":"2.1","2":"2.1","version_comment":"I had omitted to look for backticks while doing multiline searches","3":"I had omitted to look for backticks while doing multiline searches","package":"quotes.vim","4":"quotes.vim","src_id":"16645","5":"16645","creation_date":"1318194993","6":"1318194993"},{"0":"3284","vim_version":"7.0","1":"7.0","script_version":"2.0","2":"2.0","version_comment":"* Added support for backticks\r\n* Removed support for the repeat plugin (makes it more interactive)\r\n* Better algorithm","3":"* Added support for backticks\r\n* Removed support for the repeat plugin (makes it more interactive)\r\n* Better algorithm","package":"quotes.vim","4":"quotes.vim","src_id":"16642","5":"16642","creation_date":"1318155318","6":"1318155318"},{"0":"3284","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"quotes.vim","4":"quotes.vim","src_id":"14081","5":"14081","creation_date":"1287578630","6":"1287578630"}]},"3283":{"script_id":"3283","0":"3283","script_name":"OMNeT++4.x NED Syntax file","1":"OMNeT++4.x NED Syntax file","script_type":"syntax","2":"syntax","summary":"The script is a syntax file for OMNeT++ 4.x NED scripts","3":"The script is a syntax file for OMNeT++ 4.x NED scripts","description":"I find the syntax file for ned, but it is just for OMNeT++ 3.x network simulator and was not updated for a long time. Now, The OMNeT++ 4.x network simulator is released, I wish the ned.vim file can help users work easily.\r\n\r\nThe syntax file include:\r\n* highlight all functions keywords\r\n* highlight the number, float, double types and so on\r\n* highlight the properties(such as: @loose, @prompt, @unit and so on)\r\n* code folding\r\n    you can set this by edit the .vimrc, for examples \"let ned_fold=1\" or \"let ned_nofold_blocks=1\" or \"let ned_nofold_packages=1\"\r\n* highlight the document keywords, TODO, FIXME and so on\r\n\r\nmore information in the ned.vim, enjoy it.","4":"I find the syntax file for ned, but it is just for OMNeT++ 3.x network simulator and was not updated for a long time. Now, The OMNeT++ 4.x network simulator is released, I wish the ned.vim file can help users work easily.\r\n\r\nThe syntax file include:\r\n* highlight all functions keywords\r\n* highlight the number, float, double types and so on\r\n* highlight the properties(such as: @loose, @prompt, @unit and so on)\r\n* code folding\r\n    you can set this by edit the .vimrc, for examples \"let ned_fold=1\" or \"let ned_nofold_blocks=1\" or \"let ned_nofold_packages=1\"\r\n* highlight the document keywords, TODO, FIXME and so on\r\n\r\nmore information in the ned.vim, enjoy it.","install_details":"copy to ~\/.vim\/syntax (if there is not that directory, you can execute the command \"mkdir -p ~\/.vim\/syntax\")\r\nadd to your ~\/.vimrc: \r\n   au BufNewFile,BufRead *.ned set syntax=ned ","5":"copy to ~\/.vim\/syntax (if there is not that directory, you can execute the command \"mkdir -p ~\/.vim\/syntax\")\r\nadd to your ~\/.vimrc: \r\n   au BufNewFile,BufRead *.ned set syntax=ned ","first_name":"lei","6":"lei","last_name":"xue","7":"xue","releases":[{"0":"3283","vim_version":"7.0","1":"7.0","script_version":"0.2","2":"0.2","version_comment":"add \"package\" and \"inout\" syntax","3":"add \"package\" and \"inout\" syntax","package":"ned.vim","4":"ned.vim","src_id":"14381","5":"14381","creation_date":"1290781203","6":"1290781203"},{"0":"3283","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"ned.vim","4":"ned.vim","src_id":"14077","5":"14077","creation_date":"1287491701","6":"1287491701"}]},"3282":{"script_id":"3282","0":"3282","script_name":"eregex.vim","1":"eregex.vim","script_type":"utility","2":"utility","summary":"Perl\/Ruby style regular expression","3":"Perl\/Ruby style regular expression","description":"# Introduction\r\n\r\nhttp:\/\/vim.wikia.com\/wiki\/Perl_compatible_regular_expressions\r\n\r\nIn this tip. I introduced a plugin to help you use Perl style regular expression in Vim.\r\nBut the maintainer is disappear. And the default package is not easy to install.\r\nSo I start to maintain it.\r\n\r\nRepo: http:\/\/github.com\/othree\/eregex.vim\r\n\r\n\r\n## Quick Start\r\n\r\nAfter installed. Just press \/ or ? for search, it will map to :M command.\r\nYou can call eregex#toggle funtion to toggle the keymapping. For example, add the following line into your .vimrc file:\r\n\r\n    nnoremap <leader>\/ :call eregex#toggle()<CR>\r\n\r\nThen you can use <leader>\/ to toggle eregex.vim.\r\nFor replacement, use :%S\/\/ (uppercase S) to use perl style regexp.\r\n\r\nSee :help eregex for more information.\r\n\r\n## Config\r\n\r\nDefault disable, put this line in vimrc:\r\n\r\n    let g:eregex_default_enable = 0\r\n\r\nCustom search delimeter:\r\n\r\n    let g:eregex_forward_delim = '\/'\r\n    let g:eregex_backward_delim = '?'\r\n\r\n# Attribute\r\n\r\nAuthor : 安久津","4":"# Introduction\r\n\r\nhttp:\/\/vim.wikia.com\/wiki\/Perl_compatible_regular_expressions\r\n\r\nIn this tip. I introduced a plugin to help you use Perl style regular expression in Vim.\r\nBut the maintainer is disappear. And the default package is not easy to install.\r\nSo I start to maintain it.\r\n\r\nRepo: http:\/\/github.com\/othree\/eregex.vim\r\n\r\n\r\n## Quick Start\r\n\r\nAfter installed. Just press \/ or ? for search, it will map to :M command.\r\nYou can call eregex#toggle funtion to toggle the keymapping. For example, add the following line into your .vimrc file:\r\n\r\n    nnoremap <leader>\/ :call eregex#toggle()<CR>\r\n\r\nThen you can use <leader>\/ to toggle eregex.vim.\r\nFor replacement, use :%S\/\/ (uppercase S) to use perl style regexp.\r\n\r\nSee :help eregex for more information.\r\n\r\n## Config\r\n\r\nDefault disable, put this line in vimrc:\r\n\r\n    let g:eregex_default_enable = 0\r\n\r\nCustom search delimeter:\r\n\r\n    let g:eregex_forward_delim = '\/'\r\n    let g:eregex_backward_delim = '?'\r\n\r\n# Attribute\r\n\r\nAuthor : 安久津","install_details":"Use Vundle or pathogen is suggested.\r\n\r\nUse vimball package.\r\nOpen it with Vim and execute :so % .","5":"Use Vundle or pathogen is suggested.\r\n\r\nUse vimball package.\r\nOpen it with Vim and execute :so % .","first_name":"wei ko","6":"wei ko","last_name":"kao","7":"kao","releases":[{"0":"3282","vim_version":"7.0","1":"7.0","script_version":"2.60","2":"2.60","version_comment":"Support backword search.\r\nSupport count argument.\r\nUse function to auto map keys.\r\nDefine custom search delimeter.\r\nhlsearch works fine.","3":"Support backword search.\r\nSupport count argument.\r\nUse function to auto map keys.\r\nDefine custom search delimeter.\r\nhlsearch works fine.","package":"eregex.vim-2.60.vmb","4":"eregex.vim-2.60.vmb","src_id":"19567","5":"19567","creation_date":"1361705320","6":"1361705320"},{"0":"3282","vim_version":"7.0","1":"7.0","script_version":"2.56","2":"2.56","version_comment":"Update to correct vimball file","3":"Update to correct vimball file","package":"eregex.vim-2.56.vba","4":"eregex.vim-2.56.vba","src_id":"16152","5":"16152","creation_date":"1311759771","6":"1311759771"}]},"3281":{"script_id":"3281","0":"3281","script_name":"run_python_tests","1":"run_python_tests","script_type":"ftplugin","2":"ftplugin","summary":"Run Python unit tests asynchronously","3":"Run Python unit tests asynchronously","description":"Run Python Tests\r\n\r\n    http:\/\/bitbucket.org\/tartley\/vim_run_python_tests\r\n\r\n    Vim scripts to run Python unit tests.\r\n\r\n    Only currently tested on Vim 7.2 on Windows XP.\r\n    \r\n\r\nDESCRIPTION\r\n    \r\n    Provides key bindings to:\r\n\r\n    <Leader>a : toggles between the Python file in the current buffer and its unit tests.\r\n    F4 : Toggle the quickfix window open or closed.\r\n    F5 : Run the Python file in the current buffer\r\n           (i.e. run \"python dir\\subdir\\file.py\".)\r\n    F6 : Find & run the unit tests of the Python file in the current buffer\r\n           (i.e. find the unittest module as described below, then run \r\n           \"python -m unittest package.subpackage.module\"\r\n    F7 : Run the single test method under the cursor \r\n            (i.e. find the name of the test method the cursor is in, find its test class name, then run\r\n            \"python -m unittest --verbose package.subpackage.module.class.method\")\r\n\r\n    For F5, F6, & F7, you will want to check what Vim's current directory is. This will affect the path or sequence of packages used to reference your test module. Set the current directory in Vim using the :cd command. It should be set to the same directory that you'd have to be in to execute your tests from the command-line, which is generally your project root.\r\n\r\n    All running of files or tests is done asynchronously, so you can continue using Vim while it runs. When complete, the output is read into Vim's quickfix window.\r\n    \r\n    Alternatively, pressing Shift-F5, -F6, or -F7 will run the respective command in a new text terminal, which will remain open to display the results, and will automatically re-run the command whenever it detects changes to any file in or below the current directory.\r\n\r\n    When looking for the test module that corresponds to the current file, we search in the same dir, and in a bunch of likely-named subdirectories (e.g. 'test', 'tests', 'unittest', 'unittests') for a file of an likely-sounding test name. e.g. when 'widget.py' is the current buffer, we search for 'testwidget.py', 'test_widget.py', 'widget_tests.py', etc.\r\n\r\n\r\nTROUBLESHOOTING\r\n\r\n    Q) When I try to run tests, I see a traceback from unittest, such as: \"ImportError: No module named X\", or \"ValueError: Attempted relative import beyond toplevel package\"\r\n    A) Are you sure Vim's current working directory is correct?\r\n\r\n\r\nPYTHON TRACEBACKS IN THE VIM QUICKFIX WINDOW\r\n\r\n    The default value of Vim's errorformat variable for working with Python only shows one entry from each traceback, which seems unhelpful to me. To fix this, you can create a file ~\/.vim\/compiler\/pyunit, which contains just:\r\n\r\n        CompilerSet efm=\\%A\\ \\ File\\ \\\"%f\\\"\\\\,\\ line\\ %l\\\\,\\ %m,%C\\ %m,%Z\r\n\r\n    Now when you run the ':compiler pyunit' command (as run_python_tests does whenever you press F5, F6, or F7), Vim's quickfix window will display all the entries in each traceback.\r\n\r\n\r\nTODO\r\n\r\n    * Make it all work on Linux\r\n    * Instead of printing out status messages, can we prepend them to the output in the quickfix window?\r\n\r\n\r\nTHANKS\r\n\r\n    Pretty much all of this is stolen from various existing scripts at vim.org, or from my awesome colleagues at Resolver Systems.\r\n\r\n\r\nCONTACT\r\n\r\n    I know nothing about Vim scripting, so I'd love to hear about it if you have problems with this script, or ideas on how it could be better.\r\n\r\n    Jonathan Hartley, tartley@tartley.com\r\n","4":"Run Python Tests\r\n\r\n    http:\/\/bitbucket.org\/tartley\/vim_run_python_tests\r\n\r\n    Vim scripts to run Python unit tests.\r\n\r\n    Only currently tested on Vim 7.2 on Windows XP.\r\n    \r\n\r\nDESCRIPTION\r\n    \r\n    Provides key bindings to:\r\n\r\n    <Leader>a : toggles between the Python file in the current buffer and its unit tests.\r\n    F4 : Toggle the quickfix window open or closed.\r\n    F5 : Run the Python file in the current buffer\r\n           (i.e. run \"python dir\\subdir\\file.py\".)\r\n    F6 : Find & run the unit tests of the Python file in the current buffer\r\n           (i.e. find the unittest module as described below, then run \r\n           \"python -m unittest package.subpackage.module\"\r\n    F7 : Run the single test method under the cursor \r\n            (i.e. find the name of the test method the cursor is in, find its test class name, then run\r\n            \"python -m unittest --verbose package.subpackage.module.class.method\")\r\n\r\n    For F5, F6, & F7, you will want to check what Vim's current directory is. This will affect the path or sequence of packages used to reference your test module. Set the current directory in Vim using the :cd command. It should be set to the same directory that you'd have to be in to execute your tests from the command-line, which is generally your project root.\r\n\r\n    All running of files or tests is done asynchronously, so you can continue using Vim while it runs. When complete, the output is read into Vim's quickfix window.\r\n    \r\n    Alternatively, pressing Shift-F5, -F6, or -F7 will run the respective command in a new text terminal, which will remain open to display the results, and will automatically re-run the command whenever it detects changes to any file in or below the current directory.\r\n\r\n    When looking for the test module that corresponds to the current file, we search in the same dir, and in a bunch of likely-named subdirectories (e.g. 'test', 'tests', 'unittest', 'unittests') for a file of an likely-sounding test name. e.g. when 'widget.py' is the current buffer, we search for 'testwidget.py', 'test_widget.py', 'widget_tests.py', etc.\r\n\r\n\r\nTROUBLESHOOTING\r\n\r\n    Q) When I try to run tests, I see a traceback from unittest, such as: \"ImportError: No module named X\", or \"ValueError: Attempted relative import beyond toplevel package\"\r\n    A) Are you sure Vim's current working directory is correct?\r\n\r\n\r\nPYTHON TRACEBACKS IN THE VIM QUICKFIX WINDOW\r\n\r\n    The default value of Vim's errorformat variable for working with Python only shows one entry from each traceback, which seems unhelpful to me. To fix this, you can create a file ~\/.vim\/compiler\/pyunit, which contains just:\r\n\r\n        CompilerSet efm=\\%A\\ \\ File\\ \\\"%f\\\"\\\\,\\ line\\ %l\\\\,\\ %m,%C\\ %m,%Z\r\n\r\n    Now when you run the ':compiler pyunit' command (as run_python_tests does whenever you press F5, F6, or F7), Vim's quickfix window will display all the entries in each traceback.\r\n\r\n\r\nTODO\r\n\r\n    * Make it all work on Linux\r\n    * Instead of printing out status messages, can we prepend them to the output in the quickfix window?\r\n\r\n\r\nTHANKS\r\n\r\n    Pretty much all of this is stolen from various existing scripts at vim.org, or from my awesome colleagues at Resolver Systems.\r\n\r\n\r\nCONTACT\r\n\r\n    I know nothing about Vim scripting, so I'd love to hear about it if you have problems with this script, or ideas on how it could be better.\r\n\r\n    Jonathan Hartley, tartley@tartley.com\r\n","install_details":"    Unzip into your ~\/.vim folder. It should provide:\r\n\r\n    ~\/.vim\r\n        |-ftplugin\r\n           |-python\r\n              |-run_python_tests.vim\r\n              |-run_python_tests\r\n                 |-a bunch of files in here, including:\r\n                 |-README.txt\r\n\r\nIt defines some vimscript and Python functions, and then binds some keys to them.\r\n","5":"    Unzip into your ~\/.vim folder. It should provide:\r\n\r\n    ~\/.vim\r\n        |-ftplugin\r\n           |-python\r\n              |-run_python_tests.vim\r\n              |-run_python_tests\r\n                 |-a bunch of files in here, including:\r\n                 |-README.txt\r\n\r\nIt defines some vimscript and Python functions, and then binds some keys to them.\r\n","first_name":"jonathan","6":"jonathan","last_name":"hartley","7":"hartley","releases":[{"0":"3281","vim_version":"7.2","1":"7.2","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"run_python_tests_0.1.zip","4":"run_python_tests_0.1.zip","src_id":"14067","5":"14067","creation_date":"1287283530","6":"1287283530"}]},"3280":{"script_id":"3280","0":"3280","script_name":"Tabbi","1":"Tabbi","script_type":"utility","2":"utility","summary":"Aligns text as a table","3":"Aligns text as a table","description":"A simple vim plugin that aligns text separated with tabs or two or more whitespaces, so that each part starts in the same column as in the other lines. Similar as a table, but without lines.\r\n\r\nBefore:\r\npart one        part two     part three\r\n another part one              another part two    another part three\r\n\r\nAfter:\r\npart one                  part two                 part three\r\nanother part one    another part two   another part three\r\n\r\nUsage: to align the whole buffer, type :Tabbi, for aligning parts type e.g. :10,20Tabbi or use visual mode.\r\n\r\n\r\n\r\nWith the function Tabb(<pattern> [<trim> [,<separator]]) it is possible to format the selected lines.\r\n<pattern> is the pattern after which the lines should be formatted, \u00c2\u00a7x or \u00c2\u00a7x-y is replaced by the corresponding column. \u00c2\u00a7- can be used to align the lines like the :Tabbi command.\r\n<trim> is a boolean specifying if the parts are trimmed (default 0).\r\n<sep> is a string or regular expression that specifies the string separating the line into columns. The default is tabs or two or more whitespaces.\r\nSee the plugin file for more details.\r\n\r\nBefore:\r\npart one, part two  ,part three , part four, rest\r\none  , two , three\r\n\r\n-> select the lines and type :call Tabb(\"\u00c2\u00a72: \u00c2\u00a71\u00c2\u00a7- - \u00c2\u00a73-4\", 1, \",\")\r\n\r\nResult:\r\npart two: part one  - part three , part four\r\ntwo: one                  - three\r\n","4":"A simple vim plugin that aligns text separated with tabs or two or more whitespaces, so that each part starts in the same column as in the other lines. Similar as a table, but without lines.\r\n\r\nBefore:\r\npart one        part two     part three\r\n another part one              another part two    another part three\r\n\r\nAfter:\r\npart one                  part two                 part three\r\nanother part one    another part two   another part three\r\n\r\nUsage: to align the whole buffer, type :Tabbi, for aligning parts type e.g. :10,20Tabbi or use visual mode.\r\n\r\n\r\n\r\nWith the function Tabb(<pattern> [<trim> [,<separator]]) it is possible to format the selected lines.\r\n<pattern> is the pattern after which the lines should be formatted, \u00c2\u00a7x or \u00c2\u00a7x-y is replaced by the corresponding column. \u00c2\u00a7- can be used to align the lines like the :Tabbi command.\r\n<trim> is a boolean specifying if the parts are trimmed (default 0).\r\n<sep> is a string or regular expression that specifies the string separating the line into columns. The default is tabs or two or more whitespaces.\r\nSee the plugin file for more details.\r\n\r\nBefore:\r\npart one, part two  ,part three , part four, rest\r\none  , two , three\r\n\r\n-> select the lines and type :call Tabb(\"\u00c2\u00a72: \u00c2\u00a71\u00c2\u00a7- - \u00c2\u00a73-4\", 1, \",\")\r\n\r\nResult:\r\npart two: part one  - part three , part four\r\ntwo: one                  - three\r\n","install_details":"Put tabbi.vim in the plugin folder (e.g. ~\/.vim\/plugin\/).","5":"Put tabbi.vim in the plugin folder (e.g. ~\/.vim\/plugin\/).","first_name":"Daniel","6":"Daniel","last_name":"Schemala","7":"Schemala","releases":[{"0":"3280","vim_version":"7.0","1":"7.0","script_version":"1.2","2":"1.2","version_comment":"Whitespace at the beginning of the line are not pruned any more, and added a new formatting function.","3":"Whitespace at the beginning of the line are not pruned any more, and added a new formatting function.","package":"tabbi.vim","4":"tabbi.vim","src_id":"14334","5":"14334","creation_date":"1290299422","6":"1290299422"},{"0":"3280","vim_version":"6.0","1":"6.0","script_version":"1.1","2":"1.1","version_comment":"Works now also with two or more whitespaces as separator, and aligns with tabs or whitespaces according to the setting of \u00e2\u0080\u009cexpandtab\u00e2\u0080\u009d.","3":"Works now also with two or more whitespaces as separator, and aligns with tabs or whitespaces according to the setting of \u00e2\u0080\u009cexpandtab\u00e2\u0080\u009d.","package":"tabbi.vim","4":"tabbi.vim","src_id":"14068","5":"14068","creation_date":"1287328366","6":"1287328366"},{"0":"3280","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"tabbi.vim","4":"tabbi.vim","src_id":"14065","5":"14065","creation_date":"1287252526","6":"1287252526"}]},"3279":{"script_id":"3279","0":"3279","script_name":"ProjectParse","1":"ProjectParse","script_type":"utility","2":"utility","summary":"Parse common project types to augment the project plugin","3":"Parse common project types to augment the project plugin","description":"*** Summary ***\r\n\r\nProjectParse is a plugin that analyzes several common project formats and creates entries for them for use with  Vim's `project` plugin.  ProjectParse will also watch the specified project and automatically update it's entry when the project changes. ProjectParse currently supports the following project types:\r\n\r\n    * Microsoft Visual Studio Projects and Solutions\r\n    * Code::Blocks Projects and Workspaces\r\n    * Automake Makefiles\r\n    * MPLAB Projects\r\n    * CodeLite Projects\r\n    * (More to come!)\r\n\r\nBy simply running the :ProjectParse command on a relevant file, a file listing will be added to a user's configuration for the `project` plugin and will be kept up to date.\r\n\r\n*** Motivation ***\r\n\r\nOne of the most popular plugins available for Vim, the `project` plugin vimscript #69 provides a mechanism for creating lists of files that makeup a project. Beyond just giving you a file listing, it provides some great functionality such as automatically opening your project files, grepping through each file in the list, and running arbitrary commands on these files.                \r\n\r\nThe project plugin creates a project by scanning through the user's filesystem for files that match a specified pattern.  This approach, while effective for some projects, isn't optimal for others.  Often, the filesystem may contain files that match the specified pattern but are not a part of the project (such as temporary files or older revisions of relevant files).  Also, when the user's filesystem is large, generating the list of files can be quite time-consuming (I've had projects with 1,500 relevant files in a directory of 30,000 files, where >28,000 files are analyzed unnecessarily).  Another problem is that by relying on a pre-configured file pattern, certain important files can be missed when they are not part of the configured pattern, especially as projects evolve.\r\n\r\nOften, software developers already have a list of their relevant files in the form of a project for a well-known software tool like Microsoft Visual Studio. This is where ProjectParse enters.  ProjectParse is capable of analyzing project files for several popular software tools to automatically (and quickly) create a project for the `project` plugin.","4":"*** Summary ***\r\n\r\nProjectParse is a plugin that analyzes several common project formats and creates entries for them for use with  Vim's `project` plugin.  ProjectParse will also watch the specified project and automatically update it's entry when the project changes. ProjectParse currently supports the following project types:\r\n\r\n    * Microsoft Visual Studio Projects and Solutions\r\n    * Code::Blocks Projects and Workspaces\r\n    * Automake Makefiles\r\n    * MPLAB Projects\r\n    * CodeLite Projects\r\n    * (More to come!)\r\n\r\nBy simply running the :ProjectParse command on a relevant file, a file listing will be added to a user's configuration for the `project` plugin and will be kept up to date.\r\n\r\n*** Motivation ***\r\n\r\nOne of the most popular plugins available for Vim, the `project` plugin vimscript #69 provides a mechanism for creating lists of files that makeup a project. Beyond just giving you a file listing, it provides some great functionality such as automatically opening your project files, grepping through each file in the list, and running arbitrary commands on these files.                \r\n\r\nThe project plugin creates a project by scanning through the user's filesystem for files that match a specified pattern.  This approach, while effective for some projects, isn't optimal for others.  Often, the filesystem may contain files that match the specified pattern but are not a part of the project (such as temporary files or older revisions of relevant files).  Also, when the user's filesystem is large, generating the list of files can be quite time-consuming (I've had projects with 1,500 relevant files in a directory of 30,000 files, where >28,000 files are analyzed unnecessarily).  Another problem is that by relying on a pre-configured file pattern, certain important files can be missed when they are not part of the configured pattern, especially as projects evolve.\r\n\r\nOften, software developers already have a list of their relevant files in the form of a project for a well-known software tool like Microsoft Visual Studio. This is where ProjectParse enters.  ProjectParse is capable of analyzing project files for several popular software tools to automatically (and quickly) create a project for the `project` plugin.","install_details":"Copy ProjectParse.vim to your plugin directory; copy ProjectParse.txt to your doc directory.  Run helptags on your doc directory.","5":"Copy ProjectParse.vim to your plugin directory; copy ProjectParse.txt to your doc directory.  Run helptags on your doc directory.","first_name":"Daniel","6":"Daniel","last_name":"Price","7":"Price","releases":[{"0":"3279","vim_version":"7.0","1":"7.0","script_version":"1.1a","2":"1.1a","version_comment":"Fixed a typo that prevented Visual Studio parsing from working","3":"Fixed a typo that prevented Visual Studio parsing from working","package":"ProjectParse.zip","4":"ProjectParse.zip","src_id":"14292","5":"14292","creation_date":"1290053966","6":"1290053966"},{"0":"3279","vim_version":"7.0","1":"7.0","script_version":"1.1","2":"1.1","version_comment":"Added automatic update of projects upon a change to the project file.\r\n  - Projects will need to be reparsed to support this functionality\r\nAdded support for CodeLite projects\r\nAdded support for MPLAB projects\r\nImproved other parsers","3":"Added automatic update of projects upon a change to the project file.\r\n  - Projects will need to be reparsed to support this functionality\r\nAdded support for CodeLite projects\r\nAdded support for MPLAB projects\r\nImproved other parsers","package":"ProjectParse.zip","4":"ProjectParse.zip","src_id":"14278","5":"14278","creation_date":"1289964881","6":"1289964881"},{"0":"3279","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"ProjectParse.zip","4":"ProjectParse.zip","src_id":"14062","5":"14062","creation_date":"1287185557","6":"1287185557"}]},"3278":{"script_id":"3278","0":"3278","script_name":"Python 3.x Standard Library Reference","1":"Python 3.x Standard Library Reference","script_type":"utility","2":"utility","summary":"The Python 3.x standard library documentation as a Vim help file","3":"The Python 3.x standard library documentation as a Vim help file","description":"Installing this help file will give you access to the Python 3.1 standard library documentation as a Vim help file (available from within Vim by typing \":help py3stdlib\"). For this release I've only tagged the module names (otherwise the help tagspace becomes too cluttered). I have also left a lot of RST syntax decorations (e.g., backticks, bold) intact to preserve table alignment etc. If you have any suggestions for improvement or find areas in the documentation that need to be fixed, please let me know.","4":"Installing this help file will give you access to the Python 3.1 standard library documentation as a Vim help file (available from within Vim by typing \":help py3stdlib\"). For this release I've only tagged the module names (otherwise the help tagspace becomes too cluttered). I have also left a lot of RST syntax decorations (e.g., backticks, bold) intact to preserve table alignment etc. If you have any suggestions for improvement or find areas in the documentation that need to be fixed, please let me know.","install_details":"1. Download the file.\r\n2. Change to your $VIMRUNTIME directory (e.g., \"cd ~\/.vim\").\r\n3. Unarchive the file (e.g., \"unzip ~\/Downloads\/py3stdlib.zip\").\r\n4. Change to the \"doc\" subdirectory (e.g., \"cd doc\").\r\n5. Rebuild the tags: \"vim -c  \":helptags . | :q\"","5":"1. Download the file.\r\n2. Change to your $VIMRUNTIME directory (e.g., \"cd ~\/.vim\").\r\n3. Unarchive the file (e.g., \"unzip ~\/Downloads\/py3stdlib.zip\").\r\n4. Change to the \"doc\" subdirectory (e.g., \"cd doc\").\r\n5. Rebuild the tags: \"vim -c  \":helptags . | :q\"","first_name":"Jeet","6":"Jeet","last_name":"Sukumaran","7":"Sukumaran","releases":[{"0":"3278","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"py3stdlib.zip","4":"py3stdlib.zip","src_id":"14057","5":"14057","creation_date":"1287104816","6":"1287104816"}]},"3277":{"script_id":"3277","0":"3277","script_name":"Python 2.x Standard Library Reference","1":"Python 2.x Standard Library Reference","script_type":"utility","2":"utility","summary":"The Python 2.x standard library documentation as a Vim help file","3":"The Python 2.x standard library documentation as a Vim help file","description":"Installing this help file will give you access to the Python 2.7 standard library documentation as a Vim help file (available from within Vim by typing \":help py2stdlib\"). For this release I've only tagged the module names (otherwise the help tagspace becomes too cluttered).  I have also left a lot of RST syntax decorations (e.g., backticks, bold) intact to preserve table alignment etc. If you have any suggestions for improvement or find areas in the documentation that need to be fixed, please let me know.","4":"Installing this help file will give you access to the Python 2.7 standard library documentation as a Vim help file (available from within Vim by typing \":help py2stdlib\"). For this release I've only tagged the module names (otherwise the help tagspace becomes too cluttered).  I have also left a lot of RST syntax decorations (e.g., backticks, bold) intact to preserve table alignment etc. If you have any suggestions for improvement or find areas in the documentation that need to be fixed, please let me know.","install_details":"1. Download the file.\r\n2. Change to your $VIMRUNTIME directory (e.g., \"cd ~\/.vim\").\r\n3. Unarchive the file (e.g., \"unzip ~\/Downloads\/py2stdlib.zip\").\r\n4. Change to the \"doc\" subdirectory (e.g., \"cd doc\").\r\n5. Rebuild the tags: \"vim -c  \":helptags . | :q\"","5":"1. Download the file.\r\n2. Change to your $VIMRUNTIME directory (e.g., \"cd ~\/.vim\").\r\n3. Unarchive the file (e.g., \"unzip ~\/Downloads\/py2stdlib.zip\").\r\n4. Change to the \"doc\" subdirectory (e.g., \"cd doc\").\r\n5. Rebuild the tags: \"vim -c  \":helptags . | :q\"","first_name":"Jeet","6":"Jeet","last_name":"Sukumaran","7":"Sukumaran","releases":[{"0":"3277","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"py2stdlib.zip","4":"py2stdlib.zip","src_id":"14056","5":"14056","creation_date":"1287104528","6":"1287104528"}]},"3276":{"script_id":"3276","0":"3276","script_name":"ProjectCTags","1":"ProjectCTags","script_type":"utility","2":"utility","summary":"Generates CTAGS for versioned projects without the need to maintain project file","3":"Generates CTAGS for versioned projects without the need to maintain project file","description":"ProjectCTags is a plugin that enables you to generate CTags for a project which is under version control. These tags can then be used to Eclipse-like \"Jump-To-Definition\" or autocompletion of source code. Currently the plugin recognizes source code projects which are versioned with git, CVS and SVN version control systems. This plugin eases the task of generating up-to-date tag files. For people who like to maintain vim project files (Personally I do not like to do that, I just want tags for everything in my project folders), vimscript #3221 might be more appropriate. Once you have generated the tags you can use them in the following ways:\r\n\r\n* Jump to definition of the tag (if it is located in your project) under the cursor with Ctrl-]\r\n* Autocomplete C\/C++ source code with vimscript #1520 (See vimscript #1643 for intelligent <Tab> key completion)\r\n\r\nWhen you have opened a file, the plugin may either automatically update the corresponding tagfiles or it does this on your command (optional). It creates two tagfiles: One in the current folder, which contains detailed informations such as tags for local variables, and one tagfile in the project folder, which contains a less detailed overview of the globally visible tags in all source files in the versioned tree. By default it creates tags in the proper format for vimscript #1520.\r\n\r\nThe generated tags will only cover the code that is contained in your project! STL code etc is not included. If you want autocompletion for STL code you must download vimscript #2358 and insert the following into your .vimrc\r\n\r\nset tags += \"path\/to\/stl_tag_file\"\r\n\r\nIf you have questions or suggestions about\/for the plugin, feel free to contact me. And of course, if you like the plugin, vote for it in the box below :-)","4":"ProjectCTags is a plugin that enables you to generate CTags for a project which is under version control. These tags can then be used to Eclipse-like \"Jump-To-Definition\" or autocompletion of source code. Currently the plugin recognizes source code projects which are versioned with git, CVS and SVN version control systems. This plugin eases the task of generating up-to-date tag files. For people who like to maintain vim project files (Personally I do not like to do that, I just want tags for everything in my project folders), vimscript #3221 might be more appropriate. Once you have generated the tags you can use them in the following ways:\r\n\r\n* Jump to definition of the tag (if it is located in your project) under the cursor with Ctrl-]\r\n* Autocomplete C\/C++ source code with vimscript #1520 (See vimscript #1643 for intelligent <Tab> key completion)\r\n\r\nWhen you have opened a file, the plugin may either automatically update the corresponding tagfiles or it does this on your command (optional). It creates two tagfiles: One in the current folder, which contains detailed informations such as tags for local variables, and one tagfile in the project folder, which contains a less detailed overview of the globally visible tags in all source files in the versioned tree. By default it creates tags in the proper format for vimscript #1520.\r\n\r\nThe generated tags will only cover the code that is contained in your project! STL code etc is not included. If you want autocompletion for STL code you must download vimscript #2358 and insert the following into your .vimrc\r\n\r\nset tags += \"path\/to\/stl_tag_file\"\r\n\r\nIf you have questions or suggestions about\/for the plugin, feel free to contact me. And of course, if you like the plugin, vote for it in the box below :-)","install_details":"Just move projectCTags.vim to ~\/.vim\/plugin. The plugin requires CTags to be installed (http:\/\/ctags.sourceforge.net\/). If CTags is not in your $PATH environment variable, then you must specify the path to the CTags executable by putting\r\n\r\nlet g:projectCTagsCTagsExe = \"path\/to\/ctags\"\r\n\r\ninto your .vimrc file. To generate and set the CTags you can then use :GenerateProjectCTags( \"Tag Setting Name\", \"ctags options\" ). It is useful to map this to a key like\r\n\r\nmap  <F3>  :call GenerateProjectCTags( \"Standard\", \"\" )<CR>\r\nmap  <F4>  :call GenerateProjectCTags( \"Exclude Stuff\", \"--languages=C,C++ --exclude=folder1 --exclude=folder2\" )<CR>\r\n\r\n\r\nFor further options, see the \"projectCTags.vim\" file. They are all listed and documented at the top of the file. A useful option, which should be set inside the ~\/.vimrc, is:\r\n\r\nlet g:projectCTagsAutogenerateTags = 1\r\n\r\nThis will let ProjectCTags automatically regenerate the tag files when you open a C\/C++ file if you have already created the tags once manually by invoking :GenerateProjectCTags() before. This will then re-use the options (second parameter of GenerateProjectCTags) which were used last time inside the project. The options are stored in a \".tags_options\" file in the project folder.","5":"Just move projectCTags.vim to ~\/.vim\/plugin. The plugin requires CTags to be installed (http:\/\/ctags.sourceforge.net\/). If CTags is not in your $PATH environment variable, then you must specify the path to the CTags executable by putting\r\n\r\nlet g:projectCTagsCTagsExe = \"path\/to\/ctags\"\r\n\r\ninto your .vimrc file. To generate and set the CTags you can then use :GenerateProjectCTags( \"Tag Setting Name\", \"ctags options\" ). It is useful to map this to a key like\r\n\r\nmap  <F3>  :call GenerateProjectCTags( \"Standard\", \"\" )<CR>\r\nmap  <F4>  :call GenerateProjectCTags( \"Exclude Stuff\", \"--languages=C,C++ --exclude=folder1 --exclude=folder2\" )<CR>\r\n\r\n\r\nFor further options, see the \"projectCTags.vim\" file. They are all listed and documented at the top of the file. A useful option, which should be set inside the ~\/.vimrc, is:\r\n\r\nlet g:projectCTagsAutogenerateTags = 1\r\n\r\nThis will let ProjectCTags automatically regenerate the tag files when you open a C\/C++ file if you have already created the tags once manually by invoking :GenerateProjectCTags() before. This will then re-use the options (second parameter of GenerateProjectCTags) which were used last time inside the project. The options are stored in a \".tags_options\" file in the project folder.","first_name":"T.","6":"T.","last_name":"Kelter","7":"Kelter","releases":[{"0":"3276","vim_version":"7.0","1":"7.0","script_version":"0.3.1","2":"0.3.1","version_comment":"Fixed a misformatted line-break which led to a syntax error.","3":"Fixed a misformatted line-break which led to a syntax error.","package":"projectCTags.vim","4":"projectCTags.vim","src_id":"14520","5":"14520","creation_date":"1292410417","6":"1292410417"},{"0":"3276","vim_version":"7.0","1":"7.0","script_version":"0.3","2":"0.3","version_comment":"The output generated by the plugin is now less verbose. Options were added to specify individual verbosity levels.","3":"The output generated by the plugin is now less verbose. Options were added to specify individual verbosity levels.","package":"projectCTags.vim","4":"projectCTags.vim","src_id":"14328","5":"14328","creation_date":"1290261681","6":"1290261681"},{"0":"3276","vim_version":"7.0","1":"7.0","script_version":"0.2","2":"0.2","version_comment":"Automatically uses the correct path separator ('\\\\') on Windows systems now (thanks to Дмитрий Франк)","3":"Automatically uses the correct path separator ('\\\\') on Windows systems now (thanks to Дмитрий Франк)","package":"projectCTags.vim","4":"projectCTags.vim","src_id":"14192","5":"14192","creation_date":"1289037423","6":"1289037423"},{"0":"3276","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"projectCTags.vim","4":"projectCTags.vim","src_id":"14051","5":"14051","creation_date":"1286973489","6":"1286973489"}]},"3275":{"script_id":"3275","0":"3275","script_name":"actionscript.vim","1":"actionscript.vim","script_type":"syntax","2":"syntax","summary":"ActionScript 3.0 syntax file with regular expressions","3":"ActionScript 3.0 syntax file with regular expressions","description":"Improves vimscript #1061 by adding regular expression support. Nothing fancy.","4":"Improves vimscript #1061 by adding regular expression support. Nothing fancy.","install_details":"As for vimscript #1061. An easy way is to install this into \/usr\/share\/vim\/vimcurrent\/syntax\/ or $HOME\/.vim\/syntax, and then add the following to your .vimrc to override the default \"Atlas\" association:\r\n\r\nau Bufread,BufNewFile *.as set filetype=actionscript","5":"As for vimscript #1061. An easy way is to install this into \/usr\/share\/vim\/vimcurrent\/syntax\/ or $HOME\/.vim\/syntax, and then add the following to your .vimrc to override the default \"Atlas\" association:\r\n\r\nau Bufread,BufNewFile *.as set filetype=actionscript","first_name":"Yuki","6":"Yuki","last_name":"Izumi","7":"Izumi","releases":[{"0":"3275","vim_version":"6.0","1":"6.0","script_version":"0.4","2":"0.4","version_comment":"Initial upload","3":"Initial upload","package":"actionscript.vim","4":"actionscript.vim","src_id":"14042","5":"14042","creation_date":"1286847912","6":"1286847912"}]},"3274":{"script_id":"3274","0":"3274","script_name":"Liquid Carbon","1":"Liquid Carbon","script_type":"color scheme","2":"color scheme","summary":"Dark-background GUI color scheme.","3":"Dark-background GUI color scheme.","description":"Matte dark-gray background with flat dark blue-slate trimmings, and colorful yet harmonious syntax highlighting. Screenshots available at: http:\/\/jeetworks.org\/liquidcarbon . Higher-contrast (darker background) can be set by defining \"g:liquidcarbon_high_contrast=1\" in '~\/.vimrc'.","4":"Matte dark-gray background with flat dark blue-slate trimmings, and colorful yet harmonious syntax highlighting. Screenshots available at: http:\/\/jeetworks.org\/liquidcarbon . Higher-contrast (darker background) can be set by defining \"g:liquidcarbon_high_contrast=1\" in '~\/.vimrc'.","install_details":"Download\/save\/copy\/move the file \"liquidcarbon.vim\" to your \"$VIMRUNTIME\/colors\" directory (e.g., \"~\/.vim\/colors\"). Activate the color scheme by entering the command, \":colors liquidcarbon\". ","5":"Download\/save\/copy\/move the file \"liquidcarbon.vim\" to your \"$VIMRUNTIME\/colors\" directory (e.g., \"~\/.vim\/colors\"). Activate the color scheme by entering the command, \":colors liquidcarbon\". ","first_name":"Jeet","6":"Jeet","last_name":"Sukumaran","7":"Sukumaran","releases":[{"0":"3274","vim_version":"7.0","1":"7.0","script_version":"1.1","2":"1.1","version_comment":"* Higher contrast (darker background) by setting \"g:liquidcarbon_high_contrast=1\" before activating colors.\r\n* Cursor line visibility improved. ","3":"* Higher contrast (darker background) by setting \"g:liquidcarbon_high_contrast=1\" before activating colors.\r\n* Cursor line visibility improved. ","package":"liquidcarbon.vim","4":"liquidcarbon.vim","src_id":"14080","5":"14080","creation_date":"1287541706","6":"1287541706"},{"0":"3274","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"liquidcarbon.vim","4":"liquidcarbon.vim","src_id":"14035","5":"14035","creation_date":"1286674746","6":"1286674746"}]},"3273":{"script_id":"3273","0":"3273","script_name":"kirikiri.vim","1":"kirikiri.vim","script_type":"syntax","2":"syntax","summary":"syntax file for kirikiri (吉里吉里)","3":"syntax file for kirikiri (吉里吉里)","description":"repository: http:\/\/github.com\/tyru\/kirikiri.vim\r\n\r\n\r\n吉里吉里のsyntaxファイルです。\r\nsyntax\/tjs.vimがあればiscript, endscriptの間もハイライトします。\r\n(syntax\/tjs.vimはまだ開発中です)\r\n\r\nsyntax file for kirikiri.\r\nIf syntax\/tjs.vim is installed,\r\nit highlights between iscript, endscript.\r\n(NOTE: syntax\/tjs.vim is under development)","4":"repository: http:\/\/github.com\/tyru\/kirikiri.vim\r\n\r\n\r\n吉里吉里のsyntaxファイルです。\r\nsyntax\/tjs.vimがあればiscript, endscriptの間もハイライトします。\r\n(syntax\/tjs.vimはまだ開発中です)\r\n\r\nsyntax file for kirikiri.\r\nIf syntax\/tjs.vim is installed,\r\nit highlights between iscript, endscript.\r\n(NOTE: syntax\/tjs.vim is under development)","install_details":"","5":"","first_name":"tyru","6":"tyru","last_name":" ","7":" ","releases":[{"0":"3273","vim_version":"7.0","1":"7.0","script_version":"0.0.0","2":"0.0.0","version_comment":"Initial upload","3":"Initial upload","package":"kirikiri.zip","4":"kirikiri.zip","src_id":"14033","5":"14033","creation_date":"1286627788","6":"1286627788"}]},"3272":{"script_id":"3272","0":"3272","script_name":"tchaba","1":"tchaba","script_type":"color scheme","2":"color scheme","summary":"A dark color scheme, 256 color terminals","3":"A dark color scheme, 256 color terminals","description":"Screenshot:\r\nhttp:\/\/dl.dropbox.com\/u\/15349775\/vimsample.png","4":"Screenshot:\r\nhttp:\/\/dl.dropbox.com\/u\/15349775\/vimsample.png","install_details":"- Set  \"t_Co\"  to 256 in ~\/.vimrc to make Vim use 256 colors:\r\nset t_Co=256\r\n\r\n- Copy this script to your ~\/.vim\/colors.","5":"- Set  \"t_Co\"  to 256 in ~\/.vimrc to make Vim use 256 colors:\r\nset t_Co=256\r\n\r\n- Copy this script to your ~\/.vim\/colors.","first_name":"Lucas","6":"Lucas","last_name":"Avan\u00c3\u00a7o","7":"Avan\u00c3\u00a7o","releases":[{"0":"3272","vim_version":"7.0","1":"7.0","script_version":"2.0","2":"2.0","version_comment":"Cleaner script and a new appearance.","3":"Cleaner script and a new appearance.","package":"tchaba2.vim","4":"tchaba2.vim","src_id":"15280","5":"15280","creation_date":"1300912853","6":"1300912853"},{"0":"3272","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"tchaba.vim","4":"tchaba.vim","src_id":"14022","5":"14022","creation_date":"1286472307","6":"1286472307"}]},"3271":{"script_id":"3271","0":"3271","script_name":"RangeMacro","1":"RangeMacro","script_type":"utility","2":"utility","summary":"Execute macro repeatedly until the end of a range is reached. ","3":"Execute macro repeatedly until the end of a range is reached. ","description":"DESCRIPTION\r\nMacros are a fantastic way to apply the same modification many many times.\r\nJust record once and then repeat, repeat, repeat...\r\n\r\nThough it's easy to repeat (@@, [count]@{0-9a-z\".=*}) a macro, explicit\r\nrepeating becomes cumbersome when you're dealing with hundreds of repeats. You\r\ncan write a recursive macro (i.e. invoking the macro at the end), but that\r\nwill execute over the entire buffer, until the macro errors out on the border\r\nof the buffer. Simple macros that mostly restrict themselves to a single line\r\ncan be repeated via :[range]normal @{0-9a-z\".=*}, but that breaks when lines\r\nare inserted or removed, or the macro jumps to other lines.\r\n\r\nWhat's needed for extensive macro repetitions is to repeatedly execute the\r\nmacro over a range, and stop once the macro navigates out of the range.\r\n\r\nThis plugin provides a :RangeMacro command and mappings that execute a\r\nrecorded macro over a range, area of text covered by {motion}, or the current\r\nseletion.\r\n\r\nRELATED WORKS\r\n- CommandWithMutableRange.vim (vimscript #3270) executes commands which may\r\n  add or remove lines for each line in the range.\r\n\r\nUSAGE\r\n:[range]RangeMacro {0-9a-z\".*+}\r\n                        Position the cursor on the first column of the start\r\n                        of [range] and execute the contents of register\r\n                        {0-9a-z\".*+} repeatedly until the cursor moves beyond\r\n                        the lines covered by [range].\r\n\r\n<Leader>@{0-9a-z\".*+}{motion}\r\n                        Repeatedly execute the contents of register\r\n                        {0-9a-z\".*+} until the cursor moves outside the text\r\n                        covered by {motion}.\r\n\r\n{Visual}<Leader>@{0-9a-z\".*+}\r\n                        Position the cursor on the first column of the\r\n                        selection and execute the contents of register\r\n                        {0-9a-z\".*+} repeatedly until the cursor moves outside\r\n                        the selection. All selection modes are supported:\r\n                        characterwise, linewise and blockwise.\r\n\r\nNote: The check whether the macro moved outside the range is only done _after_\r\neach macro invocation. During macro evaluation, jumps outside the range can be\r\nused and will not stop macro execution.\r\n\r\nSUITABLE MACROS\r\nTo make a macro repeatable, the macro must move to the position where the next\r\nmacro call needs to take place, typically either as the first or last command\r\nof the macro. The macro will always be executed from top to bottom of the\r\nrange, regardless of how {motion} or the selection was made.\r\nSo, for example, if the macro processes line(s) sequentially, append the \"j\"\r\ncommand to move to the next line; if the buffer areas are located via\r\nsearching, you could use the \"n\" command to move to the next match.","4":"DESCRIPTION\r\nMacros are a fantastic way to apply the same modification many many times.\r\nJust record once and then repeat, repeat, repeat...\r\n\r\nThough it's easy to repeat (@@, [count]@{0-9a-z\".=*}) a macro, explicit\r\nrepeating becomes cumbersome when you're dealing with hundreds of repeats. You\r\ncan write a recursive macro (i.e. invoking the macro at the end), but that\r\nwill execute over the entire buffer, until the macro errors out on the border\r\nof the buffer. Simple macros that mostly restrict themselves to a single line\r\ncan be repeated via :[range]normal @{0-9a-z\".=*}, but that breaks when lines\r\nare inserted or removed, or the macro jumps to other lines.\r\n\r\nWhat's needed for extensive macro repetitions is to repeatedly execute the\r\nmacro over a range, and stop once the macro navigates out of the range.\r\n\r\nThis plugin provides a :RangeMacro command and mappings that execute a\r\nrecorded macro over a range, area of text covered by {motion}, or the current\r\nseletion.\r\n\r\nRELATED WORKS\r\n- CommandWithMutableRange.vim (vimscript #3270) executes commands which may\r\n  add or remove lines for each line in the range.\r\n\r\nUSAGE\r\n:[range]RangeMacro {0-9a-z\".*+}\r\n                        Position the cursor on the first column of the start\r\n                        of [range] and execute the contents of register\r\n                        {0-9a-z\".*+} repeatedly until the cursor moves beyond\r\n                        the lines covered by [range].\r\n\r\n<Leader>@{0-9a-z\".*+}{motion}\r\n                        Repeatedly execute the contents of register\r\n                        {0-9a-z\".*+} until the cursor moves outside the text\r\n                        covered by {motion}.\r\n\r\n{Visual}<Leader>@{0-9a-z\".*+}\r\n                        Position the cursor on the first column of the\r\n                        selection and execute the contents of register\r\n                        {0-9a-z\".*+} repeatedly until the cursor moves outside\r\n                        the selection. All selection modes are supported:\r\n                        characterwise, linewise and blockwise.\r\n\r\nNote: The check whether the macro moved outside the range is only done _after_\r\neach macro invocation. During macro evaluation, jumps outside the range can be\r\nused and will not stop macro execution.\r\n\r\nSUITABLE MACROS\r\nTo make a macro repeatable, the macro must move to the position where the next\r\nmacro call needs to take place, typically either as the first or last command\r\nof the macro. The macro will always be executed from top to bottom of the\r\nrange, regardless of how {motion} or the selection was made.\r\nSo, for example, if the macro processes line(s) sequentially, append the \"j\"\r\ncommand to move to the next line; if the buffer areas are located via\r\nsearching, you could use the \"n\" command to move to the next match.","install_details":"INSTALLATION\r\nThis script is packaged as a vimball. If you have the \"gunzip\" decompressor\r\nin your PATH, simply edit the *.vba.gz package in Vim; otherwise, decompress\r\nthe archive first, e.g. using WinZip. Inside Vim, install by sourcing the\r\nvimball or via the :UseVimball command. \r\n    vim RangeMacro.vba.gz\r\n    :so %\r\nTo uninstall, use the :RmVimball command. \r\n\r\nDEPENDENCIES\r\n- Requires Vim 7.0 or higher. \r\n\r\nCONFIGURATION\r\nFor a permanent configuration, put the following commands into your vimrc: \r\n\r\nAs there must be mappings for all supported registers, the mapping cannot be\r\neasily customized via the <Plug> mechanism. Instead, if you prefer a different\r\nmapping, redefine the start of the normal and visual mode mappings (before\r\nthe plugin is sourced): \r\n    let g:RangeMacro_Mapping = '<Leader>@'","5":"INSTALLATION\r\nThis script is packaged as a vimball. If you have the \"gunzip\" decompressor\r\nin your PATH, simply edit the *.vba.gz package in Vim; otherwise, decompress\r\nthe archive first, e.g. using WinZip. Inside Vim, install by sourcing the\r\nvimball or via the :UseVimball command. \r\n    vim RangeMacro.vba.gz\r\n    :so %\r\nTo uninstall, use the :RmVimball command. \r\n\r\nDEPENDENCIES\r\n- Requires Vim 7.0 or higher. \r\n\r\nCONFIGURATION\r\nFor a permanent configuration, put the following commands into your vimrc: \r\n\r\nAs there must be mappings for all supported registers, the mapping cannot be\r\neasily customized via the <Plug> mechanism. Instead, if you prefer a different\r\nmapping, redefine the start of the normal and visual mode mappings (before\r\nthe plugin is sourced): \r\n    let g:RangeMacro_Mapping = '<Leader>@'","first_name":"Ingo","6":"Ingo","last_name":"Karkat","7":"Karkat","releases":[{"0":"3271","vim_version":"7.0","1":"7.0","script_version":"1.00","2":"1.00","version_comment":"Initial upload","3":"Initial upload","package":"RangeMacro.vba.gz","4":"RangeMacro.vba.gz","src_id":"14021","5":"14021","creation_date":"1286459477","6":"1286459477"}]},"3270":{"script_id":"3270","0":"3270","script_name":"CommandWithMutableRange","1":"CommandWithMutableRange","script_type":"utility","2":"utility","summary":"Execute commands which may add or remove lines for each line in the range. ","3":"Execute commands which may add or remove lines for each line in the range. ","description":"DESCRIPTION\r\nThis plugin offers enhanced versions of the :[range]normal[!] and :[range]call\r\ncommands which allow for additions and deletions of lines during iteration,\r\nand adapt the initially supplied [range] accordingly.\r\n\r\nThe built-in :normal[!] and :call commands can take a [range], and are then\r\nexecuted for each line in the range. If the supplied command \/ function\r\nmodifies the number of lines in the buffer, the iteration continues over the\r\ninitially supplied range of line numbers, totally oblivious to the changes.\r\nThus, if you want to apply modifications that add or delete lines before or\r\ninside the [range], this built-in Vim functionality isn't much of a help. (You\r\ncan work around this by recording a macro and then manually repeating it over\r\neach line, until you reach the end of the range, but you need to do the\r\nchecking.)\r\n\r\nRELATED WORKS\r\n- RangeMacro.vim (vimscript #3271) executes macros repeatedly until the end of\r\n  a range is reached, also taking addition \/ removal of lines into account.\r\n\r\nUSAGE\r\nThe plugin provides enhanced versions of the :call, :normal and :execute\r\nVim commands:\r\n\r\n:[range]CallWithMutableRange {name}([arguments])\r\n                        Call a function (that does not need to accept a range)\r\n                        once for every line in [range].\r\n\r\n:[range]NormalWithMutableRange[!] {commands}\r\n                        Execute Normal mode commands {commands} for each line\r\n                        in the [range].\r\n\r\n:[range]ExecuteWithMutableRange {expr1} ...\r\n                        Execute the string that results from the evaluation of\r\n                        {expr1} as an Ex command, once for every line in\r\n                        [range]. {expr1} is re-evaluated on each line.\r\n                        Normally, (custom) commands that can operate over\r\n                        multiple lines should take an optional [range], but\r\n                        sometimes this wasn't implemented, and the command\r\n                        only operates on the current position. In these cases,\r\n                        (in addition to ad-hoc expressions) this command is\r\n                        useful, and also handles (most) deletions and\r\n                        insertions gracefully.\r\n\r\nFor each iteration, the cursor is positioned in the first column of that line.\r\nFolding is temporarily disabled. The cursor is left at the last line (possibly\r\nmoved by the last invocation). The arguments are re-evaluated for each line.","4":"DESCRIPTION\r\nThis plugin offers enhanced versions of the :[range]normal[!] and :[range]call\r\ncommands which allow for additions and deletions of lines during iteration,\r\nand adapt the initially supplied [range] accordingly.\r\n\r\nThe built-in :normal[!] and :call commands can take a [range], and are then\r\nexecuted for each line in the range. If the supplied command \/ function\r\nmodifies the number of lines in the buffer, the iteration continues over the\r\ninitially supplied range of line numbers, totally oblivious to the changes.\r\nThus, if you want to apply modifications that add or delete lines before or\r\ninside the [range], this built-in Vim functionality isn't much of a help. (You\r\ncan work around this by recording a macro and then manually repeating it over\r\neach line, until you reach the end of the range, but you need to do the\r\nchecking.)\r\n\r\nRELATED WORKS\r\n- RangeMacro.vim (vimscript #3271) executes macros repeatedly until the end of\r\n  a range is reached, also taking addition \/ removal of lines into account.\r\n\r\nUSAGE\r\nThe plugin provides enhanced versions of the :call, :normal and :execute\r\nVim commands:\r\n\r\n:[range]CallWithMutableRange {name}([arguments])\r\n                        Call a function (that does not need to accept a range)\r\n                        once for every line in [range].\r\n\r\n:[range]NormalWithMutableRange[!] {commands}\r\n                        Execute Normal mode commands {commands} for each line\r\n                        in the [range].\r\n\r\n:[range]ExecuteWithMutableRange {expr1} ...\r\n                        Execute the string that results from the evaluation of\r\n                        {expr1} as an Ex command, once for every line in\r\n                        [range]. {expr1} is re-evaluated on each line.\r\n                        Normally, (custom) commands that can operate over\r\n                        multiple lines should take an optional [range], but\r\n                        sometimes this wasn't implemented, and the command\r\n                        only operates on the current position. In these cases,\r\n                        (in addition to ad-hoc expressions) this command is\r\n                        useful, and also handles (most) deletions and\r\n                        insertions gracefully.\r\n\r\nFor each iteration, the cursor is positioned in the first column of that line.\r\nFolding is temporarily disabled. The cursor is left at the last line (possibly\r\nmoved by the last invocation). The arguments are re-evaluated for each line.","install_details":"INSTALLATION\r\nThis script is packaged as a vimball. If you have the \"gunzip\" decompressor\r\nin your PATH, simply edit the *.vba.gz package in Vim; otherwise, decompress\r\nthe archive first, e.g. using WinZip. Inside Vim, install by sourcing the\r\nvimball or via the :UseVimball command. \r\n    vim CommandWithMutableRange.vba.gz\r\n    :so %\r\nTo uninstall, use the :RmVimball command. \r\n\r\nDEPENDENCIES\r\n- Requires Vim 7.0 or higher. \r\n\r\nCONFIGURATION\r\nBy default, the commands try to find 3 unused marks in the current buffer, and\r\nwill refuse to work if no unused marks can be found. Alternatively, you can\r\nreserve any number of marks (but a maximum of 3 will be used) for use by the\r\ncommands by setting a global variable (either temporarily in a user function,\r\nor permanently in your vimrc file): \r\n    let g:CommandWithMutableRange_marks = 'abc'","5":"INSTALLATION\r\nThis script is packaged as a vimball. If you have the \"gunzip\" decompressor\r\nin your PATH, simply edit the *.vba.gz package in Vim; otherwise, decompress\r\nthe archive first, e.g. using WinZip. Inside Vim, install by sourcing the\r\nvimball or via the :UseVimball command. \r\n    vim CommandWithMutableRange.vba.gz\r\n    :so %\r\nTo uninstall, use the :RmVimball command. \r\n\r\nDEPENDENCIES\r\n- Requires Vim 7.0 or higher. \r\n\r\nCONFIGURATION\r\nBy default, the commands try to find 3 unused marks in the current buffer, and\r\nwill refuse to work if no unused marks can be found. Alternatively, you can\r\nreserve any number of marks (but a maximum of 3 will be used) for use by the\r\ncommands by setting a global variable (either temporarily in a user function,\r\nor permanently in your vimrc file): \r\n    let g:CommandWithMutableRange_marks = 'abc'","first_name":"Ingo","6":"Ingo","last_name":"Karkat","7":"Karkat","releases":[{"0":"3270","vim_version":"7.0","1":"7.0","script_version":"1.00","2":"1.00","version_comment":"Initial upload","3":"Initial upload","package":"CommandWithMutableRange.vba.gz","4":"CommandWithMutableRange.vba.gz","src_id":"14020","5":"14020","creation_date":"1286459405","6":"1286459405"}]},"3269":{"script_id":"3269","0":"3269","script_name":"open_file_from_clip_board","1":"open_file_from_clip_board","script_type":"utility","2":"utility","summary":"open file path that is copied in clipboard","3":"open file path that is copied in clipboard","description":"Note this script need clipboard supported \r\n\r\nhttp:\/\/vim.wikia.com\/wiki\/Accessing_the_system_clipboard\r\n\r\nspecifically, it use the * register to get the text in the clipboard\r\n\r\nthis little script define a function call OpenFilesFromClipboard()\r\n\r\nIf you, for example, execute some command from the terminal (maybe a grep) and get result like this:\r\n\r\n\/Users\/me\/myfile:23:something something\r\n\/Users\/me\/anotherfile: 34 I am a file\r\n\/Users\/me\/yetanotherone hello\r\n\r\nwhat you can do with this plugin is: highlight the text and copy it into your system clipboard (Cmd-c in MacOSX and Ctrl-c in Windows)\r\n\r\nAssuming you have a mapping in your .vimrc\r\nmap <LEADER>jc :call OpenFilesFromClipboard()<CR>\r\n\r\nthen open your vim and type <LEADER>jc will open that each file into a new tab\r\nI hard code to tabnew for now, check back later version for more flexibility\r\n\r\nNote:\r\n just reallize that support different program on different environment is impossible. If it works for you, great, otherwise, please read the code, the idea and code it up for your usage","4":"Note this script need clipboard supported \r\n\r\nhttp:\/\/vim.wikia.com\/wiki\/Accessing_the_system_clipboard\r\n\r\nspecifically, it use the * register to get the text in the clipboard\r\n\r\nthis little script define a function call OpenFilesFromClipboard()\r\n\r\nIf you, for example, execute some command from the terminal (maybe a grep) and get result like this:\r\n\r\n\/Users\/me\/myfile:23:something something\r\n\/Users\/me\/anotherfile: 34 I am a file\r\n\/Users\/me\/yetanotherone hello\r\n\r\nwhat you can do with this plugin is: highlight the text and copy it into your system clipboard (Cmd-c in MacOSX and Ctrl-c in Windows)\r\n\r\nAssuming you have a mapping in your .vimrc\r\nmap <LEADER>jc :call OpenFilesFromClipboard()<CR>\r\n\r\nthen open your vim and type <LEADER>jc will open that each file into a new tab\r\nI hard code to tabnew for now, check back later version for more flexibility\r\n\r\nNote:\r\n just reallize that support different program on different environment is impossible. If it works for you, great, otherwise, please read the code, the idea and code it up for your usage","install_details":"copy the .vim file to your vim space\/plugin\r\nmap a key to function OpenFilesFromClipboard() e.g:\r\n\r\nmap jcb :call OpenFilesFromClipboard()\r\n\r\nenjoy!!","5":"copy the .vim file to your vim space\/plugin\r\nmap a key to function OpenFilesFromClipboard() e.g:\r\n\r\nmap jcb :call OpenFilesFromClipboard()\r\n\r\nenjoy!!","first_name":"Vinh","6":"Vinh","last_name":"Tran","7":"Tran","releases":[{"0":"3269","vim_version":"7.0","1":"7.0","script_version":"1.2","2":"1.2","version_comment":"Included a patch by Martin Lemburg (martin.lemburg@gmx.net) for support on window.","3":"Included a patch by Martin Lemburg (martin.lemburg@gmx.net) for support on window.","package":"clipboard_file_open.vim","4":"clipboard_file_open.vim","src_id":"14043","5":"14043","creation_date":"1286867164","6":"1286867164"},{"0":"3269","vim_version":"7.0","1":"7.0","script_version":"1.1","2":"1.1","version_comment":"Fix the bug that fail to jump to the line number","3":"Fix the bug that fail to jump to the line number","package":"clipboard_file_open.vim","4":"clipboard_file_open.vim","src_id":"14025","5":"14025","creation_date":"1286494698","6":"1286494698"},{"0":"3269","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"clipboard_file_open.vim","4":"clipboard_file_open.vim","src_id":"14019","5":"14019","creation_date":"1286458122","6":"1286458122"}]},"3268":{"script_id":"3268","0":"3268","script_name":"command-list","1":"command-list","script_type":"utility","2":"utility","summary":"create a list of command and display as needed","3":"create a list of command and display as needed","description":"Command list allowed you to define a list(group) of command\r\nDefine a shortcut to display the list, from there you can choose a command to execute. Command list is written in ruby so your vim need +ruby supported\r\n\r\nScreenshot:\r\n\r\nhttp:\/\/vim.wikia.com\/wiki\/File:Screen_shot.png\r\n\r\nFor any question please put it on this script's wiki page\r\n\r\nhttp:\/\/vim.wikia.com\/wiki\/Script:3268\r\n","4":"Command list allowed you to define a list(group) of command\r\nDefine a shortcut to display the list, from there you can choose a command to execute. Command list is written in ruby so your vim need +ruby supported\r\n\r\nScreenshot:\r\n\r\nhttp:\/\/vim.wikia.com\/wiki\/File:Screen_shot.png\r\n\r\nFor any question please put it on this script's wiki page\r\n\r\nhttp:\/\/vim.wikia.com\/wiki\/Script:3268\r\n","install_details":"unzip it in to you vim space. please read the doc\/command-list.txt for how to set up the command list.\r\n\r\nIf you set up the map for the list, you can use the map shortcut to display\r\nthe shortcut or you can do it manually in your .vimrc as follow\r\n\r\nmap mapkey :ruby CommandList::display_command_list('Jump')<CR>\r\n\r\nyou can add multiple list into a single display by adding it to the parameters\r\nof the display_command_list call. For example:\r\n\r\nmap mapkey :ruby CommandList::display_command_list('Jump', 'Format')<CR>\r\n\r\nIf no parameters is given, all the list will be displayed\r\n\r\nThere is a sample file: plugin\/command-list.rb.sample for your reference.\r\n\r\n*Updated*: you could also use the line number to choose the command, but only from 1 - 9 :D","5":"unzip it in to you vim space. please read the doc\/command-list.txt for how to set up the command list.\r\n\r\nIf you set up the map for the list, you can use the map shortcut to display\r\nthe shortcut or you can do it manually in your .vimrc as follow\r\n\r\nmap mapkey :ruby CommandList::display_command_list('Jump')<CR>\r\n\r\nyou can add multiple list into a single display by adding it to the parameters\r\nof the display_command_list call. For example:\r\n\r\nmap mapkey :ruby CommandList::display_command_list('Jump', 'Format')<CR>\r\n\r\nIf no parameters is given, all the list will be displayed\r\n\r\nThere is a sample file: plugin\/command-list.rb.sample for your reference.\r\n\r\n*Updated*: you could also use the line number to choose the command, but only from 1 - 9 :D","first_name":"Vinh","6":"Vinh","last_name":"Tran","7":"Tran","releases":[{"0":"3268","vim_version":"7.0","1":"7.0","script_version":"1.1","2":"1.1","version_comment":"Update the doco","3":"Update the doco","package":"command-list.zip","4":"command-list.zip","src_id":"14007","5":"14007","creation_date":"1286360972","6":"1286360972"},{"0":"3268","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"command-list.zip","4":"command-list.zip","src_id":"14006","5":"14006","creation_date":"1286360865","6":"1286360865"}]},"3267":{"script_id":"3267","0":"3267","script_name":"omnetpp","1":"omnetpp","script_type":"ftplugin","2":"ftplugin","summary":"help to edit and debug the ned file by OMNeT++","3":"help to edit and debug the ned file by OMNeT++","description":"help to edit and debug the ned file by OMNeT++. ","4":"help to edit and debug the ned file by OMNeT++. ","install_details":"copy omnetpp.vim to $HOME\/.vim\/plugin\/","5":"copy omnetpp.vim to $HOME\/.vim\/plugin\/","first_name":"lei","6":"lei","last_name":"xue","7":"xue","releases":[{"0":"3267","vim_version":"7.0","1":"7.0","script_version":"0.1.2","2":"0.1.2","version_comment":"fix some bugs for OMNeT++ 4.x ned script.\r\nchange the comments from '#' to \"\/\/\"; change the simple options","3":"fix some bugs for OMNeT++ 4.x ned script.\r\nchange the comments from '#' to \"\/\/\"; change the simple options","package":"omnetpp.vim","4":"omnetpp.vim","src_id":"14044","5":"14044","creation_date":"1286887822","6":"1286887822"},{"0":"3267","vim_version":"7.0","1":"7.0","script_version":"0.1.1","2":"0.1.1","version_comment":"add some mapping keys for easily input.","3":"add some mapping keys for easily input.","package":"omnetpp.vim","4":"omnetpp.vim","src_id":"14018","5":"14018","creation_date":"1286453369","6":"1286453369"},{"0":"3267","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"omnetpp.tar.gz","4":"omnetpp.tar.gz","src_id":"14004","5":"14004","creation_date":"1286350326","6":"1286350326"}]},"3266":{"script_id":"3266","0":"3266","script_name":"codeblocks-dark","1":"codeblocks-dark","script_type":"color scheme","2":"color scheme","summary":"Code::Blocks original theme in a dark manner","3":"Code::Blocks original theme in a dark manner","description":"Inspired by the original Code::Blocks theme in a dark manner.\r\n\r\nGithub: https:\/\/github.com\/noscript\/codeblocks-dark.vim\r\n","4":"Inspired by the original Code::Blocks theme in a dark manner.\r\n\r\nGithub: https:\/\/github.com\/noscript\/codeblocks-dark.vim\r\n","install_details":"Copy to ~\/.vim\/colors\/","5":"Copy to ~\/.vim\/colors\/","first_name":"Sergey","6":"Sergey","last_name":"Vlasov","7":"Vlasov","releases":[{"0":"3266","vim_version":"7.0","1":"7.0","script_version":"0.5","2":"0.5","version_comment":"revamp + dropped cterm colors","3":"revamp + dropped cterm colors","package":"codeblocks-dark.vim","4":"codeblocks-dark.vim","src_id":"25714","5":"25714","creation_date":"1513254876","6":"1513254876"},{"0":"3266","vim_version":"7.0","1":"7.0","script_version":"0.4","2":"0.4","version_comment":"added cterm colors","3":"added cterm colors","package":"codeblocks-dark.vim","4":"codeblocks-dark.vim","src_id":"22646","5":"22646","creation_date":"1416928600","6":"1416928600"},{"0":"3266","vim_version":"7.0","1":"7.0","script_version":"0.3","2":"0.3","version_comment":"more consistency","3":"more consistency","package":"codeblocks-dark.vim","4":"codeblocks-dark.vim","src_id":"21691","5":"21691","creation_date":"1396191217","6":"1396191217"},{"0":"3266","vim_version":"7.0","1":"7.0","script_version":"0.2","2":"0.2","version_comment":"Softer colors","3":"Softer colors","package":"codeblocks_dark.vim","4":"codeblocks_dark.vim","src_id":"17704","5":"17704","creation_date":"1333378143","6":"1333378143"},{"0":"3266","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"codeblocks_dark.vim","4":"codeblocks_dark.vim","src_id":"13991","5":"13991","creation_date":"1286272440","6":"1286272440"}]},"3265":{"script_id":"3265","0":"3265","script_name":"bazel","1":"bazel","script_type":"syntax","2":"syntax","summary":"Bazel build system integration","3":"Bazel build system integration","description":"Provides support for Bazel target autocompletion, goto-definition for BUILD\r\nfiles, listing references and more.\r\n\r\nGitHub: https:\/\/github.com\/noscript\/bazel.vim","4":"Provides support for Bazel target autocompletion, goto-definition for BUILD\r\nfiles, listing references and more.\r\n\r\nGitHub: https:\/\/github.com\/noscript\/bazel.vim","install_details":"Extract to ~\/.vim\/","5":"Extract to ~\/.vim\/","first_name":"Sergey","6":"Sergey","last_name":"Vlasov","7":"Vlasov","releases":[{"0":"3265","vim_version":"9.0","1":"9.0","script_version":"0.2","2":"0.2","version_comment":"* disable \"goto BUILD\" for bazel files\r\n* detect workspace fix\r\n* autocommands fix\r\n* quotation fix","3":"* disable \"goto BUILD\" for bazel files\r\n* detect workspace fix\r\n* autocommands fix\r\n* quotation fix","package":"bazel-0.2.zip","4":"bazel-0.2.zip","src_id":"28531","5":"28531","creation_date":"1692430134","6":"1692430134"},{"0":"3265","vim_version":"9.0","1":"9.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"bazel-0.1.zip","4":"bazel-0.1.zip","src_id":"28527","5":"28527","creation_date":"1692328322","6":"1692328322"}]},"3264":{"script_id":"3264","0":"3264","script_name":"Vimtodo","1":"Vimtodo","script_type":"ftplugin","2":"ftplugin","summary":"Todo manager script inspired by todo.txt and org-mode","3":"Todo manager script inspired by todo.txt and org-mode","description":"Vimtodo originally started out as a set of syntax highlights for the todo.txt\r\n(http:\/\/www.todotxt.com\/) format in vim with a few added extras such as\r\nsubtasks. However, it quickly grew into a more fully featured task management\r\nsystem, taking several ideas from Emacs' org-mode.\r\n\r\nGithub: http:\/\/github.com\/mivok\/vimtodo","4":"Vimtodo originally started out as a set of syntax highlights for the todo.txt\r\n(http:\/\/www.todotxt.com\/) format in vim with a few added extras such as\r\nsubtasks. However, it quickly grew into a more fully featured task management\r\nsystem, taking several ideas from Emacs' org-mode.\r\n\r\nGithub: http:\/\/github.com\/mivok\/vimtodo","install_details":"Untar to ~\/.vim (only autoload, ftplugin, doc, syntax dirs are needed). If using pathogen, untar to ~\/.vim\/bundle\/vimtodo.","5":"Untar to ~\/.vim (only autoload, ftplugin, doc, syntax dirs are needed). If using pathogen, untar to ~\/.vim\/bundle\/vimtodo.","first_name":"Mark","6":"Mark","last_name":"Harrison","7":"Harrison","releases":[{"0":"3264","vim_version":"7.0","1":"7.0","script_version":"0.2","2":"0.2","version_comment":"Bugfixes\/documentation updates","3":"Bugfixes\/documentation updates","package":"vimtodo-0.2.tgz","4":"vimtodo-0.2.tgz","src_id":"13987","5":"13987","creation_date":"1286225075","6":"1286225075"},{"0":"3264","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"vimtodo.tgz","4":"vimtodo.tgz","src_id":"13982","5":"13982","creation_date":"1286076524","6":"1286076524"}]},"3263":{"script_id":"3263","0":"3263","script_name":"Bird Syntax","1":"Bird Syntax","script_type":"syntax","2":"syntax","summary":"Syntax highlighting for Bird configuration files","3":"Syntax highlighting for Bird configuration files","description":"This is a syntax file for the Bird Internet Routing Daemon configuration files.  It supports all keywords as of Bird version 1.2.4, along with filter, function, and protocol section folding.\r\n\r\nBird information can be found here: http:\/\/bird.network.cz\/\r\n\r\nThere isn't any accompanying file type detection, so you'll need to \":setf bird\" or use a modeline, a la:\r\n\r\n# vim: set ft=bird nosta noet ts=4 sw=4:","4":"This is a syntax file for the Bird Internet Routing Daemon configuration files.  It supports all keywords as of Bird version 1.2.4, along with filter, function, and protocol section folding.\r\n\r\nBird information can be found here: http:\/\/bird.network.cz\/\r\n\r\nThere isn't any accompanying file type detection, so you'll need to \":setf bird\" or use a modeline, a la:\r\n\r\n# vim: set ft=bird nosta noet ts=4 sw=4:","install_details":"Copy to~\/.vim\/syntax.","5":"Copy to~\/.vim\/syntax.","first_name":"Mahlon","6":"Mahlon","last_name":"Smith","7":"Smith","releases":[{"0":"3263","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"bird.vim","4":"bird.vim","src_id":"13967","5":"13967","creation_date":"1285947248","6":"1285947248"}]},"3262":{"script_id":"3262","0":"3262","script_name":"diff-fold.vim","1":"diff-fold.vim","script_type":"ftplugin","2":"ftplugin","summary":"Folds changesets, files, and hunks in Mercurial diff output","3":"Folds changesets, files, and hunks in Mercurial diff output","description":"Pipe various Mercurial diff output to vim and see changesets, files, and\r\nhunks folded nicely together.  In addition to providing folding of diff\r\ntext, diff_fold also provides a navigation pane which you can use to more\r\neasily navigate large diffs.\r\n\r\nSome examples:\r\n    hg in --patch | vim -\r\n    hg diff | vim -\r\n    hg diff -r 12 -r 13 | vim -\r\n    hg export -r 12: | vim -\r\n    hg log --patch src\\somefile.cpp | vim -\r\n\r\nNavigation pane usage:\r\n       \r\n    The keybinding <Leader>nav will bring up the navigation pane.  You can\r\n    use the 'Enter' or 'v' keys to either go to, or view whole changsets\r\n    or files in the Diff View\r\n\r\n    If you don't like the default mapping, you can map a new one as\r\n    follows:\r\n        map {newmap} <Plug>DiffFoldNav\r\n\r\nRight now, this pretty much just works with Mercurial diff output.  Because Hg can use Git style patches, it does work with some Git output but it is not 100% reliable or useful.\r\n\r\nEventually, I hope to make this work with more version control systems and just about anything that can produce unified diff output.\r\n\r\nThis plugin has also been made into a pathogen bundle and can be installed with an 'hg clone https:\/\/bitbucket.org\/thetoast\/diff-fold' in your pathogen bundle folder.\r\nIn the future, the pathogen bundle may be more up-to-date, but any major updates will be made available here.","4":"Pipe various Mercurial diff output to vim and see changesets, files, and\r\nhunks folded nicely together.  In addition to providing folding of diff\r\ntext, diff_fold also provides a navigation pane which you can use to more\r\neasily navigate large diffs.\r\n\r\nSome examples:\r\n    hg in --patch | vim -\r\n    hg diff | vim -\r\n    hg diff -r 12 -r 13 | vim -\r\n    hg export -r 12: | vim -\r\n    hg log --patch src\\somefile.cpp | vim -\r\n\r\nNavigation pane usage:\r\n       \r\n    The keybinding <Leader>nav will bring up the navigation pane.  You can\r\n    use the 'Enter' or 'v' keys to either go to, or view whole changsets\r\n    or files in the Diff View\r\n\r\n    If you don't like the default mapping, you can map a new one as\r\n    follows:\r\n        map {newmap} <Plug>DiffFoldNav\r\n\r\nRight now, this pretty much just works with Mercurial diff output.  Because Hg can use Git style patches, it does work with some Git output but it is not 100% reliable or useful.\r\n\r\nEventually, I hope to make this work with more version control systems and just about anything that can produce unified diff output.\r\n\r\nThis plugin has also been made into a pathogen bundle and can be installed with an 'hg clone https:\/\/bitbucket.org\/thetoast\/diff-fold' in your pathogen bundle folder.\r\nIn the future, the pathogen bundle may be more up-to-date, but any major updates will be made available here.","install_details":"Unzip into your ~\/.vim or vimfiles folder.","5":"Unzip into your ~\/.vim or vimfiles folder.","first_name":"Ryan","6":"Ryan","last_name":"Mechelke","7":"Mechelke","releases":[{"0":"3262","vim_version":"7.0","1":"7.0","script_version":"0.4","2":"0.4","version_comment":"* Added syntax highlighting to changeset details\r\n* Added a navigation pane for navigating large diffs","3":"* Added syntax highlighting to changeset details\r\n* Added a navigation pane for navigating large diffs","package":"diff-fold.zip","4":"diff-fold.zip","src_id":"15000","5":"15000","creation_date":"1297380191","6":"1297380191"},{"0":"3262","vim_version":"7.0","1":"7.0","script_version":"0.3.1","2":"0.3.1","version_comment":"* Fixed a bug with 'hg export' style changsets\r\n* Added foldtext for 'hg export' style changesets\r\n* Made global commands silent","3":"* Fixed a bug with 'hg export' style changsets\r\n* Added foldtext for 'hg export' style changesets\r\n* Made global commands silent","package":"diff-fold.zip","4":"diff-fold.zip","src_id":"14730","5":"14730","creation_date":"1294765706","6":"1294765706"},{"0":"3262","vim_version":"7.0","1":"7.0","script_version":"0.3","2":"0.3","version_comment":"* Adding an ftdetect script so that hg output is recognized automatically. '-c \"setlocal ft=diff\"' no longer required\r\n* Adding support for folding changesets produced by 'hg export' command\r\n* More error handling","3":"* Adding an ftdetect script so that hg output is recognized automatically. '-c \"setlocal ft=diff\"' no longer required\r\n* Adding support for folding changesets produced by 'hg export' command\r\n* More error handling","package":"diff-fold.zip","4":"diff-fold.zip","src_id":"14693","5":"14693","creation_date":"1294359015","6":"1294359015"},{"0":"3262","vim_version":"7.0","1":"7.0","script_version":"0.2","2":"0.2","version_comment":"* changed all \"exec normal\" calls to \"normal!\"\r\n* checking for existence of final hunks\/diffs\/changesets to avoid double-folding in some cases\r\n* foldtext now being set with \"setlocal\"\r\n\r\nThanks, Ingo, for the patch!\r\n","3":"* changed all \"exec normal\" calls to \"normal!\"\r\n* checking for existence of final hunks\/diffs\/changesets to avoid double-folding in some cases\r\n* foldtext now being set with \"setlocal\"\r\n\r\nThanks, Ingo, for the patch!\r\n","package":"diff_fold.vim","4":"diff_fold.vim","src_id":"13966","5":"13966","creation_date":"1285943768","6":"1285943768"},{"0":"3262","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"diff.vim","4":"diff.vim","src_id":"13965","5":"13965","creation_date":"1285904013","6":"1285904013"}]},"3261":{"script_id":"3261","0":"3261","script_name":"Selenitic","1":"Selenitic","script_type":"color scheme","2":"color scheme","summary":"Port of Visual Studio 2010 Selenetic color scheme","3":"Port of Visual Studio 2010 Selenetic color scheme","description":"Port of the Selenetic color scheme ( http:\/\/studiostyles.info\/schemes\/selenitic )","4":"Port of the Selenetic color scheme ( http:\/\/studiostyles.info\/schemes\/selenitic )","install_details":"Drop the file in ~\/.vim\/colors\r\n:color selenitic","5":"Drop the file in ~\/.vim\/colors\r\n:color selenitic","first_name":"Vincent","6":"Vincent","last_name":"B","7":"B","releases":[{"0":"3261","vim_version":"7.2","1":"7.2","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"selenitic.vim","4":"selenitic.vim","src_id":"13952","5":"13952","creation_date":"1285694143","6":"1285694143"}]},"3260":{"script_id":"3260","0":"3260","script_name":"Son of Obisidian","1":"Son of Obisidian","script_type":"color scheme","2":"color scheme","summary":"Port of Visual Studio 2010 Son of obsidian color scheme","3":"Port of Visual Studio 2010 Son of obsidian color scheme","description":"Port of a Visual Studio 2010 theme :\r\nhttp:\/\/studiostyles.info\/schemes\/son-of-obsidian","4":"Port of a Visual Studio 2010 theme :\r\nhttp:\/\/studiostyles.info\/schemes\/son-of-obsidian","install_details":"drop it in \u00c2\u00a0~\/.vim\/colors\/\r\n:color sonofobsidian","5":"drop it in \u00c2\u00a0~\/.vim\/colors\/\r\n:color sonofobsidian","first_name":"Vincent","6":"Vincent","last_name":"B","7":"B","releases":[{"0":"3260","vim_version":"7.2","1":"7.2","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"sonofobsidian.vim","4":"sonofobsidian.vim","src_id":"13951","5":"13951","creation_date":"1285693993","6":"1285693993"}]},"3259":{"script_id":"3259","0":"3259","script_name":"clang","1":"clang","script_type":"utility","2":"utility","summary":"Clang compiler definition","3":"Clang compiler definition","description":"Compiler definition for clang, use :compiler clang to use it","4":"Compiler definition for clang, use :compiler clang to use it","install_details":"drop it in ~\/.vim\/compiler","5":"drop it in ~\/.vim\/compiler","first_name":"Vincent","6":"Vincent","last_name":"B","7":"B","releases":[{"0":"3259","vim_version":"7.2","1":"7.2","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"clang.vim","4":"clang.vim","src_id":"13950","5":"13950","creation_date":"1285693727","6":"1285693727"}]},"3258":{"script_id":"3258","0":"3258","script_name":"pyunit","1":"pyunit","script_type":"ftplugin","2":"ftplugin","summary":"Quick source\/test switcher and unit test runner for Python","3":"Quick source\/test switcher and unit test runner for Python","description":"Usage\r\n-----\r\n1. Open a Python file (or its corresponding unit test file named\r\n   ``test_<filename>.py``)\r\n2. Press ``<F8>`` to run ``nosetests`` on it\r\n\r\nIt shows the errors inside a quickfix window, which will allow your to\r\nquickly jump to the error locations by simply pressing ``[Enter]``.\r\n\r\n\r\nSource files vs. test files\r\n---------------------------\r\n``vim-pyunit`` assumes that you have a single test file for each Python\r\nsource file.  The settings ``PyUnitTestPrefix``, ``PyUnitSourceRoot``,\r\n``PyUnitTestsRoot``, and ``PyUnitTestsStructure`` determine how the plugin\r\nfinds which test files belong to which source files.\r\n\r\nThe ``PyUnitTestsStructure`` setting is the most important one, because it\r\ndetermines where the PyUnit plugin searches for source and test files.\r\nThere are three options:\r\n\r\n* **flat**: Put all test files in a single test directory.  File names are\r\n  composed by resembling the source's module structure, using underscores\r\n  as separators.  For example, the test file for the source file\r\n  ``foo\/bar.py`` is called ``tests\/test_foo_bar.py``.\r\n* **side-by-side**: Put all the test files in the same directory as the\r\n  source files.  Test files are prefixed with ``test_``.  For example, the\r\n  test file for the source file ``foo\/bar.py`` is called\r\n  ``foo\/test_bar.py``.  Use this setting when testing Django apps.\r\n* **follow-hierarchy**: Put all the test files in a separate test\r\n  directory (specified by ``PyUnitTestsRoot``), but keep the same\r\n  directory hierarchy as used in the source directory.\r\n  For example, the test file for the source file ``foo\/bar.py`` is called\r\n  ``tests\/test_foo\/test_bar.py``.\r\n\r\n\r\nKeyboard mappings\r\n-----------------\r\nBy default, the ``vim-pyunit`` plugin defines the following keyboard\r\nmappings:\r\n\r\n+----------+------------------------------------------------------------+\r\n| Keymap   | Description                                                |\r\n+==========+============================================================+\r\n| F8       | Run ``nosetests`` for the current file. This mapping can   |\r\n|          | be used on both the source file, and on its corresponding  |\r\n|          | test file. Calls ``PyUnitRunTests()``                      |\r\n+----------+------------------------------------------------------------+\r\n| Shift+F8 | Run ``nosetests`` for all test files in the project, this  |\r\n|          | is equivalent to running ``nosetests`` in the root of your |\r\n|          | project. Calls ``PyUnitRunAllTests()``                     |\r\n+----------+------------------------------------------------------------+\r\n| F9       | Switch between the source and the corresponding test file. |\r\n|          | If the source or test file is not yet open, it is opened.  |\r\n|          | The setting ``tests_split_window`` is used to determine    |\r\n|          | where the file needs to be opened screen-wise. Calls       |\r\n|          | ``PyUnitSwitchToCounterpart()``                            |\r\n+----------+------------------------------------------------------------+\r\n\r\nThe plugin autodetects whether you have remapped the functions to custom\r\nkeyboard mappings.  If so, if does not register the default mappings.  So\r\nto pick your own shortcut key mappings, simply add lines like this to your\r\n``.vimrc``::\r\n\r\n    noremap ,t :call PyUnitRunTests()<CR>\r\n    noremap! ,t <Esc>:call PyUnitRunTests()<CR>\r\n\r\n(Which would map the test runner to comma-T. ``<F8>`` then remains what it\r\nwas.)\r\n\r\nIf you wish to disable any automatic keyboard mapping, simply set::\r\n\r\n    let no_pyunit_maps = 1\r\n\r\n\r\nConfiguration\r\n-------------\r\nThe plugin supports setting of the following variables:\r\n\r\n+-------------------------------+------------------------------------------------+---------------------------+-----------------------------------+\r\n| Variable                      | Description                                    | Values                    | Default                           |\r\n+===============================+================================================+===========================+===================================+\r\n| ``PyUnitShowTests``           | Shows the tests.                               | 0 or 1                    | 1                                 |\r\n+-------------------------------+------------------------------------------------+---------------------------+-----------------------------------+\r\n| ``PyUnitCmd``                 | The command to run the unit test.              | any string                | \"nosetests -q --with-machineout\"  |\r\n+-------------------------------+------------------------------------------------+---------------------------+-----------------------------------+\r\n| ``ProjRootIndicators``        | List of filenames indicating the project root. | list of file names        | [\".git\", \"setup.py\", \"setup.cfg\"] |\r\n+-------------------------------+------------------------------------------------+---------------------------+-----------------------------------+\r\n| ``ProjRootStopAtHomeDir``     | Stop the search for the project root at the    | 0 or 1                    | 1                                 |\r\n|                               | user's home dir.                               |                           |                                   |\r\n+-------------------------------+------------------------------------------------+---------------------------+-----------------------------------+\r\n| ``PyUnitTestPrefix``          | The filename prefix to use for test files.     | any string                | \"test\\_\"                          |\r\n+-------------------------------+------------------------------------------------+---------------------------+-----------------------------------+\r\n| ``PyUnitTestSuffix``          | *Not implemented yet*                          | 0 or 1                    | n\/a                               |\r\n+-------------------------------+------------------------------------------------+---------------------------+-----------------------------------+\r\n| ``PyUnitSourceRoot``          | The relative location where all source files   | directory spec, or empty  | \"\"                                |\r\n|                               | live.                                          |                           |                                   |\r\n+-------------------------------+------------------------------------------------+---------------------------+-----------------------------------+\r\n| ``PyUnitTestsRoot``           | The relative location where all tests live.    | directory spec            | \"tests\"                           |\r\n+-------------------------------+------------------------------------------------+---------------------------+-----------------------------------+\r\n| ``PyUnitTestsStructure``      | Specifies how you wish to organise your tests. | flat, follow-hierarchy,   | \"follow-hierarchy\"                |\r\n|                               |                                                | side-by-side              |                                   |\r\n+-------------------------------+------------------------------------------------+---------------------------+-----------------------------------+\r\n| ``PyUnitTestsSplitWindow``    | Specifies where test files should be opened,   | left, right, top, bottom, | \"right\"                           |\r\n|                               | when oopened next to the source file. When set | no                        |                                   |\r\n|                               | to ``no``, doesn't open a new window at all,   |                           |                                   |\r\n|                               | but reuses the current buffer.                 |                           |                                   |\r\n+-------------------------------+------------------------------------------------+---------------------------+-----------------------------------+\r\n| ``PyUnitConfirmTestCreation`` | Ask to confirm creation of new test files.     | 0 or 1                    | 1                                 |\r\n+-------------------------------+------------------------------------------------+---------------------------+-----------------------------------+\r\n\r\n\r\nTips\r\n----\r\nThis plugin goes well together with the following plugins:\r\n\r\n- PEP8_ (Python coding style checker under ``<F6>``)\r\n- PyFlakes_ (Python static syntax checker under ``<F7>``)\r\n\r\n.. _PEP8: http:\/\/github.com\/nvie\/vim-pep8\r\n.. _PyFlakes: http:\/\/github.com\/nvie\/vim-pyflakes\r\n","4":"Usage\r\n-----\r\n1. Open a Python file (or its corresponding unit test file named\r\n   ``test_<filename>.py``)\r\n2. Press ``<F8>`` to run ``nosetests`` on it\r\n\r\nIt shows the errors inside a quickfix window, which will allow your to\r\nquickly jump to the error locations by simply pressing ``[Enter]``.\r\n\r\n\r\nSource files vs. test files\r\n---------------------------\r\n``vim-pyunit`` assumes that you have a single test file for each Python\r\nsource file.  The settings ``PyUnitTestPrefix``, ``PyUnitSourceRoot``,\r\n``PyUnitTestsRoot``, and ``PyUnitTestsStructure`` determine how the plugin\r\nfinds which test files belong to which source files.\r\n\r\nThe ``PyUnitTestsStructure`` setting is the most important one, because it\r\ndetermines where the PyUnit plugin searches for source and test files.\r\nThere are three options:\r\n\r\n* **flat**: Put all test files in a single test directory.  File names are\r\n  composed by resembling the source's module structure, using underscores\r\n  as separators.  For example, the test file for the source file\r\n  ``foo\/bar.py`` is called ``tests\/test_foo_bar.py``.\r\n* **side-by-side**: Put all the test files in the same directory as the\r\n  source files.  Test files are prefixed with ``test_``.  For example, the\r\n  test file for the source file ``foo\/bar.py`` is called\r\n  ``foo\/test_bar.py``.  Use this setting when testing Django apps.\r\n* **follow-hierarchy**: Put all the test files in a separate test\r\n  directory (specified by ``PyUnitTestsRoot``), but keep the same\r\n  directory hierarchy as used in the source directory.\r\n  For example, the test file for the source file ``foo\/bar.py`` is called\r\n  ``tests\/test_foo\/test_bar.py``.\r\n\r\n\r\nKeyboard mappings\r\n-----------------\r\nBy default, the ``vim-pyunit`` plugin defines the following keyboard\r\nmappings:\r\n\r\n+----------+------------------------------------------------------------+\r\n| Keymap   | Description                                                |\r\n+==========+============================================================+\r\n| F8       | Run ``nosetests`` for the current file. This mapping can   |\r\n|          | be used on both the source file, and on its corresponding  |\r\n|          | test file. Calls ``PyUnitRunTests()``                      |\r\n+----------+------------------------------------------------------------+\r\n| Shift+F8 | Run ``nosetests`` for all test files in the project, this  |\r\n|          | is equivalent to running ``nosetests`` in the root of your |\r\n|          | project. Calls ``PyUnitRunAllTests()``                     |\r\n+----------+------------------------------------------------------------+\r\n| F9       | Switch between the source and the corresponding test file. |\r\n|          | If the source or test file is not yet open, it is opened.  |\r\n|          | The setting ``tests_split_window`` is used to determine    |\r\n|          | where the file needs to be opened screen-wise. Calls       |\r\n|          | ``PyUnitSwitchToCounterpart()``                            |\r\n+----------+------------------------------------------------------------+\r\n\r\nThe plugin autodetects whether you have remapped the functions to custom\r\nkeyboard mappings.  If so, if does not register the default mappings.  So\r\nto pick your own shortcut key mappings, simply add lines like this to your\r\n``.vimrc``::\r\n\r\n    noremap ,t :call PyUnitRunTests()<CR>\r\n    noremap! ,t <Esc>:call PyUnitRunTests()<CR>\r\n\r\n(Which would map the test runner to comma-T. ``<F8>`` then remains what it\r\nwas.)\r\n\r\nIf you wish to disable any automatic keyboard mapping, simply set::\r\n\r\n    let no_pyunit_maps = 1\r\n\r\n\r\nConfiguration\r\n-------------\r\nThe plugin supports setting of the following variables:\r\n\r\n+-------------------------------+------------------------------------------------+---------------------------+-----------------------------------+\r\n| Variable                      | Description                                    | Values                    | Default                           |\r\n+===============================+================================================+===========================+===================================+\r\n| ``PyUnitShowTests``           | Shows the tests.                               | 0 or 1                    | 1                                 |\r\n+-------------------------------+------------------------------------------------+---------------------------+-----------------------------------+\r\n| ``PyUnitCmd``                 | The command to run the unit test.              | any string                | \"nosetests -q --with-machineout\"  |\r\n+-------------------------------+------------------------------------------------+---------------------------+-----------------------------------+\r\n| ``ProjRootIndicators``        | List of filenames indicating the project root. | list of file names        | [\".git\", \"setup.py\", \"setup.cfg\"] |\r\n+-------------------------------+------------------------------------------------+---------------------------+-----------------------------------+\r\n| ``ProjRootStopAtHomeDir``     | Stop the search for the project root at the    | 0 or 1                    | 1                                 |\r\n|                               | user's home dir.                               |                           |                                   |\r\n+-------------------------------+------------------------------------------------+---------------------------+-----------------------------------+\r\n| ``PyUnitTestPrefix``          | The filename prefix to use for test files.     | any string                | \"test\\_\"                          |\r\n+-------------------------------+------------------------------------------------+---------------------------+-----------------------------------+\r\n| ``PyUnitTestSuffix``          | *Not implemented yet*                          | 0 or 1                    | n\/a                               |\r\n+-------------------------------+------------------------------------------------+---------------------------+-----------------------------------+\r\n| ``PyUnitSourceRoot``          | The relative location where all source files   | directory spec, or empty  | \"\"                                |\r\n|                               | live.                                          |                           |                                   |\r\n+-------------------------------+------------------------------------------------+---------------------------+-----------------------------------+\r\n| ``PyUnitTestsRoot``           | The relative location where all tests live.    | directory spec            | \"tests\"                           |\r\n+-------------------------------+------------------------------------------------+---------------------------+-----------------------------------+\r\n| ``PyUnitTestsStructure``      | Specifies how you wish to organise your tests. | flat, follow-hierarchy,   | \"follow-hierarchy\"                |\r\n|                               |                                                | side-by-side              |                                   |\r\n+-------------------------------+------------------------------------------------+---------------------------+-----------------------------------+\r\n| ``PyUnitTestsSplitWindow``    | Specifies where test files should be opened,   | left, right, top, bottom, | \"right\"                           |\r\n|                               | when oopened next to the source file. When set | no                        |                                   |\r\n|                               | to ``no``, doesn't open a new window at all,   |                           |                                   |\r\n|                               | but reuses the current buffer.                 |                           |                                   |\r\n+-------------------------------+------------------------------------------------+---------------------------+-----------------------------------+\r\n| ``PyUnitConfirmTestCreation`` | Ask to confirm creation of new test files.     | 0 or 1                    | 1                                 |\r\n+-------------------------------+------------------------------------------------+---------------------------+-----------------------------------+\r\n\r\n\r\nTips\r\n----\r\nThis plugin goes well together with the following plugins:\r\n\r\n- PEP8_ (Python coding style checker under ``<F6>``)\r\n- PyFlakes_ (Python static syntax checker under ``<F7>``)\r\n\r\n.. _PEP8: http:\/\/github.com\/nvie\/vim-pep8\r\n.. _PyFlakes: http:\/\/github.com\/nvie\/vim-pyflakes\r\n","install_details":"Installation\r\n------------\r\n1. Install the following packages from PyPI:\r\n\r\n   - nose_: the unit test runner;\r\n   - nose_machineout_:  The ``machineout`` plugin formats the ``nose`` output\r\n     so that Vim can parse it more easily;\r\n   - vim_bridge_:  This is required for the vim plugin scripts, to call\r\n     directly into Python functions.\r\n\r\n2. Clone the git repository::\r\n\r\n       git clone git:\/\/github.com\/nvie\/vim-pyunit.git\r\n       cd vim-pyunit\r\n\r\n3. Copy the file ``ftplugin\/python_pyunit.vim`` to your ``~\/.vim\/ftplugin``\r\n   directory\r\n\r\n.. _nose: http:\/\/pypi.python.org\/pypi\/nose\r\n.. _nose_machineout: http:\/\/pypi.python.org\/pypi\/nose_machineout\r\n.. _vim_bridge: http:\/\/pypi.python.org\/pypi\/vim_bridge\r\n","5":"Installation\r\n------------\r\n1. Install the following packages from PyPI:\r\n\r\n   - nose_: the unit test runner;\r\n   - nose_machineout_:  The ``machineout`` plugin formats the ``nose`` output\r\n     so that Vim can parse it more easily;\r\n   - vim_bridge_:  This is required for the vim plugin scripts, to call\r\n     directly into Python functions.\r\n\r\n2. Clone the git repository::\r\n\r\n       git clone git:\/\/github.com\/nvie\/vim-pyunit.git\r\n       cd vim-pyunit\r\n\r\n3. Copy the file ``ftplugin\/python_pyunit.vim`` to your ``~\/.vim\/ftplugin``\r\n   directory\r\n\r\n.. _nose: http:\/\/pypi.python.org\/pypi\/nose\r\n.. _nose_machineout: http:\/\/pypi.python.org\/pypi\/nose_machineout\r\n.. _vim_bridge: http:\/\/pypi.python.org\/pypi\/vim_bridge\r\n","first_name":"Vincent","6":"Vincent","last_name":"Driessen","7":"Driessen","releases":[{"0":"3258","vim_version":"7.0","1":"7.0","script_version":"0.3","2":"0.3","version_comment":"Initial upload","3":"Initial upload","package":"python_pyunit.vim","4":"python_pyunit.vim","src_id":"13944","5":"13944","creation_date":"1285620664","6":"1285620664"}]},"3257":{"script_id":"3257","0":"3257","script_name":"Say Time","1":"Say Time","script_type":"utility","2":"utility","summary":"Say time date and time through speakers every 1\/2 hr","3":"Say time date and time through speakers every 1\/2 hr","description":"For Windows.  It is handy to know what day and time it is but it is easy to forget.  This program reminds you of that every half hour.  Says:  day of week, day of month, month, and time in 24-hour format.  Not a vimscript, but seems relevant.  You might also try my gradually changing color scheme for vim: http:\/\/www.vim.org\/scripts\/script.php?script_id=2658.","4":"For Windows.  It is handy to know what day and time it is but it is easy to forget.  This program reminds you of that every half hour.  Says:  day of week, day of month, month, and time in 24-hour format.  Not a vimscript, but seems relevant.  You might also try my gradually changing color scheme for vim: http:\/\/www.vim.org\/scripts\/script.php?script_id=2658.","install_details":"Download AutoIT 3.0 for Windows if you haven't already got it.  Search Google.  Once installed simply compile saytime.au3 and run .exe.  AutoIT 3.0 installer creates entries in the right-click context menu of Explorer to allow you to create the .exe.  I advice to put a shortcut to it in your Windows start-up group, or start it manually.","5":"Download AutoIT 3.0 for Windows if you haven't already got it.  Search Google.  Once installed simply compile saytime.au3 and run .exe.  AutoIT 3.0 installer creates entries in the right-click context menu of Explorer to allow you to create the .exe.  I advice to put a shortcut to it in your Windows start-up group, or start it manually.","first_name":"Paul","6":"Paul","last_name":"Contreras","7":"Contreras","releases":[{"0":"3257","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Corrected a poorly worded comment, because its point was important","3":"Corrected a poorly worded comment, because its point was important","package":"saytime.au3","4":"saytime.au3","src_id":"13940","5":"13940","creation_date":"1285597690","6":"1285597690"},{"0":"3257","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"saytime.au3","4":"saytime.au3","src_id":"13935","5":"13935","creation_date":"1285590258","6":"1285590258"}]},"3256":{"script_id":"3256","0":"3256","script_name":"phaver","1":"phaver","script_type":"syntax","2":"syntax","summary":"phaver syntax highlighting script ","3":"phaver syntax highlighting script ","description":"A very simple syntax highlighting script for the phaver language","4":"A very simple syntax highlighting script for the phaver language","install_details":"Place phaver.vim file in ~\/.vim\/syntax\/ folder.\r\nadd \"au BufNewFile,BufRead *.pha \t\t\tsetf phaver\" to $VIM_HOME\/filetype.vim\r\n","5":"Place phaver.vim file in ~\/.vim\/syntax\/ folder.\r\nadd \"au BufNewFile,BufRead *.pha \t\t\tsetf phaver\" to $VIM_HOME\/filetype.vim\r\n","first_name":"huang","6":"huang","last_name":"chongdi","7":"chongdi","releases":[{"0":"3256","vim_version":"7.0","1":"7.0","script_version":"0.11","2":"0.11","version_comment":"change some syntax highlighting setting","3":"change some syntax highlighting setting","package":"phaver.vim","4":"phaver.vim","src_id":"14032","5":"14032","creation_date":"1286589087","6":"1286589087"},{"0":"3256","vim_version":"7.2","1":"7.2","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"phaver.vim","4":"phaver.vim","src_id":"13930","5":"13930","creation_date":"1285569070","6":"1285569070"}]},"3255":{"script_id":"3255","0":"3255","script_name":"sequence","1":"sequence","script_type":"utility","2":"utility","summary":"Increment \/ Decrement a sequence of numbers","3":"Increment \/ Decrement a sequence of numbers","description":"Usage:\r\n\r\nPut the cursor anywhere on these lines. The range will be guessed and the first\r\nsequence of numbers will be transformed. If you want to transform the second\r\nsequence of numbers you must use a visual block selection (dashes in this\r\nexample).\r\n\r\narray [1] = 9              array [1] = -9-              array [1] = 9\r\narray [1] = 9              array [2] = -9-              array [2] = 8\r\narray [1] = 9    alt-a:    array [3] = -9-    alt-x:    array [3] = 7\r\narray [1] = 9              array [4] = -9-              array [4] = 6\r\narray [1] = 9              array [5] = -9-              array [5] = 5\r\n\r\nWith a count:\r\n\r\narray [1] = 9                array [1] = -9-                array [1] = 9\r\narray [1] = 9                array [3] = -9-                array [3] = 7\r\narray [1] = 9    2 alt-a:    array [5] = -9-    2 alt-x:    array [5] = 5\r\narray [1] = 9                array [7] = -9-                array [7] = 3\r\narray [1] = 9                array [9] = -9-                array [9] = 1\r\n\r\nNote: If the range is not easy to guess, use a selection instead\r\n\r\nIf you wanted to increment \/ decrement all numbers by only one, select your\r\nlines and press ^a \/ ^x\r\n\r\n   v mode                     ^v mode\r\narray [1] = 8             array [6] = -8-             array [6] = 5\r\narray [1] = 8             array [6] = -8-             array [6] = 5\r\narray [1] = 8    5 ^a:    array [6] = -8-    3 ^x:    array [6] = 5\r\narray [1] = 8             array [6] = -8-             array [6] = 5\r\narray [1] = 8             array [6] = -8-             array [6] = 5\r\n\r\n----------------------------------------------------------------------------\r\n\r\nThis plugin integrates with Tim Pope's repeat plugin. It means that you can use\r\n. to repeat any normal mode (for now) sequence mapping you just used!\r\n\r\nFor more information see: http:\/\/github.com\/tpope\/vim-repeat\r\n\r\n----------------------------------------------------------------------------\r\n\r\nYou have the possibility to define your own custom mappings in your .vimrc:\r\n\r\n    vmap <m-a> <plug>SequenceV_Increment\r\n    vmap <m-x> <plug>SequenceV_Decrement\r\n    nmap <m-a> <plug>SequenceN_Increment\r\n    nmap <m-x> <plug>SequenceN_Decrement\r\n\r\n    vmap <c-a> <plug>SequenceAdd\r\n    vmap <c-x> <plug>SequenceSubtract\r\n\r\nNote: You can replace Alt+a, Alt+x, Ctrl+a and Ctrl+x with whatever you like.","4":"Usage:\r\n\r\nPut the cursor anywhere on these lines. The range will be guessed and the first\r\nsequence of numbers will be transformed. If you want to transform the second\r\nsequence of numbers you must use a visual block selection (dashes in this\r\nexample).\r\n\r\narray [1] = 9              array [1] = -9-              array [1] = 9\r\narray [1] = 9              array [2] = -9-              array [2] = 8\r\narray [1] = 9    alt-a:    array [3] = -9-    alt-x:    array [3] = 7\r\narray [1] = 9              array [4] = -9-              array [4] = 6\r\narray [1] = 9              array [5] = -9-              array [5] = 5\r\n\r\nWith a count:\r\n\r\narray [1] = 9                array [1] = -9-                array [1] = 9\r\narray [1] = 9                array [3] = -9-                array [3] = 7\r\narray [1] = 9    2 alt-a:    array [5] = -9-    2 alt-x:    array [5] = 5\r\narray [1] = 9                array [7] = -9-                array [7] = 3\r\narray [1] = 9                array [9] = -9-                array [9] = 1\r\n\r\nNote: If the range is not easy to guess, use a selection instead\r\n\r\nIf you wanted to increment \/ decrement all numbers by only one, select your\r\nlines and press ^a \/ ^x\r\n\r\n   v mode                     ^v mode\r\narray [1] = 8             array [6] = -8-             array [6] = 5\r\narray [1] = 8             array [6] = -8-             array [6] = 5\r\narray [1] = 8    5 ^a:    array [6] = -8-    3 ^x:    array [6] = 5\r\narray [1] = 8             array [6] = -8-             array [6] = 5\r\narray [1] = 8             array [6] = -8-             array [6] = 5\r\n\r\n----------------------------------------------------------------------------\r\n\r\nThis plugin integrates with Tim Pope's repeat plugin. It means that you can use\r\n. to repeat any normal mode (for now) sequence mapping you just used!\r\n\r\nFor more information see: http:\/\/github.com\/tpope\/vim-repeat\r\n\r\n----------------------------------------------------------------------------\r\n\r\nYou have the possibility to define your own custom mappings in your .vimrc:\r\n\r\n    vmap <m-a> <plug>SequenceV_Increment\r\n    vmap <m-x> <plug>SequenceV_Decrement\r\n    nmap <m-a> <plug>SequenceN_Increment\r\n    nmap <m-x> <plug>SequenceN_Decrement\r\n\r\n    vmap <c-a> <plug>SequenceAdd\r\n    vmap <c-x> <plug>SequenceSubtract\r\n\r\nNote: You can replace Alt+a, Alt+x, Ctrl+a and Ctrl+x with whatever you like.","install_details":"sequence.vim -> ~\/.vim\/plugin\r\nsequence.txt -> ~\/.vim\/doc\r\n\r\nLatest version at:\r\nhttps:\/\/github.com\/kurkale6ka\/vim-sequence","5":"sequence.vim -> ~\/.vim\/plugin\r\nsequence.txt -> ~\/.vim\/doc\r\n\r\nLatest version at:\r\nhttps:\/\/github.com\/kurkale6ka\/vim-sequence","first_name":"Dimitar","6":"Dimitar","last_name":"Dimitrov","7":"Dimitrov","releases":[{"0":"3255","vim_version":"7.0","1":"7.0","script_version":"2.0","2":"2.0","version_comment":"Made the plugin mappings more flexible: you could redefine them in your .vimrc if you wanted\r\nAdded support for Tim Pope's repeat plugin in normal mode","3":"Made the plugin mappings more flexible: you could redefine them in your .vimrc if you wanted\r\nAdded support for Tim Pope's repeat plugin in normal mode","package":"sequence.zip","4":"sequence.zip","src_id":"14008","5":"14008","creation_date":"1286364514","6":"1286364514"},{"0":"3255","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"sequence.zip","4":"sequence.zip","src_id":"13923","5":"13923","creation_date":"1285512370","6":"1285512370"}]},"3254":{"script_id":"3254","0":"3254","script_name":"ora-workbench","1":"ora-workbench","script_type":"utility","2":"utility","summary":"A workbench for Oracle databases","3":"A workbench for Oracle databases","description":"The ORA-Workbench is a VIM plugin to use VIM a development environment for\r\nORACLE databases. \r\n\r\nThe ORA-Workbench shows the typical layout of modern development environment consiting\r\nof:\r\n\t- the object tree on the left side\r\n\t- a editing area in upper right \r\n\t- a \"log\" window in the lower right\r\n\r\nThe workbench requires a Oracle Client installation (I'm calling SQLPLUS). The\r\nprogram \"sqlplus\" must be in the \"path\". \r\n\r\nThis plugin has been tested with:\r\n\t- vim*7.2, vim*7.3\r\n\t- ORACLE*10.2, ORACLE*11g\r\n\t- MS Windows 2000\r\n\t- SUSE Linux*10, SUSE Linux*11\r\n","4":"The ORA-Workbench is a VIM plugin to use VIM a development environment for\r\nORACLE databases. \r\n\r\nThe ORA-Workbench shows the typical layout of modern development environment consiting\r\nof:\r\n\t- the object tree on the left side\r\n\t- a editing area in upper right \r\n\t- a \"log\" window in the lower right\r\n\r\nThe workbench requires a Oracle Client installation (I'm calling SQLPLUS). The\r\nprogram \"sqlplus\" must be in the \"path\". \r\n\r\nThis plugin has been tested with:\r\n\t- vim*7.2, vim*7.3\r\n\t- ORACLE*10.2, ORACLE*11g\r\n\t- MS Windows 2000\r\n\t- SUSE Linux*10, SUSE Linux*11\r\n","install_details":"- create the directory \".vim\" (for linux systems) or \"vimfiles\"\r\n\t  (MS-Windows system) in your home directory.\r\n- create the sub-directory \"plugin\"\r\n- copy the file \"orawb.vim\" into the \"plugin\" directory\r\n- create the sub-directory \"doc\"\r\n- copy the file \"orawb.txt\" into the \"dic\" directory.\r\n- start vim\r\n- execute the command \":helptags ~\/.vim\/doc\" (linux) or \r\n  \":helptags ~\/vimfiles\/doc\" (Windows)\r\n- make sure that \"sqlplus\" is in your operation system PATH.","5":"- create the directory \".vim\" (for linux systems) or \"vimfiles\"\r\n\t  (MS-Windows system) in your home directory.\r\n- create the sub-directory \"plugin\"\r\n- copy the file \"orawb.vim\" into the \"plugin\" directory\r\n- create the sub-directory \"doc\"\r\n- copy the file \"orawb.txt\" into the \"dic\" directory.\r\n- start vim\r\n- execute the command \":helptags ~\/.vim\/doc\" (linux) or \r\n  \":helptags ~\/vimfiles\/doc\" (Windows)\r\n- make sure that \"sqlplus\" is in your operation system PATH.","first_name":"Robert","6":"Robert","last_name":"Kaltenthaler","7":"Kaltenthaler","releases":[{"0":"3254","vim_version":"7.0","1":"7.0","script_version":"1.12","2":"1.12","version_comment":"Bug-Fix: describe improved","3":"Bug-Fix: describe improved","package":"orawb.tgz","4":"orawb.tgz","src_id":"27719","5":"27719","creation_date":"1629952881","6":"1629952881"},{"0":"3254","vim_version":"7.0","1":"7.0","script_version":"1.11","2":"1.11","version_comment":"Support for local connect and easy-connect added.","3":"Support for local connect and easy-connect added.","package":"orawb.tgz","4":"orawb.tgz","src_id":"27716","5":"27716","creation_date":"1629765916","6":"1629765916"},{"0":"3254","vim_version":"7.0","1":"7.0","script_version":"1.10","2":"1.10","version_comment":"This new version includes the command Yprint to create DDL files \r\nfor most of the objects in the database.","3":"This new version includes the command Yprint to create DDL files \r\nfor most of the objects in the database.","package":"orawb.tgz","4":"orawb.tgz","src_id":"21232","5":"21232","creation_date":"1387842776","6":"1387842776"},{"0":"3254","vim_version":"7.0","1":"7.0","script_version":"1.9","2":"1.9","version_comment":"The \"workbench\" is now able to display database links.","3":"The \"workbench\" is now able to display database links.","package":"orawb.tgz","4":"orawb.tgz","src_id":"19789","5":"19789","creation_date":"1365498883","6":"1365498883"},{"0":"3254","vim_version":"7.0","1":"7.0","script_version":"1.8","2":"1.8","version_comment":"Bug-fix: you can now save the content of a worksheet to a file using \":sav <filename>\"","3":"Bug-fix: you can now save the content of a worksheet to a file using \":sav <filename>\"","package":"orawb.tgz","4":"orawb.tgz","src_id":"19745","5":"19745","creation_date":"1364852574","6":"1364852574"},{"0":"3254","vim_version":"7.0","1":"7.0","script_version":"1.7","2":"1.7","version_comment":"The workbench is now able to open \"synonyms\" with the \r\ncommand \":Yopen\". \r\nYou will get the DDL script to create or replace the synonym. \r\nOkay - just a small thing, but I'm using lot of\r\nsynonyms.\r\n","3":"The workbench is now able to open \"synonyms\" with the \r\ncommand \":Yopen\". \r\nYou will get the DDL script to create or replace the synonym. \r\nOkay - just a small thing, but I'm using lot of\r\nsynonyms.\r\n","package":"orawb.tgz","4":"orawb.tgz","src_id":"19600","5":"19600","creation_date":"1362608194","6":"1362608194"},{"0":"3254","vim_version":"7.3","1":"7.3","script_version":"1.6","2":"1.6","version_comment":"The build-in \"omni-completion\" function now covers column names and function \/ procedure name from packages.","3":"The build-in \"omni-completion\" function now covers column names and function \/ procedure name from packages.","package":"orawb.tgz","4":"orawb.tgz","src_id":"19236","5":"19236","creation_date":"1356367819","6":"1356367819"},{"0":"3254","vim_version":"7.0","1":"7.0","script_version":"1.5","2":"1.5","version_comment":"Bug-fix: The sort-order of source code lines can be mixed up. This could happen when you open a package body from the database. This is error has been fixed.","3":"Bug-fix: The sort-order of source code lines can be mixed up. This could happen when you open a package body from the database. This is error has been fixed.","package":"orawb.tgz","4":"orawb.tgz","src_id":"18402","5":"18402","creation_date":"1344980125","6":"1344980125"},{"0":"3254","vim_version":"7.0","1":"7.0","script_version":"1.4","2":"1.4","version_comment":"Now you can supply the connection information (user\/password\/database) together with the commands \"Yshow\" and \"Yconnect\"","3":"Now you can supply the connection information (user\/password\/database) together with the commands \"Yshow\" and \"Yconnect\"","package":"orawb.tgz","4":"orawb.tgz","src_id":"16786","5":"16786","creation_date":"1320252573","6":"1320252573"},{"0":"3254","vim_version":"7.2","1":"7.2","script_version":"1.2","2":"1.2","version_comment":"The \"normal mode\" keys are now the same as the command line keys (ym-->Ym, yd -->Yd...).\r\nThe commands can be used without calling \"Yshow\" to display the database meta information.\r\n\r\n","3":"The \"normal mode\" keys are now the same as the command line keys (ym-->Ym, yd -->Yd...).\r\nThe commands can be used without calling \"Yshow\" to display the database meta information.\r\n\r\n","package":"orawb.tgz","4":"orawb.tgz","src_id":"16693","5":"16693","creation_date":"1318916921","6":"1318916921"},{"0":"3254","vim_version":"7.0","1":"7.0","script_version":"1.1","2":"1.1","version_comment":"The key-mapping to execute SQL commands is now\r\navailable for all buffers.\r\nThe (new) command Yw[orksheet] creates a new SQL worksheet.","3":"The key-mapping to execute SQL commands is now\r\navailable for all buffers.\r\nThe (new) command Yw[orksheet] creates a new SQL worksheet.","package":"orawb.zip","4":"orawb.zip","src_id":"14122","5":"14122","creation_date":"1288076860","6":"1288076860"},{"0":"3254","vim_version":"7.2","1":"7.2","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"orawb.zip","4":"orawb.zip","src_id":"13920","5":"13920","creation_date":"1285494508","6":"1285494508"}]},"3253":{"script_id":"3253","0":"3253","script_name":"makesd.vim","1":"makesd.vim","script_type":"utility","2":"utility","summary":"Generate Perl and C-style section dividers","3":"Generate Perl and C-style section dividers","description":"This is a simple plugin to generate fancy-looking comments \/ section dividers with centered titles and append them at the current cursor position. For an example, see:\r\n\r\nhttp:\/\/www.chaseventers.org\/2010\/09\/vim-plugin-makesdmakecsd.html","4":"This is a simple plugin to generate fancy-looking comments \/ section dividers with centered titles and append them at the current cursor position. For an example, see:\r\n\r\nhttp:\/\/www.chaseventers.org\/2010\/09\/vim-plugin-makesdmakecsd.html","install_details":"Install to ~\/.vim\/plugin\/ or C:\\YourHomeDir\\vimfiles\\plugin","5":"Install to ~\/.vim\/plugin\/ or C:\\YourHomeDir\\vimfiles\\plugin","first_name":"Chase","6":"Chase","last_name":"Venters","7":"Venters","releases":[{"0":"3253","vim_version":"7.0","1":"7.0","script_version":"0.01","2":"0.01","version_comment":"Initial upload","3":"Initial upload","package":"makesd.vim","4":"makesd.vim","src_id":"13913","5":"13913","creation_date":"1285377383","6":"1285377383"}]},"3252":{"script_id":"3252","0":"3252","script_name":"L9","1":"L9","script_type":"utility","2":"utility","summary":"Vim-script library","3":"Vim-script library","description":"Repository:\r\n  https:\/\/bitbucket.org\/ns9tks\/vim-l9\/\r\n\r\nIssues:\r\n  http:\/\/bitbucket.org\/ns9tks\/vim-l9\/issues\/\r\n\r\nDownload latest(development) version\r\n  https:\/\/bitbucket.org\/ns9tks\/vim-l9\/get\/tip.zip\r\n\r\n\r\n==============================================================================\r\nINTRODUCTION                                                 *l9-introduction*\r\n\r\nl9 is a Vim-script library, which provides some utility functions and commands\r\nfor programming in Vim.\r\n\r\n==============================================================================\r\n INSTALLATION                                                *l9-installation*\r\n\r\nPut all files into your runtime directory. If you have the zip file, extract\r\nit to your runtime directory.\r\n\r\nYou should place the files as follows:\r\n>\r\n        <your runtime directory>\/plugin\/l9.vim\r\n        <your runtime directory>\/doc\/l9.txt\r\n        ...\r\n<\r\nIf you are disgusted to make your runtime directory confused with a lot of\r\nplugins, put each of the plugins into a directory individually and just add\r\nthe directory path to 'runtimepath'. It's easy to uninstall plugins.\r\n\r\nThen update your help tags files to enable help for this plugin. See\r\n|add-local-help| for details.\r\n\r\n==============================================================================\r\nUSAGE                                                               *l9-usage*\r\n\r\nSee source code.\r\n\r\n==============================================================================\r\n","4":"Repository:\r\n  https:\/\/bitbucket.org\/ns9tks\/vim-l9\/\r\n\r\nIssues:\r\n  http:\/\/bitbucket.org\/ns9tks\/vim-l9\/issues\/\r\n\r\nDownload latest(development) version\r\n  https:\/\/bitbucket.org\/ns9tks\/vim-l9\/get\/tip.zip\r\n\r\n\r\n==============================================================================\r\nINTRODUCTION                                                 *l9-introduction*\r\n\r\nl9 is a Vim-script library, which provides some utility functions and commands\r\nfor programming in Vim.\r\n\r\n==============================================================================\r\n INSTALLATION                                                *l9-installation*\r\n\r\nPut all files into your runtime directory. If you have the zip file, extract\r\nit to your runtime directory.\r\n\r\nYou should place the files as follows:\r\n>\r\n        <your runtime directory>\/plugin\/l9.vim\r\n        <your runtime directory>\/doc\/l9.txt\r\n        ...\r\n<\r\nIf you are disgusted to make your runtime directory confused with a lot of\r\nplugins, put each of the plugins into a directory individually and just add\r\nthe directory path to 'runtimepath'. It's easy to uninstall plugins.\r\n\r\nThen update your help tags files to enable help for this plugin. See\r\n|add-local-help| for details.\r\n\r\n==============================================================================\r\nUSAGE                                                               *l9-usage*\r\n\r\nSee source code.\r\n\r\n==============================================================================\r\n","install_details":"","5":"","first_name":"Takeshi","6":"Takeshi","last_name":"NISHIDA","7":"NISHIDA","releases":[{"0":"3252","vim_version":"7.2","1":"7.2","script_version":"1.1","2":"1.1","version_comment":"- Added l9#zip()\r\n- Added l9#tempvariables#getList()\r\n- Changed l9#guardScriptLoading()\r\n- Removed l9#tempvariables#swap()\r\n","3":"- Added l9#zip()\r\n- Added l9#tempvariables#getList()\r\n- Changed l9#guardScriptLoading()\r\n- Removed l9#tempvariables#swap()\r\n","package":"vim-l9.zip","4":"vim-l9.zip","src_id":"13948","5":"13948","creation_date":"1285686540","6":"1285686540"},{"0":"3252","vim_version":"7.2","1":"7.2","script_version":"1.0.1","2":"1.0.1","version_comment":"- Fixed a bug that floating point numbers weren't evaluated correctly and\r\n  caused errors on some non-English locales.\r\n","3":"- Fixed a bug that floating point numbers weren't evaluated correctly and\r\n  caused errors on some non-English locales.\r\n","package":"vim-l9.zip","4":"vim-l9.zip","src_id":"13936","5":"13936","creation_date":"1285595625","6":"1285595625"},{"0":"3252","vim_version":"7.2","1":"7.2","script_version":"1.0","2":"1.0","version_comment":"Initial","3":"Initial","package":"vim-l9.zip","4":"vim-l9.zip","src_id":"13907","5":"13907","creation_date":"1285340122","6":"1285340122"}]},"3251":{"script_id":"3251","0":"3251","script_name":"RubyProxy","1":"RubyProxy","script_type":"utility","2":"utility","summary":"Makes most of vims functions available to ruby via a proxy. ","3":"Makes most of vims functions available to ruby via a proxy. ","description":"RubyProxy\r\nRubyProxy acts as a proxy between ruby and vim, so that most of vims functions are usable in ruby. Only the functions, which accepts lists and dictionary won't work. And functions, which returns Dictionaries. It can work with functions that return lists now (including depth n with n > 1).  Floats are a problem, because the string function won't accept it in VIM 7.2. \r\n\r\nThere is a example added in  RubyProxy.vim, to show to use this class.\r\n\r\nUSAGE\r\n\r\nYou need to prefix every vim function with the letter V (from VIM). E.g:\r\n\r\nwithProxy:\r\n\r\nwithProxy accepts a block and makes the proxy available in the scope of the block. \r\n\r\nEvery function from :help functions can be called. \r\nIf you want to use a certain function, the function name must be prefixed with V to avoid clashes with ruby's functions. \r\n\r\nEXAMPLE: \r\n\r\nruby withProxy { |p| puts p.Vconfirm(\"Test\",\"&Yes\\n&No\")}\r\n\r\nThis will show you a dialog box and return one if someone clicked Yes and 2 where someone clicked No.\r\n\r\nAnother example (with a function, which returns lists):\r\n\r\nwithProxy {|p| p.Vgetbufline(1,1,10).each {|x| puts (\"hello\" + x)}}\r\n\r\nThis appends hello to the first 10 lines from buffer 1 and echo the lines.\r\n\r\nTODO:\r\n\r\nAdding support for dictionaries. \r\nAdding support for floats. (It is built in, but the string function won't accept floats) \r\nAdding data conversions from Ruby to Vim. Now it only accepts list, strings or numbers. \r\n\r\nThis approach would probably be pretty easy to adopt for other languages, so create more plugin for different languages. \r\n\r\nSee the wiki for more information. Or for some information in Dutch, see here: http:\/\/www.i-bytes.nl\/code","4":"RubyProxy\r\nRubyProxy acts as a proxy between ruby and vim, so that most of vims functions are usable in ruby. Only the functions, which accepts lists and dictionary won't work. And functions, which returns Dictionaries. It can work with functions that return lists now (including depth n with n > 1).  Floats are a problem, because the string function won't accept it in VIM 7.2. \r\n\r\nThere is a example added in  RubyProxy.vim, to show to use this class.\r\n\r\nUSAGE\r\n\r\nYou need to prefix every vim function with the letter V (from VIM). E.g:\r\n\r\nwithProxy:\r\n\r\nwithProxy accepts a block and makes the proxy available in the scope of the block. \r\n\r\nEvery function from :help functions can be called. \r\nIf you want to use a certain function, the function name must be prefixed with V to avoid clashes with ruby's functions. \r\n\r\nEXAMPLE: \r\n\r\nruby withProxy { |p| puts p.Vconfirm(\"Test\",\"&Yes\\n&No\")}\r\n\r\nThis will show you a dialog box and return one if someone clicked Yes and 2 where someone clicked No.\r\n\r\nAnother example (with a function, which returns lists):\r\n\r\nwithProxy {|p| p.Vgetbufline(1,1,10).each {|x| puts (\"hello\" + x)}}\r\n\r\nThis appends hello to the first 10 lines from buffer 1 and echo the lines.\r\n\r\nTODO:\r\n\r\nAdding support for dictionaries. \r\nAdding support for floats. (It is built in, but the string function won't accept floats) \r\nAdding data conversions from Ruby to Vim. Now it only accepts list, strings or numbers. \r\n\r\nThis approach would probably be pretty easy to adopt for other languages, so create more plugin for different languages. \r\n\r\nSee the wiki for more information. Or for some information in Dutch, see here: http:\/\/www.i-bytes.nl\/code","install_details":"Just put it into your plugin directory. \r\nYou need if_ruby enabled, otherwise you cannot use the plugin. \r\nYour ruby installation needs yaml installed.","5":"Just put it into your plugin directory. \r\nYou need if_ruby enabled, otherwise you cannot use the plugin. \r\nYour ruby installation needs yaml installed.","first_name":"Edgar","6":"Edgar","last_name":"Klerks","7":"Klerks","releases":[{"0":"3251","vim_version":"7.0","1":"7.0","script_version":"0.21","2":"0.21","version_comment":"Added support for multilevel lists.\r\nCleaned up script (make use of script variables.).","3":"Added support for multilevel lists.\r\nCleaned up script (make use of script variables.).","package":"RubyProxy.vim","4":"RubyProxy.vim","src_id":"13911","5":"13911","creation_date":"1285360014","6":"1285360014"},{"0":"3251","vim_version":"7.0","1":"7.0","script_version":"0.2","2":"0.2","version_comment":"Added support for data conversion from Ruby to Vim, currently supports: List, String, Number. Dictionary and Floats coming soon. This version is not yet fully tested. But it seems to support multidepth lists. ","3":"Added support for data conversion from Ruby to Vim, currently supports: List, String, Number. Dictionary and Floats coming soon. This version is not yet fully tested. But it seems to support multidepth lists. ","package":"RubyProxy.vim","4":"RubyProxy.vim","src_id":"13904","5":"13904","creation_date":"1285323034","6":"1285323034"},{"0":"3251","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"RubyProxy.vim","4":"RubyProxy.vim","src_id":"13896","5":"13896","creation_date":"1285268699","6":"1285268699"}]},"3250":{"script_id":"3250","0":"3250","script_name":"swap","1":"swap","script_type":"utility","2":"utility","summary":"Easy swapping of text","3":"Easy swapping of text","description":"1. Visual mode\r\n\r\n    1.1 \\x\r\n\r\n    First select some text ([] represents the highlighted area). Then press \\x\r\n\r\n    [a ==   123] [  a == 123 ] [a==123]\r\n           |              |             |\r\n          V            V           V\r\n     123 ==   a     123 == a    123==a\r\n\r\n    Note: Your selection can be loose and include white spaces at both ends.\r\n\r\n    1.2 \\\\x\r\n\r\n    By default the plugin acts on comparison operators\r\n    You are however allowed to specify any pivot for the swapping.\r\n\r\n    First select some text. Then press \\\\x\r\n    You will be asked to give a pattern (% used here)\r\n\r\n    Just testing  %  a percentage as a pivot\r\n                             |\r\n                            V\r\n    a percentage as a pivot  %  Just testing\r\n\r\n    1.3\r\n\r\n    You can also use V, v or ^v to select several lines (v used), then press \\x\r\n\r\n    a == [123\r\n    user !~ unknown\r\n    0]!=#1\r\n         |\r\n        V\r\n    123 == a\r\n    unknown !~ user\r\n    1!=#0\r\n\r\n--------------------------------------------------\r\n2. Normal mode\r\n\r\n    Swap with WORD on the right \\x\r\n    ========================\r\n\r\n    # indicates the cursor position in the examples below.\r\n\r\n          #\r\n    zero one      a_longer_word three\r\n              |\r\n             V\r\n    zero a_longer_word      one three\r\n\r\n    Swap with WORD on the left  \\X\r\n    ========================\r\n\r\n    zero one two       three\r\n    let's have some more fun\r\n      #      |\r\n             V\r\n    zero one two       let's\r\n    three have some more fun\r\n\r\n2.1 Repeat\r\n\r\n    This plugin integrates with Tim Pope's repeat plugin. It means that you can\r\n    use . to repeat any normal mode (for now) swap mapping you just used!\r\n\r\n    For more information see: http:\/\/github.com\/tpope\/vim-repeat\r\n\r\n--------------------------------------------------\r\n3. Supported comparison operators\r\n\r\n    Comparison operators\r\n        ===    !==     <>    ==#    !=#     >#\r\n        >=#     <#    <=#    =~#    !~#    ==?\r\n        !=?     >?    >=?     <?    <=?    =~?\r\n        !~?     ==     !=     >=     =~     <=\r\n        !~      ~=\r\n\r\n    Logical operators\r\n         &&     ||\r\n\r\n    Assignment operators\r\n         +=     -=     *=     \/=     %=     &=\r\n         |=     ^=    <<=    >>=\r\n\r\n    Scope operators\r\n         ::\r\n\r\n    Pointer operators\r\n        ->*     ->     .*\r\n\r\n    Bitwise operators\r\n         <<     >>\r\n\r\n    Misc operators\r\n         >      <       =      +      -      *\r\n         \/      %       &      |      ^      .\r\n         ?      :       ,     '=     '<     '>\r\n         !<     !>\r\n\r\n3.1 Custom operators\r\n\r\n    You can define your own operators by putting a similar line in your vimrc:\r\n\r\n    let g:swap_custom_ops = ['first_operator', 'second_operator', ...]\r\n\r\n4. Custom mappings\r\n\r\nYou have the possibility to define your own custom mappings in your .vimrc:\r\n\r\n    vmap <leader>x         <plug>SwapSwapOperands\r\n    vmap <leader><leader>x <plug>SwapSwapOperandsPivot\r\n    nmap <leader>x         <plug>SwapSwapWithR_WORD\r\n    nmap <leader>X         <plug>SwapSwapWithL_WORD\r\n\r\nNote: You can replace \\x, \\\\x, \\X with whatever you like.","4":"1. Visual mode\r\n\r\n    1.1 \\x\r\n\r\n    First select some text ([] represents the highlighted area). Then press \\x\r\n\r\n    [a ==   123] [  a == 123 ] [a==123]\r\n           |              |             |\r\n          V            V           V\r\n     123 ==   a     123 == a    123==a\r\n\r\n    Note: Your selection can be loose and include white spaces at both ends.\r\n\r\n    1.2 \\\\x\r\n\r\n    By default the plugin acts on comparison operators\r\n    You are however allowed to specify any pivot for the swapping.\r\n\r\n    First select some text. Then press \\\\x\r\n    You will be asked to give a pattern (% used here)\r\n\r\n    Just testing  %  a percentage as a pivot\r\n                             |\r\n                            V\r\n    a percentage as a pivot  %  Just testing\r\n\r\n    1.3\r\n\r\n    You can also use V, v or ^v to select several lines (v used), then press \\x\r\n\r\n    a == [123\r\n    user !~ unknown\r\n    0]!=#1\r\n         |\r\n        V\r\n    123 == a\r\n    unknown !~ user\r\n    1!=#0\r\n\r\n--------------------------------------------------\r\n2. Normal mode\r\n\r\n    Swap with WORD on the right \\x\r\n    ========================\r\n\r\n    # indicates the cursor position in the examples below.\r\n\r\n          #\r\n    zero one      a_longer_word three\r\n              |\r\n             V\r\n    zero a_longer_word      one three\r\n\r\n    Swap with WORD on the left  \\X\r\n    ========================\r\n\r\n    zero one two       three\r\n    let's have some more fun\r\n      #      |\r\n             V\r\n    zero one two       let's\r\n    three have some more fun\r\n\r\n2.1 Repeat\r\n\r\n    This plugin integrates with Tim Pope's repeat plugin. It means that you can\r\n    use . to repeat any normal mode (for now) swap mapping you just used!\r\n\r\n    For more information see: http:\/\/github.com\/tpope\/vim-repeat\r\n\r\n--------------------------------------------------\r\n3. Supported comparison operators\r\n\r\n    Comparison operators\r\n        ===    !==     <>    ==#    !=#     >#\r\n        >=#     <#    <=#    =~#    !~#    ==?\r\n        !=?     >?    >=?     <?    <=?    =~?\r\n        !~?     ==     !=     >=     =~     <=\r\n        !~      ~=\r\n\r\n    Logical operators\r\n         &&     ||\r\n\r\n    Assignment operators\r\n         +=     -=     *=     \/=     %=     &=\r\n         |=     ^=    <<=    >>=\r\n\r\n    Scope operators\r\n         ::\r\n\r\n    Pointer operators\r\n        ->*     ->     .*\r\n\r\n    Bitwise operators\r\n         <<     >>\r\n\r\n    Misc operators\r\n         >      <       =      +      -      *\r\n         \/      %       &      |      ^      .\r\n         ?      :       ,     '=     '<     '>\r\n         !<     !>\r\n\r\n3.1 Custom operators\r\n\r\n    You can define your own operators by putting a similar line in your vimrc:\r\n\r\n    let g:swap_custom_ops = ['first_operator', 'second_operator', ...]\r\n\r\n4. Custom mappings\r\n\r\nYou have the possibility to define your own custom mappings in your .vimrc:\r\n\r\n    vmap <leader>x         <plug>SwapSwapOperands\r\n    vmap <leader><leader>x <plug>SwapSwapOperandsPivot\r\n    nmap <leader>x         <plug>SwapSwapWithR_WORD\r\n    nmap <leader>X         <plug>SwapSwapWithL_WORD\r\n\r\nNote: You can replace \\x, \\\\x, \\X with whatever you like.","install_details":"swap.vim -> ~\/.vim\/plugin\r\nswap.txt   -> ~\/.vim\/doc\r\n\r\nLatest version at:\r\nhttps:\/\/github.com\/kurkale6ka\/vim-swap","5":"swap.vim -> ~\/.vim\/plugin\r\nswap.txt   -> ~\/.vim\/doc\r\n\r\nLatest version at:\r\nhttps:\/\/github.com\/kurkale6ka\/vim-swap","first_name":"Dimitar","6":"Dimitar","last_name":"Dimitrov","7":"Dimitrov","releases":[{"0":"3250","vim_version":"7.0","1":"7.0","script_version":"3.3","2":"3.3","version_comment":"Made the plugin mappings more flexible: you could redefine them in your .vimrc\r\nbut you don't have to","3":"Made the plugin mappings more flexible: you could redefine them in your .vimrc\r\nbut you don't have to","package":"swap.zip","4":"swap.zip","src_id":"14009","5":"14009","creation_date":"1286364692","6":"1286364692"},{"0":"3250","vim_version":"7.0","1":"7.0","script_version":"3.2","2":"3.2","version_comment":"Changed <plug>SwapSwapOperandsPivot to <plug>SwapSwapPivotOperands\r\nbecause this map name caused <plug>SwapSwapOperands to wait and be very slow!","3":"Changed <plug>SwapSwapOperandsPivot to <plug>SwapSwapPivotOperands\r\nbecause this map name caused <plug>SwapSwapOperands to wait and be very slow!","package":"swap.zip","4":"swap.zip","src_id":"14005","5":"14005","creation_date":"1286359528","6":"1286359528"},{"0":"3250","vim_version":"7.0","1":"7.0","script_version":"3.1","2":"3.1","version_comment":"- Fixed a bug when selection goes beyond $ (using ve=all for instance)\r\n- Made in sort that \/ history is kept clean (unchanged) after using swap.vim","3":"- Fixed a bug when selection goes beyond $ (using ve=all for instance)\r\n- Made in sort that \/ history is kept clean (unchanged) after using swap.vim","package":"swap.zip","4":"swap.zip","src_id":"13999","5":"13999","creation_date":"1286323469","6":"1286323469"},{"0":"3250","vim_version":"7.0","1":"7.0","script_version":"3.0","2":"3.0","version_comment":"- Added support for more operators (+ custom ones)\r\n- Added partial support for the repeat.vim plugin\r\n- Allowed all mappings to be customized\r\n- Simplified the code","3":"- Added support for more operators (+ custom ones)\r\n- Added partial support for the repeat.vim plugin\r\n- Allowed all mappings to be customized\r\n- Simplified the code","package":"swap.zip","4":"swap.zip","src_id":"13997","5":"13997","creation_date":"1286308164","6":"1286308164"},{"0":"3250","vim_version":"7.0","1":"7.0","script_version":"2.1","2":"2.1","version_comment":"Changed \\<left>x to \\X + fixed a bug when trying to swap at BOF or EOF","3":"Changed \\<left>x to \\X + fixed a bug when trying to swap at BOF or EOF","package":"swap.zip","4":"swap.zip","src_id":"13914","5":"13914","creation_date":"1285401414","6":"1285401414"},{"0":"3250","vim_version":"7.0","1":"7.0","script_version":"2.0","2":"2.0","version_comment":"Swapping of words works a treat now.\r\nSwapping is stricter now, it is only about swapping:\r\n\r\nEx: a== b was transformed to b == a. In the new version it becomes:\r\n      b== a\r\n\r\nChanged the mappings too: \\x, \\\\x and \\<left>x are used now.\r\n                                         think of them as of ^w x in Vim.","3":"Swapping of words works a treat now.\r\nSwapping is stricter now, it is only about swapping:\r\n\r\nEx: a== b was transformed to b == a. In the new version it becomes:\r\n      b== a\r\n\r\nChanged the mappings too: \\x, \\\\x and \\<left>x are used now.\r\n                                         think of them as of ^w x in Vim.","package":"swap.zip","4":"swap.zip","src_id":"13912","5":"13912","creation_date":"1285365725","6":"1285365725"},{"0":"3250","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"swap.zip","4":"swap.zip","src_id":"13894","5":"13894","creation_date":"1285260571","6":"1285260571"}]},"3249":{"script_id":"3249","0":"3249","script_name":"Jasmine snippets (for snipMate)","1":"Jasmine snippets (for snipMate)","script_type":"utility","2":"utility","summary":"A set of snippets for the Jasmine JavaScript BDD Framework","3":"A set of snippets for the Jasmine JavaScript BDD Framework","description":"Jasmine (http:\/\/pivotal.github.com\/jasmine\/) is a behavior-driven-development framework for JavaScript with some very nice features. This set of snipMate snippets aims to make developing tests with Jasmine quicker and easier.\r\n\r\nFor example, rather than typing out the full:\r\n\r\n\"description('Description Here', function() {});\"\r\n\r\nYou can type \"des<TAB>\". This will create the full description block, with convenient tab stops. Tre magnifique!\r\n\r\nList of Included Snippets (this is actually just the file):\r\n\r\n# After Each\r\nsnippet aft\r\n\tafterEach(function() { \r\n\t\t${1} \r\n\t}\r\n\r\n# Any\r\nsnippet any\r\n\tjasmine.any(${1})\r\n\r\n#\tBefore Each\r\nsnippet bef\r\n\tbeforeEach(function() {\r\n\t\t${1}\r\n\t});\r\n\r\n# Describe\r\nsnippet des\r\n\tdescribe(\"${1:description}\", function() {\r\n\t\t${2}\r\n\t});${3}\t\r\n\r\n# Expect not to be defined\r\nsnippet notd\r\n\texpect(${1:target}).not.toBeDefined();${2}\r\n\r\n# Expect not to be falsy\r\nsnippet notf\r\n\texpect(${1:target}).not.toBeFalsy();${2}\r\n\r\n# Expect not to be null\r\nsnippet notn\r\n\texpect(${1:target}).not.toBeNull();${2}\r\n\r\n# Expect to be truthy\r\nsnippet nott\r\n\texpect(${1:target}).not.toBeTruthy();${2}\r\n\r\n# Expect not to contain\r\nsnippet notc\r\n\texpect(${1:target}).not.toContain(${2:value});${3}\r\n\r\n# Expect not to equal\r\nsnippet note\r\n\texpect(${1:target}).not.toEqual(${2:value});${3}\r\n\r\n# Expect not to match\r\nsnippet notm\r\n\texpect(${1:target}).not.toBeDefined();${2}\r\n\r\n# Expect not\r\nsnippet notx\r\n\texpect(${1:target}).not;${2}\r\n\r\n# Expect to be defined\r\nsnippet ed\r\n\texpect(${1:target}).toBeDefined();${2}\r\n\r\n# Expect to be falsy\r\nsnippet ef\r\n\texpect(${1:target}).toBeFalsy();${2}\r\n\r\n# Expect to be null\r\nsnippet en\r\n\texpect(${1:target}).toBeNull();${2}\r\n\r\n# Expect to be truthy\r\nsnippet et\r\n\texpect(${1:target}).toBeTruthy();${2}\r\n\r\n# Expect to contain\r\nsnippet ec\r\n\texpect(${1:target}).toContain(${2:value});${3}\r\n\r\n# Expect to equal\r\nsnippet ee\r\n\texpect(${1:target}).toEqual(${2:value});${3}\r\n\r\n# Expect to match\r\nsnippet em\r\n\texpect(${1:target}).toMatch(${2:pattern});${3}\r\n\r\n# Expect was called with\r\nsnippet escw\r\n\texpect(${1:target}).wasCalledWith(${2:arguments});${3}\r\n\r\n# Expect was called\r\nsnippet esc\r\n\texpect(${1:target}).wasCalled();${2}\r\n\r\n# Expect was not called with\r\nsnippet notscw\r\n\texpect(${1:target}).wasNotCalledWith(${2:arguments});${3}\r\n\r\n# Expect was not called\r\nsnippet notsc\r\n\texpect(${1:target}).wasNotCalled();${3}\r\n\r\n# Expect\r\nsnippet ex\r\n\texpect(${1:target});${2}\r\n\r\n# It\r\nsnippet it\r\n\tit(\"${1:description}\", function() {\r\n\t\t${2}\r\n\t});${3}\r\n\r\n# Runs\r\nsnippet ru\r\n\truns(function() {\r\n\t\t${1}\r\n\t});${2}\r\n\r\n# Spy on and call fake\r\nsnippet scf\r\n\tspyOn(${1:object}, \"${2:method}\").andCallFake(${3:function});${4}\r\n\r\n# Spy on and call through\r\nsnippet sct\r\n\tspyOn(${1:object}, \"${2:method}\").andCallThrough();${3}\r\n\r\n# Spy on and return\r\nsnippet sr\r\n\tspyOn(${1:object}, \"${2:method}\").andReturn(${3:arguments});${4}\r\n\r\n# Spy on and throw\r\nsnippet st\r\n\tspyOn(${1:object}, \"${2:method}\").andThrow(${3:exception});${4}\r\n\r\n# Spy on\r\nsnippet s\r\n\tspyOn(${1:object}, \"${2:method}\");${3}\r\n\r\n# Waits (wa)\r\nsnippet wa\r\n\twaits(${1});${2}","4":"Jasmine (http:\/\/pivotal.github.com\/jasmine\/) is a behavior-driven-development framework for JavaScript with some very nice features. This set of snipMate snippets aims to make developing tests with Jasmine quicker and easier.\r\n\r\nFor example, rather than typing out the full:\r\n\r\n\"description('Description Here', function() {});\"\r\n\r\nYou can type \"des<TAB>\". This will create the full description block, with convenient tab stops. Tre magnifique!\r\n\r\nList of Included Snippets (this is actually just the file):\r\n\r\n# After Each\r\nsnippet aft\r\n\tafterEach(function() { \r\n\t\t${1} \r\n\t}\r\n\r\n# Any\r\nsnippet any\r\n\tjasmine.any(${1})\r\n\r\n#\tBefore Each\r\nsnippet bef\r\n\tbeforeEach(function() {\r\n\t\t${1}\r\n\t});\r\n\r\n# Describe\r\nsnippet des\r\n\tdescribe(\"${1:description}\", function() {\r\n\t\t${2}\r\n\t});${3}\t\r\n\r\n# Expect not to be defined\r\nsnippet notd\r\n\texpect(${1:target}).not.toBeDefined();${2}\r\n\r\n# Expect not to be falsy\r\nsnippet notf\r\n\texpect(${1:target}).not.toBeFalsy();${2}\r\n\r\n# Expect not to be null\r\nsnippet notn\r\n\texpect(${1:target}).not.toBeNull();${2}\r\n\r\n# Expect to be truthy\r\nsnippet nott\r\n\texpect(${1:target}).not.toBeTruthy();${2}\r\n\r\n# Expect not to contain\r\nsnippet notc\r\n\texpect(${1:target}).not.toContain(${2:value});${3}\r\n\r\n# Expect not to equal\r\nsnippet note\r\n\texpect(${1:target}).not.toEqual(${2:value});${3}\r\n\r\n# Expect not to match\r\nsnippet notm\r\n\texpect(${1:target}).not.toBeDefined();${2}\r\n\r\n# Expect not\r\nsnippet notx\r\n\texpect(${1:target}).not;${2}\r\n\r\n# Expect to be defined\r\nsnippet ed\r\n\texpect(${1:target}).toBeDefined();${2}\r\n\r\n# Expect to be falsy\r\nsnippet ef\r\n\texpect(${1:target}).toBeFalsy();${2}\r\n\r\n# Expect to be null\r\nsnippet en\r\n\texpect(${1:target}).toBeNull();${2}\r\n\r\n# Expect to be truthy\r\nsnippet et\r\n\texpect(${1:target}).toBeTruthy();${2}\r\n\r\n# Expect to contain\r\nsnippet ec\r\n\texpect(${1:target}).toContain(${2:value});${3}\r\n\r\n# Expect to equal\r\nsnippet ee\r\n\texpect(${1:target}).toEqual(${2:value});${3}\r\n\r\n# Expect to match\r\nsnippet em\r\n\texpect(${1:target}).toMatch(${2:pattern});${3}\r\n\r\n# Expect was called with\r\nsnippet escw\r\n\texpect(${1:target}).wasCalledWith(${2:arguments});${3}\r\n\r\n# Expect was called\r\nsnippet esc\r\n\texpect(${1:target}).wasCalled();${2}\r\n\r\n# Expect was not called with\r\nsnippet notscw\r\n\texpect(${1:target}).wasNotCalledWith(${2:arguments});${3}\r\n\r\n# Expect was not called\r\nsnippet notsc\r\n\texpect(${1:target}).wasNotCalled();${3}\r\n\r\n# Expect\r\nsnippet ex\r\n\texpect(${1:target});${2}\r\n\r\n# It\r\nsnippet it\r\n\tit(\"${1:description}\", function() {\r\n\t\t${2}\r\n\t});${3}\r\n\r\n# Runs\r\nsnippet ru\r\n\truns(function() {\r\n\t\t${1}\r\n\t});${2}\r\n\r\n# Spy on and call fake\r\nsnippet scf\r\n\tspyOn(${1:object}, \"${2:method}\").andCallFake(${3:function});${4}\r\n\r\n# Spy on and call through\r\nsnippet sct\r\n\tspyOn(${1:object}, \"${2:method}\").andCallThrough();${3}\r\n\r\n# Spy on and return\r\nsnippet sr\r\n\tspyOn(${1:object}, \"${2:method}\").andReturn(${3:arguments});${4}\r\n\r\n# Spy on and throw\r\nsnippet st\r\n\tspyOn(${1:object}, \"${2:method}\").andThrow(${3:exception});${4}\r\n\r\n# Spy on\r\nsnippet s\r\n\tspyOn(${1:object}, \"${2:method}\");${3}\r\n\r\n# Waits (wa)\r\nsnippet wa\r\n\twaits(${1});${2}","install_details":"First, install snipMate if you do not have it installed (http:\/\/www.vim.org\/scripts\/script.php?script_id=2540)\r\n\r\nThen, copy javascript-jasmine.snippets to $VIMRUNTIME\/snippets\/.\r\n\r\nLaunch a new instance of Vim, and play with the magic!","5":"First, install snipMate if you do not have it installed (http:\/\/www.vim.org\/scripts\/script.php?script_id=2540)\r\n\r\nThen, copy javascript-jasmine.snippets to $VIMRUNTIME\/snippets\/.\r\n\r\nLaunch a new instance of Vim, and play with the magic!","first_name":"Brian","6":"Brian","last_name":"Egan","7":"Egan","releases":[{"0":"3249","vim_version":"7.0","1":"7.0","script_version":"0.1.0","2":"0.1.0","version_comment":"Initial upload","3":"Initial upload","package":"javascript-jasmine.snippets","4":"javascript-jasmine.snippets","src_id":"13887","5":"13887","creation_date":"1285198842","6":"1285198842"}]},"3248":{"script_id":"3248","0":"3248","script_name":"Zephyr Color Scheme","1":"Zephyr Color Scheme","script_type":"color scheme","2":"color scheme","summary":"Dark color scheme with distinct but calm colors","3":"Dark color scheme with distinct but calm colors","description":"This is a color scheme based on gardener and modified to have more distinct colors which aren\\'t too bright.\r\n\r\nScreenshot (PHP) [v1.0.1]: http:\/\/i.imgur.com\/6l9Nm.png","4":"This is a color scheme based on gardener and modified to have more distinct colors which aren\\'t too bright.\r\n\r\nScreenshot (PHP) [v1.0.1]: http:\/\/i.imgur.com\/6l9Nm.png","install_details":"","5":"","first_name":"Matt","6":"Matt","last_name":"Creenan","7":"Creenan","releases":[{"0":"3248","vim_version":"7.0","1":"7.0","script_version":"1.01","2":"1.01","version_comment":"Updated a few colors, added some PHP defaults","3":"Updated a few colors, added some PHP defaults","package":"zephyr.vim","4":"zephyr.vim","src_id":"14084","5":"14084","creation_date":"1287600979","6":"1287600979"},{"0":"3248","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"zephyr.vim","4":"zephyr.vim","src_id":"13885","5":"13885","creation_date":"1285170479","6":"1285170479"}]},"3247":{"script_id":"3247","0":"3247","script_name":"Shades of Amber","1":"Shades of Amber","script_type":"color scheme","2":"color scheme","summary":"Amber monitor influenced, nostalgic colour scheme","3":"Amber monitor influenced, nostalgic colour scheme","description":"At college (way back when), whenever I was given the choice, I would choose the amber terminal over the green one every time.\r\nIt's easy on the eye, and somehow \u00e2\u0080\u009ccooler\u00e2\u0080\u009d.\r\n\r\nAnyway, here's my stab at reproducing the experience (with a broader palette of oranges).\r\nAnd it's in constant daily use. Hope you like it.\r\n\r\n[comments welcome]","4":"At college (way back when), whenever I was given the choice, I would choose the amber terminal over the green one every time.\r\nIt's easy on the eye, and somehow \u00e2\u0080\u009ccooler\u00e2\u0080\u009d.\r\n\r\nAnyway, here's my stab at reproducing the experience (with a broader palette of oranges).\r\nAnd it's in constant daily use. Hope you like it.\r\n\r\n[comments welcome]","install_details":"Put this in your colorscheme directory. e.g.\r\ncp shadesofamber.vim ~\/.vim\/colors","5":"Put this in your colorscheme directory. e.g.\r\ncp shadesofamber.vim ~\/.vim\/colors","first_name":"Tim","6":"Tim","last_name":"Brown","7":"Brown","releases":[{"0":"3247","vim_version":"7.0","1":"7.0","script_version":"1.1","2":"1.1","version_comment":"Three-digit #abc colours are now six-digit #aabbccl","3":"Three-digit #abc colours are now six-digit #aabbccl","package":"shadesofamber.vim","4":"shadesofamber.vim","src_id":"13932","5":"13932","creation_date":"1285581927","6":"1285581927"},{"0":"3247","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"shadesofamber.vim","4":"shadesofamber.vim","src_id":"13884","5":"13884","creation_date":"1285148912","6":"1285148912"}]},"3246":{"script_id":"3246","0":"3246","script_name":"CaptureClipboard","1":"CaptureClipboard","script_type":"utility","2":"utility","summary":"Append system clipboard changes to current buffer. ","3":"Append system clipboard changes to current buffer. ","description":"DESCRIPTION\r\nQuotes or text fragments can be collected from various sources outside Vim\r\ninto a single text document through the clipboard. This plugin makes\r\nconsecutive copy-and-pastes into Vim much more comfortable by monitoring the\r\nsystem clipboard for changes and appending them into the current Vim buffer\r\nautomatically. Feedback about the number of captures is given in Vim's window\r\ntitle, so one does not have to switch back and forth between applications any\r\nmore, and can completely focus on text collection via CTRL-C, CTRL-C, ...\r\n\r\nUSAGE\r\n:[count]CaptureClipboard[!] {delimiter}\r\n:[count]CaptureClipboard[!] {prefix}^M{suffix}\r\n:[count]CaptureClipboard[!] {prefix}^M{delimiter}^M{suffix}\r\n:[count]CaptureClipboard[!] {first-prefix}^M{prefix}^M{delimiter}^M{suffix}\r\n:[count]CaptureClipboardReverse[!] {...}\r\n                        Monitors the clipboard for changes and inserts any\r\n                        change of clipboard contents into the current buffer\r\n                        (in new lines, or, if given, delimited by {delimiter},\r\n                        and with {prefix} before and {suffix} after).\r\n                        To stop, press <CTRL-C> or copy a literal dot (\".\") to\r\n                        the clipboard. If [count] is given, the capture stops\r\n                        after [count] captures.\r\n\r\n                        If [!] is given, whitespace (including new lines) is\r\n                        trimmed from the beginning and end of each capture.\r\n\r\n                        With :CaptureClipboardReverse, changes are prepended,\r\n                        reverting the insertion order. Normally, changes are\r\n                        appended to the current or given [line].\r\n                        Use :$|CaptureClipboard to append to the end of the\r\n                        current buffer.\r\n\r\n                        {delimiter} is evaluated as an expression if it is\r\n                        (single- or double-) quoted, or contains backslashes.\r\n                        The default {delimiter} is \"\\n\"; each capture is\r\n                        placed on a new line. Use '' to place everything next\r\n                        to each other, ' ' to put a space character in\r\n                        between, \"\\n--\\n\" to insert a -- separator line\r\n                        between captures. When {delimiter} contains a newline\r\n                        character, the first capture will already start on a\r\n                        new line.\r\n                        Backslash-escaped characters (like \\n) are also\r\n                        supported in {prefix} and {suffix}.\r\n:CaptureSelection [...] Variant (on Linux) that uses the selection\r\n                        (quotestar) instead of the system clipboard.\r\n\r\nCTRL-R ?                Wait for one capture from the clipboard and insert it\r\n                        at the current cursor position.","4":"DESCRIPTION\r\nQuotes or text fragments can be collected from various sources outside Vim\r\ninto a single text document through the clipboard. This plugin makes\r\nconsecutive copy-and-pastes into Vim much more comfortable by monitoring the\r\nsystem clipboard for changes and appending them into the current Vim buffer\r\nautomatically. Feedback about the number of captures is given in Vim's window\r\ntitle, so one does not have to switch back and forth between applications any\r\nmore, and can completely focus on text collection via CTRL-C, CTRL-C, ...\r\n\r\nUSAGE\r\n:[count]CaptureClipboard[!] {delimiter}\r\n:[count]CaptureClipboard[!] {prefix}^M{suffix}\r\n:[count]CaptureClipboard[!] {prefix}^M{delimiter}^M{suffix}\r\n:[count]CaptureClipboard[!] {first-prefix}^M{prefix}^M{delimiter}^M{suffix}\r\n:[count]CaptureClipboardReverse[!] {...}\r\n                        Monitors the clipboard for changes and inserts any\r\n                        change of clipboard contents into the current buffer\r\n                        (in new lines, or, if given, delimited by {delimiter},\r\n                        and with {prefix} before and {suffix} after).\r\n                        To stop, press <CTRL-C> or copy a literal dot (\".\") to\r\n                        the clipboard. If [count] is given, the capture stops\r\n                        after [count] captures.\r\n\r\n                        If [!] is given, whitespace (including new lines) is\r\n                        trimmed from the beginning and end of each capture.\r\n\r\n                        With :CaptureClipboardReverse, changes are prepended,\r\n                        reverting the insertion order. Normally, changes are\r\n                        appended to the current or given [line].\r\n                        Use :$|CaptureClipboard to append to the end of the\r\n                        current buffer.\r\n\r\n                        {delimiter} is evaluated as an expression if it is\r\n                        (single- or double-) quoted, or contains backslashes.\r\n                        The default {delimiter} is \"\\n\"; each capture is\r\n                        placed on a new line. Use '' to place everything next\r\n                        to each other, ' ' to put a space character in\r\n                        between, \"\\n--\\n\" to insert a -- separator line\r\n                        between captures. When {delimiter} contains a newline\r\n                        character, the first capture will already start on a\r\n                        new line.\r\n                        Backslash-escaped characters (like \\n) are also\r\n                        supported in {prefix} and {suffix}.\r\n:CaptureSelection [...] Variant (on Linux) that uses the selection\r\n                        (quotestar) instead of the system clipboard.\r\n\r\nCTRL-R ?                Wait for one capture from the clipboard and insert it\r\n                        at the current cursor position.","install_details":"INSTALLATION\r\nThe code is hosted in a Git repo at\r\n    https:\/\/github.com\/inkarkat\/vim-CaptureClipboard\r\nYou can use your favorite plugin manager, or \"git clone\" into a directory used\r\nfor Vim packages. Releases are on the \"stable\" branch, the latest unstable\r\ndevelopment snapshot on \"master\".\r\n\r\nThis script is also packaged as a vimball. If you have the \"gunzip\"\r\ndecompressor in your PATH, simply edit the *.vmb.gz package in Vim; otherwise,\r\ndecompress the archive first, e.g. using WinZip. Inside Vim, install by\r\nsourcing the vimball or via the :UseVimball command.\r\n    vim CaptureClipboard*.vmb.gz\r\n    :so %\r\nTo uninstall, use the :RmVimball command.\r\n\r\nDEPENDENCIES\r\n- Requires Vim 7.0 or higher.\r\n- Requires the ingo-library.vim plugin (vimscript #4433), version 1.024 or\r\n  higher.\r\n\r\nCONFIGURATION\r\nFor a permanent configuration, put the following commands into your vimrc:\r\n\r\nBy default, each capture will be placed on a new line in the capture buffer;\r\ni.e. the delimiter between captures is a newline character:\r\n    let g:CaptureClipboard_DefaultDelimiter = \"\\n\"\r\n\r\nThe marker text that will stop capturing can be changed via:\r\n    let g:CaptureClipboard_EndOfCaptureMarker = '.'\r\n\r\nIf you capture a lot of text or the captured information is very valuable, you\r\ncan automatically persist the capture buffer after each capture. Enable via:\r\n    let g:CaptureClipboard_IsAutoSave = 1\r\n\r\nIn X, changes to the current selection (quotestar) are captured. If you want\r\nto only capture changes to the X clipboard (quoteplus), not every change in\r\nselection, use:\r\n    let g:CaptureClipboard_Register = '+'\r\n\r\nIf you want to use a different mapping, map your keys to the\r\n<Plug>(CaptureClipboardInsertOne) mapping target _before_ sourcing the script\r\n(e.g. in your vimrc):\r\n    imap <C-R>? <Plug>(CaptureClipboardInsertOne)","5":"INSTALLATION\r\nThe code is hosted in a Git repo at\r\n    https:\/\/github.com\/inkarkat\/vim-CaptureClipboard\r\nYou can use your favorite plugin manager, or \"git clone\" into a directory used\r\nfor Vim packages. Releases are on the \"stable\" branch, the latest unstable\r\ndevelopment snapshot on \"master\".\r\n\r\nThis script is also packaged as a vimball. If you have the \"gunzip\"\r\ndecompressor in your PATH, simply edit the *.vmb.gz package in Vim; otherwise,\r\ndecompress the archive first, e.g. using WinZip. Inside Vim, install by\r\nsourcing the vimball or via the :UseVimball command.\r\n    vim CaptureClipboard*.vmb.gz\r\n    :so %\r\nTo uninstall, use the :RmVimball command.\r\n\r\nDEPENDENCIES\r\n- Requires Vim 7.0 or higher.\r\n- Requires the ingo-library.vim plugin (vimscript #4433), version 1.024 or\r\n  higher.\r\n\r\nCONFIGURATION\r\nFor a permanent configuration, put the following commands into your vimrc:\r\n\r\nBy default, each capture will be placed on a new line in the capture buffer;\r\ni.e. the delimiter between captures is a newline character:\r\n    let g:CaptureClipboard_DefaultDelimiter = \"\\n\"\r\n\r\nThe marker text that will stop capturing can be changed via:\r\n    let g:CaptureClipboard_EndOfCaptureMarker = '.'\r\n\r\nIf you capture a lot of text or the captured information is very valuable, you\r\ncan automatically persist the capture buffer after each capture. Enable via:\r\n    let g:CaptureClipboard_IsAutoSave = 1\r\n\r\nIn X, changes to the current selection (quotestar) are captured. If you want\r\nto only capture changes to the X clipboard (quoteplus), not every change in\r\nselection, use:\r\n    let g:CaptureClipboard_Register = '+'\r\n\r\nIf you want to use a different mapping, map your keys to the\r\n<Plug>(CaptureClipboardInsertOne) mapping target _before_ sourcing the script\r\n(e.g. in your vimrc):\r\n    imap <C-R>? <Plug>(CaptureClipboardInsertOne)","first_name":"Ingo","6":"Ingo","last_name":"Karkat","7":"Karkat","releases":[{"0":"3246","vim_version":"7.0","1":"7.0","script_version":"1.21","2":"1.21","version_comment":"- Default to \"+ on Linux; add :CaptureSelection variant for \"* there.","3":"- Default to \"+ on Linux; add :CaptureSelection variant for \"* there.","package":"CaptureClipboard-1.21.vmb.gz","4":"CaptureClipboard-1.21.vmb.gz","src_id":"26493","5":"26493","creation_date":"1558326031","6":"1558326031"},{"0":"3246","vim_version":"7.0","1":"7.0","script_version":"1.20","2":"1.20","version_comment":"- Use ingo#lines#PutWrapper() to avoid clobbering the expression register.\r\n- ENH: Support {prefix}^M{suffix} and {first-prefix}^M{prefix}^M{delimiter}^M{suffix} alternatives to the simplistic {delimiter}. *** You need to separately install ingo-library (vimscript #4433) version 1.024 (or higher)! ***","3":"- Use ingo#lines#PutWrapper() to avoid clobbering the expression register.\r\n- ENH: Support {prefix}^M{suffix} and {first-prefix}^M{prefix}^M{delimiter}^M{suffix} alternatives to the simplistic {delimiter}. *** You need to separately install ingo-library (vimscript #4433) version 1.024 (or higher)! ***","package":"CaptureClipboard-1.20.vmb.gz","4":"CaptureClipboard-1.20.vmb.gz","src_id":"23213","5":"23213","creation_date":"1429788890","6":"1429788890"},{"0":"3246","vim_version":"7.0","1":"7.0","script_version":"1.11","2":"1.11","version_comment":"Implement check for no-modifiable buffer via noop-modification instead of checking for 'modifiable'; this also handles the read-only warning.","3":"Implement check for no-modifiable buffer via noop-modification instead of checking for 'modifiable'; this also handles the read-only warning.","package":"CaptureClipboard-1.11.vmb.gz","4":"CaptureClipboard-1.11.vmb.gz","src_id":"19256","5":"19256","creation_date":"1356841271","6":"1356841271"},{"0":"3246","vim_version":"7.0","1":"7.0","script_version":"1.10","2":"1.10","version_comment":"Add mapping to wait for and insert one capture.","3":"Add mapping to wait for and insert one capture.","package":"CaptureClipboard-1.10.vmb.gz","4":"CaptureClipboard-1.10.vmb.gz","src_id":"18923","5":"18923","creation_date":"1351522738","6":"1351522738"},{"0":"3246","vim_version":"7.0","1":"7.0","script_version":"1.00","2":"1.00","version_comment":"Initial upload","3":"Initial upload","package":"CaptureClipboard.vba.gz","4":"CaptureClipboard.vba.gz","src_id":"13873","5":"13873","creation_date":"1284988277","6":"1284988277"}]},"3245":{"script_id":"3245","0":"3245","script_name":"Heliotrope","1":"Heliotrope","script_type":"color scheme","2":"color scheme","summary":"A dark-on-light color scheme ","3":"A dark-on-light color scheme ","description":"A green-orange color scheme. \r\n\r\nHeliotrope (a.k.a. bloodstone) is a mineral that is a dark chalcedony green with orange-red streaks. \r\n\r\nAs I do most of my coding in Haskell, the colors for syntax elements has been chosen with their prevalence in mind: functions in orange, green for types and then different shades of each for the rest.\r\n\r\nScreenshots: \r\n    http:\/\/luola.net\/~ane\/misc\/helio1.png - Haskell and Java\r\n    http:\/\/luola.net\/~ane\/misc\/helio2.png - Haskell (again!) and Ruby","4":"A green-orange color scheme. \r\n\r\nHeliotrope (a.k.a. bloodstone) is a mineral that is a dark chalcedony green with orange-red streaks. \r\n\r\nAs I do most of my coding in Haskell, the colors for syntax elements has been chosen with their prevalence in mind: functions in orange, green for types and then different shades of each for the rest.\r\n\r\nScreenshots: \r\n    http:\/\/luola.net\/~ane\/misc\/helio1.png - Haskell and Java\r\n    http:\/\/luola.net\/~ane\/misc\/helio2.png - Haskell (again!) and Ruby","install_details":"Save to your $VIMFILES\/colors directory and type :colors heliotrope or open in vim and type :so %","5":"Save to your $VIMFILES\/colors directory and type :colors heliotrope or open in vim and type :so %","first_name":"Antoine","6":"Antoine","last_name":"Kalmbach","7":"Kalmbach","releases":[{"0":"3245","vim_version":"7.0","1":"7.0","script_version":"0.0.1","2":"0.0.1","version_comment":"Initial upload","3":"Initial upload","package":"heliotrope.vim","4":"heliotrope.vim","src_id":"13869","5":"13869","creation_date":"1284908290","6":"1284908290"}]},"3244":{"script_id":"3244","0":"3244","script_name":"Timer routine","1":"Timer routine","script_type":"utility","2":"utility","summary":"Does a 'timer' for vimscript like there is on other languages","3":"Does a 'timer' for vimscript like there is on other languages","description":"Most programming environments give you some sort of a timer callback facility you can attach to one of your functions to do a thing periodically.  This is missing in VIM.  This script 'emulates' one by doing a quick series of un-obstrusive kepresses that cause the key pressed timeout to reset continually.  Normally this happens every for seconds.  This can be changed.  The updatetimer is used to achive this.  A value of 1000 will cause the 'timer' to be called every one second.  When you want to hook something up to this timer, simply create an autocommand for on update wait or something, I forget what it is called.  It looks something similar to: au * onUpdateTimeout * do something, but this is not right.  More later :)","4":"Most programming environments give you some sort of a timer callback facility you can attach to one of your functions to do a thing periodically.  This is missing in VIM.  This script 'emulates' one by doing a quick series of un-obstrusive kepresses that cause the key pressed timeout to reset continually.  Normally this happens every for seconds.  This can be changed.  The updatetimer is used to achive this.  A value of 1000 will cause the 'timer' to be called every one second.  When you want to hook something up to this timer, simply create an autocommand for on update wait or something, I forget what it is called.  It looks something similar to: au * onUpdateTimeout * do something, but this is not right.  More later :)","install_details":"Paste it in your _vimrc somewhere.","5":"Paste it in your _vimrc somewhere.","first_name":"Paul","6":"Paul","last_name":"Contreras","7":"Contreras","releases":[{"0":"3244","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Just modified the tail 'END TIMER' comment to make it dead obvious to you when you read it where this script ends.","3":"Just modified the tail 'END TIMER' comment to make it dead obvious to you when you read it where this script ends.","package":"Timer.vim","4":"Timer.vim","src_id":"13872","5":"13872","creation_date":"1284926066","6":"1284926066"},{"0":"3244","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"Timer.vim","4":"Timer.vim","src_id":"13867","5":"13867","creation_date":"1284901782","6":"1284901782"}]},"3243":{"script_id":"3243","0":"3243","script_name":"aspnetide.vim","1":"aspnetide.vim","script_type":"ftplugin","2":"ftplugin","summary":"aspnetide.vim: A Plugin that turns vim into an asp.net IDE!","3":"aspnetide.vim: A Plugin that turns vim into an asp.net IDE!","description":"Turns VIM into an asp.net IDE!\r\n\r\nFeatures\r\n-------------\r\n* ASPHelp - F1: Jump to online help based on selected word.\r\n* ASPBuild - <leader>ab: Find a solution file for the project and build. Errors shown in quickfix.\r\n* ASPAltFile - <leader>af: Navigate to alternate files (ASPX <-> code-behind).\r\n* ASPRun - F5: Run app in local webserver and navigate to selected page.\r\n* ASPGoTo - <leader>ag: Go to class file based on name.\r\n\r\nScreencast of how to use this plugin:\r\nhttp:\/\/www.youtube.com\/watch?v=9lYgblj1tc0\r\n\r\nNotes:\r\n--------\r\n*For those new to vim, <leader> is a backslash by default.\r\n*You may need to have VS.NET installed for ASPRun to work. Not sure if the local web server gets installed with just the framework.\r\n*The  ASPBuild and ASPRun features only work on windows. With a few tweaks this could work nicely for mono on linux though...\r\n\r\nPatches welcome, github location:\r\ngit:\/\/github.com\/bryanthankins\/vim-aspnetide.git","4":"Turns VIM into an asp.net IDE!\r\n\r\nFeatures\r\n-------------\r\n* ASPHelp - F1: Jump to online help based on selected word.\r\n* ASPBuild - <leader>ab: Find a solution file for the project and build. Errors shown in quickfix.\r\n* ASPAltFile - <leader>af: Navigate to alternate files (ASPX <-> code-behind).\r\n* ASPRun - F5: Run app in local webserver and navigate to selected page.\r\n* ASPGoTo - <leader>ag: Go to class file based on name.\r\n\r\nScreencast of how to use this plugin:\r\nhttp:\/\/www.youtube.com\/watch?v=9lYgblj1tc0\r\n\r\nNotes:\r\n--------\r\n*For those new to vim, <leader> is a backslash by default.\r\n*You may need to have VS.NET installed for ASPRun to work. Not sure if the local web server gets installed with just the framework.\r\n*The  ASPBuild and ASPRun features only work on windows. With a few tweaks this could work nicely for mono on linux though...\r\n\r\nPatches welcome, github location:\r\ngit:\/\/github.com\/bryanthankins\/vim-aspnetide.git","install_details":"Extract the zip file to ~\/.vim (or vimfiles on Windows).  To use the help, see :help add-local-help.  In a nutshell, :helptags ~\/.vim\/doc. (or :helptags $VIM\/vimfiles\/doc on windows)\r\n\r\nFor details, see :help aspnetide","5":"Extract the zip file to ~\/.vim (or vimfiles on Windows).  To use the help, see :help add-local-help.  In a nutshell, :helptags ~\/.vim\/doc. (or :helptags $VIM\/vimfiles\/doc on windows)\r\n\r\nFor details, see :help aspnetide","first_name":"Bryant","6":"Bryant","last_name":"Hankins","7":"Hankins","releases":[{"0":"3243","vim_version":"7.0","1":"7.0","script_version":"1.6","2":"1.6","version_comment":"Fixed issue with Build Succeeded showing improperly","3":"Fixed issue with Build Succeeded showing improperly","package":"aspnetide.zip","4":"aspnetide.zip","src_id":"14118","5":"14118","creation_date":"1288025405","6":"1288025405"},{"0":"3243","vim_version":"7.0","1":"7.0","script_version":"1.5","2":"1.5","version_comment":"fixed plugin dir name and issue with build","3":"fixed plugin dir name and issue with build","package":"aspnetide.zip","4":"aspnetide.zip","src_id":"14087","5":"14087","creation_date":"1287611995","6":"1287611995"},{"0":"3243","vim_version":"7.0","1":"7.0","script_version":"1.4","2":"1.4","version_comment":"Updated the build process to filter warnings and remove cope","3":"Updated the build process to filter warnings and remove cope","package":"aspnetide.zip","4":"aspnetide.zip","src_id":"14055","5":"14055","creation_date":"1287103627","6":"1287103627"},{"0":"3243","vim_version":"7.0","1":"7.0","script_version":"1.3","2":"1.3","version_comment":"Updated to parse sln and use the proper target framework for building and running","3":"Updated to parse sln and use the proper target framework for building and running","package":"aspnetide.zip","4":"aspnetide.zip","src_id":"14013","5":"14013","creation_date":"1286409747","6":"1286409747"},{"0":"3243","vim_version":"7.0","1":"7.0","script_version":"1.2","2":"1.2","version_comment":"-fixed issue with DB loader","3":"-fixed issue with DB loader","package":"aspnetide.zip","4":"aspnetide.zip","src_id":"13985","5":"13985","creation_date":"1286211302","6":"1286211302"},{"0":"3243","vim_version":"7.0","1":"7.0","script_version":"1.1","2":"1.1","version_comment":"Fixed an issue with the \"Run\" command on asp.net 4.0 apps","3":"Fixed an issue with the \"Run\" command on asp.net 4.0 apps","package":"aspnetide.zip","4":"aspnetide.zip","src_id":"13971","5":"13971","creation_date":"1285979442","6":"1285979442"},{"0":"3243","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"-Added support for opening alternate file in new window\r\n-Added support for parsing web.config and loading conn strings into DBExt for easy querying.\r\n","3":"-Added support for opening alternate file in new window\r\n-Added support for parsing web.config and loading conn strings into DBExt for easy querying.\r\n","package":"aspnetide.zip","4":"aspnetide.zip","src_id":"13958","5":"13958","creation_date":"1285814970","6":"1285814970"},{"0":"3243","vim_version":"7.0","1":"7.0","script_version":"0.93","2":"0.93","version_comment":"-Added MVC support for \"Go to alternate file\". Will navigate between Controller and Template files","3":"-Added MVC support for \"Go to alternate file\". Will navigate between Controller and Template files","package":"aspnetide.zip","4":"aspnetide.zip","src_id":"13927","5":"13927","creation_date":"1285546398","6":"1285546398"},{"0":"3243","vim_version":"7.0","1":"7.0","script_version":"0.92","2":"0.92","version_comment":"Added vim docs. Changed key mappings to be more unique. Added goto file feature","3":"Added vim docs. Changed key mappings to be more unique. Added goto file feature","package":"aspnetide.zip","4":"aspnetide.zip","src_id":"13897","5":"13897","creation_date":"1285270520","6":"1285270520"},{"0":"3243","vim_version":"7.0","1":"7.0","script_version":"0.91","2":"0.91","version_comment":"-Added support for those with only the 3.5 framework msbuild installed\r\n-Added better error messages","3":"-Added support for those with only the 3.5 framework msbuild installed\r\n-Added better error messages","package":"aspnetide.vim","4":"aspnetide.vim","src_id":"13875","5":"13875","creation_date":"1285003832","6":"1285003832"},{"0":"3243","vim_version":"7.0","1":"7.0","script_version":"0.9","2":"0.9","version_comment":"Initial upload","3":"Initial upload","package":"aspnetide.vim","4":"aspnetide.vim","src_id":"13865","5":"13865","creation_date":"1284865623","6":"1284865623"}]},"3242":{"script_id":"3242","0":"3242","script_name":"Open associated programs","1":"Open associated programs","script_type":"utility","2":"utility","summary":"Open files and web pages in associated programs from Vim","3":"Open files and web pages in associated programs from Vim","description":"This plug-in has been abandoned! Most of its code has been absorbed into my miscellaneous scripts for Vim (see https:\/\/github.com\/xolox\/vim-misc) while the user interface part is still found in the shell plug-in (vimscript #3123). I will no longer maintain the \"Open associated programs\" plug-in since I'm shifting focus to the miscellaneous scripts (because they're included in all of my Vim plug-ins and since I need the \"open associated programs\" functionality in several of my plug-ins, this makes most sense).\r\n\r\n----\r\n\r\nThis plug-in knows how to open files, directories, URLs and e-mail addresses from inside Vim using the associated programs. It should work on Windows, Mac OS X and most Linux installations. For more information about the plug-in please refer to its homepage or the project page on GitHub:\r\n\r\n \u00e2\u0080\u00a2 http:\/\/peterodding.com\/code\/vim\/open-associated-programs\/\r\n \u00e2\u0080\u00a2 http:\/\/github.com\/xolox\/vim-open-associated-programs\r\n\r\nIf you have questions, bug reports, suggestions, etc. the author can be contacted at peter@peterodding.com. If you like this plug-in please vote for it below!","4":"This plug-in has been abandoned! Most of its code has been absorbed into my miscellaneous scripts for Vim (see https:\/\/github.com\/xolox\/vim-misc) while the user interface part is still found in the shell plug-in (vimscript #3123). I will no longer maintain the \"Open associated programs\" plug-in since I'm shifting focus to the miscellaneous scripts (because they're included in all of my Vim plug-ins and since I need the \"open associated programs\" functionality in several of my plug-ins, this makes most sense).\r\n\r\n----\r\n\r\nThis plug-in knows how to open files, directories, URLs and e-mail addresses from inside Vim using the associated programs. It should work on Windows, Mac OS X and most Linux installations. For more information about the plug-in please refer to its homepage or the project page on GitHub:\r\n\r\n \u00e2\u0080\u00a2 http:\/\/peterodding.com\/code\/vim\/open-associated-programs\/\r\n \u00e2\u0080\u00a2 http:\/\/github.com\/xolox\/vim-open-associated-programs\r\n\r\nIf you have questions, bug reports, suggestions, etc. the author can be contacted at peter@peterodding.com. If you like this plug-in please vote for it below!","install_details":"Unzip the most recent ZIP archive file (see below) inside your Vim profile directory (usually this is \"~\/.vim\" on UNIX and \"%USERPROFILE%\\vimfiles\" on Windows), restart Vim and execute the command \":helptags ~\/.vim\/doc\" (use \":helptags ~\\vimfiles\\doc\" instead on Windows).\r\n\r\nNote that on Windows a command prompt window pops up when either of the functions is called. If this bothers you then you can install my shell.vim plug-in (see vimscript #3123) which includes a DLL that works around this issue. Once you\u00e2\u0080\u0099ve installed both plug-ins it should work out of the box!","5":"Unzip the most recent ZIP archive file (see below) inside your Vim profile directory (usually this is \"~\/.vim\" on UNIX and \"%USERPROFILE%\\vimfiles\" on Windows), restart Vim and execute the command \":helptags ~\/.vim\/doc\" (use \":helptags ~\\vimfiles\\doc\" instead on Windows).\r\n\r\nNote that on Windows a command prompt window pops up when either of the functions is called. If this bothers you then you can install my shell.vim plug-in (see vimscript #3123) which includes a DLL that works around this issue. Once you\u00e2\u0080\u0099ve installed both plug-ins it should work out of the box!","first_name":"Peter","6":"Peter","last_name":"Odding","7":"Odding","releases":[{"0":"3242","vim_version":"7.0","1":"7.0","script_version":"1.2.1","2":"1.2.1","version_comment":"Bug fix for E121 in handle_error():\r\nhttps:\/\/github.com\/xolox\/vim-open-associated-programs\/commit\/87dd8d408b40710afbbc","3":"Bug fix for E121 in handle_error():\r\nhttps:\/\/github.com\/xolox\/vim-open-associated-programs\/commit\/87dd8d408b40710afbbc","package":"open-associated-programs.zip","4":"open-associated-programs.zip","src_id":"14429","5":"14429","creation_date":"1291427491","6":"1291427491"},{"0":"3242","vim_version":"7.0","1":"7.0","script_version":"1.2","2":"1.2","version_comment":"Renamed plug-in from \u00e2\u0080\u0098Open external location\u00e2\u0080\u0099 to \u00e2\u0080\u0098Open associated programs\u00e2\u0080\u0099:\r\nhttp:\/\/github.com\/xolox\/vim-open-associated-programs\/commit\/71111c7e19ae02368a5f","3":"Renamed plug-in from \u00e2\u0080\u0098Open external location\u00e2\u0080\u0099 to \u00e2\u0080\u0098Open associated programs\u00e2\u0080\u0099:\r\nhttp:\/\/github.com\/xolox\/vim-open-associated-programs\/commit\/71111c7e19ae02368a5f","package":"open-associated-programs.zip","4":"open-associated-programs.zip","src_id":"13855","5":"13855","creation_date":"1284825491","6":"1284825491"},{"0":"3242","vim_version":"7.0","1":"7.0","script_version":"1.1","2":"1.1","version_comment":"Fixed reference to vim.org, added GLVS header:\r\nhttp:\/\/github.com\/xolox\/vim-open-external-location\/commit\/c706b115c4","3":"Fixed reference to vim.org, added GLVS header:\r\nhttp:\/\/github.com\/xolox\/vim-open-external-location\/commit\/c706b115c4","package":"open-external-location.zip","4":"open-external-location.zip","src_id":"13852","5":"13852","creation_date":"1284767698","6":"1284767698"},{"0":"3242","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"open-external-location.zip","4":"open-external-location.zip","src_id":"13851","5":"13851","creation_date":"1284766842","6":"1284766842"}]},"3241":{"script_id":"3241","0":"3241","script_name":"bufsurf","1":"bufsurf","script_type":"utility","2":"utility","summary":"Plugin for navigating buffers webbrowser style.","3":"Plugin for navigating buffers webbrowser style.","description":"When editing multiple files oftentimes it would be nice to be able to go back\r\nand forth between the last edited files, just like a web browser allows the\r\nuser to navigate web pages forward and backward in history. The standard\r\n:bn(ext) and :bp(revious) Vim commands allow to switch between next and\r\nprevious buffers respectively, but they do no take the history of the last\r\nused files into account. Instead, they use the order in which the files were\r\nopened, which can cause confusion in case the user expects to navigate forward\r\nand backwards in history.  For example, in case the user opened the files A,\r\nB, and C in the order:\r\n\r\nA, B, C\r\n\r\nand the navigation history would be\r\n\r\nA, B, C, B\r\n\r\nthen :bp(revious) in the last buffer (B) would open up buffer A, where C is\r\npreferable. This buffer supplies the user with the commands :BufSurfForward\r\nand :BufSurfBack to navigate buffers forwards and backwards according to the\r\nnavigation history.\r\n\r\nThe latest version of this plugin is available at:\r\n\r\n  http:\/\/github.com\/ton\/vim-bufsurf\r\n\r\nBugs can be reported there as well.","4":"When editing multiple files oftentimes it would be nice to be able to go back\r\nand forth between the last edited files, just like a web browser allows the\r\nuser to navigate web pages forward and backward in history. The standard\r\n:bn(ext) and :bp(revious) Vim commands allow to switch between next and\r\nprevious buffers respectively, but they do no take the history of the last\r\nused files into account. Instead, they use the order in which the files were\r\nopened, which can cause confusion in case the user expects to navigate forward\r\nand backwards in history.  For example, in case the user opened the files A,\r\nB, and C in the order:\r\n\r\nA, B, C\r\n\r\nand the navigation history would be\r\n\r\nA, B, C, B\r\n\r\nthen :bp(revious) in the last buffer (B) would open up buffer A, where C is\r\npreferable. This buffer supplies the user with the commands :BufSurfForward\r\nand :BufSurfBack to navigate buffers forwards and backwards according to the\r\nnavigation history.\r\n\r\nThe latest version of this plugin is available at:\r\n\r\n  http:\/\/github.com\/ton\/vim-bufsurf\r\n\r\nBugs can be reported there as well.","install_details":"","5":"","first_name":"Ton","6":"Ton","last_name":"van den Heuvel","7":"van den Heuvel","releases":[{"0":"3241","vim_version":"7.3","1":"7.3","script_version":"0.2","2":"0.2","version_comment":"- Rewritten in vimscript (drop Ruby dependency).\r\n- Allow ignoring specific buffer names from showing up in the navigation history.","3":"- Rewritten in vimscript (drop Ruby dependency).\r\n- Allow ignoring specific buffer names from showing up in the navigation history.","package":"bufsurf.tar.gz","4":"bufsurf.tar.gz","src_id":"15252","5":"15252","creation_date":"1300570953","6":"1300570953"},{"0":"3241","vim_version":"7.2","1":"7.2","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"bufsurf.tar.gz","4":"bufsurf.tar.gz","src_id":"13847","5":"13847","creation_date":"1284743310","6":"1284743310"}]},"3240":{"script_id":"3240","0":"3240","script_name":"tdvim_FoldDigest","1":"tdvim_FoldDigest","script_type":"utility","2":"utility","summary":"Creates an outline view from folds in the current buffer","3":"Creates an outline view from folds in the current buffer","description":"This plugin creates a new buffer with an outline view of all folds in the current buffer.\r\nIt is based on vimscript #732.\r\nUsage:\r\n\t:FoldDigest\r\n\r\n   Transform all folds in the current buffer into digest tree form, and\r\n   show it in another buffer.  The buffer is called ==FOLDDIGEST==.  It shows\r\n   not only all fold start positions, but also a tree depended on original\r\n   folds hierarchy.\r\n\r\n   In a FOLDDIGEST, you can move around the cursor, and when type <CR> jump\r\n   to fold at under it.  If you enter FOLDDIGEST window from other windows,\r\n   when depended buffer is availabeled, it will be synchronized\r\n   automatically.  If you want to force synchronize, type \"r\" in a\r\n   FOLDDIGEST buffer.\r\n   It is also possible to jump to the folsd under the cursor with a double\r\n   click.\r\n   The FOLDDIGEST window is updated when entering in a new buffer.\r\n\r\n   :FoldDigestToggle\r\n\r\n   Toggles FOLDDIGEST window\r\n\r\n   :FoldDigestClose\r\n\r\n   close FOLDDIGEST window\r\n\r\n   You can also map your own keys to these commands","4":"This plugin creates a new buffer with an outline view of all folds in the current buffer.\r\nIt is based on vimscript #732.\r\nUsage:\r\n\t:FoldDigest\r\n\r\n   Transform all folds in the current buffer into digest tree form, and\r\n   show it in another buffer.  The buffer is called ==FOLDDIGEST==.  It shows\r\n   not only all fold start positions, but also a tree depended on original\r\n   folds hierarchy.\r\n\r\n   In a FOLDDIGEST, you can move around the cursor, and when type <CR> jump\r\n   to fold at under it.  If you enter FOLDDIGEST window from other windows,\r\n   when depended buffer is availabeled, it will be synchronized\r\n   automatically.  If you want to force synchronize, type \"r\" in a\r\n   FOLDDIGEST buffer.\r\n   It is also possible to jump to the folsd under the cursor with a double\r\n   click.\r\n   The FOLDDIGEST window is updated when entering in a new buffer.\r\n\r\n   :FoldDigestToggle\r\n\r\n   Toggles FOLDDIGEST window\r\n\r\n   :FoldDigestClose\r\n\r\n   close FOLDDIGEST window\r\n\r\n   You can also map your own keys to these commands","install_details":"Extract the file at one of your vim directories.\r\n  ex. $HOME\/.vim\/\r\n  ex. $HOME\\vimfiles\\\r\n  ex. $VIM\\vimfiles\\","5":"Extract the file at one of your vim directories.\r\n  ex. $HOME\/.vim\/\r\n  ex. $HOME\\vimfiles\\\r\n  ex. $VIM\\vimfiles\\","first_name":"Pablo","6":"Pablo","last_name":"Gimenez","7":"Gimenez","releases":[{"0":"3240","vim_version":"7.2","1":"7.2","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"tdvimFoldDigest_0.1.tgz","4":"tdvimFoldDigest_0.1.tgz","src_id":"13843","5":"13843","creation_date":"1284660909","6":"1284660909"}]},"3239":{"script_id":"3239","0":"3239","script_name":"minibufexplorer++","1":"minibufexplorer++","script_type":"utility","2":"utility","summary":"Elegant buffer explorer - takes very little screen space","3":"Elegant buffer explorer - takes very little screen space","description":"This script is deprecated! A new and more experienced maintainer, Federico Holgado, has stepped up and is now maintaining a more updated version of this plugin on https:\/\/github.com\/fholgado\/minibufexpl.vim - please get it from there!\r\n\r\nThis is a modification of the original script available here: http:\/\/www.vim.org\/scripts\/script.php?script_id=159\r\n\r\nAdded to the original script were the following keybindings:\r\nh and l to move left and right when selecting buffers in addition to the original Tab and Shift-Tab\r\no and e to show a buffer in addition to the original <CR>\r\ns to open the selected buffer in a split window\r\nv to open the selected buffer in a vertically split window\r\n\r\nBig thanks to Bindu Wavell for writing this script! I just added some minor things which I think others might find useful. I tried submitting this as a patch to him, but got no answer. Bindu: Contact me if you want to integrate this into your plugin and I'll remove this one.\r\n\r\nOriginal description:\r\n\r\nSeveral modern GUI editors list your open buffers as tabs along the top or bottom of your screen (VisualStudio, DreamWeaver, EditPlus and UltraEdit come to mind), now we have this feature in VIM! You can checkout a screenshot here: http:\/\/www.wavell.net\/vim\/vim_screenshot.gif. \r\n\r\nYou can quickly switch buffers by double-clicking the appropriate \"tab\" (if you don't want to use the mouse just put the cursor on the \"tab\" and press enter). As you open and close buffers the tabs get updated. Buffers that are modified get visually marked and buffers that are open in a window get visually marked. The -MiniBufferExplorer- opens automatically when you open more than one eligible buffer (no need to open the explorer if you\u00e2\u0080\u0099re only editing one file.) -MiniBufExplorer- doesn't bother showing non-modifiable or hidden buffers. You can delete buffers by selecting them and pressing d on the keyboard. \r\n\r\nWhen you are in the -MiniBufExplorer- window, Tab and Shift-Tab move forward and backward respectively through the buffer list. \r\n\r\nThere are a growing number of optional features in this script that are enabled by letting variables in your .vimrc: \r\n\r\n  control + the vim direction keys [hjkl] can be made to move you between windows. \r\n  control + arrow keys can be made to do the same thing \r\n  control + tab & shift + control + tab can be setup to switch through your open windows (like in MS Windows) \r\n  control + tab & shift + control + tab can alternatively be setup to cycle forwards and backwards through your modifiable buffers in the current window \r\n\r\nNOTE: Some versions of vim don't support all of the key mappings that this script uses so you may experience degraded functionality. For example on Solaris SHIFT-TAB appears to fire the regular TAB mappings (same for console and gvim.) Also CONTROL+ARROWS appears to work in gvim on Solaris, but not in my xterm. All of the key bindings appear to work in Windows. \r\n\r\n[Thanks to Jeff Lanzarotta for his BufExplorer plugin (http:\/\/vim.sourceforge.net\/scripts\/script.php?script_id=42) that got me started down this slippery slope.]","4":"This script is deprecated! A new and more experienced maintainer, Federico Holgado, has stepped up and is now maintaining a more updated version of this plugin on https:\/\/github.com\/fholgado\/minibufexpl.vim - please get it from there!\r\n\r\nThis is a modification of the original script available here: http:\/\/www.vim.org\/scripts\/script.php?script_id=159\r\n\r\nAdded to the original script were the following keybindings:\r\nh and l to move left and right when selecting buffers in addition to the original Tab and Shift-Tab\r\no and e to show a buffer in addition to the original <CR>\r\ns to open the selected buffer in a split window\r\nv to open the selected buffer in a vertically split window\r\n\r\nBig thanks to Bindu Wavell for writing this script! I just added some minor things which I think others might find useful. I tried submitting this as a patch to him, but got no answer. Bindu: Contact me if you want to integrate this into your plugin and I'll remove this one.\r\n\r\nOriginal description:\r\n\r\nSeveral modern GUI editors list your open buffers as tabs along the top or bottom of your screen (VisualStudio, DreamWeaver, EditPlus and UltraEdit come to mind), now we have this feature in VIM! You can checkout a screenshot here: http:\/\/www.wavell.net\/vim\/vim_screenshot.gif. \r\n\r\nYou can quickly switch buffers by double-clicking the appropriate \"tab\" (if you don't want to use the mouse just put the cursor on the \"tab\" and press enter). As you open and close buffers the tabs get updated. Buffers that are modified get visually marked and buffers that are open in a window get visually marked. The -MiniBufferExplorer- opens automatically when you open more than one eligible buffer (no need to open the explorer if you\u00e2\u0080\u0099re only editing one file.) -MiniBufExplorer- doesn't bother showing non-modifiable or hidden buffers. You can delete buffers by selecting them and pressing d on the keyboard. \r\n\r\nWhen you are in the -MiniBufExplorer- window, Tab and Shift-Tab move forward and backward respectively through the buffer list. \r\n\r\nThere are a growing number of optional features in this script that are enabled by letting variables in your .vimrc: \r\n\r\n  control + the vim direction keys [hjkl] can be made to move you between windows. \r\n  control + arrow keys can be made to do the same thing \r\n  control + tab & shift + control + tab can be setup to switch through your open windows (like in MS Windows) \r\n  control + tab & shift + control + tab can alternatively be setup to cycle forwards and backwards through your modifiable buffers in the current window \r\n\r\nNOTE: Some versions of vim don't support all of the key mappings that this script uses so you may experience degraded functionality. For example on Solaris SHIFT-TAB appears to fire the regular TAB mappings (same for console and gvim.) Also CONTROL+ARROWS appears to work in gvim on Solaris, but not in my xterm. All of the key bindings appear to work in Windows. \r\n\r\n[Thanks to Jeff Lanzarotta for his BufExplorer plugin (http:\/\/vim.sourceforge.net\/scripts\/script.php?script_id=42) that got me started down this slippery slope.]","install_details":"Go to https:\/\/github.com\/fholgado\/minibufexpl.vim to download the plugin.\r\n\r\nCopy minibufexpl.vim into your plugin directory. Or :source minibufexpl.vim. That is all you need to get started. \r\n\r\nIf you want to enable extra functionality (documented in the source) you might want to add the following to your .vimrc: \r\n\r\n  let g:miniBufExplMapWindowNavVim = 1 \r\n  let g:miniBufExplMapWindowNavArrows = 1 \r\n  let g:miniBufExplMapCTabSwitchBufs = 1 \r\n  let g:miniBufExplModSelTarget = 1 \r\n\r\nThese are options that I expect most user will enjoy. \r\n\r\nYou can configure things like how tabs wrap, how big or small the explorer window is, if the explorer window is horizonal or vertical, the use of single or double click for buffer selection, what colors are used for the tabs in different states, how many buffers need to be open before the explorer window opens, etc. There are also some commands that you can use in your own key bindings for simple buffer manipulation. All of these options and more are documented at the top of the source file.","5":"Go to https:\/\/github.com\/fholgado\/minibufexpl.vim to download the plugin.\r\n\r\nCopy minibufexpl.vim into your plugin directory. Or :source minibufexpl.vim. That is all you need to get started. \r\n\r\nIf you want to enable extra functionality (documented in the source) you might want to add the following to your .vimrc: \r\n\r\n  let g:miniBufExplMapWindowNavVim = 1 \r\n  let g:miniBufExplMapWindowNavArrows = 1 \r\n  let g:miniBufExplMapCTabSwitchBufs = 1 \r\n  let g:miniBufExplModSelTarget = 1 \r\n\r\nThese are options that I expect most user will enjoy. \r\n\r\nYou can configure things like how tabs wrap, how big or small the explorer window is, if the explorer window is horizonal or vertical, the use of single or double click for buffer selection, what colors are used for the tabs in different states, how many buffers need to be open before the explorer window opens, etc. There are also some commands that you can use in your own key bindings for simple buffer manipulation. All of these options and more are documented at the top of the source file.","first_name":"Oliver","6":"Oliver","last_name":"Uvman","7":"Uvman","releases":[{"0":"3239","vim_version":"6.0","1":"6.0","script_version":"6.3.4","2":"6.3.4","version_comment":"Now returns to augroup NONE after setting augroup commands. Big thanks to Maciej Łaszcz for the bug report!\r\n","3":"Now returns to augroup NONE after setting augroup commands. Big thanks to Maciej Łaszcz for the bug report!\r\n","package":"minibufexplpp.vim","4":"minibufexplpp.vim","src_id":"14207","5":"14207","creation_date":"1289236705","6":"1289236705"},{"0":"3239","vim_version":"7.0","1":"7.0","script_version":"6.3.3","2":"6.3.3","version_comment":"Initial upload","3":"Initial upload","package":"minibufexplpp.vim","4":"minibufexplpp.vim","src_id":"13838","5":"13838","creation_date":"1284574277","6":"1284574277"}]},"3238":{"script_id":"3238","0":"3238","script_name":"LimitWindowSize","1":"LimitWindowSize","script_type":"utility","2":"utility","summary":"Reduce the current window size by placing an empty padding window next to it. ","3":"Reduce the current window size by placing an empty padding window next to it. ","description":"DESCRIPTION\r\nText files that do not have \"hard\" word wrapping via embedded line breaks can\r\nbe cumbersome to edit in a wide editor window, as it is strenuous on the eyes\r\nto jump back and forth between begin and end of the soft-wrapped lines.\r\nThe simplest solution is to resize the editor window (:set columns=80), but\r\none may still want to have the large editor size for other edited buffers that\r\nbenefit from the large screen real estate.\r\n\r\nThis plugin places an empty padding window next to the current window, thereby\r\nreducing its size while maintaining the overall editor size.\r\n\r\nUSAGE\r\n:LimitWindowWidth [{width}]\r\n                        Limit the window width of the current window by placing\r\n                        an empty padding window to the right. If there already\r\n                        is a padding window, its size is adapted according to\r\n                        'textwidth' \/ {width}, or removed if the width is so\r\n                        large that no padding is needed.","4":"DESCRIPTION\r\nText files that do not have \"hard\" word wrapping via embedded line breaks can\r\nbe cumbersome to edit in a wide editor window, as it is strenuous on the eyes\r\nto jump back and forth between begin and end of the soft-wrapped lines.\r\nThe simplest solution is to resize the editor window (:set columns=80), but\r\none may still want to have the large editor size for other edited buffers that\r\nbenefit from the large screen real estate.\r\n\r\nThis plugin places an empty padding window next to the current window, thereby\r\nreducing its size while maintaining the overall editor size.\r\n\r\nUSAGE\r\n:LimitWindowWidth [{width}]\r\n                        Limit the window width of the current window by placing\r\n                        an empty padding window to the right. If there already\r\n                        is a padding window, its size is adapted according to\r\n                        'textwidth' \/ {width}, or removed if the width is so\r\n                        large that no padding is needed.","install_details":"INSTALLATION\r\nThis script is packaged as a vimball. If you have the \"gunzip\" decompressor\r\nin your PATH, simply edit the *.vmb.gz package in Vim; otherwise, decompress\r\nthe archive first, e.g. using WinZip. Inside Vim, install by sourcing the\r\nvimball or via the :UseVimball command.\r\n    vim LimitWindowSize*.vmb.gz\r\n    :so %\r\nTo uninstall, use the :RmVimball command.\r\n\r\nDEPENDENCIES\r\n- Requires Vim 7.0 or higher.\r\n- Requires the ingo-library.vim plugin (vimscript #4433), version 1.004 or\r\n  higher.","5":"INSTALLATION\r\nThis script is packaged as a vimball. If you have the \"gunzip\" decompressor\r\nin your PATH, simply edit the *.vmb.gz package in Vim; otherwise, decompress\r\nthe archive first, e.g. using WinZip. Inside Vim, install by sourcing the\r\nvimball or via the :UseVimball command.\r\n    vim LimitWindowSize*.vmb.gz\r\n    :so %\r\nTo uninstall, use the :RmVimball command.\r\n\r\nDEPENDENCIES\r\n- Requires Vim 7.0 or higher.\r\n- Requires the ingo-library.vim plugin (vimscript #4433), version 1.004 or\r\n  higher.","first_name":"Ingo","6":"Ingo","last_name":"Karkat","7":"Karkat","releases":[{"0":"3238","vim_version":"7.0","1":"7.0","script_version":"1.01","2":"1.01","version_comment":"- Add workaround for when a :LimitWindowWidth command is issued from a still minimized GVIM in the process of restoring its window. The check for the window width then needs to be delayed until after the VimResized event.\r\n- Add dependency to ingo-library (vimscript #4433). *** You need to separately install ingo-library (vimscript #4433) version 1.004 (or higher)! ***","3":"- Add workaround for when a :LimitWindowWidth command is issued from a still minimized GVIM in the process of restoring its window. The check for the window width then needs to be delayed until after the VimResized event.\r\n- Add dependency to ingo-library (vimscript #4433). *** You need to separately install ingo-library (vimscript #4433) version 1.004 (or higher)! ***","package":"LimitWindowSize-1.01.vmb.gz","4":"LimitWindowSize-1.01.vmb.gz","src_id":"21123","5":"21123","creation_date":"1385714262","6":"1385714262"},{"0":"3238","vim_version":"7.0","1":"7.0","script_version":"1.00","2":"1.00","version_comment":"Initial upload","3":"Initial upload","package":"LimitWindowSize.vba.gz","4":"LimitWindowSize.vba.gz","src_id":"13830","5":"13830","creation_date":"1284490455","6":"1284490455"}]},"3237":{"script_id":"3237","0":"3237","script_name":"blockinsert","1":"blockinsert","script_type":"utility","2":"utility","summary":"Easy Insert\/Append to a paragraph of text","3":"Easy Insert\/Append to a paragraph of text","description":"                   Easy Insert\/Append to a paragraph of text\r\n\r\nBlockinsert can take a range but if no such is given it will act upon the\r\ncurrent paragraph.\r\n\r\n        First line of code\r\n            Another line of code\r\n    Yet another one\r\n        Last line of code\r\n\r\n1.1 Insert\r\n\r\n[count] \\i - will transform the above into: (count 3 used)\r\n\r\n        ---First line of code\r\n            ---Another line of code\r\n    ---Yet another one\r\n        ---Last line of code\r\n\r\n1.2 Append\r\n\r\n[count] \\a > will transform the above into: (count 2 used)\r\n\r\n        ---First line of code>>\r\n            ---Another line of code>>\r\n    ---Yet another one>>\r\n        ---Last line of code>>\r\n\r\n1.3 Delete\r\n\r\n[count] \\i or \\a without any text will delete as many characters: (3\\i used)\r\n\r\n        First line of code>>\r\n            Another line of code>>\r\n    Yet another one>>\r\n        Last line of code>>\r\n\r\n1.4 Act on both ends\r\n\r\n[count] \\[] will use both \\i and \\a: (2\\[] * ** used)\r\n\r\n        Note: the same [count] will be applied to both operations\r\n\r\n        **First line of code>>****\r\n            **Another line of code>>****\r\n    **Yet another one>>****\r\n        **Last line of code>>****\r\n\r\n1.5 Act on both ends using the same text\r\n\r\n[count] \\[[ will use both \\i and \\a and the same text: (| used)\r\n\r\n        |**First line of code>>****|\r\n            |**Another line of code>>****|\r\n    |**Yet another one>>****|\r\n        |**Last line of code>>****|\r\n\r\n1.6 Record\r\n\r\n\\qi, \\qa and \\q[] will execute rather than write the text in input.\r\n\r\nExample with \\qa gUaW:\r\n\r\n        |**First line of CODE>>****|\r\n            |**Another line of CODE>>****|\r\n    |**Yet another ONE>>****|\r\n        |**Last line of CODE>>****|\r\n\r\n==========================================================\r\n\r\nThere is one special case. When selecting text in visual block mode, the\r\nboundaries of the text acted upon are defined by the limits of the visual area.\r\n\r\nExample: (the <bar>s represent our selection)\r\n\r\n    Some text here                |stridx(      |       end of this line\r\n    Some other text...            |strridx(     |       text after a function\r\n    Let's start a third line       |strlen(      |       ...finish this line\r\n    End of paragraph            |substitute(|       end indeed.\r\n\r\nNow that a selection has been defined, all you need to do is type:\r\n\\a followed by )\r\nand your text will become:\r\n\r\n    Some text here                 stridx()              end of this line\r\n    Some other text...             strridx()             text after a function\r\n    Let's start a third line        strlen()              ...finish this line\r\n    End of paragraph              substitute()       end indeed.\r\n\r\n==========================================================\r\n\r\nFor all this to work you MUST define your custom mappings in your vimrc:\r\n\r\nvmap <leader>i  <plug>blockinsert-i\r\nvmap <leader>a  <plug>blockinsert-a\r\nvmap <leader>qi <plug>blockinsert-qi\r\nvmap <leader>qa <plug>blockinsert-qa\r\n\r\nnmap <leader>i  <plug>blockinsert-i\r\nnmap <leader>a  <plug>blockinsert-a\r\nnmap <leader>qi <plug>blockinsert-qi\r\nnmap <leader>qa <plug>blockinsert-qa\r\n\r\nvmap <leader>[]  <plug>blockinsert-b\r\nvmap <leader>[[  <plug>blockinsert-ub\r\nvmap <leader>]]  <plug>blockinsert-ub\r\nvmap <leader>q[] <plug>blockinsert-qb\r\nvmap <leader>q[[ <plug>blockinsert-uqb\r\nvmap <leader>q]] <plug>blockinsert-uqb\r\n\r\nnmap <leader>[]  <plug>blockinsert-b\r\nnmap <leader>[[  <plug>blockinsert-ub\r\nnmap <leader>]]  <plug>blockinsert-ub\r\nnmap <leader>q[] <plug>blockinsert-qb\r\nnmap <leader>q[[ <plug>blockinsert-uqb\r\nnmap <leader>q]] <plug>blockinsert-uqb\r\n\r\nNote: You can replace \\i, \\a, \\qi, \\qa, \\[], \\[[, \\]], \\q[], \\q[[, \\q]]\r\n      with whatever you like.","4":"                   Easy Insert\/Append to a paragraph of text\r\n\r\nBlockinsert can take a range but if no such is given it will act upon the\r\ncurrent paragraph.\r\n\r\n        First line of code\r\n            Another line of code\r\n    Yet another one\r\n        Last line of code\r\n\r\n1.1 Insert\r\n\r\n[count] \\i - will transform the above into: (count 3 used)\r\n\r\n        ---First line of code\r\n            ---Another line of code\r\n    ---Yet another one\r\n        ---Last line of code\r\n\r\n1.2 Append\r\n\r\n[count] \\a > will transform the above into: (count 2 used)\r\n\r\n        ---First line of code>>\r\n            ---Another line of code>>\r\n    ---Yet another one>>\r\n        ---Last line of code>>\r\n\r\n1.3 Delete\r\n\r\n[count] \\i or \\a without any text will delete as many characters: (3\\i used)\r\n\r\n        First line of code>>\r\n            Another line of code>>\r\n    Yet another one>>\r\n        Last line of code>>\r\n\r\n1.4 Act on both ends\r\n\r\n[count] \\[] will use both \\i and \\a: (2\\[] * ** used)\r\n\r\n        Note: the same [count] will be applied to both operations\r\n\r\n        **First line of code>>****\r\n            **Another line of code>>****\r\n    **Yet another one>>****\r\n        **Last line of code>>****\r\n\r\n1.5 Act on both ends using the same text\r\n\r\n[count] \\[[ will use both \\i and \\a and the same text: (| used)\r\n\r\n        |**First line of code>>****|\r\n            |**Another line of code>>****|\r\n    |**Yet another one>>****|\r\n        |**Last line of code>>****|\r\n\r\n1.6 Record\r\n\r\n\\qi, \\qa and \\q[] will execute rather than write the text in input.\r\n\r\nExample with \\qa gUaW:\r\n\r\n        |**First line of CODE>>****|\r\n            |**Another line of CODE>>****|\r\n    |**Yet another ONE>>****|\r\n        |**Last line of CODE>>****|\r\n\r\n==========================================================\r\n\r\nThere is one special case. When selecting text in visual block mode, the\r\nboundaries of the text acted upon are defined by the limits of the visual area.\r\n\r\nExample: (the <bar>s represent our selection)\r\n\r\n    Some text here                |stridx(      |       end of this line\r\n    Some other text...            |strridx(     |       text after a function\r\n    Let's start a third line       |strlen(      |       ...finish this line\r\n    End of paragraph            |substitute(|       end indeed.\r\n\r\nNow that a selection has been defined, all you need to do is type:\r\n\\a followed by )\r\nand your text will become:\r\n\r\n    Some text here                 stridx()              end of this line\r\n    Some other text...             strridx()             text after a function\r\n    Let's start a third line        strlen()              ...finish this line\r\n    End of paragraph              substitute()       end indeed.\r\n\r\n==========================================================\r\n\r\nFor all this to work you MUST define your custom mappings in your vimrc:\r\n\r\nvmap <leader>i  <plug>blockinsert-i\r\nvmap <leader>a  <plug>blockinsert-a\r\nvmap <leader>qi <plug>blockinsert-qi\r\nvmap <leader>qa <plug>blockinsert-qa\r\n\r\nnmap <leader>i  <plug>blockinsert-i\r\nnmap <leader>a  <plug>blockinsert-a\r\nnmap <leader>qi <plug>blockinsert-qi\r\nnmap <leader>qa <plug>blockinsert-qa\r\n\r\nvmap <leader>[]  <plug>blockinsert-b\r\nvmap <leader>[[  <plug>blockinsert-ub\r\nvmap <leader>]]  <plug>blockinsert-ub\r\nvmap <leader>q[] <plug>blockinsert-qb\r\nvmap <leader>q[[ <plug>blockinsert-uqb\r\nvmap <leader>q]] <plug>blockinsert-uqb\r\n\r\nnmap <leader>[]  <plug>blockinsert-b\r\nnmap <leader>[[  <plug>blockinsert-ub\r\nnmap <leader>]]  <plug>blockinsert-ub\r\nnmap <leader>q[] <plug>blockinsert-qb\r\nnmap <leader>q[[ <plug>blockinsert-uqb\r\nnmap <leader>q]] <plug>blockinsert-uqb\r\n\r\nNote: You can replace \\i, \\a, \\qi, \\qa, \\[], \\[[, \\]], \\q[], \\q[[, \\q]]\r\n      with whatever you like.","install_details":"blockinsert.vim --> ~\/.vim\/plugin\r\nblockinsert.txt  --> ~\/.vim\/doc\r\n\r\nLatest version at:\r\nhttps:\/\/github.com\/kurkale6ka\/vim-blockinsert","5":"blockinsert.vim --> ~\/.vim\/plugin\r\nblockinsert.txt  --> ~\/.vim\/doc\r\n\r\nLatest version at:\r\nhttps:\/\/github.com\/kurkale6ka\/vim-blockinsert","first_name":"Dimitar","6":"Dimitar","last_name":"Dimitrov","7":"Dimitrov","releases":[{"0":"3237","vim_version":"7.0","1":"7.0","script_version":"4.1","2":"4.1","version_comment":"A single line is a valid range now","3":"A single line is a valid range now","package":"blockinsert.zip","4":"blockinsert.zip","src_id":"13874","5":"13874","creation_date":"1284990733","6":"1284990733"},{"0":"3237","vim_version":"7.0","1":"7.0","script_version":"4.0","2":"4.0","version_comment":"Deletion:\r\n    made it work correctly in visual block mode\r\n    repeating it doesn't require to re-enter empty text anymore\r\n\r\nImproved interactive messages\r\n\r\nAdded support for right to left editing\r\n\r\nDefined g:blockinsert_commands and used it to disable blockinsert commands by\r\ndefault\r\n\r\nWhen repeating actions performed on a visual block selection, blank portions of\r\ntext in the new area will be correctly skipped.\r\n\r\nCorrected the virtualedit mess. Still need to disable it though.\r\nRenamed the commands to begin with Block... & created Block[Q]BothSame.\r\nUpdated the help file.","3":"Deletion:\r\n    made it work correctly in visual block mode\r\n    repeating it doesn't require to re-enter empty text anymore\r\n\r\nImproved interactive messages\r\n\r\nAdded support for right to left editing\r\n\r\nDefined g:blockinsert_commands and used it to disable blockinsert commands by\r\ndefault\r\n\r\nWhen repeating actions performed on a visual block selection, blank portions of\r\ntext in the new area will be correctly skipped.\r\n\r\nCorrected the virtualedit mess. Still need to disable it though.\r\nRenamed the commands to begin with Block... & created Block[Q]BothSame.\r\nUpdated the help file.","package":"blockinsert.zip","4":"blockinsert.zip","src_id":"13857","5":"13857","creation_date":"1284839816","6":"1284839816"},{"0":"3237","vim_version":"7.0","1":"7.0","script_version":"3.2","2":"3.2","version_comment":"The mappings can now operate on a visual block area defined anywhere.\r\nThe . (dot) is able to repeat that action now.","3":"The mappings can now operate on a visual block area defined anywhere.\r\nThe . (dot) is able to repeat that action now.","package":"blockinsert.zip","4":"blockinsert.zip","src_id":"13846","5":"13846","creation_date":"1284716682","6":"1284716682"},{"0":"3237","vim_version":"7.0","1":"7.0","script_version":"3.1","2":"3.1","version_comment":"Corrected a small regression which made the use of . (dot) impossible.","3":"Corrected a small regression which made the use of . (dot) impossible.","package":"blockinsert.zip","4":"blockinsert.zip","src_id":"13842","5":"13842","creation_date":"1284632974","6":"1284632974"},{"0":"3237","vim_version":"7.0","1":"7.0","script_version":"3.0","2":"3.0","version_comment":"New feature:\r\n\r\nAdded the possibility to define the boundaries of the text acted upon by drawing a visual block selection.\r\n\r\nExample: (the <bar>s represent our selection)\r\n\r\n    Some text here                |stridx(       |       end of this line\r\n    Some other text...            |strridx(      |       text after a function\r\n    Let's start a third line       |strlen(       |       ...finish this line\r\n    End of paragraph             |substitute(|       end indeed.\r\n\r\nNow that a selection has been defined, all you need to do is type:\r\n\\a followed by )\r\nand your text will become:\r\n\r\n    Some text here                 stridx()           end of this line\r\n    Some other text...             strridx()          text after a function\r\n    Let's start a third line        strlen()           ...finish this line\r\n    End of paragraph              substitute()    end indeed.\r\n\r\nEnjoy.\r\n\r\ntodo: Add the possibility to repeat this action by typing . (dot)\r\ntodo: Create \\[[, \\]], \\q[[, \\q]] for cases where we want the same text on both ends.","3":"New feature:\r\n\r\nAdded the possibility to define the boundaries of the text acted upon by drawing a visual block selection.\r\n\r\nExample: (the <bar>s represent our selection)\r\n\r\n    Some text here                |stridx(       |       end of this line\r\n    Some other text...            |strridx(      |       text after a function\r\n    Let's start a third line       |strlen(       |       ...finish this line\r\n    End of paragraph             |substitute(|       end indeed.\r\n\r\nNow that a selection has been defined, all you need to do is type:\r\n\\a followed by )\r\nand your text will become:\r\n\r\n    Some text here                 stridx()           end of this line\r\n    Some other text...             strridx()          text after a function\r\n    Let's start a third line        strlen()           ...finish this line\r\n    End of paragraph              substitute()    end indeed.\r\n\r\nEnjoy.\r\n\r\ntodo: Add the possibility to repeat this action by typing . (dot)\r\ntodo: Create \\[[, \\]], \\q[[, \\q]] for cases where we want the same text on both ends.","package":"blockinsert.zip","4":"blockinsert.zip","src_id":"13841","5":"13841","creation_date":"1284631110","6":"1284631110"},{"0":"3237","vim_version":"7.0","1":"7.0","script_version":"2.1","2":"2.1","version_comment":"2 bug fixes:\r\n\r\n- If a count was used with \\qi, \\qa or \\q[], it wasn't interpreted correctly.\r\n- There was also a problem with reseting virtualedit to its original value.","3":"2 bug fixes:\r\n\r\n- If a count was used with \\qi, \\qa or \\q[], it wasn't interpreted correctly.\r\n- There was also a problem with reseting virtualedit to its original value.","package":"blockinsert.zip","4":"blockinsert.zip","src_id":"13835","5":"13835","creation_date":"1284568128","6":"1284568128"},{"0":"3237","vim_version":"7.0","1":"7.0","script_version":"2.0","2":"2.0","version_comment":"Improved integration with the 'repeat' plugin.\r\n\r\nThe inserted \/ appended text is now remembered,\r\nyou don't have to re-enter it when repeating.","3":"Improved integration with the 'repeat' plugin.\r\n\r\nThe inserted \/ appended text is now remembered,\r\nyou don't have to re-enter it when repeating.","package":"blockinsert.zip","4":"blockinsert.zip","src_id":"13829","5":"13829","creation_date":"1284483351","6":"1284483351"},{"0":"3237","vim_version":"7.0","1":"7.0","script_version":"1.1","2":"1.1","version_comment":"Integrated blockinsert with Tim Pope's repeat plugin.\r\nIt is now possible to repeat blockinsert mappings by pressing . (dot)\r\n\r\nMore info about repeat:\r\nhttp:\/\/www.vim.org\/scripts\/script.php?script_id=2136\r\nhttp:\/\/github.com\/tpope\/vim-repeat","3":"Integrated blockinsert with Tim Pope's repeat plugin.\r\nIt is now possible to repeat blockinsert mappings by pressing . (dot)\r\n\r\nMore info about repeat:\r\nhttp:\/\/www.vim.org\/scripts\/script.php?script_id=2136\r\nhttp:\/\/github.com\/tpope\/vim-repeat","package":"blockinsert.zip","4":"blockinsert.zip","src_id":"13817","5":"13817","creation_date":"1284420458","6":"1284420458"},{"0":"3237","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"blockinsert.zip","4":"blockinsert.zip","src_id":"13816","5":"13816","creation_date":"1284386396","6":"1284386396"}]},"3236":{"script_id":"3236","0":"3236","script_name":"html5.vim","1":"html5.vim","script_type":"utility","2":"utility","summary":"HTML5 omnicomplete funtion and syntax for Vim","3":"HTML5 omnicomplete funtion and syntax for Vim","description":"HTML5 omnicomplete funtion and syntax for Vim.\r\nBased on the default htmlcomplete.vim.\r\n\r\nSupport all new elements and attribute.\r\nSupport microdata.\r\nSupport RDFa.\r\nSupport WAI-ARIA.\r\n\r\nsyntax from http:\/\/www.vim.org\/scripts\/script.php?script_id=3232\r\n\r\ngit repo: http:\/\/github.com\/othree\/html5.vim","4":"HTML5 omnicomplete funtion and syntax for Vim.\r\nBased on the default htmlcomplete.vim.\r\n\r\nSupport all new elements and attribute.\r\nSupport microdata.\r\nSupport RDFa.\r\nSupport WAI-ARIA.\r\n\r\nsyntax from http:\/\/www.vim.org\/scripts\/script.php?script_id=3232\r\n\r\ngit repo: http:\/\/github.com\/othree\/html5.vim","install_details":"Use vimball to install","5":"Use vimball to install","first_name":"wei ko","6":"wei ko","last_name":"kao","7":"kao","releases":[{"0":"3236","vim_version":"7.0","1":"7.0","script_version":"0.27","2":"0.27","version_comment":"Update to correct vimball, old vimball files didn't have enough data.","3":"Update to correct vimball, old vimball files didn't have enough data.","package":"html5.vim-0.27.vba","4":"html5.vim-0.27.vba","src_id":"16151","5":"16151","creation_date":"1311759627","6":"1311759627"}]},"3235":{"script_id":"3235","0":"3235","script_name":"showcolor.vim","1":"showcolor.vim","script_type":"utility","2":"utility","summary":"show all color in term or gui with vim.","3":"show all color in term or gui with vim.","description":"show all color in term or gui with vim.\r\n\r\nterm:\r\n:call ShowColorTerm()\r\ngui:\r\n:call ShowColor(0x00,0xFF,15)","4":"show all color in term or gui with vim.\r\n\r\nterm:\r\n:call ShowColorTerm()\r\ngui:\r\n:call ShowColor(0x00,0xFF,15)","install_details":"put it into plugin,then enjoy it.","5":"put it into plugin,then enjoy it.","first_name":"zhu","6":"zhu","last_name":"nianyang","7":"nianyang","releases":[{"0":"3235","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"showcolor.vim","4":"showcolor.vim","src_id":"13795","5":"13795","creation_date":"1284035552","6":"1284035552"}]},"3234":{"script_id":"3234","0":"3234","script_name":"ToggleLineNumberMode","1":"ToggleLineNumberMode","script_type":"utility","2":"utility","summary":"Switch between ","3":"Switch between ","description":"switch between \"Relative\" and \"Absolute\" line number is easy with command\r\n''':set nornu'''\r\nand\r\n''':set rnu'''\r\n\r\n\r\n\r\nit could be more easier by a vim script:\r\n\r\nfunction! g:ToggleNuMode()\r\n\tif(&rnu == 1)\r\n\t\tset nornu\r\n\telse\r\n\t\tset rnu\r\n\tendif\r\nendfunc\r\n\r\nand a Ctrl+L key map\r\nnnoremap <C-L> :call g:ToggleNuMode()<cr>\r\n\r\nthis is exactly what the script does, you can just put the code into your vimrc if you don't want install a plugin :)","4":"switch between \"Relative\" and \"Absolute\" line number is easy with command\r\n''':set nornu'''\r\nand\r\n''':set rnu'''\r\n\r\n\r\n\r\nit could be more easier by a vim script:\r\n\r\nfunction! g:ToggleNuMode()\r\n\tif(&rnu == 1)\r\n\t\tset nornu\r\n\telse\r\n\t\tset rnu\r\n\tendif\r\nendfunc\r\n\r\nand a Ctrl+L key map\r\nnnoremap <C-L> :call g:ToggleNuMode()<cr>\r\n\r\nthis is exactly what the script does, you can just put the code into your vimrc if you don't want install a plugin :)","install_details":"put it into your vimfiles\/plugin","5":"put it into your vimfiles\/plugin","first_name":"aj3423","6":"aj3423","last_name":" ","7":" ","releases":[{"0":"3234","vim_version":"7.3","1":"7.3","script_version":"1.1","2":"1.1","version_comment":"vim7.4 uses \"set nornu\"","3":"vim7.4 uses \"set nornu\"","package":"toggleRelative.vim","4":"toggleRelative.vim","src_id":"20820","5":"20820","creation_date":"1379593351","6":"1379593351"},{"0":"3234","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"toggleRelative.vim","4":"toggleRelative.vim","src_id":"13790","5":"13790","creation_date":"1284012253","6":"1284012253"}]},"3233":{"script_id":"3233","0":"3233","script_name":"VimgrepBuffer","1":"VimgrepBuffer","script_type":"utility","2":"utility","summary":"Run vimgrep on buffers","3":"Run vimgrep on buffers","description":"************************************************************************************\r\nThis plugin has been superceded by Buffersaurus, available at:\r\nhttp:\/\/www.vim.org\/scripts\/script.php?script_id=3620\r\n************************************************************************************\r\n\r\nThis plugin provides easy application of the 'vimgrep' command on buffers\r\n(as opposed to the filesystem, which is its normal mode of operation).\r\nIt provides two commands: one to search just the current buffer, and the\r\nother to search all listed buffers.\r\nThe QuickFix buffer will be populated with the search results, if any, and\r\nopened for viewing. The search pattern will also be assigned to the search\r\nregister, so that matches will be highlighted if 'hlsearch' is on (':set\r\nhlsearch').\r\n\r\nTwo commands are provided, ':G' and ':GG'. The first limits the search to\r\nthe current buffer, while the second searches all listed buffers.\r\n\r\nIf you do not like the cryptic\/genericness of these 'short' commands, put:\r\n\r\n    let g:vimgrepbuffer_long_command = 1\r\n\r\nin your \"~\/.vimrc\", and ':VimgrepBuffer' and ':VimgrepBuffers' will be set as\r\nthe commands instead.\r\n\r\nThe pattern specification is *exactly* like that for 'vimgrep'.  This means\r\nthat if the pattern starts with a non-identifier character or contains any literal whitespace\r\ncharacters, for correct behavior you will have to enclose the pattern in\r\ndelimiter characters (e.g. \"\/\", \"@\", \"#\"):\r\n\r\n   :G \/\\s*print \"\\d\/\r\n   :GG \/\\s*def\\s\\+\\w\\+(\/\r\n   :G \/\\(def\\s\\+\\|class\\s\\+\\)\/\r\n   :GG \/\\cisland\/\r\n   :G \/the quick brown \\w\\+\/\r\n   :GG \/except \\+\\w\\+Error\/\r\n\r\nIf your pattern starts with an identifier-character you can omit the enclosing\r\ndelimiters:\r\n\r\n   :G def\\s\\+\\w\\+(.*\\*\\*kwargs)\r\n   :GG except\\s\\+\\w\\+Error\r\n\r\nIn this latter case, the pattern will be considered to be\r\nwhitespace-delimited, and so if your pattern contains any literal whitespace\r\nyou may get incorrect results. This behavior is exactly like that of\r\n'vimgrep'.\r\n\r\nYou might also be interested in looking at \"grep.vim\" (http:\/\/www.vim.org\/scripts\/script.php?script_id=311) as an alternative for \"grep-on-buffer\" operations, especially if you want to use external grep programs.\r\n\"grep.vim\" provides a much broader range of functionality and commands, and is typically faster.  However, the grep dialect you will have to use is that of the external grep programs, rather than that of Vim. The main reason I wrote \"VimgrepBuffer\" (and why you might be interested in using it) is to be able to use Vim's grep dialect to express the search patterns. ","4":"************************************************************************************\r\nThis plugin has been superceded by Buffersaurus, available at:\r\nhttp:\/\/www.vim.org\/scripts\/script.php?script_id=3620\r\n************************************************************************************\r\n\r\nThis plugin provides easy application of the 'vimgrep' command on buffers\r\n(as opposed to the filesystem, which is its normal mode of operation).\r\nIt provides two commands: one to search just the current buffer, and the\r\nother to search all listed buffers.\r\nThe QuickFix buffer will be populated with the search results, if any, and\r\nopened for viewing. The search pattern will also be assigned to the search\r\nregister, so that matches will be highlighted if 'hlsearch' is on (':set\r\nhlsearch').\r\n\r\nTwo commands are provided, ':G' and ':GG'. The first limits the search to\r\nthe current buffer, while the second searches all listed buffers.\r\n\r\nIf you do not like the cryptic\/genericness of these 'short' commands, put:\r\n\r\n    let g:vimgrepbuffer_long_command = 1\r\n\r\nin your \"~\/.vimrc\", and ':VimgrepBuffer' and ':VimgrepBuffers' will be set as\r\nthe commands instead.\r\n\r\nThe pattern specification is *exactly* like that for 'vimgrep'.  This means\r\nthat if the pattern starts with a non-identifier character or contains any literal whitespace\r\ncharacters, for correct behavior you will have to enclose the pattern in\r\ndelimiter characters (e.g. \"\/\", \"@\", \"#\"):\r\n\r\n   :G \/\\s*print \"\\d\/\r\n   :GG \/\\s*def\\s\\+\\w\\+(\/\r\n   :G \/\\(def\\s\\+\\|class\\s\\+\\)\/\r\n   :GG \/\\cisland\/\r\n   :G \/the quick brown \\w\\+\/\r\n   :GG \/except \\+\\w\\+Error\/\r\n\r\nIf your pattern starts with an identifier-character you can omit the enclosing\r\ndelimiters:\r\n\r\n   :G def\\s\\+\\w\\+(.*\\*\\*kwargs)\r\n   :GG except\\s\\+\\w\\+Error\r\n\r\nIn this latter case, the pattern will be considered to be\r\nwhitespace-delimited, and so if your pattern contains any literal whitespace\r\nyou may get incorrect results. This behavior is exactly like that of\r\n'vimgrep'.\r\n\r\nYou might also be interested in looking at \"grep.vim\" (http:\/\/www.vim.org\/scripts\/script.php?script_id=311) as an alternative for \"grep-on-buffer\" operations, especially if you want to use external grep programs.\r\n\"grep.vim\" provides a much broader range of functionality and commands, and is typically faster.  However, the grep dialect you will have to use is that of the external grep programs, rather than that of Vim. The main reason I wrote \"VimgrepBuffer\" (and why you might be interested in using it) is to be able to use Vim's grep dialect to express the search patterns. ","install_details":"You can use this script as a plugin by copying it to your plugin directory (e.g., \"~\/.vim\/plugin\")\r\nSee |add-global-plugin| for instructions. ","5":"You can use this script as a plugin by copying it to your plugin directory (e.g., \"~\/.vim\/plugin\")\r\nSee |add-global-plugin| for instructions. ","first_name":"Jeet","6":"Jeet","last_name":"Sukumaran","7":"Sukumaran","releases":[{"0":"3233","vim_version":"7.0","1":"7.0","script_version":"1.0.1","2":"1.0.1","version_comment":"Added examples and clarification of reg-exp behavior to script documentation comments.","3":"Added examples and clarification of reg-exp behavior to script documentation comments.","package":"vimgrepbuffer.vim","4":"vimgrepbuffer.vim","src_id":"13787","5":"13787","creation_date":"1283999958","6":"1283999958"},{"0":"3233","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"vimgrepbuffer.vim","4":"vimgrepbuffer.vim","src_id":"13786","5":"13786","creation_date":"1283991107","6":"1283991107"}]},"3232":{"script_id":"3232","0":"3232","script_name":"HTML5 Syntax File","1":"HTML5 Syntax File","script_type":"syntax","2":"syntax","summary":"HTML5 Syntax File","3":"HTML5 Syntax File","description":"HTML5 syntax file plus microdata, RDFa, WAI-ARIA support\r\n\r\nRepository: http:\/\/github.com\/othree\/html5-syntax.vim","4":"HTML5 syntax file plus microdata, RDFa, WAI-ARIA support\r\n\r\nRepository: http:\/\/github.com\/othree\/html5-syntax.vim","install_details":"copy syntax\/html.vim to ~\/.vim\/syntax","5":"copy syntax\/html.vim to ~\/.vim\/syntax","first_name":"wei ko","6":"wei ko","last_name":"kao","7":"kao","releases":[{"0":"3232","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"html5-syntax.tar.gz","4":"html5-syntax.tar.gz","src_id":"13783","5":"13783","creation_date":"1283964727","6":"1283964727"}]},"3231":{"script_id":"3231","0":"3231","script_name":"PyInteractive","1":"PyInteractive","script_type":"utility","2":"utility","summary":"Simple python read-eval-print loop inside Vim","3":"Simple python read-eval-print loop inside Vim","description":"This plugin is a simple realization of read-eval-print loop for Python in Vim command window. It requires Python support (see +python) and at least version 2.6 of Python interpreter (you can check python version by running :py import sys; print(sys.version) ). \r\n\r\nFeatures:\r\n - auto-completion (tab)\r\n - auto-indent\r\n - keeps your recent results in the result history, for later user.\r\n - IPython-like magic operators (e.g. object?)\r\n - evaluate selected code\r\n - and more (see the pyinteractive documentation for details)\r\n\r\nDemonstration (ver 0.5): http:\/\/www.youtube.com\/watch?v=oy9Cv3eKy-0&feature=plcp\r\nProject home: https:\/\/github.com\/clericJ\/pyinteractive-vim\r\n\r\n\r\nCommands:\r\n\r\n :PyInteractiveREPL\r\n     Opens an interactive Python console in vim. If you want to finish working with the interpreter, \r\n      press <esc>. Interpreter states are saved between PyInteractive sessions (but not between vim\r\n     sessions), so that if you use PyInteractiveREPL, type x=1 here, close it and then reopen again, \r\n     variable x will still have value 1. \r\n\r\n  :PyInteractiveHistory [options]\r\n      Echoes session history.\r\n      Possible options:\r\n           -r          Print history without any formatting (mnemonic: raw)\r\n           -i          Print only input history (mnemonic: input)\r\n           -o          Print only output history (mnemonic: output)\r\n           -f {FILE}   Write history to file {FILE}\r\n\r\n :PyInteractiveEval {code}\r\n    Evaluate given code in the interpreter. Command is useful for quickly testing results\r\n    and for scripting purposes (for example, in context menu). Example:\r\n            :PyInteractiveEval def inc(x): return x+1\r\n            :PyInteractiveEval inc(1)\r\n            2\r\n            :PyInteractiveREPL\r\n            >>> inc(10)\r\n            11\r\n\r\n  :PyInteractiveRunBuffer\r\n      Execute current buffer in python interpreter and show result.\r\n\r\nAutocompletion is defined for PyInteractiveEval command and for input() opened by PyInteractiveREPL command and can be accessed by pressing <tab> key (default, see wildchar if you want to change this). \r\n\r\n\r\nExamples:\r\n\r\n:PyInteractiveREPL\r\n>>> def inc_10(x):\r\n...     return x+10\r\n...\r\n>>> inc_10(7)\r\n17\r\n>>>  import sys\r\n>>> sys.ex<tab> # codecompletion (see pyinteractive-autocompletion)\r\n<built-in function exit>\r\n\r\n<ESC>\r\n\r\n:PyInteractiveEval inc_10(11) +1\r\n22\r\n:PyInteractiveHistory\r\n in[1]: def inc_10(x):\r\n in[2]:     return x+10\r\n in[3]:\r\n in[4]: inc_10(7)\r\nout[1]: 17\r\n in[5]: import sys\r\n in[6]: sys.exit\r\nout[2]: <built-in function exit>\r\n in[7]: inc_10(11) +1\r\nout[3]: 22","4":"This plugin is a simple realization of read-eval-print loop for Python in Vim command window. It requires Python support (see +python) and at least version 2.6 of Python interpreter (you can check python version by running :py import sys; print(sys.version) ). \r\n\r\nFeatures:\r\n - auto-completion (tab)\r\n - auto-indent\r\n - keeps your recent results in the result history, for later user.\r\n - IPython-like magic operators (e.g. object?)\r\n - evaluate selected code\r\n - and more (see the pyinteractive documentation for details)\r\n\r\nDemonstration (ver 0.5): http:\/\/www.youtube.com\/watch?v=oy9Cv3eKy-0&feature=plcp\r\nProject home: https:\/\/github.com\/clericJ\/pyinteractive-vim\r\n\r\n\r\nCommands:\r\n\r\n :PyInteractiveREPL\r\n     Opens an interactive Python console in vim. If you want to finish working with the interpreter, \r\n      press <esc>. Interpreter states are saved between PyInteractive sessions (but not between vim\r\n     sessions), so that if you use PyInteractiveREPL, type x=1 here, close it and then reopen again, \r\n     variable x will still have value 1. \r\n\r\n  :PyInteractiveHistory [options]\r\n      Echoes session history.\r\n      Possible options:\r\n           -r          Print history without any formatting (mnemonic: raw)\r\n           -i          Print only input history (mnemonic: input)\r\n           -o          Print only output history (mnemonic: output)\r\n           -f {FILE}   Write history to file {FILE}\r\n\r\n :PyInteractiveEval {code}\r\n    Evaluate given code in the interpreter. Command is useful for quickly testing results\r\n    and for scripting purposes (for example, in context menu). Example:\r\n            :PyInteractiveEval def inc(x): return x+1\r\n            :PyInteractiveEval inc(1)\r\n            2\r\n            :PyInteractiveREPL\r\n            >>> inc(10)\r\n            11\r\n\r\n  :PyInteractiveRunBuffer\r\n      Execute current buffer in python interpreter and show result.\r\n\r\nAutocompletion is defined for PyInteractiveEval command and for input() opened by PyInteractiveREPL command and can be accessed by pressing <tab> key (default, see wildchar if you want to change this). \r\n\r\n\r\nExamples:\r\n\r\n:PyInteractiveREPL\r\n>>> def inc_10(x):\r\n...     return x+10\r\n...\r\n>>> inc_10(7)\r\n17\r\n>>>  import sys\r\n>>> sys.ex<tab> # codecompletion (see pyinteractive-autocompletion)\r\n<built-in function exit>\r\n\r\n<ESC>\r\n\r\n:PyInteractiveEval inc_10(11) +1\r\n22\r\n:PyInteractiveHistory\r\n in[1]: def inc_10(x):\r\n in[2]:     return x+10\r\n in[3]:\r\n in[4]: inc_10(7)\r\nout[1]: 17\r\n in[5]: import sys\r\n in[6]: sys.exit\r\nout[2]: <built-in function exit>\r\n in[7]: inc_10(11) +1\r\nout[3]: 22","install_details":"Unzip the most recent ZIP archive file (see below) inside your Vim profile directory (usually this is \\\"~\/.vim\\\" on UNIX and \\\"%USERPROFILE%\\\\vimfiles\\\" on Windows), restart Vim and execute the command \\\":helptags ~\/.vim\/doc\\\" (use \\\":helptags ~\\\\vimfiles\\\\doc\\\" instead on Windows).\r\nOr use vim-addon-manager (http:\/\/www.vim.org\/scripts\/script.php?script_id=2905)","5":"Unzip the most recent ZIP archive file (see below) inside your Vim profile directory (usually this is \\\"~\/.vim\\\" on UNIX and \\\"%USERPROFILE%\\\\vimfiles\\\" on Windows), restart Vim and execute the command \\\":helptags ~\/.vim\/doc\\\" (use \\\":helptags ~\\\\vimfiles\\\\doc\\\" instead on Windows).\r\nOr use vim-addon-manager (http:\/\/www.vim.org\/scripts\/script.php?script_id=2905)","first_name":"Almaz","6":"Almaz","last_name":"Karimov","7":"Karimov","releases":[{"0":"3231","vim_version":"7.0","1":"7.0","script_version":"0.7.0","2":"0.7.0","version_comment":"- Added PyInteractiveEvalRange command\r\n- Added context menu item Evaluate as Python code (for selected text)\r\n- Bugfixes","3":"- Added PyInteractiveEvalRange command\r\n- Added context menu item Evaluate as Python code (for selected text)\r\n- Bugfixes","package":"pyinteractive-vim.zip","4":"pyinteractive-vim.zip","src_id":"20520","5":"20520","creation_date":"1373822668","6":"1373822668"},{"0":"3231","vim_version":"7.2","1":"7.2","script_version":"0.6.2","2":"0.6.2","version_comment":" - Added magic command \"!\" for pretty printing (e.g. sys.modules!)\r\n - Added mapping <c-i> (interpreter call)\r\n - Code reorganization","3":" - Added magic command \"!\" for pretty printing (e.g. sys.modules!)\r\n - Added mapping <c-i> (interpreter call)\r\n - Code reorganization","package":"pyinteractive-vim.zip","4":"pyinteractive-vim.zip","src_id":"17514","5":"17514","creation_date":"1329920792","6":"1329920792"},{"0":"3231","vim_version":"7.2","1":"7.2","script_version":"0.6.1","2":"0.6.1","version_comment":" - Added magic command \"?\" (analog IPython)\r\n - Added magic command \"%<\" - append intput history to current buffer\r\n - Added magic command \"%>\" - append output history to current buffer\r\n - In interpreter namespace added vim and sys modules, and _interpreter object\r\n - Fixed error in history output\r\n - Bugfixes","3":" - Added magic command \"?\" (analog IPython)\r\n - Added magic command \"%<\" - append intput history to current buffer\r\n - Added magic command \"%>\" - append output history to current buffer\r\n - In interpreter namespace added vim and sys modules, and _interpreter object\r\n - Fixed error in history output\r\n - Bugfixes","package":"pyinteractive-vim.zip","4":"pyinteractive-vim.zip","src_id":"16725","5":"16725","creation_date":"1319349791","6":"1319349791"},{"0":"3231","vim_version":"7.2","1":"7.2","script_version":"0.5.4","2":"0.5.4","version_comment":" - Added command PyInteractiveRunBuffer\r\n - Added PyInteractive menu (Plugin.PyInteractive) and context menu item \"Evaluate\" (for selected text)\r\n - Added option pyinteractive_add_menu\r\n - Added pyinteractive_add_context_menu\r\n - Added new option \"-o\" in PyInteractiveHistory command\r\n - Bugfixes","3":" - Added command PyInteractiveRunBuffer\r\n - Added PyInteractive menu (Plugin.PyInteractive) and context menu item \"Evaluate\" (for selected text)\r\n - Added option pyinteractive_add_menu\r\n - Added pyinteractive_add_context_menu\r\n - Added new option \"-o\" in PyInteractiveHistory command\r\n - Bugfixes","package":"pyinteractive-vim.zip","4":"pyinteractive-vim.zip","src_id":"16707","5":"16707","creation_date":"1319042855","6":"1319042855"},{"0":"3231","vim_version":"7.0","1":"7.0","script_version":"0.5.3","2":"0.5.3","version_comment":"Initial upload","3":"Initial upload","package":"pyinteractive-vim.zip","4":"pyinteractive-vim.zip","src_id":"13778","5":"13778","creation_date":"1283935791","6":"1283935791"}]},"3230":{"script_id":"3230","0":"3230","script_name":"TeX-PDF","1":"TeX-PDF","script_type":"ftplugin","2":"ftplugin","summary":"Lightweight ","3":"Lightweight ","description":"Description\r\n===========\r\n\r\nThis plugin provides support for specialized lightweight \"stay-out-of-your-way\"\r\nTeX-to-PDF compilation and viewing.  In contrast to some of the other more\r\ncomprehensive TeX\/LaTeX suites, it provides nothing else but two commands, and\r\nleaves the rest of your Vim platform undisturbed, except for a few key maps to\r\ninvoke the commands.\r\n\r\nFeatures\r\n========\r\n\r\n    - Runs \"make\" if a Makefile is found, otherwise invokes Rubber (if\r\n      installed) or pdflatex (otherwise) on the current file.\r\n    - Successful builds will result in PDF being opened\/refreshed in the\r\n      default external viewer.\r\n    - Unsuccessful builds will result in the QuickFix buffer being opened and\r\n      to list the errors, with line numbers, description etc.\r\n\r\nUsage\r\n=====\r\nOnce the plugin is installed (see below), when you have a TeX or LaTeX document\r\nopen in the buffer, type '\\r' or <Shift-F9> to compile the document and open\r\n(or refresh) the resulting PDF in your system's default PDF viewer. To just\r\ncompile the document to PDF without opening it, type '\\m' or <F9>.  If there\r\nare any compile errors, a window will open and list all the problematic lines.\r\nAs usual, you can navigate forward and backward through this list using the\r\n':cnext' and ':cprev' commands, and you will automatically be taken to the\r\ncorresponding line in the source document.\r\n\r\nWorking with Rubber\r\n===================\r\n\r\nThis plugin will work quite happily with the stock TeX\/LaTeX tools found on\r\nmost systems. As described above, for example, this plugin will run \"make\" if a\r\nMakefile is found in the current working directory (by-passing Rubber, even if\r\ninstalled), and fall back to the standard \"pdflatex\" if Rubber is not\r\ninstalled.\r\n\r\nHowever, installation of \"Rubber\" (https:\/\/launchpad.net\/rubber) in conjunction\r\nwith this plugin makes Vim a *very* powerful, yet highly ergonomic and\r\nnon-intrusive, LaTeX IDE, making Makefiles unneccessary for many document\r\nprojects. Rubber takes care of the multiple TeX compile passes required to get\r\nthe the bibliographies, references, cross-references, etc. correctly built,\r\nwhile this plug-in takes care of opening\/refreshing the PDF view on successful\r\nbuilds, as well as providing for a *clean* view of the errors on an\r\nunsuccessful build.\r\n\r\nOperation\r\n=========\r\n\r\nThis plugin provides two commands: \"BuildAndViewTexPdf\" and \"BuildTexPdf\".\r\n\r\n\"BuildAndViewTexPdf\" will build the PDF from the TeX source, and, if\r\nsuccessful, will open the resulting PDF for viewing in an external viewer (or\r\nrefresh the PDF if already opened).\r\n\r\n\"BuildTexPdf\" will build the PDF from the TeX source without opening\/refreshing\r\nthe PDF.\r\n\r\nThe build logic is:\r\n\r\n    (1) If a Makefile is found in the current directory, then \"make\" will be\r\n        invoked.\r\n    (2) If there is no Makefile in the current directory, but \"Rubber\"\r\n        (https:\/\/launchpad.net\/rubber) is installed and available, then this will\r\n        invoked on the current buffer file.\r\n    (3) If Rubber is not installed, then \"pdflatex\" will be invoked on the\r\n        current buffer file.\r\n\r\nIf the build is unsuccessful, the QuickFix buffer is populated with the\r\n(parsed, cleaned, and filtered) error messages and automatically opened,\r\nshowing, for each error, the line number and description of the error. You can\r\nthen used \":cnext\", \":cprev\", etc. to visit each of the error lines.\r\n\r\nKey Mapping\r\n===========\r\n\r\nBy default, '<Leader>r' (mnemonic: 'run') and '<S-F9>' are mapped to\r\n\"BuildAndViewTexPdf\", while '<Leader>m' (mnemonic: 'make') and '<F9>' are\r\nmapped to \"BuildTexPdf\"\r\n\r\nIf you prefer not to have any of the above keys mapped, then include the\r\nfollowing in your '~\/.vimrc':\r\n\r\n    let g:tex_pdf_map_keys = 0\r\n\r\nIf you prefer not to have the '\\r' and '\\m' leader keys mapped but keep the\r\nfunction key mapping, you can include the following in your '~\/.vimrc':\r\n\r\n    let g:tex_pdf_map_leader_keys = 0\r\n\r\nAlternatively, you can keep the leader keys mapped but by-pass the function key\r\nmapping by including the following in your '~\/.vimrc':\r\n\r\n    let g:tex_pdf_map_func_keys = 0\r\n\r\nYou can, of course, map any keys that you want to the commands. For example,\r\nby including the following in your '~\/.vimrc', you will map Command-V to the\r\n\"compile and view\" command and Command-T to the \"just compile\" command in\r\nboth normal and insert modes:\r\n\r\n    noremap <silent> <D-V> <Esc>:BuildAndViewTexPdf<CR>\r\n    inoremap <silent> <D-V> <Esc>:BuildAndViewTexPdf<CR>\r\n    noremap <silent> <D-T> <Esc>:BuildTexPdf<CR>\r\n    inoremap <silent> <D-T> <Esc>:BuildTexPdf<CR>\r\n","4":"Description\r\n===========\r\n\r\nThis plugin provides support for specialized lightweight \"stay-out-of-your-way\"\r\nTeX-to-PDF compilation and viewing.  In contrast to some of the other more\r\ncomprehensive TeX\/LaTeX suites, it provides nothing else but two commands, and\r\nleaves the rest of your Vim platform undisturbed, except for a few key maps to\r\ninvoke the commands.\r\n\r\nFeatures\r\n========\r\n\r\n    - Runs \"make\" if a Makefile is found, otherwise invokes Rubber (if\r\n      installed) or pdflatex (otherwise) on the current file.\r\n    - Successful builds will result in PDF being opened\/refreshed in the\r\n      default external viewer.\r\n    - Unsuccessful builds will result in the QuickFix buffer being opened and\r\n      to list the errors, with line numbers, description etc.\r\n\r\nUsage\r\n=====\r\nOnce the plugin is installed (see below), when you have a TeX or LaTeX document\r\nopen in the buffer, type '\\r' or <Shift-F9> to compile the document and open\r\n(or refresh) the resulting PDF in your system's default PDF viewer. To just\r\ncompile the document to PDF without opening it, type '\\m' or <F9>.  If there\r\nare any compile errors, a window will open and list all the problematic lines.\r\nAs usual, you can navigate forward and backward through this list using the\r\n':cnext' and ':cprev' commands, and you will automatically be taken to the\r\ncorresponding line in the source document.\r\n\r\nWorking with Rubber\r\n===================\r\n\r\nThis plugin will work quite happily with the stock TeX\/LaTeX tools found on\r\nmost systems. As described above, for example, this plugin will run \"make\" if a\r\nMakefile is found in the current working directory (by-passing Rubber, even if\r\ninstalled), and fall back to the standard \"pdflatex\" if Rubber is not\r\ninstalled.\r\n\r\nHowever, installation of \"Rubber\" (https:\/\/launchpad.net\/rubber) in conjunction\r\nwith this plugin makes Vim a *very* powerful, yet highly ergonomic and\r\nnon-intrusive, LaTeX IDE, making Makefiles unneccessary for many document\r\nprojects. Rubber takes care of the multiple TeX compile passes required to get\r\nthe the bibliographies, references, cross-references, etc. correctly built,\r\nwhile this plug-in takes care of opening\/refreshing the PDF view on successful\r\nbuilds, as well as providing for a *clean* view of the errors on an\r\nunsuccessful build.\r\n\r\nOperation\r\n=========\r\n\r\nThis plugin provides two commands: \"BuildAndViewTexPdf\" and \"BuildTexPdf\".\r\n\r\n\"BuildAndViewTexPdf\" will build the PDF from the TeX source, and, if\r\nsuccessful, will open the resulting PDF for viewing in an external viewer (or\r\nrefresh the PDF if already opened).\r\n\r\n\"BuildTexPdf\" will build the PDF from the TeX source without opening\/refreshing\r\nthe PDF.\r\n\r\nThe build logic is:\r\n\r\n    (1) If a Makefile is found in the current directory, then \"make\" will be\r\n        invoked.\r\n    (2) If there is no Makefile in the current directory, but \"Rubber\"\r\n        (https:\/\/launchpad.net\/rubber) is installed and available, then this will\r\n        invoked on the current buffer file.\r\n    (3) If Rubber is not installed, then \"pdflatex\" will be invoked on the\r\n        current buffer file.\r\n\r\nIf the build is unsuccessful, the QuickFix buffer is populated with the\r\n(parsed, cleaned, and filtered) error messages and automatically opened,\r\nshowing, for each error, the line number and description of the error. You can\r\nthen used \":cnext\", \":cprev\", etc. to visit each of the error lines.\r\n\r\nKey Mapping\r\n===========\r\n\r\nBy default, '<Leader>r' (mnemonic: 'run') and '<S-F9>' are mapped to\r\n\"BuildAndViewTexPdf\", while '<Leader>m' (mnemonic: 'make') and '<F9>' are\r\nmapped to \"BuildTexPdf\"\r\n\r\nIf you prefer not to have any of the above keys mapped, then include the\r\nfollowing in your '~\/.vimrc':\r\n\r\n    let g:tex_pdf_map_keys = 0\r\n\r\nIf you prefer not to have the '\\r' and '\\m' leader keys mapped but keep the\r\nfunction key mapping, you can include the following in your '~\/.vimrc':\r\n\r\n    let g:tex_pdf_map_leader_keys = 0\r\n\r\nAlternatively, you can keep the leader keys mapped but by-pass the function key\r\nmapping by including the following in your '~\/.vimrc':\r\n\r\n    let g:tex_pdf_map_func_keys = 0\r\n\r\nYou can, of course, map any keys that you want to the commands. For example,\r\nby including the following in your '~\/.vimrc', you will map Command-V to the\r\n\"compile and view\" command and Command-T to the \"just compile\" command in\r\nboth normal and insert modes:\r\n\r\n    noremap <silent> <D-V> <Esc>:BuildAndViewTexPdf<CR>\r\n    inoremap <silent> <D-V> <Esc>:BuildAndViewTexPdf<CR>\r\n    noremap <silent> <D-T> <Esc>:BuildTexPdf<CR>\r\n    inoremap <silent> <D-T> <Esc>:BuildTexPdf<CR>\r\n","install_details":"Unarchive the file while in your Vim home directory: this will result in  the bundled file, \"tex_pdf.vim\" being copied to \"~\/.vim\/ftplugin\/tex\". Alternatively, you can just unpack and copy the file to this location yourself manually.","5":"Unarchive the file while in your Vim home directory: this will result in  the bundled file, \"tex_pdf.vim\" being copied to \"~\/.vim\/ftplugin\/tex\". Alternatively, you can just unpack and copy the file to this location yourself manually.","first_name":"Jeet","6":"Jeet","last_name":"Sukumaran","7":"Sukumaran","releases":[{"0":"3230","vim_version":"7.0","1":"7.0","script_version":"1.4.2","2":"1.4.2","version_comment":"- Add `-shell-escape` to command invocation","3":"- Add `-shell-escape` to command invocation","package":"tex-pdf.tar.gz","4":"tex-pdf.tar.gz","src_id":"21901","5":"21901","creation_date":"1400363436","6":"1400363436"},{"0":"3230","vim_version":"7.0","1":"7.0","script_version":"1.41","2":"1.41","version_comment":"Restore header guard","3":"Restore header guard","package":"tex_pdf.tar.gz","4":"tex_pdf.tar.gz","src_id":"18261","5":"18261","creation_date":"1342285902","6":"1342285902"},{"0":"3230","vim_version":"7.0","1":"7.0","script_version":"1.4","2":"1.4","version_comment":"- Jump to first error line on previous window on error ","3":"- Jump to first error line on previous window on error ","package":"tex_pdf.tar.gz","4":"tex_pdf.tar.gz","src_id":"18260","5":"18260","creation_date":"1342285795","6":"1342285795"},{"0":"3230","vim_version":"7.0","1":"7.0","script_version":"1.3A","2":"1.3A","version_comment":"Correct compression protocol used (previous upload was actually bzip2).","3":"Correct compression protocol used (previous upload was actually bzip2).","package":"tex_pdf.tar.gz","4":"tex_pdf.tar.gz","src_id":"13845","5":"13845","creation_date":"1284705597","6":"1284705597"},{"0":"3230","vim_version":"7.0","1":"7.0","script_version":"1.3","2":"1.3","version_comment":"Fixed failure to redraw in console Vim when running external make\/rubber.","3":"Fixed failure to redraw in console Vim when running external make\/rubber.","package":"tex-pdf.tar.gz","4":"tex-pdf.tar.gz","src_id":"13793","5":"13793","creation_date":"1284013967","6":"1284013967"},{"0":"3230","vim_version":"7.0","1":"7.0","script_version":"1.2","2":"1.2","version_comment":"On successful compiles, cursor is restored to original position. On compile error, smarter jumping to location of first error.","3":"On successful compiles, cursor is restored to original position. On compile error, smarter jumping to location of first error.","package":"tex-pdf.tar.gz","4":"tex-pdf.tar.gz","src_id":"13785","5":"13785","creation_date":"1283988342","6":"1283988342"},{"0":"3230","vim_version":"7.0","1":"7.0","script_version":"1.1","2":"1.1","version_comment":"Better handling of compile errors, automatically jumping to first error line.","3":"Better handling of compile errors, automatically jumping to first error line.","package":"tex-pdf.tar.gz","4":"tex-pdf.tar.gz","src_id":"13782","5":"13782","creation_date":"1283960868","6":"1283960868"},{"0":"3230","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Re-upload.","3":"Re-upload.","package":"tex-pdf.tar.gz","4":"tex-pdf.tar.gz","src_id":"13775","5":"13775","creation_date":"1283921318","6":"1283921318"}]},"3229":{"script_id":"3229","0":"3229","script_name":"stem-search","1":"stem-search","script_type":"utility","2":"utility","summary":"StmSrch is a reverse-stem searching script","3":"StmSrch is a reverse-stem searching script","description":"Source and associated data files for testing hosted at:\r\nhttp:\/\/github.com\/msbmsb\/stem-search.vim\r\n\r\nStmSrch is a reverse-stem searching script. It implements the Porter stemming algorithm, by Martin Porter. It also handles irregular verbs and noun pluralizations.\r\n\r\nThis script can be useful for searching or scanning through corpus files.\r\n\r\nEach word input to the :StmSrch command will be stemmed and then formulated in such a way as to match possible conjugations or pluralizations. Without any word given for input, it will attempt to stem the current word under the cursor. The matching is done using word boundaries so not just any substring will match.\r\n\r\nFor example: \r\n- :StmSrch search \r\nwill match any of: \r\n- search, searching, searches, searchers, searched, ...\r\nand a string of words will work as well, matching in order: \r\n- :StmSrch thieves are running from bunnies \r\nwill match strings of words like: \r\n- thief was ran from bunny \r\n- thieves be run from bunnies\r\n\r\nSearch hits are highlighted, and the highlight color can be modified by\r\nediting the color in the s:StmSrchInit() function. The matches will stay \r\nhighlighted even if you search again using the normal \\'\/\\' key. This is\r\nuseful for cases where you are browsing through a large corpus file, for \r\nexample and want to see the relative location of matches. \r\n\r\nUse :ClrStmSrch to clear the highlighting for the StmSrch group.\r\n\r\nFor stemmed words, the search is greedy and may over match. This was useful \r\nfor my purposes. If more exact word endings are required, this can be added.\r\n\r\n----\r\nTo use this vim script, add it to ~\/.vim\/plugin\/\r\n\r\nSee doc\/stem-search.vim.txt for more information about the script.\r\n\r\n----\r\n","4":"Source and associated data files for testing hosted at:\r\nhttp:\/\/github.com\/msbmsb\/stem-search.vim\r\n\r\nStmSrch is a reverse-stem searching script. It implements the Porter stemming algorithm, by Martin Porter. It also handles irregular verbs and noun pluralizations.\r\n\r\nThis script can be useful for searching or scanning through corpus files.\r\n\r\nEach word input to the :StmSrch command will be stemmed and then formulated in such a way as to match possible conjugations or pluralizations. Without any word given for input, it will attempt to stem the current word under the cursor. The matching is done using word boundaries so not just any substring will match.\r\n\r\nFor example: \r\n- :StmSrch search \r\nwill match any of: \r\n- search, searching, searches, searchers, searched, ...\r\nand a string of words will work as well, matching in order: \r\n- :StmSrch thieves are running from bunnies \r\nwill match strings of words like: \r\n- thief was ran from bunny \r\n- thieves be run from bunnies\r\n\r\nSearch hits are highlighted, and the highlight color can be modified by\r\nediting the color in the s:StmSrchInit() function. The matches will stay \r\nhighlighted even if you search again using the normal \\'\/\\' key. This is\r\nuseful for cases where you are browsing through a large corpus file, for \r\nexample and want to see the relative location of matches. \r\n\r\nUse :ClrStmSrch to clear the highlighting for the StmSrch group.\r\n\r\nFor stemmed words, the search is greedy and may over match. This was useful \r\nfor my purposes. If more exact word endings are required, this can be added.\r\n\r\n----\r\nTo use this vim script, add it to ~\/.vim\/plugin\/\r\n\r\nSee doc\/stem-search.vim.txt for more information about the script.\r\n\r\n----\r\n","install_details":"To use this vim script, add it to ~\/.vim\/plugin\/","5":"To use this vim script, add it to ~\/.vim\/plugin\/","first_name":"Mitchell","6":"Mitchell","last_name":"Bowden","7":"Bowden","releases":[{"0":"3229","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"stem-search.vim","4":"stem-search.vim","src_id":"13758","5":"13758","creation_date":"1283574769","6":"1283574769"}]},"3228":{"script_id":"3228","0":"3228","script_name":"porter-stem","1":"porter-stem","script_type":"utility","2":"utility","summary":"PorterStem implements the Porter stemming algorithm for use as script utility ","3":"PorterStem implements the Porter stemming algorithm for use as script utility ","description":"Source and associated data files for testing hosted at:\r\nhttp:\/\/github.com\/msbmsb\/porter-stem.vim\r\n\r\nPorterStem is a vim script that implements the Porter stemming algorithm, by Martin Porter, details of which can be found at: http:\/\/tartarus.org\/~martin\/PorterStemmer\/\r\n\r\nThe main function outputs the single string of the stem, and the script only\r\nechoes the output to the screen. This script, while it can be used as-is\r\nif you want to know what the stem for a word is, is mostly a container for \r\nthe algorithm implementation in vim script.\r\n\r\nPorterStem command syntax:\r\n-  :PorterStem (<word>)*\r\n\r\nEach word input to the :PorterStem command will be stemmed and processed by\r\nthe ProcessStem function, that by default simply echoes to the screen.\r\nWithout any word given for input, it will attempt to stem the current word \r\nunder the cursor via expand('<cword>').\r\n\r\nFor example:\r\n-  :PorterStem searching\r\nwill output:\r\n-  search\r\nand a string of words will work as well, matching in order:\r\n-  :PorterStem thieves are running from the bunny\r\nwill output:\r\n-  thiev are run from bunni\r\n\r\nRunning :PorterTest <test-file> <expected-results-file> will run each \r\nword in <test-file> and match the stem result to the same line in the \r\n<expected-results-file>, showing if any are incorrect stem matches.\r\nProvided in the github repository are two files voc.txt and output.txt \r\nfrom Martin Porter's site providing a set of test words.\r\n\r\n----\r\nTo use this vim script, add it to ~\/.vim\/plugin\/\r\n\r\nSee doc\/porter-stem.vim.txt for more information about the script.\r\nSee http:\/\/github.com\/msbmsb\/stem-search.vim for a script that uses this method for reverse-stem searching in a file.\r\n\r\n----","4":"Source and associated data files for testing hosted at:\r\nhttp:\/\/github.com\/msbmsb\/porter-stem.vim\r\n\r\nPorterStem is a vim script that implements the Porter stemming algorithm, by Martin Porter, details of which can be found at: http:\/\/tartarus.org\/~martin\/PorterStemmer\/\r\n\r\nThe main function outputs the single string of the stem, and the script only\r\nechoes the output to the screen. This script, while it can be used as-is\r\nif you want to know what the stem for a word is, is mostly a container for \r\nthe algorithm implementation in vim script.\r\n\r\nPorterStem command syntax:\r\n-  :PorterStem (<word>)*\r\n\r\nEach word input to the :PorterStem command will be stemmed and processed by\r\nthe ProcessStem function, that by default simply echoes to the screen.\r\nWithout any word given for input, it will attempt to stem the current word \r\nunder the cursor via expand('<cword>').\r\n\r\nFor example:\r\n-  :PorterStem searching\r\nwill output:\r\n-  search\r\nand a string of words will work as well, matching in order:\r\n-  :PorterStem thieves are running from the bunny\r\nwill output:\r\n-  thiev are run from bunni\r\n\r\nRunning :PorterTest <test-file> <expected-results-file> will run each \r\nword in <test-file> and match the stem result to the same line in the \r\n<expected-results-file>, showing if any are incorrect stem matches.\r\nProvided in the github repository are two files voc.txt and output.txt \r\nfrom Martin Porter's site providing a set of test words.\r\n\r\n----\r\nTo use this vim script, add it to ~\/.vim\/plugin\/\r\n\r\nSee doc\/porter-stem.vim.txt for more information about the script.\r\nSee http:\/\/github.com\/msbmsb\/stem-search.vim for a script that uses this method for reverse-stem searching in a file.\r\n\r\n----","install_details":"To use this vim script, add it to ~\/.vim\/plugin\/","5":"To use this vim script, add it to ~\/.vim\/plugin\/","first_name":"Mitchell","6":"Mitchell","last_name":"Bowden","7":"Bowden","releases":[{"0":"3228","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"porter-stem.vim","4":"porter-stem.vim","src_id":"13757","5":"13757","creation_date":"1283574733","6":"1283574733"}]},"3227":{"script_id":"3227","0":"3227","script_name":"Simple Javascript Indenter","1":"Simple Javascript Indenter","script_type":"indent","2":"indent","summary":"A simple javascript indent script, support OOP, jquery","3":"A simple javascript indent script, support OOP, jquery","description":"A simple indent plugin for javascript, \r\n\r\nRepository: http:\/\/github.com\/jiangmiao\/simple-javascript-indenter\r\nScreenshot: http:\/\/www.jiangmiao.org\/blog\/wp-content\/uploads\/2010\/09\/vim_simple_javascript_indenter_v1.4.1.png (with Brief Mode on)\r\n\r\n==Options==\r\ng:SimpleJsIndenter_BriefMode (default 0)\r\n  set 1 to turn brief mode on.\r\n\r\ng:SimpleJsIndenter_CaseIndentLevel (default 0)\r\n  the case indent level in switch. the value could be -1, -0.5, 0.\r\n\r\n===About Brief Mode===\r\nAdd 'let g:SimpleJsIndenter_BriefMode = 1' to ~\/.vimrc to use brief mode.\r\n\r\nIn Brief Mode script will not indent more than one shiftwidth each line.\r\neg:\r\nFor a lot of people prefer set shiftwidth to 4, so in normal mode, it will indent looks like\r\neach(function() {\r\n........something(); \/\/ indent 2 shiftwidth\r\n});\r\n(((\r\n............something(); \/\/ indent 3 shiftwidth\r\n)));\r\n\r\nIn brief mode it will indent as\r\neach(function() {\r\n....something(); \/\/ indent 1 shiftwidth\r\n});\r\n(((\r\n....something();\r\n)))\r\n\r\n===ATTENTION===\r\nBe sure to always close the brackets with the same level as open, or the after code will not indent correctly.\r\neg:\r\nfunction() {\r\n....each(function() {\r\n....} \/\/ should use }); instead of }\r\n);    \/\/ already indented..\r\nsomething();\r\n}\r\n\r\n\r\n== Indent Effects  ==\r\n\/*\r\n * Comment Test \r\n * function() {\r\n *\/\r\n{\r\n  \/* a [{( *\/\r\n  \/\/ b [{(\r\n  comment('\/* com', a \/* [{( *\/); \/* c *\/ \/\/ d\r\n  ok();\r\n  \/\/ Assign Test\r\n  var a, \/* { *\/\r\n      b, \/\/ [\r\n      c = '{'\r\n  var a = \"Hello\" +\r\n          \"World\"\r\n  d = function() {\r\n    aoeu\r\n  }\r\n  var k = function() {\r\n    var k=3,\r\n        m=4\r\n  }\r\n\r\n  var rurl = \/{[('\"\/,\r\n      r20 = \/%20\/g,\r\n\r\n  a = 1,\r\n  b = 2\r\n  a = 1 +\r\n      2 *\r\n      3\r\n}\r\n\r\n\/\/ Function nested\r\n;(function($) {\r\n    $(document).ready(function() {\r\n        $('#foo').click(function() {\r\n            $.post(url, {\r\n                a: 1, \r\n                b: 2,\r\n              }, function() {\r\n                ok(); \r\n              }\r\n            );\r\n        });\r\n    });\r\n})(jQuery);\r\n\r\n\/\/ Array Object Test\r\nstring_test(\"('\",'(\"',\"[\",'{',\"\\\"{\",\"\\\\'{\"); \r\n{\r\n  array_object_test: [\r\n    1,\r\n    2,\r\n    {\r\n      a: [3,4],\r\n      b: [\r\n        3,\r\n        4\r\n      ],\r\n      c: string_test(\"('\",'(\"',\"[\",'{',\"\\\"{\",\"\\\\'{\"),\r\n      function_test: function() {\r\n        return 0;\r\n      },\r\n      one_line_function_test: function() { return [1] }\r\n    }\r\n  ]\r\n}\r\n\r\n\/\/ One Line Test\r\n{\r\n  if( a == b &&\r\n    c == d ||\r\n    e == f) \r\n  {\r\n    ok();\r\n  }\r\n  if(a) {\r\n    b;\r\n  } else {\r\n    e;\r\n  }\r\n  if(a)\r\n    b;\r\n  else if(k) {\r\n    aeou\r\n  } else\r\n    c;\r\n  while(true)\r\n    foo += 1;\r\n  try\r\n    a;\r\n  catch\r\n    b;\r\n  finally\r\n    c;\r\n  ok();\r\n}\r\n","4":"A simple indent plugin for javascript, \r\n\r\nRepository: http:\/\/github.com\/jiangmiao\/simple-javascript-indenter\r\nScreenshot: http:\/\/www.jiangmiao.org\/blog\/wp-content\/uploads\/2010\/09\/vim_simple_javascript_indenter_v1.4.1.png (with Brief Mode on)\r\n\r\n==Options==\r\ng:SimpleJsIndenter_BriefMode (default 0)\r\n  set 1 to turn brief mode on.\r\n\r\ng:SimpleJsIndenter_CaseIndentLevel (default 0)\r\n  the case indent level in switch. the value could be -1, -0.5, 0.\r\n\r\n===About Brief Mode===\r\nAdd 'let g:SimpleJsIndenter_BriefMode = 1' to ~\/.vimrc to use brief mode.\r\n\r\nIn Brief Mode script will not indent more than one shiftwidth each line.\r\neg:\r\nFor a lot of people prefer set shiftwidth to 4, so in normal mode, it will indent looks like\r\neach(function() {\r\n........something(); \/\/ indent 2 shiftwidth\r\n});\r\n(((\r\n............something(); \/\/ indent 3 shiftwidth\r\n)));\r\n\r\nIn brief mode it will indent as\r\neach(function() {\r\n....something(); \/\/ indent 1 shiftwidth\r\n});\r\n(((\r\n....something();\r\n)))\r\n\r\n===ATTENTION===\r\nBe sure to always close the brackets with the same level as open, or the after code will not indent correctly.\r\neg:\r\nfunction() {\r\n....each(function() {\r\n....} \/\/ should use }); instead of }\r\n);    \/\/ already indented..\r\nsomething();\r\n}\r\n\r\n\r\n== Indent Effects  ==\r\n\/*\r\n * Comment Test \r\n * function() {\r\n *\/\r\n{\r\n  \/* a [{( *\/\r\n  \/\/ b [{(\r\n  comment('\/* com', a \/* [{( *\/); \/* c *\/ \/\/ d\r\n  ok();\r\n  \/\/ Assign Test\r\n  var a, \/* { *\/\r\n      b, \/\/ [\r\n      c = '{'\r\n  var a = \"Hello\" +\r\n          \"World\"\r\n  d = function() {\r\n    aoeu\r\n  }\r\n  var k = function() {\r\n    var k=3,\r\n        m=4\r\n  }\r\n\r\n  var rurl = \/{[('\"\/,\r\n      r20 = \/%20\/g,\r\n\r\n  a = 1,\r\n  b = 2\r\n  a = 1 +\r\n      2 *\r\n      3\r\n}\r\n\r\n\/\/ Function nested\r\n;(function($) {\r\n    $(document).ready(function() {\r\n        $('#foo').click(function() {\r\n            $.post(url, {\r\n                a: 1, \r\n                b: 2,\r\n              }, function() {\r\n                ok(); \r\n              }\r\n            );\r\n        });\r\n    });\r\n})(jQuery);\r\n\r\n\/\/ Array Object Test\r\nstring_test(\"('\",'(\"',\"[\",'{',\"\\\"{\",\"\\\\'{\"); \r\n{\r\n  array_object_test: [\r\n    1,\r\n    2,\r\n    {\r\n      a: [3,4],\r\n      b: [\r\n        3,\r\n        4\r\n      ],\r\n      c: string_test(\"('\",'(\"',\"[\",'{',\"\\\"{\",\"\\\\'{\"),\r\n      function_test: function() {\r\n        return 0;\r\n      },\r\n      one_line_function_test: function() { return [1] }\r\n    }\r\n  ]\r\n}\r\n\r\n\/\/ One Line Test\r\n{\r\n  if( a == b &&\r\n    c == d ||\r\n    e == f) \r\n  {\r\n    ok();\r\n  }\r\n  if(a) {\r\n    b;\r\n  } else {\r\n    e;\r\n  }\r\n  if(a)\r\n    b;\r\n  else if(k) {\r\n    aeou\r\n  } else\r\n    c;\r\n  while(true)\r\n    foo += 1;\r\n  try\r\n    a;\r\n  catch\r\n    b;\r\n  finally\r\n    c;\r\n  ok();\r\n}\r\n","install_details":"copy indent\/javascript.vim to ~\/.vim\/indent\r\nOptional:\r\nAdd 'let g:SimpleJsIndenter_BriefMode = 1' to ~\/.vimrc to use brief mode .","5":"copy indent\/javascript.vim to ~\/.vim\/indent\r\nOptional:\r\nAdd 'let g:SimpleJsIndenter_BriefMode = 1' to ~\/.vimrc to use brief mode .","first_name":"Miao","6":"Miao","last_name":"Jiang","7":"Jiang","releases":[{"0":"3227","vim_version":"7.0","1":"7.0","script_version":"1.4.6","2":"1.4.6","version_comment":"        New: return indent supported\r\n\r\n                return a +\r\n                       b +\r\n                       c;\r\n\r\n        Fix: failed indent for\r\n\r\n                var a,\r\n                    \/\/ ca\r\n                    b,\r\n                    \/* cb *\/\r\n                    c;\r\n","3":"        New: return indent supported\r\n\r\n                return a +\r\n                       b +\r\n                       c;\r\n\r\n        Fix: failed indent for\r\n\r\n                var a,\r\n                    \/\/ ca\r\n                    b,\r\n                    \/* cb *\/\r\n                    c;\r\n","package":"simple-javascript-indenter-v1.4.6.tar.gz","4":"simple-javascript-indenter-v1.4.6.tar.gz","src_id":"16695","5":"16695","creation_date":"1318959594","6":"1318959594"},{"0":"3227","vim_version":"7.0","1":"7.0","script_version":"1.4.5","2":"1.4.5","version_comment":"  Fix: float indent level is invalid in vim 7.3\r\n\r\n  Fix: failed indent for\r\n    var a = \/reg\/,\r\n        c = 'bar'\r\n\r\n  Optimize code\r\n","3":"  Fix: float indent level is invalid in vim 7.3\r\n\r\n  Fix: failed indent for\r\n    var a = \/reg\/,\r\n        c = 'bar'\r\n\r\n  Optimize code\r\n","package":"simple-javascript-indenter-v1.4.5.tar.gz","4":"simple-javascript-indenter-v1.4.5.tar.gz","src_id":"16666","5":"16666","creation_date":"1318532803","6":"1318532803"},{"0":"3227","vim_version":"7.0","1":"7.0","script_version":"1.4.4","2":"1.4.4","version_comment":"\tFix: failed indent for\r\n\t\t(a \/ b); \/\/ c (\r\n\t\r\n\tFix: failed indent for\r\n\t\t'' + \"'\" + \/\/ ' (\r\n\r\n\tFix: failed indent in Brief Mode for\r\n\t\tfoo (a(b,\r\n\t\t\tc)) {\r\n\t\t\taoeu\r\n\t\t}\r\n","3":"\tFix: failed indent for\r\n\t\t(a \/ b); \/\/ c (\r\n\t\r\n\tFix: failed indent for\r\n\t\t'' + \"'\" + \/\/ ' (\r\n\r\n\tFix: failed indent in Brief Mode for\r\n\t\tfoo (a(b,\r\n\t\t\tc)) {\r\n\t\t\taoeu\r\n\t\t}\r\n","package":"simple-javascript-indenter-v1.4.4.tar.gz","4":"simple-javascript-indenter-v1.4.4.tar.gz","src_id":"16664","5":"16664","creation_date":"1318513002","6":"1318513002"},{"0":"3227","vim_version":"7.0","1":"7.0","script_version":"1.4.3","2":"1.4.3","version_comment":"\tFix: failed indent in brief mode, and optimize in normal mode for code\r\n\t{\r\n\t\tconsole.info((function() {\r\n\t\t}).something);\r\n\t\tnext(); \r\n\t}\r\n","3":"\tFix: failed indent in brief mode, and optimize in normal mode for code\r\n\t{\r\n\t\tconsole.info((function() {\r\n\t\t}).something);\r\n\t\tnext(); \r\n\t}\r\n","package":"simple-javascript-indenter-v1.4.3.tar.gz","4":"simple-javascript-indenter-v1.4.3.tar.gz","src_id":"16132","5":"16132","creation_date":"1311491087","6":"1311491087"},{"0":"3227","vim_version":"7.0","1":"7.0","script_version":"1.4.2","2":"1.4.2","version_comment":"add option g:SimpleJsIndenter_CaseIndentLevel ","3":"add option g:SimpleJsIndenter_CaseIndentLevel ","package":"simple-javascript-indenter-v1.4.2.tar.gz","4":"simple-javascript-indenter-v1.4.2.tar.gz","src_id":"15661","5":"15661","creation_date":"1305641121","6":"1305641121"},{"0":"3227","vim_version":"7.0","1":"7.0","script_version":"1.4.1","2":"1.4.1","version_comment":"Update: Indent current line when input } ) ]\r\nUpdate: Change comment indentation style\r\n","3":"Update: Indent current line when input } ) ]\r\nUpdate: Change comment indentation style\r\n","package":"simple-javascript-indenter-v1.4.1.tar.gz","4":"simple-javascript-indenter-v1.4.1.tar.gz","src_id":"15510","5":"15510","creation_date":"1303540824","6":"1303540824"},{"0":"3227","vim_version":"7.0","1":"7.0","script_version":"1.4.0","2":"1.4.0","version_comment":"Support switch...case .","3":"Support switch...case .","package":"simple-javascript-indenter-v1.4.0.tar.gz","4":"simple-javascript-indenter-v1.4.0.tar.gz","src_id":"15294","5":"15294","creation_date":"1301131219","6":"1301131219"},{"0":"3227","vim_version":"7.0","1":"7.0","script_version":"1.3.4","2":"1.3.4","version_comment":"\tFix: failed indent for \r\n\t\tfunction escapeattr(b) {\r\n\t\t\treturn b ? b.replace(\/([\\.#\\[\\]])\/ig, \"\\\\$1\") : \"\"\r\n\t\t}\r\n\r\n\thttps:\/\/github.com\/jiangmiao\/simple-javascript-indenter\/issues#issue\/1 (Thanks to whentp)\r\n","3":"\tFix: failed indent for \r\n\t\tfunction escapeattr(b) {\r\n\t\t\treturn b ? b.replace(\/([\\.#\\[\\]])\/ig, \"\\\\$1\") : \"\"\r\n\t\t}\r\n\r\n\thttps:\/\/github.com\/jiangmiao\/simple-javascript-indenter\/issues#issue\/1 (Thanks to whentp)\r\n","package":"simple-javascript-indenter-v1.3.4.tar.gz","4":"simple-javascript-indenter-v1.3.4.tar.gz","src_id":"15270","5":"15270","creation_date":"1300727428","6":"1300727428"},{"0":"3227","vim_version":"7.0","1":"7.0","script_version":"1.3.3","2":"1.3.3","version_comment":"Fix Failed Indent for\r\n\t\ttest(\/*a'*\/b,'c') {\r\n\t\t\tfoo();\r\n\t\t}\r\n","3":"Fix Failed Indent for\r\n\t\ttest(\/*a'*\/b,'c') {\r\n\t\t\tfoo();\r\n\t\t}\r\n","package":"simple-javascript-indenter-v1.3.3.tar.gz","4":"simple-javascript-indenter-v1.3.3.tar.gz","src_id":"14705","5":"14705","creation_date":"1294468736","6":"1294468736"},{"0":"3227","vim_version":"7.0","1":"7.0","script_version":"1.3.2","2":"1.3.2","version_comment":"\tFIX: failed indent for\r\n\t\tfunction a() {\r\n\t\t\t$('\"', {'b'}, function() {\r\n\t\t\t});\r\n\t\t}","3":"\tFIX: failed indent for\r\n\t\tfunction a() {\r\n\t\t\t$('\"', {'b'}, function() {\r\n\t\t\t});\r\n\t\t}","package":"simple-javascript-indenter-v1.3.2.tar.gz","4":"simple-javascript-indenter-v1.3.2.tar.gz","src_id":"14700","5":"14700","creation_date":"1294414938","6":"1294414938"},{"0":"3227","vim_version":"7.0","1":"7.0","script_version":"1.3.1","2":"1.3.1","version_comment":"Fix 3 format indent failed. ","3":"Fix 3 format indent failed. ","package":"simple-javascript-indenter-v1.3.1.tar.gz","4":"simple-javascript-indenter-v1.3.1.tar.gz","src_id":"14341","5":"14341","creation_date":"1290364856","6":"1290364856"},{"0":"3227","vim_version":"7.0","1":"7.0","script_version":"1.2.1","2":"1.2.1","version_comment":"Support: indent for if, else, else if, while, try, catch, finally without brackets.\r\n","3":"Support: indent for if, else, else if, while, try, catch, finally without brackets.\r\n","package":"simple-javascript-indenter-v1.2.1.tar.gz","4":"simple-javascript-indenter-v1.2.1.tar.gz","src_id":"13777","5":"13777","creation_date":"1283925261","6":"1283925261"},{"0":"3227","vim_version":"7.0","1":"7.0","script_version":"1.1.1","2":"1.1.1","version_comment":"FIX: indent error for code\r\nif( A ||\r\n\tB &&\r\n\tC)\r\n{\r\n}\r\n","3":"FIX: indent error for code\r\nif( A ||\r\n\tB &&\r\n\tC)\r\n{\r\n}\r\n","package":"simple-javascript-indenter-v1.1.1.tar.gz","4":"simple-javascript-indenter-v1.1.1.tar.gz","src_id":"13770","5":"13770","creation_date":"1283794689","6":"1283794689"},{"0":"3227","vim_version":"7.0","1":"7.0","script_version":"1.0.1","2":"1.0.1","version_comment":"Fix comment issue isn't solved after whole reindent if the first line is blank.","3":"Fix comment issue isn't solved after whole reindent if the first line is blank.","package":"simple-javascript-indenter-v1.0.1.tar.gz","4":"simple-javascript-indenter-v1.0.1.tar.gz","src_id":"13760","5":"13760","creation_date":"1283678195","6":"1283678195"}]},"3226":{"script_id":"3226","0":"3226","script_name":"lodestone","1":"lodestone","script_type":"color scheme","2":"color scheme","summary":"The most magnetic color scheme, guaranteed. (256 color)","3":"The most magnetic color scheme, guaranteed. (256 color)","description":"The most magnetic color scheme, guaranteed. \r\n\r\nA really wonderful color scheme. \r\n\r\nWould a shiv help motivate you?\r\n\r\nScreenshot: http:\/\/f.cl.ly\/items\/452C3Z0r3F1Z3p3B1j0S\/Voila_Capture.png","4":"The most magnetic color scheme, guaranteed. \r\n\r\nA really wonderful color scheme. \r\n\r\nWould a shiv help motivate you?\r\n\r\nScreenshot: http:\/\/f.cl.ly\/items\/452C3Z0r3F1Z3p3B1j0S\/Voila_Capture.png","install_details":"Copy to ~\/.vim\/colors","5":"Copy to ~\/.vim\/colors","first_name":"Matt","6":"Matt","last_name":"Petty","7":"Petty","releases":[{"0":"3226","vim_version":"7.0","1":"7.0","script_version":"4.1.1","2":"4.1.1","version_comment":"Minor color tweaks","3":"Minor color tweaks","package":"lodestone.vim","4":"lodestone.vim","src_id":"16943","5":"16943","creation_date":"1321982023","6":"1321982023"},{"0":"3226","vim_version":"7.0","1":"7.0","script_version":"4.1","2":"4.1","version_comment":"Adjustment to terminal colors to better match GUI","3":"Adjustment to terminal colors to better match GUI","package":"lodestone.vim","4":"lodestone.vim","src_id":"14557","5":"14557","creation_date":"1292683566","6":"1292683566"},{"0":"3226","vim_version":"7.0","1":"7.0","script_version":"4.0","2":"4.0","version_comment":"Initial upload","3":"Initial upload","package":"lodestone.vim","4":"lodestone.vim","src_id":"13736","5":"13736","creation_date":"1283279820","6":"1283279820"}]},"3225":{"script_id":"3225","0":"3225","script_name":"Flex 4","1":"Flex 4","script_type":"syntax","2":"syntax","summary":"Syntax highlighting for Adobe Flex 4","3":"Syntax highlighting for Adobe Flex 4","description":"Syntax highlighting for Adobe Flex 4 - mxml, actionscript 3 programming languages.\r\n(Modified version 1.1)\r\n\r\nThanks to previous authors:\r\nJohannes Zellner <johannes [at] zellner [dot] org>\r\nPaul Siegmann <pauls [at] euronet [dot] nl>\r\nAbdul Qabiz <mail [at] abdulqabiz [dot] com>","4":"Syntax highlighting for Adobe Flex 4 - mxml, actionscript 3 programming languages.\r\n(Modified version 1.1)\r\n\r\nThanks to previous authors:\r\nJohannes Zellner <johannes [at] zellner [dot] org>\r\nPaul Siegmann <pauls [at] euronet [dot] nl>\r\nAbdul Qabiz <mail [at] abdulqabiz [dot] com>","install_details":"Copy mxml.vim and actionscript.vim to syntax folder inside the vim directory.\r\nEdit your _vimrc file to include:\r\nautocmd BufRead *.as set filetype=actionscript\r\nautocmd BufRead *.mxml set filetype=mxml\r\nsyntax on","5":"Copy mxml.vim and actionscript.vim to syntax folder inside the vim directory.\r\nEdit your _vimrc file to include:\r\nautocmd BufRead *.as set filetype=actionscript\r\nautocmd BufRead *.mxml set filetype=mxml\r\nsyntax on","first_name":"Jaseem","6":"Jaseem","last_name":"V V","7":"V V","releases":[{"0":"3225","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"mxml_as3.zip","4":"mxml_as3.zip","src_id":"13720","5":"13720","creation_date":"1283128325","6":"1283128325"}]},"3224":{"script_id":"3224","0":"3224","script_name":"VIM Color Picker","1":"VIM Color Picker","script_type":"utility","2":"utility","summary":"A simple color picker for VIM, based on GTK color chooser dialog.","3":"A simple color picker for VIM, based on GTK color chooser dialog.","description":"VIM Color Picker is a simple color selector, based on GTK color chooser dialog. It permit you to easily insert an hexadecimal color in your CSS or HTML code. \r\n\r\nSCREENSHOT:\r\n    http:\/\/static.flogisoft.com\/vim\/vim_color_picker_0.1.png\r\n\r\nUSE:\r\n  When your are in insert mode or visual mode, press the <F5> button.\r\n  The color picker dialog appear, select a color and validate.\r\n\r\nDEPENDENCIES:\r\n  For working, this script need:\r\n    * VIM 7.x with Python support\r\n    * PyGTK 2.x","4":"VIM Color Picker is a simple color selector, based on GTK color chooser dialog. It permit you to easily insert an hexadecimal color in your CSS or HTML code. \r\n\r\nSCREENSHOT:\r\n    http:\/\/static.flogisoft.com\/vim\/vim_color_picker_0.1.png\r\n\r\nUSE:\r\n  When your are in insert mode or visual mode, press the <F5> button.\r\n  The color picker dialog appear, select a color and validate.\r\n\r\nDEPENDENCIES:\r\n  For working, this script need:\r\n    * VIM 7.x with Python support\r\n    * PyGTK 2.x","install_details":"Just copy \"color_picker.vim\" in your pluggin directory.","5":"Just copy \"color_picker.vim\" in your pluggin directory.","first_name":"Fabien","6":"Fabien","last_name":"LOISON","7":"LOISON","releases":[{"0":"3224","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"vim_color_picker_0.1.tar.gz","4":"vim_color_picker_0.1.tar.gz","src_id":"13715","5":"13715","creation_date":"1283103550","6":"1283103550"}]},"3223":{"script_id":"3223","0":"3223","script_name":"LanguageTool","1":"LanguageTool","script_type":"utility","2":"utility","summary":"Grammar checker for English, French, German (etc.) in Vim ","3":"Grammar checker for English, French, German (etc.) in Vim ","description":"This plugin integrates the LanguageTool grammar checker into Vim.\r\nCurrent version of LanguageTool can check grammar in many languages\r\nSee the list of supported languages: http:\/\/www.languagetool.org\/languages\/\r\nor http:\/\/www.languagetool.org\/ or more information about LanguageTool.\r\n\r\nThe script defines 2 commands:\r\n\r\n* Use  :LanguageToolCheck  to check grammar in current buffer.\r\n  This will check for grammar mistakes in text of current buffer\r\n  and highlight the errors. It also opens a new scratch window with the\r\n  list of grammar errors with further explanations for each error.\r\n  Pressing <Enter> in scratch buffer will jump to that error. The\r\n  location list for the buffer being checked is also populated.\r\n  So you can use location commands such as :lopen to open the location\r\n  list window, :lne to jump to the next error, etc.\r\n\r\n* Use  :LanguageToolClear  to remove highlighting of grammar mistakes,\r\n  close the scratch window containing the list of errors, clear and\r\n  close the location list.\r\n\r\nSee screenshots of grammar checking in English and French at:\r\n  http:\/\/dominique.pelle.free.fr\/pic\/LanguageToolVimPlugin_en.png\r\n  http:\/\/dominique.pelle.free.fr\/pic\/LanguageToolVimPlugin_fr.png\r\n\r\nSee  :help LanguageTool  for more details.\r\n\r\nLicense:\r\n  The VIM LICENSE applies to LanguageTool.vim plugin\r\n  (see \":help copyright\" except use \"LanguageTool.vim\" instead of Vim\").","4":"This plugin integrates the LanguageTool grammar checker into Vim.\r\nCurrent version of LanguageTool can check grammar in many languages\r\nSee the list of supported languages: http:\/\/www.languagetool.org\/languages\/\r\nor http:\/\/www.languagetool.org\/ or more information about LanguageTool.\r\n\r\nThe script defines 2 commands:\r\n\r\n* Use  :LanguageToolCheck  to check grammar in current buffer.\r\n  This will check for grammar mistakes in text of current buffer\r\n  and highlight the errors. It also opens a new scratch window with the\r\n  list of grammar errors with further explanations for each error.\r\n  Pressing <Enter> in scratch buffer will jump to that error. The\r\n  location list for the buffer being checked is also populated.\r\n  So you can use location commands such as :lopen to open the location\r\n  list window, :lne to jump to the next error, etc.\r\n\r\n* Use  :LanguageToolClear  to remove highlighting of grammar mistakes,\r\n  close the scratch window containing the list of errors, clear and\r\n  close the location list.\r\n\r\nSee screenshots of grammar checking in English and French at:\r\n  http:\/\/dominique.pelle.free.fr\/pic\/LanguageToolVimPlugin_en.png\r\n  http:\/\/dominique.pelle.free.fr\/pic\/LanguageToolVimPlugin_fr.png\r\n\r\nSee  :help LanguageTool  for more details.\r\n\r\nLicense:\r\n  The VIM LICENSE applies to LanguageTool.vim plugin\r\n  (see \":help copyright\" except use \"LanguageTool.vim\" instead of Vim\").","install_details":"Install the plugin with:\r\n\r\n  $ mkdir ~\/.vim\r\n  $ cd ~\/.vim\r\n  $ unzip \/path-to\/LanguageTool.zip\r\n  $ vim -c 'helptags ~\/.vim\/doc'\r\n\r\nTo use this plugin, you need to install the Java LanguageTool program. You\r\ncan choose to:\r\n\r\n* download stand-alone version of LanguageTool (LanguageTool-*.zip) from:\r\n  http:\/\/www.languagetool.org\/ using the orange button labeled\r\n  \"LanguageTool for standalone for your desktop\". The standalone version of\r\n  Vim not only does grammar checking but also contains Hunspell dictionaries\r\n  for spell checking.\r\n* or download a nightly build LanguageTool-.*-snapshot.zip from\r\n  http:\/\/www.languagetool.org\/download\/snapshots\/. It contains a more\r\n  recent version than the stable version but it is not as well tested.\r\n* or checkout and build the latest LanguageTool from sources in git\r\n  (https:\/\/github.com\/languagetool-org\/languagetool)\r\n\r\nSee \":help languagetool-installation\" for more details about installing LanguageTool.\r\n\r\nAfter installing LanguageTool, you must specify the location of the file\r\nlanguagetool-commandline.jar in your $HOME\/.vimrc file. Example:\r\n\r\n  let g:languagetool_jar='$HOME\/languagetool\/languagetool-standalone\/target\/LanguageTool-3.3-SNAPSHOT\/LanguageTool-3.3-SNAPSHOT\/languagetool-commandline.jar'","5":"Install the plugin with:\r\n\r\n  $ mkdir ~\/.vim\r\n  $ cd ~\/.vim\r\n  $ unzip \/path-to\/LanguageTool.zip\r\n  $ vim -c 'helptags ~\/.vim\/doc'\r\n\r\nTo use this plugin, you need to install the Java LanguageTool program. You\r\ncan choose to:\r\n\r\n* download stand-alone version of LanguageTool (LanguageTool-*.zip) from:\r\n  http:\/\/www.languagetool.org\/ using the orange button labeled\r\n  \"LanguageTool for standalone for your desktop\". The standalone version of\r\n  Vim not only does grammar checking but also contains Hunspell dictionaries\r\n  for spell checking.\r\n* or download a nightly build LanguageTool-.*-snapshot.zip from\r\n  http:\/\/www.languagetool.org\/download\/snapshots\/. It contains a more\r\n  recent version than the stable version but it is not as well tested.\r\n* or checkout and build the latest LanguageTool from sources in git\r\n  (https:\/\/github.com\/languagetool-org\/languagetool)\r\n\r\nSee \":help languagetool-installation\" for more details about installing LanguageTool.\r\n\r\nAfter installing LanguageTool, you must specify the location of the file\r\nlanguagetool-commandline.jar in your $HOME\/.vimrc file. Example:\r\n\r\n  let g:languagetool_jar='$HOME\/languagetool\/languagetool-standalone\/target\/LanguageTool-3.3-SNAPSHOT\/LanguageTool-3.3-SNAPSHOT\/languagetool-commandline.jar'","first_name":"Dominique","6":"Dominique","last_name":"Pell\u00c3\u00a9","7":"Pell\u00c3\u00a9","releases":[{"0":"3223","vim_version":"7.0","1":"7.0","script_version":"1.30","2":"1.30","version_comment":"- fixed several bugs","3":"- fixed several bugs","package":"LanguageTool.zip","4":"LanguageTool.zip","src_id":"24588","5":"24588","creation_date":"1475781653","6":"1475781653"},{"0":"3223","vim_version":"7.0","1":"7.0","script_version":"1.29","2":"1.29","version_comment":"- highlighting text could be wrong when text contained tabs","3":"- highlighting text could be wrong when text contained tabs","package":"LanguageTool.zip","4":"LanguageTool.zip","src_id":"23923","5":"23923","creation_date":"1453066801","6":"1453066801"},{"0":"3223","vim_version":"7.0","1":"7.0","script_version":"1.28","2":"1.28","version_comment":"- updated help file to reflect the change in LanguageTool:\r\n   LanguageTool.jar file was renamed into\r\n   languagetool-commandline.jar","3":"- updated help file to reflect the change in LanguageTool:\r\n   LanguageTool.jar file was renamed into\r\n   languagetool-commandline.jar","package":"LanguageTool.zip","4":"LanguageTool.zip","src_id":"21514","5":"21514","creation_date":"1392933924","6":"1392933924"},{"0":"3223","vim_version":"7.0","1":"7.0","script_version":"1.27","2":"1.27","version_comment":"- print stderr output of LanguageTool command line if somehow it fails to help diagnose problems.","3":"- print stderr output of LanguageTool command line if somehow it fails to help diagnose problems.","package":"LanguageTool.zip","4":"LanguageTool.zip","src_id":"21172","5":"21172","creation_date":"1386456322","6":"1386456322"},{"0":"3223","vim_version":"7.0","1":"7.0","script_version":"1.26","2":"1.26","version_comment":"- updated doc to describe how to download and install LanguageTool","3":"- updated doc to describe how to download and install LanguageTool","package":"LanguageTool.zip","4":"LanguageTool.zip","src_id":"20790","5":"20790","creation_date":"1378934198","6":"1378934198"},{"0":"3223","vim_version":"7.0","1":"7.0","script_version":"1.25","2":"1.25","version_comment":"- minor doc updates","3":"- minor doc updates","package":"LanguageTool.zip","4":"LanguageTool.zip","src_id":"19486","5":"19486","creation_date":"1360359727","6":"1360359727"},{"0":"3223","vim_version":"7.0","1":"7.0","script_version":"1.24","2":"1.24","version_comment":"- updated doc to explain how to build LanguageTool after LanguageTool moved from Ant to Maven\r\n- German spelling mistakes were highlighted as grammar errors\r\n- if no language is specified, use 'en-US' as default rather than 'en' so spelling mistakes are signalled.","3":"- updated doc to explain how to build LanguageTool after LanguageTool moved from Ant to Maven\r\n- German spelling mistakes were highlighted as grammar errors\r\n- if no language is specified, use 'en-US' as default rather than 'en' so spelling mistakes are signalled.","package":"LanguageTool.zip","4":"LanguageTool.zip","src_id":"19485","5":"19485","creation_date":"1360358141","6":"1360358141"},{"0":"3223","vim_version":"7.0","1":"7.0","script_version":"1.23","2":"1.23","version_comment":"- added items in menu of gvim: Plugin->LanguageTool->{Check,Clear}","3":"- added items in menu of gvim: Plugin->LanguageTool->{Check,Clear}","package":"LanguageTool.zip","4":"LanguageTool.zip","src_id":"18679","5":"18679","creation_date":"1348465651","6":"1348465651"},{"0":"3223","vim_version":"7.0","1":"7.0","script_version":"1.22","2":"1.22","version_comment":"- fixed xml parsing which was broken with latest LanguageTool nightly build (soon to become LanguageTool-1.9)\r\n- use norm! rather than norm to be more robust","3":"- fixed xml parsing which was broken with latest LanguageTool nightly build (soon to become LanguageTool-1.9)\r\n- use norm! rather than norm to be more robust","package":"LanguageTool.zip","4":"LanguageTool.zip","src_id":"18652","5":"18652","creation_date":"1348258881","6":"1348258881"},{"0":"3223","vim_version":"7.0","1":"7.0","script_version":"1.21","2":"1.21","version_comment":"- fixed bug reported by Alexey Radkov: plugin set invalid language for LanguageTool when 'spelllang' contained multiple languages (such as: ru_ru,en_us).\r\n- LanguageTool-1.8 is not required to be able to use language regions such as en-US, de-DE, etc.","3":"- fixed bug reported by Alexey Radkov: plugin set invalid language for LanguageTool when 'spelllang' contained multiple languages (such as: ru_ru,en_us).\r\n- LanguageTool-1.8 is not required to be able to use language regions such as en-US, de-DE, etc.","package":"LanguageTool.zip","4":"LanguageTool.zip","src_id":"18208","5":"18208","creation_date":"1341172769","6":"1341172769"},{"0":"3223","vim_version":"7.0","1":"7.0","script_version":"1.20","2":"1.20","version_comment":"- different highlighting for spelling error rules HUNSPELL_NO_SUGGEST_RULE and MORFOLOGIK_RULE_* than for grammar errors\r\n- automatically find the language region from spelllang","3":"- different highlighting for spelling error rules HUNSPELL_NO_SUGGEST_RULE and MORFOLOGIK_RULE_* than for grammar errors\r\n- automatically find the language region from spelllang","package":"LanguageTool.zip","4":"LanguageTool.zip","src_id":"18193","5":"18193","creation_date":"1340746532","6":"1340746532"},{"0":"3223","vim_version":"7.0","1":"7.0","script_version":"1.19","2":"1.19","version_comment":"- oops, last version fixed a highlighting bug with multi-byte, and introduced another bug. Correctly fixed now.","3":"- oops, last version fixed a highlighting bug with multi-byte, and introduced another bug. Correctly fixed now.","package":"LanguageTool.zip","4":"LanguageTool.zip","src_id":"18141","5":"18141","creation_date":"1339908567","6":"1339908567"},{"0":"3223","vim_version":"7.0","1":"7.0","script_version":"1.18","2":"1.18","version_comment":"- added g:languagetool_lang configuration variable to override 'spelllang'.\r\n- use different colors for grammar mistakes and spelling errors given by new HUNSPELL_RULE rule in LanguageTool-1.8.\r\n- fixed bug with utf-8 when highlighting errors","3":"- added g:languagetool_lang configuration variable to override 'spelllang'.\r\n- use different colors for grammar mistakes and spelling errors given by new HUNSPELL_RULE rule in LanguageTool-1.8.\r\n- fixed bug with utf-8 when highlighting errors","package":"LanguageTool.zip","4":"LanguageTool.zip","src_id":"18118","5":"18118","creation_date":"1339529077","6":"1339529077"},{"0":"3223","vim_version":"7.0","1":"7.0","script_version":"1.17","2":"1.17","version_comment":"- Unescape XML special char (ampersand...) before showing the URL ","3":"- Unescape XML special char (ampersand...) before showing the URL ","package":"LanguageTool.zip","4":"LanguageTool.zip","src_id":"18065","5":"18065","creation_date":"1338408563","6":"1338408563"},{"0":"3223","vim_version":"7.0","1":"7.0","script_version":"1.16","2":"1.16","version_comment":"- added support for <url> (new in LanguageTool-1.8) which can show a URL with more detailed information about a grammatical error.\r\n- added link to screencast in doc.","3":"- added support for <url> (new in LanguageTool-1.8) which can show a URL with more detailed information about a grammatical error.\r\n- added link to screencast in doc.","package":"LanguageTool.zip","4":"LanguageTool.zip","src_id":"18064","5":"18064","creation_date":"1338404688","6":"1338404688"},{"0":"3223","vim_version":"7.0","1":"7.0","script_version":"1.15","2":"1.15","version_comment":"Wrong portion of text could be highlighted when text near error contained quotes.","3":"Wrong portion of text could be highlighted when text near error contained quotes.","package":"LanguageTool.zip","4":"LanguageTool.zip","src_id":"17572","5":"17572","creation_date":"1331151585","6":"1331151585"},{"0":"3223","vim_version":"7.0","1":"7.0","script_version":"1.14","2":"1.14","version_comment":"- display subid in XML output of LanguageTool (introduced in LanguageTool-1.1)\r\n- updated doc now the LanguageTool project uses svn rather than cvs\r\n- removed handling of mouse (it was more annoying than useful to grab the mouse)\r\n","3":"- display subid in XML output of LanguageTool (introduced in LanguageTool-1.1)\r\n- updated doc now the LanguageTool project uses svn rather than cvs\r\n- removed handling of mouse (it was more annoying than useful to grab the mouse)\r\n","package":"LanguageTool.zip","4":"LanguageTool.zip","src_id":"15306","5":"15306","creation_date":"1301248014","6":"1301248014"},{"0":"3223","vim_version":"7.0","1":"7.0","script_version":"1.13","2":"1.13","version_comment":"- cope with small changes in XML output of LanguageTool-1-1-beta.\r\n- Plugin can still parse output of LanguageTool-1.0.","3":"- cope with small changes in XML output of LanguageTool-1-1-beta.\r\n- Plugin can still parse output of LanguageTool-1.0.","package":"LanguageTool.zip","4":"LanguageTool.zip","src_id":"13878","5":"13878","creation_date":"1285005785","6":"1285005785"},{"0":"3223","vim_version":"7.0","1":"7.0","script_version":"1.12","2":"1.12","version_comment":"- (bug) fixed incorrect handling of multibyte causing missing highlighting","3":"- (bug) fixed incorrect handling of multibyte causing missing highlighting","package":"LanguageTool.zip","4":"LanguageTool.zip","src_id":"13773","5":"13773","creation_date":"1283888152","6":"1283888152"},{"0":"3223","vim_version":"7.0","1":"7.0","script_version":"1.11","2":"1.11","version_comment":"- (bug) regex to parse rules from LanguageTool output did not accept rule with dash\r\n- (improvement) don't waste a line displaying \"Correction:\" in scratch buffer when error has no suggested correction ","3":"- (bug) regex to parse rules from LanguageTool output did not accept rule with dash\r\n- (improvement) don't waste a line displaying \"Correction:\" in scratch buffer when error has no suggested correction ","package":"LanguageTool.zip","4":"LanguageTool.zip","src_id":"13759","5":"13759","creation_date":"1283628373","6":"1283628373"},{"0":"3223","vim_version":"7.0","1":"7.0","script_version":"1.10","2":"1.10","version_comment":"- avoid spurious highlighting when text of error appears multiple times in line.","3":"- avoid spurious highlighting when text of error appears multiple times in line.","package":"LanguageTool.zip","4":"LanguageTool.zip","src_id":"13748","5":"13748","creation_date":"1283502681","6":"1283502681"},{"0":"3223","vim_version":"7.0","1":"7.0","script_version":"1.9","2":"1.9","version_comment":"- improved handling of LeftMouse event (used when clicking on error to jump to its location)","3":"- improved handling of LeftMouse event (used when clicking on error to jump to its location)","package":"LanguageTool.zip","4":"LanguageTool.zip","src_id":"13745","5":"13745","creation_date":"1283461773","6":"1283461773"},{"0":"3223","vim_version":"7.0","1":"7.0","script_version":"1.8","2":"1.8","version_comment":"- (bug) fixed syntax error\r\n- fixed broken links in help page","3":"- (bug) fixed syntax error\r\n- fixed broken links in help page","package":"LanguageTool.zip","4":"LanguageTool.zip","src_id":"13730","5":"13730","creation_date":"1283194973","6":"1283194973"},{"0":"3223","vim_version":"7.0","1":"7.0","script_version":"1.7","2":"1.7","version_comment":"- :LanguageToolCheck command now accepts a range \r\n- (bug) more fixes to properly handle XML characters such as & ","3":"- :LanguageToolCheck command now accepts a range \r\n- (bug) more fixes to properly handle XML characters such as & ","package":"LanguageTool.zip","4":"LanguageTool.zip","src_id":"13729","5":"13729","creation_date":"1283190002","6":"1283190002"},{"0":"3223","vim_version":"7.0","1":"7.0","script_version":"1.6","2":"1.6","version_comment":"- created a Vim help page  (:help LanguageTool)","3":"- created a Vim help page  (:help LanguageTool)","package":"LanguageTool.zip","4":"LanguageTool.zip","src_id":"13727","5":"13727","creation_date":"1283161784","6":"1283161784"},{"0":"3223","vim_version":"7.0","1":"7.0","script_version":"1.5","2":"1.5","version_comment":"- (bug) XML code such as " < (etc) had to be replaced in \" & (etc)\r\n- (bug) escaping \\ and ' in regex was not right\r\n- improved comment explaining how to install LanguageTool\r\n","3":"- (bug) XML code such as " < (etc) had to be replaced in \" & (etc)\r\n- (bug) escaping \\ and ' in regex was not right\r\n- improved comment explaining how to install LanguageTool\r\n","package":"LanguageTool.vim","4":"LanguageTool.vim","src_id":"13726","5":"13726","creation_date":"1283152544","6":"1283152544"},{"0":"3223","vim_version":"7.0","1":"7.0","script_version":"1.4","2":"1.4","version_comment":"- (bug) substitute things like "e; into \" from input XML.","3":"- (bug) substitute things like "e; into \" from input XML.","package":"LanguageTool.vim","4":"LanguageTool.vim","src_id":"13719","5":"13719","creation_date":"1283124542","6":"1283124542"},{"0":"3223","vim_version":"7.0","1":"7.0","script_version":"1.3","2":"1.3","version_comment":"- populate location list (can now use commands :lopen, :lne, ...)","3":"- populate location list (can now use commands :lopen, :lne, ...)","package":"LanguageTool.vim","4":"LanguageTool.vim","src_id":"13717","5":"13717","creation_date":"1283119852","6":"1283119852"},{"0":"3223","vim_version":"7.0","1":"7.0","script_version":"1.2","2":"1.2","version_comment":"- check whether running language tool succeeded + a few other fixes","3":"- check whether running language tool succeeded + a few other fixes","package":"LanguageTool.vim","4":"LanguageTool.vim","src_id":"13716","5":"13716","creation_date":"1283112343","6":"1283112343"},{"0":"3223","vim_version":"7.0","1":"7.0","script_version":"1.1","2":"1.1","version_comment":"- (bug) fall back to 'enc' encoding when 'fenc' is not set\r\n- (new) can now click on error in scratch buffer to jump to them (if mouse is enabled)\r\n","3":"- (bug) fall back to 'enc' encoding when 'fenc' is not set\r\n- (new) can now click on error in scratch buffer to jump to them (if mouse is enabled)\r\n","package":"LanguageTool.vim","4":"LanguageTool.vim","src_id":"13714","5":"13714","creation_date":"1283099672","6":"1283099672"},{"0":"3223","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"- added escape() and nomagic in a regex to avoid errors\r\n","3":"- added escape() and nomagic in a regex to avoid errors\r\n","package":"LanguageTool.vim","4":"LanguageTool.vim","src_id":"13712","5":"13712","creation_date":"1283085879","6":"1283085879"},{"0":"3223","vim_version":"7.0","1":"7.0","script_version":"0.9","2":"0.9","version_comment":"- pressing <Enter> on an error in scratch buffer now jumps to that error","3":"- pressing <Enter> on an error in scratch buffer now jumps to that error","package":"LanguageTool.vim","4":"LanguageTool.vim","src_id":"13709","5":"13709","creation_date":"1283069055","6":"1283069055"},{"0":"3223","vim_version":"7.0","1":"7.0","script_version":"0.8","2":"0.8","version_comment":"Initial upload","3":"Initial upload","package":"LanguageTool.vim","4":"LanguageTool.vim","src_id":"13705","5":"13705","creation_date":"1283024335","6":"1283024335"}]},"3222":{"script_id":"3222","0":"3222","script_name":"285colors-with-az-menu","1":"285colors-with-az-menu","script_type":"color scheme","2":"color scheme","summary":"285 color schemes for Vim with alphabetical menu","3":"285 color schemes for Vim with alphabetical menu","description":"A version of \"Color Sampler Pack\", original by Robert Melton <iam@robertmelton.com>\r\n","4":"A version of \"Color Sampler Pack\", original by Robert Melton <iam@robertmelton.com>\r\n","install_details":"Unzip and place the files in the 'plugin' and 'colors' directories.","5":"Unzip and place the files in the 'plugin' and 'colors' directories.","first_name":"Stan","6":"Stan","last_name":"Ba","7":"Ba","releases":[{"0":"3222","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"285colors-with-az-menu.zip","4":"285colors-with-az-menu.zip","src_id":"13693","5":"13693","creation_date":"1282917623","6":"1282917623"}]},"3221":{"script_id":"3221","0":"3221","script_name":"indexer.tar.gz","1":"indexer.tar.gz","script_type":"utility","2":"utility","summary":"Auto-generate tags for all files of project(s) and keep tags up-to-date","3":"Auto-generate tags for all files of project(s) and keep tags up-to-date","description":"I've published a detailed article about Indexer + Vimprj usage, you might want to read it: https:\/\/dmitryfrank.com\/articles\/vim_project_code_navigation\r\n\r\n-----------------------------------\r\n\r\nThis plugin can work in two ways:\r\n1) independently\r\n2) as add-on for project.tar.gz (vimscript #69)\r\n\r\nIn both ways, it provides painless automatic tags generation for whole project(s) and keeps tags up-to-date.\r\n\r\nIMPORTANT: you need patched version of ctags (5.8.1) to make this plugin work correctly with C\/C++ files, because of bug in ctags 5.8. You can read detailed info about this bug and download patched version here: http:\/\/dfrank.ru\/ctags581\/en.html\r\n\r\nThis plugin can be very useful when it's used together with plugins omnicppcomplete (for c, c++ development), code_complete.vim and other plugins that use tags.  You also will be able to jump from function call to its definition just by pressing Ctrl-] or g]\r\n\r\nAs i said, Indexer can work as add-on for project.tar.gz plugin ( vimscript #69 ). Indexer reads project file, parses it and builds tags for all files in project. But it also works fine without project.tar.gz.\r\n\r\nActually, if you use project.tar.gz plugin and your projects file is default (~\/.vimprojects), then setting Indexer up is very easily: you can just install this plugin, start Vim and open any file from your project. Indexer will detect that opened file is a file from project and automatically start ctags for each file in this project.  It also set &path and &tags options for Vim.\r\n\r\nIf you use project.tar.gz, but you have another projects file, you should set option g:indexer_projectsSettingsFilename in your vimrc.\r\n\r\nIf you don't use project.tar.gz then you can use \".indexer_files\" to define projects and files to index.  Default location of this file is \"~\/.indexer_files\". You can change it by modifying variable g:indexer_indexerListFilename\r\n\r\nSyntax of this file is simple, probably the best way to explain it is to show an example:\r\n\r\nNOTE! Since Indexer 4.10 syntax of .indexer_files is changed a bit, to make ctags work much more effectively.  However, old syntax will work too, for backward compatibility.  If you used Indexer before with .indexer_files, please read this:\r\n:help indexer-syn-change-4.10\r\n\r\n--------------------- example ~\/.indexer_files -----------------------\r\n   [CoolProject]\r\n\r\n   \/home\/user\/cool_project\r\n\r\n   [AnotherProject]\r\n   option:ctags_params = \"--languages=c++\"\r\n\r\n   \/home\/user\/another_project\/src\r\n   \/home\/user\/another_project\/lib\r\n-------------------------------------------------------------------------------\r\nI hope all is obvious:\r\nThere's two projects: CoolProject and AnotherProject.\r\nCoolProject just contains ALL files from \"\/home\/user\/myproject\".\r\nAnotherProject is configured more complicated.\r\nIt specifies additional parameter for ctags: \"--languages=c++\".\r\nIt is needed to make ctags ignore all files except c++ sources.\r\nI would recommend you to read and understand ctags help, to be able to write perfect configuration for your projects.\r\nYou can read it here: http:\/\/ctags.sourceforge.net\/ctags.html\r\nThe options you need to know first is the following two:\r\n   --languages=[+|-]<list>\r\n   --langmap=<map>[,<map[...]>]\r\n\r\n\r\nIf you have many projects and you are lazy to put every project in\r\nthis file, you can put in your ~\/.indexer_files something like this:\r\n\r\n--------------------- example ~\/.indexer_files -----------------------\r\n[PROJECTS_PARENT]\r\noption:ctags_params=\"--languages=c++,c,python,java\"\r\n\r\n~\/workspace\r\n-------------------------------------------------------------------------------\r\n\r\nThe keyword is PROJECTS_PARENT.\r\nIn this way, each directory in ~\/workspace will be interpreted as separate\r\nproject, and you can open any file from any project in ~\/workspace, and the \r\nwhole proper project will be indexed.\r\n\r\n\r\nPlease note: suggested ctags options is tested with ctags 5.8. As far as i\r\nknow, option --languages is marked as deprecated in ctags 5.9, but i still did\r\nnot test it, because the latest version on http:\/\/ctags.sourceforge.net is\r\nstill 5.8. I hope i will have time for this soon.\r\n\r\n\r\nIndexer 3.0 and later supports open several files from several projects. For example, a little story.\r\n\r\nYou have two projects: \"project1\" and \"project2\", and you use \"~\/.indexer_files\".\r\n\r\n1) you open file1 from project1. \r\n   Indexer generates tags for all files from project1 and set &tags:\r\n   ~\/.indexer_files_tags\/project1\r\n2) you open file2 from the same project1.\r\n   Indexer just notes that file2 is file from project1. \r\n   &tags does not change.\r\n3) you open file3 from project2.\r\n   Indexer generates tags for all files from project2 and set &tags:\r\n   ~\/.indexer_files_tags\/project2.\r\n4) you switch to buffer with file1.\r\n   Indexer does not generate any tags, it just changes &tags to\r\n   ~\/.indexer_files_tags\/project1\r\n5) you switch to buffer with file3.\r\n   Indexer changes &tags back to ~\/.indexer_files_tags\/project2 .\r\n\r\nSo, you should not care about your projects. It just works. If you have some projects with subprojects, i would recommend you to use .vimprj directory with specific settings for your project, in which you can set any options such as &tags, &tabstop, etc. More detailed: read :help vimprj\r\n\r\nActually, Indexer sets &path for needed project when you swith to new buffer, not only &tags.\r\n\r\n----\r\n\r\nIt is successfully tested on Vim 7.3, on the following systems:\r\n*) Archlinux\r\n*) Ubuntu 10.4\r\n*) Windows XP\r\n*) Mac OS X Lion\r\n\r\nPlease, if you have another system configuration and all works fine for you, \r\nplease send to me your configuration, i'll update text on this page.\r\n\r\nIf you have any troubles using this plugin, feel free to email me.\r\nYou also can contact me in irc:\r\nserver: irc.freenode.net\r\nchannel: #vim\r\nnick: dfrank\r\n\r\n-------------------------\r\n\r\nDevelopment mercurial repository: http:\/\/hg.dfrank.ru\/vim\/bundle\/indexer_development\r\nStable git repository: https:\/\/github.com\/vim-scripts\/indexer.tar.gz (Note that this repository is auto-generated by http:\/\/vim-scripts.org as a mirror of http:\/\/www.vim.org)\r\n\r\n\r\n","4":"I've published a detailed article about Indexer + Vimprj usage, you might want to read it: https:\/\/dmitryfrank.com\/articles\/vim_project_code_navigation\r\n\r\n-----------------------------------\r\n\r\nThis plugin can work in two ways:\r\n1) independently\r\n2) as add-on for project.tar.gz (vimscript #69)\r\n\r\nIn both ways, it provides painless automatic tags generation for whole project(s) and keeps tags up-to-date.\r\n\r\nIMPORTANT: you need patched version of ctags (5.8.1) to make this plugin work correctly with C\/C++ files, because of bug in ctags 5.8. You can read detailed info about this bug and download patched version here: http:\/\/dfrank.ru\/ctags581\/en.html\r\n\r\nThis plugin can be very useful when it's used together with plugins omnicppcomplete (for c, c++ development), code_complete.vim and other plugins that use tags.  You also will be able to jump from function call to its definition just by pressing Ctrl-] or g]\r\n\r\nAs i said, Indexer can work as add-on for project.tar.gz plugin ( vimscript #69 ). Indexer reads project file, parses it and builds tags for all files in project. But it also works fine without project.tar.gz.\r\n\r\nActually, if you use project.tar.gz plugin and your projects file is default (~\/.vimprojects), then setting Indexer up is very easily: you can just install this plugin, start Vim and open any file from your project. Indexer will detect that opened file is a file from project and automatically start ctags for each file in this project.  It also set &path and &tags options for Vim.\r\n\r\nIf you use project.tar.gz, but you have another projects file, you should set option g:indexer_projectsSettingsFilename in your vimrc.\r\n\r\nIf you don't use project.tar.gz then you can use \".indexer_files\" to define projects and files to index.  Default location of this file is \"~\/.indexer_files\". You can change it by modifying variable g:indexer_indexerListFilename\r\n\r\nSyntax of this file is simple, probably the best way to explain it is to show an example:\r\n\r\nNOTE! Since Indexer 4.10 syntax of .indexer_files is changed a bit, to make ctags work much more effectively.  However, old syntax will work too, for backward compatibility.  If you used Indexer before with .indexer_files, please read this:\r\n:help indexer-syn-change-4.10\r\n\r\n--------------------- example ~\/.indexer_files -----------------------\r\n   [CoolProject]\r\n\r\n   \/home\/user\/cool_project\r\n\r\n   [AnotherProject]\r\n   option:ctags_params = \"--languages=c++\"\r\n\r\n   \/home\/user\/another_project\/src\r\n   \/home\/user\/another_project\/lib\r\n-------------------------------------------------------------------------------\r\nI hope all is obvious:\r\nThere's two projects: CoolProject and AnotherProject.\r\nCoolProject just contains ALL files from \"\/home\/user\/myproject\".\r\nAnotherProject is configured more complicated.\r\nIt specifies additional parameter for ctags: \"--languages=c++\".\r\nIt is needed to make ctags ignore all files except c++ sources.\r\nI would recommend you to read and understand ctags help, to be able to write perfect configuration for your projects.\r\nYou can read it here: http:\/\/ctags.sourceforge.net\/ctags.html\r\nThe options you need to know first is the following two:\r\n   --languages=[+|-]<list>\r\n   --langmap=<map>[,<map[...]>]\r\n\r\n\r\nIf you have many projects and you are lazy to put every project in\r\nthis file, you can put in your ~\/.indexer_files something like this:\r\n\r\n--------------------- example ~\/.indexer_files -----------------------\r\n[PROJECTS_PARENT]\r\noption:ctags_params=\"--languages=c++,c,python,java\"\r\n\r\n~\/workspace\r\n-------------------------------------------------------------------------------\r\n\r\nThe keyword is PROJECTS_PARENT.\r\nIn this way, each directory in ~\/workspace will be interpreted as separate\r\nproject, and you can open any file from any project in ~\/workspace, and the \r\nwhole proper project will be indexed.\r\n\r\n\r\nPlease note: suggested ctags options is tested with ctags 5.8. As far as i\r\nknow, option --languages is marked as deprecated in ctags 5.9, but i still did\r\nnot test it, because the latest version on http:\/\/ctags.sourceforge.net is\r\nstill 5.8. I hope i will have time for this soon.\r\n\r\n\r\nIndexer 3.0 and later supports open several files from several projects. For example, a little story.\r\n\r\nYou have two projects: \"project1\" and \"project2\", and you use \"~\/.indexer_files\".\r\n\r\n1) you open file1 from project1. \r\n   Indexer generates tags for all files from project1 and set &tags:\r\n   ~\/.indexer_files_tags\/project1\r\n2) you open file2 from the same project1.\r\n   Indexer just notes that file2 is file from project1. \r\n   &tags does not change.\r\n3) you open file3 from project2.\r\n   Indexer generates tags for all files from project2 and set &tags:\r\n   ~\/.indexer_files_tags\/project2.\r\n4) you switch to buffer with file1.\r\n   Indexer does not generate any tags, it just changes &tags to\r\n   ~\/.indexer_files_tags\/project1\r\n5) you switch to buffer with file3.\r\n   Indexer changes &tags back to ~\/.indexer_files_tags\/project2 .\r\n\r\nSo, you should not care about your projects. It just works. If you have some projects with subprojects, i would recommend you to use .vimprj directory with specific settings for your project, in which you can set any options such as &tags, &tabstop, etc. More detailed: read :help vimprj\r\n\r\nActually, Indexer sets &path for needed project when you swith to new buffer, not only &tags.\r\n\r\n----\r\n\r\nIt is successfully tested on Vim 7.3, on the following systems:\r\n*) Archlinux\r\n*) Ubuntu 10.4\r\n*) Windows XP\r\n*) Mac OS X Lion\r\n\r\nPlease, if you have another system configuration and all works fine for you, \r\nplease send to me your configuration, i'll update text on this page.\r\n\r\nIf you have any troubles using this plugin, feel free to email me.\r\nYou also can contact me in irc:\r\nserver: irc.freenode.net\r\nchannel: #vim\r\nnick: dfrank\r\n\r\n-------------------------\r\n\r\nDevelopment mercurial repository: http:\/\/hg.dfrank.ru\/vim\/bundle\/indexer_development\r\nStable git repository: https:\/\/github.com\/vim-scripts\/indexer.tar.gz (Note that this repository is auto-generated by http:\/\/vim-scripts.org as a mirror of http:\/\/www.vim.org)\r\n\r\n\r\n","install_details":"There's some dependencies: \r\n1) script-library DfrankUtil (vimscript #3884) \r\n2) script Vimprj (vimscript #3872)\r\n\r\nFunctionality of the Vimprj plugin has been implemented in Indexer earlier, but now Indexer functionality is divided in two plugins: Indexer and Vimprj.\r\nIf you don't need Vimprj's functionality, just install Vimprj and do not use it. It will not disturb you.\r\n\r\nAnd i suggest you to use pathogen (vimscript #2332) to manage your plugins.\r\n","5":"There's some dependencies: \r\n1) script-library DfrankUtil (vimscript #3884) \r\n2) script Vimprj (vimscript #3872)\r\n\r\nFunctionality of the Vimprj plugin has been implemented in Indexer earlier, but now Indexer functionality is divided in two plugins: Indexer and Vimprj.\r\nIf you don't need Vimprj's functionality, just install Vimprj and do not use it. It will not disturb you.\r\n\r\nAnd i suggest you to use pathogen (vimscript #2332) to manage your plugins.\r\n","first_name":"Dmitry","6":"Dmitry","last_name":"Frank","7":"Frank","releases":[{"0":"3221","vim_version":"7.0","1":"7.0","script_version":"4.16","2":"4.16","version_comment":"I've published a thorough article on advanced Indexer + Vimprj usage, you might want to check it out: http:\/\/dmitryfrank.com\/articles\/vim_project_code_navigation\r\n\r\nNew in this version:\r\n\r\n- Added an option dontUpdateTagsIfFileExists that prevents Indexer from re-generating tags if tags file already exists. Useful on large projects;\r\n- Added several example projects that illustrate Indexer + Vimprj usage. See the aforementioned article for details\r\n","3":"I've published a thorough article on advanced Indexer + Vimprj usage, you might want to check it out: http:\/\/dmitryfrank.com\/articles\/vim_project_code_navigation\r\n\r\nNew in this version:\r\n\r\n- Added an option dontUpdateTagsIfFileExists that prevents Indexer from re-generating tags if tags file already exists. Useful on large projects;\r\n- Added several example projects that illustrate Indexer + Vimprj usage. See the aforementioned article for details\r\n","package":"indexer-4.16.zip","4":"indexer-4.16.zip","src_id":"23666","5":"23666","creation_date":"1444657588","6":"1444657588"},{"0":"3221","vim_version":"7.0","1":"7.0","script_version":"4.15","2":"4.15","version_comment":"*) Fixed issue with background tags generation in terminal vim, thanks to John Jarvis.\r\n*) Fixed some little appearance bugs\r\n*) Compatibility with latest vimprj plugin (1.08)","3":"*) Fixed issue with background tags generation in terminal vim, thanks to John Jarvis.\r\n*) Fixed some little appearance bugs\r\n*) Compatibility with latest vimprj plugin (1.08)","package":"indexer-4.15.zip","4":"indexer-4.15.zip","src_id":"18526","5":"18526","creation_date":"1346523451","6":"1346523451"},{"0":"3221","vim_version":"7.0","1":"7.0","script_version":"4.14","2":"4.14","version_comment":"*) Nested projects is now supported. If one project is a subdir(s) of another one, then only nested project will be used for inner files.  This will also work for PROJECTS_PARENT. I mean, you can set up your .indexer_files just like that: \r\n\r\n[PROJECTS_PARENT] \r\n~\/dev \r\n~\/dev\/SomeProject \r\n\r\nand then each dir in ~\/dev will be a separate project, and each dir in ~\/dev\/SomeProject will also be sepate project. \r\n\r\n*) Some bugfix","3":"*) Nested projects is now supported. If one project is a subdir(s) of another one, then only nested project will be used for inner files.  This will also work for PROJECTS_PARENT. I mean, you can set up your .indexer_files just like that: \r\n\r\n[PROJECTS_PARENT] \r\n~\/dev \r\n~\/dev\/SomeProject \r\n\r\nand then each dir in ~\/dev will be a separate project, and each dir in ~\/dev\/SomeProject will also be sepate project. \r\n\r\n*) Some bugfix","package":"indexer-4.14.tar.gz","4":"indexer-4.14.tar.gz","src_id":"17352","5":"17352","creation_date":"1328041341","6":"1328041341"},{"0":"3221","vim_version":"7.0","1":"7.0","script_version":"4.13","2":"4.13","version_comment":"*) MacVim is now supported. Thanks to Asis Hallab for bugreport and for help to implement it.\r\n*) Added new option g:indexer_vimExecutable, it is needed if you want your\r\ncustom vim to be executed instead of standard \"vim\" (or \"mvim\" on MacVim). Thanks to Asis Hallab again for nice idea.","3":"*) MacVim is now supported. Thanks to Asis Hallab for bugreport and for help to implement it.\r\n*) Added new option g:indexer_vimExecutable, it is needed if you want your\r\ncustom vim to be executed instead of standard \"vim\" (or \"mvim\" on MacVim). Thanks to Asis Hallab again for nice idea.","package":"indexer-4.13.tar.gz","4":"indexer-4.13.tar.gz","src_id":"17335","5":"17335","creation_date":"1327861910","6":"1327861910"},{"0":"3221","vim_version":"7.0","1":"7.0","script_version":"4.12","2":"4.12","version_comment":"*) Bugfix: file .indexer_files wasn't parsed if you have custom filename for it with \"~\" in the path. Thanks to Dmitry Yudin for reporting this.\r\n*) Bugfix: syntax file for .indexer_files had fileformat \"dos\". Changed to \"unix\".","3":"*) Bugfix: file .indexer_files wasn't parsed if you have custom filename for it with \"~\" in the path. Thanks to Dmitry Yudin for reporting this.\r\n*) Bugfix: syntax file for .indexer_files had fileformat \"dos\". Changed to \"unix\".","package":"indexer-4.12.tar.gz","4":"indexer-4.12.tar.gz","src_id":"17250","5":"17250","creation_date":"1326912180","6":"1326912180"},{"0":"3221","vim_version":"7.0","1":"7.0","script_version":"4.11","2":"4.11","version_comment":"*) Optimization: when there's many projects available, opening new file was too slow. Now this is solved.\r\n*) Please download latest version 1.06 of Vimprj script (vimscript #3872).\r\n*) Yet another dependency added: script-library DfrankUtil (vimscript #3884). Sorry if you are bored by all these dependencies, but now i really need to put my common code in one place.","3":"*) Optimization: when there's many projects available, opening new file was too slow. Now this is solved.\r\n*) Please download latest version 1.06 of Vimprj script (vimscript #3872).\r\n*) Yet another dependency added: script-library DfrankUtil (vimscript #3884). Sorry if you are bored by all these dependencies, but now i really need to put my common code in one place.","package":"indexer-4.11.tar.gz","4":"indexer-4.11.tar.gz","src_id":"17220","5":"17220","creation_date":"1326646529","6":"1326646529"},{"0":"3221","vim_version":"7.0","1":"7.0","script_version":"4.10","2":"4.10","version_comment":"*) Optimized work with .vimprojects file (with project.tar.gz plugin) on rather large projects: now, Indexer generates filelist, stores it into the file and passes it to ctags with \"-L\" key, instead of passing each file directly in command line. This makes ctags work much faster, because in earlier versions it was called several times with \"-a\" key if command is too long.\r\n*) Optimized work with .indexer_files file: syntax of this file changed a bit, to make ctags settings much more effective. However, old syntax works too, for backward compatibility reasons. If you used Indexer before with .indexer_files, then I would strongly recommend you to read :help indexer-syn-change-4.10 .\r\n*) Added syntax file for .indexer_files .\r\nIf you found a bug, please report it to me.\r\n","3":"*) Optimized work with .vimprojects file (with project.tar.gz plugin) on rather large projects: now, Indexer generates filelist, stores it into the file and passes it to ctags with \"-L\" key, instead of passing each file directly in command line. This makes ctags work much faster, because in earlier versions it was called several times with \"-a\" key if command is too long.\r\n*) Optimized work with .indexer_files file: syntax of this file changed a bit, to make ctags settings much more effective. However, old syntax works too, for backward compatibility reasons. If you used Indexer before with .indexer_files, then I would strongly recommend you to read :help indexer-syn-change-4.10 .\r\n*) Added syntax file for .indexer_files .\r\nIf you found a bug, please report it to me.\r\n","package":"indexer-4.10.tar.gz","4":"indexer-4.10.tar.gz","src_id":"17208","5":"17208","creation_date":"1326575248","6":"1326575248"},{"0":"3221","vim_version":"7.0","1":"7.0","script_version":"4.04","2":"4.04","version_comment":"*) IMPORTANT NOTE: since version 4.00 there is a dependency: plugin vimprj ( vimscript #3872 )\r\n*) Some performance improvements\r\n*) Many, many refactor. Previous versions was laggy in some cases when used on remote machines, now it is solved. Thanks to Thiago Bellini for bugreports and for being a beta-tester.","3":"*) IMPORTANT NOTE: since version 4.00 there is a dependency: plugin vimprj ( vimscript #3872 )\r\n*) Some performance improvements\r\n*) Many, many refactor. Previous versions was laggy in some cases when used on remote machines, now it is solved. Thanks to Thiago Bellini for bugreports and for being a beta-tester.","package":"indexer-4.04.tar.gz","4":"indexer-4.04.tar.gz","src_id":"17168","5":"17168","creation_date":"1325961054","6":"1325961054"},{"0":"3221","vim_version":"7.0","1":"7.0","script_version":"3.18","2":"3.18","version_comment":"* Added option g:indexer_changeCurDirIfVimprjFound.\r\nIf anyone wants to make Indexer not to change current dir automatically if .vimprj directory is found, then you can specify in your vimrc:\r\n\r\nlet g:indexer_changeCurDirIfVimprjFound = 0\r\n","3":"* Added option g:indexer_changeCurDirIfVimprjFound.\r\nIf anyone wants to make Indexer not to change current dir automatically if .vimprj directory is found, then you can specify in your vimrc:\r\n\r\nlet g:indexer_changeCurDirIfVimprjFound = 0\r\n","package":"indexer-3.18.tar.gz","4":"indexer-3.18.tar.gz","src_id":"16521","5":"16521","creation_date":"1315977944","6":"1315977944"},{"0":"3221","vim_version":"7.0","1":"7.0","script_version":"3.17","2":"3.17","version_comment":"* Optimization change: with .indexer_files default value of g:indexer_ctagsDontSpecifyFilesIfPossible is 1, but with .vimprojects default value is 0.","3":"* Optimization change: with .indexer_files default value of g:indexer_ctagsDontSpecifyFilesIfPossible is 1, but with .vimprojects default value is 0.","package":"indexer-3.17.tar.gz","4":"indexer-3.17.tar.gz","src_id":"16324","5":"16324","creation_date":"1313950643","6":"1313950643"},{"0":"3221","vim_version":"7.0","1":"7.0","script_version":"3.16","2":"3.16","version_comment":"* Bugfix: on FreeBSD we should check executable 'exctags' before 'ctags', because of 'ctags' is also present, but it is not actually Exuberant ctags. Thanks to Olivier Szika for bugreport.","3":"* Bugfix: on FreeBSD we should check executable 'exctags' before 'ctags', because of 'ctags' is also present, but it is not actually Exuberant ctags. Thanks to Olivier Szika for bugreport.","package":"indexer-3.16.tar.gz","4":"indexer-3.16.tar.gz","src_id":"16293","5":"16293","creation_date":"1313652238","6":"1313652238"},{"0":"3221","vim_version":"7.0","1":"7.0","script_version":"3.14","2":"3.14","version_comment":"* Bugfix: $INDEXER_PROJECT_ROOT wasn't work in .vimprojects file. Thanks to Alexander Pazdnikov for bugreport.","3":"* Bugfix: $INDEXER_PROJECT_ROOT wasn't work in .vimprojects file. Thanks to Alexander Pazdnikov for bugreport.","package":"indexer-3.14.tar.gz","4":"indexer-3.14.tar.gz","src_id":"15524","5":"15524","creation_date":"1303802130","6":"1303802130"},{"0":"3221","vim_version":"7.0","1":"7.0","script_version":"3.12","2":"3.12","version_comment":"Some improvements in error reporting: \r\n* error if no ctags is available in the PATH, \r\n* warning when ctags returns error.","3":"Some improvements in error reporting: \r\n* error if no ctags is available in the PATH, \r\n* warning when ctags returns error.","package":"indexer-3.12.tar.gz","4":"indexer-3.12.tar.gz","src_id":"15298","5":"15298","creation_date":"1301181766","6":"1301181766"},{"0":"3221","vim_version":"7.0","1":"7.0","script_version":"3.11","2":"3.11","version_comment":"* Bugfix: if \"noswapfile\" option is set, then tags wasn't generated. Thanks to Thiago Bellini for help and persistence =)\r\n* Bugfix: :IndexerFiles command didn't work.","3":"* Bugfix: if \"noswapfile\" option is set, then tags wasn't generated. Thanks to Thiago Bellini for help and persistence =)\r\n* Bugfix: :IndexerFiles command didn't work.","package":"indexer-3.11.tar.gz","4":"indexer-3.11.tar.gz","src_id":"15282","5":"15282","creation_date":"1300949796","6":"1300949796"},{"0":"3221","vim_version":"7.0","1":"7.0","script_version":"3.1","2":"3.1","version_comment":"* Bugfixes\r\n* When no servername is present, tags generate in Vim thread, not in background. (because i don't know how to execute remote command in Vim without servername. If anyone know, please contact me)","3":"* Bugfixes\r\n* When no servername is present, tags generate in Vim thread, not in background. (because i don't know how to execute remote command in Vim without servername. If anyone know, please contact me)","package":"indexer-3.1.tar.gz","4":"indexer-3.1.tar.gz","src_id":"15271","5":"15271","creation_date":"1300740155","6":"1300740155"},{"0":"3221","vim_version":"7.0","1":"7.0","script_version":"3.0","2":"3.0","version_comment":"* Multiple projects supported. For example, you open file1 from one project, and then you open file2 from second project. Then, when you switch to file1, &tags will be set to tags file for first project, and when you switch to file2, then &tags will be set back for second project. You should not care about it.\r\n* Background tags generation (thanks to Thiago Bellini for pointing me at needed script). You have not to wait every time while ctags is working.\r\n* By default, on Windows tags generates always for whole project, because of bugs in all Windows versions of Sed i have. Actually, now this isn't problem, because of tags generates in background.\r\n* Tags file is sorted now. In Indexer 2.x it was unsorted because of bugs in Sed, and to make tags unsorted was workaround. As i already said, in Linux Sed works fine, and on Windows Sed doesn't uses by default, so, tags file can be sorted.","3":"* Multiple projects supported. For example, you open file1 from one project, and then you open file2 from second project. Then, when you switch to file1, &tags will be set to tags file for first project, and when you switch to file2, then &tags will be set back for second project. You should not care about it.\r\n* Background tags generation (thanks to Thiago Bellini for pointing me at needed script). You have not to wait every time while ctags is working.\r\n* By default, on Windows tags generates always for whole project, because of bugs in all Windows versions of Sed i have. Actually, now this isn't problem, because of tags generates in background.\r\n* Tags file is sorted now. In Indexer 2.x it was unsorted because of bugs in Sed, and to make tags unsorted was workaround. As i already said, in Linux Sed works fine, and on Windows Sed doesn't uses by default, so, tags file can be sorted.","package":"indexer-3.0.tar.gz","4":"indexer-3.0.tar.gz","src_id":"15235","5":"15235","creation_date":"1300387769","6":"1300387769"},{"0":"3221","vim_version":"7.0","1":"7.0","script_version":"2.01","2":"2.01","version_comment":"The only thing changed is that maximum command length on Windows systems decreased from 8186 to 8000, because of on some systems 8186 is too large, i don't know, why. I hope 8000 will work at all Windows systems (XP or later).\r\nThanks to Dan Price again.","3":"The only thing changed is that maximum command length on Windows systems decreased from 8186 to 8000, because of on some systems 8186 is too large, i don't know, why. I hope 8000 will work at all Windows systems (XP or later).\r\nThanks to Dan Price again.","package":"indexer-2.01.tar.gz","4":"indexer-2.01.tar.gz","src_id":"14270","5":"14270","creation_date":"1289851445","6":"1289851445"},{"0":"3221","vim_version":"7.0","1":"7.0","script_version":"2.0","2":"2.0","version_comment":"IMPORTANT! You need patched version of ctags (5.8.1) to make this version of plugin work correctly, because of bug in ctags 5.8. You can read detailed info about this bug and download pathed version here: http:\/\/dfrank.ru\/ctags581\/en.html \r\n\r\n* Solved trouble with large projects: if there's very many files in your project and command to ctags is too long, then ctags calling several times with \"-a\" key. (Again: to make this work you need patched version of ctags); \r\n* option \"DontSpecifyFilesIfPossible\" working with .vimprojects file too now \r\n* when using append at filesave, old tags removing from tags file by SED. (this is needed to exclude garbage in tags file)\r\nThanks to Dan Price for ideas and inspiration :)","3":"IMPORTANT! You need patched version of ctags (5.8.1) to make this version of plugin work correctly, because of bug in ctags 5.8. You can read detailed info about this bug and download pathed version here: http:\/\/dfrank.ru\/ctags581\/en.html \r\n\r\n* Solved trouble with large projects: if there's very many files in your project and command to ctags is too long, then ctags calling several times with \"-a\" key. (Again: to make this work you need patched version of ctags); \r\n* option \"DontSpecifyFilesIfPossible\" working with .vimprojects file too now \r\n* when using append at filesave, old tags removing from tags file by SED. (this is needed to exclude garbage in tags file)\r\nThanks to Dan Price for ideas and inspiration :)","package":"indexer-2.0.tar.gz","4":"indexer-2.0.tar.gz","src_id":"14234","5":"14234","creation_date":"1289480940","6":"1289480940"},{"0":"3221","vim_version":"7.0","1":"7.0","script_version":"1.8","2":"1.8","version_comment":"* Fixed some bugs (thanks to Julian Kooij)","3":"* Fixed some bugs (thanks to Julian Kooij)","package":"indexer-1.8.tar.gz","4":"indexer-1.8.tar.gz","src_id":"13919","5":"13919","creation_date":"1285492568","6":"1285492568"},{"0":"3221","vim_version":"7.0","1":"7.0","script_version":"1.7","2":"1.7","version_comment":"* Fixed bug that caused not all comments in .vimprojects was parsed correctly (thanks to Alexander Q).\r\n* Fixed some little bugs.","3":"* Fixed bug that caused not all comments in .vimprojects was parsed correctly (thanks to Alexander Q).\r\n* Fixed some little bugs.","package":"indexer-1.7.tar.gz","4":"indexer-1.7.tar.gz","src_id":"13803","5":"13803","creation_date":"1284150330","6":"1284150330"},{"0":"3221","vim_version":"7.0","1":"7.0","script_version":"1.6","2":"1.6","version_comment":"* For every projects creating unique tags file to avoid conflicts (thanks to Torkve)","3":"* For every projects creating unique tags file to avoid conflicts (thanks to Torkve)","package":"indexer-1.6.tar.gz","4":"indexer-1.6.tar.gz","src_id":"13741","5":"13741","creation_date":"1283362592","6":"1283362592"},{"0":"3221","vim_version":"7.0","1":"7.0","script_version":"1.5","2":"1.5","version_comment":"* Fixed bug that caused paths with spaces wasn't parsed correctly. \r\n* Added PROJECTS_PARENT .indexer_files feature (possibility to define directory with many projects inside).","3":"* Fixed bug that caused paths with spaces wasn't parsed correctly. \r\n* Added PROJECTS_PARENT .indexer_files feature (possibility to define directory with many projects inside).","package":"indexer-1.5.tar.gz","4":"indexer-1.5.tar.gz","src_id":"13738","5":"13738","creation_date":"1283284608","6":"1283284608"},{"0":"3221","vim_version":"7.0","1":"7.0","script_version":"1.4","2":"1.4","version_comment":"Fixed bug that caused paths with \"~\" wasn't parsed correctly (thanks Makoto Nokata)","3":"Fixed bug that caused paths with \"~\" wasn't parsed correctly (thanks Makoto Nokata)","package":"indexer-1.4.tar.gz","4":"indexer-1.4.tar.gz","src_id":"13731","5":"13731","creation_date":"1283199310","6":"1283199310"},{"0":"3221","vim_version":"7.0","1":"7.0","script_version":"1.3","2":"1.3","version_comment":"* Fixed some bugs\r\n* Default name of project settings directory has been changed from \".vim\" to \".vimprj\" to avoid conflicts with standard ~\/.vim directory. If you are using this feature and your project settings dir is \".vim\", please rename it.","3":"* Fixed some bugs\r\n* Default name of project settings directory has been changed from \".vim\" to \".vimprj\" to avoid conflicts with standard ~\/.vim directory. If you are using this feature and your project settings dir is \".vim\", please rename it.","package":"indexer-1.3.tar.gz","4":"indexer-1.3.tar.gz","src_id":"13724","5":"13724","creation_date":"1283147718","6":"1283147718"},{"0":"3221","vim_version":"7.0","1":"7.0","script_version":"1.2","2":"1.2","version_comment":"Initial upload","3":"Initial upload","package":"indexer-1.2.tar.gz","4":"indexer-1.2.tar.gz","src_id":"13685","5":"13685","creation_date":"1282851924","6":"1282851924"}]},"3220":{"script_id":"3220","0":"3220","script_name":"Better CSS Syntax for Vim","1":"Better CSS Syntax for Vim","script_type":"syntax","2":"syntax","summary":"Make CSS more readable.","3":"Make CSS more readable.","description":"\r\nSyntax highlights for full CSS2, most of HTML5 & CSS3 properties (include prefix like -moz-).\r\n\r\nPreview:\r\n\r\nMolokai sheme:\r\n\r\nhttps:\/\/img.skitch.com\/20120531-nt3x6qcgkjj7huarpfsh65cmph.jpg\r\n\r\nSlate scheme:\r\n\r\nhttps:\/\/img.skitch.com\/20120531-ju922dsa9u68ib7cbwq27yaygj.jpg\r\n\r\nKnown issue:\r\n\r\n- May not collaborate with some plugins, e.g. CSS Color, Sass\r\n- Some properties can't highlighted well with prefix\r\n- CSS3 animation properties highlighting\r\n\r\nBecause of this plugin is built for standard CSS and not compatible with original css.vim[1], if you run into any error that related to CSS, you may need this:\r\n\r\nSass:\r\n\r\nHow to get rid of the error:\r\n\r\n- edit `sass.vim`, go to line 16, delete `cssValue.*,`\r\n- edit your `.vimrc`, add `au BufRead,BufNewFile *.sass set filetype=css`\r\n\r\nOr, try css3 syntax[2] or vim-css3-syntax[3].\r\n\r\n----\r\n\r\n[1] https:\/\/github.com\/ChrisYip\/Better-CSS-Syntax-for-Vim\/issues\/9#issuecomment-6034606\r\n[2] http:\/\/www.vim.org\/scripts\/script.php?script_id=3042\r\n[3] https:\/\/github.com\/hail2u\/vim-css3-syntax","4":"\r\nSyntax highlights for full CSS2, most of HTML5 & CSS3 properties (include prefix like -moz-).\r\n\r\nPreview:\r\n\r\nMolokai sheme:\r\n\r\nhttps:\/\/img.skitch.com\/20120531-nt3x6qcgkjj7huarpfsh65cmph.jpg\r\n\r\nSlate scheme:\r\n\r\nhttps:\/\/img.skitch.com\/20120531-ju922dsa9u68ib7cbwq27yaygj.jpg\r\n\r\nKnown issue:\r\n\r\n- May not collaborate with some plugins, e.g. CSS Color, Sass\r\n- Some properties can't highlighted well with prefix\r\n- CSS3 animation properties highlighting\r\n\r\nBecause of this plugin is built for standard CSS and not compatible with original css.vim[1], if you run into any error that related to CSS, you may need this:\r\n\r\nSass:\r\n\r\nHow to get rid of the error:\r\n\r\n- edit `sass.vim`, go to line 16, delete `cssValue.*,`\r\n- edit your `.vimrc`, add `au BufRead,BufNewFile *.sass set filetype=css`\r\n\r\nOr, try css3 syntax[2] or vim-css3-syntax[3].\r\n\r\n----\r\n\r\n[1] https:\/\/github.com\/ChrisYip\/Better-CSS-Syntax-for-Vim\/issues\/9#issuecomment-6034606\r\n[2] http:\/\/www.vim.org\/scripts\/script.php?script_id=3042\r\n[3] https:\/\/github.com\/hail2u\/vim-css3-syntax","install_details":"Copy css.vim to your ~\/.vim\/Syntax.","5":"Copy css.vim to your ~\/.vim\/Syntax.","first_name":"Chris","6":"Chris","last_name":"Yip","7":"Yip","releases":[{"0":"3220","vim_version":"7.0","1":"7.0","script_version":"2012\/5\/29","2":"2012\/5\/29","version_comment":"Change log is here: https:\/\/github.com\/ChrisYip\/Better-CSS-Syntax-for-Vim\/commits\/master","3":"Change log is here: https:\/\/github.com\/ChrisYip\/Better-CSS-Syntax-for-Vim\/commits\/master","package":"css.vim.zip","4":"css.vim.zip","src_id":"18055","5":"18055","creation_date":"1338234898","6":"1338234898"},{"0":"3220","vim_version":"7.0","1":"7.0","script_version":"20110302","2":"20110302","version_comment":"1. Improved @import, @media, rotate(), rgba() highlights; \r\n2. Bug fixing.","3":"1. Improved @import, @media, rotate(), rgba() highlights; \r\n2. Bug fixing.","package":"css.vim.zip","4":"css.vim.zip","src_id":"15146","5":"15146","creation_date":"1299080463","6":"1299080463"},{"0":"3220","vim_version":"7.0","1":"7.0","script_version":"20100827","2":"20100827","version_comment":"Initial upload","3":"Initial upload","package":"css.vim","4":"css.vim","src_id":"13684","5":"13684","creation_date":"1282847611","6":"1282847611"}]},"3219":{"script_id":"3219","0":"3219","script_name":"ProjectTag","1":"ProjectTag","script_type":"utility","2":"utility","summary":"This plugin is aimed at generating tags for a whole project.","3":"This plugin is aimed at generating tags for a whole project.","description":"This plugin is aimed at generating tags for a whole project. \r\nExuberant Ctags is required for this plugin:\r\nhttp:\/\/ctags.sourceforge.net\/\r\nThis plugin is quite useful when used with omnicomplete plugins, such as \r\nOmniCppComplete(vimscript #1520), \r\npythoncomplete(vimscript #1542), \r\njavacomplete(vimscript #1785).\r\nvim must be compiled with python support for this plugin to run. At least\r\npython 2.4 is required. Python 3.x is not supported currently.\r\n\r\nFor C\/C++ projects, there's no need to generate a seperate tag file for the\r\nincluded header files any more! This plugin will also parses the header files\r\ncited in your source code, so a tag file providing information of all sources\r\nfiles in your project and header files included in your sources would be\r\ngenerated. \r\n\r\nThis plugin could also generate tags in background by using python \r\nmultithread library, so your editing work would not be blocked when \r\ngenerating tag files.\r\n\r\n\r\nThe following is a short tutorial.\r\n\r\nFirst, enter your project root directory, for example \/home\/user\/myproject.\r\nThen create a project file, the file name must be \"project.prom\". Edit this\r\nfile. Copy the following content to this file:\r\n=========\r\n[general]\r\nsources=source1,source2,...\r\ninclude_dirs=include_dir1,include_dir2,...\r\ntagprog=ctags_command\r\ntagflag=--your-tag-flags\r\n=========\r\n\r\nReplace source1,source2,... with your source file, such as main.c,\r\nsrc\/foo.cpp;\r\n\r\nreplace include_dir1,include_dir2,... with your include directories, such as\r\n\/usr\/include, \/usr\/local\/include (not required for non C\/C++ project, in fact,\r\neven for C\/C++ project, it is also optional);\r\n\r\nreplace ctags_command with your ctags command, such as ctags, \/usr\/bin\/ctags;\r\n\r\nreplace --your-tag-flags with your tag flags, such as --extra=+q.\r\n\r\n\r\nFor example, for the following source tree:\r\n\r\n- src\/\r\n  main.cpp\r\n  foo.cpp\r\n  bar.cpp\r\n- include\/\r\n  foo.h\r\n  bar.h\r\n\r\nThe project file could be like the following:\r\n=========\r\n[general]\r\nsources=src\/main.cpp, src\/foo.cpp, src\/bar.cpp\r\ninclude_dirs=.\/include,\/usr\/include\r\ntagprog=ctags\r\ntagflag=--extra=+q --c++-kinds=+p --fields=+iaS \r\n=========\r\n              \r\nThen save the file.\r\n\r\nUse vim to open a source file, such as foo.cpp. Use the command\r\n\":GenProTags\" to generate the tag file(this might be some kind of slow). if\r\nyou don't want to be blocked when generating the tag file, use \":GenProTagsBg\"\r\ninstead. This will generate the tag file in background.\r\n\r\nMake sure that your project path does not contain spaces, or it wouldn't work.\r\n\r\n\r\nIf you find any bug, please report it to hong@topbug.net, or submit it on the\r\nissue tracker: \r\nhttps:\/\/bitbucket.org\/xuhdev\/projecttag\/issues\r\n\r\nRepository: \r\nhttps:\/\/bitbucket.org\/xuhdev\/projecttag\r\n\r\nFollow xuhdev on twitter if you are interested in my development:\r\nhttp:\/\/twitter.com\/xuhdev\r\n\r\n\r\nIf you are working on a UNIX-like system, There is also an alternative way to generate a ctags file for your C\/C++ source files and their included header files:\r\n\r\nhttp:\/\/dev.hongxu.me\/blog\/2012\/03\/17\/generate-ctags-files-for-c-slash-c-plus-plus-source-files-and-all-of-their-included-header-files\/","4":"This plugin is aimed at generating tags for a whole project. \r\nExuberant Ctags is required for this plugin:\r\nhttp:\/\/ctags.sourceforge.net\/\r\nThis plugin is quite useful when used with omnicomplete plugins, such as \r\nOmniCppComplete(vimscript #1520), \r\npythoncomplete(vimscript #1542), \r\njavacomplete(vimscript #1785).\r\nvim must be compiled with python support for this plugin to run. At least\r\npython 2.4 is required. Python 3.x is not supported currently.\r\n\r\nFor C\/C++ projects, there's no need to generate a seperate tag file for the\r\nincluded header files any more! This plugin will also parses the header files\r\ncited in your source code, so a tag file providing information of all sources\r\nfiles in your project and header files included in your sources would be\r\ngenerated. \r\n\r\nThis plugin could also generate tags in background by using python \r\nmultithread library, so your editing work would not be blocked when \r\ngenerating tag files.\r\n\r\n\r\nThe following is a short tutorial.\r\n\r\nFirst, enter your project root directory, for example \/home\/user\/myproject.\r\nThen create a project file, the file name must be \"project.prom\". Edit this\r\nfile. Copy the following content to this file:\r\n=========\r\n[general]\r\nsources=source1,source2,...\r\ninclude_dirs=include_dir1,include_dir2,...\r\ntagprog=ctags_command\r\ntagflag=--your-tag-flags\r\n=========\r\n\r\nReplace source1,source2,... with your source file, such as main.c,\r\nsrc\/foo.cpp;\r\n\r\nreplace include_dir1,include_dir2,... with your include directories, such as\r\n\/usr\/include, \/usr\/local\/include (not required for non C\/C++ project, in fact,\r\neven for C\/C++ project, it is also optional);\r\n\r\nreplace ctags_command with your ctags command, such as ctags, \/usr\/bin\/ctags;\r\n\r\nreplace --your-tag-flags with your tag flags, such as --extra=+q.\r\n\r\n\r\nFor example, for the following source tree:\r\n\r\n- src\/\r\n  main.cpp\r\n  foo.cpp\r\n  bar.cpp\r\n- include\/\r\n  foo.h\r\n  bar.h\r\n\r\nThe project file could be like the following:\r\n=========\r\n[general]\r\nsources=src\/main.cpp, src\/foo.cpp, src\/bar.cpp\r\ninclude_dirs=.\/include,\/usr\/include\r\ntagprog=ctags\r\ntagflag=--extra=+q --c++-kinds=+p --fields=+iaS \r\n=========\r\n              \r\nThen save the file.\r\n\r\nUse vim to open a source file, such as foo.cpp. Use the command\r\n\":GenProTags\" to generate the tag file(this might be some kind of slow). if\r\nyou don't want to be blocked when generating the tag file, use \":GenProTagsBg\"\r\ninstead. This will generate the tag file in background.\r\n\r\nMake sure that your project path does not contain spaces, or it wouldn't work.\r\n\r\n\r\nIf you find any bug, please report it to hong@topbug.net, or submit it on the\r\nissue tracker: \r\nhttps:\/\/bitbucket.org\/xuhdev\/projecttag\/issues\r\n\r\nRepository: \r\nhttps:\/\/bitbucket.org\/xuhdev\/projecttag\r\n\r\nFollow xuhdev on twitter if you are interested in my development:\r\nhttp:\/\/twitter.com\/xuhdev\r\n\r\n\r\nIf you are working on a UNIX-like system, There is also an alternative way to generate a ctags file for your C\/C++ source files and their included header files:\r\n\r\nhttp:\/\/dev.hongxu.me\/blog\/2012\/03\/17\/generate-ctags-files-for-c-slash-c-plus-plus-source-files-and-all-of-their-included-header-files\/","install_details":"Download the ProjectTag.zip file and extract it to your vim runtime\r\ndirectory(~\/.vim on linux and $VIM_INSTALLATION_FOLDER\\vimfiles on\r\nwindows), you'd better then use helptags command to generate the help\r\ntag(for example use \":helptags ~\/.vim\/doc\" on Linux).\r\n","5":"Download the ProjectTag.zip file and extract it to your vim runtime\r\ndirectory(~\/.vim on linux and $VIM_INSTALLATION_FOLDER\\vimfiles on\r\nwindows), you'd better then use helptags command to generate the help\r\ntag(for example use \":helptags ~\/.vim\/doc\" on Linux).\r\n","first_name":"Hong","6":"Hong","last_name":"Xu","7":"Xu","releases":[{"0":"3219","vim_version":"7.0","1":"7.0","script_version":"0.1.10","2":"0.1.10","version_comment":"Also handle the situation when ctags doesn't return 0;\r\nImprove the error messages.","3":"Also handle the situation when ctags doesn't return 0;\r\nImprove the error messages.","package":"ProjectTag.zip","4":"ProjectTag.zip","src_id":"14944","5":"14944","creation_date":"1296730655","6":"1296730655"},{"0":"3219","vim_version":"7.2","1":"7.2","script_version":"0.1.9","2":"0.1.9","version_comment":"Also recognize this kind of include: \"# include\",\"#\\tinclude\",etc;\r\nmove ProjectTag.py from ProjectTag\/ to plugin\/ProjectTag\/, so please delete the \"ProjectTag\" directory in the old version if you are upgrading.\r\n","3":"Also recognize this kind of include: \"# include\",\"#\\tinclude\",etc;\r\nmove ProjectTag.py from ProjectTag\/ to plugin\/ProjectTag\/, so please delete the \"ProjectTag\" directory in the old version if you are upgrading.\r\n","package":"ProjectTag.zip","4":"ProjectTag.zip","src_id":"14439","5":"14439","creation_date":"1291522573","6":"1291522573"},{"0":"3219","vim_version":"7.2","1":"7.2","script_version":"0.1.8","2":"0.1.8","version_comment":"Fix a vim 'tags' setting problem. Convert the document file format to unix format.","3":"Fix a vim 'tags' setting problem. Convert the document file format to unix format.","package":"ProjectTag.zip","4":"ProjectTag.zip","src_id":"14402","5":"14402","creation_date":"1291104123","6":"1291104123"},{"0":"3219","vim_version":"7.2","1":"7.2","script_version":"0.1.7","2":"0.1.7","version_comment":"fix a minor document bug.","3":"fix a minor document bug.","package":"ProjectTag.zip","4":"ProjectTag.zip","src_id":"14380","5":"14380","creation_date":"1290775453","6":"1290775453"},{"0":"3219","vim_version":"7.0","1":"7.0","script_version":"0.1.6","2":"0.1.6","version_comment":"Fix a bug when \"sources\" contain some non-exist files.","3":"Fix a bug when \"sources\" contain some non-exist files.","package":"ProjectTag.zip","4":"ProjectTag.zip","src_id":"14358","5":"14358","creation_date":"1290494183","6":"1290494183"},{"0":"3219","vim_version":"7.0","1":"7.0","script_version":"0.1.5","2":"0.1.5","version_comment":"fix a minor bug: if current working directory is not where current file locates, this plugin would not work properly.","3":"fix a minor bug: if current working directory is not where current file locates, this plugin would not work properly.","package":"ProjectTag.zip","4":"ProjectTag.zip","src_id":"13891","5":"13891","creation_date":"1285219114","6":"1285219114"},{"0":"3219","vim_version":"7.0","1":"7.0","script_version":"0.1.4","2":"0.1.4","version_comment":"Improve the performance.","3":"Improve the performance.","package":"ProjectTag.zip","4":"ProjectTag.zip","src_id":"13883","5":"13883","creation_date":"1285140795","6":"1285140795"},{"0":"3219","vim_version":"7.0","1":"7.0","script_version":"0.1.3","2":"0.1.3","version_comment":"Don't enable this plugin when required python packages are not found. Improve the document.","3":"Don't enable this plugin when required python packages are not found. Improve the document.","package":"ProjectTag.zip","4":"ProjectTag.zip","src_id":"13754","5":"13754","creation_date":"1283533649","6":"1283533649"},{"0":"3219","vim_version":"7.0","1":"7.0","script_version":"0.1.2","2":"0.1.2","version_comment":"Don't generate tags if project not found, add GetLatestScript support.","3":"Don't generate tags if project not found, add GetLatestScript support.","package":"ProjectTag.zip","4":"ProjectTag.zip","src_id":"13699","5":"13699","creation_date":"1282974446","6":"1282974446"},{"0":"3219","vim_version":"7.0","1":"7.0","script_version":"0.1.1","2":"0.1.1","version_comment":"When searching for header files, also search for the header files in the same directory with the source file.","3":"When searching for header files, also search for the header files in the same directory with the source file.","package":"ProjectTag.zip","4":"ProjectTag.zip","src_id":"13687","5":"13687","creation_date":"1282879639","6":"1282879639"},{"0":"3219","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"ProjectTag.zip","4":"ProjectTag.zip","src_id":"13682","5":"13682","creation_date":"1282831817","6":"1282831817"}]},"3218":{"script_id":"3218","0":"3218","script_name":"processing snipmate","1":"processing snipmate","script_type":"utility","2":"utility","summary":"A port of the Textmate bundle to work with processing pde files","3":"A port of the Textmate bundle to work with processing pde files","description":"Port of the original bundle for textmate to work with pde files (processing). Use with snipMate. \r\n\r\npls, use my http:\/\/github.com\/tcha-tcho to contact me about this code      :)\r\n\r\nthankyou all","4":"Port of the original bundle for textmate to work with pde files (processing). Use with snipMate. \r\n\r\npls, use my http:\/\/github.com\/tcha-tcho to contact me about this code      :)\r\n\r\nthankyou all","install_details":"put this file with the others snippets files inside of snipMate plugin directory","5":"put this file with the others snippets files inside of snipMate plugin directory","first_name":"Eduardo","6":"Eduardo","last_name":"Malpeli","7":"Malpeli","releases":[{"0":"3218","vim_version":"7.0","1":"7.0","script_version":"6.1","2":"6.1","version_comment":"some fixing in the sintaxe","3":"some fixing in the sintaxe","package":"processing.snippets","4":"processing.snippets","src_id":"13723","5":"13723","creation_date":"1283147248","6":"1283147248"},{"0":"3218","vim_version":"7.0","1":"7.0","script_version":"6.0","2":"6.0","version_comment":"Initial upload","3":"Initial upload","package":"processing.snippets","4":"processing.snippets","src_id":"13676","5":"13676","creation_date":"1282783357","6":"1282783357"}]},"3217":{"script_id":"3217","0":"3217","script_name":"qnamebuf","1":"qnamebuf","script_type":"utility","2":"utility","summary":"QuickNameBuf: A quick general manager","3":"QuickNameBuf: A quick general manager","description":"I really like qname (vimscript #2317) and qbuf (vimscript #1910) and decided that it would be nice to combine them.  The author recommended I upload under my name.\r\n\r\nVersion 0.07 introduced a redesign, there are three files:\r\n1) qnamepicker: A core that provides a generic function other scripts can call to allow the user to select an item from a list in the command prompt (in a lusty fashion).\r\n2) qnamefile: Like command-t but in mostly pure vim (there is a requirement on the find utility).\r\n3) qnamebuf: The classic buffer selector as before.\r\nand there was a significant speedup by replacing a custom matcher function with a regular expression.\r\n\r\nAlso in the documentation for qnamepicker I show how one can utilize the script for the project (vimscript #69) to provide a lusty selector for the files in the project (complete with the shortcuts below!).  I have found this to be a life-changing combination ;-).\r\n\r\nqnamebuf Usage:\r\n<F4> opens a list of the current buffers, and typing a string filters the list (by default ala lustyexplorer vimscript #1890).  All filtering is case insensitive (even if using Regular Expressions).  If there are many files open goes to a simplified view (just relative buffer number, and the filename with path), when filtered enough shows more information:\r\n    1) Relative Buffer Number\r\n    2) Current Buffer (%), Alternative Buffer (#), or if it is open in a visible split (=)\r\n    3) File name\r\n    4) Buffer number\r\n    5) Relative file path\r\n\r\nIn addition to the common commands below, qnamebuf accepts:\r\n    <M-L> Toggle between listed and unlisted buffers\r\n    <M-D> bdelete the selected buffer, the explorer stays open and retains cursor position\r\n    <M-C> Close the window containing the buffer\r\n    <F4>    Close the qnamebuf explorer\r\n\r\nqnamefile Usage:\r\n<S-F4> opens an explorer from the current working directory showing all files which are not in a hidden directory (one that starts with '.').  This script relies on the external find utility.\r\n\r\nCommon shortcuts to qnamefile and qnamebuf:\r\n    <BS> Delete last char entered\r\n    <C-U> Delete all entered chars\r\n    <ESC> or <C-G> close the explorer\r\n    <CR> Open the selected file in the current window\r\n    <M-S> Open the selected file in a split window\r\n    <M-V> Open the selected file in a vert split window\r\n    <M-T> Open the selected file in a new tab\r\n    <UP> <DOWN> <LEFT> <RIGHT> navigates the selection\r\n    <HOME> <END> move to the first\/last item\r\n    <M-1>, ..., <M-0> open the first, ..., tenth file in the list\r\n\r\nNote, I wanted these to be <C-...> but <C-1>...<C-0> are not real key sequences.\r\n\r\nqnamepicker Usage:\r\nSee the documentation for a detailed description of how to call the function, and examples.  Essentially provides a function:\r\n    QNamePickerStart(list, dict)\r\nwhere a:list is the set of items, and a:dict provides a mechanism to customize various parts (e.g. rendering, extra keys for various actions, etcetera).\r\n\r\nCustomization:\r\nqnamebuf and qnamefile can be customized (in slightly different manners).  See the documentation for details on these.\r\n\r\nHints:\r\nI find the following mappings very useful (jump to the ith file):\r\n    nmap <silent> <M-1> :brewind<CR>\r\n    nmap <silent> <M-2> :brewind \\| 1bn<CR>\r\n    nmap <silent> <M-3> :brewind \\| 2bn<CR>\r\n    nmap <silent> <M-4> :brewind \\| 3bn<CR>\r\n    nmap <silent> <M-5> :brewind \\| 4bn<CR>\r\n    nmap <silent> <M-6> :brewind \\| 5bn<CR>\r\n    nmap <silent> <M-7> :brewind \\| 6bn<CR>\r\n    nmap <silent> <M-8> :brewind \\| 7bn<CR>\r\n    nmap <silent> <M-9> :brewind \\| 8bn<CR>\r\n    nmap <silent> <M-0> :brewind \\| 9bn<CR>\r\nWhen starting qnamebuf the numbers are displayed and this allows consistent access.\r\n\r\nAlso be sure to check the hints section of qnamepicker's documentation for some code to add to .vimproject_mappings to provide a lusty picker for the files in a project (it is slightly too long to be useful here)!","4":"I really like qname (vimscript #2317) and qbuf (vimscript #1910) and decided that it would be nice to combine them.  The author recommended I upload under my name.\r\n\r\nVersion 0.07 introduced a redesign, there are three files:\r\n1) qnamepicker: A core that provides a generic function other scripts can call to allow the user to select an item from a list in the command prompt (in a lusty fashion).\r\n2) qnamefile: Like command-t but in mostly pure vim (there is a requirement on the find utility).\r\n3) qnamebuf: The classic buffer selector as before.\r\nand there was a significant speedup by replacing a custom matcher function with a regular expression.\r\n\r\nAlso in the documentation for qnamepicker I show how one can utilize the script for the project (vimscript #69) to provide a lusty selector for the files in the project (complete with the shortcuts below!).  I have found this to be a life-changing combination ;-).\r\n\r\nqnamebuf Usage:\r\n<F4> opens a list of the current buffers, and typing a string filters the list (by default ala lustyexplorer vimscript #1890).  All filtering is case insensitive (even if using Regular Expressions).  If there are many files open goes to a simplified view (just relative buffer number, and the filename with path), when filtered enough shows more information:\r\n    1) Relative Buffer Number\r\n    2) Current Buffer (%), Alternative Buffer (#), or if it is open in a visible split (=)\r\n    3) File name\r\n    4) Buffer number\r\n    5) Relative file path\r\n\r\nIn addition to the common commands below, qnamebuf accepts:\r\n    <M-L> Toggle between listed and unlisted buffers\r\n    <M-D> bdelete the selected buffer, the explorer stays open and retains cursor position\r\n    <M-C> Close the window containing the buffer\r\n    <F4>    Close the qnamebuf explorer\r\n\r\nqnamefile Usage:\r\n<S-F4> opens an explorer from the current working directory showing all files which are not in a hidden directory (one that starts with '.').  This script relies on the external find utility.\r\n\r\nCommon shortcuts to qnamefile and qnamebuf:\r\n    <BS> Delete last char entered\r\n    <C-U> Delete all entered chars\r\n    <ESC> or <C-G> close the explorer\r\n    <CR> Open the selected file in the current window\r\n    <M-S> Open the selected file in a split window\r\n    <M-V> Open the selected file in a vert split window\r\n    <M-T> Open the selected file in a new tab\r\n    <UP> <DOWN> <LEFT> <RIGHT> navigates the selection\r\n    <HOME> <END> move to the first\/last item\r\n    <M-1>, ..., <M-0> open the first, ..., tenth file in the list\r\n\r\nNote, I wanted these to be <C-...> but <C-1>...<C-0> are not real key sequences.\r\n\r\nqnamepicker Usage:\r\nSee the documentation for a detailed description of how to call the function, and examples.  Essentially provides a function:\r\n    QNamePickerStart(list, dict)\r\nwhere a:list is the set of items, and a:dict provides a mechanism to customize various parts (e.g. rendering, extra keys for various actions, etcetera).\r\n\r\nCustomization:\r\nqnamebuf and qnamefile can be customized (in slightly different manners).  See the documentation for details on these.\r\n\r\nHints:\r\nI find the following mappings very useful (jump to the ith file):\r\n    nmap <silent> <M-1> :brewind<CR>\r\n    nmap <silent> <M-2> :brewind \\| 1bn<CR>\r\n    nmap <silent> <M-3> :brewind \\| 2bn<CR>\r\n    nmap <silent> <M-4> :brewind \\| 3bn<CR>\r\n    nmap <silent> <M-5> :brewind \\| 4bn<CR>\r\n    nmap <silent> <M-6> :brewind \\| 5bn<CR>\r\n    nmap <silent> <M-7> :brewind \\| 6bn<CR>\r\n    nmap <silent> <M-8> :brewind \\| 7bn<CR>\r\n    nmap <silent> <M-9> :brewind \\| 8bn<CR>\r\n    nmap <silent> <M-0> :brewind \\| 9bn<CR>\r\nWhen starting qnamebuf the numbers are displayed and this allows consistent access.\r\n\r\nAlso be sure to check the hints section of qnamepicker's documentation for some code to add to .vimproject_mappings to provide a lusty picker for the files in a project (it is slightly too long to be useful here)!","install_details":"Extract $HOME\/.vim\/","5":"Extract $HOME\/.vim\/","first_name":"Matt","6":"Matt","last_name":"Spear","7":"Spear","releases":[{"0":"3217","vim_version":"7.0","1":"7.0","script_version":"0.08","2":"0.08","version_comment":"Minor changes:\r\n* History feature added\r\n* ignore_case option added\r\n* Change the prompt to show the current regexp versus fuzzy maching\r\n* C-R to change between regexp and fuzzy matching\r\n* M-P to do path matching in qnamefile","3":"Minor changes:\r\n* History feature added\r\n* ignore_case option added\r\n* Change the prompt to show the current regexp versus fuzzy maching\r\n* C-R to change between regexp and fuzzy matching\r\n* M-P to do path matching in qnamefile","package":"qnamebuf.zip","4":"qnamebuf.zip","src_id":"21101","5":"21101","creation_date":"1385359225","6":"1385359225"},{"0":"3217","vim_version":"7.0","1":"7.0","script_version":"0.07","2":"0.07","version_comment":"Complete redesign, now has a flexible core that scripts can plug into to get a lusty picker.","3":"Complete redesign, now has a flexible core that scripts can plug into to get a lusty picker.","package":"qnamebuf.zip","4":"qnamebuf.zip","src_id":"15680","5":"15680","creation_date":"1305859866","6":"1305859866"},{"0":"3217","vim_version":"7.0","1":"7.0","script_version":"0.05","2":"0.05","version_comment":"Fixed a bug which would cause operations to fail on a filtered list.","3":"Fixed a bug which would cause operations to fail on a filtered list.","package":"qnamebuf.zip","4":"qnamebuf.zip","src_id":"14921","5":"14921","creation_date":"1296442283","6":"1296442283"},{"0":"3217","vim_version":"7.0","1":"7.0","script_version":"0.04","2":"0.04","version_comment":"Fixed overwriting the @y register.  Made the cmap silent.  Thanks to Peter for the patch!","3":"Fixed overwriting the @y register.  Made the cmap silent.  Thanks to Peter for the patch!","package":"qnamebuf.zip","4":"qnamebuf.zip","src_id":"14554","5":"14554","creation_date":"1292650825","6":"1292650825"},{"0":"3217","vim_version":"7.0","1":"7.0","script_version":"0.03","2":"0.03","version_comment":"Made a mistake to always define the mapping for QNameBufInit even if a mapping to it existed.","3":"Made a mistake to always define the mapping for QNameBufInit even if a mapping to it existed.","package":"qnamebuf.zip","4":"qnamebuf.zip","src_id":"14542","5":"14542","creation_date":"1292568151","6":"1292568151"},{"0":"3217","vim_version":"7.0","1":"7.0","script_version":"0.02","2":"0.02","version_comment":"Added support for <LEADER>X being a synonym for <M-X>.  Some minor code cleanup.","3":"Added support for <LEADER>X being a synonym for <M-X>.  Some minor code cleanup.","package":"qnamebuf.zip","4":"qnamebuf.zip","src_id":"14541","5":"14541","creation_date":"1292566601","6":"1292566601"},{"0":"3217","vim_version":"7.0","1":"7.0","script_version":"0.01","2":"0.01","version_comment":"Initial upload","3":"Initial upload","package":"qnamebuf.vim","4":"qnamebuf.vim","src_id":"13659","5":"13659","creation_date":"1282621586","6":"1282621586"}]},"3216":{"script_id":"3216","0":"3216","script_name":"Replay.vim","1":"Replay.vim","script_type":"utility","2":"utility","summary":"Record and Replay your editing Session","3":"Record and Replay your editing Session","description":"Feedback is welcome. Please rate this plugin, if you like it.\r\n\r\nThis plugin does not cope with recording and replaying macros, rather it steps though your undo tree so you can see, \r\nwhat changes have been done, since starting editing. It also allows to simply screen record a Vim session using ffmpeg\/avconv so you can easily share with others how to work with Vim.\r\n\r\nUse :StartRecording \"tag\" to start recording from the current change on and save it under the name \"tag\"\r\nUse :StopRecording \"tag\" to let the Recording for \"tag\" end at this change.\r\nUse :Replay \"tag\" to Replay your changes.\r\n\r\nYou can usually leave tagname out and Replay.vim will record your changes under the name \"Default\".\r\nSee :h Replay.txt to read the help\r\n\r\nThis Plugin is also available at github: http:\/\/github.com\/chrisbra\/Replay","4":"Feedback is welcome. Please rate this plugin, if you like it.\r\n\r\nThis plugin does not cope with recording and replaying macros, rather it steps though your undo tree so you can see, \r\nwhat changes have been done, since starting editing. It also allows to simply screen record a Vim session using ffmpeg\/avconv so you can easily share with others how to work with Vim.\r\n\r\nUse :StartRecording \"tag\" to start recording from the current change on and save it under the name \"tag\"\r\nUse :StopRecording \"tag\" to let the Recording for \"tag\" end at this change.\r\nUse :Replay \"tag\" to Replay your changes.\r\n\r\nYou can usually leave tagname out and Replay.vim will record your changes under the name \"Default\".\r\nSee :h Replay.txt to read the help\r\n\r\nThis Plugin is also available at github: http:\/\/github.com\/chrisbra\/Replay","install_details":"as usual. Open the file in vim, and source it (:so %)","5":"as usual. Open the file in vim, and source it (:so %)","first_name":"Christian","6":"Christian","last_name":"Brabandt","7":"Brabandt","releases":[{"0":"3216","vim_version":"7.3","1":"7.3","script_version":"5","2":"5","version_comment":"- improvements for |:ScreenCapture| capture\n(automatically uploaded)","3":"- improvements for |:ScreenCapture| capture\n(automatically uploaded)","package":"Replay-0.5.vmb","4":"Replay-0.5.vmb","src_id":"20649","5":"20649","creation_date":"1376512014","6":"1376512014"},{"0":"3216","vim_version":"7.3","1":"7.3","script_version":"4","2":"4","version_comment":"- disable folding\n- enable to screenrecord the replay using ffmpeg\/avconv (fixes https:\/\/github.com\/chrisbra\/Replay\/issues\/1, suggested by David Jacobs, thanks!)\n(automatically uploaded)","3":"- disable folding\n- enable to screenrecord the replay using ffmpeg\/avconv (fixes https:\/\/github.com\/chrisbra\/Replay\/issues\/1, suggested by David Jacobs, thanks!)\n(automatically uploaded)","package":"Replay-0.4.vmb","4":"Replay-0.4.vmb","src_id":"19576","5":"19576","creation_date":"1362001943","6":"1362001943"},{"0":"3216","vim_version":"7.2","1":"7.2","script_version":"0.3","2":"0.3","version_comment":"- Automatically stopp Recording for latest started Recording session  (suggested by Salim Halim, thanks!)\r\n- Changed recording of time to use localtime() instead of storing a string \r\n- Better documentation for :ListRecordings\r\n- ListRecordings now also displays the change number (so you can easily jump to a change using :undo)","3":"- Automatically stopp Recording for latest started Recording session  (suggested by Salim Halim, thanks!)\r\n- Changed recording of time to use localtime() instead of storing a string \r\n- Better documentation for :ListRecordings\r\n- ListRecordings now also displays the change number (so you can easily jump to a change using :undo)","package":"Replay-0.3.vba","4":"Replay-0.3.vba","src_id":"13690","5":"13690","creation_date":"1282911594","6":"1282911594"},{"0":"3216","vim_version":"7.2","1":"7.2","script_version":"0.2","2":"0.2","version_comment":"-enabled |GLVS|\n-small bugfixes\n-changed default playback rate to 200ms\n-make sure start is after stop","3":"-enabled |GLVS|\n-small bugfixes\n-changed default playback rate to 200ms\n-make sure start is after stop","package":"Replay-0.2.vba","4":"Replay-0.2.vba","src_id":"13662","5":"13662","creation_date":"1282651282","6":"1282651282"},{"0":"3216","vim_version":"7.2","1":"7.2","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"Replay-0.1.vba","4":"Replay-0.1.vba","src_id":"13658","5":"13658","creation_date":"1282592020","6":"1282592020"}]},"3215":{"script_id":"3215","0":"3215","script_name":"View Ports","1":"View Ports","script_type":"utility","2":"utility","summary":"Change tab title in terminal version of Vim","3":"Change tab title in terminal version of Vim","description":"Basic script to name your Vim tabs the way you want.\r\n\r\nMore tab operations is planned, but for now that's all.","4":"Basic script to name your Vim tabs the way you want.\r\n\r\nMore tab operations is planned, but for now that's all.","install_details":"Just open the viewports.vba in Vim and issue :so % command.","5":"Just open the viewports.vba in Vim and issue :so % command.","first_name":"Victor","6":"Victor","last_name":"Farazdagi","7":"Farazdagi","releases":[{"0":"3215","vim_version":"7.0","1":"7.0","script_version":"0.9","2":"0.9","version_comment":"Initial upload","3":"Initial upload","package":"viewports.vba","4":"viewports.vba","src_id":"13636","5":"13636","creation_date":"1282322579","6":"1282322579"}]},"3214":{"script_id":"3214","0":"3214","script_name":"presets","1":"presets","script_type":"utility","2":"utility","summary":"Quickly switch between vim configurations","3":"Quickly switch between vim configurations","description":"This plugins allows users to push presets (sets of |options|) onto a \r\nconfiguration stack and remove them later on, i.e., it allows users to \r\nquickly switch between pre-defined configurations (e.g. GUI-related \r\noptions).\r\n\r\nIn order to push a preset, use the |:Preset| command:\r\n\r\n    :Preset! NAME\r\n\r\nFull docs:\r\nhttp:\/\/github.com\/tomtom\/presets_vim\/blob\/master\/doc\/presets.txt","4":"This plugins allows users to push presets (sets of |options|) onto a \r\nconfiguration stack and remove them later on, i.e., it allows users to \r\nquickly switch between pre-defined configurations (e.g. GUI-related \r\noptions).\r\n\r\nIn order to push a preset, use the |:Preset| command:\r\n\r\n    :Preset! NAME\r\n\r\nFull docs:\r\nhttp:\/\/github.com\/tomtom\/presets_vim\/blob\/master\/doc\/presets.txt","install_details":"Edit the vba file and type: >\r\n\r\n    :so %\r\n\r\nSee :help vimball for details.\r\n\r\n\r\nPost-Install~\r\n\r\nCheck the values of the following variables and set them in your |vimrc| \r\nfile if necessary:\r\n\r\n    - |g:presets#font|\r\n    - |g:presets#font_sizes|\r\n\r\nAlso available via git\r\nhttp:\/\/github.com\/tomtom\/presets_vim","5":"Edit the vba file and type: >\r\n\r\n    :so %\r\n\r\nSee :help vimball for details.\r\n\r\n\r\nPost-Install~\r\n\r\nCheck the values of the following variables and set them in your |vimrc| \r\nfile if necessary:\r\n\r\n    - |g:presets#font|\r\n    - |g:presets#font_sizes|\r\n\r\nAlso available via git\r\nhttp:\/\/github.com\/tomtom\/presets_vim","first_name":"Tom","6":"Tom","last_name":"Link","7":"Link","releases":[{"0":"3214","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"presets.vba","4":"presets.vba","src_id":"13635","5":"13635","creation_date":"1282322560","6":"1282322560"}]},"3213":{"script_id":"3213","0":"3213","script_name":"rslTools","1":"rslTools","script_type":"ftplugin","2":"ftplugin","summary":"A tool set for renderman shading language developers","3":"A tool set for renderman shading language developers","description":"RSL Vim tools are a set of Vim commands that help people to write, compile and render their RSL shaders in one place. Usually at the time of shader writing, switching between different applications to compile and render the shader is very time consuming. These scripts intgrate all of these steps and using them, developer can manage his\\her time more efficiently. It is customizable and support different renderman implementations.","4":"RSL Vim tools are a set of Vim commands that help people to write, compile and render their RSL shaders in one place. Usually at the time of shader writing, switching between different applications to compile and render the shader is very time consuming. These scripts intgrate all of these steps and using them, developer can manage his\\her time more efficiently. It is customizable and support different renderman implementations.","install_details":"Extract the package in $VIMRUNTIME folder and overwrite","5":"Extract the package in $VIMRUNTIME folder and overwrite","first_name":"mostafa","6":"mostafa","last_name":"ari","7":"ari","releases":[{"0":"3213","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"rslTools.tar.gz","4":"rslTools.tar.gz","src_id":"13631","5":"13631","creation_date":"1282283633","6":"1282283633"}]},"3212":{"script_id":"3212","0":"3212","script_name":"python_showpydoc","1":"python_showpydoc","script_type":"ftplugin","2":"ftplugin","summary":"Show document python within gvim command line~","3":"Show document python within gvim command line~","description":"details in scripts\r\n","4":"details in scripts\r\n","install_details":"make sure \"filetype plugin on\" \r\nthe rarfile have 4 scripts: \r\npython_showpydoc_2.vim is used for python2.x \r\nand python_showpydoc_3.vim for python3 \r\nthe python_showpydoc.vim and ShowPyDoc_PSD117.py for python2.x and python3\r\ncopy the scripts you want to ftplugin","5":"make sure \"filetype plugin on\" \r\nthe rarfile have 4 scripts: \r\npython_showpydoc_2.vim is used for python2.x \r\nand python_showpydoc_3.vim for python3 \r\nthe python_showpydoc.vim and ShowPyDoc_PSD117.py for python2.x and python3\r\ncopy the scripts you want to ftplugin","first_name":"Reaper","6":"Reaper","last_name":"Des","7":"Des","releases":[{"0":"3212","vim_version":"7.3","1":"7.3","script_version":"1.0","2":"1.0","version_comment":"None","3":"None","package":"python_showpydoc.rar","4":"python_showpydoc.rar","src_id":"13630","5":"13630","creation_date":"1282269409","6":"1282269409"}]},"3211":{"script_id":"3211","0":"3211","script_name":"operator-reverse","1":"operator-reverse","script_type":"utility","2":"utility","summary":"Operator to reverse text\/lines","3":"Operator to reverse text\/lines","description":"operator-reverse provides operator \/ ex commands to reverse text \/ lines.\r\n\r\nRequirements:\r\n- |operator-user| (vimscript#2692)\r\n\r\n\r\nrepository\r\n  http:\/\/github.com\/tyru\/operator-reverse.vim","4":"operator-reverse provides operator \/ ex commands to reverse text \/ lines.\r\n\r\nRequirements:\r\n- |operator-user| (vimscript#2692)\r\n\r\n\r\nrepository\r\n  http:\/\/github.com\/tyru\/operator-reverse.vim","install_details":"","5":"","first_name":"tyru","6":"tyru","last_name":" ","7":" ","releases":[{"0":"3211","vim_version":"7.0","1":"7.0","script_version":"0.0.0","2":"0.0.0","version_comment":"Initial upload","3":"Initial upload","package":"operator-reverse.zip","4":"operator-reverse.zip","src_id":"13621","5":"13621","creation_date":"1282191201","6":"1282191201"}]},"3210":{"script_id":"3210","0":"3210","script_name":"Smart Parentheses","1":"Smart Parentheses","script_type":"utility","2":"utility","summary":"Minimal but smart parentheses handling for programming","3":"Minimal but smart parentheses handling for programming","description":"Actually most types of brackets are supported, as long it works with %. This script aims to provide some useful tricks of ParEdit but be less restrictive and more geared towards C-style programming rather than Lisp. It has less than 5% of ParEdit probably, if you want something more similar, look for slimev.\r\n\r\nThis makes the open brackets (, [, and < introduce a balanced pair. If there is already an unbalance, the script determines if adding a closing bracket makes matters better or worse. In the latter case, the closing bracket is not added.\r\n\r\nTyping the close bracket checks if the next non-whitespace character is already that same symbol. If it is, the script just zaps all white-space until the existing symbol and moves past it. If there is no closing symbol, a new closing bracket is introduced. (Note that is much less restrictive than ParEdit but also much less safe).\r\n\r\nFor { a special case exists: typing a second { in a row introduces extra newlines for C-style programming rather than a nested pair of curly brackets. Also, } doesn't remove all white-space like the other brackets do. Again, this is convenient for programming.\r\n\r\nIn normal mode, you can type a number N and then an opening bracket, and the script will put brackets around the following N words, similar to what you can do in ParEdit.","4":"Actually most types of brackets are supported, as long it works with %. This script aims to provide some useful tricks of ParEdit but be less restrictive and more geared towards C-style programming rather than Lisp. It has less than 5% of ParEdit probably, if you want something more similar, look for slimev.\r\n\r\nThis makes the open brackets (, [, and < introduce a balanced pair. If there is already an unbalance, the script determines if adding a closing bracket makes matters better or worse. In the latter case, the closing bracket is not added.\r\n\r\nTyping the close bracket checks if the next non-whitespace character is already that same symbol. If it is, the script just zaps all white-space until the existing symbol and moves past it. If there is no closing symbol, a new closing bracket is introduced. (Note that is much less restrictive than ParEdit but also much less safe).\r\n\r\nFor { a special case exists: typing a second { in a row introduces extra newlines for C-style programming rather than a nested pair of curly brackets. Also, } doesn't remove all white-space like the other brackets do. Again, this is convenient for programming.\r\n\r\nIn normal mode, you can type a number N and then an opening bracket, and the script will put brackets around the following N words, similar to what you can do in ParEdit.","install_details":"Put in plugins directory, and run RemapParensForBuffer in buffers (autocmd!) where you want this to work.","5":"Put in plugins directory, and run RemapParensForBuffer in buffers (autocmd!) where you want this to work.","first_name":"Niels","6":"Niels","last_name":"Aan de Brugh","7":"Aan de Brugh","releases":[{"0":"3210","vim_version":"7.0","1":"7.0","script_version":"0.2","2":"0.2","version_comment":"Added option to exclude bracket types, escaping and only set up mappings if matchpairs is set properly.","3":"Added option to exclude bracket types, escaping and only set up mappings if matchpairs is set properly.","package":"smartparen.vim","4":"smartparen.vim","src_id":"13686","5":"13686","creation_date":"1282855806","6":"1282855806"},{"0":"3210","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"smartparen.vim","4":"smartparen.vim","src_id":"13620","5":"13620","creation_date":"1282165321","6":"1282165321"}]},"3209":{"script_id":"3209","0":"3209","script_name":"Quotes","1":"Quotes","script_type":"utility","2":"utility","summary":"Minimal but smart quote handling for programming","3":"Minimal but smart quote handling for programming","description":"Useful handling of quote-symbols for programming, without becoming too complicated or restrictive.\r\n\r\nThis script is designed so the sequence of keystrokes you would normally type (without any scripted assistance) yields the same result as with this script enabled. But that doesn\\\\\\'t mean you have to.\r\n\r\n- Typing \\\\\\\" introduces a new string and puts the cursor inside unless one of the following cases applies.\r\n- Typing \\\\\\\" just before the end of a string jumps out of the string (so you can continue typing).\r\n- Typing \\\\\\\" inside a string introduces a pair of escaped quote-symbols and puts the cursor in between.\r\n- Typing \\\\\\\" inside a string right after an escape character (i.e. an odd number of back-slashes) just inserts a \\\\\\\".\r\n- Typing \\\\\\\" just before \\\\\\\\\\\\\\\" inside a string jumps over the \\\\\\\\\\\\\\\", so (again) you can continue typing.\r\n\r\nIt\\\\\\'s pretty minimal, but useful I hope.\r\n\r\nThis is a 0.1 version, it has not yet been heavily used.","4":"Useful handling of quote-symbols for programming, without becoming too complicated or restrictive.\r\n\r\nThis script is designed so the sequence of keystrokes you would normally type (without any scripted assistance) yields the same result as with this script enabled. But that doesn\\\\\\'t mean you have to.\r\n\r\n- Typing \\\\\\\" introduces a new string and puts the cursor inside unless one of the following cases applies.\r\n- Typing \\\\\\\" just before the end of a string jumps out of the string (so you can continue typing).\r\n- Typing \\\\\\\" inside a string introduces a pair of escaped quote-symbols and puts the cursor in between.\r\n- Typing \\\\\\\" inside a string right after an escape character (i.e. an odd number of back-slashes) just inserts a \\\\\\\".\r\n- Typing \\\\\\\" just before \\\\\\\\\\\\\\\" inside a string jumps over the \\\\\\\\\\\\\\\", so (again) you can continue typing.\r\n\r\nIt\\\\\\'s pretty minimal, but useful I hope.\r\n\r\nThis is a 0.1 version, it has not yet been heavily used.","install_details":"Drop in plugins directory. Run RemapQuoteForBuffer inside each buffer (autocmd!) where you want this enabled.","5":"Drop in plugins directory. Run RemapQuoteForBuffer inside each buffer (autocmd!) where you want this enabled.","first_name":"Niels","6":"Niels","last_name":"Aan de Brugh","7":"Aan de Brugh","releases":[{"0":"3209","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"quotes.vim","4":"quotes.vim","src_id":"13619","5":"13619","creation_date":"1282164586","6":"1282164586"}]},"3208":{"script_id":"3208","0":"3208","script_name":"cHiTags","1":"cHiTags","script_type":"utility","2":"utility","summary":"Hi tags","3":"Hi tags","description":"Hi Tags Use C. \r\nIn linux fast.\r\nWindows Slow.","4":"Hi Tags Use C. \r\nIn linux fast.\r\nWindows Slow.","install_details":"","5":"","first_name":"su","6":"su","last_name":"su","7":"su","releases":[{"0":"3208","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"add sort tr ","3":"add sort tr ","package":"readtags.zip","4":"readtags.zip","src_id":"13609","5":"13609","creation_date":"1282102388","6":"1282102388"}]},"3207":{"script_id":"3207","0":"3207","script_name":"bundler","1":"bundler","script_type":"utility","2":"utility","summary":"Vim Ex-command wrapper for Ruby Bundler","3":"Vim Ex-command wrapper for Ruby Bundler","description":"Ruby Bundler is a RubyGem that is used for Rails 3+ and other Ruby projects to check dependencies of RubyGems for the project.\r\n\r\nTo use you can do the following:\r\n * :cd to a project with a Gemfile located at the root.\r\n * Open Gemfile\r\n * In Ex-command mode type <tt>:Bundle check<\/tt>\r\n * This will check your Gemfile dependencies are satisfied.  If there are RubyGem requirements specified in your Gemfile that are not satisfied the plugin will open up a quickfix window and for each error open up the Gemfile at the requirement that fails using quickfix keybindings.\r\n\r\nFull featured quickfix support for other Bundler subcommands coming soon.  You can clone the Git repository on GitHub from here:\r\nhttp:\/\/github.com\/mbbx6spp\/vim-bundler","4":"Ruby Bundler is a RubyGem that is used for Rails 3+ and other Ruby projects to check dependencies of RubyGems for the project.\r\n\r\nTo use you can do the following:\r\n * :cd to a project with a Gemfile located at the root.\r\n * Open Gemfile\r\n * In Ex-command mode type <tt>:Bundle check<\/tt>\r\n * This will check your Gemfile dependencies are satisfied.  If there are RubyGem requirements specified in your Gemfile that are not satisfied the plugin will open up a quickfix window and for each error open up the Gemfile at the requirement that fails using quickfix keybindings.\r\n\r\nFull featured quickfix support for other Bundler subcommands coming soon.  You can clone the Git repository on GitHub from here:\r\nhttp:\/\/github.com\/mbbx6spp\/vim-bundler","install_details":"On *NIX-like systems extract archive under ${HOME}\/.vim directory (if you don\\'t have one create one).  If on Windows extract archive under ${HOME}\/vimfiles directory.  Retain directory structure of archive file.","5":"On *NIX-like systems extract archive under ${HOME}\/.vim directory (if you don\\'t have one create one).  If on Windows extract archive under ${HOME}\/vimfiles directory.  Retain directory structure of archive file.","first_name":"Susan","6":"Susan","last_name":"Potter","7":"Potter","releases":[{"0":"3207","vim_version":"7.0","1":"7.0","script_version":"0.2","2":"0.2","version_comment":"* Fixed autocomplete function\r\n* Fixed autocmd problems\r\n* Removed redundant section from documenation","3":"* Fixed autocomplete function\r\n* Fixed autocmd problems\r\n* Removed redundant section from documenation","package":"vim-bundler-v0.2-0.zip","4":"vim-bundler-v0.2-0.zip","src_id":"13647","5":"13647","creation_date":"1282527488","6":"1282527488"},{"0":"3207","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"vim-bundler-v0.1-0.zip","4":"vim-bundler-v0.1-0.zip","src_id":"13603","5":"13603","creation_date":"1282070982","6":"1282070982"}]},"3206":{"script_id":"3206","0":"3206","script_name":"tangoshady","1":"tangoshady","script_type":"color scheme","2":"color scheme","summary":"the real TANGO colorscheme","3":"the real TANGO colorscheme","description":"This is a dark background tango colorscheme for gvim, macvim etc.\r\n\r\nInspired by the default vim settings in ubuntu linux gnome-terminal. Colors are one-to-one except some modifications like the Pmenu for better reading experience.\r\n\r\nIMPORTANT: THIS IS ONLY FOR GUI VIM\r\n\r\n\r\n\r\n\r\nFor donations email Shady at vimpimps@gmail.com","4":"This is a dark background tango colorscheme for gvim, macvim etc.\r\n\r\nInspired by the default vim settings in ubuntu linux gnome-terminal. Colors are one-to-one except some modifications like the Pmenu for better reading experience.\r\n\r\nIMPORTANT: THIS IS ONLY FOR GUI VIM\r\n\r\n\r\n\r\n\r\nFor donations email Shady at vimpimps@gmail.com","install_details":"In terminal:\r\ncp tangoshady.vim ~\/.vim\/colors\r\n\r\nIn vim\r\n:colorscheme tangoshady","5":"In terminal:\r\ncp tangoshady.vim ~\/.vim\/colors\r\n\r\nIn vim\r\n:colorscheme tangoshady","first_name":"vim","6":"vim","last_name":"pimps","7":"pimps","releases":[{"0":"3206","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"tangoshady.vim","4":"tangoshady.vim","src_id":"13598","5":"13598","creation_date":"1282026471","6":"1282026471"}]},"3205":{"script_id":"3205","0":"3205","script_name":"python_showpydoc.vim","1":"python_showpydoc.vim","script_type":"ftplugin","2":"ftplugin","summary":"Show document string of python3 or later in command line~","3":"Show document string of python3 or later in command line~","description":"The script has updated for support both python2.x and python3.x \r\ngo to vimscript#3212 for new version.  \r\nNote: this plugin needs python3\/dyn so that using gvim7.3 is easist and best way.\r\n\r\nusage:         commands:\r\n                 :Spydoc object\r\n                 the \"object\" can be an \"imported\" class, module or function(\/method)\r\n                 the command return document string corresponding to the object.\r\n                 else return type of the object.\r\n                 if the object is \"unimported\" the command will fail except for\r\n                 modules re, vim and\r\n                 FunctionType, MethodType, ModuleType, BuiltinFunctionType,\r\n                 BuiltinMethodType imported from module types\r\n\r\ntip:             this plugin now is just designed for standart python3 library,\r\n                 if try the command with a user-defined \"object\", \r\n                 be very likely to get an error \"name 'object' is not defined\".\r\n\r\nexamples:  lets say a simple python script:\r\n                   import sys;\r\n                   form sys import path;\r\n                   class Test(object): pass;\r\n                   t = Test();\r\n                and input following commands:\r\n\r\n                :Spydoc sys \r\n                sys document(module)\r\n\r\n                :Spydoc sys.exit\r\n                sys.exit document(function)\r\n\r\n                :Spydoc sys.path\r\n                type of sys.path(built-in type list)\r\n\r\n                :Spydoc path\r\n                type of os.path(same as above)\r\n\r\n                :Spydoc Test:\r\n                error: name 'Test' is not define\r\n\r\n                :Spydoc t:\r\n                error: name 't' is not define\r\n\r\n                :Spydoc sys.ss\r\n                error: 'module' object has no attribute 'ss'\r\n\r\n                :Spydoc sys.exit()\r\n                error: 'sys.exit()' is a wrong?","4":"The script has updated for support both python2.x and python3.x \r\ngo to vimscript#3212 for new version.  \r\nNote: this plugin needs python3\/dyn so that using gvim7.3 is easist and best way.\r\n\r\nusage:         commands:\r\n                 :Spydoc object\r\n                 the \"object\" can be an \"imported\" class, module or function(\/method)\r\n                 the command return document string corresponding to the object.\r\n                 else return type of the object.\r\n                 if the object is \"unimported\" the command will fail except for\r\n                 modules re, vim and\r\n                 FunctionType, MethodType, ModuleType, BuiltinFunctionType,\r\n                 BuiltinMethodType imported from module types\r\n\r\ntip:             this plugin now is just designed for standart python3 library,\r\n                 if try the command with a user-defined \"object\", \r\n                 be very likely to get an error \"name 'object' is not defined\".\r\n\r\nexamples:  lets say a simple python script:\r\n                   import sys;\r\n                   form sys import path;\r\n                   class Test(object): pass;\r\n                   t = Test();\r\n                and input following commands:\r\n\r\n                :Spydoc sys \r\n                sys document(module)\r\n\r\n                :Spydoc sys.exit\r\n                sys.exit document(function)\r\n\r\n                :Spydoc sys.path\r\n                type of sys.path(built-in type list)\r\n\r\n                :Spydoc path\r\n                type of os.path(same as above)\r\n\r\n                :Spydoc Test:\r\n                error: name 'Test' is not define\r\n\r\n                :Spydoc t:\r\n                error: name 't' is not define\r\n\r\n                :Spydoc sys.ss\r\n                error: 'module' object has no attribute 'ss'\r\n\r\n                :Spydoc sys.exit()\r\n                error: 'sys.exit()' is a wrong?","install_details":"Install:        make sure \"filetype plugin on\" and gvim complied with python3\/dyn\r\n                copy python_showpydoc.vim to your ftplugin directory","5":"Install:        make sure \"filetype plugin on\" and gvim complied with python3\/dyn\r\n                copy python_showpydoc.vim to your ftplugin directory","first_name":"Reaper","6":"Reaper","last_name":"Des","7":"Des","releases":[{"0":"3205","vim_version":"7.3","1":"7.3","script_version":"1.1","2":"1.1","version_comment":"-fixed 2 unnecessary attributes\r\n-to confuse names in plugin to minimize name-crash","3":"-fixed 2 unnecessary attributes\r\n-to confuse names in plugin to minimize name-crash","package":"python_showpydoc.vim","4":"python_showpydoc.vim","src_id":"13599","5":"13599","creation_date":"1282032825","6":"1282032825"},{"0":"3205","vim_version":"7.3","1":"7.3","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"python_showpydoc.vim","4":"python_showpydoc.vim","src_id":"13597","5":"13597","creation_date":"1282019782","6":"1282019782"}]},"3204":{"script_id":"3204","0":"3204","script_name":"htip","1":"htip","script_type":"utility","2":"utility","summary":"quick haskell hints at the status line","3":"quick haskell hints at the status line","description":"with default key binding enabled, move the cursor over a word, for example \"map\" and press <leader>ht \r\nthis will put the following line in the status line: \r\n\r\n\r\n1\/1: map :: (a->b) -> [a] -> [b]\r\n(1\/1 - first line of, well, a single line) \r\n\r\npressing <leader>hh will show the next line, if any.\r\n\r\n<leader>hH show the previous one, the list is cyclic \r\n\r\nthere are also <leader>hi for info, <leader>hb for browse, <leader>hk for kind.\r\n\r\nsee code for more details ","4":"with default key binding enabled, move the cursor over a word, for example \"map\" and press <leader>ht \r\nthis will put the following line in the status line: \r\n\r\n\r\n1\/1: map :: (a->b) -> [a] -> [b]\r\n(1\/1 - first line of, well, a single line) \r\n\r\npressing <leader>hh will show the next line, if any.\r\n\r\n<leader>hH show the previous one, the list is cyclic \r\n\r\nthere are also <leader>hi for info, <leader>hb for browse, <leader>hk for kind.\r\n\r\nsee code for more details ","install_details":"just put under ~\/.vim\/plugin \r\nto enable default key bindings put \r\nlet g:htip_bindkeys=1 \r\nin your ~\/.vimrc ","5":"just put under ~\/.vim\/plugin \r\nto enable default key bindings put \r\nlet g:htip_bindkeys=1 \r\nin your ~\/.vimrc ","first_name":"Itay","6":"Itay","last_name":"Donenhirsch","7":"Donenhirsch","releases":[{"0":"3204","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"htip.vim","4":"htip.vim","src_id":"13592","5":"13592","creation_date":"1281988722","6":"1281988722"}]},"3203":{"script_id":"3203","0":"3203","script_name":"mantip","1":"mantip","script_type":"utility","2":"utility","summary":"quick tip from synopsis section in man pages for words","3":"quick tip from synopsis section in man pages for words","description":"with default key binding enabled, move the cursor over a word, for example strcmp and press <leader>d\r\nthis will put the following line in the status line:\r\n\r\nSTRCMP(3) 1\/2: int strcmp(const char *s1, const char *s2);\r\n(STCMP(3) - man page, 1\/2 - first line of two lines)\r\n\r\npressing <leader>d again will show the next decelration:\r\n\r\nSTRCMP(3) 2\/2: int strncmp(const char *s1, const char *s2, size_t n);\r\n\r\n<leader>D show the previous one, the list is cyclic\r\n\r\nuse <leader>1..9 to man specific sections\r\n\r\nsee code for more details\r\n","4":"with default key binding enabled, move the cursor over a word, for example strcmp and press <leader>d\r\nthis will put the following line in the status line:\r\n\r\nSTRCMP(3) 1\/2: int strcmp(const char *s1, const char *s2);\r\n(STCMP(3) - man page, 1\/2 - first line of two lines)\r\n\r\npressing <leader>d again will show the next decelration:\r\n\r\nSTRCMP(3) 2\/2: int strncmp(const char *s1, const char *s2, size_t n);\r\n\r\n<leader>D show the previous one, the list is cyclic\r\n\r\nuse <leader>1..9 to man specific sections\r\n\r\nsee code for more details\r\n","install_details":"just put under ~\/.vim\/plugin\r\nto enable default key bindings put\r\nlet g:mantip_bindkeys=1\r\nin your ~\/.vimrc\r\n","5":"just put under ~\/.vim\/plugin\r\nto enable default key bindings put\r\nlet g:mantip_bindkeys=1\r\nin your ~\/.vimrc\r\n","first_name":"Itay","6":"Itay","last_name":"Donenhirsch","7":"Donenhirsch","releases":[{"0":"3203","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"mantip.vim","4":"mantip.vim","src_id":"13587","5":"13587","creation_date":"1281969394","6":"1281969394"}]},"3202":{"script_id":"3202","0":"3202","script_name":"rdark-terminal","1":"rdark-terminal","script_type":"color scheme","2":"color scheme","summary":"256 Color Terminal version of the rdark colorscheme","3":"256 Color Terminal version of the rdark colorscheme","description":"I ported the rdark colorscheme (http:\/\/www.vim.org\/scripts\/script.php?script_id=1732) to fit in a 256 color capable terminal.\r\n\r\nInfo: As the original background color is not available in 256 color mode\r\nI've set it to black. But you can set the color your terminal should display\r\nfor black to #1e2426 and you will have almost a 1:1 copy of the gui scheme.\r\nI also suggest to set the second black color to #2c3032. (It is the\r\nbackground color which ist used for NonText)\r\nIf you're using a terminal which reads from Xdefaults (e.g. urxvt) you just\r\ndo this in your .Xdefaults:\r\n*color0:     rgb:1e\/24\/26\r\n*color8:     rgb:2c\/30\/32\r\n\r\nScreenshot: http:\/\/www.img-share.net\/uploads\/125vim_b1.png","4":"I ported the rdark colorscheme (http:\/\/www.vim.org\/scripts\/script.php?script_id=1732) to fit in a 256 color capable terminal.\r\n\r\nInfo: As the original background color is not available in 256 color mode\r\nI've set it to black. But you can set the color your terminal should display\r\nfor black to #1e2426 and you will have almost a 1:1 copy of the gui scheme.\r\nI also suggest to set the second black color to #2c3032. (It is the\r\nbackground color which ist used for NonText)\r\nIf you're using a terminal which reads from Xdefaults (e.g. urxvt) you just\r\ndo this in your .Xdefaults:\r\n*color0:     rgb:1e\/24\/26\r\n*color8:     rgb:2c\/30\/32\r\n\r\nScreenshot: http:\/\/www.img-share.net\/uploads\/125vim_b1.png","install_details":"","5":"","first_name":"Lukas","6":"Lukas","last_name":"Gr\u00c3\u00a4sslin","7":"Gr\u00c3\u00a4sslin","releases":[{"0":"3202","vim_version":"7.0","1":"7.0","script_version":"0.2","2":"0.2","version_comment":"Some color updates","3":"Some color updates","package":"rdark-terminal.vim","4":"rdark-terminal.vim","src_id":"13655","5":"13655","creation_date":"1282583089","6":"1282583089"},{"0":"3202","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"rdark-terminal.vim","4":"rdark-terminal.vim","src_id":"13586","5":"13586","creation_date":"1281965258","6":"1281965258"}]},"3201":{"script_id":"3201","0":"3201","script_name":"trailing-whitespace","1":"trailing-whitespace","script_type":"utility","2":"utility","summary":" Highlights trailing whitespace in red and offers:FixWhitespace","3":" Highlights trailing whitespace in red and offers:FixWhitespace","description":"This plugin causes all trailing whitespace to be highlighted in red.\r\n\r\nTo fix the whitespace errors, just call :FixWhitespace.  By default it\r\noperates on the entire file.  Pass a range (or use V to select some lines)\r\nto restrict the portion of the file that gets fixed.\r\n\r\nThe repo is at http:\/\/github.com\/bronson\/vim-trailing-whitespace\r\n\r\nBased on http:\/\/vim.wikia.com\/wiki\/Highlight_unwanted_spaces\r\n","4":"This plugin causes all trailing whitespace to be highlighted in red.\r\n\r\nTo fix the whitespace errors, just call :FixWhitespace.  By default it\r\noperates on the entire file.  Pass a range (or use V to select some lines)\r\nto restrict the portion of the file that gets fixed.\r\n\r\nThe repo is at http:\/\/github.com\/bronson\/vim-trailing-whitespace\r\n\r\nBased on http:\/\/vim.wikia.com\/wiki\/Highlight_unwanted_spaces\r\n","install_details":"Install trailing-whitespace.vim in ~\/.vim\/plugin and trailing-whitespace.txt in ~\/.vim\/doc.","5":"Install trailing-whitespace.vim in ~\/.vim\/plugin and trailing-whitespace.txt in ~\/.vim\/doc.","first_name":"Scott","6":"Scott","last_name":"Bronson","7":"Bronson","releases":[{"0":"3201","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Don't modify the cursor position or search highlight when fixing whitespace.","3":"Don't modify the cursor position or search highlight when fixing whitespace.","package":"trailing-whitespace-1.0.tar.gz","4":"trailing-whitespace-1.0.tar.gz","src_id":"13839","5":"13839","creation_date":"1284600058","6":"1284600058"},{"0":"3201","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"trailing-whitespace.tar.gz","4":"trailing-whitespace.tar.gz","src_id":"13577","5":"13577","creation_date":"1281849648","6":"1281849648"}]},"3200":{"script_id":"3200","0":"3200","script_name":"Haskell Conceal","1":"Haskell Conceal","script_type":"syntax","2":"syntax","summary":"Add some conceal operation to haskell's syntax","3":"Add some conceal operation to haskell's syntax","description":"Use Vim 7.3 Conceal feature to display unicode operator\r\nin Haskell without changing the underlying file.\r\n\r\nGitHub: https:\/\/github.com\/Twinside\/vim-haskellConceal\r\n","4":"Use Vim 7.3 Conceal feature to display unicode operator\r\nin Haskell without changing the underlying file.\r\n\r\nGitHub: https:\/\/github.com\/Twinside\/vim-haskellConceal\r\n","install_details":"Decompress in your ~\/vimfiles or ~\/.vim, if you're using\r\npathogen (you should), put it in ~\/.vim\/bundle\/haskellConceal\r\nfolder","5":"Decompress in your ~\/vimfiles or ~\/.vim, if you're using\r\npathogen (you should), put it in ~\/.vim\/bundle\/haskellConceal\r\nfolder","first_name":"Vincent","6":"Vincent","last_name":"B","7":"B","releases":[{"0":"3200","vim_version":"7.3","1":"7.3","script_version":"1.1","2":"1.1","version_comment":"Fixing conceal level to be local (thx Erlend Hamberg)","3":"Fixing conceal level to be local (thx Erlend Hamberg)","package":"haskellConceal.zip","4":"haskellConceal.zip","src_id":"15105","5":"15105","creation_date":"1298537773","6":"1298537773"},{"0":"3200","vim_version":"7.2","1":"7.2","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"HaskellConceal.vba","4":"HaskellConceal.vba","src_id":"13575","5":"13575","creation_date":"1281833410","6":"1281833410"}]},"3199":{"script_id":"3199","0":"3199","script_name":"vim-addon-ocaml","1":"vim-addon-ocaml","script_type":"utility","2":"utility","summary":"collected ocaml scripts - some completion - annotations","3":"collected ocaml scripts - some completion - annotations","description":"http:\/\/github.com\/MarcWeber\/vim-addon-ocaml\r\n\r\nThis collection includes well known scripts I was pointed to such as ocaml\r\nindentation, annot support as well as omni completion support\r\n\r\nI modified the indenting slightly so that the args  \"..\" and x y are not\r\nindented at all. (Using vim indentation they are indented the same as Printf\r\nwhich is annoying)\r\n\r\nlet f x =\r\n  let y = x + 1 in\r\n  Printf.printf\r\n    \"%d + 1 = %d\"\r\n    x y\r\n\r\ncompletion details:\r\n====================\r\n\r\nAll completion is based on .mli files found in all tag files.\r\nIf you don't have tags, tell Vim which .mli files to use:\r\n\r\nlet g:vim_addon_ocaml = { 'provide_additional_mlis': function('name of function returning a list of .mli files') }\r\n\r\na) name completion:\r\n  all .mli files are grepped for the name\r\n  Additionally all let bindings found in current buffer are taken into account\r\n\r\nb) type completion:\r\n\r\n  con:str           finnds concat : string -> string\r\n\r\n  :^int->string$    finds string_of_int\r\n\r\nc) var based completion (not that well tested)\r\n\r\n  x:conc\r\n\r\n  the type of x is looked up by .annot files (you must have created the musing ocamlc or ocamelopt)\r\n  Then b) completion is used using the type of x.\r\n","4":"http:\/\/github.com\/MarcWeber\/vim-addon-ocaml\r\n\r\nThis collection includes well known scripts I was pointed to such as ocaml\r\nindentation, annot support as well as omni completion support\r\n\r\nI modified the indenting slightly so that the args  \"..\" and x y are not\r\nindented at all. (Using vim indentation they are indented the same as Printf\r\nwhich is annoying)\r\n\r\nlet f x =\r\n  let y = x + 1 in\r\n  Printf.printf\r\n    \"%d + 1 = %d\"\r\n    x y\r\n\r\ncompletion details:\r\n====================\r\n\r\nAll completion is based on .mli files found in all tag files.\r\nIf you don't have tags, tell Vim which .mli files to use:\r\n\r\nlet g:vim_addon_ocaml = { 'provide_additional_mlis': function('name of function returning a list of .mli files') }\r\n\r\na) name completion:\r\n  all .mli files are grepped for the name\r\n  Additionally all let bindings found in current buffer are taken into account\r\n\r\nb) type completion:\r\n\r\n  con:str           finnds concat : string -> string\r\n\r\n  :^int->string$    finds string_of_int\r\n\r\nc) var based completion (not that well tested)\r\n\r\n  x:conc\r\n\r\n  the type of x is looked up by .annot files (you must have created the musing ocamlc or ocamelopt)\r\n  Then b) completion is used using the type of x.\r\n","install_details":"Recommended way of installation: use vim-addon-manager because it depends on a set of other plugins. See http:\/\/github.com\/MarcWeber\/vim-addon-manager\r\n\r\nIf you have any trouble don't blame - send me a message instead. Thanks","5":"Recommended way of installation: use vim-addon-manager because it depends on a set of other plugins. See http:\/\/github.com\/MarcWeber\/vim-addon-manager\r\n\r\nIf you have any trouble don't blame - send me a message instead. Thanks","first_name":"Marc","6":"Marc","last_name":"Weber","7":"Weber","releases":[{"0":"3199","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"vim-addon-ocaml-initial-upload.zip","4":"vim-addon-ocaml-initial-upload.zip","src_id":"13574","5":"13574","creation_date":"1281832149","6":"1281832149"}]},"3198":{"script_id":"3198","0":"3198","script_name":"undofile.vim","1":"undofile.vim","script_type":"utility","2":"utility","summary":"persistent undo: enable 'undofile' for certain files only","3":"persistent undo: enable 'undofile' for certain files only","description":"If you want 'undofile' only for certain files, you will notice that 'undofile' cannot be set in a modeline, or once the buffer is loaded (because an existing undo file will not be loaded then).  Bram suggests to use a BufReadPre autocmd which sets 'undofile' before the buffer is loaded.  This script does the steps for you.\r\n\r\nUsage:\r\n\r\n:SetUndoFile[!]\r\n\r\n  execute :setlocal undofile, install a BufReadPre autocmd for the current file name and also maintain a plugin file \"plugin\/undofile_autocmds.vim\" that enables all such autocmds at next startup of Vim.\r\n\r\n  This means you can execute this command once for the current file and then never ever again -- FIRE AND FORGET ;)\r\n\r\n  The plugin file (if not found in the runtimepath) is stored in the first directory of the runtimepath (which must contain a \"plugin\" folder).  Older Vims will ignore the plugin.\r\n\r\n  With [!], ignore if 'undofile' is already set.\r\n\r\n\r\n:UnsetUndoFile\r\n\r\n  opposite of :SetUndoFile.  Does :setlocal noundofile, removes the autcommand and the autcommand entry from \"plugin\/undofile_autocmds.vim\"; finally it executes :DelUndoFile.\r\n\r\n\r\n:DelUndoFile\r\n\r\n  delete the undofile for the current buffer.  Fails silently.\r\n\r\nPLEASE REPORT BUGS","4":"If you want 'undofile' only for certain files, you will notice that 'undofile' cannot be set in a modeline, or once the buffer is loaded (because an existing undo file will not be loaded then).  Bram suggests to use a BufReadPre autocmd which sets 'undofile' before the buffer is loaded.  This script does the steps for you.\r\n\r\nUsage:\r\n\r\n:SetUndoFile[!]\r\n\r\n  execute :setlocal undofile, install a BufReadPre autocmd for the current file name and also maintain a plugin file \"plugin\/undofile_autocmds.vim\" that enables all such autocmds at next startup of Vim.\r\n\r\n  This means you can execute this command once for the current file and then never ever again -- FIRE AND FORGET ;)\r\n\r\n  The plugin file (if not found in the runtimepath) is stored in the first directory of the runtimepath (which must contain a \"plugin\" folder).  Older Vims will ignore the plugin.\r\n\r\n  With [!], ignore if 'undofile' is already set.\r\n\r\n\r\n:UnsetUndoFile\r\n\r\n  opposite of :SetUndoFile.  Does :setlocal noundofile, removes the autcommand and the autcommand entry from \"plugin\/undofile_autocmds.vim\"; finally it executes :DelUndoFile.\r\n\r\n\r\n:DelUndoFile\r\n\r\n  delete the undofile for the current buffer.  Fails silently.\r\n\r\nPLEASE REPORT BUGS","install_details":"Note: With Vim 7.3.392 or newer, you can set 'undofile' in the modeline!  No need for this script then ... (2012 Jan 28)\r\n\r\nrequires the persistent_undo feature (since Vim7.3)\r\n:source this script when needed, or drop it in your plugin folder","5":"Note: With Vim 7.3.392 or newer, you can set 'undofile' in the modeline!  No need for this script then ... (2012 Jan 28)\r\n\r\nrequires the persistent_undo feature (since Vim7.3)\r\n:source this script when needed, or drop it in your plugin folder","first_name":"Andy","6":"Andy","last_name":"Wokula","7":"Wokula","releases":[{"0":"3198","vim_version":"7.0","1":"7.0","script_version":"0.2","2":"0.2","version_comment":"forgot the init folklore","3":"forgot the init folklore","package":"undofile.vim","4":"undofile.vim","src_id":"13567","5":"13567","creation_date":"1281806520","6":"1281806520"},{"0":"3198","vim_version":"7.2","1":"7.2","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"undofile.vim","4":"undofile.vim","src_id":"13565","5":"13565","creation_date":"1281804677","6":"1281804677"}]},"3197":{"script_id":"3197","0":"3197","script_name":"current-func-info.vim","1":"current-func-info.vim","script_type":"utility","2":"utility","summary":"Get current function name","3":"Get current function name","description":"Supported languages: C, Perl, Ruby, Python, PHP, Vim script\r\nRepository: http:\/\/github.com\/tyru\/current-func-info.vim\r\n\r\n\r\ncurrent-func-info shows current function's name to statusline, tabline,\r\nanywhere.\r\n|cfi#get_func_name()| to get function's name.\r\n\r\n\r\ncfi#load()\t\t\t\t*cfi#load()*\r\n\tLoad \"autoload\/cfi.vim\" and \"plugin\/cfi.vim\".\r\n\r\ncfi#get_func_name([{filetype}])\t\t\t\t*cfi#get_func_name()*\r\n\tReturns function's name.\r\n\tIf {filetype} is omitted, current 'filetype' is used instead.\r\n\tInclude this expression to |'statusline'| or |'tabline'| and so on.\r\n\r\ncfi#format({fmt}, {default})\t\t\t*cfi#format()*\r\n\tReturns formatted string. >\r\n    let &statusline = '%{cfi#format(\"[%s()]\", \"no function\")}'\r\n<\tThis returns \"no function\" if cfi#get_func_name() returns empty string.\r\n\tOr returns \"[func()]\" if cfi#get_func_name() returns \"func\".\r\n\r\ncfi#create_finder({filetype})\t\t\t\t*cfi#create_finder()*\r\n\tReturns Dictionary of instance for finder.\r\n\r\n\tTo create finder, implement |s:finder.find()| or\r\n\timplement |s:finder.get_func_name()|, |s:finder.find_begin()|,\r\n\t|s:finder.find_end()|.\r\n\r\n\t(TODO: Write more descriptions)\r\n\r\n\tSee ftplugin\/*.vim for the details.\r\n\r\ncfi#supported_filetype({filetype})\t\t\t\t*cfi#supported_filetype()*\r\n\tReturn boolean value if {filetype} is supported.","4":"Supported languages: C, Perl, Ruby, Python, PHP, Vim script\r\nRepository: http:\/\/github.com\/tyru\/current-func-info.vim\r\n\r\n\r\ncurrent-func-info shows current function's name to statusline, tabline,\r\nanywhere.\r\n|cfi#get_func_name()| to get function's name.\r\n\r\n\r\ncfi#load()\t\t\t\t*cfi#load()*\r\n\tLoad \"autoload\/cfi.vim\" and \"plugin\/cfi.vim\".\r\n\r\ncfi#get_func_name([{filetype}])\t\t\t\t*cfi#get_func_name()*\r\n\tReturns function's name.\r\n\tIf {filetype} is omitted, current 'filetype' is used instead.\r\n\tInclude this expression to |'statusline'| or |'tabline'| and so on.\r\n\r\ncfi#format({fmt}, {default})\t\t\t*cfi#format()*\r\n\tReturns formatted string. >\r\n    let &statusline = '%{cfi#format(\"[%s()]\", \"no function\")}'\r\n<\tThis returns \"no function\" if cfi#get_func_name() returns empty string.\r\n\tOr returns \"[func()]\" if cfi#get_func_name() returns \"func\".\r\n\r\ncfi#create_finder({filetype})\t\t\t\t*cfi#create_finder()*\r\n\tReturns Dictionary of instance for finder.\r\n\r\n\tTo create finder, implement |s:finder.find()| or\r\n\timplement |s:finder.get_func_name()|, |s:finder.find_begin()|,\r\n\t|s:finder.find_end()|.\r\n\r\n\t(TODO: Write more descriptions)\r\n\r\n\tSee ftplugin\/*.vim for the details.\r\n\r\ncfi#supported_filetype({filetype})\t\t\t\t*cfi#supported_filetype()*\r\n\tReturn boolean value if {filetype} is supported.","install_details":"","5":"","first_name":"tyru","6":"tyru","last_name":" ","7":" ","releases":[{"0":"3197","vim_version":"7.0","1":"7.0","script_version":"0.0.5","2":"0.0.5","version_comment":"- Fix the flickering of c ftplugin\r\n- Add variables g:cfi_disable, g:loaded_cfi_ftplugin_{lang}.","3":"- Fix the flickering of c ftplugin\r\n- Add variables g:cfi_disable, g:loaded_cfi_ftplugin_{lang}.","package":"cfi.zip","4":"cfi.zip","src_id":"14617","5":"14617","creation_date":"1293278560","6":"1293278560"},{"0":"3197","vim_version":"7.0","1":"7.0","script_version":"0.0.4","2":"0.0.4","version_comment":"Include PHP support. Thanks Chris Ruzin.","3":"Include PHP support. Thanks Chris Ruzin.","package":"cfi.zip","4":"cfi.zip","src_id":"13768","5":"13768","creation_date":"1283782328","6":"1283782328"},{"0":"3197","vim_version":"7.0","1":"7.0","script_version":"0.0.3","2":"0.0.3","version_comment":"Fix bug: Ruby ftplugin did not work.","3":"Fix bug: Ruby ftplugin did not work.","package":"cfi.zip","4":"cfi.zip","src_id":"13742","5":"13742","creation_date":"1283425718","6":"1283425718"},{"0":"3197","vim_version":"7.0","1":"7.0","script_version":"0.0.2","2":"0.0.2","version_comment":"- Implement cfi#format()\r\n- Implement Python support","3":"- Implement cfi#format()\r\n- Implement Python support","package":"cfi.zip","4":"cfi.zip","src_id":"13638","5":"13638","creation_date":"1282391980","6":"1282391980"},{"0":"3197","vim_version":"7.0","1":"7.0","script_version":"0.0.1","2":"0.0.1","version_comment":"- Fixed bug of ftplugin\/vim\/cfi.vim: couldn't get the name of last function in a file.","3":"- Fixed bug of ftplugin\/vim\/cfi.vim: couldn't get the name of last function in a file.","package":"cfi.zip","4":"cfi.zip","src_id":"13558","5":"13558","creation_date":"1281689309","6":"1281689309"},{"0":"3197","vim_version":"7.0","1":"7.0","script_version":"0.0.0","2":"0.0.0","version_comment":"Initial upload","3":"Initial upload","package":"cfi.zip","4":"cfi.zip","src_id":"13557","5":"13557","creation_date":"1281676452","6":"1281676452"}]},"3196":{"script_id":"3196","0":"3196","script_name":"gedim","1":"gedim","script_type":"utility","2":"utility","summary":"Auto-size Graphical EDitor DIMensions on open.","3":"Auto-size Graphical EDitor DIMensions on open.","description":"My portable computer is my primary workstation. I either use an external, high resolution monitor or its built-in screen, depending on where I am. I often use also someone else's monitors, when I'm working remotely. This forces me to change the graphical Vim editor dimensions for every location where I happen to be. Though not complicated, it's annoying. That's why I wrote this script\/Vim auto-command that does the job instead. Just define the desired editor columns and lines for a given resolution, and MacVim will open at that size every time that the same resolution is detected.\r\n\r\nFeatures:\r\n\r\n    * User configurable: add as many output device resolutions and editor sizes as desired or needed\r\n    * MacVim and gVim compatible\r\n    * Works on OS X, Linux\/Gnome, Linux\/KDE, and Windows\r\n    * Unobtrusive; set it up once and forget about it\r\n\r\nNo more dragging the window corners to resize. No more :set columns=128. Just open Vim and get to work!","4":"My portable computer is my primary workstation. I either use an external, high resolution monitor or its built-in screen, depending on where I am. I often use also someone else's monitors, when I'm working remotely. This forces me to change the graphical Vim editor dimensions for every location where I happen to be. Though not complicated, it's annoying. That's why I wrote this script\/Vim auto-command that does the job instead. Just define the desired editor columns and lines for a given resolution, and MacVim will open at that size every time that the same resolution is detected.\r\n\r\nFeatures:\r\n\r\n    * User configurable: add as many output device resolutions and editor sizes as desired or needed\r\n    * MacVim and gVim compatible\r\n    * Works on OS X, Linux\/Gnome, Linux\/KDE, and Windows\r\n    * Unobtrusive; set it up once and forget about it\r\n\r\nNo more dragging the window corners to resize. No more :set columns=128. Just open Vim and get to work!","install_details":"UNIX-like systems:\r\n\r\ncd ~\/.vim\r\n\r\nunzip \/path\/to\/gedim.zip\r\n\r\nvi\r\n:helptags ~\/.vim\/doc\r\n\r\n\r\nWindows systems:\r\n\r\nUnpack the .zip file and copy the files to your\r\ngvim or vim configuration directory, then:\r\n\r\nvi\r\n:helptags \/path\/to\/doc\r\n\r\n\r\nCaveat Fenestrae emptor:\r\n------------------------\r\nUnfortunately the developers and testers had only limited access to a Windows machine.  Please let me know if you had issues through the URL in the comments section.\r\n\r\nComments, questions, bug reports:\r\n---------------------------------\r\nhttp:\/\/eugeneciurana.com\/contact or\r\nhttp:\/\/ciurana.eu\/contact for your questions.\r\n\r\nProject page:  http:\/\/eugeneciurana.com\/gedim.vim\r\n\r\nIMPORTANT:\r\n:help gedim-configuration\r\n\r\nThis section tells you how to configure the various editor sizes corresponding to each screen resolution.\r\n","5":"UNIX-like systems:\r\n\r\ncd ~\/.vim\r\n\r\nunzip \/path\/to\/gedim.zip\r\n\r\nvi\r\n:helptags ~\/.vim\/doc\r\n\r\n\r\nWindows systems:\r\n\r\nUnpack the .zip file and copy the files to your\r\ngvim or vim configuration directory, then:\r\n\r\nvi\r\n:helptags \/path\/to\/doc\r\n\r\n\r\nCaveat Fenestrae emptor:\r\n------------------------\r\nUnfortunately the developers and testers had only limited access to a Windows machine.  Please let me know if you had issues through the URL in the comments section.\r\n\r\nComments, questions, bug reports:\r\n---------------------------------\r\nhttp:\/\/eugeneciurana.com\/contact or\r\nhttp:\/\/ciurana.eu\/contact for your questions.\r\n\r\nProject page:  http:\/\/eugeneciurana.com\/gedim.vim\r\n\r\nIMPORTANT:\r\n:help gedim-configuration\r\n\r\nThis section tells you how to configure the various editor sizes corresponding to each screen resolution.\r\n","first_name":"Eugene","6":"Eugene","last_name":"Ciurana","7":"Ciurana","releases":[{"0":"3196","vim_version":"7.0","1":"7.0","script_version":"1.2b","2":"1.2b","version_comment":"Updated the documentation for Windows support in response to a bug report when running gVim + gedim in Windows Vista; the appropriate course, according to the Windows experts contributors to this project, is to use Windows 7 or later (Windows 8.1 on the date of this update).","3":"Updated the documentation for Windows support in response to a bug report when running gVim + gedim in Windows Vista; the appropriate course, according to the Windows experts contributors to this project, is to use Windows 7 or later (Windows 8.1 on the date of this update).","package":"gedim.zip","4":"gedim.zip","src_id":"22467","5":"22467","creation_date":"1412096659","6":"1412096659"},{"0":"3196","vim_version":"7.0","1":"7.0","script_version":"1.2","2":"1.2","version_comment":"Faster screen detection on OS X - improvement by Ludvig Ericson - thanks!  Also added main display detection on MacVim \/ gVim running on Macs with multiple displays attached.","3":"Faster screen detection on OS X - improvement by Ludvig Ericson - thanks!  Also added main display detection on MacVim \/ gVim running on Macs with multiple displays attached.","package":"gedim.zip","4":"gedim.zip","src_id":"13753","5":"13753","creation_date":"1283532364","6":"1283532364"},{"0":"3196","vim_version":"7.0","1":"7.0","script_version":"1.1c","2":"1.1c","version_comment":"Fixed a typo in the documentation comments and updated contributors list.  No functional changes if you already have 1.1b.","3":"Fixed a typo in the documentation comments and updated contributors list.  No functional changes if you already have 1.1b.","package":"gedim.zip","4":"gedim.zip","src_id":"13566","5":"13566","creation_date":"1281804954","6":"1281804954"},{"0":"3196","vim_version":"7.0","1":"7.0","script_version":"1.1b","2":"1.1b","version_comment":"Fixed the EOL detection code for the Windows script that reports the screen resolution; the original author had forgotten that EOL in DOS\/Windows == \\r\\n.  Thanks to Nathan Tenney for pointing that out an for providing a fix.","3":"Fixed the EOL detection code for the Windows script that reports the screen resolution; the original author had forgotten that EOL in DOS\/Windows == \\r\\n.  Thanks to Nathan Tenney for pointing that out an for providing a fix.","package":"gedim.zip","4":"gedim.zip","src_id":"13562","5":"13562","creation_date":"1281768874","6":"1281768874"},{"0":"3196","vim_version":"7.0","1":"7.0","script_version":"1.1","2":"1.1","version_comment":"Initial upload","3":"Initial upload","package":"gedim.zip","4":"gedim.zip","src_id":"13553","5":"13553","creation_date":"1281563543","6":"1281563543"}]},"3195":{"script_id":"3195","0":"3195","script_name":"Starting .vimrc","1":"Starting .vimrc","script_type":"utility","2":"utility","summary":"Simple .vimrc to get up and running","3":"Simple .vimrc to get up and running","description":"This is my base .vimrc that I synchronise between all my machines, there's nothing fancy here, just some syntax, line numbers and some other niceties.","4":"This is my base .vimrc that I synchronise between all my machines, there's nothing fancy here, just some syntax, line numbers and some other niceties.","install_details":"download to ~\/.vimrc","5":"download to ~\/.vimrc","first_name":"Tristram","6":"Tristram","last_name":"Oaten","7":"Oaten","releases":[{"0":"3195","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":".vimrc","4":".vimrc","src_id":"13544","5":"13544","creation_date":"1281453637","6":"1281453637"}]},"3194":{"script_id":"3194","0":"3194","script_name":"ovim","1":"ovim","script_type":"utility","2":"utility","summary":"open files in running gvim from a terminal","3":"open files in running gvim from a terminal","description":"ovim is a zsh script that makes it convenient to open files\r\nor execute \"ex\" commands in gvim from a Unix terminal.\r\n\r\nExamples:\r\n\r\nOpen all c files and jump to the first \"main\" string:\r\n    ovim *.c +\/main\r\n\r\nOpen all cpp files that contain the \"sstream\" string:\r\n    grep -l sstream *.cpp | xargs ovim\r\nor\r\n    ovim -c vimgrep sstream *.cpp\r\n\r\nOpen the README.txt file in a new window:\r\n    ovim -c split README.txt\r\n\r\nMake gvim jump to a tag with respect to the \"tags\" file\r\nin the shell directory (try this in \/usr\/share\/vim\/vim72\/doc):\r\n    ovim -c tag \/grail\r\n\r\nChange to the current shell directory in gvim:\r\n    ovim -c cd .\r\n\r\nOpen all txt files in the gvim server MYGVIM.  The server name is\r\ncapitalized thus \"-s mygvim\" is the same as \"-s MYGVIM\":\r\n    ovim -s mygvim *.txt\r\n\r\nMake gvim a bit animated:\r\n    ovim -c \"winpos \"{1..400}\" 1|\"\r\n\r\nFeautures:\r\n\r\n* speed \"gvim --remote f1 f2 f3 ... f50\" could cause about 10 second screen\r\nupdates in some older gvim versions.  With ovim gvim sources a temporary\r\nscript file and avoids such slow downs.\r\n\r\n* intelligent server selection.  ovim attempts to reuse\r\nthe last server used, if it is not running, it will select the last live\r\ngvim server or finally would start new gvim process.  The server\r\nselection can be forced with a \"-s MYSERVER\" option.  Note that this\r\nserver choice is permanent, i.e., subsequent calls of ovim would try\r\nto use the same server.\r\n\r\n* \"ex\" commands are executed in the current shell directory\r\n\"ovim -c split filename\" works even if terminal and the gvim server are\r\nin different directories.  The gvim directory is changed to the terminal\r\ndirectory just before the ex commands execution and then restored back.\r\nThis is done in such way that \"ovim -c cd somewhere\" works as expected.\r\n","4":"ovim is a zsh script that makes it convenient to open files\r\nor execute \"ex\" commands in gvim from a Unix terminal.\r\n\r\nExamples:\r\n\r\nOpen all c files and jump to the first \"main\" string:\r\n    ovim *.c +\/main\r\n\r\nOpen all cpp files that contain the \"sstream\" string:\r\n    grep -l sstream *.cpp | xargs ovim\r\nor\r\n    ovim -c vimgrep sstream *.cpp\r\n\r\nOpen the README.txt file in a new window:\r\n    ovim -c split README.txt\r\n\r\nMake gvim jump to a tag with respect to the \"tags\" file\r\nin the shell directory (try this in \/usr\/share\/vim\/vim72\/doc):\r\n    ovim -c tag \/grail\r\n\r\nChange to the current shell directory in gvim:\r\n    ovim -c cd .\r\n\r\nOpen all txt files in the gvim server MYGVIM.  The server name is\r\ncapitalized thus \"-s mygvim\" is the same as \"-s MYGVIM\":\r\n    ovim -s mygvim *.txt\r\n\r\nMake gvim a bit animated:\r\n    ovim -c \"winpos \"{1..400}\" 1|\"\r\n\r\nFeautures:\r\n\r\n* speed \"gvim --remote f1 f2 f3 ... f50\" could cause about 10 second screen\r\nupdates in some older gvim versions.  With ovim gvim sources a temporary\r\nscript file and avoids such slow downs.\r\n\r\n* intelligent server selection.  ovim attempts to reuse\r\nthe last server used, if it is not running, it will select the last live\r\ngvim server or finally would start new gvim process.  The server\r\nselection can be forced with a \"-s MYSERVER\" option.  Note that this\r\nserver choice is permanent, i.e., subsequent calls of ovim would try\r\nto use the same server.\r\n\r\n* \"ex\" commands are executed in the current shell directory\r\n\"ovim -c split filename\" works even if terminal and the gvim server are\r\nin different directories.  The gvim directory is changed to the terminal\r\ndirectory just before the ex commands execution and then restored back.\r\nThis is done in such way that \"ovim -c cd somewhere\" works as expected.\r\n","install_details":"Copy the script file to $HOME\/bin\/ or to some other directory\r\nin the PATH and make it executable using \"chmod +x ovim\".  \r\nMake sure the zsh shell is installed, it is usually available\r\nas a \"zsh\" package in recent Linux distributions.","5":"Copy the script file to $HOME\/bin\/ or to some other directory\r\nin the PATH and make it executable using \"chmod +x ovim\".  \r\nMake sure the zsh shell is installed, it is usually available\r\nas a \"zsh\" package in recent Linux distributions.","first_name":"Pavol","6":"Pavol","last_name":"Juhas","7":"Juhas","releases":[{"0":"3194","vim_version":"7.0","1":"7.0","script_version":"161","2":"161","version_comment":"Initial upload","3":"Initial upload","package":"ovim","4":"ovim","src_id":"13534","5":"13534","creation_date":"1281414623","6":"1281414623"}]},"3193":{"script_id":"3193","0":"3193","script_name":"v4daemon","1":"v4daemon","script_type":"utility","2":"utility","summary":"Send vim buffer lines to your background daemon (i.e. netcat)","3":"Send vim buffer lines to your background daemon (i.e. netcat)","description":"This script eases sending lines to the ahead-started daemon. I needed and tested it for creating a test server with netcat and send the pre-recorded sentences to the clients:\r\n\r\n:V4dStart nc -l -p 10010\r\n\r\nStarts netcat listening on port 10010. Then you start a client somewhere.\r\nFrom the buffer you are working:\r\n\r\n[Select by v,V,ctrl-v] :V4dSendLine\r\n[Select by v] :V4dSendWord\r\n\r\nSends the line(s) you are on\/selected to the daemon (and pushed to clients in my case).\r\n\r\n:V4dStop\r\n\r\n(-:njoy!\r\n","4":"This script eases sending lines to the ahead-started daemon. I needed and tested it for creating a test server with netcat and send the pre-recorded sentences to the clients:\r\n\r\n:V4dStart nc -l -p 10010\r\n\r\nStarts netcat listening on port 10010. Then you start a client somewhere.\r\nFrom the buffer you are working:\r\n\r\n[Select by v,V,ctrl-v] :V4dSendLine\r\n[Select by v] :V4dSendWord\r\n\r\nSends the line(s) you are on\/selected to the daemon (and pushed to clients in my case).\r\n\r\n:V4dStop\r\n\r\n(-:njoy!\r\n","install_details":"Untar v4daemon into $HOME\/.vim\r\nA helper program will be extracted in .vim\/v4d_sendcmd.sh. Change the path if you want to:\r\n\r\nlet g:v4d_sendcmd_directory = \"somewhere\"\r\n\r\nTodo: - show output from the background process\r\n          - use other utilities (sh, python) as daemon if it is possible\r\n","5":"Untar v4daemon into $HOME\/.vim\r\nA helper program will be extracted in .vim\/v4d_sendcmd.sh. Change the path if you want to:\r\n\r\nlet g:v4d_sendcmd_directory = \"somewhere\"\r\n\r\nTodo: - show output from the background process\r\n          - use other utilities (sh, python) as daemon if it is possible\r\n","first_name":"umit","6":"umit","last_name":"kablan","7":"kablan","releases":[{"0":"3193","vim_version":"6.0","1":"6.0","script_version":"0.2","2":"0.2","version_comment":"Removed V4dSendVisual. Now V4dSendLine is enough.\r\nAdded V4dSendWord for visual character-wide selection.","3":"Removed V4dSendVisual. Now V4dSendLine is enough.\r\nAdded V4dSendWord for visual character-wide selection.","package":"v4daemon.tar.gz","4":"v4daemon.tar.gz","src_id":"13600","5":"13600","creation_date":"1282038874","6":"1282038874"},{"0":"3193","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"v4daemon.tar.gz","4":"v4daemon.tar.gz","src_id":"13523","5":"13523","creation_date":"1281287756","6":"1281287756"}]},"3192":{"script_id":"3192","0":"3192","script_name":"jade.vim","1":"jade.vim","script_type":"syntax","2":"syntax","summary":"Jade syntax and indenting","3":"Jade syntax and indenting","description":"Runtime files for the Jade template engine.","4":"Runtime files for the Jade template engine.","install_details":"Exract to ~\/.vim","5":"Exract to ~\/.vim","first_name":"Joshua","6":"Joshua","last_name":"Borton","7":"Borton","releases":[{"0":"3192","vim_version":"7.0","1":"7.0","script_version":"1.1","2":"1.1","version_comment":"Added pipe continuation for script blocks.","3":"Added pipe continuation for script blocks.","package":"jade.zip","4":"jade.zip","src_id":"13895","5":"13895","creation_date":"1285264548","6":"1285264548"},{"0":"3192","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Fixed the empty archive.","3":"Fixed the empty archive.","package":"jade.zip","4":"jade.zip","src_id":"13703","5":"13703","creation_date":"1283017436","6":"1283017436"}]},"3191":{"script_id":"3191","0":"3191","script_name":"DokuVimKi","1":"DokuVimKi","script_type":"utility","2":"utility","summary":"Allows to edit DokuWiki pages via XMLRPC","3":"Allows to edit DokuWiki pages via XMLRPC","description":"This plugin allows you to edit wiki pages of a remote DokuWiki [1] instance using the DokuWiki XMLRPC API. \r\n\r\nFor more information please visit  http:\/\/www.chimeric.de\/projects\/dokuwiki\/dokuvimki\r\n\r\n[1] http:\/\/dokuwiki.org","4":"This plugin allows you to edit wiki pages of a remote DokuWiki [1] instance using the DokuWiki XMLRPC API. \r\n\r\nFor more information please visit  http:\/\/www.chimeric.de\/projects\/dokuwiki\/dokuvimki\r\n\r\n[1] http:\/\/dokuwiki.org","install_details":"Unpack into your ~\/.vim folder. You'll need vim with python support enabled, a recent development snapshot of DokuWiki and the dokuwikixmlrpc python module (install using easy_install).","5":"Unpack into your ~\/.vim folder. You'll need vim with python support enabled, a recent development snapshot of DokuWiki and the dokuwikixmlrpc python module (install using easy_install).","first_name":"Michael","6":"Michael","last_name":"Klier","7":"Klier","releases":[{"0":"3191","vim_version":"7.0","1":"7.0","script_version":"20100806","2":"20100806","version_comment":"Initial upload","3":"Initial upload","package":"dokuvimki.tgz","4":"dokuvimki.tgz","src_id":"13501","5":"13501","creation_date":"1281089128","6":"1281089128"}]},"3190":{"script_id":"3190","0":"3190","script_name":"yamlvim","1":"yamlvim","script_type":"utility","2":"utility","summary":"YAML dumper\/emitter in pure vimscript","3":"YAML dumper\/emitter in pure vimscript","description":"This is the library that is able to represent arbitrary Vim data in YAML 1.2. It also provides a parser that is python YAML parser pyyaml rewritten in pure vimscript.\r\n\r\nDocumentation: http:\/\/vimcommunity.bitbucket.org\/doc\/yaml.txt.html\r\nProject page: https:\/\/bitbucket.org\/ZyX_I\/yamlvim\r\nDependencies (you do not need to install them by yourself, see installation details):\r\nvimscript #3631, https:\/\/bitbucket.org\/ZyX_I\/frawor\r\nvimscript #3189, https:\/\/bitbucket.org\/ZyX_I\/vimoop","4":"This is the library that is able to represent arbitrary Vim data in YAML 1.2. It also provides a parser that is python YAML parser pyyaml rewritten in pure vimscript.\r\n\r\nDocumentation: http:\/\/vimcommunity.bitbucket.org\/doc\/yaml.txt.html\r\nProject page: https:\/\/bitbucket.org\/ZyX_I\/yamlvim\r\nDependencies (you do not need to install them by yourself, see installation details):\r\nvimscript #3631, https:\/\/bitbucket.org\/ZyX_I\/frawor\r\nvimscript #3189, https:\/\/bitbucket.org\/ZyX_I\/vimoop","install_details":"You can install this plugin using vim-addon-manager (vimscript #2905) plugin (install vim-addon-manager, run \u00e2\u0080\u009cActivateAddons yamlvim\u00e2\u0080\u009d and add \u00e2\u0080\u009ccall vam#ActivateAddons([\"yamlvim\"])\u00e2\u0080\u009d to your .vimrc. Vim-addon-manager will install all dependencies for you). You can also use archives attached to this page, they contain plugin with all dependencies, so you do not need to fetch them yourself.\r\n\r\nGentoo users can use the following mercurial overlay: http:\/\/bitbucket.org\/ZyX_I\/pluginloader-overlay.","5":"You can install this plugin using vim-addon-manager (vimscript #2905) plugin (install vim-addon-manager, run \u00e2\u0080\u009cActivateAddons yamlvim\u00e2\u0080\u009d and add \u00e2\u0080\u009ccall vam#ActivateAddons([\"yamlvim\"])\u00e2\u0080\u009d to your .vimrc. Vim-addon-manager will install all dependencies for you). You can also use archives attached to this page, they contain plugin with all dependencies, so you do not need to fetch them yourself.\r\n\r\nGentoo users can use the following mercurial overlay: http:\/\/bitbucket.org\/ZyX_I\/pluginloader-overlay.","first_name":"ZyX","6":"ZyX","last_name":" ","7":" ","releases":[{"0":"3190","vim_version":"7.3","1":"7.3","script_version":"2.1.1","2":"2.1.1","version_comment":"Made it follow vimoop file location change","3":"Made it follow vimoop file location change","package":"yamlvim-2.1.1.tar.gz","4":"yamlvim-2.1.1.tar.gz","src_id":"19145","5":"19145","creation_date":"1354971363","6":"1354971363"},{"0":"3190","vim_version":"7.3","1":"7.3","script_version":"2.1","2":"2.1","version_comment":"Splitted everything into a number of files, slightly improved documentation","3":"Splitted everything into a number of files, slightly improved documentation","package":"yamlvim-2.1.tar.gz","4":"yamlvim-2.1.tar.gz","src_id":"19135","5":"19135","creation_date":"1354920036","6":"1354920036"},{"0":"3190","vim_version":"7.3","1":"7.3","script_version":"2.0.1","2":"2.0.1","version_comment":"Added `\\\/' escape sequence\nFixed \\N and \\_ escapes","3":"Added `\\\/' escape sequence\nFixed \\N and \\_ escapes","package":"yamlvim-2.0.1.tar.gz","4":"yamlvim-2.0.1.tar.gz","src_id":"16807","5":"16807","creation_date":"1320490383","6":"1320490383"},{"0":"3190","vim_version":"7.3","1":"7.3","script_version":"2.0","2":"2.0","version_comment":"Ported plugin to frawor","3":"Ported plugin to frawor","package":"yamlvim-2.0.tar.gz","4":"yamlvim-2.0.tar.gz","src_id":"15985","5":"15985","creation_date":"1309115079","6":"1309115079"},{"0":"3190","vim_version":"7.3","1":"7.3","script_version":"1.5.3","2":"1.5.3","version_comment":"Fixed bugs with loading diacritics and modifying opts dictionary passed to dumper","3":"Fixed bugs with loading diacritics and modifying opts dictionary passed to dumper","package":"yamlvim-1.5.3.tar.gz","4":"yamlvim-1.5.3.tar.gz","src_id":"14723","5":"14723","creation_date":"1294665433","6":"1294665433"},{"0":"3190","vim_version":"9999","1":"9999","script_version":"1.5.2","2":"1.5.2","version_comment":"Reposting bundle due to core plugins update","3":"Reposting bundle due to core plugins update","package":"yamlvim-1.5.2.tar.gz","4":"yamlvim-1.5.2.tar.gz","src_id":"14565","5":"14565","creation_date":"1292713518","6":"1292713518"},{"0":"3190","vim_version":"9999","1":"9999","script_version":"1.5.2","2":"1.5.2","version_comment":"Reposting bundle due to core plugins update","3":"Reposting bundle due to core plugins update","package":"yamlvim-1.5.2.tar.gz","4":"yamlvim-1.5.2.tar.gz","src_id":"14318","5":"14318","creation_date":"1290257901","6":"1290257901"},{"0":"3190","vim_version":"7.2","1":"7.2","script_version":"1.5.2","2":"1.5.2","version_comment":"Minor fix: removed escaping of `[' inside a collection","3":"Minor fix: removed escaping of `[' inside a collection","package":"yamlvim-1.5.2.tar.gz","4":"yamlvim-1.5.2.tar.gz","src_id":"14314","5":"14314","creation_date":"1290254321","6":"1290254321"},{"0":"3190","vim_version":"7.2","1":"7.2","script_version":"1.5","2":"1.5","version_comment":"Added scalar style chooser that is able to use any scalar style\nAdded ability to dump strings with non-utf characters\nImproved pyyaml compatibility\nNeither dumper nor loader depends on vim's `\\p' pattern (improved standart conformance)\nSome bug fixes","3":"Added scalar style chooser that is able to use any scalar style\nAdded ability to dump strings with non-utf characters\nImproved pyyaml compatibility\nNeither dumper nor loader depends on vim's `\\p' pattern (improved standart conformance)\nSome bug fixes","package":"yamlvim-1.5.tar.gz","4":"yamlvim-1.5.tar.gz","src_id":"14058","5":"14058","creation_date":"1287138539","6":"1287138539"},{"0":"3190","vim_version":"7.2","1":"7.2","script_version":"1.4.5","2":"1.4.5","version_comment":"Some bug fixes. Known bug: it is not able to dump strings with invalid (non-utf8) characters","3":"Some bug fixes. Known bug: it is not able to dump strings with invalid (non-utf8) characters","package":"yamlvim-1.4.5.tar.gz","4":"yamlvim-1.4.5.tar.gz","src_id":"13984","5":"13984","creation_date":"1286137969","6":"1286137969"},{"0":"3190","vim_version":"7.2","1":"7.2","script_version":"1.4.4","2":"1.4.4","version_comment":"Added all_flow dumper option, made memory leak much less huge","3":"Added all_flow dumper option, made memory leak much less huge","package":"yamlvim-1.4.4.tar.gz","4":"yamlvim-1.4.4.tar.gz","src_id":"13916","5":"13916","creation_date":"1285417478","6":"1285417478"},{"0":"3190","vim_version":"7.2","1":"7.2","script_version":"1.4.3","2":"1.4.3","version_comment":"Fixed some dumper errors","3":"Fixed some dumper errors","package":"yamlvim-1.4.3.tar.gz","4":"yamlvim-1.4.3.tar.gz","src_id":"13864","5":"13864","creation_date":"1284848517","6":"1284848517"},{"0":"3190","vim_version":"7.2","1":"7.2","script_version":"1.4","2":"1.4","version_comment":"Added YAML syntax file","3":"Added YAML syntax file","package":"yamlvim-1.4.tar.gz","4":"yamlvim-1.4.tar.gz","src_id":"13789","5":"13789","creation_date":"1284007654","6":"1284007654"},{"0":"3190","vim_version":"7.2","1":"7.2","script_version":"1.3.3","2":"1.3.3","version_comment":"Lots of bugfixes, improved tests","3":"Lots of bugfixes, improved tests","package":"yamlvim-1.3.3.tar.gz","4":"yamlvim-1.3.3.tar.gz","src_id":"13642","5":"13642","creation_date":"1282480905","6":"1282480905"},{"0":"3190","vim_version":"7.2","1":"7.2","script_version":"1.3.2","2":"1.3.2","version_comment":"Added ability to sort dictionary keys before dumping","3":"Added ability to sort dictionary keys before dumping","package":"yamlvim-1.3.2.tar.gz","4":"yamlvim-1.3.2.tar.gz","src_id":"13604","5":"13604","creation_date":"1282072243","6":"1282072243"},{"0":"3190","vim_version":"7.2","1":"7.2","script_version":"1.3.1","2":"1.3.1","version_comment":"Added locked variables dumping\/loading (it means saving and restoring locks information), added dumping with custom tags, some bug fixes","3":"Added locked variables dumping\/loading (it means saving and restoring locks information), added dumping with custom tags, some bug fixes","package":"yamlvim-1.3.1.tar.gz","4":"yamlvim-1.3.1.tar.gz","src_id":"13568","5":"13568","creation_date":"1281808164","6":"1281808164"},{"0":"3190","vim_version":"7.2","1":"7.2","script_version":"1.2","2":"1.2","version_comment":"Added documentation, added add_*constructor and del_*constructor functions, some bug fixes","3":"Added documentation, added add_*constructor and del_*constructor functions, some bug fixes","package":"yamlvim-1.2.tar.gz","4":"yamlvim-1.2.tar.gz","src_id":"13548","5":"13548","creation_date":"1281547777","6":"1281547777"},{"0":"3190","vim_version":"7.2","1":"7.2","script_version":"1.1.1","2":"1.1.1","version_comment":"More bug fixes","3":"More bug fixes","package":"yamlvim-1.1.1.tar.gz","4":"yamlvim-1.1.1.tar.gz","src_id":"13546","5":"13546","creation_date":"1281521794","6":"1281521794"},{"0":"3190","vim_version":"7.2","1":"7.2","script_version":"1.1","2":"1.1","version_comment":"Added load_all function, some bug fixes","3":"Added load_all function, some bug fixes","package":"yamlvim-1.1.tar.gz","4":"yamlvim-1.1.tar.gz","src_id":"13530","5":"13530","creation_date":"1281388119","6":"1281388119"},{"0":"3190","vim_version":"7.2","1":"7.2","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"yamlvim-1.0.tar.xz","4":"yamlvim-1.0.tar.xz","src_id":"13489","5":"13489","creation_date":"1280952145","6":"1280952145"}]},"3189":{"script_id":"3189","0":"3189","script_name":"vimoop","1":"vimoop","script_type":"utility","2":"utility","summary":"Adds some features of Python OOP model to vim.","3":"Adds some features of Python OOP model to vim.","description":"Provides inheritance, uses __init__ function as a constructor. This plugin was used to create YAML parser (vimscript #3190) by rewriting Python code in vimscript.\r\n\r\nDocumentation: http:\/\/vimcommunity.bitbucket.org\/doc\/oop.txt.html\r\nProject page: https:\/\/bitbucket.org\/ZyX_I\/vimoop\r\nDependencies (you do not need to install them by yourself, see installation details):\r\nvimscript #3631, https:\/\/bitbucket.org\/ZyX_I\/frawor","4":"Provides inheritance, uses __init__ function as a constructor. This plugin was used to create YAML parser (vimscript #3190) by rewriting Python code in vimscript.\r\n\r\nDocumentation: http:\/\/vimcommunity.bitbucket.org\/doc\/oop.txt.html\r\nProject page: https:\/\/bitbucket.org\/ZyX_I\/vimoop\r\nDependencies (you do not need to install them by yourself, see installation details):\r\nvimscript #3631, https:\/\/bitbucket.org\/ZyX_I\/frawor","install_details":"You can install this plugin using vim-addon-manager (vimscript #2905) plugin (install vim-addon-manager, run \u00e2\u0080\u009cActivateAddons jsonvim\u00e2\u0080\u009d and add \u00e2\u0080\u009ccall vam#ActivateAddons([\"jsonvim\"])\u00e2\u0080\u009d to your .vimrc. Vim-addon-manager will install all dependencies for you). You can also use archives attached to this page, they contain plugin with all dependencies, so you do not need to fetch them yourself.\r\n\r\nGentoo users can use the following mercurial overlay: https:\/\/bitbucket.org\/ZyX_I\/pluginloader-overlay.","5":"You can install this plugin using vim-addon-manager (vimscript #2905) plugin (install vim-addon-manager, run \u00e2\u0080\u009cActivateAddons jsonvim\u00e2\u0080\u009d and add \u00e2\u0080\u009ccall vam#ActivateAddons([\"jsonvim\"])\u00e2\u0080\u009d to your .vimrc. Vim-addon-manager will install all dependencies for you). You can also use archives attached to this page, they contain plugin with all dependencies, so you do not need to fetch them yourself.\r\n\r\nGentoo users can use the following mercurial overlay: https:\/\/bitbucket.org\/ZyX_I\/pluginloader-overlay.","first_name":"ZyX","6":"ZyX","last_name":" ","7":" ","releases":[{"0":"3189","vim_version":"7.3","1":"7.3","script_version":"2.1.1","2":"2.1.1","version_comment":"Remove third argument to frawor#Setup","3":"Remove third argument to frawor#Setup","package":"vimoop-2.1.1.tar.gz","4":"vimoop-2.1.1.tar.gz","src_id":"20864","5":"20864","creation_date":"1380602040","6":"1380602040"},{"0":"3189","vim_version":"7.3","1":"7.3","script_version":"2.1","2":"2.1","version_comment":"Moved plugin\/oop.vim to autoload\/oop.vim","3":"Moved plugin\/oop.vim to autoload\/oop.vim","package":"vimoop-2.1.tar.gz","4":"vimoop-2.1.tar.gz","src_id":"19143","5":"19143","creation_date":"1354970934","6":"1354970934"},{"0":"3189","vim_version":"7.3","1":"7.3","script_version":"2.0","2":"2.0","version_comment":"Ported plugin to frawor, officially added instanceof function","3":"Ported plugin to frawor, officially added instanceof function","package":"vimoop-2.0.tar.gz","4":"vimoop-2.0.tar.gz","src_id":"15983","5":"15983","creation_date":"1309101293","6":"1309101293"},{"0":"3189","vim_version":"9999","1":"9999","script_version":"1.1.2","2":"1.1.2","version_comment":"Reposting bundle due to core plugins update","3":"Reposting bundle due to core plugins update","package":"vimoop-1.1.2.tar.gz","4":"vimoop-1.1.2.tar.gz","src_id":"14572","5":"14572","creation_date":"1292713567","6":"1292713567"},{"0":"3189","vim_version":"9999","1":"9999","script_version":"1.1.2","2":"1.1.2","version_comment":"Reposting bundle due to core plugins update","3":"Reposting bundle due to core plugins update","package":"vimoop-1.1.2.tar.gz","4":"vimoop-1.1.2.tar.gz","src_id":"14326","5":"14326","creation_date":"1290257942","6":"1290257942"},{"0":"3189","vim_version":"7.2","1":"7.2","script_version":"1.1.2","2":"1.1.2","version_comment":"Added documentation","3":"Added documentation","package":"vimoop-1.1.2.tar.gz","4":"vimoop-1.1.2.tar.gz","src_id":"13813","5":"13813","creation_date":"1284247835","6":"1284247835"},{"0":"3189","vim_version":"7.2","1":"7.2","script_version":"1.1.1","2":"1.1.1","version_comment":"Added default exception message","3":"Added default exception message","package":"vimoop-1.1.1.tar.gz","4":"vimoop-1.1.1.tar.gz","src_id":"13569","5":"13569","creation_date":"1281808727","6":"1281808727"},{"0":"3189","vim_version":"7.2","1":"7.2","script_version":"1.1","2":"1.1","version_comment":"Added Exception built-in class, commented out list of instances attached to the class, so that garbage collector could free them.","3":"Added Exception built-in class, commented out list of instances attached to the class, so that garbage collector could free them.","package":"vimoop-1.1.tar.gz","4":"vimoop-1.1.tar.gz","src_id":"13537","5":"13537","creation_date":"1281415278","6":"1281415278"},{"0":"3189","vim_version":"7.2","1":"7.2","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"vimoop-1.0.tar.xz","4":"vimoop-1.0.tar.xz","src_id":"13481","5":"13481","creation_date":"1280951398","6":"1280951398"}]},"3188":{"script_id":"3188","0":"3188","script_name":"vimcompcrtr","1":"vimcompcrtr","script_type":"utility","2":"utility","summary":"Script that makes creating completion functions much easier.","3":"Script that makes creating completion functions much easier.","description":"**This plugin is deprecated. Use FWC DSL provided by frawor (vimscript #3631) instead**\r\n\r\nThis plugin makes creating custom completion functions much easier.\r\n\r\nFeatures:\r\n    \u00e2\u0080\u0094 Ability to get variants from list and from dictionary keys\r\n    \u00e2\u0080\u0094 Ability to get variants from custom function\r\n    \u00e2\u0080\u0094 Allows modifying the completion description\r\n\r\nDocumentation: http:\/\/vimpluginloader.sourceforge.net\/doc\/comp.txt.html\r\nProject page: http:\/\/sourceforge.net\/projects\/vimcompcrtr\r\nDependencies (you do not need to install them by yourself, see installation details):\r\nvimscript #3184, http:\/\/sourceforge.net\/projects\/vimpluginloader\r\nvimscript #3186, http:\/\/sourceforge.net\/projects\/vimstuff\r\nvimscript #3187, http:\/\/sourceforge.net\/projects\/vimargumentchec\r\nvimscript #3325, http:\/\/bitbucket.org\/ZyX_I\/vim-fileutils\/overview","4":"**This plugin is deprecated. Use FWC DSL provided by frawor (vimscript #3631) instead**\r\n\r\nThis plugin makes creating custom completion functions much easier.\r\n\r\nFeatures:\r\n    \u00e2\u0080\u0094 Ability to get variants from list and from dictionary keys\r\n    \u00e2\u0080\u0094 Ability to get variants from custom function\r\n    \u00e2\u0080\u0094 Allows modifying the completion description\r\n\r\nDocumentation: http:\/\/vimpluginloader.sourceforge.net\/doc\/comp.txt.html\r\nProject page: http:\/\/sourceforge.net\/projects\/vimcompcrtr\r\nDependencies (you do not need to install them by yourself, see installation details):\r\nvimscript #3184, http:\/\/sourceforge.net\/projects\/vimpluginloader\r\nvimscript #3186, http:\/\/sourceforge.net\/projects\/vimstuff\r\nvimscript #3187, http:\/\/sourceforge.net\/projects\/vimargumentchec\r\nvimscript #3325, http:\/\/bitbucket.org\/ZyX_I\/vim-fileutils\/overview","install_details":"You can install this plugin using scriptmanager (vimscript #2905) plugin (install scriptmanager, run ``ActivateAddons vimpluginloader'' and add ``call vam#ActivateAddons([\"vimpluginloader\"])'' to your .vimrc. Vim-addon-manager will install all dependencies for you). You can also use archives attached to this page, they contain plugin with all dependencies, so you do not need to fetch them yourself. Note that vimscript #3186's and this plugin's archives contain the same files.\r\n\r\nGentoo users can use the following mercurial overlay: http:\/\/vimpluginloader.hg.sourceforge.net:8000\/hgroot\/vimpluginloader\/pluginloader-overlay.","5":"You can install this plugin using scriptmanager (vimscript #2905) plugin (install scriptmanager, run ``ActivateAddons vimpluginloader'' and add ``call vam#ActivateAddons([\"vimpluginloader\"])'' to your .vimrc. Vim-addon-manager will install all dependencies for you). You can also use archives attached to this page, they contain plugin with all dependencies, so you do not need to fetch them yourself. Note that vimscript #3186's and this plugin's archives contain the same files.\r\n\r\nGentoo users can use the following mercurial overlay: http:\/\/vimpluginloader.hg.sourceforge.net:8000\/hgroot\/vimpluginloader\/pluginloader-overlay.","first_name":"ZyX","6":"ZyX","last_name":" ","7":" ","releases":[{"0":"3188","vim_version":"7.3","1":"7.3","script_version":"1.5.3","2":"1.5.3","version_comment":"Fixed two bugs:\nCompleting of all no* alternatives\nNot completing the only possible prefix if prefix truncating is allowed","3":"Fixed two bugs:\nCompleting of all no* alternatives\nNot completing the only possible prefix if prefix truncating is allowed","package":"vimcompcrtr-1.5.3.tar.gz","4":"vimcompcrtr-1.5.3.tar.gz","src_id":"14573","5":"14573","creation_date":"1292726478","6":"1292726478"},{"0":"3188","vim_version":"9999","1":"9999","script_version":"1.5.2","2":"1.5.2","version_comment":"Reposting bundle due to core plugins update","3":"Reposting bundle due to core plugins update","package":"vimcompcrtr-1.5.2.tar.gz","4":"vimcompcrtr-1.5.2.tar.gz","src_id":"14570","5":"14570","creation_date":"1292713554","6":"1292713554"},{"0":"3188","vim_version":"7.3","1":"7.3","script_version":"1.5.2","2":"1.5.2","version_comment":"Added alternating prefixes support","3":"Added alternating prefixes support","package":"vimcompcrtr-1.5.2.tar.gz","4":"vimcompcrtr-1.5.2.tar.gz","src_id":"14563","5":"14563","creation_date":"1292713480","6":"1292713480"},{"0":"3188","vim_version":"7.3","1":"7.3","script_version":"1.5","2":"1.5","version_comment":"Greatly improved `pref' model","3":"Greatly improved `pref' model","package":"vimcompcrtr-1.5.tar.gz","4":"vimcompcrtr-1.5.tar.gz","src_id":"14524","5":"14524","creation_date":"1292447489","6":"1292447489"},{"0":"3188","vim_version":"7.3","1":"7.3","script_version":"1.3.3","2":"1.3.3","version_comment":"Made pref model less strict about prefixes","3":"Made pref model less strict about prefixes","package":"vimcompcrtr-1.3.3.tar.gz","4":"vimcompcrtr-1.3.3.tar.gz","src_id":"14489","5":"14489","creation_date":"1292182825","6":"1292182825"},{"0":"3188","vim_version":"7.3","1":"7.3","script_version":"1.3.2","2":"1.3.2","version_comment":"Made `escape' escape less characters by default","3":"Made `escape' escape less characters by default","package":"vimcompcrtr-1.3.2.tar.gz","4":"vimcompcrtr-1.3.2.tar.gz","src_id":"14374","5":"14374","creation_date":"1290704297","6":"1290704297"},{"0":"3188","vim_version":"7.3","1":"7.3","script_version":"1.3.1","2":"1.3.1","version_comment":"Fixed file completion","3":"Fixed file completion","package":"vimcompcrtr-1.3.1.tar.gz","4":"vimcompcrtr-1.3.1.tar.gz","src_id":"14373","5":"14373","creation_date":"1290703832","6":"1290703832"},{"0":"3188","vim_version":"7.3","1":"7.3","script_version":"1.3","2":"1.3","version_comment":"!!! Changed `file' argument description syntax\nAdded =file and =file! argument descriptions (see documenation)","3":"!!! Changed `file' argument description syntax\nAdded =file and =file! argument descriptions (see documenation)","package":"vimcompcrtr-1.3.tar.gz","4":"vimcompcrtr-1.3.tar.gz","src_id":"14343","5":"14343","creation_date":"1290376033","6":"1290376033"},{"0":"3188","vim_version":"7.3","1":"7.3","script_version":"1.2.3","2":"1.2.3","version_comment":"Made file completion not prepend .\/ when completing empty string","3":"Made file completion not prepend .\/ when completing empty string","package":"vimcompcrtr-1.2.3.tar.gz","4":"vimcompcrtr-1.2.3.tar.gz","src_id":"14336","5":"14336","creation_date":"1290338133","6":"1290338133"},{"0":"3188","vim_version":"7.3","1":"7.3","script_version":"1.2.2","2":"1.2.2","version_comment":"Various file completion fixes","3":"Various file completion fixes","package":"vimcompcrtr-1.2.2.tar.gz","4":"vimcompcrtr-1.2.2.tar.gz","src_id":"14331","5":"14331","creation_date":"1290283286","6":"1290283286"},{"0":"3188","vim_version":"9999","1":"9999","script_version":"1.2.1","2":"1.2.1","version_comment":"Reposting bundle due to core plugins update","3":"Reposting bundle due to core plugins update","package":"vimcompcrtr-1.2.1.tar.gz","4":"vimcompcrtr-1.2.1.tar.gz","src_id":"14324","5":"14324","creation_date":"1290257932","6":"1290257932"},{"0":"3188","vim_version":"7.3","1":"7.3","script_version":"1.2.1","2":"1.2.1","version_comment":"Added TrailingSeparator option (affects directory completion)","3":"Added TrailingSeparator option (affects directory completion)","package":"vimcompcrtr-1.2.1.tar.gz","4":"vimcompcrtr-1.2.1.tar.gz","src_id":"14259","5":"14259","creation_date":"1289751550","6":"1289751550"},{"0":"3188","vim_version":"7.2","1":"7.2","script_version":"1.2","2":"1.2","version_comment":"Improved filename completion, added insert mode completion support","3":"Improved filename completion, added insert mode completion support","package":"vimcompcrtr-1.2.tar.gz","4":"vimcompcrtr-1.2.tar.gz","src_id":"14220","5":"14220","creation_date":"1289364677","6":"1289364677"},{"0":"3188","vim_version":"7.2","1":"7.2","script_version":"1.1.1","2":"1.1.1","version_comment":"Fixed filename completion","3":"Fixed filename completion","package":"vimcompcrtr-1.1.1.tar.gz","4":"vimcompcrtr-1.1.1.tar.gz","src_id":"13804","5":"13804","creation_date":"1284150781","6":"1284150781"},{"0":"3188","vim_version":"7.2","1":"7.2","script_version":"1.1","2":"1.1","version_comment":"Added input() completion support and simple `words' model (argument model that ignores context)","3":"Added input() completion support and simple `words' model (argument model that ignores context)","package":"vimcompcrtr-1.1.tar.gz","4":"vimcompcrtr-1.1.tar.gz","src_id":"13695","5":"13695","creation_date":"1282922987","6":"1282922987"},{"0":"3188","vim_version":"7.2","1":"7.2","script_version":"1.0.1","2":"1.0.1","version_comment":"Fixed dependency list","3":"Fixed dependency list","package":"vimcompcrtr-1.0.1.tar.gz","4":"vimcompcrtr-1.0.1.tar.gz","src_id":"13666","5":"13666","creation_date":"1282666714","6":"1282666714"},{"0":"3188","vim_version":"7.2","1":"7.2","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"vimcompcrtr-1.0.tar.gz","4":"vimcompcrtr-1.0.tar.gz","src_id":"13643","5":"13643","creation_date":"1282481123","6":"1282481123"},{"0":"3188","vim_version":"7.2","1":"7.2","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"vimcompcrtr-1.0.tar.xz","4":"vimcompcrtr-1.0.tar.xz","src_id":"13483","5":"13483","creation_date":"1280951544","6":"1280951544"}]},"3187":{"script_id":"3187","0":"3187","script_name":"vimargumentchec","1":"vimargumentchec","script_type":"utility","2":"utility","summary":"Library that helps to check function and command arguments.","3":"Library that helps to check function and command arguments.","description":"**This plugin is deprecated. Use FWC DSL provided by frawor (vimscript #3631) instead**\r\n\r\nThis plugin provides the ability to check whether function or command\r\narguments match specific model or whether some value matches specific model.\r\n\r\nFeatures:\r\n    \u00e2\u0080\u0094 Checks a list of arguments against specified model\r\n    \u00e2\u0080\u0094 Checks a single value against specified model\r\n    \u00e2\u0080\u0094 Provides a way to specify default values for optional arguments\r\n    \u00e2\u0080\u0094 Provides a way to check a single value, convert it, and check again\r\n\r\nDocumentation: http:\/\/vimpluginloader.sourceforge.net\/doc\/chk.txt.html\r\nProject page: http:\/\/sourceforge.net\/projects\/vimargumentchec\r\nDependencies (you do not need to install them by yourself, see installation details):\r\nvimscript #3184, http:\/\/sourceforge.net\/projects\/vimpluginloader","4":"**This plugin is deprecated. Use FWC DSL provided by frawor (vimscript #3631) instead**\r\n\r\nThis plugin provides the ability to check whether function or command\r\narguments match specific model or whether some value matches specific model.\r\n\r\nFeatures:\r\n    \u00e2\u0080\u0094 Checks a list of arguments against specified model\r\n    \u00e2\u0080\u0094 Checks a single value against specified model\r\n    \u00e2\u0080\u0094 Provides a way to specify default values for optional arguments\r\n    \u00e2\u0080\u0094 Provides a way to check a single value, convert it, and check again\r\n\r\nDocumentation: http:\/\/vimpluginloader.sourceforge.net\/doc\/chk.txt.html\r\nProject page: http:\/\/sourceforge.net\/projects\/vimargumentchec\r\nDependencies (you do not need to install them by yourself, see installation details):\r\nvimscript #3184, http:\/\/sourceforge.net\/projects\/vimpluginloader","install_details":"You can install this plugin using scriptmanager (vimscript #2905) plugin (install scriptmanager, run ``ActivateAddons vimpluginloader'' and add ``call vam#ActivateAddons([\"vimpluginloader\"])'' to your .vimrc. Vim-addon-manager will install all dependencies for you). You can also use archives attached to this page, they contain plugin with all dependencies, so you do not need to fetch them yourself. Note that vimscript #3186's and this plugin's archives contain the same files.\r\n\r\nGentoo users can use the following mercurial overlay: http:\/\/vimpluginloader.hg.sourceforge.net:8000\/hgroot\/vimpluginloader\/pluginloader-overlay.","5":"You can install this plugin using scriptmanager (vimscript #2905) plugin (install scriptmanager, run ``ActivateAddons vimpluginloader'' and add ``call vam#ActivateAddons([\"vimpluginloader\"])'' to your .vimrc. Vim-addon-manager will install all dependencies for you). You can also use archives attached to this page, they contain plugin with all dependencies, so you do not need to fetch them yourself. Note that vimscript #3186's and this plugin's archives contain the same files.\r\n\r\nGentoo users can use the following mercurial overlay: http:\/\/vimpluginloader.hg.sourceforge.net:8000\/hgroot\/vimpluginloader\/pluginloader-overlay.","first_name":"ZyX","6":"ZyX","last_name":" ","7":" ","releases":[{"0":"3187","vim_version":"7.3","1":"7.3","script_version":"1.1.1","2":"1.1.1","version_comment":"Bug fixes, some refactoring","3":"Bug fixes, some refactoring","package":"vimargumentchec-1.1.1.tar.gz","4":"vimargumentchec-1.1.1.tar.gz","src_id":"14674","5":"14674","creation_date":"1294054733","6":"1294054733"},{"0":"3187","vim_version":"9999","1":"9999","script_version":"1.1","2":"1.1","version_comment":"Reposting bundle due to core plugins update","3":"Reposting bundle due to core plugins update","package":"vimargumentchec-1.1.tar.gz","4":"vimargumentchec-1.1.tar.gz","src_id":"14568","5":"14568","creation_date":"1292713539","6":"1292713539"},{"0":"3187","vim_version":"7.3","1":"7.3","script_version":"1.1","2":"1.1","version_comment":"Added alternating prefixes, some fixes","3":"Added alternating prefixes, some fixes","package":"vimargumentchec-1.1.tar.gz","4":"vimargumentchec-1.1.tar.gz","src_id":"14535","5":"14535","creation_date":"1292525961","6":"1292525961"},{"0":"3187","vim_version":"7.3","1":"7.3","script_version":"1.0.13","2":"1.0.13","version_comment":"Fixed bug in optlst check","3":"Fixed bug in optlst check","package":"vimargumentchec-1.0.13.tar.gz","4":"vimargumentchec-1.0.13.tar.gz","src_id":"14491","5":"14491","creation_date":"1292183757","6":"1292183757"},{"0":"3187","vim_version":"9999","1":"9999","script_version":"1.0.12","2":"1.0.12","version_comment":"Reposting bundle due to core plugins update","3":"Reposting bundle due to core plugins update","package":"vimargumentchec-1.0.12.tar.gz","4":"vimargumentchec-1.0.12.tar.gz","src_id":"14322","5":"14322","creation_date":"1290257921","6":"1290257921"},{"0":"3187","vim_version":"7.2","1":"7.2","script_version":"1.0.12","2":"1.0.12","version_comment":"Made `eval' and `func' checks more safe","3":"Made `eval' and `func' checks more safe","package":"vimargumentchec-1.0.12.tar.gz","4":"vimargumentchec-1.0.12.tar.gz","src_id":"13934","5":"13934","creation_date":"1285586340","6":"1285586340"},{"0":"3187","vim_version":"7.2","1":"7.2","script_version":"1.0.11","2":"1.0.11","version_comment":"Added `optlst' check (checks optional items in list)","3":"Added `optlst' check (checks optional items in list)","package":"vimargumentchec-1.0.11.tar.gz","4":"vimargumentchec-1.0.11.tar.gz","src_id":"13917","5":"13917","creation_date":"1285434872","6":"1285434872"},{"0":"3187","vim_version":"7.2","1":"7.2","script_version":"1.0.10","2":"1.0.10","version_comment":"Fixed `func' transformation","3":"Fixed `func' transformation","package":"vimargumentchec-1.0.10.tar.gz","4":"vimargumentchec-1.0.10.tar.gz","src_id":"13822","5":"13822","creation_date":"1284462196","6":"1284462196"},{"0":"3187","vim_version":"7.2","1":"7.2","script_version":"1.0.9","2":"1.0.9","version_comment":"Improved error messages","3":"Improved error messages","package":"vimargumentchec-1.0.9.tar.gz","4":"vimargumentchec-1.0.9.tar.gz","src_id":"13811","5":"13811","creation_date":"1284243379","6":"1284243379"},{"0":"3187","vim_version":"7.2","1":"7.2","script_version":"1.0.8","2":"1.0.8","version_comment":"Added `next' key to `optional' model: it may be used to describe non-fixed number of optional arguments","3":"Added `next' key to `optional' model: it may be used to describe non-fixed number of optional arguments","package":"vimargumentchec-1.0.8.tar.gz","4":"vimargumentchec-1.0.8.tar.gz","src_id":"13807","5":"13807","creation_date":"1284208320","6":"1284208320"},{"0":"3187","vim_version":"7.2","1":"7.2","script_version":"1.0.6","2":"1.0.6","version_comment":"Added `isfunc' test (tests whether given function exists and is callable)","3":"Added `isfunc' test (tests whether given function exists and is callable)","package":"vimargumentchec-1.0.6.tar.gz","4":"vimargumentchec-1.0.6.tar.gz","src_id":"13732","5":"13732","creation_date":"1283228833","6":"1283228833"},{"0":"3187","vim_version":"7.2","1":"7.2","script_version":"1.0.5","2":"1.0.5","version_comment":"Added isdirectory and executable checks to file check","3":"Added isdirectory and executable checks to file check","package":"vimargumentchec-1.0.5.tar.gz","4":"vimargumentchec-1.0.5.tar.gz","src_id":"13711","5":"13711","creation_date":"1283073948","6":"1283073948"},{"0":"3187","vim_version":"7.2","1":"7.2","script_version":"1.0.4","2":"1.0.4","version_comment":"Fixed some bugs","3":"Fixed some bugs","package":"vimargumentchec-1.0.4.tar.gz","4":"vimargumentchec-1.0.4.tar.gz","src_id":"13708","5":"13708","creation_date":"1283030201","6":"1283030201"},{"0":"3187","vim_version":"7.2","1":"7.2","script_version":"1.0.3","2":"1.0.3","version_comment":"Removed redirection of error messages (that caused some bugs)","3":"Removed redirection of error messages (that caused some bugs)","package":"vimargumentchec-1.0.3.tar.gz","4":"vimargumentchec-1.0.3.tar.gz","src_id":"13641","5":"13641","creation_date":"1282473510","6":"1282473510"},{"0":"3187","vim_version":"7.2","1":"7.2","script_version":"1.0.2","2":"1.0.2","version_comment":"Fixed nums check","3":"Fixed nums check","package":"vimargumentchec-1.0.2.tar.gz","4":"vimargumentchec-1.0.2.tar.gz","src_id":"13615","5":"13615","creation_date":"1282131419","6":"1282131419"},{"0":"3187","vim_version":"7.2","1":"7.2","script_version":"1.0.1","2":"1.0.1","version_comment":"Fixed `ambigious prefix' error","3":"Fixed `ambigious prefix' error","package":"vimargumentchec-1.0.1.tar.gz","4":"vimargumentchec-1.0.1.tar.gz","src_id":"13550","5":"13550","creation_date":"1281552361","6":"1281552361"},{"0":"3187","vim_version":"7.2","1":"7.2","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"vimargumentchec-1.0.tar.gz","4":"vimargumentchec-1.0.tar.gz","src_id":"13541","5":"13541","creation_date":"1281420179","6":"1281420179"}]},"3186":{"script_id":"3186","0":"3186","script_name":"vimstuff","1":"vimstuff","script_type":"utility","2":"utility","summary":"Some useful vim functions","3":"Some useful vim functions","description":"**This plugin is deprecated. Some functions were moved to frawor (vimscript #3631)**\r\n\r\nThis plugin contains some functions that can be useful for plugin developers and one command that may be useful to all users:\r\n\r\n    \u00e2\u0080\u0094 :SE command (:e replacement with zsh-like completion and multiple file arguments support)\r\n    \u00e2\u0080\u0094 Pure vimscript base64 decoder\r\n    \u00e2\u0080\u0094 Bitwise OR and AND functions (slow and unsigned integer only)\r\n    \u00e2\u0080\u0094 Some escaping and quoting functions\r\n    \u00e2\u0080\u0094 Function that prints table with higlighted header\r\n    \u00e2\u0080\u0094 Failsafe builtin `string()' replacement (for representation purposes only)\r\n    \u00e2\u0080\u0094 ...\r\n\r\nProject page: http:\/\/sourceforge.net\/projects\/vimstuff\r\nDependencies (you do not need to install them by yourself, see installation details):\r\nvimscript #3184, http:\/\/sourceforge.net\/projects\/vimpluginloader","4":"**This plugin is deprecated. Some functions were moved to frawor (vimscript #3631)**\r\n\r\nThis plugin contains some functions that can be useful for plugin developers and one command that may be useful to all users:\r\n\r\n    \u00e2\u0080\u0094 :SE command (:e replacement with zsh-like completion and multiple file arguments support)\r\n    \u00e2\u0080\u0094 Pure vimscript base64 decoder\r\n    \u00e2\u0080\u0094 Bitwise OR and AND functions (slow and unsigned integer only)\r\n    \u00e2\u0080\u0094 Some escaping and quoting functions\r\n    \u00e2\u0080\u0094 Function that prints table with higlighted header\r\n    \u00e2\u0080\u0094 Failsafe builtin `string()' replacement (for representation purposes only)\r\n    \u00e2\u0080\u0094 ...\r\n\r\nProject page: http:\/\/sourceforge.net\/projects\/vimstuff\r\nDependencies (you do not need to install them by yourself, see installation details):\r\nvimscript #3184, http:\/\/sourceforge.net\/projects\/vimpluginloader","install_details":"You can install this plugin using scriptmanager (vimscript #2905) plugin (install scriptmanager, run ``ActivateAddons vimpluginloader'' and add ``call vam#ActivateAddons([\"vimpluginloader\"])'' to your .vimrc. Vim-addon-manager will install all dependencies for you). You can also use archives attached to this page, they contain plugin with all dependencies, so you do not need to fetch them yourself.\r\n\r\nGentoo users can use the following mercurial overlay: http:\/\/vimpluginloader.hg.sourceforge.net:8000\/hgroot\/vimpluginloader\/pluginloader-overlay.\r\n\r\nNote for plugin developers: it is better to copy frequently used functions to your plugin as almost all functions define argument checker which is slow.","5":"You can install this plugin using scriptmanager (vimscript #2905) plugin (install scriptmanager, run ``ActivateAddons vimpluginloader'' and add ``call vam#ActivateAddons([\"vimpluginloader\"])'' to your .vimrc. Vim-addon-manager will install all dependencies for you). You can also use archives attached to this page, they contain plugin with all dependencies, so you do not need to fetch them yourself.\r\n\r\nGentoo users can use the following mercurial overlay: http:\/\/vimpluginloader.hg.sourceforge.net:8000\/hgroot\/vimpluginloader\/pluginloader-overlay.\r\n\r\nNote for plugin developers: it is better to copy frequently used functions to your plugin as almost all functions define argument checker which is slow.","first_name":"ZyX","6":"ZyX","last_name":" ","7":" ","releases":[{"0":"3186","vim_version":"9999","1":"9999","script_version":"1.0.11","2":"1.0.11","version_comment":"Reposting bundle due to core plugins update","3":"Reposting bundle due to core plugins update","package":"vimstuff-1.0.11.tar.gz","4":"vimstuff-1.0.11.tar.gz","src_id":"14564","5":"14564","creation_date":"1292713513","6":"1292713513"},{"0":"3186","vim_version":"9999","1":"9999","script_version":"1.0.11","2":"1.0.11","version_comment":"Reposting bundle due to core plugins update","3":"Reposting bundle due to core plugins update","package":"vimstuff-1.0.11.tar.gz","4":"vimstuff-1.0.11.tar.gz","src_id":"14317","5":"14317","creation_date":"1290257895","6":"1290257895"},{"0":"3186","vim_version":"7.2","1":"7.2","script_version":"1.0.11","2":"1.0.11","version_comment":"Fixed restoring history from list, added saving history on plugin unloading","3":"Fixed restoring history from list, added saving history on plugin unloading","package":"vimstuff-1.0.11.tar.gz","4":"vimstuff-1.0.11.tar.gz","src_id":"14085","5":"14085","creation_date":"1287604662","6":"1287604662"},{"0":"3186","vim_version":"7.2","1":"7.2","script_version":"1.0.10","2":"1.0.10","version_comment":"Added support for 30th patch (do not save history for custom inputs as string, leave it as list)","3":"Added support for 30th patch (do not save history for custom inputs as string, leave it as list)","package":"vimstuff-1.0.10.tar.gz","4":"vimstuff-1.0.10.tar.gz","src_id":"14083","5":"14083","creation_date":"1287592345","6":"1287592345"},{"0":"3186","vim_version":"7.2","1":"7.2","script_version":"1.0.9","2":"1.0.9","version_comment":"Added base64 encoder\nRemoved `iswriteable' function (it duplicates vimargumentchec (vimscript #3187) functionality)\nRemoved :SE command (it was moved to zvim plugin which is now in alpha version and can be found only at http:\/\/bitbucket.org\/ZyX_I\/zvim)","3":"Added base64 encoder\nRemoved `iswriteable' function (it duplicates vimargumentchec (vimscript #3187) functionality)\nRemoved :SE command (it was moved to zvim plugin which is now in alpha version and can be found only at http:\/\/bitbucket.org\/ZyX_I\/zvim)","package":"vimstuff-1.0.9.tar.gz","4":"vimstuff-1.0.9.tar.gz","src_id":"14012","5":"14012","creation_date":"1286404864","6":"1286404864"},{"0":"3186","vim_version":"7.2","1":"7.2","script_version":"1.0.7","2":"1.0.7","version_comment":"Fixed completion for :SE command","3":"Fixed completion for :SE command","package":"vimstuff-1.0.7.tar.gz","4":"vimstuff-1.0.7.tar.gz","src_id":"13802","5":"13802","creation_date":"1284148294","6":"1284148294"},{"0":"3186","vim_version":"7.2","1":"7.2","script_version":"1.0.5","2":"1.0.5","version_comment":"Added storing of custom input history in viminfo file","3":"Added storing of custom input history in viminfo file","package":"vimstuff-1.0.5.tar.gz","4":"vimstuff-1.0.5.tar.gz","src_id":"13713","5":"13713","creation_date":"1283087356","6":"1283087356"},{"0":"3186","vim_version":"7.2","1":"7.2","script_version":"1.0.4","2":"1.0.4","version_comment":"Fixed base64 decoder, made it able to return array of numbers instead of string, fixed completion","3":"Fixed base64 decoder, made it able to return array of numbers instead of string, fixed completion","package":"vimstuff-1.0.4.tar.gz","4":"vimstuff-1.0.4.tar.gz","src_id":"13700","5":"13700","creation_date":"1283008316","6":"1283008316"},{"0":"3186","vim_version":"7.2","1":"7.2","script_version":"1.0.3","2":"1.0.3","version_comment":"Added function that can create input()-like functions with custom history","3":"Added function that can create input()-like functions with custom history","package":"vimstuff-1.0.3.tar.gz","4":"vimstuff-1.0.3.tar.gz","src_id":"13694","5":"13694","creation_date":"1282917892","6":"1282917892"},{"0":"3186","vim_version":"7.2","1":"7.2","script_version":"1.0.2","2":"1.0.2","version_comment":"Made plugin use lazygetfunctions+run","3":"Made plugin use lazygetfunctions+run","package":"vimstuff-1.0.2.tar.gz","4":"vimstuff-1.0.2.tar.gz","src_id":"13665","5":"13665","creation_date":"1282666637","6":"1282666637"},{"0":"3186","vim_version":"7.2","1":"7.2","script_version":"1.0.1","2":"1.0.1","version_comment":"Fixed regescape function","3":"Fixed regescape function","package":"vimstuff-1.0.1.tar.gz","4":"vimstuff-1.0.1.tar.gz","src_id":"13571","5":"13571","creation_date":"1281828269","6":"1281828269"},{"0":"3186","vim_version":"7.2","1":"7.2","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"vimstuff-1.0.tar.gz","4":"vimstuff-1.0.tar.gz","src_id":"13540","5":"13540","creation_date":"1281420138","6":"1281420138"}]},"3185":{"script_id":"3185","0":"3185","script_name":"jsonvim","1":"jsonvim","script_type":"utility","2":"utility","summary":"Library that makes vim able to safely load JSON files","3":"Library that makes vim able to safely load JSON files","description":"This plugin provides the ability to load JSON encoded data from files and dump \r\nVim variables to files. Data loaded is cached in order to speed up the \r\nplugin.\r\n\r\nThis plugin also provides Russian documentation. Add \u00c2\u00abru\u00c2\u00bb to option \u00c2\u00abhelplang\u00c2\u00bb in order to use it.\r\n\r\nDocumentation: http:\/\/vimpluginloader.sourceforge.net\/doc\/json.txt.html\r\nRussian documentation: http:\/\/vimpluginloader.sourceforge.net\/doc\/json.rux.html\r\nProject page: http:\/\/sourceforge.net\/projects\/jsonvim\r\nDependencies (you do not need to install them by yourself, see installation details):\r\nvimscript #3631, https:\/\/bitbucket.org\/ZyX_I\/frawor","4":"This plugin provides the ability to load JSON encoded data from files and dump \r\nVim variables to files. Data loaded is cached in order to speed up the \r\nplugin.\r\n\r\nThis plugin also provides Russian documentation. Add \u00c2\u00abru\u00c2\u00bb to option \u00c2\u00abhelplang\u00c2\u00bb in order to use it.\r\n\r\nDocumentation: http:\/\/vimpluginloader.sourceforge.net\/doc\/json.txt.html\r\nRussian documentation: http:\/\/vimpluginloader.sourceforge.net\/doc\/json.rux.html\r\nProject page: http:\/\/sourceforge.net\/projects\/jsonvim\r\nDependencies (you do not need to install them by yourself, see installation details):\r\nvimscript #3631, https:\/\/bitbucket.org\/ZyX_I\/frawor","install_details":"You can install this plugin using vim-addon-manager (vimscript #2905) plugin (install vim-addon-manager, run \u00e2\u0080\u009cActivateAddons jsonvim\u00e2\u0080\u009d and add \u00e2\u0080\u009ccall vam#ActivateAddons([\"jsonvim\"])\u00e2\u0080\u009d to your .vimrc. Vim-addon-manager will install all dependencies for you). You can also use archives attached to this page, they contain plugin with all dependencies, so you do not need to fetch them yourself.\r\n\r\nGentoo users can use the following mercurial overlay: https:\/\/bitbucket.org\/ZyX_I\/pluginloader-overlay.\r\n\r\nIt is recommended to use vim with python support: this will speed up this plugin.","5":"You can install this plugin using vim-addon-manager (vimscript #2905) plugin (install vim-addon-manager, run \u00e2\u0080\u009cActivateAddons jsonvim\u00e2\u0080\u009d and add \u00e2\u0080\u009ccall vam#ActivateAddons([\"jsonvim\"])\u00e2\u0080\u009d to your .vimrc. Vim-addon-manager will install all dependencies for you). You can also use archives attached to this page, they contain plugin with all dependencies, so you do not need to fetch them yourself.\r\n\r\nGentoo users can use the following mercurial overlay: https:\/\/bitbucket.org\/ZyX_I\/pluginloader-overlay.\r\n\r\nIt is recommended to use vim with python support: this will speed up this plugin.","first_name":"ZyX","6":"ZyX","last_name":" ","7":" ","releases":[{"0":"3185","vim_version":"7.3","1":"7.3","script_version":"2.1","2":"2.1","version_comment":"Moved plugin to autoload\/json.vim, slightly improved documentation","3":"Moved plugin to autoload\/json.vim, slightly improved documentation","package":"jsonvim-2.1.tar.gz","4":"jsonvim-2.1.tar.gz","src_id":"19136","5":"19136","creation_date":"1354920791","6":"1354920791"},{"0":"3185","vim_version":"7.3","1":"7.3","script_version":"2.0","2":"2.0","version_comment":"Ported plugin to frawor, fixed some python errors","3":"Ported plugin to frawor, fixed some python errors","package":"jsonvim-2.0.tar.gz","4":"jsonvim-2.0.tar.gz","src_id":"15972","5":"15972","creation_date":"1309008226","6":"1309008226"},{"0":"3185","vim_version":"9999","1":"9999","script_version":"1.0.3","2":"1.0.3","version_comment":"Reposting bundle due to core plugins update","3":"Reposting bundle due to core plugins update","package":"jsonvim-1.0.3.tar.gz","4":"jsonvim-1.0.3.tar.gz","src_id":"14567","5":"14567","creation_date":"1292713531","6":"1292713531"},{"0":"3185","vim_version":"9999","1":"9999","script_version":"1.0.3","2":"1.0.3","version_comment":"Reposting bundle due to core plugins update","3":"Reposting bundle due to core plugins update","package":"jsonvim-1.0.3.tar.gz","4":"jsonvim-1.0.3.tar.gz","src_id":"14320","5":"14320","creation_date":"1290257912","6":"1290257912"},{"0":"3185","vim_version":"7.2","1":"7.2","script_version":"1.0.3","2":"1.0.3","version_comment":"Minor fix: removed escaping of `[' inside a collection","3":"Minor fix: removed escaping of `[' inside a collection","package":"jsonvim-1.0.3.tar.gz","4":"jsonvim-1.0.3.tar.gz","src_id":"14302","5":"14302","creation_date":"1290099465","6":"1290099465"},{"0":"3185","vim_version":"7.2","1":"7.2","script_version":"1.0.2","2":"1.0.2","version_comment":"Made plugin support other Python JSON implementations, including standart json","3":"Made plugin support other Python JSON implementations, including standart json","package":"jsonvim-1.0.2.tar.gz","4":"jsonvim-1.0.2.tar.gz","src_id":"13677","5":"13677","creation_date":"1282814974","6":"1282814974"},{"0":"3185","vim_version":"7.2","1":"7.2","script_version":"1.0.1","2":"1.0.1","version_comment":"Added russian translation","3":"Added russian translation","package":"jsonvim-1.0.1.tar.gz","4":"jsonvim-1.0.1.tar.gz","src_id":"13670","5":"13670","creation_date":"1282732629","6":"1282732629"},{"0":"3185","vim_version":"7.2","1":"7.2","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"jsonvim-1.0.tar.gz","4":"jsonvim-1.0.tar.gz","src_id":"13539","5":"13539","creation_date":"1281420103","6":"1281420103"}]},"3184":{"script_id":"3184","0":"3184","script_name":"vimpluginloader","1":"vimpluginloader","script_type":"utility","2":"utility","summary":"Plugin that helps to create complicated vim scripts","3":"Plugin that helps to create complicated vim scripts","description":"**This plugin is deprecated. Use frawor (vimscript #3631) instead**\r\n\r\nThis plugin provides the ability to autoload plugins on demand, create \r\nglobal functions and commands and extend mksession with plugin support.\r\n\r\nFeatures:\r\n    \u00e2\u0080\u0094 Autoloading plugins on FuncUndefined event.\r\n    \u00e2\u0080\u0094 Autoloading plugins when their command is called.\r\n    \u00e2\u0080\u0094 Autoloading plugins when their mapping is used.\r\n    \u00e2\u0080\u0094 Autoloading plugins when their functionality is required.\r\n    \u00e2\u0080\u0094 Displaying plugins' status.\r\n    \u00e2\u0080\u0094 Unloading and reloading plugins (useful for plugin developers).\r\n    \u00e2\u0080\u0094 Searching for a function number through registered plugins.\r\n    \u00e2\u0080\u0094 Checking function arguments before running a function.\r\n    \u00e2\u0080\u0094 Create a session file with plugin's data.\r\n\r\nDocumentation: http:\/\/vimpluginloader.sourceforge.net\/doc\/load.txt.html\r\nProject page: http:\/\/sourceforge.net\/projects\/vimpluginloader\r\nDependencies (you do not need to install them by yourself, see installation details):\r\nvimscript #3187, http:\/\/sourceforge.net\/projects\/vimargumentchec\r\nvimscript #3188, http:\/\/sourceforge.net\/projects\/vimcompcrtr\r\nvimscript #3190, http:\/\/sourceforge.net\/projects\/yamlvim","4":"**This plugin is deprecated. Use frawor (vimscript #3631) instead**\r\n\r\nThis plugin provides the ability to autoload plugins on demand, create \r\nglobal functions and commands and extend mksession with plugin support.\r\n\r\nFeatures:\r\n    \u00e2\u0080\u0094 Autoloading plugins on FuncUndefined event.\r\n    \u00e2\u0080\u0094 Autoloading plugins when their command is called.\r\n    \u00e2\u0080\u0094 Autoloading plugins when their mapping is used.\r\n    \u00e2\u0080\u0094 Autoloading plugins when their functionality is required.\r\n    \u00e2\u0080\u0094 Displaying plugins' status.\r\n    \u00e2\u0080\u0094 Unloading and reloading plugins (useful for plugin developers).\r\n    \u00e2\u0080\u0094 Searching for a function number through registered plugins.\r\n    \u00e2\u0080\u0094 Checking function arguments before running a function.\r\n    \u00e2\u0080\u0094 Create a session file with plugin's data.\r\n\r\nDocumentation: http:\/\/vimpluginloader.sourceforge.net\/doc\/load.txt.html\r\nProject page: http:\/\/sourceforge.net\/projects\/vimpluginloader\r\nDependencies (you do not need to install them by yourself, see installation details):\r\nvimscript #3187, http:\/\/sourceforge.net\/projects\/vimargumentchec\r\nvimscript #3188, http:\/\/sourceforge.net\/projects\/vimcompcrtr\r\nvimscript #3190, http:\/\/sourceforge.net\/projects\/yamlvim","install_details":"You can install this plugin using scriptmanager (vimscript #2905) plugin (install scriptmanager, run ``ActivateAddons vimpluginloader'' and add ``call vam#ActivateAddons([\"vimpluginloader\"])'' to your .vimrc. Vim-addon-manager will install all dependencies for you). You can also use archives attached to this page, they contain plugin with all dependencies, so you do not need to fetch them yourself.\r\n\r\nGentoo users can use the following mercurial overlay: http:\/\/vimpluginloader.hg.sourceforge.net:8000\/hgroot\/vimpluginloader\/pluginloader-overlay.","5":"You can install this plugin using scriptmanager (vimscript #2905) plugin (install scriptmanager, run ``ActivateAddons vimpluginloader'' and add ``call vam#ActivateAddons([\"vimpluginloader\"])'' to your .vimrc. Vim-addon-manager will install all dependencies for you). You can also use archives attached to this page, they contain plugin with all dependencies, so you do not need to fetch them yourself.\r\n\r\nGentoo users can use the following mercurial overlay: http:\/\/vimpluginloader.hg.sourceforge.net:8000\/hgroot\/vimpluginloader\/pluginloader-overlay.","first_name":"ZyX","6":"ZyX","last_name":" ","7":" ","releases":[{"0":"3184","vim_version":"7.3","1":"7.3","script_version":"1.4.5","2":"1.4.5","version_comment":"Added `autocmd' constructed function (it is replacement for :autocmd command which has the only advantage: autocommands defined by autocmd() will get automatically removed on plugin unload)","3":"Added `autocmd' constructed function (it is replacement for :autocmd command which has the only advantage: autocommands defined by autocmd() will get automatically removed on plugin unload)","package":"vimpluginloader-1.4.5.tar.gz","4":"vimpluginloader-1.4.5.tar.gz","src_id":"14943","5":"14943","creation_date":"1296705469","6":"1296705469"},{"0":"3184","vim_version":"7.3","1":"7.3","script_version":"1.4.4","2":"1.4.4","version_comment":"Added `operator' mapping option (defines operator mapping), some documentation improvements","3":"Added `operator' mapping option (defines operator mapping), some documentation improvements","package":"vimpluginloader-1.4.4.tar.gz","4":"vimpluginloader-1.4.4.tar.gz","src_id":"14883","5":"14883","creation_date":"1296155624","6":"1296155624"},{"0":"3184","vim_version":"7.3","1":"7.3","script_version":"1.4.3","2":"1.4.3","version_comment":"Added `remap' mapping option\nAdded possibility to specify multiple mapping modes\nSome buf fixes","3":"Added `remap' mapping option\nAdded possibility to specify multiple mapping modes\nSome buf fixes","package":"vimpluginloader-1.4.3.tar.gz","4":"vimpluginloader-1.4.3.tar.gz","src_id":"14791","5":"14791","creation_date":"1295461842","6":"1295461842"},{"0":"3184","vim_version":"7.3","1":"7.3","script_version":"1.4.2","2":"1.4.2","version_comment":"Some bug fixes","3":"Some bug fixes","package":"vimpluginloader-1.4.2.tar.gz","4":"vimpluginloader-1.4.2.tar.gz","src_id":"14755","5":"14755","creation_date":"1295114407","6":"1295114407"},{"0":"3184","vim_version":"7.3","1":"7.3","script_version":"1.4.1","2":"1.4.1","version_comment":"Added `bufdict' reginfo function","3":"Added `bufdict' reginfo function","package":"vimpluginloader-1.4.1.tar.gz","4":"vimpluginloader-1.4.1.tar.gz","src_id":"14747","5":"14747","creation_date":"1295036728","6":"1295036728"},{"0":"3184","vim_version":"7.3","1":"7.3","script_version":"1.4","2":"1.4","version_comment":"Added `getc' and `nochars' mapping dictionaries","3":"Added `getc' and `nochars' mapping dictionaries","package":"vimpluginloader-1.4.tar.gz","4":"vimpluginloader-1.4.tar.gz","src_id":"14742","5":"14742","creation_date":"1294956569","6":"1294956569"},{"0":"3184","vim_version":"7.3","1":"7.3","script_version":"1.3.11","2":"1.3.11","version_comment":"Added function and breakadd actions, some fixes","3":"Added function and breakadd actions, some fixes","package":"vimpluginloader-1.3.11.tar.gz","4":"vimpluginloader-1.3.11.tar.gz","src_id":"14704","5":"14704","creation_date":"1294448422","6":"1294448422"},{"0":"3184","vim_version":"7.3","1":"7.3","script_version":"1.3.10","2":"1.3.10","version_comment":"Fixed an issue with using load#LoadFuncdict().getfunctions from vimrc","3":"Fixed an issue with using load#LoadFuncdict().getfunctions from vimrc","package":"vimpluginloader-1.3.10.tar.gz","4":"vimpluginloader-1.3.10.tar.gz","src_id":"14676","5":"14676","creation_date":"1294076334","6":"1294076334"},{"0":"3184","vim_version":"7.3","1":"7.3","script_version":"1.3.7","2":"1.3.7","version_comment":"Added load#Setup function, made error messages a bit more verbose","3":"Added load#Setup function, made error messages a bit more verbose","package":"vimpluginloader-1.3.7.tar.gz","4":"vimpluginloader-1.3.7.tar.gz","src_id":"14669","5":"14669","creation_date":"1293920278","6":"1293920278"},{"0":"3184","vim_version":"7.3","1":"7.3","script_version":"1.3.6","2":"1.3.6","version_comment":"Added sesreload action, some session and event fixes","3":"Added sesreload action, some session and event fixes","package":"vimpluginloader-1.3.6.tar.gz","4":"vimpluginloader-1.3.6.tar.gz","src_id":"14640","5":"14640","creation_date":"1293569983","6":"1293569983"},{"0":"3184","vim_version":"9999","1":"9999","script_version":"1.3.5","2":"1.3.5","version_comment":"Reposting bundle due to core plugins update","3":"Reposting bundle due to core plugins update","package":"vimpluginloader-1.3.5.tar.gz","4":"vimpluginloader-1.3.5.tar.gz","src_id":"14571","5":"14571","creation_date":"1292713561","6":"1292713561"},{"0":"3184","vim_version":"7.3","1":"7.3","script_version":"1.3.5","2":"1.3.5","version_comment":"Fixed reloading of chk plugin","3":"Fixed reloading of chk plugin","package":"vimpluginloader-1.3.5.tar.gz","4":"vimpluginloader-1.3.5.tar.gz","src_id":"14533","5":"14533","creation_date":"1292516537","6":"1292516537"},{"0":"3184","vim_version":"7.3","1":"7.3","script_version":"1.3.4","2":"1.3.4","version_comment":"Improved nrof completion, replaced echo with echomsg in eerror, fixed preload check","3":"Improved nrof completion, replaced echo with echomsg in eerror, fixed preload check","package":"vimpluginloader-1.3.4.tar.gz","4":"vimpluginloader-1.3.4.tar.gz","src_id":"14490","5":"14490","creation_date":"1292183628","6":"1292183628"},{"0":"3184","vim_version":"9999","1":"9999","script_version":"1.3.3","2":"1.3.3","version_comment":"Reposting bundle due to core plugins update","3":"Reposting bundle due to core plugins update","package":"vimpluginloader-1.3.3.tar.gz","4":"vimpluginloader-1.3.3.tar.gz","src_id":"14325","5":"14325","creation_date":"1290257937","6":"1290257937"},{"0":"3184","vim_version":"7.3","1":"7.3","script_version":"1.3.3","2":"1.3.3","version_comment":"Added DisableOptionChecks and _disable_option_checks options","3":"Added DisableOptionChecks and _disable_option_checks options","package":"vimpluginloader-1.3.3.tar.gz","4":"vimpluginloader-1.3.3.tar.gz","src_id":"14263","5":"14263","creation_date":"1289770761","6":"1289770761"},{"0":"3184","vim_version":"7.2","1":"7.2","script_version":"1.3.2","2":"1.3.2","version_comment":"Improved load#LoadFuncdict function, added load#SetOption and load#CreateDictFunction functions","3":"Improved load#LoadFuncdict function, added load#SetOption and load#CreateDictFunction functions","package":"vimpluginloader-1.3.2.tar.gz","4":"vimpluginloader-1.3.2.tar.gz","src_id":"13933","5":"13933","creation_date":"1285585709","6":"1285585709"},{"0":"3184","vim_version":"7.2","1":"7.2","script_version":"1.3.1","2":"1.3.1","version_comment":"Fixed some mapping bugs","3":"Fixed some mapping bugs","package":"vimpluginloader-1.3.1.tar.gz","4":"vimpluginloader-1.3.1.tar.gz","src_id":"13921","5":"13921","creation_date":"1285507473","6":"1285507473"},{"0":"3184","vim_version":"7.2","1":"7.2","script_version":"1.3","2":"1.3","version_comment":"Provided a way to register different plugin types and place plugin file not directly under plugin directory\nAdded support for autoloading external dependencies\nMade plugin reload itself without errors","3":"Provided a way to register different plugin types and place plugin file not directly under plugin directory\nAdded support for autoloading external dependencies\nMade plugin reload itself without errors","package":"vimpluginloader-1.3.tar.gz","4":"vimpluginloader-1.3.tar.gz","src_id":"13918","5":"13918","creation_date":"1285458959","6":"1285458959"},{"0":"3184","vim_version":"7.2","1":"7.2","script_version":"1.2","2":"1.2","version_comment":"Added session creation","3":"Added session creation","package":"vimpluginloader-1.2.tar.gz","4":"vimpluginloader-1.2.tar.gz","src_id":"13809","5":"13809","creation_date":"1284233247","6":"1284233247"},{"0":"3184","vim_version":"7.2","1":"7.2","script_version":"1.1.4","2":"1.1.4","version_comment":"Improved findnr action (now it takes a list of numbers separated by anything except spaces), improved autocmd[!] action (now it does not force you to escape spaces), improved error messages, some bug fixes","3":"Improved findnr action (now it takes a list of numbers separated by anything except spaces), improved autocmd[!] action (now it does not force you to escape spaces), improved error messages, some bug fixes","package":"vimpluginloader-1.1.4.tar.gz","4":"vimpluginloader-1.1.4.tar.gz","src_id":"13808","5":"13808","creation_date":"1284209250","6":"1284209250"},{"0":"3184","vim_version":"7.2","1":"7.2","script_version":"1.1.3","2":"1.1.3","version_comment":"Added lazygetfunctions() and run() functions useful for cyclic dependency resolution","3":"Added lazygetfunctions() and run() functions useful for cyclic dependency resolution","package":"vimpluginloader-1.1.3.tar.gz","4":"vimpluginloader-1.1.3.tar.gz","src_id":"13664","5":"13664","creation_date":"1282666453","6":"1282666453"},{"0":"3184","vim_version":"7.2","1":"7.2","script_version":"1.1.2","2":"1.1.2","version_comment":"Fixed completion for vim7.3","3":"Fixed completion for vim7.3","package":"vimpluginloader-1.1.2.tar.gz","4":"vimpluginloader-1.1.2.tar.gz","src_id":"13614","5":"13614","creation_date":"1282130516","6":"1282130516"},{"0":"3184","vim_version":"7.2","1":"7.2","script_version":"1.1","2":"1.1","version_comment":"Added `autocommands'","3":"Added `autocommands'","package":"vimpluginloader-1.1.tar.gz","4":"vimpluginloader-1.1.tar.gz","src_id":"13552","5":"13552","creation_date":"1281556286","6":"1281556286"},{"0":"3184","vim_version":"7.2","1":"7.2","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"vimpluginloader-1.0.tar.gz","4":"vimpluginloader-1.0.tar.gz","src_id":"13538","5":"13538","creation_date":"1281420042","6":"1281420042"}]},"3183":{"script_id":"3183","0":"3183","script_name":"CSS3 Highlights","1":"CSS3 Highlights","script_type":"syntax","2":"syntax","summary":"CSS3 Highlights","3":"CSS3 Highlights","description":"Dumped! Please check this: http:\/\/www.vim.org\/scripts\/script.php?script_id=3220\r\n\r\nBased on original css.vim.\r\n\r\nAdded CSS3 properties highlights, support most of CSS3 prop, and will recognize prefix like -moz-, -webkit-\r\n\r\nNext step is make both prop and attr highlight colors more readable.\r\n\r\nWelcome for any feedbacks!","4":"Dumped! Please check this: http:\/\/www.vim.org\/scripts\/script.php?script_id=3220\r\n\r\nBased on original css.vim.\r\n\r\nAdded CSS3 properties highlights, support most of CSS3 prop, and will recognize prefix like -moz-, -webkit-\r\n\r\nNext step is make both prop and attr highlight colors more readable.\r\n\r\nWelcome for any feedbacks!","install_details":"Put css.vim to ~\/.vim\/syntax\/","5":"Put css.vim to ~\/.vim\/syntax\/","first_name":"Chris","6":"Chris","last_name":"Yip","7":"Yip","releases":[{"0":"3183","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"css.vim","4":"css.vim","src_id":"13471","5":"13471","creation_date":"1280906446","6":"1280906446"}]},"3182":{"script_id":"3182","0":"3182","script_name":"mail_movement","1":"mail_movement","script_type":"ftplugin","2":"ftplugin","summary":"Movement over email quotes with ]] etc. ","3":"Movement over email quotes with ]] etc. ","description":"DESCRIPTION\r\nThis filetype plugin provides movement commands and text objects for email\r\nquotes.\r\n\r\nUSAGE\r\nA quoted email is determined either by:\r\n- lines prefixed with \">\" (one, or multiple for nested quotes)\r\n- an optional email separator, e.g.\r\n-----Original Message-----\r\n  and the standard\r\nFrom: <Name>\r\n  optionally followed by other header lines.\r\n\r\nMove around email quotes of either:\r\n- a certain nesting level, as determined by the current line; if the cursor is\r\n  not on a quoted line, any nesting level will be used.\r\n- the range of lines from the \"From: <Name>\" mail header up to the line\r\n  preceding the next email separator or next mail header.\r\n\r\n]]                      Go to [count] next start of an email quote.\r\n][                      Go to [count] next end of an email quote.\r\n[[                      Go to [count] previous start of an email quote.\r\n[]                      Go to [count] previous end of an email quote.\r\n\r\nMove to nested email quote (i.e. of a higher nesting level as the current\r\nline; if the cursor is not on a quoted line, any nesting level will be used).\r\n\r\n]+                      Go to [count] next start of a nested email quote.\r\n[+                      Go to [count] previous start of a nested email quote.\r\n\r\naq                      \"a quote\" text object, select [count] email quotes, i.e.\r\n                        - contiguous lines having at least the same as the\r\n                          current line's nesting level\r\n                        - one email message including the preceding mail\r\n                          headers and optional email separator\r\niq                      \"inner quote\" text object, select [count] regions with\r\n                        either:\r\n                        - the same nesting level\r\n                        - the contents of an email message without the\r\n                          preceding mail headers","4":"DESCRIPTION\r\nThis filetype plugin provides movement commands and text objects for email\r\nquotes.\r\n\r\nUSAGE\r\nA quoted email is determined either by:\r\n- lines prefixed with \">\" (one, or multiple for nested quotes)\r\n- an optional email separator, e.g.\r\n-----Original Message-----\r\n  and the standard\r\nFrom: <Name>\r\n  optionally followed by other header lines.\r\n\r\nMove around email quotes of either:\r\n- a certain nesting level, as determined by the current line; if the cursor is\r\n  not on a quoted line, any nesting level will be used.\r\n- the range of lines from the \"From: <Name>\" mail header up to the line\r\n  preceding the next email separator or next mail header.\r\n\r\n]]                      Go to [count] next start of an email quote.\r\n][                      Go to [count] next end of an email quote.\r\n[[                      Go to [count] previous start of an email quote.\r\n[]                      Go to [count] previous end of an email quote.\r\n\r\nMove to nested email quote (i.e. of a higher nesting level as the current\r\nline; if the cursor is not on a quoted line, any nesting level will be used).\r\n\r\n]+                      Go to [count] next start of a nested email quote.\r\n[+                      Go to [count] previous start of a nested email quote.\r\n\r\naq                      \"a quote\" text object, select [count] email quotes, i.e.\r\n                        - contiguous lines having at least the same as the\r\n                          current line's nesting level\r\n                        - one email message including the preceding mail\r\n                          headers and optional email separator\r\niq                      \"inner quote\" text object, select [count] regions with\r\n                        either:\r\n                        - the same nesting level\r\n                        - the contents of an email message without the\r\n                          preceding mail headers","install_details":"INSTALLATION\r\nThis script is packaged as a vimball. If you have the \"gunzip\" decompressor\r\nin your PATH, simply edit the *.vmb.gz package in Vim; otherwise, decompress\r\nthe archive first, e.g. using WinZip. Inside Vim, install by sourcing the\r\nvimball or via the :UseVimball command.\r\n    vim mail_movement*.vmb.gz\r\n    :so %\r\nTo uninstall, use the :RmVimball command.\r\n\r\nThe commands and text objects are only active when 'filetype' is set to\r\n\"mail\". If you use Vim as an external editor for your browser or email\r\nprogram, you need to make sure that the filetype is properly detected, or\r\nmanually set the filetype every time via\r\n    :setf mail\r\nIf you want to use this plugin also for other filetypes, e.g. \"txt\", create a\r\nfile ftplugin\/txt_movement.vim in your 'runtimepath' (usually ~\/.vim) with the\r\nfollowing contents:\r\n    runtime! ftplugin\/mail_movement.vim\r\n\r\nDEPENDENCIES\r\n- Requires Vim 7.0 or higher.\r\n- Requires the CountJump plugin (vimscript #3130), version 1.40.\r\n\r\nCONFIGURATION\r\nFor a permanent configuration, put the following commands into your vimrc:\r\n\r\nTo change the default motion mapping, use:\r\n    let g:mail_movement_BeginMapping = ''\r\n    let g:mail_movement_EndMapping = ''\r\n    let g:mail_movement_NestedMapping = '+'\r\nTo also change the [ \/ ] prefix to something else, follow the instructions for\r\nCountJump-remap-motions.\r\n\r\nTo change the default text object mappings, use:\r\n    let g:mail_movement_QuoteTextObject = 'q'\r\nTo also change the i prefix to something else, follow the instructions for\r\nCountJump-remap-text-objects.","5":"INSTALLATION\r\nThis script is packaged as a vimball. If you have the \"gunzip\" decompressor\r\nin your PATH, simply edit the *.vmb.gz package in Vim; otherwise, decompress\r\nthe archive first, e.g. using WinZip. Inside Vim, install by sourcing the\r\nvimball or via the :UseVimball command.\r\n    vim mail_movement*.vmb.gz\r\n    :so %\r\nTo uninstall, use the :RmVimball command.\r\n\r\nThe commands and text objects are only active when 'filetype' is set to\r\n\"mail\". If you use Vim as an external editor for your browser or email\r\nprogram, you need to make sure that the filetype is properly detected, or\r\nmanually set the filetype every time via\r\n    :setf mail\r\nIf you want to use this plugin also for other filetypes, e.g. \"txt\", create a\r\nfile ftplugin\/txt_movement.vim in your 'runtimepath' (usually ~\/.vim) with the\r\nfollowing contents:\r\n    runtime! ftplugin\/mail_movement.vim\r\n\r\nDEPENDENCIES\r\n- Requires Vim 7.0 or higher.\r\n- Requires the CountJump plugin (vimscript #3130), version 1.40.\r\n\r\nCONFIGURATION\r\nFor a permanent configuration, put the following commands into your vimrc:\r\n\r\nTo change the default motion mapping, use:\r\n    let g:mail_movement_BeginMapping = ''\r\n    let g:mail_movement_EndMapping = ''\r\n    let g:mail_movement_NestedMapping = '+'\r\nTo also change the [ \/ ] prefix to something else, follow the instructions for\r\nCountJump-remap-motions.\r\n\r\nTo change the default text object mappings, use:\r\n    let g:mail_movement_QuoteTextObject = 'q'\r\nTo also change the i prefix to something else, follow the instructions for\r\nCountJump-remap-text-objects.","first_name":"Ingo","6":"Ingo","last_name":"Karkat","7":"Karkat","releases":[{"0":"3182","vim_version":"7.0","1":"7.0","script_version":"1.55","2":"1.55","version_comment":"- Allow to reconfigure the mappings for the motion and text objects.\r\n- Extract functions into separate autoload script.","3":"- Allow to reconfigure the mappings for the motion and text objects.\r\n- Extract functions into separate autoload script.","package":"mail_movement-1.55.vmb.gz","4":"mail_movement-1.55.vmb.gz","src_id":"22233","5":"22233","creation_date":"1406020254","6":"1406020254"},{"0":"3182","vim_version":"7.0","1":"7.0","script_version":"1.54","2":"1.54","version_comment":"Avoid use of s:function() by using autoload function name. This fixes a regression in Vim 7.3.1032, reported by lilydjwg.","3":"Avoid use of s:function() by using autoload function name. This fixes a regression in Vim 7.3.1032, reported by lilydjwg.","package":"mail_movement-1.54.vmb.gz","4":"mail_movement-1.54.vmb.gz","src_id":"20302","5":"20302","creation_date":"1370465450","6":"1370465450"},{"0":"3182","vim_version":"7.0","1":"7.0","script_version":"1.53","2":"1.53","version_comment":"FIX: Directly ring the bell to avoid problems when running under :silent!. ","3":"FIX: Directly ring the bell to avoid problems when running under :silent!. ","package":"mail_movement.vba.gz","4":"mail_movement.vba.gz","src_id":"15869","5":"15869","creation_date":"1307972501","6":"1307972501"},{"0":"3182","vim_version":"7.0","1":"7.0","script_version":"1.52","2":"1.52","version_comment":"Adapted to CountJump#Region#JumpToNextRegion() again returning jump position in version 1.40. ","3":"Adapted to CountJump#Region#JumpToNextRegion() again returning jump position in version 1.40. ","package":"mail_movement.vba.gz","4":"mail_movement.vba.gz","src_id":"14588","5":"14588","creation_date":"1292856239","6":"1292856239"},{"0":"3182","vim_version":"7.0","1":"7.0","script_version":"1.51","2":"1.51","version_comment":"- ENH: ][ mapping in operator-pending and visual mode now also operates over \/ select the last line of the quote. This is what the user expects.\r\n- Adapted to changed interface of CountJump.vim; now requires version 1.30. ","3":"- ENH: ][ mapping in operator-pending and visual mode now also operates over \/ select the last line of the quote. This is what the user expects.\r\n- Adapted to changed interface of CountJump.vim; now requires version 1.30. ","package":"mail_movement.vba.gz","4":"mail_movement.vba.gz","src_id":"14585","5":"14585","creation_date":"1292836508","6":"1292836508"},{"0":"3182","vim_version":"7.0","1":"7.0","script_version":"1.00","2":"1.00","version_comment":"Initial upload","3":"Initial upload","package":"mail_movement.vba.gz","4":"mail_movement.vba.gz","src_id":"13466","5":"13466","creation_date":"1280844158","6":"1280844158"}]},"3181":{"script_id":"3181","0":"3181","script_name":"fortunes_movement","1":"fortunes_movement","script_type":"ftplugin","2":"ftplugin","summary":"Movement over email fortunes with ]] etc. ","3":"Movement over email fortunes with ]] etc. ","description":"DESCRIPTION\r\nThis filetype plugin provides movement commands and text objects for email\r\nfortunes, i.e. blocks of text delimited by \/^-- \\?$\/.\r\n\r\nUSAGE\r\n                        Move around fortunes:\r\n]]                      Go to [count] next start of a fortune.\r\n][                      Go to [count] next end of a fortune.\r\n[[                      Go to [count] previous start of a fortune.\r\n[]                      Go to [count] previous end of a fortune.\r\n\r\nif                      \"inner fortune\" text object, select [count] fortunes,\r\n                        excluding the fortune separator.\r\naf                      \"a fortune\" text object, select [count] fortunes, including\r\n                        the preceding fortune separator.","4":"DESCRIPTION\r\nThis filetype plugin provides movement commands and text objects for email\r\nfortunes, i.e. blocks of text delimited by \/^-- \\?$\/.\r\n\r\nUSAGE\r\n                        Move around fortunes:\r\n]]                      Go to [count] next start of a fortune.\r\n][                      Go to [count] next end of a fortune.\r\n[[                      Go to [count] previous start of a fortune.\r\n[]                      Go to [count] previous end of a fortune.\r\n\r\nif                      \"inner fortune\" text object, select [count] fortunes,\r\n                        excluding the fortune separator.\r\naf                      \"a fortune\" text object, select [count] fortunes, including\r\n                        the preceding fortune separator.","install_details":"INSTALLATION\r\nThis script is packaged as a vimball. If you have the \"gunzip\" decompressor\r\nin your PATH, simply edit the *.vba.gz package in Vim; otherwise, decompress\r\nthe archive first, e.g. using WinZip. Inside Vim, install by sourcing the\r\nvimball or via the :UseVimball command.\r\n    vim fortune_movement.vba.gz\r\n    :so %\r\nTo uninstall, use the :RmVimball command. \r\n\r\nDEPENDENCIES\r\n- Requires Vim 7.0 or higher. \r\n- Requires the CountJump plugin (vimscript #3130), version 1.30. \r\n\r\nCONFIGURATION\r\nThe commands and text objects are only active when 'filetype' is set to\r\n\"fortunes\".\r\nYou need to make sure that the filetype is properly detected, for example via\r\nthe following fragment in .vim\/filetype.vim: \r\n    augroup filetypedetect\r\n        \" Fortunes files. \r\n        autocmd BufNewFile,BufRead fortunes.txt,*\/fortunes\/*.txt setf fortunes \r\n    augroup END\r\nor manually set the filetype every time via \r\n    :setf fortunes\r\nIf you want to use this plugin also for other filetypes, e.g. \"txt\", create a\r\nfile ftplugin\/txt_movement.vim in your 'runtimepath' (usually ~\/.vim) with the\r\nfollowing contents: \r\n    runtime! ftplugin\/fortunes_movement.vim\r\nThis is more maintainable than simply renaming fortunes_movement.vim. ","5":"INSTALLATION\r\nThis script is packaged as a vimball. If you have the \"gunzip\" decompressor\r\nin your PATH, simply edit the *.vba.gz package in Vim; otherwise, decompress\r\nthe archive first, e.g. using WinZip. Inside Vim, install by sourcing the\r\nvimball or via the :UseVimball command.\r\n    vim fortune_movement.vba.gz\r\n    :so %\r\nTo uninstall, use the :RmVimball command. \r\n\r\nDEPENDENCIES\r\n- Requires Vim 7.0 or higher. \r\n- Requires the CountJump plugin (vimscript #3130), version 1.30. \r\n\r\nCONFIGURATION\r\nThe commands and text objects are only active when 'filetype' is set to\r\n\"fortunes\".\r\nYou need to make sure that the filetype is properly detected, for example via\r\nthe following fragment in .vim\/filetype.vim: \r\n    augroup filetypedetect\r\n        \" Fortunes files. \r\n        autocmd BufNewFile,BufRead fortunes.txt,*\/fortunes\/*.txt setf fortunes \r\n    augroup END\r\nor manually set the filetype every time via \r\n    :setf fortunes\r\nIf you want to use this plugin also for other filetypes, e.g. \"txt\", create a\r\nfile ftplugin\/txt_movement.vim in your 'runtimepath' (usually ~\/.vim) with the\r\nfollowing contents: \r\n    runtime! ftplugin\/fortunes_movement.vim\r\nThis is more maintainable than simply renaming fortunes_movement.vim. ","first_name":"Ingo","6":"Ingo","last_name":"Karkat","7":"Karkat","releases":[{"0":"3181","vim_version":"7.0","1":"7.0","script_version":"1.10","2":"1.10","version_comment":"Switched definition of motion mappings from patterns to begin and end to a region of continguous lines defined by a non-matching pattern (representing the fortune separator line). This should make it more correct with corner cases. Requires CountJump version 1.30.","3":"Switched definition of motion mappings from patterns to begin and end to a region of continguous lines defined by a non-matching pattern (representing the fortune separator line). This should make it more correct with corner cases. Requires CountJump version 1.30.","package":"fortunes_movement.vba.gz","4":"fortunes_movement.vba.gz","src_id":"14586","5":"14586","creation_date":"1292836552","6":"1292836552"},{"0":"3181","vim_version":"7.0","1":"7.0","script_version":"1.00","2":"1.00","version_comment":"Initial upload","3":"Initial upload","package":"fortunes_movement.vba.gz","4":"fortunes_movement.vba.gz","src_id":"13465","5":"13465","creation_date":"1280844096","6":"1280844096"}]},"3180":{"script_id":"3180","0":"3180","script_name":"diff_movement","1":"diff_movement","script_type":"ftplugin","2":"ftplugin","summary":"Movement over diff hunks with ]] etc. ","3":"Movement over diff hunks with ]] etc. ","description":"DESCRIPTION\r\nThis filetype plugin provides movement commands and text objects for diff hunks.\r\nSupports traditional, context and unified diff formats.\r\n\r\nRELATED WORKS\r\n- textobj-gitgutter (vimscript #4458) provides an inner-hunk text object for\r\n  hunks provided by the vim-gitgutter plugin. It also requires textobj-user.\r\n\r\nUSAGE\r\n                        Move around diff hunks:\r\n]]                      Go to [count] next start of a diff hunk.\r\n][                      Go to [count] next end of a diff hunk.\r\n[[                      Go to [count] previous start of a diff hunk.\r\n[]                      Go to [count] previous end of a diff hunk.\r\n\r\nih                      \"inner hunk\" text object, select [count] hunk contents.\r\nah                      \"a hunk\" text object, select [count] hunks, including\r\n                        the header.","4":"DESCRIPTION\r\nThis filetype plugin provides movement commands and text objects for diff hunks.\r\nSupports traditional, context and unified diff formats.\r\n\r\nRELATED WORKS\r\n- textobj-gitgutter (vimscript #4458) provides an inner-hunk text object for\r\n  hunks provided by the vim-gitgutter plugin. It also requires textobj-user.\r\n\r\nUSAGE\r\n                        Move around diff hunks:\r\n]]                      Go to [count] next start of a diff hunk.\r\n][                      Go to [count] next end of a diff hunk.\r\n[[                      Go to [count] previous start of a diff hunk.\r\n[]                      Go to [count] previous end of a diff hunk.\r\n\r\nih                      \"inner hunk\" text object, select [count] hunk contents.\r\nah                      \"a hunk\" text object, select [count] hunks, including\r\n                        the header.","install_details":"INSTALLATION\r\nThis script is packaged as a vimball. If you have the \"gunzip\" decompressor\r\nin your PATH, simply edit the *.vmb.gz package in Vim; otherwise, decompress\r\nthe archive first, e.g. using WinZip. Inside Vim, install by sourcing the\r\nvimball or via the :UseVimball command.\r\n    vim diff_movement*.vmb.gz\r\n    :so %\r\nTo uninstall, use the :RmVimball command.\r\n\r\nDEPENDENCIES\r\n- Requires Vim 7.0 or higher.\r\n- Requires the CountJump plugin (vimscript #3130).","5":"INSTALLATION\r\nThis script is packaged as a vimball. If you have the \"gunzip\" decompressor\r\nin your PATH, simply edit the *.vmb.gz package in Vim; otherwise, decompress\r\nthe archive first, e.g. using WinZip. Inside Vim, install by sourcing the\r\nvimball or via the :UseVimball command.\r\n    vim diff_movement*.vmb.gz\r\n    :so %\r\nTo uninstall, use the :RmVimball command.\r\n\r\nDEPENDENCIES\r\n- Requires Vim 7.0 or higher.\r\n- Requires the CountJump plugin (vimscript #3130).","first_name":"Ingo","6":"Ingo","last_name":"Karkat","7":"Karkat","releases":[{"0":"3180","vim_version":"7.0","1":"7.0","script_version":"1.01","2":"1.01","version_comment":"Avoid use of s:function() by using autoload function name. This fixes a regression in Vim 7.3.1032, reported by lilydjwg.","3":"Avoid use of s:function() by using autoload function name. This fixes a regression in Vim 7.3.1032, reported by lilydjwg.","package":"diff_movement-1.01.vmb.gz","4":"diff_movement-1.01.vmb.gz","src_id":"20301","5":"20301","creation_date":"1370465384","6":"1370465384"},{"0":"3180","vim_version":"7.0","1":"7.0","script_version":"1.00","2":"1.00","version_comment":"Initial upload","3":"Initial upload","package":"diff_movement.vba.gz","4":"diff_movement.vba.gz","src_id":"13464","5":"13464","creation_date":"1280843961","6":"1280843961"}]},"3179":{"script_id":"3179","0":"3179","script_name":"help_movement","1":"help_movement","script_type":"ftplugin","2":"ftplugin","summary":"Movement over Vim help sections with ]] etc. ","3":"Movement over Vim help sections with ]] etc. ","description":"DESCRIPTION\r\nThis filetype plugin provides movement commands for Vim help sections.\r\n\r\nUSAGE\r\n                        Move around Vim help sections (starting with a =====\r\n                        line).\r\n]]                      Go to [count] next start of a help section.\r\n][                      Go to [count] next end of a help section.\r\n[[                      Go to [count] previous start of a help section.\r\n[]                      Go to [count] previous end of a help section.","4":"DESCRIPTION\r\nThis filetype plugin provides movement commands for Vim help sections.\r\n\r\nUSAGE\r\n                        Move around Vim help sections (starting with a =====\r\n                        line).\r\n]]                      Go to [count] next start of a help section.\r\n][                      Go to [count] next end of a help section.\r\n[[                      Go to [count] previous start of a help section.\r\n[]                      Go to [count] previous end of a help section.","install_details":"INSTALLATION\r\nThis script is packaged as a vimball. If you have the \"gunzip\" decompressor\r\nin your PATH, simply edit the *.vba.gz package in Vim; otherwise, decompress\r\nthe archive first, e.g. using WinZip. Inside Vim, install by sourcing the\r\nvimball or via the :UseVimball command.\r\n    vim help_movement.vba.gz\r\n    :so %\r\nTo uninstall, use the :RmVimball command. \r\n\r\nDEPENDENCIES\r\n- Requires Vim 7.0 or higher. \r\n- Requires the CountJump plugin (vimscript #3130). ","5":"INSTALLATION\r\nThis script is packaged as a vimball. If you have the \"gunzip\" decompressor\r\nin your PATH, simply edit the *.vba.gz package in Vim; otherwise, decompress\r\nthe archive first, e.g. using WinZip. Inside Vim, install by sourcing the\r\nvimball or via the :UseVimball command.\r\n    vim help_movement.vba.gz\r\n    :so %\r\nTo uninstall, use the :RmVimball command. \r\n\r\nDEPENDENCIES\r\n- Requires Vim 7.0 or higher. \r\n- Requires the CountJump plugin (vimscript #3130). ","first_name":"Ingo","6":"Ingo","last_name":"Karkat","7":"Karkat","releases":[{"0":"3179","vim_version":"7.0","1":"7.0","script_version":"1.00","2":"1.00","version_comment":"Initial upload","3":"Initial upload","package":"help_movement.vba.gz","4":"help_movement.vba.gz","src_id":"13463","5":"13463","creation_date":"1280843878","6":"1280843878"}]},"3178":{"script_id":"3178","0":"3178","script_name":"Shapley Values","1":"Shapley Values","script_type":"utility","2":"utility","summary":"This scripts computes Some Shapley values for Gmes with Externalities","3":"This scripts computes Some Shapley values for Gmes with Externalities","description":"The script provides tools to compute:\r\nShapley Value (also using Ieong-Shoham rules) of a Normal form game,\r\nMcQuillin-Shapley value\r\nPham-Do-Norde-Shapley value \r\nMeyrson-Shapley values                (all three for games in partition form, i.e. with externalities) \r\n","4":"The script provides tools to compute:\r\nShapley Value (also using Ieong-Shoham rules) of a Normal form game,\r\nMcQuillin-Shapley value\r\nPham-Do-Norde-Shapley value \r\nMeyrson-Shapley values                (all three for games in partition form, i.e. with externalities) \r\n","install_details":"Just open the script, and source it. It is self documented.","5":"Just open the script, and source it. It is self documented.","first_name":"Marcin","6":"Marcin","last_name":"Szamotulski","7":"Szamotulski","releases":[{"0":"3178","vim_version":"7.0","1":"7.0","script_version":"1","2":"1","version_comment":"Initial upload","3":"Initial upload","package":"shapley_values.vim","4":"shapley_values.vim","src_id":"13457","5":"13457","creation_date":"1280761172","6":"1280761172"}]},"3177":{"script_id":"3177","0":"3177","script_name":"BusierBee","1":"BusierBee","script_type":"color scheme","2":"color scheme","summary":"A modification of BusyBee.vim","3":"A modification of BusyBee.vim","description":"This is a (tiny) modification of the BusyBee colour scheme (\"vimscript #2549\") by Patrick J. Anderson... basically just changed Function colours to be different from Normal colours (hence the \"busier\") and tweaked the String colour.","4":"This is a (tiny) modification of the BusyBee colour scheme (\"vimscript #2549\") by Patrick J. Anderson... basically just changed Function colours to be different from Normal colours (hence the \"busier\") and tweaked the String colour.","install_details":"Copy to ~\/.vim\/colors","5":"Copy to ~\/.vim\/colors","first_name":"Stuart","6":"Stuart","last_name":"Radnidge","7":"Radnidge","releases":[{"0":"3177","vim_version":"7.0","1":"7.0","script_version":"1.0.0","2":"1.0.0","version_comment":"Initial upload","3":"Initial upload","package":"busierbee.vim","4":"busierbee.vim","src_id":"13453","5":"13453","creation_date":"1280683349","6":"1280683349"}]},"3176":{"script_id":"3176","0":"3176","script_name":"typeredeemer","1":"typeredeemer","script_type":"utility","2":"utility","summary":"Simple font-size unit conversion for your CSS stylesheets","3":"Simple font-size unit conversion for your CSS stylesheets","description":"Ever wanted to change your font-size\/line-height declarations from one unit to another without resorting to going back and forth between vim and an online conversion tool? This script lets you convert between px, em and % values through the use of some simple key mappings.\r\n\r\nMappings for converting one font-size\/line-height declaration at a time include:\r\n\r\n<leader>px - convert value to px equivalent\r\n<leader>em - convert value to em equivalent\r\n<leader>p% - convert value to percent equivalent\r\n\r\nTo convert all font-size and line-height declarations at the same time:\r\n\r\n<leader>apx - convert all to px\r\n<leader>aem - convert all to em\r\n<leader>ap% - convert all to %\r\n\r\nYou don't have to be bound to the browser default size of 16px, which this script uses by default. To change this value, use the mapping '<leader>sd' and specify a new default size in px (i.e. 17.0). To check what this value is at any time, use the mapping '<leader>gd'.","4":"Ever wanted to change your font-size\/line-height declarations from one unit to another without resorting to going back and forth between vim and an online conversion tool? This script lets you convert between px, em and % values through the use of some simple key mappings.\r\n\r\nMappings for converting one font-size\/line-height declaration at a time include:\r\n\r\n<leader>px - convert value to px equivalent\r\n<leader>em - convert value to em equivalent\r\n<leader>p% - convert value to percent equivalent\r\n\r\nTo convert all font-size and line-height declarations at the same time:\r\n\r\n<leader>apx - convert all to px\r\n<leader>aem - convert all to em\r\n<leader>ap% - convert all to %\r\n\r\nYou don't have to be bound to the browser default size of 16px, which this script uses by default. To change this value, use the mapping '<leader>sd' and specify a new default size in px (i.e. 17.0). To check what this value is at any time, use the mapping '<leader>gd'.","install_details":"Unzip in your ~\/.vim folder and run :helptags ~\/.vim\/doc.","5":"Unzip in your ~\/.vim folder and run :helptags ~\/.vim\/doc.","first_name":"Lou","6":"Lou","last_name":"Gonzalez","7":"Gonzalez","releases":[{"0":"3176","vim_version":"7.0","1":"7.0","script_version":"0.1.0","2":"0.1.0","version_comment":"Initial upload","3":"Initial upload","package":"typeredeemer.zip","4":"typeredeemer.zip","src_id":"13448","5":"13448","creation_date":"1280609651","6":"1280609651"}]},"3175":{"script_id":"3175","0":"3175","script_name":"Haskell Highlight Enhanced","1":"Haskell Highlight Enhanced","script_type":"syntax","2":"syntax","summary":"highlight all Haskell98 standard function & classes & datatypes","3":"highlight all Haskell98 standard function & classes & datatypes","description":"Mainly based on the plugin (http:\/\/www.vim.org\/scripts\/script.php?script_id=2062) which is no longer maintained,\r\nthe last version is 1.2, so I get started from 1.3.\r\nThx to it !\r\n\r\nThat one regards 'class' and 'datatype' as the same, but this one separates them.\r\nThat one only highlights the func & class & datatype in the standard Prelude, but this one includes all the official.\r\n\r\nHere's the SNAPSHOT\r\nhttp:\/\/treblih.is-programmer.com\/user_files\/treblih\/Image\/hask.png\r\n\r\nU could see that 'datatype' and 'keyword' are in green, while 'class' in black, function in purple.\r\n\r\nEnjoy","4":"Mainly based on the plugin (http:\/\/www.vim.org\/scripts\/script.php?script_id=2062) which is no longer maintained,\r\nthe last version is 1.2, so I get started from 1.3.\r\nThx to it !\r\n\r\nThat one regards 'class' and 'datatype' as the same, but this one separates them.\r\nThat one only highlights the func & class & datatype in the standard Prelude, but this one includes all the official.\r\n\r\nHere's the SNAPSHOT\r\nhttp:\/\/treblih.is-programmer.com\/user_files\/treblih\/Image\/hask.png\r\n\r\nU could see that 'datatype' and 'keyword' are in green, while 'class' in black, function in purple.\r\n\r\nEnjoy","install_details":"just put haskell.vim to ~\/.vim\/syntax\/","5":"just put haskell.vim to ~\/.vim\/syntax\/","first_name":"Yang","6":"Yang","last_name":"Zhang","7":"Zhang","releases":[{"0":"3175","vim_version":"7.0","1":"7.0","script_version":"1.4","2":"1.4","version_comment":"bug fixed","3":"bug fixed","package":"haskell.vim","4":"haskell.vim","src_id":"13451","5":"13451","creation_date":"1280659958","6":"1280659958"},{"0":"3175","vim_version":"7.2","1":"7.2","script_version":"1.3","2":"1.3","version_comment":"Initial upload","3":"Initial upload","package":"haskell.vim","4":"haskell.vim","src_id":"13445","5":"13445","creation_date":"1280552083","6":"1280552083"}]},"3174":{"script_id":"3174","0":"3174","script_name":"JsLint Helper","1":"JsLint Helper","script_type":"utility","2":"utility","summary":"a javascript code validator","3":"a javascript code validator","description":"when use  \":w\" to save a .js file, this plugin will validate its content and display the errors via Vim's sign functionality.\r\n\r\nscreen shot:\r\nhttp:\/\/i1021.photobucket.com\/albums\/af333\/aj3423\/jslint.png\r\n\r\nonly for windows\r\n","4":"when use  \":w\" to save a .js file, this plugin will validate its content and display the errors via Vim's sign functionality.\r\n\r\nscreen shot:\r\nhttp:\/\/i1021.photobucket.com\/albums\/af333\/aj3423\/jslint.png\r\n\r\nonly for windows\r\n","install_details":"1.  install Jslint\r\n      1)  download it here:   http:\/\/www.javascriptlint.com\/download.htm\r\n      2)  extract it in some folder, and add this folder to the \"path\" environment variable\r\n      3)  try command \"jsl\" in command line , make sure it is available\r\n\r\n2.  put it in  \"\/vimfiles\/plugin\"  ","5":"1.  install Jslint\r\n      1)  download it here:   http:\/\/www.javascriptlint.com\/download.htm\r\n      2)  extract it in some folder, and add this folder to the \"path\" environment variable\r\n      3)  try command \"jsl\" in command line , make sure it is available\r\n\r\n2.  put it in  \"\/vimfiles\/plugin\"  ","first_name":"aj3423","6":"aj3423","last_name":" ","7":" ","releases":[{"0":"3174","vim_version":"7.2","1":"7.2","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"jsLintHelper.vim","4":"jsLintHelper.vim","src_id":"13437","5":"13437","creation_date":"1280495858","6":"1280495858"}]},"3173":{"script_id":"3173","0":"3173","script_name":"vimgcwsyntax","1":"vimgcwsyntax","script_type":"syntax","2":"syntax","summary":"Vim Syntax File for Google Code Wiki","3":"Vim Syntax File for Google Code Wiki","description":"This is a syntax file for Google Code Wiki, supporting highlighting of main features of Google Code Wiki, like:\r\n\r\n* Formating (bold, emphasis etc.)\r\n* Code text\r\n* Block links\r\n* Google Code Wiki pragmas\r\n* Titles\r\n* Folding between sections and in code block\r\n\r\nBesides syntax and folding features, it has a powerful function for the formatexpr option. Just :set formatexpr=googlecodewiki#FormatExpr() and you will be able to format your texts without breaking link blocks or quote blocks. This features can be turned off with global variables.\r\n\r\nYou might want to follow its development on its Google Code page: http:\/\/code.google.com\/p\/vimgcwsyntax\/","4":"This is a syntax file for Google Code Wiki, supporting highlighting of main features of Google Code Wiki, like:\r\n\r\n* Formating (bold, emphasis etc.)\r\n* Code text\r\n* Block links\r\n* Google Code Wiki pragmas\r\n* Titles\r\n* Folding between sections and in code block\r\n\r\nBesides syntax and folding features, it has a powerful function for the formatexpr option. Just :set formatexpr=googlecodewiki#FormatExpr() and you will be able to format your texts without breaking link blocks or quote blocks. This features can be turned off with global variables.\r\n\r\nYou might want to follow its development on its Google Code page: http:\/\/code.google.com\/p\/vimgcwsyntax\/","install_details":"Just put it in your syntax directory. In you .vimrc, include the following line to associate .wiki files to the googlecodewiki syntax:\r\n\r\nautocmd BufNewFile,BufRead *.wiki set ft=googlecodewiki","5":"Just put it in your syntax directory. In you .vimrc, include the following line to associate .wiki files to the googlecodewiki syntax:\r\n\r\nautocmd BufNewFile,BufRead *.wiki set ft=googlecodewiki","first_name":"Silas","6":"Silas","last_name":"Silva","7":"Silva","releases":[{"0":"3173","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Vim Google Syntax File for Google Code Wiki is stable and it is 1.0 now.  Changes include:\r\n\r\n* Split syntax and ftplugin functionality in different files.\r\n* Fixed issue 2, that triggered errors when functions were reloaded\r\n* Dropped version for Vim versions lower than 7.","3":"Vim Google Syntax File for Google Code Wiki is stable and it is 1.0 now.  Changes include:\r\n\r\n* Split syntax and ftplugin functionality in different files.\r\n* Fixed issue 2, that triggered errors when functions were reloaded\r\n* Dropped version for Vim versions lower than 7.","package":"vimgcwsyntax-1.0.tar.gz","4":"vimgcwsyntax-1.0.tar.gz","src_id":"13989","5":"13989","creation_date":"1286227837","6":"1286227837"},{"0":"3173","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"googlecodewiki.vim","4":"googlecodewiki.vim","src_id":"13434","5":"13434","creation_date":"1280457336","6":"1280457336"}]},"3172":{"script_id":"3172","0":"3172","script_name":"SyntaxComplete","1":"SyntaxComplete","script_type":"utility","2":"utility","summary":"OMNI Completion based on the current syntax highlights","3":"OMNI Completion based on the current syntax highlights","description":"SyntaxComplete.vim is a plugin which uses the new Vim7 OMNI completion features (intellisense code completion).\r\n\r\nSyntaxComplete.vim version 5.0 is included in the Vim 7.2 release.\r\nSyntaxComplete.vim version 7.0 is included in the Vim 7.3 release.\r\nSyntaxComplete.vim version 8.0 is included in the Vim 7.3 release.\r\nSyntaxComplete.vim version 9.0 is included in the Vim 7.3 release.\r\nSyntaxComplete.vim version 10.0 is included in the Vim 7.3 release.\r\nSyntaxComplete.vim version 11.0 is included in the Vim 7.3 release.\r\nSyntaxComplete.vim version 12.0 is included in the Vim 7.3 release.\r\nSyntaxComplete.vim version 13.0 is included in the Vim 7.3 release.\r\nSyntaxComplete.vim version 13.0 is included in the Vim 8.1 release.\r\nSyntaxComplete.vim version 14.0 is included in the Vim 8.2 release.\r\n\r\nWhat does it do:\r\n-----------------------\r\nVim has the ability to color syntax highlight nearly 500 languages.  Part of this highlighting includes knowing what keywords are part of a language.  Many filetypes already have custom completion scripts written for them, the syntaxcomplete plugin provides basic completion for all other filetypes.  It does this by populating the omni completion list with the text Vim already knows how to color highlight.  It can be used for any filetype and provides a minimal language-sensitive completion.\r\n\r\nThere are not many languages with full blown OMNI completion scripts written in Vim.  Yet, having a list of functions and keywords to complete can be very handy especially when you are working with a predefined API.\r\n\r\nAdding the following to your .vimrc, will setup SyntaxComplete for every filetype that does not already have a language specific OMNI script:\r\n\r\n    if has(\"autocmd\") && exists(\"+omnifunc\")\r\n\tautocmd Filetype *\r\n\t\t    \\\tif &omnifunc == \"\" |\r\n\t\t    \\\t\tsetlocal omnifunc=syntaxcomplete#Complete |\r\n\t\t    \\\tendif\r\n    endif\r\n\r\n\r\nIt also provides some public functions so other plugin writers can pull syntax keywords (based on group names) from Vim and utilize them in any manor.  Examples are included in the help files, but here is a simple example:\r\n    let myKeywords = []\r\n    let myKeywords = OmniSyntaxList( ['sqlKeyword'] )\r\n    let allItems = OmniSyntaxList( [] )\r\n\r\nRegex can also be used to identify which syntax groups to include:\r\n    let myKeywords = OmniSyntaxList( ['html\\w\\+', 'jquery\\w\\+'] )\r\n\r\n\r\n\r\nExisting instructions can be found within Vim7 using\r\n:h ft-syntax-omni\r\n\r\nThis plugin is new to Vim7.  Improvements to the script will be uploaded here, and supplied to Bram for inclusion into future versions of Vim7.\r\n \r\nThere are many customizations which can be made per filetype via your .vimrc.  See the documentation for details.\r\n\r\n","4":"SyntaxComplete.vim is a plugin which uses the new Vim7 OMNI completion features (intellisense code completion).\r\n\r\nSyntaxComplete.vim version 5.0 is included in the Vim 7.2 release.\r\nSyntaxComplete.vim version 7.0 is included in the Vim 7.3 release.\r\nSyntaxComplete.vim version 8.0 is included in the Vim 7.3 release.\r\nSyntaxComplete.vim version 9.0 is included in the Vim 7.3 release.\r\nSyntaxComplete.vim version 10.0 is included in the Vim 7.3 release.\r\nSyntaxComplete.vim version 11.0 is included in the Vim 7.3 release.\r\nSyntaxComplete.vim version 12.0 is included in the Vim 7.3 release.\r\nSyntaxComplete.vim version 13.0 is included in the Vim 7.3 release.\r\nSyntaxComplete.vim version 13.0 is included in the Vim 8.1 release.\r\nSyntaxComplete.vim version 14.0 is included in the Vim 8.2 release.\r\n\r\nWhat does it do:\r\n-----------------------\r\nVim has the ability to color syntax highlight nearly 500 languages.  Part of this highlighting includes knowing what keywords are part of a language.  Many filetypes already have custom completion scripts written for them, the syntaxcomplete plugin provides basic completion for all other filetypes.  It does this by populating the omni completion list with the text Vim already knows how to color highlight.  It can be used for any filetype and provides a minimal language-sensitive completion.\r\n\r\nThere are not many languages with full blown OMNI completion scripts written in Vim.  Yet, having a list of functions and keywords to complete can be very handy especially when you are working with a predefined API.\r\n\r\nAdding the following to your .vimrc, will setup SyntaxComplete for every filetype that does not already have a language specific OMNI script:\r\n\r\n    if has(\"autocmd\") && exists(\"+omnifunc\")\r\n\tautocmd Filetype *\r\n\t\t    \\\tif &omnifunc == \"\" |\r\n\t\t    \\\t\tsetlocal omnifunc=syntaxcomplete#Complete |\r\n\t\t    \\\tendif\r\n    endif\r\n\r\n\r\nIt also provides some public functions so other plugin writers can pull syntax keywords (based on group names) from Vim and utilize them in any manor.  Examples are included in the help files, but here is a simple example:\r\n    let myKeywords = []\r\n    let myKeywords = OmniSyntaxList( ['sqlKeyword'] )\r\n    let allItems = OmniSyntaxList( [] )\r\n\r\nRegex can also be used to identify which syntax groups to include:\r\n    let myKeywords = OmniSyntaxList( ['html\\w\\+', 'jquery\\w\\+'] )\r\n\r\n\r\n\r\nExisting instructions can be found within Vim7 using\r\n:h ft-syntax-omni\r\n\r\nThis plugin is new to Vim7.  Improvements to the script will be uploaded here, and supplied to Bram for inclusion into future versions of Vim7.\r\n \r\nThere are many customizations which can be made per filetype via your .vimrc.  See the documentation for details.\r\n\r\n","install_details":"install details\r\nCopy syntaxcomplete.vim to:\r\n.vim\/autoload\/syntaxcomplete.vim (Unix)\r\nvimfiles\\autoload\\syntaxcomplete.vim (Windows)\r\n\r\nFor documentation:\r\n:h ft-syntax-omni ","5":"install details\r\nCopy syntaxcomplete.vim to:\r\n.vim\/autoload\/syntaxcomplete.vim (Unix)\r\nvimfiles\\autoload\\syntaxcomplete.vim (Windows)\r\n\r\nFor documentation:\r\n:h ft-syntax-omni ","first_name":"David","6":"David","last_name":"Fishburn","7":"Fishburn","releases":[{"0":"3172","vim_version":"7.0","1":"7.0","script_version":"15.0","2":"15.0","version_comment":"NF: You can no override filetype specific global variables with buffer local variables.\r\n\r\nBF: SyntaxComplete ignored all buffer specific overrides, always used global","3":"NF: You can no override filetype specific global variables with buffer local variables.\r\n\r\nBF: SyntaxComplete ignored all buffer specific overrides, always used global","package":"syntaxcomplete.vim","4":"syntaxcomplete.vim","src_id":"27579","5":"27579","creation_date":"1619612745","6":"1619612745"},{"0":"3172","vim_version":"7.0","1":"7.0","script_version":"14.0","2":"14.0","version_comment":"BF: A single quote and is_keyword contains 39, an invalid expression is reported.","3":"BF: A single quote and is_keyword contains 39, an invalid expression is reported.","package":"syntaxcomplete.vim","4":"syntaxcomplete.vim","src_id":"27425","5":"27425","creation_date":"1609227296","6":"1609227296"},{"0":"3172","vim_version":"7.0","1":"7.0","script_version":"13.0","2":"13.0","version_comment":"NF: Extended the option omni_syntax_group_include_{filetype} to accept a comma separated list of regex's rather than string.  For example, for the javascript filetype you could use:\r\n     let g:omni_syntax_group_include_javascript = 'javascript\\w\\+,jquery\\w\\+'\r\n\r\nNF: Some syntax files (perl.vim) use the match \/\/ syntax as a mechanism to identify keywords.  This update attempts to parse the match syntax and pull out syntax items which are at least 3 words or more.\r\n","3":"NF: Extended the option omni_syntax_group_include_{filetype} to accept a comma separated list of regex's rather than string.  For example, for the javascript filetype you could use:\r\n     let g:omni_syntax_group_include_javascript = 'javascript\\w\\+,jquery\\w\\+'\r\n\r\nNF: Some syntax files (perl.vim) use the match \/\/ syntax as a mechanism to identify keywords.  This update attempts to parse the match syntax and pull out syntax items which are at least 3 words or more.\r\n","package":"syntaxcomplete.vim","4":"syntaxcomplete.vim","src_id":"20270","5":"20270","creation_date":"1370209449","6":"1370209449"},{"0":"3172","vim_version":"7.0","1":"7.0","script_version":"12.0","2":"12.0","version_comment":"Version 12.0\r\n\r\nBF: It is possible to have '-' as part of iskeyword, when checking for character ranges, tighten up the regex.  E688: More targets than List items.\r\n                                                          \r\nVersion 11.0\r\n \r\nBF: Corrected which characters required escaping during substitution calls.\r\n","3":"Version 12.0\r\n\r\nBF: It is possible to have '-' as part of iskeyword, when checking for character ranges, tighten up the regex.  E688: More targets than List items.\r\n                                                          \r\nVersion 11.0\r\n \r\nBF: Corrected which characters required escaping during substitution calls.\r\n","package":"syntaxcomplete.vim","4":"syntaxcomplete.vim","src_id":"19470","5":"19470","creation_date":"1359994334","6":"1359994334"},{"0":"3172","vim_version":"7.0","1":"7.0","script_version":"10.0","2":"10.0","version_comment":"Cycle through all the character ranges specified in the\r\niskeyword option and build a list of valid word separators.\r\n\r\nPrior to this change, only actual characters were used, \r\nwhere for example ASCII \"45\" == \"-\".  If \"45\" were used \r\nin iskeyword the hyphen would not be picked up.  \r\n\r\nThis introduces a new option, since the character ranges\r\nspecified could be multibyte:\r\n    let g:omni_syntax_use_single_byte = 1\r\n\r\nThis by default will only allow single byte ASCII \r\ncharacters to be added and an additional check to ensure\r\nthe character is printable (see documentation for isprint).\r\n","3":"Cycle through all the character ranges specified in the\r\niskeyword option and build a list of valid word separators.\r\n\r\nPrior to this change, only actual characters were used, \r\nwhere for example ASCII \"45\" == \"-\".  If \"45\" were used \r\nin iskeyword the hyphen would not be picked up.  \r\n\r\nThis introduces a new option, since the character ranges\r\nspecified could be multibyte:\r\n    let g:omni_syntax_use_single_byte = 1\r\n\r\nThis by default will only allow single byte ASCII \r\ncharacters to be added and an additional check to ensure\r\nthe character is printable (see documentation for isprint).\r\n","package":"syntaxcomplete.vim","4":"syntaxcomplete.vim","src_id":"18847","5":"18847","creation_date":"1350782753","6":"1350782753"},{"0":"3172","vim_version":"7.3","1":"7.3","script_version":"9.0","2":"9.0","version_comment":"Included in Vim 7.3 but you must pull from Vim sources.  This will allow you to update to it.\r\n\r\nVersion 9.0\r\n- Add the check for cpo.\r\n                                                             \r\nVersion 8.0\r\n- Updated SyntaxCSyntaxGroupItems()\r\n        - Some additional syntax items were also allowed\r\n          on nextgroup= lines which were ignored by default.\r\n          Now these lines are processed independently.\r\n","3":"Included in Vim 7.3 but you must pull from Vim sources.  This will allow you to update to it.\r\n\r\nVersion 9.0\r\n- Add the check for cpo.\r\n                                                             \r\nVersion 8.0\r\n- Updated SyntaxCSyntaxGroupItems()\r\n        - Some additional syntax items were also allowed\r\n          on nextgroup= lines which were ignored by default.\r\n          Now these lines are processed independently.\r\n","package":"syntaxcomplete.vim","4":"syntaxcomplete.vim","src_id":"17832","5":"17832","creation_date":"1335645227","6":"1335645227"},{"0":"3172","vim_version":"7.0","1":"7.0","script_version":"7.0","2":"7.0","version_comment":"Initial upload","3":"Initial upload","package":"syntaxcomplete.vim","4":"syntaxcomplete.vim","src_id":"13428","5":"13428","creation_date":"1280410623","6":"1280410623"}]},"3171":{"script_id":"3171","0":"3171","script_name":"phpcomplete.vim","1":"phpcomplete.vim","script_type":"ftplugin","2":"ftplugin","summary":"php omnicomplete with extra support","3":"php omnicomplete with extra support","description":"Default phpcomplete.vim does not support in-file checking of $var = new Class; so if you don't have a tags file with the variable in it already you have to hack around it by placing the comment \/* @var $yourvar YourClass *\/ above the line which is really kludgy.\r\n\r\nThis patch allows for in-file checking so you don't need the comment.\r\n\r\n$instance = new Class;\r\n...\r\n$instance->Blah(); \/\/ <-- complete without comment\r\n\r\nIt also allows support for singleton instantiations:\r\n\r\n$instance = Class::getInstance();\r\n$instance->completeMe(); \/\/ sweet completion\r\n\r\n=== Usage ===\r\n\/\/ example class which has a TAGS file generated for it somewhere\r\nclass SomeClass {\r\n  private function _private_method() {} \/\/ never shows up in completion list\r\n  public static function staticMethod() {} \/\/ only shows up when using completion on SomeClass::<C-X><C-O>\r\n  public function completeMe() {} \/\/ only shows up when using completion on $instance_of_someclass-><C-X><C-O>\r\n}\r\n\r\n== Non-static completion ==\r\n$instance = new SomeClass;\r\n...\r\n$instance-><C-X><C-O> to display the omnicompletion menu (see :help ins-completion)\r\n$instance->completeMe(); \/\/ will autoselect completeMe since it's the only public non-static method\r\n\r\n== Static completion ==\r\nSomeClass::<C-X><C-O> to display omnicompletion menu\r\nSomeClass::staticMethod(); \/\/ once again will autoselect staticMethod since it's the only public static method\r\n\r\n== Singleton completion ==\r\n$instance = SomeClass::getInstance();\r\n$instance-><C-X><C-O> complete just like non-static\r\n\r\n\r\n\r\n=== Other features ===\r\n * Correct restriction of static or standard methods based on context ( show only static methods with :: and only standard with ->)\r\n * Real support for self:: and $this-> with the aforementioned context restriction\r\n * Constant variable completion (not just define(VARIABLE, 1) but const VARIABLE = 1)\r\n\r\nFollow updates:\r\nhttp:\/\/github.com\/shawncplus\/phpcomplete.vim","4":"Default phpcomplete.vim does not support in-file checking of $var = new Class; so if you don't have a tags file with the variable in it already you have to hack around it by placing the comment \/* @var $yourvar YourClass *\/ above the line which is really kludgy.\r\n\r\nThis patch allows for in-file checking so you don't need the comment.\r\n\r\n$instance = new Class;\r\n...\r\n$instance->Blah(); \/\/ <-- complete without comment\r\n\r\nIt also allows support for singleton instantiations:\r\n\r\n$instance = Class::getInstance();\r\n$instance->completeMe(); \/\/ sweet completion\r\n\r\n=== Usage ===\r\n\/\/ example class which has a TAGS file generated for it somewhere\r\nclass SomeClass {\r\n  private function _private_method() {} \/\/ never shows up in completion list\r\n  public static function staticMethod() {} \/\/ only shows up when using completion on SomeClass::<C-X><C-O>\r\n  public function completeMe() {} \/\/ only shows up when using completion on $instance_of_someclass-><C-X><C-O>\r\n}\r\n\r\n== Non-static completion ==\r\n$instance = new SomeClass;\r\n...\r\n$instance-><C-X><C-O> to display the omnicompletion menu (see :help ins-completion)\r\n$instance->completeMe(); \/\/ will autoselect completeMe since it's the only public non-static method\r\n\r\n== Static completion ==\r\nSomeClass::<C-X><C-O> to display omnicompletion menu\r\nSomeClass::staticMethod(); \/\/ once again will autoselect staticMethod since it's the only public static method\r\n\r\n== Singleton completion ==\r\n$instance = SomeClass::getInstance();\r\n$instance-><C-X><C-O> complete just like non-static\r\n\r\n\r\n\r\n=== Other features ===\r\n * Correct restriction of static or standard methods based on context ( show only static methods with :: and only standard with ->)\r\n * Real support for self:: and $this-> with the aforementioned context restriction\r\n * Constant variable completion (not just define(VARIABLE, 1) but const VARIABLE = 1)\r\n\r\nFollow updates:\r\nhttp:\/\/github.com\/shawncplus\/phpcomplete.vim","install_details":"Place in $HOME\/.vim\/autoload\/phpcomplete.vim and enable the php ftplugin","5":"Place in $HOME\/.vim\/autoload\/phpcomplete.vim and enable the php ftplugin","first_name":"Shawn","6":"Shawn","last_name":"Biddle","7":"Biddle","releases":[{"0":"3171","vim_version":"7.0","1":"7.0","script_version":"1.3.3","2":"1.3.3","version_comment":"Also do in-file checking for static completion","3":"Also do in-file checking for static completion","package":"phpcomplete.vim","4":"phpcomplete.vim","src_id":"14129","5":"14129","creation_date":"1288137339","6":"1288137339"},{"0":"3171","vim_version":"7.0","1":"7.0","script_version":"1.3.2","2":"1.3.2","version_comment":"Don't complete self::, static::, or $this-> while outside of a class","3":"Don't complete self::, static::, or $this-> while outside of a class","package":"phpcomplete.vim","4":"phpcomplete.vim","src_id":"13496","5":"13496","creation_date":"1281030958","6":"1281030958"},{"0":"3171","vim_version":"7.0","1":"7.0","script_version":"1.3.1","2":"1.3.1","version_comment":"Support for PHP 5.3's LSB static:: context","3":"Support for PHP 5.3's LSB static:: context","package":"phpcomplete.vim","4":"phpcomplete.vim","src_id":"13494","5":"13494","creation_date":"1281024672","6":"1281024672"},{"0":"3171","vim_version":"7.0","1":"7.0","script_version":"1.3","2":"1.3","version_comment":"Correctly limit completion lists to static or normal methods based on :: or ->. Adds support for self:: completion","3":"Correctly limit completion lists to static or normal methods based on :: or ->. Adds support for self:: completion","package":"phpcomplete.vim","4":"phpcomplete.vim","src_id":"13431","5":"13431","creation_date":"1280438078","6":"1280438078"},{"0":"3171","vim_version":"7.0","1":"7.0","script_version":"1.2","2":"1.2","version_comment":"Added in-file completion for $this-> context","3":"Added in-file completion for $this-> context","package":"phpcomplete.vim","4":"phpcomplete.vim","src_id":"13429","5":"13429","creation_date":"1280427510","6":"1280427510"},{"0":"3171","vim_version":"7.0","1":"7.0","script_version":"1.1","2":"1.1","version_comment":"Added support for completion of const variables (const SOMETHING = 1;, not just \r\ndefine(\"SOMETHING\", 1);) ","3":"Added support for completion of const variables (const SOMETHING = 1;, not just \r\ndefine(\"SOMETHING\", 1);) ","package":"phpcomplete.vim","4":"phpcomplete.vim","src_id":"13421","5":"13421","creation_date":"1280353640","6":"1280353640"},{"0":"3171","vim_version":"7.2","1":"7.2","script_version":"1","2":"1","version_comment":"Initial upload","3":"Initial upload","package":"phpcomplete.vim","4":"phpcomplete.vim","src_id":"13419","5":"13419","creation_date":"1280337683","6":"1280337683"}]},"3170":{"script_id":"3170","0":"3170","script_name":"foo","1":"foo","script_type":"color scheme","2":"color scheme","summary":"placeholder","3":"placeholder","description":"none","4":"none","install_details":"","5":"","first_name":"Ted","6":"Ted","last_name":"Dele","7":"Dele","releases":[{"0":"3170","vim_version":"7.2","1":"7.2","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"pw.vim","4":"pw.vim","src_id":"13418","5":"13418","creation_date":"1280337414","6":"1280337414"}]},"3169":{"script_id":"3169","0":"3169","script_name":"luainspect.vim","1":"luainspect.vim","script_type":"syntax","2":"syntax","summary":"Semantic highlighting for Lua in Vim","3":"Semantic highlighting for Lua in Vim","description":"This Vim plug-in uses the LuaInspect tool to (automatically) perform semantic highlighting of variables in Lua source code. It was inspired by lua2-mode (for Emacs) and the SciTE plug-in included with LuaInspect. For more information about the plug-in please refer to its homepage or the project page on GitHub:\r\n\r\n \u00e2\u0080\u00a2 http:\/\/peterodding.com\/code\/vim\/lua-inspect\/\r\n \u00e2\u0080\u00a2 http:\/\/github.com\/xolox\/vim-lua-inspect\r\n\r\nIf you have questions, bug reports, suggestions, etc. the author can be contacted at peter@peterodding.com. If you like this plug-in please vote for it below!","4":"This Vim plug-in uses the LuaInspect tool to (automatically) perform semantic highlighting of variables in Lua source code. It was inspired by lua2-mode (for Emacs) and the SciTE plug-in included with LuaInspect. For more information about the plug-in please refer to its homepage or the project page on GitHub:\r\n\r\n \u00e2\u0080\u00a2 http:\/\/peterodding.com\/code\/vim\/lua-inspect\/\r\n \u00e2\u0080\u00a2 http:\/\/github.com\/xolox\/vim-lua-inspect\r\n\r\nIf you have questions, bug reports, suggestions, etc. the author can be contacted at peter@peterodding.com. If you like this plug-in please vote for it below!","install_details":"Please note that the vim-lua-inspect plug-in requires my vim-misc plug-in which is separately distributed (see vimscript #4597).\r\n\r\nUnzip the most recent ZIP archives of the vim-lua-inspect and vim-misc plug-ins inside your Vim profile directory (usually this is ~\/.vim on UNIX and %USERPROFILE%\\vimfiles on Windows), restart Vim and execute the command :helptags ~\/.vim\/doc (use :helptags ~\\vimfiles\\doc instead on Windows).\r\n\r\nIf you prefer you can also use Pathogen, Vundle or a similar tool to install & update the vim-lua-inspect and vim-misc plug-ins using a local clone of the git repository.\r\n\r\nNow try it out: Edit a Lua file and within a few seconds semantic highlighting should be enabled automatically!\r\n\r\nNote that on Windows a command prompt window pops up whenever LuaInspect is run as an external process. If this bothers you then you can install my shell.vim plug-in (see vimscript #3123) which includes a DLL that works around this issue. Once you\u00e2\u0080\u0099ve installed both plug-ins it should work out of the box!","5":"Please note that the vim-lua-inspect plug-in requires my vim-misc plug-in which is separately distributed (see vimscript #4597).\r\n\r\nUnzip the most recent ZIP archives of the vim-lua-inspect and vim-misc plug-ins inside your Vim profile directory (usually this is ~\/.vim on UNIX and %USERPROFILE%\\vimfiles on Windows), restart Vim and execute the command :helptags ~\/.vim\/doc (use :helptags ~\\vimfiles\\doc instead on Windows).\r\n\r\nIf you prefer you can also use Pathogen, Vundle or a similar tool to install & update the vim-lua-inspect and vim-misc plug-ins using a local clone of the git repository.\r\n\r\nNow try it out: Edit a Lua file and within a few seconds semantic highlighting should be enabled automatically!\r\n\r\nNote that on Windows a command prompt window pops up whenever LuaInspect is run as an external process. If this bothers you then you can install my shell.vim plug-in (see vimscript #3123) which includes a DLL that works around this issue. Once you\u00e2\u0080\u0099ve installed both plug-ins it should work out of the box!","first_name":"Peter","6":"Peter","last_name":"Odding","7":"Odding","releases":[{"0":"3169","vim_version":"7.0","1":"7.0","script_version":"0.5.2","2":"0.5.2","version_comment":" \u00e2\u0080\u00a2 Tackle pull request #4 - Allow alternative mappings:\n   http:\/\/github.com\/xolox\/vim-lua-inspect\/commit\/0e59882","3":" \u00e2\u0080\u00a2 Tackle pull request #4 - Allow alternative mappings:\n   http:\/\/github.com\/xolox\/vim-lua-inspect\/commit\/0e59882","package":"luainspect.zip","4":"luainspect.zip","src_id":"22046","5":"22046","creation_date":"1403030873","6":"1403030873"},{"0":"3169","vim_version":"7.0","1":"7.0","script_version":"0.5.1","2":"0.5.1","version_comment":" \u00e2\u0080\u00a2 Mention LuaInspect and Metalua licenses in README:\n   http:\/\/github.com\/xolox\/vim-lua-inspect\/commit\/c79c8d9\n\n \u00e2\u0080\u00a2 Make sure vim-misc is installed, politely complain if it isn't:\n   http:\/\/github.com\/xolox\/vim-lua-inspect\/commit\/d7fb876","3":" \u00e2\u0080\u00a2 Mention LuaInspect and Metalua licenses in README:\n   http:\/\/github.com\/xolox\/vim-lua-inspect\/commit\/c79c8d9\n\n \u00e2\u0080\u00a2 Make sure vim-misc is installed, politely complain if it isn't:\n   http:\/\/github.com\/xolox\/vim-lua-inspect\/commit\/d7fb876","package":"luainspect.zip","4":"luainspect.zip","src_id":"20683","5":"20683","creation_date":"1376932139","6":"1376932139"},{"0":"3169","vim_version":"7.0","1":"7.0","script_version":"0.5","2":"0.5","version_comment":" \u00e2\u0080\u00a2 Support for Lua 5.2 (updated to latest version of LuaInspect):\n   http:\/\/github.com\/xolox\/vim-lua-inspect\/commit\/0bf9775","3":" \u00e2\u0080\u00a2 Support for Lua 5.2 (updated to latest version of LuaInspect):\n   http:\/\/github.com\/xolox\/vim-lua-inspect\/commit\/0bf9775","package":"luainspect.zip","4":"luainspect.zip","src_id":"20538","5":"20538","creation_date":"1374181445","6":"1374181445"},{"0":"3169","vim_version":"7.0","1":"7.0","script_version":"0.4.27","2":"0.4.27","version_comment":" \u00e2\u0080\u00a2 Make \"go to definition\" compatible* with Lua 5.2:\n   http:\/\/github.com\/xolox\/vim-lua-inspect\/commit\/77f9da1","3":" \u00e2\u0080\u00a2 Make \"go to definition\" compatible* with Lua 5.2:\n   http:\/\/github.com\/xolox\/vim-lua-inspect\/commit\/77f9da1","package":"luainspect.zip","4":"luainspect.zip","src_id":"20223","5":"20223","creation_date":"1369674217","6":"1369674217"},{"0":"3169","vim_version":"7.0","1":"7.0","script_version":"0.4.26","2":"0.4.26","version_comment":" \u00e2\u0080\u00a2 Document vim-misc as external dependency (needs to be installed separately from now on):\n   http:\/\/github.com\/xolox\/vim-lua-inspect\/commit\/ebf637d","3":" \u00e2\u0080\u00a2 Document vim-misc as external dependency (needs to be installed separately from now on):\n   http:\/\/github.com\/xolox\/vim-lua-inspect\/commit\/ebf637d","package":"luainspect.zip","4":"luainspect.zip","src_id":"20215","5":"20215","creation_date":"1369518450","6":"1369518450"},{"0":"3169","vim_version":"7.0","1":"7.0","script_version":"0.4.24","2":"0.4.24","version_comment":" \u00e2\u0080\u00a2 Updated miscellaneous scripts:\n   http:\/\/github.com\/xolox\/vim-lua-inspect\/commit\/942f58a","3":" \u00e2\u0080\u00a2 Updated miscellaneous scripts:\n   http:\/\/github.com\/xolox\/vim-lua-inspect\/commit\/942f58a","package":"luainspect.zip","4":"luainspect.zip","src_id":"20179","5":"20179","creation_date":"1369054149","6":"1369054149"},{"0":"3169","vim_version":"7.0","1":"7.0","script_version":"0.4.23","2":"0.4.23","version_comment":" \u00e2\u0080\u00a2 Updated miscellaneous scripts:\n   http:\/\/github.com\/xolox\/vim-lua-inspect\/commit\/dab5a33","3":" \u00e2\u0080\u00a2 Updated miscellaneous scripts:\n   http:\/\/github.com\/xolox\/vim-lua-inspect\/commit\/dab5a33","package":"luainspect.zip","4":"luainspect.zip","src_id":"20167","5":"20167","creation_date":"1369003013","6":"1369003013"},{"0":"3169","vim_version":"7.0","1":"7.0","script_version":"0.4.22","2":"0.4.22","version_comment":" \u00e2\u0080\u00a2 Updated miscellaneous scripts:\n   http:\/\/github.com\/xolox\/vim-lua-inspect\/commit\/8e23d8e\n   http:\/\/github.com\/xolox\/vim-lua-inspect\/commit\/9c88b0e","3":" \u00e2\u0080\u00a2 Updated miscellaneous scripts:\n   http:\/\/github.com\/xolox\/vim-lua-inspect\/commit\/8e23d8e\n   http:\/\/github.com\/xolox\/vim-lua-inspect\/commit\/9c88b0e","package":"luainspect.zip","4":"luainspect.zip","src_id":"20121","5":"20121","creation_date":"1368481049","6":"1368481049"},{"0":"3169","vim_version":"7.0","1":"7.0","script_version":"0.4.21","2":"0.4.21","version_comment":" \u00e2\u0080\u00a2 Bug fix & improvements for running LuaInspect as external process:\n   http:\/\/github.com\/xolox\/vim-lua-inspect\/commit\/a95cd00","3":" \u00e2\u0080\u00a2 Bug fix & improvements for running LuaInspect as external process:\n   http:\/\/github.com\/xolox\/vim-lua-inspect\/commit\/a95cd00","package":"luainspect.zip","4":"luainspect.zip","src_id":"20099","5":"20099","creation_date":"1368356440","6":"1368356440"},{"0":"3169","vim_version":"7.0","1":"7.0","script_version":"0.4.20","2":"0.4.20","version_comment":" \u00e2\u0080\u00a2 Bug fix: Remove hidden Unicode character causing E129:\n   http:\/\/github.com\/xolox\/vim-lua-inspect\/commit\/1c183f4","3":" \u00e2\u0080\u00a2 Bug fix: Remove hidden Unicode character causing E129:\n   http:\/\/github.com\/xolox\/vim-lua-inspect\/commit\/1c183f4","package":"luainspect.zip","4":"luainspect.zip","src_id":"20097","5":"20097","creation_date":"1368353361","6":"1368353361"},{"0":"3169","vim_version":"7.0","1":"7.0","script_version":"0.4.19","2":"0.4.19","version_comment":" \u00e2\u0080\u00a2 Updated miscellaneous scripts:\n   http:\/\/github.com\/xolox\/vim-lua-inspect\/commit\/2192365","3":" \u00e2\u0080\u00a2 Updated miscellaneous scripts:\n   http:\/\/github.com\/xolox\/vim-lua-inspect\/commit\/2192365","package":"luainspect.zip","4":"luainspect.zip","src_id":"20004","5":"20004","creation_date":"1367487419","6":"1367487419"},{"0":"3169","vim_version":"7.0","1":"7.0","script_version":"0.4.18","2":"0.4.18","version_comment":" \u00e2\u0080\u00a2 Updated miscellaneous scripts:\n   http:\/\/github.com\/xolox\/vim-lua-inspect\/commit\/e0815fe","3":" \u00e2\u0080\u00a2 Updated miscellaneous scripts:\n   http:\/\/github.com\/xolox\/vim-lua-inspect\/commit\/e0815fe","package":"luainspect.zip","4":"luainspect.zip","src_id":"19964","5":"19964","creation_date":"1367160268","6":"1367160268"},{"0":"3169","vim_version":"7.0","1":"7.0","script_version":"0.4.17","2":"0.4.17","version_comment":" \u00e2\u0080\u00a2 Make compatibility with miscellaneous scripts explicit:\n   http:\/\/github.com\/xolox\/vim-lua-inspect\/commit\/c66d2b7","3":" \u00e2\u0080\u00a2 Make compatibility with miscellaneous scripts explicit:\n   http:\/\/github.com\/xolox\/vim-lua-inspect\/commit\/c66d2b7","package":"luainspect.zip","4":"luainspect.zip","src_id":"19870","5":"19870","creation_date":"1366485647","6":"1366485647"},{"0":"3169","vim_version":"7.0","1":"7.0","script_version":"0.4.16","2":"0.4.16","version_comment":" \u00e2\u0080\u00a2 xolox#misc#os#exec() uses xolox#shell#execute() when available, falls back to system():\n   http:\/\/github.com\/xolox\/vim-lua-inspect\/commit\/9b4c774\n   http:\/\/github.com\/xolox\/vim-lua-inspect\/commit\/d488dd2\n   http:\/\/github.com\/xolox\/vim-lua-inspect\/commit\/2161dc7","3":" \u00e2\u0080\u00a2 xolox#misc#os#exec() uses xolox#shell#execute() when available, falls back to system():\n   http:\/\/github.com\/xolox\/vim-lua-inspect\/commit\/9b4c774\n   http:\/\/github.com\/xolox\/vim-lua-inspect\/commit\/d488dd2\n   http:\/\/github.com\/xolox\/vim-lua-inspect\/commit\/2161dc7","package":"luainspect.zip","4":"luainspect.zip","src_id":"16958","5":"16958","creation_date":"1322174671","6":"1322174671"},{"0":"3169","vim_version":"7.0","1":"7.0","script_version":"0.4.15","2":"0.4.15","version_comment":" \u00e2\u0080\u00a2 Updated miscellaneous scripts:\n   http:\/\/github.com\/xolox\/vim-lua-inspect\/commit\/1529fff","3":" \u00e2\u0080\u00a2 Updated miscellaneous scripts:\n   http:\/\/github.com\/xolox\/vim-lua-inspect\/commit\/1529fff","package":"luainspect.zip","4":"luainspect.zip","src_id":"16925","5":"16925","creation_date":"1321910590","6":"1321910590"},{"0":"3169","vim_version":"7.0","1":"7.0","script_version":"0.4.14","2":"0.4.14","version_comment":" \u00e2\u0080\u00a2 New :LuaInspectToggle command:\n   http:\/\/github.com\/xolox\/vim-lua-inspect\/commit\/1ed6e7a","3":" \u00e2\u0080\u00a2 New :LuaInspectToggle command:\n   http:\/\/github.com\/xolox\/vim-lua-inspect\/commit\/1ed6e7a","package":"luainspect.zip","4":"luainspect.zip","src_id":"16875","5":"16875","creation_date":"1321398955","6":"1321398955"},{"0":"3169","vim_version":"7.0","1":"7.0","script_version":"0.4.13","2":"0.4.13","version_comment":" \u00e2\u0080\u00a2 Updated miscellaneous scripts:\n   http:\/\/github.com\/xolox\/vim-lua-inspect\/commit\/c8c3405","3":" \u00e2\u0080\u00a2 Updated miscellaneous scripts:\n   http:\/\/github.com\/xolox\/vim-lua-inspect\/commit\/c8c3405","package":"luainspect.zip","4":"luainspect.zip","src_id":"16579","5":"16579","creation_date":"1316994666","6":"1316994666"},{"0":"3169","vim_version":"7.0","1":"7.0","script_version":"0.4.12","2":"0.4.12","version_comment":" \u00e2\u0080\u00a2 Updated miscellaneous scripts:\n   http:\/\/github.com\/xolox\/vim-lua-inspect\/commit\/fd90005","3":" \u00e2\u0080\u00a2 Updated miscellaneous scripts:\n   http:\/\/github.com\/xolox\/vim-lua-inspect\/commit\/fd90005","package":"luainspect.zip","4":"luainspect.zip","src_id":"16457","5":"16457","creation_date":"1315144964","6":"1315144964"},{"0":"3169","vim_version":"7.0","1":"7.0","script_version":"0.4.11","2":"0.4.11","version_comment":" \u00e2\u0080\u00a2 Define version as variable, include version in messages:\n   http:\/\/github.com\/xolox\/vim-lua-inspect\/commit\/b92c629","3":" \u00e2\u0080\u00a2 Define version as variable, include version in messages:\n   http:\/\/github.com\/xolox\/vim-lua-inspect\/commit\/b92c629","package":"luainspect.zip","4":"luainspect.zip","src_id":"16379","5":"16379","creation_date":"1314498171","6":"1314498171"},{"0":"3169","vim_version":"7.0","1":"7.0","script_version":"0.4.10","2":"0.4.10","version_comment":" \u00e2\u0080\u00a2 Added example to showcase semantic highlighting:\r\n   http:\/\/github.com\/xolox\/vim-lua-inspect\/commit\/0249104\r\n\r\n \u00e2\u0080\u00a2 Make g:lua_inspect_path default compatible with Pathogen:\r\n   http:\/\/github.com\/xolox\/vim-lua-inspect\/commit\/26e6f35\r\n\r\n \u00e2\u0080\u00a2 Bug fix: Only enable tooltips when supported: (thanks Micheal for the bug report!)\r\n   http:\/\/github.com\/xolox\/vim-lua-inspect\/commit\/987eda1","3":" \u00e2\u0080\u00a2 Added example to showcase semantic highlighting:\r\n   http:\/\/github.com\/xolox\/vim-lua-inspect\/commit\/0249104\r\n\r\n \u00e2\u0080\u00a2 Make g:lua_inspect_path default compatible with Pathogen:\r\n   http:\/\/github.com\/xolox\/vim-lua-inspect\/commit\/26e6f35\r\n\r\n \u00e2\u0080\u00a2 Bug fix: Only enable tooltips when supported: (thanks Micheal for the bug report!)\r\n   http:\/\/github.com\/xolox\/vim-lua-inspect\/commit\/987eda1","package":"luainspect.zip","4":"luainspect.zip","src_id":"15725","5":"15725","creation_date":"1306358959","6":"1306358959"},{"0":"3169","vim_version":"7.0","1":"7.0","script_version":"0.4.7","2":"0.4.7","version_comment":" \u00e2\u0080\u00a2 Improve syntax error messages for unnamed buffers:\r\n   http:\/\/github.com\/xolox\/vim-lua-inspect\/commit\/3cbe412883edda9ce4cc\r\n\r\n \u00e2\u0080\u00a2 Make parse_text() more robust against missing buffer variables:\r\n   http:\/\/github.com\/xolox\/vim-lua-inspect\/commit\/bc013227961f7dc24818\r\n\r\n \u00e2\u0080\u00a2 Bug fix: Focus doesn't return to original window:\r\n   http:\/\/github.com\/xolox\/vim-lua-inspect\/commit\/806dcb21f9f7be1de715","3":" \u00e2\u0080\u00a2 Improve syntax error messages for unnamed buffers:\r\n   http:\/\/github.com\/xolox\/vim-lua-inspect\/commit\/3cbe412883edda9ce4cc\r\n\r\n \u00e2\u0080\u00a2 Make parse_text() more robust against missing buffer variables:\r\n   http:\/\/github.com\/xolox\/vim-lua-inspect\/commit\/bc013227961f7dc24818\r\n\r\n \u00e2\u0080\u00a2 Bug fix: Focus doesn't return to original window:\r\n   http:\/\/github.com\/xolox\/vim-lua-inspect\/commit\/806dcb21f9f7be1de715","package":"luainspect.zip","4":"luainspect.zip","src_id":"14034","5":"14034","creation_date":"1286636925","6":"1286636925"},{"0":"3169","vim_version":"7.0","1":"7.0","script_version":"0.4.5","2":"0.4.5","version_comment":" \u00e2\u0080\u00a2 Always clear previously overlayed highlighting:\r\n   http:\/\/github.com\/xolox\/vim-lua-inspect\/commit\/62942b011979937fba84ea4795f7a5c593323f31\r\n\r\n \u00e2\u0080\u00a2 Bug fix for `E776: No location list':\r\n   http:\/\/github.com\/xolox\/vim-lua-inspect\/commit\/47b25952b638bb02f69c7fb479cbb2d57c806a94\r\n\r\n \u00e2\u0080\u00a2 Make argument count warnings highlight only function names:\r\n   http:\/\/github.com\/xolox\/vim-lua-inspect\/commit\/22b75bcf657d4f55e48cce3801613ee3e3086af1\r\n\r\nLots of miscellaneous changes (see http:\/\/github.com\/xolox\/vim-lua-inspect\/commits\/) to make the plug-in compatible with the newest release of LuaInspect, which itself includes bug fixes that fix bugs in this plug-in (e.g. when you add some empty lines to the start of a Lua buffer the highlighting would break, this turned out to be a bug in the Metalua lexer).","3":" \u00e2\u0080\u00a2 Always clear previously overlayed highlighting:\r\n   http:\/\/github.com\/xolox\/vim-lua-inspect\/commit\/62942b011979937fba84ea4795f7a5c593323f31\r\n\r\n \u00e2\u0080\u00a2 Bug fix for `E776: No location list':\r\n   http:\/\/github.com\/xolox\/vim-lua-inspect\/commit\/47b25952b638bb02f69c7fb479cbb2d57c806a94\r\n\r\n \u00e2\u0080\u00a2 Make argument count warnings highlight only function names:\r\n   http:\/\/github.com\/xolox\/vim-lua-inspect\/commit\/22b75bcf657d4f55e48cce3801613ee3e3086af1\r\n\r\nLots of miscellaneous changes (see http:\/\/github.com\/xolox\/vim-lua-inspect\/commits\/) to make the plug-in compatible with the newest release of LuaInspect, which itself includes bug fixes that fix bugs in this plug-in (e.g. when you add some empty lines to the start of a Lua buffer the highlighting would break, this turned out to be a bug in the Metalua lexer).","package":"luainspect.zip","4":"luainspect.zip","src_id":"13627","5":"13627","creation_date":"1282220853","6":"1282220853"},{"0":"3169","vim_version":"7.0","1":"7.0","script_version":"0.4.3","2":"0.4.3","version_comment":" \u00e2\u0080\u00a2 Bug fix: Strip newlines from warnings:\r\n   http:\/\/github.com\/xolox\/vim-lua-inspect\/commit\/59ba90c6c496dfe929cb83b896fe4e594d06354a\r\n\r\n \u00e2\u0080\u00a2 Ignore LuaInspect status messages on stderr (only applies when not using if-lua):\r\n   http:\/\/github.com\/xolox\/vim-lua-inspect\/commit\/fd3920c5fd7faba9881a2b89525b5caa7753baa8\r\n\r\n \u00e2\u0080\u00a2 Enable renaming variables that only differ in case:\r\n   http:\/\/github.com\/xolox\/vim-lua-inspect\/commit\/14b1ff64e29b6333d492a9fc8dfddb0427ee449e","3":" \u00e2\u0080\u00a2 Bug fix: Strip newlines from warnings:\r\n   http:\/\/github.com\/xolox\/vim-lua-inspect\/commit\/59ba90c6c496dfe929cb83b896fe4e594d06354a\r\n\r\n \u00e2\u0080\u00a2 Ignore LuaInspect status messages on stderr (only applies when not using if-lua):\r\n   http:\/\/github.com\/xolox\/vim-lua-inspect\/commit\/fd3920c5fd7faba9881a2b89525b5caa7753baa8\r\n\r\n \u00e2\u0080\u00a2 Enable renaming variables that only differ in case:\r\n   http:\/\/github.com\/xolox\/vim-lua-inspect\/commit\/14b1ff64e29b6333d492a9fc8dfddb0427ee449e","package":"luainspect.zip","4":"luainspect.zip","src_id":"13590","5":"13590","creation_date":"1281980448","6":"1281980448"},{"0":"3169","vim_version":"7.0","1":"7.0","script_version":"0.4","2":"0.4","version_comment":"Some new features and lots of bug fixes:\r\n\r\n \u00e2\u0080\u00a2 Support dark colorschemes following scite.lua:\r\n   http:\/\/github.com\/xolox\/vim-lua-inspect\/commit\/c6a8ecf5067329540d70a313336d28cd33dbf4f9\r\n\r\n \u00e2\u0080\u00a2 Bug fix: Show error highlighting only in Lua buffers:\r\n   http:\/\/github.com\/xolox\/vim-lua-inspect\/commit\/2d671c489bdf42dfe68b289588c09e0a18c7ce0b\r\n\r\n \u00e2\u0080\u00a2 Bug fix: Overlay argument count highlighting:\r\n   http:\/\/github.com\/xolox\/vim-lua-inspect\/commit\/7f9cbd60cbbc949ddb5c809eac2ba3a88dad44a6\r\n\r\n \u00e2\u0080\u00a2 Split plug-in into command definitions \/ autoload functions:\r\n   http:\/\/github.com\/xolox\/vim-lua-inspect\/commit\/527e1b76a06c04baf2b9b597f1fbd5e0ef02fca4\r\n\r\n \u00e2\u0080\u00a2 if-lua now includes io.*; remove workaround\r\n   http:\/\/github.com\/xolox\/vim-lua-inspect\/commit\/5f3bdbafcc5258487e94cf55dae9cde5374d97d1\r\n\r\n \u00e2\u0080\u00a2 Time plug-in execution for all actions:\r\n   http:\/\/github.com\/xolox\/vim-lua-inspect\/commit\/2a33bcb6876ef1bd0705ea8738ee0e5c735fff42 \r\n\r\n \u00e2\u0080\u00a2 Use real buffer names instead of \u00e2\u0080\u0098noname.lua\u00e2\u0080\u0099:\r\n   http:\/\/github.com\/xolox\/vim-lua-inspect\/commit\/2e93bdd4f3de8a39fc22a6f2d29021a5873d057b\r\n\r\n \u00e2\u0080\u00a2 Improved highlighting for argument count warnings:\r\n   http:\/\/github.com\/xolox\/vim-lua-inspect\/commit\/17bb37cefb7e562cacc0d076c6189aaf92026aca\r\n\r\n \u00e2\u0080\u00a2 Use LuaInspect's get_value_details() function:\r\n   http:\/\/github.com\/xolox\/vim-lua-inspect\/commit\/cca74e2556c351e91e150bcf33b69f537b4a2644\r\n\r\n \u00e2\u0080\u00a2 Show warnings by LuaInspect in location list:\r\n   http:\/\/github.com\/xolox\/vim-lua-inspect\/commit\/f0eeca23130a1bbff1293e7203dcde8f7340d06a\r\n\r\n \u00e2\u0080\u00a2 The packages for version 0.3.3 and 0.3.6 below should have been self contained but I failed to include the LuaInspect sources. This has been fixed now. Sorry about that!","3":"Some new features and lots of bug fixes:\r\n\r\n \u00e2\u0080\u00a2 Support dark colorschemes following scite.lua:\r\n   http:\/\/github.com\/xolox\/vim-lua-inspect\/commit\/c6a8ecf5067329540d70a313336d28cd33dbf4f9\r\n\r\n \u00e2\u0080\u00a2 Bug fix: Show error highlighting only in Lua buffers:\r\n   http:\/\/github.com\/xolox\/vim-lua-inspect\/commit\/2d671c489bdf42dfe68b289588c09e0a18c7ce0b\r\n\r\n \u00e2\u0080\u00a2 Bug fix: Overlay argument count highlighting:\r\n   http:\/\/github.com\/xolox\/vim-lua-inspect\/commit\/7f9cbd60cbbc949ddb5c809eac2ba3a88dad44a6\r\n\r\n \u00e2\u0080\u00a2 Split plug-in into command definitions \/ autoload functions:\r\n   http:\/\/github.com\/xolox\/vim-lua-inspect\/commit\/527e1b76a06c04baf2b9b597f1fbd5e0ef02fca4\r\n\r\n \u00e2\u0080\u00a2 if-lua now includes io.*; remove workaround\r\n   http:\/\/github.com\/xolox\/vim-lua-inspect\/commit\/5f3bdbafcc5258487e94cf55dae9cde5374d97d1\r\n\r\n \u00e2\u0080\u00a2 Time plug-in execution for all actions:\r\n   http:\/\/github.com\/xolox\/vim-lua-inspect\/commit\/2a33bcb6876ef1bd0705ea8738ee0e5c735fff42 \r\n\r\n \u00e2\u0080\u00a2 Use real buffer names instead of \u00e2\u0080\u0098noname.lua\u00e2\u0080\u0099:\r\n   http:\/\/github.com\/xolox\/vim-lua-inspect\/commit\/2e93bdd4f3de8a39fc22a6f2d29021a5873d057b\r\n\r\n \u00e2\u0080\u00a2 Improved highlighting for argument count warnings:\r\n   http:\/\/github.com\/xolox\/vim-lua-inspect\/commit\/17bb37cefb7e562cacc0d076c6189aaf92026aca\r\n\r\n \u00e2\u0080\u00a2 Use LuaInspect's get_value_details() function:\r\n   http:\/\/github.com\/xolox\/vim-lua-inspect\/commit\/cca74e2556c351e91e150bcf33b69f537b4a2644\r\n\r\n \u00e2\u0080\u00a2 Show warnings by LuaInspect in location list:\r\n   http:\/\/github.com\/xolox\/vim-lua-inspect\/commit\/f0eeca23130a1bbff1293e7203dcde8f7340d06a\r\n\r\n \u00e2\u0080\u00a2 The packages for version 0.3.3 and 0.3.6 below should have been self contained but I failed to include the LuaInspect sources. This has been fixed now. Sorry about that!","package":"luainspect.zip","4":"luainspect.zip","src_id":"13581","5":"13581","creation_date":"1281901587","6":"1281901587"},{"0":"3169","vim_version":"7.0","1":"7.0","script_version":"0.3.6","2":"0.3.6","version_comment":" \u00e2\u0080\u00a2 Warn user + show tooltips for syntax errors:\r\n   http:\/\/github.com\/xolox\/vim-lua-inspect\/commit\/b0b58008127bcecae658922707370f0df915847c\r\n\r\n \u00e2\u0080\u00a2 Better highlighting of selected variables:\r\n   http:\/\/github.com\/xolox\/vim-lua-inspect\/commit\/026fdd42bca366b95a271c3b8c9fa78cbc17c0f9\r\n\r\n \u00e2\u0080\u00a2 Highlight wrong function argument count:\r\n   http:\/\/github.com\/xolox\/vim-lua-inspect\/commit\/72a058e773a97781eaa731567faf1f2268576563","3":" \u00e2\u0080\u00a2 Warn user + show tooltips for syntax errors:\r\n   http:\/\/github.com\/xolox\/vim-lua-inspect\/commit\/b0b58008127bcecae658922707370f0df915847c\r\n\r\n \u00e2\u0080\u00a2 Better highlighting of selected variables:\r\n   http:\/\/github.com\/xolox\/vim-lua-inspect\/commit\/026fdd42bca366b95a271c3b8c9fa78cbc17c0f9\r\n\r\n \u00e2\u0080\u00a2 Highlight wrong function argument count:\r\n   http:\/\/github.com\/xolox\/vim-lua-inspect\/commit\/72a058e773a97781eaa731567faf1f2268576563","package":"luainspect.zip","4":"luainspect.zip","src_id":"13555","5":"13555","creation_date":"1281577401","6":"1281577401"},{"0":"3169","vim_version":"7.0","1":"7.0","script_version":"0.3.3","2":"0.3.3","version_comment":" \u00e2\u0080\u00a2 <F2> mapping to rename all occurrences of variable:\r\n   http:\/\/github.com\/xolox\/vim-lua-inspect\/commit\/0c52221a952874807e50d668b0c89511378bdb10\r\n\r\n \u00e2\u0080\u00a2 'gd' mapping to jump to variable declaration:\r\n   http:\/\/github.com\/xolox\/vim-lua-inspect\/commit\/bb99531941ca10ffd9b77a2a9dcd83a354a022cf\r\n\r\n \u00e2\u0080\u00a2 Tooltips to show variable details like state\/type\/signature\/value:\r\n   http:\/\/github.com\/xolox\/vim-lua-inspect\/commit\/dc640de6799ba3da5f70073828da91ffaf0b596a","3":" \u00e2\u0080\u00a2 <F2> mapping to rename all occurrences of variable:\r\n   http:\/\/github.com\/xolox\/vim-lua-inspect\/commit\/0c52221a952874807e50d668b0c89511378bdb10\r\n\r\n \u00e2\u0080\u00a2 'gd' mapping to jump to variable declaration:\r\n   http:\/\/github.com\/xolox\/vim-lua-inspect\/commit\/bb99531941ca10ffd9b77a2a9dcd83a354a022cf\r\n\r\n \u00e2\u0080\u00a2 Tooltips to show variable details like state\/type\/signature\/value:\r\n   http:\/\/github.com\/xolox\/vim-lua-inspect\/commit\/dc640de6799ba3da5f70073828da91ffaf0b596a","package":"luainspect.zip","4":"luainspect.zip","src_id":"13549","5":"13549","creation_date":"1281551672","6":"1281551672"},{"0":"3169","vim_version":"7.0","1":"7.0","script_version":"0.2.4","2":"0.2.4","version_comment":" \u00e2\u0080\u00a2 Highlight syntax errors as spelling errors:\r\n   http:\/\/github.com\/xolox\/vim-lua-inspect\/commit\/f5b367d8dd7d9d6da1fb359ab19b0e44c49161f7\r\n\r\n \u00e2\u0080\u00a2 Support automatic updates using GLVS plug-in:\r\n   http:\/\/github.com\/xolox\/vim-lua-inspect\/commit\/4c2c0bfd45e86dbfdbedf66c20425a3b4e9426a6","3":" \u00e2\u0080\u00a2 Highlight syntax errors as spelling errors:\r\n   http:\/\/github.com\/xolox\/vim-lua-inspect\/commit\/f5b367d8dd7d9d6da1fb359ab19b0e44c49161f7\r\n\r\n \u00e2\u0080\u00a2 Support automatic updates using GLVS plug-in:\r\n   http:\/\/github.com\/xolox\/vim-lua-inspect\/commit\/4c2c0bfd45e86dbfdbedf66c20425a3b4e9426a6","package":"luainspect.zip","4":"luainspect.zip","src_id":"13536","5":"13536","creation_date":"1281415028","6":"1281415028"},{"0":"3169","vim_version":"7.0","1":"7.0","script_version":"0.2.2","2":"0.2.2","version_comment":" \u00e2\u0080\u00a2 Now works on Windows and disables easytags.vim:\r\n   http:\/\/github.com\/xolox\/vim-lua-inspect\/commit\/ce2b578242ccf3d4eef658accc7e4711f34fbbbc\r\n\r\n \u00e2\u0080\u00a2 Converted the plug-in to a self contained package: Unzip and you're off!\r\n   http:\/\/github.com\/xolox\/vim-lua-inspect\/commit\/43307cbb3a99b3a6075640151626f50846ced474\r\n\r\n \u00e2\u0080\u00a2 Don't show command prompts on Windows (integration with my shell.vim plug-in):\r\n   http:\/\/github.com\/xolox\/vim-lua-inspect\/commit\/2689c2d1896d47c6aa3fa2d919d06d353cf0c17f","3":" \u00e2\u0080\u00a2 Now works on Windows and disables easytags.vim:\r\n   http:\/\/github.com\/xolox\/vim-lua-inspect\/commit\/ce2b578242ccf3d4eef658accc7e4711f34fbbbc\r\n\r\n \u00e2\u0080\u00a2 Converted the plug-in to a self contained package: Unzip and you're off!\r\n   http:\/\/github.com\/xolox\/vim-lua-inspect\/commit\/43307cbb3a99b3a6075640151626f50846ced474\r\n\r\n \u00e2\u0080\u00a2 Don't show command prompts on Windows (integration with my shell.vim plug-in):\r\n   http:\/\/github.com\/xolox\/vim-lua-inspect\/commit\/2689c2d1896d47c6aa3fa2d919d06d353cf0c17f","package":"luainspect.zip","4":"luainspect.zip","src_id":"13533","5":"13533","creation_date":"1281411291","6":"1281411291"},{"0":"3169","vim_version":"7.0","1":"7.0","script_version":"0.2.1","2":"0.2.1","version_comment":" \u00e2\u0080\u00a2 Highlight occurrences of variable under text cursor:\r\n   http:\/\/github.com\/xolox\/vim-lua-inspect\/commit\/6a0430cff4f4806a89732037437562ef3c36d0a0\r\n\r\n \u00e2\u0080\u00a2 Don't parse the text when it hasn't been changed:\r\n   http:\/\/github.com\/xolox\/vim-lua-inspect\/commit\/a9205704796749a0556ce6e7a7959654b3983caa\r\n\r\n \u00e2\u0080\u00a2 Use new LuaInspect API (without incremental parsing for now):\r\n   http:\/\/github.com\/xolox\/vim-lua-inspect\/commit\/a14b977c69b6682054e80b9bcceb1c0f797fcd21\r\n\r\n \u00e2\u0080\u00a2 Use if-lua by default (because of if-lua-corelibs.diff):\r\n   http:\/\/github.com\/xolox\/vim-lua-inspect\/commit\/7bec1f49c6f12bbdde1f6d5a3470a9f66a8e34e2\r\n\r\n \u00e2\u0080\u00a2 Support disabling plug-in for specific buffers:\r\n   http:\/\/github.com\/xolox\/vim-lua-inspect\/commit\/3e5967143918c6bc383fae0442f10210c81be0f8","3":" \u00e2\u0080\u00a2 Highlight occurrences of variable under text cursor:\r\n   http:\/\/github.com\/xolox\/vim-lua-inspect\/commit\/6a0430cff4f4806a89732037437562ef3c36d0a0\r\n\r\n \u00e2\u0080\u00a2 Don't parse the text when it hasn't been changed:\r\n   http:\/\/github.com\/xolox\/vim-lua-inspect\/commit\/a9205704796749a0556ce6e7a7959654b3983caa\r\n\r\n \u00e2\u0080\u00a2 Use new LuaInspect API (without incremental parsing for now):\r\n   http:\/\/github.com\/xolox\/vim-lua-inspect\/commit\/a14b977c69b6682054e80b9bcceb1c0f797fcd21\r\n\r\n \u00e2\u0080\u00a2 Use if-lua by default (because of if-lua-corelibs.diff):\r\n   http:\/\/github.com\/xolox\/vim-lua-inspect\/commit\/7bec1f49c6f12bbdde1f6d5a3470a9f66a8e34e2\r\n\r\n \u00e2\u0080\u00a2 Support disabling plug-in for specific buffers:\r\n   http:\/\/github.com\/xolox\/vim-lua-inspect\/commit\/3e5967143918c6bc383fae0442f10210c81be0f8","package":"luainspect.zip","4":"luainspect.zip","src_id":"13519","5":"13519","creation_date":"1281224924","6":"1281224924"},{"0":"3169","vim_version":"7.0","1":"7.0","script_version":"0.1.4","2":"0.1.4","version_comment":" \u00e2\u0080\u00a2 Don't perform semantic highlighting in 'diff' mode:\r\n   http:\/\/github.com\/xolox\/vim-lua-inspect\/commit\/47a223e11b469d871f8968c7f5bb7543d0f54e2c\r\n\r\n \u00e2\u0080\u00a2 Add word boundaries to Vim search patterns:\r\n   http:\/\/github.com\/xolox\/vim-lua-inspect\/commit\/59637bd8e2843b51780866f10899f759aa07c416\r\n\r\n \u00e2\u0080\u00a2 (Performance) improvements suggested by Luis Carvalho:\r\n   http:\/\/github.com\/xolox\/vim-lua-inspect\/commit\/7de26617d1f659a3e173f8be5ed0305fee6a83a9\r\n\r\n \u00e2\u0080\u00a2 `ErrorMsg' has better highlighting between colorschemes than `Error':\r\n   http:\/\/github.com\/xolox\/vim-lua-inspect\/commit\/63dc4bb0f8094b45c7abe416d1ccbc28426d54cc\r\n\r\n \u00e2\u0080\u00a2 Simplified wrapper as suggested by David Manura:\r\n   http:\/\/github.com\/xolox\/vim-lua-inspect\/commit\/ed34601710a09222ef3351082c40cc249eae9821","3":" \u00e2\u0080\u00a2 Don't perform semantic highlighting in 'diff' mode:\r\n   http:\/\/github.com\/xolox\/vim-lua-inspect\/commit\/47a223e11b469d871f8968c7f5bb7543d0f54e2c\r\n\r\n \u00e2\u0080\u00a2 Add word boundaries to Vim search patterns:\r\n   http:\/\/github.com\/xolox\/vim-lua-inspect\/commit\/59637bd8e2843b51780866f10899f759aa07c416\r\n\r\n \u00e2\u0080\u00a2 (Performance) improvements suggested by Luis Carvalho:\r\n   http:\/\/github.com\/xolox\/vim-lua-inspect\/commit\/7de26617d1f659a3e173f8be5ed0305fee6a83a9\r\n\r\n \u00e2\u0080\u00a2 `ErrorMsg' has better highlighting between colorschemes than `Error':\r\n   http:\/\/github.com\/xolox\/vim-lua-inspect\/commit\/63dc4bb0f8094b45c7abe416d1ccbc28426d54cc\r\n\r\n \u00e2\u0080\u00a2 Simplified wrapper as suggested by David Manura:\r\n   http:\/\/github.com\/xolox\/vim-lua-inspect\/commit\/ed34601710a09222ef3351082c40cc249eae9821","package":"luainspect.zip","4":"luainspect.zip","src_id":"13417","5":"13417","creation_date":"1280287322","6":"1280287322"},{"0":"3169","vim_version":"7.0","1":"7.0","script_version":"0.1.3","2":"0.1.3","version_comment":" \u00e2\u0080\u00a2 Enable users to define styles which the plug-in won't override:\r\n   http:\/\/github.com\/xolox\/vim-lua-inspect\/commit\/67777a75f4b9f4896d5818b57611d34c82a0187c\r\n\r\n \u00e2\u0080\u00a2 Enable highlighting on user defined events:\r\n   http:\/\/github.com\/xolox\/vim-lua-inspect\/commit\/d07a1ff10cbd78d5e16c28d234b5e37bc0de88ad","3":" \u00e2\u0080\u00a2 Enable users to define styles which the plug-in won't override:\r\n   http:\/\/github.com\/xolox\/vim-lua-inspect\/commit\/67777a75f4b9f4896d5818b57611d34c82a0187c\r\n\r\n \u00e2\u0080\u00a2 Enable highlighting on user defined events:\r\n   http:\/\/github.com\/xolox\/vim-lua-inspect\/commit\/d07a1ff10cbd78d5e16c28d234b5e37bc0de88ad","package":"luainspect.zip","4":"luainspect.zip","src_id":"13415","5":"13415","creation_date":"1280253480","6":"1280253480"},{"0":"3169","vim_version":"7.0","1":"7.0","script_version":"0.1.2","2":"0.1.2","version_comment":"README improvements, miscellaneous other changes: http:\/\/github.com\/xolox\/vim-lua-inspect\/commit\/ec4e1c31facda80b316a5062fe71a4fe40e07f84","3":"README improvements, miscellaneous other changes: http:\/\/github.com\/xolox\/vim-lua-inspect\/commit\/ec4e1c31facda80b316a5062fe71a4fe40e07f84","package":"luainspect.zip","4":"luainspect.zip","src_id":"13414","5":"13414","creation_date":"1280246198","6":"1280246198"},{"0":"3169","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"luainspect.zip","4":"luainspect.zip","src_id":"13413","5":"13413","creation_date":"1280243334","6":"1280243334"}]},"3168":{"script_id":"3168","0":"3168","script_name":"mojo.vim","1":"mojo.vim","script_type":"syntax","2":"syntax","summary":"Mojolicious templates syntax","3":"Mojolicious templates syntax","description":"Syntax file for Mojolicious (http:\/\/mojolicio.us) epl templates.\r\nDesigned to highlight syntax of both html.ep and html.epl formats and (optional) __DATA__ section of Perl files.\r\n\r\nmojo.vim lives at http:\/\/github.com\/yko\/mojo.vim","4":"Syntax file for Mojolicious (http:\/\/mojolicio.us) epl templates.\r\nDesigned to highlight syntax of both html.ep and html.epl formats and (optional) __DATA__ section of Perl files.\r\n\r\nmojo.vim lives at http:\/\/github.com\/yko\/mojo.vim","install_details":"run make install\r\nor use VimBall (.vba) package","5":"run make install\r\nor use VimBall (.vba) package","first_name":"Yaroslav","6":"Yaroslav","last_name":"Korshak","7":"Korshak","releases":[{"0":"3168","vim_version":"7.0","1":"7.0","script_version":"0.04","2":"0.04","version_comment":"VimBall of 0.04, see below","3":"VimBall of 0.04, see below","package":"mojo-0_04.vba","4":"mojo-0_04.vba","src_id":"16220","5":"16220","creation_date":"1312915437","6":"1312915437"},{"0":"3168","vim_version":"7.0","1":"7.0","script_version":"0.04","2":"0.04","version_comment":"Highlight default Mojolicious tag helpers\r\nHighlight css and js code inside of appropriate tag helpers\r\nSnipmate support for .epl files (http:\/\/www.vim.org\/scripts\/script.php?script_id=2540)\r\nSome minor bugfixes and tests improvements","3":"Highlight default Mojolicious tag helpers\r\nHighlight css and js code inside of appropriate tag helpers\r\nSnipmate support for .epl files (http:\/\/www.vim.org\/scripts\/script.php?script_id=2540)\r\nSome minor bugfixes and tests improvements","package":"mojo-0_04.tar.gz","4":"mojo-0_04.tar.gz","src_id":"16219","5":"16219","creation_date":"1312915379","6":"1312915379"},{"0":"3168","vim_version":"7.0","1":"7.0","script_version":"0.03","2":"0.03","version_comment":"VimBall of 0.03, see below","3":"VimBall of 0.03, see below","package":"mojo.vba","4":"mojo.vba","src_id":"14624","5":"14624","creation_date":"1293371325","6":"1293371325"},{"0":"3168","vim_version":"7.0","1":"7.0","script_version":"0.03","2":"0.03","version_comment":"New improved Mojolicious epl syntax\r\nMuch more organic structure\r\nTests!","3":"New improved Mojolicious epl syntax\r\nMuch more organic structure\r\nTests!","package":"mojo.tar.gz","4":"mojo.tar.gz","src_id":"14623","5":"14623","creation_date":"1293370696","6":"1293370696"},{"0":"3168","vim_version":"6.0","1":"6.0","script_version":"0.0.4","2":"0.0.4","version_comment":"Fix 'perl_fold' and few another minor fixes","3":"Fix 'perl_fold' and few another minor fixes","package":"mojo.tar.gz","4":"mojo.tar.gz","src_id":"13556","5":"13556","creation_date":"1281618136","6":"1281618136"},{"0":"3168","vim_version":"6.0","1":"6.0","script_version":"0.0.3","2":"0.0.3","version_comment":"Initial upload","3":"Initial upload","package":"mojo.tar.gz","4":"mojo.tar.gz","src_id":"13411","5":"13411","creation_date":"1280231590","6":"1280231590"}]},"3167":{"script_id":"3167","0":"3167","script_name":"regbuf.vim","1":"regbuf.vim","script_type":"utility","2":"utility","summary":"Handy :registers buffer","3":"Handy :registers buffer","description":"|regbuf| is handy |:reg| buffer.\r\n\r\n1. Yank\/Paste register\r\n2. Edit register on buffer\r\n3. etc.","4":"|regbuf| is handy |:reg| buffer.\r\n\r\n1. Yank\/Paste register\r\n2. Edit register on buffer\r\n3. etc.","install_details":"Initial upload","5":"Initial upload","first_name":"tyru","6":"tyru","last_name":" ","7":" ","releases":[{"0":"3167","vim_version":"7.0","1":"7.0","script_version":"0.0.1","2":"0.0.1","version_comment":"- Apply guns patch. Thanks guns.\r\n  - Set default register to \"+ or \"* if &clipboard has unnamedplus or unnamed","3":"- Apply guns patch. Thanks guns.\r\n  - Set default register to \"+ or \"* if &clipboard has unnamedplus or unnamed","package":"regbuf.zip","4":"regbuf.zip","src_id":"15629","5":"15629","creation_date":"1305226943","6":"1305226943"},{"0":"3167","vim_version":"7.0","1":"7.0","script_version":"0.0.0","2":"0.0.0","version_comment":"Initial upload","3":"Initial upload","package":"regbuf.zip","4":"regbuf.zip","src_id":"13410","5":"13410","creation_date":"1280206339","6":"1280206339"}]},"3166":{"script_id":"3166","0":"3166","script_name":"toggle_mouse","1":"toggle_mouse","script_type":"utility","2":"utility","summary":"Toggles the mouse focus on or off.","3":"Toggles the mouse focus on or off.","description":"Toggles the mouse focus between Vim and your terminal emulator, allowing terminal emulator mouse commands, like copy\/paste.","4":"Toggles the mouse focus between Vim and your terminal emulator, allowing terminal emulator mouse commands, like copy\/paste.","install_details":"Copy the file plugin\/toggle_mouse.vim to your ~\/.vim\/plugin directory.","5":"Copy the file plugin\/toggle_mouse.vim to your ~\/.vim\/plugin directory.","first_name":"Vincent","6":"Vincent","last_name":"Driessen","7":"Driessen","releases":[{"0":"3166","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"toggle_mouse.vim","4":"toggle_mouse.vim","src_id":"13406","5":"13406","creation_date":"1280147058","6":"1280147058"}]},"3165":{"script_id":"3165","0":"3165","script_name":"obviously-insert","1":"obviously-insert","script_type":"utility","2":"utility","summary":"Makes it REALLY obvious if you are in insert mode.","3":"Makes it REALLY obvious if you are in insert mode.","description":"This script will change the colour of both the status bar and background when you enter and exit insert mode so no more typing : in the middle of your code.\r\n\r\nYou can choose the colours to use right at the top of the script.\r\n\r\nCredits: Many people on irc:\/\/irc.freenode.org in #vim.\r\n\r\nSpecial Credits:\r\ngodlygeek - Answered so many of my questions I lost count.\r\nDave Kirby - Pointing out version 0.5 was broken with gvim in GUI mode and why.\r\n\r\nI deleted the previous versions because they are broken in some (benign) way so you shouldn't use them.","4":"This script will change the colour of both the status bar and background when you enter and exit insert mode so no more typing : in the middle of your code.\r\n\r\nYou can choose the colours to use right at the top of the script.\r\n\r\nCredits: Many people on irc:\/\/irc.freenode.org in #vim.\r\n\r\nSpecial Credits:\r\ngodlygeek - Answered so many of my questions I lost count.\r\nDave Kirby - Pointing out version 0.5 was broken with gvim in GUI mode and why.\r\n\r\nI deleted the previous versions because they are broken in some (benign) way so you shouldn't use them.","install_details":"Put it in your plugins dir.","5":"Put it in your plugins dir.","first_name":"Rob","6":"Rob","last_name":"Fortune","7":"Fortune","releases":[{"0":"3165","vim_version":"7.0","1":"7.0","script_version":"0.7","2":"0.7","version_comment":"Works with normal vim as well as gvim now.","3":"Works with normal vim as well as gvim now.","package":"obviously-insert.vim","4":"obviously-insert.vim","src_id":"13449","5":"13449","creation_date":"1280618399","6":"1280618399"}]},"3164":{"script_id":"3164","0":"3164","script_name":"pythondo","1":"pythondo","script_type":"utility","2":"utility","summary":"Add ","3":"Add ","description":"This plugin adds a command \":Pythondo\", which is rather like \":perldo\" or\" \":rubydo\".\r\n\r\n  :[range]Pythondo {cmd}\r\n  :[range]Pyd {cmd}\r\n          Execute Python command {cmd} for each line in the\r\n           [range], with variable \"s\" being set to the text of each line in\r\n           turn, and variable \"n\" being the corresponding line number.  \r\n           Setting variable \"s\" will change the text, but note that it \r\n           is not possible to add or delete lines using this command.\r\n           The default for [range] is the whole file: \"1,$\".\r\n           Setting variable \"n\" will set the text to line of number n, not\r\n           the current line. It's better not to set variable \"n\".\r\n  \r\n\r\nHere are some things you can try: >\r\n  :Pythondo s = str(n+1) + ' ' + s  # Add line number to each line\r\n  :py import time\r\n  :.Pythondo s = time.ctime()\r\n","4":"This plugin adds a command \":Pythondo\", which is rather like \":perldo\" or\" \":rubydo\".\r\n\r\n  :[range]Pythondo {cmd}\r\n  :[range]Pyd {cmd}\r\n          Execute Python command {cmd} for each line in the\r\n           [range], with variable \"s\" being set to the text of each line in\r\n           turn, and variable \"n\" being the corresponding line number.  \r\n           Setting variable \"s\" will change the text, but note that it \r\n           is not possible to add or delete lines using this command.\r\n           The default for [range] is the whole file: \"1,$\".\r\n           Setting variable \"n\" will set the text to line of number n, not\r\n           the current line. It's better not to set variable \"n\".\r\n  \r\n\r\nHere are some things you can try: >\r\n  :Pythondo s = str(n+1) + ' ' + s  # Add line number to each line\r\n  :py import time\r\n  :.Pythondo s = time.ctime()\r\n","install_details":"Copy the file pythondo.vim to plugin folder,\r\nand place pythondo.txt in doc folder.\r\n","5":"Copy the file pythondo.vim to plugin folder,\r\nand place pythondo.txt in doc folder.\r\n","first_name":"lubin","6":"lubin","last_name":"yin","7":"yin","releases":[{"0":"3164","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Add help file.","3":"Add help file.","package":"pythondo.zip","4":"pythondo.zip","src_id":"13412","5":"13412","creation_date":"1280239933","6":"1280239933"},{"0":"3164","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"pythondo.vim","4":"pythondo.vim","src_id":"13389","5":"13389","creation_date":"1279865564","6":"1279865564"}]},"3163":{"script_id":"3163","0":"3163","script_name":"endline","1":"endline","script_type":"utility","2":"utility","summary":"Easily add filetype-specific line-endings.","3":"Easily add filetype-specific line-endings.","description":"This plugin maps (by default) <S-CR> to add a filetype's provided \"line ending\"\r\nto the end of the current line if it is not already present. For instance, a ';'\r\nwould be added to the end of a line of JavaScript source.\r\n\r\nThis is similar to a feature provided by TextMate, mapped to\r\nCommand-Option-Return in that application.\r\n\r\nUsage:\r\n\r\nSomewhere in your .vimrc (or equivalent), provide a global dict mapping filetype\r\nnames to line endings, like so:\r\n\r\nlet g:Endlines = {\r\n  \\'erlang': '.',\r\n  \\'java': ';',\r\n  \\'javascript': ';',\r\n  \\'ocaml': ';;',\r\n  \\'perl': ';',\r\n  \\'php': ';',\r\n  \\'python': ':',\r\n  \\'sml': ';'\r\n\\}\r\n\r\nMappings can also be a list of patterns that will be tried in order. In the\r\nfollowing example, a \" ->\" is appended if the line starts with no whitespace\r\nand ends with a \")\", and a \",\" is appended if the line ends with\r\nnon-whitespace.\r\n\r\nlet g:Endlines = {\r\n      \\'erlang':     [\r\n        \\['^\\S.*)$', ' ->'],\r\n        \\['\\S$', ',']]\r\n      \\}\r\n\r\nBy default, <S-CR> is mapped in both insert and normal mode. In insert mode, a\r\nnew line is added as well.\r\n\r\nGlobal Options:\r\n\r\ng:EndlineMapping ('<S-CR>'): The default endline mapping.\r\ng:EndlineInsertMapping (g:EndlineMapping): The insert mode mapping.\r\ng:EndlineNormalMapping (g:EndlineMapping): The normal mode mapping.\r\ng:EndlineInsert (1): 0 to disable the insert mode mapping.\r\ng:EndlineNormal (1): 0 to disable the normal mode mapping.\r\ng:Endlines ({}): See \"Usage\"","4":"This plugin maps (by default) <S-CR> to add a filetype's provided \"line ending\"\r\nto the end of the current line if it is not already present. For instance, a ';'\r\nwould be added to the end of a line of JavaScript source.\r\n\r\nThis is similar to a feature provided by TextMate, mapped to\r\nCommand-Option-Return in that application.\r\n\r\nUsage:\r\n\r\nSomewhere in your .vimrc (or equivalent), provide a global dict mapping filetype\r\nnames to line endings, like so:\r\n\r\nlet g:Endlines = {\r\n  \\'erlang': '.',\r\n  \\'java': ';',\r\n  \\'javascript': ';',\r\n  \\'ocaml': ';;',\r\n  \\'perl': ';',\r\n  \\'php': ';',\r\n  \\'python': ':',\r\n  \\'sml': ';'\r\n\\}\r\n\r\nMappings can also be a list of patterns that will be tried in order. In the\r\nfollowing example, a \" ->\" is appended if the line starts with no whitespace\r\nand ends with a \")\", and a \",\" is appended if the line ends with\r\nnon-whitespace.\r\n\r\nlet g:Endlines = {\r\n      \\'erlang':     [\r\n        \\['^\\S.*)$', ' ->'],\r\n        \\['\\S$', ',']]\r\n      \\}\r\n\r\nBy default, <S-CR> is mapped in both insert and normal mode. In insert mode, a\r\nnew line is added as well.\r\n\r\nGlobal Options:\r\n\r\ng:EndlineMapping ('<S-CR>'): The default endline mapping.\r\ng:EndlineInsertMapping (g:EndlineMapping): The insert mode mapping.\r\ng:EndlineNormalMapping (g:EndlineMapping): The normal mode mapping.\r\ng:EndlineInsert (1): 0 to disable the insert mode mapping.\r\ng:EndlineNormal (1): 0 to disable the normal mode mapping.\r\ng:Endlines ({}): See \"Usage\"","install_details":"1. Extract the downloaded endline.zip file\r\n2. Copy endline\/doc\/endline.txt to .vim\/doc\/endline.txt\r\n3. Copy endline\/plugin\/endline.vim to .vim\/plugin\/endline.vim\r\n4. Run :helptags ~\/.vim\/doc to load the documentation\r\n5. Map your filetype line-endings (see \"Usage\" above, or :h Endline-usage)","5":"1. Extract the downloaded endline.zip file\r\n2. Copy endline\/doc\/endline.txt to .vim\/doc\/endline.txt\r\n3. Copy endline\/plugin\/endline.vim to .vim\/plugin\/endline.vim\r\n4. Run :helptags ~\/.vim\/doc to load the documentation\r\n5. Map your filetype line-endings (see \"Usage\" above, or :h Endline-usage)","first_name":"Thomas","6":"Thomas","last_name":"Allen","7":"Allen","releases":[{"0":"3163","vim_version":"7.0","1":"7.0","script_version":"0.2.0","2":"0.2.0","version_comment":"Added support for pattern-specific line endings.","3":"Added support for pattern-specific line endings.","package":"endline.zip","4":"endline.zip","src_id":"23397","5":"23397","creation_date":"1434488738","6":"1434488738"},{"0":"3163","vim_version":"7.0","1":"7.0","script_version":"0.1.1","2":"0.1.1","version_comment":"Fix bad global function definition.","3":"Fix bad global function definition.","package":"endline.zip","4":"endline.zip","src_id":"23394","5":"23394","creation_date":"1434472015","6":"1434472015"},{"0":"3163","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"endline.tgz","4":"endline.tgz","src_id":"13386","5":"13386","creation_date":"1279809930","6":"1279809930"}]},"3162":{"script_id":"3162","0":"3162","script_name":"tabops","1":"tabops","script_type":"utility","2":"utility","summary":"A collection of miscellaneous functionalities operating tabs.","3":"A collection of miscellaneous functionalities operating tabs.","description":"Description:\r\n\r\n  This script provides tab operation functionalities.\r\n  Going to some tab, moving some tab and sorting tabs.\r\n\r\n\r\nUsage:\r\n  1. (optional) set prefix if you want to change. (let g:Tabops_prefix)\r\n     default: <Tab>\r\n  2. (optional) let g:Tabops_use??? variables 0 if you want to disable some features.\r\n  3. start editing\r\n                                                                                      \r\n  X. execute :Tabops command with some parameters (see Feature section)\r\n                                                                                      \r\nFeature:\r\n                                                                                      \r\n  * the default prefix is <Tab>\r\n                                                                                      \r\n  if g:Tabops_useGoto == 1 then ...\r\n      <C-Tab>  : goto the next tab.\r\n      <S-C-Tab>: goto the prev tab.\r\n                                                                                      \r\n      {prefix}1: goto the 1st tab.\r\n      {prefix}2: goto the 2nd tab.\r\n         :\r\n      {prefix}8: goto the 8th tab.\r\n      {prefix}9: goto the LAST tab.\r\n                                                                                      \r\n  if g:Tabops_useMove == 1 then ...\r\n      {prefix}l: swap the current tab with the right one.\r\n      {prefix}h: swap the cerrent tab with the left one.\r\n                                                                                      \r\n                                                                                      \r\n  :Tabops [Close | Open | ...]\r\n      Close\r\n          Right\r\n          Left\r\n              closes right\/left tabs except the current tab.\r\n      Open\r\n          Siblings [LOADED]\r\n              scans buffers that are in the same directory, and open them in tabs.\r\n              with LOADED, only loaded buffers are read in tabs. (not globbed)\r\n          WndInNewTab\r\n              (in splitted window) closes the current window and opens it in new tab.\r\n      Reopen\r\n          re-opens a closed tab.\r\n      Sort\r\n          ByPath\r\n              sorts tabs comparing their paths.\r\n          ByBufnr\r\n              sorts tabs comparing their internal numbers.\r\n          ByLastChange\r\n              sorts tabs comparing their recently-changed timestamps.\r\n              the most recent tab comes to left.\r\n      Uniq\r\n          closes duplicate tabs.\r\n","4":"Description:\r\n\r\n  This script provides tab operation functionalities.\r\n  Going to some tab, moving some tab and sorting tabs.\r\n\r\n\r\nUsage:\r\n  1. (optional) set prefix if you want to change. (let g:Tabops_prefix)\r\n     default: <Tab>\r\n  2. (optional) let g:Tabops_use??? variables 0 if you want to disable some features.\r\n  3. start editing\r\n                                                                                      \r\n  X. execute :Tabops command with some parameters (see Feature section)\r\n                                                                                      \r\nFeature:\r\n                                                                                      \r\n  * the default prefix is <Tab>\r\n                                                                                      \r\n  if g:Tabops_useGoto == 1 then ...\r\n      <C-Tab>  : goto the next tab.\r\n      <S-C-Tab>: goto the prev tab.\r\n                                                                                      \r\n      {prefix}1: goto the 1st tab.\r\n      {prefix}2: goto the 2nd tab.\r\n         :\r\n      {prefix}8: goto the 8th tab.\r\n      {prefix}9: goto the LAST tab.\r\n                                                                                      \r\n  if g:Tabops_useMove == 1 then ...\r\n      {prefix}l: swap the current tab with the right one.\r\n      {prefix}h: swap the cerrent tab with the left one.\r\n                                                                                      \r\n                                                                                      \r\n  :Tabops [Close | Open | ...]\r\n      Close\r\n          Right\r\n          Left\r\n              closes right\/left tabs except the current tab.\r\n      Open\r\n          Siblings [LOADED]\r\n              scans buffers that are in the same directory, and open them in tabs.\r\n              with LOADED, only loaded buffers are read in tabs. (not globbed)\r\n          WndInNewTab\r\n              (in splitted window) closes the current window and opens it in new tab.\r\n      Reopen\r\n          re-opens a closed tab.\r\n      Sort\r\n          ByPath\r\n              sorts tabs comparing their paths.\r\n          ByBufnr\r\n              sorts tabs comparing their internal numbers.\r\n          ByLastChange\r\n              sorts tabs comparing their recently-changed timestamps.\r\n              the most recent tab comes to left.\r\n      Uniq\r\n          closes duplicate tabs.\r\n","install_details":"Just source this file. (Put this file into the plugin directory.)","5":"Just source this file. (Put this file into the plugin directory.)","first_name":"Shuhei","6":"Shuhei","last_name":"Kubota","7":"Kubota","releases":[{"0":"3162","vim_version":"7.0","1":"7.0","script_version":"0.7.0","2":"0.7.0","version_comment":"fix tab swap","3":"fix tab swap","package":"tabops.vim","4":"tabops.vim","src_id":"26162","5":"26162","creation_date":"1533383132","6":"1533383132"},{"0":"3162","vim_version":"7.0","1":"7.0","script_version":"0.6.2","2":"0.6.2","version_comment":"fixed Open-Sibling globbing. (file path containing spaces)","3":"fixed Open-Sibling globbing. (file path containing spaces)","package":"tabops.vim","4":"tabops.vim","src_id":"18590","5":"18590","creation_date":"1347534700","6":"1347534700"},{"0":"3162","vim_version":"7.0","1":"7.0","script_version":"0.6.1","2":"0.6.1","version_comment":"changed EOL characters.","3":"changed EOL characters.","package":"tabops.vim","4":"tabops.vim","src_id":"15937","5":"15937","creation_date":"1308534300","6":"1308534300"},{"0":"3162","vim_version":"7.0","1":"7.0","script_version":"0.6","2":"0.6","version_comment":"improved Sort ByLastChange to handle changed date and time.","3":"improved Sort ByLastChange to handle changed date and time.","package":"tabops.vim","4":"tabops.vim","src_id":"15193","5":"15193","creation_date":"1299805834","6":"1299805834"},{"0":"3162","vim_version":"7.0","1":"7.0","script_version":"0.5","2":"0.5","version_comment":"1. Parameterized commands (:TabopsSortByBufnr -> :Tabops Sort ByBufnr) \r\n2. Added command :Tabops Open WndInNewTab (reopens the current window in a new tab)","3":"1. Parameterized commands (:TabopsSortByBufnr -> :Tabops Sort ByBufnr) \r\n2. Added command :Tabops Open WndInNewTab (reopens the current window in a new tab)","package":"tabops.vim","4":"tabops.vim","src_id":"14506","5":"14506","creation_date":"1292324595","6":"1292324595"},{"0":"3162","vim_version":"7.0","1":"7.0","script_version":"0.4","2":"0.4","version_comment":"Added command :TabopsCloseRight\/Left","3":"Added command :TabopsCloseRight\/Left","package":"tabops.vim","4":"tabops.vim","src_id":"13844","5":"13844","creation_date":"1284689673","6":"1284689673"}]},"3161":{"script_id":"3161","0":"3161","script_name":"pyflakes","1":"pyflakes","script_type":"ftplugin","2":"ftplugin","summary":"Vim filetype plugin for running pyflakes on Python files","3":"Vim filetype plugin for running pyflakes on Python files","description":"Usage\r\n-----\r\n1. Open a Python file\r\n2. Press `<F7>` to run `pyflakes` on it\r\n\r\nIt shows the errors inside a quickfix window, which will allow your to quickly\r\njump to the error locations by simply pressing [Enter].\r\n\r\nCustomization\r\n-------------\r\nIf you don't want to use the `<F7>` key for pyflakes-checking, simply remap it to\r\nanother key.  It autodetects whether it has been remapped and won't register\r\nthe `<F7>` key if so.  For example, to remap it to `<F3>` instead, use:\r\n\r\n    autocmd FileType python map <buffer> <F3> :call Pyflakes()<CR>\r\n","4":"Usage\r\n-----\r\n1. Open a Python file\r\n2. Press `<F7>` to run `pyflakes` on it\r\n\r\nIt shows the errors inside a quickfix window, which will allow your to quickly\r\njump to the error locations by simply pressing [Enter].\r\n\r\nCustomization\r\n-------------\r\nIf you don't want to use the `<F7>` key for pyflakes-checking, simply remap it to\r\nanother key.  It autodetects whether it has been remapped and won't register\r\nthe `<F7>` key if so.  For example, to remap it to `<F3>` instead, use:\r\n\r\n    autocmd FileType python map <buffer> <F3> :call Pyflakes()<CR>\r\n","install_details":"Installation\r\n------------\r\n1. Install pyflakes (http:\/\/pypi.python.org\/pypi\/pyflakes\/)\r\n2. Copy the file `ftplugin\/python_pyflakes.vim` to your `~\/.vim\/ftplugin` directory\r\n","5":"Installation\r\n------------\r\n1. Install pyflakes (http:\/\/pypi.python.org\/pypi\/pyflakes\/)\r\n2. Copy the file `ftplugin\/python_pyflakes.vim` to your `~\/.vim\/ftplugin` directory\r\n","first_name":"Vincent","6":"Vincent","last_name":"Driessen","7":"Driessen","releases":[{"0":"3161","vim_version":"6.0","1":"6.0","script_version":"1.1","2":"1.1","version_comment":"Doesn't redeclare the function if it is already defined. This avoids an error message when loading another Python file in the same buffer.","3":"Doesn't redeclare the function if it is already defined. This avoids an error message when loading another Python file in the same buffer.","package":"python_pyflakes.vim","4":"python_pyflakes.vim","src_id":"13394","5":"13394","creation_date":"1279889292","6":"1279889292"},{"0":"3161","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"python_pyflakes.vim","4":"python_pyflakes.vim","src_id":"13370","5":"13370","creation_date":"1279710348","6":"1279710348"}]},"3160":{"script_id":"3160","0":"3160","script_name":"pep8","1":"pep8","script_type":"ftplugin","2":"ftplugin","summary":"Vim filetype plugin for running PEP8 on Python files","3":"Vim filetype plugin for running PEP8 on Python files","description":"Usage\r\n-----\r\n1. Open a Python file\r\n2. Press `<F6>` to run `pep8` on it\r\n\r\nIt shows the errors inside a quickfix window, which will allow your to quickly\r\njump to the error locations by simply pressing [Enter].\r\n\r\nCustomization\r\n-------------\r\nIf you don't want to use the `<F6>` key for PEP8-checking, simply remap it to\r\nanother key.  It autodetects whether it has been remapped and won't register\r\nthe `<F6>` key if so.  For example, to remap it to `<F3>` instead, use:\r\n\r\n    autocmd FileType python map <buffer> <F3> :call Pep8()<CR>\r\n","4":"Usage\r\n-----\r\n1. Open a Python file\r\n2. Press `<F6>` to run `pep8` on it\r\n\r\nIt shows the errors inside a quickfix window, which will allow your to quickly\r\njump to the error locations by simply pressing [Enter].\r\n\r\nCustomization\r\n-------------\r\nIf you don't want to use the `<F6>` key for PEP8-checking, simply remap it to\r\nanother key.  It autodetects whether it has been remapped and won't register\r\nthe `<F6>` key if so.  For example, to remap it to `<F3>` instead, use:\r\n\r\n    autocmd FileType python map <buffer> <F3> :call Pep8()<CR>\r\n","install_details":"Installation\r\n------------\r\n1. Install pep8 (http:\/\/pypi.python.org\/pypi\/pep8)\r\n2. Copy the file `ftplugin\/python_pep8.vim` to your `~\/.vim\/ftplugin` directory\r\n","5":"Installation\r\n------------\r\n1. Install pep8 (http:\/\/pypi.python.org\/pypi\/pep8)\r\n2. Copy the file `ftplugin\/python_pep8.vim` to your `~\/.vim\/ftplugin` directory\r\n","first_name":"Vincent","6":"Vincent","last_name":"Driessen","7":"Driessen","releases":[{"0":"3160","vim_version":"6.0","1":"6.0","script_version":"1.1","2":"1.1","version_comment":"Doesn't redeclare the function if it is already defined. This avoids an error message when loading another Python file in the same buffer.\r\n\r\nAlso, jumps to the right column position for errors.","3":"Doesn't redeclare the function if it is already defined. This avoids an error message when loading another Python file in the same buffer.\r\n\r\nAlso, jumps to the right column position for errors.","package":"python_pep8.vim","4":"python_pep8.vim","src_id":"13395","5":"13395","creation_date":"1279894264","6":"1279894264"},{"0":"3160","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"python_pep8.vim","4":"python_pep8.vim","src_id":"13369","5":"13369","creation_date":"1279710257","6":"1279710257"}]},"3159":{"script_id":"3159","0":"3159","script_name":"ekini dark colorscheme","1":"ekini dark colorscheme","script_type":"color scheme","2":"color scheme","summary":"Dark and cool color scheme","3":"Dark and cool color scheme","description":"Vim color scheme port of http:\/\/bit.ly\/1VpbZy\r\n\r\nScreenshot: http:\/\/imgur.com\/24oot.png","4":"Vim color scheme port of http:\/\/bit.ly\/1VpbZy\r\n\r\nScreenshot: http:\/\/imgur.com\/24oot.png","install_details":"Copy to $VIM\/colors\/","5":"Copy to $VIM\/colors\/","first_name":"John Louis","6":"John Louis","last_name":"del Rosario","7":"del Rosario","releases":[{"0":"3159","vim_version":"7.2","1":"7.2","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"ekinivim.vim","4":"ekinivim.vim","src_id":"13366","5":"13366","creation_date":"1279693876","6":"1279693876"}]},"3158":{"script_id":"3158","0":"3158","script_name":"gitview","1":"gitview","script_type":"utility","2":"utility","summary":"browse changed git files within vim","3":"browse changed git files within vim","description":"this plugin enables you to open a window which lists changed git files as seen by git status -s\r\nuse by invoking\r\n:GitView\r\n\r\nvery preliminary version, but basically works\r\n\r\nshamelessly using stolen code from NERDTree :)\r\n","4":"this plugin enables you to open a window which lists changed git files as seen by git status -s\r\nuse by invoking\r\n:GitView\r\n\r\nvery preliminary version, but basically works\r\n\r\nshamelessly using stolen code from NERDTree :)\r\n","install_details":"just throw it in the plugins directory .vim\/plugin\r\n","5":"just throw it in the plugins directory .vim\/plugin\r\n","first_name":"Itay","6":"Itay","last_name":"Donenhirsch","7":"Donenhirsch","releases":[{"0":"3158","vim_version":"7.2","1":"7.2","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"gitview.vim","4":"gitview.vim","src_id":"13351","5":"13351","creation_date":"1279543282","6":"1279543282"}]},"3157":{"script_id":"3157","0":"3157","script_name":"opencl.vim","1":"opencl.vim","script_type":"syntax","2":"syntax","summary":"Syntax file for OpenCL 1.1","3":"Syntax file for OpenCL 1.1","description":"Script provides syntax highlight for OpenCL (Open Computing Language) syntax files (*.cl).","4":"Script provides syntax highlight for OpenCL (Open Computing Language) syntax files (*.cl).","install_details":"Place file within \/syntax\r\nEdit filetype.vim:\r\n\r\nadd lines -  \r\n\" OpenCL\r\nau BufNewFile,BufRead *.cl\t\t\tsetf opencl\r\n\r\nRemove- (stop vim from recognizing *.cl as common lisp)\r\n*.cl from Lisp \r\n","5":"Place file within \/syntax\r\nEdit filetype.vim:\r\n\r\nadd lines -  \r\n\" OpenCL\r\nau BufNewFile,BufRead *.cl\t\t\tsetf opencl\r\n\r\nRemove- (stop vim from recognizing *.cl as common lisp)\r\n*.cl from Lisp \r\n","first_name":"Terence","6":"Terence","last_name":"Ou","7":"Ou","releases":[{"0":"3157","vim_version":"6.0","1":"6.0","script_version":"1.1","2":"1.1","version_comment":"Initial upload","3":"Initial upload","package":"opencl.vim","4":"opencl.vim","src_id":"13350","5":"13350","creation_date":"1279540181","6":"1279540181"}]},"3156":{"script_id":"3156","0":"3156","script_name":"ikiwiki-syntax","1":"ikiwiki-syntax","script_type":"syntax","2":"syntax","summary":"syntax highlighting for ikiwiki files","3":"syntax highlighting for ikiwiki files","description":"This syntax file highlights the wikilinks and directives in IkiWiki files\r\n(.mdwn)\r\n\r\nPlease note that this syntax definition only defines highlighting for directives\r\nand wikilinks, *not* markdown files. To obtain proper highlighting of ikiwiki\r\nfiles (markdown + wikilinks\/directives), you must install the Markdown syntax\r\nfile (vimscript #1242).\r\n\r\nYou can also use this syntax definition if you use reST, by installing the reST\r\nsyntax file (vimscript #973), and putting the following in your .vimrc file:\r\n\r\n    let g:ikiwiki_render_filetype = 'rest'\r\n\r\nThis step is not required for using markdown files.\r\n\r\nThis syntax file has a git repository; you can clone it with:\r\n\r\ngit clone http:\/\/git.devnull.li\/ikiwiki-syntax.git\r\n","4":"This syntax file highlights the wikilinks and directives in IkiWiki files\r\n(.mdwn)\r\n\r\nPlease note that this syntax definition only defines highlighting for directives\r\nand wikilinks, *not* markdown files. To obtain proper highlighting of ikiwiki\r\nfiles (markdown + wikilinks\/directives), you must install the Markdown syntax\r\nfile (vimscript #1242).\r\n\r\nYou can also use this syntax definition if you use reST, by installing the reST\r\nsyntax file (vimscript #973), and putting the following in your .vimrc file:\r\n\r\n    let g:ikiwiki_render_filetype = 'rest'\r\n\r\nThis step is not required for using markdown files.\r\n\r\nThis syntax file has a git repository; you can clone it with:\r\n\r\ngit clone http:\/\/git.devnull.li\/ikiwiki-syntax.git\r\n","install_details":"unzip into ~\/.vim (or ~\\vimfiles on Windows)","5":"unzip into ~\/.vim (or ~\\vimfiles on Windows)","first_name":"Javier","6":"Javier","last_name":"Rojas","7":"Rojas","releases":[{"0":"3156","vim_version":"7.0","1":"7.0","script_version":"1.2","2":"1.2","version_comment":"added a fix for a \"undefined b:current_syntax\" problem. Thanks to F. Heiderich","3":"added a fix for a \"undefined b:current_syntax\" problem. Thanks to F. Heiderich","package":"ikiwiki-syntax_1.2.zip","4":"ikiwiki-syntax_1.2.zip","src_id":"16350","5":"16350","creation_date":"1314297213","6":"1314297213"},{"0":"3156","vim_version":"7.0","1":"7.0","script_version":"1.1","2":"1.1","version_comment":"Initial upload","3":"Initial upload","package":"ikiwiki-syntax.zip","4":"ikiwiki-syntax.zip","src_id":"13349","5":"13349","creation_date":"1279519670","6":"1279519670"}]},"3155":{"script_id":"3155","0":"3155","script_name":"slang_syntax","1":"slang_syntax","script_type":"syntax","2":"syntax","summary":"Sytanx files for OpenGL shader languages GLSL 400 and GLSL 330","3":"Sytanx files for OpenGL shader languages GLSL 400 and GLSL 330","description":"Sytax files for GLSL 400 and GLSL 330\r\n\r\nThis is based on vimscript#1002, but include new keywords and constructs.\r\n\r\nShows compatibility keywords\/functions etc as warnings.","4":"Sytax files for GLSL 400 and GLSL 330\r\n\r\nThis is based on vimscript#1002, but include new keywords and constructs.\r\n\r\nShows compatibility keywords\/functions etc as warnings.","install_details":"Extract package.\r\nPut glsl400.vim and glsl330.vim in vim syntax directory (for me C:\\Program Files\\Vim\\vim72\\syntax).\r\nAppend content of vimrc.vim to your vimrc to enable filetype recognition.","5":"Extract package.\r\nPut glsl400.vim and glsl330.vim in vim syntax directory (for me C:\\Program Files\\Vim\\vim72\\syntax).\r\nAppend content of vimrc.vim to your vimrc to enable filetype recognition.","first_name":"Kamil","6":"Kamil","last_name":"Patelczyk","7":"Patelczyk","releases":[{"0":"3155","vim_version":"6.0","1":"6.0","script_version":"1","2":"1","version_comment":"Initial upload","3":"Initial upload","package":"slang_syntax.tar.gz","4":"slang_syntax.tar.gz","src_id":"13347","5":"13347","creation_date":"1279446366","6":"1279446366"}]},"3154":{"script_id":"3154","0":"3154","script_name":"vorax","1":"vorax","script_type":"utility","2":"utility","summary":"An Oracle IDE for Geeks.","3":"An Oracle IDE for Geeks.","description":"Vorax is a simple yet powerful IDE for Oracle databases, built on top of the widely known Vim editor and Oracle SqlPLUS.\r\n\r\nFEATURES\r\n\r\n   * Advanced code completion\r\n   * A nice database explorer\r\n   * Connections manager\r\n   * Formatted output\r\n   * PL\/SQL support\r\n   * Integrated Oracle documentation search\r\n\r\nThis project is hosted on: http:\/\/talek.github.io\/vorax4\r\nDocumentation: https:\/\/github.com\/talek\/vorax4\/wiki\r\nVoraX Blog: http:\/\/vorax-ide.blogspot.com\/","4":"Vorax is a simple yet powerful IDE for Oracle databases, built on top of the widely known Vim editor and Oracle SqlPLUS.\r\n\r\nFEATURES\r\n\r\n   * Advanced code completion\r\n   * A nice database explorer\r\n   * Connections manager\r\n   * Formatted output\r\n   * PL\/SQL support\r\n   * Integrated Oracle documentation search\r\n\r\nThis project is hosted on: http:\/\/talek.github.io\/vorax4\r\nDocumentation: https:\/\/github.com\/talek\/vorax4\/wiki\r\nVoraX Blog: http:\/\/vorax-ide.blogspot.com\/","install_details":"VoraX follows the standard procedure of installing a Vim plugin. However, you need to take care of some dependencies VoraX relies on:\r\n\r\n   * ensure you have ruby1.9.3 or ruby2.0\r\n   * vim 7.3 compiled with ruby support\r\n   * install vorax.gem to get the dependent gems: gem install vorax --no-rdoc --no-ri\r\n   * ensure you have a valid Oracle client with sqlplus available\r\n   * install Vorax vim plugin: manually, pathogen, vundle... it's up to you.\r\n","5":"VoraX follows the standard procedure of installing a Vim plugin. However, you need to take care of some dependencies VoraX relies on:\r\n\r\n   * ensure you have ruby1.9.3 or ruby2.0\r\n   * vim 7.3 compiled with ruby support\r\n   * install vorax.gem to get the dependent gems: gem install vorax --no-rdoc --no-ri\r\n   * ensure you have a valid Oracle client with sqlplus available\r\n   * install Vorax vim plugin: manually, pathogen, vundle... it's up to you.\r\n","first_name":"Alexandru","6":"Alexandru","last_name":"Tica","7":"Tica","releases":[{"0":"3154","vim_version":"7.4","1":"7.4","script_version":"4.3.31","2":"4.3.31","version_comment":"- completion items based on words from the output window\r\n- VORAXNew command added\r\n- dependent objects when extracting the definition of an object\r\n- open the definition of an Oracle user from the database explorer\r\n- SPACE key to highlight the current statement before executing it (available in an SQL buffer only)\r\n- transaction indicator in the status line when Vorax is in an open transaction (thanks to Frank Streitzig)\r\n- many bug fixes","3":"- completion items based on words from the output window\r\n- VORAXNew command added\r\n- dependent objects when extracting the definition of an object\r\n- open the definition of an Oracle user from the database explorer\r\n- SPACE key to highlight the current statement before executing it (available in an SQL buffer only)\r\n- transaction indicator in the status line when Vorax is in an open transaction (thanks to Frank Streitzig)\r\n- many bug fixes","package":"vorax-4.3.31.zip","4":"vorax-4.3.31.zip","src_id":"22020","5":"22020","creation_date":"1402489944","6":"1402489944"},{"0":"3154","vim_version":"7.3","1":"7.3","script_version":"4.3.3","2":"4.3.3","version_comment":"- syntax files for Oracle SQL\/PLSQL code\r\n- new indent files which are smarter when it comes to indent Oracle code\r\n- add the possibility to execute the entire SQL buffer\r\n- bug fixes","3":"- syntax files for Oracle SQL\/PLSQL code\r\n- new indent files which are smarter when it comes to indent Oracle code\r\n- add the possibility to execute the entire SQL buffer\r\n- bug fixes","package":"vorax-4.3.3.zip","4":"vorax-4.3.3.zip","src_id":"21388","5":"21388","creation_date":"1390840610","6":"1390840610"}]},"3153":{"script_id":"3153","0":"3153","script_name":"CSS one-line \/ multi-line folding","1":"CSS one-line \/ multi-line folding","script_type":"ftplugin","2":"ftplugin","summary":"Folded text is compressed on one line","3":"Folded text is compressed on one line","description":"\/* one-line CSS (see http:\/\/neutroncreations.com\/blog\/single-line-vs-multi-line-css-plus-textmate-tips\/) *\/\r\nheader h1 { float: left;  width: 155px; height: 50px;  }\r\n\r\n\/* Multiline CSS *\/\r\nheader h1 {\r\n  float: left;\r\n  width: 155px;\r\n  height: 50px;\r\n}\r\n\r\nWhich to choose? One line CSS is easier to scan through and saves space, but multi-line CSS is easier to grep and edit.\r\n\r\nThis script sets you up so you edit and save multi-line CSS, but when you turn folding on, everything\u00c2\u00b4s compressed on one line so you can scan through it easier.\r\n\r\nControls are vim\u00c2\u00b4s standard for text folding:\r\nzo and zc: Open and Close fold (set multiline, set oneline)\r\nzR and zM: Reopen and Close all (globally set multiline, globally set oneline)\r\nzj, zk: go down and up a fold (CSS block).\r\n","4":"\/* one-line CSS (see http:\/\/neutroncreations.com\/blog\/single-line-vs-multi-line-css-plus-textmate-tips\/) *\/\r\nheader h1 { float: left;  width: 155px; height: 50px;  }\r\n\r\n\/* Multiline CSS *\/\r\nheader h1 {\r\n  float: left;\r\n  width: 155px;\r\n  height: 50px;\r\n}\r\n\r\nWhich to choose? One line CSS is easier to scan through and saves space, but multi-line CSS is easier to grep and edit.\r\n\r\nThis script sets you up so you edit and save multi-line CSS, but when you turn folding on, everything\u00c2\u00b4s compressed on one line so you can scan through it easier.\r\n\r\nControls are vim\u00c2\u00b4s standard for text folding:\r\nzo and zc: Open and Close fold (set multiline, set oneline)\r\nzR and zM: Reopen and Close all (globally set multiline, globally set oneline)\r\nzj, zk: go down and up a fold (CSS block).\r\n","install_details":"Copy to ~\/.vim\/ftplugin\/css_folding.vim","5":"Copy to ~\/.vim\/ftplugin\/css_folding.vim","first_name":"Michael","6":"Michael","last_name":"W","7":"W","releases":[{"0":"3153","vim_version":"7.2","1":"7.2","script_version":"0.'","2":"0.'","version_comment":"Initial upload","3":"Initial upload","package":"css_folding.vim","4":"css_folding.vim","src_id":"13344","5":"13344","creation_date":"1279339377","6":"1279339377"}]},"3152":{"script_id":"3152","0":"3152","script_name":"sablecc.vim","1":"sablecc.vim","script_type":"syntax","2":"syntax","summary":"syntax highlighting for sablecc","3":"syntax highlighting for sablecc","description":"This file provides syntax highlighting for sablecc grammar. For windows compatible the \r\ngrammar should end with .scc\r\n","4":"This file provides syntax highlighting for sablecc grammar. For windows compatible the \r\ngrammar should end with .scc\r\n","install_details":"I have not try in windows. This instruction is for Linux\r\n1) Copy the file in syntax directory\r\n$ mkdir -p ~\/.vim\/syntax\r\n$ cp sablecc.vim ~\/.vim\/syntax\r\n\r\n2) Associate *.scc file with the script\r\ngvim ~\/.vimrc\r\n\r\nput these line in the script:\r\n\r\naugroup filetypedetect\r\n\tau BufNewFile,BufRead *.scc setf sablecc\r\naugroup END\r\n\r\n","5":"I have not try in windows. This instruction is for Linux\r\n1) Copy the file in syntax directory\r\n$ mkdir -p ~\/.vim\/syntax\r\n$ cp sablecc.vim ~\/.vim\/syntax\r\n\r\n2) Associate *.scc file with the script\r\ngvim ~\/.vimrc\r\n\r\nput these line in the script:\r\n\r\naugroup filetypedetect\r\n\tau BufNewFile,BufRead *.scc setf sablecc\r\naugroup END\r\n\r\n","first_name":"lazy","6":"lazy","last_name":"boy","7":"boy","releases":[{"0":"3152","vim_version":"7.0","1":"7.0","script_version":"July, 15th","2":"July, 15th","version_comment":"hightlighting for transformation from CST to AST. ( {-> .....} )","3":"hightlighting for transformation from CST to AST. ( {-> .....} )","package":"sablecc.vim","4":"sablecc.vim","src_id":"13983","5":"13983","creation_date":"1286094664","6":"1286094664"},{"0":"3152","vim_version":"7.2","1":"7.2","script_version":"beta","2":"beta","version_comment":"Initial upload","3":"Initial upload","package":"sablecc.vim","4":"sablecc.vim","src_id":"13340","5":"13340","creation_date":"1279270628","6":"1279270628"}]},"3151":{"script_id":"3151","0":"3151","script_name":"pytestator","1":"pytestator","script_type":"utility","2":"utility","summary":"simple script to simplify the use of unit test in python","3":"simple script to simplify the use of unit test in python","description":"This a really simple script to made your life easier if you write unit test in python (you should !).\r\n\r\nThis script assume that your test file is name test_<other file name>.\r\nBtw, this shouldn't be hard to change\r\n\r\nHere are the basic commands:\r\n,tc create the test file - stand for \"test create\"\r\n,tF force to create a test file (this will be necessary if another file already have the matching name, this file will be destroyed) - \"test Force (create)\"\r\n,tr run the unittest for this file - stand for \"test run\"\r\n,s  swap between test file and actual file, if the test file doesn't exist, it will be created - stand for \"swap\"\r\n\r\nYou'll be mostly (exclusivly ?) using only ,s and ,tr\r\n\r\nOther feature:\r\n - will display a big red stupid message in your statusline if this python file don't have a test file, remove the set statusline+=blabla if you don't want to have it.\r\n\r\nIf you have comments\/bugs repport\/feature request\/chocolate feel free to send me an email or ping me on irc (psycojoker@irc.freenode.net#vim)\r\n\r\n*Not* include in the script, I love those mappings:\r\nimap ,ar self.assertRaises()<left>\r\nimap ,ae self.assertEqual()<left>\r\nimap ,at self.assertTrue()<left>\r\nimap ,af self.assertFalse()<left>","4":"This a really simple script to made your life easier if you write unit test in python (you should !).\r\n\r\nThis script assume that your test file is name test_<other file name>.\r\nBtw, this shouldn't be hard to change\r\n\r\nHere are the basic commands:\r\n,tc create the test file - stand for \"test create\"\r\n,tF force to create a test file (this will be necessary if another file already have the matching name, this file will be destroyed) - \"test Force (create)\"\r\n,tr run the unittest for this file - stand for \"test run\"\r\n,s  swap between test file and actual file, if the test file doesn't exist, it will be created - stand for \"swap\"\r\n\r\nYou'll be mostly (exclusivly ?) using only ,s and ,tr\r\n\r\nOther feature:\r\n - will display a big red stupid message in your statusline if this python file don't have a test file, remove the set statusline+=blabla if you don't want to have it.\r\n\r\nIf you have comments\/bugs repport\/feature request\/chocolate feel free to send me an email or ping me on irc (psycojoker@irc.freenode.net#vim)\r\n\r\n*Not* include in the script, I love those mappings:\r\nimap ,ar self.assertRaises()<left>\r\nimap ,ae self.assertEqual()<left>\r\nimap ,at self.assertTrue()<left>\r\nimap ,af self.assertFalse()<left>","install_details":"Just put the file into ~\/.vim\/plugin\/","5":"Just put the file into ~\/.vim\/plugin\/","first_name":"Laurent","6":"Laurent","last_name":"Peuch","7":"Peuch","releases":[{"0":"3151","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"pytestator.vim","4":"pytestator.vim","src_id":"13335","5":"13335","creation_date":"1279160522","6":"1279160522"}]},"3150":{"script_id":"3150","0":"3150","script_name":"session.vim","1":"session.vim","script_type":"utility","2":"utility","summary":"Extended session management for Vim","3":"Extended session management for Vim","description":"The session.vim plug-in improves upon Vim's built-in :mksession command by enabling you to easily and (if you want) automatically persist and restore your Vim editing sessions. It works by generating a Vim script that restores your current settings and the arrangement of tab pages and\/or split windows and the files they contain. For more information about the plug-in please refer to its homepage or the project page on GitHub:\r\n\r\n\u00e2\u0080\u00a2 http:\/\/peterodding.com\/code\/vim\/session\/\r\n\u00e2\u0080\u00a2 http:\/\/github.com\/xolox\/vim-session\r\n\r\nIf you have questions, bug reports, suggestions, etc. the author can be contacted at peter@peterodding.com. If you like this plug-in please vote for it below!","4":"The session.vim plug-in improves upon Vim's built-in :mksession command by enabling you to easily and (if you want) automatically persist and restore your Vim editing sessions. It works by generating a Vim script that restores your current settings and the arrangement of tab pages and\/or split windows and the files they contain. For more information about the plug-in please refer to its homepage or the project page on GitHub:\r\n\r\n\u00e2\u0080\u00a2 http:\/\/peterodding.com\/code\/vim\/session\/\r\n\u00e2\u0080\u00a2 http:\/\/github.com\/xolox\/vim-session\r\n\r\nIf you have questions, bug reports, suggestions, etc. the author can be contacted at peter@peterodding.com. If you like this plug-in please vote for it below!","install_details":"Please note that the vim-session plug-in requires my vim-misc plug-in which is separately distributed (see vimscript #4597). \r\n\r\nUnzip the most recent ZIP archives of the vim-session and vim-misc plug-ins inside your Vim profile directory (usually this is ~\/.vim on UNIX and %USERPROFILE%\\vimfiles on Windows), restart Vim and execute the command :helptags ~\/.vim\/doc (use :helptags ~\\vimfiles\\doc instead on Windows). Now try it out: Open some tab pages and\/or split windows, change your color scheme, etc. then save your session using the \":SaveSession my-first-session\" command. You can now restore this session at any time by executing the \":OpenSession my-first-session\" command.\r\n\r\nIf you prefer you can also use Pathogen, Vundle or a similar tool to install & update the vim-session and vim-misc plug-ins using a local clone of the git repository.","5":"Please note that the vim-session plug-in requires my vim-misc plug-in which is separately distributed (see vimscript #4597). \r\n\r\nUnzip the most recent ZIP archives of the vim-session and vim-misc plug-ins inside your Vim profile directory (usually this is ~\/.vim on UNIX and %USERPROFILE%\\vimfiles on Windows), restart Vim and execute the command :helptags ~\/.vim\/doc (use :helptags ~\\vimfiles\\doc instead on Windows). Now try it out: Open some tab pages and\/or split windows, change your color scheme, etc. then save your session using the \":SaveSession my-first-session\" command. You can now restore this session at any time by executing the \":OpenSession my-first-session\" command.\r\n\r\nIf you prefer you can also use Pathogen, Vundle or a similar tool to install & update the vim-session and vim-misc plug-ins using a local clone of the git repository.","first_name":"Peter","6":"Peter","last_name":"Odding","7":"Odding","releases":[{"0":"3150","vim_version":"7.0","1":"7.0","script_version":"2.13.1","2":"2.13.1","version_comment":" \u00e2\u0080\u00a2 Document usage of multiple platforms (issue #85):\n   http:\/\/github.com\/xolox\/vim-session\/commit\/9e9a608","3":" \u00e2\u0080\u00a2 Document usage of multiple platforms (issue #85):\n   http:\/\/github.com\/xolox\/vim-session\/commit\/9e9a608","package":"session.zip","4":"session.zip","src_id":"23698","5":"23698","creation_date":"1446379426","6":"1446379426"},{"0":"3150","vim_version":"7.0","1":"7.0","script_version":"2.13","2":"2.13","version_comment":" \u00e2\u0080\u00a2 Document how to omit hidden & unloaded buffers from session persistence:\n   http:\/\/github.com\/xolox\/vim-session\/commit\/5642089\n\n \u00e2\u0080\u00a2 Issue #128: Make saving of GUI font optional:\n   http:\/\/github.com\/xolox\/vim-session\/commit\/397d637","3":" \u00e2\u0080\u00a2 Document how to omit hidden & unloaded buffers from session persistence:\n   http:\/\/github.com\/xolox\/vim-session\/commit\/5642089\n\n \u00e2\u0080\u00a2 Issue #128: Make saving of GUI font optional:\n   http:\/\/github.com\/xolox\/vim-session\/commit\/397d637","package":"session.zip","4":"session.zip","src_id":"23573","5":"23573","creation_date":"1441390249","6":"1441390249"},{"0":"3150","vim_version":"7.0","1":"7.0","script_version":"2.12","2":"2.12","version_comment":" \u00e2\u0080\u00a2 auto_save_to option added:\n   http:\/\/github.com\/xolox\/vim-session\/commit\/46d6c02\n\n \u00e2\u0080\u00a2 Remove outdated information from documentation:\n   http:\/\/github.com\/xolox\/vim-session\/commit\/705d726\n\n \u00e2\u0080\u00a2 Merge pull request #81: Add g:session_autosave_to (override) option:\n   http:\/\/github.com\/xolox\/vim-session\/commit\/060dea4","3":" \u00e2\u0080\u00a2 auto_save_to option added:\n   http:\/\/github.com\/xolox\/vim-session\/commit\/46d6c02\n\n \u00e2\u0080\u00a2 Remove outdated information from documentation:\n   http:\/\/github.com\/xolox\/vim-session\/commit\/705d726\n\n \u00e2\u0080\u00a2 Merge pull request #81: Add g:session_autosave_to (override) option:\n   http:\/\/github.com\/xolox\/vim-session\/commit\/060dea4","package":"session.zip","4":"session.zip","src_id":"23460","5":"23460","creation_date":"1436384872","6":"1436384872"},{"0":"3150","vim_version":"7.0","1":"7.0","script_version":"2.11","2":"2.11","version_comment":" \u00e2\u0080\u00a2 Update screenshots of automatic session save\/restore in README:\n   http:\/\/github.com\/xolox\/vim-session\/commit\/8670b1e\n\n \u00e2\u0080\u00a2 Update installation instructions:\n   http:\/\/github.com\/xolox\/vim-session\/commit\/5c3ab85\n\n \u00e2\u0080\u00a2 Enable silencing automatic periodic sessions saving:\n   http:\/\/github.com\/xolox\/vim-session\/commit\/7aa90d4","3":" \u00e2\u0080\u00a2 Update screenshots of automatic session save\/restore in README:\n   http:\/\/github.com\/xolox\/vim-session\/commit\/8670b1e\n\n \u00e2\u0080\u00a2 Update installation instructions:\n   http:\/\/github.com\/xolox\/vim-session\/commit\/5c3ab85\n\n \u00e2\u0080\u00a2 Enable silencing automatic periodic sessions saving:\n   http:\/\/github.com\/xolox\/vim-session\/commit\/7aa90d4","package":"session.zip","4":"session.zip","src_id":"23459","5":"23459","creation_date":"1436379671","6":"1436379671"},{"0":"3150","vim_version":"7.0","1":"7.0","script_version":"2.10.1","2":"2.10.1","version_comment":" \u00e2\u0080\u00a2 Rephrase prompts for automatic session save\/restore:\n   http:\/\/github.com\/xolox\/vim-session\/commit\/fb6118b","3":" \u00e2\u0080\u00a2 Rephrase prompts for automatic session save\/restore:\n   http:\/\/github.com\/xolox\/vim-session\/commit\/fb6118b","package":"session.zip","4":"session.zip","src_id":"23037","5":"23037","creation_date":"1426436639","6":"1426436639"},{"0":"3150","vim_version":"7.0","1":"7.0","script_version":"2.10","2":"2.10","version_comment":" \u00e2\u0080\u00a2 Make GUI dialogs from s:prompt easier to read:\n   http:\/\/github.com\/xolox\/vim-session\/commit\/80d7822\n\n \u00e2\u0080\u00a2 Merge pull request #104: Make GUI dialogs easier to read:\n   http:\/\/github.com\/xolox\/vim-session\/commit\/c7ea852","3":" \u00e2\u0080\u00a2 Make GUI dialogs from s:prompt easier to read:\n   http:\/\/github.com\/xolox\/vim-session\/commit\/80d7822\n\n \u00e2\u0080\u00a2 Merge pull request #104: Make GUI dialogs easier to read:\n   http:\/\/github.com\/xolox\/vim-session\/commit\/c7ea852","package":"session.zip","4":"session.zip","src_id":"23035","5":"23035","creation_date":"1426423129","6":"1426423129"},{"0":"3150","vim_version":"7.0","1":"7.0","script_version":"2.9.2","2":"2.9.2","version_comment":" \u00e2\u0080\u00a2 Merge pull request 116: Fix --servername option when using vim-startify:\n   http:\/\/github.com\/xolox\/vim-session\/commit\/a5d564f\n\n \u00e2\u0080\u00a2 Move \"session is empty?\" check to separate function:\n   http:\/\/github.com\/xolox\/vim-session\/commit\/35b6742","3":" \u00e2\u0080\u00a2 Merge pull request 116: Fix --servername option when using vim-startify:\n   http:\/\/github.com\/xolox\/vim-session\/commit\/a5d564f\n\n \u00e2\u0080\u00a2 Move \"session is empty?\" check to separate function:\n   http:\/\/github.com\/xolox\/vim-session\/commit\/35b6742","package":"session.zip","4":"session.zip","src_id":"23032","5":"23032","creation_date":"1426411420","6":"1426411420"},{"0":"3150","vim_version":"7.0","1":"7.0","script_version":"2.9","2":"2.9","version_comment":" \u00e2\u0080\u00a2 Add option to disable session locking (issue #112 on GitHub):\n   http:\/\/github.com\/xolox\/vim-session\/commit\/46d8732","3":" \u00e2\u0080\u00a2 Add option to disable session locking (issue #112 on GitHub):\n   http:\/\/github.com\/xolox\/vim-session\/commit\/46d8732","package":"session.zip","4":"session.zip","src_id":"22925","5":"22925","creation_date":"1424296666","6":"1424296666"},{"0":"3150","vim_version":"7.0","1":"7.0","script_version":"2.8","2":"2.8","version_comment":" \u00e2\u0080\u00a2 Automatically store lock files in \/var\/lock when possible (issue #110):\n   http:\/\/github.com\/xolox\/vim-session\/commit\/f2dab5d","3":" \u00e2\u0080\u00a2 Automatically store lock files in \/var\/lock when possible (issue #110):\n   http:\/\/github.com\/xolox\/vim-session\/commit\/f2dab5d","package":"session.zip","4":"session.zip","src_id":"22915","5":"22915","creation_date":"1423830399","6":"1423830399"},{"0":"3150","vim_version":"7.0","1":"7.0","script_version":"2.7","2":"2.7","version_comment":" \u00e2\u0080\u00a2 Add support for lock directory configuration:\n   http:\/\/github.com\/xolox\/vim-session\/commit\/4fb9cdd","3":" \u00e2\u0080\u00a2 Add support for lock directory configuration:\n   http:\/\/github.com\/xolox\/vim-session\/commit\/4fb9cdd","package":"session.zip","4":"session.zip","src_id":"22423","5":"22423","creation_date":"1410692879","6":"1410692879"},{"0":"3150","vim_version":"7.0","1":"7.0","script_version":"2.6.4","2":"2.6.4","version_comment":" \u00e2\u0080\u00a2 Drop the filtering of :args and :argu from the session file:\n   http:\/\/github.com\/xolox\/vim-session\/commit\/40d08ab","3":" \u00e2\u0080\u00a2 Drop the filtering of :args and :argu from the session file:\n   http:\/\/github.com\/xolox\/vim-session\/commit\/40d08ab","package":"session.zip","4":"session.zip","src_id":"22278","5":"22278","creation_date":"1406751800","6":"1406751800"},{"0":"3150","vim_version":"7.0","1":"7.0","script_version":"2.6.3","2":"2.6.3","version_comment":" \u00e2\u0080\u00a2 Write correct session lock when (auto-)opening tab-scoped session:\n   http:\/\/github.com\/xolox\/vim-session\/commit\/8254cff","3":" \u00e2\u0080\u00a2 Write correct session lock when (auto-)opening tab-scoped session:\n   http:\/\/github.com\/xolox\/vim-session\/commit\/8254cff","package":"session.zip","4":"session.zip","src_id":"22277","5":"22277","creation_date":"1406750072","6":"1406750072"},{"0":"3150","vim_version":"7.0","1":"7.0","script_version":"2.6.2","2":"2.6.2","version_comment":" \u00e2\u0080\u00a2 Resolve issue #100 (bug fix for session_default_overwrite implementation):\n   http:\/\/github.com\/xolox\/vim-session\/commit\/c247d0b","3":" \u00e2\u0080\u00a2 Resolve issue #100 (bug fix for session_default_overwrite implementation):\n   http:\/\/github.com\/xolox\/vim-session\/commit\/c247d0b","package":"session.zip","4":"session.zip","src_id":"22276","5":"22276","creation_date":"1406749767","6":"1406749767"},{"0":"3150","vim_version":"7.0","1":"7.0","script_version":"2.6.1","2":"2.6.1","version_comment":" \u00e2\u0080\u00a2 Try to improve user feedback when sessions are locked:\n   http:\/\/github.com\/xolox\/vim-session\/commit\/d833471","3":" \u00e2\u0080\u00a2 Try to improve user feedback when sessions are locked:\n   http:\/\/github.com\/xolox\/vim-session\/commit\/d833471","package":"session.zip","4":"session.zip","src_id":"22146","5":"22146","creation_date":"1404688741","6":"1404688741"},{"0":"3150","vim_version":"7.0","1":"7.0","script_version":"2.6","2":"2.6","version_comment":" \u00e2\u0080\u00a2 Merge pull request #88: User defined session name completion suggestions:\n   http:\/\/github.com\/xolox\/vim-session\/commit\/f13514a","3":" \u00e2\u0080\u00a2 Merge pull request #88: User defined session name completion suggestions:\n   http:\/\/github.com\/xolox\/vim-session\/commit\/f13514a","package":"session.zip","4":"session.zip","src_id":"22141","5":"22141","creation_date":"1404678333","6":"1404678333"},{"0":"3150","vim_version":"7.0","1":"7.0","script_version":"2.5","2":"2.5","version_comment":" \u00e2\u0080\u00a2 Explicitly credit Ingo for his work, also mention other contributions:\n   http:\/\/github.com\/xolox\/vim-session\/commit\/d98a032\n\n \u00e2\u0080\u00a2 Use xolox#misc#cursorhold#register() to setup periodic callback:\n   http:\/\/github.com\/xolox\/vim-session\/commit\/cf412a9\n\n \u00e2\u0080\u00a2 Merge pull request #78: Make color scheme persistence configurable:\n   http:\/\/github.com\/xolox\/vim-session\/commit\/407ce08","3":" \u00e2\u0080\u00a2 Explicitly credit Ingo for his work, also mention other contributions:\n   http:\/\/github.com\/xolox\/vim-session\/commit\/d98a032\n\n \u00e2\u0080\u00a2 Use xolox#misc#cursorhold#register() to setup periodic callback:\n   http:\/\/github.com\/xolox\/vim-session\/commit\/cf412a9\n\n \u00e2\u0080\u00a2 Merge pull request #78: Make color scheme persistence configurable:\n   http:\/\/github.com\/xolox\/vim-session\/commit\/407ce08","package":"session.zip","4":"session.zip","src_id":"22140","5":"22140","creation_date":"1404673325","6":"1404673325"},{"0":"3150","vim_version":"7.0","1":"7.0","script_version":"2.4.14","2":"2.4.14","version_comment":" \u00e2\u0080\u00a2 FIX: Correct order of tab and window restore commands:\n   http:\/\/github.com\/xolox\/vim-session\/commit\/81dc04c\n\n \u00e2\u0080\u00a2 Handle (i.e. do not increase) zero-width windows:\n   http:\/\/github.com\/xolox\/vim-session\/commit\/c8f8417\n\n \u00e2\u0080\u00a2 BUG: No prompt for session auto-load when unloaded buffers exist:\n   http:\/\/github.com\/xolox\/vim-session\/commit\/e497a6d\n\n \u00e2\u0080\u00a2 Merge pull request #93: Correct order of tab and window restore commands:\n   http:\/\/github.com\/xolox\/vim-session\/commit\/70cbfa9\n\n \u00e2\u0080\u00a2 Merge pull request #94: Handle (i.e. do not increase) zero-width windows:\n   http:\/\/github.com\/xolox\/vim-session\/commit\/5338653\n\n \u00e2\u0080\u00a2 Merge pull request #95: No prompt for session auto-load when unloaded buffers exist:\n   http:\/\/github.com\/xolox\/vim-session\/commit\/da040dd","3":" \u00e2\u0080\u00a2 FIX: Correct order of tab and window restore commands:\n   http:\/\/github.com\/xolox\/vim-session\/commit\/81dc04c\n\n \u00e2\u0080\u00a2 Handle (i.e. do not increase) zero-width windows:\n   http:\/\/github.com\/xolox\/vim-session\/commit\/c8f8417\n\n \u00e2\u0080\u00a2 BUG: No prompt for session auto-load when unloaded buffers exist:\n   http:\/\/github.com\/xolox\/vim-session\/commit\/e497a6d\n\n \u00e2\u0080\u00a2 Merge pull request #93: Correct order of tab and window restore commands:\n   http:\/\/github.com\/xolox\/vim-session\/commit\/70cbfa9\n\n \u00e2\u0080\u00a2 Merge pull request #94: Handle (i.e. do not increase) zero-width windows:\n   http:\/\/github.com\/xolox\/vim-session\/commit\/5338653\n\n \u00e2\u0080\u00a2 Merge pull request #95: No prompt for session auto-load when unloaded buffers exist:\n   http:\/\/github.com\/xolox\/vim-session\/commit\/da040dd","package":"session.zip","4":"session.zip","src_id":"22055","5":"22055","creation_date":"1403124809","6":"1403124809"},{"0":"3150","vim_version":"7.0","1":"7.0","script_version":"2.4.11","2":"2.4.11","version_comment":" \u00e2\u0080\u00a2 Remove the -count=94919 workaround for :AppendTabSession.:\n   http:\/\/github.com\/xolox\/vim-session\/commit\/de89506\n\n \u00e2\u0080\u00a2 Don't leave behind empty tab page when :AppendTabSession is unsuccessful:\n   http:\/\/github.com\/xolox\/vim-session\/commit\/f7845fa\n\n \u00e2\u0080\u00a2 Merge pull request #82: Remove -count=94919 workaround for :AppendTabSession:\n   http:\/\/github.com\/xolox\/vim-session\/commit\/1f576c1\n\n \u00e2\u0080\u00a2 Merge pull request #83: Don't leave behind empty tab page when :AppendTabSession is unsuccessful:\n   http:\/\/github.com\/xolox\/vim-session\/commit\/8e124c9","3":" \u00e2\u0080\u00a2 Remove the -count=94919 workaround for :AppendTabSession.:\n   http:\/\/github.com\/xolox\/vim-session\/commit\/de89506\n\n \u00e2\u0080\u00a2 Don't leave behind empty tab page when :AppendTabSession is unsuccessful:\n   http:\/\/github.com\/xolox\/vim-session\/commit\/f7845fa\n\n \u00e2\u0080\u00a2 Merge pull request #82: Remove -count=94919 workaround for :AppendTabSession:\n   http:\/\/github.com\/xolox\/vim-session\/commit\/1f576c1\n\n \u00e2\u0080\u00a2 Merge pull request #83: Don't leave behind empty tab page when :AppendTabSession is unsuccessful:\n   http:\/\/github.com\/xolox\/vim-session\/commit\/8e124c9","package":"session.zip","4":"session.zip","src_id":"22047","5":"22047","creation_date":"1403033968","6":"1403033968"},{"0":"3150","vim_version":"7.0","1":"7.0","script_version":"2.4.9","2":"2.4.9","version_comment":" \u00e2\u0080\u00a2 Make :ViewSession compatible with console Vim (reported by Yuki Iwanaga):\n   http:\/\/github.com\/xolox\/vim-session\/commit\/a55318b","3":" \u00e2\u0080\u00a2 Make :ViewSession compatible with console Vim (reported by Yuki Iwanaga):\n   http:\/\/github.com\/xolox\/vim-session\/commit\/a55318b","package":"session.zip","4":"session.zip","src_id":"20922","5":"20922","creation_date":"1381858040","6":"1381858040"},{"0":"3150","vim_version":"7.0","1":"7.0","script_version":"2.4.8","2":"2.4.8","version_comment":" \u00e2\u0080\u00a2 Allow to turn off the default Session menu via g:session_menu option (contributed by Ingo Karkat):\n   http:\/\/github.com\/xolox\/vim-session\/commit\/58ae953\n   http:\/\/github.com\/xolox\/vim-session\/commit\/9607a6b","3":" \u00e2\u0080\u00a2 Allow to turn off the default Session menu via g:session_menu option (contributed by Ingo Karkat):\n   http:\/\/github.com\/xolox\/vim-session\/commit\/58ae953\n   http:\/\/github.com\/xolox\/vim-session\/commit\/9607a6b","package":"session.zip","4":"session.zip","src_id":"20549","5":"20549","creation_date":"1374317402","6":"1374317402"},{"0":"3150","vim_version":"7.0","1":"7.0","script_version":"2.4.7","2":"2.4.7","version_comment":" \u00e2\u0080\u00a2 Support for sessions with multiple TagList windows:\n   http:\/\/github.com\/xolox\/vim-session\/commit\/1f9bb68","3":" \u00e2\u0080\u00a2 Support for sessions with multiple TagList windows:\n   http:\/\/github.com\/xolox\/vim-session\/commit\/1f9bb68","package":"session.zip","4":"session.zip","src_id":"20481","5":"20481","creation_date":"1372977119","6":"1372977119"},{"0":"3150","vim_version":"7.0","1":"7.0","script_version":"2.4.6","2":"2.4.6","version_comment":" \u00e2\u0080\u00a2 Add session_default_overwrite option (see readme for details):\n   http:\/\/github.com\/xolox\/vim-session\/commit\/7186722","3":" \u00e2\u0080\u00a2 Add session_default_overwrite option (see readme for details):\n   http:\/\/github.com\/xolox\/vim-session\/commit\/7186722","package":"session.zip","4":"session.zip","src_id":"20478","5":"20478","creation_date":"1372893964","6":"1372893964"},{"0":"3150","vim_version":"7.0","1":"7.0","script_version":"2.4.5","2":"2.4.5","version_comment":" \u00e2\u0080\u00a2 Make sure vim-misc is installed, politely complain if it isn't:\n   http:\/\/github.com\/xolox\/vim-session\/commit\/70c89aa","3":" \u00e2\u0080\u00a2 Make sure vim-misc is installed, politely complain if it isn't:\n   http:\/\/github.com\/xolox\/vim-session\/commit\/70c89aa","package":"session.zip","4":"session.zip","src_id":"20477","5":"20477","creation_date":"1372890525","6":"1372890525"},{"0":"3150","vim_version":"7.0","1":"7.0","script_version":"2.4.4","2":"2.4.4","version_comment":" \u00e2\u0080\u00a2 Internal refactoring: Merge s:get_name() and xolox#session#find_current_session():\n   http:\/\/github.com\/xolox\/vim-session\/commit\/f454460\n\n \u00e2\u0080\u00a2 Internal refactoring: Replace s:select_name() with xolox#session#prompt_for_name():\n   http:\/\/github.com\/xolox\/vim-session\/commit\/11c9534\n\n \u00e2\u0080\u00a2 Working on inline function documentation:\n   http:\/\/github.com\/xolox\/vim-session\/commit\/c06bcb1\n   http:\/\/github.com\/xolox\/vim-session\/commit\/74e5034\n\n \u00e2\u0080\u00a2 Bug fix: Re-implement Vim's special handling of initial, empty buffer:\n   http:\/\/github.com\/xolox\/vim-session\/commit\/d5c3b6a","3":" \u00e2\u0080\u00a2 Internal refactoring: Merge s:get_name() and xolox#session#find_current_session():\n   http:\/\/github.com\/xolox\/vim-session\/commit\/f454460\n\n \u00e2\u0080\u00a2 Internal refactoring: Replace s:select_name() with xolox#session#prompt_for_name():\n   http:\/\/github.com\/xolox\/vim-session\/commit\/11c9534\n\n \u00e2\u0080\u00a2 Working on inline function documentation:\n   http:\/\/github.com\/xolox\/vim-session\/commit\/c06bcb1\n   http:\/\/github.com\/xolox\/vim-session\/commit\/74e5034\n\n \u00e2\u0080\u00a2 Bug fix: Re-implement Vim's special handling of initial, empty buffer:\n   http:\/\/github.com\/xolox\/vim-session\/commit\/d5c3b6a","package":"session.zip","4":"session.zip","src_id":"20420","5":"20420","creation_date":"1372110538","6":"1372110538"},{"0":"3150","vim_version":"7.0","1":"7.0","script_version":"2.4.1","2":"2.4.1","version_comment":" \u00e2\u0080\u00a2 Bug fix: Disable Vim's special handling of initial, empty buffer:\n   http:\/\/github.com\/xolox\/vim-session\/commit\/aadb3a2","3":" \u00e2\u0080\u00a2 Bug fix: Disable Vim's special handling of initial, empty buffer:\n   http:\/\/github.com\/xolox\/vim-session\/commit\/aadb3a2","package":"session.zip","4":"session.zip","src_id":"20396","5":"20396","creation_date":"1371873354","6":"1371873354"},{"0":"3150","vim_version":"7.0","1":"7.0","script_version":"2.4","2":"2.4","version_comment":" \u00e2\u0080\u00a2 Make :RestartVim retain server name (contributed by Steve Vermeulen):\n   http:\/\/github.com\/xolox\/vim-session\/commit\/098f32b\n   http:\/\/github.com\/xolox\/vim-session\/commit\/dd7f738\n   http:\/\/github.com\/xolox\/vim-session\/commit\/bbd1f8f","3":" \u00e2\u0080\u00a2 Make :RestartVim retain server name (contributed by Steve Vermeulen):\n   http:\/\/github.com\/xolox\/vim-session\/commit\/098f32b\n   http:\/\/github.com\/xolox\/vim-session\/commit\/dd7f738\n   http:\/\/github.com\/xolox\/vim-session\/commit\/bbd1f8f","package":"session.zip","4":"session.zip","src_id":"20393","5":"20393","creation_date":"1371863893","6":"1371863893"},{"0":"3150","vim_version":"7.0","1":"7.0","script_version":"2.3.11","2":"2.3.11","version_comment":" \u00e2\u0080\u00a2 Bug fix: Don't persist &go and &gfn when !has('gui'):\n   http:\/\/github.com\/xolox\/vim-session\/commit\/4664cc7","3":" \u00e2\u0080\u00a2 Bug fix: Don't persist &go and &gfn when !has('gui'):\n   http:\/\/github.com\/xolox\/vim-session\/commit\/4664cc7","package":"session.zip","4":"session.zip","src_id":"20308","5":"20308","creation_date":"1370543902","6":"1370543902"},{"0":"3150","vim_version":"7.0","1":"7.0","script_version":"2.3.10","2":"2.3.10","version_comment":" \u00e2\u0080\u00a2 BUG: Wrong \"global session\" label when saving tab session for the first time (contributed by Ingo Karkat):\n   http:\/\/github.com\/xolox\/vim-session\/commit\/dd8931a","3":" \u00e2\u0080\u00a2 BUG: Wrong \"global session\" label when saving tab session for the first time (contributed by Ingo Karkat):\n   http:\/\/github.com\/xolox\/vim-session\/commit\/dd8931a","package":"session.zip","4":"session.zip","src_id":"20253","5":"20253","creation_date":"1370080562","6":"1370080562"},{"0":"3150","vim_version":"7.0","1":"7.0","script_version":"2.3.9","2":"2.3.9","version_comment":" \u00e2\u0080\u00a2 Don't ask to forget when not recalling last session:\n   http:\/\/github.com\/xolox\/vim-session\/commit\/cfc5bdf","3":" \u00e2\u0080\u00a2 Don't ask to forget when not recalling last session:\n   http:\/\/github.com\/xolox\/vim-session\/commit\/cfc5bdf","package":"session.zip","4":"session.zip","src_id":"20217","5":"20217","creation_date":"1369519793","6":"1369519793"},{"0":"3150","vim_version":"7.0","1":"7.0","script_version":"2.3.8","2":"2.3.8","version_comment":" \u00e2\u0080\u00a2 Allow to forget a saved default session, too (contribute by Ingo Karkat):\n   http:\/\/github.com\/xolox\/vim-session\/commit\/95d3b41","3":" \u00e2\u0080\u00a2 Allow to forget a saved default session, too (contribute by Ingo Karkat):\n   http:\/\/github.com\/xolox\/vim-session\/commit\/95d3b41","package":"session.zip","4":"session.zip","src_id":"20216","5":"20216","creation_date":"1369519435","6":"1369519435"},{"0":"3150","vim_version":"7.0","1":"7.0","script_version":"2.3.7","2":"2.3.7","version_comment":" \u00e2\u0080\u00a2 Persist Vim's verbosity (makes it easier to debug :RestartVim :-):\n   http:\/\/github.com\/xolox\/vim-session\/commit\/62410ba\n\n \u00e2\u0080\u00a2 Improve integration between vim-shell & vim-session:\n   http:\/\/github.com\/xolox\/vim-session\/commit\/b2cdcaf","3":" \u00e2\u0080\u00a2 Persist Vim's verbosity (makes it easier to debug :RestartVim :-):\n   http:\/\/github.com\/xolox\/vim-session\/commit\/62410ba\n\n \u00e2\u0080\u00a2 Improve integration between vim-shell & vim-session:\n   http:\/\/github.com\/xolox\/vim-session\/commit\/b2cdcaf","package":"session.zip","4":"session.zip","src_id":"20210","5":"20210","creation_date":"1369501408","6":"1369501408"},{"0":"3150","vim_version":"7.0","1":"7.0","script_version":"2.3.5","2":"2.3.5","version_comment":" \u00e2\u0080\u00a2 Document vim-misc as external dependency (needs to be installed separately from now on):\n   http:\/\/github.com\/xolox\/vim-session\/commit\/f97fc05\n\n \u00e2\u0080\u00a2 Bug fix for :RestartVim on Windows (fixed quoting):\n   http:\/\/github.com\/xolox\/vim-session\/commit\/b69e9ae","3":" \u00e2\u0080\u00a2 Document vim-misc as external dependency (needs to be installed separately from now on):\n   http:\/\/github.com\/xolox\/vim-session\/commit\/f97fc05\n\n \u00e2\u0080\u00a2 Bug fix for :RestartVim on Windows (fixed quoting):\n   http:\/\/github.com\/xolox\/vim-session\/commit\/b69e9ae","package":"session.zip","4":"session.zip","src_id":"20206","5":"20206","creation_date":"1369487266","6":"1369487266"},{"0":"3150","vim_version":"7.0","1":"7.0","script_version":"2.3.4","2":"2.3.4","version_comment":" \u00e2\u0080\u00a2 Determine tab \/ global scope from sourced session, not the config (contributed by Ingo Karkat):\n   http:\/\/github.com\/xolox\/vim-session\/commit\/982be75\n   http:\/\/github.com\/xolox\/vim-session\/commit\/359575c","3":" \u00e2\u0080\u00a2 Determine tab \/ global scope from sourced session, not the config (contributed by Ingo Karkat):\n   http:\/\/github.com\/xolox\/vim-session\/commit\/982be75\n   http:\/\/github.com\/xolox\/vim-session\/commit\/359575c","package":"session.zip","4":"session.zip","src_id":"20200","5":"20200","creation_date":"1369349838","6":"1369349838"},{"0":"3150","vim_version":"7.0","1":"7.0","script_version":"2.3.2","2":"2.3.2","version_comment":" \u00e2\u0080\u00a2 Updated miscellaneous scripts:\n   http:\/\/github.com\/xolox\/vim-session\/commit\/5ad0d15","3":" \u00e2\u0080\u00a2 Updated miscellaneous scripts:\n   http:\/\/github.com\/xolox\/vim-session\/commit\/5ad0d15","package":"session.zip","4":"session.zip","src_id":"20184","5":"20184","creation_date":"1369054579","6":"1369054579"},{"0":"3150","vim_version":"7.0","1":"7.0","script_version":"2.3.1","2":"2.3.1","version_comment":" \u00e2\u0080\u00a2 Updated miscellaneous scripts:\n   http:\/\/github.com\/xolox\/vim-session\/commit\/f1cb34e","3":" \u00e2\u0080\u00a2 Updated miscellaneous scripts:\n   http:\/\/github.com\/xolox\/vim-session\/commit\/f1cb34e","package":"session.zip","4":"session.zip","src_id":"20172","5":"20172","creation_date":"1369003441","6":"1369003441"},{"0":"3150","vim_version":"7.0","1":"7.0","script_version":"2.3","2":"2.3","version_comment":" \u00e2\u0080\u00a2 Bug fix for automatic, periodic session saving:\n   http:\/\/github.com\/xolox\/vim-session\/commit\/45c1525\n\n \u00e2\u0080\u00a2 Updated miscellaneous scripts:\n   http:\/\/github.com\/xolox\/vim-session\/commit\/05c4188\n   http:\/\/github.com\/xolox\/vim-session\/commit\/9c88b0e","3":" \u00e2\u0080\u00a2 Bug fix for automatic, periodic session saving:\n   http:\/\/github.com\/xolox\/vim-session\/commit\/45c1525\n\n \u00e2\u0080\u00a2 Updated miscellaneous scripts:\n   http:\/\/github.com\/xolox\/vim-session\/commit\/05c4188\n   http:\/\/github.com\/xolox\/vim-session\/commit\/9c88b0e","package":"session.zip","4":"session.zip","src_id":"20127","5":"20127","creation_date":"1368482218","6":"1368482218"},{"0":"3150","vim_version":"7.0","1":"7.0","script_version":"2.2","2":"2.2","version_comment":" \u00e2\u0080\u00a2 Support for Conque Shell (suggested by Colin Wood):\n   http:\/\/github.com\/xolox\/vim-session\/commit\/4552274","3":" \u00e2\u0080\u00a2 Support for Conque Shell (suggested by Colin Wood):\n   http:\/\/github.com\/xolox\/vim-session\/commit\/4552274","package":"session.zip","4":"session.zip","src_id":"20102","5":"20102","creation_date":"1368388969","6":"1368388969"},{"0":"3150","vim_version":"7.0","1":"7.0","script_version":"2.1","2":"2.1","version_comment":" \u00e2\u0080\u00a2 Define menu items for commands defined by plug-in (suggested by Sergiy Borodych):\n   http:\/\/github.com\/xolox\/vim-session\/commit\/ad6feb7","3":" \u00e2\u0080\u00a2 Define menu items for commands defined by plug-in (suggested by Sergiy Borodych):\n   http:\/\/github.com\/xolox\/vim-session\/commit\/ad6feb7","package":"session.zip","4":"session.zip","src_id":"20101","5":"20101","creation_date":"1368384292","6":"1368384292"},{"0":"3150","vim_version":"7.0","1":"7.0","script_version":"2.0","2":"2.0","version_comment":" \u00e2\u0080\u00a2 Support for tab scoped sessions (large contributions by Ingo Karkat):\n   http:\/\/github.com\/xolox\/vim-session\/commit\/702d22c","3":" \u00e2\u0080\u00a2 Support for tab scoped sessions (large contributions by Ingo Karkat):\n   http:\/\/github.com\/xolox\/vim-session\/commit\/702d22c","package":"session.zip","4":"session.zip","src_id":"20027","5":"20027","creation_date":"1367800339","6":"1367800339"},{"0":"3150","vim_version":"7.0","1":"7.0","script_version":"1.8","2":"1.8","version_comment":" \u00e2\u0080\u00a2 Option to automatically save sessions every few minutes:\n   http:\/\/github.com\/xolox\/vim-session\/commit\/96e547e","3":" \u00e2\u0080\u00a2 Option to automatically save sessions every few minutes:\n   http:\/\/github.com\/xolox\/vim-session\/commit\/96e547e","package":"session.zip","4":"session.zip","src_id":"20024","5":"20024","creation_date":"1367781323","6":"1367781323"},{"0":"3150","vim_version":"7.0","1":"7.0","script_version":"1.7.3","2":"1.7.3","version_comment":" \u00e2\u0080\u00a2 Bug fix: Make auto-load work when 'viminfo' contains '%' (reported by Diego Mesa)\n   http:\/\/github.com\/xolox\/vim-session\/commit\/166f1f7","3":" \u00e2\u0080\u00a2 Bug fix: Make auto-load work when 'viminfo' contains '%' (reported by Diego Mesa)\n   http:\/\/github.com\/xolox\/vim-session\/commit\/166f1f7","package":"session.zip","4":"session.zip","src_id":"20017","5":"20017","creation_date":"1367627583","6":"1367627583"},{"0":"3150","vim_version":"7.0","1":"7.0","script_version":"1.7.2","2":"1.7.2","version_comment":" \u00e2\u0080\u00a2 Make it easier to save a session for the 1st time (issues #19, #25):\n   http:\/\/github.com\/xolox\/vim-session\/commit\/8cc18f0","3":" \u00e2\u0080\u00a2 Make it easier to save a session for the 1st time (issues #19, #25):\n   http:\/\/github.com\/xolox\/vim-session\/commit\/8cc18f0","package":"session.zip","4":"session.zip","src_id":"20016","5":"20016","creation_date":"1367619630","6":"1367619630"},{"0":"3150","vim_version":"7.0","1":"7.0","script_version":"1.7.1","2":"1.7.1","version_comment":" \u00e2\u0080\u00a2 Bug fix: E121: Undefined variable: a:var (reported by Ivan Kuznetsov):\n   http:\/\/github.com\/xolox\/vim-session\/commit\/7d2a45c","3":" \u00e2\u0080\u00a2 Bug fix: E121: Undefined variable: a:var (reported by Ivan Kuznetsov):\n   http:\/\/github.com\/xolox\/vim-session\/commit\/7d2a45c","package":"session.zip","4":"session.zip","src_id":"20014","5":"20014","creation_date":"1367601843","6":"1367601843"},{"0":"3150","vim_version":"7.0","1":"7.0","script_version":"1.7","2":"1.7","version_comment":" \u00e2\u0080\u00a2 Enable non-verbose interactive prompts (suggested by Ingo Karkat):\n   http:\/\/github.com\/xolox\/vim-session\/commit\/c9fa3e2\n\n \u00e2\u0080\u00a2 Make it possible to forget the last used session (suggested by Ingo Karkat):\n   http:\/\/github.com\/xolox\/vim-session\/commit\/037d0ba","3":" \u00e2\u0080\u00a2 Enable non-verbose interactive prompts (suggested by Ingo Karkat):\n   http:\/\/github.com\/xolox\/vim-session\/commit\/c9fa3e2\n\n \u00e2\u0080\u00a2 Make it possible to forget the last used session (suggested by Ingo Karkat):\n   http:\/\/github.com\/xolox\/vim-session\/commit\/037d0ba","package":"session.zip","4":"session.zip","src_id":"20013","5":"20013","creation_date":"1367530601","6":"1367530601"},{"0":"3150","vim_version":"7.0","1":"7.0","script_version":"1.6.3","2":"1.6.3","version_comment":" \u00e2\u0080\u00a2 Make :RestartVim work on Mac OS X:\n   http:\/\/github.com\/xolox\/vim-session\/commit\/165ece4","3":" \u00e2\u0080\u00a2 Make :RestartVim work on Mac OS X:\n   http:\/\/github.com\/xolox\/vim-session\/commit\/165ece4","package":"session.zip","4":"session.zip","src_id":"20002","5":"20002","creation_date":"1367455025","6":"1367455025"},{"0":"3150","vim_version":"7.0","1":"7.0","script_version":"1.6.2","2":"1.6.2","version_comment":" \u00e2\u0080\u00a2 Option to set session filename extension:\n   http:\/\/github.com\/xolox\/vim-session\/commit\/b892cca","3":" \u00e2\u0080\u00a2 Option to set session filename extension:\n   http:\/\/github.com\/xolox\/vim-session\/commit\/b892cca","package":"session.zip","4":"session.zip","src_id":"20001","5":"20001","creation_date":"1367452559","6":"1367452559"},{"0":"3150","vim_version":"7.0","1":"7.0","script_version":"1.6.1","2":"1.6.1","version_comment":" \u00e2\u0080\u00a2 Option to set default session name (issue #22):\n   http:\/\/github.com\/xolox\/vim-session\/commit\/6a4af75","3":" \u00e2\u0080\u00a2 Option to set default session name (issue #22):\n   http:\/\/github.com\/xolox\/vim-session\/commit\/6a4af75","package":"session.zip","4":"session.zip","src_id":"20000","5":"20000","creation_date":"1367452211","6":"1367452211"},{"0":"3150","vim_version":"7.0","1":"7.0","script_version":"1.6","2":"1.6","version_comment":" \u00e2\u0080\u00a2 Bug fix: Release session lock before launching new instance (:RestartVim):\n   http:\/\/github.com\/xolox\/vim-session\/commit\/64f3cac\n\n \u00e2\u0080\u00a2 Expand environment variables in command arguments (issue #20):\n   http:\/\/github.com\/xolox\/vim-session\/commit\/d0a3940","3":" \u00e2\u0080\u00a2 Bug fix: Release session lock before launching new instance (:RestartVim):\n   http:\/\/github.com\/xolox\/vim-session\/commit\/64f3cac\n\n \u00e2\u0080\u00a2 Expand environment variables in command arguments (issue #20):\n   http:\/\/github.com\/xolox\/vim-session\/commit\/d0a3940","package":"session.zip","4":"session.zip","src_id":"19999","5":"19999","creation_date":"1367451644","6":"1367451644"},{"0":"3150","vim_version":"7.0","1":"7.0","script_version":"1.5.11","2":"1.5.11","version_comment":" \u00e2\u0080\u00a2 Updated miscellaneous scripts:\n   http:\/\/github.com\/xolox\/vim-session\/commit\/66e75f6","3":" \u00e2\u0080\u00a2 Updated miscellaneous scripts:\n   http:\/\/github.com\/xolox\/vim-session\/commit\/66e75f6","package":"session.zip","4":"session.zip","src_id":"19961","5":"19961","creation_date":"1367159598","6":"1367159598"},{"0":"3150","vim_version":"7.0","1":"7.0","script_version":"1.5.10","2":"1.5.10","version_comment":" \u00e2\u0080\u00a2 Handle :normal! fold restore in session file (contributed by Ingo Karkat):\n   http:\/\/github.com\/xolox\/vim-session\/commit\/597de09","3":" \u00e2\u0080\u00a2 Handle :normal! fold restore in session file (contributed by Ingo Karkat):\n   http:\/\/github.com\/xolox\/vim-session\/commit\/597de09","package":"session.zip","4":"session.zip","src_id":"19880","5":"19880","creation_date":"1366535880","6":"1366535880"},{"0":"3150","vim_version":"7.0","1":"7.0","script_version":"1.5.9","2":"1.5.9","version_comment":" \u00e2\u0080\u00a2 Invoke autoload functions instead of custom commands (contributed by Ingo Karkat):\n   http:\/\/github.com\/xolox\/vim-session\/commit\/b6b6d7f","3":" \u00e2\u0080\u00a2 Invoke autoload functions instead of custom commands (contributed by Ingo Karkat):\n   http:\/\/github.com\/xolox\/vim-session\/commit\/b6b6d7f","package":"session.zip","4":"session.zip","src_id":"19879","5":"19879","creation_date":"1366534298","6":"1366534298"},{"0":"3150","vim_version":"7.0","1":"7.0","script_version":"1.5.8","2":"1.5.8","version_comment":" \u00e2\u0080\u00a2 Avoid mandatory persistence of Vim size.:\n   http:\/\/github.com\/xolox\/vim-session\/commit\/1707199\n\n \u00e2\u0080\u00a2 Skip \"save changes?\" prompt when reopening sessions:\n   http:\/\/github.com\/xolox\/vim-session\/commit\/2f22b53\n\n \u00e2\u0080\u00a2 Merge pull request #32:\n   http:\/\/github.com\/xolox\/vim-session\/commit\/e24a284\n\n \u00e2\u0080\u00a2 Make compatibility with miscellaneous scripts explicit:\n   http:\/\/github.com\/xolox\/vim-session\/commit\/d405393","3":" \u00e2\u0080\u00a2 Avoid mandatory persistence of Vim size.:\n   http:\/\/github.com\/xolox\/vim-session\/commit\/1707199\n\n \u00e2\u0080\u00a2 Skip \"save changes?\" prompt when reopening sessions:\n   http:\/\/github.com\/xolox\/vim-session\/commit\/2f22b53\n\n \u00e2\u0080\u00a2 Merge pull request #32:\n   http:\/\/github.com\/xolox\/vim-session\/commit\/e24a284\n\n \u00e2\u0080\u00a2 Make compatibility with miscellaneous scripts explicit:\n   http:\/\/github.com\/xolox\/vim-session\/commit\/d405393","package":"session.zip","4":"session.zip","src_id":"19876","5":"19876","creation_date":"1366504632","6":"1366504632"},{"0":"3150","vim_version":"7.0","1":"7.0","script_version":"1.5.5","2":"1.5.5","version_comment":" \u00e2\u0080\u00a2 Remove dirty session tracking; it's too fragile (contributed by Matthew Torok):\n   http:\/\/github.com\/xolox\/vim-session\/commit\/5d79e44\n\n \u00e2\u0080\u00a2 Bug fix: Don't fire SessionLoadPost event until session is fully loaded  (contributed by Matthew Torok):\n   http:\/\/github.com\/xolox\/vim-session\/commit\/db3f793\n\n \u00e2\u0080\u00a2 Bug fix: On session restore, maintain cwd after loading NERDTree (contributed by Matthew Torok)\n   http:\/\/github.com\/xolox\/vim-session\/commit\/d9ecc6a","3":" \u00e2\u0080\u00a2 Remove dirty session tracking; it's too fragile (contributed by Matthew Torok):\n   http:\/\/github.com\/xolox\/vim-session\/commit\/5d79e44\n\n \u00e2\u0080\u00a2 Bug fix: Don't fire SessionLoadPost event until session is fully loaded  (contributed by Matthew Torok):\n   http:\/\/github.com\/xolox\/vim-session\/commit\/db3f793\n\n \u00e2\u0080\u00a2 Bug fix: On session restore, maintain cwd after loading NERDTree (contributed by Matthew Torok)\n   http:\/\/github.com\/xolox\/vim-session\/commit\/d9ecc6a","package":"session.zip","4":"session.zip","src_id":"19866","5":"19866","creation_date":"1366457853","6":"1366457853"},{"0":"3150","vim_version":"7.0","1":"7.0","script_version":"1.5.2","2":"1.5.2","version_comment":" \u00e2\u0080\u00a2 Bug fix: Disable :argglobal\/:argument commands just like :args:\n   http:\/\/github.com\/xolox\/vim-session\/commit\/e365e75","3":" \u00e2\u0080\u00a2 Bug fix: Disable :argglobal\/:argument commands just like :args:\n   http:\/\/github.com\/xolox\/vim-session\/commit\/e365e75","package":"session.zip","4":"session.zip","src_id":"19856","5":"19856","creation_date":"1366320817","6":"1366320817"},{"0":"3150","vim_version":"7.0","1":"7.0","script_version":"1.5.1","2":"1.5.1","version_comment":" \u00e2\u0080\u00a2 Bug fix: Strip :args from :mksession output:\n   http:\/\/github.com\/xolox\/vim-session\/commit\/66cbbb4","3":" \u00e2\u0080\u00a2 Bug fix: Strip :args from :mksession output:\n   http:\/\/github.com\/xolox\/vim-session\/commit\/66cbbb4","package":"session.zip","4":"session.zip","src_id":"19839","5":"19839","creation_date":"1366235641","6":"1366235641"},{"0":"3150","vim_version":"7.0","1":"7.0","script_version":"1.5","2":"1.5","version_comment":" \u00e2\u0080\u00a2 Support for BufExplorer windows:\n   http:\/\/github.com\/xolox\/vim-session\/commit\/ca2e72f","3":" \u00e2\u0080\u00a2 Support for BufExplorer windows:\n   http:\/\/github.com\/xolox\/vim-session\/commit\/ca2e72f","package":"session.zip","4":"session.zip","src_id":"17211","5":"17211","creation_date":"1326592018","6":"1326592018"},{"0":"3150","vim_version":"7.0","1":"7.0","script_version":"1.4.25","2":"1.4.25","version_comment":" \u00e2\u0080\u00a2 New g:session_command_aliases option (issue #11):\n   http:\/\/github.com\/xolox\/vim-session\/commit\/5d26cab","3":" \u00e2\u0080\u00a2 New g:session_command_aliases option (issue #11):\n   http:\/\/github.com\/xolox\/vim-session\/commit\/5d26cab","package":"session.zip","4":"session.zip","src_id":"17055","5":"17055","creation_date":"1323615784","6":"1323615784"},{"0":"3150","vim_version":"7.0","1":"7.0","script_version":"1.4.24","2":"1.4.24","version_comment":" \u00e2\u0080\u00a2 Updated miscellaneous scripts:\n   http:\/\/github.com\/xolox\/vim-session\/commit\/1a9e32a\n   http:\/\/github.com\/xolox\/vim-session\/commit\/11d7575\n   http:\/\/github.com\/xolox\/vim-session\/commit\/9b4c774","3":" \u00e2\u0080\u00a2 Updated miscellaneous scripts:\n   http:\/\/github.com\/xolox\/vim-session\/commit\/1a9e32a\n   http:\/\/github.com\/xolox\/vim-session\/commit\/11d7575\n   http:\/\/github.com\/xolox\/vim-session\/commit\/9b4c774","package":"session.zip","4":"session.zip","src_id":"16973","5":"16973","creation_date":"1322268130","6":"1322268130"},{"0":"3150","vim_version":"7.0","1":"7.0","script_version":"1.4.23","2":"1.4.23","version_comment":" \u00e2\u0080\u00a2 Work around &shellslash setting on Windows:\n   http:\/\/github.com\/xolox\/vim-session\/commit\/02babeb","3":" \u00e2\u0080\u00a2 Work around &shellslash setting on Windows:\n   http:\/\/github.com\/xolox\/vim-session\/commit\/02babeb","package":"session.zip","4":"session.zip","src_id":"16929","5":"16929","creation_date":"1321911440","6":"1321911440"},{"0":"3150","vim_version":"7.0","1":"7.0","script_version":"1.4.22","2":"1.4.22","version_comment":" \u00e2\u0080\u00a2 Documentation bug fix for previous commit:\n   http:\/\/github.com\/xolox\/vim-session\/commit\/6b0595a","3":" \u00e2\u0080\u00a2 Documentation bug fix for previous commit:\n   http:\/\/github.com\/xolox\/vim-session\/commit\/6b0595a","package":"session.zip","4":"session.zip","src_id":"16874","5":"16874","creation_date":"1321391737","6":"1321391737"},{"0":"3150","vim_version":"7.0","1":"7.0","script_version":"1.4.21","2":"1.4.21","version_comment":" \u00e2\u0080\u00a2 New 'session_persist_globals' option (requested by Roman Byshko):\n   http:\/\/github.com\/xolox\/vim-session\/commit\/ff71e04","3":" \u00e2\u0080\u00a2 New 'session_persist_globals' option (requested by Roman Byshko):\n   http:\/\/github.com\/xolox\/vim-session\/commit\/ff71e04","package":"session.zip","4":"session.zip","src_id":"16853","5":"16853","creation_date":"1321033699","6":"1321033699"},{"0":"3150","vim_version":"7.0","1":"7.0","script_version":"1.4.20","2":"1.4.20","version_comment":" \u00e2\u0080\u00a2 Mark session dirty when buffer list changes:\n   http:\/\/github.com\/xolox\/vim-session\/commit\/1ed64d2\n\n \u00e2\u0080\u00a2 Make :RestartVim preserve $VIM and $VIMRUNTIME:\n   http:\/\/github.com\/xolox\/vim-session\/commit\/f56fe44","3":" \u00e2\u0080\u00a2 Mark session dirty when buffer list changes:\n   http:\/\/github.com\/xolox\/vim-session\/commit\/1ed64d2\n\n \u00e2\u0080\u00a2 Make :RestartVim preserve $VIM and $VIMRUNTIME:\n   http:\/\/github.com\/xolox\/vim-session\/commit\/f56fe44","package":"session.zip","4":"session.zip","src_id":"16611","5":"16611","creation_date":"1317502626","6":"1317502626"},{"0":"3150","vim_version":"7.0","1":"7.0","script_version":"1.4.18","2":"1.4.18","version_comment":" \u00e2\u0080\u00a2 Updated miscellaneous scripts:\n   http:\/\/github.com\/xolox\/vim-session\/commit\/f9888a1","3":" \u00e2\u0080\u00a2 Updated miscellaneous scripts:\n   http:\/\/github.com\/xolox\/vim-session\/commit\/f9888a1","package":"session.zip","4":"session.zip","src_id":"16583","5":"16583","creation_date":"1316994860","6":"1316994860"},{"0":"3150","vim_version":"7.0","1":"7.0","script_version":"1.4.17","2":"1.4.17","version_comment":" \u00e2\u0080\u00a2 Silence \"E95: Buffer with this name already exist\" messages:\n   http:\/\/github.com\/xolox\/vim-session\/commit\/f061ad9","3":" \u00e2\u0080\u00a2 Silence \"E95: Buffer with this name already exist\" messages:\n   http:\/\/github.com\/xolox\/vim-session\/commit\/f061ad9","package":"session.zip","4":"session.zip","src_id":"16558","5":"16558","creation_date":"1316548282","6":"1316548282"},{"0":"3150","vim_version":"7.0","1":"7.0","script_version":"1.4.16","2":"1.4.16","version_comment":" \u00e2\u0080\u00a2 Improve support for special windows, specifically NERDTree:\n   http:\/\/github.com\/xolox\/vim-session\/commit\/5a4db7c\n\n \u00e2\u0080\u00a2 Separate persistence of &background vs. :colorscheme:\n   http:\/\/github.com\/xolox\/vim-session\/commit\/363c40d","3":" \u00e2\u0080\u00a2 Improve support for special windows, specifically NERDTree:\n   http:\/\/github.com\/xolox\/vim-session\/commit\/5a4db7c\n\n \u00e2\u0080\u00a2 Separate persistence of &background vs. :colorscheme:\n   http:\/\/github.com\/xolox\/vim-session\/commit\/363c40d","package":"session.zip","4":"session.zip","src_id":"16547","5":"16547","creation_date":"1316305477","6":"1316305477"},{"0":"3150","vim_version":"7.0","1":"7.0","script_version":"1.4.14","2":"1.4.14","version_comment":" \u00e2\u0080\u00a2 Support for mirrored NERDTree windows (requested by Sebastian Tramp):\n   http:\/\/github.com\/xolox\/vim-session\/commit\/fe58d29","3":" \u00e2\u0080\u00a2 Support for mirrored NERDTree windows (requested by Sebastian Tramp):\n   http:\/\/github.com\/xolox\/vim-session\/commit\/fe58d29","package":"session.zip","4":"session.zip","src_id":"16544","5":"16544","creation_date":"1316297199","6":"1316297199"},{"0":"3150","vim_version":"7.0","1":"7.0","script_version":"1.4.13","2":"1.4.13","version_comment":" \u00e2\u0080\u00a2 Switch order of :colorscheme, :set background= commands:\n   http:\/\/github.com\/xolox\/vim-session\/commit\/a3ba9f6","3":" \u00e2\u0080\u00a2 Switch order of :colorscheme, :set background= commands:\n   http:\/\/github.com\/xolox\/vim-session\/commit\/a3ba9f6","package":"session.zip","4":"session.zip","src_id":"16542","5":"16542","creation_date":"1316295631","6":"1316295631"},{"0":"3150","vim_version":"7.0","1":"7.0","script_version":"1.4.12","2":"1.4.12","version_comment":" \u00e2\u0080\u00a2 Updated miscellaneous scripts:\n   http:\/\/github.com\/xolox\/vim-session\/commit\/cbb9a3b","3":" \u00e2\u0080\u00a2 Updated miscellaneous scripts:\n   http:\/\/github.com\/xolox\/vim-session\/commit\/cbb9a3b","package":"session.zip","4":"session.zip","src_id":"16461","5":"16461","creation_date":"1315145421","6":"1315145421"},{"0":"3150","vim_version":"7.0","1":"7.0","script_version":"1.4.11","2":"1.4.11","version_comment":" \u00e2\u0080\u00a2 Version bump because of miscellaneous scripts:\n   http:\/\/github.com\/xolox\/vim-session\/commit\/4c09a02\n   http:\/\/github.com\/xolox\/vim-session\/commit\/96e63ff","3":" \u00e2\u0080\u00a2 Version bump because of miscellaneous scripts:\n   http:\/\/github.com\/xolox\/vim-session\/commit\/4c09a02\n   http:\/\/github.com\/xolox\/vim-session\/commit\/96e63ff","package":"session.zip","4":"session.zip","src_id":"16419","5":"16419","creation_date":"1314826795","6":"1314826795"},{"0":"3150","vim_version":"7.0","1":"7.0","script_version":"1.4.10","2":"1.4.10","version_comment":" \u00e2\u0080\u00a2 Move version variable to autoload script:\n   http:\/\/github.com\/xolox\/vim-session\/commit\/93d504a\n\n \u00e2\u0080\u00a2 Updated miscellaneous scripts (https:\/\/github.com\/xolox\/vim-misc):\n   http:\/\/github.com\/xolox\/vim-session\/commit\/e374c77","3":" \u00e2\u0080\u00a2 Move version variable to autoload script:\n   http:\/\/github.com\/xolox\/vim-session\/commit\/93d504a\n\n \u00e2\u0080\u00a2 Updated miscellaneous scripts (https:\/\/github.com\/xolox\/vim-misc):\n   http:\/\/github.com\/xolox\/vim-session\/commit\/e374c77","package":"session.zip","4":"session.zip","src_id":"16416","5":"16416","creation_date":"1314820055","6":"1314820055"},{"0":"3150","vim_version":"7.0","1":"7.0","script_version":"1.4.9","2":"1.4.9","version_comment":" \u00e2\u0080\u00a2 Define version as variable, include version in messages:\n   http:\/\/github.com\/xolox\/vim-session\/commit\/435786b","3":" \u00e2\u0080\u00a2 Define version as variable, include version in messages:\n   http:\/\/github.com\/xolox\/vim-session\/commit\/435786b","package":"session.zip","4":"session.zip","src_id":"15923","5":"15923","creation_date":"1308361031","6":"1308361031"},{"0":"3150","vim_version":"7.0","1":"7.0","script_version":"1.4.8","2":"1.4.8","version_comment":" \u00e2\u0080\u00a2 Bug fix: Don't hang during :RestartVim when &verbose >= 1:\n   http:\/\/github.com\/xolox\/vim-session\/commit\/1f9c911","3":" \u00e2\u0080\u00a2 Bug fix: Don't hang during :RestartVim when &verbose >= 1:\n   http:\/\/github.com\/xolox\/vim-session\/commit\/1f9c911","package":"session.zip","4":"session.zip","src_id":"15875","5":"15875","creation_date":"1307999017","6":"1307999017"},{"0":"3150","vim_version":"7.0","1":"7.0","script_version":"1.4.7","2":"1.4.7","version_comment":" \u00e2\u0080\u00a2 Ignore \"No fold found\" errors:\n   http:\/\/github.com\/xolox\/vim-session\/commit\/13d405d","3":" \u00e2\u0080\u00a2 Ignore \"No fold found\" errors:\n   http:\/\/github.com\/xolox\/vim-session\/commit\/13d405d","package":"session.zip","4":"session.zip","src_id":"15861","5":"15861","creation_date":"1307908198","6":"1307908198"},{"0":"3150","vim_version":"7.0","1":"7.0","script_version":"1.4.6","2":"1.4.6","version_comment":" \u00e2\u0080\u00a2 Ignore missing fonts (reported by SteP):\r\n   http:\/\/github.com\/xolox\/vim-session\/commit\/d9af5b1","3":" \u00e2\u0080\u00a2 Ignore missing fonts (reported by SteP):\r\n   http:\/\/github.com\/xolox\/vim-session\/commit\/d9af5b1","package":"session.zip","4":"session.zip","src_id":"15803","5":"15803","creation_date":"1307140842","6":"1307140842"},{"0":"3150","vim_version":"7.0","1":"7.0","script_version":"1.4.5","2":"1.4.5","version_comment":" \u00e2\u0080\u00a2 Make it possible to disable automatic loading\/saving (suggested by Tommi Kivel\u00c3\u00a4):\r\n   http:\/\/github.com\/xolox\/vim-session\/commit\/28a1eaf","3":" \u00e2\u0080\u00a2 Make it possible to disable automatic loading\/saving (suggested by Tommi Kivel\u00c3\u00a4):\r\n   http:\/\/github.com\/xolox\/vim-session\/commit\/28a1eaf","package":"session.zip","4":"session.zip","src_id":"15792","5":"15792","creation_date":"1306966756","6":"1306966756"},{"0":"3150","vim_version":"7.0","1":"7.0","script_version":"1.4.4","2":"1.4.4","version_comment":" \u00e2\u0080\u00a2 Restore NERDTree buffer after :CloseSession (thanks to Brandon Martin for bug report \/ feature request :-):\r\n   http:\/\/github.com\/xolox\/vim-session\/commit\/e6a4ff2","3":" \u00e2\u0080\u00a2 Restore NERDTree buffer after :CloseSession (thanks to Brandon Martin for bug report \/ feature request :-):\r\n   http:\/\/github.com\/xolox\/vim-session\/commit\/e6a4ff2","package":"session.zip","4":"session.zip","src_id":"15740","5":"15740","creation_date":"1306447166","6":"1306447166"},{"0":"3150","vim_version":"7.0","1":"7.0","script_version":"1.4.3","2":"1.4.3","version_comment":" \u00e2\u0080\u00a2 Enable opening last used session when starting Vim (thanks to James Cox for suggestion):\r\n   http:\/\/github.com\/xolox\/vim-session\/commit\/6855a81\r\n\r\n \u00e2\u0080\u00a2 Remember the 'background' setting:\r\n   http:\/\/github.com\/xolox\/vim-session\/commit\/3635adb","3":" \u00e2\u0080\u00a2 Enable opening last used session when starting Vim (thanks to James Cox for suggestion):\r\n   http:\/\/github.com\/xolox\/vim-session\/commit\/6855a81\r\n\r\n \u00e2\u0080\u00a2 Remember the 'background' setting:\r\n   http:\/\/github.com\/xolox\/vim-session\/commit\/3635adb","package":"session.zip","4":"session.zip","src_id":"15739","5":"15739","creation_date":"1306442948","6":"1306442948"},{"0":"3150","vim_version":"7.0","1":"7.0","script_version":"1.4","2":"1.4","version_comment":" \u00e2\u0080\u00a2 Make :OpenSession and :CloseSession preserve working directory:\r\n   https:\/\/github.com\/xolox\/vim-session\/commit\/ae7ba3a9e99db2f52c7a\r\n\r\n \u00e2\u0080\u00a2 Make :CloseSession close buffers (or they'll keep piling up):\r\n   https:\/\/github.com\/xolox\/vim-session\/commit\/cab03c308b5dabaa6cd8\r\n\r\nThanks to Brandon Martin for reporting both issues!","3":" \u00e2\u0080\u00a2 Make :OpenSession and :CloseSession preserve working directory:\r\n   https:\/\/github.com\/xolox\/vim-session\/commit\/ae7ba3a9e99db2f52c7a\r\n\r\n \u00e2\u0080\u00a2 Make :CloseSession close buffers (or they'll keep piling up):\r\n   https:\/\/github.com\/xolox\/vim-session\/commit\/cab03c308b5dabaa6cd8\r\n\r\nThanks to Brandon Martin for reporting both issues!","package":"session.zip","4":"session.zip","src_id":"15630","5":"15630","creation_date":"1305231009","6":"1305231009"},{"0":"3150","vim_version":"7.0","1":"7.0","script_version":"1.3.8","2":"1.3.8","version_comment":" \u00e2\u0080\u00a2 The plug-in will now try to restore quick-fix windows:\r\n   https:\/\/github.com\/xolox\/vim-session\/commit\/46962c2c87236ea02b67\r\n\r\n \u00e2\u0080\u00a2 I've instrumented the :OpenSession \/ :SaveSession commands so that they'll print their execution time when &verbose >= 1:\r\n   https:\/\/github.com\/xolox\/vim-session\/commit\/dba3f0c493fb10b19d6f\r\n\r\n \u00e2\u0080\u00a2 Support for special windows has been simplified:\r\n   https:\/\/github.com\/xolox\/vim-session\/commit\/196fda1ad95c5a350510","3":" \u00e2\u0080\u00a2 The plug-in will now try to restore quick-fix windows:\r\n   https:\/\/github.com\/xolox\/vim-session\/commit\/46962c2c87236ea02b67\r\n\r\n \u00e2\u0080\u00a2 I've instrumented the :OpenSession \/ :SaveSession commands so that they'll print their execution time when &verbose >= 1:\r\n   https:\/\/github.com\/xolox\/vim-session\/commit\/dba3f0c493fb10b19d6f\r\n\r\n \u00e2\u0080\u00a2 Support for special windows has been simplified:\r\n   https:\/\/github.com\/xolox\/vim-session\/commit\/196fda1ad95c5a350510","package":"session.zip","4":"session.zip","src_id":"14614","5":"14614","creation_date":"1293243255","6":"1293243255"},{"0":"3150","vim_version":"7.0","1":"7.0","script_version":"1.3.5","2":"1.3.5","version_comment":" \u00e2\u0080\u00a2 Restore compatibility with netrw buffers:\r\n   https:\/\/github.com\/xolox\/vim-session\/commit\/54f2f388962ad7c288f2\r\n\r\n \u00e2\u0080\u00a2 Persist window size for plug-in windows:\r\n   https:\/\/github.com\/xolox\/vim-session\/commit\/8bf201e5c73a33ff1626\r\n\r\n \u00e2\u0080\u00a2 Remove duplicate code and fnameescape() bug \r\n   https:\/\/github.com\/xolox\/vim-session\/commit\/309dc4b2f90586fa54fc","3":" \u00e2\u0080\u00a2 Restore compatibility with netrw buffers:\r\n   https:\/\/github.com\/xolox\/vim-session\/commit\/54f2f388962ad7c288f2\r\n\r\n \u00e2\u0080\u00a2 Persist window size for plug-in windows:\r\n   https:\/\/github.com\/xolox\/vim-session\/commit\/8bf201e5c73a33ff1626\r\n\r\n \u00e2\u0080\u00a2 Remove duplicate code and fnameescape() bug \r\n   https:\/\/github.com\/xolox\/vim-session\/commit\/309dc4b2f90586fa54fc","package":"session.zip","4":"session.zip","src_id":"14591","5":"14591","creation_date":"1292886381","6":"1292886381"},{"0":"3150","vim_version":"7.0","1":"7.0","script_version":"1.3.2","2":"1.3.2","version_comment":" \u00e2\u0080\u00a2 Use real script name in messages:\r\n   https:\/\/github.com\/xolox\/vim-session\/commit\/9628d48de4220056aad1\r\n\r\n \u00e2\u0080\u00a2 Improved & documented the :RestartVim command:\r\n   https:\/\/github.com\/xolox\/vim-session\/commit\/86807060e97c4487082f","3":" \u00e2\u0080\u00a2 Use real script name in messages:\r\n   https:\/\/github.com\/xolox\/vim-session\/commit\/9628d48de4220056aad1\r\n\r\n \u00e2\u0080\u00a2 Improved & documented the :RestartVim command:\r\n   https:\/\/github.com\/xolox\/vim-session\/commit\/86807060e97c4487082f","package":"session.zip","4":"session.zip","src_id":"14590","5":"14590","creation_date":"1292876281","6":"1292876281"},{"0":"3150","vim_version":"7.0","1":"7.0","script_version":"1.3","2":"1.3","version_comment":" \u00e2\u0080\u00a2 Bug fix? Unlock deleted sessions:\r\n   http:\/\/github.com\/xolox\/vim-session\/commit\/ca5fe566022303034526c791543cffb218f5faa7\r\n\r\n \u00e2\u0080\u00a2 :ViewSession to quickly view generated Vim scripts:\r\n   http:\/\/github.com\/xolox\/vim-session\/commit\/5cbb45ae5855ab6406a2013c4fabdae5abfb3d51\r\n\r\n \u00e2\u0080\u00a2 Improve command argument handling, avoid double unescaping:\r\n   http:\/\/github.com\/xolox\/vim-session\/commit\/8cc669975b8d8026b1649c899cd3fc37513a8478\r\n\r\n \u00e2\u0080\u00a2 Make Vim on GTK restore &lines and &columns:\r\n   http:\/\/github.com\/xolox\/vim-session\/commit\/6fa62c702173682ca3825e2bcb2fe4d7ffbede7d\r\n\r\n \u00e2\u0080\u00a2 Silence :RestartVim, ignore lock files:\r\n   http:\/\/github.com\/xolox\/vim-session\/commit\/b0631c7a0edbe4b2493637783a9c84225ba05a9e\r\n\r\n \u00e2\u0080\u00a2 Use :mksession instead of reimplementing it, support 'sessionoptions', restore ':Project' windows:\r\n   http:\/\/github.com\/xolox\/vim-session\/commit\/a0475914cff7af83e58325391e933ce77cd23161","3":" \u00e2\u0080\u00a2 Bug fix? Unlock deleted sessions:\r\n   http:\/\/github.com\/xolox\/vim-session\/commit\/ca5fe566022303034526c791543cffb218f5faa7\r\n\r\n \u00e2\u0080\u00a2 :ViewSession to quickly view generated Vim scripts:\r\n   http:\/\/github.com\/xolox\/vim-session\/commit\/5cbb45ae5855ab6406a2013c4fabdae5abfb3d51\r\n\r\n \u00e2\u0080\u00a2 Improve command argument handling, avoid double unescaping:\r\n   http:\/\/github.com\/xolox\/vim-session\/commit\/8cc669975b8d8026b1649c899cd3fc37513a8478\r\n\r\n \u00e2\u0080\u00a2 Make Vim on GTK restore &lines and &columns:\r\n   http:\/\/github.com\/xolox\/vim-session\/commit\/6fa62c702173682ca3825e2bcb2fe4d7ffbede7d\r\n\r\n \u00e2\u0080\u00a2 Silence :RestartVim, ignore lock files:\r\n   http:\/\/github.com\/xolox\/vim-session\/commit\/b0631c7a0edbe4b2493637783a9c84225ba05a9e\r\n\r\n \u00e2\u0080\u00a2 Use :mksession instead of reimplementing it, support 'sessionoptions', restore ':Project' windows:\r\n   http:\/\/github.com\/xolox\/vim-session\/commit\/a0475914cff7af83e58325391e933ce77cd23161","package":"session.zip","4":"session.zip","src_id":"13722","5":"13722","creation_date":"1283145604","6":"1283145604"},{"0":"3150","vim_version":"7.0","1":"7.0","script_version":"1.2.3","2":"1.2.3","version_comment":" \u00e2\u0080\u00a2 Improve compatibility with :mksession by setting g:SessionLoad:\r\n   http:\/\/github.com\/xolox\/vim-session\/commit\/fe61f0170e1a54dd6a87ac3031228370de3c5497\r\n\r\n \u00e2\u0080\u00a2 Vim 7.0 compatibility, :Restart improvement:\r\n   http:\/\/github.com\/xolox\/vim-session\/commit\/c02815d6505d520ebf76471c0605a2d120f69899","3":" \u00e2\u0080\u00a2 Improve compatibility with :mksession by setting g:SessionLoad:\r\n   http:\/\/github.com\/xolox\/vim-session\/commit\/fe61f0170e1a54dd6a87ac3031228370de3c5497\r\n\r\n \u00e2\u0080\u00a2 Vim 7.0 compatibility, :Restart improvement:\r\n   http:\/\/github.com\/xolox\/vim-session\/commit\/c02815d6505d520ebf76471c0605a2d120f69899","package":"session.zip","4":"session.zip","src_id":"13625","5":"13625","creation_date":"1282215351","6":"1282215351"},{"0":"3150","vim_version":"7.0","1":"7.0","script_version":"1.2.2","2":"1.2.2","version_comment":" \u00e2\u0080\u00a2 Enable user defined SwapExists autocmd using <nested> keyword:\r\n   http:\/\/github.com\/xolox\/vim-session\/commit\/0341c020336174460455719be50049caaceea3d2\r\n\r\n \u00e2\u0080\u00a2 Experimental :RestartVim command (to be documented):\r\n   http:\/\/github.com\/xolox\/vim-session\/commit\/ec2ead371fb6e77a31c6b8dcbc151f290d3b07fc\r\n\r\n \u00e2\u0080\u00a2 Experimental support for buffer list persistence:\r\n   http:\/\/github.com\/xolox\/vim-session\/commit\/6ad9516c3aba9b7cfa04c9233d4bb7ff3e2e48f8","3":" \u00e2\u0080\u00a2 Enable user defined SwapExists autocmd using <nested> keyword:\r\n   http:\/\/github.com\/xolox\/vim-session\/commit\/0341c020336174460455719be50049caaceea3d2\r\n\r\n \u00e2\u0080\u00a2 Experimental :RestartVim command (to be documented):\r\n   http:\/\/github.com\/xolox\/vim-session\/commit\/ec2ead371fb6e77a31c6b8dcbc151f290d3b07fc\r\n\r\n \u00e2\u0080\u00a2 Experimental support for buffer list persistence:\r\n   http:\/\/github.com\/xolox\/vim-session\/commit\/6ad9516c3aba9b7cfa04c9233d4bb7ff3e2e48f8","package":"session.zip","4":"session.zip","src_id":"13439","5":"13439","creation_date":"1280504694","6":"1280504694"},{"0":"3150","vim_version":"7.0","1":"7.0","script_version":"1.2.1","2":"1.2.1","version_comment":" \u00e2\u0080\u00a2 Plug-in doesn't prompt on --servername anymore, that was before lock files:\r\n   http:\/\/github.com\/xolox\/vim-session\/commit\/765e9312dbb7909783cd3f096ad42aae3859b412\r\n\r\n \u00e2\u0080\u00a2 The default session isn't automatically deleted anymore, that was an ugly hack before lock files were used!\r\n \u00e2\u0080\u00a2 Finished description of g:session_autosave option :-s\r\n \u00e2\u0080\u00a2 Documented the :DeleteSession command.\r\n \u00e2\u0080\u00a2 Documented session locking and the bang workaround.\r\n \u00e2\u0080\u00a2 The :SaveSession command now locks the session after saving.\r\n   http:\/\/github.com\/xolox\/vim-session\/commit\/50ad3662d58bc574a93f5c327f8fab5d0f9c4f5f","3":" \u00e2\u0080\u00a2 Plug-in doesn't prompt on --servername anymore, that was before lock files:\r\n   http:\/\/github.com\/xolox\/vim-session\/commit\/765e9312dbb7909783cd3f096ad42aae3859b412\r\n\r\n \u00e2\u0080\u00a2 The default session isn't automatically deleted anymore, that was an ugly hack before lock files were used!\r\n \u00e2\u0080\u00a2 Finished description of g:session_autosave option :-s\r\n \u00e2\u0080\u00a2 Documented the :DeleteSession command.\r\n \u00e2\u0080\u00a2 Documented session locking and the bang workaround.\r\n \u00e2\u0080\u00a2 The :SaveSession command now locks the session after saving.\r\n   http:\/\/github.com\/xolox\/vim-session\/commit\/50ad3662d58bc574a93f5c327f8fab5d0f9c4f5f","package":"session.zip","4":"session.zip","src_id":"13342","5":"13342","creation_date":"1279286823","6":"1279286823"},{"0":"3150","vim_version":"7.0","1":"7.0","script_version":"1.2","2":"1.2","version_comment":" \u00e2\u0080\u00a2 Added uniform confirmational messages to :commands:\r\n   http:\/\/github.com\/xolox\/vim-session\/commit\/7b31f5ba0c4c3d44afaddf39eed3aa739ae23a63\r\n\r\n \u00e2\u0080\u00a2 Basic support for restoring NERD tree:\r\n   http:\/\/github.com\/xolox\/vim-session\/commit\/7513e54b91477755ff5e615e054b0e2e7f5802e9","3":" \u00e2\u0080\u00a2 Added uniform confirmational messages to :commands:\r\n   http:\/\/github.com\/xolox\/vim-session\/commit\/7b31f5ba0c4c3d44afaddf39eed3aa739ae23a63\r\n\r\n \u00e2\u0080\u00a2 Basic support for restoring NERD tree:\r\n   http:\/\/github.com\/xolox\/vim-session\/commit\/7513e54b91477755ff5e615e054b0e2e7f5802e9","package":"session.zip","4":"session.zip","src_id":"13341","5":"13341","creation_date":"1279279129","6":"1279279129"},{"0":"3150","vim_version":"7.0","1":"7.0","script_version":"1.1.1","2":"1.1.1","version_comment":"Improved documentation, added automatic update support using GLVS plug-in:\r\nhttp:\/\/github.com\/xolox\/vim-session\/commit\/b228b5ad7cff4fcab76a432b340b82f6336a4e6d","3":"Improved documentation, added automatic update support using GLVS plug-in:\r\nhttp:\/\/github.com\/xolox\/vim-session\/commit\/b228b5ad7cff4fcab76a432b340b82f6336a4e6d","package":"session.zip","4":"session.zip","src_id":"13334","5":"13334","creation_date":"1279156555","6":"1279156555"},{"0":"3150","vim_version":"7.0","1":"7.0","script_version":"1.1","2":"1.1","version_comment":"Initial upload","3":"Initial upload","package":"session.zip","4":"session.zip","src_id":"13333","5":"13333","creation_date":"1279156065","6":"1279156065"}]},"3149":{"script_id":"3149","0":"3149","script_name":"Smooth Center","1":"Smooth Center","script_type":"utility","2":"utility","summary":"Smoothly centres display when you press Esc like zz, zt and zb","3":"Smoothly centres display when you press Esc like zz, zt and zb","description":"Normal VIM lets you center the file based on the current cursor position when you press zz, zt and zb.  This is nice but wouldn't it be nicer if this centering took place smoothly, like panning across a scene of a movie.  This script gives you this: Esc, SHIFT-Esc and SHIFT-F1 in Normal mode work like for zz, zt and zb respectively.  You can cancel by re-pressing Esc.   Script correctly accounts for 'scrolloff' setting.  Note: the default updatetime should be lowered to see this or else it will not appear to do anything.  The default is 4000 but I use 650.  There are some glitches in the Center (Normal mode \/ ESC) like the scrolling keeps going back in on itself when there are folds present, and the scrolling tries to continue if you are at the bottom of the buffer.  These do not affect S-Esc \/ S-F1, (zb and zt equivs. respectively) and works ok if there are no folds or you are not at the bottom of the script.  Working on these!! :)","4":"Normal VIM lets you center the file based on the current cursor position when you press zz, zt and zb.  This is nice but wouldn't it be nicer if this centering took place smoothly, like panning across a scene of a movie.  This script gives you this: Esc, SHIFT-Esc and SHIFT-F1 in Normal mode work like for zz, zt and zb respectively.  You can cancel by re-pressing Esc.   Script correctly accounts for 'scrolloff' setting.  Note: the default updatetime should be lowered to see this or else it will not appear to do anything.  The default is 4000 but I use 650.  There are some glitches in the Center (Normal mode \/ ESC) like the scrolling keeps going back in on itself when there are folds present, and the scrolling tries to continue if you are at the bottom of the buffer.  These do not affect S-Esc \/ S-F1, (zb and zt equivs. respectively) and works ok if there are no folds or you are not at the bottom of the script.  Working on these!! :)","install_details":"Paste it in your _vimrc file. Replace obviously if it is already there.  It is obviously marked.    If you see no scrolling happen, do set ut=1000, because sometimes having a low ut makes the timer not work. Speaking of which, you should have this Timer somewhere in your vimrc, because this makes automatic scrolling possible.  http:\/\/www.vim.org\/scripts\/script.php?script_id=3244","5":"Paste it in your _vimrc file. Replace obviously if it is already there.  It is obviously marked.    If you see no scrolling happen, do set ut=1000, because sometimes having a low ut makes the timer not work. Speaking of which, you should have this Timer somewhere in your vimrc, because this makes automatic scrolling possible.  http:\/\/www.vim.org\/scripts\/script.php?script_id=3244","first_name":"Paul","6":"Paul","last_name":"Contreras","7":"Contreras","releases":[{"0":"3149","vim_version":"7.0","1":"7.0","script_version":"1.7","2":"1.7","version_comment":"Made improvements to scroll till cursor is on top and cursor is at bottom cases.  These work very reliably when in folded mode.  The center case is not quite stable but kind of works, there are still some glitches in folded mode and when the buffer is scrolled near the bottom.","3":"Made improvements to scroll till cursor is on top and cursor is at bottom cases.  These work very reliably when in folded mode.  The center case is not quite stable but kind of works, there are still some glitches in folded mode and when the buffer is scrolled near the bottom.","package":"SmoothCenter.vim","4":"SmoothCenter.vim","src_id":"13848","5":"13848","creation_date":"1284744093","6":"1284744093"},{"0":"3149","vim_version":"7.0","1":"7.0","script_version":"1.6","2":"1.6","version_comment":"Had a slight glitch that happened but not always when you did Shift-ESC, the scrolling would just continue. Not sure why but fixed it and checked it so that this does not happen.  Had a bug that caused the continuing of scrolling when line wrapping was on. This gave incorrect readings for the window height so that scrolling would continue.  Fixed this by putting in a check that warns you if wrap is on, and doesn't scroll.","3":"Had a slight glitch that happened but not always when you did Shift-ESC, the scrolling would just continue. Not sure why but fixed it and checked it so that this does not happen.  Had a bug that caused the continuing of scrolling when line wrapping was on. This gave incorrect readings for the window height so that scrolling would continue.  Fixed this by putting in a check that warns you if wrap is on, and doesn't scroll.","package":"SmoothCenter.vim","4":"SmoothCenter.vim","src_id":"13657","5":"13657","creation_date":"1282591972","6":"1282591972"},{"0":"3149","vim_version":"6.0","1":"6.0","script_version":"1.5","2":"1.5","version_comment":"Sorted out some funky messy logic where 'zb' equivalent in normal vim in Smooth Center did not work, if the cursor was parked on the last line. (S-ESC).  Nothing happened.  Obviously fixed it now so that it does.","3":"Sorted out some funky messy logic where 'zb' equivalent in normal vim in Smooth Center did not work, if the cursor was parked on the last line. (S-ESC).  Nothing happened.  Obviously fixed it now so that it does.","package":"SmoothCenter.vim","4":"SmoothCenter.vim","src_id":"13589","5":"13589","creation_date":"1281979553","6":"1281979553"},{"0":"3149","vim_version":"6.0","1":"6.0","script_version":"1.4","2":"1.4","version_comment":"Fixed a subtle bug that meant that if scrolloff>0 the display would keep on centering but not immediately. If you were at the top of bottom having done S-ESC or S-F1 with scrolloff>0 then the display would stop scrolling then, but then later on when you moved off that line the display would keep on trying to scroll. This was to do with where I had attempted to account for the 'scrolloff' value in the centering bit of my code.  Made the command line clear so that you don't see a silly 'call StartSmoothCentering()' at the bottom of the screen each time.","3":"Fixed a subtle bug that meant that if scrolloff>0 the display would keep on centering but not immediately. If you were at the top of bottom having done S-ESC or S-F1 with scrolloff>0 then the display would stop scrolling then, but then later on when you moved off that line the display would keep on trying to scroll. This was to do with where I had attempted to account for the 'scrolloff' value in the centering bit of my code.  Made the command line clear so that you don't see a silly 'call StartSmoothCentering()' at the bottom of the screen each time.","package":"SmoothCenter.vim","4":"SmoothCenter.vim","src_id":"13516","5":"13516","creation_date":"1281195585","6":"1281195585"},{"0":"3149","vim_version":"6.0","1":"6.0","script_version":"1.3","2":"1.3","version_comment":"Fixed the glitch where if you had a scrolloff>0 set it would carry on scrolling if you were at the top and bottom and you did a S-ESC or S-F1.  Now correctly identifies the scrolloff setting and accounts for this value, not just the cursors position within the current window.  Changed key mappings to be a more natural-feeling S-ESC gets you 'out of the code', in other words lets you see where you are by scrolling the file down, whereas S-F1 scrolls up and hence further deep into the file.","3":"Fixed the glitch where if you had a scrolloff>0 set it would carry on scrolling if you were at the top and bottom and you did a S-ESC or S-F1.  Now correctly identifies the scrolloff setting and accounts for this value, not just the cursors position within the current window.  Changed key mappings to be a more natural-feeling S-ESC gets you 'out of the code', in other words lets you see where you are by scrolling the file down, whereas S-F1 scrolls up and hence further deep into the file.","package":"SmoothCenter.vim","4":"SmoothCenter.vim","src_id":"13508","5":"13508","creation_date":"1281190641","6":"1281190641"},{"0":"3149","vim_version":"6.0","1":"6.0","script_version":"1.2","2":"1.2","version_comment":"Had a bug where the end cases were not being detected properly, the top of the file and the end of the file respectively. I got them confused, so it looked like the scrolling wouldn't start if the first line was showing when you press S-Esc.","3":"Had a bug where the end cases were not being detected properly, the top of the file and the end of the file respectively. I got them confused, so it looked like the scrolling wouldn't start if the first line was showing when you press S-Esc.","package":"SmoothCenter.vim","4":"SmoothCenter.vim","src_id":"13490","5":"13490","creation_date":"1280964437","6":"1280964437"},{"0":"3149","vim_version":"6.0","1":"6.0","script_version":"1.1","2":"1.1","version_comment":"Cured the glitch that the centering is not centering when the end of the file is not as far as the bottom of the window.  Added a couple of new modes, these act just like zt and zb in normal mode. They are shift-ESC and shift-F1 respectively.  So now you've got all zz, zt & zb as smooth-equivalents: ESC, S-ESC and S-F1 respectively.","3":"Cured the glitch that the centering is not centering when the end of the file is not as far as the bottom of the window.  Added a couple of new modes, these act just like zt and zb in normal mode. They are shift-ESC and shift-F1 respectively.  So now you've got all zz, zt & zb as smooth-equivalents: ESC, S-ESC and S-F1 respectively.","package":"SmoothCenter.vim","4":"SmoothCenter.vim","src_id":"13450","5":"13450","creation_date":"1280626735","6":"1280626735"},{"0":"3149","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"SmoothCenter.vim","4":"SmoothCenter.vim","src_id":"13328","5":"13328","creation_date":"1279128178","6":"1279128178"}]},"3148":{"script_id":"3148","0":"3148","script_name":"reload.vim","1":"reload.vim","script_type":"utility","2":"utility","summary":"Automatic reloading of Vim scripts ((file-type) plug-ins, auto-load\/syntax\/inden","3":"Automatic reloading of Vim scripts ((file-type) plug-ins, auto-load\/syntax\/inden","description":"The reload.vim plug-in automatically reloads various types of Vim scripts as they're being edited in Vim to give you instant feedback on the changes you make. For example while writing a Vim syntax script you can open a split window of the relevant file type and every time you :update your syntax script, reload.vim will refresh the syntax highlighting in the split window. For more information about the plug-in please refer to its homepage or the project page on GitHub:\r\n\r\n \u00e2\u0080\u00a2 http:\/\/peterodding.com\/code\/vim\/reload\/\r\n \u00e2\u0080\u00a2 http:\/\/github.com\/xolox\/vim-reload\r\n\r\nIf you have questions, bug reports, suggestions, etc. the author can be contacted at peter@peterodding.com. If you like this plug-in please vote for it below!","4":"The reload.vim plug-in automatically reloads various types of Vim scripts as they're being edited in Vim to give you instant feedback on the changes you make. For example while writing a Vim syntax script you can open a split window of the relevant file type and every time you :update your syntax script, reload.vim will refresh the syntax highlighting in the split window. For more information about the plug-in please refer to its homepage or the project page on GitHub:\r\n\r\n \u00e2\u0080\u00a2 http:\/\/peterodding.com\/code\/vim\/reload\/\r\n \u00e2\u0080\u00a2 http:\/\/github.com\/xolox\/vim-reload\r\n\r\nIf you have questions, bug reports, suggestions, etc. the author can be contacted at peter@peterodding.com. If you like this plug-in please vote for it below!","install_details":"Please note that the vim-reload plug-in requires my vim-misc plug-in which is separately distributed (see vimscript #4597).\r\n\r\nUnzip the most recent ZIP archives of the vim-reload and vim-misc plug-ins inside your Vim profile directory (usually this is ~\/.vim on UNIX and %USERPROFILE%\\vimfiles on Windows), restart Vim and execute the command :helptags ~\/.vim\/doc (use :helptags ~\\vimfiles\\doc instead on Windows).\r\n\r\nNow try it out: Edit any Vim script that's already loaded and check that the script is reloaded when you save it (the reload.vim plug-in will print a message to confirm when a script is reloaded).\r\n\r\nIf you prefer you can also use Pathogen, Vundle or a similar tool to install & update the vim-reload and vim-misc plug-ins using a local clone of the git repository.","5":"Please note that the vim-reload plug-in requires my vim-misc plug-in which is separately distributed (see vimscript #4597).\r\n\r\nUnzip the most recent ZIP archives of the vim-reload and vim-misc plug-ins inside your Vim profile directory (usually this is ~\/.vim on UNIX and %USERPROFILE%\\vimfiles on Windows), restart Vim and execute the command :helptags ~\/.vim\/doc (use :helptags ~\\vimfiles\\doc instead on Windows).\r\n\r\nNow try it out: Edit any Vim script that's already loaded and check that the script is reloaded when you save it (the reload.vim plug-in will print a message to confirm when a script is reloaded).\r\n\r\nIf you prefer you can also use Pathogen, Vundle or a similar tool to install & update the vim-reload and vim-misc plug-ins using a local clone of the git repository.","first_name":"Peter","6":"Peter","last_name":"Odding","7":"Odding","releases":[{"0":"3148","vim_version":"7.0","1":"7.0","script_version":"0.6.16","2":"0.6.16","version_comment":" \u00e2\u0080\u00a2 Document vim-misc as external dependency (needs to be installed separately from now on):\n   http:\/\/github.com\/xolox\/vim-reload\/commit\/54d2c81\n\n \u00e2\u0080\u00a2 Bug fix: Reload messages on Windows showed corrupted filenames:\n   http:\/\/github.com\/xolox\/vim-reload\/commit\/5b6dbcb","3":" \u00e2\u0080\u00a2 Document vim-misc as external dependency (needs to be installed separately from now on):\n   http:\/\/github.com\/xolox\/vim-reload\/commit\/54d2c81\n\n \u00e2\u0080\u00a2 Bug fix: Reload messages on Windows showed corrupted filenames:\n   http:\/\/github.com\/xolox\/vim-reload\/commit\/5b6dbcb","package":"reload.zip","4":"reload.zip","src_id":"20207","5":"20207","creation_date":"1369498530","6":"1369498530"},{"0":"3148","vim_version":"7.0","1":"7.0","script_version":"0.6.14","2":"0.6.14","version_comment":" \u00e2\u0080\u00a2 Updated miscellaneous scripts:\n   http:\/\/github.com\/xolox\/vim-reload\/commit\/17047ef","3":" \u00e2\u0080\u00a2 Updated miscellaneous scripts:\n   http:\/\/github.com\/xolox\/vim-reload\/commit\/17047ef","package":"reload.zip","4":"reload.zip","src_id":"20183","5":"20183","creation_date":"1369054551","6":"1369054551"},{"0":"3148","vim_version":"7.0","1":"7.0","script_version":"0.6.13","2":"0.6.13","version_comment":" \u00e2\u0080\u00a2 Updated miscellaneous scripts:\n   http:\/\/github.com\/xolox\/vim-reload\/commit\/8522483","3":" \u00e2\u0080\u00a2 Updated miscellaneous scripts:\n   http:\/\/github.com\/xolox\/vim-reload\/commit\/8522483","package":"reload.zip","4":"reload.zip","src_id":"20171","5":"20171","creation_date":"1369003411","6":"1369003411"},{"0":"3148","vim_version":"7.0","1":"7.0","script_version":"0.6.12","2":"0.6.12","version_comment":" \u00e2\u0080\u00a2 Updated miscellaneous scripts:\n   http:\/\/github.com\/xolox\/vim-reload\/commit\/24827be\n   http:\/\/github.com\/xolox\/vim-reload\/commit\/9c88b0e","3":" \u00e2\u0080\u00a2 Updated miscellaneous scripts:\n   http:\/\/github.com\/xolox\/vim-reload\/commit\/24827be\n   http:\/\/github.com\/xolox\/vim-reload\/commit\/9c88b0e","package":"reload.zip","4":"reload.zip","src_id":"20125","5":"20125","creation_date":"1368481335","6":"1368481335"},{"0":"3148","vim_version":"7.0","1":"7.0","script_version":"0.6.11","2":"0.6.11","version_comment":" \u00e2\u0080\u00a2 Updated miscellaneous scripts:\n   http:\/\/github.com\/xolox\/vim-reload\/commit\/444413e","3":" \u00e2\u0080\u00a2 Updated miscellaneous scripts:\n   http:\/\/github.com\/xolox\/vim-reload\/commit\/444413e","package":"reload.zip","4":"reload.zip","src_id":"20008","5":"20008","creation_date":"1367488126","6":"1367488126"},{"0":"3148","vim_version":"7.0","1":"7.0","script_version":"0.6.10","2":"0.6.10","version_comment":" \u00e2\u0080\u00a2 Updated miscellaneous scripts:\n   http:\/\/github.com\/xolox\/vim-reload\/commit\/b72f810","3":" \u00e2\u0080\u00a2 Updated miscellaneous scripts:\n   http:\/\/github.com\/xolox\/vim-reload\/commit\/b72f810","package":"reload.zip","4":"reload.zip","src_id":"19960","5":"19960","creation_date":"1367159481","6":"1367159481"},{"0":"3148","vim_version":"7.0","1":"7.0","script_version":"0.6.9","2":"0.6.9","version_comment":" \u00e2\u0080\u00a2 Make compatibility with miscellaneous scripts explicit:\n   http:\/\/github.com\/xolox\/vim-reload\/commit\/31d1835","3":" \u00e2\u0080\u00a2 Make compatibility with miscellaneous scripts explicit:\n   http:\/\/github.com\/xolox\/vim-reload\/commit\/31d1835","package":"reload.zip","4":"reload.zip","src_id":"19875","5":"19875","creation_date":"1366504338","6":"1366504338"},{"0":"3148","vim_version":"7.0","1":"7.0","script_version":"0.6.8","2":"0.6.8","version_comment":" \u00e2\u0080\u00a2 Bug fix for file type plug-in reloading (also hide last buffer):\n   http:\/\/github.com\/xolox\/vim-reload\/commit\/46c9fb1","3":" \u00e2\u0080\u00a2 Bug fix for file type plug-in reloading (also hide last buffer):\n   http:\/\/github.com\/xolox\/vim-reload\/commit\/46c9fb1","package":"reload.zip","4":"reload.zip","src_id":"17005","5":"17005","creation_date":"1322766505","6":"1322766505"},{"0":"3148","vim_version":"7.0","1":"7.0","script_version":"0.6.7","2":"0.6.7","version_comment":" \u00e2\u0080\u00a2 Updated miscellaneous scripts:\n   http:\/\/github.com\/xolox\/vim-reload\/commit\/b767e0c\n   http:\/\/github.com\/xolox\/vim-reload\/commit\/a927516\n   http:\/\/github.com\/xolox\/vim-reload\/commit\/9b4c774","3":" \u00e2\u0080\u00a2 Updated miscellaneous scripts:\n   http:\/\/github.com\/xolox\/vim-reload\/commit\/b767e0c\n   http:\/\/github.com\/xolox\/vim-reload\/commit\/a927516\n   http:\/\/github.com\/xolox\/vim-reload\/commit\/9b4c774","package":"reload.zip","4":"reload.zip","src_id":"16972","5":"16972","creation_date":"1322268091","6":"1322268091"},{"0":"3148","vim_version":"7.0","1":"7.0","script_version":"0.6.6","2":"0.6.6","version_comment":" \u00e2\u0080\u00a2 Updated miscellaneous scripts:\n   http:\/\/github.com\/xolox\/vim-reload\/commit\/d2a8b23","3":" \u00e2\u0080\u00a2 Updated miscellaneous scripts:\n   http:\/\/github.com\/xolox\/vim-reload\/commit\/d2a8b23","package":"reload.zip","4":"reload.zip","src_id":"16928","5":"16928","creation_date":"1321911153","6":"1321911153"},{"0":"3148","vim_version":"7.0","1":"7.0","script_version":"0.6.5","2":"0.6.5","version_comment":" \u00e2\u0080\u00a2 Updated miscellaneous scripts:\n   http:\/\/github.com\/xolox\/vim-reload\/commit\/9913832","3":" \u00e2\u0080\u00a2 Updated miscellaneous scripts:\n   http:\/\/github.com\/xolox\/vim-reload\/commit\/9913832","package":"reload.zip","4":"reload.zip","src_id":"16582","5":"16582","creation_date":"1316994819","6":"1316994819"},{"0":"3148","vim_version":"7.0","1":"7.0","script_version":"0.6.4","2":"0.6.4","version_comment":" \u00e2\u0080\u00a2 Move version variable to autoload script:\n   http:\/\/github.com\/xolox\/vim-reload\/commit\/a3d786c\n\n \u00e2\u0080\u00a2 Updated miscellaneous scripts","3":" \u00e2\u0080\u00a2 Move version variable to autoload script:\n   http:\/\/github.com\/xolox\/vim-reload\/commit\/a3d786c\n\n \u00e2\u0080\u00a2 Updated miscellaneous scripts","package":"reload.zip","4":"reload.zip","src_id":"16460","5":"16460","creation_date":"1315145363","6":"1315145363"},{"0":"3148","vim_version":"7.0","1":"7.0","script_version":"0.6.2","2":"0.6.2","version_comment":" \u00e2\u0080\u00a2 Define version as variable, include version in messages:\n   http:\/\/github.com\/xolox\/vim-reload\/commit\/6c11e27","3":" \u00e2\u0080\u00a2 Define version as variable, include version in messages:\n   http:\/\/github.com\/xolox\/vim-reload\/commit\/6c11e27","package":"reload.zip","4":"reload.zip","src_id":"15924","5":"15924","creation_date":"1308362492","6":"1308362492"},{"0":"3148","vim_version":"7.0","1":"7.0","script_version":"0.6","2":"0.6","version_comment":"Support for generic file type plug-ins (thanks to Britton Kerin for the suggestion):\r\nhttps:\/\/github.com\/xolox\/vim-reload\/commit\/b6b3952940e00c2f010e","3":"Support for generic file type plug-ins (thanks to Britton Kerin for the suggestion):\r\nhttps:\/\/github.com\/xolox\/vim-reload\/commit\/b6b3952940e00c2f010e","package":"reload.zip","4":"reload.zip","src_id":"14956","5":"14956","creation_date":"1296862171","6":"1296862171"},{"0":"3148","vim_version":"7.0","1":"7.0","script_version":"0.5.2","2":"0.5.2","version_comment":"Bug fix for case insensitive filenames (reported by Jeff Bevis):\r\nhttp:\/\/github.com\/xolox\/vim-reload\/commit\/138e64dcc3770f3fb008","3":"Bug fix for case insensitive filenames (reported by Jeff Bevis):\r\nhttp:\/\/github.com\/xolox\/vim-reload\/commit\/138e64dcc3770f3fb008","package":"reload.zip","4":"reload.zip","src_id":"14072","5":"14072","creation_date":"1287430960","6":"1287430960"},{"0":"3148","vim_version":"7.0","1":"7.0","script_version":"0.5.1","2":"0.5.1","version_comment":"Bug fix: Forgot that color scheme reloading can fail:\r\nhttp:\/\/github.com\/xolox\/vim-reload\/commit\/e2443ff27a07e15a94d7935ae202d69894b1ab50","3":"Bug fix: Forgot that color scheme reloading can fail:\r\nhttp:\/\/github.com\/xolox\/vim-reload\/commit\/e2443ff27a07e15a94d7935ae202d69894b1ab50","package":"reload.zip","4":"reload.zip","src_id":"13392","5":"13392","creation_date":"1279886944","6":"1279886944"},{"0":"3148","vim_version":"7.0","1":"7.0","script_version":"0.5","2":"0.5","version_comment":" \u00e2\u0080\u00a2 Simplified ftplugin\/syntax\/indent reloading, fixed E325 workaround:\r\n   http:\/\/github.com\/xolox\/vim-reload\/commit\/b703505c93f24f27c973b37836257c1cacda011d\r\n\r\n \u00e2\u0080\u00a2 Shortened code by moving xolox#timer#stop() calls:\r\n   http:\/\/github.com\/xolox\/vim-reload\/commit\/cd36d10f1f92a3b7e7d6c765e149af623772b3aa","3":" \u00e2\u0080\u00a2 Simplified ftplugin\/syntax\/indent reloading, fixed E325 workaround:\r\n   http:\/\/github.com\/xolox\/vim-reload\/commit\/b703505c93f24f27c973b37836257c1cacda011d\r\n\r\n \u00e2\u0080\u00a2 Shortened code by moving xolox#timer#stop() calls:\r\n   http:\/\/github.com\/xolox\/vim-reload\/commit\/cd36d10f1f92a3b7e7d6c765e149af623772b3aa","package":"reload.zip","4":"reload.zip","src_id":"13388","5":"13388","creation_date":"1279849837","6":"1279849837"},{"0":"3148","vim_version":"7.0","1":"7.0","script_version":"0.4","2":"0.4","version_comment":"The plug-in now clears inclusion guards before reloading plug-in scripts: http:\/\/github.com\/xolox\/vim-reload\/commit\/8fb0c8585c95056873bc2f4b4178cf874d97da20","3":"The plug-in now clears inclusion guards before reloading plug-in scripts: http:\/\/github.com\/xolox\/vim-reload\/commit\/8fb0c8585c95056873bc2f4b4178cf874d97da20","package":"reload.zip","4":"reload.zip","src_id":"13332","5":"13332","creation_date":"1279155365","6":"1279155365"},{"0":"3148","vim_version":"7.0","1":"7.0","script_version":"0.3.1","2":"0.3.1","version_comment":"Automatic update support using GLVS and README updates:\r\nhttp:\/\/github.com\/xolox\/vim-reload\/commit\/5fc2712cede6af6ab27911e02142a0b26bae6620","3":"Automatic update support using GLVS and README updates:\r\nhttp:\/\/github.com\/xolox\/vim-reload\/commit\/5fc2712cede6af6ab27911e02142a0b26bae6620","package":"reload.zip","4":"reload.zip","src_id":"13326","5":"13326","creation_date":"1278991336","6":"1278991336"},{"0":"3148","vim_version":"7.0","1":"7.0","script_version":"0.3","2":"0.3","version_comment":"Initial upload","3":"Initial upload","package":"reload.zip","4":"reload.zip","src_id":"13325","5":"13325","creation_date":"1278990512","6":"1278990512"}]},"3147":{"script_id":"3147","0":"3147","script_name":"wmgraphviz","1":"wmgraphviz","script_type":"ftplugin","2":"ftplugin","summary":"Plugin for Graphviz DOT","3":"Plugin for Graphviz DOT","description":"Vim plugin for Graphviz DOT.\r\n\r\nFeatures:\r\n- Omnicompletion\r\n- Compiling and viewing commands\r\n\r\nMost recent version available at http:\/\/github.com\/wannesm\/wmgraphviz.vim","4":"Vim plugin for Graphviz DOT.\r\n\r\nFeatures:\r\n- Omnicompletion\r\n- Compiling and viewing commands\r\n\r\nMost recent version available at http:\/\/github.com\/wannesm\/wmgraphviz.vim","install_details":"Inspecting:\r\n$ tar -ztvf wmgraphviz.vim.tgz \r\ndoc\/wmgraphviz.txt\r\nftplugin\/dot.vim\r\nsnippets\/dot.snippets\r\n\r\nInstalling:\r\n$ cd ~\/.vim\/\r\n$ zcat wmgraphviz.vim.tgz | tar xvf -","5":"Inspecting:\r\n$ tar -ztvf wmgraphviz.vim.tgz \r\ndoc\/wmgraphviz.txt\r\nftplugin\/dot.vim\r\nsnippets\/dot.snippets\r\n\r\nInstalling:\r\n$ cd ~\/.vim\/\r\n$ zcat wmgraphviz.vim.tgz | tar xvf -","first_name":"Wannes","6":"Wannes","last_name":"Meert","7":"Meert","releases":[{"0":"3147","vim_version":"7.3","1":"7.3","script_version":"1.1","2":"1.1","version_comment":"Changed:\r\n\r\n- [FIX] Handle filenames with spaces (Johannes Holzfu\u00c3\u009f)\r\n- [ADDED] Use xdg-open on unix for viewing\r\n- [ADDED] Support for Dot2TeX","3":"Changed:\r\n\r\n- [FIX] Handle filenames with spaces (Johannes Holzfu\u00c3\u009f)\r\n- [ADDED] Use xdg-open on unix for viewing\r\n- [ADDED] Support for Dot2TeX","package":"wmgraphviz.vim.tgz","4":"wmgraphviz.vim.tgz","src_id":"14529","5":"14529","creation_date":"1292503745","6":"1292503745"},{"0":"3147","vim_version":"7.0","1":"7.0","script_version":"1.0.2","2":"1.0.2","version_comment":"- Improved omnicompletion \r\n- Added Snipmate snippets","3":"- Improved omnicompletion \r\n- Added Snipmate snippets","package":"wmgraphviz.vim.tgz","4":"wmgraphviz.vim.tgz","src_id":"13401","5":"13401","creation_date":"1279964654","6":"1279964654"},{"0":"3147","vim_version":"7.0","1":"7.0","script_version":"1.0.1","2":"1.0.1","version_comment":"- Better support for multi-graph files\r\n- Small fixes","3":"- Better support for multi-graph files\r\n- Small fixes","package":"wmgraphviz.vim.tgz","4":"wmgraphviz.vim.tgz","src_id":"13327","5":"13327","creation_date":"1279033743","6":"1279033743"},{"0":"3147","vim_version":"7.2","1":"7.2","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"wmgraphviz.vim.tgz","4":"wmgraphviz.vim.tgz","src_id":"13324","5":"13324","creation_date":"1278931077","6":"1278931077"}]},"3146":{"script_id":"3146","0":"3146","script_name":"quickrun.vim","1":"quickrun.vim","script_type":"utility","2":"utility","summary":"Run a command and show its result quickly.","3":"Run a command and show its result quickly.","description":"*quickrun* is Vim plugin to execute whole\/part of editing file and show the result.\r\nIt provides :QuickRun command for it.\r\n\r\nDefault is set in the following languages:\r\n\r\n- awk\r\n- bash\r\n- c\r\n- clojure\r\n- coffee\r\n- cpp\r\n- cs\r\n- d\r\n- dart\r\n- dosbatch\r\n- erlang\r\n- eruby\r\n- fortran\r\n- go\r\n- groovy\r\n- haskell\r\n- io\r\n- java\r\n- javascript\r\n- jsx\r\n- lisp\r\n- llvm\r\n- lua\r\n- markdown\r\n- ocaml\r\n- perl\r\n- perl6\r\n- php\r\n- python\r\n- r\r\n- ruby\r\n- rust\r\n- scala\r\n- scheme\r\n- sed\r\n- sh\r\n- vim\r\n- wsh\r\n- zsh\r\n\r\nYou can add settings for other languages and situations.\r\n\r\nLatest Version:\r\nhttps:\/\/github.com\/thinca\/vim-quickrun\r\n","4":"*quickrun* is Vim plugin to execute whole\/part of editing file and show the result.\r\nIt provides :QuickRun command for it.\r\n\r\nDefault is set in the following languages:\r\n\r\n- awk\r\n- bash\r\n- c\r\n- clojure\r\n- coffee\r\n- cpp\r\n- cs\r\n- d\r\n- dart\r\n- dosbatch\r\n- erlang\r\n- eruby\r\n- fortran\r\n- go\r\n- groovy\r\n- haskell\r\n- io\r\n- java\r\n- javascript\r\n- jsx\r\n- lisp\r\n- llvm\r\n- lua\r\n- markdown\r\n- ocaml\r\n- perl\r\n- perl6\r\n- php\r\n- python\r\n- r\r\n- ruby\r\n- rust\r\n- scala\r\n- scheme\r\n- sed\r\n- sh\r\n- vim\r\n- wsh\r\n- zsh\r\n\r\nYou can add settings for other languages and situations.\r\n\r\nLatest Version:\r\nhttps:\/\/github.com\/thinca\/vim-quickrun\r\n","install_details":"","5":"","first_name":"thinca","6":"thinca","last_name":" ","7":" ","releases":[{"0":"3146","vim_version":"7.2","1":"7.2","script_version":"0.6.0","2":"0.6.0","version_comment":"- Changed the constitution of module system.\r\n  - quickrun#xxx_module() => quickrun#module#xxx()\r\n  - Changed the arguments of quickrun#module#register().\r\n  - Added quickrun#module#unregister().\r\n  - Added quickrun#module#exists().\r\n- Added hook module.\r\n- Some options were moved to hook and removed.\r\n  - output_encode\r\n  - shebang\r\n  - eval\r\n- Some options were added to some modules.\r\n  - runner\/vimproc\r\n    - sleep\r\n  - outputter\/buffer\r\n    - name\r\n    - filetype\r\n- Added runner\/vimscript.\r\n- The specification which executes the command of Vim was deleted.\r\n","3":"- Changed the constitution of module system.\r\n  - quickrun#xxx_module() => quickrun#module#xxx()\r\n  - Changed the arguments of quickrun#module#register().\r\n  - Added quickrun#module#unregister().\r\n  - Added quickrun#module#exists().\r\n- Added hook module.\r\n- Some options were moved to hook and removed.\r\n  - output_encode\r\n  - shebang\r\n  - eval\r\n- Some options were added to some modules.\r\n  - runner\/vimproc\r\n    - sleep\r\n  - outputter\/buffer\r\n    - name\r\n    - filetype\r\n- Added runner\/vimscript.\r\n- The specification which executes the command of Vim was deleted.\r\n","package":"vim-quickrun-0.6.0.zip","4":"vim-quickrun-0.6.0.zip","src_id":"18181","5":"18181","creation_date":"1340431324","6":"1340431324"},{"0":"3146","vim_version":"7.2","1":"7.2","script_version":"0.5.1","2":"0.5.1","version_comment":"- Added \"srcfile\" option.\r\n- Added quickrun#get_module().\r\n- Module was made unregisterable.\r\n- Improved the expanding of \"exec\".","3":"- Added \"srcfile\" option.\r\n- Added quickrun#get_module().\r\n- Module was made unregisterable.\r\n- Improved the expanding of \"exec\".","package":"vim-quickrun-0.5.1.zip","4":"vim-quickrun-0.5.1.zip","src_id":"16715","5":"16715","creation_date":"1319214533","6":"1319214533"},{"0":"3146","vim_version":"7.2","1":"7.2","script_version":"0.5.0","2":"0.5.0","version_comment":"- Implemented the module system.\r\n  - Some options are not compatible.\r\n  - See :help quickrun-module more details.\r\n- Moved QuickRun() into quickrun#operator().\r\n- Other many changes.","3":"- Implemented the module system.\r\n  - Some options are not compatible.\r\n  - See :help quickrun-module more details.\r\n- Moved QuickRun() into quickrun#operator().\r\n- Other many changes.","package":"vim-quickrun-0.5.0.zip","4":"vim-quickrun-0.5.0.zip","src_id":"16149","5":"16149","creation_date":"1311705511","6":"1311705511"},{"0":"3146","vim_version":"7.2","1":"7.2","script_version":"0.4.7","2":"0.4.7","version_comment":"- Added and improved the default values.","3":"- Added and improved the default values.","package":"vim-quickrun-0.4.7.zip","4":"vim-quickrun-0.4.7.zip","src_id":"15701","5":"15701","creation_date":"1306192723","6":"1306192723"},{"0":"3146","vim_version":"7.2","1":"7.2","script_version":"0.4.5","2":"0.4.5","version_comment":"- Improved the default value for go language.\r\n- Improved the default value for javascript.\r\n- Do not escape %c symbol if shebang line was used.\r\n- Fixed the \"shebang\" option always worked.","3":"- Improved the default value for go language.\r\n- Improved the default value for javascript.\r\n- Do not escape %c symbol if shebang line was used.\r\n- Fixed the \"shebang\" option always worked.","package":"vim-quickrun-0.4.5.zip","4":"vim-quickrun-0.4.5.zip","src_id":"14987","5":"14987","creation_date":"1297174202","6":"1297174202"},{"0":"3146","vim_version":"7.2","1":"7.2","script_version":"0.4.4","2":"0.4.4","version_comment":"- Always expand \"input\" option.\r\n- Fixed a bug when \"runmode\" option is \"async:python\".\r\n- Improved behavior in MS Windows.\r\n- Changed \"%c\" into symbol that specifies file.","3":"- Always expand \"input\" option.\r\n- Fixed a bug when \"runmode\" option is \"async:python\".\r\n- Improved behavior in MS Windows.\r\n- Changed \"%c\" into symbol that specifies file.","package":"vim-quickrun-0.4.4.zip","4":"vim-quickrun-0.4.4.zip","src_id":"14729","5":"14729","creation_date":"1294756979","6":"1294756979"},{"0":"3146","vim_version":"7.2","1":"7.2","script_version":"0.4.3","2":"0.4.3","version_comment":"- Added the default config for erlang.\r\n- Added \"cmdopt\" option.\r\n- Expand \"args\" option.\r\n- Improved the command line completion.\r\n- \":to\" of output_encode is omissible.\r\n- Fixed a bug of infinity loop.","3":"- Added the default config for erlang.\r\n- Added \"cmdopt\" option.\r\n- Expand \"args\" option.\r\n- Improved the command line completion.\r\n- \":to\" of output_encode is omissible.\r\n- Fixed a bug of infinity loop.","package":"vim-quickrun-0.4.3.zip","4":"vim-quickrun-0.4.3.zip","src_id":"14508","5":"14508","creation_date":"1292335128","6":"1292335128"},{"0":"3146","vim_version":"7.2","1":"7.2","script_version":"0.4.2","2":"0.4.2","version_comment":"- Added \"_\" to the default type name.\r\n- Added perl6 support as default.\r\n- Expand |quickrun-option-output|.\r\n- Fixed a bug that \"split\" option doesn't work in twice or later.\r\n- Changed g:quickrun_default_config to g:quickrun#default_config.\r\n- Added the following values to |quickrun-option-runmode|.\r\n  - \"async:vimproc\"\r\n  - \"async:python\"\r\n  - These are experimental.\r\n- Check hasmapto() before <Leader>r is defined.\r\n- Improve the reading and writing of a file.","3":"- Added \"_\" to the default type name.\r\n- Added perl6 support as default.\r\n- Expand |quickrun-option-output|.\r\n- Fixed a bug that \"split\" option doesn't work in twice or later.\r\n- Changed g:quickrun_default_config to g:quickrun#default_config.\r\n- Added the following values to |quickrun-option-runmode|.\r\n  - \"async:vimproc\"\r\n  - \"async:python\"\r\n  - These are experimental.\r\n- Check hasmapto() before <Leader>r is defined.\r\n- Improve the reading and writing of a file.","package":"vim-quickrun-0.4.2.zip","4":"vim-quickrun-0.4.2.zip","src_id":"14082","5":"14082","creation_date":"1287589804","6":"1287589804"},{"0":"3146","vim_version":"7.2","1":"7.2","script_version":"0.4.1","2":"0.4.1","version_comment":"Initial upload","3":"Initial upload","package":"vim-quickrun-0.4.1.zip","4":"vim-quickrun-0.4.1.zip","src_id":"13321","5":"13321","creation_date":"1278857876","6":"1278857876"}]},"3145":{"script_id":"3145","0":"3145","script_name":"zetavim","1":"zetavim","script_type":"utility","2":"utility","summary":"Plugin to ftdetect, syntax highlight ZWiki-zeta markup. Interface with Zeta site","3":"Plugin to ftdetect, syntax highlight ZWiki-zeta markup. Interface with Zeta site","description":"Short Description :\r\n===============\r\n\r\nA collection of plug-in that is useful with Zwiki tool and Zeta project collaboration suite. The package contains three parts, namely,\r\n\r\n* detecting text files written in ZWiki-zeta markup\r\n*  syntax highlighting markup text\r\n*  vim & python plugin to interface with zeta http server to edit wiki, tickets and reviews with vim\r\n\r\nQuick Links :\r\n===========\r\n\r\nTo know more on how to interface with Zeta project collaboration site, check out the link,\r\nhttp:\/\/dev.discoverzeta.com\/help\/VimIntegration\r\n\r\nUse structured-text while interfacing with Zeta server via Vim.\r\nhttp:\/\/dev.discoverzeta.com\/help\/StructuredText\r\n\r\nDownload ZWiki-zeta from python package index,\r\nhttp:\/\/pypi.python.org\/pypi\/zwiki-zeta\/0.9beta\r\n\r\nFor documentation and obtaining Zeta application,\r\nhttp:\/\/discoverzeta.com\r\n\r\nParticipate in our mailing list with your queries and comments,\r\nhttp:\/\/groups.google.com\/group\/zeta-discuss","4":"Short Description :\r\n===============\r\n\r\nA collection of plug-in that is useful with Zwiki tool and Zeta project collaboration suite. The package contains three parts, namely,\r\n\r\n* detecting text files written in ZWiki-zeta markup\r\n*  syntax highlighting markup text\r\n*  vim & python plugin to interface with zeta http server to edit wiki, tickets and reviews with vim\r\n\r\nQuick Links :\r\n===========\r\n\r\nTo know more on how to interface with Zeta project collaboration site, check out the link,\r\nhttp:\/\/dev.discoverzeta.com\/help\/VimIntegration\r\n\r\nUse structured-text while interfacing with Zeta server via Vim.\r\nhttp:\/\/dev.discoverzeta.com\/help\/StructuredText\r\n\r\nDownload ZWiki-zeta from python package index,\r\nhttp:\/\/pypi.python.org\/pypi\/zwiki-zeta\/0.9beta\r\n\r\nFor documentation and obtaining Zeta application,\r\nhttp:\/\/discoverzeta.com\r\n\r\nParticipate in our mailing list with your queries and comments,\r\nhttp:\/\/groups.google.com\/group\/zeta-discuss","install_details":"Download the tar.gz file into your $(HOME)\/.vim\/ directory. Change to $(HOME)\/.vim directory and un-tar the package.","5":"Download the tar.gz file into your $(HOME)\/.vim\/ directory. Change to $(HOME)\/.vim directory and un-tar the package.","first_name":"Pratap","6":"Pratap","last_name":"Chakravarthy","7":"Chakravarthy","releases":[{"0":"3145","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"zetavim-0.1.tar.gz","4":"zetavim-0.1.tar.gz","src_id":"13313","5":"13313","creation_date":"1278773901","6":"1278773901"}]},"3144":{"script_id":"3144","0":"3144","script_name":"hgrev","1":"hgrev","script_type":"utility","2":"utility","summary":"Display Mercurial revision info in the Vim statusline.","3":"Display Mercurial revision info in the Vim statusline.","description":"HGRev is a small plugin that can find the current buffer's revision ID from a Mercurial (http:\/\/mercurial.selenic.com\/) repository.\r\n\r\nIt is intended for use in the Vim statusline - here's an example to enable it:\r\n\r\n   set statusline=[r%{HGRev()}] \r\n\r\nHGRev exports the \"HGRev()\" function (for use in the statusline), and\r\na command called \":RefreshMercurialRev\", which you can use to manually\r\nupdate the revision information for the current buffer.  If you've added\r\nHGRev() to your statusline, you'll see the file revision, branch, tags,\r\nand file status reflected -- if you used the statusline example above,\r\nyou should see something like this:\r\n\r\n   [r192+ default tip M]\r\n\r\nThe information displayed can be easily customized, and HGRev can also\r\nautomatically update the status line on file changes.  (This behavior is\r\ndisabled by default -- see the documentation for details.)\r\n\r\nOnce installed, HGRev has built-in help.  Access it via \":help HGRev\".\r\n","4":"HGRev is a small plugin that can find the current buffer's revision ID from a Mercurial (http:\/\/mercurial.selenic.com\/) repository.\r\n\r\nIt is intended for use in the Vim statusline - here's an example to enable it:\r\n\r\n   set statusline=[r%{HGRev()}] \r\n\r\nHGRev exports the \"HGRev()\" function (for use in the statusline), and\r\na command called \":RefreshMercurialRev\", which you can use to manually\r\nupdate the revision information for the current buffer.  If you've added\r\nHGRev() to your statusline, you'll see the file revision, branch, tags,\r\nand file status reflected -- if you used the statusline example above,\r\nyou should see something like this:\r\n\r\n   [r192+ default tip M]\r\n\r\nThe information displayed can be easily customized, and HGRev can also\r\nautomatically update the status line on file changes.  (This behavior is\r\ndisabled by default -- see the documentation for details.)\r\n\r\nOnce installed, HGRev has built-in help.  Access it via \":help HGRev\".\r\n","install_details":"Install the VimBall plugin (vimscript #1502) if you don't already have it.\r\n\r\nThen open hgrev.vba.gz from within vim.\r\n\r\n    :so %\r\n","5":"Install the VimBall plugin (vimscript #1502) if you don't already have it.\r\n\r\nThen open hgrev.vba.gz from within vim.\r\n\r\n    :so %\r\n","first_name":"Mahlon","6":"Mahlon","last_name":"Smith","7":"Smith","releases":[{"0":"3144","vim_version":"7.0","1":"7.0","script_version":"0.2","2":"0.2","version_comment":"Don't try to find an HG repo on remote buffers.  (Miguel Ventura <miguel.ventura@gmail.com>)","3":"Don't try to find an HG repo on remote buffers.  (Miguel Ventura <miguel.ventura@gmail.com>)","package":"hgrev.vba.gz","4":"hgrev.vba.gz","src_id":"18588","5":"18588","creation_date":"1347472754","6":"1347472754"},{"0":"3144","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"hgrev.vba.gz","4":"hgrev.vba.gz","src_id":"13307","5":"13307","creation_date":"1278603501","6":"1278603501"}]},"3143":{"script_id":"3143","0":"3143","script_name":"vim-haxe","1":"vim-haxe","script_type":"utility","2":"utility","summary":"haxe language support","3":"haxe language support","description":"depends on some more plugins. See vim-haxe-addon-info.txt.\r\nI recommend you installing it using the vim-addon-manager plugin.\r\n\r\nThis plugin provides HaXe completion syntax highlighting, completion based on the HaXe compiler output, running HaXe using vim-addon-actions","4":"depends on some more plugins. See vim-haxe-addon-info.txt.\r\nI recommend you installing it using the vim-addon-manager plugin.\r\n\r\nThis plugin provides HaXe completion syntax highlighting, completion based on the HaXe compiler output, running HaXe using vim-addon-actions","install_details":"","5":"","first_name":"Marc","6":"Marc","last_name":"Weber","7":"Weber","releases":[{"0":"3143","vim_version":"7.0","1":"7.0","script_version":"0.1.3","2":"0.1.3","version_comment":"gC -> neko.io.File.getContent completion, don't complet func local vars after . TF -> flash.text.TextField completion","3":"gC -> neko.io.File.getContent completion, don't complet func local vars after . TF -> flash.text.TextField completion","package":"vim-haxe-0.1.3.zip","4":"vim-haxe-0.1.3.zip","src_id":"13771","5":"13771","creation_date":"1283850948","6":"1283850948"},{"0":"3143","vim_version":"7.0","1":"7.0","script_version":"0.1.2","2":"0.1.2","version_comment":"tag std lib matching current target, support HaXe completion when using quick targets. a tmp.hxml file is created for that purpose","3":"tag std lib matching current target, support HaXe completion when using quick targets. a tmp.hxml file is created for that purpose","package":"vim-haxe-0.1.2.zip","4":"vim-haxe-0.1.2.zip","src_id":"13380","5":"13380","creation_date":"1279750890","6":"1279750890"},{"0":"3143","vim_version":"7.0","1":"7.0","script_version":"0.1.1","2":"0.1.1","version_comment":"small fix syntax highlighting, action targeting flash","3":"small fix syntax highlighting, action targeting flash","package":"vim-haxe-0.1.1.zip","4":"vim-haxe-0.1.1.zip","src_id":"13367","5":"13367","creation_date":"1279695186","6":"1279695186"},{"0":"3143","vim_version":"7.2","1":"7.2","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"initial-upload.zip","4":"initial-upload.zip","src_id":"13305","5":"13305","creation_date":"1278540441","6":"1278540441"}]},"3142":{"script_id":"3142","0":"3142","script_name":"vim-snipplr","1":"vim-snipplr","script_type":"utility","2":"utility","summary":"frontend for http:\/\/www.snipplr.com\/","3":"frontend for http:\/\/www.snipplr.com\/","description":"snipplr.vim \r\n============\r\nSnipplr.vim is frontend for http:\/\/www.snipplr.com\/\r\nYou can open your favoritted snippet or get snippet you specified by ID or URL.\r\nRequire Ruby to work(not require +ruby feature).\r\nCurrently work on *nix only.\r\n\r\nINSTALL\r\n---------------\r\n\r\n    cp plugin\/snipplr.vim $HOME\/.vim\/plugin\/\r\n    cp syntax\/snipplrlist.vim $HOME\/.vim\/syntax\/\r\n    copy bin\/snipplr.rb to one of the directory in $PATH\r\n\r\nSETUP\r\n---------------\r\n\r\nCreate account on http:\/\/www.snipplr.com\/\r\nYou can find API KEY at buttom of \"Setting\" page.\r\n\r\nthen save API KEY as `~\/.snipplr\/api_key`\r\n\r\nGLOVAL VARIABLE\r\n---------------\r\nYou can exclusively set path for snipplr.rb in `.vimrc`\r\n\r\n    let g:snipplr_rb = '$HOME\/.vim\/bundle\/snipplr\/bin\/snipplr.rb'\r\n\r\nCommand\r\n----------\r\n\r\nsnipplr.rb save snippets once get as `~\/.snipplr\/db.yml.`\r\nYou can avoid cache with exlamation(!) version command.\r\n\r\n### SnipplrGet\r\nIn opend snippet buffer you can use 'i' to view informatin about that snippet.\r\n\r\n    :SnipplrGet 1234\r\n    :SnipplrGet http:\/\/snipplr.com\/view\/1234\/sample\r\n\r\n### SnipplrList\r\n\r\n    :SnipplrList\r\n    :SnipplrList!\r\n\r\n### SnipplrFind\r\nTo this comman work, you have to install [ fuzzyfinder ]( http:\/\/www.vim.org\/scripts\/script.php?script_id=1984 )\r\n\r\n    :SnipplrFind\r\n    :SnipplrFind!\r\n\r\nKeyMapping Example\r\n------------------\r\n\r\n    nnoremap <silent> <Space>sl :<C-u>SnipplrFind<CR>\r\n    nnoremap <silent> <Space>sr :<C-u>SnipplrFind!<CR>\r\n\r\nTODO\r\n------------------\r\nparametarize cache dir and api_key location etc..  \r\nquery with metadata(tag, user.. etc)  \r\npost snippet from vim buffer  \r\nmore informative syntax highlight with predefined keyword for lang name  \r\ndynamically change window height for snipplr list  \r\nmerge more than one cache data to one cache(which is comvenient for  \r\n   collabolate with coworker  ","4":"snipplr.vim \r\n============\r\nSnipplr.vim is frontend for http:\/\/www.snipplr.com\/\r\nYou can open your favoritted snippet or get snippet you specified by ID or URL.\r\nRequire Ruby to work(not require +ruby feature).\r\nCurrently work on *nix only.\r\n\r\nINSTALL\r\n---------------\r\n\r\n    cp plugin\/snipplr.vim $HOME\/.vim\/plugin\/\r\n    cp syntax\/snipplrlist.vim $HOME\/.vim\/syntax\/\r\n    copy bin\/snipplr.rb to one of the directory in $PATH\r\n\r\nSETUP\r\n---------------\r\n\r\nCreate account on http:\/\/www.snipplr.com\/\r\nYou can find API KEY at buttom of \"Setting\" page.\r\n\r\nthen save API KEY as `~\/.snipplr\/api_key`\r\n\r\nGLOVAL VARIABLE\r\n---------------\r\nYou can exclusively set path for snipplr.rb in `.vimrc`\r\n\r\n    let g:snipplr_rb = '$HOME\/.vim\/bundle\/snipplr\/bin\/snipplr.rb'\r\n\r\nCommand\r\n----------\r\n\r\nsnipplr.rb save snippets once get as `~\/.snipplr\/db.yml.`\r\nYou can avoid cache with exlamation(!) version command.\r\n\r\n### SnipplrGet\r\nIn opend snippet buffer you can use 'i' to view informatin about that snippet.\r\n\r\n    :SnipplrGet 1234\r\n    :SnipplrGet http:\/\/snipplr.com\/view\/1234\/sample\r\n\r\n### SnipplrList\r\n\r\n    :SnipplrList\r\n    :SnipplrList!\r\n\r\n### SnipplrFind\r\nTo this comman work, you have to install [ fuzzyfinder ]( http:\/\/www.vim.org\/scripts\/script.php?script_id=1984 )\r\n\r\n    :SnipplrFind\r\n    :SnipplrFind!\r\n\r\nKeyMapping Example\r\n------------------\r\n\r\n    nnoremap <silent> <Space>sl :<C-u>SnipplrFind<CR>\r\n    nnoremap <silent> <Space>sr :<C-u>SnipplrFind!<CR>\r\n\r\nTODO\r\n------------------\r\nparametarize cache dir and api_key location etc..  \r\nquery with metadata(tag, user.. etc)  \r\npost snippet from vim buffer  \r\nmore informative syntax highlight with predefined keyword for lang name  \r\ndynamically change window height for snipplr list  \r\nmerge more than one cache data to one cache(which is comvenient for  \r\n   collabolate with coworker  ","install_details":"","5":"","first_name":"t9md","6":"t9md","last_name":"jp","7":"jp","releases":[{"0":"3142","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"vim-snipplr.zip","4":"vim-snipplr.zip","src_id":"13299","5":"13299","creation_date":"1278501434","6":"1278501434"}]},"3141":{"script_id":"3141","0":"3141","script_name":"ez_scroll","1":"ez_scroll","script_type":"utility","2":"utility","summary":"Scroll a window using right click+drag","3":"Scroll a window using right click+drag","description":"Sometimes I prefer to use the mouse to scroll a file.  Like if I'm just reading a file and not editing it then my hands aren't going to be perched on the keyboard and so looking down to find the right keys to control the scrolling is going to be distressful.  Or if I'm looking at a different window or if I've just focused the window with the file in it and my hand is already on the mouse.  But scroll-bars --- with their variable sized beveled areas ---  are precision controls that require quite a lot of attention and sobriety to operate.  And if I'm less than a few pages from where I want to scroll to (like, maybe I'm reading the whole file line-by-line) and if the file is really large (like, maybe it's a book) then scroll-bars are just plain silly: You're looking at maybe a couple millimeters of beveled area that you've got to click on and then drag another couple millimeters.  Another medium that often has large files that one reads line-by-line is the pdf.  The designers of pdf reading software have noticed the scroll-bar issue and they've come up with what I think is a nice interface: You can right-click anywhere on the window with the `hand' cursor and just paw your way through the pages.  It's even enabled by default; so sure are they that this is what you're going to want to use to scroll around.  Another common way to scroll by less than a few lines with the mouse is the scroll-wheel interface.  That's already there in vim if you have `:set mouse=a' (and this is on in gvim by default).  But I really detest it.  It engenders a really awkward finger movement that I reserve for one activity only and it's not scrolling.  And I don't think that finger movement's good for your hand anyway and so it shouldn't be used outside of bed.  So after all of this, why not have the right-click and drag functionality in vim?  Right drag isn't used for anything else anyways.\r\n","4":"Sometimes I prefer to use the mouse to scroll a file.  Like if I'm just reading a file and not editing it then my hands aren't going to be perched on the keyboard and so looking down to find the right keys to control the scrolling is going to be distressful.  Or if I'm looking at a different window or if I've just focused the window with the file in it and my hand is already on the mouse.  But scroll-bars --- with their variable sized beveled areas ---  are precision controls that require quite a lot of attention and sobriety to operate.  And if I'm less than a few pages from where I want to scroll to (like, maybe I'm reading the whole file line-by-line) and if the file is really large (like, maybe it's a book) then scroll-bars are just plain silly: You're looking at maybe a couple millimeters of beveled area that you've got to click on and then drag another couple millimeters.  Another medium that often has large files that one reads line-by-line is the pdf.  The designers of pdf reading software have noticed the scroll-bar issue and they've come up with what I think is a nice interface: You can right-click anywhere on the window with the `hand' cursor and just paw your way through the pages.  It's even enabled by default; so sure are they that this is what you're going to want to use to scroll around.  Another common way to scroll by less than a few lines with the mouse is the scroll-wheel interface.  That's already there in vim if you have `:set mouse=a' (and this is on in gvim by default).  But I really detest it.  It engenders a really awkward finger movement that I reserve for one activity only and it's not scrolling.  And I don't think that finger movement's good for your hand anyway and so it shouldn't be used outside of bed.  So after all of this, why not have the right-click and drag functionality in vim?  Right drag isn't used for anything else anyways.\r\n","install_details":"Either copy everything to your `.vimrc' or add `:source \/path\/to\/ez_scroll.vim' to your `.vimrc'.","5":"Either copy everything to your `.vimrc' or add `:source \/path\/to\/ez_scroll.vim' to your `.vimrc'.","first_name":"20iiid","6":"20iiid","last_name":" ","7":" ","releases":[{"0":"3141","vim_version":"7.2","1":"7.2","script_version":"1.1","2":"1.1","version_comment":"Initial upload","3":"Initial upload","package":"ez_scroll.vim","4":"ez_scroll.vim","src_id":"13294","5":"13294","creation_date":"1278350728","6":"1278350728"}]},"3140":{"script_id":"3140","0":"3140","script_name":"obsidian","1":"obsidian","script_type":"color scheme","2":"color scheme","summary":"a colorscheme based on Obsidian Coast","3":"a colorscheme based on Obsidian Coast","description":"Most KDE users are familiar with the classic Obsidian Coast colorscheme-- dark with blue selection highlights. I ported it to GVim using the excellently commented lucius colorscheme. I included some extra colors from Kate's schemata as well.\r\n\r\nScreenshot ( perl ): https:\/\/github.com\/dbb\/themes\/blob\/master\/obsidian_vim_perl.png\r\n\r\nUpdated version: https:\/\/github.com\/dbb\/vim\/blob\/master\/obsidian.vim","4":"Most KDE users are familiar with the classic Obsidian Coast colorscheme-- dark with blue selection highlights. I ported it to GVim using the excellently commented lucius colorscheme. I included some extra colors from Kate's schemata as well.\r\n\r\nScreenshot ( perl ): https:\/\/github.com\/dbb\/themes\/blob\/master\/obsidian_vim_perl.png\r\n\r\nUpdated version: https:\/\/github.com\/dbb\/vim\/blob\/master\/obsidian.vim","install_details":"% curl -O http:\/\/github.com\/dbb\/vim\/raw\/master\/obsidian.vim\r\n% mkdir -p ~\/.vim\/colors\r\n% mv obsidian.vim ~\/.vim\/colors\r\n% gvim +'colorscheme obsidian'","5":"% curl -O http:\/\/github.com\/dbb\/vim\/raw\/master\/obsidian.vim\r\n% mkdir -p ~\/.vim\/colors\r\n% mv obsidian.vim ~\/.vim\/colors\r\n% gvim +'colorscheme obsidian'","first_name":"Daniel","6":"Daniel","last_name":"B","7":"B","releases":[{"0":"3140","vim_version":"7.2","1":"7.2","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"obsidian.vim","4":"obsidian.vim","src_id":"13290","5":"13290","creation_date":"1278229923","6":"1278229923"}]},"3139":{"script_id":"3139","0":"3139","script_name":"phd","1":"phd","script_type":"color scheme","2":"color scheme","summary":"Color theme with dark blue background for coding","3":"Color theme with dark blue background for coding","description":"I'll skip long talks about how this theme looks, take a look for yourself at http:\/\/leetless.de\/vim.html\r\n\r\nNote that this theme (like all my themes) only defines colors for gvim, i.e. textmode\/console colors are not being set. Feel free to contact me for questions and suggestions, for example via the methods mentioned on http:\/\/leetless.de","4":"I'll skip long talks about how this theme looks, take a look for yourself at http:\/\/leetless.de\/vim.html\r\n\r\nNote that this theme (like all my themes) only defines colors for gvim, i.e. textmode\/console colors are not being set. Feel free to contact me for questions and suggestions, for example via the methods mentioned on http:\/\/leetless.de","install_details":"Copy the file into your color theme directory (for linux thats ~\/.vim\/colors).\r\nType\r\n:colors phd\r\nto select the theme. Use your favorite search engine or vims help system to find out more about how to use color schemes.","5":"Copy the file into your color theme directory (for linux thats ~\/.vim\/colors).\r\nType\r\n:colors phd\r\nto select the theme. Use your favorite search engine or vims help system to find out more about how to use color schemes.","first_name":"Henning","6":"Henning","last_name":"Hasemann","7":"Hasemann","releases":[{"0":"3139","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"phd.vim","4":"phd.vim","src_id":"13284","5":"13284","creation_date":"1278169532","6":"1278169532"}]},"3138":{"script_id":"3138","0":"3138","script_name":"datascript.vim","1":"datascript.vim","script_type":"syntax","2":"syntax","summary":"Syntax file for the Datascript modelling binary datatypes language","3":"Syntax file for the Datascript modelling binary datatypes language","description":"Syntax file for the Datascript modelling binary datatypes language.\r\n\r\nScreenshot of syntax highlighted datascript file with doxygen comments:\r\n  http:\/\/dominique.pelle.free.fr\/pic\/datascript-syntax.png\r\n\r\nFor more information about Datascript language, see:\r\n  http:\/\/datascript.berlios.de\/ ","4":"Syntax file for the Datascript modelling binary datatypes language.\r\n\r\nScreenshot of syntax highlighted datascript file with doxygen comments:\r\n  http:\/\/dominique.pelle.free.fr\/pic\/datascript-syntax.png\r\n\r\nFor more information about Datascript language, see:\r\n  http:\/\/datascript.berlios.de\/ ","install_details":"Save the file datascript.vim to your ~\/.vim\/syntax\/ directory\r\n(or $VIM\/vimfiles\/syntax\/ on Windows) \r\n\r\nUse  \":set filetype=datascript\" to activate datascript file type.\r\nOr you can use \":set filetype=datascript.doxygen\" to activate\r\nboth datascript and and doxygen file types.\r\n\r\nTo automatically set the datascript file type when opening\r\n*.ds files, create the following file ~\/.vim\/filetype.vim\r\n\r\nif exists(\"did_load_filetypes\")\r\n  finish\r\nendif\r\naugroup filetypedetect\r\n  au! BufRead,BufNewFile *.ds setfiletype datascript.doxygen\r\naugroup END","5":"Save the file datascript.vim to your ~\/.vim\/syntax\/ directory\r\n(or $VIM\/vimfiles\/syntax\/ on Windows) \r\n\r\nUse  \":set filetype=datascript\" to activate datascript file type.\r\nOr you can use \":set filetype=datascript.doxygen\" to activate\r\nboth datascript and and doxygen file types.\r\n\r\nTo automatically set the datascript file type when opening\r\n*.ds files, create the following file ~\/.vim\/filetype.vim\r\n\r\nif exists(\"did_load_filetypes\")\r\n  finish\r\nendif\r\naugroup filetypedetect\r\n  au! BufRead,BufNewFile *.ds setfiletype datascript.doxygen\r\naugroup END","first_name":"Dominique","6":"Dominique","last_name":"Pell\u00c3\u00a9","7":"Pell\u00c3\u00a9","releases":[{"0":"3138","vim_version":"6.0","1":"6.0","script_version":"0.7","2":"0.7","version_comment":"- added missing keywords, etc.","3":"- added missing keywords, etc.","package":"datascript.vim","4":"datascript.vim","src_id":"13285","5":"13285","creation_date":"1278180142","6":"1278180142"},{"0":"3138","vim_version":"6.0","1":"6.0","script_version":"0.6","2":"0.6","version_comment":"- Added missing highlighting for dsCommentStart","3":"- Added missing highlighting for dsCommentStart","package":"datascript.vim","4":"datascript.vim","src_id":"13282","5":"13282","creation_date":"1278158791","6":"1278158791"},{"0":"3138","vim_version":"6.0","1":"6.0","script_version":"0.5","2":"0.5","version_comment":"Initial upload","3":"Initial upload","package":"datascript.vim","4":"datascript.vim","src_id":"13281","5":"13281","creation_date":"1278158053","6":"1278158053"}]},"3137":{"script_id":"3137","0":"3137","script_name":"tac-syntax","1":"tac-syntax","script_type":"syntax","2":"syntax","summary":"Syntax for Tac files (http:\/\/slimmer.gforge.inria.fr\/tac\/)","3":"Syntax for Tac files (http:\/\/slimmer.gforge.inria.fr\/tac\/)","description":"Syntax for Tac files (http:\/\/slimmer.gforge.inria.fr\/tac\/)","4":"Syntax for Tac files (http:\/\/slimmer.gforge.inria.fr\/tac\/)","install_details":"The contents of tac-syntax\/ftdetect (resp. ftplugin, resp. syntax) goes into ~\/.vim\/ftdetect (resp. ftplugin, resp. syntax).\r\n","5":"The contents of tac-syntax\/ftdetect (resp. ftplugin, resp. syntax) goes into ~\/.vim\/ftdetect (resp. ftplugin, resp. syntax).\r\n","first_name":"Vincent","6":"Vincent","last_name":"Aravantinos","7":"Aravantinos","releases":[{"0":"3137","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"tac-syntax.tar.gz","4":"tac-syntax.tar.gz","src_id":"13279","5":"13279","creation_date":"1278058408","6":"1278058408"}]},"3136":{"script_id":"3136","0":"3136","script_name":"beluga-syntax","1":"beluga-syntax","script_type":"syntax","2":"syntax","summary":"Syntax for Beluga fles (http:\/\/www.cs.mcgill.ca\/~complogic\/beluga\/)","3":"Syntax for Beluga fles (http:\/\/www.cs.mcgill.ca\/~complogic\/beluga\/)","description":"Syntax for Beluga fles (http:\/\/www.cs.mcgill.ca\/~complogic\/beluga\/).\r\n\r\nIf colouring gets desynchronized, type <LocalLeader>s.","4":"Syntax for Beluga fles (http:\/\/www.cs.mcgill.ca\/~complogic\/beluga\/).\r\n\r\nIf colouring gets desynchronized, type <LocalLeader>s.","install_details":"The contents of beluga-syntax\/ftdetect (resp. ftplugin, resp. syntax) goes into ~\/.vim\/ftdetect (resp. ftplugin, resp. syntax).","5":"The contents of beluga-syntax\/ftdetect (resp. ftplugin, resp. syntax) goes into ~\/.vim\/ftdetect (resp. ftplugin, resp. syntax).","first_name":"Vincent","6":"Vincent","last_name":"Aravantinos","7":"Aravantinos","releases":[{"0":"3136","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"beluga-syntax.tar.gz","4":"beluga-syntax.tar.gz","src_id":"13278","5":"13278","creation_date":"1278058149","6":"1278058149"}]},"3135":{"script_id":"3135","0":"3135","script_name":"Vim Script Updater","1":"Vim Script Updater","script_type":"utility","2":"utility","summary":"Automatically update vim scripts","3":"Automatically update vim scripts","description":"This Python script updates vim scripts listed in a watch list that you create.\r\nIt converts any script to a vimball, thus allowing for easier uninstallation with :RmVimball.\r\nYou can have multiple watch lists if you want to keep things sorted.\r\n\r\nIf you don't care about vimballs and prefer a script that is run from within Vim rather than in the terminal, you can use GetLatestVimScripts: vimscript#642\r\n\r\nWhen run, it parses a watch-list file, looks for updates on www.vim.org, asks for a confirmation to download updated scripts, converts them to vimballs and installs them, and commits changes to the watch list.\r\n\r\nThe script is quite new and still needs some debugging. Please report bugs to me.\r\n\r\nIf you use a watch list from the former bash implementation, the new Python version will need to redownload all the scripts once to upgrade the watch list format. I have rewritten the script in Python to get rid of the dependencies (xsltproc, curl, etc.) of the bash version.\r\n\r\n--------------------------------------------------------------------\r\n\r\nusage: .\/vim-update-scripts.py watchlist\r\n\r\nwhere watchlist is a file containing one or more lines with the following syntax:\r\n\tscript ID\r\nor\r\n\tscript ID|prefix\r\n\r\nExample file:\r\n\t42\r\n\t1259|colors\r\n\t3096|plugin\r\n\t3108\r\n","4":"This Python script updates vim scripts listed in a watch list that you create.\r\nIt converts any script to a vimball, thus allowing for easier uninstallation with :RmVimball.\r\nYou can have multiple watch lists if you want to keep things sorted.\r\n\r\nIf you don't care about vimballs and prefer a script that is run from within Vim rather than in the terminal, you can use GetLatestVimScripts: vimscript#642\r\n\r\nWhen run, it parses a watch-list file, looks for updates on www.vim.org, asks for a confirmation to download updated scripts, converts them to vimballs and installs them, and commits changes to the watch list.\r\n\r\nThe script is quite new and still needs some debugging. Please report bugs to me.\r\n\r\nIf you use a watch list from the former bash implementation, the new Python version will need to redownload all the scripts once to upgrade the watch list format. I have rewritten the script in Python to get rid of the dependencies (xsltproc, curl, etc.) of the bash version.\r\n\r\n--------------------------------------------------------------------\r\n\r\nusage: .\/vim-update-scripts.py watchlist\r\n\r\nwhere watchlist is a file containing one or more lines with the following syntax:\r\n\tscript ID\r\nor\r\n\tscript ID|prefix\r\n\r\nExample file:\r\n\t42\r\n\t1259|colors\r\n\t3096|plugin\r\n\t3108\r\n","install_details":"1. Download the file vim-update-scripts.py\r\n2. Make it executable:\r\n        chmod +x vim-update-scripts.py\r\n3. Create a watch list:\r\n        echo -e \"42\\n1259|colors\\n3096|plugin\\n3108\" > watch-list\r\n4. Run the script once in a while:\r\n        .\/vim-update-scripts.py watch-list\r\n\r\nNote: You can change the line VIM = 'vim' at the beginning of the script to suit your needs.","5":"1. Download the file vim-update-scripts.py\r\n2. Make it executable:\r\n        chmod +x vim-update-scripts.py\r\n3. Create a watch list:\r\n        echo -e \"42\\n1259|colors\\n3096|plugin\\n3108\" > watch-list\r\n4. Run the script once in a while:\r\n        .\/vim-update-scripts.py watch-list\r\n\r\nNote: You can change the line VIM = 'vim' at the beginning of the script to suit your needs.","first_name":"David","6":"David","last_name":"Munger","7":"Munger","releases":[{"0":"3135","vim_version":"7.3","1":"7.3","script_version":"1.0.2","2":"1.0.2","version_comment":"- use the new .vmb extension for vimballs","3":"- use the new .vmb extension for vimballs","package":"vim-update-scripts.py","4":"vim-update-scripts.py","src_id":"16180","5":"16180","creation_date":"1312254232","6":"1312254232"},{"0":"3135","vim_version":"7.0","1":"7.0","script_version":"1.0.1","2":"1.0.1","version_comment":"Fix a byte\/string conversion bug that appeared with the new Python version.","3":"Fix a byte\/string conversion bug that appeared with the new Python version.","package":"vim-update-scripts.py","4":"vim-update-scripts.py","src_id":"16091","5":"16091","creation_date":"1311003503","6":"1311003503"},{"0":"3135","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"updated to Python 3","3":"updated to Python 3","package":"vim-update-scripts.py","4":"vim-update-scripts.py","src_id":"14206","5":"14206","creation_date":"1289232047","6":"1289232047"},{"0":"3135","vim_version":"7.0","1":"7.0","script_version":"0.6.0","2":"0.6.0","version_comment":"new python version\r\nif you use a watch-list from the shell-script version, the new python version will need to redownload all the scripts in the watchlist once","3":"new python version\r\nif you use a watch-list from the shell-script version, the new python version will need to redownload all the scripts in the watchlist once","package":"vim-update-scripts.py","4":"vim-update-scripts.py","src_id":"13289","5":"13289","creation_date":"1278203945","6":"1278203945"},{"0":"3135","vim_version":"7.0","1":"7.0","script_version":"0.5.1","2":"0.5.1","version_comment":"- unzip .vim.gz, .vim.bz2, .vba.gz, .vba.bz2 if needed","3":"- unzip .vim.gz, .vim.bz2, .vba.gz, .vba.bz2 if needed","package":"update-watch-list.sh","4":"update-watch-list.sh","src_id":"13277","5":"13277","creation_date":"1278005434","6":"1278005434"}]},"3134":{"script_id":"3134","0":"3134","script_name":"rvm.vim","1":"rvm.vim","script_type":"utility","2":"utility","summary":"RVM Integration","3":"RVM Integration","description":"Adds RVM (Ruby Version Manager http:\/\/rvm.beginrescueend.com\/) integration to Vim.\r\n\r\nCurrently that is a function for adding the active Ruby to the status line.\r\n\r\nLatest and greatest is on github, also that is the place to report issues http:\/\/github.com\/csexton\/rvm.vim","4":"Adds RVM (Ruby Version Manager http:\/\/rvm.beginrescueend.com\/) integration to Vim.\r\n\r\nCurrently that is a function for adding the active Ruby to the status line.\r\n\r\nLatest and greatest is on github, also that is the place to report issues http:\/\/github.com\/csexton\/rvm.vim","install_details":"Copy rvm.vim into your ~\/.vim\/plugin directory.\r\n\r\nTo add the active rvm ruby to the status line:\r\n\r\n    set statusline+=%{rvm#statusline()}\r\n\r\nOr you could get fancy and do something like this:\r\n\r\n    set statusline=[%n]\\ %<%.99f\\ %h%w%m%r%y%{exists('g:loaded_rvm')?rvm#statusline():''}%=%-16(\\ %l,%c-%v\\ %)%P\r\n\r\nHaving the \"exists\" check will degrade gracefully if you move your .vimrc around to computers that may not have the rvm.vim plugin installed.","5":"Copy rvm.vim into your ~\/.vim\/plugin directory.\r\n\r\nTo add the active rvm ruby to the status line:\r\n\r\n    set statusline+=%{rvm#statusline()}\r\n\r\nOr you could get fancy and do something like this:\r\n\r\n    set statusline=[%n]\\ %<%.99f\\ %h%w%m%r%y%{exists('g:loaded_rvm')?rvm#statusline():''}%=%-16(\\ %l,%c-%v\\ %)%P\r\n\r\nHaving the \"exists\" check will degrade gracefully if you move your .vimrc around to computers that may not have the rvm.vim plugin installed.","first_name":"Christopher","6":"Christopher","last_name":"Sexton","7":"Sexton","releases":[{"0":"3134","vim_version":"6.0","1":"6.0","script_version":"0.1.0","2":"0.1.0","version_comment":"Initial upload","3":"Initial upload","package":"rvm.vim","4":"rvm.vim","src_id":"13252","5":"13252","creation_date":"1277688676","6":"1277688676"}]},"3133":{"script_id":"3133","0":"3133","script_name":"open-browser.vim","1":"open-browser.vim","script_type":"utility","2":"utility","summary":"Open URI with your favorite browser from your most favorite editor","3":"Open URI with your favorite browser from your most favorite editor","description":"SYNOPSIS\r\n\r\n\t\" This is my setting.\r\n\tlet g:netrw_nogx = 1 \" disable netrw's gx mapping.\r\n\tnmap gx <Plug>(openbrowser-smart-search)\r\n\tvmap gx <Plug>(openbrowser-smart-search)\r\n\r\n\r\n\t\" Open URI under cursor.\r\n\tnmap map-you-like <Plug>(openbrowser-open)\r\n\t\" Open selected URI.\r\n\tvmap map-you-like <Plug>(openbrowser-open)\r\n\r\n\t\" Search word under cursor.\r\n\tnmap map-you-like <Plug>(openbrowser-search)\r\n\t\" Search selected word. vmap map-you-like <Plug>(openbrowser-search)\r\n\r\n\t\" If it looks like URI, Open URI under cursor.\r\n\t\" Otherwise, Search word under cursor.\r\n\tnmap map-you-like <Plug>(openbrowser-smart-search)\r\n\t\" If it looks like URI, Open selected URI.\r\n\t\" Otherwise, Search selected word.\r\n\tvmap map-you-like <Plug>(openbrowser-smart-search)\r\n\r\n\t\" In command-line\r\n\t:OpenBrowser http:\/\/google.com\/\r\n\t:OpenBrowserSearch ggrks\r\n\t:OpenBrowserSmartSearch http:\/\/google.com\/\r\n\t:OpenBrowserSmartSearch ggrks\r\n\r\n\r\nENVIRONMENTS\r\n\r\nWe have tested on these environments.\r\n- Ubuntu 9.10 GNOME\r\n- Windows XP\r\n- Cygwin\r\n- Mac OS X\r\n\r\nThanks for testing:\r\n- mfumi (Mac OS X)\r\n- iicebar (Windows XP)\r\n\r\nLATEST VERSION\r\nhttp:\/\/github.com\/tyru\/open-browser.vim","4":"SYNOPSIS\r\n\r\n\t\" This is my setting.\r\n\tlet g:netrw_nogx = 1 \" disable netrw's gx mapping.\r\n\tnmap gx <Plug>(openbrowser-smart-search)\r\n\tvmap gx <Plug>(openbrowser-smart-search)\r\n\r\n\r\n\t\" Open URI under cursor.\r\n\tnmap map-you-like <Plug>(openbrowser-open)\r\n\t\" Open selected URI.\r\n\tvmap map-you-like <Plug>(openbrowser-open)\r\n\r\n\t\" Search word under cursor.\r\n\tnmap map-you-like <Plug>(openbrowser-search)\r\n\t\" Search selected word. vmap map-you-like <Plug>(openbrowser-search)\r\n\r\n\t\" If it looks like URI, Open URI under cursor.\r\n\t\" Otherwise, Search word under cursor.\r\n\tnmap map-you-like <Plug>(openbrowser-smart-search)\r\n\t\" If it looks like URI, Open selected URI.\r\n\t\" Otherwise, Search selected word.\r\n\tvmap map-you-like <Plug>(openbrowser-smart-search)\r\n\r\n\t\" In command-line\r\n\t:OpenBrowser http:\/\/google.com\/\r\n\t:OpenBrowserSearch ggrks\r\n\t:OpenBrowserSmartSearch http:\/\/google.com\/\r\n\t:OpenBrowserSmartSearch ggrks\r\n\r\n\r\nENVIRONMENTS\r\n\r\nWe have tested on these environments.\r\n- Ubuntu 9.10 GNOME\r\n- Windows XP\r\n- Cygwin\r\n- Mac OS X\r\n\r\nThanks for testing:\r\n- mfumi (Mac OS X)\r\n- iicebar (Windows XP)\r\n\r\nLATEST VERSION\r\nhttp:\/\/github.com\/tyru\/open-browser.vim","install_details":"unzip zip file, and move them to ~\/.vim or ~\/vimfiles (Windows).","5":"unzip zip file, and move them to ~\/.vim or ~\/vimfiles (Windows).","first_name":"tyru","6":"tyru","last_name":" ","7":" ","releases":[{"0":"3133","vim_version":"7.4","1":"7.4","script_version":"2.0.0","2":"2.0.0","version_comment":"* [Fix] Vim hangs until a browser exits (close #68)\r\n* [Feature] Add DevDocs to search engines (#69)\r\n* [Feature] Open multiple URLs when selecting in visual-mode (#70)\r\n* [Feature] If there are no words on cursor, find next URL after cursor. (#71)\r\n* [Fix] Allow the url without dots like http:\/\/localhost\/ (#80)\r\n* [Fix] ':OpenBrowser' won't open 'http:\/\/203.0.113.11' (#82)\r\n* [Feature] Support MSYS2 (fix #92)\r\n* [Feature] Support Windows Subsystem for Linux (#105)\r\n* [Feature] Add fileformat.info as search engine\r\n* [Feature] Write internal code as vim-jp\/vital.vim modules; easily reuseable as Vim script library (vital is embeddable library and mechanism: it provides node_modules directory for Node.js, or vendor directory for Go) (#113)\r\n* More many improvements and bugfixes\r\nNOTE: this is the final release for Vim 7.4 support.","3":"* [Fix] Vim hangs until a browser exits (close #68)\r\n* [Feature] Add DevDocs to search engines (#69)\r\n* [Feature] Open multiple URLs when selecting in visual-mode (#70)\r\n* [Feature] If there are no words on cursor, find next URL after cursor. (#71)\r\n* [Fix] Allow the url without dots like http:\/\/localhost\/ (#80)\r\n* [Fix] ':OpenBrowser' won't open 'http:\/\/203.0.113.11' (#82)\r\n* [Feature] Support MSYS2 (fix #92)\r\n* [Feature] Support Windows Subsystem for Linux (#105)\r\n* [Feature] Add fileformat.info as search engine\r\n* [Feature] Write internal code as vim-jp\/vital.vim modules; easily reuseable as Vim script library (vital is embeddable library and mechanism: it provides node_modules directory for Node.js, or vendor directory for Go) (#113)\r\n* More many improvements and bugfixes\r\nNOTE: this is the final release for Vim 7.4 support.","package":"open-browser-v2.0.0.zip","4":"open-browser-v2.0.0.zip","src_id":"25873","5":"25873","creation_date":"1520771784","6":"1520771784"},{"0":"3133","vim_version":"7.0","1":"7.0","script_version":"0.1.1","2":"0.1.1","version_comment":"- Avoid hit-enter-prompt when opening URL\r\n- Add English\/Japanese menus\r\n- Allow to disable the default search engines\r\n- Add g:openbrowser_short_message\r\n- Improve URI\/URL handling\r\n- Improve vimproc.vim integration\r\n- Improve open-browser-github.vim integration\r\n- Improve ghq command integration\r\n- Change structure of g:openbrowser_browser_commands\r\n- Remove g:openbrowser_{isfname,iskeyword}\r\n- ...and fixed many many problems...","3":"- Avoid hit-enter-prompt when opening URL\r\n- Add English\/Japanese menus\r\n- Allow to disable the default search engines\r\n- Add g:openbrowser_short_message\r\n- Improve URI\/URL handling\r\n- Improve vimproc.vim integration\r\n- Improve open-browser-github.vim integration\r\n- Improve ghq command integration\r\n- Change structure of g:openbrowser_browser_commands\r\n- Remove g:openbrowser_{isfname,iskeyword}\r\n- ...and fixed many many problems...","package":"open-browser.vim-0.1.1.zip","4":"open-browser.vim-0.1.1.zip","src_id":"22958","5":"22958","creation_date":"1425124900","6":"1425124900"},{"0":"3133","vim_version":"7.0","1":"7.0","script_version":"0.0.7","2":"0.0.7","version_comment":"- Support some search engines (alphabetically)\r\n  Most search engines were suggested by stardiviner, thanks!\r\n  - Ask Ubuntu\r\n  - Baidu\r\n  - Blekko\r\n  - CPAN (search.cpan.org)\r\n  - DuckDuckGo\r\n  - GitHub\r\n  - Google Code (en)\r\n  - PHP (www.php.net)\r\n  - Python (docs.python.org)\r\n  - SPACE ALC\r\n  - Twitter Search\r\n  - Twitter (user)\r\n  - VeryCD\r\n  - Wikipedia (en)\r\n  - vim.org\r\n- Fix bug: command-line completion did not return all matched search engines,\r\n  it returned only first matched search engine.\r\n- Fix bug: if the key contains \"-\" in g:openbrowser_search_engines,\r\n  it does not work.\r\n- Change s:expand_keyword() syntax. It recognizes only {vim expression}.\r\n  (see :help openbrowser-option-syntax for details)\r\n  - Change default value of g:openbrowser_open_rules\r\n  - Change default value of g:openbrowser_search_engines","3":"- Support some search engines (alphabetically)\r\n  Most search engines were suggested by stardiviner, thanks!\r\n  - Ask Ubuntu\r\n  - Baidu\r\n  - Blekko\r\n  - CPAN (search.cpan.org)\r\n  - DuckDuckGo\r\n  - GitHub\r\n  - Google Code (en)\r\n  - PHP (www.php.net)\r\n  - Python (docs.python.org)\r\n  - SPACE ALC\r\n  - Twitter Search\r\n  - Twitter (user)\r\n  - VeryCD\r\n  - Wikipedia (en)\r\n  - vim.org\r\n- Fix bug: command-line completion did not return all matched search engines,\r\n  it returned only first matched search engine.\r\n- Fix bug: if the key contains \"-\" in g:openbrowser_search_engines,\r\n  it does not work.\r\n- Change s:expand_keyword() syntax. It recognizes only {vim expression}.\r\n  (see :help openbrowser-option-syntax for details)\r\n  - Change default value of g:openbrowser_open_rules\r\n  - Change default value of g:openbrowser_search_engines","package":"openbrowser.zip","4":"openbrowser.zip","src_id":"17003","5":"17003","creation_date":"1322749573","6":"1322749573"},{"0":"3133","vim_version":"7.0","1":"7.0","script_version":"0.0.6a","2":"0.0.6a","version_comment":"- Allow b:option, w:option, t:option not only g:option.\r\n- Fix Mac OS X environment detection.\r\n  (Thanks Chomo for the report. and sorry to forget including your name in 0.0.6 changelog. I've uploaded again.)\r\n- Fix the problem that open-browser.vim does not work on cygwin.\r\n  (Thanks toooooooby for the patch. and sorry to forget including your name in 0.0.6 changelog. I've uploaded again.)","3":"- Allow b:option, w:option, t:option not only g:option.\r\n- Fix Mac OS X environment detection.\r\n  (Thanks Chomo for the report. and sorry to forget including your name in 0.0.6 changelog. I've uploaded again.)\r\n- Fix the problem that open-browser.vim does not work on cygwin.\r\n  (Thanks toooooooby for the patch. and sorry to forget including your name in 0.0.6 changelog. I've uploaded again.)","package":"openbrowser.zip","4":"openbrowser.zip","src_id":"16984","5":"16984","creation_date":"1322376072","6":"1322376072"},{"0":"3133","vim_version":"7.0","1":"7.0","script_version":"0.0.5","2":"0.0.5","version_comment":"(NOTE: Next release will break some backward compatibility, maybe)\r\n- Document fix\/improvement\r\n- Add :command-completion to :OpenBrowserSmartSearch.\r\n- :OpenBrowserSmartSearch: allow {search-engine} option\r\n  like :OpenBrowserSearch\r\n- Minor bug fixes","3":"(NOTE: Next release will break some backward compatibility, maybe)\r\n- Document fix\/improvement\r\n- Add :command-completion to :OpenBrowserSmartSearch.\r\n- :OpenBrowserSmartSearch: allow {search-engine} option\r\n  like :OpenBrowserSearch\r\n- Minor bug fixes","package":"openbrowser.zip","4":"openbrowser.zip","src_id":"16007","5":"16007","creation_date":"1309401405","6":"1309401405"},{"0":"3133","vim_version":"7.0","1":"7.0","script_version":"0.0.4","2":"0.0.4","version_comment":"- Improve |:OpenBrowserSearch| completion\r\n- Add <Plug>(openbrowser-search)\r\n- Add <Plug>(openbrowser-smart-search)\r\n- Merge Daniel Hahler's branch. thanks!\r\n- Spawn a browser in background\r\n  - This fixes freezing when spawning a browser\r\n- Change |g:openbrowser_fix_schemes| default value\r\n  - Add pair: \"ttps\" => \"https\"\r\n- etc.","3":"- Improve |:OpenBrowserSearch| completion\r\n- Add <Plug>(openbrowser-search)\r\n- Add <Plug>(openbrowser-smart-search)\r\n- Merge Daniel Hahler's branch. thanks!\r\n- Spawn a browser in background\r\n  - This fixes freezing when spawning a browser\r\n- Change |g:openbrowser_fix_schemes| default value\r\n  - Add pair: \"ttps\" => \"https\"\r\n- etc.","package":"openbrowser.zip","4":"openbrowser.zip","src_id":"15942","5":"15942","creation_date":"1308629161","6":"1308629161"},{"0":"3133","vim_version":"7.0","1":"7.0","script_version":"0.0.3","2":"0.0.3","version_comment":"- Implement g:openbrowser_default_search.\r\n- Implement g:openbrowser_search_engines.\r\n- Implement g:openbrowser_open_filepath_in_vim.\r\n- Implement g:openbrowser_open_vim_command.\r\n- Separate plugin\/openbrowser.vim to autoload\/openbrowser.vim to save the memory.\r\n- Bundle urilib.vim (autoload\/urilib.vim)\r\n- Fix bug: openbrowser should open URI which has no scheme\r\n  (e.g.: example.com)","3":"- Implement g:openbrowser_default_search.\r\n- Implement g:openbrowser_search_engines.\r\n- Implement g:openbrowser_open_filepath_in_vim.\r\n- Implement g:openbrowser_open_vim_command.\r\n- Separate plugin\/openbrowser.vim to autoload\/openbrowser.vim to save the memory.\r\n- Bundle urilib.vim (autoload\/urilib.vim)\r\n- Fix bug: openbrowser should open URI which has no scheme\r\n  (e.g.: example.com)","package":"openbrowser.zip","4":"openbrowser.zip","src_id":"15180","5":"15180","creation_date":"1299673132","6":"1299673132"},{"0":"3133","vim_version":"7.0","1":"7.0","script_version":"0.0.2","2":"0.0.2","version_comment":"- Rename |g:openbrowser_isfname| to |g:openbrowser_iskeyword|.\r\nvariable |g:openbrowser_isfname| is still available for\r\nbackward compatibility.\r\n- Specialize |g:openbrowser_iskeyword| value to get URI in <cword>.\r\n- More readable messages.","3":"- Rename |g:openbrowser_isfname| to |g:openbrowser_iskeyword|.\r\nvariable |g:openbrowser_isfname| is still available for\r\nbackward compatibility.\r\n- Specialize |g:openbrowser_iskeyword| value to get URI in <cword>.\r\n- More readable messages.","package":"openbrowser.zip","4":"openbrowser.zip","src_id":"13256","5":"13256","creation_date":"1277737884","6":"1277737884"},{"0":"3133","vim_version":"7.0","1":"7.0","script_version":"0.0.1","2":"0.0.1","version_comment":"- Support opening file path.\r\n- Fix minor bugs.","3":"- Support opening file path.\r\n- Fix minor bugs.","package":"openbrowser.zip","4":"openbrowser.zip","src_id":"13249","5":"13249","creation_date":"1277608482","6":"1277608482"},{"0":"3133","vim_version":"7.0","1":"7.0","script_version":"0.0.0","2":"0.0.0","version_comment":"Initial upload","3":"Initial upload","package":"openbrowser.zip","4":"openbrowser.zip","src_id":"13244","5":"13244","creation_date":"1277569974","6":"1277569974"}]},"3132":{"script_id":"3132","0":"3132","script_name":"underwater-mod","1":"underwater-mod","script_type":"color scheme","2":"color scheme","summary":"Eye-pleasing dark blue scheme based on Underwater colorscheme","3":"Eye-pleasing dark blue scheme based on Underwater colorscheme","description":"Underwater-mod is a mod of Underwater [1]. Colors for NERDTree, Ruby, ERB, HAML and HTML elements are assigned. Tweaks to general colors, like vertical split, give Vim a simpler appearance.  See screenshot [2] which uses Consolas font.\r\n\r\n[1] http:\/\/www.vim.org\/scripts\/script.php?script_id=2977\r\n[2] http:\/\/img193.imageshack.us\/img193\/8104\/screenshot20100623at319.png","4":"Underwater-mod is a mod of Underwater [1]. Colors for NERDTree, Ruby, ERB, HAML and HTML elements are assigned. Tweaks to general colors, like vertical split, give Vim a simpler appearance.  See screenshot [2] which uses Consolas font.\r\n\r\n[1] http:\/\/www.vim.org\/scripts\/script.php?script_id=2977\r\n[2] http:\/\/img193.imageshack.us\/img193\/8104\/screenshot20100623at319.png","install_details":"Dowload. From terminal, copy the file to colors folder:\r\n  cp ~\/Downloads\/underwater-mod.vim ~\/.vim\/colors\r\n\r\nUsing pathogen? https:\/\/github.com\/mgutz\/vim-colors\r\n\r\nIn vim, use the color scheme:\r\n  :colo underwater-mod","5":"Dowload. From terminal, copy the file to colors folder:\r\n  cp ~\/Downloads\/underwater-mod.vim ~\/.vim\/colors\r\n\r\nUsing pathogen? https:\/\/github.com\/mgutz\/vim-colors\r\n\r\nIn vim, use the color scheme:\r\n  :colo underwater-mod","first_name":"Mario","6":"Mario","last_name":"Gutierrez","7":"Gutierrez","releases":[{"0":"3132","vim_version":"7.0","1":"7.0","script_version":"0.3","2":"0.3","version_comment":"many color tweaks","3":"many color tweaks","package":"underwater-mod.vim","4":"underwater-mod.vim","src_id":"14657","5":"14657","creation_date":"1293693388","6":"1293693388"},{"0":"3132","vim_version":"7.0","1":"7.0","script_version":"0.2","2":"0.2","version_comment":"* private\/public Ruby access\r\n* less overpowering TODO\r\n* help documents fix \r\n* markdown changes for syntax: http:\/\/www.vim.org\/scripts\/script.php?script_id=1242\r\n* HAML tag\r\n* Tab colors\r\n","3":"* private\/public Ruby access\r\n* less overpowering TODO\r\n* help documents fix \r\n* markdown changes for syntax: http:\/\/www.vim.org\/scripts\/script.php?script_id=1242\r\n* HAML tag\r\n* Tab colors\r\n","package":"underwater-mod.vim","4":"underwater-mod.vim","src_id":"13273","5":"13273","creation_date":"1277929407","6":"1277929407"},{"0":"3132","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"underwater-mod.vim","4":"underwater-mod.vim","src_id":"13237","5":"13237","creation_date":"1277332531","6":"1277332531"}]},"3131":{"script_id":"3131","0":"3131","script_name":"darkBlue","1":"darkBlue","script_type":"color scheme","2":"color scheme","summary":"A darkblue color scheme.","3":"A darkblue color scheme.","description":"This is a color scheme that I mimicked a SciTE color scheme.\r\n\r\nSee here for screenshots: http:\/\/bytefluent.com\/vivify\/index.php?remote=www.vim.org%2Fscripts%2Fdownload_script.php%3Fsrc_id%3D17648","4":"This is a color scheme that I mimicked a SciTE color scheme.\r\n\r\nSee here for screenshots: http:\/\/bytefluent.com\/vivify\/index.php?remote=www.vim.org%2Fscripts%2Fdownload_script.php%3Fsrc_id%3D17648","install_details":"","5":"","first_name":"lilydjwg","6":"lilydjwg","last_name":" ","7":" ","releases":[{"0":"3131","vim_version":"7.0","1":"7.0","script_version":"1.2","2":"1.2","version_comment":"fix Visual highlighting with vim 9.1.61.","3":"fix Visual highlighting with vim 9.1.61.","package":"darkBlue.vim","4":"darkBlue.vim","src_id":"28600","5":"28600","creation_date":"1706676209","6":"1706676209"},{"0":"3131","vim_version":"7.0","1":"7.0","script_version":"1.1","2":"1.1","version_comment":"* support for newly added CursorLineNr group","3":"* support for newly added CursorLineNr group","package":"darkBlue.vim","4":"darkBlue.vim","src_id":"17648","5":"17648","creation_date":"1332522336","6":"1332522336"},{"0":"3131","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"darkBlue.vim","4":"darkBlue.vim","src_id":"13235","5":"13235","creation_date":"1277225572","6":"1277225572"}]},"3130":{"script_id":"3130","0":"3130","script_name":"CountJump","1":"CountJump","script_type":"utility","2":"utility","summary":"Create custom motions and text objects via repeated jumps. ","3":"Create custom motions and text objects via repeated jumps. ","description":"DESCRIPTION\r\nThough it is not difficult to write a custom movement (basically a :map\r\nthat executes some kind of search or jump) and a custom text-object (an\r\n:omap that selects a range of text), this is too complex for a novice user\r\nand often repetitive.\r\nThis plugin covers the common use case where the movement and boundaries of a\r\ntext object can be specified via start and end patterns, and offers a single\r\nfunction to set up related mappings. With it, you can enhance some built-in\r\nVim mappings to take an optional [count], and quickly define new mappings for\r\nhelp file sections, diff hunks, embedded macros, and so on...\r\n\r\nAs a generalization of the start and end patterns, the movement and boundaries\r\nof a text object can also be specified via jump functions, i.e. Funcrefs of\r\nfunctions that position the cursor on the appropriate location and return that\r\nlocation. This can be used where the jump is difficult to express with a\r\nsingle regular expression, the jump may need adapting depending on the\r\ncontext, or other uses.\r\nThis plugin contains some support for movement and text objects consisting of\r\ntext regions that can be defined by continuous lines that match a particular\r\npattern, e.g. comment blocks that all start with \/^\\s*#\/.\r\n\r\nSEE ALSO\r\nThe following ftplugins use this plugin:\r\n\r\n- diff_movement.vim (vimscript #3180):\r\n  Movement over diff hunks with ]] etc.\r\n- diffwindow_movement.vim (vimscript #3719):\r\n  Movement over changes in a diff window.\r\n- dosbatch_movement.vim (vimscript #4004):\r\n  Movement over MSDOS batch file functions \/ labels with ]m etc.\r\n- fortunes_movement.vim (vimscript #3181):\r\n  Movement over email fortunes with ]] etc.\r\n- help_movement.vim (vimscript #3179):\r\n  Movement over Vim help sections with ]] etc.\r\n- mail_movement.vim (vimscript #3182):\r\n  Movement over email quotes with ]] etc.\r\n- vbs_movement.vim (vimscript #4003):\r\n  Movement over VBScript classes \/ functions \/ properties \/ subs with ]m etc.\r\n- vim_movement.vim (vimscript #4002):\r\n  Movement over Vim functions with ]m etc.\r\n\r\nThe following plugins offer new motions through this plugin:\r\n\r\n- ConflictMotions.vim (vimscript #3991):\r\n  Motions to and inside SCM conflict markers.\r\n- JumpToTrailingWhitespace.vim (vimscript #3968):\r\n  Motions to locate unwanted whitespace at the end of lines.\r\n- JumpToVerticalBlock.vim (vimscript #5657):\r\n  Like W \/ E, but vertically in the same column.\r\n- JumpToVerticalOccurrence.vim (vimscript #4841):\r\n  Like f{char}, but searching the same screen column, not line.\r\n- SameSyntaxMotion.vim (vimscript #4338):\r\n  Motions to the borders of the same syntax highlighting.\r\n- TaskMotion.vim (vimscript #3990):\r\n  Motions to task and TODO markers.\r\n\r\nRELATED WORKS\r\n- motpat.vim (vimscript #3030) offers similar functions to setup motion\r\n  mappings, but no text objects (yet).\r\n- textobj-user (vimscript #2100) has support for user-defined text objects via\r\n  regular expressions, but they don't support selecting multiple via [count].\r\n- movealong.vim (vimscript #4691) provides a :Movealong command (and optional\r\n  mappings) that repeatedly executes a motion until a condition of a syntax,\r\n  pattern match, or arbitrary expression is met.\r\n\r\nUSAGE\r\nThe plugin defines several functions, which set up the appropriate mappings\r\nbased on the arguments that you supply. The following is an overview; you'll\r\nfind the details directly in the implementation files in the\r\nautoload\/CountJump\/ directory.\r\n\r\nCountJump#Motion#MakeBracketMotion( mapArgs, keyAfterBracket, inverseKeyAfterBracket, patternToBegin, patternToEnd, isEndPatternToEnd, ... )\r\n\r\nThis function sets up mappings starting with [ and ] for movement (with\r\noptional [count]) relative to the current cursor position, targeting either a\r\ntext pattern at the beginning ([{keyAfterBracket} mapping) or a text pattern\r\nat the end (]{inverseKeyAfterBracket} mapping) of whatever you want to treat\r\nas a text block.\r\n\r\nCountJump#Motion#MakeBracketMotionWithJumpFunctions( mapArgs, keyAfterBracket, inverseKeyAfterBracket, JumpToBeginForward, JumpToBeginBackward, JumpToEndForward, JumpToEndBackward, isEndJumpToEnd, ... )\r\n\r\nThis function sets up mappings starting with [ and ] for movement (with\r\noptional [count]) relative to the current cursor position, but rely on four\r\npassed jump functions instead of text patterns to do the movement.\r\n\r\nCountJump#TextObject#MakeWithCountSearch( mapArgs, textObjectKey, types, selectionMode, patternToBegin, patternToEnd )\r\n\r\nDefines a complete set of mappings for inner and\/or outer text objects that\r\nsupport an optional [count] and are driven by search patterns for the\r\nbeginning and end of a block. Outer text objects include the matched pattern\r\ntext, inner ones not. Selection can be characterwise, linewise or blockwise.\r\n\r\nCountJump#TextObject#MakeWithJumpFunctions( mapArgs, textObjectKey, types, selectionMode, JumpToBegin, JumpToEnd )\r\n\r\nThis is a generalization of CountJump#TextObject#MakeWithCountSearch() that\r\ninvokes custom functions instead of searching for a fixed pattern. This is\r\nuseful if the check for a match is too complex for a single regular\r\nexpression, or if you need to adjust the match position depending on the\r\ncircumstances.\r\n\r\nOften, a region can be defined as a block of continuous lines that all match a\r\ncertain pattern (or, even more generic, where a provided predicate function\r\nreturns a match position). The following functions aid in implementing\r\nmovements to the boundaries of these regions and text objects consisting of\r\nthe region:\r\n\r\nCountJump#Region#JumpToRegionEnd( count, Expr, isMatch, step, isToEndOfLine )\r\n\r\nStarting from the current line, search for the position where the count'th\r\nregion ends. Use this function to build Funcrefs for forward \/ backward jumps\r\nthat can then be passed to CountJump#TextObject#MakeWithJumpFunctions().\r\n\r\nCountJump#Region#JumpToNextRegion( count, Expr, isMatch, step, isAcrossRegion, isToEndOfLine )\r\n\r\nStarting from the current line, search for the position where the count'th\r\nregion begins\/ends.\r\n\r\nCountJump#Region#Motion#MakeBracketMotion( mapArgs, keyAfterBracket, inverseKeyAfterBracket, Expr, isMatch, ... )\r\n\r\nThis function sets up mappings starting with [ and ] for movement (with\r\noptional [count]) relative to the current cursor position, targeting a text\r\nregion defined by contiguous lines that (don't) match a:Expr.\r\n\r\nCountJump#Region#TextObject#Make( mapArgs, textObjectKey, types, selectionMode, Expr, isMatch )\r\n\r\nDefines a complete set of mappings for inner and\/or outer text objects that\r\nsupport an optional [count] and select regions of lines which are defined by\r\ncontiguous lines that (don't) match a:Expr.\r\nThe inner text object comprises all lines of the region itself, while the\r\nouter text object also includes all adjacent lines above and below which do\r\nnot themselves belong to a region.\r\n\r\nThe custom Funcrefs for jumps and predicates of lines belonging to a range may\r\nbe invoked multiple times until the CountJump function arrives at its\r\ndestination. To help the Funcrefs to determine where in this sequence they\r\nare, an empty g:CountJump_MotionContext dictionary is initialized at the\r\nstart of a range motion (for pattern \/ jump functions, this isn't necessary;\r\nthere's either no custom code or just a single invocation), and an empty\r\ng:CountJump_TextObjectContext dictionary is initialized at the start of a text\r\nobject. Funcrefs can put custom information (e.g. the particular comment\r\nprefix on the current line) in there and evaluate this in subsequent\r\ninvocations.\r\n\r\nEXAMPLE\r\nLet's illustrate the usage by developing custom motions and text objects for\r\nPascal begin..end blocks.\r\n\r\nWe want to move around blocks, and override the default section movements for\r\nit:\r\n]]                      Go to [count] next start of a block.\r\n][                      Go to [count] next end of a block.\r\n[[                      Go to [count] previous start of a block.\r\n[]                      Go to [count] previous end of a block.\r\n\r\n    call CountJump#Motion#MakeBracketMotion('<buffer>', '', '', '\\c^begin\\n\\zs', '\\c^.*\\nend', 0)\r\nThe begin pattern positions the cursor on the beginning of the line following\r\nthe \"begin\" keyword, the end pattern on the beginning of the line\r\npreceding the \"end\" keyword.\r\n\r\nWe want to select a block, either including or excluding the lines with the\r\nbegin..end keywords:\r\nib                      \"inner block\" text object, select [count] contents of\r\n                        a block.\r\nab                      \"a block\" text object, select [count] blocks.\r\n\r\n    call CountJump#TextObject#MakeWithCountSearch('<buffer>', 'b', 'ai', 'V', '\\c^begin\\n', '\\c^end.*$')\r\n\r\nIf there is a filetype detection for Pascal files, we can simply put the\r\nabove calls in a ~\/.vim\/ftplugin\/pascal_movement.vim script and are done.","4":"DESCRIPTION\r\nThough it is not difficult to write a custom movement (basically a :map\r\nthat executes some kind of search or jump) and a custom text-object (an\r\n:omap that selects a range of text), this is too complex for a novice user\r\nand often repetitive.\r\nThis plugin covers the common use case where the movement and boundaries of a\r\ntext object can be specified via start and end patterns, and offers a single\r\nfunction to set up related mappings. With it, you can enhance some built-in\r\nVim mappings to take an optional [count], and quickly define new mappings for\r\nhelp file sections, diff hunks, embedded macros, and so on...\r\n\r\nAs a generalization of the start and end patterns, the movement and boundaries\r\nof a text object can also be specified via jump functions, i.e. Funcrefs of\r\nfunctions that position the cursor on the appropriate location and return that\r\nlocation. This can be used where the jump is difficult to express with a\r\nsingle regular expression, the jump may need adapting depending on the\r\ncontext, or other uses.\r\nThis plugin contains some support for movement and text objects consisting of\r\ntext regions that can be defined by continuous lines that match a particular\r\npattern, e.g. comment blocks that all start with \/^\\s*#\/.\r\n\r\nSEE ALSO\r\nThe following ftplugins use this plugin:\r\n\r\n- diff_movement.vim (vimscript #3180):\r\n  Movement over diff hunks with ]] etc.\r\n- diffwindow_movement.vim (vimscript #3719):\r\n  Movement over changes in a diff window.\r\n- dosbatch_movement.vim (vimscript #4004):\r\n  Movement over MSDOS batch file functions \/ labels with ]m etc.\r\n- fortunes_movement.vim (vimscript #3181):\r\n  Movement over email fortunes with ]] etc.\r\n- help_movement.vim (vimscript #3179):\r\n  Movement over Vim help sections with ]] etc.\r\n- mail_movement.vim (vimscript #3182):\r\n  Movement over email quotes with ]] etc.\r\n- vbs_movement.vim (vimscript #4003):\r\n  Movement over VBScript classes \/ functions \/ properties \/ subs with ]m etc.\r\n- vim_movement.vim (vimscript #4002):\r\n  Movement over Vim functions with ]m etc.\r\n\r\nThe following plugins offer new motions through this plugin:\r\n\r\n- ConflictMotions.vim (vimscript #3991):\r\n  Motions to and inside SCM conflict markers.\r\n- JumpToTrailingWhitespace.vim (vimscript #3968):\r\n  Motions to locate unwanted whitespace at the end of lines.\r\n- JumpToVerticalBlock.vim (vimscript #5657):\r\n  Like W \/ E, but vertically in the same column.\r\n- JumpToVerticalOccurrence.vim (vimscript #4841):\r\n  Like f{char}, but searching the same screen column, not line.\r\n- SameSyntaxMotion.vim (vimscript #4338):\r\n  Motions to the borders of the same syntax highlighting.\r\n- TaskMotion.vim (vimscript #3990):\r\n  Motions to task and TODO markers.\r\n\r\nRELATED WORKS\r\n- motpat.vim (vimscript #3030) offers similar functions to setup motion\r\n  mappings, but no text objects (yet).\r\n- textobj-user (vimscript #2100) has support for user-defined text objects via\r\n  regular expressions, but they don't support selecting multiple via [count].\r\n- movealong.vim (vimscript #4691) provides a :Movealong command (and optional\r\n  mappings) that repeatedly executes a motion until a condition of a syntax,\r\n  pattern match, or arbitrary expression is met.\r\n\r\nUSAGE\r\nThe plugin defines several functions, which set up the appropriate mappings\r\nbased on the arguments that you supply. The following is an overview; you'll\r\nfind the details directly in the implementation files in the\r\nautoload\/CountJump\/ directory.\r\n\r\nCountJump#Motion#MakeBracketMotion( mapArgs, keyAfterBracket, inverseKeyAfterBracket, patternToBegin, patternToEnd, isEndPatternToEnd, ... )\r\n\r\nThis function sets up mappings starting with [ and ] for movement (with\r\noptional [count]) relative to the current cursor position, targeting either a\r\ntext pattern at the beginning ([{keyAfterBracket} mapping) or a text pattern\r\nat the end (]{inverseKeyAfterBracket} mapping) of whatever you want to treat\r\nas a text block.\r\n\r\nCountJump#Motion#MakeBracketMotionWithJumpFunctions( mapArgs, keyAfterBracket, inverseKeyAfterBracket, JumpToBeginForward, JumpToBeginBackward, JumpToEndForward, JumpToEndBackward, isEndJumpToEnd, ... )\r\n\r\nThis function sets up mappings starting with [ and ] for movement (with\r\noptional [count]) relative to the current cursor position, but rely on four\r\npassed jump functions instead of text patterns to do the movement.\r\n\r\nCountJump#TextObject#MakeWithCountSearch( mapArgs, textObjectKey, types, selectionMode, patternToBegin, patternToEnd )\r\n\r\nDefines a complete set of mappings for inner and\/or outer text objects that\r\nsupport an optional [count] and are driven by search patterns for the\r\nbeginning and end of a block. Outer text objects include the matched pattern\r\ntext, inner ones not. Selection can be characterwise, linewise or blockwise.\r\n\r\nCountJump#TextObject#MakeWithJumpFunctions( mapArgs, textObjectKey, types, selectionMode, JumpToBegin, JumpToEnd )\r\n\r\nThis is a generalization of CountJump#TextObject#MakeWithCountSearch() that\r\ninvokes custom functions instead of searching for a fixed pattern. This is\r\nuseful if the check for a match is too complex for a single regular\r\nexpression, or if you need to adjust the match position depending on the\r\ncircumstances.\r\n\r\nOften, a region can be defined as a block of continuous lines that all match a\r\ncertain pattern (or, even more generic, where a provided predicate function\r\nreturns a match position). The following functions aid in implementing\r\nmovements to the boundaries of these regions and text objects consisting of\r\nthe region:\r\n\r\nCountJump#Region#JumpToRegionEnd( count, Expr, isMatch, step, isToEndOfLine )\r\n\r\nStarting from the current line, search for the position where the count'th\r\nregion ends. Use this function to build Funcrefs for forward \/ backward jumps\r\nthat can then be passed to CountJump#TextObject#MakeWithJumpFunctions().\r\n\r\nCountJump#Region#JumpToNextRegion( count, Expr, isMatch, step, isAcrossRegion, isToEndOfLine )\r\n\r\nStarting from the current line, search for the position where the count'th\r\nregion begins\/ends.\r\n\r\nCountJump#Region#Motion#MakeBracketMotion( mapArgs, keyAfterBracket, inverseKeyAfterBracket, Expr, isMatch, ... )\r\n\r\nThis function sets up mappings starting with [ and ] for movement (with\r\noptional [count]) relative to the current cursor position, targeting a text\r\nregion defined by contiguous lines that (don't) match a:Expr.\r\n\r\nCountJump#Region#TextObject#Make( mapArgs, textObjectKey, types, selectionMode, Expr, isMatch )\r\n\r\nDefines a complete set of mappings for inner and\/or outer text objects that\r\nsupport an optional [count] and select regions of lines which are defined by\r\ncontiguous lines that (don't) match a:Expr.\r\nThe inner text object comprises all lines of the region itself, while the\r\nouter text object also includes all adjacent lines above and below which do\r\nnot themselves belong to a region.\r\n\r\nThe custom Funcrefs for jumps and predicates of lines belonging to a range may\r\nbe invoked multiple times until the CountJump function arrives at its\r\ndestination. To help the Funcrefs to determine where in this sequence they\r\nare, an empty g:CountJump_MotionContext dictionary is initialized at the\r\nstart of a range motion (for pattern \/ jump functions, this isn't necessary;\r\nthere's either no custom code or just a single invocation), and an empty\r\ng:CountJump_TextObjectContext dictionary is initialized at the start of a text\r\nobject. Funcrefs can put custom information (e.g. the particular comment\r\nprefix on the current line) in there and evaluate this in subsequent\r\ninvocations.\r\n\r\nEXAMPLE\r\nLet's illustrate the usage by developing custom motions and text objects for\r\nPascal begin..end blocks.\r\n\r\nWe want to move around blocks, and override the default section movements for\r\nit:\r\n]]                      Go to [count] next start of a block.\r\n][                      Go to [count] next end of a block.\r\n[[                      Go to [count] previous start of a block.\r\n[]                      Go to [count] previous end of a block.\r\n\r\n    call CountJump#Motion#MakeBracketMotion('<buffer>', '', '', '\\c^begin\\n\\zs', '\\c^.*\\nend', 0)\r\nThe begin pattern positions the cursor on the beginning of the line following\r\nthe \"begin\" keyword, the end pattern on the beginning of the line\r\npreceding the \"end\" keyword.\r\n\r\nWe want to select a block, either including or excluding the lines with the\r\nbegin..end keywords:\r\nib                      \"inner block\" text object, select [count] contents of\r\n                        a block.\r\nab                      \"a block\" text object, select [count] blocks.\r\n\r\n    call CountJump#TextObject#MakeWithCountSearch('<buffer>', 'b', 'ai', 'V', '\\c^begin\\n', '\\c^end.*$')\r\n\r\nIf there is a filetype detection for Pascal files, we can simply put the\r\nabove calls in a ~\/.vim\/ftplugin\/pascal_movement.vim script and are done.","install_details":"INSTALLATION\r\nThe code is hosted in a Git repo at\r\n    https:\/\/github.com\/inkarkat\/vim-CountJump\r\nYou can use your favorite plugin manager, or \"git clone\" into a directory used\r\nfor Vim packages. Releases are on the \"stable\" branch, the latest unstable\r\ndevelopment snapshot on \"master\".\r\n\r\nThis script is also packaged as a vimball. If you have the \"gunzip\"\r\ndecompressor in your PATH, simply edit the *.vmb.gz package in Vim; otherwise,\r\ndecompress the archive first, e.g. using WinZip. Inside Vim, install by\r\nsourcing the vimball or via the :UseVimball command.\r\n    vim CountJump*.vmb.gz\r\n    :so %\r\nTo uninstall, use the :RmVimball command.\r\n\r\nDEPENDENCIES\r\n- Requires Vim 7.0 or higher.\r\n- Requires the ingo-library.vim plugin (vimscript #4433), version 1.041 or\r\n  higher.\r\n\r\nINTEGRATION\r\nIf you want to define motions that do not start with [ \/ ], and the plugin\r\nthat employs CountJump offers a configuration variable like\r\ng:PluginName_mapping to influence the mapped key(s), you can define\r\nintermediate <Plug>-mappings (using-<Plug>), and then define your own custom\r\nmappings based on them:\r\n    let g:PluginName_mapping = '<Plug>PluginName%s'\r\n    nmap { <Plug>PluginNameBackward\r\n    nmap } <Plug>PluginNameForward\r\n    omap { <Plug>PluginNameBackward\r\n    omap } <Plug>PluginNameForward\r\n    vmap { <Plug>PluginNameBackward\r\n    vmap } <Plug>PluginNameForward\r\n\r\nIf you want to define text objects that do not start with i \/ a, and the plugin\r\nthat employs CountJump offers a configuration variable like\r\ng:PluginName_mapping to influence the mapped key(s), you can define\r\nintermediate <Plug>-mappings (using-<Plug>), and then define your own custom\r\nmappings based on them:\r\n    let g:PluginName_mapping = '<Plug>PluginName%s'\r\n    omap ,p <Plug>PluginNameInner\r\n    omap ,P <Plug>PluginNameOuter\r\n    vmap ,p <Plug>PluginNameInner\r\n    vmap ,P <Plug>PluginNameOuter","5":"INSTALLATION\r\nThe code is hosted in a Git repo at\r\n    https:\/\/github.com\/inkarkat\/vim-CountJump\r\nYou can use your favorite plugin manager, or \"git clone\" into a directory used\r\nfor Vim packages. Releases are on the \"stable\" branch, the latest unstable\r\ndevelopment snapshot on \"master\".\r\n\r\nThis script is also packaged as a vimball. If you have the \"gunzip\"\r\ndecompressor in your PATH, simply edit the *.vmb.gz package in Vim; otherwise,\r\ndecompress the archive first, e.g. using WinZip. Inside Vim, install by\r\nsourcing the vimball or via the :UseVimball command.\r\n    vim CountJump*.vmb.gz\r\n    :so %\r\nTo uninstall, use the :RmVimball command.\r\n\r\nDEPENDENCIES\r\n- Requires Vim 7.0 or higher.\r\n- Requires the ingo-library.vim plugin (vimscript #4433), version 1.041 or\r\n  higher.\r\n\r\nINTEGRATION\r\nIf you want to define motions that do not start with [ \/ ], and the plugin\r\nthat employs CountJump offers a configuration variable like\r\ng:PluginName_mapping to influence the mapped key(s), you can define\r\nintermediate <Plug>-mappings (using-<Plug>), and then define your own custom\r\nmappings based on them:\r\n    let g:PluginName_mapping = '<Plug>PluginName%s'\r\n    nmap { <Plug>PluginNameBackward\r\n    nmap } <Plug>PluginNameForward\r\n    omap { <Plug>PluginNameBackward\r\n    omap } <Plug>PluginNameForward\r\n    vmap { <Plug>PluginNameBackward\r\n    vmap } <Plug>PluginNameForward\r\n\r\nIf you want to define text objects that do not start with i \/ a, and the plugin\r\nthat employs CountJump offers a configuration variable like\r\ng:PluginName_mapping to influence the mapped key(s), you can define\r\nintermediate <Plug>-mappings (using-<Plug>), and then define your own custom\r\nmappings based on them:\r\n    let g:PluginName_mapping = '<Plug>PluginName%s'\r\n    omap ,p <Plug>PluginNameInner\r\n    omap ,P <Plug>PluginNameOuter\r\n    vmap ,p <Plug>PluginNameInner\r\n    vmap ,P <Plug>PluginNameOuter","first_name":"Ingo","6":"Ingo","last_name":"Karkat","7":"Karkat","releases":[{"0":"3130","vim_version":"7.0","1":"7.0","script_version":"1.91","2":"1.91","version_comment":"- ENH: Allow Funcref for a:searchArguments \/ first search argument \/ a:patternTo{Begin,End}\r\n- ENH: Allow to influence given [count] via CountJump#CountCountJumpWithWrapMessage() variant of CountJump#CountJumpWithWrapMessage().\r\n- FIX: Avoid \"Error detected while processing :\" additional line above an exception thrown (from a client-supplied Funcref).\r\n- ENH: Allow client-supplied Funcrefs to throw a \"CountJump: <error text>\" exception to issue custom errors.\r\n- Prevent a custom text object from clobbering the register passed to a custom operator (as :omaps defined by this plugin). *** You need to update to ingo-library (vimscript #4433) version 1.041! ***","3":"- ENH: Allow Funcref for a:searchArguments \/ first search argument \/ a:patternTo{Begin,End}\r\n- ENH: Allow to influence given [count] via CountJump#CountCountJumpWithWrapMessage() variant of CountJump#CountJumpWithWrapMessage().\r\n- FIX: Avoid \"Error detected while processing :\" additional line above an exception thrown (from a client-supplied Funcref).\r\n- ENH: Allow client-supplied Funcrefs to throw a \"CountJump: <error text>\" exception to issue custom errors.\r\n- Prevent a custom text object from clobbering the register passed to a custom operator (as :omaps defined by this plugin). *** You need to update to ingo-library (vimscript #4433) version 1.041! ***","package":"CountJump-1.91.vmb.gz","4":"CountJump-1.91.vmb.gz","src_id":"27100","5":"27100","creation_date":"1585970759","6":"1585970759"},{"0":"3130","vim_version":"7.0","1":"7.0","script_version":"1.90","2":"1.90","version_comment":"- Rename g:CountJump_Context to g:CountJump_MotionContext, to avoid a clash with the text object in CountJump#TextObject#TextObjectWithJumpFunctions(). Clear g:CountJump_MotionContext at the end of the function.\r\n- Rename g:CountJump_Context to g:CountJump_TextObjectContext. When using CountJump#Region#TextObject#Make(), the generated jump functions also set that context, and there's a clash with CountJump#TextObject#TextObjectWithJumpFunctions(). In particular, one cannot store a context for the entire text object (both jumps to begin and end), as the individual jump functions clear the identical context. Clear g:CountJump_TextObjectContext at the end of the function.\r\n- ENH: Support non-argument Funcref for a:Expr that gets evaluated once at the beginning, and should yield a regular expression that is then used in its stead.","3":"- Rename g:CountJump_Context to g:CountJump_MotionContext, to avoid a clash with the text object in CountJump#TextObject#TextObjectWithJumpFunctions(). Clear g:CountJump_MotionContext at the end of the function.\r\n- Rename g:CountJump_Context to g:CountJump_TextObjectContext. When using CountJump#Region#TextObject#Make(), the generated jump functions also set that context, and there's a clash with CountJump#TextObject#TextObjectWithJumpFunctions(). In particular, one cannot store a context for the entire text object (both jumps to begin and end), as the individual jump functions clear the identical context. Clear g:CountJump_TextObjectContext at the end of the function.\r\n- ENH: Support non-argument Funcref for a:Expr that gets evaluated once at the beginning, and should yield a regular expression that is then used in its stead.","package":"CountJump-1.90.vmb.gz","4":"CountJump-1.90.vmb.gz","src_id":"25823","5":"25823","creation_date":"1518371255","6":"1518371255"},{"0":"3130","vim_version":"7.0","1":"7.0","script_version":"1.86","2":"1.86","version_comment":"- CountJump#Motion#MakeBracketMotion(): The a:patternToBegin, a:patternToEnd, a:searchName arguments may contain special characters that need escaping in a map. Use ingo#escape#command#mapescape().\r\n- CountJump#Region#Motion#MakeBracketMotion(): The a:Expr argument may contain special characters that need escaping in a map. Use ingo#escape#command#mapescape().\r\n- Retire duplicated fallback for ingo#motion#helper#AdditionalMovement(); since version 1.85, the ingo-library is now a mandatory dependency.\r\n- CountJump#Motion#MakeBracketMotionWithJumpFunctions(), CountJump#TextObject#MakeWithJumpFunctions(), CountJump#Region#Motion#MakeBracketMotion(): Catch all exceptions and report only the text. My ErrorMotion.vim plugin could be slow to find the next error if there is none. Aborting with <C-c> would print a long multi-line exception: \"Error detected while processing function ErrorMotion#Forward[1]..CountJump#JumpFunc[39]..HlgroupMotion#JumpWithWrapMessage[26]..CountJump#CountJumpFuncWithWrapMessage[35]..HlgroupMotion#SearchFirstHlgroup: line   67: Interrupted\". As we apparently cannot avoid the printing of \"Type :quit<Enter>  to exit Vim\", suppress the Vim:Interrupt exception, and :echoerr all others.","3":"- CountJump#Motion#MakeBracketMotion(): The a:patternToBegin, a:patternToEnd, a:searchName arguments may contain special characters that need escaping in a map. Use ingo#escape#command#mapescape().\r\n- CountJump#Region#Motion#MakeBracketMotion(): The a:Expr argument may contain special characters that need escaping in a map. Use ingo#escape#command#mapescape().\r\n- Retire duplicated fallback for ingo#motion#helper#AdditionalMovement(); since version 1.85, the ingo-library is now a mandatory dependency.\r\n- CountJump#Motion#MakeBracketMotionWithJumpFunctions(), CountJump#TextObject#MakeWithJumpFunctions(), CountJump#Region#Motion#MakeBracketMotion(): Catch all exceptions and report only the text. My ErrorMotion.vim plugin could be slow to find the next error if there is none. Aborting with <C-c> would print a long multi-line exception: \"Error detected while processing function ErrorMotion#Forward[1]..CountJump#JumpFunc[39]..HlgroupMotion#JumpWithWrapMessage[26]..CountJump#CountJumpFuncWithWrapMessage[35]..HlgroupMotion#SearchFirstHlgroup: line   67: Interrupted\". As we apparently cannot avoid the printing of \"Type :quit<Enter>  to exit Vim\", suppress the Vim:Interrupt exception, and :echoerr all others.","package":"CountJump-1.86.vmb.gz","4":"CountJump-1.86.vmb.gz","src_id":"25441","5":"25441","creation_date":"1500880997","6":"1500880997"},{"0":"3130","vim_version":"7.0","1":"7.0","script_version":"1.85","2":"1.85","version_comment":"- Use ingo\/pos.vim.\r\n- Use ingo#msg#WarningMsg().\r\n- Make test for 'virtualedit' option values also account for multiple values. *** You need to update to ingo-library (vimscript #4433) version 1.019! ***","3":"- Use ingo\/pos.vim.\r\n- Use ingo#msg#WarningMsg().\r\n- Make test for 'virtualedit' option values also account for multiple values. *** You need to update to ingo-library (vimscript #4433) version 1.019! ***","package":"CountJump-1.85.vmb.gz","4":"CountJump-1.85.vmb.gz","src_id":"22719","5":"22719","creation_date":"1419333606","6":"1419333606"},{"0":"3130","vim_version":"7.0","1":"7.0","script_version":"1.84","2":"1.84","version_comment":"- Pin down the 'virtualedit' setting (to \"onemore\") during CountJump#TextObject#TextObjectWithJumpFunctions() to avoid that a characterwise outer text object that ends at the end of a line includes the line's newline character when 'selection' is \"exclusive\".\r\n- FIX: There are no buffer-local functions with a b: scope prefix, and Vim 7.4.264 disallows those invalid function names now. Previously, multiple buffer-local text objects with the same key would override each other. Instead, make the functions created by CountJump#TextObject#MakeWithCountSearch() and CountJump#Region#TextObject#Make() buffer-scoped by prefixing \"s:B\" and the buffer number.","3":"- Pin down the 'virtualedit' setting (to \"onemore\") during CountJump#TextObject#TextObjectWithJumpFunctions() to avoid that a characterwise outer text object that ends at the end of a line includes the line's newline character when 'selection' is \"exclusive\".\r\n- FIX: There are no buffer-local functions with a b: scope prefix, and Vim 7.4.264 disallows those invalid function names now. Previously, multiple buffer-local text objects with the same key would override each other. Instead, make the functions created by CountJump#TextObject#MakeWithCountSearch() and CountJump#Region#TextObject#Make() buffer-scoped by prefixing \"s:B\" and the buffer number.","package":"CountJump-1.84.vmb.gz","4":"CountJump-1.84.vmb.gz","src_id":"21828","5":"21828","creation_date":"1398434274","6":"1398434274"},{"0":"3130","vim_version":"7.0","1":"7.0","script_version":"1.83","2":"1.83","version_comment":"- Use more canonical way of invoking the Funcrefs in CountJump#Motion#MakeBracketMotionWithJumpFunctions(); this will then also work with passed String function names.\r\n- FIX: Need to save v:count1 before issuing the normal mode \"gv\" command.\r\n- Minor: Make substitute() robust against 'ignorecase'.\r\n- Add optional dependency to ingo-library (vimscript #4433).\r\n- FIX: In text objects, when the end position is before the begin position, that's not a valid selection. Test for this and abort in that case.\r\n- For linewise selections, always position the cursor at the start of the end line to be consistent with the built-in text objects, and to avoid complicating the search patterns when attempting to do this through them.","3":"- Use more canonical way of invoking the Funcrefs in CountJump#Motion#MakeBracketMotionWithJumpFunctions(); this will then also work with passed String function names.\r\n- FIX: Need to save v:count1 before issuing the normal mode \"gv\" command.\r\n- Minor: Make substitute() robust against 'ignorecase'.\r\n- Add optional dependency to ingo-library (vimscript #4433).\r\n- FIX: In text objects, when the end position is before the begin position, that's not a valid selection. Test for this and abort in that case.\r\n- For linewise selections, always position the cursor at the start of the end line to be consistent with the built-in text objects, and to avoid complicating the search patterns when attempting to do this through them.","package":"CountJump-1.83.vmb.gz","4":"CountJump-1.83.vmb.gz","src_id":"21361","5":"21361","creation_date":"1390462109","6":"1390462109"},{"0":"3130","vim_version":"7.0","1":"7.0","script_version":"1.81","2":"1.81","version_comment":"- ENH: Add optional a:searchName argument to CountJump#Motion#MakeBracketMotion() to make searches wrap around when 'wrapscan' is set. Custom jump functions can do this since version 1.70; now, this can also be utilized by motions defined via a search pattern.\r\n- BUG: Wrong variable scope for copied a:isBackward in CountJump#CountSearchWithWrapMessage().","3":"- ENH: Add optional a:searchName argument to CountJump#Motion#MakeBracketMotion() to make searches wrap around when 'wrapscan' is set. Custom jump functions can do this since version 1.70; now, this can also be utilized by motions defined via a search pattern.\r\n- BUG: Wrong variable scope for copied a:isBackward in CountJump#CountSearchWithWrapMessage().","package":"CountJump-1.81.vmb.gz","4":"CountJump-1.81.vmb.gz","src_id":"18817","5":"18817","creation_date":"1350392703","6":"1350392703"},{"0":"3130","vim_version":"7.0","1":"7.0","script_version":"1.80","2":"1.80","version_comment":"- FIX: In CountJump#TextObject#TextObjectWithJumpFunctions(), do not beep when there's no end position. In this case, the jump function (often CountJump#CountSearch()) should have emitted a beep already, and we want to avoid a double beep.\r\n- Also handle move to the buffer's very last character in operator-pending mode with a pattern to end \"O\" motion.\r\n- Add CountJump#CountJumpFuncWithWrapMessage() \/ CountJump#CountJumpFunc() to help implement custom motions with only a simple function that performs a single jump.\r\n- FIX: Visual end pattern \/ jump to end with 'selection' set to \"exclusive\" also requires the special additional treatment of moving one right, like operator-pending mode.\r\n- BUG: Operator-pending motion with end pattern \/ jump to end operates on one character too few when moving to begin.\r\n- Clear any previous wrap message when wrapping is enabled; it's confusing otherwise.","3":"- FIX: In CountJump#TextObject#TextObjectWithJumpFunctions(), do not beep when there's no end position. In this case, the jump function (often CountJump#CountSearch()) should have emitted a beep already, and we want to avoid a double beep.\r\n- Also handle move to the buffer's very last character in operator-pending mode with a pattern to end \"O\" motion.\r\n- Add CountJump#CountJumpFuncWithWrapMessage() \/ CountJump#CountJumpFunc() to help implement custom motions with only a simple function that performs a single jump.\r\n- FIX: Visual end pattern \/ jump to end with 'selection' set to \"exclusive\" also requires the special additional treatment of moving one right, like operator-pending mode.\r\n- BUG: Operator-pending motion with end pattern \/ jump to end operates on one character too few when moving to begin.\r\n- Clear any previous wrap message when wrapping is enabled; it's confusing otherwise.","package":"CountJump-1.80.vmb.gz","4":"CountJump-1.80.vmb.gz","src_id":"18807","5":"18807","creation_date":"1350285093","6":"1350285093"},{"0":"3130","vim_version":"7.0","1":"7.0","script_version":"1.70","2":"1.70","version_comment":"- ENH: Check for searches wrapping around the buffer and issue a corresponding warning, like the built-in searches do. Though the mappings that can be made with CountJump currently do not use 'wrapscan', other plugins that define their own jump functions and use the CountJump#CountJump() function for it may use it. Create function overloads CountJump#CountJumpWithWrapMessage() and CountJump#CountSearchWithWrapMessage().","3":"- ENH: Check for searches wrapping around the buffer and issue a corresponding warning, like the built-in searches do. Though the mappings that can be made with CountJump currently do not use 'wrapscan', other plugins that define their own jump functions and use the CountJump#CountJump() function for it may use it. Create function overloads CountJump#CountJumpWithWrapMessage() and CountJump#CountSearchWithWrapMessage().","package":"CountJump-1.70.vmb.gz","4":"CountJump-1.70.vmb.gz","src_id":"18535","5":"18535","creation_date":"1346664369","6":"1346664369"},{"0":"3130","vim_version":"7.0","1":"7.0","script_version":"1.60","2":"1.60","version_comment":"- ENH: Allow motions that do not start with [ \/ ] and text objects that do not start with i \/ a by passing keys that begin with <Plug>. With this, plugins using CountJump can offer the expected customizability.","3":"- ENH: Allow motions that do not start with [ \/ ] and text objects that do not start with i \/ a by passing keys that begin with <Plug>. With this, plugins using CountJump can offer the expected customizability.","package":"CountJump.vba.gz","4":"CountJump.vba.gz","src_id":"17667","5":"17667","creation_date":"1332851582","6":"1332851582"},{"0":"3130","vim_version":"7.0","1":"7.0","script_version":"1.50","2":"1.50","version_comment":"- For regions of lines, also support a match()-like Funcref instead of a pattern to define the range. This for example enables to define a range of diff changes via a predicate function that checks diff_hlID() != 0. \r\n- Initialize global g:CountJump_Context object for custom use by Funcrefs. ","3":"- For regions of lines, also support a match()-like Funcref instead of a pattern to define the range. This for example enables to define a range of diff changes via a predicate function that checks diff_hlID() != 0. \r\n- Initialize global g:CountJump_Context object for custom use by Funcrefs. ","package":"CountJump.vba.gz","4":"CountJump.vba.gz","src_id":"16407","5":"16407","creation_date":"1314774991","6":"1314774991"},{"0":"3130","vim_version":"7.0","1":"7.0","script_version":"1.41","2":"1.41","version_comment":"FIX: Directly ring the bell to avoid problems when running under :silent!. ","3":"FIX: Directly ring the bell to avoid problems when running under :silent!. ","package":"CountJump.vba.gz","4":"CountJump.vba.gz","src_id":"15870","5":"15870","creation_date":"1307972538","6":"1307972538"},{"0":"3130","vim_version":"7.0","1":"7.0","script_version":"1.40","2":"1.40","version_comment":"- ENH: Added CountJump#Region#TextObject#Make() to easily define text objects for regions. \r\n- Interface change: Jump functions again return position (and actual, corrected one for a:isToEndOfLine). Though the position is not used for motions, it is necessary for text objects to differentiate between \"already at the begin\/end position\" and \"no such position\".  ","3":"- ENH: Added CountJump#Region#TextObject#Make() to easily define text objects for regions. \r\n- Interface change: Jump functions again return position (and actual, corrected one for a:isToEndOfLine). Though the position is not used for motions, it is necessary for text objects to differentiate between \"already at the begin\/end position\" and \"no such position\".  ","package":"CountJump.vba.gz","4":"CountJump.vba.gz","src_id":"14587","5":"14587","creation_date":"1292856160","6":"1292856160"},{"0":"3130","vim_version":"7.0","1":"7.0","script_version":"1.30","2":"1.30","version_comment":"- ENH: Added CountJump#Region#Motion#MakeBracketMotion() to easily define bracket motions for regions. \r\n- Interface changes: \r\n  - Jump functions don't necessarily return jump position any more; this special case is only required for text objects. \r\n  - Moved CountJump#Region#Jump() to CountJump#JumpFunc(). \r\n  - Added a:isToEndOfLine argument to CountJump#Region#JumpToRegionEnd() and CountJump#Region#JumpToNextRegion(), which is useful for operator-pending and characterwise visual mode mappings; the entire last line will then be operated on \/ selected. \r\n  - Added a:isMatch argument to CountJump#Region#SearchForRegionEnd(), CountJump#Region#JumpToRegionEnd(), CountJump#Region#SearchForNextRegion(), CountJump#Region#JumpToNextRegion(). This allows definition of regions via non-matches, which can be substantially simpler (and faster to match) than coming up with a \"negative\" regular expression.","3":"- ENH: Added CountJump#Region#Motion#MakeBracketMotion() to easily define bracket motions for regions. \r\n- Interface changes: \r\n  - Jump functions don't necessarily return jump position any more; this special case is only required for text objects. \r\n  - Moved CountJump#Region#Jump() to CountJump#JumpFunc(). \r\n  - Added a:isToEndOfLine argument to CountJump#Region#JumpToRegionEnd() and CountJump#Region#JumpToNextRegion(), which is useful for operator-pending and characterwise visual mode mappings; the entire last line will then be operated on \/ selected. \r\n  - Added a:isMatch argument to CountJump#Region#SearchForRegionEnd(), CountJump#Region#JumpToRegionEnd(), CountJump#Region#SearchForNextRegion(), CountJump#Region#JumpToNextRegion(). This allows definition of regions via non-matches, which can be substantially simpler (and faster to match) than coming up with a \"negative\" regular expression.","package":"CountJump.vba.gz","4":"CountJump.vba.gz","src_id":"14581","5":"14581","creation_date":"1292835466","6":"1292835466"},{"0":"3130","vim_version":"7.0","1":"7.0","script_version":"1.22","2":"1.22","version_comment":"- No more motion mappings and text objects for select mode; as the mappings start with a printable character, no select-mode mapping should be defined. ","3":"- No more motion mappings and text objects for select mode; as the mappings start with a printable character, no select-mode mapping should be defined. ","package":"CountJump.vba.gz","4":"CountJump.vba.gz","src_id":"13502","5":"13502","creation_date":"1281121508","6":"1281121508"},{"0":"3130","vim_version":"7.0","1":"7.0","script_version":"1.21","2":"1.21","version_comment":"- FIX: A 2]] jump inside a region (unless last line) jumped like a 1]] jump. The search for next region must not decrease the iteration counter when _not_ searching _across_ the region. \r\n- FIX: Must not do (characterwise) end position adaptation for linewise text object that does not exclude boundaries. \r\n- Switched example from email fortunes to Pascal begin..end blocks, as they are conceptually easier. ","3":"- FIX: A 2]] jump inside a region (unless last line) jumped like a 1]] jump. The search for next region must not decrease the iteration counter when _not_ searching _across_ the region. \r\n- FIX: Must not do (characterwise) end position adaptation for linewise text object that does not exclude boundaries. \r\n- Switched example from email fortunes to Pascal begin..end blocks, as they are conceptually easier. ","package":"CountJump.vba.gz","4":"CountJump.vba.gz","src_id":"13462","5":"13462","creation_date":"1280842763","6":"1280842763"},{"0":"3130","vim_version":"7.0","1":"7.0","script_version":"1.20","2":"1.20","version_comment":"- ENH: In CountJump#Motion#MakeBracketMotion(), a:keyAfterBracket and a:inverseKeyAfterBracket can now be empty, the resulting mappings are then omitted. Likewise, any jump function can be empty in CountJump#Motion#MakeBracketMotionWithJumpFunctions().\r\n- With the added CountJump#Motion#MakeBracketMotionWithJumpFunctions() motions can be defined via jump functions, similar to how text objects can be defined. \r\n- Added CountJump\/Region.vim to move to borders of a region defined by lines matching a pattern. \r\n- FIX: CountJump#CountJump() with mode \"O\" didn't add original position to jump list. \r\n- The previous visual selection is kept when the text object could not be selected. (Beforehand, a new selection of the text object's selection type was created.) \r\n- The adjustment movements after the jumps to the text object boundaries now do not cause beeps if that movement cannot be done (e.g. a 'j' at the end of the buffer). ","3":"- ENH: In CountJump#Motion#MakeBracketMotion(), a:keyAfterBracket and a:inverseKeyAfterBracket can now be empty, the resulting mappings are then omitted. Likewise, any jump function can be empty in CountJump#Motion#MakeBracketMotionWithJumpFunctions().\r\n- With the added CountJump#Motion#MakeBracketMotionWithJumpFunctions() motions can be defined via jump functions, similar to how text objects can be defined. \r\n- Added CountJump\/Region.vim to move to borders of a region defined by lines matching a pattern. \r\n- FIX: CountJump#CountJump() with mode \"O\" didn't add original position to jump list. \r\n- The previous visual selection is kept when the text object could not be selected. (Beforehand, a new selection of the text object's selection type was created.) \r\n- The adjustment movements after the jumps to the text object boundaries now do not cause beeps if that movement cannot be done (e.g. a 'j' at the end of the buffer). ","package":"CountJump.vba.gz","4":"CountJump.vba.gz","src_id":"13461","5":"13461","creation_date":"1280818188","6":"1280818188"},{"0":"3130","vim_version":"7.0","1":"7.0","script_version":"1.10","2":"1.10","version_comment":"- Changed behavior if there aren't [count] matches: Instead of jumping to the last available match (and ringing the bell), the cursor stays at the original position, like with the old vi-compatible motions. \r\n- ENH: Only adding to jump list if there actually is a match. This is like the built-in Vim motions work. \r\n- FIX: For a linewise text object, the end cursor column is not important; do not compare with the original cursor column in this case. ","3":"- Changed behavior if there aren't [count] matches: Instead of jumping to the last available match (and ringing the bell), the cursor stays at the original position, like with the old vi-compatible motions. \r\n- ENH: Only adding to jump list if there actually is a match. This is like the built-in Vim motions work. \r\n- FIX: For a linewise text object, the end cursor column is not important; do not compare with the original cursor column in this case. ","package":"CountJump.vba.gz","4":"CountJump.vba.gz","src_id":"13359","5":"13359","creation_date":"1279651658","6":"1279651658"},{"0":"3130","vim_version":"7.0","1":"7.0","script_version":"1.00","2":"1.00","version_comment":"Initial upload","3":"Initial upload","package":"CountJump.vba.gz","4":"CountJump.vba.gz","src_id":"13233","5":"13233","creation_date":"1277215678","6":"1277215678"}]},"3129":{"script_id":"3129","0":"3129","script_name":"teraterm","1":"teraterm","script_type":"syntax","2":"syntax","summary":"Teraterm MACRO syntax highlighting","3":"Teraterm MACRO syntax highlighting","description":"Teraterm MACRO syntax highlighting. This script provides syntax highlighting for the Teraterm MACRO programming\/scripting language.","4":"Teraterm MACRO syntax highlighting. This script provides syntax highlighting for the Teraterm MACRO programming\/scripting language.","install_details":"1) Put the teraterm.vim into your vimfiles\/syntax directory\r\n2) Edit your vimfiles\/filetype.vim to include something like the lines below, which assumes that these files will end in *.ttl:\r\n\r\naugroup filetypedetect\r\n\r\n\\\" Teraterm MACRO files\r\nau BufNewFile,BufRead *.ttl\tsetf Teraterm\r\n\r\naugroup END","5":"1) Put the teraterm.vim into your vimfiles\/syntax directory\r\n2) Edit your vimfiles\/filetype.vim to include something like the lines below, which assumes that these files will end in *.ttl:\r\n\r\naugroup filetypedetect\r\n\r\n\\\" Teraterm MACRO files\r\nau BufNewFile,BufRead *.ttl\tsetf Teraterm\r\n\r\naugroup END","first_name":"Russell","6":"Russell","last_name":"Brinkmann","7":"Brinkmann","releases":[{"0":"3129","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"teraterm.vim","4":"teraterm.vim","src_id":"13230","5":"13230","creation_date":"1277152135","6":"1277152135"}]},"3128":{"script_id":"3128","0":"3128","script_name":"Search in Addressbook","1":"Search in Addressbook","script_type":"utility","2":"utility","summary":"Complete email addresses from an external addressbook","3":"Complete email addresses from an external addressbook","description":"This is a script using the User Complete feature to complete the email addresses from an external addressbook. It depends on an external app to get the contacts addreses, included in the package is an example that search the EDS.\r\n Its a perfect companion when you edit headers while sending mails in mutt","4":"This is a script using the User Complete feature to complete the email addresses from an external addressbook. It depends on an external app to get the contacts addreses, included in the package is an example that search the EDS.\r\n Its a perfect companion when you edit headers while sending mails in mutt","install_details":"","5":"","first_name":"Matias","6":"Matias","last_name":"V","7":"V","releases":[{"0":"3128","vim_version":"7.2","1":"7.2","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"address-search.zip","4":"address-search.zip","src_id":"13219","5":"13219","creation_date":"1276970509","6":"1276970509"}]},"3127":{"script_id":"3127","0":"3127","script_name":"gams","1":"gams","script_type":"syntax","2":"syntax","summary":"gams syntax highlighting","3":"gams syntax highlighting","description":"syntax highlighting for the GAMS programming language\r\n\r\nupdate: moved to http:\/\/github.com\/trialsolution\/gamsvim\r\nCheck github for updates.","4":"syntax highlighting for the GAMS programming language\r\n\r\nupdate: moved to http:\/\/github.com\/trialsolution\/gamsvim\r\nCheck github for updates.","install_details":"1. put gams.vim in the syntax directory\r\n2. associate .gms files with the highlighting by adding the following line to your filetype.vim:\r\nau BufNewFile,BufRead *.gms\t\tsetf gams","5":"1. put gams.vim in the syntax directory\r\n2. associate .gms files with the highlighting by adding the following line to your filetype.vim:\r\nau BufNewFile,BufRead *.gms\t\tsetf gams","first_name":"mihaly","6":"mihaly","last_name":"himics","7":"himics","releases":[{"0":"3127","vim_version":"6.0","1":"6.0","script_version":"0.14","2":"0.14","version_comment":"only the function sqr is added","3":"only the function sqr is added","package":"gams.vim","4":"gams.vim","src_id":"13352","5":"13352","creation_date":"1279550551","6":"1279550551"},{"0":"3127","vim_version":"6.0","1":"6.0","script_version":"0.13","2":"0.13","version_comment":"List of dollar commands extended based on the Bruce Mccarl user guide.","3":"List of dollar commands extended based on the Bruce Mccarl user guide.","package":"gams.vim","4":"gams.vim","src_id":"13348","5":"13348","creation_date":"1279484079","6":"1279484079"},{"0":"3127","vim_version":"6.0","1":"6.0","script_version":"0.12","2":"0.12","version_comment":"brackets issue with logical operators solved\r\nthe dollar conditional operator is added\r\n","3":"brackets issue with logical operators solved\r\nthe dollar conditional operator is added\r\n","package":"gams.vim","4":"gams.vim","src_id":"13207","5":"13207","creation_date":"1276771761","6":"1276771761"},{"0":"3127","vim_version":"6.0","1":"6.0","script_version":"0.11","2":"0.11","version_comment":"highlight of logical operators and\/or corrected\r\nadded some more gams statement\r\nthanks Key for the comments!","3":"highlight of logical operators and\/or corrected\r\nadded some more gams statement\r\nthanks Key for the comments!","package":"gams.vim","4":"gams.vim","src_id":"13206","5":"13206","creation_date":"1276770479","6":"1276770479"},{"0":"3127","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"gams.vim","4":"gams.vim","src_id":"13205","5":"13205","creation_date":"1276766358","6":"1276766358"}]},"3126":{"script_id":"3126","0":"3126","script_name":"xpcomplete","1":"xpcomplete","script_type":"utility","2":"utility","summary":"Completion for the XP-Framework (php)","3":"Completion for the XP-Framework (php)","description":"This file provides the ability to handle a better completion with the XP-Framework. This file is based on the original version from phpcomplete.vim delivered by a standard vim installation.\r\n\r\nXP-Framework: http:\/\/xp-framework.net\/\r\n\r\nRequirements:\r\n\r\nctags:\r\nUse absolute paths and --PHP-kinds=+cfidv for your ctag files\r\n\r\nExample:\r\nctags -f $HOME\/devel\/xp.ctags\/tags \\\\\r\n--langmap=\\\"php:+.inc\\\" \\\\\r\n-h \\\".php.inc\\\" -R --totals=yes \\\\\r\n--PHP-kinds=+cfidv \\\\\r\n--fields=+iaS \\\\\r\n$HOME\/devel\/xp.public\/trunk\/skeleton \\\\\r\n$HOME\/devel\/xp.public\/trunk\/ports\/classes \\\\\r\n$HOME\/devel\/xp.projects\/**\/src\r\n\r\nTODO:\r\nScreenshots\r\nBetter description\r\n","4":"This file provides the ability to handle a better completion with the XP-Framework. This file is based on the original version from phpcomplete.vim delivered by a standard vim installation.\r\n\r\nXP-Framework: http:\/\/xp-framework.net\/\r\n\r\nRequirements:\r\n\r\nctags:\r\nUse absolute paths and --PHP-kinds=+cfidv for your ctag files\r\n\r\nExample:\r\nctags -f $HOME\/devel\/xp.ctags\/tags \\\\\r\n--langmap=\\\"php:+.inc\\\" \\\\\r\n-h \\\".php.inc\\\" -R --totals=yes \\\\\r\n--PHP-kinds=+cfidv \\\\\r\n--fields=+iaS \\\\\r\n$HOME\/devel\/xp.public\/trunk\/skeleton \\\\\r\n$HOME\/devel\/xp.public\/trunk\/ports\/classes \\\\\r\n$HOME\/devel\/xp.projects\/**\/src\r\n\r\nTODO:\r\nScreenshots\r\nBetter description\r\n","install_details":"save xpcomplete.vim in ~\/.vim\/autoload\/\r\n\r\nadd follogwing to your vimrc:\r\nautocmd FileType php set omnifunc=xpcomplete#CompletePHP\r\nset tags+=$HOME\/devel\/xp.ctags\/tags\r\n\r\nIf ctags isn\\'t installed you can download it from its homepage http:\/\/ctags.sourceforge.net\/ or if you\\'re running Debian\/Ubuntu you can install it by executing the following shell command:\r\n\r\n    sudo apt-get install exuberant-ctags","5":"save xpcomplete.vim in ~\/.vim\/autoload\/\r\n\r\nadd follogwing to your vimrc:\r\nautocmd FileType php set omnifunc=xpcomplete#CompletePHP\r\nset tags+=$HOME\/devel\/xp.ctags\/tags\r\n\r\nIf ctags isn\\'t installed you can download it from its homepage http:\/\/ctags.sourceforge.net\/ or if you\\'re running Debian\/Ubuntu you can install it by executing the following shell command:\r\n\r\n    sudo apt-get install exuberant-ctags","first_name":"Sebastian","6":"Sebastian","last_name":"Kusnier","7":"Kusnier","releases":[{"0":"3126","vim_version":"7.0","1":"7.0","script_version":"r660","2":"r660","version_comment":"Previous Bugfix was not perfect\r\nThis version should work better","3":"Previous Bugfix was not perfect\r\nThis version should work better","package":"xpcomplete.vim","4":"xpcomplete.vim","src_id":"13223","5":"13223","creation_date":"1277050538","6":"1277050538"},{"0":"3126","vim_version":"7.0","1":"7.0","script_version":"v659","2":"v659","version_comment":"Bugfix:\r\n- Solved problem with nested function calls","3":"Bugfix:\r\n- Solved problem with nested function calls","package":"xpcomplete.vim","4":"xpcomplete.vim","src_id":"13220","5":"13220","creation_date":"1276972770","6":"1276972770"},{"0":"3126","vim_version":"7.0","1":"7.0","script_version":"r653","2":"r653","version_comment":"Initial upload","3":"Initial upload","package":"xpcomplete.vim","4":"xpcomplete.vim","src_id":"13193","5":"13193","creation_date":"1276631189","6":"1276631189"}]},"3125":{"script_id":"3125","0":"3125","script_name":"PIV","1":"PIV","script_type":"ftplugin","2":"ftplugin","summary":"PHP Integration environment for Vim","3":"PHP Integration environment for Vim","description":"PHP Integration for VIM\r\nDescription\r\n\r\nThis project contains the most feature complete and up to date php integration for vim. It began as a fork of the largely outdated VIP (formerly PDV), but has morphed into it's own project. While the file is located here, development happens on github. http:\/\/github.com\/spf13\/PIV.\r\n\r\nIt does not include non PHP specific functionality like commenting but rather suggests you use one of the many general purpose plugins that do a great job.. Recommendations provided at the end of this doc.\r\n\r\nFeatures\r\n\r\nSyntax updated for PHP 5.3\r\n\r\nThe list of PHP constants, functions, and classes was updated to be current with PHP 5.3. Many new classes were added in the 5.2 branch and the distributed version only covers up to 5.1.4.\r\n\r\nBetter Fold Support\r\n\r\nThis plugin can fold PHP functions and\/or classes, properties with their PhpDoc, without manually adding marker style folds ({{{ and }}}) http:\/\/www.vim.org\/scripts\/script.php?script_id=1623\r\n\r\nCan be turned off by setting\r\n\r\nlet g:DisableAutoPHPFolding = 1\r\nin your .vimrc file.\r\n\r\nPHP Doc Gen\r\n\r\nGenerate phpDocumentor conforming documentation blocks for your PHP code.\r\n\r\nTo use place cursor on line with class, function or variable definition and type ,pd (in n mode)\r\n\r\nBetter Completion\r\n\r\nPHP completion script for use with omniComplete.\r\n\r\nCompletion from current file, tags and php builtin:\r\n\r\n* classes (after new), \r\n* functions  \r\n* variables\r\n* constants \r\n* language keywords \r\nAfter -> and :: options limited to funcs and vars.\r\n\r\nBetter indenting w\/automatic formatting\r\n\r\nCustom php indenting file for VIM\r\n\r\nRecommendations\r\n\r\nIt isn't my intention to provide php specific functionality when a good general purpose solution exists.\r\n\r\nThe following plugins are recommended and can be found in my vim config repository http:\/\/github.com\/spf13\/spf13-vim.\r\n\r\nSnipmate\r\nNerdCommenter\r\nNerdTree\r\nSuperTab\r\nFugitive\r\nDelimitMate\r\nMatchit\r\nCheckSyntax\r\nSurrounding\r\nAutoCloseTag","4":"PHP Integration for VIM\r\nDescription\r\n\r\nThis project contains the most feature complete and up to date php integration for vim. It began as a fork of the largely outdated VIP (formerly PDV), but has morphed into it's own project. While the file is located here, development happens on github. http:\/\/github.com\/spf13\/PIV.\r\n\r\nIt does not include non PHP specific functionality like commenting but rather suggests you use one of the many general purpose plugins that do a great job.. Recommendations provided at the end of this doc.\r\n\r\nFeatures\r\n\r\nSyntax updated for PHP 5.3\r\n\r\nThe list of PHP constants, functions, and classes was updated to be current with PHP 5.3. Many new classes were added in the 5.2 branch and the distributed version only covers up to 5.1.4.\r\n\r\nBetter Fold Support\r\n\r\nThis plugin can fold PHP functions and\/or classes, properties with their PhpDoc, without manually adding marker style folds ({{{ and }}}) http:\/\/www.vim.org\/scripts\/script.php?script_id=1623\r\n\r\nCan be turned off by setting\r\n\r\nlet g:DisableAutoPHPFolding = 1\r\nin your .vimrc file.\r\n\r\nPHP Doc Gen\r\n\r\nGenerate phpDocumentor conforming documentation blocks for your PHP code.\r\n\r\nTo use place cursor on line with class, function or variable definition and type ,pd (in n mode)\r\n\r\nBetter Completion\r\n\r\nPHP completion script for use with omniComplete.\r\n\r\nCompletion from current file, tags and php builtin:\r\n\r\n* classes (after new), \r\n* functions  \r\n* variables\r\n* constants \r\n* language keywords \r\nAfter -> and :: options limited to funcs and vars.\r\n\r\nBetter indenting w\/automatic formatting\r\n\r\nCustom php indenting file for VIM\r\n\r\nRecommendations\r\n\r\nIt isn't my intention to provide php specific functionality when a good general purpose solution exists.\r\n\r\nThe following plugins are recommended and can be found in my vim config repository http:\/\/github.com\/spf13\/spf13-vim.\r\n\r\nSnipmate\r\nNerdCommenter\r\nNerdTree\r\nSuperTab\r\nFugitive\r\nDelimitMate\r\nMatchit\r\nCheckSyntax\r\nSurrounding\r\nAutoCloseTag","install_details":"Download the tarball. Extract to your home directory... or.. \r\n\r\nSetup VIM using pathogen to have a well organized vim directory.\r\n\r\nInstall this as a submodule for easy updating. ","5":"Download the tarball. Extract to your home directory... or.. \r\n\r\nSetup VIM using pathogen to have a well organized vim directory.\r\n\r\nInstall this as a submodule for easy updating. ","first_name":"Steve","6":"Steve","last_name":"Francia","7":"Francia","releases":[{"0":"3125","vim_version":"7.2","1":"7.2","script_version":".9","2":".9","version_comment":"Initial upload","3":"Initial upload","package":"piv.tar.gz","4":"piv.tar.gz","src_id":"13186","5":"13186","creation_date":"1276623384","6":"1276623384"}]},"3124":{"script_id":"3124","0":"3124","script_name":"vim-addon-sbt","1":"vim-addon-sbt","script_type":"utility","2":"utility","summary":"run sbt (simple build tool) within vim using python background process","3":"run sbt (simple build tool) within vim using python background process","description":"This script integrates the sbt (simple-biuld-tool) with Vim. It can be used to develop Java or Scala applications conviniently.\r\nIntegrates with vim-addon-actions. You can setup a mapping to run sbt and feed compilation results into quickfix window using both: a background python job or a background sh job.\r\nThe pyhton job is using sbt interactive mode so compilation should be fastest.\r\nFor large projects you still want to consiider using an IDE..\r\n\r\nhttp:\/\/github.com\/MarcWeber\/ensime (<- Don't miss this. It provides Scala code completion. However it requires X, See vim-addon-async).\r\nIf you dont' have X you may want to try the codefellow project which I do no longer support","4":"This script integrates the sbt (simple-biuld-tool) with Vim. It can be used to develop Java or Scala applications conviniently.\r\nIntegrates with vim-addon-actions. You can setup a mapping to run sbt and feed compilation results into quickfix window using both: a background python job or a background sh job.\r\nThe pyhton job is using sbt interactive mode so compilation should be fastest.\r\nFor large projects you still want to consiider using an IDE..\r\n\r\nhttp:\/\/github.com\/MarcWeber\/ensime (<- Don't miss this. It provides Scala code completion. However it requires X, See vim-addon-async).\r\nIf you dont' have X you may want to try the codefellow project which I do no longer support","install_details":"I recommend using vim-addon-manager. I also recommend using latest version from github:\r\nhttp:\/\/github.com\/MarcWeber\/vim-addon-sbt\r\n\r\nIf something doesn't work as expected contact me on irc or by email. I do support this script.","5":"I recommend using vim-addon-manager. I also recommend using latest version from github:\r\nhttp:\/\/github.com\/MarcWeber\/vim-addon-sbt\r\n\r\nIf something doesn't work as expected contact me on irc or by email. I do support this script.","first_name":"Marc","6":"Marc","last_name":"Weber","7":"Weber","releases":[{"0":"3124","vim_version":"7.0","1":"7.0","script_version":"0.1.1.2","2":"0.1.1.2","version_comment":"adding important cause of malfunction to the trouble shooting section of README","3":"adding important cause of malfunction to the trouble shooting section of README","package":"vim-addon-sbt-0.1.1.2.zip","4":"vim-addon-sbt-0.1.1.2.zip","src_id":"13409","5":"13409","creation_date":"1280181483","6":"1280181483"},{"0":"3124","vim_version":"7.0","1":"7.0","script_version":"0.1.1.1","2":"0.1.1.1","version_comment":"fix implementation of new feature","3":"fix implementation of new feature","package":"vim-addon-sbt-0.1.1.1.zip","4":"vim-addon-sbt-0.1.1.1.zip","src_id":"13376","5":"13376","creation_date":"1279738922","6":"1279738922"},{"0":"3124","vim_version":"7.0","1":"7.0","script_version":"0.1.1","2":"0.1.1","version_comment":"adding SBT command completion","3":"adding SBT command completion","package":"vim-addon-sbt-0.1.1.zip","4":"vim-addon-sbt-0.1.1.zip","src_id":"13372","5":"13372","creation_date":"1279723628","6":"1279723628"},{"0":"3124","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"-","3":"-","package":"vim-addon-sbt-0.1.zip","4":"vim-addon-sbt-0.1.zip","src_id":"13304","5":"13304","creation_date":"1278539799","6":"1278539799"},{"0":"3124","vim_version":"7.2","1":"7.2","script_version":"0.0","2":"0.0","version_comment":"Initial upload","3":"Initial upload","package":"MarcWeber-vim-addon-sbt-f09ef36.zip","4":"MarcWeber-vim-addon-sbt-f09ef36.zip","src_id":"13177","5":"13177","creation_date":"1276451494","6":"1276451494"}]},"3123":{"script_id":"3123","0":"3123","script_name":"shell.vim","1":"shell.vim","script_type":"utility","2":"utility","summary":"Improved integration between Vim and its environment (fullscreen, open URL, etc)","3":"Improved integration between Vim and its environment (fullscreen, open URL, etc)","description":"This plug-in aims to improve the integration between Vim and its environment by providing functions to switch to full-screen (see the screenshots at http:\/\/peterodding.com\/code\/vim\/shell\/screenshots), open URLs in the user's default web browser and execute external commands in the background without opening a command prompt window. A DLL is included to perform these things on Windows, while on UNIX external commands are used.\r\n\r\nFor more information about the plug-in please refer to its homepage or the project page on GitHub:\r\n\r\n \u00e2\u0080\u00a2 http:\/\/peterodding.com\/code\/vim\/shell\/\r\n \u00e2\u0080\u00a2 http:\/\/github.com\/xolox\/vim-shell\r\n\r\nIf you have questions, bug reports, suggestions, etc. the author can be contacted at peter@peterodding.com. If you like this plug-in please vote for it below!\r\n\r\nALTERNATIVES\r\nAfter publishing this plug-in I found that vimscript #687 and vimscript #2596 also implement full-screen on Windows using a similar approach. I prefer the effect of my plug-in because it seems to hide window decorations more effectively. Also note that my plug-in was developed independently of the other two.","4":"This plug-in aims to improve the integration between Vim and its environment by providing functions to switch to full-screen (see the screenshots at http:\/\/peterodding.com\/code\/vim\/shell\/screenshots), open URLs in the user's default web browser and execute external commands in the background without opening a command prompt window. A DLL is included to perform these things on Windows, while on UNIX external commands are used.\r\n\r\nFor more information about the plug-in please refer to its homepage or the project page on GitHub:\r\n\r\n \u00e2\u0080\u00a2 http:\/\/peterodding.com\/code\/vim\/shell\/\r\n \u00e2\u0080\u00a2 http:\/\/github.com\/xolox\/vim-shell\r\n\r\nIf you have questions, bug reports, suggestions, etc. the author can be contacted at peter@peterodding.com. If you like this plug-in please vote for it below!\r\n\r\nALTERNATIVES\r\nAfter publishing this plug-in I found that vimscript #687 and vimscript #2596 also implement full-screen on Windows using a similar approach. I prefer the effect of my plug-in because it seems to hide window decorations more effectively. Also note that my plug-in was developed independently of the other two.","install_details":"Please note that the vim-shell plug-in requires my vim-misc plug-in which is separately distributed (see vimscript #4597). \r\n\r\nUnzip the most recent ZIP archives of the vim-shell and vim-misc plug-ins inside your Vim profile directory (usually this is ~\/.vim on UNIX and %USERPROFILE%\\vimfiles on Windows), restart Vim and execute the command :helptags ~\/.vim\/doc (use :helptags ~\\vimfiles\\doc instead on Windows). Now try it out:\r\n\r\n \u00e2\u0080\u00a2 Press <F11> or execute :Fullscreen to switch to full-screen mode and back;\r\n\r\n \u00e2\u0080\u00a2 Press <F6> or execute :Open to open files, directories, URLs and e-mail addresses using their associated default programs. By default the filename\/URL\/etc. under the text cursor is used, but you can also give an argument to the :Open command, for example:\r\n\r\n    :Open $VIMRUNTIME\r\n    :Open http:\/\/www.vim.org\/scripts\/script.php?script_id=3123\r\n\r\nIf you prefer you can also use Pathogen, Vundle or a similar tool to install & update the vim-shell and vim-misc plug-ins using a local clone of the git repository.","5":"Please note that the vim-shell plug-in requires my vim-misc plug-in which is separately distributed (see vimscript #4597). \r\n\r\nUnzip the most recent ZIP archives of the vim-shell and vim-misc plug-ins inside your Vim profile directory (usually this is ~\/.vim on UNIX and %USERPROFILE%\\vimfiles on Windows), restart Vim and execute the command :helptags ~\/.vim\/doc (use :helptags ~\\vimfiles\\doc instead on Windows). Now try it out:\r\n\r\n \u00e2\u0080\u00a2 Press <F11> or execute :Fullscreen to switch to full-screen mode and back;\r\n\r\n \u00e2\u0080\u00a2 Press <F6> or execute :Open to open files, directories, URLs and e-mail addresses using their associated default programs. By default the filename\/URL\/etc. under the text cursor is used, but you can also give an argument to the :Open command, for example:\r\n\r\n    :Open $VIMRUNTIME\r\n    :Open http:\/\/www.vim.org\/scripts\/script.php?script_id=3123\r\n\r\nIf you prefer you can also use Pathogen, Vundle or a similar tool to install & update the vim-shell and vim-misc plug-ins using a local clone of the git repository.","first_name":"Peter","6":"Peter","last_name":"Odding","7":"Odding","releases":[{"0":"3123","vim_version":"7.0","1":"7.0","script_version":"0.13.6","2":"0.13.6","version_comment":" \u00e2\u0080\u00a2 Increase verbosity of xolox#shell#can_use_dll():\n   http:\/\/github.com\/xolox\/vim-shell\/commit\/1e50986\n\n \u00e2\u0080\u00a2 Make it possible to disable use of the DDL (useful during testing):\n   http:\/\/github.com\/xolox\/vim-shell\/commit\/c697297\n\n \u00e2\u0080\u00a2 Make it possible to silence full screen message (issue #26):\n   http:\/\/github.com\/xolox\/vim-shell\/commit\/c19945c","3":" \u00e2\u0080\u00a2 Increase verbosity of xolox#shell#can_use_dll():\n   http:\/\/github.com\/xolox\/vim-shell\/commit\/1e50986\n\n \u00e2\u0080\u00a2 Make it possible to disable use of the DDL (useful during testing):\n   http:\/\/github.com\/xolox\/vim-shell\/commit\/c697297\n\n \u00e2\u0080\u00a2 Make it possible to silence full screen message (issue #26):\n   http:\/\/github.com\/xolox\/vim-shell\/commit\/c19945c","package":"shell.zip","4":"shell.zip","src_id":"22145","5":"22145","creation_date":"1404687140","6":"1404687140"},{"0":"3123","vim_version":"7.0","1":"7.0","script_version":"0.13.3","2":"0.13.3","version_comment":" \u00e2\u0080\u00a2 Support MacVim fullscreen:\n   http:\/\/github.com\/xolox\/vim-shell\/commit\/5d79d74\n\n \u00e2\u0080\u00a2 Merge pull request #25: Support MacVim fullscreen:\n   http:\/\/github.com\/xolox\/vim-shell\/commit\/42f1549","3":" \u00e2\u0080\u00a2 Support MacVim fullscreen:\n   http:\/\/github.com\/xolox\/vim-shell\/commit\/5d79d74\n\n \u00e2\u0080\u00a2 Merge pull request #25: Support MacVim fullscreen:\n   http:\/\/github.com\/xolox\/vim-shell\/commit\/42f1549","package":"shell.zip","4":"shell.zip","src_id":"22032","5":"22032","creation_date":"1402947026","6":"1402947026"},{"0":"3123","vim_version":"7.0","1":"7.0","script_version":"0.13.2","2":"0.13.2","version_comment":" \u00e2\u0080\u00a2 Remove duplicate help tag (reported by Yaofeng Peng):\n   http:\/\/github.com\/xolox\/vim-shell\/commit\/80f04f0","3":" \u00e2\u0080\u00a2 Remove duplicate help tag (reported by Yaofeng Peng):\n   http:\/\/github.com\/xolox\/vim-shell\/commit\/80f04f0","package":"shell.zip","4":"shell.zip","src_id":"20745","5":"20745","creation_date":"1378155795","6":"1378155795"},{"0":"3123","vim_version":"7.0","1":"7.0","script_version":"0.13.1","2":"0.13.1","version_comment":" \u00e2\u0080\u00a2 Make sure vim-misc is installed, politely complain if it isn't:\n   http:\/\/github.com\/xolox\/vim-shell\/commit\/1e1a116","3":" \u00e2\u0080\u00a2 Make sure vim-misc is installed, politely complain if it isn't:\n   http:\/\/github.com\/xolox\/vim-shell\/commit\/1e1a116","package":"shell.zip","4":"shell.zip","src_id":"20687","5":"20687","creation_date":"1376942823","6":"1376942823"},{"0":"3123","vim_version":"7.0","1":"7.0","script_version":"0.13","2":"0.13","version_comment":" \u00e2\u0080\u00a2 MakeWithShell triggering QuickFixCmdPre & QuickFixCmdPost (contributed by Marc Montu):\n   http:\/\/github.com\/xolox\/vim-shell\/commit\/1382495\n\n \u00e2\u0080\u00a2 Improvements on pull request #16 (the change above):\n   http:\/\/github.com\/xolox\/vim-shell\/commit\/a04b3ab","3":" \u00e2\u0080\u00a2 MakeWithShell triggering QuickFixCmdPre & QuickFixCmdPost (contributed by Marc Montu):\n   http:\/\/github.com\/xolox\/vim-shell\/commit\/1382495\n\n \u00e2\u0080\u00a2 Improvements on pull request #16 (the change above):\n   http:\/\/github.com\/xolox\/vim-shell\/commit\/a04b3ab","package":"shell.zip","4":"shell.zip","src_id":"20344","5":"20344","creation_date":"1371067509","6":"1371067509"},{"0":"3123","vim_version":"7.0","1":"7.0","script_version":"0.12.10","2":"0.12.10","version_comment":" \u00e2\u0080\u00a2 Improve quoting in execute_with_dll() (suggested by Ingo Karkat):\n   http:\/\/github.com\/xolox\/vim-shell\/commit\/e7157d5","3":" \u00e2\u0080\u00a2 Improve quoting in execute_with_dll() (suggested by Ingo Karkat):\n   http:\/\/github.com\/xolox\/vim-shell\/commit\/e7157d5","package":"shell.zip","4":"shell.zip","src_id":"20273","5":"20273","creation_date":"1370283084","6":"1370283084"},{"0":"3123","vim_version":"7.0","1":"7.0","script_version":"0.12.9","2":"0.12.9","version_comment":" \u00e2\u0080\u00a2 Bug fixes for 64 bit Windows backend of xolox#shell#execute_with_dll() (contributed by Ingo Karkat):\n   http:\/\/github.com\/xolox\/vim-shell\/commit\/aac1374\n   http:\/\/github.com\/xolox\/vim-shell\/commit\/e93e625\n   http:\/\/github.com\/xolox\/vim-shell\/commit\/84c2fda","3":" \u00e2\u0080\u00a2 Bug fixes for 64 bit Windows backend of xolox#shell#execute_with_dll() (contributed by Ingo Karkat):\n   http:\/\/github.com\/xolox\/vim-shell\/commit\/aac1374\n   http:\/\/github.com\/xolox\/vim-shell\/commit\/e93e625\n   http:\/\/github.com\/xolox\/vim-shell\/commit\/84c2fda","package":"shell.zip","4":"shell.zip","src_id":"20225","5":"20225","creation_date":"1369761464","6":"1369761464"},{"0":"3123","vim_version":"7.0","1":"7.0","script_version":"0.12.7","2":"0.12.7","version_comment":" \u00e2\u0080\u00a2 Make reporting in s:library_call() user friendly:\n   http:\/\/github.com\/xolox\/vim-shell\/commit\/1b27cc0\n\n \u00e2\u0080\u00a2 Document vim-misc as external dependency (needs to be installed separately from now on):\n   http:\/\/github.com\/xolox\/vim-shell\/commit\/4849e83\n\n \u00e2\u0080\u00a2 Improve integration between vim-shell & vim-session (issue #11):\n   http:\/\/github.com\/xolox\/vim-shell\/commit\/5357db8","3":" \u00e2\u0080\u00a2 Make reporting in s:library_call() user friendly:\n   http:\/\/github.com\/xolox\/vim-shell\/commit\/1b27cc0\n\n \u00e2\u0080\u00a2 Document vim-misc as external dependency (needs to be installed separately from now on):\n   http:\/\/github.com\/xolox\/vim-shell\/commit\/4849e83\n\n \u00e2\u0080\u00a2 Improve integration between vim-shell & vim-session (issue #11):\n   http:\/\/github.com\/xolox\/vim-shell\/commit\/5357db8","package":"shell.zip","4":"shell.zip","src_id":"20209","5":"20209","creation_date":"1369500920","6":"1369500920"},{"0":"3123","vim_version":"7.0","1":"7.0","script_version":"0.12.5","2":"0.12.5","version_comment":" \u00e2\u0080\u00a2 Updated miscellaneous scripts:\n   http:\/\/github.com\/xolox\/vim-shell\/commit\/4aada54","3":" \u00e2\u0080\u00a2 Updated miscellaneous scripts:\n   http:\/\/github.com\/xolox\/vim-shell\/commit\/4aada54","package":"shell.zip","4":"shell.zip","src_id":"20185","5":"20185","creation_date":"1369054622","6":"1369054622"},{"0":"3123","vim_version":"7.0","1":"7.0","script_version":"0.12.4","2":"0.12.4","version_comment":" \u00e2\u0080\u00a2 Updated miscellaneous scripts:\n   http:\/\/github.com\/xolox\/vim-shell\/commit\/60a36f7","3":" \u00e2\u0080\u00a2 Updated miscellaneous scripts:\n   http:\/\/github.com\/xolox\/vim-shell\/commit\/60a36f7","package":"shell.zip","4":"shell.zip","src_id":"20173","5":"20173","creation_date":"1369003484","6":"1369003484"},{"0":"3123","vim_version":"7.0","1":"7.0","script_version":"0.12.2","2":"0.12.2","version_comment":" \u00e2\u0080\u00a2 Provide v:shell_error equivalent (g:xolox#shell#make_exit_code):\n   http:\/\/github.com\/xolox\/vim-shell\/commit\/e0a301a","3":" \u00e2\u0080\u00a2 Provide v:shell_error equivalent (g:xolox#shell#make_exit_code):\n   http:\/\/github.com\/xolox\/vim-shell\/commit\/e0a301a","package":"shell.zip","4":"shell.zip","src_id":"20141","5":"20141","creation_date":"1368565676","6":"1368565676"},{"0":"3123","vim_version":"7.0","1":"7.0","script_version":"0.12.1","2":"0.12.1","version_comment":"This release contains a big internal refactoring that makes most of what was\npreviously called xolox#shell#execute() available as xolox#misc#os#exec() for\nuse by all of my plug-ins, even when the vim-shell plug-in is not installed.\n\nAs a bonus xolox#misc#os#exec() reliably reports exit codes both on Windows\nusing the compiled DLL and on other platforms using plain system().\n\nReferences:\n\n \u00e2\u0080\u00a2 Move xolox#shell#execute() -> xolox#misc#os#exec():\n   http:\/\/github.com\/xolox\/vim-shell\/commit\/6539185\n\n \u00e2\u0080\u00a2 Updated miscellaneous scripts:\n   http:\/\/github.com\/xolox\/vim-shell\/commit\/f8ee02d\n   http:\/\/github.com\/xolox\/vim-shell\/commit\/9c88b0e","3":"This release contains a big internal refactoring that makes most of what was\npreviously called xolox#shell#execute() available as xolox#misc#os#exec() for\nuse by all of my plug-ins, even when the vim-shell plug-in is not installed.\n\nAs a bonus xolox#misc#os#exec() reliably reports exit codes both on Windows\nusing the compiled DLL and on other platforms using plain system().\n\nReferences:\n\n \u00e2\u0080\u00a2 Move xolox#shell#execute() -> xolox#misc#os#exec():\n   http:\/\/github.com\/xolox\/vim-shell\/commit\/6539185\n\n \u00e2\u0080\u00a2 Updated miscellaneous scripts:\n   http:\/\/github.com\/xolox\/vim-shell\/commit\/f8ee02d\n   http:\/\/github.com\/xolox\/vim-shell\/commit\/9c88b0e","package":"shell.zip","4":"shell.zip","src_id":"20128","5":"20128","creation_date":"1368482322","6":"1368482322"},{"0":"3123","vim_version":"7.0","1":"7.0","script_version":"0.11.3","2":"0.11.3","version_comment":" \u00e2\u0080\u00a2 Bug fix: Insufficient arguments for printf():\n   http:\/\/github.com\/xolox\/vim-shell\/commit\/e82a7f6","3":" \u00e2\u0080\u00a2 Bug fix: Insufficient arguments for printf():\n   http:\/\/github.com\/xolox\/vim-shell\/commit\/e82a7f6","package":"shell.zip","4":"shell.zip","src_id":"20028","5":"20028","creation_date":"1367801177","6":"1367801177"},{"0":"3123","vim_version":"7.0","1":"7.0","script_version":"0.11.2","2":"0.11.2","version_comment":" \u00e2\u0080\u00a2 Bug fix for changes to \"always on top\" behavior:\n   http:\/\/github.com\/xolox\/vim-shell\/commit\/427f408","3":" \u00e2\u0080\u00a2 Bug fix for changes to \"always on top\" behavior:\n   http:\/\/github.com\/xolox\/vim-shell\/commit\/427f408","package":"shell.zip","4":"shell.zip","src_id":"20015","5":"20015","creation_date":"1367613500","6":"1367613500"},{"0":"3123","vim_version":"7.0","1":"7.0","script_version":"0.11","2":"0.11","version_comment":" \u00e2\u0080\u00a2 Make it possible to disable \"always on top\" on Windows:\n   http:\/\/github.com\/xolox\/vim-shell\/commit\/a239d6b","3":" \u00e2\u0080\u00a2 Make it possible to disable \"always on top\" on Windows:\n   http:\/\/github.com\/xolox\/vim-shell\/commit\/a239d6b","package":"shell.zip","4":"shell.zip","src_id":"20009","5":"20009","creation_date":"1367491565","6":"1367491565"},{"0":"3123","vim_version":"7.0","1":"7.0","script_version":"0.10","2":"0.10","version_comment":" \u00e2\u0080\u00a2 Make integration (:make without console window):\n   http:\/\/github.com\/xolox\/vim-shell\/commit\/52c9b24","3":" \u00e2\u0080\u00a2 Make integration (:make without console window):\n   http:\/\/github.com\/xolox\/vim-shell\/commit\/52c9b24","package":"shell.zip","4":"shell.zip","src_id":"19998","5":"19998","creation_date":"1367450476","6":"1367450476"},{"0":"3123","vim_version":"7.0","1":"7.0","script_version":"0.9.25","2":"0.9.25","version_comment":" \u00e2\u0080\u00a2 Updated miscellaneous scripts:\n   http:\/\/github.com\/xolox\/vim-shell\/commit\/2e381eb","3":" \u00e2\u0080\u00a2 Updated miscellaneous scripts:\n   http:\/\/github.com\/xolox\/vim-shell\/commit\/2e381eb","package":"shell.zip","4":"shell.zip","src_id":"19962","5":"19962","creation_date":"1367159727","6":"1367159727"},{"0":"3123","vim_version":"7.0","1":"7.0","script_version":"0.9.24","2":"0.9.24","version_comment":" \u00e2\u0080\u00a2 Make compatibility with miscellaneous scripts explicit:\n   http:\/\/github.com\/xolox\/vim-shell\/commit\/07355e3","3":" \u00e2\u0080\u00a2 Make compatibility with miscellaneous scripts explicit:\n   http:\/\/github.com\/xolox\/vim-shell\/commit\/07355e3","package":"shell.zip","4":"shell.zip","src_id":"19877","5":"19877","creation_date":"1366504943","6":"1366504943"},{"0":"3123","vim_version":"7.0","1":"7.0","script_version":"0.9.23","2":"0.9.23","version_comment":" \u00e2\u0080\u00a2 Updated miscellaneous scripts:\n   http:\/\/github.com\/xolox\/vim-shell\/commit\/4adb4ad\n   http:\/\/github.com\/xolox\/vim-shell\/commit\/3a41726\n   http:\/\/github.com\/xolox\/vim-shell\/commit\/9b4c774","3":" \u00e2\u0080\u00a2 Updated miscellaneous scripts:\n   http:\/\/github.com\/xolox\/vim-shell\/commit\/4adb4ad\n   http:\/\/github.com\/xolox\/vim-shell\/commit\/3a41726\n   http:\/\/github.com\/xolox\/vim-shell\/commit\/9b4c774","package":"shell.zip","4":"shell.zip","src_id":"16974","5":"16974","creation_date":"1322268173","6":"1322268173"},{"0":"3123","vim_version":"7.0","1":"7.0","script_version":"0.9.22","2":"0.9.22","version_comment":" \u00e2\u0080\u00a2 Rename xolox#shell#escape() to xolox#misc#escape#shell():\n   http:\/\/github.com\/xolox\/vim-shell\/commit\/8c600e9","3":" \u00e2\u0080\u00a2 Rename xolox#shell#escape() to xolox#misc#escape#shell():\n   http:\/\/github.com\/xolox\/vim-shell\/commit\/8c600e9","package":"shell.zip","4":"shell.zip","src_id":"16930","5":"16930","creation_date":"1321911746","6":"1321911746"},{"0":"3123","vim_version":"7.0","1":"7.0","script_version":"0.9.21","2":"0.9.21","version_comment":" \u00e2\u0080\u00a2 Make the full screen window top most (shell.c patch contributed by Guo Yu):\n   http:\/\/github.com\/xolox\/vim-shell\/commit\/d51681b","3":" \u00e2\u0080\u00a2 Make the full screen window top most (shell.c patch contributed by Guo Yu):\n   http:\/\/github.com\/xolox\/vim-shell\/commit\/d51681b","package":"shell.zip","4":"shell.zip","src_id":"16851","5":"16851","creation_date":"1321027675","6":"1321027675"},{"0":"3123","vim_version":"7.0","1":"7.0","script_version":"0.9.20","2":"0.9.20","version_comment":" \u00e2\u0080\u00a2 Workaround &shellslash option on Windows (issue #6):\n   http:\/\/github.com\/xolox\/vim-shell\/commit\/942e75a","3":" \u00e2\u0080\u00a2 Workaround &shellslash option on Windows (issue #6):\n   http:\/\/github.com\/xolox\/vim-shell\/commit\/942e75a","package":"shell.zip","4":"shell.zip","src_id":"16765","5":"16765","creation_date":"1319840436","6":"1319840436"},{"0":"3123","vim_version":"7.0","1":"7.0","script_version":"0.9.18","2":"0.9.18","version_comment":" \u00e2\u0080\u00a2 Use HTTP HEAD to disambiguate URLs with trailing punctuation (issue #4):\n   http:\/\/github.com\/xolox\/vim-shell\/commit\/d530837","3":" \u00e2\u0080\u00a2 Use HTTP HEAD to disambiguate URLs with trailing punctuation (issue #4):\n   http:\/\/github.com\/xolox\/vim-shell\/commit\/d530837","package":"shell.zip","4":"shell.zip","src_id":"16764","5":"16764","creation_date":"1319838598","6":"1319838598"},{"0":"3123","vim_version":"7.0","1":"7.0","script_version":"0.9.17","2":"0.9.17","version_comment":" \u00e2\u0080\u00a2 Bug fix: Restore regex to match e-mail addresses:\n   http:\/\/github.com\/xolox\/vim-shell\/commit\/350962b\n\n \u00e2\u0080\u00a2 Workaround for E488 (bug in Vim or my understanding of Vim?):\n   http:\/\/github.com\/xolox\/vim-shell\/commit\/32ce59b\n\n \u00e2\u0080\u00a2 Add debugging statements (should make it easier to debug issues like #5):\n   http:\/\/github.com\/xolox\/vim-shell\/commit\/7eb0d85\n\n \u00e2\u0080\u00a2 Debugging statements for execution of external commands:\n   http:\/\/github.com\/xolox\/vim-shell\/commit\/37dbfc3","3":" \u00e2\u0080\u00a2 Bug fix: Restore regex to match e-mail addresses:\n   http:\/\/github.com\/xolox\/vim-shell\/commit\/350962b\n\n \u00e2\u0080\u00a2 Workaround for E488 (bug in Vim or my understanding of Vim?):\n   http:\/\/github.com\/xolox\/vim-shell\/commit\/32ce59b\n\n \u00e2\u0080\u00a2 Add debugging statements (should make it easier to debug issues like #5):\n   http:\/\/github.com\/xolox\/vim-shell\/commit\/7eb0d85\n\n \u00e2\u0080\u00a2 Debugging statements for execution of external commands:\n   http:\/\/github.com\/xolox\/vim-shell\/commit\/37dbfc3","package":"shell.zip","4":"shell.zip","src_id":"16699","5":"16699","creation_date":"1318967582","6":"1318967582"},{"0":"3123","vim_version":"7.0","1":"7.0","script_version":"0.9.13","2":"0.9.13","version_comment":" \u00e2\u0080\u00a2 Updated miscellaneous scripts:\n   http:\/\/github.com\/xolox\/vim-shell\/commit\/a97dd83","3":" \u00e2\u0080\u00a2 Updated miscellaneous scripts:\n   http:\/\/github.com\/xolox\/vim-shell\/commit\/a97dd83","package":"shell.zip","4":"shell.zip","src_id":"16584","5":"16584","creation_date":"1316994893","6":"1316994893"},{"0":"3123","vim_version":"7.0","1":"7.0","script_version":"0.9.12","2":"0.9.12","version_comment":" \u00e2\u0080\u00a2 Extract :Maximize from :Fullscreen (suggested by Benjamin Bergman):\n   http:\/\/github.com\/xolox\/vim-shell\/commit\/665a2b5","3":" \u00e2\u0080\u00a2 Extract :Maximize from :Fullscreen (suggested by Benjamin Bergman):\n   http:\/\/github.com\/xolox\/vim-shell\/commit\/665a2b5","package":"shell.zip","4":"shell.zip","src_id":"16546","5":"16546","creation_date":"1316301781","6":"1316301781"},{"0":"3123","vim_version":"7.0","1":"7.0","script_version":"0.9.11","2":"0.9.11","version_comment":" \u00e2\u0080\u00a2 Updated miscellaneous scripts:\n   http:\/\/github.com\/xolox\/vim-shell\/commit\/34ef803","3":" \u00e2\u0080\u00a2 Updated miscellaneous scripts:\n   http:\/\/github.com\/xolox\/vim-shell\/commit\/34ef803","package":"shell.zip","4":"shell.zip","src_id":"16462","5":"16462","creation_date":"1315145460","6":"1315145460"},{"0":"3123","vim_version":"7.0","1":"7.0","script_version":"0.9.10","2":"0.9.10","version_comment":" \u00e2\u0080\u00a2 Version bump because of miscellaneous scripts:\n   http:\/\/github.com\/xolox\/vim-shell\/commit\/c284b38\n   http:\/\/github.com\/xolox\/vim-shell\/commit\/8310041","3":" \u00e2\u0080\u00a2 Version bump because of miscellaneous scripts:\n   http:\/\/github.com\/xolox\/vim-shell\/commit\/c284b38\n   http:\/\/github.com\/xolox\/vim-shell\/commit\/8310041","package":"shell.zip","4":"shell.zip","src_id":"16420","5":"16420","creation_date":"1314826932","6":"1314826932"},{"0":"3123","vim_version":"7.0","1":"7.0","script_version":"0.9.9","2":"0.9.9","version_comment":" \u00e2\u0080\u00a2 Option handling with xolox#misc#option#get({name}, {default}):\n   http:\/\/github.com\/xolox\/vim-shell\/commit\/e228b0e\n   http:\/\/github.com\/xolox\/vim-shell\/commit\/0b1c06e\n   http:\/\/github.com\/xolox\/vim-shell\/commit\/168d0cd\n\n \u00e2\u0080\u00a2 Move version variable to autoload script:\n   http:\/\/github.com\/xolox\/vim-shell\/commit\/6cbfe98\n   http:\/\/github.com\/xolox\/vim-shell\/commit\/168d0cd\n\n \u00e2\u0080\u00a2 Document xolox#shell#fullscreen(), xolox#shell#is_fullscreen()\n   http:\/\/github.com\/xolox\/vim-shell\/commit\/168d0cd","3":" \u00e2\u0080\u00a2 Option handling with xolox#misc#option#get({name}, {default}):\n   http:\/\/github.com\/xolox\/vim-shell\/commit\/e228b0e\n   http:\/\/github.com\/xolox\/vim-shell\/commit\/0b1c06e\n   http:\/\/github.com\/xolox\/vim-shell\/commit\/168d0cd\n\n \u00e2\u0080\u00a2 Move version variable to autoload script:\n   http:\/\/github.com\/xolox\/vim-shell\/commit\/6cbfe98\n   http:\/\/github.com\/xolox\/vim-shell\/commit\/168d0cd\n\n \u00e2\u0080\u00a2 Document xolox#shell#fullscreen(), xolox#shell#is_fullscreen()\n   http:\/\/github.com\/xolox\/vim-shell\/commit\/168d0cd","package":"shell.zip","4":"shell.zip","src_id":"16415","5":"16415","creation_date":"1314818232","6":"1314818232"},{"0":"3123","vim_version":"7.0","1":"7.0","script_version":"0.9.7","2":"0.9.7","version_comment":" \u00e2\u0080\u00a2 Define version as variable, include version in messages:\n   http:\/\/github.com\/xolox\/vim-shell\/commit\/a0ed509","3":" \u00e2\u0080\u00a2 Define version as variable, include version in messages:\n   http:\/\/github.com\/xolox\/vim-shell\/commit\/a0ed509","package":"shell.zip","4":"shell.zip","src_id":"15926","5":"15926","creation_date":"1308365072","6":"1308365072"},{"0":"3123","vim_version":"7.0","1":"7.0","script_version":"0.9.6","2":"0.9.6","version_comment":" \u00e2\u0080\u00a2 Bug fix: Rename xolox#open -> xolox#misc#open (reported by Tim Dahlin):\n   http:\/\/github.com\/xolox\/vim-shell\/commit\/73f9744","3":" \u00e2\u0080\u00a2 Bug fix: Rename xolox#open -> xolox#misc#open (reported by Tim Dahlin):\n   http:\/\/github.com\/xolox\/vim-shell\/commit\/73f9744","package":"shell.zip","4":"shell.zip","src_id":"15919","5":"15919","creation_date":"1308329838","6":"1308329838"},{"0":"3123","vim_version":"7.0","1":"7.0","script_version":"0.9.5","2":"0.9.5","version_comment":" \u00e2\u0080\u00a2 Don't check existence of temporary files, just try to read them:\n   http:\/\/github.com\/xolox\/vim-shell\/commit\/d0e682a","3":" \u00e2\u0080\u00a2 Don't check existence of temporary files, just try to read them:\n   http:\/\/github.com\/xolox\/vim-shell\/commit\/d0e682a","package":"shell.zip","4":"shell.zip","src_id":"15916","5":"15916","creation_date":"1308323818","6":"1308323818"},{"0":"3123","vim_version":"7.0","1":"7.0","script_version":"0.9.2","2":"0.9.2","version_comment":"Use Vim's \"shell\" and \"shellcmdflag\" options:\r\nhttps:\/\/github.com\/xolox\/vim-shell\/commit\/993f941c76e70f7f717c\r\n\r\nAlso the character encoding of the included help file was changed to ASCII to accommodate users that don't have Unicode support (enabled).","3":"Use Vim's \"shell\" and \"shellcmdflag\" options:\r\nhttps:\/\/github.com\/xolox\/vim-shell\/commit\/993f941c76e70f7f717c\r\n\r\nAlso the character encoding of the included help file was changed to ASCII to accommodate users that don't have Unicode support (enabled).","package":"shell.zip","4":"shell.zip","src_id":"14954","5":"14954","creation_date":"1296842099","6":"1296842099"},{"0":"3123","vim_version":"7.0","1":"7.0","script_version":"0.9.1","2":"0.9.1","version_comment":"Restore window position\/size on leaving full-screen (this fixes issue #2 reported by dionysiac- on GitHub):\r\nhttps:\/\/github.com\/xolox\/vim-shell\/commit\/681404594304bfa6a052","3":"Restore window position\/size on leaving full-screen (this fixes issue #2 reported by dionysiac- on GitHub):\r\nhttps:\/\/github.com\/xolox\/vim-shell\/commit\/681404594304bfa6a052","package":"shell.zip","4":"shell.zip","src_id":"14560","5":"14560","creation_date":"1292692693","6":"1292692693"},{"0":"3123","vim_version":"7.0","1":"7.0","script_version":"0.9","2":"0.9","version_comment":"Support for Windows x64, improved error handling (thanks to Stan Angeloff for getting me to build an x64 DLL and helping me test the DLL and automatic bitness detection):\r\nhttps:\/\/github.com\/xolox\/vim-shell\/commit\/669a9f2d5cce67b34599","3":"Support for Windows x64, improved error handling (thanks to Stan Angeloff for getting me to build an x64 DLL and helping me test the DLL and automatic bitness detection):\r\nhttps:\/\/github.com\/xolox\/vim-shell\/commit\/669a9f2d5cce67b34599","package":"shell.zip","4":"shell.zip","src_id":"14430","5":"14430","creation_date":"1291429425","6":"1291429425"},{"0":"3123","vim_version":"7.0","1":"7.0","script_version":"0.8.2","2":"0.8.2","version_comment":" \u00e2\u0080\u00a2 Bug fix: %s\/xolox#open#shell\/xolox#open#file\/:\r\n   http:\/\/github.com\/xolox\/vim-shell\/commit\/452e951e2fcc4c7afa5a\r\n\r\n \u00e2\u0080\u00a2 Truncate expand() result to one pathname:\r\n   http:\/\/github.com\/xolox\/vim-shell\/commit\/dc3448ec7f3a66b17199\r\n\r\n \u00e2\u0080\u00a2 Bug fix: Open either file or directory, but never both!\r\n   http:\/\/github.com\/xolox\/vim-shell\/commit\/de1303de9b9317affe10","3":" \u00e2\u0080\u00a2 Bug fix: %s\/xolox#open#shell\/xolox#open#file\/:\r\n   http:\/\/github.com\/xolox\/vim-shell\/commit\/452e951e2fcc4c7afa5a\r\n\r\n \u00e2\u0080\u00a2 Truncate expand() result to one pathname:\r\n   http:\/\/github.com\/xolox\/vim-shell\/commit\/dc3448ec7f3a66b17199\r\n\r\n \u00e2\u0080\u00a2 Bug fix: Open either file or directory, but never both!\r\n   http:\/\/github.com\/xolox\/vim-shell\/commit\/de1303de9b9317affe10","package":"shell.zip","4":"shell.zip","src_id":"13866","5":"13866","creation_date":"1284896302","6":"1284896302"},{"0":"3123","vim_version":"7.0","1":"7.0","script_version":"0.8","2":"0.8","version_comment":"http:\/\/github.com\/xolox\/vim-shell\/commit\/4d2313b6508c26a1a843:\r\n \u00e2\u0080\u00a2 Moved openurl() & open_with() to dedicated plug-in (included in ZIP archive)\r\n \u00e2\u0080\u00a2 Simplified Mac OS X support\r\n \u00e2\u0080\u00a2 Support command line web browsers in s:open_at_cursor()","3":"http:\/\/github.com\/xolox\/vim-shell\/commit\/4d2313b6508c26a1a843:\r\n \u00e2\u0080\u00a2 Moved openurl() & open_with() to dedicated plug-in (included in ZIP archive)\r\n \u00e2\u0080\u00a2 Simplified Mac OS X support\r\n \u00e2\u0080\u00a2 Support command line web browsers in s:open_at_cursor()","package":"shell.zip","4":"shell.zip","src_id":"13853","5":"13853","creation_date":"1284769942","6":"1284769942"},{"0":"3123","vim_version":"7.0","1":"7.0","script_version":"0.7.3","2":"0.7.3","version_comment":"Bug fix: Only toggle active window using `wmctrl' and report errors from libcall('fullscreen'): \r\nhttp:\/\/github.com\/xolox\/vim-shell\/commit\/ca43642589089a29dc24f18e00a7edd04820bc9e","3":"Bug fix: Only toggle active window using `wmctrl' and report errors from libcall('fullscreen'): \r\nhttp:\/\/github.com\/xolox\/vim-shell\/commit\/ca43642589089a29dc24f18e00a7edd04820bc9e","package":"shell.zip","4":"shell.zip","src_id":"13721","5":"13721","creation_date":"1283133273","6":"1283133273"},{"0":"3123","vim_version":"7.0","1":"7.0","script_version":"0.7.2","2":"0.7.2","version_comment":"Bug fix for E33: No previous substitute regular expression:\r\nhttp:\/\/github.com\/xolox\/vim-shell\/commit\/8ab66c465f5f7e29cc7677b2d54012f0fe762576\r\n\r\nThe packages for version 0.7 and 0.7.1 below should have included the \"shell.dll\" dynamic link library but I failed to include it. This has been fixed now. Sorry about that!","3":"Bug fix for E33: No previous substitute regular expression:\r\nhttp:\/\/github.com\/xolox\/vim-shell\/commit\/8ab66c465f5f7e29cc7677b2d54012f0fe762576\r\n\r\nThe packages for version 0.7 and 0.7.1 below should have included the \"shell.dll\" dynamic link library but I failed to include it. This has been fixed now. Sorry about that!","package":"shell.zip","4":"shell.zip","src_id":"13582","5":"13582","creation_date":"1281903109","6":"1281903109"},{"0":"3123","vim_version":"7.0","1":"7.0","script_version":"0.7.1","2":"0.7.1","version_comment":"Enable passing stdin to xolox#shell#execute():\r\nhttp:\/\/github.com\/xolox\/vim-shell\/commit\/fc16d5c0e72d8ba4112d239f211cc0576640aaa3","3":"Enable passing stdin to xolox#shell#execute():\r\nhttp:\/\/github.com\/xolox\/vim-shell\/commit\/fc16d5c0e72d8ba4112d239f211cc0576640aaa3","package":"shell.zip","4":"shell.zip","src_id":"13532","5":"13532","creation_date":"1281410495","6":"1281410495"},{"0":"3123","vim_version":"7.0","1":"7.0","script_version":"0.7","2":"0.7","version_comment":"\u00e2\u0080\u00a2 Full-screen mode now hides Vim's menu\/toolbar\/tabline by default. This makes it useful even when the actual full-screen state of Vim's GUI window can't be changed because the DLL\/wmctrl is unavailable.\r\n\r\n\u00e2\u0080\u00a2 Full-screen mode should now work in most graphical terminal emulators like xterm and gnome-terminal (though <F11> won't work in the latter).\r\n\r\n\u00e2\u0080\u00a2 Included user friendly :Open and :Fullscreen commands plus default key mappings so the plug-in is more useful out of the box.\r\n\r\n\u00e2\u0080\u00a2 The xolox#shell#execute() function now returns the output of the shell command if it was executed in synchronous mode (this enables integration with my easytags.vim plug-in).\r\n\r\n\u00e2\u0080\u00a2 I've merged my unreleased `hyperlink.vim' plug-in into `shell.vim' which improves the openurl() functionality and includes automatic highlighting for URLs and e-mail addresses in comments and strings.\r\n\r\nAll from http:\/\/github.com\/xolox\/vim-shell\/commit\/2f6414109fa52b20c1a86faff215fe1329ba6eb8","3":"\u00e2\u0080\u00a2 Full-screen mode now hides Vim's menu\/toolbar\/tabline by default. This makes it useful even when the actual full-screen state of Vim's GUI window can't be changed because the DLL\/wmctrl is unavailable.\r\n\r\n\u00e2\u0080\u00a2 Full-screen mode should now work in most graphical terminal emulators like xterm and gnome-terminal (though <F11> won't work in the latter).\r\n\r\n\u00e2\u0080\u00a2 Included user friendly :Open and :Fullscreen commands plus default key mappings so the plug-in is more useful out of the box.\r\n\r\n\u00e2\u0080\u00a2 The xolox#shell#execute() function now returns the output of the shell command if it was executed in synchronous mode (this enables integration with my easytags.vim plug-in).\r\n\r\n\u00e2\u0080\u00a2 I've merged my unreleased `hyperlink.vim' plug-in into `shell.vim' which improves the openurl() functionality and includes automatic highlighting for URLs and e-mail addresses in comments and strings.\r\n\r\nAll from http:\/\/github.com\/xolox\/vim-shell\/commit\/2f6414109fa52b20c1a86faff215fe1329ba6eb8","package":"shell.zip","4":"shell.zip","src_id":"13529","5":"13529","creation_date":"1281387709","6":"1281387709"},{"0":"3123","vim_version":"7.0","1":"7.0","script_version":"0.6.1","2":"0.6.1","version_comment":"Bug fix: Updated instructions to match new execute() implementation. Sorry about that!\r\nhttp:\/\/github.com\/xolox\/vim-shell\/commit\/2cc68db470c974acbc4c43ea001536c1106ae0e2","3":"Bug fix: Updated instructions to match new execute() implementation. Sorry about that!\r\nhttp:\/\/github.com\/xolox\/vim-shell\/commit\/2cc68db470c974acbc4c43ea001536c1106ae0e2","package":"shell.zip","4":"shell.zip","src_id":"13183","5":"13183","creation_date":"1276539094","6":"1276539094"},{"0":"3123","vim_version":"7.0","1":"7.0","script_version":"0.6","2":"0.6","version_comment":"* Improved test instructions for execute()\r\n  http:\/\/github.com\/xolox\/vim-shell\/commit\/50453066d1d211cfa6e426b78f3e503e3f46c82e\r\n\r\n* Better DLL detection, synchronous command execution\r\n  http:\/\/github.com\/xolox\/vim-shell\/commit\/82f6cb0f013480f994438d44b6cf98ae136569c0\r\n\r\n* Improved README, added screenshots, fixed typo\r\n  http:\/\/github.com\/xolox\/vim-shell\/commit\/364ceee3040e77f0a3fb8b4b657aac612f6dbcc4","3":"* Improved test instructions for execute()\r\n  http:\/\/github.com\/xolox\/vim-shell\/commit\/50453066d1d211cfa6e426b78f3e503e3f46c82e\r\n\r\n* Better DLL detection, synchronous command execution\r\n  http:\/\/github.com\/xolox\/vim-shell\/commit\/82f6cb0f013480f994438d44b6cf98ae136569c0\r\n\r\n* Improved README, added screenshots, fixed typo\r\n  http:\/\/github.com\/xolox\/vim-shell\/commit\/364ceee3040e77f0a3fb8b4b657aac612f6dbcc4","package":"shell.zip","4":"shell.zip","src_id":"13182","5":"13182","creation_date":"1276532607","6":"1276532607"},{"0":"3123","vim_version":"7.0","1":"7.0","script_version":"0.5.2","2":"0.5.2","version_comment":"Bug fix for execute() implementation in DLL\r\nhttp:\/\/github.com\/xolox\/vim-shell\/commit\/c46f8e522f53283528f1dc9ab58cc6eb0a9c5507","3":"Bug fix for execute() implementation in DLL\r\nhttp:\/\/github.com\/xolox\/vim-shell\/commit\/c46f8e522f53283528f1dc9ab58cc6eb0a9c5507","package":"shell.zip","4":"shell.zip","src_id":"13179","5":"13179","creation_date":"1276474458","6":"1276474458"},{"0":"3123","vim_version":"7.0","1":"7.0","script_version":"0.5.1","2":"0.5.1","version_comment":"Fixed typo in NMAKE makefile and references to Vim scripts page.","3":"Fixed typo in NMAKE makefile and references to Vim scripts page.","package":"shell.zip","4":"shell.zip","src_id":"13176","5":"13176","creation_date":"1276443287","6":"1276443287"},{"0":"3123","vim_version":"7.0","1":"7.0","script_version":"0.5","2":"0.5","version_comment":"Initial upload","3":"Initial upload","package":"shell.zip","4":"shell.zip","src_id":"13175","5":"13175","creation_date":"1276442132","6":"1276442132"}]},"3122":{"script_id":"3122","0":"3122","script_name":"PySuite","1":"PySuite","script_type":"utility","2":"utility","summary":"A collection of python vim scripts","3":"A collection of python vim scripts","description":"You need vim compiled with python to use these! To test if your vim includes python, use this command:  :python print 'hi'. If you get an error, you don't have python. \r\n\r\nIncluded scripts are:\r\n\r\n- vimp3 - music player for vim (scores, random mode taking scores into account, multiple playlists per file, option to pause between tracks; note: other scripts will work in win\/linux, this one is only for linux)\r\n- outliner similar to TVO\r\n- todo list manager\r\n- project manager (load\/unload by dir\/project, make an outline of python files, etc)\r\n- calendar that supports adding notes to dates\r\n- plugin to track expenses and balances\r\n- sortable table with fields separated by 2+ spaces\r\n- resize - set a list of main vim window sizes and use two shortcuts to resize -\/+\r\n- helpgrep - enter a few words and use :helpgrep cmd to search for them in any order\r\n- pystripdoc - make a copy of buffer with stripped out python docstrings and comments\r\n- pyfolddoc - fold python docstrings and comments\r\n- aligncode - align code by '=' or '#' chars\r\n\r\nFor a more detailed description, see home page: http:\/\/lightbird.net\/pysuite\/.","4":"You need vim compiled with python to use these! To test if your vim includes python, use this command:  :python print 'hi'. If you get an error, you don't have python. \r\n\r\nIncluded scripts are:\r\n\r\n- vimp3 - music player for vim (scores, random mode taking scores into account, multiple playlists per file, option to pause between tracks; note: other scripts will work in win\/linux, this one is only for linux)\r\n- outliner similar to TVO\r\n- todo list manager\r\n- project manager (load\/unload by dir\/project, make an outline of python files, etc)\r\n- calendar that supports adding notes to dates\r\n- plugin to track expenses and balances\r\n- sortable table with fields separated by 2+ spaces\r\n- resize - set a list of main vim window sizes and use two shortcuts to resize -\/+\r\n- helpgrep - enter a few words and use :helpgrep cmd to search for them in any order\r\n- pystripdoc - make a copy of buffer with stripped out python docstrings and comments\r\n- pyfolddoc - fold python docstrings and comments\r\n- aligncode - align code by '=' or '#' chars\r\n\r\nFor a more detailed description, see home page: http:\/\/lightbird.net\/pysuite\/.","install_details":"Unzip in ~\/.vim\/ ; cd to pysuite and look at the docs, then cp -r ftplugin\/ plugin\/ python\/ syntax\/ ~\/.vim\/  if you need all scripts; if you want only a few scripts, copy pysuite.vim to .vim\/plugin\/ and the scripts you want to respective dirs under ~\/.vim\/ .\r\n\r\nNot tested on windows but most will probably work fine and the rest - with minor adjustments.","5":"Unzip in ~\/.vim\/ ; cd to pysuite and look at the docs, then cp -r ftplugin\/ plugin\/ python\/ syntax\/ ~\/.vim\/  if you need all scripts; if you want only a few scripts, copy pysuite.vim to .vim\/plugin\/ and the scripts you want to respective dirs under ~\/.vim\/ .\r\n\r\nNot tested on windows but most will probably work fine and the rest - with minor adjustments.","first_name":"A","6":"A","last_name":"K","7":"K","releases":[{"0":"3122","vim_version":"7.0","1":"7.0","script_version":"0.3.0","2":"0.3.0","version_comment":"Added vimp3 script. Fixed some performance issues with the suite, added reverse sorting to scripts that have sortable tables, fixed a bug in cal with insertion of new entries after existing entries.","3":"Added vimp3 script. Fixed some performance issues with the suite, added reverse sorting to scripts that have sortable tables, fixed a bug in cal with insertion of new entries after existing entries.","package":"pysuite-0.3.0.tar.gz","4":"pysuite-0.3.0.tar.gz","src_id":"13247","5":"13247","creation_date":"1277586399","6":"1277586399"},{"0":"3122","vim_version":"7.0","1":"7.0","script_version":"0.2.6","2":"0.2.6","version_comment":"A number of serious bugs fixed: missing potl script, old pysuite.vim (broke opening files in vimject and probably other things).","3":"A number of serious bugs fixed: missing potl script, old pysuite.vim (broke opening files in vimject and probably other things).","package":"pysuite-0.2.6.tar.gz","4":"pysuite-0.2.6.tar.gz","src_id":"13173","5":"13173","creation_date":"1276392966","6":"1276392966"},{"0":"3122","vim_version":"7.0","1":"7.0","script_version":"0.2.5","2":"0.2.5","version_comment":"Initial upload","3":"Initial upload","package":"pysuite-0.2.5.tar.gz","4":"pysuite-0.2.5.tar.gz","src_id":"13171","5":"13171","creation_date":"1276376676","6":"1276376676"}]},"3121":{"script_id":"3121","0":"3121","script_name":"django_templates.vim","1":"django_templates.vim","script_type":"utility","2":"utility","summary":"Macros and menus for django templates","3":"Macros and menus for django templates","description":"Almost each django template keyword or filter may be accessed by its short cut (and by the menu if using a GUI) in each of 3 modes.\r\nIf you don't like to use \"<F8>\" as a trigger you can change it to, for examle \"?\".\r\nOpen asp.vim in Vim editor and substitute :%s\/<F8>\/?\/g ","4":"Almost each django template keyword or filter may be accessed by its short cut (and by the menu if using a GUI) in each of 3 modes.\r\nIf you don't like to use \"<F8>\" as a trigger you can change it to, for examle \"?\".\r\nOpen asp.vim in Vim editor and substitute :%s\/<F8>\/?\/g ","install_details":"Copy to plugin directory.","5":"Copy to plugin directory.","first_name":"Branislav","6":"Branislav","last_name":"Sobotka","7":"Sobotka","releases":[{"0":"3121","vim_version":"7.0","1":"7.0","script_version":"0.4","2":"0.4","version_comment":"added inline abbreviations  for commands if, if else, for","3":"added inline abbreviations  for commands if, if else, for","package":"django_templates.vim","4":"django_templates.vim","src_id":"17298","5":"17298","creation_date":"1327270825","6":"1327270825"},{"0":"3121","vim_version":"7.0","1":"7.0","script_version":"0.3","2":"0.3","version_comment":"bug fix","3":"bug fix","package":"django_templates.vim","4":"django_templates.vim","src_id":"15579","5":"15579","creation_date":"1304515787","6":"1304515787"},{"0":"3121","vim_version":"7.0","1":"7.0","script_version":"0.2","2":"0.2","version_comment":"Some bugs fixed.\r\nAdded:\r\n- Abbreviation  for {{  }}  triggered by F10","3":"Some bugs fixed.\r\nAdded:\r\n- Abbreviation  for {{  }}  triggered by F10","package":"django_templates.vim","4":"django_templates.vim","src_id":"14059","5":"14059","creation_date":"1287150165","6":"1287150165"},{"0":"3121","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"django_templates.vim","4":"django_templates.vim","src_id":"13167","5":"13167","creation_date":"1276288854","6":"1276288854"}]},"3120":{"script_id":"3120","0":"3120","script_name":"grails-vim","1":"grails-vim","script_type":"utility","2":"utility","summary":"Easy file navigation and testing of Grails projects ","3":"Easy file navigation and testing of Grails projects ","description":"Grails-vim makes it easy to navigate Grails projects and view the test reports that Grails creates.\r\n\r\n  - Navigate from Domain Models to Controllers, Views, Tests and Test Reports\r\n  - Easily view the errors \/ failed tests, and jump to the failed tests.\r\n  - Quickly navigate controller methods, such as Save, Create, Edit, Index\r\n  - Provides built-in syntax highlighting for .gsp pages\r\n\r\nScreenshots:\r\n\r\nhttp:\/\/notesmine.com\/grails_vim#screenshots\r\n\r\nRecommended Additional Plugins:\r\n\r\nFuzzy Finder:  http:\/\/www.vim.org\/scripts\/script.php?script_id=1984\r\n\r\n","4":"Grails-vim makes it easy to navigate Grails projects and view the test reports that Grails creates.\r\n\r\n  - Navigate from Domain Models to Controllers, Views, Tests and Test Reports\r\n  - Easily view the errors \/ failed tests, and jump to the failed tests.\r\n  - Quickly navigate controller methods, such as Save, Create, Edit, Index\r\n  - Provides built-in syntax highlighting for .gsp pages\r\n\r\nScreenshots:\r\n\r\nhttp:\/\/notesmine.com\/grails_vim#screenshots\r\n\r\nRecommended Additional Plugins:\r\n\r\nFuzzy Finder:  http:\/\/www.vim.org\/scripts\/script.php?script_id=1984\r\n\r\n","install_details":"Unzip grails-vim.zip into your ~\/.vim directory.\r\n\r\nInside Vim, run\r\n\r\n:helptags ~\/.vim\/doc\r\n\r\n:help grails\r\n\r\nIf you want to jump to test results, make sure you have the $GROOVY_HOME \r\nenvironment variable set correctly.\r\n","5":"Unzip grails-vim.zip into your ~\/.vim directory.\r\n\r\nInside Vim, run\r\n\r\n:helptags ~\/.vim\/doc\r\n\r\n:help grails\r\n\r\nIf you want to jump to test results, make sure you have the $GROOVY_HOME \r\nenvironment variable set correctly.\r\n","first_name":"Nathan","6":"Nathan","last_name":"Neff","7":"Neff","releases":[{"0":"3120","vim_version":"6.0","1":"6.0","script_version":"0.2","2":"0.2","version_comment":"0.2 features:\r\n    Added |GrailsMapPrefix| to allow users to define their own map leader\r\n    for GrailsVim commands\r\n\r\n    Added <Plug>GrailsDisplayUrlMappings\r\n\r\n    Added documentation about how to change mappings using g:GrailsMapPrefix\r\n    and\/or <leader>\r\n","3":"0.2 features:\r\n    Added |GrailsMapPrefix| to allow users to define their own map leader\r\n    for GrailsVim commands\r\n\r\n    Added <Plug>GrailsDisplayUrlMappings\r\n\r\n    Added documentation about how to change mappings using g:GrailsMapPrefix\r\n    and\/or <leader>\r\n","package":"grails-vim.zip","4":"grails-vim.zip","src_id":"13213","5":"13213","creation_date":"1276895912","6":"1276895912"},{"0":"3120","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"grails-vim.zip","4":"grails-vim.zip","src_id":"13166","5":"13166","creation_date":"1276284055","6":"1276284055"}]},"3119":{"script_id":"3119","0":"3119","script_name":"tcbuild.vim","1":"tcbuild.vim","script_type":"syntax","2":"syntax","summary":"syntax of buildinfo file of TCbuild (build tool for Fortran)","3":"syntax of buildinfo file of TCbuild (build tool for Fortran)","description":"Define the syntax (keywords and comments) for the buildinfo file of TCbuild, a new build tool for Fortran.","4":"Define the syntax (keywords and comments) for the buildinfo file of TCbuild, a new build tool for Fortran.","install_details":"Place tcbuild.vim file in ~\/.vim\/syntax\/ folder.\r\n\r\nYou may want to make vim autodetect it by having this in your ~\/.vimrc :\r\nautocmd BufRead,BufNewFile buildinfo set filetype=tcbuild","5":"Place tcbuild.vim file in ~\/.vim\/syntax\/ folder.\r\n\r\nYou may want to make vim autodetect it by having this in your ~\/.vimrc :\r\nautocmd BufRead,BufNewFile buildinfo set filetype=tcbuild","first_name":"David","6":"David","last_name":"Froger","7":"Froger","releases":[{"0":"3119","vim_version":"5.7","1":"5.7","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"tcbuild.vim","4":"tcbuild.vim","src_id":"13156","5":"13156","creation_date":"1276163594","6":"1276163594"}]},"3118":{"script_id":"3118","0":"3118","script_name":"skk.vim","1":"skk.vim","script_type":"utility","2":"utility","summary":"Japanese SKK","3":"Japanese SKK","description":"* This script is an implementation of the Japanese SKK (Simple Kana to Kanji\r\nconversion program).\r\n\r\n* Get older versions from vimscript#1589.\r\n(Thanks to Noriaki Yagi for inventing this script!)\r\n\r\n* This plugin works under vim6, vim7.\r\n\r\n* Repository\r\nhttp:\/\/github.com\/tyru\/skk.vim\/","4":"* This script is an implementation of the Japanese SKK (Simple Kana to Kanji\r\nconversion program).\r\n\r\n* Get older versions from vimscript#1589.\r\n(Thanks to Noriaki Yagi for inventing this script!)\r\n\r\n* This plugin works under vim6, vim7.\r\n\r\n* Repository\r\nhttp:\/\/github.com\/tyru\/skk.vim\/","install_details":"REQUIREMENT: SKK-JISYO.[SML]\r\nSet two global variables if necessary.\r\n  let skk_jisyo = \"path to private dictionary\"\r\n  let skk_large_jisyo = \"path to SKK-JISYO.[SML]\"\r\n:so skk.vim or put this script into your plugin directory.\r\nTo start SKK-mode, press <C-j> in Insert-mode or Commandline-mode. ","5":"REQUIREMENT: SKK-JISYO.[SML]\r\nSet two global variables if necessary.\r\n  let skk_jisyo = \"path to private dictionary\"\r\n  let skk_large_jisyo = \"path to SKK-JISYO.[SML]\"\r\n:so skk.vim or put this script into your plugin directory.\r\nTo start SKK-mode, press <C-j> in Insert-mode or Commandline-mode. ","first_name":"tyru","6":"tyru","last_name":" ","7":" ","releases":[{"0":"3118","vim_version":"6.0","1":"6.0","script_version":"0.27.0","2":"0.27.0","version_comment":"- Apply the changes of Anyakichi repository. thanks Anyakichi.\r\n-- Add g:skk_external_prog_encoding option.\r\n-- Improve text-wrapping behavior.\r\n-- Add <C-c> as cancel key for word-registration.\r\n-- Fix \";hass;uru\" conversion problem when using sticky shift.\r\n-- Do \":redraw\" before showing conversion candidates.\r\n- Move syntax\/skkdict.vim to https:\/\/github.com\/tyru\/skkdict.vim\r\n-- Bundle syntax\/skkdict.vim and ftdetect\/skkdict.vim\r\ninto zip file uploaded to www.vim.org","3":"- Apply the changes of Anyakichi repository. thanks Anyakichi.\r\n-- Add g:skk_external_prog_encoding option.\r\n-- Improve text-wrapping behavior.\r\n-- Add <C-c> as cancel key for word-registration.\r\n-- Fix \";hass;uru\" conversion problem when using sticky shift.\r\n-- Do \":redraw\" before showing conversion candidates.\r\n- Move syntax\/skkdict.vim to https:\/\/github.com\/tyru\/skkdict.vim\r\n-- Bundle syntax\/skkdict.vim and ftdetect\/skkdict.vim\r\ninto zip file uploaded to www.vim.org","package":"skk.zip","4":"skk.zip","src_id":"15190","5":"15190","creation_date":"1299778344","6":"1299778344"},{"0":"3118","vim_version":"6.0","1":"6.0","script_version":"0.26.2","2":"0.26.2","version_comment":"NOTE: Removed v0.26.0 from vim.org\r\n\r\nv0.26.2:\r\n- Fix fatal bug: g:skk_henkan_point_keys default value was wrongly changed\r\n- Fix bug: Several keys in normal mode mapped by skk.vim do not accept [count]. Thanks Toshiki Kataoka for reporting the bug.\r\n\r\nv0.26.0:\r\n- Applied super blooper's JLOD patch. Thanks.\r\n-- Added g:skk_enable_jlod_layout","3":"NOTE: Removed v0.26.0 from vim.org\r\n\r\nv0.26.2:\r\n- Fix fatal bug: g:skk_henkan_point_keys default value was wrongly changed\r\n- Fix bug: Several keys in normal mode mapped by skk.vim do not accept [count]. Thanks Toshiki Kataoka for reporting the bug.\r\n\r\nv0.26.0:\r\n- Applied super blooper's JLOD patch. Thanks.\r\n-- Added g:skk_enable_jlod_layout","package":"skk.zip","4":"skk.zip","src_id":"13747","5":"13747","creation_date":"1283497466","6":"1283497466"},{"0":"3118","vim_version":"6.0","1":"6.0","script_version":"0.25","2":"0.25","version_comment":"- Allow non-win32 environment to use g:skk_use_color_cursor. (it was win32 only)\r\n- Add syntax\/skk.vim (SKK dictionary)","3":"- Allow non-win32 environment to use g:skk_use_color_cursor. (it was win32 only)\r\n- Add syntax\/skk.vim (SKK dictionary)","package":"skk.zip","4":"skk.zip","src_id":"13368","5":"13368","creation_date":"1279697076","6":"1279697076"},{"0":"3118","vim_version":"6.0","1":"6.0","script_version":"0.24","2":"0.24","version_comment":"- Fix\/Add more tips to skk.jax\r\n- Implement g:skk_jisyo_encoding, g:skk_large_jisyo_encoding.\r\n(And previous version number on vim.org was wrong: 2.3.2 => 0.23.2)","3":"- Fix\/Add more tips to skk.jax\r\n- Implement g:skk_jisyo_encoding, g:skk_large_jisyo_encoding.\r\n(And previous version number on vim.org was wrong: 2.3.2 => 0.23.2)","package":"skk.zip","4":"skk.zip","src_id":"13295","5":"13295","creation_date":"1278376562","6":"1278376562"},{"0":"3118","vim_version":"6.0","1":"6.0","script_version":"2.3.2","2":"2.3.2","version_comment":"Initial upload","3":"Initial upload","package":"skk.zip","4":"skk.zip","src_id":"13154","5":"13154","creation_date":"1276161507","6":"1276161507"}]},"3117":{"script_id":"3117","0":"3117","script_name":"fu","1":"fu","script_type":"color scheme","2":"color scheme","summary":"Clean and beautiful colorscheme. Do your eyes a favour.","3":"Clean and beautiful colorscheme. Do your eyes a favour.","description":"Look for yourself.\r\nScreenshot1: http:\/\/images.datenhalter.de\/syntax_highlighting_fu_1.png\r\nScreenshot2: http:\/\/images.datenhalter.de\/syntax_highlighting_fu_2.png\r\n\r\nBlog post: http:\/\/aaron-mueller.de\/blog\/the-most-awesome-colorscheme-for-vim\r\n\r\nWARNING: This colorscheme need a 256 Color terminal.","4":"Look for yourself.\r\nScreenshot1: http:\/\/images.datenhalter.de\/syntax_highlighting_fu_1.png\r\nScreenshot2: http:\/\/images.datenhalter.de\/syntax_highlighting_fu_2.png\r\n\r\nBlog post: http:\/\/aaron-mueller.de\/blog\/the-most-awesome-colorscheme-for-vim\r\n\r\nWARNING: This colorscheme need a 256 Color terminal.","install_details":"1. Copy it into your ~\/.vim\/colors\/ folder\r\n2. Edit your ~\/.vimrc and put \"colorscheme fu\" in it","5":"1. Copy it into your ~\/.vim\/colors\/ folder\r\n2. Edit your ~\/.vimrc and put \"colorscheme fu\" in it","first_name":"Aaron","6":"Aaron","last_name":"Mueller","7":"Mueller","releases":[{"0":"3117","vim_version":"7.0","1":"7.0","script_version":"1.1","2":"1.1","version_comment":"Merge contributions from Florian Eitel (whitespace issues, color refinements) and Tinou (GUI version of the colorscheme). I also cleaned up the file a little bit.","3":"Merge contributions from Florian Eitel (whitespace issues, color refinements) and Tinou (GUI version of the colorscheme). I also cleaned up the file a little bit.","package":"fu.vim","4":"fu.vim","src_id":"13152","5":"13152","creation_date":"1276120935","6":"1276120935"},{"0":"3117","vim_version":"7.2","1":"7.2","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"fu.vim","4":"fu.vim","src_id":"13149","5":"13149","creation_date":"1276076747","6":"1276076747"}]},"3116":{"script_id":"3116","0":"3116","script_name":"CFWheels Dictionary","1":"CFWheels Dictionary","script_type":"syntax","2":"syntax","summary":"dictionary file for CFWheel functions","3":"dictionary file for CFWheel functions","description":"Functions where taken from http:\/\/cfwheels.org\/docs\/function and placed into a vim dictionary file for code completion.\r\n\r\nThis was created for use at http:\/\/www.peaksystems.com, we hope you find use for it as well.","4":"Functions where taken from http:\/\/cfwheels.org\/docs\/function and placed into a vim dictionary file for code completion.\r\n\r\nThis was created for use at http:\/\/www.peaksystems.com, we hope you find use for it as well.","install_details":"place CFWheels.dict in ~\/.vim\/dic\/\r\n\r\n------Then place the following lines in your .vimrc-------\r\nau BufRead,BufNewFile *.cfm,*.cfc set dictionary+=~\/.vim\/dic\/CFWheels.dict\r\n\"set completion matching on\r\nset complete-=k complete+=k\r\n\"case insensitive\r\nset ignorecase\r\n\r\n-------->end\r\n \r\nYou can then reload the changes with \r\n     :so % \r\nor \r\n     :source $MYVIMRC\r\ndepending on what global variables you have access to.","5":"place CFWheels.dict in ~\/.vim\/dic\/\r\n\r\n------Then place the following lines in your .vimrc-------\r\nau BufRead,BufNewFile *.cfm,*.cfc set dictionary+=~\/.vim\/dic\/CFWheels.dict\r\n\"set completion matching on\r\nset complete-=k complete+=k\r\n\"case insensitive\r\nset ignorecase\r\n\r\n-------->end\r\n \r\nYou can then reload the changes with \r\n     :so % \r\nor \r\n     :source $MYVIMRC\r\ndepending on what global variables you have access to.","first_name":"travis","6":"travis","last_name":"spangle","7":"spangle","releases":[{"0":"3116","vim_version":"6.0","1":"6.0","script_version":"1","2":"1","version_comment":"Initial upload","3":"Initial upload","package":"CFWheels.dict","4":"CFWheels.dict","src_id":"13142","5":"13142","creation_date":"1275944109","6":"1275944109"}]},"3115":{"script_id":"3115","0":"3115","script_name":"SingleCompile","1":"SingleCompile","script_type":"utility","2":"utility","summary":"Make it more convenient to compile or run a single source file.","3":"Make it more convenient to compile or run a single source file.","description":"Homepage: http:\/\/singlecompile.topbug.net\r\n\r\nThis plugin is aimed at making it more convenient to compile or run a single\r\nsource file without leaving vim.\r\n\r\nA short introduction is available here: http:\/\/www.topbug.net\/blog\/2012\/03\/07\/use-singlecompile-to-compile-and-run-a-single-source-file-easily-in-vim\/\r\n\r\nConsider this situation: you have just written a small c source file for a\r\nsmall test, but you have to write a Makefile to compile it or exit vim to\r\ncompile it or compile it using \"!gcc\" without quickfix feature because vim's\r\nmake command only use the \"make\" command? This plugin will help you out.\r\n\r\nAdd these key-mappings to your vimrc:\r\n\r\n nmap <F9> :SCCompile<cr>\r\n nmap <F10> :SCCompileRun<cr>\r\n\r\nNote that the two lines here should not have any trailing space. If your file\r\ntype is supported, then press F9 to compile your source file, and press F10 to\r\ncompile and run your source file. If there is a compilation error, and the\r\n|quickfix| feature is enabled, then you could use |:cope| command to see the\r\nerror list. You may also use \":SCChooseCompiler\" command to choose a compiler\r\nif you have more than one kind of compiler available on you system.\r\n\":SCViewResult\" will show you the last run result.\r\n\r\n\r\nFeatures:\r\n1. Compile or run the source file quickly using quickfix feature and compiler feature of vim;\r\n2. Compilers and interpreters auto detecting;\r\n3. Fast switch between several installed compilers or interpreters;\r\n4. Multi-language support;\r\n5. Custom your own compiler\/interpreter template;\r\n6. View the result of last run command at any time(requires \"tee\" command);\r\n7. Run the compiled program asynchronously and view the result at any time\r\n   (see :SCCompileRunAsync in the help file).\r\n\r\n\r\nHere is a list of built-in supported compilers or interpreter(For some\r\ncompilers, you need to set the environment varibles correctly to make them\r\navailable for SingleCompile):\r\n\r\nAda:\r\n    gnat (GNAT)\r\n\r\nbash:\r\n    bash (Bourne-Again Shell)\r\n\r\nC:\r\n    bcc (Borland C++ Builder), Windows only\r\n    cc (UNIX C Compiler), UNIX only\r\n    ch (SoftIntegration Ch)\r\n    clang (the Clang C and Objective-C compiler)\r\n    gcc (GNU C Compiler)\r\n    icc (Intel C++ Compiler)\r\n    lcc (Little C Compiler)\r\n    msvc (Microsoft Visual C++ (In PATH)), Windows only\r\n    msvc80 (Microsoft Visual C++ 2005), Windows only\r\n    msvc90 (Microsoft Visual C++ 2008), Windows only\r\n    msvc100 (Microsoft Visual C++ 2010), Windows only\r\n    msvc110 (Microsoft Visual C++ 2012), Windows only\r\n    open-watcom (Open Watcom C\/C++32 Compiler)\r\n    open64 (Open64 C Compiler), UNIX only\r\n    pcc (Portable C Compiler)\r\n    sol-studio (Sun C Compiler(Sun Solaris Studio)), UNIX only\r\n    tcc (Tiny C Compiler)\r\n    tcc-run (Tiny C Compiler with \"-run\" Flag)\r\n\r\nC++:\r\n    bcc (Borland C++ Builder), Windows Only\r\n    ch (SoftIntegration Ch)\r\n    clang (the Clang C and Objective-C compiler)\r\n    g++ (GNU C++ Compiler)\r\n    icc (Intel C++ Compiler)\r\n    msvc (Microsoft Visual C++ (In PATH)), Windows only\r\n    msvc80 (Microsoft Visual C++ 2005), Windows only\r\n    msvc90 (Microsoft Visual C++ 2008), Windows only\r\n    msvc100 (Microsoft Visual C++ 2010), Windows only\r\n    msvc110 (Microsoft Visual C++ 2012), Windows only\r\n    open-watcom (Open Watcom C\/C++32 Compiler)\r\n    open64 (Open64 C++ Compiler), UNIX only\r\n    sol-studio (Sun C++ Compiler(Sun Solaris Studio)), UNIX only\r\n\r\nC#:\r\n    msvcs(Microsoft Visual C#), Windows Only\r\n    mono (Mono C# compiler)\r\n\r\ncmake:\r\n    cmake (cmake)\r\n\r\nCoffeeScript:\r\n    coffee (CoffeeScript)\r\n\r\ncsh:\r\n    csh (C Shell)\r\n    tcsh (TENEX C Shell)\r\n\r\nD:\r\n    dmd (DMD Compiler)\r\n\r\ndos batch:\r\n    dosbatch (DOS Batch)\r\n\r\nerlang:\r\n    escript (Erlang Scripting Support)\r\n\r\nFortran:\r\n    ftn95 (Silverfrost FTN95), Windows only\r\n    g77 (GNU Fortran 77 Compiler)\r\n    g95 (G95)\r\n    gfortran (GNU Fortran Compiler)\r\n    ifort (Intel Fortran Compiler)\r\n    open-watcom (Open Watcom Fortran 77\/32 Compiler)\r\n    open64-f90 (Open64 Fortran 90 Compiler), UNIX only\r\n    open64-f95 (Open64 Fortran 95 Compiler), UNIX only\r\n    sol-studio-f77 (Sun Fortran 77 Compiler(Sun Solaris Studio)), UNIX only\r\n    sol-studio-f90 (Sun Fortran 90 Compiler(Sun Solaris Studio)), UNIX only\r\n    sol-studio-f95 (Sun Fortran 95 Compiler(Sun Solaris Studio)), UNIX only\r\n\r\nGo:\r\n    go (Go)\r\n\r\nHaskell:\r\n    ghc (Glasgow Haskell Compiler)\r\n    runhaskell (runhaskell)\r\n\r\nhtml:\r\n    arora (Arora)\r\n    chrome (Google Chrome)\r\n    chromium (Chromium)\r\n    epiphany (Epiphany)\r\n    firefox (Mozilla Firefox)\r\n    ie (Microsoft Internet Explorer)\r\n    konqueror (Konqueror)\r\n    opera (Opera)\r\n\r\nIDL(Interactive Data Language):\r\n    idl (ITT Visual Information Solutions Interactive Data Language)\r\n    gdl (GNU Data Language incremental compiler)\r\n\r\nJava:\r\n    gcj (GNU Java Compiler)\r\n    sunjdk (Sun Java Development Kit)\r\n\r\nJavaScript:\r\n    gjs (Javascript Bindings for GNOME)\r\n    js (SpiderMonkey, a JavaScript engine written in C)\r\n    node.js (node.js)\r\n    rhino (Rhino, a JavaScript engine written in Java)\r\n\r\nksh:\r\n    ksh (Korn Shell)\r\n\r\nLaTeX:\r\n    latex (LaTeX)\r\n    pdflatex (pdfLaTeX)\r\n    latexmk (Automatic LaTeX document generation routine)\r\n\r\nLISP:\r\n    clisp (GNU CLISP)\r\n    ecl (Embeddable Common-Lisp)\r\n    gcl (GNU Common Lisp)\r\n\r\nLiveScript:\r\n    lsc (LiveScript)\r\n\r\nlua:\r\n    lua (Lua Interpreter)\r\n\r\nMakefile:\r\n    gmake (GNU Make)\r\n    nmake (Microsoft Program Maintenance Utility)\r\n    mingw32-make (MinGW32 Make)\r\n\r\nMarkdown:\r\n    markdown (text-to-HTML conversion tool)\r\n    rdiscount (Discount Markdown Processor for Ruby)\r\n    Markdown (Python implementation of the Markdown language)\r\n\r\nMatlab:\r\n    matlab (MathWorks MATLAB)\r\n        Note: For Matlab, I highly recommend you to try out vim-matlab-behave plugin: https:\/\/github.com\/elmanuelito\/vim-matlab-behave\r\n    octave (GNU Octave)\r\n\r\nObject-C:\r\n    clang (the Clang C and Objective-C compiler)\r\n    gcc (GNU Object-C Compiler)\r\n\r\nPascal:\r\n    fpc (Free Pascal Compiler)\r\n    gpc (GNU Pascal Compiler)\r\n\r\nperl:\r\n    perl (Perl Interpreter)\r\n\r\nPHP:\r\n    php (PHP Command Line Interface 'CLI')\r\n\r\npython:\r\n    ironpython (IronPython)\r\n    jython (Jython)\r\n    pypy (PyPy)\r\n    python (Python Interpreter, usually the system default Python, no matter it is Python 2 or 3.)\r\n    python2 (Python 2 Interpreter)\r\n    python3 (Python 3 Interpreter)\r\n\r\nQML:\r\n    qmlscene (QML Scene, for viewing QML based on QtQuick 2)\r\n    qmlviewer (QML Viewer, for viewing QML based on QtQuick 1)\r\n    Note: vim does not detect qml files out of the box.\r\n    See https:\/\/github.com\/peterhoeg\/vim-qml\r\n\r\nR:\r\n    R (R)\r\n\r\nreStructuredText:\r\n    rst2html (reST to HTML)\r\n\r\nruby:\r\n    ruby (Ruby Interpreter)\r\n    jruby (Ruby on top of Java JVM, default mode)\r\n    jruby1.8 (Ruby on top of Java JVM, Ruby 1.8 mode)\r\n    jruby1.9 (Ruby on top of Java JVM, Ruby 1.9 mode)\r\n    jruby2.0 (Ruby on top of Java JVM, Ruby 2.0 mode, requires JRuby 1.7.4 or\r\nlater)\r\n\r\nrust:\r\n    rustc (Rust compiler)\r\n\r\nscala:\r\n    scala (Scala compiler)\r\n    Note: vim does not detect scala files out the box.\r\n    See https:\/\/github.com\/bjartek\/scala-vim-support\r\n\r\nsh:\r\n    ash (Almquist Shell)\r\n    bash (Bourne-Again Shell)\r\n    dash (Debian Almquist Shell)\r\n    ksh (Korn Shell)\r\n    sh (Bourne Shell)\r\n    zsh (Z Shell)\r\n\r\ntcl:\r\n    tclsh (Simple shell containing Tcl interpreter)\r\n\r\ntcsh:\r\n    tcsh (TENEX C Shell)\r\n\r\nvb script:\r\n    vb (VB Script Interpreter)\r\n\r\nxhtml:\r\n    arora (Arora)\r\n    chrome (Google Chrome)\r\n    epiphany (Epiphany)\r\n    firefox (Mozilla Firefox)\r\n    ie (Microsoft Internet Explorer)\r\n    konqueror (Konqueror)\r\n    opera (Opera)\r\n\r\nzsh:\r\n    zsh (Z Shell)\r\n\r\n\r\n\r\nYou can add your compiler or interpreter support if the compiler or \r\ninterpreter you want is not in the list. See details in the help file \r\nSingleCompile.txt\r\n\r\nThere are some supporting code in this plugin for Marc Weber's\r\nvim-addon-actions:\r\n     http:\/\/github.com\/MarcWeber\/vim-addon-actions \r\n\r\nFeedback is welcome. If you find any bug or have some good ideas to\r\nimprove this plugin, please feel free to report it to hong@topbug.net \r\nor submit it on the issue tracker:\r\n\r\nhttps:\/\/github.com\/xuhdev\/SingleCompile\/issues\r\n\r\nIf you've written some templates for some compilers or interpreters which are\r\nnot included as built-in template, and you think they are useful for other\r\npeople, you could send me an email to inform me, and I'll put them in the\r\nbuilt-in templates.\r\n\r\n\r\nGit Repository:  https:\/\/github.com\/xuhdev\/SingleCompile\r\n\r\nCheck the wiki pages for some tips: https:\/\/github.com\/xuhdev\/SingleCompile\/wiki\/_pages\r\n\r\nFollow xuhdev on twitter if you are interested in my development:\r\nhttp:\/\/twitter.com\/xuhdev\r\n","4":"Homepage: http:\/\/singlecompile.topbug.net\r\n\r\nThis plugin is aimed at making it more convenient to compile or run a single\r\nsource file without leaving vim.\r\n\r\nA short introduction is available here: http:\/\/www.topbug.net\/blog\/2012\/03\/07\/use-singlecompile-to-compile-and-run-a-single-source-file-easily-in-vim\/\r\n\r\nConsider this situation: you have just written a small c source file for a\r\nsmall test, but you have to write a Makefile to compile it or exit vim to\r\ncompile it or compile it using \"!gcc\" without quickfix feature because vim's\r\nmake command only use the \"make\" command? This plugin will help you out.\r\n\r\nAdd these key-mappings to your vimrc:\r\n\r\n nmap <F9> :SCCompile<cr>\r\n nmap <F10> :SCCompileRun<cr>\r\n\r\nNote that the two lines here should not have any trailing space. If your file\r\ntype is supported, then press F9 to compile your source file, and press F10 to\r\ncompile and run your source file. If there is a compilation error, and the\r\n|quickfix| feature is enabled, then you could use |:cope| command to see the\r\nerror list. You may also use \":SCChooseCompiler\" command to choose a compiler\r\nif you have more than one kind of compiler available on you system.\r\n\":SCViewResult\" will show you the last run result.\r\n\r\n\r\nFeatures:\r\n1. Compile or run the source file quickly using quickfix feature and compiler feature of vim;\r\n2. Compilers and interpreters auto detecting;\r\n3. Fast switch between several installed compilers or interpreters;\r\n4. Multi-language support;\r\n5. Custom your own compiler\/interpreter template;\r\n6. View the result of last run command at any time(requires \"tee\" command);\r\n7. Run the compiled program asynchronously and view the result at any time\r\n   (see :SCCompileRunAsync in the help file).\r\n\r\n\r\nHere is a list of built-in supported compilers or interpreter(For some\r\ncompilers, you need to set the environment varibles correctly to make them\r\navailable for SingleCompile):\r\n\r\nAda:\r\n    gnat (GNAT)\r\n\r\nbash:\r\n    bash (Bourne-Again Shell)\r\n\r\nC:\r\n    bcc (Borland C++ Builder), Windows only\r\n    cc (UNIX C Compiler), UNIX only\r\n    ch (SoftIntegration Ch)\r\n    clang (the Clang C and Objective-C compiler)\r\n    gcc (GNU C Compiler)\r\n    icc (Intel C++ Compiler)\r\n    lcc (Little C Compiler)\r\n    msvc (Microsoft Visual C++ (In PATH)), Windows only\r\n    msvc80 (Microsoft Visual C++ 2005), Windows only\r\n    msvc90 (Microsoft Visual C++ 2008), Windows only\r\n    msvc100 (Microsoft Visual C++ 2010), Windows only\r\n    msvc110 (Microsoft Visual C++ 2012), Windows only\r\n    open-watcom (Open Watcom C\/C++32 Compiler)\r\n    open64 (Open64 C Compiler), UNIX only\r\n    pcc (Portable C Compiler)\r\n    sol-studio (Sun C Compiler(Sun Solaris Studio)), UNIX only\r\n    tcc (Tiny C Compiler)\r\n    tcc-run (Tiny C Compiler with \"-run\" Flag)\r\n\r\nC++:\r\n    bcc (Borland C++ Builder), Windows Only\r\n    ch (SoftIntegration Ch)\r\n    clang (the Clang C and Objective-C compiler)\r\n    g++ (GNU C++ Compiler)\r\n    icc (Intel C++ Compiler)\r\n    msvc (Microsoft Visual C++ (In PATH)), Windows only\r\n    msvc80 (Microsoft Visual C++ 2005), Windows only\r\n    msvc90 (Microsoft Visual C++ 2008), Windows only\r\n    msvc100 (Microsoft Visual C++ 2010), Windows only\r\n    msvc110 (Microsoft Visual C++ 2012), Windows only\r\n    open-watcom (Open Watcom C\/C++32 Compiler)\r\n    open64 (Open64 C++ Compiler), UNIX only\r\n    sol-studio (Sun C++ Compiler(Sun Solaris Studio)), UNIX only\r\n\r\nC#:\r\n    msvcs(Microsoft Visual C#), Windows Only\r\n    mono (Mono C# compiler)\r\n\r\ncmake:\r\n    cmake (cmake)\r\n\r\nCoffeeScript:\r\n    coffee (CoffeeScript)\r\n\r\ncsh:\r\n    csh (C Shell)\r\n    tcsh (TENEX C Shell)\r\n\r\nD:\r\n    dmd (DMD Compiler)\r\n\r\ndos batch:\r\n    dosbatch (DOS Batch)\r\n\r\nerlang:\r\n    escript (Erlang Scripting Support)\r\n\r\nFortran:\r\n    ftn95 (Silverfrost FTN95), Windows only\r\n    g77 (GNU Fortran 77 Compiler)\r\n    g95 (G95)\r\n    gfortran (GNU Fortran Compiler)\r\n    ifort (Intel Fortran Compiler)\r\n    open-watcom (Open Watcom Fortran 77\/32 Compiler)\r\n    open64-f90 (Open64 Fortran 90 Compiler), UNIX only\r\n    open64-f95 (Open64 Fortran 95 Compiler), UNIX only\r\n    sol-studio-f77 (Sun Fortran 77 Compiler(Sun Solaris Studio)), UNIX only\r\n    sol-studio-f90 (Sun Fortran 90 Compiler(Sun Solaris Studio)), UNIX only\r\n    sol-studio-f95 (Sun Fortran 95 Compiler(Sun Solaris Studio)), UNIX only\r\n\r\nGo:\r\n    go (Go)\r\n\r\nHaskell:\r\n    ghc (Glasgow Haskell Compiler)\r\n    runhaskell (runhaskell)\r\n\r\nhtml:\r\n    arora (Arora)\r\n    chrome (Google Chrome)\r\n    chromium (Chromium)\r\n    epiphany (Epiphany)\r\n    firefox (Mozilla Firefox)\r\n    ie (Microsoft Internet Explorer)\r\n    konqueror (Konqueror)\r\n    opera (Opera)\r\n\r\nIDL(Interactive Data Language):\r\n    idl (ITT Visual Information Solutions Interactive Data Language)\r\n    gdl (GNU Data Language incremental compiler)\r\n\r\nJava:\r\n    gcj (GNU Java Compiler)\r\n    sunjdk (Sun Java Development Kit)\r\n\r\nJavaScript:\r\n    gjs (Javascript Bindings for GNOME)\r\n    js (SpiderMonkey, a JavaScript engine written in C)\r\n    node.js (node.js)\r\n    rhino (Rhino, a JavaScript engine written in Java)\r\n\r\nksh:\r\n    ksh (Korn Shell)\r\n\r\nLaTeX:\r\n    latex (LaTeX)\r\n    pdflatex (pdfLaTeX)\r\n    latexmk (Automatic LaTeX document generation routine)\r\n\r\nLISP:\r\n    clisp (GNU CLISP)\r\n    ecl (Embeddable Common-Lisp)\r\n    gcl (GNU Common Lisp)\r\n\r\nLiveScript:\r\n    lsc (LiveScript)\r\n\r\nlua:\r\n    lua (Lua Interpreter)\r\n\r\nMakefile:\r\n    gmake (GNU Make)\r\n    nmake (Microsoft Program Maintenance Utility)\r\n    mingw32-make (MinGW32 Make)\r\n\r\nMarkdown:\r\n    markdown (text-to-HTML conversion tool)\r\n    rdiscount (Discount Markdown Processor for Ruby)\r\n    Markdown (Python implementation of the Markdown language)\r\n\r\nMatlab:\r\n    matlab (MathWorks MATLAB)\r\n        Note: For Matlab, I highly recommend you to try out vim-matlab-behave plugin: https:\/\/github.com\/elmanuelito\/vim-matlab-behave\r\n    octave (GNU Octave)\r\n\r\nObject-C:\r\n    clang (the Clang C and Objective-C compiler)\r\n    gcc (GNU Object-C Compiler)\r\n\r\nPascal:\r\n    fpc (Free Pascal Compiler)\r\n    gpc (GNU Pascal Compiler)\r\n\r\nperl:\r\n    perl (Perl Interpreter)\r\n\r\nPHP:\r\n    php (PHP Command Line Interface 'CLI')\r\n\r\npython:\r\n    ironpython (IronPython)\r\n    jython (Jython)\r\n    pypy (PyPy)\r\n    python (Python Interpreter, usually the system default Python, no matter it is Python 2 or 3.)\r\n    python2 (Python 2 Interpreter)\r\n    python3 (Python 3 Interpreter)\r\n\r\nQML:\r\n    qmlscene (QML Scene, for viewing QML based on QtQuick 2)\r\n    qmlviewer (QML Viewer, for viewing QML based on QtQuick 1)\r\n    Note: vim does not detect qml files out of the box.\r\n    See https:\/\/github.com\/peterhoeg\/vim-qml\r\n\r\nR:\r\n    R (R)\r\n\r\nreStructuredText:\r\n    rst2html (reST to HTML)\r\n\r\nruby:\r\n    ruby (Ruby Interpreter)\r\n    jruby (Ruby on top of Java JVM, default mode)\r\n    jruby1.8 (Ruby on top of Java JVM, Ruby 1.8 mode)\r\n    jruby1.9 (Ruby on top of Java JVM, Ruby 1.9 mode)\r\n    jruby2.0 (Ruby on top of Java JVM, Ruby 2.0 mode, requires JRuby 1.7.4 or\r\nlater)\r\n\r\nrust:\r\n    rustc (Rust compiler)\r\n\r\nscala:\r\n    scala (Scala compiler)\r\n    Note: vim does not detect scala files out the box.\r\n    See https:\/\/github.com\/bjartek\/scala-vim-support\r\n\r\nsh:\r\n    ash (Almquist Shell)\r\n    bash (Bourne-Again Shell)\r\n    dash (Debian Almquist Shell)\r\n    ksh (Korn Shell)\r\n    sh (Bourne Shell)\r\n    zsh (Z Shell)\r\n\r\ntcl:\r\n    tclsh (Simple shell containing Tcl interpreter)\r\n\r\ntcsh:\r\n    tcsh (TENEX C Shell)\r\n\r\nvb script:\r\n    vb (VB Script Interpreter)\r\n\r\nxhtml:\r\n    arora (Arora)\r\n    chrome (Google Chrome)\r\n    epiphany (Epiphany)\r\n    firefox (Mozilla Firefox)\r\n    ie (Microsoft Internet Explorer)\r\n    konqueror (Konqueror)\r\n    opera (Opera)\r\n\r\nzsh:\r\n    zsh (Z Shell)\r\n\r\n\r\n\r\nYou can add your compiler or interpreter support if the compiler or \r\ninterpreter you want is not in the list. See details in the help file \r\nSingleCompile.txt\r\n\r\nThere are some supporting code in this plugin for Marc Weber's\r\nvim-addon-actions:\r\n     http:\/\/github.com\/MarcWeber\/vim-addon-actions \r\n\r\nFeedback is welcome. If you find any bug or have some good ideas to\r\nimprove this plugin, please feel free to report it to hong@topbug.net \r\nor submit it on the issue tracker:\r\n\r\nhttps:\/\/github.com\/xuhdev\/SingleCompile\/issues\r\n\r\nIf you've written some templates for some compilers or interpreters which are\r\nnot included as built-in template, and you think they are useful for other\r\npeople, you could send me an email to inform me, and I'll put them in the\r\nbuilt-in templates.\r\n\r\n\r\nGit Repository:  https:\/\/github.com\/xuhdev\/SingleCompile\r\n\r\nCheck the wiki pages for some tips: https:\/\/github.com\/xuhdev\/SingleCompile\/wiki\/_pages\r\n\r\nFollow xuhdev on twitter if you are interested in my development:\r\nhttp:\/\/twitter.com\/xuhdev\r\n","install_details":"   Download the SingleCompile.zip file and extract it to your vim runtime\r\ndirectory(~\/.vim in UNIX\/Linux and $VIM_INSTALLATION_FOLDER\\vimfiles in windows).\r\n\r\nadd \"filetype plugin on\" to your vimrc if you haven't done it.","5":"   Download the SingleCompile.zip file and extract it to your vim runtime\r\ndirectory(~\/.vim in UNIX\/Linux and $VIM_INSTALLATION_FOLDER\\vimfiles in windows).\r\n\r\nadd \"filetype plugin on\" to your vimrc if you haven't done it.","first_name":"Hong","6":"Hong","last_name":"Xu","7":"Xu","releases":[{"0":"3115","vim_version":"7.2","1":"7.2","script_version":"2.12.0","2":"2.12.0","version_comment":"Fish Shell is supported;\r\nAdded builtin template: CoffeeScript, LiveScript, octave, JRuby, markdown.py, QML;\r\nSupport vertical splits on SCViewResult (See the g:SingleCompile_split option);\r\nMany bug fixes.","3":"Fish Shell is supported;\r\nAdded builtin template: CoffeeScript, LiveScript, octave, JRuby, markdown.py, QML;\r\nSupport vertical splits on SCViewResult (See the g:SingleCompile_split option);\r\nMany bug fixes.","package":"SingleCompile-2.12.0.zip","4":"SingleCompile-2.12.0.zip","src_id":"22022","5":"22022","creation_date":"1402511279","6":"1402511279"},{"0":"3115","vim_version":"7.0","1":"7.0","script_version":"2.11.0","2":"2.11.0","version_comment":"Add g:SingleCompile_quickfixwindowposition option to control the quickfix window position when popped up by SingleCompile;\r\nAdd g:SingleCompile_usetee option to enable and disable the use of `tee` (By zhou13).","3":"Add g:SingleCompile_quickfixwindowposition option to control the quickfix window position when popped up by SingleCompile;\r\nAdd g:SingleCompile_usetee option to enable and disable the use of `tee` (By zhou13).","package":"SingleCompile-2.11.0.zip","4":"SingleCompile-2.11.0.zip","src_id":"20188","5":"20188","creation_date":"1369074795","6":"1369074795"},{"0":"3115","vim_version":"7.0","1":"7.0","script_version":"2.10.7","2":"2.10.7","version_comment":"Add built-in template for go, rst, latexmk, and scala (note vim does not detect scala files out of the box. You may need to see https:\/\/github.com\/bjartek\/scala-vim-support);\r\nOptimize the built-in python template;\r\nmany minor bug fixes.","3":"Add built-in template for go, rst, latexmk, and scala (note vim does not detect scala files out of the box. You may need to see https:\/\/github.com\/bjartek\/scala-vim-support);\r\nOptimize the built-in python template;\r\nmany minor bug fixes.","package":"SingleCompile-2.10.7.zip","4":"SingleCompile-2.10.7.zip","src_id":"19513","5":"19513","creation_date":"1360820877","6":"1360820877"},{"0":"3115","vim_version":"7.0","1":"7.0","script_version":"2.10.6","2":"2.10.6","version_comment":"Fix cmake and dosbatch builtin template issues;\r\nAdd rst2html builtin template.","3":"Fix cmake and dosbatch builtin template issues;\r\nAdd rst2html builtin template.","package":"SingleCompile-2.10.6.zip","4":"SingleCompile-2.10.6.zip","src_id":"18352","5":"18352","creation_date":"1343734925","6":"1343734925"},{"0":"3115","vim_version":"7.0","1":"7.0","script_version":"2.10.5","2":"2.10.5","version_comment":"Fix an issue that if quickfix opens another file with a different file title when compiling, the run fails.","3":"Fix an issue that if quickfix opens another file with a different file title when compiling, the run fails.","package":"SingleCompile-2.10.5.zip","4":"SingleCompile-2.10.5.zip","src_id":"17958","5":"17958","creation_date":"1337049113","6":"1337049113"},{"0":"3115","vim_version":"7.0","1":"7.0","script_version":"2.10.4","2":"2.10.4","version_comment":"Add markdown builtin template;\r\nsplit builtin templates into small files;\r\na variety of bug fixes.","3":"Add markdown builtin template;\r\nsplit builtin templates into small files;\r\na variety of bug fixes.","package":"SingleCompile-2.10.4.zip","4":"SingleCompile-2.10.4.zip","src_id":"17908","5":"17908","creation_date":"1336542303","6":"1336542303"},{"0":"3115","vim_version":"7.0","1":"7.0","script_version":"2.10.3","2":"2.10.3","version_comment":"Do some code cleanup.\r\nRelease the final version of 2.10.x.","3":"Do some code cleanup.\r\nRelease the final version of 2.10.x.","package":"SingleCompile.zip","4":"SingleCompile.zip","src_id":"17775","5":"17775","creation_date":"1334455747","6":"1334455747"},{"0":"3115","vim_version":"7.0","1":"7.0","script_version":"2.10.2beta","2":"2.10.2beta","version_comment":"g:SingleCompile_showquickfixiferror option now supports interpreting languages on UNIX (not on Windows yet);\r\nsome minor improvements.","3":"g:SingleCompile_showquickfixiferror option now supports interpreting languages on UNIX (not on Windows yet);\r\nsome minor improvements.","package":"SingleCompile-2.10.2-beta.zip","4":"SingleCompile-2.10.2-beta.zip","src_id":"17635","5":"17635","creation_date":"1332399257","6":"1332399257"},{"0":"3115","vim_version":"7.0","1":"7.0","script_version":"2.10.1beta","2":"2.10.1beta","version_comment":"Some improvements for the result view window (by John Tyree);\r\n:SCChooseCompiler will display the current active compiler.\r\nsome minor bug fix if the result is set to be displayed right after compilation (by John Tyree).\r\n","3":"Some improvements for the result view window (by John Tyree);\r\n:SCChooseCompiler will display the current active compiler.\r\nsome minor bug fix if the result is set to be displayed right after compilation (by John Tyree).\r\n","package":"SingleCompile-2.10.1-beta.zip","4":"SingleCompile-2.10.1-beta.zip","src_id":"17552","5":"17552","creation_date":"1330669952","6":"1330669952"},{"0":"3115","vim_version":"7.0","1":"7.0","script_version":"2.10.0beta","2":"2.10.0beta","version_comment":"Implement old style template settings in a better way (Should make the plugin work faster and the code cleaner);\r\nAdd node.js built-in template for javascript. (By flebber)","3":"Implement old style template settings in a better way (Should make the plugin work faster and the code cleaner);\r\nAdd node.js built-in template for javascript. (By flebber)","package":"SingleCompile-2.10.0beta.zip","4":"SingleCompile-2.10.0beta.zip","src_id":"17306","5":"17306","creation_date":"1327335771","6":"1327335771"},{"0":"3115","vim_version":"7.0","1":"7.0","script_version":"2.9.3","2":"2.9.3","version_comment":"Add gjs(Javascript Bindings for GNOME) built-in template;\r\nadd an important note in the key mapping part of the doc (reported by flebber);\r\nadd git repo URL to the doc;\r\nadd License header.","3":"Add gjs(Javascript Bindings for GNOME) built-in template;\r\nadd an important note in the key mapping part of the doc (reported by flebber);\r\nadd git repo URL to the doc;\r\nadd License header.","package":"SingleCompile-2.9.3.zip","4":"SingleCompile-2.9.3.zip","src_id":"17187","5":"17187","creation_date":"1326280450","6":"1326280450"},{"0":"3115","vim_version":"7.0","1":"7.0","script_version":"2.9.2","2":"2.9.2","version_comment":"Fix a problem that function SingleCompile#SetCompilerTemplateByDict cannot change compilers' priority;\r\nFix an issue that Borland C Compiler built-in template cannot successfully compile a C and C++ source file;\r\nAdd priority for tex built-in template.","3":"Fix a problem that function SingleCompile#SetCompilerTemplateByDict cannot change compilers' priority;\r\nFix an issue that Borland C Compiler built-in template cannot successfully compile a C and C++ source file;\r\nAdd priority for tex built-in template.","package":"SingleCompile-2.9.2.zip","4":"SingleCompile-2.9.2.zip","src_id":"16914","5":"16914","creation_date":"1321855112","6":"1321855112"},{"0":"3115","vim_version":"7.0","1":"7.0","script_version":"2.9.1","2":"2.9.1","version_comment":"Complete document related to compiler priority;\r\nadd chromium built-in template;\r\nfix IE priority bug in the built-in template.","3":"Complete document related to compiler priority;\r\nadd chromium built-in template;\r\nfix IE priority bug in the built-in template.","package":"SingleCompile-2.9.1.zip","4":"SingleCompile-2.9.1.zip","src_id":"16626","5":"16626","creation_date":"1317869208","6":"1317869208"},{"0":"3115","vim_version":"7.0","1":"7.0","script_version":"2.9beta","2":"2.9beta","version_comment":"Now compiler template contains \"priority\" field, and each built-in template have been set a priority; this means, when user does not choose one compiler explicitly, SingleCompile will automatically choose the compiler with the highest priority (related document is not available yet);\r\nAdd clang built-in template for Object-C;\r\nsome minor improvement of clang built-in template for C and C++.","3":"Now compiler template contains \"priority\" field, and each built-in template have been set a priority; this means, when user does not choose one compiler explicitly, SingleCompile will automatically choose the compiler with the highest priority (related document is not available yet);\r\nAdd clang built-in template for Object-C;\r\nsome minor improvement of clang built-in template for C and C++.","package":"SingleCompile_2.9beta.zip","4":"SingleCompile_2.9beta.zip","src_id":"16551","5":"16551","creation_date":"1316402155","6":"1316402155"},{"0":"3115","vim_version":"7.0","1":"7.0","script_version":"2.8.9","2":"2.8.9","version_comment":"Improve the detection of Microsoft Visual C++ in the built-in template on Windows (Specified version of MSVC could be detected now)\r\n** No need to upgrade to this version if you do not use Microsoft Visual C++","3":"Improve the detection of Microsoft Visual C++ in the built-in template on Windows (Specified version of MSVC could be detected now)\r\n** No need to upgrade to this version if you do not use Microsoft Visual C++","package":"SingleCompile.zip","4":"SingleCompile.zip","src_id":"16474","5":"16474","creation_date":"1315297959","6":"1315297959"},{"0":"3115","vim_version":"7.0","1":"7.0","script_version":"2.8.8","2":"2.8.8","version_comment":"When using :SCChooseCompiler, list compilers ordered alphabetically;\r\nAdd arora, epiphany built-in template for html and xhtml;\r\nImprove the detection of IE on Windows;\r\nRemove OS\/2 supporting code since they are unable to be tested(send me an email if you have problems on this).","3":"When using :SCChooseCompiler, list compilers ordered alphabetically;\r\nAdd arora, epiphany built-in template for html and xhtml;\r\nImprove the detection of IE on Windows;\r\nRemove OS\/2 supporting code since they are unable to be tested(send me an email if you have problems on this).","package":"SingleCompile.zip","4":"SingleCompile.zip","src_id":"16444","5":"16444","creation_date":"1315043362","6":"1315043362"},{"0":"3115","vim_version":"7.0","1":"7.0","script_version":"2.8.7","2":"2.8.7","version_comment":"Fix some python asynchronous mode availability detection problem;\r\nAdd GNAT Ada compiler built-in template.","3":"Fix some python asynchronous mode availability detection problem;\r\nAdd GNAT Ada compiler built-in template.","package":"SingleCompile.zip","4":"SingleCompile.zip","src_id":"15979","5":"15979","creation_date":"1309085599","6":"1309085599"},{"0":"3115","vim_version":"7.0","1":"7.0","script_version":"2.8.6","2":"2.8.6","version_comment":"Add Object-C built-in template (gcc);\r\nimprove Javascript and idl built-in template.","3":"Add Object-C built-in template (gcc);\r\nimprove Javascript and idl built-in template.","package":"SingleCompile.zip","4":"SingleCompile.zip","src_id":"15884","5":"15884","creation_date":"1308058222","6":"1308058222"},{"0":"3115","vim_version":"7.0","1":"7.0","script_version":"2.8.5","2":"2.8.5","version_comment":"Add php built-in template;\r\nHide the console window when run asynchronously on Windows.","3":"Add php built-in template;\r\nHide the console window when run asynchronously on Windows.","package":"SingleCompile.zip","4":"SingleCompile.zip","src_id":"15723","5":"15723","creation_date":"1306335257","6":"1306335257"},{"0":"3115","vim_version":"7.0","1":"7.0","script_version":"2.8.4beta","2":"2.8.4beta","version_comment":"Some message improvements for asynchronous run.","3":"Some message improvements for asynchronous run.","package":"SingleCompile.zip","4":"SingleCompile.zip","src_id":"15694","5":"15694","creation_date":"1306044482","6":"1306044482"},{"0":"3115","vim_version":"7.0","1":"7.0","script_version":"2.8.3beta","2":"2.8.3beta","version_comment":"Add :SCIsRunningAsync command to check whether there are background process running asynchronously;\r\nmany improvements on MS-Windows for asynchronous running;\r\nadd :SCTerminateAsync and :SCViewResultAsync commands to menu;\r\nsome minor bug fixes.","3":"Add :SCIsRunningAsync command to check whether there are background process running asynchronously;\r\nmany improvements on MS-Windows for asynchronous running;\r\nadd :SCTerminateAsync and :SCViewResultAsync commands to menu;\r\nsome minor bug fixes.","package":"SingleCompile.zip","4":"SingleCompile.zip","src_id":"15689","5":"15689","creation_date":"1305941876","6":"1305941876"},{"0":"3115","vim_version":"7.0","1":"7.0","script_version":"2.8.2beta","2":"2.8.2beta","version_comment":"Add 'auto' mode for asynchronous running;\r\nadd :SCTerminateAsync command;\r\nsome bug fixes and improvements.","3":"Add 'auto' mode for asynchronous running;\r\nadd :SCTerminateAsync command;\r\nsome bug fixes and improvements.","package":"SingleCompile.zip","4":"SingleCompile.zip","src_id":"15647","5":"15647","creation_date":"1305515325","6":"1305515325"},{"0":"3115","vim_version":"7.0","1":"7.0","script_version":"2.8.1beta","2":"2.8.1beta","version_comment":"Make asynchronous run feature also available for interpreting language;\r\nsome minor bug fixes and improvements for async mode.","3":"Make asynchronous run feature also available for interpreting language;\r\nsome minor bug fixes and improvements for async mode.","package":"SingleCompile.zip","4":"SingleCompile.zip","src_id":"15637","5":"15637","creation_date":"1305370180","6":"1305370180"},{"0":"3115","vim_version":"7.0","1":"7.0","script_version":"2.8beta","2":"2.8beta","version_comment":"Now compiled program could be run\r\nasynchronously. (Currently this new feature requires vim compiled with python interface\r\n2.6+)","3":"Now compiled program could be run\r\nasynchronously. (Currently this new feature requires vim compiled with python interface\r\n2.6+)","package":"SingleCompile.zip","4":"SingleCompile.zip","src_id":"15636","5":"15636","creation_date":"1305348227","6":"1305348227"},{"0":"3115","vim_version":"7.0","1":"7.0","script_version":"2.7.3","2":"2.7.3","version_comment":"Fix a bug in IDL built-in template;\r\nadd pascal and erlang built-in template by Zhou Yichao;\r\nsome minor bug-fixes and improvements by Zhou Yichao.","3":"Fix a bug in IDL built-in template;\r\nadd pascal and erlang built-in template by Zhou Yichao;\r\nsome minor bug-fixes and improvements by Zhou Yichao.","package":"SingleCompile.zip","4":"SingleCompile.zip","src_id":"15611","5":"15611","creation_date":"1304913114","6":"1304913114"},{"0":"3115","vim_version":"7.0","1":"7.0","script_version":"2.7.2","2":"2.7.2","version_comment":"Fix a problem when compiling if using the deprecated way to add templates;\r\nfix a shell determination problem;\r\nadd IDL built-in template;","3":"Fix a problem when compiling if using the deprecated way to add templates;\r\nfix a shell determination problem;\r\nadd IDL built-in template;","package":"SingleCompile.zip","4":"SingleCompile.zip","src_id":"15461","5":"15461","creation_date":"1303017229","6":"1303017229"},{"0":"3115","vim_version":"7.0","1":"7.0","script_version":"2.7.1","2":"2.7.1","version_comment":"Fix redirection issues under csh and tcsh;\r\nadd option g:SingleCompile_showresultafterrun.","3":"Fix redirection issues under csh and tcsh;\r\nadd option g:SingleCompile_showresultafterrun.","package":"SingleCompile.zip","4":"SingleCompile.zip","src_id":"15327","5":"15327","creation_date":"1301403147","6":"1301403147"},{"0":"3115","vim_version":"7.0","1":"7.0","script_version":"2.6","2":"2.6","version_comment":"Add option g:SingleCompile_showquickfixiferror;\r\nfix a few bugs in the built-in template including templates for g++, clang and dosbatch.","3":"Add option g:SingleCompile_showquickfixiferror;\r\nfix a few bugs in the built-in template including templates for g++, clang and dosbatch.","package":"SingleCompile.zip","4":"SingleCompile.zip","src_id":"15250","5":"15250","creation_date":"1300500772","6":"1300500772"},{"0":"3115","vim_version":"7.0","1":"7.0","script_version":"2.5","2":"2.5","version_comment":"Integrate with vim's compiler feature;\r\nadd G95 and Microsoft Visual C# built-in template;\r\nfix some minor bugs.","3":"Integrate with vim's compiler feature;\r\nadd G95 and Microsoft Visual C# built-in template;\r\nfix some minor bugs.","package":"SingleCompile.zip","4":"SingleCompile.zip","src_id":"15213","5":"15213","creation_date":"1300072743","6":"1300072743"},{"0":"3115","vim_version":"7.0","1":"7.0","script_version":"2.4.2","2":"2.4.2","version_comment":"Fix a bug which may cause some programs of some language, such as java, c#, may not run properly;\r\nAdd C#(mono) built-in template.","3":"Fix a bug which may cause some programs of some language, such as java, c#, may not run properly;\r\nAdd C#(mono) built-in template.","package":"SingleCompile.zip","4":"SingleCompile.zip","src_id":"15168","5":"15168","creation_date":"1299464517","6":"1299464517"},{"0":"3115","vim_version":"7.0","1":"7.0","script_version":"2.4.1","2":"2.4.1","version_comment":"Add g:SingleCompile_resultheight option;\r\nadd TCL language built-in template.","3":"Add g:SingleCompile_resultheight option;\r\nadd TCL language built-in template.","package":"SingleCompile.zip","4":"SingleCompile.zip","src_id":"15160","5":"15160","creation_date":"1299294410","6":"1299294410"},{"0":"3115","vim_version":"7.0","1":"7.0","script_version":"2.4beta","2":"2.4beta","version_comment":"Add SCViewResult command, which allows you see the output result of last run command;\r\nif tee command is available, also use 'tee' to redirect the output result on Windows.","3":"Add SCViewResult command, which allows you see the output result of last run command;\r\nif tee command is available, also use 'tee' to redirect the output result on Windows.","package":"SingleCompile.zip","4":"SingleCompile.zip","src_id":"14977","5":"14977","creation_date":"1297135207","6":"1297135207"},{"0":"3115","vim_version":"7.0","1":"7.0","script_version":"2.3.4","2":"2.3.4","version_comment":"Add R and zsh built-in template.\r\nUpdate the document.","3":"Add R and zsh built-in template.\r\nUpdate the document.","package":"SingleCompile.zip","4":"SingleCompile.zip","src_id":"14969","5":"14969","creation_date":"1297076016","6":"1297076016"},{"0":"3115","vim_version":"7.0","1":"7.0","script_version":"2.3.3","2":"2.3.3","version_comment":"Fix some problems when the source file name contains spaces.","3":"Fix some problems when the source file name contains spaces.","package":"SingleCompile.zip","4":"SingleCompile.zip","src_id":"14933","5":"14933","creation_date":"1296550822","6":"1296550822"},{"0":"3115","vim_version":"7.0","1":"7.0","script_version":"2.3.2","2":"2.3.2","version_comment":"Add csh and tcsh built-in template;\r\nimprove sh built-in template;\r\ngives an error message when choose a compiler\/interpreter whose template is not set.","3":"Add csh and tcsh built-in template;\r\nimprove sh built-in template;\r\ngives an error message when choose a compiler\/interpreter whose template is not set.","package":"SingleCompile.zip","4":"SingleCompile.zip","src_id":"14889","5":"14889","creation_date":"1296189255","6":"1296189255"},{"0":"3115","vim_version":"7.2","1":"7.2","script_version":"2.3beta","2":"2.3beta","version_comment":"Add out-file feature. out-file feature is a feature which will detect whether the current file requires compilation according to the last modification time of the source file and the output file.\r\nMakes gfortran available on Windows for built-in template.","3":"Add out-file feature. out-file feature is a feature which will detect whether the current file requires compilation according to the last modification time of the source file and the output file.\r\nMakes gfortran available on Windows for built-in template.","package":"SingleCompile.zip","4":"SingleCompile.zip","src_id":"14818","5":"14818","creation_date":"1295611698","6":"1295611698"},{"0":"3115","vim_version":"7.2","1":"7.2","script_version":"2.2.10","2":"2.2.10","version_comment":"fix a bug when showing some specific messages.","3":"fix a bug when showing some specific messages.","package":"SingleCompile.zip","4":"SingleCompile.zip","src_id":"14738","5":"14738","creation_date":"1294843710","6":"1294843710"},{"0":"3115","vim_version":"7.2","1":"7.2","script_version":"2.2.9","2":"2.2.9","version_comment":"Fix a bug when quickfix for this plugin is set to be unused.","3":"Fix a bug when quickfix for this plugin is set to be unused.","package":"SingleCompile.zip","4":"SingleCompile.zip","src_id":"14636","5":"14636","creation_date":"1293534194","6":"1293534194"},{"0":"3115","vim_version":"7.2","1":"7.2","script_version":"2.2.8","2":"2.2.8","version_comment":"fix a language template bug.","3":"fix a language template bug.","package":"SingleCompile.zip","4":"SingleCompile.zip","src_id":"14629","5":"14629","creation_date":"1293433274","6":"1293433274"},{"0":"3115","vim_version":"7.2","1":"7.2","script_version":"2.2.7","2":"2.2.7","version_comment":"Add D language support.(Thanks, sky hi!)\r\nFix a bug about math.h recognization for C and C++.","3":"Add D language support.(Thanks, sky hi!)\r\nFix a bug about math.h recognization for C and C++.","package":"SingleCompile.zip","4":"SingleCompile.zip","src_id":"14611","5":"14611","creation_date":"1293190234","6":"1293190234"},{"0":"3115","vim_version":"7.2","1":"7.2","script_version":"2.2.6","2":"2.2.6","version_comment":"Optimize the error message when no filetype is specified when compiling;\r\nwhen buffer's name is empty, gives an error message.","3":"Optimize the error message when no filetype is specified when compiling;\r\nwhen buffer's name is empty, gives an error message.","package":"SingleCompile.zip","4":"SingleCompile.zip","src_id":"14461","5":"14461","creation_date":"1291860321","6":"1291860321"},{"0":"3115","vim_version":"7.2","1":"7.2","script_version":"2.2.5","2":"2.2.5","version_comment":"Apply Darek's patch as a better solution to fix the directory switching bug;(Thanks, Darek!)\r\nif the language template is not defined, show an error message when using \":SCChooseCompiler\" command.","3":"Apply Darek's patch as a better solution to fix the directory switching bug;(Thanks, Darek!)\r\nif the language template is not defined, show an error message when using \":SCChooseCompiler\" command.","package":"SingleCompile.zip","4":"SingleCompile.zip","src_id":"14416","5":"14416","creation_date":"1291307618","6":"1291307618"},{"0":"3115","vim_version":"7.2","1":"7.2","script_version":"2.2.4","2":"2.2.4","version_comment":"still fix directory switching problem.","3":"still fix directory switching problem.","package":"SingleCompile.zip","4":"SingleCompile.zip","src_id":"14415","5":"14415","creation_date":"1291280980","6":"1291280980"},{"0":"3115","vim_version":"7.0","1":"7.0","script_version":"2.2","2":"2.2","version_comment":"Add \"Predo\", \"Postdo\" features; \r\nmakes template smarter(such as automatically add \"-lm\" flag on UNIX when using some C compilers if math.h is included);\r\nadd some new template(Haskell, etc);\r\nimprove the document;\r\nfix some bugs.","3":"Add \"Predo\", \"Postdo\" features; \r\nmakes template smarter(such as automatically add \"-lm\" flag on UNIX when using some C compilers if math.h is included);\r\nadd some new template(Haskell, etc);\r\nimprove the document;\r\nfix some bugs.","package":"SingleCompile.zip","4":"SingleCompile.zip","src_id":"14357","5":"14357","creation_date":"1290492712","6":"1290492712"},{"0":"3115","vim_version":"7.0","1":"7.0","script_version":"1.2.1","2":"1.2.1","version_comment":"Fix a minor document bug.","3":"Fix a minor document bug.","package":"SingleCompile.zip","4":"SingleCompile.zip","src_id":"13755","5":"13755","creation_date":"1283534759","6":"1283534759"}]},"3114":{"script_id":"3114","0":"3114","script_name":"easytags.vim","1":"easytags.vim","script_type":"utility","2":"utility","summary":"Automated tag file generation and syntax highlighting of tags in Vim","3":"Automated tag file generation and syntax highlighting of tags in Vim","description":"This plug-in automatically creates a global tags file and keeps it up-to-date as you edit files in Vim. The tags are also used to perform dynamic syntax highlighting of user-defined functions and types. For more information about the plug-in please refer to its homepage or the project page on GitHub:\r\n\r\n \u00e2\u0080\u00a2 http:\/\/peterodding.com\/code\/vim\/easytags\/\r\n \u00e2\u0080\u00a2 http:\/\/github.com\/xolox\/vim-easytags\r\n\r\nIf you have questions, bug reports, suggestions, etc. the author can be contacted at peter@peterodding.com. If you like this plug-in please vote for it below!","4":"This plug-in automatically creates a global tags file and keeps it up-to-date as you edit files in Vim. The tags are also used to perform dynamic syntax highlighting of user-defined functions and types. For more information about the plug-in please refer to its homepage or the project page on GitHub:\r\n\r\n \u00e2\u0080\u00a2 http:\/\/peterodding.com\/code\/vim\/easytags\/\r\n \u00e2\u0080\u00a2 http:\/\/github.com\/xolox\/vim-easytags\r\n\r\nIf you have questions, bug reports, suggestions, etc. the author can be contacted at peter@peterodding.com. If you like this plug-in please vote for it below!","install_details":"Please note that the vim-easytags plug-in requires my vim-misc plug-in which is separately distributed (see vimscript #4597).\r\n\r\nUnzip the most recent ZIP archives of the vim-easytags and vim-misc plug-ins inside your Vim profile directory (usually this is ~\/.vim on UNIX and %USERPROFILE%\\vimfiles on Windows), restart Vim and execute the command :helptags ~\/.vim\/doc (use :helptags ~\\vimfiles\\doc instead on Windows).\r\n\r\nIf you prefer you can also use Pathogen, Vundle or a similar tool to install & update the vim-easytags and vim-misc plug-ins using a local clone of the git repository.\r\n\r\nNow try it out: Edit any file type supported by Exuberant Ctags and within ten seconds the plug-in should create\/update your tags file (\"~\/.vimtags\" on UNIX, \"~\/_vimtags\" on Windows) with the tags defined in the file you just edited! This means that whatever file you're editing in Vim (as long as its on the local file system), tags will always be available by the time you need them!\r\n\r\nAdditionally if the file you just opened is a C, C++, Objective-C, Java, Lua, Python, PHP, Ruby or Vim source file you should also notice that the function and type names defined in the file have been syntax highlighted.\r\n\r\nIf the plug-in warns you that ctags isn't installed you can download it from its homepage http:\/\/ctags.sourceforge.net\/ or if you're running Debian\/Ubuntu you can install it by executing the following shell command:\r\n\r\n    sudo apt-get install exuberant-ctags\r\n\r\nNote that on Windows a command prompt window pops up whenever Exuberant Ctags is run as an external process. If this bothers you then you can install my shell.vim plug-in (see vimscript #3123) which includes a DLL that works around this issue. Once you\u00e2\u0080\u0099ve installed both plug-ins it should work out of the box!","5":"Please note that the vim-easytags plug-in requires my vim-misc plug-in which is separately distributed (see vimscript #4597).\r\n\r\nUnzip the most recent ZIP archives of the vim-easytags and vim-misc plug-ins inside your Vim profile directory (usually this is ~\/.vim on UNIX and %USERPROFILE%\\vimfiles on Windows), restart Vim and execute the command :helptags ~\/.vim\/doc (use :helptags ~\\vimfiles\\doc instead on Windows).\r\n\r\nIf you prefer you can also use Pathogen, Vundle or a similar tool to install & update the vim-easytags and vim-misc plug-ins using a local clone of the git repository.\r\n\r\nNow try it out: Edit any file type supported by Exuberant Ctags and within ten seconds the plug-in should create\/update your tags file (\"~\/.vimtags\" on UNIX, \"~\/_vimtags\" on Windows) with the tags defined in the file you just edited! This means that whatever file you're editing in Vim (as long as its on the local file system), tags will always be available by the time you need them!\r\n\r\nAdditionally if the file you just opened is a C, C++, Objective-C, Java, Lua, Python, PHP, Ruby or Vim source file you should also notice that the function and type names defined in the file have been syntax highlighted.\r\n\r\nIf the plug-in warns you that ctags isn't installed you can download it from its homepage http:\/\/ctags.sourceforge.net\/ or if you're running Debian\/Ubuntu you can install it by executing the following shell command:\r\n\r\n    sudo apt-get install exuberant-ctags\r\n\r\nNote that on Windows a command prompt window pops up whenever Exuberant Ctags is run as an external process. If this bothers you then you can install my shell.vim plug-in (see vimscript #3123) which includes a DLL that works around this issue. Once you\u00e2\u0080\u0099ve installed both plug-ins it should work out of the box!","first_name":"Peter","6":"Peter","last_name":"Odding","7":"Odding","releases":[{"0":"3114","vim_version":"7.0","1":"7.0","script_version":"3.11","2":"3.11","version_comment":" \u00e2\u0080\u00a2 Try to support `Universal Ctags' (issue 123 on GitHub):\n   http:\/\/github.com\/xolox\/vim-easytags\/commit\/72a8753","3":" \u00e2\u0080\u00a2 Try to support `Universal Ctags' (issue 123 on GitHub):\n   http:\/\/github.com\/xolox\/vim-easytags\/commit\/72a8753","package":"easytags.zip","4":"easytags.zip","src_id":"23434","5":"23434","creation_date":"1435786640","6":"1435786640"},{"0":"3114","vim_version":"7.0","1":"7.0","script_version":"3.10.1","2":"3.10.1","version_comment":" \u00e2\u0080\u00a2 Update installation instructions:\n   http:\/\/github.com\/xolox\/vim-easytags\/commit\/584edae\n\n \u00e2\u0080\u00a2 Refer from easytags_always_enabled to easytags_async in README:\n   http:\/\/github.com\/xolox\/vim-easytags\/commit\/188b40b\n\n \u00e2\u0080\u00a2 Improve easytags_auto_{update,highlight} option documentation:\n   http:\/\/github.com\/xolox\/vim-easytags\/commit\/b05ac67\n\n \u00e2\u0080\u00a2 Merge pull request #117 (Fix typo in README):\n   http:\/\/github.com\/xolox\/vim-easytags\/commit\/da53e3b\n\n \u00e2\u0080\u00a2 Improve documentation of `easytags_dynamic_files' option:\n   http:\/\/github.com\/xolox\/vim-easytags\/commit\/a339a8c","3":" \u00e2\u0080\u00a2 Update installation instructions:\n   http:\/\/github.com\/xolox\/vim-easytags\/commit\/584edae\n\n \u00e2\u0080\u00a2 Refer from easytags_always_enabled to easytags_async in README:\n   http:\/\/github.com\/xolox\/vim-easytags\/commit\/188b40b\n\n \u00e2\u0080\u00a2 Improve easytags_auto_{update,highlight} option documentation:\n   http:\/\/github.com\/xolox\/vim-easytags\/commit\/b05ac67\n\n \u00e2\u0080\u00a2 Merge pull request #117 (Fix typo in README):\n   http:\/\/github.com\/xolox\/vim-easytags\/commit\/da53e3b\n\n \u00e2\u0080\u00a2 Improve documentation of `easytags_dynamic_files' option:\n   http:\/\/github.com\/xolox\/vim-easytags\/commit\/a339a8c","package":"easytags.zip","4":"easytags.zip","src_id":"23172","5":"23172","creation_date":"1429042767","6":"1429042767"},{"0":"3114","vim_version":"7.0","1":"7.0","script_version":"3.10","2":"3.10","version_comment":" \u00e2\u0080\u00a2 give precedence to dynamic files over storage by filetype:\n   http:\/\/github.com\/xolox\/vim-easytags\/commit\/a60b1cf\n\n \u00e2\u0080\u00a2 Merge pull request #111: Give precedence to dynamic files over storage by filetype:\n   http:\/\/github.com\/xolox\/vim-easytags\/commit\/67d82cf","3":" \u00e2\u0080\u00a2 give precedence to dynamic files over storage by filetype:\n   http:\/\/github.com\/xolox\/vim-easytags\/commit\/a60b1cf\n\n \u00e2\u0080\u00a2 Merge pull request #111: Give precedence to dynamic files over storage by filetype:\n   http:\/\/github.com\/xolox\/vim-easytags\/commit\/67d82cf","package":"easytags.zip","4":"easytags.zip","src_id":"23034","5":"23034","creation_date":"1426420001","6":"1426420001"},{"0":"3114","vim_version":"7.0","1":"7.0","script_version":"3.9.1","2":"3.9.1","version_comment":" \u00e2\u0080\u00a2 Improve handling & docs of g:easytags_opts option (issue #98):\n   http:\/\/github.com\/xolox\/vim-easytags\/commit\/8925dc6","3":" \u00e2\u0080\u00a2 Improve handling & docs of g:easytags_opts option (issue #98):\n   http:\/\/github.com\/xolox\/vim-easytags\/commit\/8925dc6","package":"easytags.zip","4":"easytags.zip","src_id":"22638","5":"22638","creation_date":"1416605929","6":"1416605929"},{"0":"3114","vim_version":"7.0","1":"7.0","script_version":"3.9","2":"3.9","version_comment":" \u00e2\u0080\u00a2 Add g:easytags_opts option (issue #98 on GitHub):\n   http:\/\/github.com\/xolox\/vim-easytags\/commit\/075ffe9","3":" \u00e2\u0080\u00a2 Add g:easytags_opts option (issue #98 on GitHub):\n   http:\/\/github.com\/xolox\/vim-easytags\/commit\/075ffe9","package":"easytags.zip","4":"easytags.zip","src_id":"22613","5":"22613","creation_date":"1415915606","6":"1415915606"},{"0":"3114","vim_version":"7.0","1":"7.0","script_version":"3.8.3","2":"3.8.3","version_comment":" \u00e2\u0080\u00a2 Improve Perl function tag highlighting (more accurate now):\n   http:\/\/github.com\/xolox\/vim-easytags\/commit\/706c665","3":" \u00e2\u0080\u00a2 Improve Perl function tag highlighting (more accurate now):\n   http:\/\/github.com\/xolox\/vim-easytags\/commit\/706c665","package":"easytags.zip","4":"easytags.zip","src_id":"22599","5":"22599","creation_date":"1415048726","6":"1415048726"},{"0":"3114","vim_version":"7.0","1":"7.0","script_version":"3.8.2","2":"3.8.2","version_comment":" \u00e2\u0080\u00a2 Bug fix for xolox#easytags#define_tagkind() invocations:\n   http:\/\/github.com\/xolox\/vim-easytags\/commit\/29ce869\n\n \u00e2\u0080\u00a2 Bug fix for xolox#easytags#filetypes#find_ctags_aliases():\n   http:\/\/github.com\/xolox\/vim-easytags\/commit\/10427de","3":" \u00e2\u0080\u00a2 Bug fix for xolox#easytags#define_tagkind() invocations:\n   http:\/\/github.com\/xolox\/vim-easytags\/commit\/29ce869\n\n \u00e2\u0080\u00a2 Bug fix for xolox#easytags#filetypes#find_ctags_aliases():\n   http:\/\/github.com\/xolox\/vim-easytags\/commit\/10427de","package":"easytags.zip","4":"easytags.zip","src_id":"22555","5":"22555","creation_date":"1413916730","6":"1413916730"},{"0":"3114","vim_version":"7.0","1":"7.0","script_version":"3.8","2":"3.8","version_comment":" \u00e2\u0080\u00a2 Change file type canonicalization to treat C as C++:\n   http:\/\/github.com\/xolox\/vim-easytags\/commit\/9b6e7d1","3":" \u00e2\u0080\u00a2 Change file type canonicalization to treat C as C++:\n   http:\/\/github.com\/xolox\/vim-easytags\/commit\/9b6e7d1","package":"easytags.zip","4":"easytags.zip","src_id":"22549","5":"22549","creation_date":"1413834511","6":"1413834511"},{"0":"3114","vim_version":"7.0","1":"7.0","script_version":"3.7","2":"3.7","version_comment":" \u00e2\u0080\u00a2 Support for Perl highlighting (thanks to Jessica Kathleen McIntosh):\n   http:\/\/github.com\/xolox\/vim-easytags\/commit\/d251fdb","3":" \u00e2\u0080\u00a2 Support for Perl highlighting (thanks to Jessica Kathleen McIntosh):\n   http:\/\/github.com\/xolox\/vim-easytags\/commit\/d251fdb","package":"easytags.zip","4":"easytags.zip","src_id":"22435","5":"22435","creation_date":"1410985933","6":"1410985933"},{"0":"3114","vim_version":"7.0","1":"7.0","script_version":"3.6.7","2":"3.6.7","version_comment":" \u00e2\u0080\u00a2 Add g:easytags_suppress_report option:\n   http:\/\/github.com\/xolox\/vim-easytags\/commit\/2d6a2ba\n\n \u00e2\u0080\u00a2 Merge pull request #95: Add g:easytags_suppress_report option:\n   http:\/\/github.com\/xolox\/vim-easytags\/commit\/b4d5dd6","3":" \u00e2\u0080\u00a2 Add g:easytags_suppress_report option:\n   http:\/\/github.com\/xolox\/vim-easytags\/commit\/2d6a2ba\n\n \u00e2\u0080\u00a2 Merge pull request #95: Add g:easytags_suppress_report option:\n   http:\/\/github.com\/xolox\/vim-easytags\/commit\/b4d5dd6","package":"easytags.zip","4":"easytags.zip","src_id":"22421","5":"22421","creation_date":"1410685785","6":"1410685785"},{"0":"3114","vim_version":"7.0","1":"7.0","script_version":"3.6.6","2":"3.6.6","version_comment":" \u00e2\u0080\u00a2 Make it easier to debug tag file selection:\n   http:\/\/github.com\/xolox\/vim-easytags\/commit\/bfe2fed\n\n \u00e2\u0080\u00a2 Bug fix for issue #90 caused by pull request #84 (async refactor):\n   http:\/\/github.com\/xolox\/vim-easytags\/commit\/364cfcc","3":" \u00e2\u0080\u00a2 Make it easier to debug tag file selection:\n   http:\/\/github.com\/xolox\/vim-easytags\/commit\/bfe2fed\n\n \u00e2\u0080\u00a2 Bug fix for issue #90 caused by pull request #84 (async refactor):\n   http:\/\/github.com\/xolox\/vim-easytags\/commit\/364cfcc","package":"easytags.zip","4":"easytags.zip","src_id":"22308","5":"22308","creation_date":"1407532843","6":"1407532843"},{"0":"3114","vim_version":"7.0","1":"7.0","script_version":"3.6.4","2":"3.6.4","version_comment":" \u00e2\u0080\u00a2 Merge pull request #84: Asynchronous tags file updates! \\o\/\n   http:\/\/github.com\/xolox\/vim-easytags\/commit\/1a09c98\n\n \u00e2\u0080\u00a2 Support for keyword based syntax highlighting (much faster):\n   http:\/\/github.com\/xolox\/vim-easytags\/commit\/b6f8757\n\n \u00e2\u0080\u00a2 Deduplicate syntax keyword arguments:\n   http:\/\/github.com\/xolox\/vim-easytags\/commit\/0a64a81\n\n \u00e2\u0080\u00a2 Filter out forbidden syntax keyword arguments:\n   http:\/\/github.com\/xolox\/vim-easytags\/commit\/2ff14b3\n\n \u00e2\u0080\u00a2 Bug fix: Restore default syntax pattern prefix\/suffix (word boundaries):\n   http:\/\/github.com\/xolox\/vim-easytags\/commit\/a18d9f7\n\n \u00e2\u0080\u00a2 Use timers to identify slow[est] parts of vim-easytags:\n   http:\/\/github.com\/xolox\/vim-easytags\/commit\/83e8cf3","3":" \u00e2\u0080\u00a2 Merge pull request #84: Asynchronous tags file updates! \\o\/\n   http:\/\/github.com\/xolox\/vim-easytags\/commit\/1a09c98\n\n \u00e2\u0080\u00a2 Support for keyword based syntax highlighting (much faster):\n   http:\/\/github.com\/xolox\/vim-easytags\/commit\/b6f8757\n\n \u00e2\u0080\u00a2 Deduplicate syntax keyword arguments:\n   http:\/\/github.com\/xolox\/vim-easytags\/commit\/0a64a81\n\n \u00e2\u0080\u00a2 Filter out forbidden syntax keyword arguments:\n   http:\/\/github.com\/xolox\/vim-easytags\/commit\/2ff14b3\n\n \u00e2\u0080\u00a2 Bug fix: Restore default syntax pattern prefix\/suffix (word boundaries):\n   http:\/\/github.com\/xolox\/vim-easytags\/commit\/a18d9f7\n\n \u00e2\u0080\u00a2 Use timers to identify slow[est] parts of vim-easytags:\n   http:\/\/github.com\/xolox\/vim-easytags\/commit\/83e8cf3","package":"easytags.zip","4":"easytags.zip","src_id":"22216","5":"22216","creation_date":"1405770616","6":"1405770616"},{"0":"3114","vim_version":"7.0","1":"7.0","script_version":"3.4.4","2":"3.4.4","version_comment":" \u00e2\u0080\u00a2 Replace \\0 by \\g<0> in python sub:\n   http:\/\/github.com\/xolox\/vim-easytags\/commit\/ed29502\n\n \u00e2\u0080\u00a2 Merge pull request #78: Bug fix for accelerated highlighting using Python:\n   http:\/\/github.com\/xolox\/vim-easytags\/commit\/110673a","3":" \u00e2\u0080\u00a2 Replace \\0 by \\g<0> in python sub:\n   http:\/\/github.com\/xolox\/vim-easytags\/commit\/ed29502\n\n \u00e2\u0080\u00a2 Merge pull request #78: Bug fix for accelerated highlighting using Python:\n   http:\/\/github.com\/xolox\/vim-easytags\/commit\/110673a","package":"easytags.zip","4":"easytags.zip","src_id":"22033","5":"22033","creation_date":"1402947577","6":"1402947577"},{"0":"3114","vim_version":"7.0","1":"7.0","script_version":"3.4.3","2":"3.4.3","version_comment":" \u00e2\u0080\u00a2 Bug fix: Support for disabled languages in Exuberant Ctags:\n   http:\/\/github.com\/xolox\/vim-easytags\/commit\/9713f0a","3":" \u00e2\u0080\u00a2 Bug fix: Support for disabled languages in Exuberant Ctags:\n   http:\/\/github.com\/xolox\/vim-easytags\/commit\/9713f0a","package":"easytags.zip","4":"easytags.zip","src_id":"20741","5":"20741","creation_date":"1378029646","6":"1378029646"},{"0":"3114","vim_version":"7.0","1":"7.0","script_version":"3.4.2","2":"3.4.2","version_comment":" \u00e2\u0080\u00a2 Fix 'multiple repeat' error from regex for C++ file types (contributed by Julian Taylor):\n   http:\/\/github.com\/xolox\/vim-easytags\/commit\/e79da3e\n   http:\/\/github.com\/xolox\/vim-easytags\/commit\/330ec57","3":" \u00e2\u0080\u00a2 Fix 'multiple repeat' error from regex for C++ file types (contributed by Julian Taylor):\n   http:\/\/github.com\/xolox\/vim-easytags\/commit\/e79da3e\n   http:\/\/github.com\/xolox\/vim-easytags\/commit\/330ec57","package":"easytags.zip","4":"easytags.zip","src_id":"20739","5":"20739","creation_date":"1377955947","6":"1377955947"},{"0":"3114","vim_version":"7.0","1":"7.0","script_version":"3.4.1","2":"3.4.1","version_comment":" \u00e2\u0080\u00a2 Make sure vim-misc is installed, politely complain if it isn't:\n   http:\/\/github.com\/xolox\/vim-easytags\/commit\/eae3e06","3":" \u00e2\u0080\u00a2 Make sure vim-misc is installed, politely complain if it isn't:\n   http:\/\/github.com\/xolox\/vim-easytags\/commit\/eae3e06","package":"easytags.zip","4":"easytags.zip","src_id":"20680","5":"20680","creation_date":"1376930621","6":"1376930621"},{"0":"3114","vim_version":"7.0","1":"7.0","script_version":"3.4","2":"3.4","version_comment":" \u00e2\u0080\u00a2 Add highlighting for Java interfaces (contributed by Nir Atias):\n   http:\/\/github.com\/xolox\/vim-easytags\/commit\/57c43f3\n   http:\/\/github.com\/xolox\/vim-easytags\/commit\/fddbe78","3":" \u00e2\u0080\u00a2 Add highlighting for Java interfaces (contributed by Nir Atias):\n   http:\/\/github.com\/xolox\/vim-easytags\/commit\/57c43f3\n   http:\/\/github.com\/xolox\/vim-easytags\/commit\/fddbe78","package":"easytags.zip","4":"easytags.zip","src_id":"20533","5":"20533","creation_date":"1374000691","6":"1374000691"},{"0":"3114","vim_version":"7.0","1":"7.0","script_version":"3.3.12","2":"3.3.12","version_comment":" \u00e2\u0080\u00a2 Make Exuberant Ctags discovery (version checking) verbose (easier to debug):\n   http:\/\/github.com\/xolox\/vim-easytags\/commit\/aae2df9","3":" \u00e2\u0080\u00a2 Make Exuberant Ctags discovery (version checking) verbose (easier to debug):\n   http:\/\/github.com\/xolox\/vim-easytags\/commit\/aae2df9","package":"easytags.zip","4":"easytags.zip","src_id":"20395","5":"20395","creation_date":"1371867973","6":"1371867973"},{"0":"3114","vim_version":"7.0","1":"7.0","script_version":"3.3.11","2":"3.3.11","version_comment":" \u00e2\u0080\u00a2 Bug fix for :UpdateTags: Gracefully handle case where no supported file type is known:\n   http:\/\/github.com\/xolox\/vim-easytags\/commit\/8c59ddd","3":" \u00e2\u0080\u00a2 Bug fix for :UpdateTags: Gracefully handle case where no supported file type is known:\n   http:\/\/github.com\/xolox\/vim-easytags\/commit\/8c59ddd","package":"easytags.zip","4":"easytags.zip","src_id":"20392","5":"20392","creation_date":"1371861896","6":"1371861896"},{"0":"3114","vim_version":"7.0","1":"7.0","script_version":"3.3.10","2":"3.3.10","version_comment":" \u00e2\u0080\u00a2 Improve plug-in initialization (make it more robust):\n   http:\/\/github.com\/xolox\/vim-easytags\/commit\/fe6ba73","3":" \u00e2\u0080\u00a2 Improve plug-in initialization (make it more robust):\n   http:\/\/github.com\/xolox\/vim-easytags\/commit\/fe6ba73","package":"easytags.zip","4":"easytags.zip","src_id":"20390","5":"20390","creation_date":"1371860047","6":"1371860047"},{"0":"3114","vim_version":"7.0","1":"7.0","script_version":"3.3.9","2":"3.3.9","version_comment":" \u00e2\u0080\u00a2 Improve handling of ignored syntax groups (issue #57 on GitHub):\n   http:\/\/github.com\/xolox\/vim-easytags\/commit\/5cf3313","3":" \u00e2\u0080\u00a2 Improve handling of ignored syntax groups (issue #57 on GitHub):\n   http:\/\/github.com\/xolox\/vim-easytags\/commit\/5cf3313","package":"easytags.zip","4":"easytags.zip","src_id":"20376","5":"20376","creation_date":"1371680707","6":"1371680707"},{"0":"3114","vim_version":"7.0","1":"7.0","script_version":"3.3.8","2":"3.3.8","version_comment":" \u00e2\u0080\u00a2 Bug fix: Don't highlight C tags inside #if 0 and Doxygen comments (issue #57 on GitHub):\n   http:\/\/github.com\/xolox\/vim-easytags\/commit\/28e2b55","3":" \u00e2\u0080\u00a2 Bug fix: Don't highlight C tags inside #if 0 and Doxygen comments (issue #57 on GitHub):\n   http:\/\/github.com\/xolox\/vim-easytags\/commit\/28e2b55","package":"easytags.zip","4":"easytags.zip","src_id":"20373","5":"20373","creation_date":"1371663461","6":"1371663461"},{"0":"3114","vim_version":"7.0","1":"7.0","script_version":"3.3.7","2":"3.3.7","version_comment":" \u00e2\u0080\u00a2 Bug fix: Don't highlight C tags inside #if 0 (issue #57 on GitHub):\n   http:\/\/github.com\/xolox\/vim-easytags\/commit\/3050c9b","3":" \u00e2\u0080\u00a2 Bug fix: Don't highlight C tags inside #if 0 (issue #57 on GitHub):\n   http:\/\/github.com\/xolox\/vim-easytags\/commit\/3050c9b","package":"easytags.zip","4":"easytags.zip","src_id":"20366","5":"20366","creation_date":"1371505871","6":"1371505871"},{"0":"3114","vim_version":"7.0","1":"7.0","script_version":"3.3.6","2":"3.3.6","version_comment":" \u00e2\u0080\u00a2 Document vim-misc as external dependency (needs to be installed separately from now on):\n   http:\/\/github.com\/xolox\/vim-easytags\/commit\/7916b46","3":" \u00e2\u0080\u00a2 Document vim-misc as external dependency (needs to be installed separately from now on):\n   http:\/\/github.com\/xolox\/vim-easytags\/commit\/7916b46","package":"easytags.zip","4":"easytags.zip","src_id":"20212","5":"20212","creation_date":"1369507446","6":"1369507446"},{"0":"3114","vim_version":"7.0","1":"7.0","script_version":"3.3.4","2":"3.3.4","version_comment":" \u00e2\u0080\u00a2 Document the g:easytags_events option (issue #46):\n   http:\/\/github.com\/xolox\/vim-easytags\/commit\/4a30d88\n\n \u00e2\u0080\u00a2 Updated miscellaneous scripts:\n   http:\/\/github.com\/xolox\/vim-easytags\/commit\/283741f","3":" \u00e2\u0080\u00a2 Document the g:easytags_events option (issue #46):\n   http:\/\/github.com\/xolox\/vim-easytags\/commit\/4a30d88\n\n \u00e2\u0080\u00a2 Updated miscellaneous scripts:\n   http:\/\/github.com\/xolox\/vim-easytags\/commit\/283741f","package":"easytags.zip","4":"easytags.zip","src_id":"20177","5":"20177","creation_date":"1369054062","6":"1369054062"},{"0":"3114","vim_version":"7.0","1":"7.0","script_version":"3.3.3","2":"3.3.3","version_comment":" \u00e2\u0080\u00a2 Document BufWritePost example, improve documentation structure (suggested by Ory Band):\n   http:\/\/github.com\/xolox\/vim-easytags\/commit\/cad39a9\n\n \u00e2\u0080\u00a2 Updated miscellaneous scripts:\n   http:\/\/github.com\/xolox\/vim-easytags\/commit\/e83117d","3":" \u00e2\u0080\u00a2 Document BufWritePost example, improve documentation structure (suggested by Ory Band):\n   http:\/\/github.com\/xolox\/vim-easytags\/commit\/cad39a9\n\n \u00e2\u0080\u00a2 Updated miscellaneous scripts:\n   http:\/\/github.com\/xolox\/vim-easytags\/commit\/e83117d","package":"easytags.zip","4":"easytags.zip","src_id":"20165","5":"20165","creation_date":"1369002842","6":"1369002842"},{"0":"3114","vim_version":"7.0","1":"7.0","script_version":"3.3.2","2":"3.3.2","version_comment":" \u00e2\u0080\u00a2 Add g:easytags_updatetime_warn option, improve documentation (reported by Ory Band):\n   http:\/\/github.com\/xolox\/vim-easytags\/commit\/384ebf4","3":" \u00e2\u0080\u00a2 Add g:easytags_updatetime_warn option, improve documentation (reported by Ory Band):\n   http:\/\/github.com\/xolox\/vim-easytags\/commit\/384ebf4","package":"easytags.zip","4":"easytags.zip","src_id":"20160","5":"20160","creation_date":"1368964452","6":"1368964452"},{"0":"3114","vim_version":"7.0","1":"7.0","script_version":"3.3.1","2":"3.3.1","version_comment":" \u00e2\u0080\u00a2 Bug fix: Don't complain about 'updatetime' when autoload is disabled (reported by Ory Band):\n   http:\/\/github.com\/xolox\/vim-easytags\/commit\/bff179d","3":" \u00e2\u0080\u00a2 Bug fix: Don't complain about 'updatetime' when autoload is disabled (reported by Ory Band):\n   http:\/\/github.com\/xolox\/vim-easytags\/commit\/bff179d","package":"easytags.zip","4":"easytags.zip","src_id":"20159","5":"20159","creation_date":"1368962056","6":"1368962056"},{"0":"3114","vim_version":"7.0","1":"7.0","script_version":"3.3","2":"3.3","version_comment":" \u00e2\u0080\u00a2 Updated miscellaneous scripts:\n   http:\/\/github.com\/xolox\/vim-easytags\/commit\/7c61b34\n   http:\/\/github.com\/xolox\/vim-easytags\/commit\/9c88b0e","3":" \u00e2\u0080\u00a2 Updated miscellaneous scripts:\n   http:\/\/github.com\/xolox\/vim-easytags\/commit\/7c61b34\n   http:\/\/github.com\/xolox\/vim-easytags\/commit\/9c88b0e","package":"easytags.zip","4":"easytags.zip","src_id":"20119","5":"20119","creation_date":"1368480933","6":"1368480933"},{"0":"3114","vim_version":"7.0","1":"7.0","script_version":"3.2","2":"3.2","version_comment":" \u00e2\u0080\u00a2 Support for composed file types:\n   http:\/\/github.com\/xolox\/vim-easytags\/commit\/9e8261a","3":" \u00e2\u0080\u00a2 Support for composed file types:\n   http:\/\/github.com\/xolox\/vim-easytags\/commit\/9e8261a","package":"easytags.zip","4":"easytags.zip","src_id":"20025","5":"20025","creation_date":"1367783288","6":"1367783288"},{"0":"3114","vim_version":"7.0","1":"7.0","script_version":"3.1.8","2":"3.1.8","version_comment":" \u00e2\u0080\u00a2 Don't try to use dynamic tags files for non-writable directories:\n   http:\/\/github.com\/xolox\/vim-easytags\/commit\/1aae392","3":" \u00e2\u0080\u00a2 Don't try to use dynamic tags files for non-writable directories:\n   http:\/\/github.com\/xolox\/vim-easytags\/commit\/1aae392","package":"easytags.zip","4":"easytags.zip","src_id":"19986","5":"19986","creation_date":"1367358077","6":"1367358077"},{"0":"3114","vim_version":"7.0","1":"7.0","script_version":"3.1.6","2":"3.1.6","version_comment":" \u00e2\u0080\u00a2 Updated miscellaneous scripts:\n   http:\/\/github.com\/xolox\/vim-easytags\/commit\/67a0a83","3":" \u00e2\u0080\u00a2 Updated miscellaneous scripts:\n   http:\/\/github.com\/xolox\/vim-easytags\/commit\/67a0a83","package":"easytags.zip","4":"easytags.zip","src_id":"19956","5":"19956","creation_date":"1367159011","6":"1367159011"},{"0":"3114","vim_version":"7.0","1":"7.0","script_version":"3.1.5","2":"3.1.5","version_comment":" \u00e2\u0080\u00a2 Bug fix: Prevent cache corruption by moving before tags write (contributed by Ingo Karkat):\n   http:\/\/github.com\/xolox\/vim-easytags\/commit\/10afe7f","3":" \u00e2\u0080\u00a2 Bug fix: Prevent cache corruption by moving before tags write (contributed by Ingo Karkat):\n   http:\/\/github.com\/xolox\/vim-easytags\/commit\/10afe7f","package":"easytags.zip","4":"easytags.zip","src_id":"19890","5":"19890","creation_date":"1366577769","6":"1366577769"},{"0":"3114","vim_version":"7.0","1":"7.0","script_version":"3.1.4","2":"3.1.4","version_comment":" \u00e2\u0080\u00a2 Bug fix for E688: More targets than List items:\n   http:\/\/github.com\/xolox\/vim-easytags\/commit\/514947b","3":" \u00e2\u0080\u00a2 Bug fix for E688: More targets than List items:\n   http:\/\/github.com\/xolox\/vim-easytags\/commit\/514947b","package":"easytags.zip","4":"easytags.zip","src_id":"19889","5":"19889","creation_date":"1366576826","6":"1366576826"},{"0":"3114","vim_version":"7.0","1":"7.0","script_version":"3.1.3","2":"3.1.3","version_comment":" \u00e2\u0080\u00a2 Do not highlight tags on :UpdateTags when it is configured off (contributed by Ingo Karkat):\n   http:\/\/github.com\/xolox\/vim-easytags\/commit\/61b7bca","3":" \u00e2\u0080\u00a2 Do not highlight tags on :UpdateTags when it is configured off (contributed by Ingo Karkat):\n   http:\/\/github.com\/xolox\/vim-easytags\/commit\/61b7bca","package":"easytags.zip","4":"easytags.zip","src_id":"19883","5":"19883","creation_date":"1366539212","6":"1366539212"},{"0":"3114","vim_version":"7.0","1":"7.0","script_version":"3.1.2","2":"3.1.2","version_comment":" \u00e2\u0080\u00a2 Make compatibility with miscellaneous scripts explicit:\n   http:\/\/github.com\/xolox\/vim-easytags\/commit\/577885f","3":" \u00e2\u0080\u00a2 Make compatibility with miscellaneous scripts explicit:\n   http:\/\/github.com\/xolox\/vim-easytags\/commit\/577885f","package":"easytags.zip","4":"easytags.zip","src_id":"19868","5":"19868","creation_date":"1366479865","6":"1366479865"},{"0":"3114","vim_version":"7.0","1":"7.0","script_version":"3.1.1","2":"3.1.1","version_comment":" \u00e2\u0080\u00a2 Add `ctags-exuberant' to the list of program names (closes issue #39):\n   http:\/\/github.com\/xolox\/vim-easytags\/commit\/d713d07","3":" \u00e2\u0080\u00a2 Add `ctags-exuberant' to the list of program names (closes issue #39):\n   http:\/\/github.com\/xolox\/vim-easytags\/commit\/d713d07","package":"easytags.zip","4":"easytags.zip","src_id":"19860","5":"19860","creation_date":"1366334150","6":"1366334150"},{"0":"3114","vim_version":"7.0","1":"7.0","script_version":"3.1","2":"3.1","version_comment":" \u00e2\u0080\u00a2 Workaround low 'updatetime' intelligently:\n   http:\/\/github.com\/xolox\/vim-easytags\/commit\/43ae6d7","3":" \u00e2\u0080\u00a2 Workaround low 'updatetime' intelligently:\n   http:\/\/github.com\/xolox\/vim-easytags\/commit\/43ae6d7","package":"easytags.zip","4":"easytags.zip","src_id":"19859","5":"19859","creation_date":"1366333185","6":"1366333185"},{"0":"3114","vim_version":"7.0","1":"7.0","script_version":"3.0","2":"3.0","version_comment":" \u00e2\u0080\u00a2 Allow to specify different ctags tool for particular languages (contributed by Ingo Karkat):\n   http:\/\/github.com\/xolox\/vim-easytags\/commit\/8a0a363\n   http:\/\/github.com\/xolox\/vim-easytags\/commit\/ebe2ba9","3":" \u00e2\u0080\u00a2 Allow to specify different ctags tool for particular languages (contributed by Ingo Karkat):\n   http:\/\/github.com\/xolox\/vim-easytags\/commit\/8a0a363\n   http:\/\/github.com\/xolox\/vim-easytags\/commit\/ebe2ba9","package":"easytags.zip","4":"easytags.zip","src_id":"19858","5":"19858","creation_date":"1366327610","6":"1366327610"},{"0":"3114","vim_version":"7.0","1":"7.0","script_version":"2.9","2":"2.9","version_comment":" \u00e2\u0080\u00a2 Avoid tag updating when ctags output has identical fingerprint (contributed by Ingo Karkat):\n   http:\/\/github.com\/xolox\/vim-easytags\/commit\/d789e8e\n   http:\/\/github.com\/xolox\/vim-easytags\/commit\/92d1f2d\n   http:\/\/github.com\/xolox\/vim-easytags\/commit\/07437cf","3":" \u00e2\u0080\u00a2 Avoid tag updating when ctags output has identical fingerprint (contributed by Ingo Karkat):\n   http:\/\/github.com\/xolox\/vim-easytags\/commit\/d789e8e\n   http:\/\/github.com\/xolox\/vim-easytags\/commit\/92d1f2d\n   http:\/\/github.com\/xolox\/vim-easytags\/commit\/07437cf","package":"easytags.zip","4":"easytags.zip","src_id":"19857","5":"19857","creation_date":"1366326351","6":"1366326351"},{"0":"3114","vim_version":"7.0","1":"7.0","script_version":"2.8.2","2":"2.8.2","version_comment":" \u00e2\u0080\u00a2 Bug fix for highlighting of function names in shell scripts:\n   http:\/\/github.com\/xolox\/vim-easytags\/commit\/df42d18","3":" \u00e2\u0080\u00a2 Bug fix for highlighting of function names in shell scripts:\n   http:\/\/github.com\/xolox\/vim-easytags\/commit\/df42d18","package":"easytags.zip","4":"easytags.zip","src_id":"19840","5":"19840","creation_date":"1366238147","6":"1366238147"},{"0":"3114","vim_version":"7.0","1":"7.0","script_version":"2.8.1","2":"2.8.1","version_comment":" \u00e2\u0080\u00a2 Bug fix: Sort tags files properly by folding to uppercase (issue #25):\n   http:\/\/github.com\/xolox\/vim-easytags\/commit\/4675193\n\n \u00e2\u0080\u00a2 Bug fix for deduplication of syntax highlighting patterns:\n   http:\/\/github.com\/xolox\/vim-easytags\/commit\/44b0487","3":" \u00e2\u0080\u00a2 Bug fix: Sort tags files properly by folding to uppercase (issue #25):\n   http:\/\/github.com\/xolox\/vim-easytags\/commit\/4675193\n\n \u00e2\u0080\u00a2 Bug fix for deduplication of syntax highlighting patterns:\n   http:\/\/github.com\/xolox\/vim-easytags\/commit\/44b0487","package":"easytags.zip","4":"easytags.zip","src_id":"17210","5":"17210","creation_date":"1326589568","6":"1326589568"},{"0":"3114","vim_version":"7.0","1":"7.0","script_version":"2.7.6","2":"2.7.6","version_comment":" \u00e2\u0080\u00a2 Fix a slight inefficiency in xolox#easytags#highlight():\n   http:\/\/github.com\/xolox\/vim-easytags\/commit\/31d1e15","3":" \u00e2\u0080\u00a2 Fix a slight inefficiency in xolox#easytags#highlight():\n   http:\/\/github.com\/xolox\/vim-easytags\/commit\/31d1e15","package":"easytags.zip","4":"easytags.zip","src_id":"17157","5":"17157","creation_date":"1325805794","6":"1325805794"},{"0":"3114","vim_version":"7.0","1":"7.0","script_version":"2.7.5","2":"2.7.5","version_comment":" \u00e2\u0080\u00a2 Updated miscellaneous scripts:\n   http:\/\/github.com\/xolox\/vim-easytags\/commit\/9b4c774\n   http:\/\/github.com\/xolox\/vim-easytags\/commit\/52881ed\n   http:\/\/github.com\/xolox\/vim-easytags\/commit\/0f57d4f","3":" \u00e2\u0080\u00a2 Updated miscellaneous scripts:\n   http:\/\/github.com\/xolox\/vim-easytags\/commit\/9b4c774\n   http:\/\/github.com\/xolox\/vim-easytags\/commit\/52881ed\n   http:\/\/github.com\/xolox\/vim-easytags\/commit\/0f57d4f","package":"easytags.zip","4":"easytags.zip","src_id":"16968","5":"16968","creation_date":"1322267902","6":"1322267902"},{"0":"3114","vim_version":"7.0","1":"7.0","script_version":"2.7.4","2":"2.7.4","version_comment":" \u00e2\u0080\u00a2 Bug fix for file type specific tags file support:\n   http:\/\/github.com\/xolox\/vim-easytags\/commit\/9762c28","3":" \u00e2\u0080\u00a2 Bug fix for file type specific tags file support:\n   http:\/\/github.com\/xolox\/vim-easytags\/commit\/9762c28","package":"easytags.zip","4":"easytags.zip","src_id":"16967","5":"16967","creation_date":"1322265430","6":"1322265430"},{"0":"3114","vim_version":"7.0","1":"7.0","script_version":"2.7.3","2":"2.7.3","version_comment":" \u00e2\u0080\u00a2 Work around &shellslash setting on Windows:\n   http:\/\/github.com\/xolox\/vim-easytags\/commit\/0da0b0d","3":" \u00e2\u0080\u00a2 Work around &shellslash setting on Windows:\n   http:\/\/github.com\/xolox\/vim-easytags\/commit\/0da0b0d","package":"easytags.zip","4":"easytags.zip","src_id":"16923","5":"16923","creation_date":"1321910045","6":"1321910045"},{"0":"3114","vim_version":"7.0","1":"7.0","script_version":"2.7.2","2":"2.7.2","version_comment":" \u00e2\u0080\u00a2 Make list of ignored syntax groups configurable:\n   http:\/\/github.com\/xolox\/vim-easytags\/commit\/e3290ab\n\n \u00e2\u0080\u00a2 Make shell script highlighting compatible with syntax folding (issue #20):\n   http:\/\/github.com\/xolox\/vim-easytags\/commit\/4b4cd4d","3":" \u00e2\u0080\u00a2 Make list of ignored syntax groups configurable:\n   http:\/\/github.com\/xolox\/vim-easytags\/commit\/e3290ab\n\n \u00e2\u0080\u00a2 Make shell script highlighting compatible with syntax folding (issue #20):\n   http:\/\/github.com\/xolox\/vim-easytags\/commit\/4b4cd4d","package":"easytags.zip","4":"easytags.zip","src_id":"16768","5":"16768","creation_date":"1319902689","6":"1319902689"},{"0":"3114","vim_version":"7.0","1":"7.0","script_version":"2.7","2":"2.7","version_comment":"Added support for AWK, Shell and Tcl highlighting (contributed by Lorance Stinson):\n \u00e2\u0080\u00a2 http:\/\/github.com\/xolox\/vim-easytags\/commit\/bf32f32\n \u00e2\u0080\u00a2 http:\/\/github.com\/xolox\/vim-easytags\/commit\/3d7e091","3":"Added support for AWK, Shell and Tcl highlighting (contributed by Lorance Stinson):\n \u00e2\u0080\u00a2 http:\/\/github.com\/xolox\/vim-easytags\/commit\/bf32f32\n \u00e2\u0080\u00a2 http:\/\/github.com\/xolox\/vim-easytags\/commit\/3d7e091","package":"easytags.zip","4":"easytags.zip","src_id":"16610","5":"16610","creation_date":"1317500474","6":"1317500474"},{"0":"3114","vim_version":"7.0","1":"7.0","script_version":"2.6.1","2":"2.6.1","version_comment":" \u00e2\u0080\u00a2 Bug fix for error handling in cache_tagged_files():\n   http:\/\/github.com\/xolox\/vim-easytags\/commit\/a380feb","3":" \u00e2\u0080\u00a2 Bug fix for error handling in cache_tagged_files():\n   http:\/\/github.com\/xolox\/vim-easytags\/commit\/a380feb","package":"easytags.zip","4":"easytags.zip","src_id":"16595","5":"16595","creation_date":"1317142453","6":"1317142453"},{"0":"3114","vim_version":"7.0","1":"7.0","script_version":"2.6","2":"2.6","version_comment":" \u00e2\u0080\u00a2 Search the whole $PATH for Exuberant Ctags (issue #18):\n   http:\/\/github.com\/xolox\/vim-easytags\/commit\/fe3f565\n\n \u00e2\u0080\u00a2 Updated miscellaneous scripts:\n   http:\/\/github.com\/xolox\/vim-easytags\/commit\/0a9a07e","3":" \u00e2\u0080\u00a2 Search the whole $PATH for Exuberant Ctags (issue #18):\n   http:\/\/github.com\/xolox\/vim-easytags\/commit\/fe3f565\n\n \u00e2\u0080\u00a2 Updated miscellaneous scripts:\n   http:\/\/github.com\/xolox\/vim-easytags\/commit\/0a9a07e","package":"easytags.zip","4":"easytags.zip","src_id":"16586","5":"16586","creation_date":"1316996425","6":"1316996425"},{"0":"3114","vim_version":"7.0","1":"7.0","script_version":"2.5.8","2":"2.5.8","version_comment":" \u00e2\u0080\u00a2 New g:easytags_updatetime_autodisable option (issue #17, reported by Strahinja Markovic):\n   http:\/\/github.com\/xolox\/vim-easytags\/commit\/100bd8d","3":" \u00e2\u0080\u00a2 New g:easytags_updatetime_autodisable option (issue #17, reported by Strahinja Markovic):\n   http:\/\/github.com\/xolox\/vim-easytags\/commit\/100bd8d","package":"easytags.zip","4":"easytags.zip","src_id":"16538","5":"16538","creation_date":"1316274511","6":"1316274511"},{"0":"3114","vim_version":"7.0","1":"7.0","script_version":"2.5.7","2":"2.5.7","version_comment":" \u00e2\u0080\u00a2 Bug fix: Correct typo in s:canonicalize():\n   http:\/\/github.com\/xolox\/vim-easytags\/commit\/1fd6ef5\n\n \u00e2\u0080\u00a2 Make scope of canonical filename cache explicit:\n   http:\/\/github.com\/xolox\/vim-easytags\/commit\/ef7c6f8\n\n \u00e2\u0080\u00a2 Improve easytags_dynamic_files implementation (best of both worlds?):\n   http:\/\/github.com\/xolox\/vim-easytags\/commit\/fae8ddd","3":" \u00e2\u0080\u00a2 Bug fix: Correct typo in s:canonicalize():\n   http:\/\/github.com\/xolox\/vim-easytags\/commit\/1fd6ef5\n\n \u00e2\u0080\u00a2 Make scope of canonical filename cache explicit:\n   http:\/\/github.com\/xolox\/vim-easytags\/commit\/ef7c6f8\n\n \u00e2\u0080\u00a2 Improve easytags_dynamic_files implementation (best of both worlds?):\n   http:\/\/github.com\/xolox\/vim-easytags\/commit\/fae8ddd","package":"easytags.zip","4":"easytags.zip","src_id":"16470","5":"16470","creation_date":"1315247724","6":"1315247724"},{"0":"3114","vim_version":"7.0","1":"7.0","script_version":"2.5.4","2":"2.5.4","version_comment":" \u00e2\u0080\u00a2 Updated miscellaneous scripts:\n   http:\/\/github.com\/xolox\/vim-easytags\/commit\/bd39218","3":" \u00e2\u0080\u00a2 Updated miscellaneous scripts:\n   http:\/\/github.com\/xolox\/vim-easytags\/commit\/bd39218","package":"easytags.zip","4":"easytags.zip","src_id":"16455","5":"16455","creation_date":"1315144791","6":"1315144791"},{"0":"3114","vim_version":"7.0","1":"7.0","script_version":"2.5.3","2":"2.5.3","version_comment":" \u00e2\u0080\u00a2 normalize-tags.py: Enable normalizing several files at once:\n   http:\/\/github.com\/xolox\/vim-easytags\/commit\/8a186f4\n\n \u00e2\u0080\u00a2 Bug fix for \"E713: Cannot use empty key for Dictionary\" (issue #16 on GitHub, reported by Zhao Cai: http:\/\/github.com\/xolox\/vim-easytags\/issues\/16):\n   http:\/\/github.com\/xolox\/vim-easytags\/commit\/f38bcf6\n\n \u00e2\u0080\u00a2 Warn about unreasonable 'updatetime' values (issue #16, see above):\n   http:\/\/github.com\/xolox\/vim-easytags\/commit\/0b47a3c\n\n \u00e2\u0080\u00a2 Write tags files to temporary files, then rename() into place (issue #16, see above):\n   http:\/\/github.com\/xolox\/vim-easytags\/commit\/f526e2b","3":" \u00e2\u0080\u00a2 normalize-tags.py: Enable normalizing several files at once:\n   http:\/\/github.com\/xolox\/vim-easytags\/commit\/8a186f4\n\n \u00e2\u0080\u00a2 Bug fix for \"E713: Cannot use empty key for Dictionary\" (issue #16 on GitHub, reported by Zhao Cai: http:\/\/github.com\/xolox\/vim-easytags\/issues\/16):\n   http:\/\/github.com\/xolox\/vim-easytags\/commit\/f38bcf6\n\n \u00e2\u0080\u00a2 Warn about unreasonable 'updatetime' values (issue #16, see above):\n   http:\/\/github.com\/xolox\/vim-easytags\/commit\/0b47a3c\n\n \u00e2\u0080\u00a2 Write tags files to temporary files, then rename() into place (issue #16, see above):\n   http:\/\/github.com\/xolox\/vim-easytags\/commit\/f526e2b","package":"easytags.zip","4":"easytags.zip","src_id":"16451","5":"16451","creation_date":"1315137515","6":"1315137515"},{"0":"3114","vim_version":"7.0","1":"7.0","script_version":"2.5","2":"2.5","version_comment":" \u00e2\u0080\u00a2 Make \"easytags_dynamic_files\" create missing tags files (suggested by Strahinja Markovic):\n   http:\/\/github.com\/xolox\/vim-easytags\/commit\/d2a2cb5","3":" \u00e2\u0080\u00a2 Make \"easytags_dynamic_files\" create missing tags files (suggested by Strahinja Markovic):\n   http:\/\/github.com\/xolox\/vim-easytags\/commit\/d2a2cb5","package":"easytags.zip","4":"easytags.zip","src_id":"16418","5":"16418","creation_date":"1314826650","6":"1314826650"},{"0":"3114","vim_version":"7.0","1":"7.0","script_version":"2.4.12","2":"2.4.12","version_comment":" \u00e2\u0080\u00a2 Explain how to setup custom ctags command line options:\n   http:\/\/github.com\/xolox\/vim-easytags\/commit\/46d87b3\n\n \u00e2\u0080\u00a2 Move version variable to autoload script:\n   http:\/\/github.com\/xolox\/vim-easytags\/commit\/4e1131e","3":" \u00e2\u0080\u00a2 Explain how to setup custom ctags command line options:\n   http:\/\/github.com\/xolox\/vim-easytags\/commit\/46d87b3\n\n \u00e2\u0080\u00a2 Move version variable to autoload script:\n   http:\/\/github.com\/xolox\/vim-easytags\/commit\/4e1131e","package":"easytags.zip","4":"easytags.zip","src_id":"16376","5":"16376","creation_date":"1314497308","6":"1314497308"},{"0":"3114","vim_version":"7.0","1":"7.0","script_version":"2.4.11","2":"2.4.11","version_comment":" \u00e2\u0080\u00a2 Never try to autoload plug-in for unsupported file types:\n   http:\/\/github.com\/xolox\/vim-easytags\/commit\/ee0966c\n\n \u00e2\u0080\u00a2 Skip unreadable tags files returned by tagfiles() (reported by Hannes von Haugwitz):\n   http:\/\/github.com\/xolox\/vim-easytags\/commit\/ba99f5f\n\n \u00e2\u0080\u00a2 Explain how to setup custom ctags command line options:\n   http:\/\/github.com\/xolox\/vim-easytags\/commit\/46d87b3","3":" \u00e2\u0080\u00a2 Never try to autoload plug-in for unsupported file types:\n   http:\/\/github.com\/xolox\/vim-easytags\/commit\/ee0966c\n\n \u00e2\u0080\u00a2 Skip unreadable tags files returned by tagfiles() (reported by Hannes von Haugwitz):\n   http:\/\/github.com\/xolox\/vim-easytags\/commit\/ba99f5f\n\n \u00e2\u0080\u00a2 Explain how to setup custom ctags command line options:\n   http:\/\/github.com\/xolox\/vim-easytags\/commit\/46d87b3","package":"easytags.zip","4":"easytags.zip","src_id":"16057","5":"16057","creation_date":"1310166927","6":"1310166927"},{"0":"3114","vim_version":"7.0","1":"7.0","script_version":"2.4.9","2":"2.4.9","version_comment":" \u00e2\u0080\u00a2 Fix broken link in README:\n   http:\/\/github.com\/xolox\/vim-easytags\/commit\/5207365","3":" \u00e2\u0080\u00a2 Fix broken link in README:\n   http:\/\/github.com\/xolox\/vim-easytags\/commit\/5207365","package":"easytags.zip","4":"easytags.zip","src_id":"15991","5":"15991","creation_date":"1309139679","6":"1309139679"},{"0":"3114","vim_version":"7.0","1":"7.0","script_version":"2.4.8","2":"2.4.8","version_comment":" \u00e2\u0080\u00a2 Bug fix and improvement for xolox#misc#option#get():\n   http:\/\/github.com\/xolox\/vim-easytags\/commit\/0b1c06e\n\n \u00e2\u0080\u00a2 Support for buffer local variants of most options (see http:\/\/peterodding.com\/code\/vim\/easytags#options):\n   http:\/\/github.com\/xolox\/vim-easytags\/commit\/2e05e0e","3":" \u00e2\u0080\u00a2 Bug fix and improvement for xolox#misc#option#get():\n   http:\/\/github.com\/xolox\/vim-easytags\/commit\/0b1c06e\n\n \u00e2\u0080\u00a2 Support for buffer local variants of most options (see http:\/\/peterodding.com\/code\/vim\/easytags#options):\n   http:\/\/github.com\/xolox\/vim-easytags\/commit\/2e05e0e","package":"easytags.zip","4":"easytags.zip","src_id":"15990","5":"15990","creation_date":"1309139231","6":"1309139231"},{"0":"3114","vim_version":"7.0","1":"7.0","script_version":"2.4.7","2":"2.4.7","version_comment":" \u00e2\u0080\u00a2 Add easytags_auto_update\/auto_highlight options (makes it possible to disable automatic updating and\/or highlighting for all or specific buffers):\n   http:\/\/github.com\/xolox\/vim-easytags\/commit\/67616b2","3":" \u00e2\u0080\u00a2 Add easytags_auto_update\/auto_highlight options (makes it possible to disable automatic updating and\/or highlighting for all or specific buffers):\n   http:\/\/github.com\/xolox\/vim-easytags\/commit\/67616b2","package":"easytags.zip","4":"easytags.zip","src_id":"15988","5":"15988","creation_date":"1309121006","6":"1309121006"},{"0":"3114","vim_version":"7.0","1":"7.0","script_version":"2.4.6","2":"2.4.6","version_comment":" \u00e2\u0080\u00a2 Finish support for file type specific tags files (+bug fix):\n   http:\/\/github.com\/xolox\/vim-easytags\/commit\/e8db2a2","3":" \u00e2\u0080\u00a2 Finish support for file type specific tags files (+bug fix):\n   http:\/\/github.com\/xolox\/vim-easytags\/commit\/e8db2a2","package":"easytags.zip","4":"easytags.zip","src_id":"15966","5":"15966","creation_date":"1308880858","6":"1308880858"},{"0":"3114","vim_version":"7.0","1":"7.0","script_version":"2.4.5","2":"2.4.5","version_comment":" \u00e2\u0080\u00a2 Allow enabling both dynamic and file type specific tags files (thanks to Kenny Stuart):\n   http:\/\/github.com\/xolox\/vim-easytags\/commit\/d727ac0\n\n \u00e2\u0080\u00a2 Tolerate corrupt tags files and ctags output:\n   http:\/\/github.com\/xolox\/vim-easytags\/commit\/b5e0b6b","3":" \u00e2\u0080\u00a2 Allow enabling both dynamic and file type specific tags files (thanks to Kenny Stuart):\n   http:\/\/github.com\/xolox\/vim-easytags\/commit\/d727ac0\n\n \u00e2\u0080\u00a2 Tolerate corrupt tags files and ctags output:\n   http:\/\/github.com\/xolox\/vim-easytags\/commit\/b5e0b6b","package":"easytags.zip","4":"easytags.zip","src_id":"15965","5":"15965","creation_date":"1308877627","6":"1308877627"},{"0":"3114","vim_version":"7.0","1":"7.0","script_version":"2.4.3","2":"2.4.3","version_comment":" \u00e2\u0080\u00a2 Define version as variable, include version in messages:\n   http:\/\/github.com\/xolox\/vim-easytags\/commit\/e454233","3":" \u00e2\u0080\u00a2 Define version as variable, include version in messages:\n   http:\/\/github.com\/xolox\/vim-easytags\/commit\/e454233","package":"easytags.zip","4":"easytags.zip","src_id":"15925","5":"15925","creation_date":"1308363387","6":"1308363387"},{"0":"3114","vim_version":"7.0","1":"7.0","script_version":"2.4.2","2":"2.4.2","version_comment":" \u00e2\u0080\u00a2 Remove duplicate tag from Vim help file:\n   http:\/\/github.com\/xolox\/vim-easytags\/commit\/27b9aa3","3":" \u00e2\u0080\u00a2 Remove duplicate tag from Vim help file:\n   http:\/\/github.com\/xolox\/vim-easytags\/commit\/27b9aa3","package":"easytags.zip","4":"easytags.zip","src_id":"15914","5":"15914","creation_date":"1308318933","6":"1308318933"},{"0":"3114","vim_version":"7.0","1":"7.0","script_version":"2.4.1","2":"2.4.1","version_comment":" \u00e2\u0080\u00a2 Documentation bug fix (it's getting late..):\n   http:\/\/github.com\/xolox\/vim-easytags\/commit\/08186f0","3":" \u00e2\u0080\u00a2 Documentation bug fix (it's getting late..):\n   http:\/\/github.com\/xolox\/vim-easytags\/commit\/08186f0","package":"easytags.zip","4":"easytags.zip","src_id":"15881","5":"15881","creation_date":"1308027249","6":"1308027249"},{"0":"3114","vim_version":"7.0","1":"7.0","script_version":"2.4","2":"2.4","version_comment":" \u00e2\u0080\u00a2 2x faster syntax highlighting using Python Interface to Vim :-)\n   http:\/\/github.com\/xolox\/vim-easytags\/commit\/9abe348","3":" \u00e2\u0080\u00a2 2x faster syntax highlighting using Python Interface to Vim :-)\n   http:\/\/github.com\/xolox\/vim-easytags\/commit\/9abe348","package":"easytags.zip","4":"easytags.zip","src_id":"15880","5":"15880","creation_date":"1308026818","6":"1308026818"},{"0":"3114","vim_version":"7.0","1":"7.0","script_version":"2.3.2","2":"2.3.2","version_comment":" \u00e2\u0080\u00a2 Fix caching of tagged files (for file type specific tags files):\n   http:\/\/github.com\/xolox\/vim-easytags\/commit\/ca9a4d8","3":" \u00e2\u0080\u00a2 Fix caching of tagged files (for file type specific tags files):\n   http:\/\/github.com\/xolox\/vim-easytags\/commit\/ca9a4d8","package":"easytags.zip","4":"easytags.zip","src_id":"15876","5":"15876","creation_date":"1308004684","6":"1308004684"},{"0":"3114","vim_version":"7.0","1":"7.0","script_version":"2.3.1","2":"2.3.1","version_comment":" \u00e2\u0080\u00a2 Minor bug fix for xolox#easytags#get_tagsfile():\n   http:\/\/github.com\/xolox\/vim-easytags\/commit\/dc167e4\n\n \u00e2\u0080\u00a2 Bug fix: Print the right message after :verbose UpdateTags!\n   http:\/\/github.com\/xolox\/vim-easytags\/commit\/2094759\n\n \u00e2\u0080\u00a2 Basic support for file type specific tags files:\n   http:\/\/github.com\/xolox\/vim-easytags\/commit\/4df41ad\n\n \u00e2\u0080\u00a2 :TagsByFileType command to create file type specific tags files from a global tags file:\n   http:\/\/github.com\/xolox\/vim-easytags\/commit\/1194a6b","3":" \u00e2\u0080\u00a2 Minor bug fix for xolox#easytags#get_tagsfile():\n   http:\/\/github.com\/xolox\/vim-easytags\/commit\/dc167e4\n\n \u00e2\u0080\u00a2 Bug fix: Print the right message after :verbose UpdateTags!\n   http:\/\/github.com\/xolox\/vim-easytags\/commit\/2094759\n\n \u00e2\u0080\u00a2 Basic support for file type specific tags files:\n   http:\/\/github.com\/xolox\/vim-easytags\/commit\/4df41ad\n\n \u00e2\u0080\u00a2 :TagsByFileType command to create file type specific tags files from a global tags file:\n   http:\/\/github.com\/xolox\/vim-easytags\/commit\/1194a6b","package":"easytags.zip","4":"easytags.zip","src_id":"15872","5":"15872","creation_date":"1307982242","6":"1307982242"},{"0":"3114","vim_version":"7.0","1":"7.0","script_version":"2.2.12","2":"2.2.12","version_comment":" \u00e2\u0080\u00a2 Automatically run :HighlightTags after using :UpdateTags:\n   http:\/\/github.com\/xolox\/vim-easytags\/commit\/6c959d2\n\n \u00e2\u0080\u00a2 Refactor automatic command registration, include more events:\n   http:\/\/github.com\/xolox\/vim-easytags\/commit\/1de4f3d","3":" \u00e2\u0080\u00a2 Automatically run :HighlightTags after using :UpdateTags:\n   http:\/\/github.com\/xolox\/vim-easytags\/commit\/6c959d2\n\n \u00e2\u0080\u00a2 Refactor automatic command registration, include more events:\n   http:\/\/github.com\/xolox\/vim-easytags\/commit\/1de4f3d","package":"easytags.zip","4":"easytags.zip","src_id":"15863","5":"15863","creation_date":"1307921773","6":"1307921773"},{"0":"3114","vim_version":"7.0","1":"7.0","script_version":"2.2.9","2":"2.2.9","version_comment":" \u00e2\u0080\u00a2 Added caveat about Cygwin, updated to-do list:\r\n   https:\/\/github.com\/xolox\/vim-easytags\/commit\/ea6efd6\r\n\r\n \u00e2\u0080\u00a2 Document the highlighting groups used by the plug-in:\r\n   https:\/\/github.com\/xolox\/vim-easytags\/commit\/2a2cba0\r\n\r\n \u00e2\u0080\u00a2 Add g:easytags_suppress_ctags_warning option:\r\n   https:\/\/github.com\/xolox\/vim-easytags\/commit\/6e279a3\r\n\r\n \u00e2\u0080\u00a2 Accept 'Development' as valid version:\r\n   https:\/\/github.com\/xolox\/vim-easytags\/commit\/0a49b11\r\n\r\n \u00e2\u0080\u00a2 Add documentation in vimdoc format:\r\n   https:\/\/github.com\/xolox\/vim-easytags\/commit\/6de3e06\r\n\r\n \u00e2\u0080\u00a2 Enable deferring tags file registration (VimEnter):\r\n   https:\/\/github.com\/xolox\/vim-easytags\/commit\/3466f61\r\n   https:\/\/github.com\/xolox\/vim-easytags\/commit\/c1635d6\r\n\r\n \u00e2\u0080\u00a2 Don't use feedkeys() hack for Vim >= 7.3:\r\n   https:\/\/github.com\/xolox\/vim-easytags\/commit\/1ee5eff\r\n\r\n \u00e2\u0080\u00a2 Enable updating of project specific tags files:\r\n   https:\/\/github.com\/xolox\/vim-easytags\/commit\/670910e\r\n\r\n \u00e2\u0080\u00a2 Check that the xolox#misc submodule is available:\r\n   https:\/\/github.com\/xolox\/vim-easytags\/commit\/6ddd431\r\n\r\n \u00e2\u0080\u00a2 Added Python script to manually cleanup tags files:\r\n   https:\/\/github.com\/xolox\/vim-easytags\/commit\/18ad44c\r\n\r\n \u00e2\u0080\u00a2 Added Python script to analyze tags file size:\r\n   https:\/\/github.com\/xolox\/vim-easytags\/commit\/f980d5d\r\n\r\n \u00e2\u0080\u00a2 Dynamic highlighting for Ruby source code (issue #9):\r\n   https:\/\/github.com\/xolox\/vim-easytags\/commit\/45e97ff\r\n\r\n \u00e2\u0080\u00a2 Bug fix for highlighting of C# classes:\r\n   https:\/\/github.com\/xolox\/vim-easytags\/commit\/6cf2a35","3":" \u00e2\u0080\u00a2 Added caveat about Cygwin, updated to-do list:\r\n   https:\/\/github.com\/xolox\/vim-easytags\/commit\/ea6efd6\r\n\r\n \u00e2\u0080\u00a2 Document the highlighting groups used by the plug-in:\r\n   https:\/\/github.com\/xolox\/vim-easytags\/commit\/2a2cba0\r\n\r\n \u00e2\u0080\u00a2 Add g:easytags_suppress_ctags_warning option:\r\n   https:\/\/github.com\/xolox\/vim-easytags\/commit\/6e279a3\r\n\r\n \u00e2\u0080\u00a2 Accept 'Development' as valid version:\r\n   https:\/\/github.com\/xolox\/vim-easytags\/commit\/0a49b11\r\n\r\n \u00e2\u0080\u00a2 Add documentation in vimdoc format:\r\n   https:\/\/github.com\/xolox\/vim-easytags\/commit\/6de3e06\r\n\r\n \u00e2\u0080\u00a2 Enable deferring tags file registration (VimEnter):\r\n   https:\/\/github.com\/xolox\/vim-easytags\/commit\/3466f61\r\n   https:\/\/github.com\/xolox\/vim-easytags\/commit\/c1635d6\r\n\r\n \u00e2\u0080\u00a2 Don't use feedkeys() hack for Vim >= 7.3:\r\n   https:\/\/github.com\/xolox\/vim-easytags\/commit\/1ee5eff\r\n\r\n \u00e2\u0080\u00a2 Enable updating of project specific tags files:\r\n   https:\/\/github.com\/xolox\/vim-easytags\/commit\/670910e\r\n\r\n \u00e2\u0080\u00a2 Check that the xolox#misc submodule is available:\r\n   https:\/\/github.com\/xolox\/vim-easytags\/commit\/6ddd431\r\n\r\n \u00e2\u0080\u00a2 Added Python script to manually cleanup tags files:\r\n   https:\/\/github.com\/xolox\/vim-easytags\/commit\/18ad44c\r\n\r\n \u00e2\u0080\u00a2 Added Python script to analyze tags file size:\r\n   https:\/\/github.com\/xolox\/vim-easytags\/commit\/f980d5d\r\n\r\n \u00e2\u0080\u00a2 Dynamic highlighting for Ruby source code (issue #9):\r\n   https:\/\/github.com\/xolox\/vim-easytags\/commit\/45e97ff\r\n\r\n \u00e2\u0080\u00a2 Bug fix for highlighting of C# classes:\r\n   https:\/\/github.com\/xolox\/vim-easytags\/commit\/6cf2a35","package":"easytags.zip","4":"easytags.zip","src_id":"15700","5":"15700","creation_date":"1306177191","6":"1306177191"},{"0":"3114","vim_version":"7.0","1":"7.0","script_version":"2.2","2":"2.2","version_comment":" \u00e2\u0080\u00a2 Bug fix for alias handling:\r\n   https:\/\/github.com\/xolox\/vim-easytags\/commit\/3b4db424731f952050b9\r\n\r\n \u00e2\u0080\u00a2 Don't highlight PHP functions not followed by `(':\r\n   https:\/\/github.com\/xolox\/vim-easytags\/commit\/d8a8c5ef9d2d9c48767b\r\n\r\n \u00e2\u0080\u00a2 Highlight C# classes, structs and methods (thanks to feedback from Aleksey Baibarin):\r\n   https:\/\/github.com\/xolox\/vim-easytags\/commit\/98780b1904c066a510ba\r\n\r\n \u00e2\u0080\u00a2 Added caveat about Cygwin (thanks to feedback from Alex Zuroff!), updated to-do list:\r\n   https:\/\/github.com\/xolox\/vim-easytags\/commit\/d8a8c5ef9d2d9c48767b","3":" \u00e2\u0080\u00a2 Bug fix for alias handling:\r\n   https:\/\/github.com\/xolox\/vim-easytags\/commit\/3b4db424731f952050b9\r\n\r\n \u00e2\u0080\u00a2 Don't highlight PHP functions not followed by `(':\r\n   https:\/\/github.com\/xolox\/vim-easytags\/commit\/d8a8c5ef9d2d9c48767b\r\n\r\n \u00e2\u0080\u00a2 Highlight C# classes, structs and methods (thanks to feedback from Aleksey Baibarin):\r\n   https:\/\/github.com\/xolox\/vim-easytags\/commit\/98780b1904c066a510ba\r\n\r\n \u00e2\u0080\u00a2 Added caveat about Cygwin (thanks to feedback from Alex Zuroff!), updated to-do list:\r\n   https:\/\/github.com\/xolox\/vim-easytags\/commit\/d8a8c5ef9d2d9c48767b","package":"easytags.zip","4":"easytags.zip","src_id":"15110","5":"15110","creation_date":"1298576078","6":"1298576078"},{"0":"3114","vim_version":"7.0","1":"7.0","script_version":"2.1.9","2":"2.1.9","version_comment":" \u00e2\u0080\u00a2 Don't highlight tags inside #include <...>:\r\n   https:\/\/github.com\/xolox\/vim-easytags\/commit\/ae3eb31b705401d21f9f\r\n\r\n \u00e2\u0080\u00a2 Highlighting for Python class names:\r\n   https:\/\/github.com\/xolox\/vim-easytags\/commit\/d3551a3fa2315874ae52","3":" \u00e2\u0080\u00a2 Don't highlight tags inside #include <...>:\r\n   https:\/\/github.com\/xolox\/vim-easytags\/commit\/ae3eb31b705401d21f9f\r\n\r\n \u00e2\u0080\u00a2 Highlighting for Python class names:\r\n   https:\/\/github.com\/xolox\/vim-easytags\/commit\/d3551a3fa2315874ae52","package":"easytags.zip","4":"easytags.zip","src_id":"14437","5":"14437","creation_date":"1291502990","6":"1291502990"},{"0":"3114","vim_version":"7.0","1":"7.0","script_version":"2.1.7.2","2":"2.1.7.2","version_comment":"Bug fix for duplicate help tag in \u00e2\u0080\u0098easytags.txt\u00e2\u0080\u0099 (no associated commit because \u00e2\u0080\u0098easytags.txt\u00e2\u0080\u0099 is generated from \u00e2\u0080\u0098README.md\u00e2\u0080\u0099 \u00e2\u0080\u0094 I just fixed the conversion script and regenerated \u00e2\u0080\u0098easytags.txt\u00e2\u0080\u0099)","3":"Bug fix for duplicate help tag in \u00e2\u0080\u0098easytags.txt\u00e2\u0080\u0099 (no associated commit because \u00e2\u0080\u0098easytags.txt\u00e2\u0080\u0099 is generated from \u00e2\u0080\u0098README.md\u00e2\u0080\u0099 \u00e2\u0080\u0094 I just fixed the conversion script and regenerated \u00e2\u0080\u0098easytags.txt\u00e2\u0080\u0099)","package":"easytags.zip","4":"easytags.zip","src_id":"13915","5":"13915","creation_date":"1285404918","6":"1285404918"},{"0":"3114","vim_version":"7.0","1":"7.0","script_version":"2.1.7","2":"2.1.7","version_comment":" \u00e2\u0080\u00a2 Documented :HighlightTags tags file format requirements:\r\n   http:\/\/github.com\/xolox\/vim-easytags\/commit\/738d7508181423e1633e4d5d6014e8ad2acb4595\r\n\r\n \u00e2\u0080\u00a2 Remove no longer needed PublishPre automatic command:\r\n   http:\/\/github.com\/xolox\/vim-easytags\/commit\/3735a5c31b94cb575d6821e697d867fe475d73cf\r\n\r\n \u00e2\u0080\u00a2 Fixed easytags#update() to overcome argument limit:\r\n   http:\/\/github.com\/xolox\/vim-easytags\/commit\/0d0fac667e38114324d1a90f848f49a5af71f859\r\n\r\n \u00e2\u0080\u00a2 Bug fix: Canonicalize arguments to :UpdateTags:\r\n   http:\/\/github.com\/xolox\/vim-easytags\/commit\/5efb2c7ee0d6926aaa0ad3080a53857ec910d4d3","3":" \u00e2\u0080\u00a2 Documented :HighlightTags tags file format requirements:\r\n   http:\/\/github.com\/xolox\/vim-easytags\/commit\/738d7508181423e1633e4d5d6014e8ad2acb4595\r\n\r\n \u00e2\u0080\u00a2 Remove no longer needed PublishPre automatic command:\r\n   http:\/\/github.com\/xolox\/vim-easytags\/commit\/3735a5c31b94cb575d6821e697d867fe475d73cf\r\n\r\n \u00e2\u0080\u00a2 Fixed easytags#update() to overcome argument limit:\r\n   http:\/\/github.com\/xolox\/vim-easytags\/commit\/0d0fac667e38114324d1a90f848f49a5af71f859\r\n\r\n \u00e2\u0080\u00a2 Bug fix: Canonicalize arguments to :UpdateTags:\r\n   http:\/\/github.com\/xolox\/vim-easytags\/commit\/5efb2c7ee0d6926aaa0ad3080a53857ec910d4d3","package":"easytags.zip","4":"easytags.zip","src_id":"13763","5":"13763","creation_date":"1283728669","6":"1283728669"},{"0":"3114","vim_version":"7.0","1":"7.0","script_version":"2.1.4","2":"2.1.4","version_comment":"Fix automatic ctags detection on FreeBSD (reported by Derek Tattersall):\r\nhttp:\/\/github.com\/xolox\/vim-easytags\/commit\/eea8f41b9e04b8b533d1670a1090b16255f9b5f2","3":"Fix automatic ctags detection on FreeBSD (reported by Derek Tattersall):\r\nhttp:\/\/github.com\/xolox\/vim-easytags\/commit\/eea8f41b9e04b8b533d1670a1090b16255f9b5f2","package":"easytags.zip","4":"easytags.zip","src_id":"13551","5":"13551","creation_date":"1281555162","6":"1281555162"},{"0":"3114","vim_version":"7.0","1":"7.0","script_version":"2.1.3","2":"2.1.3","version_comment":" \u00e2\u0080\u00a2 Support scanning & highlighting of struct\/class members in C\/C++ sources:\r\n   http:\/\/github.com\/xolox\/vim-easytags\/commit\/2f73c57c857fc0a4f3bed718a90f0296890778a3\r\n\r\n \u00e2\u0080\u00a2 Always scan C\/C++ sources for function prototypes:\r\n   http:\/\/github.com\/xolox\/vim-easytags\/commit\/7b041bd0ae8c65e80c84d20727b1eafaf04327bd","3":" \u00e2\u0080\u00a2 Support scanning & highlighting of struct\/class members in C\/C++ sources:\r\n   http:\/\/github.com\/xolox\/vim-easytags\/commit\/2f73c57c857fc0a4f3bed718a90f0296890778a3\r\n\r\n \u00e2\u0080\u00a2 Always scan C\/C++ sources for function prototypes:\r\n   http:\/\/github.com\/xolox\/vim-easytags\/commit\/7b041bd0ae8c65e80c84d20727b1eafaf04327bd","package":"easytags.zip","4":"easytags.zip","src_id":"13547","5":"13547","creation_date":"1281523050","6":"1281523050"},{"0":"3114","vim_version":"7.0","1":"7.0","script_version":"2.1","2":"2.1","version_comment":" \u00e2\u0080\u00a2 Support for automatic recursion using ctags -R:\r\n   http:\/\/github.com\/xolox\/vim-easytags\/commit\/0d9567900f23e8ca243db16df80004aa7c658623\r\n\r\n \u00e2\u0080\u00a2 Bug fix for broken alias support (reported by zhang xinli):\r\n   http:\/\/github.com\/xolox\/vim-easytags\/commit\/80847259b7c3dd5781384f31914a7d7465ed0069","3":" \u00e2\u0080\u00a2 Support for automatic recursion using ctags -R:\r\n   http:\/\/github.com\/xolox\/vim-easytags\/commit\/0d9567900f23e8ca243db16df80004aa7c658623\r\n\r\n \u00e2\u0080\u00a2 Bug fix for broken alias support (reported by zhang xinli):\r\n   http:\/\/github.com\/xolox\/vim-easytags\/commit\/80847259b7c3dd5781384f31914a7d7465ed0069","package":"easytags.zip","4":"easytags.zip","src_id":"13545","5":"13545","creation_date":"1281462033","6":"1281462033"},{"0":"3114","vim_version":"7.0","1":"7.0","script_version":"2.0","2":"2.0","version_comment":"http:\/\/github.com\/xolox\/vim-easytags\/commit\/89f9205ff840329aa75166249a99b1d0f227d661:\r\n \u00e2\u0080\u00a2 Enable commands like :UpdateTags -R ~\/.vim\/.\r\n \u00e2\u0080\u00a2 Fixed a rare problem where tags sort before the !_TAG_FILE_SORTED header causing E432.\r\n \u00e2\u0080\u00a2 Finally documented the :UpdateTags and :HighlightTags commands.\r\n \u00e2\u0080\u00a2 Dynamic highlighting can now be disabled for individual buffers, which can come in handy when the highlighting conflicts with another plug-in: Just set the 'b:easytags_nohl' variable to any value.\r\n\r\nhttp:\/\/github.com\/xolox\/vim-easytags\/commit\/7e8533fceefb4358444997bf3deda8c1812069c7:\r\n \u00e2\u0080\u00a2 Automatic\/optional integration with shell.vim","3":"http:\/\/github.com\/xolox\/vim-easytags\/commit\/89f9205ff840329aa75166249a99b1d0f227d661:\r\n \u00e2\u0080\u00a2 Enable commands like :UpdateTags -R ~\/.vim\/.\r\n \u00e2\u0080\u00a2 Fixed a rare problem where tags sort before the !_TAG_FILE_SORTED header causing E432.\r\n \u00e2\u0080\u00a2 Finally documented the :UpdateTags and :HighlightTags commands.\r\n \u00e2\u0080\u00a2 Dynamic highlighting can now be disabled for individual buffers, which can come in handy when the highlighting conflicts with another plug-in: Just set the 'b:easytags_nohl' variable to any value.\r\n\r\nhttp:\/\/github.com\/xolox\/vim-easytags\/commit\/7e8533fceefb4358444997bf3deda8c1812069c7:\r\n \u00e2\u0080\u00a2 Automatic\/optional integration with shell.vim","package":"easytags.zip","4":"easytags.zip","src_id":"13531","5":"13531","creation_date":"1281388770","6":"1281388770"},{"0":"3114","vim_version":"7.0","1":"7.0","script_version":"1.9.7","2":"1.9.7","version_comment":" \u00e2\u0080\u00a2 Create case folded tags files when &ignorecase is on:\r\n   http:\/\/github.com\/xolox\/vim-easytags\/commit\/ff64be5fe506a9a15dce28bac5b5585d4430f4a6\r\n\r\n \u00e2\u0080\u00a2 The plug-in now finally registers the global tags file automatically on both Windows and UNIX:\r\n   http:\/\/github.com\/xolox\/vim-easytags\/commit\/3b934f6e0d0d4a44875024713dd0aeefdcdd206b","3":" \u00e2\u0080\u00a2 Create case folded tags files when &ignorecase is on:\r\n   http:\/\/github.com\/xolox\/vim-easytags\/commit\/ff64be5fe506a9a15dce28bac5b5585d4430f4a6\r\n\r\n \u00e2\u0080\u00a2 The plug-in now finally registers the global tags file automatically on both Windows and UNIX:\r\n   http:\/\/github.com\/xolox\/vim-easytags\/commit\/3b934f6e0d0d4a44875024713dd0aeefdcdd206b","package":"easytags.zip","4":"easytags.zip","src_id":"13358","5":"13358","creation_date":"1279624792","6":"1279624792"},{"0":"3114","vim_version":"7.0","1":"7.0","script_version":"1.9.6","2":"1.9.6","version_comment":"* Improved README, added references to Vim documentation\r\n  http:\/\/github.com\/xolox\/vim-easytags\/commit\/726c08bf946ba3cdabab23a63bb8892c19408a04\r\n\r\n* Handle patterns that are too large for Vim to evaluate\r\n  http:\/\/github.com\/xolox\/vim-easytags\/commit\/92cd87df83b24e1c45b946bc9eadbe4482de12ba\r\n\r\n* Bug fix for strange \"E433: No tags file\" problem\r\n  http:\/\/github.com\/xolox\/vim-easytags\/commit\/4fef0c17749e687d670b2e9e4e429022ec4c1055","3":"* Improved README, added references to Vim documentation\r\n  http:\/\/github.com\/xolox\/vim-easytags\/commit\/726c08bf946ba3cdabab23a63bb8892c19408a04\r\n\r\n* Handle patterns that are too large for Vim to evaluate\r\n  http:\/\/github.com\/xolox\/vim-easytags\/commit\/92cd87df83b24e1c45b946bc9eadbe4482de12ba\r\n\r\n* Bug fix for strange \"E433: No tags file\" problem\r\n  http:\/\/github.com\/xolox\/vim-easytags\/commit\/4fef0c17749e687d670b2e9e4e429022ec4c1055","package":"easytags.zip","4":"easytags.zip","src_id":"13316","5":"13316","creation_date":"1278780724","6":"1278780724"},{"0":"3114","vim_version":"7.0","1":"7.0","script_version":"1.9.5","2":"1.9.5","version_comment":"Proper handling of unnamed buffers\r\nhttp:\/\/github.com\/xolox\/vim-easytags\/commit\/24cd42357f25f0cf182c83b3b82a3b60e6e6e9f0","3":"Proper handling of unnamed buffers\r\nhttp:\/\/github.com\/xolox\/vim-easytags\/commit\/24cd42357f25f0cf182c83b3b82a3b60e6e6e9f0","package":"easytags.zip","4":"easytags.zip","src_id":"13198","5":"13198","creation_date":"1276694497","6":"1276694497"},{"0":"3114","vim_version":"7.0","1":"7.0","script_version":"1.9.4","2":"1.9.4","version_comment":"Bug fix for E713: Cannot use empty key for Dictionary\r\nhttp:\/\/github.com\/xolox\/vim-easytags\/commit\/f31333832adf37467ff70218f889f00e77e57027","3":"Bug fix for E713: Cannot use empty key for Dictionary\r\nhttp:\/\/github.com\/xolox\/vim-easytags\/commit\/f31333832adf37467ff70218f889f00e77e57027","package":"easytags.zip","4":"easytags.zip","src_id":"13197","5":"13197","creation_date":"1276692791","6":"1276692791"},{"0":"3114","vim_version":"7.0","1":"7.0","script_version":"1.9.3","2":"1.9.3","version_comment":"Version detection of Exuberant Ctags, better error handling, bug fix for dynamic highlighting\r\nhttp:\/\/github.com\/xolox\/vim-easytags\/commit\/5cb775c9a8e8ea07abbb39f09f72c818c2ad518b","3":"Version detection of Exuberant Ctags, better error handling, bug fix for dynamic highlighting\r\nhttp:\/\/github.com\/xolox\/vim-easytags\/commit\/5cb775c9a8e8ea07abbb39f09f72c818c2ad518b","package":"easytags.zip","4":"easytags.zip","src_id":"13185","5":"13185","creation_date":"1276585325","6":"1276585325"},{"0":"3114","vim_version":"7.0","1":"7.0","script_version":"1.9.2","2":"1.9.2","version_comment":"Bug fix: Accidentally included local changes from project directory in previous release, sorry!","3":"Bug fix: Accidentally included local changes from project directory in previous release, sorry!","package":"easytags.zip","4":"easytags.zip","src_id":"13184","5":"13184","creation_date":"1276548786","6":"1276548786"},{"0":"3114","vim_version":"7.0","1":"7.0","script_version":"1.9.1","2":"1.9.1","version_comment":"Bug fix: Ignore missing tags file when caching tagged files\r\nhttp:\/\/github.com\/xolox\/vim-easytags\/commit\/d064e0639f488b975af12aad01040493e265804c","3":"Bug fix: Ignore missing tags file when caching tagged files\r\nhttp:\/\/github.com\/xolox\/vim-easytags\/commit\/d064e0639f488b975af12aad01040493e265804c","package":"easytags.zip","4":"easytags.zip","src_id":"13178","5":"13178","creation_date":"1276472588","6":"1276472588"},{"0":"3114","vim_version":"7.0","1":"7.0","script_version":"1.9","2":"1.9","version_comment":"Fixed tags file corruption on Windows!\r\nhttp:\/\/github.com\/xolox\/vim-easytags\/commit\/ad3bd15a76acaeb8bd5c92e104ab95a7b55f6fee\r\n\r\n * Fixed tags file corruption on Windows: It turns out that the function readfile() accepts CR+NL line endings and just strips CR characters, however the writefile() function doesn't write CR+NL but just NL. Manually adding the CR characters to the end of each line before writing the tags file solves the corruption bug.\r\n\r\n * The headers and entries in tags files are now properly separated from each other while rewriting the tags file to filter expired entries.\r\n\r\n * Don't bother trying to filter expired tags when the tags file doesn't reference the current filename at all (improves performance a bit).\r\n\r\n * Fixed a buggy easytags#file_has_tags() call in easytags#autoload() that made the plug-in always scan each edited file at least once.\r\n\r\n * Changed folds to provide basic outline of function categories.\r\n\r\n * Restructured definitions for default configuration of dynamic syntax highlighting support so definitions don't all have to be indented.\r\n\r\nSorry about the large diff, this version took a few days of experimentation to build which means lots of little changes.","3":"Fixed tags file corruption on Windows!\r\nhttp:\/\/github.com\/xolox\/vim-easytags\/commit\/ad3bd15a76acaeb8bd5c92e104ab95a7b55f6fee\r\n\r\n * Fixed tags file corruption on Windows: It turns out that the function readfile() accepts CR+NL line endings and just strips CR characters, however the writefile() function doesn't write CR+NL but just NL. Manually adding the CR characters to the end of each line before writing the tags file solves the corruption bug.\r\n\r\n * The headers and entries in tags files are now properly separated from each other while rewriting the tags file to filter expired entries.\r\n\r\n * Don't bother trying to filter expired tags when the tags file doesn't reference the current filename at all (improves performance a bit).\r\n\r\n * Fixed a buggy easytags#file_has_tags() call in easytags#autoload() that made the plug-in always scan each edited file at least once.\r\n\r\n * Changed folds to provide basic outline of function categories.\r\n\r\n * Restructured definitions for default configuration of dynamic syntax highlighting support so definitions don't all have to be indented.\r\n\r\nSorry about the large diff, this version took a few days of experimentation to build which means lots of little changes.","package":"easytags.zip","4":"easytags.zip","src_id":"13172","5":"13172","creation_date":"1276387686","6":"1276387686"},{"0":"3114","vim_version":"7.0","1":"7.0","script_version":"1.8.2","2":"1.8.2","version_comment":" * Moved &tags option parsing to autoload script\r\n  http:\/\/github.com\/xolox\/vim-easytags\/commit\/1c8733ee23d792bf5f7c325f6e5babec14f798f2\r\n\r\n* Bug fix: Expand ~ to $HOME manually on Win32 \r\n  http:\/\/github.com\/xolox\/vim-easytags\/commit\/71cc2ef765f18ab150bf834993c0e90a68797629","3":" * Moved &tags option parsing to autoload script\r\n  http:\/\/github.com\/xolox\/vim-easytags\/commit\/1c8733ee23d792bf5f7c325f6e5babec14f798f2\r\n\r\n* Bug fix: Expand ~ to $HOME manually on Win32 \r\n  http:\/\/github.com\/xolox\/vim-easytags\/commit\/71cc2ef765f18ab150bf834993c0e90a68797629","package":"easytags.zip","4":"easytags.zip","src_id":"13162","5":"13162","creation_date":"1276208388","6":"1276208388"},{"0":"3114","vim_version":"7.0","1":"7.0","script_version":"1.8.1","2":"1.8.1","version_comment":"* Dynamic highlighting for Java identifiers\r\n  http:\/\/github.com\/xolox\/vim-easytags\/commit\/3f762e26ab7b9730ec0757257a9bd924d1f6f05e","3":"* Dynamic highlighting for Java identifiers\r\n  http:\/\/github.com\/xolox\/vim-easytags\/commit\/3f762e26ab7b9730ec0757257a9bd924d1f6f05e","package":"easytags.zip","4":"easytags.zip","src_id":"13161","5":"13161","creation_date":"1276201622","6":"1276201622"},{"0":"3114","vim_version":"7.0","1":"7.0","script_version":"1.8","2":"1.8","version_comment":"The plug-in now more-or-less supports Microsoft Windows, the only remaining problems are the flashing command prompt (which I know how to fix) and the fact that CursorHold seems to fire repeatedly (which I don't, yet).\r\n\r\n* Make sure there's something to highlight before doing so\r\n  http:\/\/github.com\/xolox\/vim-easytags\/commit\/d227685a4110e5f3f11cd1b49118172f528a52d7\r\n\r\n* Scan files not contained in tags file on 1st :edit\r\n  http:\/\/github.com\/xolox\/vim-easytags\/commit\/ac315a019ea96302d3ac7166d7f5febb34ee38ca\r\n\r\n* Bug fix: Make sure tags include \"language\" field\r\n  http:\/\/github.com\/xolox\/vim-easytags\/commit\/d319117aa8392b2605d9bab64d1153827fd29488\r\n\r\n* Bug fix: Add easytags_file to &tags option \r\n  http:\/\/github.com\/xolox\/vim-easytags\/commit\/62cbd2a750a40dd520b6a7f1a92463c92f37baca","3":"The plug-in now more-or-less supports Microsoft Windows, the only remaining problems are the flashing command prompt (which I know how to fix) and the fact that CursorHold seems to fire repeatedly (which I don't, yet).\r\n\r\n* Make sure there's something to highlight before doing so\r\n  http:\/\/github.com\/xolox\/vim-easytags\/commit\/d227685a4110e5f3f11cd1b49118172f528a52d7\r\n\r\n* Scan files not contained in tags file on 1st :edit\r\n  http:\/\/github.com\/xolox\/vim-easytags\/commit\/ac315a019ea96302d3ac7166d7f5febb34ee38ca\r\n\r\n* Bug fix: Make sure tags include \"language\" field\r\n  http:\/\/github.com\/xolox\/vim-easytags\/commit\/d319117aa8392b2605d9bab64d1153827fd29488\r\n\r\n* Bug fix: Add easytags_file to &tags option \r\n  http:\/\/github.com\/xolox\/vim-easytags\/commit\/62cbd2a750a40dd520b6a7f1a92463c92f37baca","package":"easytags.zip","4":"easytags.zip","src_id":"13160","5":"13160","creation_date":"1276200377","6":"1276200377"},{"0":"3114","vim_version":"7.0","1":"7.0","script_version":"1.7","2":"1.7","version_comment":"* Added \"easytags_ignored_filetypes\" option\r\n  http:\/\/github.com\/xolox\/vim-easytags\/commit\/6dd0b7a882d8102f5cff1b2acc927b91cc03e514\r\n\r\n* Updated latest zip link in README\r\n  http:\/\/github.com\/xolox\/vim-easytags\/commit\/cfeac5a045f38799edf3076211eb791e39a5dee6\r\n\r\n* Alias support & defaults for C\/C++\/Obj-C\/Obj-C++\r\n  http:\/\/github.com\/xolox\/vim-easytags\/commit\/61b99f078557d65331e72de60d145e16b8bbb88e","3":"* Added \"easytags_ignored_filetypes\" option\r\n  http:\/\/github.com\/xolox\/vim-easytags\/commit\/6dd0b7a882d8102f5cff1b2acc927b91cc03e514\r\n\r\n* Updated latest zip link in README\r\n  http:\/\/github.com\/xolox\/vim-easytags\/commit\/cfeac5a045f38799edf3076211eb791e39a5dee6\r\n\r\n* Alias support & defaults for C\/C++\/Obj-C\/Obj-C++\r\n  http:\/\/github.com\/xolox\/vim-easytags\/commit\/61b99f078557d65331e72de60d145e16b8bbb88e","package":"easytags.zip","4":"easytags.zip","src_id":"13148","5":"13148","creation_date":"1276065509","6":"1276065509"},{"0":"3114","vim_version":"7.0","1":"7.0","script_version":"1.6.3","2":"1.6.3","version_comment":"* Moved script-local function s:unique() to autoload script:\r\n  http:\/\/github.com\/xolox\/vim-easytags\/commit\/8d13bd28ed9c5bfeef4ac09c2981821e1cf0fdc1\r\n\r\n* Wrapped public facing functions in try\/catch blocks:\r\n  http:\/\/github.com\/xolox\/vim-easytags\/commit\/5bd20f02ebfd7c7bf5a33a2cd31a7d76a54911dd\r\n\r\n* Bug fix for undefined variable in easytags#get_tagsfile()\r\n  http:\/\/github.com\/xolox\/vim-easytags\/commit\/5bd20f02ebfd7c7bf5a33a2cd31a7d76a54911dd#L0L107","3":"* Moved script-local function s:unique() to autoload script:\r\n  http:\/\/github.com\/xolox\/vim-easytags\/commit\/8d13bd28ed9c5bfeef4ac09c2981821e1cf0fdc1\r\n\r\n* Wrapped public facing functions in try\/catch blocks:\r\n  http:\/\/github.com\/xolox\/vim-easytags\/commit\/5bd20f02ebfd7c7bf5a33a2cd31a7d76a54911dd\r\n\r\n* Bug fix for undefined variable in easytags#get_tagsfile()\r\n  http:\/\/github.com\/xolox\/vim-easytags\/commit\/5bd20f02ebfd7c7bf5a33a2cd31a7d76a54911dd#L0L107","package":"easytags.zip","4":"easytags.zip","src_id":"13134","5":"13134","creation_date":"1275824812","6":"1275824812"},{"0":"3114","vim_version":"7.0","1":"7.0","script_version":"1.6.2","2":"1.6.2","version_comment":"Initial upload with fixed references to www.vim.org scripts entry","3":"Initial upload with fixed references to www.vim.org scripts entry","package":"easytags.zip","4":"easytags.zip","src_id":"13130","5":"13130","creation_date":"1275812225","6":"1275812225"}]},"3113":{"script_id":"3113","0":"3113","script_name":"formatvim","1":"formatvim","script_type":"utility","2":"utility","summary":" Convert current file to colored HTML, BBCode or whatever","3":" Convert current file to colored HTML, BBCode or whatever","description":"This plugin provides the ability to convert current file to colored HTML, \r\nBBcode, (in future) LaTeX or whatever you have written specification for.\r\n\r\nFeatures:\r\n    ∙ Flexible format specifications.\r\n    ∙ Ability to create abstract stylesheets.\r\n    ∙ 'list' [1] and 'listchars' [2] options support (only tab, trail, eol and conceal \r\n      for now).\r\n    ∙ Side-by-side diffs support. format-side-by-side-diff [3]\r\n    ∙ Support for creating numbered lines.\r\n    ∙ Dynamic folds support. g:format_AllFolds [4]\r\n\r\nDifferencies with built-in :TOhtml [5]:\r\n    ∙ For large files formatting using my plugin is faster.\r\n    ∙ 'list' [1] and 'listchars' [2] options support.\r\n    ∙ Background color for the whole line with differencies, not just for text \r\n      (for g:html_no_pre [6]=1) and without trailing spaces (for \r\n      g:html_no_pre [6]=0).\r\n    ∙ Signs support. signs [7]\r\n    ∙ Tags linked to their definition. Implemented for 2html in \r\n      vimscript\u00c2\u00a0#2252. g:format_IgnoreTags [8]\r\n    ∙ (HTML) Anchors in tags definition location: for copying links. \r\n      g:format_HTMLAddLinkAtTagLine [9]\r\n    ∙ Side-by-side diff based on tables (2html relies on lines having the same \r\n      height which is generally false).\r\n    ∙ Full conceal support: with g:format_FormatConcealed [10] set to\u00c2\u00a02 \r\n      formats-format-html generates both concealed and shown.\r\n    ∙ Non-copyable signs, fold columns and numbers by default. 2html requires \r\n      setting g:html_prevent_copy [11].\r\n    ∙ 'fillchars' [12] vert suboption support (2html supports only diff and fold \r\n      suboptions).\r\n    ∙ Matches and 'hlsearch' [13] support. g:format_FormatMatches [14]\r\n    ∙ More correct highlighting in some cases.\r\n    ∙ Support for formats other then HTML\/XHTML (format-formats [15]). Makes it \r\n      relatively easy to add new format to the list of supported formats \r\n      (format-f-format.add [16]).\r\n    ∙ 2html still has more options for HTML formatting though.\r\n    ∙ Full 'foldcolumn' [17] support: 2html sets foldcolumn to either 'foldcolumn' [17] \r\n      value or maximum fold level, whichever is greater, formatvim uses \r\n      'foldcolumn' [17] value, fully emulating what vim shows.\r\n    ∙ 'spell' [18] checking support. g:format_IgnoreSpell [19]\r\n\r\n\r\nPlugin requires some additional plugins:\r\n    ∙ frawor (https:\/\/bitbucket.org\/ZyX_I\/frawor)\r\n\r\nNote: formatvim supports VAM (https:\/\/github.com\/MarcWeber\/vim-addon-manager). \r\n      It is prefered that you use it for formatvim installation.\r\n\r\n\r\nProject page: https:\/\/bitbucket.org\/ZyX_I\/formatvim\r\nDocumentation: http:\/\/vimcommunity.bitbucket.org\/doc\/format.txt.html\r\n\r\n\r\n[1] http:\/\/vimcommunity.bitbucket.org\/doc\/options.txt.html#.27list.27\r\n[2] http:\/\/vimcommunity.bitbucket.org\/doc\/options.txt.html#.27listchars.27\r\n[3] http:\/\/vimcommunity.bitbucket.org\/doc\/format.txt.html#format-side-by-side-diff\r\n[4] http:\/\/vimcommunity.bitbucket.org\/doc\/format.txt.html#g.3aformat_AllFolds\r\n[5] http:\/\/vimcommunity.bitbucket.org\/doc\/syntax.txt.html#.3aTOhtml\r\n[6] http:\/\/vimcommunity.bitbucket.org\/doc\/syntax.txt.html#g.3ahtml_no_pre\r\n[7] http:\/\/vimcommunity.bitbucket.org\/doc\/sign.txt.html#signs\r\n[8] http:\/\/vimcommunity.bitbucket.org\/doc\/format.txt.html#g.3aformat_IgnoreTags\r\n[9] http:\/\/vimcommunity.bitbucket.org\/doc\/format.txt.html#g.3aformat_HTMLAddLinkAtTagLine\r\n[10] http:\/\/vimcommunity.bitbucket.org\/doc\/format.txt.html#g.3aformat_FormatConcealed\r\n[11] http:\/\/vimcommunity.bitbucket.org\/doc\/syntax.txt.html#g.3ahtml_prevent_copy\r\n[12] http:\/\/vimcommunity.bitbucket.org\/doc\/options.txt.html#.27fillchars.27\r\n[13] http:\/\/vimcommunity.bitbucket.org\/doc\/options.txt.html#.27hlsearch.27\r\n[14] http:\/\/vimcommunity.bitbucket.org\/doc\/format.txt.html#g.3aformat_FormatMatches\r\n[15] http:\/\/vimcommunity.bitbucket.org\/doc\/format.txt.html#format-formats\r\n[16] http:\/\/vimcommunity.bitbucket.org\/doc\/format.txt.html#format-f-format.2eadd\r\n[17] http:\/\/vimcommunity.bitbucket.org\/doc\/options.txt.html#.27foldcolumn.27\r\n[18] http:\/\/vimcommunity.bitbucket.org\/doc\/options.txt.html#.27spell.27\r\n[19] http:\/\/vimcommunity.bitbucket.org\/doc\/format.txt.html#g.3aformat_IgnoreSpell\r\n\r\n","4":"This plugin provides the ability to convert current file to colored HTML, \r\nBBcode, (in future) LaTeX or whatever you have written specification for.\r\n\r\nFeatures:\r\n    ∙ Flexible format specifications.\r\n    ∙ Ability to create abstract stylesheets.\r\n    ∙ 'list' [1] and 'listchars' [2] options support (only tab, trail, eol and conceal \r\n      for now).\r\n    ∙ Side-by-side diffs support. format-side-by-side-diff [3]\r\n    ∙ Support for creating numbered lines.\r\n    ∙ Dynamic folds support. g:format_AllFolds [4]\r\n\r\nDifferencies with built-in :TOhtml [5]:\r\n    ∙ For large files formatting using my plugin is faster.\r\n    ∙ 'list' [1] and 'listchars' [2] options support.\r\n    ∙ Background color for the whole line with differencies, not just for text \r\n      (for g:html_no_pre [6]=1) and without trailing spaces (for \r\n      g:html_no_pre [6]=0).\r\n    ∙ Signs support. signs [7]\r\n    ∙ Tags linked to their definition. Implemented for 2html in \r\n      vimscript\u00c2\u00a0#2252. g:format_IgnoreTags [8]\r\n    ∙ (HTML) Anchors in tags definition location: for copying links. \r\n      g:format_HTMLAddLinkAtTagLine [9]\r\n    ∙ Side-by-side diff based on tables (2html relies on lines having the same \r\n      height which is generally false).\r\n    ∙ Full conceal support: with g:format_FormatConcealed [10] set to\u00c2\u00a02 \r\n      formats-format-html generates both concealed and shown.\r\n    ∙ Non-copyable signs, fold columns and numbers by default. 2html requires \r\n      setting g:html_prevent_copy [11].\r\n    ∙ 'fillchars' [12] vert suboption support (2html supports only diff and fold \r\n      suboptions).\r\n    ∙ Matches and 'hlsearch' [13] support. g:format_FormatMatches [14]\r\n    ∙ More correct highlighting in some cases.\r\n    ∙ Support for formats other then HTML\/XHTML (format-formats [15]). Makes it \r\n      relatively easy to add new format to the list of supported formats \r\n      (format-f-format.add [16]).\r\n    ∙ 2html still has more options for HTML formatting though.\r\n    ∙ Full 'foldcolumn' [17] support: 2html sets foldcolumn to either 'foldcolumn' [17] \r\n      value or maximum fold level, whichever is greater, formatvim uses \r\n      'foldcolumn' [17] value, fully emulating what vim shows.\r\n    ∙ 'spell' [18] checking support. g:format_IgnoreSpell [19]\r\n\r\n\r\nPlugin requires some additional plugins:\r\n    ∙ frawor (https:\/\/bitbucket.org\/ZyX_I\/frawor)\r\n\r\nNote: formatvim supports VAM (https:\/\/github.com\/MarcWeber\/vim-addon-manager). \r\n      It is prefered that you use it for formatvim installation.\r\n\r\n\r\nProject page: https:\/\/bitbucket.org\/ZyX_I\/formatvim\r\nDocumentation: http:\/\/vimcommunity.bitbucket.org\/doc\/format.txt.html\r\n\r\n\r\n[1] http:\/\/vimcommunity.bitbucket.org\/doc\/options.txt.html#.27list.27\r\n[2] http:\/\/vimcommunity.bitbucket.org\/doc\/options.txt.html#.27listchars.27\r\n[3] http:\/\/vimcommunity.bitbucket.org\/doc\/format.txt.html#format-side-by-side-diff\r\n[4] http:\/\/vimcommunity.bitbucket.org\/doc\/format.txt.html#g.3aformat_AllFolds\r\n[5] http:\/\/vimcommunity.bitbucket.org\/doc\/syntax.txt.html#.3aTOhtml\r\n[6] http:\/\/vimcommunity.bitbucket.org\/doc\/syntax.txt.html#g.3ahtml_no_pre\r\n[7] http:\/\/vimcommunity.bitbucket.org\/doc\/sign.txt.html#signs\r\n[8] http:\/\/vimcommunity.bitbucket.org\/doc\/format.txt.html#g.3aformat_IgnoreTags\r\n[9] http:\/\/vimcommunity.bitbucket.org\/doc\/format.txt.html#g.3aformat_HTMLAddLinkAtTagLine\r\n[10] http:\/\/vimcommunity.bitbucket.org\/doc\/format.txt.html#g.3aformat_FormatConcealed\r\n[11] http:\/\/vimcommunity.bitbucket.org\/doc\/syntax.txt.html#g.3ahtml_prevent_copy\r\n[12] http:\/\/vimcommunity.bitbucket.org\/doc\/options.txt.html#.27fillchars.27\r\n[13] http:\/\/vimcommunity.bitbucket.org\/doc\/options.txt.html#.27hlsearch.27\r\n[14] http:\/\/vimcommunity.bitbucket.org\/doc\/format.txt.html#g.3aformat_FormatMatches\r\n[15] http:\/\/vimcommunity.bitbucket.org\/doc\/format.txt.html#format-formats\r\n[16] http:\/\/vimcommunity.bitbucket.org\/doc\/format.txt.html#format-f-format.2eadd\r\n[17] http:\/\/vimcommunity.bitbucket.org\/doc\/options.txt.html#.27foldcolumn.27\r\n[18] http:\/\/vimcommunity.bitbucket.org\/doc\/options.txt.html#.27spell.27\r\n[19] http:\/\/vimcommunity.bitbucket.org\/doc\/format.txt.html#g.3aformat_IgnoreSpell\r\n\r\n","install_details":"You can install this plugin using vim-addon-manager (vimscript #2905) plugin (install vim-addon-manager, run \u00e2\u0080\u009cActivateAddons formatvim\u00e2\u0080\u009d and add \u00e2\u0080\u009ccall vam#ActivateAddons(['formatvim'])\u00e2\u0080\u009d to your .vimrc. Vim-addon-manager will install all dependencies for you). You can also use archives attached to this page, they contain plugin with all dependencies, so you do not need to fetch them yourself.\r\n\r\nGentoo users can use the following mercurial overlay: https:\/\/bitbucket.org\/ZyX_I\/pluginloader-overlay.\r\n","5":"You can install this plugin using vim-addon-manager (vimscript #2905) plugin (install vim-addon-manager, run \u00e2\u0080\u009cActivateAddons formatvim\u00e2\u0080\u009d and add \u00e2\u0080\u009ccall vam#ActivateAddons(['formatvim'])\u00e2\u0080\u009d to your .vimrc. Vim-addon-manager will install all dependencies for you). You can also use archives attached to this page, they contain plugin with all dependencies, so you do not need to fetch them yourself.\r\n\r\nGentoo users can use the following mercurial overlay: https:\/\/bitbucket.org\/ZyX_I\/pluginloader-overlay.\r\n","first_name":"ZyX","6":"ZyX","last_name":" ","7":" ","releases":[{"0":"3113","vim_version":"7.3","1":"7.3","script_version":"4.3","2":"4.3","version_comment":"- Added g:format_FormatLinks [1] and g:format_LinkRegexes [2] options which control \n  which text should be turned into links.\n- Added v:hlsearch [3] support.\n- Added support for matches created by matchaddpos() [4].\n- Added support for spell [5] checker.\n- Added missing diff argument to :Format: it was documented, but did not \n  actually exist.\n\n[1] http:\/\/vimpluginloader.sourceforge.net\/doc\/format.txt.html#g.3aformat_FormatLinks\n[2] http:\/\/vimpluginloader.sourceforge.net\/doc\/format.txt.html#g.3aformat_LinkRegexes\n[3] http:\/\/vimpluginloader.sourceforge.net\/doc\/eval.txt.html#v.3ahlsearch\n[4] http:\/\/vimpluginloader.sourceforge.net\/doc\/eval.txt.html#matchaddpos.28.29\n[5] http:\/\/vimpluginloader.sourceforge.net\/doc\/spell.txt.html#spell\n","3":"- Added g:format_FormatLinks [1] and g:format_LinkRegexes [2] options which control \n  which text should be turned into links.\n- Added v:hlsearch [3] support.\n- Added support for matches created by matchaddpos() [4].\n- Added support for spell [5] checker.\n- Added missing diff argument to :Format: it was documented, but did not \n  actually exist.\n\n[1] http:\/\/vimpluginloader.sourceforge.net\/doc\/format.txt.html#g.3aformat_FormatLinks\n[2] http:\/\/vimpluginloader.sourceforge.net\/doc\/format.txt.html#g.3aformat_LinkRegexes\n[3] http:\/\/vimpluginloader.sourceforge.net\/doc\/eval.txt.html#v.3ahlsearch\n[4] http:\/\/vimpluginloader.sourceforge.net\/doc\/eval.txt.html#matchaddpos.28.29\n[5] http:\/\/vimpluginloader.sourceforge.net\/doc\/spell.txt.html#spell\n","package":"formatvim-4.3.tar.gz","4":"formatvim-4.3.tar.gz","src_id":"22748","5":"22748","creation_date":"1420136547","6":"1420136547"},{"0":"3113","vim_version":"7.4","1":"7.4","script_version":"4.2","2":"4.2","version_comment":"HTML:\n- Added g:format_HTMLAdditionalCSS [1] option that allows overriding some CSS\n  properties from vimrc.\n- Refactored and documented CSS classes used in specification: see documentation \n  for g:format_HTMLAdditionalCSS [1].\n- Added g:format_HTMLFontFamily [2] option that controls font-family CSS property.\n\nDeveloper changes:\n- Now using format-spec-@=@ [3] properly is not possible without specifying @$@. \n  This change replaced used empirics (previously documentation said that you \n  should make sure string "'." is not present before @=@ in your expr).\n\n[1] http:\/\/vimpluginloader.sourceforge.net\/doc\/format.txt.html#g.3aformat_HTMLAdditionalCSS\n[2] http:\/\/vimpluginloader.sourceforge.net\/doc\/format.txt.html#g.3aformat_HTMLFontFamily\n[3] http:\/\/vimpluginloader.sourceforge.net\/doc\/format.txt.html#format-spec-.40.3d.40\n","3":"HTML:\n- Added g:format_HTMLAdditionalCSS [1] option that allows overriding some CSS\n  properties from vimrc.\n- Refactored and documented CSS classes used in specification: see documentation \n  for g:format_HTMLAdditionalCSS [1].\n- Added g:format_HTMLFontFamily [2] option that controls font-family CSS property.\n\nDeveloper changes:\n- Now using format-spec-@=@ [3] properly is not possible without specifying @$@. \n  This change replaced used empirics (previously documentation said that you \n  should make sure string "'." is not present before @=@ in your expr).\n\n[1] http:\/\/vimpluginloader.sourceforge.net\/doc\/format.txt.html#g.3aformat_HTMLAdditionalCSS\n[2] http:\/\/vimpluginloader.sourceforge.net\/doc\/format.txt.html#g.3aformat_HTMLFontFamily\n[3] http:\/\/vimpluginloader.sourceforge.net\/doc\/format.txt.html#format-spec-.40.3d.40\n","package":"formatvim-4.2.tar.gz","4":"formatvim-4.2.tar.gz","src_id":"20801","5":"20801","creation_date":"1379104552","6":"1379104552"},{"0":"3113","vim_version":"7.4","1":"7.4","script_version":"4.1","2":"4.1","version_comment":"New:\n- Add specification for www.vim.org (very simple: just adds [N] and links at-\n  the bottom): the above description and this message is formatted using it\n\nHTML:\n- Improved computation of line width\n- Made it also wiki-escape colons in anchors\n\nDeveloper options:\n- g:format_Debugging_Break configuration option that allows setting-\n  breakpoints in generated functions\n- g:format_Debugging_SaveO option that controls whether opts dictionary-\n  contents should be listed\n- Added format-spec-@!key@ [1] and format-spec-@!!key@ [2]: mutable dictionaries-\n  that are able to hold state\n- Removed opts.strescape\n\nFixes:\n- Fixed AllFolds javascript: clicking on header link unexpectedly caused outer-\n  fold close\n- Fixed double escaping that happened with some options’ values\n- Fixed closed folds appearance with 'foldcolumn' [3] set to 1\n- Fixed some typos in CSS\n\n[1] http:\/\/vimpluginloader.sourceforge.net\/doc\/format.txt.html#format-spec-.40.21key.40\n[2] http:\/\/vimpluginloader.sourceforge.net\/doc\/format.txt.html#format-spec-.40.21.21key.40\n[3] http:\/\/vimpluginloader.sourceforge.net\/doc\/options.txt.html#.27foldcolumn.27\n","3":"New:\n- Add specification for www.vim.org (very simple: just adds [N] and links at-\n  the bottom): the above description and this message is formatted using it\n\nHTML:\n- Improved computation of line width\n- Made it also wiki-escape colons in anchors\n\nDeveloper options:\n- g:format_Debugging_Break configuration option that allows setting-\n  breakpoints in generated functions\n- g:format_Debugging_SaveO option that controls whether opts dictionary-\n  contents should be listed\n- Added format-spec-@!key@ [1] and format-spec-@!!key@ [2]: mutable dictionaries-\n  that are able to hold state\n- Removed opts.strescape\n\nFixes:\n- Fixed AllFolds javascript: clicking on header link unexpectedly caused outer-\n  fold close\n- Fixed double escaping that happened with some options’ values\n- Fixed closed folds appearance with 'foldcolumn' [3] set to 1\n- Fixed some typos in CSS\n\n[1] http:\/\/vimpluginloader.sourceforge.net\/doc\/format.txt.html#format-spec-.40.21key.40\n[2] http:\/\/vimpluginloader.sourceforge.net\/doc\/format.txt.html#format-spec-.40.21.21key.40\n[3] http:\/\/vimpluginloader.sourceforge.net\/doc\/options.txt.html#.27foldcolumn.27\n","package":"formatvim-4.1.tar.gz","4":"formatvim-4.1.tar.gz","src_id":"20789","5":"20789","creation_date":"1378924522","6":"1378924522"},{"0":"3113","vim_version":"7.4","1":"7.4","script_version":"4.0.1","2":"4.0.1","version_comment":"Some AllFolds improvements:\n- Added support for &foldminlines option\n- Added sign, number and fold colum contents to the link text\n- Improved JavaScript used by HTML AllFolds implementation","3":"Some AllFolds improvements:\n- Added support for &foldminlines option\n- Added sign, number and fold colum contents to the link text\n- Improved JavaScript used by HTML AllFolds implementation","package":"formatvim-4.0.1.tar.gz","4":"formatvim-4.0.1.tar.gz","src_id":"20769","5":"20769","creation_date":"1378727594","6":"1378727594"},{"0":"3113","vim_version":"7.3","1":"7.3","script_version":"4.0","2":"4.0","version_comment":"Added support for &concealcursor\nAdded IgnoreDiff option\nAdded options for HTML formatter, including\n- an option to add links at the place where tag is defined (so that they can be easily copied)\n- Added option that controls file name in anchors\n- Added option that controls <title> contents\n- Added option that enables generating human-readable style names\nAdded support for formatting matches\nAdd @<@expr@>@: compile-time evaluated expressions\nAdd addoptsfun format key\nMajor performance improvement of tags processing (requires vim-7.3.627)\nMinor performance improvement of main formatting cycle\nRemoved caching\nRemoved concealed key, added concealedstart and concealedend\nAdded debugging options and profiling support\nA big number of fixes\nMade signs column use uncopyable <input> with background image for icons","3":"Added support for &concealcursor\nAdded IgnoreDiff option\nAdded options for HTML formatter, including\n- an option to add links at the place where tag is defined (so that they can be easily copied)\n- Added option that controls file name in anchors\n- Added option that controls <title> contents\n- Added option that enables generating human-readable style names\nAdded support for formatting matches\nAdd @<@expr@>@: compile-time evaluated expressions\nAdd addoptsfun format key\nMajor performance improvement of tags processing (requires vim-7.3.627)\nMinor performance improvement of main formatting cycle\nRemoved caching\nRemoved concealed key, added concealedstart and concealedend\nAdded debugging options and profiling support\nA big number of fixes\nMade signs column use uncopyable <input> with background image for icons","package":"formatvim-4.0.tar.gz","4":"formatvim-4.0.tar.gz","src_id":"20766","5":"20766","creation_date":"1378642013","6":"1378642013"},{"0":"3113","vim_version":"7.3","1":"7.3","script_version":"3.2.3","2":"3.2.3","version_comment":"Splitted plugin into autoload\/format.vim and plugin\/format.vim\nFixed progress bar\nFixed html-vimwiki style (both are regressions)","3":"Splitted plugin into autoload\/format.vim and plugin\/format.vim\nFixed progress bar\nFixed html-vimwiki style (both are regressions)","package":"formatvim-3.2.3.tar.gz","4":"formatvim-3.2.3.tar.gz","src_id":"19134","5":"19134","creation_date":"1354919562","6":"1354919562"},{"0":"3113","vim_version":"7.3","1":"7.3","script_version":"3.2.2","2":"3.2.2","version_comment":"Improved unselectable columns\nMade script that creates color file require almost no manual work\nImproved perfomance","3":"Improved unselectable columns\nMade script that creates color file require almost no manual work\nImproved perfomance","package":"formatvim-3.2.2.tar.gz","4":"formatvim-3.2.2.tar.gz","src_id":"18677","5":"18677","creation_date":"1348415436","6":"1348415436"},{"0":"3113","vim_version":"7.3","1":"7.3","script_version":"3.2","2":"3.2","version_comment":"Added id="tag" spans to html specification\nAdded @__key@\nAdded support for &highlight\nAdded support for &numberwidth\nAdded csi format","3":"Added id="tag" spans to html specification\nAdded @__key@\nAdded support for &highlight\nAdded support for &numberwidth\nAdded csi format","package":"formatvim-3.2.tar.gz","4":"formatvim-3.2.tar.gz","src_id":"18616","5":"18616","creation_date":"1347732207","6":"1347732207"},{"0":"3113","vim_version":"7.3","1":"7.3","script_version":"3.1","2":"3.1","version_comment":"Improved tags processing speed\nAdded starttagreg\/endtagreg command-line options and StartTagReg\/EndTagReg global options (useful for formatting help files)\nMade html specification not use &nbsp;s anymore","3":"Improved tags processing speed\nAdded starttagreg\/endtagreg command-line options and StartTagReg\/EndTagReg global options (useful for formatting help files)\nMade html specification not use &nbsp;s anymore","package":"formatvim-3.1.tar.gz","4":"formatvim-3.1.tar.gz","src_id":"18202","5":"18202","creation_date":"1341075175","6":"1341075175"},{"0":"3113","vim_version":"7.3","1":"7.3","script_version":"3.0","2":"3.0","version_comment":"Ported plugin to new framework\nVarious foldcolumn fixes\nFixed highlighting of line under cursor\nAdded signs support\nMade numbers, fold and signs column uncopyable in html specification\nAdded fillchars option support\nMinor perfomance improvement\nAdded to' prefix for :Format command, other API changes","3":"Ported plugin to new framework\nVarious foldcolumn fixes\nFixed highlighting of line under cursor\nAdded signs support\nMade numbers, fold and signs column uncopyable in html specification\nAdded fillchars option support\nMinor perfomance improvement\nAdded to' prefix for :Format command, other API changes","package":"formatvim-3.0.tar.gz","4":"formatvim-3.0.tar.gz","src_id":"15935","5":"15935","creation_date":"1308488974","6":"1308488974"},{"0":"3113","vim_version":"7.3","1":"7.3","script_version":"2.5.1","2":"2.5.1","version_comment":"Fixed error when creating side-by-side diff with difffillers at the end of buffers","3":"Fixed error when creating side-by-side diff with difffillers at the end of buffers","package":"formatvim-2.5.1.tar.gz","4":"formatvim-2.5.1.tar.gz","src_id":"15375","5":"15375","creation_date":"1301893755","6":"1301893755"},{"0":"3113","vim_version":"7.3","1":"7.3","script_version":"2.5","2":"2.5","version_comment":"Switched to new FormatCommand arguments model","3":"Switched to new FormatCommand arguments model","package":"formatvim-2.5.tar.gz","4":"formatvim-2.5.tar.gz","src_id":"14574","5":"14574","creation_date":"1292726563","6":"1292726563"},{"0":"3113","vim_version":"9999","1":"9999","script_version":"2.4.3","2":"2.4.3","version_comment":"Reposting bundle due to core plugins update","3":"Reposting bundle due to core plugins update","package":"formatvim-2.4.3.tar.gz","4":"formatvim-2.4.3.tar.gz","src_id":"14569","5":"14569","creation_date":"1292713548","6":"1292713548"},{"0":"3113","vim_version":"7.3","1":"7.3","script_version":"2.4.3","2":"2.4.3","version_comment":"Removed yamlvim dependency, added tokens format specification and @~@ and @^@, fixed formatting of closed folds","3":"Removed yamlvim dependency, added tokens format specification and @~@ and @^@, fixed formatting of closed folds","package":"formatvim-2.4.3.tar.gz","4":"formatvim-2.4.3.tar.gz","src_id":"14476","5":"14476","creation_date":"1292105032","6":"1292105032"},{"0":"3113","vim_version":"9999","1":"9999","script_version":"2.4.2","2":"2.4.2","version_comment":"Reposting bundle due to core plugins update","3":"Reposting bundle due to core plugins update","package":"formatvim-2.4.2.tar.gz","4":"formatvim-2.4.2.tar.gz","src_id":"14323","5":"14323","creation_date":"1290257926","6":"1290257926"},{"0":"3113","vim_version":"7.3","1":"7.3","script_version":"2.4.2","2":"2.4.2","version_comment":"Moved color lists to config\/formatvim\/colors-*.yaml, made it possible to override colors","3":"Moved color lists to config\/formatvim\/colors-*.yaml, made it possible to override colors","package":"formatvim-2.4.2.tar.gz","4":"formatvim-2.4.2.tar.gz","src_id":"14190","5":"14190","creation_date":"1289036737","6":"1289036737"},{"0":"3113","vim_version":"7.2","1":"7.2","script_version":"2.3.4","2":"2.3.4","version_comment":"Added %!{cmd}!% format specification, added lcs:conceal support, added support for the case when 'lcs' does not have tab and 'list' is on, lots of bugfixes","3":"Added %!{cmd}!% format specification, added lcs:conceal support, added support for the case when 'lcs' does not have tab and 'list' is on, lots of bugfixes","package":"formatvim-2.3.4.tar.gz","4":"formatvim-2.3.4.tar.gz","src_id":"13788","5":"13788","creation_date":"1284007274","6":"1284007274"},{"0":"3113","vim_version":"7.2","1":"7.2","script_version":"2.3.3","2":"2.3.3","version_comment":"Added tests, fixed one bug","3":"Added tests, fixed one bug","package":"formatvim-2.3.3.tar.gz","4":"formatvim-2.3.3.tar.gz","src_id":"13707","5":"13707","creation_date":"1283028975","6":"1283028975"},{"0":"3113","vim_version":"7.2","1":"7.2","script_version":"2.3.2","2":"2.3.2","version_comment":"Fixed displaying of blank lines","3":"Fixed displaying of blank lines","package":"formatvim-2.3.2.tar.gz","4":"formatvim-2.3.2.tar.gz","src_id":"13706","5":"13706","creation_date":"1283026229","6":"1283026229"},{"0":"3113","vim_version":"7.2","1":"7.2","script_version":"2.3.1","2":"2.3.1","version_comment":"Added relative numbering support","3":"Added relative numbering support","package":"formatvim-2.3.1.tar.gz","4":"formatvim-2.3.1.tar.gz","src_id":"13704","5":"13704","creation_date":"1283019753","6":"1283019753"},{"0":"3113","vim_version":"7.2","1":"7.2","script_version":"2.3","2":"2.3","version_comment":"Added concealed characters support","3":"Added concealed characters support","package":"formatvim-2.3.tar.gz","4":"formatvim-2.3.tar.gz","src_id":"13702","5":"13702","creation_date":"1283017370","6":"1283017370"},{"0":"3113","vim_version":"7.2","1":"7.2","script_version":"2.2.1","2":"2.2.1","version_comment":"Fixed some validator errors","3":"Fixed some validator errors","package":"formatvim-2.2.1.tar.gz","4":"formatvim-2.2.1.tar.gz","src_id":"13616","5":"13616","creation_date":"1282132330","6":"1282132330"},{"0":"3113","vim_version":"7.2","1":"7.2","script_version":"2.2","2":"2.2","version_comment":"Added support for tags","3":"Added support for tags","package":"formatvim-2.2.tar.gz","4":"formatvim-2.2.tar.gz","src_id":"13572","5":"13572","creation_date":"1281828596","6":"1281828596"},{"0":"3113","vim_version":"7.2","1":"7.2","script_version":"2.1","2":"2.1","version_comment":"Added support for more then two diff windows, some other fixes","3":"Added support for more then two diff windows, some other fixes","package":"formatvim-2.1.tar.gz","4":"formatvim-2.1.tar.gz","src_id":"13520","5":"13520","creation_date":"1281272019","6":"1281272019"},{"0":"3113","vim_version":"7.2","1":"7.2","script_version":"2.0","2":"2.0","version_comment":"Added experimental side-by-side diff creation, added cursor position support (unfinished, disabled by default), major changes to format specification, some fixes","3":"Added experimental side-by-side diff creation, added cursor position support (unfinished, disabled by default), major changes to format specification, some fixes","package":"format-2.0.tar.xz","4":"format-2.0.tar.xz","src_id":"13488","5":"13488","creation_date":"1280951833","6":"1280951833"},{"0":"3113","vim_version":"7.0","1":"7.0","script_version":"1.8.2","2":"1.8.2","version_comment":"Added \u00c2\u00abKeepColorCache\u00c2\u00bb option, improved \u00c2\u00abbbcode-unixforum\u00c2\u00bb format specification, some other fixes.","3":"Added \u00c2\u00abKeepColorCache\u00c2\u00bb option, improved \u00c2\u00abbbcode-unixforum\u00c2\u00bb format specification, some other fixes.","package":"format-1.8.2.tar.xz","4":"format-1.8.2.tar.xz","src_id":"13269","5":"13269","creation_date":"1277910268","6":"1277910268"},{"0":"3113","vim_version":"7.0","1":"7.0","script_version":"1.8.1","2":"1.8.1","version_comment":"Made \u00c2\u00ablinestart'\u00c2\u00bband \u00c2\u00ablineend\u00c2\u00bb keys optional, some fixes","3":"Made \u00c2\u00ablinestart'\u00c2\u00bband \u00c2\u00ablineend\u00c2\u00bb keys optional, some fixes","package":"format-1.8.1.tar.xz","4":"format-1.8.1.tar.xz","src_id":"13266","5":"13266","creation_date":"1277888157","6":"1277888157"},{"0":"3113","vim_version":"7.0","1":"7.0","script_version":"1.8","2":"1.8","version_comment":"Added FormatCommand options that override both default and user settings.","3":"Added FormatCommand options that override both default and user settings.","package":"format-1.8.tar.xz","4":"format-1.8.tar.xz","src_id":"13265","5":"13265","creation_date":"1277880198","6":"1277880198"},{"0":"3113","vim_version":"7.0","1":"7.0","script_version":"1.7","2":"1.7","version_comment":"Added \u00c2\u00abhtml-vimwiki\u00c2\u00bb format.","3":"Added \u00c2\u00abhtml-vimwiki\u00c2\u00bb format.","package":"format-1.7.tar.xz","4":"format-1.7.tar.xz","src_id":"13260","5":"13260","creation_date":"1277751038","6":"1277751038"},{"0":"3113","vim_version":"7.0","1":"7.0","script_version":"1.6","2":"1.6","version_comment":"Added commandline completion","3":"Added commandline completion","package":"format-1.6.tar.xz","4":"format-1.6.tar.xz","src_id":"13140","5":"13140","creation_date":"1275855455","6":"1275855455"},{"0":"3113","vim_version":"7.0","1":"7.0","script_version":"1.5","2":"1.5","version_comment":"Added AllFolds option (for html format specification it is just like g:html_dynamic_folds for 2html, but you are free to write something else), ~8% perfomance improvement.","3":"Added AllFolds option (for html format specification it is just like g:html_dynamic_folds for 2html, but you are free to write something else), ~8% perfomance improvement.","package":"format-1.5.tar.xz","4":"format-1.5.tar.xz","src_id":"13137","5":"13137","creation_date":"1275847648","6":"1275847648"},{"0":"3113","vim_version":"7.0","1":"7.0","script_version":"1.4","2":"1.4","version_comment":"Added \"nolf\" (joins everything in a single line) and \"haslf\" (allow format specification to define line breaks) format specification options.","3":"Added \"nolf\" (joins everything in a single line) and \"haslf\" (allow format specification to define line breaks) format specification options.","package":"format-1.4.tar.xz","4":"format-1.4.tar.xz","src_id":"13133","5":"13133","creation_date":"1275816661","6":"1275816661"},{"0":"3113","vim_version":"7.0","1":"7.0","script_version":"1.3","2":"1.3","version_comment":"Added lcs:nbsp handling, some fixes","3":"Added lcs:nbsp handling, some fixes","package":"format-1.3.tar.xz","4":"format-1.3.tar.xz","src_id":"13131","5":"13131","creation_date":"1275814368","6":"1275814368"},{"0":"3113","vim_version":"7.0","1":"7.0","script_version":"1.2.1","2":"1.2.1","version_comment":"Greatly improved performance (~37% for ShowProgress=0, ~53% for ShowProgress=1 and ~43% for ShowProgress=2).","3":"Greatly improved performance (~37% for ShowProgress=0, ~53% for ShowProgress=1 and ~43% for ShowProgress=2).","package":"format-1.2.1.tar.xz","4":"format-1.2.1.tar.xz","src_id":"13119","5":"13119","creation_date":"1275787693","6":"1275787693"},{"0":"3113","vim_version":"7.0","1":"7.0","script_version":"1.2","2":"1.2","version_comment":"Added ShowProgress option (adds progressbar). Note that ShowProgress=2 makes my script ~30% slower while ShowProgress=1 slows down only for ~5%.","3":"Added ShowProgress option (adds progressbar). Note that ShowProgress=2 makes my script ~30% slower while ShowProgress=1 slows down only for ~5%.","package":"format-1.2.tar.xz","4":"format-1.2.tar.xz","src_id":"13118","5":"13118","creation_date":"1275778418","6":"1275778418"},{"0":"3113","vim_version":"7.0","1":"7.0","script_version":"1.1","2":"1.1","version_comment":"Added NoLineNR (removes line numbering) and CollapsFiller (collapses too long diff fillers) options.","3":"Added NoLineNR (removes line numbering) and CollapsFiller (collapses too long diff fillers) options.","package":"format-1.1.tar.xz","4":"format-1.1.tar.xz","src_id":"13117","5":"13117","creation_date":"1275771333","6":"1275771333"},{"0":"3113","vim_version":"7.2","1":"7.2","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"format-1.0.tar.xz","4":"format-1.0.tar.xz","src_id":"13116","5":"13116","creation_date":"1275764335","6":"1275764335"}]},"3112":{"script_id":"3112","0":"3112","script_name":"RemoveFile.vim","1":"RemoveFile.vim","script_type":"utility","2":"utility","summary":"Remove a file from the disk","3":"Remove a file from the disk","description":"Usage:\r\n\r\n :Remove[!] [file]\r\n\r\nWith a ! the script will remove the specified file without prompting.  If file is omitted, the script uses the file associated with the current buffer.\r\n\r\nThis script does not delete, change, or update any associated buffers in any way.","4":"Usage:\r\n\r\n :Remove[!] [file]\r\n\r\nWith a ! the script will remove the specified file without prompting.  If file is omitted, the script uses the file associated with the current buffer.\r\n\r\nThis script does not delete, change, or update any associated buffers in any way.","install_details":"Place RemoveFile.vim in your plugin directory.  See \":help 'runtimepath'\".  Alternately, put it wherever you want and source it in your vimrc.","5":"Place RemoveFile.vim in your plugin directory.  See \":help 'runtimepath'\".  Alternately, put it wherever you want and source it in your vimrc.","first_name":"Christian J.","6":"Christian J.","last_name":"Robinson","7":"Robinson","releases":[{"0":"3112","vim_version":"7.0","1":"7.0","script_version":"0.2","2":"0.2","version_comment":"- Update for Vim 9 (no new features)","3":"- Update for Vim 9 (no new features)","package":"RemoveFile.vim","4":"RemoveFile.vim","src_id":"28144","5":"28144","creation_date":"1661156432","6":"1661156432"},{"0":"3112","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"RemoveFile.vim","4":"RemoveFile.vim","src_id":"13114","5":"13114","creation_date":"1275760744","6":"1275760744"}]},"3111":{"script_id":"3111","0":"3111","script_name":"leglight2","1":"leglight2","script_type":"color scheme","2":"color scheme","summary":"Another light colour scheme based off of legiblelight","3":"Another light colour scheme based off of legiblelight","description":"I wrote legiblelight on a win box and it didn't port over to my linux machine well, so I re-wrote it in linux with a few tweaks. Hope you like it. ","4":"I wrote legiblelight on a win box and it didn't port over to my linux machine well, so I re-wrote it in linux with a few tweaks. Hope you like it. ","install_details":"add to ~\/.vim\/colors like any other script","5":"add to ~\/.vim\/colors like any other script","first_name":"Tony","6":"Tony","last_name":"Dunsworth","7":"Dunsworth","releases":[{"0":"3111","vim_version":"7.0","1":"7.0","script_version":"1.0.1","2":"1.0.1","version_comment":"Initial upload","3":"Initial upload","package":"leglight2.vim","4":"leglight2.vim","src_id":"13107","5":"13107","creation_date":"1275653594","6":"1275653594"}]},"3110":{"script_id":"3110","0":"3110","script_name":"mdx.vim","1":"mdx.vim","script_type":"syntax","2":"syntax","summary":"Syntax highlighting for MDX (OLAP queries) ","3":"Syntax highlighting for MDX (OLAP queries) ","description":"Syntax highlighting for MDX (OLAP queries)\r\n\r\nIf you want to add any improvements, please fork the file from:\r\nhttp:\/\/github.com\/findango\/mdxdotvim\r\n","4":"Syntax highlighting for MDX (OLAP queries)\r\n\r\nIf you want to add any improvements, please fork the file from:\r\nhttp:\/\/github.com\/findango\/mdxdotvim\r\n","install_details":"Unzip in ~\/.vim or ~\/vimfiles (on Windows).\r\n","5":"Unzip in ~\/.vim or ~\/vimfiles (on Windows).\r\n","first_name":"Finlay","6":"Finlay","last_name":"Cannon","7":"Cannon","releases":[{"0":"3110","vim_version":"6.0","1":"6.0","script_version":"1.2","2":"1.2","version_comment":"Added ftplugin with commentstring settings.","3":"Added ftplugin with commentstring settings.","package":"mdx-1.2.zip","4":"mdx-1.2.zip","src_id":"20971","5":"20971","creation_date":"1382934883","6":"1382934883"},{"0":"3110","vim_version":"6.0","1":"6.0","script_version":"1.1","2":"1.1","version_comment":"Added ftdetect, and handling for [member names]","3":"Added ftdetect, and handling for [member names]","package":"mdx.zip","4":"mdx.zip","src_id":"15646","5":"15646","creation_date":"1305488562","6":"1305488562"},{"0":"3110","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"mdx.vim","4":"mdx.vim","src_id":"13106","5":"13106","creation_date":"1275631012","6":"1275631012"}]},"3109":{"script_id":"3109","0":"3109","script_name":"LaTeX Box","1":"LaTeX Box","script_type":"ftplugin","2":"ftplugin","summary":"Lightweight Toolbox for LaTeX","3":"Lightweight Toolbox for LaTeX","description":"This plugin provides:\r\n- Background compilation using latexmk;\r\n- Completion for commands, environments, labels, and bibtex entries;\r\n- A simple table of contents;\r\n- Smart indentation (activated with \"set smartindent\");\r\n- HIghlight matching \\begin\/\\end pairs;\r\n- Motion between \\begin\/\\end pairs with the % key;\r\n- Motion through brackets\/braces (with user-defined keys);\r\n- Environment objects (e.g., select environement with \"vie\" or \"vae\");\r\n- Inline math objects (e.g., select inline math with \"vi$\" or \"va$\").\r\n\r\nSee \":help latex-box\" for more details.\r\n\r\nThis plugins aims at being lightweight and simple. For more fully-fledged plugins, see:\r\n- LaTeX-Suite: vimscript#475\r\n- AutomaticTexPlugin: vimscript#2945\r\n\r\n","4":"This plugin provides:\r\n- Background compilation using latexmk;\r\n- Completion for commands, environments, labels, and bibtex entries;\r\n- A simple table of contents;\r\n- Smart indentation (activated with \"set smartindent\");\r\n- HIghlight matching \\begin\/\\end pairs;\r\n- Motion between \\begin\/\\end pairs with the % key;\r\n- Motion through brackets\/braces (with user-defined keys);\r\n- Environment objects (e.g., select environement with \"vie\" or \"vae\");\r\n- Inline math objects (e.g., select inline math with \"vi$\" or \"va$\").\r\n\r\nSee \":help latex-box\" for more details.\r\n\r\nThis plugins aims at being lightweight and simple. For more fully-fledged plugins, see:\r\n- LaTeX-Suite: vimscript#475\r\n- AutomaticTexPlugin: vimscript#2945\r\n\r\n","install_details":"Edit the vba file in vim and source it with \":so %\".\r\nTo use background compilation, try <Leader>ll\r\nTo use omni completion, try <CTRL-X><CTRL-O>\r\n\r\nOfficial repository: https:\/\/github.com\/LaTeX-Box-Team\/LaTeX-Box\r\n\r\nOld Project Page: https:\/\/launchpad.net\/vim-latex-box\r\nOld Bug Tracker: https:\/\/bugs.launchpad.net\/vim-latex-box\/\r\nWe will migrate the bug reports to github.","5":"Edit the vba file in vim and source it with \":so %\".\r\nTo use background compilation, try <Leader>ll\r\nTo use omni completion, try <CTRL-X><CTRL-O>\r\n\r\nOfficial repository: https:\/\/github.com\/LaTeX-Box-Team\/LaTeX-Box\r\n\r\nOld Project Page: https:\/\/launchpad.net\/vim-latex-box\r\nOld Bug Tracker: https:\/\/bugs.launchpad.net\/vim-latex-box\/\r\nWe will migrate the bug reports to github.","first_name":"David","6":"David","last_name":"Munger","7":"Munger","releases":[{"0":"3109","vim_version":"7.3","1":"7.3","script_version":"0.9.5","2":"0.9.5","version_comment":"fixed viewer command","3":"fixed viewer command","package":"LatexBox.vmb","4":"LatexBox.vmb","src_id":"16732","5":"16732","creation_date":"1319464634","6":"1319464634"},{"0":"3109","vim_version":"7.3","1":"7.3","script_version":"0.9.5","2":"0.9.5","version_comment":"bug fixes\r\nsome support for tcsh\r\npatch to wrap in environment by W. E. Skeith","3":"bug fixes\r\nsome support for tcsh\r\npatch to wrap in environment by W. E. Skeith","package":"LatexBox.vmb","4":"LatexBox.vmb","src_id":"16675","5":"16675","creation_date":"1318692536","6":"1318692536"},{"0":"3109","vim_version":"7.2","1":"7.2","script_version":"0.9.4","2":"0.9.4","version_comment":"bug fixes","3":"bug fixes","package":"LatexBox.vba","4":"LatexBox.vba","src_id":"14972","5":"14972","creation_date":"1297089027","6":"1297089027"},{"0":"3109","vim_version":"7.2","1":"7.2","script_version":"0.9.3","2":"0.9.3","version_comment":"fix TOC bug for unnumbered sections","3":"fix TOC bug for unnumbered sections","package":"LatexBox.vba","4":"LatexBox.vba","src_id":"13673","5":"13673","creation_date":"1282739792","6":"1282739792"},{"0":"3109","vim_version":"7.2","1":"7.2","script_version":"0.9.2","2":"0.9.2","version_comment":"fix TOC bug with amsart","3":"fix TOC bug with amsart","package":"LatexBox.vba","4":"LatexBox.vba","src_id":"13663","5":"13663","creation_date":"1282665778","6":"1282665778"},{"0":"3109","vim_version":"7.0","1":"7.0","script_version":"0.9.1","2":"0.9.1","version_comment":"Plenty of minor bug fixes.","3":"Plenty of minor bug fixes.","package":"LatexBox.vba","4":"LatexBox.vba","src_id":"13495","5":"13495","creation_date":"1281027759","6":"1281027759"},{"0":"3109","vim_version":"7.0","1":"7.0","script_version":"0.9.0","2":"0.9.0","version_comment":"- add highlight matching pairs\r\n- improve pair matching","3":"- add highlight matching pairs\r\n- improve pair matching","package":"LatexBox.vba","4":"LatexBox.vba","src_id":"13264","5":"13264","creation_date":"1277872850","6":"1277872850"},{"0":"3109","vim_version":"7.0","1":"7.0","script_version":"0.8.5","2":"0.8.5","version_comment":"Added the indent file that was missing in previous versions. I forgot to add it to the vimball in the previous versions.","3":"Added the indent file that was missing in previous versions. I forgot to add it to the vimball in the previous versions.","package":"LatexBox.vba","4":"LatexBox.vba","src_id":"13248","5":"13248","creation_date":"1277590470","6":"1277590470"},{"0":"3109","vim_version":"7.0","1":"7.0","script_version":"0.8.4","2":"0.8.4","version_comment":"- New g:LatexBox_split_width setting\r\n- Add matching for '$' pairs\r\n- Add inline math objects","3":"- New g:LatexBox_split_width setting\r\n- Add matching for '$' pairs\r\n- Add inline math objects","package":"LatexBox.vba","4":"LatexBox.vba","src_id":"13238","5":"13238","creation_date":"1277334292","6":"1277334292"},{"0":"3109","vim_version":"7.0","1":"7.0","script_version":"0.8.3","2":"0.8.3","version_comment":"- Load errors automatically when latexmk exits with nonzero status\r\n- Fixed a stupid bug that would prevent in bibtex completion","3":"- Load errors automatically when latexmk exits with nonzero status\r\n- Fixed a stupid bug that would prevent in bibtex completion","package":"LatexBox.vba","4":"LatexBox.vba","src_id":"13234","5":"13234","creation_date":"1277216441","6":"1277216441"},{"0":"3109","vim_version":"7.0","1":"7.0","script_version":"0.8.2","2":"0.8.2","version_comment":"- Optimized smart indentation for speed","3":"- Optimized smart indentation for speed","package":"LatexBox.vba","4":"LatexBox.vba","src_id":"13231","5":"13231","creation_date":"1277172411","6":"1277172411"},{"0":"3109","vim_version":"7.0","1":"7.0","script_version":"0.8.1","2":"0.8.1","version_comment":"- Fixed bug in % matching.\r\n- Support for environment objects (e.g., select with \"vie\" or \"vae\")","3":"- Fixed bug in % matching.\r\n- Support for environment objects (e.g., select with \"vie\" or \"vae\")","package":"LatexBox.vba","4":"LatexBox.vba","src_id":"13228","5":"13228","creation_date":"1277099153","6":"1277099153"},{"0":"3109","vim_version":"7.0","1":"7.0","script_version":"0.8","2":"0.8","version_comment":"- Smart indentation \r\n- Navigation through \\begin\/\\end and \\left\/\\right pairs with % \r\n- Change environment, including \\[ \\] \r\n- Kill all latexmk instances when vim quits \r\n- Speed optimization \r\n- Do not complete closing bracket if already present \r\n- Support \\left\/\\right in close last environment","3":"- Smart indentation \r\n- Navigation through \\begin\/\\end and \\left\/\\right pairs with % \r\n- Change environment, including \\[ \\] \r\n- Kill all latexmk instances when vim quits \r\n- Speed optimization \r\n- Do not complete closing bracket if already present \r\n- Support \\left\/\\right in close last environment","package":"LatexBox.vba","4":"LatexBox.vba","src_id":"13227","5":"13227","creation_date":"1277077776","6":"1277077776"},{"0":"3109","vim_version":"7.0","1":"7.0","script_version":"0.5","2":"0.5","version_comment":"minor bug fixes\r\nfixes by Marcin Szamotulski\r\ndeprecated templates\r\nnew mappings <Plug>CloseLastEnv and <Plug>WrapSelection","3":"minor bug fixes\r\nfixes by Marcin Szamotulski\r\ndeprecated templates\r\nnew mappings <Plug>CloseLastEnv and <Plug>WrapSelection","package":"LatexBox.vba","4":"LatexBox.vba","src_id":"13203","5":"13203","creation_date":"1276753797","6":"1276753797"},{"0":"3109","vim_version":"7.0","1":"7.0","script_version":"0.4","2":"0.4","version_comment":"Added :LatexmkStop command to stop latexmk (thanks to Charlie Tanksley for Mac testing). \r\nBug fix in the TOC by Marcin Szamotulski. \r\nNew :LatexmkStatusDetailed command to show process group ID's of running instances of latexmk. \r\nNew g:LatexBox_cite_pattern and g:LatexBox_ref_pattern options.","3":"Added :LatexmkStop command to stop latexmk (thanks to Charlie Tanksley for Mac testing). \r\nBug fix in the TOC by Marcin Szamotulski. \r\nNew :LatexmkStatusDetailed command to show process group ID's of running instances of latexmk. \r\nNew g:LatexBox_cite_pattern and g:LatexBox_ref_pattern options.","package":"LatexBox.vba","4":"LatexBox.vba","src_id":"13191","5":"13191","creation_date":"1276626894","6":"1276626894"},{"0":"3109","vim_version":"6.0","1":"6.0","script_version":"0.3.3","2":"0.3.3","version_comment":"Fixed a bug in \\ref completion.","3":"Fixed a bug in \\ref completion.","package":"LatexBox.vba","4":"LatexBox.vba","src_id":"13159","5":"13159","creation_date":"1276200187","6":"1276200187"},{"0":"3109","vim_version":"6.0","1":"6.0","script_version":"0.3.2","2":"0.3.2","version_comment":"Fixed a bug in brace\/bracket motion","3":"Fixed a bug in brace\/bracket motion","package":"LatexBox.vba","4":"LatexBox.vba","src_id":"13150","5":"13150","creation_date":"1276108071","6":"1276108071"},{"0":"3109","vim_version":"6.0","1":"6.0","script_version":"0.3.1","2":"0.3.1","version_comment":"Fixed a but in the TOC.","3":"Fixed a but in the TOC.","package":"LatexBox.vba","4":"LatexBox.vba","src_id":"13101","5":"13101","creation_date":"1275600017","6":"1275600017"}]},"3108":{"script_id":"3108","0":"3108","script_name":"GUI Box","1":"GUI Box","script_type":"utility","2":"utility","summary":"Color scheme and font menu window","3":"Color scheme and font menu window","description":"This plugin provides:\r\n- A color scheme menu to choose among your favorite color schemes;\r\n- A font menu to choose among your favorite fonts;\r\n- A command to toggle the GUI menu.\r\n\r\nSee \":help gui-box\" for details.","4":"This plugin provides:\r\n- A color scheme menu to choose among your favorite color schemes;\r\n- A font menu to choose among your favorite fonts;\r\n- A command to toggle the GUI menu.\r\n\r\nSee \":help gui-box\" for details.","install_details":"Open the vba file in vim, then source it with \":so %\".\r\n\r\nTo use the plugin, you must edit your .gvimrc in order to:\r\n\r\n1. define your favorite fonts and color schemes, e.g.\r\n\r\n\tlet g:gui_fonts = ['Monospace 10', 'Lucida Console 10', 'Courier New 10']\r\n\tlet g:gui_colors = ['ego', 'corporation', 'github', 'satori', 'sienna']\r\n\r\n2. add your own mappings, e.g.\r\n\r\n\tnmap <Leader>gc <Plug>ColorMenu\r\n\tnmap <Leader>gf <Plug>FontMenu\r\n\tnmap <Leader>gm <Plug>ToggleMenuBar\r\n\r\nProject Page: https:\/\/launchpad.net\/vim-gui-box\r\nBug Tracker: https:\/\/bugs.launchpad.net\/vim-gui-box\/","5":"Open the vba file in vim, then source it with \":so %\".\r\n\r\nTo use the plugin, you must edit your .gvimrc in order to:\r\n\r\n1. define your favorite fonts and color schemes, e.g.\r\n\r\n\tlet g:gui_fonts = ['Monospace 10', 'Lucida Console 10', 'Courier New 10']\r\n\tlet g:gui_colors = ['ego', 'corporation', 'github', 'satori', 'sienna']\r\n\r\n2. add your own mappings, e.g.\r\n\r\n\tnmap <Leader>gc <Plug>ColorMenu\r\n\tnmap <Leader>gf <Plug>FontMenu\r\n\tnmap <Leader>gm <Plug>ToggleMenuBar\r\n\r\nProject Page: https:\/\/launchpad.net\/vim-gui-box\r\nBug Tracker: https:\/\/bugs.launchpad.net\/vim-gui-box\/","first_name":"David","6":"David","last_name":"Munger","7":"Munger","releases":[{"0":"3108","vim_version":"7.0","1":"7.0","script_version":"0.6.2","2":"0.6.2","version_comment":"Add nospell (thanks Marcin).","3":"Add nospell (thanks Marcin).","package":"GuiBox.vba","4":"GuiBox.vba","src_id":"15615","5":"15615","creation_date":"1304956376","6":"1304956376"},{"0":"3108","vim_version":"7.0","1":"7.0","script_version":"0.6.1","2":"0.6.1","version_comment":"Fixed a bug that would make buffers unmodifiable.","3":"Fixed a bug that would make buffers unmodifiable.","package":"GuiBox.vba","4":"GuiBox.vba","src_id":"13215","5":"13215","creation_date":"1276922575","6":"1276922575"},{"0":"3108","vim_version":"7.0","1":"7.0","script_version":"0.6","2":"0.6","version_comment":"Added change font size functionality.","3":"Added change font size functionality.","package":"GuiBox.vba","4":"GuiBox.vba","src_id":"13209","5":"13209","creation_date":"1276801868","6":"1276801868"},{"0":"3108","vim_version":"6.0","1":"6.0","script_version":"0.5.1","2":"0.5.1","version_comment":"Added support for separators in the color\/font list.","3":"Added support for separators in the color\/font list.","package":"GuiBox.vba","4":"GuiBox.vba","src_id":"13102","5":"13102","creation_date":"1275600098","6":"1275600098"},{"0":"3108","vim_version":"6.0","1":"6.0","script_version":"0.5","2":"0.5","version_comment":"Initial upload","3":"Initial upload","package":"GuiBox.vba","4":"GuiBox.vba","src_id":"13095","5":"13095","creation_date":"1275528047","6":"1275528047"}]},"3107":{"script_id":"3107","0":"3107","script_name":"writebackupToAdjacentDir","1":"writebackupToAdjacentDir","script_type":"utility","2":"utility","summary":"Backup to an adjacent backup directory. ","3":"Backup to an adjacent backup directory. ","description":"Redirect backups made by the writebackup plugin (vimscript #1828) that would\r\nnormally go into the original file's directory into an adjacent directory with a\r\n\"{dir}.backup\" name, if it exists. This allows to use the plugin in places where\r\nbackup files would cause problems.\r\n\r\nDESCRIPTION\r\nMany customization directories (e.g. \/etc\/profile.d\/) consider all contained\r\nfiles, regardless of file extension or execute permissions. Creating a\r\n{file}.YYYYMMDD[a-z] backup in there causes trouble and strange effects,\r\nbecause the backups are used in addition to the main configuration file - not\r\nwhat was intended! However, putting the backups in the same directory\r\ngenerally is a good idea - just not for these special directories.\r\n\r\nThis plugin offers a solution by integrating into the writebackup.vim plugin\r\nso that it checks for a directory with a '.backup' extension (e.g.\r\n\/etc\/profile.d.backup\/), and places the backups in there, in case it exists.\r\nIn all other cases, the backup is made in the default directory, as before.\r\n\r\nUSAGE\r\nAdjacent backup directories are never created by this plugin; you have to\r\ncreate such a directory yourself to indicate that backups should be placed in\r\nthere.\r\n\r\n:WriteBackupMakeAdjacentDir [..\/..|\/path\/to\/dir] [{prot}]\r\n                Create a backup directory adjacent to the current file's\r\n                directory, or in a parent of that (\"..\", \"..\/..\", etc.), or of\r\n                any passed directory.\r\n                If {prot} is given it is used to set the protection bits;\r\n                default is 0755.\r\n\r\nAfter the adjacent backup directory has been created, just use :WriteBackup\r\nas before.","4":"Redirect backups made by the writebackup plugin (vimscript #1828) that would\r\nnormally go into the original file's directory into an adjacent directory with a\r\n\"{dir}.backup\" name, if it exists. This allows to use the plugin in places where\r\nbackup files would cause problems.\r\n\r\nDESCRIPTION\r\nMany customization directories (e.g. \/etc\/profile.d\/) consider all contained\r\nfiles, regardless of file extension or execute permissions. Creating a\r\n{file}.YYYYMMDD[a-z] backup in there causes trouble and strange effects,\r\nbecause the backups are used in addition to the main configuration file - not\r\nwhat was intended! However, putting the backups in the same directory\r\ngenerally is a good idea - just not for these special directories.\r\n\r\nThis plugin offers a solution by integrating into the writebackup.vim plugin\r\nso that it checks for a directory with a '.backup' extension (e.g.\r\n\/etc\/profile.d.backup\/), and places the backups in there, in case it exists.\r\nIn all other cases, the backup is made in the default directory, as before.\r\n\r\nUSAGE\r\nAdjacent backup directories are never created by this plugin; you have to\r\ncreate such a directory yourself to indicate that backups should be placed in\r\nthere.\r\n\r\n:WriteBackupMakeAdjacentDir [..\/..|\/path\/to\/dir] [{prot}]\r\n                Create a backup directory adjacent to the current file's\r\n                directory, or in a parent of that (\"..\", \"..\/..\", etc.), or of\r\n                any passed directory.\r\n                If {prot} is given it is used to set the protection bits;\r\n                default is 0755.\r\n\r\nAfter the adjacent backup directory has been created, just use :WriteBackup\r\nas before.","install_details":"INSTALLATION\r\nThis script is packaged as a vimball. If you have the \"gunzip\" decompressor\r\nin your PATH, simply edit the *.vmb.gz package in Vim; otherwise, decompress\r\nthe archive first, e.g. using WinZip. Inside Vim, install by sourcing the\r\nvimball or via the :UseVimball command.\r\n    vim writebackupToAdjacentDir*.vmb.gz\r\n    :so %\r\nTo uninstall, use the :RmVimball command.\r\n\r\nDEPENDENCIES\r\n- Requires Vim 7.0 or higher.\r\n- Requires the ingo-library.vim plugin (vimscript #4433), version 1.011 or\r\n  higher.\r\n- Requires the writebackup.vim plugin (vimscript #1828), version 1.30 or\r\n  higher.\r\n- The writebackupVersionControl.vim plugin (vimscript #1829), which\r\n  complements writebackup.vim, fully supports this extension, but is not\r\n  required.\r\n\r\nCONFIGURATION\r\nFor a permanent configuration, put the following commands into your vimrc:\r\n\r\nTo change the name of the adjacent backup directory, specify a different\r\ntemplate via\r\n    let g:WriteBackupAdjacentDir_BackupDirTemplate = '%s.backup'\r\nThis must contain the \"%s\" placeholder, which is replaced with the original\r\nfile's directory, e.g. \"backup of %s\".\r\n\r\nThis plugin injects itself into writebackup.vim via the\r\ng:WriteBackup_BackupDir configuration. Its previous value is saved in\r\ng:WriteBackupAdjacentDir_BackupDir and used as a fallback, when no adjacent\r\ndirectory exists. If you need to change the fallback after sourcing the\r\nplugins, use the latter variable. However, to override this for a particular\r\nbuffer, you still have to use the b:WriteBackup_BackupDir variable, as this\r\nplugin does not provide yet another override.\r\n\r\nBy default, the plugin also searches for backup directories in upper\r\ndirectories (until it reaches the file system root), and then re-creates the\r\npath to the current file inside that parallel backup directory hierarchy. If\r\nyou want to revert to the version 1.x behavior of the plugin, turn this off\r\nvia:\r\n    let g:WriteBackupAdjacentDir_IsUpwardsBackupDirSearch = 0","5":"INSTALLATION\r\nThis script is packaged as a vimball. If you have the \"gunzip\" decompressor\r\nin your PATH, simply edit the *.vmb.gz package in Vim; otherwise, decompress\r\nthe archive first, e.g. using WinZip. Inside Vim, install by sourcing the\r\nvimball or via the :UseVimball command.\r\n    vim writebackupToAdjacentDir*.vmb.gz\r\n    :so %\r\nTo uninstall, use the :RmVimball command.\r\n\r\nDEPENDENCIES\r\n- Requires Vim 7.0 or higher.\r\n- Requires the ingo-library.vim plugin (vimscript #4433), version 1.011 or\r\n  higher.\r\n- Requires the writebackup.vim plugin (vimscript #1828), version 1.30 or\r\n  higher.\r\n- The writebackupVersionControl.vim plugin (vimscript #1829), which\r\n  complements writebackup.vim, fully supports this extension, but is not\r\n  required.\r\n\r\nCONFIGURATION\r\nFor a permanent configuration, put the following commands into your vimrc:\r\n\r\nTo change the name of the adjacent backup directory, specify a different\r\ntemplate via\r\n    let g:WriteBackupAdjacentDir_BackupDirTemplate = '%s.backup'\r\nThis must contain the \"%s\" placeholder, which is replaced with the original\r\nfile's directory, e.g. \"backup of %s\".\r\n\r\nThis plugin injects itself into writebackup.vim via the\r\ng:WriteBackup_BackupDir configuration. Its previous value is saved in\r\ng:WriteBackupAdjacentDir_BackupDir and used as a fallback, when no adjacent\r\ndirectory exists. If you need to change the fallback after sourcing the\r\nplugins, use the latter variable. However, to override this for a particular\r\nbuffer, you still have to use the b:WriteBackup_BackupDir variable, as this\r\nplugin does not provide yet another override.\r\n\r\nBy default, the plugin also searches for backup directories in upper\r\ndirectories (until it reaches the file system root), and then re-creates the\r\npath to the current file inside that parallel backup directory hierarchy. If\r\nyou want to revert to the version 1.x behavior of the plugin, turn this off\r\nvia:\r\n    let g:WriteBackupAdjacentDir_IsUpwardsBackupDirSearch = 0","first_name":"Ingo","6":"Ingo","last_name":"Karkat","7":"Karkat","releases":[{"0":"3107","vim_version":"7.0","1":"7.0","script_version":"2.01","2":"2.01","version_comment":"- Compatibility: Fix Funcref errors for Vim 7.0\/1.","3":"- Compatibility: Fix Funcref errors for Vim 7.0\/1.","package":"writebackupToAdjacentDir-2.01.vmb.gz","4":"writebackupToAdjacentDir-2.01.vmb.gz","src_id":"21402","5":"21402","creation_date":"1391028300","6":"1391028300"},{"0":"3107","vim_version":"7.0","1":"7.0","script_version":"2.00","2":"2.00","version_comment":"- ENH: Implement upwards directory hierarchy search for backup directories, and then re-create the path to the current file inside that parallel backup directory hierarchy.\r\n- ENH: :WriteBackupMakeAdjacentDir now optionally also takes a target directory to better support the new upwards directory hierarchy search.\r\n- Abort :WriteBackupMakeAdjacentDir on error.\r\n- Add dependency to ingo-library (vimscript #4433). *** You need to separately install ingo-library (vimscript #4433) version 1.011 (or higher)! ***","3":"- ENH: Implement upwards directory hierarchy search for backup directories, and then re-create the path to the current file inside that parallel backup directory hierarchy.\r\n- ENH: :WriteBackupMakeAdjacentDir now optionally also takes a target directory to better support the new upwards directory hierarchy search.\r\n- Abort :WriteBackupMakeAdjacentDir on error.\r\n- Add dependency to ingo-library (vimscript #4433). *** You need to separately install ingo-library (vimscript #4433) version 1.011 (or higher)! ***","package":"writebackupToAdjacentDir-2.00.vmb.gz","4":"writebackupToAdjacentDir-2.00.vmb.gz","src_id":"20590","5":"20590","creation_date":"1375429507","6":"1375429507"},{"0":"3107","vim_version":"7.0","1":"7.0","script_version":"1.10","2":"1.10","version_comment":"ENH: Save configured g:WriteBackup_BackupDir and use that as a fallback instead of always defaulting to '.', thereby allowing absolute and dynamic backup directories as a fallback. Suggested by Geoffrey Nimal. ","3":"ENH: Save configured g:WriteBackup_BackupDir and use that as a fallback instead of always defaulting to '.', thereby allowing absolute and dynamic backup directories as a fallback. Suggested by Geoffrey Nimal. ","package":"writebackupToAdjacentDir.vba.gz","4":"writebackupToAdjacentDir.vba.gz","src_id":"17485","5":"17485","creation_date":"1329480110","6":"1329480110"},{"0":"3107","vim_version":"7.0","1":"7.0","script_version":"1.00","2":"1.00","version_comment":"Initial upload","3":"Initial upload","package":"writebackupToAdjacentDir.vba.gz","4":"writebackupToAdjacentDir.vba.gz","src_id":"13088","5":"13088","creation_date":"1275493026","6":"1275493026"}]},"3106":{"script_id":"3106","0":"3106","script_name":"truebasic.vim","1":"truebasic.vim","script_type":"syntax","2":"syntax","summary":"Syntax file for TrueBasic.","3":"Syntax file for TrueBasic.","description":"A simple syntax highlighter for the TrueBasic language.\r\nhttp:\/\/www.truebasic.com\/","4":"A simple syntax highlighter for the TrueBasic language.\r\nhttp:\/\/www.truebasic.com\/","install_details":"","5":"","first_name":"Tim","6":"Tim","last_name":"Swast","7":"Swast","releases":[{"0":"3106","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"truebasic.vim","4":"truebasic.vim","src_id":"13064","5":"13064","creation_date":"1275012153","6":"1275012153"}]},"3105":{"script_id":"3105","0":"3105","script_name":"legiblelight","1":"legiblelight","script_type":"color scheme","2":"color scheme","summary":"another light scheme, easier on eyes","3":"another light scheme, easier on eyes","description":"This is the other one I've been working on. It is a light colour scheme with more subdued colours to be easier on the eyes. (Or at least easier on my eyes.) \r\n\r\nWith 1.1.2, I have added the CTerm section into is so it is functional for the GUI and should be for the terminal as well.","4":"This is the other one I've been working on. It is a light colour scheme with more subdued colours to be easier on the eyes. (Or at least easier on my eyes.) \r\n\r\nWith 1.1.2, I have added the CTerm section into is so it is functional for the GUI and should be for the terminal as well.","install_details":"Copy to the normal directories either the \/vim72\/colors\/ or to \/.vim\/colors\/","5":"Copy to the normal directories either the \/vim72\/colors\/ or to \/.vim\/colors\/","first_name":"Tony","6":"Tony","last_name":"Dunsworth","7":"Dunsworth","releases":[{"0":"3105","vim_version":"7.0","1":"7.0","script_version":"1.1.2","2":"1.1.2","version_comment":"I have added in the CTerm colours for CTerm==8 and CTerm==256. Any feedback or questions\/requests\/etc would be appreciated. ","3":"I have added in the CTerm colours for CTerm==8 and CTerm==256. Any feedback or questions\/requests\/etc would be appreciated. ","package":"legiblelight.vim","4":"legiblelight.vim","src_id":"13099","5":"13099","creation_date":"1275575040","6":"1275575040"},{"0":"3105","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"legiblelight.vim","4":"legiblelight.vim","src_id":"13063","5":"13063","creation_date":"1274979115","6":"1274979115"}]},"3104":{"script_id":"3104","0":"3104","script_name":"pyref.vim","1":"pyref.vim","script_type":"utility","2":"utility","summary":"Context-sensitive documentation for Python source code","3":"Context-sensitive documentation for Python source code","description":"The file \"pyref.vim\" is a plug-in for the Vim text editor that maps the <F1> key in Python buffers to search through the Python language and library reference documentation for the keyword or identifier at the current cursor position and open the first match in your web browser. When no GUI is available a command-line web browser like lynx or w3m will be used, otherwise the plug-in prefers a graphical web browser like Mozilla Firefox or Google Chrome. For more information about the plug-in please refer to its homepage or the project page on GitHub:\r\n\r\n\u00e2\u0080\u00a2 http:\/\/peterodding.com\/code\/vim\/pyref\/\r\n\u00e2\u0080\u00a2 http:\/\/github.com\/xolox\/vim-pyref\r\n\r\nIf you have questions, bug reports, suggestions, etc. the author can be contacted at peter@peterodding.com. If you like this plug-in please vote for it below!\r\n\r\nALTERNATIVES\r\nIf you don't like using your web browser to read documentation but would rather do so inside Vim, or if you need the documentation of a module that's not in the Python standard library, try vimscript #910 and vimscript #1112. Both of these use the \"pydoc.py\" Python script included with the standard Python installation, which means they automatically work on all modules known to Python (including user-defined modules).","4":"The file \"pyref.vim\" is a plug-in for the Vim text editor that maps the <F1> key in Python buffers to search through the Python language and library reference documentation for the keyword or identifier at the current cursor position and open the first match in your web browser. When no GUI is available a command-line web browser like lynx or w3m will be used, otherwise the plug-in prefers a graphical web browser like Mozilla Firefox or Google Chrome. For more information about the plug-in please refer to its homepage or the project page on GitHub:\r\n\r\n\u00e2\u0080\u00a2 http:\/\/peterodding.com\/code\/vim\/pyref\/\r\n\u00e2\u0080\u00a2 http:\/\/github.com\/xolox\/vim-pyref\r\n\r\nIf you have questions, bug reports, suggestions, etc. the author can be contacted at peter@peterodding.com. If you like this plug-in please vote for it below!\r\n\r\nALTERNATIVES\r\nIf you don't like using your web browser to read documentation but would rather do so inside Vim, or if you need the documentation of a module that's not in the Python standard library, try vimscript #910 and vimscript #1112. Both of these use the \"pydoc.py\" Python script included with the standard Python installation, which means they automatically work on all modules known to Python (including user-defined modules).","install_details":"Unzip the most recent ZIP archive file (see below) inside your Vim profile directory (usually this is \"~\/.vim\" on UNIX and \"%USERPROFILE%\\vimfiles\" on Windows), restart Vim and execute the command \":helptags ~\/.vim\/doc\" (use \":helptags ~\\vimfiles\\doc\" instead on Windows). Now try it out: Open a Python script and press the <F1> key on any interesting identifier. If it doesn't work at first, please check the README included in the ZIP.","5":"Unzip the most recent ZIP archive file (see below) inside your Vim profile directory (usually this is \"~\/.vim\" on UNIX and \"%USERPROFILE%\\vimfiles\" on Windows), restart Vim and execute the command \":helptags ~\/.vim\/doc\" (use \":helptags ~\\vimfiles\\doc\" instead on Windows). Now try it out: Open a Python script and press the <F1> key on any interesting identifier. If it doesn't work at first, please check the README included in the ZIP.","first_name":"Peter","6":"Peter","last_name":"Odding","7":"Odding","releases":[{"0":"3104","vim_version":"7.0","1":"7.0","script_version":"0.7.16","2":"0.7.16","version_comment":" \u00e2\u0080\u00a2 Remove embedded miscellaneous scripts (they need to be installed separately from now on):\n   http:\/\/github.com\/xolox\/vim-pyref\/commit\/712b775\n\n \u00e2\u0080\u00a2 Document vim-misc as external dependency:\n   http:\/\/github.com\/xolox\/vim-pyref\/commit\/d57636a\n\n \u00e2\u0080\u00a2 Make sure vim-misc is installed, politely complain if it isn't:\n   http:\/\/github.com\/xolox\/vim-pyref\/commit\/75da45a\n\n \u00e2\u0080\u00a2 Remove vim-misc compatibility check (missed that):\n   http:\/\/github.com\/xolox\/vim-pyref\/commit\/a06070e","3":" \u00e2\u0080\u00a2 Remove embedded miscellaneous scripts (they need to be installed separately from now on):\n   http:\/\/github.com\/xolox\/vim-pyref\/commit\/712b775\n\n \u00e2\u0080\u00a2 Document vim-misc as external dependency:\n   http:\/\/github.com\/xolox\/vim-pyref\/commit\/d57636a\n\n \u00e2\u0080\u00a2 Make sure vim-misc is installed, politely complain if it isn't:\n   http:\/\/github.com\/xolox\/vim-pyref\/commit\/75da45a\n\n \u00e2\u0080\u00a2 Remove vim-misc compatibility check (missed that):\n   http:\/\/github.com\/xolox\/vim-pyref\/commit\/a06070e","package":"pyref.zip","4":"pyref.zip","src_id":"20688","5":"20688","creation_date":"1376950424","6":"1376950424"},{"0":"3104","vim_version":"7.0","1":"7.0","script_version":"0.7.14","2":"0.7.14","version_comment":" \u00e2\u0080\u00a2 Updated miscellaneous scripts:\n   http:\/\/github.com\/xolox\/vim-pyref\/commit\/bbdad43","3":" \u00e2\u0080\u00a2 Updated miscellaneous scripts:\n   http:\/\/github.com\/xolox\/vim-pyref\/commit\/bbdad43","package":"pyref.zip","4":"pyref.zip","src_id":"20182","5":"20182","creation_date":"1369054278","6":"1369054278"},{"0":"3104","vim_version":"7.0","1":"7.0","script_version":"0.7.13","2":"0.7.13","version_comment":" \u00e2\u0080\u00a2 Updated miscellaneous scripts:\n   http:\/\/github.com\/xolox\/vim-pyref\/commit\/7ef2448","3":" \u00e2\u0080\u00a2 Updated miscellaneous scripts:\n   http:\/\/github.com\/xolox\/vim-pyref\/commit\/7ef2448","package":"pyref.zip","4":"pyref.zip","src_id":"20170","5":"20170","creation_date":"1369003128","6":"1369003128"},{"0":"3104","vim_version":"7.0","1":"7.0","script_version":"0.7.12","2":"0.7.12","version_comment":" \u00e2\u0080\u00a2 Updated miscellaneous scripts:\n   http:\/\/github.com\/xolox\/vim-pyref\/commit\/21f503f\n   http:\/\/github.com\/xolox\/vim-pyref\/commit\/9c88b0e","3":" \u00e2\u0080\u00a2 Updated miscellaneous scripts:\n   http:\/\/github.com\/xolox\/vim-pyref\/commit\/21f503f\n   http:\/\/github.com\/xolox\/vim-pyref\/commit\/9c88b0e","package":"pyref.zip","4":"pyref.zip","src_id":"20124","5":"20124","creation_date":"1368481257","6":"1368481257"},{"0":"3104","vim_version":"7.0","1":"7.0","script_version":"0.7.11","2":"0.7.11","version_comment":" \u00e2\u0080\u00a2 Updated miscellaneous scripts:\n   http:\/\/github.com\/xolox\/vim-pyref\/commit\/35c639e","3":" \u00e2\u0080\u00a2 Updated miscellaneous scripts:\n   http:\/\/github.com\/xolox\/vim-pyref\/commit\/35c639e","package":"pyref.zip","4":"pyref.zip","src_id":"20007","5":"20007","creation_date":"1367487754","6":"1367487754"},{"0":"3104","vim_version":"7.0","1":"7.0","script_version":"0.7.10","2":"0.7.10","version_comment":" \u00e2\u0080\u00a2 Updated miscellaneous scripts:\n   http:\/\/github.com\/xolox\/vim-pyref\/commit\/87c783d","3":" \u00e2\u0080\u00a2 Updated miscellaneous scripts:\n   http:\/\/github.com\/xolox\/vim-pyref\/commit\/87c783d","package":"pyref.zip","4":"pyref.zip","src_id":"19959","5":"19959","creation_date":"1367159404","6":"1367159404"},{"0":"3104","vim_version":"7.0","1":"7.0","script_version":"0.7.9","2":"0.7.9","version_comment":" \u00e2\u0080\u00a2 Make compatibility with miscellaneous scripts explicit:\n   http:\/\/github.com\/xolox\/vim-pyref\/commit\/d486822","3":" \u00e2\u0080\u00a2 Make compatibility with miscellaneous scripts explicit:\n   http:\/\/github.com\/xolox\/vim-pyref\/commit\/d486822","package":"pyref.zip","4":"pyref.zip","src_id":"19874","5":"19874","creation_date":"1366503306","6":"1366503306"},{"0":"3104","vim_version":"7.0","1":"7.0","script_version":"0.7.8","2":"0.7.8","version_comment":" \u00e2\u0080\u00a2 Updated miscellaneous scripts:\n   http:\/\/github.com\/xolox\/vim-pyref\/commit\/11cba18\n   http:\/\/github.com\/xolox\/vim-pyref\/commit\/63289db\n   http:\/\/github.com\/xolox\/vim-pyref\/commit\/9b4c774","3":" \u00e2\u0080\u00a2 Updated miscellaneous scripts:\n   http:\/\/github.com\/xolox\/vim-pyref\/commit\/11cba18\n   http:\/\/github.com\/xolox\/vim-pyref\/commit\/63289db\n   http:\/\/github.com\/xolox\/vim-pyref\/commit\/9b4c774","package":"pyref.zip","4":"pyref.zip","src_id":"16971","5":"16971","creation_date":"1322268047","6":"1322268047"},{"0":"3104","vim_version":"7.0","1":"7.0","script_version":"0.7.7","2":"0.7.7","version_comment":" \u00e2\u0080\u00a2 Updated miscellaneous scripts:\n   http:\/\/github.com\/xolox\/vim-pyref\/commit\/ce002d6","3":" \u00e2\u0080\u00a2 Updated miscellaneous scripts:\n   http:\/\/github.com\/xolox\/vim-pyref\/commit\/ce002d6","package":"pyref.zip","4":"pyref.zip","src_id":"16927","5":"16927","creation_date":"1321911041","6":"1321911041"},{"0":"3104","vim_version":"7.0","1":"7.0","script_version":"0.7.6","2":"0.7.6","version_comment":" \u00e2\u0080\u00a2 Updated miscellaneous scripts:\n   http:\/\/github.com\/xolox\/vim-pyref\/commit\/927aeff","3":" \u00e2\u0080\u00a2 Updated miscellaneous scripts:\n   http:\/\/github.com\/xolox\/vim-pyref\/commit\/927aeff","package":"pyref.zip","4":"pyref.zip","src_id":"16581","5":"16581","creation_date":"1316994748","6":"1316994748"},{"0":"3104","vim_version":"7.0","1":"7.0","script_version":"0.7.5","2":"0.7.5","version_comment":" \u00e2\u0080\u00a2 Move the index (and spider) to the proper location:\n   http:\/\/github.com\/xolox\/vim-pyref\/commit\/42ad155\n\n \u00e2\u0080\u00a2 Define version as variable, include in messages:\n   http:\/\/github.com\/xolox\/vim-pyref\/commit\/42ed86b\n\n \u00e2\u0080\u00a2 Updated miscellaneous scripts","3":" \u00e2\u0080\u00a2 Move the index (and spider) to the proper location:\n   http:\/\/github.com\/xolox\/vim-pyref\/commit\/42ad155\n\n \u00e2\u0080\u00a2 Define version as variable, include in messages:\n   http:\/\/github.com\/xolox\/vim-pyref\/commit\/42ed86b\n\n \u00e2\u0080\u00a2 Updated miscellaneous scripts","package":"pyref.zip","4":"pyref.zip","src_id":"16459","5":"16459","creation_date":"1315145194","6":"1315145194"},{"0":"3104","vim_version":"7.0","1":"7.0","script_version":"0.7","2":"0.7","version_comment":"Now with out of the box support for Django documentation:\r\nhttps:\/\/github.com\/xolox\/vim-pyref\/commit\/2982ea5c73d78d7d2b39","3":"Now with out of the box support for Django documentation:\r\nhttps:\/\/github.com\/xolox\/vim-pyref\/commit\/2982ea5c73d78d7d2b39","package":"pyref.zip","4":"pyref.zip","src_id":"14576","5":"14576","creation_date":"1292763844","6":"1292763844"},{"0":"3104","vim_version":"7.0","1":"7.0","script_version":"0.6","2":"0.6","version_comment":" \u00e2\u0080\u00a2 Moved OpenBrowser() to external autoload plug-in:\r\n   http:\/\/github.com\/xolox\/vim-pyref\/commit\/b059112e6d111f84cb35\r\n\r\n \u00e2\u0080\u00a2 Added :PyRef command, converted to autoload script:\r\n   http:\/\/github.com\/xolox\/vim-pyref\/commit\/a37a24fe6630f40d7145","3":" \u00e2\u0080\u00a2 Moved OpenBrowser() to external autoload plug-in:\r\n   http:\/\/github.com\/xolox\/vim-pyref\/commit\/b059112e6d111f84cb35\r\n\r\n \u00e2\u0080\u00a2 Added :PyRef command, converted to autoload script:\r\n   http:\/\/github.com\/xolox\/vim-pyref\/commit\/a37a24fe6630f40d7145","package":"pyref.zip","4":"pyref.zip","src_id":"13858","5":"13858","creation_date":"1284845093","6":"1284845093"},{"0":"3104","vim_version":"7.0","1":"7.0","script_version":"0.5","2":"0.5","version_comment":" * Make all searches case-sensitive since Python is as well\r\n * Search for substring match on word boundaries\r\n * Progressively smaller suffix search now uses word boundary\r\n * If verbose is >= 1 pyref.vim reports used search patterns\r\n\r\nSee the changeset at http:\/\/github.com\/xolox\/vim-pyref\/commit\/175bf469a0c556f8596604892ce2c309f19582d7","3":" * Make all searches case-sensitive since Python is as well\r\n * Search for substring match on word boundaries\r\n * Progressively smaller suffix search now uses word boundary\r\n * If verbose is >= 1 pyref.vim reports used search patterns\r\n\r\nSee the changeset at http:\/\/github.com\/xolox\/vim-pyref\/commit\/175bf469a0c556f8596604892ce2c309f19582d7","package":"pyref.zip","4":"pyref.zip","src_id":"13143","5":"13143","creation_date":"1275960928","6":"1275960928"},{"0":"3104","vim_version":"7.0","1":"7.0","script_version":"0.4.2","2":"0.4.2","version_comment":"Fixed broken links in README\r\nhttp:\/\/github.com\/xolox\/vim-pyref\/commit\/5dd2e8b539d73a1c7dd01688bb6947f46a827396","3":"Fixed broken links in README\r\nhttp:\/\/github.com\/xolox\/vim-pyref\/commit\/5dd2e8b539d73a1c7dd01688bb6947f46a827396","package":"pyref.zip","4":"pyref.zip","src_id":"13135","5":"13135","creation_date":"1275835613","6":"1275835613"},{"0":"3104","vim_version":"7.0","1":"7.0","script_version":"0.4.1","2":"0.4.1","version_comment":"Includes generated Vim documentation based on README","3":"Includes generated Vim documentation based on README","package":"pyref.zip","4":"pyref.zip","src_id":"13121","5":"13121","creation_date":"1275796454","6":"1275796454"},{"0":"3104","vim_version":"7.0","1":"7.0","script_version":"0.4","2":"0.4","version_comment":"* Moved all remaining documentation from pyref.vim to README.md \r\n  http:\/\/github.com\/xolox\/vim-pyref\/commit\/218990f6c228ff0bcf2cd70e48cba5cc443da25d \r\n\r\n* Re-organized the plug-in to make it auto-update compatible (using the getscript plug-in). \r\n  This also simplifies installation: Just unzip the latest release inside your ~\/.vim\/ directory. \r\n  http:\/\/github.com\/xolox\/vim-pyref\/commit\/16ba180113f4c6c3eded4706fb319746dd9f7aae\r\n \r\n* Support for exceptions imported from the `exceptions` module","3":"* Moved all remaining documentation from pyref.vim to README.md \r\n  http:\/\/github.com\/xolox\/vim-pyref\/commit\/218990f6c228ff0bcf2cd70e48cba5cc443da25d \r\n\r\n* Re-organized the plug-in to make it auto-update compatible (using the getscript plug-in). \r\n  This also simplifies installation: Just unzip the latest release inside your ~\/.vim\/ directory. \r\n  http:\/\/github.com\/xolox\/vim-pyref\/commit\/16ba180113f4c6c3eded4706fb319746dd9f7aae\r\n \r\n* Support for exceptions imported from the `exceptions` module","package":"pyref.zip","4":"pyref.zip","src_id":"13104","5":"13104","creation_date":"1275607880","6":"1275607880"},{"0":"3104","vim_version":"7.0","1":"7.0","script_version":"0.3","2":"0.3","version_comment":"* Bug fix: Don't map insert mode when mapping is printable character\r\n  http:\/\/github.com\/xolox\/vim-pyref\/commit\/2d45371f62b9eb274b837ce084c1ad77710af713\r\n\r\n* Improved auto-detection of the appropriate browser (CLI vs. GUI)\r\n  http:\/\/github.com\/xolox\/vim-pyref\/commit\/dd6901c84f9e2b863d05963a2673b7f8b71adcd8\r\n\r\n* Resolve object attributes to standard library identifiers.\r\n  http:\/\/github.com\/xolox\/vim-pyref\/commit\/bf6751d5fb6a3e7f9babe114269a3de85be8d319\r\n\r\n* Included README.html for people who don't like Markdown :-)","3":"* Bug fix: Don't map insert mode when mapping is printable character\r\n  http:\/\/github.com\/xolox\/vim-pyref\/commit\/2d45371f62b9eb274b837ce084c1ad77710af713\r\n\r\n* Improved auto-detection of the appropriate browser (CLI vs. GUI)\r\n  http:\/\/github.com\/xolox\/vim-pyref\/commit\/dd6901c84f9e2b863d05963a2673b7f8b71adcd8\r\n\r\n* Resolve object attributes to standard library identifiers.\r\n  http:\/\/github.com\/xolox\/vim-pyref\/commit\/bf6751d5fb6a3e7f9babe114269a3de85be8d319\r\n\r\n* Included README.html for people who don't like Markdown :-)","package":"pyref.zip","4":"pyref.zip","src_id":"13098","5":"13098","creation_date":"1275568005","6":"1275568005"},{"0":"3104","vim_version":"7.0","1":"7.0","script_version":"0.2","2":"0.2","version_comment":"Initial upload","3":"Initial upload","package":"pyref.zip","4":"pyref.zip","src_id":"13060","5":"13060","creation_date":"1274904174","6":"1274904174"}]},"3103":{"script_id":"3103","0":"3103","script_name":"tony_light","1":"tony_light","script_type":"color scheme","2":"color scheme","summary":"Another Light Colour Scheme","3":"Another Light Colour Scheme","description":"I was frustrated by the light colour files available, so I've written two of my own. This one and another I'm still tweaking. Any comments and suggestions will be appreciated. ","4":"I was frustrated by the light colour files available, so I've written two of my own. This one and another I'm still tweaking. Any comments and suggestions will be appreciated. ","install_details":"Just copy over to the colors file","5":"Just copy over to the colors file","first_name":"Tony","6":"Tony","last_name":"Dunsworth","7":"Dunsworth","releases":[{"0":"3103","vim_version":"6.0","1":"6.0","script_version":"1.1","2":"1.1","version_comment":"Initial upload","3":"Initial upload","package":"tony_light.vim","4":"tony_light.vim","src_id":"13059","5":"13059","creation_date":"1274896452","6":"1274896452"}]},"3102":{"script_id":"3102","0":"3102","script_name":"vplinst","1":"vplinst","script_type":"utility","2":"utility","summary":"[yet another] Vim Plugin Installer","3":"[yet another] Vim Plugin Installer","description":"IMPORTANT: don't use vplinst. It is kept here for historical reasons, but there are much better plugin installers out there. Check Vundle (http:\/\/www.vim.org\/scripts\/script.php?script_id=3458), for instance.\r\n\r\n--\r\n\r\nVplinst stands for \"VIM plugin installer\" and is an attempt to make an automatic plugin installer for Vim. It installs scripts distributed in various different manners: vba (VimBall), tgz, .vim, .zip. You just configure the scripts you want in the vplinst.conf file, run the script and it will download and install them for you.\r\n\r\nThis utility consists in awk and sh scripts, that almost match POSIX and may run in any UNIX operating system with \/bin\/sh and awk.\r\n\r\nFork it on http:\/\/github.com\/silasdb\/vplinst\r\n\r\nPlease, communicate any problems and bugs you experienced.","4":"IMPORTANT: don't use vplinst. It is kept here for historical reasons, but there are much better plugin installers out there. Check Vundle (http:\/\/www.vim.org\/scripts\/script.php?script_id=3458), for instance.\r\n\r\n--\r\n\r\nVplinst stands for \"VIM plugin installer\" and is an attempt to make an automatic plugin installer for Vim. It installs scripts distributed in various different manners: vba (VimBall), tgz, .vim, .zip. You just configure the scripts you want in the vplinst.conf file, run the script and it will download and install them for you.\r\n\r\nThis utility consists in awk and sh scripts, that almost match POSIX and may run in any UNIX operating system with \/bin\/sh and awk.\r\n\r\nFork it on http:\/\/github.com\/silasdb\/vplinst\r\n\r\nPlease, communicate any problems and bugs you experienced.","install_details":"Just unpack it, cd the directory where the unpacked scripts belong to and run the vplinst.sh script. Configure the scripts you want in the vplinst.conf file. More information in the README.rst file.","5":"Just unpack it, cd the directory where the unpacked scripts belong to and run the vplinst.sh script. Configure the scripts you want in the vplinst.conf file. More information in the README.rst file.","first_name":"Silas","6":"Silas","last_name":"Silva","7":"Silva","releases":[{"0":"3102","vim_version":"7.0","1":"7.0","script_version":"1.1","2":"1.1","version_comment":"Changes from vplinst-1.0 to vplinst-1.1:\r\n\r\n    * Fixed bug: tar was not being executed for .tgz files.\r\n    * New TODO.rst file in the source distribution\r\n    * Added support for ftp - now supporting ftp and wget.\r\n    * Added the RELEASENOTES.rst file, with releasing information.","3":"Changes from vplinst-1.0 to vplinst-1.1:\r\n\r\n    * Fixed bug: tar was not being executed for .tgz files.\r\n    * New TODO.rst file in the source distribution\r\n    * Added support for ftp - now supporting ftp and wget.\r\n    * Added the RELEASENOTES.rst file, with releasing information.","package":"vplinst-1.1.tar.gz","4":"vplinst-1.1.tar.gz","src_id":"13263","5":"13263","creation_date":"1277781903","6":"1277781903"},{"0":"3102","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"vplinst-1.0.tar.gz","4":"vplinst-1.0.tar.gz","src_id":"13053","5":"13053","creation_date":"1274798038","6":"1274798038"}]},"3101":{"script_id":"3101","0":"3101","script_name":"Tumble","1":"Tumble","script_type":"utility","2":"utility","summary":"A plugin to post to the tumblr.vim microblogging service","3":"A plugin to post to the tumblr.vim microblogging service","description":"Tumble for vim\r\n==============\r\n\r\nThis script adds to vim the ability to send text entries to the tumblr.com\r\nblogging platform. It supports markdown formatting, and is able to edit and\r\ndelete previous entries.\r\n\r\nIn order to work, the variables\r\n\r\ntumblr_email\r\ntumblr_password\r\ntumblr_tumblelog\r\n\r\nmust be set. They are evaluated on every command, so you can change them on\r\nthe fly in case you need to switch to another blog.\r\n\r\ntumble.vim adds three commands to Vim:\r\n\r\n:Tumble\r\n:TumbleLink\r\n:ListTumbles\r\n\r\nThe syntax for :Tumble is\r\n\r\n:[range]Tumble [draft|publish]\r\n\r\nBy default, it posts the entire current buffer to tumblr.com, but a range can\r\nbe supplied if that isn't desired. For example, \":,Tumble\" would post the\r\ncurrent selection.\r\n\r\nUnless 'draft' (sans ') is given as an argument, it publishes the post\r\nimmediately. The default behaviour is equivalent to \":Tumble publish\". Any\r\nother argument could make the posting to fail. tumble.vim doesn't have safety\r\nmeasures against that currently.\r\n\r\nWhenever it can, tumble.vim tries to be smart. If it finds a first level setext\r\nstyle markdown title in the first lines of the buffer or range, it detects it\r\nas a title. If the title is found to be the same as the one from an earlier\r\npost, it overwrites it, instead of sending a new post.\r\n\r\nThe syntax for :TumbleLink is\r\n\r\n:[range]TumbleLink\r\n\r\nIt assumes the [range] is formatted thus:\r\n\r\nline\r\n1 URL\r\n2 NAME\r\n3... DESCRIPTION\r\n\r\nNAME and DESCRIPTION are optional, but NAME should always be on line 2 (so if you don't want to give a name to the link, you should keep this line blank).\r\n\r\nThe syntax for :ListTumbles is\r\n\r\n:ListTumbles draft|published\r\n\r\nIt prints a list of your published or drafting posts in the current buffer. If you\r\npress <enter> over a post line, tumble.vim will try to fetch the post and load it\r\nfor editing. If you press <delete>, it will delete the post.\r\n\r\nThe original version was based on Travis Jeffery's tumblr.vim\r\n(http:\/\/www.vim.org\/scripts\/script.php?script_id=2329), and the current version\r\ncontains some ideas from it.\r\n\r\nFelipe Morales\r\nhel.sheep@gmail.com","4":"Tumble for vim\r\n==============\r\n\r\nThis script adds to vim the ability to send text entries to the tumblr.com\r\nblogging platform. It supports markdown formatting, and is able to edit and\r\ndelete previous entries.\r\n\r\nIn order to work, the variables\r\n\r\ntumblr_email\r\ntumblr_password\r\ntumblr_tumblelog\r\n\r\nmust be set. They are evaluated on every command, so you can change them on\r\nthe fly in case you need to switch to another blog.\r\n\r\ntumble.vim adds three commands to Vim:\r\n\r\n:Tumble\r\n:TumbleLink\r\n:ListTumbles\r\n\r\nThe syntax for :Tumble is\r\n\r\n:[range]Tumble [draft|publish]\r\n\r\nBy default, it posts the entire current buffer to tumblr.com, but a range can\r\nbe supplied if that isn't desired. For example, \":,Tumble\" would post the\r\ncurrent selection.\r\n\r\nUnless 'draft' (sans ') is given as an argument, it publishes the post\r\nimmediately. The default behaviour is equivalent to \":Tumble publish\". Any\r\nother argument could make the posting to fail. tumble.vim doesn't have safety\r\nmeasures against that currently.\r\n\r\nWhenever it can, tumble.vim tries to be smart. If it finds a first level setext\r\nstyle markdown title in the first lines of the buffer or range, it detects it\r\nas a title. If the title is found to be the same as the one from an earlier\r\npost, it overwrites it, instead of sending a new post.\r\n\r\nThe syntax for :TumbleLink is\r\n\r\n:[range]TumbleLink\r\n\r\nIt assumes the [range] is formatted thus:\r\n\r\nline\r\n1 URL\r\n2 NAME\r\n3... DESCRIPTION\r\n\r\nNAME and DESCRIPTION are optional, but NAME should always be on line 2 (so if you don't want to give a name to the link, you should keep this line blank).\r\n\r\nThe syntax for :ListTumbles is\r\n\r\n:ListTumbles draft|published\r\n\r\nIt prints a list of your published or drafting posts in the current buffer. If you\r\npress <enter> over a post line, tumble.vim will try to fetch the post and load it\r\nfor editing. If you press <delete>, it will delete the post.\r\n\r\nThe original version was based on Travis Jeffery's tumblr.vim\r\n(http:\/\/www.vim.org\/scripts\/script.php?script_id=2329), and the current version\r\ncontains some ideas from it.\r\n\r\nFelipe Morales\r\nhel.sheep@gmail.com","install_details":"open the .vba file in vim and source it.\r\n\r\nYou must set the following variable (change as needed)\r\n\r\nlet tumblr_email = 'foo@bar.com\r\nlet tumblr_password = 'password'\r\nlet tumblr_tumblelog = 'myblog.tumblr.com'\r\n\r\nYou can change those on the run, so you can post to several blogs in the same session.","5":"open the .vba file in vim and source it.\r\n\r\nYou must set the following variable (change as needed)\r\n\r\nlet tumblr_email = 'foo@bar.com\r\nlet tumblr_password = 'password'\r\nlet tumblr_tumblelog = 'myblog.tumblr.com'\r\n\r\nYou can change those on the run, so you can post to several blogs in the same session.","first_name":"Felipe","6":"Felipe","last_name":"Morales","7":"Morales","releases":[{"0":"3101","vim_version":"7.2","1":"7.2","script_version":"11062010","2":"11062010","version_comment":"added autocompletion and proxy support (thanks to Aditya V. Mukherjee).","3":"added autocompletion and proxy support (thanks to Aditya V. Mukherjee).","package":"tumble.zip","4":"tumble.zip","src_id":"14197","5":"14197","creation_date":"1289071257","6":"1289071257"},{"0":"3101","vim_version":"7.2","1":"7.2","script_version":"24052010","2":"24052010","version_comment":"Initial upload","3":"Initial upload","package":"tumble.vba","4":"tumble.vba","src_id":"13052","5":"13052","creation_date":"1274728483","6":"1274728483"}]},"3100":{"script_id":"3100","0":"3100","script_name":"nevfn","1":"nevfn","script_type":"color scheme","2":"color scheme","summary":"Dark colorscheme based on desert","3":"Dark colorscheme based on desert","description":".","4":".","install_details":"","5":"","first_name":"Kana","6":"Kana","last_name":"Natsuno","7":"Natsuno","releases":[{"0":"3100","vim_version":"7.2","1":"7.2","script_version":"0.0.0","2":"0.0.0","version_comment":"Initial upload","3":"Initial upload","package":"nevfn.vim","4":"nevfn.vim","src_id":"13049","5":"13049","creation_date":"1274697405","6":"1274697405"}]},"3099":{"script_id":"3099","0":"3099","script_name":"mflrename","1":"mflrename","script_type":"utility","2":"utility","summary":"Multiple file rename","3":"Multiple file rename","description":"Small script to ease renaming a set of files\r\n\r\nThe idea is to make multiple file renaming as easy (and powerful) as editing a dump of file names. The script will just generate a script with the rename commands\r\n","4":"Small script to ease renaming a set of files\r\n\r\nThe idea is to make multiple file renaming as easy (and powerful) as editing a dump of file names. The script will just generate a script with the rename commands\r\n","install_details":"copy to your .vim\/plugin\/ folder and read instructions within the header","5":"copy to your .vim\/plugin\/ folder and read instructions within the header","first_name":"Francisco","6":"Francisco","last_name":"Garcia","7":"Garcia","releases":[{"0":"3099","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"mflrename.vim","4":"mflrename.vim","src_id":"13048","5":"13048","creation_date":"1274633271","6":"1274633271"}]},"3098":{"script_id":"3098","0":"3098","script_name":"PNote","1":"PNote","script_type":"utility","2":"utility","summary":"Power Notes","3":"Power Notes","description":"This tiny script provides the syntax, folding function and other minor functionality that I need for my notes.\r\n\r\nI try to keep al my notes in simple plain ASCII text files. However I admit that some formating and folding is nice. Hence I came up with a very simple syntax based on some markers and indentation rules, wrap all that together into this Vim script and Voil\u00c3\u00a0! Now I can keep my text notes within a compressed style and smart folding along the power of Vim to ease the access to my notes.\r\n\r\nYou can get a longer description and one screenshot at: \r\n\r\nhttps:\/\/github.com\/fgarcia\/pnote\r\n","4":"This tiny script provides the syntax, folding function and other minor functionality that I need for my notes.\r\n\r\nI try to keep al my notes in simple plain ASCII text files. However I admit that some formating and folding is nice. Hence I came up with a very simple syntax based on some markers and indentation rules, wrap all that together into this Vim script and Voil\u00c3\u00a0! Now I can keep my text notes within a compressed style and smart folding along the power of Vim to ease the access to my notes.\r\n\r\nYou can get a longer description and one screenshot at: \r\n\r\nhttps:\/\/github.com\/fgarcia\/pnote\r\n","install_details":"Install as usual. Download the latest version, open with vim and...\r\n     :so %\r\n\r\nMake sure you have somewhere in your Vimrc file the filetype plugin enabled: \r\n     :filetype plugin on","5":"Install as usual. Download the latest version, open with vim and...\r\n     :so %\r\n\r\nMake sure you have somewhere in your Vimrc file the filetype plugin enabled: \r\n     :filetype plugin on","first_name":"Francisco","6":"Francisco","last_name":"Garcia","7":"Garcia","releases":[{"0":"3098","vim_version":"7.0","1":"7.0","script_version":"0.2","2":"0.2","version_comment":"Syntax for bibliography nodes \r\nSyntax for command line instructions \r\nEasy copy to command line instructions to the system clipboard \r\nMinor bugfixes","3":"Syntax for bibliography nodes \r\nSyntax for command line instructions \r\nEasy copy to command line instructions to the system clipboard \r\nMinor bugfixes","package":"pnote.vba","4":"pnote.vba","src_id":"15258","5":"15258","creation_date":"1300630405","6":"1300630405"},{"0":"3098","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"pnote.vba","4":"pnote.vba","src_id":"13047","5":"13047","creation_date":"1274632788","6":"1274632788"}]},"3097":{"script_id":"3097","0":"3097","script_name":"Silence","1":"Silence","script_type":"color scheme","2":"color scheme","summary":"Light color scheme","3":"Light color scheme","description":"Continuation of the http:\/\/www.vim.org\/scripts\/script.php?script_id=2266 with some updates, \r\n\r\nsome screenshots :\r\n\r\n( html )  http:\/\/img192.imageshack.us\/img192\/1646\/screenhtml.png \r\n( php )  http:\/\/img706.imageshack.us\/img706\/1218\/silencek.png \r\n( C )     http:\/\/img295.imageshack.us\/img295\/1156\/screenc.png\r\nhttp:\/\/img405.imageshack.us\/my.php?image=c13rf1.png \r\nhttp:\/\/img210.imageshack.us\/my.php?image=c14lk3.png \r\n\r\nUpdates for constants, int, float types, boolean now have a light background. ","4":"Continuation of the http:\/\/www.vim.org\/scripts\/script.php?script_id=2266 with some updates, \r\n\r\nsome screenshots :\r\n\r\n( html )  http:\/\/img192.imageshack.us\/img192\/1646\/screenhtml.png \r\n( php )  http:\/\/img706.imageshack.us\/img706\/1218\/silencek.png \r\n( C )     http:\/\/img295.imageshack.us\/img295\/1156\/screenc.png\r\nhttp:\/\/img405.imageshack.us\/my.php?image=c13rf1.png \r\nhttp:\/\/img210.imageshack.us\/my.php?image=c14lk3.png \r\n\r\nUpdates for constants, int, float types, boolean now have a light background. ","install_details":"Put it into you $home\/.vim\/colors\/   directory  ","5":"Put it into you $home\/.vim\/colors\/   directory  ","first_name":"Vasilii","6":"Vasilii","last_name":"Pascal","7":"Pascal","releases":[{"0":"3097","vim_version":"6.0","1":"6.0","script_version":"1.4.3","2":"1.4.3","version_comment":"Initial upload","3":"Initial upload","package":"silent.vim","4":"silent.vim","src_id":"13042","5":"13042","creation_date":"1274477994","6":"1274477994"}]},"3096":{"script_id":"3096","0":"3096","script_name":"yaifa","1":"yaifa","script_type":"utility","2":"utility","summary":"Yet another indent finder, almost...","3":"Yet another indent finder, almost...","description":"This plug-in will try to detect the kind of indentation used in your file and\r\nset the indenting options to the appropriate values. It recognizes the\r\nfollowing types of indentation:\r\n\r\n1. Space: Only spaces are used to indent.\r\n2. Tab: Only tabs are used.\r\n3. Mixed: A combination of tabs and space is used. e.g.: a tab stands for 8\r\n    spaces, but each indentation level is 4 spaces.\r\n\r\nIn order to guess the indentation of the buffer, it looks for increments in\r\nthe indentation level and into the involved lines to see the type of\r\nindentation and the number of spaces of the change.  The type of indentation\r\nwith the most lines is used to set the options.\r\n\r\nIf Yaifa ever guesses wrong indentation, send me immediately a mail, if\r\npossible with the offending file, or open an issue on GitHub.\r\n\r\nThis script started as a port to VimL from Philippe Fremy's Python script\r\nIndent Finder (vimscript#513), hence the \"Almost\" part of the name.","4":"This plug-in will try to detect the kind of indentation used in your file and\r\nset the indenting options to the appropriate values. It recognizes the\r\nfollowing types of indentation:\r\n\r\n1. Space: Only spaces are used to indent.\r\n2. Tab: Only tabs are used.\r\n3. Mixed: A combination of tabs and space is used. e.g.: a tab stands for 8\r\n    spaces, but each indentation level is 4 spaces.\r\n\r\nIn order to guess the indentation of the buffer, it looks for increments in\r\nthe indentation level and into the involved lines to see the type of\r\nindentation and the number of spaces of the change.  The type of indentation\r\nwith the most lines is used to set the options.\r\n\r\nIf Yaifa ever guesses wrong indentation, send me immediately a mail, if\r\npossible with the offending file, or open an issue on GitHub.\r\n\r\nThis script started as a port to VimL from Philippe Fremy's Python script\r\nIndent Finder (vimscript#513), hence the \"Almost\" part of the name.","install_details":"Extract the files under ~\/.vim","5":"Extract the files under ~\/.vim","first_name":"Israel","6":"Israel","last_name":"Chauca Fuentes","7":"Chauca Fuentes","releases":[{"0":"3096","vim_version":"7.0","1":"7.0","script_version":"2.1","2":"2.1","version_comment":"Fix some logic and add support for NeoVim","3":"Fix some logic and add support for NeoVim","package":"yaifa.tar.gz","4":"yaifa.tar.gz","src_id":"26270","5":"26270","creation_date":"1541863005","6":"1541863005"},{"0":"3096","vim_version":"7.0","1":"7.0","script_version":"2.0","2":"2.0","version_comment":"- Script was rewritten and it is 67% faster than previous version and more accurate.\r\n- Added documentation.\r\n- Renamed :YAIFAMagic to :Yaifa\r\n- Added several configuration variables.","3":"- Script was rewritten and it is 67% faster than previous version and more accurate.\r\n- Added documentation.\r\n- Renamed :YAIFAMagic to :Yaifa\r\n- Added several configuration variables.","package":"yaifa.tar.gz","4":"yaifa.tar.gz","src_id":"26242","5":"26242","creation_date":"1539345507","6":"1539345507"},{"0":"3096","vim_version":"6.0","1":"6.0","script_version":"1.3","2":"1.3","version_comment":"- Add missing variable.\r\n- Stop defining all function on every run.","3":"- Add missing variable.\r\n- Stop defining all function on every run.","package":"yaifa.vim","4":"yaifa.vim","src_id":"13605","5":"13605","creation_date":"1282085088","6":"1282085088"},{"0":"3096","vim_version":"6.0","1":"6.0","script_version":"1.2","2":"1.2","version_comment":"- Reduce max number of lines to be scanned by default, it was set too high, which made the start-up slow.\r\n- Set 'tabstop' to 8 with 'expandtab'.\r\n- Use 'expandtab' and 'shiftwidth' to set default indenting values.","3":"- Reduce max number of lines to be scanned by default, it was set too high, which made the start-up slow.\r\n- Set 'tabstop' to 8 with 'expandtab'.\r\n- Use 'expandtab' and 'shiftwidth' to set default indenting values.","package":"yaifa.vim","4":"yaifa.vim","src_id":"13584","5":"13584","creation_date":"1281924178","6":"1281924178"},{"0":"3096","vim_version":"6.0","1":"6.0","script_version":"1.1","2":"1.1","version_comment":"- Float calculations eliminated for better compatibility.\r\n- Command added.","3":"- Float calculations eliminated for better compatibility.\r\n- Command added.","package":"yaifa.vim","4":"yaifa.vim","src_id":"13044","5":"13044","creation_date":"1274591288","6":"1274591288"},{"0":"3096","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"yaifa.vim","4":"yaifa.vim","src_id":"13031","5":"13031","creation_date":"1274344231","6":"1274344231"}]},"3095":{"script_id":"3095","0":"3095","script_name":"cvsdiff.vim","1":"cvsdiff.vim","script_type":"utility","2":"utility","summary":"visual 'cvs diff -r version' utility for vim diffsplit","3":"visual 'cvs diff -r version' utility for vim diffsplit","description":"This is a version of vimscript #1214 with full functionality: previously the version argument was mis-handled.","4":"This is a version of vimscript #1214 with full functionality: previously the version argument was mis-handled.","install_details":"See vimscript #1214.","5":"See vimscript #1214.","first_name":"Michael","6":"Michael","last_name":"McCutcheon","7":"McCutcheon","releases":[{"0":"3095","vim_version":"6.0","1":"6.0","script_version":"1.2","2":"1.2","version_comment":"Actually checked it works this time!","3":"Actually checked it works this time!","package":"cvsdiff.vim","4":"cvsdiff.vim","src_id":"13035","5":"13035","creation_date":"1274385466","6":"1274385466"},{"0":"3095","vim_version":"6.0","1":"6.0","script_version":"1.1","2":"1.1","version_comment":"Proper handling of a single argument: identifies 'v' as being a request for vertical split (not a version tag). ","3":"Proper handling of a single argument: identifies 'v' as being a request for vertical split (not a version tag). ","package":"cvsdiff.vim","4":"cvsdiff.vim","src_id":"13034","5":"13034","creation_date":"1274384122","6":"1274384122"},{"0":"3095","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"cvsdiff.vim","4":"cvsdiff.vim","src_id":"13028","5":"13028","creation_date":"1274299101","6":"1274299101"}]},"3094":{"script_id":"3094","0":"3094","script_name":"syntax-codecsconf","1":"syntax-codecsconf","script_type":"syntax","2":"syntax","summary":"syntax for mplayer-src codecs.conf","3":"syntax for mplayer-src codecs.conf","description":"This HELPFUL syntax definition makes your mplayer codecs.conf file shine.","4":"This HELPFUL syntax definition makes your mplayer codecs.conf file shine.","install_details":"Copy codecsconf.vim to vimruntime syntax\/ directory. set ft=codecsconf to see the effect or add:\r\n\r\nau BufRead,BufNewFile codecs.conf set ft=codecsconf\r\n\r\nto your vimrc file.","5":"Copy codecsconf.vim to vimruntime syntax\/ directory. set ft=codecsconf to see the effect or add:\r\n\r\nau BufRead,BufNewFile codecs.conf set ft=codecsconf\r\n\r\nto your vimrc file.","first_name":"umit","6":"umit","last_name":"kablan","7":"kablan","releases":[{"0":"3094","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"codecsconf.vim","4":"codecsconf.vim","src_id":"13022","5":"13022","creation_date":"1274110124","6":"1274110124"}]},"3093":{"script_id":"3093","0":"3093","script_name":"TortoiseTyping","1":"TortoiseTyping","script_type":"game","2":"game","summary":"a minimal typing tutor for touch-typists","3":"a minimal typing tutor for touch-typists","description":"-----------------------------------------------------------\r\n\r\nUpdate August 2, 2012: The latest version of this script is hosted at https:\/\/github.com\/thanthese\/Tortoise-Typing\r\n\r\n-----------------------------------------------------------\r\n\r\n\r\nContents:\r\n  1. Description\r\n  2. Quick Start\r\n  3. Advanced Options and Features\r\n  4. Licensing\r\n  5. Installation\r\n\r\n\r\n========================================\r\n1. Description\r\n\r\nTortoiseTyping is a minimal typing tutor aimed at touch-typists who would like to spend a few minutes a week sharpening their skills.\r\n\r\nThis script is called TortoiseTyping because with typing its slow, steady, and accurate wins the race.\r\n\r\nCompatible with Vim 7.2 and above.  Requires the Vim was compiled with the python switch, which will be true for almost all modern distributions.\r\n\r\n\r\n========================================\r\n2. Quick Start\r\n\r\nEscape ends the program.\r\n\r\nRun the :TutorialTyping command to start the two-minute tutorial.\r\n\r\nRun the :TortoiseTyping command to start the program with default settings: \"A Christmas Carol\" text, shuffled sentence order, and 150 word session.\r\n\r\nRun the :FileTyping <filepath> command to start like :TortoiseTyping, but with the file <filepath> of your choice.\r\n\r\n\r\n========================================\r\n3. Advanced Options and Features\r\n\r\nThe main screen has a progress bar showing percent completion through text.  (Use the tab key to toggle graphical\/fraction representation.)  Below that are words per minute and accuracy statistics.\r\n\r\nMain program options:\r\n- filepath: choose source file\r\n- randomize: whether or not to shuffle sentence order\r\n- wordcount: truncates source to wordcount number of words\r\n\r\nThe main entry point into the program is the python startTyping() function.  The :TortoiseTyping command calls it like this:\r\n\r\n  command! TortoiseTyping py startTyping(\r\n    \\ filepath=\"xmasCarol.txt\",\r\n    \\ randomize=True,\r\n    \\ wordCount=150)\r\n\r\nFeel free to use combinations of commands, mappings, and functions to customize how the program starts.\r\n\r\n\r\n========================================\r\n4. Licensing\r\n\r\nThis work is distributed as is, and I make no guarantee that it won't trash your system.  As always when trying new things, it makes good sense to save what you're working on first.\r\n\r\nFeel free to modify and distribute this script in any way, so long as you credit me and send me an email if you do anything cool with it.","4":"-----------------------------------------------------------\r\n\r\nUpdate August 2, 2012: The latest version of this script is hosted at https:\/\/github.com\/thanthese\/Tortoise-Typing\r\n\r\n-----------------------------------------------------------\r\n\r\n\r\nContents:\r\n  1. Description\r\n  2. Quick Start\r\n  3. Advanced Options and Features\r\n  4. Licensing\r\n  5. Installation\r\n\r\n\r\n========================================\r\n1. Description\r\n\r\nTortoiseTyping is a minimal typing tutor aimed at touch-typists who would like to spend a few minutes a week sharpening their skills.\r\n\r\nThis script is called TortoiseTyping because with typing its slow, steady, and accurate wins the race.\r\n\r\nCompatible with Vim 7.2 and above.  Requires the Vim was compiled with the python switch, which will be true for almost all modern distributions.\r\n\r\n\r\n========================================\r\n2. Quick Start\r\n\r\nEscape ends the program.\r\n\r\nRun the :TutorialTyping command to start the two-minute tutorial.\r\n\r\nRun the :TortoiseTyping command to start the program with default settings: \"A Christmas Carol\" text, shuffled sentence order, and 150 word session.\r\n\r\nRun the :FileTyping <filepath> command to start like :TortoiseTyping, but with the file <filepath> of your choice.\r\n\r\n\r\n========================================\r\n3. Advanced Options and Features\r\n\r\nThe main screen has a progress bar showing percent completion through text.  (Use the tab key to toggle graphical\/fraction representation.)  Below that are words per minute and accuracy statistics.\r\n\r\nMain program options:\r\n- filepath: choose source file\r\n- randomize: whether or not to shuffle sentence order\r\n- wordcount: truncates source to wordcount number of words\r\n\r\nThe main entry point into the program is the python startTyping() function.  The :TortoiseTyping command calls it like this:\r\n\r\n  command! TortoiseTyping py startTyping(\r\n    \\ filepath=\"xmasCarol.txt\",\r\n    \\ randomize=True,\r\n    \\ wordCount=150)\r\n\r\nFeel free to use combinations of commands, mappings, and functions to customize how the program starts.\r\n\r\n\r\n========================================\r\n4. Licensing\r\n\r\nThis work is distributed as is, and I make no guarantee that it won't trash your system.  As always when trying new things, it makes good sense to save what you're working on first.\r\n\r\nFeel free to modify and distribute this script in any way, so long as you credit me and send me an email if you do anything cool with it.","install_details":"Unzip tortoiseTyping.zip into ~\/.vim\/plugin\/ and (re)start vim.\r\n\r\nThis command\r\n\r\n  ls ~\/.vim\/plugin\/tortoiseTyping\/\r\n\r\nshould yield this:\r\n\r\n  README.txt\r\n  tortoiseTyping.vim\r\n  xmasCarol.txt","5":"Unzip tortoiseTyping.zip into ~\/.vim\/plugin\/ and (re)start vim.\r\n\r\nThis command\r\n\r\n  ls ~\/.vim\/plugin\/tortoiseTyping\/\r\n\r\nshould yield this:\r\n\r\n  README.txt\r\n  tortoiseTyping.vim\r\n  xmasCarol.txt","first_name":"Stephen","6":"Stephen","last_name":"Mann","7":"Mann","releases":[{"0":"3093","vim_version":"7.0","1":"7.0","script_version":"2.0","2":"2.0","version_comment":"Uploaded correct .zip file.  Runs on vim 7.2 and above.","3":"Uploaded correct .zip file.  Runs on vim 7.2 and above.","package":"tortoiseTyping.zip","4":"tortoiseTyping.zip","src_id":"13012","5":"13012","creation_date":"1273961512","6":"1273961512"}]},"3092":{"script_id":"3092","0":"3092","script_name":"autocomp.vim","1":"autocomp.vim","script_type":"utility","2":"utility","summary":"Auto-complete VIM script tailored for those with RSI","3":"Auto-complete VIM script tailored for those with RSI","description":"The purpose of this script is to allow the user to auto-complete a word without having to first press a key combination to open up the list of options, and then have to press more keys (usually the arrow keys) until you get to the word you want to type. With this script, you type a letter or two, and then the number that represents the word that you want to type. The idea is to have the user press as few keys as possible for an auto-completion.\r\n\r\nThis script is made for people who cannot type as much as they used to anymore. It will probably slow you down somewhat initially, but if you're looking for this script, you're probably not worried about speed.\r\nUntil someone figures out how to connect speech recognition to VIM in a useful way, this may help.  :-)\r\n\r\nDocumentation and usage instructions are in the file autocomp.vim.","4":"The purpose of this script is to allow the user to auto-complete a word without having to first press a key combination to open up the list of options, and then have to press more keys (usually the arrow keys) until you get to the word you want to type. With this script, you type a letter or two, and then the number that represents the word that you want to type. The idea is to have the user press as few keys as possible for an auto-completion.\r\n\r\nThis script is made for people who cannot type as much as they used to anymore. It will probably slow you down somewhat initially, but if you're looking for this script, you're probably not worried about speed.\r\nUntil someone figures out how to connect speech recognition to VIM in a useful way, this may help.  :-)\r\n\r\nDocumentation and usage instructions are in the file autocomp.vim.","install_details":"Copy autocomp.vim to the VIM plugin's directory.\r\nOn Windows, this would be: ...\\vimfiles\\plugin\\.\r\nOn Linux: ~\/.vim\/plugin\/.\r\n\r\nUse the F5 key to open the auto-complete window.\r\nYou can customize the key using something like the following in your VIM rc file:\r\nnmap <unique> <...> <Plug>AutocompStart\r\n\r\nAlso available at:\r\nhttp:\/\/github.com\/andre-luiz-dos-santos\/autocomp","5":"Copy autocomp.vim to the VIM plugin's directory.\r\nOn Windows, this would be: ...\\vimfiles\\plugin\\.\r\nOn Linux: ~\/.vim\/plugin\/.\r\n\r\nUse the F5 key to open the auto-complete window.\r\nYou can customize the key using something like the following in your VIM rc file:\r\nnmap <unique> <...> <Plug>AutocompStart\r\n\r\nAlso available at:\r\nhttp:\/\/github.com\/andre-luiz-dos-santos\/autocomp","first_name":"Andr\u00c3\u00a9","6":"Andr\u00c3\u00a9","last_name":"dos Santos","7":"dos Santos","releases":[{"0":"3092","vim_version":"7.0","1":"7.0","script_version":"1.1.1","2":"1.1.1","version_comment":"Minor bug fix.","3":"Minor bug fix.","package":"autocomp.vim","4":"autocomp.vim","src_id":"14209","5":"14209","creation_date":"1289255345","6":"1289255345"},{"0":"3092","vim_version":"7.0","1":"7.0","script_version":"1.1","2":"1.1","version_comment":"Smarter auto-complete buffer.\r\nMoved auto-complete window to the left.","3":"Smarter auto-complete buffer.\r\nMoved auto-complete window to the left.","package":"autocomp.vim","4":"autocomp.vim","src_id":"14119","5":"14119","creation_date":"1288025818","6":"1288025818"},{"0":"3092","vim_version":"7.0","1":"7.0","script_version":"1.0.1","2":"1.0.1","version_comment":"The previous version didn't work on Linux because the file was saved with Windows line endings. Switched to UNIX line endings.","3":"The previous version didn't work on Linux because the file was saved with Windows line endings. Switched to UNIX line endings.","package":"autocomp.vim","4":"autocomp.vim","src_id":"13016","5":"13016","creation_date":"1274033820","6":"1274033820"},{"0":"3092","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"autocomp.vim","4":"autocomp.vim","src_id":"13010","5":"13010","creation_date":"1273958303","6":"1273958303"}]},"3091":{"script_id":"3091","0":"3091","script_name":"Sessions","1":"Sessions","script_type":"utility","2":"utility","summary":"Vim-Sessions is an automatic session generator, per project basis","3":"Vim-Sessions is an automatic session generator, per project basis","description":"Vim-Sessions is an automatic session generator, per project (aka directory) basis, for Vim editor.\r\n\r\nMore information, please visit the repository http:\/\/github.com\/edsono\/vim-sessions.","4":"Vim-Sessions is an automatic session generator, per project (aka directory) basis, for Vim editor.\r\n\r\nMore information, please visit the repository http:\/\/github.com\/edsono\/vim-sessions.","install_details":"For install, just download the .vba.gz file and run vim sessions-<version>.vba.gz +\":source %\".\r\n","5":"For install, just download the .vba.gz file and run vim sessions-<version>.vba.gz +\":source %\".\r\n","first_name":"Hallison","6":"Hallison","last_name":"Batista","7":"Batista","releases":[{"0":"3091","vim_version":"6.0","1":"6.0","script_version":"1.0.0","2":"1.0.0","version_comment":"This is the first stable release version.\r\n\r\n* Removed all echomsg in comments.\r\n* All function names have been renamed with plugin name in prefix.\r\n* Several improvements in source code.\r\n","3":"This is the first stable release version.\r\n\r\n* Removed all echomsg in comments.\r\n* All function names have been renamed with plugin name in prefix.\r\n* Several improvements in source code.\r\n","package":"sessions-1.0.0.vba.gz","4":"sessions-1.0.0.vba.gz","src_id":"13272","5":"13272","creation_date":"1277922406","6":"1277922406"},{"0":"3091","vim_version":"6.0","1":"6.0","script_version":"0.1.3","2":"0.1.3","version_comment":"* Added messages in history.\r\n* Improvements in project search path.\r\n* improvements in session load\/save file.\r\n* Several improvements in source code.","3":"* Added messages in history.\r\n* Improvements in project search path.\r\n* improvements in session load\/save file.\r\n* Several improvements in source code.","package":"sessions-0.1.3.vba.gz","4":"sessions-0.1.3.vba.gz","src_id":"13007","5":"13007","creation_date":"1273879553","6":"1273879553"},{"0":"3091","vim_version":"6.0","1":"6.0","script_version":"0.1.2","2":"0.1.2","version_comment":"* Fixes in checking project directory","3":"* Fixes in checking project directory","package":"sessions-0.1.2.vba.gz","4":"sessions-0.1.2.vba.gz","src_id":"12997","5":"12997","creation_date":"1273702702","6":"1273702702"},{"0":"3091","vim_version":"6.0","1":"6.0","script_version":"0.1.1","2":"0.1.1","version_comment":"* Added support to multiple code paths.\r\n* Added bake tasks.","3":"* Added support to multiple code paths.\r\n* Added bake tasks.","package":"sessions-0.1.1.vba.gz","4":"sessions-0.1.1.vba.gz","src_id":"12996","5":"12996","creation_date":"1273689986","6":"1273689986"},{"0":"3091","vim_version":"6.0","1":"6.0","script_version":"0.1.0","2":"0.1.0","version_comment":"Initial upload","3":"Initial upload","package":"sessions-0.1.0.vba.gz","4":"sessions-0.1.0.vba.gz","src_id":"12994","5":"12994","creation_date":"1273678042","6":"1273678042"}]},"3090":{"script_id":"3090","0":"3090","script_name":"RTL","1":"RTL","script_type":"color scheme","2":"color scheme","summary":"Color highlighting for gcc rtl dumps","3":"Color highlighting for gcc rtl dumps","description":"This plugin is the syntax file for rtl gcc dump which is useful for gcc debugging.","4":"This plugin is the syntax file for rtl gcc dump which is useful for gcc debugging.","install_details":"1. Copy rtl.vim in your .vim\/syntax directory\r\n2. If you want Vim to detect the filetype, add to $VIM\/filetype.vim:\r\nau BufNewFile,BufRead *.c.* \tsetf rtl\r\n","5":"1. Copy rtl.vim in your .vim\/syntax directory\r\n2. If you want Vim to detect the filetype, add to $VIM\/filetype.vim:\r\nau BufNewFile,BufRead *.c.* \tsetf rtl\r\n","first_name":"Igor","6":"Igor","last_name":"Petushkov","7":"Petushkov","releases":[{"0":"3090","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"rtl.vim","4":"rtl.vim","src_id":"12992","5":"12992","creation_date":"1273672781","6":"1273672781"}]},"3089":{"script_id":"3089","0":"3089","script_name":"vimtl","1":"vimtl","script_type":"syntax","2":"syntax","summary":"Allow to handle todo lists","3":"Allow to handle todo lists","description":"Keyboard shotcuts\r\n=================\r\n\r\n,c\r\n    Create a task.\r\n,s\r\n    Create a subtask\r\n,d\r\n    Mark Done\r\n,r\r\n    Mark as cancel\r\n,1\r\n    Convert to OTL style\r\n,2\r\n    Convert to litle box style\r\n,3\r\n    Convert to single sytyle\r\n","4":"Keyboard shotcuts\r\n=================\r\n\r\n,c\r\n    Create a task.\r\n,s\r\n    Create a subtask\r\n,d\r\n    Mark Done\r\n,r\r\n    Mark as cancel\r\n,1\r\n    Convert to OTL style\r\n,2\r\n    Convert to litle box style\r\n,3\r\n    Convert to single sytyle\r\n","install_details":"cd ~\/.vim\r\ntar xzf vimtl.tar.gz\r\n\r\nThen, open a new file and run the command:\r\n\r\n     :call Loadvimtl()\r\n\r\nOr set a common file extension like .otl o .tl:\r\n\r\n     autocmd BufWinEnter *.otl call Loadvimtl()\r\n     autocmd BufWinEnter *.tl call Loadvimtl()\r\n","5":"cd ~\/.vim\r\ntar xzf vimtl.tar.gz\r\n\r\nThen, open a new file and run the command:\r\n\r\n     :call Loadvimtl()\r\n\r\nOr set a common file extension like .otl o .tl:\r\n\r\n     autocmd BufWinEnter *.otl call Loadvimtl()\r\n     autocmd BufWinEnter *.tl call Loadvimtl()\r\n","first_name":"Hugo","6":"Hugo","last_name":"Ruscitti","7":"Ruscitti","releases":[{"0":"3089","vim_version":"7.0","1":"7.0","script_version":"0.22","2":"0.22","version_comment":"Add new mark style and mapping ',1' ',2' and ',3' in insert mode.","3":"Add new mark style and mapping ',1' ',2' and ',3' in insert mode.","package":"vimtl.tar.gz","4":"vimtl.tar.gz","src_id":"13002","5":"13002","creation_date":"1273778628","6":"1273778628"},{"0":"3089","vim_version":"6.0","1":"6.0","script_version":"0.2","2":"0.2","version_comment":"add new command \"Loadvimtl\"","3":"add new command \"Loadvimtl\"","package":"vimtl_02.tar.gz","4":"vimtl_02.tar.gz","src_id":"12998","5":"12998","creation_date":"1273720809","6":"1273720809"},{"0":"3089","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"vimtl.tar.gz","4":"vimtl.tar.gz","src_id":"12982","5":"12982","creation_date":"1273445113","6":"1273445113"}]},"3088":{"script_id":"3088","0":"3088","script_name":"GetFile","1":"GetFile","script_type":"utility","2":"utility","summary":"Select and Open a File by typing part of its path.","3":"Select and Open a File by typing part of its path.","description":"This script  caches the content of a part of the filesystem and help retrieves the appropriate file based on a pattern.\r\nIt has been heavily inspired by the FindFile plugin. However, this plugin is not limited to filename patterns only as you can type any part of a file path (thus including folders).\r\nThe plugin also comes with some options that allow faster search like automatic search 'completion' of folders, case sensitivity, ...\r\nThe pattern supports wildcards (* \/ ?).\r\n \r\nIt is a 2 step process to use:\r\n    1. cache the files\r\n    2. search through them\r\n\r\nThis is my first vim script so feel free to give me advices :)\r\n\r\nHere is the documentation that you can find inside the script header:\r\n\r\n               You can use the following functions:\r\n\r\n                 \":GetFileCacheFiles <path>\" - Caches the files. Has to be called at least once before a call to \":GetFile\".\r\n                 \":GetFileClearCache\" - Clear the cache.\r\n                 \":GetFile\" - Start searching for a file.\r\n\r\n               You may want to add the following lines in your ~\/.vimrc file:\r\n               (or whatever shortcut you find suitable)\r\n\r\n               \"nmap <silent> <unique> fc :GetFileCacheFiles .<CR>\"\r\n               \"nmap <silent> <unique> ff :GetFile<CR>\"\r\n\r\n               Once in the \"[GetFile]\" buffer:\r\n                 \r\n                 Use \"<Up>\" \/ \"<C-p>\" and \"<Down>\" \/ \"<C-n>\" to select a file. \r\n                 \"<CR>\" opens the selected file. (If no selection done, it opens the first file).\r\n                 \"<ESC>\" exits the buffer.\r\n\r\n               Supported Options that you can specify in your .vimrc file:\r\n\r\n                   \"g:GetFileIgnoreList\" \r\n                       List of patterns to ignore.\r\n                       Default = ['*.o', '*.pyc', '*\/tmp\/*', '*~', '*\/.svn\/*', '*#']\r\n\r\n                   \"g:GetFileIgnoreCase\"\r\n                       Do not take case into account when searching files.\r\n                       Default = 0\r\n\r\n                   \"g:GetFileAutoFillFolder\"\r\n                       Speeds up the search when searching through folders as\r\n                       typing '\/' is equivalent to typing '*\/'.\r\n                       There are 3 possible values:\r\n                           0: do not use this option\r\n                           1: auto complete the current folder only. (match till\r\n                           the next '\/' only)\r\n                           2: auto complete the entire sub hierarchy. (match\r\n                           till the last possible '\/')\r\n                       Default = 1\r\n\r\n               Example of how to set an option in you .vimrc file:\r\n               \r\n                   \"let g:GetFileAutoFillFolder = 2\"\r\n","4":"This script  caches the content of a part of the filesystem and help retrieves the appropriate file based on a pattern.\r\nIt has been heavily inspired by the FindFile plugin. However, this plugin is not limited to filename patterns only as you can type any part of a file path (thus including folders).\r\nThe plugin also comes with some options that allow faster search like automatic search 'completion' of folders, case sensitivity, ...\r\nThe pattern supports wildcards (* \/ ?).\r\n \r\nIt is a 2 step process to use:\r\n    1. cache the files\r\n    2. search through them\r\n\r\nThis is my first vim script so feel free to give me advices :)\r\n\r\nHere is the documentation that you can find inside the script header:\r\n\r\n               You can use the following functions:\r\n\r\n                 \":GetFileCacheFiles <path>\" - Caches the files. Has to be called at least once before a call to \":GetFile\".\r\n                 \":GetFileClearCache\" - Clear the cache.\r\n                 \":GetFile\" - Start searching for a file.\r\n\r\n               You may want to add the following lines in your ~\/.vimrc file:\r\n               (or whatever shortcut you find suitable)\r\n\r\n               \"nmap <silent> <unique> fc :GetFileCacheFiles .<CR>\"\r\n               \"nmap <silent> <unique> ff :GetFile<CR>\"\r\n\r\n               Once in the \"[GetFile]\" buffer:\r\n                 \r\n                 Use \"<Up>\" \/ \"<C-p>\" and \"<Down>\" \/ \"<C-n>\" to select a file. \r\n                 \"<CR>\" opens the selected file. (If no selection done, it opens the first file).\r\n                 \"<ESC>\" exits the buffer.\r\n\r\n               Supported Options that you can specify in your .vimrc file:\r\n\r\n                   \"g:GetFileIgnoreList\" \r\n                       List of patterns to ignore.\r\n                       Default = ['*.o', '*.pyc', '*\/tmp\/*', '*~', '*\/.svn\/*', '*#']\r\n\r\n                   \"g:GetFileIgnoreCase\"\r\n                       Do not take case into account when searching files.\r\n                       Default = 0\r\n\r\n                   \"g:GetFileAutoFillFolder\"\r\n                       Speeds up the search when searching through folders as\r\n                       typing '\/' is equivalent to typing '*\/'.\r\n                       There are 3 possible values:\r\n                           0: do not use this option\r\n                           1: auto complete the current folder only. (match till\r\n                           the next '\/' only)\r\n                           2: auto complete the entire sub hierarchy. (match\r\n                           till the last possible '\/')\r\n                       Default = 1\r\n\r\n               Example of how to set an option in you .vimrc file:\r\n               \r\n                   \"let g:GetFileAutoFillFolder = 2\"\r\n","install_details":"","5":"","first_name":"Romain","6":"Romain","last_name":"Maurer","7":"Maurer","releases":[{"0":"3088","vim_version":"7.0","1":"7.0","script_version":"1.0.3","2":"1.0.3","version_comment":"Initial upload","3":"Initial upload","package":"getfile.vim","4":"getfile.vim","src_id":"12967","5":"12967","creation_date":"1273205768","6":"1273205768"}]},"3087":{"script_id":"3087","0":"3087","script_name":"OutlookVim","1":"OutlookVim","script_type":"utility","2":"utility","summary":"Use Vim to edit the body of an email for Microsoft Outlook","3":"Use Vim to edit the body of an email for Microsoft Outlook","description":"For Windows users, this plugin will allow you to add a button in Microsoft Outlook which will create a new buffer in Vim with the body of the current email.  The buffer can be edited in:\r\n    1.  Any instance of a running Vim (multiple buffers).\r\n    2.  A specific instance of Vim (if you like to group your Vim's by project).\r\n    3.  Whether to use a new tab (for each mail).\r\n\r\nThere are many ways to customize OutlookVim so that it will fit how you use Vim.  Besides the 3 basics above, you can also control which commands Vim uses to edit the mail to complete customization.\r\n\r\nYou can also add 4 more buttons to Outlook's Inbox view, to Compose, Reply, ReplyAll or Forward any highlighted messages in the Inbox.\r\n\r\nThe filetype of the buffer is automatically set to \"mail\".  This allows you to use all of Vim's great plugins and editing features to alter the email and customize the buffer using Vim's standard filetype support.  When finished, simply saving the file will automatically update the body of the email in Microsoft Outlook.\r\n\r\nYou can also also edit HTML emails, though this is disabled by default.  See :h outlook.txt and look for the option g:outlook_supported_body_format.\r\n\r\nYou can send any buffer you are currently editing in Vim into a new Outlook email by running the command:\r\n:OutlookNewEmail\r\n\r\n\r\nThis has been tested with:\r\n    Outlook 2003 (WinXP SP3) \r\n    Outlook 2007 (Windows 7 64bit and 32bit)\r\n    Outlook 2010 (Windows 7 64bit and 32bit)\r\n\r\nThere are a number of preferences you can set within the plugin to customize it for your use.  \r\nThese settings can be explored here:\r\n    :h outlook-configuration\r\n    :h outlook.txt\r\n\r\nInstallation instructions for Outlook can be found here:\r\n    :h outlook-macro\r\n    :h outlook.txt\r\n\r\nNOTE:  All code is included in these files.  There are no executable files you need to run on your system.   For those interested, the documentation outlines how Vim and Outlook communicate with each other.\r\n\r\nIf your Vim is Unicode enabled (:set encoding? fileencodings?), you will be able to edit emails which contain Unicode characters.  \r\n    :h outlook-Unicode\r\n\r\nPlease use the vim_use group to post comments and suggestions.\r\n\r\n\r\n","4":"For Windows users, this plugin will allow you to add a button in Microsoft Outlook which will create a new buffer in Vim with the body of the current email.  The buffer can be edited in:\r\n    1.  Any instance of a running Vim (multiple buffers).\r\n    2.  A specific instance of Vim (if you like to group your Vim's by project).\r\n    3.  Whether to use a new tab (for each mail).\r\n\r\nThere are many ways to customize OutlookVim so that it will fit how you use Vim.  Besides the 3 basics above, you can also control which commands Vim uses to edit the mail to complete customization.\r\n\r\nYou can also add 4 more buttons to Outlook's Inbox view, to Compose, Reply, ReplyAll or Forward any highlighted messages in the Inbox.\r\n\r\nThe filetype of the buffer is automatically set to \"mail\".  This allows you to use all of Vim's great plugins and editing features to alter the email and customize the buffer using Vim's standard filetype support.  When finished, simply saving the file will automatically update the body of the email in Microsoft Outlook.\r\n\r\nYou can also also edit HTML emails, though this is disabled by default.  See :h outlook.txt and look for the option g:outlook_supported_body_format.\r\n\r\nYou can send any buffer you are currently editing in Vim into a new Outlook email by running the command:\r\n:OutlookNewEmail\r\n\r\n\r\nThis has been tested with:\r\n    Outlook 2003 (WinXP SP3) \r\n    Outlook 2007 (Windows 7 64bit and 32bit)\r\n    Outlook 2010 (Windows 7 64bit and 32bit)\r\n\r\nThere are a number of preferences you can set within the plugin to customize it for your use.  \r\nThese settings can be explored here:\r\n    :h outlook-configuration\r\n    :h outlook.txt\r\n\r\nInstallation instructions for Outlook can be found here:\r\n    :h outlook-macro\r\n    :h outlook.txt\r\n\r\nNOTE:  All code is included in these files.  There are no executable files you need to run on your system.   For those interested, the documentation outlines how Vim and Outlook communicate with each other.\r\n\r\nIf your Vim is Unicode enabled (:set encoding? fileencodings?), you will be able to edit emails which contain Unicode characters.  \r\n    :h outlook-Unicode\r\n\r\nPlease use the vim_use group to post comments and suggestions.\r\n\r\n\r\n","install_details":"Unzip outlookvim_vXXX.zip into your $VIM\/vimfiles directory.  \r\n\r\nTo update the Vim Help, run:\r\n:helptags $VIM\/vimfiles\/doc  (Windows) \r\n\r\nThe help contains two pieces of important information:\r\n:h outlookvim\r\n\r\n1.  How to install two buttons in Outlook to launch Vim\r\n2.  How to configure your Vim plugin to your file locations and your preferences.\r\n","5":"Unzip outlookvim_vXXX.zip into your $VIM\/vimfiles directory.  \r\n\r\nTo update the Vim Help, run:\r\n:helptags $VIM\/vimfiles\/doc  (Windows) \r\n\r\nThe help contains two pieces of important information:\r\n:h outlookvim\r\n\r\n1.  How to install two buttons in Outlook to launch Vim\r\n2.  How to configure your Vim plugin to your file locations and your preferences.\r\n","first_name":"David","6":"David","last_name":"Fishburn","7":"Fishburn","releases":[{"0":"3087","vim_version":"7.0","1":"7.0","script_version":"14.0","2":"14.0","version_comment":"Added Vim Licence","3":"Added Vim Licence","package":"outlookvim_v14.zip","4":"outlookvim_v14.zip","src_id":"24022","5":"24022","creation_date":"1455799697","6":"1455799697"},{"0":"3087","vim_version":"7.0","1":"7.0","script_version":"13.0","2":"13.0","version_comment":"Bug Fixes\r\n---------\r\n- OutlookVim globally set the textwidth for Vim if g:outlook_textwidth is defined, instead of setting the textwidth for the specific email buffer opened when editing an email.  The textwidth for the buffer will only be set if g:outlook_textwidth is set and > 0 (Antonis Loumiotis).\r\n","3":"Bug Fixes\r\n---------\r\n- OutlookVim globally set the textwidth for Vim if g:outlook_textwidth is defined, instead of setting the textwidth for the specific email buffer opened when editing an email.  The textwidth for the buffer will only be set if g:outlook_textwidth is set and > 0 (Antonis Loumiotis).\r\n","package":"outlookvim_v13.zip","4":"outlookvim_v13.zip","src_id":"20951","5":"20951","creation_date":"1382640277","6":"1382640277"},{"0":"3087","vim_version":"7.0","1":"7.0","script_version":"12.0","2":"12.0","version_comment":"New Features\r\n------------\r\n- Four new macros have been added for the Outlook toolbars, Compose, Reply, ReplyToAll, Forward.  Unlike the previous Edit macro these macros can be used from your Inbox view.  They can be added to the Inbox toolbar and will simply open the selected email items and automatically launch Vim.  These macros support selecting multiple items in your Inbox.  Compose obviously creates only a single email (J\u00c3\u00b6rn Waterstraat).\r\n- New option g:outlook_edit_cmd (defaults to \"edit\") allows you to control what command will be used to edit a new email.  For example, if you wanted a split at the bottom of Vim, you could set it to 'botright split'.\r\n                                                                                 \r\nBug Fixes\r\n---------\r\n- In some cases when opening am email in Vim which was in insert mode or having unsaved text it was possible for the text to be overwritten (Gary Johnson).\r\n","3":"New Features\r\n------------\r\n- Four new macros have been added for the Outlook toolbars, Compose, Reply, ReplyToAll, Forward.  Unlike the previous Edit macro these macros can be used from your Inbox view.  They can be added to the Inbox toolbar and will simply open the selected email items and automatically launch Vim.  These macros support selecting multiple items in your Inbox.  Compose obviously creates only a single email (J\u00c3\u00b6rn Waterstraat).\r\n- New option g:outlook_edit_cmd (defaults to \"edit\") allows you to control what command will be used to edit a new email.  For example, if you wanted a split at the bottom of Vim, you could set it to 'botright split'.\r\n                                                                                 \r\nBug Fixes\r\n---------\r\n- In some cases when opening am email in Vim which was in insert mode or having unsaved text it was possible for the text to be overwritten (Gary Johnson).\r\n","package":"outlookvim_v12.zip","4":"outlookvim_v12.zip","src_id":"20764","5":"20764","creation_date":"1378522462","6":"1378522462"},{"0":"3087","vim_version":"7.0","1":"7.0","script_version":"11.0","2":"11.0","version_comment":"New Features\r\n------------\r\n- Changed how the filetype is set for Outlook.  The g:outlook_file_type will be used for all mail.  If g:outlook_supported_body_format = 'html' and the buffer begins with the html tag the filetype will be set to 'html'.\r\n                                                                              \r\nBug Fixes\r\n---------\r\n- g:outlook_supported_body_format was not checked in the Outlook macro, a previous variable name was used (Gary Johnson).\r\n","3":"New Features\r\n------------\r\n- Changed how the filetype is set for Outlook.  The g:outlook_file_type will be used for all mail.  If g:outlook_supported_body_format = 'html' and the buffer begins with the html tag the filetype will be set to 'html'.\r\n                                                                              \r\nBug Fixes\r\n---------\r\n- g:outlook_supported_body_format was not checked in the Outlook macro, a previous variable name was used (Gary Johnson).\r\n","package":"outlookvim_v11.zip","4":"outlookvim_v11.zip","src_id":"20360","5":"20360","creation_date":"1371326518","6":"1371326518"},{"0":"3087","vim_version":"7.0","1":"7.0","script_version":"10.0","2":"10.0","version_comment":"New Features\r\n------------\r\n- Editing HTML formated Outlook emails is now supported.  A new option has been added, g:outlook_supported_body_format, can have one of two values: plain or html.\r\n\r\nNOTE: Outlook html contains a lot of markup tags.  It can make it difficult to find the body text within all the tags.\r\n\r\n- A new option has been added, g:outlook_file_type, which defaults to 'mail'.  When opening the buffer within Vim, this file type is set for the buffer.   You may want to change this value if you are editig HTM emails.\r\n\r\n- A new command has been added: OutlookNewEmail.  This will take the contents of the existing buffer and create a new Outlook email.  If the filetype is 'html' and g:outlook_supported_body_format = 'html', the email body will be html rather than plain text.  The command can be run as often as necessary, a new Outlook email will be created each time.\r\n                                                                              \r\nBug Fixes\r\n---------\r\n- The additional changes to the VB code to support both 32-bit and 64-bit platforms does not work with Outlook 2007 32-bit (at least).  The new changes will work for either (Greg Dunn).\r\n","3":"New Features\r\n------------\r\n- Editing HTML formated Outlook emails is now supported.  A new option has been added, g:outlook_supported_body_format, can have one of two values: plain or html.\r\n\r\nNOTE: Outlook html contains a lot of markup tags.  It can make it difficult to find the body text within all the tags.\r\n\r\n- A new option has been added, g:outlook_file_type, which defaults to 'mail'.  When opening the buffer within Vim, this file type is set for the buffer.   You may want to change this value if you are editig HTM emails.\r\n\r\n- A new command has been added: OutlookNewEmail.  This will take the contents of the existing buffer and create a new Outlook email.  If the filetype is 'html' and g:outlook_supported_body_format = 'html', the email body will be html rather than plain text.  The command can be run as often as necessary, a new Outlook email will be created each time.\r\n                                                                              \r\nBug Fixes\r\n---------\r\n- The additional changes to the VB code to support both 32-bit and 64-bit platforms does not work with Outlook 2007 32-bit (at least).  The new changes will work for either (Greg Dunn).\r\n","package":"outlookvim_v10.zip","4":"outlookvim_v10.zip","src_id":"20247","5":"20247","creation_date":"1370053944","6":"1370053944"},{"0":"3087","vim_version":"7.0","1":"7.0","script_version":"9.0","2":"9.0","version_comment":"NF: Added new option, g:outlook_always_use_unicode, to override Outlook and force all emails to use utf-16le fileencoding.\r\n\r\nNF: Added new option, g:outlook_scan_email_body_unicode, to override whether messages will be scanned for unicode characters.\r\n\r\nNF: Added new option, g:outlook_debug, to turn on messages displayed to both Outlook and Vim.\r\n\r\nNF: Updated some of the messages displayed to be more informative.\r\n                                                                            \r\nBF: Editing unicode emails did not reliably work with OutlookVim.\r\n\r\nBF: Unicode detection was not always correct in the Outlook Basic file.\r\n\r\nBF: Updated the codepage which Vim expects unicode messages from Outlook to be encoded in (Andr\u00c3\u00a1s).\r\n\r\nBF: Added some additional changes to the VB code to support both 32-bit and 64-bit platforms (Paul).\r\n","3":"NF: Added new option, g:outlook_always_use_unicode, to override Outlook and force all emails to use utf-16le fileencoding.\r\n\r\nNF: Added new option, g:outlook_scan_email_body_unicode, to override whether messages will be scanned for unicode characters.\r\n\r\nNF: Added new option, g:outlook_debug, to turn on messages displayed to both Outlook and Vim.\r\n\r\nNF: Updated some of the messages displayed to be more informative.\r\n                                                                            \r\nBF: Editing unicode emails did not reliably work with OutlookVim.\r\n\r\nBF: Unicode detection was not always correct in the Outlook Basic file.\r\n\r\nBF: Updated the codepage which Vim expects unicode messages from Outlook to be encoded in (Andr\u00c3\u00a1s).\r\n\r\nBF: Added some additional changes to the VB code to support both 32-bit and 64-bit platforms (Paul).\r\n","package":"outlookvim_v9.zip","4":"outlookvim_v9.zip","src_id":"20106","5":"20106","creation_date":"1368410492","6":"1368410492"},{"0":"3087","vim_version":"7.0","1":"7.0","script_version":"8.0","2":"8.0","version_comment":"New Features\r\n------------\r\n- When preparing to edit an email in Vim, OutlookVim.bas will query the Vim instance checking to see if multibyte support is enabled in Vim.  It does this by checking to see if a bomb is enabled (:set bomb) and the value of fileencodings (:set fileencodings) to see if ucs-bom or any utf strings have been specified.  If multibyte is enabled, then the file created by OutlookVim.bas will be saved in unicode.  If your Vim is not setup to edit unicode files, Outlook will not enable the unicode format.\r\n","3":"New Features\r\n------------\r\n- When preparing to edit an email in Vim, OutlookVim.bas will query the Vim instance checking to see if multibyte support is enabled in Vim.  It does this by checking to see if a bomb is enabled (:set bomb) and the value of fileencodings (:set fileencodings) to see if ucs-bom or any utf strings have been specified.  If multibyte is enabled, then the file created by OutlookVim.bas will be saved in unicode.  If your Vim is not setup to edit unicode files, Outlook will not enable the unicode format.\r\n","package":"outlookvim_v8.zip","4":"outlookvim_v8.zip","src_id":"19460","5":"19460","creation_date":"1359741908","6":"1359741908"},{"0":"3087","vim_version":"7.0","1":"7.0","script_version":"7.0","2":"7.0","version_comment":"NF: Added support for Outlook 2010.\r\n\r\nNF: Added documentation on how to self sign the Outlook Vim macro so that security settings do not have to change in Outlook to use the macro.  Changing these settings are not possible in some companies.\r\n","3":"NF: Added support for Outlook 2010.\r\n\r\nNF: Added documentation on how to self sign the Outlook Vim macro so that security settings do not have to change in Outlook to use the macro.  Changing these settings are not possible in some companies.\r\n","package":"outlookvim_v7.zip","4":"outlookvim_v7.zip","src_id":"18768","5":"18768","creation_date":"1349828757","6":"1349828757"},{"0":"3087","vim_version":"7.0","1":"7.0","script_version":"6.0","2":"6.0","version_comment":"Bug Fix\r\n----------\r\n- Changed how the script looks for some system files especially useful if you do not store your vimfiles directory in the $VIM directory (Adam Duck).\r\n","3":"Bug Fix\r\n----------\r\n- Changed how the script looks for some system files especially useful if you do not store your vimfiles directory in the $VIM directory (Adam Duck).\r\n","package":"outlookvim_v6.zip","4":"outlookvim_v6.zip","src_id":"17505","5":"17505","creation_date":"1329789137","6":"1329789137"},{"0":"3087","vim_version":"7.0","1":"7.0","script_version":"5.0","2":"5.0","version_comment":"New Features\r\n------------\r\n- Changed how the script looks for some system files especially useful if you do not store your vimfiles directory in the $VIM directory (Adam Duck).\r\n","3":"New Features\r\n------------\r\n- Changed how the script looks for some system files especially useful if you do not store your vimfiles directory in the $VIM directory (Adam Duck).\r\n","package":"outlookvim_v5.zip","4":"outlookvim_v5.zip","src_id":"13561","5":"13561","creation_date":"1281752742","6":"1281752742"},{"0":"3087","vim_version":"7.0","1":"7.0","script_version":"4.0","2":"4.0","version_comment":"New Features\r\n------------\r\n- Updated documentation.  Added a troubleshooting section (Zsolt Botykai).\r\n- Updated outlookvim.js to display a message if double clicked on to determine if Windows Script Host is correctly installed.\r\n- Updated outlookvim.bas (the Outlook VBScript Macro) to show an error if it cannot access the file system.  Modified all the message boxes Outlook may display to indicate \"OutlookVim:\" is displaying the message.\r\n- You can specify whether new emails should be opened in a new tab via the g:outlook_use_tabs configuration option (Zsolt Botykai).\r\n\r\nAfter unzipping the contents into your vimfiles directory, copy and paste the outlookvim.bas file into your Outlook macro created earlier (ALT-F11 in Outlook).\r\n\r\nAlso from within Vim run (choose the location where the plugin was installed):\r\n:helptags $VIM\\vimfiles\\doc","3":"New Features\r\n------------\r\n- Updated documentation.  Added a troubleshooting section (Zsolt Botykai).\r\n- Updated outlookvim.js to display a message if double clicked on to determine if Windows Script Host is correctly installed.\r\n- Updated outlookvim.bas (the Outlook VBScript Macro) to show an error if it cannot access the file system.  Modified all the message boxes Outlook may display to indicate \"OutlookVim:\" is displaying the message.\r\n- You can specify whether new emails should be opened in a new tab via the g:outlook_use_tabs configuration option (Zsolt Botykai).\r\n\r\nAfter unzipping the contents into your vimfiles directory, copy and paste the outlookvim.bas file into your Outlook macro created earlier (ALT-F11 in Outlook).\r\n\r\nAlso from within Vim run (choose the location where the plugin was installed):\r\n:helptags $VIM\\vimfiles\\doc","package":"outlookvim_v4.zip","4":"outlookvim_v4.zip","src_id":"13108","5":"13108","creation_date":"1275654755","6":"1275654755"},{"0":"3087","vim_version":"7.0","1":"7.0","script_version":"3.0","2":"3.0","version_comment":" New Features\r\n ------------\r\n - You can specify which Vim instance to edit the file by setting a variable in your .vimrc (i.e. let g:outlook_servername = 'OUTLOOK')\r\n \r\n Bug Fixes\r\n ---------\r\n - For some (international?) Windows versions, there were errors when (or a failure) editing the file.  Needed to escape the backslashes of the filename.\r\n","3":" New Features\r\n ------------\r\n - You can specify which Vim instance to edit the file by setting a variable in your .vimrc (i.e. let g:outlook_servername = 'OUTLOOK')\r\n \r\n Bug Fixes\r\n ---------\r\n - For some (international?) Windows versions, there were errors when (or a failure) editing the file.  Needed to escape the backslashes of the filename.\r\n","package":"outlookvim_v3.zip","4":"outlookvim_v3.zip","src_id":"12984","5":"12984","creation_date":"1273460166","6":"1273460166"},{"0":"3087","vim_version":"7.0","1":"7.0","script_version":"2.0","2":"2.0","version_comment":"This version adds support for Microsoft Outlook 2007 as well as earlier versions. \r\nDocumentation improvements.","3":"This version adds support for Microsoft Outlook 2007 as well as earlier versions. \r\nDocumentation improvements.","package":"outlookvim_v2.zip","4":"outlookvim_v2.zip","src_id":"12965","5":"12965","creation_date":"1273195469","6":"1273195469"},{"0":"3087","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"outlookvim_v1.zip","4":"outlookvim_v1.zip","src_id":"12963","5":"12963","creation_date":"1273195200","6":"1273195200"}]},"3086":{"script_id":"3086","0":"3086","script_name":"glyph.vim","1":"glyph.vim","script_type":"syntax","2":"syntax","summary":"Syntax highlighting for the Glyph Macro Language","3":"Syntax highlighting for the Glyph Macro Language","description":"A simple syntax highlighter for the Glyph Macro Language. For more information on the Glyph Document Authoring Framework, see http:\/\/www.h3rald.com\/glyph\/","4":"A simple syntax highlighter for the Glyph Macro Language. For more information on the Glyph Document Authoring Framework, see http:\/\/www.h3rald.com\/glyph\/","install_details":"","5":"","first_name":"Fabio","6":"Fabio","last_name":"Cevasco","7":"Cevasco","releases":[{"0":"3086","vim_version":"7.0","1":"7.0","script_version":"1.5.0","2":"1.5.0","version_comment":"Added macro composition support, Glyph 0.5.0 macros.","3":"Added macro composition support, Glyph 0.5.0 macros.","package":"glyph.vim","4":"glyph.vim","src_id":"15131","5":"15131","creation_date":"1298832516","6":"1298832516"},{"0":"3086","vim_version":"6.0","1":"6.0","script_version":"1.4.2","2":"1.4.2","version_comment":"Minor improvements.","3":"Minor improvements.","package":"glyph.vim","4":"glyph.vim","src_id":"13170","5":"13170","creation_date":"1276343356","6":"1276343356"},{"0":"3086","vim_version":"6.0","1":"6.0","script_version":"1.4.0","2":"1.4.0","version_comment":"- Quoting macro names are now highlighted\r\n- Quoting macros are no longer highlighted in comments\r\n- Attribute names are now highlighted within quoting macros\r\n- Added highlighting for placeholders\r\n","3":"- Quoting macro names are now highlighted\r\n- Quoting macros are no longer highlighted in comments\r\n- Attribute names are now highlighted within quoting macros\r\n- Added highlighting for placeholders\r\n","package":"glyph.vim","4":"glyph.vim","src_id":"13113","5":"13113","creation_date":"1275734439","6":"1275734439"},{"0":"3086","vim_version":"6.0","1":"6.0","script_version":"1.3.0","2":"1.3.0","version_comment":"Added highlighting for core macros.","3":"Added highlighting for core macros.","package":"glyph.vim","4":"glyph.vim","src_id":"13097","5":"13097","creation_date":"1275565937","6":"1275565937"},{"0":"3086","vim_version":"6.0","1":"6.0","script_version":"1.2.0","2":"1.2.0","version_comment":"Added comment highlighting.","3":"Added comment highlighting.","package":"glyph.vim","4":"glyph.vim","src_id":"13078","5":"13078","creation_date":"1275332118","6":"1275332118"},{"0":"3086","vim_version":"6.0","1":"6.0","script_version":"1.1.0","2":"1.1.0","version_comment":"Added highlighting for attributes.","3":"Added highlighting for attributes.","package":"glyph.vim","4":"glyph.vim","src_id":"13073","5":"13073","creation_date":"1275220103","6":"1275220103"},{"0":"3086","vim_version":"6.0","1":"6.0","script_version":"1.0.0","2":"1.0.0","version_comment":"Initial upload","3":"Initial upload","package":"glyph.vim","4":"glyph.vim","src_id":"12962","5":"12962","creation_date":"1273146341","6":"1273146341"}]},"3085":{"script_id":"3085","0":"3085","script_name":"tf2.vim","1":"tf2.vim","script_type":"syntax","2":"syntax","summary":"TF2 script syntax highlighting","3":"TF2 script syntax highlighting","description":"Extremely basic syntax highlighting of Team Fortress 2 scripts (.cfg). Pretty much a find\/replace of the original quake.vim with the custom color support removed.","4":"Extremely basic syntax highlighting of Team Fortress 2 scripts (.cfg). Pretty much a find\/replace of the original quake.vim with the custom color support removed.","install_details":"1) Place tf2.vim into ~\/.vim\/syntax in Linux or ~\/vimfiles\/syntax in Windows (make the folders if they don't already exist).\r\n2) Add the following to ~\/.vim\/filetype.vim or ~\/vimfiles\/filetype.vim (make an empty filetype.vim if it doesn't already exist) to automatically detect TF2 scripts:\r\n\r\naugroup filetypedetect\r\n    au! BufRead,BufNewFile *\/tf\/cfg\/*.cfg\tsetfiletype tf2\r\naugroup END","5":"1) Place tf2.vim into ~\/.vim\/syntax in Linux or ~\/vimfiles\/syntax in Windows (make the folders if they don't already exist).\r\n2) Add the following to ~\/.vim\/filetype.vim or ~\/vimfiles\/filetype.vim (make an empty filetype.vim if it doesn't already exist) to automatically detect TF2 scripts:\r\n\r\naugroup filetypedetect\r\n    au! BufRead,BufNewFile *\/tf\/cfg\/*.cfg\tsetfiletype tf2\r\naugroup END","first_name":"Sumant","6":"Sumant","last_name":"Manne","7":"Manne","releases":[{"0":"3085","vim_version":"6.0","1":"6.0","script_version":".2","2":".2","version_comment":"a few more commands added\r\nI'm going to have to write a script to properly make this script eventually =S","3":"a few more commands added\r\nI'm going to have to write a script to properly make this script eventually =S","package":"tf2.vim","4":"tf2.vim","src_id":"13085","5":"13085","creation_date":"1275447976","6":"1275447976"},{"0":"3085","vim_version":"6.0","1":"6.0","script_version":".1","2":".1","version_comment":"Initial upload","3":"Initial upload","package":"tf2.vim","4":"tf2.vim","src_id":"12960","5":"12960","creation_date":"1273122357","6":"1273122357"}]},"3084":{"script_id":"3084","0":"3084","script_name":"dc.vim","1":"dc.vim","script_type":"syntax","2":"syntax","summary":"syntax definitions for dc (desktop calculator)","3":"syntax definitions for dc (desktop calculator)","description":"Syntax definitions file for dc (desktop calculator). \r\n\r\nCatch a glimpse of it at http:\/\/brhefele.brainaxle.com\/misc\/dc.html - note this html file was generated using vim's export highlighted as html tool.\r\n\r\nImportant note: this was written to support the way I code dc. The big problem with highlighting dc (IMO) is that of macros. Macros are stored in strings, with no clear way to delineate what a string may or may not be used for later on. Or, at least, no prescribed way. So, I need to prescribe my own way. Basically, everything inside [\u00e2\u0080\u00a6] is interpreted as a string, unless the string is followed by an execute command (x) OR a save command and a newline (s.\\n). This allows me to use macros as functions, and for the sake of tidiness, I keep all functions on their own lines. I assume, then, that a [\u00e2\u0080\u00a6]sx in the middle of the line is just a string being saved for later. I make a lot of assumptions. And I may change this later to allow for some variables to be set depending on a user's usage. For instance, I also set load\/save register operations to a specific highlight. But if you load a register to execute, including as part of a conditional, the whole operation changes to a different highlight (that for execute).\r\n\r\nSo again, this won't work for everyone. It might not work for anyone except me, really, since who uses dc these days anyway? But if you have any issues, suggestions, I welcome any and all emails on the subject.\r\n","4":"Syntax definitions file for dc (desktop calculator). \r\n\r\nCatch a glimpse of it at http:\/\/brhefele.brainaxle.com\/misc\/dc.html - note this html file was generated using vim's export highlighted as html tool.\r\n\r\nImportant note: this was written to support the way I code dc. The big problem with highlighting dc (IMO) is that of macros. Macros are stored in strings, with no clear way to delineate what a string may or may not be used for later on. Or, at least, no prescribed way. So, I need to prescribe my own way. Basically, everything inside [\u00e2\u0080\u00a6] is interpreted as a string, unless the string is followed by an execute command (x) OR a save command and a newline (s.\\n). This allows me to use macros as functions, and for the sake of tidiness, I keep all functions on their own lines. I assume, then, that a [\u00e2\u0080\u00a6]sx in the middle of the line is just a string being saved for later. I make a lot of assumptions. And I may change this later to allow for some variables to be set depending on a user's usage. For instance, I also set load\/save register operations to a specific highlight. But if you load a register to execute, including as part of a conditional, the whole operation changes to a different highlight (that for execute).\r\n\r\nSo again, this won't work for everyone. It might not work for anyone except me, really, since who uses dc these days anyway? But if you have any issues, suggestions, I welcome any and all emails on the subject.\r\n","install_details":"Drop dc.vim into ~\/.vim\/syntax\r\nEither set the filetype manually (:setf dc) or add\r\n\r\nau! BufRead,BufNewFile *.dc  setfiletype dc\r\n\r\nto filetype.vim.","5":"Drop dc.vim into ~\/.vim\/syntax\r\nEither set the filetype manually (:setf dc) or add\r\n\r\nau! BufRead,BufNewFile *.dc  setfiletype dc\r\n\r\nto filetype.vim.","first_name":"bri","6":"bri","last_name":"hefele","7":"hefele","releases":[{"0":"3084","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"dc.vim","4":"dc.vim","src_id":"12940","5":"12940","creation_date":"1272991678","6":"1272991678"}]},"3083":{"script_id":"3083","0":"3083","script_name":"qiushibaike","1":"qiushibaike","script_type":"utility","2":"utility","summary":"在Vim上看糗事百科","3":"在Vim上看糗事百科","description":"这个脚本实现了在vim上看糗事百科。\r\n需要环境：\r\n    python（默认的vim7.2是支持python2.4的，如果想要2.6的版本，请到  http:\/\/www.vimer.cn  下载）\r\n    BeautifulSoup4\r\n使用方法：\r\n    QB                          最新糗事，第二次执行会自动翻页\r\n    QBHot                    最糗糗事，第二次执行会自动翻页\r\n    QBReset                重置页码为1  \r\n\r\n作者主页：http:\/\/www.vimer.cn","4":"这个脚本实现了在vim上看糗事百科。\r\n需要环境：\r\n    python（默认的vim7.2是支持python2.4的，如果想要2.6的版本，请到  http:\/\/www.vimer.cn  下载）\r\n    BeautifulSoup4\r\n使用方法：\r\n    QB                          最新糗事，第二次执行会自动翻页\r\n    QBHot                    最糗糗事，第二次执行会自动翻页\r\n    QBReset                重置页码为1  \r\n\r\n作者主页：http:\/\/www.vimer.cn","install_details":"把文件直接放到plugin目录即可","5":"把文件直接放到plugin目录即可","first_name":"zhu","6":"zhu","last_name":"nianyang","7":"nianyang","releases":[{"0":"3083","vim_version":"7.0","1":"7.0","script_version":"2.0.1","2":"2.0.1","version_comment":"qiushibaike changed the url","3":"qiushibaike changed the url","package":"qiushibaike.vim","4":"qiushibaike.vim","src_id":"18140","5":"18140","creation_date":"1339906851","6":"1339906851"},{"0":"3083","vim_version":"7.0","1":"7.0","script_version":"2.0","2":"2.0","version_comment":"upgrade beautifulsoup to 4.0.\r\nfix some bug.","3":"upgrade beautifulsoup to 4.0.\r\nfix some bug.","package":"qiushibaike.vim","4":"qiushibaike.vim","src_id":"18120","5":"18120","creation_date":"1339554625","6":"1339554625"},{"0":"3083","vim_version":"7.0","1":"7.0","script_version":"1.9","2":"1.9","version_comment":"Add cmd QBReset.\r\nDel cmd QBN and QBHotN.\r\nQB and QBHot will remember the page num.","3":"Add cmd QBReset.\r\nDel cmd QBN and QBHotN.\r\nQB and QBHot will remember the page num.","package":"qiushibaike.vim","4":"qiushibaike.vim","src_id":"16608","5":"16608","creation_date":"1317440087","6":"1317440087"},{"0":"3083","vim_version":"7.0","1":"7.0","script_version":"1.8","2":"1.8","version_comment":"糗事百科网站改版。\r\n对应插件要做一定修改。\r\n并且加入了超时控制，默认是5秒。\r\n也可以通过\r\nlet g:qiushibaike_timeout=5\r\n来修改。","3":"糗事百科网站改版。\r\n对应插件要做一定修改。\r\n并且加入了超时控制，默认是5秒。\r\n也可以通过\r\nlet g:qiushibaike_timeout=5\r\n来修改。","package":"qiushibaike.vim","4":"qiushibaike.vim","src_id":"16600","5":"16600","creation_date":"1317293034","6":"1317293034"},{"0":"3083","vim_version":"7.0","1":"7.0","script_version":"1.7","2":"1.7","version_comment":"fix the bug of tab.\r\n修复当存在tab页时，会出现bug的问题","3":"fix the bug of tab.\r\n修复当存在tab页时，会出现bug的问题","package":"qiushibaike.vim","4":"qiushibaike.vim","src_id":"15403","5":"15403","creation_date":"1302106841","6":"1302106841"},{"0":"3083","vim_version":"7.0","1":"7.0","script_version":"1.6","2":"1.6","version_comment":"change the cmd.\r\nQB                          最新糗事 \r\nQBN                         下一页最新糗事 \r\nQBHot                       最糗糗事 \r\nQBHotN                      下一页最糗糗事 \r\n","3":"change the cmd.\r\nQB                          最新糗事 \r\nQBN                         下一页最新糗事 \r\nQBHot                       最糗糗事 \r\nQBHotN                      下一页最糗糗事 \r\n","package":"qiushibaike.vim","4":"qiushibaike.vim","src_id":"15395","5":"15395","creation_date":"1302057796","6":"1302057796"},{"0":"3083","vim_version":"7.0","1":"7.0","script_version":"1.5","2":"1.5","version_comment":"support http proxy","3":"support http proxy","package":"qiushibaike.vim","4":"qiushibaike.vim","src_id":"15370","5":"15370","creation_date":"1301850593","6":"1301850593"},{"0":"3083","vim_version":"7.0","1":"7.0","script_version":"1.4","2":"1.4","version_comment":"qiushibaike.com has change the sytle，so we need change this plugin to support it.","3":"qiushibaike.com has change the sytle，so we need change this plugin to support it.","package":"qiushibaike.vim","4":"qiushibaike.vim","src_id":"13610","5":"13610","creation_date":"1282103830","6":"1282103830"},{"0":"3083","vim_version":"7.0","1":"7.0","script_version":"1.3","2":"1.3","version_comment":"用BeautifulStoneSoup将>之类的标记转化成实体。","3":"用BeautifulStoneSoup将>之类的标记转化成实体。","package":"qiushibaike.vim","4":"qiushibaike.vim","src_id":"12949","5":"12949","creation_date":"1273035919","6":"1273035919"},{"0":"3083","vim_version":"7.0","1":"7.0","script_version":"1.2","2":"1.2","version_comment":"修正编码问题。\r\n从糗事百科获取的数据会自动转化为vim中文本文件的编码，避免出现乱码。","3":"修正编码问题。\r\n从糗事百科获取的数据会自动转化为vim中文本文件的编码，避免出现乱码。","package":"qiushibaike.vim","4":"qiushibaike.vim","src_id":"12948","5":"12948","creation_date":"1273025566","6":"1273025566"},{"0":"3083","vim_version":"7.0","1":"7.0","script_version":"1.1","2":"1.1","version_comment":"修改了发送包的信息","3":"修改了发送包的信息","package":"qiushibaike.vim","4":"qiushibaike.vim","src_id":"12947","5":"12947","creation_date":"1273022719","6":"1273022719"},{"0":"3083","vim_version":"7.2","1":"7.2","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"qiushibaike.vim","4":"qiushibaike.vim","src_id":"12939","5":"12939","creation_date":"1272983310","6":"1272983310"}]},"3082":{"script_id":"3082","0":"3082","script_name":"tagmaster","1":"tagmaster","script_type":"utility","2":"utility","summary":"Tags manipulation script","3":"Tags manipulation script","description":"Tagmaster is a plugin aimed for easy operating with tags and tag files. It allows generating tags for current project or file, deleting tags for given file, updating tags, etc.\r\nTags file name can be either specified explicitly, or deduced. Any tag file (found with tagfiles() function) is checked for if it can belong to current project (placed at the same directory level, or several levels up).\r\nBefore updating tags for given file, they all are deleted first to avoid duplicate tags.\r\nWhen generating tags for project, current filetype is considered and only files of this filetype are scanned. This is done to avoid collecting garbage from auxiliary files like config scripts, Makefiles, etc.\r\n\r\nNOTE: This plugin supports only exuberant ctags version. You should have it in your PATH environment.","4":"Tagmaster is a plugin aimed for easy operating with tags and tag files. It allows generating tags for current project or file, deleting tags for given file, updating tags, etc.\r\nTags file name can be either specified explicitly, or deduced. Any tag file (found with tagfiles() function) is checked for if it can belong to current project (placed at the same directory level, or several levels up).\r\nBefore updating tags for given file, they all are deleted first to avoid duplicate tags.\r\nWhen generating tags for project, current filetype is considered and only files of this filetype are scanned. This is done to avoid collecting garbage from auxiliary files like config scripts, Makefiles, etc.\r\n\r\nNOTE: This plugin supports only exuberant ctags version. You should have it in your PATH environment.","install_details":"move tagmaster.vim and ftypes.vim to the same directory (any) and source tagmaster.vim.","5":"move tagmaster.vim and ftypes.vim to the same directory (any) and source tagmaster.vim.","first_name":"Vladimir","6":"Vladimir","last_name":"Pavluk","7":"Pavluk","releases":[{"0":"3082","vim_version":"7.0","1":"7.0","script_version":"0.3","2":"0.3","version_comment":"Fixed -recurse option behaviour on Windows OS.\r\nFixed possible exceeding command-line length limit.\r\nMerged extensions for both C and C++ sources as one project can easily contain both.","3":"Fixed -recurse option behaviour on Windows OS.\r\nFixed possible exceeding command-line length limit.\r\nMerged extensions for both C and C++ sources as one project can easily contain both.","package":"tagmaster-0.3.zip","4":"tagmaster-0.3.zip","src_id":"12980","5":"12980","creation_date":"1273423909","6":"1273423909"},{"0":"3082","vim_version":"7.0","1":"7.0","script_version":"0.2","2":"0.2","version_comment":"Fixed tags-relative path translation.\r\nAdded -add \/ -noadd switches for TUpdate command (primarily for using with autocommands to update tags for saved file)","3":"Fixed tags-relative path translation.\r\nAdded -add \/ -noadd switches for TUpdate command (primarily for using with autocommands to update tags for saved file)","package":"tagmaster-0.2.zip","4":"tagmaster-0.2.zip","src_id":"12969","5":"12969","creation_date":"1273237213","6":"1273237213"},{"0":"3082","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"tagmaster-0.1.zip","4":"tagmaster-0.1.zip","src_id":"12936","5":"12936","creation_date":"1272963641","6":"1272963641"}]},"3081":{"script_id":"3081","0":"3081","script_name":"JavaScript Indent","1":"JavaScript Indent","script_type":"indent","2":"indent","summary":"Javascript indenter (HTML indent is included)","3":"Javascript indenter (HTML indent is included)","description":"Hosted at: http:\/\/code.google.com\/p\/web-indent\/\r\n\r\n*Update: (3\/30\/11) - Release Candidate 1.0 - Progress Started.\r\n*Update: (5\/14\/10) - Beta 3.0 Released (See Below) (First Release Candidate)\r\n*Update: (5\/6\/10) - Beta 2.2 Released (See Below)\r\n*Update: (5\/6\/10) - Beta 2.1 Released (See Below)\r\n*Update: (5\/5\/10) - Beta 2.0 Released (See Below)\r\n*Update: (5\/3\/10) - Beta 1.0 Released (See Below)\r\n\r\nSummary:\r\n================================================================================\r\nI wrote this basically due to the lack of any good javascript indent plugin out there.  And due to javascripts lax syntactical structure cindent() just wont cut it. \r\n\r\nWeb-Indent handles all basic forms of add notes, bugs and multi-line and singe line objects: \r\nvar x = {\r\n     y : {\r\n           z;\r\n     }\r\n}\r\n\r\nvar y = [\r\n      x,\r\n      y,\r\n      z\r\n]\r\n\r\nvar z = {x : x, y : y, w: w};\r\n\r\nt; \/\/ no indent\r\n\r\nHandles all basic control structures (with or without leading '{'):\r\nif(x)\r\n      \/\/ comment\r\n      y;\r\nz;\r\n\r\nHandles inline and nextline control structure block initializers ('{' in the vernacular):\r\nif(x) {\r\n     x;\r\n} \r\nelse \r\n{\r\n     z; \r\n}\r\n\r\nHandles multi-line function declarations:\r\nvar x = function( \r\n      y, \/\/ notice one tab over\r\n      z,\r\n      w) {\r\n      t;\r\n}\r\n\r\nHandles multi-line control structure statements:\r\nif( x == y ||\r\n      y == z ||\r\n      z == w) \r\n{\r\n      t;\r\n}\r\n\r\nThis indenter is also fully compatible with Mootools and esp. its Class package.  I haven't tested it with any of the other frameworks, but due to their similar syntactical nature, I'm assuming they will work as will.\r\n\r\nIncluded Files:\r\n================================================================================\r\n      ~test.js - A sample js file with various coding patterns.  Set tabstop=6 and shiftwidth=6 and comments should line up correctly.\r\n      ~indent\/javascript.vim - The core indenting file\r\n      ~indent\/html.vim - An updated version of the pre-packaged html indenter that utilizes javascript.vim (MUST BE LOCATED IN SAME DIRECTORY!!)\r\n\r\nRelease Notes:\r\n================================================================================\r\n~1.0 Released: (5\/15\/10)\r\n      - Fixed: Continuation Lines\r\n      - Removed: Logging\r\n\r\n~Beta 3.0 Released: (5\/14\/10)\r\n      - Fixed: Runaway Indentation.  \r\n      - Fixed: indentkeys now correctly invoke indent.\r\n      - Fixed: Comment lines with keywords are correctly indented.  Thanks to trojhlav for pointing it out.\r\n      - Notes:\r\n            \\ First Release Candidate (v 1.0)\r\n            \\ Correctly indented entire jQuery source.\r\n            \\ Correctly indented entire MooTools source.\r\n      - Concerns: \r\n            \\ Still no support for continuation lines.\r\n~ \r\n\r\nPS: I'm also not sure if I'm allowed to repost the html.vim, since I couldn't find a license for it.  I'm pretty sure it was the one packaged with vim by default.  If anyone has any objections, I'll take it down immediately.","4":"Hosted at: http:\/\/code.google.com\/p\/web-indent\/\r\n\r\n*Update: (3\/30\/11) - Release Candidate 1.0 - Progress Started.\r\n*Update: (5\/14\/10) - Beta 3.0 Released (See Below) (First Release Candidate)\r\n*Update: (5\/6\/10) - Beta 2.2 Released (See Below)\r\n*Update: (5\/6\/10) - Beta 2.1 Released (See Below)\r\n*Update: (5\/5\/10) - Beta 2.0 Released (See Below)\r\n*Update: (5\/3\/10) - Beta 1.0 Released (See Below)\r\n\r\nSummary:\r\n================================================================================\r\nI wrote this basically due to the lack of any good javascript indent plugin out there.  And due to javascripts lax syntactical structure cindent() just wont cut it. \r\n\r\nWeb-Indent handles all basic forms of add notes, bugs and multi-line and singe line objects: \r\nvar x = {\r\n     y : {\r\n           z;\r\n     }\r\n}\r\n\r\nvar y = [\r\n      x,\r\n      y,\r\n      z\r\n]\r\n\r\nvar z = {x : x, y : y, w: w};\r\n\r\nt; \/\/ no indent\r\n\r\nHandles all basic control structures (with or without leading '{'):\r\nif(x)\r\n      \/\/ comment\r\n      y;\r\nz;\r\n\r\nHandles inline and nextline control structure block initializers ('{' in the vernacular):\r\nif(x) {\r\n     x;\r\n} \r\nelse \r\n{\r\n     z; \r\n}\r\n\r\nHandles multi-line function declarations:\r\nvar x = function( \r\n      y, \/\/ notice one tab over\r\n      z,\r\n      w) {\r\n      t;\r\n}\r\n\r\nHandles multi-line control structure statements:\r\nif( x == y ||\r\n      y == z ||\r\n      z == w) \r\n{\r\n      t;\r\n}\r\n\r\nThis indenter is also fully compatible with Mootools and esp. its Class package.  I haven't tested it with any of the other frameworks, but due to their similar syntactical nature, I'm assuming they will work as will.\r\n\r\nIncluded Files:\r\n================================================================================\r\n      ~test.js - A sample js file with various coding patterns.  Set tabstop=6 and shiftwidth=6 and comments should line up correctly.\r\n      ~indent\/javascript.vim - The core indenting file\r\n      ~indent\/html.vim - An updated version of the pre-packaged html indenter that utilizes javascript.vim (MUST BE LOCATED IN SAME DIRECTORY!!)\r\n\r\nRelease Notes:\r\n================================================================================\r\n~1.0 Released: (5\/15\/10)\r\n      - Fixed: Continuation Lines\r\n      - Removed: Logging\r\n\r\n~Beta 3.0 Released: (5\/14\/10)\r\n      - Fixed: Runaway Indentation.  \r\n      - Fixed: indentkeys now correctly invoke indent.\r\n      - Fixed: Comment lines with keywords are correctly indented.  Thanks to trojhlav for pointing it out.\r\n      - Notes:\r\n            \\ First Release Candidate (v 1.0)\r\n            \\ Correctly indented entire jQuery source.\r\n            \\ Correctly indented entire MooTools source.\r\n      - Concerns: \r\n            \\ Still no support for continuation lines.\r\n~ \r\n\r\nPS: I'm also not sure if I'm allowed to repost the html.vim, since I couldn't find a license for it.  I'm pretty sure it was the one packaged with vim by default.  If anyone has any objections, I'll take it down immediately.","install_details":"Installation With Pathogen:\r\n      1. Place in pathogen directory\r\n\r\nInstallation W\/Out Pathogen:\r\n      1. Place in .vim\/indent directory, or anywhere in your runtime path.\r\n      2. If placed outside of .vim\/indent directory, set g:js_indent = \/location\/to\/javascript.vim in your .vimrc file. (This tells the html.vim file where to find the javascript indent file)\r\n\r\nTo Disable Logging: \r\n      1.  let g:js_indent_log = 0 in your .vimrc file.\r\n        ","5":"Installation With Pathogen:\r\n      1. Place in pathogen directory\r\n\r\nInstallation W\/Out Pathogen:\r\n      1. Place in .vim\/indent directory, or anywhere in your runtime path.\r\n      2. If placed outside of .vim\/indent directory, set g:js_indent = \/location\/to\/javascript.vim in your .vimrc file. (This tells the html.vim file where to find the javascript indent file)\r\n\r\nTo Disable Logging: \r\n      1.  let g:js_indent_log = 0 in your .vimrc file.\r\n        ","first_name":"Preston","6":"Preston","last_name":"Koprivica","7":"Koprivica","releases":[{"0":"3081","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":" See: web-indent.tar.gz v 1.0 ~","3":" See: web-indent.tar.gz v 1.0 ~","package":"web-indent.zip","4":"web-indent.zip","src_id":"15645","5":"15645","creation_date":"1305481710","6":"1305481710"},{"0":"3081","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Release 1.0! \r\n- Removed indentKeys completely\r\n- Removed Logging\r\n- Continuation Lines Supported!\r\n- Refactored Logic.\r\n","3":"Release 1.0! \r\n- Removed indentKeys completely\r\n- Removed Logging\r\n- Continuation Lines Supported!\r\n- Refactored Logic.\r\n","package":"web-indent.tar.gz","4":"web-indent.tar.gz","src_id":"15643","5":"15643","creation_date":"1305481297","6":"1305481297"},{"0":"3081","vim_version":"7.0","1":"7.0","script_version":"b3.0","2":"b3.0","version_comment":"Fixed: Runaway Indentation \r\nFixed: indentkeys correctly invokes indent\r\nFixed: Comment lines with keywords.  (Tentative fix)","3":"Fixed: Runaway Indentation \r\nFixed: indentkeys correctly invokes indent\r\nFixed: Comment lines with keywords.  (Tentative fix)","package":"web-indent.tar.gz","4":"web-indent.tar.gz","src_id":"13005","5":"13005","creation_date":"1273876280","6":"1273876280"},{"0":"3081","vim_version":"7.0","1":"7.0","script_version":"b2.2","2":"b2.2","version_comment":"Added: Support for while() control block.\r\nAdded: Support for do {} while(); control block.\r\nAdded: Support for with() {} control block. \r\nAdded: Skeleton support for all MULTI-LINE cntrl blocks  SINGLE LINE cntrl blocks DO NOT HAVE SKELETON VERSIONS!!\r\nAdded: Skeleton support for function declarations.\r\nAdded: Skeleton support for basic objects.\r\nAdded: Tests for skeleton code.","3":"Added: Support for while() control block.\r\nAdded: Support for do {} while(); control block.\r\nAdded: Support for with() {} control block. \r\nAdded: Skeleton support for all MULTI-LINE cntrl blocks  SINGLE LINE cntrl blocks DO NOT HAVE SKELETON VERSIONS!!\r\nAdded: Skeleton support for function declarations.\r\nAdded: Skeleton support for basic objects.\r\nAdded: Tests for skeleton code.","package":"web-indent.tar.gz","4":"web-indent.tar.gz","src_id":"12955","5":"12955","creation_date":"1273087136","6":"1273087136"},{"0":"3081","vim_version":"6.0","1":"6.0","script_version":"b2.1","2":"b2.1","version_comment":"Fixed: Object endings regex.  Now doesn't include preceding {, or [;\r\nFixed: Multi-Line invocation (Caveat: Must end in a ; or ,)","3":"Fixed: Object endings regex.  Now doesn't include preceding {, or [;\r\nFixed: Multi-Line invocation (Caveat: Must end in a ; or ,)","package":"web-indent.tar.gz","4":"web-indent.tar.gz","src_id":"12952","5":"12952","creation_date":"1273073918","6":"1273073918"},{"0":"3081","vim_version":"7.0","1":"7.0","script_version":"b2.0","2":"b2.0","version_comment":"Completely Rewrote\r\nFixed: Determines comment lines by synIDAttr\r\nAdded: Anonymous function handling","3":"Completely Rewrote\r\nFixed: Determines comment lines by synIDAttr\r\nAdded: Anonymous function handling","package":"web-indent.tar.gz","4":"web-indent.tar.gz","src_id":"12945","5":"12945","creation_date":"1273020261","6":"1273020261"}]},"3080":{"script_id":"3080","0":"3080","script_name":"deprecated","1":"deprecated","script_type":"utility","2":"utility","summary":"deprecated","3":"deprecated","description":"deprecated","4":"deprecated","install_details":"deprecated","5":"deprecated","first_name":"Hong","6":"Hong","last_name":"Xu","7":"Xu","releases":[{"0":"3080","vim_version":"5.7","1":"5.7","script_version":"0.0","2":"0.0","version_comment":"deprecated","3":"deprecated","package":"deprecated","4":"deprecated","src_id":"14824","5":"14824","creation_date":"1295699161","6":"1295699161"}]},"3079":{"script_id":"3079","0":"3079","script_name":"CodeFactory","1":"CodeFactory","script_type":"color scheme","2":"color scheme","summary":"A clean and dark color scheme for developers (Vim\/GVim)","3":"A clean and dark color scheme for developers (Vim\/GVim)","description":"This color scheme uses dark background and sober colors to develop without headache ;-)\r\n\r\nThe colors of the terminal version could be more pleasant if you use modified colors in .Xdefaults (or .Xresources depending on your O.S.)\r\n\r\nYou can contact me to get my .Xdefaults color theme (for xterm and urxvt): dsw [AT] mailoo.org\r\n\r\nEnjoy!\r\n\r\nPS: Sorry for my bad english...","4":"This color scheme uses dark background and sober colors to develop without headache ;-)\r\n\r\nThe colors of the terminal version could be more pleasant if you use modified colors in .Xdefaults (or .Xresources depending on your O.S.)\r\n\r\nYou can contact me to get my .Xdefaults color theme (for xterm and urxvt): dsw [AT] mailoo.org\r\n\r\nEnjoy!\r\n\r\nPS: Sorry for my bad english...","install_details":"","5":"","first_name":"Dee Sub Wun","6":"Dee Sub Wun","last_name":".","7":".","releases":[{"0":"3079","vim_version":"6.0","1":"6.0","script_version":"3","2":"3","version_comment":"Fixed colors for splitting","3":"Fixed colors for splitting","package":"CodeFactoryv3.vim","4":"CodeFactoryv3.vim","src_id":"12958","5":"12958","creation_date":"1273098256","6":"1273098256"}]},"3078":{"script_id":"3078","0":"3078","script_name":"Delphi (7-2010)","1":"Delphi (7-2010)","script_type":"syntax","2":"syntax","summary":"Delphi syntax highlight","3":"Delphi syntax highlight","description":"This is an updated delphi.vim syntax file for Delphi 2010, based on the original by Thorsten Maerz describedin vimscript #60.   The hard-coded colours have been removed, so changing color schemes will change the delphi syntax highlight colors too.   For Delphi 2010, additional language features will now be recognized, such as \"reference to\" and \"class procedure\" and so on.  I tried to contact Thorsten to find out about updating the existing script, but I have not received a reply as yet.\r\n\r\n","4":"This is an updated delphi.vim syntax file for Delphi 2010, based on the original by Thorsten Maerz describedin vimscript #60.   The hard-coded colours have been removed, so changing color schemes will change the delphi syntax highlight colors too.   For Delphi 2010, additional language features will now be recognized, such as \"reference to\" and \"class procedure\" and so on.  I tried to contact Thorsten to find out about updating the existing script, but I have not received a reply as yet.\r\n\r\n","install_details":"As described in vimscript #60, add delphi.vim to the syntax folder, and edit filetype.vim to add the new \"Delphi\/Pascal\" block.   An updated pascal.vim file included, in which pascal \"line\" comments (\/\/) are fixed.","5":"As described in vimscript #60, add delphi.vim to the syntax folder, and edit filetype.vim to add the new \"Delphi\/Pascal\" block.   An updated pascal.vim file included, in which pascal \"line\" comments (\/\/) are fixed.","first_name":"Caleb","6":"Caleb","last_name":"Hattingh","7":"Hattingh","releases":[{"0":"3078","vim_version":"7.2","1":"7.2","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"Delphi2010.zip","4":"Delphi2010.zip","src_id":"12923","5":"12923","creation_date":"1272745638","6":"1272745638"}]},"3077":{"script_id":"3077","0":"3077","script_name":"ego.vim","1":"ego.vim","script_type":"color scheme","2":"color scheme","summary":"A VIM color scheme using a dark background and beautiful foreground colors.","3":"A VIM color scheme using a dark background and beautiful foreground colors.","description":"Based on the ego Xcode theme: http:\/\/developers.enormego.com\/view\/xcode_ego_theme \r\n\r\nThis is my first theme I've created, so it needs quite a bit of improvement. Feel free to fork the project and contribute: http:\/\/github.com\/geetarista\/ego.vim \r\n\r\nScreenshot: http:\/\/github.com\/geetarista\/ego.vim\/raw\/master\/screenshot.png","4":"Based on the ego Xcode theme: http:\/\/developers.enormego.com\/view\/xcode_ego_theme \r\n\r\nThis is my first theme I've created, so it needs quite a bit of improvement. Feel free to fork the project and contribute: http:\/\/github.com\/geetarista\/ego.vim \r\n\r\nScreenshot: http:\/\/github.com\/geetarista\/ego.vim\/raw\/master\/screenshot.png","install_details":"Just copy ego.vim to ~\/vim\/colors.","5":"Just copy ego.vim to ~\/vim\/colors.","first_name":"Robby","6":"Robby","last_name":"Colvin","7":"Colvin","releases":[{"0":"3077","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"ego.vim","4":"ego.vim","src_id":"12921","5":"12921","creation_date":"1272655896","6":"1272655896"}]},"3075":{"script_id":"3075","0":"3075","script_name":"NrrwRgn","1":"NrrwRgn","script_type":"utility","2":"utility","summary":"A Narrow Region Plugin similar to Emacs","3":"A Narrow Region Plugin similar to Emacs","description":"This is a script emulates Emacs Narrowing feature, by opening a selected range in a new scratch buffer.\r\n\r\nSimilar scripts:\r\nnarrow_region: http:\/\/www.vim.org\/scripts\/script.php?script_id=2038\r\nnarrow: http:\/\/www.vim.org\/scripts\/script.php?script_id=2097\r\nnarrow: http:\/\/www.vim.org\/scripts\/script.php?script_id=2446\r\n\r\nUse :NarrowRegion to narrow a line based selection or alternatively visually select a range and press <Leader>nr\r\n\r\nIn the scratch buffer simply save it and the changes will be copied into the original file.\r\nThis is only a very simple help. You should probably read the help, that is provided with the plugin. See :h NarrowRegion\r\n\r\nThis Plugin is also available at github: http:\/\/github.com\/chrisbra\/NrrwRgn\r\n\r\nPlease rate this plugin if you like it!","4":"This is a script emulates Emacs Narrowing feature, by opening a selected range in a new scratch buffer.\r\n\r\nSimilar scripts:\r\nnarrow_region: http:\/\/www.vim.org\/scripts\/script.php?script_id=2038\r\nnarrow: http:\/\/www.vim.org\/scripts\/script.php?script_id=2097\r\nnarrow: http:\/\/www.vim.org\/scripts\/script.php?script_id=2446\r\n\r\nUse :NarrowRegion to narrow a line based selection or alternatively visually select a range and press <Leader>nr\r\n\r\nIn the scratch buffer simply save it and the changes will be copied into the original file.\r\nThis is only a very simple help. You should probably read the help, that is provided with the plugin. See :h NarrowRegion\r\n\r\nThis Plugin is also available at github: http:\/\/github.com\/chrisbra\/NrrwRgn\r\n\r\nPlease rate this plugin if you like it!","install_details":"as usual. Open the file in vim, and source it (:so %)","5":"as usual. Open the file in vim, and source it (:so %)","first_name":"Christian","6":"Christian","last_name":"Brabandt","7":"Brabandt","releases":[{"0":"3075","vim_version":"7.4","1":"7.4","script_version":"33","2":"33","version_comment":"- set local options later, so that FileType autocommands don't trigger to early\n- make sure, shortening the buffer name handles multibyte characters correctly.\n- new public function nrrwrgn#NrrwRgnStatus()\n- <Leader>nr also mapped as operator function (so the region over which you move will be opened in the narrowed window\n- highlighting wrong when char-selecting within a line\n- needs Vim 7.4\n- mention how to abort the narrowed window (suggested by David Fishburn, thanks!)\n- Execute hooks after the options for the narrowed window have been set (issue #29, reported by fmorales, thanks!)\n- <Leader><Space> Toggles the Narrowed Window Size (idea by David Fishburn, thanks!)\n- New hook b:nrrw_aucmd_written, to be executed, whenever the narrowed info has been written back into the original buffer.\n- g:nrrw_rgn_write_on_sync is being deprecated in favor of using the newly written hook\n- error on writing back multi narrowed window (issue #30, reported by aleprovencio https:\/\/github.com\/chrisbra\/NrrwRgn\/issues\/30, thanks!)\n- error when calling Incr Function, Make it override over global mapping. (issue #31, reported by zc he https:\/\/github.com\/chrisbra\/NrrwRgn\/issues\/31, thanks!)\n- |:NRP| didn't work as documented (reported by David Fishburn, thanks!)\n- fix small syntax error in autoload file (issue #32, reported by itchyny (https:\/\/github.com\/chrisbra\/NrrwRgn\/issues\/32, thanks!)\n- check, that dict key is available before accessing it (issue #33, reported by SirCorion (https:\/\/github.com\/chrisbra\/NrrwRgn\/issues\/33, thanks!)\n(automatically uploaded)","3":"- set local options later, so that FileType autocommands don't trigger to early\n- make sure, shortening the buffer name handles multibyte characters correctly.\n- new public function nrrwrgn#NrrwRgnStatus()\n- <Leader>nr also mapped as operator function (so the region over which you move will be opened in the narrowed window\n- highlighting wrong when char-selecting within a line\n- needs Vim 7.4\n- mention how to abort the narrowed window (suggested by David Fishburn, thanks!)\n- Execute hooks after the options for the narrowed window have been set (issue #29, reported by fmorales, thanks!)\n- <Leader><Space> Toggles the Narrowed Window Size (idea by David Fishburn, thanks!)\n- New hook b:nrrw_aucmd_written, to be executed, whenever the narrowed info has been written back into the original buffer.\n- g:nrrw_rgn_write_on_sync is being deprecated in favor of using the newly written hook\n- error on writing back multi narrowed window (issue #30, reported by aleprovencio https:\/\/github.com\/chrisbra\/NrrwRgn\/issues\/30, thanks!)\n- error when calling Incr Function, Make it override over global mapping. (issue #31, reported by zc he https:\/\/github.com\/chrisbra\/NrrwRgn\/issues\/31, thanks!)\n- |:NRP| didn't work as documented (reported by David Fishburn, thanks!)\n- fix small syntax error in autoload file (issue #32, reported by itchyny (https:\/\/github.com\/chrisbra\/NrrwRgn\/issues\/32, thanks!)\n- check, that dict key is available before accessing it (issue #33, reported by SirCorion (https:\/\/github.com\/chrisbra\/NrrwRgn\/issues\/33, thanks!)\n(automatically uploaded)","package":"NrrwRgn-0.33.vmb","4":"NrrwRgn-0.33.vmb","src_id":"22795","5":"22795","creation_date":"1421351736","6":"1421351736"},{"0":"3075","vim_version":"7.4","1":"7.4","script_version":"32","2":"32","version_comment":"- hooks could corrupt the narrowed buffer, if it wasn't closed (reported by\n  jszakemeister https:\/\/github.com\/chrisbra\/NrrwRgn\/issues\/19, thanks!)\n- Don't parse \/doc\/options.txt for finding out buffer-local options\n  (reported by AguirreIF https:\/\/github.com\/chrisbra\/NrrwRgn\/issues\/21,\n  thanks!), instead include a fix set of option names to set when opening the\n  narrowed buffer.\n- Switching buffers in the original narrowed buffer, may confuse NrrwRgn.\n- Code cleanup (no more separate functions for visual and normal mode)\n- fix issue 22 (characterwise narrowing was brocken in last commit, reported\n  by Matthew Boehm in https:\/\/github.com\/chrisbra\/NrrwRgn\/issues\/22, thanks!)\n- in characterwise visual selection, trailing \\n is not stripped when writing\n  (reported by Matthew Boehm in https:\/\/github.com\/chrisbra\/NrrwRgn\/23,\n  thanks!)\n- highlighting was wrong for characterwise visual selections\n- update original window for multi narrowed regions (\n  https:\/\/github.com\/chrisbra\/NrrwRgn\/24, reported by Dane Summers, thanks!),\n  use the g:nrrw_rgn_update_orig_win variable to enable\n- error when narrowed window was moved to new tab and trying to quit\n  (https:\/\/github.com\/chrisbra\/NrrwRgn\/2, reported by Mario Ricalde, thanks!)\n- better default names for the narrowed window\n  (https:\/\/github.com\/chrisbra\/Nrrwrgn\/28, reported by Mario Ricalde, thanks!)\n- when setting g:nrrw_rgn_write_on_sync the original file will be saved,\n  whenever the narrowed window is written back\n  (https:\/\/github.com\/chrisbra\/26, reported by Mario Ricalde, thanks!)\n- Some more error handling when using |:WidenRegion|\n- Make sure highlighting is removed when using |:WidenRegion|\n(automatically uploaded)","3":"- hooks could corrupt the narrowed buffer, if it wasn't closed (reported by\n  jszakemeister https:\/\/github.com\/chrisbra\/NrrwRgn\/issues\/19, thanks!)\n- Don't parse \/doc\/options.txt for finding out buffer-local options\n  (reported by AguirreIF https:\/\/github.com\/chrisbra\/NrrwRgn\/issues\/21,\n  thanks!), instead include a fix set of option names to set when opening the\n  narrowed buffer.\n- Switching buffers in the original narrowed buffer, may confuse NrrwRgn.\n- Code cleanup (no more separate functions for visual and normal mode)\n- fix issue 22 (characterwise narrowing was brocken in last commit, reported\n  by Matthew Boehm in https:\/\/github.com\/chrisbra\/NrrwRgn\/issues\/22, thanks!)\n- in characterwise visual selection, trailing \\n is not stripped when writing\n  (reported by Matthew Boehm in https:\/\/github.com\/chrisbra\/NrrwRgn\/23,\n  thanks!)\n- highlighting was wrong for characterwise visual selections\n- update original window for multi narrowed regions (\n  https:\/\/github.com\/chrisbra\/NrrwRgn\/24, reported by Dane Summers, thanks!),\n  use the g:nrrw_rgn_update_orig_win variable to enable\n- error when narrowed window was moved to new tab and trying to quit\n  (https:\/\/github.com\/chrisbra\/NrrwRgn\/2, reported by Mario Ricalde, thanks!)\n- better default names for the narrowed window\n  (https:\/\/github.com\/chrisbra\/Nrrwrgn\/28, reported by Mario Ricalde, thanks!)\n- when setting g:nrrw_rgn_write_on_sync the original file will be saved,\n  whenever the narrowed window is written back\n  (https:\/\/github.com\/chrisbra\/26, reported by Mario Ricalde, thanks!)\n- Some more error handling when using |:WidenRegion|\n- Make sure highlighting is removed when using |:WidenRegion|\n(automatically uploaded)","package":"NrrwRgn-0.32.vmb","4":"NrrwRgn-0.32.vmb","src_id":"21680","5":"21680","creation_date":"1395958723","6":"1395958723"},{"0":"3075","vim_version":"7.3","1":"7.3","script_version":"31","2":"31","version_comment":"- NRM threw some errors (reported by pydave in\n  https:\/\/github.com\/chrisbra\/NrrwRgn\/issues\/17, thanks!)\n- don't create swapfiles (reported by ping, thanks!)\n(automatically uploaded)","3":"- NRM threw some errors (reported by pydave in\n  https:\/\/github.com\/chrisbra\/NrrwRgn\/issues\/17, thanks!)\n- don't create swapfiles (reported by ping, thanks!)\n(automatically uploaded)","package":"NrrwRgn-0.31.vmb","4":"NrrwRgn-0.31.vmb","src_id":"19520","5":"19520","creation_date":"1361050212","6":"1361050212"},{"0":"3075","vim_version":"7.3","1":"7.3","script_version":"30","2":"30","version_comment":"- |NRL| throws erros, when used without having first narrowed a region - |NRV!| not allowed (reported by ping, thanks!)\n- when using single window narrowing, :w would jump back to the original window. Only do this, when 'hidden' is not set (reported by ping, thanks!)\n- when narrowing a region, the last visual selected region wasn't correctly restored (reported by ping, thanks!)\n- some code cleanup\n- recursive narrowing was broken, fix it (reported by ping, thanks!)\n(automatically uploaded)","3":"- |NRL| throws erros, when used without having first narrowed a region - |NRV!| not allowed (reported by ping, thanks!)\n- when using single window narrowing, :w would jump back to the original window. Only do this, when 'hidden' is not set (reported by ping, thanks!)\n- when narrowing a region, the last visual selected region wasn't correctly restored (reported by ping, thanks!)\n- some code cleanup\n- recursive narrowing was broken, fix it (reported by ping, thanks!)\n(automatically uploaded)","package":"NrrwRgn-0.30.vmb","4":"NrrwRgn-0.30.vmb","src_id":"19429","5":"19429","creation_date":"1359113633","6":"1359113633"},{"0":"3075","vim_version":"7.3","1":"7.3","script_version":"29","2":"29","version_comment":"\n- Use ! to have the narrowed buffer not opened in a new window (suggested by\n  Greg Sexton thanks!, issue #8\n  https:\/\/github.com\/chrisbra\/NrrwRgn\/issues\/8)\n- Fix mappings for visual mode (https:\/\/github.com\/chrisbra\/NrrwRgn\/issues\/9,\n  reported by Sung Pae, thanks!)\n- Fix problem with setting the filetype\n  (https:\/\/github.com\/chrisbra\/NrrwRgn\/issues\/10, reported by Hong Xu,\n  thanks!)\n- Fix some minor problems, when using ! mode\n(automatically uploaded)","3":"\n- Use ! to have the narrowed buffer not opened in a new window (suggested by\n  Greg Sexton thanks!, issue #8\n  https:\/\/github.com\/chrisbra\/NrrwRgn\/issues\/8)\n- Fix mappings for visual mode (https:\/\/github.com\/chrisbra\/NrrwRgn\/issues\/9,\n  reported by Sung Pae, thanks!)\n- Fix problem with setting the filetype\n  (https:\/\/github.com\/chrisbra\/NrrwRgn\/issues\/10, reported by Hong Xu,\n  thanks!)\n- Fix some minor problems, when using ! mode\n(automatically uploaded)","package":"NrrwRgn-0.29.vmb","4":"NrrwRgn-0.29.vmb","src_id":"18441","5":"18441","creation_date":"1345484302","6":"1345484302"},{"0":"3075","vim_version":"7.3","1":"7.3","script_version":"28","2":"28","version_comment":"- Plugin did not store last narrowed region when narrowed window was moved to another tabpage (reported by Ben Fritz, thanks!)\n(automatically uploaded)","3":"- Plugin did not store last narrowed region when narrowed window was moved to another tabpage (reported by Ben Fritz, thanks!)\n(automatically uploaded)","package":"NrrwRgn-0.28.vmb","4":"NrrwRgn-0.28.vmb","src_id":"18086","5":"18086","creation_date":"1338724151","6":"1338724151"},{"0":"3075","vim_version":"7.3","1":"7.3","script_version":"27","2":"27","version_comment":"- When using |:NR| on a line that is folded, include the whole folded region in the Narrowed window.\n- Better filetype detection for comments\n- Error handling, when doing |:NRM| without doing |:NRP| first\n- Use |:NRP!| to clear the old selection\n- Don't load the autoload script when sourcing the plugin script (reported by Sergey Khorev, thanks!)\n- Vim 7.3.449 introduced E855, prevent this error.\n- |:NRL|\n- |NRM| did not correctly parse the list of lines provided by |:NRP|\n- highlighted pattern for blockwise visual narrowed regions was wrong\n- Saving blockwise visual selected regions back, could corrupt the contents\n(automatically uploaded)","3":"- When using |:NR| on a line that is folded, include the whole folded region in the Narrowed window.\n- Better filetype detection for comments\n- Error handling, when doing |:NRM| without doing |:NRP| first\n- Use |:NRP!| to clear the old selection\n- Don't load the autoload script when sourcing the plugin script (reported by Sergey Khorev, thanks!)\n- Vim 7.3.449 introduced E855, prevent this error.\n- |:NRL|\n- |NRM| did not correctly parse the list of lines provided by |:NRP|\n- highlighted pattern for blockwise visual narrowed regions was wrong\n- Saving blockwise visual selected regions back, could corrupt the contents\n(automatically uploaded)","package":"NrrwRgn-0.27.vmb","4":"NrrwRgn-0.27.vmb","src_id":"17987","5":"17987","creation_date":"1337282163","6":"1337282163"},{"0":"3075","vim_version":"7.3","1":"7.3","script_version":"26","2":"26","version_comment":"- Fix issue https:\/\/github.com\/chrisbra\/NrrwRgn\/issues\/7 (reported by Alessio B., thanks!)\n(automatically uploaded)","3":"- Fix issue https:\/\/github.com\/chrisbra\/NrrwRgn\/issues\/7 (reported by Alessio B., thanks!)\n(automatically uploaded)","package":"NrrwRgn-0.26.vmb","4":"NrrwRgn-0.26.vmb","src_id":"17145","5":"17145","creation_date":"1325536558","6":"1325536558"},{"0":"3075","vim_version":"7.3","1":"7.3","script_version":"25","2":"25","version_comment":"- updated documentation (patch by Jean, thanks!)\n- make it possible, to not sync the narrowed buffer back by disabling\n  it using |:NRSyncOnWrite| |:NRNoSyncOnWrite|\n(automatically uploaded)","3":"- updated documentation (patch by Jean, thanks!)\n- make it possible, to not sync the narrowed buffer back by disabling\n  it using |:NRSyncOnWrite| |:NRNoSyncOnWrite|\n(automatically uploaded)","package":"NrrwRgn-0.25.vmb","4":"NrrwRgn-0.25.vmb","src_id":"16834","5":"16834","creation_date":"1320788157","6":"1320788157"},{"0":"3075","vim_version":"7.3","1":"7.3","script_version":"24","2":"24","version_comment":"(uploaded as release 0.24, as 0.23 was falsly uploaded to vim.org)\n(automatically uploaded)","3":"(uploaded as release 0.24, as 0.23 was falsly uploaded to vim.org)\n(automatically uploaded)","package":"NrrwRgn-0.24.vmb","4":"NrrwRgn-0.24.vmb","src_id":"16734","5":"16734","creation_date":"1319484490","6":"1319484490"},{"0":"3075","vim_version":"7.3","1":"7.3","script_version":"21","2":"21","version_comment":"-Fix issue https:\/\/github.com\/chrisbra\/NrrwRgn\/issues\/5\n(automatically uploaded)","3":"-Fix issue https:\/\/github.com\/chrisbra\/NrrwRgn\/issues\/5\n(automatically uploaded)","package":"NrrwRgn-0.21.vba","4":"NrrwRgn-0.21.vba","src_id":"16147","5":"16147","creation_date":"1311664033","6":"1311664033"},{"0":"3075","vim_version":"7.3","1":"7.3","script_version":"20","2":"20","version_comment":"- allow customization via the g:nrrw_topbot_leftright variable\n  (Thanks Herbert Sitz!)\n- allow what options will be applied using the g:nrrw_custom_options dict\n  (suggested by Herbert Sitz. Thanks!)\n- NRV didn't hightlight the region that was selected\n  (reported by Herbert Sitz, Thanks- use the g:nrrw_rgn_protect variable, to prevent that the original buffer\n  will be protected. This is useful, if you narrow several regions of the\n  same buffer and want to write those changes indepentently\n  (reported by kolyuchiy in https:\/\/github.com\/chrisbra\/NrrwRgn\/issues\/3,\n  Thanks- fix an error with not correctly deleting the highlighted region, that was\n  discovered when reporting issue 3 (see above).\n  (Reported by kolyuchiy, thanks!)\n- Catch errors, when setting window local options.\n  (Patch by Sung Pae, Thanks!)\n(automatically uploaded)","3":"- allow customization via the g:nrrw_topbot_leftright variable\n  (Thanks Herbert Sitz!)\n- allow what options will be applied using the g:nrrw_custom_options dict\n  (suggested by Herbert Sitz. Thanks!)\n- NRV didn't hightlight the region that was selected\n  (reported by Herbert Sitz, Thanks- use the g:nrrw_rgn_protect variable, to prevent that the original buffer\n  will be protected. This is useful, if you narrow several regions of the\n  same buffer and want to write those changes indepentently\n  (reported by kolyuchiy in https:\/\/github.com\/chrisbra\/NrrwRgn\/issues\/3,\n  Thanks- fix an error with not correctly deleting the highlighted region, that was\n  discovered when reporting issue 3 (see above).\n  (Reported by kolyuchiy, thanks!)\n- Catch errors, when setting window local options.\n  (Patch by Sung Pae, Thanks!)\n(automatically uploaded)","package":"NrrwRgn-0.20.vba","4":"NrrwRgn-0.20.vba","src_id":"16138","5":"16138","creation_date":"1311618412","6":"1311618412"},{"0":"3075","vim_version":"7.3","1":"7.3","script_version":"19","2":"19","version_comment":"fix issue 2 from github https:\/\/github.com\/chrisbra\/NrrwRgn\/issues\/2\n(Widening does not work, if the narrowed windows have been moved to a new tabspace). Reported by vanschelven, thanks! \n(automatically uploaded)","3":"fix issue 2 from github https:\/\/github.com\/chrisbra\/NrrwRgn\/issues\/2\n(Widening does not work, if the narrowed windows have been moved to a new tabspace). Reported by vanschelven, thanks! \n(automatically uploaded)","package":"NrrwRgn-0.19.vba","4":"NrrwRgn-0.19.vba","src_id":"15695","5":"15695","creation_date":"1306065776","6":"1306065776"},{"0":"3075","vim_version":"7.3","1":"7.3","script_version":"18","2":"18","version_comment":"Experimental version:\n- experimental feature: Allow to Narrow several different regions at once using :g\/pattern\/NRP and afterwards calling :NRM (This only works linewise. Should that be made possible for any reagion?)\n- disable folds, before writing changes back, otherwise chances are, you'll lose more data then wanted\n- code cleanup\n(automatically uploaded)","3":"Experimental version:\n- experimental feature: Allow to Narrow several different regions at once using :g\/pattern\/NRP and afterwards calling :NRM (This only works linewise. Should that be made possible for any reagion?)\n- disable folds, before writing changes back, otherwise chances are, you'll lose more data then wanted\n- code cleanup\n(automatically uploaded)","package":"NrrwRgn-0.18.vba","4":"NrrwRgn-0.18.vba","src_id":"14474","5":"14474","creation_date":"1292073913","6":"1292073913"},{"0":"3075","vim_version":"7.3","1":"7.3","script_version":"17","2":"17","version_comment":"- cache the options, that will be set (instead of parsing\n  $VIMRUNTIME\/doc\/options.txt everytime) in the Narrowed Window\n- getting the options didn't work, when using an autocommand like this:\n  autocmd BufEnter * cd %:p:h\n  (reported by Hong Xu, Thanks!)\n- :q didn't clean up the Narrowed Buffer correctly. Fix this\n- some code cleanup \n(automatically uploaded)","3":"- cache the options, that will be set (instead of parsing\n  $VIMRUNTIME\/doc\/options.txt everytime) in the Narrowed Window\n- getting the options didn't work, when using an autocommand like this:\n  autocmd BufEnter * cd %:p:h\n  (reported by Hong Xu, Thanks!)\n- :q didn't clean up the Narrowed Buffer correctly. Fix this\n- some code cleanup \n(automatically uploaded)","package":"NrrwRgn-0.17.vba","4":"NrrwRgn-0.17.vba","src_id":"14408","5":"14408","creation_date":"1291145027","6":"1291145027"},{"0":"3075","vim_version":"7.3","1":"7.3","script_version":"16","2":"16","version_comment":"- Bugfix: copy all local options to the narrowed window (reported by Xu Hong, Thanks)\n- Make :q quit the narrowed window correctly\n(automatically uploaded)","3":"- Bugfix: copy all local options to the narrowed window (reported by Xu Hong, Thanks)\n- Make :q quit the narrowed window correctly\n(automatically uploaded)","package":"NrrwRgn-0.16.vba","4":"NrrwRgn-0.16.vba","src_id":"14289","5":"14289","creation_date":"1290024947","6":"1290024947"},{"0":"3075","vim_version":"7.2","1":"7.2","script_version":"0.15","2":"0.15","version_comment":"-minor documentation update (reported by Hong Xu, Thanks!)","3":"-minor documentation update (reported by Hong Xu, Thanks!)","package":"NrrwRgn-0.15.vba","4":"NrrwRgn-0.15.vba","src_id":"13683","5":"13683","creation_date":"1282845351","6":"1282845351"},{"0":"3075","vim_version":"7.2","1":"7.2","script_version":"0.14","2":"0.14","version_comment":"- Bugfix: :only in the original buffer resulted in errors (reported by Adam\n  Monsen)","3":"- Bugfix: :only in the original buffer resulted in errors (reported by Adam\n  Monsen)","package":"NrrwRgn-0.14.vba","4":"NrrwRgn-0.14.vba","src_id":"13678","5":"13678","creation_date":"1282820346","6":"1282820346"},{"0":"3075","vim_version":"7.2","1":"7.2","script_version":"0.13","2":"0.13","version_comment":"This adds the experimental feature of using the command :NUD to view a chunk of a unified diff in diff-mode","3":"This adds the experimental feature of using the command :NUD to view a chunk of a unified diff in diff-mode","package":"NrrwRgn-0.13.vba","4":"NrrwRgn-0.13.vba","src_id":"13644","5":"13644","creation_date":"1282482758","6":"1282482758"},{"0":"3075","vim_version":"7.0","1":"7.0","script_version":"0.12","2":"0.12","version_comment":"The Vimball for Version 0.11 contained some garbage that causes various errors.. So this Version is a new packaged version and should work now. Not sure how that happened.\r\n(Thanks Dennis Hostetler!)","3":"The Vimball for Version 0.11 contained some garbage that causes various errors.. So this Version is a new packaged version and should work now. Not sure how that happened.\r\n(Thanks Dennis Hostetler!)","package":"NrrwRgn-0.12.vba","4":"NrrwRgn-0.12.vba","src_id":"13422","5":"13422","creation_date":"1280355030","6":"1280355030"},{"0":"3075","vim_version":"7.0","1":"7.0","script_version":"0.11","2":"0.11","version_comment":"Don't set 'winfixwidth' and 'winfixheight'","3":"Don't set 'winfixwidth' and 'winfixheight'","package":"NrrwRgn-0.11.vba","4":"NrrwRgn-0.11.vba","src_id":"13420","5":"13420","creation_date":"1280342133","6":"1280342133"},{"0":"3075","vim_version":"7.0","1":"7.0","script_version":"0.10","2":"0.10","version_comment":"- Restore Cursorposition using winrestview() and winsaveview()\r\n- fix a bug, that prevented the use of visual narrowing\r\n- Make sure when closing the narrowed buffer, the content will be written to\r\n  the right original region\r\n- use topleft for opening the Narrowed window\r\n- check, that the original buffer is still available\r\n- If you Narrow the complete buffer using :NRV and write the changes back, an\r\n  additional trailing line is inserted. Remove that line.\r\n- When writing the changes back, update the highlighting.","3":"- Restore Cursorposition using winrestview() and winsaveview()\r\n- fix a bug, that prevented the use of visual narrowing\r\n- Make sure when closing the narrowed buffer, the content will be written to\r\n  the right original region\r\n- use topleft for opening the Narrowed window\r\n- check, that the original buffer is still available\r\n- If you Narrow the complete buffer using :NRV and write the changes back, an\r\n  additional trailing line is inserted. Remove that line.\r\n- When writing the changes back, update the highlighting.","package":"NrrwRgn-0.10.vba","4":"NrrwRgn-0.10.vba","src_id":"13038","5":"13038","creation_date":"1274391204","6":"1274391204"},{"0":"3075","vim_version":"7.0","1":"7.0","script_version":"0.9","2":"0.9","version_comment":"- It is now possible to Narrow a window recursively. This allows to have\r\n  several narrowed windows, and allows for example to only diff certain\r\n  regions (as was suggested in a recent thread at the vim_use mailinglist:\r\n  http:\/\/groups.google.com\/group\/vim_use\/msg\/05d7fd9bd1556f0e) therefore, the\r\n  use for the g:nrrw_rgn_sepwin variable isn't necessary anymore.\r\n- Small documentation updates","3":"- It is now possible to Narrow a window recursively. This allows to have\r\n  several narrowed windows, and allows for example to only diff certain\r\n  regions (as was suggested in a recent thread at the vim_use mailinglist:\r\n  http:\/\/groups.google.com\/group\/vim_use\/msg\/05d7fd9bd1556f0e) therefore, the\r\n  use for the g:nrrw_rgn_sepwin variable isn't necessary anymore.\r\n- Small documentation updates","package":"NrrwRgn-0.9.vba","4":"NrrwRgn-0.9.vba","src_id":"13029","5":"13029","creation_date":"1274335965","6":"1274335965"},{"0":"3075","vim_version":"7.0","1":"7.0","script_version":"0.8","2":"0.8","version_comment":"- the g:nrrw_rgn_sepwin variable can be used to force seperate Narrowed Windows, so you could easily diff those windows.\r\n- make the separating of several windows a little bit safer (look at the bufnr(), so it should work without problems for several buffers)\r\n- switch from script local variables to buffer local variables, so narrowing for several buffers should work.\r\n- set 'winfixheight' for narrowed window \r\n- Added command :NRV (suggested by Charles Campbell, thanks!)\r\n- added error handling, in case :NRV is called, without a selected region\r\n- take care of beeps, when calling :NRV\r\n- output WarningMsg","3":"- the g:nrrw_rgn_sepwin variable can be used to force seperate Narrowed Windows, so you could easily diff those windows.\r\n- make the separating of several windows a little bit safer (look at the bufnr(), so it should work without problems for several buffers)\r\n- switch from script local variables to buffer local variables, so narrowing for several buffers should work.\r\n- set 'winfixheight' for narrowed window \r\n- Added command :NRV (suggested by Charles Campbell, thanks!)\r\n- added error handling, in case :NRV is called, without a selected region\r\n- take care of beeps, when calling :NRV\r\n- output WarningMsg","package":"NrrwRgn-0.8.vba","4":"NrrwRgn-0.8.vba","src_id":"13025","5":"13025","creation_date":"1274217930","6":"1274217930"},{"0":"3075","vim_version":"7.0","1":"7.0","script_version":"0.7","2":"0.7","version_comment":"- really use the black hole register for deleting the old buffer contents in the narrowed buffer (suggestion by esquifit in http:\/\/groups.google.com\/group\/comp.editors\/msg\/3eb3e3a7c68597db)\r\n- make autocommand nesting, so the highlighting will be removed when writing the buffer contents.\r\n- Use g:nrrw_rgn_nohl variable to disable highlighting (as this can be disturbing).","3":"- really use the black hole register for deleting the old buffer contents in the narrowed buffer (suggestion by esquifit in http:\/\/groups.google.com\/group\/comp.editors\/msg\/3eb3e3a7c68597db)\r\n- make autocommand nesting, so the highlighting will be removed when writing the buffer contents.\r\n- Use g:nrrw_rgn_nohl variable to disable highlighting (as this can be disturbing).","package":"NrrwRgn-0.7.vba","4":"NrrwRgn-0.7.vba","src_id":"13023","5":"13023","creation_date":"1274124087","6":"1274124087"},{"0":"3075","vim_version":"7.0","1":"7.0","script_version":"0.6","2":"0.6","version_comment":"Version 0.6:\r\n- the previous version had problems restoring the orig buffer, this version fixes it (highlighting and setl ma did not work correctly)\r\nVersion 0.5 (unreleased): \r\n- The mapping that allows for narrowing a visually selected range, did not work.  (Fixed!)\r\n- Make :WidenRegion work as expected (close the widened window)","3":"Version 0.6:\r\n- the previous version had problems restoring the orig buffer, this version fixes it (highlighting and setl ma did not work correctly)\r\nVersion 0.5 (unreleased): \r\n- The mapping that allows for narrowing a visually selected range, did not work.  (Fixed!)\r\n- Make :WidenRegion work as expected (close the widened window)","package":"NrrwRgn-0.6.vba","4":"NrrwRgn-0.6.vba","src_id":"12938","5":"12938","creation_date":"1272971066","6":"1272971066"},{"0":"3075","vim_version":"7.0","1":"7.0","script_version":"0.4","2":"0.4","version_comment":"- Highlight narrowed region in the original buffer\r\n- Save and Restore search-register\r\n- Provide shortcut commands |:NR|\r\n- Provide command |:NW| and |:NarrowWindow|\r\n- Make plugin autoloadable\r\n- Enable GLVS (see |:GLVS|)\r\n- Provide Documenation (:h NarrowRegion)\r\n- Distribute Plugin as vimball |pi_vimball.txt|","3":"- Highlight narrowed region in the original buffer\r\n- Save and Restore search-register\r\n- Provide shortcut commands |:NR|\r\n- Provide command |:NW| and |:NarrowWindow|\r\n- Make plugin autoloadable\r\n- Enable GLVS (see |:GLVS|)\r\n- Provide Documenation (:h NarrowRegion)\r\n- Distribute Plugin as vimball |pi_vimball.txt|","package":"NrrwRgn-0.4.vba","4":"NrrwRgn-0.4.vba","src_id":"12912","5":"12912","creation_date":"1272486011","6":"1272486011"},{"0":"3075","vim_version":"7.2","1":"7.2","script_version":"0.3","2":"0.3","version_comment":"Initial upload","3":"Initial upload","package":"NrrwRgn.vba","4":"NrrwRgn.vba","src_id":"12911","5":"12911","creation_date":"1272453080","6":"1272453080"}]},"3074":{"script_id":"3074","0":"3074","script_name":"Trac Wikimarkup","1":"Trac Wikimarkup","script_type":"syntax","2":"syntax","summary":"Better syntax highlighting for Trac wikimarkup","3":"Better syntax highlighting for Trac wikimarkup","description":"Syntax highlighting for Trac WikiMarkup.  \r\n\r\nI was a little unsatisfied with the other available wikimarkup highlighters available-- they were either too focused on a specific wiki engine to be useful for Trac, or its highlighting was less-than-complete.\r\n\r\nIn an effort to address this issue, I decided to make a few updates and modifications to http:\/\/www.vim.org\/scripts\/script.php?script_id=725.","4":"Syntax highlighting for Trac WikiMarkup.  \r\n\r\nI was a little unsatisfied with the other available wikimarkup highlighters available-- they were either too focused on a specific wiki engine to be useful for Trac, or its highlighting was less-than-complete.\r\n\r\nIn an effort to address this issue, I decided to make a few updates and modifications to http:\/\/www.vim.org\/scripts\/script.php?script_id=725.","install_details":"","5":"","first_name":"Adam","6":"Adam","last_name":"Coddington","7":"Coddington","releases":[{"0":"3074","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"wiki.vim","4":"wiki.vim","src_id":"12908","5":"12908","creation_date":"1272386368","6":"1272386368"}]},"3073":{"script_id":"3073","0":"3073","script_name":"kiss.vim","1":"kiss.vim","script_type":"color scheme","2":"color scheme","summary":"dark and simple colorscheme","3":"dark and simple colorscheme","description":"just a simple colorscheme :)\r\nscreenshot: http:\/\/s.cyrill.lilect.net\/uploader\/files\/201004252246250000.png ","4":"just a simple colorscheme :)\r\nscreenshot: http:\/\/s.cyrill.lilect.net\/uploader\/files\/201004252246250000.png ","install_details":"copy to vim\/colors","5":"copy to vim\/colors","first_name":"kt0x2e","6":"kt0x2e","last_name":"  ","7":"  ","releases":[{"0":"3073","vim_version":"7.2","1":"7.2","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"kiss.vim","4":"kiss.vim","src_id":"12901","5":"12901","creation_date":"1272203703","6":"1272203703"}]},"3072":{"script_id":"3072","0":"3072","script_name":"self.vim","1":"self.vim","script_type":"utility","2":"utility","summary":"Vim Self Object Prototype System","3":"Vim Self Object Prototype System","description":"The self.vim library provides a base Object Prototype for a VimScript object\r\nhierarchy which includes\r\nmethod and data inheritance. Method dispatch is static rather than dynamic - a\r\nVimScript\r\nfunction calling limitation. Included are a couple of limited test scripts.\r\n\r\nSource can be found at: https:\/\/github.com\/megaannum\/self\r\nSelf tutorial:\r\nhttps:\/\/github.com\/megaannum\/self\/blob\/master\/tutorial\/self\/Tutorial.md\r\n\r\nThe Self library is currently being used in the following scripts:\r\nForms Library\r\n  http:\/\/www.vim.org\/scripts\/script.php?script_id=4150\r\nColorschemer utility\r\n  http:\/\/www.vim.org\/scripts\/script.php?script_id=4240\r\nScalacommenter utility\r\n  http:\/\/www.vim.org\/scripts\/script.php?script_id=3047\r\nVimside, Vim Scala IDE\r\n  http:\/\/www.vim.org\/scripts\/script.php?script_id=4298\r\n","4":"The self.vim library provides a base Object Prototype for a VimScript object\r\nhierarchy which includes\r\nmethod and data inheritance. Method dispatch is static rather than dynamic - a\r\nVimScript\r\nfunction calling limitation. Included are a couple of limited test scripts.\r\n\r\nSource can be found at: https:\/\/github.com\/megaannum\/self\r\nSelf tutorial:\r\nhttps:\/\/github.com\/megaannum\/self\/blob\/master\/tutorial\/self\/Tutorial.md\r\n\r\nThe Self library is currently being used in the following scripts:\r\nForms Library\r\n  http:\/\/www.vim.org\/scripts\/script.php?script_id=4150\r\nColorschemer utility\r\n  http:\/\/www.vim.org\/scripts\/script.php?script_id=4240\r\nScalacommenter utility\r\n  http:\/\/www.vim.org\/scripts\/script.php?script_id=3047\r\nVimside, Vim Scala IDE\r\n  http:\/\/www.vim.org\/scripts\/script.php?script_id=4298\r\n","install_details":"    \r\nSelf.vim is a library plugin and can be placed in the autoload directory.\r\n    $HOME\/.vim\/autoload\/self.vim\r\n    \r\nIntalling with vim-addon-manager (VAM)\r\n\r\nFor more information about vim-addon-manager, see\r\n[vim-addon-manager](https:\/\/github.com\/MarcWeber\/vim-addon-manager) and\r\n[Vim-addon-manager getting\r\nstarted](https:\/\/github.com\/MarcWeber\/vim-addon-manager\/blob\/master\/doc\/vim-addon-manager-getting-started.txt)\r\n\r\nIn your .vimrc, add self as shown below:\r\n\r\n    fun SetupVAM()\r\n      ...\r\n      let g:vim_addon_manager = {}\r\n      let g:vim_addon_manager.plugin_sources = {}\r\n      ....\r\n      let g:vim_addon_manager.plugin_sources['self'] = {'type': 'git', 'url':\r\n'git:\/\/github.com\/megaannum\/self'}\r\n\r\n      let plugins = [\r\n        \\ 'self'\r\n        \\ ]\r\n\r\n      call vam#ActivateAddons(plugins,{'auto_install' : 0})\r\n      ...\r\n    endf\r\n    call SetupVAM()\r\n\r\nNow start Vim. You will be asked by vim-addon-manager\r\nif you would like to download and install the self plugin (no dependencies).\r\n\r\nInstalling with pathogen\r\n  I do not use pathogen. An example usage would be welcome.\r\n","5":"    \r\nSelf.vim is a library plugin and can be placed in the autoload directory.\r\n    $HOME\/.vim\/autoload\/self.vim\r\n    \r\nIntalling with vim-addon-manager (VAM)\r\n\r\nFor more information about vim-addon-manager, see\r\n[vim-addon-manager](https:\/\/github.com\/MarcWeber\/vim-addon-manager) and\r\n[Vim-addon-manager getting\r\nstarted](https:\/\/github.com\/MarcWeber\/vim-addon-manager\/blob\/master\/doc\/vim-addon-manager-getting-started.txt)\r\n\r\nIn your .vimrc, add self as shown below:\r\n\r\n    fun SetupVAM()\r\n      ...\r\n      let g:vim_addon_manager = {}\r\n      let g:vim_addon_manager.plugin_sources = {}\r\n      ....\r\n      let g:vim_addon_manager.plugin_sources['self'] = {'type': 'git', 'url':\r\n'git:\/\/github.com\/megaannum\/self'}\r\n\r\n      let plugins = [\r\n        \\ 'self'\r\n        \\ ]\r\n\r\n      call vam#ActivateAddons(plugins,{'auto_install' : 0})\r\n      ...\r\n    endf\r\n    call SetupVAM()\r\n\r\nNow start Vim. You will be asked by vim-addon-manager\r\nif you would like to download and install the self plugin (no dependencies).\r\n\r\nInstalling with pathogen\r\n  I do not use pathogen. An example usage would be welcome.\r\n","first_name":"richard","6":"richard","last_name":"emberson","7":"emberson","releases":[{"0":"3072","vim_version":"7.0","1":"7.0","script_version":"2.5","2":"2.5","version_comment":"No longer use IS_TRUE\/IS_FALSE (now, 1\/0)\r\nAdded version function","3":"No longer use IS_TRUE\/IS_FALSE (now, 1\/0)\r\nAdded version function","package":"self.zip","4":"self.zip","src_id":"19064","5":"19064","creation_date":"1354223325","6":"1354223325"},{"0":"3072","vim_version":"7.0","1":"7.0","script_version":"2.3","2":"2.3","version_comment":"Changed '_type' attribute to '_kind' and getType() to getKind().\r\nObjectPrototype methods are now named not numbered.\r\nAdded tutorial.\r\nAdded rational number example.","3":"Changed '_type' attribute to '_kind' and getType() to getKind().\r\nObjectPrototype methods are now named not numbered.\r\nAdded tutorial.\r\nAdded rational number example.","package":"self.zip","4":"self.zip","src_id":"18482","5":"18482","creation_date":"1345824294","6":"1345824294"},{"0":"3072","vim_version":"7.3","1":"7.3","script_version":"2.2","2":"2.2","version_comment":"Vim 7.3 could not handle construct: call funcReturnDictionary().someFunc()","3":"Vim 7.3 could not handle construct: call funcReturnDictionary().someFunc()","package":"self.zip","4":"self.zip","src_id":"18345","5":"18345","creation_date":"1343667795","6":"1343667795"},{"0":"3072","vim_version":"7.0","1":"7.0","script_version":"2.1.1","2":"2.1.1","version_comment":"Added additional documentation.","3":"Added additional documentation.","package":"self.zip","4":"self.zip","src_id":"18337","5":"18337","creation_date":"1343581525","6":"1343581525"},{"0":"3072","vim_version":"7.0","1":"7.0","script_version":"2.1","2":"2.1","version_comment":"Fixed FLOAT_TYPE value","3":"Fixed FLOAT_TYPE value","package":"self.zip","4":"self.zip","src_id":"18333","5":"18333","creation_date":"1343430360","6":"1343430360"},{"0":"3072","vim_version":"7.0","1":"7.0","script_version":"2.0","2":"2.0","version_comment":"Corrected bugs found while writing the {Forms} library.\r\nRe-organized code so that it could be autoloaded.\r\nAdded folding.\r\nAdded Object and Prototype Managers.\r\nAdded the 'reload(prefix)' function.","3":"Corrected bugs found while writing the {Forms} library.\r\nRe-organized code so that it could be autoloaded.\r\nAdded folding.\r\nAdded Object and Prototype Managers.\r\nAdded the 'reload(prefix)' function.","package":"self.zip","4":"self.zip","src_id":"18329","5":"18329","creation_date":"1343415568","6":"1343415568"},{"0":"3072","vim_version":"7.2","1":"7.2","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"self.zip","4":"self.zip","src_id":"12886","5":"12886","creation_date":"1271904840","6":"1271904840"}]},"3071":{"script_id":"3071","0":"3071","script_name":"reimin","1":"reimin","script_type":"utility","2":"utility","summary":"Add an #include without jumping","3":"Add an #include without jumping","description":"Usually adding an #include to a C or C++ source file means jumping the cursor to a line near the top of the file, adding the include, and jumping back. I consider jumping away from where the cursor is right now a distracting act, and thus the raison d\\'\u00c3\u00aatre of this plugin.\r\n\r\nIn normal mode enter :IncludeLocal or :IncludeSystem. You will be prompted for an include: enter the header name with no double quotes or angle-brackets.\r\n\r\nThe latest code is at http:\/\/github.com\/wilhelmtell\/reimin, but I will do my best to sync Vim Scripts when I make any significant release.","4":"Usually adding an #include to a C or C++ source file means jumping the cursor to a line near the top of the file, adding the include, and jumping back. I consider jumping away from where the cursor is right now a distracting act, and thus the raison d\\'\u00c3\u00aatre of this plugin.\r\n\r\nIn normal mode enter :IncludeLocal or :IncludeSystem. You will be prompted for an include: enter the header name with no double quotes or angle-brackets.\r\n\r\nThe latest code is at http:\/\/github.com\/wilhelmtell\/reimin, but I will do my best to sync Vim Scripts when I make any significant release.","install_details":"Unpack the tarball in your Vim directory -- e.g. $HOME\/.vim and the start a new session of Vim.","5":"Unpack the tarball in your Vim directory -- e.g. $HOME\/.vim and the start a new session of Vim.","first_name":"Matan","6":"Matan","last_name":"Nassau","7":"Nassau","releases":[{"0":"3071","vim_version":"6.0","1":"6.0","script_version":"v0.0.1","2":"v0.0.1","version_comment":"Initial upload","3":"Initial upload","package":"wilhelmtell-reimin-v0.0.1-0-g43c5ce9.tar.gz","4":"wilhelmtell-reimin-v0.0.1-0-g43c5ce9.tar.gz","src_id":"12885","5":"12885","creation_date":"1271896008","6":"1271896008"}]},"3070":{"script_id":"3070","0":"3070","script_name":"ShowMultiBase","1":"ShowMultiBase","script_type":"utility","2":"utility","summary":"Display a number in binary, octal, decimal and hexadecimal formats","3":"Display a number in binary, octal, decimal and hexadecimal formats","description":"This is a very simple script to display a number in all or some of binary, octal, decimal and hexadecimal formats at the same time.\r\n\r\nThere are several existing converter scripts available, which you might want to check:\r\n- vimscript #238 : Function to output a number as HEX\r\n- vimscript #1538 : Convert from base(2,8,10,16) to base(2-32). Also character to html entity.\r\n- vimscript #54 : Convert to\/from various numeric bases\r\n\r\nThe motivation of this script is a bit different, however. I often have to read logfiles with hexdumps and numbers with altering bases. Therefore, I want to see the binary, decimal and hexadecimal representations at the same time to help easier reading of these logfiles and to avoid using an external calculator as much as possible. In addition, I wanted to have more control over how the numbers are displayed that I can reuse the displayed numbers in e.g. reports.\r\n\r\nE.g, with the default settings, executing the :ShowMultiBase command, while the cursor is on the number 1234, you'll have the following output: b0100 1101 0010 == 02322 == 1234 == 0x04d2\r\nIf the number is e.g. hexadecimal, you can override the autosensed base (10) with :ShowMultiBase 16\r\n\r\nThe conversion utility functions are also available, but if you need a general conversion function, I recommend using vimscript #54.\r\nThere are several display configurations (e.g: bases to show, prefix usage, segmentation etc.), for details see the comments in the script!\r\n\r\nSyntax: :ShowMultiBase [base [number]]\r\nIf 'number' is not specified, the number under the cursor is taken as input. If 'base' is not specified, it is autosensed. If 'number' is given, 'base' must be also given, but 0 may be used to autosense.\r\n\r\nThe following mappings are created by default:\r\n\\=   Display the number under the cursor with autosensed base in the configured bases\r\n\\b=  Display the binary number under the cursor in the configured bases\r\n\\o=  Display the octal number under the cursor in the configured bases\r\n\\d=  Display the decimal number under the cursor in the configured bases\r\n\\h=  Display the hexadecimal number under the cursor in the configured bases\r\n","4":"This is a very simple script to display a number in all or some of binary, octal, decimal and hexadecimal formats at the same time.\r\n\r\nThere are several existing converter scripts available, which you might want to check:\r\n- vimscript #238 : Function to output a number as HEX\r\n- vimscript #1538 : Convert from base(2,8,10,16) to base(2-32). Also character to html entity.\r\n- vimscript #54 : Convert to\/from various numeric bases\r\n\r\nThe motivation of this script is a bit different, however. I often have to read logfiles with hexdumps and numbers with altering bases. Therefore, I want to see the binary, decimal and hexadecimal representations at the same time to help easier reading of these logfiles and to avoid using an external calculator as much as possible. In addition, I wanted to have more control over how the numbers are displayed that I can reuse the displayed numbers in e.g. reports.\r\n\r\nE.g, with the default settings, executing the :ShowMultiBase command, while the cursor is on the number 1234, you'll have the following output: b0100 1101 0010 == 02322 == 1234 == 0x04d2\r\nIf the number is e.g. hexadecimal, you can override the autosensed base (10) with :ShowMultiBase 16\r\n\r\nThe conversion utility functions are also available, but if you need a general conversion function, I recommend using vimscript #54.\r\nThere are several display configurations (e.g: bases to show, prefix usage, segmentation etc.), for details see the comments in the script!\r\n\r\nSyntax: :ShowMultiBase [base [number]]\r\nIf 'number' is not specified, the number under the cursor is taken as input. If 'base' is not specified, it is autosensed. If 'number' is given, 'base' must be also given, but 0 may be used to autosense.\r\n\r\nThe following mappings are created by default:\r\n\\=   Display the number under the cursor with autosensed base in the configured bases\r\n\\b=  Display the binary number under the cursor in the configured bases\r\n\\o=  Display the octal number under the cursor in the configured bases\r\n\\d=  Display the decimal number under the cursor in the configured bases\r\n\\h=  Display the hexadecimal number under the cursor in the configured bases\r\n","install_details":"Copy showmultibase.vim to your plugin folder (see http:\/\/vimdoc.sourceforge.net\/htmldoc\/options.html#%27runtimepath%27 to find out about where it is located on your OS)!\r\nIf you do not need the default mappings, add the following in your vimrc file and define your choice: let g:ShowMultiBase_UseDefaultMappings = 0\r\n","5":"Copy showmultibase.vim to your plugin folder (see http:\/\/vimdoc.sourceforge.net\/htmldoc\/options.html#%27runtimepath%27 to find out about where it is located on your OS)!\r\nIf you do not need the default mappings, add the following in your vimrc file and define your choice: let g:ShowMultiBase_UseDefaultMappings = 0\r\n","first_name":"Lajos","6":"Lajos","last_name":"Zaccomer","7":"Zaccomer","releases":[{"0":"3070","vim_version":"8.0","1":"8.0","script_version":"1.1","2":"1.1","version_comment":"- selection support\r\n- Ian Munsie bugfix: Oct\/Hex\/Dec FillSegment, SegmentSize configuration fix for Register and Display","3":"- selection support\r\n- Ian Munsie bugfix: Oct\/Hex\/Dec FillSegment, SegmentSize configuration fix for Register and Display","package":"showmultibase.vim","4":"showmultibase.vim","src_id":"27067","5":"27067","creation_date":"1583885590","6":"1583885590"},{"0":"3070","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Save results in registers. Independent configuration of parsing, display and register formats (sorry, backward incompatible).","3":"Save results in registers. Independent configuration of parsing, display and register formats (sorry, backward incompatible).","package":"showmultibase.vim","4":"showmultibase.vim","src_id":"13922","5":"13922","creation_date":"1285510228","6":"1285510228"},{"0":"3070","vim_version":"7.0","1":"7.0","script_version":"0.2","2":"0.2","version_comment":"- Mun Johl reported problem with 32< bit numbers. Fixed with using float instead of number, so the handled range is considerably increased and limited only by VIM's float precision (see :help floating-point-precision).\r\n- Fixed removal of leading zero digits\r\n- Mandatory leading 1 in binary removed\r\n- Default binary display segment size changed from 4 to 8","3":"- Mun Johl reported problem with 32< bit numbers. Fixed with using float instead of number, so the handled range is considerably increased and limited only by VIM's float precision (see :help floating-point-precision).\r\n- Fixed removal of leading zero digits\r\n- Mandatory leading 1 in binary removed\r\n- Default binary display segment size changed from 4 to 8","package":"showmultibase.vim","4":"showmultibase.vim","src_id":"13710","5":"13710","creation_date":"1283072570","6":"1283072570"},{"0":"3070","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"showmultibase.vim","4":"showmultibase.vim","src_id":"12884","5":"12884","creation_date":"1271882430","6":"1271882430"}]},"3069":{"script_id":"3069","0":"3069","script_name":"Slidedown Syntax","1":"Slidedown Syntax","script_type":"syntax","2":"syntax","summary":"highlighting for the Slidedown presentation tool","3":"highlighting for the Slidedown presentation tool","description":"Adds syntax highlighting for the Slidedown presentation software (http:\/\/github.com\/nakajima\/slidedown).  Requires that some Markdown syntax file be available.","4":"Adds syntax highlighting for the Slidedown presentation software (http:\/\/github.com\/nakajima\/slidedown).  Requires that some Markdown syntax file be available.","install_details":"Use Pathogen (http:\/\/www.vim.org\/scripts\/script.php?script_id=2332) and un-tar into ~\/.vim\/bundle \r\n\r\nOr, un-tar and copy the contents of the ftdetect and syntax directories into the corresponding directories in ~\/.vim, creating them if necessary.\r\n","5":"Use Pathogen (http:\/\/www.vim.org\/scripts\/script.php?script_id=2332) and un-tar into ~\/.vim\/bundle \r\n\r\nOr, un-tar and copy the contents of the ftdetect and syntax directories into the corresponding directories in ~\/.vim, creating them if necessary.\r\n","first_name":"Ben","6":"Ben","last_name":"Bleything","7":"Bleything","releases":[{"0":"3069","vim_version":"7.2","1":"7.2","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"vim-slidedown.tgz","4":"vim-slidedown.tgz","src_id":"12880","5":"12880","creation_date":"1271830165","6":"1271830165"}]},"3068":{"script_id":"3068","0":"3068","script_name":"recover.vim","1":"recover.vim","script_type":"utility","2":"utility","summary":"Show differences for recovered files","3":"Show differences for recovered files","description":"Please rate the plugin, if you like it!\r\n\r\n2. recover Manual                                       *recover-manual*\r\n\r\nFunctionality\r\n\r\nWhen using |recovery|, it is hard to tell, what has been changed between the\r\nrecovered file and the actual on disk version. The aim of this plugin is, to\r\nhave an easy way to see differences, between the recovered files and the files\r\nrestored on disk.\r\n\r\nTherefore this plugin sets up an auto command, that will create a diff buffer\r\nbetween the recovered file and the on-disk version of the same file. You can\r\neasily see, what has been changed and save your recovered work back to the\r\nfile on disk.\r\n\r\nBy default this plugin is enabled. To disable it, use >\r\n    :RecoverPluginDisable\r\n\r\nTo enable this plugin again, use >\r\n    :RecoverPluginEnable\r\n\r\n3. ChangesPlugin Feedback                                   *recover-feedback*\r\n\r\nFeedback is always welcome. If you like the plugin, please rate it at the\r\nvim-page:\r\nhttp:\/\/www.vim.org\/scripts\/script.php?script_id=3068\r\n\r\nYou can also follow the development of the plugin at github:\r\nhttp:\/\/github.com\/chrisbra\/Recover.vim\r\n\r\nPlease don't hesitate to report any bugs to the maintainer, mentioned in the\r\nthird line of this document.\r\n","4":"Please rate the plugin, if you like it!\r\n\r\n2. recover Manual                                       *recover-manual*\r\n\r\nFunctionality\r\n\r\nWhen using |recovery|, it is hard to tell, what has been changed between the\r\nrecovered file and the actual on disk version. The aim of this plugin is, to\r\nhave an easy way to see differences, between the recovered files and the files\r\nrestored on disk.\r\n\r\nTherefore this plugin sets up an auto command, that will create a diff buffer\r\nbetween the recovered file and the on-disk version of the same file. You can\r\neasily see, what has been changed and save your recovered work back to the\r\nfile on disk.\r\n\r\nBy default this plugin is enabled. To disable it, use >\r\n    :RecoverPluginDisable\r\n\r\nTo enable this plugin again, use >\r\n    :RecoverPluginEnable\r\n\r\n3. ChangesPlugin Feedback                                   *recover-feedback*\r\n\r\nFeedback is always welcome. If you like the plugin, please rate it at the\r\nvim-page:\r\nhttp:\/\/www.vim.org\/scripts\/script.php?script_id=3068\r\n\r\nYou can also follow the development of the plugin at github:\r\nhttp:\/\/github.com\/chrisbra\/Recover.vim\r\n\r\nPlease don't hesitate to report any bugs to the maintainer, mentioned in the\r\nthird line of this document.\r\n","install_details":"This plugin comes as vimball, which makes it really easy to install it\r\ninto the right place.\r\n1) Edit recover.vba with your vim (:e recover.vba)\r\n2) From within vim, simply source the file (using :so %)\r\n3) Restart vim to autoload the plugin and the documentation (:q)\r\n4) Read the help at :h recoverPlugin\r\n","5":"This plugin comes as vimball, which makes it really easy to install it\r\ninto the right place.\r\n1) Edit recover.vba with your vim (:e recover.vba)\r\n2) From within vim, simply source the file (using :so %)\r\n3) Restart vim to autoload the plugin and the documentation (:q)\r\n4) Read the help at :h recoverPlugin\r\n","first_name":"Christian","6":"Christian","last_name":"Brabandt","7":"Brabandt","releases":[{"0":"3068","vim_version":"7.3","1":"7.3","script_version":"19","2":"19","version_comment":"- fix issue 29 (plugin always loaded autoload part, https:\/\/github.com\/chrisbra\/Recover.vim\/issues\/29, reported by Justin Keyes, thanks!)\n- fix issue 30 (remove needless 2 second sleep, https:\/\/github.com\/chrisbra\/Recover.vim\/issues\/30, reported by Justin Keyes, thanks!)\n- only reset swapfile option, if the current buffer has a name\n- :RecoverPluginGet to easily get the recovered version into your buffer and finish everything up (issue 31 https:\/\/github.com\/chrisbra\/Recover.vim\/issues\/31, reported by luxigo, thanks!)","3":"- fix issue 29 (plugin always loaded autoload part, https:\/\/github.com\/chrisbra\/Recover.vim\/issues\/29, reported by Justin Keyes, thanks!)\n- fix issue 30 (remove needless 2 second sleep, https:\/\/github.com\/chrisbra\/Recover.vim\/issues\/30, reported by Justin Keyes, thanks!)\n- only reset swapfile option, if the current buffer has a name\n- :RecoverPluginGet to easily get the recovered version into your buffer and finish everything up (issue 31 https:\/\/github.com\/chrisbra\/Recover.vim\/issues\/31, reported by luxigo, thanks!)","package":"Recover-0.19.vmb","4":"Recover-0.19.vmb","src_id":"22800","5":"22800","creation_date":"1421354233","6":"1421354233"},{"0":"3068","vim_version":"7.3","1":"7.3","script_version":"18","2":"18","version_comment":"- fix issue 19 (https:\/\/github.com\/chrisbra\/Recover.vim\/issues\/19, by\nreplacing feedkeys(\"...\\n\") by feedkeys(\"...\\<cr>\", reported by vlmarek,\nthanks!)\n- fix issue 20 (https:\/\/github.com\/chrisbra\/Recover.vim\/issues\/20,\n(let vim automatically edit a file, that is unmodified in another vim\ninstance, suggested by rking, thanks!)\n- merge issue 21 (https:\/\/github.com\/chrisbra\/Recover.vim\/pull\/21, create more\nusefule README.md file, contribted by Shubham Rao, thanks!)\n- merge issue 22 (https:\/\/github.com\/chrisbra\/Recover.vim\/pull\/22, delete BufReadPost autocommand\ncontributed by Marcin Szamotulski, thanks!)","3":"- fix issue 19 (https:\/\/github.com\/chrisbra\/Recover.vim\/issues\/19, by\nreplacing feedkeys(\"...\\n\") by feedkeys(\"...\\<cr>\", reported by vlmarek,\nthanks!)\n- fix issue 20 (https:\/\/github.com\/chrisbra\/Recover.vim\/issues\/20,\n(let vim automatically edit a file, that is unmodified in another vim\ninstance, suggested by rking, thanks!)\n- merge issue 21 (https:\/\/github.com\/chrisbra\/Recover.vim\/pull\/21, create more\nusefule README.md file, contribted by Shubham Rao, thanks!)\n- merge issue 22 (https:\/\/github.com\/chrisbra\/Recover.vim\/pull\/22, delete BufReadPost autocommand\ncontributed by Marcin Szamotulski, thanks!)","package":"Recover-0.18.vmb","4":"Recover-0.18.vmb","src_id":"20655","5":"20655","creation_date":"1376549520","6":"1376549520"},{"0":"3068","vim_version":"7.3","1":"7.3","script_version":"18","2":"18","version_comment":"- fix issue 19 (https:\/\/github.com\/chrisbra\/Recover.vim\/issues\/19)\n- fix issue 20 (https:\/\/github.com\/chrisbra\/Recover.vim\/issues\/20)\n- merge issue 21 (https:\/\/github.com\/chrisbra\/Recover.vim\/pull\/21\n- merge issue 22 (https:\/\/github.com\/chrisbra\/Recover.vim\/pull\/22, delete BufReadPost autocommand\n  contributed by Marcin Szamotulski, thanks!)","3":"- fix issue 19 (https:\/\/github.com\/chrisbra\/Recover.vim\/issues\/19)\n- fix issue 20 (https:\/\/github.com\/chrisbra\/Recover.vim\/issues\/20)\n- merge issue 21 (https:\/\/github.com\/chrisbra\/Recover.vim\/pull\/21\n- merge issue 22 (https:\/\/github.com\/chrisbra\/Recover.vim\/pull\/22, delete BufReadPost autocommand\n  contributed by Marcin Szamotulski, thanks!)","package":"Recover-0.18.vmb","4":"Recover-0.18.vmb","src_id":"20654","5":"20654","creation_date":"1376549420","6":"1376549420"},{"0":"3068","vim_version":"7.3","1":"7.3","script_version":"17","2":"17","version_comment":"- fix issue 17 (https:\/\/github.com\/chrisbra\/Recover.vim\/issues\/17 patch by\n  lyokha, thanks!)\n- Use default key combinations in the dialog of the normal Vim dialog (adding\n  only the Diff option)\n- Make sure, the process ID is shown","3":"- fix issue 17 (https:\/\/github.com\/chrisbra\/Recover.vim\/issues\/17 patch by\n  lyokha, thanks!)\n- Use default key combinations in the dialog of the normal Vim dialog (adding\n  only the Diff option)\n- Make sure, the process ID is shown","package":"Recover-0.17.vmb","4":"Recover-0.17.vmb","src_id":"19524","5":"19524","creation_date":"1361052313","6":"1361052313"},{"0":"3068","vim_version":"7.3","1":"7.3","script_version":"16","2":"16","version_comment":"- Recovery did not work, when original file did not exists (issue 11 \n  https:\/\/github.com\/chrisbra\/Recover.vim\/issues\/11\n  reported by Rking, thanks!)\n- By default, delete swapfile, if no differences found (issue 15\n  https:\/\/github.com\/chrisbra\/Recover.vim\/issues\/15\n  reported by Rking, thanks!)\n- reset swapfile option, so that Vim by default creates .swp files\n  (idea and patch by Marcin Szamotulski, thanks!)\n- capture and display |E325| message (and also try to figure out the name of\n  the pid (issue 12 https:\/\/github.com\/chrisbra\/Recover.vim\/issues\/12)","3":"- Recovery did not work, when original file did not exists (issue 11 \n  https:\/\/github.com\/chrisbra\/Recover.vim\/issues\/11\n  reported by Rking, thanks!)\n- By default, delete swapfile, if no differences found (issue 15\n  https:\/\/github.com\/chrisbra\/Recover.vim\/issues\/15\n  reported by Rking, thanks!)\n- reset swapfile option, so that Vim by default creates .swp files\n  (idea and patch by Marcin Szamotulski, thanks!)\n- capture and display |E325| message (and also try to figure out the name of\n  the pid (issue 12 https:\/\/github.com\/chrisbra\/Recover.vim\/issues\/12)","package":"Recover-0.16.vmb","4":"Recover-0.16.vmb","src_id":"19011","5":"19011","creation_date":"1353533106","6":"1353533106"},{"0":"3068","vim_version":"7.3","1":"7.3","script_version":"15","2":"15","version_comment":"- fix issue 5 (https:\/\/github.com\/chrisbra\/Recover.vim\/issues\/5 patch by lyokha, thanks!)\n- CheckSwapFileExists() hangs, when a swap file was not found, make sure,\n  s:Swapname() returns a valid file name\n- fix issue 6 (https:\/\/github.com\/chrisbra\/Recover.vim\/issues\/6 patch by\n  lyokha, thanks!)\n- Avoid recursive :redir call (https:\/\/github.com\/chrisbra\/Recover.vim\/pull\/8\n  patch by Ingo Karkat, thanks!)\n- Do not set 'bexpr' for unrelated buffers (\n  https:\/\/github.com\/chrisbra\/Recover.vim\/pull\/9 patch by Ingo Karkat,\n  thanks!)\n- Avoid aborting the diff (https:\/\/github.com\/chrisbra\/Recover.vim\/pull\/10\n  patch by Ingo Karkat, thanks!)\n- Allow to directly delete the swapfile (\n  https:\/\/github.com\/chrisbra\/Recover.vim\/issues\/7 suggested by jgandt,\n  thanks!)","3":"- fix issue 5 (https:\/\/github.com\/chrisbra\/Recover.vim\/issues\/5 patch by lyokha, thanks!)\n- CheckSwapFileExists() hangs, when a swap file was not found, make sure,\n  s:Swapname() returns a valid file name\n- fix issue 6 (https:\/\/github.com\/chrisbra\/Recover.vim\/issues\/6 patch by\n  lyokha, thanks!)\n- Avoid recursive :redir call (https:\/\/github.com\/chrisbra\/Recover.vim\/pull\/8\n  patch by Ingo Karkat, thanks!)\n- Do not set 'bexpr' for unrelated buffers (\n  https:\/\/github.com\/chrisbra\/Recover.vim\/pull\/9 patch by Ingo Karkat,\n  thanks!)\n- Avoid aborting the diff (https:\/\/github.com\/chrisbra\/Recover.vim\/pull\/10\n  patch by Ingo Karkat, thanks!)\n- Allow to directly delete the swapfile (\n  https:\/\/github.com\/chrisbra\/Recover.vim\/issues\/7 suggested by jgandt,\n  thanks!)","package":"Recover-0.15.vmb","4":"Recover-0.15.vmb","src_id":"18443","5":"18443","creation_date":"1345486659","6":"1345486659"},{"0":"3068","vim_version":"7.3","1":"7.3","script_version":"14","2":"14","version_comment":"-Finally fix issue #4\nhttps:\/\/github.com\/chrisbra\/Recover.vim\/issues\/4","3":"-Finally fix issue #4\nhttps:\/\/github.com\/chrisbra\/Recover.vim\/issues\/4","package":"Recover-0.14.vmb","4":"Recover-0.14.vmb","src_id":"17694","5":"17694","creation_date":"1333193423","6":"1333193423"},{"0":"3068","vim_version":"7.3","1":"7.3","script_version":"13","2":"13","version_comment":"\n- fix issue 3 (\nhttps:\/\/github.com\/chrisbra\/Recover.vim\/issues\/3\nreported by lyokha, thanks!)\n- Ask the user to delete the swapfile\n(https:\/\/github.com\/chrisbra\/Recover.vim\/issues\/4\nreported by lyokha, thanks!)","3":"\n- fix issue 3 (\nhttps:\/\/github.com\/chrisbra\/Recover.vim\/issues\/3\nreported by lyokha, thanks!)\n- Ask the user to delete the swapfile\n(https:\/\/github.com\/chrisbra\/Recover.vim\/issues\/4\nreported by lyokha, thanks!)","package":"Recover-0.13.vmb","4":"Recover-0.13.vmb","src_id":"17690","5":"17690","creation_date":"1333055421","6":"1333055421"},{"0":"3068","vim_version":"7.3","1":"7.3","script_version":"12","2":"12","version_comment":"- minor documentation update\n- delete swap files, if no difference found (issue https:\/\/github.com\/chrisbra\/Recover.vim\/issues\/1 reported by y, thanks!)\n- fix some small issues, that prevented the development versions from working (https:\/\/github.com\/chrisbra\/Recover.vim\/issues\/2 reported by Rahul Kumar, thanks!)","3":"- minor documentation update\n- delete swap files, if no difference found (issue https:\/\/github.com\/chrisbra\/Recover.vim\/issues\/1 reported by y, thanks!)\n- fix some small issues, that prevented the development versions from working (https:\/\/github.com\/chrisbra\/Recover.vim\/issues\/2 reported by Rahul Kumar, thanks!)","package":"Recover-0.12.vmb","4":"Recover-0.12.vmb","src_id":"17658","5":"17658","creation_date":"1332701660","6":"1332701660"},{"0":"3068","vim_version":"7.3","1":"7.3","script_version":"11","2":"11","version_comment":"use confirm() instead of inputdialog (suggested by D.Fishburn, thanks!)","3":"use confirm() instead of inputdialog (suggested by D.Fishburn, thanks!)","package":"Recover-0.11.vba","4":"Recover-0.11.vba","src_id":"14097","5":"14097","creation_date":"1287694640","6":"1287694640"},{"0":"3068","vim_version":"7.0","1":"7.0","script_version":"0.9","2":"0.9","version_comment":": use feedkeys(...,'t') instead of feedkeys()  (this works more reliable, although it pollutes the history), so delete those\r\n  spurious history entries\r\n: |RecoverPluginHelp| shows a small help message, about diff commands (suggested by David Fishburn, thanks!)\r\n: |RecoverPluginFinish| is a shortcut for |FinishRecovery|\r\n","3":": use feedkeys(...,'t') instead of feedkeys()  (this works more reliable, although it pollutes the history), so delete those\r\n  spurious history entries\r\n: |RecoverPluginHelp| shows a small help message, about diff commands (suggested by David Fishburn, thanks!)\r\n: |RecoverPluginFinish| is a shortcut for |FinishRecovery|\r\n","package":"Recover-0.9.vba","4":"Recover-0.9.vba","src_id":"13091","5":"13091","creation_date":"1275500532","6":"1275500532"},{"0":"3068","vim_version":"7.0","1":"7.0","script_version":"0.8","2":"0.8","version_comment":"0.8:\r\n:make :FinishRecovery more robust\r\n0.7 (unreleased):\r\n|FinishRecovery| closes the diff-window and cleans everything up (suggestion by David Fishburn)\r\n:DeleteSwapFile is not needed anymore","3":"0.8:\r\n:make :FinishRecovery more robust\r\n0.7 (unreleased):\r\n|FinishRecovery| closes the diff-window and cleans everything up (suggestion by David Fishburn)\r\n:DeleteSwapFile is not needed anymore","package":"Recover-0.8.vba","4":"Recover-0.8.vba","src_id":"13083","5":"13083","creation_date":"1275418621","6":"1275418621"},{"0":"3068","vim_version":"7.0","1":"7.0","script_version":"0.6","2":"0.6","version_comment":": |recover-feedback|\r\n: Ask to really open a diff buffer for a file (suggestion: David Fishburn, thanks!)\r\n: DeleteSwapFile to delete the swap file, that was used to create the diff buffer\r\n: change feedkeys(...,'t') to feedkeys('..') so that not every command appears in the history.\r\n","3":": |recover-feedback|\r\n: Ask to really open a diff buffer for a file (suggestion: David Fishburn, thanks!)\r\n: DeleteSwapFile to delete the swap file, that was used to create the diff buffer\r\n: change feedkeys(...,'t') to feedkeys('..') so that not every command appears in the history.\r\n","package":"Recover-0.6.vba","4":"Recover-0.6.vba","src_id":"13080","5":"13080","creation_date":"1275338645","6":"1275338645"},{"0":"3068","vim_version":"7.0","1":"7.0","script_version":"0.5","2":"0.5","version_comment":"-0r command in recover plugin adds extra \\n\r\n  Patch by Sergey Khorev (Thanks!)\r\n- generate help file with 'et' set, so the README at github looks prettier","3":"-0r command in recover plugin adds extra \\n\r\n  Patch by Sergey Khorev (Thanks!)\r\n- generate help file with 'et' set, so the README at github looks prettier","package":"Recover-0.5.vba","4":"Recover-0.5.vba","src_id":"12943","5":"12943","creation_date":"1273002881","6":"1273002881"},{"0":"3068","vim_version":"7.0","1":"7.0","script_version":"0.4","2":"0.4","version_comment":"0.4: Apr 26, 2010: \r\n- handle Windows and Unix path differently\r\n- Code cleanup\r\n- Enabled |:GLVS|\r\n","3":"0.4: Apr 26, 2010: \r\n- handle Windows and Unix path differently\r\n- Code cleanup\r\n- Enabled |:GLVS|\r\n","package":"recover.vba","4":"recover.vba","src_id":"12903","5":"12903","creation_date":"1272317233","6":"1272317233"},{"0":"3068","vim_version":"7.2","1":"7.2","script_version":"0.3","2":"0.3","version_comment":"Initial upload","3":"Initial upload","package":"recover.vba","4":"recover.vba","src_id":"12879","5":"12879","creation_date":"1271801233","6":"1271801233"}]},"3067":{"script_id":"3067","0":"3067","script_name":"ref.vim","1":"ref.vim","script_type":"utility","2":"utility","summary":"Integrated reference viewer.","3":"Integrated reference viewer.","description":"*ref* is a Vim plugin to view the reference.  This plugin can be separated to\r\ncore of viewer and sources of reference.  As a result, various references can\r\nbe viewed by the same interface.\r\n\r\nFollowing sources are included in this plugin:\r\n- alc (Online English-Japanese\/Japanese-English dictionary)\r\n- clojure\r\n- erlang\r\n- hoogle\r\n- man\r\n- perldoc\r\n- phpmanual\r\n- pydoc\r\n- refe\r\n\r\nReference viewer is mere a buffer to view the reference.  This is opened by :Ref\r\ncommand or K like :help.  If the reference viewer is already opened in current\r\ntab page, it is used again.\r\n\r\nThis also includes unite-ref for unite.vim(vimscript #3396).\r\n\r\nLatest Version:\r\nhttps:\/\/github.com\/thinca\/vim-ref","4":"*ref* is a Vim plugin to view the reference.  This plugin can be separated to\r\ncore of viewer and sources of reference.  As a result, various references can\r\nbe viewed by the same interface.\r\n\r\nFollowing sources are included in this plugin:\r\n- alc (Online English-Japanese\/Japanese-English dictionary)\r\n- clojure\r\n- erlang\r\n- hoogle\r\n- man\r\n- perldoc\r\n- phpmanual\r\n- pydoc\r\n- refe\r\n\r\nReference viewer is mere a buffer to view the reference.  This is opened by :Ref\r\ncommand or K like :help.  If the reference viewer is already opened in current\r\ntab page, it is used again.\r\n\r\nThis also includes unite-ref for unite.vim(vimscript #3396).\r\n\r\nLatest Version:\r\nhttps:\/\/github.com\/thinca\/vim-ref","install_details":"","5":"","first_name":"thinca","6":"thinca","last_name":" ","7":" ","releases":[{"0":"3067","vim_version":"7.2","1":"7.2","script_version":"0.4.3","2":"0.4.3","version_comment":"- Added ref#rmcache().\r\n- g:ref_detect_filetype accepts a list of sources.\r\n- A function of g:ref_detect_filetype can return a Funcref.\r\n- Improved ref#register_detection().\r\n- ref-source-attr-available() became omitable.\r\n- Fixed the bug to which {name} including \"\/\" can not be taken out by ref#cache().\r\n- Fixed a bug when a list including empty string is passed to ref#uniq().\r\n\r\nThere are a lot of changes from 0.3.1.  See :help ref-changelog .","3":"- Added ref#rmcache().\r\n- g:ref_detect_filetype accepts a list of sources.\r\n- A function of g:ref_detect_filetype can return a Funcref.\r\n- Improved ref#register_detection().\r\n- ref-source-attr-available() became omitable.\r\n- Fixed the bug to which {name} including \"\/\" can not be taken out by ref#cache().\r\n- Fixed a bug when a list including empty string is passed to ref#uniq().\r\n\r\nThere are a lot of changes from 0.3.1.  See :help ref-changelog .","package":"vim-ref-0.4.3.zip","4":"vim-ref-0.4.3.zip","src_id":"14809","5":"14809","creation_date":"1295541266","6":"1295541266"},{"0":"3067","vim_version":"7.0","1":"7.0","script_version":"0.3.1","2":"0.3.1","version_comment":"- |g:ref_detect_filetype| accepts a special key _.\r\n- |g:ref_detect_filetype| accepts |Funcref|.\r\n- refe\r\n  - Fixed the collapses page of the method of refe1.","3":"- |g:ref_detect_filetype| accepts a special key _.\r\n- |g:ref_detect_filetype| accepts |Funcref|.\r\n- refe\r\n  - Fixed the collapses page of the method of refe1.","package":"vim-ref-0.3.1.zip","4":"vim-ref-0.3.1.zip","src_id":"12882","5":"12882","creation_date":"1271871357","6":"1271871357"},{"0":"3067","vim_version":"7.2","1":"7.2","script_version":"0.3.0","2":"0.3.0","version_comment":"Initial upload","3":"Initial upload","package":"vim-ref-0.3.0.zip","4":"vim-ref-0.3.0.zip","src_id":"12869","5":"12869","creation_date":"1271693577","6":"1271693577"}]},"3066":{"script_id":"3066","0":"3066","script_name":"repeater.vim","1":"repeater.vim","script_type":"utility","2":"utility","summary":"Repeat an item {n} times","3":"Repeat an item {n} times","description":"Repeater.vim allows you to repeat items {n} times. For example, if you have a\r\nsection header in ReStructuredText and you need to insert an underbar of\r\nequals signs that's the same length, you can simply move down a line and\r\ninvoke ``:Repeater =``. You can also specify a length, but the real utility of\r\nthis plugin is calculating the length for you.\r\n\r\nExamples\r\n========\r\n\r\n1. Insert 78 equals signs:\r\n    :Repeater = 78\r\n2. Insert a ReST or Markdown section header for the current line:\r\n    :Repeater -\r\n3. Insert \"THIS IS FILLER\" 999 times:\r\n    :Repeater THIS\\ IS\\ FILLER.\\  999\r\n","4":"Repeater.vim allows you to repeat items {n} times. For example, if you have a\r\nsection header in ReStructuredText and you need to insert an underbar of\r\nequals signs that's the same length, you can simply move down a line and\r\ninvoke ``:Repeater =``. You can also specify a length, but the real utility of\r\nthis plugin is calculating the length for you.\r\n\r\nExamples\r\n========\r\n\r\n1. Insert 78 equals signs:\r\n    :Repeater = 78\r\n2. Insert a ReST or Markdown section header for the current line:\r\n    :Repeater -\r\n3. Insert \"THIS IS FILLER\" 999 times:\r\n    :Repeater THIS\\ IS\\ FILLER.\\  999\r\n","install_details":"1. Download repeater.zip and unzip to \".vim\" or \"vimfiles\"\r\n        unzip -d ~\/.vim repeater-1.0.0.zip\r\n2. :helptags ~\/.vim\/doc\r\n","5":"1. Download repeater.zip and unzip to \".vim\" or \"vimfiles\"\r\n        unzip -d ~\/.vim repeater-1.0.0.zip\r\n2. :helptags ~\/.vim\/doc\r\n","first_name":"Jon-Michael","6":"Jon-Michael","last_name":"Deldin","7":"Deldin","releases":[{"0":"3066","vim_version":"7.0","1":"7.0","script_version":"1.0.0","2":"1.0.0","version_comment":"Initial upload","3":"Initial upload","package":"repeater-1.0.0.zip","4":"repeater-1.0.0.zip","src_id":"12865","5":"12865","creation_date":"1271664841","6":"1271664841"}]},"3065":{"script_id":"3065","0":"3065","script_name":"mayansmoke","1":"mayansmoke","script_type":"color scheme","2":"color scheme","summary":"Ergonomic light-background color scheme.","3":"Ergonomic light-background color scheme.","description":"This is a pleasant and ergonomic light-background color scheme, designed for long hours of coding and working. The UI elements are muted without being drab, the syntax elements are colorful without being garish, and the background is relaxing without being soporific. It is of a low-enough contrast so as not to cause eye-burn, but high-enough contrast so as not to cause eye-strain. The syntax coloration offers just a little higher resolution than most, distinguishing between class names vs. functions, strings and numbers vs. other constants, etc. Many of the colors in this color scheme are drawn from Mayan murals, paintings and codices, and thus the name.\r\n\r\nScreenshots:\r\n==========\r\n\r\n    http:\/\/jeetworks.org\/mayansmoke\r\n\r\nCustomization:\r\n==============\r\n\r\nIf any of the following highlights are defined (e.g., in your \"~\/.vimrc\"), these will override the default highlight definitions:\r\n\r\n    MayanSmokeCursorLine    (will be applied to: CursorColumn and CursorLine)\r\n    MayanSmokeSearch        (will be applied to: Search and IncSearch)\r\n    MayanSmokeSpecialKey    (will be applied to: SpecialKey)\r\n\r\nFor example, you can set the following in your \"~\/.vimrc\" to select your own colors for these items:\r\n\r\n    hi MayanSmokeCursorLine     guifg=NONE   guibg=yellow  gui=NONE\r\n    hi MayanSmokeSearch         guifg=white  guibg=blue    gui=NONE\r\n    hi MayanSmokeSpecialKey     guifg=NONE   guibg=green   gui=NONE\r\n\r\nAlternatively, you can define one or more of the following values in your \"~\/.vimrc\" to select different pre-defined levels of visibility for the above highlights:\r\n\r\n    let g:mayansmoke_cursor_line_visibility = 0  \" lower visibility\r\n    let g:mayansmoke_cursor_line_visibility = 1  \" medium visibility\r\n    let g:mayansmoke_cursor_line_visibility = 2  \" higher visibility\r\n\r\n   let g:mayansmoke_search_visibility = 0 \" low visibility\r\n   let g:mayansmoke_search_visibility = 1 \" medium visibility (default)\r\n   let g:mayansmoke_search_visibility = 2 \" high visibility\r\n   let g:mayansmoke_search_visibility = 3 \" very high visibility\r\n   let g:mayansmoke_search_visibility = 4 \" highest visibility\r\n\r\n    let g:mayansmoke_special_key_visibility = 0  \" lower visibility\r\n    let g:mayansmoke_special_key_visibility = 1  \" medium visibility\r\n    let g:mayansmoke_special_key_visibility = 2  \" higher visibility\r\n\r\n\r\n","4":"This is a pleasant and ergonomic light-background color scheme, designed for long hours of coding and working. The UI elements are muted without being drab, the syntax elements are colorful without being garish, and the background is relaxing without being soporific. It is of a low-enough contrast so as not to cause eye-burn, but high-enough contrast so as not to cause eye-strain. The syntax coloration offers just a little higher resolution than most, distinguishing between class names vs. functions, strings and numbers vs. other constants, etc. Many of the colors in this color scheme are drawn from Mayan murals, paintings and codices, and thus the name.\r\n\r\nScreenshots:\r\n==========\r\n\r\n    http:\/\/jeetworks.org\/mayansmoke\r\n\r\nCustomization:\r\n==============\r\n\r\nIf any of the following highlights are defined (e.g., in your \"~\/.vimrc\"), these will override the default highlight definitions:\r\n\r\n    MayanSmokeCursorLine    (will be applied to: CursorColumn and CursorLine)\r\n    MayanSmokeSearch        (will be applied to: Search and IncSearch)\r\n    MayanSmokeSpecialKey    (will be applied to: SpecialKey)\r\n\r\nFor example, you can set the following in your \"~\/.vimrc\" to select your own colors for these items:\r\n\r\n    hi MayanSmokeCursorLine     guifg=NONE   guibg=yellow  gui=NONE\r\n    hi MayanSmokeSearch         guifg=white  guibg=blue    gui=NONE\r\n    hi MayanSmokeSpecialKey     guifg=NONE   guibg=green   gui=NONE\r\n\r\nAlternatively, you can define one or more of the following values in your \"~\/.vimrc\" to select different pre-defined levels of visibility for the above highlights:\r\n\r\n    let g:mayansmoke_cursor_line_visibility = 0  \" lower visibility\r\n    let g:mayansmoke_cursor_line_visibility = 1  \" medium visibility\r\n    let g:mayansmoke_cursor_line_visibility = 2  \" higher visibility\r\n\r\n   let g:mayansmoke_search_visibility = 0 \" low visibility\r\n   let g:mayansmoke_search_visibility = 1 \" medium visibility (default)\r\n   let g:mayansmoke_search_visibility = 2 \" high visibility\r\n   let g:mayansmoke_search_visibility = 3 \" very high visibility\r\n   let g:mayansmoke_search_visibility = 4 \" highest visibility\r\n\r\n    let g:mayansmoke_special_key_visibility = 0  \" lower visibility\r\n    let g:mayansmoke_special_key_visibility = 1  \" medium visibility\r\n    let g:mayansmoke_special_key_visibility = 2  \" higher visibility\r\n\r\n\r\n","install_details":"Download\/save\/copy\/move the file \"mayansmoke.vim\" to your \"$VIMRUNTIME\/colors\" directory (e.g., \"~\/.vim\/colors\"). Activate the color scheme by entering the command, \":colors mayansmoke\".","5":"Download\/save\/copy\/move the file \"mayansmoke.vim\" to your \"$VIMRUNTIME\/colors\" directory (e.g., \"~\/.vim\/colors\"). Activate the color scheme by entering the command, \":colors mayansmoke\".","first_name":"Jeet","6":"Jeet","last_name":"Sukumaran","7":"Sukumaran","releases":[{"0":"3065","vim_version":"7.0","1":"7.0","script_version":"2.0","2":"2.0","version_comment":"Rework of some \"trimming\" elements (line number column, status line etc.). I think it looks a lot nicer than 1.x!","3":"Rework of some \"trimming\" elements (line number column, status line etc.). I think it looks a lot nicer than 1.x!","package":"mayansmoke.vim","4":"mayansmoke.vim","src_id":"14049","5":"14049","creation_date":"1286955738","6":"1286955738"},{"0":"3065","vim_version":"7.0","1":"7.0","script_version":"1.8","2":"1.8","version_comment":"* Added CursorColumn highlight definition.\r\n* Reworked popup menu highlights: much more harmonious with the rest of the scheme.\r\n* Match-parens color to white-on-blue.\r\n* Special key and non-text colors toned down.\r\n* Fold column color lightened up.\r\n","3":"* Added CursorColumn highlight definition.\r\n* Reworked popup menu highlights: much more harmonious with the rest of the scheme.\r\n* Match-parens color to white-on-blue.\r\n* Special key and non-text colors toned down.\r\n* Fold column color lightened up.\r\n","package":"mayansmoke.vim","4":"mayansmoke.vim","src_id":"13943","5":"13943","creation_date":"1285615014","6":"1285615014"},{"0":"3065","vim_version":"7.0","1":"7.0","script_version":"1.7","2":"1.7","version_comment":"Added more flexibility in customizing colors. Reduced garishness of search highlight color.","3":"Added more flexibility in customizing colors. Reduced garishness of search highlight color.","package":"mayansmoke.vim","4":"mayansmoke.vim","src_id":"13799","5":"13799","creation_date":"1284087473","6":"1284087473"},{"0":"3065","vim_version":"7.0","1":"7.0","script_version":"1.6","2":"1.6","version_comment":"Improved Search, QuickFix and changed DiffText colors (GUI mode).","3":"Improved Search, QuickFix and changed DiffText colors (GUI mode).","package":"mayansmoke.vim","4":"mayansmoke.vim","src_id":"13746","5":"13746","creation_date":"1283473539","6":"1283473539"},{"0":"3065","vim_version":"6.0","1":"6.0","script_version":"1.5","2":"1.5","version_comment":"Added PHP syntax colors, contributed by Ryan Kulla.","3":"Added PHP syntax colors, contributed by Ryan Kulla.","package":"mayansmoke.vim","4":"mayansmoke.vim","src_id":"13314","5":"13314","creation_date":"1278775634","6":"1278775634"},{"0":"3065","vim_version":"6.0","1":"6.0","script_version":"1.4","2":"1.4","version_comment":"* 256-color terminal mode colors, added by Clayton Parker.\r\n* Cursor line (and column) visibility can be customized by the g:mayansmoke_cursor_line_visibility variable.\r\n* Slight hue-shift in background.","3":"* 256-color terminal mode colors, added by Clayton Parker.\r\n* Cursor line (and column) visibility can be customized by the g:mayansmoke_cursor_line_visibility variable.\r\n* Slight hue-shift in background.","package":"mayansmoke.vim","4":"mayansmoke.vim","src_id":"13032","5":"13032","creation_date":"1274345142","6":"1274345142"},{"0":"3065","vim_version":"6.0","1":"6.0","script_version":"1.3","2":"1.3","version_comment":"* Added custom diff syntax colors.\r\n* Cursor line\/column color tweak (beige instead of white).","3":"* Added custom diff syntax colors.\r\n* Cursor line\/column color tweak (beige instead of white).","package":"mayansmoke.vim","4":"mayansmoke.vim","src_id":"12928","5":"12928","creation_date":"1272853271","6":"1272853271"},{"0":"3065","vim_version":"6.0","1":"6.0","script_version":"1.2","2":"1.2","version_comment":"Now allows for customization of \"Special Key\" highlighting visibility (used for whitespace\/listchar etc.) by setting of \"g:mayansmoke_special_key_visibility\" value. 0 = lower visibility, 1 = medium visibility, 2 = higher visibility.","3":"Now allows for customization of \"Special Key\" highlighting visibility (used for whitespace\/listchar etc.) by setting of \"g:mayansmoke_special_key_visibility\" value. 0 = lower visibility, 1 = medium visibility, 2 = higher visibility.","package":"mayansmoke.vim","4":"mayansmoke.vim","src_id":"12894","5":"12894","creation_date":"1272065047","6":"1272065047"},{"0":"3065","vim_version":"6.0","1":"6.0","script_version":"1.0.1","2":"1.0.1","version_comment":"* Tweaked ignore colors to actually ignore.\r\n* Added special syntax highlighting for Python decorators.","3":"* Tweaked ignore colors to actually ignore.\r\n* Added special syntax highlighting for Python decorators.","package":"mayansmoke.vim","4":"mayansmoke.vim","src_id":"12864","5":"12864","creation_date":"1271655838","6":"1271655838"},{"0":"3065","vim_version":"7.2","1":"7.2","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"mayansmoke.vim","4":"mayansmoke.vim","src_id":"12857","5":"12857","creation_date":"1271474673","6":"1271474673"}]},"3064":{"script_id":"3064","0":"3064","script_name":"after\/syntax\/c.vim","1":"after\/syntax\/c.vim","script_type":"syntax","2":"syntax","summary":"C Syntax Extensions","3":"C Syntax Extensions","description":"This file, instead of replacing the normal c.vim file, incorporates and improves upon some of the changes added in vimscript #1201, \"Extended original c.vim.\" Because this file goes in $VIMRUNTIME\/after\/syntax, it appends these additional definitions to whatever c.vim file comes with the version of Vim you use.\r\n\r\nThe main additions identify operators, delimiters, and user-defined functions\/function calls. Also included is a wealth of standard ANSI C function names as keywords. This makes C files look significantly richer, especially if your colorscheme includes color variants for the additional syntax groups.\r\n\r\nThe Match regexps for user-defined functions have been improved. The rest is mostly just selective porting from the c.vim in vimscript #1201.","4":"This file, instead of replacing the normal c.vim file, incorporates and improves upon some of the changes added in vimscript #1201, \"Extended original c.vim.\" Because this file goes in $VIMRUNTIME\/after\/syntax, it appends these additional definitions to whatever c.vim file comes with the version of Vim you use.\r\n\r\nThe main additions identify operators, delimiters, and user-defined functions\/function calls. Also included is a wealth of standard ANSI C function names as keywords. This makes C files look significantly richer, especially if your colorscheme includes color variants for the additional syntax groups.\r\n\r\nThe Match regexps for user-defined functions have been improved. The rest is mostly just selective porting from the c.vim in vimscript #1201.","install_details":"Place c.vim in $VIMRUNTIME\/after\/syntax.","5":"Place c.vim in $VIMRUNTIME\/after\/syntax.","first_name":"Mikhail","6":"Mikhail","last_name":"Wolfson","7":"Wolfson","releases":[{"0":"3064","vim_version":"7.0","1":"7.0","script_version":"0.4","2":"0.4","version_comment":"updates and fixes to cDelimiter to fix break with foldmethod=syntax, entirely suggested and solved by Ivan Freitas","3":"updates and fixes to cDelimiter to fix break with foldmethod=syntax, entirely suggested and solved by Ivan Freitas","package":"c.vim","4":"c.vim","src_id":"14548","5":"14548","creation_date":"1292611948","6":"1292611948"},{"0":"3064","vim_version":"7.0","1":"7.0","script_version":"0.3","2":"0.3","version_comment":"updates and fixes to cUserFunctionPointer, thanks to Alexei <lxmzhv@gmail.com>","3":"updates and fixes to cUserFunctionPointer, thanks to Alexei <lxmzhv@gmail.com>","package":"c.vim","4":"c.vim","src_id":"12892","5":"12892","creation_date":"1272033425","6":"1272033425"},{"0":"3064","vim_version":"7.0","1":"7.0","script_version":"0.2","2":"0.2","version_comment":"changed [] from cDelimiter to cOperator.","3":"changed [] from cDelimiter to cOperator.","package":"c.vim","4":"c.vim","src_id":"12876","5":"12876","creation_date":"1271782786","6":"1271782786"},{"0":"3064","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"c.vim","4":"c.vim","src_id":"12856","5":"12856","creation_date":"1271473386","6":"1271473386"}]},"3063":{"script_id":"3063","0":"3063","script_name":"mdark.vim","1":"mdark.vim","script_type":"color scheme","2":"color scheme","summary":"Dark colorscheme with shade variations, based on rdark\/mydark","3":"Dark colorscheme with shade variations, based on rdark\/mydark","description":"This is a dark colorscheme, based on the great work done in rdark, and its variants (such as mydark). I wanted to build on the idea of pastel highlights with a dark gray background. I ended up expanding the range of colors so that, while one color represents a group of related terms, different sub-groups within that larger group have different shades. For example, the Statements highlight group consists entirely of shades of blue, but Repeat keywords (like for, while...) get a slightly darker blue, while Exception keywords (try, catch, ...) get a lighter blue, and so on. A screenshot at http:\/\/web.mit.edu\/wolfsonm\/www\/files\/vim\/mdark_vim.png shows the scheme in action on many common filetypes.\r\n\r\nNote: not all languages will show these differences, as the default syntax files for most languages do not always make such distinctions.","4":"This is a dark colorscheme, based on the great work done in rdark, and its variants (such as mydark). I wanted to build on the idea of pastel highlights with a dark gray background. I ended up expanding the range of colors so that, while one color represents a group of related terms, different sub-groups within that larger group have different shades. For example, the Statements highlight group consists entirely of shades of blue, but Repeat keywords (like for, while...) get a slightly darker blue, while Exception keywords (try, catch, ...) get a lighter blue, and so on. A screenshot at http:\/\/web.mit.edu\/wolfsonm\/www\/files\/vim\/mdark_vim.png shows the scheme in action on many common filetypes.\r\n\r\nNote: not all languages will show these differences, as the default syntax files for most languages do not always make such distinctions.","install_details":"Place the mdark.vim file in $VIMRUNTIME\/colors. To choose the colorsheme, :color mdark.","5":"Place the mdark.vim file in $VIMRUNTIME\/colors. To choose the colorsheme, :color mdark.","first_name":"Mikhail","6":"Mikhail","last_name":"Wolfson","7":"Wolfson","releases":[{"0":"3063","vim_version":"7.2","1":"7.2","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"mdark.vim","4":"mdark.vim","src_id":"12850","5":"12850","creation_date":"1271458305","6":"1271458305"}]},"3062":{"script_id":"3062","0":"3062","script_name":"256-grayvim","1":"256-grayvim","script_type":"color scheme","2":"color scheme","summary":"Blue & gray 256 colorscheme","3":"Blue & gray 256 colorscheme","description":"Screenshots:\r\n * http:\/\/wstaw.org\/m\/2010\/04\/16\/2010-04-16-230848_640x772_scrot.png","4":"Screenshots:\r\n * http:\/\/wstaw.org\/m\/2010\/04\/16\/2010-04-16-230848_640x772_scrot.png","install_details":"","5":"","first_name":"Piotr","6":"Piotr","last_name":"Husiatynski","7":"Husiatynski","releases":[{"0":"3062","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"256-grayvim.vim","4":"256-grayvim.vim","src_id":"12849","5":"12849","creation_date":"1271452229","6":"1271452229"}]},"3061":{"script_id":"3061","0":"3061","script_name":"VxLib","1":"VxLib","script_type":"utility","2":"utility","summary":"Some utility functions packed in a library","3":"Some utility functions packed in a library","description":"Script: vxlib\r\n\r\nInitially developed for vimuiex (vimscript#2606)\r\nUsed by manuals (vimscript#3060)\r\n\r\nContains a Vim Plugin Generator that parses files in autoload directories and creates \r\nplugin initialization code for the plugin directory - a single file for all plugins. \r\nIt searches for specially marked sections in vim files (see vimuiex, manuals).\r\n\r\nSee http:\/\/vimuiex.sourceforge.net\/vimdoc\/vxlib_plugin.html for details.\r\n\r\nThe command :VxRegen will start the plugin generator, create the plugin \r\ninitialization code and update the plugin configuration file (plugins\/vxplugin.conf).  \r\n:VxRegen will execute a Python script using an existing Python installation, so \r\nPython must be in your system PATH. \r\n\r\nThe configuration file can be edited with :VxConfig. It is a simple win-ini-type \r\nfile. Currently it is only possible to include\/exclude the plugins from the \r\ninitialization code. To exclude a plugin, put 'generate=0' in the appropriate \r\nsections. By default initialization code for all found plugins is generated.\r\n\r\nGenerated plugins can also be disabled from .vimrc. Each plugin processed by the \r\nplugin generator has a unique ID. When the plugins are loaded, this ID is used to \r\ncheck if the plugin should be loaded or not. To disable a plugin with \r\nid='vimuiex#textmenu', add 'let g:vxenabled_vimuiex_textmenu=0' to .vimrc.\r\n\r\nIncluded in the library is the QuickFixPreview plugin that adds mappings\r\nto preview the line that is selected in the QuickFix window.\r\nhttp:\/\/vimuiex.sourceforge.net\/vimdoc\/vxlib_plugins.html#vxlib-quickfixpreview\r\n\r\nRelated scripts: genutils(vimscript#197), lh-vim-lib(vimscript#214), \r\ntlib(vimscript#1863), vim-addon-manager(vimscript#2905), \r\ntplugin(vimscript#2917),\r\n","4":"Script: vxlib\r\n\r\nInitially developed for vimuiex (vimscript#2606)\r\nUsed by manuals (vimscript#3060)\r\n\r\nContains a Vim Plugin Generator that parses files in autoload directories and creates \r\nplugin initialization code for the plugin directory - a single file for all plugins. \r\nIt searches for specially marked sections in vim files (see vimuiex, manuals).\r\n\r\nSee http:\/\/vimuiex.sourceforge.net\/vimdoc\/vxlib_plugin.html for details.\r\n\r\nThe command :VxRegen will start the plugin generator, create the plugin \r\ninitialization code and update the plugin configuration file (plugins\/vxplugin.conf).  \r\n:VxRegen will execute a Python script using an existing Python installation, so \r\nPython must be in your system PATH. \r\n\r\nThe configuration file can be edited with :VxConfig. It is a simple win-ini-type \r\nfile. Currently it is only possible to include\/exclude the plugins from the \r\ninitialization code. To exclude a plugin, put 'generate=0' in the appropriate \r\nsections. By default initialization code for all found plugins is generated.\r\n\r\nGenerated plugins can also be disabled from .vimrc. Each plugin processed by the \r\nplugin generator has a unique ID. When the plugins are loaded, this ID is used to \r\ncheck if the plugin should be loaded or not. To disable a plugin with \r\nid='vimuiex#textmenu', add 'let g:vxenabled_vimuiex_textmenu=0' to .vimrc.\r\n\r\nIncluded in the library is the QuickFixPreview plugin that adds mappings\r\nto preview the line that is selected in the QuickFix window.\r\nhttp:\/\/vimuiex.sourceforge.net\/vimdoc\/vxlib_plugins.html#vxlib-quickfixpreview\r\n\r\nRelated scripts: genutils(vimscript#197), lh-vim-lib(vimscript#214), \r\ntlib(vimscript#1863), vim-addon-manager(vimscript#2905), \r\ntplugin(vimscript#2917),\r\n","install_details":"Unpack into vim runtime directory (eg. ~\/.vim\/).\r\n\r\nIf you want to manage the plugins generated by VxLib, add\r\n   let g:vxlib_user_generated_plugins=1\r\nto your .vimrc and use the following commands:\r\n   :VxRegen to generate plugin initialization code for plugins that support VxLib.\r\n   :VxConfig to configure such plugins.\r\n\r\nIf g:vxlib_user_generated_plugins is not set or is equal to 0, the above commands are \r\nnot available and all the plugins from ~\/.vim\/vxlibautogen\/plugin are loaded instead.\r\n\r\nIf the generator doesn't work for some reason, there is a script in ~\/modpython\/vxlib \r\n- mkplugins.sh - that does a similar thing as VxRegen. If the script complains that \r\nit doesn't find vim, remove the parameter '--indent 1'.\r\n","5":"Unpack into vim runtime directory (eg. ~\/.vim\/).\r\n\r\nIf you want to manage the plugins generated by VxLib, add\r\n   let g:vxlib_user_generated_plugins=1\r\nto your .vimrc and use the following commands:\r\n   :VxRegen to generate plugin initialization code for plugins that support VxLib.\r\n   :VxConfig to configure such plugins.\r\n\r\nIf g:vxlib_user_generated_plugins is not set or is equal to 0, the above commands are \r\nnot available and all the plugins from ~\/.vim\/vxlibautogen\/plugin are loaded instead.\r\n\r\nIf the generator doesn't work for some reason, there is a script in ~\/modpython\/vxlib \r\n- mkplugins.sh - that does a similar thing as VxRegen. If the script complains that \r\nit doesn't find vim, remove the parameter '--indent 1'.\r\n","first_name":"Marko","6":"Marko","last_name":"Mahni\u010d","7":"Mahnič","releases":[{"0":"3061","vim_version":"7.0","1":"7.0","script_version":"0.7","2":"0.7","version_comment":"Minor changes\r\n* menu.vim added\r\n* vxlib\/cmd: #Edit sets buflisted for loaded buffers\r\n* fixed vxlib#python#prepare","3":"Minor changes\r\n* menu.vim added\r\n* vxlib\/cmd: #Edit sets buflisted for loaded buffers\r\n* fixed vxlib#python#prepare","package":"vxlib.zip","4":"vxlib.zip","src_id":"13735","5":"13735","creation_date":"1283276850","6":"1283276850"},{"0":"3061","vim_version":"6.0","1":"6.0","script_version":"0.6.7a","2":"0.6.7a","version_comment":"Support for developer-generated plugin initialization","3":"Support for developer-generated plugin initialization","package":"vxlib.zip","4":"vxlib.zip","src_id":"12861","5":"12861","creation_date":"1271613036","6":"1271613036"},{"0":"3061","vim_version":"7.0","1":"7.0","script_version":"0.6.7","2":"0.6.7","version_comment":"Initial upload","3":"Initial upload","package":"vxlib.zip","4":"vxlib.zip","src_id":"12847","5":"12847","creation_date":"1271435583","6":"1271435583"}]},"3060":{"script_id":"3060","0":"3060","script_name":"Manuals","1":"Manuals","script_type":"utility","2":"utility","summary":"An extensible help system","3":"An extensible help system","description":"Provides context sensitive word lookup. The manuals in vimhelp format that are not \r\nrelated to Vim can be kept in separate locations with separate tagfiles.\r\n\r\nThe context sensitive lookup is implemented by the plugin vxlib\/context.vim. When a \r\nmanual lookup is required (mapped to K), the plugin checks the context the cursor is \r\nin - the current filetype and the current syntax element. Then it finds all the help \r\nproviders that were registered for the detected context. The highest scored provider \r\nis executed an the results are displayed. It is also possible to display a list of \r\nproviders applicable in the current context and select one (\\km); if vimuiex is \r\ninstalled, a popup list will be displayed, otherwise the choices are echoed to the \r\nscreen and the uesr enters a choice.\r\n\r\nExample: when you're editing Python kode and press K on a keyword, an entry from the \r\nPython documentation will be displayed (the output from pydoc). When the cursor is in \r\na Python comment or a string, dict will be used instead. Similarly, when editing \r\nHTML, help for CSS can be displayed when the cursor is in the <style> section.\r\n\r\nThere are three possible types of results a provider can produce: \r\n   t - show help text for keyword\r\n   k - list similar keywords (and find help for the selected one)\r\n   g - grep the manuals to find occurences of the word\r\n\r\nThe library comes with the following providers (supported types are in parentheses):\r\n   vimhelp (tkg) - internal vim help\r\n   extvimhelp (tkg) - external help in vimhelp format, stored in a separate location\r\n   man (t) - unix man\r\n   pydoc (tg) - python documentation, requires pydoc program\r\n   pydiction (k) - uses the dictionary produced by vimscript#850\r\n   cmakeref (tkg) - vimscript#3045, uses extvimhelp\r\n   cssref (tkg) - vimscript#918, uses extvimhelp\r\n   crefvim (tkg) - vimscript#614, vimscript#2353, uses extvimhelp\r\n   luarefvim (tkg) - vimscript#1291, uses extvimhelp\r\n   dict (t) - find a dictionary entry using the dict program\r\n\r\nThe providers that use extvimhelp expect the manuals to be installed in the location \r\nset in g:vxlib_manuals_directory. Initially this location is set to ~\/.vim\/manuals \r\n(actually the script takes the first item from &rtp and appends \/manuals to it). Each \r\nmanual is stored in a subdirectory of this location, the name of the subdirectory is \r\nthe same as the name of the provider, eg.\r\n   ~\/.vim\/manuals\/cmakeref\r\n   ~\/.vim\/manuals\/luarefvim\r\n\r\nAfter you install each manual, don't forget to run :helptags %:p:h on a file from \r\nthe manual.\r\n","4":"Provides context sensitive word lookup. The manuals in vimhelp format that are not \r\nrelated to Vim can be kept in separate locations with separate tagfiles.\r\n\r\nThe context sensitive lookup is implemented by the plugin vxlib\/context.vim. When a \r\nmanual lookup is required (mapped to K), the plugin checks the context the cursor is \r\nin - the current filetype and the current syntax element. Then it finds all the help \r\nproviders that were registered for the detected context. The highest scored provider \r\nis executed an the results are displayed. It is also possible to display a list of \r\nproviders applicable in the current context and select one (\\km); if vimuiex is \r\ninstalled, a popup list will be displayed, otherwise the choices are echoed to the \r\nscreen and the uesr enters a choice.\r\n\r\nExample: when you're editing Python kode and press K on a keyword, an entry from the \r\nPython documentation will be displayed (the output from pydoc). When the cursor is in \r\na Python comment or a string, dict will be used instead. Similarly, when editing \r\nHTML, help for CSS can be displayed when the cursor is in the <style> section.\r\n\r\nThere are three possible types of results a provider can produce: \r\n   t - show help text for keyword\r\n   k - list similar keywords (and find help for the selected one)\r\n   g - grep the manuals to find occurences of the word\r\n\r\nThe library comes with the following providers (supported types are in parentheses):\r\n   vimhelp (tkg) - internal vim help\r\n   extvimhelp (tkg) - external help in vimhelp format, stored in a separate location\r\n   man (t) - unix man\r\n   pydoc (tg) - python documentation, requires pydoc program\r\n   pydiction (k) - uses the dictionary produced by vimscript#850\r\n   cmakeref (tkg) - vimscript#3045, uses extvimhelp\r\n   cssref (tkg) - vimscript#918, uses extvimhelp\r\n   crefvim (tkg) - vimscript#614, vimscript#2353, uses extvimhelp\r\n   luarefvim (tkg) - vimscript#1291, uses extvimhelp\r\n   dict (t) - find a dictionary entry using the dict program\r\n\r\nThe providers that use extvimhelp expect the manuals to be installed in the location \r\nset in g:vxlib_manuals_directory. Initially this location is set to ~\/.vim\/manuals \r\n(actually the script takes the first item from &rtp and appends \/manuals to it). Each \r\nmanual is stored in a subdirectory of this location, the name of the subdirectory is \r\nthe same as the name of the provider, eg.\r\n   ~\/.vim\/manuals\/cmakeref\r\n   ~\/.vim\/manuals\/luarefvim\r\n\r\nAfter you install each manual, don't forget to run :helptags %:p:h on a file from \r\nthe manual.\r\n","install_details":"Requires VxLib (vimscript#3061)\r\nUnpack the files into the vim runtime directory (eg. ~\/.vim).\r\n\r\nIf you wish, you can run :VxRegen to re-generate the initialization code.\r\n(see also vimscript#3061 installation for the availability of :VxRegen)\r\n\r\nThe plugin will set the following keys: K, \\kk, \\km, \\kg in normal and visual mode.  \r\nIf you would like different mappings, use :VxConfig to edit the configuration file \r\n(:VxRegen must be run at least once). Set 'generate=0' in section [manuals#maps]. An \r\nalternative is to edit ~\/.vimrc and add\r\n   let g:vxenable_manuals_maps=0","5":"Requires VxLib (vimscript#3061)\r\nUnpack the files into the vim runtime directory (eg. ~\/.vim).\r\n\r\nIf you wish, you can run :VxRegen to re-generate the initialization code.\r\n(see also vimscript#3061 installation for the availability of :VxRegen)\r\n\r\nThe plugin will set the following keys: K, \\kk, \\km, \\kg in normal and visual mode.  \r\nIf you would like different mappings, use :VxConfig to edit the configuration file \r\n(:VxRegen must be run at least once). Set 'generate=0' in section [manuals#maps]. An \r\nalternative is to edit ~\/.vimrc and add\r\n   let g:vxenable_manuals_maps=0","first_name":"Marko","6":"Marko","last_name":"Mahni\u010d","7":"Mahnič","releases":[{"0":"3060","vim_version":"7.0","1":"7.0","script_version":"0.1a","2":"0.1a","version_comment":"* added missing function","3":"* added missing function","package":"manuals.zip","4":"manuals.zip","src_id":"12863","5":"12863","creation_date":"1271613974","6":"1271613974"},{"0":"3060","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"* tested without vimuiex, fixed\r\n* vxlib can load the plugin without running :VxRegen","3":"* tested without vimuiex, fixed\r\n* vxlib can load the plugin without running :VxRegen","package":"manuals.zip","4":"manuals.zip","src_id":"12862","5":"12862","creation_date":"1271613329","6":"1271613329"},{"0":"3060","vim_version":"7.0","1":"7.0","script_version":"0.01","2":"0.01","version_comment":"Initial upload","3":"Initial upload","package":"manuals.zip","4":"manuals.zip","src_id":"12846","5":"12846","creation_date":"1271435361","6":"1271435361"}]},"3059":{"script_id":"3059","0":"3059","script_name":"lastpos.vim","1":"lastpos.vim","script_type":"utility","2":"utility","summary":"Last position jump improved for Easy Vim","3":"Last position jump improved for Easy Vim","description":"With Easy Vim [1], the code to perform a last position jump [2] can't restore a cursor position beyond EOL, because the jump will be executed in Normal mode [3].  The result in this case is a by-one error [4], so most people [5] won't find that annoying ...\r\n\r\nThe good news is that Vim seems to store a correct value in the viminfo file -- one solution is to restore the last position while in Insert mode, which is what the plugin does.\r\n\r\nEasy Vim actually is not required, the plugin will also work with a normal setup, or when you use  :startinsert  in the vimrc to merely start up in Insert mode.\r\n\r\nThe code is slightly more cautious than the original: the cursor won't be moved if something else already moved it, or if the buffer is special (help buffer, etc.).  Furthermore, to fix [6] a related case [7], the BufWinEnter autocommand is used instead of BufReadPost.\r\n\r\nThis lengthy description applies for a rather short piece of code.\r\n\r\n[1] :help 'insertmode' or :help -y\r\n[2] :h last-position-jump\r\n[3] explanation http:\/\/groups.google.com\/group\/vim_use\/msg\/c571f994f211f8fe\r\n[4] the position is almost right, no issue for Bram: http:\/\/groups.google.com\/group\/vim_dev\/msg\/fbcffe406ff01b7f\r\n[5] especially of the few Easy vimmers\r\n[6] not sure if \"modify\" is the better word as what follows is probably not a bug\r\n[7] Cursor column not remembered ... http:\/\/groups.google.com\/group\/vim_dev\/msg\/b3512cecaab3e0b1\r\n","4":"With Easy Vim [1], the code to perform a last position jump [2] can't restore a cursor position beyond EOL, because the jump will be executed in Normal mode [3].  The result in this case is a by-one error [4], so most people [5] won't find that annoying ...\r\n\r\nThe good news is that Vim seems to store a correct value in the viminfo file -- one solution is to restore the last position while in Insert mode, which is what the plugin does.\r\n\r\nEasy Vim actually is not required, the plugin will also work with a normal setup, or when you use  :startinsert  in the vimrc to merely start up in Insert mode.\r\n\r\nThe code is slightly more cautious than the original: the cursor won't be moved if something else already moved it, or if the buffer is special (help buffer, etc.).  Furthermore, to fix [6] a related case [7], the BufWinEnter autocommand is used instead of BufReadPost.\r\n\r\nThis lengthy description applies for a rather short piece of code.\r\n\r\n[1] :help 'insertmode' or :help -y\r\n[2] :h last-position-jump\r\n[3] explanation http:\/\/groups.google.com\/group\/vim_use\/msg\/c571f994f211f8fe\r\n[4] the position is almost right, no issue for Bram: http:\/\/groups.google.com\/group\/vim_dev\/msg\/fbcffe406ff01b7f\r\n[5] especially of the few Easy vimmers\r\n[6] not sure if \"modify\" is the better word as what follows is probably not a bug\r\n[7] Cursor column not remembered ... http:\/\/groups.google.com\/group\/vim_dev\/msg\/b3512cecaab3e0b1\r\n","install_details":"Drop the file into your plugin folder, restart Vim.\r\n\r\nFor newbies: this folder could be ~\\vimfiles\\plugin -- replace '~\\vimfiles' with the first entry of your 'runtimepath'.\r\n\r\nIf you are using the example vimrc :help vimrc_example.vim, you may have\r\n\r\nautocmd BufReadPost *\r\n  \\ if line(\"'\\\"\") > 1 && line(\"'\\\"\") <= line(\"$\") |\r\n  \\  exe \"normal! g`\\\"\" |\r\n  \\ endif\r\n\r\nin your vimrc \u00e2\u0080\u0093 make sure to remove this old code.","5":"Drop the file into your plugin folder, restart Vim.\r\n\r\nFor newbies: this folder could be ~\\vimfiles\\plugin -- replace '~\\vimfiles' with the first entry of your 'runtimepath'.\r\n\r\nIf you are using the example vimrc :help vimrc_example.vim, you may have\r\n\r\nautocmd BufReadPost *\r\n  \\ if line(\"'\\\"\") > 1 && line(\"'\\\"\") <= line(\"$\") |\r\n  \\  exe \"normal! g`\\\"\" |\r\n  \\ endif\r\n\r\nin your vimrc \u00e2\u0080\u0093 make sure to remove this old code.","first_name":"Andy","6":"Andy","last_name":"Wokula","7":"Wokula","releases":[{"0":"3059","vim_version":"7.0","1":"7.0","script_version":"0.6","2":"0.6","version_comment":"Initial upload","3":"Initial upload","package":"lastpos.vim","4":"lastpos.vim","src_id":"12839","5":"12839","creation_date":"1271367065","6":"1271367065"}]},"3058":{"script_id":"3058","0":"3058","script_name":"tex_mini.vim","1":"tex_mini.vim","script_type":"ftplugin","2":"ftplugin","summary":"facilitates the preparation of LaTeX documents in vim","3":"facilitates the preparation of LaTeX documents in vim","description":"facilitates the preparation of LaTeX documents in vim without requiring you to master a new interface (it basically provides some minimal <tab> completion for some common LaTeX environments and macros).","4":"facilitates the preparation of LaTeX documents in vim without requiring you to master a new interface (it basically provides some minimal <tab> completion for some common LaTeX environments and macros).","install_details":"see the header of the file","5":"see the header of the file","first_name":"Pouya","6":"Pouya","last_name":"Tafti","7":"Tafti","releases":[{"0":"3058","vim_version":"6.0","1":"6.0","script_version":"1e","2":"1e","version_comment":"Initial upload","3":"Initial upload","package":"tex_mini.vim","4":"tex_mini.vim","src_id":"12838","5":"12838","creation_date":"1271340084","6":"1271340084"}]},"3057":{"script_id":"3057","0":"3057","script_name":"vimsizer","1":"vimsizer","script_type":"utility","2":"utility","summary":"A vim global plugin that allows for quick window sizing","3":"A vim global plugin that allows for quick window sizing","description":"Vimsizer is a simple plugin that was inspired by the\r\nFiresizer (https:\/\/addons.mozilla.org\/en-US\/firefox\/addon\/5792) extension\r\nfor Firefox. This plugin gives you the ability to define a re-usable set of\r\nwindow dimensions.\r\n\r\nThere are two default sizes that are defined with the\r\nvs_window_sizes variable:\r\n\r\n    let vs_window_sizes = {\"normal\": \"150 40\", \"bigger\": \"210 50\"}\r\n\r\nYou can define your own set of sizes. Example:\r\n\r\n    let vs_window_sizes = {\"miniscule\": \"25 10\", \"magiscule\": \"200 60\"}\r\n\r\nOnce the window sizes have been defined then you can use the\r\nVSSelectWindowSize command to switch. Example:\r\n\r\n    :VSSelectWindowSize bigger\r\n    :VSSelectWindowSize normal\r\n\r\nYou can also quickly switch to any specific size you like with the\r\nVSWindowSize command:\r\n\r\n    :VSWindowSize 100 20\r\n\r\nYou can use the autogroup command to set the window size on startup.\r\nExample:\r\n\r\n    au VimEnter * exe 'VSSelectWindowSize normal'\r\n\r\nThis would set the window size to normal upon entering vim for the first\r\ntime.\r\n\r\nYou could also map a shortcut key to a window size. Example:\r\n\r\n    map <leader>1 :VSSelectWindowSize normal<CR>\r\n    map <leader>2 :VSSelectWindowSize bigger<CR>\r\n\r\nThe latest code is available on Github: http:\/\/github.com\/claytron\/vimsizer","4":"Vimsizer is a simple plugin that was inspired by the\r\nFiresizer (https:\/\/addons.mozilla.org\/en-US\/firefox\/addon\/5792) extension\r\nfor Firefox. This plugin gives you the ability to define a re-usable set of\r\nwindow dimensions.\r\n\r\nThere are two default sizes that are defined with the\r\nvs_window_sizes variable:\r\n\r\n    let vs_window_sizes = {\"normal\": \"150 40\", \"bigger\": \"210 50\"}\r\n\r\nYou can define your own set of sizes. Example:\r\n\r\n    let vs_window_sizes = {\"miniscule\": \"25 10\", \"magiscule\": \"200 60\"}\r\n\r\nOnce the window sizes have been defined then you can use the\r\nVSSelectWindowSize command to switch. Example:\r\n\r\n    :VSSelectWindowSize bigger\r\n    :VSSelectWindowSize normal\r\n\r\nYou can also quickly switch to any specific size you like with the\r\nVSWindowSize command:\r\n\r\n    :VSWindowSize 100 20\r\n\r\nYou can use the autogroup command to set the window size on startup.\r\nExample:\r\n\r\n    au VimEnter * exe 'VSSelectWindowSize normal'\r\n\r\nThis would set the window size to normal upon entering vim for the first\r\ntime.\r\n\r\nYou could also map a shortcut key to a window size. Example:\r\n\r\n    map <leader>1 :VSSelectWindowSize normal<CR>\r\n    map <leader>2 :VSSelectWindowSize bigger<CR>\r\n\r\nThe latest code is available on Github: http:\/\/github.com\/claytron\/vimsizer","install_details":"To install this plugin simply copy the vimsizer.vim into the plugin\r\ndirectory and vimsizer.txt into the doc directory in your vim folder.\r\n","5":"To install this plugin simply copy the vimsizer.vim into the plugin\r\ndirectory and vimsizer.txt into the doc directory in your vim folder.\r\n","first_name":"Clayton","6":"Clayton","last_name":"Parker","7":"Parker","releases":[{"0":"3057","vim_version":"6.0","1":"6.0","script_version":"1.2","2":"1.2","version_comment":"More packaging fixes","3":"More packaging fixes","package":"vimsizer.tgz","4":"vimsizer.tgz","src_id":"12836","5":"12836","creation_date":"1271312987","6":"1271312987"},{"0":"3057","vim_version":"6.0","1":"6.0","script_version":"1.1","2":"1.1","version_comment":"Packaging fixups","3":"Packaging fixups","package":"vimsizer.tgz","4":"vimsizer.tgz","src_id":"12835","5":"12835","creation_date":"1271312671","6":"1271312671"},{"0":"3057","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"vimsizer.tgz","4":"vimsizer.tgz","src_id":"12834","5":"12834","creation_date":"1271312264","6":"1271312264"}]},"3056":{"script_id":"3056","0":"3056","script_name":"translit3","1":"translit3","script_type":"utility","2":"utility","summary":"    Plugin used for text transliteration","3":"    Plugin used for text transliteration","description":"\r\nThis plugin provides the ability to transform one sequence of symbols into \r\nanother. The typical use case is transliteration of latin symbols into russian \r\nsymbols for systems without russian keyboard.\r\n\r\nFeatures:\r\n  - transliteration of text, provided as function argument;\r\n  - transliteration of a selection or a line range;\r\n  - input transliteration;\r\n  - setting up the input transliteration in current buffer or in all opened\r\n    buffers;\r\n  - plugin system for transliteration function;\r\n  - plugin system for input transliteration;\r\n  - loading transliteration table from a file, a variable, a dictionary or\r\n    a function;\r\n  - displaying the transliteration table on the screen.\r\n\r\nPlugin requires some additional plugins:\r\n  - frawor (https:\/\/bitbucket.org\/ZyX_I\/frawor)\r\n  - jsonvim (http:\/\/bitbucket.org\/ZyX_I\/jsonvim)\r\n(with their dependencies).\r\n\r\n\r\nProject page: https:\/\/bitbucket.org\/ZyX_I\/translit3\r\nDocumentation: http:\/\/vimcommunity.bitbucket.org\/doc\/translit3.txt.html\r\nRussian documentation: http:\/\/vimcommunity.bitbucket.org\/doc\/translit3.rux.html\r\n\r\n\r\n\r\n","4":"\r\nThis plugin provides the ability to transform one sequence of symbols into \r\nanother. The typical use case is transliteration of latin symbols into russian \r\nsymbols for systems without russian keyboard.\r\n\r\nFeatures:\r\n  - transliteration of text, provided as function argument;\r\n  - transliteration of a selection or a line range;\r\n  - input transliteration;\r\n  - setting up the input transliteration in current buffer or in all opened\r\n    buffers;\r\n  - plugin system for transliteration function;\r\n  - plugin system for input transliteration;\r\n  - loading transliteration table from a file, a variable, a dictionary or\r\n    a function;\r\n  - displaying the transliteration table on the screen.\r\n\r\nPlugin requires some additional plugins:\r\n  - frawor (https:\/\/bitbucket.org\/ZyX_I\/frawor)\r\n  - jsonvim (http:\/\/bitbucket.org\/ZyX_I\/jsonvim)\r\n(with their dependencies).\r\n\r\n\r\nProject page: https:\/\/bitbucket.org\/ZyX_I\/translit3\r\nDocumentation: http:\/\/vimcommunity.bitbucket.org\/doc\/translit3.txt.html\r\nRussian documentation: http:\/\/vimcommunity.bitbucket.org\/doc\/translit3.rux.html\r\n\r\n\r\n\r\n","install_details":"You can install this plugin using vim-addon-manager (vimscript #2905) plugin (install vim-addon-manager, run “ActivateAddons translit3” and add “call vam#ActivateAddons(["translit3"])” to your .vimrc. Vim-addon-manager will install all dependencies for you). You can also use archives attached to this page, they contain plugin with all dependencies, so you do not need to fetch them yourself. First version present on this page needs no dependencies.\r\n\r\nGentoo users can use the following mercurial overlay: http:\/\/bitbucket.org\/ZyX_I\/pluginloader-overlay.","5":"You can install this plugin using vim-addon-manager (vimscript #2905) plugin (install vim-addon-manager, run “ActivateAddons translit3” and add “call vam#ActivateAddons(["translit3"])” to your .vimrc. Vim-addon-manager will install all dependencies for you). You can also use archives attached to this page, they contain plugin with all dependencies, so you do not need to fetch them yourself. First version present on this page needs no dependencies.\r\n\r\nGentoo users can use the following mercurial overlay: http:\/\/bitbucket.org\/ZyX_I\/pluginloader-overlay.","first_name":"ZyX","6":"ZyX","last_name":" ","7":" ","releases":[{"0":"3056","vim_version":"7.3","1":"7.3","script_version":"3.1.4","2":"3.1.4","version_comment":"Make it use new functions autoload feature\nFix transliteration of block selection (it used to take one more line then necessary)","3":"Make it use new functions autoload feature\nFix transliteration of block selection (it used to take one more line then necessary)","package":"translit3-3.1.4.tar.gz","4":"translit3-3.1.4.tar.gz","src_id":"21263","5":"21263","creation_date":"1388463480","6":"1388463480"},{"0":"3056","vim_version":"7.3","1":"7.3","script_version":"3.1.3","2":"3.1.3","version_comment":"Add fullwidth characters transliteration table\nAdd workaround for new vim regexp engine bug","3":"Add fullwidth characters transliteration table\nAdd workaround for new vim regexp engine bug","package":"translit3-3.1.3.tar.gz","4":"translit3-3.1.3.tar.gz","src_id":"20729","5":"20729","creation_date":"1377801352","6":"1377801352"},{"0":"3056","vim_version":"7.3","1":"7.3","script_version":"3.1.2","2":"3.1.2","version_comment":"Moved most code to autoload\/translit3.vim","3":"Moved most code to autoload\/translit3.vim","package":"translit3-3.1.2.tar.gz","4":"translit3-3.1.2.tar.gz","src_id":"19142","5":"19142","creation_date":"1354970563","6":"1354970563"},{"0":"3056","vim_version":"7.3","1":"7.3","script_version":"3.1.1","2":"3.1.1","version_comment":"Made it follow jsonvim file location change","3":"Made it follow jsonvim file location change","package":"translit3-3.1.1.tar.gz","4":"translit3-3.1.1.tar.gz","src_id":"19137","5":"19137","creation_date":"1354920873","6":"1354920873"},{"0":"3056","vim_version":"7.3","1":"7.3","script_version":"3.1","2":"3.1","version_comment":"Added transsymb.include key that allows reusing of transsymb files","3":"Added transsymb.include key that allows reusing of transsymb files","package":"translit3-3.1.tar.gz","4":"translit3-3.1.tar.gz","src_id":"17017","5":"17017","creation_date":"1322961870","6":"1322961870"},{"0":"3056","vim_version":"7.3","1":"7.3","script_version":"3.0","2":"3.0","version_comment":"Ported plugin to frawor","3":"Ported plugin to frawor","package":"translit3-3.0.tar.gz","4":"translit3-3.0.tar.gz","src_id":"15977","5":"15977","creation_date":"1309080866","6":"1309080866"},{"0":"3056","vim_version":"7.3","1":"7.3","script_version":"2.2.15","2":"2.2.15","version_comment":"Added `TransliterateMotion' action\nAdded box drawing symbols\nImproved handling of transliteration tables from buffer variables\nImproved replace action\nSome Tr3Command fixes","3":"Added `TransliterateMotion' action\nAdded box drawing symbols\nImproved handling of transliteration tables from buffer variables\nImproved replace action\nSome Tr3Command fixes","package":"translit3-2.2.15.tar.gz","4":"translit3-2.2.15.tar.gz","src_id":"14885","5":"14885","creation_date":"1296163477","6":"1296163477"},{"0":"3056","vim_version":"7.3","1":"7.3","script_version":"2.2.14","2":"2.2.14","version_comment":"Made plugin use new vimpluginloader features, some fixes","3":"Made plugin use new vimpluginloader features, some fixes","package":"translit3-2.2.14.tar.gz","4":"translit3-2.2.14.tar.gz","src_id":"14756","5":"14756","creation_date":"1295115988","6":"1295115988"},{"0":"3056","vim_version":"9999","1":"9999","script_version":"2.2.13","2":"2.2.13","version_comment":"Reposting bundle due to core plugins update","3":"Reposting bundle due to core plugins update","package":"translit3-2.2.13.tar.gz","4":"translit3-2.2.13.tar.gz","src_id":"14641","5":"14641","creation_date":"1293570064","6":"1293570064"},{"0":"3056","vim_version":"7.3","1":"7.3","script_version":"2.2.13","2":"2.2.13","version_comment":"Fixed session support","3":"Fixed session support","package":"translit3-2.2.13.tar.gz","4":"translit3-2.2.13.tar.gz","src_id":"14639","5":"14639","creation_date":"1293569868","6":"1293569868"},{"0":"3056","vim_version":"7.3","1":"7.3","script_version":"2.2.12","2":"2.2.12","version_comment":"Added support for empty NoTransWord, EscSeq, BrkSeq and StopTrSymbs options","3":"Added support for empty NoTransWord, EscSeq, BrkSeq and StopTrSymbs options","package":"translit3-2.2.12.tar.gz","4":"translit3-2.2.12.tar.gz","src_id":"14621","5":"14621","creation_date":"1293324606","6":"1293324606"},{"0":"3056","vim_version":"7.3","1":"7.3","script_version":"2.2.11","2":"2.2.11","version_comment":"Added BreakFunc option\nMade conque_w function use new documented conque API (note that it is incompatible with old versions of conque)\nSome bug fixes","3":"Added BreakFunc option\nMade conque_w function use new documented conque API (note that it is incompatible with old versions of conque)\nSome bug fixes","package":"translit3-2.2.11.tar.gz","4":"translit3-2.2.11.tar.gz","src_id":"14599","5":"14599","creation_date":"1292972562","6":"1292972562"},{"0":"3056","vim_version":"9999","1":"9999","script_version":"2.2.10","2":"2.2.10","version_comment":"Reposting bundle due to core plugins update","3":"Reposting bundle due to core plugins update","package":"translit3-2.2.10.tar.gz","4":"translit3-2.2.10.tar.gz","src_id":"14566","5":"14566","creation_date":"1292713525","6":"1292713525"},{"0":"3056","vim_version":"7.3","1":"7.3","script_version":"2.2.10","2":"2.2.10","version_comment":"Fixed conque write function","3":"Fixed conque write function","package":"translit3-2.2.10.tar.gz","4":"translit3-2.2.10.tar.gz","src_id":"14492","5":"14492","creation_date":"1292192903","6":"1292192903"},{"0":"3056","vim_version":"7.3","1":"7.3","script_version":"2.2.6","2":"2.2.6","version_comment":"Added support for multicharacter strings for \\tr, \\tt, \\tT, \\tf and \\tF commands","3":"Added support for multicharacter strings for \\tr, \\tt, \\tT, \\tf and \\tF commands","package":"translit3-2.2.6.tar.gz","4":"translit3-2.2.6.tar.gz","src_id":"14362","5":"14362","creation_date":"1290574620","6":"1290574620"},{"0":"3056","vim_version":"9999","1":"9999","script_version":"2.2.2","2":"2.2.2","version_comment":"Reposting bundle due to core plugins update","3":"Reposting bundle due to core plugins update","package":"translit3-2.2.2.tar.gz","4":"translit3-2.2.2.tar.gz","src_id":"14319","5":"14319","creation_date":"1290257907","6":"1290257907"},{"0":"3056","vim_version":"7.2","1":"7.2","script_version":"2.2.2","2":"2.2.2","version_comment":"Removed <Nop> mappings detection for <vim-7.3.32\nFixed esc consuming after inputting multiple characters transliteration sequences","3":"Removed <Nop> mappings detection for <vim-7.3.32\nFixed esc consuming after inputting multiple characters transliteration sequences","package":"translit3-2.2.2.tar.gz","4":"translit3-2.2.2.tar.gz","src_id":"14100","5":"14100","creation_date":"1287751099","6":"1287751099"},{"0":"3056","vim_version":"7.2","1":"7.2","script_version":"2.2.1","2":"2.2.1","version_comment":"Added support for vim-7.3.32 patch. Note that format of the `exmaps' key of tof buffer dictionary changed","3":"Added support for vim-7.3.32 patch. Note that format of the `exmaps' key of tof buffer dictionary changed","package":"translit3-2.2.1.tar.gz","4":"translit3-2.2.1.tar.gz","src_id":"14088","5":"14088","creation_date":"1287612224","6":"1287612224"},{"0":"3056","vim_version":"7.2","1":"7.2","script_version":"2.2","2":"2.2","version_comment":"Added replacements for r, t, T, f and F normal mode commands: so now if you want to replace character under cursor with \u00c3\u0083\u00e2\u0080\u009a\u00c3\u0082\u00c2\u00ab, you will need to type \\tr<< in normal mode (works only for single character replacements).","3":"Added replacements for r, t, T, f and F normal mode commands: so now if you want to replace character under cursor with \u00c3\u0083\u00e2\u0080\u009a\u00c3\u0082\u00c2\u00ab, you will need to type \\tr<< in normal mode (works only for single character replacements).","package":"translit3-2.2.tar.gz","4":"translit3-2.2.tar.gz","src_id":"13886","5":"13886","creation_date":"1285176138","6":"1285176138"},{"0":"3056","vim_version":"7.2","1":"7.2","script_version":"2.1.1","2":"2.1.1","version_comment":"Fixed bug with multicharacter source strings (like \u00c3\u0083\u00e2\u0080\u009a\u00c3\u0082\u00c2\u00abch \u00c3\u0083\u00c2\u00a2\u00c3\u0082\u00e2\u0080\u00a0\u00c3\u0082\u00e2\u0080\u0099 \u00c3\u0083\u00e2\u0080\u0098\u00c3\u0082\u00e2\u0080\u00a1\u00c3\u0083\u00e2\u0080\u009a\u00c3\u0082\u00c2\u00bb)","3":"Fixed bug with multicharacter source strings (like \u00c3\u0083\u00e2\u0080\u009a\u00c3\u0082\u00c2\u00abch \u00c3\u0083\u00c2\u00a2\u00c3\u0082\u00e2\u0080\u00a0\u00c3\u0082\u00e2\u0080\u0099 \u00c3\u0083\u00e2\u0080\u0098\u00c3\u0082\u00e2\u0080\u00a1\u00c3\u0083\u00e2\u0080\u009a\u00c3\u0082\u00c2\u00bb)","package":"translit3-2.1.1.tar.gz","4":"translit3-2.1.1.tar.gz","src_id":"13836","5":"13836","creation_date":"1284568455","6":"1284568455"},{"0":"3056","vim_version":"7.2","1":"7.2","script_version":"2.1","2":"2.1","version_comment":"Added WriteFunc option (allows to override method used to send strings to buffer), added Conque Shell plugin support, fixed behavior when backspace option is not set","3":"Added WriteFunc option (allows to override method used to send strings to buffer), added Conque Shell plugin support, fixed behavior when backspace option is not set","package":"translit3-2.1.tar.gz","4":"translit3-2.1.tar.gz","src_id":"13823","5":"13823","creation_date":"1284464527","6":"1284464527"},{"0":"3056","vim_version":"7.2","1":"7.2","script_version":"2.0.6","2":"2.0.6","version_comment":"Added ConfigDir option, added tests, some bug fixes","3":"Added ConfigDir option, added tests, some bug fixes","package":"translit3-2.0.6.tar.gz","4":"translit3-2.0.6.tar.gz","src_id":"13718","5":"13718","creation_date":"1283121461","6":"1283121461"},{"0":"3056","vim_version":"7.2","1":"7.2","script_version":"2.0.5","2":"2.0.5","version_comment":"Made `Transliterate' mapping (it shows prompt and transliterates user input) use stuf\/cinput function (so that this prompts now have their own history) and new completion","3":"Made `Transliterate' mapping (it shows prompt and transliterates user input) use stuf\/cinput function (so that this prompts now have their own history) and new completion","package":"translit3-2.0.5.tar.gz","4":"translit3-2.0.5.tar.gz","src_id":"13697","5":"13697","creation_date":"1282924715","6":"1282924715"},{"0":"3056","vim_version":"7.2","1":"7.2","script_version":"2.0.3","2":"2.0.3","version_comment":"Translated messages to Russian","3":"Translated messages to Russian","package":"translit3-2.0.3.tar.gz","4":"translit3-2.0.3.tar.gz","src_id":"13671","5":"13671","creation_date":"1282733956","6":"1282733956"},{"0":"3056","vim_version":"7.2","1":"7.2","script_version":"2.0.2","2":"2.0.2","version_comment":"Some fixes to tof\/notransword plugin","3":"Some fixes to tof\/notransword plugin","package":"translit3-2.0.2.tar.gz","4":"translit3-2.0.2.tar.gz","src_id":"13652","5":"13652","creation_date":"1282575898","6":"1282575898"},{"0":"3056","vim_version":"7.2","1":"7.2","script_version":"2.0.1","2":"2.0.1","version_comment":"Updated russian documentation","3":"Updated russian documentation","package":"translit3-2.0.1.tar.gz","4":"translit3-2.0.1.tar.gz","src_id":"13639","5":"13639","creation_date":"1282412571","6":"1282412571"},{"0":"3056","vim_version":"7.2","1":"7.2","script_version":"2.0","2":"2.0","version_comment":"This is the first version published here that contains translit3 splitted into 6 plugins","3":"This is the first version published here that contains translit3 splitted into 6 plugins","package":"translit3-2.0.tar.gz","4":"translit3-2.0.tar.gz","src_id":"13542","5":"13542","creation_date":"1281420410","6":"1281420410"},{"0":"3056","vim_version":"7.2","1":"7.2","script_version":"2.0","2":"2.0","version_comment":"This is the first version published here that contains translit3 splitted into 6 plugins","3":"This is the first version published here that contains translit3 splitted into 6 plugins","package":"translit3-2.0.tar.xz","4":"translit3-2.0.tar.xz","src_id":"13482","5":"13482","creation_date":"1280951454","6":"1280951454"},{"0":"3056","vim_version":"7.2","1":"7.2","script_version":"1","2":"1","version_comment":"Initial upload","3":"Initial upload","package":"translit3-0.tar.xz","4":"translit3-0.tar.xz","src_id":"12824","5":"12824","creation_date":"1271177131","6":"1271177131"}]},"3055":{"script_id":"3055","0":"3055","script_name":"ciscoasa.vim","1":"ciscoasa.vim","script_type":"syntax","2":"syntax","summary":"Cisco ASA firewall syntax highlighting","3":"Cisco ASA firewall syntax highlighting","description":"Cisco ASA - Adaptive Security Appliance\r\n\r\nThis syntax file will highlight the many common structures of the configuration. It helps to prevent some obvious mistakes and makes the result a lot more readable.\r\n\r\nThe syntax is far from complete, but many important parts have been implemented.\r\n","4":"Cisco ASA - Adaptive Security Appliance\r\n\r\nThis syntax file will highlight the many common structures of the configuration. It helps to prevent some obvious mistakes and makes the result a lot more readable.\r\n\r\nThe syntax is far from complete, but many important parts have been implemented.\r\n","install_details":"Put the \"ciscoasa.vim\" file in ~\/.vim\/syntax and you can use the command :set syn=ciscoasa in vim to enable.","5":"Put the \"ciscoasa.vim\" file in ~\/.vim\/syntax and you can use the command :set syn=ciscoasa in vim to enable.","first_name":"Bertho","6":"Bertho","last_name":"Stultiens","7":"Stultiens","releases":[{"0":"3055","vim_version":"6.0","1":"6.0","script_version":"1.0.0","2":"1.0.0","version_comment":"Initial upload","3":"Initial upload","package":"ciscoasa.tar.gz","4":"ciscoasa.tar.gz","src_id":"12823","5":"12823","creation_date":"1271167043","6":"1271167043"}]},"3054":{"script_id":"3054","0":"3054","script_name":"Otter.vim","1":"Otter.vim","script_type":"syntax","2":"syntax","summary":"Otter theorem prover input file highlighter","3":"Otter theorem prover input file highlighter","description":"Highlight input files for the Otter theorem prover. ( http:\/\/www.mcs.anl.gov\/research\/projects\/AR\/otter\/ )\r\n","4":"Highlight input files for the Otter theorem prover. ( http:\/\/www.mcs.anl.gov\/research\/projects\/AR\/otter\/ )\r\n","install_details":"Put the following in your ~\/.vimrc\r\n\r\nau BufRead,BufNewFile *.in set filetype=otter\r\nau! Syntax otter source \/path\/to\/otter.vim\r\n\r\n","5":"Put the following in your ~\/.vimrc\r\n\r\nau BufRead,BufNewFile *.in set filetype=otter\r\nau! Syntax otter source \/path\/to\/otter.vim\r\n\r\n","first_name":"steven","6":"steven","last_name":"vanhorn","7":"vanhorn","releases":[{"0":"3054","vim_version":"6.0","1":"6.0","script_version":"4.12.10","2":"4.12.10","version_comment":"Initial upload","3":"Initial upload","package":"otter[1].vim","4":"otter[1].vim","src_id":"12821","5":"12821","creation_date":"1271098147","6":"1271098147"}]},"3053":{"script_id":"3053","0":"3053","script_name":"Maynard","1":"Maynard","script_type":"utility","2":"utility","summary":"An RPN calculator in an input() prompt","3":"An RPN calculator in an input() prompt","description":"Maynard is a (very) simple stack-based RPN calculator written in Python 2.5+ and featuring Python Decimal numbers.\r\n\r\nIt uses the Vim \"input()\" function to show the stack and to get input from the user. So if you enter \"2 3 *\" you'll get \"6\" on the stack. Etc. \r\nPress the = key to write the number at the top of the stack into the current buffer. Press <ESC> to exit. Look at the source for other commands.\r\n\r\nIf you have never used an RPN calculator this will probably annoy you, but if you have ever used an HP calculator then it should be reasonably familiar.  I'm keen to get feedback on this one, but please be kind: I'm new to both Vim and Python so it can probably be improved in all sorts of ways.\r\n\r\ntoby@cpan.org\r\n\r\nBrother Maynard is a Python reference by the way...","4":"Maynard is a (very) simple stack-based RPN calculator written in Python 2.5+ and featuring Python Decimal numbers.\r\n\r\nIt uses the Vim \"input()\" function to show the stack and to get input from the user. So if you enter \"2 3 *\" you'll get \"6\" on the stack. Etc. \r\nPress the = key to write the number at the top of the stack into the current buffer. Press <ESC> to exit. Look at the source for other commands.\r\n\r\nIf you have never used an RPN calculator this will probably annoy you, but if you have ever used an HP calculator then it should be reasonably familiar.  I'm keen to get feedback on this one, but please be kind: I'm new to both Vim and Python so it can probably be improved in all sorts of ways.\r\n\r\ntoby@cpan.org\r\n\r\nBrother Maynard is a Python reference by the way...","install_details":"Unzip maynard.zip into any directory where you keep python files or VIM scripts.  It will create maynard.py and decimal_tools.py.  If you keep them together then Python will be able to find decimal_tools when it needs it. However you may still need to set $PYTHONPATH in your profile so point at the directory where you put \"python_tools.py\".  Try adding something like this to your .profile (assuming Mac or Linux):\r\n\r\nexport PYTHONPATH=.:<path-to-file>\r\n\r\nAdd a line something like this to your .vimrc file\r\n:command! -nargs=0 <name> pyfile <path-to-file>\/maynard.py\r\n\r\nwhere <name> is whatever you want to use to call it, and <path-to-file> reflects where you unzipped it.","5":"Unzip maynard.zip into any directory where you keep python files or VIM scripts.  It will create maynard.py and decimal_tools.py.  If you keep them together then Python will be able to find decimal_tools when it needs it. However you may still need to set $PYTHONPATH in your profile so point at the directory where you put \"python_tools.py\".  Try adding something like this to your .profile (assuming Mac or Linux):\r\n\r\nexport PYTHONPATH=.:<path-to-file>\r\n\r\nAdd a line something like this to your .vimrc file\r\n:command! -nargs=0 <name> pyfile <path-to-file>\/maynard.py\r\n\r\nwhere <name> is whatever you want to use to call it, and <path-to-file> reflects where you unzipped it.","first_name":"Toby","6":"Toby","last_name":"Thurston","7":"Thurston","releases":[{"0":"3053","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"maynard.zip","4":"maynard.zip","src_id":"12811","5":"12811","creation_date":"1270997957","6":"1270997957"}]},"3052":{"script_id":"3052","0":"3052","script_name":"changesPlugin","1":"changesPlugin","script_type":"utility","2":"utility","summary":"indicate changes of a buffer","3":"indicate changes of a buffer","description":"PLEASE RATE THIS PLUGIN, IF YOU LIKE IT!\r\n\r\nFor a screenshot of the plugin see http:\/\/www.256bit.org\/~chrisbra\/changes.png\r\n\r\nFollow this plugin at github:\r\nhttp:\/\/github.com\/chrisbra\/changesPlugin\r\n\r\n1. Functionality\r\n\r\nThis plugin was written to help visualize which lines have been changes since\r\nediting started for a file. The plugin was inspired by so called changed-bars,\r\navailable at other editors, such as Embarcadero C++ Builder (there it is\r\ncalled Change Bars, see:\r\nhttp:\/\/edn.embarcadero.com\/article\/33453#6PersonalDeveloperProductivity)\r\nor Visual Studio where it is called indicator margin (see\r\nhttp:\/\/blog.eveningcreek.com\/?p=151).\r\n\r\nChangesPlugin.vim uses the |diff|-feature of vim and compares the actual\r\nbuffer with it's saved state. In order to highlight the indicator signs at the\r\nfirst column, its using |signs|. For newly added lines, the first column will\r\nbe displayed with a leading '+' and highlighted using the DiffAdd highlighting\r\n(see |hl-DiffAdd|), deleted lines will be indicated by a '-' with a\r\nDiffDelete highlighting (see |hl-DiffDelete|) and modified lines will be\r\ndisplayed using '*' and a DiffChange highlighting (see |hl-DiffChange|).\r\n\r\nThis means, that in order to use this plugin you need a vim, that was built\r\nwith |+signs|-support and |+diff|-support and you also need an executable diff\r\ncommand. If neither of these conditions are met, changePlugin.vim will issue a\r\nwarning and abort.\r\n\r\n\t\t\t\t\t\t\t *:EnableChanges*\r\nBy default the plugin is not enabled. To enable it enter >\r\n    :EnableChanges\r\nWhen you run this command, changesPlugin.vim diffs the current file agains\r\nits saved file on disk and displays the changes in the first column.\r\n\r\n\t\t\t\t\t\t\t*:DisableChanges*\r\nIf you want to disable the plugin, enter >\r\n    :DisableChanges\r\n\r\n==============================================================================\r\n\t\t\t\t\t\t\t*changesPlugin-Config*\r\n2. Configuring changesPlugin.vim\r\n\r\nThere are basically four different configuration options available.\r\n\r\n2.1 Highlighte the whole line\r\nBy default, changesPlugin.vim will only indicate a change in the first column.\r\nSetting g:changes_hl_lines to 1 will highlight the whole line. By default this\r\nvariable is unset (which is the same as setting it to 0).\r\nIf you'd like to have this, set this variable in your |.vimrc| >\r\n    :let g:changes_hl_lines=1\r\n\r\n2.2 Auto-refresh the changes\r\nBy default changesPlugin.vim will not automatically update the view. You can\r\nhowever configure it to do so. This will use an |CursorHold| autocommand to\r\nupdate the indicator signs after |'updatetime'| seconds in Normal mode when\r\nno key is pressed. To enable this feature, put this in your |.vimrc| >\r\n    let g:changes_autocmd=1\r\n\r\n2.3 Show what the indicator signs mean.\r\nBy default, whenever you run |:EnableChanges|, changesVim will print a short\r\nstatus message, what each sign means. If you don't want this, put this in your\r\n|.vimrc| >\r\n    :let g:changes_verbose=0\r\n\r\n2.4 Specify different colors.\r\nchangesVim uses the highlighting used for |diff| mode to indicate the change\r\nin a buffer. This is consistent, since when you're already used to |vimdiff|\r\nyou'll probably also know the highlighting. If for any reason you do not like\r\nthe colors, you have to define your own highlighting items.\r\nIf for example you want the DiffAdd highlighting to be displayed like White on\r\na Blue background, you can define it as follows in your |.vimrc| >\r\n\r\n    :hi DiffAdd term=bold ctermbg=4 guibg=DarkBlue\r\n\r\nIn the same way, you can change DiffDelete for indicating deleted lines and\r\nDiffChange for indicating modified lines. You can also specify your favorite\r\nhighlighting colors using your own build |colorscheme|.\r\n\r\n==============================================================================\r\n3. changesPlugin History\t\t\t\t*changesPlugin-history*\r\n    0.2: Apr 11, 2010:\tAdded Documentation\r\n\t\t\tcreated an autoload version\r\n    0.1: Apr 10, 2010:\tFirst working version","4":"PLEASE RATE THIS PLUGIN, IF YOU LIKE IT!\r\n\r\nFor a screenshot of the plugin see http:\/\/www.256bit.org\/~chrisbra\/changes.png\r\n\r\nFollow this plugin at github:\r\nhttp:\/\/github.com\/chrisbra\/changesPlugin\r\n\r\n1. Functionality\r\n\r\nThis plugin was written to help visualize which lines have been changes since\r\nediting started for a file. The plugin was inspired by so called changed-bars,\r\navailable at other editors, such as Embarcadero C++ Builder (there it is\r\ncalled Change Bars, see:\r\nhttp:\/\/edn.embarcadero.com\/article\/33453#6PersonalDeveloperProductivity)\r\nor Visual Studio where it is called indicator margin (see\r\nhttp:\/\/blog.eveningcreek.com\/?p=151).\r\n\r\nChangesPlugin.vim uses the |diff|-feature of vim and compares the actual\r\nbuffer with it's saved state. In order to highlight the indicator signs at the\r\nfirst column, its using |signs|. For newly added lines, the first column will\r\nbe displayed with a leading '+' and highlighted using the DiffAdd highlighting\r\n(see |hl-DiffAdd|), deleted lines will be indicated by a '-' with a\r\nDiffDelete highlighting (see |hl-DiffDelete|) and modified lines will be\r\ndisplayed using '*' and a DiffChange highlighting (see |hl-DiffChange|).\r\n\r\nThis means, that in order to use this plugin you need a vim, that was built\r\nwith |+signs|-support and |+diff|-support and you also need an executable diff\r\ncommand. If neither of these conditions are met, changePlugin.vim will issue a\r\nwarning and abort.\r\n\r\n\t\t\t\t\t\t\t *:EnableChanges*\r\nBy default the plugin is not enabled. To enable it enter >\r\n    :EnableChanges\r\nWhen you run this command, changesPlugin.vim diffs the current file agains\r\nits saved file on disk and displays the changes in the first column.\r\n\r\n\t\t\t\t\t\t\t*:DisableChanges*\r\nIf you want to disable the plugin, enter >\r\n    :DisableChanges\r\n\r\n==============================================================================\r\n\t\t\t\t\t\t\t*changesPlugin-Config*\r\n2. Configuring changesPlugin.vim\r\n\r\nThere are basically four different configuration options available.\r\n\r\n2.1 Highlighte the whole line\r\nBy default, changesPlugin.vim will only indicate a change in the first column.\r\nSetting g:changes_hl_lines to 1 will highlight the whole line. By default this\r\nvariable is unset (which is the same as setting it to 0).\r\nIf you'd like to have this, set this variable in your |.vimrc| >\r\n    :let g:changes_hl_lines=1\r\n\r\n2.2 Auto-refresh the changes\r\nBy default changesPlugin.vim will not automatically update the view. You can\r\nhowever configure it to do so. This will use an |CursorHold| autocommand to\r\nupdate the indicator signs after |'updatetime'| seconds in Normal mode when\r\nno key is pressed. To enable this feature, put this in your |.vimrc| >\r\n    let g:changes_autocmd=1\r\n\r\n2.3 Show what the indicator signs mean.\r\nBy default, whenever you run |:EnableChanges|, changesVim will print a short\r\nstatus message, what each sign means. If you don't want this, put this in your\r\n|.vimrc| >\r\n    :let g:changes_verbose=0\r\n\r\n2.4 Specify different colors.\r\nchangesVim uses the highlighting used for |diff| mode to indicate the change\r\nin a buffer. This is consistent, since when you're already used to |vimdiff|\r\nyou'll probably also know the highlighting. If for any reason you do not like\r\nthe colors, you have to define your own highlighting items.\r\nIf for example you want the DiffAdd highlighting to be displayed like White on\r\na Blue background, you can define it as follows in your |.vimrc| >\r\n\r\n    :hi DiffAdd term=bold ctermbg=4 guibg=DarkBlue\r\n\r\nIn the same way, you can change DiffDelete for indicating deleted lines and\r\nDiffChange for indicating modified lines. You can also specify your favorite\r\nhighlighting colors using your own build |colorscheme|.\r\n\r\n==============================================================================\r\n3. changesPlugin History\t\t\t\t*changesPlugin-history*\r\n    0.2: Apr 11, 2010:\tAdded Documentation\r\n\t\t\tcreated an autoload version\r\n    0.1: Apr 10, 2010:\tFirst working version","install_details":"This plugin comes as vimball, which makes it really easy to install it into the right place.\r\n1) Edit changes.vba with your vim (:e changes.vim)\r\n2) From within vim, simply source the file using\r\n:so %\r\n3) Restart vim to autoload the plugin and the documentation\r\n:q\r\n4) Read the help at :h changesPlugin.txt\r\n\r\nSee also the help available for vimballs at :h vimball-intro","5":"This plugin comes as vimball, which makes it really easy to install it into the right place.\r\n1) Edit changes.vba with your vim (:e changes.vim)\r\n2) From within vim, simply source the file using\r\n:so %\r\n3) Restart vim to autoload the plugin and the documentation\r\n:q\r\n4) Read the help at :h changesPlugin.txt\r\n\r\nSee also the help available for vimballs at :h vimball-intro","first_name":"Christian","6":"Christian","last_name":"Brabandt","7":"Brabandt","releases":[{"0":"3052","vim_version":"7.4","1":"7.4","script_version":"15","2":"15","version_comment":"NF: use TextChanged autocommand to update signs faster\nNF: use new utf8 symbols\nNF: Hide SignColumn\nNF: include some nice looking icons for gvim\nBF: Code cleanup\nBF: resolve symlinks\nNF: airline integration\nNF: :CF\nNF: :CT\nBF: only draw at most one deleted sign, if a range of several consecutive lines have been deleted\nNF: only place newly changed lines (instead of always removing all previous signs and adding them again)\nNF: if g:changes_linehi_diff is set, tries to highlight changes within a line by overlaying CursorColumn highlighting over that parts.\nBF: try to skip expensive TextChanged calls if possible.\nBF: detect other signs correctly (didn't work with non-english locale)\nBF: do not try to detect changes on vim help files and read only files\nBF: calling :DC twice would cause an error\nBF: Make use of patch 7.4.341\nBF: When undefining signs and starting the gui, make sure no '[Deleted]' signs are left over\nBF: Clear SignColumn before linking it to Normal group\nBF: Make sure a warning message is shown for :EC\nBF: Catch E255 when defining signs\nBF: prevent recursively calling FocusGained autocommand on windows\nNF: ChangesPlugin-Signcol\nBF: if vim-gitgutter is installed and the current buffer is handled by vim-gitgutter, let gitgutter handle the current buffer (issue https:\/\/github.com\/chrisbra\/changesPlugin\/issues\/12, reported by Gray-Wind, thanks!)\nNF: g:changes_fast variable (to enable more correct at the cost of being possibly slower placement of signs).\nBF: when updating signs, make sure that the first line of a consecutive number has the correcty type\nNF: In insert mode, when <CR> is pressed, update the signs immediately\nNF: InsertEnter\/Leave autocommands to update signs\nNF: Stage hunks for git\nNF: Ignore special buffers (help window, quickfix buffer, command line window..)\nBF: Make :CL only add the first line of each hunk to the location list.\n(automatically uploaded)","3":"NF: use TextChanged autocommand to update signs faster\nNF: use new utf8 symbols\nNF: Hide SignColumn\nNF: include some nice looking icons for gvim\nBF: Code cleanup\nBF: resolve symlinks\nNF: airline integration\nNF: :CF\nNF: :CT\nBF: only draw at most one deleted sign, if a range of several consecutive lines have been deleted\nNF: only place newly changed lines (instead of always removing all previous signs and adding them again)\nNF: if g:changes_linehi_diff is set, tries to highlight changes within a line by overlaying CursorColumn highlighting over that parts.\nBF: try to skip expensive TextChanged calls if possible.\nBF: detect other signs correctly (didn't work with non-english locale)\nBF: do not try to detect changes on vim help files and read only files\nBF: calling :DC twice would cause an error\nBF: Make use of patch 7.4.341\nBF: When undefining signs and starting the gui, make sure no '[Deleted]' signs are left over\nBF: Clear SignColumn before linking it to Normal group\nBF: Make sure a warning message is shown for :EC\nBF: Catch E255 when defining signs\nBF: prevent recursively calling FocusGained autocommand on windows\nNF: ChangesPlugin-Signcol\nBF: if vim-gitgutter is installed and the current buffer is handled by vim-gitgutter, let gitgutter handle the current buffer (issue https:\/\/github.com\/chrisbra\/changesPlugin\/issues\/12, reported by Gray-Wind, thanks!)\nNF: g:changes_fast variable (to enable more correct at the cost of being possibly slower placement of signs).\nBF: when updating signs, make sure that the first line of a consecutive number has the correcty type\nNF: In insert mode, when <CR> is pressed, update the signs immediately\nNF: InsertEnter\/Leave autocommands to update signs\nNF: Stage hunks for git\nNF: Ignore special buffers (help window, quickfix buffer, command line window..)\nBF: Make :CL only add the first line of each hunk to the location list.\n(automatically uploaded)","package":"changes.zip","4":"changes.zip","src_id":"22799","5":"22799","creation_date":"1421353543","6":"1421353543"},{"0":"3052","vim_version":"7.3","1":"7.3","script_version":"14","2":"14","version_comment":"BF: Exception not caught (reported by Marco, thanks!)\n        BF: Prevent flickering by resetting SignColumn on\n\t    updates (reported by Marco, thanks!)\n        BF: parse diff output instead of relying on vimdiff\n\t    and parsing the syntax items (prevents flickering\n\t    since no window needs to be split)\n        BF: avoid error messages, when buffer is ignored\n\t    (https:\/\/github.com\/chrisbra\/changesPlugin\/issues\/6\n\t    reported by mpfusion, thanks!)\n        BF: avoid error messages, using |DC|\n\t    (https:\/\/github.com\/chrisbra\/changesPlugin\/issues\/7\n\t    reported by mpfusion, thanks!)\n        BF: don't mess with the |alternate-file|\n\t    (https:\/\/github.com\/chrisbra\/changesPlugin\/issues\/8\n\t    reported by mpfusion, thanks!)\n        NF: |ChangesPlugin-preview|\n        NF: |ChangesPlugin-Maps|\n            [h\/]h move to previous\/next changed line\n(automatically uploaded)","3":"BF: Exception not caught (reported by Marco, thanks!)\n        BF: Prevent flickering by resetting SignColumn on\n\t    updates (reported by Marco, thanks!)\n        BF: parse diff output instead of relying on vimdiff\n\t    and parsing the syntax items (prevents flickering\n\t    since no window needs to be split)\n        BF: avoid error messages, when buffer is ignored\n\t    (https:\/\/github.com\/chrisbra\/changesPlugin\/issues\/6\n\t    reported by mpfusion, thanks!)\n        BF: avoid error messages, using |DC|\n\t    (https:\/\/github.com\/chrisbra\/changesPlugin\/issues\/7\n\t    reported by mpfusion, thanks!)\n        BF: don't mess with the |alternate-file|\n\t    (https:\/\/github.com\/chrisbra\/changesPlugin\/issues\/8\n\t    reported by mpfusion, thanks!)\n        NF: |ChangesPlugin-preview|\n        NF: |ChangesPlugin-Maps|\n            [h\/]h move to previous\/next changed line\n(automatically uploaded)","package":"changes-0.14.vmb","4":"changes-0.14.vmb","src_id":"20646","5":"20646","creation_date":"1376511142","6":"1376511142"},{"0":"3052","vim_version":"7.3","1":"7.3","script_version":"13","2":"13","version_comment":"BF: Plugin used :EnableDisplayChanges, but documentation talked about EnableChanges (same for DisableChanges)\nBF: Don't load the autoload script when sourcing the plugin (reported by Sergey Kholev, thanks!)\n(automatically uploaded)","3":"BF: Plugin used :EnableDisplayChanges, but documentation talked about EnableChanges (same for DisableChanges)\nBF: Don't load the autoload script when sourcing the plugin (reported by Sergey Kholev, thanks!)\n(automatically uploaded)","package":"changes-0.13.vmb","4":"changes-0.13.vmb","src_id":"19527","5":"19527","creation_date":"1361053103","6":"1361053103"},{"0":"3052","vim_version":"7.3","1":"7.3","script_version":"12","2":"12","version_comment":"NF: Fix issue #3 from github (check changes against\n    any file, suggested by Alessio Bolognino, Thanks!)\nBF: Fix E117 error (patch by Mate Gabri, Thanks!)\nBF: Check, that the current file is readable, before\n    diffing (patch by Mate Gabri, Thanks!)\nBF: Sometimes, the previous Window is not accessible\n    anymore\n    (http:\/\/github.com\/chrisbra\/changesPlugin\/issues\/5\n    by Mate Gabri, Thanks!)\n(automatically uploaded)","3":"NF: Fix issue #3 from github (check changes against\n    any file, suggested by Alessio Bolognino, Thanks!)\nBF: Fix E117 error (patch by Mate Gabri, Thanks!)\nBF: Check, that the current file is readable, before\n    diffing (patch by Mate Gabri, Thanks!)\nBF: Sometimes, the previous Window is not accessible\n    anymore\n    (http:\/\/github.com\/chrisbra\/changesPlugin\/issues\/5\n    by Mate Gabri, Thanks!)\n(automatically uploaded)","package":"changes-0.12.vmb","4":"changes-0.12.vmb","src_id":"17356","5":"17356","creation_date":"1328044215","6":"1328044215"},{"0":"3052","vim_version":"7.0","1":"7.0","script_version":"0.11","2":"0.11","version_comment":"BF: Document, that |InsertLeave| autocommand is used as autocommand\r\nBF: generate the help file with 'et' set, so that the README at github looks prettier\r\nBF: When staying in diff mode, don't reset 'fdm' and apply syntax coloring to scratch buffer\r\nBF: the check for the diff executable does not work as expected (Reported by Sergey Khorev), additionally outputting the Warnings did not work in that case","3":"BF: Document, that |InsertLeave| autocommand is used as autocommand\r\nBF: generate the help file with 'et' set, so that the README at github looks prettier\r\nBF: When staying in diff mode, don't reset 'fdm' and apply syntax coloring to scratch buffer\r\nBF: the check for the diff executable does not work as expected (Reported by Sergey Khorev), additionally outputting the Warnings did not work in that case","package":"changes-0.11.vba","4":"changes-0.11.vba","src_id":"12942","5":"12942","creation_date":"1273001154","6":"1273001154"},{"0":"3052","vim_version":"7.0","1":"7.0","script_version":"0.10","2":"0.10","version_comment":"Fixed Issue 1 from github (http:\/\/github.com\/chrisbra\/changesPlugin\/issues\/1\/find)\r\n","3":"Fixed Issue 1 from github (http:\/\/github.com\/chrisbra\/changesPlugin\/issues\/1\/find)\r\n","package":"changes.vba","4":"changes.vba","src_id":"12913","5":"12913","creation_date":"1272486565","6":"1272486565"},{"0":"3052","vim_version":"7.0","1":"7.0","script_version":"0.9","2":"0.9","version_comment":"0.9: Apr 24, 2010:  \r\nNF: You can now use different VCS Systems for each buffer you are using.\r\nNF: Stay in diff mode\r\nBF: Fix the display of deleted signs\r\nBF: Undefining old signs, so that changing g:changes_hl_lines works\r\nBF: Some more error handling.\r\nNF: Show an overview for changed lines in location-list (|:CL|)\r\nNF: Show what each sign means using |:CC|\r\n\r\n0.8: Apr 22, 2010:  NF: Renamed the helpfile, to make it more obvious, that it refers to a plugin\r\nNF: Outputting name of checked file, if checking against VCS\r\nBF: Don't check for empty files.\r\nBF: Reworked the Message function\r\nBF: Don't try to place signs, if there are no differences (unreleased, VCS successfully tested with git, hg, svn, cvs, bzr)\r\n0.7: Apr 19, 2010:  \r\nNF: Check against a file in a VCS (unreleased, first working version, needs to be checked for each VCS)","3":"0.9: Apr 24, 2010:  \r\nNF: You can now use different VCS Systems for each buffer you are using.\r\nNF: Stay in diff mode\r\nBF: Fix the display of deleted signs\r\nBF: Undefining old signs, so that changing g:changes_hl_lines works\r\nBF: Some more error handling.\r\nNF: Show an overview for changed lines in location-list (|:CL|)\r\nNF: Show what each sign means using |:CC|\r\n\r\n0.8: Apr 22, 2010:  NF: Renamed the helpfile, to make it more obvious, that it refers to a plugin\r\nNF: Outputting name of checked file, if checking against VCS\r\nBF: Don't check for empty files.\r\nBF: Reworked the Message function\r\nBF: Don't try to place signs, if there are no differences (unreleased, VCS successfully tested with git, hg, svn, cvs, bzr)\r\n0.7: Apr 19, 2010:  \r\nNF: Check against a file in a VCS (unreleased, first working version, needs to be checked for each VCS)","package":"changes.vba","4":"changes.vba","src_id":"12895","5":"12895","creation_date":"1272128479","6":"1272128479"},{"0":"3052","vim_version":"7.0","1":"7.0","script_version":"0.6","2":"0.6","version_comment":"BF: also take care of DiffText from diff-mode (see :h hl-DiffText)","3":"BF: also take care of DiffText from diff-mode (see :h hl-DiffText)","package":"changes.vba","4":"changes.vba","src_id":"12826","5":"12826","creation_date":"1271189911","6":"1271189911"},{"0":"3052","vim_version":"6.0","1":"6.0","script_version":"0.5","2":"0.5","version_comment":"BF: error when trying to access b:diffhl in the scratch buffer. This should be fixed now (thanks Jeet Sukumaran!)\r\nBF: Use the correct highlighting groups (thanks Jeet Sukumaran!)\r\n","3":"BF: error when trying to access b:diffhl in the scratch buffer. This should be fixed now (thanks Jeet Sukumaran!)\r\nBF: Use the correct highlighting groups (thanks Jeet Sukumaran!)\r\n","package":"changes.vba","4":"changes.vba","src_id":"12820","5":"12820","creation_date":"1271096870","6":"1271096870"},{"0":"3052","vim_version":"7.0","1":"7.0","script_version":"0.4","2":"0.4","version_comment":"NF: |ToggleChangesView| \r\nNF: The autocommand checks, if the buffer has been modified, since the last time.\r\nBF: Do not mess with signs, that have not been placed by changesPlugin.vim\r\nBF: CleanUp was seriously messed up (sorry, I must have been asleep, when writing that)\r\nBF: Take care of 'foldcolumn' setting, which would be overwritten by the signs-column","3":"NF: |ToggleChangesView| \r\nNF: The autocommand checks, if the buffer has been modified, since the last time.\r\nBF: Do not mess with signs, that have not been placed by changesPlugin.vim\r\nBF: CleanUp was seriously messed up (sorry, I must have been asleep, when writing that)\r\nBF: Take care of 'foldcolumn' setting, which would be overwritten by the signs-column","package":"changes.vba","4":"changes.vba","src_id":"12815","5":"12815","creation_date":"1271056487","6":"1271056487"},{"0":"3052","vim_version":"7.0","1":"7.0","script_version":"0.3","2":"0.3","version_comment":"BF: redraw, so that the diff window will not be displayed\r\nNF: enabled GLVS (see |GLVS|)","3":"BF: redraw, so that the diff window will not be displayed\r\nNF: enabled GLVS (see |GLVS|)","package":"changes.vba","4":"changes.vba","src_id":"12814","5":"12814","creation_date":"1271011464","6":"1271011464"},{"0":"3052","vim_version":"7.2","1":"7.2","script_version":"0.2","2":"0.2","version_comment":"Initial upload","3":"Initial upload","package":"changes.vba","4":"changes.vba","src_id":"12810","5":"12810","creation_date":"1270990160","6":"1270990160"}]},"3051":{"script_id":"3051","0":"3051","script_name":"vimform","1":"vimform","script_type":"utility","2":"utility","summary":"Simple text-based forms for vim","3":"Simple text-based forms for vim","description":"This library provides simple text-based forms for vim. Currently supported UI elements:\r\n\r\n    - text fields (with optional completion, tooltips, and validation)\r\n    - check boxes\r\n\r\nCheck out further examples on:\r\nhttp:\/\/github.com\/tomtom\/vimform_vim\/tree\/master\/test\/\r\nhttp:\/\/github.com\/tomtom\/vimform_vim\/downloads\r\n","4":"This library provides simple text-based forms for vim. Currently supported UI elements:\r\n\r\n    - text fields (with optional completion, tooltips, and validation)\r\n    - check boxes\r\n\r\nCheck out further examples on:\r\nhttp:\/\/github.com\/tomtom\/vimform_vim\/tree\/master\/test\/\r\nhttp:\/\/github.com\/tomtom\/vimform_vim\/downloads\r\n","install_details":"In order to install the vba, open the vba file in VIM and type: >\r\n\r\n    :so %\r\n\r\nSee :help vimball for details.\r\n\r\nAlso available via git:\r\nhttp:\/\/github.com\/tomtom\/vimform_vim\r\n","5":"In order to install the vba, open the vba file in VIM and type: >\r\n\r\n    :so %\r\n\r\nSee :help vimball for details.\r\n\r\nAlso available via git:\r\nhttp:\/\/github.com\/tomtom\/vimform_vim\r\n","first_name":"Tom","6":"Tom","last_name":"Link","7":"Link","releases":[{"0":"3051","vim_version":"7.0","1":"7.0","script_version":"0.3","2":"0.3","version_comment":"- Canned forms\r\n- New \"widgets\": singlechoice, file, dir\r\n","3":"- Canned forms\r\n- New \"widgets\": singlechoice, file, dir\r\n","package":"vimform.vba","4":"vimform.vba","src_id":"12830","5":"12830","creation_date":"1271267525","6":"1271267525"},{"0":"3051","vim_version":"7.0","1":"7.0","script_version":"0.2","2":"0.2","version_comment":"Initial upload","3":"Initial upload","package":"vimform.vba","4":"vimform.vba","src_id":"12809","5":"12809","creation_date":"1270975206","6":"1270975206"}]},"3050":{"script_id":"3050","0":"3050","script_name":"smartmove.vim","1":"smartmove.vim","script_type":"utility","2":"utility","summary":"Some useful keymappings for movement","3":"Some useful keymappings for movement","description":"1. Jump to next tag on screen in a help file.\r\n\r\nWhen the cursor is at or after the last tag on the screen continue the search\r\nat the top of the screen.\r\n\r\nmapped to: <tab>, <s-tab> in normal mode\r\ndisable with: let g:loaded_smartmove_nexthelptag=-1\r\n\r\nThe mapping is created on BufEnter when buftype=help or the buffer is readonly\r\nand filetype=help.\r\n\r\n2. Use H and L instead of ctrl-f and ctrl-b\r\n\r\nWhen the cursor is at the top of the screen and H is pressed the screen is\r\nscrolled up. When count is given or the cursor is not at the top of the screen,\r\nthe default function of H is executed (Home). Similar for L.\r\n\r\nmapped to: H, L in normal and visual mode\r\ndisable with: let g:loaded_smartmove_smartscreen=-1\r\n\r\n3. Make Home\/End keys smarter\r\n\r\nHome key toggles between ^\/0 on normal lines. On wrapped lines it will move the\r\ncursor to the beginning of the current screen line and if it is already there\r\nit will move one line up. Similar functionality is provided for the End key.\r\n\r\nTo enable :call smartmove#MapHomeEnd()\r\n\r\nSimilar: vimscript#3336\r\n","4":"1. Jump to next tag on screen in a help file.\r\n\r\nWhen the cursor is at or after the last tag on the screen continue the search\r\nat the top of the screen.\r\n\r\nmapped to: <tab>, <s-tab> in normal mode\r\ndisable with: let g:loaded_smartmove_nexthelptag=-1\r\n\r\nThe mapping is created on BufEnter when buftype=help or the buffer is readonly\r\nand filetype=help.\r\n\r\n2. Use H and L instead of ctrl-f and ctrl-b\r\n\r\nWhen the cursor is at the top of the screen and H is pressed the screen is\r\nscrolled up. When count is given or the cursor is not at the top of the screen,\r\nthe default function of H is executed (Home). Similar for L.\r\n\r\nmapped to: H, L in normal and visual mode\r\ndisable with: let g:loaded_smartmove_smartscreen=-1\r\n\r\n3. Make Home\/End keys smarter\r\n\r\nHome key toggles between ^\/0 on normal lines. On wrapped lines it will move the\r\ncursor to the beginning of the current screen line and if it is already there\r\nit will move one line up. Similar functionality is provided for the End key.\r\n\r\nTo enable :call smartmove#MapHomeEnd()\r\n\r\nSimilar: vimscript#3336\r\n","install_details":"Unpack into vim runtime directory (eg. ~\/.vim)","5":"Unpack into vim runtime directory (eg. ~\/.vim)","first_name":"Marko","6":"Marko","last_name":"Mahni\u010d","7":"Mahnič","releases":[{"0":"3050","vim_version":"7.0","1":"7.0","script_version":"0.5.1","2":"0.5.1","version_comment":"minor fix","3":"minor fix","package":"smartmove.zip","4":"smartmove.zip","src_id":"12803","5":"12803","creation_date":"1270834217","6":"1270834217"},{"0":"3050","vim_version":"7.0","1":"7.0","script_version":"0.5","2":"0.5","version_comment":"Initial upload","3":"Initial upload","package":"smartmove.zip","4":"smartmove.zip","src_id":"12802","5":"12802","creation_date":"1270831679","6":"1270831679"}]},"3049":{"script_id":"3049","0":"3049","script_name":"acomment","1":"acomment","script_type":"utility","2":"utility","summary":"comment plugin for vim","3":"comment plugin for vim","description":"This plugin is Depreciated!","4":"This plugin is Depreciated!","install_details":"put all files into .\/vim\/plugin\/","5":"put all files into .\/vim\/plugin\/","first_name":"-","6":"-","last_name":"-","7":"-","releases":[{"0":"3049","vim_version":"7.0","1":"7.0","script_version":"2.3","2":"2.3","version_comment":"fix bugs.","3":"fix bugs.","package":"acomment.vim","4":"acomment.vim","src_id":"22343","5":"22343","creation_date":"1408332984","6":"1408332984"}]},"3048":{"script_id":"3048","0":"3048","script_name":"vicom","1":"vicom","script_type":"utility","2":"utility","summary":"Intelligent Line Commenter for the most popular programs [LINUX ONLY]","3":"Intelligent Line Commenter for the most popular programs [LINUX ONLY]","description":"Vicom uses the [Ctrl X] and [Ctrl Y] keys to comment or uncomment lines of code in a program.\r\nIt does this by examining the filename entered on the command line. It automatically writes\r\nsuitable key maps to a small r\/w buffer located in the .vimrc file. Allowing the same pair of\r\nkeys to perform the comment or uncomment function for different comment styles.\r\nVicom's purpose is to rapidly comment out or restore blocks of source code whilst testing and\r\ndebugging. Used with the Vimake package it turns Vim in to a powerful programmers workbench.\r\nVicom once installed runs as an alias to both Vim and Gvim. So if you normally start a Vim\r\nsession such as:\r\n        vi newprog.cc   or gvim newprog.cpp\r\nVicom first examines the command line and determines that the comment and uncomment maps should\r\nbe for a cpp program. It then writes these maps to a small buffer then passes control on to Vim\r\nto perform its normal loading of the file. Now when you press <Ctl+X> or <Ctl+Y> the correct\r\ncomments occur in your program. If you load a file type that Vicom does not recognize the keymap\r\nbuffer is cleared.\r\nVicom recognizes the following file types. Gnu gcc,g++,Nasm,AT&T(gas)as,ruby,perl,python and bash.\r\n","4":"Vicom uses the [Ctrl X] and [Ctrl Y] keys to comment or uncomment lines of code in a program.\r\nIt does this by examining the filename entered on the command line. It automatically writes\r\nsuitable key maps to a small r\/w buffer located in the .vimrc file. Allowing the same pair of\r\nkeys to perform the comment or uncomment function for different comment styles.\r\nVicom's purpose is to rapidly comment out or restore blocks of source code whilst testing and\r\ndebugging. Used with the Vimake package it turns Vim in to a powerful programmers workbench.\r\nVicom once installed runs as an alias to both Vim and Gvim. So if you normally start a Vim\r\nsession such as:\r\n        vi newprog.cc   or gvim newprog.cpp\r\nVicom first examines the command line and determines that the comment and uncomment maps should\r\nbe for a cpp program. It then writes these maps to a small buffer then passes control on to Vim\r\nto perform its normal loading of the file. Now when you press <Ctl+X> or <Ctl+Y> the correct\r\ncomments occur in your program. If you load a file type that Vicom does not recognize the keymap\r\nbuffer is cleared.\r\nVicom recognizes the following file types. Gnu gcc,g++,Nasm,AT&T(gas)as,ruby,perl,python and bash.\r\n","install_details":"copy package to your home directory\r\nrun    tar -zxvf vicom-1.05.tar.gz        (vers 1.04 had a bug in automake script)\r\ncd to .\/vicom-1.05\r\nrun  .configure\r\nrun   make install\r\nrun  vcominst.\r\n\r\nFull installation and usage instruction are in the doc directory.","5":"copy package to your home directory\r\nrun    tar -zxvf vicom-1.05.tar.gz        (vers 1.04 had a bug in automake script)\r\ncd to .\/vicom-1.05\r\nrun  .configure\r\nrun   make install\r\nrun  vcominst.\r\n\r\nFull installation and usage instruction are in the doc directory.","first_name":"michael","6":"michael","last_name":"lear","7":"lear","releases":[{"0":"3048","vim_version":"6.0","1":"6.0","script_version":"1.05","2":"1.05","version_comment":"Revised version-1.04 Bug fixed in automake script preventing xydata file being\r\nrenamed to match calling program.","3":"Revised version-1.04 Bug fixed in automake script preventing xydata file being\r\nrenamed to match calling program.","package":"vicom-1.05.tar.gz","4":"vicom-1.05.tar.gz","src_id":"12799","5":"12799","creation_date":"1270817914","6":"1270817914"},{"0":"3048","vim_version":"6.0","1":"6.0","script_version":"1.04","2":"1.04","version_comment":"Initial upload","3":"Initial upload","package":"vicom-1.04.tar.gz","4":"vicom-1.04.tar.gz","src_id":"12798","5":"12798","creation_date":"1270809470","6":"1270809470"}]},"3047":{"script_id":"3047","0":"3047","script_name":"scalacommenter.vim","1":"scalacommenter.vim","script_type":"utility","2":"utility","summary":"Functions for documenting Scala-code","3":"Functions for documenting Scala-code","description":"Re-written using the Self.vim Object prototype system, hence\r\njustifying a major version number increase\r\n(see: http:\/\/www.vim.org\/scripts\/script.php?script_id=3072).\r\nThe self.vim code is embedded in the scalacommenter.vim code\r\nso you don't need to download self.vim.\r\n\r\nInspired by Kalle Bjorklid's JCommenter.\r\nWorks on Vim version 7.0 and above\r\n\r\nThis has two capabilities: \r\n  1) Generating a comment template, and\r\n  2) Formatting an existing set of comment tags.\r\n\r\nGenerating ScalaDoc comments for Scala sources.\r\nThis is triggered by executing the ScalaCommentWriter() function\r\n  1) while the cursor is over something meaningful, or\r\n  2) if a (visual) selection exists,\r\nThe selected text is parsed and the comment template generated.\r\n\r\nThe following comments are generated (in the appropriate situations):\r\n\r\n1. File comments: user specifies the template, generated when the\r\n    cursor is on the first line of the file.\r\n2. Class comments: generated when on top of a class declaration\r\n    Tags if applicable: @author, @version, @since, @param, @tparam and @throws\r\n3. Trait comments: generated when on top of a trait declaration\r\n    Tags if applicable: @author, @version and @since\r\n4. Object comments: generated when on top of a object declaration\r\n    Tags if applicable: @author, @version and @since\r\n5. Inner Class comments: generated when on top of an inner class declaration\r\n    Tags if applicable: @param, @tparam and @throws\r\n6. Inner Trait comments: generated when on top of an inner trait declaration\r\n7. Inner Object comments: generated when on top of an inner object declaration\r\n8. Method comments: generated when on top of a method declaration.\r\n    Tags if applicable: @param, @tparam, @return and @throws\r\n9. Fields, val and var, comments: generated when on top of a var or val\r\n    declaration.\r\n\r\nIf executed and the class, trait, object or method already has a ScalaDoc\r\ncomment, an attempt is made to add\/remove parameter and template parameter\r\ntags as needed.\r\n\r\nFormatting existing ScalaDoc comments for Scala sources.\r\nThis is triggered by executing the ScalaCommentFormatter() function\r\nThe user (visual) selection of the comment tag lines to be formatted\r\nand invokes the ScalaCommentFormatter() function.\r\nAs an example, the following is selected and formatted:\r\n   * @author    Tom  Jones\r\n   * @version   1.3 03\/10\/50\r\n   * @param  name This is the name\r\n   * @param  value the value to associate with the value\r\n   *  This is a second line. Here is a second second line.\r\n   *    This is a third line. Here is a third third line.\r\n   * @throws java.io.EOFException For no reason\r\n   * @author Jane Doe\r\nbecomes:\r\n   * @author  Tom Jones\r\n   * @author  Jane Doe\r\n   * @version 1.3 03\/10\/50\r\n   * @param   name                         This is the name\r\n   * @param   value                          the value to associate with the value This\r\n   *                                                     is a second line. Here is a second second\r\n   *                                                     line. This is a third line. Here is a third\r\n   *                                                     third line.\r\n   * @throws  java.io.EOFException For no reason\r\n\r\nNote that tags are re-ordered and grouped based upon Sun's JavaDoc guide.\r\nThe start line selected to be formatted must be a comment tag line.\r\nThe end line selected to be formated should be a comment tag line\r\nor a line containing additional text for a previous tag line.\r\n\r\nWork flow:\r\n  Generate comment template,\r\n  Fill in template and then\r\n  Format the comment's tags.\r\n\r\nFor more details about what is produced and how to configure the production,\r\nsee the start of the script for additional documentation.\r\n\r\nSource can be found at: https:\/\/github.com\/megaannum\/scala_commenter\r\n\r\n","4":"Re-written using the Self.vim Object prototype system, hence\r\njustifying a major version number increase\r\n(see: http:\/\/www.vim.org\/scripts\/script.php?script_id=3072).\r\nThe self.vim code is embedded in the scalacommenter.vim code\r\nso you don't need to download self.vim.\r\n\r\nInspired by Kalle Bjorklid's JCommenter.\r\nWorks on Vim version 7.0 and above\r\n\r\nThis has two capabilities: \r\n  1) Generating a comment template, and\r\n  2) Formatting an existing set of comment tags.\r\n\r\nGenerating ScalaDoc comments for Scala sources.\r\nThis is triggered by executing the ScalaCommentWriter() function\r\n  1) while the cursor is over something meaningful, or\r\n  2) if a (visual) selection exists,\r\nThe selected text is parsed and the comment template generated.\r\n\r\nThe following comments are generated (in the appropriate situations):\r\n\r\n1. File comments: user specifies the template, generated when the\r\n    cursor is on the first line of the file.\r\n2. Class comments: generated when on top of a class declaration\r\n    Tags if applicable: @author, @version, @since, @param, @tparam and @throws\r\n3. Trait comments: generated when on top of a trait declaration\r\n    Tags if applicable: @author, @version and @since\r\n4. Object comments: generated when on top of a object declaration\r\n    Tags if applicable: @author, @version and @since\r\n5. Inner Class comments: generated when on top of an inner class declaration\r\n    Tags if applicable: @param, @tparam and @throws\r\n6. Inner Trait comments: generated when on top of an inner trait declaration\r\n7. Inner Object comments: generated when on top of an inner object declaration\r\n8. Method comments: generated when on top of a method declaration.\r\n    Tags if applicable: @param, @tparam, @return and @throws\r\n9. Fields, val and var, comments: generated when on top of a var or val\r\n    declaration.\r\n\r\nIf executed and the class, trait, object or method already has a ScalaDoc\r\ncomment, an attempt is made to add\/remove parameter and template parameter\r\ntags as needed.\r\n\r\nFormatting existing ScalaDoc comments for Scala sources.\r\nThis is triggered by executing the ScalaCommentFormatter() function\r\nThe user (visual) selection of the comment tag lines to be formatted\r\nand invokes the ScalaCommentFormatter() function.\r\nAs an example, the following is selected and formatted:\r\n   * @author    Tom  Jones\r\n   * @version   1.3 03\/10\/50\r\n   * @param  name This is the name\r\n   * @param  value the value to associate with the value\r\n   *  This is a second line. Here is a second second line.\r\n   *    This is a third line. Here is a third third line.\r\n   * @throws java.io.EOFException For no reason\r\n   * @author Jane Doe\r\nbecomes:\r\n   * @author  Tom Jones\r\n   * @author  Jane Doe\r\n   * @version 1.3 03\/10\/50\r\n   * @param   name                         This is the name\r\n   * @param   value                          the value to associate with the value This\r\n   *                                                     is a second line. Here is a second second\r\n   *                                                     line. This is a third line. Here is a third\r\n   *                                                     third line.\r\n   * @throws  java.io.EOFException For no reason\r\n\r\nNote that tags are re-ordered and grouped based upon Sun's JavaDoc guide.\r\nThe start line selected to be formatted must be a comment tag line.\r\nThe end line selected to be formated should be a comment tag line\r\nor a line containing additional text for a previous tag line.\r\n\r\nWork flow:\r\n  Generate comment template,\r\n  Fill in template and then\r\n  Format the comment's tags.\r\n\r\nFor more details about what is produced and how to configure the production,\r\nsee the start of the script for additional documentation.\r\n\r\nSource can be found at: https:\/\/github.com\/megaannum\/scala_commenter\r\n\r\n","install_details":"Add the scalacommenter.vim to your .vim directory (or whatever).\r\nHere's what I have in my .vimrc:\r\n\r\n  autocmd FileType scala source $HOME\/.vim\/scalacommenter.vim\r\n  autocmd FileType scala map <M-c> :call ScalaCommentWriter()<CR>\r\n  autocmd FileType scala map <M-f> :call ScalaCommentFormatter()<CR>\r\n  autocmd FileType scala map cm :call ScalaCommentWriter()<CR>\r\n  autocmd FileType scala map cf :call ScalaCommentFormatter()<CR>\r\n  autocmd FileType scala let b:scommenter_class_author='Richard Emberson'\r\n  autocmd FileType scala let b:scommenter_file_author='Richard Emberson'\r\n  autocmd FileType scala let g:scommenter_file_copyright_list = [\r\n  \\    'COPYRIGHT',\r\n  \\    'Second line of copyright',\r\n  \\    'And a third line'\r\n  \\]\r\n  autocmd FileType scala let b:scommenter_extra_line_text_offset = 20\r\n  autocmd FileType scala let b:scommenter_user_tags = [\r\n  \\[\"pre\", 0, 1, 0],\r\n  \\[\"post\", 0, 1, 0],\r\n  \\[\"requires\", 1, 1, 0],\r\n  \\[\"provides\", 0, 1, 0]\r\n  \\]\r\n\r\nThe user tags: \"pre\", \"post\", \"requires\" and \"provides\" appear in\r\na couple of the base Scala library code - I include them just for\r\ntesting the user-defined tags capability.\r\n\r\nNote that Alt-c and <M-c> may not work on Unix systems, hence\r\nI map in command mode \"cm\" to call the ScalaCommentWriter function.\r\n","5":"Add the scalacommenter.vim to your .vim directory (or whatever).\r\nHere's what I have in my .vimrc:\r\n\r\n  autocmd FileType scala source $HOME\/.vim\/scalacommenter.vim\r\n  autocmd FileType scala map <M-c> :call ScalaCommentWriter()<CR>\r\n  autocmd FileType scala map <M-f> :call ScalaCommentFormatter()<CR>\r\n  autocmd FileType scala map cm :call ScalaCommentWriter()<CR>\r\n  autocmd FileType scala map cf :call ScalaCommentFormatter()<CR>\r\n  autocmd FileType scala let b:scommenter_class_author='Richard Emberson'\r\n  autocmd FileType scala let b:scommenter_file_author='Richard Emberson'\r\n  autocmd FileType scala let g:scommenter_file_copyright_list = [\r\n  \\    'COPYRIGHT',\r\n  \\    'Second line of copyright',\r\n  \\    'And a third line'\r\n  \\]\r\n  autocmd FileType scala let b:scommenter_extra_line_text_offset = 20\r\n  autocmd FileType scala let b:scommenter_user_tags = [\r\n  \\[\"pre\", 0, 1, 0],\r\n  \\[\"post\", 0, 1, 0],\r\n  \\[\"requires\", 1, 1, 0],\r\n  \\[\"provides\", 0, 1, 0]\r\n  \\]\r\n\r\nThe user tags: \"pre\", \"post\", \"requires\" and \"provides\" appear in\r\na couple of the base Scala library code - I include them just for\r\ntesting the user-defined tags capability.\r\n\r\nNote that Alt-c and <M-c> may not work on Unix systems, hence\r\nI map in command mode \"cm\" to call the ScalaCommentWriter function.\r\n","first_name":"richard","6":"richard","last_name":"emberson","7":"emberson","releases":[{"0":"3047","vim_version":"7.0","1":"7.0","script_version":"3.0.3","2":"3.0.3","version_comment":"Changed version number for type to kind delta","3":"Changed version number for type to kind delta","package":"scala_commenter.zip","4":"scala_commenter.zip","src_id":"18483","5":"18483","creation_date":"1345824651","6":"1345824651"},{"0":"3047","vim_version":"7.3","1":"7.3","script_version":"3.0.2","2":"3.0.2","version_comment":"Vim 7.3 could not handle construct: call funcReturnDictionary().someFunc()","3":"Vim 7.3 could not handle construct: call funcReturnDictionary().someFunc()","package":"scala_commenter.zip","4":"scala_commenter.zip","src_id":"18346","5":"18346","creation_date":"1343667998","6":"1343667998"},{"0":"3047","vim_version":"7.0","1":"7.0","script_version":"3.0","2":"3.0","version_comment":"Support for autoloading.\r\nUses latest version of Self library","3":"Support for autoloading.\r\nUses latest version of Self library","package":"scala_commenter.zip","4":"scala_commenter.zip","src_id":"18330","5":"18330","creation_date":"1343421051","6":"1343421051"},{"0":"3047","vim_version":"7.0","1":"7.0","script_version":"2.2","2":"2.2","version_comment":"Minor correction: could not handle parameters with templates with commas: \r\n  def getAtomicVars(atomicMethods: List[XMethodInfo], methods: HashMap[global.Symbol, XMethodInfo], vars: HashMap[global.Symbol, XVarInfo]) : List[XVarInfo] = {\r\n  }\r\n","3":"Minor correction: could not handle parameters with templates with commas: \r\n  def getAtomicVars(atomicMethods: List[XMethodInfo], methods: HashMap[global.Symbol, XMethodInfo], vars: HashMap[global.Symbol, XVarInfo]) : List[XVarInfo] = {\r\n  }\r\n","package":"scalacommenter.vim","4":"scalacommenter.vim","src_id":"12986","5":"12986","creation_date":"1273531741","6":"1273531741"},{"0":"3047","vim_version":"7.0","1":"7.0","script_version":"2.1","2":"2.1","version_comment":"Very minor: Method recognition failed for the List methods: '::', ':::' and 'reverse_:::'.\r\n","3":"Very minor: Method recognition failed for the List methods: '::', ':::' and 'reverse_:::'.\r\n","package":"scalacommenter.vim","4":"scalacommenter.vim","src_id":"12896","5":"12896","creation_date":"1272134455","6":"1272134455"},{"0":"3047","vim_version":"7.0","1":"7.0","script_version":"2.0","2":"2.0","version_comment":"Refactored comment generation code using Self.vim, the Vim\r\n  dictionary-base object prototype system. Unified the code that\r\n  generated output for both the writing and re-formatting of\r\n  comments.\r\nThrow tags are now sorted in alphabetical order\r\nUnified the comment writing code so that comment formatting,\r\n  first comment generation, and subsequent generation all\r\n  use the came code.\r\nText associated with an existing comment tag is no longer lost.\r\nAdd b:scommenter_top_level_tparams_only which controls if all\r\n  template parameters have @tparam tags generated or only those\r\n  at the top-level have tags generated.\r\nFixed scanning parameters, now scans past qualifiers like 'val',\r\nSupports curried notations func(a: A)(b: B). \r\n'var' or 'private var', etc.\r\nAdded b:scommenter_extra_line_text_offset allowing the user to control\r\n  the offset of any additional text associated with a tag.\r\nThere is now a b:scommenter_user_tags configuration variable allowing\r\n  the user to register in their .vimrc file third-party tags.\r\nAdded b:scommenter_warning_message_enable which controls the printing\r\n  of warning messages (if any)\r\nAdded b:scommenter_line_between_user_unknown_and_std_tags which \r\n  controls if a single comment line is printed between the \r\n  user\/unknown tags and the standard tags. \r\nAdded b:scommenter_user_unknown_before_std_tags which controls the\r\n  order of formatting of the user\/unknown tags and the standard tags.\r\nAdded b:scommenter_warn_deleted_tags which allows the user to\r\n  save the text from tags deleted during re-formatting.\r\nSupports capturing parameter template @specialized information\r\n  in comments.\r\nThe @deprecated(text) annotation now becomes a ScalaDoc @deprecated\r\n   tag (just as the @throws annotation does).\r\n","3":"Refactored comment generation code using Self.vim, the Vim\r\n  dictionary-base object prototype system. Unified the code that\r\n  generated output for both the writing and re-formatting of\r\n  comments.\r\nThrow tags are now sorted in alphabetical order\r\nUnified the comment writing code so that comment formatting,\r\n  first comment generation, and subsequent generation all\r\n  use the came code.\r\nText associated with an existing comment tag is no longer lost.\r\nAdd b:scommenter_top_level_tparams_only which controls if all\r\n  template parameters have @tparam tags generated or only those\r\n  at the top-level have tags generated.\r\nFixed scanning parameters, now scans past qualifiers like 'val',\r\nSupports curried notations func(a: A)(b: B). \r\n'var' or 'private var', etc.\r\nAdded b:scommenter_extra_line_text_offset allowing the user to control\r\n  the offset of any additional text associated with a tag.\r\nThere is now a b:scommenter_user_tags configuration variable allowing\r\n  the user to register in their .vimrc file third-party tags.\r\nAdded b:scommenter_warning_message_enable which controls the printing\r\n  of warning messages (if any)\r\nAdded b:scommenter_line_between_user_unknown_and_std_tags which \r\n  controls if a single comment line is printed between the \r\n  user\/unknown tags and the standard tags. \r\nAdded b:scommenter_user_unknown_before_std_tags which controls the\r\n  order of formatting of the user\/unknown tags and the standard tags.\r\nAdded b:scommenter_warn_deleted_tags which allows the user to\r\n  save the text from tags deleted during re-formatting.\r\nSupports capturing parameter template @specialized information\r\n  in comments.\r\nThe @deprecated(text) annotation now becomes a ScalaDoc @deprecated\r\n   tag (just as the @throws annotation does).\r\n","package":"scalacommenter.vim","4":"scalacommenter.vim","src_id":"12887","5":"12887","creation_date":"1271905265","6":"1271905265"},{"0":"3047","vim_version":"7.2","1":"7.2","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"scalacommenter.vim","4":"scalacommenter.vim","src_id":"12797","5":"12797","creation_date":"1270775932","6":"1270775932"}]},"3046":{"script_id":"3046","0":"3046","script_name":"operator-camelize","1":"operator-camelize","script_type":"utility","2":"utility","summary":"snake_case -> SnakeCase, CamelCase -> camel_case","3":"snake_case -> SnakeCase, CamelCase -> camel_case","description":"*operator-camelize* is a Vim plugin to provide an operator\r\nto camelize\/decamelize a specified text.\r\n\r\nRequirements:\r\n- |operator-user| (vimscript#2692)\r\n\r\nRepository:\r\nhttp:\/\/github.com\/tyru\/operator-camelize.vim","4":"*operator-camelize* is a Vim plugin to provide an operator\r\nto camelize\/decamelize a specified text.\r\n\r\nRequirements:\r\n- |operator-user| (vimscript#2692)\r\n\r\nRepository:\r\nhttp:\/\/github.com\/tyru\/operator-camelize.vim","install_details":"...","5":"...","first_name":"tyru","6":"tyru","last_name":" ","7":" ","releases":[{"0":"3046","vim_version":"7.0","1":"7.0","script_version":"0.0.5a","2":"0.0.5a","version_comment":"0.0.5:\r\n- Add <Plug>(operator-camelize-toggle)\r\n\r\n0.0.5a:\r\n- Fix problem that it evaluates lower camelcase as snakecase. (e.g., camelCase).","3":"0.0.5:\r\n- Add <Plug>(operator-camelize-toggle)\r\n\r\n0.0.5a:\r\n- Fix problem that it evaluates lower camelcase as snakecase. (e.g., camelCase).","package":"operator-camelize.zip","4":"operator-camelize.zip","src_id":"16023","5":"16023","creation_date":"1309664454","6":"1309664454"},{"0":"3046","vim_version":"7.0","1":"7.0","script_version":"0.0.4","2":"0.0.4","version_comment":"- Fix doc: operator-replace => operator-camelize (thanks thinca for reporting)\r\n- Support camelCase. not only PascalCase. (thanks thinca for reporting)\r\n- Add operator#camelize#load().","3":"- Fix doc: operator-replace => operator-camelize (thanks thinca for reporting)\r\n- Support camelCase. not only PascalCase. (thanks thinca for reporting)\r\n- Add operator#camelize#load().","package":"operator-camelize.zip","4":"operator-camelize.zip","src_id":"15458","5":"15458","creation_date":"1302971353","6":"1302971353"},{"0":"3046","vim_version":"7.0","1":"7.0","script_version":"0.0.3","2":"0.0.3","version_comment":"- Fix bug: When selected in blockwise visual mode,\r\n  unnecessary newline is inserted at the bottom.\r\n- Fix bug: If there are two more than words in selected range,\r\n  head character is not camelized.\r\n- A lot of internal changes.","3":"- Fix bug: When selected in blockwise visual mode,\r\n  unnecessary newline is inserted at the bottom.\r\n- Fix bug: If there are two more than words in selected range,\r\n  head character is not camelized.\r\n- A lot of internal changes.","package":"operator-camelize.zip","4":"operator-camelize.zip","src_id":"14153","5":"14153","creation_date":"1288518359","6":"1288518359"},{"0":"3046","vim_version":"7.0","1":"7.0","script_version":"0.0.2","2":"0.0.2","version_comment":"- Implement g:operator_camelize_all_uppercase_action.\r\n- Fix document descriptions.","3":"- Implement g:operator_camelize_all_uppercase_action.\r\n- Fix document descriptions.","package":"operator-camelize.zip","4":"operator-camelize.zip","src_id":"13806","5":"13806","creation_date":"1284199792","6":"1284199792"},{"0":"3046","vim_version":"7.0","1":"7.0","script_version":"0.0.1","2":"0.0.1","version_comment":"Refactoring.","3":"Refactoring.","package":"operator-camelize.zip","4":"operator-camelize.zip","src_id":"13296","5":"13296","creation_date":"1278376745","6":"1278376745"},{"0":"3046","vim_version":"7.0","1":"7.0","script_version":"0.0.0","2":"0.0.0","version_comment":"Initial upload","3":"Initial upload","package":"operator-camelize.zip","4":"operator-camelize.zip","src_id":"12793","5":"12793","creation_date":"1270639157","6":"1270639157"}]},"3045":{"script_id":"3045","0":"3045","script_name":"cmakeref","1":"cmakeref","script_type":"utility","2":"utility","summary":"CMake reference in vimhelp format with a python script to regenerate it","3":"CMake reference in vimhelp format with a python script to regenerate it","description":"CMake reference in vimhelp format with a python script to regenerate it.\r\n\r\nReference for CMake 2.8.0 included.","4":"CMake reference in vimhelp format with a python script to regenerate it.\r\n\r\nReference for CMake 2.8.0 included.","install_details":"ATM: Copy to ~\/.vim\/doc, open one of the copied help files and do:\r\n   :helptags %:p:h\r\n(vim will report errors about duplicates in the tags)\r\n\r\nSee also:\r\n   :help add-local-help","5":"ATM: Copy to ~\/.vim\/doc, open one of the copied help files and do:\r\n   :helptags %:p:h\r\n(vim will report errors about duplicates in the tags)\r\n\r\nSee also:\r\n   :help add-local-help","first_name":"Marko","6":"Marko","last_name":"Mahni\u010d","7":"Mahnič","releases":[{"0":"3045","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"* added cmake policies\r\n* cross-referenced","3":"* added cmake policies\r\n* cross-referenced","package":"cmakeref.zip","4":"cmakeref.zip","src_id":"12801","5":"12801","creation_date":"1270830035","6":"1270830035"},{"0":"3045","vim_version":"6.0","1":"6.0","script_version":"0.5","2":"0.5","version_comment":"Initial upload","3":"Initial upload","package":"cmakeref.zip","4":"cmakeref.zip","src_id":"12791","5":"12791","creation_date":"1270584180","6":"1270584180"}]},"3044":{"script_id":"3044","0":"3044","script_name":"compiler\/python.vim","1":"compiler\/python.vim","script_type":"ftplugin","2":"ftplugin","summary":"improved python compiler script","3":"improved python compiler script","description":"Based on the script and notation from vimscript #1439. This has been updated for the newer format of py_compile.\r\n\r\nFrom the original description:\r\n\"This compiler script does not run the source through the python interpreter, but instead uses the py_compile package to check for syntax errors.  This allows for a development cycle similar to a compiled language - edit, compile, run.\"\r\n ","4":"Based on the script and notation from vimscript #1439. This has been updated for the newer format of py_compile.\r\n\r\nFrom the original description:\r\n\"This compiler script does not run the source through the python interpreter, but instead uses the py_compile package to check for syntax errors.  This allows for a development cycle similar to a compiled language - edit, compile, run.\"\r\n ","install_details":"Copy the file to $VIMRUNTIME\/compiler\/ or ~\/.vim\/compiler\/","5":"Copy the file to $VIMRUNTIME\/compiler\/ or ~\/.vim\/compiler\/","first_name":"Mikhail","6":"Mikhail","last_name":"Wolfson","7":"Wolfson","releases":[{"0":"3044","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"python.vim","4":"python.vim","src_id":"12788","5":"12788","creation_date":"1270500619","6":"1270500619"}]},"3043":{"script_id":"3043","0":"3043","script_name":"clevercss.vim","1":"clevercss.vim","script_type":"syntax","2":"syntax","summary":"syntax highlighting for CleverCSS","3":"syntax highlighting for CleverCSS","description":"Rudimentary syntax highlighting for CleverCSS (http:\/\/sandbox.pocoo.org\/clevercss\/).","4":"Rudimentary syntax highlighting for CleverCSS (http:\/\/sandbox.pocoo.org\/clevercss\/).","install_details":"","5":"","first_name":"Zak","6":"Zak","last_name":"Johnson","7":"Johnson","releases":[{"0":"3043","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Update CSS property list, courtesy of Michał Sałaban","3":"Update CSS property list, courtesy of Michał Sałaban","package":"clevercss.vim","4":"clevercss.vim","src_id":"19377","5":"19377","creation_date":"1358276297","6":"1358276297"},{"0":"3043","vim_version":"6.0","1":"6.0","script_version":"0.9","2":"0.9","version_comment":"Initial upload","3":"Initial upload","package":"clevercss.vim","4":"clevercss.vim","src_id":"12785","5":"12785","creation_date":"1270447780","6":"1270447780"}]},"3042":{"script_id":"3042","0":"3042","script_name":"css3","1":"css3","script_type":"syntax","2":"syntax","summary":"css3 syntax for vim","3":"css3 syntax for vim","description":"It's really weird that vim doesn't support css3. \r\nI am just new to vim, and this is the very first script for vim I've written.\r\nTake your decision.","4":"It's really weird that vim doesn't support css3. \r\nI am just new to vim, and this is the very first script for vim I've written.\r\nTake your decision.","install_details":"Install with Vundle\r\n\r\nIf you are not using vundle, you really should have a try. Edit your vimrc:\r\n\r\nBundle \"lepture\/vim-css\"\r\nAnd install it:\r\n\r\n:so ~\/.vimrc\r\n:BundleInstall\r\n\r\n\r\n\r\nInstall with pathogen\r\n\r\nIf you prefer tpope's pathogen, that's ok. Just clone it:\r\n\r\ncd ~\/.vim\/bundle\r\ngit clone https:\/\/github.com\/lepture\/vim-css.git","5":"Install with Vundle\r\n\r\nIf you are not using vundle, you really should have a try. Edit your vimrc:\r\n\r\nBundle \"lepture\/vim-css\"\r\nAnd install it:\r\n\r\n:so ~\/.vimrc\r\n:BundleInstall\r\n\r\n\r\n\r\nInstall with pathogen\r\n\r\nIf you prefer tpope's pathogen, that's ok. Just clone it:\r\n\r\ncd ~\/.vim\/bundle\r\ngit clone https:\/\/github.com\/lepture\/vim-css.git","first_name":"Hsiaoming","6":"Hsiaoming","last_name":"Yang","7":"Yang","releases":[{"0":"3042","vim_version":"7.0","1":"7.0","script_version":"2.1","2":"2.1","version_comment":"add more syntax support","3":"add more syntax support","package":"vim-css.zip","4":"vim-css.zip","src_id":"18546","5":"18546","creation_date":"1346759333","6":"1346759333"},{"0":"3042","vim_version":"7.0","1":"7.0","script_version":"2.0","2":"2.0","version_comment":"This is a big change. Support Vundle and Pathogen now.","3":"This is a big change. Support Vundle and Pathogen now.","package":"vim-css.zip","4":"vim-css.zip","src_id":"18545","5":"18545","creation_date":"1346757571","6":"1346757571"},{"0":"3042","vim_version":"7.0","1":"7.0","script_version":"1.2","2":"1.2","version_comment":"add html tag syntax support","3":"add html tag syntax support","package":"css3.vim","4":"css3.vim","src_id":"15153","5":"15153","creation_date":"1299164220","6":"1299164220"},{"0":"3042","vim_version":"7.0","1":"7.0","script_version":"1.1","2":"1.1","version_comment":"add more keyword","3":"add more keyword","package":"css3.vim","4":"css3.vim","src_id":"15047","5":"15047","creation_date":"1298129979","6":"1298129979"},{"0":"3042","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"css3.vim","4":"css3.vim","src_id":"12784","5":"12784","creation_date":"1270446781","6":"1270446781"}]},"3041":{"script_id":"3041","0":"3041","script_name":"RST Tables","1":"RST Tables","script_type":"utility","2":"utility","summary":"Allows to create and edit restructuredText tables easily","3":"Allows to create and edit restructuredText tables easily","description":"This plugin allows to create and edit restructuredText tables easily.\r\n\r\nIts adds two new commands:\r\n\r\n    ,,c  ->  Creates a new restructuredText table.\r\n    ,,f  ->  Fix table columns in a table.\r\n\r\nFor example, if you have a paragraph with data like this:\r\n\r\n    nombre      apellido    edad\r\n    pepe        zarate      28\r\n    toto        garcia      29\r\n\r\nyou can press \",,c\" to create a simple table:\r\n\r\n    +--------+----------+------+\r\n    | nombre | apellido | edad |\r\n    +========+==========+======+\r\n    | pepe   | zarate   | 28   |\r\n    +--------+----------+------+\r\n    | toto   | garcia   | 29   |\r\n    +--------+----------+------+\r\n\r\n\r\nNow, if you change the table content, for example adding characters\r\nto the first content row.\r\n\r\n    +--------+----------+------+\r\n    | nombre | apellido | edad |\r\n    +========+==========+======+\r\n    | Un nombre muy largo que rompe la tabla   | zarate   | 28   |\r\n    +--------+----------+------+\r\n    | toto   | un appellido largo...   | 29   |\r\n    +--------+----------+------+\r\n\r\nyou need to fix the columns widths. So, press \",,f\" and you will gets:\r\n\r\n    +----------------------------------------+-----------------------+------+\r\n    | nombre                                 | apellido              | edad |\r\n    +========================================+=======================+======+\r\n    | Un nombre muy largo que rompe la tabla | zarate                | 28   |\r\n    +----------------------------------------+-----------------------+------+\r\n    | toto                                   | un appellido largo... | 29   |\r\n    +----------------------------------------+-----------------------+------+\r\n","4":"This plugin allows to create and edit restructuredText tables easily.\r\n\r\nIts adds two new commands:\r\n\r\n    ,,c  ->  Creates a new restructuredText table.\r\n    ,,f  ->  Fix table columns in a table.\r\n\r\nFor example, if you have a paragraph with data like this:\r\n\r\n    nombre      apellido    edad\r\n    pepe        zarate      28\r\n    toto        garcia      29\r\n\r\nyou can press \",,c\" to create a simple table:\r\n\r\n    +--------+----------+------+\r\n    | nombre | apellido | edad |\r\n    +========+==========+======+\r\n    | pepe   | zarate   | 28   |\r\n    +--------+----------+------+\r\n    | toto   | garcia   | 29   |\r\n    +--------+----------+------+\r\n\r\n\r\nNow, if you change the table content, for example adding characters\r\nto the first content row.\r\n\r\n    +--------+----------+------+\r\n    | nombre | apellido | edad |\r\n    +========+==========+======+\r\n    | Un nombre muy largo que rompe la tabla   | zarate   | 28   |\r\n    +--------+----------+------+\r\n    | toto   | un appellido largo...   | 29   |\r\n    +--------+----------+------+\r\n\r\nyou need to fix the columns widths. So, press \",,f\" and you will gets:\r\n\r\n    +----------------------------------------+-----------------------+------+\r\n    | nombre                                 | apellido              | edad |\r\n    +========================================+=======================+======+\r\n    | Un nombre muy largo que rompe la tabla | zarate                | 28   |\r\n    +----------------------------------------+-----------------------+------+\r\n    | toto                                   | un appellido largo... | 29   |\r\n    +----------------------------------------+-----------------------+------+\r\n","install_details":"Install the python extension to vim and then copy the file `rst_table.vim`\r\nto the `.vim\/plugin` directory in your home directory.\r\n","5":"Install the python extension to vim and then copy the file `rst_table.vim`\r\nto the `.vim\/plugin` directory in your home directory.\r\n","first_name":"Hugo","6":"Hugo","last_name":"Ruscitti","7":"Ruscitti","releases":[{"0":"3041","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"rst_table.vim","4":"rst_table.vim","src_id":"12783","5":"12783","creation_date":"1270410979","6":"1270410979"}]},"3040":{"script_id":"3040","0":"3040","script_name":"cmd.vim","1":"cmd.vim","script_type":"utility","2":"utility","summary":"Execute shell(or Windows cmd) command in Vim and echo output in Vim","3":"Execute shell(or Windows cmd) command in Vim and echo output in Vim","description":"\r\nCmd.vim is a vim plugin to provide vim the ability to execute shell command\r\ndirectly in vim and echo the result in vim. For example, you could use \":!ls\"\r\nto list all the files of current directory, Now cmd.vim provide a new command\r\n\":Ls\" to implement the same function, but the result is in vim insteading of in\r\nthe shell. The mainpage in Chinese is avaiable at:\r\n\r\nhttp:\/\/code.google.com\/p\/cmd-dot-vim\/\r\n\r\nThere are many well known shell command to implement powerful functions, now I\r\nport them to vim version, In the current release, there are four command\r\navailable now, More are to be added. For those not listed below, you could use\r\n\":Shell your_command\" to execute your_command like \"! your_command\", with the\r\nresult in Vim insteading of Shell.\r\n\r\n\t\":Date\" - print or set the system date and time\r\n\t\":Gcc\" - gcc - GNU project C and C++ compiler\r\n\t\":Ls\" - list directory contents\r\n\t\":Sdcv Words\" - call sdcv to lookup Words in vim\r\n\r\n[Note]: Please note that since Vim claim user defined commands must start with an\r\nuppercase letter, so every shell command start with an uppercase letter.\r\n\r\n[Note]: Please note that cmd.vim is an adapter, So please make sure the original\r\ncommand is available. it is expected that cmd.vim works where the original\r\ncommand works, whatever it's Linux, Cygwin, Windows, or Mac. \r\n\r\n[Note]: In most circumstances, it will be better if you map them to your\r\nfavorite map, For example, To look up the a word under the cursor, or to lookup\r\nthe words selected:\r\n\r\n\tnmap <script> <silent> <unique> <Leader>l <ESC>:Sdcv '<cword>' <CR>\r\n\tvmap <script> <silent> <unique> <Leader>l y<ESC>:Sdcv <c-r>\" <CR>","4":"\r\nCmd.vim is a vim plugin to provide vim the ability to execute shell command\r\ndirectly in vim and echo the result in vim. For example, you could use \":!ls\"\r\nto list all the files of current directory, Now cmd.vim provide a new command\r\n\":Ls\" to implement the same function, but the result is in vim insteading of in\r\nthe shell. The mainpage in Chinese is avaiable at:\r\n\r\nhttp:\/\/code.google.com\/p\/cmd-dot-vim\/\r\n\r\nThere are many well known shell command to implement powerful functions, now I\r\nport them to vim version, In the current release, there are four command\r\navailable now, More are to be added. For those not listed below, you could use\r\n\":Shell your_command\" to execute your_command like \"! your_command\", with the\r\nresult in Vim insteading of Shell.\r\n\r\n\t\":Date\" - print or set the system date and time\r\n\t\":Gcc\" - gcc - GNU project C and C++ compiler\r\n\t\":Ls\" - list directory contents\r\n\t\":Sdcv Words\" - call sdcv to lookup Words in vim\r\n\r\n[Note]: Please note that since Vim claim user defined commands must start with an\r\nuppercase letter, so every shell command start with an uppercase letter.\r\n\r\n[Note]: Please note that cmd.vim is an adapter, So please make sure the original\r\ncommand is available. it is expected that cmd.vim works where the original\r\ncommand works, whatever it's Linux, Cygwin, Windows, or Mac. \r\n\r\n[Note]: In most circumstances, it will be better if you map them to your\r\nfavorite map, For example, To look up the a word under the cursor, or to lookup\r\nthe words selected:\r\n\r\n\tnmap <script> <silent> <unique> <Leader>l <ESC>:Sdcv '<cword>' <CR>\r\n\tvmap <script> <silent> <unique> <Leader>l y<ESC>:Sdcv <c-r>\" <CR>","install_details":"\r\nPut the cmd.vim to your $HOME\/.vim\/plugin or the $HOME\/vimfiles\/plugin or\r\nthe $VIM\/vimfiles\/plugin.","5":"\r\nPut the cmd.vim to your $HOME\/.vim\/plugin or the $HOME\/vimfiles\/plugin or\r\nthe $VIM\/vimfiles\/plugin.","first_name":"yp","6":"yp","last_name":"guo","7":"guo","releases":[{"0":"3040","vim_version":"6.0","1":"6.0","script_version":"1.0.3","2":"1.0.3","version_comment":"Feature improvement:\r\nAdd a parameter '\\t' for Date command in Windows. Without that \":Date\" will be interactive.","3":"Feature improvement:\r\nAdd a parameter '\\t' for Date command in Windows. Without that \":Date\" will be interactive.","package":"cmd.vim","4":"cmd.vim","src_id":"12854","5":"12854","creation_date":"1271470273","6":"1271470273"},{"0":"3040","vim_version":"6.0","1":"6.0","script_version":"1.0.2","2":"1.0.2","version_comment":"New feature: For every command, you could use \":Shell command\" to get the same result as \":Command\". So For command not listed, cmd.vim also works. ","3":"New feature: For every command, you could use \":Shell command\" to get the same result as \":Command\". So For command not listed, cmd.vim also works. ","package":"cmd.vim","4":"cmd.vim","src_id":"12781","5":"12781","creation_date":"1270359550","6":"1270359550"},{"0":"3040","vim_version":"6.0","1":"6.0","script_version":"1.0.1","2":"1.0.1","version_comment":"1. Infrastructure changed for simplicity.\r\n2. Add a new command \":Gcc\" - compile this file using gcc.","3":"1. Infrastructure changed for simplicity.\r\n2. Add a new command \":Gcc\" - compile this file using gcc.","package":"cmd.vim","4":"cmd.vim","src_id":"12774","5":"12774","creation_date":"1270259184","6":"1270259184"},{"0":"3040","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"cmd.vim","4":"cmd.vim","src_id":"12768","5":"12768","creation_date":"1270214029","6":"1270214029"}]},"3039":{"script_id":"3039","0":"3039","script_name":"vimgdb","1":"vimgdb","script_type":"utility","2":"utility","summary":"Emacs like gdb interface to cterm vim","3":"Emacs like gdb interface to cterm vim","description":"This script provides an emacs like GDB interface to vim. Woks in cygwin and unix terminals (no need for +clientserver).\r\n\r\nFind the screen shots at \"Vim Viki\"\r\n\r\nStart the program like this\r\n\r\nvimgdb <gdb-params> <exe-file> <exe-params>\r\n\r\nThis will open vim with two windows. Type the gdb commands in bottom window. The top window will show the current file line and breakpoints highlighted.\r\n\r\nYou can also jump to top window and use the following keys\r\n<F6> run\r\n<F5> continue\r\n<F7> step into\r\n<F8> step over\r\n<F9> toggle break point\r\nCtr-p Watch the variable under Cursor\/Visual selection\r\n\r\nwatch the output\/variables in bottom window.\r\n\r\nKnown Bugs:\r\nDon't use the quit gdb command (that will hang the vim), instead quit the vim.\r\n\r\nCredits:\r\nThis script is preliminarily based on Tomas Zellerin's gdbvim","4":"This script provides an emacs like GDB interface to vim. Woks in cygwin and unix terminals (no need for +clientserver).\r\n\r\nFind the screen shots at \"Vim Viki\"\r\n\r\nStart the program like this\r\n\r\nvimgdb <gdb-params> <exe-file> <exe-params>\r\n\r\nThis will open vim with two windows. Type the gdb commands in bottom window. The top window will show the current file line and breakpoints highlighted.\r\n\r\nYou can also jump to top window and use the following keys\r\n<F6> run\r\n<F5> continue\r\n<F7> step into\r\n<F8> step over\r\n<F9> toggle break point\r\nCtr-p Watch the variable under Cursor\/Visual selection\r\n\r\nwatch the output\/variables in bottom window.\r\n\r\nKnown Bugs:\r\nDon't use the quit gdb command (that will hang the vim), instead quit the vim.\r\n\r\nCredits:\r\nThis script is preliminarily based on Tomas Zellerin's gdbvim","install_details":"copy the vimgdb, vimgdb_msg to any directory in the system path\r\n\r\ncopy the vimgdb.vim to ~\/.vim\/misc directory\r\n\r\nNeeds perl & gdb\r\n","5":"copy the vimgdb, vimgdb_msg to any directory in the system path\r\n\r\ncopy the vimgdb.vim to ~\/.vim\/misc directory\r\n\r\nNeeds perl & gdb\r\n","first_name":"Sureshkumar","6":"Sureshkumar","last_name":"Manimuthu","7":"Manimuthu","releases":[{"0":"3039","vim_version":"6.0","1":"6.0","script_version":"1.2","2":"1.2","version_comment":"Hard coded path for vimgdb_msg removed.\r\n","3":"Hard coded path for vimgdb_msg removed.\r\n","package":"vimgdb.tar.gz","4":"vimgdb.tar.gz","src_id":"13526","5":"13526","creation_date":"1281329036","6":"1281329036"},{"0":"3039","vim_version":"6.0","1":"6.0","script_version":"1.1","2":"1.1","version_comment":"Previews version did not work on some systems.\r\nThis uses sockets for communication instead of pipes.","3":"Previews version did not work on some systems.\r\nThis uses sockets for communication instead of pipes.","package":"vimgdb.zip","4":"vimgdb.zip","src_id":"13500","5":"13500","creation_date":"1281086854","6":"1281086854"},{"0":"3039","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"vimgdb.gz","4":"vimgdb.gz","src_id":"12765","5":"12765","creation_date":"1270189509","6":"1270189509"}]},"3038":{"script_id":"3038","0":"3038","script_name":"noweb.vim","1":"noweb.vim","script_type":"syntax","2":"syntax","summary":"A syntax file for noweb, with separate highlighting for documentation and code","3":"A syntax file for noweb, with separate highlighting for documentation and code","description":"This is a simple syntax for noweb. Basically, it is a nice way to view code and documentation with separate syntax highlighting. Also, it can autofold code blocks.\r\n\r\nThe script uses the following options:\r\n\r\nnoweb_backend\r\nnoweb_language\r\nnoweb_fold_code\r\n\r\nSet noweb_backend to the basename of the syntax file you want to use, minus the \\\".vim\\\" extension. So, for TeX, you would:\r\n\r\nlet noweb_backend = \\\"tex\\\"\r\n\r\nnoweb_language is similar, but is used to highlight the contents of code blocks. So, for example:\r\n\r\nlet noweb_language = \\\"cpp\\\"\r\n\r\nMakes the syntax for code snippets = C++.\r\n\r\nFinally, there is noweb_fold_code, which sets whether or not code blocks should be automatically folded. If 1, then they will be folded. Otherwise, not.","4":"This is a simple syntax for noweb. Basically, it is a nice way to view code and documentation with separate syntax highlighting. Also, it can autofold code blocks.\r\n\r\nThe script uses the following options:\r\n\r\nnoweb_backend\r\nnoweb_language\r\nnoweb_fold_code\r\n\r\nSet noweb_backend to the basename of the syntax file you want to use, minus the \\\".vim\\\" extension. So, for TeX, you would:\r\n\r\nlet noweb_backend = \\\"tex\\\"\r\n\r\nnoweb_language is similar, but is used to highlight the contents of code blocks. So, for example:\r\n\r\nlet noweb_language = \\\"cpp\\\"\r\n\r\nMakes the syntax for code snippets = C++.\r\n\r\nFinally, there is noweb_fold_code, which sets whether or not code blocks should be automatically folded. If 1, then they will be folded. Otherwise, not.","install_details":"Just copy the script to your ~\/.vim\/syntax directory.\r\n\r\nOptionally, add something like this to your ~\/.vimrc:\r\n\r\nfiletype on\r\nfiletype plugin on\r\n\r\nau BufRead,BufNewFile *.nw    set filetype=noweb\r\n\r\nlet noweb_backend = \\\"tex\\\"\r\nlet noweb_language = \\\"cpp\\\"\r\nlet noweb_fold_code = 1\r\n\r\nThis will set the script to run for .nw files, assuming a documentation backend of TeX, a code language of C++, and turns on automatic code chunk folding.","5":"Just copy the script to your ~\/.vim\/syntax directory.\r\n\r\nOptionally, add something like this to your ~\/.vimrc:\r\n\r\nfiletype on\r\nfiletype plugin on\r\n\r\nau BufRead,BufNewFile *.nw    set filetype=noweb\r\n\r\nlet noweb_backend = \\\"tex\\\"\r\nlet noweb_language = \\\"cpp\\\"\r\nlet noweb_fold_code = 1\r\n\r\nThis will set the script to run for .nw files, assuming a documentation backend of TeX, a code language of C++, and turns on automatic code chunk folding.","first_name":"Michael","6":"Michael","last_name":"McDermott","7":"McDermott","releases":[{"0":"3038","vim_version":"7.0","1":"7.0","script_version":"0.2","2":"0.2","version_comment":"Added a patch from Matt Edlefsen fixing a syntax highlighting idiosyncrasy.","3":"Added a patch from Matt Edlefsen fixing a syntax highlighting idiosyncrasy.","package":"noweb.vim","4":"noweb.vim","src_id":"13268","5":"13268","creation_date":"1277905598","6":"1277905598"},{"0":"3038","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"noweb.vim","4":"noweb.vim","src_id":"12761","5":"12761","creation_date":"1270137396","6":"1270137396"}]},"3037":{"script_id":"3037","0":"3037","script_name":"vim-indent-object","1":"vim-indent-object","script_type":"utility","2":"utility","summary":"Text Objects based on Indentation Level","3":"Text Objects based on Indentation Level","description":"Vim text objects provide a convenient way to select and operate on various\r\ntypes of objects. These objects include regions surrounded by various types of\r\nbrackets and various parts of language (ie sentences, paragraphs, etc).\r\n\r\nThis plugin defines a new text object, based on indentation levels. This is\r\nvery useful in languages such as Python, in which the syntax defines scope in\r\nterms of indentation. Using the objects defined in this plugin, an entire if\r\nstructure can be quickly selected, for example.\r\n\r\nProject Repository:\r\nhttp:\/\/github.com\/michaeljsmith\/vim-indent-object\r\n\r\nFeedback\/criticism is welcome:\r\nmsmith@msmith.id.au\r\nhttp:\/\/msmith.id.au\r\n\r\nThis plugin defines two new text objects. These are very similar - they differ\r\nonly in whether they include the line below the block or not.\r\n\r\n        Key Mapping       Description\r\n\r\n        <count>ai         (A)n (I)ndentation level and line above.\r\n        <count>ii         (I)nner (I)ndentation level (no line above).\r\n        <count>aI         (A)n (I)ndentation level and lines above\/below.\r\n        <count>iI         (I)nner (I)ndentation level (no lines above\/below).\r\n\r\n\r\nNote that the iI mapping is mostly included simply for completeness, it is\r\neffectively a synonym for ii.\r\n\r\nJust like regular text objects, these mappings can be used either with\r\noperators expecting a motion, such as 'd' or 'c', as well as in visual mode.\r\nIn visual mode the mapping can be repeated, which has the effect of\r\niteratively increasing the scope of indentation block selected. Specifying a\r\ncount can be used to achieve the same effect.\r\n\r\nThe difference between |ai| and |aI| is that |ai| includes the line\r\nimmediately above the indentation block, whereas aI includes not only that,\r\nbut also the line below. Which of these is most useful largely depends on the\r\nstructure of the language being edited.\r\n\r\nFor example, when editing the Python code, |ai| is generally more useful, as\r\nthe line above the indentation block is usually related to it. For example, in\r\nthe following code (* is used to indicate the cursor position):\r\n\r\n      if foo > 3:\r\n         log(\"foo is big\") *\r\n         foo = 3\r\n      do_something_else()\r\n\r\nthe if clause is logically related to the code block, whereas the function\r\ncall below is not. It is unlikely we would want to select the line below when\r\nwe are interested in the if block.\r\n\r\nHowever, in other languages, such as Vim scripts, control structures are\r\nusually terminated with something like 'endif'. Therefore, in this example:\r\n\r\n      if foo > 3\r\n         echo \"foo is big\" *\r\n         let foo = 3\r\n      endif\r\n      call do_something_else()\r\n\r\nwe would more likely want to include the endif when we select the if\r\nstructure.\r\n\r\nWhen scanning code blocks, the plugin usually ignores blank lines. There is an\r\nexception to this, however, when the block being selected is not indented. In\r\nthis case if blank lines are ignored, then the entire file would be selected.\r\nInstead when code at the top level is being indented blank lines are\r\nconsidered to delimit the block.\r\n","4":"Vim text objects provide a convenient way to select and operate on various\r\ntypes of objects. These objects include regions surrounded by various types of\r\nbrackets and various parts of language (ie sentences, paragraphs, etc).\r\n\r\nThis plugin defines a new text object, based on indentation levels. This is\r\nvery useful in languages such as Python, in which the syntax defines scope in\r\nterms of indentation. Using the objects defined in this plugin, an entire if\r\nstructure can be quickly selected, for example.\r\n\r\nProject Repository:\r\nhttp:\/\/github.com\/michaeljsmith\/vim-indent-object\r\n\r\nFeedback\/criticism is welcome:\r\nmsmith@msmith.id.au\r\nhttp:\/\/msmith.id.au\r\n\r\nThis plugin defines two new text objects. These are very similar - they differ\r\nonly in whether they include the line below the block or not.\r\n\r\n        Key Mapping       Description\r\n\r\n        <count>ai         (A)n (I)ndentation level and line above.\r\n        <count>ii         (I)nner (I)ndentation level (no line above).\r\n        <count>aI         (A)n (I)ndentation level and lines above\/below.\r\n        <count>iI         (I)nner (I)ndentation level (no lines above\/below).\r\n\r\n\r\nNote that the iI mapping is mostly included simply for completeness, it is\r\neffectively a synonym for ii.\r\n\r\nJust like regular text objects, these mappings can be used either with\r\noperators expecting a motion, such as 'd' or 'c', as well as in visual mode.\r\nIn visual mode the mapping can be repeated, which has the effect of\r\niteratively increasing the scope of indentation block selected. Specifying a\r\ncount can be used to achieve the same effect.\r\n\r\nThe difference between |ai| and |aI| is that |ai| includes the line\r\nimmediately above the indentation block, whereas aI includes not only that,\r\nbut also the line below. Which of these is most useful largely depends on the\r\nstructure of the language being edited.\r\n\r\nFor example, when editing the Python code, |ai| is generally more useful, as\r\nthe line above the indentation block is usually related to it. For example, in\r\nthe following code (* is used to indicate the cursor position):\r\n\r\n      if foo > 3:\r\n         log(\"foo is big\") *\r\n         foo = 3\r\n      do_something_else()\r\n\r\nthe if clause is logically related to the code block, whereas the function\r\ncall below is not. It is unlikely we would want to select the line below when\r\nwe are interested in the if block.\r\n\r\nHowever, in other languages, such as Vim scripts, control structures are\r\nusually terminated with something like 'endif'. Therefore, in this example:\r\n\r\n      if foo > 3\r\n         echo \"foo is big\" *\r\n         let foo = 3\r\n      endif\r\n      call do_something_else()\r\n\r\nwe would more likely want to include the endif when we select the if\r\nstructure.\r\n\r\nWhen scanning code blocks, the plugin usually ignores blank lines. There is an\r\nexception to this, however, when the block being selected is not indented. In\r\nthis case if blank lines are ignored, then the entire file would be selected.\r\nInstead when code at the top level is being indented blank lines are\r\nconsidered to delimit the block.\r\n","install_details":"Unpack the zip archive onto your vim runtime directory.\r\n\r\nAlternatively unpack it to a location of your choice, and update your runtimepath to point to it.","5":"Unpack the zip archive onto your vim runtime directory.\r\n\r\nAlternatively unpack it to a location of your choice, and update your runtimepath to point to it.","first_name":"Michael","6":"Michael","last_name":"Smith","7":"Smith","releases":[{"0":"3037","vim_version":"7.0","1":"7.0","script_version":"1.1.2","2":"1.1.2","version_comment":"Now uses linewise visual mode by default.","3":"Now uses linewise visual mode by default.","package":"vim-indent-object.zip","4":"vim-indent-object.zip","src_id":"12790","5":"12790","creation_date":"1270549968","6":"1270549968"},{"0":"3037","vim_version":"7.0","1":"7.0","script_version":"1.1.1","2":"1.1.1","version_comment":"Fixed when using 'ignorecase'.","3":"Fixed when using 'ignorecase'.","package":"vim-indent-object.zip","4":"vim-indent-object.zip","src_id":"12773","5":"12773","creation_date":"1270251019","6":"1270251019"},{"0":"3037","vim_version":"7.0","1":"7.0","script_version":"1.1","2":"1.1","version_comment":"Made behaviour more consistent and intuitive.","3":"Made behaviour more consistent and intuitive.","package":"vim-indent-object.zip","4":"vim-indent-object.zip","src_id":"12766","5":"12766","creation_date":"1270211333","6":"1270211333"},{"0":"3037","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"vim-indent-object.zip","4":"vim-indent-object.zip","src_id":"12758","5":"12758","creation_date":"1270105083","6":"1270105083"}]},"3036":{"script_id":"3036","0":"3036","script_name":"XTermEsc","1":"XTermEsc","script_type":"syntax","2":"syntax","summary":"highlight xterm escape sequences","3":"highlight xterm escape sequences","description":"This highlights text based on xterm escape sequences using the appropriate color. This is similar to the AnsiEsc script but does not depend on the Conceal patch.  (http:\/\/www.vim.org\/scripts\/script.php?script_id=302)\r\n\r\nThis is done using one of two modes and is configured by setting the g:xterm_trim_escapes variable. When set to 0, escape sequences will be left in the buffer and highlighted using the Ignore group. When set to 1 and the buffer is modifiable, escape sequences will be deleted and highlighting will be performed based on row-column matching. Row-column matching may not work well if the file is being edited but is appropriate under some circumstances. Note that this only affect the escape sequences themselves, not highlighted text.","4":"This highlights text based on xterm escape sequences using the appropriate color. This is similar to the AnsiEsc script but does not depend on the Conceal patch.  (http:\/\/www.vim.org\/scripts\/script.php?script_id=302)\r\n\r\nThis is done using one of two modes and is configured by setting the g:xterm_trim_escapes variable. When set to 0, escape sequences will be left in the buffer and highlighted using the Ignore group. When set to 1 and the buffer is modifiable, escape sequences will be deleted and highlighting will be performed based on row-column matching. Row-column matching may not work well if the file is being edited but is appropriate under some circumstances. Note that this only affect the escape sequences themselves, not highlighted text.","install_details":"Copy xterm.vim to your local syntax directory and use `:setf xterm' when you want highlighting.","5":"Copy xterm.vim to your local syntax directory and use `:setf xterm' when you want highlighting.","first_name":"Andy","6":"Andy","last_name":"Spencer","7":"Spencer","releases":[{"0":"3036","vim_version":"7.0","1":"7.0","script_version":"0.2","2":"0.2","version_comment":"Bug fixes, check &modifiable before trying to delete escapes, highlight escapes with Ignore group","3":"Bug fixes, check &modifiable before trying to delete escapes, highlight escapes with Ignore group","package":"xterm.vim","4":"xterm.vim","src_id":"13112","5":"13112","creation_date":"1275732300","6":"1275732300"},{"0":"3036","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"xterm.vim","4":"xterm.vim","src_id":"12757","5":"12757","creation_date":"1270097703","6":"1270097703"}]},"3035":{"script_id":"3035","0":"3035","script_name":"tesla","1":"tesla","script_type":"color scheme","2":"color scheme","summary":"A dark color scheme for the GUI","3":"A dark color scheme for the GUI","description":"Features:\r\n - change cursor color in different modes\r\n - extra python syntax highlighting (require http:\/\/www.vim.org\/scripts\/script.php?script_id=790)\r\n\r\nScreeshots: http:\/\/lazycleric.blogspot.com\/2010\/03\/vim.html","4":"Features:\r\n - change cursor color in different modes\r\n - extra python syntax highlighting (require http:\/\/www.vim.org\/scripts\/script.php?script_id=790)\r\n\r\nScreeshots: http:\/\/lazycleric.blogspot.com\/2010\/03\/vim.html","install_details":"copy to vim\/colors","5":"copy to vim\/colors","first_name":"Almaz","6":"Almaz","last_name":"Karimov","7":"Karimov","releases":[{"0":"3035","vim_version":"7.0","1":"7.0","script_version":"1.7","2":"1.7","version_comment":"Little color fixes","3":"Little color fixes","package":"tesla.vim","4":"tesla.vim","src_id":"18215","5":"18215","creation_date":"1341349334","6":"1341349334"},{"0":"3035","vim_version":"7.0","1":"7.0","script_version":"1.6","2":"1.6","version_comment":"Added TagListFileName highlighting (taglist plugin)\r\nChanged  colors for Search and Special","3":"Added TagListFileName highlighting (taglist plugin)\r\nChanged  colors for Search and Special","package":"tesla.vim","4":"tesla.vim","src_id":"14038","5":"14038","creation_date":"1286721059","6":"1286721059"},{"0":"3035","vim_version":"7.0","1":"7.0","script_version":"1.5","2":"1.5","version_comment":"Added ColorColumn for Vim 7.3","3":"Added ColorColumn for Vim 7.3","package":"tesla.vim","4":"tesla.vim","src_id":"13591","5":"13591","creation_date":"1281983654","6":"1281983654"},{"0":"3035","vim_version":"7.0","1":"7.0","script_version":"1.4","2":"1.4","version_comment":"Initial upload","3":"Initial upload","package":"tesla.vim","4":"tesla.vim","src_id":"12745","5":"12745","creation_date":"1269983269","6":"1269983269"}]},"3034":{"script_id":"3034","0":"3034","script_name":"syntax\/haskell.vim","1":"syntax\/haskell.vim","script_type":"syntax","2":"syntax","summary":"Haskell Syntax File","3":"Haskell Syntax File","description":"Improvement on the default vim haskell.vim syntax file:\r\n- highlights all Types, not just built in ones\r\n- highlights top level functions\r\n- functions and types are highlighted properly in import\/export lists\r\n- repaired spell checking, thus only string and comments are spell checked\r\n- FFI support\r\n- QuasiQuotation support\r\n- highlighting of top level Template Haskell slices\r\n\r\non github: http:\/\/github.com\/urso\/dotrc\/blob\/master\/vim\/syntax\/haskell.vim\r\n","4":"Improvement on the default vim haskell.vim syntax file:\r\n- highlights all Types, not just built in ones\r\n- highlights top level functions\r\n- functions and types are highlighted properly in import\/export lists\r\n- repaired spell checking, thus only string and comments are spell checked\r\n- FFI support\r\n- QuasiQuotation support\r\n- highlighting of top level Template Haskell slices\r\n\r\non github: http:\/\/github.com\/urso\/dotrc\/blob\/master\/vim\/syntax\/haskell.vim\r\n","install_details":"Put haskell.vim in your syntax diretory (e.g. ~\/.vim\/syntax).","5":"Put haskell.vim in your syntax diretory (e.g. ~\/.vim\/syntax).","first_name":"Steffen","6":"Steffen","last_name":"Siering","7":"Siering","releases":[{"0":"3034","vim_version":"7.0","1":"7.0","script_version":"1.4","2":"1.4","version_comment":"- rewrite of highlighting for module declarations \r\n- rewrite highlighting of import statements (with minimal error highlighting)\r\n- added quasi quotation for ghc7\r\n- added keyword \"family\" for type and data families\r\n- fixed highlighting of functions using (pattern) guards","3":"- rewrite of highlighting for module declarations \r\n- rewrite highlighting of import statements (with minimal error highlighting)\r\n- added quasi quotation for ghc7\r\n- added keyword \"family\" for type and data families\r\n- fixed highlighting of functions using (pattern) guards","package":"haskell.vim","4":"haskell.vim","src_id":"14925","5":"14925","creation_date":"1296466578","6":"1296466578"},{"0":"3034","vim_version":"7.0","1":"7.0","script_version":"1.3","2":"1.3","version_comment":"- improved quasi quotation\r\n- added Toplevel Template Haskell slices support","3":"- improved quasi quotation\r\n- added Toplevel Template Haskell slices support","package":"haskell.vim","4":"haskell.vim","src_id":"13377","5":"13377","creation_date":"1279739803","6":"1279739803"},{"0":"3034","vim_version":"7.0","1":"7.0","script_version":"1.2","2":"1.2","version_comment":"added highlighting for:\r\n- quasi quotation\r\n- package imports","3":"added highlighting for:\r\n- quasi quotation\r\n- package imports","package":"haskell.vim","4":"haskell.vim","src_id":"13240","5":"13240","creation_date":"1277494172","6":"1277494172"},{"0":"3034","vim_version":"7.0","1":"7.0","script_version":"1.1.1","2":"1.1.1","version_comment":"fixed function declaration String arguments highlighting issues ","3":"fixed function declaration String arguments highlighting issues ","package":"haskell.vim","4":"haskell.vim","src_id":"13210","5":"13210","creation_date":"1276824566","6":"1276824566"},{"0":"3034","vim_version":"7.0","1":"7.0","script_version":"1.1","2":"1.1","version_comment":"- improved module export list highlighting\r\n- fixed module highlighting bugs\r\n- added FFI highlighting","3":"- improved module export list highlighting\r\n- fixed module highlighting bugs\r\n- added FFI highlighting","package":"haskell.vim","4":"haskell.vim","src_id":"12973","5":"12973","creation_date":"1273336384","6":"1273336384"},{"0":"3034","vim_version":"7.0","1":"7.0","script_version":"1","2":"1","version_comment":"Initial upload","3":"Initial upload","package":"haskell.vim","4":"haskell.vim","src_id":"12744","5":"12744","creation_date":"1269978391","6":"1269978391"}]},"3033":{"script_id":"3033","0":"3033","script_name":"Vim Title Formatter","1":"Vim Title Formatter","script_type":"utility","2":"utility","summary":"Formats the gvim instance titlebar string for efficiency","3":"Formats the gvim instance titlebar string for efficiency","description":"This simple script formats the title string of the gvim\/vim instance in the following format:\r\n\r\n<servername\/user-defined title> | <current filename> (<filepath>)\r\n\r\nA user-defined title will take precedence over the servername. If the servername and user-defined title are both not defined or blank, then the title is simply \r\n\r\n<filename> (<filepath>)\r\n\r\nIf you ever work on multiple projects (each with its files open in a single gvim instance), then using this script, a glance will tell you which instance you're looking at (based on servername or user-defined title)\r\n\r\n:SetVimTitleString <titlestring>\r\n\r\nwill set the title of the window.\r\n\r\n:ClearVimTitleString\r\n\r\nwill clear the title of the window.","4":"This simple script formats the title string of the gvim\/vim instance in the following format:\r\n\r\n<servername\/user-defined title> | <current filename> (<filepath>)\r\n\r\nA user-defined title will take precedence over the servername. If the servername and user-defined title are both not defined or blank, then the title is simply \r\n\r\n<filename> (<filepath>)\r\n\r\nIf you ever work on multiple projects (each with its files open in a single gvim instance), then using this script, a glance will tell you which instance you're looking at (based on servername or user-defined title)\r\n\r\n:SetVimTitleString <titlestring>\r\n\r\nwill set the title of the window.\r\n\r\n:ClearVimTitleString\r\n\r\nwill clear the title of the window.","install_details":"Simply copy the file into your .vim\/plugin directory. \r\n\r\n:SetVimTitleString <titlestring>\r\n\r\nwill set the title of the window.\r\n\r\n:ClearVimTitleString\r\n\r\nwill clear the title of the window.","5":"Simply copy the file into your .vim\/plugin directory. \r\n\r\n:SetVimTitleString <titlestring>\r\n\r\nwill set the title of the window.\r\n\r\n:ClearVimTitleString\r\n\r\nwill clear the title of the window.","first_name":"Densel","6":"Densel","last_name":"Santhmayor","7":"Santhmayor","releases":[{"0":"3033","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"titleformatter.vim","4":"titleformatter.vim","src_id":"12738","5":"12738","creation_date":"1269920354","6":"1269920354"}]},"3032":{"script_id":"3032","0":"3032","script_name":"Mahewincs","1":"Mahewincs","script_type":"color scheme","2":"color scheme","summary":"A vim colorscheme","3":"A vim colorscheme","description":"I wrote this colorscheme, because I did not find one which pleased me. I also wished to have fun a little. I tried to be in a sence original and I could help myself to use many colors, and I couldn't help to wink at to my colors' country. Mahewincs is actually in the first version, it would change again, but the base will remain the same. I will  also add others colors' definitions for gui(Gvim) and otherslittle things to fix for next version.  \r\n\r\nI hope it will be use by the other persons than myself, I will so be pleased.","4":"I wrote this colorscheme, because I did not find one which pleased me. I also wished to have fun a little. I tried to be in a sence original and I could help myself to use many colors, and I couldn't help to wink at to my colors' country. Mahewincs is actually in the first version, it would change again, but the base will remain the same. I will  also add others colors' definitions for gui(Gvim) and otherslittle things to fix for next version.  \r\n\r\nI hope it will be use by the other persons than myself, I will so be pleased.","install_details":"Decompress archive: tar -zxvf Mahewincs.tar.gz,\r\nMove the colorscheme in $HOME\/.vim \/colors,\r\nAdd on this line, in your .vimrc:                                                                                                             \r\n    colorscheme Mahewincs\r\n","5":"Decompress archive: tar -zxvf Mahewincs.tar.gz,\r\nMove the colorscheme in $HOME\/.vim \/colors,\r\nAdd on this line, in your .vimrc:                                                                                                             \r\n    colorscheme Mahewincs\r\n","first_name":"Natal","6":"Natal","last_name":"Ng\u00c3\u00a9tal","7":"Ng\u00c3\u00a9tal","releases":[{"0":"3032","vim_version":"7.0","1":"7.0","script_version":"0.2","2":"0.2","version_comment":"New version of Mahewincs. Add support of gvim, and many colors for type and so on.","3":"New version of Mahewincs. Add support of gvim, and many colors for type and so on.","package":"Mahewincs.tar.gz","4":"Mahewincs.tar.gz","src_id":"17582","5":"17582","creation_date":"1331418911","6":"1331418911"},{"0":"3032","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"Mahewincs.tar.gz","4":"Mahewincs.tar.gz","src_id":"12729","5":"12729","creation_date":"1269801864","6":"1269801864"}]},"3031":{"script_id":"3031","0":"3031","script_name":"orange","1":"orange","script_type":"color scheme","2":"color scheme","summary":"a mild color theme","3":"a mild color theme","description":"a mild color theme","4":"a mild color theme","install_details":"copy to the colors folder","5":"copy to the colors folder","first_name":"christian","6":"christian","last_name":"jagd","7":"jagd","releases":[{"0":"3031","vim_version":"6.0","1":"6.0","script_version":"0.8","2":"0.8","version_comment":"Initial upload","3":"Initial upload","package":"orange.vim","4":"orange.vim","src_id":"12726","5":"12726","creation_date":"1269799115","6":"1269799115"}]},"3030":{"script_id":"3030","0":"3030","script_name":"motpat.vim","1":"motpat.vim","script_type":"utility","2":"utility","summary":"create motion mappings defined by a pattern","3":"create motion mappings defined by a pattern","description":"Create motion mappings defined by a pattern.\r\nThe resulting keys can be used in Normal, Visual and Operator-pending mode; and they accept a count.\r\n\r\n2017 Nov 10 https:\/\/github.com\/Houl\/motpat-vim\r\n\r\nFunctions:\r\n\r\nmotpat#Map({buf-local}, {lhs-forw}, {lhs-back}, {rhs-pat}[, {excl}])\r\n\r\n    {buf-local}\t\tif non-zero, create buffer-local mappings, else global mappings\r\n    {lhs-forw}\t\tkey to be mapped for forward searching (not if empty)\r\n    {lhs-back}\t\tkey to be mapped for backward searching (not if empty)\r\n    {rhs-pat}\t\tpattern to define the motion, will be part of the resulting {rhs} of the mapping\r\n    {excl}\t\ttype of motion, one of \"e\" (default), \"i\" or \"l\", for exclusive, inclusive or linewise, makes use of |o_v|.\r\n\r\n\" the following two functions just omit one argument:\r\nmotpat#Fmap({buf-local}, {lhs-forw}, {rhs-pat}[, {excl}])\r\nmotpat#Bmap({buf-local}, {lhs-back}, {rhs-pat}[, {excl}])\r\n\r\n\r\nExamples:\r\n\r\nftplugin\/vim.vim >\r\n\t\" simpler definition of ]], [[, ][, [], [\" and ]\"\r\n\r\n\t\" Move around functions.\r\n\tcall motpat#Map(1, ']]', '[[', '^\\s*fu\\%[nction]\\>')\r\n\tcall motpat#Map(1, '][', '[]', '^\\s*endf\\%[unction]\\>', 'l')\r\n\r\n\t\" Move around comments\r\n\tcall motpat#Fmap(1, ']\"', '\\%(^\\s*\".*\\n\\)\\%(^\\s*\"\\)\\@!', 'l')\r\n\tcall motpat#Bmap(1, '[\"', '\\%(^\\s*\".*\\n\\)\\@<!\\%(^\\s*\"\\)', 'l')","4":"Create motion mappings defined by a pattern.\r\nThe resulting keys can be used in Normal, Visual and Operator-pending mode; and they accept a count.\r\n\r\n2017 Nov 10 https:\/\/github.com\/Houl\/motpat-vim\r\n\r\nFunctions:\r\n\r\nmotpat#Map({buf-local}, {lhs-forw}, {lhs-back}, {rhs-pat}[, {excl}])\r\n\r\n    {buf-local}\t\tif non-zero, create buffer-local mappings, else global mappings\r\n    {lhs-forw}\t\tkey to be mapped for forward searching (not if empty)\r\n    {lhs-back}\t\tkey to be mapped for backward searching (not if empty)\r\n    {rhs-pat}\t\tpattern to define the motion, will be part of the resulting {rhs} of the mapping\r\n    {excl}\t\ttype of motion, one of \"e\" (default), \"i\" or \"l\", for exclusive, inclusive or linewise, makes use of |o_v|.\r\n\r\n\" the following two functions just omit one argument:\r\nmotpat#Fmap({buf-local}, {lhs-forw}, {rhs-pat}[, {excl}])\r\nmotpat#Bmap({buf-local}, {lhs-back}, {rhs-pat}[, {excl}])\r\n\r\n\r\nExamples:\r\n\r\nftplugin\/vim.vim >\r\n\t\" simpler definition of ]], [[, ][, [], [\" and ]\"\r\n\r\n\t\" Move around functions.\r\n\tcall motpat#Map(1, ']]', '[[', '^\\s*fu\\%[nction]\\>')\r\n\tcall motpat#Map(1, '][', '[]', '^\\s*endf\\%[unction]\\>', 'l')\r\n\r\n\t\" Move around comments\r\n\tcall motpat#Fmap(1, ']\"', '\\%(^\\s*\".*\\n\\)\\%(^\\s*\"\\)\\@!', 'l')\r\n\tcall motpat#Bmap(1, '[\"', '\\%(^\\s*\".*\\n\\)\\@<!\\%(^\\s*\"\\)', 'l')","install_details":"extract to a runtimepath folder\r\n\r\nfiles in the archive:\r\nautoload\/motpat.vim\r\nautoload\/gvmap.vim (helper script)\r\ndoc\/motpat.txt","5":"extract to a runtimepath folder\r\n\r\nfiles in the archive:\r\nautoload\/motpat.vim\r\nautoload\/gvmap.vim (helper script)\r\ndoc\/motpat.txt","first_name":"Andy","6":"Andy","last_name":"Wokula","7":"Wokula","releases":[{"0":"3030","vim_version":"7.2","1":"7.2","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"motpat_0.1.zip","4":"motpat_0.1.zip","src_id":"12721","5":"12721","creation_date":"1269789185","6":"1269789185"}]},"3029":{"script_id":"3029","0":"3029","script_name":"tex-turkce","1":"tex-turkce","script_type":"ftplugin","2":"ftplugin","summary":"Converts Turkish characters to their TeX\/HTML representation and back.","3":"Converts Turkish characters to their TeX\/HTML representation and back.","description":"tex_turkce.vim\r\nConverts Turkish characters to their TeX\/HTML representation and back.\r\n\r\nHome page: https:\/\/github.com\/caglartoklu\/tex_turkce.vim\r\n\r\nThe development is completely moved to Github.\r\nFor documentation and screenshot, please visit the homepage link.\r\nFunctionality changes will still be reflected to Vim.org page.","4":"tex_turkce.vim\r\nConverts Turkish characters to their TeX\/HTML representation and back.\r\n\r\nHome page: https:\/\/github.com\/caglartoklu\/tex_turkce.vim\r\n\r\nThe development is completely moved to Github.\r\nFor documentation and screenshot, please visit the homepage link.\r\nFunctionality changes will still be reflected to Vim.org page.","install_details":"For Vundle users:\r\n    Bundle 'caglartoklu\/tex_turkce.vim'\r\n\r\nFor Pathogen users:\r\n    cd ~\/.vim\/bundle\r\n    git clone git:\/\/github.com\/caglartoklu\/tex_turkce.vim\r\n\r\nFor all other users, simply drop the tex_turkce.vim file to your plugin directory.","5":"For Vundle users:\r\n    Bundle 'caglartoklu\/tex_turkce.vim'\r\n\r\nFor Pathogen users:\r\n    cd ~\/.vim\/bundle\r\n    git clone git:\/\/github.com\/caglartoklu\/tex_turkce.vim\r\n\r\nFor all other users, simply drop the tex_turkce.vim file to your plugin directory.","first_name":"Caglar","6":"Caglar","last_name":"Toklu","7":"Toklu","releases":[{"0":"3029","vim_version":"7.0","1":"7.0","script_version":"2013-10-30","2":"2013-10-30","version_comment":"Added generic TrTo and TrFrom commands which calls the appropriate conversion function according to the file type.","3":"Added generic TrTo and TrFrom commands which calls the appropriate conversion function according to the file type.","package":"tex_turkce.vim","4":"tex_turkce.vim","src_id":"20983","5":"20983","creation_date":"1383168737","6":"1383168737"},{"0":"3029","vim_version":"7.0","1":"7.0","script_version":"2013-10-08","2":"2013-10-08","version_comment":"- HTML support: :TrToHtml and TrFromHtml commands added.","3":"- HTML support: :TrToHtml and TrFromHtml commands added.","package":"tex_turkce.vim","4":"tex_turkce.vim","src_id":"20899","5":"20899","creation_date":"1381256637","6":"1381256637"},{"0":"3029","vim_version":"7.0","1":"7.0","script_version":"2013-10-06","2":"2013-10-06","version_comment":"- Conversion in selection instead of whole file.\r\n- If no selection is provided, whole file is used.\r\n- Commands renamed as :TrToTex and :TrFromTex\r\n- The script is now a plugin instead of ftplugin, since it will not be limited with .tex files in the future.\r\n- Hosted the code on Github, all the development will be on Github from now on.\r\n- Vim.org will be updated if a major change happens.\r\n- The license has been changed from GPL to 2-clause FreeBSD.\r\n- The file is saved in UNIX file format instead of Windows.","3":"- Conversion in selection instead of whole file.\r\n- If no selection is provided, whole file is used.\r\n- Commands renamed as :TrToTex and :TrFromTex\r\n- The script is now a plugin instead of ftplugin, since it will not be limited with .tex files in the future.\r\n- Hosted the code on Github, all the development will be on Github from now on.\r\n- Vim.org will be updated if a major change happens.\r\n- The license has been changed from GPL to 2-clause FreeBSD.\r\n- The file is saved in UNIX file format instead of Windows.","package":"tex_turkce.vim","4":"tex_turkce.vim","src_id":"20891","5":"20891","creation_date":"1381074817","6":"1381074817"},{"0":"3029","vim_version":"6.0","1":"6.0","script_version":"0.0.1","2":"0.0.1","version_comment":"Initial upload","3":"Initial upload","package":"tex_turkce.vim","4":"tex_turkce.vim","src_id":"12717","5":"12717","creation_date":"1269721900","6":"1269721900"}]},"3028":{"script_id":"3028","0":"3028","script_name":"rename.vim","1":"rename.vim","script_type":"utility","2":"utility","summary":"rename variables and files in your code","3":"rename variables and files in your code","description":"IMPORTANT:\r\n\r\nIt is recommended to use EasyGrep.vim rather than this script. The \"replace\" feature does nearly the same thing, and the implementation is much better.\r\n\r\n==\r\n\r\nThis script is a fork of renamec.vim from Bastian Mathes\r\n\r\nIt features two functions:\r\n:call Renamec() renames the variable under the cursor. Cscope is called to get the references to the corresponding C symbol.\r\n:call Renamef() renames the file under the cursor. The references to this files (like #include\"path\/to\/file\") are updated.\r\n\r\n- When renaming a variable or a file, the quickfix list is updated, so you can jump in the code to modified parts (for example to check if the comments need an update).\r\n- The buffers where the modifications occured are not unloaded and changes are joined so that they can be canceled easily with ':bufdo undo'\r\n","4":"IMPORTANT:\r\n\r\nIt is recommended to use EasyGrep.vim rather than this script. The \"replace\" feature does nearly the same thing, and the implementation is much better.\r\n\r\n==\r\n\r\nThis script is a fork of renamec.vim from Bastian Mathes\r\n\r\nIt features two functions:\r\n:call Renamec() renames the variable under the cursor. Cscope is called to get the references to the corresponding C symbol.\r\n:call Renamef() renames the file under the cursor. The references to this files (like #include\"path\/to\/file\") are updated.\r\n\r\n- When renaming a variable or a file, the quickfix list is updated, so you can jump in the code to modified parts (for example to check if the comments need an update).\r\n- The buffers where the modifications occured are not unloaded and changes are joined so that they can be canceled easily with ':bufdo undo'\r\n","install_details":"open the vimball archive with vim and source it with ':so %'","5":"open the vimball archive with vim and source it with ':so %'","first_name":"Christophe-Marie","6":"Christophe-Marie","last_name":"Duquesne","7":"Duquesne","releases":[{"0":"3028","vim_version":"7.0","1":"7.0","script_version":"1.1","2":"1.1","version_comment":"code cleanup","3":"code cleanup","package":"rename.vba","4":"rename.vba","src_id":"12710","5":"12710","creation_date":"1269611490","6":"1269611490"},{"0":"3028","vim_version":"7.2","1":"7.2","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"rename.vba","4":"rename.vba","src_id":"12707","5":"12707","creation_date":"1269561061","6":"1269561061"}]},"3027":{"script_id":"3027","0":"3027","script_name":"grsecurity","1":"grsecurity","script_type":"ftplugin","2":"ftplugin","summary":"grsecurity ftplugin to edit policy files and see grsec log messages (dmesg)","3":"grsecurity ftplugin to edit policy files and see grsec log messages (dmesg)","description":"This is a filetype plugin for editing grsecurity poilcy file, here is the short list of features:\r\n* search for a role, moving to a role, moving to previous\/next role\r\n* search for a subject in a given role, list all subjects of a role in alphabetical order\r\n* search for an object with given flags (and without some other flags)\r\n* search for subjects with learning mode set\r\n\r\n* reload the policy file and authenticate to admin role\r\n* list grsecurity messages via dmesg (from the last time that RBAC system was (re)loaded\r\n\r\nYou can also find grsecutiry syntax file (it is not included here) among vim scripts.","4":"This is a filetype plugin for editing grsecurity poilcy file, here is the short list of features:\r\n* search for a role, moving to a role, moving to previous\/next role\r\n* search for a subject in a given role, list all subjects of a role in alphabetical order\r\n* search for an object with given flags (and without some other flags)\r\n* search for subjects with learning mode set\r\n\r\n* reload the policy file and authenticate to admin role\r\n* list grsecurity messages via dmesg (from the last time that RBAC system was (re)loaded\r\n\r\nYou can also find grsecutiry syntax file (it is not included here) among vim scripts.","install_details":"open the vimball file and issue\r\n                    :so %\r\n   \r\n","5":"open the vimball file and issue\r\n                    :so %\r\n   \r\n","first_name":"Marcin","6":"Marcin","last_name":"Szamotulski","7":"Szamotulski","releases":[{"0":"3027","vim_version":"7.0","1":"7.0","script_version":"2","2":"2","version_comment":"Some small fixes.","3":"Some small fixes.","package":"grsecurity.vba","4":"grsecurity.vba","src_id":"12899","5":"12899","creation_date":"1272186844","6":"1272186844"},{"0":"3027","vim_version":"7.0","1":"7.0","script_version":"1","2":"1","version_comment":"Initial upload","3":"Initial upload","package":"grsecurity.vba","4":"grsecurity.vba","src_id":"12695","5":"12695","creation_date":"1269423466","6":"1269423466"}]},"3026":{"script_id":"3026","0":"3026","script_name":"PickAColor.vim","1":"PickAColor.vim","script_type":"utility","2":"utility","summary":"Inserts and edits color codes using a color name or a graphic color chooser.","3":"Inserts and edits color codes using a color name or a graphic color chooser.","description":"The PickAColor plugin is an attempt to make inserting or modifing colors easier. With it you can use the GTk or Mac OS X color chooser or a color name to insert or modify an existing color code. It borrows heavily from vimscript #3014 and vimscript #2756.\r\n\r\nIt provides four commands that will insert the corresponding code:\r\n- :PickHEX\r\n- :PickHSL\r\n- :PickRGB\r\n- :PickRAW\r\n\r\nYou can give a color name as an argument with the command and it will be translated to its corresponding code. You can set which set of color names to use, either web or X11, with the option g:pickacolor_use_web_colors.\r\n\r\nUsing any of the commands without arguments will open the Mac OS X (if working on a mac) or GTK (if available) color chooser dialog.\r\n\r\nWhen the cursor is on a hexadecimal color code or a color name, it will be replaced with the new color. If you open the color chooser, it will load the current color. This feature can be disabled with g:pickacolor_edit_names and g:pickacolor_edit_hex.\r\n\r\nIf there is no hexadecimal color code or a color name under the cursor, the clipboard will be read and parsed for one and it will be used for the color chooser dialog.\r\n\r\nWhen you edit or insert a color, the code will be also loaded into the clipboard (under X11 the selection clipboard will be used).\r\n\r\nBoth features can be disabled with g:pickacolor_set_clipboard and g:pickacolor_get_clipboard.\r\n\r\nThe color name supported are those listed in the following sources:\r\n\r\nWeb color names:\r\n  http:\/\/www.w3.org\/TR\/css3-color\/#svg-color\r\n\r\nX11 color names:\r\n  http:\/\/cvsweb.xfree86.org\/cvsweb\/xc\/programs\/rgb\/rgb.txt?rev=1.2\r\n\r\nRead :help PickAColor for more details.","4":"The PickAColor plugin is an attempt to make inserting or modifing colors easier. With it you can use the GTk or Mac OS X color chooser or a color name to insert or modify an existing color code. It borrows heavily from vimscript #3014 and vimscript #2756.\r\n\r\nIt provides four commands that will insert the corresponding code:\r\n- :PickHEX\r\n- :PickHSL\r\n- :PickRGB\r\n- :PickRAW\r\n\r\nYou can give a color name as an argument with the command and it will be translated to its corresponding code. You can set which set of color names to use, either web or X11, with the option g:pickacolor_use_web_colors.\r\n\r\nUsing any of the commands without arguments will open the Mac OS X (if working on a mac) or GTK (if available) color chooser dialog.\r\n\r\nWhen the cursor is on a hexadecimal color code or a color name, it will be replaced with the new color. If you open the color chooser, it will load the current color. This feature can be disabled with g:pickacolor_edit_names and g:pickacolor_edit_hex.\r\n\r\nIf there is no hexadecimal color code or a color name under the cursor, the clipboard will be read and parsed for one and it will be used for the color chooser dialog.\r\n\r\nWhen you edit or insert a color, the code will be also loaded into the clipboard (under X11 the selection clipboard will be used).\r\n\r\nBoth features can be disabled with g:pickacolor_set_clipboard and g:pickacolor_get_clipboard.\r\n\r\nThe color name supported are those listed in the following sources:\r\n\r\nWeb color names:\r\n  http:\/\/www.w3.org\/TR\/css3-color\/#svg-color\r\n\r\nX11 color names:\r\n  http:\/\/cvsweb.xfree86.org\/cvsweb\/xc\/programs\/rgb\/rgb.txt?rev=1.2\r\n\r\nRead :help PickAColor for more details.","install_details":"requirements:\r\nThe script requires Vim 7.2 or later and Python 2.5 or later with the PyGTK module and GTK.\r\n\r\nThis script is packaged as a vimball. If gnuzip is in your $PATH, simply edit PickAColor.vba.gz in Vim and then source the file; otherwise, decompress the archive first.\r\ne.g.:\r\n        vim PickAColor.vba.gz\r\n        :source %\r\n\r\nIf you want to remove this plugin, type the following inside Vim:\r\n\r\n        :RmVimball PickAColor\r\n\r\nIf you have GetLatestVimScripts configured, PickAColor will be automatically added the next time you run :GetScripts. ","5":"requirements:\r\nThe script requires Vim 7.2 or later and Python 2.5 or later with the PyGTK module and GTK.\r\n\r\nThis script is packaged as a vimball. If gnuzip is in your $PATH, simply edit PickAColor.vba.gz in Vim and then source the file; otherwise, decompress the archive first.\r\ne.g.:\r\n        vim PickAColor.vba.gz\r\n        :source %\r\n\r\nIf you want to remove this plugin, type the following inside Vim:\r\n\r\n        :RmVimball PickAColor\r\n\r\nIf you have GetLatestVimScripts configured, PickAColor will be automatically added the next time you run :GetScripts. ","first_name":"Israel","6":"Israel","last_name":"Chauca Fuentes","7":"Chauca Fuentes","releases":[{"0":"3026","vim_version":"7.0","1":"7.0","script_version":"1.1","2":"1.1","version_comment":"- Fixed some typos and noisy output. Thanks to Steve\r\n  Huff for pointing this out.\r\n- If GTK is not available and the plug-in is not\r\n  running under Mac OS X, the commands still will work with\r\n  color names.","3":"- Fixed some typos and noisy output. Thanks to Steve\r\n  Huff for pointing this out.\r\n- If GTK is not available and the plug-in is not\r\n  running under Mac OS X, the commands still will work with\r\n  color names.","package":"PickAColor.vba.gz","4":"PickAColor.vba.gz","src_id":"12692","5":"12692","creation_date":"1269373035","6":"1269373035"},{"0":"3026","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload.","3":"Initial upload.","package":"PickAColor.vba.gz","4":"PickAColor.vba.gz","src_id":"12682","5":"12682","creation_date":"1269307683","6":"1269307683"}]},"3025":{"script_id":"3025","0":"3025","script_name":"Command-T","1":"Command-T","script_type":"utility","2":"utility","summary":"Fast file navigation for VIM","3":"Fast file navigation for VIM","description":"The Command-T plug-in provides an extremely fast, intuitive mechanism for opening files with a minimal number of keystrokes. It's named \"Command-T\" because it is inspired by the \"Go to File\" window bound to Command-T in TextMate.\r\n\r\nFiles are selected by typing characters that appear in their paths, and are ordered by an algorithm which knows that characters that appear in certain locations (for example, immediately after a path separator) should be given more weight.\r\n\r\nFor more details see the project Git repository:\r\n\r\n  https:\/\/github.com\/wincent\/command-t","4":"The Command-T plug-in provides an extremely fast, intuitive mechanism for opening files with a minimal number of keystrokes. It's named \"Command-T\" because it is inspired by the \"Go to File\" window bound to Command-T in TextMate.\r\n\r\nFiles are selected by typing characters that appear in their paths, and are ordered by an algorithm which knows that characters that appear in certain locations (for example, immediately after a path separator) should be given more weight.\r\n\r\nFor more details see the project Git repository:\r\n\r\n  https:\/\/github.com\/wincent\/command-t","install_details":"Please see detailed instructions here:\r\n\r\n  https:\/\/github.com\/wincent\/command-t","5":"Please see detailed instructions here:\r\n\r\n  https:\/\/github.com\/wincent\/command-t","first_name":"Greg","6":"Greg","last_name":"Hurrell","7":"Hurrell","releases":[{"0":"3025","vim_version":"7.0","1":"7.0","script_version":"6.0.0-b.1","2":"6.0.0-b.1","version_comment":"- fix: actually respect `scanners.git.submodules` and `scanners.git.untracked` options in |commandt.setup()| (https:\/\/github.com\/wincent\/command-t\/pull\/414).\r\n- fix: avoid \"invalid option\" error to `format` at specific window dimensions (https:\/\/github.com\/wincent\/command-t\/issues\/415).\r\n","3":"- fix: actually respect `scanners.git.submodules` and `scanners.git.untracked` options in |commandt.setup()| (https:\/\/github.com\/wincent\/command-t\/pull\/414).\r\n- fix: avoid \"invalid option\" error to `format` at specific window dimensions (https:\/\/github.com\/wincent\/command-t\/issues\/415).\r\n","package":"command-t-6.0.0-b.1.zip","4":"command-t-6.0.0-b.1.zip","src_id":"28317","5":"28317","creation_date":"1671236155","6":"1671236155"},{"0":"3025","vim_version":"7.0","1":"7.0","script_version":"6.0.0-b.0","2":"6.0.0-b.0","version_comment":"- feat: add back `:CommandTLine` finder (https:\/\/github.com\/wincent\/command-t\/pull\/408).\r\n","3":"- feat: add back `:CommandTLine` finder (https:\/\/github.com\/wincent\/command-t\/pull\/408).\r\n","package":"command-t-6.0.0-b.0.zip","4":"command-t-6.0.0-b.0.zip","src_id":"28229","5":"28229","creation_date":"1666405260","6":"1666405260"},{"0":"3025","vim_version":"7.0","1":"7.0","script_version":"6.0.0-a.4","2":"6.0.0-a.4","version_comment":"- fix: use correct `git ls-files` switch when `scanners.git.untracked` is `true`.\r\n  (https:\/\/github.com\/wincent\/command-t\/pull\/405).\r\n- fix: make Watchman scanner work with a path argument\r\n  (https:\/\/github.com\/wincent\/command-t\/commit\/c7020a44cfddfb87).\r\n- feat: show \"fallback\" in prompt title if a fallback scanner kicks in\r\n  (https:\/\/github.com\/wincent\/command-t\/commit\/c16b2721fdad1d0b).\r\n","3":"- fix: use correct `git ls-files` switch when `scanners.git.untracked` is `true`.\r\n  (https:\/\/github.com\/wincent\/command-t\/pull\/405).\r\n- fix: make Watchman scanner work with a path argument\r\n  (https:\/\/github.com\/wincent\/command-t\/commit\/c7020a44cfddfb87).\r\n- feat: show \"fallback\" in prompt title if a fallback scanner kicks in\r\n  (https:\/\/github.com\/wincent\/command-t\/commit\/c16b2721fdad1d0b).\r\n","package":"command-t-6.0.0-a.4.zip","4":"command-t-6.0.0-a.4.zip","src_id":"28165","5":"28165","creation_date":"1662442703","6":"1662442703"},{"0":"3025","vim_version":"7.0","1":"7.0","script_version":"6.0.0-a.3","2":"6.0.0-a.3","version_comment":"- fix: fix build problem on 32-bit systems; this was a regression introduced\r\n  in 6.0.0-a.2 (https:\/\/github.com\/wincent\/command-t\/commit\/6c8e2a3e3b5acd00).\r\n- docs: drop unnecessary `{ remap = true }` from mapping instructions\r\n  (https:\/\/github.com\/wincent\/command-t\/pull\/401)\r\n- feat: implement fallback for when `find`, `git`, or `rg` return no results\r\n  (https:\/\/github.com\/wincent\/command-t\/commit\/9e8c790ca718b40f2).\r\n- refactor: hide standard error output from `find`, `git` and `rg`\r\n  (https:\/\/github.com\/wincent\/command-t\/commit\/b229d929ae2a55a7b).\r\n- fix: don't let control characters mess up the display\r\n  (https:\/\/github.com\/wincent\/command-t\/issues\/402).\r\n","3":"- fix: fix build problem on 32-bit systems; this was a regression introduced\r\n  in 6.0.0-a.2 (https:\/\/github.com\/wincent\/command-t\/commit\/6c8e2a3e3b5acd00).\r\n- docs: drop unnecessary `{ remap = true }` from mapping instructions\r\n  (https:\/\/github.com\/wincent\/command-t\/pull\/401)\r\n- feat: implement fallback for when `find`, `git`, or `rg` return no results\r\n  (https:\/\/github.com\/wincent\/command-t\/commit\/9e8c790ca718b40f2).\r\n- refactor: hide standard error output from `find`, `git` and `rg`\r\n  (https:\/\/github.com\/wincent\/command-t\/commit\/b229d929ae2a55a7b).\r\n- fix: don't let control characters mess up the display\r\n  (https:\/\/github.com\/wincent\/command-t\/issues\/402).\r\n","package":"command-t-6.0.0-a.3.zip","4":"command-t-6.0.0-a.3.zip","src_id":"28157","5":"28157","creation_date":"1662009807","6":"1662009807"},{"0":"3025","vim_version":"7.0","1":"7.0","script_version":"6.0.0-a.2","2":"6.0.0-a.2","version_comment":"- fix: fix rendering glitches due to interaction with vim-dirvish\r\n  (https:\/\/github.com\/wincent\/command-t\/commit\/ca959c9437d13ca0).\r\n- feat: teach prompt window to delete a word with `<C-w>`\r\n  (https:\/\/github.com\/wincent\/command-t\/commit\/0a19ffbe7bed4988).\r\n- fix: avoid aborts on 32-bit systems\r\n  (https:\/\/github.com\/wincent\/command-t\/issues\/399).\r\n","3":"- fix: fix rendering glitches due to interaction with vim-dirvish\r\n  (https:\/\/github.com\/wincent\/command-t\/commit\/ca959c9437d13ca0).\r\n- feat: teach prompt window to delete a word with `<C-w>`\r\n  (https:\/\/github.com\/wincent\/command-t\/commit\/0a19ffbe7bed4988).\r\n- fix: avoid aborts on 32-bit systems\r\n  (https:\/\/github.com\/wincent\/command-t\/issues\/399).\r\n","package":"command-t-6.0.0-a.2.zip","4":"command-t-6.0.0-a.2.zip","src_id":"28154","5":"28154","creation_date":"1661836945","6":"1661836945"},{"0":"3025","vim_version":"7.0","1":"7.0","script_version":"6.0.0-a.1","2":"6.0.0-a.1","version_comment":"- fix: gracefully handle |commandt.setup()| calls without a `finders` config.\r\n  (https:\/\/github.com\/wincent\/command-t\/commit\/e59f7406a565b574).\r\n- refactor: get rid of a potentially confusing diagnostic message\r\n  (https:\/\/github.com\/wincent\/command-t\/commit\/05b434a7dd3e2963).\r\n- docs: add documentation for the |:CommandTFind|, |:CommandTGit|,\r\n  |:CommandTRipgrep|, and |:CommandTWatchman| commands\r\n  (https:\/\/github.com\/wincent\/command-t\/commit\/c488f7f41e863398).\r\n","3":"- fix: gracefully handle |commandt.setup()| calls without a `finders` config.\r\n  (https:\/\/github.com\/wincent\/command-t\/commit\/e59f7406a565b574).\r\n- refactor: get rid of a potentially confusing diagnostic message\r\n  (https:\/\/github.com\/wincent\/command-t\/commit\/05b434a7dd3e2963).\r\n- docs: add documentation for the |:CommandTFind|, |:CommandTGit|,\r\n  |:CommandTRipgrep|, and |:CommandTWatchman| commands\r\n  (https:\/\/github.com\/wincent\/command-t\/commit\/c488f7f41e863398).\r\n","package":"command-t-6.0.0-a.1.zip","4":"command-t-6.0.0-a.1.zip","src_id":"28153","5":"28153","creation_date":"1661724409","6":"1661724409"},{"0":"3025","vim_version":"7.0","1":"7.0","script_version":"6.0.0-a.0","2":"6.0.0-a.0","version_comment":"- Rewrite in Lua; for more details see |command-t-upgrading|. Note that this\r\n  is an alpha release, so the new APIs are subject to change.\r\n","3":"- Rewrite in Lua; for more details see |command-t-upgrading|. Note that this\r\n  is an alpha release, so the new APIs are subject to change.\r\n","package":"command-t-6.0.0-a.0.zip","4":"command-t-6.0.0-a.0.zip","src_id":"28151","5":"28151","creation_date":"1661579005","6":"1661579005"},{"0":"3025","vim_version":"7.0","1":"7.0","script_version":"5.0.5","2":"5.0.5","version_comment":"- Teach watchman scanner to favor `watch-project` over `watch` when available (#390, patch from Todd Derr).","3":"- Teach watchman scanner to favor `watch-project` over `watch` when available (#390, patch from Todd Derr).","package":"command-t-5.0.5.zip","4":"command-t-5.0.5.zip","src_id":"28108","5":"28108","creation_date":"1658646872","6":"1658646872"},{"0":"3025","vim_version":"7.0","1":"7.0","script_version":"5.0.4","2":"5.0.4","version_comment":"- Support opening files which contain newlines (#365).\r\n- Guard against possible |E315| on accepting a selection.\r\n- Fix possible |E434| when trying to jump to some help targets.\r\n- Use |execute()| when available to avoid possible issues with potentially nested calls to |:redir|.\r\n- Fix conflict with vim-cool plugin (#354).\r\n- Close match listing after buffer deletion to avoid likely errors on subsequent interactions (#357, patch from Andrius Grabauskas).\r\n- Fix |E116| error opening filenames containing single quotes.\r\n- Deal with |'wildignore'| (and |g:CommandTWildIgnore|) patterns of the form \"*pattern\" (eg. \"*~\", which would ignore files created with Vim's default |'backupext'|) (#369, patch from Steve Herrell).\r\n- Turn off |'signcolumn'| in the match listing (#376).\r\n- Teach file scanner to skip over badly encoded strings.\r\n- Teach watchman scanner to tolerate broken watchman installation.\r\n","3":"- Support opening files which contain newlines (#365).\r\n- Guard against possible |E315| on accepting a selection.\r\n- Fix possible |E434| when trying to jump to some help targets.\r\n- Use |execute()| when available to avoid possible issues with potentially nested calls to |:redir|.\r\n- Fix conflict with vim-cool plugin (#354).\r\n- Close match listing after buffer deletion to avoid likely errors on subsequent interactions (#357, patch from Andrius Grabauskas).\r\n- Fix |E116| error opening filenames containing single quotes.\r\n- Deal with |'wildignore'| (and |g:CommandTWildIgnore|) patterns of the form \"*pattern\" (eg. \"*~\", which would ignore files created with Vim's default |'backupext'|) (#369, patch from Steve Herrell).\r\n- Turn off |'signcolumn'| in the match listing (#376).\r\n- Teach file scanner to skip over badly encoded strings.\r\n- Teach watchman scanner to tolerate broken watchman installation.\r\n","package":"command-t-5.0.4.zip","4":"command-t-5.0.4.zip","src_id":"28064","5":"28064","creation_date":"1653772445","6":"1653772445"},{"0":"3025","vim_version":"7.0","1":"7.0","script_version":"5.0.3","2":"5.0.3","version_comment":"- Fix unlisted buffers showing up in |:CommandTBuffer| listing on Neovim.\n- Fix edge cases with opening selections in tabs (#315).\n- Fix possible degenerate performance of |:CommandTBuffer| and\n  |:CommandTMRU| on Neovim.\n- Handle missing match listing buffer in Neovim (#342).\n","3":"- Fix unlisted buffers showing up in |:CommandTBuffer| listing on Neovim.\n- Fix edge cases with opening selections in tabs (#315).\n- Fix possible degenerate performance of |:CommandTBuffer| and\n  |:CommandTMRU| on Neovim.\n- Handle missing match listing buffer in Neovim (#342).\n","package":"command-t-5.0.3.zip","4":"command-t-5.0.3.zip","src_id":"26226","5":"26226","creation_date":"1537424209","6":"1537424209"},{"0":"3025","vim_version":"7.0","1":"7.0","script_version":"5.0.2","2":"5.0.2","version_comment":"- Fix a RangeError on 64-bit Windows (#304, patch from Adrian Keet).\n- Fix issue switching back to previously opened file in another tab (#306).\n- Fix inability to open some help targets with |:CommandTHelp| (#307).\n- Similar to #307, make |:CommandTCommand| work with commands containing\n  special characters.\n- Again similar to #307, prevent special characters in tags from being escaped\n  when using |:CommandTTag|.\n","3":"- Fix a RangeError on 64-bit Windows (#304, patch from Adrian Keet).\n- Fix issue switching back to previously opened file in another tab (#306).\n- Fix inability to open some help targets with |:CommandTHelp| (#307).\n- Similar to #307, make |:CommandTCommand| work with commands containing\n  special characters.\n- Again similar to #307, prevent special characters in tags from being escaped\n  when using |:CommandTTag|.\n","package":"command-t-5.0.2.zip","4":"command-t-5.0.2.zip","src_id":"25555","5":"25555","creation_date":"1504810116","6":"1504810116"},{"0":"3025","vim_version":"7.0","1":"7.0","script_version":"5.0.1","2":"5.0.1","version_comment":"- Fixed inability to open a top-level file with a name matching a previously\n  opened file (#295).\n- Fixed a related issue where previously opened file would cause a file to be\n  opened directly rather than in the desired split\/tab (#298).\n- Tweaked <c-w> mapping behavior to better match what other readline-ish\n  implementations do, especially with respect to moving past punctuation\n  (#301).\n","3":"- Fixed inability to open a top-level file with a name matching a previously\n  opened file (#295).\n- Fixed a related issue where previously opened file would cause a file to be\n  opened directly rather than in the desired split\/tab (#298).\n- Tweaked <c-w> mapping behavior to better match what other readline-ish\n  implementations do, especially with respect to moving past punctuation\n  (#301).\n","package":"command-t-5.0.1.zip","4":"command-t-5.0.1.zip","src_id":"25519","5":"25519","creation_date":"1503073483","6":"1503073483"},{"0":"3025","vim_version":"7.0","1":"7.0","script_version":"5.0","2":"5.0","version_comment":"- Command-T now uses |:map-<nowait>|, when available, when setting up mappings.\n- 'wildignore' filtering is now always performed by producing an equivalent\n  regular expression and applying that; previously this only happened with\n  the \"watchman\" file scanner (includes a bug fix from Henric Trotzig).\n- Fixed mis-memoization of |:CommandTHelp| and |:CommandTJump| finders\n  (whichever one you used first would be used for both).\n- Added mapping (<C-d>) to delete a buffer from the buffer list (patch from\n  Max Timkovich).\n- Added |g:CommandTGitIncludeUntracked| option (patch from Steven Stallion).\n- Added |:CommandTOpen|, which implements smart \"goto or open\" functionality,\n  and adjust |g:CommandTAcceptSelectionCommand|,\n  |g:CommandTAcceptSelectionTabCommand|,\n  |g:CommandTAcceptSelectionSplitCommand|, and\n  |g:CommandTAcceptSelectionVSplitCommand| to use it by default. Their default\n  values have been changed from \"e\", \"tabe\", \"sp\" and \"vs\" to \"CommandTOpen\n  e\", \"CommandTOpen tabe\", \"CommandTOpen sp\" and \"CommandTOpen vs\",\n  respectively. Use with |'switchbuf'| set to \"usetab\" for maximum effect.\n- Added |g:CommandTWindowFilter| for customizing the filtering expression that\n  is used to determine which windows Command-T should not open selected\n  files in.\n","3":"- Command-T now uses |:map-<nowait>|, when available, when setting up mappings.\n- 'wildignore' filtering is now always performed by producing an equivalent\n  regular expression and applying that; previously this only happened with\n  the \"watchman\" file scanner (includes a bug fix from Henric Trotzig).\n- Fixed mis-memoization of |:CommandTHelp| and |:CommandTJump| finders\n  (whichever one you used first would be used for both).\n- Added mapping (<C-d>) to delete a buffer from the buffer list (patch from\n  Max Timkovich).\n- Added |g:CommandTGitIncludeUntracked| option (patch from Steven Stallion).\n- Added |:CommandTOpen|, which implements smart \"goto or open\" functionality,\n  and adjust |g:CommandTAcceptSelectionCommand|,\n  |g:CommandTAcceptSelectionTabCommand|,\n  |g:CommandTAcceptSelectionSplitCommand|, and\n  |g:CommandTAcceptSelectionVSplitCommand| to use it by default. Their default\n  values have been changed from \"e\", \"tabe\", \"sp\" and \"vs\" to \"CommandTOpen\n  e\", \"CommandTOpen tabe\", \"CommandTOpen sp\" and \"CommandTOpen vs\",\n  respectively. Use with |'switchbuf'| set to \"usetab\" for maximum effect.\n- Added |g:CommandTWindowFilter| for customizing the filtering expression that\n  is used to determine which windows Command-T should not open selected\n  files in.\n","package":"command-t-5.0.zip","4":"command-t-5.0.zip","src_id":"25288","5":"25288","creation_date":"1496816484","6":"1496816484"},{"0":"3025","vim_version":"7.0","1":"7.0","script_version":"4.0","2":"4.0","version_comment":"- A non-leading dot in the search query can now match against dot-files and\n  \"dot-directories\" in non-leading path components.\n- Matching algorithm sped up by about 17x (with help from Hanson Wang).\n- |g:CommandTInputDebounce| now defaults to 0, as the recent optimizations\n  make debouncing largely unnecessary.\n- Added |:CommandTHelp| for jumping to locations in the help, and an\n  accompanying mapping, |<Plug>(CommandTHelp)|.\n- Added |:CommandTLine| for jumping to lines within the current buffer, and a\n  corresponding mapping, |<Plug>(CommandTLine)|.\n- Added |:CommandTHistory| for jumping to previously entered commands, and a\n  corresponding mapping, |<Plug>(CommandTHistory)|.\n- Added |:CommandTSearch| for jumping to previously entered searches, and a\n  corresponding mapping, |<Plug>(CommandTSearch)|.\n- Added |:CommandTCommand| for finding commands, and a corresponding mapping,\n  |<Plug>(CommandTCommand)|.\n- Added |<Plug>(CommandTMRU)| and |<Plug>(CommandTTag)| mappings.\n- The \"ruby\" and \"find\" scanners now show numerical progress in the prompt\n  area during their scans.\n- Removed functionality that was previously deprecated in 2.0.\n- Fix inability to type \"^\" and \"|\" at the prompt.\n- Make it possible to completely disable |'wildignore'|-based filtering by\n  setting |g:CommandTWildIgnore| to an empty string.\n- The \"watchman\" file scanner now respects |'wildignore'| and\n  |g:CommandTWildIgnore| by construcing an equivalent regular expression and\n  using that for filtering.\n- Show a warning when hitting |g:CommandTMaxFiles|, and add a corresponding\n  |g:CommandTSuppressMaxFilesWarning| setting to suppress the warning.\n","3":"- A non-leading dot in the search query can now match against dot-files and\n  \"dot-directories\" in non-leading path components.\n- Matching algorithm sped up by about 17x (with help from Hanson Wang).\n- |g:CommandTInputDebounce| now defaults to 0, as the recent optimizations\n  make debouncing largely unnecessary.\n- Added |:CommandTHelp| for jumping to locations in the help, and an\n  accompanying mapping, |<Plug>(CommandTHelp)|.\n- Added |:CommandTLine| for jumping to lines within the current buffer, and a\n  corresponding mapping, |<Plug>(CommandTLine)|.\n- Added |:CommandTHistory| for jumping to previously entered commands, and a\n  corresponding mapping, |<Plug>(CommandTHistory)|.\n- Added |:CommandTSearch| for jumping to previously entered searches, and a\n  corresponding mapping, |<Plug>(CommandTSearch)|.\n- Added |:CommandTCommand| for finding commands, and a corresponding mapping,\n  |<Plug>(CommandTCommand)|.\n- Added |<Plug>(CommandTMRU)| and |<Plug>(CommandTTag)| mappings.\n- The \"ruby\" and \"find\" scanners now show numerical progress in the prompt\n  area during their scans.\n- Removed functionality that was previously deprecated in 2.0.\n- Fix inability to type \"^\" and \"|\" at the prompt.\n- Make it possible to completely disable |'wildignore'|-based filtering by\n  setting |g:CommandTWildIgnore| to an empty string.\n- The \"watchman\" file scanner now respects |'wildignore'| and\n  |g:CommandTWildIgnore| by construcing an equivalent regular expression and\n  using that for filtering.\n- Show a warning when hitting |g:CommandTMaxFiles|, and add a corresponding\n  |g:CommandTSuppressMaxFilesWarning| setting to suppress the warning.\n","package":"command-t-4.0.zip","4":"command-t-4.0.zip","src_id":"24252","5":"24252","creation_date":"1463463187","6":"1463463187"},{"0":"3025","vim_version":"7.0","1":"7.0","script_version":"3.0.2","2":"3.0.2","version_comment":"- Minimize flicker on opening and closing the match listing in MacVim.\n- Add |CommandTWillShowMatchListing| and |CommandTDidHideMatchListing| \"User\"\n  autocommands.\n","3":"- Minimize flicker on opening and closing the match listing in MacVim.\n- Add |CommandTWillShowMatchListing| and |CommandTDidHideMatchListing| \"User\"\n  autocommands.\n","package":"command-t-3.0.2.zip","4":"command-t-3.0.2.zip","src_id":"23997","5":"23997","creation_date":"1455029322","6":"1455029322"},{"0":"3025","vim_version":"7.0","1":"7.0","script_version":"3.0.1","2":"3.0.1","version_comment":"- restore compatiblity with Ruby 1.8.7.\n","3":"- restore compatiblity with Ruby 1.8.7.\n","package":"command-t-3.0.1.zip","4":"command-t-3.0.1.zip","src_id":"23946","5":"23946","creation_date":"1453709216","6":"1453709216"},{"0":"3025","vim_version":"7.0","1":"7.0","script_version":"3.0","2":"3.0","version_comment":"- change |g:CommandTIgnoreSpaces| default value to 1.\n- change |g:CommandTMatchWindowReverse| default value to 1.\n- change |g:CommandTMaxHeight| default value to 15.\n- try harder to avoid scrolling other buffer when showing or hiding the match\n  listing\n","3":"- change |g:CommandTIgnoreSpaces| default value to 1.\n- change |g:CommandTMatchWindowReverse| default value to 1.\n- change |g:CommandTMaxHeight| default value to 15.\n- try harder to avoid scrolling other buffer when showing or hiding the match\n  listing\n","package":"command-t-3.0.zip","4":"command-t-3.0.zip","src_id":"23931","5":"23931","creation_date":"1453232394","6":"1453232394"},{"0":"3025","vim_version":"7.0","1":"7.0","script_version":"2.0","2":"2.0","version_comment":"- add |:CommandTIgnoreSpaces| option (patch from KJ Tsanaktsidis)\n- make Command-T resilient to people deleting its hidden, unlisted buffer\n- the match listing buffer now has filetype \"command-t\", which may be useful\n  for detectability\/extensibility\n- Command-T now sets the name of the match listing buffer according to how it\n  was invoked (ie. for the file finder, the name is \"Command-T [Files]\", for\n  the buffer finder, the name is \"Command-T [Buffers]\", and so on);\n  previously the name was a fixed as \"GoToFile\" regardless of the active\n  finder type\n- Many internal function names have changed, so if you or your plug-ins are\n  calling those internals they will need to be updated:\n  - `commandt#CommandTFlush()` is now `commandt#Flush()`\n  - `commandt#CommandTLoad()` is now `commandt#Load()`\n  - `commandt#CommandTShowBufferFinder()` is now `commandt#BufferFinder()`\n  - `commandt#CommandTShowFileFinder()` is now `commandt#FileFinder()`\n  - `commandt#CommandTShowJumpFinder()` is now `commandt#JumpFinder()`\n  - `commandt#CommandTShowMRUFinder()` is now `commandt#MRUFinder()`\n  - `commandt#CommandTShowTagFinder()` is now `commandt#TagFinder()`\n- A number of functions have been turned into \"private\" autoloaded functions,\n  to make it clear that they are intended only for internal use:\n  - `CommandTAcceptSelection()` is now `commandt#private#AcceptSelection()`\n  - `CommandTAcceptSelectionSplit()` is now `commandt#private#AcceptSelectionSplit()`\n  - `CommandTAcceptSelectionTab()` is now `commandt#private#AcceptSelectionTab()`\n  - `CommandTAcceptSelectionVSplit()` is now `commandt#private#AcceptSelectionVSplit()`\n  - `CommandTBackspace()` is now `commandt#private#Backspace()`\n  - `CommandTCancel()` is now `commandt#private#Cancel()`\n  - `CommandTClear()` is now `commandt#private#Clear()`\n  - `CommandTClearPrevWord()` is now `commandt#private#ClearPrevWord()`\n  - `CommandTCursorEnd()` is now `commandt#private#CursorEnd()`\n  - `CommandTCursorLeft()` is now `commandt#private#CursorLeft()`\n  - `CommandTCursorRight()` is now `commandt#private#CursorRight()`\n  - `CommandTCursorStart()` is now `commandt#private#CursorStart()`\n  - `CommandTDelete()` is now `commandt#private#Delete()`\n  - `CommandTHandleKey()` is now `commandt#private#HandleKey()`\n  - `CommandTListMatches()` is now `commandt#private#ListMatches()`\n  - `CommandTQuickfix()` is now `commandt#private#Quickfix()`\n  - `CommandTRefresh()` is now `commandt#private#Refresh()`\n  - `CommandTSelectNext()` is now `commandt#private#SelectNext()`\n  - `CommandTSelectPrev()` is now `commandt#private#SelectPrev()`\n  - `CommandTToggleFocus()` is now `commandt#private#ToggleFocus()`\n- add |g:CommandTRecursiveMatch| option\n- stop distribution as a vimball in favor of a zip archive\n- don't clobber |alternate-file| name when opening Command-T match listing\n  (patch from Jerome Castaneda)\n- add |g:CommandTCursorColor| option\n- expose mappings for |:CommandT| and |:CommandTBuffer| using `<Plug>`\n  mappings |<Plug>(CommandT)| and |<Plug>(CommandT)|\n- add `<Leader>j` mapping to |:CommandTJump|, via |<Plug>(CommandTJump)|\n  (defined only if no pre-existing mapping exists)\n","3":"- add |:CommandTIgnoreSpaces| option (patch from KJ Tsanaktsidis)\n- make Command-T resilient to people deleting its hidden, unlisted buffer\n- the match listing buffer now has filetype \"command-t\", which may be useful\n  for detectability\/extensibility\n- Command-T now sets the name of the match listing buffer according to how it\n  was invoked (ie. for the file finder, the name is \"Command-T [Files]\", for\n  the buffer finder, the name is \"Command-T [Buffers]\", and so on);\n  previously the name was a fixed as \"GoToFile\" regardless of the active\n  finder type\n- Many internal function names have changed, so if you or your plug-ins are\n  calling those internals they will need to be updated:\n  - `commandt#CommandTFlush()` is now `commandt#Flush()`\n  - `commandt#CommandTLoad()` is now `commandt#Load()`\n  - `commandt#CommandTShowBufferFinder()` is now `commandt#BufferFinder()`\n  - `commandt#CommandTShowFileFinder()` is now `commandt#FileFinder()`\n  - `commandt#CommandTShowJumpFinder()` is now `commandt#JumpFinder()`\n  - `commandt#CommandTShowMRUFinder()` is now `commandt#MRUFinder()`\n  - `commandt#CommandTShowTagFinder()` is now `commandt#TagFinder()`\n- A number of functions have been turned into \"private\" autoloaded functions,\n  to make it clear that they are intended only for internal use:\n  - `CommandTAcceptSelection()` is now `commandt#private#AcceptSelection()`\n  - `CommandTAcceptSelectionSplit()` is now `commandt#private#AcceptSelectionSplit()`\n  - `CommandTAcceptSelectionTab()` is now `commandt#private#AcceptSelectionTab()`\n  - `CommandTAcceptSelectionVSplit()` is now `commandt#private#AcceptSelectionVSplit()`\n  - `CommandTBackspace()` is now `commandt#private#Backspace()`\n  - `CommandTCancel()` is now `commandt#private#Cancel()`\n  - `CommandTClear()` is now `commandt#private#Clear()`\n  - `CommandTClearPrevWord()` is now `commandt#private#ClearPrevWord()`\n  - `CommandTCursorEnd()` is now `commandt#private#CursorEnd()`\n  - `CommandTCursorLeft()` is now `commandt#private#CursorLeft()`\n  - `CommandTCursorRight()` is now `commandt#private#CursorRight()`\n  - `CommandTCursorStart()` is now `commandt#private#CursorStart()`\n  - `CommandTDelete()` is now `commandt#private#Delete()`\n  - `CommandTHandleKey()` is now `commandt#private#HandleKey()`\n  - `CommandTListMatches()` is now `commandt#private#ListMatches()`\n  - `CommandTQuickfix()` is now `commandt#private#Quickfix()`\n  - `CommandTRefresh()` is now `commandt#private#Refresh()`\n  - `CommandTSelectNext()` is now `commandt#private#SelectNext()`\n  - `CommandTSelectPrev()` is now `commandt#private#SelectPrev()`\n  - `CommandTToggleFocus()` is now `commandt#private#ToggleFocus()`\n- add |g:CommandTRecursiveMatch| option\n- stop distribution as a vimball in favor of a zip archive\n- don't clobber |alternate-file| name when opening Command-T match listing\n  (patch from Jerome Castaneda)\n- add |g:CommandTCursorColor| option\n- expose mappings for |:CommandT| and |:CommandTBuffer| using `<Plug>`\n  mappings |<Plug>(CommandT)| and |<Plug>(CommandT)|\n- add `<Leader>j` mapping to |:CommandTJump|, via |<Plug>(CommandTJump)|\n  (defined only if no pre-existing mapping exists)\n","package":"command-t-2.0.zip","4":"command-t-2.0.zip","src_id":"23834","5":"23834","creation_date":"1451331219","6":"1451331219"},{"0":"3025","vim_version":"7.0","1":"7.0","script_version":"1.13","2":"1.13","version_comment":"- avoid \"W10: Warning: Changing a readonly file\" when starting Vim in\n  read-only mode (ie. as `view` or with the `-R` option)\n- fix infinite loop on |<Tab>| (regression introduced in 1.12)\n","3":"- avoid \"W10: Warning: Changing a readonly file\" when starting Vim in\n  read-only mode (ie. as `view` or with the `-R` option)\n- fix infinite loop on |<Tab>| (regression introduced in 1.12)\n","package":"command-t-1.13.vba","4":"command-t-1.13.vba","src_id":"23238","5":"23238","creation_date":"1430334678","6":"1430334678"},{"0":"3025","vim_version":"7.0","1":"7.0","script_version":"1.12","2":"1.12","version_comment":"- add |:CommandTLoad| command\n- fix rare failure to restore cursor color after closing Command-T (patch from\n  Vlad Seghete)\n- doc fixes and updates (patches from Daniel Hahler and Nicholas T.)\n- make it possible to force reloading of the plug-in (patch from Daniel\n  Hahler)\n- add |g:CommandTEncoding| option, to work around rare encoding compatibility\n  issues\n- fix error restoring cursor highlights involving some configurations (patch\n  from Daniel Hahler)\n- skip set-up of |<Esc>| key mapping on rxvt terminals (patch from Daniel\n  Hahler)\n- add |g:CommandTGitScanSubmodules| option, which can be used to recursively\n  scan submodules when the \"git\" file scanner is used (patch from Ben Boeckel)\n- fix for not falling back to \"find\"-based scanner when a Watchman-related\n  error occurs\n","3":"- add |:CommandTLoad| command\n- fix rare failure to restore cursor color after closing Command-T (patch from\n  Vlad Seghete)\n- doc fixes and updates (patches from Daniel Hahler and Nicholas T.)\n- make it possible to force reloading of the plug-in (patch from Daniel\n  Hahler)\n- add |g:CommandTEncoding| option, to work around rare encoding compatibility\n  issues\n- fix error restoring cursor highlights involving some configurations (patch\n  from Daniel Hahler)\n- skip set-up of |<Esc>| key mapping on rxvt terminals (patch from Daniel\n  Hahler)\n- add |g:CommandTGitScanSubmodules| option, which can be used to recursively\n  scan submodules when the \"git\" file scanner is used (patch from Ben Boeckel)\n- fix for not falling back to \"find\"-based scanner when a Watchman-related\n  error occurs\n","package":"command-t-1.12.vba","4":"command-t-1.12.vba","src_id":"23156","5":"23156","creation_date":"1428629576","6":"1428629576"},{"0":"3025","vim_version":"7.0","1":"7.0","script_version":"1.11.4","2":"1.11.4","version_comment":"- fix infinite loop on Windows when |g:CommandTTraverseSCM| is set to a value\n  other than \"pwd\" (bug present since 1.11)\n- handle unwanted split edgecase when |'hidden'| is set, the current buffer is\n  modified, and it is visible in more than one window\n","3":"- fix infinite loop on Windows when |g:CommandTTraverseSCM| is set to a value\n  other than \"pwd\" (bug present since 1.11)\n- handle unwanted split edgecase when |'hidden'| is set, the current buffer is\n  modified, and it is visible in more than one window\n","package":"command-t-1.11.4.vba","4":"command-t-1.11.4.vba","src_id":"22602","5":"22602","creation_date":"1415120711","6":"1415120711"},{"0":"3025","vim_version":"7.0","1":"7.0","script_version":"1.11.3","2":"1.11.3","version_comment":"- ignore impromperly encoded filenames (patch from Sherzod Gapirov)\n- fix failure to update path when using |:cd| in conjunction with\n  |g:CommandTTraverseSCM| set to \"pwd\" (bug present since 1.11.2)\n","3":"- ignore impromperly encoded filenames (patch from Sherzod Gapirov)\n- fix failure to update path when using |:cd| in conjunction with\n  |g:CommandTTraverseSCM| set to \"pwd\" (bug present since 1.11.2)\n","package":"command-t-1.11.3.vba","4":"command-t-1.11.3.vba","src_id":"22514","5":"22514","creation_date":"1412988434","6":"1412988434"},{"0":"3025","vim_version":"7.0","1":"7.0","script_version":"1.11.2","2":"1.11.2","version_comment":"- fix error while using Command-T outside of an SCM repo (bug present since\n  1.11.1)\n","3":"- fix error while using Command-T outside of an SCM repo (bug present since\n  1.11.1)\n","package":"command-t-1.11.2.vba","4":"command-t-1.11.2.vba","src_id":"22400","5":"22400","creation_date":"1409600914","6":"1409600914"},{"0":"3025","vim_version":"7.0","1":"7.0","script_version":"1.11.1","2":"1.11.1","version_comment":"- compatibility fixes with Ruby 1.8.6 (patch from Emily Strickland)\n- compatibility fixes with Ruby 1.8.5\n- fix 'wildignore' being ignored (bug present since 1.11)\n- fix current working directory being ignored when |g:CommandTTraverseSCM| is\n  set to \"pwd\" (bug present since 1.11)\n- performance improvements\n","3":"- compatibility fixes with Ruby 1.8.6 (patch from Emily Strickland)\n- compatibility fixes with Ruby 1.8.5\n- fix 'wildignore' being ignored (bug present since 1.11)\n- fix current working directory being ignored when |g:CommandTTraverseSCM| is\n  set to \"pwd\" (bug present since 1.11)\n- performance improvements\n","package":"command-t-1.11.1.vba","4":"command-t-1.11.1.vba","src_id":"22379","5":"22379","creation_date":"1409323390","6":"1409323390"},{"0":"3025","vim_version":"7.0","1":"7.0","script_version":"1.11","2":"1.11","version_comment":"- improve edge-case handling in match results window code (patches from\n  Richard Feldman)\n- add \"git\" file scanner (patch from Patrick Hayes)\n- speed-up when 'wildignore' is unset (patch from Patrick Hayes)\n- add |g:CommandTTraverseSCM| setting which anchors Command-T's file finder to\n  the nearest SCM directory (based on patches from David Szotten and Ben\n  Osheroff)\n- add AppStream metadata (patch from V\u00c3\u00adt Ondruch)\n","3":"- improve edge-case handling in match results window code (patches from\n  Richard Feldman)\n- add \"git\" file scanner (patch from Patrick Hayes)\n- speed-up when 'wildignore' is unset (patch from Patrick Hayes)\n- add |g:CommandTTraverseSCM| setting which anchors Command-T's file finder to\n  the nearest SCM directory (based on patches from David Szotten and Ben\n  Osheroff)\n- add AppStream metadata (patch from V\u00c3\u00adt Ondruch)\n","package":"command-t-1.11.vba","4":"command-t-1.11.vba","src_id":"22330","5":"22330","creation_date":"1408113911","6":"1408113911"},{"0":"3025","vim_version":"7.0","1":"7.0","script_version":"1.10","2":"1.10","version_comment":"- improve tag finder performance by caching tag lists (patch from Artem\n  Nezvigin)\n- consider the |'autowriteall'| option when deciding whether to open a file in\n  a split\n- make selection acceptance commands configurable (patch from Ole Petter Bang)\n- add <C-w> mapping to delete previous word of the match prompt (patch from\n  Kevin Webster)\n- try harder to always clear status line after closing the match listing\n  (patch from Ton van den Heuvel)\n- don't allow MRU autocommands to produce errors when the extension has not\n  been compiled\n- add |g:CommandTIgnoreCase| and |g:CommandTSmartCase| options, providing\n  support for case-sensitive matching (based on patch from Jacek Wysocki)\n","3":"- improve tag finder performance by caching tag lists (patch from Artem\n  Nezvigin)\n- consider the |'autowriteall'| option when deciding whether to open a file in\n  a split\n- make selection acceptance commands configurable (patch from Ole Petter Bang)\n- add <C-w> mapping to delete previous word of the match prompt (patch from\n  Kevin Webster)\n- try harder to always clear status line after closing the match listing\n  (patch from Ton van den Heuvel)\n- don't allow MRU autocommands to produce errors when the extension has not\n  been compiled\n- add |g:CommandTIgnoreCase| and |g:CommandTSmartCase| options, providing\n  support for case-sensitive matching (based on patch from Jacek Wysocki)\n","package":"command-t-1.10.vba","4":"command-t-1.10.vba","src_id":"22208","5":"22208","creation_date":"1405473134","6":"1405473134"},{"0":"3025","vim_version":"7.0","1":"7.0","script_version":"1.9.1","2":"1.9.1","version_comment":"- include the file in the release vimball archive that was missing from the\n  1.9 release\n","3":"- include the file in the release vimball archive that was missing from the\n  1.9 release\n","package":"command-t-1.9.1.vba","4":"command-t-1.9.1.vba","src_id":"21965","5":"21965","creation_date":"1401461279","6":"1401461279"},{"0":"3025","vim_version":"7.0","1":"7.0","script_version":"1.9","2":"1.9","version_comment":"- improved startup time using Vim's autload mechanism (patch from Ross\n  Lagerwall)\n- added MRU (most-recently-used) buffer finder (patch from Ton van den Heuvel)\n- fixed edge case in matching algorithm which could cause spurious matches\n  with queries containing repeated characters\n- fixed slight positive bias in the match scoring algorithm's weighting of\n  matching characters based on distance from last match\n- tune memoization in match scoring algorithm, yield a more than 10% speed\n  boost\n","3":"- improved startup time using Vim's autload mechanism (patch from Ross\n  Lagerwall)\n- added MRU (most-recently-used) buffer finder (patch from Ton van den Heuvel)\n- fixed edge case in matching algorithm which could cause spurious matches\n  with queries containing repeated characters\n- fixed slight positive bias in the match scoring algorithm's weighting of\n  matching characters based on distance from last match\n- tune memoization in match scoring algorithm, yield a more than 10% speed\n  boost\n","package":"command-t-1.9.vba","4":"command-t-1.9.vba","src_id":"21938","5":"21938","creation_date":"1401042909","6":"1401042909"},{"0":"3025","vim_version":"7.0","1":"7.0","script_version":"1.8","2":"1.8","version_comment":"- taught Watchman file scanner to use the binary protocol instead of JSON,\n  roughly doubling its speed\n- build changes to accommodate MinGW (patch from Roland Puntaier)\n","3":"- taught Watchman file scanner to use the binary protocol instead of JSON,\n  roughly doubling its speed\n- build changes to accommodate MinGW (patch from Roland Puntaier)\n","package":"command-t-1.8.vba","4":"command-t-1.8.vba","src_id":"21699","5":"21699","creation_date":"1396314365","6":"1396314365"},{"0":"3025","vim_version":"7.0","1":"7.0","script_version":"1.7","2":"1.7","version_comment":"- added |g:CommandTInputDebounce|, which can be used to improve responsiveness\n  in large file hierarchies (based on patch from Yiding Jia)\n- added a potentially faster file scanner which uses the `find` executable\n  (based on patch from Yiding Jia)\n- added a file scanner that knows how to talk to Watchman\n  (https:\/\/github.com\/facebook\/watchman)\n- added |g:CommandTFileScanner|, which can be used to switch file scanners\n- fix processor count detection on some platforms (patch from Pavel Sergeev)\n","3":"- added |g:CommandTInputDebounce|, which can be used to improve responsiveness\n  in large file hierarchies (based on patch from Yiding Jia)\n- added a potentially faster file scanner which uses the `find` executable\n  (based on patch from Yiding Jia)\n- added a file scanner that knows how to talk to Watchman\n  (https:\/\/github.com\/facebook\/watchman)\n- added |g:CommandTFileScanner|, which can be used to switch file scanners\n- fix processor count detection on some platforms (patch from Pavel Sergeev)\n","package":"command-t-1.7.vba","4":"command-t-1.7.vba","src_id":"21586","5":"21586","creation_date":"1394432379","6":"1394432379"},{"0":"3025","vim_version":"7.0","1":"7.0","script_version":"1.6.1","2":"1.6.1","version_comment":"- defer processor count detection until runtime (makes it possible to sensibly\n  build Command-T on one machine and use it on another)\n","3":"- defer processor count detection until runtime (makes it possible to sensibly\n  build Command-T on one machine and use it on another)\n","package":"command-t-1.6.1.vba","4":"command-t-1.6.1.vba","src_id":"21225","5":"21225","creation_date":"1387773747","6":"1387773747"},{"0":"3025","vim_version":"7.0","1":"7.0","script_version":"1.6","2":"1.6","version_comment":"- on systems with POSIX threads (such as OS X and Linux), Command-T will use\n  threads to compute match results in parallel, resulting in a large speed\n  boost that is especially noticeable when navigating large projects\n","3":"- on systems with POSIX threads (such as OS X and Linux), Command-T will use\n  threads to compute match results in parallel, resulting in a large speed\n  boost that is especially noticeable when navigating large projects\n","package":"command-t-1.6.vba","4":"command-t-1.6.vba","src_id":"21199","5":"21199","creation_date":"1387195444","6":"1387195444"},{"0":"3025","vim_version":"7.0","1":"7.0","script_version":"1.5.1","2":"1.5.1","version_comment":"- exclude large benchmark fixture file from source exports (patch from V\u00c3\u00adt\n  Ondruch)\n","3":"- exclude large benchmark fixture file from source exports (patch from V\u00c3\u00adt\n  Ondruch)\n","package":"command-t-1.5.1.vba","4":"command-t-1.5.1.vba","src_id":"20835","5":"20835","creation_date":"1379990763","6":"1379990763"},{"0":"3025","vim_version":"7.0","1":"7.0","script_version":"1.5","2":"1.5","version_comment":"- don't scan \"pathological\" filesystem structures (ie. circular or\n  self-referential symlinks; patch from Marcus Brito)\n- gracefully handle files starting with \"+\" (patch from Ivan Ukhov)\n- switch default selection highlight color for better readability (suggestion\n  from Andr\u00c3\u00a9 Arko), but make it possible to configure via the\n  |g:CommandTHighlightColor| setting\n- added a mapping to take the current matches and put then in the quickfix\n  window\n- performance improvements, particularly noticeable with large file\n  hierarchies\n- added |g:CommandTWildIgnore| setting (patch from Paul Jolly)\n","3":"- don't scan \"pathological\" filesystem structures (ie. circular or\n  self-referential symlinks; patch from Marcus Brito)\n- gracefully handle files starting with \"+\" (patch from Ivan Ukhov)\n- switch default selection highlight color for better readability (suggestion\n  from Andr\u00c3\u00a9 Arko), but make it possible to configure via the\n  |g:CommandTHighlightColor| setting\n- added a mapping to take the current matches and put then in the quickfix\n  window\n- performance improvements, particularly noticeable with large file\n  hierarchies\n- added |g:CommandTWildIgnore| setting (patch from Paul Jolly)\n","package":"command-t-1.5.vba","4":"command-t-1.5.vba","src_id":"20818","5":"20818","creation_date":"1379488481","6":"1379488481"},{"0":"3025","vim_version":"7.0","1":"7.0","script_version":"1.4","2":"1.4","version_comment":"- added |:CommandTTag| command (patches from Noon Silk)\n- turn off |'colorcolumn'| and |'relativenumber'| in the match window (patch\n  from Jeff Kreeftmeijer)\n- documentation update (patch from Nicholas Alpi)\n- added |:CommandTMinHeight| option (patch from Nate Kane)\n- highlight (by underlining) matched characters in the match listing (requires\n  Vim to have been compiled with the +conceal feature, which is available in\n  Vim 7.3 or later; patch from Steven Moazami)\n- added the ability to flush the cache while the match window is open using\n  <C-f>\n","3":"- added |:CommandTTag| command (patches from Noon Silk)\n- turn off |'colorcolumn'| and |'relativenumber'| in the match window (patch\n  from Jeff Kreeftmeijer)\n- documentation update (patch from Nicholas Alpi)\n- added |:CommandTMinHeight| option (patch from Nate Kane)\n- highlight (by underlining) matched characters in the match listing (requires\n  Vim to have been compiled with the +conceal feature, which is available in\n  Vim 7.3 or later; patch from Steven Moazami)\n- added the ability to flush the cache while the match window is open using\n  <C-f>\n","package":"command-t-1.4.vba","4":"command-t-1.4.vba","src_id":"18167","5":"18167","creation_date":"1340178296","6":"1340178296"},{"0":"3025","vim_version":"7.0","1":"7.0","script_version":"1.3.1","2":"1.3.1","version_comment":"- fix jumplist navigation under Ruby 1.9.x (patch from Woody Peterson)\n","3":"- fix jumplist navigation under Ruby 1.9.x (patch from Woody Peterson)\n","package":"command-t-1.3.1.vba","4":"command-t-1.3.1.vba","src_id":"17084","5":"17084","creation_date":"1324232961","6":"1324232961"},{"0":"3025","vim_version":"7.0","1":"7.0","script_version":"1.3","2":"1.3","version_comment":"- added the option to maintain multiple caches when changing among\n  directories; see the accompanying |g:CommandTMaxCachedDirectories| setting\n- added the ability to navigate using the Vim jumplist (patch from Marian\n  Schubert)\n","3":"- added the option to maintain multiple caches when changing among\n  directories; see the accompanying |g:CommandTMaxCachedDirectories| setting\n- added the ability to navigate using the Vim jumplist (patch from Marian\n  Schubert)\n","package":"command-t-1.3.vba","4":"command-t-1.3.vba","src_id":"16987","5":"16987","creation_date":"1322461530","6":"1322461530"},{"0":"3025","vim_version":"7.0","1":"7.0","script_version":"1.2.1","2":"1.2.1","version_comment":"- Remove duplicate copy of the documentation that was causing \"Duplicate tag\"\n  errors\n- Mitigate issue with distracting blinking cursor in non-GUI versions of Vim\n  (patch from Steven Moazami)\n","3":"- Remove duplicate copy of the documentation that was causing \"Duplicate tag\"\n  errors\n- Mitigate issue with distracting blinking cursor in non-GUI versions of Vim\n  (patch from Steven Moazami)\n","package":"command-t-1.2.1.vba","4":"command-t-1.2.1.vba","src_id":"15560","5":"15560","creation_date":"1304231774","6":"1304231774"},{"0":"3025","vim_version":"7.0","1":"7.0","script_version":"1.2","2":"1.2","version_comment":"- added |g:CommandTMatchWindowReverse| option, to reverse the order of items\n  in the match listing (patch from Steven Moazami)\n","3":"- added |g:CommandTMatchWindowReverse| option, to reverse the order of items\n  in the match listing (patch from Steven Moazami)\n","package":"command-t-1.2.vba","4":"command-t-1.2.vba","src_id":"15549","5":"15549","creation_date":"1304147826","6":"1304147826"},{"0":"3025","vim_version":"7.0","1":"7.0","script_version":"1.1b2","2":"1.1b2","version_comment":"- fix a glitch in the release process; the plugin itself is unchanged since 1.1b\n","3":"- fix a glitch in the release process; the plugin itself is unchanged since 1.1b\n","package":"command-t-1.1b2.vba","4":"command-t-1.1b2.vba","src_id":"15305","5":"15305","creation_date":"1301200853","6":"1301200853"},{"0":"3025","vim_version":"7.0","1":"7.0","script_version":"1.1b","2":"1.1b","version_comment":"- add |:CommandTBuffer| command for quickly selecting among open buffers\n","3":"- add |:CommandTBuffer| command for quickly selecting among open buffers\n","package":"command-t-1.1b.vba","4":"command-t-1.1b.vba","src_id":"15304","5":"15304","creation_date":"1301200823","6":"1301200823"},{"0":"3025","vim_version":"7.2","1":"7.2","script_version":"1.0.1","2":"1.0.1","version_comment":"- work around bug when mapping |:CommandTFlush|, wherein the default mapping\r\n  for |:CommandT| would not be set up\r\n- clean up when leaving the Command-T buffer via unexpected means (such as\r\n  with <C-W k> or similar)","3":"- work around bug when mapping |:CommandTFlush|, wherein the default mapping\r\n  for |:CommandT| would not be set up\r\n- clean up when leaving the Command-T buffer via unexpected means (such as\r\n  with <C-W k> or similar)","package":"command-t-1.0.1.vba","4":"command-t-1.0.1.vba","src_id":"14688","5":"14688","creation_date":"1294262968","6":"1294262968"},{"0":"3025","vim_version":"7.2","1":"7.2","script_version":"1.0","2":"1.0","version_comment":"- make relative path simplification work on Windows","3":"- make relative path simplification work on Windows","package":"command-t-1.0.vba","4":"command-t-1.0.vba","src_id":"14383","5":"14383","creation_date":"1290789479","6":"1290789479"},{"0":"3025","vim_version":"7.2","1":"7.2","script_version":"1.0b","2":"1.0b","version_comment":"- work around platform-specific Vim 7.3 bug seen by some users (wherein\r\n  Vim always falsely reports to Ruby that the buffer numbers is 0)\r\n- re-use the buffer that is used to show the match listing, rather than\r\n  throwing it away and recreating it each time Command-T is shown; this\r\n  stops the buffer numbers from creeping up needlessly","3":"- work around platform-specific Vim 7.3 bug seen by some users (wherein\r\n  Vim always falsely reports to Ruby that the buffer numbers is 0)\r\n- re-use the buffer that is used to show the match listing, rather than\r\n  throwing it away and recreating it each time Command-T is shown; this\r\n  stops the buffer numbers from creeping up needlessly","package":"command-t-1.0b.vba","4":"command-t-1.0b.vba","src_id":"14186","5":"14186","creation_date":"1288972772","6":"1288972772"},{"0":"3025","vim_version":"7.2","1":"7.2","script_version":"0.8.1","2":"0.8.1","version_comment":"- fix mapping issues for users who have set |'notimeout'| (patch from Sung Pae)","3":"- fix mapping issues for users who have set |'notimeout'| (patch from Sung Pae)","package":"command-t-0.8.1.vba","4":"command-t-0.8.1.vba","src_id":"13820","5":"13820","creation_date":"1284452088","6":"1284452088"},{"0":"3025","vim_version":"7.2","1":"7.2","script_version":"0.8","2":"0.8","version_comment":"- overrides for the default mappings can now be lists of strings, allowing multiple mappings to be defined for any given action\r\n- <Leader>t mapping only set up if no other map for |:CommandT| exists (patch from Scott Bronson)\r\n- prevent folds from appearing in the match listing\r\n- tweaks to avoid the likelihood of \"Not enough room\" errors when trying to open files\r\n- watch out for \"nil\" windows when restoring window dimensions\r\n- optimizations (avoid some repeated downcasing)\r\n- move all Ruby files under the \"command-t\" subdirectory and avoid polluting the \"Vim\" module namespace","3":"- overrides for the default mappings can now be lists of strings, allowing multiple mappings to be defined for any given action\r\n- <Leader>t mapping only set up if no other map for |:CommandT| exists (patch from Scott Bronson)\r\n- prevent folds from appearing in the match listing\r\n- tweaks to avoid the likelihood of \"Not enough room\" errors when trying to open files\r\n- watch out for \"nil\" windows when restoring window dimensions\r\n- optimizations (avoid some repeated downcasing)\r\n- move all Ruby files under the \"command-t\" subdirectory and avoid polluting the \"Vim\" module namespace","package":"command-t-0.8.vba","4":"command-t-0.8.vba","src_id":"13622","5":"13622","creation_date":"1282200978","6":"1282200978"},{"0":"3025","vim_version":"7.0","1":"7.0","script_version":"0.8b","2":"0.8b","version_comment":"- large overhaul if the scoring algorithm to make the ordering of returned results more intuitive; given the scope of the changes and room for optimization of the new algorithm, this release is labelled as \"beta\"","3":"- large overhaul if the scoring algorithm to make the ordering of returned results more intuitive; given the scope of the changes and room for optimization of the new algorithm, this release is labelled as \"beta\"","package":"command-t-0.8b.vba","4":"command-t-0.8b.vba","src_id":"13322","5":"13322","creation_date":"1278866131","6":"1278866131"},{"0":"3025","vim_version":"7.0","1":"7.0","script_version":"0.7","2":"0.7","version_comment":"- handle more |'wildignore'| patterns by delegating to VIM's own |expand()| function; with this change it is now viable to exclude patterns such as 'vendor\/rails\/**' in addition to filename-only patterns like '*.o' and '.git' (patch from Mike Lundy)\r\n- always sort results alphabetically for empty search strings; this eliminates filesystem-specific variations (patch from Mike Lundy)","3":"- handle more |'wildignore'| patterns by delegating to VIM's own |expand()| function; with this change it is now viable to exclude patterns such as 'vendor\/rails\/**' in addition to filename-only patterns like '*.o' and '.git' (patch from Mike Lundy)\r\n- always sort results alphabetically for empty search strings; this eliminates filesystem-specific variations (patch from Mike Lundy)","package":"command-t-0.7.vba","4":"command-t-0.7.vba","src_id":"13157","5":"13157","creation_date":"1276164778","6":"1276164778"},{"0":"3025","vim_version":"7.0","1":"7.0","script_version":"0.6","2":"0.6","version_comment":"- |:CommandT| now accepts an optional parameter to specify the starting directory, temporarily overriding the usual default of VIM's |:pwd|\r\n- fix truncated paths when operating from root directory","3":"- |:CommandT| now accepts an optional parameter to specify the starting directory, temporarily overriding the usual default of VIM's |:pwd|\r\n- fix truncated paths when operating from root directory","package":"command-t-0.6.vba","4":"command-t-0.6.vba","src_id":"12914","5":"12914","creation_date":"1272523808","6":"1272523808"},{"0":"3025","vim_version":"7.0","1":"7.0","script_version":"0.5.1","2":"0.5.1","version_comment":"- fix for Ruby 1.9 compatibility regression introduced in 0.5\r\n- documentation enhancements, specifically targetted at Windows users","3":"- fix for Ruby 1.9 compatibility regression introduced in 0.5\r\n- documentation enhancements, specifically targetted at Windows users","package":"command-t-0.5.1.vba","4":"command-t-0.5.1.vba","src_id":"12813","5":"12813","creation_date":"1271011087","6":"1271011087"},{"0":"3025","vim_version":"7.0","1":"7.0","script_version":"0.5","2":"0.5","version_comment":"- |:CommandTFlush| now re-evaluates settings, allowing changes made via |:let| to be picked up without having to restart VIM\r\n- fix premature abort when scanning very deep directory hierarchies\r\n- remove broken |<Esc>| key mapping on vt100 and xterm terminals\r\n- provide settings for overriding default mappings\r\n- minor performance optimization","3":"- |:CommandTFlush| now re-evaluates settings, allowing changes made via |:let| to be picked up without having to restart VIM\r\n- fix premature abort when scanning very deep directory hierarchies\r\n- remove broken |<Esc>| key mapping on vt100 and xterm terminals\r\n- provide settings for overriding default mappings\r\n- minor performance optimization","package":"command-t.vba","4":"command-t.vba","src_id":"12780","5":"12780","creation_date":"1270330996","6":"1270330996"},{"0":"3025","vim_version":"7.0","1":"7.0","script_version":"0.4","2":"0.4","version_comment":"- add |g:CommandTMatchWindowAtTop| setting (patch from Zak Johnson)\r\n- documentation fixes and enhancements\r\n- internal refactoring and simplification","3":"- add |g:CommandTMatchWindowAtTop| setting (patch from Zak Johnson)\r\n- documentation fixes and enhancements\r\n- internal refactoring and simplification","package":"command-t.vba","4":"command-t.vba","src_id":"12715","5":"12715","creation_date":"1269701619","6":"1269701619"},{"0":"3025","vim_version":"7.0","1":"7.0","script_version":"0.3","2":"0.3","version_comment":"- add |g:CommandTMaxHeight| setting for controlling the maximum height of the match window (patch from Lucas de Vries)\r\n- fix bug where |'list'| setting might be inappropriately set after dismissing Command-T\r\n- compatibility fix for different behaviour of \"autoload\" under Ruby 1.9.1\r\n- avoid \"highlight group not found\" warning when run under a version of VIM that does not have syntax highlighting support\r\n- open in split when opening normally would fail due to |'hidden'| and |'modified'| values\r\n","3":"- add |g:CommandTMaxHeight| setting for controlling the maximum height of the match window (patch from Lucas de Vries)\r\n- fix bug where |'list'| setting might be inappropriately set after dismissing Command-T\r\n- compatibility fix for different behaviour of \"autoload\" under Ruby 1.9.1\r\n- avoid \"highlight group not found\" warning when run under a version of VIM that does not have syntax highlighting support\r\n- open in split when opening normally would fail due to |'hidden'| and |'modified'| values\r\n","package":"command-t.vba","4":"command-t.vba","src_id":"12701","5":"12701","creation_date":"1269471117","6":"1269471117"},{"0":"3025","vim_version":"7.0","1":"7.0","script_version":"0.2","2":"0.2","version_comment":"- compatibility fixes for compilation under Ruby 1.9 series\r\n- compatibility fixes for compilation under Ruby 1.8.5\r\n- compatibility fixes for Windows and other non-UNIX platforms\r\n- suppress \"mapping already exists\" message if <Leader>t mapping is already defined when plug-in is loaded\r\n- exclude paths based on |'wildignore'| setting rather than a hardcoded regular expression","3":"- compatibility fixes for compilation under Ruby 1.9 series\r\n- compatibility fixes for compilation under Ruby 1.8.5\r\n- compatibility fixes for Windows and other non-UNIX platforms\r\n- suppress \"mapping already exists\" message if <Leader>t mapping is already defined when plug-in is loaded\r\n- exclude paths based on |'wildignore'| setting rather than a hardcoded regular expression","package":"command-t.vba","4":"command-t.vba","src_id":"12693","5":"12693","creation_date":"1269377087","6":"1269377087"},{"0":"3025","vim_version":"7.2","1":"7.2","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"command-t.vba","4":"command-t.vba","src_id":"12679","5":"12679","creation_date":"1269275928","6":"1269275928"}]},"3024":{"script_id":"3024","0":"3024","script_name":"vimake","1":"vimake","script_type":"color scheme","2":"color scheme","summary":"Vimake is a programming aid written in C++ for Linux","3":"Vimake is a programming aid written in C++ for Linux","description":"Ever wanted to edit\/compile\/assemble\/link and debug, then run the completed program all inside one Vim or Gvim editing session. With Vimake you can do this and much more, no need to write Makefiles, no need to exit vim to test your programs, it can all be done using just a few function keys.\r\nVimake is a programming aid which can build files in C, C++, as(Gas) & Nasm This allows single or mixed language programs to be built at the touch of a  key. You can also write, test and run bash, perl, ruby, and python scripts all\r\nwhilst in a normal Vim or Gvim session. Used with Vim\\'s QuickFix function it turns Vim into a powerful programming environment.\r\n~    ","4":"Ever wanted to edit\/compile\/assemble\/link and debug, then run the completed program all inside one Vim or Gvim editing session. With Vimake you can do this and much more, no need to write Makefiles, no need to exit vim to test your programs, it can all be done using just a few function keys.\r\nVimake is a programming aid which can build files in C, C++, as(Gas) & Nasm This allows single or mixed language programs to be built at the touch of a  key. You can also write, test and run bash, perl, ruby, and python scripts all\r\nwhilst in a normal Vim or Gvim session. Used with Vim\\'s QuickFix function it turns Vim into a powerful programming environment.\r\n~    ","install_details":"copy  the package to your home directory then run\r\ntar -zxvf vimake-1.12.tar.gz.\r\nChange directory to the doc sub-dir of the package then\r\nuse \\\"install.html\\\" for detailed installation instructions.\r\nvimake package contains a demonstration and detailed tutorial.","5":"copy  the package to your home directory then run\r\ntar -zxvf vimake-1.12.tar.gz.\r\nChange directory to the doc sub-dir of the package then\r\nuse \\\"install.html\\\" for detailed installation instructions.\r\nvimake package contains a demonstration and detailed tutorial.","first_name":"michael","6":"michael","last_name":"lear","7":"lear","releases":[{"0":"3024","vim_version":"7.0","1":"7.0","script_version":"1-18","2":"1-18","version_comment":"GTKMM has been added to the list of programs which vimake can build without the need\r\nof a Makefile. This allows the gtkmm demonstration package to be built as separate\r\nstand alone programs. The GUI IDE has now been re-written as a vim plug-in, using gtkmm\r\nprograms to display toggle key messages. The tutorial has been updated to include all of\r\nthe new features.\r\n\r\nCopy the vimake-1.18.tar.gz package to your home directory.\r\nThen use the following commands to build and install.\r\n      tar -zxvf vimake-1.18.tar.gz\r\n      cd ~\/vimake-1.18\r\n      .\/configure\r\n      make install\r\n\r\nThen change to the doc sub directory and run Tutorial.html This contains full Installation-\r\nConfiguration and a Tutorial on using Vimake in Vim, Gvim and the GUI.\r\n","3":"GTKMM has been added to the list of programs which vimake can build without the need\r\nof a Makefile. This allows the gtkmm demonstration package to be built as separate\r\nstand alone programs. The GUI IDE has now been re-written as a vim plug-in, using gtkmm\r\nprograms to display toggle key messages. The tutorial has been updated to include all of\r\nthe new features.\r\n\r\nCopy the vimake-1.18.tar.gz package to your home directory.\r\nThen use the following commands to build and install.\r\n      tar -zxvf vimake-1.18.tar.gz\r\n      cd ~\/vimake-1.18\r\n      .\/configure\r\n      make install\r\n\r\nThen change to the doc sub directory and run Tutorial.html This contains full Installation-\r\nConfiguration and a Tutorial on using Vimake in Vim, Gvim and the GUI.\r\n","package":"vimake-1.18.tar.gz","4":"vimake-1.18.tar.gz","src_id":"15501","5":"15501","creation_date":"1303450959","6":"1303450959"},{"0":"3024","vim_version":"7.0","1":"7.0","script_version":"1.15","2":"1.15","version_comment":"Fixed BUG where viclean removed any executable shell scripts from the project dir. This was because stat\r\nreturns true on all executable files. Added further test to skip all exectable shell scripts.\r\nReplaced incorrect version of utils.cc with latest version.\r\nA full installation guide  and tutorial is included in the doc directory. To build this version copy the package to your home directory then run: tar zxvf vimake-1.15.tar.gz.\r\n","3":"Fixed BUG where viclean removed any executable shell scripts from the project dir. This was because stat\r\nreturns true on all executable files. Added further test to skip all exectable shell scripts.\r\nReplaced incorrect version of utils.cc with latest version.\r\nA full installation guide  and tutorial is included in the doc directory. To build this version copy the package to your home directory then run: tar zxvf vimake-1.15.tar.gz.\r\n","package":"vimake-1.15.tar.gz","4":"vimake-1.15.tar.gz","src_id":"14290","5":"14290","creation_date":"1290027120","6":"1290027120"},{"0":"3024","vim_version":"7.0","1":"7.0","script_version":"1.14","2":"1.14","version_comment":"Vimake,    compile-assemble-link-run-debug a file or files in a vim session with hot keys.\r\nThis version of vimake has many improvements over the earlier version. It now can load,build and run\r\nin a vim session lua. It can automatically switch the ddd front end debugger to load the following\r\nfile types. Asm, C\/CPP, Bash, Python and Perl. It can also run the ruby debugger and the other script languages  in a vim shell. A full installation guide  and tutorial is included in the doc directory. To build this version copy the package to your home directory then run: tar zxvf vimake-1.14.tar.gz.\r\nChange directory to $HOME\/vimake-1.14 and follow the README instructions.\r\n","3":"Vimake,    compile-assemble-link-run-debug a file or files in a vim session with hot keys.\r\nThis version of vimake has many improvements over the earlier version. It now can load,build and run\r\nin a vim session lua. It can automatically switch the ddd front end debugger to load the following\r\nfile types. Asm, C\/CPP, Bash, Python and Perl. It can also run the ruby debugger and the other script languages  in a vim shell. A full installation guide  and tutorial is included in the doc directory. To build this version copy the package to your home directory then run: tar zxvf vimake-1.14.tar.gz.\r\nChange directory to $HOME\/vimake-1.14 and follow the README instructions.\r\n","package":"vimake-1.14.tar.gz","4":"vimake-1.14.tar.gz","src_id":"14271","5":"14271","creation_date":"1289852379","6":"1289852379"},{"0":"3024","vim_version":"6.0","1":"6.0","script_version":"1-12","2":"1-12","version_comment":"Initial upload","3":"Initial upload","package":"vimake-1.12.tar.gz","4":"vimake-1.12.tar.gz","src_id":"12670","5":"12670","creation_date":"1269114766","6":"1269114766"}]},"3023":{"script_id":"3023","0":"3023","script_name":"tslime.vim","1":"tslime.vim","script_type":"utility","2":"utility","summary":"Send text from vim to a running tmux session","3":"Send text from vim to a running tmux session","description":"Simple script which allow you to send portion of a buffer to a running tmux session.\r\n\r\nBased on http:\/\/technotales.wordpress.com\/2007\/10\/03\/like-slime-for-vim\/ which use screen instead of tmux. \r\n\r\nNote:\r\nHaving some problem uploading a new version here. You can find a more up-to-date version on github: http:\/\/github.com\/kikijump\/tslime.vim\r\nIf you're using tmux >=1.5, go fetch tslime from there.\r\n\r\n_How to use this script:_ \r\n  - Considering you have a running Ruby\/Python\/Clojure\/Whatever interpreter in    window 0 of a tmux session named 'my-session'. \r\n\r\n  - In vim, select a region in visual mode and press <C-c><C-c>. \r\n\r\n  - You will be prompt to enter the session name.  You can type the name of the session directly, in this case 'my-session', or you can press <tab> to  cycle through all the tmux sessions that are currently running. \r\n\r\n  - Next, you will be prompt for the window number, in this case 0. Like for session name, completion is available. \r\n\r\n  - When you'll press enter, the text you selected will be send to your  interpreter.","4":"Simple script which allow you to send portion of a buffer to a running tmux session.\r\n\r\nBased on http:\/\/technotales.wordpress.com\/2007\/10\/03\/like-slime-for-vim\/ which use screen instead of tmux. \r\n\r\nNote:\r\nHaving some problem uploading a new version here. You can find a more up-to-date version on github: http:\/\/github.com\/kikijump\/tslime.vim\r\nIf you're using tmux >=1.5, go fetch tslime from there.\r\n\r\n_How to use this script:_ \r\n  - Considering you have a running Ruby\/Python\/Clojure\/Whatever interpreter in    window 0 of a tmux session named 'my-session'. \r\n\r\n  - In vim, select a region in visual mode and press <C-c><C-c>. \r\n\r\n  - You will be prompt to enter the session name.  You can type the name of the session directly, in this case 'my-session', or you can press <tab> to  cycle through all the tmux sessions that are currently running. \r\n\r\n  - Next, you will be prompt for the window number, in this case 0. Like for session name, completion is available. \r\n\r\n  - When you'll press enter, the text you selected will be send to your  interpreter.","install_details":"","5":"","first_name":"C.","6":"C.","last_name":"Coutinho","7":"Coutinho","releases":[{"0":"3023","vim_version":"7.0","1":"7.0","script_version":"0.2","2":"0.2","version_comment":"Works with tmux (>=1.3)\r\nYou can indicate which pane to paste text to.\r\n\r\nFor tmux (<1.3), you should use version 0.1 of tslime.vim","3":"Works with tmux (>=1.3)\r\nYou can indicate which pane to paste text to.\r\n\r\nFor tmux (<1.3), you should use version 0.1 of tslime.vim","package":"tslime.vim","4":"tslime.vim","src_id":"14151","5":"14151","creation_date":"1288457788","6":"1288457788"},{"0":"3023","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"tslime.vim","4":"tslime.vim","src_id":"12664","5":"12664","creation_date":"1268999505","6":"1268999505"}]},"3022":{"script_id":"3022","0":"3022","script_name":"Bookmarking","1":"Bookmarking","script_type":"utility","2":"utility","summary":"A bookmaking facility for Vim for marking points of interest.","3":"A bookmaking facility for Vim for marking points of interest.","description":"Add a bookmarking feature to Vim that allows lines of interest to be marked. While similar to marks, you don't need to assign a bookmark to a mark key, instead an infinite number of bookmarks can be created and then jumped through in sequential order (by line number) with no strain on your memory. This is great to use when you are browsing through some source code for the first time and need to mark out places of interest to learn how it works. It lets you just worry about the code and not have to remember which marks you have or haven't used.\r\n\r\nUsage:\r\n  * <F3> \/ :ToggleBookmark - Set a bookmark at the current location.\r\n  * <F4> \/ :PreviousBookmark - Jump to the closest bookmark earlier that the current location in the file.\r\n  * <F5> \/ :NextBookmark - Jump to the closest bookmark later than the current location in the file.\r\n\r\nYou can follow the development on Github at http:\/\/github.com\/dterei\/VimBookmarking","4":"Add a bookmarking feature to Vim that allows lines of interest to be marked. While similar to marks, you don't need to assign a bookmark to a mark key, instead an infinite number of bookmarks can be created and then jumped through in sequential order (by line number) with no strain on your memory. This is great to use when you are browsing through some source code for the first time and need to mark out places of interest to learn how it works. It lets you just worry about the code and not have to remember which marks you have or haven't used.\r\n\r\nUsage:\r\n  * <F3> \/ :ToggleBookmark - Set a bookmark at the current location.\r\n  * <F4> \/ :PreviousBookmark - Jump to the closest bookmark earlier that the current location in the file.\r\n  * <F5> \/ :NextBookmark - Jump to the closest bookmark later than the current location in the file.\r\n\r\nYou can follow the development on Github at http:\/\/github.com\/dterei\/VimBookmarking","install_details":"Normal vimball installation process:\r\n\r\n1. Download the vimball 'bookmarking.vba'\r\n2. $ vim bookmarking.vba\r\n3. (In Vim) ': source %'\r\n4. (In Vim) ': q'\r\n","5":"Normal vimball installation process:\r\n\r\n1. Download the vimball 'bookmarking.vba'\r\n2. $ vim bookmarking.vba\r\n3. (In Vim) ': source %'\r\n4. (In Vim) ': q'\r\n","first_name":"David","6":"David","last_name":"Terei","7":"Terei","releases":[{"0":"3022","vim_version":"7.0","1":"7.0","script_version":"2.3","2":"2.3","version_comment":"Fix bookmarking to work when no signs feature present in vim","3":"Fix bookmarking to work when no signs feature present in vim","package":"bookmarking.vba","4":"bookmarking.vba","src_id":"17097","5":"17097","creation_date":"1324496385","6":"1324496385"},{"0":"3022","vim_version":"7.0","1":"7.0","script_version":"2.2","2":"2.2","version_comment":"Add a new global variable, 'g:bookmarking_menu' to control if the menu is created or not.","3":"Add a new global variable, 'g:bookmarking_menu' to control if the menu is created or not.","package":"bookmarking.vba","4":"bookmarking.vba","src_id":"16885","5":"16885","creation_date":"1321485508","6":"1321485508"},{"0":"3022","vim_version":"7.0","1":"7.0","script_version":"2.1","2":"2.1","version_comment":"Fixed a bug that caused the plugin to fail for files without a '.' in their names","3":"Fixed a bug that caused the plugin to fail for files without a '.' in their names","package":"bookmarking.vba","4":"bookmarking.vba","src_id":"13302","5":"13302","creation_date":"1278527019","6":"1278527019"},{"0":"3022","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial Release","3":"Initial Release","package":"bookmarking.vba","4":"bookmarking.vba","src_id":"12662","5":"12662","creation_date":"1268983921","6":"1268983921"}]},"3021":{"script_id":"3021","0":"3021","script_name":"Find files","1":"Find files","script_type":"utility","2":"utility","summary":"Easy find & open using find application.","3":"Easy find & open using find application.","description":"findfiles.vim is simple script that helps with finding files, using `find . -iname`\r\n\r\nUsage:\r\n * type  `:Find <file_name> [<find_params> ]` to show list of files that matches\r\n * type `\\Find` to call `:Find` with `*<cword>*` as search string\r\n\r\nResults window:\r\n * select any file any press <Return> to open it\r\n * press 'o' to open selected file and close results window\r\n * press 'q' to close results window\r\n\r\n\r\nScreenshots: \r\n * http:\/\/wstaw.org\/m\/2010\/03\/17\/2010-03-17-220325_688x314_scrot.png\r\n * http:\/\/wstaw.org\/m\/2010\/03\/20\/2010-03-20-094909_661x285_scrot.png","4":"findfiles.vim is simple script that helps with finding files, using `find . -iname`\r\n\r\nUsage:\r\n * type  `:Find <file_name> [<find_params> ]` to show list of files that matches\r\n * type `\\Find` to call `:Find` with `*<cword>*` as search string\r\n\r\nResults window:\r\n * select any file any press <Return> to open it\r\n * press 'o' to open selected file and close results window\r\n * press 'q' to close results window\r\n\r\n\r\nScreenshots: \r\n * http:\/\/wstaw.org\/m\/2010\/03\/17\/2010-03-17-220325_688x314_scrot.png\r\n * http:\/\/wstaw.org\/m\/2010\/03\/20\/2010-03-20-094909_661x285_scrot.png","install_details":"Download and save in $HOME\/.vim\/plugins\/","5":"Download and save in $HOME\/.vim\/plugins\/","first_name":"Piotr","6":"Piotr","last_name":"Husiatynski","7":"Husiatynski","releases":[{"0":"3021","vim_version":"6.0","1":"6.0","script_version":"1.02","2":"1.02","version_comment":"Optional arguments are now allowed","3":"Optional arguments are now allowed","package":"findfiles.vim","4":"findfiles.vim","src_id":"12657","5":"12657","creation_date":"1268936218","6":"1268936218"},{"0":"3021","vim_version":"6.0","1":"6.0","script_version":"1.01","2":"1.01","version_comment":"New features.","3":"New features.","package":"findfiles.vim","4":"findfiles.vim","src_id":"12656","5":"12656","creation_date":"1268933023","6":"1268933023"},{"0":"3021","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"findfiles.vim","4":"findfiles.vim","src_id":"12650","5":"12650","creation_date":"1268859275","6":"1268859275"}]},"3020":{"script_id":"3020","0":"3020","script_name":"EasyOpts","1":"EasyOpts","script_type":"utility","2":"utility","summary":"Help other scripts in the option management","3":"Help other scripts in the option management","description":"EasyOpts simplify the options management to other plugins through some facilities:\r\n - allow the plugin to initialize all the user-exposed variables to a predefined value (if not already specified).\r\n - allow the user to change the option values through a simple menu\r\n - check if the values specified by the user are correct\r\n\r\nFull documentation about how to use the plugin is provided in the help file and is demoed through some examples","4":"EasyOpts simplify the options management to other plugins through some facilities:\r\n - allow the plugin to initialize all the user-exposed variables to a predefined value (if not already specified).\r\n - allow the user to change the option values through a simple menu\r\n - check if the values specified by the user are correct\r\n\r\nFull documentation about how to use the plugin is provided in the help file and is demoed through some examples","install_details":"Copy the content of the doc\/ and plugins\/ directory in their equivalent inside the .vim folder.\r\n","5":"Copy the content of the doc\/ and plugins\/ directory in their equivalent inside the .vim folder.\r\n","first_name":"Andrea","6":"Andrea","last_name":"Carron","7":"Carron","releases":[{"0":"3020","vim_version":"7.0","1":"7.0","script_version":"0.2","2":"0.2","version_comment":"The user now could use the EasyOpts Menu to save the options or restore them to the default value. Fixed a bug in the EasyOpts_Menu_Close() functions.","3":"The user now could use the EasyOpts Menu to save the options or restore them to the default value. Fixed a bug in the EasyOpts_Menu_Close() functions.","package":"easyopts.tar.gz","4":"easyopts.tar.gz","src_id":"12794","5":"12794","creation_date":"1270644790","6":"1270644790"},{"0":"3020","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"easyopts.tar.gz","4":"easyopts.tar.gz","src_id":"12648","5":"12648","creation_date":"1268841850","6":"1268841850"}]},"3019":{"script_id":"3019","0":"3019","script_name":"spin.vim","1":"spin.vim","script_type":"syntax","2":"syntax","summary":"Syntax file for Parallax Spin language","3":"Syntax file for Parallax Spin language","description":"This is a syntax file for the Spin language, designed by Parallax for the Propeller microcontroller (\"http:\/\/www.parallax.com\/tabid\/407\/Default.aspx\"). Now there's cross-platform command line tools to upload your Spin programs to the Propeller, so you don't need the Propeller IDE (and hence, Windows) to use it. \r\n\r\nI based this syntax file on the syntax file for the Python language, since the languages have certain similarities.","4":"This is a syntax file for the Spin language, designed by Parallax for the Propeller microcontroller (\"http:\/\/www.parallax.com\/tabid\/407\/Default.aspx\"). Now there's cross-platform command line tools to upload your Spin programs to the Propeller, so you don't need the Propeller IDE (and hence, Windows) to use it. \r\n\r\nI based this syntax file on the syntax file for the Python language, since the languages have certain similarities.","install_details":"The easiest way is to put spin.vim in your .vim\/syntax folder and add something like the following to your .vimrc:\r\nau BufRead,BufNewFile *.spin set filetype=spin\r\nau! Syntax spin source $HOME\/.vim\/syntax\/spin.vim","5":"The easiest way is to put spin.vim in your .vim\/syntax folder and add something like the following to your .vimrc:\r\nau BufRead,BufNewFile *.spin set filetype=spin\r\nau! Syntax spin source $HOME\/.vim\/syntax\/spin.vim","first_name":"Daniel","6":"Daniel","last_name":"Maturana","7":"Maturana","releases":[{"0":"3019","vim_version":"6.0","1":"6.0","script_version":"0.2","2":"0.2","version_comment":"Incorporated fix for comment problem with brackets that open and close on the same line, by Gordon Child.","3":"Incorporated fix for comment problem with brackets that open and close on the same line, by Gordon Child.","package":"spin.vim","4":"spin.vim","src_id":"14662","5":"14662","creation_date":"1293769488","6":"1293769488"},{"0":"3019","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"spin.vim","4":"spin.vim","src_id":"12642","5":"12642","creation_date":"1268804410","6":"1268804410"}]},"3018":{"script_id":"3018","0":"3018","script_name":"vim-addon-completion","1":"vim-addon-completion","script_type":"utility","2":"utility","summary":"select and cycle completion function","3":"select and cycle completion function","description":"This plugin defines a global list of available completion functions so that you can switch completion functions fast.\r\n\r\nIf you write a plugin which provides completion functions be kind to your users and use this plugin to never override the choice of a user.\r\n\r\nYou can register your completion function to a global list optionally specifying a filetype scope such as \"xml\".\r\n\r\nWhen you start completion using <c-x><c-o> you'll be asked which completion function should be used if there are more than one available. This <c-x><c-o> mapping will set 'omnicomplete' by default.\r\ncompletefunc will be set to the next completefunc automatically (if it wasn't set by you).\r\n\r\nIf you jump to a different buffer your last choice will be remembered depending on filetype.\r\n\r\nOf course setting a default function can still be annoying. Thus you can just set it in a ftplugin file this way:\r\nCFComplete haxe#CompleteClassName\r\n\r\nOf course there are mappings to cycle through completion functions as well\r\n\r\nHave a look at this description:\r\nhttp:\/\/github.com\/MarcWeber\/vim-addon-completion\/blob\/master\/doc\/vim-addon-completion.txt","4":"This plugin defines a global list of available completion functions so that you can switch completion functions fast.\r\n\r\nIf you write a plugin which provides completion functions be kind to your users and use this plugin to never override the choice of a user.\r\n\r\nYou can register your completion function to a global list optionally specifying a filetype scope such as \"xml\".\r\n\r\nWhen you start completion using <c-x><c-o> you'll be asked which completion function should be used if there are more than one available. This <c-x><c-o> mapping will set 'omnicomplete' by default.\r\ncompletefunc will be set to the next completefunc automatically (if it wasn't set by you).\r\n\r\nIf you jump to a different buffer your last choice will be remembered depending on filetype.\r\n\r\nOf course setting a default function can still be annoying. Thus you can just set it in a ftplugin file this way:\r\nCFComplete haxe#CompleteClassName\r\n\r\nOf course there are mappings to cycle through completion functions as well\r\n\r\nHave a look at this description:\r\nhttp:\/\/github.com\/MarcWeber\/vim-addon-completion\/blob\/master\/doc\/vim-addon-completion.txt","install_details":"Recommended way of installation: \r\nhttp:\/\/www.vim.org\/scripts\/script.php?script_id=2905 \r\n\r\nIf you install this plugin manually you also have to get the dependencies listed in the info file manually (tlib)\r\n\r\nEnjoy and report bugs, please!","5":"Recommended way of installation: \r\nhttp:\/\/www.vim.org\/scripts\/script.php?script_id=2905 \r\n\r\nIf you install this plugin manually you also have to get the dependencies listed in the info file manually (tlib)\r\n\r\nEnjoy and report bugs, please!","first_name":"Marc","6":"Marc","last_name":"Weber","7":"Weber","releases":[{"0":"3018","vim_version":"7.0","1":"7.0","script_version":"0.2.1","2":"0.2.1","version_comment":"bug fix: use setlocal instead of set","3":"bug fix: use setlocal instead of set","package":"vim-addon-completion-0.2.1.zip","4":"vim-addon-completion-0.2.1.zip","src_id":"13701","5":"13701","creation_date":"1283009922","6":"1283009922"},{"0":"3018","vim_version":"7.0","1":"7.0","script_version":"0.2","2":"0.2","version_comment":"adding CamelCase matching implementation (used by vim-dev-plugin and vim-addon-ocaml)","3":"adding CamelCase matching implementation (used by vim-dev-plugin and vim-addon-ocaml)","package":"vim-addon-completion-0.2.zip","4":"vim-addon-completion-0.2.zip","src_id":"13573","5":"13573","creation_date":"1281831833","6":"1281831833"},{"0":"3018","vim_version":"7.2","1":"7.2","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"vim-addon-completion.zip","4":"vim-addon-completion.zip","src_id":"12635","5":"12635","creation_date":"1268699623","6":"1268699623"}]},"3017":{"script_id":"3017","0":"3017","script_name":"Cppcheck compiler","1":"Cppcheck compiler","script_type":"utility","2":"utility","summary":"Compiler definition for cppcheck","3":"Compiler definition for cppcheck","description":"Compiler definition to  use cppcheck static code checker from vim.\r\n\r\nUse :comp cppcheck to enable it, then use :make to call it.","4":"Compiler definition to  use cppcheck static code checker from vim.\r\n\r\nUse :comp cppcheck to enable it, then use :make to call it.","install_details":"open the file and type \r\n:so %\r\nto install it.","5":"open the file and type \r\n:so %\r\nto install it.","first_name":"Vincent","6":"Vincent","last_name":"B","7":"B","releases":[{"0":"3017","vim_version":"7.2","1":"7.2","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"cppcheck.vba","4":"cppcheck.vba","src_id":"12628","5":"12628","creation_date":"1268577054","6":"1268577054"}]},"3016":{"script_id":"3016","0":"3016","script_name":"happy.vim","1":"happy.vim","script_type":"syntax","2":"syntax","summary":"syntax highlight for happy files","3":"syntax highlight for happy files","description":"Happy is a parser generator system for Haskell, similar to the tool `yacc' for C. This script is syntax file for happy files.","4":"Happy is a parser generator system for Haskell, similar to the tool `yacc' for C. This script is syntax file for happy files.","install_details":"Put happy.vim in your ~\/.vim\/syntax or in $VIMRUNTIME\/syntax. \r\nTo start using it while editing alex file you can use \r\n:set syntax happy \r\nor create\/edit script for file type detecting and applying this syntax rules.","5":"Put happy.vim in your ~\/.vim\/syntax or in $VIMRUNTIME\/syntax. \r\nTo start using it while editing alex file you can use \r\n:set syntax happy \r\nor create\/edit script for file type detecting and applying this syntax rules.","first_name":"Nickolay","6":"Nickolay","last_name":"Kudasov","7":"Kudasov","releases":[{"0":"3016","vim_version":"6.0","1":"6.0","script_version":"0.2","2":"0.2","version_comment":"' (apostrophe) is now regocnized when part of non-terminal\r\nhightlighting haskell directives\r\nhightlighting todos and fixmes in haskell comments","3":"' (apostrophe) is now regocnized when part of non-terminal\r\nhightlighting haskell directives\r\nhightlighting todos and fixmes in haskell comments","package":"happy.vim","4":"happy.vim","src_id":"12653","5":"12653","creation_date":"1268906450","6":"1268906450"},{"0":"3016","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"happy.vim","4":"happy.vim","src_id":"12624","5":"12624","creation_date":"1268497444","6":"1268497444"}]},"3015":{"script_id":"3015","0":"3015","script_name":"alex.vim","1":"alex.vim","script_type":"syntax","2":"syntax","summary":"syntax highlight for alex files","3":"syntax highlight for alex files","description":"Alex is a tool for generating lexical analysers in Haskell, given a description of the tokens to be recognised in the form of regular expressions. This script is syntax file for alex files.","4":"Alex is a tool for generating lexical analysers in Haskell, given a description of the tokens to be recognised in the form of regular expressions. This script is syntax file for alex files.","install_details":"Put alex.vim in your ~\/.vim\/syntax or in $VIMRUNTIME\/syntax.\r\nTo start using it while editing alex file you can use\r\n:set syntax alex\r\nor create\/edit script for file type detecting and applying this syntax rules.","5":"Put alex.vim in your ~\/.vim\/syntax or in $VIMRUNTIME\/syntax.\r\nTo start using it while editing alex file you can use\r\n:set syntax alex\r\nor create\/edit script for file type detecting and applying this syntax rules.","first_name":"Nickolay","6":"Nickolay","last_name":"Kudasov","7":"Kudasov","releases":[{"0":"3015","vim_version":"6.0","1":"6.0","script_version":"0.2","2":"0.2","version_comment":"'$' and '@' are now part of identifiers for macro definitions\r\nhaskell directives are highlighted\r\nhightlighting fixmes\r\nhightlighting todos and fixmes in haskell comments","3":"'$' and '@' are now part of identifiers for macro definitions\r\nhaskell directives are highlighted\r\nhightlighting fixmes\r\nhightlighting todos and fixmes in haskell comments","package":"alex.vim","4":"alex.vim","src_id":"12652","5":"12652","creation_date":"1268906095","6":"1268906095"},{"0":"3015","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"alex.vim","4":"alex.vim","src_id":"12623","5":"12623","creation_date":"1268497189","6":"1268497189"}]},"3014":{"script_id":"3014","0":"3014","script_name":"ColorX","1":"ColorX","script_type":"utility","2":"utility","summary":"A script that lets you insert hex color codes by using OS X's color picker","3":"A script that lets you insert hex color codes by using OS X's color picker","description":"This script lets you insert hex or RGB color codes directly into the buffer by using OS X's color picker. This can for example be useful for web developers who are editing their CSS files with Vim on OS X or similar tasks. Furthermore, when the cursor is over a hex color code like #ffffff, this is set as the starting color for the color picker.\r\n\r\n:ColorHEX or :ColorRGB will bring up the color picker. After a color has been selected the hex or RGB values will be inserted at the current position in the buffer.","4":"This script lets you insert hex or RGB color codes directly into the buffer by using OS X's color picker. This can for example be useful for web developers who are editing their CSS files with Vim on OS X or similar tasks. Furthermore, when the cursor is over a hex color code like #ffffff, this is set as the starting color for the color picker.\r\n\r\n:ColorHEX or :ColorRGB will bring up the color picker. After a color has been selected the hex or RGB values will be inserted at the current position in the buffer.","install_details":"Just copy the script into you plugins folder. Obviously the script will only work on OS X","5":"Just copy the script into you plugins folder. Obviously the script will only work on OS X","first_name":"Maximilian","6":"Maximilian","last_name":"Nickel","7":"Nickel","releases":[{"0":"3014","vim_version":"7.0","1":"7.0","script_version":"0.3","2":"0.3","version_comment":"Pick up hex color codes under the cursor and display them when the color choser opens","3":"Pick up hex color codes under the cursor and display them when the color choser opens","package":"colorx.vim","4":"colorx.vim","src_id":"13969","5":"13969","creation_date":"1285952465","6":"1285952465"},{"0":"3014","vim_version":"7.0","1":"7.0","script_version":"0.2","2":"0.2","version_comment":"Initial upload","3":"Initial upload","package":"colorx.vim","4":"colorx.vim","src_id":"12621","5":"12621","creation_date":"1268495236","6":"1268495236"}]},"3013":{"script_id":"3013","0":"3013","script_name":"tcommand","1":"tcommand","script_type":"utility","2":"utility","summary":"Select and execute a command or menu item from a list","3":"Select and execute a command or menu item from a list","description":"Also available via git: http:\/\/github.com\/tomtom\/tcommand_vim\r\n\r\nVIM plugins are cool but with time you forget about even useful \r\ncommands. This plugin provides a command (|:TCommand|) that lets you \r\nselect a command or menu item from a list (you can optionally display \r\nhelp on the currently hightlighted command) and then run it from the \r\ncommand line. It thus provides an alternative to the built-in \r\ncommand-line completion.\r\n","4":"Also available via git: http:\/\/github.com\/tomtom\/tcommand_vim\r\n\r\nVIM plugins are cool but with time you forget about even useful \r\ncommands. This plugin provides a command (|:TCommand|) that lets you \r\nselect a command or menu item from a list (you can optionally display \r\nhelp on the currently hightlighted command) and then run it from the \r\ncommand line. It thus provides an alternative to the built-in \r\ncommand-line completion.\r\n","install_details":"Edit the vba file and type: >\r\n\r\n    :so %\r\n\r\nSee :help vimball for details. If you have difficulties or use vim 7.0, \r\nplease make sure, you have the current version of vimball\r\n(vimscript #1502) installed or update your runtime.\r\n\r\nThis script requires tlib (vimscript #1863) to be installed.\r\n\r\n\r\nPost-Install~\r\n\r\nSuggested maps (to be set in your |vimrc| file): >\r\n\r\n    noremap <Leader>: :TCommand<cr>\r\n","5":"Edit the vba file and type: >\r\n\r\n    :so %\r\n\r\nSee :help vimball for details. If you have difficulties or use vim 7.0, \r\nplease make sure, you have the current version of vimball\r\n(vimscript #1502) installed or update your runtime.\r\n\r\nThis script requires tlib (vimscript #1863) to be installed.\r\n\r\n\r\nPost-Install~\r\n\r\nSuggested maps (to be set in your |vimrc| file): >\r\n\r\n    noremap <Leader>: :TCommand<cr>\r\n","first_name":"Tom","6":"Tom","last_name":"Link","7":"Link","releases":[{"0":"3013","vim_version":"7.0","1":"7.0","script_version":"0.03","2":"0.03","version_comment":"- s:FormatItem(): Items with comments had a wrong number of tabs (fixed by Sergio Nobre)\n- CollectCommands(): Only half of the commands were included in the list\n- The original view wasn't always properly restored\n- F1 (help on commands) didn't always work\nMD5 checksum: fbb7ffb5583d9a1c37eadfacb2970825","3":"- s:FormatItem(): Items with comments had a wrong number of tabs (fixed by Sergio Nobre)\n- CollectCommands(): Only half of the commands were included in the list\n- The original view wasn't always properly restored\n- F1 (help on commands) didn't always work\nMD5 checksum: fbb7ffb5583d9a1c37eadfacb2970825","package":"tcommand.vba","4":"tcommand.vba","src_id":"17409","5":"17409","creation_date":"1328725640","6":"1328725640"},{"0":"3013","vim_version":"7.0","1":"7.0","script_version":"0.2","2":"0.2","version_comment":"Please see http:\/\/github.com\/tomtom\/tcommand_vim\/commits\/master\/\nMD5 checksum: f36d1eadd726c4b39616c6dd9cef37d2","3":"Please see http:\/\/github.com\/tomtom\/tcommand_vim\/commits\/master\/\nMD5 checksum: f36d1eadd726c4b39616c6dd9cef37d2","package":"tcommand.vba","4":"tcommand.vba","src_id":"14162","5":"14162","creation_date":"1288626836","6":"1288626836"},{"0":"3013","vim_version":"7.2","1":"7.2","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"tcommand.vba","4":"tcommand.vba","src_id":"12616","5":"12616","creation_date":"1268461516","6":"1268461516"}]},"3012":{"script_id":"3012","0":"3012","script_name":"vspec","1":"vspec","script_type":"utility","2":"utility","summary":"Testing framework for Vim script","3":"Testing framework for Vim script","description":"*vspec* is a Vim library plugin to test Vim script.\n\n\nRequirements:\n- Vim 7.3 or later\n\nLatest version:\nhttp:\/\/github.com\/kana\/vim-vspec\n\nDocument in HTML format:\nhttp:\/\/kana.github.com\/config\/vim\/vspec.html","4":"*vspec* is a Vim library plugin to test Vim script.\n\n\nRequirements:\n- Vim 7.3 or later\n\nLatest version:\nhttp:\/\/github.com\/kana\/vim-vspec\n\nDocument in HTML format:\nhttp:\/\/kana.github.com\/config\/vim\/vspec.html","install_details":"...","5":"...","first_name":"Kana","6":"Kana","last_name":"Natsuno","7":"Natsuno","releases":[{"0":"3012","vim_version":"7.0","1":"7.0","script_version":"1.1.0","2":"1.1.0","version_comment":"- |:Expect-not|:\n  - Show proper messages for failed expectations.\n- |vspec-custom-matcher|:\n  - Change the naming guideline.\n    - Use snake_case instead of camelCase.\n    - Add new aliases for predefined custom matcheres.\n    - Old aliases are still supported, but deprecated.\n  - Support custom failure message.\n    - See |vspec#customize_matcher()| for the details.\n    - It was not possible to show meaningful messages for failed expectations using custom mathcers with old versions.\n    - Change the syntax to register new matcher.\n    - Old syntax is still supported, but deprecated.\n  - Fix to properly support custom matchers with 2 or more arguments.","3":"- |:Expect-not|:\n  - Show proper messages for failed expectations.\n- |vspec-custom-matcher|:\n  - Change the naming guideline.\n    - Use snake_case instead of camelCase.\n    - Add new aliases for predefined custom matcheres.\n    - Old aliases are still supported, but deprecated.\n  - Support custom failure message.\n    - See |vspec#customize_matcher()| for the details.\n    - It was not possible to show meaningful messages for failed expectations using custom mathcers with old versions.\n    - Change the syntax to register new matcher.\n    - Old syntax is still supported, but deprecated.\n  - Fix to properly support custom matchers with 2 or more arguments.","package":"vim-vspec-1.1.0.zip","4":"vim-vspec-1.1.0.zip","src_id":"18922","5":"18922","creation_date":"1351518095","6":"1351518095"},{"0":"3012","vim_version":"7.0","1":"7.0","script_version":"1.0.2","2":"1.0.2","version_comment":"- |bin\/vspec|:\n  - Remove user's |after-directory| from 'runtimepath' to avoid unexpected interference to run tests.\n  - Remove the output adjustment for the current directory.\n- |:Expect|: Fix to parse expressions including '\"' and '|' correctly.\n- Add missing syntax highlighting for |:SKIP| and |:TODO|.","3":"- |bin\/vspec|:\n  - Remove user's |after-directory| from 'runtimepath' to avoid unexpected interference to run tests.\n  - Remove the output adjustment for the current directory.\n- |:Expect|: Fix to parse expressions including '\"' and '|' correctly.\n- Add missing syntax highlighting for |:SKIP| and |:TODO|.","package":"vim-vspec-1.0.2.zip","4":"vim-vspec-1.0.2.zip","src_id":"17436","5":"17436","creation_date":"1329050413","6":"1329050413"},{"0":"3012","vim_version":"7.0","1":"7.0","script_version":"1.0.0","2":"1.0.0","version_comment":"- Completely rewritten.  No compatibility with old versions.\n  - Output format is changed to Test Anything Protocol version 12.\n  - The style to write examples is changed.  See also |vspec-examples| for the details.\n  - Change the order of arguments to |bin\/vspec|.\n  - Change the syntax for |vspec-custom-matcher| to be extensible and readable.\n  - Add |:Expect-not| for counter examples.\n  - Add |:TODO| for incomplete examples.\n  - Add |:SKIP| for environment-specific examples.\n  - Add |:before| blocks and |:after| blocks.","3":"- Completely rewritten.  No compatibility with old versions.\n  - Output format is changed to Test Anything Protocol version 12.\n  - The style to write examples is changed.  See also |vspec-examples| for the details.\n  - Change the order of arguments to |bin\/vspec|.\n  - Change the syntax for |vspec-custom-matcher| to be extensible and readable.\n  - Add |:Expect-not| for counter examples.\n  - Add |:TODO| for incomplete examples.\n  - Add |:SKIP| for environment-specific examples.\n  - Add |:before| blocks and |:after| blocks.","package":"vim-vspec-1.0.0.zip","4":"vim-vspec-1.0.0.zip","src_id":"17339","5":"17339","creation_date":"1327937723","6":"1327937723"},{"0":"3012","vim_version":"7.0","1":"7.0","script_version":"0.0.4","2":"0.0.4","version_comment":"- Add additional syntax file for |vspec-commands|.\n- |:Should|: Provide expression completion for convenience.\n- Improve minor stuffs.","3":"- Add additional syntax file for |vspec-commands|.\n- |:Should|: Provide expression completion for convenience.\n- Improve minor stuffs.","package":"vim-vspec-0.0.4.zip","4":"vim-vspec-0.0.4.zip","src_id":"12782","5":"12782","creation_date":"1270383057","6":"1270383057"},{"0":"3012","vim_version":"7.0","1":"7.0","script_version":"0.0.3","2":"0.0.3","version_comment":"Initial upload","3":"Initial upload","package":"vim-vspec-0.0.3.zip","4":"vim-vspec-0.0.3.zip","src_id":"12611","5":"12611","creation_date":"1268403583","6":"1268403583"}]},"3011":{"script_id":"3011","0":"3011","script_name":"tumblr.vim","1":"tumblr.vim","script_type":"syntax","2":"syntax","summary":"Syntax highlighting for Tumblr themes","3":"Syntax highlighting for Tumblr themes","description":"Syntax highlighting for Tumblr themes.\r\n\r\nScreenshot: http:\/\/29.media.tumblr.com\/tumblr_kz38v6harE1qz5urdo1_500.png\r\nSource: http:\/\/github.com\/inky\/tumblr\/tree\/master\/vim\/","4":"Syntax highlighting for Tumblr themes.\r\n\r\nScreenshot: http:\/\/29.media.tumblr.com\/tumblr_kz38v6harE1qz5urdo1_500.png\r\nSource: http:\/\/github.com\/inky\/tumblr\/tree\/master\/vim\/","install_details":"Place tumblr.vim file in ~\/.vim\/syntax folder. To enable syntax highlighting for *.tumblr.html, add the following line to ~\/.vim\/filetype.vim:\r\n\r\nau! BufRead,BufNewFile *.tumblr.html setfiletype tumblr","5":"Place tumblr.vim file in ~\/.vim\/syntax folder. To enable syntax highlighting for *.tumblr.html, add the following line to ~\/.vim\/filetype.vim:\r\n\r\nau! BufRead,BufNewFile *.tumblr.html setfiletype tumblr","first_name":"Liam","6":"Liam","last_name":"Cooke","7":"Cooke","releases":[{"0":"3011","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"tumblr.vim","4":"tumblr.vim","src_id":"12603","5":"12603","creation_date":"1268338574","6":"1268338574"}]},"3010":{"script_id":"3010","0":"3010","script_name":"delete-surround-html","1":"delete-surround-html","script_type":"ftplugin","2":"ftplugin","summary":"for deleting surrounding html\/django tags","3":"for deleting surrounding html\/django tags","description":"Repo: http:\/\/github.com\/mjbrownie\/delete-surround-html\r\nExample vid (includes other plugins): http:\/\/www.youtube.com\/watch?v=NbV-OrFMalU\r\n\r\n after\/ftplugin\/html\/delete_surround_html.vim\r\n\r\n For Deleting Surrounding html  and django tags\r\n\r\n This plugin is inspired by Tim Popes surround.vim delete-surround-tag 'dst'\r\n mapping. It will let you delete the surrounding tag of a specified type\r\n rather than just the immediate tag.\r\n\r\non html filetypes this will add two normal mappings in your vimrc\r\n\r\n'dsh' (delete-surround-html) \r\ndelete - surround - html - (u)l \/ (l)i \/ (d)iv \/ (s)pan \/ (f)orm \/ (t)able \/ t(r) \/ (c)td \/ (p):\r\n\r\n'dsd' (delete-surround-django) will give you the options\r\ndelete - surround - django - (b)lock \/ (c)omment \/ (i)f* \/ (w)ith \/ (f)or :\r\n\r\nsimple example here\r\n\r\n{% comment%}\r\n{% block foo %}\r\n<div id=\"bar\">\r\n    <ul>\r\n        <li>'dsdc' here will remove the comment<\/li>\r\n        <li>'dsdb' here will remove the block<\/li>\r\n        <li>'dshd' here will remove the div<\/li>\r\n        <li>'dshu' here will remove the ul<\/li>\r\n        <li>'dshl' here will remove the li<\/li>\r\n    <\/ul>\r\n<\/div>\r\n{% endblock %}\r\n{% endcomment %}\r\n\r\nThis scripts mnemonics are intended to compliment these two scripts\r\n\r\ndjango-textobjects  http:\/\/www.vim.org\/scripts\/script.php?script_id=2999\r\nhtml-advanced-textobjects http:\/\/www.vim.org\/scripts\/script.php?script_id=3000\r\n\r\nAlso if you want the reverse, ie. to surround a visual selection with django tags\r\n\r\nyou can also use http:\/\/www.vim.org\/scripts\/script.php?script_id=1697 with the following mappings\r\n\r\nlet g:surround_{char2nr(\"b\")} = \"{% block\\1 \\r..*\\r &\\1%}\\n\\r\\n{% endblock %}\\n\"\r\nlet g:surround_{char2nr(\"i\")} = \"{% if\\1 \\r..*\\r &\\1%}\\n\\r\\n{% endif %}\\n\"\r\nlet g:surround_{char2nr(\"w\")} = \"{% with\\1 \\r..*\\r &\\1%}\\n\\r\\n{% endwith %}\\n\"\r\nlet g:surround_{char2nr(\"c\")} = \"{% comment\\1 \\r..*\\r &\\1%}\\n\\r\\n{% endcomment %}\\n\"\r\nlet g:surround_{char2nr(\"f\")} = \"{% for\\1 \\r..*\\r &\\1%}\\n\\r\\n{% endfor %}\\n\"\r\n\r\nthen go v...sb.. etc","4":"Repo: http:\/\/github.com\/mjbrownie\/delete-surround-html\r\nExample vid (includes other plugins): http:\/\/www.youtube.com\/watch?v=NbV-OrFMalU\r\n\r\n after\/ftplugin\/html\/delete_surround_html.vim\r\n\r\n For Deleting Surrounding html  and django tags\r\n\r\n This plugin is inspired by Tim Popes surround.vim delete-surround-tag 'dst'\r\n mapping. It will let you delete the surrounding tag of a specified type\r\n rather than just the immediate tag.\r\n\r\non html filetypes this will add two normal mappings in your vimrc\r\n\r\n'dsh' (delete-surround-html) \r\ndelete - surround - html - (u)l \/ (l)i \/ (d)iv \/ (s)pan \/ (f)orm \/ (t)able \/ t(r) \/ (c)td \/ (p):\r\n\r\n'dsd' (delete-surround-django) will give you the options\r\ndelete - surround - django - (b)lock \/ (c)omment \/ (i)f* \/ (w)ith \/ (f)or :\r\n\r\nsimple example here\r\n\r\n{% comment%}\r\n{% block foo %}\r\n<div id=\"bar\">\r\n    <ul>\r\n        <li>'dsdc' here will remove the comment<\/li>\r\n        <li>'dsdb' here will remove the block<\/li>\r\n        <li>'dshd' here will remove the div<\/li>\r\n        <li>'dshu' here will remove the ul<\/li>\r\n        <li>'dshl' here will remove the li<\/li>\r\n    <\/ul>\r\n<\/div>\r\n{% endblock %}\r\n{% endcomment %}\r\n\r\nThis scripts mnemonics are intended to compliment these two scripts\r\n\r\ndjango-textobjects  http:\/\/www.vim.org\/scripts\/script.php?script_id=2999\r\nhtml-advanced-textobjects http:\/\/www.vim.org\/scripts\/script.php?script_id=3000\r\n\r\nAlso if you want the reverse, ie. to surround a visual selection with django tags\r\n\r\nyou can also use http:\/\/www.vim.org\/scripts\/script.php?script_id=1697 with the following mappings\r\n\r\nlet g:surround_{char2nr(\"b\")} = \"{% block\\1 \\r..*\\r &\\1%}\\n\\r\\n{% endblock %}\\n\"\r\nlet g:surround_{char2nr(\"i\")} = \"{% if\\1 \\r..*\\r &\\1%}\\n\\r\\n{% endif %}\\n\"\r\nlet g:surround_{char2nr(\"w\")} = \"{% with\\1 \\r..*\\r &\\1%}\\n\\r\\n{% endwith %}\\n\"\r\nlet g:surround_{char2nr(\"c\")} = \"{% comment\\1 \\r..*\\r &\\1%}\\n\\r\\n{% endcomment %}\\n\"\r\nlet g:surround_{char2nr(\"f\")} = \"{% for\\1 \\r..*\\r &\\1%}\\n\\r\\n{% endfor %}\\n\"\r\n\r\nthen go v...sb.. etc","install_details":"File needs to be\r\nafter\/ftplugin\/html\/delete_surround_html.vim","5":"File needs to be\r\nafter\/ftplugin\/html\/delete_surround_html.vim","first_name":"Michael","6":"Michael","last_name":"Brown","7":"Brown","releases":[{"0":"3010","vim_version":"6.0","1":"6.0","script_version":"0.1.0","2":"0.1.0","version_comment":"Initial upload","3":"Initial upload","package":"mjbrownie-delete-surround-html-2ec2f80.zip","4":"mjbrownie-delete-surround-html-2ec2f80.zip","src_id":"12599","5":"12599","creation_date":"1268308575","6":"1268308575"}]},"3009":{"script_id":"3009","0":"3009","script_name":"treemenu.vim","1":"treemenu.vim","script_type":"utility","2":"utility","summary":"customizable treemenu plugin","3":"customizable treemenu plugin","description":"please see: http:\/\/github.com\/c9s\/treemenu.vim","4":"please see: http:\/\/github.com\/c9s\/treemenu.vim","install_details":"please see: http:\/\/github.com\/c9s\/treemenu.vim","5":"please see: http:\/\/github.com\/c9s\/treemenu.vim","first_name":"Yo-An","6":"Yo-An","last_name":"Lin","7":"Lin","releases":[{"0":"3009","vim_version":"7.2","1":"7.2","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"treemenu.vim","4":"treemenu.vim","src_id":"12593","5":"12593","creation_date":"1268255394","6":"1268255394"}]},"3008":{"script_id":"3008","0":"3008","script_name":"httplog","1":"httplog","script_type":"syntax","2":"syntax","summary":"Highlight access log of Apache, nginx, etc","3":"Highlight access log of Apache, nginx, etc","description":"This is a simple syntax file to highlight access log of several HTTP servers (with the default log format).\r\n\r\nlocalhost's IP, LAN IP will be highlighted differently and 5xx HTTP status code will be highlighted in ErrorMsg. And names of a few browsers and other clients in the user agent string will be highlighted too.","4":"This is a simple syntax file to highlight access log of several HTTP servers (with the default log format).\r\n\r\nlocalhost's IP, LAN IP will be highlighted differently and 5xx HTTP status code will be highlighted in ErrorMsg. And names of a few browsers and other clients in the user agent string will be highlighted too.","install_details":"Put it in your syntax directory. You can add this to your filetype.vim  to make Vim recognize the log files:\r\n  au BufRead\t\t*access.log*\t\t\tsetf httplog","5":"Put it in your syntax directory. You can add this to your filetype.vim  to make Vim recognize the log files:\r\n  au BufRead\t\t*access.log*\t\t\tsetf httplog","first_name":"lilydjwg","6":"lilydjwg","last_name":" ","7":" ","releases":[{"0":"3008","vim_version":"7.0","1":"7.0","script_version":"0.5","2":"0.5","version_comment":"* more user agents","3":"* more user agents","package":"httplog.vim","4":"httplog.vim","src_id":"20736","5":"20736","creation_date":"1377916481","6":"1377916481"},{"0":"3008","vim_version":"7.0","1":"7.0","script_version":"0.4","2":"0.4","version_comment":"- Match three missing HTTP requests (OPTIONS, PATCH and TRACE).\r\n- Match 172.16.0.0 - 172.31.255.255 IP address range for LAN.\r\n    \r\nThanks to Audrius Ka\u00c5\u00beukauskas.","3":"- Match three missing HTTP requests (OPTIONS, PATCH and TRACE).\r\n- Match 172.16.0.0 - 172.31.255.255 IP address range for LAN.\r\n    \r\nThanks to Audrius Ka\u00c5\u00beukauskas.","package":"httplog.vim","4":"httplog.vim","src_id":"19053","5":"19053","creation_date":"1354070712","6":"1354070712"},{"0":"3008","vim_version":"7.0","1":"7.0","script_version":"0.3","2":"0.3","version_comment":"* update user agent matching\r\n* update ip address matching","3":"* update user agent matching\r\n* update ip address matching","package":"httplog.vim","4":"httplog.vim","src_id":"19050","5":"19050","creation_date":"1354027539","6":"1354027539"},{"0":"3008","vim_version":"7.0","1":"7.0","script_version":"0.2","2":"0.2","version_comment":"Fix HTTP status code highlighting.","3":"Fix HTTP status code highlighting.","package":"httplog.vim","4":"httplog.vim","src_id":"15595","5":"15595","creation_date":"1304696850","6":"1304696850"},{"0":"3008","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"httplog.vim","4":"httplog.vim","src_id":"12580","5":"12580","creation_date":"1268141215","6":"1268141215"}]},"3007":{"script_id":"3007","0":"3007","script_name":"Twee Integration for Vim","1":"Twee Integration for Vim","script_type":"syntax","2":"syntax","summary":"Syntax highlighting and compiler support for twee interactive stories creator","3":"Syntax highlighting and compiler support for twee interactive stories creator","description":"This adds syntax highlighting and compiler support for twee files (*.tw).\r\nThe syntax highlighting was prepared with a dark colorscheme in mind.\r\n\r\nTyping :make in .tw files will run twee (1.7.5) on them and pipe it to an html file named as the current file. That is, running :make on fiction.tw will create the fiction.html file.\r\n\r\nTwee (http:\/\/gimcrackd.com\/etc\/src\/) is an interactive stories creation tool based on TyddlyWiki, developed by Chris Klimas.","4":"This adds syntax highlighting and compiler support for twee files (*.tw).\r\nThe syntax highlighting was prepared with a dark colorscheme in mind.\r\n\r\nTyping :make in .tw files will run twee (1.7.5) on them and pipe it to an html file named as the current file. That is, running :make on fiction.tw will create the fiction.html file.\r\n\r\nTwee (http:\/\/gimcrackd.com\/etc\/src\/) is an interactive stories creation tool based on TyddlyWiki, developed by Chris Klimas.","install_details":"The installer requires Vimball.\r\nInstall the scripts by opening the file and sourceing it (:source %).\r\n","5":"The installer requires Vimball.\r\nInstall the scripts by opening the file and sourceing it (:source %).\r\n","first_name":"Felipe","6":"Felipe","last_name":"Morales","7":"Morales","releases":[{"0":"3007","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"twee.vba","4":"twee.vba","src_id":"12577","5":"12577","creation_date":"1268067318","6":"1268067318"}]},"3006":{"script_id":"3006","0":"3006","script_name":"CSSMinister","1":"CSSMinister","script_type":"utility","2":"utility","summary":"Converts colors in CSS stylesheets from one format to another","3":"Converts colors in CSS stylesheets from one format to another","description":"CSSMinister provides functions and mappings that convert any hexadecimal, keyword, RGB(A) or HSL(A) color values from one format to another.  The functions fall into two categories:  1) those that change the next matching color only, and 2) those that change all colors matching the requested format in a range or in the entire buffer.\r\n\r\nFunctions that change formats one color at a time include:\r\n\r\n  :ToHex\r\n  :ToRGB\r\n  :ToRGBA\r\n  :ToHSL\r\n  :ToHSLA\r\n\r\nFunctions that change all colors matching the requested color format in a range or in the entire buffer:\r\n\r\n  :ToHexAll <format>\r\n  :ToRGBAll <format>\r\n  :ToRGBAAll <format>\r\n  :ToHSLAll <format>\r\n  :ToHSLAAll <format>\r\n\r\nWhere <format> is the color format you're converting from.\r\n\r\nAs of v1.0.0, the above commands replace the old key mappings as a less obtrusive solution for converting between different color formats. Some key mappings remain for those that prefer them:\r\n\r\n  <leader>x - convert to hex\r\n  <leader>r - convert to rgb\r\n  <leader>h - convert to hsl\r\n  <leader>ra - convert to rgba\r\n  <leader>ha - convert to hsla\r\n\r\nThis script was tested with CSS, Sass and Less stylesheets.  However, it should work anywhere CSS color values are used.","4":"CSSMinister provides functions and mappings that convert any hexadecimal, keyword, RGB(A) or HSL(A) color values from one format to another.  The functions fall into two categories:  1) those that change the next matching color only, and 2) those that change all colors matching the requested format in a range or in the entire buffer.\r\n\r\nFunctions that change formats one color at a time include:\r\n\r\n  :ToHex\r\n  :ToRGB\r\n  :ToRGBA\r\n  :ToHSL\r\n  :ToHSLA\r\n\r\nFunctions that change all colors matching the requested color format in a range or in the entire buffer:\r\n\r\n  :ToHexAll <format>\r\n  :ToRGBAll <format>\r\n  :ToRGBAAll <format>\r\n  :ToHSLAll <format>\r\n  :ToHSLAAll <format>\r\n\r\nWhere <format> is the color format you're converting from.\r\n\r\nAs of v1.0.0, the above commands replace the old key mappings as a less obtrusive solution for converting between different color formats. Some key mappings remain for those that prefer them:\r\n\r\n  <leader>x - convert to hex\r\n  <leader>r - convert to rgb\r\n  <leader>h - convert to hsl\r\n  <leader>ra - convert to rgba\r\n  <leader>ha - convert to hsla\r\n\r\nThis script was tested with CSS, Sass and Less stylesheets.  However, it should work anywhere CSS color values are used.","install_details":"If you're using vundle, add this line to your .vimrc: \r\n\r\n  Bundle \"CSSMinister\"\r\n\r\nUsing pathogen? Unzip the contents into your bundle\/ directory. Otherwise, unzip in your ~\/.vim folder and run :helptags ~\/.vim\/doc.","5":"If you're using vundle, add this line to your .vimrc: \r\n\r\n  Bundle \"CSSMinister\"\r\n\r\nUsing pathogen? Unzip the contents into your bundle\/ directory. Otherwise, unzip in your ~\/.vim folder and run :helptags ~\/.vim\/doc.","first_name":"Lou","6":"Lou","last_name":"Gonzalez","7":"Gonzalez","releases":[{"0":"3006","vim_version":"7.0","1":"7.0","script_version":"1.0.0","2":"1.0.0","version_comment":"* Added extended color keywords\r\n* Conversions between HSLA and RGBA formats\r\n* Visual mode conversions\r\n* Handle zero-padded color values in RGB(A) and HSL(A) colors\r\n* Replaced old mappings with less obstructive commands\r\n* Added config options","3":"* Added extended color keywords\r\n* Conversions between HSLA and RGBA formats\r\n* Visual mode conversions\r\n* Handle zero-padded color values in RGB(A) and HSL(A) colors\r\n* Replaced old mappings with less obstructive commands\r\n* Added config options","package":"CSSMinister.zip","4":"CSSMinister.zip","src_id":"17394","5":"17394","creation_date":"1328467311","6":"1328467311"},{"0":"3006","vim_version":"7.0","1":"7.0","script_version":"0.2.1","2":"0.2.1","version_comment":"Convert from any HTML4 color keyword to any of the supported formats.","3":"Convert from any HTML4 color keyword to any of the supported formats.","package":"CSSMinister.zip","4":"CSSMinister.zip","src_id":"12672","5":"12672","creation_date":"1269188371","6":"1269188371"},{"0":"3006","vim_version":"7.0","1":"7.0","script_version":"0.1.0","2":"0.1.0","version_comment":"Initial upload","3":"Initial upload","package":"CSSMinister.zip","4":"CSSMinister.zip","src_id":"12571","5":"12571","creation_date":"1267952243","6":"1267952243"}]},"3005":{"script_id":"3005","0":"3005","script_name":"simplecommenter","1":"simplecommenter","script_type":"utility","2":"utility","summary":"simple commenter","3":"simple commenter","description":"    quite simple, but support most language (perl,python,ruby,c,javascript ... etc)\r\n\r\n    See on github:\r\n    http:\/\/github.com\/c9s\/simple-commenter.vim\/\r\n","4":"    quite simple, but support most language (perl,python,ruby,c,javascript ... etc)\r\n\r\n    See on github:\r\n    http:\/\/github.com\/c9s\/simple-commenter.vim\/\r\n","install_details":"    $ vimana i simplecommenter.vim \r\n\r\n    See Vimana on github:  http:\/\/github.com\/c9s\/vimana\r\n\r\n    Or copy simplecommenter.vim to your ~\/.vim\/plugin\/\r\n","5":"    $ vimana i simplecommenter.vim \r\n\r\n    See Vimana on github:  http:\/\/github.com\/c9s\/vimana\r\n\r\n    Or copy simplecommenter.vim to your ~\/.vim\/plugin\/\r\n","first_name":"Yo-An","6":"Yo-An","last_name":"Lin","7":"Lin","releases":[{"0":"3005","vim_version":"7.2","1":"7.2","script_version":"0.1","2":"0.1","version_comment":"    \n    Release.\n","3":"    \n    Release.\n","package":"simplecommenter.vim","4":"simplecommenter.vim","src_id":"12629","5":"12629","creation_date":"1268614720","6":"1268614720"},{"0":"3005","vim_version":"7.0","1":"7.0","script_version":"1.1","2":"1.1","version_comment":"more options","3":"more options","package":"simplecommenter.vim","4":"simplecommenter.vim","src_id":"12557","5":"12557","creation_date":"1267738812","6":"1267738812"},{"0":"3005","vim_version":"7.2","1":"7.2","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"simplecommenter.vim","4":"simplecommenter.vim","src_id":"12556","5":"12556","creation_date":"1267735329","6":"1267735329"}]},"3004":{"script_id":"3004","0":"3004","script_name":"vxfold.vim","1":"vxfold.vim","script_type":"utility","2":"utility","summary":"Fold cycling similar to emacs org-mode (using TAB key)","3":"Fold cycling similar to emacs org-mode (using TAB key)","description":"This script implements a fold-cycling functionality similar to\r\nthe one in emacs org-mode.\r\n\r\nSubfolds are open\/closed each time TAB or Shift-TAB is pressed.\r\nTAB operates on the lines below a heading that is in the current line.\r\nShift-TAB operates on the whole buffer.\r\n\r\nAfter each press a step in the following cycle will be performed:\r\n   1. fold closed\r\n   2. show direct subheadings\r\n   3. show structure below heading + first line of text\r\n   4. unfold all\r\n\r\n   NOTES: It is possible to skip step 2 and\/or 3, but the per-buffer \r\n   configuration is still missing (I think emacs-org uses only 1-2-4). In step \r\n   2 the text under the current heading may be visible; this is because of\r\n   the way folding is implemented in Vim.\r\n\r\nFold cycling will work in buffers that are folded in the following way:\r\n  * headings have folding levels 1-9\r\n  * text has a folding level higher than 9\r\n\r\nThis means that the script can work with TVO (vimscript#517) without\r\nchanging the folding mode. To enable fold cycling in TVO mode:\r\n\r\n  :VxFoldTvo\r\n\r\nFor other modes the foldmethod has to be changed. Foldmethods are\r\nprovided for viki (vimscript#861) and vimwiki (vimscript#2226).\r\n\r\n  :VxFoldViki\r\n  :VxFoldVimWiki\r\n\r\nThe later commands will also work on any buffer that has the headings defined\r\nwith a number of characters at the beginning of line (viki='*', vimwiki='=').\r\n\r\nIf a file uses '#' characters to mark headings with levels, it is also possible\r\nto use fold cycling in it like this:\r\n\r\n  :call vxfold#SetFold_OrgBolCount('#')\r\n  :VxFoldTvo\r\n\r\nThe display of the folded text can be changed with\r\n\r\n  :call vxfold#SetFoldTextFirstLine()\r\n\r\nwhich is the default for VxFoldVimWiki and VxFoldViki.\r\n\r\nPlease report bugs\/suggestions on the Vim\/Wiki (link top right).\r\n\r\n","4":"This script implements a fold-cycling functionality similar to\r\nthe one in emacs org-mode.\r\n\r\nSubfolds are open\/closed each time TAB or Shift-TAB is pressed.\r\nTAB operates on the lines below a heading that is in the current line.\r\nShift-TAB operates on the whole buffer.\r\n\r\nAfter each press a step in the following cycle will be performed:\r\n   1. fold closed\r\n   2. show direct subheadings\r\n   3. show structure below heading + first line of text\r\n   4. unfold all\r\n\r\n   NOTES: It is possible to skip step 2 and\/or 3, but the per-buffer \r\n   configuration is still missing (I think emacs-org uses only 1-2-4). In step \r\n   2 the text under the current heading may be visible; this is because of\r\n   the way folding is implemented in Vim.\r\n\r\nFold cycling will work in buffers that are folded in the following way:\r\n  * headings have folding levels 1-9\r\n  * text has a folding level higher than 9\r\n\r\nThis means that the script can work with TVO (vimscript#517) without\r\nchanging the folding mode. To enable fold cycling in TVO mode:\r\n\r\n  :VxFoldTvo\r\n\r\nFor other modes the foldmethod has to be changed. Foldmethods are\r\nprovided for viki (vimscript#861) and vimwiki (vimscript#2226).\r\n\r\n  :VxFoldViki\r\n  :VxFoldVimWiki\r\n\r\nThe later commands will also work on any buffer that has the headings defined\r\nwith a number of characters at the beginning of line (viki='*', vimwiki='=').\r\n\r\nIf a file uses '#' characters to mark headings with levels, it is also possible\r\nto use fold cycling in it like this:\r\n\r\n  :call vxfold#SetFold_OrgBolCount('#')\r\n  :VxFoldTvo\r\n\r\nThe display of the folded text can be changed with\r\n\r\n  :call vxfold#SetFoldTextFirstLine()\r\n\r\nwhich is the default for VxFoldVimWiki and VxFoldViki.\r\n\r\nPlease report bugs\/suggestions on the Vim\/Wiki (link top right).\r\n\r\n","install_details":"Unpack into vim runtime directory (eg. ~\/.vim)","5":"Unpack into vim runtime directory (eg. ~\/.vim)","first_name":"Marko","6":"Marko","last_name":"Mahni\u010d","7":"Mahnič","releases":[{"0":"3004","vim_version":"7.2","1":"7.2","script_version":"0.2","2":"0.2","version_comment":"* fold expression settings changed to buffer-local","3":"* fold expression settings changed to buffer-local","package":"vxfold.zip","4":"vxfold.zip","src_id":"14826","5":"14826","creation_date":"1295723687","6":"1295723687"},{"0":"3004","vim_version":"7.2","1":"7.2","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"vxfold.zip","4":"vxfold.zip","src_id":"12542","5":"12542","creation_date":"1267556025","6":"1267556025"}]},"3003":{"script_id":"3003","0":"3003","script_name":"indent\/python","1":"indent\/python","script_type":"indent","2":"indent","summary":"Yet another Python indentation script","3":"Yet another Python indentation script","description":"This is my attempt at indenting Python to conform to PEP8.  Based on the 7.2 Python indentation, with bits of vimscript #974 hacked in.","4":"This is my attempt at indenting Python to conform to PEP8.  Based on the 7.2 Python indentation, with bits of vimscript #974 hacked in.","install_details":"Copy the script to your ~\/.vim\/indent directory.","5":"Copy the script to your ~\/.vim\/indent directory.","first_name":"David","6":"David","last_name":"Moore","7":"Moore","releases":[{"0":"3003","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"python.vim","4":"python.vim","src_id":"12541","5":"12541","creation_date":"1267546201","6":"1267546201"}]},"3002":{"script_id":"3002","0":"3002","script_name":"tag_in_new_tab","1":"tag_in_new_tab","script_type":"utility","2":"utility","summary":"Open tag in new tab.","3":"Open tag in new tab.","description":"With this plugin, Shift-Enter in normal mode opens a definition of identifier under cursor in a new tab. Uses tag files (see :help tags).\r\n\r\nSee comments for simpler replacement. Thanks for comment goes to an unknown well-doer! ;-)","4":"With this plugin, Shift-Enter in normal mode opens a definition of identifier under cursor in a new tab. Uses tag files (see :help tags).\r\n\r\nSee comments for simpler replacement. Thanks for comment goes to an unknown well-doer! ;-)","install_details":"Copy the plugin into your ~\/.vim\/plugin\/ directory.\r\nNot tested on Windows.","5":"Copy the plugin into your ~\/.vim\/plugin\/ directory.\r\nNot tested on Windows.","first_name":"Miroslav","6":"Miroslav","last_name":"Tynovsky","7":"Tynovsky","releases":[{"0":"3002","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"tag_in_new_tab.vim","4":"tag_in_new_tab.vim","src_id":"12538","5":"12538","creation_date":"1267534492","6":"1267534492"}]},"3001":{"script_id":"3001","0":"3001","script_name":"candyman.vim","1":"candyman.vim","script_type":"color scheme","2":"color scheme","summary":"dark colorscheme based on jellybeans","3":"dark colorscheme based on jellybeans","description":"candyman is derived from jellybeans.vim with some clearer color demarcations (window splits and clearer \"#TODO\" strings)\r\n\r\nScreenshot:\r\nhttp:\/\/www.flickr.com\/photos\/28853165@N05\/5203737877\/","4":"candyman is derived from jellybeans.vim with some clearer color demarcations (window splits and clearer \"#TODO\" strings)\r\n\r\nScreenshot:\r\nhttp:\/\/www.flickr.com\/photos\/28853165@N05\/5203737877\/","install_details":"copy file to .vim\/colors","5":"copy file to .vim\/colors","first_name":"Paul","6":"Paul","last_name":"L","7":"L","releases":[{"0":"3001","vim_version":"7.0","1":"7.0","script_version":"1.3","2":"1.3","version_comment":"more refinements for window splits, enjoy...","3":"more refinements for window splits, enjoy...","package":"candyman.vim","4":"candyman.vim","src_id":"14346","5":"14346","creation_date":"1290411552","6":"1290411552"},{"0":"3001","vim_version":"7.0","1":"7.0","script_version":"1.2","2":"1.2","version_comment":"clearer visual mode","3":"clearer visual mode","package":"candyman.vim","4":"candyman.vim","src_id":"13069","5":"13069","creation_date":"1275024415","6":"1275024415"},{"0":"3001","vim_version":"7.2","1":"7.2","script_version":"1","2":"1","version_comment":"Initial upload","3":"Initial upload","package":"candyman.vim","4":"candyman.vim","src_id":"12528","5":"12528","creation_date":"1267421418","6":"1267421418"}]},"3000":{"script_id":"3000","0":"3000","script_name":"html advanced text objects","1":"html advanced text objects","script_type":"ftplugin","2":"ftplugin","summary":"some alternate text objects for html","3":"some alternate text objects for html","description":"Repo: http:\/\/github.com\/mjbrownie\/html-textobjects\r\nExample vid (includes other plugins): http:\/\/www.youtube.com\/watch?v=NbV-OrFMalU\r\n\r\nThe inbuilt text object for html (cit cat) is great for the immediate tag but requires some additional movement if you have nesting. \r\nThis plugin gives you some more text objects to play with eg 'cahf' (cut-around-html-form) 'cihb' (cut-in-html-body) , 'viht' (visual-inner-html-table) , 'gUihd' (go UPPERCASE in html div)\r\n\r\nThis is still very much a work in progress any ideas on mapping naming conventions\/ bugs etc please contact me.\r\n\r\n\" Dependencies:\r\n\"\r\n\" textobj-user by Kana Natsuno\r\n\" http:\/\/www.vim.org\/scripts\/script.php?script_id=2100\r\n\"\r\n\"\r\n\" Overview:\r\n\"\r\n\" This plugin adds some textobjects to the html filetype\r\n\"\r\n\" ihf\/ahf - in\/around a <form>\r\n\" ihf\/ahd - in\/around a <div>\r\n\" ihf\/ahs - in\/around a <span>\r\n\"\r\n\"\r\n\" ihb <body>\r\n\" ihp <p>\r\n\" ihu <ul>\r\n\" ihl <li>\r\n\" iht <table>\r\n\" ihr <tr>\r\n\" ihc <td> (in-html-cell to avoid clash with <div>)\r\n\"\"\r\n\" so Use as you would other text objects in visual selection, cutting and\r\n\" dealleting etc.\r\n\"\r\n\" Installation:\r\n\"\r\n\" Please ensure you have the above plugins installed as instructed\r\n\" This file should be in your after\/ftplugin for html\r\n\"\r\n\" ~\/.vim\/after\/ftplugin\/html\/html_textobjects.vim\r\n\"\r\n\" }}\r\n\r\nNote theres a complimentary django textobject script \r\n\r\nhttp:\/\/www.vim.org\/scripts\/script.php?script_id=2999","4":"Repo: http:\/\/github.com\/mjbrownie\/html-textobjects\r\nExample vid (includes other plugins): http:\/\/www.youtube.com\/watch?v=NbV-OrFMalU\r\n\r\nThe inbuilt text object for html (cit cat) is great for the immediate tag but requires some additional movement if you have nesting. \r\nThis plugin gives you some more text objects to play with eg 'cahf' (cut-around-html-form) 'cihb' (cut-in-html-body) , 'viht' (visual-inner-html-table) , 'gUihd' (go UPPERCASE in html div)\r\n\r\nThis is still very much a work in progress any ideas on mapping naming conventions\/ bugs etc please contact me.\r\n\r\n\" Dependencies:\r\n\"\r\n\" textobj-user by Kana Natsuno\r\n\" http:\/\/www.vim.org\/scripts\/script.php?script_id=2100\r\n\"\r\n\"\r\n\" Overview:\r\n\"\r\n\" This plugin adds some textobjects to the html filetype\r\n\"\r\n\" ihf\/ahf - in\/around a <form>\r\n\" ihf\/ahd - in\/around a <div>\r\n\" ihf\/ahs - in\/around a <span>\r\n\"\r\n\"\r\n\" ihb <body>\r\n\" ihp <p>\r\n\" ihu <ul>\r\n\" ihl <li>\r\n\" iht <table>\r\n\" ihr <tr>\r\n\" ihc <td> (in-html-cell to avoid clash with <div>)\r\n\"\"\r\n\" so Use as you would other text objects in visual selection, cutting and\r\n\" dealleting etc.\r\n\"\r\n\" Installation:\r\n\"\r\n\" Please ensure you have the above plugins installed as instructed\r\n\" This file should be in your after\/ftplugin for html\r\n\"\r\n\" ~\/.vim\/after\/ftplugin\/html\/html_textobjects.vim\r\n\"\r\n\" }}\r\n\r\nNote theres a complimentary django textobject script \r\n\r\nhttp:\/\/www.vim.org\/scripts\/script.php?script_id=2999","install_details":"File needs to be in \" ~\/.vim\/after\/ftplugin\/html\/html_textobjects.vim","5":"File needs to be in \" ~\/.vim\/after\/ftplugin\/html\/html_textobjects.vim","first_name":"Michael","6":"Michael","last_name":"Brown","7":"Brown","releases":[{"0":"3000","vim_version":"7.0","1":"7.0","script_version":"0.2.1","2":"0.2.1","version_comment":"Fixed a bufnr bug affecting around mappings","3":"Fixed a bufnr bug affecting around mappings","package":"mjbrownie-html-textobjects-cbf4ba7.zip","4":"mjbrownie-html-textobjects-cbf4ba7.zip","src_id":"12600","5":"12600","creation_date":"1268310357","6":"1268310357"},{"0":"3000","vim_version":"7.0","1":"7.0","script_version":"0.2.0","2":"0.2.0","version_comment":"Improved nesting handling. Removed matchit dependency","3":"Improved nesting handling. Removed matchit dependency","package":"mjbrownie-html-textobjects-f6e5573.zip","4":"mjbrownie-html-textobjects-f6e5573.zip","src_id":"12598","5":"12598","creation_date":"1268300244","6":"1268300244"},{"0":"3000","vim_version":"7.0","1":"7.0","script_version":"0.1.1","2":"0.1.1","version_comment":"bugfix: fixed greedy visual inner html tags. Improved no match handling ","3":"bugfix: fixed greedy visual inner html tags. Improved no match handling ","package":"mjbrownie-html-textobjects-fdc4678.zip","4":"mjbrownie-html-textobjects-fdc4678.zip","src_id":"12526","5":"12526","creation_date":"1267419619","6":"1267419619"},{"0":"3000","vim_version":"7.0","1":"7.0","script_version":"0.1.0","2":"0.1.0","version_comment":"Initial upload","3":"Initial upload","package":"html-textobjects.zip","4":"html-textobjects.zip","src_id":"12521","5":"12521","creation_date":"1267364196","6":"1267364196"}]},"2999":{"script_id":"2999","0":"2999","script_name":"django template textobjects","1":"django template textobjects","script_type":"ftplugin","2":"ftplugin","summary":"textobject mappings for the django template language","3":"textobject mappings for the django template language","description":"\" Dependencies:\r\n\"\r\n\"     textobj-user by Kana Natsuno\r\n\"     http:\/\/www.vim.org\/scripts\/script.php?script_id=2100\r\n\"\r\n\"\r\n\" Overview:\r\n\"     This plugin adds some textobjects to the htmldjango filetype\r\n\"\r\n\"     idb\/adb - in\/around a django {% block %}\r\n\"     idf\/adf - in around a django {% for %} loop\r\n\"     idi\/adi - in\/around a django {% if* } tag\r\n\"     idw\/adw - in around a django {% with %} tag\r\n\"     idc\/adc - in around a django {% comment %} tag\r\n\"     idC\/adC - in around a django {% cache %} tag\r\n\"     ids\/ads - in around a django {% spaceless %} tag\r\n\"\r\n\"    so Use as you would other text objects in visual selection, cutting and\r\n\"    dealleting etc.\r\n\"\r\n\" Installation:\r\n\"\r\n\"   Pathogen\/Vundle (recommended):\r\n\"\r\n\"   git clone https:\/\/github.com\/kana\/vim-textobj-user.git ~\/.vim\/bundle\/vim-textobj-user\r\n\"   git clone git:\/\/github.com\/mjbrownie\/django-template-textobjects.git ~\/.vim\/bundle\/django_template_textobjects\r\n\"\r\n\"   Manual:\r\n\"\r\n\"   Please ensure you have the above plugins installed as instructed\r\n\"   This file should be in your after\/ftplugin for htmldjango\r\n\"\r\n\"   ~\/.vim\/after\/ftplugin\/htmldjango\/template_textobjects.vim\r\n\"\r\n\"","4":"\" Dependencies:\r\n\"\r\n\"     textobj-user by Kana Natsuno\r\n\"     http:\/\/www.vim.org\/scripts\/script.php?script_id=2100\r\n\"\r\n\"\r\n\" Overview:\r\n\"     This plugin adds some textobjects to the htmldjango filetype\r\n\"\r\n\"     idb\/adb - in\/around a django {% block %}\r\n\"     idf\/adf - in around a django {% for %} loop\r\n\"     idi\/adi - in\/around a django {% if* } tag\r\n\"     idw\/adw - in around a django {% with %} tag\r\n\"     idc\/adc - in around a django {% comment %} tag\r\n\"     idC\/adC - in around a django {% cache %} tag\r\n\"     ids\/ads - in around a django {% spaceless %} tag\r\n\"\r\n\"    so Use as you would other text objects in visual selection, cutting and\r\n\"    dealleting etc.\r\n\"\r\n\" Installation:\r\n\"\r\n\"   Pathogen\/Vundle (recommended):\r\n\"\r\n\"   git clone https:\/\/github.com\/kana\/vim-textobj-user.git ~\/.vim\/bundle\/vim-textobj-user\r\n\"   git clone git:\/\/github.com\/mjbrownie\/django-template-textobjects.git ~\/.vim\/bundle\/django_template_textobjects\r\n\"\r\n\"   Manual:\r\n\"\r\n\"   Please ensure you have the above plugins installed as instructed\r\n\"   This file should be in your after\/ftplugin for htmldjango\r\n\"\r\n\"   ~\/.vim\/after\/ftplugin\/htmldjango\/template_textobjects.vim\r\n\"\r\n\"","install_details":"\"   Please ensure you have the above plugins installed as instructed\r\n\"   This file should be in your after\/ftplugin for django_template\r\n\"\r\n\"   ~\/.vim\/after\/ftplugin\/htmldjango\/template_textobjects.vim\r\n","5":"\"   Please ensure you have the above plugins installed as instructed\r\n\"   This file should be in your after\/ftplugin for django_template\r\n\"\r\n\"   ~\/.vim\/after\/ftplugin\/htmldjango\/template_textobjects.vim\r\n","first_name":"Michael","6":"Michael","last_name":"Brown","7":"Brown","releases":[{"0":"2999","vim_version":"7.0","1":"7.0","script_version":"0.7.5","2":"0.7.5","version_comment":"vim 7.4 compatibility fix. Thanks Daniel Hahler","3":"vim 7.4 compatibility fix. Thanks Daniel Hahler","package":"django-template-textobjects-0-7-5.zip","4":"django-template-textobjects-0-7-5.zip","src_id":"21940","5":"21940","creation_date":"1401079031","6":"1401079031"},{"0":"2999","vim_version":"7.0","1":"7.0","script_version":"0.7.4","2":"0.7.4","version_comment":"added django 1.4 {% elif %} matchit.vim pattern. thanks Youhei Nitta","3":"added django 1.4 {% elif %} matchit.vim pattern. thanks Youhei Nitta","package":"django-template-textobjects-master.zip","4":"django-template-textobjects-master.zip","src_id":"21656","5":"21656","creation_date":"1395646200","6":"1395646200"},{"0":"2999","vim_version":"7.2","1":"7.2","script_version":"0.7.3","2":"0.7.3","version_comment":"Added general closed tag and variable matching idv\/adv and idt\/adt\r\neg. dadt will delete-around-django-tag {% url foo as bar %}\r\nAdded idT\/adT for {% blocktrans %}","3":"Added general closed tag and variable matching idv\/adv and idt\/adt\r\neg. dadt will delete-around-django-tag {% url foo as bar %}\r\nAdded idT\/adT for {% blocktrans %}","package":"django-template-textobjects-master.tar.gz","4":"django-template-textobjects-master.tar.gz","src_id":"19099","5":"19099","creation_date":"1354593554","6":"1354593554"},{"0":"2999","vim_version":"7.2","1":"7.2","script_version":"0.2.1","2":"0.2.1","version_comment":"added idC\/adC for {% cache %}. comment fixes. fixed load issue when matchit.vim missing  - thanks aleprovencio","3":"added idC\/adC for {% cache %}. comment fixes. fixed load issue when matchit.vim missing  - thanks aleprovencio","package":"mjbrownie-django-template-textobjects-fc9c815.tar.gz","4":"mjbrownie-django-template-textobjects-fc9c815.tar.gz","src_id":"18423","5":"18423","creation_date":"1345259797","6":"1345259797"},{"0":"2999","vim_version":"7.0","1":"7.0","script_version":"0.2.0","2":"0.2.0","version_comment":"Fixed a bufnr bug affecting around mappings","3":"Fixed a bufnr bug affecting around mappings","package":"mjbrownie-django-template-textobjects-67c0f0f.zip","4":"mjbrownie-django-template-textobjects-67c0f0f.zip","src_id":"12602","5":"12602","creation_date":"1268312113","6":"1268312113"},{"0":"2999","vim_version":"7.0","1":"7.0","script_version":"0.2.0","2":"0.2.0","version_comment":"Improved nesting logic. Removed matchit dependancy","3":"Improved nesting logic. Removed matchit dependancy","package":"mjbrownie-django-template-textobjects-5ee23f9.zip","4":"mjbrownie-django-template-textobjects-5ee23f9.zip","src_id":"12597","5":"12597","creation_date":"1268300012","6":"1268300012"},{"0":"2999","vim_version":"7.0","1":"7.0","script_version":"0.1.1","2":"0.1.1","version_comment":"Fix for inner block visual grabbing }{ . no match handling","3":"Fix for inner block visual grabbing }{ . no match handling","package":"mjbrownie-django-template-textobjects-4ed2ec5.zip","4":"mjbrownie-django-template-textobjects-4ed2ec5.zip","src_id":"12527","5":"12527","creation_date":"1267420315","6":"1267420315"},{"0":"2999","vim_version":"7.0","1":"7.0","script_version":"0.1.0","2":"0.1.0","version_comment":"Initial Upload: Without git metafile","3":"Initial Upload: Without git metafile","package":"django-template-textobjects-0.10.zip","4":"django-template-textobjects-0.10.zip","src_id":"12522","5":"12522","creation_date":"1267364822","6":"1267364822"}]},"2998":{"script_id":"2998","0":"2998","script_name":"BackgroundColor.vim","1":"BackgroundColor.vim","script_type":"utility","2":"utility","summary":"Define a background color for your vim","3":"Define a background color for your vim","description":"BackgroundColor.vim only works, if your vim is compiled with signs-support.  If it is, you can use signs, to define a background color for your text.\r\n\r\nThis plugin defines these Commands:\r\n:Red Color the selected Range red\r\n:White Color the selected Range white\r\n:Yellow Color the selected Range yellow\r\n:Blue Color the selected Range blue\r\n:Green Color the selected range Green\r\n:Black Color the selected range Black\r\n:Custom1\r\n:Custom2\r\nColor the selected range with your defined Color1 or 2\r\nThose 2 commands are only defined, if you have specified a color for this command.\r\nYou can define a custom color using the 2 variables g:bg_color_custom1 and g:bg_color_custom2\r\n\r\n:Clear Clear the selected range\r\n:ClearAll Clear the whole buffer of all background colors.\r\n\r\nAll commands (excep :ClearAll, which only uses the whole buffer) accept a range, on which they operate. So you can use, e.g. :%Red to color the whole buffer red.\r\n\r\nI am not sure if this is really useful, but in case you find it usefull, please rate this plugin.","4":"BackgroundColor.vim only works, if your vim is compiled with signs-support.  If it is, you can use signs, to define a background color for your text.\r\n\r\nThis plugin defines these Commands:\r\n:Red Color the selected Range red\r\n:White Color the selected Range white\r\n:Yellow Color the selected Range yellow\r\n:Blue Color the selected Range blue\r\n:Green Color the selected range Green\r\n:Black Color the selected range Black\r\n:Custom1\r\n:Custom2\r\nColor the selected range with your defined Color1 or 2\r\nThose 2 commands are only defined, if you have specified a color for this command.\r\nYou can define a custom color using the 2 variables g:bg_color_custom1 and g:bg_color_custom2\r\n\r\n:Clear Clear the selected range\r\n:ClearAll Clear the whole buffer of all background colors.\r\n\r\nAll commands (excep :ClearAll, which only uses the whole buffer) accept a range, on which they operate. So you can use, e.g. :%Red to color the whole buffer red.\r\n\r\nI am not sure if this is really useful, but in case you find it usefull, please rate this plugin.","install_details":"simply put backgroundColor.vim in your plugin directory. (e.g. ~\/.vim\/plugin\/) Create directories, that do not exist currently.","5":"simply put backgroundColor.vim in your plugin directory. (e.g. ~\/.vim\/plugin\/) Create directories, that do not exist currently.","first_name":"Christian","6":"Christian","last_name":"Brabandt","7":"Brabandt","releases":[{"0":"2998","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"backgroundColor.vim","4":"backgroundColor.vim","src_id":"12516","5":"12516","creation_date":"1267307788","6":"1267307788"}]},"2997":{"script_id":"2997","0":"2997","script_name":"utlx_interwiki.vim","1":"utlx_interwiki.vim","script_type":"utility","2":"utility","summary":"A scheme that adds interwiki linking to the script UTL ","3":"A scheme that adds interwiki linking to the script UTL ","description":"A scheme for the vimscript#293 (UTL) that adds interwiki linking.\r\nRequires vimscript#293. By default it supports UTL version 3.0.\r\nTo use with UTL 2.0, see Customization below.\r\n\r\nA wiki can be defined anywhere in the current file like this:\r\n\r\n   [wp]: http:\/\/en.wikipedia.org\/wiki\r\n\r\nA link from the current file to a page on the wiki may look like this:\r\n\r\n   iw:\/\/wp\/Vim_(text_editor)\r\n\r\nBy placing the cursor on the link, and executing :Utl, the link will be\r\ninternally expanded to\r\n\r\n   http:\/\/en.wikipedia.org\/wiki\/Vim_(text_editor)\r\n\r\nand passed to UTL which will open the URL in the preferred program.\r\nSee vimscript#293 for more information.\r\n\r\nThe URL can contain a placeholder '%p' that will be replaced with\r\nthe path of an interwiki link, for example\r\n\r\n   [script]: http:\/\/www.vim.org\/scripts\/script.php?script_id=%p\r\n   'iw:\/\/script\/2997' --> http:\/\/www.vim.org\/scripts\/script.php?script_id=2997\r\n\r\n\r\nGlobal wikis can be defined in .vimrc:\r\n\r\n   let g:utlextra_interwikis = {\r\n      \\ 'LOG': ['\/path\/to\/log', '.txt'],\r\n      \\ 'google': 'http:\/\/www.google.com\/search?q=%p',\r\n      \\ }\r\n\r\nThis defines a wiki named LOG that is in the directory '\/path\/to\/log' and\r\nuses files with the extension '.txt'. To jump to a log entry from anywhere\r\nan URL like the following can be used:\r\n\r\n   iw:\/\/LOG\/201002#tn=2010-02-27\r\n   \r\nwhich will be expanded to:\r\n   \r\n   file:\/\/\/path\/to\/log\/201002.txt#tn=2010-02-27\r\n\r\nThe extension .txt is added only if the path in the URL (\/201002 in this case)\r\ndoesn't have one.\r\n\r\nIf at some point the log files are moved to another directory, all references\r\nto the log entries will be valid if the value for '\/path\/to\/log' is changed \r\nin g:utlextra_interwikis.\r\n\r\nThe second interwiki, 'google' displays the results of a google search. Because\r\nit doesn't have a default extension it is defined as a simple string.\r\nThe link iw:\/\/google\/vim+editor will be expanded to\r\n\r\n   http:\/\/www.google.com\/search=vim+editor\r\n\r\n('%p' is replaced by 'vim+editor') and displayed in the browser.\r\n\r\nThe format of g:utlextra_interwikis is similar to the format used in\r\nvimscript#861 (Viki\/Deplate). In fact if the 'intervikis' are defined\r\nfor Viki\/Deplate, they will be imported by this script (interwikis\r\ndefined in g:utlextra_interwikis take precedence).\r\n\r\nIf interwikis are defined globally and also in the current file, locally\r\ndefined interwikis take precedence.\r\n\r\nThe format of an interwiki definition is:\r\n\r\n   [name]: URL | default_extension\r\n\r\nwhere default_extension starts with a dot. The format may change in the future\r\nto avoid confilcts with other markup applications, for example:\r\n\r\n   [w=name]: URL | default_extension\r\n\r\n(please report confilcts and suggest alternatives on vim wiki).\r\n\r\nInterwikis can also be defined in comments, but only a limited set of\r\ncomments is currently supported and the feature has not been extensively\r\ntested:\r\n   \" [wiki]:...\r\n   * [wiki]:...\r\n   # [wiki]:...\r\n   \/\/ [wiki]:...\r\n   \/* [wiki]:...\r\n\r\nIf the interwiki URL uses an empty wikiname, the link will be transformed\r\nas a link inside the current wiki. The path of the current file will be\r\nmatched to all defined interwikis and if found, the settings for that wiki\r\nwill be used. If a wiki isn't defined, the target file will have the same\r\nextension as the current file (if the path in URL doesn't already have an\r\nextension).\r\n   \r\n   'iw:\/\/\/localfile'        --> .\/localfile.txt\r\n   'iw:\/\/\/localfile.viki'   --> .\/localfile.viki\r\n   'iw:\/\/.\/localfile'       --> .\/localfile.txt\r\n\r\n\r\nCustomization:\r\n\r\ng:utlextra_interwiki_scheme = 'iw'\r\n   Change the scheme to use instead of 'iw'. Multiple schemes can\r\n   be used for interwiki linking, for example 'iw,wiki'.\r\n\r\ng:utlextra_utl_version = 3\r\n   Which version of UTL is installed. The interface for defining\r\n   additional schemas handlded by UTL has changed between versions\r\n   2 and 3. This script supports version 3 by default.\r\n   Set to 2 to use with UTL 2.0.\r\n\r\ng:utlextra_import_viki = 1\r\n   Set to 1 to import interwikis from Viki\/Deplate.\r\n   Set to 0 to skip importation.\r\n\r\ng:utlextra_interwiki_match_case = 0\r\n   If set to 1, the exact case must be used for interwiki names.\r\n   If set to 0, first a case-sensitive match will be performed\r\n   and if it fails a case insensitive will be used.\r\n\r\n","4":"A scheme for the vimscript#293 (UTL) that adds interwiki linking.\r\nRequires vimscript#293. By default it supports UTL version 3.0.\r\nTo use with UTL 2.0, see Customization below.\r\n\r\nA wiki can be defined anywhere in the current file like this:\r\n\r\n   [wp]: http:\/\/en.wikipedia.org\/wiki\r\n\r\nA link from the current file to a page on the wiki may look like this:\r\n\r\n   iw:\/\/wp\/Vim_(text_editor)\r\n\r\nBy placing the cursor on the link, and executing :Utl, the link will be\r\ninternally expanded to\r\n\r\n   http:\/\/en.wikipedia.org\/wiki\/Vim_(text_editor)\r\n\r\nand passed to UTL which will open the URL in the preferred program.\r\nSee vimscript#293 for more information.\r\n\r\nThe URL can contain a placeholder '%p' that will be replaced with\r\nthe path of an interwiki link, for example\r\n\r\n   [script]: http:\/\/www.vim.org\/scripts\/script.php?script_id=%p\r\n   'iw:\/\/script\/2997' --> http:\/\/www.vim.org\/scripts\/script.php?script_id=2997\r\n\r\n\r\nGlobal wikis can be defined in .vimrc:\r\n\r\n   let g:utlextra_interwikis = {\r\n      \\ 'LOG': ['\/path\/to\/log', '.txt'],\r\n      \\ 'google': 'http:\/\/www.google.com\/search?q=%p',\r\n      \\ }\r\n\r\nThis defines a wiki named LOG that is in the directory '\/path\/to\/log' and\r\nuses files with the extension '.txt'. To jump to a log entry from anywhere\r\nan URL like the following can be used:\r\n\r\n   iw:\/\/LOG\/201002#tn=2010-02-27\r\n   \r\nwhich will be expanded to:\r\n   \r\n   file:\/\/\/path\/to\/log\/201002.txt#tn=2010-02-27\r\n\r\nThe extension .txt is added only if the path in the URL (\/201002 in this case)\r\ndoesn't have one.\r\n\r\nIf at some point the log files are moved to another directory, all references\r\nto the log entries will be valid if the value for '\/path\/to\/log' is changed \r\nin g:utlextra_interwikis.\r\n\r\nThe second interwiki, 'google' displays the results of a google search. Because\r\nit doesn't have a default extension it is defined as a simple string.\r\nThe link iw:\/\/google\/vim+editor will be expanded to\r\n\r\n   http:\/\/www.google.com\/search=vim+editor\r\n\r\n('%p' is replaced by 'vim+editor') and displayed in the browser.\r\n\r\nThe format of g:utlextra_interwikis is similar to the format used in\r\nvimscript#861 (Viki\/Deplate). In fact if the 'intervikis' are defined\r\nfor Viki\/Deplate, they will be imported by this script (interwikis\r\ndefined in g:utlextra_interwikis take precedence).\r\n\r\nIf interwikis are defined globally and also in the current file, locally\r\ndefined interwikis take precedence.\r\n\r\nThe format of an interwiki definition is:\r\n\r\n   [name]: URL | default_extension\r\n\r\nwhere default_extension starts with a dot. The format may change in the future\r\nto avoid confilcts with other markup applications, for example:\r\n\r\n   [w=name]: URL | default_extension\r\n\r\n(please report confilcts and suggest alternatives on vim wiki).\r\n\r\nInterwikis can also be defined in comments, but only a limited set of\r\ncomments is currently supported and the feature has not been extensively\r\ntested:\r\n   \" [wiki]:...\r\n   * [wiki]:...\r\n   # [wiki]:...\r\n   \/\/ [wiki]:...\r\n   \/* [wiki]:...\r\n\r\nIf the interwiki URL uses an empty wikiname, the link will be transformed\r\nas a link inside the current wiki. The path of the current file will be\r\nmatched to all defined interwikis and if found, the settings for that wiki\r\nwill be used. If a wiki isn't defined, the target file will have the same\r\nextension as the current file (if the path in URL doesn't already have an\r\nextension).\r\n   \r\n   'iw:\/\/\/localfile'        --> .\/localfile.txt\r\n   'iw:\/\/\/localfile.viki'   --> .\/localfile.viki\r\n   'iw:\/\/.\/localfile'       --> .\/localfile.txt\r\n\r\n\r\nCustomization:\r\n\r\ng:utlextra_interwiki_scheme = 'iw'\r\n   Change the scheme to use instead of 'iw'. Multiple schemes can\r\n   be used for interwiki linking, for example 'iw,wiki'.\r\n\r\ng:utlextra_utl_version = 3\r\n   Which version of UTL is installed. The interface for defining\r\n   additional schemas handlded by UTL has changed between versions\r\n   2 and 3. This script supports version 3 by default.\r\n   Set to 2 to use with UTL 2.0.\r\n\r\ng:utlextra_import_viki = 1\r\n   Set to 1 to import interwikis from Viki\/Deplate.\r\n   Set to 0 to skip importation.\r\n\r\ng:utlextra_interwiki_match_case = 0\r\n   If set to 1, the exact case must be used for interwiki names.\r\n   If set to 0, first a case-sensitive match will be performed\r\n   and if it fails a case insensitive will be used.\r\n\r\n","install_details":"Unpack into ~\/.vim directory.\r\n\r\nAdd the follwing line to .vimrc to specify the installed version of UTL:\r\n   let g:utlextra_utl_version = 2\r\n(you can check the version of UTL with :h utl)\r\n\r\nIf the wrong version of UTL is specified, you will get an error like:\r\n   E118: Too many arguments for function: Utl_AddressScheme_iw    \r\n\r\nPrerequisites:\r\n   * install vimscript#293 (UTL)\r\n","5":"Unpack into ~\/.vim directory.\r\n\r\nAdd the follwing line to .vimrc to specify the installed version of UTL:\r\n   let g:utlextra_utl_version = 2\r\n(you can check the version of UTL with :h utl)\r\n\r\nIf the wrong version of UTL is specified, you will get an error like:\r\n   E118: Too many arguments for function: Utl_AddressScheme_iw    \r\n\r\nPrerequisites:\r\n   * install vimscript#293 (UTL)\r\n","first_name":"Marko","6":"Marko","last_name":"Mahni\u010d","7":"Mahnič","releases":[{"0":"2997","vim_version":"7.0","1":"7.0","script_version":"0.4","2":"0.4","version_comment":"* documentation added\r\n* minor fixes","3":"* documentation added\r\n* minor fixes","package":"utlx_interwiki.zip","4":"utlx_interwiki.zip","src_id":"15035","5":"15035","creation_date":"1297978093","6":"1297978093"},{"0":"2997","vim_version":"7.0","1":"7.0","script_version":"0.3","2":"0.3","version_comment":"Added parameter %p to interwiki URL definition","3":"Added parameter %p to interwiki URL definition","package":"utlx_interwiki.zip","4":"utlx_interwiki.zip","src_id":"12524","5":"12524","creation_date":"1267388470","6":"1267388470"},{"0":"2997","vim_version":"7.0","1":"7.0","script_version":"0.2","2":"0.2","version_comment":"Added support for UTL 2.0","3":"Added support for UTL 2.0","package":"utlx_interwiki.zip","4":"utlx_interwiki.zip","src_id":"12517","5":"12517","creation_date":"1267345095","6":"1267345095"},{"0":"2997","vim_version":"7.2","1":"7.2","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"utlx_interwiki.zip","4":"utlx_interwiki.zip","src_id":"12515","5":"12515","creation_date":"1267296226","6":"1267296226"}]},"2996":{"script_id":"2996","0":"2996","script_name":"TranslateEnToCn","1":"TranslateEnToCn","script_type":"utility","2":"utility","summary":"translate english to chinese in vim","3":"translate english to chinese in vim","description":"put cursor on the english word in normal mode , then type :Trans , \r\nor in Visual-mode type :TransV ,\r\nI map the :Trans and :TransV to <Space>,just like \r\nnnoremap <Space> :Trans<CR>\r\nvnoremap <Space> <ESC>:TransV<CR>\r\nin .vimrc files.\r\nNow,Visual-mode only support 'v' and 'V','<C-V>' will be\r\ntreated same as 'v' mode\r\n\r\nTested in Gvim72 on WindowsXP\r\n","4":"put cursor on the english word in normal mode , then type :Trans , \r\nor in Visual-mode type :TransV ,\r\nI map the :Trans and :TransV to <Space>,just like \r\nnnoremap <Space> :Trans<CR>\r\nvnoremap <Space> <ESC>:TransV<CR>\r\nin .vimrc files.\r\nNow,Visual-mode only support 'v' and 'V','<C-V>' will be\r\ntreated same as 'v' mode\r\n\r\nTested in Gvim72 on WindowsXP\r\n","install_details":"drop it to plugin\r\nrequire python2.5+","5":"drop it to plugin\r\nrequire python2.5+","first_name":"sowill","6":"sowill","last_name":"cinderella","7":"cinderella","releases":[{"0":"2996","vim_version":"6.0","1":"6.0","script_version":"1.5","2":"1.5","version_comment":"support Visual Mode","3":"support Visual Mode","package":"translate.vim","4":"translate.vim","src_id":"12572","5":"12572","creation_date":"1267954485","6":"1267954485"},{"0":"2996","vim_version":"7.0","1":"7.0","script_version":"1.4","2":"1.4","version_comment":"Add tips when no result was found or no word under cursor","3":"Add tips when no result was found or no word under cursor","package":"translate.vim","4":"translate.vim","src_id":"12531","5":"12531","creation_date":"1267449641","6":"1267449641"},{"0":"2996","vim_version":"7.0","1":"7.0","script_version":"1.3","2":"1.3","version_comment":"fix the encoding bug","3":"fix the encoding bug","package":"translate.vim","4":"translate.vim","src_id":"12529","5":"12529","creation_date":"1267434833","6":"1267434833"},{"0":"2996","vim_version":"7.0","1":"7.0","script_version":"1.2","2":"1.2","version_comment":"set the fileformat to unix, so it can be used in linix","3":"set the fileformat to unix, so it can be used in linix","package":"translate.vim","4":"translate.vim","src_id":"12514","5":"12514","creation_date":"1267282109","6":"1267282109"},{"0":"2996","vim_version":"7.0","1":"7.0","script_version":"1.1","2":"1.1","version_comment":"Initial upload","3":"Initial upload","package":"translate.vim","4":"translate.vim","src_id":"12511","5":"12511","creation_date":"1267257331","6":"1267257331"}]},"2995":{"script_id":"2995","0":"2995","script_name":"colorselector","1":"colorselector","script_type":"utility","2":"utility","summary":"\n    provide an emacs-like colorscheme selector buffer.\n","3":"\n    provide an emacs-like colorscheme selector buffer.\n","description":"\n    provide an emacs-like colorscheme selector buffer.\n\n    see: http:\/\/github.com\/c9s\/colorselector.vim\n","4":"\n    provide an emacs-like colorscheme selector buffer.\n\n    see: http:\/\/github.com\/c9s\/colorselector.vim\n","install_details":"\n    cp plugin script to ~\/.vim\/plugin\/\n\n    or use Vimana.\n","5":"\n    cp plugin script to ~\/.vim\/plugin\/\n\n    or use Vimana.\n","first_name":"Yo-An","6":"Yo-An","last_name":"Lin","7":"Lin","releases":[{"0":"2995","vim_version":"7.0    7.2","1":"7.0    7.2","script_version":"0.1","2":"0.1","version_comment":"\n    basic commands","3":"\n    basic commands","package":"colorselector.vim","4":"colorselector.vim","src_id":"12594","5":"12594","creation_date":"1268255546","6":"1268255546"},{"0":"2995","vim_version":"7.0    7.2","1":"7.0    7.2","script_version":"0.1","2":"0.1","version_comment":"\n    basic commands","3":"\n    basic commands","package":"colorselector.vim","4":"colorselector.vim","src_id":"12532","5":"12532","creation_date":"1267454212","6":"1267454212"},{"0":"2995","vim_version":"7.0    7.2","1":"7.0    7.2","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"colorselector.tar.gz","4":"colorselector.tar.gz","src_id":"12510","5":"12510","creation_date":"1267250933","6":"1267250933"}]},"2994":{"script_id":"2994","0":"2994","script_name":"Rackup","1":"Rackup","script_type":"syntax","2":"syntax","summary":"Syntax file for Rackup (config.ru) files","3":"Syntax file for Rackup (config.ru) files","description":"It defines rackup files (*.ru) and turns on Ruby syntax highlighting on these files. Added \"use\" and \"run\" as keywords.\r\n\r\nIt also works nicely with tComment ( vimscript #1173 )\r\n\r\ninspired by the Gemfile syntax file by ujihisa ( vimscript #2912 )\r\n\r\n","4":"It defines rackup files (*.ru) and turns on Ruby syntax highlighting on these files. Added \"use\" and \"run\" as keywords.\r\n\r\nIt also works nicely with tComment ( vimscript #1173 )\r\n\r\ninspired by the Gemfile syntax file by ujihisa ( vimscript #2912 )\r\n\r\n","install_details":"You might want to add the file ~\/.vim\/ftdetect\/Rackup.vim:\r\nautocmd BufRead,BufNewFile *.ru set filetype=Rackup","5":"You might want to add the file ~\/.vim\/ftdetect\/Rackup.vim:\r\nautocmd BufRead,BufNewFile *.ru set filetype=Rackup","first_name":"iain","6":"iain","last_name":"hecker","7":"hecker","releases":[{"0":"2994","vim_version":"6.0","1":"6.0","script_version":"1","2":"1","version_comment":"Initial upload","3":"Initial upload","package":"Rackup.vim","4":"Rackup.vim","src_id":"12504","5":"12504","creation_date":"1267215837","6":"1267215837"}]},"2993":{"script_id":"2993","0":"2993","script_name":"ywtxt","1":"ywtxt","script_type":"utility","2":"utility","summary":"Ease vim to write plain documents.","3":"Ease vim to write plain documents.","description":"1  Introduce:\r\n   \r\n   Ease vim to write plain document. It's at the very early stage, with\r\n   some fancy highlights. Any advice is welcome. My email is:\r\n\r\n   ywupub AT gmail DOT com\r\n\r\n2  Usage:\r\n\r\n   Open a new file: test.ywtxt, done.\r\n\r\n3  ywtxt file format:\r\n3.1  Heading format:\r\n\r\nywtxt treats lines start with \"#  \" or \"1  \"(note the following 2\r\nspaces) as a 1st level heading, \"#.#  \" or \"1.1  \"(note the following 2\r\nspaces) as a 2nd level heading, so forth.\r\n\r\nLines started with optional spaces and \"%\" are treated as a comment\r\nline. Characters between *bold* will get bolded, \/italic\/ italic,\r\n_underlined_ underlined.\r\n\r\nTODO and NOTE in document will get highlighted.\r\n   \r\n\"Figure #.  \", \"Fig. #.  \", \"图 #.  \", \"Table #.  \",  \"表 #.  \",\r\n\"Figure #-#.  \", \"Fig. #-#.  \", \"图 #-#.  \", \"Table #-#.  \",  \"表 #-#.  \"\r\nwill make ywtxt know it's a figure\/table, and can generate the figures\/tables\r\nof contents for them(note there are 2 spaces following the \"#.\".\r\n\r\nThe first line in document with a trailing space is a title:\r\n        This is a title, note the spaces after the dot.  \r\n\r\nywtxt use foldmethod 'marker' for mom document, so everything you can do with vim folding marker also can be implemented with ywtxt.\r\n\r\n3.2  Snip support:\r\n\r\nHit <Ctrl-j> then s will prompt you insert a filetype of snip,\r\nyou can use <tab> to auto-complete the filetype name. The snip region\r\nwill get highlighted according to the syntax of it(if vim supports it).\r\nWarn, if you insert a filetype which vim doesn't support, you will meet\r\nerror warning when opening the file.\r\n\r\nNote: Trying to insert ywtxt filetype as a snip will make ywtxt's\r\nfolding fragible.\r\n\r\n3.3  Cross-references\r\n\r\nDefine a anchor: '[#anchor]' without the prefix '*', then hit <enter> on the\r\nstring \"*[path\/to\/file#anchor]\" will let you go to the anchor.\r\n\r\nHit <Enter> on the pattern \"*[path\/to\/file#anchor]\" in document will let you\r\ngo to the file and locate onto the \"[#anchor]\" position.\r\nFor example: \r\n    *[.\/mini2.ywtxt#string]\r\nWill go to mini2.ywtxt and locate on the anchor [#string].\r\n\r\nIf you omit the \"file\" part in the pattern, then ywtxt will try to\r\nlocate the position in the current document.\r\nFor example: \r\n    *[#string]\r\nWill go to the anchor [#string] in the current document.\r\n\r\nIf document doesn't contain [#string], ywtxt will warn you and go to normal\r\nstring \"string\".\r\n\r\n3.4  More highlightings\r\n\r\nThere are times, however, when the simple markup isn't flexible enough.\r\nIn such cases, You can use Txtfmt (The Vim Highlighter) to add arbitrary\r\nhighlighting to my journal entries. The trick is to set 'filetype' equal\r\nto ywtxt.txtfmt instead of ywtxt alone. The following screenshot shows\r\nthe result:\r\n    \r\n   http:\/\/txtfmt.webs.com\/ywtxt.htm\r\n    \r\nThe highlighting provided by Txtfmt is similar to \"rich text\" in a word\r\nprocessor: foreground\/background colors and all combinations of\r\nunderline, bold, italic, etc...\r\n    \r\nTxtfmt (The Vim Highlighter):\r\nhttp:\/\/www.vim.org\/scripts\/script.php?script_id=2208\r\n\r\n4  Key maps:\r\n4.1  Key maps for the normal window(mother file window):\r\n\r\n      <Tab>               Fold\/unfold. Under ^[keyword], echo the corresponding reference name. Under the lines in the bibliography section, jump to the citing point of the document.\r\n      <Enter>             Under ^[keyword] or the lines in the bibliography section, jump into the .bib file and located to the coressponding location.\r\n      \\t                  Open a table of contents(toc) window of the current document, it's named as \"_<file you're writing>_TOC_\" .\r\n      <Ctrl-j>            Prompt for inserting a new (parent\/current\/child\/other level heading)\/Non_export2html\/Reference\/Snip.\r\n      \\o                  Insert a current level heading line.\r\n      \\O                  Insert a parent level heading line.\r\n      \\q                  Close the toc window.\r\n      \\<tab>              Jump into the toc window without refreshing.\r\n\r\n4.2  key maps for insert mode\r\n      <Ctrl-j>            Prompt for inserting a new (parent\/current\/child\/other level heading)\/Non_export2html\/Reference\/Snip.\r\n      _{                  _{} insert a subscript.\r\n      ^{                  ^{} insert a superscript.\r\n      ^[                  ^[] insert a citation.\r\n\r\n4.3  key maps for toc window:\r\n\r\n      <Enter>             Jump into the coressponding location of the document.\r\n      <space>             Jump into the coressponding location of the document without leaving the toc window.\r\n      x                   Jump into the coressponding location of the document and close the toc window.\r\n      <Leader><tab>       Jump into the mother file window without changing the position.\r\n      q                   Close the toc window.\r\n      r                   Refresh the toc window.\r\n      Shift_H             Decrease the level of heading.\r\n      Shift_L             Increase the level of heading.\r\n      Shift_J             Move current heading region down.\r\n      Shift_K             Move current heading region up.\r\n      Shift_D             Delete current heading region, and put the content into register z.\r\n      Shift_Y             Yank current heading region, and put the content into register z.\r\n      Shift_S             Auto number the sections mark(#.) in mother file according to the toc's showing.\r\n      w                   Save the mother file.\r\n      u                   Undo the mother file.\r\n      ctrl_R              Redo the mother file.\r\n      Shift_E             Export the ywtxt file to simple html file.\r\n      Shift_X             Outline\/un-outline the document. (Not working yet)\r\n      Shift_j             Go to the next line and outline the document. (Not working yet)\r\n      Shift_k             Go to the previous line and outline the document. (Not working yet)\r\n      t                   Toggle the toc type: \"Con(t)ents\/(F)igures\/Ta(b)les\/(A)nchors\/(L)inks\".\r\n\r\n5  html export feature:\r\n\r\n   In toc window, hit <shift-e> will export .ywtxt to .html file, after\r\n   saved the new openning buffer of the generated html file, you can\r\n   open the html in your browser, or even copy and paste it into your\r\n   office suite to reserve the looking of .ywtxt.\r\n\r\n   All strings _{} will become subscript, ^{} superscript. Comment lines\r\n   will be deleted. [\/path\/to\/file.bmp] will display directly in\r\n   html(supports jpg, png, bmp and gif).\r\n\r\n   Hit <ctrl-j> then % will insert region mark: \"^% BEGIN_NOHTML {{{\", \"^% END_NOHTML }}}\". Regions between \"^% BEGIN_NOHTML {{{\", \"^% END_NOHTML }}}\" will not be exported to html. Warn!!!: please don't try to nested the region, otherwise you might break up your document!!!\r\n\r\n   Hint: You can export the .ywtxt to .html, then paste it into Microsoft Word, then the levels of heading will abey with the html.\r\n\r\n6  Misc vars:\r\n6.1  g:ywtxt_autonumber\r\n\r\nConfiguring auto-setting the heading number after creating the heading. Note if you feel it makes vim slow down, you's better disable it.\r\nExample: set g:ywtxt_autonumber=0\r\n\r\n6.2  g:ywtxt_browserapp\r\n\r\nConfigure the browser app for viewing the html after exported.\r\nYou must make sure browser app is runable.\r\nExample: set g:ywtxt_browserapp = 'opera'\r\n\r\n6.3  g:ywtxt_tocwidth\r\n\r\nConfiguration for toc window's width. Default is the document's 1\/4.\r\nExample: set g:ywtxt_tocwidth=20\r\n\r\n6.4  g:ywtxt_headings_hl\r\n\r\nSpecify the colors for headings, you must strictly follow the following pattern:\r\n\r\n    \\ 'heading level':[['color for dark term', 'color for light term'], ['color for dark gui',], ['color for light gui'],\r\n\r\notherwise, ywtxt will produce error.  Also note that the colors you specify must be ones that vim knows. The setting format is(example is the default setting) is:\r\n\r\n    let g:ywtxt_headings_hl = {\r\n                \\ '1':[['blue', 'blue'],['LightSkyBlue', 'Blue1']],\r\n                \\ '2':[['yellow', 'yellow'],['LightGoldenrod', 'DarkGoldenrod']],\r\n                \\ '3':[['cyan', 'cyan'],['Cyan1', 'Purple']],\r\n                \\ '4':[['red', 'red'],['red1', 'red']],\r\n                \\ '5':[['green', 'green'],['PaleGreen', 'ForestGreen']],\r\n                \\ '6':[['magenta', 'magenta'],['Aquamarine', 'CadetBlue']],\r\n                \\ '7':[['blue', 'blue'],['LightSteelBlue', 'Orchid']],\r\n                \\ '8':[['green', 'green'],['LightSalmon', 'RosyBrown']],\r\n                \\ '9':[['blue', 'blue'],['LightSkyBlue', 'Blue1']],\r\n                \\ '10':[['yellow', 'yellow'],['LightGoldenrod', 'DarkGoldenrod']],\r\n                \\}\r\n\r\nYou can add more highlighting levels than 10 as you wish.\r\n\r\nTIP: You can assign blank value for the default bg\/fg color in bold face.\r\n\r\nlet g:ywtxt_headings_hl = {\r\n            \\ '1':[['', ''],['', '']],\r\n            \\ '2':[['', ''],['', '']],\r\n            \\ '3':[['', ''],['', '']],\r\n            \\ '4':[['', ''],['', '']],\r\n            \\ '5':[['', ''],['', '']],\r\n            \\ '6':[['', ''],['', '']],\r\n            \\ '7':[['', ''],['', '']],\r\n            \\ '8':[['', ''],['', '']],\r\n            \\ '9':[['', ''],['', '']],\r\n            \\ '10':[['', ''],['', '']],\r\n            \\}\r\n\r\n6.5  g:ywtxt_2htmlpre_usercmds, g:ywtxt_2htmlpost_usercmds\r\n\r\nYou can run cmds before and after the 2html routine, format:\r\n\r\n    let g:ywtxt_2htmlpre_usercmds=['vim_cmd1', 'vim_cmd2']\r\n    let g:ywtxt_2htmlpost_usercmds=['vim_cmd3', 'vim_cmd4']\r\n\r\nfor example,\r\n\r\n    let g:ywtxt_2htmlpre_usercmds=['set nonumber']\r\n    let g:ywtxt_2htmlpost_usercmds=['set number']\r\n\r\nwill make the 2html routine disable the number the lines then back to 'number' option after 2html. However, if you want to do some modification operators, it's very dangrous, use at your own risk!!!\r\n7  Advanced features\r\n7.1  Customize section number style:\r\n\r\nFor global effect: add a line as the following line in your .vimrc:\r\n\r\n    let g:ywtxt_HeadingsPat = '\"Chapter #\" \"Section #\" \"#.\" \"#.#\"'\r\n\r\nFor buffer effect: Add a line into .ywtxt(Must add it from a start of line, no any space allowed before the '%'):\r\n\r\n    % HEADINGS \"Chapter #\" \"Section #\" \"#.\" \"#.#\"\r\n\r\nTo immune from the global effect for some files: Add a line into .ywtxt(Must add it from a start of line, no any space allowed before the '%'):\r\n\r\n    % HEADINGS NONE\r\n\r\nExplanation:\r\n\r\nIf you've defined the headings pattern as the above way, then next time you open the document,  ywtxt will use all(here is \"Chapter #\" \"Section #\" \"#.\") of patterns excluding the last one(here is \"#.#\") as the very first level headings' pattern, the last one is used for ywtxt to determine how to auto-generate the following deeper levels, in this example, the 1st level heading will be \"Chapter #  \", 2nd \"Section #  \", 3th \"#.  \", 4th '#.# ', 5th '#.#.# ', and so on(Note the 2 spaces after the heading). You can omit the last one be a ywtxt's known pattern, then ywtxt will auto-generate the levels from the last one you've specified with \"#.#\", \"#.#.#\", ..., if you want ywtxt to auto-generate with other level, then you have to specify the last one with ywtxt's known heading pattern, e.g.  \"#\", \"#.#\", \"#.#.#\"... Heading is always followed by 2 spaces(but you don't need to specify the space here, ywtxt always auto-inserts them for you.).\r\n\r\n7.2  include other files\r\n\r\n    Lines starting with '% input \/dir\/to\/file' will include another file when 2html. The feature is very limited at present, no proper heading syntax supporting.\r\n\r\n7.3  Advanced .bib file support:\r\n\r\n   Warn: It needs you have some basic knowledge on the bib file and its\r\n   format, if you haven't heard of it, please skip this section. ywtxt's\r\n   bib supporting is very limited, now it just fits for me, only works\r\n   for article class.\r\n\r\n7.3.1  Usage:\r\n\r\n      1) In .ywtxt, you can insert the text like '^[keyword1]' or\r\n      '^[keyword1, 2]' to mean referrig to a single or multiple references.\r\n      \"keyword1\" means the keyword in .bib file.\r\n\r\n      2) Add the following 2 lines into your foo.ywtxt file whereever you like:\r\n\r\n      % bibfile = '\/path\/to\/your\/bib\/file.bib'\r\n      % endbib\r\n\r\n      3) In toc window, hit <Shift-b> will generate the Bibliography in\r\n      between the lines of mensioned above for you.\r\n\r\n      Warn!!! everything between the above lines will be deleted, you've been warned!\r\n\r\n      You can\r\n      \r\n        let g:ywtxt_bib_nump = 0\r\n\r\n      to disable the [<number>] ahead of the reference list.\r\n\r\n      4) Under the ^[keyword], use <Tab> to show you the reference name,\r\n      under the lines in the Bibliography section, use <Tab> to go to the\r\n      citing location in the document.\r\n\r\n      Under the ^[keyword] or lines in the Bibliography section, use\r\n      <Enter> to jump into the .bib file and located under the\r\n      corresponding location.\r\n\r\n      After exporting to html, ^[keyword] will change into ^[<num>].\r\n\r\n7.3.2  multiple references sections:\r\n\r\nYou can use multiple references section, just be sure that every\r\nreferences section has the following two lines:\r\n\r\n      % bibfile = '\/path\/to\/your\/bib\/file.bib'\r\n      % endbib\r\n\r\n7.3.3  .bib format:\r\n\r\n      It has some restrictions with the bib file: every item must start at a new line, and be embraced by {}, ended with a comma ','. Every entry must be ended at a separated line with '}', following is an example:\r\n\r\n      @article{keyword1,\r\n      title = {title},\r\n      author = {author1 and author2},\r\n      journal = {journal},\r\n      volumn = {1},\r\n      number = {1},\r\n      year = {2010},\r\n      pages = {1--2},\r\n      }\r\n\r\n      @book{keyword2,\r\n      author = {author1 and author2},\r\n      address = {Nanjing},\r\n      publisher = {publisher},\r\n      year = {2010},\r\n      }\r\n\r\n      Customize bib entry type:\r\n\r\n      To customize your own types of bib entry, you need to let ywvim know all of them firstly:\r\n\r\n          let g:ywtxt_bib_entrytypes = [\"article\", \"book\"] : \r\n\r\n      Then specify the format for each bib entry that you have specified before, the format is a list: g:ywtxt_bib_entries_{type}, with the items [entry, trailing character] or [entry, heading character, traling character], the default in ywtxt is:\r\n\r\n          let g:ywtxt_bib_entries_article = [\r\n                      \\[\"author\",\". \"],\r\n                      \\[\"title\",\". \"],\r\n                      \\[\"journal\",\", \"],\r\n                      \\[\"year\",\", \"],\r\n                      \\[\"volume\",\"\"],\r\n                      \\[\"number\",\"(\", \") :\"],\r\n                      \\[\"pages\",\". \"],\r\n                      \\]\r\n          let s:ywtxt_bib_entries_book = [\r\n                      \\[\"author\",\". \"],\r\n                      \\[\"title\",\". \"],\r\n                      \\[\"address\",\": \"],\r\n                      \\[\"publisher\",\", \"],\r\n                      \\[\"year\",\". \"],\r\n                      \\]\r\n\r\n8  Thanks\r\n\r\n   txtbrowser[http:\/\/www.vim.org\/scripts\/script.php?script_id=2899]'s author Guoyooo Ping for the inspiration.\r\n\r\n9  Todoes:\r\n   1) Support to bib input's auto-completion and other input\r\n   auto-completions\r\n\r\n   2) To integrate vimwiki's table support.","4":"1  Introduce:\r\n   \r\n   Ease vim to write plain document. It's at the very early stage, with\r\n   some fancy highlights. Any advice is welcome. My email is:\r\n\r\n   ywupub AT gmail DOT com\r\n\r\n2  Usage:\r\n\r\n   Open a new file: test.ywtxt, done.\r\n\r\n3  ywtxt file format:\r\n3.1  Heading format:\r\n\r\nywtxt treats lines start with \"#  \" or \"1  \"(note the following 2\r\nspaces) as a 1st level heading, \"#.#  \" or \"1.1  \"(note the following 2\r\nspaces) as a 2nd level heading, so forth.\r\n\r\nLines started with optional spaces and \"%\" are treated as a comment\r\nline. Characters between *bold* will get bolded, \/italic\/ italic,\r\n_underlined_ underlined.\r\n\r\nTODO and NOTE in document will get highlighted.\r\n   \r\n\"Figure #.  \", \"Fig. #.  \", \"图 #.  \", \"Table #.  \",  \"表 #.  \",\r\n\"Figure #-#.  \", \"Fig. #-#.  \", \"图 #-#.  \", \"Table #-#.  \",  \"表 #-#.  \"\r\nwill make ywtxt know it's a figure\/table, and can generate the figures\/tables\r\nof contents for them(note there are 2 spaces following the \"#.\".\r\n\r\nThe first line in document with a trailing space is a title:\r\n        This is a title, note the spaces after the dot.  \r\n\r\nywtxt use foldmethod 'marker' for mom document, so everything you can do with vim folding marker also can be implemented with ywtxt.\r\n\r\n3.2  Snip support:\r\n\r\nHit <Ctrl-j> then s will prompt you insert a filetype of snip,\r\nyou can use <tab> to auto-complete the filetype name. The snip region\r\nwill get highlighted according to the syntax of it(if vim supports it).\r\nWarn, if you insert a filetype which vim doesn't support, you will meet\r\nerror warning when opening the file.\r\n\r\nNote: Trying to insert ywtxt filetype as a snip will make ywtxt's\r\nfolding fragible.\r\n\r\n3.3  Cross-references\r\n\r\nDefine a anchor: '[#anchor]' without the prefix '*', then hit <enter> on the\r\nstring \"*[path\/to\/file#anchor]\" will let you go to the anchor.\r\n\r\nHit <Enter> on the pattern \"*[path\/to\/file#anchor]\" in document will let you\r\ngo to the file and locate onto the \"[#anchor]\" position.\r\nFor example: \r\n    *[.\/mini2.ywtxt#string]\r\nWill go to mini2.ywtxt and locate on the anchor [#string].\r\n\r\nIf you omit the \"file\" part in the pattern, then ywtxt will try to\r\nlocate the position in the current document.\r\nFor example: \r\n    *[#string]\r\nWill go to the anchor [#string] in the current document.\r\n\r\nIf document doesn't contain [#string], ywtxt will warn you and go to normal\r\nstring \"string\".\r\n\r\n3.4  More highlightings\r\n\r\nThere are times, however, when the simple markup isn't flexible enough.\r\nIn such cases, You can use Txtfmt (The Vim Highlighter) to add arbitrary\r\nhighlighting to my journal entries. The trick is to set 'filetype' equal\r\nto ywtxt.txtfmt instead of ywtxt alone. The following screenshot shows\r\nthe result:\r\n    \r\n   http:\/\/txtfmt.webs.com\/ywtxt.htm\r\n    \r\nThe highlighting provided by Txtfmt is similar to \"rich text\" in a word\r\nprocessor: foreground\/background colors and all combinations of\r\nunderline, bold, italic, etc...\r\n    \r\nTxtfmt (The Vim Highlighter):\r\nhttp:\/\/www.vim.org\/scripts\/script.php?script_id=2208\r\n\r\n4  Key maps:\r\n4.1  Key maps for the normal window(mother file window):\r\n\r\n      <Tab>               Fold\/unfold. Under ^[keyword], echo the corresponding reference name. Under the lines in the bibliography section, jump to the citing point of the document.\r\n      <Enter>             Under ^[keyword] or the lines in the bibliography section, jump into the .bib file and located to the coressponding location.\r\n      \\t                  Open a table of contents(toc) window of the current document, it's named as \"_<file you're writing>_TOC_\" .\r\n      <Ctrl-j>            Prompt for inserting a new (parent\/current\/child\/other level heading)\/Non_export2html\/Reference\/Snip.\r\n      \\o                  Insert a current level heading line.\r\n      \\O                  Insert a parent level heading line.\r\n      \\q                  Close the toc window.\r\n      \\<tab>              Jump into the toc window without refreshing.\r\n\r\n4.2  key maps for insert mode\r\n      <Ctrl-j>            Prompt for inserting a new (parent\/current\/child\/other level heading)\/Non_export2html\/Reference\/Snip.\r\n      _{                  _{} insert a subscript.\r\n      ^{                  ^{} insert a superscript.\r\n      ^[                  ^[] insert a citation.\r\n\r\n4.3  key maps for toc window:\r\n\r\n      <Enter>             Jump into the coressponding location of the document.\r\n      <space>             Jump into the coressponding location of the document without leaving the toc window.\r\n      x                   Jump into the coressponding location of the document and close the toc window.\r\n      <Leader><tab>       Jump into the mother file window without changing the position.\r\n      q                   Close the toc window.\r\n      r                   Refresh the toc window.\r\n      Shift_H             Decrease the level of heading.\r\n      Shift_L             Increase the level of heading.\r\n      Shift_J             Move current heading region down.\r\n      Shift_K             Move current heading region up.\r\n      Shift_D             Delete current heading region, and put the content into register z.\r\n      Shift_Y             Yank current heading region, and put the content into register z.\r\n      Shift_S             Auto number the sections mark(#.) in mother file according to the toc's showing.\r\n      w                   Save the mother file.\r\n      u                   Undo the mother file.\r\n      ctrl_R              Redo the mother file.\r\n      Shift_E             Export the ywtxt file to simple html file.\r\n      Shift_X             Outline\/un-outline the document. (Not working yet)\r\n      Shift_j             Go to the next line and outline the document. (Not working yet)\r\n      Shift_k             Go to the previous line and outline the document. (Not working yet)\r\n      t                   Toggle the toc type: \"Con(t)ents\/(F)igures\/Ta(b)les\/(A)nchors\/(L)inks\".\r\n\r\n5  html export feature:\r\n\r\n   In toc window, hit <shift-e> will export .ywtxt to .html file, after\r\n   saved the new openning buffer of the generated html file, you can\r\n   open the html in your browser, or even copy and paste it into your\r\n   office suite to reserve the looking of .ywtxt.\r\n\r\n   All strings _{} will become subscript, ^{} superscript. Comment lines\r\n   will be deleted. [\/path\/to\/file.bmp] will display directly in\r\n   html(supports jpg, png, bmp and gif).\r\n\r\n   Hit <ctrl-j> then % will insert region mark: \"^% BEGIN_NOHTML {{{\", \"^% END_NOHTML }}}\". Regions between \"^% BEGIN_NOHTML {{{\", \"^% END_NOHTML }}}\" will not be exported to html. Warn!!!: please don't try to nested the region, otherwise you might break up your document!!!\r\n\r\n   Hint: You can export the .ywtxt to .html, then paste it into Microsoft Word, then the levels of heading will abey with the html.\r\n\r\n6  Misc vars:\r\n6.1  g:ywtxt_autonumber\r\n\r\nConfiguring auto-setting the heading number after creating the heading. Note if you feel it makes vim slow down, you's better disable it.\r\nExample: set g:ywtxt_autonumber=0\r\n\r\n6.2  g:ywtxt_browserapp\r\n\r\nConfigure the browser app for viewing the html after exported.\r\nYou must make sure browser app is runable.\r\nExample: set g:ywtxt_browserapp = 'opera'\r\n\r\n6.3  g:ywtxt_tocwidth\r\n\r\nConfiguration for toc window's width. Default is the document's 1\/4.\r\nExample: set g:ywtxt_tocwidth=20\r\n\r\n6.4  g:ywtxt_headings_hl\r\n\r\nSpecify the colors for headings, you must strictly follow the following pattern:\r\n\r\n    \\ 'heading level':[['color for dark term', 'color for light term'], ['color for dark gui',], ['color for light gui'],\r\n\r\notherwise, ywtxt will produce error.  Also note that the colors you specify must be ones that vim knows. The setting format is(example is the default setting) is:\r\n\r\n    let g:ywtxt_headings_hl = {\r\n                \\ '1':[['blue', 'blue'],['LightSkyBlue', 'Blue1']],\r\n                \\ '2':[['yellow', 'yellow'],['LightGoldenrod', 'DarkGoldenrod']],\r\n                \\ '3':[['cyan', 'cyan'],['Cyan1', 'Purple']],\r\n                \\ '4':[['red', 'red'],['red1', 'red']],\r\n                \\ '5':[['green', 'green'],['PaleGreen', 'ForestGreen']],\r\n                \\ '6':[['magenta', 'magenta'],['Aquamarine', 'CadetBlue']],\r\n                \\ '7':[['blue', 'blue'],['LightSteelBlue', 'Orchid']],\r\n                \\ '8':[['green', 'green'],['LightSalmon', 'RosyBrown']],\r\n                \\ '9':[['blue', 'blue'],['LightSkyBlue', 'Blue1']],\r\n                \\ '10':[['yellow', 'yellow'],['LightGoldenrod', 'DarkGoldenrod']],\r\n                \\}\r\n\r\nYou can add more highlighting levels than 10 as you wish.\r\n\r\nTIP: You can assign blank value for the default bg\/fg color in bold face.\r\n\r\nlet g:ywtxt_headings_hl = {\r\n            \\ '1':[['', ''],['', '']],\r\n            \\ '2':[['', ''],['', '']],\r\n            \\ '3':[['', ''],['', '']],\r\n            \\ '4':[['', ''],['', '']],\r\n            \\ '5':[['', ''],['', '']],\r\n            \\ '6':[['', ''],['', '']],\r\n            \\ '7':[['', ''],['', '']],\r\n            \\ '8':[['', ''],['', '']],\r\n            \\ '9':[['', ''],['', '']],\r\n            \\ '10':[['', ''],['', '']],\r\n            \\}\r\n\r\n6.5  g:ywtxt_2htmlpre_usercmds, g:ywtxt_2htmlpost_usercmds\r\n\r\nYou can run cmds before and after the 2html routine, format:\r\n\r\n    let g:ywtxt_2htmlpre_usercmds=['vim_cmd1', 'vim_cmd2']\r\n    let g:ywtxt_2htmlpost_usercmds=['vim_cmd3', 'vim_cmd4']\r\n\r\nfor example,\r\n\r\n    let g:ywtxt_2htmlpre_usercmds=['set nonumber']\r\n    let g:ywtxt_2htmlpost_usercmds=['set number']\r\n\r\nwill make the 2html routine disable the number the lines then back to 'number' option after 2html. However, if you want to do some modification operators, it's very dangrous, use at your own risk!!!\r\n7  Advanced features\r\n7.1  Customize section number style:\r\n\r\nFor global effect: add a line as the following line in your .vimrc:\r\n\r\n    let g:ywtxt_HeadingsPat = '\"Chapter #\" \"Section #\" \"#.\" \"#.#\"'\r\n\r\nFor buffer effect: Add a line into .ywtxt(Must add it from a start of line, no any space allowed before the '%'):\r\n\r\n    % HEADINGS \"Chapter #\" \"Section #\" \"#.\" \"#.#\"\r\n\r\nTo immune from the global effect for some files: Add a line into .ywtxt(Must add it from a start of line, no any space allowed before the '%'):\r\n\r\n    % HEADINGS NONE\r\n\r\nExplanation:\r\n\r\nIf you've defined the headings pattern as the above way, then next time you open the document,  ywtxt will use all(here is \"Chapter #\" \"Section #\" \"#.\") of patterns excluding the last one(here is \"#.#\") as the very first level headings' pattern, the last one is used for ywtxt to determine how to auto-generate the following deeper levels, in this example, the 1st level heading will be \"Chapter #  \", 2nd \"Section #  \", 3th \"#.  \", 4th '#.# ', 5th '#.#.# ', and so on(Note the 2 spaces after the heading). You can omit the last one be a ywtxt's known pattern, then ywtxt will auto-generate the levels from the last one you've specified with \"#.#\", \"#.#.#\", ..., if you want ywtxt to auto-generate with other level, then you have to specify the last one with ywtxt's known heading pattern, e.g.  \"#\", \"#.#\", \"#.#.#\"... Heading is always followed by 2 spaces(but you don't need to specify the space here, ywtxt always auto-inserts them for you.).\r\n\r\n7.2  include other files\r\n\r\n    Lines starting with '% input \/dir\/to\/file' will include another file when 2html. The feature is very limited at present, no proper heading syntax supporting.\r\n\r\n7.3  Advanced .bib file support:\r\n\r\n   Warn: It needs you have some basic knowledge on the bib file and its\r\n   format, if you haven't heard of it, please skip this section. ywtxt's\r\n   bib supporting is very limited, now it just fits for me, only works\r\n   for article class.\r\n\r\n7.3.1  Usage:\r\n\r\n      1) In .ywtxt, you can insert the text like '^[keyword1]' or\r\n      '^[keyword1, 2]' to mean referrig to a single or multiple references.\r\n      \"keyword1\" means the keyword in .bib file.\r\n\r\n      2) Add the following 2 lines into your foo.ywtxt file whereever you like:\r\n\r\n      % bibfile = '\/path\/to\/your\/bib\/file.bib'\r\n      % endbib\r\n\r\n      3) In toc window, hit <Shift-b> will generate the Bibliography in\r\n      between the lines of mensioned above for you.\r\n\r\n      Warn!!! everything between the above lines will be deleted, you've been warned!\r\n\r\n      You can\r\n      \r\n        let g:ywtxt_bib_nump = 0\r\n\r\n      to disable the [<number>] ahead of the reference list.\r\n\r\n      4) Under the ^[keyword], use <Tab> to show you the reference name,\r\n      under the lines in the Bibliography section, use <Tab> to go to the\r\n      citing location in the document.\r\n\r\n      Under the ^[keyword] or lines in the Bibliography section, use\r\n      <Enter> to jump into the .bib file and located under the\r\n      corresponding location.\r\n\r\n      After exporting to html, ^[keyword] will change into ^[<num>].\r\n\r\n7.3.2  multiple references sections:\r\n\r\nYou can use multiple references section, just be sure that every\r\nreferences section has the following two lines:\r\n\r\n      % bibfile = '\/path\/to\/your\/bib\/file.bib'\r\n      % endbib\r\n\r\n7.3.3  .bib format:\r\n\r\n      It has some restrictions with the bib file: every item must start at a new line, and be embraced by {}, ended with a comma ','. Every entry must be ended at a separated line with '}', following is an example:\r\n\r\n      @article{keyword1,\r\n      title = {title},\r\n      author = {author1 and author2},\r\n      journal = {journal},\r\n      volumn = {1},\r\n      number = {1},\r\n      year = {2010},\r\n      pages = {1--2},\r\n      }\r\n\r\n      @book{keyword2,\r\n      author = {author1 and author2},\r\n      address = {Nanjing},\r\n      publisher = {publisher},\r\n      year = {2010},\r\n      }\r\n\r\n      Customize bib entry type:\r\n\r\n      To customize your own types of bib entry, you need to let ywvim know all of them firstly:\r\n\r\n          let g:ywtxt_bib_entrytypes = [\"article\", \"book\"] : \r\n\r\n      Then specify the format for each bib entry that you have specified before, the format is a list: g:ywtxt_bib_entries_{type}, with the items [entry, trailing character] or [entry, heading character, traling character], the default in ywtxt is:\r\n\r\n          let g:ywtxt_bib_entries_article = [\r\n                      \\[\"author\",\". \"],\r\n                      \\[\"title\",\". \"],\r\n                      \\[\"journal\",\", \"],\r\n                      \\[\"year\",\", \"],\r\n                      \\[\"volume\",\"\"],\r\n                      \\[\"number\",\"(\", \") :\"],\r\n                      \\[\"pages\",\". \"],\r\n                      \\]\r\n          let s:ywtxt_bib_entries_book = [\r\n                      \\[\"author\",\". \"],\r\n                      \\[\"title\",\". \"],\r\n                      \\[\"address\",\": \"],\r\n                      \\[\"publisher\",\", \"],\r\n                      \\[\"year\",\". \"],\r\n                      \\]\r\n\r\n8  Thanks\r\n\r\n   txtbrowser[http:\/\/www.vim.org\/scripts\/script.php?script_id=2899]'s author Guoyooo Ping for the inspiration.\r\n\r\n9  Todoes:\r\n   1) Support to bib input's auto-completion and other input\r\n   auto-completions\r\n\r\n   2) To integrate vimwiki's table support.","install_details":"Installation: Extract the downloaded script tarball into ~\/.vim\/, it has following files:\r\n\r\n    plugin\/ywtxt.vim\r\n    ftplugin\/ywtxt.vim\r\n    syntax\/ywtxt.vim\r\n\r\nAdd the following line into ~\/.vimrc:\r\n\r\n    au BufRead,BufNewFile *.ywtxt set ft=ywtxt\r\n\r\nDone. If you don't like the file name's suffix .ywtxt, you can change it to whatever you want.\r\n\r\nAn Example file mini.ywtxt:\r\n=======> mini.ywtxt start <========\r\n                                  Title \r\n\r\n% HEADINGS \"Chapter #\" \"Section #\" \"#.\" \"#.#\"\r\n\r\nChapter 1  Hello\r\n\r\nFig. #.  wfwefe\r\n\r\n*[#anchor]\r\n\r\nSection 1  Bla\r\n% [#anchor]\r\n\r\nFigure #.  wfwefef\r\nRefer to ^[bibkw]\r\nRefer to ^[bibkw3]\r\n\r\nSection 2  References\r\n% bibfile = '.\/mini.bib'\r\n[1] Ref Title 1. Yue Wu 1. Ref Jou 1. 2010. 1(2) :3--4. \r\n[2] Ref Title 3. Yue Wu 3. Ref Jou 3. 2010. 1(2) :3--4. \r\n% endbib\r\n\r\nChapter 2  Hello2\r\n\r\nTable #.  wfwefef\r\n\r\nSection 1  Bla2\r\n\r\nRefer to ^[bibkw2]\r\nRefer to ^[bibkw]\r\nRefer to ^[bibkw3]\r\nRefer to the book^[bibkw4].\r\n\r\nSection 2  References\r\n\r\n% bibfile = '.\/mini.bib'\r\n[1] Ref Title 2. Yue Wu 2. Ref Jou 2. 2010. 1(2) :3--4. \r\n[2] Ref Title 1. Yue Wu 1. Ref Jou 1. 2010. 1(2) :3--4. \r\n[3] Ref Title 3. Yue Wu 3. Ref Jou 3. 2010. 1(2) :3--4. \r\n[4] Yue Wu book. Book1. Pekin: publisher, 2010. \r\n% endbib\r\n\r\n% vim:ft=ywtxt:\r\n=======> mini.ywtxt end <========\r\n \r\n An Example file mini.bib:\r\n=======> mini.bib start <========\r\n@article{bibkw,\r\n    author = {Yue Wu 1},\r\n    title = {Ref Title 1},\r\n    journal = {Ref Jou 1},\r\n    year = {2010},\r\n    volume = {1},\r\n    number = {2},\r\n    pages = {3--4},\r\n}\r\n@article{bibkw2,\r\n    author = {Yue Wu 2},\r\n    title = {Ref Title 2},\r\n    journal = {Ref Jou 2},\r\n    year = {2010},\r\n    volume = {1},\r\n    number = {2},\r\n    pages = {3--4},\r\n}\r\n@article{bibkw3,\r\n    author = {Yue Wu 3},\r\n    title = {Ref Title 3},\r\n    journal = {Ref Jou 3},\r\n    year = {2010},\r\n    volume = {1},\r\n    number = {2},\r\n    pages = {3--4},\r\n}\r\n@book{bibkw4,\r\n    author = {Yue Wu book},\r\n    title = {Book1},\r\n    address = {Pekin},\r\n    publisher = {publisher},\r\n    year = {2010},\r\n}\r\n=======> mini.bib end <========","5":"Installation: Extract the downloaded script tarball into ~\/.vim\/, it has following files:\r\n\r\n    plugin\/ywtxt.vim\r\n    ftplugin\/ywtxt.vim\r\n    syntax\/ywtxt.vim\r\n\r\nAdd the following line into ~\/.vimrc:\r\n\r\n    au BufRead,BufNewFile *.ywtxt set ft=ywtxt\r\n\r\nDone. If you don't like the file name's suffix .ywtxt, you can change it to whatever you want.\r\n\r\nAn Example file mini.ywtxt:\r\n=======> mini.ywtxt start <========\r\n                                  Title \r\n\r\n% HEADINGS \"Chapter #\" \"Section #\" \"#.\" \"#.#\"\r\n\r\nChapter 1  Hello\r\n\r\nFig. #.  wfwefe\r\n\r\n*[#anchor]\r\n\r\nSection 1  Bla\r\n% [#anchor]\r\n\r\nFigure #.  wfwefef\r\nRefer to ^[bibkw]\r\nRefer to ^[bibkw3]\r\n\r\nSection 2  References\r\n% bibfile = '.\/mini.bib'\r\n[1] Ref Title 1. Yue Wu 1. Ref Jou 1. 2010. 1(2) :3--4. \r\n[2] Ref Title 3. Yue Wu 3. Ref Jou 3. 2010. 1(2) :3--4. \r\n% endbib\r\n\r\nChapter 2  Hello2\r\n\r\nTable #.  wfwefef\r\n\r\nSection 1  Bla2\r\n\r\nRefer to ^[bibkw2]\r\nRefer to ^[bibkw]\r\nRefer to ^[bibkw3]\r\nRefer to the book^[bibkw4].\r\n\r\nSection 2  References\r\n\r\n% bibfile = '.\/mini.bib'\r\n[1] Ref Title 2. Yue Wu 2. Ref Jou 2. 2010. 1(2) :3--4. \r\n[2] Ref Title 1. Yue Wu 1. Ref Jou 1. 2010. 1(2) :3--4. \r\n[3] Ref Title 3. Yue Wu 3. Ref Jou 3. 2010. 1(2) :3--4. \r\n[4] Yue Wu book. Book1. Pekin: publisher, 2010. \r\n% endbib\r\n\r\n% vim:ft=ywtxt:\r\n=======> mini.ywtxt end <========\r\n \r\n An Example file mini.bib:\r\n=======> mini.bib start <========\r\n@article{bibkw,\r\n    author = {Yue Wu 1},\r\n    title = {Ref Title 1},\r\n    journal = {Ref Jou 1},\r\n    year = {2010},\r\n    volume = {1},\r\n    number = {2},\r\n    pages = {3--4},\r\n}\r\n@article{bibkw2,\r\n    author = {Yue Wu 2},\r\n    title = {Ref Title 2},\r\n    journal = {Ref Jou 2},\r\n    year = {2010},\r\n    volume = {1},\r\n    number = {2},\r\n    pages = {3--4},\r\n}\r\n@article{bibkw3,\r\n    author = {Yue Wu 3},\r\n    title = {Ref Title 3},\r\n    journal = {Ref Jou 3},\r\n    year = {2010},\r\n    volume = {1},\r\n    number = {2},\r\n    pages = {3--4},\r\n}\r\n@book{bibkw4,\r\n    author = {Yue Wu book},\r\n    title = {Book1},\r\n    address = {Pekin},\r\n    publisher = {publisher},\r\n    year = {2010},\r\n}\r\n=======> mini.bib end <========","first_name":"Yue","6":"Yue","last_name":"Wu","7":"Wu","releases":[{"0":"2993","vim_version":"7.0","1":"7.0","script_version":"0.18","2":"0.18","version_comment":"1. Greatly improved: speed issue for large document.\r\n\r\n2. Major changed: foldmethod changed from 'syntax' to 'marker' in documnet for speed issue, so you need to append '{{{' and '}}} to lines '^% BEGIN.*$' and '^% END.*$' respectively to fold your old format of ywtxt documents. Method:\r\n:%s\/^\\(% BEGIN.*\\)\/\\1 {{{\/c\r\n:%s\/^\\(% END.*\\)\/\\1 }}}\/c\r\nSorry for inconvenience!\r\n\r\n3. Fixed: bug in wrong location when inserting nohtml region.\r\n\r\n4. Changed: heading creation will prompt you to insert heading text.\r\n\r\n5. Improved toc generation speed.","3":"1. Greatly improved: speed issue for large document.\r\n\r\n2. Major changed: foldmethod changed from 'syntax' to 'marker' in documnet for speed issue, so you need to append '{{{' and '}}} to lines '^% BEGIN.*$' and '^% END.*$' respectively to fold your old format of ywtxt documents. Method:\r\n:%s\/^\\(% BEGIN.*\\)\/\\1 {{{\/c\r\n:%s\/^\\(% END.*\\)\/\\1 }}}\/c\r\nSorry for inconvenience!\r\n\r\n3. Fixed: bug in wrong location when inserting nohtml region.\r\n\r\n4. Changed: heading creation will prompt you to insert heading text.\r\n\r\n5. Improved toc generation speed.","package":"ywtxt_0.18.tar.bz2","4":"ywtxt_0.18.tar.bz2","src_id":"13460","5":"13460","creation_date":"1280812331","6":"1280812331"},{"0":"2993","vim_version":"7.0","1":"7.0","script_version":"0.17","2":"0.17","version_comment":"1. Added: In toc window, keymap J, K to move a heading region up\/down. D\/Y to delete\/yank a heading region, and put deleted\/yanked content into \"z.\r\n2. Changed: key map to re-indent heading level in toc window \\> -> L; \\< -> H\r\n3. Changed: Doesn't fold document's headings for speed issue.\r\n4. Changed: g:ywtxt_autonumber is on by default, heading creation will set section number.\r\n5. Improved: g:ywtxt_headings_hl, now you can assign blank value for the default bg\/fg color in bold face.\r\n6. Improved: heading syntax.\r\n7. Fixed: bug in heading creation.\r\n8. Fixed: export2html bug in nohtml region","3":"1. Added: In toc window, keymap J, K to move a heading region up\/down. D\/Y to delete\/yank a heading region, and put deleted\/yanked content into \"z.\r\n2. Changed: key map to re-indent heading level in toc window \\> -> L; \\< -> H\r\n3. Changed: Doesn't fold document's headings for speed issue.\r\n4. Changed: g:ywtxt_autonumber is on by default, heading creation will set section number.\r\n5. Improved: g:ywtxt_headings_hl, now you can assign blank value for the default bg\/fg color in bold face.\r\n6. Improved: heading syntax.\r\n7. Fixed: bug in heading creation.\r\n8. Fixed: export2html bug in nohtml region","package":"ywtxt_0.17.tar.bz2","4":"ywtxt_0.17.tar.bz2","src_id":"13446","5":"13446","creation_date":"1280560385","6":"1280560385"},{"0":"2993","vim_version":"7.0","1":"7.0","script_version":"0.16_1","2":"0.16_1","version_comment":"Added support for non_export2html region \"^% BEGIN_NOHTML\", \"^% END_NOHTML\"(keymap: <ctrl-o>%).\r\n\r\nImproved the function for switching the types of toc: \"Con(t)ents\/(F)igures\/Ta(b)les\/(A)nchors\/(L)inks\"\r\n\r\nFixed non-working keymap for <space> in toc window.\r\n\r\nFixed reindentation bug with customized headings.\r\n\r\nFixed a heading level bug with the customized heading which contains \"#.\".\r\n","3":"Added support for non_export2html region \"^% BEGIN_NOHTML\", \"^% END_NOHTML\"(keymap: <ctrl-o>%).\r\n\r\nImproved the function for switching the types of toc: \"Con(t)ents\/(F)igures\/Ta(b)les\/(A)nchors\/(L)inks\"\r\n\r\nFixed non-working keymap for <space> in toc window.\r\n\r\nFixed reindentation bug with customized headings.\r\n\r\nFixed a heading level bug with the customized heading which contains \"#.\".\r\n","package":"ywtxt_0.16_1.tar.bz2","4":"ywtxt_0.16_1.tar.bz2","src_id":"13061","5":"13061","creation_date":"1274960567","6":"1274960567"},{"0":"2993","vim_version":"7.0","1":"7.0","script_version":"0.16","2":"0.16","version_comment":"1) Changed the reference region format, please see document for details.\r\n\r\n2) Abandoned var: g:ywtxt_biblioname.\r\n\r\n3) Added operator to create arbitrary heading level(<Ctrl-j> o).\r\n\r\n4) Added syntax for title: The first line in document with a trailing space.\r\n\r\n5) Added book type to the default bib type.\r\n[1] Authors. Book name. City: publisher, year.\r\n\r\n6) Changed export-to-html routine, now will generate a tmp file firstly(foo.ywtxt -> foo_ywtxt -> foo_ywtxt.html -> rm foo_ywtxt).\r\n\r\n7) Added vars: g:ywtxt_2htmlpre_usercmds, g:ywtxt_2htmlpost_usercmds, see doc for details(Section 6.5).\r\n\r\n8) Added var: g:ywtxt_bib_nump to set\/unset [<number>] in References list when generating references. Default: 1.\r\n\r\n9) Added feature '% input file', to include another file when 2html. The feature is very limited, no proper heading syntax supporting.\r\n\r\n10) Improved syntax for bold\/underlined\/italic chars in-between * around the Chinese charactors.\r\n\r\n11) Improved the cursor postion in the document after doing operators in toc window.\r\n\r\n12) Fixed locating back to the document after finishing exporting to html.\r\n\r\n13) Fixed non-working of changing bib keywords to numbers while exporting to html.\r\n\r\n14) Fixed a bug of heading recorgnization.\r\n\r\n15) Fixed a bug with the function of the bib file finding.\r\n\r\n16) Fixed error while hit <tab> on '~'.\r\n\r\n17) Fixed error related to <tab> (reference recognization).","3":"1) Changed the reference region format, please see document for details.\r\n\r\n2) Abandoned var: g:ywtxt_biblioname.\r\n\r\n3) Added operator to create arbitrary heading level(<Ctrl-j> o).\r\n\r\n4) Added syntax for title: The first line in document with a trailing space.\r\n\r\n5) Added book type to the default bib type.\r\n[1] Authors. Book name. City: publisher, year.\r\n\r\n6) Changed export-to-html routine, now will generate a tmp file firstly(foo.ywtxt -> foo_ywtxt -> foo_ywtxt.html -> rm foo_ywtxt).\r\n\r\n7) Added vars: g:ywtxt_2htmlpre_usercmds, g:ywtxt_2htmlpost_usercmds, see doc for details(Section 6.5).\r\n\r\n8) Added var: g:ywtxt_bib_nump to set\/unset [<number>] in References list when generating references. Default: 1.\r\n\r\n9) Added feature '% input file', to include another file when 2html. The feature is very limited, no proper heading syntax supporting.\r\n\r\n10) Improved syntax for bold\/underlined\/italic chars in-between * around the Chinese charactors.\r\n\r\n11) Improved the cursor postion in the document after doing operators in toc window.\r\n\r\n12) Fixed locating back to the document after finishing exporting to html.\r\n\r\n13) Fixed non-working of changing bib keywords to numbers while exporting to html.\r\n\r\n14) Fixed a bug of heading recorgnization.\r\n\r\n15) Fixed a bug with the function of the bib file finding.\r\n\r\n16) Fixed error while hit <tab> on '~'.\r\n\r\n17) Fixed error related to <tab> (reference recognization).","package":"ywtxt_0.16.tar.bz2","4":"ywtxt_0.16.tar.bz2","src_id":"13039","5":"13039","creation_date":"1274431286","6":"1274431286"},{"0":"2993","vim_version":"7.0","1":"7.0","script_version":"0.15_6","2":"0.15_6","version_comment":"1) Changed, removed and integrated keymaps for creating headings\/reference\/snip, works both in normal\/insert mode(<Ctrl-j>).\r\n2) Added var for configuring auto-setting the heading number after creating a heading(set g:ywtxt_autonumber=1). Note it will be slow.\r\n3) Improved syntax bug for bold\/underlined\/italic\/.","3":"1) Changed, removed and integrated keymaps for creating headings\/reference\/snip, works both in normal\/insert mode(<Ctrl-j>).\r\n2) Added var for configuring auto-setting the heading number after creating a heading(set g:ywtxt_autonumber=1). Note it will be slow.\r\n3) Improved syntax bug for bold\/underlined\/italic\/.","package":"ywtxt_0.15_6.tar.bz2","4":"ywtxt_0.15_6.tar.bz2","src_id":"12890","5":"12890","creation_date":"1272024913","6":"1272024913"},{"0":"2993","vim_version":"7.0","1":"7.0","script_version":"0.15_5","2":"0.15_5","version_comment":"Fixed a bug of location with <space>, thanks Zhang Xin's good catch.","3":"Fixed a bug of location with <space>, thanks Zhang Xin's good catch.","package":"ywtxt_0.15_5.tar.bz2","4":"ywtxt_0.15_5.tar.bz2","src_id":"12779","5":"12779","creation_date":"1270306343","6":"1270306343"},{"0":"2993","vim_version":"7.0","1":"7.0","script_version":"0.15_4","2":"0.15_4","version_comment":"Fixed snip inserting bug which is brought by the last update.","3":"Fixed snip inserting bug which is brought by the last update.","package":"ywtxt_0.15_4.tar.bz2","4":"ywtxt_0.15_4.tar.bz2","src_id":"12778","5":"12778","creation_date":"1270305474","6":"1270305474"},{"0":"2993","vim_version":"7.0","1":"7.0","script_version":"0.15_3","2":"0.15_3","version_comment":"1) Added syntax for figure\/table(figure #-#.; table #-#.)\r\n2) Fixed comment region bug.\r\n3) Removed setting to nowrap in toc window.\r\n4) Removed '[' as a file name charactor, now <C-x><C-f> can complete the file name after '['.","3":"1) Added syntax for figure\/table(figure #-#.; table #-#.)\r\n2) Fixed comment region bug.\r\n3) Removed setting to nowrap in toc window.\r\n4) Removed '[' as a file name charactor, now <C-x><C-f> can complete the file name after '['.","package":"ywtxt_0.15_3.tar.bz2","4":"ywtxt_0.15_3.tar.bz2","src_id":"12777","5":"12777","creation_date":"1270298529","6":"1270298529"},{"0":"2993","vim_version":"7.0","1":"7.0","script_version":"0.15_2","2":"0.15_2","version_comment":"1) Improved anchor-locating behavior for Chinese and English.\r\n2) Changed highlight for anchor.\r\n3) Added keymap for insert mode: _{ _{}","3":"1) Improved anchor-locating behavior for Chinese and English.\r\n2) Changed highlight for anchor.\r\n3) Added keymap for insert mode: _{ _{}","package":"ywtxt_0.15_2.tar.bz2","4":"ywtxt_0.15_2.tar.bz2","src_id":"12704","5":"12704","creation_date":"1269521922","6":"1269521922"},{"0":"2993","vim_version":"7.0","1":"7.0","script_version":"0.15_1","2":"0.15_1","version_comment":"1) Added definition for anchor \"[#anchor]\", please see the section cross-references in document. Thanks for Adrien Pied Pi\u00c3\u00a9rard's suggestion.\r\n2) Removed keymap in insert mode: _(_{}). Thanks for Adrien Pied Pi\u00c3\u00a9rard's suggestion.\r\n3) Added syntax highligh for anchor. Thanks for Adrien Pied Pi\u00c3\u00a9rard's suggestion.\r\n4) Removed textwidth setting.\r\n5) Suppressed new file msg when open toc window.","3":"1) Added definition for anchor \"[#anchor]\", please see the section cross-references in document. Thanks for Adrien Pied Pi\u00c3\u00a9rard's suggestion.\r\n2) Removed keymap in insert mode: _(_{}). Thanks for Adrien Pied Pi\u00c3\u00a9rard's suggestion.\r\n3) Added syntax highligh for anchor. Thanks for Adrien Pied Pi\u00c3\u00a9rard's suggestion.\r\n4) Removed textwidth setting.\r\n5) Suppressed new file msg when open toc window.","package":"ywtxt_0.15_1.tar.bz2","4":"ywtxt_0.15_1.tar.bz2","src_id":"12696","5":"12696","creation_date":"1269430328","6":"1269430328"},{"0":"2993","vim_version":"7.0","1":"7.0","script_version":"0.15","2":"0.15","version_comment":"1) Added var g:ywtxt_browserapp to support opening html directly after export to html, see section \"Misc vars\" for detail.\r\n2) Added support for Cross-references(*[file#anchor]). Please see the section \"ywtxt file format\" for details.","3":"1) Added var g:ywtxt_browserapp to support opening html directly after export to html, see section \"Misc vars\" for detail.\r\n2) Added support for Cross-references(*[file#anchor]). Please see the section \"ywtxt file format\" for details.","package":"ywtxt_0.15.tar.bz2","4":"ywtxt_0.15.tar.bz2","src_id":"12683","5":"12683","creation_date":"1269319565","6":"1269319565"},{"0":"2993","vim_version":"7.0","1":"7.0","script_version":"0.14_2","2":"0.14_2","version_comment":"1) Fixed outline\/unoutline in toc window.\r\n2) Suppressed the not pattern found warning when exporting to html.","3":"1) Fixed outline\/unoutline in toc window.\r\n2) Suppressed the not pattern found warning when exporting to html.","package":"ywtxt_0.14_2.tar.bz2","4":"ywtxt_0.14_2.tar.bz2","src_id":"12674","5":"12674","creation_date":"1269253654","6":"1269253654"},{"0":"2993","vim_version":"7.0","1":"7.0","script_version":"0.14_1","2":"0.14_1","version_comment":"Fixed toc window not refresh after undo\/redo","3":"Fixed toc window not refresh after undo\/redo","package":"ywtxt_0.14_1.tar.bz2","4":"ywtxt_0.14_1.tar.bz2","src_id":"12665","5":"12665","creation_date":"1269007533","6":"1269007533"},{"0":"2993","vim_version":"7.0","1":"7.0","script_version":"0.14","2":"0.14","version_comment":"1) Added configurable heading highlighting(g:ywtxt_headings_hl) support. Please see the document for details.\r\n2) Added encoding declaration in syntax\/ywtxt.vim and ftplugin\/ywtxt.vim, to prevent encoding issue. thanks zhangxin's report.\r\n3) Improved italic, bold, and underlined definition to allow blank spaces in between.","3":"1) Added configurable heading highlighting(g:ywtxt_headings_hl) support. Please see the document for details.\r\n2) Added encoding declaration in syntax\/ywtxt.vim and ftplugin\/ywtxt.vim, to prevent encoding issue. thanks zhangxin's report.\r\n3) Improved italic, bold, and underlined definition to allow blank spaces in between.","package":"ywtxt_0.14.tar.bz2","4":"ywtxt_0.14.tar.bz2","src_id":"12663","5":"12663","creation_date":"1268995391","6":"1268995391"},{"0":"2993","vim_version":"7.0","1":"7.0","script_version":"0.13_2","2":"0.13_2","version_comment":"1) Fixed errors caused by operations on toc window title line. Thanks pengo's catching.\r\n2) Speeded up a little for the toc window opening and jumping.\r\n3) Added syntax: \"图 #.  \",  \"表 #.  \".","3":"1) Fixed errors caused by operations on toc window title line. Thanks pengo's catching.\r\n2) Speeded up a little for the toc window opening and jumping.\r\n3) Added syntax: \"图 #.  \",  \"表 #.  \".","package":"ywtxt_0.13_2.tar.bz2","4":"ywtxt_0.13_2.tar.bz2","src_id":"12636","5":"12636","creation_date":"1268743126","6":"1268743126"},{"0":"2993","vim_version":"7.0","1":"7.0","script_version":"0.13_1","2":"0.13_1","version_comment":"Fixed bug: operations in toc winodow unworking.","3":"Fixed bug: operations in toc winodow unworking.","package":"ywtxt_0.13_1.tar.bz2","4":"ywtxt_0.13_1.tar.bz2","src_id":"12631","5":"12631","creation_date":"1268643236","6":"1268643236"},{"0":"2993","vim_version":"7.0","1":"7.0","script_version":"0.13","2":"0.13","version_comment":"1) Added feature: Customized heading pattern can be set globally(g:ywtxt_HeadingsPat), please see the advanced features in the document for details.\r\n2) Improved: The setting for customized heading pattern needn't force user to specify the last pattern to be a ywtxt known pattern.\r\n3) Improved the handling of the title line in toc window.\r\n4) Improved uncontinious section support, thanks for zhangxin's catch.\r\n5) Ignore the unproper user setting for customized section pattern.\r\n6) Fixed a bug in keymap shift-x: Outline\/un-outline.","3":"1) Added feature: Customized heading pattern can be set globally(g:ywtxt_HeadingsPat), please see the advanced features in the document for details.\r\n2) Improved: The setting for customized heading pattern needn't force user to specify the last pattern to be a ywtxt known pattern.\r\n3) Improved the handling of the title line in toc window.\r\n4) Improved uncontinious section support, thanks for zhangxin's catch.\r\n5) Ignore the unproper user setting for customized section pattern.\r\n6) Fixed a bug in keymap shift-x: Outline\/un-outline.","package":"ywtxt_0.13.tar.bz2","4":"ywtxt_0.13.tar.bz2","src_id":"12630","5":"12630","creation_date":"1268635473","6":"1268635473"},{"0":"2993","vim_version":"7.0","1":"7.0","script_version":"0.12_3","2":"0.12_3","version_comment":"Fixed a bug in customize section pattern which has spaces in name.","3":"Fixed a bug in customize section pattern which has spaces in name.","package":"ywtxt_0.12_3.tar.bz2","4":"ywtxt_0.12_3.tar.bz2","src_id":"12620","5":"12620","creation_date":"1268491252","6":"1268491252"},{"0":"2993","vim_version":"7.0","1":"7.0","script_version":"0.12_2","2":"0.12_2","version_comment":"Fixed a bug in bib generation.\r\nFixed a heading syntax bug.","3":"Fixed a bug in bib generation.\r\nFixed a heading syntax bug.","package":"ywtxt_0.12_2.tar.bz2","4":"ywtxt_0.12_2.tar.bz2","src_id":"12619","5":"12619","creation_date":"1268490468","6":"1268490468"},{"0":"2993","vim_version":"7.0","1":"7.0","script_version":"0.12_1","2":"0.12_1","version_comment":"Fixed bug: toc location uncorrectly.\r\nFixed reindent bug.\r\n","3":"Fixed bug: toc location uncorrectly.\r\nFixed reindent bug.\r\n","package":"ywtxt_0.12_1.tar.bz2","4":"ywtxt_0.12_1.tar.bz2","src_id":"12618","5":"12618","creation_date":"1268473947","6":"1268473947"},{"0":"2993","vim_version":"7.0","1":"7.0","script_version":"0.12","2":"0.12","version_comment":"1) Added feature to customize section number style, please see the advanced features section in document.\r\n\r\n2) Improved snip folding and syntax supportings.\r\n\r\n3) Improved the displaying of toc.\r\n\r\n4) Improved keymap in toc window: Shift-x fold\/unfold all.\r\nThanks for pengo's suggestion.\r\n\r\n5) Added warning before trying to generate references region.\r\nThanks for pengo's suggestion.\r\n\r\n6) Improved the uncontinuous headings handling.\r\nthanks for pengo's catching.\r\n\r\n7) Changed: Syntax for figure and table to:\r\n\"Figure #.  \"\r\n\"Fig. #.  \"\r\n\"Table #.  \"\r\n\r\n8) Added support on Figure\/table of contents. Hit 't' in toc window to toggle\r\ntoc's type.\r\n\r\n9) Added support for the Multiple reference sections. Please see the\r\nadvanced feature in document.","3":"1) Added feature to customize section number style, please see the advanced features section in document.\r\n\r\n2) Improved snip folding and syntax supportings.\r\n\r\n3) Improved the displaying of toc.\r\n\r\n4) Improved keymap in toc window: Shift-x fold\/unfold all.\r\nThanks for pengo's suggestion.\r\n\r\n5) Added warning before trying to generate references region.\r\nThanks for pengo's suggestion.\r\n\r\n6) Improved the uncontinuous headings handling.\r\nthanks for pengo's catching.\r\n\r\n7) Changed: Syntax for figure and table to:\r\n\"Figure #.  \"\r\n\"Fig. #.  \"\r\n\"Table #.  \"\r\n\r\n8) Added support on Figure\/table of contents. Hit 't' in toc window to toggle\r\ntoc's type.\r\n\r\n9) Added support for the Multiple reference sections. Please see the\r\nadvanced feature in document.","package":"ywtxt_0.12.tar.bz2","4":"ywtxt_0.12.tar.bz2","src_id":"12617","5":"12617","creation_date":"1268462031","6":"1268462031"},{"0":"2993","vim_version":"7.0","1":"7.0","script_version":"0.11_2","2":"0.11_2","version_comment":"1) Fixed non-working toc window.\r\n2) Fixed references region identification. Thanks for pengo's catching.\r\n3) Improved toc window intendation. Thanks for pengo's suggestion.","3":"1) Fixed non-working toc window.\r\n2) Fixed references region identification. Thanks for pengo's catching.\r\n3) Improved toc window intendation. Thanks for pengo's suggestion.","package":"ywtxt_0.11_2.tar.bz2","4":"ywtxt_0.11_2.tar.bz2","src_id":"12589","5":"12589","creation_date":"1268217628","6":"1268217628"},{"0":"2993","vim_version":"7.0","1":"7.0","script_version":"0.11_1","2":"0.11_1","version_comment":"Fixed folding and toc highlighting bugs.","3":"Fixed folding and toc highlighting bugs.","package":"ywtxt_0.11_1.tar.bz2","4":"ywtxt_0.11_1.tar.bz2","src_id":"12588","5":"12588","creation_date":"1268208117","6":"1268208117"},{"0":"2993","vim_version":"7.0","1":"7.0","script_version":"0.11","2":"0.11","version_comment":"1) NOTE! Imcompatible changed!!!: heading format changed again till 0.10: \"1  \", \"#.#  \"(note the following has 2 spaces!)\r\nHow to upgrade:\r\n0.10 user: :call Ywtxt_old2new()<CR> This function will be abandoned in next release.\r\nearlier than 0.10 user: :%s\/^\\(\\%(\\%(#\\|\\d\\+\\)\\.\\)*\\)\\(#\\|\\d\\+\\)\\.\\(\\s\\)\/\\1\\2\\3 \/g\r\n2) snip support. <Leader>I inserts snip, auto-completion supported. See the document for details.\r\n3) Added keymaps for toc window: J, K: outline next\/previous line.\r\n4) Abandoned indentation feature.\r\n5) Fixed html export bugs. Thanks for pengo's great catch.\r\n6) note and todo strings get highlighted anywhere.\r\n7) Added done(DONE) syntax.\r\n8) Optimized the toc display.","3":"1) NOTE! Imcompatible changed!!!: heading format changed again till 0.10: \"1  \", \"#.#  \"(note the following has 2 spaces!)\r\nHow to upgrade:\r\n0.10 user: :call Ywtxt_old2new()<CR> This function will be abandoned in next release.\r\nearlier than 0.10 user: :%s\/^\\(\\%(\\%(#\\|\\d\\+\\)\\.\\)*\\)\\(#\\|\\d\\+\\)\\.\\(\\s\\)\/\\1\\2\\3 \/g\r\n2) snip support. <Leader>I inserts snip, auto-completion supported. See the document for details.\r\n3) Added keymaps for toc window: J, K: outline next\/previous line.\r\n4) Abandoned indentation feature.\r\n5) Fixed html export bugs. Thanks for pengo's great catch.\r\n6) note and todo strings get highlighted anywhere.\r\n7) Added done(DONE) syntax.\r\n8) Optimized the toc display.","package":"ywtxt_0.11.tar.bz2","4":"ywtxt_0.11.tar.bz2","src_id":"12587","5":"12587","creation_date":"1268207549","6":"1268207549"},{"0":"2993","vim_version":"7.0","1":"7.0","script_version":"0.10_3","2":"0.10_3","version_comment":"This will be the last 0.10 series verion, please see all 0.10 series's changelog and the updated document to get how to update. Note again! you can use :call Ywtxt_old2new() then ggVG= to reformat the old version, but please care the inproperly reformat!!! Ywtxt_old2new() will be abandoned in next version! You've been warned.\r\n1) Fixed a heading determination error.","3":"This will be the last 0.10 series verion, please see all 0.10 series's changelog and the updated document to get how to update. Note again! you can use :call Ywtxt_old2new() then ggVG= to reformat the old version, but please care the inproperly reformat!!! Ywtxt_old2new() will be abandoned in next version! You've been warned.\r\n1) Fixed a heading determination error.","package":"ywtxt_0.10_3.tar.bz2","4":"ywtxt_0.10_3.tar.bz2","src_id":"12586","5":"12586","creation_date":"1268183214","6":"1268183214"},{"0":"2993","vim_version":"7.0","1":"7.0","script_version":"0.10_2","2":"0.10_2","version_comment":"This will be the last 0.10 series verion, please see all 0.10 series's changelog and the updated document to get how to update. Note again! you can use :call Ywtxt_old2new() then ggVG= to reformat the old version, but please care the inproperly reformat!!! Ywtxt_old2new() will be abandoned in next version! You've been warned.\r\n1) Improved heading determination\r\n2) Improved Indentation function","3":"This will be the last 0.10 series verion, please see all 0.10 series's changelog and the updated document to get how to update. Note again! you can use :call Ywtxt_old2new() then ggVG= to reformat the old version, but please care the inproperly reformat!!! Ywtxt_old2new() will be abandoned in next version! You've been warned.\r\n1) Improved heading determination\r\n2) Improved Indentation function","package":"ywtxt_0.10_2.tar.bz2","4":"ywtxt_0.10_2.tar.bz2","src_id":"12585","5":"12585","creation_date":"1268182808","6":"1268182808"},{"0":"2993","vim_version":"7.0","1":"7.0","script_version":"0.10_1","2":"0.10_1","version_comment":"Fixed: a serious toc heading bug.\r\nNote!!! Please see the version *0.10*'s changelog and the updated document for detailed changes, otherwise ywtxt will not work properly with the older format in the new version!","3":"Fixed: a serious toc heading bug.\r\nNote!!! Please see the version *0.10*'s changelog and the updated document for detailed changes, otherwise ywtxt will not work properly with the older format in the new version!","package":"ywtxt_0.10_1.tar.bz2","4":"ywtxt_0.10_1.tar.bz2","src_id":"12584","5":"12584","creation_date":"1268178723","6":"1268178723"},{"0":"2993","vim_version":"7.0","1":"7.0","script_version":"0.10","2":"0.10","version_comment":"1) Uncompatible Changed!: Heading format changed to \"#. \", \"   #.# \", old user can use :call Ywtxt_old2new() to reformat the old format of ywtxt, note that function Ywtxt_old2new() will abandon in next version.\r\n2) Widened: Comment region definition: Lines starts with optional spaces and % considered as comment.\r\n3) Changed: Delete comment region when export to html.\r\n4) Added: Markup for superscript(^{}) and subscript(_{})\r\n5) Added: imap for _(_{}), ^{(^{}) and ^[(^[])\r\n6) Added: g:ywtxt_tocwidth for configuration of toc window's width. Thanks for pengo's suggestion.\r\n7) Improved: Highlight note and todo strings in headings. Add \"注意\" in note syntax. Thanks for pengo's suggestion.\r\n8) Added: markup of \"[\/path\/to\/local.pic]\" (jpg, png, bmp, gif) can be viewed in exporting html directly.\r\n9) Changed: bibliography's name to references.\r\n10) Added: Auto Indent.\r\n11) Improved: toc window cursorline.\r\n12) Improved: reindent func.","3":"1) Uncompatible Changed!: Heading format changed to \"#. \", \"   #.# \", old user can use :call Ywtxt_old2new() to reformat the old format of ywtxt, note that function Ywtxt_old2new() will abandon in next version.\r\n2) Widened: Comment region definition: Lines starts with optional spaces and % considered as comment.\r\n3) Changed: Delete comment region when export to html.\r\n4) Added: Markup for superscript(^{}) and subscript(_{})\r\n5) Added: imap for _(_{}), ^{(^{}) and ^[(^[])\r\n6) Added: g:ywtxt_tocwidth for configuration of toc window's width. Thanks for pengo's suggestion.\r\n7) Improved: Highlight note and todo strings in headings. Add \"注意\" in note syntax. Thanks for pengo's suggestion.\r\n8) Added: markup of \"[\/path\/to\/local.pic]\" (jpg, png, bmp, gif) can be viewed in exporting html directly.\r\n9) Changed: bibliography's name to references.\r\n10) Added: Auto Indent.\r\n11) Improved: toc window cursorline.\r\n12) Improved: reindent func.","package":"ywtxt_0.10.tar.bz2","4":"ywtxt_0.10.tar.bz2","src_id":"12581","5":"12581","creation_date":"1268149090","6":"1268149090"},{"0":"2993","vim_version":"7.0","1":"7.0","script_version":"0.9","2":"0.9","version_comment":"1) Added simple html export. Hit <Shift-e> in toc window will export .ywtxt to .html, set the references keyword to number in document.\r\n2) Added keymap in toc window: <Shift-X> will outline the heading in document.\r\n3) Changed definition of keymap <space>: open the heading in document without leaving the toc window.\r\n4) Abandoned the :call Ywtxt_GenBibliography() way to generate bibliography, use <Shift-b> in toc window instead.\r\n5) Improved reindent function.\r\n6) Suppressed the no folding found warning of <tab>.","3":"1) Added simple html export. Hit <Shift-e> in toc window will export .ywtxt to .html, set the references keyword to number in document.\r\n2) Added keymap in toc window: <Shift-X> will outline the heading in document.\r\n3) Changed definition of keymap <space>: open the heading in document without leaving the toc window.\r\n4) Abandoned the :call Ywtxt_GenBibliography() way to generate bibliography, use <Shift-b> in toc window instead.\r\n5) Improved reindent function.\r\n6) Suppressed the no folding found warning of <tab>.","package":"ywtxt_0.9.tar.bz2","4":"ywtxt_0.9.tar.bz2","src_id":"12573","5":"12573","creation_date":"1267967532","6":"1267967532"},{"0":"2993","vim_version":"7.0","1":"7.0","script_version":"0.8","2":"0.8","version_comment":"1) Changed toc window openning from horizotally to vertically.\r\n2) Added syntax for TODO, NOTE.","3":"1) Changed toc window openning from horizotally to vertically.\r\n2) Added syntax for TODO, NOTE.","package":"ywtxt_0.8.tar.bz2","4":"ywtxt_0.8.tar.bz2","src_id":"12559","5":"12559","creation_date":"1267800768","6":"1267800768"},{"0":"2993","vim_version":"7.0","1":"7.0","script_version":"0.7","2":"0.7","version_comment":"1) Added support and keymaps for bibliography generation and viewing, please see the advancd feature in the document for details.\r\n2) Improved the header creation funtion.\r\n3) Added syntax for Figure capture.","3":"1) Added support and keymaps for bibliography generation and viewing, please see the advancd feature in the document for details.\r\n2) Improved the header creation funtion.\r\n3) Added syntax for Figure capture.","package":"ywtxt_0.7.tar.bz2","4":"ywtxt_0.7.tar.bz2","src_id":"12540","5":"12540","creation_date":"1267541316","6":"1267541316"},{"0":"2993","vim_version":"7.0","1":"7.0","script_version":"0.6","2":"0.6","version_comment":"1) Added feature: auto number the section numbers in file according to the toc, and added key maps in toc window(S, w, <leader><tab>, <C-r>, u) and normal file(<leader><tab>). See the document for details.\r\n2) Added syntax for bold(*b*), underline(_u_) and italic(\/i\/).\r\n3) Fixed cursor location of toc window.\r\n4) Cleaned some unused vars.","3":"1) Added feature: auto number the section numbers in file according to the toc, and added key maps in toc window(S, w, <leader><tab>, <C-r>, u) and normal file(<leader><tab>). See the document for details.\r\n2) Added syntax for bold(*b*), underline(_u_) and italic(\/i\/).\r\n3) Fixed cursor location of toc window.\r\n4) Cleaned some unused vars.","package":"ywtxt_0.6.tar.bz2","4":"ywtxt_0.6.tar.bz2","src_id":"12519","5":"12519","creation_date":"1267355063","6":"1267355063"},{"0":"2993","vim_version":"7.0","1":"7.0","script_version":"0.5","2":"0.5","version_comment":"1. Improved the toc refresh.\r\n2. Removed the dangerous saving operation when changing the level of header.","3":"1. Improved the toc refresh.\r\n2. Removed the dangerous saving operation when changing the level of header.","package":"ywtxt_0.5.tar.bz2","4":"ywtxt_0.5.tar.bz2","src_id":"12513","5":"12513","creation_date":"1267269648","6":"1267269648"},{"0":"2993","vim_version":"7.0","1":"7.0","script_version":"0.4","2":"0.4","version_comment":"Added support for auto-generating numbered sections in toc window.\r\nFixed unprecisely jumping from toc's bug.","3":"Added support for auto-generating numbered sections in toc window.\r\nFixed unprecisely jumping from toc's bug.","package":"ywtxt_0.4.tar.bz2","4":"ywtxt_0.4.tar.bz2","src_id":"12512","5":"12512","creation_date":"1267267022","6":"1267267022"},{"0":"2993","vim_version":"7.0","1":"7.0","script_version":"0.3","2":"0.3","version_comment":"1) Fixed syntax for headers matching bug.\r\n2) Added feature of changing the level of headers with \\< and \\> in toc window (Warn!: file will get saved!).\r\n3) Added keymap <enter>, x for toc window, see the document for detail.\r\n4) Added syntax for [keywords,keywords], figures(Fig. #.<space>) and tables(Table #).","3":"1) Fixed syntax for headers matching bug.\r\n2) Added feature of changing the level of headers with \\< and \\> in toc window (Warn!: file will get saved!).\r\n3) Added keymap <enter>, x for toc window, see the document for detail.\r\n4) Added syntax for [keywords,keywords], figures(Fig. #.<space>) and tables(Table #).","package":"ywtxt_0.3.tar.bz2","4":"ywtxt_0.3.tar.bz2","src_id":"12508","5":"12508","creation_date":"1267236690","6":"1267236690"},{"0":"2993","vim_version":"7.0","1":"7.0","script_version":"0.2","2":"0.2","version_comment":"1) Added highlight for headers(up to 10 levels).\r\n2) Fixed toc generation and cursor location bugs.\r\n3) Remove normal window key maps for toc window.\r\n4) Changed toc window name to the _<file name root>_TOC_\r\n5) Added Function for refreshing the toc window(bind it to r in toc window).\r\n6) Added key map for normal window: \\q      Close the toc window.","3":"1) Added highlight for headers(up to 10 levels).\r\n2) Fixed toc generation and cursor location bugs.\r\n3) Remove normal window key maps for toc window.\r\n4) Changed toc window name to the _<file name root>_TOC_\r\n5) Added Function for refreshing the toc window(bind it to r in toc window).\r\n6) Added key map for normal window: \\q      Close the toc window.","package":"ywtxt_0.2.tar.bz2","4":"ywtxt_0.2.tar.bz2","src_id":"12505","5":"12505","creation_date":"1267227455","6":"1267227455"},{"0":"2993","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"ywtxt_0.1.tar.bz2","4":"ywtxt_0.1.tar.bz2","src_id":"12502","5":"12502","creation_date":"1267195338","6":"1267195338"}]},"2992":{"script_id":"2992","0":"2992","script_name":"SaveSigns","1":"SaveSigns","script_type":"utility","2":"utility","summary":"Save and Restore your Signs","3":"Save and Restore your Signs","description":"This plugin was written to allow you to save your |signs| easily. Signs can be\r\nused to specific highlight certains rows in a buffer. This might be useful\r\nwhen using a debugger or display a |mark|. Note however, that this works only\r\nwhen the signs feature has been compiled into your vim.\r\n\r\nIf you have defined signs in your file, you might want to save these signs to\r\nbe able to reload these signs later on (e.g. with a |Session|). Therefore this\r\nplugin defines the |:SaveSigns| command, which will store all defined signs in\r\na file in such a way that reloading that file will restore all defined signs.\r\n\r\nWhen saving Signs, the plugin creates a Vim Script, that can be read in using\r\n|:source| It will save Sign Definitions (see |:sign-define|), Sign placements\r\n(see |:sign-place|) and the Sign hilighting (see |hl-SignColumn|).\r\n\r\nSince signs are usually associated with a buffer or a file, sourcing this file\r\nusing |:source| will only restore those signs whose buffers are loaded in that\r\nvim session. Note: All Signs that were defined before reloading this file will\r\nbe lost.\r\n\r\n2.1 :SaveSigns\t\t\t\t\t\t\t*:SaveSigns*\r\n\r\n:SaveSigns\t\tStore all currently defined signs in a temporary file.\r\n\t\t\tThis file will be opened in a new split window and you\r\n\t\t\tcan edit it further. Note: This file won't be saved.\r\n\t\t\tYou need to explicitly save it.\r\n\r\n:SaveSigns[!] {name}\tStore all currently defined signs in a file called\r\n\t\t\t{name}. If this file exists, it won't be used a new\r\n\t\t\ttemporary file will be created. Use ! to force storing\r\n\t\t\tthe info in that file. This will however erase the\r\n\t\t\tfile {name}. So use with caution.\r\n\r\nKeywords: Signs, Save, Restore","4":"This plugin was written to allow you to save your |signs| easily. Signs can be\r\nused to specific highlight certains rows in a buffer. This might be useful\r\nwhen using a debugger or display a |mark|. Note however, that this works only\r\nwhen the signs feature has been compiled into your vim.\r\n\r\nIf you have defined signs in your file, you might want to save these signs to\r\nbe able to reload these signs later on (e.g. with a |Session|). Therefore this\r\nplugin defines the |:SaveSigns| command, which will store all defined signs in\r\na file in such a way that reloading that file will restore all defined signs.\r\n\r\nWhen saving Signs, the plugin creates a Vim Script, that can be read in using\r\n|:source| It will save Sign Definitions (see |:sign-define|), Sign placements\r\n(see |:sign-place|) and the Sign hilighting (see |hl-SignColumn|).\r\n\r\nSince signs are usually associated with a buffer or a file, sourcing this file\r\nusing |:source| will only restore those signs whose buffers are loaded in that\r\nvim session. Note: All Signs that were defined before reloading this file will\r\nbe lost.\r\n\r\n2.1 :SaveSigns\t\t\t\t\t\t\t*:SaveSigns*\r\n\r\n:SaveSigns\t\tStore all currently defined signs in a temporary file.\r\n\t\t\tThis file will be opened in a new split window and you\r\n\t\t\tcan edit it further. Note: This file won't be saved.\r\n\t\t\tYou need to explicitly save it.\r\n\r\n:SaveSigns[!] {name}\tStore all currently defined signs in a file called\r\n\t\t\t{name}. If this file exists, it won't be used a new\r\n\t\t\ttemporary file will be created. Use ! to force storing\r\n\t\t\tthe info in that file. This will however erase the\r\n\t\t\tfile {name}. So use with caution.\r\n\r\nKeywords: Signs, Save, Restore","install_details":"Load file in your vim and simply source it from within vim.\r\n:so %\r\n\r\nThis should install the plugin. For the documentation take a look at :h savesigns.txt\r\n\r\nSee :h vimball-intro for details on installing vimball plugins.","5":"Load file in your vim and simply source it from within vim.\r\n:so %\r\n\r\nThis should install the plugin. For the documentation take a look at :h savesigns.txt\r\n\r\nSee :h vimball-intro for details on installing vimball plugins.","first_name":"Christian","6":"Christian","last_name":"Brabandt","7":"Brabandt","releases":[{"0":"2992","vim_version":"7.3","1":"7.3","script_version":"4","2":"4","version_comment":"- use the blackhole register for deleting the buffer content\n- install target did not work\n- Deleted spell modeline\n(automatically uploaded)","3":"- use the blackhole register for deleting the buffer content\n- install target did not work\n- Deleted spell modeline\n(automatically uploaded)","package":"savesigns-0.4.vmb","4":"savesigns-0.4.vmb","src_id":"19525","5":"19525","creation_date":"1361052886","6":"1361052886"},{"0":"2992","vim_version":"6.0","1":"6.0","script_version":"0.3","2":"0.3","version_comment":"Enabled GLVS (see :h GLVS)","3":"Enabled GLVS (see :h GLVS)","package":"SaveSigns.vba","4":"SaveSigns.vba","src_id":"12497","5":"12497","creation_date":"1267127734","6":"1267127734"},{"0":"2992","vim_version":"6.0","1":"6.0","script_version":"0.2","2":"0.2","version_comment":"Initial upload","3":"Initial upload","package":"SaveSigns.vba","4":"SaveSigns.vba","src_id":"12496","5":"12496","creation_date":"1267127493","6":"1267127493"}]},"2991":{"script_id":"2991","0":"2991","script_name":"rcom","1":"rcom","script_type":"ftplugin","2":"ftplugin","summary":"Evaluate R (www.r-project.org) code via rcom, rserve, screen, or tmux","3":"Evaluate R (www.r-project.org) code via rcom, rserve, screen, or tmux","description":"The rcom ftplugin uses one of the following methods to evaluate R code:\r\n\r\n    screen ... default method; works under Linux & Windows (with cygwin\/mintty & Windows Rterm)\r\n    screen or tmux ... via the screen vim plugin; works under Linux & Windows\r\n    RServe ... requires +ruby and the rserve-client rubygem; works under Linux & (less reliably) under Windows\r\n    RCom interface ... requires http:\/\/rcom.univie.ac.at; works under Windows\r\n\r\nWith the exception of RCOM, most methods should work also under Mac OS \r\nbut that was not tested.\r\n\r\nAfter installation, interaction with R is enabled for all\r\nbuffers with filetype r. For other filetypes, you can use the\r\nfunctions |rcom#EvaluateInBuffer()|.\r\n\r\n\r\nFeatures:\r\n\r\n    - Evaluate R code\r\n    - Operator map\r\n    - Maps for normal, visual, and insert mode\r\n    - Keyword map (|K|)\r\n    - Inspect & edit\/fix object (<LocalLeader>K)\r\n    - Debug functions\r\n\r\nThe following features are supported only with some methods:\r\n\r\n    - Omnicompletion for R\r\n    - Get return values from R\r\n\r\n\r\nMaps~\r\n\r\nThe ftplugin provides several maps (see also |g:rcom_map|, \r\n|g:rcom_mapp|) to evaluate R code and optionally print the result in \r\nnormal, insert, and visual mode. There is also an operator (see \r\n|g:rcom_mapop|).\r\n\r\nDefault Maps:\r\n    <c-cr>    ... Evaluate the current line\r\n    <c-s-cr>  ... Evaluate the current line & print result\r\n    +.        ... Evaluate the current line (normal mode)\r\n    +{motion} ... Operator\r\n    [visual]+ ... Evaluate the visual area\r\n    +p        ... Toggle printing for the above maps\r\n    +d        ... Toggle a function's debug status\r\n    +l        ... Open the log window\r\n    ++        ... Evaluate the |maparg| previously mapped to +\r\n    K         ... Info on the word under cursor\r\n    <LocalLeader>K ... Inspect\/edit\/fix the object under cursor\r\n\r\n\r\nNormal usage~\r\n\r\n    0.  Optional steps:\r\n            a. Prepare a running instance of RGui if using the RCOM \r\n               method.\r\n            b. RCOM and screen methods: The results get printed in the R \r\n               window. You might want to arrange the windows in a way, \r\n               so that you can see VIM, R console and R graphic device \r\n               at the same time.\r\n    1.  Open an R source file in VIM.\r\n    2a. Type <c-cr> to evaluate the current line\/visual area in R.\r\n    2b. Type [count]+ or +{motion} to evaluate some text in R. (You can \r\n        type ++ to invoke |+|.)\r\n","4":"The rcom ftplugin uses one of the following methods to evaluate R code:\r\n\r\n    screen ... default method; works under Linux & Windows (with cygwin\/mintty & Windows Rterm)\r\n    screen or tmux ... via the screen vim plugin; works under Linux & Windows\r\n    RServe ... requires +ruby and the rserve-client rubygem; works under Linux & (less reliably) under Windows\r\n    RCom interface ... requires http:\/\/rcom.univie.ac.at; works under Windows\r\n\r\nWith the exception of RCOM, most methods should work also under Mac OS \r\nbut that was not tested.\r\n\r\nAfter installation, interaction with R is enabled for all\r\nbuffers with filetype r. For other filetypes, you can use the\r\nfunctions |rcom#EvaluateInBuffer()|.\r\n\r\n\r\nFeatures:\r\n\r\n    - Evaluate R code\r\n    - Operator map\r\n    - Maps for normal, visual, and insert mode\r\n    - Keyword map (|K|)\r\n    - Inspect & edit\/fix object (<LocalLeader>K)\r\n    - Debug functions\r\n\r\nThe following features are supported only with some methods:\r\n\r\n    - Omnicompletion for R\r\n    - Get return values from R\r\n\r\n\r\nMaps~\r\n\r\nThe ftplugin provides several maps (see also |g:rcom_map|, \r\n|g:rcom_mapp|) to evaluate R code and optionally print the result in \r\nnormal, insert, and visual mode. There is also an operator (see \r\n|g:rcom_mapop|).\r\n\r\nDefault Maps:\r\n    <c-cr>    ... Evaluate the current line\r\n    <c-s-cr>  ... Evaluate the current line & print result\r\n    +.        ... Evaluate the current line (normal mode)\r\n    +{motion} ... Operator\r\n    [visual]+ ... Evaluate the visual area\r\n    +p        ... Toggle printing for the above maps\r\n    +d        ... Toggle a function's debug status\r\n    +l        ... Open the log window\r\n    ++        ... Evaluate the |maparg| previously mapped to +\r\n    K         ... Info on the word under cursor\r\n    <LocalLeader>K ... Inspect\/edit\/fix the object under cursor\r\n\r\n\r\nNormal usage~\r\n\r\n    0.  Optional steps:\r\n            a. Prepare a running instance of RGui if using the RCOM \r\n               method.\r\n            b. RCOM and screen methods: The results get printed in the R \r\n               window. You might want to arrange the windows in a way, \r\n               so that you can see VIM, R console and R graphic device \r\n               at the same time.\r\n    1.  Open an R source file in VIM.\r\n    2a. Type <c-cr> to evaluate the current line\/visual area in R.\r\n    2b. Type [count]+ or +{motion} to evaluate some text in R. (You can \r\n        type ++ to invoke |+|.)\r\n","install_details":"Requirements:\r\n\r\n    - R\r\n\r\nRCOM method:\r\n\r\n    - Windows only (because of rcom)\r\n    - A ruby-enabled version of vim -- :echo has('ruby') must print 1\r\n    - A suitable version of rcom (http:\/\/rcom.univie.ac.at). The rcom \r\n      library has to be loaded in vim, which should be the default \r\n      behaviour after installing rcom. The following code snippet must \r\n      not throw an error: >\r\n\r\n      :ruby require 'win32ole'; r = WIN32OLE.new(\"StatConnectorSrv.StatConnector\"); r.Init(\"R\"); r.Close\r\n\r\nRServe method:\r\n\r\n    - A ruby-enabled version of vim -- :echo has('ruby') must print 1\r\n    - R rserve library installed\r\n    - rserve-client rubygem installed\r\n\r\nScreen method:\r\n\r\n    - screen\r\n    - For tmux: Eric Van Dewoestine's screen vim plugin installed (see \r\n      http:\/\/www.vim.org\/scripts\/script.php?script_id=2711)\r\n","5":"Requirements:\r\n\r\n    - R\r\n\r\nRCOM method:\r\n\r\n    - Windows only (because of rcom)\r\n    - A ruby-enabled version of vim -- :echo has('ruby') must print 1\r\n    - A suitable version of rcom (http:\/\/rcom.univie.ac.at). The rcom \r\n      library has to be loaded in vim, which should be the default \r\n      behaviour after installing rcom. The following code snippet must \r\n      not throw an error: >\r\n\r\n      :ruby require 'win32ole'; r = WIN32OLE.new(\"StatConnectorSrv.StatConnector\"); r.Init(\"R\"); r.Close\r\n\r\nRServe method:\r\n\r\n    - A ruby-enabled version of vim -- :echo has('ruby') must print 1\r\n    - R rserve library installed\r\n    - rserve-client rubygem installed\r\n\r\nScreen method:\r\n\r\n    - screen\r\n    - For tmux: Eric Van Dewoestine's screen vim plugin installed (see \r\n      http:\/\/www.vim.org\/scripts\/script.php?script_id=2711)\r\n","first_name":"Tom","6":"Tom","last_name":"Link","7":"Link","releases":[{"0":"2991","vim_version":"7.0","1":"7.0","script_version":"0.03","2":"0.03","version_comment":"- .gitignore\n- g:rcom_r_plugin_compatibility: Use maps somewhat similar to the r-plugin (untested)\n- Support alternative methods to connect to R: rserve and screen\/tmux\n- RDebug\/RUndebug commands\n- screen: rcom's own simplified method to use screen (now the default method)\n- Method = screen: Support for gvim @ linux & gnome-terminal\n- g:rcom#reuse = g:rcom#method == 'rcom'\n- g:rcom#r_object_browser = 'str'\n- Use rcom_vim.R\n- g:rcom#screen#rterm = executable('Rterm') ? 'Rterm --ess' : 'R'\n- s:reuse = g:rcom#reuse || !has(\"gui_running\")\n- g:rcom#screen#rcom_session replaces g:rcom#screen#rcom_args\n- g:rcom#screen#rcom_sep = 0\n- Make rcom\/screen work also on the terminal\n- s:Scratch() takes buffer \"type\" as an argument\n- rcom#EvaluateInBuffer(): Show the transcript if the transcript buffer is visible or when running vim as server\n- Highlight debugged functions\n- rcom#Debug(fn): Toggle the debug status\n- g:rcom#options = 'warn = 1'\n- Connect & Disconnect return 1 when they created \/ closed an instance of R\n- rcom.options\n- screen\/rcom: Better timing; make sure not to miss commands\n- screen\/rcom: set s:tempfile only once\n- rcom_vim.R\n- rcom_vim.R: Fixed checks for \"reuse\"\n- g:rcom#screen#rcom_shell is a format string\n- Improved timing (use msgwait=0 and sleep for g:rcom#screen#rcom_shell seconds in order not to miss a subsequent eval)\n- rcom#Quit(): Remove buffer-local autocommand\n- rcom\/screen: set msgwait & msgminwait to 0 (reset on disconnect)\n- rcom\/screen: When waiting for a response, also check the file size &, if mode == 'r', the file content\n- g:rcom#options: if has('gui_running') set help_type = \"html\"\n- rcom.complete()\n- rcom#Keyword(): Pass name and name as string as argument\n- rcom#Info(): Call rcom#EvaluateInBuffer() with mode = ''\n- Fix missed disconnect when using multiple R buffers\n- Filename conversion (e.g. via cygpath)\n- screen\/rcom: Always use -S for gvim\n- rcom\/screen: Run -wipe with session info\nMD5 checksum: f45fe4fdf1e8876ec0549e7572026227","3":"- .gitignore\n- g:rcom_r_plugin_compatibility: Use maps somewhat similar to the r-plugin (untested)\n- Support alternative methods to connect to R: rserve and screen\/tmux\n- RDebug\/RUndebug commands\n- screen: rcom's own simplified method to use screen (now the default method)\n- Method = screen: Support for gvim @ linux & gnome-terminal\n- g:rcom#reuse = g:rcom#method == 'rcom'\n- g:rcom#r_object_browser = 'str'\n- Use rcom_vim.R\n- g:rcom#screen#rterm = executable('Rterm') ? 'Rterm --ess' : 'R'\n- s:reuse = g:rcom#reuse || !has(\"gui_running\")\n- g:rcom#screen#rcom_session replaces g:rcom#screen#rcom_args\n- g:rcom#screen#rcom_sep = 0\n- Make rcom\/screen work also on the terminal\n- s:Scratch() takes buffer \"type\" as an argument\n- rcom#EvaluateInBuffer(): Show the transcript if the transcript buffer is visible or when running vim as server\n- Highlight debugged functions\n- rcom#Debug(fn): Toggle the debug status\n- g:rcom#options = 'warn = 1'\n- Connect & Disconnect return 1 when they created \/ closed an instance of R\n- rcom.options\n- screen\/rcom: Better timing; make sure not to miss commands\n- screen\/rcom: set s:tempfile only once\n- rcom_vim.R\n- rcom_vim.R: Fixed checks for \"reuse\"\n- g:rcom#screen#rcom_shell is a format string\n- Improved timing (use msgwait=0 and sleep for g:rcom#screen#rcom_shell seconds in order not to miss a subsequent eval)\n- rcom#Quit(): Remove buffer-local autocommand\n- rcom\/screen: set msgwait & msgminwait to 0 (reset on disconnect)\n- rcom\/screen: When waiting for a response, also check the file size &, if mode == 'r', the file content\n- g:rcom#options: if has('gui_running') set help_type = \"html\"\n- rcom.complete()\n- rcom#Keyword(): Pass name and name as string as argument\n- rcom#Info(): Call rcom#EvaluateInBuffer() with mode = ''\n- Fix missed disconnect when using multiple R buffers\n- Filename conversion (e.g. via cygpath)\n- screen\/rcom: Always use -S for gvim\n- rcom\/screen: Run -wipe with session info\nMD5 checksum: f45fe4fdf1e8876ec0549e7572026227","package":"rcom.vba","4":"rcom.vba","src_id":"18291","5":"18291","creation_date":"1342788528","6":"1342788528"},{"0":"2991","vim_version":"7.0","1":"7.0","script_version":"0.2","2":"0.2","version_comment":"- Add cursor markers only if w:tskeleton_hypercomplete exists\r\n- g:rcom#reuse: If 0, don't use a running instance of R GUI (transcribe the results in VIM; be aware that some problems could cause problems)\r\n- If there is a vim server named RCOM running, evaluate R code remotely (this won't block the current instance of gvim)\r\n- Use g:rcom#server to start an instance of gvim that acts as server\/proxy\r\n- Transcript, log","3":"- Add cursor markers only if w:tskeleton_hypercomplete exists\r\n- g:rcom#reuse: If 0, don't use a running instance of R GUI (transcribe the results in VIM; be aware that some problems could cause problems)\r\n- If there is a vim server named RCOM running, evaluate R code remotely (this won't block the current instance of gvim)\r\n- Use g:rcom#server to start an instance of gvim that acts as server\/proxy\r\n- Transcript, log","package":"rcom.vba.gz","4":"rcom.vba.gz","src_id":"12583","5":"12583","creation_date":"1268162714","6":"1268162714"},{"0":"2991","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"rcom.vba.gz","4":"rcom.vba.gz","src_id":"12495","5":"12495","creation_date":"1267119943","6":"1267119943"}]},"2990":{"script_id":"2990","0":"2990","script_name":"stickykey","1":"stickykey","script_type":"utility","2":"utility","summary":"You don't need press very far away meta keys","3":"You don't need press very far away meta keys","description":"latest version at http:\/\/github.com\/tyru\/stickykey.vim\/\r\n\r\n\r\nThis plugin provides Sticky Key to you.\r\nWith Sticky Key, you can emulate <C-o> by \";o\".\r\n(In this case, <Plug>(stickykey-ctrl) is mapped to \";\")\r\n\r\nAnd I suppose you are using GNU screen :)\r\nInputting screen's hotkey is a little complicated.\r\nBut you can send key input to screen fastly, certainly, and easily.\r\n\r\n\r\n\r\nMAPPINGS\r\n\r\n<Plug>(stickykey-...-remap) works like recursive mapping.\r\n\r\n\r\n<Plug>(stickykey-ctrl)\r\n<Plug>(stickykey-ctrl-remap)\r\n    Sticky key for |ctrl|.\r\n\r\n<Plug>(stickykey-alt)\r\n<Plug>(stickykey-alt-remap)\r\n    Sticky key for |alt|.\r\n\r\n<Plug>(stickykey-shift)\r\n<Plug>(stickykey-shift-remap)\r\n    Sticky key for |shift|.\r\n\r\n<Plug>(stickykey-command)\r\n<Plug>(stickykey-command-remap)\r\n    Sticky key for Macintosh command key. (see |<D-|)\r\n\r\n\r\nVARIABLES\r\n\r\ng:stickykey_when_no_escaped_key\t\t\tstring (default: \"thru\")\r\n    This variables determines when stickykey can not find\r\n    escaped input with meta key.\r\n    For e.g., while waiting the next key after pressing\r\n    \"<Plug>(stickykey-ctrl)\", <C-o> is input.\r\n    This variable can be any one of those:\r\n        \"nop\":\r\n            Behave like no key is input.\r\n        \"thru\":\r\n            Execute key without escaping with meta key.\r\n        \"again\":\r\n            Dispose current key input, wait next input again.","4":"latest version at http:\/\/github.com\/tyru\/stickykey.vim\/\r\n\r\n\r\nThis plugin provides Sticky Key to you.\r\nWith Sticky Key, you can emulate <C-o> by \";o\".\r\n(In this case, <Plug>(stickykey-ctrl) is mapped to \";\")\r\n\r\nAnd I suppose you are using GNU screen :)\r\nInputting screen's hotkey is a little complicated.\r\nBut you can send key input to screen fastly, certainly, and easily.\r\n\r\n\r\n\r\nMAPPINGS\r\n\r\n<Plug>(stickykey-...-remap) works like recursive mapping.\r\n\r\n\r\n<Plug>(stickykey-ctrl)\r\n<Plug>(stickykey-ctrl-remap)\r\n    Sticky key for |ctrl|.\r\n\r\n<Plug>(stickykey-alt)\r\n<Plug>(stickykey-alt-remap)\r\n    Sticky key for |alt|.\r\n\r\n<Plug>(stickykey-shift)\r\n<Plug>(stickykey-shift-remap)\r\n    Sticky key for |shift|.\r\n\r\n<Plug>(stickykey-command)\r\n<Plug>(stickykey-command-remap)\r\n    Sticky key for Macintosh command key. (see |<D-|)\r\n\r\n\r\nVARIABLES\r\n\r\ng:stickykey_when_no_escaped_key\t\t\tstring (default: \"thru\")\r\n    This variables determines when stickykey can not find\r\n    escaped input with meta key.\r\n    For e.g., while waiting the next key after pressing\r\n    \"<Plug>(stickykey-ctrl)\", <C-o> is input.\r\n    This variable can be any one of those:\r\n        \"nop\":\r\n            Behave like no key is input.\r\n        \"thru\":\r\n            Execute key without escaping with meta key.\r\n        \"again\":\r\n            Dispose current key input, wait next input again.","install_details":"just install to your ~\/.vim directory","5":"just install to your ~\/.vim directory","first_name":"tyru","6":"tyru","last_name":" ","7":" ","releases":[{"0":"2990","vim_version":"7.0","1":"7.0","script_version":"0.0.1a","2":"0.0.1a","version_comment":"fix error: j is undefined variable","3":"fix error: j is undefined variable","package":"stickeykey.zip","4":"stickeykey.zip","src_id":"14886","5":"14886","creation_date":"1296187670","6":"1296187670"},{"0":"2990","vim_version":"7.0","1":"7.0","script_version":"0.0.1","2":"0.0.1","version_comment":"- refactoring\r\n- add experimental options to g:stickykey_when_no_escaped_key (\"input\", \"mapping\")","3":"- refactoring\r\n- add experimental options to g:stickykey_when_no_escaped_key (\"input\", \"mapping\")","package":"stickeykey.zip","4":"stickeykey.zip","src_id":"14881","5":"14881","creation_date":"1296136895","6":"1296136895"},{"0":"2990","vim_version":"7.0","1":"7.0","script_version":"0.0.0","2":"0.0.0","version_comment":"Initial upload","3":"Initial upload","package":"stickykey.zip","4":"stickykey.zip","src_id":"12493","5":"12493","creation_date":"1267104079","6":"1267104079"}]},"2989":{"script_id":"2989","0":"2989","script_name":"pummode","1":"pummode","script_type":"utility","2":"utility","summary":"Select completion menu with j and k.","3":"Select completion menu with j and k.","description":"Put this in your .vimrc\r\n\r\n\tcall pummode#map('i', '', 0, 'j', '<C-n>')\r\n\tcall pummode#map('i', '', 0, 'k', '<C-p>')\r\n\tcall pummode#map('i', '', 0, '<CR>', '<C-y>')\r\n\r\nSo now you can select popup menu with j and k, <CR> to insert that item.\r\nSee the document for more detail.\r\n\r\nlatest version at http:\/\/github.com\/tyru\/pummode.vim\/","4":"Put this in your .vimrc\r\n\r\n\tcall pummode#map('i', '', 0, 'j', '<C-n>')\r\n\tcall pummode#map('i', '', 0, 'k', '<C-p>')\r\n\tcall pummode#map('i', '', 0, '<CR>', '<C-y>')\r\n\r\nSo now you can select popup menu with j and k, <CR> to insert that item.\r\nSee the document for more detail.\r\n\r\nlatest version at http:\/\/github.com\/tyru\/pummode.vim\/","install_details":"just install to your ~\/.vim directory","5":"just install to your ~\/.vim directory","first_name":"tyru","6":"tyru","last_name":" ","7":" ","releases":[{"0":"2989","vim_version":"7.2","1":"7.2","script_version":"0.0.0","2":"0.0.0","version_comment":"Initial upload","3":"Initial upload","package":"pummode.zip","4":"pummode.zip","src_id":"12492","5":"12492","creation_date":"1267101631","6":"1267101631"}]},"2988":{"script_id":"2988","0":"2988","script_name":"OpenCL C syntax highlighting","1":"OpenCL C syntax highlighting","script_type":"syntax","2":"syntax","summary":"OpenCL C syntax highlighting","3":"OpenCL C syntax highlighting","description":"OpenCL C syntax highlighting.","4":"OpenCL C syntax highlighting.","install_details":"source it from your ~\/.vim\/syntax\/c.vim \r\nor add line to your .vimrc \r\nautocmd FileType c,cpp source \/path\/to\/opencl.vim","5":"source it from your ~\/.vim\/syntax\/c.vim \r\nor add line to your .vimrc \r\nautocmd FileType c,cpp source \/path\/to\/opencl.vim","first_name":"Mateusz","6":"Mateusz","last_name":"Manowiecki","7":"Manowiecki","releases":[{"0":"2988","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"opencl.vim","4":"opencl.vim","src_id":"12486","5":"12486","creation_date":"1267040997","6":"1267040997"}]},"2987":{"script_id":"2987","0":"2987","script_name":"loadtags","1":"loadtags","script_type":"utility","2":"utility","summary":"Load the correct set of tags for the file you're editing","3":"Load the correct set of tags for the file you're editing","description":"When you open a file, it searches for tags files in all ancestor directories and loads them. This is useful when you work on several projects and have different set of tags for each of them.\r\n\r\nLet's say that you open file \/home\/user\/projects\/my_proj\/lib\/hello.pm. Loadtags plugin looks for files \r\n\r\n\/home\/user\/projects\/my_proj\/lib\/tags, \r\n\/home\/user\/projects\/my_proj\/tags, \r\n\/home\/user\/projects\/tags, \r\n\/home\/user\/tags, \r\n\/home\/tags, \r\n\/tags \r\n\r\nand calls setlocal tags+= on those that exist.","4":"When you open a file, it searches for tags files in all ancestor directories and loads them. This is useful when you work on several projects and have different set of tags for each of them.\r\n\r\nLet's say that you open file \/home\/user\/projects\/my_proj\/lib\/hello.pm. Loadtags plugin looks for files \r\n\r\n\/home\/user\/projects\/my_proj\/lib\/tags, \r\n\/home\/user\/projects\/my_proj\/tags, \r\n\/home\/user\/projects\/tags, \r\n\/home\/user\/tags, \r\n\/home\/tags, \r\n\/tags \r\n\r\nand calls setlocal tags+= on those that exist.","install_details":"Store the loadtags.vim into your ~\/.vim\/plugin directory.\r\nCreate tags file for every your project and store it in the project's root directory (see :help tags).\r\n\r\nI don't know if it works on Windows.","5":"Store the loadtags.vim into your ~\/.vim\/plugin directory.\r\nCreate tags file for every your project and store it in the project's root directory (see :help tags).\r\n\r\nI don't know if it works on Windows.","first_name":"Miroslav","6":"Miroslav","last_name":"Tynovsky","7":"Tynovsky","releases":[{"0":"2987","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"loadtags.vim","4":"loadtags.vim","src_id":"12485","5":"12485","creation_date":"1267028059","6":"1267028059"}]},"2986":{"script_id":"2986","0":"2986","script_name":"AddCppClass","1":"AddCppClass","script_type":"utility","2":"utility","summary":"this plugin is to help you add a c++ class conveniently","3":"this plugin is to help you add a c++ class conveniently","description":"This plugin is far from perfect and thus is not recommended any more.\r\nUse snipmate(vimscript#2540) instead.\r\n------------------------------------------------\r\n\r\nthis plugin is to help you add a c++ class conveniently. \r\nafter you install this plugin, type :AddCppClass under normal mode, you will be leaded to a wizard that help you add a c++ class.\r\n\r\n\r\ncontact me if you have any question or suggestion. (email: xuhdev AT gmail DOT com)","4":"This plugin is far from perfect and thus is not recommended any more.\r\nUse snipmate(vimscript#2540) instead.\r\n------------------------------------------------\r\n\r\nthis plugin is to help you add a c++ class conveniently. \r\nafter you install this plugin, type :AddCppClass under normal mode, you will be leaded to a wizard that help you add a c++ class.\r\n\r\n\r\ncontact me if you have any question or suggestion. (email: xuhdev AT gmail DOT com)","install_details":"extract the zip file to your runtime folder(~\/.vim on Linux and $VIM_INSTALLATION_FOLDER\\vimfiles on windows)","5":"extract the zip file to your runtime folder(~\/.vim on Linux and $VIM_INSTALLATION_FOLDER\\vimfiles on windows)","first_name":"Hong","6":"Hong","last_name":"Xu","7":"Xu","releases":[{"0":"2986","vim_version":"7.0","1":"7.0","script_version":"0.1.2","2":"0.1.2","version_comment":"Only a document fix. And this plugin is not recommended for use any more.","3":"Only a document fix. And this plugin is not recommended for use any more.","package":"AddCppClass.zip","4":"AddCppClass.zip","src_id":"15350","5":"15350","creation_date":"1301664763","6":"1301664763"}]},"2985":{"script_id":"2985","0":"2985","script_name":"BUGS language","1":"BUGS language","script_type":"syntax","2":"syntax","summary":"syntax highlighting","3":"syntax highlighting","description":"Yes, it's a quite simple one.","4":"Yes, it's a quite simple one.","install_details":"The same as installing other vim syntax file","5":"The same as installing other vim syntax file","first_name":"Chen","6":"Chen","last_name":"Zhuojun","7":"Zhuojun","releases":[{"0":"2985","vim_version":"6.0","1":"6.0","script_version":"1","2":"1","version_comment":"Initial upload","3":"Initial upload","package":"bugs.vim","4":"bugs.vim","src_id":"12472","5":"12472","creation_date":"1266924860","6":"1266924860"}]},"2984":{"script_id":"2984","0":"2984","script_name":"R syntax highlighting","1":"R syntax highlighting","script_type":"syntax","2":"syntax","summary":"R syntax highlighting","3":"R syntax highlighting","description":"The highlighting principle is sensitivity over specificity.\r\nThe differences between this file and the prior highlighting syntax file are:\r\n\r\nAdd syntax file folding;\r\nAdd an option to highlight the keywords based on the base package only or based on various contributed packages also;\r\nAdd some rFunction per some distributions;\r\nRevise rType based on latest R (Ver 2.10.1) manual;\r\nAdd rPreProc;\r\nCorrect rArrow with rOperator according to R manual.\r\n\r\nMaintainer contacted but no response. So I upload a new one here.","4":"The highlighting principle is sensitivity over specificity.\r\nThe differences between this file and the prior highlighting syntax file are:\r\n\r\nAdd syntax file folding;\r\nAdd an option to highlight the keywords based on the base package only or based on various contributed packages also;\r\nAdd some rFunction per some distributions;\r\nRevise rType based on latest R (Ver 2.10.1) manual;\r\nAdd rPreProc;\r\nCorrect rArrow with rOperator according to R manual.\r\n\r\nMaintainer contacted but no response. So I upload a new one here.","install_details":"","5":"","first_name":"Chen","6":"Chen","last_name":"Zhuojun","7":"Zhuojun","releases":[{"0":"2984","vim_version":"6.0","1":"6.0","script_version":"1.002","2":"1.002","version_comment":" ","3":" ","package":"r.vim","4":"r.vim","src_id":"12808","5":"12808","creation_date":"1270951744","6":"1270951744"},{"0":"2984","vim_version":"6.0","1":"6.0","script_version":"1.001","2":"1.001","version_comment":"misc","3":"misc","package":"r.vim","4":"r.vim","src_id":"12719","5":"12719","creation_date":"1269741432","6":"1269741432"},{"0":"2984","vim_version":"6.0","1":"6.0","script_version":"1","2":"1","version_comment":"Initial upload","3":"Initial upload","package":"r.vim","4":"r.vim","src_id":"12470","5":"12470","creation_date":"1266923258","6":"1266923258"}]},"2983":{"script_id":"2983","0":"2983","script_name":"qmake--syntax.vim","1":"qmake--syntax.vim","script_type":"syntax","2":"syntax","summary":"syntax for qmake tool from QT","3":"syntax for qmake tool from QT","description":"Simple syntax file for project files (*.pro, *.pri) used with qmake tool from QT Toolkit\r\n","4":"Simple syntax file for project files (*.pro, *.pri) used with qmake tool from QT Toolkit\r\n","install_details":"Create a directory $HOME\/.vim\/syntax\r\nCopy qmake.vim into that directory","5":"Create a directory $HOME\/.vim\/syntax\r\nCopy qmake.vim into that directory","first_name":"Makoto","6":"Makoto","last_name":"Nokata","7":"Nokata","releases":[{"0":"2983","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"qmake.vim","4":"qmake.vim","src_id":"12449","5":"12449","creation_date":"1266679897","6":"1266679897"}]},"2982":{"script_id":"2982","0":"2982","script_name":"jumphl.vim","1":"jumphl.vim","script_type":"utility","2":"utility","summary":"Highlight cursor line after cursor jump","3":"Highlight cursor line after cursor jump","description":"The script highlights the cursor line after a jump. This makes it easy to\r\nspot the new cursor position. The highlight will be removed automatically\r\nwhen you move the cursor within the current line, or down or up by one line.\r\n\r\nThis is a modification of\r\nhttp:\/\/vim.wikia.com\/wiki\/Highlight_cursor_line_after_cursor_jump\r\n\r\n\r\nCOMMANDS\r\n\r\n:DoJumpHl\r\n:NoJumpHl\r\nenable or disable the script.  The script is disabled per default.\r\n\r\n\r\nVARIABLES\r\n\r\n:let g:jumphl_ignore_bufpat = '_NERD_tree_\\C'\r\nDo nothing for buffers where the bufname matches this pattern.\r\n","4":"The script highlights the cursor line after a jump. This makes it easy to\r\nspot the new cursor position. The highlight will be removed automatically\r\nwhen you move the cursor within the current line, or down or up by one line.\r\n\r\nThis is a modification of\r\nhttp:\/\/vim.wikia.com\/wiki\/Highlight_cursor_line_after_cursor_jump\r\n\r\n\r\nCOMMANDS\r\n\r\n:DoJumpHl\r\n:NoJumpHl\r\nenable or disable the script.  The script is disabled per default.\r\n\r\n\r\nVARIABLES\r\n\r\n:let g:jumphl_ignore_bufpat = '_NERD_tree_\\C'\r\nDo nothing for buffers where the bufname matches this pattern.\r\n","install_details":"Drop this file in your plugin folder or :source it when needed.","5":"Drop this file in your plugin folder or :source it when needed.","first_name":"Andy","6":"Andy","last_name":"Wokula","7":"Wokula","releases":[{"0":"2982","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"jumphl.vim","4":"jumphl.vim","src_id":"12428","5":"12428","creation_date":"1266589723","6":"1266589723"}]},"2981":{"script_id":"2981","0":"2981","script_name":"Emmet.vim","1":"Emmet.vim","script_type":"utility","2":"utility","summary":"vim plugins for HTML and CSS hi-speed coding.","3":"vim plugins for HTML and CSS hi-speed coding.","description":"\nThis is vim script support expanding abbreviation like emmet.\nref: http:\/\/emmet.io\/\n\nThere is a movie using emmet.vim\nref: http:\/\/mattn.github.com\/emmet-vim\n\nSource Repository.\nref: http:\/\/github.com\/mattn\/emmet-vim\n\nType abbreviation\n   +-------------------------------------\n   | html:5_\n   +-------------------------------------\n\"_\" is a cursor position. and type \"<c-y>,\" (Ctrl + y and Comma)\nNOTE: Don't worry about key map. you can change it easily.\n   +-------------------------------------\n   | <!DOCTYPE HTML>\n   | <html lang=\"en\">\n   | <head>\n   |     <title><\/title>\n   |     <meta charset=\"UTF-8\">\n   | <\/head>\n   | <body>\n   |      _\n   | <\/body>\n   | <\/html>\n   +-------------------------------------\nType following\n   +-------------------------------------\n   | div#foo$*2>div.bar\n   +-------------------------------------\nAnd type \"<c-y>,\"\n   +-------------------------------------\n   |<div id=\"foo1\">\n   |    <div class=\"bar\">_<\/div>\n   |<\/div>\n   |<div id=\"foo2\">\n   |    <div class=\"bar\"><\/div>\n   |<\/div>\n   | _\n   +-------------------------------------\n\nTutorial:\n\n  http:\/\/github.com\/mattn\/emmet-vim\/raw\/master\/TUTORIAL\n\nHow work this:\n\n  http:\/\/mattn.github.com\/emmet-vim\n\nTips:\n\nYou can customize behavior of expanding with overriding config.\nThis configuration will be merged at loading plugin.\n\n  let g:user_emmet_settings = {\n  \\  'indentation' : '  ',\n  \\  'perl' : {\n  \\    'aliases' : {\n  \\      'req' : 'require '\n  \\    },\n  \\    'snippets' : {\n  \\      'use' : \"use strict\\nuse warnings\\n\\n\",\n  \\      'warn' : \"warn \\\"|\\\";\",\n  \\    }\n  \\  }\n  \\}\n\n  let g:user_emmet_expandabbr_key = '<c-e>'\n\n  let g:use_emmet_complete_tag = 1\n\nYou can set language attribute in html using emmet_settings['lang'].\n","4":"\nThis is vim script support expanding abbreviation like emmet.\nref: http:\/\/emmet.io\/\n\nThere is a movie using emmet.vim\nref: http:\/\/mattn.github.com\/emmet-vim\n\nSource Repository.\nref: http:\/\/github.com\/mattn\/emmet-vim\n\nType abbreviation\n   +-------------------------------------\n   | html:5_\n   +-------------------------------------\n\"_\" is a cursor position. and type \"<c-y>,\" (Ctrl + y and Comma)\nNOTE: Don't worry about key map. you can change it easily.\n   +-------------------------------------\n   | <!DOCTYPE HTML>\n   | <html lang=\"en\">\n   | <head>\n   |     <title><\/title>\n   |     <meta charset=\"UTF-8\">\n   | <\/head>\n   | <body>\n   |      _\n   | <\/body>\n   | <\/html>\n   +-------------------------------------\nType following\n   +-------------------------------------\n   | div#foo$*2>div.bar\n   +-------------------------------------\nAnd type \"<c-y>,\"\n   +-------------------------------------\n   |<div id=\"foo1\">\n   |    <div class=\"bar\">_<\/div>\n   |<\/div>\n   |<div id=\"foo2\">\n   |    <div class=\"bar\"><\/div>\n   |<\/div>\n   | _\n   +-------------------------------------\n\nTutorial:\n\n  http:\/\/github.com\/mattn\/emmet-vim\/raw\/master\/TUTORIAL\n\nHow work this:\n\n  http:\/\/mattn.github.com\/emmet-vim\n\nTips:\n\nYou can customize behavior of expanding with overriding config.\nThis configuration will be merged at loading plugin.\n\n  let g:user_emmet_settings = {\n  \\  'indentation' : '  ',\n  \\  'perl' : {\n  \\    'aliases' : {\n  \\      'req' : 'require '\n  \\    },\n  \\    'snippets' : {\n  \\      'use' : \"use strict\\nuse warnings\\n\\n\",\n  \\      'warn' : \"warn \\\"|\\\";\",\n  \\    }\n  \\  }\n  \\}\n\n  let g:user_emmet_expandabbr_key = '<c-e>'\n\n  let g:use_emmet_complete_tag = 1\n\nYou can set language attribute in html using emmet_settings['lang'].\n","install_details":"\n# cd ~\/.vim\n# unzip emmet-vim.zip\n\nor if you install pathogen.vim:\n\n# cd ~\/.vim\/bundle # or make directory\n# unzip \/path\/to\/emmet-vim.zip\n\nif you get sources from repository:\n\n# cd ~\/.vim\/bundle # or make directory\n# git clone http:\/\/github.com\/mattn\/emmet-vim.git\n","5":"\n# cd ~\/.vim\n# unzip emmet-vim.zip\n\nor if you install pathogen.vim:\n\n# cd ~\/.vim\/bundle # or make directory\n# unzip \/path\/to\/emmet-vim.zip\n\nif you get sources from repository:\n\n# cd ~\/.vim\/bundle # or make directory\n# git clone http:\/\/github.com\/mattn\/emmet-vim.git\n","first_name":"Yasuhiro","6":"Yasuhiro","last_name":"Matsumoto","7":"Matsumoto","releases":[{"0":"2981","vim_version":"7.0","1":"7.0","script_version":"0.86","2":"0.86","version_comment":"This is an upgrade for Emmet.vim: lot of bug fixes.\n","3":"This is an upgrade for Emmet.vim: lot of bug fixes.\n","package":"emmet-vim.zip","4":"emmet-vim.zip","src_id":"23483","5":"23483","creation_date":"1437914786","6":"1437914786"},{"0":"2981","vim_version":"7.0","1":"7.0","script_version":"0.85","2":"0.85","version_comment":"This is an upgrade for Emmet.vim: lot of bug fixes.\n","3":"This is an upgrade for Emmet.vim: lot of bug fixes.\n","package":"emmet-vim.zip","4":"emmet-vim.zip","src_id":"22403","5":"22403","creation_date":"1409703252","6":"1409703252"},{"0":"2981","vim_version":"7.0","1":"7.0","script_version":"0.84","2":"0.84","version_comment":"This is an upgrade for Emmet.vim: lot of bug fixes. fix bug that interpose insert completion plugins.\n","3":"This is an upgrade for Emmet.vim: lot of bug fixes. fix bug that interpose insert completion plugins.\n","package":"emmet-vim.zip","4":"emmet-vim.zip","src_id":"22402","5":"22402","creation_date":"1409703148","6":"1409703148"},{"0":"2981","vim_version":"7.0","1":"7.0","script_version":"0.83","2":"0.83","version_comment":"This is an upgrade for Emmet.vim: lot of bug fixes.\n","3":"This is an upgrade for Emmet.vim: lot of bug fixes.\n","package":"emmet-vim.zip","4":"emmet-vim.zip","src_id":"21081","5":"21081","creation_date":"1385013905","6":"1385013905"},{"0":"2981","vim_version":"7.0","1":"7.0","script_version":"0.82","2":"0.82","version_comment":"This is an upgrade for Emmet.vim: many bug fixes.\n","3":"This is an upgrade for Emmet.vim: many bug fixes.\n","package":"emmet-vim.zip","4":"emmet-vim.zip","src_id":"20637","5":"20637","creation_date":"1376396989","6":"1376396989"},{"0":"2981","vim_version":"7.0","1":"7.0","script_version":"0.81","2":"0.81","version_comment":"Release of Emmet.vim: renamed from ZenCoding.vim.\n","3":"Release of Emmet.vim: renamed from ZenCoding.vim.\n","package":"emmet-vim.zip","4":"emmet-vim.zip","src_id":"20605","5":"20605","creation_date":"1375797311","6":"1375797311"},{"0":"2981","vim_version":"7.0","1":"7.0","script_version":"0.80","2":"0.80","version_comment":"This is an upgrade for ZenCoding.vim: add emmet features.\n","3":"This is an upgrade for ZenCoding.vim: add emmet features.\n","package":"zencoding-vim.zip","4":"zencoding-vim.zip","src_id":"18992","5":"18992","creation_date":"1353288396","6":"1353288396"},{"0":"2981","vim_version":"7.0","1":"7.0","script_version":"0.74","2":"0.74","version_comment":"This is an upgrade for ZenCoding.vim: many bug fixes.\n","3":"This is an upgrade for ZenCoding.vim: many bug fixes.\n","package":"zencoding-vim.zip","4":"zencoding-vim.zip","src_id":"18236","5":"18236","creation_date":"1341806259","6":"1341806259"},{"0":"2981","vim_version":"7.0","1":"7.0","script_version":"0.73","2":"0.73","version_comment":"This is an upgrade for ZenCoding.vim: many bug fixes. and support slim format (experimental).\n","3":"This is an upgrade for ZenCoding.vim: many bug fixes. and support slim format (experimental).\n","package":"zencoding-vim.zip","4":"zencoding-vim.zip","src_id":"18107","5":"18107","creation_date":"1339262752","6":"1339262752"},{"0":"2981","vim_version":"7.0","1":"7.0","script_version":"0.72","2":"0.72","version_comment":"This is an upgrade for ZenCoding.vim:\n[fix] fix finding tokens.\n","3":"This is an upgrade for ZenCoding.vim:\n[fix] fix finding tokens.\n","package":"zencoding-vim.zip","4":"zencoding-vim.zip","src_id":"18056","5":"18056","creation_date":"1338249092","6":"1338249092"},{"0":"2981","vim_version":"7.0","1":"7.0","script_version":"0.71","2":"0.71","version_comment":"This is an upgrade for ZenCoding.vim:\n[fix] fix finding begin of tokens.\n","3":"This is an upgrade for ZenCoding.vim:\n[fix] fix finding begin of tokens.\n","package":"zencoding-vim.zip","4":"zencoding-vim.zip","src_id":"18052","5":"18052","creation_date":"1338193553","6":"1338193553"},{"0":"2981","vim_version":"7.0","1":"7.0","script_version":"0.70","2":"0.70","version_comment":"This is an upgrade for ZenCoding.vim:\n[mod] Changed behavior of expanding. \"div div>a|\" should keep first div element.\n[add] Supported slim formatter.\n","3":"This is an upgrade for ZenCoding.vim:\n[mod] Changed behavior of expanding. \"div div>a|\" should keep first div element.\n[add] Supported slim formatter.\n","package":"zencoding-vim.zip","4":"zencoding-vim.zip","src_id":"18050","5":"18050","creation_date":"1338168298","6":"1338168298"},{"0":"2981","vim_version":"7.0","1":"7.0","script_version":"0.60","2":"0.60","version_comment":"This is an upgrade for ZenCoding.vim:\n[fix] fixed expanding {{}}.\n","3":"This is an upgrade for ZenCoding.vim:\n[fix] fixed expanding {{}}.\n","package":"zencoding-vim.zip","4":"zencoding-vim.zip","src_id":"17852","5":"17852","creation_date":"1335929568","6":"1335929568"},{"0":"2981","vim_version":"7.0","1":"7.0","script_version":"0.59","2":"0.59","version_comment":"This is an upgrade for ZenCoding.vim:\n[fix] fixed toggleComment and mny bugs.\n","3":"This is an upgrade for ZenCoding.vim:\n[fix] fixed toggleComment and mny bugs.\n","package":"zencoding-vim.zip","4":"zencoding-vim.zip","src_id":"17346","5":"17346","creation_date":"1327985703","6":"1327985703"},{"0":"2981","vim_version":"7.0","1":"7.0","script_version":"0.58","2":"0.58","version_comment":"This is an upgrade for ZenCoding.vim:\n[fix] fixed 'foo+' style expandos.\n","3":"This is an upgrade for ZenCoding.vim:\n[fix] fixed 'foo+' style expandos.\n","package":"zencoding-vim.zip","4":"zencoding-vim.zip","src_id":"16939","5":"16939","creation_date":"1321965570","6":"1321965570"},{"0":"2981","vim_version":"7.0","1":"7.0","script_version":"0.57","2":"0.57","version_comment":"This is an upgrade for ZenCoding.vim:\n[fix] fixed expandos that don't work 'choose' in xsl.\n","3":"This is an upgrade for ZenCoding.vim:\n[fix] fixed expandos that don't work 'choose' in xsl.\n","package":"zencoding-vim.zip","4":"zencoding-vim.zip","src_id":"16935","5":"16935","creation_date":"1321956602","6":"1321956602"},{"0":"2981","vim_version":"7.0","1":"7.0","script_version":"0.56","2":"0.56","version_comment":"This is an upgrade for ZenCoding.vim:\n[fix] fixed contents parser.\n","3":"This is an upgrade for ZenCoding.vim:\n[fix] fixed contents parser.\n","package":"zencoding-vim.zip","4":"zencoding-vim.zip","src_id":"16824","5":"16824","creation_date":"1320718334","6":"1320718334"},{"0":"2981","vim_version":"7.0","1":"7.0","script_version":"0.55","2":"0.55","version_comment":"uploaded again: sorry, files was old.\n","3":"uploaded again: sorry, files was old.\n","package":"zencoding-vim.zip","4":"zencoding-vim.zip","src_id":"16737","5":"16737","creation_date":"1319518295","6":"1319518295"}]},"2980":{"script_id":"2980","0":"2980","script_name":"php-doc upgrade","1":"php-doc upgrade","script_type":"utility","2":"utility","summary":"2005 php-doc plugin w\/ added bonuses","3":"2005 php-doc plugin w\/ added bonuses","description":"added things like\r\n\r\n- {{{ }}} wrapper support in functions\r\n- fixed int\/bool\/string\/float crap to properly work\r\n","4":"added things like\r\n\r\n- {{{ }}} wrapper support in functions\r\n- fixed int\/bool\/string\/float crap to properly work\r\n","install_details":"inoremap <C-P> <ESC>:call PhpDocSingle()<CR>i                                                                                         nnoremap <C-P> :call PhpDocSingle()<CR>\r\nvnoremap <C-P> :call PhpDocRange()<CR>\r\nnnoremap <C-H> :Php <q-args>    ","5":"inoremap <C-P> <ESC>:call PhpDocSingle()<CR>i                                                                                         nnoremap <C-P> :call PhpDocSingle()<CR>\r\nvnoremap <C-P> :call PhpDocRange()<CR>\r\nnnoremap <C-H> :Php <q-args>    ","first_name":"kevin","6":"kevin","last_name":"olson","7":"olson","releases":[{"0":"2980","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"php-doc.vim","4":"php-doc.vim","src_id":"12411","5":"12411","creation_date":"1266544321","6":"1266544321"}]},"2979":{"script_id":"2979","0":"2979","script_name":"Parameter Text Objects","1":"Parameter Text Objects","script_type":"utility","2":"utility","summary":"Defines parameter text objects","3":"Defines parameter text objects","description":"This script defines a parameter text object. A parameter is the text between parentheses or commas, typically found in a function's argument list.\r\n\r\nThis script also adds mappings to help you associate printf-type \"%\"-formatted strings with their corresponding arguments.\r\n\r\nSee:\r\n:help text-objects\r\n  for a description of what can be done with text objects.\r\n\r\nLike all the other text-objects, a parameter text object can be selected following these commands: 'd', 'c', 'y', 'v', etc. The script defines these operator mappings:\r\n\r\n   aP    \"a parameter\", select a parameter, including one comma (if there is one).\r\n\r\n   iP    \"inner parameter\", select a parameter, not including commas.\r\n \r\nThis script also adds commands that are helpful when constructing printf-style \"%\" formatted strings. Press \",a\" (by default) to move the cursor to the corresponding argument. Press \",A\" (by default) to do the opposite.\r\n","4":"This script defines a parameter text object. A parameter is the text between parentheses or commas, typically found in a function's argument list.\r\n\r\nThis script also adds mappings to help you associate printf-type \"%\"-formatted strings with their corresponding arguments.\r\n\r\nSee:\r\n:help text-objects\r\n  for a description of what can be done with text objects.\r\n\r\nLike all the other text-objects, a parameter text object can be selected following these commands: 'd', 'c', 'y', 'v', etc. The script defines these operator mappings:\r\n\r\n   aP    \"a parameter\", select a parameter, including one comma (if there is one).\r\n\r\n   iP    \"inner parameter\", select a parameter, not including commas.\r\n \r\nThis script also adds commands that are helpful when constructing printf-style \"%\" formatted strings. Press \",a\" (by default) to move the cursor to the corresponding argument. Press \",A\" (by default) to do the opposite.\r\n","install_details":"Drop the vim script in your plugin directory.","5":"Drop the vim script in your plugin directory.","first_name":"David","6":"David","last_name":"Larson","7":"Larson","releases":[{"0":"2979","vim_version":"7.0","1":"7.0","script_version":"1.1","2":"1.1","version_comment":"Added mappings for %-formatted strings.","3":"Added mappings for %-formatted strings.","package":"parameter_objects.vim","4":"parameter_objects.vim","src_id":"27077","5":"27077","creation_date":"1584158068","6":"1584158068"},{"0":"2979","vim_version":"7.0","1":"7.0","script_version":"0.2a","2":"0.2a","version_comment":"The script can handle counts now (eg. 2daP). Implementation suggestion by David Kotchan (thanks David!).","3":"The script can handle counts now (eg. 2daP). Implementation suggestion by David Kotchan (thanks David!).","package":"parameter_objects.vim","4":"parameter_objects.vim","src_id":"12640","5":"12640","creation_date":"1268774475","6":"1268774475"},{"0":"2979","vim_version":"7.0","1":"7.0","script_version":"0.1d","2":"0.1d","version_comment":"Added <Plug> mappings so that the user can easily remap the commands. Suggested by Kana Natsuno","3":"Added <Plug> mappings so that the user can easily remap the commands. Suggested by Kana Natsuno","package":"parameter_objects.vim","4":"parameter_objects.vim","src_id":"12439","5":"12439","creation_date":"1266617880","6":"1266617880"},{"0":"2979","vim_version":"7.0","1":"7.0","script_version":"0.1c","2":"0.1c","version_comment":"Ignores strings and comments","3":"Ignores strings and comments","package":"parameter_objects.vim","4":"parameter_objects.vim","src_id":"12406","5":"12406","creation_date":"1266528650","6":"1266528650"}]},"2978":{"script_id":"2978","0":"2978","script_name":"trogdor","1":"trogdor","script_type":"color scheme","2":"color scheme","summary":"A coding theme to help minimize eye strain.","3":"A coding theme to help minimize eye strain.","description":"This is an upload of my C\/C++ theme for gVim that I designed to minimize long hour coding eye strain, and I think it works better than most.  A picture of it can be found here \r\nhttp:\/\/renderguild.com\/vim\/colors\/trogdor.png\r\n\r\n","4":"This is an upload of my C\/C++ theme for gVim that I designed to minimize long hour coding eye strain, and I think it works better than most.  A picture of it can be found here \r\nhttp:\/\/renderguild.com\/vim\/colors\/trogdor.png\r\n\r\n","install_details":"1. Copy trogdor.vim into your \/gvim\/colors\/ folder\r\n2. Inside of gvim execute \":color trogdor\"\r\n\r\n","5":"1. Copy trogdor.vim into your \/gvim\/colors\/ folder\r\n2. Inside of gvim execute \":color trogdor\"\r\n\r\n","first_name":"Bruce","6":"Bruce","last_name":"G","7":"G","releases":[{"0":"2978","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"trogdor.vim","4":"trogdor.vim","src_id":"12397","5":"12397","creation_date":"1266483304","6":"1266483304"}]},"2977":{"script_id":"2977","0":"2977","script_name":"underwater","1":"underwater","script_type":"color scheme","2":"color scheme","summary":"An easy on the eyes dark blue theme","3":"An easy on the eyes dark blue theme","description":"A port of my theme for Komodo, this theme is past-midnight coding friendly:\r\nhttp:\/\/imgur.com\/iEBiU.png\r\n\r\nI do tweak it sometimes, so check back here now and then.","4":"A port of my theme for Komodo, this theme is past-midnight coding friendly:\r\nhttp:\/\/imgur.com\/iEBiU.png\r\n\r\nI do tweak it sometimes, so check back here now and then.","install_details":"1. Copy underwater.vim to ~\/.vim\/colors\/\r\n2. Inside of vim execute \":color underwater\"","5":"1. Copy underwater.vim to ~\/.vim\/colors\/\r\n2. Inside of vim execute \":color underwater\"","first_name":"Dmitry","6":"Dmitry","last_name":"Kichenko","7":"Kichenko","releases":[{"0":"2977","vim_version":"6.0","1":"6.0","script_version":"1.0.4","2":"1.0.4","version_comment":"Muted the special character colour a bit.","3":"Muted the special character colour a bit.","package":"underwater.vim","4":"underwater.vim","src_id":"12480","5":"12480","creation_date":"1266977189","6":"1266977189"},{"0":"2977","vim_version":"6.0","1":"6.0","script_version":"1.0.3.1","2":"1.0.3.1","version_comment":"-Slightly darker cursorline\r\n-Slightly darker cursor\r\nI just can't stop updating this theme!","3":"-Slightly darker cursorline\r\n-Slightly darker cursor\r\nI just can't stop updating this theme!","package":"underwater.vim","4":"underwater.vim","src_id":"12402","5":"12402","creation_date":"1266521915","6":"1266521915"},{"0":"2977","vim_version":"6.0","1":"6.0","script_version":"1.0.3","2":"1.0.3","version_comment":"Special thanks to the reddit community for pointing out the flaws!\r\n-Fixed vertical split\r\n-Fixed cursor line\r\n-Fixed PMenu\r\n-Fixed search highlighting\r\n-Fixed folding","3":"Special thanks to the reddit community for pointing out the flaws!\r\n-Fixed vertical split\r\n-Fixed cursor line\r\n-Fixed PMenu\r\n-Fixed search highlighting\r\n-Fixed folding","package":"underwater.vim","4":"underwater.vim","src_id":"12401","5":"12401","creation_date":"1266511307","6":"1266511307"},{"0":"2977","vim_version":"6.0","1":"6.0","script_version":"1.0.2","2":"1.0.2","version_comment":"Boosted colour saturation slightly on the purples and oranges.","3":"Boosted colour saturation slightly on the purples and oranges.","package":"underwater.vim","4":"underwater.vim","src_id":"12396","5":"12396","creation_date":"1266466454","6":"1266466454"},{"0":"2977","vim_version":"6.0","1":"6.0","script_version":"1.0.1","2":"1.0.1","version_comment":"Tweaked the statement color slightly","3":"Tweaked the statement color slightly","package":" underwater.vim","4":" underwater.vim","src_id":"12395","5":"12395","creation_date":"1266460914","6":"1266460914"},{"0":"2977","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"underwater.vim","4":"underwater.vim","src_id":"12394","5":"12394","creation_date":"1266459209","6":"1266459209"}]},"2976":{"script_id":"2976","0":"2976","script_name":"blowfish.vim","1":"blowfish.vim","script_type":"utility","2":"utility","summary":"blowfish function","3":"blowfish function","description":"This is a port of blowfish function.\r\n\r\nlet encrypted = blowfish#encrypt(\"password\", \"data\", 1)\r\nlet decrypted = blowfish#decrypt(\"password\", encrypted, 1)\r\necho encrypted\r\n=> [113, 35, 42, 246, 6, 245, 188, 236]\r\necho decrypted\r\n=> [100, 97, 116, 97] (\"data\")","4":"This is a port of blowfish function.\r\n\r\nlet encrypted = blowfish#encrypt(\"password\", \"data\", 1)\r\nlet decrypted = blowfish#decrypt(\"password\", encrypted, 1)\r\necho encrypted\r\n=> [113, 35, 42, 246, 6, 245, 188, 236]\r\necho decrypted\r\n=> [100, 97, 116, 97] (\"data\")","install_details":"Put file in your autoload directory.","5":"Put file in your autoload directory.","first_name":"Yukihiro","6":"Yukihiro","last_name":"Nakadaira","7":"Nakadaira","releases":[{"0":"2976","vim_version":"7.2","1":"7.2","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"blowfish.vim","4":"blowfish.vim","src_id":"12390","5":"12390","creation_date":"1266330623","6":"1266330623"}]},"2975":{"script_id":"2975","0":"2975","script_name":"fugitive.vim","1":"fugitive.vim","script_type":"utility","2":"utility","summary":"A Git wrapper so awesome, it should be illegal","3":"A Git wrapper so awesome, it should be illegal","description":"Fugitive is the premier Vim plugin for Git.  Or maybe it's the premier Git plugin for Vim?  Either way, it's \"so awesome, it should be illegal\".  That's why it's called Fugitive.\r\n\r\nThe crown jewel of Fugitive is :Git (or just :G), which calls any arbitrary Git command.  If you know how to use Git at the command line, you know how to use :Git.  It's vaguely akin to :!git but with numerous improvements:\r\n\r\n* The default behavior is to directly echo the command's output.  Quiet commands like :Git add avoid the dreaded \"Press ENTER or type command to continue\" prompt.\r\n* :Git commit, :Git rebase -i, and other commands that invoke an editor do their editing in the current Vim instance.\r\n* :Git diff, :Git log, and other verbose, paginated commands have their output loaded into a temporary buffer.  Force this behavior for any command with :Git --paginate or :Git -p.\r\n* :Git blame uses a temporary buffer with maps for additional triage.  Press enter on a line to view the commit where the line changed, or g? to see other available maps.  Omit the filename argument and the currently edited file will be blamed in a vertical, scroll-bound split.\r\n* :Git mergetool and :Git difftool load their changesets into the quickfix list.\r\n* Called with no arguments, :Git opens a summary window with dirty files and unpushed and unpulled commits.  Press g? to bring up a list of maps for numerous operations including diffing, staging, committing, rebasing, and stashing.  (This is the successor to the old :Gstatus.)\r\n* This command (along with all other commands) always uses the current buffer's repository, so you don't need to worry about the current working directory.\r\n\r\nAdditional commands are provided for higher level operations:\r\n\r\n* View any blob, tree, commit, or tag in the repository with :Gedit (and :Gsplit, etc.).  For example, :Gedit HEAD~3:% loads the current file as it existed 3 commits ago.\r\n* :Gdiffsplit brings up the staged version of the file side by side with the working tree version.  Use Vim's diff handling capabilities to apply changes to the staged version, and write that buffer to stage the changes.  You can also give an arbitrary :Gedit argument to diff against older versions of the file.\r\n* :Gread is a variant of git checkout -- filename that operates on the buffer rather than the file itself.  This means you can use u to undo it and you never get any warnings about the file changing outside Vim.\r\n* :Gwrite writes to both the work tree and index versions of a file, making it like git add when called from a work tree file and like git checkout when called from the index or a blob in history.\r\n* :Ggrep is :grep for git grep.  :Glgrep is :lgrep for the same.\r\n* :GMove does a git mv on the current file and changes the buffer name to match.  :GRename does the same with a destination filename relative to the current file's directory.\r\n* :GDelete does a git rm on the current file and simultaneously deletes the buffer.  :GRemove does the same but leaves the (now empty) buffer open.\r\n* :GBrowse to open the current file on the web front-end of your favorite hosting provider, with optional line range (try it in visual mode).  Plugins are available for popular providers.\r\n\r\nAdd %{FugitiveStatusline()} to 'statusline' to get an indicator with the current branch in your statusline.\r\n\r\nFor more information, see :help fugitive.","4":"Fugitive is the premier Vim plugin for Git.  Or maybe it's the premier Git plugin for Vim?  Either way, it's \"so awesome, it should be illegal\".  That's why it's called Fugitive.\r\n\r\nThe crown jewel of Fugitive is :Git (or just :G), which calls any arbitrary Git command.  If you know how to use Git at the command line, you know how to use :Git.  It's vaguely akin to :!git but with numerous improvements:\r\n\r\n* The default behavior is to directly echo the command's output.  Quiet commands like :Git add avoid the dreaded \"Press ENTER or type command to continue\" prompt.\r\n* :Git commit, :Git rebase -i, and other commands that invoke an editor do their editing in the current Vim instance.\r\n* :Git diff, :Git log, and other verbose, paginated commands have their output loaded into a temporary buffer.  Force this behavior for any command with :Git --paginate or :Git -p.\r\n* :Git blame uses a temporary buffer with maps for additional triage.  Press enter on a line to view the commit where the line changed, or g? to see other available maps.  Omit the filename argument and the currently edited file will be blamed in a vertical, scroll-bound split.\r\n* :Git mergetool and :Git difftool load their changesets into the quickfix list.\r\n* Called with no arguments, :Git opens a summary window with dirty files and unpushed and unpulled commits.  Press g? to bring up a list of maps for numerous operations including diffing, staging, committing, rebasing, and stashing.  (This is the successor to the old :Gstatus.)\r\n* This command (along with all other commands) always uses the current buffer's repository, so you don't need to worry about the current working directory.\r\n\r\nAdditional commands are provided for higher level operations:\r\n\r\n* View any blob, tree, commit, or tag in the repository with :Gedit (and :Gsplit, etc.).  For example, :Gedit HEAD~3:% loads the current file as it existed 3 commits ago.\r\n* :Gdiffsplit brings up the staged version of the file side by side with the working tree version.  Use Vim's diff handling capabilities to apply changes to the staged version, and write that buffer to stage the changes.  You can also give an arbitrary :Gedit argument to diff against older versions of the file.\r\n* :Gread is a variant of git checkout -- filename that operates on the buffer rather than the file itself.  This means you can use u to undo it and you never get any warnings about the file changing outside Vim.\r\n* :Gwrite writes to both the work tree and index versions of a file, making it like git add when called from a work tree file and like git checkout when called from the index or a blob in history.\r\n* :Ggrep is :grep for git grep.  :Glgrep is :lgrep for the same.\r\n* :GMove does a git mv on the current file and changes the buffer name to match.  :GRename does the same with a destination filename relative to the current file's directory.\r\n* :GDelete does a git rm on the current file and simultaneously deletes the buffer.  :GRemove does the same but leaves the (now empty) buffer open.\r\n* :GBrowse to open the current file on the web front-end of your favorite hosting provider, with optional line range (try it in visual mode).  Plugins are available for popular providers.\r\n\r\nAdd %{FugitiveStatusline()} to 'statusline' to get an indicator with the current branch in your statusline.\r\n\r\nFor more information, see :help fugitive.","install_details":"Extract in ~\/.vim (~\\vimfiles on Windows).","5":"Extract in ~\/.vim (~\\vimfiles on Windows).","first_name":"Tim","6":"Tim","last_name":"Pope","7":"Pope","releases":[{"0":"2975","vim_version":"7.3","1":"7.3","script_version":"3.7","2":"3.7","version_comment":"Move \"Unpushed\" sections above \"Unpulled\".\r\nShow commits that are unpushed anywhere when no upstream is set.\r\nProvide czs map as :Git stash push --staged.\r\nSupport the MSYS Vim bundled with Git for Windows.\r\nTurn remaining deprecated commands (:Gbrowse, etc.) into error stubs.","3":"Move \"Unpushed\" sections above \"Unpulled\".\r\nShow commits that are unpushed anywhere when no upstream is set.\r\nProvide czs map as :Git stash push --staged.\r\nSupport the MSYS Vim bundled with Git for Windows.\r\nTurn remaining deprecated commands (:Gbrowse, etc.) into error stubs.","package":"fugitive.zip","4":"fugitive.zip","src_id":"28072","5":"28072","creation_date":"1654610684","6":"1654610684"},{"0":"2975","vim_version":"7.3","1":"7.3","script_version":"3.6","2":"3.6","version_comment":"Fix support for older Vim 7 patch levels.\r\nSupport copies on :Gclog --follow.","3":"Fix support for older Vim 7 patch levels.\r\nSupport copies on :Gclog --follow.","package":"fugitive.zip","4":"fugitive.zip","src_id":"27818","5":"27818","creation_date":"1637902608","6":"1637902608"},{"0":"2975","vim_version":"7.3","1":"7.3","script_version":"3.5","2":"3.5","version_comment":"Lazy initialization.\r\nMake status buffer diff retrieval asynchronous.\r\nSupport jump to diff from :Git log --name-status.\r\nUse smudge filters when viewing blobs.\r\nProvide User FugitiveEditor event.\r\nProvide FugitiveRemote() API function.","3":"Lazy initialization.\r\nMake status buffer diff retrieval asynchronous.\r\nSupport jump to diff from :Git log --name-status.\r\nUse smudge filters when viewing blobs.\r\nProvide User FugitiveEditor event.\r\nProvide FugitiveRemote() API function.","package":"fugitive.zip","4":"fugitive.zip","src_id":"27806","5":"27806","creation_date":"1636986628","6":"1636986628"},{"0":"2975","vim_version":"7.3","1":"7.3","script_version":"3.4","2":"3.4","version_comment":"Use jobs for all Git execution.  Faster and less prone to user error.\r\nStream :Git! to the preview window.\r\nMake :Git grep behave like other :Git commands, not :Ggrep.\r\nSilence output and open quickfix list on :Ggrep -q.\r\nSupport :Ggrep outside repository with --no-index.\r\nExpand ##, $ENVVAR, and ~\/path in arguments to :Git.\r\nExpand \"%\" and other special sequences during tab completion.\r\nImprove tab completion for :Git push.\r\nDisable -- More -- prompt on :Git push, fetch, and --no-pager.\r\nProvide FugitiveObject\/FugitiveStageBlob\/FugitivePager events.\r\nSimplify :Gdiffsplit \"smart\" split direction.\r\nSupport jump to commit in :Git log --graph.\r\nUse local not upstream branch name for :GBrowse default.\r\nBetter support for ssh config in :GBrowse.\r\nReplace older deprecation warnings with error messages.\r\nAssorted public API enhancements.\r\nRequire Git 1.8.5 or newer.\r\nRequire Vim 7.3 or newer.  Full functionality requires Vim 8.1.\r\nDirectly echo :Git output for trivial commands like \"add\" on Vim 7.\r\nFix E1208 when loading plugin on Vim 8.2.3141.","3":"Use jobs for all Git execution.  Faster and less prone to user error.\r\nStream :Git! to the preview window.\r\nMake :Git grep behave like other :Git commands, not :Ggrep.\r\nSilence output and open quickfix list on :Ggrep -q.\r\nSupport :Ggrep outside repository with --no-index.\r\nExpand ##, $ENVVAR, and ~\/path in arguments to :Git.\r\nExpand \"%\" and other special sequences during tab completion.\r\nImprove tab completion for :Git push.\r\nDisable -- More -- prompt on :Git push, fetch, and --no-pager.\r\nProvide FugitiveObject\/FugitiveStageBlob\/FugitivePager events.\r\nSimplify :Gdiffsplit \"smart\" split direction.\r\nSupport jump to commit in :Git log --graph.\r\nUse local not upstream branch name for :GBrowse default.\r\nBetter support for ssh config in :GBrowse.\r\nReplace older deprecation warnings with error messages.\r\nAssorted public API enhancements.\r\nRequire Git 1.8.5 or newer.\r\nRequire Vim 7.3 or newer.  Full functionality requires Vim 8.1.\r\nDirectly echo :Git output for trivial commands like \"add\" on Vim 7.\r\nFix E1208 when loading plugin on Vim 8.2.3141.","package":"fugitive.zip","4":"fugitive.zip","src_id":"27726","5":"27726","creation_date":"1630640414","6":"1630640414"},{"0":"2975","vim_version":"7.0","1":"7.0","script_version":"3.3","2":"3.3","version_comment":"Replace :! :Git backend with smart job runner.\r\nReplace special cased commit\/revert\/rebase\/merge\/etc. with regular :Git.\r\nSupport :Git -c config.name=value and other common flags.\r\nImprove completion of :Git subcommands, including hiding plumbing commands.\r\nImprove completion of arguments to :Git subcommands.\r\nShow unpulled and unpushed sections for both upstream and push remote.\r\nIntroduce capitalized naming scheme for :GMove\/:GRename\/:GRemove\/:GDelete\/:GBrowse.\r\nExpand SSH host aliases in remote URLs for :GBrowse.\r\nEnable opening arbitrary URLs with :GBrowse.\r\nAdd warnings to deprecated commands.\r\nRemove all other temp buffer commands in favor of :Git --paginate.\r\nDon't automatically invoke :setlocal foldmethod=syntax in Fugitive buffers.\r\nSupport colored :Git blame commits in 256 color terminals.\r\nBug fixes.","3":"Replace :! :Git backend with smart job runner.\r\nReplace special cased commit\/revert\/rebase\/merge\/etc. with regular :Git.\r\nSupport :Git -c config.name=value and other common flags.\r\nImprove completion of :Git subcommands, including hiding plumbing commands.\r\nImprove completion of arguments to :Git subcommands.\r\nShow unpulled and unpushed sections for both upstream and push remote.\r\nIntroduce capitalized naming scheme for :GMove\/:GRename\/:GRemove\/:GDelete\/:GBrowse.\r\nExpand SSH host aliases in remote URLs for :GBrowse.\r\nEnable opening arbitrary URLs with :GBrowse.\r\nAdd warnings to deprecated commands.\r\nRemove all other temp buffer commands in favor of :Git --paginate.\r\nDon't automatically invoke :setlocal foldmethod=syntax in Fugitive buffers.\r\nSupport colored :Git blame commits in 256 color terminals.\r\nBug fixes.","package":"fugitive.zip","4":"fugitive.zip","src_id":"27571","5":"27571","creation_date":"1618538654","6":"1618538654"},{"0":"2975","vim_version":"7.0","1":"7.0","script_version":"3.2","2":"3.2","version_comment":"Provide :Git mergetool to load conflicts into quickfix list.\r\nProvide :Git difftool to load arbitrary changesets into quickfix list.\r\nCall FugitiveBlob\/FugitiveCommit\/etc autocommands on Fugitive buffer load.\r\n:Git --paginate display results in temp buffer.\r\n:Git --no-pager no longer displays results in temp buffer.\r\nAccomodate loading Fugitive buffers in popup window.\r\nBetter PowerShell support.\r\nBug fixes.","3":"Provide :Git mergetool to load conflicts into quickfix list.\r\nProvide :Git difftool to load arbitrary changesets into quickfix list.\r\nCall FugitiveBlob\/FugitiveCommit\/etc autocommands on Fugitive buffer load.\r\n:Git --paginate display results in temp buffer.\r\n:Git --no-pager no longer displays results in temp buffer.\r\nAccomodate loading Fugitive buffers in popup window.\r\nBetter PowerShell support.\r\nBug fixes.","package":"fugitive.zip","4":"fugitive.zip","src_id":"26933","5":"26933","creation_date":"1579637138","6":"1579637138"},{"0":"2975","vim_version":"7.0","1":"7.0","script_version":"3.1","2":"3.1","version_comment":"Commands are now global, not buffer local.\r\nCalling a command in an unnamed buffer uses the working directory.\r\nPreserve line number on :Gedit to return to work tree buffer.\r\nBetter submodule support in :Gstatus.\r\nSupport git-blame revision ignoring features.\r\nShow first parent diff in merge commit buffer.\r\nRemove deprecated support for .git\/tags.\r\nBug fixes.","3":"Commands are now global, not buffer local.\r\nCalling a command in an unnamed buffer uses the working directory.\r\nPreserve line number on :Gedit to return to work tree buffer.\r\nBetter submodule support in :Gstatus.\r\nSupport git-blame revision ignoring features.\r\nShow first parent diff in merge commit buffer.\r\nRemove deprecated support for .git\/tags.\r\nBug fixes.","package":"fugitive.zip","4":"fugitive.zip","src_id":"26783","5":"26783","creation_date":"1570783910","6":"1570783910"},{"0":"2975","vim_version":"7.0","1":"7.0","script_version":"3.0","2":"3.0","version_comment":"Use custom format for :Gstatus, not literal git status output.\r\nInline diffing in :Gstatus, with support for staging individual hunks.\r\nList unpushed and unpulled commits in :Gstatus.\r\nShow rebase status in :Gstatus.\r\nGreatly expanded set of mappings in :Gstatus. Try g?, c?, and r?.\r\n:Gstatus p (add --patch) is changed to P.\r\n:Gstatus U (checkout\/clean) is changed to X. New U behavior is global reset.\r\n:Gstatus 2X\/3X performs checkout --ours\/--theirs.\r\n:Gstatus gI ignores file.\r\nSmarter :Gstatus automatic reload.\r\n:Git subcommand calls :Gsubcommand when appropriate.\r\n:Git add --patch and similar commands use :terminal.\r\n:Git diff, :Git log, and :Git --no-pager display results in temp buffer.\r\n:Git and subcommand wrappers use custom quoting rather than shell escaping.\r\n:Git ... .\/path is relative to working directory.\r\nAdd --option completion to :Git and git wrappers.\r\nProvide :G as wrapper for both :Gstatus and :Git.\r\nSupport for :Grebase --interactive.\r\n:Gblame accepts all arguments, including filenames and commits.\r\nSupport :Gblame --reverse to navigate forwards through history.\r\nSupport :Gblame with range to blame subset of current file.\r\nAllow disabling dynamic blame colors with let g:fugitive_dynamic_colors = 0.\r\n:Glog opens quickfix list instead of displaying raw log output.\r\nCleaner :Glog quickfix list leveraging Vim's new \"module\" format.\r\n:Glog no longer defaults to current file.  Use :0Glog for that.\r\n:0Glog follows file across renames.\r\n:Glog name softly deprecated in favor of :Gclog (named after :cfile).\r\nProvide :Grevert.\r\n:Gdiff renamed to :Gdiffsplit.\r\n:Gdiffsplit always opens one window.  Use :Gdiffsplit! for conflicts.\r\nSupport git grep --column.\r\nChdir with git -C rather than :cd for most commands. (Git 1.8.5 required).\r\nShow all stderr hook output on :Gcommit.\r\nProvide core.askPass default for Gpush and friends.\r\nRequire bang to :Gwrite from index.\r\nBug fixes.\r\nPolish.","3":"Use custom format for :Gstatus, not literal git status output.\r\nInline diffing in :Gstatus, with support for staging individual hunks.\r\nList unpushed and unpulled commits in :Gstatus.\r\nShow rebase status in :Gstatus.\r\nGreatly expanded set of mappings in :Gstatus. Try g?, c?, and r?.\r\n:Gstatus p (add --patch) is changed to P.\r\n:Gstatus U (checkout\/clean) is changed to X. New U behavior is global reset.\r\n:Gstatus 2X\/3X performs checkout --ours\/--theirs.\r\n:Gstatus gI ignores file.\r\nSmarter :Gstatus automatic reload.\r\n:Git subcommand calls :Gsubcommand when appropriate.\r\n:Git add --patch and similar commands use :terminal.\r\n:Git diff, :Git log, and :Git --no-pager display results in temp buffer.\r\n:Git and subcommand wrappers use custom quoting rather than shell escaping.\r\n:Git ... .\/path is relative to working directory.\r\nAdd --option completion to :Git and git wrappers.\r\nProvide :G as wrapper for both :Gstatus and :Git.\r\nSupport for :Grebase --interactive.\r\n:Gblame accepts all arguments, including filenames and commits.\r\nSupport :Gblame --reverse to navigate forwards through history.\r\nSupport :Gblame with range to blame subset of current file.\r\nAllow disabling dynamic blame colors with let g:fugitive_dynamic_colors = 0.\r\n:Glog opens quickfix list instead of displaying raw log output.\r\nCleaner :Glog quickfix list leveraging Vim's new \"module\" format.\r\n:Glog no longer defaults to current file.  Use :0Glog for that.\r\n:0Glog follows file across renames.\r\n:Glog name softly deprecated in favor of :Gclog (named after :cfile).\r\nProvide :Grevert.\r\n:Gdiff renamed to :Gdiffsplit.\r\n:Gdiffsplit always opens one window.  Use :Gdiffsplit! for conflicts.\r\nSupport git grep --column.\r\nChdir with git -C rather than :cd for most commands. (Git 1.8.5 required).\r\nShow all stderr hook output on :Gcommit.\r\nProvide core.askPass default for Gpush and friends.\r\nRequire bang to :Gwrite from index.\r\nBug fixes.\r\nPolish.","package":"fugitive.zip","4":"fugitive.zip","src_id":"26701","5":"26701","creation_date":"1566344720","6":"1566344720"},{"0":"2975","vim_version":"7.0","1":"7.0","script_version":"2.5","2":"2.5","version_comment":"Support :source and :write on Fugitive URLs.\r\nSupport :Gedit +cmd ++opt.\r\nSupport :Gedit \/absolute\/path and .\/relative\/path.\r\nSupport expansion flags, like :Gedit %:h.\r\nSupport completion of commits for --fixup=\/--squash=.\r\nSupport :Gread commit to read commit message.\r\nAdjust :Gbrowse line range for upstream head.\r\nMap <CR> in blobs to jump to blamed commit.\r\nMap p to jump to file in preview window.\r\nMake :Gmove always relative to repository root.\r\nLoad Projectionist config from .git\/info\/projections.json.\r\nDrop instaweb support.\r\nNew public function API.\r\nMajor robustness and error handling improvements.\r\nBug fixes.","3":"Support :source and :write on Fugitive URLs.\r\nSupport :Gedit +cmd ++opt.\r\nSupport :Gedit \/absolute\/path and .\/relative\/path.\r\nSupport expansion flags, like :Gedit %:h.\r\nSupport completion of commits for --fixup=\/--squash=.\r\nSupport :Gread commit to read commit message.\r\nAdjust :Gbrowse line range for upstream head.\r\nMap <CR> in blobs to jump to blamed commit.\r\nMap p to jump to file in preview window.\r\nMake :Gmove always relative to repository root.\r\nLoad Projectionist config from .git\/info\/projections.json.\r\nDrop instaweb support.\r\nNew public function API.\r\nMajor robustness and error handling improvements.\r\nBug fixes.","package":"fugitive.zip","4":"fugitive.zip","src_id":"26285","5":"26285","creation_date":"1542934893","6":"1542934893"},{"0":"2975","vim_version":"7.0","1":"7.0","script_version":"2.4","2":"2.4","version_comment":"Split into plugin, autoload, and ftdetect files.\r\nSupport mods like :vertical on :Gstatus and :Gedit family.\r\nProvide :Grebase (no --interactive).\r\nBug fixes.","3":"Split into plugin, autoload, and ftdetect files.\r\nSupport mods like :vertical on :Gstatus and :Gedit family.\r\nProvide :Grebase (no --interactive).\r\nBug fixes.","package":"fugitive.zip","4":"fugitive.zip","src_id":"26124","5":"26124","creation_date":"1531227915","6":"1531227915"},{"0":"2975","vim_version":"7.0","1":"7.0","script_version":"2.3","2":"2.3","version_comment":"Support worktrees.\r\nProvide API for extensible :Gbrowse support.\r\nRemove GitHub URL support in favor of rhubarb.vim.\r\nProvide :Gdelete to delete both file and buffer.\r\nProvide :Grename to move relative to file's parent directory.\r\nSplit to open file when :Gstatus is only window.\r\nProvide U in :Gstatus to discard changes.\r\nProvide additional :Gstatus commit maps.\r\nProvide d2o and d3o to obtain diff during conflict.\r\nSupport :tab Gcommit.\r\nOpen :Gcommit tab before current.\r\nSupport :Gdiff +cmd.\r\nSupport gf in Git file types.\r\nAdd flagship.vim statusline indicator.\r\nUse the Neovim terminal emulator for :Git.\r\nBug fixes.","3":"Support worktrees.\r\nProvide API for extensible :Gbrowse support.\r\nRemove GitHub URL support in favor of rhubarb.vim.\r\nProvide :Gdelete to delete both file and buffer.\r\nProvide :Grename to move relative to file's parent directory.\r\nSplit to open file when :Gstatus is only window.\r\nProvide U in :Gstatus to discard changes.\r\nProvide additional :Gstatus commit maps.\r\nProvide d2o and d3o to obtain diff during conflict.\r\nSupport :tab Gcommit.\r\nOpen :Gcommit tab before current.\r\nSupport :Gdiff +cmd.\r\nSupport gf in Git file types.\r\nAdd flagship.vim statusline indicator.\r\nUse the Neovim terminal emulator for :Git.\r\nBug fixes.","package":"fugitive.zip","4":"fugitive.zip","src_id":"25997","5":"25997","creation_date":"1527564326","6":"1527564326"},{"0":"2975","vim_version":"7.0","1":"7.0","script_version":"2.2","2":"2.2","version_comment":"Provide :Gpush, :Gfetch, :Gmerge, and Gpull.\r\nUse -L to handle :Glog range.\r\n:Gcommit -v opens message in new tab.\r\nAPI for custom :Gbrowse handlers.\r\nInvoke :Browse if available to open URL.\r\nColorize hashes in :Gblame buffer.\r\nSet cursorbind and nobuflisted in :Gblame buffers.\r\n:Gblame in blame buffer toggles buffer.","3":"Provide :Gpush, :Gfetch, :Gmerge, and Gpull.\r\nUse -L to handle :Glog range.\r\n:Gcommit -v opens message in new tab.\r\nAPI for custom :Gbrowse handlers.\r\nInvoke :Browse if available to open URL.\r\nColorize hashes in :Gblame buffer.\r\nSet cursorbind and nobuflisted in :Gblame buffers.\r\n:Gblame in blame buffer toggles buffer.","package":"fugitive.zip","4":"fugitive.zip","src_id":"22815","5":"22815","creation_date":"1421735898","6":"1421735898"},{"0":"2975","vim_version":"7.0","1":"7.0","script_version":"2.1","2":"2.1","version_comment":"Fix :Gdiff horizontal\/vertical disposition.","3":"Fix :Gdiff horizontal\/vertical disposition.","package":"fugitive.zip","4":"fugitive.zip","src_id":"22093","5":"22093","creation_date":"1403641944","6":"1403641944"},{"0":"2975","vim_version":"7.0","1":"7.0","script_version":"2.0","2":"2.0","version_comment":"<C-R><C-G> in :Gstatus recalls cursor line filename.\r\nMap dp to show diff in :Gstatus.\r\nAdd ca and cA commit maps to :Gstatus.\r\nAdd cc alias for C in :Gstatus.\r\nDisable swapfile in :Gstatus.\r\nReplace :Gstatus cv with cva and cvc.\r\nAdd an `S` mapping for vertical splits from :Gstatus.\r\nClose diffs when navigating from :Gstatus.\r\nEnable folding in :Gstatus.\r\nAccept a count with :Gstatus <C-N>\/<C-P>.\r\nAllow <C-p> pass through to ctrlp.vim in :Gstatus.\r\nAdd . in :Gstatus to prepopulate command line with revision.\r\nFix :Gstatus dp with external diff enabled.\r\nForce displayCommentPrefix to fix :Gstatus on 1.8.5+.\r\nSupport localized `git status`.\r\nMap g? and <F1> to show help in :Gstatus and :Gblame.\r\nKill relativenumber in blame buffer.\r\nFix jump to line on reblame.\r\nReturn to blamed buffer on q in blame.\r\nRestore blamed window on gq in blame.\r\nFix :Gblame scrollbind with folds.\r\nJump from blame to commit focuses relevant diff.\r\n:Gblame: Retain original alternate buffer.\r\nUse - not <CR> for reblame.\r\nSwitch :Gblame <CR> to open commit.\r\nOpen fold when jumping to commit from blame.\r\nAdd maps for resizing blame window.\r\nConceal file names and line numbers in :Gblame.\r\nSet winfixwidth in :Gblame buffers.\r\nPress <CR> in :Gblame to open commit (reblame is now -).\r\nBetter csh support.\r\nWork around \"always\" color option.\r\nFix trailing blank line when editing index files.\r\nUse HTTPS for GitHub URLs in README.\r\n:Gdiff split direction based on 'diffopt' and window size.\r\nFocus diff window on :Gdiff.\r\nRestore options when turning off diff mode.\r\nSet bufhidden=delete in historical buffers.\r\nFix modeline errors in historical buffers.\r\nChange cp to cP.\r\nAdd :Git! et al. for loading output into a buffer.\r\nTab complete Git aliases.\r\nEnter on a +\/- diff line jumps to that line.\r\nBetter Windows support.\r\nSupport core.autocrlf=false on Windows.\r\nWork around slow \\\\ Windows network path.\r\nWork around .git in 'wildignore'.\r\nFix garbage during :Gcommit with alternate screen.\r\nFix garbling on :Gcommit when nothing is staged.\r\nHack around broken :Gcommit with symlinked .git.\r\nUse y<C-G> to yank the current object's path.\r\nPreserve alternate file in :Gmove.\r\nSupport bare repositories that don't end in .git.\r\nSupport .git-file repositories (including submodules).\r\nSupport symlinked .git if core.worktree is set.\r\nFix redraw issue after :Gbrowse.\r\nSupport GitHub FI in :Gbrowse.\r\nSupport implicit GitHub username in remote for :Gbrowse.\r\nMake fugitive commands available in nerdtree buffers.\r\nMake fugitive commands available in command line window.\r\n:Glgrep and :Gllog.\r\n:.Glog jumps to same line in each file.\r\nMap - to go up a directory.\r\nProvide custom 'foldtext'.\r\nRespect $GIT_CEILING_DIRECTORIES.\r\nLook for $GIT_DIR and $GIT_WORK_TREE.\r\nImprove Windows support.\r\nAssorted bug fixes.","3":"<C-R><C-G> in :Gstatus recalls cursor line filename.\r\nMap dp to show diff in :Gstatus.\r\nAdd ca and cA commit maps to :Gstatus.\r\nAdd cc alias for C in :Gstatus.\r\nDisable swapfile in :Gstatus.\r\nReplace :Gstatus cv with cva and cvc.\r\nAdd an `S` mapping for vertical splits from :Gstatus.\r\nClose diffs when navigating from :Gstatus.\r\nEnable folding in :Gstatus.\r\nAccept a count with :Gstatus <C-N>\/<C-P>.\r\nAllow <C-p> pass through to ctrlp.vim in :Gstatus.\r\nAdd . in :Gstatus to prepopulate command line with revision.\r\nFix :Gstatus dp with external diff enabled.\r\nForce displayCommentPrefix to fix :Gstatus on 1.8.5+.\r\nSupport localized `git status`.\r\nMap g? and <F1> to show help in :Gstatus and :Gblame.\r\nKill relativenumber in blame buffer.\r\nFix jump to line on reblame.\r\nReturn to blamed buffer on q in blame.\r\nRestore blamed window on gq in blame.\r\nFix :Gblame scrollbind with folds.\r\nJump from blame to commit focuses relevant diff.\r\n:Gblame: Retain original alternate buffer.\r\nUse - not <CR> for reblame.\r\nSwitch :Gblame <CR> to open commit.\r\nOpen fold when jumping to commit from blame.\r\nAdd maps for resizing blame window.\r\nConceal file names and line numbers in :Gblame.\r\nSet winfixwidth in :Gblame buffers.\r\nPress <CR> in :Gblame to open commit (reblame is now -).\r\nBetter csh support.\r\nWork around \"always\" color option.\r\nFix trailing blank line when editing index files.\r\nUse HTTPS for GitHub URLs in README.\r\n:Gdiff split direction based on 'diffopt' and window size.\r\nFocus diff window on :Gdiff.\r\nRestore options when turning off diff mode.\r\nSet bufhidden=delete in historical buffers.\r\nFix modeline errors in historical buffers.\r\nChange cp to cP.\r\nAdd :Git! et al. for loading output into a buffer.\r\nTab complete Git aliases.\r\nEnter on a +\/- diff line jumps to that line.\r\nBetter Windows support.\r\nSupport core.autocrlf=false on Windows.\r\nWork around slow \\\\ Windows network path.\r\nWork around .git in 'wildignore'.\r\nFix garbage during :Gcommit with alternate screen.\r\nFix garbling on :Gcommit when nothing is staged.\r\nHack around broken :Gcommit with symlinked .git.\r\nUse y<C-G> to yank the current object's path.\r\nPreserve alternate file in :Gmove.\r\nSupport bare repositories that don't end in .git.\r\nSupport .git-file repositories (including submodules).\r\nSupport symlinked .git if core.worktree is set.\r\nFix redraw issue after :Gbrowse.\r\nSupport GitHub FI in :Gbrowse.\r\nSupport implicit GitHub username in remote for :Gbrowse.\r\nMake fugitive commands available in nerdtree buffers.\r\nMake fugitive commands available in command line window.\r\n:Glgrep and :Gllog.\r\n:.Glog jumps to same line in each file.\r\nMap - to go up a directory.\r\nProvide custom 'foldtext'.\r\nRespect $GIT_CEILING_DIRECTORIES.\r\nLook for $GIT_DIR and $GIT_WORK_TREE.\r\nImprove Windows support.\r\nAssorted bug fixes.","package":"fugitive.zip","4":"fugitive.zip","src_id":"22084","5":"22084","creation_date":"1403531548","6":"1403531548"},{"0":"2975","vim_version":"7.0","1":"7.0","script_version":"1.2","2":"1.2","version_comment":"Support :Gmove in a directory.\r\nProvide :Gbrowse to open code on GitHub or in git-instaweb.\r\nProvide :Gwq to :quit after :Gwrite.\r\nProvide :Gsdiff to do a horizontal diff.\r\nMap ds in :Gstatus to do a horizontal diff.\r\nMap <C-N> and <C-P> in :Gstatus to cycle between files.\r\nMap `-` on headings in :Gstatus.\r\nMap dp in stage conflict to do the right thing.\r\nPoint 'tags' at .git\/tags.\r\nWindows fixes. [Michael Geddes]\r\n","3":"Support :Gmove in a directory.\r\nProvide :Gbrowse to open code on GitHub or in git-instaweb.\r\nProvide :Gwq to :quit after :Gwrite.\r\nProvide :Gsdiff to do a horizontal diff.\r\nMap ds in :Gstatus to do a horizontal diff.\r\nMap <C-N> and <C-P> in :Gstatus to cycle between files.\r\nMap `-` on headings in :Gstatus.\r\nMap dp in stage conflict to do the right thing.\r\nPoint 'tags' at .git\/tags.\r\nWindows fixes. [Michael Geddes]\r\n","package":"fugitive.zip","4":"fugitive.zip","src_id":"15542","5":"15542","creation_date":"1304048293","6":"1304048293"},{"0":"2975","vim_version":"7.0","1":"7.0","script_version":"1.1","2":"1.1","version_comment":"Much better windows support ('shellslash' no longer required).\r\nDelete blame buffers when closed.\r\nPass :Gblame flags along to git-blame.\r\nFix duplicate \"Signed-off-by\" lines.\r\nFinish pending commit even if exiting Vim.\r\nAllow double quotes in :Git and :Ggrep arguments.\r\n`D` in :Gstatus shows a diff.","3":"Much better windows support ('shellslash' no longer required).\r\nDelete blame buffers when closed.\r\nPass :Gblame flags along to git-blame.\r\nFix duplicate \"Signed-off-by\" lines.\r\nFinish pending commit even if exiting Vim.\r\nAllow double quotes in :Git and :Ggrep arguments.\r\n`D` in :Gstatus shows a diff.","package":"fugitive.zip","4":"fugitive.zip","src_id":"12673","5":"12673","creation_date":"1269206358","6":"1269206358"},{"0":"2975","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"fugitive.zip","4":"fugitive.zip","src_id":"12387","5":"12387","creation_date":"1266260809","6":"1266260809"}]},"2974":{"script_id":"2974","0":"2974","script_name":"mrkn256.vim","1":"mrkn256.vim","script_type":"color scheme","2":"color scheme","summary":"Color scheme designed by mrkn, for 88- and 256-color xterms.","3":"Color scheme designed by mrkn, for 88- and 256-color xterms.","description":"These are the color theme designed by mrkn based on \"desert256\" theme created by Henry So, Jr.  This theme is designed to work with with 88- and 256-color xterms.\r\n\r\nA screen shot is available at http:\/\/img.skitch.com\/20100215-rxeg4nguregi8i21dyarspmsgc.png\r\n\r\nThe ancestor version \"desert256\" theme is available at http:\/\/www.vim.org\/scripts\/script.php?script_id=1243\r\n\r\nThe real feature of this color scheme, with a wink to the \"inkpot\" theme, is the programmatic approximation of the gui colors to the palettes of 88- and 256- color xterms.  The functions that do this (folded away, for readability) are calibrated to the colors used for Thomas E. Dickey's xterm (version 200), which is available at http:\/\/dickey.his.com\/xterm\/xterm.html.\r\n\r\nHenry had struggled with trying to parse the rgb.txt file to avoid the necessity of converting color names to #rrggbb form, but decided it was just not worth the effort.  I thank a lot for his results.\r\n","4":"These are the color theme designed by mrkn based on \"desert256\" theme created by Henry So, Jr.  This theme is designed to work with with 88- and 256-color xterms.\r\n\r\nA screen shot is available at http:\/\/img.skitch.com\/20100215-rxeg4nguregi8i21dyarspmsgc.png\r\n\r\nThe ancestor version \"desert256\" theme is available at http:\/\/www.vim.org\/scripts\/script.php?script_id=1243\r\n\r\nThe real feature of this color scheme, with a wink to the \"inkpot\" theme, is the programmatic approximation of the gui colors to the palettes of 88- and 256- color xterms.  The functions that do this (folded away, for readability) are calibrated to the colors used for Thomas E. Dickey's xterm (version 200), which is available at http:\/\/dickey.his.com\/xterm\/xterm.html.\r\n\r\nHenry had struggled with trying to parse the rgb.txt file to avoid the necessity of converting color names to #rrggbb form, but decided it was just not worth the effort.  I thank a lot for his results.\r\n","install_details":"Copy this file into ~\/.vim\/colors (or $VIM\/vimfiles\/colors in Windows).  Start it from within vim using :colorscheme mrkn256.","5":"Copy this file into ~\/.vim\/colors (or $VIM\/vimfiles\/colors in Windows).  Start it from within vim using :colorscheme mrkn256.","first_name":"Kenta","6":"Kenta","last_name":"Murata","7":"Murata","releases":[{"0":"2974","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"mrkn256.vim","4":"mrkn256.vim","src_id":"12384","5":"12384","creation_date":"1266246271","6":"1266246271"}]},"2973":{"script_id":"2973","0":"2973","script_name":"cucumber.zip","1":"cucumber.zip","script_type":"utility","2":"utility","summary":"Cucumber runtime files","3":"Cucumber runtime files","description":"This provides syntax highlightling, indenting, and a filetype plugin for Cucumber, the acceptance testing framework. It's mostly self explanatory. You can use CTRL-] on a step to jump to its Ruby definition.\r\n\r\nIf you want to keep up to date, use the version upstream:\r\n\r\nhttp:\/\/github.com\/tpope\/vim-cucumber","4":"This provides syntax highlightling, indenting, and a filetype plugin for Cucumber, the acceptance testing framework. It's mostly self explanatory. You can use CTRL-] on a step to jump to its Ruby definition.\r\n\r\nIf you want to keep up to date, use the version upstream:\r\n\r\nhttp:\/\/github.com\/tpope\/vim-cucumber","install_details":"Extract in ~\/.vim (~\\vimfiles on Windows).","5":"Extract in ~\/.vim (~\\vimfiles on Windows).","first_name":"Tim","6":"Tim","last_name":"Pope","7":"Pope","releases":[{"0":"2973","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"cucumber.zip","4":"cucumber.zip","src_id":"12385","5":"12385","creation_date":"1266248297","6":"1266248297"}]},"2972":{"script_id":"2972","0":"2972","script_name":"hmac.vim","1":"hmac.vim","script_type":"utility","2":"utility","summary":"hmac() function","3":"hmac() function","description":"This is a port of rfc 2104 hmac function.\r\n\r\nhmac#md5(key, text) require vimscript#2806\r\nhmac#sha1(key, text) require vimscript#2971","4":"This is a port of rfc 2104 hmac function.\r\n\r\nhmac#md5(key, text) require vimscript#2806\r\nhmac#sha1(key, text) require vimscript#2971","install_details":"Put file in your autoload directory.","5":"Put file in your autoload directory.","first_name":"Yukihiro","6":"Yukihiro","last_name":"Nakadaira","7":"Nakadaira","releases":[{"0":"2972","vim_version":"7.2","1":"7.2","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"hmac.vim","4":"hmac.vim","src_id":"12380","5":"12380","creation_date":"1266050478","6":"1266050478"}]},"2971":{"script_id":"2971","0":"2971","script_name":"sha1.vim","1":"sha1.vim","script_type":"utility","2":"utility","summary":"sha1() function","3":"sha1() function","description":"This is a port of rfc 3174 sha1 function.\r\n\r\n:echo sha1#sha1(\"hello, world\")\r\nb7e23ec29af22b0b4e41da31e868d57226121c84","4":"This is a port of rfc 3174 sha1 function.\r\n\r\n:echo sha1#sha1(\"hello, world\")\r\nb7e23ec29af22b0b4e41da31e868d57226121c84","install_details":"Put file in your autoload directory.","5":"Put file in your autoload directory.","first_name":"Yukihiro","6":"Yukihiro","last_name":"Nakadaira","7":"Nakadaira","releases":[{"0":"2971","vim_version":"7.2","1":"7.2","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"sha1.vim","4":"sha1.vim","src_id":"12378","5":"12378","creation_date":"1266034407","6":"1266034407"}]},"2970":{"script_id":"2970","0":"2970","script_name":"ISBN-10 to EAN-13 converter","1":"ISBN-10 to EAN-13 converter","script_type":"utility","2":"utility","summary":"Convert ISBNs to EAN-13s","3":"Convert ISBNs to EAN-13s","description":"Allows conversions between ISBN-10 >> 978 prefix EAN-13s, and 978 prefix EAN-13s >> ISBN-10 \r\n\r\nThere are three methods of converting ISBNs and EANs: \r\n\r\n:ReplaceLineIsbnEan \r\n    If the entirety of the current line is a valid ISBN-10, replaces it with the converted 978 prefix \r\n    EAN-13 \r\n:ReplaceLineEanIsbn \r\n    If the entirety of the current line is a valid EAN-13 with a 978 prefix, replaces it with the \r\n    converted ISBN-10 \r\n\r\n:ReplaceSelectedIsbnEan \r\n    If the selected text is a valid ISBN-10, replaces that text with the converted 978 prefix EAN-13 \r\n:ReplaceSelectedEanIsbn \r\n    If the selected text is a valid EAN-13 with a 978 prefix, replaces it with the converted ISBN-10 \r\n\r\n:ReplaceAllIsbnEan \r\n    Searches for any 10 digit number, of 9 digit number followed by x or X. For each match, if it is \r\n    a valid ISBN-10, then it replaces that match with the converted 978 prefix EAN-13 \r\n:ReplaceAllEanIsbn \r\n    Searches for any 13 digit number. For each match, if it is a valid 978 prefix EAN-13, then it \r\n    replaces that match with the converted ISBN-10.","4":"Allows conversions between ISBN-10 >> 978 prefix EAN-13s, and 978 prefix EAN-13s >> ISBN-10 \r\n\r\nThere are three methods of converting ISBNs and EANs: \r\n\r\n:ReplaceLineIsbnEan \r\n    If the entirety of the current line is a valid ISBN-10, replaces it with the converted 978 prefix \r\n    EAN-13 \r\n:ReplaceLineEanIsbn \r\n    If the entirety of the current line is a valid EAN-13 with a 978 prefix, replaces it with the \r\n    converted ISBN-10 \r\n\r\n:ReplaceSelectedIsbnEan \r\n    If the selected text is a valid ISBN-10, replaces that text with the converted 978 prefix EAN-13 \r\n:ReplaceSelectedEanIsbn \r\n    If the selected text is a valid EAN-13 with a 978 prefix, replaces it with the converted ISBN-10 \r\n\r\n:ReplaceAllIsbnEan \r\n    Searches for any 10 digit number, of 9 digit number followed by x or X. For each match, if it is \r\n    a valid ISBN-10, then it replaces that match with the converted 978 prefix EAN-13 \r\n:ReplaceAllEanIsbn \r\n    Searches for any 13 digit number. For each match, if it is a valid 978 prefix EAN-13, then it \r\n    replaces that match with the converted ISBN-10.","install_details":"Copy ean13.vim to your plugins directory.","5":"Copy ean13.vim to your plugins directory.","first_name":"Brandon","6":"Brandon","last_name":"Waskiewicz","7":"Waskiewicz","releases":[{"0":"2970","vim_version":"6.0","1":"6.0","script_version":"0.95","2":"0.95","version_comment":"Removed previous version.\r\n\r\nAdded several new functions.\r\nMapped basic user commands.\r\nAdded license.\r\nRemoved bug with replace-all that would skip valid match at beginning of buffer.","3":"Removed previous version.\r\n\r\nAdded several new functions.\r\nMapped basic user commands.\r\nAdded license.\r\nRemoved bug with replace-all that would skip valid match at beginning of buffer.","package":"ean13.vim","4":"ean13.vim","src_id":"12386","5":"12386","creation_date":"1266251006","6":"1266251006"}]},"2969":{"script_id":"2969","0":"2969","script_name":"ucf.vim","1":"ucf.vim","script_type":"syntax","2":"syntax","summary":"Xilinx User Constraint File Syntax","3":"Xilinx User Constraint File Syntax","description":"This is a syntax file for a Xilinx FPGA User Constraint File (*.ucf)","4":"This is a syntax file for a Xilinx FPGA User Constraint File (*.ucf)","install_details":"Put it in your ~vim\/vimfiles\/syntax directory. At that point you should have the option to switch to the ucf syntax.\r\n\r\nThen, either create a file in ~vim\/vimfile\/ftdetect with the following line, or if you use one global file for all your file type detections, at it to the global file. Check the vim help on \"new file-type\" (ie :help new-filetype).","5":"Put it in your ~vim\/vimfiles\/syntax directory. At that point you should have the option to switch to the ucf syntax.\r\n\r\nThen, either create a file in ~vim\/vimfile\/ftdetect with the following line, or if you use one global file for all your file type detections, at it to the global file. Check the vim help on \"new file-type\" (ie :help new-filetype).","first_name":"Russell","6":"Russell","last_name":"Brinkmann","7":"Brinkmann","releases":[{"0":"2969","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"ucf.vim","4":"ucf.vim","src_id":"12343","5":"12343","creation_date":"1265713788","6":"1265713788"}]},"2968":{"script_id":"2968","0":"2968","script_name":"ikiwiki-nav","1":"ikiwiki-nav","script_type":"ftplugin","2":"ftplugin","summary":"several helpers for editing ikiwiki pages","3":"several helpers for editing ikiwiki pages","description":"This ftplugin eases the editing of IkiWiki wikis by providing the following features:\r\n\r\n  * Wikilink autocompletion through omnicompletion.\r\n  * Jump to previous\/next wikilink\r\n  * Open the file corresponding to the wikilink under the cursor in the current window\/a new window\/a new tab page\r\n  * Create the file corresponing to the wikilink under the cursor in the current window\/a new window\/a new tab page\r\n\r\nFor the usage details, mappings defined and other stuff, see :help ikiwiki-intro after you install the plugin\r\n\r\nThere is a git repo for the plugin in  http:\/\/git.devnull.li\/ikiwiki-nav.git\/. The master branch always has the latest stable version, and the dev branch has the latest version of the plugin.\r\n\r\nFeel free to contact the author (see the AUTHORS file in the package) with bug reports\/suggestions\/whatever :)","4":"This ftplugin eases the editing of IkiWiki wikis by providing the following features:\r\n\r\n  * Wikilink autocompletion through omnicompletion.\r\n  * Jump to previous\/next wikilink\r\n  * Open the file corresponding to the wikilink under the cursor in the current window\/a new window\/a new tab page\r\n  * Create the file corresponing to the wikilink under the cursor in the current window\/a new window\/a new tab page\r\n\r\nFor the usage details, mappings defined and other stuff, see :help ikiwiki-intro after you install the plugin\r\n\r\nThere is a git repo for the plugin in  http:\/\/git.devnull.li\/ikiwiki-nav.git\/. The master branch always has the latest stable version, and the dev branch has the latest version of the plugin.\r\n\r\nFeel free to contact the author (see the AUTHORS file in the package) with bug reports\/suggestions\/whatever :)","install_details":"unzip the zip file and move all the files in the ikiwiki-nav_2.0.2 folder to your .vim directory.\r\n\r\nfrom inside vim, run the command:\r\n\r\n    helptags $HOME\/.vim\/doc","5":"unzip the zip file and move all the files in the ikiwiki-nav_2.0.2 folder to your .vim directory.\r\n\r\nfrom inside vim, run the command:\r\n\r\n    helptags $HOME\/.vim\/doc","first_name":"Javier","6":"Javier","last_name":"Rojas","7":"Rojas","releases":[{"0":"2968","vim_version":"7.0","1":"7.0","script_version":"2.0.2","2":"2.0.2","version_comment":"Fixed an annoying warning that appeared if any of the lhs of the default mappings has already been used. Thanks to F. Heiderich for the report and fix.","3":"Fixed an annoying warning that appeared if any of the lhs of the default mappings has already been used. Thanks to F. Heiderich for the report and fix.","package":"ikiwiki-nav_2.0.2.zip","4":"ikiwiki-nav_2.0.2.zip","src_id":"16496","5":"16496","creation_date":"1315590914","6":"1315590914"},{"0":"2968","vim_version":"7.0","1":"7.0","script_version":"2.0","2":"2.0","version_comment":"Added capabilities for creating wiki pages, and for wikilink completion through the omnicompletion framework","3":"Added capabilities for creating wiki pages, and for wikilink completion through the omnicompletion framework","package":"ikiwiki-nav_2.0.zip","4":"ikiwiki-nav_2.0.zip","src_id":"13814","5":"13814","creation_date":"1284335104","6":"1284335104"},{"0":"2968","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"ikiwiki_nav.vim","4":"ikiwiki_nav.vim","src_id":"12342","5":"12342","creation_date":"1265687401","6":"1265687401"}]},"2967":{"script_id":"2967","0":"2967","script_name":"daemon_saver.vim","1":"daemon_saver.vim","script_type":"game","2":"game","summary":"Vim version of FreeBSD daemon_saver","3":"Vim version of FreeBSD daemon_saver","description":"This is a Vim version of daemon_saver from FreeBSD.\r\nThe script adds :Daemon command, which starts screensaver.\r\nDaemon speed is adjustable through g:daemon_saver_speed variable. Default is '80' (ms).\r\n\r\nTo start the screensaver automatically after some time put this to your .vimrc:\r\n\r\nau CursorHold * Daemon\r\nset updatetime=60000\r\n\r\nThis will start Daemon after 60 seconds of vim being idle.","4":"This is a Vim version of daemon_saver from FreeBSD.\r\nThe script adds :Daemon command, which starts screensaver.\r\nDaemon speed is adjustable through g:daemon_saver_speed variable. Default is '80' (ms).\r\n\r\nTo start the screensaver automatically after some time put this to your .vimrc:\r\n\r\nau CursorHold * Daemon\r\nset updatetime=60000\r\n\r\nThis will start Daemon after 60 seconds of vim being idle.","install_details":"Add script to plugin directory.","5":"Add script to plugin directory.","first_name":"forneus","6":"forneus","last_name":"forneus","7":"forneus","releases":[{"0":"2967","vim_version":"7.0","1":"7.0","script_version":"2.1","2":"2.1","version_comment":"* fixes changing background on cterm \r\n* fixes restroring syntax highliting","3":"* fixes changing background on cterm \r\n* fixes restroring syntax highliting","package":"daemon_saver.vim","4":"daemon_saver.vim","src_id":"12361","5":"12361","creation_date":"1265976848","6":"1265976848"},{"0":"2967","vim_version":"7.0","1":"7.0","script_version":"2.0","2":"2.0","version_comment":"* works with NERDTree & TagList \r\n* restores help window\r\n* stores more session information","3":"* works with NERDTree & TagList \r\n* restores help window\r\n* stores more session information","package":"daemon_saver.vim","4":"daemon_saver.vim","src_id":"12356","5":"12356","creation_date":"1265894873","6":"1265894873"},{"0":"2967","vim_version":"7.0","1":"7.0","script_version":"1.1","2":"1.1","version_comment":"* works with modified buffers\r\n* restores Cursor colors properly\r\n* uses minimum session information","3":"* works with modified buffers\r\n* restores Cursor colors properly\r\n* uses minimum session information","package":"daemon_saver.vim","4":"daemon_saver.vim","src_id":"12353","5":"12353","creation_date":"1265800319","6":"1265800319"},{"0":"2967","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"daemon_saver.vim","4":"daemon_saver.vim","src_id":"12333","5":"12333","creation_date":"1265569339","6":"1265569339"}]},"2966":{"script_id":"2966","0":"2966","script_name":"Doxia APT","1":"Doxia APT","script_type":"syntax","2":"syntax","summary":"syntax highlighting of Doxia APT files as used by Maven","3":"syntax highlighting of Doxia APT files as used by Maven","description":"Syntax highlighting for Doxia APT files, as used by Maven for documentation purposes. The format is described here: http:\/\/maven.apache.org\/doxia\/references\/apt-format.html","4":"Syntax highlighting for Doxia APT files, as used by Maven for documentation purposes. The format is described here: http:\/\/maven.apache.org\/doxia\/references\/apt-format.html","install_details":"Just copy the file to your local syntax directory and put something like this in your local filetype.vim:\r\n  au! BufRead,BufNewFile *.apt  setf doxiaapt\r\n","5":"Just copy the file to your local syntax directory and put something like this in your local filetype.vim:\r\n  au! BufRead,BufNewFile *.apt  setf doxiaapt\r\n","first_name":"Joris","6":"Joris","last_name":"Kuipers","7":"Kuipers","releases":[{"0":"2966","vim_version":"5.7","1":"5.7","script_version":"1.1","2":"1.1","version_comment":"minor cleanups, added syntax support for macros (http:\/\/maven.apache.org\/doxia\/macros\/index.html)","3":"minor cleanups, added syntax support for macros (http:\/\/maven.apache.org\/doxia\/macros\/index.html)","package":"doxiaapt.vim","4":"doxiaapt.vim","src_id":"12341","5":"12341","creation_date":"1265665418","6":"1265665418"},{"0":"2966","vim_version":"5.7","1":"5.7","script_version":"1.0","2":"1.0","version_comment":"initial release","3":"initial release","package":"doxiaapt.vim","4":"doxiaapt.vim","src_id":"12330","5":"12330","creation_date":"1265544756","6":"1265544756"}]},"2965":{"script_id":"2965","0":"2965","script_name":"SyntaxMotion.vim","1":"SyntaxMotion.vim","script_type":"utility","2":"utility","summary":"Cursor motion & visual selection by syntax highlighting group","3":"Cursor motion & visual selection by syntax highlighting group","description":"This plugin provides cursor motion by syntax highlighting groups in normal\r\nand visual mode:\r\n\r\n- type  \\<right>  (actually <Leader><right>) to move the cursor forward to \r\n  the end of the syntax group where cursor is located.\r\n\r\n- type  \\<left>  (actually <Leader><right>) to move the cursor forward to \r\n  the beginning of the syntax group where cursor is located.\r\n\r\nFor example, when inside a string, pressing  \\<right>  moves to the end of \r\nthe string.  When inside a comment, pressing  \\<left>  moves to the \r\nbeginning of the comment.  You can extrapolate this behavior to any kind\r\nof syntax group.\r\n\r\nRepeating the motion multiple times will move to the next syntax\r\nhighlighting group (forward or backward). A repeat count number can also be\r\ngiven before typing  \\<left>  or  \\<right>.  For example, typing  3\\<left>\r\nmoves the cursor to the left by 3 syntax elements.\r\n\r\nStrictly speaking, motion actually moves to the start or end of the text\r\nwhich has the same \"color\" (rather than same \"syntax group\") as the color\r\nof the text where cursor is originally located. So if your color scheme\r\ndefines the same colors for multiple syntax groups, motion may actually span\r\nmultiple consecutive syntax groups if they have the same colors.  Motion is\r\nbased on syntax highlighting colors rather than syntax highlighting groups\r\nto make behavior more intuitive (what you see is what you get) since users\r\nsee colors on the screen but may not be aware of different syntax highlight\r\ngroups.\r\n\r\nPlugin also provides a way to select the text visually around the position\r\nof the cursor with the same syntax group as where cursor is located:\r\n\r\n- type  va<right>  to visually select the text with the same syntax as \r\n  where cursor is located, and move the cursor to the end of the selected\r\n  text.\r\n\r\n- type  va<left>  to visually select the text with the same syntax as \r\n  where cursor is located, and move the cursor to the beginning of the \r\n  selected text.\r\n\r\nSyntax highlighting must be enabled for the plugin to work.\r\n\r\nLicense: The VIM LICENSE applies to SyntaxMotion.vim (see \":help copyright\"\r\nexcept use \"SyntaxMotion.vim\" instead of \"Vim\").\r\n\r\nToDo:\r\n- write a proper help page\r\n- provide mapping in operator pending mode\r\n","4":"This plugin provides cursor motion by syntax highlighting groups in normal\r\nand visual mode:\r\n\r\n- type  \\<right>  (actually <Leader><right>) to move the cursor forward to \r\n  the end of the syntax group where cursor is located.\r\n\r\n- type  \\<left>  (actually <Leader><right>) to move the cursor forward to \r\n  the beginning of the syntax group where cursor is located.\r\n\r\nFor example, when inside a string, pressing  \\<right>  moves to the end of \r\nthe string.  When inside a comment, pressing  \\<left>  moves to the \r\nbeginning of the comment.  You can extrapolate this behavior to any kind\r\nof syntax group.\r\n\r\nRepeating the motion multiple times will move to the next syntax\r\nhighlighting group (forward or backward). A repeat count number can also be\r\ngiven before typing  \\<left>  or  \\<right>.  For example, typing  3\\<left>\r\nmoves the cursor to the left by 3 syntax elements.\r\n\r\nStrictly speaking, motion actually moves to the start or end of the text\r\nwhich has the same \"color\" (rather than same \"syntax group\") as the color\r\nof the text where cursor is originally located. So if your color scheme\r\ndefines the same colors for multiple syntax groups, motion may actually span\r\nmultiple consecutive syntax groups if they have the same colors.  Motion is\r\nbased on syntax highlighting colors rather than syntax highlighting groups\r\nto make behavior more intuitive (what you see is what you get) since users\r\nsee colors on the screen but may not be aware of different syntax highlight\r\ngroups.\r\n\r\nPlugin also provides a way to select the text visually around the position\r\nof the cursor with the same syntax group as where cursor is located:\r\n\r\n- type  va<right>  to visually select the text with the same syntax as \r\n  where cursor is located, and move the cursor to the end of the selected\r\n  text.\r\n\r\n- type  va<left>  to visually select the text with the same syntax as \r\n  where cursor is located, and move the cursor to the beginning of the \r\n  selected text.\r\n\r\nSyntax highlighting must be enabled for the plugin to work.\r\n\r\nLicense: The VIM LICENSE applies to SyntaxMotion.vim (see \":help copyright\"\r\nexcept use \"SyntaxMotion.vim\" instead of \"Vim\").\r\n\r\nToDo:\r\n- write a proper help page\r\n- provide mapping in operator pending mode\r\n","install_details":"Drop SyntaxMotion.vim into your favorite plugin directory: ~\/.vim\/plugin\/ on Unix, $HOME\/vimfiles\/plugin or $VIM\/vimfiles\/plugin on Windows).\r\n","5":"Drop SyntaxMotion.vim into your favorite plugin directory: ~\/.vim\/plugin\/ on Unix, $HOME\/vimfiles\/plugin or $VIM\/vimfiles\/plugin on Windows).\r\n","first_name":"Dominique","6":"Dominique","last_name":"Pell\u00c3\u00a9","7":"Pell\u00c3\u00a9","releases":[{"0":"2965","vim_version":"7.0","1":"7.0","script_version":"0.5","2":"0.5","version_comment":"Bug fix in Visual Selection when cursor was at beginning or end of syntax block","3":"Bug fix in Visual Selection when cursor was at beginning or end of syntax block","package":"SyntaxMotion.vim","4":"SyntaxMotion.vim","src_id":"12358","5":"12358","creation_date":"1265954750","6":"1265954750"},{"0":"2965","vim_version":"7.0","1":"7.0","script_version":"0.4","2":"0.4","version_comment":"Added mappings to perform visual selection of text which has same syntax as where cursor is located. Use  va<left>  and   va<right>","3":"Added mappings to perform visual selection of text which has same syntax as where cursor is located. Use  va<left>  and   va<right>","package":"SyntaxMotion.vim","4":"SyntaxMotion.vim","src_id":"12357","5":"12357","creation_date":"1265921049","6":"1265921049"},{"0":"2965","vim_version":"7.0","1":"7.0","script_version":"0.3","2":"0.3","version_comment":"now work with repeat count  (example: 3\\<right>)","3":"now work with repeat count  (example: 3\\<right>)","package":"SyntaxMotion.vim","4":"SyntaxMotion.vim","src_id":"12331","5":"12331","creation_date":"1265552439","6":"1265552439"},{"0":"2965","vim_version":"7.0","1":"7.0","script_version":"0.2","2":"0.2","version_comment":"now also works in visual mode","3":"now also works in visual mode","package":"SyntaxMotion.vim","4":"SyntaxMotion.vim","src_id":"12328","5":"12328","creation_date":"1265544367","6":"1265544367"},{"0":"2965","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"SyntaxMotion.vim","4":"SyntaxMotion.vim","src_id":"12327","5":"12327","creation_date":"1265535823","6":"1265535823"}]},"2964":{"script_id":"2964","0":"2964","script_name":"neutron.vim","1":"neutron.vim","script_type":"color scheme","2":"color scheme","summary":"Light background colorscheme","3":"Light background colorscheme","description":"This colorscheme is placed in the Public Domain\r\nAuthor: Joseph Wecker\r\n\r\nPut this together for those days when I need a light background in gvim instead\r\nof a dark (in which case I usually use zenburn).  This syntax has the following\r\nattributes:\r\n\r\n- Soft and easy on the eyes, but enough contrast\r\n- No italics or bold text because I sometimes get rendering issues\r\n- Nice colors - evenly balanced\r\n- Colors for all main syntax items! (pet-peeve- otherwise great colorschemes\r\n  that combine syntactic elements into the same color)\r\n\r\nI used proton.vim as a starting template (hence the name)- but I don't think\r\nthere's much of proton left in neutron.\r\n\r\nDevelopment at http:\/\/github.com\/josephwecker\/neutron.vim\r\n","4":"This colorscheme is placed in the Public Domain\r\nAuthor: Joseph Wecker\r\n\r\nPut this together for those days when I need a light background in gvim instead\r\nof a dark (in which case I usually use zenburn).  This syntax has the following\r\nattributes:\r\n\r\n- Soft and easy on the eyes, but enough contrast\r\n- No italics or bold text because I sometimes get rendering issues\r\n- Nice colors - evenly balanced\r\n- Colors for all main syntax items! (pet-peeve- otherwise great colorschemes\r\n  that combine syntactic elements into the same color)\r\n\r\nI used proton.vim as a starting template (hence the name)- but I don't think\r\nthere's much of proton left in neutron.\r\n\r\nDevelopment at http:\/\/github.com\/josephwecker\/neutron.vim\r\n","install_details":"Place in your ~\/.vim\/colors directory","5":"Place in your ~\/.vim\/colors directory","first_name":"joseph","6":"joseph","last_name":"wecker","7":"wecker","releases":[{"0":"2964","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"neutron.vim","4":"neutron.vim","src_id":"12326","5":"12326","creation_date":"1265522841","6":"1265522841"}]},"2963":{"script_id":"2963","0":"2963","script_name":"line number yank","1":"line number yank","script_type":"utility","2":"utility","summary":"yank lines with line number","3":"yank lines with line number","description":"The script is used for yank lines with their line number.\r\nYou can yank lines for specific range with their line number by key map \\ny\r\nFor example, the text from line 9 to 12 is like the follow:\r\n\r\nline9\r\nline10\r\nline11\r\nline12\r\n\r\nif you specified text from line 9 to line 12 under visual mode, press `\\ny'. Then if you press `p', it would paste:\r\n\r\n  9  line9\r\n 10  line10\r\n 11  line11\r\n 12  line12\r\n\r\nIf the line number is larger than 999, the format would not that tidy.","4":"The script is used for yank lines with their line number.\r\nYou can yank lines for specific range with their line number by key map \\ny\r\nFor example, the text from line 9 to 12 is like the follow:\r\n\r\nline9\r\nline10\r\nline11\r\nline12\r\n\r\nif you specified text from line 9 to line 12 under visual mode, press `\\ny'. Then if you press `p', it would paste:\r\n\r\n  9  line9\r\n 10  line10\r\n 11  line11\r\n 12  line12\r\n\r\nIf the line number is larger than 999, the format would not that tidy.","install_details":"Just simply copy lnyank.vim into you plugin directory($HOME\/.vim\/plugin for unix)","5":"Just simply copy lnyank.vim into you plugin directory($HOME\/.vim\/plugin for unix)","first_name":"Zhang","6":"Zhang","last_name":"Huicong","7":"Huicong","releases":[{"0":"2963","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"lnyank.vim","4":"lnyank.vim","src_id":"12320","5":"12320","creation_date":"1265443837","6":"1265443837"}]},"2962":{"script_id":"2962","0":"2962","script_name":"liftweb.vim","1":"liftweb.vim","script_type":"utility","2":"utility","summary":"A plugin for vim to ease navigation for projects that use the Lift framework.","3":"A plugin for vim to ease navigation for projects that use the Lift framework.","description":"A plugin for vim to ease navigation for projects that use the Lift Scala web \r\nframework. Heavily inspired by the awesome that is Tim Pope's rails.vim (at \r\nhttp:\/\/rails.vim.tpope.net\/) . \r\n\r\nCurrently provides a few commands: \r\n\r\n* :Lmodel, Lsnippet, Lactor, Lcomet, Llib -- all take a class name and take you to \r\n  the appropriate associated file \r\n* :Lview -- takes a class name and takes you to the appropriate view file \r\n* :Lspec or :Ltest -- when called from a class (e.g., GroupSnip), takes you to \r\n  the associated test file (GroupSnipTest) \r\n* :Lclass -- the opposite of Lspec, takes you to the class for the current test \r\n* :Lboot -- takes you directly to Boot.scala \r\n* :Lcss, Ljavascript, Lsass -- takes a filename and takes you to the appropriate file \r\n\r\nAll commands are properly autocompleted.\r\n\r\nThe github repository for this lives at http:\/\/github.com\/Shadowfiend\/liftweb-vim\/ ; \r\nplease file bugs at http:\/\/github.com\/Shadowfiend\/liftweb-vim\/issues .","4":"A plugin for vim to ease navigation for projects that use the Lift Scala web \r\nframework. Heavily inspired by the awesome that is Tim Pope's rails.vim (at \r\nhttp:\/\/rails.vim.tpope.net\/) . \r\n\r\nCurrently provides a few commands: \r\n\r\n* :Lmodel, Lsnippet, Lactor, Lcomet, Llib -- all take a class name and take you to \r\n  the appropriate associated file \r\n* :Lview -- takes a class name and takes you to the appropriate view file \r\n* :Lspec or :Ltest -- when called from a class (e.g., GroupSnip), takes you to \r\n  the associated test file (GroupSnipTest) \r\n* :Lclass -- the opposite of Lspec, takes you to the class for the current test \r\n* :Lboot -- takes you directly to Boot.scala \r\n* :Lcss, Ljavascript, Lsass -- takes a filename and takes you to the appropriate file \r\n\r\nAll commands are properly autocompleted.\r\n\r\nThe github repository for this lives at http:\/\/github.com\/Shadowfiend\/liftweb-vim\/ ; \r\nplease file bugs at http:\/\/github.com\/Shadowfiend\/liftweb-vim\/issues .","install_details":"Just copy the files to the appropriate locations in ~\/.vim and open a scala file in your Lift project and you're ready to rock. \r\n\r\nAlternatively, use Tim Pope's pathogen.vim (http:\/\/www.vim.org\/scripts\/script.php?script_id=2332 ) and put this plugin's files in ~\/.vim\/bundle\/liftweb-vim\/ (or extract the tarball directly there).","5":"Just copy the files to the appropriate locations in ~\/.vim and open a scala file in your Lift project and you're ready to rock. \r\n\r\nAlternatively, use Tim Pope's pathogen.vim (http:\/\/www.vim.org\/scripts\/script.php?script_id=2332 ) and put this plugin's files in ~\/.vim\/bundle\/liftweb-vim\/ (or extract the tarball directly there).","first_name":"Antonio","6":"Antonio","last_name":"Salazar Cardozo","7":"Salazar Cardozo","releases":[{"0":"2962","vim_version":"7.0","1":"7.0","script_version":"1.2.1","2":"1.2.1","version_comment":"Added Lboot, Ljavascript, Lcss, and Lsass commands. Also fixed Llib completion and added Llib to list of supported commands.\r\n\r\nFixed archive to be a proper tar.gz archive.","3":"Added Lboot, Ljavascript, Lcss, and Lsass commands. Also fixed Llib completion and added Llib to list of supported commands.\r\n\r\nFixed archive to be a proper tar.gz archive.","package":"liftweb-vim.tar.gz","4":"liftweb-vim.tar.gz","src_id":"21171","5":"21171","creation_date":"1386443913","6":"1386443913"},{"0":"2962","vim_version":"7.0","1":"7.0","script_version":"1.2","2":"1.2","version_comment":"Added Lboot, Ljavascript, Lcss, and Lsass commands. Also fixed Llib completion and added Llib to list of supported commands.","3":"Added Lboot, Ljavascript, Lcss, and Lsass commands. Also fixed Llib completion and added Llib to list of supported commands.","package":"liftweb-vim.tar.gz","4":"liftweb-vim.tar.gz","src_id":"14551","5":"14551","creation_date":"1292621291","6":"1292621291"},{"0":"2962","vim_version":"7.0","1":"7.0","script_version":"1.1","2":"1.1","version_comment":"Added correct vim script id for GetLatestVimScripts configuration.","3":"Added correct vim script id for GetLatestVimScripts configuration.","package":"liftweb-vim.tar.gz","4":"liftweb-vim.tar.gz","src_id":"12319","5":"12319","creation_date":"1265435447","6":"1265435447"},{"0":"2962","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"liftweb-vim.tar.gz","4":"liftweb-vim.tar.gz","src_id":"12315","5":"12315","creation_date":"1265435051","6":"1265435051"}]},"2961":{"script_id":"2961","0":"2961","script_name":"groovyindent","1":"groovyindent","script_type":"indent","2":"indent","summary":"groovy indent script","3":"groovy indent script","description":"groovy indent script","4":"groovy indent script","install_details":"just place this script into VIM\/indent\/","5":"just place this script into VIM\/indent\/","first_name":"anderson","6":"anderson","last_name":"zhang","7":"zhang","releases":[{"0":"2961","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"groovy.vim","4":"groovy.vim","src_id":"12312","5":"12312","creation_date":"1265389758","6":"1265389758"}]},"2960":{"script_id":"2960","0":"2960","script_name":"bisect","1":"bisect","script_type":"utility","2":"utility","summary":"Navigation via bisection","3":"Navigation via bisection","description":"This plugin will allow you to reach a desired location on the visible screen by\r\nperforming a sequence of bisections to the left, right, up, and down.  By default,\r\nthese are performed using the <C-h>, <C-l>, <C-j>, and <C-k> commands, respectively.\r\n<C-i> cancels a bisect.\r\n\r\nHorizontal and vertical commands can be interleaved.\r\n\r\nWorks in normal and all visual modes.\r\n\r\nMore information available here: http:\/\/github.com\/mikezackles\/Bisect","4":"This plugin will allow you to reach a desired location on the visible screen by\r\nperforming a sequence of bisections to the left, right, up, and down.  By default,\r\nthese are performed using the <C-h>, <C-l>, <C-j>, and <C-k> commands, respectively.\r\n<C-i> cancels a bisect.\r\n\r\nHorizontal and vertical commands can be interleaved.\r\n\r\nWorks in normal and all visual modes.\r\n\r\nMore information available here: http:\/\/github.com\/mikezackles\/Bisect","install_details":"Use the git repo, or open the vimball and run\r\n:so %","5":"Use the git repo, or open the vimball and run\r\n:so %","first_name":"Zachary","6":"Zachary","last_name":"Michaels","7":"Michaels","releases":[{"0":"2960","vim_version":"7.0","1":"7.0","script_version":"2.0","2":"2.0","version_comment":"Full support for visual mark mode.  User configuration variables.  No register usage.  Paging functions.  Nonstrict bisection.","3":"Full support for visual mark mode.  User configuration variables.  No register usage.  Paging functions.  Nonstrict bisection.","package":"bisect.vmb","4":"bisect.vmb","src_id":"16746","5":"16746","creation_date":"1319652847","6":"1319652847"},{"0":"2960","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Fixed inconsistencies between bisecting left\/right and up\/down.  Attempting to move past a boundary now automatically starts a new bisection.","3":"Fixed inconsistencies between bisecting left\/right and up\/down.  Attempting to move past a boundary now automatically starts a new bisection.","package":"bisect.vmb","4":"bisect.vmb","src_id":"16717","5":"16717","creation_date":"1319225900","6":"1319225900"},{"0":"2960","vim_version":"7.0","1":"7.0","script_version":"0.0.1","2":"0.0.1","version_comment":"Vimball for easier install.  Extra doc.","3":"Vimball for easier install.  Extra doc.","package":"bisect.vba.gz","4":"bisect.vba.gz","src_id":"12305","5":"12305","creation_date":"1265298951","6":"1265298951"},{"0":"2960","vim_version":"7.0","1":"7.0","script_version":"0.0.1","2":"0.0.1","version_comment":"Initial upload","3":"Initial upload","package":"bisect.tgz","4":"bisect.tgz","src_id":"12298","5":"12298","creation_date":"1265237362","6":"1265237362"}]},"2959":{"script_id":"2959","0":"2959","script_name":"emoticon.vim","1":"emoticon.vim","script_type":"game","2":"game","summary":"\n    emoticon omni completion\n","3":"\n    emoticon omni completion\n","description":"\n    emoticon omni completion\n","4":"\n    emoticon omni completion\n","install_details":"    \n    just\n","5":"    \n    just\n","first_name":"Yo-An","6":"Yo-An","last_name":"Lin","7":"Lin","releases":[{"0":"2959","vim_version":"7.2","1":"7.2","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"emoticon.vim","4":"emoticon.vim","src_id":"12291","5":"12291","creation_date":"1265222105","6":"1265222105"}]},"2958":{"script_id":"2958","0":"2958","script_name":"emoticon.vim","1":"emoticon.vim","script_type":"game","2":"game","summary":"\n    emoticon omni completion\n","3":"\n    emoticon omni completion\n","description":"\n    emoticon omni completion\n","4":"\n    emoticon omni completion\n","install_details":"    \n    just\n","5":"    \n    just\n","first_name":"Yo-An","6":"Yo-An","last_name":"Lin","7":"Lin","releases":[{"0":"2958","vim_version":"7.2","1":"7.2","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"emoticon.vim","4":"emoticon.vim","src_id":"12290","5":"12290","creation_date":"1265221541","6":"1265221541"}]},"2957":{"script_id":"2957","0":"2957","script_name":"load_template","1":"load_template","script_type":"utility","2":"utility","summary":"Loading templates as html,makefile,class ... and you can make template yourself!","3":"Loading templates as html,makefile,class ... and you can make template yourself!","description":"The plugin mainly provides the functionality that loading templates such as class,html,makefile and so on.The plugin also can load templates with script to take the replace of the filename or classname.(As default,the plugin has already included templates as main,singleton class,html,xml,makefile.)\r\nFor any question,welcome to my blog http:\/\/www.vimer.cn,\r\nand welcome to email me:zny2008@gmail.com \/ dantezhu@vip.qq.com\r\nThe plugin's homepage is :\r\nhttp:\/\/www.vimer.cn\/2010\/02\/vimer-cn%e5%8e%9f%e5%88%9bvimgvim%e6%8f%92%e4%bb%b6load_template%e6%ad%a3%e5%bc%8f%e5%8f%91%e5%b8%83.html\r\nUse guide:\r\n\t1)Download load_template.vim,and put it into the plugin directory.\r\n\r\n\t2)Assign the directory where to load templates in your vimrc file.\r\n\tFor example\r\n\tlet g:template_path = 'C:\\template\\\\'\r\n\tWarning:Don't forget about the last '\\\\'.\r\n\r\n\t3)New\/Open a test.cpp,execute\r\n\t:LoadTemplate\r\n\tIt will show the template list like this:\r\n\tTemplate filelist:\r\n\t0\t\t:\t\tcpp\/main.cpp\r\n\t1\t\t:\t\tcpp\/singleton.h\r\n\tplease select:\r\n\r\n\t4)There are also options available that allow you to make your own templates(you can write vim script in it.) \r\n\tJust try it yourself.\r\n\r\n=================================================\r\n该插件主要实现了自动载入各种模板的功能（如类模板，html模板，makefile模板等等），并且支持动态模版的功能，即能够通过脚本动态的实现文件名，类名的替换。（默认已经提供了简单main函数模板、单体类模板、html标准模板、xml标准模板）\r\n欢迎来 http:\/\/www.vimer.cn   来分享你的模板文件，或者直接给我\r\n发送邮件zny2008@gmail.com\/dantezhu@vip.qq.com\r\n这个插件的主页是：\r\nhttp:\/\/www.vimer.cn\/2010\/02\/vimer-cn%e5%8e%9f%e5%88%9bvimgvim%e6%8f%92%e4%bb%b6load_template%e6%ad%a3%e5%bc%8f%e5%8f%91%e5%b8%83.html\r\n\r\n使用说明\r\n\t1）下载load_template.vim插件，并放在plugin的目录下\r\n\t2）在vimrc文件中指定你的模板目录，来指定插件读取模板的目录。\r\n\t如在下载包中已经带了一个template的目录，里面按照文件扩展名、文件类型，分别建立了目录，你可以将这个template文件夹复制到C:\\\\，那么就可以指定\r\n\tlet g:template_path = 'C:\\template\\\\'\r\n\t注意，最后的'\\\\'请务必不要忘记（在linux下也是一样要加 '\/' ）\r\n\t3）新建\/打开一个test.cpp，执行\r\n\t:LoadTemplate\r\n\t试试看，是否有类似模板列表出来啦~\r\n\tTemplate filelist:\r\n\t0\t\t:\t\tcpp\/main.cpp\r\n\t1\t\t:\t\tcpp\/singleton.h\r\n\tplease select:\r\n\t4）你甚至可以自己制作模板文件~~只需要参考已经存在的模板文件就行啦~~支持vim脚本的哦\r\n","4":"The plugin mainly provides the functionality that loading templates such as class,html,makefile and so on.The plugin also can load templates with script to take the replace of the filename or classname.(As default,the plugin has already included templates as main,singleton class,html,xml,makefile.)\r\nFor any question,welcome to my blog http:\/\/www.vimer.cn,\r\nand welcome to email me:zny2008@gmail.com \/ dantezhu@vip.qq.com\r\nThe plugin's homepage is :\r\nhttp:\/\/www.vimer.cn\/2010\/02\/vimer-cn%e5%8e%9f%e5%88%9bvimgvim%e6%8f%92%e4%bb%b6load_template%e6%ad%a3%e5%bc%8f%e5%8f%91%e5%b8%83.html\r\nUse guide:\r\n\t1)Download load_template.vim,and put it into the plugin directory.\r\n\r\n\t2)Assign the directory where to load templates in your vimrc file.\r\n\tFor example\r\n\tlet g:template_path = 'C:\\template\\\\'\r\n\tWarning:Don't forget about the last '\\\\'.\r\n\r\n\t3)New\/Open a test.cpp,execute\r\n\t:LoadTemplate\r\n\tIt will show the template list like this:\r\n\tTemplate filelist:\r\n\t0\t\t:\t\tcpp\/main.cpp\r\n\t1\t\t:\t\tcpp\/singleton.h\r\n\tplease select:\r\n\r\n\t4)There are also options available that allow you to make your own templates(you can write vim script in it.) \r\n\tJust try it yourself.\r\n\r\n=================================================\r\n该插件主要实现了自动载入各种模板的功能（如类模板，html模板，makefile模板等等），并且支持动态模版的功能，即能够通过脚本动态的实现文件名，类名的替换。（默认已经提供了简单main函数模板、单体类模板、html标准模板、xml标准模板）\r\n欢迎来 http:\/\/www.vimer.cn   来分享你的模板文件，或者直接给我\r\n发送邮件zny2008@gmail.com\/dantezhu@vip.qq.com\r\n这个插件的主页是：\r\nhttp:\/\/www.vimer.cn\/2010\/02\/vimer-cn%e5%8e%9f%e5%88%9bvimgvim%e6%8f%92%e4%bb%b6load_template%e6%ad%a3%e5%bc%8f%e5%8f%91%e5%b8%83.html\r\n\r\n使用说明\r\n\t1）下载load_template.vim插件，并放在plugin的目录下\r\n\t2）在vimrc文件中指定你的模板目录，来指定插件读取模板的目录。\r\n\t如在下载包中已经带了一个template的目录，里面按照文件扩展名、文件类型，分别建立了目录，你可以将这个template文件夹复制到C:\\\\，那么就可以指定\r\n\tlet g:template_path = 'C:\\template\\\\'\r\n\t注意，最后的'\\\\'请务必不要忘记（在linux下也是一样要加 '\/' ）\r\n\t3）新建\/打开一个test.cpp，执行\r\n\t:LoadTemplate\r\n\t试试看，是否有类似模板列表出来啦~\r\n\tTemplate filelist:\r\n\t0\t\t:\t\tcpp\/main.cpp\r\n\t1\t\t:\t\tcpp\/singleton.h\r\n\tplease select:\r\n\t4）你甚至可以自己制作模板文件~~只需要参考已经存在的模板文件就行啦~~支持vim脚本的哦\r\n","install_details":"","5":"","first_name":"zhu","6":"zhu","last_name":"nianyang","7":"nianyang","releases":[{"0":"2957","vim_version":"7.0","1":"7.0","script_version":"1.1.0","2":"1.1.0","version_comment":"new feature:\r\nyou can control the cursor's last place. you can see the main.cpp template to know more.\r\n\r\n新特性：\r\n现在可以控制鼠标的最后停留位置啦，你可以看一下 main.cpp这个模板来了解更多。","3":"new feature:\r\nyou can control the cursor's last place. you can see the main.cpp template to know more.\r\n\r\n新特性：\r\n现在可以控制鼠标的最后停留位置啦，你可以看一下 main.cpp这个模板来了解更多。","package":"load_template.zip","4":"load_template.zip","src_id":"12344","5":"12344","creation_date":"1265718516","6":"1265718516"},{"0":"2957","vim_version":"7.0","1":"7.0","script_version":"1.0.3","2":"1.0.3","version_comment":"if is windows\r\nlet the default template directory is $VIM.'\\vimfiles\\template\\'\r\nelse if linux or else\r\nlet the default template directory is $HOME.'\/.vim\/template\/'","3":"if is windows\r\nlet the default template directory is $VIM.'\\vimfiles\\template\\'\r\nelse if linux or else\r\nlet the default template directory is $HOME.'\/.vim\/template\/'","package":"load_template.zip","4":"load_template.zip","src_id":"12303","5":"12303","creation_date":"1265269275","6":"1265269275"},{"0":"2957","vim_version":"7.0","1":"7.0","script_version":"1.0.2","2":"1.0.2","version_comment":"fix the bug:\r\nE121: 未定义的变量: g:vimrc_splitstr\r\n\r\nE15: 无效的表达式: \u00e2\u0080\u0098~\u00e2\u0080\u0099.g:vimrc_splitstr.\u00e2\u0080\u0099template_source.vim\u00e2\u0080\u0099\r\n\r\n","3":"fix the bug:\r\nE121: 未定义的变量: g:vimrc_splitstr\r\n\r\nE15: 无效的表达式: \u00e2\u0080\u0098~\u00e2\u0080\u0099.g:vimrc_splitstr.\u00e2\u0080\u0099template_source.vim\u00e2\u0080\u0099\r\n\r\n","package":"load_template.zip","4":"load_template.zip","src_id":"12302","5":"12302","creation_date":"1265255620","6":"1265255620"},{"0":"2957","vim_version":"7.0","1":"7.0","script_version":"1.0.1","2":"1.0.1","version_comment":"the doc file miss something...","3":"the doc file miss something...","package":"load_template.zip","4":"load_template.zip","src_id":"12289","5":"12289","creation_date":"1265208775","6":"1265208775"},{"0":"2957","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"load_template.zip","4":"load_template.zip","src_id":"12288","5":"12288","creation_date":"1265208017","6":"1265208017"}]},"2956":{"script_id":"2956","0":"2956","script_name":"csp.vim","1":"csp.vim","script_type":"syntax","2":"syntax","summary":"syntax file for CSP","3":"syntax file for CSP","description":"syntax file for CSP (Communication Sequential Processes, using FDR input syntax). New version because of new Web home page of maintainer.","4":"syntax file for CSP (Communication Sequential Processes, using FDR input syntax). New version because of new Web home page of maintainer.","install_details":"See Web page: http:\/\/homepages.hs-bremen.de\/~jbredereke\/en\/software\/vim\/","5":"See Web page: http:\/\/homepages.hs-bremen.de\/~jbredereke\/en\/software\/vim\/","first_name":"Jan","6":"Jan","last_name":"Bredereke","7":"Bredereke","releases":[{"0":"2956","vim_version":"6.0","1":"6.0","script_version":"0.6.1","2":"0.6.1","version_comment":"Initial upload","3":"Initial upload","package":"csp.vim","4":"csp.vim","src_id":"12287","5":"12287","creation_date":"1265194878","6":"1265194878"}]},"2955":{"script_id":"2955","0":"2955","script_name":"hex.vim","1":"hex.vim","script_type":"ftplugin","2":"ftplugin","summary":"ftplugin for Intel Hex files","3":"ftplugin for Intel Hex files","description":"This is a filetype plugin for Intel Hex Files.\r\nShows the address and decimal data at the cursor position.\r\n:HexGotoAddress 0x...... : Jump to address\r\n\r\nActually it is only for 'Extended linear address record ' (type 04)\r\nIf you need other types too, send me your hex-file","4":"This is a filetype plugin for Intel Hex Files.\r\nShows the address and decimal data at the cursor position.\r\n:HexGotoAddress 0x...... : Jump to address\r\n\r\nActually it is only for 'Extended linear address record ' (type 04)\r\nIf you need other types too, send me your hex-file","install_details":"simply put it in your ftplugin directory","5":"simply put it in your ftplugin directory","first_name":"Stefan","6":"Stefan","last_name":"Liebl","7":"Liebl","releases":[{"0":"2955","vim_version":"7.0","1":"7.0","script_version":"1","2":"1","version_comment":"Initial upload","3":"Initial upload","package":"hex.vim","4":"hex.vim","src_id":"12273","5":"12273","creation_date":"1265123831","6":"1265123831"}]},"2954":{"script_id":"2954","0":"2954","script_name":"hypergit.vim","1":"hypergit.vim","script_type":"utility","2":"utility","summary":"an awesome git plugin for vim.","3":"an awesome git plugin for vim.","description":"* hypergit plugin provides a tree menu just like NERD_Tree, you can execute\r\ngit command very easily. you can expand, collpase, execute on each node.\r\n\r\n* it also provides a bunch of commands and key mapping, \r\n\r\n* support editing of `git rebase -i [branch]`\r\n\r\n* status buffer to edit\/commit\/delete\/add files.\r\n\r\nPlease see:  http:\/\/github.com\/c9s\/hypergit.vim","4":"* hypergit plugin provides a tree menu just like NERD_Tree, you can execute\r\ngit command very easily. you can expand, collpase, execute on each node.\r\n\r\n* it also provides a bunch of commands and key mapping, \r\n\r\n* support editing of `git rebase -i [branch]`\r\n\r\n* status buffer to edit\/commit\/delete\/add files.\r\n\r\nPlease see:  http:\/\/github.com\/c9s\/hypergit.vim","install_details":"\r\njust run make:\r\n\r\n   $ make install\r\n\r\nhttp:\/\/github.com\/c9s\/hypergit.vim","5":"\r\njust run make:\r\n\r\n   $ make install\r\n\r\nhttp:\/\/github.com\/c9s\/hypergit.vim","first_name":"Yo-An","6":"Yo-An","last_name":"Lin","7":"Lin","releases":[{"0":"2954","vim_version":"7.0","1":"7.0","script_version":"0.7","2":"0.7","version_comment":"repack.","3":"repack.","package":"hypergit.vim-0.7.tar.gz","4":"hypergit.vim-0.7.tar.gz","src_id":"12689","5":"12689","creation_date":"1269364853","6":"1269364853"},{"0":"2954","vim_version":"7.0","1":"7.0","script_version":"0.7","2":"0.7","version_comment":"repack.","3":"repack.","package":"hypergit.vim-0.7.tar.gz","4":"hypergit.vim-0.7.tar.gz","src_id":"12687","5":"12687","creation_date":"1269363338","6":"1269363338"}]},"2953":{"script_id":"2953","0":"2953","script_name":"Wavefront's obj","1":"Wavefront's obj","script_type":"syntax","2":"syntax","summary":"Syntax for wavefront's obj file format","3":"Syntax for wavefront's obj file format","description":"Note : this syntax file is included in Vim 7.3\r\n\r\nwavefront's obj is a file format to store 3D meshes, and is stored as an ASCII file.","4":"Note : this syntax file is included in Vim 7.3\r\n\r\nwavefront's obj is a file format to store 3D meshes, and is stored as an ASCII file.","install_details":"Open obj.vba in vim then type :\r\n:so %","5":"Open obj.vba in vim then type :\r\n:so %","first_name":"Vincent","6":"Vincent","last_name":"B","7":"B","releases":[{"0":"2953","vim_version":"7.2","1":"7.2","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"obj.vba","4":"obj.vba","src_id":"12253","5":"12253","creation_date":"1264957946","6":"1264957946"}]},"2952":{"script_id":"2952","0":"2952","script_name":"c standard functions highlight","1":"c standard functions highlight","script_type":"syntax","2":"syntax","summary":"highlight most functions in C89\/C99\/unistd.h","3":"highlight most functions in C89\/C99\/unistd.h","description":"general c highlight doesn't support standard function symbols, so mixed with the symbols defined ourselves(wrong? oh, i'm a silly pig).\r\n\r\nlet's separate them from now on.\r\n\r\nsee in the snapshot including in the tarball. they're black, u'll know that. \r\n\r\nmay u have a good day.","4":"general c highlight doesn't support standard function symbols, so mixed with the symbols defined ourselves(wrong? oh, i'm a silly pig).\r\n\r\nlet's separate them from now on.\r\n\r\nsee in the snapshot including in the tarball. they're black, u'll know that. \r\n\r\nmay u have a good day.","install_details":"so easy:\r\n\r\nmove this c.vim to ~\/.vim\/syntax if there's no same name file,\r\nor copy the contents to the original c.vim, both works.","5":"so easy:\r\n\r\nmove this c.vim to ~\/.vim\/syntax if there's no same name file,\r\nor copy the contents to the original c.vim, both works.","first_name":"Yang","6":"Yang","last_name":"Zhang","7":"Zhang","releases":[{"0":"2952","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"no comment","3":"no comment","package":"c_std_func_highlight.tgz","4":"c_std_func_highlight.tgz","src_id":"12251","5":"12251","creation_date":"1264953831","6":"1264953831"}]},"2951":{"script_id":"2951","0":"2951","script_name":"SaneCL","1":"SaneCL","script_type":"indent","2":"indent","summary":"Quickly indents Common Lisp code and is 100% VimScript","3":"Quickly indents Common Lisp code and is 100% VimScript","description":"Bug reports or comments welcome! Email: oconnore@gmail.com\r\n----------------\r\n\r\nParsing is done using a per character tokenizer. Two stacks are used to simulate a recursive parse.\r\n\r\nMappings:\r\n<Tab> indents lines (or ranges in visual mode)\r\n<C-\\> indents the toplevel form. Or whatever is at 150[(.\r\n\r\nTo indent an entire file, do 1GVG<Tab>. This may take a while for a large file.\r\n\r\nCommands:\r\n:CLLoadLispwords refreshes the lisp word file\r\n:CLIndentForm indents the toplevel form\r\n:CLIndentRange indents a range\r\n:CLIndentLine indents a line\r\n:CLSetWord <word> <number> sets a lispword\r\n\r\nCustomizable variables:\r\nString :: g:CL_lispwords_file defaults to ~\/lispwords.\r\nBoolean :: g:CL_aggressive_literals defaults to 1\r\nBoolean :: g:CL_retab_on_open defaults to 1\r\nInteger :: g:CL_auto_zero_limit defaults to 25\r\nList <String> :: g:CL_loop_keywords lists all known loop keywords\r\nList <String> :: g:CL_flets lists forms to be handled similar to flet\r\nList < List < String, Integer > > :: g:CL_auto_prefixes lists all regexp base lisp numbers.\r\n\r\nAdd <<let g:VARIABLE = VALUE >> to your ~\/.vimrc to change this. For Boolean variables, 1 is true and 0 is false.\r\n\r\nLisp words are stored 1 per line as such:\r\n<symbol> <lisp #>\r\n\r\nAggressive literals means that forms such as (:hello world), ('got milk) and (&optional var1 var2) are treated as literals. The first character of the first symbol (if it is a symbol) are tested to match [&':].\r\n\r\nWhile indenting, auto prefixes iterates over each string-integer pair. If the string matches the parent (for example \"def\" matches \"defclass\", and \"^[abc].*$\" matches \"chair\"), then the associated lisp word number is used for indentation. The first match wins.\r\nI default to: [[\"with-\",1], [\"def\",2], [\"make-\",1], [\"map\",1]]\r\n\r\nAuto zero limit was added to preserve screen real estate for long lispy symbol names. If a symbol in your program looks like \"variable-that-holds-an-integer-and-is-used-for-counting\", you may appreciate this setting. Any parent string longer than the limit will be handled as a lisp number zero. By default, this is 25 characters.\r\n\r\nMy lispwords file is available at: http:\/\/paste.lisp.org\/display\/97882\r\nIt is not complete, but might be a useful starting point.\r\n\r\nThe indentation behavior was based on a description at http:\/\/evalwhen.com\/scmindent\/index.html.","4":"Bug reports or comments welcome! Email: oconnore@gmail.com\r\n----------------\r\n\r\nParsing is done using a per character tokenizer. Two stacks are used to simulate a recursive parse.\r\n\r\nMappings:\r\n<Tab> indents lines (or ranges in visual mode)\r\n<C-\\> indents the toplevel form. Or whatever is at 150[(.\r\n\r\nTo indent an entire file, do 1GVG<Tab>. This may take a while for a large file.\r\n\r\nCommands:\r\n:CLLoadLispwords refreshes the lisp word file\r\n:CLIndentForm indents the toplevel form\r\n:CLIndentRange indents a range\r\n:CLIndentLine indents a line\r\n:CLSetWord <word> <number> sets a lispword\r\n\r\nCustomizable variables:\r\nString :: g:CL_lispwords_file defaults to ~\/lispwords.\r\nBoolean :: g:CL_aggressive_literals defaults to 1\r\nBoolean :: g:CL_retab_on_open defaults to 1\r\nInteger :: g:CL_auto_zero_limit defaults to 25\r\nList <String> :: g:CL_loop_keywords lists all known loop keywords\r\nList <String> :: g:CL_flets lists forms to be handled similar to flet\r\nList < List < String, Integer > > :: g:CL_auto_prefixes lists all regexp base lisp numbers.\r\n\r\nAdd <<let g:VARIABLE = VALUE >> to your ~\/.vimrc to change this. For Boolean variables, 1 is true and 0 is false.\r\n\r\nLisp words are stored 1 per line as such:\r\n<symbol> <lisp #>\r\n\r\nAggressive literals means that forms such as (:hello world), ('got milk) and (&optional var1 var2) are treated as literals. The first character of the first symbol (if it is a symbol) are tested to match [&':].\r\n\r\nWhile indenting, auto prefixes iterates over each string-integer pair. If the string matches the parent (for example \"def\" matches \"defclass\", and \"^[abc].*$\" matches \"chair\"), then the associated lisp word number is used for indentation. The first match wins.\r\nI default to: [[\"with-\",1], [\"def\",2], [\"make-\",1], [\"map\",1]]\r\n\r\nAuto zero limit was added to preserve screen real estate for long lispy symbol names. If a symbol in your program looks like \"variable-that-holds-an-integer-and-is-used-for-counting\", you may appreciate this setting. Any parent string longer than the limit will be handled as a lisp number zero. By default, this is 25 characters.\r\n\r\nMy lispwords file is available at: http:\/\/paste.lisp.org\/display\/97882\r\nIt is not complete, but might be a useful starting point.\r\n\r\nThe indentation behavior was based on a description at http:\/\/evalwhen.com\/scmindent\/index.html.","install_details":"Save to ~\/.vim\/ftplugins\/lisp.vim, or configure a custom command in your .vimrc such as:\r\nautocommand! BufRead *.lisp source <file_location>\r\n\r\nProvide an empty lispwords file, or you will see an error on the first run.","5":"Save to ~\/.vim\/ftplugins\/lisp.vim, or configure a custom command in your .vimrc such as:\r\nautocommand! BufRead *.lisp source <file_location>\r\n\r\nProvide an empty lispwords file, or you will see an error on the first run.","first_name":"Eric","6":"Eric","last_name":"O'Connor","7":"O'Connor","releases":[{"0":"2951","vim_version":"6.0","1":"6.0","script_version":"2.0","2":"2.0","version_comment":"Minor change - break the auto prefix loop correctly.","3":"Minor change - break the auto prefix loop correctly.","package":"lisp.vim","4":"lisp.vim","src_id":"12848","5":"12848","creation_date":"1271439529","6":"1271439529"},{"0":"2951","vim_version":"6.0","1":"6.0","script_version":"1.9","2":"1.9","version_comment":"Bug fixes, and prefix based form handling.","3":"Bug fixes, and prefix based form handling.","package":"lisp.vim","4":"lisp.vim","src_id":"12845","5":"12845","creation_date":"1271430301","6":"1271430301"},{"0":"2951","vim_version":"6.0","1":"6.0","script_version":"1.8","2":"1.8","version_comment":"Proper comment handling. Added g:CL_define_keywords to handle multi-line variable lists.","3":"Proper comment handling. Added g:CL_define_keywords to handle multi-line variable lists.","package":"lisp.vim","4":"lisp.vim","src_id":"12654","5":"12654","creation_date":"1268920504","6":"1268920504"},{"0":"2951","vim_version":"6.0","1":"6.0","script_version":"1.7","2":"1.7","version_comment":"Macrolets, flets, labels.","3":"Macrolets, flets, labels.","package":"lisp.vim","4":"lisp.vim","src_id":"12324","5":"12324","creation_date":"1265489796","6":"1265489796"},{"0":"2951","vim_version":"6.0","1":"6.0","script_version":"1.6","2":"1.6","version_comment":"Loop form handling.","3":"Loop form handling.","package":"lisp.vim","4":"lisp.vim","src_id":"12322","5":"12322","creation_date":"1265488002","6":"1265488002"},{"0":"2951","vim_version":"6.0","1":"6.0","script_version":"1.5","2":"1.5","version_comment":"+ Simple vector's gave parentheses error because they weren't handled within the sharp-sign state\r\n+ Screen stability bugs\r\n+ Improved plug-in hygiene (b:undo_ftplugin)\r\n+ Added an option [g:CL_aggressive_literals] to detect all forms beginning in [&:'].* as literals. Default: true\r\n+ Default re-tabs a new lisp file. Turn off with g:CL_retab_on_open = 0\r\n+ Changed the g:lispwords_file variable to g:CL_lispwords_file to avoid confusion.\r\n+ Removed unused code","3":"+ Simple vector's gave parentheses error because they weren't handled within the sharp-sign state\r\n+ Screen stability bugs\r\n+ Improved plug-in hygiene (b:undo_ftplugin)\r\n+ Added an option [g:CL_aggressive_literals] to detect all forms beginning in [&:'].* as literals. Default: true\r\n+ Default re-tabs a new lisp file. Turn off with g:CL_retab_on_open = 0\r\n+ Changed the g:lispwords_file variable to g:CL_lispwords_file to avoid confusion.\r\n+ Removed unused code","package":"lisp.vim","4":"lisp.vim","src_id":"12321","5":"12321","creation_date":"1265478076","6":"1265478076"},{"0":"2951","vim_version":"6.0","1":"6.0","script_version":"1.4","2":"1.4","version_comment":"More bug fixes regarding expandtab handling. It may be beneficial to issue :retab! if you transition from expanded tabs to hard tabs.\r\nNew lines are now auto indented properly.","3":"More bug fixes regarding expandtab handling. It may be beneficial to issue :retab! if you transition from expanded tabs to hard tabs.\r\nNew lines are now auto indented properly.","package":"lisp.vim","4":"lisp.vim","src_id":"12299","5":"12299","creation_date":"1265241257","6":"1265241257"},{"0":"2951","vim_version":"6.0","1":"6.0","script_version":"1.3","2":"1.3","version_comment":"Changed the algorithm slightly so it jives better with <noexpandtab>.\r\nMinor bug fixes:\r\nA multi-line s-exp or string on the first line of it's parent will now indent correctly.","3":"Changed the algorithm slightly so it jives better with <noexpandtab>.\r\nMinor bug fixes:\r\nA multi-line s-exp or string on the first line of it's parent will now indent correctly.","package":"lisp.vim","4":"lisp.vim","src_id":"12260","5":"12260","creation_date":"1265002564","6":"1265002564"},{"0":"2951","vim_version":"6.0","1":"6.0","script_version":"1.2","2":"1.2","version_comment":"Persistent lisp words - saves on quit.\r\n<CLSetWord defun 2> sets a lisp word.","3":"Persistent lisp words - saves on quit.\r\n<CLSetWord defun 2> sets a lisp word.","package":"lisp.vim","4":"lisp.vim","src_id":"12259","5":"12259","creation_date":"1264997423","6":"1264997423"},{"0":"2951","vim_version":"6.0","1":"6.0","script_version":"1.1","2":"1.1","version_comment":"Oops! Sorry to the ... 8 people that have downloaded so far.\r\nFixed 2 bugs:\r\n1. When reducing indentation, the script attempted to jump to a negative column, causing the cursor to jump.\r\n2. With <noexpandtab>, the indentation counted tabs as a single space. Corrected by adding (&tabstop-1) * the number of leading tabs to the indentation\r\n\r\nLet me know if you find anything else wrong with it: <oconnore@gmail.com>","3":"Oops! Sorry to the ... 8 people that have downloaded so far.\r\nFixed 2 bugs:\r\n1. When reducing indentation, the script attempted to jump to a negative column, causing the cursor to jump.\r\n2. With <noexpandtab>, the indentation counted tabs as a single space. Corrected by adding (&tabstop-1) * the number of leading tabs to the indentation\r\n\r\nLet me know if you find anything else wrong with it: <oconnore@gmail.com>","package":"lisp.vim","4":"lisp.vim","src_id":"12256","5":"12256","creation_date":"1264978290","6":"1264978290"},{"0":"2951","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"lisp.vim","4":"lisp.vim","src_id":"12247","5":"12247","creation_date":"1264924031","6":"1264924031"}]},"2950":{"script_id":"2950","0":"2950","script_name":"cflow output colorful","1":"cflow output colorful","script_type":"syntax","2":"syntax","summary":"to analyze the source codes more effectively by using GNU cflow","3":"to analyze the source codes more effectively by using GNU cflow","description":"Regard cflow's output as a new language, thus we could highlight it's output to analyze the source code. so the file name suffix should be \".cflow\", just like \"cflow -o xxx.cflow\" \r\n\r\n\r\nThe snapshot has been in the tarball \r\n\r\nSNAPSHOT: \r\ncyan\t--\tfunctions defined ourself \r\npurple\t--\tvariables defined ourself \r\nred\t--\tsystem functions \r\nblack\t--\tsystem symbols \r\nyellow\t--\tfile name \r\ngreen\t--\ttype keywords in C \r\nwhite\t--\tsomething else \r\norange(fg) --\tnumber \r\norange(bg) --\trecursive functions \r\n\r\n\r\nEnjoy it \r\n\r\n","4":"Regard cflow's output as a new language, thus we could highlight it's output to analyze the source code. so the file name suffix should be \".cflow\", just like \"cflow -o xxx.cflow\" \r\n\r\n\r\nThe snapshot has been in the tarball \r\n\r\nSNAPSHOT: \r\ncyan\t--\tfunctions defined ourself \r\npurple\t--\tvariables defined ourself \r\nred\t--\tsystem functions \r\nblack\t--\tsystem symbols \r\nyellow\t--\tfile name \r\ngreen\t--\ttype keywords in C \r\nwhite\t--\tsomething else \r\norange(fg) --\tnumber \r\norange(bg) --\trecursive functions \r\n\r\n\r\nEnjoy it \r\n\r\n","install_details":"STEP 1: \r\nadd \"au BufNewFile,BufRead *.cflow setf cflow\" in u ~\/.vimrc \r\n\r\nSTEP 2: \r\nmove cflow.vim to ~\/.vim\/syntax ","5":"STEP 1: \r\nadd \"au BufNewFile,BufRead *.cflow setf cflow\" in u ~\/.vimrc \r\n\r\nSTEP 2: \r\nmove cflow.vim to ~\/.vim\/syntax ","first_name":"Yang","6":"Yang","last_name":"Zhang","7":"Zhang","releases":[{"0":"2950","vim_version":"7.0","1":"7.0","script_version":"1.3","2":"1.3","version_comment":"newest snapshot also\r\n\r\nkeyword bugs fixed","3":"newest snapshot also\r\n\r\nkeyword bugs fixed","package":"cflow_highlight_1.3.tgz","4":"cflow_highlight_1.3.tgz","src_id":"12249","5":"12249","creation_date":"1264951838","6":"1264951838"},{"0":"2950","vim_version":"7.0","1":"7.0","script_version":"1.2","2":"1.2","version_comment":"snapshot including\r\n\r\nfixed bugs","3":"snapshot including\r\n\r\nfixed bugs","package":"cflow_highlight_1.2.tgz","4":"cflow_highlight_1.2.tgz","src_id":"12246","5":"12246","creation_date":"1264909757","6":"1264909757"},{"0":"2950","vim_version":"7.0","1":"7.0","script_version":"1.1","2":"1.1","version_comment":"1. also including a snapshot\r\n\r\n2. add highlight features about GNU cflow\\'s recursive funcion output\r\n\r\n3. has included almost all symbols in C89\/C99 standard libs\\'n unistd.h, \r\n   so this version could seperate the user symbol\\'n sys symbol more clearly\r\n\r\n4. fixed some bugs","3":"1. also including a snapshot\r\n\r\n2. add highlight features about GNU cflow\\'s recursive funcion output\r\n\r\n3. has included almost all symbols in C89\/C99 standard libs\\'n unistd.h, \r\n   so this version could seperate the user symbol\\'n sys symbol more clearly\r\n\r\n4. fixed some bugs","package":"cflow_highlight_1.1.tgz","4":"cflow_highlight_1.1.tgz","src_id":"12243","5":"12243","creation_date":"1264876910","6":"1264876910"},{"0":"2950","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"no comment","3":"no comment","package":"cflow_highlight.tgz","4":"cflow_highlight.tgz","src_id":"12235","5":"12235","creation_date":"1264796372","6":"1264796372"}]},"2949":{"script_id":"2949","0":"2949","script_name":"The Max Impact Experiment","1":"The Max Impact Experiment","script_type":"utility","2":"utility","summary":"A playground to see how much we can do with pithy code","3":"A playground to see how much we can do with pithy code","description":"The other day I was sitting around drinking beer and thinking, \"Gosh, I hate how long it takes for the list of buffers to show up on the screen when I type :ls. I wish there was a built-in command that quickly opens a window with a list of buffers. Like a :bopen command that works just like the :copen and :lopen commands...\" Then it hit me. Yes, the Frisbee hit me right on the melon and I had to get off my lawn chair to throw it back. When I sat back down I had an idea... The buffer list is a perfect use of the location list! Its got file names... even line numbers! Well, I took out the laptop that I was laying on, brushed off the sand and experimented with it. So... How much work did it take to create a location list containing buffers? Precious little it turns out... \r\n\r\nHere's the jist of it... \r\n\r\n\" 1. place the output of the ls command into a variable... \r\n   redir => out \r\n   silent ls \r\n   redir END \r\n\r\n\" 2. split the string into an array... \r\n   let l = split(out, '\\n') \r\n\r\n\" 3. set the error format to conform to the buffer list format... \r\n   set efm=%m\\\"%f\\\"%*\\\\sline\\ %l \r\n\r\n\" 4. create a location list based on the list of buffers, then open the window... \r\n   lgetexpr l \r\n   lopen \r\n\r\nBlam! That's it! Now I've got a window that lists buffers, and selecting one of them will take me right to it! Granted, it's raw. But it works and it only took 7 lines of code! \r\n\r\nThen I had another loathsome thought as I was rubbing the bump on my forehead... There are many pretty, feature-rich buffer scripts out there. So what use is this? \r\n\r\nNow, either I had too much to drink or the Frisbee hit me harder that I thought because my darth-vader pug (http:\/\/bboylimping.files.wordpress.com\/2009\/05\/darth-vader-dog-costume.jpg) started arguing with me. He said, \"Because you are using the built-in location list, vim will take care of buffer selection for you, even window management, and all the location list commands are at your disposal!\" \r\n\r\nHoping that nobody could see me arguing with Darthy I said, \"Yea, so what? There are other scripts out there that have a much prettier buffer list, have more features...\" \r\n\r\n\"Shut up!\u00e2\u0080\u009d he said, interrupting me. \"It isn't about that. It's about doing as much as you can with as little code as possible.\" \r\n\r\nKnowing that he was right and humiliated that my dog beat me in an argument, I threw the Frisbee as hard as I could and hoped that he would leave me alone. It didn't work. He just sat there and stared at me with a look that said \"you're so immature...\" \r\n\r\n\"Now, post it!\" \r\n\"Hell no!\" I said with a scoff. \"Who do you think you are? You're a no-talent-ass-clown pug in a Darth-Vader costume! You're not fooling anyone, you know. Oh, and news flash: you missed the Men in Black auditions by 15 years.\" \r\n\r\nHe just stared at me with a judgmental look on his face. Not wanting to give him the satisfaction, I casually turned over with a yawn so he couldn't see me post the script. \r\n\r\nSo, here it is... I've added only a *minimum* collection of useful features to the buflist. I've refined the hell out of it; smoothing out the worst of the rough edges. No feature takes more than a few lines of code, the whole thing is only about 70-75 lines. \r\n\r\nWhy have this experiment? Well... there are some important advantages to keeping things short: \r\n- There are fewer places for bugs to hide. \r\n- The code runs considerably faster because it leverages more of the native C code.\r\n- It is easier to understand (usually). \r\n- It is easier to fix bugs. \r\n- A sufficient level of obfuscation adds to job security... and \r\n- It saves $0.000000001 in hard-drive space. \r\n\r\nDownload it and take a look at it. Play around with it. Adore the elegance of it. Can you think of any other features to add?\r\n\r\nDarthy: \"Arff! You can do it!\" Aww, crap... he caught me. \r\n\r\nFeel free to contact me with ideas and updates (take a look at my profile for the email). \r\n\r\nFor those of you who are expecting the world's best buffer script, then give a negative rating... hey lighten up! This is just a fun exercise! Please add a comment before rating! Comments can be posted on the corresponding wiki page (see link at the top of this page).","4":"The other day I was sitting around drinking beer and thinking, \"Gosh, I hate how long it takes for the list of buffers to show up on the screen when I type :ls. I wish there was a built-in command that quickly opens a window with a list of buffers. Like a :bopen command that works just like the :copen and :lopen commands...\" Then it hit me. Yes, the Frisbee hit me right on the melon and I had to get off my lawn chair to throw it back. When I sat back down I had an idea... The buffer list is a perfect use of the location list! Its got file names... even line numbers! Well, I took out the laptop that I was laying on, brushed off the sand and experimented with it. So... How much work did it take to create a location list containing buffers? Precious little it turns out... \r\n\r\nHere's the jist of it... \r\n\r\n\" 1. place the output of the ls command into a variable... \r\n   redir => out \r\n   silent ls \r\n   redir END \r\n\r\n\" 2. split the string into an array... \r\n   let l = split(out, '\\n') \r\n\r\n\" 3. set the error format to conform to the buffer list format... \r\n   set efm=%m\\\"%f\\\"%*\\\\sline\\ %l \r\n\r\n\" 4. create a location list based on the list of buffers, then open the window... \r\n   lgetexpr l \r\n   lopen \r\n\r\nBlam! That's it! Now I've got a window that lists buffers, and selecting one of them will take me right to it! Granted, it's raw. But it works and it only took 7 lines of code! \r\n\r\nThen I had another loathsome thought as I was rubbing the bump on my forehead... There are many pretty, feature-rich buffer scripts out there. So what use is this? \r\n\r\nNow, either I had too much to drink or the Frisbee hit me harder that I thought because my darth-vader pug (http:\/\/bboylimping.files.wordpress.com\/2009\/05\/darth-vader-dog-costume.jpg) started arguing with me. He said, \"Because you are using the built-in location list, vim will take care of buffer selection for you, even window management, and all the location list commands are at your disposal!\" \r\n\r\nHoping that nobody could see me arguing with Darthy I said, \"Yea, so what? There are other scripts out there that have a much prettier buffer list, have more features...\" \r\n\r\n\"Shut up!\u00e2\u0080\u009d he said, interrupting me. \"It isn't about that. It's about doing as much as you can with as little code as possible.\" \r\n\r\nKnowing that he was right and humiliated that my dog beat me in an argument, I threw the Frisbee as hard as I could and hoped that he would leave me alone. It didn't work. He just sat there and stared at me with a look that said \"you're so immature...\" \r\n\r\n\"Now, post it!\" \r\n\"Hell no!\" I said with a scoff. \"Who do you think you are? You're a no-talent-ass-clown pug in a Darth-Vader costume! You're not fooling anyone, you know. Oh, and news flash: you missed the Men in Black auditions by 15 years.\" \r\n\r\nHe just stared at me with a judgmental look on his face. Not wanting to give him the satisfaction, I casually turned over with a yawn so he couldn't see me post the script. \r\n\r\nSo, here it is... I've added only a *minimum* collection of useful features to the buflist. I've refined the hell out of it; smoothing out the worst of the rough edges. No feature takes more than a few lines of code, the whole thing is only about 70-75 lines. \r\n\r\nWhy have this experiment? Well... there are some important advantages to keeping things short: \r\n- There are fewer places for bugs to hide. \r\n- The code runs considerably faster because it leverages more of the native C code.\r\n- It is easier to understand (usually). \r\n- It is easier to fix bugs. \r\n- A sufficient level of obfuscation adds to job security... and \r\n- It saves $0.000000001 in hard-drive space. \r\n\r\nDownload it and take a look at it. Play around with it. Adore the elegance of it. Can you think of any other features to add?\r\n\r\nDarthy: \"Arff! You can do it!\" Aww, crap... he caught me. \r\n\r\nFeel free to contact me with ideas and updates (take a look at my profile for the email). \r\n\r\nFor those of you who are expecting the world's best buffer script, then give a negative rating... hey lighten up! This is just a fun exercise! Please add a comment before rating! Comments can be posted on the corresponding wiki page (see link at the top of this page).","install_details":"Drop it in your plugin directory.","5":"Drop it in your plugin directory.","first_name":"David","6":"David","last_name":"Larson","7":"Larson","releases":[{"0":"2949","vim_version":"7.0","1":"7.0","script_version":"0.2a","2":"0.2a","version_comment":"You can now change the mapping to open the buffer list by setting the buflist_open variable. Added usage documentation.","3":"You can now change the mapping to open the buffer list by setting the buflist_open variable. Added usage documentation.","package":"buflist.vim","4":"buflist.vim","src_id":"12503","5":"12503","creation_date":"1267211822","6":"1267211822"},{"0":"2949","vim_version":"7.0","1":"7.0","script_version":"0.2","2":"0.2","version_comment":"Found that if I use an autocommand to close the window it simplified the script a lot! It is only about 29 lines long now! (ignoring empty lines) ","3":"Found that if I use an autocommand to close the window it simplified the script a lot! It is only about 29 lines long now! (ignoring empty lines) ","package":"buflist.vim","4":"buflist.vim","src_id":"12369","5":"12369","creation_date":"1266010404","6":"1266010404"},{"0":"2949","vim_version":"7.0","1":"7.0","script_version":"0.1aa","2":"0.1aa","version_comment":"Bug fix: sometimes shortening a path made it longer. \r\nStrengthened my resolve to add only pithy features. (I almost gave in to the temptation of adding custom highlighting that was of little to no use and was several lines long... but I stood strong. Thank you for your prayers.)","3":"Bug fix: sometimes shortening a path made it longer. \r\nStrengthened my resolve to add only pithy features. (I almost gave in to the temptation of adding custom highlighting that was of little to no use and was several lines long... but I stood strong. Thank you for your prayers.)","package":"buflist.vim","4":"buflist.vim","src_id":"12300","5":"12300","creation_date":"1265241887","6":"1265241887"},{"0":"2949","vim_version":"7.0","1":"7.0","script_version":"0.1a","2":"0.1a","version_comment":"Added more comments and obfuscation.","3":"Added more comments and obfuscation.","package":"buflist.vim","4":"buflist.vim","src_id":"12269","5":"12269","creation_date":"1265057446","6":"1265057446"},{"0":"2949","vim_version":"7.2","1":"7.2","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"buflist.vim","4":"buflist.vim","src_id":"12217","5":"12217","creation_date":"1264706709","6":"1264706709"}]},"2948":{"script_id":"2948","0":"2948","script_name":"GoogleSuggest Complete","1":"GoogleSuggest Complete","script_type":"utility","2":"utility","summary":"complete function using google suggest API. perhaps, you should input japanese w","3":"complete function using google suggest API. perhaps, you should input japanese w","description":"Lesson1:\r\n\r\n  takasu\r\n\r\n  http:\/\/go-gyazo.appspot.com\/95db054f3a2a0bdf.png\r\n\r\n  <c-x><c-u>\r\n\r\n  http:\/\/go-gyazo.appspot.com\/37a26d916480c937.png\r\n\r\n  * perhaps, you can see the candidates above.\r\n\r\nLesson2:\r\n\r\n  watasinonamaeha<c-x><c-u>\r\n\r\n  => 私の名前はキムサムスン\r\n  * who is kim samsoon?\r\n\r\nEtc:\r\n\r\n  naitu<c-x><c-u>\r\n  => ナイツ お笑い\r\n\r\n  www<c-x><c-u>\r\n  => www.yahoo.co.jp\r\n\r\n  gm<c-x><c-u>\r\n  => gmailへようこそ\r\n\r\n  vimp<c-x><c-u>\r\n  => vimperator\r\n\r\n  puri<c-x><c-u>\r\n  => プリキュア","4":"Lesson1:\r\n\r\n  takasu\r\n\r\n  http:\/\/go-gyazo.appspot.com\/95db054f3a2a0bdf.png\r\n\r\n  <c-x><c-u>\r\n\r\n  http:\/\/go-gyazo.appspot.com\/37a26d916480c937.png\r\n\r\n  * perhaps, you can see the candidates above.\r\n\r\nLesson2:\r\n\r\n  watasinonamaeha<c-x><c-u>\r\n\r\n  => 私の名前はキムサムスン\r\n  * who is kim samsoon?\r\n\r\nEtc:\r\n\r\n  naitu<c-x><c-u>\r\n  => ナイツ お笑い\r\n\r\n  www<c-x><c-u>\r\n  => www.yahoo.co.jp\r\n\r\n  gm<c-x><c-u>\r\n  => gmailへようこそ\r\n\r\n  vimp<c-x><c-u>\r\n  => vimperator\r\n\r\n  puri<c-x><c-u>\r\n  => プリキュア","install_details":"cp googlesugguest-complete.vim ~\/.vim\/plugin","5":"cp googlesugguest-complete.vim ~\/.vim\/plugin","first_name":"Yasuhiro","6":"Yasuhiro","last_name":"Matsumoto","7":"Matsumoto","releases":[{"0":"2948","vim_version":"7.0","1":"7.0","script_version":"0.2","2":"0.2","version_comment":"This is an upgrade for GoogleSuggest Complete. fixed input-output encoding.","3":"This is an upgrade for GoogleSuggest Complete. fixed input-output encoding.","package":"googlesuggest-complete.vim","4":"googlesuggest-complete.vim","src_id":"12221","5":"12221","creation_date":"1264735469","6":"1264735469"},{"0":"2948","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"googlesuggest-complete.vim","4":"googlesuggest-complete.vim","src_id":"12204","5":"12204","creation_date":"1264662222","6":"1264662222"}]},"2947":{"script_id":"2947","0":"2947","script_name":"bvemu.vim","1":"bvemu.vim","script_type":"color scheme","2":"color scheme","summary":"Another Dark Scheme for gvim","3":"Another Dark Scheme for gvim","description":"This is a dark scheme and the preview is available at http:\/\/bvemu.blogspot.com\/2010\/01\/preview-of-files-with-colorschemebvemu.html \r\n\r\nComments are welcomed\r\n\r\nJust place the bvemu.vim files in your .vim\/colors\/ directory \r\nand in your .vimrc  set as following \r\ncolorscheme bvemu","4":"This is a dark scheme and the preview is available at http:\/\/bvemu.blogspot.com\/2010\/01\/preview-of-files-with-colorschemebvemu.html \r\n\r\nComments are welcomed\r\n\r\nJust place the bvemu.vim files in your .vim\/colors\/ directory \r\nand in your .vimrc  set as following \r\ncolorscheme bvemu","install_details":"","5":"","first_name":"Bala Subramanyam","6":"Bala Subramanyam","last_name":"V","7":"V","releases":[{"0":"2947","vim_version":"7.0","1":"7.0","script_version":"1.1","2":"1.1","version_comment":"Minor Update as per user`s request","3":"Minor Update as per user`s request","package":"bvemu.vim","4":"bvemu.vim","src_id":"12201","5":"12201","creation_date":"1264613189","6":"1264613189"},{"0":"2947","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"bvemu.vim","4":"bvemu.vim","src_id":"12198","5":"12198","creation_date":"1264578278","6":"1264578278"}]},"2946":{"script_id":"2946","0":"2946","script_name":"AGTD","1":"AGTD","script_type":"utility","2":"utility","summary":"Almighty GTD File for Vim","3":"Almighty GTD File for Vim","description":"Tired of trying thousand of tools to organize my life, and inspired in the\r\nidea of ONE BIG TEXT FILE from Danny O'Brien, I decided that the world needed\r\nyet another GTD tool. The \"Almighty\" part is a reference to the idea of having\r\nall type of notes about your tasks in one single file.\r\n\r\nThe whole idea of this GTD implementation relies in some custom notation\r\nmarks, the Folding capabilities of VIM and its power to work quickly with\r\ntext. I wanted something portable to collect, edit, search and structure\r\nlightning fast my notes.\r\n\r\nYou can get a longer description and one screenshot at:\r\n\r\nhttps:\/\/github.com\/fgarcia\/agtd\r\n","4":"Tired of trying thousand of tools to organize my life, and inspired in the\r\nidea of ONE BIG TEXT FILE from Danny O'Brien, I decided that the world needed\r\nyet another GTD tool. The \"Almighty\" part is a reference to the idea of having\r\nall type of notes about your tasks in one single file.\r\n\r\nThe whole idea of this GTD implementation relies in some custom notation\r\nmarks, the Folding capabilities of VIM and its power to work quickly with\r\ntext. I wanted something portable to collect, edit, search and structure\r\nlightning fast my notes.\r\n\r\nYou can get a longer description and one screenshot at:\r\n\r\nhttps:\/\/github.com\/fgarcia\/agtd\r\n","install_details":"Open the file and install with\r\n     :so %\r\n\r\nMake sure you have somewhere in your Vimrc file the filetype plugin enabled:\r\n     :filetype plugin on","5":"Open the file and install with\r\n     :so %\r\n\r\nMake sure you have somewhere in your Vimrc file the filetype plugin enabled:\r\n     :filetype plugin on","first_name":"Francisco","6":"Francisco","last_name":"Garcia","7":"Garcia","releases":[{"0":"2946","vim_version":"7.0","1":"7.0","script_version":"0.4","2":"0.4","version_comment":"This project is no longer maintained","3":"This project is no longer maintained","package":"agtd.vim","4":"agtd.vim","src_id":"23259","5":"23259","creation_date":"1430814103","6":"1430814103"}]},"2945":{"script_id":"2945","0":"2945","script_name":"AutomaticLaTeXPlugin","1":"AutomaticLaTeXPlugin","script_type":"ftplugin","2":"ftplugin","summary":"Background compilation, completion, bib serch, toc and other nice features.","3":"Background compilation, completion, bib serch, toc and other nice features.","description":"NOT MAINTAINED\r\n\r\nThis is a complete plugin with lots of tools to make editing of TeX\/LaTeX file more friendly. Its main features include: background compilation, forward and inverse search for both dvi and pdf (okular), extended completion, AMSRef query for bibliography references, font preview, support for projects with multiple tex files, and much much more. For a detailed list of features see: \r\n        http:\/\/atp-vim.sourceforge.net\/features.shtml\r\nAfter looking there you can read the complete documentation in vim (:help atp) \r\n\r\nWant to help to develop: fork me at GitHub:\r\nhttps:\/\/github.com\/coot\/atp_vim\r\n\r\n\r\nLATEST SNAPSHOTS:\r\n    You can get the latest snapshots (stable\/unstable releases) on \r\n        http:\/\/sourceforge.net\/projects\/atp-vim\/files\/snapshots\/ \r\n    or if you have ATP version 9.2 or higher using :UpdateATP command \r\n    inside vim (check out :help atp-:UpdateATP)\r\n\r\nONLINE HELP:\r\n        http:\/\/atp-vim.sourceforge.net\/help.shtml\r\n\r\nLATEX BOX:\r\n    This plugin includes: vimscript#3109  (LatexBox by David Munger). \r\n","4":"NOT MAINTAINED\r\n\r\nThis is a complete plugin with lots of tools to make editing of TeX\/LaTeX file more friendly. Its main features include: background compilation, forward and inverse search for both dvi and pdf (okular), extended completion, AMSRef query for bibliography references, font preview, support for projects with multiple tex files, and much much more. For a detailed list of features see: \r\n        http:\/\/atp-vim.sourceforge.net\/features.shtml\r\nAfter looking there you can read the complete documentation in vim (:help atp) \r\n\r\nWant to help to develop: fork me at GitHub:\r\nhttps:\/\/github.com\/coot\/atp_vim\r\n\r\n\r\nLATEST SNAPSHOTS:\r\n    You can get the latest snapshots (stable\/unstable releases) on \r\n        http:\/\/sourceforge.net\/projects\/atp-vim\/files\/snapshots\/ \r\n    or if you have ATP version 9.2 or higher using :UpdateATP command \r\n    inside vim (check out :help atp-:UpdateATP)\r\n\r\nONLINE HELP:\r\n        http:\/\/atp-vim.sourceforge.net\/help.shtml\r\n\r\nLATEX BOX:\r\n    This plugin includes: vimscript#3109  (LatexBox by David Munger). \r\n","install_details":"To install open the vimball file and source it ':so %' or ':source %'. You can use $HOME\/.atp.vim configuration file to set the atp variables, which is handy for local-buffer settings.","5":"To install open the vimball file and source it ':so %' or ':source %'. You can use $HOME\/.atp.vim configuration file to set the atp variables, which is handy for local-buffer settings.","first_name":"Marcin","6":"Marcin","last_name":"Szamotulski","7":"Szamotulski","releases":[{"0":"2945","vim_version":"7.4","1":"7.4","script_version":"12.5","2":"12.5","version_comment":"A few bug fixes.","3":"A few bug fixes.","package":"AutomaticTexPlugin_12.5.vmb","4":"AutomaticTexPlugin_12.5.vmb","src_id":"21762","5":"21762","creation_date":"1397290451","6":"1397290451"},{"0":"2945","vim_version":"7.3","1":"7.3","script_version":"12.4","2":"12.4","version_comment":"New release.","3":"New release.","package":"AutomaticTexPlugin_12.4.vmb","4":"AutomaticTexPlugin_12.4.vmb","src_id":"21370","5":"21370","creation_date":"1390643699","6":"1390643699"},{"0":"2945","vim_version":"7.3","1":"7.3","script_version":"12.3","2":"12.3","version_comment":"see ':h atp-news'. First release which supports windows os.","3":"see ':h atp-news'. First release which supports windows os.","package":"AutomaticTexPlugin_12.3.vmb","4":"AutomaticTexPlugin_12.3.vmb","src_id":"19965","5":"19965","creation_date":"1367162822","6":"1367162822"},{"0":"2945","vim_version":"7.3","1":"7.3","script_version":"12.2","2":"12.2","version_comment":"A new version with a few fixes. See :help atp-news.","3":"A new version with a few fixes. See :help atp-news.","package":"AutomaticTexPlugin_12.2.vmb","4":"AutomaticTexPlugin_12.2.vmb","src_id":"19440","5":"19440","creation_date":"1359368754","6":"1359368754"},{"0":"2945","vim_version":"7.3","1":"7.3","script_version":"12.1","2":"12.1","version_comment":"Fixes for ATP 12 release + some small amendments, see \":help atp-news\".","3":"Fixes for ATP 12 release + some small amendments, see \":help atp-news\".","package":"AutomaticTexPlugin_12.1.vmb","4":"AutomaticTexPlugin_12.1.vmb","src_id":"18694","5":"18694","creation_date":"1348684574","6":"1348684574"},{"0":"2945","vim_version":"7.3","1":"7.3","script_version":"12","2":"12","version_comment":"New release, with lots of bug fixes, major updates and great new features. For the news look at \":help atp-news\" .","3":"New release, with lots of bug fixes, major updates and great new features. For the news look at \":help atp-news\" .","package":"AutomaticTexPlugin_12.vmb","4":"AutomaticTexPlugin_12.vmb","src_id":"18648","5":"18648","creation_date":"1348227623","6":"1348227623"},{"0":"2945","vim_version":"7.3","1":"7.3","script_version":"11","2":"11","version_comment":"See for changes at \\\":help atp-news\\\".","3":"See for changes at \\\":help atp-news\\\".","package":"AutomaticTexPlugin_11.vmb","4":"AutomaticTexPlugin_11.vmb","src_id":"17959","5":"17959","creation_date":"1337062855","6":"1337062855"},{"0":"2945","vim_version":"7.3","1":"7.3","script_version":"10.6.4","2":"10.6.4","version_comment":"New release with some small changes, see :help atp-news","3":"New release with some small changes, see :help atp-news","package":"AutomaticTexPlugin_10.6.4.vmb","4":"AutomaticTexPlugin_10.6.4.vmb","src_id":"17124","5":"17124","creation_date":"1325092139","6":"1325092139"},{"0":"2945","vim_version":"7.3","1":"7.3","script_version":"10.6.3","2":"10.6.3","version_comment":"See :help atp-news.","3":"See :help atp-news.","package":"AutomaticTexPlugin_10.6.3.vmb","4":"AutomaticTexPlugin_10.6.3.vmb","src_id":"17054","5":"17054","creation_date":"1323594478","6":"1323594478"},{"0":"2945","vim_version":"7.3","1":"7.3","script_version":"10.6.2","2":"10.6.2","version_comment":"For changes see ':help atp-news'.","3":"For changes see ':help atp-news'.","package":"AutomaticTexPlugin_10.6.2.vmb","4":"AutomaticTexPlugin_10.6.2.vmb","src_id":"17050","5":"17050","creation_date":"1323534307","6":"1323534307"},{"0":"2945","vim_version":"7.3","1":"7.3","script_version":"10.6.1","2":"10.6.1","version_comment":"See :help atp-news.","3":"See :help atp-news.","package":"AutomaticTexPlugin_10.6.1.vmb","4":"AutomaticTexPlugin_10.6.1.vmb","src_id":"16643","5":"16643","creation_date":"1318167874","6":"1318167874"},{"0":"2945","vim_version":"7.3","1":"7.3","script_version":"10.6","2":"10.6","version_comment":"See :help atp-news.","3":"See :help atp-news.","package":"AutomaticTexPlugin_10.6.vmb","4":"AutomaticTexPlugin_10.6.vmb","src_id":"16571","5":"16571","creation_date":"1316945498","6":"1316945498"},{"0":"2945","vim_version":"7.3","1":"7.3","script_version":"10.5","2":"10.5","version_comment":"version 10.5, see ':help atp-news'.","3":"version 10.5, see ':help atp-news'.","package":"AutomaticTexPlugin_10.5.vmb","4":"AutomaticTexPlugin_10.5.vmb","src_id":"16512","5":"16512","creation_date":"1315852701","6":"1315852701"},{"0":"2945","vim_version":"7.3","1":"7.3","script_version":"10.3","2":"10.3","version_comment":"* Skim and Xpdf (ver. 3.03) with both inverse and reverse searching.\r\n* normal r which acts on both opening and closing bracket simultaneously.\r\n* Tab completion is faster.\r\n* MakeLatex shows errors of bibtex\/biber\/makeidx.\r\nand some other changes and fixes.","3":"* Skim and Xpdf (ver. 3.03) with both inverse and reverse searching.\r\n* normal r which acts on both opening and closing bracket simultaneously.\r\n* Tab completion is faster.\r\n* MakeLatex shows errors of bibtex\/biber\/makeidx.\r\nand some other changes and fixes.","package":"AutomaticTexPlugin_10.3.vmb","4":"AutomaticTexPlugin_10.3.vmb","src_id":"16375","5":"16375","creation_date":"1314473771","6":"1314473771"},{"0":"2945","vim_version":"7.3","1":"7.3","script_version":"10.2","2":"10.2","version_comment":"See :help atp-news.","3":"See :help atp-news.","package":"AutomaticTexPlugin_10.2.vmb","4":"AutomaticTexPlugin_10.2.vmb","src_id":"16269","5":"16269","creation_date":"1313445382","6":"1313445382"},{"0":"2945","vim_version":"7.3","1":"7.3","script_version":"10","2":"10","version_comment":"See :help atp-news.","3":"See :help atp-news.","package":"AutomaticTexPlugin_10.vmb","4":"AutomaticTexPlugin_10.vmb","src_id":"16213","5":"16213","creation_date":"1312793482","6":"1312793482"},{"0":"2945","vim_version":"7.3","1":"7.3","script_version":"9.7.4","2":"9.7.4","version_comment":"See :help atp-news.","3":"See :help atp-news.","package":"AutomaticTexPlugin_9.7.4.vmb","4":"AutomaticTexPlugin_9.7.4.vmb","src_id":"16126","5":"16126","creation_date":"1311324761","6":"1311324761"},{"0":"2945","vim_version":"7.3","1":"7.3","script_version":"9.7.1","2":"9.7.1","version_comment":"See :help atp-vim. I forgot to add package files in 9.7 release.","3":"See :help atp-vim. I forgot to add package files in 9.7 release.","package":"AutomaticTexPlugin_9.7.1.vba","4":"AutomaticTexPlugin_9.7.1.vba","src_id":"16071","5":"16071","creation_date":"1310567004","6":"1310567004"},{"0":"2945","vim_version":"7.3","1":"7.3","script_version":"9.7","2":"9.7","version_comment":"See :help atp-vim and enjoy new features ;)","3":"See :help atp-vim and enjoy new features ;)","package":"AutomaticTexPlugin_9.7.vba","4":"AutomaticTexPlugin_9.7.vba","src_id":"16070","5":"16070","creation_date":"1310543530","6":"1310543530"},{"0":"2945","vim_version":"7.3","1":"7.3","script_version":"9.6.1","2":"9.6.1","version_comment":"Check :help atp-news. ATP has a new web page http:\/\/atp-vim.sf.net, with RSS news reader, you can get the RSS content with http:\/\/sourceforge.net\/projects\/atp-vim .","3":"Check :help atp-news. ATP has a new web page http:\/\/atp-vim.sf.net, with RSS news reader, you can get the RSS content with http:\/\/sourceforge.net\/projects\/atp-vim .","package":"AutomaticTexPlugin_9.6.1.vba","4":"AutomaticTexPlugin_9.6.1.vba","src_id":"15868","5":"15868","creation_date":"1307963885","6":"1307963885"},{"0":"2945","vim_version":"7.3","1":"7.3","script_version":"9.6","2":"9.6","version_comment":"See :help atp-news","3":"See :help atp-news","package":"AutomaticTexPlugin_9.6.vba","4":"AutomaticTexPlugin_9.6.vba","src_id":"15814","5":"15814","creation_date":"1307273327","6":"1307273327"},{"0":"2945","vim_version":"7.3","1":"7.3","script_version":"9.5","2":"9.5","version_comment":"See :help atp-news. (Tags added).","3":"See :help atp-news. (Tags added).","package":"AutomaticTexPlugin_9.5.vba","4":"AutomaticTexPlugin_9.5.vba","src_id":"15697","5":"15697","creation_date":"1306091639","6":"1306091639"},{"0":"2945","vim_version":"7.3","1":"7.3","script_version":"9.4.3","2":"9.4.3","version_comment":"Patches for 9.4 release.","3":"Patches for 9.4 release.","package":"AutomaticTexPlugin_9.4.3.vba","4":"AutomaticTexPlugin_9.4.3.vba","src_id":"15619","5":"15619","creation_date":"1305009957","6":"1305009957"},{"0":"2945","vim_version":"7.3","1":"7.3","script_version":"9.4.2","2":"9.4.2","version_comment":"Fixes for 9.4 release.","3":"Fixes for 9.4 release.","package":"AutomaticTexPlugin_9.4.2.vba","4":"AutomaticTexPlugin_9.4.2.vba","src_id":"15610","5":"15610","creation_date":"1304892436","6":"1304892436"},{"0":"2945","vim_version":"7.0","1":"7.0","script_version":"9.4.1","2":"9.4.1","version_comment":"Small fixes for 9.4 release.","3":"Small fixes for 9.4 release.","package":"AutomaticTexPlugin_9.4.1.vba","4":"AutomaticTexPlugin_9.4.1.vba","src_id":"15607","5":"15607","creation_date":"1304865703","6":"1304865703"},{"0":"2945","vim_version":"7.0","1":"7.0","script_version":"9.4","2":"9.4","version_comment":"See :help atp-news","3":"See :help atp-news","package":"AutomaticTexPlugin_9.4.vba","4":"AutomaticTexPlugin_9.4.vba","src_id":"15606","5":"15606","creation_date":"1304837750","6":"1304837750"},{"0":"2945","vim_version":"7.3","1":"7.3","script_version":"9.3.5","2":"9.3.5","version_comment":"see :help atp-news","3":"see :help atp-news","package":"AutomaticTexPlugin_9.3.5.vba","4":"AutomaticTexPlugin_9.3.5.vba","src_id":"15503","5":"15503","creation_date":"1303459998","6":"1303459998"},{"0":"2945","vim_version":"7.0","1":"7.0","script_version":"9.3","2":"9.3","version_comment":"see :help atp-news for changes.","3":"see :help atp-news for changes.","package":"AutomaticTexPlugin_9.3.vba","4":"AutomaticTexPlugin_9.3.vba","src_id":"15464","5":"15464","creation_date":"1303042793","6":"1303042793"},{"0":"2945","vim_version":"7.3","1":"7.3","script_version":"9.2.7","2":"9.2.7","version_comment":"- This update contains several small changes and one important fix (for those who do not use bibtex). See :help atp-news.","3":"- This update contains several small changes and one important fix (for those who do not use bibtex). See :help atp-news.","package":"AutomaticTexPlugin_9.2.7.vba","4":"AutomaticTexPlugin_9.2.7.vba","src_id":"15448","5":"15448","creation_date":"1302730802","6":"1302730802"},{"0":"2945","vim_version":"7.3","1":"7.3","script_version":"9.2","2":"9.2","version_comment":"* This release is a major step forward ;) see long list of changes :help atp-news, thanks for Ivo Lopez for the help!\r\nMajor news:\r\n- new compelation using python script\r\n- progress bar for compelation\r\n- UpdateATP[!]    = to get new Stable\/Unstable release directly from SourceForge project hosting site.","3":"* This release is a major step forward ;) see long list of changes :help atp-news, thanks for Ivo Lopez for the help!\r\nMajor news:\r\n- new compelation using python script\r\n- progress bar for compelation\r\n- UpdateATP[!]    = to get new Stable\/Unstable release directly from SourceForge project hosting site.","package":"AutomaticTexPlugin_9.2.vba","4":"AutomaticTexPlugin_9.2.vba","src_id":"15417","5":"15417","creation_date":"1302349328","6":"1302349328"},{"0":"2945","vim_version":"7.3","1":"7.3","script_version":"9.1.1","2":"9.1.1","version_comment":"See ver 9.1 (important fix in doc file, thanks to I.Lopez)","3":"See ver 9.1 (important fix in doc file, thanks to I.Lopez)","package":"AutomaticTexPlugin_9.1.1.vba","4":"AutomaticTexPlugin_9.1.1.vba","src_id":"15269","5":"15269","creation_date":"1300694131","6":"1300694131"},{"0":"2945","vim_version":"7.0","1":"7.0","script_version":"9.0","2":"9.0","version_comment":"See :h atp-news for changes [ there are some NEW features :), and many fixes! ]\r\n","3":"See :h atp-news for changes [ there are some NEW features :), and many fixes! ]\r\n","package":"AutomaticTexPlugin_9.vba","4":"AutomaticTexPlugin_9.vba","src_id":"15243","5":"15243","creation_date":"1300449326","6":"1300449326"}]},"2944":{"script_id":"2944","0":"2944","script_name":"visualstar.vim","1":"visualstar.vim","script_type":"utility","2":"utility","summary":"star(*) for Visual-mode.","3":"star(*) for Visual-mode.","description":"*visualstar* is a Vim plugin to provide a |star| feature for |Visual-mode|.\r\nIn other words, you can search your selection text in |Visual-mode|.\r\n\r\nLatest Version:\r\nhttps:\/\/github.com\/thinca\/vim-visualstar","4":"*visualstar* is a Vim plugin to provide a |star| feature for |Visual-mode|.\r\nIn other words, you can search your selection text in |Visual-mode|.\r\n\r\nLatest Version:\r\nhttps:\/\/github.com\/thinca\/vim-visualstar","install_details":"","5":"","first_name":"thinca","6":"thinca","last_name":" ","7":" ","releases":[{"0":"2944","vim_version":"7.2","1":"7.2","script_version":"0.4.0","2":"0.4.0","version_comment":"- Removed default key mappings from Select-mode.\r\n- Added key mappings from <S-LeftMouse>.","3":"- Removed default key mappings from Select-mode.\r\n- Added key mappings from <S-LeftMouse>.","package":"vim-visualstar-0.4.0.zip","4":"vim-visualstar-0.4.0.zip","src_id":"18199","5":"18199","creation_date":"1340878859","6":"1340878859"},{"0":"2944","vim_version":"7.2","1":"7.2","script_version":"0.3.0","2":"0.3.0","version_comment":"- Added key mappings from <kMultiply>.","3":"- Added key mappings from <kMultiply>.","package":"vim-visualstar-0.3.0.zip","4":"vim-visualstar-0.3.0.zip","src_id":"17936","5":"17936","creation_date":"1336771595","6":"1336771595"},{"0":"2944","vim_version":"7.0","1":"7.0","script_version":"0.2.1","2":"0.2.1","version_comment":"- Improved for multibyte character.","3":"- Improved for multibyte character.","package":"vim-visualstar-0.2.1.zip","4":"vim-visualstar-0.2.1.zip","src_id":"12891","5":"12891","creation_date":"1272031178","6":"1272031178"},{"0":"2944","vim_version":"7.2","1":"7.2","script_version":"0.2.0","2":"0.2.0","version_comment":"Initial upload","3":"Initial upload","package":"vim-visualstar-0.2.0.zip","4":"vim-visualstar-0.2.0.zip","src_id":"12181","5":"12181","creation_date":"1264439899","6":"1264439899"}]},"2943":{"script_id":"2943","0":"2943","script_name":"ccvext.vim","1":"ccvext.vim","script_type":"ftplugin","2":"ftplugin","summary":"More convenience way to use ctags and cscope in vim","3":"More convenience way to use ctags and cscope in vim","description":"This is a new version from JumpInCode.vim I don't know why i can't upload a new version to the old JumpInCode page (http:\/\/www.vim.org\/scripts\/script.php?script_id=2770)? So I start this branch\r\n\r\nctags and cscope plugin for vim, more convenice way to use ctags and cscope in vim.\r\n\r\nCommand:\r\n\\sy Generate tags and cscope database from current directory.\r\n\\sc Configure window --- Take care of the help information below the window.\r\n     D:      Remove the project's database.\r\n     d:      Remove the project from current environment.\r\n     a(\/n): Add the project to current environment.\r\n\r\nSample_1:\r\n    :e your_source_.h\r\n    :cd %:p:h\r\n    \\sy\r\n    <Enter>\r\n    :EnQuickSnippet\r\n\r\nSample_2:\r\n    :cd d:\\\r\n    \\sc\r\n    <Select your database and input enter>\r\n    :EnQuickSnippet\r\n\r\nSuggestion:\r\n    1. <Leader>sy is default script command, if it conflict with your other script you can change it at line 753 of script.\r\n    2. <Leader>sy is default script command, if it conflict with your other script you can change it at line 754 of script.\r\n    3. Command EnQuickSnippet, DiQuickSnippet are not mapped, for convenient way is map it to your own command in your .vimrc or _vimrc file.\r\n    4. This script is better work with script: taglist ( http:\/\/www.vim.org\/scripts\/script.php?script_id=273 )\r\n    5. This script is better work with script: MRU  ( http:\/\/www.vim.org\/scripts\/script.php?script_id=273 )\r\n    6. This script is better work with script: Mark  ( http:\/\/www.vim.org\/scripts\/script.php?script_id=1238 )\r\n    7. This script is better work with script: NERDTree ( http:\/\/www.vim.org\/scripts\/script.php?script_id=1658 )\r\n\r\nUpdate (4.7.0)\r\n4.7.0\r\n    Descript:\r\n    - Fix the problem about permission on Unix like system.\r\n4.6.0 \r\n  Descript:\r\n    - Fix the problem the multi cscope connection problem about that connection then \r\n      disconnection for few times the connection order will confused.\r\n4.5.0\r\n  Descript:\r\n    - Fix the problem when ccvext work with script bufexplorer.vim\r\n4.4.0\r\n  Descript:\r\n    - Add C# source code supported. (Recently I am working with it)\r\n    - Fix the problem: Sometimes double click the soruce snippet window will cause a dead loop.\r\n  TUDO:\r\n    - Cscope database list is not work perfect.\r\n4.3.0\r\n  Descript:\r\n    - When tags file and cscope file not exist, auto remove it from config list.\r\n4.2.0\r\n  Descript:\r\n    - Don't search from tags when the text's lenght is equal to 1\r\n    - Don't search from tags when the text data is c\/c++ key word.\r\n  BugFix:\r\n    - Fix the problem about double click in the main source window.\r\n4.1.0\r\n  Descript:\r\n    - Modify tip window's info when tags searched not found.\r\n4.0.0\r\n  Descript:\r\n    - Rename commands name\r\n    - Auto update source snippet window\r\n\r\nRequirement:\r\n    ctags and cscope. And windows user can download them from http:\/\/code.google.com\/p\/easy-vim\/downloads\/list\r\n","4":"This is a new version from JumpInCode.vim I don't know why i can't upload a new version to the old JumpInCode page (http:\/\/www.vim.org\/scripts\/script.php?script_id=2770)? So I start this branch\r\n\r\nctags and cscope plugin for vim, more convenice way to use ctags and cscope in vim.\r\n\r\nCommand:\r\n\\sy Generate tags and cscope database from current directory.\r\n\\sc Configure window --- Take care of the help information below the window.\r\n     D:      Remove the project's database.\r\n     d:      Remove the project from current environment.\r\n     a(\/n): Add the project to current environment.\r\n\r\nSample_1:\r\n    :e your_source_.h\r\n    :cd %:p:h\r\n    \\sy\r\n    <Enter>\r\n    :EnQuickSnippet\r\n\r\nSample_2:\r\n    :cd d:\\\r\n    \\sc\r\n    <Select your database and input enter>\r\n    :EnQuickSnippet\r\n\r\nSuggestion:\r\n    1. <Leader>sy is default script command, if it conflict with your other script you can change it at line 753 of script.\r\n    2. <Leader>sy is default script command, if it conflict with your other script you can change it at line 754 of script.\r\n    3. Command EnQuickSnippet, DiQuickSnippet are not mapped, for convenient way is map it to your own command in your .vimrc or _vimrc file.\r\n    4. This script is better work with script: taglist ( http:\/\/www.vim.org\/scripts\/script.php?script_id=273 )\r\n    5. This script is better work with script: MRU  ( http:\/\/www.vim.org\/scripts\/script.php?script_id=273 )\r\n    6. This script is better work with script: Mark  ( http:\/\/www.vim.org\/scripts\/script.php?script_id=1238 )\r\n    7. This script is better work with script: NERDTree ( http:\/\/www.vim.org\/scripts\/script.php?script_id=1658 )\r\n\r\nUpdate (4.7.0)\r\n4.7.0\r\n    Descript:\r\n    - Fix the problem about permission on Unix like system.\r\n4.6.0 \r\n  Descript:\r\n    - Fix the problem the multi cscope connection problem about that connection then \r\n      disconnection for few times the connection order will confused.\r\n4.5.0\r\n  Descript:\r\n    - Fix the problem when ccvext work with script bufexplorer.vim\r\n4.4.0\r\n  Descript:\r\n    - Add C# source code supported. (Recently I am working with it)\r\n    - Fix the problem: Sometimes double click the soruce snippet window will cause a dead loop.\r\n  TUDO:\r\n    - Cscope database list is not work perfect.\r\n4.3.0\r\n  Descript:\r\n    - When tags file and cscope file not exist, auto remove it from config list.\r\n4.2.0\r\n  Descript:\r\n    - Don't search from tags when the text's lenght is equal to 1\r\n    - Don't search from tags when the text data is c\/c++ key word.\r\n  BugFix:\r\n    - Fix the problem about double click in the main source window.\r\n4.1.0\r\n  Descript:\r\n    - Modify tip window's info when tags searched not found.\r\n4.0.0\r\n  Descript:\r\n    - Rename commands name\r\n    - Auto update source snippet window\r\n\r\nRequirement:\r\n    ctags and cscope. And windows user can download them from http:\/\/code.google.com\/p\/easy-vim\/downloads\/list\r\n","install_details":"copy ccvext.vim to  ~\/.vim\/plugin\/","5":"copy ccvext.vim to  ~\/.vim\/plugin\/","first_name":"zuopeng","6":"zuopeng","last_name":"chen","7":"chen","releases":[{"0":"2943","vim_version":"7.0","1":"7.0","script_version":"4.7","2":"4.7","version_comment":"Fix the problem about permission on Unix like system, I am sorry about this. You know that permission problem never showed up on windows.","3":"Fix the problem about permission on Unix like system, I am sorry about this. You know that permission problem never showed up on windows.","package":"ccvext.vim","4":"ccvext.vim","src_id":"16390","5":"16390","creation_date":"1314579932","6":"1314579932"},{"0":"2943","vim_version":"7.0","1":"7.0","script_version":"4.6","2":"4.6","version_comment":"Fix the problem the multi cscope connection problem about that connection then disconnection for few times the connection order will confused.","3":"Fix the problem the multi cscope connection problem about that connection then disconnection for few times the connection order will confused.","package":"ccvext.vim","4":"ccvext.vim","src_id":"16387","5":"16387","creation_date":"1314508083","6":"1314508083"},{"0":"2943","vim_version":"7.0","1":"7.0","script_version":"4.5","2":"4.5","version_comment":"Fix the problem when ccvext work with script bufexplorer.vim","3":"Fix the problem when ccvext work with script bufexplorer.vim","package":"ccvext.vim","4":"ccvext.vim","src_id":"15992","5":"15992","creation_date":"1309168255","6":"1309168255"},{"0":"2943","vim_version":"7.0","1":"7.0","script_version":"4.4","2":"4.4","version_comment":"- Add C# source code supported (Recently I am working with it) \r\n- Fix the problem: Sometimes double click the soruce snippet window will cause a dead loop.","3":"- Add C# source code supported (Recently I am working with it) \r\n- Fix the problem: Sometimes double click the soruce snippet window will cause a dead loop.","package":"ccvext.vim","4":"ccvext.vim","src_id":"15959","5":"15959","creation_date":"1308826254","6":"1308826254"},{"0":"2943","vim_version":"7.0","1":"7.0","script_version":"4.3","2":"4.3","version_comment":"When tags file and cscope file not exist, auto remove it from config list.","3":"When tags file and cscope file not exist, auto remove it from config list.","package":"ccvext.vim","4":"ccvext.vim","src_id":"15943","5":"15943","creation_date":"1308636642","6":"1308636642"},{"0":"2943","vim_version":"7.0","1":"7.0","script_version":"4.2","2":"4.2","version_comment":"Descript:\r\n  - Don't search from tags when the text's lenght is equal to 1\r\n  - Don't search from tags when the text data is c\/c++ key word.\r\nBugFix:\r\n  - Fix the problem about double click in the main source window.\r\n","3":"Descript:\r\n  - Don't search from tags when the text's lenght is equal to 1\r\n  - Don't search from tags when the text data is c\/c++ key word.\r\nBugFix:\r\n  - Fix the problem about double click in the main source window.\r\n","package":"ccvext.vim","4":"ccvext.vim","src_id":"15847","5":"15847","creation_date":"1307678277","6":"1307678277"},{"0":"2943","vim_version":"7.0","1":"7.0","script_version":"4.1","2":"4.1","version_comment":"Update the prompt when tags not found.","3":"Update the prompt when tags not found.","package":"ccvext.vim","4":"ccvext.vim","src_id":"15846","5":"15846","creation_date":"1307667970","6":"1307667970"},{"0":"2943","vim_version":"7.0","1":"7.0","script_version":"4.0","2":"4.0","version_comment":"1. Fix some bug in the old script, and add some new function in gvim. \r\n2. Add command EnQuickSnippet and DiquickSnippet. This is a better way to use ctags, Now vim is working pretty like sourceinside, specially on windows givm. ","3":"1. Fix some bug in the old script, and add some new function in gvim. \r\n2. Add command EnQuickSnippet and DiquickSnippet. This is a better way to use ctags, Now vim is working pretty like sourceinside, specially on windows givm. ","package":"ccvext.vim","4":"ccvext.vim","src_id":"15813","5":"15813","creation_date":"1307270735","6":"1307270735"}]},"2942":{"script_id":"2942","0":"2942","script_name":"Ruby\/Sinatra","1":"Ruby\/Sinatra","script_type":"syntax","2":"syntax","summary":"Syntax highlight for Ruby\/Sinatra micro-framework","3":"Syntax highlight for Ruby\/Sinatra micro-framework","description":"Vim support for syntax highlight and snippets that helper coding\r\napplications based in Ruby\/Sinatra micro-framework.\r\n\r\nThe snippets are written with base the SnipMate #2540 plugin.\r\n\r\nYou maybe contributes to source. So, send a feedback in issue tracker (http:\/\/github.com\/hallison\/vim-ruby-sinatra\/issues).\r\n\r\nVim-Ruby\/Sinatra is hosted on following servers:\r\n\r\n-- Github (http:\/\/github.com\/hallison\/vim-ruby-sinatra)\r\n-- Codaset (http:\/\/codaset.com\/hallison\/vim-ruby-sinatra\/issues)\r\n\r\nCopyright (C) 2010 Hallison Batista <email@hallisonbatista.com>\r\n","4":"Vim support for syntax highlight and snippets that helper coding\r\napplications based in Ruby\/Sinatra micro-framework.\r\n\r\nThe snippets are written with base the SnipMate #2540 plugin.\r\n\r\nYou maybe contributes to source. So, send a feedback in issue tracker (http:\/\/github.com\/hallison\/vim-ruby-sinatra\/issues).\r\n\r\nVim-Ruby\/Sinatra is hosted on following servers:\r\n\r\n-- Github (http:\/\/github.com\/hallison\/vim-ruby-sinatra)\r\n-- Codaset (http:\/\/codaset.com\/hallison\/vim-ruby-sinatra\/issues)\r\n\r\nCopyright (C) 2010 Hallison Batista <email@hallisonbatista.com>\r\n","install_details":"Download the gzipball and open the package using Vim. Use the command `:source %`. Or run the following command:\r\n\r\n$ vim ruby-sinatra-<version>.vba.gz +\":source %\"\r\n\r\nDone! All files will be extracted in your Vim home directory.\r\n","5":"Download the gzipball and open the package using Vim. Use the command `:source %`. Or run the following command:\r\n\r\n$ vim ruby-sinatra-<version>.vba.gz +\":source %\"\r\n\r\nDone! All files will be extracted in your Vim home directory.\r\n","first_name":"Hallison","6":"Hallison","last_name":"Batista","7":"Batista","releases":[{"0":"2942","vim_version":"6.0","1":"6.0","script_version":"0.2.0","2":"0.2.0","version_comment":"* Updates in tasks to make the manifest file.\r\n* Removed unnecessary files.\r\n* Small improvements.\r\n* Fixes in the syntax detection.","3":"* Updates in tasks to make the manifest file.\r\n* Removed unnecessary files.\r\n* Small improvements.\r\n* Fixes in the syntax detection.","package":"ruby-sinatra-0.2.0.vba.gz","4":"ruby-sinatra-0.2.0.vba.gz","src_id":"12222","5":"12222","creation_date":"1264746210","6":"1264746210"},{"0":"2942","vim_version":"6.0","1":"6.0","script_version":"0.1.0","2":"0.1.0","version_comment":"Initial upload","3":"Initial upload","package":"ruby-sinatra-0.1.0.vba.gz","4":"ruby-sinatra-0.1.0.vba.gz","src_id":"12169","5":"12169","creation_date":"1264296044","6":"1264296044"}]},"2941":{"script_id":"2941","0":"2941","script_name":"actionscript3id.vim","1":"actionscript3id.vim","script_type":"syntax","2":"syntax","summary":"vim syntax highlight identifiers of actionscript 3","3":"vim syntax highlight identifiers of actionscript 3","description":"All identifiers are mined from the documentations of flex 4 sdk.\r\nThere are 8 groups: Flex Interfaces, Flex Classes, Flex Constants, Flex Functions and those only available in AIR runtime.","4":"All identifiers are mined from the documentations of flex 4 sdk.\r\nThere are 8 groups: Flex Interfaces, Flex Classes, Flex Constants, Flex Functions and those only available in AIR runtime.","install_details":"Throwing it into you \\\\\\\"syntax\\\\\\\" directory\r\nThen adding this line to your syntax\/actionscript.vim\r\n\r\nruntime! syntax\/actionscriptid.vim\r\n","5":"Throwing it into you \\\\\\\"syntax\\\\\\\" directory\r\nThen adding this line to your syntax\/actionscript.vim\r\n\r\nruntime! syntax\/actionscriptid.vim\r\n","first_name":"Zhenliang","6":"Zhenliang","last_name":"Ju","7":"Ju","releases":[{"0":"2941","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"actionscriptid.vim","4":"actionscriptid.vim","src_id":"12168","5":"12168","creation_date":"1264264229","6":"1264264229"}]},"2940":{"script_id":"2940","0":"2940","script_name":"vim-addon-mw-utils","1":"vim-addon-mw-utils","script_type":"utility","2":"utility","summary":"some utilities I wrote","3":"some utilities I wrote","description":"* cached file contents\r\n  get some information from files and cache the result.\r\n  Reparse the file when it has changed automatically.\r\n\r\n* tiny-cmd : Never get the \"Press ENTER or type command to continue\"\r\n   message again\r\n\r\n* funcref:\r\n  - poor man's closures for Vim.\r\n  - Create function objects calling autoload function without sourcing that file\r\n  - (be lazy, do the work when it has to be done)\r\n  - get rid of the \"Use upper case letters for custom functions\" annoyance\r\n\r\n   Example:\r\n  let myFun = funcref#Function(\"return ARGS[0]\")\r\n  let result = funcref#Call(myFun, [2])\r\n\r\n  let myFun2 =  funcref#Function(\"foo#bar#Baz\")\r\n  \r\n  \" pass arguments (kind of simple closure):\r\n  let myFun2 =  funcref#Function(\"return ARGS\", {args: [1]} )\r\n  echo funcref#Call(myFun, [2])\r\n\r\n  echoes [1,2]\r\n\r\n  \" bind function to an object:\r\n  let myFun2 =  funcref#Function(\"return SELF.myvalue\", {self: {\"a\": \"myvalue\"} } )\r\n\r\netc..\r\n\r\nThis library is used by many of my plugins\r\n\r\nIf something doesn't work it's a bug. So tell me to fix it!\r\n\r\nReuse this code if you like it!","4":"* cached file contents\r\n  get some information from files and cache the result.\r\n  Reparse the file when it has changed automatically.\r\n\r\n* tiny-cmd : Never get the \"Press ENTER or type command to continue\"\r\n   message again\r\n\r\n* funcref:\r\n  - poor man's closures for Vim.\r\n  - Create function objects calling autoload function without sourcing that file\r\n  - (be lazy, do the work when it has to be done)\r\n  - get rid of the \"Use upper case letters for custom functions\" annoyance\r\n\r\n   Example:\r\n  let myFun = funcref#Function(\"return ARGS[0]\")\r\n  let result = funcref#Call(myFun, [2])\r\n\r\n  let myFun2 =  funcref#Function(\"foo#bar#Baz\")\r\n  \r\n  \" pass arguments (kind of simple closure):\r\n  let myFun2 =  funcref#Function(\"return ARGS\", {args: [1]} )\r\n  echo funcref#Call(myFun, [2])\r\n\r\n  echoes [1,2]\r\n\r\n  \" bind function to an object:\r\n  let myFun2 =  funcref#Function(\"return SELF.myvalue\", {self: {\"a\": \"myvalue\"} } )\r\n\r\netc..\r\n\r\nThis library is used by many of my plugins\r\n\r\nIf something doesn't work it's a bug. So tell me to fix it!\r\n\r\nReuse this code if you like it!","install_details":"git repo: http:\/\/github.com\/MarcWeber\/vim-addon-mw-utils\r\n\r\nI recommend using the vim-addon-manager to install this plugin.\r\n-> http:\/\/www.vim.org\/scripts\/script.php?script_id=2905\r\n\r\nPut this into your .vimrc and be done:\r\ncall scriptmanager#Activate([\"vim-addon-mw-utils\"])","5":"git repo: http:\/\/github.com\/MarcWeber\/vim-addon-mw-utils\r\n\r\nI recommend using the vim-addon-manager to install this plugin.\r\n-> http:\/\/www.vim.org\/scripts\/script.php?script_id=2905\r\n\r\nPut this into your .vimrc and be done:\r\ncall scriptmanager#Activate([\"vim-addon-mw-utils\"])","first_name":"Marc","6":"Marc","last_name":"Weber","7":"Weber","releases":[{"0":"2940","vim_version":"7.2","1":"7.2","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"vim-addon-mw-utils.zip","4":"vim-addon-mw-utils.zip","src_id":"12159","5":"12159","creation_date":"1264163881","6":"1264163881"}]},"2939":{"script_id":"2939","0":"2939","script_name":"strawimodo","1":"strawimodo","script_type":"color scheme","2":"color scheme","summary":"GUI-only - colorful but sane","3":"GUI-only - colorful but sane","description":"That's my first theme loosely based on railscasts.vim. It's GUI-only.\r\n\r\nScreenshots:\r\n\r\nhttp:\/\/mhinz.spline.de\/strawimodo1.png\r\nhttp:\/\/mhinz.spline.de\/strawimodo2.png\r\n\r\n","4":"That's my first theme loosely based on railscasts.vim. It's GUI-only.\r\n\r\nScreenshots:\r\n\r\nhttp:\/\/mhinz.spline.de\/strawimodo1.png\r\nhttp:\/\/mhinz.spline.de\/strawimodo2.png\r\n\r\n","install_details":"Just copy it to your ~\/.vim\/colors\/ and use it by executing \":colo strawimodo\"","5":"Just copy it to your ~\/.vim\/colors\/ and use it by executing \":colo strawimodo\"","first_name":"Marco","6":"Marco","last_name":"H.","7":"H.","releases":[{"0":"2939","vim_version":"7.0","1":"7.0","script_version":"0.3","2":"0.3","version_comment":"Initial upload","3":"Initial upload","package":"strawimodo.vim","4":"strawimodo.vim","src_id":"12157","5":"12157","creation_date":"1264122900","6":"1264122900"}]},"2938":{"script_id":"2938","0":"2938","script_name":"Multi-Replace","1":"Multi-Replace","script_type":"utility","2":"utility","summary":"Perfom non-cumulative multi-replace","3":"Perfom non-cumulative multi-replace","description":"This script provides several functions to do multiple-string replacements.\r\n\r\nThe quick brown fox jumped over the six lazy dogs.\r\nreplace (dogs=fox, fox=dogs, x=ck) will give\r\nThe quick brown dogs jumped over the sick lazy fox.\r\n\r\nNote that values are non-cumulative and longest-string-first, which is why\r\n\"x=ck\" does not interfere with \"dogs=fox\" or \"fox=dogs\" replacements.\r\nThis can be used to specify exceptions in a replacement list. \r\n\r\nTypical uses: \r\n- Replacing variable names (eg code localization \/ code reuse)\r\n- Replacing keywords with translations\r\n- Generating code from a template\r\n- Swapping keywords\r\n  etc\r\n\r\nIts main function is provided  by the MultiReplace function, which performs\r\nnon-cumulative replacements, replacing occurrences of hash keys with their corresponding hash values. Hash values may be arrays, in which case values are rotated across the lines containing the key value. Range of lines to replace may also be specified.\r\n\r\nMultiReplace(dict, from, to)\r\n\r\nSeveral functions that create the \"dict\" hash are also provided.\r\n\r\n1) Read values from prompt\r\nMultiReplace(ReadUserlist(), 1,  \"$\")\r\n\r\n2) Replacement dictionary\r\nA buffer may be also specified. A replacement list buffer will contain TAB separated pairs, with the string to find on the left and the string to replace with on the right. Such a replacement would be invoked with\r\n\r\nMultiReplace(ReadDictionary(\"#\"), 1, \"$\")\r\n\r\nWhere the \"#\" here refers to the alternate buffer:\r\nReadDictionary(buffer)\r\n\r\n3) Look up table \r\nA buffer containing delimiter-separated values my also be used. To use a csv that does not contain quote marks (ie, no quotes and no values with linebreaks), and replace all occurrences from column 1 with values from column 4:\r\n\r\nMultiReplace(ReadColumns(\"#\", \",\", 1, 4), 1, \"$\")\r\n\r\nReadColumns is defined as\r\nReadColumns(buffer, sep, keycol, valcol)\r\n\r\nMappings\r\nThe following mappings are included in the file. This allows you to select a range of text, enter \",rem\" and then enter \"=\" and specify find=replace pairs for a quick replacement.\r\n\r\n:map ,rem :call MultiReplace(\"\",1,\"$\")\r\n:vmap ,rem :call MultiReplace(\"\",line(\"'<\"),line(\"'>\"))\r\n\r\n\r\n\r\n\r\n","4":"This script provides several functions to do multiple-string replacements.\r\n\r\nThe quick brown fox jumped over the six lazy dogs.\r\nreplace (dogs=fox, fox=dogs, x=ck) will give\r\nThe quick brown dogs jumped over the sick lazy fox.\r\n\r\nNote that values are non-cumulative and longest-string-first, which is why\r\n\"x=ck\" does not interfere with \"dogs=fox\" or \"fox=dogs\" replacements.\r\nThis can be used to specify exceptions in a replacement list. \r\n\r\nTypical uses: \r\n- Replacing variable names (eg code localization \/ code reuse)\r\n- Replacing keywords with translations\r\n- Generating code from a template\r\n- Swapping keywords\r\n  etc\r\n\r\nIts main function is provided  by the MultiReplace function, which performs\r\nnon-cumulative replacements, replacing occurrences of hash keys with their corresponding hash values. Hash values may be arrays, in which case values are rotated across the lines containing the key value. Range of lines to replace may also be specified.\r\n\r\nMultiReplace(dict, from, to)\r\n\r\nSeveral functions that create the \"dict\" hash are also provided.\r\n\r\n1) Read values from prompt\r\nMultiReplace(ReadUserlist(), 1,  \"$\")\r\n\r\n2) Replacement dictionary\r\nA buffer may be also specified. A replacement list buffer will contain TAB separated pairs, with the string to find on the left and the string to replace with on the right. Such a replacement would be invoked with\r\n\r\nMultiReplace(ReadDictionary(\"#\"), 1, \"$\")\r\n\r\nWhere the \"#\" here refers to the alternate buffer:\r\nReadDictionary(buffer)\r\n\r\n3) Look up table \r\nA buffer containing delimiter-separated values my also be used. To use a csv that does not contain quote marks (ie, no quotes and no values with linebreaks), and replace all occurrences from column 1 with values from column 4:\r\n\r\nMultiReplace(ReadColumns(\"#\", \",\", 1, 4), 1, \"$\")\r\n\r\nReadColumns is defined as\r\nReadColumns(buffer, sep, keycol, valcol)\r\n\r\nMappings\r\nThe following mappings are included in the file. This allows you to select a range of text, enter \",rem\" and then enter \"=\" and specify find=replace pairs for a quick replacement.\r\n\r\n:map ,rem :call MultiReplace(\"\",1,\"$\")\r\n:vmap ,rem :call MultiReplace(\"\",line(\"'<\"),line(\"'>\"))\r\n\r\n\r\n\r\n\r\n","install_details":"Insert contents into your vimrc file.","5":"Insert contents into your vimrc file.","first_name":"eiji","6":"eiji","last_name":"kumiai","7":"kumiai","releases":[{"0":"2938","vim_version":"7.0","1":"7.0","script_version":"1.1","2":"1.1","version_comment":"Fixed problem with \"N\" becoming \"n\" when in ignorecase mode.","3":"Fixed problem with \"N\" becoming \"n\" when in ignorecase mode.","package":"multireplace.vim","4":"multireplace.vim","src_id":"12304","5":"12304","creation_date":"1265298827","6":"1265298827"},{"0":"2938","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"multireplace.vim","4":"multireplace.vim","src_id":"12156","5":"12156","creation_date":"1264117442","6":"1264117442"}]},"2937":{"script_id":"2937","0":"2937","script_name":"hexHighlight.vim","1":"hexHighlight.vim","script_type":"utility","2":"utility","summary":"Plugin to highlight hex codes in gvim.","3":"Plugin to highlight hex codes in gvim.","description":"This plugin looks for hex codes of the format #ffffff or #fff and toggles a highlight in that color. It is useful for editing colorschemes, and generally any config file dealing with colors.\r\n\r\nOnly works with the graphical version of vim.","4":"This plugin looks for hex codes of the format #ffffff or #fff and toggles a highlight in that color. It is useful for editing colorschemes, and generally any config file dealing with colors.\r\n\r\nOnly works with the graphical version of vim.","install_details":"Put hexHighlight.vim into your .vim\/plugins directory, or simply :source the file.\r\n\r\nThe default keymapping to toggle hex code highlighting is <Leader>F2, and the default <Leader> bind is \"\\\", so \\F2 should work by default.\r\n\r\nThe toggle can be called manually by :call HexHighlight()","5":"Put hexHighlight.vim into your .vim\/plugins directory, or simply :source the file.\r\n\r\nThe default keymapping to toggle hex code highlighting is <Leader>F2, and the default <Leader> bind is \"\\\", so \\F2 should work by default.\r\n\r\nThe toggle can be called manually by :call HexHighlight()","first_name":"Yuri","6":"Yuri","last_name":"Feldman","7":"Feldman","releases":[{"0":"2937","vim_version":"7.2","1":"7.2","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"hexHighlight.vim","4":"hexHighlight.vim","src_id":"12150","5":"12150","creation_date":"1264060866","6":"1264060866"}]},"2936":{"script_id":"2936","0":"2936","script_name":"bzr-commit","1":"bzr-commit","script_type":"utility","2":"utility","summary":"Commit bazaar using splited view (diff, status and commit comment)","3":"Commit bazaar using splited view (diff, status and commit comment)","description":"This bash script open a vim instance showing diff, status and an editable comment buffer for you commit message.","4":"This bash script open a vim instance showing diff, status and an editable comment buffer for you commit message.","install_details":"put bzr-commit.sh in ~\/bin\/\r\nthen:\r\n$ chmod +x ~\/bin\/bzr-commit.sh\r\nuse by invoking \r\n$ bzr-commit.sh","5":"put bzr-commit.sh in ~\/bin\/\r\nthen:\r\n$ chmod +x ~\/bin\/bzr-commit.sh\r\nuse by invoking \r\n$ bzr-commit.sh","first_name":"Louis","6":"Louis","last_name":"Lynch","7":"Lynch","releases":[{"0":"2936","vim_version":"7.2","1":"7.2","script_version":"7.2","2":"7.2","version_comment":"Initial upload","3":"Initial upload","package":"bzr-commit.sh","4":"bzr-commit.sh","src_id":"12141","5":"12141","creation_date":"1264020085","6":"1264020085"}]},"2935":{"script_id":"2935","0":"2935","script_name":"superSnipMate","1":"superSnipMate","script_type":"ftplugin","2":"ftplugin","summary":"improved from snipMate with which you can expand your snippet within another","3":"improved from snipMate with which you can expand your snippet within another","description":"developed from snipMate \r\n\r\nMy email: gm.chaochao@gmail.com","4":"developed from snipMate \r\n\r\nMy email: gm.chaochao@gmail.com","install_details":"","5":"","first_name":"\u738b","6":"王","last_name":"\u52bf\u8d85","7":"势超","releases":[{"0":"2935","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"superSnipMate.tar.gz","4":"superSnipMate.tar.gz","src_id":"12136","5":"12136","creation_date":"1264012399","6":"1264012399"}]},"2934":{"script_id":"2934","0":"2934","script_name":"vim-addon-actions","1":"vim-addon-actions","script_type":"utility","2":"utility","summary":"keep list of actions you can bind to shortcuts easily on demand","3":"keep list of actions you can bind to shortcuts easily on demand","description":"Press <s-FX> to map an action to the FX key where X is one of 2,3,4 ..\r\nThis action can be\r\n* run last command\r\n* run make\r\n* ....\r\n\r\nAlternatively you can set an action which is run whenever you write a buffer:\r\nSetActionOnBufWrite\r\n\r\nThis plugin can be reused by many IDE like plugins (eg my vim-addon-fcsh does so)\r\n\r\nI got two bad ratings. Would you consider sending me a note why you think it's that bad?","4":"Press <s-FX> to map an action to the FX key where X is one of 2,3,4 ..\r\nThis action can be\r\n* run last command\r\n* run make\r\n* ....\r\n\r\nAlternatively you can set an action which is run whenever you write a buffer:\r\nSetActionOnBufWrite\r\n\r\nThis plugin can be reused by many IDE like plugins (eg my vim-addon-fcsh does so)\r\n\r\nI got two bad ratings. Would you consider sending me a note why you think it's that bad?","install_details":"recommended way of installation:\r\nUse vim-addon-manager http:\/\/www.vim.org\/scripts\/script.php?script_id=2905\r\n\r\ngit repo: http:\/\/github.com\/MarcWeber\/vim-addon-actions","5":"recommended way of installation:\r\nUse vim-addon-manager http:\/\/www.vim.org\/scripts\/script.php?script_id=2905\r\n\r\ngit repo: http:\/\/github.com\/MarcWeber\/vim-addon-actions","first_name":"Marc","6":"Marc","last_name":"Weber","7":"Weber","releases":[{"0":"2934","vim_version":"7.0","1":"7.0","script_version":"0.2.2","2":"0.2.2","version_comment":"bugfix au! ActionOnBufWrite[!] didn't remove the old autocommand previously","3":"bugfix au! ActionOnBufWrite[!] didn't remove the old autocommand previously","package":"vim-addon-actions-0.2.2.zip","4":"vim-addon-actions-0.2.2.zip","src_id":"13767","5":"13767","creation_date":"1283778918","6":"1283778918"},{"0":"2934","vim_version":"7.0","1":"7.0","script_version":"0.2.1","2":"0.2.1","version_comment":"ActionOnBufWrite*: supporting bang patterns","3":"ActionOnBufWrite*: supporting bang patterns","package":"vim-addon-actions-0.2.1.zip","4":"vim-addon-actions-0.2.1.zip","src_id":"13585","5":"13585","creation_date":"1281950858","6":"1281950858"},{"0":"2934","vim_version":"7.0","1":"7.0","script_version":"0.2","2":"0.2","version_comment":"updates and fixes","3":"updates and fixes","package":"vim-addon-actions-0.2.zip","4":"vim-addon-actions-0.2.zip","src_id":"13202","5":"13202","creation_date":"1276747915","6":"1276747915"},{"0":"2934","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"vim-addon-actions.zip","4":"vim-addon-actions.zip","src_id":"12133","5":"12133","creation_date":"1263997777","6":"1263997777"}]},"2933":{"script_id":"2933","0":"2933","script_name":"vim-addon-fcsh","1":"vim-addon-fcsh","script_type":"utility","2":"utility","summary":"run adobe fcsh Flex compiler shell in background decreasing compilation times","3":"run adobe fcsh Flex compiler shell in background decreasing compilation times","description":"There is a Flex SDK for Linux. The complier is written in Java and has a long start time.\r\nTo increase speed there is the fcsh (flex compiler shell). You compile once and everything will be kept in memory. This plugin runs fcsh for you so that you can get fcsh compilation failures in your quickfix window.\r\n\r\nEnjoy!","4":"There is a Flex SDK for Linux. The complier is written in Java and has a long start time.\r\nTo increase speed there is the fcsh (flex compiler shell). You compile once and everything will be kept in memory. This plugin runs fcsh for you so that you can get fcsh compilation failures in your quickfix window.\r\n\r\nEnjoy!","install_details":"Recommended way of installation:\r\nhttp:\/\/www.vim.org\/scripts\/script.php?script_id=2905\r\n\r\nIf you install this plugin manually you also have to get the dependencies listed in the info file manually.\r\n\r\ngit repository:\r\nhttp:\/\/github.com\/MarcWeber\/vim-addon-fcsh","5":"Recommended way of installation:\r\nhttp:\/\/www.vim.org\/scripts\/script.php?script_id=2905\r\n\r\nIf you install this plugin manually you also have to get the dependencies listed in the info file manually.\r\n\r\ngit repository:\r\nhttp:\/\/github.com\/MarcWeber\/vim-addon-fcsh","first_name":"Marc","6":"Marc","last_name":"Weber","7":"Weber","releases":[{"0":"2933","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"bug-fix. dependencies are found automatically now","3":"bug-fix. dependencies are found automatically now","package":"vim-addon-fcsh.zip","4":"vim-addon-fcsh.zip","src_id":"12206","5":"12206","creation_date":"1264682265","6":"1264682265"}]},"2932":{"script_id":"2932","0":"2932","script_name":"histwin.vim","1":"histwin.vim","script_type":"utility","2":"utility","summary":"Browse the undo tree","3":"Browse the undo tree","description":"PLEASE RATE THIS PLUGIN, IF YOU LIKE IT!\r\n\r\nFeedback is always welcome. See :h histwin-feedback.\r\n\r\nYou can now follow development of this plugin via github: http:\/\/github.com\/chrisbra\/histwin.vim\r\n\r\nVim 7 has an amazing feature that is called undo-branches. See :h undo-tree. Unfortunalley it is a little bit clumsy to use. \r\n\r\nTherefore this plugin allows for easy navigation between the different undo-branches for a file.\r\nSee this screenshot: http:\/\/www.256bit.org\/~chrisbra\/vim_undotree.png\r\nThis plugin was inspired by the undo_branches plugin (http:\/\/www.vim.org\/scripts\/script.php?script_id=1997).\r\n\r\nThis plugin allows you to\r\n- see all available undo-branches (Timestamps and Keywords)\r\n- tag certain states\r\n- switching to different states (including the first state (before any changes were made)\r\n- allow to diff the selected undo-branch with the current version\r\n- replay the changes (ok, this is just for fun ;)\r\n\r\nOpen the UndoBrowse window by issuing :UB\r\nA new window will appear, which contains the name of the file you are watching a small help\r\nbanner that contains the most important mappings for this window and a list of all available\r\nundo-branches (which shows the time when this change was made and your tags for that state, if there are any). On each entry you can press Enter or T to jump to that state or tag that state.\r\n\r\nThis plugin maps the following keys:\r\n- 'Enter' on an entry jump to that state in time of the file\r\n- 'T' tags a state with a phrase. \r\n- 'R' lets you replay a change \r\n- 'I' opens\/closes the help banner\r\n- 'Q' closes the window\r\n- CTRL-L reload view\r\n- D diff selected version","4":"PLEASE RATE THIS PLUGIN, IF YOU LIKE IT!\r\n\r\nFeedback is always welcome. See :h histwin-feedback.\r\n\r\nYou can now follow development of this plugin via github: http:\/\/github.com\/chrisbra\/histwin.vim\r\n\r\nVim 7 has an amazing feature that is called undo-branches. See :h undo-tree. Unfortunalley it is a little bit clumsy to use. \r\n\r\nTherefore this plugin allows for easy navigation between the different undo-branches for a file.\r\nSee this screenshot: http:\/\/www.256bit.org\/~chrisbra\/vim_undotree.png\r\nThis plugin was inspired by the undo_branches plugin (http:\/\/www.vim.org\/scripts\/script.php?script_id=1997).\r\n\r\nThis plugin allows you to\r\n- see all available undo-branches (Timestamps and Keywords)\r\n- tag certain states\r\n- switching to different states (including the first state (before any changes were made)\r\n- allow to diff the selected undo-branch with the current version\r\n- replay the changes (ok, this is just for fun ;)\r\n\r\nOpen the UndoBrowse window by issuing :UB\r\nA new window will appear, which contains the name of the file you are watching a small help\r\nbanner that contains the most important mappings for this window and a list of all available\r\nundo-branches (which shows the time when this change was made and your tags for that state, if there are any). On each entry you can press Enter or T to jump to that state or tag that state.\r\n\r\nThis plugin maps the following keys:\r\n- 'Enter' on an entry jump to that state in time of the file\r\n- 'T' tags a state with a phrase. \r\n- 'R' lets you replay a change \r\n- 'I' opens\/closes the help banner\r\n- 'Q' closes the window\r\n- CTRL-L reload view\r\n- D diff selected version","install_details":"edit the file histwin.vba with vim. From within vim simply load this file:\r\n:so %\r\n\r\nVim will automatically install this plugin.","5":"edit the file histwin.vba with vim. From within vim simply load this file:\r\n:so %\r\n\r\nVim will automatically install this plugin.","first_name":"Christian","6":"Christian","last_name":"Brabandt","7":"Brabandt","releases":[{"0":"2932","vim_version":"7.3","1":"7.3","script_version":"24","2":"24","version_comment":"- prevent loading of autoload script too early (reported by Sergey Khorev, thanks!)\n- apply &fenc setting before writing file for diff (patch by Ben Fritz, thanks!)\n(automatically uploaded)","3":"- prevent loading of autoload script too early (reported by Sergey Khorev, thanks!)\n- apply &fenc setting before writing file for diff (patch by Ben Fritz, thanks!)\n(automatically uploaded)","package":"histwin-0.24.vba","4":"histwin-0.24.vba","src_id":"19529","5":"19529","creation_date":"1361053435","6":"1361053435"},{"0":"2932","vim_version":"7.3","1":"7.3","script_version":"25","2":"25","version_comment":"fix issue 2 from github https:\/\/github.com\/chrisbra\/histwin\/issues\/2\n(When 'splitright' is set, Diffing a previous undo branch separates the window layout, reported by bootleq, thanks!)\n(automatically uploaded)","3":"fix issue 2 from github https:\/\/github.com\/chrisbra\/histwin\/issues\/2\n(When 'splitright' is set, Diffing a previous undo branch separates the window layout, reported by bootleq, thanks!)\n(automatically uploaded)","package":"histwin-0.25.vba","4":"histwin-0.25.vba","src_id":"16266","5":"16266","creation_date":"1313431263","6":"1313431263"},{"0":"2932","vim_version":"7.3","1":"7.3","script_version":"24","2":"24","version_comment":":ID is already defined by the visincr plugin, instead use the command :HistID, also a wrong error message is fixed\n(automatically uploaded)","3":":ID is already defined by the visincr plugin, instead use the command :HistID, also a wrong error message is fixed\n(automatically uploaded)","package":"histwin-0.24.vba","4":"histwin-0.24.vba","src_id":"16181","5":"16181","creation_date":"1312264221","6":"1312264221"},{"0":"2932","vim_version":"7.3","1":"7.3","script_version":"23","2":"23","version_comment":"Purge Undo history with \"X\"\n(automatically uploaded)","3":"Purge Undo history with \"X\"\n(automatically uploaded)","package":"histwin-0.23.vba","4":"histwin-0.23.vba","src_id":"16173","5":"16173","creation_date":"1312032960","6":"1312032960"},{"0":"2932","vim_version":"7.3","1":"7.3","script_version":"22","2":"22","version_comment":"- Display signs for changed lines\n- |:ID|\n- small code improvements\n(automatically uploaded)","3":"- Display signs for changed lines\n- |:ID|\n- small code improvements\n(automatically uploaded)","package":"histwin-0.22.vba","4":"histwin-0.22.vba","src_id":"16158","5":"16158","creation_date":"1311804113","6":"1311804113"},{"0":"2932","vim_version":"7.3","1":"7.3","script_version":"21","2":"21","version_comment":"- more standard like help files\n- make sure, the autoload script is only called when needed\n  (and not on startup)","3":"- more standard like help files\n- make sure, the autoload script is only called when needed\n  (and not on startup)","package":"histwin-0.21.vba","4":"histwin-0.21.vba","src_id":"14555","5":"14555","creation_date":"1292658940","6":"1292658940"},{"0":"2932","vim_version":"7.3","1":"7.3","script_version":"20","2":"20","version_comment":"-Enable storing the tags as Dicionary in .viminfo\n  (this might not work as expected, cause we are storing a nested\n  Dictionary)\n- Show a diff in the preview window when pressing P (or on autocommand\n  CursorHold if enabled)\n- a little bit code cleanup (as always ;))\n- correctly catch E830 and give an error message (reported by D.\n  Fishburn)\n(automatically uploaded)","3":"-Enable storing the tags as Dicionary in .viminfo\n  (this might not work as expected, cause we are storing a nested\n  Dictionary)\n- Show a diff in the preview window when pressing P (or on autocommand\n  CursorHold if enabled)\n- a little bit code cleanup (as always ;))\n- correctly catch E830 and give an error message (reported by D.\n  Fishburn)\n(automatically uploaded)","package":"histwin-0.20.vba","4":"histwin-0.20.vba","src_id":"14086","5":"14086","creation_date":"1287605953","6":"1287605953"},{"0":"2932","vim_version":"7.3","1":"7.3","script_version":"19","2":"19","version_comment":"Make sure the first entry will be tagged 'Start Editing'","3":"Make sure the first entry will be tagged 'Start Editing'","package":"histwin-0.19.vba","4":"histwin-0.19.vba","src_id":"14071","5":"14071","creation_date":"1287429211","6":"1287429211"},{"0":"2932","vim_version":"7.3","1":"7.3","script_version":"18","2":"18","version_comment":"don't leave the buffer in nomodifiable state (reported by D. Doran)","3":"don't leave the buffer in nomodifiable state (reported by D. Doran)","package":"histwin-0.18.vba","4":"histwin-0.18.vba","src_id":"14063","5":"14063","creation_date":"1287228007","6":"1287228007"},{"0":"2932","vim_version":"7.3","1":"7.3","script_version":"17","2":"17","version_comment":"the initial entry should be visible for Vim < 7.3.005","3":"the initial entry should be visible for Vim < 7.3.005","package":"histwin-0.17.vba","4":"histwin-0.17.vba","src_id":"14037","5":"14037","creation_date":"1286711774","6":"1286711774"},{"0":"2932","vim_version":"7.3","1":"7.3","script_version":"16","2":"16","version_comment":"-more bugfixing. :UB throws errors in Vim before 7.3.005 fix that","3":"-more bugfixing. :UB throws errors in Vim before 7.3.005 fix that","package":"histwin-0.16.vba","4":"histwin-0.16.vba","src_id":"14036","5":"14036","creation_date":"1286711140","6":"1286711140"},{"0":"2932","vim_version":"7.3","1":"7.3","script_version":"15","2":"15","version_comment":"Fixed bug when no undo-tree was available (partly by Ben Boeckel. Thanks!)\n-More error handling (when the cursor is not on a list item)\n-Commenting out the entry to store the histdict in a global variable, that should be written to the .viminfo file (but is not yet supported by plain vim)","3":"Fixed bug when no undo-tree was available (partly by Ben Boeckel. Thanks!)\n-More error handling (when the cursor is not on a list item)\n-Commenting out the entry to store the histdict in a global variable, that should be written to the .viminfo file (but is not yet supported by plain vim)","package":"histwin-0.15.vba","4":"histwin-0.15.vba","src_id":"14024","5":"14024","creation_date":"1286488844","6":"1286488844"},{"0":"2932","vim_version":"7.3","1":"7.3","script_version":"14","2":"14","version_comment":" (experimental version):\n- don't fix the width of the histwin window\n- now use the undotree() function by default (if patch 7.3.005 is\n  included)\n- display save states in the detailed view\n- display the 'rehash' when a state is not accessible anymore\n- fixed an annoying bug, that when jumping to a particular undo state,\n  the plugin would jump to the wrong state (I hate octal mode)\n- Make displaying the time much more reliable and also don't display\n  the time, if the change happened more than 24h ago (instead, display\n  the date, when this change was done).\n- slightly improved error handling.\n- prepare plugin, to permantly store the undotags in the viminfo file\n  (this isn't supported by a plain vanilla vim and requires a patch)\n- A major rewrite (code cleanup, better documentation)\n","3":" (experimental version):\n- don't fix the width of the histwin window\n- now use the undotree() function by default (if patch 7.3.005 is\n  included)\n- display save states in the detailed view\n- display the 'rehash' when a state is not accessible anymore\n- fixed an annoying bug, that when jumping to a particular undo state,\n  the plugin would jump to the wrong state (I hate octal mode)\n- Make displaying the time much more reliable and also don't display\n  the time, if the change happened more than 24h ago (instead, display\n  the date, when this change was done).\n- slightly improved error handling.\n- prepare plugin, to permantly store the undotags in the viminfo file\n  (this isn't supported by a plain vanilla vim and requires a patch)\n- A major rewrite (code cleanup, better documentation)\n","package":"histwin-0.14.vba","4":"histwin-0.14.vba","src_id":"13957","5":"13957","creation_date":"1285791436","6":"1285791436"},{"0":"2932","vim_version":"7.2","1":"7.2","script_version":"0.13","2":"0.13","version_comment":"- New version that uses Vim 7.3 persistent undo features |new-persistent-undo|\n- Display saved counter in detailed view\n- Display indicator for saved branches.\n- in diff mode, don't set the original buffer to be nomodifiable (so you can always merge chunks).\n- Check for Vim Version 7.3 (the plugin won't work with older versions of Vim)","3":"- New version that uses Vim 7.3 persistent undo features |new-persistent-undo|\n- Display saved counter in detailed view\n- Display indicator for saved branches.\n- in diff mode, don't set the original buffer to be nomodifiable (so you can always merge chunks).\n- Check for Vim Version 7.3 (the plugin won't work with older versions of Vim)","package":"histwin-0.13.vba","4":"histwin-0.13.vba","src_id":"13734","5":"13734","creation_date":"1283256443","6":"1283256443"},{"0":"2932","vim_version":"7.0","1":"7.0","script_version":"0.12","2":"0.12","version_comment":"- Small extension to the help file\r\n- generate help file with 'et' set, so the README at github looks better\r\n- Highlight the key binding using |hl-SpecialKey|\r\n- The help tag for the color configuration was wrong.","3":"- Small extension to the help file\r\n- generate help file with 'et' set, so the README at github looks better\r\n- Highlight the key binding using |hl-SpecialKey|\r\n- The help tag for the color configuration was wrong.","package":"histwin-0.12.vba","4":"histwin-0.12.vba","src_id":"12944","5":"12944","creation_date":"1273005854","6":"1273005854"},{"0":"2932","vim_version":"7.0","1":"7.0","script_version":"0.11","2":"0.11","version_comment":"- Set old buffers read only (disable the setting via the g:undo_tree_nomod variable\r\n- Make sure, Warning Messages are really displayed using :unsilent","3":"- Set old buffers read only (disable the setting via the g:undo_tree_nomod variable\r\n- Make sure, Warning Messages are really displayed using :unsilent","package":"histwin.vba","4":"histwin.vba","src_id":"12883","5":"12883","creation_date":"1271878267","6":"1271878267"},{"0":"2932","vim_version":"7.0","1":"7.0","script_version":"0.10","2":"0.10","version_comment":"- Fixed annoying Resizing bug\r\n- linebreak tags, if they are too long\r\n- dynamically grow the histwin window, for longer tags (up\r\n   to a maximum)\r\n- Bugfix: Always indicate the correct branch\r\n- Added a few try\/catch statements and some error handling","3":"- Fixed annoying Resizing bug\r\n- linebreak tags, if they are too long\r\n- dynamically grow the histwin window, for longer tags (up\r\n   to a maximum)\r\n- Bugfix: Always indicate the correct branch\r\n- Added a few try\/catch statements and some error handling","package":"histwin.vba","4":"histwin.vba","src_id":"12878","5":"12878","creation_date":"1271797716","6":"1271797716"},{"0":"2932","vim_version":"7.0","1":"7.0","script_version":"0.9","2":"0.9","version_comment":"BF: Error handling for Replaying (it may not work always)\r\nNF: Finally added Documentation (see :h histwin.txt)\r\nBF: Use syntax highlighting\r\nBF: Tagging finally works (you can now tag additional states)\r\n","3":"BF: Error handling for Replaying (it may not work always)\r\nNF: Finally added Documentation (see :h histwin.txt)\r\nBF: Use syntax highlighting\r\nBF: Tagging finally works (you can now tag additional states)\r\n","package":"histwin.vba","4":"histwin.vba","src_id":"12202","5":"12202","creation_date":"1264633898","6":"1264633898"},{"0":"2932","vim_version":"7.0","1":"7.0","script_version":"0.8","2":"0.8","version_comment":"- NF: make speed of the replay adjustable. Use g:undo_tree_speed to set time in milliseconds\r\n- BF: code cleanup\r\n- BF: highlighting should work better now.\r\n","3":"- NF: make speed of the replay adjustable. Use g:undo_tree_speed to set time in milliseconds\r\n- BF: code cleanup\r\n- BF: highlighting should work better now.\r\n","package":"histwin.vba","4":"histwin.vba","src_id":"12155","5":"12155","creation_date":"1264113604","6":"1264113604"},{"0":"2932","vim_version":"7.0","1":"7.0","script_version":"0.7.2.","2":"0.7.2.","version_comment":"- BF: Check undolevel Settings\r\n- BF: make sure when switching to a different undo branch, that the undo-tree will be updated","3":"- BF: Check undolevel Settings\r\n- BF: make sure when switching to a different undo branch, that the undo-tree will be updated","package":"histwin.vba","4":"histwin.vba","src_id":"12146","5":"12146","creation_date":"1264028787","6":"1264028787"},{"0":"2932","vim_version":"7.0","1":"7.0","script_version":"0.7.1","2":"0.7.1","version_comment":"BF: fixed a problem with mapping the keys which broke the Undo-Tree keys (I guess I don't fully understand, when to use s: and <sid>)","3":"BF: fixed a problem with mapping the keys which broke the Undo-Tree keys (I guess I don't fully understand, when to use s: and <sid>)","package":"histwin.vba","4":"histwin.vba","src_id":"12145","5":"12145","creation_date":"1264026896","6":"1264026896"},{"0":"2932","vim_version":"7.0","1":"7.0","script_version":"0.7","2":"0.7","version_comment":"- NF: created autoloadPlugin (patch by Charles Campbell) Thanks!\r\n- NF: enabled GLVS (patch by Charles Campbell) Thanks!\r\n- NF: made Plugin available as histwin.vba\r\n- NF: Check for availability of :UB before defining it\r\n- BF: cleaned up old comments\r\n- BF: deleted :noautocmd which could cause trouble with other plugins\r\n- BF: small changes in coding style (<sid> to s:, fun instead of fu)","3":"- NF: created autoloadPlugin (patch by Charles Campbell) Thanks!\r\n- NF: enabled GLVS (patch by Charles Campbell) Thanks!\r\n- NF: made Plugin available as histwin.vba\r\n- NF: Check for availability of :UB before defining it\r\n- BF: cleaned up old comments\r\n- BF: deleted :noautocmd which could cause trouble with other plugins\r\n- BF: small changes in coding style (<sid> to s:, fun instead of fu)","package":"histwin.vba","4":"histwin.vba","src_id":"12144","5":"12144","creation_date":"1264025403","6":"1264025403"},{"0":"2932","vim_version":"7.0","1":"7.0","script_version":"0.6","2":"0.6","version_comment":"BF: fix missing bufname() when creating the undo_tree window\r\nNF: make undo_tree window a little bit smaller (size is adjustable via g:undo_tree_wdth variable)","3":"BF: fix missing bufname() when creating the undo_tree window\r\nNF: make undo_tree window a little bit smaller (size is adjustable via g:undo_tree_wdth variable)","package":"histwin.vim","4":"histwin.vim","src_id":"12142","5":"12142","creation_date":"1264020655","6":"1264020655"},{"0":"2932","vim_version":"7.0","1":"7.0","script_version":"0.5","2":"0.5","version_comment":"NF: Allow diffing with selected branch\r\nNF: highlight current version\r\nNF: Use changenr() to determine undobranch\r\nNF: <C-L> updates view\r\nNF: allow switching to initial load state, before buffer was edited\r\nBF: Fix annoying bug, that displays --No lines in buffer--\r\nBF: fix several small annoying bugs","3":"NF: Allow diffing with selected branch\r\nNF: highlight current version\r\nNF: Use changenr() to determine undobranch\r\nNF: <C-L> updates view\r\nNF: allow switching to initial load state, before buffer was edited\r\nBF: Fix annoying bug, that displays --No lines in buffer--\r\nBF: fix several small annoying bugs","package":"histwin.vim","4":"histwin.vim","src_id":"12140","5":"12140","creation_date":"1264017442","6":"1264017442"},{"0":"2932","vim_version":"7.2","1":"7.2","script_version":"0.2","2":"0.2","version_comment":"Initial upload","3":"Initial upload","package":"histwin.vim","4":"histwin.vim","src_id":"12130","5":"12130","creation_date":"1263942943","6":"1263942943"}]},"2931":{"script_id":"2931","0":"2931","script_name":"fontzoom.vim","1":"fontzoom.vim","script_type":"utility","2":"utility","summary":"The fontsize controller in gVim.","3":"The fontsize controller in gVim.","description":"*fontzoom* is a Vim plugin to control gui fontsize.  You can change fontsize\r\nwith + and - keys(when default setting).  You can also use the [count].\r\nThis plugin remember 'guifont', 'lines', and 'columns' when you change\r\nfontsize first.  And tries to keep the size of the window as much as possible.\r\n\r\nsimilar plugins:\r\nguifont++.vim        vimscript #593\r\nzoom.vim        vimscript #2321\r\nfontsize.vim        vimscript #2809\r\n\r\nLatest Version:\r\nhttps:\/\/github.com\/thinca\/vim-fontzoom","4":"*fontzoom* is a Vim plugin to control gui fontsize.  You can change fontsize\r\nwith + and - keys(when default setting).  You can also use the [count].\r\nThis plugin remember 'guifont', 'lines', and 'columns' when you change\r\nfontsize first.  And tries to keep the size of the window as much as possible.\r\n\r\nsimilar plugins:\r\nguifont++.vim        vimscript #593\r\nzoom.vim        vimscript #2321\r\nfontsize.vim        vimscript #2809\r\n\r\nLatest Version:\r\nhttps:\/\/github.com\/thinca\/vim-fontzoom","install_details":"","5":"","first_name":"thinca","6":"thinca","last_name":" ","7":" ","releases":[{"0":"2931","vim_version":"7.2","1":"7.2","script_version":"0.1.1","2":"0.1.1","version_comment":"- Added default key mappings.\r\n  - <C-ScrollWheelUp> and <C-ScrollWheelDown>.","3":"- Added default key mappings.\r\n  - <C-ScrollWheelUp> and <C-ScrollWheelDown>.","package":"vim-fontzoom-0.1.1.zip","4":"vim-fontzoom-0.1.1.zip","src_id":"15101","5":"15101","creation_date":"1298476389","6":"1298476389"},{"0":"2931","vim_version":"7.2","1":"7.2","script_version":"0.1.0","2":"0.1.0","version_comment":"Initial upload","3":"Initial upload","package":"vim-fontzoom-0.1.0.zip","4":"vim-fontzoom-0.1.0.zip","src_id":"12125","5":"12125","creation_date":"1263916925","6":"1263916925"}]},"2930":{"script_id":"2930","0":"2930","script_name":"rfc syntax","1":"rfc syntax","script_type":"syntax","2":"syntax","summary":"Simple syntax highlight for RFC file","3":"Simple syntax highlight for RFC file","description":"Simple syntax highlight for RFC (Request For Comments) file.\r\nIt can highlight the contents, the titles and so on.\r\n\r\nA ftplugin is also provided to use <C-]> to jump from the contents or reference note ([1] like things). You can then use <C-t> to go back. <C-o> and `` should work as expected.","4":"Simple syntax highlight for RFC (Request For Comments) file.\r\nIt can highlight the contents, the titles and so on.\r\n\r\nA ftplugin is also provided to use <C-]> to jump from the contents or reference note ([1] like things). You can then use <C-t> to go back. <C-o> and `` should work as expected.","install_details":"unzip the archive to your .vim (or vimfiles) directory.\r\n\r\nYou must add filetype detect by yourself. For example, add\r\n  if expand('%:t') =~? 'rfc\\d\\+'\r\n    setfiletype rfc\r\n  endif\r\nto your scripts.vim will make Vim recognize all files with name rfcXXXX as RFC file.\r\n","5":"unzip the archive to your .vim (or vimfiles) directory.\r\n\r\nYou must add filetype detect by yourself. For example, add\r\n  if expand('%:t') =~? 'rfc\\d\\+'\r\n    setfiletype rfc\r\n  endif\r\nto your scripts.vim will make Vim recognize all files with name rfcXXXX as RFC file.\r\n","first_name":"lilydjwg","6":"lilydjwg","last_name":" ","7":" ","releases":[{"0":"2930","vim_version":"7.0","1":"7.0","script_version":"1.2","2":"1.2","version_comment":"* support multiple backward steps. Thanks to Chenxiong Qi","3":"* support multiple backward steps. Thanks to Chenxiong Qi","package":"rfc.zip","4":"rfc.zip","src_id":"21264","5":"21264","creation_date":"1388502020","6":"1388502020"},{"0":"2930","vim_version":"7.0","1":"7.0","script_version":"1.1","2":"1.1","version_comment":"* better reference jump (thanks to Marcelo Mont\u00c3\u00ba)","3":"* better reference jump (thanks to Marcelo Mont\u00c3\u00ba)","package":"rfc.zip","4":"rfc.zip","src_id":"21120","5":"21120","creation_date":"1385564781","6":"1385564781"},{"0":"2930","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"* better <C-]> handling\r\n* <C-t> to go back","3":"* better <C-]> handling\r\n* <C-t> to go back","package":"rfc.zip","4":"rfc.zip","src_id":"17302","5":"17302","creation_date":"1327325793","6":"1327325793"},{"0":"2930","vim_version":"6.0","1":"6.0","script_version":"0.2.1","2":"0.2.1","version_comment":"FIXed a typo which causes the first line of the file to be deleted.","3":"FIXed a typo which causes the first line of the file to be deleted.","package":"rfc.zip","4":"rfc.zip","src_id":"12147","5":"12147","creation_date":"1264050292","6":"1264050292"}]},"2929":{"script_id":"2929","0":"2929","script_name":"mark_tools","1":"mark_tools","script_type":"utility","2":"utility","summary":"Toggle and navigate marks","3":"Toggle and navigate marks","description":"The plugin is another try on Vim marks. Often I end up using two separate mark groups for navigation (a-f and t-z) so I created a plugin to simplify this. Version 1.1 adds the ability to display marks in quickfix and location list windows.\r\n\r\nProvided mappings:\r\n<Plug>ToggleMarkAZ - mark\/unmark current position, if there are multiple marks on the line, remove the first\r\n<Plug>ToggleMarkZA - mark\/unmark current position, if there are multiple marks on the line, remove the last\r\n<Plug>ForceMarkAZ - add an unused mark starting from a, even if the position is marked\r\n<Plug>ForceMarkZA - add an unused mark starting from z, even if the position is marked\r\n<Plug>NextMarkPos - go to next mark\r\n<Plug>PrevMarkPos - go to prev mark\r\n<Plug>NextMarkLexi - go to previous mark in lexicographical order\r\n<Plug>PrevMarkLexi - go to next mark in lexicographical order\r\n<Plug>MarksLoc    - open location list window with local mark positions\r\n<Plug>MarksQF\t    - open quickfix window with marks\r\n\r\nRecommended mapping to put into your .vimrc:\r\nnmap <Leader>a <Plug>ToggleMarkAZ\r\nnmap <Leader>z <Plug>ToggleMarkZA\r\nnmap <Leader>A <Plug>ForceMarkAZ\r\nnmap <Leader>Z <Plug>ForceMarkZA\r\nnmap <Leader>m <Plug>NextMarkPos\r\nnmap <Leader>M <Plug>PrevMarkPos\r\nnmap <Leader>l <Plug>NextMarkLexi\r\nnmap <Leader>L <Plug>PrevMarkLexi\r\nnmap <Leader>w <Plug>MarksLoc\r\nnmap <Leader>W <Plug>MarksQF\r\n\r\nSo\r\n\\a and \\z will toggle a mark at current line\r\n\\A and \\Z force another mark\r\n\\m and \\M go to next\/prev mark\r\n\\l and \\L go to next\/prev mark alphabetically\r\n\\w and \\W populate location list\/quickfix window with marks\r\n\r\nAlso I suggest to install a plugin to visualise marks e.g. quickfixsigns (vimscript#2584)\r\n\r\nCustomisation:\r\ntoggle_marks_wrap_search variable controls whether search wraps around or not (order of precedence: w:toggle_marks_wrap_search, b:toggle_marks_wrap_search, g:toggle_marks_wrap_search)\r\nPossible values:\r\n-1 - use 'wrapscan' option value\r\n 0 - do not wrap\r\n 1 - always wrap (default)\r\n\r\nVariables below define which marks should be displayed in loclist and quickfix windows respectively\r\nlet g:lmarks_names = 'abcdefghijklmnopqrstuvwxyz''.'\r\nlet g:gmarks_names = 'ABCDEFGHIJKLMNOPQRSTUVWXYZ0123456789'\r\n\r\nI use the plugin on daily basis. If you found any problems or want to suggest a feature, drop me an email.","4":"The plugin is another try on Vim marks. Often I end up using two separate mark groups for navigation (a-f and t-z) so I created a plugin to simplify this. Version 1.1 adds the ability to display marks in quickfix and location list windows.\r\n\r\nProvided mappings:\r\n<Plug>ToggleMarkAZ - mark\/unmark current position, if there are multiple marks on the line, remove the first\r\n<Plug>ToggleMarkZA - mark\/unmark current position, if there are multiple marks on the line, remove the last\r\n<Plug>ForceMarkAZ - add an unused mark starting from a, even if the position is marked\r\n<Plug>ForceMarkZA - add an unused mark starting from z, even if the position is marked\r\n<Plug>NextMarkPos - go to next mark\r\n<Plug>PrevMarkPos - go to prev mark\r\n<Plug>NextMarkLexi - go to previous mark in lexicographical order\r\n<Plug>PrevMarkLexi - go to next mark in lexicographical order\r\n<Plug>MarksLoc    - open location list window with local mark positions\r\n<Plug>MarksQF\t    - open quickfix window with marks\r\n\r\nRecommended mapping to put into your .vimrc:\r\nnmap <Leader>a <Plug>ToggleMarkAZ\r\nnmap <Leader>z <Plug>ToggleMarkZA\r\nnmap <Leader>A <Plug>ForceMarkAZ\r\nnmap <Leader>Z <Plug>ForceMarkZA\r\nnmap <Leader>m <Plug>NextMarkPos\r\nnmap <Leader>M <Plug>PrevMarkPos\r\nnmap <Leader>l <Plug>NextMarkLexi\r\nnmap <Leader>L <Plug>PrevMarkLexi\r\nnmap <Leader>w <Plug>MarksLoc\r\nnmap <Leader>W <Plug>MarksQF\r\n\r\nSo\r\n\\a and \\z will toggle a mark at current line\r\n\\A and \\Z force another mark\r\n\\m and \\M go to next\/prev mark\r\n\\l and \\L go to next\/prev mark alphabetically\r\n\\w and \\W populate location list\/quickfix window with marks\r\n\r\nAlso I suggest to install a plugin to visualise marks e.g. quickfixsigns (vimscript#2584)\r\n\r\nCustomisation:\r\ntoggle_marks_wrap_search variable controls whether search wraps around or not (order of precedence: w:toggle_marks_wrap_search, b:toggle_marks_wrap_search, g:toggle_marks_wrap_search)\r\nPossible values:\r\n-1 - use 'wrapscan' option value\r\n 0 - do not wrap\r\n 1 - always wrap (default)\r\n\r\nVariables below define which marks should be displayed in loclist and quickfix windows respectively\r\nlet g:lmarks_names = 'abcdefghijklmnopqrstuvwxyz''.'\r\nlet g:gmarks_names = 'ABCDEFGHIJKLMNOPQRSTUVWXYZ0123456789'\r\n\r\nI use the plugin on daily basis. If you found any problems or want to suggest a feature, drop me an email.","install_details":"Put into $VIMRUNTIME\/plugin or source the plugin directly with \":so mark_tools.vim\"\r\n\r\nAlso available on https:\/\/bitbucket.org\/khorser\/vim-mark-tools and https:\/\/github.com\/khorser\/vim-mark-tools","5":"Put into $VIMRUNTIME\/plugin or source the plugin directly with \":so mark_tools.vim\"\r\n\r\nAlso available on https:\/\/bitbucket.org\/khorser\/vim-mark-tools and https:\/\/github.com\/khorser\/vim-mark-tools","first_name":"Sergey","6":"Sergey","last_name":"Khorev","7":"Khorev","releases":[{"0":"2929","vim_version":"7.0","1":"7.0","script_version":"1.1","2":"1.1","version_comment":"Renamed to mark_tools, added functionality to display marks in quickfix\/loclist windows","3":"Renamed to mark_tools, added functionality to display marks in quickfix\/loclist windows","package":"mark_tools.vim","4":"mark_tools.vim","src_id":"12264","5":"12264","creation_date":"1265035148","6":"1265035148"},{"0":"2929","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"toggle_local_marks.vim","4":"toggle_local_marks.vim","src_id":"12113","5":"12113","creation_date":"1263633028","6":"1263633028"}]},"2928":{"script_id":"2928","0":"2928","script_name":"Vimrc Version Numbering","1":"Vimrc Version Numbering","script_type":"utility","2":"utility","summary":"automatic vimrc version numbering","3":"automatic vimrc version numbering","description":"Automatically increments and displays version number stored inside  vimrc file itself. Version number is automatically updated when a modified vimrc file is saved.\r\n\r\nDisplays version number  of vimrc in use when vim is started. This makes it easy to ensure that you have your latest copy of vimrc on different computers.\r\n\r\nAlso useful if someone you know uses your vimrc wholesale, or if there are a few versions of \"standard\" versions of vimrc going around in your environment.","4":"Automatically increments and displays version number stored inside  vimrc file itself. Version number is automatically updated when a modified vimrc file is saved.\r\n\r\nDisplays version number  of vimrc in use when vim is started. This makes it easy to ensure that you have your latest copy of vimrc on different computers.\r\n\r\nAlso useful if someone you know uses your vimrc wholesale, or if there are a few versions of \"standard\" versions of vimrc going around in your environment.","install_details":"insert code into your vimrc file.","5":"insert code into your vimrc file.","first_name":"eiji","6":"eiji","last_name":"kumiai","7":"kumiai","releases":[{"0":"2928","vim_version":"7.0","1":"7.0","script_version":"1.1","2":"1.1","version_comment":"- Added debug mode to stop version number from incrementing.\r\n\r\nEdit as follows to allow incrementation.\r\n:let g:debugmode=0\r\n\r\nEdit as follows to disallow incrementation\r\n:let g:debugmode=1\r\n\r\n- Removed map \",it\" to clean up code\r\n","3":"- Added debug mode to stop version number from incrementing.\r\n\r\nEdit as follows to allow incrementation.\r\n:let g:debugmode=0\r\n\r\nEdit as follows to disallow incrementation\r\n:let g:debugmode=1\r\n\r\n- Removed map \",it\" to clean up code\r\n","package":"vimrc_version.vim","4":"vimrc_version.vim","src_id":"12332","5":"12332","creation_date":"1265555011","6":"1265555011"},{"0":"2928","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"vimrc_version.vim","4":"vimrc_version.vim","src_id":"12112","5":"12112","creation_date":"1263621962","6":"1263621962"}]},"2927":{"script_id":"2927","0":"2927","script_name":"Dictionary List Replacements","1":"Dictionary List Replacements","script_type":"utility","2":"utility","summary":"==SUPERSEDED BY MULTI-REPLACE==","3":"==SUPERSEDED BY MULTI-REPLACE==","description":"Functionality in this script has been superseded by Multi-Replace.\r\nRefer to http:\/\/www.vim.org\/scripts\/script.php?script_id=2938\r\n\r\n-------------------------------------------------------------\r\n\r\nThis script provides two replacement capabilities, both involving a second buffer.\r\n\r\n[=] OVERVIEW\r\n\r\n1. DICTIONARY REPLACE\r\n=====================\r\nReplace words according to a tab-separated list of word-pairs.\r\nWords on the left of the tab are the words to search for, \r\nwords on the right are the corresponding replacements.\r\n\r\nExample:\r\n  1. %s\r\n  2. %s\r\n  3. %b\r\n  [BEFORE]===============\r\n  1. stars\r\n  2. stars\r\n  3. breasts\r\n  [AFTER]================\r\n\r\nTypical use: \r\n- Variable substitution on a template.\r\n- Performing a join on two lists\r\n- Reording lines given orderd list of keys\r\n\r\n2. LIST REPLACE\r\n===============\r\nReplace matches using text from line matching\r\norder of appearance.\r\n\r\nExample:\r\n  1. %f are good for your body.\r\n  2. %v are bad for your body.\r\n  3. %f are good for your body.\r\n  4. %v are bad for your body.\r\n  5. %f are good for your body.\r\n  6. %v are bad for your body.\r\n  [BEFORE]===============\r\n  1. apples are good for your body.\r\n  2. %v are bad for your body.\r\n  3. vegetables are good for your body.\r\n  4. %v are bad for your body.\r\n  5. vitamins are good for your body.\r\n  6. %v are bad for your body.\r\n  [AFTER]================\r\n\r\nTypical use: \r\n- Repeating blocks of code with different identtifiers\r\n- Intersparsing lines from a file with lines from another file\r\n\r\n[=] USAGE\r\n\r\n1. DICTIONARY REPLACE\r\n=====================\r\n\r\nLet's say we have some text.\r\n  =====================\r\n  your eyes are like stars kissing the breasts of the galaxies.\r\n  your %e are like %s kissing the %b of the galaxies.\r\n  1. %s\r\n  2. %s\r\n  3. %b\r\n  4. %s\r\n  5. %b\r\n  6. %e\r\n  7. %e\r\n  [TEXT]================\r\n\r\nIn a separate buffer, prepare a list of tab-separated words. Make sure\r\nthat the pairs are sperated by tabs and not space characters!\r\n  =====================\r\n  breasts\tstars\r\n  eyes\tbreasts\r\n  stars\teyes\r\n  %s\tstars\r\n  %b\tbreasts\r\n  %e\teyes\r\n  [DICT]================\r\n\r\nIn the alternate buffer, runthe command \",dict\" \r\n(comma-dict) standing for \"dictionary\".\r\n  ,dict\r\n\r\nNow go back to our text buffer, and do a selection to match all words. Only words matching current search pattern are replaced.\r\n  \/\\S\\+\r\n\r\nRun the command \",rict\" (comma-rict) standing for \"replace dictionary\".\r\n  =====================\r\n  your breasts are like eyes kissing the stars of the galaxies.\r\n  your eyes are like stars kissing the breasts of the galaxies.\r\n  1. stars\r\n  2. stars\r\n  3. breasts\r\n  4. stars\r\n  5. breasts\r\n  6. eyes\r\n  7. eyes\r\n  [TEXT]=[+]=============\r\n\r\nLimitation: \r\nReplacements are only done on words matching \r\nthe current search pattern. This is not a true\r\nmulti-replace solution, but more efficient.\r\n\r\n2. List Replace\r\n===============\r\n\r\nLet's say we have some text.\r\n  =====================\r\n  1. %f are good for your body.\r\n  2. %v are bad for your body.\r\n  3. %f are good for your body.\r\n  4. %v are bad for your body.\r\n  5. %f are good for your body.\r\n  6. %v are bad for your body.\r\n  [TEXT]================\r\n\r\nIn a separate buffer, the list for replacement.\r\nMake sure there are enough rows to match target\r\ntext!\r\n  =====================\r\n  apples\r\n  vegetables\r\n  vitamins\r\n  [DICT]================\r\n\r\nIn the alternate buffer, runthe command \",list\" \r\n(comma-list) standing for \"list\".\r\n  ,list\r\n\r\nNow go back to our text buffer, and do a selection\r\nto match %f which we want to replace.\r\n  \/%f\r\n\r\nRun the command \",rist\" (comma-rist) standing for \"replace list\".\r\n  =====================\r\n  1. apples are good for your body.\r\n  2. %v are bad for your body.\r\n  3. vegetables are good for your body.\r\n  4. %v are bad for your body.\r\n  5. vitamins are good for your body.\r\n  6. %v are bad for your body.\r\n  [TEXT]=[+]=============\r\n\r\nLimitation: \r\nMatches on the same line are replaced with the same string. There's no option to choose to replace with the next string right now.","4":"Functionality in this script has been superseded by Multi-Replace.\r\nRefer to http:\/\/www.vim.org\/scripts\/script.php?script_id=2938\r\n\r\n-------------------------------------------------------------\r\n\r\nThis script provides two replacement capabilities, both involving a second buffer.\r\n\r\n[=] OVERVIEW\r\n\r\n1. DICTIONARY REPLACE\r\n=====================\r\nReplace words according to a tab-separated list of word-pairs.\r\nWords on the left of the tab are the words to search for, \r\nwords on the right are the corresponding replacements.\r\n\r\nExample:\r\n  1. %s\r\n  2. %s\r\n  3. %b\r\n  [BEFORE]===============\r\n  1. stars\r\n  2. stars\r\n  3. breasts\r\n  [AFTER]================\r\n\r\nTypical use: \r\n- Variable substitution on a template.\r\n- Performing a join on two lists\r\n- Reording lines given orderd list of keys\r\n\r\n2. LIST REPLACE\r\n===============\r\nReplace matches using text from line matching\r\norder of appearance.\r\n\r\nExample:\r\n  1. %f are good for your body.\r\n  2. %v are bad for your body.\r\n  3. %f are good for your body.\r\n  4. %v are bad for your body.\r\n  5. %f are good for your body.\r\n  6. %v are bad for your body.\r\n  [BEFORE]===============\r\n  1. apples are good for your body.\r\n  2. %v are bad for your body.\r\n  3. vegetables are good for your body.\r\n  4. %v are bad for your body.\r\n  5. vitamins are good for your body.\r\n  6. %v are bad for your body.\r\n  [AFTER]================\r\n\r\nTypical use: \r\n- Repeating blocks of code with different identtifiers\r\n- Intersparsing lines from a file with lines from another file\r\n\r\n[=] USAGE\r\n\r\n1. DICTIONARY REPLACE\r\n=====================\r\n\r\nLet's say we have some text.\r\n  =====================\r\n  your eyes are like stars kissing the breasts of the galaxies.\r\n  your %e are like %s kissing the %b of the galaxies.\r\n  1. %s\r\n  2. %s\r\n  3. %b\r\n  4. %s\r\n  5. %b\r\n  6. %e\r\n  7. %e\r\n  [TEXT]================\r\n\r\nIn a separate buffer, prepare a list of tab-separated words. Make sure\r\nthat the pairs are sperated by tabs and not space characters!\r\n  =====================\r\n  breasts\tstars\r\n  eyes\tbreasts\r\n  stars\teyes\r\n  %s\tstars\r\n  %b\tbreasts\r\n  %e\teyes\r\n  [DICT]================\r\n\r\nIn the alternate buffer, runthe command \",dict\" \r\n(comma-dict) standing for \"dictionary\".\r\n  ,dict\r\n\r\nNow go back to our text buffer, and do a selection to match all words. Only words matching current search pattern are replaced.\r\n  \/\\S\\+\r\n\r\nRun the command \",rict\" (comma-rict) standing for \"replace dictionary\".\r\n  =====================\r\n  your breasts are like eyes kissing the stars of the galaxies.\r\n  your eyes are like stars kissing the breasts of the galaxies.\r\n  1. stars\r\n  2. stars\r\n  3. breasts\r\n  4. stars\r\n  5. breasts\r\n  6. eyes\r\n  7. eyes\r\n  [TEXT]=[+]=============\r\n\r\nLimitation: \r\nReplacements are only done on words matching \r\nthe current search pattern. This is not a true\r\nmulti-replace solution, but more efficient.\r\n\r\n2. List Replace\r\n===============\r\n\r\nLet's say we have some text.\r\n  =====================\r\n  1. %f are good for your body.\r\n  2. %v are bad for your body.\r\n  3. %f are good for your body.\r\n  4. %v are bad for your body.\r\n  5. %f are good for your body.\r\n  6. %v are bad for your body.\r\n  [TEXT]================\r\n\r\nIn a separate buffer, the list for replacement.\r\nMake sure there are enough rows to match target\r\ntext!\r\n  =====================\r\n  apples\r\n  vegetables\r\n  vitamins\r\n  [DICT]================\r\n\r\nIn the alternate buffer, runthe command \",list\" \r\n(comma-list) standing for \"list\".\r\n  ,list\r\n\r\nNow go back to our text buffer, and do a selection\r\nto match %f which we want to replace.\r\n  \/%f\r\n\r\nRun the command \",rist\" (comma-rist) standing for \"replace list\".\r\n  =====================\r\n  1. apples are good for your body.\r\n  2. %v are bad for your body.\r\n  3. vegetables are good for your body.\r\n  4. %v are bad for your body.\r\n  5. vitamins are good for your body.\r\n  6. %v are bad for your body.\r\n  [TEXT]=[+]=============\r\n\r\nLimitation: \r\nMatches on the same line are replaced with the same string. There's no option to choose to replace with the next string right now.","install_details":"Paste contents of file into your vimrc","5":"Paste contents of file into your vimrc","first_name":"eiji","6":"eiji","last_name":"kumiai","7":"kumiai","releases":[{"0":"2927","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"dictionarylist.vim","4":"dictionarylist.vim","src_id":"12110","5":"12110","creation_date":"1263589945","6":"1263589945"}]},"2926":{"script_id":"2926","0":"2926","script_name":"SnippetComplete","1":"SnippetComplete","script_type":"utility","2":"utility","summary":"Insert mode completion that completes defined abbreviations and other snippets.","3":"Insert mode completion that completes defined abbreviations and other snippets.","description":"DESCRIPTION\r\nInsert mode abbreviations and snippets can dramatically speed up editing, but\r\nhow does one remember all those shortcuts that are rarely used? You can list\r\nall insert mode abbreviations via :ia to break out of this vicious circle,\r\nbut switching to command mode for that is cumbersome.\r\n\r\nThis plugin offers a context-sensitive insert mode completion to quickly list\r\nand complete defined abbreviations directly while typing.\r\n\r\nSEE ALSO\r\n- The SnippetCompleteSnipMate.vim plugin (vimscript #4276) extends the\r\n  completion with snippets for the popular snipMate plugin (vimscript #2540).\r\n\r\nUSAGE\r\nIn insert mode, optionally type part of the snippet shortcut or a fragment\r\nfrom its expected expansion, and invoke the snippet completion via CTRL-X ].\r\nYou can then search forward and backward via CTRL-N \/ CTRL-P, as usual.\r\n\r\nCTRL-X ]                Find matches for abbreviations that start with the\r\n                        text in front of the cursor. If other snippet types\r\n                        are registered, show those, too.\r\n                        If no matches were found that way, matches anywhere in\r\n                        the snippet or in the snippet's expanded text will be\r\n                        shown. So if you can't remember the shortcut, but a\r\n                        word fragment from the resulting expansion, just try\r\n                        with that.\r\n\r\n                        There are three types of abbreviations (full-id,\r\n                        end-id and non-id), which can consist of different\r\n                        characters. Thus, there can be more than one candidate\r\n                        for the existing completion base, e.g. \"pre@c\" can\r\n                        expand into a full-id abbreviation starting with \"c\"\r\n                        or into a non-id one starting with \"pre@c\". The\r\n                        completion indicates such a ambiguity through the\r\n                        message \"base n of m; next: blah\", and you can cycle\r\n                        through the different completion bases by repeating\r\n                        the i_CTRL-X_] shortcut.\r\n\r\n                        Matches are selected and inserted as with any other\r\n                        ins-completion, see popupmenu-keys. If you use\r\n                        <Space> or i_CTRL-] to select an abbreviation, it'll\r\n                        be expanded automatically.\r\n\r\nCTRL-X g]               Find matches for buffer-local abbreviations that start\r\n                        with the text in front of the cursor. If other snippet\r\n                        types are registered, show those (local ones), too.","4":"DESCRIPTION\r\nInsert mode abbreviations and snippets can dramatically speed up editing, but\r\nhow does one remember all those shortcuts that are rarely used? You can list\r\nall insert mode abbreviations via :ia to break out of this vicious circle,\r\nbut switching to command mode for that is cumbersome.\r\n\r\nThis plugin offers a context-sensitive insert mode completion to quickly list\r\nand complete defined abbreviations directly while typing.\r\n\r\nSEE ALSO\r\n- The SnippetCompleteSnipMate.vim plugin (vimscript #4276) extends the\r\n  completion with snippets for the popular snipMate plugin (vimscript #2540).\r\n\r\nUSAGE\r\nIn insert mode, optionally type part of the snippet shortcut or a fragment\r\nfrom its expected expansion, and invoke the snippet completion via CTRL-X ].\r\nYou can then search forward and backward via CTRL-N \/ CTRL-P, as usual.\r\n\r\nCTRL-X ]                Find matches for abbreviations that start with the\r\n                        text in front of the cursor. If other snippet types\r\n                        are registered, show those, too.\r\n                        If no matches were found that way, matches anywhere in\r\n                        the snippet or in the snippet's expanded text will be\r\n                        shown. So if you can't remember the shortcut, but a\r\n                        word fragment from the resulting expansion, just try\r\n                        with that.\r\n\r\n                        There are three types of abbreviations (full-id,\r\n                        end-id and non-id), which can consist of different\r\n                        characters. Thus, there can be more than one candidate\r\n                        for the existing completion base, e.g. \"pre@c\" can\r\n                        expand into a full-id abbreviation starting with \"c\"\r\n                        or into a non-id one starting with \"pre@c\". The\r\n                        completion indicates such a ambiguity through the\r\n                        message \"base n of m; next: blah\", and you can cycle\r\n                        through the different completion bases by repeating\r\n                        the i_CTRL-X_] shortcut.\r\n\r\n                        Matches are selected and inserted as with any other\r\n                        ins-completion, see popupmenu-keys. If you use\r\n                        <Space> or i_CTRL-] to select an abbreviation, it'll\r\n                        be expanded automatically.\r\n\r\nCTRL-X g]               Find matches for buffer-local abbreviations that start\r\n                        with the text in front of the cursor. If other snippet\r\n                        types are registered, show those (local ones), too.","install_details":"INSTALLATION\r\nThis script is packaged as a vimball. If you have the \"gunzip\" decompressor\r\nin your PATH, simply edit the *.vmb.gz package in Vim; otherwise, decompress\r\nthe archive first, e.g. using WinZip. Inside Vim, install by sourcing the\r\nvimball or via the :UseVimball command.\r\n    vim SnippetComplete*.vmb.gz\r\n    :so %\r\nTo uninstall, use the :RmVimball command.\r\n\r\nDEPENDENCIES\r\n- Requires Vim 7.0 or higher.\r\n- Requires the CompleteHelper.vim plugin (vimscript #3914), version 1.10 or\r\n  higher.\r\n- Requires the ingo-library.vim plugin (vimscript #4433), version 1.009 or\r\n  higher.\r\n\r\nCONFIGURATION\r\nFor a permanent configuration, put the following commands into your vimrc:\r\n\r\nIf you want to use a different mapping, map your keys to the\r\n<Plug>(SnippetComplete...) mapping targets _before_ sourcing the script (e.g.\r\nin your vimrc).\r\nFor example, to use CTRL-X <Tab> as the completion trigger, define this:\r\n    imap <C-x><Tab> <Plug>(SnippetComplete)\r\n\r\nINTEGRATION\r\nThere exist multiple snippet systems that extend the built-in abbreviations\r\nwith support for filetype-specific and more complex expansions, like allowing\r\nplaceholders and expansion of in-line scriptlets. One popular one is the\r\nsnipMate plugin (vimscript #2540).\r\nSince there is a seamless transition from simple abbreviation to complex\r\nsnippet, it may help to have a completion for both sources. To support this,\r\nthis plugin allows to write completions for other snippet plugins with just a\r\nlittle bit of configuration and a function to retrieve the valid snippets.\r\nThis completion can be stand-alone via a different mapping, or it can add the\r\nsnippets to the i_CTRL-X_] completion mapping provided here.","5":"INSTALLATION\r\nThis script is packaged as a vimball. If you have the \"gunzip\" decompressor\r\nin your PATH, simply edit the *.vmb.gz package in Vim; otherwise, decompress\r\nthe archive first, e.g. using WinZip. Inside Vim, install by sourcing the\r\nvimball or via the :UseVimball command.\r\n    vim SnippetComplete*.vmb.gz\r\n    :so %\r\nTo uninstall, use the :RmVimball command.\r\n\r\nDEPENDENCIES\r\n- Requires Vim 7.0 or higher.\r\n- Requires the CompleteHelper.vim plugin (vimscript #3914), version 1.10 or\r\n  higher.\r\n- Requires the ingo-library.vim plugin (vimscript #4433), version 1.009 or\r\n  higher.\r\n\r\nCONFIGURATION\r\nFor a permanent configuration, put the following commands into your vimrc:\r\n\r\nIf you want to use a different mapping, map your keys to the\r\n<Plug>(SnippetComplete...) mapping targets _before_ sourcing the script (e.g.\r\nin your vimrc).\r\nFor example, to use CTRL-X <Tab> as the completion trigger, define this:\r\n    imap <C-x><Tab> <Plug>(SnippetComplete)\r\n\r\nINTEGRATION\r\nThere exist multiple snippet systems that extend the built-in abbreviations\r\nwith support for filetype-specific and more complex expansions, like allowing\r\nplaceholders and expansion of in-line scriptlets. One popular one is the\r\nsnipMate plugin (vimscript #2540).\r\nSince there is a seamless transition from simple abbreviation to complex\r\nsnippet, it may help to have a completion for both sources. To support this,\r\nthis plugin allows to write completions for other snippet plugins with just a\r\nlittle bit of configuration and a function to retrieve the valid snippets.\r\nThis completion can be stand-alone via a different mapping, or it can add the\r\nsnippets to the i_CTRL-X_] completion mapping provided here.","first_name":"Ingo","6":"Ingo","last_name":"Karkat","7":"Karkat","releases":[{"0":"2926","vim_version":"7.0","1":"7.0","script_version":"2.20","2":"2.20","version_comment":"- ENH: Add CTRL-X g] mapping variant that limits the results to buffer-local abbreviations. This is useful to quickly get an overview of filetype-specific abbreviations, which are usually drowned in the sea of global ones (and snippets if integrated).\r\n- Add dependency to ingo-library (vimscript #4433). *** You need to separately install ingo-library (vimscript #4433) version 1.009 (or higher)! ***","3":"- ENH: Add CTRL-X g] mapping variant that limits the results to buffer-local abbreviations. This is useful to quickly get an overview of filetype-specific abbreviations, which are usually drowned in the sea of global ones (and snippets if integrated).\r\n- Add dependency to ingo-library (vimscript #4433). *** You need to separately install ingo-library (vimscript #4433) version 1.009 (or higher)! ***","package":"SnippetComplete-2.20.vmb.gz","4":"SnippetComplete-2.20.vmb.gz","src_id":"21727","5":"21727","creation_date":"1396537690","6":"1396537690"},{"0":"2926","vim_version":"7.0","1":"7.0","script_version":"2.11","2":"2.11","version_comment":"FIX: Must use numerical sort() for s:lastCompletionsByBaseCol.","3":"FIX: Must use numerical sort() for s:lastCompletionsByBaseCol.","package":"SnippetComplete-2.11.vmb.gz","4":"SnippetComplete-2.11.vmb.gz","src_id":"19389","5":"19389","creation_date":"1358610739","6":"1358610739"},{"0":"2926","vim_version":"7.0","1":"7.0","script_version":"2.10","2":"2.10","version_comment":"- ENH: When no base doesn't match with the beginning of a snippet, fall back to matches either anywhere in the snippet or in the snippet expansion.\r\n- Truncate very long or multi-line snippet expansions in the popup menu. This requires the CompleteHelper plugin. When the entire snippet doesn't fit into the popup menu, offer it for showing in the preview window. *** THIS PLUGIN NOW REQUIRES THE CompleteHelper PLUGIN (vimscript #3914) ***","3":"- ENH: When no base doesn't match with the beginning of a snippet, fall back to matches either anywhere in the snippet or in the snippet expansion.\r\n- Truncate very long or multi-line snippet expansions in the popup menu. This requires the CompleteHelper plugin. When the entire snippet doesn't fit into the popup menu, offer it for showing in the preview window. *** THIS PLUGIN NOW REQUIRES THE CompleteHelper PLUGIN (vimscript #3914) ***","package":"SnippetComplete-2.10.vmb.gz","4":"SnippetComplete-2.10.vmb.gz","src_id":"18840","5":"18840","creation_date":"1350659958","6":"1350659958"},{"0":"2926","vim_version":"7.0","1":"7.0","script_version":"2.01","2":"2.01","version_comment":"- FIX: Vim 7.0\/1 need preloading of functions referenced in Funcrefs.","3":"- FIX: Vim 7.0\/1 need preloading of functions referenced in Funcrefs.","package":"SnippetComplete.vba.gz","4":"SnippetComplete.vba.gz","src_id":"18398","5":"18398","creation_date":"1344847084","6":"1344847084"},{"0":"2926","vim_version":"7.0","1":"7.0","script_version":"2.00","2":"2.00","version_comment":"Modularize and generalize for completing other types of snippets (e.g. from snipMate).","3":"Modularize and generalize for completing other types of snippets (e.g. from snipMate).","package":"SnippetComplete.vba.gz","4":"SnippetComplete.vba.gz","src_id":"17901","5":"17901","creation_date":"1336466140","6":"1336466140"},{"0":"2926","vim_version":"7.0","1":"7.0","script_version":"1.01","2":"1.01","version_comment":"Using separate autoload script to help speed up Vim startup.","3":"Using separate autoload script to help speed up Vim startup.","package":"SnippetComplete.vba.gz","4":"SnippetComplete.vba.gz","src_id":"13931","5":"13931","creation_date":"1285576006","6":"1285576006"},{"0":"2926","vim_version":"7.0","1":"7.0","script_version":"1.00","2":"1.00","version_comment":"Initial upload","3":"Initial upload","package":"SnippetComplete.vba.gz","4":"SnippetComplete.vba.gz","src_id":"12091","5":"12091","creation_date":"1263477234","6":"1263477234"}]},"2925":{"script_id":"2925","0":"2925","script_name":"apt-complete.vim","1":"apt-complete.vim","script_type":"plugin","2":"plugin","summary":" provide debian package name completion","3":" provide debian package name completion","description":"    apt-complete.vim\r\n    ============\r\n    provide deb package name completion.\r\n\r\n\r\n    commands\r\n    =========\r\n\r\n        :AptCompleteOn   # turn deb package completion on\r\n        :AptCompleteOff  # turn deb package completion off (set `completefunc` back)\r\n        :AptCompleteToggle\r\n","4":"    apt-complete.vim\r\n    ============\r\n    provide deb package name completion.\r\n\r\n\r\n    commands\r\n    =========\r\n\r\n        :AptCompleteOn   # turn deb package completion on\r\n        :AptCompleteOff  # turn deb package completion off (set `completefunc` back)\r\n        :AptCompleteToggle\r\n","install_details":"    put plugin\/aptcomplete.vim to your ~\/.vim\/plugin\/","5":"    put plugin\/aptcomplete.vim to your ~\/.vim\/plugin\/","first_name":"Yo-An","6":"Yo-An","last_name":"Lin","7":"Lin","releases":[{"0":"2925","vim_version":"7.2","1":"7.2","script_version":"0.14","2":"0.14","version_comment":"option for enable aptcomplete by default.\n","3":"option for enable aptcomplete by default.\n","package":"apt-complete-vim-0.14.tar.gz","4":"apt-complete-vim-0.14.tar.gz","src_id":"12106","5":"12106","creation_date":"1263495268","6":"1263495268"},{"0":"2925","vim_version":"7.2","1":"7.2","script_version":"0.13","2":"0.13","version_comment":"fix toggle function.\n(This package is released by VIM::Packager http:\/\/github.com\/c9s\/vim-packager)\n","3":"fix toggle function.\n(This package is released by VIM::Packager http:\/\/github.com\/c9s\/vim-packager)\n","package":"apt-complete-vim-0.13.tar.gz","4":"apt-complete-vim-0.13.tar.gz","src_id":"12094","5":"12094","creation_date":"1263478862","6":"1263478862"},{"0":"2925","vim_version":"7.2","1":"7.2","script_version":"0.11","2":"0.11","version_comment":"add toggle command.\n(This package is released by VIM::Packager http:\/\/github.com\/c9s\/vim-packager)\n","3":"add toggle command.\n(This package is released by VIM::Packager http:\/\/github.com\/c9s\/vim-packager)\n","package":"apt-complete-vim-0.11.tar.gz","4":"apt-complete-vim-0.11.tar.gz","src_id":"12092","5":"12092","creation_date":"1263477547","6":"1263477547"},{"0":"2925","vim_version":"7.2","1":"7.2","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"apt-complete-vim-0.1.tar.gz","4":"apt-complete-vim-0.1.tar.gz","src_id":"12090","5":"12090","creation_date":"1263477199","6":"1263477199"}]},"2924":{"script_id":"2924","0":"2924","script_name":"tocterm","1":"tocterm","script_type":"utility","2":"utility","summary":"Utitliy to add cterm support to color schemes without the GUIColorSchemes plugin","3":"Utitliy to add cterm support to color schemes without the GUIColorSchemes plugin","description":"Script to add cterm support to color schemes without the need for the GUIColorSchemes plugin\r\n\r\nDetails, Installation and Usage: http:\/\/shawnbiddle.com\/toCterm\r\n\r\nNote: The utlity will only convert HTML colors. Named colors (Grey, Green, etc.) will not be translated to cterm.\r\nNote #2: Depending on the speed of your machine and the size of your colorscheme the script may take a while.","4":"Script to add cterm support to color schemes without the need for the GUIColorSchemes plugin\r\n\r\nDetails, Installation and Usage: http:\/\/shawnbiddle.com\/toCterm\r\n\r\nNote: The utlity will only convert HTML colors. Named colors (Grey, Green, etc.) will not be translated to cterm.\r\nNote #2: Depending on the speed of your machine and the size of your colorscheme the script may take a while.","install_details":"","5":"","first_name":"Shawn","6":"Shawn","last_name":"Biddle","7":"Biddle","releases":[{"0":"2924","vim_version":"7.0","1":"7.0","script_version":"1.1","2":"1.1","version_comment":"Renamed the xterm executable to prevent any conflicts with real xterm","3":"Renamed the xterm executable to prevent any conflicts with real xterm","package":"tocterm.tar.gz","4":"tocterm.tar.gz","src_id":"13955","5":"13955","creation_date":"1285767938","6":"1285767938"},{"0":"2924","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"tocterm.tar.gz","4":"tocterm.tar.gz","src_id":"12087","5":"12087","creation_date":"1263404483","6":"1263404483"}]},"2923":{"script_id":"2923","0":"2923","script_name":"std.vim","1":"std.vim","script_type":"utility","2":"utility","summary":"standard util vim functions","3":"standard util vim functions","description":"standard util vim functions for reducing duplicated function code in each plugin ,  this vim function library is in progress. patches are welcome.\r\n","4":"standard util vim functions for reducing duplicated function code in each plugin ,  this vim function library is in progress. patches are welcome.\r\n","install_details":"see http:\/\/github.com\/c9s\/std.vim\/","5":"see http:\/\/github.com\/c9s\/std.vim\/","first_name":"Yo-An","6":"Yo-An","last_name":"Lin","7":"Lin","releases":[{"0":"2923","vim_version":"7.2","1":"7.2","script_version":"0.22","2":"0.22","version_comment":"update doc.\n(released by VIM::Packager http:\/\/github.com\/c9s\/vim-packager)\n","3":"update doc.\n(released by VIM::Packager http:\/\/github.com\/c9s\/vim-packager)\n","package":"std-vim-0.22.tar.gz","4":"std-vim-0.22.tar.gz","src_id":"12048","5":"12048","creation_date":"1263105029","6":"1263105029"},{"0":"2923","vim_version":"7.2","1":"7.2","script_version":"0.2","2":"0.2","version_comment":"Initial upload","3":"Initial upload","package":"std-vim-0.2.tar.gz","4":"std-vim-0.2.tar.gz","src_id":"12047","5":"12047","creation_date":"1263104262","6":"1263104262"}]},"2922":{"script_id":"2922","0":"2922","script_name":"vimomni","1":"vimomni","script_type":"ftplugin","2":"ftplugin","summary":"omni completion for VimL","3":"omni completion for VimL","description":"please see:    http:\/\/github.com\/c9s\/vimomni.vim\r\n","4":"please see:    http:\/\/github.com\/c9s\/vimomni.vim\r\n","install_details":"    see:\r\n    http:\/\/github.com\/c9s\/vimomni.vim","5":"    see:\r\n    http:\/\/github.com\/c9s\/vimomni.vim","first_name":"Yo-An","6":"Yo-An","last_name":"Lin","7":"Lin","releases":[{"0":"2922","vim_version":"7.2","1":"7.2","script_version":"0.22","2":"0.22","version_comment":"* check -complete= case\n(This package is released by VIM::Packager http:\/\/github.com\/c9s\/vim-packager)\n","3":"* check -complete= case\n(This package is released by VIM::Packager http:\/\/github.com\/c9s\/vim-packager)\n","package":"vimomni-vim-0.22.tar.gz","4":"vimomni-vim-0.22.tar.gz","src_id":"12078","5":"12078","creation_date":"1263322410","6":"1263322410"},{"0":"2922","vim_version":"7.2","1":"7.2","script_version":"0.21","2":"0.21","version_comment":"* add map arguments completion support.\n* complete command name after a mapping command.\n(This package is released by VIM::Packager http:\/\/github.com\/c9s\/vim-packager)\n","3":"* add map arguments completion support.\n* complete command name after a mapping command.\n(This package is released by VIM::Packager http:\/\/github.com\/c9s\/vim-packager)\n","package":"vimomni-vim-0.21.tar.gz","4":"vimomni-vim-0.21.tar.gz","src_id":"12077","5":"12077","creation_date":"1263322112","6":"1263322112"},{"0":"2922","vim_version":"7.2","1":"7.2","script_version":"0.2","2":"0.2","version_comment":"sorry for debug code.\n(This package is released by VIM::Packager http:\/\/github.com\/c9s\/vim-packager)\n","3":"sorry for debug code.\n(This package is released by VIM::Packager http:\/\/github.com\/c9s\/vim-packager)\n","package":"vimlomni-vim-0.2.tar.gz","4":"vimlomni-vim-0.2.tar.gz","src_id":"12071","5":"12071","creation_date":"1263209722","6":"1263209722"},{"0":"2922","vim_version":"7.2","1":"7.2","script_version":"0.19","2":"0.19","version_comment":"addmore command attributes.\n(This package is released by VIM::Packager http:\/\/github.com\/c9s\/vim-packager)\n","3":"addmore command attributes.\n(This package is released by VIM::Packager http:\/\/github.com\/c9s\/vim-packager)\n","package":"vimlomni-vim-0.19.tar.gz","4":"vimlomni-vim-0.19.tar.gz","src_id":"12070","5":"12070","creation_date":"1263209418","6":"1263209418"},{"0":"2922","vim_version":"7.2","1":"7.2","script_version":"0.18","2":"0.18","version_comment":"add command argument completion support.\n(This package is released by VIM::Packager http:\/\/github.com\/c9s\/vim-packager)\n","3":"add command argument completion support.\n(This package is released by VIM::Packager http:\/\/github.com\/c9s\/vim-packager)\n","package":"vimlomni-vim-0.18.tar.gz","4":"vimlomni-vim-0.18.tar.gz","src_id":"12069","5":"12069","creation_date":"1263209021","6":"1263209021"},{"0":"2922","vim_version":"7.2","1":"7.2","script_version":"0.17","2":"0.17","version_comment":"foldmarker fixed\n(This package is released by VIM::Packager http:\/\/github.com\/c9s\/vim-packager)\n","3":"foldmarker fixed\n(This package is released by VIM::Packager http:\/\/github.com\/c9s\/vim-packager)\n","package":"vimlomni-vim-0.17.tar.gz","4":"vimlomni-vim-0.17.tar.gz","src_id":"12068","5":"12068","creation_date":"1263207526","6":"1263207526"},{"0":"2922","vim_version":"7.2","1":"7.2","script_version":"0.16","2":"0.16","version_comment":"add autoload prefix completion.\n(This package is released by VIM::Packager http:\/\/github.com\/c9s\/vim-packager)\n","3":"add autoload prefix completion.\n(This package is released by VIM::Packager http:\/\/github.com\/c9s\/vim-packager)\n","package":"vimlomni-vim-0.16.tar.gz","4":"vimlomni-vim-0.16.tar.gz","src_id":"12066","5":"12066","creation_date":"1263195234","6":"1263195234"},{"0":"2922","vim_version":"7.2","1":"7.2","script_version":"0.15","2":"0.15","version_comment":"* add autocommand event name completion support.\n* add feature name completion support.\n(This package is released by VIM::Packager http:\/\/github.com\/c9s\/vim-packager)\n","3":"* add autocommand event name completion support.\n* add feature name completion support.\n(This package is released by VIM::Packager http:\/\/github.com\/c9s\/vim-packager)\n","package":"vimlomni-vim-0.15.tar.gz","4":"vimlomni-vim-0.15.tar.gz","src_id":"12065","5":"12065","creation_date":"1263173544","6":"1263173544"},{"0":"2922","vim_version":"7.2","1":"7.2","script_version":"0.14","2":"0.14","version_comment":"more context checking\n(VIM::Packager http:\/\/github.com\/c9s\/vim-packager)\n","3":"more context checking\n(VIM::Packager http:\/\/github.com\/c9s\/vim-packager)\n","package":"vimlomni-vim-0.14.tar.gz","4":"vimlomni-vim-0.14.tar.gz","src_id":"12045","5":"12045","creation_date":"1263092012","6":"1263092012"},{"0":"2922","vim_version":"7.2","1":"7.2","script_version":"0.13","2":"0.13","version_comment":"context fix\n(This package is released by VIM::Packager http:\/\/github.com\/c9s\/vim-packager)\n","3":"context fix\n(This package is released by VIM::Packager http:\/\/github.com\/c9s\/vim-packager)\n","package":"vimlomni-vim-0.13.tar.gz","4":"vimlomni-vim-0.13.tar.gz","src_id":"12044","5":"12044","creation_date":"1263091136","6":"1263091136"},{"0":"2922","vim_version":"7.2","1":"7.2","script_version":"0.12","2":"0.12","version_comment":"update.\n(This package is released by VIM::Packager http:\/\/github.com\/c9s\/vim-packager)\n","3":"update.\n(This package is released by VIM::Packager http:\/\/github.com\/c9s\/vim-packager)\n","package":"vimlomni-vim-0.12.tar.gz","4":"vimlomni-vim-0.12.tar.gz","src_id":"12042","5":"12042","creation_date":"1263090320","6":"1263090320"},{"0":"2922","vim_version":"7.2","1":"7.2","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"vimomni-vim-0.1.tar.gz","4":"vimomni-vim-0.1.tar.gz","src_id":"12037","5":"12037","creation_date":"1263049859","6":"1263049859"}]},"2921":{"script_id":"2921","0":"2921","script_name":"FirstEffectiveLine.vim","1":"FirstEffectiveLine.vim","script_type":"utility","2":"utility","summary":"Go to the first effective(non-comment) line of the file","3":"Go to the first effective(non-comment) line of the file","description":"This plugin provides a normal mode command 'gG', which moves to the first\r\neffective line of the current file.\r\nIn this script, \"effective line\" means a line whose first character is\r\nnot a comment nor a preprocessor nor empty.\r\n\r\nIf you want to map the command to another keys than 'gG', add a line like below\r\nin your vimrc.\r\n  nmap YOURKEY <Plug>GotoFirstEffectiveLine\r\n","4":"This plugin provides a normal mode command 'gG', which moves to the first\r\neffective line of the current file.\r\nIn this script, \"effective line\" means a line whose first character is\r\nnot a comment nor a preprocessor nor empty.\r\n\r\nIf you want to map the command to another keys than 'gG', add a line like below\r\nin your vimrc.\r\n  nmap YOURKEY <Plug>GotoFirstEffectiveLine\r\n","install_details":"Place this file in \/usr\/share\/vim\/vim*\/plugin or ~\/.vim\/plugin\/\r\n","5":"Place this file in \/usr\/share\/vim\/vim*\/plugin or ~\/.vim\/plugin\/\r\n","first_name":"Takahiro","6":"Takahiro","last_name":"SUZUKI","7":"SUZUKI","releases":[{"0":"2921","vim_version":"7.0","1":"7.0","script_version":"1.0.0","2":"1.0.0","version_comment":"Initial upload","3":"Initial upload","package":"FirstEffectiveLine.vim","4":"FirstEffectiveLine.vim","src_id":"12028","5":"12028","creation_date":"1262902758","6":"1262902758"}]},"2920":{"script_id":"2920","0":"2920","script_name":"Mercury compiler support","1":"Mercury compiler support","script_type":"utility","2":"utility","summary":"Ftplugin, syntax and supplemental plugin for Mercury compiler","3":"Ftplugin, syntax and supplemental plugin for Mercury compiler","description":"This is a set of Vim plugins to simplify work with Mercury language compiler\r\n(http:\/\/www.mercury.csse.unimelb.edu.au)\r\nNative Mercury installer for Windows can be found here: \r\nhttp:\/\/code.google.com\/p\/winmercury\r\n\r\nFiletype plugin is a modified version of ftplugin from officical Mercury distribution. Syntax plugin is a copy of official plugin\r\n\r\nmercury_commands plugin provides convenience commands for Mercury compiler:\r\n\r\n:Mmc [arg1]... - Invoke compiler (mmc), using current file when no arguments passed.\r\n:Mmake [arg1]... - Invoke mmake (mmake.bat on Windows).\r\n:Mmerr - Show last output from :Mmc or :Mmake.\r\n:Mmod name [interface_imports]\r\n:Mmod name {interfaceimports} [implementation_imports] - Insert module template, interface_imports and implementation_imports are comma-separated lists of modules.\r\n:Mmain name [interface_imports]\r\n:Mmain name {interfaceimports} [implementation_imports] - Insert module template containing the `main' predicate\r\n\r\nI am not actively using and developing it anymore. Feel free to fork it on https:\/\/bitbucket.org\/khorser\/vim-mercury or https:\/\/github.com\/khorser\/vim-mercury","4":"This is a set of Vim plugins to simplify work with Mercury language compiler\r\n(http:\/\/www.mercury.csse.unimelb.edu.au)\r\nNative Mercury installer for Windows can be found here: \r\nhttp:\/\/code.google.com\/p\/winmercury\r\n\r\nFiletype plugin is a modified version of ftplugin from officical Mercury distribution. Syntax plugin is a copy of official plugin\r\n\r\nmercury_commands plugin provides convenience commands for Mercury compiler:\r\n\r\n:Mmc [arg1]... - Invoke compiler (mmc), using current file when no arguments passed.\r\n:Mmake [arg1]... - Invoke mmake (mmake.bat on Windows).\r\n:Mmerr - Show last output from :Mmc or :Mmake.\r\n:Mmod name [interface_imports]\r\n:Mmod name {interfaceimports} [implementation_imports] - Insert module template, interface_imports and implementation_imports are comma-separated lists of modules.\r\n:Mmain name [interface_imports]\r\n:Mmain name {interfaceimports} [implementation_imports] - Insert module template containing the `main' predicate\r\n\r\nI am not actively using and developing it anymore. Feel free to fork it on https:\/\/bitbucket.org\/khorser\/vim-mercury or https:\/\/github.com\/khorser\/vim-mercury","install_details":"It is packed as a Vimball, so do steps below:\r\nvim Mercury.vba\r\n:so %\r\n:q\r\n","5":"It is packed as a Vimball, so do steps below:\r\nvim Mercury.vba\r\n:so %\r\n:q\r\n","first_name":"Sergey","6":"Sergey","last_name":"Khorev","7":"Khorev","releases":[{"0":"2920","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"Mercury.vba","4":"Mercury.vba","src_id":"12025","5":"12025","creation_date":"1262881163","6":"1262881163"}]},"2919":{"script_id":"2919","0":"2919","script_name":"Preamble","1":"Preamble","script_type":"utility","2":"utility","summary":"Automatically folds long licensing and copyright preambles that head sources.","3":"Automatically folds long licensing and copyright preambles that head sources.","description":"This plugin will automatically fold long preambles, such as GPL copyright\r\nnotices, located at the head of source files.  You may find it helpful if,\r\nlike me, you use syntax folding infrequently. \r\n\r\nVery often, I read third-party library sources and examples, such as Nokia's\r\nQt library, various GNU utilities, and many others.  I want to see the \r\nfunctions and read the comments but not the 50 lines of licensing and \r\ncopyright notices that head every file. Because these are third-party \r\nsources, I do not want to modify the files to include Vim fold markers.\r\n\r\nWHAT IT DOES:\r\n\r\nThis plugin does not use fold markers and does not modify files.\r\nIt adds the fold by changing the foldmethod to \"manual\" and inserting a \r\nmanual fold. \r\n\r\nIf the foldmethod is 'syntax', the plugin will do nothing except try to \r\nclose the fold on line 1, if one exists.  No fold is created and the\r\nfoldmethod is not changed.\r\n\r\nThe preamble has to start at the top of the file, but may be preceded by \r\nempty lines.  It will consist of leading blank lines followed by lines \r\nwith comments starting in column one. The preamble will stop at the first line\r\nnot having a comment in the first column.  \r\n\r\nNote: If the preamble uses 'c' style comments without a border of characters\r\nin column 1 the preamble will not be recognized. \r\n\r\n","4":"This plugin will automatically fold long preambles, such as GPL copyright\r\nnotices, located at the head of source files.  You may find it helpful if,\r\nlike me, you use syntax folding infrequently. \r\n\r\nVery often, I read third-party library sources and examples, such as Nokia's\r\nQt library, various GNU utilities, and many others.  I want to see the \r\nfunctions and read the comments but not the 50 lines of licensing and \r\ncopyright notices that head every file. Because these are third-party \r\nsources, I do not want to modify the files to include Vim fold markers.\r\n\r\nWHAT IT DOES:\r\n\r\nThis plugin does not use fold markers and does not modify files.\r\nIt adds the fold by changing the foldmethod to \"manual\" and inserting a \r\nmanual fold. \r\n\r\nIf the foldmethod is 'syntax', the plugin will do nothing except try to \r\nclose the fold on line 1, if one exists.  No fold is created and the\r\nfoldmethod is not changed.\r\n\r\nThe preamble has to start at the top of the file, but may be preceded by \r\nempty lines.  It will consist of leading blank lines followed by lines \r\nwith comments starting in column one. The preamble will stop at the first line\r\nnot having a comment in the first column.  \r\n\r\nNote: If the preamble uses 'c' style comments without a border of characters\r\nin column 1 the preamble will not be recognized. \r\n\r\n","install_details":"The vimball archive contains 2 files:   \r\n    autoload\/Preamble.vim\r\n    doc\/Preamble.txt\r\n\r\nInstall using the Vimball plugin by typing:\r\n    vim Preamble.vba\r\n       :so % \r\n       :q \r\n\r\nFor automatic folding, add a line to your .vimrc file, such as:\r\n    call Preamble#Enable('cpp,java')\r\n\r\nFor more info on usage and options, type:   :help preamble","5":"The vimball archive contains 2 files:   \r\n    autoload\/Preamble.vim\r\n    doc\/Preamble.txt\r\n\r\nInstall using the Vimball plugin by typing:\r\n    vim Preamble.vba\r\n       :so % \r\n       :q \r\n\r\nFor automatic folding, add a line to your .vimrc file, such as:\r\n    call Preamble#Enable('cpp,java')\r\n\r\nFor more info on usage and options, type:   :help preamble","first_name":"Mel","6":"Mel","last_name":"Davis","7":"Davis","releases":[{"0":"2919","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"Preamble.vba","4":"Preamble.vba","src_id":"12021","5":"12021","creation_date":"1262806691","6":"1262806691"}]},"2918":{"script_id":"2918","0":"2918","script_name":"SpitVspit","1":"SpitVspit","script_type":"utility","2":"utility","summary":"Powerful multiple files splitting.","3":"Powerful multiple files splitting.","description":"This is a little script I did because I have always wanted to type\r\n\r\n:sp a.cpp b.hpp *.tex......\r\n\r\nSo... This does it now!\r\n\r\nYou just have to put this file in the plugin directory and the help in the doc directory and that will remap sp and vsp abbreviation to my function, allowing you to type :vsp *.txt\r\n\r\nLet me know if you find some bugs ;-)","4":"This is a little script I did because I have always wanted to type\r\n\r\n:sp a.cpp b.hpp *.tex......\r\n\r\nSo... This does it now!\r\n\r\nYou just have to put this file in the plugin directory and the help in the doc directory and that will remap sp and vsp abbreviation to my function, allowing you to type :vsp *.txt\r\n\r\nLet me know if you find some bugs ;-)","install_details":"I don't know about what came in which version (I run the latest), but the commands you need for my script are very basic and I think they are in Vim for a long time now:\r\n- (v)split\r\n- substitute\r\n- command\r\n- cabclear\r\n- splitright\/splitbelow\r\n- args\/argadd\r\n- expand\r\n- next","5":"I don't know about what came in which version (I run the latest), but the commands you need for my script are very basic and I think they are in Vim for a long time now:\r\n- (v)split\r\n- substitute\r\n- command\r\n- cabclear\r\n- splitright\/splitbelow\r\n- args\/argadd\r\n- expand\r\n- next","first_name":"Ga\u00c3\u00abl","6":"Ga\u00c3\u00abl","last_name":"Induni","7":"Induni","releases":[{"0":"2918","vim_version":"7.0","1":"7.0","script_version":"2.2","2":"2.2","version_comment":"Enabling calling Spit with a count to act like :5split","3":"Enabling calling Spit with a count to act like :5split","package":"SpitVspit_2_2.tar.gz","4":"SpitVspit_2_2.tar.gz","src_id":"18019","5":"18019","creation_date":"1337777554","6":"1337777554"},{"0":"2918","vim_version":"7.0","1":"7.0","script_version":"2.1.3","2":"2.1.3","version_comment":"Replaced almost all single-quoted string with double-quoted ones","3":"Replaced almost all single-quoted string with double-quoted ones","package":"SpitVspit_2_1_3.tar.gz","4":"SpitVspit_2_1_3.tar.gz","src_id":"17509","5":"17509","creation_date":"1329815490","6":"1329815490"},{"0":"2918","vim_version":"7.0","1":"7.0","script_version":"2.1.1","2":"2.1.1","version_comment":"Added help for Wspit command","3":"Added help for Wspit command","package":"SpitVspit_2_1_1.tar.gz","4":"SpitVspit_2_1_1.tar.gz","src_id":"14940","5":"14940","creation_date":"1296660328","6":"1296660328"},{"0":"2918","vim_version":"7.0","1":"7.0","script_version":"2.1","2":"2.1","version_comment":"New feature: Wspit with multiple arguments makes vsplit for the first and split the following. Try it yourself ;-)","3":"New feature: Wspit with multiple arguments makes vsplit for the first and split the following. Try it yourself ;-)","package":"SpitVspit_2_1.tar.gz","4":"SpitVspit_2_1.tar.gz","src_id":"14893","5":"14893","creation_date":"1296203930","6":"1296203930"},{"0":"2918","vim_version":"7.0","1":"7.0","script_version":"2.0.6","2":"2.0.6","version_comment":"Fixed bug with regexp * character, prevent split the current file when using *.smth","3":"Fixed bug with regexp * character, prevent split the current file when using *.smth","package":"SpitVspit.tar.gz","4":"SpitVspit.tar.gz","src_id":"14655","5":"14655","creation_date":"1293657126","6":"1293657126"},{"0":"2918","vim_version":"7.0","1":"7.0","script_version":"2.0.5","2":"2.0.5","version_comment":"Minor bugs fixed.","3":"Minor bugs fixed.","package":"SpitVspit.tar.gz","4":"SpitVspit.tar.gz","src_id":"14578","5":"14578","creation_date":"1292769837","6":"1292769837"},{"0":"2918","vim_version":"7.0","1":"7.0","script_version":"2.0.4","2":"2.0.4","version_comment":"GetLatestVimScript compatible.","3":"GetLatestVimScript compatible.","package":"SpitVspit.tar.gz","4":"SpitVspit.tar.gz","src_id":"14577","5":"14577","creation_date":"1292769112","6":"1292769112"},{"0":"2918","vim_version":"7.0","1":"7.0","script_version":"2.0.3","2":"2.0.3","version_comment":"Fixed some bugs caused by misuse of match(). Keeps all the already present args.","3":"Fixed some bugs caused by misuse of match(). Keeps all the already present args.","package":"SpitVspit.tar.gz","4":"SpitVspit.tar.gz","src_id":"14544","5":"14544","creation_date":"1292589516","6":"1292589516"},{"0":"2918","vim_version":"7.0","1":"7.0","script_version":"2.0.2","2":"2.0.2","version_comment":"When using E, keeps the current files in args. Added help file.","3":"When using E, keeps the current files in args. Added help file.","package":"SpitVspit.tar.gz","4":"SpitVspit.tar.gz","src_id":"14532","5":"14532","creation_date":"1292513906","6":"1292513906"},{"0":"2918","vim_version":"7.0","1":"7.0","script_version":"2.0.1","2":"2.0.1","version_comment":"Added global variable to prevent many loadings.","3":"Added global variable to prevent many loadings.","package":"SpitVspit.vim","4":"SpitVspit.vim","src_id":"14526","5":"14526","creation_date":"1292482207","6":"1292482207"},{"0":"2918","vim_version":"7.0","1":"7.0","script_version":"2.0","2":"2.0","version_comment":"Completely rewritten the script to use only one function using more arguments. New features: command :e also supported in the same way (using *.m or creating new files).","3":"Completely rewritten the script to use only one function using more arguments. New features: command :e also supported in the same way (using *.m or creating new files).","package":"SpitVspit.vim","4":"SpitVspit.vim","src_id":"14518","5":"14518","creation_date":"1292398672","6":"1292398672"},{"0":"2918","vim_version":"7.0","1":"7.0","script_version":"1.2","2":"1.2","version_comment":"Fixed minor bugs with spitup\/down and vspitleft\/right","3":"Fixed minor bugs with spitup\/down and vspitleft\/right","package":"SpitVspit.vim","4":"SpitVspit.vim","src_id":"14432","5":"14432","creation_date":"1291453738","6":"1291453738"},{"0":"2918","vim_version":"5.7","1":"5.7","script_version":"1.1","2":"1.1","version_comment":"New features: SpitUp (spu), SpitDown (spd), VspitLeft (vspl) and VspitRight (vspr) allow you to choose where to split if you want... Otherwise there are still the usual Spit and Vspit functions that work according to your settings in your vimrc about the splitright and splitbelow parameters.","3":"New features: SpitUp (spu), SpitDown (spd), VspitLeft (vspl) and VspitRight (vspr) allow you to choose where to split if you want... Otherwise there are still the usual Spit and Vspit functions that work according to your settings in your vimrc about the splitright and splitbelow parameters.","package":"SpitVspit.vim","4":"SpitVspit.vim","src_id":"12348","5":"12348","creation_date":"1265724284","6":"1265724284"},{"0":"2918","vim_version":"5.7","1":"5.7","script_version":"1.0.1","2":"1.0.1","version_comment":"Fixed bug: cannot split with files that does not exist.","3":"Fixed bug: cannot split with files that does not exist.","package":"SpitVspit.vim","4":"SpitVspit.vim","src_id":"12027","5":"12027","creation_date":"1262889421","6":"1262889421"},{"0":"2918","vim_version":"5.7","1":"5.7","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"SpitVspit.vim","4":"SpitVspit.vim","src_id":"12017","5":"12017","creation_date":"1262722760","6":"1262722760"}]},"2917":{"script_id":"2917","0":"2917","script_name":"tplugin","1":"tplugin","script_type":"utility","2":"utility","summary":"A plugin loader\/runtimepath manager with autoload capabilities","3":"A plugin loader\/runtimepath manager with autoload capabilities","description":"tplugin is a plugin management tool similar to pathogen. Other than \r\npathogen tplugin expands the 'runtimepath' as needed (e.g. when \r\ncalling a command or function that is defined in a bundle) in order to \r\nhave minimal impact on startup time.\r\n\r\nThis plugin helps users to deal with plugins that are distributed via \r\nsource code repositories. Usually, you would make those plugins \r\navailable to vim by adding the local copies of those repositories to \r\n|runtimepath|. The disadvantage of this approach is that the value of \r\n|runtimepath| becomes unnecessarily complex and that the plugins are \r\nloaded on startup.\r\n\r\ntplugin scans those plugins for commands and functions. It then amends \r\nthe |runtimepath| only if a respective command\/function\/map is called \r\n(similar to the AsNeeded plugin). This helps to keep your |runtimepath| \r\nsimple and to improve startup time.\r\n\r\nIn order to achieve this goal, plugins are installed in an alternative \r\ndirectory structure where each plugin (consequently referred to as \r\n\"repo\") is installed in a subdirectory. tplugin takes care of modifying \r\n'runtimepath' and of loading the vim script files as necessary.\r\n\r\nAlternative directory layout:\r\n\r\n    ROOT\/\r\n      repo1\/\r\n        after\/\r\n        autoload\/\r\n        doc\/\r\n        plugin\/\r\n      repo2\/\r\n        after\/\r\n        autoload\/\r\n        doc\/\r\n        plugin\/\r\n      ...\r\n\r\nRepos can be enabled (i.e. added to 'runtimepath') either explicitly \r\nwith the |:TPlugin| command or automatically by calling a command, \r\nfunction, or by requesting a filetype plugin\/syntax\/indent file defined \r\nin a repo -- this is done similar to how AsNeeded autoloads files.\r\n\r\nFull docs:\r\nhttp:\/\/github.com\/tomtom\/tplugin_vim\/blob\/master\/doc\/tplugin.txt","4":"tplugin is a plugin management tool similar to pathogen. Other than \r\npathogen tplugin expands the 'runtimepath' as needed (e.g. when \r\ncalling a command or function that is defined in a bundle) in order to \r\nhave minimal impact on startup time.\r\n\r\nThis plugin helps users to deal with plugins that are distributed via \r\nsource code repositories. Usually, you would make those plugins \r\navailable to vim by adding the local copies of those repositories to \r\n|runtimepath|. The disadvantage of this approach is that the value of \r\n|runtimepath| becomes unnecessarily complex and that the plugins are \r\nloaded on startup.\r\n\r\ntplugin scans those plugins for commands and functions. It then amends \r\nthe |runtimepath| only if a respective command\/function\/map is called \r\n(similar to the AsNeeded plugin). This helps to keep your |runtimepath| \r\nsimple and to improve startup time.\r\n\r\nIn order to achieve this goal, plugins are installed in an alternative \r\ndirectory structure where each plugin (consequently referred to as \r\n\"repo\") is installed in a subdirectory. tplugin takes care of modifying \r\n'runtimepath' and of loading the vim script files as necessary.\r\n\r\nAlternative directory layout:\r\n\r\n    ROOT\/\r\n      repo1\/\r\n        after\/\r\n        autoload\/\r\n        doc\/\r\n        plugin\/\r\n      repo2\/\r\n        after\/\r\n        autoload\/\r\n        doc\/\r\n        plugin\/\r\n      ...\r\n\r\nRepos can be enabled (i.e. added to 'runtimepath') either explicitly \r\nwith the |:TPlugin| command or automatically by calling a command, \r\nfunction, or by requesting a filetype plugin\/syntax\/indent file defined \r\nin a repo -- this is done similar to how AsNeeded autoloads files.\r\n\r\nFull docs:\r\nhttp:\/\/github.com\/tomtom\/tplugin_vim\/blob\/master\/doc\/tplugin.txt","install_details":"Edit the vba file and type: >\r\n\r\n    :so %\r\n\r\nSee :help vimball for details. If you have difficulties or use vim 7.0, \r\nplease make sure, you have the current version of vimball\r\n(vimscript #1502) installed or update your runtime.\r\n\r\nGetting started:\r\n\r\n    1. Add this to your vimrc file:\r\n\r\n        runtime macros\/tplugin.vim\r\n        \" Only necessary if you use a non-standard root directory\r\n        TPluginRoot \/home\/x\/src\/repos\r\n\r\n    2. Install your plugins\/repos in the root directory.\r\n\r\n    3. After restarting vim, type :TPluginScan!\r\n\r\nAlso available as git repository:\r\nhttp:\/\/github.com\/tomtom\/tplugin_vim","5":"Edit the vba file and type: >\r\n\r\n    :so %\r\n\r\nSee :help vimball for details. If you have difficulties or use vim 7.0, \r\nplease make sure, you have the current version of vimball\r\n(vimscript #1502) installed or update your runtime.\r\n\r\nGetting started:\r\n\r\n    1. Add this to your vimrc file:\r\n\r\n        runtime macros\/tplugin.vim\r\n        \" Only necessary if you use a non-standard root directory\r\n        TPluginRoot \/home\/x\/src\/repos\r\n\r\n    2. Install your plugins\/repos in the root directory.\r\n\r\n    3. After restarting vim, type :TPluginScan!\r\n\r\nAlso available as git repository:\r\nhttp:\/\/github.com\/tomtom\/tplugin_vim","first_name":"Tom","6":"Tom","last_name":"Link","7":"Link","releases":[{"0":"2917","vim_version":"7.0","1":"7.0","script_version":"1.00","2":"1.00","version_comment":"- Don't try to run :helptags on directories with no text files\n- g:tplugin#show_helptags_errors: If true, show errors when running :helptags.\n- Support for extradite\n- TPluginVimEnter(): :do VimEnter commands only if such autocommands are defined\n- Make sure to register repos with no plugin file\n- Autoload: Ignore E121 errors (local variables) and echo v:exception on errors\n- g:tplugin#show_helptags_errors: If true, show errors when running helptags\nMD5 checksum: 7c454f3a1f0a380743d5dcb39cfae912","3":"- Don't try to run :helptags on directories with no text files\n- g:tplugin#show_helptags_errors: If true, show errors when running :helptags.\n- Support for extradite\n- TPluginVimEnter(): :do VimEnter commands only if such autocommands are defined\n- Make sure to register repos with no plugin file\n- Autoload: Ignore E121 errors (local variables) and echo v:exception on errors\n- g:tplugin#show_helptags_errors: If true, show errors when running helptags\nMD5 checksum: 7c454f3a1f0a380743d5dcb39cfae912","package":"tplugin.vba","4":"tplugin.vba","src_id":"19016","5":"19016","creation_date":"1353615572","6":"1353615572"},{"0":"2917","vim_version":"7.0","1":"7.0","script_version":"0.14","2":"0.14","version_comment":"- TPluginRegisterPlugin works again\n- TPluginRoot!: With bang, mark this root for shallow scans\n- Speed up scanning of \"shallow roots\"\nMD5 checksum: fba3e4a4fad872e074f76dd3988c2cb3","3":"- TPluginRegisterPlugin works again\n- TPluginRoot!: With bang, mark this root for shallow scans\n- Speed up scanning of \"shallow roots\"\nMD5 checksum: fba3e4a4fad872e074f76dd3988c2cb3","package":"tplugin.vba","4":"tplugin.vba","src_id":"17288","5":"17288","creation_date":"1327167728","6":"1327167728"},{"0":"2917","vim_version":"7.0","1":"7.0","script_version":"0.13","2":"0.13","version_comment":"- Fix message when rescanning roots due to outdated meta files; rescan only once\nMD5 checksum: 395629f472fea537b25cfb12ae01f829","3":"- Fix message when rescanning roots due to outdated meta files; rescan only once\nMD5 checksum: 395629f472fea537b25cfb12ae01f829","package":"tplugin.vba","4":"tplugin.vba","src_id":"17075","5":"17075","creation_date":"1324110023","6":"1324110023"},{"0":"2917","vim_version":"7.0","1":"7.0","script_version":"0.12","2":"0.12","version_comment":"- Run helptags with silent!\n- vcsdo: Finalize the name of the log buffer as script-local variable\n- Experimental support for <VIMPLUGIN> tags used in vx* plugins.\n- .gitignore\n- Experimental support for parsing *-addon-info.txt and simpler dependency management\n- s:AutoloadFunction(): Properly support autoload funcs in subdirectories\n- &rtp wasn't properly updated in certain situations\n- Experimental: Scan sources for VimEnter autocommands\n- autoload\/tplugin\/vcscommand: Adapt to new arguments\n- FIX: scanning of autocmds: Don't use \\k\n- autoload\/tplugin\/fugitive: Don't call #fugitive_utility#VimEnter\n- SetRoot(): Use inputdialog() to display \"Rescanning roots: Please be patient\" message\n- TPluginRequire: Remove check for s:done[rootrepo] (over-optimization)\n- s:TPluginComplete(): show all known repos as completion candidates\nMD5 checksum: 8ff9f5f7c97d3e306bb543a60cf16271","3":"- Run helptags with silent!\n- vcsdo: Finalize the name of the log buffer as script-local variable\n- Experimental support for <VIMPLUGIN> tags used in vx* plugins.\n- .gitignore\n- Experimental support for parsing *-addon-info.txt and simpler dependency management\n- s:AutoloadFunction(): Properly support autoload funcs in subdirectories\n- &rtp wasn't properly updated in certain situations\n- Experimental: Scan sources for VimEnter autocommands\n- autoload\/tplugin\/vcscommand: Adapt to new arguments\n- FIX: scanning of autocmds: Don't use \\k\n- autoload\/tplugin\/fugitive: Don't call #fugitive_utility#VimEnter\n- SetRoot(): Use inputdialog() to display \"Rescanning roots: Please be patient\" message\n- TPluginRequire: Remove check for s:done[rootrepo] (over-optimization)\n- s:TPluginComplete(): show all known repos as completion candidates\nMD5 checksum: 8ff9f5f7c97d3e306bb543a60cf16271","package":"tplugin.vba","4":"tplugin.vba","src_id":"15733","5":"15733","creation_date":"1306394169","6":"1306394169"},{"0":"2917","vim_version":"7.0","1":"7.0","script_version":"0.11","2":"0.11","version_comment":"Please see http:\/\/github.com\/tomtom\/tplugin_vim\/commits\/master\/","3":"Please see http:\/\/github.com\/tomtom\/tplugin_vim\/commits\/master\/","package":"tplugin.vba","4":"tplugin.vba","src_id":"14160","5":"14160","creation_date":"1288619292","6":"1288619292"},{"0":"2917","vim_version":"7.0","1":"7.0","script_version":"0.10","2":"0.10","version_comment":"- Make helptags of repositories that weren't yet loaded available to the user.\r\n- Renamed variables: g:tplugin#autoload_exclude, g:tplugin#scan\r\n- Custom autoload definitions for some 3rd party plugins (PoC)","3":"- Make helptags of repositories that weren't yet loaded available to the user.\r\n- Renamed variables: g:tplugin#autoload_exclude, g:tplugin#scan\r\n- Custom autoload definitions for some 3rd party plugins (PoC)","package":"tplugin.vba","4":"tplugin.vba","src_id":"13976","5":"13976","creation_date":"1286010539","6":"1286010539"},{"0":"2917","vim_version":"7.0","1":"7.0","script_version":"0.9","2":"0.9","version_comment":"- Renamed #TPluginInclude to @TPluginInclude\r\n- Added support for @TPluginMap, @TPluginBefore, @TPluginAfter annotations\r\n- TPluginMap() restores the proper mode\r\n- Load after\/autoload\/* files\r\n- ...","3":"- Renamed #TPluginInclude to @TPluginInclude\r\n- Added support for @TPluginMap, @TPluginBefore, @TPluginAfter annotations\r\n- TPluginMap() restores the proper mode\r\n- Load after\/autoload\/* files\r\n- ...","package":"tplugin.vba","4":"tplugin.vba","src_id":"13660","5":"13660","creation_date":"1282631139","6":"1282631139"},{"0":"2917","vim_version":"7.0","1":"7.0","script_version":"0.8","2":"0.8","version_comment":"- Delete commands only when they were defined without a bang; make sure all commands in a file defined without a bang are deleted\r\n- g:tplugin_scan defaults to 'cfpt'\r\n- Don't register each autoload function but deduce the repo\/plugin from the prefix.\r\n- g:tplugin_scan defaults to 'cfpta'\r\n- TPluginCommand and TPluginFunction are functions. Removed the commands with the same name.\r\n- #TPluginInclude tag\r\n","3":"- Delete commands only when they were defined without a bang; make sure all commands in a file defined without a bang are deleted\r\n- g:tplugin_scan defaults to 'cfpt'\r\n- Don't register each autoload function but deduce the repo\/plugin from the prefix.\r\n- g:tplugin_scan defaults to 'cfpta'\r\n- TPluginCommand and TPluginFunction are functions. Removed the commands with the same name.\r\n- #TPluginInclude tag\r\n","package":"tplugin.vba","4":"tplugin.vba","src_id":"12831","5":"12831","creation_date":"1271267621","6":"1271267621"},{"0":"2917","vim_version":"7.0","1":"7.0","script_version":"0.7","2":"0.7","version_comment":"- TPluginScan: try to maintain information about command-line completion (this won't work if a custom script-local completion function is used)\r\n","3":"- TPluginScan: try to maintain information about command-line completion (this won't work if a custom script-local completion function is used)\r\n","package":"tplugin.vba.gz","4":"tplugin.vba.gz","src_id":"12443","5":"12443","creation_date":"1266653413","6":"1266653413"},{"0":"2917","vim_version":"7.0","1":"7.0","script_version":"0.6","2":"0.6","version_comment":"- CHANGE: The root specific autoload files are now called '_tplugin.vim'\r\n- Provide a poor-man implementation of fnameescape() for users of older versions of vim.\r\n- If the root name ends with '*', the root is no directory tree but a single directory (actually a plugin repo)\r\n- s:TPluginComplete(): Hide tplugin autoload files.\r\n","3":"- CHANGE: The root specific autoload files are now called '_tplugin.vim'\r\n- Provide a poor-man implementation of fnameescape() for users of older versions of vim.\r\n- If the root name ends with '*', the root is no directory tree but a single directory (actually a plugin repo)\r\n- s:TPluginComplete(): Hide tplugin autoload files.\r\n","package":"tplugin.vba.gz","4":"tplugin.vba.gz","src_id":"12391","5":"12391","creation_date":"1266346528","6":"1266346528"},{"0":"2917","vim_version":"7.0","1":"7.0","script_version":"0.5","2":"0.5","version_comment":"- Support for ftdetect\r\n- Support for ftplugins in directories and named {&FT}_{NAME}.vim\r\n- :TPlugin accepts \"-\" as argument, which means load \"NO PLUGIN\".\r\n- :TPluginScan: don't use full filenames as arguments for TPluginFiletype()\r\n- FIX: Concatenation of filetype-related files\r\n- FIX: Don't add autoload files to the menu.\r\n- FIX: Don't load any plugins when autoloading an \"autoload function\"\r\n- FIX: Filetype-related problems\r\n- FIX: s:ScanLine: Don't create duplicate autoload commands.\r\n- FIX: s:ScanRoots(): Remove empty entries from filelist\r\n- g:tplugin_autoload_exclude: Exclude repos from autoloading\r\n- If g:tplugin_autoload == 2, run |:TPluginScan| after updating tplugin.\r\n- Moved autoload functions to macros\/tplugin.vim -- users have to rescan their repos.\r\n- Per repo metadata (ROOT\/REPO\/tplugin.vim)\r\n- Relaxed the rx for functions\r\n- Replaced :TPluginMap with a function TPluginMap()\r\n- Speed up :TPluginScan (s:ScanRoots(): run glob() only once, filter file contents before passing it to s:ScanSource())\r\n- TPluginMap(): Don't map keys if the key already is mapped (via maparg())\r\n","3":"- Support for ftdetect\r\n- Support for ftplugins in directories and named {&FT}_{NAME}.vim\r\n- :TPlugin accepts \"-\" as argument, which means load \"NO PLUGIN\".\r\n- :TPluginScan: don't use full filenames as arguments for TPluginFiletype()\r\n- FIX: Concatenation of filetype-related files\r\n- FIX: Don't add autoload files to the menu.\r\n- FIX: Don't load any plugins when autoloading an \"autoload function\"\r\n- FIX: Filetype-related problems\r\n- FIX: s:ScanLine: Don't create duplicate autoload commands.\r\n- FIX: s:ScanRoots(): Remove empty entries from filelist\r\n- g:tplugin_autoload_exclude: Exclude repos from autoloading\r\n- If g:tplugin_autoload == 2, run |:TPluginScan| after updating tplugin.\r\n- Moved autoload functions to macros\/tplugin.vim -- users have to rescan their repos.\r\n- Per repo metadata (ROOT\/REPO\/tplugin.vim)\r\n- Relaxed the rx for functions\r\n- Replaced :TPluginMap with a function TPluginMap()\r\n- Speed up :TPluginScan (s:ScanRoots(): run glob() only once, filter file contents before passing it to s:ScanSource())\r\n- TPluginMap(): Don't map keys if the key already is mapped (via maparg())\r\n","package":"tplugin.vba.gz","4":"tplugin.vba.gz","src_id":"12275","5":"12275","creation_date":"1265141223","6":"1265141223"},{"0":"2917","vim_version":"7.0","1":"7.0","script_version":"0.3","2":"0.3","version_comment":"- TPluginBefore, TPluginAfter commands to define inter-repo dependencies\r\n- Support for autoloading filetypes\r\n- Support for autoloading <plug> maps\r\n- Build helptags during :TPluginScan (i.e. support for helptags requires \r\nautoload to be enabled) - Call delcommand before autoloading a plugin because of an unknown command\r\n- TPluginScan: Take a root directory as the second optional argument\r\n- The autoload file was renamed to ROOT\/tplugin.vim\r\n- When adding a repository to &rtp, ROOT\/tplugin_REPO.vim is loaded\r\n","3":"- TPluginBefore, TPluginAfter commands to define inter-repo dependencies\r\n- Support for autoloading filetypes\r\n- Support for autoloading <plug> maps\r\n- Build helptags during :TPluginScan (i.e. support for helptags requires \r\nautoload to be enabled) - Call delcommand before autoloading a plugin because of an unknown command\r\n- TPluginScan: Take a root directory as the second optional argument\r\n- The autoload file was renamed to ROOT\/tplugin.vim\r\n- When adding a repository to &rtp, ROOT\/tplugin_REPO.vim is loaded\r\n","package":"tplugin.vba.gz","4":"tplugin.vba.gz","src_id":"12127","5":"12127","creation_date":"1263930870","6":"1263930870"},{"0":"2917","vim_version":"7.0","1":"7.0","script_version":"0.2","2":"0.2","version_comment":"- Experimental autoload for commands and functions (\u00c3\u00a0 la AsNeeded)\r\n- Improved command-line completion for :TPlugin\r\n- The after path is inserted at the second to last position\r\n- When autoload is enabled and g:tplugin_menu_prefix is not empty, build a menu with available plugins (NOTE: this is disabled by default)\r\n","3":"- Experimental autoload for commands and functions (\u00c3\u00a0 la AsNeeded)\r\n- Improved command-line completion for :TPlugin\r\n- The after path is inserted at the second to last position\r\n- When autoload is enabled and g:tplugin_menu_prefix is not empty, build a menu with available plugins (NOTE: this is disabled by default)\r\n","package":"tplugin.vba.gz","4":"tplugin.vba.gz","src_id":"12050","5":"12050","creation_date":"1263114294","6":"1263114294"},{"0":"2917","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"tplugin.vba.gz","4":"tplugin.vba.gz","src_id":"12015","5":"12015","creation_date":"1262688298","6":"1262688298"}]},"2916":{"script_id":"2916","0":"2916","script_name":"extended help","1":"extended help","script_type":"utility","2":"utility","summary":"Simple plugin to open and close help without leaving current window","3":"Simple plugin to open and close help without leaving current window","description":"Plugin to open and close help without leaving current window\r\nIt is mostly useful when you want a quick reference\r\n\r\nUse:\r\n:Help subject - get help using :help command. It opens help window but cursor stays in the current window\r\n:Help! subject - help with :help! command\r\n:Help or :Help! - close help window\r\n","4":"Plugin to open and close help without leaving current window\r\nIt is mostly useful when you want a quick reference\r\n\r\nUse:\r\n:Help subject - get help using :help command. It opens help window but cursor stays in the current window\r\n:Help! subject - help with :help! command\r\n:Help or :Help! - close help window\r\n","install_details":"put into $VIMRUNTIME\/plugin","5":"put into $VIMRUNTIME\/plugin","first_name":"Sergey","6":"Sergey","last_name":"Khorev","7":"Khorev","releases":[{"0":"2916","vim_version":"6.0","1":"6.0","script_version":"1.1","2":"1.1","version_comment":"Add completion, fix argument handling, do not switch to another window if :Help was used in help window","3":"Add completion, fix argument handling, do not switch to another window if :Help was used in help window","package":"extended_help.vim","4":"extended_help.vim","src_id":"12029","5":"12029","creation_date":"1262957096","6":"1262957096"},{"0":"2916","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"extended_help.vim","4":"extended_help.vim","src_id":"12014","5":"12014","creation_date":"1262680383","6":"1262680383"}]},"2915":{"script_id":"2915","0":"2915","script_name":"startup_profile","1":"startup_profile","script_type":"patch","2":"patch","summary":"Profile vim startup","3":"Profile vim startup","description":"With the introduction of the autoload directory, plugins were often \r\nsplit into several separate files. The downside is that it isn't always \r\nthat obvious which files are actually loaded on startup.\r\n\r\nThis macro creates a CSV file including a list of loaded files during \r\nstartup and some indicators (number of lines\/bytes, timing). You can \r\nopen this (semicolon-separated) CSV in any spreadsheet application, sort \r\nthe data etc.\r\n\r\nIn order to activate the macro, check the value of g:startup_profile_csv \r\nin the source code and temporarily insert the following line(s) at the \r\nbeginning of your |vimrc| file: >\r\n\r\n    \" Setting g:startup_profile_csv is optional.\r\n    let g:startup_profile_csv = \"...\"\r\n    runtime macros\/startup_profile.vim\r\n\r\nThe list can serve as a starting point for optimizing your startup time, \r\ne.g. by delaying certain calls to functions in autoload files or by \r\nmaking use of the AsNeeded (vimscript #915) or the tplugin (vimscript #2917) \r\nplugins.\r\n\r\nDepending on your system configuration and the speed of your hard drive, \r\nseeking for files or, e.g., creating menu entries may prove to be costly \r\nwith respect to startup time.\r\n","4":"With the introduction of the autoload directory, plugins were often \r\nsplit into several separate files. The downside is that it isn't always \r\nthat obvious which files are actually loaded on startup.\r\n\r\nThis macro creates a CSV file including a list of loaded files during \r\nstartup and some indicators (number of lines\/bytes, timing). You can \r\nopen this (semicolon-separated) CSV in any spreadsheet application, sort \r\nthe data etc.\r\n\r\nIn order to activate the macro, check the value of g:startup_profile_csv \r\nin the source code and temporarily insert the following line(s) at the \r\nbeginning of your |vimrc| file: >\r\n\r\n    \" Setting g:startup_profile_csv is optional.\r\n    let g:startup_profile_csv = \"...\"\r\n    runtime macros\/startup_profile.vim\r\n\r\nThe list can serve as a starting point for optimizing your startup time, \r\ne.g. by delaying certain calls to functions in autoload files or by \r\nmaking use of the AsNeeded (vimscript #915) or the tplugin (vimscript #2917) \r\nplugins.\r\n\r\nDepending on your system configuration and the speed of your hard drive, \r\nseeking for files or, e.g., creating menu entries may prove to be costly \r\nwith respect to startup time.\r\n","install_details":"startup_profile requires vim 7.2.\r\n\r\nEdit the vba file and type: >\r\n\r\n    :so %\r\n\r\nSee :help vimball for details.\r\n\r\nAdd \"runtime macros\/startup_profile.vim\" to your |vimrc| file but see \r\nabove.\r\n\r\nAlso available via git: http:\/\/github.com\/tomtom\/startup_profile_vim\r\n\r\nNOTE. The script category (see above) is wrong. This is a utility\/macro,\r\nno patch.","5":"startup_profile requires vim 7.2.\r\n\r\nEdit the vba file and type: >\r\n\r\n    :so %\r\n\r\nSee :help vimball for details.\r\n\r\nAdd \"runtime macros\/startup_profile.vim\" to your |vimrc| file but see \r\nabove.\r\n\r\nAlso available via git: http:\/\/github.com\/tomtom\/startup_profile_vim\r\n\r\nNOTE. The script category (see above) is wrong. This is a utility\/macro,\r\nno patch.","first_name":"Tom","6":"Tom","last_name":"Link","7":"Link","releases":[{"0":"2915","vim_version":"7.0","1":"7.0","script_version":"0.2","2":"0.2","version_comment":"- Add size data on VimEnter, minimize impact of script logging on startup time\r\n","3":"- Add size data on VimEnter, minimize impact of script logging on startup time\r\n","package":"startup_profile.vba.gz","4":"startup_profile.vba.gz","src_id":"12036","5":"12036","creation_date":"1263036081","6":"1263036081"},{"0":"2915","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"startup_profile.vba.gz","4":"startup_profile.vba.gz","src_id":"12008","5":"12008","creation_date":"1262596867","6":"1262596867"}]},"2914":{"script_id":"2914","0":"2914","script_name":"pep8","1":"pep8","script_type":"utility","2":"utility","summary":"Check your python source files with PEP8","3":"Check your python source files with PEP8","description":"You need to install this tool: http:\/\/github.com\/cburroughs\/pep8.py\r\nIt's a simple program that just checks if your python code is pep-8 compliant.\r\n\r\nPressing F5 will run it using the \"quickfix\" feature.\r\nThis way you can \"navigate\" through errors using :cn and other standard commands.\r\n\r\nThis is mostly copied from http:\/\/www.vim.org\/scripts\/script.php?script_id=891","4":"You need to install this tool: http:\/\/github.com\/cburroughs\/pep8.py\r\nIt's a simple program that just checks if your python code is pep-8 compliant.\r\n\r\nPressing F5 will run it using the \"quickfix\" feature.\r\nThis way you can \"navigate\" through errors using :cn and other standard commands.\r\n\r\nThis is mostly copied from http:\/\/www.vim.org\/scripts\/script.php?script_id=891","install_details":"just put the file in your ~\/.vim\/ftplugin\/python directory (if that doesn't exist, create it)\r\n\r\nThe default mapping is F5, you can change it putting\r\nlet g:pep8_map='whatever'\r\nin your vimrc","5":"just put the file in your ~\/.vim\/ftplugin\/python directory (if that doesn't exist, create it)\r\n\r\nThe default mapping is F5, you can change it putting\r\nlet g:pep8_map='whatever'\r\nin your vimrc","first_name":"Davide","6":"Davide","last_name":"Lo Re","7":"Lo Re","releases":[{"0":"2914","vim_version":"7.0","1":"7.0","script_version":"0.3.1","2":"0.3.1","version_comment":"The \"PEP8 correct\" message is now highlighted in green (as in makegreen)","3":"The \"PEP8 correct\" message is now highlighted in green (as in makegreen)","package":"pep8.vim","4":"pep8.vim","src_id":"14366","5":"14366","creation_date":"1290611278","6":"1290611278"},{"0":"2914","vim_version":"7.0","1":"7.0","script_version":"0.3","2":"0.3","version_comment":"* Allow to choose the mapping\r\n* If there are no errors, just print \"PEP8 correct\" (a-la makegreen)\r\n(thanks Adrien LEMAIRE for the suggestions)","3":"* Allow to choose the mapping\r\n* If there are no errors, just print \"PEP8 correct\" (a-la makegreen)\r\n(thanks Adrien LEMAIRE for the suggestions)","package":"pep8.vim","4":"pep8.vim","src_id":"14365","5":"14365","creation_date":"1290610138","6":"1290610138"},{"0":"2914","vim_version":"7.0","1":"7.0","script_version":"0.2","2":"0.2","version_comment":"bugfix when trying to open 2 python files (thanks to Robson Roberto Souza Peixoto)","3":"bugfix when trying to open 2 python files (thanks to Robson Roberto Souza Peixoto)","package":"pep8.vim","4":"pep8.vim","src_id":"14168","5":"14168","creation_date":"1288734253","6":"1288734253"},{"0":"2914","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"pep8.vim","4":"pep8.vim","src_id":"12006","5":"12006","creation_date":"1262554097","6":"1262554097"}]},"2913":{"script_id":"2913","0":"2913","script_name":"spidermonkey.vim","1":"spidermonkey.vim","script_type":"ftplugin","2":"ftplugin","summary":"\n    spidermonkey syntax supports and snippets , reference query.\n","3":"\n    spidermonkey syntax supports and snippets , reference query.\n","description":"\n    spidermonkey syntax supports and snippets , reference query.\n","4":"\n    spidermonkey syntax supports and snippets , reference query.\n","install_details":"    ","5":"    ","first_name":"Yo-An","6":"Yo-An","last_name":"Lin","7":"Lin","releases":[{"0":"2913","vim_version":"7.2","1":"7.2","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"spidermonkey-vim-0.1.tar.gz","4":"spidermonkey-vim-0.1.tar.gz","src_id":"12005","5":"12005","creation_date":"1262511180","6":"1262511180"}]},"2912":{"script_id":"2912","0":"2912","script_name":"syntax\/Gemfile.vim","1":"syntax\/Gemfile.vim","script_type":"syntax","2":"syntax","summary":"The syntax file of Gemfile which is used for a RubyGems library \"Bundler\"","3":"The syntax file of Gemfile which is used for a RubyGems library \"Bundler\"","description":"Highlights some method names for Gemfile.","4":"Highlights some method names for Gemfile.","install_details":"Copy the `Gemfile.vim` on your ~\/.vim\/syntax\/ directory.\r\n\r\nYou may need to write ftdetect for Gemfile like:\r\n\r\n    \" ~\/.vim\/ftdetect\/Gemfile.vim\r\n    autocmd BufRead,BufNewFile Gemfile set filetype=Gemfile\r\n","5":"Copy the `Gemfile.vim` on your ~\/.vim\/syntax\/ directory.\r\n\r\nYou may need to write ftdetect for Gemfile like:\r\n\r\n    \" ~\/.vim\/ftdetect\/Gemfile.vim\r\n    autocmd BufRead,BufNewFile Gemfile set filetype=Gemfile\r\n","first_name":"ujihisa","6":"ujihisa","last_name":".","7":".","releases":[{"0":"2912","vim_version":"6.0","1":"6.0","script_version":"1.1","2":"1.1","version_comment":"To work with the latest version of Bundler.\r\n(Patch from Iain Hecker. Thanks!)","3":"To work with the latest version of Bundler.\r\n(Patch from Iain Hecker. Thanks!)","package":"Gemfile.vim","4":"Gemfile.vim","src_id":"12498","5":"12498","creation_date":"1267133517","6":"1267133517"},{"0":"2912","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"Gemfile.vim","4":"Gemfile.vim","src_id":"12004","5":"12004","creation_date":"1262498170","6":"1262498170"}]},"2911":{"script_id":"2911","0":"2911","script_name":"selfdot","1":"selfdot","script_type":"ftplugin","2":"ftplugin","summary":"type `self.` by pressing `.`","3":"type `self.` by pressing `.`","description":"Vim plugin that lets you type `self.` by pressing `.` in Python files.\r\n\r\nhttps:\/\/github.com\/narfdotpl\/selfdot.vim","4":"Vim plugin that lets you type `self.` by pressing `.` in Python files.\r\n\r\nhttps:\/\/github.com\/narfdotpl\/selfdot.vim","install_details":"","5":"","first_name":"Maciej","6":"Maciej","last_name":"Konieczny","7":"Konieczny","releases":[{"0":"2911","vim_version":"7.0","1":"7.0","script_version":"none","2":"none","version_comment":"Screw vim.org\/scripts!","3":"Screw vim.org\/scripts!","package":"empty.vim","4":"empty.vim","src_id":"16185","5":"16185","creation_date":"1312307199","6":"1312307199"}]},"2910":{"script_id":"2910","0":"2910","script_name":"restart.vim","1":"restart.vim","script_type":"utility","2":"utility","summary":"Restart your gVim","3":"Restart your gVim","description":"Usage:\r\n  Commands:\r\n      :Restart\r\n          If modified buffer(s) exist, gVim won't restart.\r\n          If you want to quit anyway, add bang(:Restart!).\r\n\r\n  Global Variables:\r\n      g:restart_command (default: 'Restart')\r\n          command name to restart gVim.\r\n\r\n      g:restart_save_window_values (default: 1)\r\n          Save window values when restarting gVim.\r\n          Saving values are as follows:\r\n          - &line\r\n          - &columns\r\n          - gVim window position (getwinposx(), getwinposy())\r\n          Before v0.0.1, restart.vim saves above values.\r\n          So this variable is for compatibility.\r\n\r\n      g:restart_save_fn (default: g:restart_save_fn is true: ['s:save_window_values'], false: [])\r\n          This variable saves functions returning ex command.\r\n          e.g., in your .vimrc:\r\n\r\n              function! Hello()\r\n                  return 'echomsg \"hello\"'\r\n              endfunction\r\n              let g:restart_save_fn = [function('Hello')]\r\n\r\n          This meaningless example shows \"hello\" in new starting up gVim.\r\n          When g:restart_save_window_values is true,\r\n          this variable is ['s:save_window_values'].\r\n\r\n              function! s:save_window_values()\r\n                  return join([\r\n                  \\       printf('set lines=%d', &lines),\r\n                  \\       printf('set columns=%d', &columns),\r\n                  \\       printf('winpos %s %s', getwinposx(), getwinposy()),\r\n                  \\   ],\r\n                  \\   ' | '\r\n                  \\)\r\n              endfunction\r\n\r\n         As you can see, this function saves current gVim's:\r\n         - &line\r\n         - &columns\r\n         - getwinposx()\r\n         - getwinposy()\r\n\r\n      g:restart_vim_progname (default: \"gvim\")\r\n         gVim program name to restart.\r\n\r\n         FIXME:\r\n         Under MS Windows, you must not assign .bat file path\r\n         to this variable. Because cmd.exe appears and won't close.\r\n\r\n      g:restart_sessionoptions (default: \"\")\r\n         If this variable is not empty, make a session from this value.\r\n         And restore the session after vim restarts.\r\n\r\nTODO:\r\n  - Support terminal vim\r\n  - Support MacVim\r\n      - MacVim support was implemented by ujihisa.\r\n      But g:restart_sessionoptions is not recognized.","4":"Usage:\r\n  Commands:\r\n      :Restart\r\n          If modified buffer(s) exist, gVim won't restart.\r\n          If you want to quit anyway, add bang(:Restart!).\r\n\r\n  Global Variables:\r\n      g:restart_command (default: 'Restart')\r\n          command name to restart gVim.\r\n\r\n      g:restart_save_window_values (default: 1)\r\n          Save window values when restarting gVim.\r\n          Saving values are as follows:\r\n          - &line\r\n          - &columns\r\n          - gVim window position (getwinposx(), getwinposy())\r\n          Before v0.0.1, restart.vim saves above values.\r\n          So this variable is for compatibility.\r\n\r\n      g:restart_save_fn (default: g:restart_save_fn is true: ['s:save_window_values'], false: [])\r\n          This variable saves functions returning ex command.\r\n          e.g., in your .vimrc:\r\n\r\n              function! Hello()\r\n                  return 'echomsg \"hello\"'\r\n              endfunction\r\n              let g:restart_save_fn = [function('Hello')]\r\n\r\n          This meaningless example shows \"hello\" in new starting up gVim.\r\n          When g:restart_save_window_values is true,\r\n          this variable is ['s:save_window_values'].\r\n\r\n              function! s:save_window_values()\r\n                  return join([\r\n                  \\       printf('set lines=%d', &lines),\r\n                  \\       printf('set columns=%d', &columns),\r\n                  \\       printf('winpos %s %s', getwinposx(), getwinposy()),\r\n                  \\   ],\r\n                  \\   ' | '\r\n                  \\)\r\n              endfunction\r\n\r\n         As you can see, this function saves current gVim's:\r\n         - &line\r\n         - &columns\r\n         - getwinposx()\r\n         - getwinposy()\r\n\r\n      g:restart_vim_progname (default: \"gvim\")\r\n         gVim program name to restart.\r\n\r\n         FIXME:\r\n         Under MS Windows, you must not assign .bat file path\r\n         to this variable. Because cmd.exe appears and won't close.\r\n\r\n      g:restart_sessionoptions (default: \"\")\r\n         If this variable is not empty, make a session from this value.\r\n         And restore the session after vim restarts.\r\n\r\nTODO:\r\n  - Support terminal vim\r\n  - Support MacVim\r\n      - MacVim support was implemented by ujihisa.\r\n      But g:restart_sessionoptions is not recognized.","install_details":"...","5":"...","first_name":"tyru","6":"tyru","last_name":" ","7":" ","releases":[{"0":"2910","vim_version":"7.0","1":"7.0","script_version":"0.0.8","2":"0.0.8","version_comment":"- Add |restart-tips|.\r\n- Improve error handling while restarting","3":"- Add |restart-tips|.\r\n- Improve error handling while restarting","package":"restart.zip","4":"restart.zip","src_id":"17001","5":"17001","creation_date":"1322749233","6":"1322749233"},{"0":"2910","vim_version":"7.0","1":"7.0","script_version":"0.0.7","2":"0.0.7","version_comment":"- separate doc to doc\/restart.txt\r\n- add g:restart_cd option (thanks thinca).\r\n- fix minor bug.","3":"- separate doc to doc\/restart.txt\r\n- add g:restart_cd option (thanks thinca).\r\n- fix minor bug.","package":"restart.zip","4":"restart.zip","src_id":"15152","5":"15152","creation_date":"1299152740","6":"1299152740"},{"0":"2910","vim_version":"7.0","1":"7.0","script_version":"0.0.6","2":"0.0.6","version_comment":"- Fix error when switching to GUI using :gui\r\n- Fix warning: Delete all buffers before starting new Vim\r\nto not show a warning about swap file. thanks thinca.","3":"- Fix error when switching to GUI using :gui\r\n- Fix warning: Delete all buffers before starting new Vim\r\nto not show a warning about swap file. thanks thinca.","package":"restart.zip","4":"restart.zip","src_id":"14625","5":"14625","creation_date":"1293415545","6":"1293415545"},{"0":"2910","vim_version":"7.0","1":"7.0","script_version":"0.0.5a","2":"0.0.5a","version_comment":"GUI MacVim support (not complete). thanks ujihisa.","3":"GUI MacVim support (not complete). thanks ujihisa.","package":"restart.zip","4":"restart.zip","src_id":"14431","5":"14431","creation_date":"1291432109","6":"1291432109"},{"0":"2910","vim_version":"7.0","1":"7.0","script_version":"0.0.4","2":"0.0.4","version_comment":"Add g:restart_sessionoptions. thanks thinca.","3":"Add g:restart_sessionoptions. thanks thinca.","package":"restart.zip","4":"restart.zip","src_id":"14386","5":"14386","creation_date":"1290834587","6":"1290834587"},{"0":"2910","vim_version":"7.0","1":"7.0","script_version":"0.0.3","2":"0.0.3","version_comment":"- Add g:restart_vim_progname.\r\n- Support MS Windows.\r\n- Fix minor bugs.","3":"- Add g:restart_vim_progname.\r\n- Support MS Windows.\r\n- Fix minor bugs.","package":"restart.zip","4":"restart.zip","src_id":"13242","5":"13242","creation_date":"1277548763","6":"1277548763"},{"0":"2910","vim_version":"7.0","1":"7.0","script_version":"0.0.2","2":"0.0.2","version_comment":"- Don't show 'modified buffer(s) ...' when banged.\r\n- Add g:restart_save_window_values, g:restart_save_fn.","3":"- Don't show 'modified buffer(s) ...' when banged.\r\n- Add g:restart_save_window_values, g:restart_save_fn.","package":"restart.vim","4":"restart.vim","src_id":"12924","5":"12924","creation_date":"1272771175","6":"1272771175"},{"0":"2910","vim_version":"7.0","1":"7.0","script_version":"0.0.1","2":"0.0.1","version_comment":"- Do not restart if modified buffer(s) exist.\r\n- etc.","3":"- Do not restart if modified buffer(s) exist.\r\n- etc.","package":"restart.zip","4":"restart.zip","src_id":"12535","5":"12535","creation_date":"1267509509","6":"1267509509"},{"0":"2910","vim_version":"7.0","1":"7.0","script_version":"0.0.0","2":"0.0.0","version_comment":"Initial upload","3":"Initial upload","package":"restart.vim","4":"restart.vim","src_id":"11994","5":"11994","creation_date":"1262346426","6":"1262346426"}]},"2909":{"script_id":"2909","0":"2909","script_name":"Flex Development Support","1":"Flex Development Support","script_type":"utility","2":"utility","summary":"Flex development support, ftplugin, indent, syntax, code completion, ...","3":"Flex development support, ftplugin, indent, syntax, code completion, ...","description":"Adobe Flex is a highly productive, free open source framework for building and maintaining expressive web applications that deploy consistently on all major browsers, desktops, and operating systems.  Flex applications can be built using the free Flex SDK (http:\/\/www.adobe.com\/cfusion\/entitlement\/index.cfm?e=flex3sdk).\r\n\r\nHere is a snippet from :h flex.txt (after installing).\r\n\r\nThis document outlines the various features the Vim Flex Development Support suite provides and how to interact with it to enhance the Vim development experience for Flex applications.\r\n\r\n1. Overview\r\n2. Filetypes\r\n3. Navigation\r\n    3.1 Matchit\r\n    3.2 Text Object Motions\r\n    3.3 Macros\r\n    3.4 Imports\r\n4. OMNI MXML Completion\r\n5. Compilation\r\n    5.1 mxmlc\r\n    5.2 Ant \r\n6. Indenting\r\n7. Syntax Highlighting\r\n8. Flex Tutorial\r\n    8.1 Code Completion\r\n    8.2 Imports\r\n    8.3 Compiling\r\n        8.3.1 mxmlc\r\n        8.3.2 Ant\r\n\r\nEssentially, this suite provides:\r\n    file type support\r\n    indent\r\n    syntax\r\n    compiler\r\n    code completion\r\n    \r\nSince this is a new project, please post to vim_use with comments and suggestions.  Especially if you are having difficultly getting things working as expected.\r\n\r\n\r\nIf someone knows how to generate a list of classes and the associated methods for ActionScript, please let me know.  I will add code completion for it in addition to the MXML code completion.\r\n\r\n","4":"Adobe Flex is a highly productive, free open source framework for building and maintaining expressive web applications that deploy consistently on all major browsers, desktops, and operating systems.  Flex applications can be built using the free Flex SDK (http:\/\/www.adobe.com\/cfusion\/entitlement\/index.cfm?e=flex3sdk).\r\n\r\nHere is a snippet from :h flex.txt (after installing).\r\n\r\nThis document outlines the various features the Vim Flex Development Support suite provides and how to interact with it to enhance the Vim development experience for Flex applications.\r\n\r\n1. Overview\r\n2. Filetypes\r\n3. Navigation\r\n    3.1 Matchit\r\n    3.2 Text Object Motions\r\n    3.3 Macros\r\n    3.4 Imports\r\n4. OMNI MXML Completion\r\n5. Compilation\r\n    5.1 mxmlc\r\n    5.2 Ant \r\n6. Indenting\r\n7. Syntax Highlighting\r\n8. Flex Tutorial\r\n    8.1 Code Completion\r\n    8.2 Imports\r\n    8.3 Compiling\r\n        8.3.1 mxmlc\r\n        8.3.2 Ant\r\n\r\nEssentially, this suite provides:\r\n    file type support\r\n    indent\r\n    syntax\r\n    compiler\r\n    code completion\r\n    \r\nSince this is a new project, please post to vim_use with comments and suggestions.  Especially if you are having difficultly getting things working as expected.\r\n\r\n\r\nIf someone knows how to generate a list of classes and the associated methods for ActionScript, please let me know.  I will add code completion for it in addition to the MXML code completion.\r\n\r\n","install_details":"The zip file contains the necessary path structure.\r\n\r\nOn *nix, unzip into:\r\n$HOME\/.vim\/\r\n\r\nOn Windows unzip into:\r\n$VIM\/vimfiles\/ \r\n\r\nTo update the Vim Help, run:\r\n:helptags $HOME\/.vim\/doc  (Unix)\r\n:helptags $VIM\/vimfiles\/doc  (Windows)\r\n ","5":"The zip file contains the necessary path structure.\r\n\r\nOn *nix, unzip into:\r\n$HOME\/.vim\/\r\n\r\nOn Windows unzip into:\r\n$VIM\/vimfiles\/ \r\n\r\nTo update the Vim Help, run:\r\n:helptags $HOME\/.vim\/doc  (Unix)\r\n:helptags $VIM\/vimfiles\/doc  (Windows)\r\n ","first_name":"David","6":"David","last_name":"Fishburn","7":"Fishburn","releases":[{"0":"2909","vim_version":"7.0","1":"7.0","script_version":"3.0","2":"3.0","version_comment":"Updated the syntax files.\r\nUpdated the indent files (Ingo Karkat).\r\nThere were apparently some issues unzipping this file on *nix platforms related to the XML completion files.\r\nAll files now use the unix fileformat (:set ff=unix) so there shouldn't be issues using this on *nix.\r\n","3":"Updated the syntax files.\r\nUpdated the indent files (Ingo Karkat).\r\nThere were apparently some issues unzipping this file on *nix platforms related to the XML completion files.\r\nAll files now use the unix fileformat (:set ff=unix) so there shouldn't be issues using this on *nix.\r\n","package":"flex_dev_30.zip","4":"flex_dev_30.zip","src_id":"12966","5":"12966","creation_date":"1273198340","6":"1273198340"},{"0":"2909","vim_version":"7.0","1":"7.0","script_version":"2.0","2":"2.0","version_comment":"The autoload\/mxmlcomplete.vim file was missing.\r\nMinor update to the documentation.\r\n","3":"The autoload\/mxmlcomplete.vim file was missing.\r\nMinor update to the documentation.\r\n","package":"flex_dev_20.zip","4":"flex_dev_20.zip","src_id":"12085","5":"12085","creation_date":"1263389627","6":"1263389627"},{"0":"2909","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"flex_dev_10.zip","4":"flex_dev_10.zip","src_id":"11986","5":"11986","creation_date":"1262231587","6":"1262231587"}]},"2908":{"script_id":"2908","0":"2908","script_name":"Enhanced Ex","1":"Enhanced Ex","script_type":"utility","2":"utility","summary":"Improve your efficiency in ex-mode","3":"Improve your efficiency in ex-mode","description":"Improve your editing efficiency when in ex-mode.\r\n\r\nThis plugin provides a collection of functions and mappings to help you increase your productivity on the command-line. Functions include:\r\n- Reverse search your ex history using regular expressions,\r\n- Zap to any previously typed character,\r\n- Capture all ex output in a *Messages* buffer for processing, just like in Emacs,\r\n- and more.","4":"Improve your editing efficiency when in ex-mode.\r\n\r\nThis plugin provides a collection of functions and mappings to help you increase your productivity on the command-line. Functions include:\r\n- Reverse search your ex history using regular expressions,\r\n- Zap to any previously typed character,\r\n- Capture all ex output in a *Messages* buffer for processing, just like in Emacs,\r\n- and more.","install_details":"Just put it in your ~\/.vim\/plugin\/ directory, or load it manually in vim with the :source command.","5":"Just put it in your ~\/.vim\/plugin\/ directory, or load it manually in vim with the :source command.","first_name":"Joel","6":"Joel","last_name":"Jackson","7":"Jackson","releases":[{"0":"2908","vim_version":"7.0","1":"7.0","script_version":"1.1","2":"1.1","version_comment":"Fixed minor version problem","3":"Fixed minor version problem","package":"ex.vim","4":"ex.vim","src_id":"11992","5":"11992","creation_date":"1262338151","6":"1262338151"},{"0":"2908","vim_version":"7.2","1":"7.2","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"ex.vim","4":"ex.vim","src_id":"11984","5":"11984","creation_date":"1262171969","6":"1262171969"}]},"2907":{"script_id":"2907","0":"2907","script_name":"hlint","1":"hlint","script_type":"utility","2":"utility","summary":"Compiler definition for the hlint (haskell checker) tool","3":"Compiler definition for the hlint (haskell checker) tool","description":"hlint is an haskell code source checker, producing many warnings\/recommendations. This script allow to vim to parse it's output and then jumping directly to pointed locations.\r\n\r\nTo use it :\r\n:comp hlint","4":"hlint is an haskell code source checker, producing many warnings\/recommendations. This script allow to vim to parse it's output and then jumping directly to pointed locations.\r\n\r\nTo use it :\r\n:comp hlint","install_details":"Open the file in vim then type :\r\n:so %","5":"Open the file in vim then type :\r\n:so %","first_name":"Vincent","6":"Vincent","last_name":"B","7":"B","releases":[{"0":"2907","vim_version":"7.0","1":"7.0","script_version":"1.02","2":"1.02","version_comment":"Fixed problem with shellpipe\r\nSwitched to vimball distribution","3":"Fixed problem with shellpipe\r\nSwitched to vimball distribution","package":"hlint.vba","4":"hlint.vba","src_id":"12537","5":"12537","creation_date":"1267521601","6":"1267521601"}]},"2906":{"script_id":"2906","0":"2906","script_name":"Vim Condensed Quick Reference","1":"Vim Condensed Quick Reference","script_type":"utility","2":"utility","summary":"Vim quick reference in LaTeX, PDF and PS formats","3":"Vim quick reference in LaTeX, PDF and PS formats","description":"This a condensed quick reference on Vim commands and options. I tried to squeeze as many as possible into two-sided A4.\r\n\r\nIt is not user manual or guide, just a reference. For notation see the last column.\r\n\r\nPlease send your feedback to sergey.khorev@gmail.com","4":"This a condensed quick reference on Vim commands and options. I tried to squeeze as many as possible into two-sided A4.\r\n\r\nIt is not user manual or guide, just a reference. For notation see the last column.\r\n\r\nPlease send your feedback to sergey.khorev@gmail.com","install_details":"Unpack somewhere, print out.","5":"Unpack somewhere, print out.","first_name":"Sergey","6":"Sergey","last_name":"Khorev","7":"Khorev","releases":[{"0":"2906","vim_version":"7.0","1":"7.0","script_version":"1.2","2":"1.2","version_comment":"Minor tweaks","3":"Minor tweaks","package":"vimquickref.zip","4":"vimquickref.zip","src_id":"12697","5":"12697","creation_date":"1269435568","6":"1269435568"},{"0":"2906","vim_version":"7.0","1":"7.0","script_version":"1.1","2":"1.1","version_comment":"Fixed found errors and obscurities","3":"Fixed found errors and obscurities","package":"vimquickref.zip","4":"vimquickref.zip","src_id":"12019","5":"12019","creation_date":"1262765580","6":"1262765580"},{"0":"2906","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"vimquickref.zip","4":"vimquickref.zip","src_id":"11968","5":"11968","creation_date":"1261987281","6":"1261987281"}]},"2905":{"script_id":"2905","0":"2905","script_name":"vim-addon-manager","1":"vim-addon-manager","script_type":"utility","2":"utility","summary":"manage and update plugins easily","3":"manage and update plugins easily","description":"NEW: Windows users can use this download form now: http:\/\/mawercer.de\/~marc\/vam\/index.php to get plugins.\r\n\r\nNote:\r\nThere is also  http:\/\/packages.debian.org\/sid\/vim-addon-manager\r\nwhich servers a similar purpose but is Debian specific.\r\nI chose the same name by accident. See doc\/*\r\n\r\nusage example:\r\n\r\nset runtimepath+=~\/path-to\/vim-plugin-manager\r\ncall scriptmanager#Activate([\"vim-haxe\",\"The_NERD_tree\",\"vim-latex\"])\r\n\r\nOn startup you'll have to confirm installing plugins.\r\nFor reviewing plugins before usage try :InstallAddon command which downloads only\r\n\r\nNote: I setup a cron job which updates the \r\nvim-plugin-manager-known-repositories every couple of days.\r\n\r\nDetailed description can be found in the doc directory of this distribution.\r\n\r\nTROUBLE ? Contact me or create a ticket (github page).\r\n\r\nAdditional note: Voting on www.vim.org is known to be inaccurate. If you have a problem, contact me and I'll help you.","4":"NEW: Windows users can use this download form now: http:\/\/mawercer.de\/~marc\/vam\/index.php to get plugins.\r\n\r\nNote:\r\nThere is also  http:\/\/packages.debian.org\/sid\/vim-addon-manager\r\nwhich servers a similar purpose but is Debian specific.\r\nI chose the same name by accident. See doc\/*\r\n\r\nusage example:\r\n\r\nset runtimepath+=~\/path-to\/vim-plugin-manager\r\ncall scriptmanager#Activate([\"vim-haxe\",\"The_NERD_tree\",\"vim-latex\"])\r\n\r\nOn startup you'll have to confirm installing plugins.\r\nFor reviewing plugins before usage try :InstallAddon command which downloads only\r\n\r\nNote: I setup a cron job which updates the \r\nvim-plugin-manager-known-repositories every couple of days.\r\n\r\nDetailed description can be found in the doc directory of this distribution.\r\n\r\nTROUBLE ? Contact me or create a ticket (github page).\r\n\r\nAdditional note: Voting on www.vim.org is known to be inaccurate. If you have a problem, contact me and I'll help you.","install_details":"Details: http:\/\/github.com\/MarcWeber\/vim-addon-manager\/blob\/master\/doc\/vim-addon-manager-getting-started.txt\r\nsection 2","5":"Details: http:\/\/github.com\/MarcWeber\/vim-addon-manager\/blob\/master\/doc\/vim-addon-manager-getting-started.txt\r\nsection 2","first_name":"Marc","6":"Marc","last_name":"Weber","7":"Weber","releases":[{"0":"2905","vim_version":"7.0","1":"7.0","script_version":"0.0","2":"0.0","version_comment":"howto get latest VAM version","3":"howto get latest VAM version","package":"howto-downnload-vim-addon-manager.txt","4":"howto-downnload-vim-addon-manager.txt","src_id":"18409","5":"18409","creation_date":"1345057836","6":"1345057836"}]},"2904":{"script_id":"2904","0":"2904","script_name":"Cfengine version 3 syntax","1":"Cfengine version 3 syntax","script_type":"syntax","2":"syntax","summary":"Cfengine 3 syntax highlighting","3":"Cfengine 3 syntax highlighting","description":"Cfengine 3 syntax highlighting. Latest version now over at Github: https:\/\/github.com\/neilhwatson\/vim_cf3","4":"Cfengine 3 syntax highlighting. Latest version now over at Github: https:\/\/github.com\/neilhwatson\/vim_cf3","install_details":"","5":"","first_name":"neil","6":"neil","last_name":"watson","7":"watson","releases":[{"0":"2904","vim_version":"7.0","1":"7.0","script_version":"20111219","2":"20111219","version_comment":"Now matches single quotes as well as double.","3":"Now matches single quotes as well as double.","package":"cf3.vim","4":"cf3.vim","src_id":"17089","5":"17089","creation_date":"1324313048","6":"1324313048"},{"0":"2904","vim_version":"7.0","1":"7.0","script_version":"20111121","2":"20111121","version_comment":"List variables '@' are now highlighted.","3":"List variables '@' are now highlighted.","package":"cf3.vim","4":"cf3.vim","src_id":"16916","5":"16916","creation_date":"1321883762","6":"1321883762"},{"0":"2904","vim_version":"7.0","1":"7.0","script_version":"3","2":"3","version_comment":"Added changes from John Coleman at Yale U.","3":"Added changes from John Coleman at Yale U.","package":"cf3.vim","4":"cf3.vim","src_id":"16491","5":"16491","creation_date":"1315490965","6":"1315490965"},{"0":"2904","vim_version":"7.0","1":"7.0","script_version":"2","2":"2","version_comment":"Minor improvement for CF3Types.","3":"Minor improvement for CF3Types.","package":"cf3.vim","4":"cf3.vim","src_id":"13898","5":"13898","creation_date":"1285272491","6":"1285272491"},{"0":"2904","vim_version":"5.7","1":"5.7","script_version":"1","2":"1","version_comment":"Initial upload","3":"Initial upload","package":"cf3.vim","4":"cf3.vim","src_id":"11965","5":"11965","creation_date":"1261929057","6":"1261929057"}]},"2903":{"script_id":"2903","0":"2903","script_name":"Cfengine 3 ftplugin","1":"Cfengine 3 ftplugin","script_type":"ftplugin","2":"ftplugin","summary":"Abbreviations and other help for Cfengine 3 files","3":"Abbreviations and other help for Cfengine 3 files","description":"Abbreviations and other help for Cfengine 3 files.  Latest version now over at Github: https:\/\/github.com\/neilhwatson\/vim_cf3","4":"Abbreviations and other help for Cfengine 3 files.  Latest version now over at Github: https:\/\/github.com\/neilhwatson\/vim_cf3","install_details":"","5":"","first_name":"neil","6":"neil","last_name":"watson","7":"watson","releases":[{"0":"2903","vim_version":"7.0","1":"7.0","script_version":"20111219","2":"20111219","version_comment":"minor fix","3":"minor fix","package":"cf3.vim","4":"cf3.vim","src_id":"17088","5":"17088","creation_date":"1324312998","6":"1324312998"},{"0":"2903","vim_version":"7.0","1":"7.0","script_version":"20111121","2":"20111121","version_comment":"New abbreviations for slist, string and usebundle.","3":"New abbreviations for slist, string and usebundle.","package":"cf3.vim","4":"cf3.vim","src_id":"16915","5":"16915","creation_date":"1321883700","6":"1321883700"},{"0":"2903","vim_version":"7.0","1":"7.0","script_version":"20111005","2":"20111005","version_comment":" Wednesday October 05 2011\r\n - Added comment and handle abbs.  Assumes you have the Eatchar and Getchar functions.\r\n - Can now wrap words and lists in quotes.\r\n - Insert blank promises (,p)\r\n - Insert blank testing skeleton (,k)","3":" Wednesday October 05 2011\r\n - Added comment and handle abbs.  Assumes you have the Eatchar and Getchar functions.\r\n - Can now wrap words and lists in quotes.\r\n - Insert blank promises (,p)\r\n - Insert blank testing skeleton (,k)","package":"cf3.vim","4":"cf3.vim","src_id":"16622","5":"16622","creation_date":"1317824533","6":"1317824533"},{"0":"2903","vim_version":"5.7","1":"5.7","script_version":"1","2":"1","version_comment":"Initial upload","3":"Initial upload","package":"cf3.vim","4":"cf3.vim","src_id":"11964","5":"11964","creation_date":"1261928963","6":"1261928963"}]},"2902":{"script_id":"2902","0":"2902","script_name":"AuthorInfo","1":"AuthorInfo","script_type":"ftplugin","2":"ftplugin","summary":"You can add your author info in any source files,such as cpp,c,java,and c#.","3":"You can add your author info in any source files,such as cpp,c,java,and c#.","description":"You can add your author info in any source files,such as cpp,c,java,and c#,python,php,bash....\r\nLike this:\r\n\/*=============================================================================\r\n#  Author:          dantezhu - http:\/\/www.vimer.cn\r\n#  Email:           zny2008@gmail.com\r\n#  FileName:        test2.cpp\r\n#  Description:     \r\n#  Version:         0.0.1\r\n#  LastChange:      2011-02-15 19:32:25\r\n#  History:         \r\n=============================================================================*\/\r\nwhen you type <F4>,this will add in the head of your source file,and when you type <F4> again,It will update automatically.\r\n\r\n1)you need install The NERD Commenter first.\r\nurl is : http:\/\/www.vim.org\/scripts\/script.php?script_id=1218\r\n\r\n2)you need some config in vimrc:\r\n\r\nlet g:vimrc_author='dantezhu'\r\nlet g:vimrc_email='zny2008@gmail.com'\r\nlet g:vimrc_homepage='http:\/\/www.vimer.cn'\r\n\r\nnmap <F4> :AuthorInfoDetect<cr>\r\n\r\n\r\nMy homepage is http:\/\/www.vimer.cn,and wellcome。","4":"You can add your author info in any source files,such as cpp,c,java,and c#,python,php,bash....\r\nLike this:\r\n\/*=============================================================================\r\n#  Author:          dantezhu - http:\/\/www.vimer.cn\r\n#  Email:           zny2008@gmail.com\r\n#  FileName:        test2.cpp\r\n#  Description:     \r\n#  Version:         0.0.1\r\n#  LastChange:      2011-02-15 19:32:25\r\n#  History:         \r\n=============================================================================*\/\r\nwhen you type <F4>,this will add in the head of your source file,and when you type <F4> again,It will update automatically.\r\n\r\n1)you need install The NERD Commenter first.\r\nurl is : http:\/\/www.vim.org\/scripts\/script.php?script_id=1218\r\n\r\n2)you need some config in vimrc:\r\n\r\nlet g:vimrc_author='dantezhu'\r\nlet g:vimrc_email='zny2008@gmail.com'\r\nlet g:vimrc_homepage='http:\/\/www.vimer.cn'\r\n\r\nnmap <F4> :AuthorInfoDetect<cr>\r\n\r\n\r\nMy homepage is http:\/\/www.vimer.cn,and wellcome。","install_details":"Put this file in the vim plugins directory (~\/.vim\/plugin\/) to load it automatically.","5":"Put this file in the vim plugins directory (~\/.vim\/plugin\/) to load it automatically.","first_name":"zhu","6":"zhu","last_name":"nianyang","7":"nianyang","releases":[{"0":"2902","vim_version":"7.0","1":"7.0","script_version":"1.5","2":"1.5","version_comment":"support skip bash's #!xxx","3":"support skip bash's #!xxx","package":"authorinfo.vim","4":"authorinfo.vim","src_id":"16295","5":"16295","creation_date":"1313683846","6":"1313683846"},{"0":"2902","vim_version":"7.0","1":"7.0","script_version":"1.4","2":"1.4","version_comment":"I am so sorry,the nerd comment is upgrade,it's mapping was changed. \r\nNow,I fix the bug.","3":"I am so sorry,the nerd comment is upgrade,it's mapping was changed. \r\nNow,I fix the bug.","package":"authorinfo.vim","4":"authorinfo.vim","src_id":"15095","5":"15095","creation_date":"1298450649","6":"1298450649"},{"0":"2902","vim_version":"7.0","1":"7.0","script_version":"1.3","2":"1.3","version_comment":"more comfortable~","3":"more comfortable~","package":"authorinfo.vim","4":"authorinfo.vim","src_id":"15017","5":"15017","creation_date":"1297786066","6":"1297786066"},{"0":"2902","vim_version":"7.0","1":"7.0","script_version":"1.2","2":"1.2","version_comment":"need install The NERD Commenter first. \r\nurl is : http:\/\/www.vim.org\/scripts\/script.php?script_id=1218","3":"need install The NERD Commenter first. \r\nurl is : http:\/\/www.vim.org\/scripts\/script.php?script_id=1218","package":"authorinfo.vim","4":"authorinfo.vim","src_id":"15012","5":"15012","creation_date":"1297771685","6":"1297771685"},{"0":"2902","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"AuthorInfo.vim","4":"AuthorInfo.vim","src_id":"11963","5":"11963","creation_date":"1261912903","6":"1261912903"}]},"2901":{"script_id":"2901","0":"2901","script_name":"ShowFunc.vim","1":"ShowFunc.vim","script_type":"ftplugin","2":"ftplugin","summary":"Show the function's define.","3":"Show the function's define.","description":"This plugin can show the function's define where the cursor at when you type \"fd\".\r\nWell,You can also type \"(\" after a functionname,then the define will show in the command line.\r\n\r\nAfter all:\r\nThis plugin supports types such as cpp,c,java,c# with Exuberant Ctags.\r\n\r\nMy home page: http:\/\/www.vimer.cn ,and willcome.\r\n","4":"This plugin can show the function's define where the cursor at when you type \"fd\".\r\nWell,You can also type \"(\" after a functionname,then the define will show in the command line.\r\n\r\nAfter all:\r\nThis plugin supports types such as cpp,c,java,c# with Exuberant Ctags.\r\n\r\nMy home page: http:\/\/www.vimer.cn ,and willcome.\r\n","install_details":"Put this file in the vim plugins directory (~\/.vim\/plugin\/) to load it automatically.","5":"Put this file in the vim plugins directory (~\/.vim\/plugin\/) to load it automatically.","first_name":"zhu","6":"zhu","last_name":"nianyang","7":"nianyang","releases":[{"0":"2901","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"ShowFunc.vim","4":"ShowFunc.vim","src_id":"11962","5":"11962","creation_date":"1261912152","6":"1261912152"}]},"2900":{"script_id":"2900","0":"2900","script_name":"gitolite.vim","1":"gitolite.vim","script_type":"syntax","2":"syntax","summary":"Syntax highlight and indent rules for gitolite configuration","3":"Syntax highlight and indent rules for gitolite configuration","description":"Syntax highlight and indent rules for gitolite (https:\/\/github.com\/sitaramc\/gitolite) configuration file \"gitolite.conf\".\r\n\r\nSource: https:\/\/github.com\/tmatilai\/gitolite.vim","4":"Syntax highlight and indent rules for gitolite (https:\/\/github.com\/sitaramc\/gitolite) configuration file \"gitolite.conf\".\r\n\r\nSource: https:\/\/github.com\/tmatilai\/gitolite.vim","install_details":"The recommended method is to install pathogen.vim (vimscript #2332), and then clone gitolite.vim repository (or copy the content) under ~\/.vim\/bundle:\r\n\r\n    cd ~\/.vim\/bundle\r\n    git clone git:\/\/github.com\/tmatilai\/gitolite.vim.git\r\n\r\nAnother option is to download and open the Vimball (gitolite.vba.gz) in Vim and call:\r\n    :source %s","5":"The recommended method is to install pathogen.vim (vimscript #2332), and then clone gitolite.vim repository (or copy the content) under ~\/.vim\/bundle:\r\n\r\n    cd ~\/.vim\/bundle\r\n    git clone git:\/\/github.com\/tmatilai\/gitolite.vim.git\r\n\r\nAnother option is to download and open the Vimball (gitolite.vba.gz) in Vim and call:\r\n    :source %s","first_name":"Teemu","6":"Teemu","last_name":"Matilainen","7":"Matilainen","releases":[{"0":"2900","vim_version":"7.0","1":"7.0","script_version":"13","2":"13","version_comment":"Fix cpoptions handling. Thanks to Thilo Six.","3":"Fix cpoptions handling. Thanks to Thilo Six.","package":"gitolite.vba.gz","4":"gitolite.vba.gz","src_id":"17118","5":"17118","creation_date":"1324835705","6":"1324835705"},{"0":"2900","vim_version":"6.0","1":"6.0","script_version":"12","2":"12","version_comment":"- Add indent rules\r\n- Allow a comma in regex pattern for wild repos","3":"- Add indent rules\r\n- Allow a comma in regex pattern for wild repos","package":"gitolite.vba.gz","4":"gitolite.vba.gz","src_id":"16982","5":"16982","creation_date":"1322335196","6":"1322335196"},{"0":"2900","vim_version":"6.0","1":"6.0","script_version":"11","2":"11","version_comment":"Highlight subconf command","3":"Highlight subconf command","package":"gitolite.vba.gz","4":"gitolite.vba.gz","src_id":"16631","5":"16631","creation_date":"1317995420","6":"1317995420"},{"0":"2900","vim_version":"6.0","1":"6.0","script_version":"10","2":"10","version_comment":"Separate C and D permissions","3":"Separate C and D permissions","package":"gitolite.vba.gz","4":"gitolite.vba.gz","src_id":"13679","5":"13679","creation_date":"1282821538","6":"1282821538"},{"0":"2900","vim_version":"6.0","1":"6.0","script_version":"9","2":"9","version_comment":"\"D\" permission must be combined with \"RW\" or \"RW+\"","3":"\"D\" permission must be combined with \"RW\" or \"RW+\"","package":"gitolite.vba.gz","4":"gitolite.vba.gz","src_id":"12889","5":"12889","creation_date":"1271981385","6":"1271981385"},{"0":"2900","vim_version":"6.0","1":"6.0","script_version":"8","2":"8","version_comment":"Highlight D permission","3":"Highlight D permission","package":"gitolite.vba.gz","4":"gitolite.vba.gz","src_id":"12822","5":"12822","creation_date":"1271101741","6":"1271101741"},{"0":"2900","vim_version":"6.0","1":"6.0","script_version":"7","2":"7","version_comment":"- Highlight USER in refexes (personal branches)\r\n- Highlight whitespace error in group definitions","3":"- Highlight USER in refexes (personal branches)\r\n- Highlight whitespace error in group definitions","package":"gitolite.vba.gz","4":"gitolite.vba.gz","src_id":"12706","5":"12706","creation_date":"1269556252","6":"1269556252"},{"0":"2900","vim_version":"6.0","1":"6.0","script_version":"6","2":"6","version_comment":"Highlight groups in refs","3":"Highlight groups in refs","package":"gitolite.vba.gz","4":"gitolite.vba.gz","src_id":"12487","5":"12487","creation_date":"1267045953","6":"1267045953"},{"0":"2900","vim_version":"6.0","1":"6.0","script_version":"5","2":"5","version_comment":"Highlight all files in gitolite-admin\/conf\/","3":"Highlight all files in gitolite-admin\/conf\/","package":"gitolite.vba.gz","4":"gitolite.vba.gz","src_id":"12340","5":"12340","creation_date":"1265655012","6":"1265655012"},{"0":"2900","vim_version":"6.0","1":"6.0","script_version":"4","2":"4","version_comment":"Highlight EXTCMD\/ definitions","3":"Highlight EXTCMD\/ definitions","package":"gitolite.vba.gz","4":"gitolite.vba.gz","src_id":"12271","5":"12271","creation_date":"1265074670","6":"1265074670"},{"0":"2900","vim_version":"6.0","1":"6.0","script_version":"3","2":"3","version_comment":"Almost full rewrite:\r\n- Highlight illegal characters in group, repo and ACL definitions\r\n- Highlight wildcard repositories\r\n- Highlight denied users\/groups\r\n- Do not require space around \"=\" characters\r\n- Highlight NAME-based restrictions","3":"Almost full rewrite:\r\n- Highlight illegal characters in group, repo and ACL definitions\r\n- Highlight wildcard repositories\r\n- Highlight denied users\/groups\r\n- Do not require space around \"=\" characters\r\n- Highlight NAME-based restrictions","package":"gitolite.vba.gz","4":"gitolite.vba.gz","src_id":"12123","5":"12123","creation_date":"1263851555","6":"1263851555"},{"0":"2900","vim_version":"6.0","1":"6.0","script_version":"2","2":"2","version_comment":"- Create a Vimball that also include ftdetect\r\n- Support \"include\" command","3":"- Create a Vimball that also include ftdetect\r\n- Support \"include\" command","package":"gitolite.vba.gz","4":"gitolite.vba.gz","src_id":"12108","5":"12108","creation_date":"1263523306","6":"1263523306"},{"0":"2900","vim_version":"6.0","1":"6.0","script_version":"1","2":"1","version_comment":"Initial upload","3":"Initial upload","package":"gitolite.vim","4":"gitolite.vim","src_id":"11958","5":"11958","creation_date":"1261851034","6":"1261851034"}]},"2899":{"script_id":"2899","0":"2899","script_name":"TxtBrowser","1":"TxtBrowser","script_type":"syntax","2":"syntax","summary":"Browse .txt and .rst files easily(show the title tag and syntax highlight)","3":"Browse .txt and .rst files easily(show the title tag and syntax highlight)","description":"The \"TxtBrowser\" plugin works along with taglist(vimscript #273: taglist.vim),\r\nIt generate the document outline automatically for .txt and .rst files. Meanwhile it highlight the .txt and .rst files for you:\r\n\r\n1) Use \":Tlist\" command to open the outline of a .txt\/.rst file in the taglist\r\nwindow.\r\n\r\n2) Use \":TlistUpdate\" to update the outline after modification.\r\n\r\n3) Syntax highlight: highlight the key element in your plain text. This include\r\nthe title, URLs, keywords you defined(default is TODO, ERROR, etc), Words in\r\nbracket, etc. Syntax hightlight would be auto loaded after install. Snapshot of\r\nfeature 1 and 2 are available at:\r\n\r\nhttp:\/\/guoyoooping.blog.163.com\/album\/edit\/#m=1&aid=193892890\r\n\r\n4) Browser Utilities(use \":help txtbrowser\" for details):\r\n\r\n<Leader>s: Search text under cursor(or selected) through search engine(google).\r\n<Leader>f: Find text under cursor(or selected) through web dictionary(www.dict.cn).\r\n<Leader>g: Goto the URL under cursor(or selected).\r\n","4":"The \"TxtBrowser\" plugin works along with taglist(vimscript #273: taglist.vim),\r\nIt generate the document outline automatically for .txt and .rst files. Meanwhile it highlight the .txt and .rst files for you:\r\n\r\n1) Use \":Tlist\" command to open the outline of a .txt\/.rst file in the taglist\r\nwindow.\r\n\r\n2) Use \":TlistUpdate\" to update the outline after modification.\r\n\r\n3) Syntax highlight: highlight the key element in your plain text. This include\r\nthe title, URLs, keywords you defined(default is TODO, ERROR, etc), Words in\r\nbracket, etc. Syntax hightlight would be auto loaded after install. Snapshot of\r\nfeature 1 and 2 are available at:\r\n\r\nhttp:\/\/guoyoooping.blog.163.com\/album\/edit\/#m=1&aid=193892890\r\n\r\n4) Browser Utilities(use \":help txtbrowser\" for details):\r\n\r\n<Leader>s: Search text under cursor(or selected) through search engine(google).\r\n<Leader>f: Find text under cursor(or selected) through web dictionary(www.dict.cn).\r\n<Leader>g: Goto the URL under cursor(or selected).\r\n","install_details":"1) Please make sure universal-ctags(https:\/\/github.com\/universal-ctags\/ctags) has been installed(Exuberant Ctags doesn't work for .rst files).\r\n\r\n2) Please make sure taglist(vimscript #273: taglist.vim) has been installed.\r\n\r\n3) Download the txtbrowser file and uncompress the files to your .vim directory:\r\n\r\n    $ tar xvf txtbrowser-1.3.6.tar.bz2 -C ~\/\r\n    .vim\/\r\n    .vim\/doc\/\r\n    .vim\/doc\/txtbrowser.cnx\r\n    .vim\/doc\/txtbrowser.txt\r\n    .vim\/ftplugin\/\r\n    .vim\/ftplugin\/gdb.vim\r\n    .vim\/ftplugin\/rst.vim\r\n    .vim\/ftplugin\/txt.vim\r\n    .vim\/plugin\/\r\n    .vim\/plugin\/txtbrowser.vim\r\n    .vim\/syntax\/\r\n    .vim\/syntax\/txt.vim\r\n\r\n4) open the .vim\/doc\/txtbrowser.txt Install the helptags using \":helptags .\"\r\n\r\n5) Add the following line into your .vimrc file and restart your vim.\r\n\r\n    syntax on \"syntax highlighting on\r\n    filetype plugin on\r\n    au BufRead,BufNewFile *.txt setlocal ft=txt\r\n    au BufRead,BufNewFile *.rst setlocal ft=rst\r\n    au BufRead,BufNewFile *.gdb setlocal ft=gdb","5":"1) Please make sure universal-ctags(https:\/\/github.com\/universal-ctags\/ctags) has been installed(Exuberant Ctags doesn't work for .rst files).\r\n\r\n2) Please make sure taglist(vimscript #273: taglist.vim) has been installed.\r\n\r\n3) Download the txtbrowser file and uncompress the files to your .vim directory:\r\n\r\n    $ tar xvf txtbrowser-1.3.6.tar.bz2 -C ~\/\r\n    .vim\/\r\n    .vim\/doc\/\r\n    .vim\/doc\/txtbrowser.cnx\r\n    .vim\/doc\/txtbrowser.txt\r\n    .vim\/ftplugin\/\r\n    .vim\/ftplugin\/gdb.vim\r\n    .vim\/ftplugin\/rst.vim\r\n    .vim\/ftplugin\/txt.vim\r\n    .vim\/plugin\/\r\n    .vim\/plugin\/txtbrowser.vim\r\n    .vim\/syntax\/\r\n    .vim\/syntax\/txt.vim\r\n\r\n4) open the .vim\/doc\/txtbrowser.txt Install the helptags using \":helptags .\"\r\n\r\n5) Add the following line into your .vimrc file and restart your vim.\r\n\r\n    syntax on \"syntax highlighting on\r\n    filetype plugin on\r\n    au BufRead,BufNewFile *.txt setlocal ft=txt\r\n    au BufRead,BufNewFile *.rst setlocal ft=rst\r\n    au BufRead,BufNewFile *.gdb setlocal ft=gdb","first_name":"yp","6":"yp","last_name":"guo","7":"guo","releases":[{"0":"2899","vim_version":"7.0","1":"7.0","script_version":"1.3.6","2":"1.3.6","version_comment":"1) Support .rst file.\r\n2) Support .gdb file.\r\n","3":"1) Support .rst file.\r\n2) Support .gdb file.\r\n","package":"txtbrowser-1.3.6.tar.bz2","4":"txtbrowser-1.3.6.tar.bz2","src_id":"28118","5":"28118","creation_date":"1659807768","6":"1659807768"},{"0":"2899","vim_version":"6.0","1":"6.0","script_version":"1.3.5","2":"1.3.5","version_comment":"1) Since tatlist window could show titles like \"digit+space+char\", Highlight them;\r\n2) The default dictionary is changed from \"www.google.cn\/dictionary\" to \"www.google.com\/dictionary\".\r\n3) Using maparg() insteading of mapcheck() to check whether the map exist.\r\n4) Add some new features such as \"Make the text Bold\/Italic\/Red\/Green\/Blue\". It is informational and will function in most cases, but still have many problems.\r\n5) support url such as \"https:\/\/\";\r\n6) Allow user to open the url with user defined browser, and the screen will update immediately;","3":"1) Since tatlist window could show titles like \"digit+space+char\", Highlight them;\r\n2) The default dictionary is changed from \"www.google.cn\/dictionary\" to \"www.google.com\/dictionary\".\r\n3) Using maparg() insteading of mapcheck() to check whether the map exist.\r\n4) Add some new features such as \"Make the text Bold\/Italic\/Red\/Green\/Blue\". It is informational and will function in most cases, but still have many problems.\r\n5) support url such as \"https:\/\/\";\r\n6) Allow user to open the url with user defined browser, and the screen will update immediately;","package":"txtbrowser-1.3.5.zip","4":"txtbrowser-1.3.5.zip","src_id":"16207","5":"16207","creation_date":"1312630472","6":"1312630472"},{"0":"2899","vim_version":"6.0","1":"6.0","script_version":"1.3.4","2":"1.3.4","version_comment":"1. Add all the function to the right click menu. Shall I disable the right click menu by default? I need advice.\r\n2. Fix somes bugs. Thanks to Hong Xu for warm help.","3":"1. Add all the function to the right click menu. Shall I disable the right click menu by default? I need advice.\r\n2. Fix somes bugs. Thanks to Hong Xu for warm help.","package":"txtbrowser-1.3.4.zip","4":"txtbrowser-1.3.4.zip","src_id":"13506","5":"13506","creation_date":"1281147342","6":"1281147342"},{"0":"2899","vim_version":"6.0","1":"6.0","script_version":"1.3.3","2":"1.3.3","version_comment":"Use the \"#\" to search backward insteading of \"?\", it's default in vim. Thanks to Hong Xu again for warm advice.","3":"Use the \"#\" to search backward insteading of \"?\", it's default in vim. Thanks to Hong Xu again for warm advice.","package":"txtbrowser-1.3.3.zip","4":"txtbrowser-1.3.3.zip","src_id":"13319","5":"13319","creation_date":"1278810008","6":"1278810008"},{"0":"2899","vim_version":"6.0","1":"6.0","script_version":"1.3.2","2":"1.3.2","version_comment":"1) Highlight the braces, quotes and square brackets along with the syntax matchs.\r\n2) Only highlight the syntax \"txtList\" itself, not including the spaces ahead of it.\r\n3) Add New features: ?: Search backward for the word under cursor(or selected).\r\nThanks to Pengo and Hong Xu for warm advice.","3":"1) Highlight the braces, quotes and square brackets along with the syntax matchs.\r\n2) Only highlight the syntax \"txtList\" itself, not including the spaces ahead of it.\r\n3) Add New features: ?: Search backward for the word under cursor(or selected).\r\nThanks to Pengo and Hong Xu for warm advice.","package":"txtbrowser-1.3.2.zip","4":"txtbrowser-1.3.2.zip","src_id":"13309","5":"13309","creation_date":"1278657131","6":"1278657131"},{"0":"2899","vim_version":"6.0","1":"6.0","script_version":"1.3.1","2":"1.3.1","version_comment":"Add new features:\r\n<Leader>h: Highlight the word under cursor(or selected);\r\n*: Search forward for the word under cursor(or selected).","3":"Add new features:\r\n<Leader>h: Highlight the word under cursor(or selected);\r\n*: Search forward for the word under cursor(or selected).","package":"txtbrowser-1.3.1.zip","4":"txtbrowser-1.3.1.zip","src_id":"13216","5":"13216","creation_date":"1276932638","6":"1276932638"},{"0":"2899","vim_version":"6.0","1":"6.0","script_version":"1.3","2":"1.3","version_comment":"Equal to 1.2.9, Compared to version 1.2, there are changes as following:\r\n1)Infrastructure improvement for easy install. Users only need to unzip the file to you $HOME or vimfiles directory.\r\n2)Bug fix: fix many bugs in encodings, Now Chinese in almost every circumstance could be show normally.\r\n3)Bug fix: syntax highligh parse error between two \"'s\".\r\n4)Other bug fix and feature improvement.","3":"Equal to 1.2.9, Compared to version 1.2, there are changes as following:\r\n1)Infrastructure improvement for easy install. Users only need to unzip the file to you $HOME or vimfiles directory.\r\n2)Bug fix: fix many bugs in encodings, Now Chinese in almost every circumstance could be show normally.\r\n3)Bug fix: syntax highligh parse error between two \"'s\".\r\n4)Other bug fix and feature improvement.","package":"txtbrowser-1.3.zip","4":"txtbrowser-1.3.zip","src_id":"13214","5":"13214","creation_date":"1276919744","6":"1276919744"},{"0":"2899","vim_version":"6.0","1":"6.0","script_version":"1.2","2":"1.2","version_comment":"This version(1.2) equals to version 1.1.8. Minor version upgrade to wait for\r\nnew feature added. compared to 1.1, there are changes:\r\n1)Plugin name changed from \"txt.zip\" to \"TxtBrowser\"\r\n2)Add utilities to browser url in vim.\r\n3)bug fix for Chinese title couldn't listed(\":help txt-faqs\" 6.2 for details)","3":"This version(1.2) equals to version 1.1.8. Minor version upgrade to wait for\r\nnew feature added. compared to 1.1, there are changes:\r\n1)Plugin name changed from \"txt.zip\" to \"TxtBrowser\"\r\n2)Add utilities to browser url in vim.\r\n3)bug fix for Chinese title couldn't listed(\":help txt-faqs\" 6.2 for details)","package":"txtbrowser.zip","4":"txtbrowser.zip","src_id":"12563","5":"12563","creation_date":"1267833818","6":"1267833818"},{"0":"2899","vim_version":"6.0","1":"6.0","script_version":"1.1","2":"1.1","version_comment":"Same as release 1.0.6(minor change.) Version upgrate to 1.1.x for new features release. Changes since version 1.0:\r\n1) Delete some personal configuration in txt.vim.\r\n2) Add the help document in both English and Chinese. ","3":"Same as release 1.0.6(minor change.) Version upgrate to 1.1.x for new features release. Changes since version 1.0:\r\n1) Delete some personal configuration in txt.vim.\r\n2) Add the help document in both English and Chinese. ","package":"txt.zip","4":"txt.zip","src_id":"12165","5":"12165","creation_date":"1264218881","6":"1264218881"},{"0":"2899","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"txt.zip","4":"txt.zip","src_id":"11955","5":"11955","creation_date":"1261796818","6":"1261796818"}]},"2898":{"script_id":"2898","0":"2898","script_name":"circos.vim","1":"circos.vim","script_type":"syntax","2":"syntax","summary":"Syntax file for Circos visualization program conf files","3":"Syntax file for Circos visualization program conf files","description":"Circos http:\/\/mkweb.bcgsc.ca\/circos is a visualization program for genes, but can also be used for anything you would like to visualize as a circle with relationships.\r\n\r\nThis syntax file helps edit circos.conf, ideogram.conf and ticks.conf.","4":"Circos http:\/\/mkweb.bcgsc.ca\/circos is a visualization program for genes, but can also be used for anything you would like to visualize as a circle with relationships.\r\n\r\nThis syntax file helps edit circos.conf, ideogram.conf and ticks.conf.","install_details":"Copy circos.vim to your ~\/.vim\/syntax\/ directory\r\n\r\nOn your configuration file ~\/.vimrc add the following lines:\r\n\r\naugroup filetype\r\n  au! BufNewFile,BufRead circos*conf,ideogram*conf,ticks*conf  set ft=circos ai textwidth=80 formatoptions=tcroqn2 comments=n:>\r\naugroup END\r\n","5":"Copy circos.vim to your ~\/.vim\/syntax\/ directory\r\n\r\nOn your configuration file ~\/.vimrc add the following lines:\r\n\r\naugroup filetype\r\n  au! BufNewFile,BufRead circos*conf,ideogram*conf,ticks*conf  set ft=circos ai textwidth=80 formatoptions=tcroqn2 comments=n:>\r\naugroup END\r\n","first_name":"Jose Manuel","6":"Jose Manuel","last_name":"Pavon","7":"Pavon","releases":[{"0":"2898","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"circos.vim","4":"circos.vim","src_id":"11950","5":"11950","creation_date":"1261736525","6":"1261736525"}]},"2897":{"script_id":"2897","0":"2897","script_name":"Chrysoprase","1":"Chrysoprase","script_type":"color scheme","2":"color scheme","summary":"A dark-on-light colour scheme","3":"A dark-on-light colour scheme","description":"Chrysoprase is a Vim colour scheme influenced by the github.com default syntax highlighting colour theme.  \r\n\r\nScreenshots:\r\n\r\nHaskell with two vertical windows: http:\/\/users.jyu.fi\/~anhekalm\/misc\/chrysoprase1.png\r\nPHP with TagList and NERDTree: http:\/\/users.jyu.fi\/~anhekalm\/misc\/chrysoprase2.png\r\n\r\n(Font used is DejaVu Sans Mono 12pt with GDI++ font enhancements on Windows 7.)","4":"Chrysoprase is a Vim colour scheme influenced by the github.com default syntax highlighting colour theme.  \r\n\r\nScreenshots:\r\n\r\nHaskell with two vertical windows: http:\/\/users.jyu.fi\/~anhekalm\/misc\/chrysoprase1.png\r\nPHP with TagList and NERDTree: http:\/\/users.jyu.fi\/~anhekalm\/misc\/chrysoprase2.png\r\n\r\n(Font used is DejaVu Sans Mono 12pt with GDI++ font enhancements on Windows 7.)","install_details":"Copy chrysoprase.vim to the $VIMFILES\/colors\/ directory and restart Vim and type :colorscheme chrysoprase.","5":"Copy chrysoprase.vim to the $VIMFILES\/colors\/ directory and restart Vim and type :colorscheme chrysoprase.","first_name":"Antoine","6":"Antoine","last_name":"Kalmbach","7":"Kalmbach","releases":[{"0":"2897","vim_version":"7.0","1":"7.0","script_version":"0.0.2","2":"0.0.2","version_comment":"Improved the contrasts on cursor block, current line and column highlights.","3":"Improved the contrasts on cursor block, current line and column highlights.","package":"chrysoprase.vim","4":"chrysoprase.vim","src_id":"11951","5":"11951","creation_date":"1261738874","6":"1261738874"},{"0":"2897","vim_version":"7.0","1":"7.0","script_version":"0.0.1","2":"0.0.1","version_comment":"Initial upload","3":"Initial upload","package":"chrysoprase.vim","4":"chrysoprase.vim","src_id":"11948","5":"11948","creation_date":"1261668059","6":"1261668059"}]},"2896":{"script_id":"2896","0":"2896","script_name":"open terminal, filemanager","1":"open terminal, filemanager","script_type":"utility","2":"utility","summary":"Open native terminal , file manager app for various platforms","3":"Open native terminal , file manager app for various platforms","description":"Some vim user want to shell like emacs's eshell. But vim don't support shell, \r\nterminal interface in vim (at least  7.x version). \r\n\r\nIn this situation, I try some terminal patches or shell attached plugins. But everyone don't perfectly emulate native terminal or have much dependencies. So I use simple native terminal and filemanager open script for my various platforms. \r\n\r\n\r\n\r\nCommmands \r\n    :OpenTerminal              Open native terminal sw. \r\n    :OpenFilemanager        Open native file manager. \r\n\r\n\r\n\r\nKey map recommendations (I'm using) \r\n   nnoremap <silent> <F9> :OpenTerminal<CR> \r\n   nnoremap <silent> <F10> :OpenFilemanager<CR><CR> \r\n\r\n\r\n\r\nTested platform \r\n * Mac  ~ Terminal.app,      finder\r\n  * MacVim\r\n * Windows 7 64bit, XP ~cmd.exe , explorer \r\n  * [portable] gVim\r\n * Gnome  ~ gnome-terminal,  nautilus\r\n  * gVim\r\n\r\nThis is very simple script. If plugin show wrong operation feedback to me. I can't test in windows xp, KDE etc  :)\r\n ","4":"Some vim user want to shell like emacs's eshell. But vim don't support shell, \r\nterminal interface in vim (at least  7.x version). \r\n\r\nIn this situation, I try some terminal patches or shell attached plugins. But everyone don't perfectly emulate native terminal or have much dependencies. So I use simple native terminal and filemanager open script for my various platforms. \r\n\r\n\r\n\r\nCommmands \r\n    :OpenTerminal              Open native terminal sw. \r\n    :OpenFilemanager        Open native file manager. \r\n\r\n\r\n\r\nKey map recommendations (I'm using) \r\n   nnoremap <silent> <F9> :OpenTerminal<CR> \r\n   nnoremap <silent> <F10> :OpenFilemanager<CR><CR> \r\n\r\n\r\n\r\nTested platform \r\n * Mac  ~ Terminal.app,      finder\r\n  * MacVim\r\n * Windows 7 64bit, XP ~cmd.exe , explorer \r\n  * [portable] gVim\r\n * Gnome  ~ gnome-terminal,  nautilus\r\n  * gVim\r\n\r\nThis is very simple script. If plugin show wrong operation feedback to me. I can't test in windows xp, KDE etc  :)\r\n ","install_details":"open \"open_terminal.vba\" with vim\r\n:so %\r\n:help open-terminal\r\n\r\n","5":"open \"open_terminal.vba\" with vim\r\n:so %\r\n:help open-terminal\r\n\r\n","first_name":"Sangmin","6":"Sangmin","last_name":"Ryu","7":"Ryu","releases":[{"0":"2896","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"open_terminal.vba","4":"open_terminal.vba","src_id":"11941","5":"11941","creation_date":"1261521731","6":"1261521731"}]},"2895":{"script_id":"2895","0":"2895","script_name":"PyPit","1":"PyPit","script_type":"utility","2":"utility","summary":"Python version of pitconfig.vim","3":"Python version of pitconfig.vim","description":"You can put configurations such as passwords or user names out of vimrc.\r\n\r\nWhen you want to backup vimrc into public repository service such as GitHub, you may put secret informations out of vimrc.\r\nBut how?\r\n\r\npypit.vim (and its parents, pitconfig.vim and rbpit.vim) can.\r\n\r\nAs pitconfig.vim requires Perl interface, and rbpit.vim requires Ruby interface, pypit.vim requires Python interface.","4":"You can put configurations such as passwords or user names out of vimrc.\r\n\r\nWhen you want to backup vimrc into public repository service such as GitHub, you may put secret informations out of vimrc.\r\nBut how?\r\n\r\npypit.vim (and its parents, pitconfig.vim and rbpit.vim) can.\r\n\r\nAs pitconfig.vim requires Perl interface, and rbpit.vim requires Ruby interface, pypit.vim requires Python interface.","install_details":"1) Download zip archive and unzip it.\r\n\r\n2) Put doc and plugin directory in:\r\n- Windows: $HOME\/vimfiles\r\n- UNIX (include Cygwin): $HOME\/.vim\r\n\r\n3) install Pit Python module using easy_install:\r\n$ easy_install pit\r\n(if you are in Linux, you may use package manager such as apt or yum)","5":"1) Download zip archive and unzip it.\r\n\r\n2) Put doc and plugin directory in:\r\n- Windows: $HOME\/vimfiles\r\n- UNIX (include Cygwin): $HOME\/.vim\r\n\r\n3) install Pit Python module using easy_install:\r\n$ easy_install pit\r\n(if you are in Linux, you may use package manager such as apt or yum)","first_name":"Masanori","6":"Masanori","last_name":"OGINO","7":"OGINO","releases":[{"0":"2895","vim_version":"7.0","1":"7.0","script_version":"0.0.2","2":"0.0.2","version_comment":"Fix many bugs.","3":"Fix many bugs.","package":"pypit.zip","4":"pypit.zip","src_id":"11946","5":"11946","creation_date":"1261611269","6":"1261611269"},{"0":"2895","vim_version":"7.2","1":"7.2","script_version":"0.0.1","2":"0.0.1","version_comment":"Initial upload","3":"Initial upload","package":"pypit.zip","4":"pypit.zip","src_id":"11935","5":"11935","creation_date":"1261440801","6":"1261440801"}]},"2894":{"script_id":"2894","0":"2894","script_name":"vikitasks","1":"vikitasks","script_type":"utility","2":"utility","summary":"A \"distributed\" todo lists manager for viki (with limited support for todo.txt)","3":"A \"distributed\" todo lists manager for viki (with limited support for todo.txt)","description":"vikitasks is a distributed todo lists manager. It provides a quick \r\noverview of priority\/task lists maintained in several viki files. \r\nDepending on your settings, you can quickly search all \"homepages\" \r\nof intervikis or search only project-specific files. Buffers \r\ncontaining task lists are added to the list of vikitasks. There is \r\nalso an option to view a list of current tasks on startup.\r\n\r\nDemo:\r\nhttp:\/\/vimsomnia.blogspot.com\/2010\/11\/vikitasks-viki-demonstration-personal.html\r\n\r\nUsage:\r\n    :VikiTasks[!] [CONSTRAINT] [PATTERN] [FILE_PATTERNS]\r\n\r\n\r\nFeatures:\r\n    - Collect tasks from viki's priority lists (see |viki-tasks|)\r\n    - Sort those tasks\r\n    - Browse tasks with a given date\r\n    - Optionally browse all tasks (incl. those without a date)\r\n\r\n\r\nLet's say you have the files:\r\n\r\nfoo.txt: >\r\n    * Foo\r\n        #A 2009-12-13 Do this\r\n        #C 2009-12-20 :call @Anna What was it she wanted to tell me?\r\n        #A Whatever\r\n\r\nbar.txt: >\r\n    * Bar\r\n        #C 2009-12-24 :call @Bernie Wish him good luck\r\n        #D 2009-11-01 Do that\r\n\r\nLet's assume you have added both files to |g:vikitasks#files|. Switch to \r\nthe buffer foo.txt and call >\r\n\r\n    :VikiTasks!\r\n\r\nand you get the following list: >\r\n\r\n    Bar.txt|2| #D 2009-11-01 Do that\r\n    Foo.txt|2| #A 2009-12-13 Do this\r\n    Foo.txt|3| #C 2009-12-20 Call @Anna\r\n    Bar.txt|3| #C 2009-12-24 Wish @Bernie good luck\r\n\r\nIf you do\/had done this on the 15 December 2009, the third line would be \r\nhighlighted, i.e. the entries above the cursor refer to passed\/missed \r\nevents. If you had called :VikiTasks! (behold the bang), then the \r\n\"Whatever\" entry would have been included in the list too.\r\n\r\nIf you had called >\r\n    \r\n    :VikiTasks current\r\n\r\nonly the first two items would be listed.\r\n\r\nThis week's tasks (i.e. the tasks that should be accomplished today or \r\nwithin the following six days) could be listed with >\r\n    \r\n    :VikiTasks 6\r\n\r\n\r\nAlso available via git\r\nhttp:\/\/github.com\/tomtom\/vikitasks_vim","4":"vikitasks is a distributed todo lists manager. It provides a quick \r\noverview of priority\/task lists maintained in several viki files. \r\nDepending on your settings, you can quickly search all \"homepages\" \r\nof intervikis or search only project-specific files. Buffers \r\ncontaining task lists are added to the list of vikitasks. There is \r\nalso an option to view a list of current tasks on startup.\r\n\r\nDemo:\r\nhttp:\/\/vimsomnia.blogspot.com\/2010\/11\/vikitasks-viki-demonstration-personal.html\r\n\r\nUsage:\r\n    :VikiTasks[!] [CONSTRAINT] [PATTERN] [FILE_PATTERNS]\r\n\r\n\r\nFeatures:\r\n    - Collect tasks from viki's priority lists (see |viki-tasks|)\r\n    - Sort those tasks\r\n    - Browse tasks with a given date\r\n    - Optionally browse all tasks (incl. those without a date)\r\n\r\n\r\nLet's say you have the files:\r\n\r\nfoo.txt: >\r\n    * Foo\r\n        #A 2009-12-13 Do this\r\n        #C 2009-12-20 :call @Anna What was it she wanted to tell me?\r\n        #A Whatever\r\n\r\nbar.txt: >\r\n    * Bar\r\n        #C 2009-12-24 :call @Bernie Wish him good luck\r\n        #D 2009-11-01 Do that\r\n\r\nLet's assume you have added both files to |g:vikitasks#files|. Switch to \r\nthe buffer foo.txt and call >\r\n\r\n    :VikiTasks!\r\n\r\nand you get the following list: >\r\n\r\n    Bar.txt|2| #D 2009-11-01 Do that\r\n    Foo.txt|2| #A 2009-12-13 Do this\r\n    Foo.txt|3| #C 2009-12-20 Call @Anna\r\n    Bar.txt|3| #C 2009-12-24 Wish @Bernie good luck\r\n\r\nIf you do\/had done this on the 15 December 2009, the third line would be \r\nhighlighted, i.e. the entries above the cursor refer to passed\/missed \r\nevents. If you had called :VikiTasks! (behold the bang), then the \r\n\"Whatever\" entry would have been included in the list too.\r\n\r\nIf you had called >\r\n    \r\n    :VikiTasks current\r\n\r\nonly the first two items would be listed.\r\n\r\nThis week's tasks (i.e. the tasks that should be accomplished today or \r\nwithin the following six days) could be listed with >\r\n    \r\n    :VikiTasks 6\r\n\r\n\r\nAlso available via git\r\nhttp:\/\/github.com\/tomtom\/vikitasks_vim","install_details":"Edit the vba file and type: >\r\n\r\n    :so %\r\n\r\nSee :help vimball for details. If you have difficulties or use vim 7.0, \r\nplease make sure, you have the current version of vimball\r\n(vimscript #1502) installed or update your runtime.\r\n\r\nThis script requires tlib (vimscript #1863), trag (vimscript #2033), and \r\nviki (vimscript #861) to be installed.\r\n","5":"Edit the vba file and type: >\r\n\r\n    :so %\r\n\r\nSee :help vimball for details. If you have difficulties or use vim 7.0, \r\nplease make sure, you have the current version of vimball\r\n(vimscript #1502) installed or update your runtime.\r\n\r\nThis script requires tlib (vimscript #1863), trag (vimscript #2033), and \r\nviki (vimscript #861) to be installed.\r\n","first_name":"Tom","6":"Tom","last_name":"Link","7":"Link","releases":[{"0":"2894","vim_version":"7.0","1":"7.0","script_version":"1.02","2":"1.02","version_comment":"- Fix variable name in doc\n- Grammar tweaks\n- Doc edits and rename three functions\n- <f2>k: Select items in a certain category\n- intervikis config went to vikitasks#ft#viki#intervikis\n- intervikis config moved\n- g:vikitasks_startup_alarms is an expression\n- vikitasks#OnLeave(): Don't use :wall but :update on each modified buffer\n- vikitasks#OnLeave(): Make sure to scan changed buffers on leave\n- s:ScanFiles(): for i in reverse(remove_tasks\n- Prepare for taskpaper support\n- Initial support for taskpaper\n- VikiTasksDueInMonths\n- CLOSE #8: g:vikitasks#rx_letters -> g:vikitasks#rx_categories in docs (thanks Garonenur)\n- ftplugin\/viki: let b:vikiSpecialProtocols .= '\\|todo'\n- resolve() dir names\n- ftplugin\/todotxt: let g:vikiOpenUrlWith_todo = 'call vikitasks#ft#todotxt#OpenTodoUrl(''%{URL}'')'\n- viki\/GetFiles(): Fix iv_include\/iv_exclude\n- Adapt for tlib 1.15 etc.\n- vikitasks#FormatQFLE: Use tlib#qfl#QfeFilename\n- FIX #9: adapt for use of tlib 1.16; misc enhancements\n- Use tlib#file#Glob()\n- vikitasks#AgentPaste: check range\n- s\/TLibTrace\/Tlibtrace\/g\nMD5 checksum: 0716a81d4db8946d8b81ecacc289011d","3":"- Fix variable name in doc\n- Grammar tweaks\n- Doc edits and rename three functions\n- <f2>k: Select items in a certain category\n- intervikis config went to vikitasks#ft#viki#intervikis\n- intervikis config moved\n- g:vikitasks_startup_alarms is an expression\n- vikitasks#OnLeave(): Don't use :wall but :update on each modified buffer\n- vikitasks#OnLeave(): Make sure to scan changed buffers on leave\n- s:ScanFiles(): for i in reverse(remove_tasks\n- Prepare for taskpaper support\n- Initial support for taskpaper\n- VikiTasksDueInMonths\n- CLOSE #8: g:vikitasks#rx_letters -> g:vikitasks#rx_categories in docs (thanks Garonenur)\n- ftplugin\/viki: let b:vikiSpecialProtocols .= '\\|todo'\n- resolve() dir names\n- ftplugin\/todotxt: let g:vikiOpenUrlWith_todo = 'call vikitasks#ft#todotxt#OpenTodoUrl(''%{URL}'')'\n- viki\/GetFiles(): Fix iv_include\/iv_exclude\n- Adapt for tlib 1.15 etc.\n- vikitasks#FormatQFLE: Use tlib#qfl#QfeFilename\n- FIX #9: adapt for use of tlib 1.16; misc enhancements\n- Use tlib#file#Glob()\n- vikitasks#AgentPaste: check range\n- s\/TLibTrace\/Tlibtrace\/g\nMD5 checksum: 0716a81d4db8946d8b81ecacc289011d","package":"vikitasks.vba","4":"vikitasks.vba","src_id":"23723","5":"23723","creation_date":"1447087478","6":"1447087478"},{"0":"2894","vim_version":"7.0","1":"7.0","script_version":"1.01","2":"1.01","version_comment":"- Support for threshold dates (t:YYYY-MM-DD)\n- IsThresholdOk(): ignore \"t:\" prefix\n- g:vikitasks#threshold_days: Hide tasks with due dates N days in the future\n- ScanFiles(): Avoid random error and display a message\n- ScanFiles(): Display error message for unknown buffers\n- Clean up task lines (e.g. remove \"t:\" threshold tags)\n- Use index_next_syntax for customization\n- Use set_syntax & format_item\n- vikitasks#SetSyntax(): Define vikitasksItem syntax; set b:vikiMarkInexistent = 0\n- vikitasks#SetSyntax(): Hide some dates\n- Show progressbar more often\n- AgentDueWeeks, AgentDueDays: Abort correctly when pressing <c-c>\n- todotxt: ConvertLine(): Don't add default due date if g:vikitasks#ft#todotxt#due_default is empty\n- g:vikitasks#auto_save: f true, save _all_ modified buffers via |:wall|, when leaving the tasks list.\n- g:vikitasks#ft#todotxt#respect_h1: hide lines containing a h:1 tag in todo.txt files (used by SimpleTask app)\n- Require tlib 1.06 & trag 1.02\nMD5 checksum: b20334cce201fa22484ea6bc523f7eb4","3":"- Support for threshold dates (t:YYYY-MM-DD)\n- IsThresholdOk(): ignore \"t:\" prefix\n- g:vikitasks#threshold_days: Hide tasks with due dates N days in the future\n- ScanFiles(): Avoid random error and display a message\n- ScanFiles(): Display error message for unknown buffers\n- Clean up task lines (e.g. remove \"t:\" threshold tags)\n- Use index_next_syntax for customization\n- Use set_syntax & format_item\n- vikitasks#SetSyntax(): Define vikitasksItem syntax; set b:vikiMarkInexistent = 0\n- vikitasks#SetSyntax(): Hide some dates\n- Show progressbar more often\n- AgentDueWeeks, AgentDueDays: Abort correctly when pressing <c-c>\n- todotxt: ConvertLine(): Don't add default due date if g:vikitasks#ft#todotxt#due_default is empty\n- g:vikitasks#auto_save: f true, save _all_ modified buffers via |:wall|, when leaving the tasks list.\n- g:vikitasks#ft#todotxt#respect_h1: hide lines containing a h:1 tag in todo.txt files (used by SimpleTask app)\n- Require tlib 1.06 & trag 1.02\nMD5 checksum: b20334cce201fa22484ea6bc523f7eb4","package":"vikitasks.vba","4":"vikitasks.vba","src_id":"22594","5":"22594","creation_date":"1414922085","6":"1414922085"},{"0":"2894","vim_version":"7.0","1":"7.0","script_version":"1.00","2":"1.00","version_comment":"- Help template\n- FIX Don't call VikiTasksDueInDays & VikiTasksDueInWeeks with <count>\n- <c-n> Paste selected items into a new window\n- Rewrite A\n- Remove s:files (use s:file_defs instead)\n- Full support for todo.txt (requires trag 0.12)\n- Correctly set today marker for last but one item\n- g:vikitasks#filetype_map\n- todo.txt: Improved support for changing the category\/priority\n- .ArchiveHeader(): type error\n- FIX support for scanning intervikis\n- :VikiTasksAlarms: FIX bang value\n- #AfterChange hook\n- g:vikitasks#rx_letters defaults to 'A-P'\n- Renamed g:vikitasks#rx_letters to g:vikitasks#rx_categories\n- g:vikitasks#alarms: Support for persistent_categories (always include tasks in these categories in the \"Alarms\" list)\n- FIX Use g:vikitasks#rx_categories in todotxt.vim\n- g:vikitasks#alarms.persistent_categories defaults to [A]\n- g:vikitasks#cache_check_mtime: Detect files that were changed by external programs based on mtime\n- s:GetTasks() if g:vikitasks#cache_check_mtime: Remove obsolete filename\n- g:vikitasks#cache_check_mtime_rx (replaces g:vikitasks#cache_check_mtime)\n- Checking g:vikitasks#cache_check_mtime_rx actually works (properly init trag)\n- g:vikitasks_startup_alarms defaults to 0 (without user intervention don't display alarms on startup)\n- g:vikitasks#after_change_buffer_exec: Run command after changing a buffer\n- g:vikitasks#use_unspecified_dates default to 1\n- scriptencoding utf-8\n- g:vikitasks#files_ignored defaults to ['_archived\\.[^.]\\+$']\n- g:vikitasks#convert_cygwin\n- Misc improvements\n- Load cached data only once\n- FIX: duplicate entries\nMD5 checksum: f1556492bc4b63a0275c2bf6f37141fe","3":"- Help template\n- FIX Don't call VikiTasksDueInDays & VikiTasksDueInWeeks with <count>\n- <c-n> Paste selected items into a new window\n- Rewrite A\n- Remove s:files (use s:file_defs instead)\n- Full support for todo.txt (requires trag 0.12)\n- Correctly set today marker for last but one item\n- g:vikitasks#filetype_map\n- todo.txt: Improved support for changing the category\/priority\n- .ArchiveHeader(): type error\n- FIX support for scanning intervikis\n- :VikiTasksAlarms: FIX bang value\n- #AfterChange hook\n- g:vikitasks#rx_letters defaults to 'A-P'\n- Renamed g:vikitasks#rx_letters to g:vikitasks#rx_categories\n- g:vikitasks#alarms: Support for persistent_categories (always include tasks in these categories in the \"Alarms\" list)\n- FIX Use g:vikitasks#rx_categories in todotxt.vim\n- g:vikitasks#alarms.persistent_categories defaults to [A]\n- g:vikitasks#cache_check_mtime: Detect files that were changed by external programs based on mtime\n- s:GetTasks() if g:vikitasks#cache_check_mtime: Remove obsolete filename\n- g:vikitasks#cache_check_mtime_rx (replaces g:vikitasks#cache_check_mtime)\n- Checking g:vikitasks#cache_check_mtime_rx actually works (properly init trag)\n- g:vikitasks_startup_alarms defaults to 0 (without user intervention don't display alarms on startup)\n- g:vikitasks#after_change_buffer_exec: Run command after changing a buffer\n- g:vikitasks#use_unspecified_dates default to 1\n- scriptencoding utf-8\n- g:vikitasks#files_ignored defaults to ['_archived\\.[^.]\\+$']\n- g:vikitasks#convert_cygwin\n- Misc improvements\n- Load cached data only once\n- FIX: duplicate entries\nMD5 checksum: f1556492bc4b63a0275c2bf6f37141fe","package":"vikitasks.vba","4":"vikitasks.vba","src_id":"21714","5":"21714","creation_date":"1396459136","6":"1396459136"},{"0":"2894","vim_version":"7.0","1":"7.0","script_version":"0.06","2":"0.06","version_comment":"- Check the value of g:tlib_filename_sep instead of !&shellslash\n- addon-info\n- <c-c>, <localleader>tc: Change a task's category\n- If g:vikitasks#files contains glob patterns, make sure to remove duplicates\n- s:AddInterVikis(): move adding of dir\/pattern to s:AddDirPattern()\n- viki maps: Remove count with <c-u> from maps\n- Adapt for tlib 1.06\n- NEW :VikiTasksPaste command: paste vikitasks items to a (new) buffer (closes #4)\n- Small docs tweaks\n- Make display of pasted tasks list configurable via g:vikitasks#paste\n- Do doc tweaks on source instead\n- Merge branch 'master' of https:\/\/github.com\/tomtom\/vikitasks_vim\n- Typo\n- We're using N for [count], right?\n- Consider [count]\nMD5 checksum: 7d53532b805b741dd90d65def5b546f1","3":"- Check the value of g:tlib_filename_sep instead of !&shellslash\n- addon-info\n- <c-c>, <localleader>tc: Change a task's category\n- If g:vikitasks#files contains glob patterns, make sure to remove duplicates\n- s:AddInterVikis(): move adding of dir\/pattern to s:AddDirPattern()\n- viki maps: Remove count with <c-u> from maps\n- Adapt for tlib 1.06\n- NEW :VikiTasksPaste command: paste vikitasks items to a (new) buffer (closes #4)\n- Small docs tweaks\n- Make display of pasted tasks list configurable via g:vikitasks#paste\n- Do doc tweaks on source instead\n- Merge branch 'master' of https:\/\/github.com\/tomtom\/vikitasks_vim\n- Typo\n- We're using N for [count], right?\n- Consider [count]\nMD5 checksum: 7d53532b805b741dd90d65def5b546f1","package":"vikitasks.vba","4":"vikitasks.vba","src_id":"20933","5":"20933","creation_date":"1382117886","6":"1382117886"},{"0":"2894","vim_version":"7.0","1":"7.0","script_version":"0.05","2":"0.05","version_comment":"- Duplicate tag in help file\n- g:vikitasks#today: show a break line in suspended list views\n- VikiTasks: Files pattern arguments sometimes got lost\n- Files patterns were ignored when working with a cached list\n- g:vikitasks#today: Changed to \"DUE\"\n- Integration with\/dependency on viki_vim is now optional\n- Check has('vim_starting') when running vikitasks#Alarm()\n- Experimental support for todo.txt task lists (requires trag 0.10)\n- Improved regexps for todotxt files\n- s:Convert(): Run at most 5 iterations when replacing keywords\n- Access trag_filenames through rag#HasFiletype() and trag#SetFiletype()\n- g:vikitasks#ignore_completed_tasks:  If true, completely ignore completed tasks (fixes #1)\n- g:vikitasks_startup_alarms default value: don't display the alarms list if vim is called with an argument\n- When calling glob() for intervikis, make sure to scan subdirectories\n- Keyboard shortcuts for mark done, archive done, list files etc.\n- Minor changes to how constraints work & new commands: mark done, set due date, archive final\/done tasks etc. (require tlib 1.0)\n- g:vikitasks#use_calendar: use |:Calendar| as date picker\nMD5 checksum: 4bf05727153faee87e36a28483e12211","3":"- Duplicate tag in help file\n- g:vikitasks#today: show a break line in suspended list views\n- VikiTasks: Files pattern arguments sometimes got lost\n- Files patterns were ignored when working with a cached list\n- g:vikitasks#today: Changed to \"DUE\"\n- Integration with\/dependency on viki_vim is now optional\n- Check has('vim_starting') when running vikitasks#Alarm()\n- Experimental support for todo.txt task lists (requires trag 0.10)\n- Improved regexps for todotxt files\n- s:Convert(): Run at most 5 iterations when replacing keywords\n- Access trag_filenames through rag#HasFiletype() and trag#SetFiletype()\n- g:vikitasks#ignore_completed_tasks:  If true, completely ignore completed tasks (fixes #1)\n- g:vikitasks_startup_alarms default value: don't display the alarms list if vim is called with an argument\n- When calling glob() for intervikis, make sure to scan subdirectories\n- Keyboard shortcuts for mark done, archive done, list files etc.\n- Minor changes to how constraints work & new commands: mark done, set due date, archive final\/done tasks etc. (require tlib 1.0)\n- g:vikitasks#use_calendar: use |:Calendar| as date picker\nMD5 checksum: 4bf05727153faee87e36a28483e12211","package":"vikitasks.vba","4":"vikitasks.vba","src_id":"18707","5":"18707","creation_date":"1348830954","6":"1348830954"},{"0":"2894","vim_version":"7.0","1":"7.0","script_version":"0.04","2":"0.04","version_comment":"- s:GetCurrentTask(): skip pending tasks (date = '_')\n- VikiTasksStatic (by tub78)\n- .gitignore\n- Don't check for has('vim_starting')\nMD5 checksum: 2f8c5fc7e4399d35f9f0a8b9a4ea9fef","3":"- s:GetCurrentTask(): skip pending tasks (date = '_')\n- VikiTasksStatic (by tub78)\n- .gitignore\n- Don't check for has('vim_starting')\nMD5 checksum: 2f8c5fc7e4399d35f9f0a8b9a4ea9fef","package":"vikitasks.vba","4":"vikitasks.vba","src_id":"17286","5":"17286","creation_date":"1327166961","6":"1327166961"},{"0":"2894","vim_version":"7.0","1":"7.0","script_version":"0.03","2":"0.03","version_comment":"- g:vikitasks#remove_unreadable_files: Remove unreadable files\n- FIX: remove buffers with no tasks from the list\n- g:vikitasks#use_unspecified_dates: Interpret entries with an unspecified date (\"_\") as current tasks\n- g:vikitasks_startup_alarms doesn't assume a special case for gtk\n- Load viki if it wasn't loaded yet\n- If g:vikitasks#intervikis == 2, scan all interviki pages (not just the homepage)\n- Run VimEnter command immediately if !has('vim_stating')\n- FIX: rx didn't match entries with no text\nMD5 checksum: b1157748e17e1f667c443d0e1d273e41","3":"- g:vikitasks#remove_unreadable_files: Remove unreadable files\n- FIX: remove buffers with no tasks from the list\n- g:vikitasks#use_unspecified_dates: Interpret entries with an unspecified date (\"_\") as current tasks\n- g:vikitasks_startup_alarms doesn't assume a special case for gtk\n- Load viki if it wasn't loaded yet\n- If g:vikitasks#intervikis == 2, scan all interviki pages (not just the homepage)\n- Run VimEnter command immediately if !has('vim_stating')\n- FIX: rx didn't match entries with no text\nMD5 checksum: b1157748e17e1f667c443d0e1d273e41","package":"vikitasks.vba","4":"vikitasks.vba","src_id":"14194","5":"14194","creation_date":"1289047987","6":"1289047987"},{"0":"2894","vim_version":"7.0","1":"7.0","script_version":"0.2b","2":"0.2b","version_comment":"- :VikiTasks now takes a pattern as optional second argument. This change makes the :VikiTasksGrep command obsolete, which was removed.\r\n- Moved the definition of some variables from plugin\/vikitasks.vim to autoload\/vikitasks.vim\r\n- Scan buffers on save\r\n- Require tlib 0.37\r\n- The arguments for :VikiTasks have changed\r\n","3":"- :VikiTasks now takes a pattern as optional second argument. This change makes the :VikiTasksGrep command obsolete, which was removed.\r\n- Moved the definition of some variables from plugin\/vikitasks.vim to autoload\/vikitasks.vim\r\n- Scan buffers on save\r\n- Require tlib 0.37\r\n- The arguments for :VikiTasks have changed\r\n","package":"vikitasks.vba","4":"vikitasks.vba","src_id":"12756","5":"12756","creation_date":"1270055286","6":"1270055286"},{"0":"2894","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"vikitasks.vba.gz","4":"vikitasks.vba.gz","src_id":"11934","5":"11934","creation_date":"1261424048","6":"1261424048"}]},"2893":{"script_id":"2893","0":"2893","script_name":"filetype-completion.vim","1":"filetype-completion.vim","script_type":"utility","2":"utility","summary":"filetype completion","3":"filetype completion","description":"\r\nFiletype Completion\r\n===================\r\n`setfiletype` command doesn't provide completion. this plugin provides a way\r\nfor you to set filetype with a command which supports completion. just type:\r\n\r\n    :sft\r\n\r\nor \r\n\r\n    :setf\r\n\r\n`:sft` or `:setf` will simply expand to SetFiletype command.\r\n","4":"\r\nFiletype Completion\r\n===================\r\n`setfiletype` command doesn't provide completion. this plugin provides a way\r\nfor you to set filetype with a command which supports completion. just type:\r\n\r\n    :sft\r\n\r\nor \r\n\r\n    :setf\r\n\r\n`:sft` or `:setf` will simply expand to SetFiletype command.\r\n","install_details":"just copy to ~\/.vim\/plugin\/","5":"just copy to ~\/.vim\/plugin\/","first_name":"Yo-An","6":"Yo-An","last_name":"Lin","7":"Lin","releases":[{"0":"2893","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"filetype-completion.vim","4":"filetype-completion.vim","src_id":"11929","5":"11929","creation_date":"1261401824","6":"1261401824"}]},"2892":{"script_id":"2892","0":"2892","script_name":"doubleTap","1":"doubleTap","script_type":"ftplugin","2":"ftplugin","summary":"Double Tap Certain Characters to insert and jump out of character pairs.","3":"Double Tap Certain Characters to insert and jump out of character pairs.","description":"This plugin provides an easy, way to insert matching pair characters, ie: [],(),'', and not so matchy characters like + and . , common concatenation characters.\r\n DoubleTap also provides a quick and easy way to terminate a line no matter where on the line the cursor is. \r\nFor instance a double semicolon, ;;, will trim all of the white space at the end of the line and insert a semicolon at the end of the current line.\r\nDoubleTap provides some simple abstraction functions to do the more intricate work and then provides default mappings to wire those functions to characters,pairs and events. You can easily use the core functions provided by doubleTap to create your own mappings and behaviours.\r\n","4":"This plugin provides an easy, way to insert matching pair characters, ie: [],(),'', and not so matchy characters like + and . , common concatenation characters.\r\n DoubleTap also provides a quick and easy way to terminate a line no matter where on the line the cursor is. \r\nFor instance a double semicolon, ;;, will trim all of the white space at the end of the line and insert a semicolon at the end of the current line.\r\nDoubleTap provides some simple abstraction functions to do the more intricate work and then provides default mappings to wire those functions to characters,pairs and events. You can easily use the core functions provided by doubleTap to create your own mappings and behaviours.\r\n","install_details":"unzip doubleTap.zip -d ~\/.vim (or equivalent, e.g. $HOME\\vimfiles on Windows) ","5":"unzip doubleTap.zip -d ~\/.vim (or equivalent, e.g. $HOME\\vimfiles on Windows) ","first_name":"jeff","6":"jeff","last_name":"buttars","7":"buttars","releases":[{"0":"2892","vim_version":"7.0","1":"7.0","script_version":"1","2":"1","version_comment":"Initial upload","3":"Initial upload","package":"doubleTap.zip","4":"doubleTap.zip","src_id":"11928","5":"11928","creation_date":"1261353230","6":"1261353230"}]},"2891":{"script_id":"2891","0":"2891","script_name":"create_start_fold_marker.vim","1":"create_start_fold_marker.vim","script_type":"utility","2":"utility","summary":"create start fold marker with level number","3":"create start fold marker with level number","description":"This plugin helps insert start fold markers with level numbers: {{{1, {{{2, {{{3, and so on. It creates the following global mappings for Normal and Visual modes:\r\n\r\n<Leader>fm         Create start fold marker with level number. It is apppended to the end of current line. The level is set to that of the previous start fold marker with level number (if any). The start fold marker string is obtained from option 'foldmarker'.\r\n\r\n<Leader>fM         Create fold marker as child: level number is incremented by 1.\r\n\r\n<Leader>cm         Create fold marker as comment according to buffer's filetype.  E.g., if filetype is html, <!--{{{1--> is appended. Dictionary s:commentstrings defines comment strings for a few filetypes.  For all other filetypes, comment strings are obtained from option 'commentstring'. If comment strings are not what you want, you can edit dictionary s:commentstrings.\r\n\r\n<Leader>cM         Create fold marker as comment and as child.\r\n","4":"This plugin helps insert start fold markers with level numbers: {{{1, {{{2, {{{3, and so on. It creates the following global mappings for Normal and Visual modes:\r\n\r\n<Leader>fm         Create start fold marker with level number. It is apppended to the end of current line. The level is set to that of the previous start fold marker with level number (if any). The start fold marker string is obtained from option 'foldmarker'.\r\n\r\n<Leader>fM         Create fold marker as child: level number is incremented by 1.\r\n\r\n<Leader>cm         Create fold marker as comment according to buffer's filetype.  E.g., if filetype is html, <!--{{{1--> is appended. Dictionary s:commentstrings defines comment strings for a few filetypes.  For all other filetypes, comment strings are obtained from option 'commentstring'. If comment strings are not what you want, you can edit dictionary s:commentstrings.\r\n\r\n<Leader>cM         Create fold marker as comment and as child.\r\n","install_details":"Source the script or put it in your local plugin folder.","5":"Source the script or put it in your local plugin folder.","first_name":"Vlad","6":"Vlad","last_name":"Irnov","7":"Irnov","releases":[{"0":"2891","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"create_start_fold_marker.vim","4":"create_start_fold_marker.vim","src_id":"11926","5":"11926","creation_date":"1261240701","6":"1261240701"}]},"2890":{"script_id":"2890","0":"2890","script_name":"slurper.vim","1":"slurper.vim","script_type":"utility","2":"utility","summary":"Provides vim features for .slurper files.","3":"Provides vim features for .slurper files.","description":"Description\r\nslurper.vim was written as a companion to the slurper gem (http:\/\/github.com\/hashrocket\/slurper). The slurper gem allows you compose stories in a plain text file and then slurp them into Pivotal Tracker through the api in bulk. You will need to install the slurper gem for slurper.vim to be useful.\r\n\r\nslurper.vim turns on spell check and provides macros for generating story templates in the correct format to speed up your story writing even further. It also provides syntax highlighting and indenting for .slurper files.\r\n\r\nIf you find slurper.vim useful or have suggestions please let me know. Constructive input is greatly appreciated.\r\n\r\nInstallation\r\nDownload the packaged file from www.vim.org\/scripts\/script.php?script_id=2890 extract and copy the slurper.vim files into their corresponding folders within your .vim directory.\r\n\r\nAlternately my preferred method of installing vim plugins is to use Tim Pope's pathogen.vim plugin (http:\/\/www.vim.org\/scripts\/script.php?script_id=2332) and git clone plugins into my ~\/.vimbundles directory.\r\n\r\nUsage\r\nCTRL-h generates a new chore and puts you in insert mode on the name line.\r\n\r\n==\r\nstory_type:\r\n  chore\r\nname:\r\n\r\ndescription:\r\n\r\n\r\nlabels:\r\nCTRL-j generates a new feature and puts you in insert mode on the name line.\r\n\r\n==\r\nstory_type:\r\n  feature\r\nname:\r\n\r\ndescription:\r\n\r\n\r\nlabels:\r\n\r\n\r\nCTRL-k generates a new release and puts you in insert mode on the name line.\r\n\r\n==\r\nstory_type:\r\n  release\r\nname:\r\n\r\ndescription:\r\n\r\n\r\nlabels:\r\n\r\n\r\nCTRL-l generates a new bug and puts you in insert mode on the name line.\r\n\r\n==\r\nstory_type:\r\n  bug\r\nname:\r\n\r\ndescription:\r\n\r\n\r\nlabels:\r\n\r\n\r\nThe macros work the same in insert or edit modes. They also work anywhere in a story file.\r\n\r\nStory Folding\r\nWe found that frequently we wanted to see just a list of all of the features in our file. To do this you can use the built in code folding key strokes.\r\n\r\nClose all folds (Show just story names)\r\n\r\nzM\r\nOpen all folds (Show full stories)\r\n\r\nzR\r\nFor more on folding in Vim check out\r\n\r\n:help folding","4":"Description\r\nslurper.vim was written as a companion to the slurper gem (http:\/\/github.com\/hashrocket\/slurper). The slurper gem allows you compose stories in a plain text file and then slurp them into Pivotal Tracker through the api in bulk. You will need to install the slurper gem for slurper.vim to be useful.\r\n\r\nslurper.vim turns on spell check and provides macros for generating story templates in the correct format to speed up your story writing even further. It also provides syntax highlighting and indenting for .slurper files.\r\n\r\nIf you find slurper.vim useful or have suggestions please let me know. Constructive input is greatly appreciated.\r\n\r\nInstallation\r\nDownload the packaged file from www.vim.org\/scripts\/script.php?script_id=2890 extract and copy the slurper.vim files into their corresponding folders within your .vim directory.\r\n\r\nAlternately my preferred method of installing vim plugins is to use Tim Pope's pathogen.vim plugin (http:\/\/www.vim.org\/scripts\/script.php?script_id=2332) and git clone plugins into my ~\/.vimbundles directory.\r\n\r\nUsage\r\nCTRL-h generates a new chore and puts you in insert mode on the name line.\r\n\r\n==\r\nstory_type:\r\n  chore\r\nname:\r\n\r\ndescription:\r\n\r\n\r\nlabels:\r\nCTRL-j generates a new feature and puts you in insert mode on the name line.\r\n\r\n==\r\nstory_type:\r\n  feature\r\nname:\r\n\r\ndescription:\r\n\r\n\r\nlabels:\r\n\r\n\r\nCTRL-k generates a new release and puts you in insert mode on the name line.\r\n\r\n==\r\nstory_type:\r\n  release\r\nname:\r\n\r\ndescription:\r\n\r\n\r\nlabels:\r\n\r\n\r\nCTRL-l generates a new bug and puts you in insert mode on the name line.\r\n\r\n==\r\nstory_type:\r\n  bug\r\nname:\r\n\r\ndescription:\r\n\r\n\r\nlabels:\r\n\r\n\r\nThe macros work the same in insert or edit modes. They also work anywhere in a story file.\r\n\r\nStory Folding\r\nWe found that frequently we wanted to see just a list of all of the features in our file. To do this you can use the built in code folding key strokes.\r\n\r\nClose all folds (Show just story names)\r\n\r\nzM\r\nOpen all folds (Show full stories)\r\n\r\nzR\r\nFor more on folding in Vim check out\r\n\r\n:help folding","install_details":"Copy slurper.vim files into their corresponding folders within your .vim directory.\r\n\r\nor my preferred method of installing vim plugins is to use Tim Pope's pathogen.vim plugin.\r\n\r\nhttp:\/\/www.vim.org\/scripts\/script.php?script_id=2332","5":"Copy slurper.vim files into their corresponding folders within your .vim directory.\r\n\r\nor my preferred method of installing vim plugins is to use Tim Pope's pathogen.vim plugin.\r\n\r\nhttp:\/\/www.vim.org\/scripts\/script.php?script_id=2332","first_name":"Adam","6":"Adam","last_name":"Lowe","7":"Lowe","releases":[{"0":"2890","vim_version":"7.0","1":"7.0","script_version":"1.1.1","2":"1.1.1","version_comment":"Removed stubbed story content to be more flexible and prepare for new tracker features.","3":"Removed stubbed story content to be more flexible and prepare for new tracker features.","package":"vim-slurper.tgz","4":"vim-slurper.tgz","src_id":"17386","5":"17386","creation_date":"1328373451","6":"1328373451"},{"0":"2890","vim_version":"7.0","1":"7.0","script_version":"1.0.0","2":"1.0.0","version_comment":"Add auto indenting, updated macros to work anywhere in a story, and story folding.","3":"Add auto indenting, updated macros to work anywhere in a story, and story folding.","package":"vim-slurper.tar.gz","4":"vim-slurper.tar.gz","src_id":"13772","5":"13772","creation_date":"1283881595","6":"1283881595"},{"0":"2890","vim_version":"7.0","1":"7.0","script_version":"0.3.1","2":"0.3.1","version_comment":"Force 2 spaces for tab in .slurper files","3":"Force 2 spaces for tab in .slurper files","package":"vim-slurper.tar.gz","4":"vim-slurper.tar.gz","src_id":"12569","5":"12569","creation_date":"1267892686","6":"1267892686"},{"0":"2890","vim_version":"7.0","1":"7.0","script_version":"0.3.0","2":"0.3.0","version_comment":"Support chores, features, releases and bugs. Updated story format to match version 0.3.0 of the slurper gem.","3":"Support chores, features, releases and bugs. Updated story format to match version 0.3.0 of the slurper gem.","package":"vim-slurper.tar.gz","4":"vim-slurper.tar.gz","src_id":"12313","5":"12313","creation_date":"1265395970","6":"1265395970"},{"0":"2890","vim_version":"7.0","1":"7.0","script_version":"0.2.1","2":"0.2.1","version_comment":"Correct indenting issue for labels.","3":"Correct indenting issue for labels.","package":"vim-slurper.tar.gz","4":"vim-slurper.tar.gz","src_id":"12120","5":"12120","creation_date":"1263766121","6":"1263766121"},{"0":"2890","vim_version":"7.0","1":"7.0","script_version":"0.2.0","2":"0.2.0","version_comment":"Added syntax highlighting and updated key maps to be less obtrusive.","3":"Added syntax highlighting and updated key maps to be less obtrusive.","package":"vim-slurper.tar.gz","4":"vim-slurper.tar.gz","src_id":"11959","5":"11959","creation_date":"1261868563","6":"1261868563"},{"0":"2890","vim_version":"7.0","1":"7.0","script_version":"0.1.0","2":"0.1.0","version_comment":"Initial upload","3":"Initial upload","package":"slurper.tar.gz","4":"slurper.tar.gz","src_id":"11917","5":"11917","creation_date":"1261113980","6":"1261113980"}]},"2889":{"script_id":"2889","0":"2889","script_name":"bluechia.vim","1":"bluechia.vim","script_type":"color scheme","2":"color scheme","summary":"A dark color scheme for GUI","3":"A dark color scheme for GUI","description":"A dark color scheme for GUI. ","4":"A dark color scheme for GUI. ","install_details":"Copy the file to ~\/.vim\/colors or (<your-vim-dir>\\runtime\\colors on Windows) and do \r\n:colorscheme bluechia","5":"Copy the file to ~\/.vim\/colors or (<your-vim-dir>\\runtime\\colors on Windows) and do \r\n:colorscheme bluechia","first_name":"Crux","6":"Crux","last_name":"One","7":"One","releases":[{"0":"2889","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"bluechia.vim","4":"bluechia.vim","src_id":"11910","5":"11910","creation_date":"1260964443","6":"1260964443"}]},"2888":{"script_id":"2888","0":"2888","script_name":"CodeOverview","1":"CodeOverview","script_type":"utility","2":"utility","summary":"Display a graphical overview of code alongside a gvim window.","3":"Display a graphical overview of code alongside a gvim window.","description":"Demonstration video : http:\/\/www.youtube.com\/watch?v=vQqeAk__vvE\r\n\r\nGitHub for the script : https:\/\/github.com\/Twinside\/vim-codeoverview\r\n\r\nTo use this plugin, you must :\r\n- Be running on Windows with .net Framework >= 3.0\r\n- use gVim version >= 7.2 (possibly with some patches)\r\nthen launch gvim and type the following commands to start the plugin :\r\n:ShowCodeOverview\r\n:CodeOverviewAuto \r\n:SnapshotFile\r\n\r\nBy default the automatic overview generation is deactivated to avoid\r\nhurting performances. If you always want CodeOverview, put the first two\r\ncommands in your .vimrc. The last command is just to force refresh for\r\nyour current file.\r\n\r\nUsage :\r\n======\r\n:ShowCodeOverview \r\n    Start the overview panel.\r\n\r\n:HideCodeOverview \r\n    Hide the overview panel\r\n    Also stop automatic overview generation.\r\n\r\n:CodeOverviewNoAuto \r\n    Disable automatic overview generation.\r\n\r\n:CodeOverviewAuto \r\n    Setup automatic overview generation.\r\n\r\n:SnapshotFile \r\n    Refresh your current overview.\r\n\r\nAs some requested, Here's the code source of binary parts, it's a little messy, sorry :\r\nhttp:\/\/github.com\/Twinside\/CodeOverview\r\n\r\nKnown problems :\r\n==============\r\n- View doesn't really track vim scrolling\r\nIt's the current trade-off between performance and functionality.","4":"Demonstration video : http:\/\/www.youtube.com\/watch?v=vQqeAk__vvE\r\n\r\nGitHub for the script : https:\/\/github.com\/Twinside\/vim-codeoverview\r\n\r\nTo use this plugin, you must :\r\n- Be running on Windows with .net Framework >= 3.0\r\n- use gVim version >= 7.2 (possibly with some patches)\r\nthen launch gvim and type the following commands to start the plugin :\r\n:ShowCodeOverview\r\n:CodeOverviewAuto \r\n:SnapshotFile\r\n\r\nBy default the automatic overview generation is deactivated to avoid\r\nhurting performances. If you always want CodeOverview, put the first two\r\ncommands in your .vimrc. The last command is just to force refresh for\r\nyour current file.\r\n\r\nUsage :\r\n======\r\n:ShowCodeOverview \r\n    Start the overview panel.\r\n\r\n:HideCodeOverview \r\n    Hide the overview panel\r\n    Also stop automatic overview generation.\r\n\r\n:CodeOverviewNoAuto \r\n    Disable automatic overview generation.\r\n\r\n:CodeOverviewAuto \r\n    Setup automatic overview generation.\r\n\r\n:SnapshotFile \r\n    Refresh your current overview.\r\n\r\nAs some requested, Here's the code source of binary parts, it's a little messy, sorry :\r\nhttp:\/\/github.com\/Twinside\/CodeOverview\r\n\r\nKnown problems :\r\n==============\r\n- View doesn't really track vim scrolling\r\nIt's the current trade-off between performance and functionality.","install_details":"uncompress the archive and put in your ~\/vimfiles\/plugin folder. or put it in ~\/.vim\/bundle\/vim-codeoverview","5":"uncompress the archive and put in your ~\/vimfiles\/plugin folder. or put it in ~\/.vim\/bundle\/vim-codeoverview","first_name":"Vincent","6":"Vincent","last_name":"B","7":"B","releases":[{"0":"2888","vim_version":"7.2","1":"7.2","script_version":"1.8","2":"1.8","version_comment":"Added variable to control auto-start of script.","3":"Added variable to control auto-start of script.","package":"CodeOverview.zip","4":"CodeOverview.zip","src_id":"13947","5":"13947","creation_date":"1285661299","6":"1285661299"}]},"2887":{"script_id":"2887","0":"2887","script_name":"manuscript","1":"manuscript","script_type":"color scheme","2":"color scheme","summary":"Dark colorscheme","3":"Dark colorscheme","description":"GUI only dark colorscheme. No bolds and italics.\r\n\r\nScreenshots: http:\/\/habamax.ru\/myvim\/index.html#manuscript","4":"GUI only dark colorscheme. No bolds and italics.\r\n\r\nScreenshots: http:\/\/habamax.ru\/myvim\/index.html#manuscript","install_details":"","5":"","first_name":"Maxim","6":"Maxim","last_name":"Kim","7":"Kim","releases":[{"0":"2887","vim_version":"7.0","1":"7.0","script_version":"2010-03","2":"2010-03","version_comment":"Adjust some colors.","3":"Adjust some colors.","package":"manuscript.vim","4":"manuscript.vim","src_id":"12590","5":"12590","creation_date":"1268242444","6":"1268242444"},{"0":"2887","vim_version":"7.0","1":"7.0","script_version":"2010-02","2":"2010-02","version_comment":"Refine some colors.","3":"Refine some colors.","package":"manuscript.vim","4":"manuscript.vim","src_id":"12445","5":"12445","creation_date":"1266655725","6":"1266655725"},{"0":"2887","vim_version":"7.0","1":"7.0","script_version":"2009-12","2":"2009-12","version_comment":"Initial upload","3":"Initial upload","package":"manuscript.vim","4":"manuscript.vim","src_id":"11893","5":"11893","creation_date":"1260617099","6":"1260617099"}]},"2886":{"script_id":"2886","0":"2886","script_name":"cgc.vim","1":"cgc.vim","script_type":"utility","2":"utility","summary":"A compiler description for nVidia cg compiler","3":"A compiler description for nVidia cg compiler","description":"An error format parsing for cg programs","4":"An error format parsing for cg programs","install_details":"drop it in ~\/.vim\/compiler or ~\\vimfiles\\compiler","5":"drop it in ~\/.vim\/compiler or ~\\vimfiles\\compiler","first_name":"Vincent","6":"Vincent","last_name":"B","7":"B","releases":[{"0":"2886","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"cgc.vim","4":"cgc.vim","src_id":"11884","5":"11884","creation_date":"1260288722","6":"1260288722"}]},"2885":{"script_id":"2885","0":"2885","script_name":"gsession.vim","1":"gsession.vim","script_type":"utility","2":"utility","summary":"global session manager (improved)","3":"global session manager (improved)","description":"gsession.vim provides global namespace and current path namespace for you to save session. so if you save session with the same name in different space, it won't conflict.\r\n\r\ngsession.vim also provides anonymous sessions , so you don't need to think about session name , gsession.vim saves time for you.\r\n\r\ngsession.vim saves your session files into the same directory (~\/.vim\/session\/) by default. and auto-detect your session file to load session file when you are opening vim editor without arguments. you can also define your session dir by g:session_dir option.\r\n\r\ngsession.vim also save your session file when you are leaving vim editor.\r\n\r\ngsession.vim also support making a local session file <leader>sS, which is just like :mksession! command. but you can define your favorite session filename.","4":"gsession.vim provides global namespace and current path namespace for you to save session. so if you save session with the same name in different space, it won't conflict.\r\n\r\ngsession.vim also provides anonymous sessions , so you don't need to think about session name , gsession.vim saves time for you.\r\n\r\ngsession.vim saves your session files into the same directory (~\/.vim\/session\/) by default. and auto-detect your session file to load session file when you are opening vim editor without arguments. you can also define your session dir by g:session_dir option.\r\n\r\ngsession.vim also save your session file when you are leaving vim editor.\r\n\r\ngsession.vim also support making a local session file <leader>sS, which is just like :mksession! command. but you can define your favorite session filename.","install_details":"see http:\/\/github.com\/c9s\/gsession.vim for more details.","5":"see http:\/\/github.com\/c9s\/gsession.vim for more details.","first_name":"Yo-An","6":"Yo-An","last_name":"Lin","7":"Lin","releases":[{"0":"2885","vim_version":"7.2","1":"7.2","script_version":"0.23","2":"0.23","version_comment":"different namespace support for git branch\n(This package is released by VIM::Packager http:\/\/github.com\/c9s\/vim-packager)\n","3":"different namespace support for git branch\n(This package is released by VIM::Packager http:\/\/github.com\/c9s\/vim-packager)\n","package":"gsession-vim-0.23.tar.gz","4":"gsession-vim-0.23.tar.gz","src_id":"12482","5":"12482","creation_date":"1266997046","6":"1266997046"},{"0":"2885","vim_version":"7.2","1":"7.2","script_version":"0.22","2":"0.22","version_comment":"windows path support\n(This package is released by VIM::Packager http:\/\/github.com\/c9s\/vim-packager)\n","3":"windows path support\n(This package is released by VIM::Packager http:\/\/github.com\/c9s\/vim-packager)\n","package":"gsession-vim-0.22.tar.gz","4":"gsession-vim-0.22.tar.gz","src_id":"12479","5":"12479","creation_date":"1266974424","6":"1266974424"},{"0":"2885","vim_version":"7.2","1":"7.2","script_version":"0.21","2":"0.21","version_comment":"remove sesdir property from option.\n(This package is released by VIM::Packager http:\/\/github.com\/c9s\/vim-packager)\n","3":"remove sesdir property from option.\n(This package is released by VIM::Packager http:\/\/github.com\/c9s\/vim-packager)\n","package":"gsession-vim-0.21.tar.gz","4":"gsession-vim-0.21.tar.gz","src_id":"11888","5":"11888","creation_date":"1260399332","6":"1260399332"},{"0":"2885","vim_version":"6.0","1":"6.0","script_version":"0.2","2":"0.2","version_comment":"Initial upload","3":"Initial upload","package":"gsession-vim-0.2.tar.gz","4":"gsession-vim-0.2.tar.gz","src_id":"11883","5":"11883","creation_date":"1260284624","6":"1260284624"}]},"2884":{"script_id":"2884","0":"2884","script_name":"JavaAspect","1":"JavaAspect","script_type":"utility","2":"utility","summary":"A script that generates aspect template for Java.","3":"A script that generates aspect template for Java.","description":"Most of the popular aspect programming models in java, either introduce new language keywords or heavily use reflection and xml to achieve the goal.  This script takes a different approach, it generates the aspect boilerplate at the source code level without the extra effort to learn new programming framework.  The generated code can be used as a decorator to wrap around the real object, thusly working as an aspect.  Besides basic OO concepts, It has no fancy names to pollute your brain, it just lets you concentrate on your real work.  ","4":"Most of the popular aspect programming models in java, either introduce new language keywords or heavily use reflection and xml to achieve the goal.  This script takes a different approach, it generates the aspect boilerplate at the source code level without the extra effort to learn new programming framework.  The generated code can be used as a decorator to wrap around the real object, thusly working as an aspect.  Besides basic OO concepts, It has no fancy names to pollute your brain, it just lets you concentrate on your real work.  ","install_details":"For how to use this script please refer to the comments in JavaAspect.vim and readme.","5":"For how to use this script please refer to the comments in JavaAspect.vim and readme.","first_name":"Yiu","6":"Yiu","last_name":"Wing","7":"Wing","releases":[{"0":"2884","vim_version":"7.0","1":"7.0","script_version":"1","2":"1","version_comment":"Initial upload","3":"Initial upload","package":"aspect.tar.gz","4":"aspect.tar.gz","src_id":"11879","5":"11879","creation_date":"1260147989","6":"1260147989"}]},"2883":{"script_id":"2883","0":"2883","script_name":"growlnotify.vim","1":"growlnotify.vim","script_type":"utility","2":"utility","summary":"growlnotify wrapper for vim script.","3":"growlnotify wrapper for vim script.","description":"see: http:\/\/github.com\/c9s\/growlnotify.vim","4":"see: http:\/\/github.com\/c9s\/growlnotify.vim","install_details":"see: http:\/\/github.com\/c9s\/growlnotify.vim","5":"see: http:\/\/github.com\/c9s\/growlnotify.vim","first_name":"Yo-An","6":"Yo-An","last_name":"Lin","7":"Lin","releases":[{"0":"2883","vim_version":"7.2","1":"7.2","script_version":"0.11","2":"0.11","version_comment":"released with growlnotify binary\n(This package is released by VIM::Packager http:\/\/github.com\/c9s\/vim-packager)\n","3":"released with growlnotify binary\n(This package is released by VIM::Packager http:\/\/github.com\/c9s\/vim-packager)\n","package":"growlnotify-vim-0.11.tar.gz","4":"growlnotify-vim-0.11.tar.gz","src_id":"11876","5":"11876","creation_date":"1260044212","6":"1260044212"},{"0":"2883","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"growlnotify-vim-0.1.tar.gz","4":"growlnotify-vim-0.1.tar.gz","src_id":"11868","5":"11868","creation_date":"1260022023","6":"1260022023"}]},"2882":{"script_id":"2882","0":"2882","script_name":"Markdown","1":"Markdown","script_type":"syntax","2":"syntax","summary":"Syntax highlight for Markdown text files","3":"Syntax highlight for Markdown text files","description":"See the script http:\/\/www.vim.org\/scripts\/script.php?script_id=1242.\r\n\r\nThis is a new version and distribution of the Markdown syntax highlight. Visit http:\/\/github.com\/hallison\/vim-markdown for more information about this plugin\/syntax.\r\n","4":"See the script http:\/\/www.vim.org\/scripts\/script.php?script_id=1242.\r\n\r\nThis is a new version and distribution of the Markdown syntax highlight. Visit http:\/\/github.com\/hallison\/vim-markdown for more information about this plugin\/syntax.\r\n","install_details":"Easy! Just open gzipball file with Vim (of course!) and use command :source %. All files will be extracted in your Vim home directory.\r\n\r\n$ vim markdown-<version>.vba.gz +\":source % | quit!\"\r\n\r\nPlease, visit https:\/\/github.com\/hallison\/vim-markdown\/tree\/changes for more information.\r\n","5":"Easy! Just open gzipball file with Vim (of course!) and use command :source %. All files will be extracted in your Vim home directory.\r\n\r\n$ vim markdown-<version>.vba.gz +\":source % | quit!\"\r\n\r\nPlease, visit https:\/\/github.com\/hallison\/vim-markdown\/tree\/changes for more information.\r\n","first_name":"Hallison","6":"Hallison","last_name":"Batista","7":"Batista","releases":[{"0":"2882","vim_version":"7.0","1":"7.0","script_version":"1.2.2","2":"1.2.2","version_comment":"* Fixes.\r\n  * Multi-paragraph list items.\r\n  * Code block in list.","3":"* Fixes.\r\n  * Multi-paragraph list items.\r\n  * Code block in list.","package":"markdown-1.2.2.vba.gz","4":"markdown-1.2.2.vba.gz","src_id":"15150","5":"15150","creation_date":"1299114358","6":"1299114358"},{"0":"2882","vim_version":"7.0","1":"7.0","script_version":"1.2.1","2":"1.2.1","version_comment":"* Fixes.\r\n  * The backtick trigger has been fixed.\r\n\r\n* Improvements.\r\n  * Adding of task for creating a package for tests.\r\n","3":"* Fixes.\r\n  * The backtick trigger has been fixed.\r\n\r\n* Improvements.\r\n  * Adding of task for creating a package for tests.\r\n","package":"markdown-1.2.1.vba.gz","4":"markdown-1.2.1.vba.gz","src_id":"14608","5":"14608","creation_date":"1293139106","6":"1293139106"},{"0":"2882","vim_version":"7.0","1":"7.0","script_version":"1.2.0","2":"1.2.0","version_comment":"* Fixes.\r\n  * The italics has been fixed. Thanks to Ian Smith-Heisters.\r\n  * Fix in gzip package extension.\r\n\r\n* Improvements.\r\n  * Support multi-line captioned images and links. This feature is supported\r\n    by Pandoc and others parsers. Thanks to Bryan Silverthorn.\r\n  * You can install Markdown using vim-addon-manager. More details see\r\n    <http:\/\/github.com\/MarcWeber\/vim-addon-manager>.\r\n","3":"* Fixes.\r\n  * The italics has been fixed. Thanks to Ian Smith-Heisters.\r\n  * Fix in gzip package extension.\r\n\r\n* Improvements.\r\n  * Support multi-line captioned images and links. This feature is supported\r\n    by Pandoc and others parsers. Thanks to Bryan Silverthorn.\r\n  * You can install Markdown using vim-addon-manager. More details see\r\n    <http:\/\/github.com\/MarcWeber\/vim-addon-manager>.\r\n","package":"markdown-1.2.0.vba.gz","4":"markdown-1.2.0.vba.gz","src_id":"14427","5":"14427","creation_date":"1291416493","6":"1291416493"},{"0":"2882","vim_version":"6.0","1":"6.0","script_version":"1.1.0","2":"1.1.0","version_comment":"* Enhancements\r\n  * Added build using Bakefile (Bash-Toolbox)\r\n  * Manifest file for VBA package.\r\n* Fixes\r\n  * Fixes in the file detection.\r\n  * Fixes in link snippets","3":"* Enhancements\r\n  * Added build using Bakefile (Bash-Toolbox)\r\n  * Manifest file for VBA package.\r\n* Fixes\r\n  * Fixes in the file detection.\r\n  * Fixes in link snippets","package":"markdown-1.1.0.vba.gz","4":"markdown-1.1.0.vba.gz","src_id":"12224","5":"12224","creation_date":"1264778486","6":"1264778486"},{"0":"2882","vim_version":"6.0","1":"6.0","script_version":"1.0.3","2":"1.0.3","version_comment":"* Added auto-detection for file type.\r\n* Updates in documentation.\r\n* Updates in package list.\r\n","3":"* Added auto-detection for file type.\r\n* Updates in documentation.\r\n* Updates in package list.\r\n","package":"markdown-1.0.3.vba.gz","4":"markdown-1.0.3.vba.gz","src_id":"12012","5":"12012","creation_date":"1262633941","6":"1262633941"},{"0":"2882","vim_version":"6.0","1":"6.0","script_version":"1.0.2","2":"1.0.2","version_comment":"* Updates in documentation.\r\n* Renamed build file.\r\n","3":"* Updates in documentation.\r\n* Renamed build file.\r\n","package":"markdown-1.0.2.vba.gz","4":"markdown-1.0.2.vba.gz","src_id":"11939","5":"11939","creation_date":"1261515775","6":"1261515775"},{"0":"2882","vim_version":"6.0","1":"6.0","script_version":"1.0.1","2":"1.0.1","version_comment":"*  Fix in task pool file.\r\n*  Change file name of the package content.\r\n*  New tasks in pool.\r\n*  Small improvements in syntax and doc updates.\r\n","3":"*  Fix in task pool file.\r\n*  Change file name of the package content.\r\n*  New tasks in pool.\r\n*  Small improvements in syntax and doc updates.\r\n","package":"markdown-1.0.1.vba.gz","4":"markdown-1.0.1.vba.gz","src_id":"11864","5":"11864","creation_date":"1259950527","6":"1259950527"},{"0":"2882","vim_version":"6.0","1":"6.0","script_version":"1.0.0","2":"1.0.0","version_comment":"Initial upload","3":"Initial upload","package":"markdown-1.0.0.vba.gz","4":"markdown-1.0.0.vba.gz","src_id":"11858","5":"11858","creation_date":"1259914650","6":"1259914650"}]},"2881":{"script_id":"2881","0":"2881","script_name":"mib_translator","1":"mib_translator","script_type":"utility","2":"utility","summary":"Translate SNMP OIDs from within Vim","3":"Translate SNMP OIDs from within Vim","description":"mib_translator.vim\r\nTranslates SNMP OIDs within Vim using Net-SNMP's snmptranslate command.\r\nIt can display the OID of a label, or a label of an OID whether it is a comment, or a string literal in your code.\r\n\r\nFor screenshots and documentation, please see the homepage.\r\n\r\nHome page: https:\/\/github.com\/caglartoklu\/mib_translator.vim\r\n\r\nThe development is completely moved to Github.\r\nFor documentation and screenshot, please visit the homepage link.\r\nFunctionality changes will still be reflected to Vim.org page.","4":"mib_translator.vim\r\nTranslates SNMP OIDs within Vim using Net-SNMP's snmptranslate command.\r\nIt can display the OID of a label, or a label of an OID whether it is a comment, or a string literal in your code.\r\n\r\nFor screenshots and documentation, please see the homepage.\r\n\r\nHome page: https:\/\/github.com\/caglartoklu\/mib_translator.vim\r\n\r\nThe development is completely moved to Github.\r\nFor documentation and screenshot, please visit the homepage link.\r\nFunctionality changes will still be reflected to Vim.org page.","install_details":"For Vundle users:\r\n    Bundle 'caglartoklu\/mib_translator.vim'\r\n\r\nFor Pathogen users:\r\n    cd ~\/.vim\/bundle\r\n    git clone git:\/\/github.com\/caglartoklu\/mib_translator.vim\r\n\r\nFor all other users, simply drop the mib_translator.vim file to your plugin directory.","5":"For Vundle users:\r\n    Bundle 'caglartoklu\/mib_translator.vim'\r\n\r\nFor Pathogen users:\r\n    cd ~\/.vim\/bundle\r\n    git clone git:\/\/github.com\/caglartoklu\/mib_translator.vim\r\n\r\nFor all other users, simply drop the mib_translator.vim file to your plugin directory.","first_name":"Caglar","6":"Caglar","last_name":"Toklu","7":"Toklu","releases":[{"0":"2881","vim_version":"7.0","1":"7.0","script_version":"0.0.6","2":"0.0.6","version_comment":"- Added: `OidTranslateInfer` command, to infer if the word under cursor\r\n  is whether an OID number or an OID label, and call the appropriate\r\n  function.\r\n- Added: option `g:OidTranslatorNetSnmpLogging` to enable\/disable\r\n  Net-SNMP logs.\r\n- Added option `g:OidTranslatorExposingCommand`, when used, it will print\r\n  the Net-SNMP command to get the information on top of the created\r\n  translator buffer.\r\n- Added option `g:OidTranslatorInferMapping` which will be used\r\n  to map the `:OidTranslateInfer` command.\r\n- Added: Command `:OidTranslateNumberList` to display the list\r\n  of OIDs defined in Net-SNMP in another buffer.\r\n- Added: If the OID is starts with `1.1`, the leading `1` is automatically\r\n  removed.\r\n- Added: If there are no arguments for `OidTranslateFromLabel` command,\r\n  current word will be used as the argument.\r\n- Added: If there are no arguments for `OidTranslateFromOid` command,\r\n  the OID under cursor will be used.\r\n- Added: If the parameters to launch the command are empty\/faulty,\r\n  a warning will be displayed and the command will not be run.\r\n- Added: Displaying line numbers in the opened buffer, especially\r\n  useful for listing OID number.\r\n- Fixed : The plugin could cause other new buffers to be non-modifiable,\r\n  now all the options are applied using setlocal, without side effects.","3":"- Added: `OidTranslateInfer` command, to infer if the word under cursor\r\n  is whether an OID number or an OID label, and call the appropriate\r\n  function.\r\n- Added: option `g:OidTranslatorNetSnmpLogging` to enable\/disable\r\n  Net-SNMP logs.\r\n- Added option `g:OidTranslatorExposingCommand`, when used, it will print\r\n  the Net-SNMP command to get the information on top of the created\r\n  translator buffer.\r\n- Added option `g:OidTranslatorInferMapping` which will be used\r\n  to map the `:OidTranslateInfer` command.\r\n- Added: Command `:OidTranslateNumberList` to display the list\r\n  of OIDs defined in Net-SNMP in another buffer.\r\n- Added: If the OID is starts with `1.1`, the leading `1` is automatically\r\n  removed.\r\n- Added: If there are no arguments for `OidTranslateFromLabel` command,\r\n  current word will be used as the argument.\r\n- Added: If there are no arguments for `OidTranslateFromOid` command,\r\n  the OID under cursor will be used.\r\n- Added: If the parameters to launch the command are empty\/faulty,\r\n  a warning will be displayed and the command will not be run.\r\n- Added: Displaying line numbers in the opened buffer, especially\r\n  useful for listing OID number.\r\n- Fixed : The plugin could cause other new buffers to be non-modifiable,\r\n  now all the options are applied using setlocal, without side effects.","package":"mib_translator.vim","4":"mib_translator.vim","src_id":"21004","5":"21004","creation_date":"1383599396","6":"1383599396"},{"0":"2881","vim_version":"6.0","1":"6.0","script_version":"0.0.4","2":"0.0.4","version_comment":"- Fixed: If the opened buffer is deleted by hand, that raised an error when the buffer is opened again.\r\n","3":"- Fixed: If the opened buffer is deleted by hand, that raised an error when the buffer is opened again.\r\n","package":"mib_translator.vim","4":"mib_translator.vim","src_id":"12844","5":"12844","creation_date":"1271420786","6":"1271420786"},{"0":"2881","vim_version":"6.0","1":"6.0","script_version":"0.0.3","2":"0.0.3","version_comment":"- Fixed: Opened buffer remained unmodifiable for the second run.\r\n","3":"- Fixed: Opened buffer remained unmodifiable for the second run.\r\n","package":"mib_translator.vim","4":"mib_translator.vim","src_id":"12843","5":"12843","creation_date":"1271418899","6":"1271418899"},{"0":"2881","vim_version":"6.0","1":"6.0","script_version":"0.0.2","2":"0.0.2","version_comment":"- The opened buffer is colored with MIB file syntax, making it more readable.\r\n- The opened buffer is not modifiable from now on.\r\n- Made it more compatible with other plugins, the functions starts with 's:'.","3":"- The opened buffer is colored with MIB file syntax, making it more readable.\r\n- The opened buffer is not modifiable from now on.\r\n- Made it more compatible with other plugins, the functions starts with 's:'.","package":"mib_translator.vim","4":"mib_translator.vim","src_id":"12842","5":"12842","creation_date":"1271417720","6":"1271417720"},{"0":"2881","vim_version":"6.0","1":"6.0","script_version":"0.0.1","2":"0.0.1","version_comment":"Initial upload","3":"Initial upload","package":"mib_translator.vim","4":"mib_translator.vim","src_id":"11851","5":"11851","creation_date":"1259851234","6":"1259851234"}]},"2880":{"script_id":"2880","0":"2880","script_name":"rcshell.vim","1":"rcshell.vim","script_type":"syntax","2":"syntax","summary":"syntax highlight file for the rc shell scripting language","3":"syntax highlight file for the rc shell scripting language","description":"This is a syntax file for the rc shell scripting language.  \r\n\r\n## Compatibility\r\n\r\nFor unix (not plan9) users, there are two slightly different rc available.\r\nOne is [plan9port][plan9port] and [9base][9base]'s version\r\nand the other is Byron Rakitzis'\r\n(as packaged by Debian and other *nix software distribution).\r\n\r\nThis syntax file is compatible with both versions.\r\n\r\n[plan9port]: https:\/\/github.com\/9fans\/plan9port\r\n[9base]: http:\/\/tools.suckless.org\/9base\r\n\r\n\r\n## Repository\r\n\r\n- **Repository:** http:\/\/github.com\/weakish\/rcshell.vim\r\n- **Issue tracker:** https:\/\/github.com\/weakish\/rcshell.vim\/issues\r\n\r\n## Credit\r\n\r\nThis is based on [Andy Spencer][andy]'s work for the plan9 rc shell.\r\nThere is a minor trade off for maintain compatibility with two versions of rc mentioned above:\r\nless powerful `(ba)sh like substitution` syntax error detection.\r\n\r\n[andy]: https:\/\/github.com\/Andy753421 \r\n\r\n## Tips \r\n\r\nThis is not related to syntax directly, but I think users who codes rc shell script in Vim may have interests.\r\n\r\nIf you want to use `rc` as the embedded shell in vim,\r\nadd the following lines to your .vimrc:\r\n\r\n```vim\r\nset shell=\/usr\/bin\/rc\\ -l\r\n\"  or \/bin\/rc or \/usr\/local\/bin\/rc or \/opt\/local \/bin\/rc, etc\r\nset shellcmdflag=-c\r\nset shellpipe=>[2=1]\\|\\ tee\r\nset shellredir=>%s\\ >[2=1]\r\n```\r\n","4":"This is a syntax file for the rc shell scripting language.  \r\n\r\n## Compatibility\r\n\r\nFor unix (not plan9) users, there are two slightly different rc available.\r\nOne is [plan9port][plan9port] and [9base][9base]'s version\r\nand the other is Byron Rakitzis'\r\n(as packaged by Debian and other *nix software distribution).\r\n\r\nThis syntax file is compatible with both versions.\r\n\r\n[plan9port]: https:\/\/github.com\/9fans\/plan9port\r\n[9base]: http:\/\/tools.suckless.org\/9base\r\n\r\n\r\n## Repository\r\n\r\n- **Repository:** http:\/\/github.com\/weakish\/rcshell.vim\r\n- **Issue tracker:** https:\/\/github.com\/weakish\/rcshell.vim\/issues\r\n\r\n## Credit\r\n\r\nThis is based on [Andy Spencer][andy]'s work for the plan9 rc shell.\r\nThere is a minor trade off for maintain compatibility with two versions of rc mentioned above:\r\nless powerful `(ba)sh like substitution` syntax error detection.\r\n\r\n[andy]: https:\/\/github.com\/Andy753421 \r\n\r\n## Tips \r\n\r\nThis is not related to syntax directly, but I think users who codes rc shell script in Vim may have interests.\r\n\r\nIf you want to use `rc` as the embedded shell in vim,\r\nadd the following lines to your .vimrc:\r\n\r\n```vim\r\nset shell=\/usr\/bin\/rc\\ -l\r\n\"  or \/bin\/rc or \/usr\/local\/bin\/rc or \/opt\/local \/bin\/rc, etc\r\nset shellcmdflag=-c\r\nset shellpipe=>[2=1]\\|\\ tee\r\nset shellredir=>%s\\ >[2=1]\r\n```\r\n","install_details":"Download the tarball here and do this:\r\n\r\n```sh\r\ncd ~\/.vim\r\ntar --strip=1 -zxf path\/to\/master.tar.gz","5":"Download the tarball here and do this:\r\n\r\n```sh\r\ncd ~\/.vim\r\ntar --strip=1 -zxf path\/to\/master.tar.gz","first_name":"Jakukyo","6":"Jakukyo","last_name":"Friel","7":"Friel","releases":[{"0":"2880","vim_version":"7.0","1":"7.0","script_version":"0.2.0","2":"0.2.0","version_comment":"- Detect rc shell via shebang.\r\n- Provide a way to disable this syntax file.","3":"- Detect rc shell via shebang.\r\n- Provide a way to disable this syntax file.","package":"rcshell.vim-0.2.0.tar.gz","4":"rcshell.vim-0.2.0.tar.gz","src_id":"22742","5":"22742","creation_date":"1419773187","6":"1419773187"},{"0":"2880","vim_version":"5.7","1":"5.7","script_version":"0.1.1","2":"0.1.1","version_comment":"Rename rc.vim to rcshell.vim. Fix a bug that rcshell.vim detect will be overridden by M$ resource type.","3":"Rename rc.vim to rcshell.vim. Fix a bug that rcshell.vim detect will be overridden by M$ resource type.","package":"0.1.1.tar.gz","4":"0.1.1.tar.gz","src_id":"22707","5":"22707","creation_date":"1418833102","6":"1418833102"},{"0":"2880","vim_version":"7.0","1":"7.0","script_version":"20091226","2":"20091226","version_comment":"Adjust rcHereDoc pattern to get <<EOF >output highlighted correctly.","3":"Adjust rcHereDoc pattern to get <<EOF >output highlighted correctly.","package":"rc.vim","4":"rc.vim","src_id":"11957","5":"11957","creation_date":"1261843067","6":"1261843067"},{"0":"2880","vim_version":"5.7","1":"5.7","script_version":"20091204","2":"20091204","version_comment":"I suggest all users to replace the old version. The old version is my poorly-reinvented wheel.  This new version is based on Andy Spencer's work.  Andy Spencer's syntax file is for p9p's rc and I made some minor changes to make it compatible with Byron Rakitzis' reimplementation too.","3":"I suggest all users to replace the old version. The old version is my poorly-reinvented wheel.  This new version is based on Andy Spencer's work.  Andy Spencer's syntax file is for p9p's rc and I made some minor changes to make it compatible with Byron Rakitzis' reimplementation too.","package":"rc.vim","4":"rc.vim","src_id":"11861","5":"11861","creation_date":"1259941098","6":"1259941098"}]},"2879":{"script_id":"2879","0":"2879","script_name":"XPstatusline","1":"XPstatusline","script_type":"utility","2":"utility","summary":"statusline with many infomation","3":"statusline with many infomation","description":"statusline config of grey2 colortheme : http:\/\/www.vim.org\/scripts\/script.php?script_id=2859;\r\n\r\n\r\nPreview : http:\/\/photo.blog.sina.com.cn\/photo\/5bc27867t78c51c25aefd;","4":"statusline config of grey2 colortheme : http:\/\/www.vim.org\/scripts\/script.php?script_id=2859;\r\n\r\n\r\nPreview : http:\/\/photo.blog.sina.com.cn\/photo\/5bc27867t78c51c25aefd;","install_details":"copy it into ~\/.vim\/plugin or ~\/_vimfiles\/plugin","5":"copy it into ~\/.vim\/plugin or ~\/_vimfiles\/plugin","first_name":"drdr","6":"drdr","last_name":"xp","7":"xp","releases":[{"0":"2879","vim_version":"7.2","1":"7.2","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"statusline.vim","4":"statusline.vim","src_id":"11846","5":"11846","creation_date":"1259821049","6":"1259821049"}]},"2878":{"script_id":"2878","0":"2878","script_name":"RDoc","1":"RDoc","script_type":"syntax","2":"syntax","summary":"Syntax highlight for Ruby Documentation","3":"Syntax highlight for Ruby Documentation","description":"Visit http:\/\/github.com\/hallison\/vim-rdoc for more information about this plugin\/syntax.","4":"Visit http:\/\/github.com\/hallison\/vim-rdoc for more information about this plugin\/syntax.","install_details":"Easy! Just open gzipball file with Vim (of course!) and use command :source %. All files will be extracted in your Vim home directory.\r\nPlease, visit http:\/\/github.com\/hallison\/vim-rdoc for more information.","5":"Easy! Just open gzipball file with Vim (of course!) and use command :source %. All files will be extracted in your Vim home directory.\r\nPlease, visit http:\/\/github.com\/hallison\/vim-rdoc for more information.","first_name":"Hallison","6":"Hallison","last_name":"Batista","7":"Batista","releases":[{"0":"2878","vim_version":"6.0","1":"6.0","script_version":"1.1.3","2":"1.1.3","version_comment":"* Inline links (Thanks to Toby Matejovsky).\r\n* Fix in task that builds package.","3":"* Inline links (Thanks to Toby Matejovsky).\r\n* Fix in task that builds package.","package":"rdoc-1.1.3.vba.gz","4":"rdoc-1.1.3.vba.gz","src_id":"13882","5":"13882","creation_date":"1285128823","6":"1285128823"},{"0":"2878","vim_version":"6.0","1":"6.0","script_version":"1.1.2","2":"1.1.2","version_comment":"* Removed unnecessary files and small updates.\r\n* Added Bakefile for build using `bake`.\r\n* Updated package file list and documentation.","3":"* Removed unnecessary files and small updates.\r\n* Added Bakefile for build using `bake`.\r\n* Updated package file list and documentation.","package":"rdoc-1.1.2.vba.gz","4":"rdoc-1.1.2.vba.gz","src_id":"12236","5":"12236","creation_date":"1264798642","6":"1264798642"},{"0":"2878","vim_version":"6.0","1":"6.0","script_version":"1.1.1","2":"1.1.1","version_comment":"* Added auto-detection file type.\r\n* Updates in package file list.\r\n* Updates in documentation.\r\n","3":"* Added auto-detection file type.\r\n* Updates in package file list.\r\n* Updates in documentation.\r\n","package":"rdoc-1.1.1.vba.gz","4":"rdoc-1.1.1.vba.gz","src_id":"12013","5":"12013","creation_date":"1262635096","6":"1262635096"},{"0":"2878","vim_version":"6.0","1":"6.0","script_version":"1.1.0","2":"1.1.0","version_comment":"* Added new snippets.\r\n* Added Vimball deployment.\r\n* Fix in build tasks.\r\n* Improvements in code and new pool tasks.\r\n* Change the file name of the package content.\r\n* Updates in documentation and renamed build file.\r\n","3":"* Added new snippets.\r\n* Added Vimball deployment.\r\n* Fix in build tasks.\r\n* Improvements in code and new pool tasks.\r\n* Change the file name of the package content.\r\n* Updates in documentation and renamed build file.\r\n","package":"rdoc-1.1.0.vba.gz","4":"rdoc-1.1.0.vba.gz","src_id":"11940","5":"11940","creation_date":"1261515950","6":"1261515950"},{"0":"2878","vim_version":"6.0","1":"6.0","script_version":"1.0.0","2":"1.0.0","version_comment":"* Changed the file name of the package content.\r\n* Improvements in code and new pool tasks.\r\n* Fix in pool tasks.","3":"* Changed the file name of the package content.\r\n* Improvements in code and new pool tasks.\r\n* Fix in pool tasks.","package":"rdoc-1.0.0.vba.gz","4":"rdoc-1.0.0.vba.gz","src_id":"11860","5":"11860","creation_date":"1259940928","6":"1259940928"},{"0":"2878","vim_version":"6.0","1":"6.0","script_version":"0.1.1","2":"0.1.1","version_comment":"* Vimball has been added.\r\n* New snippets.","3":"* Vimball has been added.\r\n* New snippets.","package":"rdoc-0.1.1.vba.gz","4":"rdoc-0.1.1.vba.gz","src_id":"11856","5":"11856","creation_date":"1259907051","6":"1259907051"},{"0":"2878","vim_version":"6.0","1":"6.0","script_version":"0.1.0","2":"0.1.0","version_comment":"Initial upload","3":"Initial upload","package":"rdoc-0.1.0.zip","4":"rdoc-0.1.0.zip","src_id":"11844","5":"11844","creation_date":"1259777696","6":"1259777696"}]},"2877":{"script_id":"2877","0":"2877","script_name":"spinner.vim","1":"spinner.vim","script_type":"utility","2":"utility","summary":"fast buffer\/file\/tab\/window switching plugin with only 3 keys.","3":"fast buffer\/file\/tab\/window switching plugin with only 3 keys.","description":"Introduction:\r\na basic idea is easy pressable key,\r\nand quickly switchable search type .\r\n\r\nBasic Usage:\r\nDefault defined key map is\r\n    <C-CR>     open next item .\r\n    <S-CR>     open previous item .\r\n    <C-S-CR>   switch spinner.vim search mode .\r\n\r\nspinner.vim search mode is switching, when you press <C-S-CR>.\r\nDefined search mode is\r\n    1. open next\/previous buffer (initial) .\r\n    2. open next\/previous file in currently opened file directory .\r\n    3. open next\/previous most recently edited file (last 10 files) .\r\n    4. open next\/previous tab .\r\n    5. open next\/previous window .\r\n    6. open next\/previous quickfix line .\r\n    7. open next\/previous quickfix file .\r\n\r\nSpinner Search Mode Details:\r\n1.open next\/previous buffer (initial) .\r\n    <C-CR> open next buffer.\r\n    <S-CR> open previous buffer.\r\n  same with :bnext, :bNext .\r\n\r\n2.open next\/previous file in currently opened file directory .\r\n    <C-CR> open alphabetically next file.\r\n    <S-CR> open alphabetically previous file .\r\n  opening files are searched in currently opened file directory.\r\n\r\n  current test version use code from\r\n  nextfile : open the next or previous file\r\n  (vimscript #2605)\r\n\r\n3.open next\/previous most recently edited file (last 10 files) .\r\n    <C-CR> open alphabetically next file.\r\n    <S-CR> open alphabetically previous file .\r\n\r\n  recently edited file path are stored at openinig file (limit 10 item).\r\n  stored file is placed at\r\n      $HOME\/.vim_spinner_mru_files , or\r\n      $VIM\/.vim_spinner_mru_files , or\r\n      $USERPROFILE\/_vim_spinner_mru_files .\r\n\r\n  current test version use code from\r\n  mru.vim : Plugin to manage Most Recently Used (MRU) files\r\n  (vimscript #521)\r\n\r\n4.open next\/previous tab .\r\n    <C-CR> go to next tab.\r\n    <S-CR> go to previous tab.\r\n  same with :tabnext, :tabNext .\r\n\r\n5.open next\/previous window .\r\n    <C-CR> move cursor to next splitted window.\r\n    <S-CR> move cursor to previous splitted window.\r\n\r\n6.open next\/previous quickfix line .\r\n    <C-CR> go to next error in quickfix list.\r\n    <S-CR> go to previous error in quickfix list.\r\n  same with :cnext, :cNext .\r\n\r\n7.open next\/previous quickfix file .\r\n    <C-CR> go to next error file in quickfix list.\r\n    <S-CR> go to previous error file in quickfix list.\r\n  same with :cnfile, :cNfile .\r\n\r\nOther Usage:\r\nswitch search mode with number.\r\n    1<C-S-CR>  set switch spinner.vim mode to buffer type.\r\n    2<C-S-CR>  set switch spinner.vim mode to same_directory_file type.\r\n    3<C-S-CR>  set switch spinner.vim mode to most_recently_edited type.\r\n    4<C-S-CR>  set switch spinner.vim mode to tab type.\r\n    5<C-S-CR>  set switch spinner.vim mode to window type.\r\n    6<C-S-CR>  set switch spinner.vim mode to quickfix type.\r\n    7<C-S-CR>  set switch spinner.vim mode to quickfix_file type.\r\n\r\nthis key map display current spinner search mode.\r\n    <A-CR>     display current spinner mode .\r\n    <M-CR>     display current spinner mode .\r\n\r\nConfigurations:\r\nAction Key Map:\r\n    let g:spinner_nextitem_key = {mapping}\r\n    let g:spinner_previousitem_key = {mapping}\r\n    let g:spinner_switchmode_key = {mapping}\r\n    let g:spinner_displaymode_key = {mapping}\r\n\r\n    for example,\r\n    let g:spinner_nextitem_key = ',n'\r\n    let g:spinner_previousitem_key = ',p'\r\n    let g:spinner_switchmode_key = ',s'\r\n    let g:spinner_displaymode_key = ',d'\r\n\r\ncaution!!\r\n    default mapping is for GUI. default mapping do not work on\r\n    Windows DOS prompt, PowerShell, Mac OSX Terminal,,,\r\n\r\nInitial Search Type:\r\n  let g:spinner_initial_search_type = {seach type number}\r\n\r\n  for example,\r\n  let g:spinner_initial_search_type = 2\r\n\r\n      1 : buffer (default)\r\n      2 : same_directory_file\r\n      3 : most_recently_edited\r\n      4 : tab\r\n      5 : window\r\n      6 : quickfix\r\n      7 : quickfix_file\r\n\r\nSource Repository:\r\n    https:\/\/code.google.com\/p\/spinner-vim-plugin\/\r\n","4":"Introduction:\r\na basic idea is easy pressable key,\r\nand quickly switchable search type .\r\n\r\nBasic Usage:\r\nDefault defined key map is\r\n    <C-CR>     open next item .\r\n    <S-CR>     open previous item .\r\n    <C-S-CR>   switch spinner.vim search mode .\r\n\r\nspinner.vim search mode is switching, when you press <C-S-CR>.\r\nDefined search mode is\r\n    1. open next\/previous buffer (initial) .\r\n    2. open next\/previous file in currently opened file directory .\r\n    3. open next\/previous most recently edited file (last 10 files) .\r\n    4. open next\/previous tab .\r\n    5. open next\/previous window .\r\n    6. open next\/previous quickfix line .\r\n    7. open next\/previous quickfix file .\r\n\r\nSpinner Search Mode Details:\r\n1.open next\/previous buffer (initial) .\r\n    <C-CR> open next buffer.\r\n    <S-CR> open previous buffer.\r\n  same with :bnext, :bNext .\r\n\r\n2.open next\/previous file in currently opened file directory .\r\n    <C-CR> open alphabetically next file.\r\n    <S-CR> open alphabetically previous file .\r\n  opening files are searched in currently opened file directory.\r\n\r\n  current test version use code from\r\n  nextfile : open the next or previous file\r\n  (vimscript #2605)\r\n\r\n3.open next\/previous most recently edited file (last 10 files) .\r\n    <C-CR> open alphabetically next file.\r\n    <S-CR> open alphabetically previous file .\r\n\r\n  recently edited file path are stored at openinig file (limit 10 item).\r\n  stored file is placed at\r\n      $HOME\/.vim_spinner_mru_files , or\r\n      $VIM\/.vim_spinner_mru_files , or\r\n      $USERPROFILE\/_vim_spinner_mru_files .\r\n\r\n  current test version use code from\r\n  mru.vim : Plugin to manage Most Recently Used (MRU) files\r\n  (vimscript #521)\r\n\r\n4.open next\/previous tab .\r\n    <C-CR> go to next tab.\r\n    <S-CR> go to previous tab.\r\n  same with :tabnext, :tabNext .\r\n\r\n5.open next\/previous window .\r\n    <C-CR> move cursor to next splitted window.\r\n    <S-CR> move cursor to previous splitted window.\r\n\r\n6.open next\/previous quickfix line .\r\n    <C-CR> go to next error in quickfix list.\r\n    <S-CR> go to previous error in quickfix list.\r\n  same with :cnext, :cNext .\r\n\r\n7.open next\/previous quickfix file .\r\n    <C-CR> go to next error file in quickfix list.\r\n    <S-CR> go to previous error file in quickfix list.\r\n  same with :cnfile, :cNfile .\r\n\r\nOther Usage:\r\nswitch search mode with number.\r\n    1<C-S-CR>  set switch spinner.vim mode to buffer type.\r\n    2<C-S-CR>  set switch spinner.vim mode to same_directory_file type.\r\n    3<C-S-CR>  set switch spinner.vim mode to most_recently_edited type.\r\n    4<C-S-CR>  set switch spinner.vim mode to tab type.\r\n    5<C-S-CR>  set switch spinner.vim mode to window type.\r\n    6<C-S-CR>  set switch spinner.vim mode to quickfix type.\r\n    7<C-S-CR>  set switch spinner.vim mode to quickfix_file type.\r\n\r\nthis key map display current spinner search mode.\r\n    <A-CR>     display current spinner mode .\r\n    <M-CR>     display current spinner mode .\r\n\r\nConfigurations:\r\nAction Key Map:\r\n    let g:spinner_nextitem_key = {mapping}\r\n    let g:spinner_previousitem_key = {mapping}\r\n    let g:spinner_switchmode_key = {mapping}\r\n    let g:spinner_displaymode_key = {mapping}\r\n\r\n    for example,\r\n    let g:spinner_nextitem_key = ',n'\r\n    let g:spinner_previousitem_key = ',p'\r\n    let g:spinner_switchmode_key = ',s'\r\n    let g:spinner_displaymode_key = ',d'\r\n\r\ncaution!!\r\n    default mapping is for GUI. default mapping do not work on\r\n    Windows DOS prompt, PowerShell, Mac OSX Terminal,,,\r\n\r\nInitial Search Type:\r\n  let g:spinner_initial_search_type = {seach type number}\r\n\r\n  for example,\r\n  let g:spinner_initial_search_type = 2\r\n\r\n      1 : buffer (default)\r\n      2 : same_directory_file\r\n      3 : most_recently_edited\r\n      4 : tab\r\n      5 : window\r\n      6 : quickfix\r\n      7 : quickfix_file\r\n\r\nSource Repository:\r\n    https:\/\/code.google.com\/p\/spinner-vim-plugin\/\r\n","install_details":"1. open spinner-vim-plugin.vba with Vim editor.\r\n2. extract spinner-vim-plugin with :source command.\r\n\r\n    source %\r\n","5":"1. open spinner-vim-plugin.vba with Vim editor.\r\n2. extract spinner-vim-plugin with :source command.\r\n\r\n    source %\r\n","first_name":"omi","6":"omi","last_name":"taku","7":"taku","releases":[{"0":"2877","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"to vimball archive.","3":"to vimball archive.","package":"spinner-vim-plugin.vba","4":"spinner-vim-plugin.vba","src_id":"11903","5":"11903","creation_date":"1260864898","6":"1260864898"},{"0":"2877","vim_version":"7.0","1":"7.0","script_version":"0.5.2","2":"0.5.2","version_comment":"- update plugins initialize logic.\r\n- same_directory_file mode will not open $PATHEXT extension file.\r\n  (for Windows)","3":"- update plugins initialize logic.\r\n- same_directory_file mode will not open $PATHEXT extension file.\r\n  (for Windows)","package":"spinner.zip","4":"spinner.zip","src_id":"11885","5":"11885","creation_date":"1260360073","6":"1260360073"},{"0":"2877","vim_version":"7.0","1":"7.0","script_version":"0.5.1","2":"0.5.1","version_comment":"- update some displaying messages.\r\n- add spinner.vim help document.\r\n- fix most_recently_edited mode initialize bug.\r\n","3":"- update some displaying messages.\r\n- add spinner.vim help document.\r\n- fix most_recently_edited mode initialize bug.\r\n","package":"spinner.zip","4":"spinner.zip","src_id":"11848","5":"11848","creation_date":"1259839473","6":"1259839473"},{"0":"2877","vim_version":"7.2","1":"7.2","script_version":"0.5","2":"0.5","version_comment":"Initial upload","3":"Initial upload","package":"spinner.zip","4":"spinner.zip","src_id":"11841","5":"11841","creation_date":"1259755360","6":"1259755360"}]},"2876":{"script_id":"2876","0":"2876","script_name":"HTML menu for GVIM","1":"HTML menu for GVIM","script_type":"utility","2":"utility","summary":"my HTML menu with Tag I use often","3":"my HTML menu with Tag I use often","description":"This is my personal Html menu for GVim. I started to write it for 6.x release and updated it everytime I needed ;)\r\nIt includes :\r\n\r\n* a \"new blank Html\" feature, \r\n* all Heading tags, \r\n* formatting text with tags most used (not all...) and font\/color tags, \r\n* function to insert Tables, List Item, special chars\r\n* option to indent source page \r\n\r\nand more...\r\n","4":"This is my personal Html menu for GVim. I started to write it for 6.x release and updated it everytime I needed ;)\r\nIt includes :\r\n\r\n* a \"new blank Html\" feature, \r\n* all Heading tags, \r\n* formatting text with tags most used (not all...) and font\/color tags, \r\n* function to insert Tables, List Item, special chars\r\n* option to indent source page \r\n\r\nand more...\r\n","install_details":"first save the file in GVim folder,  then add in your .vimrc this line:\r\nsource $VIMRUNTIME\/vim_menu_HTMLpol\r\n","5":"first save the file in GVim folder,  then add in your .vimrc this line:\r\nsource $VIMRUNTIME\/vim_menu_HTMLpol\r\n","first_name":"Paolo","6":"Paolo","last_name":"Baruffa","7":"Baruffa","releases":[{"0":"2876","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"vim_menu_HTMLpol","4":"vim_menu_HTMLpol","src_id":"11840","5":"11840","creation_date":"1259741811","6":"1259741811"}]},"2875":{"script_id":"2875","0":"2875","script_name":"signal_dec_VHDL","1":"signal_dec_VHDL","script_type":"utility","2":"utility","summary":"Defines internal signals in VHDL","3":"Defines internal signals in VHDL","description":"This utility defines an internal signal in VHDL. It map the function to key combination ,,. Within the architecture region, do ,, in visual mode and you will be prompted for the length of the signal. Only works for std_logic and std_logic_vector.","4":"This utility defines an internal signal in VHDL. It map the function to key combination ,,. Within the architecture region, do ,, in visual mode and you will be prompted for the length of the signal. Only works for std_logic and std_logic_vector.","install_details":"copy the file anywhere and source it in your _vimrc.","5":"copy the file anywhere and source it in your _vimrc.","first_name":"Sunil","6":"Sunil","last_name":"Shukla","7":"Shukla","releases":[{"0":"2875","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"signal_dec_VHDL.vim","4":"signal_dec_VHDL.vim","src_id":"11832","5":"11832","creation_date":"1259573415","6":"1259573415"}]},"2874":{"script_id":"2874","0":"2874","script_name":"php.vim","1":"php.vim","script_type":"syntax","2":"syntax","summary":"PHP syntax file updated for PHP 5.3","3":"PHP syntax file updated for PHP 5.3","description":"This is an updated version of the php.vim syntax file distributed with VIM. The list of PHP constants, functions, and classes was updated to be current with PHP 5.3. Many new classes were added in the 5.2 branch and the distributed version only covers up to 5.1.4. In addition I simplified the file, removing several sections that are not often used (at least by me) such as automatic folding of all control structures and ASP tags support. I also removed several switches designed for b\/c with VIM 5.X and 6.X. As an addition I have included the PHP file I used to generate the constant, function, class list. It uses reflection to mine out these items from your PHP installation and generate part of the php.vim script. Before running open up the file and adjust the output file location and the list of extensions to generate syntax for. Then run \"php php_vimgen.php\" from your shell.","4":"This is an updated version of the php.vim syntax file distributed with VIM. The list of PHP constants, functions, and classes was updated to be current with PHP 5.3. Many new classes were added in the 5.2 branch and the distributed version only covers up to 5.1.4. In addition I simplified the file, removing several sections that are not often used (at least by me) such as automatic folding of all control structures and ASP tags support. I also removed several switches designed for b\/c with VIM 5.X and 6.X. As an addition I have included the PHP file I used to generate the constant, function, class list. It uses reflection to mine out these items from your PHP installation and generate part of the php.vim script. Before running open up the file and adjust the output file location and the list of extensions to generate syntax for. Then run \"php php_vimgen.php\" from your shell.","install_details":"Create the following directory if it does not already exist and place php.vim inside of it.\r\nUnix: \/home\/<username>\/.vim\/syntax\/\r\nWindows up to & incl XP: C:\\Documents and Settings\\<username>\\_vim\\syntax\\\r\nWindows Vista & 7: C:\\Users\\<username\\_vim\\syntax\\","5":"Create the following directory if it does not already exist and place php.vim inside of it.\r\nUnix: \/home\/<username>\/.vim\/syntax\/\r\nWindows up to & incl XP: C:\\Documents and Settings\\<username>\\_vim\\syntax\\\r\nWindows Vista & 7: C:\\Users\\<username\\_vim\\syntax\\","first_name":"Paul","6":"Paul","last_name":"Garvin","7":"Garvin","releases":[{"0":"2874","vim_version":"7.0","1":"7.0","script_version":"1.1","2":"1.1","version_comment":"Added missing keyword 'default'. Added highlighting of escaped single quotes, double quotes, backslashes, and dollar signs in strings. Shows up same color as \\r, \\n & friends.","3":"Added missing keyword 'default'. Added highlighting of escaped single quotes, double quotes, backslashes, and dollar signs in strings. Shows up same color as \\r, \\n & friends.","package":"php53.tar.gz","4":"php53.tar.gz","src_id":"12772","5":"12772","creation_date":"1270230839","6":"1270230839"},{"0":"2874","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"php53.tar.gz","4":"php53.tar.gz","src_id":"11828","5":"11828","creation_date":"1259514064","6":"1259514064"}]},"2873":{"script_id":"2873","0":"2873","script_name":"record-repeat.vim","1":"record-repeat.vim","script_type":"utility","2":"utility","summary":"Repeat sequences of commands","3":"Repeat sequences of commands","description":"Automagically record and repeat a sequence of commands using the [count]@(<command>) mapping.\r\n\r\nFor example: 5@(jj) will move the cursor down 10 lines. This is similar to qajjq4@a but hopefully easier to type and understand.","4":"Automagically record and repeat a sequence of commands using the [count]@(<command>) mapping.\r\n\r\nFor example: 5@(jj) will move the cursor down 10 lines. This is similar to qajjq4@a but hopefully easier to type and understand.","install_details":"","5":"","first_name":"Andy","6":"Andy","last_name":"Spencer","7":"Spencer","releases":[{"0":"2873","vim_version":"7.0","1":"7.0","script_version":"0.1.1","2":"0.1.1","version_comment":"Use <nop> instead of :<CR>","3":"Use <nop> instead of :<CR>","package":"record-repeat.vim","4":"record-repeat.vim","src_id":"11819","5":"11819","creation_date":"1259342643","6":"1259342643"},{"0":"2873","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"record-repeat.vim","4":"record-repeat.vim","src_id":"11818","5":"11818","creation_date":"1259341575","6":"1259341575"}]},"2872":{"script_id":"2872","0":"2872","script_name":"signature_block.vim","1":"signature_block.vim","script_type":"utility","2":"utility","summary":"Add and manipulate signature blocks in e-mails","3":"Add and manipulate signature blocks in e-mails","description":"signature_block.vim is a simple plugin for adding and manipulating signature blocks in e-mails.\r\n\r\nIt provides handy functions that can be called from maps or autocommands.\r\n\r\nThere are other scripts offering similar functionality, see vimscript #45 or vimscript #10 or vimscript #509 but signature_block.vim is easier to understand and it can be easily extended.\r\n\r\nThe upstream git repository is available at:\r\nhttps:\/\/git.ao2.it\/vim\/signature_block.vim.git\/","4":"signature_block.vim is a simple plugin for adding and manipulating signature blocks in e-mails.\r\n\r\nIt provides handy functions that can be called from maps or autocommands.\r\n\r\nThere are other scripts offering similar functionality, see vimscript #45 or vimscript #10 or vimscript #509 but signature_block.vim is easier to understand and it can be easily extended.\r\n\r\nThe upstream git repository is available at:\r\nhttps:\/\/git.ao2.it\/vim\/signature_block.vim.git\/","install_details":"Drop the signature_block.vim file into your $HOME\/.vim\/plugin directory and call it from autocmd, like that:\r\n\r\n\" Replace the git version with a signature in cover letters generated with git-format-patch\r\nautocmd BufRead 0000-cover-letter.patch if ReplaceLastSignature('~\/.signature') | w | endif\r\nautocmd BufRead 0000-cover-letter.patch autocmd! BufRead 0000-cover-letter.patch\r\n","5":"Drop the signature_block.vim file into your $HOME\/.vim\/plugin directory and call it from autocmd, like that:\r\n\r\n\" Replace the git version with a signature in cover letters generated with git-format-patch\r\nautocmd BufRead 0000-cover-letter.patch if ReplaceLastSignature('~\/.signature') | w | endif\r\nautocmd BufRead 0000-cover-letter.patch autocmd! BufRead 0000-cover-letter.patch\r\n","first_name":"Antonio","6":"Antonio","last_name":"Ospite","7":"Ospite","releases":[{"0":"2872","vim_version":"7.0","1":"7.0","script_version":"0.2","2":"0.2","version_comment":"- Check that the signature file is readable before removing the old signature and append the new one.\r\n- Minor fixes.\r\n","3":"- Check that the signature file is readable before removing the old signature and append the new one.\r\n- Minor fixes.\r\n","package":"signature_block.vim","4":"signature_block.vim","src_id":"24313","5":"24313","creation_date":"1465398503","6":"1465398503"},{"0":"2872","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"signature_block.vim","4":"signature_block.vim","src_id":"11813","5":"11813","creation_date":"1259243273","6":"1259243273"}]},"2871":{"script_id":"2871","0":"2871","script_name":"FindMate","1":"FindMate","script_type":"utility","2":"utility","summary":"Find files in your whole system or current directory","3":"Find files in your whole system or current directory","description":"FindMate provides a convenient way (at least for me) to quickly find the\r\nfiles you want. It uses the locate and file commands to achieve its goal\r\n(vimgrep on windows). \r\n\r\nOriginality it was released by Manuel Aguilar and Victor Guardiola but since I\r\ncouldn't reach neither of them I decide to upload it by myself (and add some\r\ndocumentation) because I consider that this script could help someone else.\r\n\r\nThe original script can be still found at\r\n\r\nhttp:\/\/snipt.net\/voyeg3r\/findmate-plugin-for-vim\/\r\n\r\nYou can launch FindMate by typing:\r\n\r\n    ,, File_name (two commas)\r\n\r\nOr\r\n\r\n    :FindMate File_name\r\n\r\nThe shortcut can be redefined by using:\r\n\r\n    map your_shortcut   <Plug>FindMate","4":"FindMate provides a convenient way (at least for me) to quickly find the\r\nfiles you want. It uses the locate and file commands to achieve its goal\r\n(vimgrep on windows). \r\n\r\nOriginality it was released by Manuel Aguilar and Victor Guardiola but since I\r\ncouldn't reach neither of them I decide to upload it by myself (and add some\r\ndocumentation) because I consider that this script could help someone else.\r\n\r\nThe original script can be still found at\r\n\r\nhttp:\/\/snipt.net\/voyeg3r\/findmate-plugin-for-vim\/\r\n\r\nYou can launch FindMate by typing:\r\n\r\n    ,, File_name (two commas)\r\n\r\nOr\r\n\r\n    :FindMate File_name\r\n\r\nThe shortcut can be redefined by using:\r\n\r\n    map your_shortcut   <Plug>FindMate","install_details":"Download this file to ~\/.vim  or to \/vimfiles  (on Win32 platforms) and extract the files there.\r\nUpdate your help tags files, running:\r\n\r\n:helpt ~\/.vim\/doc\/","5":"Download this file to ~\/.vim  or to \/vimfiles  (on Win32 platforms) and extract the files there.\r\nUpdate your help tags files, running:\r\n\r\n:helpt ~\/.vim\/doc\/","first_name":"chili","6":"chili","last_name":"cuil","7":"cuil","releases":[{"0":"2871","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"FindMate.zip","4":"FindMate.zip","src_id":"11807","5":"11807","creation_date":"1259212614","6":"1259212614"},{"0":"2871","vim_version":"6.0","1":"6.0","script_version":"original","2":"original","version_comment":"Original","3":"Original","package":"findmate.vim.orig","4":"findmate.vim.orig","src_id":"11804","5":"11804","creation_date":"1259210914","6":"1259210914"}]},"2870":{"script_id":"2870","0":"2870","script_name":"OmniTags","1":"OmniTags","script_type":"utility","2":"utility","summary":"This plugin can help you to maintenance tags file.","3":"This plugin can help you to maintenance tags file.","description":"SEE MY NEW PLUGIN: vimscript #3684, it is more powerful for c programmer!\r\n\r\n 12 \"   This plugin can help you to maintenance tags file.\r\n 13 \"\r\n 14 \"   There are 3 commands:\r\n 15 \"\r\n 16 \"     1. :OmniTagsLoad \/path\/to\/tags-file\r\n 17 \"\r\n 18 \"     Load the tags-file and generate a list of source files indexed by\r\n 19 \"     tags-file.\r\n 20 \"\r\n 21 \"     If tags-file doesn't exist, it can create a null file automaticlly.\r\n 22 \"\r\n 23 \"     Once tags-file are loaded, every buffer-write event will trigger a\r\n 24 \"     re-index operation on current file if current file exists in tags-file.\r\n 25 \"\r\n 26 \"     The re-index operation will do:\r\n 27 \"       a) delete tags of current file from tags-file.\r\n 28 \"       b) call \"ctags -a\" command add the tags of current file to tags-file.\r\n 29 \"\r\n 30 \"     Therefor, your tags-file will always updated.\r\n 31 \"\r\n 32 \"     Don't mind the speed of re-index operation, it is indetectable while\r\n 33 \"     the tags-file size small than 20MiB.\r\n 34 \"\r\n 35 \"     2. :OmniTagsUpdate {file1} {file2} ...\r\n 36 \"\r\n 37 \"     Update the tags-file loaded before, you can specify many files and use\r\n 38 \"     wildcards(see \":h wildcards\"), \"wildignore\" option(see \"h: wildignore\")\r\n 39 \"     also influences the result of wildcards parsing.\r\n 40 \"\r\n 41 \"     If files are not in tags yet, the plugin will add those files to tags,\r\n 42 \"     if files already exists, the plugin will update them.\r\n 43 \"\r\n 44 \"     You can specify no files, for re-index all files that already indexed.\r\n 45 \"\r\n 46 \"     3. :OmniTagsUnload\r\n 47 \"\r\n 48 \"     Just an oppsite of :OmniTagsLoad, usually needs not be called by human.","4":"SEE MY NEW PLUGIN: vimscript #3684, it is more powerful for c programmer!\r\n\r\n 12 \"   This plugin can help you to maintenance tags file.\r\n 13 \"\r\n 14 \"   There are 3 commands:\r\n 15 \"\r\n 16 \"     1. :OmniTagsLoad \/path\/to\/tags-file\r\n 17 \"\r\n 18 \"     Load the tags-file and generate a list of source files indexed by\r\n 19 \"     tags-file.\r\n 20 \"\r\n 21 \"     If tags-file doesn't exist, it can create a null file automaticlly.\r\n 22 \"\r\n 23 \"     Once tags-file are loaded, every buffer-write event will trigger a\r\n 24 \"     re-index operation on current file if current file exists in tags-file.\r\n 25 \"\r\n 26 \"     The re-index operation will do:\r\n 27 \"       a) delete tags of current file from tags-file.\r\n 28 \"       b) call \"ctags -a\" command add the tags of current file to tags-file.\r\n 29 \"\r\n 30 \"     Therefor, your tags-file will always updated.\r\n 31 \"\r\n 32 \"     Don't mind the speed of re-index operation, it is indetectable while\r\n 33 \"     the tags-file size small than 20MiB.\r\n 34 \"\r\n 35 \"     2. :OmniTagsUpdate {file1} {file2} ...\r\n 36 \"\r\n 37 \"     Update the tags-file loaded before, you can specify many files and use\r\n 38 \"     wildcards(see \":h wildcards\"), \"wildignore\" option(see \"h: wildignore\")\r\n 39 \"     also influences the result of wildcards parsing.\r\n 40 \"\r\n 41 \"     If files are not in tags yet, the plugin will add those files to tags,\r\n 42 \"     if files already exists, the plugin will update them.\r\n 43 \"\r\n 44 \"     You can specify no files, for re-index all files that already indexed.\r\n 45 \"\r\n 46 \"     3. :OmniTagsUnload\r\n 47 \"\r\n 48 \"     Just an oppsite of :OmniTagsLoad, usually needs not be called by human.","install_details":"Just drop the script to ~\/.vim\/plugin.\r\n\r\nI added a map to .vimrc \"nmap <silent> <leader>t <ESC>:OmniTagsLoad tags<CR>\" to load tags-file in current dir.\r\n\r\nThe plugin depends on unix commands below:\r\n  ctags, grep, tail, cut, sort\r\n\r\nCommon linux distribution installed them normally, you can find windows version of them at http:\/\/ctags.sf.net\/ and http:\/\/gnuwin32.sf.net\/ (windows version are not test yet, I guess it will work).\r\n\r\nBTW: There is a problem in ctags, see http:\/\/sourceforge.net\/tracker\/?func=detail&aid=2819658&group_id=6556&atid=106556. It will buggy when you using OmniTags and write many files. Use this patch to resolve that.","5":"Just drop the script to ~\/.vim\/plugin.\r\n\r\nI added a map to .vimrc \"nmap <silent> <leader>t <ESC>:OmniTagsLoad tags<CR>\" to load tags-file in current dir.\r\n\r\nThe plugin depends on unix commands below:\r\n  ctags, grep, tail, cut, sort\r\n\r\nCommon linux distribution installed them normally, you can find windows version of them at http:\/\/ctags.sf.net\/ and http:\/\/gnuwin32.sf.net\/ (windows version are not test yet, I guess it will work).\r\n\r\nBTW: There is a problem in ctags, see http:\/\/sourceforge.net\/tracker\/?func=detail&aid=2819658&group_id=6556&atid=106556. It will buggy when you using OmniTags and write many files. Use this patch to resolve that.","first_name":"lei","6":"lei","last_name":"fw","7":"fw","releases":[{"0":"2870","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"omnitags.tbz","4":"omnitags.tbz","src_id":"11796","5":"11796","creation_date":"1259073660","6":"1259073660"}]},"2869":{"script_id":"2869","0":"2869","script_name":"Ruby Single Test","1":"Ruby Single Test","script_type":"utility","2":"utility","summary":"Runs a single Ruby test under the cursor","3":"Runs a single Ruby test under the cursor","description":"When a ruby test file with your cursor within a test block, hit\r\n<leader>.\r\n(that's <leader><period>) and that test, and only that test, will run in quickfix.\r\nThat's it!\r\n\r\nSupports Test::Unit, Rspec and Minitest.  If run on an Rspec describe block it will run all the tests in that block (just using existing spec command-line functionality for that one).\r\n\r\nThe script is also hosted on GitHub:\r\nhttp:\/\/github.com\/dmcinnes\/ruby_single_test","4":"When a ruby test file with your cursor within a test block, hit\r\n<leader>.\r\n(that's <leader><period>) and that test, and only that test, will run in quickfix.\r\nThat's it!\r\n\r\nSupports Test::Unit, Rspec and Minitest.  If run on an Rspec describe block it will run all the tests in that block (just using existing spec command-line functionality for that one).\r\n\r\nThe script is also hosted on GitHub:\r\nhttp:\/\/github.com\/dmcinnes\/ruby_single_test","install_details":"Just drop the script in your .vim\/plugins folder.\r\n\r\nIf you use Vundle install with \":BundleInstall dmcinnes\/ruby_single_test\"\r\n\r\nIf you're having problems using rspec, be sure the makeprg is set to your spec executable.  To test this type:\r\n:echo &makeprg\r\nWhile in an rspec file.  It should output \"spec\".\r\n\r\nFor more information read Vim's documentation on makeprg (:h makeprg).\r\n\r\nThe Specky! plugin adds lots of goodness that makes working with rspecs nice, like filetype detection and syntax highlighting:\r\nhttp:\/\/www.vim.org\/scripts\/script.php?script_id=2286\r\n\r\nTo remap the command, to <leader>t for instance, add something like this to your .vimrc:\r\nnmap <silent> <leader>t <Plug>ExecuteRubyTest\r\n\r\nRuby Single Test defaults to using make! (with the bang).  To disable this behavior drop this in your .vimrc:\r\nlet g:ruby_single_test_no_bang = 1","5":"Just drop the script in your .vim\/plugins folder.\r\n\r\nIf you use Vundle install with \":BundleInstall dmcinnes\/ruby_single_test\"\r\n\r\nIf you're having problems using rspec, be sure the makeprg is set to your spec executable.  To test this type:\r\n:echo &makeprg\r\nWhile in an rspec file.  It should output \"spec\".\r\n\r\nFor more information read Vim's documentation on makeprg (:h makeprg).\r\n\r\nThe Specky! plugin adds lots of goodness that makes working with rspecs nice, like filetype detection and syntax highlighting:\r\nhttp:\/\/www.vim.org\/scripts\/script.php?script_id=2286\r\n\r\nTo remap the command, to <leader>t for instance, add something like this to your .vimrc:\r\nnmap <silent> <leader>t <Plug>ExecuteRubyTest\r\n\r\nRuby Single Test defaults to using make! (with the bang).  To disable this behavior drop this in your .vimrc:\r\nlet g:ruby_single_test_no_bang = 1","first_name":"Doug","6":"Doug","last_name":"McInnes","7":"McInnes","releases":[{"0":"2869","vim_version":"7.0","1":"7.0","script_version":"1.0.3","2":"1.0.3","version_comment":"support both single and double quotes in minitest","3":"support both single and double quotes in minitest","package":"ruby_single_test.vim","4":"ruby_single_test.vim","src_id":"20089","5":"20089","creation_date":"1368219281","6":"1368219281"},{"0":"2869","vim_version":"7.0","1":"7.0","script_version":"1.0.2","2":"1.0.2","version_comment":"now supports Minitest","3":"now supports Minitest","package":"ruby_single_test.vim","4":"ruby_single_test.vim","src_id":"20073","5":"20073","creation_date":"1368043101","6":"1368043101"},{"0":"2869","vim_version":"7.0","1":"7.0","script_version":"1.0.1","2":"1.0.1","version_comment":"Initial upload","3":"Initial upload","package":"ruby_single_test.vim","4":"ruby_single_test.vim","src_id":"11792","5":"11792","creation_date":"1259014204","6":"1259014204"}]},"2868":{"script_id":"2868","0":"2868","script_name":"fortran_line_length","1":"fortran_line_length","script_type":"utility","2":"utility","summary":"According to the file extension of a FORTRAN source file, a valid length is set.","3":"According to the file extension of a FORTRAN source file, a valid length is set.","description":"fortran_line_length.vim\r\nMarks the lines overflowing lines according to the extension of FORTRAN files.\r\n\r\nAny characters occurring after this column are considered as error, and are marked so by highlighting.\r\n\r\nFor screenshots and documentation, please see:\r\nhttps:\/\/github.com\/caglartoklu\/fortran_line_length.vim","4":"fortran_line_length.vim\r\nMarks the lines overflowing lines according to the extension of FORTRAN files.\r\n\r\nAny characters occurring after this column are considered as error, and are marked so by highlighting.\r\n\r\nFor screenshots and documentation, please see:\r\nhttps:\/\/github.com\/caglartoklu\/fortran_line_length.vim","install_details":"For Vundle users:\r\n    Bundle 'caglartoklu\/fortran_line_length.vim'\r\n\r\nFor Pathogen users:\r\n    cd ~\/.vim\/bundle\r\n    git clone git:\/\/github.com\/caglartoklu\/fortran_line_length.vim\r\n\r\nFor all other users, simply drop the fortran_line_length.vim file to your plugin directory.","5":"For Vundle users:\r\n    Bundle 'caglartoklu\/fortran_line_length.vim'\r\n\r\nFor Pathogen users:\r\n    cd ~\/.vim\/bundle\r\n    git clone git:\/\/github.com\/caglartoklu\/fortran_line_length.vim\r\n\r\nFor all other users, simply drop the fortran_line_length.vim file to your plugin directory.","first_name":"Caglar","6":"Caglar","last_name":"Toklu","7":"Toklu","releases":[{"0":"2868","vim_version":"7.0","1":"7.0","script_version":"2013-09-27","2":"2013-09-27","version_comment":"Synchronization version numbers, documentation and content with Github.","3":"Synchronization version numbers, documentation and content with Github.","package":"fortran_line_length.vim","4":"fortran_line_length.vim","src_id":"20857","5":"20857","creation_date":"1380295248","6":"1380295248"},{"0":"2868","vim_version":"6.0","1":"6.0","script_version":"0.0.3","2":"0.0.3","version_comment":"- FIX: Loosing the match ID after removing the match in another buffer.\r\n- Priority can be customized.\r\n- Group name can be customized if necessary.\r\n- Script will not load itself if it has been loaded before.\r\n- Script is now respecting the script ID to avoid clashes with others.","3":"- FIX: Loosing the match ID after removing the match in another buffer.\r\n- Priority can be customized.\r\n- Group name can be customized if necessary.\r\n- Script will not load itself if it has been loaded before.\r\n- Script is now respecting the script ID to avoid clashes with others.","package":"fortran_line_length.vim","4":"fortran_line_length.vim","src_id":"12893","5":"12893","creation_date":"1272050158","6":"1272050158"},{"0":"2868","vim_version":"6.0","1":"6.0","script_version":"0.0.2","2":"0.0.2","version_comment":"- 0.0.2, 2009-12-07\r\n  - The display format for match is now read from the global variable g:FORTRANMatchDisplayFormat instead of hard coded settings.\r\n    Now you can adapt it to your favorite colorscheme within VIMRC without modifiying the plugin itself.\r\n  - The file is saved in UNIX file format instead of Windows","3":"- 0.0.2, 2009-12-07\r\n  - The display format for match is now read from the global variable g:FORTRANMatchDisplayFormat instead of hard coded settings.\r\n    Now you can adapt it to your favorite colorscheme within VIMRC without modifiying the plugin itself.\r\n  - The file is saved in UNIX file format instead of Windows","package":"fortran_line_length.vim","4":"fortran_line_length.vim","src_id":"11880","5":"11880","creation_date":"1260181906","6":"1260181906"},{"0":"2868","vim_version":"6.0","1":"6.0","script_version":"0.0.1","2":"0.0.1","version_comment":"Initial upload","3":"Initial upload","package":"fortran_line_length.vim","4":"fortran_line_length.vim","src_id":"11791","5":"11791","creation_date":"1258997030","6":"1258997030"}]},"2867":{"script_id":"2867","0":"2867","script_name":"\"Go\" Syntax","1":"\"Go\" Syntax","script_type":"syntax","2":"syntax","summary":"Syntax definitions for Google's \"Go\" language.","3":"Syntax definitions for Google's \"Go\" language.","description":"I am new to syntaxes, but this is a first-attempt at hacking up some Go syntax support.\r\n\r\nI started with the existing C syntax file and just hacked it up until it looked ok.\r\n\r\nImprovements are welcome.","4":"I am new to syntaxes, but this is a first-attempt at hacking up some Go syntax support.\r\n\r\nI started with the existing C syntax file and just hacked it up until it looked ok.\r\n\r\nImprovements are welcome.","install_details":"","5":"","first_name":"jesse","6":"jesse","last_name":"dailey","7":"dailey","releases":[{"0":"2867","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"go.vim","4":"go.vim","src_id":"11790","5":"11790","creation_date":"1258995907","6":"1258995907"}]},"2866":{"script_id":"2866","0":"2866","script_name":"gemcolors","1":"gemcolors","script_type":"color scheme","2":"color scheme","summary":"colorfull theme dark background","3":"colorfull theme dark background","description":"Example:\r\nhttp:\/\/farm3.static.flickr.com\/2564\/4127746406_5c93fea0a8_o.png\r\n\r\nhttp:\/\/farm3.static.flickr.com\/2679\/4126975329_9c9966d1db_o.png\r\n\r\n\r\nBug report: http:\/\/huacnlee.com\/blog\/vim-color-scheme-gemcolors","4":"Example:\r\nhttp:\/\/farm3.static.flickr.com\/2564\/4127746406_5c93fea0a8_o.png\r\n\r\nhttp:\/\/farm3.static.flickr.com\/2679\/4126975329_9c9966d1db_o.png\r\n\r\n\r\nBug report: http:\/\/huacnlee.com\/blog\/vim-color-scheme-gemcolors","install_details":"copy gemcolors into your .vim\/colors path\r\nopen you .vimrc (windows as _vimrc) and append(if existed colorscheme replace it):\r\n\r\n  colorscheme gemcolors \r\n\r\n","5":"copy gemcolors into your .vim\/colors path\r\nopen you .vimrc (windows as _vimrc) and append(if existed colorscheme replace it):\r\n\r\n  colorscheme gemcolors \r\n\r\n","first_name":"Jason","6":"Jason","last_name":"Lee","7":"Lee","releases":[{"0":"2866","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"gemcolors.vim","4":"gemcolors.vim","src_id":"11788","5":"11788","creation_date":"1258969622","6":"1258969622"}]},"2865":{"script_id":"2865","0":"2865","script_name":"colqer","1":"colqer","script_type":"utility","2":"utility","summary":"switch to colemak in insert mode","3":"switch to colemak in insert mode","description":"This script allows to quicky switch to Colemak   from a Qwerty keyboard, which is usefull if you are learning Colemak or want to come back to the Qwerty keybinding from a Colemaek keyboard.\r\n \r\nThis is a an approximation of the langmap feature, but which works even if your vim version has been compiled with the langmap feature.\r\n\r\nDepending of your keyboard layout, this script will either map the qwerty key into Colemak key in insert mode\r\nor map the Colemak key to qwerty in command mode.\r\nSo whatever your keyboard is Qwerty or Colemak, you could type text in Colemak and command in Qwerty.\r\n\r\nThis script is disabled by default, to activate it, type \\; (on a Qwerty keyboard) or \\o )on a Colemak one).\r\nMapping:\r\n<Leader>; toggle script on Qwerty keyboard\r\n<Leader>o toggle script activation on a Colemak keyboard\r\n(if you don't know wthat Leader is, it would probably be  \"\\\" in your case, so the mapping are \\; and \\o)\r\n\r\nWarning, this script might interfere with your personal mapping, in that case the easiest way to do it is to delete or modify  the problematic mapping\/unmapping  lines in the script.","4":"This script allows to quicky switch to Colemak   from a Qwerty keyboard, which is usefull if you are learning Colemak or want to come back to the Qwerty keybinding from a Colemaek keyboard.\r\n \r\nThis is a an approximation of the langmap feature, but which works even if your vim version has been compiled with the langmap feature.\r\n\r\nDepending of your keyboard layout, this script will either map the qwerty key into Colemak key in insert mode\r\nor map the Colemak key to qwerty in command mode.\r\nSo whatever your keyboard is Qwerty or Colemak, you could type text in Colemak and command in Qwerty.\r\n\r\nThis script is disabled by default, to activate it, type \\; (on a Qwerty keyboard) or \\o )on a Colemak one).\r\nMapping:\r\n<Leader>; toggle script on Qwerty keyboard\r\n<Leader>o toggle script activation on a Colemak keyboard\r\n(if you don't know wthat Leader is, it would probably be  \"\\\" in your case, so the mapping are \\; and \\o)\r\n\r\nWarning, this script might interfere with your personal mapping, in that case the easiest way to do it is to delete or modify  the problematic mapping\/unmapping  lines in the script.","install_details":"just download the file and drop it in your plugin directory (.vim\/plugin in your home folder).","5":"just download the file and drop it in your plugin directory (.vim\/plugin in your home folder).","first_name":"bmx","6":"bmx","last_name":"007","7":"007","releases":[{"0":"2865","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"colqer.vim","4":"colqer.vim","src_id":"11784","5":"11784","creation_date":"1258893937","6":"1258893937"}]},"2864":{"script_id":"2864","0":"2864","script_name":"NSIS syntax highlighting","1":"NSIS syntax highlighting","script_type":"syntax","2":"syntax","summary":"NSIS syntax file for NSIS 2.46","3":"NSIS syntax file for NSIS 2.46","description":"This is a new syntax file for NSIS 2.46, properly documented as to where in the user manual each keyword comes from as well.  It was based originally on nsis.vim from Vim 7.2 (last edited 12 May 2004), and all keywords were refreshed from the 2.46 user manual.\r\n\r\nAll new NSIS syntax is properly supported and highlighted.\r\n\r\n(I really think that this should go into the Vim core runtime files as an update to the old script, but I'm not sure about how to go about getting that to happen.)","4":"This is a new syntax file for NSIS 2.46, properly documented as to where in the user manual each keyword comes from as well.  It was based originally on nsis.vim from Vim 7.2 (last edited 12 May 2004), and all keywords were refreshed from the 2.46 user manual.\r\n\r\nAll new NSIS syntax is properly supported and highlighted.\r\n\r\n(I really think that this should go into the Vim core runtime files as an update to the old script, but I'm not sure about how to go about getting that to happen.)","install_details":"Place nsis.vim in $VIMRUNTIME\\syntax or in vimfiles\\syntax (wherever vimfiles is).\r\n\r\nIf you want NSIS script headers to be highlighted as well (which you should and which Vim itself should), add:\r\n    augroup filetypedetect\r\n        au BufNewFile,BufRead *.nsh setf nsis\r\n    augroup END\r\nto your vimrc, or just the middle line to $VIMRUNTIME\\filetype.vim just below the *.nsi line (around line 1216)\r\n\r\n(It works for Vim 5.7 or later, designed in 7.2\/7.3)","5":"Place nsis.vim in $VIMRUNTIME\\syntax or in vimfiles\\syntax (wherever vimfiles is).\r\n\r\nIf you want NSIS script headers to be highlighted as well (which you should and which Vim itself should), add:\r\n    augroup filetypedetect\r\n        au BufNewFile,BufRead *.nsh setf nsis\r\n    augroup END\r\nto your vimrc, or just the middle line to $VIMRUNTIME\\filetype.vim just below the *.nsi line (around line 1216)\r\n\r\n(It works for Vim 5.7 or later, designed in 7.2\/7.3)","first_name":"Chris","6":"Chris","last_name":"Morgan","7":"Morgan","releases":[{"0":"2864","vim_version":"5.7","1":"5.7","script_version":"2.46-2","2":"2.46-2","version_comment":"Highlight $\\' and $\\` as well as $\\\"","3":"Highlight $\\' and $\\` as well as $\\\"","package":"nsis.vim","4":"nsis.vim","src_id":"17564","5":"17564","creation_date":"1330930415","6":"1330930415"},{"0":"2864","vim_version":"5.7","1":"5.7","script_version":"2.46-1","2":"2.46-1","version_comment":"Improved !else to highlight the optional if((macro)?n?def) argument\r\nAdded SetPluginUnload (not in NSIS user manual; deprecated but still used)\r\nFixed highlighting of any single character as Number (bad decimal rule)\r\nStarted doing incorrect syntax error highlighting and only highlighting arguments in the proper place\r\nAdded the line continuation character (\\)\r\nVariable highlighting (far from perfect and doesn't auto-update, but it may be helpful)\r\nAdded extra Unicode NSIS instructions (and nsis_no_unicode_instructions to not highlight them): FileReadWord, FileReadUTF16LE, FileWriteWord, FileWriteUTF16LE, FindProc\r\nAdded MB_USERICON to MessageBox parameters","3":"Improved !else to highlight the optional if((macro)?n?def) argument\r\nAdded SetPluginUnload (not in NSIS user manual; deprecated but still used)\r\nFixed highlighting of any single character as Number (bad decimal rule)\r\nStarted doing incorrect syntax error highlighting and only highlighting arguments in the proper place\r\nAdded the line continuation character (\\)\r\nVariable highlighting (far from perfect and doesn't auto-update, but it may be helpful)\r\nAdded extra Unicode NSIS instructions (and nsis_no_unicode_instructions to not highlight them): FileReadWord, FileReadUTF16LE, FileWriteWord, FileWriteUTF16LE, FindProc\r\nAdded MB_USERICON to MessageBox parameters","package":"nsis.vim","4":"nsis.vim","src_id":"17562","5":"17562","creation_date":"1330903318","6":"1330903318"},{"0":"2864","vim_version":"5.7","1":"5.7","script_version":"2.45-3","2":"2.45-3","version_comment":"Fixed ; or # comment characters at end of line making the next line a comment\r\nFixed ${|} and ${||} LogicLib highlighting\r\nChanged nsisTodo list's contents and added it and @Spell to a new nsisCommentGroup","3":"Fixed ; or # comment characters at end of line making the next line a comment\r\nFixed ${|} and ${||} LogicLib highlighting\r\nChanged nsisTodo list's contents and added it and @Spell to a new nsisCommentGroup","package":"nsis.vim","4":"nsis.vim","src_id":"11882","5":"11882","creation_date":"1260273569","6":"1260273569"},{"0":"2864","vim_version":"5.7","1":"5.7","script_version":"2.45-2","2":"2.45-2","version_comment":"Fixed missing colouring of nsisConstVar (NSIS constants like $DESKTOP)","3":"Fixed missing colouring of nsisConstVar (NSIS constants like $DESKTOP)","package":"nsis.vim","4":"nsis.vim","src_id":"11787","5":"11787","creation_date":"1258932071","6":"1258932071"},{"0":"2864","vim_version":"5.7","1":"5.7","script_version":"2.45-1","2":"2.45-1","version_comment":"Initial upload","3":"Initial upload","package":"nsis.vim","4":"nsis.vim","src_id":"11783","5":"11783","creation_date":"1258892444","6":"1258892444"}]},"2863":{"script_id":"2863","0":"2863","script_name":"GNU as syntax","1":"GNU as syntax","script_type":"syntax","2":"syntax","summary":"GNU as (AT&T) syntax for *86 CPUs","3":"GNU as (AT&T) syntax for *86 CPUs","description":"This file defines a (almost) complete syntax for GNU as assembler.\r\n\r\nMy motivation in writing this was the lack of a complete, working syntax for this\r\ncommon assembler.\r\n\r\nFor now the basic as directives as well as the Intel \/ AMD instruction sets are included.\r\nOpcodes supporting a size suffix are recognised plain as well as suffixed with b\/w\/l\/q.\r\n\r\n== NOTE ON UPDATES\r\n\r\nPlease note that the whole project is now hosted on github - see https:\/\/github.com\/HealsCodes\/vim-gas\/\r\n\r\n\r\nI will try to keep the latest version available on vim.org however there is no 100% guarantee.\r\nGithub offers the flexibility for everyone to easily participate and help me enhance this project.\r\n\r\n== Supported instructions a per version 0.6:\r\n\r\n-- X86 common instruction set (8086 - 686)\r\n-- Katmai Streaming SIMD instructions (SSE -- a.k.a. KNI, XMM, MMX2)\r\n-- Introduced in Deschutes but necessary for SSE support\r\n-- XSAVE group (AVX and extended state)\r\n-- Generic memory operations\r\n-- New MMX instructions introduced in Katmai\r\n-- AMD Enhanced 3DNow! (Athlon) instructions\r\n-- Willamette SSE2 Cacheability Instructions\r\n-- Willamette MMX instructions (SSE2 SIMD Integer Instructions)\r\n-- Willamette Streaming SIMD instructions (SSE2)\r\n-- Prescott New Instructions (SSE3)\r\n-- VMX Instructions\r\n-- Extended Page Tables VMX instructions\r\n-- Tejas New Instructions (SSSE3)\r\n-- AMD SSE4A\r\n-- New instructions in Barcelona\r\n-- Penryn New Instructions (SSE4.1)\r\n-- Nehalem New Instructions (SSE4.2)\r\n-- AMD SSE5 instructions\r\n-- Intel SMX\r\n-- Geode (Cyrix) 3DNow! additions\r\n-- Intel AES instructions\r\n-- Intel AVX AES instructions\r\n-- Intel AVX instructions\r\n-- Intel Carry-Less Multiplication instructions (CLMUL)\r\n-- Intel AVX Carry-Less Multiplication instructions (CLMUL)\r\n-- Intel Fused Multiply-Add instructions (FMA)\r\n-- VIA (Centaur) security instructions\r\n-- AMD XOP, FMA4 and CVT16 instructions (SSE5)\r\n-- Systematic names for the hinting nop instructions\r\n-- AVR\r\n-- ARM (thumb)\r\n\r\nYou can set different highlighting for each set listed above by adding a line like this to you .vimrc:\r\n\r\nhi def link gasOpcodeX86_PENT_SSE  <some_highlighting>\r\n\r\nscreenshot here: http:\/\/skitch.com\/shirkrin\/neq8c\/gnu-as-syntax-for-vim\r\n\r\n== per-file opcode enable \/ disable\r\n\r\nSince version 0.6 it is possible to disable sets of opcodes by either CPU they where introduced in or by their extension name.\r\nThis is done by setting a special variable recognized by gas.vim to the list of disabled opcodes.\r\n\r\nE.g.\r\n\r\n\" globally disable all x86_64 opcodes\r\n:let g:gasDisableOpcodes='x86_64'\r\n\r\n\" disable SSE and SSE2 for this buffer\r\nlet b:gasDisableOpcodes='sse sse2'\r\n\r\nDisabled opcodes will be highlighted as errors.\r\n\r\nrecognized CPU groups:\r\n           186, 286, 386, 3862, 486, 8086, amd, future, ia64, katmai, nehalem,\r\n            p6, pentium_m, pentium, prescott, sandybridge, hasswell, x64, x642, x86_64\r\n\r\nrecognized extension groups:\r\n           base, 3dnow, mmx, mmx2, sse, sse2, sse3, ssse3, sse4.1, sse4.2, sse4a,\r\n           sse5, avx, fma, vmx, avx, avx2\r\n\r\n\r\nI hope this syntax file will be useful to other people \r\n  - but don't blame me if it doesn't suit your needs.\r\n","4":"This file defines a (almost) complete syntax for GNU as assembler.\r\n\r\nMy motivation in writing this was the lack of a complete, working syntax for this\r\ncommon assembler.\r\n\r\nFor now the basic as directives as well as the Intel \/ AMD instruction sets are included.\r\nOpcodes supporting a size suffix are recognised plain as well as suffixed with b\/w\/l\/q.\r\n\r\n== NOTE ON UPDATES\r\n\r\nPlease note that the whole project is now hosted on github - see https:\/\/github.com\/HealsCodes\/vim-gas\/\r\n\r\n\r\nI will try to keep the latest version available on vim.org however there is no 100% guarantee.\r\nGithub offers the flexibility for everyone to easily participate and help me enhance this project.\r\n\r\n== Supported instructions a per version 0.6:\r\n\r\n-- X86 common instruction set (8086 - 686)\r\n-- Katmai Streaming SIMD instructions (SSE -- a.k.a. KNI, XMM, MMX2)\r\n-- Introduced in Deschutes but necessary for SSE support\r\n-- XSAVE group (AVX and extended state)\r\n-- Generic memory operations\r\n-- New MMX instructions introduced in Katmai\r\n-- AMD Enhanced 3DNow! (Athlon) instructions\r\n-- Willamette SSE2 Cacheability Instructions\r\n-- Willamette MMX instructions (SSE2 SIMD Integer Instructions)\r\n-- Willamette Streaming SIMD instructions (SSE2)\r\n-- Prescott New Instructions (SSE3)\r\n-- VMX Instructions\r\n-- Extended Page Tables VMX instructions\r\n-- Tejas New Instructions (SSSE3)\r\n-- AMD SSE4A\r\n-- New instructions in Barcelona\r\n-- Penryn New Instructions (SSE4.1)\r\n-- Nehalem New Instructions (SSE4.2)\r\n-- AMD SSE5 instructions\r\n-- Intel SMX\r\n-- Geode (Cyrix) 3DNow! additions\r\n-- Intel AES instructions\r\n-- Intel AVX AES instructions\r\n-- Intel AVX instructions\r\n-- Intel Carry-Less Multiplication instructions (CLMUL)\r\n-- Intel AVX Carry-Less Multiplication instructions (CLMUL)\r\n-- Intel Fused Multiply-Add instructions (FMA)\r\n-- VIA (Centaur) security instructions\r\n-- AMD XOP, FMA4 and CVT16 instructions (SSE5)\r\n-- Systematic names for the hinting nop instructions\r\n-- AVR\r\n-- ARM (thumb)\r\n\r\nYou can set different highlighting for each set listed above by adding a line like this to you .vimrc:\r\n\r\nhi def link gasOpcodeX86_PENT_SSE  <some_highlighting>\r\n\r\nscreenshot here: http:\/\/skitch.com\/shirkrin\/neq8c\/gnu-as-syntax-for-vim\r\n\r\n== per-file opcode enable \/ disable\r\n\r\nSince version 0.6 it is possible to disable sets of opcodes by either CPU they where introduced in or by their extension name.\r\nThis is done by setting a special variable recognized by gas.vim to the list of disabled opcodes.\r\n\r\nE.g.\r\n\r\n\" globally disable all x86_64 opcodes\r\n:let g:gasDisableOpcodes='x86_64'\r\n\r\n\" disable SSE and SSE2 for this buffer\r\nlet b:gasDisableOpcodes='sse sse2'\r\n\r\nDisabled opcodes will be highlighted as errors.\r\n\r\nrecognized CPU groups:\r\n           186, 286, 386, 3862, 486, 8086, amd, future, ia64, katmai, nehalem,\r\n            p6, pentium_m, pentium, prescott, sandybridge, hasswell, x64, x642, x86_64\r\n\r\nrecognized extension groups:\r\n           base, 3dnow, mmx, mmx2, sse, sse2, sse3, ssse3, sse4.1, sse4.2, sse4a,\r\n           sse5, avx, fma, vmx, avx, avx2\r\n\r\n\r\nI hope this syntax file will be useful to other people \r\n  - but don't blame me if it doesn't suit your needs.\r\n","install_details":"Copy to .vim\/syntax\/ in your home folder.\r\nAdd this line to the end of your file: \r\n\r\n\/* vim: ft=gas :\r\n*\/\r\n","5":"Copy to .vim\/syntax\/ in your home folder.\r\nAdd this line to the end of your file: \r\n\r\n\/* vim: ft=gas :\r\n*\/\r\n","first_name":"Ren\u00c3\u00a9","6":"Ren\u00c3\u00a9","last_name":"K\u00c3\u00b6cher","7":"K\u00c3\u00b6cher","releases":[{"0":"2863","vim_version":"7.0","1":"7.0","script_version":"0.15","2":"0.15","version_comment":"Add various new intel instructions as well as support for AVR and ARM","3":"Add various new intel instructions as well as support for AVR and ARM","package":"gas.vim","4":"gas.vim","src_id":"27822","5":"27822","creation_date":"1638238665","6":"1638238665"},{"0":"2863","vim_version":"7.0","1":"7.0","script_version":"0.9","2":"0.9","version_comment":"Add support for pop{,b,w,l,q} opcodes - credit goes to Hal Ashburner who provided the patch.","3":"Add support for pop{,b,w,l,q} opcodes - credit goes to Hal Ashburner who provided the patch.","package":"gas.vim","4":"gas.vim","src_id":"20660","5":"20660","creation_date":"1376593926","6":"1376593926"},{"0":"2863","vim_version":"6.0","1":"6.0","script_version":"0.8","2":"0.8","version_comment":"Implemented some enhancements suggested by M. Herrmann:\r\n\r\n- add *inc* as keyword (not inc[bwlq])\r\n- add '#' as comment character (without loosing C preprocessor support)\r\n- fix a few mnemonics which don't comply with b\/w\/l\/q suffixes","3":"Implemented some enhancements suggested by M. Herrmann:\r\n\r\n- add *inc* as keyword (not inc[bwlq])\r\n- add '#' as comment character (without loosing C preprocessor support)\r\n- fix a few mnemonics which don't comply with b\/w\/l\/q suffixes","package":"gas.vim","4":"gas.vim","src_id":"11980","5":"11980","creation_date":"1262102509","6":"1262102509"},{"0":"2863","vim_version":"6.0","1":"6.0","script_version":"0.7","2":"0.7","version_comment":"minor tweaks \/ fixes (popfl, stosl, typos in a few registers)","3":"minor tweaks \/ fixes (popfl, stosl, typos in a few registers)","package":"gas.vim","4":"gas.vim","src_id":"11816","5":"11816","creation_date":"1259329066","6":"1259329066"},{"0":"2863","vim_version":"6.0","1":"6.0","script_version":"0.6","2":"0.6","version_comment":"Redone all opcodes - they where generated from a static opcode table and <b,w,l,q> suffixes are now recognized only \r\nfor opcodes that really support them. \r\n\r\nNew feature to disable opcodes (highlighted as Error) by either CPU or extension type. \r\nSet g:gasDisableOpcodes or b:gasDisableOpcodes to a space-separated list of CPU's or Extensions: \r\n\r\nE.g. leg b:gasDisableOpcodes='x86_64 sse sse2' \r\n\r\nCPUs: \r\n           186, 286, 386, 3862, 486, 8086, amd, future, ia64, katmai, nehalem, \r\n            p6, pentium_m, pentium, prescott, sandybridge, x64, x642, x86_64 \r\n\r\nExtensions: \r\n           base, 3dnow, mmx, mmx2, sse, sse2, sse3, ssse3, sse4.1, sse4.2, sse4a, sse5, avx, fma, vmx ","3":"Redone all opcodes - they where generated from a static opcode table and <b,w,l,q> suffixes are now recognized only \r\nfor opcodes that really support them. \r\n\r\nNew feature to disable opcodes (highlighted as Error) by either CPU or extension type. \r\nSet g:gasDisableOpcodes or b:gasDisableOpcodes to a space-separated list of CPU's or Extensions: \r\n\r\nE.g. leg b:gasDisableOpcodes='x86_64 sse sse2' \r\n\r\nCPUs: \r\n           186, 286, 386, 3862, 486, 8086, amd, future, ia64, katmai, nehalem, \r\n            p6, pentium_m, pentium, prescott, sandybridge, x64, x642, x86_64 \r\n\r\nExtensions: \r\n           base, 3dnow, mmx, mmx2, sse, sse2, sse3, ssse3, sse4.1, sse4.2, sse4a, sse5, avx, fma, vmx ","package":"gas.vim","4":"gas.vim","src_id":"11815","5":"11815","creation_date":"1259265270","6":"1259265270"},{"0":"2863","vim_version":"6.0","1":"6.0","script_version":"0.5","2":"0.5","version_comment":"- improved syntax synchronizing\r\n- fixed strings with nested quotes\r\n- support for c-style pre-processor tags (via c.vim)\r\n\r\nKnown Bugs: \r\n\r\nPre-processor tokens require an extra blank line to not                        mix up the following assembler statement. ","3":"- improved syntax synchronizing\r\n- fixed strings with nested quotes\r\n- support for c-style pre-processor tags (via c.vim)\r\n\r\nKnown Bugs: \r\n\r\nPre-processor tokens require an extra blank line to not                        mix up the following assembler statement. ","package":"gas.vim","4":"gas.vim","src_id":"11811","5":"11811","creation_date":"1259221229","6":"1259221229"},{"0":"2863","vim_version":"6.0","1":"6.0","script_version":"0.4","2":"0.4","version_comment":"Fixed an issue where braces and brackets would be shown as part of symbols.","3":"Fixed an issue where braces and brackets would be shown as part of symbols.","package":"gas.vim","4":"gas.vim","src_id":"11780","5":"11780","creation_date":"1258812262","6":"1258812262"}]},"2862":{"script_id":"2862","0":"2862","script_name":"JumpInCode (new update)","1":"JumpInCode (new update)","script_type":"ftplugin","2":"ftplugin","summary":"Cscope and tags plugin , build files in your Current directory","3":"Cscope and tags plugin , build files in your Current directory","description":"我喜欢这个插件,我觉得很方便所以我修改了下感谢zuopeng chen提供的脚本\r\n\r\n此代码修改于http:\/\/www.vim.org\/scripts\/script.php?script_id=2770 也是自动生成tags和cscope,但它生成的文件是在当前目录\/OutDB\/下\r\n\r\n提示：\r\n      请确定了你已安装了ctags和cscope， 如果是windows请把ctags.exe和cscope.exe放到$VIM\\vim7* 目录下。\r\n       ctags 和cscope Win32版： http:\/\/code.google.com\/p\/easy-vim\/ \r\n\r\n\r\n--------------------华丽的分界线------------------\r\n***** 1.03vesion *******\r\n\r\ncommand:\r\n<leader>jc  Generate tags and cscope database from current directory to :\r\n                    生成当前目录的tags和cscope到:\r\n\r\nall OS  \/\/buillding file in Current Directory\r\nCurrentDirectory(当前目录)\/OutDB\/cscope.out,tags\r\n\r\nother command \r\n<leader>jst       list existed tags full name and choose tags\r\n                          列举已存在tags的全路径,选择要使用的tags \r\n<leader>jsc      list existed cscope database full name and choose cscope.out \r\n                          列举已存在cscope的数据库的全路径, 选择要使用的cscope.out \r\n\r\n----------------------------------------------------------\r\n\r\nThanks to zuopeng chen .\r\nthe code change from http:\/\/www.vim.org\/scripts\/script.php?script_id=2770.\r\nalso auto build tags & cacope ,but this script build path at CurrentDirectory\/OutDB in all OS\r\n\r\nAdditional:\r\n        Please insure you have installed ctags and cscope, Win32 Vim puts ctags.exe and cscope.exe in $VIM\\vim7*\r\n\r\n        ctags and cscope for win32 you can download from : http:\/\/code.google.com\/p\/easy-vim\/\r\n\r\nvim default <leader> is \" \\ \"  :P","4":"我喜欢这个插件,我觉得很方便所以我修改了下感谢zuopeng chen提供的脚本\r\n\r\n此代码修改于http:\/\/www.vim.org\/scripts\/script.php?script_id=2770 也是自动生成tags和cscope,但它生成的文件是在当前目录\/OutDB\/下\r\n\r\n提示：\r\n      请确定了你已安装了ctags和cscope， 如果是windows请把ctags.exe和cscope.exe放到$VIM\\vim7* 目录下。\r\n       ctags 和cscope Win32版： http:\/\/code.google.com\/p\/easy-vim\/ \r\n\r\n\r\n--------------------华丽的分界线------------------\r\n***** 1.03vesion *******\r\n\r\ncommand:\r\n<leader>jc  Generate tags and cscope database from current directory to :\r\n                    生成当前目录的tags和cscope到:\r\n\r\nall OS  \/\/buillding file in Current Directory\r\nCurrentDirectory(当前目录)\/OutDB\/cscope.out,tags\r\n\r\nother command \r\n<leader>jst       list existed tags full name and choose tags\r\n                          列举已存在tags的全路径,选择要使用的tags \r\n<leader>jsc      list existed cscope database full name and choose cscope.out \r\n                          列举已存在cscope的数据库的全路径, 选择要使用的cscope.out \r\n\r\n----------------------------------------------------------\r\n\r\nThanks to zuopeng chen .\r\nthe code change from http:\/\/www.vim.org\/scripts\/script.php?script_id=2770.\r\nalso auto build tags & cacope ,but this script build path at CurrentDirectory\/OutDB in all OS\r\n\r\nAdditional:\r\n        Please insure you have installed ctags and cscope, Win32 Vim puts ctags.exe and cscope.exe in $VIM\\vim7*\r\n\r\n        ctags and cscope for win32 you can download from : http:\/\/code.google.com\/p\/easy-vim\/\r\n\r\nvim default <leader> is \" \\ \"  :P","install_details":"$VIM\\vimfiles\\plugin\\JumpInCode_Plus.vim\r\nor\r\n$VIM\\vim7*\\plugin\\JumplnCode_Plus.vim","5":"$VIM\\vimfiles\\plugin\\JumpInCode_Plus.vim\r\nor\r\n$VIM\\vim7*\\plugin\\JumplnCode_Plus.vim","first_name":"Angluca","6":"Angluca","last_name":"Ac","7":"Ac","releases":[{"0":"2862","vim_version":"7.0","1":"7.0","script_version":"1.03","2":"1.03","version_comment":"Fixed BUGs, Get rid of the user variable,it's well","3":"Fixed BUGs, Get rid of the user variable,it's well","package":"JumpInCode_Plus.vim","4":"JumpInCode_Plus.vim","src_id":"11954","5":"11954","creation_date":"1261772796","6":"1261772796"},{"0":"2862","vim_version":"7.0","1":"7.0","script_version":"1.01","2":"1.01","version_comment":"linux and win32 build files in CurrentPath","3":"linux and win32 build files in CurrentPath","package":"JumpInCode_Plus.vim","4":"JumpInCode_Plus.vim","src_id":"11922","5":"11922","creation_date":"1261221923","6":"1261221923"},{"0":"2862","vim_version":"6.0","1":"6.0","script_version":"1.00","2":"1.00","version_comment":"Initial upload","3":"Initial upload","package":"JumpInCode Plus.vim","4":"JumpInCode Plus.vim","src_id":"11778","5":"11778","creation_date":"1258809007","6":"1258809007"}]},"2861":{"script_id":"2861","0":"2861","script_name":"i can't delete this","1":"i can't delete this","script_type":"utility","2":"utility","summary":"i can't delete this","3":"i can't delete this","description":"for people want to find the repository, please visit https:\/\/github.com\/c9s\/hypergit.vim","4":"for people want to find the repository, please visit https:\/\/github.com\/c9s\/hypergit.vim","install_details":"for people want to find the repository, please visit https:\/\/github.com\/c9s\/hypergit.vim","5":"for people want to find the repository, please visit https:\/\/github.com\/c9s\/hypergit.vim","first_name":"Yo-An","6":"Yo-An","last_name":"Lin","7":"Lin","releases":[{"0":"2861","vim_version":"7.2","1":"7.2","script_version":"1.7","2":"1.7","version_comment":"* disable diff cnt for temporary\n(This package is released by VIM::Packager http:\/\/github.com\/c9s\/vim-packager)","3":"* disable diff cnt for temporary\n(This package is released by VIM::Packager http:\/\/github.com\/c9s\/vim-packager)","package":"fastgit-vim-1.7.tar.gz","4":"fastgit-vim-1.7.tar.gz","src_id":"11821","5":"11821","creation_date":"1259347942","6":"1259347942"}]},"2860":{"script_id":"2860","0":"2860","script_name":"prettyprint.vim","1":"prettyprint.vim","script_type":"utility","2":"utility","summary":"Prettyprint vim variables.","3":"Prettyprint vim variables.","description":"*prettyprint* is a Vim plugin to prettyprint vim variable for debug.\r\n\r\nExample:\r\nWhen g:prettyprint_width = 78, you run the following command,\r\n    :PP {'triangular':[3,6,9,12,15],'squares':[1,4,16,25,36],'pentagonal':[1,5,12,22,35]}\r\n\r\nYou get the following display as a result.\r\n    {\r\n      'pentagonal': [1, 5, 12, 22, 35],\r\n      'squares': [1, 4, 16, 25, 36],\r\n      'triangular': [3, 6, 9, 12, 15]\r\n    }\r\n\r\n\r\nExample of usage: You try the following command to view the all global variables.\r\n\r\n    :PP g:\r\n\r\n\r\nLatest Version:\r\nhttps:\/\/github.com\/thinca\/vim-prettyprint","4":"*prettyprint* is a Vim plugin to prettyprint vim variable for debug.\r\n\r\nExample:\r\nWhen g:prettyprint_width = 78, you run the following command,\r\n    :PP {'triangular':[3,6,9,12,15],'squares':[1,4,16,25,36],'pentagonal':[1,5,12,22,35]}\r\n\r\nYou get the following display as a result.\r\n    {\r\n      'pentagonal': [1, 5, 12, 22, 35],\r\n      'squares': [1, 4, 16, 25, 36],\r\n      'triangular': [3, 6, 9, 12, 15]\r\n    }\r\n\r\n\r\nExample of usage: You try the following command to view the all global variables.\r\n\r\n    :PP g:\r\n\r\n\r\nLatest Version:\r\nhttps:\/\/github.com\/thinca\/vim-prettyprint","install_details":"","5":"","first_name":"thinca","6":"thinca","last_name":" ","7":" ","releases":[{"0":"2860","vim_version":"7.2","1":"7.2","script_version":"0.3.2","2":"0.3.2","version_comment":"- Added g:prettyprint_string option.\r\n- Improved Funcref support.","3":"- Added g:prettyprint_string option.\r\n- Improved Funcref support.","package":"vim-prettyprint-0.3.2.zip","4":"vim-prettyprint-0.3.2.zip","src_id":"17102","5":"17102","creation_date":"1324572967","6":"1324572967"},{"0":"2860","vim_version":"7.2","1":"7.2","script_version":"0.3.1","2":"0.3.1","version_comment":"- Added the buffer local version of options.\r\n  - b:prettyprint_indent\r\n  - b:prettyprint_width\r\n- :PrettyPrint accepts \"!\" for saving the output.\r\n","3":"- Added the buffer local version of options.\r\n  - b:prettyprint_indent\r\n  - b:prettyprint_width\r\n- :PrettyPrint accepts \"!\" for saving the output.\r\n","package":"vim-prettyprint-0.3.1.zip","4":"vim-prettyprint-0.3.1.zip","src_id":"13769","5":"13769","creation_date":"1283792768","6":"1283792768"},{"0":"2860","vim_version":"7.2","1":"7.2","script_version":"0.3.0","2":"0.3.0","version_comment":"Initial upload","3":"Initial upload","package":"vim-prettyprint-0.3.0.zip","4":"vim-prettyprint-0.3.0.zip","src_id":"11772","5":"11772","creation_date":"1258737117","6":"1258737117"}]},"2859":{"script_id":"2859","0":"2859","script_name":"grey2","1":"grey2","script_type":"color scheme","2":"color scheme","summary":"dark scheme ","3":"dark scheme ","description":"dark scheme like terminal but not very sharp.\r\nPreview:\r\nhttp:\/\/photo.blog.sina.com.cn\/photo\/5bc27867t78c51c25aefd\r\n\r\nIt\u00e2\u0080\u0098s designed for XPTemplate :\r\nhttp:\/\/www.vim.org\/scripts\/script.php?script_id=2611","4":"dark scheme like terminal but not very sharp.\r\nPreview:\r\nhttp:\/\/photo.blog.sina.com.cn\/photo\/5bc27867t78c51c25aefd\r\n\r\nIt\u00e2\u0080\u0098s designed for XPTemplate :\r\nhttp:\/\/www.vim.org\/scripts\/script.php?script_id=2611","install_details":"copy to ~\/.vim\/colors\/","5":"copy to ~\/.vim\/colors\/","first_name":"drdr","6":"drdr","last_name":"xp","7":"xp","releases":[{"0":"2859","vim_version":"7.0","1":"7.0","script_version":"2","2":"2","version_comment":"add line:   let g:grey2_text_bg = 0   to disable displaying text background color ","3":"add line:   let g:grey2_text_bg = 0   to disable displaying text background color ","package":"grey2.vim","4":"grey2.vim","src_id":"12379","5":"12379","creation_date":"1266049185","6":"1266049185"},{"0":"2859","vim_version":"7.2","1":"7.2","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"grey2.vim","4":"grey2.vim","src_id":"11766","5":"11766","creation_date":"1258688829","6":"1258688829"}]},"2858":{"script_id":"2858","0":"2858","script_name":"textobj-fatpack","1":"textobj-fatpack","script_type":"utility","2":"utility","summary":"Various text objects in single package","3":"Various text objects in single package","description":"*textobj-fatpack* is a Vim plugin to provide many kinds of |text-objects|.  In\r\nother words, this is a meta package which includes the following plugins to\r\nprovide various text objects:\r\n\r\n|textobj-datetime| 0.3.1 (vimscript#2101)    Date and time\r\n|textobj-diff|     0.0.0 (vimscript#2415)    Diff hunk\r\n|textobj-entire|   0.0.1 (vimscript#2610)    Entire buffer\r\n|textobj-fold|     0.1.2 (vimscript#2275)    Folding\r\n|textobj-function| 0.1.0 (vimscript#2619)    Function\r\n|textobj-indent|   0.0.3 (vimscript#2484)    Indented block\r\n|textobj-jabraces| 0.1.1 (vimscript#2276)    Japanese braces\r\n|textobj-lastpat|  0.0.0 (vimscript#2355)    Last search pattern\r\n|textobj-syntax|   0.0.0 (vimscript#2716)    Syntax highlighted item\r\n|textobj-user|     0.3.8 (vimscript#2100)    For your own one\r\n\r\n\r\nRequirements:\r\n- Vim 7.2 or later\r\n\r\nLatest version:\r\nhttp:\/\/github.com\/kana\/vim-textobj-fatpack\r\n\r\nDocument in HTML format:\r\nhttp:\/\/kana.github.com\/config\/vim\/textobj-fatpack.html","4":"*textobj-fatpack* is a Vim plugin to provide many kinds of |text-objects|.  In\r\nother words, this is a meta package which includes the following plugins to\r\nprovide various text objects:\r\n\r\n|textobj-datetime| 0.3.1 (vimscript#2101)    Date and time\r\n|textobj-diff|     0.0.0 (vimscript#2415)    Diff hunk\r\n|textobj-entire|   0.0.1 (vimscript#2610)    Entire buffer\r\n|textobj-fold|     0.1.2 (vimscript#2275)    Folding\r\n|textobj-function| 0.1.0 (vimscript#2619)    Function\r\n|textobj-indent|   0.0.3 (vimscript#2484)    Indented block\r\n|textobj-jabraces| 0.1.1 (vimscript#2276)    Japanese braces\r\n|textobj-lastpat|  0.0.0 (vimscript#2355)    Last search pattern\r\n|textobj-syntax|   0.0.0 (vimscript#2716)    Syntax highlighted item\r\n|textobj-user|     0.3.8 (vimscript#2100)    For your own one\r\n\r\n\r\nRequirements:\r\n- Vim 7.2 or later\r\n\r\nLatest version:\r\nhttp:\/\/github.com\/kana\/vim-textobj-fatpack\r\n\r\nDocument in HTML format:\r\nhttp:\/\/kana.github.com\/config\/vim\/textobj-fatpack.html","install_details":"...","5":"...","first_name":"Kana","6":"Kana","last_name":"Natsuno","7":"Natsuno","releases":[{"0":"2858","vim_version":"7.0","1":"7.0","script_version":"0.0.0","2":"0.0.0","version_comment":"Initial upload","3":"Initial upload","package":"vim-textobj-fatpack-0.0.0.zip","4":"vim-textobj-fatpack-0.0.0.zip","src_id":"11764","5":"11764","creation_date":"1258633139","6":"1258633139"}]},"2857":{"script_id":"2857","0":"2857","script_name":"exjumplist","1":"exjumplist","script_type":"utility","2":"utility","summary":"Extra commands for jumplist","3":"Extra commands for jumplist","description":"*exjumplist* is a Vim plugin to provide extra commands for |jumplist|:\r\n\r\n- Go to the next\/previous position in different buffer.\r\n- Go to the first\/last position in jumplist\r\n\r\n\r\nRequirements:\r\n- Vim 7.2 or later\r\n\r\nLatest version:\r\nhttp:\/\/github.com\/kana\/vim-exjumplist\r\n\r\nDocument in HTML format:\r\nhttp:\/\/kana.github.com\/config\/vim\/exjumplist.html","4":"*exjumplist* is a Vim plugin to provide extra commands for |jumplist|:\r\n\r\n- Go to the next\/previous position in different buffer.\r\n- Go to the first\/last position in jumplist\r\n\r\n\r\nRequirements:\r\n- Vim 7.2 or later\r\n\r\nLatest version:\r\nhttp:\/\/github.com\/kana\/vim-exjumplist\r\n\r\nDocument in HTML format:\r\nhttp:\/\/kana.github.com\/config\/vim\/exjumplist.html","install_details":"...","5":"...","first_name":"Kana","6":"Kana","last_name":"Natsuno","7":"Natsuno","releases":[{"0":"2857","vim_version":"7.0","1":"7.0","script_version":"0.0.0","2":"0.0.0","version_comment":"Initial upload","3":"Initial upload","package":"vim-exjumplist-0.0.0.zip","4":"vim-exjumplist-0.0.0.zip","src_id":"11763","5":"11763","creation_date":"1258628641","6":"1258628641"}]},"2856":{"script_id":"2856","0":"2856","script_name":"vimmpc","1":"vimmpc","script_type":"utility","2":"utility","summary":"Manipulate a running mpd daemon from within vim","3":"Manipulate a running mpd daemon from within vim","description":"Uploading this old utility due to popular demand (and to promote interest).\r\n\r\nAbout\r\n--------\r\n\r\nVimmpc provides functionality for manipulating http:\/\/www.musicpd.org\/\r\nfrom within Vim.\r\n\r\nMain site: http:\/\/gavin.brokentrain.net\/projects\/vimmpc\/","4":"Uploading this old utility due to popular demand (and to promote interest).\r\n\r\nAbout\r\n--------\r\n\r\nVimmpc provides functionality for manipulating http:\/\/www.musicpd.org\/\r\nfrom within Vim.\r\n\r\nMain site: http:\/\/gavin.brokentrain.net\/projects\/vimmpc\/","install_details":"Download and extract straight to vim directory or by symlinking:-\r\n\r\n  tar xzf vimmpc-(revision).tar.gz\r\n  cd ~\/.vim\/plugin\r\n  ln -s \/path\/to\/vimmpc\/vimmpc.vim\r\n  ln -s \/path\/to\/vimmpc\/vimmpc.py\r\n\r\nAnd finally:\r\n  $ vim -c 'MPC' to launch. (or :MPC from within vim)","5":"Download and extract straight to vim directory or by symlinking:-\r\n\r\n  tar xzf vimmpc-(revision).tar.gz\r\n  cd ~\/.vim\/plugin\r\n  ln -s \/path\/to\/vimmpc\/vimmpc.vim\r\n  ln -s \/path\/to\/vimmpc\/vimmpc.py\r\n\r\nAnd finally:\r\n  $ vim -c 'MPC' to launch. (or :MPC from within vim)","first_name":"Gavin","6":"Gavin","last_name":"Gilmour","7":"Gilmour","releases":[{"0":"2856","vim_version":"7.0","1":"7.0","script_version":"20070410","2":"20070410","version_comment":"Initial upload","3":"Initial upload","package":"vimmpc-20070410.tar.gz","4":"vimmpc-20070410.tar.gz","src_id":"11762","5":"11762","creation_date":"1258628058","6":"1258628058"}]},"2855":{"script_id":"2855","0":"2855","script_name":"github theme","1":"github theme","script_type":"color scheme","2":"color scheme","summary":"A gvim colorscheme based on github's syntax highlighting","3":"A gvim colorscheme based on github's syntax highlighting","description":"NOTE: An updated version of this colorscheme (with 256 color terminal support and a standard vim plugin directory layout) can be found at https:\/\/github.com\/acarapetis\/vim-colors-github\r\n\r\nScreenshot: http:\/\/i.imgur.com\/LJXdy.png\r\nDiffsplit screenshot: http:\/\/i.imgur.com\/RKtVD.png\r\n\r\nThis is a port of github's lovely light-background syntax highlighting theme.  I tried to make it as comprehensive as possible; it should look good with:\r\n - Completion menus\r\n - Diffsplit\r\n - STL highlighting\r\n\r\nIt's not an exact replica, but it's pretty close - enjoy!","4":"NOTE: An updated version of this colorscheme (with 256 color terminal support and a standard vim plugin directory layout) can be found at https:\/\/github.com\/acarapetis\/vim-colors-github\r\n\r\nScreenshot: http:\/\/i.imgur.com\/LJXdy.png\r\nDiffsplit screenshot: http:\/\/i.imgur.com\/RKtVD.png\r\n\r\nThis is a port of github's lovely light-background syntax highlighting theme.  I tried to make it as comprehensive as possible; it should look good with:\r\n - Completion menus\r\n - Diffsplit\r\n - STL highlighting\r\n\r\nIt's not an exact replica, but it's pretty close - enjoy!","install_details":"Copy github.vim to ~\/.vim\/colors\/","5":"Copy github.vim to ~\/.vim\/colors\/","first_name":"Anthony","6":"Anthony","last_name":"Carapetis","7":"Carapetis","releases":[{"0":"2855","vim_version":"7.0","1":"7.0","script_version":"1.2","2":"1.2","version_comment":"croaky@github's version - includes 256 color support","3":"croaky@github's version - includes 256 color support","package":"github.vim","4":"github.vim","src_id":"23147","5":"23147","creation_date":"1428467274","6":"1428467274"},{"0":"2855","vim_version":"7.0","1":"7.0","script_version":"1.1","2":"1.1","version_comment":"Some tweaks from Steffen Siering:\r\n * changed cursor to dark matte gray-blue\r\n * darkened StatusLine, StatusLineNC and VerticalSplit a little\r\n * added some more elements to Syntax groups to adjust highlighting more to githubs style, thus some languages \"look\" more concise (like Haskell, Javascript, C, Asm...)","3":"Some tweaks from Steffen Siering:\r\n * changed cursor to dark matte gray-blue\r\n * darkened StatusLine, StatusLineNC and VerticalSplit a little\r\n * added some more elements to Syntax groups to adjust highlighting more to githubs style, thus some languages \"look\" more concise (like Haskell, Javascript, C, Asm...)","package":"github.vim","4":"github.vim","src_id":"12456","5":"12456","creation_date":"1266752202","6":"1266752202"},{"0":"2855","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"github.vim","4":"github.vim","src_id":"11742","5":"11742","creation_date":"1258427137","6":"1258427137"}]},"2854":{"script_id":"2854","0":"2854","script_name":"go.vim","1":"go.vim","script_type":"syntax","2":"syntax","summary":"Syntax file for the Go programming language","3":"Syntax file for the Go programming language","description":"Syntax file for the Go programming language.\r\n\r\nNOTE: There is already a syntax file in the go repository. You can find it under $GOROOT\/misc\/vim\/go.vim","4":"Syntax file for the Go programming language.\r\n\r\nNOTE: There is already a syntax file in the go repository. You can find it under $GOROOT\/misc\/vim\/go.vim","install_details":"Copy it to ~\/.vim\/syntax","5":"Copy it to ~\/.vim\/syntax","first_name":"David","6":"David","last_name":"Daub","7":"Daub","releases":[{"0":"2854","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"go.vim","4":"go.vim","src_id":"11735","5":"11735","creation_date":"1258323726","6":"1258323726"}]},"2853":{"script_id":"2853","0":"2853","script_name":"go.vim","1":"go.vim","script_type":"syntax","2":"syntax","summary":"Syntax file for the Go programming language","3":"Syntax file for the Go programming language","description":"Syntax file for the Go programming language.\r\n\r\nNOTE: There is already a syntax file in the go repository. You can find it under $GOROOT\/misc\/vim\/go.vim","4":"Syntax file for the Go programming language.\r\n\r\nNOTE: There is already a syntax file in the go repository. You can find it under $GOROOT\/misc\/vim\/go.vim","install_details":"Copy it to ~\/.vim\/syntax","5":"Copy it to ~\/.vim\/syntax","first_name":"David","6":"David","last_name":"Daub","7":"Daub","releases":[{"0":"2853","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"go.vim","4":"go.vim","src_id":"11734","5":"11734","creation_date":"1258323591","6":"1258323591"}]},"2852":{"script_id":"2852","0":"2852","script_name":"perlomni.vim","1":"perlomni.vim","script_type":"ftplugin","2":"ftplugin","summary":"perl omni completion  (perl-completion.vim)","3":"perl omni completion  (perl-completion.vim)","description":"This perl omni completion support basic Moose syntax, variable name (array , hash .. ) completion , class method , object method completion ...etc.\r\n\r\nSee screencast:\r\nhttp:\/\/www.youtube.com\/watch?v=hZ7871WcIv0\r\n\r\n\r\nplease refers to:\r\nhttp:\/\/github.com\/c9s\/perlomni.vim\r\n\r\n","4":"This perl omni completion support basic Moose syntax, variable name (array , hash .. ) completion , class method , object method completion ...etc.\r\n\r\nSee screencast:\r\nhttp:\/\/www.youtube.com\/watch?v=hZ7871WcIv0\r\n\r\n\r\nplease refers to:\r\nhttp:\/\/github.com\/c9s\/perlomni.vim\r\n\r\n","install_details":"just run:\r\n\r\n      make install\r\n\r\nplease refers to:\r\n\r\nhttp:\/\/github.com\/c9s\/perl-completion.vim\r\n","5":"just run:\r\n\r\n      make install\r\n\r\nplease refers to:\r\n\r\nhttp:\/\/github.com\/c9s\/perl-completion.vim\r\n","first_name":"Yo-An","6":"Yo-An","last_name":"Lin","7":"Lin","releases":[{"0":"2852","vim_version":"7.0","1":"7.0","script_version":"2.42","2":"2.42","version_comment":"add DBIx::Class dictinoary.","3":"add DBIx::Class dictinoary.","package":"perl-completion.vim-2.42.tar.gz","4":"perl-completion.vim-2.42.tar.gz","src_id":"13656","5":"13656","creation_date":"1282588589","6":"1282588589"},{"0":"2852","vim_version":"7.0","1":"7.0","script_version":"2.4","2":"2.4","version_comment":"Fix bugs.","3":"Fix bugs.","package":"perl-completion.vim-2.4.tar.gz","4":"perl-completion.vim-2.4.tar.gz","src_id":"12741","5":"12741","creation_date":"1269939835","6":"1269939835"},{"0":"2852","vim_version":"7.0","1":"7.0","script_version":"2.3","2":"2.3","version_comment":"Fix issues, use Cache. and support base class function completion.","3":"Fix issues, use Cache. and support base class function completion.","package":"perl-completion.vim-2.3.tar.gz","4":"perl-completion.vim-2.3.tar.gz","src_id":"12737","5":"12737","creation_date":"1269902207","6":"1269902207"},{"0":"2852","vim_version":"7.0","1":"7.0","script_version":"2.1","2":"2.1","version_comment":"support Moose! and it's extendible","3":"support Moose! and it's extendible","package":"perl-completion.vim-2.1.tar.gz","4":"perl-completion.vim-2.1.tar.gz","src_id":"12718","5":"12718","creation_date":"1269729635","6":"1269729635"},{"0":"2852","vim_version":"7.0","1":"7.0","script_version":"1.71","2":"1.71","version_comment":"improve completion performance.\n(released by VIM::Packager http:\/\/github.com\/c9s\/vim-packager)\n","3":"improve completion performance.\n(released by VIM::Packager http:\/\/github.com\/c9s\/vim-packager)\n","package":"perl-completion-vim-1.71.tar.gz","4":"perl-completion-vim-1.71.tar.gz","src_id":"12054","5":"12054","creation_date":"1263130198","6":"1263130198"},{"0":"2852","vim_version":"7.0","1":"7.0","script_version":"1.6","2":"1.6","version_comment":"perl completion comes with context completion now.\n","3":"perl completion comes with context completion now.\n","package":"perl-completion-vim-1.6.tar.gz","4":"perl-completion-vim-1.6.tar.gz","src_id":"11812","5":"11812","creation_date":"1259222787","6":"1259222787"},{"0":"2852","vim_version":"7.0","1":"7.0","script_version":"1.3","2":"1.3","version_comment":"cache functions\n","3":"cache functions\n","package":"perl-completion-vim-1.3.tar.gz","4":"perl-completion-vim-1.3.tar.gz","src_id":"11757","5":"11757","creation_date":"1258572653","6":"1258572653"},{"0":"2852","vim_version":"7.0","1":"7.0","script_version":"0.5","2":"0.5","version_comment":"use omnifunc to bind\n","3":"use omnifunc to bind\n","package":"perl-completion-vim-0.5.tar.gz","4":"perl-completion-vim-0.5.tar.gz","src_id":"11727","5":"11727","creation_date":"1258183670","6":"1258183670"}]},"2851":{"script_id":"2851","0":"2851","script_name":"Speedware","1":"Speedware","script_type":"syntax","2":"syntax","summary":"Syntax Highlighting for Speedware","3":"Syntax Highlighting for Speedware","description":"Highlights syntax for Speedware\/Autobahn II code. Works for viewing spec files and any txt file with the .spw extension. Also allows for syntax highlighting if Vim is set as external editor in Autobahn.\r\n\r\nThis is a very rough file, improvements are welcome. I may also be the only one that would actually use this. If you like it or want something changed, please email me at patrick dot rubbs dot regan at gmail dot com.","4":"Highlights syntax for Speedware\/Autobahn II code. Works for viewing spec files and any txt file with the .spw extension. Also allows for syntax highlighting if Vim is set as external editor in Autobahn.\r\n\r\nThis is a very rough file, improvements are welcome. I may also be the only one that would actually use this. If you like it or want something changed, please email me at patrick dot rubbs dot regan at gmail dot com.","install_details":"Install in syntax folder.","5":"Install in syntax folder.","first_name":"Patrick","6":"Patrick","last_name":"Regan","7":"Regan","releases":[{"0":"2851","vim_version":"7.0","1":"7.0","script_version":".1.1","2":".1.1","version_comment":"First upload was made on MS-WIN. This uses Unix EOL's so that there is no problems trying to source it in different environments. Also cleaned up bad tabs, do to some custom editor settings I had.","3":"First upload was made on MS-WIN. This uses Unix EOL's so that there is no problems trying to source it in different environments. Also cleaned up bad tabs, do to some custom editor settings I had.","package":"spw.vim","4":"spw.vim","src_id":"11724","5":"11724","creation_date":"1258144693","6":"1258144693"},{"0":"2851","vim_version":"7.2","1":"7.2","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"spw.vim","4":"spw.vim","src_id":"11723","5":"11723","creation_date":"1258137981","6":"1258137981"}]},"2850":{"script_id":"2850","0":"2850","script_name":"FindInNERDTree","1":"FindInNERDTree","script_type":"utility","2":"utility","summary":"Expands NERDTree to file in current buffer","3":"Expands NERDTree to file in current buffer","description":"!!! THE CURRENT VERSION OF NERDTree ALREADY HAS THIS FEATURE !!!\r\n\r\nI.e. you don't need this plugin :)\r\n\r\n---\r\n\r\nFindInNERDTree is a NERDTree vimscript #1658 plugin that recursively opens the tree to the location of the current buffer. If you jump around source code using ctags, trying to open the tree to where you are can be quite a chore. With this script you can hit a key combination and have the tree immediately pop open to your location.\r\n\r\nThe script is also hosted on GitHub:\r\nhttp:\/\/github.com\/dmcinnes\/FindInNERDTree","4":"!!! THE CURRENT VERSION OF NERDTree ALREADY HAS THIS FEATURE !!!\r\n\r\nI.e. you don't need this plugin :)\r\n\r\n---\r\n\r\nFindInNERDTree is a NERDTree vimscript #1658 plugin that recursively opens the tree to the location of the current buffer. If you jump around source code using ctags, trying to open the tree to where you are can be quite a chore. With this script you can hit a key combination and have the tree immediately pop open to your location.\r\n\r\nThe script is also hosted on GitHub:\r\nhttp:\/\/github.com\/dmcinnes\/FindInNERDTree","install_details":"Requires version 4.0.0 of NERDTree vimscript #1658!  If you're getting error messages you probably need to update!\r\n\r\nDrop the script into the NERDTree plugin folder:\r\n.vim\/plugin\/nerdtree_plugin\r\n\r\nAdd a mapping to your .vimrc file, e.g. this fires it off with Control-f:\r\nnnoremap <silent> <C-f> :call FindInNERDTree()<CR>\r\n","5":"Requires version 4.0.0 of NERDTree vimscript #1658!  If you're getting error messages you probably need to update!\r\n\r\nDrop the script into the NERDTree plugin folder:\r\n.vim\/plugin\/nerdtree_plugin\r\n\r\nAdd a mapping to your .vimrc file, e.g. this fires it off with Control-f:\r\nnnoremap <silent> <C-f> :call FindInNERDTree()<CR>\r\n","first_name":"Doug","6":"Doug","last_name":"McInnes","7":"McInnes","releases":[{"0":"2850","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"FindInNERDTree.vim","4":"FindInNERDTree.vim","src_id":"11722","5":"11722","creation_date":"1258134714","6":"1258134714"}]},"2849":{"script_id":"2849","0":"2849","script_name":"color codes SQL keywords from Oracle 11g","1":"color codes SQL keywords from Oracle 11g","script_type":"syntax","2":"syntax","summary":"code update from Alvin Steele","3":"code update from Alvin Steele","description":"Update more function from Alvin Steele","4":"Update more function from Alvin Steele","install_details":"Install in the Vim\\vimfiles\\syntax directory","5":"Install in the Vim\\vimfiles\\syntax directory","first_name":"Roy","6":"Roy","last_name":"Chan","7":"Chan","releases":[{"0":"2849","vim_version":"6.0","1":"6.0","script_version":"7.2","2":"7.2","version_comment":"Initial upload","3":"Initial upload","package":"sqloracle.vim","4":"sqloracle.vim","src_id":"11718","5":"11718","creation_date":"1258099093","6":"1258099093"}]},"2848":{"script_id":"2848","0":"2848","script_name":"Script Walker","1":"Script Walker","script_type":"utility","2":"utility","summary":"Walks up and down the file for you","3":"Walks up and down the file for you","description":"On pressing of F12 key starts the cursor walking to the top and then bottom of the file. Rate sate by updatetime. If it's too slow for you put set ut=1000 somewhere in you vimrc, that will make it walk every second. Press F11 to switch direction. (Simply change the mappings if you'd like to use different keys.)\r\n\r\nWorks very will with \"Changing Colour\" script. (http:\/\/www.vim.org\/scripts\/script.php?script_id=2658). Coding will now never be boring again.","4":"On pressing of F12 key starts the cursor walking to the top and then bottom of the file. Rate sate by updatetime. If it's too slow for you put set ut=1000 somewhere in you vimrc, that will make it walk every second. Press F11 to switch direction. (Simply change the mappings if you'd like to use different keys.)\r\n\r\nWorks very will with \"Changing Colour\" script. (http:\/\/www.vim.org\/scripts\/script.php?script_id=2658). Coding will now never be boring again.","install_details":"Paste this somewhere in your vimrc. It's clearly marked.","5":"Paste this somewhere in your vimrc. It's clearly marked.","first_name":"Paul","6":"Paul","last_name":"Contreras","7":"Contreras","releases":[{"0":"2848","vim_version":"6.0","1":"6.0","script_version":"1.2","2":"1.2","version_comment":"Corrected the message which incorrectly reported the walking direction when you switch walking on as the wrong way.","3":"Corrected the message which incorrectly reported the walking direction when you switch walking on as the wrong way.","package":"script-walker.vim","4":"script-walker.vim","src_id":"11699","5":"11699","creation_date":"1257781485","6":"1257781485"},{"0":"2848","vim_version":"6.0","1":"6.0","script_version":"1.1","2":"1.1","version_comment":"Deleted a redundant StopWalking() function, added a new map to change walking direction, made the prompts more informative.\r\n","3":"Deleted a redundant StopWalking() function, added a new map to change walking direction, made the prompts more informative.\r\n","package":"script-walker.vim","4":"script-walker.vim","src_id":"11696","5":"11696","creation_date":"1257761858","6":"1257761858"},{"0":"2848","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"script-walker.vim","4":"script-walker.vim","src_id":"11689","5":"11689","creation_date":"1257711242","6":"1257711242"}]},"2847":{"script_id":"2847","0":"2847","script_name":"pod-helper.vim","1":"pod-helper.vim","script_type":"ftplugin","2":"ftplugin","summary":"perl pod helpers","3":"perl pod helpers","description":"please refer to:\r\n\r\nhttp:\/\/github.com\/c9s\/pod-helper.vim","4":"please refer to:\r\n\r\nhttp:\/\/github.com\/c9s\/pod-helper.vim","install_details":"","5":"","first_name":"Yo-An","6":"Yo-An","last_name":"Lin","7":"Lin","releases":[{"0":"2847","vim_version":"7.2","1":"7.2","script_version":"0.3","2":"0.3","version_comment":"new release.\n\nthis package is auto-released by VIM::Packager.\n","3":"new release.\n\nthis package is auto-released by VIM::Packager.\n","package":"pod-helper-vim-0.3.tar.gz","4":"pod-helper-vim-0.3.tar.gz","src_id":"11810","5":"11810","creation_date":"1259215470","6":"1259215470"},{"0":"2847","vim_version":"7.2","1":"7.2","script_version":"0.2","2":"0.2","version_comment":"update\n","3":"update\n","package":"pod-helper-vim-0.2.tar.gz","4":"pod-helper-vim-0.2.tar.gz","src_id":"11759","5":"11759","creation_date":"1258574968","6":"1258574968"},{"0":"2847","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"pod-helper-vim-0.1.tar.gz","4":"pod-helper-vim-0.1.tar.gz","src_id":"11688","5":"11688","creation_date":"1257707389","6":"1257707389"}]},"2846":{"script_id":"2846","0":"2846","script_name":"haskellFold","1":"haskellFold","script_type":"ftplugin","2":"ftplugin","summary":"Provide a foldexpr function which give nice folding for haskell files.","3":"Provide a foldexpr function which give nice folding for haskell files.","description":"Provide a better folding for haskell file. The folded lines are transformed\r\nto display the type signature (if any) of the function, providing a great\r\noverview of your file content.\r\n\r\nYou can see some screenshot at http:\/\/twinside.github.com\/vim-haskellFold\/ \r\nGitHub repository : https:\/\/github.com\/Twinside\/vim-haskellFold\r\n","4":"Provide a better folding for haskell file. The folded lines are transformed\r\nto display the type signature (if any) of the function, providing a great\r\noverview of your file content.\r\n\r\nYou can see some screenshot at http:\/\/twinside.github.com\/vim-haskellFold\/ \r\nGitHub repository : https:\/\/github.com\/Twinside\/vim-haskellFold\r\n","install_details":"Drop the file in ~\/.vim\/plugin or ~\/vimfiles\/plugin folder, or if you\r\nuse pathogen into the ~\/.vim\/bundle\/vim-haskellFold or\r\n~\/vimfiles\/bundle\/vim-haskellFold","5":"Drop the file in ~\/.vim\/plugin or ~\/vimfiles\/plugin folder, or if you\r\nuse pathogen into the ~\/.vim\/bundle\/vim-haskellFold or\r\n~\/vimfiles\/bundle\/vim-haskellFold","first_name":"Vincent","6":"Vincent","last_name":"B","7":"B","releases":[{"0":"2846","vim_version":"7.2","1":"7.2","script_version":"1.2","2":"1.2","version_comment":"Reacting to file type instead of file extension ","3":"Reacting to file type instead of file extension ","package":"haskellFold.zip","4":"haskellFold.zip","src_id":"15114","5":"15114","creation_date":"1298586647","6":"1298586647"},{"0":"2846","vim_version":"7.2","1":"7.2","script_version":"1.1","2":"1.1","version_comment":"Showing function signature in folded text","3":"Showing function signature in folded text","package":"haskellFold.vim","4":"haskellFold.vim","src_id":"14930","5":"14930","creation_date":"1296505643","6":"1296505643"}]},"2845":{"script_id":"2845","0":"2845","script_name":"ywchaos","1":"ywchaos","script_type":"utility","2":"utility","summary":"Journal taking and diary making, to record all the chaos of your life :)","3":"Journal taking and diary making, to record all the chaos of your life :)","description":"It's at the very early stage. If you feel the script is useful but still not so convenient in the journal taking and chaos orgnizing with vim in KISS way, any feedback is welcome, if you have thoughts on improvement, any advice is appreciated! My email is:\r\n\r\n        ywupub AT gmail DOT com\r\n\r\n1. Journal recording.\r\n\r\nHit the key <Leader>n (<Leader> normally means \\ on your keyboard if you haven't changed the <Leader> definition.) to create a new journal entry. ywchaos will insert a new entry with timestamp under today's datestamp for you.\r\n\r\n2. Tag support.\r\n\r\nyou can add a tag with the format of \"@tag\"(Without the double quotes) at anywhere you want in a file, or use \"@tag1|tag2\" for creating multi-tags, you can also use \"@tag:subtag\" to define sub-tags. <tab> can be used for autocompletion after '@', '|' or ':'.\r\nAfter a \"@tag\" has been defined, next time you edit ywchaos file, ywchaos will add the \"tag\" to TAGS list region which is on the very first part of the file. You can also use <Leader><C-l> to reflesh the TAGS list region manually.\r\n\r\n(subtag support is experimental, not so convenient for subtag adding at present, you much create tag then :subtag for every subtag.)\r\n\r\n3. Folding & highlighting & picture supporting.\r\n\r\nywchaos folds the file according to the datestamp[mm\/dd\/yyyy], the timestamp[hh:mm:ss], and the snip. Just a few highlightings(tags, journal entries) for ywchaos itself are supported at present, ywchaos is to manage the..., chaos, so I've no idea which stuffs should be highlighted, if you have a good advice, please let me know.\r\n\r\nBUT great news is, you can insert any other different filetypes of snip as you like, and use their syntaxs to hightlight(if they exists), so ywchaos can actually support all highlightings as vim supports! Only syntax is supported, not indentation. I don't know if filetype's indentation can be integrated in one file, if you know, please let me know.\r\n\r\nywchaos makes the insertion of picture is easy, you can hit <Leader>i, select the html tag, then use the auto completion to insert a <img src=> tag(auto-completion for file name after '=' is supported), then you can rename ywchaos file from foo.ywchaos to foo.html, then see the pictures in your browser.\r\n\r\nSpecial note for txtfmt users: you can use set ft=ywchaos.txtfmt, instead of simply ft=ywchaos to make ywchaos and txtfmt[http:\/\/www.vim.org\/scripts\/script.php?script_id=2208] work together. Thanks Brett Stahlman for such nice script to turn vim into a word processor :) You could go to http:\/\/txtfmt.webs.com\/ywchaos.htm for the screenshots!\r\n\r\n4. keybinding:\r\n\r\n<Leader>n          Create a new journal entry with the format of \"$datestamp\\n$timestamp\" and start editing.\r\n\r\n<Leader>i          ywchaos will prompt you to insert html tags or other filetype of snips as you like(auto-completion is supported), and use the corresponding syntax to highlight the html tag or snip region.\r\n\r\n<Tab>       When on TAGS list region, unfolds all the entries which have the tag under the cursor, another <Tab> will restore to old fold way, otherwise do folding\/unfolding toggling. When in insert mode, <tab> will try to complete the tag name after '@' or '|'.\r\n\r\n<Leader><C-l>      Refresh the TAGS list region manually.\r\n\r\n<C-]>       To vimgrep the tag(auto-completion is supported) for current file.\r\n\r\n5. A sample test.ywchaos(Trick: you can name it to test.htm to view the picture):\r\n\r\n------------------------------------------------\r\n<meta http-equiv=\"Content-Type\" content=\"text\/html; charset=utf-8\"\/>\r\n<pre style=\"word-wrap: break-word; white-space: pre-wrap; white-space: -moz-pre-wrap\" >\r\n<TAGS>\r\nChinese \r\nProgramming      C\r\nvim              ywchaos\r\n中文 \r\n<\/TAGS>\r\n\r\nLogo pic:\r\n<img src=http:\/\/www.google.com\/intl\/en_ALL\/images\/logo.gif >\r\n\r\n11\/18\/2009\r\n22:40:40 @中文|Chinese\r\n这是中文测试. This is a test for Chinese.\r\n11\/08\/2009 \r\n15:52:00 @vim:ywchaos \r\nI've created a new ywchaos entry in vim. \r\nIt's not so good, I'll email developer to improve it! \r\n\r\nFollowing the a C snip that I'm learning for programming! @Programming:C \r\n<BEGINSNIP=c> \r\n#include <stdio.h> \r\n\/* Just for example. *\/\r\nmain() \r\n{ \r\n    int i; \r\n    printf(\"Hello, ywchaos!\\n\"); \r\n} \r\n<ENDSNIP=c> \r\n\r\nvim:ft=ywchaos:\r\n------------------------------------------------\r\n\r\n6. Thanks:\r\n\r\nChristian Brabandt for the help with the function that gets tags in file.\r\nXbeta for the inspiration of html tag support[http:\/\/xbeta.info\/pre-txt.htm]","4":"It's at the very early stage. If you feel the script is useful but still not so convenient in the journal taking and chaos orgnizing with vim in KISS way, any feedback is welcome, if you have thoughts on improvement, any advice is appreciated! My email is:\r\n\r\n        ywupub AT gmail DOT com\r\n\r\n1. Journal recording.\r\n\r\nHit the key <Leader>n (<Leader> normally means \\ on your keyboard if you haven't changed the <Leader> definition.) to create a new journal entry. ywchaos will insert a new entry with timestamp under today's datestamp for you.\r\n\r\n2. Tag support.\r\n\r\nyou can add a tag with the format of \"@tag\"(Without the double quotes) at anywhere you want in a file, or use \"@tag1|tag2\" for creating multi-tags, you can also use \"@tag:subtag\" to define sub-tags. <tab> can be used for autocompletion after '@', '|' or ':'.\r\nAfter a \"@tag\" has been defined, next time you edit ywchaos file, ywchaos will add the \"tag\" to TAGS list region which is on the very first part of the file. You can also use <Leader><C-l> to reflesh the TAGS list region manually.\r\n\r\n(subtag support is experimental, not so convenient for subtag adding at present, you much create tag then :subtag for every subtag.)\r\n\r\n3. Folding & highlighting & picture supporting.\r\n\r\nywchaos folds the file according to the datestamp[mm\/dd\/yyyy], the timestamp[hh:mm:ss], and the snip. Just a few highlightings(tags, journal entries) for ywchaos itself are supported at present, ywchaos is to manage the..., chaos, so I've no idea which stuffs should be highlighted, if you have a good advice, please let me know.\r\n\r\nBUT great news is, you can insert any other different filetypes of snip as you like, and use their syntaxs to hightlight(if they exists), so ywchaos can actually support all highlightings as vim supports! Only syntax is supported, not indentation. I don't know if filetype's indentation can be integrated in one file, if you know, please let me know.\r\n\r\nywchaos makes the insertion of picture is easy, you can hit <Leader>i, select the html tag, then use the auto completion to insert a <img src=> tag(auto-completion for file name after '=' is supported), then you can rename ywchaos file from foo.ywchaos to foo.html, then see the pictures in your browser.\r\n\r\nSpecial note for txtfmt users: you can use set ft=ywchaos.txtfmt, instead of simply ft=ywchaos to make ywchaos and txtfmt[http:\/\/www.vim.org\/scripts\/script.php?script_id=2208] work together. Thanks Brett Stahlman for such nice script to turn vim into a word processor :) You could go to http:\/\/txtfmt.webs.com\/ywchaos.htm for the screenshots!\r\n\r\n4. keybinding:\r\n\r\n<Leader>n          Create a new journal entry with the format of \"$datestamp\\n$timestamp\" and start editing.\r\n\r\n<Leader>i          ywchaos will prompt you to insert html tags or other filetype of snips as you like(auto-completion is supported), and use the corresponding syntax to highlight the html tag or snip region.\r\n\r\n<Tab>       When on TAGS list region, unfolds all the entries which have the tag under the cursor, another <Tab> will restore to old fold way, otherwise do folding\/unfolding toggling. When in insert mode, <tab> will try to complete the tag name after '@' or '|'.\r\n\r\n<Leader><C-l>      Refresh the TAGS list region manually.\r\n\r\n<C-]>       To vimgrep the tag(auto-completion is supported) for current file.\r\n\r\n5. A sample test.ywchaos(Trick: you can name it to test.htm to view the picture):\r\n\r\n------------------------------------------------\r\n<meta http-equiv=\"Content-Type\" content=\"text\/html; charset=utf-8\"\/>\r\n<pre style=\"word-wrap: break-word; white-space: pre-wrap; white-space: -moz-pre-wrap\" >\r\n<TAGS>\r\nChinese \r\nProgramming      C\r\nvim              ywchaos\r\n中文 \r\n<\/TAGS>\r\n\r\nLogo pic:\r\n<img src=http:\/\/www.google.com\/intl\/en_ALL\/images\/logo.gif >\r\n\r\n11\/18\/2009\r\n22:40:40 @中文|Chinese\r\n这是中文测试. This is a test for Chinese.\r\n11\/08\/2009 \r\n15:52:00 @vim:ywchaos \r\nI've created a new ywchaos entry in vim. \r\nIt's not so good, I'll email developer to improve it! \r\n\r\nFollowing the a C snip that I'm learning for programming! @Programming:C \r\n<BEGINSNIP=c> \r\n#include <stdio.h> \r\n\/* Just for example. *\/\r\nmain() \r\n{ \r\n    int i; \r\n    printf(\"Hello, ywchaos!\\n\"); \r\n} \r\n<ENDSNIP=c> \r\n\r\nvim:ft=ywchaos:\r\n------------------------------------------------\r\n\r\n6. Thanks:\r\n\r\nChristian Brabandt for the help with the function that gets tags in file.\r\nXbeta for the inspiration of html tag support[http:\/\/xbeta.info\/pre-txt.htm]","install_details":"1. Unzip(tar jxvf) ywchaos.tar.bz2 into your ~\/.vim\/(or vimfiles\/ when on windows).\r\n\r\nywchaos has the following files:\r\n\r\n    plugin\/ywchaos.vim\r\n    ftplugin\/ywchaos.vim\r\n    syntax\/ywchaos.vim\r\n\r\n2. Create a new file with a line at the very end of the file:\r\n\r\n    vim:ft=ywchaos:\r\n\r\n3. That's all. Now close the file then re-open it. If modeline is annoying, you can add one line in your ~\/.vimrc:\r\n\r\n    au BufRead,BufNewFile *.ywchaos set ft=ywchaos\r\n\r\nThen next time when you want to create a new ywchaos file, named it with foo.ywchaos is enough.","5":"1. Unzip(tar jxvf) ywchaos.tar.bz2 into your ~\/.vim\/(or vimfiles\/ when on windows).\r\n\r\nywchaos has the following files:\r\n\r\n    plugin\/ywchaos.vim\r\n    ftplugin\/ywchaos.vim\r\n    syntax\/ywchaos.vim\r\n\r\n2. Create a new file with a line at the very end of the file:\r\n\r\n    vim:ft=ywchaos:\r\n\r\n3. That's all. Now close the file then re-open it. If modeline is annoying, you can add one line in your ~\/.vimrc:\r\n\r\n    au BufRead,BufNewFile *.ywchaos set ft=ywchaos\r\n\r\nThen next time when you want to create a new ywchaos file, named it with foo.ywchaos is enough.","first_name":"Yue","6":"Yue","last_name":"Wu","7":"Wu","releases":[{"0":"2845","vim_version":"7.0","1":"7.0","script_version":"0.14","2":"0.14","version_comment":"1) Reserved first two lines for html pre tags to fix html encoding issue, please see the example file and adjust for your own file.\r\n2) Changed folding functions. Now use <tab> in tags list region to toggle tags view or dates view.\r\n3) Fixed bug in new entry creation.","3":"1) Reserved first two lines for html pre tags to fix html encoding issue, please see the example file and adjust for your own file.\r\n2) Changed folding functions. Now use <tab> in tags list region to toggle tags view or dates view.\r\n3) Fixed bug in new entry creation.","package":"ywchaos-0.14.tar.bz2","4":"ywchaos-0.14.tar.bz2","src_id":"12468","5":"12468","creation_date":"1266902994","6":"1266902994"},{"0":"2845","vim_version":"7.0","1":"7.0","script_version":"0.13","2":"0.13","version_comment":"1. Implemented html syntax, now you can rename ywchaos file to .html to view the pictures.\r\n2. Added simplist html tags insertion & completion support.\r\n3. Changed Tag list region to start from 2nd line. 1st line reserves for html pre tag.\r\nPlease take the test file in the document for a try!","3":"1. Implemented html syntax, now you can rename ywchaos file to .html to view the pictures.\r\n2. Added simplist html tags insertion & completion support.\r\n3. Changed Tag list region to start from 2nd line. 1st line reserves for html pre tag.\r\nPlease take the test file in the document for a try!","package":"ywchaos-0.13.tar.bz2","4":"ywchaos-0.13.tar.bz2","src_id":"12339","5":"12339","creation_date":"1265648756","6":"1265648756"},{"0":"2845","vim_version":"7.0","1":"7.0","script_version":"0.12","2":"0.12","version_comment":"1. Fixed bug that cursor position may change after refresh the TAGS list region.\r\n2. Improved the highlight after tag name changed.","3":"1. Fixed bug that cursor position may change after refresh the TAGS list region.\r\n2. Improved the highlight after tag name changed.","package":"ywchaos-0.12.tar.bz2","4":"ywchaos-0.12.tar.bz2","src_id":"11895","5":"11895","creation_date":"1260664753","6":"1260664753"},{"0":"2845","vim_version":"7.0","1":"7.0","script_version":"0.11","2":"0.11","version_comment":"1) Tag grep(<C-]>) and tag outlining(<TAB>) now differ well with the subtags sharing a same name which in different parent tags.\r\n2) Improved TAGS list region generation function.","3":"1) Tag grep(<C-]>) and tag outlining(<TAB>) now differ well with the subtags sharing a same name which in different parent tags.\r\n2) Improved TAGS list region generation function.","package":"ywchaos-0.11.tar.bz2","4":"ywchaos-0.11.tar.bz2","src_id":"11817","5":"11817","creation_date":"1259331243","6":"1259331243"},{"0":"2845","vim_version":"7.0","1":"7.0","script_version":"0.10","2":"0.10","version_comment":"1) Improved TAGS list region generating function to prevent the lost of TAGS header.\r\n2) Fixed the bug of messing up the highlighting when inserting multi filetypes of snips.\r\n3) Fixed bug of vimgrep(<C-]>) for the multi-tag & subtag's matching.\r\n4) Ignore case in tags highlighting.\r\n5) Improved highlighting. Highlights accroding to English *word* and Chinese *charactors* .\r\n6) Removed '@' from the option of 'iskwd'.","3":"1) Improved TAGS list region generating function to prevent the lost of TAGS header.\r\n2) Fixed the bug of messing up the highlighting when inserting multi filetypes of snips.\r\n3) Fixed bug of vimgrep(<C-]>) for the multi-tag & subtag's matching.\r\n4) Ignore case in tags highlighting.\r\n5) Improved highlighting. Highlights accroding to English *word* and Chinese *charactors* .\r\n6) Removed '@' from the option of 'iskwd'.","package":"ywchaos-0.10.tar.bz2","4":"ywchaos-0.10.tar.bz2","src_id":"11770","5":"11770","creation_date":"1258729285","6":"1258729285"},{"0":"2845","vim_version":"7.0","1":"7.0","script_version":"0.9","2":"0.9","version_comment":"1. Arrange the subtags alphabetically.\r\n2. Improved <Tab> for subtag completion.","3":"1. Arrange the subtags alphabetically.\r\n2. Improved <Tab> for subtag completion.","package":"ywchaos-0.9.tar.bz2","4":"ywchaos-0.9.tar.bz2","src_id":"11736","5":"11736","creation_date":"1258335907","6":"1258335907"},{"0":"2845","vim_version":"7.0","1":"7.0","script_version":"0.8","2":"0.8","version_comment":"1) Fixed <C-]> not working for the new format of TAGS list region.\r\n2) Improved TAGS list region generating function.","3":"1) Fixed <C-]> not working for the new format of TAGS list region.\r\n2) Improved TAGS list region generating function.","package":"ywchaos-0.8.tar.bz2","4":"ywchaos-0.8.tar.bz2","src_id":"11729","5":"11729","creation_date":"1258275571","6":"1258275571"},{"0":"2845","vim_version":"7.0","1":"7.0","script_version":"0.7_2","2":"0.7_2","version_comment":"Fixed a bug with the var undefined...","3":"Fixed a bug with the var undefined...","package":"ywchaos-0.7_2.tar.bz2","4":"ywchaos-0.7_2.tar.bz2","src_id":"11721","5":"11721","creation_date":"1258122200","6":"1258122200"},{"0":"2845","vim_version":"7.0","1":"7.0","script_version":"0.7","2":"0.7","version_comment":"UPGRATE NOTE!!!: Delete the TAGSLINE manually please, new version use a different fomat which is called TAGS list region now. Please see the document and the sample file for detail.\r\n1) Tagsline format has changed to TAGS list region. Also note that the modeline should be change to the end of file if you use modeline.\r\n2) Added sub-tags supported which defined by @tag:subtag.\r\n3) Improved to test condition that if <tab> should try to complete on '|' and ':'.\r\n4) Fixed minor highlighting bug.","3":"UPGRATE NOTE!!!: Delete the TAGSLINE manually please, new version use a different fomat which is called TAGS list region now. Please see the document and the sample file for detail.\r\n1) Tagsline format has changed to TAGS list region. Also note that the modeline should be change to the end of file if you use modeline.\r\n2) Added sub-tags supported which defined by @tag:subtag.\r\n3) Improved to test condition that if <tab> should try to complete on '|' and ':'.\r\n4) Fixed minor highlighting bug.","package":"ywchaos-0.7.tar.bz2","4":"ywchaos-0.7.tar.bz2","src_id":"11720","5":"11720","creation_date":"1258120127","6":"1258120127"},{"0":"2845","vim_version":"7.0","1":"7.0","script_version":"0.6","2":"0.6","version_comment":"1) Added <tab> autocompetion for tag name when in insert mode after '@' and '|'.\r\n2) Added folding support on snips.\r\n3) Added syntax of @tag1|tag2 to support multi-tags.\r\n4) Improved syntax highlighting.\r\n5) Removed useless buffer variable.","3":"1) Added <tab> autocompetion for tag name when in insert mode after '@' and '|'.\r\n2) Added folding support on snips.\r\n3) Added syntax of @tag1|tag2 to support multi-tags.\r\n4) Improved syntax highlighting.\r\n5) Removed useless buffer variable.","package":"ywchaos-0.6.tar.bz2","4":"ywchaos-0.6.tar.bz2","src_id":"11705","5":"11705","creation_date":"1257908405","6":"1257908405"},{"0":"2845","vim_version":"7.0","1":"7.0","script_version":"0.5_2","2":"0.5_2","version_comment":"Fixed bug that snips can't be highlighted when start editing.","3":"Fixed bug that snips can't be highlighted when start editing.","package":"ywchaos-0.5_2.tar.bz2","4":"ywchaos-0.5_2.tar.bz2","src_id":"11704","5":"11704","creation_date":"1257848303","6":"1257848303"},{"0":"2845","vim_version":"7.0","1":"7.0","script_version":"0.5","2":"0.5","version_comment":"Supports inserting any other filetypes of snip and their highlightings!","3":"Supports inserting any other filetypes of snip and their highlightings!","package":"ywchaos-0.5.tar.bz2","4":"ywchaos-0.5.tar.bz2","src_id":"11703","5":"11703","creation_date":"1257843982","6":"1257843982"},{"0":"2845","vim_version":"7.0","1":"7.0","script_version":"0.4","2":"0.4","version_comment":"1) Suppressed <Tab> no fold found's warning.\r\n2) Fixed bug of <Tab> behavior on TAGSLINE.\r\n3) Added <Leader><C-l> for easing the TAGSLINE refresh.","3":"1) Suppressed <Tab> no fold found's warning.\r\n2) Fixed bug of <Tab> behavior on TAGSLINE.\r\n3) Added <Leader><C-l> for easing the TAGSLINE refresh.","package":"ywchaos-0.4.tar.bz2","4":"ywchaos-0.4.tar.bz2","src_id":"11695","5":"11695","creation_date":"1257761387","6":"1257761387"},{"0":"2845","vim_version":"7.0","1":"7.0","script_version":"0.3","2":"0.3","version_comment":"TAGSLINE treament improved.\r\n<Tab> key map improved.\r\nAccept 'yy' and 'yyyy' as year string, but 'yyyy' is recommended.\r\nMinor bugs fixed.","3":"TAGSLINE treament improved.\r\n<Tab> key map improved.\r\nAccept 'yy' and 'yyyy' as year string, but 'yyyy' is recommended.\r\nMinor bugs fixed.","package":"ywchaos-0.3.tar.bz2","4":"ywchaos-0.3.tar.bz2","src_id":"11691","5":"11691","creation_date":"1257729557","6":"1257729557"},{"0":"2845","vim_version":"7.0","1":"7.0","script_version":"0.2","2":"0.2","version_comment":"1. More highlightings support.\r\n2. Timestamp format changed to show second now.\r\n3. Timestamp entry can be folded now.","3":"1. More highlightings support.\r\n2. Timestamp format changed to show second now.\r\n3. Timestamp entry can be folded now.","package":"ywchaos-0.2.tar.bz2","4":"ywchaos-0.2.tar.bz2","src_id":"11687","5":"11687","creation_date":"1257666495","6":"1257666495"},{"0":"2845","vim_version":"7.0","1":"7.0","script_version":"0.1_2","2":"0.1_2","version_comment":"Fixed wrong package suffix, sorry for inconvenient!","3":"Fixed wrong package suffix, sorry for inconvenient!","package":"ywchaos-0.1_2.tar.bz2","4":"ywchaos-0.1_2.tar.bz2","src_id":"11674","5":"11674","creation_date":"1257578169","6":"1257578169"},{"0":"2845","vim_version":"7.0","1":"7.0","script_version":"0.1_2","2":"0.1_2","version_comment":"Fixed non-work highlighting and some minor bugs.","3":"Fixed non-work highlighting and some minor bugs.","package":"ywchaos-0.1_2.vim","4":"ywchaos-0.1_2.vim","src_id":"11673","5":"11673","creation_date":"1257578048","6":"1257578048"},{"0":"2845","vim_version":"7.0","1":"7.0","script_version":"0.1_1","2":"0.1_1","version_comment":"Fix function name typo.","3":"Fix function name typo.","package":"ywchaos-0.1_1.tar.bz2","4":"ywchaos-0.1_1.tar.bz2","src_id":"11672","5":"11672","creation_date":"1257577546","6":"1257577546"},{"0":"2845","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"ywchaos-0.1.tar.bz2","4":"ywchaos-0.1.tar.bz2","src_id":"11671","5":"11671","creation_date":"1257576183","6":"1257576183"}]},"2844":{"script_id":"2844","0":"2844","script_name":"simple comment","1":"simple comment","script_type":"utility","2":"utility","summary":"simple toggle comment script","3":"simple toggle comment script","description":"Simple comment is a small script (eight lines) to toggle line comment. It use \"s\" as trigger key. You can easily add more langages, take a look at the .vim !","4":"Simple comment is a small script (eight lines) to toggle line comment. It use \"s\" as trigger key. You can easily add more langages, take a look at the .vim !","install_details":"Add this next line to your vimrc, s can be another key.\r\n\r\nmap <silent> s :call Co(&ft)<CR>\r\n\r\nPut the .vim in your plugin folder or in your home and add \"so ~\/simple_comment.vim\" to your vimrc.","5":"Add this next line to your vimrc, s can be another key.\r\n\r\nmap <silent> s :call Co(&ft)<CR>\r\n\r\nPut the .vim in your plugin folder or in your home and add \"so ~\/simple_comment.vim\" to your vimrc.","first_name":"Maxime","6":"Maxime","last_name":"Boisvert","7":"Boisvert","releases":[{"0":"2844","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"simple_comment.vim","4":"simple_comment.vim","src_id":"11668","5":"11668","creation_date":"1257542585","6":"1257542585"}]},"2843":{"script_id":"2843","0":"2843","script_name":"FlipLR","1":"FlipLR","script_type":"utility","2":"utility","summary":"Flips left hand side and right hand side.","3":"Flips left hand side and right hand side.","description":"This script flips left hand side and right hand side.\r\n'lhs {operator} rhs' => 'rhs {operator} lhs'\r\n\r\nUsage:\r\n  1. In visual mode, select left hand side, operator and right hand side.\r\n  2. execute ':FlipLR operator'\r\n  2'. execute ':FlipLR \/operator\/' to flip with regexp\r\n\r\n  This mapping may help you.\r\n      noremap \\f :call g:FlipLR_startHighlightingPivot()<CR><ESC>:FlipLR <C-R>=g:FlipLR_detectPivot()<CR>\r\n\r\nScreencast:\r\n  http:\/\/bitbucket.org\/shu\/fliplr\/downloads\/fliplr.htm\r\n\r\nRepository:\r\n  http:\/\/bitbucket.org\/shu\/fliplr\/","4":"This script flips left hand side and right hand side.\r\n'lhs {operator} rhs' => 'rhs {operator} lhs'\r\n\r\nUsage:\r\n  1. In visual mode, select left hand side, operator and right hand side.\r\n  2. execute ':FlipLR operator'\r\n  2'. execute ':FlipLR \/operator\/' to flip with regexp\r\n\r\n  This mapping may help you.\r\n      noremap \\f :call g:FlipLR_startHighlightingPivot()<CR><ESC>:FlipLR <C-R>=g:FlipLR_detectPivot()<CR>\r\n\r\nScreencast:\r\n  http:\/\/bitbucket.org\/shu\/fliplr\/downloads\/fliplr.htm\r\n\r\nRepository:\r\n  http:\/\/bitbucket.org\/shu\/fliplr\/","install_details":"Just source this file. (Put this file into the plugin directory.)","5":"Just source this file. (Put this file into the plugin directory.)","first_name":"Shuhei","6":"Shuhei","last_name":"Kubota","7":"Kubota","releases":[{"0":"2843","vim_version":"7.0","1":"7.0","script_version":"1.3","2":"1.3","version_comment":"improved pivot detection\r\nuse  noremap \\f :call g:FlipLR_startHighlightingPivot()<CR><ESC>:FlipLR <C-R>=g:FlipLR_detectPivot()<CR>\r\n","3":"improved pivot detection\r\nuse  noremap \\f :call g:FlipLR_startHighlightingPivot()<CR><ESC>:FlipLR <C-R>=g:FlipLR_detectPivot()<CR>\r\n","package":"fliplr.vim","4":"fliplr.vim","src_id":"18867","5":"18867","creation_date":"1351036467","6":"1351036467"},{"0":"2843","vim_version":"7.0","1":"7.0","script_version":"1.1","2":"1.1","version_comment":"added regexp support and auto detection","3":"added regexp support and auto detection","package":"fliplr.vim","4":"fliplr.vim","src_id":"11702","5":"11702","creation_date":"1257842785","6":"1257842785"},{"0":"2843","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"changed EOL characters (ff=dos -> ff=unix)","3":"changed EOL characters (ff=dos -> ff=unix)","package":"fliplr.vim","4":"fliplr.vim","src_id":"11670","5":"11670","creation_date":"1257555472","6":"1257555472"},{"0":"2843","vim_version":"7.2","1":"7.2","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"fliplr.vim","4":"fliplr.vim","src_id":"11664","5":"11664","creation_date":"1257507735","6":"1257507735"}]},"2842":{"script_id":"2842","0":"2842","script_name":"vorg","1":"vorg","script_type":"syntax","2":"syntax","summary":"vim organizer syntax file","3":"vim organizer syntax file","description":"vorg is a simple organizer file format for managing your notes and tasks. It was inspired by org-mode for emacs but the format is different. \r\nIt is still very much work-in-progress. \r\n\r\nUsage: \r\n\r\nCreate a file with the .vorg extension and use the following format:\r\n\r\n- Topic\r\n  - Subtopic <tag1> <tag2> \r\n    - Subsubtopic\r\n      Subsubtopic text goes here\r\n    - [ ] A task\r\n    - [ ] Another task\r\n\t\t\r\nNotes: \r\n\r\n  - To indent sub topics in insert mode use <TAB>\r\n  - In normal mode, use <TAB> to fold and unfold topics\r\n  - You can also use asterisk signs (*) instead of minus signs(-)\r\n  - Tasks are indicated using a pair of square brackets with a blank inside [ ]\r\n  - You can create tasks without sub items by omitting the -\r\n\r\nMore Info:\r\n\r\n\t\t- Topic with a deadline < {date}\r\n\t\t- Topic with tags <tag1> <tag2> <tag3>\r\n\t\t- Topic with a timestamp ~ {date} @ {time}\r\n\t\t- Topic with a timestamp ~ {datetime}\r\n\t\t- {date} @ {time} ~ Topic with a timestamp\r\n\t\t- Topic with text content\r\n\t\t  some text...\r\n\r\n\r\n \t\tInsert-mode Shortcuts:\r\n\r\n\t\t-- create a new indented item\r\n\t\t-= create a new task\r\n\r\n\t\tctrl+j move line down\r\n\t\tctrl+k move line up\r\n\r\n\t\tdd - current date\r\n\t\tdt - current date+time\r\n\r\n\t\tNormal-mode Shortcuts:\r\n\t\t\r\n\t\t<TAB> expand\/collapse topics, use <shift> for all sub-topics\r\n\r\n\t\tctrl+t find tags (type the tag name and then press <CR>)\r\n\t\tctrl+o find contexts (type the context and then press <CR>)\r\n\r\n\t\tctrl+j  shifts line down\r\n\t\tctrl+k shifts line up\r\n\r\n\t\t,c checkmark a task\r\n\t\t,u uncheckmark a task\r\n\r\n\t\t,w follow hyperlink\r\n\r\nThanks Niels AdB for Tip 1557!\r\nThanks Frank Butler for Tip 646!\r\n\r\nMore info can be found inside the script..\r\nFor updates follow me on twitter (L3V3L9) and look for the upcoming vorg screencast.\r\n","4":"vorg is a simple organizer file format for managing your notes and tasks. It was inspired by org-mode for emacs but the format is different. \r\nIt is still very much work-in-progress. \r\n\r\nUsage: \r\n\r\nCreate a file with the .vorg extension and use the following format:\r\n\r\n- Topic\r\n  - Subtopic <tag1> <tag2> \r\n    - Subsubtopic\r\n      Subsubtopic text goes here\r\n    - [ ] A task\r\n    - [ ] Another task\r\n\t\t\r\nNotes: \r\n\r\n  - To indent sub topics in insert mode use <TAB>\r\n  - In normal mode, use <TAB> to fold and unfold topics\r\n  - You can also use asterisk signs (*) instead of minus signs(-)\r\n  - Tasks are indicated using a pair of square brackets with a blank inside [ ]\r\n  - You can create tasks without sub items by omitting the -\r\n\r\nMore Info:\r\n\r\n\t\t- Topic with a deadline < {date}\r\n\t\t- Topic with tags <tag1> <tag2> <tag3>\r\n\t\t- Topic with a timestamp ~ {date} @ {time}\r\n\t\t- Topic with a timestamp ~ {datetime}\r\n\t\t- {date} @ {time} ~ Topic with a timestamp\r\n\t\t- Topic with text content\r\n\t\t  some text...\r\n\r\n\r\n \t\tInsert-mode Shortcuts:\r\n\r\n\t\t-- create a new indented item\r\n\t\t-= create a new task\r\n\r\n\t\tctrl+j move line down\r\n\t\tctrl+k move line up\r\n\r\n\t\tdd - current date\r\n\t\tdt - current date+time\r\n\r\n\t\tNormal-mode Shortcuts:\r\n\t\t\r\n\t\t<TAB> expand\/collapse topics, use <shift> for all sub-topics\r\n\r\n\t\tctrl+t find tags (type the tag name and then press <CR>)\r\n\t\tctrl+o find contexts (type the context and then press <CR>)\r\n\r\n\t\tctrl+j  shifts line down\r\n\t\tctrl+k shifts line up\r\n\r\n\t\t,c checkmark a task\r\n\t\t,u uncheckmark a task\r\n\r\n\t\t,w follow hyperlink\r\n\r\nThanks Niels AdB for Tip 1557!\r\nThanks Frank Butler for Tip 646!\r\n\r\nMore info can be found inside the script..\r\nFor updates follow me on twitter (L3V3L9) and look for the upcoming vorg screencast.\r\n","install_details":"Simply extract the vorg archive in your ~\/.vim folder or use pathogen\r\n\r\nI also recommend installing the following plugins as well:\r\n- speeddating\r\n- tabular\r\n \t\t        \r\n","5":"Simply extract the vorg archive in your ~\/.vim folder or use pathogen\r\n\r\nI also recommend installing the following plugins as well:\r\n- speeddating\r\n- tabular\r\n \t\t        \r\n","first_name":"Ithai","6":"Ithai","last_name":"Levi","7":"Levi","releases":[{"0":"2842","vim_version":"7.0","1":"7.0","script_version":"0.2.0","2":"0.2.0","version_comment":"vorg now recognizes files based on the .vorg extension. Plugin is now modular and better arranged. Added a vorg.py script to support inserting vorg items from the command line - good for adding stuff from anywhere. Coloring was also improved. ","3":"vorg now recognizes files based on the .vorg extension. Plugin is now modular and better arranged. Added a vorg.py script to support inserting vorg items from the command line - good for adding stuff from anywhere. Coloring was also improved. ","package":"vorg.tar.gz","4":"vorg.tar.gz","src_id":"17000","5":"17000","creation_date":"1322747661","6":"1322747661"},{"0":"2842","vim_version":"7.0","1":"7.0","script_version":"0.1.0","2":"0.1.0","version_comment":"Initial upload","3":"Initial upload","package":"vorg.vim","4":"vorg.vim","src_id":"11663","5":"11663","creation_date":"1257440810","6":"1257440810"}]},"2841":{"script_id":"2841","0":"2841","script_name":"coldgreen.vim","1":"coldgreen.vim","script_type":"color scheme","2":"color scheme","summary":"base on dark background and green, blue color","3":"base on dark background and green, blue color","description":"This is vim color scheme file. base on dark background and green and blue color. This color script is optimized for Python source code, Now.\r\n\r\nscreenshots here: http:\/\/www.hexacosa.net\/project\/coldgreen\/","4":"This is vim color scheme file. base on dark background and green and blue color. This color script is optimized for Python source code, Now.\r\n\r\nscreenshots here: http:\/\/www.hexacosa.net\/project\/coldgreen\/","install_details":"copy to $VIMSCRIPTDIR\/colors\/","5":"copy to $VIMSCRIPTDIR\/colors\/","first_name":"Hideo","6":"Hideo","last_name":"Hattori","7":"Hattori","releases":[{"0":"2841","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"coldgreen.vim","4":"coldgreen.vim","src_id":"11660","5":"11660","creation_date":"1257431359","6":"1257431359"}]},"2840":{"script_id":"2840","0":"2840","script_name":"deprecated","1":"deprecated","script_type":"ftplugin","2":"ftplugin","summary":"..","3":"..","description":".","4":".","install_details":".","5":".","first_name":"jinhu","6":"jinhu","last_name":"lu","7":"lu","releases":[{"0":"2840","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"verilog.vim","4":"verilog.vim","src_id":"11659","5":"11659","creation_date":"1257422187","6":"1257422187"}]},"2839":{"script_id":"2839","0":"2839","script_name":"QuickFixHighlight","1":"QuickFixHighlight","script_type":"utility","2":"utility","summary":"Initial release","3":"Initial release","description":"QuickFixHighlight highlights lines that have quickfix errors defined for them.\r\n\r\nA screenshot can be found at http:\/\/miffe.org\/wiki\/Blog\/QuickFixHighlight\/","4":"QuickFixHighlight highlights lines that have quickfix errors defined for them.\r\n\r\nA screenshot can be found at http:\/\/miffe.org\/wiki\/Blog\/QuickFixHighlight\/","install_details":"Just put the script in the plugins directory.","5":"Just put the script in the plugins directory.","first_name":"Mikael","6":"Mikael","last_name":"Eriksson","7":"Eriksson","releases":[{"0":"2839","vim_version":"6.0","1":"6.0","script_version":"1","2":"1","version_comment":"Initial upload","3":"Initial upload","package":"QuickFixHighlight.vim","4":"QuickFixHighlight.vim","src_id":"11658","5":"11658","creation_date":"1257361795","6":"1257361795"}]},"2838":{"script_id":"2838","0":"2838","script_name":"HiVim","1":"HiVim","script_type":"color scheme","2":"color scheme","summary":"HiVim is a color scheme creator","3":"HiVim is a color scheme creator","description":"HiVim is actually a great (in my opinion) G\/Vim color scheme creator written in Tcl\/Tk\/Tix\/Bwidget.\r\n\r\nHiVim calls GVim so to test your scheme (the fun part) you need GVim installed.\r\n\r\nYou also need Tcl\/Tk\/Tix\/Bwidget installed...\r\n\r\nA screen shot is here:\r\n\r\nhttp:\/\/img.photobucket.com\/albums\/v124\/DefEye\/Screenshot-17.png\r\n\r\nA stand alone executable is here (all libraries included):\r\n\r\nhttp:\/\/www.mediafire.com\/file\/zy5ux4yn0wm\/HiVim-executable.tar.gz\r\n","4":"HiVim is actually a great (in my opinion) G\/Vim color scheme creator written in Tcl\/Tk\/Tix\/Bwidget.\r\n\r\nHiVim calls GVim so to test your scheme (the fun part) you need GVim installed.\r\n\r\nYou also need Tcl\/Tk\/Tix\/Bwidget installed...\r\n\r\nA screen shot is here:\r\n\r\nhttp:\/\/img.photobucket.com\/albums\/v124\/DefEye\/Screenshot-17.png\r\n\r\nA stand alone executable is here (all libraries included):\r\n\r\nhttp:\/\/www.mediafire.com\/file\/zy5ux4yn0wm\/HiVim-executable.tar.gz\r\n","install_details":"Run: .\/main.tcl\r\n\r\nFor the stand alone executable:\r\n\r\n.\/main","5":"Run: .\/main.tcl\r\n\r\nFor the stand alone executable:\r\n\r\n.\/main","first_name":"Stratis","6":"Stratis","last_name":"Aftousmis","7":"Aftousmis","releases":[{"0":"2838","vim_version":"6.0","1":"6.0","script_version":"1.2","2":"1.2","version_comment":"Traded tk_chooseColor for SelectColor (big improvment!)\r\n\r\nI also added more images...","3":"Traded tk_chooseColor for SelectColor (big improvment!)\r\n\r\nI also added more images...","package":"HiVim.tar.gz","4":"HiVim.tar.gz","src_id":"11700","5":"11700","creation_date":"1257789454","6":"1257789454"},{"0":"2838","vim_version":"6.0","1":"6.0","script_version":"1.1","2":"1.1","version_comment":"I changed the way HiVim starts GVim...","3":"I changed the way HiVim starts GVim...","package":"HiVim.tar.gz","4":"HiVim.tar.gz","src_id":"11657","5":"11657","creation_date":"1257353507","6":"1257353507"}]},"2837":{"script_id":"2837","0":"2837","script_name":"powershellCall","1":"powershellCall","script_type":"utility","2":"utility","summary":"Allow the use of Powershell to evaluate some buffer lines","3":"Allow the use of Powershell to evaluate some buffer lines","description":"This script provide 2 commands permitting some dialog with Microsoft Powershell.\r\n\r\nLines can be evaluated within vim, no filtering allowed for the moment.\r\n\r\nGitHub : https:\/\/github.com\/Twinside\/vim-powershellCall","4":"This script provide 2 commands permitting some dialog with Microsoft Powershell.\r\n\r\nLines can be evaluated within vim, no filtering allowed for the moment.\r\n\r\nGitHub : https:\/\/github.com\/Twinside\/vim-powershellCall","install_details":"drop it in your ~\/.vim\/plugin or ~\/vimfiles\/plugin directory, or better make a powershellCall folder in your bundle directory using pathogen","5":"drop it in your ~\/.vim\/plugin or ~\/vimfiles\/plugin directory, or better make a powershellCall folder in your bundle directory using pathogen","first_name":"Vincent","6":"Vincent","last_name":"B","7":"B","releases":[{"0":"2837","vim_version":"7.2","1":"7.2","script_version":"1.1","2":"1.1","version_comment":"Added better documentation","3":"Added better documentation","package":"vim-powershellCall.zip","4":"vim-powershellCall.zip","src_id":"15025","5":"15025","creation_date":"1297855713","6":"1297855713"},{"0":"2837","vim_version":"7.2","1":"7.2","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"powershellCall.vim","4":"powershellCall.vim","src_id":"11654","5":"11654","creation_date":"1257282494","6":"1257282494"}]},"2836":{"script_id":"2836","0":"2836","script_name":"wikinotes","1":"wikinotes","script_type":"syntax","2":"syntax","summary":"Wikipedia syntax with added functionality for taking notes","3":"Wikipedia syntax with added functionality for taking notes","description":"It is very practical to keep all kinds of notes in simple text files (as for example suggested in David Allen's \"Getting Things Done\" and blogs like joelonsoftware.com).\r\n\r\nCombining this with the editing mightiness of vim and some syntax highlighting for better structuring, you've got an easy but powerful tool for notes at your hand.\r\n\r\nI used the Wikipedia syntax as base, since it's proven simple human-readable syntax, that is well known.\r\nThen I added a few features like c-style commenting and html link highlighting.\r\n\r\nScreenshot: http:\/\/www.oxpal.com\/downloads\/vim\/wikinotes_syntax.png\r\n\r\nIt's most practical when setting this syntax file as standard for .txt or .wiki files. It then can also be used for editing actual Wikipedia text using vim (you might want to check out the firefox \"it's all text\" extension).","4":"It is very practical to keep all kinds of notes in simple text files (as for example suggested in David Allen's \"Getting Things Done\" and blogs like joelonsoftware.com).\r\n\r\nCombining this with the editing mightiness of vim and some syntax highlighting for better structuring, you've got an easy but powerful tool for notes at your hand.\r\n\r\nI used the Wikipedia syntax as base, since it's proven simple human-readable syntax, that is well known.\r\nThen I added a few features like c-style commenting and html link highlighting.\r\n\r\nScreenshot: http:\/\/www.oxpal.com\/downloads\/vim\/wikinotes_syntax.png\r\n\r\nIt's most practical when setting this syntax file as standard for .txt or .wiki files. It then can also be used for editing actual Wikipedia text using vim (you might want to check out the firefox \"it's all text\" extension).","install_details":"Copy into your syntax folder as usual and activate it with:\r\n:set syntax=wikinotes\r\n\r\nBy adding the following line to your filetypes.vim, you can make  vim open all .wiki files automatically with this syntax:\r\nau BufNewFile,BufRead *.wiki setf wikinotes\r\n(replace *.wiki if you prefer another file extension)","5":"Copy into your syntax folder as usual and activate it with:\r\n:set syntax=wikinotes\r\n\r\nBy adding the following line to your filetypes.vim, you can make  vim open all .wiki files automatically with this syntax:\r\nau BufNewFile,BufRead *.wiki setf wikinotes\r\n(replace *.wiki if you prefer another file extension)","first_name":"Thomas","6":"Thomas","last_name":"Schmall","7":"Schmall","releases":[{"0":"2836","vim_version":"5.7","1":"5.7","script_version":"1.0","2":"1.0","version_comment":"Initial upload.","3":"Initial upload.","package":"wikinotes.vim","4":"wikinotes.vim","src_id":"11647","5":"11647","creation_date":"1257128362","6":"1257128362"}]},"2835":{"script_id":"2835","0":"2835","script_name":"phpcodesniffer.vim","1":"phpcodesniffer.vim","script_type":"utility","2":"utility","summary":"Revisar los est\u00c3\u00a1ndares de programaci\u00c3\u00b3n con PhpCodeSniffer","3":"Revisar los est\u00c3\u00a1ndares de programaci\u00c3\u00b3n con PhpCodeSniffer","description":"Revisar los est\u00c3\u00a1ndares de programaci\u00c3\u00b3n sobre el fichero que estamos trabajando.\r\n\r\nEste script esta basado sobre el script de Thomas Link (samul@web.de) (phpchecksyntax)","4":"Revisar los est\u00c3\u00a1ndares de programaci\u00c3\u00b3n sobre el fichero que estamos trabajando.\r\n\r\nEste script esta basado sobre el script de Thomas Link (samul@web.de) (phpchecksyntax)","install_details":"Guardar el fichero en la carpeta ~\/.vim\/plugins","5":"Guardar el fichero en la carpeta ~\/.vim\/plugins","first_name":"Mag","6":"Mag","last_name":"San","7":"San","releases":[{"0":"2835","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"phpcodesniffer.vim","4":"phpcodesniffer.vim","src_id":"11642","5":"11642","creation_date":"1257117155","6":"1257117155"}]},"2834":{"script_id":"2834","0":"2834","script_name":"template.vim","1":"template.vim","script_type":"utility","2":"utility","summary":"Simple and flexible template engine.","3":"Simple and flexible template engine.","description":"*template* is a Vim plugin to read the template file automatically when the\r\nedit of the file is newly started.  Template file is selected to match the\r\nfile name to open. Also, you can run any command after the open.\r\n\r\n\r\nExample:\r\nIf the template files are located as follows:\r\n\r\n ~\/.vim\/template\r\n |-- doc\r\n |   `-- template.txt\r\n |-- plugin\r\n |   `-- template.vim\r\n |-- template.java\r\n |-- template.rb\r\n |-- template.vim\r\n |-- template_spec.rb\r\n `-- templateTest.java\r\n\r\nTemplate is loaded as follows.\r\n\r\nOpen file                       Template that is loaded\r\n---------                       -----------------------\r\nfoo.vim                         template.vim\r\nplugin\/foo.vim                  plugin\/template.vim\r\nFoo.java                        template.java\r\nFooTest.java                    templateTest.java\r\nfoo.rb                          template.rb\r\nfoo_spec.rb                     template_spec.rb\r\nfoo.txt                         (None)\r\ndoc\/foo.txt                     doc\/template.txt\r\n\r\n\r\nAnd, you can execute commands when template loaded.\r\n\r\nExamples:\r\nDefines replacing keywords:\r\n    autocmd User plugin-template-loaded call s:template_keywords()\r\n    function! s:template_keywords()\r\n      %s\/<+FILE NAME+>\/\\=expand('%:t')\/g\r\n      %s\/<+DATE+>\/\\=strftime('%Y-%m-%d')\/g\r\n      \" And more...\r\n    endfunction\r\n\r\nEvaluate by vim and expand the inside of <%= %>:\r\n    autocmd User plugin-template-loaded\r\n    \\ silent %s\/<%=\\(.\\{-}\\)%>\/\\=eval(submatch(1))\/ge\r\n\r\nExpand the date it is written in the following template.\r\n    <%= strftime('%Y-%m-%d') %>\r\n\r\nMove the cursor to <+CURSOR+>:\r\n    autocmd User plugin-template-loaded\r\n    \\    if search('<+CURSOR+>')\r\n    \\  |   execute 'normal! \"_da>'\r\n    \\  | endif\r\n\r\nFiltered by an external command:\r\n    autocmd User plugin-template-loaded silent! :%!erb\r\n    autocmd User plugin-template-loaded silent! :%!php\r\n\r\n\r\nLatest Version:\r\nhttps:\/\/github.com\/thinca\/vim-template","4":"*template* is a Vim plugin to read the template file automatically when the\r\nedit of the file is newly started.  Template file is selected to match the\r\nfile name to open. Also, you can run any command after the open.\r\n\r\n\r\nExample:\r\nIf the template files are located as follows:\r\n\r\n ~\/.vim\/template\r\n |-- doc\r\n |   `-- template.txt\r\n |-- plugin\r\n |   `-- template.vim\r\n |-- template.java\r\n |-- template.rb\r\n |-- template.vim\r\n |-- template_spec.rb\r\n `-- templateTest.java\r\n\r\nTemplate is loaded as follows.\r\n\r\nOpen file                       Template that is loaded\r\n---------                       -----------------------\r\nfoo.vim                         template.vim\r\nplugin\/foo.vim                  plugin\/template.vim\r\nFoo.java                        template.java\r\nFooTest.java                    templateTest.java\r\nfoo.rb                          template.rb\r\nfoo_spec.rb                     template_spec.rb\r\nfoo.txt                         (None)\r\ndoc\/foo.txt                     doc\/template.txt\r\n\r\n\r\nAnd, you can execute commands when template loaded.\r\n\r\nExamples:\r\nDefines replacing keywords:\r\n    autocmd User plugin-template-loaded call s:template_keywords()\r\n    function! s:template_keywords()\r\n      %s\/<+FILE NAME+>\/\\=expand('%:t')\/g\r\n      %s\/<+DATE+>\/\\=strftime('%Y-%m-%d')\/g\r\n      \" And more...\r\n    endfunction\r\n\r\nEvaluate by vim and expand the inside of <%= %>:\r\n    autocmd User plugin-template-loaded\r\n    \\ silent %s\/<%=\\(.\\{-}\\)%>\/\\=eval(submatch(1))\/ge\r\n\r\nExpand the date it is written in the following template.\r\n    <%= strftime('%Y-%m-%d') %>\r\n\r\nMove the cursor to <+CURSOR+>:\r\n    autocmd User plugin-template-loaded\r\n    \\    if search('<+CURSOR+>')\r\n    \\  |   execute 'normal! \"_da>'\r\n    \\  | endif\r\n\r\nFiltered by an external command:\r\n    autocmd User plugin-template-loaded silent! :%!erb\r\n    autocmd User plugin-template-loaded silent! :%!php\r\n\r\n\r\nLatest Version:\r\nhttps:\/\/github.com\/thinca\/vim-template","install_details":"","5":"","first_name":"thinca","6":"thinca","last_name":" ","7":" ","releases":[{"0":"2834","vim_version":"7.3","1":"7.3","script_version":"0.3.0","2":"0.3.0","version_comment":"- autoloadize.\r\n  - Added template#load().\r\n  - Added template#search().\r\n  - Added template#loading().\r\n- Added [line] support to :Templateload.\r\n- Use <nomodeline> if possible.","3":"- autoloadize.\r\n  - Added template#load().\r\n  - Added template#search().\r\n  - Added template#loading().\r\n- Added [line] support to :Templateload.\r\n- Use <nomodeline> if possible.","package":"vim-template-0.3.0.zip","4":"vim-template-0.3.0.zip","src_id":"18080","5":"18080","creation_date":"1338639346","6":"1338639346"},{"0":"2834","vim_version":"7.0","1":"7.0","script_version":"0.2.1","2":"0.2.1","version_comment":"- It was made not to become an error even when 'verbose' was one or more and the template was not found.\r\n- Execute the event without :silent.","3":"- It was made not to become an error even when 'verbose' was one or more and the template was not found.\r\n- Execute the event without :silent.","package":"vim-template-0.2.1.zip","4":"vim-template-0.2.1.zip","src_id":"13158","5":"13158","creation_date":"1276187586","6":"1276187586"},{"0":"2834","vim_version":"7.2","1":"7.2","script_version":"0.2.0","2":"0.2.0","version_comment":"Initial upload","3":"Initial upload","package":"vim-template-0.2.0.zip","4":"vim-template-0.2.0.zip","src_id":"11635","5":"11635","creation_date":"1257025569","6":"1257025569"}]},"2833":{"script_id":"2833","0":"2833","script_name":"buf_it","1":"buf_it","script_type":"utility","2":"utility","summary":"Buffer list in statusline","3":"Buffer list in statusline","description":"Buffer list in statusline\r\nUse\r\nalt + num to change  buf \r\n<leader>num to split buf\r\nalt+[ alt-] Show next part list If too much buf.\r\n,bo close other bufs.\r\n","4":"Buffer list in statusline\r\nUse\r\nalt + num to change  buf \r\n<leader>num to split buf\r\nalt+[ alt-] Show next part list If too much buf.\r\n,bo close other bufs.\r\n","install_details":"","5":"","first_name":"su","6":"su","last_name":"su","7":"su","releases":[{"0":"2833","vim_version":"7.0","1":"7.0","script_version":"v2.0","2":"v2.0","version_comment":"chang buf Idx","3":"chang buf Idx","package":"buf_it.vim","4":"buf_it.vim","src_id":"16529","5":"16529","creation_date":"1316054955","6":"1316054955"},{"0":"2833","vim_version":"7.0","1":"7.0","script_version":"v3.0","2":"v3.0","version_comment":"chang shotkey","3":"chang shotkey","package":"buf_it.vim","4":"buf_it.vim","src_id":"16465","5":"16465","creation_date":"1315183487","6":"1315183487"},{"0":"2833","vim_version":"7.0","1":"7.0","script_version":"1.4","2":"1.4","version_comment":"x","3":"x","package":"buf_it.vim","4":"buf_it.vim","src_id":"13840","5":"13840","creation_date":"1284617843","6":"1284617843"}]},"2832":{"script_id":"2832","0":"2832","script_name":"xmms2ctrl","1":"xmms2ctrl","script_type":"utility","2":"utility","summary":"Control XMMS2 through VIM","3":"Control XMMS2 through VIM","description":"A plugin to control XMMS2 from vim using nyxmms2.  It is released under GPLv2\r\n\r\nIt has the following features\r\n\r\n    * toggle play\/pause\r\n    * add track to playlist\r\n    * remove track from playlist\r\n    * previous track\r\n    * next track\r\n    * stop playing\r\n    * clear playlist\r\n    * seek through songs or goto specific time in a song\r\n    * change volume\r\n    * show current song playing\r\n    * jump to specific track in playlist\r\n    * load xmms2 playlist\r\n    * list all xmms2 playlists\r\n    * remove xmms2 playlist\r\n    * set config options in xmms2 ","4":"A plugin to control XMMS2 from vim using nyxmms2.  It is released under GPLv2\r\n\r\nIt has the following features\r\n\r\n    * toggle play\/pause\r\n    * add track to playlist\r\n    * remove track from playlist\r\n    * previous track\r\n    * next track\r\n    * stop playing\r\n    * clear playlist\r\n    * seek through songs or goto specific time in a song\r\n    * change volume\r\n    * show current song playing\r\n    * jump to specific track in playlist\r\n    * load xmms2 playlist\r\n    * list all xmms2 playlists\r\n    * remove xmms2 playlist\r\n    * set config options in xmms2 ","install_details":"install in your plugin directory\r\n\r\ntype \\xh for help on usage","5":"install in your plugin directory\r\n\r\ntype \\xh for help on usage","first_name":"Dereck","6":"Dereck","last_name":"Martin","7":"Martin","releases":[{"0":"2832","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"initial upload","3":"initial upload","package":"xmms2ctrl.vim","4":"xmms2ctrl.vim","src_id":"11622","5":"11622","creation_date":"1256842722","6":"1256842722"}]},"2831":{"script_id":"2831","0":"2831","script_name":"mimicpak","1":"mimicpak","script_type":"color scheme","2":"color scheme","summary":"Converted colorschemes from other Editors\/IDEs, plus originals.","3":"Converted colorschemes from other Editors\/IDEs, plus originals.","description":"The MimicPak is a set of 17 colorschemes which were converted (ripped-off)\r\nfrom other editors and IDEs and that use and share some common\r\ntweaking options, like the font style among others.  Some original,\r\npersonal, invented and cloned colorschemes are included too.\r\n\r\nThe IDEs\/Editors may have had more colorschemes, but only some\r\n(which I think that were great) are included.  Most of the colorschemes\r\nare only for gVim, this is so, because of time reasons and available\r\nnumber of colors.  However, you can use the CSApprox plugin\r\n( vimscript#2390 ) to use them on 88\/256 color terms.  Although some of them\r\nhave the cterm colors for 16 color terminals.\r\n\r\nFor a fast way to try out these schemes, the included mimicpak.vim\r\nplugin script creates a submenu \"MimicPak\" under the \"Themes\" menu on the main\r\nmenubar.\r\n\r\nAfter correctly installing this pack, you can see the help with:\r\n   :h mimicpak\r\n       >> to get general help\r\n   :h mimic-overview\r\n       >> quick overview of colorschemes by background colors.\r\n   :h mimic-options\r\n       >> to see the shared options.\r\n   :h name_of_scheme.vim   \r\n       >> to see specific options (if any) of a  particular colorscheme.\r\n\r\n================\r\nSHARED OPTIONS\r\n================\r\nAll the included colorschemes use and share the following common option\r\nvariables (these can either be set as: buffer, window, tabpage or global) :\r\n\r\n   * mimic_font_style:  controls the style of the fonts.\r\n\r\n        let  mimic_font_style = 0    \" schemes will use plain fonts\r\n        let  mimic_font_style = 1    \" schemes will use bold fonts\r\n        let  mimic_font_style = 2    \" schemes will use italic fonts\r\n        let  mimic_font_style = 3    \" schemes will use bold and italic fonts\r\n\r\n   * mimic_colorize_gui:  if set, GUI elements (menu, toolbar,\r\n        scrollbar) will be colorized (works only for some GUIs).\r\n\r\nThat said, you only need to set these options once and you'll get the\r\nsame look when changing to another of these schemes.\r\n\r\nFor further help about these, try:\r\n   :h mimic_font_style\r\n   :h mimic_colorize_gui\r\n\r\n==============\r\nSCREENSHOTS\r\n==============\r\nHere are some: http:\/\/img97.imageshack.us\/g\/scameemacsplain.png\/\r\n\r\nA slideshow: http:\/\/img513.imageshack.us\/slideshow\/player.php?id=img513\/5013\/1256781939pe8.smil\r\n\r\nMost of the included colorschemes are intended to be \"easy on the eyes\"\r\n(well, almost) and I hope that you might find at least 2 or 3\r\ncolorschemes from this pack that you could use for every day coding :)\r\n\r\nIf you like it (or if you don't) PLEASE RATE this thing!\r\n","4":"The MimicPak is a set of 17 colorschemes which were converted (ripped-off)\r\nfrom other editors and IDEs and that use and share some common\r\ntweaking options, like the font style among others.  Some original,\r\npersonal, invented and cloned colorschemes are included too.\r\n\r\nThe IDEs\/Editors may have had more colorschemes, but only some\r\n(which I think that were great) are included.  Most of the colorschemes\r\nare only for gVim, this is so, because of time reasons and available\r\nnumber of colors.  However, you can use the CSApprox plugin\r\n( vimscript#2390 ) to use them on 88\/256 color terms.  Although some of them\r\nhave the cterm colors for 16 color terminals.\r\n\r\nFor a fast way to try out these schemes, the included mimicpak.vim\r\nplugin script creates a submenu \"MimicPak\" under the \"Themes\" menu on the main\r\nmenubar.\r\n\r\nAfter correctly installing this pack, you can see the help with:\r\n   :h mimicpak\r\n       >> to get general help\r\n   :h mimic-overview\r\n       >> quick overview of colorschemes by background colors.\r\n   :h mimic-options\r\n       >> to see the shared options.\r\n   :h name_of_scheme.vim   \r\n       >> to see specific options (if any) of a  particular colorscheme.\r\n\r\n================\r\nSHARED OPTIONS\r\n================\r\nAll the included colorschemes use and share the following common option\r\nvariables (these can either be set as: buffer, window, tabpage or global) :\r\n\r\n   * mimic_font_style:  controls the style of the fonts.\r\n\r\n        let  mimic_font_style = 0    \" schemes will use plain fonts\r\n        let  mimic_font_style = 1    \" schemes will use bold fonts\r\n        let  mimic_font_style = 2    \" schemes will use italic fonts\r\n        let  mimic_font_style = 3    \" schemes will use bold and italic fonts\r\n\r\n   * mimic_colorize_gui:  if set, GUI elements (menu, toolbar,\r\n        scrollbar) will be colorized (works only for some GUIs).\r\n\r\nThat said, you only need to set these options once and you'll get the\r\nsame look when changing to another of these schemes.\r\n\r\nFor further help about these, try:\r\n   :h mimic_font_style\r\n   :h mimic_colorize_gui\r\n\r\n==============\r\nSCREENSHOTS\r\n==============\r\nHere are some: http:\/\/img97.imageshack.us\/g\/scameemacsplain.png\/\r\n\r\nA slideshow: http:\/\/img513.imageshack.us\/slideshow\/player.php?id=img513\/5013\/1256781939pe8.smil\r\n\r\nMost of the included colorschemes are intended to be \"easy on the eyes\"\r\n(well, almost) and I hope that you might find at least 2 or 3\r\ncolorschemes from this pack that you could use for every day coding :)\r\n\r\nIf you like it (or if you don't) PLEASE RATE this thing!\r\n","install_details":"* For the compressed Vimball file (.vba.gz):\r\n  Just open it in Vim\/gVim and then type:\r\n\r\n   :so %\r\n   :q\r\n\r\n  And that's all.\r\n\r\n[Windows users: you'll need to have gzip in your %PATH%].\r\n\r\n* For the zip file (.zip): extract them to a directory that is in your\r\n'runtimepath'.\r\n   On Unix\/linux:  $HOME\/.vim\/\r\n   On Windows:  %USERPROFILE%\\vimfiles\\ or YOUR_VIM_INSTALLATION_PATH\\vimfiles\\\r\n\r\nThen open Vim\/gVim and type:\r\n   :helptags THE_EXTRACTION_PATH\/doc\r\n\r\nAfter correct installation, you can see the help with:\r\n   :h mimicpak\r\n   :h mimicpak-toc\r\n\r\nThat's all... Enjoy!","5":"* For the compressed Vimball file (.vba.gz):\r\n  Just open it in Vim\/gVim and then type:\r\n\r\n   :so %\r\n   :q\r\n\r\n  And that's all.\r\n\r\n[Windows users: you'll need to have gzip in your %PATH%].\r\n\r\n* For the zip file (.zip): extract them to a directory that is in your\r\n'runtimepath'.\r\n   On Unix\/linux:  $HOME\/.vim\/\r\n   On Windows:  %USERPROFILE%\\vimfiles\\ or YOUR_VIM_INSTALLATION_PATH\\vimfiles\\\r\n\r\nThen open Vim\/gVim and type:\r\n   :helptags THE_EXTRACTION_PATH\/doc\r\n\r\nAfter correct installation, you can see the help with:\r\n   :h mimicpak\r\n   :h mimicpak-toc\r\n\r\nThat's all... Enjoy!","first_name":"Jaime","6":"Jaime","last_name":"Wottrich","7":"Wottrich","releases":[{"0":"2831","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Zip version (if you still use Vim 6).","3":"Zip version (if you still use Vim 6).","package":"mimicpak.zip","4":"mimicpak.zip","src_id":"11619","5":"11619","creation_date":"1256780752","6":"1256780752"},{"0":"2831","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"mimicpak.vba.gz","4":"mimicpak.vba.gz","src_id":"11618","5":"11618","creation_date":"1256780614","6":"1256780614"}]},"2830":{"script_id":"2830","0":"2830","script_name":"csv.vim","1":"csv.vim","script_type":"ftplugin","2":"ftplugin","summary":"A Filetype plugin for csv files.","3":"A Filetype plugin for csv files.","description":"This plugin is used for handling column separated data with Vim. Usually those \r\nfiles are called csv files and use the ',' as delimiter, though sometimes they \r\nuse e.g. the '|' or ';' as delimiter and there also exists fixedwidth columns. \r\nThe aim of this plugin is to ease handling these kinds of files.               \r\n                                                                               \r\nThis is a filetype plugin for CSV files. It was heavily influenced by          \r\nthe Vim Wiki Tip667 (http:\/\/vim.wikia.com\/wiki\/VimTip667), though it           \r\nworks differently.\r\n\r\nAlso you can create ascii tables using :Table\r\n\r\nFor a screenshot, of  how the plugin can be used, see\r\nhttp:\/\/www.256bit.org\/~chrisbra\/csv.gif\r\n\r\nPlease vote for the plugin, if you like it!\r\n\r\nThis little filetype plugin allows among others:\r\n -  Display on which column the cursor is as well as number of columns\r\n -  Search for text within a column using :SearchInColumn command\r\n -  Highlight the column on which the cursor is using :HiColumn command\r\n -  Visually arrange all columns using :ArrangeColumn command\r\n -  Delete a Column using :DeleteColumn command\r\n -  Display a vertical or horizontal header line using :Header or :VHeader command\r\n -  Sort a Column using :Sort command\r\n -  Copy Column to register using :Column command\r\n -  Move a column behind another column using :MoveCol command\r\n -  Calculate the Sum of all values within a column using :SumCol command (you can also define your\r\n    own custom aggregate functions)\r\n -  Move through the columns using the normal mode commands \r\n    (W forwards, H backwards, K upwards, J downwards)\r\n -  sets up a nice syntax highlighting, concealing the delimiter, if your Vim supports it\r\n -  dynamic filtering (Press enter on a value and all other lines, that don't have this value in this column\r\n    will be folded away. Press enter on another value and this value will be ANDed to the filter list. Press\r\n    Backspace to delete the last item from the filter list. Press Space to fold all lines, that have the same value\r\n    in the current field, Press Enter to fold all lines, that have a different value in the current field.\r\n    Use :Filters to see what filters are actvie)\r\n -  Analyze all values of a column (distribution) using :Analyze command\r\n -  Insert new records, using :NewRecord command\r\n -  Implement a wizard to setup fixed-width CSV files using :CSVFixed\r\n -  Hide certain columns, using :VertFold\r\n-   :Table to create ascii type tables (this function is available as plugin for all filetypes)\r\n\r\nPlease read the help on how to use the plugin\r\n :h ft-csv.txt","4":"This plugin is used for handling column separated data with Vim. Usually those \r\nfiles are called csv files and use the ',' as delimiter, though sometimes they \r\nuse e.g. the '|' or ';' as delimiter and there also exists fixedwidth columns. \r\nThe aim of this plugin is to ease handling these kinds of files.               \r\n                                                                               \r\nThis is a filetype plugin for CSV files. It was heavily influenced by          \r\nthe Vim Wiki Tip667 (http:\/\/vim.wikia.com\/wiki\/VimTip667), though it           \r\nworks differently.\r\n\r\nAlso you can create ascii tables using :Table\r\n\r\nFor a screenshot, of  how the plugin can be used, see\r\nhttp:\/\/www.256bit.org\/~chrisbra\/csv.gif\r\n\r\nPlease vote for the plugin, if you like it!\r\n\r\nThis little filetype plugin allows among others:\r\n -  Display on which column the cursor is as well as number of columns\r\n -  Search for text within a column using :SearchInColumn command\r\n -  Highlight the column on which the cursor is using :HiColumn command\r\n -  Visually arrange all columns using :ArrangeColumn command\r\n -  Delete a Column using :DeleteColumn command\r\n -  Display a vertical or horizontal header line using :Header or :VHeader command\r\n -  Sort a Column using :Sort command\r\n -  Copy Column to register using :Column command\r\n -  Move a column behind another column using :MoveCol command\r\n -  Calculate the Sum of all values within a column using :SumCol command (you can also define your\r\n    own custom aggregate functions)\r\n -  Move through the columns using the normal mode commands \r\n    (W forwards, H backwards, K upwards, J downwards)\r\n -  sets up a nice syntax highlighting, concealing the delimiter, if your Vim supports it\r\n -  dynamic filtering (Press enter on a value and all other lines, that don't have this value in this column\r\n    will be folded away. Press enter on another value and this value will be ANDed to the filter list. Press\r\n    Backspace to delete the last item from the filter list. Press Space to fold all lines, that have the same value\r\n    in the current field, Press Enter to fold all lines, that have a different value in the current field.\r\n    Use :Filters to see what filters are actvie)\r\n -  Analyze all values of a column (distribution) using :Analyze command\r\n -  Insert new records, using :NewRecord command\r\n -  Implement a wizard to setup fixed-width CSV files using :CSVFixed\r\n -  Hide certain columns, using :VertFold\r\n-   :Table to create ascii type tables (this function is available as plugin for all filetypes)\r\n\r\nPlease read the help on how to use the plugin\r\n :h ft-csv.txt","install_details":"Open csv.vmb in Vim and source the file: \r\n\r\n:so % \r\n\r\nThis will install the plugin into your $HOME\/.vim\/ftplugin directory and the documentation into your $HOME\/.vim\/doc directory. \r\n\r\nSee also the help for installing Vimball-Archives (:h vimball-intro) \r\n\r\nTake a look at :h ft-csv.txt for the documenation \r\n and read :h csv-installation to have vim automatically detect csv-files.","5":"Open csv.vmb in Vim and source the file: \r\n\r\n:so % \r\n\r\nThis will install the plugin into your $HOME\/.vim\/ftplugin directory and the documentation into your $HOME\/.vim\/doc directory. \r\n\r\nSee also the help for installing Vimball-Archives (:h vimball-intro) \r\n\r\nTake a look at :h ft-csv.txt for the documenation \r\n and read :h csv-installation to have vim automatically detect csv-files.","first_name":"Christian","6":"Christian","last_name":"Brabandt","7":"Brabandt","releases":[{"0":"2830","vim_version":"7.4","1":"7.4","script_version":"31","2":"31","version_comment":"- fix that H on the very first cell, results in an endless loop (https:\/\/github.com\/chrisbra\/csv.vim\/issues\/31, reported by lahvak, thanks!)\n- fix that count for |AddColumn| did not work (according to the documentation) (https:\/\/github.com\/chrisbra\/csv.vim\/issues\/32, reported by lahvak, thanks!)\n- invalid reference to a WarningMsg() function\n- WhatColumn! error, if the first line did not contain as many fields as the line to check.\n- Rename |:Table| command to |:CSVTable| ( https:\/\/github.com\/chrisbra\/csv.vim\/issues\/33, reported by Peter Jaros, thanks!)\n- Mention to escape special characters when manually specifying the delimiter. https:\/\/github.com\/chrisbra\/csv.vim\/issues\/35), also detect '^' as delimiter.\n- Csv fixed with columns better use '\\%v' to match columns, otherwise, one could get problems with multibyte chars\n- Sorting should work better with csv fixed with patterns (could generate an inavlide pattern before)\n- Refactor GetSID() (provided by Ingo Karkat https:\/\/github.com\/chrisbra\/csv.vim\/pull\/37, thanks!)\n- New public function |CSVSum()|\n- Restrict |csv-arrange-autocmd| to specific file sizes (suggested by Spencer Boucher in https:\/\/github.com\/chrisbra\/csv.vim\/issues\/39, thanks!)\n- Make |:CSVSearchInColumn| wrap pattern in '%\\(..\\)' pairs, so it works correctly with '\\|' atoms\n- Small improvements on |:CSVTable| and |:NewDelimiter| command\n- <Up> and <Down> should skip folds (like in normal Vi mode, suggested by\n  Kamaraju Kusuma, thanks!)\n(automatically uploaded)","3":"- fix that H on the very first cell, results in an endless loop (https:\/\/github.com\/chrisbra\/csv.vim\/issues\/31, reported by lahvak, thanks!)\n- fix that count for |AddColumn| did not work (according to the documentation) (https:\/\/github.com\/chrisbra\/csv.vim\/issues\/32, reported by lahvak, thanks!)\n- invalid reference to a WarningMsg() function\n- WhatColumn! error, if the first line did not contain as many fields as the line to check.\n- Rename |:Table| command to |:CSVTable| ( https:\/\/github.com\/chrisbra\/csv.vim\/issues\/33, reported by Peter Jaros, thanks!)\n- Mention to escape special characters when manually specifying the delimiter. https:\/\/github.com\/chrisbra\/csv.vim\/issues\/35), also detect '^' as delimiter.\n- Csv fixed with columns better use '\\%v' to match columns, otherwise, one could get problems with multibyte chars\n- Sorting should work better with csv fixed with patterns (could generate an inavlide pattern before)\n- Refactor GetSID() (provided by Ingo Karkat https:\/\/github.com\/chrisbra\/csv.vim\/pull\/37, thanks!)\n- New public function |CSVSum()|\n- Restrict |csv-arrange-autocmd| to specific file sizes (suggested by Spencer Boucher in https:\/\/github.com\/chrisbra\/csv.vim\/issues\/39, thanks!)\n- Make |:CSVSearchInColumn| wrap pattern in '%\\(..\\)' pairs, so it works correctly with '\\|' atoms\n- Small improvements on |:CSVTable| and |:NewDelimiter| command\n- <Up> and <Down> should skip folds (like in normal Vi mode, suggested by\n  Kamaraju Kusuma, thanks!)\n(automatically uploaded)","package":"csv-0.31.vmb","4":"csv-0.31.vmb","src_id":"22798","5":"22798","creation_date":"1421352517","6":"1421352517"},{"0":"2830","vim_version":"7.3","1":"7.3","script_version":"30","2":"30","version_comment":"- |:CSVSubstitute| should substitute all matches in a column, when 'g' flag is given\n- Don't override 'fdt' setting (https:\/\/github.com\/chrisbra\/csv.vim\/issues\/18, reported by Noah Frederick, thanks!)\n- Consistent Commands naming (https:\/\/github.com\/chrisbra\/csv.vim\/issues\/19, reported by Noah Frederick, thanks!)\n- New Function |CSVField()| and |CSVCol()|\n- clean up function did not remove certain buffer local variables, possible error when calling Menu function to disable CSV menu\n- make |:CSVArrangeColumn| do not output the numer of substitutions happened (suggested by Caylan Larson, thanks!)\n- better cleaning up on exit, if Header windows were used\n- Let |:CSVVHeader| accept a number, of how many columns to show (suggested by Caylan Larson, thanks!)\n- better error-handling for |CSVFixed|\n- selection of inner\/outer text objects  was wrong, reported by Ingo Karkat, thanks!)\n- errors, when using |:CSVAnalyze| and there were empty attributes\n- allow to left-align columns when using |:CSVArrangeColumn|\n- |SumCol_CSV| did not detect negative values\n- make <cr> in (Virtual-) Replace work as documented\n(automatically uploaded)","3":"- |:CSVSubstitute| should substitute all matches in a column, when 'g' flag is given\n- Don't override 'fdt' setting (https:\/\/github.com\/chrisbra\/csv.vim\/issues\/18, reported by Noah Frederick, thanks!)\n- Consistent Commands naming (https:\/\/github.com\/chrisbra\/csv.vim\/issues\/19, reported by Noah Frederick, thanks!)\n- New Function |CSVField()| and |CSVCol()|\n- clean up function did not remove certain buffer local variables, possible error when calling Menu function to disable CSV menu\n- make |:CSVArrangeColumn| do not output the numer of substitutions happened (suggested by Caylan Larson, thanks!)\n- better cleaning up on exit, if Header windows were used\n- Let |:CSVVHeader| accept a number, of how many columns to show (suggested by Caylan Larson, thanks!)\n- better error-handling for |CSVFixed|\n- selection of inner\/outer text objects  was wrong, reported by Ingo Karkat, thanks!)\n- errors, when using |:CSVAnalyze| and there were empty attributes\n- allow to left-align columns when using |:CSVArrangeColumn|\n- |SumCol_CSV| did not detect negative values\n- make <cr> in (Virtual-) Replace work as documented\n(automatically uploaded)","package":"csv-0.30.vmb","4":"csv-0.30.vmb","src_id":"21684","5":"21684","creation_date":"1395959394","6":"1395959394"},{"0":"2830","vim_version":"7.3","1":"7.3","script_version":"29","2":"29","version_comment":"-setup |QuitPre| autocommand to quit cleanly in newer vims when using :Header and :VHeader\n- new |AddColumn_CSV| command\n- prevent mapping of keys, if g:csv_nomap_<keyname> is set\n  (reported by ping)\n- new |Substitute_CSV| command\n- better syntax highlighting\n- small speedup for |ArrangeColumn_CSV|\n- 'E' did not correctly move the the previous column\n- support for vim-airline added\n(automatically uploaded)","3":"-setup |QuitPre| autocommand to quit cleanly in newer vims when using :Header and :VHeader\n- new |AddColumn_CSV| command\n- prevent mapping of keys, if g:csv_nomap_<keyname> is set\n  (reported by ping)\n- new |Substitute_CSV| command\n- better syntax highlighting\n- small speedup for |ArrangeColumn_CSV|\n- 'E' did not correctly move the the previous column\n- support for vim-airline added\n(automatically uploaded)","package":"csv-0.29.vmb","4":"csv-0.29.vmb","src_id":"20645","5":"20645","creation_date":"1376510881","6":"1376510881"},{"0":"2830","vim_version":"7.3","1":"7.3","script_version":"28","2":"28","version_comment":"new command :Table to create ascii tables for non-csv files (this feature is available as plugin (for all filetypes)\n(automatically uploaded)","3":"new command :Table to create ascii tables for non-csv files (this feature is available as plugin (for all filetypes)\n(automatically uploaded)","package":"csv-0.28.vmb","4":"csv-0.28.vmb","src_id":"19186","5":"19186","creation_date":"1355521142","6":"1355521142"},{"0":"2830","vim_version":"7.3","1":"7.3","script_version":"27","2":"27","version_comment":"- Better |CSV-Tabularize|\n- Documentation update\n(automatically uploaded)","3":"- Better |CSV-Tabularize|\n- Documentation update\n(automatically uploaded)","package":"csv-0.27.vmb","4":"csv-0.27.vmb","src_id":"19010","5":"19010","creation_date":"1353532973","6":"1353532973"},{"0":"2830","vim_version":"7.3","1":"7.3","script_version":"26","2":"26","version_comment":"- Better handling of setting filetype specific options\n- |CSV-Tabularize|\n- fix some small errors\n(automatically uploaded)","3":"- Better handling of setting filetype specific options\n- |CSV-Tabularize|\n- fix some small errors\n(automatically uploaded)","package":"csv-0.26.vmb","4":"csv-0.26.vmb","src_id":"18311","5":"18311","creation_date":"1343247875","6":"1343247875"},{"0":"2830","vim_version":"7.3","1":"7.3","script_version":"25","2":"25","version_comment":"- |SearchInColumn_CSV| should match non-greedily, patch by Mat\u00c3\u0083\u00e2\u0080\u009e\u00c3\u0082\u00e2\u0080\u00baj Korvas,\n- better argument parsing for |SearchInColumn_CSV|, patch by Mat\u00c3\u0083\u00e2\u0080\u009e\u00c3\u0082\u00e2\u0080\u00baj Korvas,\n  thanks!\n(automatically uploaded)","3":"- |SearchInColumn_CSV| should match non-greedily, patch by Mat\u00c3\u0083\u00e2\u0080\u009e\u00c3\u0082\u00e2\u0080\u00baj Korvas,\n- better argument parsing for |SearchInColumn_CSV|, patch by Mat\u00c3\u0083\u00e2\u0080\u009e\u00c3\u0082\u00e2\u0080\u00baj Korvas,\n  thanks!\n(automatically uploaded)","package":"csv-0.25.vmb","4":"csv-0.25.vmb","src_id":"17986","5":"17986","creation_date":"1337281684","6":"1337281684"},{"0":"2830","vim_version":"7.3","1":"7.3","script_version":"24","2":"24","version_comment":"- Allow to transpose the file (|csv-transpose|, suggested by Karan Mistry, thanks!)\n- |DeleteColumn_CSV| allows to specify a search pattern and all matching\n  columns will be deleted (suggested by Karan Mistry, thanks!)\n(automatically uploaded)","3":"- Allow to transpose the file (|csv-transpose|, suggested by Karan Mistry, thanks!)\n- |DeleteColumn_CSV| allows to specify a search pattern and all matching\n  columns will be deleted (suggested by Karan Mistry, thanks!)\n(automatically uploaded)","package":"csv-0.24.vmb","4":"csv-0.24.vmb","src_id":"17763","5":"17763","creation_date":"1334258386","6":"1334258386"},{"0":"2830","vim_version":"7.3","1":"7.3","script_version":"23","2":"23","version_comment":"- Don't error out, when creating a new file and syntax highlighting script can't find the delimiter (ftplugin will still give a warning, so)\n- Don't pollute the search register when loading a file\n- Give Warning when number format is wrong\n- Don't source ftdetect several times (patch by Zhao Cai, thanks!)\n- |NewDelimiter_CSV| to change the delimiter of the file\n- |Duplicate_CSV| to check for duplicate records in the file\n- Issue https:\/\/github.com\/chrisbra\/csv.vim\/issues\/13 fixed (missing quote, reported by y, thanks!)\n- |CSVPat()| function\n- 'lz' does not work with |:silent| |:s| (patch by Sergey Khorev, thanks!)\n- support comments (|csv_comment|, suggested by Peng Yu, thanks!)\n(automatically uploaded)","3":"- Don't error out, when creating a new file and syntax highlighting script can't find the delimiter (ftplugin will still give a warning, so)\n- Don't pollute the search register when loading a file\n- Give Warning when number format is wrong\n- Don't source ftdetect several times (patch by Zhao Cai, thanks!)\n- |NewDelimiter_CSV| to change the delimiter of the file\n- |Duplicate_CSV| to check for duplicate records in the file\n- Issue https:\/\/github.com\/chrisbra\/csv.vim\/issues\/13 fixed (missing quote, reported by y, thanks!)\n- |CSVPat()| function\n- 'lz' does not work with |:silent| |:s| (patch by Sergey Khorev, thanks!)\n- support comments (|csv_comment|, suggested by Peng Yu, thanks!)\n(automatically uploaded)","package":"csv-0.23.vmb","4":"csv-0.23.vmb","src_id":"17657","5":"17657","creation_date":"1332701320","6":"1332701320"},{"0":"2830","vim_version":"7.3","1":"7.3","script_version":"22","2":"22","version_comment":"- Small enhancements to |SumCol_CSV|\n- :Filters! reapplys the dynamic filter\n- Apply |csv-aggregate-functions| only to those values, that are not folded away.\n- |SumCol_CSV| can use a different number format (suggested by James Cole, thanks! (also |csv-nrformat|\n- Documentation updates (suggested by James Cole and Peng Yu)\n- More code cleanup and error handling\n  https:\/\/github.com\/chrisbra\/csv.vim\/issues\/9 reported Daniel Carl, thanks!\n  https:\/\/github.com\/chrisbra\/csv.vim\/issues\/8 patch by Daniel Carl, thanks!\n- New Command |NewRecord_CSV| (suggest by James Cole, thanks!)\n- new textobjects InnerField (if) and outerField (af) which contain the field without or with the delimiter (suggested by James Cole, thanks!)\n- |csv-arrange-autocmd| to let Vim automatically visually arrange the columns using |ArrangeColumn_CSV|\n- |csv-move-folds| let Vim move folded lines to the end\n- implement a Menu for graphical Vim\n(automatically uploaded)","3":"- Small enhancements to |SumCol_CSV|\n- :Filters! reapplys the dynamic filter\n- Apply |csv-aggregate-functions| only to those values, that are not folded away.\n- |SumCol_CSV| can use a different number format (suggested by James Cole, thanks! (also |csv-nrformat|\n- Documentation updates (suggested by James Cole and Peng Yu)\n- More code cleanup and error handling\n  https:\/\/github.com\/chrisbra\/csv.vim\/issues\/9 reported Daniel Carl, thanks!\n  https:\/\/github.com\/chrisbra\/csv.vim\/issues\/8 patch by Daniel Carl, thanks!\n- New Command |NewRecord_CSV| (suggest by James Cole, thanks!)\n- new textobjects InnerField (if) and outerField (af) which contain the field without or with the delimiter (suggested by James Cole, thanks!)\n- |csv-arrange-autocmd| to let Vim automatically visually arrange the columns using |ArrangeColumn_CSV|\n- |csv-move-folds| let Vim move folded lines to the end\n- implement a Menu for graphical Vim\n(automatically uploaded)","package":"csv-0.22.vmb","4":"csv-0.22.vmb","src_id":"16836","5":"16836","creation_date":"1320788333","6":"1320788333"},{"0":"2830","vim_version":"7.3","1":"7.3","script_version":"21","2":"21","version_comment":"- Implement a wizard for initializing fixed-width columns (|CSVFixed|)\n- Vertical folding (|VertFold_CSV|)\n- fix plugin indentation (by Daniel Karl, thanks!)\n- fixed missing bang parameter for HiColumn function (by Daniel Karl, thanks!)\n- fixed broken autodection of delimiter (reported by Peng Yu, thanks!)\n(automatically uploaded)","3":"- Implement a wizard for initializing fixed-width columns (|CSVFixed|)\n- Vertical folding (|VertFold_CSV|)\n- fix plugin indentation (by Daniel Karl, thanks!)\n- fixed missing bang parameter for HiColumn function (by Daniel Karl, thanks!)\n- fixed broken autodection of delimiter (reported by Peng Yu, thanks!)\n(automatically uploaded)","package":"csv-0.21.vmb","4":"csv-0.21.vmb","src_id":"16628","5":"16628","creation_date":"1317927134","6":"1317927134"},{"0":"2830","vim_version":"7.3","1":"7.3","script_version":"19","2":"19","version_comment":"- Make |:ArrangeColumn| more robust\n- Link CSVDelimiter to the Conceal highlighting group for Vims that have\n  +conceal feature (suggested by John Orr, thanks!)\n- allow the possibility to return the Column name in the statusline |csv-stl|\n  (suggested by John Orr, thanks!)\n- documentation updates\n- Allow to dynamically add Filters, see |csv-filter|\n- Also display what filters are active, see |:Filter|\n- Analyze a column for the distribution of a value |csv-analyze|\n- Implement UnArrangeColumn command |UnArrangeColumn_CSV|\n  (suggested by Daniel Karl in https:\/\/github.com\/chrisbra\/csv.vim\/issues\/7)\n(automatically uploaded)","3":"- Make |:ArrangeColumn| more robust\n- Link CSVDelimiter to the Conceal highlighting group for Vims that have\n  +conceal feature (suggested by John Orr, thanks!)\n- allow the possibility to return the Column name in the statusline |csv-stl|\n  (suggested by John Orr, thanks!)\n- documentation updates\n- Allow to dynamically add Filters, see |csv-filter|\n- Also display what filters are active, see |:Filter|\n- Analyze a column for the distribution of a value |csv-analyze|\n- Implement UnArrangeColumn command |UnArrangeColumn_CSV|\n  (suggested by Daniel Karl in https:\/\/github.com\/chrisbra\/csv.vim\/issues\/7)\n(automatically uploaded)","package":"csv-0.19.vmb","4":"csv-0.19.vmb","src_id":"16592","5":"16592","creation_date":"1317071275","6":"1317071275"},{"0":"2830","vim_version":"7.3","1":"7.3","script_version":"18","2":"18","version_comment":"- fix small typos in documentation\n- document, that 'K' and 'J' have been remapped and the originial function is\n  available as \\K and \\J\n- Delimiters should not be highlighted within a column, only when used\n  as actual delimiters (suggested by Peng Yu, thanks!)\n- Performance improvements for |:ArrangeColumn|\n(automatically uploaded)","3":"- fix small typos in documentation\n- document, that 'K' and 'J' have been remapped and the originial function is\n  available as \\K and \\J\n- Delimiters should not be highlighted within a column, only when used\n  as actual delimiters (suggested by Peng Yu, thanks!)\n- Performance improvements for |:ArrangeColumn|\n(automatically uploaded)","package":"csv-0.18.vmb","4":"csv-0.18.vmb","src_id":"16406","5":"16406","creation_date":"1314733483","6":"1314733483"},{"0":"2830","vim_version":"7.3","1":"7.3","script_version":"17","2":"17","version_comment":"- small cosmetic changes\n- small documentation updates\n- fold away changelog in help file\n- Document, that |DeleteColumn_CSV| deletes the column on which the cursor\n  is, if no column number has been specified\n- Support csv fixed width columns (|csv-fixedwidth|)\n- Support to interactively convert your csv file to a different\n  format (|csv-convert|)\n(automatically uploaded)","3":"- small cosmetic changes\n- small documentation updates\n- fold away changelog in help file\n- Document, that |DeleteColumn_CSV| deletes the column on which the cursor\n  is, if no column number has been specified\n- Support csv fixed width columns (|csv-fixedwidth|)\n- Support to interactively convert your csv file to a different\n  format (|csv-convert|)\n(automatically uploaded)","package":"csv-0.17.vba","4":"csv-0.17.vba","src_id":"16274","5":"16274","creation_date":"1313479953","6":"1313479953"},{"0":"2830","vim_version":"7.3","1":"7.3","script_version":"16","2":"16","version_comment":"-Sort on the range, specified (reported by Peng Yu, thanks!)\n-|MoveCol_CSV| to move a column behind another column\n (suggested by Peng Yu, thanks!)\n-Document how to use custom functions with a column\n (|csv-aggregate-functions|)\n-Use g:csv_highlight_column variable, to have Vim automatically\n highlight the column on which the cursor is (|csv-hicol|)\n-Header\/VHeader command should work better now (|Header_CSV|,\n |VHeader_CSV|)\n-Use setreg() for setting the register for the |Column_CSV|\n command and make sure it is blockwise.\n-Release 0.14 was not correctly uploaded to vim.org\n(automatically uploaded)","3":"-Sort on the range, specified (reported by Peng Yu, thanks!)\n-|MoveCol_CSV| to move a column behind another column\n (suggested by Peng Yu, thanks!)\n-Document how to use custom functions with a column\n (|csv-aggregate-functions|)\n-Use g:csv_highlight_column variable, to have Vim automatically\n highlight the column on which the cursor is (|csv-hicol|)\n-Header\/VHeader command should work better now (|Header_CSV|,\n |VHeader_CSV|)\n-Use setreg() for setting the register for the |Column_CSV|\n command and make sure it is blockwise.\n-Release 0.14 was not correctly uploaded to vim.org\n(automatically uploaded)","package":"csv-0.16.vba","4":"csv-0.16.vba","src_id":"16140","5":"16140","creation_date":"1311631470","6":"1311631470"},{"0":"2830","vim_version":"7.3","1":"7.3","script_version":"13","2":"13","version_comment":"\n-documentation update\n-https:\/\/github.com\/chrisbra\/csv.vim\/issues#issue\/2 thanks lespea!\n-https:\/\/github.com\/chrisbra\/csv.vim\/issues#issue\/3 thanks lespea!\n-https:\/\/github.com\/chrisbra\/csv.vim\/issues#issue\/1 thanks lespea!\n-fix some small annoying bugs\n-WhatColumn! displays column name\n(automatically uploaded)","3":"\n-documentation update\n-https:\/\/github.com\/chrisbra\/csv.vim\/issues#issue\/2 thanks lespea!\n-https:\/\/github.com\/chrisbra\/csv.vim\/issues#issue\/3 thanks lespea!\n-https:\/\/github.com\/chrisbra\/csv.vim\/issues#issue\/1 thanks lespea!\n-fix some small annoying bugs\n-WhatColumn! displays column name\n(automatically uploaded)","package":"csv-0.13.vba","4":"csv-0.13.vba","src_id":"15219","5":"15219","creation_date":"1300141054","6":"1300141054"},{"0":"2830","vim_version":"7.2","1":"7.2","script_version":"12","2":"12","version_comment":"-don't use :noa when switching between windows\n-make sure, colwidth() doesn't throw an error\n(automatically uploaded)","3":"-don't use :noa when switching between windows\n-make sure, colwidth() doesn't throw an error\n(automatically uploaded)","package":"csv-0.12.vba","4":"csv-0.12.vba","src_id":"15113","5":"15113","creation_date":"1298582515","6":"1298582515"},{"0":"2830","vim_version":"7.2","1":"7.2","script_version":"11","2":"11","version_comment":"-new command :Column\n-:SearchInColumn did not find anything in the last if no delimiter was given (reported by chroyer)\n-:VHeader displays the first column as Header similar to how :Header works\n-:HeaderToggle and VHeaderToggle commands that toggles displaying the header lines\/columns\n(automatically uploaded)","3":"-new command :Column\n-:SearchInColumn did not find anything in the last if no delimiter was given (reported by chroyer)\n-:VHeader displays the first column as Header similar to how :Header works\n-:HeaderToggle and VHeaderToggle commands that toggles displaying the header lines\/columns\n(automatically uploaded)","package":"csv-0.11.vba","4":"csv-0.11.vba","src_id":"15111","5":"15111","creation_date":"1298579278","6":"1298579278"},{"0":"2830","vim_version":"7.2","1":"7.2","script_version":"10","2":"10","version_comment":"-Only conceal real delimiters\n-document g:csv_no_conceal variable\n-document g:csv_nl variable\n-document conceal feature and syntax highlighting\n-Normal mode command <Up>\/<Down> work like K\/J\n-More robust regular expression engine, that can\n also handle newlines inside quoted strings.\n-Slightly adjusted syntax highlighting\n(automatically uploaded)","3":"-Only conceal real delimiters\n-document g:csv_no_conceal variable\n-document g:csv_nl variable\n-document conceal feature and syntax highlighting\n-Normal mode command <Up>\/<Down> work like K\/J\n-More robust regular expression engine, that can\n also handle newlines inside quoted strings.\n-Slightly adjusted syntax highlighting\n(automatically uploaded)","package":"csv-0.10.vba","4":"csv-0.10.vba","src_id":"15103","5":"15103","creation_date":"1298498080","6":"1298498080"},{"0":"2830","vim_version":"7.2","1":"7.2","script_version":"9","2":"9","version_comment":"-use conceal char depending on encoding\n-Map normal mode keys also for visual\/select and operator pending mode\n(automatically uploaded)","3":"-use conceal char depending on encoding\n-Map normal mode keys also for visual\/select and operator pending mode\n(automatically uploaded)","package":"csv-0.9.vba","4":"csv-0.9.vba","src_id":"15045","5":"15045","creation_date":"1298123432","6":"1298123432"},{"0":"2830","vim_version":"7.2","1":"7.2","script_version":"8","2":"8","version_comment":"-Better Error handling\n-HiColumn! removes highlighting\n-Enable NrColumns, that was deactivated in v.0.7\n-a ColorScheme autocommand makes sure, that the syntax highlighting is reapplied, after changing the colorscheme.\n-small performance improvements for |ArrangeColumn_CSV|\n-Syntax Highlighting conceales delimiter\n-A lot more documentation\n-SearchInColumn now searches in the current column, if no column has been specified\n(automatically uploaded)","3":"-Better Error handling\n-HiColumn! removes highlighting\n-Enable NrColumns, that was deactivated in v.0.7\n-a ColorScheme autocommand makes sure, that the syntax highlighting is reapplied, after changing the colorscheme.\n-small performance improvements for |ArrangeColumn_CSV|\n-Syntax Highlighting conceales delimiter\n-A lot more documentation\n-SearchInColumn now searches in the current column, if no column has been specified\n(automatically uploaded)","package":"csv-0.8.vba","4":"csv-0.8.vba","src_id":"15037","5":"15037","creation_date":"1297980195","6":"1297980195"},{"0":"2830","vim_version":"7.2","1":"7.2","script_version":"7","2":"7","version_comment":"-Make the motion commands 'W' and 'E' work more reliable\n-Document how to setup filetype plugins\n-Make |WhatColumn_CSV| work more reliable (report from http:\/\/vim.wikia.com\/Script:3280)\n-DeleteColumn deletes current column, if no argument given\n-|ArrangeColumn_CSV| handles errors better\n-Code cleanup\n-Syntax highlighting\n-'H' and 'L' move forward\/backwards between csv fields\n-'K' and 'J' move upwards\/downwards within the same column\n-|Sort_CSV| to sort on a certain column\n-|csv-tips| on how to colorize the statusline\n(automatically uploaded)","3":"-Make the motion commands 'W' and 'E' work more reliable\n-Document how to setup filetype plugins\n-Make |WhatColumn_CSV| work more reliable (report from http:\/\/vim.wikia.com\/Script:3280)\n-DeleteColumn deletes current column, if no argument given\n-|ArrangeColumn_CSV| handles errors better\n-Code cleanup\n-Syntax highlighting\n-'H' and 'L' move forward\/backwards between csv fields\n-'K' and 'J' move upwards\/downwards within the same column\n-|Sort_CSV| to sort on a certain column\n-|csv-tips| on how to colorize the statusline\n(automatically uploaded)","package":"csv-0.7.vba","4":"csv-0.7.vba","src_id":"15031","5":"15031","creation_date":"1297894989","6":"1297894989"},{"0":"2830","vim_version":"7.2","1":"7.2","script_version":"6","2":"6","version_comment":"-Make |ArrangeColumn| work more reliable (had problems with multibyte chars before)\n-Add |Header| function\n-'W' and 'E' move forward\/backwards between csv fields\n(automatically uploaded)","3":"-Make |ArrangeColumn| work more reliable (had problems with multibyte chars before)\n-Add |Header| function\n-'W' and 'E' move forward\/backwards between csv fields\n(automatically uploaded)","package":"csv-0.6.vba","4":"csv-0.6.vba","src_id":"15021","5":"15021","creation_date":"1297811315","6":"1297811315"},{"0":"2830","vim_version":"7.0","1":"7.0","script_version":"0.5","2":"0.5","version_comment":"enabled GLVS (see :h GLVS),\r\nput cvs.vim on a public repository available at http:\/\/github.com\/chrisbra\/csv.vim","3":"enabled GLVS (see :h GLVS),\r\nput cvs.vim on a public repository available at http:\/\/github.com\/chrisbra\/csv.vim","package":"csv.vba","4":"csv.vba","src_id":"12877","5":"12877","creation_date":"1271786723","6":"1271786723"},{"0":"2830","vim_version":"7.0","1":"7.0","script_version":"0.4a","2":"0.4a","version_comment":"fixed documentation","3":"fixed documentation","package":"csv.vba","4":"csv.vba","src_id":"12607","5":"12607","creation_date":"1268343316","6":"1268343316"},{"0":"2830","vim_version":"7.0","1":"7.0","script_version":"0.4","2":"0.4","version_comment":"Better error handling\r\nadded :InitCSV to reinitialize the plugin\r\n:HiColumn now by default the current column, if no argument is given","3":"Better error handling\r\nadded :InitCSV to reinitialize the plugin\r\n:HiColumn now by default the current column, if no argument is given","package":"csv.vba","4":"csv.vba","src_id":"12604","5":"12604","creation_date":"1268341210","6":"1268341210"},{"0":"2830","vim_version":"7.2","1":"7.2","script_version":"0.3","2":"0.3","version_comment":"Initial upload","3":"Initial upload","package":"csv.vba","4":"csv.vba","src_id":"11615","5":"11615","creation_date":"1256771337","6":"1256771337"}]},"2829":{"script_id":"2829","0":"2829","script_name":"roo.vim","1":"roo.vim","script_type":"syntax","2":"syntax","summary":"Spring Roo syntax highlighting","3":"Spring Roo syntax highlighting","description":"Simple syntax highlighting for Spring Roo (http:\/\/www.springsource.org\/roo) script files","4":"Simple syntax highlighting for Spring Roo (http:\/\/www.springsource.org\/roo) script files","install_details":"Put this in your vimfiles\/syntax directory and add something like this to your filetype.vim:\r\n  au! BufNewFile,BufRead *.roo  setf roo\r\n","5":"Put this in your vimfiles\/syntax directory and add something like this to your filetype.vim:\r\n  au! BufNewFile,BufRead *.roo  setf roo\r\n","first_name":"Joris","6":"Joris","last_name":"Kuipers","7":"Kuipers","releases":[{"0":"2829","vim_version":"5.7","1":"5.7","script_version":"1.1","2":"1.1","version_comment":"Added '#' as start of line comment for Roo versions 1.1.0.M3 and up (https:\/\/jira.springsource.org\/browse\/ROO-1116)","3":"Added '#' as start of line comment for Roo versions 1.1.0.M3 and up (https:\/\/jira.springsource.org\/browse\/ROO-1116)","package":"roo.vim","4":"roo.vim","src_id":"13739","5":"13739","creation_date":"1283288503","6":"1283288503"},{"0":"2829","vim_version":"5.7","1":"5.7","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"roo.vim","4":"roo.vim","src_id":"11614","5":"11614","creation_date":"1256766038","6":"1256766038"}]},"2828":{"script_id":"2828","0":"2828","script_name":"Cobalt Colour scheme","1":"Cobalt Colour scheme","script_type":"color scheme","2":"color scheme","summary":"Vim version of TextMates Cobalt colour scheme","3":"Vim version of TextMates Cobalt colour scheme","description":"This is a Vim version of one of TextMate's default colour schemes, Cobalt. Only designed for GVim.\r\n\r\nIf you want to follow the development you can find it on Github at http:\/\/github.com\/dterei\/VimCobaltColourScheme","4":"This is a Vim version of one of TextMate's default colour schemes, Cobalt. Only designed for GVim.\r\n\r\nIf you want to follow the development you can find it on Github at http:\/\/github.com\/dterei\/VimCobaltColourScheme","install_details":"Download and copy to ~\/.vim\/colors directory.","5":"Download and copy to ~\/.vim\/colors directory.","first_name":"David","6":"David","last_name":"Terei","7":"Terei","releases":[{"0":"2828","vim_version":"7.0","1":"7.0","script_version":"1.4","2":"1.4","version_comment":"* Improvements to the window dividers\r\n* Tweaks to directory colour","3":"* Improvements to the window dividers\r\n* Tweaks to directory colour","package":"cobalt.vim","4":"cobalt.vim","src_id":"15086","5":"15086","creation_date":"1298404417","6":"1298404417"},{"0":"2828","vim_version":"7.0","1":"7.0","script_version":"1.2","2":"1.2","version_comment":"Some tweaks made to improve accuracy. Most of the work was done by Константин Городинский. While I believe this version is more accurate then the old version, I prefer the look of the old, so I have continued the old version as an 'inspired by cobalt' colour scheme here vimscript#3439","3":"Some tweaks made to improve accuracy. Most of the work was done by Константин Городинский. While I believe this version is more accurate then the old version, I prefer the look of the old, so I have continued the old version as an 'inspired by cobalt' colour scheme here vimscript#3439","package":"cobalt.vim","4":"cobalt.vim","src_id":"14949","5":"14949","creation_date":"1296770487","6":"1296770487"},{"0":"2828","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"cobalt.vim","4":"cobalt.vim","src_id":"11607","5":"11607","creation_date":"1256707300","6":"1256707300"}]},"2827":{"script_id":"2827","0":"2827","script_name":"RTM.vim","1":"RTM.vim","script_type":"utility","2":"utility","summary":"Vim plugin for Remember The Milk","3":"Vim plugin for Remember The Milk","description":"============\r\nProject info\r\n============\r\n\r\nAuthor: Kosei Kitahara <surgo.jp@gmail.com>\r\nProject host: http:\/\/bitbucket.org\/Surgo\/rtm.vim\/\r\n\r\n=====\r\nUsage\r\n=====\r\n\r\nAdd Task\r\n--------\r\n\r\n * add current line to task\r\n   `:C[RTM] -a` command\r\n * add current buffer to task\r\n   `:B[RTM] -a` command\r\n\r\n====\r\nTODO\r\n====\r\n\r\n * set tag, location, priority to task\r\n * complete task\r\n * delete task","4":"============\r\nProject info\r\n============\r\n\r\nAuthor: Kosei Kitahara <surgo.jp@gmail.com>\r\nProject host: http:\/\/bitbucket.org\/Surgo\/rtm.vim\/\r\n\r\n=====\r\nUsage\r\n=====\r\n\r\nAdd Task\r\n--------\r\n\r\n * add current line to task\r\n   `:C[RTM] -a` command\r\n * add current buffer to task\r\n   `:B[RTM] -a` command\r\n\r\n====\r\nTODO\r\n====\r\n\r\n * set tag, location, priority to task\r\n * complete task\r\n * delete task","install_details":"=======\r\nInstall\r\n=======\r\n\r\n * get and set path to cURL (no need SSL)\r\n   http:\/\/curl.haxx.se\/download.html\r\n   if windows, put curl.exe to vim home directory\r\n * get md5.vim plugin and put vim plugin directory\r\n   http:\/\/www.vim.org\/scripts\/script.php?script_id=2806\r\n * put rtm.vim to vim plugin directory\r\n\r\n==========\r\nActivation\r\n==========\r\n\r\n * get ur RTM (Non-commercial use) API key and shared secret\r\n   https:\/\/www.rememberthemilk.com\/services\/api\/keys.rtm\r\n * set .vimrc file\r\n  * `let rtm_api_key='<ur api key>'`\r\n  * `let rtm_shared_secret='<ur shared secret>'`\r\n * get allow api access url via `:RTM -a` command\r\n * allow api access\r\n * get token via: `:RTM -t` command\r\n * token put .vimrc file\r\n  * `let rtm_token='<ur token>'`","5":"=======\r\nInstall\r\n=======\r\n\r\n * get and set path to cURL (no need SSL)\r\n   http:\/\/curl.haxx.se\/download.html\r\n   if windows, put curl.exe to vim home directory\r\n * get md5.vim plugin and put vim plugin directory\r\n   http:\/\/www.vim.org\/scripts\/script.php?script_id=2806\r\n * put rtm.vim to vim plugin directory\r\n\r\n==========\r\nActivation\r\n==========\r\n\r\n * get ur RTM (Non-commercial use) API key and shared secret\r\n   https:\/\/www.rememberthemilk.com\/services\/api\/keys.rtm\r\n * set .vimrc file\r\n  * `let rtm_api_key='<ur api key>'`\r\n  * `let rtm_shared_secret='<ur shared secret>'`\r\n * get allow api access url via `:RTM -a` command\r\n * allow api access\r\n * get token via: `:RTM -t` command\r\n * token put .vimrc file\r\n  * `let rtm_token='<ur token>'`","first_name":"Kosei","6":"Kosei","last_name":"Kitahara","7":"Kitahara","releases":[{"0":"2827","vim_version":"7.2","1":"7.2","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"rtm.vim","4":"rtm.vim","src_id":"11605","5":"11605","creation_date":"1256660324","6":"1256660324"}]},"2826":{"script_id":"2826","0":"2826","script_name":"multisearch.vim","1":"multisearch.vim","script_type":"utility","2":"utility","summary":"Search + highlight multiple search terms","3":"Search + highlight multiple search terms","description":"I routinely need to examine log files from production, and found the need to highlight and search multiple terms during the process. I took ideas from such scripts such as Highlighter.vim, MultipleSearch.vim and MultipleSearch2.vim and created a script to help me with the above task. In April, 2008, I rewrote the script virtually from scratch and over the last year and a half improved its functionality. I now submit the result of my efforts for the benefit of the Vim community.\r\n\r\nMulti Search enables highlighting (and searching) multiple search terms. Each defined search term's highlight state can be enabled or disabled. Searches can be performed on all the defined terms, all enabled terms, or on specific terms.\r\n\r\nOn platforms that support it, the Multi Search menu makes it easier to use some of the Multi Search commands. Multi Search also defines mappings for the more commonly used commands.\r\n\r\nAlthough it is marked as requiring Vim 7.2, the Multi Search plugin was developed and tested using Vim 7.1. Please see the installation instructions below. Once installed, detailed help can be obtained by\r\n\r\n\t:help Msearch\r\n\r\nEmail bug reports and enhancement requests to the author. Happy Viming!","4":"I routinely need to examine log files from production, and found the need to highlight and search multiple terms during the process. I took ideas from such scripts such as Highlighter.vim, MultipleSearch.vim and MultipleSearch2.vim and created a script to help me with the above task. In April, 2008, I rewrote the script virtually from scratch and over the last year and a half improved its functionality. I now submit the result of my efforts for the benefit of the Vim community.\r\n\r\nMulti Search enables highlighting (and searching) multiple search terms. Each defined search term's highlight state can be enabled or disabled. Searches can be performed on all the defined terms, all enabled terms, or on specific terms.\r\n\r\nOn platforms that support it, the Multi Search menu makes it easier to use some of the Multi Search commands. Multi Search also defines mappings for the more commonly used commands.\r\n\r\nAlthough it is marked as requiring Vim 7.2, the Multi Search plugin was developed and tested using Vim 7.1. Please see the installation instructions below. Once installed, detailed help can be obtained by\r\n\r\n\t:help Msearch\r\n\r\nEmail bug reports and enhancement requests to the author. Happy Viming!","install_details":"Multi Search comes packaged as a Vimball file. Source the vimball file to extract its contents:\r\n\r\n\t\t% vim multisearch.vimball\r\n\t\t:source %","5":"Multi Search comes packaged as a Vimball file. Source the vimball file to extract its contents:\r\n\r\n\t\t% vim multisearch.vimball\r\n\t\t:source %","first_name":"Mitanu","6":"Mitanu","last_name":"Paul","7":"Paul","releases":[{"0":"2826","vim_version":"7.0","1":"7.0","script_version":"0.8-unix","2":"0.8-unix","version_comment":"Updated with a vimball file with fileformat=unix so that it can be unpacked in non-DOS platforms. If you had trouble unpacking the vimball provided with the initial upload, please try again.","3":"Updated with a vimball file with fileformat=unix so that it can be unpacked in non-DOS platforms. If you had trouble unpacking the vimball provided with the initial upload, please try again.","package":"multisearch.vimball","4":"multisearch.vimball","src_id":"11627","5":"11627","creation_date":"1256865354","6":"1256865354"},{"0":"2826","vim_version":"7.2","1":"7.2","script_version":"0.8","2":"0.8","version_comment":"Initial upload","3":"Initial upload","package":"multisearch.vimball","4":"multisearch.vimball","src_id":"11601","5":"11601","creation_date":"1256607119","6":"1256607119"}]},"2825":{"script_id":"2825","0":"2825","script_name":"filter","1":"filter","script_type":"utility","2":"utility","summary":"apply filters to text, by filetype","3":"apply filters to text, by filetype","description":"You can filter text in vim by executing the following command \r\n:%!filter_executable\r\nWith an appropriate collection of filters, this feature can help to format text or source code, pretty print, or do advanced editing. \r\nHowever, each filter has to be in your $PATH (unless you want to specify the path manually), and you have to remember the name of the program.\r\nAlso, if you have many filters, organizing them can be complicated. You may be tempted to give them long names, or you may be feeling that you end up clogging your $PATH with numerous filters that you only use in rare situations.\r\n\r\nThis plugin helps to solve this problem. You maintain your filter scripts inside of your vim folder, in a folder 'filters' with subfolders per filetype (~\/.vim\/filters\/all for filters that are always available).\r\n\r\nYou can then apply a filter both with an Ex command (:Filter) and with a shortcut (\\f in normal mode, <C-L>f in insert mode, by default). The plugin looks in ~\/.vim\/filters for filter scripts appropriate to the file type, and allows you to select one, interactively. The given current range is then filtered through the script.","4":"You can filter text in vim by executing the following command \r\n:%!filter_executable\r\nWith an appropriate collection of filters, this feature can help to format text or source code, pretty print, or do advanced editing. \r\nHowever, each filter has to be in your $PATH (unless you want to specify the path manually), and you have to remember the name of the program.\r\nAlso, if you have many filters, organizing them can be complicated. You may be tempted to give them long names, or you may be feeling that you end up clogging your $PATH with numerous filters that you only use in rare situations.\r\n\r\nThis plugin helps to solve this problem. You maintain your filter scripts inside of your vim folder, in a folder 'filters' with subfolders per filetype (~\/.vim\/filters\/all for filters that are always available).\r\n\r\nYou can then apply a filter both with an Ex command (:Filter) and with a shortcut (\\f in normal mode, <C-L>f in insert mode, by default). The plugin looks in ~\/.vim\/filters for filter scripts appropriate to the file type, and allows you to select one, interactively. The given current range is then filtered through the script.","install_details":"Put filter.vim inside of your plugins folder\r\nCreate the folders ~\/.vim\/filters, and  ~\/.vim\/filters\/all.\r\nOrganize any filter scripts that you have by filetype and put them in ~\/.vim\/filters (e.g. ~\/.vim\/filters\/tex, ~\/.vim\/filters\/mail, ...)","5":"Put filter.vim inside of your plugins folder\r\nCreate the folders ~\/.vim\/filters, and  ~\/.vim\/filters\/all.\r\nOrganize any filter scripts that you have by filetype and put them in ~\/.vim\/filters (e.g. ~\/.vim\/filters\/tex, ~\/.vim\/filters\/mail, ...)","first_name":"Michael","6":"Michael","last_name":"Goerz","7":"Goerz","releases":[{"0":"2825","vim_version":"6.0","1":"6.0","script_version":"1.1","2":"1.1","version_comment":"you can now give additional command line flags to your filter","3":"you can now give additional command line flags to your filter","package":"filter.vim","4":"filter.vim","src_id":"11582","5":"11582","creation_date":"1256412168","6":"1256412168"},{"0":"2825","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"filter.vim","4":"filter.vim","src_id":"11581","5":"11581","creation_date":"1256411845","6":"1256411845"}]},"2824":{"script_id":"2824","0":"2824","script_name":"libperl.vim","1":"libperl.vim","script_type":"utility","2":"utility","summary":"provide standard vim functions for perl code","3":"provide standard vim functions for perl code","description":"git repository:   http:\/\/github.com\/c9s\/libperl.vim\r\n\r\n\r\nyou can just call those function by:\r\n\r\nlet retsult = libperl#whatever_function(  arg , arg2 )\r\n\r\nfunctions:\r\n\r\nfun! libperl#echo(msg)\r\nfun! libperl#get_perl_lib_paths()\r\nfun! libperl#get_module_file_path(mod)\r\nfun! libperl#tab_open_module_file_in_paths(mod)\r\nfun! libperl#tab_open_tag(tag)\r\nfun! libperl#translate_module_name(n)\r\nfun! libperl#open_tag(tag)\r\nfun! libperl#open_module()\r\nfun! libperl#get_cursor_module_name()\r\nfun! libperl#get_cursor_method_name()\r\nfun! libperl#find_method(method_name)\r\nfun! libperl#edit_file(fullpath,method)\r\nfun! libperl#tab_edit_file(fullpath,method)\r\nfun! libperl#tab_open_module_from_cursor()\r\nfun! libperl#open_module_in_paths(mod)\r\nfun! libperl#get_inc()\r\nfun! libperl#find_perl_package_files()\r\nfun! libperl#install_module()\r\nfun! libperl#get_package_sourcelist_path()\r\nfun! libperl#find_base_classes(file)\r\nfun! libperl#grep_file_functions(file)\r\nfun! libperl#parse_base_class_functions(filepath)\r\nfun! libperl#get_method_comp_refer_start()\r\nfun! libperl#get_method_comp_refer_base()\r\nfun! libperl#get_method_comp_start()\r\nfun! libperl#get_method_comp_base()\r\nfun! libperl#clear_method_comp_base()\r\nfun! libperl#get_pkg_comp_start()\r\nfun! libperl#get_pkg_comp_base()\r\nfun! libperl#use_ok(pkg)\r\nfun! libperl#get_cpan_module_list(force)\r\nfun! libperl#get_installed_cpan_module_list(force)\r\nfun! libperl#get_currentlib_cpan_module_list(force)\r\nfun! libperl#get_current_lib_package_name()\r\n","4":"git repository:   http:\/\/github.com\/c9s\/libperl.vim\r\n\r\n\r\nyou can just call those function by:\r\n\r\nlet retsult = libperl#whatever_function(  arg , arg2 )\r\n\r\nfunctions:\r\n\r\nfun! libperl#echo(msg)\r\nfun! libperl#get_perl_lib_paths()\r\nfun! libperl#get_module_file_path(mod)\r\nfun! libperl#tab_open_module_file_in_paths(mod)\r\nfun! libperl#tab_open_tag(tag)\r\nfun! libperl#translate_module_name(n)\r\nfun! libperl#open_tag(tag)\r\nfun! libperl#open_module()\r\nfun! libperl#get_cursor_module_name()\r\nfun! libperl#get_cursor_method_name()\r\nfun! libperl#find_method(method_name)\r\nfun! libperl#edit_file(fullpath,method)\r\nfun! libperl#tab_edit_file(fullpath,method)\r\nfun! libperl#tab_open_module_from_cursor()\r\nfun! libperl#open_module_in_paths(mod)\r\nfun! libperl#get_inc()\r\nfun! libperl#find_perl_package_files()\r\nfun! libperl#install_module()\r\nfun! libperl#get_package_sourcelist_path()\r\nfun! libperl#find_base_classes(file)\r\nfun! libperl#grep_file_functions(file)\r\nfun! libperl#parse_base_class_functions(filepath)\r\nfun! libperl#get_method_comp_refer_start()\r\nfun! libperl#get_method_comp_refer_base()\r\nfun! libperl#get_method_comp_start()\r\nfun! libperl#get_method_comp_base()\r\nfun! libperl#clear_method_comp_base()\r\nfun! libperl#get_pkg_comp_start()\r\nfun! libperl#get_pkg_comp_base()\r\nfun! libperl#use_ok(pkg)\r\nfun! libperl#get_cpan_module_list(force)\r\nfun! libperl#get_installed_cpan_module_list(force)\r\nfun! libperl#get_currentlib_cpan_module_list(force)\r\nfun! libperl#get_current_lib_package_name()\r\n","install_details":"just :\r\n\r\n$ make install","5":"just :\r\n\r\n$ make install","first_name":"Yo-An","6":"Yo-An","last_name":"Lin","7":"Lin","releases":[{"0":"2824","vim_version":"7.2","1":"7.2","script_version":"0.72","2":"0.72","version_comment":"release\n(This package is released by VIM::Packager http:\/\/github.com\/c9s\/vim-packager)\n","3":"release\n(This package is released by VIM::Packager http:\/\/github.com\/c9s\/vim-packager)\n","package":"libperl-vim-0.72.tar.gz","4":"libperl-vim-0.72.tar.gz","src_id":"11873","5":"11873","creation_date":"1260042195","6":"1260042195"},{"0":"2824","vim_version":"7.2","1":"7.2","script_version":"0.71","2":"0.71","version_comment":"module list cache dir\n(This package is released by VIM::Packager http:\/\/github.com\/c9s\/vim-packager)\n","3":"module list cache dir\n(This package is released by VIM::Packager http:\/\/github.com\/c9s\/vim-packager)\n","package":"libperl-vim-0.71.tar.gz","4":"libperl-vim-0.71.tar.gz","src_id":"11870","5":"11870","creation_date":"1260041932","6":"1260041932"},{"0":"2824","vim_version":"7.2","1":"7.2","script_version":"0.6","2":"0.6","version_comment":"update\n","3":"update\n","package":"libperl-vim-0.6.tar.gz","4":"libperl-vim-0.6.tar.gz","src_id":"11758","5":"11758","creation_date":"1258573355","6":"1258573355"},{"0":"2824","vim_version":"7.0","1":"7.0","script_version":"0.3","2":"0.3","version_comment":"Initial upload","3":"Initial upload","package":"libperl.tar.gz","4":"libperl.tar.gz","src_id":"11574","5":"11574","creation_date":"1256369287","6":"1256369287"}]},"2823":{"script_id":"2823","0":"2823","script_name":"baan.vim","1":"baan.vim","script_type":"indent","2":"indent","summary":"Indenting for Baan scripts","3":"Indenting for Baan scripts","description":"Hitherto I have not found an indent vim script for Baan. This is just a small indent file that works for baan scripts. \r\n\r\nVersion created: Gvim 7.2\r\n\r\nPlease let me know if there are any improvement\/bugs. \r\n\r\n","4":"Hitherto I have not found an indent vim script for Baan. This is just a small indent file that works for baan scripts. \r\n\r\nVersion created: Gvim 7.2\r\n\r\nPlease let me know if there are any improvement\/bugs. \r\n\r\n","install_details":"Place this file in the \"indent\" directory under the directory where vim is installed ($VIMHOME).\r\nIf your file has \".baan\" extension this should work automatically. If it does not for some reason or the other then\r\n                     \"set indentexpr=Get_Baan_Indent()\"\r\nAs an aside (and as a Baan coder) you might probably want to add this to your .vmrc:\r\n                    \"set filetype=baan\"  \r\n\r\n               \r\n","5":"Place this file in the \"indent\" directory under the directory where vim is installed ($VIMHOME).\r\nIf your file has \".baan\" extension this should work automatically. If it does not for some reason or the other then\r\n                     \"set indentexpr=Get_Baan_Indent()\"\r\nAs an aside (and as a Baan coder) you might probably want to add this to your .vmrc:\r\n                    \"set filetype=baan\"  \r\n\r\n               \r\n","first_name":"Rajesh","6":"Rajesh","last_name":"Kannan","7":"Kannan","releases":[{"0":"2823","vim_version":"7.0","1":"7.0","script_version":"0.22","2":"0.22","version_comment":"pre-processor definitions get indent of 0. ","3":"pre-processor definitions get indent of 0. ","package":"baan.vim","4":"baan.vim","src_id":"11595","5":"11595","creation_date":"1256552907","6":"1256552907"},{"0":"2823","vim_version":"7.0","1":"7.0","script_version":"0.21","2":"0.21","version_comment":"Double deduction of indents on \"endcase\". ","3":"Double deduction of indents on \"endcase\". ","package":"baan.vim","4":"baan.vim","src_id":"11571","5":"11571","creation_date":"1256305429","6":"1256305429"},{"0":"2823","vim_version":"7.0","1":"7.0","script_version":"0.2","2":"0.2","version_comment":"In v0.1 only 3GL was indented.\r\nAdded indenting for 4GL syntax as well. \r\nPlease let me know if there are any bugs. Thanks!","3":"In v0.1 only 3GL was indented.\r\nAdded indenting for 4GL syntax as well. \r\nPlease let me know if there are any bugs. Thanks!","package":"baan.vim","4":"baan.vim","src_id":"11569","5":"11569","creation_date":"1256294381","6":"1256294381"},{"0":"2823","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"baan.vim","4":"baan.vim","src_id":"11567","5":"11567","creation_date":"1256283881","6":"1256283881"}]},"2822":{"script_id":"2822","0":"2822","script_name":"unicode.vim","1":"unicode.vim","script_type":"utility","2":"utility","summary":"Various enhancements for using unicode and digraphs with Vim","3":"Various enhancements for using unicode and digraphs with Vim","description":"Basically, this plugin serves 3 purposes:\r\n\r\n1. Complete Characters\r\n\r\nA custom completion function is available to complete characters using their Unicode name or Codepoint. If a digraph exists for that character, it will be displayed in paranthesis. Press Ctrl-X Ctrl-Z to trigger this completion from insert mode. Also a new custom completion for digraph chars is available. Press Ctrl-X Ctrl-G to trigger this completion. It will display all digraphs, that are reachable from the previous typed letter.\r\n\r\n2. Identify Characters\r\n\r\nThe :UnicodeName command can be used to identify the character under the cursor. This works similar to the builtin ga command (in fact, the help also states a possibility to map this command to the ga builtin command), but it also displays the digraph character (if it exists) and the HTML entity.\r\nThe :SearchUnicode command can be used to search in the unicode character table to search for a certain unicode character with a given name or value.\r\nThe :UnicodeTable can be used to generate an Unicode table, including HTML entity names and Digraph chars. The UnicodeTable will be nicely syntax highlighted.\r\n\r\n3. Ease the use of Digraphs\r\n\r\nUse the :Digraphs command to search for an digraph with the given name (e.g. :Digraphs copy will display all digraphs that will create a character name which contains copy in its name). You can also search for the decimal value. This plugin also maps the key <F4> that will allow to transform 2 given normal chars into their digraph char.\r\n\r\nFor a screenshot, see: https:\/\/chrisbra.github.io\/vim-screencasts\/unicode-screencast.gif \r\nNote: the development version of this plugin is available at github: https:\/\/github.com\/chrisbra\/unicode.vim\r\n\r\nHere is a short overview of the functionality provided by the plugin:\r\n\r\nEx commands:\r\n    :Digraphs        - Search for specific digraph char\r\n    :SearchUnicode   - Search for specific unicode char\r\n    :UnicodeName     - Identify character under cursor (like ga command)\r\n    :UnicodeTable    - Print Unicode Table in new window\r\n    :DownloadUnicode - Download (or update) Unicode data\r\n\r\nNormal mode commands:\r\n    <C-X><C-G>  - Complete Digraph char\r\n    <C-X><C-Z>  - Complete Unicode char\r\n    <F4>        - Combine characters into digraphs\r\n\r\nScripting Functions:\r\n    unicode#FindUnicodeBy() - Find unicode characters\r\n    unicode#FindDigraphBy() - Find Digraph char\r\n    unicode#Digraph()       - Returns digraph char\r\n    unicode#UnicodeName()   - Identifies unicode character (by value)","4":"Basically, this plugin serves 3 purposes:\r\n\r\n1. Complete Characters\r\n\r\nA custom completion function is available to complete characters using their Unicode name or Codepoint. If a digraph exists for that character, it will be displayed in paranthesis. Press Ctrl-X Ctrl-Z to trigger this completion from insert mode. Also a new custom completion for digraph chars is available. Press Ctrl-X Ctrl-G to trigger this completion. It will display all digraphs, that are reachable from the previous typed letter.\r\n\r\n2. Identify Characters\r\n\r\nThe :UnicodeName command can be used to identify the character under the cursor. This works similar to the builtin ga command (in fact, the help also states a possibility to map this command to the ga builtin command), but it also displays the digraph character (if it exists) and the HTML entity.\r\nThe :SearchUnicode command can be used to search in the unicode character table to search for a certain unicode character with a given name or value.\r\nThe :UnicodeTable can be used to generate an Unicode table, including HTML entity names and Digraph chars. The UnicodeTable will be nicely syntax highlighted.\r\n\r\n3. Ease the use of Digraphs\r\n\r\nUse the :Digraphs command to search for an digraph with the given name (e.g. :Digraphs copy will display all digraphs that will create a character name which contains copy in its name). You can also search for the decimal value. This plugin also maps the key <F4> that will allow to transform 2 given normal chars into their digraph char.\r\n\r\nFor a screenshot, see: https:\/\/chrisbra.github.io\/vim-screencasts\/unicode-screencast.gif \r\nNote: the development version of this plugin is available at github: https:\/\/github.com\/chrisbra\/unicode.vim\r\n\r\nHere is a short overview of the functionality provided by the plugin:\r\n\r\nEx commands:\r\n    :Digraphs        - Search for specific digraph char\r\n    :SearchUnicode   - Search for specific unicode char\r\n    :UnicodeName     - Identify character under cursor (like ga command)\r\n    :UnicodeTable    - Print Unicode Table in new window\r\n    :DownloadUnicode - Download (or update) Unicode data\r\n\r\nNormal mode commands:\r\n    <C-X><C-G>  - Complete Digraph char\r\n    <C-X><C-Z>  - Complete Unicode char\r\n    <F4>        - Combine characters into digraphs\r\n\r\nScripting Functions:\r\n    unicode#FindUnicodeBy() - Find unicode characters\r\n    unicode#FindDigraphBy() - Find Digraph char\r\n    unicode#Digraph()       - Returns digraph char\r\n    unicode#UnicodeName()   - Identifies unicode character (by value)","install_details":"simply source the file and the plugin will be installed automatically\r\n:e unicode-<nr>.vmb\r\n:so %\r\n\r\nAnd afterwards, have a look at the documentation: :h unicode.txt\r\n\r\nAlternatively, use the plugin manager of your choice.","5":"simply source the file and the plugin will be installed automatically\r\n:e unicode-<nr>.vmb\r\n:so %\r\n\r\nAnd afterwards, have a look at the documentation: :h unicode.txt\r\n\r\nAlternatively, use the plugin manager of your choice.","first_name":"Christian","6":"Christian","last_name":"Brabandt","7":"Brabandt","releases":[{"0":"2822","vim_version":"7.4","1":"7.4","script_version":"21","2":"21","version_comment":"This is release 0.21\n(automatically uploaded)","3":"This is release 0.21\n(automatically uploaded)","package":"unicode.vim-0.21.vmb","4":"unicode.vim-0.21.vmb","src_id":"25588","5":"25588","creation_date":"1506492369","6":"1506492369"},{"0":"2822","vim_version":"7.4","1":"7.4","script_version":"20","2":"20","version_comment":"- unicode#Digraph expects a 2 char string\n- Install a QuitPre autocommand for :UnicodeTable\n- Make :Digraphs! output the digraph name\n(automatically uploaded)","3":"- unicode#Digraph expects a 2 char string\n- Install a QuitPre autocommand for :UnicodeTable\n- Make :Digraphs! output the digraph name\n(automatically uploaded)","package":"unicode-0.20.vmb","4":"unicode-0.20.vmb","src_id":"22794","5":"22794","creation_date":"1421351483","6":"1421351483"},{"0":"2822","vim_version":"7.4","1":"7.4","script_version":"19","2":"19","version_comment":"- |:UnicodeName| shows all digraphs per character\n- |:UnicodeName| shows decimal value for glyph\n- |:SearchUnicode| search unicode character by name or value\n- Make functions publicly available (|unicode#Digraphs()|, |unicode#Digraph()|, |unicode#FindUnicodeBy()|, |unicode#UnicodeName()|)\n- cache UnicodeData.txt file in VimL dictionary format (so reading will be faster)\n- Performance tuning, more comments, better error handling\n- All configuration variables have a common g:Unicode... prefix\n- document |<Plug>(UnicodeGA)|\n- Always display digraph char when completing unicode char (and a digraph is available).\n- Unicode completion always available using <C-X><C-Z>\n- Therefore removed |:EnableUnicodeCompletion| and |:DisableUnicodeCompletion| commands\n- too slow unicode completions will be stopped after 2 seconds\n- fix annoying new line bug, when using digraph generation in visual mode\n- new command |:UnicodeTable|\n- new command |:DownloadUnicode| (including syntax highlighting)\n(automatically uploaded)","3":"- |:UnicodeName| shows all digraphs per character\n- |:UnicodeName| shows decimal value for glyph\n- |:SearchUnicode| search unicode character by name or value\n- Make functions publicly available (|unicode#Digraphs()|, |unicode#Digraph()|, |unicode#FindUnicodeBy()|, |unicode#UnicodeName()|)\n- cache UnicodeData.txt file in VimL dictionary format (so reading will be faster)\n- Performance tuning, more comments, better error handling\n- All configuration variables have a common g:Unicode... prefix\n- document |<Plug>(UnicodeGA)|\n- Always display digraph char when completing unicode char (and a digraph is available).\n- Unicode completion always available using <C-X><C-Z>\n- Therefore removed |:EnableUnicodeCompletion| and |:DisableUnicodeCompletion| commands\n- too slow unicode completions will be stopped after 2 seconds\n- fix annoying new line bug, when using digraph generation in visual mode\n- new command |:UnicodeTable|\n- new command |:DownloadUnicode| (including syntax highlighting)\n(automatically uploaded)","package":"unicode-0.19.vmb","4":"unicode-0.19.vmb","src_id":"21785","5":"21785","creation_date":"1397684692","6":"1397684692"},{"0":"2822","vim_version":"7.4","1":"7.4","script_version":"18","2":"18","version_comment":"- include mapping for easier digraph generation\n- fix wrong display of :Digraphs 57344\n- |:Digraphs| can also search for unicode name\n(automatically uploaded)","3":"- include mapping for easier digraph generation\n- fix wrong display of :Digraphs 57344\n- |:Digraphs| can also search for unicode name\n(automatically uploaded)","package":"unicode-0.18.vmb","4":"unicode-0.18.vmb","src_id":"21685","5":"21685","creation_date":"1395959611","6":"1395959611"},{"0":"2822","vim_version":"7.3","1":"7.3","script_version":"17","2":"17","version_comment":"- disable preview window (for completing unicode chars) by default, can be enabled by setting the variable g:UnicodeShowPreviewWindow (patch by Marcin Szamotulski, thanks!)\n(automatically uploaded)","3":"- disable preview window (for completing unicode chars) by default, can be enabled by setting the variable g:UnicodeShowPreviewWindow (patch by Marcin Szamotulski, thanks!)\n(automatically uploaded)","package":"unicode-0.17.vmb","4":"unicode-0.17.vmb","src_id":"20656","5":"20656","creation_date":"1376549664","6":"1376549664"},{"0":"2822","vim_version":"7.3","1":"7.3","script_version":"16","2":"16","version_comment":":UnicodeName returns html entity, if possible\n(automatically uploaded)","3":":UnicodeName returns html entity, if possible\n(automatically uploaded)","package":"unicode-0.16.vmb","4":"unicode-0.16.vmb","src_id":"19522","5":"19522","creation_date":"1361051685","6":"1361051685"},{"0":"2822","vim_version":"7.3","1":"7.3","script_version":"15","2":"15","version_comment":"- make sure, the returned digraphs list is not empty.\n(automatically uploaded)","3":"- make sure, the returned digraphs list is not empty.\n(automatically uploaded)","package":"unicode-0.15.vmb","4":"unicode-0.15.vmb","src_id":"19476","5":"19476","creation_date":"1360094154","6":"1360094154"},{"0":"2822","vim_version":"7.3","1":"7.3","script_version":"14","2":"14","version_comment":"Added command :Digraphs for better output of digraphs\n(automatically uploaded)","3":"Added command :Digraphs for better output of digraphs\n(automatically uploaded)","package":"unicode-0.14.vmb","4":"unicode-0.14.vmb","src_id":"19074","5":"19074","creation_date":"1354393510","6":"1354393510"},{"0":"2822","vim_version":"7.3","1":"7.3","script_version":"13","2":"13","version_comment":"- better output for |UnicodeName| (did previously hide messages)\n(automatically uploaded)","3":"- better output for |UnicodeName| (did previously hide messages)\n(automatically uploaded)","package":"unicode-0.13.vmb","4":"unicode-0.13.vmb","src_id":"18569","5":"18569","creation_date":"1347137659","6":"1347137659"},{"0":"2822","vim_version":"7.3","1":"7.3","script_version":"12","2":"12","version_comment":"- UnicodeName shows digraph, if it exists\n- better completion of digraphs\n(automatically uploaded)","3":"- UnicodeName shows digraph, if it exists\n- better completion of digraphs\n(automatically uploaded)","package":"unicode-0.12.vmb","4":"unicode-0.12.vmb","src_id":"17762","5":"17762","creation_date":"1334257424","6":"1334257424"},{"0":"2822","vim_version":"7.3","1":"7.3","script_version":"10","2":"10","version_comment":"- enable completing of only the names\r\n- Really disable the 'completefunc' when disabling the function","3":"- enable completing of only the names\r\n- Really disable the 'completefunc' when disabling the function","package":"unicode-0.10.vmb","4":"unicode-0.10.vmb","src_id":"17070","5":"17070","creation_date":"1323960837","6":"1323960837"},{"0":"2822","vim_version":"7.3","1":"7.3","script_version":"9","2":"9","version_comment":":UnicodeName checks for existence of UnicodeData.txt\n:UnicodeName now also detects combined chars\n:UnicodeName now also outputs control chars\n(automatically uploaded)","3":":UnicodeName checks for existence of UnicodeData.txt\n:UnicodeName now also detects combined chars\n:UnicodeName now also outputs control chars\n(automatically uploaded)","package":"unicode-0.9.vba","4":"unicode-0.9.vba","src_id":"16111","5":"16111","creation_date":"1311193450","6":"1311193450"},{"0":"2822","vim_version":"7.3","1":"7.3","script_version":"0.8","2":"0.8","version_comment":" New Release\n- Fix an issue with configuring the plugin (Thanks jgm)\n- Code cleanup\n- Make use of the preview window, when completing\n  Digraph or Unicode Glyphs\n- By default, the Digraph Glyphs will now be enabled\n  using |i_Ctrl-X_CTRL-G| instead of using\n  Ctrl-X_Ctrl-C which wouldn't work in a terminal\n- |:UnicodeName| now displays the hexadecimal Unicode\n  Codepoint instead of the decimal one (as this seems\n  to be the official way to display unicode\n  codepoints).\n","3":" New Release\n- Fix an issue with configuring the plugin (Thanks jgm)\n- Code cleanup\n- Make use of the preview window, when completing\n  Digraph or Unicode Glyphs\n- By default, the Digraph Glyphs will now be enabled\n  using |i_Ctrl-X_CTRL-G| instead of using\n  Ctrl-X_Ctrl-C which wouldn't work in a terminal\n- |:UnicodeName| now displays the hexadecimal Unicode\n  Codepoint instead of the decimal one (as this seems\n  to be the official way to display unicode\n  codepoints).\n","package":"unicode.vba","4":"unicode.vba","src_id":"13962","5":"13962","creation_date":"1285872895","6":"1285872895"},{"0":"2822","vim_version":"7.3","1":"7.3","script_version":"0.7","2":"0.7","version_comment":"\n- Determine the Name of a Character using :UnicodeName\n- the global variable g:enableUnicodeCompletion determines, whether the completion will be loaded automatically","3":"\n- Determine the Name of a Character using :UnicodeName\n- the global variable g:enableUnicodeCompletion determines, whether the completion will be loaded automatically","package":"unicode.vba","4":"unicode.vba","src_id":"13899","5":"13899","creation_date":"1285274649","6":"1285274649"},{"0":"2822","vim_version":"7.2","1":"7.2","script_version":"0.6","2":"0.6","version_comment":"- many small bugfixes with regard to error-handling and error displaying\n- use default netrw_http_cmd (instead of hardwiring wget)\n- small documentation update (Inlude a snippet of UnicodeData.txt and get rid of Index.txt data)","3":"- many small bugfixes with regard to error-handling and error displaying\n- use default netrw_http_cmd (instead of hardwiring wget)\n- small documentation update (Inlude a snippet of UnicodeData.txt and get rid of Index.txt data)","package":"unicode-0.6.vba","4":"unicode-0.6.vba","src_id":"13680","5":"13680","creation_date":"1282824110","6":"1282824110"},{"0":"2822","vim_version":"7.0","1":"7.0","script_version":"0.5","2":"0.5","version_comment":"New public repository at http:\/\/github.com\/chrisbra\/unicode.vim","3":"New public repository at http:\/\/github.com\/chrisbra\/unicode.vim","package":"unicode.vba","4":"unicode.vba","src_id":"12871","5":"12871","creation_date":"1271711034","6":"1271711034"},{"0":"2822","vim_version":"7.0","1":"7.0","script_version":"0.4","2":"0.4","version_comment":"Use UnicodeData.txt to generate Data\r\n(Index.txt does not contain all glyphs).\r\nCheck for empty file UnicodeData.txt\r\n","3":"Use UnicodeData.txt to generate Data\r\n(Index.txt does not contain all glyphs).\r\nCheck for empty file UnicodeData.txt\r\n","package":"unicode.vba","4":"unicode.vba","src_id":"12268","5":"12268","creation_date":"1265056668","6":"1265056668"},{"0":"2822","vim_version":"7.0","1":"7.0","script_version":"0.3","2":"0.3","version_comment":"Added digraph completion\r\n","3":"Added digraph completion\r\n","package":"unicode.vba","4":"unicode.vba","src_id":"11600","5":"11600","creation_date":"1256599389","6":"1256599389"},{"0":"2822","vim_version":"7.0","1":"7.0","script_version":"0.2","2":"0.2","version_comment":"Enabled GetLatestVimScripts","3":"Enabled GetLatestVimScripts","package":"unicode.vba","4":"unicode.vba","src_id":"11564","5":"11564","creation_date":"1256248538","6":"1256248538"},{"0":"2822","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"unicode.vba","4":"unicode.vba","src_id":"11563","5":"11563","creation_date":"1256248115","6":"1256248115"}]},"2821":{"script_id":"2821","0":"2821","script_name":"sqlplus.vim","1":"sqlplus.vim","script_type":"utility","2":"utility","summary":" Execute SQL queries and commands from within VIM (using Oracle's SQL*Plus)","3":" Execute SQL queries and commands from within VIM (using Oracle's SQL*Plus)","description":"This file contains routines that may be used to execute SQL queries and describe\r\ntables from within VIM.  It depends on SQL*Plus.  You must have $ORACLE_HOME\r\n$ORACLE_SID set in your environment, although you can explicitly set the\r\ndatabase name to use with the :DB <db-name> command.\r\n\r\nIn command mode:\r\n  <F7>: execute the whole script without applying any changes to it\r\n  <F8>: execute the SELECT query under your cursor.  The query must begin with\r\n        the \"select\" keyword and end with a \";\"\r\n  <Leader><F8>: prompt for an SQL command\/query to execute.\r\n  <F9>: treat the identifier under the cursor as a table name, and do a 'describe'\r\n        on it.\r\n  <F10>: prompt for a table to describe.\r\n  <Leader>sb: open an empty buffer in a new window to enter SQL commands in\r\n  <Leader>ss: execute the (one-line) query on the current line\r\n  <Leader>se: execute the query under the cursor (as <F8>)\r\n  <Leader>st: describe the table under the cursor (as <F9>)\r\n  <Leader>sc: open the user's common SQL buffer (g:sqlplus_common_buffer) in a\r\n              new window.\r\n\r\n  :Select <...> -- execute the given Select query.\r\n  :Update <...> -- execute the given Update command.\r\n  :Delete <...> -- execute the given Delete command\r\n  :DB <db-name> -- set the database name to <db-name>\r\n  :SQL <...> -- open a blank SQL buffer in a new window, or if a filename is\r\n                specified, open the given file in a new window.\r\n\r\nIn visual mode:\r\n  <F8>: execute the selected query\r\n\r\nIf queries contain bind variables, you will be prompted to give a value for each\r\none.  if the value is a string, you must explicitly put quotes around it.  If the\r\nquery contains an INTO clause, it is removed before executing.\r\n\r\nYou will be prompted for your user-name, password and tnsname the first time you access\r\none of these functions during a session.  After that, your user-id and password\r\nwill be remembered until the session ends.\r\n\r\nThe results of the query\/command are displayed in a separate window.\r\n\r\nYou can specify the values of the following global variables in your .vimrc\r\nfile, to alter the behavior of this plugin:\r\n\r\n  g:sqlplus_userid -- the user-id to log in to the database as.  If this\r\n      is specified, g:sqlplus_passwd must be given as well, which is the\r\n      password to use.  Default: \"\"\r\n  g:sqlplus_path -- the path the the SQL*Plus executable, including any\r\n      command line options.  Default: $ORACLE_HOME . \"\/bin\/sqlplus -s\"\r\n  g:sqlplus_common_commands -- any SQL*Plus commands that should be\r\n      executed every time SQL*Plus is invoked.\r\n      Default: \"set pagesize 10000\\nset wrap off\\nset linesize 9999\\n\"\r\n  g:sqlplus_common_buffer -- the name of a file that will contain\r\n      common SQL queries and expressions, that may be opened via the\r\n      <Leader>sc command.\r\n  g:sqlplus_db -- the name of the database to connect to.  This variable\r\n      may also be modified via the :DB command.\r\n\r\nAll the honor goes to Jamis Buck \"http:\/\/www.vim.org\/account\/profile.php?user_id=261\" who wrote the  first version \"http:\/\/www.vim.org\/scripts\/script.php?script_id=97\" of this script. Unfortunately I can not maintain his original script, so I had to fork it.","4":"This file contains routines that may be used to execute SQL queries and describe\r\ntables from within VIM.  It depends on SQL*Plus.  You must have $ORACLE_HOME\r\n$ORACLE_SID set in your environment, although you can explicitly set the\r\ndatabase name to use with the :DB <db-name> command.\r\n\r\nIn command mode:\r\n  <F7>: execute the whole script without applying any changes to it\r\n  <F8>: execute the SELECT query under your cursor.  The query must begin with\r\n        the \"select\" keyword and end with a \";\"\r\n  <Leader><F8>: prompt for an SQL command\/query to execute.\r\n  <F9>: treat the identifier under the cursor as a table name, and do a 'describe'\r\n        on it.\r\n  <F10>: prompt for a table to describe.\r\n  <Leader>sb: open an empty buffer in a new window to enter SQL commands in\r\n  <Leader>ss: execute the (one-line) query on the current line\r\n  <Leader>se: execute the query under the cursor (as <F8>)\r\n  <Leader>st: describe the table under the cursor (as <F9>)\r\n  <Leader>sc: open the user's common SQL buffer (g:sqlplus_common_buffer) in a\r\n              new window.\r\n\r\n  :Select <...> -- execute the given Select query.\r\n  :Update <...> -- execute the given Update command.\r\n  :Delete <...> -- execute the given Delete command\r\n  :DB <db-name> -- set the database name to <db-name>\r\n  :SQL <...> -- open a blank SQL buffer in a new window, or if a filename is\r\n                specified, open the given file in a new window.\r\n\r\nIn visual mode:\r\n  <F8>: execute the selected query\r\n\r\nIf queries contain bind variables, you will be prompted to give a value for each\r\none.  if the value is a string, you must explicitly put quotes around it.  If the\r\nquery contains an INTO clause, it is removed before executing.\r\n\r\nYou will be prompted for your user-name, password and tnsname the first time you access\r\none of these functions during a session.  After that, your user-id and password\r\nwill be remembered until the session ends.\r\n\r\nThe results of the query\/command are displayed in a separate window.\r\n\r\nYou can specify the values of the following global variables in your .vimrc\r\nfile, to alter the behavior of this plugin:\r\n\r\n  g:sqlplus_userid -- the user-id to log in to the database as.  If this\r\n      is specified, g:sqlplus_passwd must be given as well, which is the\r\n      password to use.  Default: \"\"\r\n  g:sqlplus_path -- the path the the SQL*Plus executable, including any\r\n      command line options.  Default: $ORACLE_HOME . \"\/bin\/sqlplus -s\"\r\n  g:sqlplus_common_commands -- any SQL*Plus commands that should be\r\n      executed every time SQL*Plus is invoked.\r\n      Default: \"set pagesize 10000\\nset wrap off\\nset linesize 9999\\n\"\r\n  g:sqlplus_common_buffer -- the name of a file that will contain\r\n      common SQL queries and expressions, that may be opened via the\r\n      <Leader>sc command.\r\n  g:sqlplus_db -- the name of the database to connect to.  This variable\r\n      may also be modified via the :DB command.\r\n\r\nAll the honor goes to Jamis Buck \"http:\/\/www.vim.org\/account\/profile.php?user_id=261\" who wrote the  first version \"http:\/\/www.vim.org\/scripts\/script.php?script_id=97\" of this script. Unfortunately I can not maintain his original script, so I had to fork it.","install_details":"Copy the sqlplus.vim script to your $HOME\/.vim\/plugin directory to install it for your user or copy it into $VIM_INSTALLATION_PATH\/plugin to install it for all users on this server.  Make sure you have set ORACLE_HOME in your environment, to point to the root of your oracle installation.  (ie, $ORACLE_HOME\/bin should contain sqlplus).","5":"Copy the sqlplus.vim script to your $HOME\/.vim\/plugin directory to install it for your user or copy it into $VIM_INSTALLATION_PATH\/plugin to install it for all users on this server.  Make sure you have set ORACLE_HOME in your environment, to point to the root of your oracle installation.  (ie, $ORACLE_HOME\/bin should contain sqlplus).","first_name":"Dani","6":"Dani","last_name":"Rey","7":"Rey","releases":[{"0":"2821","vim_version":"6.0","1":"6.0","script_version":"2.0.0","2":"2.0.0","version_comment":"Initial upload","3":"Initial upload","package":"sqlplus.vim","4":"sqlplus.vim","src_id":"11561","5":"11561","creation_date":"1256232300","6":"1256232300"}]},"2820":{"script_id":"2820","0":"2820","script_name":"DBGp-client","1":"DBGp-client","script_type":"utility","2":"utility","summary":"Initial upload","3":"Initial upload","description":"This is a small modification of Ethan McCreadie's version, itself a modification of \r\nSeung Woo Shin's XDebug remote debugger: http:\/\/www.vim.org\/scripts\/script.php?script_id=2218\r\n\r\nIt fixes a bug I encountered when adding a breakpoint to a remote file on a local mount.","4":"This is a small modification of Ethan McCreadie's version, itself a modification of \r\nSeung Woo Shin's XDebug remote debugger: http:\/\/www.vim.org\/scripts\/script.php?script_id=2218\r\n\r\nIt fixes a bug I encountered when adding a breakpoint to a remote file on a local mount.","install_details":"Just untar these files and place them in your .vim\/plugin directory.","5":"Just untar these files and place them in your .vim\/plugin directory.","first_name":"Julien","6":"Julien","last_name":"...","7":"...","releases":[{"0":"2820","vim_version":"6.0","1":"6.0","script_version":"0.12","2":"0.12","version_comment":"Initial upload","3":"Initial upload","package":"debugger.tar.gz","4":"debugger.tar.gz","src_id":"11560","5":"11560","creation_date":"1256226519","6":"1256226519"}]},"2819":{"script_id":"2819","0":"2819","script_name":"smarty syntax","1":"smarty syntax","script_type":"syntax","2":"syntax","summary":"Syntax highlight for Smarty Template Engine","3":"Syntax highlight for Smarty Template Engine","description":"Bug fix of script: http:\/\/www.vim.org\/scripts\/script.php?script_id=1798","4":"Bug fix of script: http:\/\/www.vim.org\/scripts\/script.php?script_id=1798","install_details":"See http:\/\/www.vim.org\/scripts\/script.php?script_id=1798","5":"See http:\/\/www.vim.org\/scripts\/script.php?script_id=1798","first_name":"Rodrigo","6":"Rodrigo","last_name":"Machado","7":"Machado","releases":[{"0":"2819","vim_version":"6.0","1":"6.0","script_version":"1","2":"1","version_comment":"Initial upload","3":"Initial upload","package":"smarty.vim","4":"smarty.vim","src_id":"11553","5":"11553","creation_date":"1256053691","6":"1256053691"}]},"2818":{"script_id":"2818","0":"2818","script_name":"Asneeded 2","1":"Asneeded 2","script_type":"utility","2":"utility","summary":"Load scripts as needed","3":"Load scripts as needed","description":"Asneeded allows loading a script by the name of a command or function that\r\nthe script defines.  You can use :AN to load by a command; functions are\r\nloaded automatically (via FuncUndefined).\r\n\r\nExample (this is supposed to work with the default setup):\r\n\r\n\t:AN ANedit\r\n\r\nThis will source the script  AsNeeded\/anplus.vim  (located below the\r\n'runtimepath') which defines the :ANedit command.\r\n\r\nBefore :AN can be used, user scripts need to be scanned with :ANmakeTags to\r\ncreate ANtags files.  These files (like normal tags files) map commands and\r\nfunctions to script file names.  In order to find ANtags files,\r\ng:asneeded_path needs to be set up properly.\r\n\r\nThis script has the same purpose as the AsNeeded plugin created by DrChip\r\n(vimscript #915).\r\n\r\nThe ANtags file format is compatible, but paths included in file names are\r\nnot recognized.  In other words, each directory needs its own ANtags file.\r\n\r\n\r\nComparison (not to be taken too seriously...) of both scripts:\r\n\r\nAdvantages:\r\n- no creation of temporary buffers\r\n- configurable load path (load scripts from more than one location)\r\n- command-line completion instead of a menu\r\n- :ANmakeTags creates tags for certain files, not for a whole directory\r\n- :AN only loads a script if the command argument is not defined yet\r\n- single tags can be disabled in the ANtags file to solve ambiguities\r\n\r\nLeft Offs:\r\n- mappings are not recognized (at least not per default)\r\n- no \"on-the-fly\" mode: search for functions and commands requires an ANtags\r\n  file\r\n- :AN only takes a command name as argument (not a function name)\r\n- no creation of skeleton commands (beyond purpose)\r\n\r\nDrChip's AsNeeded version: 17c","4":"Asneeded allows loading a script by the name of a command or function that\r\nthe script defines.  You can use :AN to load by a command; functions are\r\nloaded automatically (via FuncUndefined).\r\n\r\nExample (this is supposed to work with the default setup):\r\n\r\n\t:AN ANedit\r\n\r\nThis will source the script  AsNeeded\/anplus.vim  (located below the\r\n'runtimepath') which defines the :ANedit command.\r\n\r\nBefore :AN can be used, user scripts need to be scanned with :ANmakeTags to\r\ncreate ANtags files.  These files (like normal tags files) map commands and\r\nfunctions to script file names.  In order to find ANtags files,\r\ng:asneeded_path needs to be set up properly.\r\n\r\nThis script has the same purpose as the AsNeeded plugin created by DrChip\r\n(vimscript #915).\r\n\r\nThe ANtags file format is compatible, but paths included in file names are\r\nnot recognized.  In other words, each directory needs its own ANtags file.\r\n\r\n\r\nComparison (not to be taken too seriously...) of both scripts:\r\n\r\nAdvantages:\r\n- no creation of temporary buffers\r\n- configurable load path (load scripts from more than one location)\r\n- command-line completion instead of a menu\r\n- :ANmakeTags creates tags for certain files, not for a whole directory\r\n- :AN only loads a script if the command argument is not defined yet\r\n- single tags can be disabled in the ANtags file to solve ambiguities\r\n\r\nLeft Offs:\r\n- mappings are not recognized (at least not per default)\r\n- no \"on-the-fly\" mode: search for functions and commands requires an ANtags\r\n  file\r\n- :AN only takes a command name as argument (not a function name)\r\n- no creation of skeleton commands (beyond purpose)\r\n\r\nDrChip's AsNeeded version: 17c","install_details":"Notes:\r\n- Asneeded comes in a ZIP-archive, easy to inspect with your file manager.\r\n- There is a new folder \"AsNeeded\".\r\n\r\nYou can now unpack (to ~\\vimfiles or ~\/.vim ...) and do :helptags\r\n\r\nYet to be tested on Unix.","5":"Notes:\r\n- Asneeded comes in a ZIP-archive, easy to inspect with your file manager.\r\n- There is a new folder \"AsNeeded\".\r\n\r\nYou can now unpack (to ~\\vimfiles or ~\/.vim ...) and do :helptags\r\n\r\nYet to be tested on Unix.","first_name":"Andy","6":"Andy","last_name":"Wokula","7":"Wokula","releases":[{"0":"2818","vim_version":"7.0","1":"7.0","script_version":"0.1.1","2":"0.1.1","version_comment":"BF: didn't ignore entries with paths in ANtags files","3":"BF: didn't ignore entries with paths in ANtags files","package":"asneeded_0.1.1.zip","4":"asneeded_0.1.1.zip","src_id":"11552","5":"11552","creation_date":"1256035055","6":"1256035055"},{"0":"2818","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"asneeded.zip","4":"asneeded.zip","src_id":"11551","5":"11551","creation_date":"1255988657","6":"1255988657"}]},"2817":{"script_id":"2817","0":"2817","script_name":"testname","1":"testname","script_type":"utility","2":"utility","summary":"Generate unused file name for testing purpose","3":"Generate unused file name for testing purpose","description":"Get an unused file name for testing purpose.\r\n\r\nFile names are counted A1,A2,..,A9,B10,..,B99,C100,..  Several \"sets\" can be\r\ndefined.  A set specifies path and extension of the file name to be\r\ngenerated.  Files named \"lastnr.dat\" maintain the counter(s) for each set.\r\nSelect a set with a KEY.  An expr-abbr is a useful way to trigger the\r\nfunctions.\r\n\r\nUsage: edit a new test file:\r\n    :new tn#\r\n\r\nCustomization: variables in the vimrc\r\n\r\ng:testname#set    (dictionary)\r\n\r\n    :let g:testname#set = {}\r\n    :let g:testname#set[KEY] = { \"ext\": EXT, \"path\": PATH [, \"lnk\": LNPK] }\r\n    :...\r\n    \r\n    KEY - (string) the selector; for use in the abbreviation, e.g. \"vim\"\r\n    EXT - (string) extension for the file name to be generated, e.g. \".vim\"\r\n    PATH - (string) path in which to create the new files and \"lastnr.dat\"\r\n        (user creates the files, script only creates lastnr.dat)\r\n    LNPK - (string) optional selector to choose the path for lastnr.dat from\r\n        another set; \"LastNr.dat Path Key\".  Makes it possible to have a\r\n        single lastnr.dat file for all paths.\r\n    \r\n    * You can overwrite the one default KEY \"vim\".\r\n    * Different KEYs can share PATH (the lastnr file contains a line for\r\n      each KEY), only PATH + EXT must be unique (in general).\r\n\r\ng:testname#lastnrfile\t    (string)\r\n\r\n    name of lastnr-file in PATH; must be given without (esp. absolute) path;\r\n    default is \"lastnr.dat\"\r\n\r\ng:testname#firstnr    (string)\r\n\r\n    first \"number\" to be used, default \"A1\"\r\n","4":"Get an unused file name for testing purpose.\r\n\r\nFile names are counted A1,A2,..,A9,B10,..,B99,C100,..  Several \"sets\" can be\r\ndefined.  A set specifies path and extension of the file name to be\r\ngenerated.  Files named \"lastnr.dat\" maintain the counter(s) for each set.\r\nSelect a set with a KEY.  An expr-abbr is a useful way to trigger the\r\nfunctions.\r\n\r\nUsage: edit a new test file:\r\n    :new tn#\r\n\r\nCustomization: variables in the vimrc\r\n\r\ng:testname#set    (dictionary)\r\n\r\n    :let g:testname#set = {}\r\n    :let g:testname#set[KEY] = { \"ext\": EXT, \"path\": PATH [, \"lnk\": LNPK] }\r\n    :...\r\n    \r\n    KEY - (string) the selector; for use in the abbreviation, e.g. \"vim\"\r\n    EXT - (string) extension for the file name to be generated, e.g. \".vim\"\r\n    PATH - (string) path in which to create the new files and \"lastnr.dat\"\r\n        (user creates the files, script only creates lastnr.dat)\r\n    LNPK - (string) optional selector to choose the path for lastnr.dat from\r\n        another set; \"LastNr.dat Path Key\".  Makes it possible to have a\r\n        single lastnr.dat file for all paths.\r\n    \r\n    * You can overwrite the one default KEY \"vim\".\r\n    * Different KEYs can share PATH (the lastnr file contains a line for\r\n      each KEY), only PATH + EXT must be unique (in general).\r\n\r\ng:testname#lastnrfile\t    (string)\r\n\r\n    name of lastnr-file in PATH; must be given without (esp. absolute) path;\r\n    default is \"lastnr.dat\"\r\n\r\ng:testname#firstnr    (string)\r\n\r\n    first \"number\" to be used, default \"A1\"\r\n","install_details":"put the script in your autoload folder\r\n\r\ncustomize g:testname#set\r\n\r\nsetup an abbrevation for each set, the following will work with default\r\ntestname#set:\r\n    :cabbr <expr> tn# testname#GetFreeName(\"vim\") \r\n","5":"put the script in your autoload folder\r\n\r\ncustomize g:testname#set\r\n\r\nsetup an abbrevation for each set, the following will work with default\r\ntestname#set:\r\n    :cabbr <expr> tn# testname#GetFreeName(\"vim\") \r\n","first_name":"Andy","6":"Andy","last_name":"Wokula","7":"Wokula","releases":[{"0":"2817","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"testname.vim","4":"testname.vim","src_id":"11550","5":"11550","creation_date":"1255976385","6":"1255976385"}]},"2816":{"script_id":"2816","0":"2816","script_name":"Execute selection in Python and append","1":"Execute selection in Python and append","script_type":"utility","2":"utility","summary":"Execute a selection in Python and paste result after","3":"Execute a selection in Python and paste result after","description":"This script executes a selection in Python and then pastes the result after that selection or replaces the selection. Useful for testing small software snippets and documenting them in the same buffer.\r\n\r\nIt is based on http:\/\/vim.wikia.com\/wiki\/Execute_Python_from_within_current_file","4":"This script executes a selection in Python and then pastes the result after that selection or replaces the selection. Useful for testing small software snippets and documenting them in the same buffer.\r\n\r\nIt is based on http:\/\/vim.wikia.com\/wiki\/Execute_Python_from_within_current_file","install_details":"Just put into your .vimrc and then use command :Pyea (appends) or :Pyer (replaces) .","5":"Just put into your .vimrc and then use command :Pyea (appends) or :Pyer (replaces) .","first_name":"Michal","6":"Michal","last_name":"Gajda","7":"Gajda","releases":[{"0":"2816","vim_version":"7.0","1":"7.0","script_version":"0.2","2":"0.2","version_comment":"Now :Pyea appends after selection, and :Pyer replaces selection with results of Python snippet.","3":"Now :Pyea appends after selection, and :Pyer replaces selection with results of Python snippet.","package":"pythonExecuteAppendOrReplace.vim","4":"pythonExecuteAppendOrReplace.vim","src_id":"11548","5":"11548","creation_date":"1255954751","6":"1255954751"},{"0":"2816","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"pythonExecuteAppend.vim","4":"pythonExecuteAppend.vim","src_id":"11542","5":"11542","creation_date":"1255855306","6":"1255855306"}]},"2815":{"script_id":"2815","0":"2815","script_name":"hornet.vim","1":"hornet.vim","script_type":"color scheme","2":"color scheme","summary":"Hornet style colorscheme","3":"Hornet style colorscheme","description":"Hornet is a modification of the colorscheme busybee (vimscript #2549) by Patrick Anderson.\r\nHornet refers to the famous \"Green hornet\" and is supposed to be a greener version of busybee.","4":"Hornet is a modification of the colorscheme busybee (vimscript #2549) by Patrick Anderson.\r\nHornet refers to the famous \"Green hornet\" and is supposed to be a greener version of busybee.","install_details":"Copy hornet.vim to your ~\/.vim\/colors\/ directory.","5":"Copy hornet.vim to your ~\/.vim\/colors\/ directory.","first_name":"Taurus","6":"Taurus","last_name":"Olson","7":"Olson","releases":[{"0":"2815","vim_version":"7.2","1":"7.2","script_version":"1.0.2","2":"1.0.2","version_comment":"Initial upload","3":"Initial upload","package":"hornet.vim","4":"hornet.vim","src_id":"11540","5":"11540","creation_date":"1255794704","6":"1255794704"}]},"2814":{"script_id":"2814","0":"2814","script_name":"PyMol syntax","1":"PyMol syntax","script_type":"syntax","2":"syntax","summary":"PyMol syntax ","3":"PyMol syntax ","description":"May be useful for editing .pml scripts of PyMol http:\/\/pymol.org.","4":"May be useful for editing .pml scripts of PyMol http:\/\/pymol.org.","install_details":"Just put the syntax file in your ~\/.vim\/syntax\/, and load with:\r\n\r\nautocmd BufRead *.pml source ~\/.vim\/syntax\/pymol.vim","5":"Just put the syntax file in your ~\/.vim\/syntax\/, and load with:\r\n\r\nautocmd BufRead *.pml source ~\/.vim\/syntax\/pymol.vim","first_name":"Michal","6":"Michal","last_name":"Gajda","7":"Gajda","releases":[{"0":"2814","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"pymol.vim","4":"pymol.vim","src_id":"11539","5":"11539","creation_date":"1255783548","6":"1255783548"}]},"2813":{"script_id":"2813","0":"2813","script_name":"MailApp","1":"MailApp","script_type":"utility","2":"utility","summary":"This plugin allows Mac OS X users to send e-mails from Vim using Mail.app.","3":"This plugin allows Mac OS X users to send e-mails from Vim using Mail.app.","description":"This plugin allows Mac OS X users to send e-mails from Vim using the Mail.app application.\r\n\r\nIt provides syntax highlighting, auto-completion for header name, e-mail and attachment.\r\n\r\nTo start a new e-mail, use the command :NewMailApp, which will open a new buffer where you can start writing. To send the e-mail, use the command :SendMailApp.","4":"This plugin allows Mac OS X users to send e-mails from Vim using the Mail.app application.\r\n\r\nIt provides syntax highlighting, auto-completion for header name, e-mail and attachment.\r\n\r\nTo start a new e-mail, use the command :NewMailApp, which will open a new buffer where you can start writing. To send the e-mail, use the command :SendMailApp.","install_details":"Mac OS X 10.5 or later is required for this plug-in and Mail.app must be configured to send messages. To install it, unzip the MailApp.zip file and place every file in the respective folder inside your \"~\/.vim\" folder, keeping the same folder structure, except for MailApp.bundle that should go inside your \"Documents\" folder.\r\n\r\n ~\/\r\n   |-.vim\/\r\n   |    |-doc\/mailapp.txt\r\n   |    |-ftplugin\/mailapp.vim\r\n   |    |-plugin\/MailApp.vim\r\n   |    |-syntax\/mailapp.vim\r\n   |-\/Documents\/MailApp.bundle\r\n\r\nIf you place MailApp.bunlde somewhere else, you need to set the 'MailApp_bundle' option in your vimrc so MailApp.vim can find it.\r\n\r\nAfter you placed the files in their place, run \":helptags ~\/.vim\/doc\" to update the help files tags.\r\n","5":"Mac OS X 10.5 or later is required for this plug-in and Mail.app must be configured to send messages. To install it, unzip the MailApp.zip file and place every file in the respective folder inside your \"~\/.vim\" folder, keeping the same folder structure, except for MailApp.bundle that should go inside your \"Documents\" folder.\r\n\r\n ~\/\r\n   |-.vim\/\r\n   |    |-doc\/mailapp.txt\r\n   |    |-ftplugin\/mailapp.vim\r\n   |    |-plugin\/MailApp.vim\r\n   |    |-syntax\/mailapp.vim\r\n   |-\/Documents\/MailApp.bundle\r\n\r\nIf you place MailApp.bunlde somewhere else, you need to set the 'MailApp_bundle' option in your vimrc so MailApp.vim can find it.\r\n\r\nAfter you placed the files in their place, run \":helptags ~\/.vim\/doc\" to update the help files tags.\r\n","first_name":"Israel","6":"Israel","last_name":"Chauca Fuentes","7":"Chauca Fuentes","releases":[{"0":"2813","vim_version":"7.0","1":"7.0","script_version":"1.1","2":"1.1","version_comment":"Fixed a problem with the \"from\" header that would prevent the message from being sent.","3":"Fixed a problem with the \"from\" header that would prevent the message from being sent.","package":"MailApp.zip","4":"MailApp.zip","src_id":"11549","5":"11549","creation_date":"1255971241","6":"1255971241"},{"0":"2813","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"MailApp.zip","4":"MailApp.zip","src_id":"11534","5":"11534","creation_date":"1255715002","6":"1255715002"}]},"2812":{"script_id":"2812","0":"2812","script_name":"term.vim","1":"term.vim","script_type":"game","2":"game","summary":"Terminal library","3":"Terminal library","description":"Terminal library for Unix CUI terminal.\r\n\r\nExample:\r\n  \" Display current time at bottom of screen.\r\n  \" move cursor\r\n  call term#position(&lines, 1)\r\n  \" fg=blue bg=red\r\n  call term#attr(0, 34, 41)\r\n  \" print text\r\n  call term#text(strftime(\"%c\"))\r\n  \" reset attribute\r\n  call term#attr()\r\n  \" output\r\n  call term#out()\r\n\r\nTry :call term#demo()\r\n","4":"Terminal library for Unix CUI terminal.\r\n\r\nExample:\r\n  \" Display current time at bottom of screen.\r\n  \" move cursor\r\n  call term#position(&lines, 1)\r\n  \" fg=blue bg=red\r\n  call term#attr(0, 34, 41)\r\n  \" print text\r\n  call term#text(strftime(\"%c\"))\r\n  \" reset attribute\r\n  call term#attr()\r\n  \" output\r\n  call term#out()\r\n\r\nTry :call term#demo()\r\n","install_details":"Put file in your autoload directory.","5":"Put file in your autoload directory.","first_name":"Yukihiro","6":"Yukihiro","last_name":"Nakadaira","7":"Nakadaira","releases":[{"0":"2812","vim_version":"7.2","1":"7.2","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"term.vim","4":"term.vim","src_id":"11530","5":"11530","creation_date":"1255619770","6":"1255619770"}]},"2811":{"script_id":"2811","0":"2811","script_name":"hlasm.vim","1":"hlasm.vim","script_type":"syntax","2":"syntax","summary":"asm370 hlasm mvs","3":"asm370 hlasm mvs","description":"Syntax highlight file for hlasm or asm370. You can freely add any missing keyword in \"syn keyword xInstruction\", \"syn keyword xDirective\", \"syn keyword xMacro\",  \"syn keyword xParameter\" \"syn keyword xRegister' etc.","4":"Syntax highlight file for hlasm or asm370. You can freely add any missing keyword in \"syn keyword xInstruction\", \"syn keyword xDirective\", \"syn keyword xMacro\",  \"syn keyword xParameter\" \"syn keyword xRegister' etc.","install_details":"Copy the hlasm.vim to vim syntax folder.  Use \":set ft=hlasm\" command to enable hlasm syntax highlight.","5":"Copy the hlasm.vim to vim syntax folder.  Use \":set ft=hlasm\" command to enable hlasm syntax highlight.","first_name":"bing","6":"bing","last_name":"shen","7":"shen","releases":[{"0":"2811","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"hlasm.vim","4":"hlasm.vim","src_id":"11528","5":"11528","creation_date":"1255515189","6":"1255515189"}]},"2810":{"script_id":"2810","0":"2810","script_name":"InsertChar","1":"InsertChar","script_type":"utility","2":"utility","summary":"Press <tab> to insert a single character","3":"Press <tab> to insert a single character","description":"Allows you to use <tab> <letter> to insert a single character (no need to press escape). You can also use 3<tab> <letter> to insert 3 characters.\r\n\r\nIf you install vimscript #2136, then the '.' command will also repeat the last insert.\r\n","4":"Allows you to use <tab> <letter> to insert a single character (no need to press escape). You can also use 3<tab> <letter> to insert 3 characters.\r\n\r\nIf you install vimscript #2136, then the '.' command will also repeat the last insert.\r\n","install_details":"Step 1:\r\nPlace InsertChar.vim in the ~\/.vim\/plugin\/ folder, or ~\/.vim\/autoload if your prefer.\r\n\r\nStep 2:\r\nSet up a mapping in your ~\/.vimrc:\r\nnnoremap <TAB> :<C-U>call InsertChar#insert(v:count1)<CR>\r\n\r\nYou can change <TAB> to any other key you prefer, but the rest of the command must be the same.\r\n","5":"Step 1:\r\nPlace InsertChar.vim in the ~\/.vim\/plugin\/ folder, or ~\/.vim\/autoload if your prefer.\r\n\r\nStep 2:\r\nSet up a mapping in your ~\/.vimrc:\r\nnnoremap <TAB> :<C-U>call InsertChar#insert(v:count1)<CR>\r\n\r\nYou can change <TAB> to any other key you prefer, but the rest of the command must be the same.\r\n","first_name":"Peter","6":"Peter","last_name":"Hodge","7":"Hodge","releases":[{"0":"2810","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"InsertChar.vim","4":"InsertChar.vim","src_id":"11521","5":"11521","creation_date":"1255404089","6":"1255404089"}]},"2809":{"script_id":"2809","0":"2809","script_name":"fontsize","1":"fontsize","script_type":"utility","2":"utility","summary":"Adjust Gvim font size via keypresses","3":"Adjust Gvim font size via keypresses","description":"******************************************\r\nFontsize - Adjust font size via keypresses\r\n******************************************\r\n\r\nFontsize provides key mappings for adjusting the font size in Gvim.  The\r\ninitial mappings launch a \"font size\" mode in which single keypresses are used\r\nto adjust the font.  This mode ends after a timeout or when the user presses\r\nany key not defined in the mode.\r\n\r\nFor example, using the default key bindings, pressing <Leader><Leader>+ will\r\nenter \"font size\" mode and increase the font size by one.  Once in the mode,\r\npressing the \"+\" key repeatedly will increase the font size by one for each\r\nadditional press.  Additionally, a [count] may be provided to change the font size\r\nby larger increments.\r\n\r\nSee documentation in doc\/fontsize for installation and usage instructions.\r\n\r\nDeveloped by Michael Henry (vim at drmikehenry.com).\r\n\r\nDistributed under Vim's license.\r\n\r\nGit repository:   https:\/\/github.com\/drmikehenry\/vim-fontsize\r\n","4":"******************************************\r\nFontsize - Adjust font size via keypresses\r\n******************************************\r\n\r\nFontsize provides key mappings for adjusting the font size in Gvim.  The\r\ninitial mappings launch a \"font size\" mode in which single keypresses are used\r\nto adjust the font.  This mode ends after a timeout or when the user presses\r\nany key not defined in the mode.\r\n\r\nFor example, using the default key bindings, pressing <Leader><Leader>+ will\r\nenter \"font size\" mode and increase the font size by one.  Once in the mode,\r\npressing the \"+\" key repeatedly will increase the font size by one for each\r\nadditional press.  Additionally, a [count] may be provided to change the font size\r\nby larger increments.\r\n\r\nSee documentation in doc\/fontsize for installation and usage instructions.\r\n\r\nDeveloped by Michael Henry (vim at drmikehenry.com).\r\n\r\nDistributed under Vim's license.\r\n\r\nGit repository:   https:\/\/github.com\/drmikehenry\/vim-fontsize\r\n","install_details":"","5":"","first_name":"Michael","6":"Michael","last_name":"Henry","7":"Henry","releases":[{"0":"2809","vim_version":"7.0","1":"7.0","script_version":"0.5.0","2":"0.5.0","version_comment":"Add support for Neovim GUIs (at least nvim-qt and neovide).\r\n","3":"Add support for Neovim GUIs (at least nvim-qt and neovide).\r\n","package":"fontsize-0.5.0.zip","4":"fontsize-0.5.0.zip","src_id":"28532","5":"28532","creation_date":"1692508484","6":"1692508484"},{"0":"2809","vim_version":"7.0","1":"7.0","script_version":"0.4.1","2":"0.4.1","version_comment":"Add support for GTK3-based GUI.","3":"Add support for GTK3-based GUI.","package":"fontsize-0.4.1.zip","4":"fontsize-0.4.1.zip","src_id":"24735","5":"24735","creation_date":"1479258946","6":"1479258946"},{"0":"2809","vim_version":"7.0","1":"7.0","script_version":"0.4.0","2":"0.4.0","version_comment":"Add configurable time-out settings for font mode (including the ability to never time out).","3":"Add configurable time-out settings for font mode (including the ability to never time out).","package":"fontsize-0.4.0.zip","4":"fontsize-0.4.0.zip","src_id":"23641","5":"23641","creation_date":"1443993713","6":"1443993713"},{"0":"2809","vim_version":"7.0","1":"7.0","script_version":"0.3.4","2":"0.3.4","version_comment":"Do not load plugin without GUI running (thanks to Anatolii Sakhnik).","3":"Do not load plugin without GUI running (thanks to Anatolii Sakhnik).","package":"fontsize-0.3.4.zip","4":"fontsize-0.3.4.zip","src_id":"23250","5":"23250","creation_date":"1430437933","6":"1430437933"},{"0":"2809","vim_version":"7.0","1":"7.0","script_version":"0.3.3","2":"0.3.3","version_comment":"- Add support for [count] (thanks to Ingo Karkat).\r\n","3":"- Add support for [count] (thanks to Ingo Karkat).\r\n","package":"fontsize-0.3.3.zip","4":"fontsize-0.3.3.zip","src_id":"21736","5":"21736","creation_date":"1396704956","6":"1396704956"},{"0":"2809","vim_version":"7.0","1":"7.0","script_version":"0.3.2","2":"0.3.2","version_comment":"Minor update:\r\n\r\n- Add autoloaded guard.\r\n- Fix paste error in documentation (thanks to hfs for the bug report).\r\n","3":"Minor update:\r\n\r\n- Add autoloaded guard.\r\n- Fix paste error in documentation (thanks to hfs for the bug report).\r\n","package":"fontsize-0.3.2.zip","4":"fontsize-0.3.2.zip","src_id":"21483","5":"21483","creation_date":"1392385238","6":"1392385238"},{"0":"2809","vim_version":"7.0","1":"7.0","script_version":"0.3.1","2":"0.3.1","version_comment":"Documentation reorganization.","3":"Documentation reorganization.","package":"fontsize-0.3.1.zip","4":"fontsize-0.3.1.zip","src_id":"20878","5":"20878","creation_date":"1380818907","6":"1380818907"},{"0":"2809","vim_version":"7.0","1":"7.0","script_version":"0.3.0","2":"0.3.0","version_comment":"- Switch default key bindings to <Leader><Leader>x instead of <Leader>xx.\r\n\r\n- Convert to bundle-based installation instructions.\r\n\r\n- Use getfontname() instead of reading 'guifont', allowing fontsize to work\r\n  when 'guifont' was not set or was set to a comma-separated list of fonts\r\n  where the first font was not valid.\r\n\r\n- Use \"(fontsize)\" string for prettier-looking 'showcmd' output.\r\n","3":"- Switch default key bindings to <Leader><Leader>x instead of <Leader>xx.\r\n\r\n- Convert to bundle-based installation instructions.\r\n\r\n- Use getfontname() instead of reading 'guifont', allowing fontsize to work\r\n  when 'guifont' was not set or was set to a comma-separated list of fonts\r\n  where the first font was not valid.\r\n\r\n- Use \"(fontsize)\" string for prettier-looking 'showcmd' output.\r\n","package":"vim-fontsize-0.3.0.zip","4":"vim-fontsize-0.3.0.zip","src_id":"20869","5":"20869","creation_date":"1380754256","6":"1380754256"},{"0":"2809","vim_version":"7.0","1":"7.0","script_version":"0.2.1","2":"0.2.1","version_comment":"Properly restore cpoptions.","3":"Properly restore cpoptions.","package":"fontsize-0.2.1.vba","4":"fontsize-0.2.1.vba","src_id":"20836","5":"20836","creation_date":"1380018893","6":"1380018893"},{"0":"2809","vim_version":"7.0","1":"7.0","script_version":"0.2.0","2":"0.2.0","version_comment":"Version 0.2.0    Date    2009-10-21                 *fontsize-changelog-0.2.0*\r\n\r\n  - Changed <Leader>== to enter \"font size\" mode without changing the \r\n    font size.\r\n\r\n  - Fixed regex for win32 and others to not require colon after size field\r\n    (e.g., \"fontname:h12\" works, don't need \"fontname:h12:cANSI\").  Added\r\n    regex support for other platforms.\r\n\r\n  - Added g:fontsize_encoding feature to handle different encodings for\r\n    &guifont and &guifontwide.\r\n\r\n  - Handles empty &guifont better now (but cannot change font size in that\r\n    case).\r\n\r\n  - Added documentation sections for TODO, ChangeLog.","3":"Version 0.2.0    Date    2009-10-21                 *fontsize-changelog-0.2.0*\r\n\r\n  - Changed <Leader>== to enter \"font size\" mode without changing the \r\n    font size.\r\n\r\n  - Fixed regex for win32 and others to not require colon after size field\r\n    (e.g., \"fontname:h12\" works, don't need \"fontname:h12:cANSI\").  Added\r\n    regex support for other platforms.\r\n\r\n  - Added g:fontsize_encoding feature to handle different encodings for\r\n    &guifont and &guifontwide.\r\n\r\n  - Handles empty &guifont better now (but cannot change font size in that\r\n    case).\r\n\r\n  - Added documentation sections for TODO, ChangeLog.","package":"fontsize-0.2.0.vba","4":"fontsize-0.2.0.vba","src_id":"11568","5":"11568","creation_date":"1256289817","6":"1256289817"},{"0":"2809","vim_version":"7.0","1":"7.0","script_version":"0.1.0","2":"0.1.0","version_comment":"Initial upload","3":"Initial upload","package":"fontsize-0.1.0.vba","4":"fontsize-0.1.0.vba","src_id":"11518","5":"11518","creation_date":"1255299991","6":"1255299991"}]},"2808":{"script_id":"2808","0":"2808","script_name":"haxe_plugin","1":"haxe_plugin","script_type":"ftplugin","2":"ftplugin","summary":"Alternative flashdeveloper for programming on haxe","3":"Alternative flashdeveloper for programming on haxe","description":"You love omnicomplete for vim.\r\nThis begin decision for best navigation on standard haxe library at console enviroment.\r\nScript is a dampish, but function executes.\r\n","4":"You love omnicomplete for vim.\r\nThis begin decision for best navigation on standard haxe library at console enviroment.\r\nScript is a dampish, but function executes.\r\n","install_details":"Simple so... etc\r\n","5":"Simple so... etc\r\n","first_name":"Nikolay","6":"Nikolay","last_name":"Vladimirovich","7":"Vladimirovich","releases":[{"0":"2808","vim_version":"7.0","1":"7.0","script_version":"0.001","2":"0.001","version_comment":"Initial upload","3":"Initial upload","package":"omnihaxeselectpack2.vim","4":"omnihaxeselectpack2.vim","src_id":"11517","5":"11517","creation_date":"1255298841","6":"1255298841"}]},"2807":{"script_id":"2807","0":"2807","script_name":"Nmap syntax highlight","1":"Nmap syntax highlight","script_type":"syntax","2":"syntax","summary":"Nmap syntax highlight","3":"Nmap syntax highlight","description":"Nmap syntax highlight file. With this file you can view Nmap (*.nmap) files with nice colors :)","4":"Nmap syntax highlight file. With this file you can view Nmap (*.nmap) files with nice colors :)","install_details":"","5":"","first_name":"pento","6":"pento","last_name":"pento","7":"pento","releases":[{"0":"2807","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"nmap.vim","4":"nmap.vim","src_id":"11516","5":"11516","creation_date":"1255283158","6":"1255283158"}]},"2806":{"script_id":"2806","0":"2806","script_name":"md5.vim","1":"md5.vim","script_type":"game","2":"game","summary":"md5() function","3":"md5() function","description":"This is a port of rfc1321 md5 function.\r\n\r\n:echo md5#md5(\"hello, world\")\r\ne4d7f1b4ed2e42d15898f4b27b019da4","4":"This is a port of rfc1321 md5 function.\r\n\r\n:echo md5#md5(\"hello, world\")\r\ne4d7f1b4ed2e42d15898f4b27b019da4","install_details":"Put file in your autoload directory.","5":"Put file in your autoload directory.","first_name":"Yukihiro","6":"Yukihiro","last_name":"Nakadaira","7":"Nakadaira","releases":[{"0":"2806","vim_version":"7.2","1":"7.2","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"md5.vim","4":"md5.vim","src_id":"11508","5":"11508","creation_date":"1255242029","6":"1255242029"}]},"2805":{"script_id":"2805","0":"2805","script_name":"assistant","1":"assistant","script_type":"utility","2":"utility","summary":"Display the definition of functions, variables, etc. (Tags, PHP\/JS\/Vim\/...)","3":"Display the definition of functions, variables, etc. (Tags, PHP\/JS\/Vim\/...)","description":"Display the definition of functions, variables, etc. (Tags, PHP\/JS\/Vim\/...)\r\n\r\nUsage:\r\n\r\n    press <C-k> to view the definition(load from tags and dict file) of function, variable, etc.\r\n    press <C-x><C-u> to complete text.\r\n","4":"Display the definition of functions, variables, etc. (Tags, PHP\/JS\/Vim\/...)\r\n\r\nUsage:\r\n\r\n    press <C-k> to view the definition(load from tags and dict file) of function, variable, etc.\r\n    press <C-x><C-u> to complete text.\r\n","install_details":"Just put the files into ~\/.vim\/plugin or <HOMEDIR>\\vimfiles\\plugin (for Windows).","5":"Just put the files into ~\/.vim\/plugin or <HOMEDIR>\\vimfiles\\plugin (for Windows).","first_name":"-","6":"-","last_name":"-","7":"-","releases":[{"0":"2805","vim_version":"7.0","1":"7.0","script_version":"1.5.8","2":"1.5.8","version_comment":"fix error while filetype is empty","3":"fix error while filetype is empty","package":"vim-assistant-1.5.8.zip","4":"vim-assistant-1.5.8.zip","src_id":"22247","5":"22247","creation_date":"1406043638","6":"1406043638"}]},"2804":{"script_id":"2804","0":"2804","script_name":"chocolate.vim","1":"chocolate.vim","script_type":"color scheme","2":"color scheme","summary":"Choclolate color scheme, based on the W3C core style","3":"Choclolate color scheme, based on the W3C core style","description":"\"Choclolate\", a dark colorscheme based on the W3C core style of the same name and 'clean.vim' by Ron Aaron.\r\n\r\nSee http:\/\/www.w3.org\/StyleSheets\/Core\/Overview\r\n\r\nSample:\r\n\r\nhttp:\/\/happy.cat\/blog\/VIM-Chocolate-Colorscheme-2008-06-04-16-30.html","4":"\"Choclolate\", a dark colorscheme based on the W3C core style of the same name and 'clean.vim' by Ron Aaron.\r\n\r\nSee http:\/\/www.w3.org\/StyleSheets\/Core\/Overview\r\n\r\nSample:\r\n\r\nhttp:\/\/happy.cat\/blog\/VIM-Chocolate-Colorscheme-2008-06-04-16-30.html","install_details":"Linux \/ UNIX:  drop this file in $HOME\/.vim\/colors\r\nWindows: place in $HOME\\vimfiles\\colors\r\n:colorscheme chocolate\r\n","5":"Linux \/ UNIX:  drop this file in $HOME\/.vim\/colors\r\nWindows: place in $HOME\\vimfiles\\colors\r\n:colorscheme chocolate\r\n","first_name":"Adam","6":"Adam","last_name":"Hayward","7":"Hayward","releases":[{"0":"2804","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"chocolate.vim","4":"chocolate.vim","src_id":"11501","5":"11501","creation_date":"1255086059","6":"1255086059"}]},"2803":{"script_id":"2803","0":"2803","script_name":"php_localvarcheck.vim","1":"php_localvarcheck.vim","script_type":"ftplugin","2":"ftplugin","summary":"highlight unused\/unassigned local variable","3":"highlight unused\/unassigned local variable","description":"function example($unused) {\r\n  echo $unassigned;\r\n}\r\n\r\n$unused and $unassigned are highlighted when the cursor is in example().","4":"function example($unused) {\r\n  echo $unassigned;\r\n}\r\n\r\n$unused and $unassigned are highlighted when the cursor is in example().","install_details":"Put file in you ftplugin directory.","5":"Put file in you ftplugin directory.","first_name":"Yukihiro","6":"Yukihiro","last_name":"Nakadaira","7":"Nakadaira","releases":[{"0":"2803","vim_version":"7.0","1":"7.0","script_version":"1.1","2":"1.1","version_comment":"Fixed a bug that function is not caught when the cursor is positioned before function keyword.","3":"Fixed a bug that function is not caught when the cursor is positioned before function keyword.","package":"php_localvarcheck.vim","4":"php_localvarcheck.vim","src_id":"11495","5":"11495","creation_date":"1254996335","6":"1254996335"},{"0":"2803","vim_version":"7.2","1":"7.2","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"php_localvarcheck.vim","4":"php_localvarcheck.vim","src_id":"11494","5":"11494","creation_date":"1254912536","6":"1254912536"}]},"2802":{"script_id":"2802","0":"2802","script_name":"JavaScript syntax (add E4X support)","1":"JavaScript syntax (add E4X support)","script_type":"syntax","2":"syntax","summary":"Fix highlighting on E4X (CDATA) blocks","3":"Fix highlighting on E4X (CDATA) blocks","description":"Supplementary syntax file for JavaScript.\r\n\r\nAdds support for properly highlighting E4X (ECMAscript4XML) blocks, which is a CDATA chunk of raw text inside ECMAscript\/JavaScript code.  See http:\/\/en.wikipedia.org\/wiki\/ECMAScript_for_XML or http:\/\/userscripts.org\/guides\/4","4":"Supplementary syntax file for JavaScript.\r\n\r\nAdds support for properly highlighting E4X (ECMAscript4XML) blocks, which is a CDATA chunk of raw text inside ECMAscript\/JavaScript code.  See http:\/\/en.wikipedia.org\/wiki\/ECMAScript_for_XML or http:\/\/userscripts.org\/guides\/4","install_details":"Save this file to ~\/.vim\/after\/syntax\/javascript.vim and you're good to go.","5":"Save this file to ~\/.vim\/after\/syntax\/javascript.vim and you're good to go.","first_name":"Adam","6":"Adam","last_name":"Katz","7":"Katz","releases":[{"0":"2802","vim_version":"5.7","1":"5.7","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"javascript.vim","4":"javascript.vim","src_id":"11493","5":"11493","creation_date":"1254874394","6":"1254874394"}]},"2801":{"script_id":"2801","0":"2801","script_name":"NERD_tree Project","1":"NERD_tree Project","script_type":"utility","2":"utility","summary":"It tries to find out root project directory, browse project file with NERD_tree.","3":"It tries to find out root project directory, browse project file with NERD_tree.","description":"This plugin works together with NERD_tree (http:\/\/www.vim.org\/scripts\/script.php?script_id=1658). It tries to find out root project directory for current file, and calls NERD_tree in that directory. If no project found, then calls NERD_tree in current directory.\r\n\r\n=== How does this plugin work ===\r\nIt searches several files used to indicate a project root directory when creating or reading file:\r\n    build.xml, Makefile, .project, .lvimrc\r\nIf any one of them found, the located directory is recognized as project root directory. Command 'ToggleNERDTree' should open this directory as root so that you could keep working on the proper project. NERD_tree opens current directory if nothing found.\r\n\r\n=== Usage ===\r\n  Type in normal mode:\r\n      :ToggleNERDTree<CR>,\r\n  or map shortcut in your .vimrc file:\r\n      map <F8> :ToggleNERDTree<CR>\r\n\r\n=== Customize ===\r\n  Make NERD_tree Project to recognize more project, such as scons:\r\n      let g:NTPNames = add(g:NTPNames, 'SConstruct')\r\n  or add more file types:\r\n      extend(g:NTPNames, ['*.sln', '*.csproj'])","4":"This plugin works together with NERD_tree (http:\/\/www.vim.org\/scripts\/script.php?script_id=1658). It tries to find out root project directory for current file, and calls NERD_tree in that directory. If no project found, then calls NERD_tree in current directory.\r\n\r\n=== How does this plugin work ===\r\nIt searches several files used to indicate a project root directory when creating or reading file:\r\n    build.xml, Makefile, .project, .lvimrc\r\nIf any one of them found, the located directory is recognized as project root directory. Command 'ToggleNERDTree' should open this directory as root so that you could keep working on the proper project. NERD_tree opens current directory if nothing found.\r\n\r\n=== Usage ===\r\n  Type in normal mode:\r\n      :ToggleNERDTree<CR>,\r\n  or map shortcut in your .vimrc file:\r\n      map <F8> :ToggleNERDTree<CR>\r\n\r\n=== Customize ===\r\n  Make NERD_tree Project to recognize more project, such as scons:\r\n      let g:NTPNames = add(g:NTPNames, 'SConstruct')\r\n  or add more file types:\r\n      extend(g:NTPNames, ['*.sln', '*.csproj'])","install_details":"First, make sure NERD_tree is installed. Then put NERD_tree_project.vim in ~\/.vim\/plugin (*nix) or $HOME\/vimfiles\/plugin (DOS).","5":"First, make sure NERD_tree is installed. Then put NERD_tree_project.vim in ~\/.vim\/plugin (*nix) or $HOME\/vimfiles\/plugin (DOS).","first_name":"Janlay","6":"Janlay","last_name":"Wu","7":"Wu","releases":[{"0":"2801","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"NERD_tree_project.vim","4":"NERD_tree_project.vim","src_id":"11487","5":"11487","creation_date":"1254818034","6":"1254818034"}]},"2800":{"script_id":"2800","0":"2800","script_name":"Windows PowerShell indent (enhanced)","1":"Windows PowerShell indent (enhanced)","script_type":"indent","2":"indent","summary":"New version - everything indents correctly","3":"New version - everything indents correctly","description":"PowerShell indentation script. Partially relying on the built-in cindent but fixing many PowerShell specific indentations like the comment problem (lines that begin with # were considered precompiler and were never indented) and extraneous indentation after a param() line or a line that ends with a .net function call.\r\n\r\nBest used with the Windows PowerShell syntax and ftplugin files (vimscript #1327 and vimscript #1816)\r\n\r\nIndentation should be perfect now.\r\nIf you happen to find anything that does not indent correctly - please comment on my blog post:\r\nhttp:\/\/blogs.msdn.com\/lior\/archive\/2009\/10\/18\/powershell-indentation-for-vim-version-2-0.aspx","4":"PowerShell indentation script. Partially relying on the built-in cindent but fixing many PowerShell specific indentations like the comment problem (lines that begin with # were considered precompiler and were never indented) and extraneous indentation after a param() line or a line that ends with a .net function call.\r\n\r\nBest used with the Windows PowerShell syntax and ftplugin files (vimscript #1327 and vimscript #1816)\r\n\r\nIndentation should be perfect now.\r\nIf you happen to find anything that does not indent correctly - please comment on my blog post:\r\nhttp:\/\/blogs.msdn.com\/lior\/archive\/2009\/10\/18\/powershell-indentation-for-vim-version-2-0.aspx","install_details":"Copy this file into your indent folder.\r\n","5":"Copy this file into your indent folder.\r\n","first_name":"Lior","6":"Lior","last_name":"Elia","7":"Elia","releases":[{"0":"2800","vim_version":"6.0","1":"6.0","script_version":"2.0","2":"2.0","version_comment":"Fixed many things. Currently there are no open issues.\r\nIf you find something that doesn't indent correctly, please comment so that I can fix this. Also if you find this script useful please rate it.","3":"Fixed many things. Currently there are no open issues.\r\nIf you find something that doesn't indent correctly, please comment so that I can fix this. Also if you find this script useful please rate it.","package":"ps1.vim","4":"ps1.vim","src_id":"11547","5":"11547","creation_date":"1255897132","6":"1255897132"},{"0":"2800","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"ps1.vim","4":"ps1.vim","src_id":"11479","5":"11479","creation_date":"1254648835","6":"1254648835"}]},"2799":{"script_id":"2799","0":"2799","script_name":"tango.vim","1":"tango.vim","script_type":"color scheme","2":"color scheme","summary":"Full Tango based colorscheme","3":"Full Tango based colorscheme","description":"Based on the Tango color palette.\t\r\nThe background is white by default, to have a really full Tango colorscheme put this in your .vimrc file:\r\n\r\nlet g:bg_tango = 1\r\n\r\nScreenshots: \r\nC - http:\/\/www.focolivre.org\/arquivos\/tango_vim.png\r\nPython - http:\/\/www.focolivre.org\/arquivos\/tango_vim1.png\r\nPerl - http:\/\/www.focolivre.org\/arquivos\/tango_vim2.png\r\n\r\nTo more about the Tango Project: http:\/\/tango.freedesktop.org\r\nFor suggestions or any other thing, feel free to email me.","4":"Based on the Tango color palette.\t\r\nThe background is white by default, to have a really full Tango colorscheme put this in your .vimrc file:\r\n\r\nlet g:bg_tango = 1\r\n\r\nScreenshots: \r\nC - http:\/\/www.focolivre.org\/arquivos\/tango_vim.png\r\nPython - http:\/\/www.focolivre.org\/arquivos\/tango_vim1.png\r\nPerl - http:\/\/www.focolivre.org\/arquivos\/tango_vim2.png\r\n\r\nTo more about the Tango Project: http:\/\/tango.freedesktop.org\r\nFor suggestions or any other thing, feel free to email me.","install_details":"Just copy the file to your .vim\/colors folder. ","5":"Just copy the file to your .vim\/colors folder. ","first_name":"Taylon","6":"Taylon","last_name":"Silmer","7":"Silmer","releases":[{"0":"2799","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"tango.vim","4":"tango.vim","src_id":"11478","5":"11478","creation_date":"1254608947","6":"1254608947"}]},"2798":{"script_id":"2798","0":"2798","script_name":"Pasto","1":"Pasto","script_type":"utility","2":"utility","summary":"paste it to Pasto","3":"paste it to Pasto","description":"Paste & read from Pasto server\r\nhttp:\/\/trac-hg.assembla.com\/pasto\r\n\r\nExample server:\r\nhttp:\/\/pasto.elefantesrosas.com.ar\/","4":"Paste & read from Pasto server\r\nhttp:\/\/trac-hg.assembla.com\/pasto\r\n\r\nExample server:\r\nhttp:\/\/pasto.elefantesrosas.com.ar\/","install_details":"install on ~\/.vim\/plugins\/","5":"install on ~\/.vim\/plugins\/","first_name":"toto","6":"toto","last_name":"loco","7":"loco","releases":[{"0":"2798","vim_version":"7.0","1":"7.0","script_version":"0.5","2":"0.5","version_comment":"default domain changed","3":"default domain changed","package":"pasto.vim","4":"pasto.vim","src_id":"11662","5":"11662","creation_date":"1257440371","6":"1257440371"},{"0":"2798","vim_version":"7.0","1":"7.0","script_version":"0.4","2":"0.4","version_comment":"some bug fixes","3":"some bug fixes","package":"pasto.vim","4":"pasto.vim","src_id":"11492","5":"11492","creation_date":"1254864694","6":"1254864694"},{"0":"2798","vim_version":"7.0","1":"7.0","script_version":"0.3","2":"0.3","version_comment":"Initial upload","3":"Initial upload","package":"pasto.vim","4":"pasto.vim","src_id":"11475","5":"11475","creation_date":"1254591503","6":"1254591503"}]},"2797":{"script_id":"2797","0":"2797","script_name":"SoftTabStops","1":"SoftTabStops","script_type":"utility","2":"utility","summary":"Set typewriter like tabstops.","3":"Set typewriter like tabstops.","description":"Description:\r\n  This plugin provides the ability to enter tabular data quickly in two\r\n  different ways:\r\n      - Set explicit stops at the columns.\r\n      - Enter a sample row and have the stops inferred from it.\r\n  The plugin provides a visual editor such that you can set explicit stops\r\n  with ease. The stops can be toggled using a mouse or keyboard. You can\r\n  toggle the plugin functionality on and off at the buffer or global\r\n  level.\r\n\r\nUsage:\r\n  - Use :STTgl to toggle using tabstops. This maps\/unmaps <Tab> and <BS>.\r\n    When buffer-local tabs are enabled (the default), the maps are made\r\n    local to the current buffer, otherwise, the maps are global.\r\n  - Use :STEdit[!] to bring up an editor for setting explicit tab stops (or\r\n    to just view them). You would see three lines, two with numbers to guide\r\n    the column number and another to show the current tab stops. To toggle\r\n    stop at a any column, move cursor to the column and push spacebar or\r\n    directly click left mouse button. To save changes at the end, use :wq\r\n    command (or just :w, to leave the window open). You can press \"q\" to\r\n    quit when no changes have been made. When buffer-local tabs have been\r\n    enabled (the default), use bang to edit the global tabstops.\r\n  - Use STReset to reset the tabstops to one every 8 columns (or whatever\r\n    'tabstop' is set to), or STClear to clear all of them.\r\n  - By default the stops are lcoal to a buffer\r\n    (g:softtabstops_local_to_buffer setting is set). This helps to localize\r\n    the stops and maps to the current buffer of interest, but as a result\r\n    are not shared across buffers. The tabstops will be stored as a list of\r\n    columns in the buffer local variable called \"b:softtabstops\". To have\r\n    same set of stops for all buffers reset this setting and have the stops\r\n    stored in the global variable \"g:softtabstops\".\r\n  - You can manipulate softtabstops in any of these ways:\r\n      - directly, by using the Vim's |List| functions. You can even clone\r\n        (using |copy()| function) the global \"g:softtabstops\" to the buffer\r\n        local variable \"b:softtabstops\"\r\n      - using plugin commands :STAddTab, :STRemoveTab, :STReset and :STClear\r\n      - using visual editor started by :STEdit command\r\n  - When softtabstops is toggled on and off, the plugin doesn't try to\r\n    restore any prior maps for <Tab> and <BS>, this is because Vim doesn't\r\n    provide any means to capture a map completely. If the experimental\r\n    g:softtabstops_restore_original_map option is turned on the plugin\r\n    attempts to capture the maps by parsing the :map command output and the\r\n    maparg() result, but this method is very limited, and will not work for\r\n    many scenarios. If you have have your own insert mode mappings for <Tab>\r\n    and <BS> or use a plugin that defines them, make sure this plugin\r\n    doesn't conflict with them.\r\n\r\nSettings:\r\n  - g:softtabstops_local_to_buffer (default: 1). Set to 0 to make tabstops\r\n    shared globally by all buffers. This also makes :STTgl create global\r\n    maps.\r\n  - g:softtabstops_repeat_last_stop (default: 0). When set to 1, the plugin\r\n    repeats the entire sequence of tabstops when it needs to extend them.\r\n  - g:softtabstops_align_line_with_editor (default: 1): Set to 0 to avoid\r\n    repositioning the current line when the tab editor is opened.\r\n  - g:softtabstops_infer_tabstops (default: 1). Set to 0, if you don't want\r\n    the plugin to infer the tabstops based on the previous lines, when no\r\n    explicit tabstops are set (or existing ones are cleared using :STClear)\r\n  - g:softtabstops_infer_imm_nonblank_only (default: 1). Set to 0, if you\r\n    want the tabstops to be inferred from the previous line, only when there\r\n    are no blank lines between them.\r\n  - g:softtabstops_editor_guide_start_num (default: 0). Controls the column\r\n    number sequence in the tab editor. Should be between 0 to 9.\r\n  - g:softtabstops_editor_guide_end_num (default: 9). Controls the column\r\n    number sequence in the tab editor. Should be between 0 to 9 and greater\r\n    than g:softtabstops_editor_guide_start_num.\r\n  - g:softtabstops_restore_original_map (default: 0). Set to 1 to enable the\r\n    experimental feature to save and restore maps while toggling on and off.\r\n\r\nLimitations:\r\n  - Can only insert all spaces, not a mix of tabs and spaces.\r\n","4":"Description:\r\n  This plugin provides the ability to enter tabular data quickly in two\r\n  different ways:\r\n      - Set explicit stops at the columns.\r\n      - Enter a sample row and have the stops inferred from it.\r\n  The plugin provides a visual editor such that you can set explicit stops\r\n  with ease. The stops can be toggled using a mouse or keyboard. You can\r\n  toggle the plugin functionality on and off at the buffer or global\r\n  level.\r\n\r\nUsage:\r\n  - Use :STTgl to toggle using tabstops. This maps\/unmaps <Tab> and <BS>.\r\n    When buffer-local tabs are enabled (the default), the maps are made\r\n    local to the current buffer, otherwise, the maps are global.\r\n  - Use :STEdit[!] to bring up an editor for setting explicit tab stops (or\r\n    to just view them). You would see three lines, two with numbers to guide\r\n    the column number and another to show the current tab stops. To toggle\r\n    stop at a any column, move cursor to the column and push spacebar or\r\n    directly click left mouse button. To save changes at the end, use :wq\r\n    command (or just :w, to leave the window open). You can press \"q\" to\r\n    quit when no changes have been made. When buffer-local tabs have been\r\n    enabled (the default), use bang to edit the global tabstops.\r\n  - Use STReset to reset the tabstops to one every 8 columns (or whatever\r\n    'tabstop' is set to), or STClear to clear all of them.\r\n  - By default the stops are lcoal to a buffer\r\n    (g:softtabstops_local_to_buffer setting is set). This helps to localize\r\n    the stops and maps to the current buffer of interest, but as a result\r\n    are not shared across buffers. The tabstops will be stored as a list of\r\n    columns in the buffer local variable called \"b:softtabstops\". To have\r\n    same set of stops for all buffers reset this setting and have the stops\r\n    stored in the global variable \"g:softtabstops\".\r\n  - You can manipulate softtabstops in any of these ways:\r\n      - directly, by using the Vim's |List| functions. You can even clone\r\n        (using |copy()| function) the global \"g:softtabstops\" to the buffer\r\n        local variable \"b:softtabstops\"\r\n      - using plugin commands :STAddTab, :STRemoveTab, :STReset and :STClear\r\n      - using visual editor started by :STEdit command\r\n  - When softtabstops is toggled on and off, the plugin doesn't try to\r\n    restore any prior maps for <Tab> and <BS>, this is because Vim doesn't\r\n    provide any means to capture a map completely. If the experimental\r\n    g:softtabstops_restore_original_map option is turned on the plugin\r\n    attempts to capture the maps by parsing the :map command output and the\r\n    maparg() result, but this method is very limited, and will not work for\r\n    many scenarios. If you have have your own insert mode mappings for <Tab>\r\n    and <BS> or use a plugin that defines them, make sure this plugin\r\n    doesn't conflict with them.\r\n\r\nSettings:\r\n  - g:softtabstops_local_to_buffer (default: 1). Set to 0 to make tabstops\r\n    shared globally by all buffers. This also makes :STTgl create global\r\n    maps.\r\n  - g:softtabstops_repeat_last_stop (default: 0). When set to 1, the plugin\r\n    repeats the entire sequence of tabstops when it needs to extend them.\r\n  - g:softtabstops_align_line_with_editor (default: 1): Set to 0 to avoid\r\n    repositioning the current line when the tab editor is opened.\r\n  - g:softtabstops_infer_tabstops (default: 1). Set to 0, if you don't want\r\n    the plugin to infer the tabstops based on the previous lines, when no\r\n    explicit tabstops are set (or existing ones are cleared using :STClear)\r\n  - g:softtabstops_infer_imm_nonblank_only (default: 1). Set to 0, if you\r\n    want the tabstops to be inferred from the previous line, only when there\r\n    are no blank lines between them.\r\n  - g:softtabstops_editor_guide_start_num (default: 0). Controls the column\r\n    number sequence in the tab editor. Should be between 0 to 9.\r\n  - g:softtabstops_editor_guide_end_num (default: 9). Controls the column\r\n    number sequence in the tab editor. Should be between 0 to 9 and greater\r\n    than g:softtabstops_editor_guide_start_num.\r\n  - g:softtabstops_restore_original_map (default: 0). Set to 1 to enable the\r\n    experimental feature to save and restore maps while toggling on and off.\r\n\r\nLimitations:\r\n  - Can only insert all spaces, not a mix of tabs and spaces.\r\n","install_details":"Unzip the file into your runtime. Also make sure the latest version of genutils (vimscript #197) is installed.","5":"Unzip the file into your runtime. Also make sure the latest version of genutils (vimscript #197) is installed.","first_name":"Hari Krishna","6":"Hari Krishna","last_name":"Dara","7":"Dara","releases":[{"0":"2797","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"softtabstops-1.0.zip","4":"softtabstops-1.0.zip","src_id":"11467","5":"11467","creation_date":"1254448826","6":"1254448826"}]},"2796":{"script_id":"2796","0":"2796","script_name":"CheckAttach.vim","1":"CheckAttach.vim","script_type":"utility","2":"utility","summary":"Check for attachments when writing mails with mutt","3":"Check for attachments when writing mails with mutt","description":"If you like the plugin, please rate it!\r\n\r\nYou can now follow the plugin at github: http:\/\/github.com\/chrisbra\/CheckAttach\r\n\r\n                                                                  *CheckAttach*\r\n1. Functionality\r\n\r\nWhen using mutt as your mail user agent, you can specify which files to attach\r\nusing the pseudo header :Attach. This only works when edit_headers is set in\r\nyour .muttrc configuration file. See the mutt manual for further information\r\nabout that topic.\r\n\r\nA simple version of this plugin has been posted to the mutt-users list (see\r\nhttp:\/\/marc.info\/?i=20090116091203.GB3197%20()%20256bit%20!%20org) and\r\nafter using it for some time, I decided to make a plugin out of it.\r\n\r\nThis plugin checks, whether certain keywords exist in your mail, and if found,\r\nyou'll be asked to attach the files. This is done to prevent that you sent\r\nmails in which you announce to attach some files but actually forget to attach\r\nthe files so that your have to write a second mail which often is quite\r\nembarassing.\r\n\r\nTherefore this plugin checks for the presence of keywords which indicate that\r\nan attachment should be attached. If if finds these keywords, the plugin will\r\nask you for the files to attach, whenever you save your mail.\r\n\r\nThis looks like this:\r\nAttach file: (leave empty to abbort):\r\n\r\nAt that prompt you can specify any file you'd like to attach. It allows\r\nfilename completion, so you can use <Tab> to let vim complete file paths.\r\nAdditionally you can specify glob patterns and let vim attach all files, that\r\nmatch the pattern. So if you enter ~\/.vim\/plugin\/*.vim vim would add for each\r\nplugin it finds an Attach-header.  If you enter an empty value or \"n\" (without\r\nthe quotes), no file will be attached.\r\n\r\nThe plugin will by default escape blank space in your filename by using '\\'.\r\nmutt before version 1.5.20 had a bug, that would not allow you to add files\r\nwhose filename contain spaces. If you are using mutt version smaller 1.5.20\r\nthis means you would have to rename those files first before attaching them.\r\n(See mutt bug 3179: http:\/\/dev.mutt.org\/trac\/ticket\/3179)\r\n\r\nYou can specify which keywords will be searched by setting the\r\ng:attach_check_keywords variable. By default this variable is specified as:\r\nlet g:attach_check_keywords = 'attach,attachment,angeh\u00c3\u00a4ngt,Anhang'\r\nso that it can handle German and English. If you would like to add the keyword\r\nfoobar, use this command:\r\nlet g:attach_check_keywords .=',foobar'\r\n\r\n                                         *EnableCheckAttach* *DisableCheckAttach*\r\nYou can disable the plugin by issuing the command\r\n:DisableCheckAttach\r\nEnabling the attachment check is then again enabled by issuing\r\n:EnableCheckAttach\r\nYou can also use the ! attribute when saving your buffer to temporarily skip\r\nthe check. So if you use :w! the buffer will not be checked for attachments,\r\nonly if you use :w it will.\r\n\r\n\r\n==============================================================================\r\n2. CheckAttach History                                      *CheckAttach-history*\r\n    0.2: Sept 29, 2009     Added Documentation\r\n    0.1: Sept 29, 2009     First working version, using simple commands\r\n\r\n==============================================================================\r\nvim:tw=78:ts=8:ft=help","4":"If you like the plugin, please rate it!\r\n\r\nYou can now follow the plugin at github: http:\/\/github.com\/chrisbra\/CheckAttach\r\n\r\n                                                                  *CheckAttach*\r\n1. Functionality\r\n\r\nWhen using mutt as your mail user agent, you can specify which files to attach\r\nusing the pseudo header :Attach. This only works when edit_headers is set in\r\nyour .muttrc configuration file. See the mutt manual for further information\r\nabout that topic.\r\n\r\nA simple version of this plugin has been posted to the mutt-users list (see\r\nhttp:\/\/marc.info\/?i=20090116091203.GB3197%20()%20256bit%20!%20org) and\r\nafter using it for some time, I decided to make a plugin out of it.\r\n\r\nThis plugin checks, whether certain keywords exist in your mail, and if found,\r\nyou'll be asked to attach the files. This is done to prevent that you sent\r\nmails in which you announce to attach some files but actually forget to attach\r\nthe files so that your have to write a second mail which often is quite\r\nembarassing.\r\n\r\nTherefore this plugin checks for the presence of keywords which indicate that\r\nan attachment should be attached. If if finds these keywords, the plugin will\r\nask you for the files to attach, whenever you save your mail.\r\n\r\nThis looks like this:\r\nAttach file: (leave empty to abbort):\r\n\r\nAt that prompt you can specify any file you'd like to attach. It allows\r\nfilename completion, so you can use <Tab> to let vim complete file paths.\r\nAdditionally you can specify glob patterns and let vim attach all files, that\r\nmatch the pattern. So if you enter ~\/.vim\/plugin\/*.vim vim would add for each\r\nplugin it finds an Attach-header.  If you enter an empty value or \"n\" (without\r\nthe quotes), no file will be attached.\r\n\r\nThe plugin will by default escape blank space in your filename by using '\\'.\r\nmutt before version 1.5.20 had a bug, that would not allow you to add files\r\nwhose filename contain spaces. If you are using mutt version smaller 1.5.20\r\nthis means you would have to rename those files first before attaching them.\r\n(See mutt bug 3179: http:\/\/dev.mutt.org\/trac\/ticket\/3179)\r\n\r\nYou can specify which keywords will be searched by setting the\r\ng:attach_check_keywords variable. By default this variable is specified as:\r\nlet g:attach_check_keywords = 'attach,attachment,angeh\u00c3\u00a4ngt,Anhang'\r\nso that it can handle German and English. If you would like to add the keyword\r\nfoobar, use this command:\r\nlet g:attach_check_keywords .=',foobar'\r\n\r\n                                         *EnableCheckAttach* *DisableCheckAttach*\r\nYou can disable the plugin by issuing the command\r\n:DisableCheckAttach\r\nEnabling the attachment check is then again enabled by issuing\r\n:EnableCheckAttach\r\nYou can also use the ! attribute when saving your buffer to temporarily skip\r\nthe check. So if you use :w! the buffer will not be checked for attachments,\r\nonly if you use :w it will.\r\n\r\n\r\n==============================================================================\r\n2. CheckAttach History                                      *CheckAttach-history*\r\n    0.2: Sept 29, 2009     Added Documentation\r\n    0.1: Sept 29, 2009     First working version, using simple commands\r\n\r\n==============================================================================\r\nvim:tw=78:ts=8:ft=help","install_details":"Open CheckAttach.vba in Vim and source the file:\r\n\r\n:so %\r\n\r\nThis will install the plugin into your $HOME\/.vim\/plugin directory and the documentation into your $HOME\/.vim\/doc directory.\r\n\r\nSee also the help for installing Vimball-Archives (:h vimball-intro)\r\n\r\nTake a look at :h CheckAttach.txt for the documenation","5":"Open CheckAttach.vba in Vim and source the file:\r\n\r\n:so %\r\n\r\nThis will install the plugin into your $HOME\/.vim\/plugin directory and the documentation into your $HOME\/.vim\/doc directory.\r\n\r\nSee also the help for installing Vimball-Archives (:h vimball-intro)\r\n\r\nTake a look at :h CheckAttach.txt for the documenation","first_name":"Christian","6":"Christian","last_name":"Brabandt","7":"Brabandt","releases":[{"0":"2796","vim_version":"7.4","1":"7.4","script_version":"17","2":"17","version_comment":"- Always use the full path to the attached file. Matters if the working directory of mutt and vim disagree.\n   - Using :AttachFile with ranger was broken (reported by Ram-Z at https:\/\/github.com\/chrisbra\/CheckAttach\/issues\/5, thanks!)\n(automatically uploaded)","3":"- Always use the full path to the attached file. Matters if the working directory of mutt and vim disagree.\n   - Using :AttachFile with ranger was broken (reported by Ram-Z at https:\/\/github.com\/chrisbra\/CheckAttach\/issues\/5, thanks!)\n(automatically uploaded)","package":"CheckAttach-0.17.vmb","4":"CheckAttach-0.17.vmb","src_id":"22797","5":"22797","creation_date":"1421352187","6":"1421352187"},{"0":"2796","vim_version":"7.4","1":"7.4","script_version":"16","2":"16","version_comment":"- allow to specify several patterns after |:AttachFile| (issue #4, https:\/\/github.com\/chrisbra\/CheckAttach\/issues\/4 reported by AguirreIF, thanks!)\n(automatically uploaded)","3":"- allow to specify several patterns after |:AttachFile| (issue #4, https:\/\/github.com\/chrisbra\/CheckAttach\/issues\/4 reported by AguirreIF, thanks!)\n(automatically uploaded)","package":"CheckAttach-0.16.vmb","4":"CheckAttach-0.16.vmb","src_id":"21683","5":"21683","creation_date":"1395959162","6":"1395959162"},{"0":"2796","vim_version":"7.3","1":"7.3","script_version":"15","2":"15","version_comment":"- don't match Attach: header when trying to look for matching attachment keywords\n(automatically uploaded)","3":"- don't match Attach: header when trying to look for matching attachment keywords\n(automatically uploaded)","package":"CheckAttach-0.15.vmb","4":"CheckAttach-0.15.vmb","src_id":"20648","5":"20648","creation_date":"1376511905","6":"1376511905"},{"0":"2796","vim_version":"7.3","1":"7.3","script_version":"14","2":"14","version_comment":"Fix issue https:\/\/github.com\/chrisbra\/CheckAttach\/issues\/2 reportedby daaugusto, thanks!\n(automatically uploaded)","3":"Fix issue https:\/\/github.com\/chrisbra\/CheckAttach\/issues\/2 reportedby daaugusto, thanks!\n(automatically uploaded)","package":"CheckAttach-0.14.vmb","4":"CheckAttach-0.14.vmb","src_id":"18134","5":"18134","creation_date":"1339839851","6":"1339839851"},{"0":"2796","vim_version":"7.3","1":"7.3","script_version":"13","2":"13","version_comment":"-allow plugin to use an external file manager\n  for selecting the files (suggested by mutt-users\n  mailinglist)\n-Command definition will be buffer local\n-Don't check for matches of the keywords in the\n  quoted of the message (suggested by Sebastian\n  Tramp, thanks!)\n-Don't check for matches inside the header (start at\n  subject line, suggested by Sebastian Tramp,\n  thanks!)\n-Only check as long, as no :Attach header is\n  available when the g:checkattach_once variable is\n  set (suggested by Sebastian Tramp, thanks!)\n-Documentation update\n(automatically uploaded)","3":"-allow plugin to use an external file manager\n  for selecting the files (suggested by mutt-users\n  mailinglist)\n-Command definition will be buffer local\n-Don't check for matches of the keywords in the\n  quoted of the message (suggested by Sebastian\n  Tramp, thanks!)\n-Don't check for matches inside the header (start at\n  subject line, suggested by Sebastian Tramp,\n  thanks!)\n-Only check as long, as no :Attach header is\n  available when the g:checkattach_once variable is\n  set (suggested by Sebastian Tramp, thanks!)\n-Documentation update\n(automatically uploaded)","package":"CheckAttach-0.13.vmb","4":"CheckAttach-0.13.vmb","src_id":"16835","5":"16835","creation_date":"1320788253","6":"1320788253"},{"0":"2796","vim_version":"7.3","1":"7.3","script_version":"12","2":"12","version_comment":"Update the plugin (include some changes, that got lost with 0.11)\n(automatically uploaded)","3":"Update the plugin (include some changes, that got lost with 0.11)\n(automatically uploaded)","package":"CheckAttach-0.12.vmb","4":"CheckAttach-0.12.vmb","src_id":"16742","5":"16742","creation_date":"1319572859","6":"1319572859"},{"0":"2796","vim_version":"7.3","1":"7.3","script_version":"11","2":"11","version_comment":"-Make a filetype plugin out of it, it does not make sense to have it as plugin, since its only use is with mutt (aka ft: mail)\n-Documentation update\n(automatically uploaded)","3":"-Make a filetype plugin out of it, it does not make sense to have it as plugin, since its only use is with mutt (aka ft: mail)\n-Documentation update\n(automatically uploaded)","package":"CheckAttach-0.11.vmb","4":"CheckAttach-0.11.vmb","src_id":"16607","5":"16607","creation_date":"1317412002","6":"1317412002"},{"0":"2796","vim_version":"7.3","1":"7.3","script_version":"10","2":"10","version_comment":"Spelling fix by Scott Stevenson (Thanks!)\n(automatically uploaded)","3":"Spelling fix by Scott Stevenson (Thanks!)\n(automatically uploaded)","package":"CheckAttach-0.10.vba","4":"CheckAttach-0.10.vba","src_id":"14778","5":"14778","creation_date":"1295292870","6":"1295292870"},{"0":"2796","vim_version":"7.3","1":"7.3","script_version":"9","2":"9","version_comment":"include new command |:AttachFile| for attaching several files using a glob pattern\n(automatically uploaded)","3":"include new command |:AttachFile| for attaching several files using a glob pattern\n(automatically uploaded)","package":"CheckAttach-0.9.vba","4":"CheckAttach-0.9.vba","src_id":"14543","5":"14543","creation_date":"1292572460","6":"1292572460"},{"0":"2796","vim_version":"7.3","1":"7.3","script_version":"8","2":"8","version_comment":"- Make ftplugin instead of plugin (don't trigger check of filetypes)\n- clear matchlist on next run\n- code cleanup\n(automatically uploaded)","3":"- Make ftplugin instead of plugin (don't trigger check of filetypes)\n- clear matchlist on next run\n- code cleanup\n(automatically uploaded)","package":"CheckAttach-0.8.vba","4":"CheckAttach-0.8.vba","src_id":"14407","5":"14407","creation_date":"1291144726","6":"1291144726"},{"0":"2796","vim_version":"7.0","1":"7.0","script_version":"0.7","2":"0.7","version_comment":"0.7: May  05, 2010:\r\nForce checking the filetype\r\n0.6: May  05, 2010:\r\n- Force filetype detection, which did prevent of the plugin to be working correctly\r\n- Created a public github repository at http:\/\/github.com\/chrisbra\/CheckAttach\r\n- Small changes to the documentation\r\n(unreleased)","3":"0.7: May  05, 2010:\r\nForce checking the filetype\r\n0.6: May  05, 2010:\r\n- Force filetype detection, which did prevent of the plugin to be working correctly\r\n- Created a public github repository at http:\/\/github.com\/chrisbra\/CheckAttach\r\n- Small changes to the documentation\r\n(unreleased)","package":"CheckAttach-0.7.vba","4":"CheckAttach-0.7.vba","src_id":"12956","5":"12956","creation_date":"1273088217","6":"1273088217"},{"0":"2796","vim_version":"6.0","1":"6.0","script_version":"0.5","2":"0.5","version_comment":"Search without matching case.\r\nThis prevented CheckAttach from working correctly, which made me sent mails without attaching the files. Change default keywords a little bit","3":"Search without matching case.\r\nThis prevented CheckAttach from working correctly, which made me sent mails without attaching the files. Change default keywords a little bit","package":"CheckAttach.vba","4":"CheckAttach.vba","src_id":"12544","5":"12544","creation_date":"1267565650","6":"1267565650"},{"0":"2796","vim_version":"7.0","1":"7.0","script_version":"0.4","2":"0.4","version_comment":"Highlight matching keywords\r\nuse g:attach_check_ft to define for which filetypes to enable the plugin","3":"Highlight matching keywords\r\nuse g:attach_check_ft to define for which filetypes to enable the plugin","package":"CheckAttach.vba","4":"CheckAttach.vba","src_id":"12185","5":"12185","creation_date":"1264498079","6":"1264498079"},{"0":"2796","vim_version":"7.0","1":"7.0","script_version":"0.3","2":"0.3","version_comment":"Fixed Copyright statement,\r\nenabled GetLatestScripts","3":"Fixed Copyright statement,\r\nenabled GetLatestScripts","package":"CheckAttach.vba","4":"CheckAttach.vba","src_id":"11461","5":"11461","creation_date":"1254376408","6":"1254376408"},{"0":"2796","vim_version":"7.0","1":"7.0","script_version":"0.2","2":"0.2","version_comment":"Initial upload","3":"Initial upload","package":"CheckAttach.vba","4":"CheckAttach.vba","src_id":"11455","5":"11455","creation_date":"1254262289","6":"1254262289"}]},"2795":{"script_id":"2795","0":"2795","script_name":"Functionator","1":"Functionator","script_type":"utility","2":"utility","summary":"Simple script that shows the name of the current function","3":"Simple script that shows the name of the current function","description":"This is a simple script I use that shows the name of the function the cursor is currently in when gn is pressed, and goes to the [count] line of that function when [count]gn is used.\r\n\r\nCurrently supports: C, Objective-C, JavaScript, Python, and Vim script.","4":"This is a simple script I use that shows the name of the function the cursor is currently in when gn is pressed, and goes to the [count] line of that function when [count]gn is used.\r\n\r\nCurrently supports: C, Objective-C, JavaScript, Python, and Vim script.","install_details":"Place functionator.vim in ~\/.vim\/plugin or equivalent.","5":"Place functionator.vim in ~\/.vim\/plugin or equivalent.","first_name":"Michael","6":"Michael","last_name":"Sanders","7":"Sanders","releases":[{"0":"2795","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"functionator.vim","4":"functionator.vim","src_id":"11454","5":"11454","creation_date":"1254244064","6":"1254244064"}]},"2794":{"script_id":"2794","0":"2794","script_name":"phpErrorMarker","1":"phpErrorMarker","script_type":"ftplugin","2":"ftplugin","summary":"Mark syntax errors in php file","3":"Mark syntax errors in php file","description":"phpErrorMarker set makeprg et errroformat automaticaly for php file.\r\nA call to :make launch php syntax checking and set sign (:h sign for more informations) if there are any errors in file.\r\nSome variables may be interesting :\r\ng:phpErrorMarker#autowrite : if true, file will be automaticaly write before syntax checking, default is \"0\".\r\ng:phpErrorMarker#php : path to php binary, default is \"php\".\r\ng:phpErrorMarker#textError : sign used for error, default is \"><\".\r\ng:phpErrorMarker#textWarning : sign used for warning, default is \"--\".\r\ng:phpErrorMarker#automake : if true, make is automaticaly done after a write command like \":w\", default is \"0\".\r\ng:phpErrorMarker#openQuickfix : if true, quickfix window will be automaticaly opened after \":make\".\r\ng:phpErrorMarker#filter: if not empty, define the filter utility to clean PHP output.\r\nSet these variables in your .vimrc to override default values, like that :\r\n\r\nlet g:phpErrorMarker#autowrite = 1\r\n\r\nPlease, report any bug to phpErrorMarker.vim[..at..]mageekbox.net. ","4":"phpErrorMarker set makeprg et errroformat automaticaly for php file.\r\nA call to :make launch php syntax checking and set sign (:h sign for more informations) if there are any errors in file.\r\nSome variables may be interesting :\r\ng:phpErrorMarker#autowrite : if true, file will be automaticaly write before syntax checking, default is \"0\".\r\ng:phpErrorMarker#php : path to php binary, default is \"php\".\r\ng:phpErrorMarker#textError : sign used for error, default is \"><\".\r\ng:phpErrorMarker#textWarning : sign used for warning, default is \"--\".\r\ng:phpErrorMarker#automake : if true, make is automaticaly done after a write command like \":w\", default is \"0\".\r\ng:phpErrorMarker#openQuickfix : if true, quickfix window will be automaticaly opened after \":make\".\r\ng:phpErrorMarker#filter: if not empty, define the filter utility to clean PHP output.\r\nSet these variables in your .vimrc to override default values, like that :\r\n\r\nlet g:phpErrorMarker#autowrite = 1\r\n\r\nPlease, report any bug to phpErrorMarker.vim[..at..]mageekbox.net. ","install_details":"Download vimball, open it with vim, and do :so %. \r\nCreate or open a php file, and do :make.","5":"Download vimball, open it with vim, and do :so %. \r\nCreate or open a php file, and do :make.","first_name":"Frederic","6":"Frederic","last_name":"Hardy","7":"Hardy","releases":[{"0":"2794","vim_version":"7.0","1":"7.0","script_version":"0.0.7","2":"0.0.7","version_comment":"Add filtering support to clean `php -l ` output.\r\nFor example, do `let g:phpErrorMarker#filter=\"grep -v '^^M$'\" to remove lines which contains only \"\\r\".\r\nAdd phpErrorMarker#configure() to reconfigure phpErrorMarker if one of its global variables was updated.","3":"Add filtering support to clean `php -l ` output.\r\nFor example, do `let g:phpErrorMarker#filter=\"grep -v '^^M$'\" to remove lines which contains only \"\\r\".\r\nAdd phpErrorMarker#configure() to reconfigure phpErrorMarker if one of its global variables was updated.","package":"phpErrorMarker.vmb","4":"phpErrorMarker.vmb","src_id":"24407","5":"24407","creation_date":"1469712434","6":"1469712434"},{"0":"2794","vim_version":"7.0","1":"7.0","script_version":"0.0.6","2":"0.0.6","version_comment":"Improve errorformat to match more precisely PHP parse error message.","3":"Improve errorformat to match more precisely PHP parse error message.","package":"phpErrorMarker.vmb","4":"phpErrorMarker.vmb","src_id":"19225","5":"19225","creation_date":"1356097488","6":"1356097488"},{"0":"2794","vim_version":"6.0","1":"6.0","script_version":"0.0.5","2":"0.0.5","version_comment":"Autocommand about quickfix window are now called only when :make is used.","3":"Autocommand about quickfix window are now called only when :make is used.","package":"phpErrorMarker.vmb","4":"phpErrorMarker.vmb","src_id":"19205","5":"19205","creation_date":"1355843100","6":"1355843100"},{"0":"2794","vim_version":"6.0","1":"6.0","script_version":"0.0.4","2":"0.0.4","version_comment":"Add a call to <C-L> after autowrite to remove a screen bug in vim.","3":"Add a call to <C-L> after autowrite to remove a screen bug in vim.","package":"phpErrorMarker.vba","4":"phpErrorMarker.vba","src_id":"11488","5":"11488","creation_date":"1254823591","6":"1254823591"},{"0":"2794","vim_version":"6.0","1":"6.0","script_version":"0.0.3","2":"0.0.3","version_comment":"Remove bugs.","3":"Remove bugs.","package":"phpErrorMarker.vba","4":"phpErrorMarker.vba","src_id":"11448","5":"11448","creation_date":"1254141242","6":"1254141242"},{"0":"2794","vim_version":"6.0","1":"6.0","script_version":"0.0.2","2":"0.0.2","version_comment":"Add GLVS.\r\nAdd g:phpErrorMarker#openQuickfix variable, default is \"1\".","3":"Add GLVS.\r\nAdd g:phpErrorMarker#openQuickfix variable, default is \"1\".","package":"phpErrorMarker.vba","4":"phpErrorMarker.vba","src_id":"11433","5":"11433","creation_date":"1253888009","6":"1253888009"},{"0":"2794","vim_version":"6.0","1":"6.0","script_version":"0.0.1","2":"0.0.1","version_comment":"Initial upload","3":"Initial upload","package":"phpErrorMarker.vba","4":"phpErrorMarker.vba","src_id":"11432","5":"11432","creation_date":"1253887367","6":"1253887367"}]},"2793":{"script_id":"2793","0":"2793","script_name":"hybridevel","1":"hybridevel","script_type":"utility","2":"utility","summary":"plugin for hybrid program","3":"plugin for hybrid program","description":"This plugin provides lots of functions for hybrid project. Each function has \r\nthe shortcut and the Ex command.\r\n\r\nNow the plugin supports the following projects: c,c++,java,make,ant,\r\nflash, and matlab are listed in the $VIMRUNTIME\/development directory. You\r\ncan write scripts such as python.vim to support other projects.","4":"This plugin provides lots of functions for hybrid project. Each function has \r\nthe shortcut and the Ex command.\r\n\r\nNow the plugin supports the following projects: c,c++,java,make,ant,\r\nflash, and matlab are listed in the $VIMRUNTIME\/development directory. You\r\ncan write scripts such as python.vim to support other projects.","install_details":"","5":"","first_name":"Zhenliang","6":"Zhenliang","last_name":"Ju","7":"Ju","releases":[{"0":"2793","vim_version":"7.0","1":"7.0","script_version":"7.0","2":"7.0","version_comment":"Its dependent plugin shellinsidevim.vim has been combined in this plugin.\r\nSo you can execute shell command directly with ex command :Shell,\r\nand the output will display in the quickfix window.\r\n\r\nBTW, if the shell command is a compiler that your vim supports, the compiler will be sourced.","3":"Its dependent plugin shellinsidevim.vim has been combined in this plugin.\r\nSo you can execute shell command directly with ex command :Shell,\r\nand the output will display in the quickfix window.\r\n\r\nBTW, if the shell command is a compiler that your vim supports, the compiler will be sourced.","package":"vimhybridevel.tar.bz2","4":"vimhybridevel.tar.bz2","src_id":"12284","5":"12284","creation_date":"1265179471","6":"1265179471"},{"0":"2793","vim_version":"7.2","1":"7.2","script_version":"7.0","2":"7.0","version_comment":"Initial upload","3":"Initial upload","package":"Hybridevel.tar.bz2","4":"Hybridevel.tar.bz2","src_id":"11418","5":"11418","creation_date":"1253690499","6":"1253690499"}]},"2792":{"script_id":"2792","0":"2792","script_name":"perdirvimrc: Autoload vimrc files per di","1":"perdirvimrc: Autoload vimrc files per di","script_type":"utility","2":"utility","summary":"Loads vimrc files that are above the opened file in the directory tree","3":"Loads vimrc files that are above the opened file in the directory tree","description":"This script loads Vim configuration files at startup beginning\r\nfrom the root directory down to the current working directory.\r\n\r\nThis is useful when you want to to set up a specific configuration that\r\nis only loaded when you edit files within a certain directory.\r\n \r\nLet's look at a common situation. To configure Vim depending on your\r\nproject, your tree would look like this:\r\n\r\n~\/projects  .................................. Your programming projects\r\n~\/projects\/.vim  .......................... Vim settings for all your projects\r\n~\/projects\/c-projects  ................ Your C projects\r\n~\/projects\/c-projects\/.vim  ........ Vim settings for your C projects\r\n~\/projects\/php-projects  ........... Your PHP projects\r\n~\/projects\/php-projects\/.vim  ... Vim settings for your PHP projects\r\n\r\nWhen you open the file ~\/projects\/c-projects\/main.c the plugin loads\r\nthis files in the given order:\r\n\r\n~\/projects\/.vim\r\n~\/projects\/c-projects\/.vim\r\n\r\nThe scripts autoloads files with the name\r\n\r\n      _vimrc\r\n      _vim\r\n      .vimrc\r\n      .vim\r\n\r\n","4":"This script loads Vim configuration files at startup beginning\r\nfrom the root directory down to the current working directory.\r\n\r\nThis is useful when you want to to set up a specific configuration that\r\nis only loaded when you edit files within a certain directory.\r\n \r\nLet's look at a common situation. To configure Vim depending on your\r\nproject, your tree would look like this:\r\n\r\n~\/projects  .................................. Your programming projects\r\n~\/projects\/.vim  .......................... Vim settings for all your projects\r\n~\/projects\/c-projects  ................ Your C projects\r\n~\/projects\/c-projects\/.vim  ........ Vim settings for your C projects\r\n~\/projects\/php-projects  ........... Your PHP projects\r\n~\/projects\/php-projects\/.vim  ... Vim settings for your PHP projects\r\n\r\nWhen you open the file ~\/projects\/c-projects\/main.c the plugin loads\r\nthis files in the given order:\r\n\r\n~\/projects\/.vim\r\n~\/projects\/c-projects\/.vim\r\n\r\nThe scripts autoloads files with the name\r\n\r\n      _vimrc\r\n      _vim\r\n      .vimrc\r\n      .vim\r\n\r\n","install_details":"Copy \"perdirvimrc.vim\" to your local plugin folder.","5":"Copy \"perdirvimrc.vim\" to your local plugin folder.","first_name":"Wolfgang","6":"Wolfgang","last_name":"Plaschg","7":"Plaschg","releases":[{"0":"2792","vim_version":"6.0","1":"6.0","script_version":"0.2","2":"0.2","version_comment":"- removed unix-specific bugs","3":"- removed unix-specific bugs","package":"perdirvimrc.vim","4":"perdirvimrc.vim","src_id":"11440","5":"11440","creation_date":"1254062332","6":"1254062332"},{"0":"2792","vim_version":"6.0","1":"6.0","script_version":"0.2","2":"0.2","version_comment":"- per directory vim-resources are (re-)loaded after BufRead events (File open, Buffer change etc.)","3":"- per directory vim-resources are (re-)loaded after BufRead events (File open, Buffer change etc.)","package":"perdirvimrc.vim","4":"perdirvimrc.vim","src_id":"11419","5":"11419","creation_date":"1253691640","6":"1253691640"},{"0":"2792","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"perdirvimrc.vim","4":"perdirvimrc.vim","src_id":"11412","5":"11412","creation_date":"1253442604","6":"1253442604"}]},"2791":{"script_id":"2791","0":"2791","script_name":"popup_it","1":"popup_it","script_type":"utility","2":"utility","summary":"Auto complete popup plugin","3":"Auto complete popup plugin","description":"use regexp to match line pattern\r\nthen auto popup complete menu.\r\ndefault support c c.gtk tex html css javascript \r\n\r\n\"             let g:usrPopup= {}\r\n\"             let s:usrPopup[\"type\"] = [\r\n\"                         \\ {'cmd'     : \"\\<c-n>\",\r\n\"                         \\  'pattern' : ['xx', 'yy'],\r\n\"                         \\  'exclude' : ['zz'],\r\n\"                         \\ },\r\n\"                         \\{item2}\r\n\"                         \\{item3}\r\n\"                         \\]\r\n","4":"use regexp to match line pattern\r\nthen auto popup complete menu.\r\ndefault support c c.gtk tex html css javascript \r\n\r\n\"             let g:usrPopup= {}\r\n\"             let s:usrPopup[\"type\"] = [\r\n\"                         \\ {'cmd'     : \"\\<c-n>\",\r\n\"                         \\  'pattern' : ['xx', 'yy'],\r\n\"                         \\  'exclude' : ['zz'],\r\n\"                         \\ },\r\n\"                         \\{item2}\r\n\"                         \\{item3}\r\n\"                         \\]\r\n","install_details":"Put this file in your VIM plugins dir","5":"Put this file in your VIM plugins dir","first_name":"su","6":"su","last_name":"su","7":"su","releases":[{"0":"2791","vim_version":"6.0","1":"6.0","script_version":"1.07","2":"1.07","version_comment":"Let input more smooth\r\nSet autopopup delay time.\r\n\r\nlet g:PopupDelayTime=400  \r\nput it to .vimrc (ms)   ","3":"Let input more smooth\r\nSet autopopup delay time.\r\n\r\nlet g:PopupDelayTime=400  \r\nput it to .vimrc (ms)   ","package":"popup_it.vim","4":"popup_it.vim","src_id":"12900","5":"12900","creation_date":"1272195779","6":"1272195779"}]},"2790":{"script_id":"2790","0":"2790","script_name":"cmdline-increment.vim","1":"cmdline-increment.vim","script_type":"utility","2":"utility","summary":"increment, decrement commandline number.","3":"increment, decrement commandline number.","description":"Increment last appearing number in commandline-mode command with Control-a ,\r\nand decrement with Control-x .\r\n\r\n    <C-a> increment commandline last appearing number.\r\n    <C-x> decrement commandline last appearing number.\r\n\r\n\r\n------------------------------------------------------------------------------\r\n[Usage]\r\n\r\n1.  Enter commandline mode.\r\n2.  Enter next command.\r\n\r\n    :edit workfile_1.txt\r\n\r\n3.  And Press Control-a , or press Control-x .\r\n\r\n\r\n------------------------------------------------------------------------------\r\n[Customized Mapping]\r\n\r\nIf you will customize increment, decrement mapping,\r\nadd put these code to your vimrc .\r\n\r\n    \" (for example)\r\n    \" increment with Shift-Up\r\n    cmap <S-Up> <Plug>IncrementCommandLineNumber\r\n    \" decrement with Shift-Down\r\n    cmap <S-Down> <Plug>DecrementCommandLineNumber\r\n","4":"Increment last appearing number in commandline-mode command with Control-a ,\r\nand decrement with Control-x .\r\n\r\n    <C-a> increment commandline last appearing number.\r\n    <C-x> decrement commandline last appearing number.\r\n\r\n\r\n------------------------------------------------------------------------------\r\n[Usage]\r\n\r\n1.  Enter commandline mode.\r\n2.  Enter next command.\r\n\r\n    :edit workfile_1.txt\r\n\r\n3.  And Press Control-a , or press Control-x .\r\n\r\n\r\n------------------------------------------------------------------------------\r\n[Customized Mapping]\r\n\r\nIf you will customize increment, decrement mapping,\r\nadd put these code to your vimrc .\r\n\r\n    \" (for example)\r\n    \" increment with Shift-Up\r\n    cmap <S-Up> <Plug>IncrementCommandLineNumber\r\n    \" decrement with Shift-Down\r\n    cmap <S-Down> <Plug>DecrementCommandLineNumber\r\n","install_details":"copy cmdline-increment.vim to your plugin directory.","5":"copy cmdline-increment.vim to your plugin directory.","first_name":"omi","6":"omi","last_name":"taku","7":"taku","releases":[{"0":"2790","vim_version":"7.0","1":"7.0","script_version":"0.2","2":"0.2","version_comment":"- plugin is now not using 'l' register.\r\n- below 0 number decrement is newly not supported.\r\n  minial value is 0.\r\n- default mapping is switched to <c-a>, <c-x>.\r\n- custom mapping is supported.\r\n","3":"- plugin is now not using 'l' register.\r\n- below 0 number decrement is newly not supported.\r\n  minial value is 0.\r\n- default mapping is switched to <c-a>, <c-x>.\r\n- custom mapping is supported.\r\n","package":"cmdline-increment.vim","4":"cmdline-increment.vim","src_id":"11405","5":"11405","creation_date":"1253290880","6":"1253290880"},{"0":"2790","vim_version":"7.2","1":"7.2","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"cmdline-increment.vim","4":"cmdline-increment.vim","src_id":"11398","5":"11398","creation_date":"1253207323","6":"1253207323"}]},"2789":{"script_id":"2789","0":"2789","script_name":"rargs.vim","1":"rargs.vim","script_type":"utility","2":"utility","summary":"read the contents of many files at one time.","3":"read the contents of many files at one time.","description":"':RArgs' command that this plugin defined can read\r\nselected files contents at one time.\r\n( like :read command, but for multiple files. )\r\n\r\n\r\n------------------------------------------------------------------------------\r\n[command format]\r\n\r\n\" read {filename1}, {filename2}, and {filename3},\r\n\" contents are inserted into N.\r\n:[N]RArgs [++opt] {filename1} [{filename2} {filename3}...]\r\n\r\n[N]\r\n    contents read are inserted into the specified line,\r\n    or not specify line, contents are inserted into cursor position.\r\n\r\n[++opt]\r\n    file reading option.\r\n    see ':help ++opt', for more information.\r\n\r\n{filename1} [{filename2} {filename3}...]\r\n    filepath list.\r\n\r\n\r\n------------------------------------------------------------------------------\r\n[filepath parameters]\r\n\r\n\" read sample1.txt, sample2.txt, and sample3.txt\r\n:RArgs sample1.txt sample2.txt sample3.txt\r\n\r\n\" wildcards are allowed\r\n:RArgs sample*\r\n\r\n\" Vim special keywords are allowed\r\n:RArgs #2 #4 #6<.bak\r\n\r\n\" reading the file at multiple times are allowed\r\n:RArgs sample1.txt sample1.txt sample1.txt\r\n\r\n\" file encoding, file format\r\n:RArgs ++enc=utf-8 ++ff=unix sample1.txt sample2.txt sample3.txt\r\n\r\n\r\n------------------------------------------------------------------------------\r\n[inserting file position]\r\n\r\nIf you do not specify line number,\r\nthe contents of selected files are inserted into cursor line.\r\n\r\n\" contents are inserted into cursor line.\r\n:RArgs sample1.txt sample2.txt sample3.txt\r\n\r\n\" contents are inserted into specified line.\r\n:200RArgs sample1.txt sample2.txt sample3.txt\r\n\r\n\" contents are inserted into first line of buffer.\r\n:0RArgs sample1.txt sample2.txt sample3.txt\r\n\r\n\r\n------------------------------------------------------------------------------\r\n[Configuration]\r\n\r\n'g:rargs_exit_when_error'\r\n\r\nIf you set 1 to 'g:rargs_exit_when_error',\r\nexit when error is found. Default aciion is error is ignored.\r\n\r\nlet g:rargs_exit_when_error = '1'\r\n\r\n","4":"':RArgs' command that this plugin defined can read\r\nselected files contents at one time.\r\n( like :read command, but for multiple files. )\r\n\r\n\r\n------------------------------------------------------------------------------\r\n[command format]\r\n\r\n\" read {filename1}, {filename2}, and {filename3},\r\n\" contents are inserted into N.\r\n:[N]RArgs [++opt] {filename1} [{filename2} {filename3}...]\r\n\r\n[N]\r\n    contents read are inserted into the specified line,\r\n    or not specify line, contents are inserted into cursor position.\r\n\r\n[++opt]\r\n    file reading option.\r\n    see ':help ++opt', for more information.\r\n\r\n{filename1} [{filename2} {filename3}...]\r\n    filepath list.\r\n\r\n\r\n------------------------------------------------------------------------------\r\n[filepath parameters]\r\n\r\n\" read sample1.txt, sample2.txt, and sample3.txt\r\n:RArgs sample1.txt sample2.txt sample3.txt\r\n\r\n\" wildcards are allowed\r\n:RArgs sample*\r\n\r\n\" Vim special keywords are allowed\r\n:RArgs #2 #4 #6<.bak\r\n\r\n\" reading the file at multiple times are allowed\r\n:RArgs sample1.txt sample1.txt sample1.txt\r\n\r\n\" file encoding, file format\r\n:RArgs ++enc=utf-8 ++ff=unix sample1.txt sample2.txt sample3.txt\r\n\r\n\r\n------------------------------------------------------------------------------\r\n[inserting file position]\r\n\r\nIf you do not specify line number,\r\nthe contents of selected files are inserted into cursor line.\r\n\r\n\" contents are inserted into cursor line.\r\n:RArgs sample1.txt sample2.txt sample3.txt\r\n\r\n\" contents are inserted into specified line.\r\n:200RArgs sample1.txt sample2.txt sample3.txt\r\n\r\n\" contents are inserted into first line of buffer.\r\n:0RArgs sample1.txt sample2.txt sample3.txt\r\n\r\n\r\n------------------------------------------------------------------------------\r\n[Configuration]\r\n\r\n'g:rargs_exit_when_error'\r\n\r\nIf you set 1 to 'g:rargs_exit_when_error',\r\nexit when error is found. Default aciion is error is ignored.\r\n\r\nlet g:rargs_exit_when_error = '1'\r\n\r\n","install_details":"copy rargs.vim into your plugin directory.\r\n","5":"copy rargs.vim into your plugin directory.\r\n","first_name":"omi","6":"omi","last_name":"taku","7":"taku","releases":[{"0":"2789","vim_version":"7.0","1":"7.0","script_version":"0.2","2":"0.2","version_comment":"add exception handling logic.\r\n++opt parameter is supported.\r\noption 'g:rargs_exit_when_error' is supported.\r\n\r\n","3":"add exception handling logic.\r\n++opt parameter is supported.\r\noption 'g:rargs_exit_when_error' is supported.\r\n\r\n","package":"rargs.vim","4":"rargs.vim","src_id":"11397","5":"11397","creation_date":"1253207120","6":"1253207120"},{"0":"2789","vim_version":"7.2","1":"7.2","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"rargs.vim","4":"rargs.vim","src_id":"11391","5":"11391","creation_date":"1253121442","6":"1253121442"}]},"2788":{"script_id":"2788","0":"2788","script_name":"InsertList","1":"InsertList","script_type":"utility","2":"utility","summary":"Insert number-list.","3":"Insert number-list.","description":"Function:\r\n ------------\r\n This plugin inserts input-string before select position, and increments last-number.\r\n\r\nUsage:\r\n ------------\r\n Execute vim script in selected area (with Visual Mode).\r\n Plugin will be used for create following number-list.\r\n\r\nnumber-list\r\n--------------------------\r\n1.\r\n     1.1.\r\n         1.1.1.\r\n         1.1.2.\r\n         1.1.3.\r\n         1.1.4.\r\n     1.2.\r\n     1.3.\r\n     1.4.\r\n     1.5.\r\n     1.6.\r\n2.\r\n     2.1.\r\n     2.2.\r\n     2.3.\r\n     2.4.\r\n--------------------------\r\n\r\n------------------------------------------------------------------------------\r\n[command format]\r\n:'<,'>INSERTLIST numberlist\r\n   or \r\n:'<,'>InsertList numberlist\r\n\r\nex1: \r\n========================================\r\nbefore text\r\n------------\r\n\r\n\r\n------------\r\n\r\n(1) Please use \"Visual mode blockwise\", and select following text area.\r\n------------\r\n|\r\n|\r\n------------\r\n\r\n(2) Input following command.\r\n:'<,'>INSERTLIST 1.\r\n\r\nafter text\r\n------------\r\n1.\r\n2.\r\n------------\r\n========================================\r\nex2: \r\nbefore text\r\n------------\r\naaa \r\nbbb \r\n------------\r\n\r\n(1) Please use \"Visual mode blockwise\", and select following text area.\r\n------------\r\naaa|\r\nbbb|\r\n------------\r\n\r\n(2) Input following command.\r\n:'<,'>INSERTLIST 1.\r\n\r\nafter text\r\n------------\r\naaa1.\r\nbbb2.\r\n------------\r\n========================================\r\nex3:\r\n\r\nbefore text\r\n------------\r\n\r\n\r\n------------\r\n\r\n(1) Please use \"Visual mode blockwise\", and select following text area.\r\n------------\r\n|\r\n|\r\n------------\r\n\r\n(2) Input following command.\r\n:'<,'>INSERTLIST strName[0] = \r\n\r\nafter text\r\n------------\r\nstrName[0] = \r\nstrName[1] = \r\n------------\r\n========================================\r\nex4:\r\n\r\nbefore text\r\n------------\r\n\r\n\r\n------------\r\n\r\n(1) Set following option.\r\n:set virtualedit=all\r\n\r\n(2) Please use \"Visual mode blockwise\", and select following text area.\r\n------------\r\n    |\r\n    |\r\n------------\r\n\r\n(3) Input following command.\r\n:'<,'>INSERTLIST 1.\r\n\r\nafter text\r\n------------\r\n    1.\r\n    2.\r\n------------\r\n========================================\r\nex5: Other input-string format pattern.\r\n\r\n(1) 1.1 to 1.N\r\n(2) 1-1 to 1-N\r\n(3) <1> to <N>\r\n(4) 001 to 00N\r\n","4":"Function:\r\n ------------\r\n This plugin inserts input-string before select position, and increments last-number.\r\n\r\nUsage:\r\n ------------\r\n Execute vim script in selected area (with Visual Mode).\r\n Plugin will be used for create following number-list.\r\n\r\nnumber-list\r\n--------------------------\r\n1.\r\n     1.1.\r\n         1.1.1.\r\n         1.1.2.\r\n         1.1.3.\r\n         1.1.4.\r\n     1.2.\r\n     1.3.\r\n     1.4.\r\n     1.5.\r\n     1.6.\r\n2.\r\n     2.1.\r\n     2.2.\r\n     2.3.\r\n     2.4.\r\n--------------------------\r\n\r\n------------------------------------------------------------------------------\r\n[command format]\r\n:'<,'>INSERTLIST numberlist\r\n   or \r\n:'<,'>InsertList numberlist\r\n\r\nex1: \r\n========================================\r\nbefore text\r\n------------\r\n\r\n\r\n------------\r\n\r\n(1) Please use \"Visual mode blockwise\", and select following text area.\r\n------------\r\n|\r\n|\r\n------------\r\n\r\n(2) Input following command.\r\n:'<,'>INSERTLIST 1.\r\n\r\nafter text\r\n------------\r\n1.\r\n2.\r\n------------\r\n========================================\r\nex2: \r\nbefore text\r\n------------\r\naaa \r\nbbb \r\n------------\r\n\r\n(1) Please use \"Visual mode blockwise\", and select following text area.\r\n------------\r\naaa|\r\nbbb|\r\n------------\r\n\r\n(2) Input following command.\r\n:'<,'>INSERTLIST 1.\r\n\r\nafter text\r\n------------\r\naaa1.\r\nbbb2.\r\n------------\r\n========================================\r\nex3:\r\n\r\nbefore text\r\n------------\r\n\r\n\r\n------------\r\n\r\n(1) Please use \"Visual mode blockwise\", and select following text area.\r\n------------\r\n|\r\n|\r\n------------\r\n\r\n(2) Input following command.\r\n:'<,'>INSERTLIST strName[0] = \r\n\r\nafter text\r\n------------\r\nstrName[0] = \r\nstrName[1] = \r\n------------\r\n========================================\r\nex4:\r\n\r\nbefore text\r\n------------\r\n\r\n\r\n------------\r\n\r\n(1) Set following option.\r\n:set virtualedit=all\r\n\r\n(2) Please use \"Visual mode blockwise\", and select following text area.\r\n------------\r\n    |\r\n    |\r\n------------\r\n\r\n(3) Input following command.\r\n:'<,'>INSERTLIST 1.\r\n\r\nafter text\r\n------------\r\n    1.\r\n    2.\r\n------------\r\n========================================\r\nex5: Other input-string format pattern.\r\n\r\n(1) 1.1 to 1.N\r\n(2) 1-1 to 1-N\r\n(3) <1> to <N>\r\n(4) 001 to 00N\r\n","install_details":" 1. Copy the InsertList.vim file to one of the following directories:\r\n       $HOME\/.vim\/plugin     - Unix like systems\r\n       $HOME\/vimfiles\/plugin - MS-Windows\r\n       $VIM:vimfiles:plugin  - Macintosh\r\n       $VIM\/vimfiles\/plugin  - All\r\n","5":" 1. Copy the InsertList.vim file to one of the following directories:\r\n       $HOME\/.vim\/plugin     - Unix like systems\r\n       $HOME\/vimfiles\/plugin - MS-Windows\r\n       $VIM:vimfiles:plugin  - Macintosh\r\n       $VIM\/vimfiles\/plugin  - All\r\n","first_name":"Shingo","6":"Shingo","last_name":"Sato","7":"Sato","releases":[{"0":"2788","vim_version":"7.0","1":"7.0","script_version":"1.1","2":"1.1","version_comment":"I modify following problem.\r\n\r\n(1) If you install the YankRing.vim, insertlist.vim update Yank history.","3":"I modify following problem.\r\n\r\n(1) If you install the YankRing.vim, insertlist.vim update Yank history.","package":"InsertList.vim","4":"InsertList.vim","src_id":"11388","5":"11388","creation_date":"1253106139","6":"1253106139"}]},"2787":{"script_id":"2787","0":"2787","script_name":"Melt Vim","1":"Melt Vim","script_type":"syntax","2":"syntax","summary":"Plugin for Melt files","3":"Plugin for Melt files","description":"Plugin for Melt (http:\/\/melt.forge.ocamlcore.org\/) files: \r\n- syntax colouring (with handling of spelling) \r\n- filetype detection \r\n- filetype plugin \r\n- compiler plugin \r\n\r\nFeatures: \r\n* automatic detection of .mlt files \r\n* syntax coloration \r\n* compiler error handling (i.e. go to the location of the error indicated by Melt - warning: approximative) \r\n* handling of spelling, english is the default, see :h spell for more details \r\n* and the following commands: \r\n\r\n+ normal mode: \r\n - gf on a module name will open the corresponding file \r\n\r\n+ visual mode (xxx denotes the selected text, xxx -> ... means \"xxx is rewritten as ...\"): \r\n - <LocalLeader>\": xxx -> \"xxx\" (i.e. inserts quotes around xxx) \r\n - <LocalLeader>(: xxx -> (xxx) \r\n - <LocalLeader>{: xxx -> {xxx} \r\n - <LocalLeader>[: xxx -> [xxx] \r\n - <LocalLeader>cc: xxx -> (*xxx*) \r\n - <LocalLeader>e: xxx -> {emph \"xxx\"} \r\n - <LocalLeader><LocalLeader>: ask for a string s (typically a caml function), then xxx -> {s \"xxx\"} \r\nNote: <LocalLeader> is generally bound to ',' \r\n\r\n+ if the matchit plugin (http:\/\/www.vim.org\/scripts\/script.php?script_id=39) is installed then '%' will switch between struct\/end, let\/in, match\/with, ... \r\n\r\n+ if the Nerd commenter plugin (http:\/\/www.vim.org\/scripts\/script.php?script_id=1218) is installed then its usual commands handle melt comments \r\n\r\n+ if you set the variable g:MeltCloseDelimiters then: \r\n - typing \" will write \"\" and put the cursor between the quotes \r\n - typing ( will write () and put the cursor between the parentheses \r\n - typing { will write {} and put the cursor between the braces \r\n - typing [ will write [] and put the cursor between the brackets \r\n\r\n+ main rule to detect the compiler for :make (see compiler\/melt.vim for details): \r\n1. if there is a Makefile then :make launches make \r\n2. if there is a myocamlbuild.ml then :make launches ocamlbuild \r\n3. otherwise launch melt \r\n","4":"Plugin for Melt (http:\/\/melt.forge.ocamlcore.org\/) files: \r\n- syntax colouring (with handling of spelling) \r\n- filetype detection \r\n- filetype plugin \r\n- compiler plugin \r\n\r\nFeatures: \r\n* automatic detection of .mlt files \r\n* syntax coloration \r\n* compiler error handling (i.e. go to the location of the error indicated by Melt - warning: approximative) \r\n* handling of spelling, english is the default, see :h spell for more details \r\n* and the following commands: \r\n\r\n+ normal mode: \r\n - gf on a module name will open the corresponding file \r\n\r\n+ visual mode (xxx denotes the selected text, xxx -> ... means \"xxx is rewritten as ...\"): \r\n - <LocalLeader>\": xxx -> \"xxx\" (i.e. inserts quotes around xxx) \r\n - <LocalLeader>(: xxx -> (xxx) \r\n - <LocalLeader>{: xxx -> {xxx} \r\n - <LocalLeader>[: xxx -> [xxx] \r\n - <LocalLeader>cc: xxx -> (*xxx*) \r\n - <LocalLeader>e: xxx -> {emph \"xxx\"} \r\n - <LocalLeader><LocalLeader>: ask for a string s (typically a caml function), then xxx -> {s \"xxx\"} \r\nNote: <LocalLeader> is generally bound to ',' \r\n\r\n+ if the matchit plugin (http:\/\/www.vim.org\/scripts\/script.php?script_id=39) is installed then '%' will switch between struct\/end, let\/in, match\/with, ... \r\n\r\n+ if the Nerd commenter plugin (http:\/\/www.vim.org\/scripts\/script.php?script_id=1218) is installed then its usual commands handle melt comments \r\n\r\n+ if you set the variable g:MeltCloseDelimiters then: \r\n - typing \" will write \"\" and put the cursor between the quotes \r\n - typing ( will write () and put the cursor between the parentheses \r\n - typing { will write {} and put the cursor between the braces \r\n - typing [ will write [] and put the cursor between the brackets \r\n\r\n+ main rule to detect the compiler for :make (see compiler\/melt.vim for details): \r\n1. if there is a Makefile then :make launches make \r\n2. if there is a myocamlbuild.ml then :make launches ocamlbuild \r\n3. otherwise launch melt \r\n","install_details":"1. untar the archive meltvim.tar.gz \r\n2. cp -r meltvim-xxx\/* $HOME\/.vim\/ \r\n\r\nThe archive contains ftdetect\/melt.vim, ftplugin\/melt.vim, compiler\/melt.vim and syntax\/melt.vim.\r\n ","5":"1. untar the archive meltvim.tar.gz \r\n2. cp -r meltvim-xxx\/* $HOME\/.vim\/ \r\n\r\nThe archive contains ftdetect\/melt.vim, ftplugin\/melt.vim, compiler\/melt.vim and syntax\/melt.vim.\r\n ","first_name":"Vincent","6":"Vincent","last_name":"Aravantinos","7":"Aravantinos","releases":[{"0":"2787","vim_version":"6.0","1":"6.0","script_version":"0.2","2":"0.2","version_comment":"- added handling of *spelling*\r\n- added the filetype plugin with various commands\r\n- better syntax coloration\r\n- now goes to the location of an error\r\n","3":"- added handling of *spelling*\r\n- added the filetype plugin with various commands\r\n- better syntax coloration\r\n- now goes to the location of an error\r\n","package":"meltvim-0.2.tar.gz","4":"meltvim-0.2.tar.gz","src_id":"12840","5":"12840","creation_date":"1271372525","6":"1271372525"},{"0":"2787","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"meltsyntax-0.1.tar.gz","4":"meltsyntax-0.1.tar.gz","src_id":"11374","5":"11374","creation_date":"1252928414","6":"1252928414"}]},"2786":{"script_id":"2786","0":"2786","script_name":"cpan.vim","1":"cpan.vim","script_type":"utility","2":"utility","summary":"cpan module helper","3":"cpan module helper","description":"please see:\r\nhttp:\/\/github.com\/c9s\/cpan.vim","4":"please see:\r\nhttp:\/\/github.com\/c9s\/cpan.vim","install_details":"run make:\r\n\r\n$ make install","5":"run make:\r\n\r\n$ make install","first_name":"Yo-An","6":"Yo-An","last_name":"Lin","7":"Lin","releases":[{"0":"2786","vim_version":"7.0","1":"7.0","script_version":"3.0","2":"3.0","version_comment":"repack.","3":"repack.","package":"cpan.vim-3.0.tar.gz","4":"cpan.vim-3.0.tar.gz","src_id":"12688","5":"12688","creation_date":"1269364756","6":"1269364756"},{"0":"2786","vim_version":"7.0","1":"7.0","script_version":"2.3","2":"2.3","version_comment":"use new makefile.","3":"use new makefile.","package":"cpan.vim.tar.gz","4":"cpan.vim.tar.gz","src_id":"12668","5":"12668","creation_date":"1269110456","6":"1269110456"},{"0":"2786","vim_version":"7.0","1":"7.0","script_version":"2.2","2":"2.2","version_comment":"new release\n(This package is released by VIM::Packager http:\/\/github.com\/c9s\/vim-packager)\n","3":"new release\n(This package is released by VIM::Packager http:\/\/github.com\/c9s\/vim-packager)\n","package":"cpan-vim-2.2.tar.gz","4":"cpan-vim-2.2.tar.gz","src_id":"11872","5":"11872","creation_date":"1260042171","6":"1260042171"},{"0":"2786","vim_version":"7.0","1":"7.0","script_version":"1.3","2":"1.3","version_comment":"libperl updates.\n","3":"libperl updates.\n","package":"cpan-vim-1.3.tar.gz","4":"cpan-vim-1.3.tar.gz","src_id":"11756","5":"11756","creation_date":"1258572060","6":"1258572060"},{"0":"2786","vim_version":"7.0","1":"7.0","script_version":"1.1","2":"1.1","version_comment":"new release\n","3":"new release\n","package":"cpan-vim-1.1.tar.gz","4":"cpan-vim-1.1.tar.gz","src_id":"11749","5":"11749","creation_date":"1258478060","6":"1258478060"},{"0":"2786","vim_version":"7.0","1":"7.0","script_version":"2.0","2":"2.0","version_comment":"add function reference search feature , more completions , please checkout README file","3":"add function reference search feature , more completions , please checkout README file","package":"cpan.vim.tar.gz","4":"cpan.vim.tar.gz","src_id":"11466","5":"11466","creation_date":"1254422750","6":"1254422750"}]},"2785":{"script_id":"2785","0":"2785","script_name":"wwwsearch","1":"wwwsearch","script_type":"utility","2":"utility","summary":"Search WWW easily from Vim","3":"Search WWW easily from Vim","description":"*wwwsearch* is a Vim plugin to provide various ways to search the World Wide\r\nWeb with various web search engines.  For example,\r\n\r\n\t:Wwwsearch vim\r\n\r\nthe above command activates your favorite Web browser then searches WWW for\r\na keyword \"vim\" with a search engine (by default, Google).  You can also\r\nspecify which search engine to use as follows:\r\n\r\n\t:Wwwsearch -google vim\r\n\r\nSee also |wwwsearch-interface|, |wwwsearch-customizing| and\r\n|wwwsearch-examples| for more details.\r\n\r\n\r\nRequirements:\r\n- Vim 7.2 or later\r\n\r\nOptionals:\r\n- |operator-user| (vimscript#2692)\r\n\r\nLatest version:\r\nhttp:\/\/github.com\/kana\/vim-wwwsearch\r\n\r\nDocument in HTML format:\r\nhttp:\/\/kana.github.com\/config\/vim\/wwwsearch.html","4":"*wwwsearch* is a Vim plugin to provide various ways to search the World Wide\r\nWeb with various web search engines.  For example,\r\n\r\n\t:Wwwsearch vim\r\n\r\nthe above command activates your favorite Web browser then searches WWW for\r\na keyword \"vim\" with a search engine (by default, Google).  You can also\r\nspecify which search engine to use as follows:\r\n\r\n\t:Wwwsearch -google vim\r\n\r\nSee also |wwwsearch-interface|, |wwwsearch-customizing| and\r\n|wwwsearch-examples| for more details.\r\n\r\n\r\nRequirements:\r\n- Vim 7.2 or later\r\n\r\nOptionals:\r\n- |operator-user| (vimscript#2692)\r\n\r\nLatest version:\r\nhttp:\/\/github.com\/kana\/vim-wwwsearch\r\n\r\nDocument in HTML format:\r\nhttp:\/\/kana.github.com\/config\/vim\/wwwsearch.html","install_details":"...","5":"...","first_name":"Kana","6":"Kana","last_name":"Natsuno","7":"Natsuno","releases":[{"0":"2785","vim_version":"7.0","1":"7.0","script_version":"0.0.1","2":"0.0.1","version_comment":"- Fix the default value of |g:wwwsearch_command_to_open_uri| for Microsoft Windows.  The old value doesn't work.  (Thanks to id:ampmmn and id:ursm for reporting).","3":"- Fix the default value of |g:wwwsearch_command_to_open_uri| for Microsoft Windows.  The old value doesn't work.  (Thanks to id:ampmmn and id:ursm for reporting).","package":"vim-wwwsearch-0.0.1.zip","4":"vim-wwwsearch-0.0.1.zip","src_id":"11378","5":"11378","creation_date":"1253011327","6":"1253011327"},{"0":"2785","vim_version":"7.0","1":"7.0","script_version":"0.0.0","2":"0.0.0","version_comment":"Initial upload","3":"Initial upload","package":"vim-wwwsearch-0.0.0.zip","4":"vim-wwwsearch-0.0.0.zip","src_id":"11361","5":"11361","creation_date":"1252814556","6":"1252814556"}]},"2784":{"script_id":"2784","0":"2784","script_name":"template-init.vim","1":"template-init.vim","script_type":"utility","2":"utility","summary":"provide more flexiable template","3":"provide more flexiable template","description":"template-init.vim let you to leave place holders in your template , then you can press <tab> key to jump to next placeholder (in insert mode)\r\n\r\nthe placeholder could be in vimscript , so that you can generate content by vim function or vim command , even in perl or ruby.\r\n\r\nlet g:skeleton_path = expand('~\/.vim\/skeleton')\r\nlet g:skeleton_placeholder_key = '<Tab>'\r\n\r\n to setup template:\r\n   au BufNewFile *.t   :call InitTemplate('template.t')\r\n   au BufNewFile *.pl  :call InitTemplate('')\r\n\r\n to setup placeholder:\r\n   {{!perl:  print q|test|}}\r\n   {{!vim: expand('%')}}\r\n   {{:normal ggyp}}\r\n   {{place holder}}\r\n\r\ngithub:  http:\/\/github.com\/c9s\/template-init.vim\r\n","4":"template-init.vim let you to leave place holders in your template , then you can press <tab> key to jump to next placeholder (in insert mode)\r\n\r\nthe placeholder could be in vimscript , so that you can generate content by vim function or vim command , even in perl or ruby.\r\n\r\nlet g:skeleton_path = expand('~\/.vim\/skeleton')\r\nlet g:skeleton_placeholder_key = '<Tab>'\r\n\r\n to setup template:\r\n   au BufNewFile *.t   :call InitTemplate('template.t')\r\n   au BufNewFile *.pl  :call InitTemplate('')\r\n\r\n to setup placeholder:\r\n   {{!perl:  print q|test|}}\r\n   {{!vim: expand('%')}}\r\n   {{:normal ggyp}}\r\n   {{place holder}}\r\n\r\ngithub:  http:\/\/github.com\/c9s\/template-init.vim\r\n","install_details":"$ make install ","5":"$ make install ","first_name":"Yo-An","6":"Yo-An","last_name":"Lin","7":"Lin","releases":[{"0":"2784","vim_version":"7.0","1":"7.0","script_version":"1.1","2":"1.1","version_comment":"new version vim plugin","3":"new version vim plugin","package":"template-init.tar.gz","4":"template-init.tar.gz","src_id":"11370","5":"11370","creation_date":"1252850873","6":"1252850873"},{"0":"2784","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"template-init.tar.gz","4":"template-init.tar.gz","src_id":"11360","5":"11360","creation_date":"1252775824","6":"1252775824"}]},"2783":{"script_id":"2783","0":"2783","script_name":"DumbBuf","1":"DumbBuf","script_type":"utility","2":"utility","summary":"simple buffer manager like QuickBuf.vim","3":"simple buffer manager like QuickBuf.vim","description":"latest version at http:\/\/github.com\/tyru\/DumbBuf.vim\/\r\nincluding missing versions, all versions are mirrored at http:\/\/github.com\/tyru\/DumbBuf.vim\/downloads\r\nJapanese description is here: http:\/\/vim.g.hatena.ne.jp\/tyru\/20091030\r\nscreenshot is here: http:\/\/f.hatena.ne.jp\/tyru\/20091031002751\r\n\r\n\r\nMy .vimrc:\r\n  let dumbbuf_hotkey = '<Leader>b'\r\n  \" sometimes I put <Esc> to close dumbbuf buffer,\r\n  \" which was mapped to close QuickBuf's list :)\r\n  let dumbbuf_mappings = {\r\n      \\'n': {\r\n          \\'<Esc>': {'alias_to': 'q'},\r\n      \\}\r\n  \\}\r\n\r\n  let dumbbuf_wrap_cursor = 0\r\n  let dumbbuf_remove_marked_when_close = 1\r\n\r\n\r\nMappings:\r\n  please define g:dumbbuf_hotkey at first.\r\n  if that is not defined, this script is not loaded.\r\n\r\n  Visual Mode:\r\n      x\r\n          mark buffers on selected region.\r\n          see Normal Mode's xx for details.\r\n\r\n  Normal Mode:\r\n      q\r\n          :close dumbbuf buffer.\r\n      g:dumbbuf_hotkey\r\n          toggle dumbbuf buffer.\r\n      <CR>\r\n          :edit buffer.\r\n      u\r\n         open one by one. this is same as QuickBuf's u.\r\n      s\r\n         :split buffer.\r\n      v\r\n         :vspilt buffer.\r\n      t\r\n         :tabedit buffer.\r\n      d\r\n         :bdelete buffer.\r\n      w\r\n         :bwipeout buffer.\r\n      l\r\n         toggle listed buffers or unlisted buffers.\r\n      c\r\n         :close buffer.\r\n      x\r\n          mark buffer.\r\n          if one or more marked buffers exist,\r\n          's', 'v', 't', 'd', 'w', 'c'\r\n          get to be able to execute for that buffers at a time.\r\n\r\n  and, if you turn on 'g:dumbbuf_single_key',\r\n  you can use single key mappings like QuickBuf.vim.\r\n  see 'g:dumbbuf_single_key' at 'Global Variables' for details.\r\n\r\n\r\nGlobal Variables:\r\n  g:dumbbuf_hotkey (default: no default value)\r\n      a mapping which calls dumbbuf buffer.\r\n      if this variable is not defined, this plugin will be not loaded.\r\n\r\n  g:dumbbuf_open_with (default: 'botright')\r\n      open dumbbuf buffer with this command.\r\n\r\n  g:dumbbuf_vertical (default: 0)\r\n      if true, open dumbbuf buffer vertically.\r\n\r\n  g:dumbbuf_buffer_height (default: 10)\r\n      dumbbuf buffer's height.\r\n      this is used when only g:dumbbuf_vertical is false.\r\n\r\n  g:dumbbuf_buffer_width (default: 25)\r\n      dumbbuf buffer's width.\r\n      this is used when only g:dumbbuf_vertical is true.\r\n\r\n  g:dumbbuf_listed_buffer_name (default: '__buffers__')\r\n      dumbbuf buffer's filename.\r\n      set this filename when showing 'listed buffers'.\r\n      'listed buffers' are opposite of 'unlisted-buffers'.\r\n      see ':help unlisted-buffer'.\r\n\r\n      NOTE: DON'T assign string which includes whitespace, or any special\r\n      characters like \"*\", \"?\", \",\".\r\n      see :help file-pattern\r\n\r\n  g:dumbbuf_unlisted_buffer_name (default: '__unlisted_buffers__')\r\n      dumbbuf buffer's filename.\r\n      set this filename when showing 'unlisted buffers'.\r\n\r\n      NOTE: DON'T assign string which includes whitespace, or any special\r\n      characters like \"*\", \"?\", \",\".\r\n      see :help file-pattern\r\n\r\n  g:dumbbuf_cursor_pos (default: 'current')\r\n      jumps to this position when dumbbuf buffer opens.\r\n      this is useful for deleting some buffers continuaslly.\r\n\r\n      'current':\r\n          jump to the current buffer's line.\r\n      'keep':\r\n          keep the cursor pos.\r\n      'top':\r\n          always jump to the top line.\r\n      'bottom':\r\n          always jump to the bottom line\r\n\r\n  g:dumbbuf_shown_type (default: '')\r\n      show this type of buffers list.\r\n\r\n      '':\r\n          if current buffer is unlisted, show unlisted buffers list.\r\n          if current buffer is listed, show listed buffers list.\r\n      'unlisted':\r\n          show always unlisted buffers list.\r\n      'listed':\r\n          show always listed buffers list.\r\n      'project':\r\n          show buffers each project.\r\n\r\n  g:dumbbuf_close_when_exec (default: 0)\r\n      if true, close when execute local mapping from dumbbuf buffer.\r\n\r\n  g:dumbbuf_remove_marked_when_close (default: 0)\r\n      remove all marked buffers on closing dumbbuf buffer.\r\n      this default value is for only backward compatibility.\r\n      (if I could fix this variable name...\r\n       'dumbbuf_close_when_exec' => 'dumbbuf_close_on_exec')\r\n\r\n  g:dumbbuf_downward (default: 1)\r\n      if true, go downwardly when 'u' mapping.\r\n      if false, go upwardly.\r\n\r\n  g:dumbbuf_hl_cursorline (default: \"guibg=Red  guifg=White\")\r\n      local value of highlight 'CursorLine' in dumbbuf buffer.\r\n\r\n  g:dumbbuf_wrap_cursor (default: 1)\r\n      wrap the cursor at the top or bottom of dumbbuf buffer.\r\n\r\n  g:dumbbuf_all_shown_types (default: ['listed', 'unlisted', 'project'])\r\n      all available shown types.\r\n\r\n  g:dumbbuf_timeoutlen (default: 0)\r\n      local value of &timeoutlen in dumbbuf buffer.\r\n\r\n\r\n  For The Experienced User:\r\n      g:dumbbuf_disp_expr (default: see the definition)\r\n          this variable is for the experienced users.\r\n\r\n          'v:val' has buffer's info.\r\n          NOTE: 'val' does NOT work now.\r\n\r\n      g:dumbbuf_options (default: see the definition)\r\n          this variable is for the experienced users.\r\n          dumbbuf buffer will be set up with these options.\r\n\r\n      g:dumbbuf_mappings (default: see the definition)\r\n          this variable is for the experienced users.\r\n          these settings will override default value.\r\n\r\n          if your .vimrc setting is\r\n\r\n            let g:dumbbuf_mappings = {\r\n                \\'n': {\r\n                    \\'<Esc>': {'alias_to': 'q'}\r\n                \\}\r\n            \\}\r\n\r\n          you can type <Esc> to close dumbbuf buffer.\r\n          no influences for other default mappings.\r\n\r\n          and there are some special keys:\r\n              'alias_to': 'map'\r\n                  make an alias for 'map'.\r\n              'swap_with': 'map'\r\n","4":"latest version at http:\/\/github.com\/tyru\/DumbBuf.vim\/\r\nincluding missing versions, all versions are mirrored at http:\/\/github.com\/tyru\/DumbBuf.vim\/downloads\r\nJapanese description is here: http:\/\/vim.g.hatena.ne.jp\/tyru\/20091030\r\nscreenshot is here: http:\/\/f.hatena.ne.jp\/tyru\/20091031002751\r\n\r\n\r\nMy .vimrc:\r\n  let dumbbuf_hotkey = '<Leader>b'\r\n  \" sometimes I put <Esc> to close dumbbuf buffer,\r\n  \" which was mapped to close QuickBuf's list :)\r\n  let dumbbuf_mappings = {\r\n      \\'n': {\r\n          \\'<Esc>': {'alias_to': 'q'},\r\n      \\}\r\n  \\}\r\n\r\n  let dumbbuf_wrap_cursor = 0\r\n  let dumbbuf_remove_marked_when_close = 1\r\n\r\n\r\nMappings:\r\n  please define g:dumbbuf_hotkey at first.\r\n  if that is not defined, this script is not loaded.\r\n\r\n  Visual Mode:\r\n      x\r\n          mark buffers on selected region.\r\n          see Normal Mode's xx for details.\r\n\r\n  Normal Mode:\r\n      q\r\n          :close dumbbuf buffer.\r\n      g:dumbbuf_hotkey\r\n          toggle dumbbuf buffer.\r\n      <CR>\r\n          :edit buffer.\r\n      u\r\n         open one by one. this is same as QuickBuf's u.\r\n      s\r\n         :split buffer.\r\n      v\r\n         :vspilt buffer.\r\n      t\r\n         :tabedit buffer.\r\n      d\r\n         :bdelete buffer.\r\n      w\r\n         :bwipeout buffer.\r\n      l\r\n         toggle listed buffers or unlisted buffers.\r\n      c\r\n         :close buffer.\r\n      x\r\n          mark buffer.\r\n          if one or more marked buffers exist,\r\n          's', 'v', 't', 'd', 'w', 'c'\r\n          get to be able to execute for that buffers at a time.\r\n\r\n  and, if you turn on 'g:dumbbuf_single_key',\r\n  you can use single key mappings like QuickBuf.vim.\r\n  see 'g:dumbbuf_single_key' at 'Global Variables' for details.\r\n\r\n\r\nGlobal Variables:\r\n  g:dumbbuf_hotkey (default: no default value)\r\n      a mapping which calls dumbbuf buffer.\r\n      if this variable is not defined, this plugin will be not loaded.\r\n\r\n  g:dumbbuf_open_with (default: 'botright')\r\n      open dumbbuf buffer with this command.\r\n\r\n  g:dumbbuf_vertical (default: 0)\r\n      if true, open dumbbuf buffer vertically.\r\n\r\n  g:dumbbuf_buffer_height (default: 10)\r\n      dumbbuf buffer's height.\r\n      this is used when only g:dumbbuf_vertical is false.\r\n\r\n  g:dumbbuf_buffer_width (default: 25)\r\n      dumbbuf buffer's width.\r\n      this is used when only g:dumbbuf_vertical is true.\r\n\r\n  g:dumbbuf_listed_buffer_name (default: '__buffers__')\r\n      dumbbuf buffer's filename.\r\n      set this filename when showing 'listed buffers'.\r\n      'listed buffers' are opposite of 'unlisted-buffers'.\r\n      see ':help unlisted-buffer'.\r\n\r\n      NOTE: DON'T assign string which includes whitespace, or any special\r\n      characters like \"*\", \"?\", \",\".\r\n      see :help file-pattern\r\n\r\n  g:dumbbuf_unlisted_buffer_name (default: '__unlisted_buffers__')\r\n      dumbbuf buffer's filename.\r\n      set this filename when showing 'unlisted buffers'.\r\n\r\n      NOTE: DON'T assign string which includes whitespace, or any special\r\n      characters like \"*\", \"?\", \",\".\r\n      see :help file-pattern\r\n\r\n  g:dumbbuf_cursor_pos (default: 'current')\r\n      jumps to this position when dumbbuf buffer opens.\r\n      this is useful for deleting some buffers continuaslly.\r\n\r\n      'current':\r\n          jump to the current buffer's line.\r\n      'keep':\r\n          keep the cursor pos.\r\n      'top':\r\n          always jump to the top line.\r\n      'bottom':\r\n          always jump to the bottom line\r\n\r\n  g:dumbbuf_shown_type (default: '')\r\n      show this type of buffers list.\r\n\r\n      '':\r\n          if current buffer is unlisted, show unlisted buffers list.\r\n          if current buffer is listed, show listed buffers list.\r\n      'unlisted':\r\n          show always unlisted buffers list.\r\n      'listed':\r\n          show always listed buffers list.\r\n      'project':\r\n          show buffers each project.\r\n\r\n  g:dumbbuf_close_when_exec (default: 0)\r\n      if true, close when execute local mapping from dumbbuf buffer.\r\n\r\n  g:dumbbuf_remove_marked_when_close (default: 0)\r\n      remove all marked buffers on closing dumbbuf buffer.\r\n      this default value is for only backward compatibility.\r\n      (if I could fix this variable name...\r\n       'dumbbuf_close_when_exec' => 'dumbbuf_close_on_exec')\r\n\r\n  g:dumbbuf_downward (default: 1)\r\n      if true, go downwardly when 'u' mapping.\r\n      if false, go upwardly.\r\n\r\n  g:dumbbuf_hl_cursorline (default: \"guibg=Red  guifg=White\")\r\n      local value of highlight 'CursorLine' in dumbbuf buffer.\r\n\r\n  g:dumbbuf_wrap_cursor (default: 1)\r\n      wrap the cursor at the top or bottom of dumbbuf buffer.\r\n\r\n  g:dumbbuf_all_shown_types (default: ['listed', 'unlisted', 'project'])\r\n      all available shown types.\r\n\r\n  g:dumbbuf_timeoutlen (default: 0)\r\n      local value of &timeoutlen in dumbbuf buffer.\r\n\r\n\r\n  For The Experienced User:\r\n      g:dumbbuf_disp_expr (default: see the definition)\r\n          this variable is for the experienced users.\r\n\r\n          'v:val' has buffer's info.\r\n          NOTE: 'val' does NOT work now.\r\n\r\n      g:dumbbuf_options (default: see the definition)\r\n          this variable is for the experienced users.\r\n          dumbbuf buffer will be set up with these options.\r\n\r\n      g:dumbbuf_mappings (default: see the definition)\r\n          this variable is for the experienced users.\r\n          these settings will override default value.\r\n\r\n          if your .vimrc setting is\r\n\r\n            let g:dumbbuf_mappings = {\r\n                \\'n': {\r\n                    \\'<Esc>': {'alias_to': 'q'}\r\n                \\}\r\n            \\}\r\n\r\n          you can type <Esc> to close dumbbuf buffer.\r\n          no influences for other default mappings.\r\n\r\n          and there are some special keys:\r\n              'alias_to': 'map'\r\n                  make an alias for 'map'.\r\n              'swap_with': 'map'\r\n","install_details":"move to your plugin's directory(~\/.vim\/plugin\/).\r\nwrite g:dumbbuf_hotkey setting to your .vimrc like below:\r\n  let g:dumbbuf_hotkey = '<Leader>b'","5":"move to your plugin's directory(~\/.vim\/plugin\/).\r\nwrite g:dumbbuf_hotkey setting to your .vimrc like below:\r\n  let g:dumbbuf_hotkey = '<Leader>b'","first_name":"tyru","6":"tyru","last_name":" ","7":" ","releases":[{"0":"2783","vim_version":"7.0","1":"7.0","script_version":"0.0.9","2":"0.0.9","version_comment":"- Add 'o' mapping to execute ':sbuffer'. Thanks to Jan Christoph.\r\n- Fix bug to fail to restore original CursorLine highlight.\r\n- Change default value of g:dumbbuf_options\r\n- Allow to execute mappings even on noname buffer.\r\n- Add '<Plug>(dumbbuf-open)'.\r\n  g:dumbbuf_hotkey is not '',\r\n  g:dumbbuf_hotkey is mapped to '<Plug>(dumbbuf-open)'.\r\n- Write document\r\n- etc.","3":"- Add 'o' mapping to execute ':sbuffer'. Thanks to Jan Christoph.\r\n- Fix bug to fail to restore original CursorLine highlight.\r\n- Change default value of g:dumbbuf_options\r\n- Allow to execute mappings even on noname buffer.\r\n- Add '<Plug>(dumbbuf-open)'.\r\n  g:dumbbuf_hotkey is not '',\r\n  g:dumbbuf_hotkey is mapped to '<Plug>(dumbbuf-open)'.\r\n- Write document\r\n- etc.","package":"dumbbuf.zip","4":"dumbbuf.zip","src_id":"12534","5":"12534","creation_date":"1267509317","6":"1267509317"},{"0":"2783","vim_version":"7.0","1":"7.0","script_version":"0.0.8","2":"0.0.8","version_comment":"Happy New Year, Vimmers ;)\r\n\r\n- NOTE: If you want to use mapping\r\n  2 more than characters to toggle dumbbuf buffer,\r\n  you have to change g:dumbbuf_timeoutlen.\r\n  for e.g.: let g:dumbbuf_timeoutlen = 100\r\n  But you can always use 'q' to close buffer.\r\n- Change default values of g:dumbbuf_disp_expr, g:dumbbuf_options\r\n  (Options written in 'For The Experienced User' may be changed\r\n  in the future. sorry)\r\n- Implement g:dumbbuf_all_shown_types.\r\n- Remove g:dumbbuf_single_key, g:dumbbuf_single_key_echo_stack,\r\n  g:dumbbuf_updatetime\r\n- Remove single key emulation.\r\n  This emulates normal key input\r\n  in order to prevent Vim from waiting candidate keys.\r\n  Now I know I have invented the wheel :)\r\n  (I changed &timeout, &timeoutlen)\r\n- Suppress flicker when mapping executed.\r\n- Some optimizations.\r\n- Some fixes of minor bugs.","3":"Happy New Year, Vimmers ;)\r\n\r\n- NOTE: If you want to use mapping\r\n  2 more than characters to toggle dumbbuf buffer,\r\n  you have to change g:dumbbuf_timeoutlen.\r\n  for e.g.: let g:dumbbuf_timeoutlen = 100\r\n  But you can always use 'q' to close buffer.\r\n- Change default values of g:dumbbuf_disp_expr, g:dumbbuf_options\r\n  (Options written in 'For The Experienced User' may be changed\r\n  in the future. sorry)\r\n- Implement g:dumbbuf_all_shown_types.\r\n- Remove g:dumbbuf_single_key, g:dumbbuf_single_key_echo_stack,\r\n  g:dumbbuf_updatetime\r\n- Remove single key emulation.\r\n  This emulates normal key input\r\n  in order to prevent Vim from waiting candidate keys.\r\n  Now I know I have invented the wheel :)\r\n  (I changed &timeout, &timeoutlen)\r\n- Suppress flicker when mapping executed.\r\n- Some optimizations.\r\n- Some fixes of minor bugs.","package":"dumbbuf.vim","4":"dumbbuf.vim","src_id":"11993","5":"11993","creation_date":"1262343615","6":"1262343615"},{"0":"2783","vim_version":"7.0","1":"7.0","script_version":"0.0.7","2":"0.0.7","version_comment":"- highlight support\r\n- add option g:dumbbuf_single_key_echo_stack,\r\n  g:dumbbuf_hl_cursorline,\r\n  g:dumbbuf_remove_marked_when_close.\r\n- change g:dumbbuf_disp_expr's spec.\r\n- fix minor bugs and do some optimizations.\r\n- replace the words 'select' to 'mark' in document and source code.\r\n  I would use 'select' for only visual mode's region.","3":"- highlight support\r\n- add option g:dumbbuf_single_key_echo_stack,\r\n  g:dumbbuf_hl_cursorline,\r\n  g:dumbbuf_remove_marked_when_close.\r\n- change g:dumbbuf_disp_expr's spec.\r\n- fix minor bugs and do some optimizations.\r\n- replace the words 'select' to 'mark' in document and source code.\r\n  I would use 'select' for only visual mode's region.","package":"dumbbuf.vim","4":"dumbbuf.vim","src_id":"11629","5":"11629","creation_date":"1256912436","6":"1256912436"},{"0":"2783","vim_version":"7.0","1":"7.0","script_version":"0.0.6","2":"0.0.6","version_comment":"0.0.5:\r\n    - fix bug: when using with another plugin that uses unlisted buffer,\r\n      pressing <CR> in dumbbuf buffer jumps into that unlisted buffer.\r\n      * Thanks to Bernhard Walle for reporting the bug :) *\r\n    - add g:dumbbuf_open_with.\r\n0.0.6:\r\n    - fix bug: when there is no buffers in list,\r\n      dumbbuf can't get selected buffer info.\r\n    - add option g:dumbbuf_wrap_cursor, and allow 'keep' in\r\n      g:dumbbuf_cursor_pos.\r\n    - implement 'select' of buffers. mapping is 'xx'.\r\n","3":"0.0.5:\r\n    - fix bug: when using with another plugin that uses unlisted buffer,\r\n      pressing <CR> in dumbbuf buffer jumps into that unlisted buffer.\r\n      * Thanks to Bernhard Walle for reporting the bug :) *\r\n    - add g:dumbbuf_open_with.\r\n0.0.6:\r\n    - fix bug: when there is no buffers in list,\r\n      dumbbuf can't get selected buffer info.\r\n    - add option g:dumbbuf_wrap_cursor, and allow 'keep' in\r\n      g:dumbbuf_cursor_pos.\r\n    - implement 'select' of buffers. mapping is 'xx'.\r\n","package":"dumbbuf.vim","4":"dumbbuf.vim","src_id":"11450","5":"11450","creation_date":"1254154098","6":"1254154098"},{"0":"2783","vim_version":"7.0","1":"7.0","script_version":"0.0.4","2":"0.0.4","version_comment":"- implement single key mappings like QuickBuf.vim.\r\n  'let g:dumbbuf_single_key = 1' to use it.\r\n- add g:dumbbuf_single_key, g:dumbbuf_updatetime.\r\n- map plain gg and G mappings in local buffer.\r\n- fix bug of making a waste buffer when called from\r\n  unlisted buffer.\r\n","3":"- implement single key mappings like QuickBuf.vim.\r\n  'let g:dumbbuf_single_key = 1' to use it.\r\n- add g:dumbbuf_single_key, g:dumbbuf_updatetime.\r\n- map plain gg and G mappings in local buffer.\r\n- fix bug of making a waste buffer when called from\r\n  unlisted buffer.\r\n","package":"dumbbuf.vim","4":"dumbbuf.vim","src_id":"11436","5":"11436","creation_date":"1253954928","6":"1253954928"},{"0":"2783","vim_version":"7.0","1":"7.0","script_version":"0.0.3","2":"0.0.3","version_comment":"- fix bug of trapping all errors(including other plugin error).","3":"- fix bug of trapping all errors(including other plugin error).","package":"dumbbuf.vim","4":"dumbbuf.vim","src_id":"11422","5":"11422","creation_date":"1253752167","6":"1253752167"},{"0":"2783","vim_version":"6.0","1":"6.0","script_version":"0.0.1","2":"0.0.1","version_comment":"implement g:dumbbuf_cursor_pos, g:dumbbuf_shown_type, and 'tt' mapping.\r\nand fix bug of showing listed buffers even if current buffer is unlisted.","3":"implement g:dumbbuf_cursor_pos, g:dumbbuf_shown_type, and 'tt' mapping.\r\nand fix bug of showing listed buffers even if current buffer is unlisted.","package":"dumbbuf.vim","4":"dumbbuf.vim","src_id":"11364","5":"11364","creation_date":"1252831983","6":"1252831983"},{"0":"2783","vim_version":"6.0","1":"6.0","script_version":"0.0.0","2":"0.0.0","version_comment":"Initial upload","3":"Initial upload","package":"dumbbuf.vim","4":"dumbbuf.vim","src_id":"11359","5":"11359","creation_date":"1252694059","6":"1252694059"}]},"2782":{"script_id":"2782","0":"2782","script_name":"operator-replace","1":"operator-replace","script_type":"utility","2":"utility","summary":"Operator to replace text with register content","3":"Operator to replace text with register content","description":"*operator-replace* is a Vim plugin to provide an operator to replace\na specified text with register content.  This is shortcut for several types of\noperations such as \"d{motion}P\" and \"c{motion}<C-r>{register}\".\n\n\nRequirements:\n- Vim 7.2 or later\n- |operator-user| 0.0.5 or later (vimscript#2692)\n\nLatest version:\nhttp:\/\/github.com\/kana\/config\/commits\/vim-operator-replace\n\nDocument in HTML format:\nhttp:\/\/kana.github.com\/config\/vim\/operator-replace.html","4":"*operator-replace* is a Vim plugin to provide an operator to replace\na specified text with register content.  This is shortcut for several types of\noperations such as \"d{motion}P\" and \"c{motion}<C-r>{register}\".\n\n\nRequirements:\n- Vim 7.2 or later\n- |operator-user| 0.0.5 or later (vimscript#2692)\n\nLatest version:\nhttp:\/\/github.com\/kana\/config\/commits\/vim-operator-replace\n\nDocument in HTML format:\nhttp:\/\/kana.github.com\/config\/vim\/operator-replace.html","install_details":"...","5":"...","first_name":"Kana","6":"Kana","last_name":"Natsuno","7":"Natsuno","releases":[{"0":"2782","vim_version":"7.0","1":"7.0","script_version":"0.0.3","2":"0.0.3","version_comment":"- Fix to correctly handle empty region.  For example, |<Plug>(operator-replace)| with |it| on text such as \"<div><\/div>\" did not work correctly.","3":"- Fix to correctly handle empty region.  For example, |<Plug>(operator-replace)| with |it| on text such as \"<div><\/div>\" did not work correctly.","package":"vim-operator-replace-0.0.3.zip","4":"vim-operator-replace-0.0.3.zip","src_id":"19063","5":"19063","creation_date":"1354193036","6":"1354193036"},{"0":"2782","vim_version":"7.0","1":"7.0","script_version":"0.0.1","2":"0.0.1","version_comment":"- Fix edge case bugs.  Now replaacing at the end of line or the end of buffer work as you expect.","3":"- Fix edge case bugs.  Now replaacing at the end of line or the end of buffer work as you expect.","package":"vim-operator-replace-0.0.1.zip","4":"vim-operator-replace-0.0.1.zip","src_id":"11381","5":"11381","creation_date":"1253055895","6":"1253055895"},{"0":"2782","vim_version":"7.0","1":"7.0","script_version":"0.0.0","2":"0.0.0","version_comment":"Initial upload","3":"Initial upload","package":"vim-operator-replace-0.0.0.zip","4":"vim-operator-replace-0.0.0.zip","src_id":"11354","5":"11354","creation_date":"1252582384","6":"1252582384"}]},"2781":{"script_id":"2781","0":"2781","script_name":"Django helper utils","1":"Django helper utils","script_type":"utility","2":"utility","summary":"Url tag jump, template path import and html client dump","3":"Url tag jump, template path import and html client dump","description":"repo here: http:\/\/github.com\/mjbrownie\/django_helper.vim\/tree\/master\r\n\r\n#note. This is only tested on linux with python support. in my ~\/.bashrc I have the following line which allows django modules to be imported \r\n\r\nexport DJANGO_SETTINGS_MODULE=settings\r\n\r\nResolve a url to a tag \r\n\r\nUsage\r\n\r\nfor a given django url path\r\n\r\nurlpatterns(\r\n '\/some\/url\/path', 'some.django.view.function_name'\r\n)\r\n\r\n:DUrlTag \/some\/relative\/path\/\r\n\r\nwill resolve the path to the function and then call\r\n:tag function_name\r\n\r\nYou need to have an up to date tags file and the command might choke on\r\ncomplicated views with lots of decorators etc.\r\n\r\n\r\n:DClient \/some\/relative\/path\/\r\n\r\nwill dump the html in a scratch window split\r\n\r\nif settings.py is in the root  of the path this script will :set path+= all template directories including INSTALLED_APPS, \r\n\r\nso you can 'gf' to template files","4":"repo here: http:\/\/github.com\/mjbrownie\/django_helper.vim\/tree\/master\r\n\r\n#note. This is only tested on linux with python support. in my ~\/.bashrc I have the following line which allows django modules to be imported \r\n\r\nexport DJANGO_SETTINGS_MODULE=settings\r\n\r\nResolve a url to a tag \r\n\r\nUsage\r\n\r\nfor a given django url path\r\n\r\nurlpatterns(\r\n '\/some\/url\/path', 'some.django.view.function_name'\r\n)\r\n\r\n:DUrlTag \/some\/relative\/path\/\r\n\r\nwill resolve the path to the function and then call\r\n:tag function_name\r\n\r\nYou need to have an up to date tags file and the command might choke on\r\ncomplicated views with lots of decorators etc.\r\n\r\n\r\n:DClient \/some\/relative\/path\/\r\n\r\nwill dump the html in a scratch window split\r\n\r\nif settings.py is in the root  of the path this script will :set path+= all template directories including INSTALLED_APPS, \r\n\r\nso you can 'gf' to template files","install_details":"","5":"","first_name":"Michael","6":"Michael","last_name":"Brown","7":"Brown","releases":[{"0":"2781","vim_version":"7.2","1":"7.2","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"django_helper.vim","4":"django_helper.vim","src_id":"11348","5":"11348","creation_date":"1252484982","6":"1252484982"}]},"2780":{"script_id":"2780","0":"2780","script_name":"python tag import","1":"python tag import","script_type":"ftplugin","2":"ftplugin","summary":"guesses the import path of a python tag","3":"guesses the import path of a python tag","description":"(Note this plugin is superceded by rope.vim).\r\n\r\nrepo: http:\/\/github.com\/mjbrownie\/Python-Tag-Import\/tree\/master. bugs\/suggestions welcome\r\n\r\nvisual example here http:\/\/ttyshare.com\/rec\/michael\/77604285\/\r\n\r\nThis is for when you remember the name of a library function\/class but not the module.path it is under\r\n\r\nEg. on a new line type. (control-b in insert mode is the default key but can be changed. see below)\r\n\r\nfuncname<c-b>\r\nto get complete import  options eg \r\n\r\nfrom foo.bar.module import funcname\r\nimport foo.bar.module as module\r\n\r\netc.\r\n\r\nIn normal mode <leader>i will create an import for the current word\r\n\r\nYou can customise the import statements to your style preferences in your .vimrc eg\r\n\r\nlet g:pythontagimport_from = 0\r\nturns off \r\nfrom  foo.bar.module import funcname\r\n\r\nlet g:pythontagimport_from_mod = 0\r\nturns off \r\nfrom foo.bar import module #module.funcname\r\n\r\nlet g:pythontagimport_as = 0\r\nturns off \r\nimport foo.bar.module as module #module.funcname\r\n\r\nlet g:pythontagimport_full  = 0\r\nturns off\r\nimport foo.bar.module #foo.bar.module.funcname\r\n\r\n\r\n\" Usage:\r\n\"\r\n\"           You need a ctags file with the --fields=+i\r\n\"           option set\r\n\"\r\n\"           on a new line type the function you want to import\r\n\"           then hit the complete key\r\n\"           \r\n\"           eg. type on a line\r\n\"           \r\n\"           some_func\r\n\"           hit <c-b>in insert mode and get\r\n\"           from some.app.module.path import some_func\r\n\"\r\n\"           hotkey:\r\n\"               insert mode map.\r\n\"               <c-b> is the current default.\r\n\"\r\n\"           variables:\r\n\"\r\n\"               g:pythontagimportkey\r\n\"                   the key used to complete function\r\n\"                   parameters and key words.\r\n\"\r\n\"Limitations:\r\n\"\r\n\"           This plugin is only as smart as your tags file.\r\n\"           Completion is created through inspecting the filename\r\n\"           in the tags file so functions that are rereferenced will not be\r\n\"           picked up. I put this out there in the hope someone can do \r\n\"           some fancy introspective alternative.\r\n\"\r\n\"Options:\r\n\"           Setting the path can keep options relevant. At tht moment\r\n\"           it defaults to sys.path. It can come up with some bad guesses\r\n\"           Eg.\r\n\"           let g:python_path = ['\/usr\/lib\/python2.4\/site-packages\/']\r\n\r\n","4":"(Note this plugin is superceded by rope.vim).\r\n\r\nrepo: http:\/\/github.com\/mjbrownie\/Python-Tag-Import\/tree\/master. bugs\/suggestions welcome\r\n\r\nvisual example here http:\/\/ttyshare.com\/rec\/michael\/77604285\/\r\n\r\nThis is for when you remember the name of a library function\/class but not the module.path it is under\r\n\r\nEg. on a new line type. (control-b in insert mode is the default key but can be changed. see below)\r\n\r\nfuncname<c-b>\r\nto get complete import  options eg \r\n\r\nfrom foo.bar.module import funcname\r\nimport foo.bar.module as module\r\n\r\netc.\r\n\r\nIn normal mode <leader>i will create an import for the current word\r\n\r\nYou can customise the import statements to your style preferences in your .vimrc eg\r\n\r\nlet g:pythontagimport_from = 0\r\nturns off \r\nfrom  foo.bar.module import funcname\r\n\r\nlet g:pythontagimport_from_mod = 0\r\nturns off \r\nfrom foo.bar import module #module.funcname\r\n\r\nlet g:pythontagimport_as = 0\r\nturns off \r\nimport foo.bar.module as module #module.funcname\r\n\r\nlet g:pythontagimport_full  = 0\r\nturns off\r\nimport foo.bar.module #foo.bar.module.funcname\r\n\r\n\r\n\" Usage:\r\n\"\r\n\"           You need a ctags file with the --fields=+i\r\n\"           option set\r\n\"\r\n\"           on a new line type the function you want to import\r\n\"           then hit the complete key\r\n\"           \r\n\"           eg. type on a line\r\n\"           \r\n\"           some_func\r\n\"           hit <c-b>in insert mode and get\r\n\"           from some.app.module.path import some_func\r\n\"\r\n\"           hotkey:\r\n\"               insert mode map.\r\n\"               <c-b> is the current default.\r\n\"\r\n\"           variables:\r\n\"\r\n\"               g:pythontagimportkey\r\n\"                   the key used to complete function\r\n\"                   parameters and key words.\r\n\"\r\n\"Limitations:\r\n\"\r\n\"           This plugin is only as smart as your tags file.\r\n\"           Completion is created through inspecting the filename\r\n\"           in the tags file so functions that are rereferenced will not be\r\n\"           picked up. I put this out there in the hope someone can do \r\n\"           some fancy introspective alternative.\r\n\"\r\n\"Options:\r\n\"           Setting the path can keep options relevant. At tht moment\r\n\"           it defaults to sys.path. It can come up with some bad guesses\r\n\"           Eg.\r\n\"           let g:python_path = ['\/usr\/lib\/python2.4\/site-packages\/']\r\n\r\n","install_details":"","5":"","first_name":"Michael","6":"Michael","last_name":"Brown","7":"Brown","releases":[{"0":"2780","vim_version":"7.0","1":"7.0","script_version":"0.3.1","2":"0.3.1","version_comment":"Uses getline for better expansion. Added a normal mode mapping to get the import statement forthe <cword>","3":"Uses getline for better expansion. Added a normal mode mapping to get the import statement forthe <cword>","package":"python_tag_import.vim","4":"python_tag_import.vim","src_id":"12499","5":"12499","creation_date":"1267158753","6":"1267158753"},{"0":"2780","vim_version":"7.0","1":"7.0","script_version":"0.3","2":"0.3","version_comment":"Added support for variations in python import statements. Eg. from ? import ?, import ? as ?, etc","3":"Added support for variations in python import statements. Eg. from ? import ?, import ? as ?, etc","package":"python_tag_import.vim","4":"python_tag_import.vim","src_id":"11710","5":"11710","creation_date":"1257999992","6":"1257999992"},{"0":"2780","vim_version":"7.0","1":"7.0","script_version":"0.1.1","2":"0.1.1","version_comment":"Fixed a bug introduced affecting relative directories","3":"Fixed a bug introduced affecting relative directories","package":"python_tag_import.vim","4":"python_tag_import.vim","src_id":"11353","5":"11353","creation_date":"1252571990","6":"1252571990"},{"0":"2780","vim_version":"7.2","1":"7.2","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"python_tag_import.vim","4":"python_tag_import.vim","src_id":"11347","5":"11347","creation_date":"1252484494","6":"1252484494"}]},"2779":{"script_id":"2779","0":"2779","script_name":"moss","1":"moss","script_type":"color scheme","2":"color scheme","summary":"Dark color scheme for low light conditions","3":"Dark color scheme for low light conditions","description":"Moss is a dark scheme consisting primarily of green & blue.\r\n墨绿背景，以蓝绿为主色调，比较暗，适合夜晚等弱光环境使用。\r\nscreenshots\r\n2.1\r\n               perl: http:\/\/i33.tinypic.com\/ipmuxh.png\r\n    shell script: http:\/\/i38.tinypic.com\/f2ubyq.png\r\n2.2\r\n               perl: http:\/\/i44.tinypic.com\/30kpqpl.png","4":"Moss is a dark scheme consisting primarily of green & blue.\r\n墨绿背景，以蓝绿为主色调，比较暗，适合夜晚等弱光环境使用。\r\nscreenshots\r\n2.1\r\n               perl: http:\/\/i33.tinypic.com\/ipmuxh.png\r\n    shell script: http:\/\/i38.tinypic.com\/f2ubyq.png\r\n2.2\r\n               perl: http:\/\/i44.tinypic.com\/30kpqpl.png","install_details":"Copy the file to ~\/.vim\/colors (or $VIM\/vimfiles\/colors on Windows) and :colo moss","5":"Copy the file to ~\/.vim\/colors (or $VIM\/vimfiles\/colors on Windows) and :colo moss","first_name":"Chunlin","6":"Chunlin","last_name":"Li(\u674e)","7":"Li(李)","releases":[{"0":"2779","vim_version":"7.0","1":"7.0","script_version":"2.2","2":"2.2","version_comment":"特别版\r\nSpecial Edition","3":"特别版\r\nSpecial Edition","package":"moss.vim","4":"moss.vim","src_id":"16850","5":"16850","creation_date":"1321024793","6":"1321024793"},{"0":"2779","vim_version":"6.0","1":"6.0","script_version":"2.1","2":"2.1","version_comment":"Add 256 color term support","3":"Add 256 color term support","package":"moss.vim","4":"moss.vim","src_id":"13499","5":"13499","creation_date":"1281086600","6":"1281086600"}]},"2778":{"script_id":"2778","0":"2778","script_name":"gui2term.py","1":"gui2term.py","script_type":"utility","2":"utility","summary":"Python script that add 256-color terminal support to GUI only colorschemes.","3":"Python script that add 256-color terminal support to GUI only colorschemes.","description":"Requirement: python3 for 2.0+. However, it should not be hard to make it work under Python 2 if you are familiar with Python (you can try the `3to2` command).\r\n\r\nUsage:\r\ninvoke it like this in commandline:\r\n  .\/gui2term.py sourcefile newfile\r\nor\r\n  python3 gui2term.py sourcefile newfile\r\n\r\nNote:\r\n* It searches and processes lines in a vim colorscheme that seems like a normal highlight command, so it does not work with all the colorscheme.\r\n* Some GUI only colorschemes may use the default scheme if it found itself under a terminal. You need to manually remove these lines.\r\n* For some colors, the output is rather bad.\r\n\r\ngui2term is part of winterpy on github: https:\/\/github.com\/lilydjwg\/winterpy\/tree\/master\/pyexe\/gui2term.py","4":"Requirement: python3 for 2.0+. However, it should not be hard to make it work under Python 2 if you are familiar with Python (you can try the `3to2` command).\r\n\r\nUsage:\r\ninvoke it like this in commandline:\r\n  .\/gui2term.py sourcefile newfile\r\nor\r\n  python3 gui2term.py sourcefile newfile\r\n\r\nNote:\r\n* It searches and processes lines in a vim colorscheme that seems like a normal highlight command, so it does not work with all the colorscheme.\r\n* Some GUI only colorschemes may use the default scheme if it found itself under a terminal. You need to manually remove these lines.\r\n* For some colors, the output is rather bad.\r\n\r\ngui2term is part of winterpy on github: https:\/\/github.com\/lilydjwg\/winterpy\/tree\/master\/pyexe\/gui2term.py","install_details":"Put the file wherever you like.\r\n\r\nTo make it recognize color names, the script needs the rgb.txt file (:help rgb.txt). It will check the current working directory and where it lies for it. If there is a 'locate' command on your system, it will also try to use that. The file may be found where you installed Vim; it may also be shipped with X window, emacs and some other packages.\r\n","5":"Put the file wherever you like.\r\n\r\nTo make it recognize color names, the script needs the rgb.txt file (:help rgb.txt). It will check the current working directory and where it lies for it. If there is a 'locate' command on your system, it will also try to use that. The file may be found where you installed Vim; it may also be shipped with X window, emacs and some other packages.\r\n","first_name":"lilydjwg","6":"lilydjwg","last_name":" ","7":" ","releases":[{"0":"2778","vim_version":"7.0","1":"7.0","script_version":"3.0.3","2":"3.0.3","version_comment":"when trying 'locate' command, add '-e' option and read only one line.","3":"when trying 'locate' command, add '-e' option and read only one line.","package":"gui2term.py","4":"gui2term.py","src_id":"16205","5":"16205","creation_date":"1312615821","6":"1312615821"},{"0":"2778","vim_version":"7.0","1":"7.0","script_version":"3.0.2","2":"3.0.2","version_comment":"when finding rgb.txt, try 'locate' command last.","3":"when finding rgb.txt, try 'locate' command last.","package":"gui2term.py","4":"gui2term.py","src_id":"15952","5":"15952","creation_date":"1308745472","6":"1308745472"},{"0":"2778","vim_version":"7.0","1":"7.0","script_version":"3.0.1","2":"3.0.1","version_comment":"- use 'NONE' instead of 'none' as the later is reported to be invalid color names sometimes\r\n- sorted highlight args so that it is easy to remove what has been added or modified","3":"- use 'NONE' instead of 'none' as the later is reported to be invalid color names sometimes\r\n- sorted highlight args so that it is easy to remove what has been added or modified","package":"gui2term.py","4":"gui2term.py","src_id":"15912","5":"15912","creation_date":"1308308030","6":"1308308030"},{"0":"2778","vim_version":"7.0","1":"7.0","script_version":"3.0","2":"3.0","version_comment":"* try to use `locate' to find rgb.txt\r\n* improve color matching algorithm (thanks to Eric Pruitt for the idea)\r\n* other small fixes","3":"* try to use `locate' to find rgb.txt\r\n* improve color matching algorithm (thanks to Eric Pruitt for the idea)\r\n* other small fixes","package":"gui2term.py","4":"gui2term.py","src_id":"15892","5":"15892","creation_date":"1308070020","6":"1308070020"},{"0":"2778","vim_version":"7.0","1":"7.0","script_version":"2.0","2":"2.0","version_comment":"- Rewrite so that when there are already cterm definitions, they will be updated.\r\n- Avoid Chinese output.\r\n- Switch to Python 3.","3":"- Rewrite so that when there are already cterm definitions, they will be updated.\r\n- Avoid Chinese output.\r\n- Switch to Python 3.","package":"gui2term.py","4":"gui2term.py","src_id":"14746","5":"14746","creation_date":"1295011639","6":"1295011639"},{"0":"2778","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"gui2term.py","4":"gui2term.py","src_id":"11331","5":"11331","creation_date":"1252227343","6":"1252227343"}]},"2777":{"script_id":"2777","0":"2777","script_name":"tir_black","1":"tir_black","script_type":"color scheme","2":"color scheme","summary":"based on ir_black colorscheme, tweaked for 256 color terms","3":"based on ir_black colorscheme, tweaked for 256 color terms","description":"Screenshot running in MacVim: http:\/\/www.jordansoyke.com-a.googlepages.com\/tir_black_shot.jpg\r\nThis is a colorscheme based on ir_black (http:\/\/blog.infinitered.com\/entries\/show\/8). I really like this scheme, but I wanted it to work in 256 color terminals.","4":"Screenshot running in MacVim: http:\/\/www.jordansoyke.com-a.googlepages.com\/tir_black_shot.jpg\r\nThis is a colorscheme based on ir_black (http:\/\/blog.infinitered.com\/entries\/show\/8). I really like this scheme, but I wanted it to work in 256 color terminals.","install_details":"just put this in ~\/.vim\/colors","5":"just put this in ~\/.vim\/colors","first_name":"jordan","6":"jordan","last_name":"soyke","7":"soyke","releases":[{"0":"2777","vim_version":"7.0","1":"7.0","script_version":"1.2","2":"1.2","version_comment":"adjusted statusline to have higher contrast, look more like gui version.","3":"adjusted statusline to have higher contrast, look more like gui version.","package":"tir_black.vim","4":"tir_black.vim","src_id":"11430","5":"11430","creation_date":"1253862822","6":"1253862822"},{"0":"2777","vim_version":"6.0","1":"6.0","script_version":"1.1","2":"1.1","version_comment":"Fixed unsightly TODO and search highlighting.","3":"Fixed unsightly TODO and search highlighting.","package":"tir_black.vim","4":"tir_black.vim","src_id":"11410","5":"11410","creation_date":"1253411823","6":"1253411823"},{"0":"2777","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"tir_black.vim","4":"tir_black.vim","src_id":"11327","5":"11327","creation_date":"1252123543","6":"1252123543"}]},"2776":{"script_id":"2776","0":"2776","script_name":"vilight.vim","1":"vilight.vim","script_type":"color scheme","2":"color scheme","summary":"A more literal translation of Will Farrington's Twilight color theme","3":"A more literal translation of Will Farrington's Twilight color theme","description":"A big fan of the gedit color theme 'Twilight' by Will Farrington, I made a pretty literal translation of it for vim here. Originally, the only changes from Farrington's scheme were that I did away with the 'dark maroon' guibg and added Pmenu colors, but it has slowly grown to incorporate even more 'Vim-isms'. \r\n\r\nScreenshots here => \"http:\/\/robrobbins.info\/?page_id=2\"","4":"A big fan of the gedit color theme 'Twilight' by Will Farrington, I made a pretty literal translation of it for vim here. Originally, the only changes from Farrington's scheme were that I did away with the 'dark maroon' guibg and added Pmenu colors, but it has slowly grown to incorporate even more 'Vim-isms'. \r\n\r\nScreenshots here => \"http:\/\/robrobbins.info\/?page_id=2\"","install_details":"Just drop into .vim\/colors. I haven't made terminal compatible modes yet, so it only looks proper in gvim. If you have any term prefs in your .vimrc (like I had t_co=256) comment them out if you plan to launch from a terminal window or the colors may be incorrect (I notice this on my linux box. I'm going to update with terminal compat modes soon - rob)","5":"Just drop into .vim\/colors. I haven't made terminal compatible modes yet, so it only looks proper in gvim. If you have any term prefs in your .vimrc (like I had t_co=256) comment them out if you plan to launch from a terminal window or the colors may be incorrect (I notice this on my linux box. I'm going to update with terminal compat modes soon - rob)","first_name":"rob","6":"rob","last_name":"robbins","7":"robbins","releases":[{"0":"2776","vim_version":"7.0","1":"7.0","script_version":"1.5","2":"1.5","version_comment":"Added (SpecialKey) for Tab. Thanks to Tyler Kahn.","3":"Added (SpecialKey) for Tab. Thanks to Tyler Kahn.","package":"vilight.vim","4":"vilight.vim","src_id":"16574","5":"16574","creation_date":"1316975731","6":"1316975731"},{"0":"2776","vim_version":"7.0","1":"7.0","script_version":"1.4","2":"1.4","version_comment":"Softer all around with more grays (I\\'ve been working in Macvim lately). Added more highlighting for HTML, JavaScript and Python in particular. Use fonts that have regular, bold, and italic variants (the excellent Panic Sans comes to mind).","3":"Softer all around with more grays (I\\'ve been working in Macvim lately). Added more highlighting for HTML, JavaScript and Python in particular. Use fonts that have regular, bold, and italic variants (the excellent Panic Sans comes to mind).","package":"vilight.vim","4":"vilight.vim","src_id":"14098","5":"14098","creation_date":"1287696139","6":"1287696139"},{"0":"2776","vim_version":"7.0","1":"7.0","script_version":"1.3.1","2":"1.3.1","version_comment":"A few tweaks from my current working version such as:\r\n1. Italics for comments and folds\r\n2. underlines for errors to increse visibility\r\n3. and more...;)\r\n(Corrected an error from this mornings uploaded version with 1.3.1)","3":"A few tweaks from my current working version such as:\r\n1. Italics for comments and folds\r\n2. underlines for errors to increse visibility\r\n3. and more...;)\r\n(Corrected an error from this mornings uploaded version with 1.3.1)","package":"vilight.vim","4":"vilight.vim","src_id":"12694","5":"12694","creation_date":"1269378854","6":"1269378854"},{"0":"2776","vim_version":"7.0","1":"7.0","script_version":"1.2","2":"1.2","version_comment":"Added colors for Diff","3":"Added colors for Diff","package":"vilight.vim","4":"vilight.vim","src_id":"11887","5":"11887","creation_date":"1260391893","6":"1260391893"},{"0":"2776","vim_version":"7.0","1":"7.0","script_version":"1.1","2":"1.1","version_comment":"TODO and TITLE needed tweaking. ","3":"TODO and TITLE needed tweaking. ","package":"vilight.vim","4":"vilight.vim","src_id":"11330","5":"11330","creation_date":"1252175045","6":"1252175045"},{"0":"2776","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"vilight.vim","4":"vilight.vim","src_id":"11325","5":"11325","creation_date":"1252102382","6":"1252102382"}]},"2775":{"script_id":"2775","0":"2775","script_name":"logpad.vim","1":"logpad.vim","script_type":"utility","2":"utility","summary":"Vim plugin for emulating Windows Notepad's logging functionality","3":"Vim plugin for emulating Windows Notepad's logging functionality","description":"logpad.vim emulates Windows Notepad's logging feature.\r\n\r\nCreate a new file, write .LOG as the first line and save it. Every time you reopen the file, a new line with the current timestamp is added, so you can easily maintain a chronologic log of your tasks.\r\n\r\nBy default, this plugin works the same way as the original Notepad. You can modify certain aspects of it by setting the following variables:\r\n\r\nlet LogpadEnabled = [ 0 \/ 1 ]\r\n* enables\/disables logpad\r\n* default value: 1\r\n\r\nlet LogpadInsert = [ 0 \/ 1 ]\r\n* automatically enables &insertmode when a new log entry is created\r\n* default value: 0\r\n\r\nlet LogpadLineBreak = [ 0 \/ 1 ]\r\n* adds an empty line before a new log entry\r\n* default value: 0 (Windows Notepad behavior)\r\n\r\nlet LogpadIgnoreNotes = [ 0 \/ 1 ]\r\n* allows adding notes before the first log entry\r\n* default value: 0\r\n\r\nlet LogpadIgnoreReadOnly = [ 0 \/ 1 ]\r\n* allows logpad to ignore a file's read-only flag\r\n* default value: 0","4":"logpad.vim emulates Windows Notepad's logging feature.\r\n\r\nCreate a new file, write .LOG as the first line and save it. Every time you reopen the file, a new line with the current timestamp is added, so you can easily maintain a chronologic log of your tasks.\r\n\r\nBy default, this plugin works the same way as the original Notepad. You can modify certain aspects of it by setting the following variables:\r\n\r\nlet LogpadEnabled = [ 0 \/ 1 ]\r\n* enables\/disables logpad\r\n* default value: 1\r\n\r\nlet LogpadInsert = [ 0 \/ 1 ]\r\n* automatically enables &insertmode when a new log entry is created\r\n* default value: 0\r\n\r\nlet LogpadLineBreak = [ 0 \/ 1 ]\r\n* adds an empty line before a new log entry\r\n* default value: 0 (Windows Notepad behavior)\r\n\r\nlet LogpadIgnoreNotes = [ 0 \/ 1 ]\r\n* allows adding notes before the first log entry\r\n* default value: 0\r\n\r\nlet LogpadIgnoreReadOnly = [ 0 \/ 1 ]\r\n* allows logpad to ignore a file's read-only flag\r\n* default value: 0","install_details":"Download the logpad.vim file. Put it into your plugins directory. That's it, basically.","5":"Download the logpad.vim file. Put it into your plugins directory. That's it, basically.","first_name":"tux.","6":"tux.","last_name":"(tuxproject.de)","7":"(tuxproject.de)","releases":[{"0":"2775","vim_version":"6.0","1":"6.0","script_version":"1.6","2":"1.6","version_comment":"fix: logpad.vim was not detecting some timestamps correctly","3":"fix: logpad.vim was not detecting some timestamps correctly","package":"logpad.vim","4":"logpad.vim","src_id":"20518","5":"20518","creation_date":"1373818858","6":"1373818858"},{"0":"2775","vim_version":"6.0","1":"6.0","script_version":"1.5","2":"1.5","version_comment":"insert mode code improvement and using function! now (partial patch by Talha Mansoor)","3":"insert mode code improvement and using function! now (partial patch by Talha Mansoor)","package":"logpad.vim","4":"logpad.vim","src_id":"20515","5":"20515","creation_date":"1373817141","6":"1373817141"},{"0":"2775","vim_version":"6.0","1":"6.0","script_version":"1.4","2":"1.4","version_comment":"added check and switch for ignoring a file's read-only flag (just to be sure...)","3":"added check and switch for ignoring a file's read-only flag (just to be sure...)","package":"logpad.vim","4":"logpad.vim","src_id":"11921","5":"11921","creation_date":"1261196344","6":"1261196344"},{"0":"2775","vim_version":"6.0","1":"6.0","script_version":"1.3","2":"1.3","version_comment":"added support for GetLatestVimScripts\r\nremoved initial (unnecessary) cursor() call","3":"added support for GetLatestVimScripts\r\nremoved initial (unnecessary) cursor() call","package":"logpad.vim","4":"logpad.vim","src_id":"11342","5":"11342","creation_date":"1252385773","6":"1252385773"},{"0":"2775","vim_version":"6.0","1":"6.0","script_version":"1.2","2":"1.2","version_comment":"fix: converted logpad.vim to UNIX format (was not working outside Windows, big sorry)","3":"fix: converted logpad.vim to UNIX format (was not working outside Windows, big sorry)","package":"logpad.vim","4":"logpad.vim","src_id":"11329","5":"11329","creation_date":"1252171952","6":"1252171952"},{"0":"2775","vim_version":"6.0","1":"6.0","script_version":"1.1","2":"1.1","version_comment":"fix: the LogpadLineBreak setting also affects the single empty line below \".LOG\" (original Notepad, emulated by default, doesn't add one either)","3":"fix: the LogpadLineBreak setting also affects the single empty line below \".LOG\" (original Notepad, emulated by default, doesn't add one either)","package":"logpad.vim","4":"logpad.vim","src_id":"11326","5":"11326","creation_date":"1252118677","6":"1252118677"},{"0":"2775","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"logpad.vim","4":"logpad.vim","src_id":"11324","5":"11324","creation_date":"1252093089","6":"1252093089"}]},"2774":{"script_id":"2774","0":"2774","script_name":"whitebox.vim","1":"whitebox.vim","script_type":"color scheme","2":"color scheme","summary":"Light colorscheme with bright colors.","3":"Light colorscheme with bright colors.","description":"Whitebox is a scheme I made because I couldn't find any without dull colors. ","4":"Whitebox is a scheme I made because I couldn't find any without dull colors. ","install_details":"Move whitebox.vim to the ~\/.vim\/colors directory. Type :colorscheme whitebox to launch it.","5":"Move whitebox.vim to the ~\/.vim\/colors directory. Type :colorscheme whitebox to launch it.","first_name":"Taurus","6":"Taurus","last_name":"Olson","7":"Olson","releases":[{"0":"2774","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"whitebox.vim","4":"whitebox.vim","src_id":"11323","5":"11323","creation_date":"1252092694","6":"1252092694"}]},"2773":{"script_id":"2773","0":"2773","script_name":"grex","1":"grex","script_type":"utility","2":"utility","summary":"Operate on lines matched to the last search pattern (:g\/re\/x)","3":"Operate on lines matched to the last search pattern (:g\/re\/x)","description":"*grex* is a Vim plugin to provide useful commands to operate on lines matched\r\nto the last search pattern.  For example, suppose you edit the following\r\ncontent:\r\n\r\n\t#950 bugfix: jump behavior\r\n\t#923 bugfix: vs fold\r\n\t#930 enhancement: foldlevel adjustment\r\n\t#927 todo: release\r\n\t#926 enhancement: performance\r\n\t#924 enhancement: completion\r\n\t#931 bugfix: syntax highlighting\r\n\t#928 enhancement: key mappings\r\n\r\nOnce you search for a keyword such as \"bugfix:\", you can yank all lines\r\nmatched to the search pattern with |:Grey|.  After executing |:Grey|, you can\r\nput the following text:\r\n\r\n\t#950 bugfix: jump behavior\r\n\t#923 bugfix: vs fold\r\n\t#931 bugfix: syntax highlighting\r\n\r\nThere is another command |:Gred| which deletes matched lines instead.\r\n\r\nThis plugin also provides functions and operators to do the same processes as\r\n|:Gred| or |:Grey|.  See |grex-functions|, |grex-key-mappings| and\r\n|grex-commands| for the details.\r\n\r\n\r\nRequirements:\r\n- Vim 7.2 or later\r\n\r\nOptionals:\r\n- |operator-user| 0.0.5 or later (vimscript#2692)\r\n\r\nLatest version:\r\nhttp:\/\/github.com\/kana\/vim-grex\r\n\r\nDocument in HTML format:\r\nhttp:\/\/kana.github.com\/config\/vim\/grex.html","4":"*grex* is a Vim plugin to provide useful commands to operate on lines matched\r\nto the last search pattern.  For example, suppose you edit the following\r\ncontent:\r\n\r\n\t#950 bugfix: jump behavior\r\n\t#923 bugfix: vs fold\r\n\t#930 enhancement: foldlevel adjustment\r\n\t#927 todo: release\r\n\t#926 enhancement: performance\r\n\t#924 enhancement: completion\r\n\t#931 bugfix: syntax highlighting\r\n\t#928 enhancement: key mappings\r\n\r\nOnce you search for a keyword such as \"bugfix:\", you can yank all lines\r\nmatched to the search pattern with |:Grey|.  After executing |:Grey|, you can\r\nput the following text:\r\n\r\n\t#950 bugfix: jump behavior\r\n\t#923 bugfix: vs fold\r\n\t#931 bugfix: syntax highlighting\r\n\r\nThere is another command |:Gred| which deletes matched lines instead.\r\n\r\nThis plugin also provides functions and operators to do the same processes as\r\n|:Gred| or |:Grey|.  See |grex-functions|, |grex-key-mappings| and\r\n|grex-commands| for the details.\r\n\r\n\r\nRequirements:\r\n- Vim 7.2 or later\r\n\r\nOptionals:\r\n- |operator-user| 0.0.5 or later (vimscript#2692)\r\n\r\nLatest version:\r\nhttp:\/\/github.com\/kana\/vim-grex\r\n\r\nDocument in HTML format:\r\nhttp:\/\/kana.github.com\/config\/vim\/grex.html","install_details":"...","5":"...","first_name":"Kana","6":"Kana","last_name":"Natsuno","7":"Natsuno","releases":[{"0":"2773","vim_version":"7.0","1":"7.0","script_version":"0.0.1","2":"0.0.1","version_comment":"Feature enhancements:\n- Add |:Gred|, |grex#delete()| and |<Plug>(operator-grex-delete)|.\n- Support register designation for |grex-operators|.  |operator-user| 0.0.5 or later is required to use this feature.\n- Support register designation for functions |grex-functions|.\n\nMinor improvements:\n- Revise the document.\n\nIncompatible changes:\n- Rename the plugin as \"grex\".  The old name \"grey\" is not proper for further enhancements.\n- Rename all commands, functions and key mappings.","3":"Feature enhancements:\n- Add |:Gred|, |grex#delete()| and |<Plug>(operator-grex-delete)|.\n- Support register designation for |grex-operators|.  |operator-user| 0.0.5 or later is required to use this feature.\n- Support register designation for functions |grex-functions|.\n\nMinor improvements:\n- Revise the document.\n\nIncompatible changes:\n- Rename the plugin as \"grex\".  The old name \"grey\" is not proper for further enhancements.\n- Rename all commands, functions and key mappings.","package":"vim-grex-0.0.1.zip","4":"vim-grex-0.0.1.zip","src_id":"11344","5":"11344","creation_date":"1252452297","6":"1252452297"},{"0":"2773","vim_version":"7.0","1":"7.0","script_version":"0.0.0","2":"0.0.0","version_comment":"Initial upload","3":"Initial upload","package":"vim-grey-0.0.0.zip","4":"vim-grey-0.0.0.zip","src_id":"11322","5":"11322","creation_date":"1252074728","6":"1252074728"}]},"2772":{"script_id":"2772","0":"2772","script_name":"Smart Home Key","1":"Smart Home Key","script_type":"utility","2":"utility","summary":"Better Home key experience for editing, especially for coding","3":"Better Home key experience for editing, especially for coding","description":"Trigger <Home> key arbitrarily in vim or follow below steps:\r\n\r\n    a. Normal mode\r\n        1. Press <Home> key in the middle of a line\r\n        2. Press <Home> key again\r\n\r\n     b. Insert mode\r\n          do the same as above. It works well ^_^\r\n\r\nTake a look at demo film : http:\/\/vimeo.com\/6433112\r\n\r\nGithub: https:\/\/github.com\/chenkaie\/smarthomekey.vim","4":"Trigger <Home> key arbitrarily in vim or follow below steps:\r\n\r\n    a. Normal mode\r\n        1. Press <Home> key in the middle of a line\r\n        2. Press <Home> key again\r\n\r\n     b. Insert mode\r\n          do the same as above. It works well ^_^\r\n\r\nTake a look at demo film : http:\/\/vimeo.com\/6433112\r\n\r\nGithub: https:\/\/github.com\/chenkaie\/smarthomekey.vim","install_details":"Place in ~\/.vim\/plugin (to load at start up)","5":"Place in ~\/.vim\/plugin (to load at start up)","first_name":"Kent","6":"Kent","last_name":"Chen","7":"Chen","releases":[{"0":"2772","vim_version":"7.0","1":"7.0","script_version":"1.2","2":"1.2","version_comment":"by <silent> way to hide annoying msg!","3":"by <silent> way to hide annoying msg!","package":"crazyhomekey.vim","4":"crazyhomekey.vim","src_id":"11476","5":"11476","creation_date":"1254595586","6":"1254595586"},{"0":"2772","vim_version":"7.0","1":"7.0","script_version":"1.1","2":"1.1","version_comment":"Fine tune this script and layout","3":"Fine tune this script and layout","package":"crazyhomekey.vim","4":"crazyhomekey.vim","src_id":"11316","5":"11316","creation_date":"1252051176","6":"1252051176"},{"0":"2772","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"crazyhomekey.vim","4":"crazyhomekey.vim","src_id":"11315","5":"11315","creation_date":"1252050723","6":"1252050723"}]},"2771":{"script_id":"2771","0":"2771","script_name":"Conque Shell","1":"Conque Shell","script_type":"utility","2":"utility","summary":"Run interactive commands inside a Vim buffer","3":"Run interactive commands inside a Vim buffer","description":"*no longer supported*\r\n\r\nConque is a Vim plugin which allows you to run interactive programs, such as bash on linux or powershell.exe on Windows, inside a Vim buffer. In other words it is a terminal emulator which uses a Vim buffer to display the program output. \r\n\r\n== SCREENSHOTS ==\r\n\r\nhttp:\/\/Conque.googlecode.com\/svn\/wiki\/screenshot\/unix.jpg\r\nhttp:\/\/Conque.googlecode.com\/svn\/wiki\/screenshot\/windows.jpg\r\n\r\n== USAGE ==\r\n\r\nType :ConqueTerm <command> to run your command in vim, for example:\r\n\r\n:ConqueTerm bash\r\n:ConqueTerm mysql -h localhost -u joe -p sock_collection\r\n:ConqueTerm Powershell.exe\r\n:ConqueTerm C:\\Python27\\python.exe\r\n\r\nTo open ConqueTerm in a new horizontal or vertical buffer use:\r\n\r\n:ConqueTermSplit <command>\r\n:ConqueTermVSplit <command>\r\n:ConqueTermTab <command>\r\n\r\nAll text typed in insert mode will be sent to your shell. Use the <F9> key to send a visual selection from any buffer to the shell.\r\n\r\nFor more help type :help ConqueTerm\r\n","4":"*no longer supported*\r\n\r\nConque is a Vim plugin which allows you to run interactive programs, such as bash on linux or powershell.exe on Windows, inside a Vim buffer. In other words it is a terminal emulator which uses a Vim buffer to display the program output. \r\n\r\n== SCREENSHOTS ==\r\n\r\nhttp:\/\/Conque.googlecode.com\/svn\/wiki\/screenshot\/unix.jpg\r\nhttp:\/\/Conque.googlecode.com\/svn\/wiki\/screenshot\/windows.jpg\r\n\r\n== USAGE ==\r\n\r\nType :ConqueTerm <command> to run your command in vim, for example:\r\n\r\n:ConqueTerm bash\r\n:ConqueTerm mysql -h localhost -u joe -p sock_collection\r\n:ConqueTerm Powershell.exe\r\n:ConqueTerm C:\\Python27\\python.exe\r\n\r\nTo open ConqueTerm in a new horizontal or vertical buffer use:\r\n\r\n:ConqueTermSplit <command>\r\n:ConqueTermVSplit <command>\r\n:ConqueTermTab <command>\r\n\r\nAll text typed in insert mode will be sent to your shell. Use the <F9> key to send a visual selection from any buffer to the shell.\r\n\r\nFor more help type :help ConqueTerm\r\n","install_details":"== UNIX REQUIREMENTS ==\r\n\r\n   * Vim or GVim 7.0+ with +python and\/or +python3\r\n   * Python 2.3+ and\/or 3.x\r\n\r\n== WINDOWS REQUIREMENTS ==\r\n\r\n   * GVim 7.3 (the official installer from this site)\r\n   * Python 2.7 and\/or 3.1\r\n\r\n== INSTALLATION ==\r\n\r\nvi conque_term.vba\r\n:so %\r\n:q\r\n\r\nOpen conque_term.vba and type the command `:so %` to install it with the Vimball utility. Alternatively, download the zip archive and copy the files by hand into your .vim directory.\r\n","5":"== UNIX REQUIREMENTS ==\r\n\r\n   * Vim or GVim 7.0+ with +python and\/or +python3\r\n   * Python 2.3+ and\/or 3.x\r\n\r\n== WINDOWS REQUIREMENTS ==\r\n\r\n   * GVim 7.3 (the official installer from this site)\r\n   * Python 2.7 and\/or 3.1\r\n\r\n== INSTALLATION ==\r\n\r\nvi conque_term.vba\r\n:so %\r\n:q\r\n\r\nOpen conque_term.vba and type the command `:so %` to install it with the Vimball utility. Alternatively, download the zip archive and copy the files by hand into your .vim directory.\r\n","first_name":"Nico","6":"Nico","last_name":"Raffo","7":"Raffo","releases":[{"0":"2771","vim_version":"7.0","1":"7.0","script_version":"2.2","2":"2.2","version_comment":"* Fixed: previous Vimball was missing files\r\n* Bugfix release","3":"* Fixed: previous Vimball was missing files\r\n* Bugfix release","package":"conqueterm_2.2.vmb","4":"conqueterm_2.2.vmb","src_id":"16279","5":"16279","creation_date":"1313514157","6":"1313514157"},{"0":"2771","vim_version":"7.0","1":"7.0","script_version":"2.2","2":"2.2","version_comment":"Bugfix release. No new features.","3":"Bugfix release. No new features.","package":"conque_2.2.tar.gz","4":"conque_2.2.tar.gz","src_id":"16251","5":"16251","creation_date":"1313195687","6":"1313195687"},{"0":"2771","vim_version":"7.0","1":"7.0","script_version":"202","2":"202","version_comment":"Bugfix release. No new features.","3":"Bugfix release. No new features.","package":"conque_2.2.zip","4":"conque_2.2.zip","src_id":"16250","5":"16250","creation_date":"1313195640","6":"1313195640"},{"0":"2771","vim_version":"7.0","1":"7.0","script_version":"2.1","2":"2.1","version_comment":" * Various performance improvements (Fast mode option)\r\n * Improved unicode handling\r\n * API additions (user-defined callback functions)\r\n * New key shortcuts (execute current file in Conque, etc...)\r\n * Bugfixes","3":" * Various performance improvements (Fast mode option)\r\n * Improved unicode handling\r\n * API additions (user-defined callback functions)\r\n * New key shortcuts (execute current file in Conque, etc...)\r\n * Bugfixes","package":"conque_2.1.vba","4":"conque_2.1.vba","src_id":"15386","5":"15386","creation_date":"1301984810","6":"1301984810"},{"0":"2771","vim_version":"7.0","1":"7.0","script_version":"2.1","2":"2.1","version_comment":"See above","3":"See above","package":"conque_2.1.tar.gz","4":"conque_2.1.tar.gz","src_id":"15385","5":"15385","creation_date":"1301984779","6":"1301984779"},{"0":"2771","vim_version":"7.0","1":"7.0","script_version":"2.1","2":"2.1","version_comment":"See above","3":"See above","package":"conque_2.1.zip","4":"conque_2.1.zip","src_id":"15384","5":"15384","creation_date":"1301984722","6":"1301984722"},{"0":"2771","vim_version":"7.0","1":"7.0","script_version":"2.0","2":"2.0","version_comment":" * Windows support!\r\n * Python 3 support","3":" * Windows support!\r\n * Python 3 support","package":"conque_2.0.vba","4":"conque_2.0.vba","src_id":"14282","5":"14282","creation_date":"1289970052","6":"1289970052"},{"0":"2771","vim_version":"7.0","1":"7.0","script_version":"2.0","2":"2.0","version_comment":"See above","3":"See above","package":"conque_2.0.tar.gz","4":"conque_2.0.tar.gz","src_id":"14281","5":"14281","creation_date":"1289969990","6":"1289969990"},{"0":"2771","vim_version":"7.0","1":"7.0","script_version":"2.0","2":"2.0","version_comment":"See above","3":"See above","package":"conque_2.0.zip","4":"conque_2.0.zip","src_id":"14280","5":"14280","creation_date":"1289969945","6":"1289969945"},{"0":"2771","vim_version":"7.0","1":"7.0","script_version":"1.2","2":"1.2","version_comment":"Mostly bugfixes. New features include:\r\n \r\n * New API functions (BETA)\r\n * New ConqueTerm_CloseOnEnd? option\r\n","3":"Mostly bugfixes. New features include:\r\n \r\n * New API functions (BETA)\r\n * New ConqueTerm_CloseOnEnd? option\r\n","package":"conque_1.2.vba","4":"conque_1.2.vba","src_id":"14041","5":"14041","creation_date":"1286847713","6":"1286847713"},{"0":"2771","vim_version":"7.0","1":"7.0","script_version":"1.2","2":"1.2","version_comment":"Mostly bugfixes. New features include:\r\n \r\n * New API functions (BETA)\r\n * New ConqueTerm_CloseOnEnd? option\r\n","3":"Mostly bugfixes. New features include:\r\n \r\n * New API functions (BETA)\r\n * New ConqueTerm_CloseOnEnd? option\r\n","package":"conque_1.2.zip","4":"conque_1.2.zip","src_id":"14040","5":"14040","creation_date":"1286847679","6":"1286847679"},{"0":"2771","vim_version":"7.0","1":"7.0","script_version":"1.1","2":"1.1","version_comment":" * Allow shell buffer to be hidden\r\n * Fix xterm colors\r\n * Allow custom key for leaving insert mode\r\n * Various other bugfixes","3":" * Allow shell buffer to be hidden\r\n * Fix xterm colors\r\n * Allow custom key for leaving insert mode\r\n * Various other bugfixes","package":"conque_1.1.vba","4":"conque_1.1.vba","src_id":"13071","5":"13071","creation_date":"1275026002","6":"1275026002"},{"0":"2771","vim_version":"7.0","1":"7.0","script_version":"1.1","2":"1.1","version_comment":" * Allow shell buffer to be hidden\r\n * Fix xterm colors\r\n * Allow custom key for leaving insert mode\r\n * Various other bugfixes","3":" * Allow shell buffer to be hidden\r\n * Fix xterm colors\r\n * Allow custom key for leaving insert mode\r\n * Various other bugfixes","package":"conque_1.1.tar.gz","4":"conque_1.1.tar.gz","src_id":"13070","5":"13070","creation_date":"1275025937","6":"1275025937"},{"0":"2771","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"   * Complete python rewrite\r\n   * Add support for ncurses based applications\r\n   * Add continuous polling, instead of using <Tab>\r\n   * Improve speed\r\n   * Improve syntax highlighting\r\n","3":"   * Complete python rewrite\r\n   * Add support for ncurses based applications\r\n   * Add continuous polling, instead of using <Tab>\r\n   * Improve speed\r\n   * Improve syntax highlighting\r\n","package":"conque_term_1.0.vba","4":"conque_term_1.0.vba","src_id":"12286","5":"12286","creation_date":"1265184696","6":"1265184696"},{"0":"2771","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Same as above.","3":"Same as above.","package":"conque_1.0.tar.gz","4":"conque_1.0.tar.gz","src_id":"12285","5":"12285","creation_date":"1265184599","6":"1265184599"},{"0":"2771","vim_version":"7.0","1":"7.0","script_version":"0.6","2":"0.6","version_comment":" * Fix GVim errors with non-english locale\r\n * No functional changes","3":" * Fix GVim errors with non-english locale\r\n * No functional changes","package":"conque_0.6.zip","4":"conque_0.6.zip","src_id":"11916","5":"11916","creation_date":"1261108977","6":"1261108977"},{"0":"2771","vim_version":"7.0","1":"7.0","script_version":"0.5","2":"0.5","version_comment":" * Various performance enhancements and bugfixes. * Rewritten escape sequence processing","3":" * Various performance enhancements and bugfixes. * Rewritten escape sequence processing","package":"conque_0.5.zip","4":"conque_0.5.zip","src_id":"11843","5":"11843","creation_date":"1259773179","6":"1259773179"},{"0":"2771","vim_version":"7.0","1":"7.0","script_version":"0.4","2":"0.4","version_comment":"    * Improved history and tab completion\r\n    * Fix escape sequence formatting and improve highlighting\r\n    * Send selected text to shell from any buffer\r\n    * Add special handling of \"vi\" and \"man\" commands\r\n    * Various bugfixes","3":"    * Improved history and tab completion\r\n    * Fix escape sequence formatting and improve highlighting\r\n    * Send selected text to shell from any buffer\r\n    * Add special handling of \"vi\" and \"man\" commands\r\n    * Various bugfixes","package":"conque_0.4.zip","4":"conque_0.4.zip","src_id":"11628","5":"11628","creation_date":"1256879467","6":"1256879467"},{"0":"2771","vim_version":"7.0","1":"7.0","script_version":"0.3","2":"0.3","version_comment":" * Apply escape sequence coloring to output, e.g. ls --color\r\n * Clean up syntax files for portability\r\n * Fix several Vim 7.1 bugs\r\n * Bugfixes for multiple shell buffers\r\n * Add experimental shell folding option","3":" * Apply escape sequence coloring to output, e.g. ls --color\r\n * Clean up syntax files for portability\r\n * Fix several Vim 7.1 bugs\r\n * Bugfixes for multiple shell buffers\r\n * Add experimental shell folding option","package":"conque_0.3.zip","4":"conque_0.3.zip","src_id":"11527","5":"11527","creation_date":"1255493821","6":"1255493821"},{"0":"2771","vim_version":"7.0","1":"7.0","script_version":"0.2","2":"0.2","version_comment":"* New subprocess management in Python instead of C\r\n* Stronger support in OS X and Windows\r\n* Faster\/less buggy tab completion\r\n* Support for multiple shell buffers","3":"* New subprocess management in Python instead of C\r\n* Stronger support in OS X and Windows\r\n* Faster\/less buggy tab completion\r\n* Support for multiple shell buffers","package":"Conque_0.2.zip","4":"Conque_0.2.zip","src_id":"11470","5":"11470","creation_date":"1254461954","6":"1254461954"},{"0":"2771","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"Conque_0.1.zip","4":"Conque_0.1.zip","src_id":"11311","5":"11311","creation_date":"1252009402","6":"1252009402"}]},"2770":{"script_id":"2770","0":"2770","script_name":"JumpInCode","1":"JumpInCode","script_type":"ftplugin","2":"ftplugin","summary":"more convenice way to use ctags and cscope in vim","3":"more convenice way to use ctags and cscope in vim","description":"\"EN\"\r\nctags and cscope plugin, more convenice way to use ctags and cscope in vim \r\n\r\nCommand:\r\n\\jc   Generate tags and cscope database from current directory\r\n\\jst   tags config window\r\n\\jsc  cscope.out config window\r\n                   \r\nRequirement:\r\nctags and cscope\r\nwin32: $VIM\\vim7*\\ctags.exe\r\nwin32: $VIM\\vim7*\\cscope.exe\r\n\r\nYou can download ctags.exe and cscope.exe from： http:\/\/code.google.com\/p\/easy-vim\/\r\n\r\nWho can tell me why I can't upload a new version?\r\n \r\nI don't know why I can't upload a new version, so I start a new branches at: http:\/\/www.vim.org\/scripts\/script.php?script_id=2943\r\n\r\n\"中文  ZH\"\r\n自动生成并使用ctags和cscope\r\n\r\n命令：\r\n\\jc    从当前目录生成tags和cscope.out \r\n\\jsc  cscope配置窗口\r\n\\jst   tags     配置窗口\r\n\r\n系统要求：\r\n预安装要求ctags和cscope: \r\nwin32: $VIM\\vim7*\\ctags.exe\r\nwin32: $VIM\\vim7*\\cscope.exe\r\nunix: ctags and cscope\r\n\r\nctags 和cscope Win32版： http:\/\/code.google.com\/p\/easy-vim\/\r\n\r\n不知道为什么这个页面的我不能够提交新的版本，所以我开了新的分支页面：http:\/\/www.vim.org\/scripts\/script.php?script_id=2943\r\n","4":"\"EN\"\r\nctags and cscope plugin, more convenice way to use ctags and cscope in vim \r\n\r\nCommand:\r\n\\jc   Generate tags and cscope database from current directory\r\n\\jst   tags config window\r\n\\jsc  cscope.out config window\r\n                   \r\nRequirement:\r\nctags and cscope\r\nwin32: $VIM\\vim7*\\ctags.exe\r\nwin32: $VIM\\vim7*\\cscope.exe\r\n\r\nYou can download ctags.exe and cscope.exe from： http:\/\/code.google.com\/p\/easy-vim\/\r\n\r\nWho can tell me why I can't upload a new version?\r\n \r\nI don't know why I can't upload a new version, so I start a new branches at: http:\/\/www.vim.org\/scripts\/script.php?script_id=2943\r\n\r\n\"中文  ZH\"\r\n自动生成并使用ctags和cscope\r\n\r\n命令：\r\n\\jc    从当前目录生成tags和cscope.out \r\n\\jsc  cscope配置窗口\r\n\\jst   tags     配置窗口\r\n\r\n系统要求：\r\n预安装要求ctags和cscope: \r\nwin32: $VIM\\vim7*\\ctags.exe\r\nwin32: $VIM\\vim7*\\cscope.exe\r\nunix: ctags and cscope\r\n\r\nctags 和cscope Win32版： http:\/\/code.google.com\/p\/easy-vim\/\r\n\r\n不知道为什么这个页面的我不能够提交新的版本，所以我开了新的分支页面：http:\/\/www.vim.org\/scripts\/script.php?script_id=2943\r\n","install_details":"Copy JumpInCode.vim to  ~\/.vim\/plugin\/","5":"Copy JumpInCode.vim to  ~\/.vim\/plugin\/","first_name":"zuopeng","6":"zuopeng","last_name":"chen","7":"chen","releases":[{"0":"2770","vim_version":"6.0","1":"6.0","script_version":"1.00","2":"1.00","version_comment":"修复了脚本中大多数问题，1.00稳定版本\r\nAlmost all bugs Fix in script, stable version 1.00","3":"修复了脚本中大多数问题，1.00稳定版本\r\nAlmost all bugs Fix in script, stable version 1.00","package":"JumpInCode.vim","4":"JumpInCode.vim","src_id":"11411","5":"11411","creation_date":"1253415401","6":"1253415401"}]},"2769":{"script_id":"2769","0":"2769","script_name":"pipe.vim","1":"pipe.vim","script_type":"utility","2":"utility","summary":"make vim part of a unix pipe and allow it to edit the pipe contents","3":"make vim part of a unix pipe and allow it to edit the pipe contents","description":"find | pipe.vim | nl\r\nfind | xargs pipe.vim\r\n\r\nSimplify invoking vim within Unix pipes for situations not covered by a simple *vi -*: I just too often forget to properly add all the required >\/dev\/tty <\/dev\/tty and similar in pipes and xargs commands.\r\n\r\nAll input is collected into a temporary file, prefixed with a small help text. Vim then edits this file with its IO being redirected to the tty. After editing the file is printed to stdout and serves as input for the next pipeline stage. \r\n\r\nSome more information can be found in the comments in the script itself.\r\n\r\nNote that the  name is just my way of not cluttering ~\/bin: pipe.vim is a perl script for use with pipes that is a helper for vim. It is NOT a vim macro.\r\n\r\nThe current version is available from:\r\nhttp:\/\/jakobi.github.com\/script-archive-doc\/\r\nhttp:\/\/github.com\/jakobi\/script-archive\/tree\/master\/vim\/","4":"find | pipe.vim | nl\r\nfind | xargs pipe.vim\r\n\r\nSimplify invoking vim within Unix pipes for situations not covered by a simple *vi -*: I just too often forget to properly add all the required >\/dev\/tty <\/dev\/tty and similar in pipes and xargs commands.\r\n\r\nAll input is collected into a temporary file, prefixed with a small help text. Vim then edits this file with its IO being redirected to the tty. After editing the file is printed to stdout and serves as input for the next pipeline stage. \r\n\r\nSome more information can be found in the comments in the script itself.\r\n\r\nNote that the  name is just my way of not cluttering ~\/bin: pipe.vim is a perl script for use with pipes that is a helper for vim. It is NOT a vim macro.\r\n\r\nThe current version is available from:\r\nhttp:\/\/jakobi.github.com\/script-archive-doc\/\r\nhttp:\/\/github.com\/jakobi\/script-archive\/tree\/master\/vim\/","install_details":"Unix: just place pipe.vim command in path.","5":"Unix: just place pipe.vim command in path.","first_name":"peter","6":"peter","last_name":"jakobi","7":"jakobi","releases":[{"0":"2769","vim_version":"6.0","1":"6.0","script_version":"0.1.2","2":"0.1.2","version_comment":"fixed security issue with <>","3":"fixed security issue with <>","package":"pipe.vim","4":"pipe.vim","src_id":"11507","5":"11507","creation_date":"1255216816","6":"1255216816"},{"0":"2769","vim_version":"6.0","1":"6.0","script_version":"0.1.1","2":"0.1.1","version_comment":"Initial upload","3":"Initial upload","package":"pipe.vim","4":"pipe.vim","src_id":"11302","5":"11302","creation_date":"1251832792","6":"1251832792"}]},"2768":{"script_id":"2768","0":"2768","script_name":"vimscript","1":"vimscript","script_type":"utility","2":"utility","summary":"use vim as an interpreter to write shell commands in vimscript like vimsh","3":"use vim as an interpreter to write shell commands in vimscript like vimsh","description":"Experiment to enable vim being invoked as a script interpreter, even when the vimscript block in question is used within a  unix pipe.\r\n\r\nThis is basically my take on the original vimscript#1069 vimsh from 2004,  sufficiently mangled until it finally did mostly work again with unix pipes and using vim 7.2 (excluding the g\/\/p issue, where the prints  get replicated all over the place - drop me a line if you have an idea). \r\n\r\nNote that vim still does some unnecessary screen redrawing if it is connected to a  tty, however I\r\nactually  managed  to run a vimscript even from a cronjob, much to  my surprise.\r\n\r\nFurther information and example vimscript blocks: see --help.\r\n\r\nI'll intend to keep this somewhat uptodate, at least until vim can be run non-interactively without the requirements for such a hack.\r\n\r\nThe current version is available from:\r\nhttp:\/\/jakobi.github.com\/script-archive-doc\/\r\nhttp:\/\/github.com\/jakobi\/script-archive\/tree\/master\/vim\/","4":"Experiment to enable vim being invoked as a script interpreter, even when the vimscript block in question is used within a  unix pipe.\r\n\r\nThis is basically my take on the original vimscript#1069 vimsh from 2004,  sufficiently mangled until it finally did mostly work again with unix pipes and using vim 7.2 (excluding the g\/\/p issue, where the prints  get replicated all over the place - drop me a line if you have an idea). \r\n\r\nNote that vim still does some unnecessary screen redrawing if it is connected to a  tty, however I\r\nactually  managed  to run a vimscript even from a cronjob, much to  my surprise.\r\n\r\nFurther information and example vimscript blocks: see --help.\r\n\r\nI'll intend to keep this somewhat uptodate, at least until vim can be run non-interactively without the requirements for such a hack.\r\n\r\nThe current version is available from:\r\nhttp:\/\/jakobi.github.com\/script-archive-doc\/\r\nhttp:\/\/github.com\/jakobi\/script-archive\/tree\/master\/vim\/","install_details":"Unix: just place the vimscript command in path.","5":"Unix: just place the vimscript command in path.","first_name":"peter","6":"peter","last_name":"jakobi","7":"jakobi","releases":[{"0":"2768","vim_version":"6.0","1":"6.0","script_version":"1.2","2":"1.2","version_comment":"Initial upload","3":"Initial upload","package":"vimscript","4":"vimscript","src_id":"11301","5":"11301","creation_date":"1251830879","6":"1251830879"}]},"2767":{"script_id":"2767","0":"2767","script_name":"emv","1":"emv","script_type":"utility","2":"utility","summary":"emv - external utilitity invoking vim for mass renaming","3":"emv - external utilitity invoking vim for mass renaming","description":"emv - editor mv - is a perl script for Unix to use the power of vim to mass rename files, with the renaming and logging done in perl, and vim used to edit the filenames with visual block commands, s\/\/\/g. In contrast to the original shell script, sorting and deleting lines is permitted.\r\n\r\nYou can specify a command of your own instead of the default \/bin\/mv. Also some special commands can be specified, which are run before any renames, including e.g. link target editing.\r\n\r\nHelp is available with --help and also in the editor buffer.\r\n\r\n[small fix: should now work with older perls as well]\r\n\r\nThe current version is available from: \r\nhttp:\/\/jakobi.github.com\/script-archive-doc\/\r\nhttp:\/\/github.com\/jakobi\/script-archive\/tree\/master\/cli.list.rename\/\r\n","4":"emv - editor mv - is a perl script for Unix to use the power of vim to mass rename files, with the renaming and logging done in perl, and vim used to edit the filenames with visual block commands, s\/\/\/g. In contrast to the original shell script, sorting and deleting lines is permitted.\r\n\r\nYou can specify a command of your own instead of the default \/bin\/mv. Also some special commands can be specified, which are run before any renames, including e.g. link target editing.\r\n\r\nHelp is available with --help and also in the editor buffer.\r\n\r\n[small fix: should now work with older perls as well]\r\n\r\nThe current version is available from: \r\nhttp:\/\/jakobi.github.com\/script-archive-doc\/\r\nhttp:\/\/github.com\/jakobi\/script-archive\/tree\/master\/cli.list.rename\/\r\n","install_details":"Copy emv to a directory in $PATH. Perl, one of bash, ksh93 (also ok: pdksh), and mv must be available on the system. Making it work with Cygwin should be possible.","5":"Copy emv to a directory in $PATH. Perl, one of bash, ksh93 (also ok: pdksh), and mv must be available on the system. Making it work with Cygwin should be possible.","first_name":"peter","6":"peter","last_name":"jakobi","7":"jakobi","releases":[{"0":"2767","vim_version":"6.0","1":"6.0","script_version":"2.00pj.4","2":"2.00pj.4","version_comment":"small fix to allow use of older perl versions","3":"small fix to allow use of older perl versions","package":"emv.tar.gz","4":"emv.tar.gz","src_id":"11371","5":"11371","creation_date":"1252868687","6":"1252868687"},{"0":"2767","vim_version":"6.0","1":"6.0","script_version":"2.0","2":"2.0","version_comment":"Initial upload","3":"Initial upload","package":"emv.tar.gz","4":"emv.tar.gz","src_id":"11300","5":"11300","creation_date":"1251829901","6":"1251829901"}]},"2766":{"script_id":"2766","0":"2766","script_name":"Join.vim","1":"Join.vim","script_type":"utility","2":"utility","summary":"Improved Algorithm for joining lines in large files","3":"Improved Algorithm for joining lines in large files","description":"ATTENTION: Vim 7.3 contains a bugfix, so this plugin isn't needed anymore!\r\n\r\nThis plugin tries to implement a different method for joining lines. This is,\r\nbecause the :join command from within vim suffers from a serious performance\r\nissue, if you are trying to join many lines (>1000).\r\n\r\nThis has been discussed on the vim development mailing list (see\r\nhttp:\/\/thread.gmane.org\/gmane.editors.vim.devel\/22065) as well as on the vim\r\nuser mailing list (see http:\/\/thread.gmane.org\/gmane.editors.vim\/80304).\r\n\r\nThere has also been a patch proposed, to improve the algorithm used by :join.\r\nThis patch is available at http:\/\/repo.or.cz\/w\/vim_extended.git, but this\r\nmeans, you'll have to build and patch your vim manually (you can't use it with\r\na prebuilt vim).\r\n\r\nUntil this patch is accepted and incorporated into mainline vim, this plugin\r\ntries to improve the joining algorithm by the method mentioned in the user\r\nmailinglist above. It basically works by breaking up the join algorithm into\r\nsmaller pieces and joining the smaller pieces together. This may have an\r\nimpact on memory usage, though.\r\n\r\n                                                              *Join-benchmark*\r\nFor reference I include some timings, joining many lines:\r\n\r\n      Lines joined      :%join      |      :%Join\r\n        25.000           3,305s     |      0,240s\r\n        50.000          13,667s     |      0,336s\r\n       100.000          64,140s     |      0,588s\r\n       200.000         331,410s     |      1,431s\r\n     1.000.000            -[1]      |      7,419s\r\n\r\n[1] benchmarking was aborted after 53 Minutes (after which only about 480.000\r\nlines have been joined).\r\n\r\nPlease also note, that using a substitute command does not prove to be faster.\r\nIt also suffers from the performance impact.\r\n\r\nAlso note, that really the best way to remove '\\n' on a file with millions\r\nof lines is using tr:\r\n\r\n~$ tr -d '\\n' <large_file >output_file\r\n\r\n2. Usage                                                          *Join-usage*\r\n\r\n:[range]J[oin][!]\r\n                        Join [range] lines.  Same as \"J\", except with [!]\r\n                        the join does not insert or delete any spaces.\r\n                        The default behavior is to join the current line\r\n                        with the line below it.\r\n\r\n:[range]J[oin][!] {count}\r\n                        Join {count} lines, starting with [range] (default:\r\n                        current line |cmdline-ranges|).  Same as \"J\", except\r\n                        with [!] the join does not insert or delete any\r\n                        spaces.\r\n\r\n\r\nYou should be able to use :Join as drop in replacement for :join. It behaves\r\nexactly like :join and understands it's syntax, with the exception of 1 point:\r\n\r\n1) :Join does not accept the use of [flags] as |:join| does.\r\n\r\nIf you want the J command to call :Join, you can use something like:\r\n:nmap J :Join<CR>\r\nto have J call :Join in normal mode and\r\n:vmap J :Join<CR>\r\n\r\n                                                            *Join-differences*\r\n3. Differences\r\n\r\nThis plugin has been made to make :Join and :join behave almost identically.\r\nIf there are further differences than those described at |Join-usage|, I am\r\ninterested at any bug describing exactly what went wrong, so I can fix this.\r\nPlease send any bug report to the mail address mentioned at the top of this\r\npage.\r\n\r\n","4":"ATTENTION: Vim 7.3 contains a bugfix, so this plugin isn't needed anymore!\r\n\r\nThis plugin tries to implement a different method for joining lines. This is,\r\nbecause the :join command from within vim suffers from a serious performance\r\nissue, if you are trying to join many lines (>1000).\r\n\r\nThis has been discussed on the vim development mailing list (see\r\nhttp:\/\/thread.gmane.org\/gmane.editors.vim.devel\/22065) as well as on the vim\r\nuser mailing list (see http:\/\/thread.gmane.org\/gmane.editors.vim\/80304).\r\n\r\nThere has also been a patch proposed, to improve the algorithm used by :join.\r\nThis patch is available at http:\/\/repo.or.cz\/w\/vim_extended.git, but this\r\nmeans, you'll have to build and patch your vim manually (you can't use it with\r\na prebuilt vim).\r\n\r\nUntil this patch is accepted and incorporated into mainline vim, this plugin\r\ntries to improve the joining algorithm by the method mentioned in the user\r\nmailinglist above. It basically works by breaking up the join algorithm into\r\nsmaller pieces and joining the smaller pieces together. This may have an\r\nimpact on memory usage, though.\r\n\r\n                                                              *Join-benchmark*\r\nFor reference I include some timings, joining many lines:\r\n\r\n      Lines joined      :%join      |      :%Join\r\n        25.000           3,305s     |      0,240s\r\n        50.000          13,667s     |      0,336s\r\n       100.000          64,140s     |      0,588s\r\n       200.000         331,410s     |      1,431s\r\n     1.000.000            -[1]      |      7,419s\r\n\r\n[1] benchmarking was aborted after 53 Minutes (after which only about 480.000\r\nlines have been joined).\r\n\r\nPlease also note, that using a substitute command does not prove to be faster.\r\nIt also suffers from the performance impact.\r\n\r\nAlso note, that really the best way to remove '\\n' on a file with millions\r\nof lines is using tr:\r\n\r\n~$ tr -d '\\n' <large_file >output_file\r\n\r\n2. Usage                                                          *Join-usage*\r\n\r\n:[range]J[oin][!]\r\n                        Join [range] lines.  Same as \"J\", except with [!]\r\n                        the join does not insert or delete any spaces.\r\n                        The default behavior is to join the current line\r\n                        with the line below it.\r\n\r\n:[range]J[oin][!] {count}\r\n                        Join {count} lines, starting with [range] (default:\r\n                        current line |cmdline-ranges|).  Same as \"J\", except\r\n                        with [!] the join does not insert or delete any\r\n                        spaces.\r\n\r\n\r\nYou should be able to use :Join as drop in replacement for :join. It behaves\r\nexactly like :join and understands it's syntax, with the exception of 1 point:\r\n\r\n1) :Join does not accept the use of [flags] as |:join| does.\r\n\r\nIf you want the J command to call :Join, you can use something like:\r\n:nmap J :Join<CR>\r\nto have J call :Join in normal mode and\r\n:vmap J :Join<CR>\r\n\r\n                                                            *Join-differences*\r\n3. Differences\r\n\r\nThis plugin has been made to make :Join and :join behave almost identically.\r\nIf there are further differences than those described at |Join-usage|, I am\r\ninterested at any bug describing exactly what went wrong, so I can fix this.\r\nPlease send any bug report to the mail address mentioned at the top of this\r\npage.\r\n\r\n","install_details":"simply source the Join.vba file:\r\nvim Join.vba\r\n:so %","5":"simply source the Join.vba file:\r\nvim Join.vba\r\n:so %","first_name":"Christian","6":"Christian","last_name":"Brabandt","7":"Brabandt","releases":[{"0":"2766","vim_version":"7.0","1":"7.0","script_version":"2.4","2":"2.4","version_comment":"- Plugin is now autoloadable\r\n- public repository at http:\/\/github.com\/chrisbra\/Join","3":"- Plugin is now autoloadable\r\n- public repository at http:\/\/github.com\/chrisbra\/Join","package":"Join.vba","4":"Join.vba","src_id":"12870","5":"12870","creation_date":"1271708809","6":"1271708809"},{"0":"2766","vim_version":"7.0","1":"7.0","script_version":"2.2","2":"2.2","version_comment":"fixed Copyright, which included wrong Plugin name","3":"fixed Copyright, which included wrong Plugin name","package":"Join.vba","4":"Join.vba","src_id":"11462","5":"11462","creation_date":"1254376473","6":"1254376473"},{"0":"2766","vim_version":"7.0","1":"7.0","script_version":"2.1","2":"2.1","version_comment":"fixed Documenation\r\nenabled GetLatestVimScripts","3":"fixed Documenation\r\nenabled GetLatestVimScripts","package":"Join.vba","4":"Join.vba","src_id":"11303","5":"11303","creation_date":"1251837403","6":"1251837403"},{"0":"2766","vim_version":"7.0","1":"7.0","script_version":"2","2":"2","version_comment":"Initial upload","3":"Initial upload","package":"Join.vba","4":"Join.vba","src_id":"11297","5":"11297","creation_date":"1251759025","6":"1251759025"}]},"2765":{"script_id":"2765","0":"2765","script_name":"Better Javascript Indentation","1":"Better Javascript Indentation","script_type":"indent","2":"indent","summary":"Vastly improved javascript indentation","3":"Vastly improved javascript indentation","description":"This is based off of the indentation script for ruby which is well written and fast. It is nearly perfect but will sometimes miss edge cases. It usually recovers those errors at the end of a block though, so overall even very long files will be largely correct. \r\n\r\nPlease fork this project at http:\/\/github.com\/pangloss\/vim-javascript to help make it even better.\r\n\r\nThis script includes Yi Zhao\\'s javascript syntax script v 0.7.7","4":"This is based off of the indentation script for ruby which is well written and fast. It is nearly perfect but will sometimes miss edge cases. It usually recovers those errors at the end of a block though, so overall even very long files will be largely correct. \r\n\r\nPlease fork this project at http:\/\/github.com\/pangloss\/vim-javascript to help make it even better.\r\n\r\nThis script includes Yi Zhao\\'s javascript syntax script v 0.7.7","install_details":"Unzip the file in your .vim directory.\r\n\r\nOr to be sure you have the latest version:\r\ngit clone git:\/\/github.com\/pangloss\/vim-javascript.git\r\ncd vim-javascript\r\nrake install","5":"Unzip the file in your .vim directory.\r\n\r\nOr to be sure you have the latest version:\r\ngit clone git:\/\/github.com\/pangloss\/vim-javascript.git\r\ncd vim-javascript\r\nrake install","first_name":"Darrick","6":"Darrick","last_name":"Wiebe","7":"Wiebe","releases":[{"0":"2765","vim_version":"6.0","1":"6.0","script_version":"1.0.0","2":"1.0.0","version_comment":"Initial upload","3":"Initial upload","package":"javascript.zip","4":"javascript.zip","src_id":"11296","5":"11296","creation_date":"1251746006","6":"1251746006"}]},"2764":{"script_id":"2764","0":"2764","script_name":"dull","1":"dull","script_type":"color scheme","2":"color scheme","summary":"a very low saturation colour scheme","3":"a very low saturation colour scheme","description":"This is a very low saturation version based on default and torte colour scheme.  It looks only little different from syntax turned off, and is good for long-time works.\r\n\r\nThis colour scheme can work for both 'light' and 'black' backgrounds.  Use \"set background=...\" to switch the different styles.\r\n\r\nBasically, it is designed for GUI, but it can fallback to a colourful mode in low-colour terminals.\r\n","4":"This is a very low saturation version based on default and torte colour scheme.  It looks only little different from syntax turned off, and is good for long-time works.\r\n\r\nThis colour scheme can work for both 'light' and 'black' backgrounds.  Use \"set background=...\" to switch the different styles.\r\n\r\nBasically, it is designed for GUI, but it can fallback to a colourful mode in low-colour terminals.\r\n","install_details":"Copy the dull.vim to $HOME\/.vim\/color\/ directory (or %HOME%\\vimfiles\\color\\ on MS-Windows)\r\n","5":"Copy the dull.vim to $HOME\/.vim\/color\/ directory (or %HOME%\\vimfiles\\color\\ on MS-Windows)\r\n","first_name":"Chun-Kin","6":"Chun-Kin","last_name":"Lee","7":"Lee","releases":[{"0":"2764","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"dull.vim","4":"dull.vim","src_id":"11294","5":"11294","creation_date":"1251687569","6":"1251687569"}]},"2763":{"script_id":"2763","0":"2763","script_name":"falcon.vim","1":"falcon.vim","script_type":"ftplugin","2":"ftplugin","summary":"Filetype plugin script for Falcon","3":"Filetype plugin script for Falcon","description":"This is the actual filetype plugin script for the falcon programming language.\r\n\r\nSyntax:  vimscript #2745 \r\nIndent:    vimscript #2752 \r\nFtplugin: vimscript #2762 \r\n\r\nFor the latest version check: \r\nhttp:\/\/github.com\/steveno\/falconpl-vim\r\n","4":"This is the actual filetype plugin script for the falcon programming language.\r\n\r\nSyntax:  vimscript #2745 \r\nIndent:    vimscript #2752 \r\nFtplugin: vimscript #2762 \r\n\r\nFor the latest version check: \r\nhttp:\/\/github.com\/steveno\/falconpl-vim\r\n","install_details":"Place in $VIM\/vimfiles\/ftplugin directory.","5":"Place in $VIM\/vimfiles\/ftplugin directory.","first_name":"Steven","6":"Steven","last_name":"Oliver","7":"Oliver","releases":[{"0":"2763","vim_version":"7.0","1":"7.0","script_version":"0.02","2":"0.02","version_comment":"Complete rewrite. Lots added.","3":"Complete rewrite. Lots added.","package":"falcon.vim","4":"falcon.vim","src_id":"13824","5":"13824","creation_date":"1284464717","6":"1284464717"},{"0":"2763","vim_version":"7.0","1":"7.0","script_version":"0.01","2":"0.01","version_comment":"Initial upload","3":"Initial upload","package":"falcon.vim","4":"falcon.vim","src_id":"11293","5":"11293","creation_date":"1251654368","6":"1251654368"}]},"2762":{"script_id":"2762","0":"2762","script_name":"falcon.vim","1":"falcon.vim","script_type":"ftplugin","2":"ftplugin","summary":"Filetype detection script","3":"Filetype detection script","description":"This file allow vim to detect your falcon source code.\r\n\r\nSyntax:   vimscript #2745 \r\nIndent:    vimscript #2752 \r\nFtdetect: vimscript #2763 \r\n\r\nFor the latest version check: \r\nhttp:\/\/github.com\/steveno\/falconpl-vim","4":"This file allow vim to detect your falcon source code.\r\n\r\nSyntax:   vimscript #2745 \r\nIndent:    vimscript #2752 \r\nFtdetect: vimscript #2763 \r\n\r\nFor the latest version check: \r\nhttp:\/\/github.com\/steveno\/falconpl-vim","install_details":"Place in $VIM\/vimfiles\/ftdetect","5":"Place in $VIM\/vimfiles\/ftdetect","first_name":"Steven","6":"Steven","last_name":"Oliver","7":"Oliver","releases":[{"0":"2762","vim_version":"7.0","1":"7.0","script_version":"0.01","2":"0.01","version_comment":"Initial upload","3":"Initial upload","package":"falcon.vim","4":"falcon.vim","src_id":"11292","5":"11292","creation_date":"1251654271","6":"1251654271"}]},"2761":{"script_id":"2761","0":"2761","script_name":"qtmplsel.vim","1":"qtmplsel.vim","script_type":"utility","2":"utility","summary":"quick template selector with expression expansion","3":"quick template selector with expression expansion","description":"This plugin enables you to select a template on creating a new file.\r\nTemplates are typically placed in ~\/.vim\/template .\r\nOn creating a file, corresponding templates, if any, are listed up. You\r\ncan select one of them by k(up)\/j(down). Press Enter to load the selected\r\ntemplate, or press 'q' to load no templates.\r\nYou can cancel the insertion of selected template by pressing 'u'(undo).\r\n\r\nThere is an optional global varialbe:\r\n  g:qts_templatedir : specifies the template dir\r\n                      (default: ~\/.vim\/template)\r\n\r\nTemplate search rules:\r\n  1) by filetype\r\n    filetype=python -> ~\/.vim\/template\/python_*\r\n  2) by suffix\r\n    *.cpp           -> ~\/.vim\/template\/*.cpp\r\n  3) by filename\r\n    Makefile        -> ~\/.vim\/template\/Makefile_*\r\n\r\nNote that especially in case 3, 'Makefile_' is a legal template name\r\nbut 'Makefile' is not even if you have no other template file.\r\n\r\nNew in 1.1.0 - expression expansion:\r\n  String surrounded by '@{@' '@}@' in the template file is regarded as a vim\r\n  expression, and will be eval()ed on loading.\r\n  e.g.)\r\n    @{@expand('%:t')@}@          ->  newfile.py\r\n    @{@strftime('%Y-%m-%d')@}@   ->  2009-08-30","4":"This plugin enables you to select a template on creating a new file.\r\nTemplates are typically placed in ~\/.vim\/template .\r\nOn creating a file, corresponding templates, if any, are listed up. You\r\ncan select one of them by k(up)\/j(down). Press Enter to load the selected\r\ntemplate, or press 'q' to load no templates.\r\nYou can cancel the insertion of selected template by pressing 'u'(undo).\r\n\r\nThere is an optional global varialbe:\r\n  g:qts_templatedir : specifies the template dir\r\n                      (default: ~\/.vim\/template)\r\n\r\nTemplate search rules:\r\n  1) by filetype\r\n    filetype=python -> ~\/.vim\/template\/python_*\r\n  2) by suffix\r\n    *.cpp           -> ~\/.vim\/template\/*.cpp\r\n  3) by filename\r\n    Makefile        -> ~\/.vim\/template\/Makefile_*\r\n\r\nNote that especially in case 3, 'Makefile_' is a legal template name\r\nbut 'Makefile' is not even if you have no other template file.\r\n\r\nNew in 1.1.0 - expression expansion:\r\n  String surrounded by '@{@' '@}@' in the template file is regarded as a vim\r\n  expression, and will be eval()ed on loading.\r\n  e.g.)\r\n    @{@expand('%:t')@}@          ->  newfile.py\r\n    @{@strftime('%Y-%m-%d')@}@   ->  2009-08-30","install_details":"Place this file in \/usr\/share\/vim\/vim*\/plugin or ~\/.vim\/plugin\/","5":"Place this file in \/usr\/share\/vim\/vim*\/plugin or ~\/.vim\/plugin\/","first_name":"Takahiro","6":"Takahiro","last_name":"SUZUKI","7":"SUZUKI","releases":[{"0":"2761","vim_version":"7.3","1":"7.3","script_version":"1.1.2","2":"1.1.2","version_comment":"bug fix, show the template list immediately.","3":"bug fix, show the template list immediately.","package":"qtmplsel.vim","4":"qtmplsel.vim","src_id":"18110","5":"18110","creation_date":"1339314292","6":"1339314292"},{"0":"2761","vim_version":"7.0","1":"7.0","script_version":"1.1.1","2":"1.1.1","version_comment":"up and down arrow keys as well as j\/k, quit on <Esc>","3":"up and down arrow keys as well as j\/k, quit on <Esc>","package":"qtmplsel.vim","4":"qtmplsel.vim","src_id":"12046","5":"12046","creation_date":"1263101784","6":"1263101784"},{"0":"2761","vim_version":"7.0","1":"7.0","script_version":"1.1.0","2":"1.1.0","version_comment":"expression expansion (@{@vim-expression@}@)","3":"expression expansion (@{@vim-expression@}@)","package":"qtmplsel.vim","4":"qtmplsel.vim","src_id":"11334","5":"11334","creation_date":"1252298250","6":"1252298250"},{"0":"2761","vim_version":"7.0","1":"7.0","script_version":"1.0.0","2":"1.0.0","version_comment":"Initial upload","3":"Initial upload","package":"qtmplsel.vim","4":"qtmplsel.vim","src_id":"11286","5":"11286","creation_date":"1251526360","6":"1251526360"}]},"2760":{"script_id":"2760","0":"2760","script_name":"Tortoise","1":"Tortoise","script_type":"utility","2":"utility","summary":"Automate TortoiseSVN from vim","3":"Automate TortoiseSVN from vim","description":"This lightweight plugin provides a Vim command-line interface to the TortoiseSVN, utilizing the automation commands provided by TortoiseProc.exe. \r\n\r\nIt also simplifies the interface such that the commands are shorter to type, and  you can make use of the Vim command-line completion on both the options as well as command names to make entering quicker. \r\n\r\nTortoiseSVN is only supported on windows, and so this plugin will work only on windows. I have been using this plugin for over a couple of years now, and refactored it recently to be more robust such that I can release it to the public. I currently use Vim 7.2 and TortoiseSVN 1.6.2 and the plugin works very well. It might work equally well on other versions, but YMMV.\r\n\r\nHere is the complete description from the script header:\r\nDescription:\r\n  The plugin essentially works as a wrapper on top of the TortoiseProc and\r\n  provides the following functionality:\r\n    - Simplify command-line syntax that TortoiseProc supports.\r\n      - Avoid specifying \/command: and \/path: prefixes and use less ambiguous\r\n        \"-\" as prefix instead of \"\/\" (customizable).\r\n      - Allow multiple paths as space separated arguments, instead of having\r\n        to use the less convenient \"*\" as the separator.\r\n    - Add command-line completion to make it easier to type the commands.\r\n    - Allow filename special characters on command-line, such as % and #10.\r\n    - Make sure the paths are acceptable to TortoiseProc.\r\n      - Make sure paths have back-slashes, even if 'shellslash' is currently\r\n        set.\r\n      - Convert relative paths to absolute paths.\r\n    - Support some aliases to the commands, such as submit->commit,\r\n      filelog->log, browse->repobrowser, status->repostatus\r\n                                                                                  \r\nUsage:\r\n  General Syntax:\r\n    SVN [-option[:value] ...] <command> [-option[:value] ...] [path ...]\r\n                                                                                  \r\n  Ex:\r\n    SVN -startrev:11000 -endrev:10000 log %\r\n    SVN -log:just\\ testing commit % # #10\r\n    SVN update .\r\n    SVN diff % ..\/other\/%\r\n                                                                                  \r\nCompletion:\r\n  Use command-line completion for <command> name, options and <paths>. The\r\n  completion also works for |cmdline-special| characters.\r\n                                                                                  \r\n  For command names and their options refer to:\r\n                                                                                  \r\n    http:\/\/tortoisesvn.net\/docs\/release\/TortoiseSVN_en\/tsvn-automation.html\r\n                                                                                  \r\nSettings:\r\n- Set g:Tortoise_Path to the location of TortoiseProc.exe (use dos short\r\n  names if the path has spaces).\r\n                                                                                  \r\n- You may use g:Tortoise_CloseOnEnd_Arg to set the \"closeonend\" value.\r\n  Defaults to \"2\".\r\n                                                                                  \r\n- You may set g:Tortoise_UseAbsolutePaths to 1 if you want to pass absolute\r\n  paths to TortoiseSVN.\r\n                                                                                  \r\n- Set g:Tortoise_OptionPrefix to \"\/\" if you prefer the native TortoiseProc\r\n  command syntax.\r\n                                                                                  \r\n- Set g:Tortoise_OptionCompleteSuffixColon to \"0\" to avoid seeing \":\" at the\r\n  end of options.\r\n","4":"This lightweight plugin provides a Vim command-line interface to the TortoiseSVN, utilizing the automation commands provided by TortoiseProc.exe. \r\n\r\nIt also simplifies the interface such that the commands are shorter to type, and  you can make use of the Vim command-line completion on both the options as well as command names to make entering quicker. \r\n\r\nTortoiseSVN is only supported on windows, and so this plugin will work only on windows. I have been using this plugin for over a couple of years now, and refactored it recently to be more robust such that I can release it to the public. I currently use Vim 7.2 and TortoiseSVN 1.6.2 and the plugin works very well. It might work equally well on other versions, but YMMV.\r\n\r\nHere is the complete description from the script header:\r\nDescription:\r\n  The plugin essentially works as a wrapper on top of the TortoiseProc and\r\n  provides the following functionality:\r\n    - Simplify command-line syntax that TortoiseProc supports.\r\n      - Avoid specifying \/command: and \/path: prefixes and use less ambiguous\r\n        \"-\" as prefix instead of \"\/\" (customizable).\r\n      - Allow multiple paths as space separated arguments, instead of having\r\n        to use the less convenient \"*\" as the separator.\r\n    - Add command-line completion to make it easier to type the commands.\r\n    - Allow filename special characters on command-line, such as % and #10.\r\n    - Make sure the paths are acceptable to TortoiseProc.\r\n      - Make sure paths have back-slashes, even if 'shellslash' is currently\r\n        set.\r\n      - Convert relative paths to absolute paths.\r\n    - Support some aliases to the commands, such as submit->commit,\r\n      filelog->log, browse->repobrowser, status->repostatus\r\n                                                                                  \r\nUsage:\r\n  General Syntax:\r\n    SVN [-option[:value] ...] <command> [-option[:value] ...] [path ...]\r\n                                                                                  \r\n  Ex:\r\n    SVN -startrev:11000 -endrev:10000 log %\r\n    SVN -log:just\\ testing commit % # #10\r\n    SVN update .\r\n    SVN diff % ..\/other\/%\r\n                                                                                  \r\nCompletion:\r\n  Use command-line completion for <command> name, options and <paths>. The\r\n  completion also works for |cmdline-special| characters.\r\n                                                                                  \r\n  For command names and their options refer to:\r\n                                                                                  \r\n    http:\/\/tortoisesvn.net\/docs\/release\/TortoiseSVN_en\/tsvn-automation.html\r\n                                                                                  \r\nSettings:\r\n- Set g:Tortoise_Path to the location of TortoiseProc.exe (use dos short\r\n  names if the path has spaces).\r\n                                                                                  \r\n- You may use g:Tortoise_CloseOnEnd_Arg to set the \"closeonend\" value.\r\n  Defaults to \"2\".\r\n                                                                                  \r\n- You may set g:Tortoise_UseAbsolutePaths to 1 if you want to pass absolute\r\n  paths to TortoiseSVN.\r\n                                                                                  \r\n- Set g:Tortoise_OptionPrefix to \"\/\" if you prefer the native TortoiseProc\r\n  command syntax.\r\n                                                                                  \r\n- Set g:Tortoise_OptionCompleteSuffixColon to \"0\" to avoid seeing \":\" at the\r\n  end of options.\r\n","install_details":"  - Expand the archive into your vim runtime path (~\/.vim or ~\/vimfiles).\r\n  - Make sure to install genutils plugin as well (vimscript #197).\r\n  - Also install TortoiseSVN and assign its path to g:Tortoise_Path setting in vimrc.\r\n","5":"  - Expand the archive into your vim runtime path (~\/.vim or ~\/vimfiles).\r\n  - Make sure to install genutils plugin as well (vimscript #197).\r\n  - Also install TortoiseSVN and assign its path to g:Tortoise_Path setting in vimrc.\r\n","first_name":"Hari Krishna","6":"Hari Krishna","last_name":"Dara","7":"Dara","releases":[{"0":"2760","vim_version":"7.2","1":"7.2","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"tortoise-1.0.zip","4":"tortoise-1.0.zip","src_id":"11285","5":"11285","creation_date":"1251512246","6":"1251512246"}]},"2759":{"script_id":"2759","0":"2759","script_name":"Quich Filter","1":"Quich Filter","script_type":"utility","2":"utility","summary":"Quickly filter all matches of a string, browse the list, and jump back quickly.","3":"Quickly filter all matches of a string, browse the list, and jump back quickly.","description":"This plug-in provides filtering\/search functionality to Vim, similar to e.g.\r\nPSPad. This plug-in offers a number of additional features:\r\n\r\n- Further filtering\/searching inside the filtered results.\r\n- Syntaxt highlighting in the filtered results.\r\n- Show context line around found matches. You can dynamically change the number\r\n  of lines.\r\n- Easy jumping to and from the filter buffers, including auto-follow.\r\n\r\nIn addition, the new 2.0 version (currently work in progress!) offers:\r\n- Fine-tuning of results (AND, OR and AND-NOT)\r\n- Showing context lines above, below or above and below the matches.\r\n- Show the raw results (no line numbering) for easy yanking.\r\n\r\nThe search results are presented in a separate buffer (and window) and the\r\nscript offers a number of convenience key-mappings to navigate from one result\r\nto the next.\r\n\r\nThere are no default mapping to start the plug-in, but setting this up can be\r\nas easy as cut-n-paste from the help file. In the results buffer a number of\r\nmappings are set up, please refer to the help file for an overview in 2.0. For\r\nolder releases, press ?. Since ? is a useful VIM command it's no longer mapped\r\nin 1.0.7. In a results window, type \":call ShowHelp()\" and press enter. \r\n","4":"This plug-in provides filtering\/search functionality to Vim, similar to e.g.\r\nPSPad. This plug-in offers a number of additional features:\r\n\r\n- Further filtering\/searching inside the filtered results.\r\n- Syntaxt highlighting in the filtered results.\r\n- Show context line around found matches. You can dynamically change the number\r\n  of lines.\r\n- Easy jumping to and from the filter buffers, including auto-follow.\r\n\r\nIn addition, the new 2.0 version (currently work in progress!) offers:\r\n- Fine-tuning of results (AND, OR and AND-NOT)\r\n- Showing context lines above, below or above and below the matches.\r\n- Show the raw results (no line numbering) for easy yanking.\r\n\r\nThe search results are presented in a separate buffer (and window) and the\r\nscript offers a number of convenience key-mappings to navigate from one result\r\nto the next.\r\n\r\nThere are no default mapping to start the plug-in, but setting this up can be\r\nas easy as cut-n-paste from the help file. In the results buffer a number of\r\nmappings are set up, please refer to the help file for an overview in 2.0. For\r\nolder releases, press ?. Since ? is a useful VIM command it's no longer mapped\r\nin 1.0.7. In a results window, type \":call ShowHelp()\" and press enter. \r\n","install_details":"Drop this file in your plug-in directory, e.g. $HOME\/vimfiles\/plugin or\r\nC:\\Program Fles\\vim\\vimfiles\\plugin, and it should be automatically sourced\r\nduring start-up.","5":"Drop this file in your plug-in directory, e.g. $HOME\/vimfiles\/plugin or\r\nC:\\Program Fles\\vim\\vimfiles\\plugin, and it should be automatically sourced\r\nduring start-up.","first_name":"Niels","6":"Niels","last_name":"Aan de Brugh","7":"Aan de Brugh","releases":[{"0":"2759","vim_version":"7.0","1":"7.0","script_version":"2.0beta1","2":"2.0beta1","version_comment":"I probably made a mistake during benchmarking this summer because after some more testing I found out the latest alpha version was about 10 times slower than 1.0.6.1 on certain files. Benchmarking was done on a US dictionary file, so lots of small lines.\r\n\r\n1.0.7 has the same problem (it uses the same sorting routine as 2.0alpha3, otherwise it's identical to its predecessor).\r\n\r\nThis version brings back the sorting code of 1.0.6, and should be much faster on bigger files. Let me know if you see performance regression, and be sure to tell me what type of files you're filtering.\r\n\r\nThanks to Yeung for bringing this to my attention.","3":"I probably made a mistake during benchmarking this summer because after some more testing I found out the latest alpha version was about 10 times slower than 1.0.6.1 on certain files. Benchmarking was done on a US dictionary file, so lots of small lines.\r\n\r\n1.0.7 has the same problem (it uses the same sorting routine as 2.0alpha3, otherwise it's identical to its predecessor).\r\n\r\nThis version brings back the sorting code of 1.0.6, and should be much faster on bigger files. Let me know if you see performance regression, and be sure to tell me what type of files you're filtering.\r\n\r\nThanks to Yeung for bringing this to my attention.","package":"filtering2.zip","4":"filtering2.zip","src_id":"17103","5":"17103","creation_date":"1324582694","6":"1324582694"},{"0":"2759","vim_version":"7.0","1":"7.0","script_version":"2.0alpha3","2":"2.0alpha3","version_comment":"Bugfixes, bugfixes.\r\nProvide some nicer user feedback (call done() after each method chain). Show setting value when toggling. Provide functionality to just count results (split up some methods for more control).\r\nThe help file is not yet updated, but this version should definitely be more usable than the previous one. Still alpha though!","3":"Bugfixes, bugfixes.\r\nProvide some nicer user feedback (call done() after each method chain). Show setting value when toggling. Provide functionality to just count results (split up some methods for more control).\r\nThe help file is not yet updated, but this version should definitely be more usable than the previous one. Still alpha though!","package":"filtering2.zip","4":"filtering2.zip","src_id":"16249","5":"16249","creation_date":"1313182589","6":"1313182589"},{"0":"2759","vim_version":"7.0","1":"7.0","script_version":"2.0alpha2","2":"2.0alpha2","version_comment":"Bugfixes, mainly for using extra patterns.","3":"Bugfixes, mainly for using extra patterns.","package":"filtering2.zip","4":"filtering2.zip","src_id":"16239","5":"16239","creation_date":"1313093172","6":"1313093172"},{"0":"2759","vim_version":"7.0","1":"7.0","script_version":"2.0alpha2","2":"2.0alpha2","version_comment":"Unix line endings.","3":"Unix line endings.","package":"filtering2.zip","4":"filtering2.zip","src_id":"16096","5":"16096","creation_date":"1311070865","6":"1311070865"},{"0":"2759","vim_version":"7.0","1":"7.0","script_version":"2.0alpha","2":"2.0alpha","version_comment":"An alpha release of a complete redesign of the plug-in code. It should be much faster than 1.0.6.1, and about as fast as the 1.0.7 version that I just uploaded.\r\n\r\nThe API of this plug-in is completely different than before.\r\n\r\nConsult the help file in the ZIP to see the details.\r\n\r\nThis is very much a work in progress! I use my own plug-in mainly for work, and since it's summer I haven't had the chance for some serious dogfooding. In summary I added some functionality that I was missing in the first version, and existing functionality should be more accessible.\r\n\r\nSome highlights:\r\n\r\n* More fine-grained filtering: gather results that match one or more alternatives (OR-semantics), if these lines also match zero or more other terms (AND-semantics), until they match zero or more even other terms (AND-NOT).\r\nThere's no real need any more to filter the results again, you can just use AND.\r\nI think weeding out results using AND-NOT can be very useful too, for example you can quickly grep for all logging of a certain component, and quickly remove debug-level logging. This was not possible before (without using fragile tricks as I've been doing myself).\r\n\r\n* Switch between highlighted line-numbered view (the default) and a \"raw\" view where you just see the plain text results without any line numbering. (Note that this disable pretty much all of the functionality of the plug-in as well.)\r\nNice for yanking text, for example when writing a problem report where the original line numbers are irrelevant.\r\n\r\n* Search for an extra pattern (existing functionality), but not just N lines ahead. You can now also specify a stop-pattern. So you can now look for lines matching M if they match pattern E(xtra) before pattern S(top). The default stop pattern is the empty line.\r\nI think this will be useful when filtering protocol log files that contain decoded messages separated by a blank line.\r\n","3":"An alpha release of a complete redesign of the plug-in code. It should be much faster than 1.0.6.1, and about as fast as the 1.0.7 version that I just uploaded.\r\n\r\nThe API of this plug-in is completely different than before.\r\n\r\nConsult the help file in the ZIP to see the details.\r\n\r\nThis is very much a work in progress! I use my own plug-in mainly for work, and since it's summer I haven't had the chance for some serious dogfooding. In summary I added some functionality that I was missing in the first version, and existing functionality should be more accessible.\r\n\r\nSome highlights:\r\n\r\n* More fine-grained filtering: gather results that match one or more alternatives (OR-semantics), if these lines also match zero or more other terms (AND-semantics), until they match zero or more even other terms (AND-NOT).\r\nThere's no real need any more to filter the results again, you can just use AND.\r\nI think weeding out results using AND-NOT can be very useful too, for example you can quickly grep for all logging of a certain component, and quickly remove debug-level logging. This was not possible before (without using fragile tricks as I've been doing myself).\r\n\r\n* Switch between highlighted line-numbered view (the default) and a \"raw\" view where you just see the plain text results without any line numbering. (Note that this disable pretty much all of the functionality of the plug-in as well.)\r\nNice for yanking text, for example when writing a problem report where the original line numbers are irrelevant.\r\n\r\n* Search for an extra pattern (existing functionality), but not just N lines ahead. You can now also specify a stop-pattern. So you can now look for lines matching M if they match pattern E(xtra) before pattern S(top). The default stop pattern is the empty line.\r\nI think this will be useful when filtering protocol log files that contain decoded messages separated by a blank line.\r\n","package":"filtering2.zip","4":"filtering2.zip","src_id":"16093","5":"16093","creation_date":"1311024208","6":"1311024208"},{"0":"2759","vim_version":"7.0","1":"7.0","script_version":"1.0.7","2":"1.0.7","version_comment":"A significant speed-up that I copied from the new 2.0 alpha source after doing some profiling on that code.\r\n\r\nAlso ? is no longer mapped to help, since it's used for searching (doh!).","3":"A significant speed-up that I copied from the new 2.0 alpha source after doing some profiling on that code.\r\n\r\nAlso ? is no longer mapped to help, since it's used for searching (doh!).","package":"filtering.vim","4":"filtering.vim","src_id":"16092","5":"16092","creation_date":"1311023261","6":"1311023261"},{"0":"2759","vim_version":"7.0","1":"7.0","script_version":"1.0.6.1","2":"1.0.6.1","version_comment":"Fixed strange resize behavior when refreshing results, and made resizing more robust for when search and\/or original buffer are hidden.","3":"Fixed strange resize behavior when refreshing results, and made resizing more robust for when search and\/or original buffer are hidden.","package":"filtering.vim","4":"filtering.vim","src_id":"13996","5":"13996","creation_date":"1286306084","6":"1286306084"},{"0":"2759","vim_version":"7.0","1":"7.0","script_version":"1.0.6","2":"1.0.6","version_comment":"This version features:\r\n\r\n- Defaults for configuration have been moved to global variables so you specify them without changing the plug-in source.\r\n- Filter a match only if it followed by another match (within a given number of lines). For example, aap|5|noot will match  \"aap\",  but only if it's followed by \"noot\" within 5 lines.\r\n- Showing all context lines up to the second match can be switched on\/off (regardless of the number of context lines showing already).\r\n- The window size is by default no more than the minimum of the number of matches and half the window size. The maximum can also be configured (absolute or as a percentage of the original window size).\r\n\r\nPress ? in a filter window to show all default binding.\r\n\r\nI should probably write up some documentation for this some day. For now please refer to the topmost section of the source.","3":"This version features:\r\n\r\n- Defaults for configuration have been moved to global variables so you specify them without changing the plug-in source.\r\n- Filter a match only if it followed by another match (within a given number of lines). For example, aap|5|noot will match  \"aap\",  but only if it's followed by \"noot\" within 5 lines.\r\n- Showing all context lines up to the second match can be switched on\/off (regardless of the number of context lines showing already).\r\n- The window size is by default no more than the minimum of the number of matches and half the window size. The maximum can also be configured (absolute or as a percentage of the original window size).\r\n\r\nPress ? in a filter window to show all default binding.\r\n\r\nI should probably write up some documentation for this some day. For now please refer to the topmost section of the source.","package":"filtering.vim","4":"filtering.vim","src_id":"13995","5":"13995","creation_date":"1286302815","6":"1286302815"},{"0":"2759","vim_version":"6.0","1":"6.0","script_version":"1.0.3.2","2":"1.0.3.2","version_comment":"Unix line endings.","3":"Unix line endings.","package":"filtering.vim","4":"filtering.vim","src_id":"13436","5":"13436","creation_date":"1280478701","6":"1280478701"},{"0":"2759","vim_version":"6.0","1":"6.0","script_version":"1.0.3.1","2":"1.0.3.1","version_comment":"Made some functions less dependent on custom mappings.","3":"Made some functions less dependent on custom mappings.","package":"filtering.vim","4":"filtering.vim","src_id":"13430","5":"13430","creation_date":"1280436396","6":"1280436396"},{"0":"2759","vim_version":"7.0","1":"7.0","script_version":"1.0.3","2":"1.0.3","version_comment":"Fixed error where ,F always searched for \":echo\".","3":"Fixed error where ,F always searched for \":echo\".","package":"filtering.vim","4":"filtering.vim","src_id":"11349","5":"11349","creation_date":"1252485221","6":"1252485221"},{"0":"2759","vim_version":"7.0","1":"7.0","script_version":"1.0.2","2":"1.0.2","version_comment":"Another bug found by a helpful user: called FancyEcho instead of s:FancyEcho in a couple of places. This is now fixed.","3":"Another bug found by a helpful user: called FancyEcho instead of s:FancyEcho in a couple of places. This is now fixed.","package":"filtering.vim","4":"filtering.vim","src_id":"11308","5":"11308","creation_date":"1251994481","6":"1251994481"},{"0":"2759","vim_version":"7.0","1":"7.0","script_version":"1.0.1","2":"1.0.1","version_comment":"No longer change the global wrapscan setting. Use an emulation for the j\/k keys.","3":"No longer change the global wrapscan setting. Use an emulation for the j\/k keys.","package":"filtering.vim","4":"filtering.vim","src_id":"11304","5":"11304","creation_date":"1251914962","6":"1251914962"},{"0":"2759","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"filtering.vim","4":"filtering.vim","src_id":"11284","5":"11284","creation_date":"1251495982","6":"1251495982"}]},"2758":{"script_id":"2758","0":"2758","script_name":"Mustang2","1":"Mustang2","script_type":"color scheme","2":"color scheme","summary":"a small edit of a beautifully picked color scheme","3":"a small edit of a beautifully picked color scheme","description":"this is a small edit of the Mustang Vim Colorscheme by hcalves. He deserves all the credit, find him and screenshots here: http:\/\/hcalves.deviantart.com\/art\/Mustang-Vim-Colorscheme-98974484 \r\n\r\nMy edits are basically only making the search highlighting look better.\r\n\r\nHonestly this theme was love at first sight for me, you should try it too. ","4":"this is a small edit of the Mustang Vim Colorscheme by hcalves. He deserves all the credit, find him and screenshots here: http:\/\/hcalves.deviantart.com\/art\/Mustang-Vim-Colorscheme-98974484 \r\n\r\nMy edits are basically only making the search highlighting look better.\r\n\r\nHonestly this theme was love at first sight for me, you should try it too. ","install_details":"Just put in your colors folder, found at\r\n\r\nwindows at:\r\nC:\\Program Files\\Vim\\vimfiles\\colors\r\n\r\non UNIX at \r\n~\/.vim\/colors\r\n\r\nthen in vim type :colo Mustang2","5":"Just put in your colors folder, found at\r\n\r\nwindows at:\r\nC:\\Program Files\\Vim\\vimfiles\\colors\r\n\r\non UNIX at \r\n~\/.vim\/colors\r\n\r\nthen in vim type :colo Mustang2","first_name":"Gage","6":"Gage","last_name":"Peterson","7":"Peterson","releases":[{"0":"2758","vim_version":"6.0","1":"6.0","script_version":"1.1","2":"1.1","version_comment":"Initial upload","3":"Initial upload","package":"Mustang.vim","4":"Mustang.vim","src_id":"11274","5":"11274","creation_date":"1251385545","6":"1251385545"}]},"2757":{"script_id":"2757","0":"2757","script_name":"forneus","1":"forneus","script_type":"color scheme","2":"color scheme","summary":"Grey background and soft, eye pleasing foreground colours","3":"Grey background and soft, eye pleasing foreground colours","description":"This is the colorsheme I've ended up after using vim for a while. I use it mostly for C\/C++ and Ruby. It can be not so beautiful for other languages but I will update it if there is a need.","4":"This is the colorsheme I've ended up after using vim for a while. I use it mostly for C\/C++ and Ruby. It can be not so beautiful for other languages but I will update it if there is a need.","install_details":"Download it and place it under your ~\/.vim\/colors directory. \r\nThis colorscheme is intended for GUI, although it can be used in 256-colour terminal with the great CSApprox plugin => vimscript#2390.","5":"Download it and place it under your ~\/.vim\/colors directory. \r\nThis colorscheme is intended for GUI, although it can be used in 256-colour terminal with the great CSApprox plugin => vimscript#2390.","first_name":"forneus","6":"forneus","last_name":"forneus","7":"forneus","releases":[{"0":"2757","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"forneus.vim","4":"forneus.vim","src_id":"11248","5":"11248","creation_date":"1251153608","6":"1251153608"}]},"2756":{"script_id":"2756","0":"2756","script_name":"color-chooser.vim","1":"color-chooser.vim","script_type":"utility","2":"utility","summary":"a graphical RGB\/HSV color selector","3":"a graphical RGB\/HSV color selector","description":"This plugin allows you to insert and edit colors using a graphical color selection window. It makes #rrggbb hex color codes; as input it detects both #rrggbb hexcodes and X11 color names.\r\n\r\nThe script supports three language locales: English, Spanish, Czech.","4":"This plugin allows you to insert and edit colors using a graphical color selection window. It makes #rrggbb hex color codes; as input it detects both #rrggbb hexcodes and X11 color names.\r\n\r\nThe script supports three language locales: English, Spanish, Czech.","install_details":"requirements:\r\nThe script requires Python version>=2.5 with PyGTK module and GTK to run. It works best with gVim (on xterm Vim there is a bug: the window does not close after the color is selected -- it is usable but awkward).\r\n\r\nhow to install: \r\nCopy the file color-chooser.vim to your plugin directory (\"~\/.vim\/plugin\"). For the change to take effect, either restart Vim or source the script manually by the command \r\n:so ~\/.vim\/plugin\/color-chooser.vim\r\n\r\nIf you want to install the script for all users, copy it to the main plugin directory of Vim - usually \"\/usr\/share\/vim\/vimcurrent\/plugin\".\r\n\r\nAfter installation, the color selection window is launched by \r\n:call ColorChooser()\r\nMap it to a key, such as <F2>, this way:\r\n:map <F2> :call ColorChooser()<enter>\r\nThe map command is commented in the script file, you can simply uncomment it.\r\n\r\nSeveral options can be set by editing the \"script configuration\" section in the file -- they are described there.","5":"requirements:\r\nThe script requires Python version>=2.5 with PyGTK module and GTK to run. It works best with gVim (on xterm Vim there is a bug: the window does not close after the color is selected -- it is usable but awkward).\r\n\r\nhow to install: \r\nCopy the file color-chooser.vim to your plugin directory (\"~\/.vim\/plugin\"). For the change to take effect, either restart Vim or source the script manually by the command \r\n:so ~\/.vim\/plugin\/color-chooser.vim\r\n\r\nIf you want to install the script for all users, copy it to the main plugin directory of Vim - usually \"\/usr\/share\/vim\/vimcurrent\/plugin\".\r\n\r\nAfter installation, the color selection window is launched by \r\n:call ColorChooser()\r\nMap it to a key, such as <F2>, this way:\r\n:map <F2> :call ColorChooser()<enter>\r\nThe map command is commented in the script file, you can simply uncomment it.\r\n\r\nSeveral options can be set by editing the \"script configuration\" section in the file -- they are described there.","first_name":"Petr","6":"Petr","last_name":"Mejzl\u00c3\u00adk","7":"Mejzl\u00c3\u00adk","releases":[{"0":"2756","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"color-chooser.vim","4":"color-chooser.vim","src_id":"11242","5":"11242","creation_date":"1251068395","6":"1251068395"}]},"2755":{"script_id":"2755","0":"2755","script_name":"evening_2","1":"evening_2","script_type":"color scheme","2":"color scheme","summary":"Few modifications on evening color scheme","3":"Few modifications on evening color scheme","description":"Made few modification on system's evening color scheme:\r\n1. Change the text color from white to grey\r\n2. Change the string and number's background color","4":"Made few modification on system's evening color scheme:\r\n1. Change the text color from white to grey\r\n2. Change the string and number's background color","install_details":"Just copy to your \\colors folder, and set the colorscheme in your vimsrc file.","5":"Just copy to your \\colors folder, and set the colorscheme in your vimsrc file.","first_name":"michael","6":"michael","last_name":"zhang","7":"zhang","releases":[{"0":"2755","vim_version":"6.0","1":"6.0","script_version":"0.2","2":"0.2","version_comment":"1. Change the line number's color\r\n2. Change the selected area's background color","3":"1. Change the line number's color\r\n2. Change the selected area's background color","package":"evening_2.vim","4":"evening_2.vim","src_id":"11249","5":"11249","creation_date":"1251170583","6":"1251170583"},{"0":"2755","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"evening_2.vim","4":"evening_2.vim","src_id":"11240","5":"11240","creation_date":"1251060524","6":"1251060524"}]},"2754":{"script_id":"2754","0":"2754","script_name":"delimitMate","1":"delimitMate","script_type":"utility","2":"utility","summary":"Provides auto-balancing and some expansions for parens, quotes, etc.","3":"Provides auto-balancing and some expansions for parens, quotes, etc.","description":"This plug-in provides automatic closing of quotes, parenthesis, brackets, etc., besides some other related features that should make your time in insert mode a little bit easier, like syntax awareness (will not insert the closing delimiter in comments and other configurable regions), visual wrapping, <CR> and <Space> expansions (off by default), and some more.\r\n\r\nMost of the features can be modified or disabled permanently, using global variables, or on a FileType basis, using :autocmd.\r\n\r\ni.e.: The following line in your vimrc would turn auto-completion off for the \"mail\" file type:\r\n\r\n        au FileType mail let b:delimitMate_autoclose = 0\r\n\r\nRead :help delimitMate for detailed information. You can also follow the \"Vim wiki\" link on the top to discuss about this script.","4":"This plug-in provides automatic closing of quotes, parenthesis, brackets, etc., besides some other related features that should make your time in insert mode a little bit easier, like syntax awareness (will not insert the closing delimiter in comments and other configurable regions), visual wrapping, <CR> and <Space> expansions (off by default), and some more.\r\n\r\nMost of the features can be modified or disabled permanently, using global variables, or on a FileType basis, using :autocmd.\r\n\r\ni.e.: The following line in your vimrc would turn auto-completion off for the \"mail\" file type:\r\n\r\n        au FileType mail let b:delimitMate_autoclose = 0\r\n\r\nRead :help delimitMate for detailed information. You can also follow the \"Vim wiki\" link on the top to discuss about this script.","install_details":"Unzip the archive in your $HOME\/.vim directory or $HOME\/vimfiles under MS Windows.\r\n\r\nGet the git repo and\/or leave bug reports and feature request here:\r\n\r\n    http:\/\/github.com\/Raimondi\/delimitMate","5":"Unzip the archive in your $HOME\/.vim directory or $HOME\/vimfiles under MS Windows.\r\n\r\nGet the git repo and\/or leave bug reports and feature request here:\r\n\r\n    http:\/\/github.com\/Raimondi\/delimitMate","first_name":"Israel","6":"Israel","last_name":"Chauca Fuentes","7":"Chauca Fuentes","releases":[{"0":"2754","vim_version":"7.0","1":"7.0","script_version":"2.7","2":"2.7","version_comment":"- Lots of bug fixes.\r\n- Add delimitMate_offByDefault.\r\n- Add delimitMate_eol_marker.\r\n- Reduce the number of mappings.\r\n- Stop using setline().\r\n- Better handling of nested quotes.\r\n- Allow a custom pattern for smart_quotes.","3":"- Lots of bug fixes.\r\n- Add delimitMate_offByDefault.\r\n- Add delimitMate_eol_marker.\r\n- Reduce the number of mappings.\r\n- Stop using setline().\r\n- Better handling of nested quotes.\r\n- Allow a custom pattern for smart_quotes.","package":"delimitMate-2.7.zip","4":"delimitMate-2.7.zip","src_id":"22665","5":"22665","creation_date":"1417587942","6":"1417587942"},{"0":"2754","vim_version":"7.0","1":"7.0","script_version":"2.6","2":"2.6","version_comment":"- Add smart_matchpairs feature.\r\n- Add mapping to jump over contiguous delimiters.\r\n- Fix behaviour of b:loaded_delimitMate.","3":"- Add smart_matchpairs feature.\r\n- Add mapping to jump over contiguous delimiters.\r\n- Fix behaviour of b:loaded_delimitMate.","package":"delimitMate-2.6.vba","4":"delimitMate-2.6.vba","src_id":"14758","5":"14758","creation_date":"1295140019","6":"1295140019"},{"0":"2754","vim_version":"7.0","1":"7.0","script_version":"2.5.1","2":"2.5.1","version_comment":"- Remove visual wrapping. Surround.vim offers a much better implementation.\r\n- Minor mods to DelimitMateTest.","3":"- Remove visual wrapping. Surround.vim offers a much better implementation.\r\n- Minor mods to DelimitMateTest.","package":"delimitMate.vba","4":"delimitMate.vba","src_id":"13963","5":"13963","creation_date":"1285890910","6":"1285890910"},{"0":"2754","vim_version":"7.0","1":"7.0","script_version":"2.5","2":"2.5","version_comment":"- Better handling of mappings.\r\n- Add report for mappings in :DelimitMateTest.\r\n- Allow the use of \"|\" and multi-byte characters in 'delimitMate_quotes' and 'delimitMate_matchpairs'.\r\n- Allow commands to be concatenated using |.","3":"- Better handling of mappings.\r\n- Add report for mappings in :DelimitMateTest.\r\n- Allow the use of \"|\" and multi-byte characters in 'delimitMate_quotes' and 'delimitMate_matchpairs'.\r\n- Allow commands to be concatenated using |.","package":"delimitMate.zip","4":"delimitMate.zip","src_id":"13910","5":"13910","creation_date":"1285357856","6":"1285357856"},{"0":"2754","vim_version":"7.0","1":"7.0","script_version":"2.4.1","2":"2.4.1","version_comment":"- Fix problem with <Home> and <End>.\r\n- Add missing doc on 'delimitMate_smart_quotes', delimitMateBalance and  'delimitMate_balance_matchpairs'.\r\n","3":"- Fix problem with <Home> and <End>.\r\n- Add missing doc on 'delimitMate_smart_quotes', delimitMateBalance and  'delimitMate_balance_matchpairs'.\r\n","package":"delimitMate.vba.gz","4":"delimitMate.vba.gz","src_id":"13447","5":"13447","creation_date":"1280599487","6":"1280599487"},{"0":"2754","vim_version":"7.0","1":"7.0","script_version":"2.4","2":"2.4","version_comment":"- Unbalanced parens: see :help delimitMateBalance.\r\n- Visual wrapping now works on block-wise visual with some limitations.\r\n- Arrow keys didn't work on terminal.\r\n- Added option to allow nested quotes.\r\n- Expand Smart Quotes to look for a string on the right of the cursor.","3":"- Unbalanced parens: see :help delimitMateBalance.\r\n- Visual wrapping now works on block-wise visual with some limitations.\r\n- Arrow keys didn't work on terminal.\r\n- Added option to allow nested quotes.\r\n- Expand Smart Quotes to look for a string on the right of the cursor.","package":"delimitMate.vba.gz","4":"delimitMate.vba.gz","src_id":"13432","5":"13432","creation_date":"1280446226","6":"1280446226"},{"0":"2754","vim_version":"7.0","1":"7.0","script_version":"2.3.1","2":"2.3.1","version_comment":"- Fix: an extra <Space> is inserted after <Space> expansion.","3":"- Fix: an extra <Space> is inserted after <Space> expansion.","package":"delimitMate.vba.gz","4":"delimitMate.vba.gz","src_id":"13139","5":"13139","creation_date":"1275850384","6":"1275850384"},{"0":"2754","vim_version":"7.0","1":"7.0","script_version":"2.3","2":"2.3","version_comment":"- Syntax aware: Will turn off when editing comments or other regions.\r\n- Changed format of most mappings.\r\n- Fix: <CR> expansion doesn't brake automatic indentation adjustments anymore.\r\n- Fix: Arrow keys would insert A, B, C or D instead of moving the cursor when using Vim on a terminal.","3":"- Syntax aware: Will turn off when editing comments or other regions.\r\n- Changed format of most mappings.\r\n- Fix: <CR> expansion doesn't brake automatic indentation adjustments anymore.\r\n- Fix: Arrow keys would insert A, B, C or D instead of moving the cursor when using Vim on a terminal.","package":"delimitMate.vba.gz","4":"delimitMate.vba.gz","src_id":"13123","5":"13123","creation_date":"1275800889","6":"1275800889"},{"0":"2754","vim_version":"7.0","1":"7.0","script_version":"2.2","2":"2.2","version_comment":"- Added command :DelimitMateSwitch to switch the plug-in on and off.\r\n- Fix: some problems with <Left>, <Right> and <CR>.\r\n- Fix: A small problem when inserting a delimiter at the beginning of the line.\r\n","3":"- Added command :DelimitMateSwitch to switch the plug-in on and off.\r\n- Fix: some problems with <Left>, <Right> and <CR>.\r\n- Fix: A small problem when inserting a delimiter at the beginning of the line.\r\n","package":"delimitMate.vba.gz","4":"delimitMate.vba.gz","src_id":"13019","5":"13019","creation_date":"1274069190","6":"1274069190"},{"0":"2754","vim_version":"7.0","1":"7.0","script_version":"2.1","2":"2.1","version_comment":"- Most of the functions have been moved to an autoload script to avoid loading unnecessary ones.\r\n- Fixed a problem with the redo command.\r\n- Many small fixes.","3":"- Most of the functions have been moved to an autoload script to avoid loading unnecessary ones.\r\n- Fixed a problem with the redo command.\r\n- Many small fixes.","package":"delimitMate.vba.gz","4":"delimitMate.vba.gz","src_id":"12985","5":"12985","creation_date":"1273515841","6":"1273515841"},{"0":"2754","vim_version":"7.0","1":"7.0","script_version":"2.0","2":"2.0","version_comment":"* New features:\r\n- All features are redo\/undo-wise safe.\r\n- A single quote typed after an alphanumeric character is considered an apostrophe and one single quote is inserted.\r\n- A quote typed after another quote inserts a single quote and the cursor jumps to the middle.\r\n- <S-Tab> jumps out of any empty pair.\r\n- <CR> and <Space> expansions are fixed, but the functions used for it are global and can be used in custom mappings. The previous system is still active if you have any of the expansion options set.\r\n- <S-Backspace> deletes the closing delimiter.\r\n\r\n* Fixed bug:\r\n- s:vars were being used to store buffer options.","3":"* New features:\r\n- All features are redo\/undo-wise safe.\r\n- A single quote typed after an alphanumeric character is considered an apostrophe and one single quote is inserted.\r\n- A quote typed after another quote inserts a single quote and the cursor jumps to the middle.\r\n- <S-Tab> jumps out of any empty pair.\r\n- <CR> and <Space> expansions are fixed, but the functions used for it are global and can be used in custom mappings. The previous system is still active if you have any of the expansion options set.\r\n- <S-Backspace> deletes the closing delimiter.\r\n\r\n* Fixed bug:\r\n- s:vars were being used to store buffer options.","package":"delimitMate.vba.gz","4":"delimitMate.vba.gz","src_id":"12764","5":"12764","creation_date":"1270162178","6":"1270162178"},{"0":"2754","vim_version":"7.0","1":"7.0","script_version":"1.6","2":"1.6","version_comment":"Now delimitMate tries to fix the balancing of single quotes when used as apostrophes. You can read \":help delimitMate_apostrophes\" for details.\r\nFixed an error when b:delimitMate_expand_space wasn't set and g:delimitMate_expand_space was.","3":"Now delimitMate tries to fix the balancing of single quotes when used as apostrophes. You can read \":help delimitMate_apostrophes\" for details.\r\nFixed an error when b:delimitMate_expand_space wasn't set and g:delimitMate_expand_space was.","package":"delimitMate.vba.gz","4":"delimitMate.vba.gz","src_id":"11531","5":"11531","creation_date":"1255669016","6":"1255669016"},{"0":"2754","vim_version":"7.0","1":"7.0","script_version":"1.5","2":"1.5","version_comment":"Fix: delimitMate should work correctly for files passed as arguments to Vim. Thanks to Ben Beuchler for helping to nail this bug.","3":"Fix: delimitMate should work correctly for files passed as arguments to Vim. Thanks to Ben Beuchler for helping to nail this bug.","package":"delimitMate.vba.gz","4":"delimitMate.vba.gz","src_id":"11486","5":"11486","creation_date":"1254737947","6":"1254737947"},{"0":"2754","vim_version":"7.0","1":"7.0","script_version":"1.4","2":"1.4","version_comment":"Fix: delimitMate is now enabled on new buffers, even if they don't have the file type option set or were opened directly from the terminal.\r\nEdit: added missing doc file.","3":"Fix: delimitMate is now enabled on new buffers, even if they don't have the file type option set or were opened directly from the terminal.\r\nEdit: added missing doc file.","package":"delimitMate.vba.gz","4":"delimitMate.vba.gz","src_id":"11463","5":"11463","creation_date":"1254380642","6":"1254380642"},{"0":"2754","vim_version":"7.0","1":"7.0","script_version":"1.3","2":"1.3","version_comment":"Local options can be used along with autocmd for specific file type configurations.\r\nFixes:\r\n- Unnamed register content is not lost on visual mode.\r\n- Use noremap where appropiate.\r\n- Wrapping a single empty line works as expected.","3":"Local options can be used along with autocmd for specific file type configurations.\r\nFixes:\r\n- Unnamed register content is not lost on visual mode.\r\n- Use noremap where appropiate.\r\n- Wrapping a single empty line works as expected.","package":"delimitMate.vba.gz","4":"delimitMate.vba.gz","src_id":"11426","5":"11426","creation_date":"1253777760","6":"1253777760"},{"0":"2754","vim_version":"7.0","1":"7.0","script_version":"1.2","2":"1.2","version_comment":"Fixes:\r\n- When inside nested empty pairs, deleting the innermost left delimiter would delete all right contiguous delimiters.\r\n- When inside an empty pair, inserting a left delimiter wouldn't insert the right one, instead the cursor would jump to the right.\r\n- New buffer inside the current window wouldn't have the mappings set.","3":"Fixes:\r\n- When inside nested empty pairs, deleting the innermost left delimiter would delete all right contiguous delimiters.\r\n- When inside an empty pair, inserting a left delimiter wouldn't insert the right one, instead the cursor would jump to the right.\r\n- New buffer inside the current window wouldn't have the mappings set.","package":"delimitMate.vba.gz","4":"delimitMate.vba.gz","src_id":"11335","5":"11335","creation_date":"1252303935","6":"1252303935"},{"0":"2754","vim_version":"7.0","1":"7.0","script_version":"1.1","2":"1.1","version_comment":"Fixed an error that ocurred when mapleader wasn't set and added support for GetLatestScripts auto-detection.","3":"Fixed an error that ocurred when mapleader wasn't set and added support for GetLatestScripts auto-detection.","package":"delimitMate.vba.gz","4":"delimitMate.vba.gz","src_id":"11251","5":"11251","creation_date":"1251211754","6":"1251211754"},{"0":"2754","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"delimitMate.vba.gz","4":"delimitMate.vba.gz","src_id":"11237","5":"11237","creation_date":"1250998864","6":"1250998864"}]},"2753":{"script_id":"2753","0":"2753","script_name":"banned.vim","1":"banned.vim","script_type":"syntax","2":"syntax","summary":"Microsoft SDL Banned API syntax highlighting plugin","3":"Microsoft SDL Banned API syntax highlighting plugin","description":"The banned.vim syntax plugin will hilight C function calls that have been banned by Microsoft's Security Development Lifecycle (SDL). Although many of these function calls are Windows-specific, there are quite a few that are available in UNIX and should be avoided. This syntax plugin adds functionality to the existing C and C++ vim syntax plugins. Details on the banned APIs can be found here: http:\/\/msdn.microsoft.com\/en-us\/library\/bb288454.aspx\r\n","4":"The banned.vim syntax plugin will hilight C function calls that have been banned by Microsoft's Security Development Lifecycle (SDL). Although many of these function calls are Windows-specific, there are quite a few that are available in UNIX and should be avoided. This syntax plugin adds functionality to the existing C and C++ vim syntax plugins. Details on the banned APIs can be found here: http:\/\/msdn.microsoft.com\/en-us\/library\/bb288454.aspx\r\n","install_details":"Copy banned.vim to your runtimepath\/after\/syntax directory as both c.vim and cpp.vim. This way both your C and C++ syntax highlighting will be ammended. That's all you have to do. There is no need to modify your runtime configs. If you don't know what your runtimepath is then check the documentation: http:\/\/vimdoc.sourceforge.net\/htmldoc\/options.html#%27runtimepath%27","5":"Copy banned.vim to your runtimepath\/after\/syntax directory as both c.vim and cpp.vim. This way both your C and C++ syntax highlighting will be ammended. That's all you have to do. There is no need to modify your runtime configs. If you don't know what your runtimepath is then check the documentation: http:\/\/vimdoc.sourceforge.net\/htmldoc\/options.html#%27runtimepath%27","first_name":"Ramsey","6":"Ramsey","last_name":"Dow","7":"Dow","releases":[{"0":"2753","vim_version":"7.0","1":"7.0","script_version":"1.1","2":"1.1","version_comment":"Updated to SDL 5.0.","3":"Updated to SDL 5.0.","package":"banned.vim","4":"banned.vim","src_id":"15577","5":"15577","creation_date":"1304501536","6":"1304501536"},{"0":"2753","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"banned.vim","4":"banned.vim","src_id":"11236","5":"11236","creation_date":"1250986844","6":"1250986844"}]},"2752":{"script_id":"2752","0":"2752","script_name":"falcon.vim","1":"falcon.vim","script_type":"indent","2":"indent","summary":"Falcon indent file","3":"Falcon indent file","description":"If you anyone has suggestions for updates or modifications I can certainly accommodate.\r\n\r\nSee Also:\r\nSyntax:  vimscript #2745\r\nFtplugin: vimscript #2762 \r\nFtdetect: vimscript #2763\r\n\r\n\r\nFor the latest version check:\r\nhttp:\/\/github.com\/steveno\/falconpl-vim","4":"If you anyone has suggestions for updates or modifications I can certainly accommodate.\r\n\r\nSee Also:\r\nSyntax:  vimscript #2745\r\nFtplugin: vimscript #2762 \r\nFtdetect: vimscript #2763\r\n\r\n\r\nFor the latest version check:\r\nhttp:\/\/github.com\/steveno\/falconpl-vim","install_details":"Put in your indent directory.","5":"Put in your indent directory.","first_name":"Steven","6":"Steven","last_name":"Oliver","7":"Oliver","releases":[{"0":"2752","vim_version":"7.0","1":"7.0","script_version":"0.2","2":"0.2","version_comment":"Major update. Should properly indent all kinds of things better now, comments, quotes, dictionaries, etc.","3":"Major update. Should properly indent all kinds of things better now, comments, quotes, dictionaries, etc.","package":"falcon.vim","4":"falcon.vim","src_id":"13876","5":"13876","creation_date":"1285005220","6":"1285005220"},{"0":"2752","vim_version":"7.0","1":"7.0","script_version":"0.01","2":"0.01","version_comment":"Initial upload","3":"Initial upload","package":"falcon.vim","4":"falcon.vim","src_id":"11235","5":"11235","creation_date":"1250979018","6":"1250979018"}]},"2751":{"script_id":"2751","0":"2751","script_name":"vimdiff+vcs","1":"vimdiff+vcs","script_type":"utility","2":"utility","summary":"Drop-in replacement for vimdiff and gvimdiff featuring automatic CVS diff","3":"Drop-in replacement for vimdiff and gvimdiff featuring automatic CVS diff","description":"Full-blown support for CVS diffing.  Like vimscript #1209 (and unlike vimscript #90 ), this is a command-line program that merely figures out what to compare a file against.  Unlike both, this is a drop-in replacement that doesn't require getting used to a new command with different syntax.  it just works.\r\n\r\nIn addition to all vim flags, vimdiff+vcs supports the CVS revision denoting flags (-r, -D).  vimdiff+vcs also supports filesystem snapshots (e.g. those from a NetApp mountpoint), automatically parsing through the archives and comparing the specified file to the most recent version that differs.\r\n\r\nThe key useful feature here is that it's fully automatic; you just type \"gvimdiff mycode.c\" and it pops up the differences between mycode.c and the latest other copy available, be it the CVS HEAD or a more recent version from your snapshots.\r\n\r\nIf I ever do start using subversion with more regularity, this script will support that too.  It's even named \"vimdiff+vcs\" rather than \"vimdiff+cvs\" in anticipation of that (well, also for the .snapshot support).","4":"Full-blown support for CVS diffing.  Like vimscript #1209 (and unlike vimscript #90 ), this is a command-line program that merely figures out what to compare a file against.  Unlike both, this is a drop-in replacement that doesn't require getting used to a new command with different syntax.  it just works.\r\n\r\nIn addition to all vim flags, vimdiff+vcs supports the CVS revision denoting flags (-r, -D).  vimdiff+vcs also supports filesystem snapshots (e.g. those from a NetApp mountpoint), automatically parsing through the archives and comparing the specified file to the most recent version that differs.\r\n\r\nThe key useful feature here is that it's fully automatic; you just type \"gvimdiff mycode.c\" and it pops up the differences between mycode.c and the latest other copy available, be it the CVS HEAD or a more recent version from your snapshots.\r\n\r\nIf I ever do start using subversion with more regularity, this script will support that too.  It's even named \"vimdiff+vcs\" rather than \"vimdiff+cvs\" in anticipation of that (well, also for the .snapshot support).","install_details":"Install to \/usr\/local\/bin\/vimdiff and symlink it from \/usr\/local\/bin\/gvimdiff\r\n\r\nYou can put it anywhere in your path as log as it is earlier (or in place of) than the official (g)vimdiff symlinks.","5":"Install to \/usr\/local\/bin\/vimdiff and symlink it from \/usr\/local\/bin\/gvimdiff\r\n\r\nYou can put it anywhere in your path as log as it is earlier (or in place of) than the official (g)vimdiff symlinks.","first_name":"Adam","6":"Adam","last_name":"Katz","7":"Katz","releases":[{"0":"2751","vim_version":"6.0","1":"6.0","script_version":"1.6","2":"1.6","version_comment":"better fetch call","3":"better fetch call","package":"vimdiff","4":"vimdiff","src_id":"11234","5":"11234","creation_date":"1250895767","6":"1250895767"},{"0":"2751","vim_version":"6.0","1":"6.0","script_version":"1.5","2":"1.5","version_comment":"Initial upload","3":"Initial upload","package":"vimdiff","4":"vimdiff","src_id":"11233","5":"11233","creation_date":"1250893708","6":"1250893708"}]},"2750":{"script_id":"2750","0":"2750","script_name":"d8g_04","1":"d8g_04","script_type":"color scheme","2":"color scheme","summary":"simple red colorscheme","3":"simple red colorscheme","description":"Preview: http:\/\/martin.kopta.eu\/vim\/colorschemes\/d8g_04.png","4":"Preview: http:\/\/martin.kopta.eu\/vim\/colorschemes\/d8g_04.png","install_details":"copy to ~\/.vimrc\/colors\/  and run \":colorscheme d8g_04\"  in Vim","5":"copy to ~\/.vimrc\/colors\/  and run \":colorscheme d8g_04\"  in Vim","first_name":"Martin","6":"Martin","last_name":"Kopta","7":"Kopta","releases":[{"0":"2750","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"d8g_04.vim","4":"d8g_04.vim","src_id":"11223","5":"11223","creation_date":"1250712190","6":"1250712190"}]},"2749":{"script_id":"2749","0":"2749","script_name":"d8g_03","1":"d8g_03","script_type":"color scheme","2":"color scheme","summary":"simple colorscheme for everyday","3":"simple colorscheme for everyday","description":"Preview: http:\/\/martin.kopta.eu\/vim\/colorschemes\/d8g_03.png","4":"Preview: http:\/\/martin.kopta.eu\/vim\/colorschemes\/d8g_03.png","install_details":"copy to ~\/.vimrc\/colors\/  and run \":colorscheme d8g_03\"  in Vim","5":"copy to ~\/.vimrc\/colors\/  and run \":colorscheme d8g_03\"  in Vim","first_name":"Martin","6":"Martin","last_name":"Kopta","7":"Kopta","releases":[{"0":"2749","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"d8g_03.vim","4":"d8g_03.vim","src_id":"11222","5":"11222","creation_date":"1250712074","6":"1250712074"}]},"2748":{"script_id":"2748","0":"2748","script_name":"d8g_02","1":"d8g_02","script_type":"color scheme","2":"color scheme","summary":"simple colorscheme for morning","3":"simple colorscheme for morning","description":"Preview: http:\/\/martin.kopta.eu\/vim\/colorschemes\/d8g_02.png","4":"Preview: http:\/\/martin.kopta.eu\/vim\/colorschemes\/d8g_02.png","install_details":"copy to ~\/.vimrc\/colors\/  and run \":colorscheme d8g_02\" in Vim","5":"copy to ~\/.vimrc\/colors\/  and run \":colorscheme d8g_02\" in Vim","first_name":"Martin","6":"Martin","last_name":"Kopta","7":"Kopta","releases":[{"0":"2748","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"d8g_02.vim","4":"d8g_02.vim","src_id":"11221","5":"11221","creation_date":"1250711999","6":"1250711999"}]},"2747":{"script_id":"2747","0":"2747","script_name":"d8g_01","1":"d8g_01","script_type":"color scheme","2":"color scheme","summary":"simple quiet colorscheme","3":"simple quiet colorscheme","description":"Preview: http:\/\/martin.kopta.eu\/vim\/colorschemes\/d8g_01.png","4":"Preview: http:\/\/martin.kopta.eu\/vim\/colorschemes\/d8g_01.png","install_details":"copy to ~\/.vimrc\/colors\/  and run \":colorscheme d8g_01\"  in Vim","5":"copy to ~\/.vimrc\/colors\/  and run \":colorscheme d8g_01\"  in Vim","first_name":"Martin","6":"Martin","last_name":"Kopta","7":"Kopta","releases":[{"0":"2747","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"d8g_01.vim","4":"d8g_01.vim","src_id":"11220","5":"11220","creation_date":"1250711861","6":"1250711861"}]},"2746":{"script_id":"2746","0":"2746","script_name":"nuweb multi-language","1":"nuweb multi-language","script_type":"syntax","2":"syntax","summary":"Syntax highlight for NUWEB (Literate Programming), multi-language version","3":"Syntax highlight for NUWEB (Literate Programming), multi-language version","description":"Almost entirely derived from by Patricio Toledo's original syntax file (http:\/\/www.vim.org\/scripts\/script.php?script_id=543) which highlits NUWEB scraps without any language-dependent syntax highlighting. I modified it in the following ways:\r\n1) Scraps beginning with \"@{\/* C *\/\" will be highlit as C\r\n2) Scraps beginning with \"@{# Python\" will be highlit as Python.\r\n3) For all other scraps, the opening \"@{\" must be followed by a newline.\r\n\r\nIt's very easy to extend this syntax file to handle other languages. If someone else could fix #3, so that \"@{anything@}\" scraps could work without a newline following \"@{\", I'd appreciate it. Also, other ideas on doing multi-language highlighting are welcome.","4":"Almost entirely derived from by Patricio Toledo's original syntax file (http:\/\/www.vim.org\/scripts\/script.php?script_id=543) which highlits NUWEB scraps without any language-dependent syntax highlighting. I modified it in the following ways:\r\n1) Scraps beginning with \"@{\/* C *\/\" will be highlit as C\r\n2) Scraps beginning with \"@{# Python\" will be highlit as Python.\r\n3) For all other scraps, the opening \"@{\" must be followed by a newline.\r\n\r\nIt's very easy to extend this syntax file to handle other languages. If someone else could fix #3, so that \"@{anything@}\" scraps could work without a newline following \"@{\", I'd appreciate it. Also, other ideas on doing multi-language highlighting are welcome.","install_details":"Download to your system syntax\/ directory or into ~\/.vim\/syntax\/.\r\n\r\nAs .w is used by CWEB, I suggest using .nw as your NUWEB extension. Add the following to your filetype.vim:\r\n'au BufNewFile,BufRead *.nw      setf nuweb'","5":"Download to your system syntax\/ directory or into ~\/.vim\/syntax\/.\r\n\r\nAs .w is used by CWEB, I suggest using .nw as your NUWEB extension. Add the following to your filetype.vim:\r\n'au BufNewFile,BufRead *.nw      setf nuweb'","first_name":"Ahmed","6":"Ahmed","last_name":"Fasih","7":"Fasih","releases":[{"0":"2746","vim_version":"6.0","1":"6.0","script_version":"0.2","2":"0.2","version_comment":"Initial upload","3":"Initial upload","package":"nuweb.vim","4":"nuweb.vim","src_id":"11218","5":"11218","creation_date":"1250695951","6":"1250695951"}]},"2745":{"script_id":"2745","0":"2745","script_name":"falcon.vim","1":"falcon.vim","script_type":"syntax","2":"syntax","summary":"Syntax file for Falcon Programming Language","3":"Syntax file for Falcon Programming Language","description":"This is a syntax highlighting file for the Falcon programming language. It's based heavily off of the PLSQL and Ruby programming language files. \r\n\r\nSee also:\r\nIndent:    vimscript #2752\r\nFtplugin: vimscript #2762 \r\nFtdetect: vimscript #2763\r\n\r\nFor the latest version check my github site:\r\nhttp:\/\/github.com\/steveno\/falconpl-vim","4":"This is a syntax highlighting file for the Falcon programming language. It's based heavily off of the PLSQL and Ruby programming language files. \r\n\r\nSee also:\r\nIndent:    vimscript #2752\r\nFtplugin: vimscript #2762 \r\nFtdetect: vimscript #2763\r\n\r\nFor the latest version check my github site:\r\nhttp:\/\/github.com\/steveno\/falconpl-vim","install_details":"Place in your $VIM_HOME\/vimfiles\/syntax directory.","5":"Place in your $VIM_HOME\/vimfiles\/syntax directory.","first_name":"Steven","6":"Steven","last_name":"Oliver","7":"Oliver","releases":[{"0":"2745","vim_version":"7.0","1":"7.0","script_version":"0.06","2":"0.06","version_comment":"Added a new keyword or two. Removed a couple of duplicate keywords. Added support for GetLatestScript. A lot of formatting, rearranging, alphabetizing.","3":"Added a new keyword or two. Removed a couple of duplicate keywords. Added support for GetLatestScript. A lot of formatting, rearranging, alphabetizing.","package":"falcon.vim","4":"falcon.vim","src_id":"13877","5":"13877","creation_date":"1285005351","6":"1285005351"},{"0":"2745","vim_version":"7.0","1":"7.0","script_version":"0.05","2":"0.05","version_comment":"Minor improvements. A couple of symbols added.","3":"Minor improvements. A couple of symbols added.","package":"falcon.vim","4":"falcon.vim","src_id":"13825","5":"13825","creation_date":"1284464813","6":"1284464813"},{"0":"2745","vim_version":"7.0","1":"7.0","script_version":"0.04","2":"0.04","version_comment":"Major rewrite of how strings are handled. Also TODO are now highlighted inside of comments. General cleanup.","3":"Major rewrite of how strings are handled. Also TODO are now highlighted inside of comments. General cleanup.","package":"falcon.vim","4":"falcon.vim","src_id":"12915","5":"12915","creation_date":"1272563991","6":"1272563991"},{"0":"2745","vim_version":"7.0","1":"7.0","script_version":"0.03","2":"0.03","version_comment":"Added a lot of new keywords","3":"Added a lot of new keywords","package":"falcon.vim","4":"falcon.vim","src_id":"11290","5":"11290","creation_date":"1251610541","6":"1251610541"},{"0":"2745","vim_version":"7.0","1":"7.0","script_version":"0.02","2":"0.02","version_comment":"Fix some highlighting errors.","3":"Fix some highlighting errors.","package":"falcon.vim","4":"falcon.vim","src_id":"11219","5":"11219","creation_date":"1250700497","6":"1250700497"},{"0":"2745","vim_version":"7.2","1":"7.2","script_version":"0.01","2":"0.01","version_comment":"Initial upload","3":"Initial upload","package":"falcon.vim","4":"falcon.vim","src_id":"11217","5":"11217","creation_date":"1250689565","6":"1250689565"}]},"2744":{"script_id":"2744","0":"2744","script_name":"git-cheat","1":"git-cheat","script_type":"utility","2":"utility","summary":"vim helpfile for git commands","3":"vim helpfile for git commands","description":"Adaption of the git cheat sheet at http:\/\/cheat.errtheblog.com\/s\/git to the vim help format.","4":"Adaption of the git cheat sheet at http:\/\/cheat.errtheblog.com\/s\/git to the vim help format.","install_details":"Copy to ~\/.vim\/doc\/\r\nFrom inside vim, run ':helptags ~\/.vim\/doc\/'","5":"Copy to ~\/.vim\/doc\/\r\nFrom inside vim, run ':helptags ~\/.vim\/doc\/'","first_name":"Michael","6":"Michael","last_name":"Goerz","7":"Goerz","releases":[{"0":"2744","vim_version":"5.7","1":"5.7","script_version":"2.0","2":"2.0","version_comment":"Initial upload","3":"Initial upload","package":"git-cheat.txt","4":"git-cheat.txt","src_id":"11211","5":"11211","creation_date":"1250606157","6":"1250606157"}]},"2743":{"script_id":"2743","0":"2743","script_name":"greek_polytonic.vim","1":"greek_polytonic.vim","script_type":"utility","2":"utility","summary":"Keymap for the typing of traditional multi-accented (polytonic) Greek","3":"Keymap for the typing of traditional multi-accented (polytonic) Greek","description":"This is a keyboard layout useful to native Greek speakers and Greek\r\nscholars (Hellenists) who wish to use Vim\/gVim to type traditional Greek\r\n(often referred to as multi-accented or polytonic).\r\n\r\nThis layout allows the typing of multi-accented (polytonic) Greek\r\ntext in the manner of writing by hand.  Accents and breathings are typed\r\nafter the vowels in any order without dead keys. In other words, first we \r\ntype the letter and then we \"decorate\" it with the required accents.  This\r\nserves for a more comfortable typing of Greek.  Furthermore it allows easier\r\ncorrection of errors. A wrong accent (or no accent) can be replaced with\r\nwith the correct one without deleting the character.  We simply place the\r\ncursor to the right of the vowel and press the required accent.  If the\r\ncharacter can take the accent, it will be replaced by the accented version\r\nof the same character.\r\n--------------------------------------------------------------\r\nThe main accent keys are as follows:\r\n\r\n\/              Oxia (acute)\r\n\\              Varia (grave)\r\n~ (or =)   Perispomeni (circumflex)\r\n]               Psili  (lenis)\r\n[               Dasia (asper)\r\n\"               Dialytika (diaeresis)\r\n|               Ypogegrammeni (Iota subscript)\r\n---------------------------------------------------------------\r\n\r\nExamples. \r\nTyping the sequence:    a\/, will give Small Alpha with Oxia.\r\nTyping:  a\/]  or  a]\/   will give Small Alpha with Oxia and Psili.\r\nTyping:  a, followed by any combination of \/,],|, will give \r\n              Small Alpha with Oxia and Psili and Ypogegrammeni.\r\n\r\nTyping of multi-accented Greek is easier this way because this method is \r\nsimilar to the way we write by hand.  Only a few accent keys are used \r\n(easier to memorize). See the included table. Also read the source file.\r\n\r\nYou can still use the dead keys of the modern Greek keymap. For example,\r\n Alpha with Tonos can be derived either with \"a\/\" or with \";a\".\r\n\r\nInstallation:\r\n\r\n  Copy the file greek_polytonic.vim to your home .vim  keymap directory\r\n  (~\/.vim\/keymap\/) If the directory does not exist, create it.\r\n\r\n\r\n\r\n\r\nUsage:\r\n\r\n  * Load the keymap:\r\n              set keymap=greek_polytonic\r\n  * Set encodings:  \r\n              set encoding=utf-8\r\n              set inputenc=utf-8\r\n              set fenc=utf-8\r\n \r\n  * Set vim to use a monospaced unicode font that includes all the \"Greek Extented\" characters and symbols.\r\n     Example: set guifont=Consolas\\ Regular\\ 16\r\n     Note: for m$ windows this should be:  set guifont=Consolas:h16\r\n\r\n  Examples of suitable fonts are:\r\n\r\n    Dejavu Sans mono\r\n    Courier New\r\n    Bitstream Vera Sans Mono\r\n    Consolas \r\n \r\n* Also switch the keyboard to Greek with ALT-SHIFT (or whatever)\r\n\r\n* To type any of the actual symbols of the accent keys (\/, \\, ] , [, .. etc.,)  \r\n   you can toggle off the keymap with CTRL-^. When this keymap is active\r\n   the word <Polytonic> appears on the far right of the status bar.\r\n\r\n*  Search for polytonic text from the search window. \r\n   To open search window type: q\/\r\n\r\n*  To Search\/Replace or type other commands that involve arguments \r\n   in polytonic text invoke the command window by typing q: \r\n   There you can either type or copy\/paste polytonic text.  \r\n\r\nNotes: \r\n\r\n   Consolas is a Microsoft font found in Windows 7 (The Consolas font shipped\r\n   with Windows Vista is not suitable - has no extended Greek characters). It\r\n   is a very good monospaced font for displaying and for printing polytonic\r\n   Greek text.  (Microsoft is very good to us Greek scholars). \r\n   Edit: Lately the open source font DejaVu Sans Mono has become better\r\n   than Consolas,  both for displaying and printing polytonic Greek text. \r\n\r\n   Here is a screenshot of vim editing the text of Homer's Iliad\r\n   displayed in 16pt DejaVu Sans Mono. The colour scheme is biogoo:\r\n  https:\/\/postimg.cc\/BjRT8p9Z\r\n\r\n   If you have problems with printing greek utf-8 from vim, \r\n   use paps (http:\/\/paps.sourceforge.net\/)\r\n   I use it from within vim by creating a command as folows:\r\n   :command Paps write !paps --font=Consolas\\ 10 | lpr\r\n\r\n   For polytonic Greek spell checking see vimscript#3388.\r\n  \r\n   Below are the settings I use in my .vimrc file so I can type and \r\n   spellcheck polytonic Greek:\r\n\r\n  \"--------------------------------------------\r\n   set guifont=Monospace\\ Regular\\ 16\r\n   set encoding=utf-8\r\n   set fenc=utf-8\r\n   set keymap=greek_polytonic\r\n   set spelllang=polytonic,en       \r\n   set spellsuggest=10\r\n   set spell\r\n  \"--------------------------------------------\r\n\r\n  Note: In my system 'Monospace' is aliased to the font DejaVu Sans Mono.  \r\n\r\n\r\n\r\n\r\n\r\n\r\n","4":"This is a keyboard layout useful to native Greek speakers and Greek\r\nscholars (Hellenists) who wish to use Vim\/gVim to type traditional Greek\r\n(often referred to as multi-accented or polytonic).\r\n\r\nThis layout allows the typing of multi-accented (polytonic) Greek\r\ntext in the manner of writing by hand.  Accents and breathings are typed\r\nafter the vowels in any order without dead keys. In other words, first we \r\ntype the letter and then we \"decorate\" it with the required accents.  This\r\nserves for a more comfortable typing of Greek.  Furthermore it allows easier\r\ncorrection of errors. A wrong accent (or no accent) can be replaced with\r\nwith the correct one without deleting the character.  We simply place the\r\ncursor to the right of the vowel and press the required accent.  If the\r\ncharacter can take the accent, it will be replaced by the accented version\r\nof the same character.\r\n--------------------------------------------------------------\r\nThe main accent keys are as follows:\r\n\r\n\/              Oxia (acute)\r\n\\              Varia (grave)\r\n~ (or =)   Perispomeni (circumflex)\r\n]               Psili  (lenis)\r\n[               Dasia (asper)\r\n\"               Dialytika (diaeresis)\r\n|               Ypogegrammeni (Iota subscript)\r\n---------------------------------------------------------------\r\n\r\nExamples. \r\nTyping the sequence:    a\/, will give Small Alpha with Oxia.\r\nTyping:  a\/]  or  a]\/   will give Small Alpha with Oxia and Psili.\r\nTyping:  a, followed by any combination of \/,],|, will give \r\n              Small Alpha with Oxia and Psili and Ypogegrammeni.\r\n\r\nTyping of multi-accented Greek is easier this way because this method is \r\nsimilar to the way we write by hand.  Only a few accent keys are used \r\n(easier to memorize). See the included table. Also read the source file.\r\n\r\nYou can still use the dead keys of the modern Greek keymap. For example,\r\n Alpha with Tonos can be derived either with \"a\/\" or with \";a\".\r\n\r\nInstallation:\r\n\r\n  Copy the file greek_polytonic.vim to your home .vim  keymap directory\r\n  (~\/.vim\/keymap\/) If the directory does not exist, create it.\r\n\r\n\r\n\r\n\r\nUsage:\r\n\r\n  * Load the keymap:\r\n              set keymap=greek_polytonic\r\n  * Set encodings:  \r\n              set encoding=utf-8\r\n              set inputenc=utf-8\r\n              set fenc=utf-8\r\n \r\n  * Set vim to use a monospaced unicode font that includes all the \"Greek Extented\" characters and symbols.\r\n     Example: set guifont=Consolas\\ Regular\\ 16\r\n     Note: for m$ windows this should be:  set guifont=Consolas:h16\r\n\r\n  Examples of suitable fonts are:\r\n\r\n    Dejavu Sans mono\r\n    Courier New\r\n    Bitstream Vera Sans Mono\r\n    Consolas \r\n \r\n* Also switch the keyboard to Greek with ALT-SHIFT (or whatever)\r\n\r\n* To type any of the actual symbols of the accent keys (\/, \\, ] , [, .. etc.,)  \r\n   you can toggle off the keymap with CTRL-^. When this keymap is active\r\n   the word <Polytonic> appears on the far right of the status bar.\r\n\r\n*  Search for polytonic text from the search window. \r\n   To open search window type: q\/\r\n\r\n*  To Search\/Replace or type other commands that involve arguments \r\n   in polytonic text invoke the command window by typing q: \r\n   There you can either type or copy\/paste polytonic text.  \r\n\r\nNotes: \r\n\r\n   Consolas is a Microsoft font found in Windows 7 (The Consolas font shipped\r\n   with Windows Vista is not suitable - has no extended Greek characters). It\r\n   is a very good monospaced font for displaying and for printing polytonic\r\n   Greek text.  (Microsoft is very good to us Greek scholars). \r\n   Edit: Lately the open source font DejaVu Sans Mono has become better\r\n   than Consolas,  both for displaying and printing polytonic Greek text. \r\n\r\n   Here is a screenshot of vim editing the text of Homer's Iliad\r\n   displayed in 16pt DejaVu Sans Mono. The colour scheme is biogoo:\r\n  https:\/\/postimg.cc\/BjRT8p9Z\r\n\r\n   If you have problems with printing greek utf-8 from vim, \r\n   use paps (http:\/\/paps.sourceforge.net\/)\r\n   I use it from within vim by creating a command as folows:\r\n   :command Paps write !paps --font=Consolas\\ 10 | lpr\r\n\r\n   For polytonic Greek spell checking see vimscript#3388.\r\n  \r\n   Below are the settings I use in my .vimrc file so I can type and \r\n   spellcheck polytonic Greek:\r\n\r\n  \"--------------------------------------------\r\n   set guifont=Monospace\\ Regular\\ 16\r\n   set encoding=utf-8\r\n   set fenc=utf-8\r\n   set keymap=greek_polytonic\r\n   set spelllang=polytonic,en       \r\n   set spellsuggest=10\r\n   set spell\r\n  \"--------------------------------------------\r\n\r\n  Note: In my system 'Monospace' is aliased to the font DejaVu Sans Mono.  \r\n\r\n\r\n\r\n\r\n\r\n\r\n","install_details":"Unzip contents.\r\n\r\nCopy the file greek_polytonic.vim to your home .vim keymap directory\r\n  (~\/.vim\/keymap\/).  If the directory does not exist, create it.\r\n","5":"Unzip contents.\r\n\r\nCopy the file greek_polytonic.vim to your home .vim keymap directory\r\n  (~\/.vim\/keymap\/).  If the directory does not exist, create it.\r\n","first_name":"Andreas","6":"Andreas","last_name":"Proteus","7":"Proteus","releases":[{"0":"2743","vim_version":"7.0","1":"7.0","script_version":"1.2","2":"1.2","version_comment":"When keymap is active display keymap name in status bar.","3":"When keymap is active display keymap name in status bar.","package":"greek-polytonic-keymap-1.2.tar.gz","4":"greek-polytonic-keymap-1.2.tar.gz","src_id":"18403","5":"18403","creation_date":"1345002738","6":"1345002738"},{"0":"2743","vim_version":"7.0","1":"7.0","script_version":"1.1","2":"1.1","version_comment":"Prefer symbols in the range UCS 0370 - 03FF when available.\r\ni.e. all (vowel + oxia) symbols are represented \r\nby their equivalent, identical in apearance (vowel + tonos).\r\nThis simplifies find\/replace and spell checking.\r\n","3":"Prefer symbols in the range UCS 0370 - 03FF when available.\r\ni.e. all (vowel + oxia) symbols are represented \r\nby their equivalent, identical in apearance (vowel + tonos).\r\nThis simplifies find\/replace and spell checking.\r\n","package":"greek-polytonic-keymap-1.1.tar.gz","4":"greek-polytonic-keymap-1.1.tar.gz","src_id":"14031","5":"14031","creation_date":"1286572049","6":"1286572049"},{"0":"2743","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"greek-polytonic-keymap.tar.gz","4":"greek-polytonic-keymap.tar.gz","src_id":"11204","5":"11204","creation_date":"1250508016","6":"1250508016"}]},"2742":{"script_id":"2742","0":"2742","script_name":"ruby.vim","1":"ruby.vim","script_type":"indent","2":"indent","summary":"Ruby Indentation with IndentAnything","3":"Ruby Indentation with IndentAnything","description":"This is a Ruby Indentation script.\r\nI don't like the default indent\/ruby.vim ( vim-ruby from RubyGems ).\r\n\r\nNOTE:\r\n  This script requires IndentAnything version 1.2.2 or above.\r\n  See http:\/\/www.vim.org\/scripts\/script.php?script_id=1839 .\r\n","4":"This is a Ruby Indentation script.\r\nI don't like the default indent\/ruby.vim ( vim-ruby from RubyGems ).\r\n\r\nNOTE:\r\n  This script requires IndentAnything version 1.2.2 or above.\r\n  See http:\/\/www.vim.org\/scripts\/script.php?script_id=1839 .\r\n","install_details":"Extract the gzip file.\r\nThen copy the file in your home directory under ~\/.vim\/indent\/.","5":"Extract the gzip file.\r\nThen copy the file in your home directory under ~\/.vim\/indent\/.","first_name":"Yuji","6":"Yuji","last_name":"Yamamoto","7":"Yamamoto","releases":[{"0":"2742","vim_version":"7.0","1":"7.0","script_version":"0.1.7","2":"0.1.7","version_comment":"Fixed a bug which happens when putting some word including 'end' (e.g. pending) in a block. (Thanks to bmx for reporting the bug!)","3":"Fixed a bug which happens when putting some word including 'end' (e.g. pending) in a block. (Thanks to bmx for reporting the bug!)","package":"ruby.vim.gz","4":"ruby.vim.gz","src_id":"18955","5":"18955","creation_date":"1352378777","6":"1352378777"},{"0":"2742","vim_version":"6.0","1":"6.0","script_version":"0.1.6","2":"0.1.6","version_comment":"Removed '*' and '\/' from b:lineContList. Because '\/' causes a mis-indent when using a Regexp literal.\r\nNote I've never tried this script on vim 6.0.","3":"Removed '*' and '\/' from b:lineContList. Because '\/' causes a mis-indent when using a Regexp literal.\r\nNote I've never tried this script on vim 6.0.","package":"ruby.vim.gz","4":"ruby.vim.gz","src_id":"11777","5":"11777","creation_date":"1258773790","6":"1258773790"},{"0":"2742","vim_version":"7.0","1":"7.0","script_version":"0.1.5","2":"0.1.5","version_comment":"Fixed a bug which happens when you use a statement modifier.","3":"Fixed a bug which happens when you use a statement modifier.","package":"ruby.vim.gz","4":"ruby.vim.gz","src_id":"11226","5":"11226","creation_date":"1250826058","6":"1250826058"},{"0":"2742","vim_version":"7.0","1":"7.0","script_version":"0.1.2","2":"0.1.2","version_comment":"Fixed a simple mistake and make one of b:indentTrios better.","3":"Fixed a simple mistake and make one of b:indentTrios better.","package":"ruby.vim.gz","4":"ruby.vim.gz","src_id":"11203","5":"11203","creation_date":"1250497966","6":"1250497966"}]},"2741":{"script_id":"2741","0":"2741","script_name":"blue.vim","1":"blue.vim","script_type":"syntax","2":"syntax","summary":"Blue programming language syntax","3":"Blue programming language syntax","description":"A syntax file for the blue programming language.","4":"A syntax file for the blue programming language.","install_details":"1. Copy the file to ~\/.vim\/syntax\r\n2. Add the following line to your ~\/.vimrc\r\nau BufRead,BufNewFile *.bl set filetype=blue\r\n3. Reopen Vim or type :source ~\/.vimrc to reload the configuration.","5":"1. Copy the file to ~\/.vim\/syntax\r\n2. Add the following line to your ~\/.vimrc\r\nau BufRead,BufNewFile *.bl set filetype=blue\r\n3. Reopen Vim or type :source ~\/.vimrc to reload the configuration.","first_name":"Higor","6":"Higor","last_name":"Eur\u00c3\u00adpedes","7":"Eur\u00c3\u00adpedes","releases":[{"0":"2741","vim_version":"6.0","1":"6.0","script_version":"1.2","2":"1.2","version_comment":"Added del, global and lexical keywords","3":"Added del, global and lexical keywords","package":"blue.vim","4":"blue.vim","src_id":"11201","5":"11201","creation_date":"1250467153","6":"1250467153"}]},"2740":{"script_id":"2740","0":"2740","script_name":"vimper","1":"vimper","script_type":"utility","2":"utility","summary":"Yet another IDE using Vim...","3":"Yet another IDE using Vim...","description":"Vimper is a Vim based IDE, a set of plugins to enable creation of development projects. There are a lot of useful plugins available to aid development, but you need to run around to gather them. The goal is to gather a lot of these plugins into one single package and also extend them or add new plugins.\r\n\r\nCurrently it supports:\r\n * C++ IDE --  definition of C\/C++ projects \r\n(projects can also be created for developing vim plugins, mainly for demo purpose). \r\n\r\nCurrent features include:\r\n\r\n* Tree based file explorer (VTreeExplore)\r\n* Auto generation of makefiles.\r\n* Integration and navigation of make errors\/warnings.\r\n* Project Window (listing all defined projects)\r\n\r\nUpdate:\r\n* Browser to View\/Navigate Class\/Structure\/Function definitions\r\n* Search files within project and navigate to search results.\r\n\r\nGoto http:\/\/vimper.sourceforge.net\/ for more details and documentation. If you run into any issues or bugs it would be great if you could log them at the sourceforge project. Any feedback or suggestion also welcome.\r\n\r\nUse :helptags <install dir>\/doc to add the vimdoc files and type :help Vimper to view the help documentation.\r\n\r\nNote: Currently this only works for GVim on Windows, need to fix some issue to make it work on (*)nix platform.","4":"Vimper is a Vim based IDE, a set of plugins to enable creation of development projects. There are a lot of useful plugins available to aid development, but you need to run around to gather them. The goal is to gather a lot of these plugins into one single package and also extend them or add new plugins.\r\n\r\nCurrently it supports:\r\n * C++ IDE --  definition of C\/C++ projects \r\n(projects can also be created for developing vim plugins, mainly for demo purpose). \r\n\r\nCurrent features include:\r\n\r\n* Tree based file explorer (VTreeExplore)\r\n* Auto generation of makefiles.\r\n* Integration and navigation of make errors\/warnings.\r\n* Project Window (listing all defined projects)\r\n\r\nUpdate:\r\n* Browser to View\/Navigate Class\/Structure\/Function definitions\r\n* Search files within project and navigate to search results.\r\n\r\nGoto http:\/\/vimper.sourceforge.net\/ for more details and documentation. If you run into any issues or bugs it would be great if you could log them at the sourceforge project. Any feedback or suggestion also welcome.\r\n\r\nUse :helptags <install dir>\/doc to add the vimdoc files and type :help Vimper to view the help documentation.\r\n\r\nNote: Currently this only works for GVim on Windows, need to fix some issue to make it work on (*)nix platform.","install_details":"To install vimper unzip the downloaded vimper-<version>.zip file and copy the contents to your Vim folder. On (*)nix machines they can be copied to the ~\/.vim directory or on Windows machines to ~\/vimfiles. You can also copy the contents to <Vim Runtime Home>\/vimfiles (though not recommended). Set the environment variable VIMPER_HOME to point to the directory to which the content was copied (eg. VIMPER_HOME=~\/.vim).\r\n\r\n","5":"To install vimper unzip the downloaded vimper-<version>.zip file and copy the contents to your Vim folder. On (*)nix machines they can be copied to the ~\/.vim directory or on Windows machines to ~\/vimfiles. You can also copy the contents to <Vim Runtime Home>\/vimfiles (though not recommended). Set the environment variable VIMPER_HOME to point to the directory to which the content was copied (eg. VIMPER_HOME=~\/.vim).\r\n\r\n","first_name":"Subho","6":"Subho","last_name":"Ghosh","7":"Ghosh","releases":[{"0":"2740","vim_version":"7.0","1":"7.0","script_version":"0.1.1","2":"0.1.1","version_comment":"Added a Class\/Structure\/Function browser\r\n\r\nAdded project search function.","3":"Added a Class\/Structure\/Function browser\r\n\r\nAdded project search function.","package":"vimper-0.1.1.zip","4":"vimper-0.1.1.zip","src_id":"11313","5":"11313","creation_date":"1252045959","6":"1252045959"},{"0":"2740","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Fixed some bugs with the Build error window.\r\n\r\nAdded the omnicppcomplete files for C\/C++ code completion.","3":"Fixed some bugs with the Build error window.\r\n\r\nAdded the omnicppcomplete files for C\/C++ code completion.","package":"vimper-0.1-alpha.zip","4":"vimper-0.1-alpha.zip","src_id":"11193","5":"11193","creation_date":"1250322738","6":"1250322738"}]},"2739":{"script_id":"2739","0":"2739","script_name":"bclear","1":"bclear","script_type":"color scheme","2":"color scheme","summary":"A bright, white color scheme for gVim.","3":"A bright, white color scheme for gVim.","description":"A bright and relatively high-contrast GUI color scheme consisting of a white background and easy-to-read colors which are meant to be strong without being painfully vivid. Aside from undercurl and underline, all other attributes are removed (e.g. no bold or italic text). No language-specific highlighting is included: only the basics. \r\n\r\nScreenshot (Vim's highlight test): http:\/\/ompldr.org\/vNXVkOQ","4":"A bright and relatively high-contrast GUI color scheme consisting of a white background and easy-to-read colors which are meant to be strong without being painfully vivid. Aside from undercurl and underline, all other attributes are removed (e.g. no bold or italic text). No language-specific highlighting is included: only the basics. \r\n\r\nScreenshot (Vim's highlight test): http:\/\/ompldr.org\/vNXVkOQ","install_details":"Copy bclear.vim to your colors directory of choice.","5":"Copy bclear.vim to your colors directory of choice.","first_name":"Ricky","6":"Ricky","last_name":"Cintron","7":"Cintron","releases":[{"0":"2739","vim_version":"7.0","1":"7.0","script_version":"20101017","2":"20101017","version_comment":"Added highlighting values for Conceal and ColorColumn","3":"Added highlighting values for Conceal and ColorColumn","package":"bclear.vim","4":"bclear.vim","src_id":"14069","5":"14069","creation_date":"1287346015","6":"1287346015"},{"0":"2739","vim_version":"6.0","1":"6.0","script_version":"20090804","2":"20090804","version_comment":"Initial upload","3":"Initial upload","package":"bclear.vim","4":"bclear.vim","src_id":"11184","5":"11184","creation_date":"1250188653","6":"1250188653"}]},"2738":{"script_id":"2738","0":"2738","script_name":"v2.vim","1":"v2.vim","script_type":"syntax","2":"syntax","summary":"A syntax highligher for Adept\/Staeubli V+ \/ V2 Robot sources","3":"A syntax highligher for Adept\/Staeubli V+ \/ V2 Robot sources","description":"A syntax highligher for Adept\/Staeubli V+ \/ V2 Robot sourcecodes","4":"A syntax highligher for Adept\/Staeubli V+ \/ V2 Robot sourcecodes","install_details":"","5":"","first_name":"soeren","6":"soeren","last_name":"sproessig","7":"sproessig","releases":[{"0":"2738","vim_version":"6.0","1":"6.0","script_version":"0.5","2":"0.5","version_comment":"+ added enhanced matching of CALL\r\n* fixed matching of string format options","3":"+ added enhanced matching of CALL\r\n* fixed matching of string format options","package":"v2.vim","4":"v2.vim","src_id":"11209","5":"11209","creation_date":"1250599677","6":"1250599677"},{"0":"2738","vim_version":"6.0","1":"6.0","script_version":"0.4","2":"0.4","version_comment":"* fixes matching  for .PROGRAMs with parameters","3":"* fixes matching  for .PROGRAMs with parameters","package":"v2.vim","4":"v2.vim","src_id":"11208","5":"11208","creation_date":"1250589182","6":"1250589182"},{"0":"2738","vim_version":"6.0","1":"6.0","script_version":"0.3","2":"0.3","version_comment":"* changed color of comment gray\r\n* changed handling of CASE OF \/ VALUE statement\r\n","3":"* changed color of comment gray\r\n* changed handling of CASE OF \/ VALUE statement\r\n","package":"v2.vim","4":"v2.vim","src_id":"11187","5":"11187","creation_date":"1250257924","6":"1250257924"},{"0":"2738","vim_version":"6.0","1":"6.0","script_version":"0.2","2":"0.2","version_comment":"+ added highlighting for GOTO and Labels\r\n+ added highlighting for VALUE x: in SELECT\r\n+ added highlighting for string variables","3":"+ added highlighting for GOTO and Labels\r\n+ added highlighting for VALUE x: in SELECT\r\n+ added highlighting for string variables","package":"v2.vim","4":"v2.vim","src_id":"11186","5":"11186","creation_date":"1250252389","6":"1250252389"},{"0":"2738","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"v2.vim","4":"v2.vim","src_id":"11183","5":"11183","creation_date":"1250178845","6":"1250178845"}]},"2737":{"script_id":"2737","0":"2737","script_name":"bib_autocomp.vim","1":"bib_autocomp.vim","script_type":"ftplugin","2":"ftplugin","summary":"Autocompletion of BibTeX entries","3":"Autocompletion of BibTeX entries","description":"  This filetype plugin does autocompletion of BibTeX entries in *.bib files.\r\n  When you type the beginning of a BibTeX entry (e.g. @article{), it will\r\n  try to complete it. The completed result might then look like this\r\n  (see configuration options for customization):\r\n    @article{<cursor position>,\r\n\t      author = {},\r\n        title = {},\r\n        journal = {},\r\n        year = {}\r\n    }\r\n\r\n  Configuration options for this plugin (you can set them in your $HOME\/.vimrc):\r\n   - g:bib_autocomp_enable (0 or 1, default 1)\r\n       Enables\/disables this plugin.\r\n   - g:bib_autocomp_tag_indent (string, default \"\\<Tab>\")\r\n       Indention of tags inside a BibTeX entry. So for example, if you want\r\n       each tag to be indented by four spaces, set this to \"    \". Or if\r\n       you want to indent by two tabs, set this to \"\\<Tab>\\<Tab>\".\r\n   - g:bib_autocomp_tag_content_enclosing (string, default '{}')\r\n       Enclosing of a tag content. If you prefer quotes to curly brackets,\r\n       set this to '\"\"' (the tag will then look like this: author = \"\").\r\n   - g:bib_autocomp_trim_last_comma (0 or 1, default 1)\r\n       When set to 1, it will omit the last comma in the tag list (so\r\n       the result will look as the @article one in the previous paragraph).\r\n       If you want to keep the comma after the last tag, set this to 0.\r\n   - g:bib_autocomp_special_entries (list of strings, default ['string',\r\n       'preamble', 'comment'])\r\n       List of entries, which are considered \"special\". A special entry\r\n       is not a type of a publication, so these entries will be completed\r\n       just with the enclosing curly brackets, e.g. @comment{}\r\n       (see http:\/\/www.bibtex.org\/Format\/ for more info).\r\n   - g:bib_autocomp_entry_mapping (dictionary, read on for info)\r\n       This dictionary defines a mapping between a BibTeX entry name\r\n       and the list of tags it should contain. It is by default initialized\r\n       to all standard entries (see http:\/\/en.wikipedia.org\/wiki\/Bibtex)\r\n       and all required tags for each entry are inserted.\r\n       If you want to add some entry or change the list of tags, set the\r\n       configuration variable in your configuration file as follows:\r\n         let g:bib_autocomp_entry_mapping = {\r\n           \\ 'entry-name': ['first-tag', 'second-tag', ...]\r\n           \\ }\r\n       So for example, if you want to change the list of tags for the\r\n       @misc entry, set the variable in this fashion:\r\n         let g:bib_autocomp_entry_mapping = {\r\n           \\ 'misc': ['author', 'title', 'howpublished', 'url']\r\n           \\ }\r\n       If you also want to add some custom entry, then use this template:\r\n         let g:bib_autocomp_entry_mapping = {\r\n           \\ 'misc': ['author', 'title', 'howpublished', 'url'],\r\n           \\ 'custom': ['author', 'title', 'url']\r\n           \\ }\r\n       As you can see, it is just a dictionary written in the Vimscript\r\n       language.\r\n\r\nRequirements:\r\n  - filetype plugin must be enabled (a line like 'filetype plugin on' must\r\n    be in your $HOME\/.vimrc [*nix] or %UserProfile%\\_vimrc [MS Windows])\r\n\r\nInstallation Details:\r\n  Put this file into your $HOME\/.vim\/ftplugin directory [*nix]\r\n  or %UserProfile%\\vimfiles\\ftplugin folder [MS Windows].\r\n\r\nNotes:\r\n This script is by all means NOT perfect, but it works for me and suits my\r\n needs very well, so it might be also useful for you. Your feedback,\r\n opinion, suggestions, bug reports, patches, simply anything you have\r\n to say is welcomed!\r\n\r\nChangelog:\r\n  1.0 (2009-08-11)\r\n    - Initial release version of this script.\r\n","4":"  This filetype plugin does autocompletion of BibTeX entries in *.bib files.\r\n  When you type the beginning of a BibTeX entry (e.g. @article{), it will\r\n  try to complete it. The completed result might then look like this\r\n  (see configuration options for customization):\r\n    @article{<cursor position>,\r\n\t      author = {},\r\n        title = {},\r\n        journal = {},\r\n        year = {}\r\n    }\r\n\r\n  Configuration options for this plugin (you can set them in your $HOME\/.vimrc):\r\n   - g:bib_autocomp_enable (0 or 1, default 1)\r\n       Enables\/disables this plugin.\r\n   - g:bib_autocomp_tag_indent (string, default \"\\<Tab>\")\r\n       Indention of tags inside a BibTeX entry. So for example, if you want\r\n       each tag to be indented by four spaces, set this to \"    \". Or if\r\n       you want to indent by two tabs, set this to \"\\<Tab>\\<Tab>\".\r\n   - g:bib_autocomp_tag_content_enclosing (string, default '{}')\r\n       Enclosing of a tag content. If you prefer quotes to curly brackets,\r\n       set this to '\"\"' (the tag will then look like this: author = \"\").\r\n   - g:bib_autocomp_trim_last_comma (0 or 1, default 1)\r\n       When set to 1, it will omit the last comma in the tag list (so\r\n       the result will look as the @article one in the previous paragraph).\r\n       If you want to keep the comma after the last tag, set this to 0.\r\n   - g:bib_autocomp_special_entries (list of strings, default ['string',\r\n       'preamble', 'comment'])\r\n       List of entries, which are considered \"special\". A special entry\r\n       is not a type of a publication, so these entries will be completed\r\n       just with the enclosing curly brackets, e.g. @comment{}\r\n       (see http:\/\/www.bibtex.org\/Format\/ for more info).\r\n   - g:bib_autocomp_entry_mapping (dictionary, read on for info)\r\n       This dictionary defines a mapping between a BibTeX entry name\r\n       and the list of tags it should contain. It is by default initialized\r\n       to all standard entries (see http:\/\/en.wikipedia.org\/wiki\/Bibtex)\r\n       and all required tags for each entry are inserted.\r\n       If you want to add some entry or change the list of tags, set the\r\n       configuration variable in your configuration file as follows:\r\n         let g:bib_autocomp_entry_mapping = {\r\n           \\ 'entry-name': ['first-tag', 'second-tag', ...]\r\n           \\ }\r\n       So for example, if you want to change the list of tags for the\r\n       @misc entry, set the variable in this fashion:\r\n         let g:bib_autocomp_entry_mapping = {\r\n           \\ 'misc': ['author', 'title', 'howpublished', 'url']\r\n           \\ }\r\n       If you also want to add some custom entry, then use this template:\r\n         let g:bib_autocomp_entry_mapping = {\r\n           \\ 'misc': ['author', 'title', 'howpublished', 'url'],\r\n           \\ 'custom': ['author', 'title', 'url']\r\n           \\ }\r\n       As you can see, it is just a dictionary written in the Vimscript\r\n       language.\r\n\r\nRequirements:\r\n  - filetype plugin must be enabled (a line like 'filetype plugin on' must\r\n    be in your $HOME\/.vimrc [*nix] or %UserProfile%\\_vimrc [MS Windows])\r\n\r\nInstallation Details:\r\n  Put this file into your $HOME\/.vim\/ftplugin directory [*nix]\r\n  or %UserProfile%\\vimfiles\\ftplugin folder [MS Windows].\r\n\r\nNotes:\r\n This script is by all means NOT perfect, but it works for me and suits my\r\n needs very well, so it might be also useful for you. Your feedback,\r\n opinion, suggestions, bug reports, patches, simply anything you have\r\n to say is welcomed!\r\n\r\nChangelog:\r\n  1.0 (2009-08-11)\r\n    - Initial release version of this script.\r\n","install_details":"Put this file into your $HOME\/.vim\/ftplugin directory [*nix] or %UserProfile%\\vimfiles\\ftplugin folder [MS Windows].","5":"Put this file into your $HOME\/.vim\/ftplugin directory [*nix] or %UserProfile%\\vimfiles\\ftplugin folder [MS Windows].","first_name":"Petr","6":"Petr","last_name":"Zemek","7":"Zemek","releases":[{"0":"2737","vim_version":"7.0","1":"7.0","script_version":"1.0.1","2":"1.0.1","version_comment":"Documentation changes.","3":"Documentation changes.","package":"bib_autocomp.vim","4":"bib_autocomp.vim","src_id":"11194","5":"11194","creation_date":"1250367343","6":"1250367343"},{"0":"2737","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"bib_autocomp.vim","4":"bib_autocomp.vim","src_id":"11174","5":"11174","creation_date":"1249982849","6":"1249982849"}]},"2736":{"script_id":"2736","0":"2736","script_name":"Syntastic","1":"Syntastic","script_type":"utility","2":"utility","summary":"Automatic syntax checking ","3":"Automatic syntax checking ","description":"Syntastic is a syntax checking plugin that runs files through external syntax checkers and displays any resulting errors to the user. This can be done on demand, or automatically as files are saved. If syntax errors are detected, the user is notified and is happy because they didn't have to compile their code or execute their script to find them.\r\n\r\nFor the latest version version https:\/\/github.com\/scrooloose\/syntastic\r\n","4":"Syntastic is a syntax checking plugin that runs files through external syntax checkers and displays any resulting errors to the user. This can be done on demand, or automatically as files are saved. If syntax errors are detected, the user is notified and is happy because they didn't have to compile their code or execute their script to find them.\r\n\r\nFor the latest version version https:\/\/github.com\/scrooloose\/syntastic\r\n","install_details":"pathogen.vim is the recommended way to install syntastic.\r\n\r\nIf using pathogen:\r\ncd ~\/.vim\/bundle\r\ngit clone https:\/\/github.com\/scrooloose\/syntastic.git\r\n\r\nOtherwise:\r\nExtract the zip file into your ~\/.vim or $HOME\\vimfiles (windows), open up vim, run helptags and then checkout :help syntastic.","5":"pathogen.vim is the recommended way to install syntastic.\r\n\r\nIf using pathogen:\r\ncd ~\/.vim\/bundle\r\ngit clone https:\/\/github.com\/scrooloose\/syntastic.git\r\n\r\nOtherwise:\r\nExtract the zip file into your ~\/.vim or $HOME\\vimfiles (windows), open up vim, run helptags and then checkout :help syntastic.","first_name":"Marty","6":"Marty","last_name":"Grenfell","7":"Grenfell","releases":[{"0":"2736","vim_version":"7.0","1":"7.0","script_version":"3.6.0","2":"3.6.0","version_comment":"Core changes:\r\n\r\n* New option g:syntastic_exit_checks (@lcd047)\r\n* New option b:syntastic_skip_checks (@lcd047)\r\n* New options b:syntastic_<filetype>_<checker>_exec and b:syntastic_<checker>_exec (@lcd047)\r\n* New postprocess function guards (@lcd047)\r\n* New options g:syntastic_<filetype>_<checker>_sort (@lcd047)\r\n* New option b:syntastic_mode (@lcd047)\r\n* New jump mode for g:syntastic_auto_jump (@lcd047)\r\n* Various bugs have been fixed.\r\n\r\nSyntax checker changes:\r\n\r\n* Added pc_lint checker for C and C++ (@2sb18)\r\n* Added scalastyle checker for Scala (@lcd047)\r\n* Added rpmlint checker for Linux RPM spec files (@lcd047)\r\n* Added mypy static type checker for Python (@RussHewgill)\r\n* Added mdl style checker for Markdown (@eToThePiIPower)\r\n* Added igor checker from DocBook SGML, nroff, and text (@lcd047)\r\n* Added rnv checker for Relax NG (@remko)\r\n* Added option for closurecompiler: g:syntastic_javascript_closurecompiler_script (@bjpbakker)\r\n* Added bashate checker for Bash scripts (@aswna)\r\n* Added prospector checker for Python projects (@lcd047)\r\n* Added reek checker for Ruby (@mmozuras)\r\n* Added flow checker for JavaScript (@faceleg)\r\n* Added luacheck checker for Lua (@tbastos)\r\n* Added option for python: g:syntastic_python_python_use_codec (@delfick)\r\n* Removed the avrgcc checker for Arduino (@lcd047)\r\n* Removed the g:syntastic_java_javac_temp_dir option from javac (@lcd047)\r\n* Various bugs have been fixed.\r\n","3":"Core changes:\r\n\r\n* New option g:syntastic_exit_checks (@lcd047)\r\n* New option b:syntastic_skip_checks (@lcd047)\r\n* New options b:syntastic_<filetype>_<checker>_exec and b:syntastic_<checker>_exec (@lcd047)\r\n* New postprocess function guards (@lcd047)\r\n* New options g:syntastic_<filetype>_<checker>_sort (@lcd047)\r\n* New option b:syntastic_mode (@lcd047)\r\n* New jump mode for g:syntastic_auto_jump (@lcd047)\r\n* Various bugs have been fixed.\r\n\r\nSyntax checker changes:\r\n\r\n* Added pc_lint checker for C and C++ (@2sb18)\r\n* Added scalastyle checker for Scala (@lcd047)\r\n* Added rpmlint checker for Linux RPM spec files (@lcd047)\r\n* Added mypy static type checker for Python (@RussHewgill)\r\n* Added mdl style checker for Markdown (@eToThePiIPower)\r\n* Added igor checker from DocBook SGML, nroff, and text (@lcd047)\r\n* Added rnv checker for Relax NG (@remko)\r\n* Added option for closurecompiler: g:syntastic_javascript_closurecompiler_script (@bjpbakker)\r\n* Added bashate checker for Bash scripts (@aswna)\r\n* Added prospector checker for Python projects (@lcd047)\r\n* Added reek checker for Ruby (@mmozuras)\r\n* Added flow checker for JavaScript (@faceleg)\r\n* Added luacheck checker for Lua (@tbastos)\r\n* Added option for python: g:syntastic_python_python_use_codec (@delfick)\r\n* Removed the avrgcc checker for Arduino (@lcd047)\r\n* Removed the g:syntastic_java_javac_temp_dir option from javac (@lcd047)\r\n* Various bugs have been fixed.\r\n","package":"syntastic.zip","4":"syntastic.zip","src_id":"22818","5":"22818","creation_date":"1421793948","6":"1421793948"},{"0":"2736","vim_version":"7.0","1":"7.0","script_version":"3.5.0","2":"3.5.0","version_comment":"Core Changes:\r\n\r\n * New option g:syntastic_sort_aggregated_errors (@lcd047)\r\n * New syntax highlight groups SyntasticStyleError and SyntasticStyleWarning (@kovidgoyal)\r\n * Lazy calls to the IsAvailable() functions (@lcd047)\r\n * New option g:syntastic_cursor_columns (@lcd047)\r\n * Various bugs have been fixed.\r\n\r\nSyntax checker changes:\r\n\r\n * Added lint checker for R (@lcd047)\r\n * Added svtools checker for R (@lcd047)\r\n * Added scan checker for Haskell (@lcd047)\r\n * Added plutil checker for OS X and iOS plists (@lcd047)\r\n * Added tslint checker for TypeScript (@swook)\r\n * Added recess checker for LESS and CSS (@pixelastic)\r\n * Added bro checker for Bro (@JustinAzoff)\r\n * Added cabal checker for Haskell Cabal files (@ianbollinger)\r\n * Added sassc checker for SASS and SCSS (@lcd047)\r\n * Removed the rustc checker for Rust, now part of the Rust compiler package (@lcd047)\r\n * Added avrgcc checker for Arduino's ino and pde files (@lcd047)\r\n * Disabled the elixir checker by default, for security reasons (lcd047)a\r\n * Added clang_check and clang_tidy checkers for C and C++ (@bbannier)\r\n * Added phplint checker for PHP (@lcd047)\r\n * A number of checker variables have been marked as deprecated (@lcd047)\r\n * Various bugs have been fixed.\r\n","3":"Core Changes:\r\n\r\n * New option g:syntastic_sort_aggregated_errors (@lcd047)\r\n * New syntax highlight groups SyntasticStyleError and SyntasticStyleWarning (@kovidgoyal)\r\n * Lazy calls to the IsAvailable() functions (@lcd047)\r\n * New option g:syntastic_cursor_columns (@lcd047)\r\n * Various bugs have been fixed.\r\n\r\nSyntax checker changes:\r\n\r\n * Added lint checker for R (@lcd047)\r\n * Added svtools checker for R (@lcd047)\r\n * Added scan checker for Haskell (@lcd047)\r\n * Added plutil checker for OS X and iOS plists (@lcd047)\r\n * Added tslint checker for TypeScript (@swook)\r\n * Added recess checker for LESS and CSS (@pixelastic)\r\n * Added bro checker for Bro (@JustinAzoff)\r\n * Added cabal checker for Haskell Cabal files (@ianbollinger)\r\n * Added sassc checker for SASS and SCSS (@lcd047)\r\n * Removed the rustc checker for Rust, now part of the Rust compiler package (@lcd047)\r\n * Added avrgcc checker for Arduino's ino and pde files (@lcd047)\r\n * Disabled the elixir checker by default, for security reasons (lcd047)a\r\n * Added clang_check and clang_tidy checkers for C and C++ (@bbannier)\r\n * Added phplint checker for PHP (@lcd047)\r\n * A number of checker variables have been marked as deprecated (@lcd047)\r\n * Various bugs have been fixed.\r\n","package":"syntastic.zip","4":"syntastic.zip","src_id":"22401","5":"22401","creation_date":"1409601146","6":"1409601146"},{"0":"2736","vim_version":"7.0","1":"7.0","script_version":"3.4.0","2":"3.4.0","version_comment":"Core changes:\r\n\r\n* Remove g:syntastic_delayed_redraws (@lcd047)\r\n* New options *_before and *_after for makeprgBuild() (@lcd047)\r\n* New jump mode for g:syntastic_auto_jump (@lcd047)\r\n* New buffer-local user variables b:syntastic_<filetype>_<checker>_<option> (@lcd047)\r\n* Overhaul of the checker registry (@lcd047)\r\n* Speed optimisations (@lcd047)\r\n* Various bugs have been fixed.\r\n\r\nSyntax checker changes:\r\n\r\n* Disable the perl checker by default, for security reasons (lcd047)\r\n* Remove support for YouCompleteMe (@lcd047)\r\n* Added vimlint checker for VimL (@lcd047)\r\n* Added bemhtmllint checker for BEMHTML (@SevInf)\r\n* Added frosted checker for Python (@sergeybe)\r\n* Added code-ayatollah checker for Racket (@lcd047)\r\n* Added makeinfo checker for texinfo (@lcd047)\r\n* Added avrgcc checker for AVR sources (@karel-)\r\n* Added gcc checker for AT&T and Intel assembly files (@jrahm)\r\n* Added syntaxerl checker for Erlang (@locojay)\r\n* Added jsxhint checker for JSX (@thomasboyt)\r\n* Various bugs have been fixed.\r\n","3":"Core changes:\r\n\r\n* Remove g:syntastic_delayed_redraws (@lcd047)\r\n* New options *_before and *_after for makeprgBuild() (@lcd047)\r\n* New jump mode for g:syntastic_auto_jump (@lcd047)\r\n* New buffer-local user variables b:syntastic_<filetype>_<checker>_<option> (@lcd047)\r\n* Overhaul of the checker registry (@lcd047)\r\n* Speed optimisations (@lcd047)\r\n* Various bugs have been fixed.\r\n\r\nSyntax checker changes:\r\n\r\n* Disable the perl checker by default, for security reasons (lcd047)\r\n* Remove support for YouCompleteMe (@lcd047)\r\n* Added vimlint checker for VimL (@lcd047)\r\n* Added bemhtmllint checker for BEMHTML (@SevInf)\r\n* Added frosted checker for Python (@sergeybe)\r\n* Added code-ayatollah checker for Racket (@lcd047)\r\n* Added makeinfo checker for texinfo (@lcd047)\r\n* Added avrgcc checker for AVR sources (@karel-)\r\n* Added gcc checker for AT&T and Intel assembly files (@jrahm)\r\n* Added syntaxerl checker for Erlang (@locojay)\r\n* Added jsxhint checker for JSX (@thomasboyt)\r\n* Various bugs have been fixed.\r\n","package":"syntastic.zip","4":"syntastic.zip","src_id":"21627","5":"21627","creation_date":"1395047617","6":"1395047617"},{"0":"2736","vim_version":"7.0","1":"7.0","script_version":"3.3.0","2":"3.3.0","version_comment":"Core changes:\r\n- Overhaul of the checker infrastructure (@lcd047)\r\n- More detailed debugging (@lcd047)\r\n- New command :SyntasticSetLoclist (@lcd047)\r\n- :SyntasticCheck now accepts multiple parameters (@lcd047)\r\n- :SyntasticInfo now takes an optional argument (@lcd047)\r\n- Option syntastic_quiet_warnings is now deprecated (@lcd047)\r\n- New options syntastic_quiet_messages and syntastic_<filetype>_<checker>_quiet_messages (@lcd047)\r\n- Speed optimisations (@lcd047)\r\n- Various bugs have been fixed.\r\n\r\n\r\nSyntax Checker Changes\r\n- Added cppcheck checker for C\/C++ (@lcd047)\r\n- Added eslint checker for JavaScript (@maksimr)\r\n- Added yamlxs checker for YAML (@colinmkeith)\r\n- Added msgfmt checker for .po files (@syucream)\r\n- Added limbo checker for Limbo (@powerman)\r\n- Added racket checker for Racket (@2sb18)\r\n- Added flex checker for Lex (@lcd047)\r\n- Added bison checker for YACC (@lcd047)\r\n- Added mxmlc checker for ActionScript (@andyearnshaw)\r\n- Added cgc checker for GLSL (@jrahm)\r\n- Added rstcheck checker for reStructuredText (@myint)\r\n- Added gotype checker for Go (@neeee)\r\n- Added haml_lint checker for HAML (@sds)\r\n- Rework of the python checker (@lcd047)\r\n- New command :SyntasticJavacEditConfig for javac (@troydm)\r\n- Added language_check grammar checker (@myint)\r\n- Added jscs checker for JavaScript (@lcd047)\r\n- Various bugs have been fixed.\r\n","3":"Core changes:\r\n- Overhaul of the checker infrastructure (@lcd047)\r\n- More detailed debugging (@lcd047)\r\n- New command :SyntasticSetLoclist (@lcd047)\r\n- :SyntasticCheck now accepts multiple parameters (@lcd047)\r\n- :SyntasticInfo now takes an optional argument (@lcd047)\r\n- Option syntastic_quiet_warnings is now deprecated (@lcd047)\r\n- New options syntastic_quiet_messages and syntastic_<filetype>_<checker>_quiet_messages (@lcd047)\r\n- Speed optimisations (@lcd047)\r\n- Various bugs have been fixed.\r\n\r\n\r\nSyntax Checker Changes\r\n- Added cppcheck checker for C\/C++ (@lcd047)\r\n- Added eslint checker for JavaScript (@maksimr)\r\n- Added yamlxs checker for YAML (@colinmkeith)\r\n- Added msgfmt checker for .po files (@syucream)\r\n- Added limbo checker for Limbo (@powerman)\r\n- Added racket checker for Racket (@2sb18)\r\n- Added flex checker for Lex (@lcd047)\r\n- Added bison checker for YACC (@lcd047)\r\n- Added mxmlc checker for ActionScript (@andyearnshaw)\r\n- Added cgc checker for GLSL (@jrahm)\r\n- Added rstcheck checker for reStructuredText (@myint)\r\n- Added gotype checker for Go (@neeee)\r\n- Added haml_lint checker for HAML (@sds)\r\n- Rework of the python checker (@lcd047)\r\n- New command :SyntasticJavacEditConfig for javac (@troydm)\r\n- Added language_check grammar checker (@myint)\r\n- Added jscs checker for JavaScript (@lcd047)\r\n- Various bugs have been fixed.\r\n","package":"syntastic.zip","4":"syntastic.zip","src_id":"21329","5":"21329","creation_date":"1389901358","6":"1389901358"},{"0":"2736","vim_version":"7.0","1":"7.0","script_version":"3.2.0","2":"3.2.0","version_comment":"Core changes:\r\n* Allow g:syntastic_filetype_map to apply to composite filetypes (@lcd047)\r\n* Re-read g:syntastic_mode_map at each attempted check (@lcd047)\r\n* New config variable g:syntastic_delayed_redraws (@lcd047)\r\n* New config variable g:syntastic_id_checkers (@lcd047)\r\n* Various bugs have been fixed.\r\n\r\nSyntax checker changes:\r\n* Added swiffer checker for Dust.js (@smfoote)\r\n* Rework of the gcc checkers (@lcd047)\r\n* Rework of the perl checker (@lcd047)\r\n* Added handlebars checker for Handlebars (@mutewinter)\r\n* Added foodcritic checker for Chef (@dougireton)\r\n* Added rubylint checker for Ruby (@YorickPeterse)\r\n* Added shellcheck checker for sh (@lcd047)\r\n* Added scss_lint checker for SCSS (@sds)\r\n* Various bugs have been fixed.\r\n","3":"Core changes:\r\n* Allow g:syntastic_filetype_map to apply to composite filetypes (@lcd047)\r\n* Re-read g:syntastic_mode_map at each attempted check (@lcd047)\r\n* New config variable g:syntastic_delayed_redraws (@lcd047)\r\n* New config variable g:syntastic_id_checkers (@lcd047)\r\n* Various bugs have been fixed.\r\n\r\nSyntax checker changes:\r\n* Added swiffer checker for Dust.js (@smfoote)\r\n* Rework of the gcc checkers (@lcd047)\r\n* Rework of the perl checker (@lcd047)\r\n* Added handlebars checker for Handlebars (@mutewinter)\r\n* Added foodcritic checker for Chef (@dougireton)\r\n* Added rubylint checker for Ruby (@YorickPeterse)\r\n* Added shellcheck checker for sh (@lcd047)\r\n* Added scss_lint checker for SCSS (@sds)\r\n* Various bugs have been fixed.\r\n","package":"syntastic.zip","4":"syntastic.zip","src_id":"21023","5":"21023","creation_date":"1384118393","6":"1384118393"},{"0":"2736","vim_version":"7.0","1":"7.0","script_version":"3.1.0","2":"3.1.0","version_comment":"Core changes:\r\n* Added simple debug message system `:let g:syntastic_debug=1` to activate (@scrooloose)\r\n* Added `:SyntasticInfo` command (@scrooloose)\r\n* Refactor notifier mechanisms into notifier classes (@lcd047)\r\n* Syntastic no longer calls `:quit` (@kovidgoyal)\r\n* New option `g:syntastic_check_on_wq` (@lcd047)\r\n* New option `g:syntastic_ignore_files` (@lcd047)\r\n* New option `g:syntastic_filetype_map` (@lcd047)\r\n* New command `:SyntasticReset` (@lcd047)\r\n* New option `g:syntastic_aggregate_errors` (@lcd047)\r\n* Many optimisations and speed improvements (@lcd047)\r\n* Many bugs fixed.\r\n\r\nSyntax checker changes:\r\n* Added go\/govet for google go (@kisielk)\r\n* Rework of HTML\/w3 (@lcd047)\r\n* Added Python\/py3kwarn for Python 3 (@liamcurry)\r\n* Added Ruby\/rubocop checker for ruby (@roktas)\r\n* Added C\/splint checker for C (@lcd047)\r\n* Added LLVM\/llvm  checker (@superjoe30)\r\n* Added Python\/pep8 checker for Python (@lcd047)\r\n* Added nroff\/mandoc checker for nroff (@lcd047)\r\n* Added POD\/podchecker checker for POD (@lcd047)\r\n* Added C\/oclint checker for C, C++, and Objective-C (@unc0)\r\n* Added Text\/atdtool spelling, style, and grammar checker (@lcd047)\r\n* Added checkers for Objective-C++\r\n* Added Go\/golint checker for Go (@hirochachacha)\r\n* Added COBOL\/cobc checker for COBOL (@lcd047)\r\n* Split Puppet\/puppetlint into separate checkers Puppet\/puppet and Puppet\/puppetlint (@lcd047)\r\n* Made the Haxe\/haxe checker aware of [Vaxe](https:\/\/github.com\/jdonaldson\/vaxe) (@jdonaldson)\r\n* Improved maven management for the Java\/javac checher (@jvenant)\r\n* Improved working with mix projects for Elixir\/elixir (@thomas-holmes)\r\n* Added HSS\/hss checker for [HSS](http:\/\/ncannasse.fr\/projects\/hss) (@jdonaldson)\r\n* Added Python\/pylama checker for Python (@lcd047)\r\n* Added Scala\/fsc checker for Scala (@kongo2002)\r\n* New options `g:syntastic_html_tidy_blocklevel_tags`, `g:syntastic_html_tidy_inline_tags`, and `g:syntastic_html_tidy_empty_tags` for the HTML\/tidy checker (@anshul)\r\n* The __gentoo-metadata__ filetype is now an alias to __xml__; the Gentoo---Metadata\/xmllint still apply (@lcd047)\r\n* Split Haskell\/ghc-mod into separate checkers Haskell\/ghc-mod and Haskell\/hlint (@zenzike)\r\n* Added Verilog\/verilator checker for Verilog (@Kocha)\r\n* Added AsciiDoc\/asciidoc checker for AsciiDoc (@lcd047)\r\n* Added Python\/pep257 checker for Python docstrings (@marc2982)\r\n* Many bugs fixed.\r\n","3":"Core changes:\r\n* Added simple debug message system `:let g:syntastic_debug=1` to activate (@scrooloose)\r\n* Added `:SyntasticInfo` command (@scrooloose)\r\n* Refactor notifier mechanisms into notifier classes (@lcd047)\r\n* Syntastic no longer calls `:quit` (@kovidgoyal)\r\n* New option `g:syntastic_check_on_wq` (@lcd047)\r\n* New option `g:syntastic_ignore_files` (@lcd047)\r\n* New option `g:syntastic_filetype_map` (@lcd047)\r\n* New command `:SyntasticReset` (@lcd047)\r\n* New option `g:syntastic_aggregate_errors` (@lcd047)\r\n* Many optimisations and speed improvements (@lcd047)\r\n* Many bugs fixed.\r\n\r\nSyntax checker changes:\r\n* Added go\/govet for google go (@kisielk)\r\n* Rework of HTML\/w3 (@lcd047)\r\n* Added Python\/py3kwarn for Python 3 (@liamcurry)\r\n* Added Ruby\/rubocop checker for ruby (@roktas)\r\n* Added C\/splint checker for C (@lcd047)\r\n* Added LLVM\/llvm  checker (@superjoe30)\r\n* Added Python\/pep8 checker for Python (@lcd047)\r\n* Added nroff\/mandoc checker for nroff (@lcd047)\r\n* Added POD\/podchecker checker for POD (@lcd047)\r\n* Added C\/oclint checker for C, C++, and Objective-C (@unc0)\r\n* Added Text\/atdtool spelling, style, and grammar checker (@lcd047)\r\n* Added checkers for Objective-C++\r\n* Added Go\/golint checker for Go (@hirochachacha)\r\n* Added COBOL\/cobc checker for COBOL (@lcd047)\r\n* Split Puppet\/puppetlint into separate checkers Puppet\/puppet and Puppet\/puppetlint (@lcd047)\r\n* Made the Haxe\/haxe checker aware of [Vaxe](https:\/\/github.com\/jdonaldson\/vaxe) (@jdonaldson)\r\n* Improved maven management for the Java\/javac checher (@jvenant)\r\n* Improved working with mix projects for Elixir\/elixir (@thomas-holmes)\r\n* Added HSS\/hss checker for [HSS](http:\/\/ncannasse.fr\/projects\/hss) (@jdonaldson)\r\n* Added Python\/pylama checker for Python (@lcd047)\r\n* Added Scala\/fsc checker for Scala (@kongo2002)\r\n* New options `g:syntastic_html_tidy_blocklevel_tags`, `g:syntastic_html_tidy_inline_tags`, and `g:syntastic_html_tidy_empty_tags` for the HTML\/tidy checker (@anshul)\r\n* The __gentoo-metadata__ filetype is now an alias to __xml__; the Gentoo---Metadata\/xmllint still apply (@lcd047)\r\n* Split Haskell\/ghc-mod into separate checkers Haskell\/ghc-mod and Haskell\/hlint (@zenzike)\r\n* Added Verilog\/verilator checker for Verilog (@Kocha)\r\n* Added AsciiDoc\/asciidoc checker for AsciiDoc (@lcd047)\r\n* Added Python\/pep257 checker for Python docstrings (@marc2982)\r\n* Many bugs fixed.\r\n","package":"syntastic.zip","4":"syntastic.zip","src_id":"20670","5":"20670","creation_date":"1376822657","6":"1376822657"},{"0":"2736","vim_version":"7.0","1":"7.0","script_version":"3.0.0","2":"3.0.0","version_comment":"See change log here: https:\/\/github.com\/scrooloose\/syntastic\/wiki\/Changelog","3":"See change log here: https:\/\/github.com\/scrooloose\/syntastic\/wiki\/Changelog","package":"syntastic.zip","4":"syntastic.zip","src_id":"19812","5":"19812","creation_date":"1365865695","6":"1365865695"},{"0":"2736","vim_version":"7.0","1":"7.0","script_version":"2.3.0","2":"2.3.0","version_comment":"- Add syntastic_loc_list_height option\r\n- Allow errors to have a \"subtype\" that is signed differently to standard\r\n  errors. Currently geared towards differentiating style errors from\r\n  syntax errors. Currently implemented for phpcs (technosophos).\r\n- New checkers for:\r\n    - yaml\r\n    - haxe (davidB)\r\n    - ocaml (edwintorok)\r\n    - pylint (parantapa)\r\n    - rust (cjab)\r\n\r\n- Updates to existing checkers:\r\n    - jslint\r\n    - jshint (gillesruppert)\r\n    - fortran (bmattern)\r\n    - sass\r\n    - html (darcyparker)\r\n    - coffee (darcyparker)\r\n    - docbk (darcyparker)\r\n    - xml\r\n    - xslt\r\n    - less (irrationalfab)\r\n    - php (AD7six, technosophos)\r\n    - cuda\r\n    - python (mitchellh, pneff)\r\n    - perl (Anthony Carapetis)\r\n    - c (naoina, zsprackett)\r\n    - puppet (frimik)\r\n","3":"- Add syntastic_loc_list_height option\r\n- Allow errors to have a \"subtype\" that is signed differently to standard\r\n  errors. Currently geared towards differentiating style errors from\r\n  syntax errors. Currently implemented for phpcs (technosophos).\r\n- New checkers for:\r\n    - yaml\r\n    - haxe (davidB)\r\n    - ocaml (edwintorok)\r\n    - pylint (parantapa)\r\n    - rust (cjab)\r\n\r\n- Updates to existing checkers:\r\n    - jslint\r\n    - jshint (gillesruppert)\r\n    - fortran (bmattern)\r\n    - sass\r\n    - html (darcyparker)\r\n    - coffee (darcyparker)\r\n    - docbk (darcyparker)\r\n    - xml\r\n    - xslt\r\n    - less (irrationalfab)\r\n    - php (AD7six, technosophos)\r\n    - cuda\r\n    - python (mitchellh, pneff)\r\n    - perl (Anthony Carapetis)\r\n    - c (naoina, zsprackett)\r\n    - puppet (frimik)\r\n","package":"syntastic.zip","4":"syntastic.zip","src_id":"17476","5":"17476","creation_date":"1329422355","6":"1329422355"},{"0":"2736","vim_version":"7.0","1":"7.0","script_version":"2.2.0","2":"2.2.0","version_comment":"* only do syntax checks when files are saved (not when first opened) - add g:syntastic_check_on_open option to get the old behavior back\r\n* bug fix with echoing error messages; fixes incompatability with cmd-t (datanoise)\r\n* dont allow warnings to mask errors when signing\/echoing errors (ashikase)\r\n* auto close location list when leaving buffer. (millermedeiros)\r\n* update errors appropriately when :SyntasticToggleMode is called\r\n* updates\/fixes to existing checkers:\r\n  * javascript\/jshint (millermedeiros)\r\n  * javascript\/jslint\r\n  * c (kongo2002)\r\n* Support for new filetypes:\r\n  * JSON (millermedeiros, tocer)\r\n  * rst (reStructuredText files) (JNRowe)\r\n  * gentoo-metadata (JNRowe)","3":"* only do syntax checks when files are saved (not when first opened) - add g:syntastic_check_on_open option to get the old behavior back\r\n* bug fix with echoing error messages; fixes incompatability with cmd-t (datanoise)\r\n* dont allow warnings to mask errors when signing\/echoing errors (ashikase)\r\n* auto close location list when leaving buffer. (millermedeiros)\r\n* update errors appropriately when :SyntasticToggleMode is called\r\n* updates\/fixes to existing checkers:\r\n  * javascript\/jshint (millermedeiros)\r\n  * javascript\/jslint\r\n  * c (kongo2002)\r\n* Support for new filetypes:\r\n  * JSON (millermedeiros, tocer)\r\n  * rst (reStructuredText files) (JNRowe)\r\n  * gentoo-metadata (JNRowe)","package":"syntastic.zip","4":"syntastic.zip","src_id":"17114","5":"17114","creation_date":"1324726639","6":"1324726639"},{"0":"2736","vim_version":"7.0","1":"7.0","script_version":"2.1.0","2":"2.1.0","version_comment":"- when the cursor is on a line containing an error, echo the error msg (kevinw)\r\n- various bug fixes and refactoring\r\n- updates\/fixes to existing checkers:\r\n    - html (millermedeiros)\r\n    - erlang\r\n    - coffeescript\r\n    - javascript\r\n    - sh\r\n    - php (add support for phpcs - technosophos)\r\n- add an applescript checker (Zhai Cai)\r\n- add support for hyphenated filetypes (JNRowe)\r\n","3":"- when the cursor is on a line containing an error, echo the error msg (kevinw)\r\n- various bug fixes and refactoring\r\n- updates\/fixes to existing checkers:\r\n    - html (millermedeiros)\r\n    - erlang\r\n    - coffeescript\r\n    - javascript\r\n    - sh\r\n    - php (add support for phpcs - technosophos)\r\n- add an applescript checker (Zhai Cai)\r\n- add support for hyphenated filetypes (JNRowe)\r\n","package":"syntastic.zip","4":"syntastic.zip","src_id":"17061","5":"17061","creation_date":"1323853837","6":"1323853837"},{"0":"2736","vim_version":"7.0","1":"7.0","script_version":"2.0.0","2":"2.0.0","version_comment":"- Add support for highlighting the erroneous parts of lines (kstep)\r\n- Add support for displaying errors via balloons (kstep)\r\n- Add syntastic_mode_map option to give more control over when checking should be done.\r\n- Add :SyntasticCheck command to force a syntax check -  useful in passive mode (justone).\r\n- Add the option to automatically close the location list, but not automatically open it (milkypostman)\r\n- Add syntastic_auto_jump option to automatically jump to the first error (milkypostman)\r\n- Only source syntax checkers as needed - instead of loading all of them when vim starts\r\n\r\n- Support for new filetypes:\r\n    - less (julienXX)\r\n    - docbook (tpope)\r\n    - matlab (jasongraham)\r\n    - go (dtjm)\r\n    - puppet (uggedal, roman, zsprackett)\r\n    - haskell (baldo, roman)\r\n    - tcl (et)\r\n    - vala (kstep)\r\n    - cuda (temporaer)\r\n    - css (oryband, sitedyno)\r\n    - fortran (Karl Yngve Lerv\u00c3\u00a5g)\r\n    - xml (kusnier)\r\n    - xslt (kusnier)\r\n    - erlang (kTT)\r\n    - zpt (claytron)\r\n\r\n- updates to existing checkers:\r\n    - javascript (mogren, bryanforbes, cjab, ajduncan)\r\n    - sass\/scss (tmm1, atourino, dlee, epeli)\r\n    - ruby (changa)\r\n    - perl (harleypig)\r\n    - haml (bmihelac)\r\n    - php (kstep, docteurklein)\r\n    - python (kstep, soli)\r\n    - lua (kstep)\r\n    - html (kstep)\r\n    - xhtml (kstep)\r\n    - c (kongo2002, brandonw)\r\n    - cpp (kongo2002)\r\n    - coffee (industrial)\r\n    - eruby (sergevm)\r\n","3":"- Add support for highlighting the erroneous parts of lines (kstep)\r\n- Add support for displaying errors via balloons (kstep)\r\n- Add syntastic_mode_map option to give more control over when checking should be done.\r\n- Add :SyntasticCheck command to force a syntax check -  useful in passive mode (justone).\r\n- Add the option to automatically close the location list, but not automatically open it (milkypostman)\r\n- Add syntastic_auto_jump option to automatically jump to the first error (milkypostman)\r\n- Only source syntax checkers as needed - instead of loading all of them when vim starts\r\n\r\n- Support for new filetypes:\r\n    - less (julienXX)\r\n    - docbook (tpope)\r\n    - matlab (jasongraham)\r\n    - go (dtjm)\r\n    - puppet (uggedal, roman, zsprackett)\r\n    - haskell (baldo, roman)\r\n    - tcl (et)\r\n    - vala (kstep)\r\n    - cuda (temporaer)\r\n    - css (oryband, sitedyno)\r\n    - fortran (Karl Yngve Lerv\u00c3\u00a5g)\r\n    - xml (kusnier)\r\n    - xslt (kusnier)\r\n    - erlang (kTT)\r\n    - zpt (claytron)\r\n\r\n- updates to existing checkers:\r\n    - javascript (mogren, bryanforbes, cjab, ajduncan)\r\n    - sass\/scss (tmm1, atourino, dlee, epeli)\r\n    - ruby (changa)\r\n    - perl (harleypig)\r\n    - haml (bmihelac)\r\n    - php (kstep, docteurklein)\r\n    - python (kstep, soli)\r\n    - lua (kstep)\r\n    - html (kstep)\r\n    - xhtml (kstep)\r\n    - c (kongo2002, brandonw)\r\n    - cpp (kongo2002)\r\n    - coffee (industrial)\r\n    - eruby (sergevm)\r\n","package":"syntastic.zip","4":"syntastic.zip","src_id":"17007","5":"17007","creation_date":"1322785581","6":"1322785581"},{"0":"2736","vim_version":"7.0","1":"7.0","script_version":"1.2.0","2":"1.2.0","version_comment":"- New syntax checkers from github:kongo2002\r\n  - c (thanks also to github:jperras)\r\n  - cpp\r\n  - lua\r\n  - sh (thanks also to github:jmcantrell)\r\n- add coffee syntax checked by github:lstoll\r\n- add tex syntax checker\r\n- make html checker play nicer with html5, thanks to github:enaeseth\r\n- escape filenames properly when invoking syntax checkers, thanks to\r\n  github:jmcantrell\r\n- adjust the ruby syntax checker to avoid some common annoying warnings,\r\n  thanks to github:robertwahler\r\n","3":"- New syntax checkers from github:kongo2002\r\n  - c (thanks also to github:jperras)\r\n  - cpp\r\n  - lua\r\n  - sh (thanks also to github:jmcantrell)\r\n- add coffee syntax checked by github:lstoll\r\n- add tex syntax checker\r\n- make html checker play nicer with html5, thanks to github:enaeseth\r\n- escape filenames properly when invoking syntax checkers, thanks to\r\n  github:jmcantrell\r\n- adjust the ruby syntax checker to avoid some common annoying warnings,\r\n  thanks to github:robertwahler\r\n","package":"syntastic.zip","4":"syntastic.zip","src_id":"14139","5":"14139","creation_date":"1288260975","6":"1288260975"},{"0":"2736","vim_version":"7.0","1":"7.0","script_version":"1.1.0","2":"1.1.0","version_comment":"Version 1.1.0 [codenamed: tpimp]\r\n- Dont load rubygems for ruby\/eruby syntax checkers.  Thanks tpope.\r\n- Improve the javascript syntax checker to catch some\r\n  warnings that were getting missed. Thanks tpope.\r\n- Dont automatically focus the error window. Thanks tpope.\r\n- Add support for cucumber [tpope], haskell & perl\r\n  [Anthony Carapetis], and xhtml\r\n- Add commands to enable\/disable syntax checking at\r\n  runtime. See :help syntastic-commands.\r\n- Add an option to specifiy syntax checkers that should\r\n  be disabled by default. See :help syntastic_disabled_filetypes.\r\n- Dont use :signs if vim wasnt compiled with support for them.\r\n","3":"Version 1.1.0 [codenamed: tpimp]\r\n- Dont load rubygems for ruby\/eruby syntax checkers.  Thanks tpope.\r\n- Improve the javascript syntax checker to catch some\r\n  warnings that were getting missed. Thanks tpope.\r\n- Dont automatically focus the error window. Thanks tpope.\r\n- Add support for cucumber [tpope], haskell & perl\r\n  [Anthony Carapetis], and xhtml\r\n- Add commands to enable\/disable syntax checking at\r\n  runtime. See :help syntastic-commands.\r\n- Add an option to specifiy syntax checkers that should\r\n  be disabled by default. See :help syntastic_disabled_filetypes.\r\n- Dont use :signs if vim wasnt compiled with support for them.\r\n","package":"syntastic.zip","4":"syntastic.zip","src_id":"11908","5":"11908","creation_date":"1260959876","6":"1260959876"},{"0":"2736","vim_version":"7.0","1":"7.0","script_version":"1.0.0","2":"1.0.0","version_comment":"Initial upload","3":"Initial upload","package":"syntastic.zip","4":"syntastic.zip","src_id":"11172","5":"11172","creation_date":"1249982380","6":"1249982380"}]},"2735":{"script_id":"2735","0":"2735","script_name":"Logcat syntax highlighter","1":"Logcat syntax highlighter","script_type":"syntax","2":"syntax","summary":"Syntax highlighting for Android logcat files","3":"Syntax highlighting for Android logcat files","description":"Highlights Android logcat files with extension *.logcat based on the log level\r\nPlease see http:\/\/developer.android.com\/guide\/developing\/tools\/adb.html#logcat for more information on Android logcat logs.\r\n","4":"Highlights Android logcat files with extension *.logcat based on the log level\r\nPlease see http:\/\/developer.android.com\/guide\/developing\/tools\/adb.html#logcat for more information on Android logcat logs.\r\n","install_details":"The adb logcat file needs to have a .logcat extension.\r\n\r\nPlease place the logcat.vim file in your ~\/.vim\/syntax directory and add the following line to your ~\/.vimrc (or _vimrc on Windows)\r\n\r\nau BufRead,BufNewFile *.logcat set filetype=logcat\r\n","5":"The adb logcat file needs to have a .logcat extension.\r\n\r\nPlease place the logcat.vim file in your ~\/.vim\/syntax directory and add the following line to your ~\/.vimrc (or _vimrc on Windows)\r\n\r\nau BufRead,BufNewFile *.logcat set filetype=logcat\r\n","first_name":"Naseer","6":"Naseer","last_name":"Ahmed","7":"Ahmed","releases":[{"0":"2735","vim_version":"6.0","1":"6.0","script_version":"1.1","2":"1.1","version_comment":"Changed color to darkgreen for log.D logs.","3":"Changed color to darkgreen for log.D logs.","package":"logcat.vim","4":"logcat.vim","src_id":"11179","5":"11179","creation_date":"1250071317","6":"1250071317"},{"0":"2735","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"logcat.vim","4":"logcat.vim","src_id":"11171","5":"11171","creation_date":"1249927433","6":"1249927433"}]},"2734":{"script_id":"2734","0":"2734","script_name":"PreviewDialog","1":"PreviewDialog","script_type":"utility","2":"utility","summary":"Shows a GTK dialog with the color or image below the cursor","3":"Shows a GTK dialog with the color or image below the cursor","description":"PreviewDialog is written to show a GTK preview dialog with the color or image below the cursor.\r\nIt's very useful to edit css files, but can be used for anything.\r\n\r\nOptions:\r\n   g:PreviewDialogKey:\r\n     Change shotcurt (Default is 'F8')\r\n    \r\n   g:PreviewDialogEnable:\r\n     Enable PreviewDialog (Default is '1')\r\n    \r\n   g:PreviewDialogAuto:\r\n     Shows the dialog automatically when hold cursor over a word (Default is '1')\r\n\r\n   g:PathPyFile:\r\n     Set the path of .py file (Default is '~\/.vim\/')\r\n    \r\n   g:DialogPosition:\r\n     Set default window position. Can you use 'center', 'right_top' or 'right_bottom' (Default is 'right_bottom')\r\n\r\nAny suggestion, bug report or feature request are welcome.","4":"PreviewDialog is written to show a GTK preview dialog with the color or image below the cursor.\r\nIt's very useful to edit css files, but can be used for anything.\r\n\r\nOptions:\r\n   g:PreviewDialogKey:\r\n     Change shotcurt (Default is 'F8')\r\n    \r\n   g:PreviewDialogEnable:\r\n     Enable PreviewDialog (Default is '1')\r\n    \r\n   g:PreviewDialogAuto:\r\n     Shows the dialog automatically when hold cursor over a word (Default is '1')\r\n\r\n   g:PathPyFile:\r\n     Set the path of .py file (Default is '~\/.vim\/')\r\n    \r\n   g:DialogPosition:\r\n     Set default window position. Can you use 'center', 'right_top' or 'right_bottom' (Default is 'right_bottom')\r\n\r\nAny suggestion, bug report or feature request are welcome.","install_details":"Requires Python and GTK.\r\n\r\nOpen preview_dialog.vba with vim\/gvim and run:\r\n:so %","5":"Requires Python and GTK.\r\n\r\nOpen preview_dialog.vba with vim\/gvim and run:\r\n:so %","first_name":"Taylon","6":"Taylon","last_name":"Silmer","7":"Silmer","releases":[{"0":"2734","vim_version":"7.2","1":"7.2","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"preview_dialog.vba","4":"preview_dialog.vba","src_id":"11163","5":"11163","creation_date":"1249833981","6":"1249833981"}]},"2733":{"script_id":"2733","0":"2733","script_name":"Buffer Reminder Remake","1":"Buffer Reminder Remake","script_type":"utility","2":"utility","summary":"reopen buffers from previus session","3":"reopen buffers from previus session","description":"Name: Buffer reminder Remix version\r\nVersion: 0.6\r\nAutor: Vakulenko Sergiy\r\nDescription: I rewrite this plugin because prev. version of plugin not work properly with tabs\/windows.\r\n\r\nVersions change log\r\n0.7\r\n- load from file regex pattern was updated by '+' and '-' symbols\r\n- added restore view of main window (help lines)\r\n\r\n\r\nI recommend use vim tab concept with this plugin.\r\nI tested more then 3 month this plugin before submit it. It's works perfectly. For you i hope too.\r\n\r\nSorry for this \"soft\" type of documentation. Next time i will create vim doc file.\r\nAlso you can mail me if you have supplementary questions about options.\r\n\r\n\r\n\r\n\r\n\r\n\r\n\r\n-------------------------------------------\r\nVARIABLES DESCRIPTION:\r\n-------------------------------------------\r\n\r\n-------------------------------------------\r\nVariable: g:BuffReminder_enablePlugin (bool)\r\n-------------------------------------------\r\nDescription: - by default - plugin is enabled. To make it work set BuffReminder_enablePlugin:\r\nlet g:BuffReminder_enablePlugin = 1\r\n\r\n-------------------------------------------\r\nVariable: g:BuffReminderRMX_OpenFirstTabByDefault (bool)\r\n-------------------------------------------\r\nDescription: - open first tab by default\r\n\r\n-------------------------------------------\r\nVariable: g:BuffReminderRMX_ProjectFiles ( [] )\r\n-------------------------------------------\r\nDescription: this variable is list of project files. Need to add\r\nthey to this list to make them treater by the right way (this file's will be\r\nopened with 'Project ' <project_file>; also to skip project split \r\nExample:\r\nlet g:BuffReminderRMX_ProjectFiles          = ['C:\\programs\\gvim\\vim_extention\\projects\\work_machine.projectfile'\r\n                                            \\, 'C:\\programs\\gvim\\vim_extention\\projects\\home_machine.projectfile']\r\n\r\n-------------------------------------------\r\nVariable: g:BufReminderRMX_ignoreFilesList ( [] )\r\n-------------------------------------------\r\nDescription: check if buff_name in ignore file list, and if yes, skip it\r\n\r\n-------------------------------------------\r\nVariable: g:BuffReminderRMX_Disable_Hidden ( bool )\r\n-------------------------------------------\r\nDescription: if this option is enabled - all 'hidden' buffers (which isn't\r\nshowed in windows) will be skipped in save procedure\r\n\r\n-------------------------------------------\r\nVariable: g:BuffReminderRMX_Default_SplitMode ( string ('split' or 'vsplit' ) )\r\n-------------------------------------------\r\nDescription: when page contain many split window with differents\r\npossitions\/size - on save - we can't decide what split mode was used. That why, the 'simplest' solution was to define window default split mode.\r\ntodo: add algorithm which decide split option according to all windows columns\/rows size in tab.\r\n\r\n-------------------------------------------\r\nVariable: g:BuffReminder_persistency_file ( string )\r\n-------------------------------------------\r\nDescription: this is path and name of persistency file. You can it redefine if default isn't good for you.\r\n","4":"Name: Buffer reminder Remix version\r\nVersion: 0.6\r\nAutor: Vakulenko Sergiy\r\nDescription: I rewrite this plugin because prev. version of plugin not work properly with tabs\/windows.\r\n\r\nVersions change log\r\n0.7\r\n- load from file regex pattern was updated by '+' and '-' symbols\r\n- added restore view of main window (help lines)\r\n\r\n\r\nI recommend use vim tab concept with this plugin.\r\nI tested more then 3 month this plugin before submit it. It's works perfectly. For you i hope too.\r\n\r\nSorry for this \"soft\" type of documentation. Next time i will create vim doc file.\r\nAlso you can mail me if you have supplementary questions about options.\r\n\r\n\r\n\r\n\r\n\r\n\r\n\r\n-------------------------------------------\r\nVARIABLES DESCRIPTION:\r\n-------------------------------------------\r\n\r\n-------------------------------------------\r\nVariable: g:BuffReminder_enablePlugin (bool)\r\n-------------------------------------------\r\nDescription: - by default - plugin is enabled. To make it work set BuffReminder_enablePlugin:\r\nlet g:BuffReminder_enablePlugin = 1\r\n\r\n-------------------------------------------\r\nVariable: g:BuffReminderRMX_OpenFirstTabByDefault (bool)\r\n-------------------------------------------\r\nDescription: - open first tab by default\r\n\r\n-------------------------------------------\r\nVariable: g:BuffReminderRMX_ProjectFiles ( [] )\r\n-------------------------------------------\r\nDescription: this variable is list of project files. Need to add\r\nthey to this list to make them treater by the right way (this file's will be\r\nopened with 'Project ' <project_file>; also to skip project split \r\nExample:\r\nlet g:BuffReminderRMX_ProjectFiles          = ['C:\\programs\\gvim\\vim_extention\\projects\\work_machine.projectfile'\r\n                                            \\, 'C:\\programs\\gvim\\vim_extention\\projects\\home_machine.projectfile']\r\n\r\n-------------------------------------------\r\nVariable: g:BufReminderRMX_ignoreFilesList ( [] )\r\n-------------------------------------------\r\nDescription: check if buff_name in ignore file list, and if yes, skip it\r\n\r\n-------------------------------------------\r\nVariable: g:BuffReminderRMX_Disable_Hidden ( bool )\r\n-------------------------------------------\r\nDescription: if this option is enabled - all 'hidden' buffers (which isn't\r\nshowed in windows) will be skipped in save procedure\r\n\r\n-------------------------------------------\r\nVariable: g:BuffReminderRMX_Default_SplitMode ( string ('split' or 'vsplit' ) )\r\n-------------------------------------------\r\nDescription: when page contain many split window with differents\r\npossitions\/size - on save - we can't decide what split mode was used. That why, the 'simplest' solution was to define window default split mode.\r\ntodo: add algorithm which decide split option according to all windows columns\/rows size in tab.\r\n\r\n-------------------------------------------\r\nVariable: g:BuffReminder_persistency_file ( string )\r\n-------------------------------------------\r\nDescription: this is path and name of persistency file. You can it redefine if default isn't good for you.\r\n","install_details":"just drop bufReminderRemake to your plugin directory ( Usually  ~\/.vim\/plugin (Linux) or $VIM\\vimfiles\\plugin (Win32) )","5":"just drop bufReminderRemake to your plugin directory ( Usually  ~\/.vim\/plugin (Linux) or $VIM\\vimfiles\\plugin (Win32) )","first_name":"Sergey","6":"Sergey","last_name":"Vakulenko","7":"Vakulenko","releases":[{"0":"2733","vim_version":"7.0","1":"7.0","script_version":"8.1","2":"8.1","version_comment":"0.81- Fix reset of viewport of last window and split views.\r\n      Also, I fix restore of last tab.\r\n      starts work very stable on Ubuntu\r\n","3":"0.81- Fix reset of viewport of last window and split views.\r\n      Also, I fix restore of last tab.\r\n      starts work very stable on Ubuntu\r\n","package":"bufReminderRemake.vim","4":"bufReminderRemake.vim","src_id":"18060","5":"18060","creation_date":"1338320065","6":"1338320065"},{"0":"2733","vim_version":"7.0","1":"7.0","script_version":"0.72","2":"0.72","version_comment":"enable plugin by default","3":"enable plugin by default","package":"bufReminderRemake.vim","4":"bufReminderRemake.vim","src_id":"17457","5":"17457","creation_date":"1329204725","6":"1329204725"},{"0":"2733","vim_version":"7.0","1":"7.0","script_version":"0.71","2":"0.71","version_comment":"little fix of variable","3":"little fix of variable","package":"bufReminderRemake.vim","4":"bufReminderRemake.vim","src_id":"17448","5":"17448","creation_date":"1329160578","6":"1329160578"},{"0":"2733","vim_version":"7.0","1":"7.0","script_version":"0.7","2":"0.7","version_comment":"fix load of files for files with -,+ symbols\r\nadded restore view of main window (help lines)\r\nstable version","3":"fix load of files for files with -,+ symbols\r\nadded restore view of main window (help lines)\r\nstable version","package":"bufReminderRemake.vim","4":"bufReminderRemake.vim","src_id":"17433","5":"17433","creation_date":"1328988206","6":"1328988206"},{"0":"2733","vim_version":"7.0","1":"7.0","script_version":"0.6","2":"0.6","version_comment":"I tested more then 3 month this plugin before submit it. It's works perfectly.","3":"I tested more then 3 month this plugin before submit it. It's works perfectly.","package":"bufReminderRemake.vim","4":"bufReminderRemake.vim","src_id":"16052","5":"16052","creation_date":"1310067346","6":"1310067346"},{"0":"2733","vim_version":"7.0","1":"7.0","script_version":"0.5","2":"0.5","version_comment":"duplicate files opening bug fixed\r\nfunctions updates to make bufReminder work faster","3":"duplicate files opening bug fixed\r\nfunctions updates to make bufReminder work faster","package":"bufReminder.vim","4":"bufReminder.vim","src_id":"11185","5":"11185","creation_date":"1250229878","6":"1250229878"},{"0":"2733","vim_version":"7.0","1":"7.0","script_version":"0.4","2":"0.4","version_comment":"setting bufRead event variables on vimEnter event ( NERD commenter dependency plugin, for example ) fixed\r\nAlias syntax highlight fixed\r\n","3":"setting bufRead event variables on vimEnter event ( NERD commenter dependency plugin, for example ) fixed\r\nAlias syntax highlight fixed\r\n","package":"bufReminder.vim","4":"bufReminder.vim","src_id":"11165","5":"11165","creation_date":"1249889740","6":"1249889740"},{"0":"2733","vim_version":"7.0","1":"7.0","script_version":"0.3","2":"0.3","version_comment":"fixed plugin behavior in diff mode\r\nfixed syntax highlight \r\n","3":"fixed plugin behavior in diff mode\r\nfixed syntax highlight \r\n","package":"bufReminder.vim","4":"bufReminder.vim","src_id":"11161","5":"11161","creation_date":"1249740504","6":"1249740504"},{"0":"2733","vim_version":"7.2","1":"7.2","script_version":"0.2","2":"0.2","version_comment":"Initial upload","3":"Initial upload","package":"bufReminder.vim","4":"bufReminder.vim","src_id":"11159","5":"11159","creation_date":"1249737418","6":"1249737418"}]},"2732":{"script_id":"2732","0":"2732","script_name":"Notes","1":"Notes","script_type":"utility","2":"utility","summary":"Lightweight note taker plugin","3":"Lightweight note taker plugin","description":"If you like to keep your notes in clear text files, Vim is of course the best editor you could use to edit. This plugin simply makes it easier to create, open, move, search etc. these notes using custom commands, all without having to leave the comfort of Vim.\r\n\r\nEach note is a separate text file that is saved under a common root configured using g:notesRoot. You can open these note files just like any other file or use the :Note command with command-line completion to make it easier.\r\n\r\nStarting to take a new note should be as simple as typing :Note. Enter your text and save to generate a name automatically based on the first line. You can also start typing in an unnamed buffer (created using <Ctrl-W>n) and later convert it as a note using :NoteAsNew command (again named automatically based on the first line).\r\n\r\nIf you prefer, you can organize the notes into subfolders using your favorite file browser (in or outside Vim) while the :NoteNewFolder, :NoteMove and :NoteRemove commands from the plugin simplify certain operations from within Vim.\r\n\r\nFeatures:\r\n- Start a new note with less number of keystrokes and less thinking\r\n- Automatic name generation\r\n- Ease of opening with command-line completion\r\n- Searching for patterns\r\n- Ease of organizing\r\n\r\nFor full documentation, refer to doc\/notes.txt or generate helptags and type :help notes.txt.\r\n","4":"If you like to keep your notes in clear text files, Vim is of course the best editor you could use to edit. This plugin simply makes it easier to create, open, move, search etc. these notes using custom commands, all without having to leave the comfort of Vim.\r\n\r\nEach note is a separate text file that is saved under a common root configured using g:notesRoot. You can open these note files just like any other file or use the :Note command with command-line completion to make it easier.\r\n\r\nStarting to take a new note should be as simple as typing :Note. Enter your text and save to generate a name automatically based on the first line. You can also start typing in an unnamed buffer (created using <Ctrl-W>n) and later convert it as a note using :NoteAsNew command (again named automatically based on the first line).\r\n\r\nIf you prefer, you can organize the notes into subfolders using your favorite file browser (in or outside Vim) while the :NoteNewFolder, :NoteMove and :NoteRemove commands from the plugin simplify certain operations from within Vim.\r\n\r\nFeatures:\r\n- Start a new note with less number of keystrokes and less thinking\r\n- Automatic name generation\r\n- Ease of opening with command-line completion\r\n- Searching for patterns\r\n- Ease of organizing\r\n\r\nFor full documentation, refer to doc\/notes.txt or generate helptags and type :help notes.txt.\r\n","install_details":"Expand the zip into your vimfiles\/.vimrc folder. Also download and install the latest version of genutils.vim plugin (vimscript #197).\r\nRun :helptags on your doc directory.\r\nPoint g:notesRoot to the root of your notes folder in your vimrc:\r\nlet g:notesRoot = '~\/notes'","5":"Expand the zip into your vimfiles\/.vimrc folder. Also download and install the latest version of genutils.vim plugin (vimscript #197).\r\nRun :helptags on your doc directory.\r\nPoint g:notesRoot to the root of your notes folder in your vimrc:\r\nlet g:notesRoot = '~\/notes'","first_name":"Hari Krishna","6":"Hari Krishna","last_name":"Dara","7":"Dara","releases":[{"0":"2732","vim_version":"7.0","1":"7.0","script_version":"2.1","2":"2.1","version_comment":"Fixed broken :NoteSaveAs command.","3":"Fixed broken :NoteSaveAs command.","package":"notes-2.1.zip","4":"notes-2.1.zip","src_id":"11400","5":"11400","creation_date":"1253236624","6":"1253236624"},{"0":"2732","vim_version":"7.0","1":"7.0","script_version":"2.0","2":"2.0","version_comment":"- Documentation in vim help file format.\r\n- Dependency on newer genutils (2.5).\r\n- New setting g:notesCompleteAnchortAtStart\r\n- Full command-line completion for all commands that accept filename or\r\n  directory paths (:NoteNewFolder, :NoteBrowse, :NoteGrep, :NoteChangeRoot\r\n  etc.).\r\n- New command :NoteSaveAs the replaces the previous :NoteAsNew with a lot more\r\n  functionality.\r\n- New command :NoteChangeRoot to make it easier to switch between multiple\r\n  notes roots.\r\n- Improved :NoteGrep command that is now fully compatible with the built-in\r\n  :vimgrep. Allows specifying one or more files or folders and even supports\r\n  completion once the pattern is entered.\r\n- Improved :NoteBrowse with folder completion and memory of last specified\r\n  folder.\r\n- Better folder completion (using newer version of genutils).\r\n- Further refactoring of code for more consistent behavior of the plugin.\r\n- Now the plugin preserves the cursor position during a file rename.\r\n","3":"- Documentation in vim help file format.\r\n- Dependency on newer genutils (2.5).\r\n- New setting g:notesCompleteAnchortAtStart\r\n- Full command-line completion for all commands that accept filename or\r\n  directory paths (:NoteNewFolder, :NoteBrowse, :NoteGrep, :NoteChangeRoot\r\n  etc.).\r\n- New command :NoteSaveAs the replaces the previous :NoteAsNew with a lot more\r\n  functionality.\r\n- New command :NoteChangeRoot to make it easier to switch between multiple\r\n  notes roots.\r\n- Improved :NoteGrep command that is now fully compatible with the built-in\r\n  :vimgrep. Allows specifying one or more files or folders and even supports\r\n  completion once the pattern is entered.\r\n- Improved :NoteBrowse with folder completion and memory of last specified\r\n  folder.\r\n- Better folder completion (using newer version of genutils).\r\n- Further refactoring of code for more consistent behavior of the plugin.\r\n- Now the plugin preserves the cursor position during a file rename.\r\n","package":"notes-2.0.zip","4":"notes-2.0.zip","src_id":"11385","5":"11385","creation_date":"1253068210","6":"1253068210"},{"0":"2732","vim_version":"7.0","1":"7.0","script_version":"1.10","2":"1.10","version_comment":"Bugfix for broken filename sync.","3":"Bugfix for broken filename sync.","package":"notes-1.10.zip","4":"notes-1.10.zip","src_id":"11215","5":"11215","creation_date":"1250657916","6":"1250657916"},{"0":"2732","vim_version":"7.0","1":"7.0","script_version":"1.9","2":"1.9","version_comment":"Fixed issues reported by Gary Johnson.\r\n- Changed line endings to work on unix like systems.\r\n- Escape filenames so that spaes will not cause an issue on unix like systems.\r\n- g:notesWordSeparator to use a different character other than space in the filenames.\r\n- Some valid paths in g:notesRoot (such as \"$HOME\/notes\" or \"~\/notes\") are not being recognized.","3":"Fixed issues reported by Gary Johnson.\r\n- Changed line endings to work on unix like systems.\r\n- Escape filenames so that spaes will not cause an issue on unix like systems.\r\n- g:notesWordSeparator to use a different character other than space in the filenames.\r\n- Some valid paths in g:notesRoot (such as \"$HOME\/notes\" or \"~\/notes\") are not being recognized.","package":"notes-1.9.zip","4":"notes-1.9.zip","src_id":"11206","5":"11206","creation_date":"1250572123","6":"1250572123"},{"0":"2732","vim_version":"7.0","1":"7.0","script_version":"1.8","2":"1.8","version_comment":"- Added g:notesFileExtension. You can now manage files with other extension (e.g., if you keep your notes in wiki style, you can let the extension to \".wiki\").\r\n- Support for setting a 'filetype' for opened notes. By default sets to \"note\", but can be changed to say \"wiki\" if your notes are in wiki format.\r\n- :NoteRemove command to remove current note file.\r\n- Misc. enhancements and fixes.","3":"- Added g:notesFileExtension. You can now manage files with other extension (e.g., if you keep your notes in wiki style, you can let the extension to \".wiki\").\r\n- Support for setting a 'filetype' for opened notes. By default sets to \"note\", but can be changed to say \"wiki\" if your notes are in wiki format.\r\n- :NoteRemove command to remove current note file.\r\n- Misc. enhancements and fixes.","package":"notes-1.8.zip","4":"notes-1.8.zip","src_id":"11189","5":"11189","creation_date":"1250273539","6":"1250273539"},{"0":"2732","vim_version":"7.2","1":"7.2","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"notes-1.0.zip","4":"notes-1.0.zip","src_id":"11158","5":"11158","creation_date":"1249696091","6":"1249696091"}]},"2731":{"script_id":"2731","0":"2731","script_name":"sherlock.vim","1":"sherlock.vim","script_type":"utility","2":"utility","summary":"Add completion in command line for '\/', '?' and ':...\/'","3":"Add completion in command line for '\/', '?' and ':...\/'","description":"sherlock.vim add completion from current buffer for command line mode ':' after a '\/', and in command line mode '\/' and '?'.\r\n\r\nBy default, it use <C-Tab> for forward completion, and <C-S-Tab> for backward completion.\r\n\r\nFor example:\r\n:%s\/tes<C-Tab> list all word which begin with 'tes' after current cursor position;\r\n:%s\/tes<C-S-Tab> list all word which begin with 'tes' before current cursor position;\r\n\/tes<C-Tab> list all word which begin with 'tes' after current cursor position;\r\n\/tes<C-S-Tab> list all word which begin with 'tes' before current cursor position;\r\n?tes<C-Tab> list all word which begin with 'tes' after current cursor position;\r\n?tes<C-S-Tab> list all word which begin with 'tes' before current cursor position;\r\n\r\nIn ':' mode, completion is available only after a '\/'.\r\n\r\nWhen the right string is in command line, you can:\r\n1) Validate it with <Enter>, or type <Esc> to go away from command line if you are in '?' or '\/' mode;\r\n2) Validate it with <Enter> or '\/', or type <Esc> to go away from command line if you are in ':' mode.\r\n\r\nYou can override the default mapping with something like that in your .vimrc:\r\ncnoremap <Whatever you want here> <C-\\>esherlock#completeBackward()<CR>\r\ncnoremap <Whatever you want here> <C-\\>esherlock#completeForward()<CR>\r\n\r\nYou can disable this plugin with this line in your .vimrc:\r\nlet sherlock#disable = 1\r\n\r\nPlease, report any bug to sherlock.vim[..at..]mageekbox.net.","4":"sherlock.vim add completion from current buffer for command line mode ':' after a '\/', and in command line mode '\/' and '?'.\r\n\r\nBy default, it use <C-Tab> for forward completion, and <C-S-Tab> for backward completion.\r\n\r\nFor example:\r\n:%s\/tes<C-Tab> list all word which begin with 'tes' after current cursor position;\r\n:%s\/tes<C-S-Tab> list all word which begin with 'tes' before current cursor position;\r\n\/tes<C-Tab> list all word which begin with 'tes' after current cursor position;\r\n\/tes<C-S-Tab> list all word which begin with 'tes' before current cursor position;\r\n?tes<C-Tab> list all word which begin with 'tes' after current cursor position;\r\n?tes<C-S-Tab> list all word which begin with 'tes' before current cursor position;\r\n\r\nIn ':' mode, completion is available only after a '\/'.\r\n\r\nWhen the right string is in command line, you can:\r\n1) Validate it with <Enter>, or type <Esc> to go away from command line if you are in '?' or '\/' mode;\r\n2) Validate it with <Enter> or '\/', or type <Esc> to go away from command line if you are in ':' mode.\r\n\r\nYou can override the default mapping with something like that in your .vimrc:\r\ncnoremap <Whatever you want here> <C-\\>esherlock#completeBackward()<CR>\r\ncnoremap <Whatever you want here> <C-\\>esherlock#completeForward()<CR>\r\n\r\nYou can disable this plugin with this line in your .vimrc:\r\nlet sherlock#disable = 1\r\n\r\nPlease, report any bug to sherlock.vim[..at..]mageekbox.net.","install_details":"Download vimball, open it with vim, and do :so %. ","5":"Download vimball, open it with vim, and do :so %. ","first_name":"Frederic","6":"Frederic","last_name":"Hardy","7":"Hardy","releases":[{"0":"2731","vim_version":"6.0","1":"6.0","script_version":"0.0.7","2":"0.0.7","version_comment":"Optimization.","3":"Optimization.","package":"sherlock.vba","4":"sherlock.vba","src_id":"11489","5":"11489","creation_date":"1254823820","6":"1254823820"},{"0":"2731","vim_version":"6.0","1":"6.0","script_version":"0.0.6","2":"0.0.6","version_comment":"Remove bugs.\r\nIt's now possible to use completion even if cursor is not at the end of command line.","3":"Remove bugs.\r\nIt's now possible to use completion even if cursor is not at the end of command line.","package":"sherlock.vba","4":"sherlock.vba","src_id":"11453","5":"11453","creation_date":"1254239086","6":"1254239086"},{"0":"2731","vim_version":"7.0","1":"7.0","script_version":"0.0.5","2":"0.0.5","version_comment":"Add <silent> on default mapping.","3":"Add <silent> on default mapping.","package":"sherlock.vba","4":"sherlock.vba","src_id":"11401","5":"11401","creation_date":"1253264107","6":"1253264107"},{"0":"2731","vim_version":"7.0","1":"7.0","script_version":"0.0.4","2":"0.0.4","version_comment":"Remove bug in vim version detection.","3":"Remove bug in vim version detection.","package":"sherlock.vba","4":"sherlock.vba","src_id":"11156","5":"11156","creation_date":"1249654744","6":"1249654744"},{"0":"2731","vim_version":"7.0","1":"7.0","script_version":"0.0.3","2":"0.0.3","version_comment":"Remove bug in <Esc> management.\r\n\r\n","3":"Remove bug in <Esc> management.\r\n\r\n","package":"sherlock.vba","4":"sherlock.vba","src_id":"11154","5":"11154","creation_date":"1249654080","6":"1249654080"},{"0":"2731","vim_version":"7.0","1":"7.0","script_version":"0.0.2","2":"0.0.2","version_comment":"Add folding support.\r\nIf completion is in a closed folder, open it, and close it then go away.","3":"Add folding support.\r\nIf completion is in a closed folder, open it, and close it then go away.","package":"sherlock.vba","4":"sherlock.vba","src_id":"11150","5":"11150","creation_date":"1249652579","6":"1249652579"},{"0":"2731","vim_version":"7.0","1":"7.0","script_version":"0.0.1","2":"0.0.1","version_comment":"Initial upload.","3":"Initial upload.","package":"sherlock.vba","4":"sherlock.vba","src_id":"11149","5":"11149","creation_date":"1249637454","6":"1249637454"}]},"2730":{"script_id":"2730","0":"2730","script_name":"donbass.vim","1":"donbass.vim","script_type":"color scheme","2":"color scheme","summary":"Finely tuned, 256 color, light-grey background colorscheme","3":"Finely tuned, 256 color, light-grey background colorscheme","description":"This is a light-background colorscheme for 256-color terminals and GUI. It was inspired by xoria256.vim colorscheme (vimscript #2140) by Dmitriy Y. Zotikov (xio) <xio@ungrund.org>, though you probably won't find anything in common. I wanted such beautiful colors as xoria but with light background.\r\n\r\nScreenshots:\r\nhttp:\/\/i.piccy.info\/i4\/d6\/69\/98d9f22ba6312262af3d909805ec.png\r\nhttp:\/\/i.piccy.info\/i4\/d3\/8d\/5e1f639a96a7345b7e0d21851823.png\r\n\r\nColor numbers (0-255) taken from Calmar's site:\r\nhttp:\/\/www.calmar.ws\/vim\/256-xterm-24bit-rgb-color-chart.html\r\n\r\nSuggestions and patches are welcome.","4":"This is a light-background colorscheme for 256-color terminals and GUI. It was inspired by xoria256.vim colorscheme (vimscript #2140) by Dmitriy Y. Zotikov (xio) <xio@ungrund.org>, though you probably won't find anything in common. I wanted such beautiful colors as xoria but with light background.\r\n\r\nScreenshots:\r\nhttp:\/\/i.piccy.info\/i4\/d6\/69\/98d9f22ba6312262af3d909805ec.png\r\nhttp:\/\/i.piccy.info\/i4\/d3\/8d\/5e1f639a96a7345b7e0d21851823.png\r\n\r\nColor numbers (0-255) taken from Calmar's site:\r\nhttp:\/\/www.calmar.ws\/vim\/256-xterm-24bit-rgb-color-chart.html\r\n\r\nSuggestions and patches are welcome.","install_details":"1. Put donbass.vim in your ~\/.vim\/colors\/  or so.\r\n2. In vim itself or your vimrc file:\r\n\r\n\" possibly needed if you use terminal\r\nset t_Co=256\r\n\r\ncolorscheme donbass","5":"1. Put donbass.vim in your ~\/.vim\/colors\/  or so.\r\n2. In vim itself or your vimrc file:\r\n\r\n\" possibly needed if you use terminal\r\nset t_Co=256\r\n\r\ncolorscheme donbass","first_name":"Dmitry","6":"Dmitry","last_name":"Maluka","7":"Maluka","releases":[{"0":"2730","vim_version":"6.0","1":"6.0","script_version":"0.4","2":"0.4","version_comment":"Spellcheking highlighting.\r\nNon-bold wildmenu.\r\nUnderlined text normal-colored.","3":"Spellcheking highlighting.\r\nNon-bold wildmenu.\r\nUnderlined text normal-colored.","package":"donbass.vim","4":"donbass.vim","src_id":"11176","5":"11176","creation_date":"1249995497","6":"1249995497"},{"0":"2730","vim_version":"6.0","1":"6.0","script_version":"0.3","2":"0.3","version_comment":"Darker normal text foreground.","3":"Darker normal text foreground.","package":"donbass.vim","4":"donbass.vim","src_id":"11166","5":"11166","creation_date":"1249893137","6":"1249893137"},{"0":"2730","vim_version":"6.0","1":"6.0","script_version":"0.2","2":"0.2","version_comment":"Lightgrey popup-menu.\r\nAdded cPreCondit highlighting.","3":"Lightgrey popup-menu.\r\nAdded cPreCondit highlighting.","package":"donbass.vim","4":"donbass.vim","src_id":"11162","5":"11162","creation_date":"1249743838","6":"1249743838"},{"0":"2730","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"donbass.vim","4":"donbass.vim","src_id":"11142","5":"11142","creation_date":"1249593325","6":"1249593325"}]},"2729":{"script_id":"2729","0":"2729","script_name":"jslint.vim","1":"jslint.vim","script_type":"utility","2":"utility","summary":"Check JavaScript files for errors with JSLint","3":"Check JavaScript files for errors with JSLint","description":"This project is no longer actively maintained.  As alternatives I recommend Syntastic (http:\/\/www.vim.org\/scripts\/script.php?script_id=2736), jshint.vim (https:\/\/github.com\/wookiehangover\/jshint.vim), or a more active fork of jslint.vim (https:\/\/github.com\/FuDesign2008\/jslint.vim).\r\n\r\nVim plugin and command line tool for running JSLint (http:\/\/jslint.com\/).\r\n\r\nJSLint is a handy tool that spots errors and common mistakes in JavaScript code.\r\n\r\nThe source code for jslint.vim is hosted at (http:\/\/github.com\/hallettj\/jslint.vim).\r\n\r\n\r\n Usage\r\n -----------------------\r\n\r\n- This plugin automatically checks the JavaScript source and highlights the\r\n  lines with errors.\r\n\r\n  It also will display more information about the error in the commandline if the curser is\r\n  in the same line.\r\n\r\n- You also can call it manually via `:JSLintUpdate`\r\n\r\n- (optional) Add any valid JSLint options to `~\/.jslintrc` file, they will be\r\n  used as global options for all JavaScript files.\r\n  For example:\r\n\r\n        \/*jslint browser: true, regexp: true *\/\r\n        \/*global jQuery, $ *\/\r\n\r\n        \/* vim: set ft=javascript: *\/\r\n\r\nTo get a detailed report of any issues in your JavaScript file outside of Vim,\r\nrun the `bin\/jslint` executable in a terminal. For example:\r\n\r\n    $ bin\/jslint ftplugin\/jslint\/fulljslint.js\r\n\r\nYou can copy `bin\/jslint` into for `PATH` for easier access. The executable\r\nrequires that the Vim plugin is installed and also requires Ruby.\r\n\r\nTo disable error highlighting altogether add this line to your `~\/.vimrc` file:\r\n\r\n    let g:JSLintHighlightErrorLine = 0\r\n\r\n\r\nAlternative Plugins\r\n---------------------\r\n\r\nSyntastic (http:\/\/www.vim.org\/scripts\/script.php?script_id=2736) supports syntax checking for a number of languages,\r\nincluding JavaScript via jshint or JSLint.\r\n\r\nThere are other plugins for Vim that integrate JavaScript Lint (http:\/\/www.javascriptlint.com\/).  JavaScript Lint is another JavaScript checker that is similar to JSLint.\r\n\r\njsl.vim (http:\/\/www.vim.org\/scripts\/script.php?script_id=2630) uses Vim's compiler infrastructure making its use consistent with syntax checkers for other languages.\r\n\r\njavaScriptLint.vim (http:\/\/www.vim.org\/scripts\/script.php?script_id=2578) runs the contents of a JavaScript file through JavaScript Lint after the file's buffer is saved and places any warnings in the quickfix error window.\r\n\r\n\r\nCredits\r\n---------\r\n\r\n- Jesse Hallett -- original author\r\n- Nathan Smith -- Windows compatibility, quickfix integration, better OS X\r\n  compatibility, support for node.js, and other improvements\r\n- Travis Jeffery -- Easy plugin installation with rake\r\n- Sam Goldstein -- Display of problem report for the current line and bug fixes\r\n- Bryan Chow -- Fixes for formatting issues and typos\r\n- Jeff Buttars -- Options to remove and to disable error highlighting\r\n- Rainux Luo -- Support for reading JSLint options from a `~\/.jslintrc` file\r\n- Pascal Hartig -- Support for running jslint with rhino and other updates\r\n- Martin Sch\u00c3\u00bcrrer -- Fixing path issues and error handling\r\n- Nik Graf -- Documentation updates\r\n- Ian McCracken -- Real-time error checking\r\n- Luke Smith -- Enhancement of OS X support\r\n- Michael Smith -- Feature to customize JavaScript executable that is used by\r\n  setting JS_CMD environment variable\r\n- Szil\u00c3\u00a1gyi Szilveszter -- Fixes for bugs when running in Windows\r\n\r\n\r\nLicense\r\n---------\r\n\r\nCopyright (c) 2008-2010 Jesse Hallett <hallettj@gmail.com>, except where\r\notherwise noted\r\n\r\nPermission is hereby granted, free of charge, to any person obtaining a copy of\r\nthis software and associated documentation files (the \"Software\"), to deal in\r\nthe Software without restriction, including without limitation the rights to\r\nuse, copy, modify, merge, publish, distribute, sublicense, and\/or sell copies\r\nof the Software, and to permit persons to whom the Software is furnished to do\r\nso, subject to the following conditions:\r\n\r\nThe above copyright notice and this permission notice shall be included in all\r\ncopies or substantial portions of the Software.\r\n\r\nThe Software shall be used for Good, not Evil.\r\n\r\nTHE SOFTWARE IS PROVIDED \"AS IS\", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR\r\nIMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,\r\nFITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE\r\nAUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER\r\nLIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,\r\nOUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE\r\nSOFTWARE.","4":"This project is no longer actively maintained.  As alternatives I recommend Syntastic (http:\/\/www.vim.org\/scripts\/script.php?script_id=2736), jshint.vim (https:\/\/github.com\/wookiehangover\/jshint.vim), or a more active fork of jslint.vim (https:\/\/github.com\/FuDesign2008\/jslint.vim).\r\n\r\nVim plugin and command line tool for running JSLint (http:\/\/jslint.com\/).\r\n\r\nJSLint is a handy tool that spots errors and common mistakes in JavaScript code.\r\n\r\nThe source code for jslint.vim is hosted at (http:\/\/github.com\/hallettj\/jslint.vim).\r\n\r\n\r\n Usage\r\n -----------------------\r\n\r\n- This plugin automatically checks the JavaScript source and highlights the\r\n  lines with errors.\r\n\r\n  It also will display more information about the error in the commandline if the curser is\r\n  in the same line.\r\n\r\n- You also can call it manually via `:JSLintUpdate`\r\n\r\n- (optional) Add any valid JSLint options to `~\/.jslintrc` file, they will be\r\n  used as global options for all JavaScript files.\r\n  For example:\r\n\r\n        \/*jslint browser: true, regexp: true *\/\r\n        \/*global jQuery, $ *\/\r\n\r\n        \/* vim: set ft=javascript: *\/\r\n\r\nTo get a detailed report of any issues in your JavaScript file outside of Vim,\r\nrun the `bin\/jslint` executable in a terminal. For example:\r\n\r\n    $ bin\/jslint ftplugin\/jslint\/fulljslint.js\r\n\r\nYou can copy `bin\/jslint` into for `PATH` for easier access. The executable\r\nrequires that the Vim plugin is installed and also requires Ruby.\r\n\r\nTo disable error highlighting altogether add this line to your `~\/.vimrc` file:\r\n\r\n    let g:JSLintHighlightErrorLine = 0\r\n\r\n\r\nAlternative Plugins\r\n---------------------\r\n\r\nSyntastic (http:\/\/www.vim.org\/scripts\/script.php?script_id=2736) supports syntax checking for a number of languages,\r\nincluding JavaScript via jshint or JSLint.\r\n\r\nThere are other plugins for Vim that integrate JavaScript Lint (http:\/\/www.javascriptlint.com\/).  JavaScript Lint is another JavaScript checker that is similar to JSLint.\r\n\r\njsl.vim (http:\/\/www.vim.org\/scripts\/script.php?script_id=2630) uses Vim's compiler infrastructure making its use consistent with syntax checkers for other languages.\r\n\r\njavaScriptLint.vim (http:\/\/www.vim.org\/scripts\/script.php?script_id=2578) runs the contents of a JavaScript file through JavaScript Lint after the file's buffer is saved and places any warnings in the quickfix error window.\r\n\r\n\r\nCredits\r\n---------\r\n\r\n- Jesse Hallett -- original author\r\n- Nathan Smith -- Windows compatibility, quickfix integration, better OS X\r\n  compatibility, support for node.js, and other improvements\r\n- Travis Jeffery -- Easy plugin installation with rake\r\n- Sam Goldstein -- Display of problem report for the current line and bug fixes\r\n- Bryan Chow -- Fixes for formatting issues and typos\r\n- Jeff Buttars -- Options to remove and to disable error highlighting\r\n- Rainux Luo -- Support for reading JSLint options from a `~\/.jslintrc` file\r\n- Pascal Hartig -- Support for running jslint with rhino and other updates\r\n- Martin Sch\u00c3\u00bcrrer -- Fixing path issues and error handling\r\n- Nik Graf -- Documentation updates\r\n- Ian McCracken -- Real-time error checking\r\n- Luke Smith -- Enhancement of OS X support\r\n- Michael Smith -- Feature to customize JavaScript executable that is used by\r\n  setting JS_CMD environment variable\r\n- Szil\u00c3\u00a1gyi Szilveszter -- Fixes for bugs when running in Windows\r\n\r\n\r\nLicense\r\n---------\r\n\r\nCopyright (c) 2008-2010 Jesse Hallett <hallettj@gmail.com>, except where\r\notherwise noted\r\n\r\nPermission is hereby granted, free of charge, to any person obtaining a copy of\r\nthis software and associated documentation files (the \"Software\"), to deal in\r\nthe Software without restriction, including without limitation the rights to\r\nuse, copy, modify, merge, publish, distribute, sublicense, and\/or sell copies\r\nof the Software, and to permit persons to whom the Software is furnished to do\r\nso, subject to the following conditions:\r\n\r\nThe above copyright notice and this permission notice shall be included in all\r\ncopies or substantial portions of the Software.\r\n\r\nThe Software shall be used for Good, not Evil.\r\n\r\nTHE SOFTWARE IS PROVIDED \"AS IS\", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR\r\nIMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,\r\nFITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE\r\nAUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER\r\nLIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,\r\nOUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE\r\nSOFTWARE.","install_details":"- Make sure you have a JavaScript interpreter installed.  On Linux jslint.vim\r\n  supports Spidermonkey, Rhino, and node.js.  Spidermonkey or node.js are\r\n  recommended because Rhino tends to have a long startup time.\r\n\r\n  In Ubuntu you can install the Spidermonkey shell with this command:\r\n\r\n        $ sudo apt-get install spidermonkey-bin\r\n\r\n  Latest Ubuntu versions don't have spidermonkey in the default repositories.\r\n  You can use rhino instead:\r\n\r\n        $ sudo apt-get install rhino\r\n\r\n  Or you can find instructions for installing node.js on the node.js website (http:\/\/nodejs.org\/).\r\n\r\n  On Windows you can use `cscript.exe` - which is probably already installed.\r\n\r\n  On MacOS X you don't need to install any JavaScript interpreter because one\r\n  is included with OS X by default.\r\n\r\n- If you have rake installed, run:\r\n\r\n        $ rake install\r\n\r\n  Otherwise copy the directory ftplugin\/ into your Vim ftplugin directory.\r\n  Usually this is `~\/.vim\/ftplugin\/`. On Windows it is `~\/vimfiles\/ftplugin\/`.\r\n","5":"- Make sure you have a JavaScript interpreter installed.  On Linux jslint.vim\r\n  supports Spidermonkey, Rhino, and node.js.  Spidermonkey or node.js are\r\n  recommended because Rhino tends to have a long startup time.\r\n\r\n  In Ubuntu you can install the Spidermonkey shell with this command:\r\n\r\n        $ sudo apt-get install spidermonkey-bin\r\n\r\n  Latest Ubuntu versions don't have spidermonkey in the default repositories.\r\n  You can use rhino instead:\r\n\r\n        $ sudo apt-get install rhino\r\n\r\n  Or you can find instructions for installing node.js on the node.js website (http:\/\/nodejs.org\/).\r\n\r\n  On Windows you can use `cscript.exe` - which is probably already installed.\r\n\r\n  On MacOS X you don't need to install any JavaScript interpreter because one\r\n  is included with OS X by default.\r\n\r\n- If you have rake installed, run:\r\n\r\n        $ rake install\r\n\r\n  Otherwise copy the directory ftplugin\/ into your Vim ftplugin directory.\r\n  Usually this is `~\/.vim\/ftplugin\/`. On Windows it is `~\/vimfiles\/ftplugin\/`.\r\n","first_name":"Jesse","6":"Jesse","last_name":"Hallett","7":"Hallett","releases":[{"0":"2729","vim_version":"6.0","1":"6.0","script_version":"0.7","2":"0.7","version_comment":"- Updated jslint to version 2010-08-08.\r\n- Now checks for errors on leaving insert mode, cursor hold, and buffer save.\r\n- Changed from plugin to ftplugin specific to JavaScript files.\r\n- Supported JavaScript interpreters now include Node.js, Rhino, Spidermonkey,\r\n  Windows Script Host, and that interpreter that is installed by default in Mac\r\n  OS X.\r\n- Added support for overriding the JavaScript interpreter that is used by\r\n  setting a value for the JS_CMD environment variable.\r\n- Fixes bugs when running in Windows.","3":"- Updated jslint to version 2010-08-08.\r\n- Now checks for errors on leaving insert mode, cursor hold, and buffer save.\r\n- Changed from plugin to ftplugin specific to JavaScript files.\r\n- Supported JavaScript interpreters now include Node.js, Rhino, Spidermonkey,\r\n  Windows Script Host, and that interpreter that is installed by default in Mac\r\n  OS X.\r\n- Added support for overriding the JavaScript interpreter that is used by\r\n  setting a value for the JS_CMD environment variable.\r\n- Fixes bugs when running in Windows.","package":"jslint.vim_0.7.tar.bz2","4":"jslint.vim_0.7.tar.bz2","src_id":"13925","5":"13925","creation_date":"1285532497","6":"1285532497"},{"0":"2729","vim_version":"6.0","1":"6.0","script_version":"0.6","2":"0.6","version_comment":"New features","3":"New features","package":"jslint.vim_0.6.tar.bz2","4":"jslint.vim_0.6.tar.bz2","src_id":"11414","5":"11414","creation_date":"1253473860","6":"1253473860"},{"0":"2729","vim_version":"6.0","1":"6.0","script_version":"0.5","2":"0.5","version_comment":"Initial upload","3":"Initial upload","package":"jslint.vim.tar.bz2","4":"jslint.vim.tar.bz2","src_id":"11140","5":"11140","creation_date":"1249592185","6":"1249592185"}]},"2728":{"script_id":"2728","0":"2728","script_name":"tkl.vim","1":"tkl.vim","script_type":"syntax","2":"syntax","summary":"A syntax file to the script files used in the Tikle tool","3":"A syntax file to the script files used in the Tikle tool","description":"A syntax file to the script files used by the Tikle tool.\r\n\r\nMore info about Tikle at http:\/\/c2zlabs.com\r\n\r\nI've only tested this with Vim 7.1 and 7.2","4":"A syntax file to the script files used by the Tikle tool.\r\n\r\nMore info about Tikle at http:\/\/c2zlabs.com\r\n\r\nI've only tested this with Vim 7.1 and 7.2","install_details":"1. Copy the file to ~\/.vim\/syntax\r\n2. Add the following line to your ~\/.vimrc\r\nau BufRead,BufNewFile *.tkl set filetype=tkl\r\n3. Reopen Vim or type :source ~\/.vimrc to reload the configuration.","5":"1. Copy the file to ~\/.vim\/syntax\r\n2. Add the following line to your ~\/.vimrc\r\nau BufRead,BufNewFile *.tkl set filetype=tkl\r\n3. Reopen Vim or type :source ~\/.vimrc to reload the configuration.","first_name":"Higor","6":"Higor","last_name":"Eur\u00c3\u00adpedes","7":"Eur\u00c3\u00adpedes","releases":[{"0":"2728","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"tkl.vim","4":"tkl.vim","src_id":"11124","5":"11124","creation_date":"1249337709","6":"1249337709"}]},"2727":{"script_id":"2727","0":"2727","script_name":"jsbeautify","1":"jsbeautify","script_type":"utility","2":"utility","summary":"a javascript source code formatter","3":"a javascript source code formatter","description":"a plugin to format your javascript souce code\r\n\r\nThe online version is here:\r\nhttp:\/\/jsbeautifier.org\/\r\n\r\nI just translated it into vimscript, it works at a low performance:)\r\n\r\nand since now I don't work as a web developer, this plugin is not maintained..\r\n\r\nusage:\r\n  <leader>ff\r\nor \r\n  bind the g:Jsbeautify() function to any short key you like\r\n","4":"a plugin to format your javascript souce code\r\n\r\nThe online version is here:\r\nhttp:\/\/jsbeautifier.org\/\r\n\r\nI just translated it into vimscript, it works at a low performance:)\r\n\r\nand since now I don't work as a web developer, this plugin is not maintained..\r\n\r\nusage:\r\n  <leader>ff\r\nor \r\n  bind the g:Jsbeautify() function to any short key you like\r\n","install_details":"put it in your:\r\nvimfiles\/plugin","5":"put it in your:\r\nvimfiles\/plugin","first_name":"aj3423","6":"aj3423","last_name":" ","7":" ","releases":[{"0":"2727","vim_version":"7.2","1":"7.2","script_version":"N\/A","2":"N\/A","version_comment":"Initial upload","3":"Initial upload","package":"jsbeautify.vim","4":"jsbeautify.vim","src_id":"11120","5":"11120","creation_date":"1249270235","6":"1249270235"}]},"2726":{"script_id":"2726","0":"2726","script_name":"Syntax Highlighting for db2diag.log","1":"Syntax Highlighting for db2diag.log","script_type":"syntax","2":"syntax","summary":"Syntax plug in for IBM DB2 diagnostic log file","3":"Syntax plug in for IBM DB2 diagnostic log file","description":"This syntax plug-in highlights the main fields in a db2diag.log file.","4":"This syntax plug-in highlights the main fields in a db2diag.log file.","install_details":"1. Copy the db2diag.log.vim file into the  ~\/.vim\/syntax\/ directory.\r\n2. Add this to your ~\/.vimrc file:\r\n\r\n    syntax on\r\n\r\n3. Create a  ~\/.vim\/ftdetect\/db2diaglog.vim file with this line in it to make Vim apply the syntax automatically, based of the file name:\r\n\r\n    autocmd BufNewFile,BufRead db2diag.log setfiletype db2diaglog\r\n\r\n    * Alternatively, you can skip this step and specify the file type every time you need the syntax by running this command:\r\n\r\n    :set filetype=db2diaglog\r\n\r\n4. Open your db2diag.log file.  You should see the colours!\r\n","5":"1. Copy the db2diag.log.vim file into the  ~\/.vim\/syntax\/ directory.\r\n2. Add this to your ~\/.vimrc file:\r\n\r\n    syntax on\r\n\r\n3. Create a  ~\/.vim\/ftdetect\/db2diaglog.vim file with this line in it to make Vim apply the syntax automatically, based of the file name:\r\n\r\n    autocmd BufNewFile,BufRead db2diag.log setfiletype db2diaglog\r\n\r\n    * Alternatively, you can skip this step and specify the file type every time you need the syntax by running this command:\r\n\r\n    :set filetype=db2diaglog\r\n\r\n4. Open your db2diag.log file.  You should see the colours!\r\n","first_name":"Jacobo","6":"Jacobo","last_name":"de Vera","7":"de Vera","releases":[{"0":"2726","vim_version":"6.0","1":"6.0","script_version":"1.0.0","2":"1.0.0","version_comment":"Initial upload","3":"Initial upload","package":"db2diaglog.vim","4":"db2diaglog.vim","src_id":"11107","5":"11107","creation_date":"1248991827","6":"1248991827"}]},"2725":{"script_id":"2725","0":"2725","script_name":"translit_converter","1":"translit_converter","script_type":"utility","2":"utility","summary":"convert transliterated text (russian)","3":"convert transliterated text (russian)","description":"This plugin creates commands for converting from and to Russian translit using utf-8 encoding. For example, to write \"Чебурашка\", write \"Cheburashka\" or \"CHeburashka\", select the word and execute command \":Torus v\" .\r\n\r\nSimilar plugins:\r\nhttp:\/\/www.vim.org\/scripts\/script.php?script_id=2401\r\nhttp:\/\/www.vim.org\/scripts\/script.php?script_id=2469\r\n\r\nUSAGE\r\n=====\r\nThis plugin creates two commands: Torussian and Fromrussian.\r\n\r\n:[range]Torussian [v]\r\n    convert from translit (latin alphabet) to Russian (utf-8)\r\n\r\n:[range]Fromrussian [v]\r\n    convert from Russian (utf-8) to translit\r\n\r\nThese can be used as follows (commands can be abbreviated):\r\n\r\n:Torus\r\n    Convert current line.\r\n\r\n:'<,'>Torus\r\n    Convert lines in Visual range. Any other range can be specified, for example :%Torus will convert entire buffer.\r\n\r\n:Torus v\r\n:'<,'>Torus v\r\n    Convert text in Visual area. If a range is specified, it is ignored.\r\n\r\nCUSTOMIZING\r\n===========\r\nIf you don't like my transliteration version, edit s:table_ru.\r\n\r\nIt is easy to add converters for other alphabets. First, create conversion table:\r\n    let s:table_greek = [ ..... ]\r\n\r\nAnd then add new commands:\r\n    com! -range -nargs=? Togreek   call s:Translit_Converter(<line1>,<line2>, 'table_greek', 0,1, <q-args>)\r\n    com! -range -nargs=? Fromgreek call s:Translit_Converter(<line1>,<line2>, 'table_greek', 1,0, <q-args>)\r\n","4":"This plugin creates commands for converting from and to Russian translit using utf-8 encoding. For example, to write \"Чебурашка\", write \"Cheburashka\" or \"CHeburashka\", select the word and execute command \":Torus v\" .\r\n\r\nSimilar plugins:\r\nhttp:\/\/www.vim.org\/scripts\/script.php?script_id=2401\r\nhttp:\/\/www.vim.org\/scripts\/script.php?script_id=2469\r\n\r\nUSAGE\r\n=====\r\nThis plugin creates two commands: Torussian and Fromrussian.\r\n\r\n:[range]Torussian [v]\r\n    convert from translit (latin alphabet) to Russian (utf-8)\r\n\r\n:[range]Fromrussian [v]\r\n    convert from Russian (utf-8) to translit\r\n\r\nThese can be used as follows (commands can be abbreviated):\r\n\r\n:Torus\r\n    Convert current line.\r\n\r\n:'<,'>Torus\r\n    Convert lines in Visual range. Any other range can be specified, for example :%Torus will convert entire buffer.\r\n\r\n:Torus v\r\n:'<,'>Torus v\r\n    Convert text in Visual area. If a range is specified, it is ignored.\r\n\r\nCUSTOMIZING\r\n===========\r\nIf you don't like my transliteration version, edit s:table_ru.\r\n\r\nIt is easy to add converters for other alphabets. First, create conversion table:\r\n    let s:table_greek = [ ..... ]\r\n\r\nAnd then add new commands:\r\n    com! -range -nargs=? Togreek   call s:Translit_Converter(<line1>,<line2>, 'table_greek', 0,1, <q-args>)\r\n    com! -range -nargs=? Fromgreek call s:Translit_Converter(<line1>,<line2>, 'table_greek', 1,0, <q-args>)\r\n","install_details":"Source the script or put it in your local plugin folder:\r\n~\/.vim\/plugin\/  or  $HOME\\vimfiles\\plugin\\","5":"Source the script or put it in your local plugin folder:\r\n~\/.vim\/plugin\/  or  $HOME\\vimfiles\\plugin\\","first_name":"Vlad","6":"Vlad","last_name":"Irnov","7":"Irnov","releases":[{"0":"2725","vim_version":"7.0","1":"7.0","script_version":"1.1","2":"1.1","version_comment":"fixed error in setting 'cpoptions'","3":"fixed error in setting 'cpoptions'","package":"translit_converter.vim","4":"translit_converter.vim","src_id":"11947","5":"11947","creation_date":"1261635744","6":"1261635744"},{"0":"2725","vim_version":"7.0","1":"7.0","script_version":"1.01","2":"1.01","version_comment":"made some variables script-local","3":"made some variables script-local","package":"translit_converter.vim","4":"translit_converter.vim","src_id":"11190","5":"11190","creation_date":"1250276356","6":"1250276356"}]},"2724":{"script_id":"2724","0":"2724","script_name":"Rename2","1":"Rename2","script_type":"utility","2":"utility","summary":"Rename the file you are currently editing and keep on editing","3":"Rename the file you are currently editing and keep on editing","description":"This is really just a bugfix for the original Rename script by Christian J. Robinson (vimscript#1928) which suffered from the fact that it did not consider the possibility that the file in the current buffer might no reside in the current directory. \r\nIn my version, the new file will always end up in the directory of the original file.","4":"This is really just a bugfix for the original Rename script by Christian J. Robinson (vimscript#1928) which suffered from the fact that it did not consider the possibility that the file in the current buffer might no reside in the current directory. \r\nIn my version, the new file will always end up in the directory of the original file.","install_details":"Simply copy the script to your ~\/.vim\/plugin directory.","5":"Simply copy the script to your ~\/.vim\/plugin directory.","first_name":"Manni","6":"Manni","last_name":"Heumann","7":"Heumann","releases":[{"0":"2724","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"Rename2.vim","4":"Rename2.vim","src_id":"11097","5":"11097","creation_date":"1248962767","6":"1248962767"}]},"2723":{"script_id":"2723","0":"2723","script_name":"math","1":"math","script_type":"utility","2":"utility","summary":"Math keymap and a menu for inserting math symbols","3":"Math keymap and a menu for inserting math symbols","description":"This plugin has three parts, a keymap, a menu for inserting math symbols, and a few maps.  The characters produced are in utf-8.\r\n\r\nThe Keymap:\r\n\r\n  :set kmp=math\r\n\r\n  Uses vim's keymap support to define key sequences which elicit Greek\r\n  upper case and lower case symbols, superscripts, subscripts, \"vulgar\"\r\n  fractions, arrows, grouping symbols, operators, relational symbols,\r\n  set symbols, and of course the ever popular miscellaneous.\r\n\r\nThe Menu:\r\n  To enable the menu, use the mouse to select  [DrChip.MathKeys.Enable].\r\n  This menu operates in the insert\/replace\/ex mode; when in insert\/replace\/ex,\r\n  use the mouse to select a symbol from the various menus and it will be\r\n  inserted.\r\n\r\nThe Maps:\r\n  While in visual block mode, and if :MathStart has been run:\r\n  _  will make various symbols into subscript symbols (numbers, vowels)\r\n  ^ will make various symbols into superscript symbols\r\n  & will transform symbols into related math symbols (- into a division line, roman alphabet into Greek, etc)\r\n\r\n(alpha\/beta version available at http:\/\/www.drchip.org\/astronaut\/vim\/index.html#MATH)\r\n","4":"This plugin has three parts, a keymap, a menu for inserting math symbols, and a few maps.  The characters produced are in utf-8.\r\n\r\nThe Keymap:\r\n\r\n  :set kmp=math\r\n\r\n  Uses vim's keymap support to define key sequences which elicit Greek\r\n  upper case and lower case symbols, superscripts, subscripts, \"vulgar\"\r\n  fractions, arrows, grouping symbols, operators, relational symbols,\r\n  set symbols, and of course the ever popular miscellaneous.\r\n\r\nThe Menu:\r\n  To enable the menu, use the mouse to select  [DrChip.MathKeys.Enable].\r\n  This menu operates in the insert\/replace\/ex mode; when in insert\/replace\/ex,\r\n  use the mouse to select a symbol from the various menus and it will be\r\n  inserted.\r\n\r\nThe Maps:\r\n  While in visual block mode, and if :MathStart has been run:\r\n  _  will make various symbols into subscript symbols (numbers, vowels)\r\n  ^ will make various symbols into superscript symbols\r\n  & will transform symbols into related math symbols (- into a division line, roman alphabet into Greek, etc)\r\n\r\n(alpha\/beta version available at http:\/\/www.drchip.org\/astronaut\/vim\/index.html#MATH)\r\n","install_details":"vim math.vba.gz\r\n:so %\r\n:q\r\n","5":"vim math.vba.gz\r\n:so %\r\n:q\r\n","first_name":"Charles","6":"Charles","last_name":"Campbell","7":"Campbell","releases":[{"0":"2723","vim_version":"7.0","1":"7.0","script_version":"3","2":"3","version_comment":"more symbols and new visual-mode maps (& ^ _ ) to facilitate math symbol production!  Example:   x2 , put cursor on the 2, press v^  and you\\'ve got x\u00c2\u00b2  (for those whose browsers don\\'t grok utf-8, that 2 is a superscript)\r\n","3":"more symbols and new visual-mode maps (& ^ _ ) to facilitate math symbol production!  Example:   x2 , put cursor on the 2, press v^  and you\\'ve got x\u00c2\u00b2  (for those whose browsers don\\'t grok utf-8, that 2 is a superscript)\r\n","package":"math.vba.gz","4":"math.vba.gz","src_id":"12554","5":"12554","creation_date":"1267720125","6":"1267720125"},{"0":"2723","vim_version":"7.0","1":"7.0","script_version":"2","2":"2","version_comment":"More symbols and ex-mode support","3":"More symbols and ex-mode support","package":"math.vba.gz","4":"math.vba.gz","src_id":"11665","5":"11665","creation_date":"1257522464","6":"1257522464"},{"0":"2723","vim_version":"7.0","1":"7.0","script_version":"1","2":"1","version_comment":"Initial upload with GetLatestVimScripts support","3":"Initial upload with GetLatestVimScripts support","package":"math.vba.gz","4":"math.vba.gz","src_id":"11087","5":"11087","creation_date":"1248882165","6":"1248882165"}]},"2722":{"script_id":"2722","0":"2722","script_name":"cssvar","1":"cssvar","script_type":"ftplugin","2":"ftplugin","summary":"Use variables in CSS","3":"Use variables in CSS","description":"This plugin allows you to define and use variables in stylesheets and make simple calculations with them, like this:\r\n\r\n    [pagewidth = 1000]\r\n    #wrapper { \r\n        width: [pagewidth]px;\r\n        margin: [pagewidth\/4]px}\r\n\r\nIn the target CSS file this will become:\r\n\r\n    #wrapper { \r\n        width: 1000px;\r\n        margin: 250px}\r\n\r\nYou can assign the value of a color to a variable and use it anywhere in the stylesheet. When you change the assignment, the value is updated in the whole stylesheet.\r\n\r\n    [textcolor = #09c]\r\n    h1 {color: [textcolor]}\r\n\r\nThe variables are surrounded by two delimiters which you can define in the plugin file (or anywhere in the stylesheet). In the examples above square brackets are used but any printable ascii character, not used in the CSS code, will do. \r\n\r\n    ^textcolor = #09c$\r\n\r\nIt's possible to define the same character as opening and closing delimiter.\r\n\r\n    |textcolor = #09c|\r\n\r\nHOW IT WORKS\r\nThe plugin uses two CSS files. One source file (in the current buffer) with the CSS code and variables and one target file with pure CSS and calculated variables. This last file is generated when the plugin is invoked and you should link to this file in the (X)HTML.\r\n","4":"This plugin allows you to define and use variables in stylesheets and make simple calculations with them, like this:\r\n\r\n    [pagewidth = 1000]\r\n    #wrapper { \r\n        width: [pagewidth]px;\r\n        margin: [pagewidth\/4]px}\r\n\r\nIn the target CSS file this will become:\r\n\r\n    #wrapper { \r\n        width: 1000px;\r\n        margin: 250px}\r\n\r\nYou can assign the value of a color to a variable and use it anywhere in the stylesheet. When you change the assignment, the value is updated in the whole stylesheet.\r\n\r\n    [textcolor = #09c]\r\n    h1 {color: [textcolor]}\r\n\r\nThe variables are surrounded by two delimiters which you can define in the plugin file (or anywhere in the stylesheet). In the examples above square brackets are used but any printable ascii character, not used in the CSS code, will do. \r\n\r\n    ^textcolor = #09c$\r\n\r\nIt's possible to define the same character as opening and closing delimiter.\r\n\r\n    |textcolor = #09c|\r\n\r\nHOW IT WORKS\r\nThe plugin uses two CSS files. One source file (in the current buffer) with the CSS code and variables and one target file with pure CSS and calculated variables. This last file is generated when the plugin is invoked and you should link to this file in the (X)HTML.\r\n","install_details":"Put css_var.vim in your file type plugin directory ~\/.vim\/ftplugin.\r\nOpen the file and change the defaults to your liking.\r\nIncluded in the zip archive is a css test file and documentation.\r\n\r\nTo invoke the plugin:\r\n:call CSSvar()\r\n\r\nYou can put a mapping in your .vimrc to call the plugin like this:\r\nnmap <F5> <Plug>CSSvar\r\nimap <F5> <C-O><Plug>CSSvar\r\n\r\nREQUIREMENTS\r\nThis plugin requires Python-enabled Vim.\r\nTested with Vim 7.1 and Python 2.5.2 on Linux and with MacVim on Mac OS X.\r\n","5":"Put css_var.vim in your file type plugin directory ~\/.vim\/ftplugin.\r\nOpen the file and change the defaults to your liking.\r\nIncluded in the zip archive is a css test file and documentation.\r\n\r\nTo invoke the plugin:\r\n:call CSSvar()\r\n\r\nYou can put a mapping in your .vimrc to call the plugin like this:\r\nnmap <F5> <Plug>CSSvar\r\nimap <F5> <C-O><Plug>CSSvar\r\n\r\nREQUIREMENTS\r\nThis plugin requires Python-enabled Vim.\r\nTested with Vim 7.1 and Python 2.5.2 on Linux and with MacVim on Mac OS X.\r\n","first_name":"Benno","6":"Benno","last_name":"van Keulen","7":"van Keulen","releases":[{"0":"2722","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"cssvar.zip","4":"cssvar.zip","src_id":"11078","5":"11078","creation_date":"1248811156","6":"1248811156"}]},"2721":{"script_id":"2721","0":"2721","script_name":"AutoFenc","1":"AutoFenc","script_type":"utility","2":"utility","summary":"Tries to automatically detect and set file encoding","3":"Tries to automatically detect and set file encoding","description":"A Vim plugin that tries to automatically detect and set file encoding when opening a file. See https:\/\/github.com\/s3rvac\/AutoFenc for more details and configuration options.\r\n","4":"A Vim plugin that tries to automatically detect and set file encoding when opening a file. See https:\/\/github.com\/s3rvac\/AutoFenc for more details and configuration options.\r\n","install_details":"Put the AutoFenc.vim file into your $HOME\/.vim\/plugin directory (Linux-like systems) or %UserProfile%\\vimfiles\\plugin folder (Windows systems).","5":"Put the AutoFenc.vim file into your $HOME\/.vim\/plugin directory (Linux-like systems) or %UserProfile%\\vimfiles\\plugin folder (Windows systems).","first_name":"Petr","6":"Petr","last_name":"Zemek","7":"Zemek","releases":[{"0":"2721","vim_version":"7.0","1":"7.0","script_version":"1.5.1","2":"1.5.1","version_comment":"- Cleanup.\r\n- Put the sources to GitHub (https:\/\/github.com\/s3rvac\/AutoFenc).","3":"- Cleanup.\r\n- Put the sources to GitHub (https:\/\/github.com\/s3rvac\/AutoFenc).","package":"AutoFenc.vim","4":"AutoFenc.vim","src_id":"21853","5":"21853","creation_date":"1399100448","6":"1399100448"},{"0":"2721","vim_version":"7.0","1":"7.0","script_version":"1.5","2":"1.5","version_comment":"Thanks to Ingo Karkat for the updates in this version.\r\n- Supported HTML\/XML\/CSS file types have been made configurable and added more defaults.\r\n- Do not emit the \"unrecognized charset\" message when the encoding is known.","3":"Thanks to Ingo Karkat for the updates in this version.\r\n- Supported HTML\/XML\/CSS file types have been made configurable and added more defaults.\r\n- Do not emit the \"unrecognized charset\" message when the encoding is known.","package":"AutoFenc.vim","4":"AutoFenc.vim","src_id":"17602","5":"17602","creation_date":"1331980940","6":"1331980940"},{"0":"2721","vim_version":"7.0","1":"7.0","script_version":"1.4","2":"1.4","version_comment":"Thanks to Ingo Karkat for the updates in this version.\r\n- Improved the detection regexp for comments:\r\n    - added \"fileencoding\" and \"charset\";\r\n    - demands that there is a whitespace in front of the keyword, so that \"daycoding\" doesn't match;\r\n    - g:autofenc_autodetect_commentexpr allows to configure the pattern for comment detection.\r\n- Introduced g:autofenc_enc_blacklist to disable some encodings. For example, the enca tool has a tendency to detect plain text files as UTF-7. With the blacklist, AutoFenc can be instructed to ignore those encodings.\r\n- The check for ASCII is set to be case-insensitive because enca reports this in uppercase, so the condition fails unless ignorecase is set.\r\n- Keeps changed CWD with 'autochdir' setting by temporarily disabling it. For example, suppose that a user has \":lcd ..\" in after\/ftplugin\/gitcommit.vim and that he is in the Git root directory, not the .git subdir when composing a commit message. The reload of the buffer by AutoFenc (via :edit) again triggered the automatic change of the working dir, and therefore the customization was lost. The 'autochdir' setting needs to be temporarily disabled to avoid that.\r\n- Added a support for plain Vim 7.0 in the shellescape() emulation from version 1.3.4. Otherwise, there were errors in Vim 7.0.","3":"Thanks to Ingo Karkat for the updates in this version.\r\n- Improved the detection regexp for comments:\r\n    - added \"fileencoding\" and \"charset\";\r\n    - demands that there is a whitespace in front of the keyword, so that \"daycoding\" doesn't match;\r\n    - g:autofenc_autodetect_commentexpr allows to configure the pattern for comment detection.\r\n- Introduced g:autofenc_enc_blacklist to disable some encodings. For example, the enca tool has a tendency to detect plain text files as UTF-7. With the blacklist, AutoFenc can be instructed to ignore those encodings.\r\n- The check for ASCII is set to be case-insensitive because enca reports this in uppercase, so the condition fails unless ignorecase is set.\r\n- Keeps changed CWD with 'autochdir' setting by temporarily disabling it. For example, suppose that a user has \":lcd ..\" in after\/ftplugin\/gitcommit.vim and that he is in the Git root directory, not the .git subdir when composing a commit message. The reload of the buffer by AutoFenc (via :edit) again triggered the automatic change of the working dir, and therefore the customization was lost. The 'autochdir' setting needs to be temporarily disabled to avoid that.\r\n- Added a support for plain Vim 7.0 in the shellescape() emulation from version 1.3.4. Otherwise, there were errors in Vim 7.0.","package":"AutoFenc.vim","4":"AutoFenc.vim","src_id":"17586","5":"17586","creation_date":"1331462175","6":"1331462175"},{"0":"2721","vim_version":"7.0","1":"7.0","script_version":"1.3.4","2":"1.3.4","version_comment":"- Don't override when the user explicitly sets file encoding with ++enc (thanks to Benjamin Fritz).\r\n- Fixed TOhtml version detection (again) and made sure line continuations can actually be used (thanks to Benjamin Fritz and Ingo Karkat).\r\n- Disabled the option shellslash on Windows before calling shellescape() (it may cause problems on Windows, thanks for the tip goes to Benjamin Fritz).\r\n","3":"- Don't override when the user explicitly sets file encoding with ++enc (thanks to Benjamin Fritz).\r\n- Fixed TOhtml version detection (again) and made sure line continuations can actually be used (thanks to Benjamin Fritz and Ingo Karkat).\r\n- Disabled the option shellslash on Windows before calling shellescape() (it may cause problems on Windows, thanks for the tip goes to Benjamin Fritz).\r\n","package":"AutoFenc.vim","4":"AutoFenc.vim","src_id":"17534","5":"17534","creation_date":"1330359414","6":"1330359414"},{"0":"2721","vim_version":"7.0","1":"7.0","script_version":"1.3.3","2":"1.3.3","version_comment":"Thanks to Ingo Karkat for the updates in this version.\r\n- Fixed a problem in the TOhtml detection when, for example, g:loaded_2html_plugin = 'vim7.3_v6'.\r\n- The return code of the call of an external program via system(ext_prog_cmd) is now checked. This prevents Vim interpreting an error message as an encoding.\r\n- shellescape() is now used instead of quoting file_path manually.\r\n","3":"Thanks to Ingo Karkat for the updates in this version.\r\n- Fixed a problem in the TOhtml detection when, for example, g:loaded_2html_plugin = 'vim7.3_v6'.\r\n- The return code of the call of an external program via system(ext_prog_cmd) is now checked. This prevents Vim interpreting an error message as an encoding.\r\n- shellescape() is now used instead of quoting file_path manually.\r\n","package":"AutoFenc.vim","4":"AutoFenc.vim","src_id":"16994","5":"16994","creation_date":"1322593242","6":"1322593242"},{"0":"2721","vim_version":"7.0","1":"7.0","script_version":"1.3.2","2":"1.3.2","version_comment":"Thanks to Benjamin Fritz for the updates in this version.\r\n- Fixed the detection of the version of the TOhtml plugin.\r\n","3":"Thanks to Benjamin Fritz for the updates in this version.\r\n- Fixed the detection of the version of the TOhtml plugin.\r\n","package":"AutoFenc.vim","4":"AutoFenc.vim","src_id":"16954","5":"16954","creation_date":"1322140101","6":"1322140101"},{"0":"2721","vim_version":"7.0","1":"7.0","script_version":"1.3.1","2":"1.3.1","version_comment":"Thanks to Benjamin Fritz for the updates in this version.\r\n - Fixed the plugin behavior when reloading a file with different settings.\r\n","3":"Thanks to Benjamin Fritz for the updates in this version.\r\n - Fixed the plugin behavior when reloading a file with different settings.\r\n","package":"AutoFenc.vim","4":"AutoFenc.vim","src_id":"16129","5":"16129","creation_date":"1311414630","6":"1311414630"},{"0":"2721","vim_version":"7.0","1":"7.0","script_version":"1.3","2":"1.3","version_comment":"Thanks to Benjamin Fritz for the updates in this version.\r\n  - Added support for HTML version 5 encoding detection.\r\n  - The script now dies gracefully in old Vims.\r\n  - 'g:autofenc_autodetect_comment_num_of_lines' renamed to 'g:autofenc_autodetect_num_of_lines'\r\n","3":"Thanks to Benjamin Fritz for the updates in this version.\r\n  - Added support for HTML version 5 encoding detection.\r\n  - The script now dies gracefully in old Vims.\r\n  - 'g:autofenc_autodetect_comment_num_of_lines' renamed to 'g:autofenc_autodetect_num_of_lines'\r\n","package":"AutoFenc.vim","4":"AutoFenc.vim","src_id":"15505","5":"15505","creation_date":"1303483558","6":"1303483558"},{"0":"2721","vim_version":"7.0","1":"7.0","script_version":"1.2.1","2":"1.2.1","version_comment":"Fixed a typo in a variable name (this resulted in an error in some occasions). Thanks to Charles Lee for pointing this bug out.","3":"Fixed a typo in a variable name (this resulted in an error in some occasions). Thanks to Charles Lee for pointing this bug out.","package":"AutoFenc.vim","4":"AutoFenc.vim","src_id":"15445","5":"15445","creation_date":"1302709932","6":"1302709932"},{"0":"2721","vim_version":"7.0","1":"7.0","script_version":"1.2","2":"1.2","version_comment":"Thanks to Benjamin Fritz for the updates in this version.\r\n  - TOhtml's IANA name\/Vim encoding conversion functions are now used.\r\n  - Changed BOM detection so it does not duplicate a check Vim already did by default (i.e. default to off if ucs-bom is in the 'fileencodings').\r\n  - Put autocmds in the AutoFenc augroup for easier handling.\r\n  - Made autocmd nested so we don't need to worry about restoring everything that other autocmds may set (e.g. syntax).\r\n  - Jumplist or cursor position during detection are not affected.\r\n  - The g:autofenc_autodetect_comment_num_of_lines option is now used also in HTML\/XML\/CSS detection routines (previously only used for encoding specified in comments).\r\n  - Improved HTML charset line regex.\r\n  - Added an option (g:autofenc_emit_messages) to emit messages about the detected\/used encoding upon opening a file. ","3":"Thanks to Benjamin Fritz for the updates in this version.\r\n  - TOhtml's IANA name\/Vim encoding conversion functions are now used.\r\n  - Changed BOM detection so it does not duplicate a check Vim already did by default (i.e. default to off if ucs-bom is in the 'fileencodings').\r\n  - Put autocmds in the AutoFenc augroup for easier handling.\r\n  - Made autocmd nested so we don't need to worry about restoring everything that other autocmds may set (e.g. syntax).\r\n  - Jumplist or cursor position during detection are not affected.\r\n  - The g:autofenc_autodetect_comment_num_of_lines option is now used also in HTML\/XML\/CSS detection routines (previously only used for encoding specified in comments).\r\n  - Improved HTML charset line regex.\r\n  - Added an option (g:autofenc_emit_messages) to emit messages about the detected\/used encoding upon opening a file. ","package":"AutoFenc.vim","4":"AutoFenc.vim","src_id":"15348","5":"15348","creation_date":"1301604477","6":"1301604477"},{"0":"2721","vim_version":"7.0","1":"7.0","script_version":"1.1.1","2":"1.1.1","version_comment":"Fixed the comment encoding detection function (see changelog).","3":"Fixed the comment encoding detection function (see changelog).","package":"AutoFenc.vim","4":"AutoFenc.vim","src_id":"11477","5":"11477","creation_date":"1254598302","6":"1254598302"},{"0":"2721","vim_version":"7.0","1":"7.0","script_version":"1.1","2":"1.1","version_comment":"Added three configuration possibilites to disable autodetection for specific files (based on file size, file type and file path). See script description for more info.\r\n","3":"Added three configuration possibilites to disable autodetection for specific files (based on file size, file type and file path). See script description for more info.\r\n","package":"AutoFenc.vim","4":"AutoFenc.vim","src_id":"11200","5":"11200","creation_date":"1250451361","6":"1250451361"},{"0":"2721","vim_version":"7.0","1":"7.0","script_version":"1.0.2","2":"1.0.2","version_comment":"Fixed the XML encoding detection function and minor code and documentation fixes.","3":"Fixed the XML encoding detection function and minor code and documentation fixes.","package":"AutoFenc.vim","4":"AutoFenc.vim","src_id":"11177","5":"11177","creation_date":"1250013916","6":"1250013916"},{"0":"2721","vim_version":"7.0","1":"7.0","script_version":"1.0.1","2":"1.0.1","version_comment":"Three bugfixes (see changelog).","3":"Three bugfixes (see changelog).","package":"AutoFenc.vim","4":"AutoFenc.vim","src_id":"11119","5":"11119","creation_date":"1249239648","6":"1249239648"},{"0":"2721","vim_version":"7.2","1":"7.2","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"AutoFenc.vim","4":"AutoFenc.vim","src_id":"11067","5":"11067","creation_date":"1248600963","6":"1248600963"}]},"2720":{"script_id":"2720","0":"2720","script_name":"arc.vim","1":"arc.vim","script_type":"syntax","2":"syntax","summary":"A syntax highlighter & filetype plugin for Paul Graham's Arc Lisp dialect.","3":"A syntax highlighter & filetype plugin for Paul Graham's Arc Lisp dialect.","description":"(Scroll down to see the install details.)\r\n\r\nNote: if you have a bug to report, please do so with the issue tracker at http:\/\/bitbucket.org\/fallintothis\/arc-vim\/issues\/ since I probably won't respond to emails.\r\n\r\nI've only tested this on Vim 7.2.  I have no idea (one way or the other) how backwards-compatible it is.\r\n\r\nSYNTAX:\r\n\r\nThe following options are available for customizing the Arc highlighter.  They work well in conjunction with the accompanying Arc ftplugin options (see below).\r\n\r\n- g:arc_rainbow\r\n\r\nIf this variable is nonzero, then matching pairs of parentheses will highlight in 10 different rainbow colors.  If this variable is 0, then rainbow colors are gone; it's just normal parentheses and quasiquoted parentheses.\r\n\r\n- g:arc_always_atstrings\r\n\r\nIn Arc 3, there is an option to enable string interpolation of arbitrary expressions using at-signs by saying\r\n  \r\n  (declare 'atstrings t)\r\n\r\nThen, for instance, \"1 + 2 = @(+ 1 2)\" is the same as \"1 + 2 = 3\".  If g:arc_always_atstrings is nonzero, then expressions after the @-symbol inside of strings will be highlighted like normal code, as though you had (declare 'atstrings t).  If this variable is 0, then atstrings will not highlight.\r\n\r\nIf you want more intelligent control over atstring highlighting, check out the accompanying ftplugin options below.\r\n\r\nEXAMPLE:\r\n\r\nYou could put\r\n\r\n  let g:arc_always_atstrings=1\r\n\r\nin your .vimrc, and whenever you were highlighting an Arc file, atstrings would highlight, but parentheses would be colored normally (non-rainbow), since you don't have to explicitly set either variable to 0.  If they don't exist, they'll do nothing anyways.\r\n\r\nFTPLUGIN:\r\n\r\nThe following options are available for customizing the Arc ftplugin.  They are meant to work in conjunction with the accompanying Arc syntax highlighter (see above).\r\n\r\n- g:arc_detect_atstrings\r\n\r\nIn Arc 3, there is an option to enable string interpolation of arbitrary expressions using at-signs by saying\r\n  \r\n  (declare 'atstrings t)\r\n\r\nThen, for instance, \"1 + 2 = @(+ 1 2)\" is the same as \"1 + 2 = 3\".  If g:arc_detect_atstrings is nonzero, then expressions after the @-symbol inside of strings will be highlighted like normal code according to the following cases:\r\n\r\n  - if a form that will enable atstrings, like\r\n      (declare 'atstrings t)\r\n    is in the source code, highlight expressions after @-symbols\r\n\r\n  - if a form that will disable atstrings, like\r\n      (declare 'atstrings nil)\r\n    is in the source code, do not highlight expressions after @-symbols\r\n\r\n  - if there are multiple forms that contradict each other (enabling\r\n    atstrings in one place while disabling them in another), then be safe and\r\n    do not highlight expressions after @-symbols.\r\n\r\nThis option can be used as an alternative to g:arc_always_atstrings, which is found in the Arc syntax highlighter (see above).  If, however, g:arc_always_atstrings is nonzero, it will take precedence over g:arc_detect_atstrings and always highlight atstrings.  When g:arc_always_atstrings is 0, behavior is dictated by g:arc_detect_atstrings.\r\n\r\nChanges in highlighting are triggered whenever you write to the file.  If you change, say\r\n\r\n  (declare 'atstrings t)\r\n\r\nto\r\n\r\n  (declare 'atstrings nil)\r\n\r\nthen :w, the atstring highlighting will be turned off.\r\n\r\n- g:arc_bodops\r\n\r\nIMPORTANT: This feature is currently available only if your Vim installation has +python support.  See :h python\r\n\r\nIf this variable is nonzero, then on every file write your source code is inspected in an attempt to find top-level macro definitions that have body parameters.  That is, \r\n\r\n  (mac foo (vars vals . body)\r\n    something)\r\n\r\nwill be detected, because it is a macro that takes a rest parameter named \"body\".  Whereas\r\n\r\n  (def foo (a b . body)\r\n    something)\r\n\r\nwill not, because it's not a macro definition, and\r\n\r\n  (def make-macro (name)\r\n    `(mac ,name body (pr \"stuff\")))\r\n\r\nwill not recognize the quasiquoted macro definition, even though it takes a body parameter.\r\n\r\nThe name of each macro found in this way will be added to the &lispwords variable.  Then, with auto-indentation, the macro\r\n\r\n  (mac foo body\r\n    bar)\r\n\r\nwill indent like\r\n\r\n  (foo a\r\n    b\r\n    c)\r\n\r\ninstead of\r\n\r\n  (foo a\r\n       b\r\n       c)\r\n\r\n(Sorry; that probably doesn't look right in a non-fixed-width font.)  This can be useful for macros that you define to be syntactic forms, much like how, say, looping constructs are defined in Arc itself.\r\n\r\n- g:arc_highlight_lispwords\r\n\r\nIf nonzero, every word in the &lispwords variable will highlight as though it were syntax.  The highlighting is updated every time you write to the file.  This can be useful in conjunction with g:arc_bodops, so that after you write the macro\r\n\r\n  (mac my-each (x xs . body)\r\n    ...do stuff...)\r\n\r\neach occurrence of \"my-each\" will be highlighted & indented just like the \"each\" macro.  You can even add words you want to be highlighted & indented by going\r\n\r\n  :setl lispwords+=foo\r\n\r\nThis lispword will then persist across file-writes, even if you've not defined a \"foo\" macro.\r\n\r\nMost of these extra features are useless without the accompanying Arc syntax highlighter, so you probably want to use it if you use these features.\r\n\r\nEXAMPLE:\r\n\r\nYou could put\r\n\r\n  let g:arc_detect_atstrings=1\r\n  let g:arc_bodops=1\r\n  let g:arc_highlight_lispwords=1\r\n\r\nin your .vimrc, and when using the Arc syntax highlighter you can test, say, news.arc and see that:\r\n\r\n  - atstrings are highlighted, as there is a positive declaration at the top of the source\r\n  \r\n  - macros like \"adop\" and \"edop\" are highlighted & auto-indented as lispwords\r\n\r\n  - but the macro \"newsop\" isn't highlighted or auto-indented, because its rest parameter is named \"args\".  So, you can :setl lw+=newsop and :w to see \"newsop\" become highlighted.","4":"(Scroll down to see the install details.)\r\n\r\nNote: if you have a bug to report, please do so with the issue tracker at http:\/\/bitbucket.org\/fallintothis\/arc-vim\/issues\/ since I probably won't respond to emails.\r\n\r\nI've only tested this on Vim 7.2.  I have no idea (one way or the other) how backwards-compatible it is.\r\n\r\nSYNTAX:\r\n\r\nThe following options are available for customizing the Arc highlighter.  They work well in conjunction with the accompanying Arc ftplugin options (see below).\r\n\r\n- g:arc_rainbow\r\n\r\nIf this variable is nonzero, then matching pairs of parentheses will highlight in 10 different rainbow colors.  If this variable is 0, then rainbow colors are gone; it's just normal parentheses and quasiquoted parentheses.\r\n\r\n- g:arc_always_atstrings\r\n\r\nIn Arc 3, there is an option to enable string interpolation of arbitrary expressions using at-signs by saying\r\n  \r\n  (declare 'atstrings t)\r\n\r\nThen, for instance, \"1 + 2 = @(+ 1 2)\" is the same as \"1 + 2 = 3\".  If g:arc_always_atstrings is nonzero, then expressions after the @-symbol inside of strings will be highlighted like normal code, as though you had (declare 'atstrings t).  If this variable is 0, then atstrings will not highlight.\r\n\r\nIf you want more intelligent control over atstring highlighting, check out the accompanying ftplugin options below.\r\n\r\nEXAMPLE:\r\n\r\nYou could put\r\n\r\n  let g:arc_always_atstrings=1\r\n\r\nin your .vimrc, and whenever you were highlighting an Arc file, atstrings would highlight, but parentheses would be colored normally (non-rainbow), since you don't have to explicitly set either variable to 0.  If they don't exist, they'll do nothing anyways.\r\n\r\nFTPLUGIN:\r\n\r\nThe following options are available for customizing the Arc ftplugin.  They are meant to work in conjunction with the accompanying Arc syntax highlighter (see above).\r\n\r\n- g:arc_detect_atstrings\r\n\r\nIn Arc 3, there is an option to enable string interpolation of arbitrary expressions using at-signs by saying\r\n  \r\n  (declare 'atstrings t)\r\n\r\nThen, for instance, \"1 + 2 = @(+ 1 2)\" is the same as \"1 + 2 = 3\".  If g:arc_detect_atstrings is nonzero, then expressions after the @-symbol inside of strings will be highlighted like normal code according to the following cases:\r\n\r\n  - if a form that will enable atstrings, like\r\n      (declare 'atstrings t)\r\n    is in the source code, highlight expressions after @-symbols\r\n\r\n  - if a form that will disable atstrings, like\r\n      (declare 'atstrings nil)\r\n    is in the source code, do not highlight expressions after @-symbols\r\n\r\n  - if there are multiple forms that contradict each other (enabling\r\n    atstrings in one place while disabling them in another), then be safe and\r\n    do not highlight expressions after @-symbols.\r\n\r\nThis option can be used as an alternative to g:arc_always_atstrings, which is found in the Arc syntax highlighter (see above).  If, however, g:arc_always_atstrings is nonzero, it will take precedence over g:arc_detect_atstrings and always highlight atstrings.  When g:arc_always_atstrings is 0, behavior is dictated by g:arc_detect_atstrings.\r\n\r\nChanges in highlighting are triggered whenever you write to the file.  If you change, say\r\n\r\n  (declare 'atstrings t)\r\n\r\nto\r\n\r\n  (declare 'atstrings nil)\r\n\r\nthen :w, the atstring highlighting will be turned off.\r\n\r\n- g:arc_bodops\r\n\r\nIMPORTANT: This feature is currently available only if your Vim installation has +python support.  See :h python\r\n\r\nIf this variable is nonzero, then on every file write your source code is inspected in an attempt to find top-level macro definitions that have body parameters.  That is, \r\n\r\n  (mac foo (vars vals . body)\r\n    something)\r\n\r\nwill be detected, because it is a macro that takes a rest parameter named \"body\".  Whereas\r\n\r\n  (def foo (a b . body)\r\n    something)\r\n\r\nwill not, because it's not a macro definition, and\r\n\r\n  (def make-macro (name)\r\n    `(mac ,name body (pr \"stuff\")))\r\n\r\nwill not recognize the quasiquoted macro definition, even though it takes a body parameter.\r\n\r\nThe name of each macro found in this way will be added to the &lispwords variable.  Then, with auto-indentation, the macro\r\n\r\n  (mac foo body\r\n    bar)\r\n\r\nwill indent like\r\n\r\n  (foo a\r\n    b\r\n    c)\r\n\r\ninstead of\r\n\r\n  (foo a\r\n       b\r\n       c)\r\n\r\n(Sorry; that probably doesn't look right in a non-fixed-width font.)  This can be useful for macros that you define to be syntactic forms, much like how, say, looping constructs are defined in Arc itself.\r\n\r\n- g:arc_highlight_lispwords\r\n\r\nIf nonzero, every word in the &lispwords variable will highlight as though it were syntax.  The highlighting is updated every time you write to the file.  This can be useful in conjunction with g:arc_bodops, so that after you write the macro\r\n\r\n  (mac my-each (x xs . body)\r\n    ...do stuff...)\r\n\r\neach occurrence of \"my-each\" will be highlighted & indented just like the \"each\" macro.  You can even add words you want to be highlighted & indented by going\r\n\r\n  :setl lispwords+=foo\r\n\r\nThis lispword will then persist across file-writes, even if you've not defined a \"foo\" macro.\r\n\r\nMost of these extra features are useless without the accompanying Arc syntax highlighter, so you probably want to use it if you use these features.\r\n\r\nEXAMPLE:\r\n\r\nYou could put\r\n\r\n  let g:arc_detect_atstrings=1\r\n  let g:arc_bodops=1\r\n  let g:arc_highlight_lispwords=1\r\n\r\nin your .vimrc, and when using the Arc syntax highlighter you can test, say, news.arc and see that:\r\n\r\n  - atstrings are highlighted, as there is a positive declaration at the top of the source\r\n  \r\n  - macros like \"adop\" and \"edop\" are highlighted & auto-indented as lispwords\r\n\r\n  - but the macro \"newsop\" isn't highlighted or auto-indented, because its rest parameter is named \"args\".  So, you can :setl lw+=newsop and :w to see \"newsop\" become highlighted.","install_details":"1.  If you haven't already, create your user runtime directory.  You typically use the first item of the runtimepath option (see :h runtimepath).  For example, using Vim's default runtimepath option on Unix:\r\n\r\n  mkdir ~\/.vim\r\n\r\n2.  If you haven't already, create directories inside of this called \"syntax\" and \"ftplugin\".  Continuing the last example:\r\n\r\n  mkdir ~\/.vim\/syntax\r\n  mkdir ~\/.vim\/ftplugin\r\n\r\n3.  Download and extract the contents of this package (arc-vim.tar.gz).  Inside, there will be two directories: \"syntax\" and \"ftplugin\".  Inside each of these are their own respective \"arc.vim\" files.  Place each in their respective directories that you have from step 2 (i.e., place the package's \"syntax\/arc.vim\" into \"~\/.vim\/syntax\/arc.vim\" and \"ftplugin\/arc.vim\" into \"~\/.vim\/ftplugin\/arc.vim\").\r\n\r\n4.  Now you can start Vim and enable the syntax highlighter.  Make sure to first do\r\n  \r\n  :syntax enable\r\n\r\nor\r\n  \r\n  :syntax on\r\n\r\nif you don't already have this in your .vimrc or such.  Then, you can do things like\r\n\r\n  :setf arc\r\n\r\nto start highlighting the current buffer.\r\n\r\n5.  You can also start Vim and enable the filetype-plugin.  Make sure to first do\r\n  \r\n  :filetype plugin on\r\n\r\nif you don't already have this in your .vimrc or such.  Then you can use commands like\r\n\r\n  :setf arc\r\n\r\nto start using the Arc filetype-plugin.  For more info, see :h ftplugins\r\n\r\n6.  If you want Vim to automatically turn on Arc syntax highlighting \/ use the Arc ftplugin, you can add\r\n\r\n  au BufRead,BufNewFile *.arc setf arc\r\n\r\nto your .vimrc (or ftdetect\/arc.vim or what-have-you; see :h new-filetype).\r\n\r\nNote that if, like me, you have any existing sessions\/views for a particular Arc file, Vim might be setting the filetype to whatever it was in the view (see :h views-sessions), which means that the above won't seem to have an effect!  You can delete the view or manually :setf arc on such files, then all should be fine.","5":"1.  If you haven't already, create your user runtime directory.  You typically use the first item of the runtimepath option (see :h runtimepath).  For example, using Vim's default runtimepath option on Unix:\r\n\r\n  mkdir ~\/.vim\r\n\r\n2.  If you haven't already, create directories inside of this called \"syntax\" and \"ftplugin\".  Continuing the last example:\r\n\r\n  mkdir ~\/.vim\/syntax\r\n  mkdir ~\/.vim\/ftplugin\r\n\r\n3.  Download and extract the contents of this package (arc-vim.tar.gz).  Inside, there will be two directories: \"syntax\" and \"ftplugin\".  Inside each of these are their own respective \"arc.vim\" files.  Place each in their respective directories that you have from step 2 (i.e., place the package's \"syntax\/arc.vim\" into \"~\/.vim\/syntax\/arc.vim\" and \"ftplugin\/arc.vim\" into \"~\/.vim\/ftplugin\/arc.vim\").\r\n\r\n4.  Now you can start Vim and enable the syntax highlighter.  Make sure to first do\r\n  \r\n  :syntax enable\r\n\r\nor\r\n  \r\n  :syntax on\r\n\r\nif you don't already have this in your .vimrc or such.  Then, you can do things like\r\n\r\n  :setf arc\r\n\r\nto start highlighting the current buffer.\r\n\r\n5.  You can also start Vim and enable the filetype-plugin.  Make sure to first do\r\n  \r\n  :filetype plugin on\r\n\r\nif you don't already have this in your .vimrc or such.  Then you can use commands like\r\n\r\n  :setf arc\r\n\r\nto start using the Arc filetype-plugin.  For more info, see :h ftplugins\r\n\r\n6.  If you want Vim to automatically turn on Arc syntax highlighting \/ use the Arc ftplugin, you can add\r\n\r\n  au BufRead,BufNewFile *.arc setf arc\r\n\r\nto your .vimrc (or ftdetect\/arc.vim or what-have-you; see :h new-filetype).\r\n\r\nNote that if, like me, you have any existing sessions\/views for a particular Arc file, Vim might be setting the filetype to whatever it was in the view (see :h views-sessions), which means that the above won't seem to have an effect!  You can delete the view or manually :setf arc on such files, then all should be fine.","first_name":"AJ","6":"AJ","last_name":"V","7":"V","releases":[{"0":"2720","vim_version":"7.0","1":"7.0","script_version":"1.1","2":"1.1","version_comment":"Changes for the Arc 3.1 release ( see http:\/\/arclanguage.org\/item?id=10254 ):\r\n  - Use & as ssyntax instead of +\r\n  - Updated the changed\/new Arc identifiers\r\n  - Removed the o from formatoptions (I found it annoying; if you set it in\r\n    your .vimrc or such, you can still use it)\r\n  - Updated the regexp for g:arc_bodops; now it will only match definitions\r\n    found at the beginning of a line, to avoid macro-defining-macro mismatches\r\n    (not a perfect solution, but catches the common cases)","3":"Changes for the Arc 3.1 release ( see http:\/\/arclanguage.org\/item?id=10254 ):\r\n  - Use & as ssyntax instead of +\r\n  - Updated the changed\/new Arc identifiers\r\n  - Removed the o from formatoptions (I found it annoying; if you set it in\r\n    your .vimrc or such, you can still use it)\r\n  - Updated the regexp for g:arc_bodops; now it will only match definitions\r\n    found at the beginning of a line, to avoid macro-defining-macro mismatches\r\n    (not a perfect solution, but catches the common cases)","package":"arc-vim.tar.gz","4":"arc-vim.tar.gz","src_id":"11135","5":"11135","creation_date":"1249567025","6":"1249567025"},{"0":"2720","vim_version":"7.2","1":"7.2","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"arc-vim.tar.gz","4":"arc-vim.tar.gz","src_id":"11060","5":"11060","creation_date":"1248447938","6":"1248447938"}]},"2719":{"script_id":"2719","0":"2719","script_name":"Proj","1":"Proj","script_type":"utility","2":"utility","summary":"Simple project tool","3":"Simple project tool","description":"Proj lets you save settings for your project in a simple file.\r\n\r\nCommands:\r\n    Note that the easiest way to use Proj is with the key mappings bound \r\n    to the commands below. <Leader>pt is the default mapping to open a \r\n    tab-specific project, for instance.\r\n\r\n    :ProjAdd\r\n     Prompts to add a new project in the current directory.\r\n\r\n    :ProjFile\r\n     Open the project file in a split.\r\n\r\n    :ProjInfo\r\n     Show all of the current project's settings in the status line.\r\n\r\n    :ProjMenu\r\n     Open a menu with all of these commands.\r\n\r\n    :ProjNotes\r\n     Open the project notes file in a split.\r\n\r\n    :ProjOpen\r\n     Prompt to open a project.\r\n\r\n    :ProjOpenTab\r\n     Prompt to open a project for the open tab. Projects opened this way will\r\n     only be active in the opened tab, so that each tab can contain a project.\r\n\r\n    :ProjRefresh\r\n     Reload the current project.\r\n\r\n    :ProjReload\r\n     Reload the project file.\r\n\r\n    :ProjVim\r\n     Open the project's vim settings file in a split.\r\n\r\nFile Syntax:\r\n    DOS .ini\r\n\r\nAvailable Settings:\r\n    browser - A custom command for the filebrowser\r\n    notes - Path to a text file with project notes\r\n    path - Path to the project root directory\r\n    vim - Path to a file with vim commands\r\n    docksend - Upload all files in the project on save if the TransmitFtp\r\n      plugin is available\r\n\r\nSample Project File:\r\n    ; This is a comment\r\n    [project]\r\n    path = \/path\/to\/project\r\n    vim = \/path\/to\/settings_file.vim\r\n    docksend ; boolean option\r\n\r\n    [path-with-spaces]\r\n    path = \/path\/to\/my\\ project ; Escape spaces with \\\r\n\r\nGlobal Options:\r\n    * g:ProjDisableMappings (default: 0) - Set to 1 to turn off all\r\n        mappings defined by this plugin\r\n    * g:ProjFile (default: '~\/.vimproj') - Path to the project file.\r\n    * g:ProjFileBrowser (default: 'NERDTree') - The filebrowser command.\r\n        Set to 'off' to not open a filebrowser.\r\n    * g:ProjMapLeader (default: '<Leader>p') - The prefix for default mappings\r\n    * g:ProjNoteFile (default: 'notes.txt') - Path to the project notes file\r\n    * g:ProjSplitMethod (default: 'vsp') - Command to use when opening a file\r\n        with a Proj command such as ProjFile.\r\n\r\n    Default maps: These are all prefixed with g:ProjMapLeader by default.\r\n        g:ProjAddMap (default: 'a') - Calls :ProjAdd\r\n        g:ProjFileMap (default: 'f') - Calls :ProjFile\r\n        g:ProjInfoMap (default: 'i') - Calls :ProjInfo\r\n        g:ProjMenuMap (default: 'm') - Calls :ProjMenu\r\n        g:ProjNotesMap (default: 'n') - Calls :ProjNotes\r\n        g:ProjOpenMap (default: 'o') - Calls :ProjOpen\r\n        g:ProjOpenTabMap (default: 't') - Calls :ProjOpenTab\r\n        g:ProjReloadMap (default: 'r') - Calls :ProjReload\r\n        g:ProjVim (default: 'v') - Calls :ProjVim","4":"Proj lets you save settings for your project in a simple file.\r\n\r\nCommands:\r\n    Note that the easiest way to use Proj is with the key mappings bound \r\n    to the commands below. <Leader>pt is the default mapping to open a \r\n    tab-specific project, for instance.\r\n\r\n    :ProjAdd\r\n     Prompts to add a new project in the current directory.\r\n\r\n    :ProjFile\r\n     Open the project file in a split.\r\n\r\n    :ProjInfo\r\n     Show all of the current project's settings in the status line.\r\n\r\n    :ProjMenu\r\n     Open a menu with all of these commands.\r\n\r\n    :ProjNotes\r\n     Open the project notes file in a split.\r\n\r\n    :ProjOpen\r\n     Prompt to open a project.\r\n\r\n    :ProjOpenTab\r\n     Prompt to open a project for the open tab. Projects opened this way will\r\n     only be active in the opened tab, so that each tab can contain a project.\r\n\r\n    :ProjRefresh\r\n     Reload the current project.\r\n\r\n    :ProjReload\r\n     Reload the project file.\r\n\r\n    :ProjVim\r\n     Open the project's vim settings file in a split.\r\n\r\nFile Syntax:\r\n    DOS .ini\r\n\r\nAvailable Settings:\r\n    browser - A custom command for the filebrowser\r\n    notes - Path to a text file with project notes\r\n    path - Path to the project root directory\r\n    vim - Path to a file with vim commands\r\n    docksend - Upload all files in the project on save if the TransmitFtp\r\n      plugin is available\r\n\r\nSample Project File:\r\n    ; This is a comment\r\n    [project]\r\n    path = \/path\/to\/project\r\n    vim = \/path\/to\/settings_file.vim\r\n    docksend ; boolean option\r\n\r\n    [path-with-spaces]\r\n    path = \/path\/to\/my\\ project ; Escape spaces with \\\r\n\r\nGlobal Options:\r\n    * g:ProjDisableMappings (default: 0) - Set to 1 to turn off all\r\n        mappings defined by this plugin\r\n    * g:ProjFile (default: '~\/.vimproj') - Path to the project file.\r\n    * g:ProjFileBrowser (default: 'NERDTree') - The filebrowser command.\r\n        Set to 'off' to not open a filebrowser.\r\n    * g:ProjMapLeader (default: '<Leader>p') - The prefix for default mappings\r\n    * g:ProjNoteFile (default: 'notes.txt') - Path to the project notes file\r\n    * g:ProjSplitMethod (default: 'vsp') - Command to use when opening a file\r\n        with a Proj command such as ProjFile.\r\n\r\n    Default maps: These are all prefixed with g:ProjMapLeader by default.\r\n        g:ProjAddMap (default: 'a') - Calls :ProjAdd\r\n        g:ProjFileMap (default: 'f') - Calls :ProjFile\r\n        g:ProjInfoMap (default: 'i') - Calls :ProjInfo\r\n        g:ProjMenuMap (default: 'm') - Calls :ProjMenu\r\n        g:ProjNotesMap (default: 'n') - Calls :ProjNotes\r\n        g:ProjOpenMap (default: 'o') - Calls :ProjOpen\r\n        g:ProjOpenTabMap (default: 't') - Calls :ProjOpenTab\r\n        g:ProjReloadMap (default: 'r') - Calls :ProjReload\r\n        g:ProjVim (default: 'v') - Calls :ProjVim","install_details":"1. Extract the downloaded proj.tgz file\r\n2. Copy proj\/doc\/proj.txt to .vim\/doc\/proj.txt\r\n3. Copy proj\/plugin\/proj.vim to .vim\/plugin\/proj.vim\r\n4. Run :helptags ~\/.vim\/doc to load the documentation\r\n5. Create a file at ~\/.vimproj or your custom g:ProjFile location with your projects","5":"1. Extract the downloaded proj.tgz file\r\n2. Copy proj\/doc\/proj.txt to .vim\/doc\/proj.txt\r\n3. Copy proj\/plugin\/proj.vim to .vim\/plugin\/proj.vim\r\n4. Run :helptags ~\/.vim\/doc to load the documentation\r\n5. Create a file at ~\/.vimproj or your custom g:ProjFile location with your projects","first_name":"Thomas","6":"Thomas","last_name":"Allen","7":"Allen","releases":[{"0":"2719","vim_version":"7.0","1":"7.0","script_version":"1.5.2","2":"1.5.2","version_comment":"Fix bad global function definition.","3":"Fix bad global function definition.","package":"proj.vim.zip","4":"proj.vim.zip","src_id":"23396","5":"23396","creation_date":"1434472442","6":"1434472442"},{"0":"2719","vim_version":"7.0","1":"7.0","script_version":"1.5.1","2":"1.5.1","version_comment":"Fixed incorrect ProjOpenTab menu action.","3":"Fixed incorrect ProjOpenTab menu action.","package":"proj.tgz","4":"proj.tgz","src_id":"14001","5":"14001","creation_date":"1286328740","6":"1286328740"},{"0":"2719","vim_version":"7.0","1":"7.0","script_version":"1.5","2":"1.5","version_comment":"Tab-specific projects.","3":"Tab-specific projects.","package":"proj.tgz","4":"proj.tgz","src_id":"14000","5":"14000","creation_date":"1286328367","6":"1286328367"},{"0":"2719","vim_version":"7.0","1":"7.0","script_version":"1.4","2":"1.4","version_comment":"Cleanup, more mappings, menu, basic prompts.","3":"Cleanup, more mappings, menu, basic prompts.","package":"proj.tgz","4":"proj.tgz","src_id":"13903","5":"13903","creation_date":"1285297745","6":"1285297745"},{"0":"2719","vim_version":"7.0","1":"7.0","script_version":"1.3.1","2":"1.3.1","version_comment":"Bugfixes for ProjNotes toggle, project entry with no docksend key.","3":"Bugfixes for ProjNotes toggle, project entry with no docksend key.","package":"proj.tgz","4":"proj.tgz","src_id":"13379","5":"13379","creation_date":"1279747080","6":"1279747080"},{"0":"2719","vim_version":"7.0","1":"7.0","script_version":"1.3","2":"1.3","version_comment":"TransmitFTP docksend integration. ProjAdd mapping.","3":"TransmitFTP docksend integration. ProjAdd mapping.","package":"proj.tgz","4":"proj.tgz","src_id":"13375","5":"13375","creation_date":"1279724945","6":"1279724945"},{"0":"2719","vim_version":"7.0","1":"7.0","script_version":"1.2","2":"1.2","version_comment":"ProjAdd command. Windows pathname bugfix (thanks Mikhail Stepura)","3":"ProjAdd command. Windows pathname bugfix (thanks Mikhail Stepura)","package":"proj.tbz","4":"proj.tbz","src_id":"12122","5":"12122","creation_date":"1263833872","6":"1263833872"}]},"2718":{"script_id":"2718","0":"2718","script_name":"mutt-canned","1":"mutt-canned","script_type":"utility","2":"utility","summary":"a utility to build and use canned responses in mutt (and indirectly in vim)","3":"a utility to build and use canned responses in mutt (and indirectly in vim)","description":"I needed a utility to deal with canned responses.  I got really addicted to the canned response stuff in gmail and my mutt had gmail envy.\r\n\r\nThis is my first attempt to remedy that, but I suspect it will evolve over time.  Feedback welcome.","4":"I needed a utility to deal with canned responses.  I got really addicted to the canned response stuff in gmail and my mutt had gmail envy.\r\n\r\nThis is my first attempt to remedy that, but I suspect it will evolve over time.  Feedback welcome.","install_details":"\r\nTo install this, add it to ~\/.vim\/scripts\/ or somewhere\r\nand add something like the following:\r\n\r\n  au BufRead \/tmp\/mutt-* source ~\/.vim\/scripts\/mutt-canned.vim\r\n  au BufRead .\/example.file source .\/mutt-canned.vim\r\n\r\n0) echo lol, canned response > ~\/.canned\/lol\r\n\r\n1.a) insert canned response at current position:\r\n     hammer CTRL-X (twice or more) to hop through them\r\n\r\n1.b) insert canned response, replacing selected text:\r\n     highlight something with V and then hammer CTRL-X to replace it\r\n\r\n1.c) build new canned response:\r\n     highlight something with V and hammer CTRL-V (twice) to build a new canned response\r\n\r\n","5":"\r\nTo install this, add it to ~\/.vim\/scripts\/ or somewhere\r\nand add something like the following:\r\n\r\n  au BufRead \/tmp\/mutt-* source ~\/.vim\/scripts\/mutt-canned.vim\r\n  au BufRead .\/example.file source .\/mutt-canned.vim\r\n\r\n0) echo lol, canned response > ~\/.canned\/lol\r\n\r\n1.a) insert canned response at current position:\r\n     hammer CTRL-X (twice or more) to hop through them\r\n\r\n1.b) insert canned response, replacing selected text:\r\n     highlight something with V and then hammer CTRL-X to replace it\r\n\r\n1.c) build new canned response:\r\n     highlight something with V and hammer CTRL-V (twice) to build a new canned response\r\n\r\n","first_name":"Paul","6":"Paul","last_name":"Miller","7":"Miller","releases":[{"0":"2718","vim_version":"6.0","1":"6.0","script_version":"0.9","2":"0.9","version_comment":"Initial upload","3":"Initial upload","package":"mutt-canned.vim","4":"mutt-canned.vim","src_id":"11042","5":"11042","creation_date":"1248093883","6":"1248093883"}]},"2717":{"script_id":"2717","0":"2717","script_name":"mutt-aliases","1":"mutt-aliases","script_type":"utility","2":"utility","summary":"another script to read your mutt aliases file","3":"another script to read your mutt aliases file","description":"I either wasn't happy with or unable to operate the mutt aliases scripts I found on this site, so I wrote my own.  It reads your aliases from g:mutt_aliases_file (global var), or from the file indicated in ~\/.muttrc, or from ~\/.aliases.\r\n\r\nIt stores them in a complete function, which can be activated with either\r\n\r\n    i_CTRL-X-CTRL-U  (see :help i_CTRL-X-CTRL-U)\r\n\r\nor via an insert mode macro \"@@\".","4":"I either wasn't happy with or unable to operate the mutt aliases scripts I found on this site, so I wrote my own.  It reads your aliases from g:mutt_aliases_file (global var), or from the file indicated in ~\/.muttrc, or from ~\/.aliases.\r\n\r\nIt stores them in a complete function, which can be activated with either\r\n\r\n    i_CTRL-X-CTRL-U  (see :help i_CTRL-X-CTRL-U)\r\n\r\nor via an insert mode macro \"@@\".","install_details":"To install this script, put it somewhere in your ~.vim\/ directory, or heck, any other place you'd like.  Then add lines to source the script at appropriate times, e.g:\r\n\r\n    au BufRead \/tmp\/mutt-* source ~\/.vim\/scripts\/mutt-aliases.vim\r\n    au BufRead .\/example.file source .\/mutt-aliases.vim\r\n","5":"To install this script, put it somewhere in your ~.vim\/ directory, or heck, any other place you'd like.  Then add lines to source the script at appropriate times, e.g:\r\n\r\n    au BufRead \/tmp\/mutt-* source ~\/.vim\/scripts\/mutt-aliases.vim\r\n    au BufRead .\/example.file source .\/mutt-aliases.vim\r\n","first_name":"Paul","6":"Paul","last_name":"Miller","7":"Miller","releases":[{"0":"2717","vim_version":"6.0","1":"6.0","script_version":"0.93","2":"0.93","version_comment":"I had a couple bugs and some leftover code that wasn't necessary.\r\n\r\nI also made the [aliasname] show in the list of choices.","3":"I had a couple bugs and some leftover code that wasn't necessary.\r\n\r\nI also made the [aliasname] show in the list of choices.","package":"mutt-aliases.vim","4":"mutt-aliases.vim","src_id":"11048","5":"11048","creation_date":"1248200188","6":"1248200188"},{"0":"2717","vim_version":"6.0","1":"6.0","script_version":"0.92","2":"0.92","version_comment":"I made a couple little tweaks to this.  Nothing particularly special.","3":"I made a couple little tweaks to this.  Nothing particularly special.","package":"mutt-aliases.vim","4":"mutt-aliases.vim","src_id":"11041","5":"11041","creation_date":"1248093486","6":"1248093486"},{"0":"2717","vim_version":"6.0","1":"6.0","script_version":"0.91","2":"0.91","version_comment":"made the address matching case insensitive","3":"made the address matching case insensitive","package":"mutt-aliases.vim","4":"mutt-aliases.vim","src_id":"11038","5":"11038","creation_date":"1248002466","6":"1248002466"},{"0":"2717","vim_version":"6.0","1":"6.0","script_version":"0.9","2":"0.9","version_comment":"Initial upload","3":"Initial upload","package":"mutt-aliases.vim","4":"mutt-aliases.vim","src_id":"11037","5":"11037","creation_date":"1248001976","6":"1248001976"}]},"2716":{"script_id":"2716","0":"2716","script_name":"textobj-syntax","1":"textobj-syntax","script_type":"utility","2":"utility","summary":"Text objects for syntax highlighted items","3":"Text objects for syntax highlighted items","description":"*textobj-syntax* is a Vim plugin to provide |text-objects| to select one or\r\nmore items which are syntax highlighted.\r\n\r\nFor example, if you edit the following line in your vimrc, characters which\r\nare underlined with \"~\" are syntax highlighted.\r\n\r\n\tnnoremap <silent> ql  :<C-u>clist<Return>\r\n\t~~~~~~~~ ~~~~~~~~      ~~~~~     ~~~~~~~~\r\n\r\nSo |<Plug>(textobj-syntax-a)| and |<Plug>(textobj-syntax-i)| (which are mapped\r\nfrom  |ay| and |iy| by default) select one of the underlined items if the\r\ncursor is located at the one of them.\r\n\r\n\r\nRequirements:\r\n- Vim 7.2 or later\r\n- |textobj-user| 0.3.8 or later (vimscript#2100)\r\n\r\nLatest version:\r\nhttp:\/\/github.com\/kana\/vim-textobj-syntax\r\n\r\nDocument in HTML format:\r\nhttp:\/\/kana.github.com\/config\/vim\/textobj-syntax.html","4":"*textobj-syntax* is a Vim plugin to provide |text-objects| to select one or\r\nmore items which are syntax highlighted.\r\n\r\nFor example, if you edit the following line in your vimrc, characters which\r\nare underlined with \"~\" are syntax highlighted.\r\n\r\n\tnnoremap <silent> ql  :<C-u>clist<Return>\r\n\t~~~~~~~~ ~~~~~~~~      ~~~~~     ~~~~~~~~\r\n\r\nSo |<Plug>(textobj-syntax-a)| and |<Plug>(textobj-syntax-i)| (which are mapped\r\nfrom  |ay| and |iy| by default) select one of the underlined items if the\r\ncursor is located at the one of them.\r\n\r\n\r\nRequirements:\r\n- Vim 7.2 or later\r\n- |textobj-user| 0.3.8 or later (vimscript#2100)\r\n\r\nLatest version:\r\nhttp:\/\/github.com\/kana\/vim-textobj-syntax\r\n\r\nDocument in HTML format:\r\nhttp:\/\/kana.github.com\/config\/vim\/textobj-syntax.html","install_details":"...","5":"...","first_name":"Kana","6":"Kana","last_name":"Natsuno","7":"Natsuno","releases":[{"0":"2716","vim_version":"7.0","1":"7.0","script_version":"0.0.0","2":"0.0.0","version_comment":"Initial upload","3":"Initial upload","package":"vim-textobj-syntax-0.0.0.zip","4":"vim-textobj-syntax-0.0.0.zip","src_id":"11035","5":"11035","creation_date":"1247957947","6":"1247957947"}]},"2715":{"script_id":"2715","0":"2715","script_name":"UltiSnips","1":"UltiSnips","script_type":"utility","2":"utility","summary":"The ultimate snippet solution for python enabled Vim.","3":"The ultimate snippet solution for python enabled Vim.","description":"UltiSnips is the Ultimate solution for snippets under Vim.\r\n\r\nhttps:\/\/github.com\/sirver\/ultisnips\r\n\r\nNote: Since 2016, the vim.org site for this plugin is not updated any more. The plugin is still actively developed and maintained. Please follow our repository for future releases and bug fixes: https:\/\/github.com\/SirVer\/ultisnips. The master branch is always stable.","4":"UltiSnips is the Ultimate solution for snippets under Vim.\r\n\r\nhttps:\/\/github.com\/sirver\/ultisnips\r\n\r\nNote: Since 2016, the vim.org site for this plugin is not updated any more. The plugin is still actively developed and maintained. Please follow our repository for future releases and bug fixes: https:\/\/github.com\/SirVer\/ultisnips. The master branch is always stable.","install_details":"See https:\/\/github.com\/SirVer\/ultisnips\/blob\/master\/doc\/UltiSnips.txt.","5":"See https:\/\/github.com\/SirVer\/ultisnips\/blob\/master\/doc\/UltiSnips.txt.","first_name":"Holger","6":"Holger","last_name":"Rapp","7":"Rapp","releases":[{"0":"2715","vim_version":"7.4","1":"7.4","script_version":"3.2","2":"3.2","version_comment":"Note: Please prefer following https:\/\/github.com\/SirVer\/ultisnips for future releases. Master is always stable.\r\n\r\n- This is the first release done again by @SirVer. And this is also posted on vim.org again. `\u00c2\u00af\\_(ツ)_\/\u00c2\u00af`\r\n- This is the last version to support Python 2.\r\n- Syntax highlighting improvements: a new one for unite & tweaks to others.\r\n- Support for transformations on multiple lines.\r\n- Python interpolation got more powerful, for example tabstops can now be modified in python interpolation, you can access the last changed placeholder text and more.\r\n- Support for deoplete.\r\n- Snippet files are no longer watched for changes. This increases performance, but also means that if you change your snippet files outside of Vim, UltiSnips will not know about it. You need to run `:call UltiSnips#RefreshSnippets()` or restart Vim.\r\n- Text objects for selecting snippets in visual mode: iS, aS","3":"Note: Please prefer following https:\/\/github.com\/SirVer\/ultisnips for future releases. Master is always stable.\r\n\r\n- This is the first release done again by @SirVer. And this is also posted on vim.org again. `\u00c2\u00af\\_(ツ)_\/\u00c2\u00af`\r\n- This is the last version to support Python 2.\r\n- Syntax highlighting improvements: a new one for unite & tweaks to others.\r\n- Support for transformations on multiple lines.\r\n- Python interpolation got more powerful, for example tabstops can now be modified in python interpolation, you can access the last changed placeholder text and more.\r\n- Support for deoplete.\r\n- Snippet files are no longer watched for changes. This increases performance, but also means that if you change your snippet files outside of Vim, UltiSnips will not know about it. You need to run `:call UltiSnips#RefreshSnippets()` or restart Vim.\r\n- Text objects for selecting snippets in visual mode: iS, aS","package":"ultisnips-3.2.tar.gz","4":"ultisnips-3.2.tar.gz","src_id":"26811","5":"26811","creation_date":"1572976738","6":"1572976738"},{"0":"2715","vim_version":"7.4","1":"7.4","script_version":"3.1","2":"3.1","version_comment":"Note: Last release for vim.org. Please follow the https:\/\/github.com\/SirVer\/ultisnips for future releases. Master is also always stable and a good choice. \r\n\r\n- This is the last release done by @SirVer. The new maintainer of UltiSnips\r\n  is @seletskiy. The repository remains https:\/\/github.com\/SirVer\/ultisnips,\r\n  so this should not affect any users. This is also the last release to be\r\n  published on vim.org. Please follow the master branch on GitHub for the\r\n  latest stable version.\r\n- New option `e`: Context aware snippets. This gives very precise and\r\n  powerful control over which snippet should be expanded depending on\r\n  surrounding code. *UltiSnips-context-snippets*\r\n- New option `m`: Trim whitespace in all snippet lines.\r\n- Very powerful, freely configurable pre\/post-expand and post-jump actions\r\n  allow for transforming the buffer outside the snippet. *UltiSnips-snippet-actions*\r\n- Automatic triggering of snippets without the need to press the expand\r\n  trigger. *UltiSnips-autotrigger*\r\n- Better error reporting for snippet errors including python stacktraces\r\n  and listing of executed code.\r\n- Undo is more granular. Each jump and expand is now a separate undo step.\r\n- UltiSnips now emits autocommands on certain events. *UltiSnips-custom-autocommands*\r\n- clearsnippets now clears all snippets below the current priority. This\r\n  fits better with the priority system introduced in 3.0.\r\n- snipMate snippets support can be disabled. *UltiSnipsEnableSnipMate*\r\n- UltiSnipsEditSplit got a new value 'context'. *UltiSnipsEditSplit*\r\n- Improved syntax highlighting for snippets filetype.\r\n- Mappings and autocommands are now only established when needed, i.e. when\r\n  a snippet is active. This boosts performance outside of snippets.\r\n- New integration with Unite, TagBar, and deoplete.\r\n- New Ctags configuration file for snippet definitions.\r\n- Bug fixes, performance improvements, code cleanups and refactorings.\r\n- No longer supports Vim < 7.4.\r\n","3":"Note: Last release for vim.org. Please follow the https:\/\/github.com\/SirVer\/ultisnips for future releases. Master is also always stable and a good choice. \r\n\r\n- This is the last release done by @SirVer. The new maintainer of UltiSnips\r\n  is @seletskiy. The repository remains https:\/\/github.com\/SirVer\/ultisnips,\r\n  so this should not affect any users. This is also the last release to be\r\n  published on vim.org. Please follow the master branch on GitHub for the\r\n  latest stable version.\r\n- New option `e`: Context aware snippets. This gives very precise and\r\n  powerful control over which snippet should be expanded depending on\r\n  surrounding code. *UltiSnips-context-snippets*\r\n- New option `m`: Trim whitespace in all snippet lines.\r\n- Very powerful, freely configurable pre\/post-expand and post-jump actions\r\n  allow for transforming the buffer outside the snippet. *UltiSnips-snippet-actions*\r\n- Automatic triggering of snippets without the need to press the expand\r\n  trigger. *UltiSnips-autotrigger*\r\n- Better error reporting for snippet errors including python stacktraces\r\n  and listing of executed code.\r\n- Undo is more granular. Each jump and expand is now a separate undo step.\r\n- UltiSnips now emits autocommands on certain events. *UltiSnips-custom-autocommands*\r\n- clearsnippets now clears all snippets below the current priority. This\r\n  fits better with the priority system introduced in 3.0.\r\n- snipMate snippets support can be disabled. *UltiSnipsEnableSnipMate*\r\n- UltiSnipsEditSplit got a new value 'context'. *UltiSnipsEditSplit*\r\n- Improved syntax highlighting for snippets filetype.\r\n- Mappings and autocommands are now only established when needed, i.e. when\r\n  a snippet is active. This boosts performance outside of snippets.\r\n- New integration with Unite, TagBar, and deoplete.\r\n- New Ctags configuration file for snippet definitions.\r\n- Bug fixes, performance improvements, code cleanups and refactorings.\r\n- No longer supports Vim < 7.4.\r\n","package":"UltiSnips-3.1.tar.gz","4":"UltiSnips-3.1.tar.gz","src_id":"23779","5":"23779","creation_date":"1449473047","6":"1449473047"},{"0":"2715","vim_version":"7.3","1":"7.3","script_version":"3.0","2":"3.0","version_comment":"- Organisational changes: The project is now hosted on github. Snippets are\r\n  now shipped separately - please track honza\/vim-snippets.\r\n- UltiSnips is now a drop in replacement for snipMate - it parses snipMate\r\n  snippets and expands them emulating snipMates smaller feature set.\r\n- Filetype tab completion for UltiSnipsEdit.\r\n- UltiSnipsEdit now only edits private snippet files. Use UltiSnipsEdit! if\r\n  you want to edit shipped files.\r\n- New option 's' which strips trailing whitespace before jumping to next\r\n  tabstop \r\n- New option 'a' which converts non-ascii characters into ascii characters\r\n  in transformations. \r\n- New keyword in snippet files: priority defines which snippets should\r\n  overwrite others. This deprecates the '!' option.\r\n  *UltiSnips-adding-snippets*\r\n- Remove common whitespace of visual line selections before inserting in an\r\n  indented tabstop.\r\n- Support for overwriting the snippet directory name on a per buffer basis\r\n  to support per project snippets. *UltiSnips-snippet-search-path* \r\n- The keymaps for jumping in snippets are now only mapped when a snippet is\r\n  active, allowing them to be used for something else otherwise.\r\n- Expanding and jumping no longer overwrites the unnamed register.\r\n- Integration with Valloric\/YouCompleteMe and Shougo\/neocomplete.vim.\r\n- Other plugins can add sources for snippets to create snippets on the fly.\r\n  *UltiSnips-extending*\r\n- Vim functions now indicates if it did any work.\r\n  *UltiSnips-trigger-functions*\r\n- For python extensions: UltiSnips adds itself to the sys.path and can be\r\n  easily imported if it is available. *UltiSnips-python-module-path*\r\n- A new function giving programmatic access to the snippets currently\r\n  available for expansion for other plugins integrating with UltiSnips.\r\n  *UltiSnips_SnippetsInCurrentScope*\r\n- New or improved snippets (now in a different repo): all, bib, c, cpp, cs,\r\n  d, django, eruby, go, haskell, html, html, htmljinja, java, javascript,\r\n  js, ledger, ocaml, perl, php, puppet, python, ruby, scss, sh, tex, vim,\r\n  xml, zsh.\r\n","3":"- Organisational changes: The project is now hosted on github. Snippets are\r\n  now shipped separately - please track honza\/vim-snippets.\r\n- UltiSnips is now a drop in replacement for snipMate - it parses snipMate\r\n  snippets and expands them emulating snipMates smaller feature set.\r\n- Filetype tab completion for UltiSnipsEdit.\r\n- UltiSnipsEdit now only edits private snippet files. Use UltiSnipsEdit! if\r\n  you want to edit shipped files.\r\n- New option 's' which strips trailing whitespace before jumping to next\r\n  tabstop \r\n- New option 'a' which converts non-ascii characters into ascii characters\r\n  in transformations. \r\n- New keyword in snippet files: priority defines which snippets should\r\n  overwrite others. This deprecates the '!' option.\r\n  *UltiSnips-adding-snippets*\r\n- Remove common whitespace of visual line selections before inserting in an\r\n  indented tabstop.\r\n- Support for overwriting the snippet directory name on a per buffer basis\r\n  to support per project snippets. *UltiSnips-snippet-search-path* \r\n- The keymaps for jumping in snippets are now only mapped when a snippet is\r\n  active, allowing them to be used for something else otherwise.\r\n- Expanding and jumping no longer overwrites the unnamed register.\r\n- Integration with Valloric\/YouCompleteMe and Shougo\/neocomplete.vim.\r\n- Other plugins can add sources for snippets to create snippets on the fly.\r\n  *UltiSnips-extending*\r\n- Vim functions now indicates if it did any work.\r\n  *UltiSnips-trigger-functions*\r\n- For python extensions: UltiSnips adds itself to the sys.path and can be\r\n  easily imported if it is available. *UltiSnips-python-module-path*\r\n- A new function giving programmatic access to the snippets currently\r\n  available for expansion for other plugins integrating with UltiSnips.\r\n  *UltiSnips_SnippetsInCurrentScope*\r\n- New or improved snippets (now in a different repo): all, bib, c, cpp, cs,\r\n  d, django, eruby, go, haskell, html, html, htmljinja, java, javascript,\r\n  js, ledger, ocaml, perl, php, puppet, python, ruby, scss, sh, tex, vim,\r\n  xml, zsh.\r\n","package":"UltiSnips-3.0.tar.gz","4":"UltiSnips-3.0.tar.gz","src_id":"21651","5":"21651","creation_date":"1395483255","6":"1395483255"},{"0":"2715","vim_version":"7.0","1":"7.0","script_version":"2.2","2":"2.2","version_comment":"Smaller Bug fixes and improvements to shipped snippets.\r\n\r\n- Support to silence Python-not-found warnings. *UltiSnips-python-warning*\r\n- Matchit support for snippet files.\r\n- Improvements to syntax file.\r\n- Various smaller bug fixes.\r\n- New command to manually add a filetype to the list for the current\r\n  buffer. *:UltiSnipsAddFiletypes*\r\n- New or improved snippets: all, snippets, haskell, bindzone, python, golang,\r\n  json, html, coffee, coffee_jasmine, javascript_jasmine, ruby, php,\r\n  markdown.\r\n","3":"Smaller Bug fixes and improvements to shipped snippets.\r\n\r\n- Support to silence Python-not-found warnings. *UltiSnips-python-warning*\r\n- Matchit support for snippet files.\r\n- Improvements to syntax file.\r\n- Various smaller bug fixes.\r\n- New command to manually add a filetype to the list for the current\r\n  buffer. *:UltiSnipsAddFiletypes*\r\n- New or improved snippets: all, snippets, haskell, bindzone, python, golang,\r\n  json, html, coffee, coffee_jasmine, javascript_jasmine, ruby, php,\r\n  markdown.\r\n","package":"UltiSnips-2.2.tar.gz","4":"UltiSnips-2.2.tar.gz","src_id":"18527","5":"18527","creation_date":"1346524116","6":"1346524116"},{"0":"2715","vim_version":"7.0","1":"7.0","script_version":"2.1","2":"2.1","version_comment":"This brings two small features related to ${VISUAL} which was introduce in 2.0: access to the content in python code via snip.v and transformations: ${VISUAL\/foo\/bar\/g}. As expected, 2.0\\'s new features introduced new bugs as, all known are fixed in 2.1.\r\n\r\n- Python interpolation access to text from visual selection via snip.v.\r\n- Support for transformations of ${VISUAL} texts.\r\n- New or improved snippets: python, tex, texmath, ruby, rails, html, django","3":"This brings two small features related to ${VISUAL} which was introduce in 2.0: access to the content in python code via snip.v and transformations: ${VISUAL\/foo\/bar\/g}. As expected, 2.0\\'s new features introduced new bugs as, all known are fixed in 2.1.\r\n\r\n- Python interpolation access to text from visual selection via snip.v.\r\n- Support for transformations of ${VISUAL} texts.\r\n- New or improved snippets: python, tex, texmath, ruby, rails, html, django","package":"UltiSnips-2.1.tar.gz","4":"UltiSnips-2.1.tar.gz","src_id":"17463","5":"17463","creation_date":"1329256599","6":"1329256599"},{"0":"2715","vim_version":"7.0","1":"7.0","script_version":"2.0","2":"2.0","version_comment":"Significant rewrite with new features and less bugs. It also has some minor backwards incompatible changes marked below.\r\n\r\n- Backwards incompatible change: Support for normal mode editing. Snippets\r\n  are no longer exited when leaving insert mode but only by leaving the\r\n  text span of the snippets. This allows usage of normal mode commands and\r\n  autoformatting. It also increases compatibility with other plugins.\r\n- Backwards incompatible change: Changed glob patterns for snippets to \r\n  behave more like Vim *UltiSnips-adding-snippets*\r\n- Backwards incompatible change: Zero Tabstop is no longer removed in\r\n  nested snippets\r\n- Support for ${VISUAL:default text} placeholder. *UltiSnips-visual-placeholder*\r\n- Improved handling of utf-8 characters in files and snippet definitions.\r\n- Full support for :py3. UltiSnips now works with python >= 2.6 or >= 3.2.\r\n- New or improved snippets: python, all\r\n","3":"Significant rewrite with new features and less bugs. It also has some minor backwards incompatible changes marked below.\r\n\r\n- Backwards incompatible change: Support for normal mode editing. Snippets\r\n  are no longer exited when leaving insert mode but only by leaving the\r\n  text span of the snippets. This allows usage of normal mode commands and\r\n  autoformatting. It also increases compatibility with other plugins.\r\n- Backwards incompatible change: Changed glob patterns for snippets to \r\n  behave more like Vim *UltiSnips-adding-snippets*\r\n- Backwards incompatible change: Zero Tabstop is no longer removed in\r\n  nested snippets\r\n- Support for ${VISUAL:default text} placeholder. *UltiSnips-visual-placeholder*\r\n- Improved handling of utf-8 characters in files and snippet definitions.\r\n- Full support for :py3. UltiSnips now works with python >= 2.6 or >= 3.2.\r\n- New or improved snippets: python, all\r\n","package":"UltiSnips-2.0.tar.gz","4":"UltiSnips-2.0.tar.gz","src_id":"17390","5":"17390","creation_date":"1328449222","6":"1328449222"},{"0":"2715","vim_version":"7.0","1":"7.0","script_version":"1.6","2":"1.6","version_comment":"Bug fix release. We also accept contributions on GitHub now (main development stays on launchpad though): https:\/\/github.com\/SirVer\/ultisnips\/\r\n\r\n- Significant speed improvements and a few bugs fixed.\r\n- Better handling of non ASCII chars in snippets by assuming UTF-8 encoding\r\n  when no other information is available.\r\n- Contributions for UltiSnips are now also accepted on GitHub: https:\/\/github.com\/SirVer\/ultisnips\/\r\n- New or improved snippets: ruby, rails, xhtml\r\n","3":"Bug fix release. We also accept contributions on GitHub now (main development stays on launchpad though): https:\/\/github.com\/SirVer\/ultisnips\/\r\n\r\n- Significant speed improvements and a few bugs fixed.\r\n- Better handling of non ASCII chars in snippets by assuming UTF-8 encoding\r\n  when no other information is available.\r\n- Contributions for UltiSnips are now also accepted on GitHub: https:\/\/github.com\/SirVer\/ultisnips\/\r\n- New or improved snippets: ruby, rails, xhtml\r\n","package":"UltiSnips-1.6.tar.gz","4":"UltiSnips-1.6.tar.gz","src_id":"17130","5":"17130","creation_date":"1325236834","6":"1325236834"},{"0":"2715","vim_version":"7.0","1":"7.0","script_version":"1.5","2":"1.5","version_comment":"This is mainly a bug-fix release. Very little user visible changes.\r\n\r\n- Some critical bug fixes for new vim versions.\r\n- New or improved snippets: tex, texmath, python, jinja2, go, puppet, xhtml\r\n- Configuration of search path for snippets *UltiSnips-snippet-search-path*\r\n- New parser implementation: A little faster, more flexible and less bugged.\r\n\r\n","3":"This is mainly a bug-fix release. Very little user visible changes.\r\n\r\n- Some critical bug fixes for new vim versions.\r\n- New or improved snippets: tex, texmath, python, jinja2, go, puppet, xhtml\r\n- Configuration of search path for snippets *UltiSnips-snippet-search-path*\r\n- New parser implementation: A little faster, more flexible and less bugged.\r\n\r\n","package":"UltiSnips-1.5.tar.gz","4":"UltiSnips-1.5.tar.gz","src_id":"16569","5":"16569","creation_date":"1316898143","6":"1316898143"},{"0":"2715","vim_version":"7.0","1":"7.0","script_version":"1.4","2":"1.4","version_comment":"This release packs a bunch of new features and a lot of bug fixes. It also comes with new snippets and for the first time ever: windows support.\r\n\r\n- New or improved snippets: php, html, djangohtml, mako, lua\r\n- Snippets are now listed alphabetically by their trigger, no longer in\r\n  order of appearance\r\n- Snippet files are now automatically reloaded when they change.\r\n- Support for other directory names for snippets beside\r\n  \"UltiSnips\" *UltiSnips-snippet-search-path*\r\n- Errors are now shown in a scratch window.\r\n- Now fully supports Windows with python >= 2.6. UltiSnips should now work\r\n  on all systems that Vim runs on.\r\n- a syntax file was added for snippets files with nice highlighting.\r\n- snippets definition files now have the filetype 'snippets'. It used to be\r\n  'snippet'.","3":"This release packs a bunch of new features and a lot of bug fixes. It also comes with new snippets and for the first time ever: windows support.\r\n\r\n- New or improved snippets: php, html, djangohtml, mako, lua\r\n- Snippets are now listed alphabetically by their trigger, no longer in\r\n  order of appearance\r\n- Snippet files are now automatically reloaded when they change.\r\n- Support for other directory names for snippets beside\r\n  \"UltiSnips\" *UltiSnips-snippet-search-path*\r\n- Errors are now shown in a scratch window.\r\n- Now fully supports Windows with python >= 2.6. UltiSnips should now work\r\n  on all systems that Vim runs on.\r\n- a syntax file was added for snippets files with nice highlighting.\r\n- snippets definition files now have the filetype 'snippets'. It used to be\r\n  'snippet'.","package":"UltiSnips-1.4.tar.gz","4":"UltiSnips-1.4.tar.gz","src_id":"16087","5":"16087","creation_date":"1310901776","6":"1310901776"},{"0":"2715","vim_version":"7.0","1":"7.0","script_version":"1.3","2":"1.3","version_comment":"UltiSnips is becoming a community project, the ChangeLog tells the story:\r\n\r\n- Erlang snippets (g0rdin)\r\n- Other VimScripts can now define and immediately expand anonymous snippets\r\n  ( *UltiSnips_Anon* ) (Ryan Wooden)\r\n- Other VimScripts can now define new snippets via a function\r\n  ( *UltiSnips_AddSnippet* ) (Ryan Wooden)\r\n- New Snippets for eruby and rails (Ches Martin).\r\n- A new Option 't' has been added to snippets that avoid expanding tabstops.\r\n  Be also more consistent with how indenting is handled. (Ryan Wooden)\r\n- Added a ftplugin script for .snippets files. Syntax highlighting still\r\n  missing. (Rupa Deadwyler)\r\n- Added UltiSnipsReset and UltiSnipsEdit (Idea by JCEB)","3":"UltiSnips is becoming a community project, the ChangeLog tells the story:\r\n\r\n- Erlang snippets (g0rdin)\r\n- Other VimScripts can now define and immediately expand anonymous snippets\r\n  ( *UltiSnips_Anon* ) (Ryan Wooden)\r\n- Other VimScripts can now define new snippets via a function\r\n  ( *UltiSnips_AddSnippet* ) (Ryan Wooden)\r\n- New Snippets for eruby and rails (Ches Martin).\r\n- A new Option 't' has been added to snippets that avoid expanding tabstops.\r\n  Be also more consistent with how indenting is handled. (Ryan Wooden)\r\n- Added a ftplugin script for .snippets files. Syntax highlighting still\r\n  missing. (Rupa Deadwyler)\r\n- Added UltiSnipsReset and UltiSnipsEdit (Idea by JCEB)","package":"UltiSnips-1.3.tar.gz","4":"UltiSnips-1.3.tar.gz","src_id":"15006","5":"15006","creation_date":"1297708068","6":"1297708068"},{"0":"2715","vim_version":"7.0","1":"7.0","script_version":"1.2","2":"1.2","version_comment":"- many bugs were fixed\r\n- smode mappings for printable characters are now removed before expanding a\r\n  snippet. This is configurable. *UltiSnips-warning-smappings*\r\n- all shipped snippets are now fully compatible with UltiSnips\r\n- added support for global snippets which enhance python interpolation even\r\n  more *UltiSnips-globals*\r\n- added support for multi word and regular expression triggers. Very\r\n  powerful in combination with python interpolation.\r\n- Python interpolation became much more powerful *UltiSnips-python* \r\n- added support for clearsnippets command *UltiSnips-clearing-snippets*\r\n- added support for option w which is a little more strict than i.\r\n- added support for listing of valid triggers. Defaults to <c-tab>.\r\n- added support for option i (inword expansion)\r\n- extends keyword is now supported on the first line of snippet files. This makes it easy to\r\n       define special cases, for example cpp extends c: a cpp trigger is useless\r\n       in c, but a c trigger is valuable for cpp. \r\n- UltiSnips now adheres to expandtab and tabstop options of vim","3":"- many bugs were fixed\r\n- smode mappings for printable characters are now removed before expanding a\r\n  snippet. This is configurable. *UltiSnips-warning-smappings*\r\n- all shipped snippets are now fully compatible with UltiSnips\r\n- added support for global snippets which enhance python interpolation even\r\n  more *UltiSnips-globals*\r\n- added support for multi word and regular expression triggers. Very\r\n  powerful in combination with python interpolation.\r\n- Python interpolation became much more powerful *UltiSnips-python* \r\n- added support for clearsnippets command *UltiSnips-clearing-snippets*\r\n- added support for option w which is a little more strict than i.\r\n- added support for listing of valid triggers. Defaults to <c-tab>.\r\n- added support for option i (inword expansion)\r\n- extends keyword is now supported on the first line of snippet files. This makes it easy to\r\n       define special cases, for example cpp extends c: a cpp trigger is useless\r\n       in c, but a c trigger is valuable for cpp. \r\n- UltiSnips now adheres to expandtab and tabstop options of vim","package":"UltiSnips-1.2.tar.gz","4":"UltiSnips-1.2.tar.gz","src_id":"13661","5":"13661","creation_date":"1282642928","6":"1282642928"},{"0":"2715","vim_version":"7.0","1":"7.0","script_version":"1.1","2":"1.1","version_comment":"Made triggers configurable. You can also use the same trigger for expanding and tabbing. The TextMate configuration <tab> and <s-tab> is now possible.\r\nConditional Inserts can now be nested\r\nAdded support for b option. This only considers a snippet at the beginning of a line ( *UltiSnips-adding-snippets* )\r\nAdded support for ! option. This overwrites previously defined snippets with the same tab trigger ( *UltiSnips-adding-snippets* )\r\nSupport for dotted filetype syntax. Now snippets for more than one filetype can be active ( *UltiSnips-adding-snippets* )\r\nMinor bug fixing.\r\n","3":"Made triggers configurable. You can also use the same trigger for expanding and tabbing. The TextMate configuration <tab> and <s-tab> is now possible.\r\nConditional Inserts can now be nested\r\nAdded support for b option. This only considers a snippet at the beginning of a line ( *UltiSnips-adding-snippets* )\r\nAdded support for ! option. This overwrites previously defined snippets with the same tab trigger ( *UltiSnips-adding-snippets* )\r\nSupport for dotted filetype syntax. Now snippets for more than one filetype can be active ( *UltiSnips-adding-snippets* )\r\nMinor bug fixing.\r\n","package":"UltiSnips-1.1.tar.gz","4":"UltiSnips-1.1.tar.gz","src_id":"11046","5":"11046","creation_date":"1248165429","6":"1248165429"},{"0":"2715","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"UltiSnips-1.0.tar.gz","4":"UltiSnips-1.0.tar.gz","src_id":"11021","5":"11021","creation_date":"1247778139","6":"1247778139"}]},"2714":{"script_id":"2714","0":"2714","script_name":"Tag Signature Balloons","1":"Tag Signature Balloons","script_type":"utility","2":"utility","summary":"Tag Signatures in Balloon Tooltips","3":"Tag Signatures in Balloon Tooltips","description":"This is a very simple script that displays the 'signature' of a tag when you hover the mouse over that tag.  Only works if Vim has('balloon_eval') and if there is an available tag file.\r\n\r\nScreenshots and the development repository are available on bitbucket: https:\/\/bitbucket.org\/abudden\/tagsignature","4":"This is a very simple script that displays the 'signature' of a tag when you hover the mouse over that tag.  Only works if Vim has('balloon_eval') and if there is an available tag file.\r\n\r\nScreenshots and the development repository are available on bitbucket: https:\/\/bitbucket.org\/abudden\/tagsignature","install_details":"Copy the file into your plugin directory.","5":"Copy the file into your plugin directory.","first_name":"Al","6":"Al","last_name":"Budden","7":"Budden","releases":[{"0":"2714","vim_version":"7.0","1":"7.0","script_version":"r736","2":"r736","version_comment":"Patch provided by Matthia Br\u00c3\u00a4ndli for tag signature balloon script - adds multi-line support.","3":"Patch provided by Matthia Br\u00c3\u00a4ndli for tag signature balloon script - adds multi-line support.","package":"tag_signature.vim","4":"tag_signature.vim","src_id":"19929","5":"19929","creation_date":"1366833879","6":"1366833879"},{"0":"2714","vim_version":"7.0","1":"7.0","script_version":"r714","2":"r714","version_comment":"Minor tweak to version check.","3":"Minor tweak to version check.","package":"tag_signature.vim","4":"tag_signature.vim","src_id":"18411","5":"18411","creation_date":"1345061037","6":"1345061037"},{"0":"2714","vim_version":"7.0","1":"7.0","script_version":"r645","2":"r645","version_comment":"Previous upload didn't work for some reason.  Re-uploading r645.","3":"Previous upload didn't work for some reason.  Re-uploading r645.","package":"tag_signature.vim","4":"tag_signature.vim","src_id":"17745","5":"17745","creation_date":"1334044759","6":"1334044759"},{"0":"2714","vim_version":"7.0","1":"7.0","script_version":"r645","2":"r645","version_comment":"Check Vim version is > 7 before loading.","3":"Check Vim version is > 7 before loading.","package":"tag_signature.vim","4":"tag_signature.vim","src_id":"17732","5":"17732","creation_date":"1333794841","6":"1333794841"},{"0":"2714","vim_version":"7.0","1":"7.0","script_version":"r319","2":"r319","version_comment":"Better handling of Java.","3":"Better handling of Java.","package":"tag_signature.vim","4":"tag_signature.vim","src_id":"11314","5":"11314","creation_date":"1252048243","6":"1252048243"},{"0":"2714","vim_version":"7.0","1":"7.0","script_version":"r314","2":"r314","version_comment":"Fixed bug: was searching for tags even when they weren't valid keywords.","3":"Fixed bug: was searching for tags even when they weren't valid keywords.","package":"tag_signature.vim","4":"tag_signature.vim","src_id":"11265","5":"11265","creation_date":"1251295515","6":"1251295515"},{"0":"2714","vim_version":"7.0","1":"7.0","script_version":"r293","2":"r293","version_comment":"Added support for multi-line balloons (where tag signature doesn't contain enough information).","3":"Added support for multi-line balloons (where tag signature doesn't contain enough information).","package":"tag_signature.vim","4":"tag_signature.vim","src_id":"11123","5":"11123","creation_date":"1249313025","6":"1249313025"},{"0":"2714","vim_version":"7.0","1":"7.0","script_version":"r284","2":"r284","version_comment":"Added support for numbered lines in tag file.","3":"Added support for numbered lines in tag file.","package":"tag_signature.vim","4":"tag_signature.vim","src_id":"11045","5":"11045","creation_date":"1248165326","6":"1248165326"},{"0":"2714","vim_version":"7.0","1":"7.0","script_version":"r283","2":"r283","version_comment":"Fixed search so that it doesn't find words including the tag.","3":"Fixed search so that it doesn't find words including the tag.","package":"tag_signature.vim","4":"tag_signature.vim","src_id":"11043","5":"11043","creation_date":"1248095945","6":"1248095945"},{"0":"2714","vim_version":"7.0","1":"7.0","script_version":"r277","2":"r277","version_comment":"Initial upload","3":"Initial upload","package":"tag_signature.vim","4":"tag_signature.vim","src_id":"11019","5":"11019","creation_date":"1247748651","6":"1247748651"}]},"2713":{"script_id":"2713","0":"2713","script_name":"nextCS.vim","1":"nextCS.vim","script_type":"utility","2":"utility","summary":"Change your color scheme easily","3":"Change your color scheme easily","description":"nextCS.vim (next Color Scheme) changes your theme in one shot.\r\n\r\n<F12> Next\r\n<F11> Previous\r\n\r\nSimple enough :)\r\n\r\nhttps:\/\/github.com\/chilicuil\/nextCS.vim","4":"nextCS.vim (next Color Scheme) changes your theme in one shot.\r\n\r\n<F12> Next\r\n<F11> Previous\r\n\r\nSimple enough :)\r\n\r\nhttps:\/\/github.com\/chilicuil\/nextCS.vim","install_details":"Download this file to ~\/.vim\/plugins\/  or to \/vimfiles\/plugins\/  (on Win32 platforms)","5":"Download this file to ~\/.vim\/plugins\/  or to \/vimfiles\/plugins\/  (on Win32 platforms)","first_name":"chili","6":"chili","last_name":"cuil","7":"cuil","releases":[{"0":"2713","vim_version":"7.0","1":"7.0","script_version":"0.0.4","2":"0.0.4","version_comment":"add <Plug>NextCS and <Plug>PreviousCS to allow extra mapping","3":"add <Plug>NextCS and <Plug>PreviousCS to allow extra mapping","package":"nextCS.vim.zip","4":"nextCS.vim.zip","src_id":"25102","5":"25102","creation_date":"1493527191","6":"1493527191"},{"0":"2713","vim_version":"7.0","1":"7.0","script_version":"0.0.3","2":"0.0.3","version_comment":"refactored, add documentation, add configuration options (mapping, theme dir)\r\n","3":"refactored, add documentation, add configuration options (mapping, theme dir)\r\n","package":"nextCS.zip","4":"nextCS.zip","src_id":"21588","5":"21588","creation_date":"1394448470","6":"1394448470"},{"0":"2713","vim_version":"7.0","1":"7.0","script_version":"0.0.2","2":"0.0.2","version_comment":"Reset SignColumn after every change, it'll fix a lot of broken themes when used with vim-gitgutter","3":"Reset SignColumn after every change, it'll fix a lot of broken themes when used with vim-gitgutter","package":"nextCS.vim","4":"nextCS.vim","src_id":"21139","5":"21139","creation_date":"1385953813","6":"1385953813"},{"0":"2713","vim_version":"7.0","1":"7.0","script_version":"0.0.1","2":"0.0.1","version_comment":"Initial upload","3":"Initial upload","package":"nextCS.vim","4":"nextCS.vim","src_id":"11018","5":"11018","creation_date":"1247712700","6":"1247712700"}]},"2712":{"script_id":"2712","0":"2712","script_name":"sign-diff","1":"sign-diff","script_type":"utility","2":"utility","summary":"show the diff status at left sidebar","3":"show the diff status at left sidebar","description":"now this plugin supports Windows though cmd.exe shows up at front most...\r\nhttp:\/\/tyru.yu-nagi.com\/stash\/screencast_vim_sign-diff.swf\r\n\r\ndiff program for windows here:\r\n  http:\/\/gnuwin32.sourceforge.net\/packages\/diffutils.htm\r\n  http:\/\/www.gfd-dennou.org\/library\/cc-env\/diff-win\/SIGEN.htm\r\nor see cygwin, mingw.\r\n\r\n\r\nUsage:\r\n  Commands:\r\n      SDAdd\r\n          add current file to diff list.\r\n          current buffer will be diffed with\r\n          the written file's buffer.\r\n          if you want to change that, see g:SD_comp_with.\r\n      SDUpdate\r\n          update signs.\r\n      SDEnable\r\n          start showing signs.\r\n      SDDisable\r\n          stop showing signs.\r\n      SDToggle\r\n          toggle showing signs.\r\n      SDList\r\n          list all signs in current file\r\n\r\n\r\n  Global Variables:\r\n      g:SD_backupdir (default:'~\/.vim-sign-diff')\r\n          backup directory to save some backup of current file.\r\n          this dir will be mkdir-ed if doesn't exist.\r\n\r\n      g:SD_diffopt (default:&diffopt)\r\n          script local value of &diffopt.\r\n\r\n      g:SD_diffexpr (default:&diffexpr)\r\n          script local value of &diffopt.\r\n\r\n      g:SD_hl_diffadd (default:'DiffAdd')\r\n          highlight group of the added line(s).\r\n\r\n      g:SD_hl_diffchange (default:'DiffChange')\r\n          highlight group of the changed line(s).\r\n\r\n      g:SD_hl_diffdelete (default:'DiffDelete')\r\n          highlight group of the deleted line(s).\r\n\r\n      g:SD_hl_difftext (default:'DiffText')\r\n          highlight group of the one changed line.\r\n\r\n      g:SD_sign_add (default:'+')\r\n          sign of the added line(s).\r\n\r\n      g:SD_sign_change (default:'*')\r\n          sign of the changed line(s).\r\n\r\n      g:SD_sign_delete (default:'-')\r\n          sign of the changed line(s).\r\n\r\n      g:SD_sign_text (default:'@')\r\n          sign of the one changed line.\r\n          see :help hl-DiffText\r\n\r\n      g:SD_comp_with (default:['written', 'buffer'])\r\n          g:SD_comp_with is List of two items.\r\n          valid items are 'buffer'(same as 1), 'written',\r\n          or number of revisions to revert.\r\n          get diff output like the following.\r\n          (if this value is default)\r\n          $ diff written buffer > output\r\n\r\n      g:SD_autocmd_add (default:['BufReadPost'])\r\n          do autocmd for adding signs with these group\r\n\r\n      g:SD_autocmd_update (default:['CursorHold', 'InsertLeave'])\r\n          do autocmd for updating signs with these group\r\n\r\n      g:SD_delete_files_vimleave (default:1)\r\n          when starting VimLeave event,\r\n          delete all files under g:SD_backupdir.\r\n\r\n      g:SD_no_update_within_seconds (default:3)\r\n          won't update within this seconds.\r\n          0 to update each autocmd.\r\n          see g:SD_autocmd_add and g:SD_autocmd_update\r\n          about timing to throw event.\r\n\r\n\r\n  Tips:\r\n      I suggest the following map.\r\n          nnoremap <C-l>  :SDUpdate<CR><C-l>\r\n","4":"now this plugin supports Windows though cmd.exe shows up at front most...\r\nhttp:\/\/tyru.yu-nagi.com\/stash\/screencast_vim_sign-diff.swf\r\n\r\ndiff program for windows here:\r\n  http:\/\/gnuwin32.sourceforge.net\/packages\/diffutils.htm\r\n  http:\/\/www.gfd-dennou.org\/library\/cc-env\/diff-win\/SIGEN.htm\r\nor see cygwin, mingw.\r\n\r\n\r\nUsage:\r\n  Commands:\r\n      SDAdd\r\n          add current file to diff list.\r\n          current buffer will be diffed with\r\n          the written file's buffer.\r\n          if you want to change that, see g:SD_comp_with.\r\n      SDUpdate\r\n          update signs.\r\n      SDEnable\r\n          start showing signs.\r\n      SDDisable\r\n          stop showing signs.\r\n      SDToggle\r\n          toggle showing signs.\r\n      SDList\r\n          list all signs in current file\r\n\r\n\r\n  Global Variables:\r\n      g:SD_backupdir (default:'~\/.vim-sign-diff')\r\n          backup directory to save some backup of current file.\r\n          this dir will be mkdir-ed if doesn't exist.\r\n\r\n      g:SD_diffopt (default:&diffopt)\r\n          script local value of &diffopt.\r\n\r\n      g:SD_diffexpr (default:&diffexpr)\r\n          script local value of &diffopt.\r\n\r\n      g:SD_hl_diffadd (default:'DiffAdd')\r\n          highlight group of the added line(s).\r\n\r\n      g:SD_hl_diffchange (default:'DiffChange')\r\n          highlight group of the changed line(s).\r\n\r\n      g:SD_hl_diffdelete (default:'DiffDelete')\r\n          highlight group of the deleted line(s).\r\n\r\n      g:SD_hl_difftext (default:'DiffText')\r\n          highlight group of the one changed line.\r\n\r\n      g:SD_sign_add (default:'+')\r\n          sign of the added line(s).\r\n\r\n      g:SD_sign_change (default:'*')\r\n          sign of the changed line(s).\r\n\r\n      g:SD_sign_delete (default:'-')\r\n          sign of the changed line(s).\r\n\r\n      g:SD_sign_text (default:'@')\r\n          sign of the one changed line.\r\n          see :help hl-DiffText\r\n\r\n      g:SD_comp_with (default:['written', 'buffer'])\r\n          g:SD_comp_with is List of two items.\r\n          valid items are 'buffer'(same as 1), 'written',\r\n          or number of revisions to revert.\r\n          get diff output like the following.\r\n          (if this value is default)\r\n          $ diff written buffer > output\r\n\r\n      g:SD_autocmd_add (default:['BufReadPost'])\r\n          do autocmd for adding signs with these group\r\n\r\n      g:SD_autocmd_update (default:['CursorHold', 'InsertLeave'])\r\n          do autocmd for updating signs with these group\r\n\r\n      g:SD_delete_files_vimleave (default:1)\r\n          when starting VimLeave event,\r\n          delete all files under g:SD_backupdir.\r\n\r\n      g:SD_no_update_within_seconds (default:3)\r\n          won't update within this seconds.\r\n          0 to update each autocmd.\r\n          see g:SD_autocmd_add and g:SD_autocmd_update\r\n          about timing to throw event.\r\n\r\n\r\n  Tips:\r\n      I suggest the following map.\r\n          nnoremap <C-l>  :SDUpdate<CR><C-l>\r\n","install_details":"just place this into ~\/.vim\/plugin\/ or other runtimepaths","5":"just place this into ~\/.vim\/plugin\/ or other runtimepaths","first_name":"tyru","6":"tyru","last_name":" ","7":" ","releases":[{"0":"2712","vim_version":"7.0","1":"7.0","script_version":"0.0.3","2":"0.0.3","version_comment":"- fix warning of SDEnable. sorry.\r\n- add g:SD_disable.\r\n","3":"- fix warning of SDEnable. sorry.\r\n- add g:SD_disable.\r\n","package":"sign-diff.vim","4":"sign-diff.vim","src_id":"11065","5":"11065","creation_date":"1248596300","6":"1248596300"},{"0":"2712","vim_version":"7.0","1":"7.0","script_version":"0.0.2","2":"0.0.2","version_comment":"- supports GetLatestVimScripts\r\n- supports Windows (but cmd.exe shows up at front most...)\r\n- fix the bug that the changed lines are highlighted as the added lines...\r\n- supports difftext(the one changed line). if you wish to let this plugin\r\nbehave same as previous version, put \"let g:SD_sign_text = '*'\" and\r\n\"let g:SD_hl_difftext = 'DiffAdd'\" into your .vimrc\r\n","3":"- supports GetLatestVimScripts\r\n- supports Windows (but cmd.exe shows up at front most...)\r\n- fix the bug that the changed lines are highlighted as the added lines...\r\n- supports difftext(the one changed line). if you wish to let this plugin\r\nbehave same as previous version, put \"let g:SD_sign_text = '*'\" and\r\n\"let g:SD_hl_difftext = 'DiffAdd'\" into your .vimrc\r\n","package":"sign-diff.vim","4":"sign-diff.vim","src_id":"11023","5":"11023","creation_date":"1247822782","6":"1247822782"},{"0":"2712","vim_version":"7.0","1":"7.0","script_version":"0.0.1","2":"0.0.1","version_comment":"- strict check the global options.\r\n- no new files are created when g:SD_comp_with is default value.\r\n- fix some bugs.","3":"- strict check the global options.\r\n- no new files are created when g:SD_comp_with is default value.\r\n- fix some bugs.","package":"sign-diff.vim","4":"sign-diff.vim","src_id":"11017","5":"11017","creation_date":"1247710037","6":"1247710037"},{"0":"2712","vim_version":"7.0","1":"7.0","script_version":"0.0.0","2":"0.0.0","version_comment":"Initial upload","3":"Initial upload","package":"sign-diff.vim","4":"sign-diff.vim","src_id":"11014","5":"11014","creation_date":"1247674753","6":"1247674753"}]},"2711":{"script_id":"2711","0":"2711","script_name":"Screen (vim + gnu screen\/tmux)","1":"Screen (vim + gnu screen\/tmux)","script_type":"utility","2":"utility","summary":"Simulate a split shell, using gnu screen or tmux, that you can send commands to.","3":"Simulate a split shell, using gnu screen or tmux, that you can send commands to.","description":"Screenshot:\r\nhttp:\/\/eclim.org\/_images\/screenshots\/vim\/screen_shell.png\r\n\r\nThis plugin aims to simulate an embedded shell in vim by allowing you to easily\r\nconvert your current vim session into one running in gnu screen (or tmux) with\r\na split gnu screen window containing a shell, and to quickly send statements \/\r\ncode to whatever program is running in that shell (bash, python, irb, etc.).\r\nSpawning the shell in your favorite terminal emulator is also supported for\r\ngvim users or anyone else that just prefers an external shell.\r\n\r\nCurrently tested on Linux and Windows (win32 gvim and cygwin vim), but\r\nshould also work on any unix based platform where screen is supported\r\n(OSX, BSD, Solaris, etc.).\r\n\r\nWindows Users: Whether you are using gvim or not, you will need cygwin\r\ninstalled with cygwin's bin directory in your windows PATH.\r\n\r\nCommands:\r\n  :ScreenShell [cmd] - Starts a screen hosted shell performing the\r\n    following steps depending on your environment.\r\n\r\n    When running a console vim on a unix based OS (Linux, BSD, OSX):\r\n      1. save a session file from your currently running vim instance\r\n         (current tab only)\r\n      2. start gnu screen with vim running in it\r\n      3. load your saved session file\r\n      4. create a lower gnu screen split window and start a shell, or if\r\n         g:ScreenShellExternal is set, start an external terminal with\r\n         screen running.\r\n      5. if a command was supplied to :ScreenShell, run it in the new\r\n         shell.\r\n         Ex. :ScreenShell ipython\r\n\r\n      Note: If you are already in a gnu screen session, then only steps\r\n            4 and 5 above will be run.\r\n\r\n    When running gvim:\r\n      1. start an external terminal with screen running.\r\n      2. if a command was supplied to :ScreenShell, run it in the new\r\n         shell.\r\n         Ex. :ScreenShell ipython\r\n\r\n  :ScreenSend - Send the visual selection or the entire buffer contents to\r\n    the running gnu screen shell window.\r\n\r\nAn example workflow may be:\r\n  Open a python file to work on:\r\n    $ vim something.py\r\n\r\n  Decide you want to run all or pieces of the code in an interactive\r\n  python shell:\r\n    :ScreenShell python\r\n\r\n  Send code from a vim buffer to the shell:\r\n    :ScreenSend\r\n\r\n  Quit the screen session and return to your original vim session:\r\n    :ScreenQuit\r\n      or\r\n    :qa\r\n\r\nhttp:\/\/github.com\/ervandew\/screen","4":"Screenshot:\r\nhttp:\/\/eclim.org\/_images\/screenshots\/vim\/screen_shell.png\r\n\r\nThis plugin aims to simulate an embedded shell in vim by allowing you to easily\r\nconvert your current vim session into one running in gnu screen (or tmux) with\r\na split gnu screen window containing a shell, and to quickly send statements \/\r\ncode to whatever program is running in that shell (bash, python, irb, etc.).\r\nSpawning the shell in your favorite terminal emulator is also supported for\r\ngvim users or anyone else that just prefers an external shell.\r\n\r\nCurrently tested on Linux and Windows (win32 gvim and cygwin vim), but\r\nshould also work on any unix based platform where screen is supported\r\n(OSX, BSD, Solaris, etc.).\r\n\r\nWindows Users: Whether you are using gvim or not, you will need cygwin\r\ninstalled with cygwin's bin directory in your windows PATH.\r\n\r\nCommands:\r\n  :ScreenShell [cmd] - Starts a screen hosted shell performing the\r\n    following steps depending on your environment.\r\n\r\n    When running a console vim on a unix based OS (Linux, BSD, OSX):\r\n      1. save a session file from your currently running vim instance\r\n         (current tab only)\r\n      2. start gnu screen with vim running in it\r\n      3. load your saved session file\r\n      4. create a lower gnu screen split window and start a shell, or if\r\n         g:ScreenShellExternal is set, start an external terminal with\r\n         screen running.\r\n      5. if a command was supplied to :ScreenShell, run it in the new\r\n         shell.\r\n         Ex. :ScreenShell ipython\r\n\r\n      Note: If you are already in a gnu screen session, then only steps\r\n            4 and 5 above will be run.\r\n\r\n    When running gvim:\r\n      1. start an external terminal with screen running.\r\n      2. if a command was supplied to :ScreenShell, run it in the new\r\n         shell.\r\n         Ex. :ScreenShell ipython\r\n\r\n  :ScreenSend - Send the visual selection or the entire buffer contents to\r\n    the running gnu screen shell window.\r\n\r\nAn example workflow may be:\r\n  Open a python file to work on:\r\n    $ vim something.py\r\n\r\n  Decide you want to run all or pieces of the code in an interactive\r\n  python shell:\r\n    :ScreenShell python\r\n\r\n  Send code from a vim buffer to the shell:\r\n    :ScreenSend\r\n\r\n  Quit the screen session and return to your original vim session:\r\n    :ScreenQuit\r\n      or\r\n    :qa\r\n\r\nhttp:\/\/github.com\/ervandew\/screen","install_details":"1. Download the vimball (screen.vba) to any directory.\r\n2. Open the file in vim ($ vim screen.vba)\r\n3. Source the file (:so %)","5":"1. Download the vimball (screen.vba) to any directory.\r\n2. Open the file in vim ($ vim screen.vba)\r\n3. Source the file (:so %)","first_name":"Eric","6":"Eric","last_name":"Van Dewoestine","7":"Van Dewoestine","releases":[{"0":"2711","vim_version":"7.0","1":"7.0","script_version":"1.5","2":"1.5","version_comment":"- expose :ScreenQuit command for all cases where screen.vim is the owner of a region, window, session, or terminal.\r\n- improved tmux pane handling for tmux 1.5 (backwards compatible for tmux 1.4).  Patch by Sung Pae","3":"- expose :ScreenQuit command for all cases where screen.vim is the owner of a region, window, session, or terminal.\r\n- improved tmux pane handling for tmux 1.5 (backwards compatible for tmux 1.4).  Patch by Sung Pae","package":"screen.vba","4":"screen.vba","src_id":"16100","5":"16100","creation_date":"1311091897","6":"1311091897"},{"0":"2711","vim_version":"7.0","1":"7.0","script_version":"1.4","2":"1.4","version_comment":"Fixes some tmux related focusing\/hanging issues.","3":"Fixes some tmux related focusing\/hanging issues.","package":"screen.vba","4":"screen.vba","src_id":"15361","5":"15361","creation_date":"1301762309","6":"1301762309"},{"0":"2711","vim_version":"7.0","1":"7.0","script_version":"1.3","2":"1.3","version_comment":"- added g:ScreenVersion var indicating the screen plugin version (requested by Jakson Alves de Aquino)\r\n- added a setting which enables expansion of tabs to spaces before sending to the target app running in screen (suggested by Joe Bain)\r\n- fixed focusing tmux pane when splitting vertically (thanks to Ben Boeckel)\r\n- added option to force attaching to the currently focused screen region when attaching to an existing session.","3":"- added g:ScreenVersion var indicating the screen plugin version (requested by Jakson Alves de Aquino)\r\n- added a setting which enables expansion of tabs to spaces before sending to the target app running in screen (suggested by Joe Bain)\r\n- fixed focusing tmux pane when splitting vertically (thanks to Ben Boeckel)\r\n- added option to force attaching to the currently focused screen region when attaching to an existing session.","package":"screen.vba","4":"screen.vba","src_id":"14174","5":"14174","creation_date":"1288845359","6":"1288845359"},{"0":"2711","vim_version":"7.0","1":"7.0","script_version":"1.2","2":"1.2","version_comment":"- suppress screen message when sending text to it\r\n- moved the bulk of the logic to an autoload script\r\n- support for tmux 1.3 added (previous version of tmux no longer supported) (thanks to Ben Boeckel)\r\n- update ScreenShellAttach for newer screen listings (thanks to benbooth5)\r\n- other enhancements + bug fixes","3":"- suppress screen message when sending text to it\r\n- moved the bulk of the logic to an autoload script\r\n- support for tmux 1.3 added (previous version of tmux no longer supported) (thanks to Ben Boeckel)\r\n- update ScreenShellAttach for newer screen listings (thanks to benbooth5)\r\n- other enhancements + bug fixes","package":"screen.vba","4":"screen.vba","src_id":"13929","5":"13929","creation_date":"1285555961","6":"1285555961"},{"0":"2711","vim_version":"7.0","1":"7.0","script_version":"1.1","2":"1.1","version_comment":"- fixed to handle non screen TERM env var better\r\n- added support for vertically split screen\/tmux regions (suggested by Hemant Borole)\r\n- added setting to specify whether vim or the shell gain focus when first opening a split region (suggested by Sung Pae)","3":"- fixed to handle non screen TERM env var better\r\n- added support for vertically split screen\/tmux regions (suggested by Hemant Borole)\r\n- added setting to specify whether vim or the shell gain focus when first opening a split region (suggested by Sung Pae)","package":"screen.vba","4":"screen.vba","src_id":"12180","5":"12180","creation_date":"1264435334","6":"1264435334"},{"0":"2711","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"- added support for using tmux instead of gnu screen\r\n- now distributing as a vimball with a help file (:h screen)","3":"- added support for using tmux instead of gnu screen\r\n- now distributing as a vimball with a help file (:h screen)","package":"screen.vba","4":"screen.vba","src_id":"11845","5":"11845","creation_date":"1259816751","6":"1259816751"},{"0":"2711","vim_version":"7.0","1":"7.0","script_version":"0.8","2":"0.8","version_comment":"Added a global funcref allowing other plugins to send strings to the running screen session (based on suggestion by Jakson Alves de Aquino)","3":"Added a global funcref allowing other plugins to send strings to the running screen session (based on suggestion by Jakson Alves de Aquino)","package":"screen.vim","4":"screen.vim","src_id":"11519","5":"11519","creation_date":"1255357096","6":"1255357096"},{"0":"2711","vim_version":"7.0","1":"7.0","script_version":"0.7","2":"0.7","version_comment":"- fixed grabbing of partial visual selection on one line for sending\r\n- now suppresses vim's reload prompt when returning to your original vim session, and auto reloads the modified files for you.","3":"- fixed grabbing of partial visual selection on one line for sending\r\n- now suppresses vim's reload prompt when returning to your original vim session, and auto reloads the modified files for you.","package":"screen.vim","4":"screen.vim","src_id":"11343","5":"11343","creation_date":"1252420379","6":"1252420379"},{"0":"2711","vim_version":"7.0","1":"7.0","script_version":"0.6","2":"0.6","version_comment":"- fixed running :ScreenShell when vim is already in a screen session.\r\n- fixed starting screen in an external terminal on Windows.\r\n- fixed executing of command supplied to :ScreenShell when using an external shell (thanks to Tobais Wolf for reporting this issue).","3":"- fixed running :ScreenShell when vim is already in a screen session.\r\n- fixed starting screen in an external terminal on Windows.\r\n- fixed executing of command supplied to :ScreenShell when using an external shell (thanks to Tobais Wolf for reporting this issue).","package":"screen.vim","4":"screen.vim","src_id":"11266","5":"11266","creation_date":"1251301521","6":"1251301521"},{"0":"2711","vim_version":"7.0","1":"7.0","script_version":"0.5","2":"0.5","version_comment":"- gvim (windows, linux, etc.) now supported by forcing usage of an external terminal\r\n- multiple vim instances running independent screen shells now supported\r\n- when using an external terminal from a console vim, only restart vim in a screen session if g:ScreenShellServername is set and clientserver is supported.\r\n- ability to attach to an existing screen session.","3":"- gvim (windows, linux, etc.) now supported by forcing usage of an external terminal\r\n- multiple vim instances running independent screen shells now supported\r\n- when using an external terminal from a console vim, only restart vim in a screen session if g:ScreenShellServername is set and clientserver is supported.\r\n- ability to attach to an existing screen session.","package":"screen.vim","4":"screen.vim","src_id":"11243","5":"11243","creation_date":"1251086283","6":"1251086283"},{"0":"2711","vim_version":"7.0","1":"7.0","script_version":"0.4","2":"0.4","version_comment":"- fixed usage in cygwin, which the previous version broke\r\n- fixed handling of large amounts of text sent through :ScreenSend (thanks to Tobias Wolf for discovering the issue)\r\n","3":"- fixed usage in cygwin, which the previous version broke\r\n- fixed handling of large amounts of text sent through :ScreenSend (thanks to Tobias Wolf for discovering the issue)\r\n","package":"screen.vim","4":"screen.vim","src_id":"11180","5":"11180","creation_date":"1250088767","6":"1250088767"},{"0":"2711","vim_version":"7.0","1":"7.0","script_version":"0.3","2":"0.3","version_comment":"- Improved error handling running :ScreenShell when not all buffers can be saved.\r\nSeveral enhancements based on suggestions by Tobias Wolf.\r\n- Added support for spawning a terminal instead of using a split region for the shell.\r\n- The vim instance started in screen now has its server name set, permitting remote calls.\r\n- The shell screen window title is now based on the command supplied to :ScreenShell, if any.\r\n- Other minor improvements behind the scenes.","3":"- Improved error handling running :ScreenShell when not all buffers can be saved.\r\nSeveral enhancements based on suggestions by Tobias Wolf.\r\n- Added support for spawning a terminal instead of using a split region for the shell.\r\n- The vim instance started in screen now has its server name set, permitting remote calls.\r\n- The shell screen window title is now based on the command supplied to :ScreenShell, if any.\r\n- Other minor improvements behind the scenes.","package":"screen.vim","4":"screen.vim","src_id":"11170","5":"11170","creation_date":"1249918046","6":"1249918046"},{"0":"2711","vim_version":"7.0","1":"7.0","script_version":"0.2","2":"0.2","version_comment":"Replaced control characters with the vim escape sequence equivalents.\r\n","3":"Replaced control characters with the vim escape sequence equivalents.\r\n","package":"screen.vim","4":"screen.vim","src_id":"11125","5":"11125","creation_date":"1249344775","6":"1249344775"},{"0":"2711","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"screen.vim","4":"screen.vim","src_id":"10999","5":"10999","creation_date":"1247340837","6":"1247340837"}]},"2710":{"script_id":"2710","0":"2710","script_name":"vimrc","1":"vimrc","script_type":"utility","2":"utility","summary":"Word Processing in Vim (_vimrc win32)","3":"Word Processing in Vim (_vimrc win32)","description":"Better than cream + menu for console version.\r\nCTRL+M makes a console menu pop up.\r\nWorks for GVim and Vim\r\nCan toggle between Word Processor Mode (word wrap\/spell)","4":"Better than cream + menu for console version.\r\nCTRL+M makes a console menu pop up.\r\nWorks for GVim and Vim\r\nCan toggle between Word Processor Mode (word wrap\/spell)","install_details":"Just backup your _vimrc and try this one.","5":"Just backup your _vimrc and try this one.","first_name":"Roy","6":"Roy","last_name":"Mathur","7":"Mathur","releases":[{"0":"2710","vim_version":"7.2","1":"7.2","script_version":"1","2":"1","version_comment":"Initial upload","3":"Initial upload","package":"_vimrc","4":"_vimrc","src_id":"10986","5":"10986","creation_date":"1247233315","6":"1247233315"}]},"2709":{"script_id":"2709","0":"2709","script_name":"SudoEdit.vim","1":"SudoEdit.vim","script_type":"utility","2":"utility","summary":"Edit Files using sudo or su or any other tool","3":"Edit Files using sudo or su or any other tool","description":"If you like this plugin, please rate it!\r\n\r\nThis plugin enables vim to read files, using sudo or su or any other tool that\r\ncan be used for changing the authentication of a user. Therefore it needs any\r\nof sudo or su installed and usable by the user. This means, you have to know\r\nthe credentials to authenticate yourself as somebody else.\r\n\r\nThis plugin is basically an extended version from sudo.vim \r\n(http:\/\/www.vim.org\/scripts\/script.php?script_id=729), which seems to be \r\nunmaintained now. For compatibility reasons, it also supports the sudo: protocol \r\nhandler, as sudo.vim provides. \r\n\r\nThat's why this plugin probably won't work on Windows, but you might be able\r\nto configure it to use a method that works on Windows (see :h SudoEdit-config)\r\n\r\nBy default SudoEdit will first try to use sudo and if sudo is not found it\r\nwill fall back and try to use su. Note, that you might have to configure these\r\ntools, before they can use them successfully.\r\n\r\nSudoEdit requires at least a Vim Version 7 with patch 111 installed. Patch 111\r\nintroduced the shellescape() functionality.\r\n\r\nThe Plugin provides the 2 Commands :SudoRead for reading a file and SudoWrite\r\nfor writing a file using the provided super user authentication mechanism. Both \r\ncommands have file completion enabled to ease the selection of files (if you are able \r\nto read the path as ordinary user).\r\n\r\nYou can optionally configure it to use any other tool, instead of sudo\/su. So you could \r\nprobably adjust it to work on Windows or you can use ssh as authentication method.","4":"If you like this plugin, please rate it!\r\n\r\nThis plugin enables vim to read files, using sudo or su or any other tool that\r\ncan be used for changing the authentication of a user. Therefore it needs any\r\nof sudo or su installed and usable by the user. This means, you have to know\r\nthe credentials to authenticate yourself as somebody else.\r\n\r\nThis plugin is basically an extended version from sudo.vim \r\n(http:\/\/www.vim.org\/scripts\/script.php?script_id=729), which seems to be \r\nunmaintained now. For compatibility reasons, it also supports the sudo: protocol \r\nhandler, as sudo.vim provides. \r\n\r\nThat's why this plugin probably won't work on Windows, but you might be able\r\nto configure it to use a method that works on Windows (see :h SudoEdit-config)\r\n\r\nBy default SudoEdit will first try to use sudo and if sudo is not found it\r\nwill fall back and try to use su. Note, that you might have to configure these\r\ntools, before they can use them successfully.\r\n\r\nSudoEdit requires at least a Vim Version 7 with patch 111 installed. Patch 111\r\nintroduced the shellescape() functionality.\r\n\r\nThe Plugin provides the 2 Commands :SudoRead for reading a file and SudoWrite\r\nfor writing a file using the provided super user authentication mechanism. Both \r\ncommands have file completion enabled to ease the selection of files (if you are able \r\nto read the path as ordinary user).\r\n\r\nYou can optionally configure it to use any other tool, instead of sudo\/su. So you could \r\nprobably adjust it to work on Windows or you can use ssh as authentication method.","install_details":"Edit SudoEdit.vba and source the file\r\n:so %\r\nis all you need. It will install the plugin and also the documentation.\r\n\r\nI suggest you take a look at :h SudoEdit.txt before using it.","5":"Edit SudoEdit.vba and source the file\r\n:so %\r\nis all you need. It will install the plugin and also the documentation.\r\n\r\nI suggest you take a look at :h SudoEdit.txt before using it.","first_name":"Christian","6":"Christian","last_name":"Brabandt","7":"Brabandt","releases":[{"0":"2709","vim_version":"7.4","1":"7.4","script_version":"21","2":"21","version_comment":"- temporarily set shelltemp (issue https:\/\/github.com\/chrisbra\/SudoEdit.vim\/issues\/32, reported by Fernando da Silva, thanks!)\n- Do not trigger autocommands when writing temp files\n- Make UAC actually work for Windows\n- many small improvements for Windows\n- do not call expand() for \/usr\/bin\/zsh variables (issue https:\/\/github.com\/chrisbra\/SudoEdit.vim\/pull\/34, fixed by Daniel Hahler, thanks!)\n- remove writable file always (and make sure it will be different in case of the Vim running twice).\n- Reset 'shellslash' on windows (suggested by Boris Danilov, thanks!)\n- change redirection when calling UAC vbs script (suggested by Boris Danilov, thanks!)\n- distribute the UAC VBScript together with the SudoEdit plugin\n- fix spelling mistakes (issue https:\/\/github.com\/chrisbra\/SudoEdit.vim\/pull\/35, fixed by Tim S\u00c3\u0083\u00c6\u0092\u00c3\u0082\u00c2\u00a6ter\u00c3\u0083\u00c6\u0092\u00c3\u0082\u00c2\u00b8y, thanks!)\n- Check file modification time before asking for reloading buffers\n(automatically uploaded)","3":"- temporarily set shelltemp (issue https:\/\/github.com\/chrisbra\/SudoEdit.vim\/issues\/32, reported by Fernando da Silva, thanks!)\n- Do not trigger autocommands when writing temp files\n- Make UAC actually work for Windows\n- many small improvements for Windows\n- do not call expand() for \/usr\/bin\/zsh variables (issue https:\/\/github.com\/chrisbra\/SudoEdit.vim\/pull\/34, fixed by Daniel Hahler, thanks!)\n- remove writable file always (and make sure it will be different in case of the Vim running twice).\n- Reset 'shellslash' on windows (suggested by Boris Danilov, thanks!)\n- change redirection when calling UAC vbs script (suggested by Boris Danilov, thanks!)\n- distribute the UAC VBScript together with the SudoEdit plugin\n- fix spelling mistakes (issue https:\/\/github.com\/chrisbra\/SudoEdit.vim\/pull\/35, fixed by Tim S\u00c3\u0083\u00c6\u0092\u00c3\u0082\u00c2\u00a6ter\u00c3\u0083\u00c6\u0092\u00c3\u0082\u00c2\u00b8y, thanks!)\n- Check file modification time before asking for reloading buffers\n(automatically uploaded)","package":"SudoEdit-0.21.vmb","4":"SudoEdit-0.21.vmb","src_id":"22796","5":"22796","creation_date":"1421351979","6":"1421351979"},{"0":"2709","vim_version":"7.4","1":"7.4","script_version":"20","2":"20","version_comment":"- skip writing undo, if the buffer hasn't been written.\n- document |g:sudo_tee| variable\n- possibly wrong undofile was written (issue https:\/\/github.com\/chrisbra\/SudoEdit.vim\/issues\/21, reported by blueyed, thanks!)\n(automatically uploaded)","3":"- skip writing undo, if the buffer hasn't been written.\n- document |g:sudo_tee| variable\n- possibly wrong undofile was written (issue https:\/\/github.com\/chrisbra\/SudoEdit.vim\/issues\/21, reported by blueyed, thanks!)\n(automatically uploaded)","package":"SudoEdit-0.20.vmb","4":"SudoEdit-0.20.vmb","src_id":"21681","5":"21681","creation_date":"1395958869","6":"1395958869"},{"0":"2709","vim_version":"7.3","1":"7.3","script_version":"19","2":"19","version_comment":" - |SudoWrite| should always write if a filename has been given (issue #23, reported by Daniel Hahler, thanks!)\n            - Better filename completion for |SudoWrite| and |SudoRead| commands (issue #20 reported by Daniel Hahler, thanks!)\n            - Fix error in VimLeave autocommand (issue #22, reported by Daniel Hahler, thanks!)\n            - reset 'shell' value (issue #24, reported by Raghavendra Prabhu, thanks!)\n(automatically uploaded)","3":" - |SudoWrite| should always write if a filename has been given (issue #23, reported by Daniel Hahler, thanks!)\n            - Better filename completion for |SudoWrite| and |SudoRead| commands (issue #20 reported by Daniel Hahler, thanks!)\n            - Fix error in VimLeave autocommand (issue #22, reported by Daniel Hahler, thanks!)\n            - reset 'shell' value (issue #24, reported by Raghavendra Prabhu, thanks!)\n(automatically uploaded)","package":"SudoEdit-0.19.vmb","4":"SudoEdit-0.19.vmb","src_id":"20650","5":"20650","creation_date":"1376512330","6":"1376512330"},{"0":"2709","vim_version":"7.3","1":"7.3","script_version":"18","2":"18","version_comment":"- expand() may return empty filenames (issue #17 patch by Daniel Hahler, thanks!)\n- better exception handling (issue #19)\n- included sudo.cmd for better usage on Windows\n- enable sudo.cmd to use UAC optionally\n(automatically uploaded)","3":"- expand() may return empty filenames (issue #17 patch by Daniel Hahler, thanks!)\n- better exception handling (issue #19)\n- included sudo.cmd for better usage on Windows\n- enable sudo.cmd to use UAC optionally\n(automatically uploaded)","package":"SudoEdit-0.18.vmb","4":"SudoEdit-0.18.vmb","src_id":"19526","5":"19526","creation_date":"1361053020","6":"1361053020"},{"0":"2709","vim_version":"7.3","1":"7.3","script_version":"17","2":"17","version_comment":"- Guard against a vim without persistent_undo feature\n- fix variable typo (https:\/\/github.com\/chrisbra\/SudoEdit.vim\/pull\/16 patch by NagatoPain, thanks!)\n(automatically uploaded)","3":"- Guard against a vim without persistent_undo feature\n- fix variable typo (https:\/\/github.com\/chrisbra\/SudoEdit.vim\/pull\/16 patch by NagatoPain, thanks!)\n(automatically uploaded)","package":"SudoEdit-0.17.vmb","4":"SudoEdit-0.17.vmb","src_id":"18440","5":"18440","creation_date":"1345483926","6":"1345483926"},{"0":"2709","vim_version":"7.3","1":"7.3","script_version":"16","2":"16","version_comment":"- Make the plugin usable on Windows |SudoEdit-Win|\n(automatically uploaded)","3":"- Make the plugin usable on Windows |SudoEdit-Win|\n(automatically uploaded)","package":"SudoEdit-0.16.vmb","4":"SudoEdit-0.16.vmb","src_id":"17988","5":"17988","creation_date":"1337282491","6":"1337282491"},{"0":"2709","vim_version":"7.3","1":"7.3","script_version":"15","2":"15","version_comment":"Fix Syntax error, reported by Gary Johnson, thanks!\n(automatically uploaded)","3":"Fix Syntax error, reported by Gary Johnson, thanks!\n(automatically uploaded)","package":"SudoEdit-0.15.vmb","4":"SudoEdit-0.15.vmb","src_id":"17899","5":"17899","creation_date":"1336458750","6":"1336458750"},{"0":"2709","vim_version":"7.3","1":"7.3","script_version":"14","2":"14","version_comment":"Fix issue 15 (https:\/\/github.com\/chrisbra\/SudoEdit.vim\/issues\/15, reported by Lenin Lee, thanks!)\n(automatically uploaded)","3":"Fix issue 15 (https:\/\/github.com\/chrisbra\/SudoEdit.vim\/issues\/15, reported by Lenin Lee, thanks!)\n(automatically uploaded)","package":"SudoEdit-0.14.vmb","4":"SudoEdit-0.14.vmb","src_id":"17841","5":"17841","creation_date":"1335794686","6":"1335794686"},{"0":"2709","vim_version":"7.3","1":"7.3","script_version":"13","2":"13","version_comment":"- in graphical Vim, display messages, so one knows, that one needs to enter the password (reported by Rob Shinn, thanks!)\n- Allow bang attribute to |SudoRead| and |SudoWrite|\n- Make use of graphical dialogs for sudo to read the passwords, if possible\n- Better debugging\n- Code cleanup\n- better filename completion with :SudoRead\/SudoWrite (now also supports completing sudo: protocol handler)\n(automatically uploaded)","3":"- in graphical Vim, display messages, so one knows, that one needs to enter the password (reported by Rob Shinn, thanks!)\n- Allow bang attribute to |SudoRead| and |SudoWrite|\n- Make use of graphical dialogs for sudo to read the passwords, if possible\n- Better debugging\n- Code cleanup\n- better filename completion with :SudoRead\/SudoWrite (now also supports completing sudo: protocol handler)\n(automatically uploaded)","package":"SudoEdit-0.13.vmb","4":"SudoEdit-0.13.vmb","src_id":"17831","5":"17831","creation_date":"1335612502","6":"1335612502"},{"0":"2709","vim_version":"7.3","1":"7.3","script_version":"12","2":"12","version_comment":"- Avoid redraw when changing permissions of the undofile\n- Don't move cursor on Reading\/Writing\n  (issue https:\/\/github.com\/chrisbra\/SudoEdit.vim\/issues\/11,\n  reported by Daniel Hahler, Thanks!)\n- Support for calling Netrw with another userid\/password\n  (issue https:\/\/github.com\/chrisbra\/SudoEdit.vim\/issues\/4,\n  reported by Daniel Hahler, Thanks!)\n- Autocmds for Writing did not fire (issue\n  https:\/\/github.com\/chrisbra\/SudoEdit.vim\/issues\/10, partly by\n  Raghavendra D Prabhu, Thanks!)\n- Newly created files are not set 'nomodified' (issue\n  https:\/\/github.com\/chrisbra\/SudoEdit.vim\/issues\/12, reported by\n  Daniel Hahler, Thanks!)\n- Can't create undofiles in write-protected directories (issue \n  https:\/\/github.com\/chrisbra\/SudoEdit.vim\/issues\/14, reported by\n  Matias Kangasj\u00c3\u0083\u00c6\u0092\u00c3\u0082\u00c2\u00a4rvel\u00c3\u0083\u00c6\u0092\u00c3\u0082\u00c2\u00a4, Thanks!)\n(automatically uploaded)","3":"- Avoid redraw when changing permissions of the undofile\n- Don't move cursor on Reading\/Writing\n  (issue https:\/\/github.com\/chrisbra\/SudoEdit.vim\/issues\/11,\n  reported by Daniel Hahler, Thanks!)\n- Support for calling Netrw with another userid\/password\n  (issue https:\/\/github.com\/chrisbra\/SudoEdit.vim\/issues\/4,\n  reported by Daniel Hahler, Thanks!)\n- Autocmds for Writing did not fire (issue\n  https:\/\/github.com\/chrisbra\/SudoEdit.vim\/issues\/10, partly by\n  Raghavendra D Prabhu, Thanks!)\n- Newly created files are not set 'nomodified' (issue\n  https:\/\/github.com\/chrisbra\/SudoEdit.vim\/issues\/12, reported by\n  Daniel Hahler, Thanks!)\n- Can't create undofiles in write-protected directories (issue \n  https:\/\/github.com\/chrisbra\/SudoEdit.vim\/issues\/14, reported by\n  Matias Kangasj\u00c3\u0083\u00c6\u0092\u00c3\u0082\u00c2\u00a4rvel\u00c3\u0083\u00c6\u0092\u00c3\u0082\u00c2\u00a4, Thanks!)\n(automatically uploaded)","package":"SudoEdit-0.12.vmb","4":"SudoEdit-0.12.vmb","src_id":"17355","5":"17355","creation_date":"1328043808","6":"1328043808"},{"0":"2709","vim_version":"7.3","1":"7.3","script_version":"11","2":"11","version_comment":"-change owner of undofile to that of the edited super-user file, so vim will automatically load the undofile when opening that file the next time (reported by Sean Farley and blueyed, thanks!)\n-Only set the filename using :f when writing to another file (https:\/\/github.com\/chrisbra\/SudoEdit.vim\/pull\/8 and also https:\/\/github.com\/chrisbra\/SudoEdit.vim\/issues\/5 patch by Daniel Hahler, thanks!)\n -fix https:\/\/github.com\/chrisbra\/SudoEdit.vim\/issues\/6 (fix permissions and path of the undofile, partly by Daniel Hahler, thanks!)\n-Don't reread the file and write undofiles for empty files (https:\/\/github.com\/chrisbra\/SudoEdit.vim\/issues\/7 reported by Daniel Hahler, thanks!)\n(automatically uploaded)","3":"-change owner of undofile to that of the edited super-user file, so vim will automatically load the undofile when opening that file the next time (reported by Sean Farley and blueyed, thanks!)\n-Only set the filename using :f when writing to another file (https:\/\/github.com\/chrisbra\/SudoEdit.vim\/pull\/8 and also https:\/\/github.com\/chrisbra\/SudoEdit.vim\/issues\/5 patch by Daniel Hahler, thanks!)\n -fix https:\/\/github.com\/chrisbra\/SudoEdit.vim\/issues\/6 (fix permissions and path of the undofile, partly by Daniel Hahler, thanks!)\n-Don't reread the file and write undofiles for empty files (https:\/\/github.com\/chrisbra\/SudoEdit.vim\/issues\/7 reported by Daniel Hahler, thanks!)\n(automatically uploaded)","package":"SudoEdit-0.11.vmb","4":"SudoEdit-0.11.vmb","src_id":"17071","5":"17071","creation_date":"1323961150","6":"1323961150"},{"0":"2709","vim_version":"7.3","1":"7.3","script_version":"10","2":"10","version_comment":"-fix https:\/\/github.com\/chrisbra\/SudoEdit.vim\/issues\/1 (exception 'emptyfile' not caught, reported by Daniel Hahler, thanks!)\n-fix https:\/\/github.com\/chrisbra\/SudoEdit.vim\/issues\/2 (Avoid W13 error, reported by Daniel Hahler, thanks!)\n-fix https:\/\/github.com\/chrisbra\/SudoEdit.vim\/issues\/3 (Write undofiles, reported by Daniel Hahler, thanks!)\n(automatically uploaded)","3":"-fix https:\/\/github.com\/chrisbra\/SudoEdit.vim\/issues\/1 (exception 'emptyfile' not caught, reported by Daniel Hahler, thanks!)\n-fix https:\/\/github.com\/chrisbra\/SudoEdit.vim\/issues\/2 (Avoid W13 error, reported by Daniel Hahler, thanks!)\n-fix https:\/\/github.com\/chrisbra\/SudoEdit.vim\/issues\/3 (Write undofiles, reported by Daniel Hahler, thanks!)\n(automatically uploaded)","package":"SudoEdit-0.10.vmb","4":"SudoEdit-0.10.vmb","src_id":"16897","5":"16897","creation_date":"1321569864","6":"1321569864"},{"0":"2709","vim_version":"7.0","1":"7.0","script_version":"0.8","2":"0.8","version_comment":"Make plugin autoloadable. See :h autoload-functions.","3":"Make plugin autoloadable. See :h autoload-functions.","package":"SudoEdit.vba","4":"SudoEdit.vba","src_id":"12872","5":"12872","creation_date":"1271714847","6":"1271714847"},{"0":"2709","vim_version":"7.0","1":"7.0","script_version":"0.7","2":"0.7","version_comment":"Support for reading\/writing using sudo:protocol handler\r\nAdded Debugging capabilities\r\n","3":"Support for reading\/writing using sudo:protocol handler\r\nAdded Debugging capabilities\r\n","package":"SudoEdit.vba","4":"SudoEdit.vba","src_id":"11599","5":"11599","creation_date":"1256592769","6":"1256592769"},{"0":"2709","vim_version":"7.0","1":"7.0","script_version":"0.6","2":"0.6","version_comment":"Fix minor bug, that prevents setting the filename correctly when writing.","3":"Fix minor bug, that prevents setting the filename correctly when writing.","package":"SudoEdit.vba","4":"SudoEdit.vba","src_id":"11012","5":"11012","creation_date":"1247592585","6":"1247592585"},{"0":"2709","vim_version":"7.0","1":"7.0","script_version":"0.5","2":"0.5","version_comment":"Minor documentation update","3":"Minor documentation update","package":"SudoEdit.vba","4":"SudoEdit.vba","src_id":"10975","5":"10975","creation_date":"1247085967","6":"1247085967"},{"0":"2709","vim_version":"7.0","1":"7.0","script_version":"0.5","2":"0.5","version_comment":"Enables the plugin for |GetLatestVimScripts|","3":"Enables the plugin for |GetLatestVimScripts|","package":"SudoEdit.vba","4":"SudoEdit.vba","src_id":"10974","5":"10974","creation_date":"1247085079","6":"1247085079"},{"0":"2709","vim_version":"7.0","1":"7.0","script_version":"0.4","2":"0.4","version_comment":"Initial upload","3":"Initial upload","package":"SudoEdit.vba","4":"SudoEdit.vba","src_id":"10973","5":"10973","creation_date":"1247084548","6":"1247084548"}]},"2708":{"script_id":"2708","0":"2708","script_name":"commentop.vim","1":"commentop.vim","script_type":"utility","2":"utility","summary":"commands and operators to comment\/uncomment lines in many languages","3":"commands and operators to comment\/uncomment lines in many languages","description":"!!NOTICE!! NO BACKWARD COMPATIBILITY FOR 1.0.2 OR BEFORE !!\r\n\r\nDescription:\r\n  This plugin provides a set of commands and operators  to comment or\r\n  uncomment lines. Linewise comment token (such as double quote in vim\r\n  script) is detected automatically by looking up filetype of the file.\r\n  Filetypes working well by default:\r\n    vim, python, perl, ruby, haskell, sh, bash, zsh, java, javascript,\r\n    Makefile, tex\r\n  With definition in this script, these also work:\r\n    (c), cpp, csharp, php, matlab\r\n\r\n  You can also easily define your own comment token for filetype. Add below\r\n  in your .vimrc:\r\n    CommentopSetCommentType FILETYPE REMOVEPATTERN INSERTSTRING\r\n\r\n  plugin keymaps:\r\n    <Plug>CommentopToggleNV    \" (n\/v) toggle comment [count] or visual lines\r\n    <Plug>CommentopAppendNV    \" (n\/v) comment out [count] or visual lines\r\n    <Plug>CommentopRemoveNV    \" (n\/v) uncomment [count] or visual lines\r\n\r\n    <Plug>CommentopToggleOP    \" (n op) toggle comment {motion}\r\n    <Plug>CommentopAppendOP    \" (n op) comment out {motion}\r\n    <Plug>CommentopRemoveOP    \" (n op) uncomment {motion}\r\n\r\n  default mapping:\r\n    co       <Plug>CommentopToggleNV\r\n    cO       <Plug>CommentopAppendNV\r\n    c<C-O>   <Plug>CommentopRemoveNV\r\n\r\n    go       <Plug>CommentopToggleOP\r\n    gO       <Plug>CommentopAppendOP\r\n    g<C-O>   <Plug>CommentopRemoveOP\r\n\r\nExamples:\r\n  in normal mode:\r\n     co          \" toggle comment for this line\r\n     3cO         \" comment out 3 lines\r\n\r\n  in normal mode (operator):\r\n     goip        \" toggle comment for this paragraph\r\n     gOa{        \" comment out this {} block\r\n\r\n  in visual mode:\r\n     c<C-O>      \" remove comments in visual selection\r\n","4":"!!NOTICE!! NO BACKWARD COMPATIBILITY FOR 1.0.2 OR BEFORE !!\r\n\r\nDescription:\r\n  This plugin provides a set of commands and operators  to comment or\r\n  uncomment lines. Linewise comment token (such as double quote in vim\r\n  script) is detected automatically by looking up filetype of the file.\r\n  Filetypes working well by default:\r\n    vim, python, perl, ruby, haskell, sh, bash, zsh, java, javascript,\r\n    Makefile, tex\r\n  With definition in this script, these also work:\r\n    (c), cpp, csharp, php, matlab\r\n\r\n  You can also easily define your own comment token for filetype. Add below\r\n  in your .vimrc:\r\n    CommentopSetCommentType FILETYPE REMOVEPATTERN INSERTSTRING\r\n\r\n  plugin keymaps:\r\n    <Plug>CommentopToggleNV    \" (n\/v) toggle comment [count] or visual lines\r\n    <Plug>CommentopAppendNV    \" (n\/v) comment out [count] or visual lines\r\n    <Plug>CommentopRemoveNV    \" (n\/v) uncomment [count] or visual lines\r\n\r\n    <Plug>CommentopToggleOP    \" (n op) toggle comment {motion}\r\n    <Plug>CommentopAppendOP    \" (n op) comment out {motion}\r\n    <Plug>CommentopRemoveOP    \" (n op) uncomment {motion}\r\n\r\n  default mapping:\r\n    co       <Plug>CommentopToggleNV\r\n    cO       <Plug>CommentopAppendNV\r\n    c<C-O>   <Plug>CommentopRemoveNV\r\n\r\n    go       <Plug>CommentopToggleOP\r\n    gO       <Plug>CommentopAppendOP\r\n    g<C-O>   <Plug>CommentopRemoveOP\r\n\r\nExamples:\r\n  in normal mode:\r\n     co          \" toggle comment for this line\r\n     3cO         \" comment out 3 lines\r\n\r\n  in normal mode (operator):\r\n     goip        \" toggle comment for this paragraph\r\n     gOa{        \" comment out this {} block\r\n\r\n  in visual mode:\r\n     c<C-O>      \" remove comments in visual selection\r\n","install_details":"Place this file in \/usr\/share\/vim\/vim*\/plugin or ~\/.vim\/plugin\/","5":"Place this file in \/usr\/share\/vim\/vim*\/plugin or ~\/.vim\/plugin\/","first_name":"Takahiro","6":"Takahiro","last_name":"SUZUKI","7":"SUZUKI","releases":[{"0":"2708","vim_version":"7.0","1":"7.0","script_version":"1.1.1","2":"1.1.1","version_comment":"simplified the script using range function.\r\ncounting WS with virtcol (work fine with mixture of tabs and spaces).\r\n","3":"simplified the script using range function.\r\ncounting WS with virtcol (work fine with mixture of tabs and spaces).\r\n","package":"commentop.vim","4":"commentop.vim","src_id":"11064","5":"11064","creation_date":"1248591158","6":"1248591158"},{"0":"2708","vim_version":"7.0","1":"7.0","script_version":"1.1.0","2":"1.1.0","version_comment":"simplified <Plug> maps (no backward compatibility for 1.0.2 or before)\r\ndetermine the comment string automatically (using 'commentstring')","3":"simplified <Plug> maps (no backward compatibility for 1.0.2 or before)\r\ndetermine the comment string automatically (using 'commentstring')","package":"commentop.vim","4":"commentop.vim","src_id":"11000","5":"11000","creation_date":"1247370397","6":"1247370397"},{"0":"2708","vim_version":"7.0","1":"7.0","script_version":"1.0.2","2":"1.0.2","version_comment":"bug fix (wrong comment string with ft=vim)","3":"bug fix (wrong comment string with ft=vim)","package":"commentop.vim","4":"commentop.vim","src_id":"10995","5":"10995","creation_date":"1247296385","6":"1247296385"},{"0":"2708","vim_version":"7.0","1":"7.0","script_version":"1.0.1","2":"1.0.1","version_comment":"bug fix (gO was mapped to comment out operator)","3":"bug fix (gO was mapped to comment out operator)","package":"commentop.vim","4":"commentop.vim","src_id":"10983","5":"10983","creation_date":"1247178764","6":"1247178764"},{"0":"2708","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"commentop.vim","4":"commentop.vim","src_id":"10972","5":"10972","creation_date":"1247083757","6":"1247083757"}]},"2707":{"script_id":"2707","0":"2707","script_name":"EnumToCase","1":"EnumToCase","script_type":"utility","2":"utility","summary":"Convert enumerated lists to case statements","3":"Convert enumerated lists to case statements","description":"This is a very simple plugin that converts a list of enumerated names (copied and pasted directly from an enum block) into a set of correctly indented case statements.\r\n\r\nThe command should be called as:\r\n\r\n:'<,'>EnumToCase\r\n\r\nMore details are available at http:\/\/sites.google.com\/site\/abudden\/contents\/Vim-Scripts\/enumtocase","4":"This is a very simple plugin that converts a list of enumerated names (copied and pasted directly from an enum block) into a set of correctly indented case statements.\r\n\r\nThe command should be called as:\r\n\r\n:'<,'>EnumToCase\r\n\r\nMore details are available at http:\/\/sites.google.com\/site\/abudden\/contents\/Vim-Scripts\/enumtocase","install_details":"Copy to the plugin\/ subdirectory in your .vim or vimfiles directory.","5":"Copy to the plugin\/ subdirectory in your .vim or vimfiles directory.","first_name":"Al","6":"Al","last_name":"Budden","7":"Budden","releases":[{"0":"2707","vim_version":"6.0","1":"6.0","script_version":"r282","2":"r282","version_comment":"Added optional support for maintaining end-of-line comments or anything.  More details on http:\/\/sites.google.com\/site\/abudden\/contents\/Vim-Scripts\/enumtocase","3":"Added optional support for maintaining end-of-line comments or anything.  More details on http:\/\/sites.google.com\/site\/abudden\/contents\/Vim-Scripts\/enumtocase","package":"enumtocase.vim","4":"enumtocase.vim","src_id":"11024","5":"11024","creation_date":"1247840534","6":"1247840534"},{"0":"2707","vim_version":"6.0","1":"6.0","script_version":"r281","2":"r281","version_comment":"Added support for comments in enum declaration (end-of-line comment suggestion from Timo Teifel).","3":"Added support for comments in enum declaration (end-of-line comment suggestion from Timo Teifel).","package":"enumtocase.vim","4":"enumtocase.vim","src_id":"11022","5":"11022","creation_date":"1247820710","6":"1247820710"},{"0":"2707","vim_version":"6.0","1":"6.0","script_version":"r272","2":"r272","version_comment":"Fixed bug in regular expression related to enumerations with a specified value.","3":"Fixed bug in regular expression related to enumerations with a specified value.","package":"enumtocase.vim","4":"enumtocase.vim","src_id":"10976","5":"10976","creation_date":"1247125322","6":"1247125322"},{"0":"2707","vim_version":"7.0","1":"7.0","script_version":"r271","2":"r271","version_comment":"Initial upload","3":"Initial upload","package":"enumtocase.vim","4":"enumtocase.vim","src_id":"10967","5":"10967","creation_date":"1247049858","6":"1247049858"}]},"2706":{"script_id":"2706","0":"2706","script_name":"PA_ruby_ri","1":"PA_ruby_ri","script_type":"utility","2":"utility","summary":"Plugin for getting `ri` documentation while you working with your ruby-like file","3":"Plugin for getting `ri` documentation while you working with your ruby-like file","description":" So, you are working with any ruby-like document(.rb, .rhtml, .rjs, etc) and need get to know some information regarding any ruby entity.\r\n In normal mode, put cursor on the word and press ,ri buttons. The ruby ri documentation will appear in command screen.\r\n Or, in visual mode, select needed word and press ,ri buttons. The ruby ri documentation will appear in command screen.\r\n That's all.\r\n","4":" So, you are working with any ruby-like document(.rb, .rhtml, .rjs, etc) and need get to know some information regarding any ruby entity.\r\n In normal mode, put cursor on the word and press ,ri buttons. The ruby ri documentation will appear in command screen.\r\n Or, in visual mode, select needed word and press ,ri buttons. The ruby ri documentation will appear in command screen.\r\n That's all.\r\n","install_details":"To install:\r\n  - Download the PA_ruby_ri.zip.\r\n  - Extract the zip archive into your runtime directory. The archive contains plugin\/PA_ruby_ri.vim, and doc\/PA_ruby_ri.txt.\r\n  - Start Vim or goto an existing instance of Vim.\r\n  - Execute the following command:\r\n\r\n      :helptag <your runtime directory\/doc>\r\n\r\n    This will generate all the help tags for any file located in the doc directory.\r\n\r\nThis plugin is only available if 'compatible' is not set and your operating system has installed ruby `ri` program.","5":"To install:\r\n  - Download the PA_ruby_ri.zip.\r\n  - Extract the zip archive into your runtime directory. The archive contains plugin\/PA_ruby_ri.vim, and doc\/PA_ruby_ri.txt.\r\n  - Start Vim or goto an existing instance of Vim.\r\n  - Execute the following command:\r\n\r\n      :helptag <your runtime directory\/doc>\r\n\r\n    This will generate all the help tags for any file located in the doc directory.\r\n\r\nThis plugin is only available if 'compatible' is not set and your operating system has installed ruby `ri` program.","first_name":"Andrij","6":"Andrij","last_name":"Pukalskyy","7":"Pukalskyy","releases":[{"0":"2706","vim_version":"7.0","1":"7.0","script_version":"0.0.1","2":"0.0.1","version_comment":"Initial upload","3":"Initial upload","package":"PA_ruby_ri.zip","4":"PA_ruby_ri.zip","src_id":"10959","5":"10959","creation_date":"1246899270","6":"1246899270"}]},"2705":{"script_id":"2705","0":"2705","script_name":"tiddlywiki","1":"tiddlywiki","script_type":"syntax","2":"syntax","summary":"TiddlyWiki syntax file","3":"TiddlyWiki syntax file","description":"For people who like the TiddlyWiki formatting syntax.\r\n\r\nhttp:\/\/tiddlywiki.org\/wiki\/TiddlyWiki_Markup","4":"For people who like the TiddlyWiki formatting syntax.\r\n\r\nhttp:\/\/tiddlywiki.org\/wiki\/TiddlyWiki_Markup","install_details":"Drop this file (tiddlywiki.vim) into ~\/.vim\/syntax\/ , open your file and :set syntax=tiddlywiki","5":"Drop this file (tiddlywiki.vim) into ~\/.vim\/syntax\/ , open your file and :set syntax=tiddlywiki","first_name":"Swaroop","6":"Swaroop","last_name":"C H","7":"C H","releases":[{"0":"2705","vim_version":"6.0","1":"6.0","script_version":"1","2":"1","version_comment":"Initial upload","3":"Initial upload","package":"tiddlywiki.vim","4":"tiddlywiki.vim","src_id":"10958","5":"10958","creation_date":"1246898880","6":"1246898880"}]},"2704":{"script_id":"2704","0":"2704","script_name":"mrpink","1":"mrpink","script_type":"color scheme","2":"color scheme","summary":"dark not black colorscheme","3":"dark not black colorscheme","description":"not that much pink. loved the movie.\r\n\r\nscreen\r\n\r\nhttp:\/\/yfrog.com\/9fmrpinkp","4":"not that much pink. loved the movie.\r\n\r\nscreen\r\n\r\nhttp:\/\/yfrog.com\/9fmrpinkp","install_details":"","5":"","first_name":"Mario","6":"Mario","last_name":"Gutierrez","7":"Gutierrez","releases":[{"0":"2704","vim_version":"7.0","1":"7.0","script_version":"1","2":"1","version_comment":"Initial upload","3":"Initial upload","package":"mrpink.vim","4":"mrpink.vim","src_id":"10957","5":"10957","creation_date":"1246898184","6":"1246898184"}]},"2703":{"script_id":"2703","0":"2703","script_name":"ReplaceWithRegister","1":"ReplaceWithRegister","script_type":"utility","2":"utility","summary":"Replace text with the contents of a register. ","3":"Replace text with the contents of a register. ","description":"DESCRIPTION\r\nReplacing an existing text with the contents of a register is a very common\r\ntask during editing. One typically first deletes the existing text via the\r\nd, D or dd commands, then pastes the register with p or P. Most of\r\nthe time, the unnamed register is involved, with the following pitfall: If you\r\nforget to delete into the black-hole register (\"_), the replacement text is\r\noverwritten!\r\n\r\nThis plugin offers a two-in-one command that replaces text covered by a\r\n{motion}, entire line(s) or the current selection with the contents of a\r\nregister; the old text is deleted into the black-hole register, i.e. it's\r\ngone. (But of course, the command can be easily undone.)\r\n\r\nThe replacement mode (characters or entire lines) is determined by the\r\nreplacement command \/ selection, not by the register contents. This avoids\r\nsurprises like when the replacement text was a linewise yank, but the\r\nreplacement is characterwise: In this case, no additional newline is inserted.\r\n\r\nSEE ALSO\r\n- ReplaceWithSameIndentRegister.vim (vimscript #5046) is a companion plugin\r\n  for the special (but frequent) case of replacing lines while keeping the\r\n  original indent.\r\n- LineJugglerCommands.vim (vimscript #4465) provides a similar :Replace [[\"]x]\r\n  Ex command.\r\n\r\nRELATED WORKS\r\n- regreplop.vim (vimscript #2702) provides an alternative implementation of\r\n  the same idea.\r\n- operator-replace (vimscript #2782) provides replacement of {motion} only,\r\n  depends on another library of the author, and does not have a default\r\n  mapping.\r\n- Luc Hermitte has an elegant minimalistic visual-mode mapping in\r\n  https:\/\/github.com\/LucHermitte\/lh-misc\/blob\/master\/plugin\/repl-visual-no-reg-overwrite.vim\r\n- EasyClip (https:\/\/github.com\/svermeulen\/vim-easyclip) changes the delete\r\n  commands to stop yanking, introduces a new \"m\" command for cutting, and also\r\n  provides an \"s\" substitution operator that pastes register contents over the\r\n  moved-over text.\r\n- R (replace) operator (vimscript #5239) provides an alternative\r\n  implementation that defaults to the clipboard register.\r\n- replace_operator.vim (vimscript #5742) provides normal (only with motion,\r\n  not by lines) and visual mode mappings.\r\n- subversive.vim (vimscript #5763) provides another alternative\r\n  implementation, has no default mappings, and as a unique feature provides a\r\n  two-motion operator that changes all occurrences in the moved-over range\r\n  with typed text; something similar to the functionality of my ChangeGlobally\r\n  plugin (vimscript #4321).\r\n\r\nUSAGE\r\n[count][\"x]gr{motion}   Replace {motion} text with the contents of register x.\r\n                        Especially when using the unnamed register, this is\r\n                        quicker than \"_d{motion}P or \"_c{motion}<C-R>\"\r\n[count][\"x]grr          Replace [count] lines with the contents of register x.\r\n                        To replace from the cursor position to the end of the\r\n                        line use [\"x]gr$\r\n{Visual}[\"x]gr          Replace the selection with the contents of register x.","4":"DESCRIPTION\r\nReplacing an existing text with the contents of a register is a very common\r\ntask during editing. One typically first deletes the existing text via the\r\nd, D or dd commands, then pastes the register with p or P. Most of\r\nthe time, the unnamed register is involved, with the following pitfall: If you\r\nforget to delete into the black-hole register (\"_), the replacement text is\r\noverwritten!\r\n\r\nThis plugin offers a two-in-one command that replaces text covered by a\r\n{motion}, entire line(s) or the current selection with the contents of a\r\nregister; the old text is deleted into the black-hole register, i.e. it's\r\ngone. (But of course, the command can be easily undone.)\r\n\r\nThe replacement mode (characters or entire lines) is determined by the\r\nreplacement command \/ selection, not by the register contents. This avoids\r\nsurprises like when the replacement text was a linewise yank, but the\r\nreplacement is characterwise: In this case, no additional newline is inserted.\r\n\r\nSEE ALSO\r\n- ReplaceWithSameIndentRegister.vim (vimscript #5046) is a companion plugin\r\n  for the special (but frequent) case of replacing lines while keeping the\r\n  original indent.\r\n- LineJugglerCommands.vim (vimscript #4465) provides a similar :Replace [[\"]x]\r\n  Ex command.\r\n\r\nRELATED WORKS\r\n- regreplop.vim (vimscript #2702) provides an alternative implementation of\r\n  the same idea.\r\n- operator-replace (vimscript #2782) provides replacement of {motion} only,\r\n  depends on another library of the author, and does not have a default\r\n  mapping.\r\n- Luc Hermitte has an elegant minimalistic visual-mode mapping in\r\n  https:\/\/github.com\/LucHermitte\/lh-misc\/blob\/master\/plugin\/repl-visual-no-reg-overwrite.vim\r\n- EasyClip (https:\/\/github.com\/svermeulen\/vim-easyclip) changes the delete\r\n  commands to stop yanking, introduces a new \"m\" command for cutting, and also\r\n  provides an \"s\" substitution operator that pastes register contents over the\r\n  moved-over text.\r\n- R (replace) operator (vimscript #5239) provides an alternative\r\n  implementation that defaults to the clipboard register.\r\n- replace_operator.vim (vimscript #5742) provides normal (only with motion,\r\n  not by lines) and visual mode mappings.\r\n- subversive.vim (vimscript #5763) provides another alternative\r\n  implementation, has no default mappings, and as a unique feature provides a\r\n  two-motion operator that changes all occurrences in the moved-over range\r\n  with typed text; something similar to the functionality of my ChangeGlobally\r\n  plugin (vimscript #4321).\r\n\r\nUSAGE\r\n[count][\"x]gr{motion}   Replace {motion} text with the contents of register x.\r\n                        Especially when using the unnamed register, this is\r\n                        quicker than \"_d{motion}P or \"_c{motion}<C-R>\"\r\n[count][\"x]grr          Replace [count] lines with the contents of register x.\r\n                        To replace from the cursor position to the end of the\r\n                        line use [\"x]gr$\r\n{Visual}[\"x]gr          Replace the selection with the contents of register x.","install_details":"INSTALLATION\r\nThe code is hosted in a Git repo at\r\n    https:\/\/github.com\/inkarkat\/vim-ReplaceWithRegister\r\nYou can use your favorite plugin manager, or \"git clone\" into a directory used\r\nfor Vim packages. Releases are on the \"stable\" branch, the latest unstable\r\ndevelopment snapshot on \"master\".\r\n\r\nThis script is also packaged as a vimball. If you have the \"gunzip\"\r\ndecompressor in your PATH, simply edit the *.vmb.gz package in Vim; otherwise,\r\ndecompress the archive first, e.g. using WinZip. Inside Vim, install by\r\nsourcing the vimball or via the :UseVimball command.\r\n    vim ReplaceWithRegister*.vmb.gz\r\n    :so %\r\nTo uninstall, use the :RmVimball command.\r\n\r\nDEPENDENCIES\r\n- Requires Vim 7.0 or higher.\r\n- repeat.vim (vimscript #2136) plugin (optional)\r\n  To support repetition with a register other than the default register, you\r\n  need version 1.1 or later.\r\n- visualrepeat.vim (vimscript #3848) plugin (version 2.00 or higher; optional)\r\n\r\nCONFIGURATION\r\nThe default mappings override the (rarely used, but somewhat related) gr\r\ncommand (replace virtual characters under the cursor with {char}).\r\nIf you want to use different mappings, map your keys to the\r\n<Plug>ReplaceWithRegister... mapping targets _before_ sourcing the script\r\n(e.g. in your vimrc):\r\n    nmap <Leader>r  <Plug>ReplaceWithRegisterOperator\r\n    nmap <Leader>rr <Plug>ReplaceWithRegisterLine\r\n    xmap <Leader>r  <Plug>ReplaceWithRegisterVisual","5":"INSTALLATION\r\nThe code is hosted in a Git repo at\r\n    https:\/\/github.com\/inkarkat\/vim-ReplaceWithRegister\r\nYou can use your favorite plugin manager, or \"git clone\" into a directory used\r\nfor Vim packages. Releases are on the \"stable\" branch, the latest unstable\r\ndevelopment snapshot on \"master\".\r\n\r\nThis script is also packaged as a vimball. If you have the \"gunzip\"\r\ndecompressor in your PATH, simply edit the *.vmb.gz package in Vim; otherwise,\r\ndecompress the archive first, e.g. using WinZip. Inside Vim, install by\r\nsourcing the vimball or via the :UseVimball command.\r\n    vim ReplaceWithRegister*.vmb.gz\r\n    :so %\r\nTo uninstall, use the :RmVimball command.\r\n\r\nDEPENDENCIES\r\n- Requires Vim 7.0 or higher.\r\n- repeat.vim (vimscript #2136) plugin (optional)\r\n  To support repetition with a register other than the default register, you\r\n  need version 1.1 or later.\r\n- visualrepeat.vim (vimscript #3848) plugin (version 2.00 or higher; optional)\r\n\r\nCONFIGURATION\r\nThe default mappings override the (rarely used, but somewhat related) gr\r\ncommand (replace virtual characters under the cursor with {char}).\r\nIf you want to use different mappings, map your keys to the\r\n<Plug>ReplaceWithRegister... mapping targets _before_ sourcing the script\r\n(e.g. in your vimrc):\r\n    nmap <Leader>r  <Plug>ReplaceWithRegisterOperator\r\n    nmap <Leader>rr <Plug>ReplaceWithRegisterLine\r\n    xmap <Leader>r  <Plug>ReplaceWithRegisterVisual","first_name":"Ingo","6":"Ingo","last_name":"Karkat","7":"Karkat","releases":[{"0":"2703","vim_version":"7.0","1":"7.0","script_version":"1.43","2":"1.43","version_comment":"- BUG: {count}grr does not repeat the count.\r\n- Suppress \"--No lines in buffer--\" message when replacing the entire buffer, and combine \"Deleted N lines\" \/ \"Added M lines\" into a single message that is given when either previous or new amount of lines reaches 'report'.","3":"- BUG: {count}grr does not repeat the count.\r\n- Suppress \"--No lines in buffer--\" message when replacing the entire buffer, and combine \"Deleted N lines\" \/ \"Added M lines\" into a single message that is given when either previous or new amount of lines reaches 'report'.","package":"ReplaceWithRegister-1.43.vmb.gz","4":"ReplaceWithRegister-1.43.vmb.gz","src_id":"26843","5":"26843","creation_date":"1574184619","6":"1574184619"},{"0":"2703","vim_version":"7.0","1":"7.0","script_version":"1.42","2":"1.42","version_comment":"- BUG: Previous version 1.41 broke replacement of single character with gr{motion}.","3":"- BUG: Previous version 1.41 broke replacement of single character with gr{motion}.","package":"ReplaceWithRegister-1.42.vmb.gz","4":"ReplaceWithRegister-1.42.vmb.gz","src_id":"22581","5":"22581","creation_date":"1414575692","6":"1414575692"},{"0":"2703","vim_version":"7.0","1":"7.0","script_version":"1.41","2":"1.41","version_comment":"- Also handle empty exclusive selection and empty text object (e.g. gri\" on \"\").\r\n","3":"- Also handle empty exclusive selection and empty text object (e.g. gri\" on \"\").\r\n","package":"ReplaceWithRegister-1.41.vmb.gz","4":"ReplaceWithRegister-1.41.vmb.gz","src_id":"21959","5":"21959","creation_date":"1401284574","6":"1401284574"},{"0":"2703","vim_version":"7.0","1":"7.0","script_version":"1.40","2":"1.40","version_comment":"- Avoid changing the jumplist.\r\n- Use optional visualrepeat#reapply#VisualMode() for normal mode repeat of a visual mapping. When supplying a [count] on such repeat of a previous linewise selection, now [count] number of lines instead of [count] times the original selection is used.","3":"- Avoid changing the jumplist.\r\n- Use optional visualrepeat#reapply#VisualMode() for normal mode repeat of a visual mapping. When supplying a [count] on such repeat of a previous linewise selection, now [count] number of lines instead of [count] times the original selection is used.","package":"ReplaceWithRegister-1.40.vmb.gz","4":"ReplaceWithRegister-1.40.vmb.gz","src_id":"21087","5":"21087","creation_date":"1385040472","6":"1385040472"},{"0":"2703","vim_version":"7.0","1":"7.0","script_version":"1.31","2":"1.31","version_comment":"BUG: When repeat.vim is not installed, the grr and v_gr mappings do nothing.\r\nNeed to :execute the :silent! call of repeat.vim to avoid that the remainder of the command line is aborted together with the call. Thanks for David Kotchan for reporting this.","3":"BUG: When repeat.vim is not installed, the grr and v_gr mappings do nothing.\r\nNeed to :execute the :silent! call of repeat.vim to avoid that the remainder of the command line is aborted together with the call. Thanks for David Kotchan for reporting this.","package":"ReplaceWithRegister-1.31.vmb.gz","4":"ReplaceWithRegister-1.31.vmb.gz","src_id":"19058","5":"19058","creation_date":"1354106456","6":"1354106456"},{"0":"2703","vim_version":"7.0","1":"7.0","script_version":"1.30","2":"1.30","version_comment":"- Adaptations for blockwise replace: \r\n  - If the register contains just a single line, temporarily duplicate the line to match the height of the blockwise selection. \r\n  - If the register contains multiple lines, paste as blockwise. \r\n- BUG: v:register is not replaced during command repetition, so repeat always used the unnamed register. Add register registration to enhanced repeat.vim plugin, which also handles repetition when used together with the expression register \"=. Requires a so far inofficial update to repeat.vim version 1.0 (that hopefully makes it into upstream), which is available at https:\/\/github.com\/inkarkat\/vim-repeat\/zipball\/1.0ENH1\r\n- Moved functions from plugin to separate autoload script. ","3":"- Adaptations for blockwise replace: \r\n  - If the register contains just a single line, temporarily duplicate the line to match the height of the blockwise selection. \r\n  - If the register contains multiple lines, paste as blockwise. \r\n- BUG: v:register is not replaced during command repetition, so repeat always used the unnamed register. Add register registration to enhanced repeat.vim plugin, which also handles repetition when used together with the expression register \"=. Requires a so far inofficial update to repeat.vim version 1.0 (that hopefully makes it into upstream), which is available at https:\/\/github.com\/inkarkat\/vim-repeat\/zipball\/1.0ENH1\r\n- Moved functions from plugin to separate autoload script. ","package":"ReplaceWithRegister.vba.gz","4":"ReplaceWithRegister.vba.gz","src_id":"17662","5":"17662","creation_date":"1332770534","6":"1332770534"},{"0":"2703","vim_version":"7.0","1":"7.0","script_version":"1.20","2":"1.20","version_comment":"- BUG: ReplaceWithRegisterOperator didn't work correctly with linewise motions (like \"+\"); need to use a linewise visual selection in this case. \r\n- BUG: Text duplicated from yanked previous lines is inserted on a replacement of a visual blockwise selection. Switch replacement mechanism to a put in visual mode in combination with a save and restore of the unnamed register. This should handle all cases and doesn't require the autoindent workaround, neither. ","3":"- BUG: ReplaceWithRegisterOperator didn't work correctly with linewise motions (like \"+\"); need to use a linewise visual selection in this case. \r\n- BUG: Text duplicated from yanked previous lines is inserted on a replacement of a visual blockwise selection. Switch replacement mechanism to a put in visual mode in combination with a save and restore of the unnamed register. This should handle all cases and doesn't require the autoindent workaround, neither. ","package":"ReplaceWithRegister.vba.gz","4":"ReplaceWithRegister.vba.gz","src_id":"15541","5":"15541","creation_date":"1303993037","6":"1303993037"},{"0":"2703","vim_version":"7.0","1":"7.0","script_version":"1.10","2":"1.10","version_comment":"- The operator-pending mapping now also handles 'nomodifiable' and 'readonly' buffers without function errors. \r\n- Add experimental support for repeating the replacement also in visual mode through visualrepeat.vim. Renamed vmap <Plug>ReplaceWithRegisterOperator toPlug>ReplaceWithRegisterVisual for that. *** PLEASE UPDATE YOUR CUSTOM MAPPINGS *** ","3":"- The operator-pending mapping now also handles 'nomodifiable' and 'readonly' buffers without function errors. \r\n- Add experimental support for repeating the replacement also in visual mode through visualrepeat.vim. Renamed vmap <Plug>ReplaceWithRegisterOperator toPlug>ReplaceWithRegisterVisual for that. *** PLEASE UPDATE YOUR CUSTOM MAPPINGS *** ","package":"ReplaceWithRegister.vba.gz","4":"ReplaceWithRegister.vba.gz","src_id":"15497","5":"15497","creation_date":"1303414805","6":"1303414805"},{"0":"2703","vim_version":"7.0","1":"7.0","script_version":"1.03","2":"1.03","version_comment":"- ENH: Better handling when buffer is 'nomodifiable' or 'readonly'. \r\n- Added separate help file and packaging the plugin as a vimball. ","3":"- ENH: Better handling when buffer is 'nomodifiable' or 'readonly'. \r\n- Added separate help file and packaging the plugin as a vimball. ","package":"ReplaceWithRegister.vba.gz","4":"ReplaceWithRegister.vba.gz","src_id":"14716","5":"14716","creation_date":"1294602767","6":"1294602767"},{"0":"2703","vim_version":"7.0","1":"7.0","script_version":"1.02","2":"1.02","version_comment":"Replaced the <SID>Count workaround with :map-expr and an intermediate expression. ","3":"Replaced the <SID>Count workaround with :map-expr and an intermediate expression. ","package":"ReplaceWithRegister.vim","4":"ReplaceWithRegister.vim","src_id":"11890","5":"11890","creation_date":"1260566775","6":"1260566775"},{"0":"2703","vim_version":"7.0","1":"7.0","script_version":"1.01","2":"1.01","version_comment":"Do not define \"gr\" mapping for select mode; printable characters should start insert mode. ","3":"Do not define \"gr\" mapping for select mode; printable characters should start insert mode. ","package":"ReplaceWithRegister.vim","4":"ReplaceWithRegister.vim","src_id":"11490","5":"11490","creation_date":"1254835484","6":"1254835484"},{"0":"2703","vim_version":"7.0","1":"7.0","script_version":"1.00","2":"1.00","version_comment":"Initial upload","3":"Initial upload","package":"ReplaceWithRegister.vim","4":"ReplaceWithRegister.vim","src_id":"10952","5":"10952","creation_date":"1246829357","6":"1246829357"}]},"2702":{"script_id":"2702","0":"2702","script_name":"regreplop.vim","1":"regreplop.vim","script_type":"utility","2":"utility","summary":"operator to replace motion\/visual with a register","3":"operator to replace motion\/visual with a register","description":"This plugin provides a operator to replace something(motion\/visual) with a\r\nspecified register.\r\nBy default, the operator is mapped at\r\n  <Plug>ReplaceMotion  \" for normal mode\r\n  <Plug>ReplaceLine    \" for normal mode (replace a line)\r\n  <Plug>ReplaceVisual  \" for visual mode\r\nand if there are no key mapping for <C-K>, <C-K> is mapped to these\r\noperators. (and <C-K><C-K> for ReplaceLine)\r\n\r\nIf you want to map them to another keys, add like below in your vimrc.\r\n  nmap YOURKEY <Plug>ReplaceMotion\r\n  nmap YOURKEY <Plug>ReplaceLine\r\n  vmap YOURKEY <Plug>ReplaceVisual\r\n\r\n----------------------------------------------------------------------------\r\nExamples:\r\n  in normal mode:\r\n     <C-K>iw     \" replace inner word with default register\r\n     \"a<C-K>iw   \" replace inner word with register a\r\n     <C-K>$      \" replace whole text right the cursor\r\n     <C-K><C-K>  \" replaces the line under cursor\r\n\r\n  in visual mode:\r\n     <C-K>       \" replace visual selection with default register\r\n     \"a<C-K>     \" replace visual selection with register a\r\n","4":"This plugin provides a operator to replace something(motion\/visual) with a\r\nspecified register.\r\nBy default, the operator is mapped at\r\n  <Plug>ReplaceMotion  \" for normal mode\r\n  <Plug>ReplaceLine    \" for normal mode (replace a line)\r\n  <Plug>ReplaceVisual  \" for visual mode\r\nand if there are no key mapping for <C-K>, <C-K> is mapped to these\r\noperators. (and <C-K><C-K> for ReplaceLine)\r\n\r\nIf you want to map them to another keys, add like below in your vimrc.\r\n  nmap YOURKEY <Plug>ReplaceMotion\r\n  nmap YOURKEY <Plug>ReplaceLine\r\n  vmap YOURKEY <Plug>ReplaceVisual\r\n\r\n----------------------------------------------------------------------------\r\nExamples:\r\n  in normal mode:\r\n     <C-K>iw     \" replace inner word with default register\r\n     \"a<C-K>iw   \" replace inner word with register a\r\n     <C-K>$      \" replace whole text right the cursor\r\n     <C-K><C-K>  \" replaces the line under cursor\r\n\r\n  in visual mode:\r\n     <C-K>       \" replace visual selection with default register\r\n     \"a<C-K>     \" replace visual selection with register a\r\n","install_details":"Place this file in \/usr\/share\/vim\/vim*\/plugin or ~\/.vim\/plugin\/\r\nNow replacing operator <C-K> is available.","5":"Place this file in \/usr\/share\/vim\/vim*\/plugin or ~\/.vim\/plugin\/\r\nNow replacing operator <C-K> is available.","first_name":"Takahiro","6":"Takahiro","last_name":"SUZUKI","7":"SUZUKI","releases":[{"0":"2702","vim_version":"7.0","1":"7.0","script_version":"1.1","2":"1.1","version_comment":"added ReplaceLine (default: <C-K><C-K>) to replace line with a register","3":"added ReplaceLine (default: <C-K><C-K>) to replace line with a register","package":"regreplop.vim","4":"regreplop.vim","src_id":"10960","5":"10960","creation_date":"1246947686","6":"1246947686"},{"0":"2702","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"regreplop.vim","4":"regreplop.vim","src_id":"10951","5":"10951","creation_date":"1246815629","6":"1246815629"}]},"2701":{"script_id":"2701","0":"2701","script_name":"editsrec","1":"editsrec","script_type":"utility","2":"utility","summary":"Vim Global Plugin for Editing .srec Files","3":"Vim Global Plugin for Editing .srec Files","description":"Vim Global Plugin for Editing .srec Files","4":"Vim Global Plugin for Editing .srec Files","install_details":"","5":"","first_name":"Alexander","6":"Alexander","last_name":"Fleck","7":"Fleck","releases":[{"0":"2701","vim_version":"7.0","1":"7.0","script_version":"00.02.20","2":"00.02.20","version_comment":"added Making a Set\r\n","3":"added Making a Set\r\n","package":"editsrec.vba","4":"editsrec.vba","src_id":"18988","5":"18988","creation_date":"1353189090","6":"1353189090"},{"0":"2701","vim_version":"7.0","1":"7.0","script_version":"00.02.10","2":"00.02.10","version_comment":"BugFix, wrong Source for CS in S5 Records\r\n","3":"BugFix, wrong Source for CS in S5 Records\r\n","package":"editsrec.vba","4":"editsrec.vba","src_id":"13194","5":"13194","creation_date":"1276633564","6":"1276633564"}]},"2700":{"script_id":"2700","0":"2700","script_name":"PKGBUILD","1":"PKGBUILD","script_type":"utility","2":"utility","summary":"helps editing and working with PKGBUILD files","3":"helps editing and working with PKGBUILD files","description":".","4":".","install_details":"Uncompress the tarball: \r\n\r\n   tar -xvzf PKGBUILD-*.tar.gz -C ~\/.vim \r\n","5":"Uncompress the tarball: \r\n\r\n   tar -xvzf PKGBUILD-*.tar.gz -C ~\/.vim \r\n","first_name":"Laszlo","6":"Laszlo","last_name":"Papp","7":"Papp","releases":[{"0":"2700","vim_version":"7.2","1":"7.2","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"PKGBUILD-0.1.tar.gz","4":"PKGBUILD-0.1.tar.gz","src_id":"10948","5":"10948","creation_date":"1246794188","6":"1246794188"}]},"2699":{"script_id":"2699","0":"2699","script_name":"argtextobj.vim","1":"argtextobj.vim","script_type":"utility","2":"utility","summary":"Text-object like motion for arguments","3":"Text-object like motion for arguments","description":"This plugin provides a text-object 'a' (argument). You can\r\nd(elete), c(hange), v(select)... an argument or inner argument in familiar ways.\r\nThat is, such as 'daa'(delete-an-argument) 'cia'(change-inner-argument) 'via'(select-inner-argument).\r\nWhat this script does is more than just typing\r\n  F,dt,\r\nbecause it recognizes inclusion relationship of parentheses.\r\n\r\nThere is an option to descide whether the motion should go out to toplevel function or not in nested function application.\r\n\r\nExamples:\r\n  case1) delete An argument\r\n      function(int arg1,    ch<press 'daa' here>ar* arg2=\"a,b,c(d,e)\")\r\n      function(int arg1<cursor here; and if you press 'daa' again..>)\r\n      function(<cursor>)\r\n\r\n  case2) change Inner argument\r\n      function(int arg1,    ch<press 'cia' here>ar* arg2=\"a,b,c(d,e)\")\r\n      function(int arg1,    <cursor here>)\r\n      \r\n  case 3) smart argument recognition (g:argumentobject_force_toplevel = 0)\r\n       function(1, (20<press 'cia' here>*30)+40, somefunc2(3, 4))\r\n       function(1, <cursor here>, somefunc2(3, 4))\r\n       \r\n       function(1, (20*30)+40, somefunc2(<press 'cia' here>3, 4))\r\n       function(1, (20*30)+40, somefunc2(<cursor here>4))\r\n\r\n  case 4) smart argument recognition (g:argumentobject_force_toplevel = 1)\r\n       function(1, (20<press 'cia' here>*30)+40, somefunc2(3, 4))\r\n       function(1, <cursor here>, somefunc2(3, 4)) \" note that this result is the same of above.\r\n       \r\n       function(1, (20*30)+40, somefunc2(<press 'cia' here>3, 4))\r\n       function(1, (20*30)+40, <cursor here>) \" sub-level function is deleted because it is a argument in terms of the outer function.\r\n","4":"This plugin provides a text-object 'a' (argument). You can\r\nd(elete), c(hange), v(select)... an argument or inner argument in familiar ways.\r\nThat is, such as 'daa'(delete-an-argument) 'cia'(change-inner-argument) 'via'(select-inner-argument).\r\nWhat this script does is more than just typing\r\n  F,dt,\r\nbecause it recognizes inclusion relationship of parentheses.\r\n\r\nThere is an option to descide whether the motion should go out to toplevel function or not in nested function application.\r\n\r\nExamples:\r\n  case1) delete An argument\r\n      function(int arg1,    ch<press 'daa' here>ar* arg2=\"a,b,c(d,e)\")\r\n      function(int arg1<cursor here; and if you press 'daa' again..>)\r\n      function(<cursor>)\r\n\r\n  case2) change Inner argument\r\n      function(int arg1,    ch<press 'cia' here>ar* arg2=\"a,b,c(d,e)\")\r\n      function(int arg1,    <cursor here>)\r\n      \r\n  case 3) smart argument recognition (g:argumentobject_force_toplevel = 0)\r\n       function(1, (20<press 'cia' here>*30)+40, somefunc2(3, 4))\r\n       function(1, <cursor here>, somefunc2(3, 4))\r\n       \r\n       function(1, (20*30)+40, somefunc2(<press 'cia' here>3, 4))\r\n       function(1, (20*30)+40, somefunc2(<cursor here>4))\r\n\r\n  case 4) smart argument recognition (g:argumentobject_force_toplevel = 1)\r\n       function(1, (20<press 'cia' here>*30)+40, somefunc2(3, 4))\r\n       function(1, <cursor here>, somefunc2(3, 4)) \" note that this result is the same of above.\r\n       \r\n       function(1, (20*30)+40, somefunc2(<press 'cia' here>3, 4))\r\n       function(1, (20*30)+40, <cursor here>) \" sub-level function is deleted because it is a argument in terms of the outer function.\r\n","install_details":"just place argtextobj.vim in \r\n\r\nLinux: ~\/.vim\/plugin\/ or \/usr\/share\/vim\/vim*\/plugin\/\r\nWindows $VIMRUNTIME\/plugin\/","5":"just place argtextobj.vim in \r\n\r\nLinux: ~\/.vim\/plugin\/ or \/usr\/share\/vim\/vim*\/plugin\/\r\nWindows $VIMRUNTIME\/plugin\/","first_name":"Takahiro","6":"Takahiro","last_name":"SUZUKI","7":"SUZUKI","releases":[{"0":"2699","vim_version":"7.0","1":"7.0","script_version":"1.1.1","2":"1.1.1","version_comment":"debug (stop beeping)","3":"debug (stop beeping)","package":"argtextobj.vim","4":"argtextobj.vim","src_id":"11985","5":"11985","creation_date":"1262196040","6":"1262196040"},{"0":"2699","vim_version":"7.0","1":"7.0","script_version":"1.1","2":"1.1","version_comment":"support for commas in quoted string (\"..\"), array ([..])\r\ndo nothing outside a function declaration\/call\r\n","3":"support for commas in quoted string (\"..\"), array ([..])\r\ndo nothing outside a function declaration\/call\r\n","package":"argtextobj.vim","4":"argtextobj.vim","src_id":"10943","5":"10943","creation_date":"1246724747","6":"1246724747"},{"0":"2699","vim_version":"7.2","1":"7.2","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"argtextobj.vim","4":"argtextobj.vim","src_id":"10939","5":"10939","creation_date":"1246708194","6":"1246708194"}]},"2698":{"script_id":"2698","0":"2698","script_name":"Dictionary file for Luxology Modo Python","1":"Dictionary file for Luxology Modo Python","script_type":"syntax","2":"syntax","summary":"Dictionary file for Luxology ModoScripting","3":"Dictionary file for Luxology ModoScripting","description":"This is just a dictionary file containing all(or most) of the internal functions-commands that Luxology Modo utilizes for external scripting languages like Perl, Python and Lua.\r\n\r\n\r\n\r\n","4":"This is just a dictionary file containing all(or most) of the internal functions-commands that Luxology Modo utilizes for external scripting languages like Perl, Python and Lua.\r\n\r\n\r\n\r\n","install_details":"Put this file into Vimfiles\/dict\/python (or your language of preferences). You need to enable dictionary completion in your vim settings or file type script to be able to utilize this dictionary pack. \r\n\r\nHere is my setup from ftplugin\/python\/python.vim\r\nset dictionary+=$VIM\/vimfiles\/dict\/python\/modo_globals.vim  iskeyword+=.,\r\n\r\n\r\nYou can also try adding this script to your Vim script arsenal for better workflow for your Modo scripts\r\nautocomplpop.vim : Automatically open the popup menu for completion \r\nhttp:\/\/www.vim.org\/scripts\/script.php?script_id=1879","5":"Put this file into Vimfiles\/dict\/python (or your language of preferences). You need to enable dictionary completion in your vim settings or file type script to be able to utilize this dictionary pack. \r\n\r\nHere is my setup from ftplugin\/python\/python.vim\r\nset dictionary+=$VIM\/vimfiles\/dict\/python\/modo_globals.vim  iskeyword+=.,\r\n\r\n\r\nYou can also try adding this script to your Vim script arsenal for better workflow for your Modo scripts\r\nautocomplpop.vim : Automatically open the popup menu for completion \r\nhttp:\/\/www.vim.org\/scripts\/script.php?script_id=1879","first_name":"kursad","6":"kursad","last_name":"karatas","7":"karatas","releases":[{"0":"2698","vim_version":"6.0","1":"6.0","script_version":"1","2":"1","version_comment":"Initial upload","3":"Initial upload","package":"modo_globals.vim","4":"modo_globals.vim","src_id":"10926","5":"10926","creation_date":"1246509416","6":"1246509416"}]},"2697":{"script_id":"2697","0":"2697","script_name":"elisex.vim","1":"elisex.vim","script_type":"color scheme","2":"color scheme","summary":"The colorscheme \"F\u00c3\u00bcr die Sexy Elise\".","3":"The colorscheme \"F\u00c3\u00bcr die Sexy Elise\".","description":"A pinky-yellowy-greeny colorscheme inspired on a popular\r\nclassical composition of \"Ludwig van Beethoven\", called\r\n\"F\u00c3\u00bcr Elise\" (For Elise). \r\n\r\nThis one uses bold and italic font styles to please your eyes.\r\n\r\nIf you aren't scarred by _Pink_ comments, you'll LOVE this scheme.\r\n\r\nNote: - Only standard (for all languages) highlight-groups are set.\r\n      - This colorscheme _should_ look nice everywhere.","4":"A pinky-yellowy-greeny colorscheme inspired on a popular\r\nclassical composition of \"Ludwig van Beethoven\", called\r\n\"F\u00c3\u00bcr Elise\" (For Elise). \r\n\r\nThis one uses bold and italic font styles to please your eyes.\r\n\r\nIf you aren't scarred by _Pink_ comments, you'll LOVE this scheme.\r\n\r\nNote: - Only standard (for all languages) highlight-groups are set.\r\n      - This colorscheme _should_ look nice everywhere.","install_details":"Just put it into your  ~\/.vim\/colors and try it with:\r\n    :color elisex\r\n\r\nAfter you try this colorscheme, you probably may want to use it every day.\r\nIf that is your case, then it is best to strip-off all useless comments\r\nand empty lines of the file. Executing these commands will do that:\r\n\r\n  * Remove all leading comments and empty lines with:\r\n       :%g\/\\(^$\\|^\\s\\+$\\)\\|\\(^\".*\\|^\\s\\+\".*\\)\/d\r\n\r\n  * Remove all leading spaces and tabs with:\r\n       :%s\/^\\s\\+\/\/g","5":"Just put it into your  ~\/.vim\/colors and try it with:\r\n    :color elisex\r\n\r\nAfter you try this colorscheme, you probably may want to use it every day.\r\nIf that is your case, then it is best to strip-off all useless comments\r\nand empty lines of the file. Executing these commands will do that:\r\n\r\n  * Remove all leading comments and empty lines with:\r\n       :%g\/\\(^$\\|^\\s\\+$\\)\\|\\(^\".*\\|^\\s\\+\".*\\)\/d\r\n\r\n  * Remove all leading spaces and tabs with:\r\n       :%s\/^\\s\\+\/\/g","first_name":"drachen","6":"drachen","last_name":"kiraa","7":"kiraa","releases":[{"0":"2697","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"elisex.vim","4":"elisex.vim","src_id":"10925","5":"10925","creation_date":"1246489623","6":"1246489623"}]},"2696":{"script_id":"2696","0":"2696","script_name":"elise.vim","1":"elise.vim","script_type":"color scheme","2":"color scheme","summary":"The colorscheme \"F\u00c3\u00bcr Elise\".","3":"The colorscheme \"F\u00c3\u00bcr Elise\".","description":"A pinky-yellowy-greeny colorscheme inspired on a popular\r\nclassical composition of \"Ludwig van Beethoven\", called\r\n\"F\u00c3\u00bcr Elise\" (For Elise).\r\n\r\nIf you aren't scarred by _Pink_ comments, you'll LOVE this scheme.\r\n\r\nNote: \r\n      - Only standard (for all languages) highlight-groups are set.\r\n      - This colorscheme _should_ look nice everywhere.\r\n\r\n","4":"A pinky-yellowy-greeny colorscheme inspired on a popular\r\nclassical composition of \"Ludwig van Beethoven\", called\r\n\"F\u00c3\u00bcr Elise\" (For Elise).\r\n\r\nIf you aren't scarred by _Pink_ comments, you'll LOVE this scheme.\r\n\r\nNote: \r\n      - Only standard (for all languages) highlight-groups are set.\r\n      - This colorscheme _should_ look nice everywhere.\r\n\r\n","install_details":"Just put it into your  ~\/.vim\/colors and try it with:\r\n    :color elise\r\nAfter you try this colorscheme, you probably may want to use it every day.\r\nIf that is your case, then it is best to strip-off all useless comments\r\nand empty lines of the file. Executing these commands will do that:\r\n\r\n  * Remove all leading comments and empty lines with:\r\n       :%g\/\\(^$\\|^\\s\\+$\\)\\|\\(^\".*\\|^\\s\\+\".*\\)\/d\r\n\r\n  * Remove all leading spaces and tabs with:\r\n       :%s\/^\\s\\+\/\/g","5":"Just put it into your  ~\/.vim\/colors and try it with:\r\n    :color elise\r\nAfter you try this colorscheme, you probably may want to use it every day.\r\nIf that is your case, then it is best to strip-off all useless comments\r\nand empty lines of the file. Executing these commands will do that:\r\n\r\n  * Remove all leading comments and empty lines with:\r\n       :%g\/\\(^$\\|^\\s\\+$\\)\\|\\(^\".*\\|^\\s\\+\".*\\)\/d\r\n\r\n  * Remove all leading spaces and tabs with:\r\n       :%s\/^\\s\\+\/\/g","first_name":"drachen","6":"drachen","last_name":"kiraa","7":"kiraa","releases":[{"0":"2696","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"elise.vim","4":"elise.vim","src_id":"10924","5":"10924","creation_date":"1246489490","6":"1246489490"}]},"2695":{"script_id":"2695","0":"2695","script_name":"EnhancedJumps","1":"EnhancedJumps","script_type":"utility","2":"utility","summary":"Enhanced jump and change list navigation commands. ","3":"Enhanced jump and change list navigation commands. ","description":"DESCRIPTION\r\nThis plugin enhances the built-in CTRL-I|\/|CTRL-O jump commands:\r\n- After a jump, the line, column and text of the next jump target are printed:\r\n    next: 3,9 ENHANCED JUMPS    by Ingo Karkat\r\n- An error message and the valid range for jumps in that direction is printed\r\n  if a jump outside the jump list is attempted:\r\n    Only 8 older jump positions.\r\n- In case the next jump would move to another buffer, only a warning is\r\n  printed at the first attempt:\r\n    next: EnhancedJumps.vim\r\n  The jump to another buffer is only done if the same jump command is repeated\r\n  once more immediately afterwards; like this: Pressing CTRL-O, noticing the\r\n  warning, then quickly pressing CTRL-O again to overcome the warning.\r\n  With this, you can eagerly jump around the current buffer. Because you will\r\n  be warned when a jump would move to another buffer, you're much less likely\r\n  to get lost.\r\n\r\nIn addition to the enhanced jump commands, separate special mappings are\r\navailable that restrict the jump targets to only local locations (in the same\r\nbuffer) and remote locations (only in other buffers).\r\n\r\nThis plugin enhances the built-in g;|\/|g, change list jump commands so that\r\nthey skip jumps to previous \/ later edit locations that lie within the\r\ncurrently visible range. This makes it easier to navigate between distant\r\nedits in a large buffer, without having to manually skip over all the local\r\nchanges.\r\n\r\nRELATED WORKS\r\n- back_to_recent_buffer.vim (vimscript #4290) implements going back to the\r\n  previous buffer.\r\n\r\nUSAGE\r\nSimply use the CTRL-O and CTRL-I commands to go to an older \/ newer cursor\r\nposition in the jump list. When a warning \"next: {file}\" is echoed, quickly\r\nrepeat the jump command to move to that buffer (a [count] need to not be\r\ntyped again; if you do include the [count], it must be the same as before).\r\nIf you do not want to move to that buffer, just ignore the warning, and\r\ncontinue browsing the current buffer. On the next jump attempt, the warning\r\nwill be repeated.\r\n\r\ng<CTRL-O>, g<CTRL-I>    Go to [count] older \/ newer cursor position in the\r\n                        current buffer. Jumps to other buffers are not\r\n                        considered. Useful when you mainly edited one file,\r\n                        briefly jumped to another, and now want to recall\r\n                        older positions without considering the other file.\r\n\r\n<Leader><CTRL-O>, <Leader><CTRL-I>\r\n                        Go to [count] older \/ newer cursor position in another\r\n                        buffer. Jumps inside the current buffer are not\r\n                        considered. Useful for recalling previously visited\r\n                        buffers without going through all local positions.\r\n                        Regardless of the jump direction, the last jump\r\n                        position in a buffer is used when there are multiple\r\n                        subsequent jumps in a buffer.\r\n\r\n<Leader><CTRL-W><CTRL-O>, <Leader><CTRL-W><CTRL-I>\r\n                        Go to [count] older \/ newer cursor position in another\r\n                        buffer. If the buffer is already visible in another\r\n                        window \/ tab page (g:EnhancedJumps_UseTab), switch\r\n                        to there instead of changing the buffer displayed in\r\n                        the current window.\r\n\r\nSimply use the g; and g, commands to go to an older \/ newer far change\r\nposition in the change list.\r\n\r\ng;                      Go to [count] older far change (that lies outside the\r\n                        currently visible range and is more than the current\r\n                        window height lines away from the previous change or\r\n                        the last accepted change).\r\n                        If [count] is larger than the number of older far\r\n                        change positions go to the oldest far change.\r\n                        If there is no older far change, go to the [count]\r\n                        older near change; i.e. fall back to the original\r\n                        behavior.\r\n                        If there is no older change an error message is given.\r\n                        (not a motion command)\r\ng,                      Go to [count] newer far change.\r\n                        Just like g; but in the opposite direction.","4":"DESCRIPTION\r\nThis plugin enhances the built-in CTRL-I|\/|CTRL-O jump commands:\r\n- After a jump, the line, column and text of the next jump target are printed:\r\n    next: 3,9 ENHANCED JUMPS    by Ingo Karkat\r\n- An error message and the valid range for jumps in that direction is printed\r\n  if a jump outside the jump list is attempted:\r\n    Only 8 older jump positions.\r\n- In case the next jump would move to another buffer, only a warning is\r\n  printed at the first attempt:\r\n    next: EnhancedJumps.vim\r\n  The jump to another buffer is only done if the same jump command is repeated\r\n  once more immediately afterwards; like this: Pressing CTRL-O, noticing the\r\n  warning, then quickly pressing CTRL-O again to overcome the warning.\r\n  With this, you can eagerly jump around the current buffer. Because you will\r\n  be warned when a jump would move to another buffer, you're much less likely\r\n  to get lost.\r\n\r\nIn addition to the enhanced jump commands, separate special mappings are\r\navailable that restrict the jump targets to only local locations (in the same\r\nbuffer) and remote locations (only in other buffers).\r\n\r\nThis plugin enhances the built-in g;|\/|g, change list jump commands so that\r\nthey skip jumps to previous \/ later edit locations that lie within the\r\ncurrently visible range. This makes it easier to navigate between distant\r\nedits in a large buffer, without having to manually skip over all the local\r\nchanges.\r\n\r\nRELATED WORKS\r\n- back_to_recent_buffer.vim (vimscript #4290) implements going back to the\r\n  previous buffer.\r\n\r\nUSAGE\r\nSimply use the CTRL-O and CTRL-I commands to go to an older \/ newer cursor\r\nposition in the jump list. When a warning \"next: {file}\" is echoed, quickly\r\nrepeat the jump command to move to that buffer (a [count] need to not be\r\ntyped again; if you do include the [count], it must be the same as before).\r\nIf you do not want to move to that buffer, just ignore the warning, and\r\ncontinue browsing the current buffer. On the next jump attempt, the warning\r\nwill be repeated.\r\n\r\ng<CTRL-O>, g<CTRL-I>    Go to [count] older \/ newer cursor position in the\r\n                        current buffer. Jumps to other buffers are not\r\n                        considered. Useful when you mainly edited one file,\r\n                        briefly jumped to another, and now want to recall\r\n                        older positions without considering the other file.\r\n\r\n<Leader><CTRL-O>, <Leader><CTRL-I>\r\n                        Go to [count] older \/ newer cursor position in another\r\n                        buffer. Jumps inside the current buffer are not\r\n                        considered. Useful for recalling previously visited\r\n                        buffers without going through all local positions.\r\n                        Regardless of the jump direction, the last jump\r\n                        position in a buffer is used when there are multiple\r\n                        subsequent jumps in a buffer.\r\n\r\n<Leader><CTRL-W><CTRL-O>, <Leader><CTRL-W><CTRL-I>\r\n                        Go to [count] older \/ newer cursor position in another\r\n                        buffer. If the buffer is already visible in another\r\n                        window \/ tab page (g:EnhancedJumps_UseTab), switch\r\n                        to there instead of changing the buffer displayed in\r\n                        the current window.\r\n\r\nSimply use the g; and g, commands to go to an older \/ newer far change\r\nposition in the change list.\r\n\r\ng;                      Go to [count] older far change (that lies outside the\r\n                        currently visible range and is more than the current\r\n                        window height lines away from the previous change or\r\n                        the last accepted change).\r\n                        If [count] is larger than the number of older far\r\n                        change positions go to the oldest far change.\r\n                        If there is no older far change, go to the [count]\r\n                        older near change; i.e. fall back to the original\r\n                        behavior.\r\n                        If there is no older change an error message is given.\r\n                        (not a motion command)\r\ng,                      Go to [count] newer far change.\r\n                        Just like g; but in the opposite direction.","install_details":"INSTALLATION\r\nThe code is hosted in a Git repo at\r\n    https:\/\/github.com\/inkarkat\/vim-EnhancedJumps\r\nYou can use your favorite plugin manager, or \"git clone\" into a directory used\r\nfor Vim packages. Releases are on the \"stable\" branch, the latest unstable\r\ndevelopment snapshot on \"master\".\r\n\r\nThis script is also packaged as a vimball. If you have the \"gunzip\"\r\ndecompressor in your PATH, simply edit the *.vmb.gz package in Vim; otherwise,\r\ndecompress the archive first, e.g. using WinZip. Inside Vim, install by\r\nsourcing the vimball or via the :UseVimball command.\r\n    vim EnhancedJumps*.vmb.gz\r\n    :so %\r\nTo uninstall, use the :RmVimball command.\r\n\r\nDEPENDENCIES\r\n- Requires Vim 7.0 or higher.\r\n- Requires the ingo-library.vim plugin (vimscript #4433), version 1.028 or\r\n  higher.\r\n\r\nCONFIGURATION\r\nFor a permanent configuration, put the following commands into your vimrc:\r\n\r\nThe time span in which the jump command must be repeated to overcome the\r\nwarning about jumping into another buffer defaults to (roughly) two seconds.\r\nTo change the timeout, set a different value (in milliseconds):\r\n    let g:stopFirstAndNotifyTimeoutLen = 2000\r\n\r\nJumps to another buffer happen with \"redir => l:fileJumpCapture\". If other\r\nplugins triggered by the (e.g. BufWinEnter) event do another :redir, this\r\ncauses an error, because nested redirs are prohibited. You can avoid this\r\nproblem by turning off the capture of jump messages:\r\n    let g:EnhancedJumps_CaptureJumpMessages = 0\r\n\r\nIf you don't want the <Leader>CTRL_W_CTRL-O \/ <Leader>CTRL_W_CTRL-I\r\nmappings to search other tab pages for windows containing the jump target:\r\n    let g:EnhancedJumps_UseTab = 0\r\n\r\nBy default, the nearest window that contains the buffer with the jump target\r\nis used. If you like to use the first buffer (like :sbuffer does), configure:\r\n    let g:EnhancedJumps_SwitchStrategy = 'first'\r\n\r\nIf you do not want to override the built-in jump commands and use separate\r\nmappings, or change the special additional mappings, map your keys to the\r\n<Plug>... mapping targets _before_ sourcing the script (e.g. in your vimrc).\r\n    nmap {          <Plug>EnhancedJumpsOlder\r\n    nmap }          <Plug>EnhancedJumpsNewer\r\n    nmap g{         <Plug>EnhancedJumpsLocalOlder\r\n    nmap g}         <Plug>EnhancedJumpsLocalNewer\r\n    nmap <Leader>{  <Plug>EnhancedJumpsRemoteOlder\r\n    nmap <Leader>}  <Plug>EnhancedJumpsRemoteNewer\r\n    nmap <C-w>{     <Plug>EnhancedJumpsSwitchRemoteOlder\r\n    nmap <C-w>}     <Plug>EnhancedJumpsSwitchRemoteNewer\r\nThere are also mappings that do both local and remote jumps, the latter\r\npotentially to another window \/ tab page, i.e. a combination of CTRL-O and\r\n<Leader>CTRL-W_CTRL-O. These are not mapped by default:\r\n    nmap ,{         <Plug>EnhancedJumpsSwitchOlder\r\n    nmap ,}         <Plug>EnhancedJumpsSwitchNewer\r\n\r\nFor the change list jump commands, you can choose between two alternatives,\r\nthe default one that falls back to near changes when there are no far changes\r\n    nmap z; <Plug>EnhancedJumpsFarFallbackChangeOlder\r\n    nmap z, <Plug>EnhancedJumpsFarFallbackChangeNewer\r\nand a pure \"far jumps\" variant:\r\n    nmap z; <Plug>EnhancedJumpsFarChangeOlder\r\n    nmap z, <Plug>EnhancedJumpsFarChangeNewer\r\n\r\nTo disable the special additional mappings:\r\n    nmap <Plug>DisableEnhancedJumpsLocalOlder  <Plug>EnhancedJumpsLocalOlder\r\n    nmap <Plug>DisableEnhancedJumpsLocalNewer  <Plug>EnhancedJumpsLocalNewer\r\n    nmap <Plug>DisableEnhancedJumpsRemoteOlder <Plug>EnhancedJumpsRemoteOlder\r\n    nmap <Plug>DisableEnhancedJumpsRemoteNewer <Plug>EnhancedJumpsRemoteNewer","5":"INSTALLATION\r\nThe code is hosted in a Git repo at\r\n    https:\/\/github.com\/inkarkat\/vim-EnhancedJumps\r\nYou can use your favorite plugin manager, or \"git clone\" into a directory used\r\nfor Vim packages. Releases are on the \"stable\" branch, the latest unstable\r\ndevelopment snapshot on \"master\".\r\n\r\nThis script is also packaged as a vimball. If you have the \"gunzip\"\r\ndecompressor in your PATH, simply edit the *.vmb.gz package in Vim; otherwise,\r\ndecompress the archive first, e.g. using WinZip. Inside Vim, install by\r\nsourcing the vimball or via the :UseVimball command.\r\n    vim EnhancedJumps*.vmb.gz\r\n    :so %\r\nTo uninstall, use the :RmVimball command.\r\n\r\nDEPENDENCIES\r\n- Requires Vim 7.0 or higher.\r\n- Requires the ingo-library.vim plugin (vimscript #4433), version 1.028 or\r\n  higher.\r\n\r\nCONFIGURATION\r\nFor a permanent configuration, put the following commands into your vimrc:\r\n\r\nThe time span in which the jump command must be repeated to overcome the\r\nwarning about jumping into another buffer defaults to (roughly) two seconds.\r\nTo change the timeout, set a different value (in milliseconds):\r\n    let g:stopFirstAndNotifyTimeoutLen = 2000\r\n\r\nJumps to another buffer happen with \"redir => l:fileJumpCapture\". If other\r\nplugins triggered by the (e.g. BufWinEnter) event do another :redir, this\r\ncauses an error, because nested redirs are prohibited. You can avoid this\r\nproblem by turning off the capture of jump messages:\r\n    let g:EnhancedJumps_CaptureJumpMessages = 0\r\n\r\nIf you don't want the <Leader>CTRL_W_CTRL-O \/ <Leader>CTRL_W_CTRL-I\r\nmappings to search other tab pages for windows containing the jump target:\r\n    let g:EnhancedJumps_UseTab = 0\r\n\r\nBy default, the nearest window that contains the buffer with the jump target\r\nis used. If you like to use the first buffer (like :sbuffer does), configure:\r\n    let g:EnhancedJumps_SwitchStrategy = 'first'\r\n\r\nIf you do not want to override the built-in jump commands and use separate\r\nmappings, or change the special additional mappings, map your keys to the\r\n<Plug>... mapping targets _before_ sourcing the script (e.g. in your vimrc).\r\n    nmap {          <Plug>EnhancedJumpsOlder\r\n    nmap }          <Plug>EnhancedJumpsNewer\r\n    nmap g{         <Plug>EnhancedJumpsLocalOlder\r\n    nmap g}         <Plug>EnhancedJumpsLocalNewer\r\n    nmap <Leader>{  <Plug>EnhancedJumpsRemoteOlder\r\n    nmap <Leader>}  <Plug>EnhancedJumpsRemoteNewer\r\n    nmap <C-w>{     <Plug>EnhancedJumpsSwitchRemoteOlder\r\n    nmap <C-w>}     <Plug>EnhancedJumpsSwitchRemoteNewer\r\nThere are also mappings that do both local and remote jumps, the latter\r\npotentially to another window \/ tab page, i.e. a combination of CTRL-O and\r\n<Leader>CTRL-W_CTRL-O. These are not mapped by default:\r\n    nmap ,{         <Plug>EnhancedJumpsSwitchOlder\r\n    nmap ,}         <Plug>EnhancedJumpsSwitchNewer\r\n\r\nFor the change list jump commands, you can choose between two alternatives,\r\nthe default one that falls back to near changes when there are no far changes\r\n    nmap z; <Plug>EnhancedJumpsFarFallbackChangeOlder\r\n    nmap z, <Plug>EnhancedJumpsFarFallbackChangeNewer\r\nand a pure \"far jumps\" variant:\r\n    nmap z; <Plug>EnhancedJumpsFarChangeOlder\r\n    nmap z, <Plug>EnhancedJumpsFarChangeNewer\r\n\r\nTo disable the special additional mappings:\r\n    nmap <Plug>DisableEnhancedJumpsLocalOlder  <Plug>EnhancedJumpsLocalOlder\r\n    nmap <Plug>DisableEnhancedJumpsLocalNewer  <Plug>EnhancedJumpsLocalNewer\r\n    nmap <Plug>DisableEnhancedJumpsRemoteOlder <Plug>EnhancedJumpsRemoteOlder\r\n    nmap <Plug>DisableEnhancedJumpsRemoteNewer <Plug>EnhancedJumpsRemoteNewer","first_name":"Ingo","6":"Ingo","last_name":"Karkat","7":"Karkat","releases":[{"0":"2695","vim_version":"7.0","1":"7.0","script_version":"3.10","2":"3.10","version_comment":"- ENH: Add <Leader><C-w><C-o> \/ <Leader><C-w><C-i> mappings to jump to the target buffer in an existing window.\r\n- Abort command sequence in case of jump errors. *** You need to update to ingo-library (vimscript #4433) version 1.028! ***","3":"- ENH: Add <Leader><C-w><C-o> \/ <Leader><C-w><C-i> mappings to jump to the target buffer in an existing window.\r\n- Abort command sequence in case of jump errors. *** You need to update to ingo-library (vimscript #4433) version 1.028! ***","package":"EnhancedJumps-3.10.vmb.gz","4":"EnhancedJumps-3.10.vmb.gz","src_id":"26259","5":"26259","creation_date":"1541362244","6":"1541362244"},{"0":"2695","vim_version":"7.0","1":"7.0","script_version":"3.03","2":"3.03","version_comment":"- After a jump to another file, also re-query the jumps, because the jumplist got updated with the text for the jumps, whereas it previously only contained the buffer name. Thanks to Daniel Hahler for sending a patch.\r\n- Especially in small terminals, jump messages may not fit and cause a hit-enter prompt. Truncate messages in s:Echo(). Local jump message only considers the header, but not the file jump messages. If its one, and cmdheight is 1, add its width to the number of reserved columns, as we append the following location. Thanks to Daniel Hahler for the patch.\r\n- The warning message before a remote jump isn't truncated to fit.\r\n- Minor: Use ingo#compat#abs().","3":"- After a jump to another file, also re-query the jumps, because the jumplist got updated with the text for the jumps, whereas it previously only contained the buffer name. Thanks to Daniel Hahler for sending a patch.\r\n- Especially in small terminals, jump messages may not fit and cause a hit-enter prompt. Truncate messages in s:Echo(). Local jump message only considers the header, but not the file jump messages. If its one, and cmdheight is 1, add its width to the number of reserved columns, as we append the following location. Thanks to Daniel Hahler for the patch.\r\n- The warning message before a remote jump isn't truncated to fit.\r\n- Minor: Use ingo#compat#abs().","package":"EnhancedJumps-3.03.vmb.gz","4":"EnhancedJumps-3.03.vmb.gz","src_id":"24746","5":"24746","creation_date":"1479472518","6":"1479472518"},{"0":"2695","vim_version":"7.0","1":"7.0","script_version":"3.02","2":"3.02","version_comment":"- Add g:EnhancedJumps_CaptureJumpMessages configuration to turn off the capturing of the messages during the jump, as the used :redir may cause errors with another, concurrent capture. This was first reported by by Alexey Radkov on 06-Jul-2012 (conflict with the Recover.vim plugin that was fixed in that plugin), now again by Maxim Gonchar (conflict with Vimfiler plugin).\r\n- Use ingo#msg#WarningMsg().\r\n- Use ingo#record#Position(). *** You need to update to ingo-library (vimscript #4433) version 1.020! ***","3":"- Add g:EnhancedJumps_CaptureJumpMessages configuration to turn off the capturing of the messages during the jump, as the used :redir may cause errors with another, concurrent capture. This was first reported by by Alexey Radkov on 06-Jul-2012 (conflict with the Recover.vim plugin that was fixed in that plugin), now again by Maxim Gonchar (conflict with Vimfiler plugin).\r\n- Use ingo#msg#WarningMsg().\r\n- Use ingo#record#Position(). *** You need to update to ingo-library (vimscript #4433) version 1.020! ***","package":"EnhancedJumps-3.02.vmb.gz","4":"EnhancedJumps-3.02.vmb.gz","src_id":"22466","5":"22466","creation_date":"1411997937","6":"1411997937"},{"0":"2695","vim_version":"7.0","1":"7.0","script_version":"3.01","2":"3.01","version_comment":"- Handle it when the :changes command sometimes outputs just the header without a following \">\" marker by catching the plugin exception in EnhancedJumps#Changes#GetJumps() and returning an empty List instead. This will cause the callers to fall back on the default g; \/ g, commands, which will then report the \"E664: changelist is empty\" error.\r\n- Add dependency to ingo-library (vimscript #4433). *** You need to separately install ingo-library (vimscript #4433) version 1.008 (or higher)! ***","3":"- Handle it when the :changes command sometimes outputs just the header without a following \">\" marker by catching the plugin exception in EnhancedJumps#Changes#GetJumps() and returning an empty List instead. This will cause the callers to fall back on the default g; \/ g, commands, which will then report the \"E664: changelist is empty\" error.\r\n- Add dependency to ingo-library (vimscript #4433). *** You need to separately install ingo-library (vimscript #4433) version 1.008 (or higher)! ***","package":"EnhancedJumps-3.01.vmb.gz","4":"EnhancedJumps-3.01.vmb.gz","src_id":"21062","5":"21062","creation_date":"1384857945","6":"1384857945"},{"0":"2695","vim_version":"7.0","1":"7.0","script_version":"3.00","2":"3.00","version_comment":"Implement enhanced change list navigation commands g; \/ g, that skip jumps to previous \/ later edit locations that lie within the currently visible range.","3":"Implement enhanced change list navigation commands g; \/ g, that skip jumps to previous \/ later edit locations that lie within the currently visible range.","package":"EnhancedJumps.vba.gz","4":"EnhancedJumps.vba.gz","src_id":"17421","5":"17421","creation_date":"1328884538","6":"1328884538"},{"0":"2695","vim_version":"7.0","1":"7.0","script_version":"2.00","2":"2.00","version_comment":"- Implement \"local jumps\" and \"remote jumps\" special mappings. \r\n- Restructure internal jump list representation to get rid of index arithmetic, duplicated checks for current index in, and enhance filter performance. \r\n- Split off functions to separate autoload script to help speed up Vim startup. ","3":"- Implement \"local jumps\" and \"remote jumps\" special mappings. \r\n- Restructure internal jump list representation to get rid of index arithmetic, duplicated checks for current index in, and enhance filter performance. \r\n- Split off functions to separate autoload script to help speed up Vim startup. ","package":"EnhancedJumps.vba.gz","4":"EnhancedJumps.vba.gz","src_id":"17420","5":"17420","creation_date":"1328884408","6":"1328884408"},{"0":"2695","vim_version":"7.0","1":"7.0","script_version":"1.13","2":"1.13","version_comment":"BUG: Jump opened fold at current position when \"No newer\/older jump position\"\r\nerror occurred. ","3":"BUG: Jump opened fold at current position when \"No newer\/older jump position\"\r\nerror occurred. ","package":"EnhancedJumps.vba.gz","4":"EnhancedJumps.vba.gz","src_id":"13425","5":"13425","creation_date":"1280385844","6":"1280385844"},{"0":"2695","vim_version":"7.0","1":"7.0","script_version":"1.12","2":"1.12","version_comment":"BF: Trailing space after the command to open the folds accidentally moved cursor one position to the right of the jump target. ","3":"BF: Trailing space after the command to open the folds accidentally moved cursor one position to the right of the jump target. ","package":"EnhancedJumps.vba.gz","4":"EnhancedJumps.vba.gz","src_id":"11025","5":"11025","creation_date":"1247860401","6":"1247860401"},{"0":"2695","vim_version":"7.0","1":"7.0","script_version":"1.11","2":"1.11","version_comment":"BF: A '^\\)' in the jump text caused \"E55: Unmatched \\)\"","3":"BF: A '^\\)' in the jump text caused \"E55: Unmatched \\)\"","package":"EnhancedJumps.vba.gz","4":"EnhancedJumps.vba.gz","src_id":"11009","5":"11009","creation_date":"1247561530","6":"1247561530"},{"0":"2695","vim_version":"7.0","1":"7.0","script_version":"1.10","2":"1.10","version_comment":"- ENH: To overcome the next buffer warning, a previously given [count] need not be specified again. A jump command with a different [count] than last time now is treated as a separate jump command and thus doesn't overcome the next buffer warning. \r\n- BF: Folds at the jump target must be explicitly opened. ","3":"- ENH: To overcome the next buffer warning, a previously given [count] need not be specified again. A jump command with a different [count] than last time now is treated as a separate jump command and thus doesn't overcome the next buffer warning. \r\n- BF: Folds at the jump target must be explicitly opened. ","package":"EnhancedJumps.vba.gz","4":"EnhancedJumps.vba.gz","src_id":"10955","5":"10955","creation_date":"1246871987","6":"1246871987"},{"0":"2695","vim_version":"7.0","1":"7.0","script_version":"1.00","2":"1.00","version_comment":"Initial upload","3":"Initial upload","package":"EnhancedJumps.vba.gz","4":"EnhancedJumps.vba.gz","src_id":"10920","5":"10920","creation_date":"1246482333","6":"1246482333"}]},"2694":{"script_id":"2694","0":"2694","script_name":"MediaWiki folding and syntax highlight","1":"MediaWiki folding and syntax highlight","script_type":"syntax","2":"syntax","summary":"folding support for MediaWiki-style syntax","3":"folding support for MediaWiki-style syntax","description":"This syntax file adds not only syntax highlight, but also folding for MediaWiki-style wikitext. (This is the syntax that Wikipedia uses, among many other sites.) I've been using it for 3 years now, and while it isn't bug-free, it's reasonably mature.\r\n\r\nNote: if folding seems broken (this does happen with long and complicated files), do \":syntax sync fromstart\". Also, you may find the \"It's All Text!\" Firefox-extension useful: https:\/\/addons.mozilla.org\/en-US\/firefox\/addon\/4125","4":"This syntax file adds not only syntax highlight, but also folding for MediaWiki-style wikitext. (This is the syntax that Wikipedia uses, among many other sites.) I've been using it for 3 years now, and while it isn't bug-free, it's reasonably mature.\r\n\r\nNote: if folding seems broken (this does happen with long and complicated files), do \":syntax sync fromstart\". Also, you may find the \"It's All Text!\" Firefox-extension useful: https:\/\/addons.mozilla.org\/en-US\/firefox\/addon\/4125","install_details":"","5":"","first_name":"Attila","6":"Attila","last_name":"Nagy","7":"Nagy","releases":[{"0":"2694","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"wp.vim","4":"wp.vim","src_id":"10905","5":"10905","creation_date":"1246094417","6":"1246094417"}]},"2693":{"script_id":"2693","0":"2693","script_name":"ats-lang-vim","1":"ats-lang-vim","script_type":"syntax","2":"syntax","summary":"syntax highlighting for ATS","3":"syntax highlighting for ATS","description":"A (rather incomplete) syntax highlighting for ATS (see http:\/\/www.ats-lang.org)\r\n\r\nFuture improvements are planned.","4":"A (rather incomplete) syntax highlighting for ATS (see http:\/\/www.ats-lang.org)\r\n\r\nFuture improvements are planned.","install_details":"Copy this script into ~\/.vim\/syntax, then add the lines below to your ~\/.vimrc:\r\n\r\nau BufRead,BufNewFile *.dats set filetype=ats\r\nau BufRead,BufNewFile *.sats set filetype=ats\r\nau! Syntax ats source ats.vim\r\n\r\nEnjoy! :)","5":"Copy this script into ~\/.vim\/syntax, then add the lines below to your ~\/.vimrc:\r\n\r\nau BufRead,BufNewFile *.dats set filetype=ats\r\nau BufRead,BufNewFile *.sats set filetype=ats\r\nau! Syntax ats source ats.vim\r\n\r\nEnjoy! :)","first_name":"Artyom","6":"Artyom","last_name":"Shalkhakov","7":"Shalkhakov","releases":[{"0":"2693","vim_version":"7.2","1":"7.2","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"ats.vim","4":"ats.vim","src_id":"10904","5":"10904","creation_date":"1246085855","6":"1246085855"}]},"2692":{"script_id":"2692","0":"2692","script_name":"operator-user","1":"operator-user","script_type":"utility","2":"utility","summary":"Define your own operator easily","3":"Define your own operator easily","description":"*operator-user* is a Vim library plugin to provide an easy way to define your\nown |operator|.  Though there are several pitfalls to define operators, you\ndon't have to take care of them with |operator#user#define()| which are\nprovided by this library plugin.\n\nFor example, the following code defines operator \"_\" to adjust the height of\nthe current window to the same as the target range:\n\n\tmap _  <Plug>(operator-adjust)\n\tcall operator#user#define('adjust', 'Op_adjust_window_height')\n\tfunction! Op_adjust_window_height(motion_wiseness)\n\t  execute (line(\"']\") - line(\"'[\") + 1) 'wincmd' '_'\n\t  normal! `[zt\n\tendfunction\n\nYou can use this operator as follows:\n\n\t10__\tAdjust to 10 lines and show the current line at the top.\n\t_ip\tAdjust to the same height of the paragraph under the cursor.\n\nThis operator is useful to adjust the visible content in the current window.\n\nSee also |operator-user-examples| for more examples and explanations.\n\n\nRequirements:\n- Vim 7.2 or later\n\nOptionals:\n- |grex| (vimscript#2773)\n- |operator-replace| (vimscript#2782)\n- |wwwsearch| (vimscript#2785)\n\nLatest version:\nhttp:\/\/github.com\/kana\/config\/commits\/vim-operator-user\n\nDocument in HTML format:\nhttp:\/\/kana.github.com\/config\/vim\/operator-user.html","4":"*operator-user* is a Vim library plugin to provide an easy way to define your\nown |operator|.  Though there are several pitfalls to define operators, you\ndon't have to take care of them with |operator#user#define()| which are\nprovided by this library plugin.\n\nFor example, the following code defines operator \"_\" to adjust the height of\nthe current window to the same as the target range:\n\n\tmap _  <Plug>(operator-adjust)\n\tcall operator#user#define('adjust', 'Op_adjust_window_height')\n\tfunction! Op_adjust_window_height(motion_wiseness)\n\t  execute (line(\"']\") - line(\"'[\") + 1) 'wincmd' '_'\n\t  normal! `[zt\n\tendfunction\n\nYou can use this operator as follows:\n\n\t10__\tAdjust to 10 lines and show the current line at the top.\n\t_ip\tAdjust to the same height of the paragraph under the cursor.\n\nThis operator is useful to adjust the visible content in the current window.\n\nSee also |operator-user-examples| for more examples and explanations.\n\n\nRequirements:\n- Vim 7.2 or later\n\nOptionals:\n- |grex| (vimscript#2773)\n- |operator-replace| (vimscript#2782)\n- |wwwsearch| (vimscript#2785)\n\nLatest version:\nhttp:\/\/github.com\/kana\/config\/commits\/vim-operator-user\n\nDocument in HTML format:\nhttp:\/\/kana.github.com\/config\/vim\/operator-user.html","install_details":"...","5":"...","first_name":"Kana","6":"Kana","last_name":"Natsuno","7":"Natsuno","releases":[{"0":"2692","vim_version":"7.0","1":"7.0","script_version":"0.0.7","2":"0.0.7","version_comment":"- |operator#user#define_ex_command|: Support {ex-command} including \"'\".  For example: s\/\"\/'\/g\n- Refine old-style test scripts.","3":"- |operator#user#define_ex_command|: Support {ex-command} including \"'\".  For example: s\/\"\/'\/g\n- Refine old-style test scripts.","package":"vim-operator-user-0.0.7.zip","4":"vim-operator-user-0.0.7.zip","src_id":"18077","5":"18077","creation_date":"1338614404","6":"1338614404"},{"0":"2692","vim_version":"7.0","1":"7.0","script_version":"0.0.5","2":"0.0.5","version_comment":"- Add |operator#user#visual_command_from_wise_name()|.\n- Revise a bit of the document.","3":"- Add |operator#user#visual_command_from_wise_name()|.\n- Revise a bit of the document.","package":"vim-operator-user-0.0.5.zip","4":"vim-operator-user-0.0.5.zip","src_id":"11340","5":"11340","creation_date":"1252364010","6":"1252364010"},{"0":"2692","vim_version":"7.0","1":"7.0","script_version":"0.0.4","2":"0.0.4","version_comment":"- Fix a bug that it rarely fails to select the same text as a given {motion} in Normal mode.  It is caused by a bug in Vim; |v:count1| may be 0 in some cases.\n- Fix a bug that register designation (\"a, \"b, etc) doesn't work for user defiend operators.","3":"- Fix a bug that it rarely fails to select the same text as a given {motion} in Normal mode.  It is caused by a bug in Vim; |v:count1| may be 0 in some cases.\n- Fix a bug that register designation (\"a, \"b, etc) doesn't work for user defiend operators.","package":"vim-operator-user-0.0.4.zip","4":"vim-operator-user-0.0.4.zip","src_id":"11338","5":"11338","creation_date":"1252333316","6":"1252333316"},{"0":"2692","vim_version":"7.0","1":"7.0","script_version":"0.0.3","2":"0.0.3","version_comment":"Incompatible change:\n- |operator#user#define()|, |operator#user#define_ex_command()|: Change the meaning of the first argument:\n\n  Old versions:\n\t  The argument is {lhs} to execute the operator to be defined.\n\n  New version:\n\t  The argument is {name} of the operator to be defined.\n\t  {lhs} to execute the operator is \"<Plug>(operator-{name})\".\n\n  See also |operator-user-bugs-C| for the details.","3":"Incompatible change:\n- |operator#user#define()|, |operator#user#define_ex_command()|: Change the meaning of the first argument:\n\n  Old versions:\n\t  The argument is {lhs} to execute the operator to be defined.\n\n  New version:\n\t  The argument is {name} of the operator to be defined.\n\t  {lhs} to execute the operator is \"<Plug>(operator-{name})\".\n\n  See also |operator-user-bugs-C| for the details.","package":"vim-operator-user-0.0.3.zip","4":"vim-operator-user-0.0.3.zip","src_id":"11320","5":"11320","creation_date":"1252068233","6":"1252068233"},{"0":"2692","vim_version":"7.0","1":"7.0","script_version":"0.0.2","2":"0.0.2","version_comment":"- Add |operator#user#define_ex_command()|.\n- Add a note on a bug.  See |operator-user-bugs-B| for the details.\n- Remove :DefineOperator.  It's useless as a part of this library.","3":"- Add |operator#user#define_ex_command()|.\n- Add a note on a bug.  See |operator-user-bugs-B| for the details.\n- Remove :DefineOperator.  It's useless as a part of this library.","package":"vim-operator-user-0.0.2.zip","4":"vim-operator-user-0.0.2.zip","src_id":"11312","5":"11312","creation_date":"1252020858","6":"1252020858"},{"0":"2692","vim_version":"7.0","1":"7.0","script_version":"0.0.1","2":"0.0.1","version_comment":"- Rename as \"operator-user\".  The old name \"myoperator\" is not good for further works.","3":"- Rename as \"operator-user\".  The old name \"myoperator\" is not good for further works.","package":"vim-operator-user-0.0.1.zip","4":"vim-operator-user-0.0.1.zip","src_id":"11029","5":"11029","creation_date":"1247911004","6":"1247911004"},{"0":"2692","vim_version":"7.0","1":"7.0","script_version":"0.0.0","2":"0.0.0","version_comment":"Initial upload","3":"Initial upload","package":"vim-myoperator-0.0.0.zip","4":"vim-myoperator-0.0.0.zip","src_id":"10902","5":"10902","creation_date":"1246052816","6":"1246052816"}]},"2691":{"script_id":"2691","0":"2691","script_name":"fbc.vim","1":"fbc.vim","script_type":"utility","2":"utility","summary":"Compiler plugin for FreeBASIC","3":"Compiler plugin for FreeBASIC","description":"fbc.vim\r\nVim compiler plugin for FreeBASIC.\r\n\r\nCompiles the buffer with FreeBASIC, and shows the compilation results in quickfix window.\r\n\r\nHome page: https:\/\/github.com\/caglartoklu\/fbc.vim","4":"fbc.vim\r\nVim compiler plugin for FreeBASIC.\r\n\r\nCompiles the buffer with FreeBASIC, and shows the compilation results in quickfix window.\r\n\r\nHome page: https:\/\/github.com\/caglartoklu\/fbc.vim","install_details":"For Vundle users:\r\n    Bundle 'caglartoklu\/fbc.vim'\r\n\r\nFor Pathogen users:\r\n    cd ~\/.vim\/bundle\r\n    git clone git:\/\/github.com\/caglartoklu\/fbc.vim\r\n\r\nFor all other users, simply drop the fbc.vim file to your compiler directory.\r\n\r\nIn Vim, the compilers are not automatically set unlike file type plugins. To achieve that, type the following into your .vrimrc file:\r\n    autocmd BufNewFile,BufRead *.bas compiler fbc\r\n\r\nTo do it only for the current buffer, you can set the following command, which will have a temporary effect:\r\n    compiler fbc","5":"For Vundle users:\r\n    Bundle 'caglartoklu\/fbc.vim'\r\n\r\nFor Pathogen users:\r\n    cd ~\/.vim\/bundle\r\n    git clone git:\/\/github.com\/caglartoklu\/fbc.vim\r\n\r\nFor all other users, simply drop the fbc.vim file to your compiler directory.\r\n\r\nIn Vim, the compilers are not automatically set unlike file type plugins. To achieve that, type the following into your .vrimrc file:\r\n    autocmd BufNewFile,BufRead *.bas compiler fbc\r\n\r\nTo do it only for the current buffer, you can set the following command, which will have a temporary effect:\r\n    compiler fbc","first_name":"Caglar","6":"Caglar","last_name":"Toklu","7":"Toklu","releases":[{"0":"2691","vim_version":"7.0","1":"7.0","script_version":"2013-09-27","2":"2013-09-27","version_comment":"Synchronization version numbers, documentation and content with Github.","3":"Synchronization version numbers, documentation and content with Github.","package":"fbc.vim","4":"fbc.vim","src_id":"20858","5":"20858","creation_date":"1380295538","6":"1380295538"},{"0":"2691","vim_version":"6.0","1":"6.0","script_version":"0.0.4","2":"0.0.4","version_comment":"Initial upload","3":"Initial upload","package":"fbc.vim","4":"fbc.vim","src_id":"10901","5":"10901","creation_date":"1246041809","6":"1246041809"}]},"2690":{"script_id":"2690","0":"2690","script_name":"kaltex.vim","1":"kaltex.vim","script_type":"color scheme","2":"color scheme","summary":"A colder colorscheme...","3":"A colder colorscheme...","description":"Same as the kalt.vim colorscheme, except that this one\r\nuses bold, italics and underlined font styles for syntax\r\nhighlighting.","4":"Same as the kalt.vim colorscheme, except that this one\r\nuses bold, italics and underlined font styles for syntax\r\nhighlighting.","install_details":"Just put it into your ~\/.vim\/colors\r\n\r\nand try it out inside GVIM\/VIM with the command:\r\n\r\n:color kaltex","5":"Just put it into your ~\/.vim\/colors\r\n\r\nand try it out inside GVIM\/VIM with the command:\r\n\r\n:color kaltex","first_name":"drachen","6":"drachen","last_name":"kiraa","7":"kiraa","releases":[{"0":"2690","vim_version":"6.0","1":"6.0","script_version":"1.1","2":"1.1","version_comment":"FIX: Cursor disappeared when moving it in a Comment. This ONLY\r\n  happened on one terminal (gnome-terminal). Now the Comment ctermfg\r\n  color is DarkGreen for all 8 color Xterms. But you'll still get the\r\n  original color (DarkGray) if your terminal supports more colors\r\n  (when you force it by setting 't_Co' to 16 or more).\r\nChanged 'Cursor', 'CursorLine', 'CursorColumn' colors to\r\n  DarkBlue instead of the ugly Green.\r\nChanged SpellRare guifg color from Magenta to DarkMagenta.\r\nChanged IncSearch guifg color from LighMagenta to Green.\r\nChanged PreCondit guifg color to a darker yellow color.\r\nSet ctermfg and guifg options of 'Search' and 'IncSearch' to the\r\n  background color.\r\nMade 'Character' guifg color more brighter.\r\nChanged 'Special' guifg color from Blue to a nice Red color.\r\nChanged 'PmenuSel' and 'Todo' gui option to bold.","3":"FIX: Cursor disappeared when moving it in a Comment. This ONLY\r\n  happened on one terminal (gnome-terminal). Now the Comment ctermfg\r\n  color is DarkGreen for all 8 color Xterms. But you'll still get the\r\n  original color (DarkGray) if your terminal supports more colors\r\n  (when you force it by setting 't_Co' to 16 or more).\r\nChanged 'Cursor', 'CursorLine', 'CursorColumn' colors to\r\n  DarkBlue instead of the ugly Green.\r\nChanged SpellRare guifg color from Magenta to DarkMagenta.\r\nChanged IncSearch guifg color from LighMagenta to Green.\r\nChanged PreCondit guifg color to a darker yellow color.\r\nSet ctermfg and guifg options of 'Search' and 'IncSearch' to the\r\n  background color.\r\nMade 'Character' guifg color more brighter.\r\nChanged 'Special' guifg color from Blue to a nice Red color.\r\nChanged 'PmenuSel' and 'Todo' gui option to bold.","package":"kaltex.vim","4":"kaltex.vim","src_id":"10922","5":"10922","creation_date":"1246489222","6":"1246489222"},{"0":"2690","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"kaltex.vim","4":"kaltex.vim","src_id":"10897","5":"10897","creation_date":"1245969743","6":"1245969743"}]},"2689":{"script_id":"2689","0":"2689","script_name":"kalt.vim","1":"kalt.vim","script_type":"color scheme","2":"color scheme","summary":"A cold colorscheme.","3":"A cold colorscheme.","description":"A cold colorscheme for GVIM\/VIM without bold, italic nor\r\nunderline font styles (except for spell checking and some \r\nGUI elements). On VIM it uses a black background, because \r\nit was easier to do and *seems* to be the only way to make \r\na colorscheme look nice on any darn terminal.\r\nThis colorscheme _should_ look nice everywhere.","4":"A cold colorscheme for GVIM\/VIM without bold, italic nor\r\nunderline font styles (except for spell checking and some \r\nGUI elements). On VIM it uses a black background, because \r\nit was easier to do and *seems* to be the only way to make \r\na colorscheme look nice on any darn terminal.\r\nThis colorscheme _should_ look nice everywhere.","install_details":"Just put it into your  ~\/.vim\/colors","5":"Just put it into your  ~\/.vim\/colors","first_name":"drachen","6":"drachen","last_name":"kiraa","7":"kiraa","releases":[{"0":"2689","vim_version":"6.0","1":"6.0","script_version":"1.1","2":"1.1","version_comment":"FIX: Cursor disappeared when moving it in a Comment. This ONLY\r\n  happened on one terminal (gnome-terminal). Now the Comment ctermfg\r\n  color is DarkGreen for all 8 color Xterms. But you'll still get the\r\n  original color (DarkGray) if your terminal supports more colors\r\n  (when you force it by setting 't_Co' to 16 or more).\r\nChanged 'Cursor', 'CursorLine', 'CursorColumn' colors to\r\n  DarkBlue instead of the ugly Green.\r\nChanged SpellRare guifg color from Magenta to DarkMagenta.\r\nChanged IncSearch guifg color from LighMagenta to Green.\r\nChanged PreCondit guifg color to a darker yellow color.\r\nSet ctermfg and guifg options of 'Search' and 'IncSearch' to the\r\n  background color.\r\nMade 'Character' guifg color more brighter.\r\nChanged 'Special' guifg color from Blue to a nice Red color.\r\n","3":"FIX: Cursor disappeared when moving it in a Comment. This ONLY\r\n  happened on one terminal (gnome-terminal). Now the Comment ctermfg\r\n  color is DarkGreen for all 8 color Xterms. But you'll still get the\r\n  original color (DarkGray) if your terminal supports more colors\r\n  (when you force it by setting 't_Co' to 16 or more).\r\nChanged 'Cursor', 'CursorLine', 'CursorColumn' colors to\r\n  DarkBlue instead of the ugly Green.\r\nChanged SpellRare guifg color from Magenta to DarkMagenta.\r\nChanged IncSearch guifg color from LighMagenta to Green.\r\nChanged PreCondit guifg color to a darker yellow color.\r\nSet ctermfg and guifg options of 'Search' and 'IncSearch' to the\r\n  background color.\r\nMade 'Character' guifg color more brighter.\r\nChanged 'Special' guifg color from Blue to a nice Red color.\r\n","package":"kalt.vim","4":"kalt.vim","src_id":"10921","5":"10921","creation_date":"1246489114","6":"1246489114"},{"0":"2689","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"kalt.vim","4":"kalt.vim","src_id":"10896","5":"10896","creation_date":"1245969528","6":"1245969528"}]},"2688":{"script_id":"2688","0":"2688","script_name":"dual.vim","1":"dual.vim","script_type":"color scheme","2":"color scheme","summary":"The Dual colorscheme that you've longing for.","3":"The Dual colorscheme that you've longing for.","description":"On VIM, it uses dark colors.\r\nOn GVIM, it uses bright colors without bold, italic nor \r\nunderline font styles (except for spell checking and \r\nsome GUI elements).\r\nOnly standard (for all languages) highlight-groups are set.\r\nThis colorscheme _should_ look nice everywhere.","4":"On VIM, it uses dark colors.\r\nOn GVIM, it uses bright colors without bold, italic nor \r\nunderline font styles (except for spell checking and \r\nsome GUI elements).\r\nOnly standard (for all languages) highlight-groups are set.\r\nThis colorscheme _should_ look nice everywhere.","install_details":"Just put it into your ~\/.vim\/colors","5":"Just put it into your ~\/.vim\/colors","first_name":"drachen","6":"drachen","last_name":"kiraa","7":"kiraa","releases":[{"0":"2688","vim_version":"6.0","1":"6.0","script_version":"1.1","2":"1.1","version_comment":"A LOT of changes, too much to mention them here\r\n(look in the File's header comment to see all the changes.)\r\nMainly, improved the entire look of the colorscheme and\r\nmade VIM and  GVIM use similar colors.\r\n\r\nIn GVIM >= 7.0 give it a try setting:\r\n    :set number cursorline","3":"A LOT of changes, too much to mention them here\r\n(look in the File's header comment to see all the changes.)\r\nMainly, improved the entire look of the colorscheme and\r\nmade VIM and  GVIM use similar colors.\r\n\r\nIn GVIM >= 7.0 give it a try setting:\r\n    :set number cursorline","package":"dual.vim","4":"dual.vim","src_id":"10923","5":"10923","creation_date":"1246489272","6":"1246489272"},{"0":"2688","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"dual.vim","4":"dual.vim","src_id":"10895","5":"10895","creation_date":"1245969320","6":"1245969320"}]},"2687":{"script_id":"2687","0":"2687","script_name":"iabassist","1":"iabassist","script_type":"utility","2":"utility","summary":"some helpful commands for defining abbreviations which expand only when wanted","3":"some helpful commands for defining abbreviations which expand only when wanted","description":"There are a ton of existing abbreviation packages, but none were quite right.  This one provides some unique features:\r\n1. Doesn't expand the abbreviation in specified areas\r\n2. Doesn't expand the abbreviation unless a tab was pressed\r\n3. Placeholder will not compile in most languages\r\n4. Includes mappings to quickly select the next placeholder, accept defaults, or delete current placeholder.\r\n\r\nUsage:\r\n    Exports:\r\n        Eatchar() - removes any trailing spaces from abbreviations\r\n        ExpandIfSafe(from, to) - expands a:from to a:to if not in a specified block (strings, comments, character, doxygen, bibbrace currently)\r\n        Iab(ab, full) - define an abbreviation from a:ab to a:full which expands if safe\r\n        IabSelectNext - Finds the next placeholder and selects it\r\n        IabSelectDefault - Selects the default option\r\n    Maps:\r\n        ,, - Select the next placeholder\r\n        ,' - Select the default for the current placeholder\r\n        ,. - Delete the current placeholder\r\n    Example:\r\n        Iab('for', 'for(\u00c2\u00ab$1:unsigned i = 0\u00c2\u00bb; \u00c2\u00ab$2:i < \u00c2\u00ab$3\u00c2\u00bb\u00c2\u00bb; \u00c2\u00ab$4:++i\u00c2\u00bb)<CR>{<CR>\u00c2\u00ab$5\u00c2\u00bb<CR>}')\r\n        will define an abbreviation for for.  Now typing for<TAB> will expand to:\r\n        for(\u00c2\u00ab$1:unsigned i = 0\u00c2\u00bb; \u00c2\u00ab$2:i < \u00c2\u00ab$3\u00c2\u00bb\u00c2\u00bb; \u00c2\u00ab$4:++i\u00c2\u00bb)\r\n        {\r\n            \u00c2\u00ab$5\u00c2\u00bb\r\n        }\r\n        with \u00c2\u00ab$1:unsigned i = 0\u00c2\u00bb being selected.  Now typing ,' will change it to unsigned i = 0; and select the $2 branch (Note the numbers are not traversed in order, but instead are merely for marking placeholders.  In a future version this may change).  As it is in select mode typing any character will replace the placeholder.  If a placeholder is unwanted one can press ,., and to traverse use ,,.\r\n\r\n        Finally, note that abbreviations only expand if the last key was a tab, this ensures typing for<SPACE> will not expand.\r\n\r\nCustomization:\r\n    At the moment the only customization is via source modification.  The most likely lines to be modified are: 1) 89-96 to change the mappings, and 2) 44 to change what are the unsafe syntax and what character is used for expansion (currently this must be a non-control character).\r\n\r\nAlternatives:\r\n    snippetsEmu - vimscript #1318\r\n    snipMate - vimscript #2540\r\n    code-snippet - vimscript #2086\r\n    The first two do much more than this, and I had issues with both, e.g. they seemed to have troubles when inserting a snippet inside the middle of a snippet.  The latter is more like this, but differs in its behavior, namely they use the (very neat) trick of mapping a special key (<S-CR>) to execute the expansion, instead this script uses the (also hopefully neat) trick of checking the last character entered and only expanding when the last character is a tab.","4":"There are a ton of existing abbreviation packages, but none were quite right.  This one provides some unique features:\r\n1. Doesn't expand the abbreviation in specified areas\r\n2. Doesn't expand the abbreviation unless a tab was pressed\r\n3. Placeholder will not compile in most languages\r\n4. Includes mappings to quickly select the next placeholder, accept defaults, or delete current placeholder.\r\n\r\nUsage:\r\n    Exports:\r\n        Eatchar() - removes any trailing spaces from abbreviations\r\n        ExpandIfSafe(from, to) - expands a:from to a:to if not in a specified block (strings, comments, character, doxygen, bibbrace currently)\r\n        Iab(ab, full) - define an abbreviation from a:ab to a:full which expands if safe\r\n        IabSelectNext - Finds the next placeholder and selects it\r\n        IabSelectDefault - Selects the default option\r\n    Maps:\r\n        ,, - Select the next placeholder\r\n        ,' - Select the default for the current placeholder\r\n        ,. - Delete the current placeholder\r\n    Example:\r\n        Iab('for', 'for(\u00c2\u00ab$1:unsigned i = 0\u00c2\u00bb; \u00c2\u00ab$2:i < \u00c2\u00ab$3\u00c2\u00bb\u00c2\u00bb; \u00c2\u00ab$4:++i\u00c2\u00bb)<CR>{<CR>\u00c2\u00ab$5\u00c2\u00bb<CR>}')\r\n        will define an abbreviation for for.  Now typing for<TAB> will expand to:\r\n        for(\u00c2\u00ab$1:unsigned i = 0\u00c2\u00bb; \u00c2\u00ab$2:i < \u00c2\u00ab$3\u00c2\u00bb\u00c2\u00bb; \u00c2\u00ab$4:++i\u00c2\u00bb)\r\n        {\r\n            \u00c2\u00ab$5\u00c2\u00bb\r\n        }\r\n        with \u00c2\u00ab$1:unsigned i = 0\u00c2\u00bb being selected.  Now typing ,' will change it to unsigned i = 0; and select the $2 branch (Note the numbers are not traversed in order, but instead are merely for marking placeholders.  In a future version this may change).  As it is in select mode typing any character will replace the placeholder.  If a placeholder is unwanted one can press ,., and to traverse use ,,.\r\n\r\n        Finally, note that abbreviations only expand if the last key was a tab, this ensures typing for<SPACE> will not expand.\r\n\r\nCustomization:\r\n    At the moment the only customization is via source modification.  The most likely lines to be modified are: 1) 89-96 to change the mappings, and 2) 44 to change what are the unsafe syntax and what character is used for expansion (currently this must be a non-control character).\r\n\r\nAlternatives:\r\n    snippetsEmu - vimscript #1318\r\n    snipMate - vimscript #2540\r\n    code-snippet - vimscript #2086\r\n    The first two do much more than this, and I had issues with both, e.g. they seemed to have troubles when inserting a snippet inside the middle of a snippet.  The latter is more like this, but differs in its behavior, namely they use the (very neat) trick of mapping a special key (<S-CR>) to execute the expansion, instead this script uses the (also hopefully neat) trick of checking the last character entered and only expanding when the last character is a tab.","install_details":"Copy to <.vim>\/plugin\/","5":"Copy to <.vim>\/plugin\/","first_name":"Matt","6":"Matt","last_name":"Spear","7":"Spear","releases":[{"0":"2687","vim_version":"7.0","1":"7.0","script_version":"0.02","2":"0.02","version_comment":"Fixed some small issues: 1) selecting default no longer overwrites the default register, 2) Some code simplification, 3) changed the mappings to ,X instead of ;X.","3":"Fixed some small issues: 1) selecting default no longer overwrites the default register, 2) Some code simplification, 3) changed the mappings to ,X instead of ;X.","package":"iabassist.vim","4":"iabassist.vim","src_id":"13640","5":"13640","creation_date":"1282445123","6":"1282445123"},{"0":"2687","vim_version":"7.0","1":"7.0","script_version":"0.01","2":"0.01","version_comment":"Initial upload","3":"Initial upload","package":"iabassist.vim","4":"iabassist.vim","src_id":"10888","5":"10888","creation_date":"1245708310","6":"1245708310"}]},"2686":{"script_id":"2686","0":"2686","script_name":"cuteTodoList","1":"cuteTodoList","script_type":"utility","2":"utility","summary":"Manage to-do lists within vim","3":"Manage to-do lists within vim","description":"Manage automatically todo lists with priority and icons.\r\n\r\nGitHub : https:\/\/github.com\/Twinside\/vim-cuteTodoList\r\n\r\nscreenshot : http:\/\/img198.imageshack.us\/gal.php?g=cutetodoclinux.png\r\n\r\nTested on :\r\n- Windows XP\/Vista\/7\r\n- Ubuntu 9.04 (GVim && Vim)","4":"Manage automatically todo lists with priority and icons.\r\n\r\nGitHub : https:\/\/github.com\/Twinside\/vim-cuteTodoList\r\n\r\nscreenshot : http:\/\/img198.imageshack.us\/gal.php?g=cutetodoclinux.png\r\n\r\nTested on :\r\n- Windows XP\/Vista\/7\r\n- Ubuntu 9.04 (GVim && Vim)","install_details":"drop the files in your ~\/.vim or ~\/vimfiles\r\n(can work in $VIM and $VIMRUNTIME folder, but favor dropping it in your profile dir)\r\nand use :TodoOpen to use","5":"drop the files in your ~\/.vim or ~\/vimfiles\r\n(can work in $VIM and $VIMRUNTIME folder, but favor dropping it in your profile dir)\r\nand use :TodoOpen to use","first_name":"Vincent","6":"Vincent","last_name":"B","7":"B","releases":[{"0":"2686","vim_version":"7.0","1":"7.0","script_version":"1.1.1","2":"1.1.1","version_comment":"now use globpath( &rtp... to find icons","3":"now use globpath( &rtp... to find icons","package":"cuteTodoList.tar.gz","4":"cuteTodoList.tar.gz","src_id":"11004","5":"11004","creation_date":"1247495533","6":"1247495533"}]},"2685":{"script_id":"2685","0":"2685","script_name":"z\/OS Enterprise Compiler PLI","1":"z\/OS Enterprise Compiler PLI","script_type":"syntax","2":"syntax","summary":"z\/OS Enterprise Compiler PLI Language Syntax File","3":"z\/OS Enterprise Compiler PLI Language Syntax File","description":"Updated for z\/OS PLI Enterprise Compiler.\r\nBased on Ing. Michael Fitz's version: vimscript #1013\r\n\r\nMaybe you need another colorscheme: vimscript #2681\r\n\r\nScreen Shot:\r\nhttp:\/\/photo2.bababian.com\/upload2\/20090616\/F49050FBC235DE77512F9B318D2FA6A8.jpg","4":"Updated for z\/OS PLI Enterprise Compiler.\r\nBased on Ing. Michael Fitz's version: vimscript #1013\r\n\r\nMaybe you need another colorscheme: vimscript #2681\r\n\r\nScreen Shot:\r\nhttp:\/\/photo2.bababian.com\/upload2\/20090616\/F49050FBC235DE77512F9B318D2FA6A8.jpg","install_details":"Drop into:\r\nvimxx\/syntax\r\nor\r\nvimfiles\/syntax","5":"Drop into:\r\nvimxx\/syntax\r\nor\r\nvimfiles\/syntax","first_name":"Ricky","6":"Ricky","last_name":"Wu","7":"Wu","releases":[{"0":"2685","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"pli.vim","4":"pli.vim","src_id":"10864","5":"10864","creation_date":"1245253517","6":"1245253517"}]},"2684":{"script_id":"2684","0":"2684","script_name":"herald.vim","1":"herald.vim","script_type":"color scheme","2":"color scheme","summary":"A dark color scheme for Vim","3":"A dark color scheme for Vim","description":"An easy-to-read dark color scheme. \r\n\r\nSee http:\/\/www.h3rald.com\/herald-vim-color-scheme for a preview and more information.","4":"An easy-to-read dark color scheme. \r\n\r\nSee http:\/\/www.h3rald.com\/herald-vim-color-scheme for a preview and more information.","install_details":"","5":"","first_name":"Fabio","6":"Fabio","last_name":"Cevasco","7":"Cevasco","releases":[{"0":"2684","vim_version":"6.0","1":"6.0","script_version":"0.2.1","2":"0.2.1","version_comment":"Improved readability in search highlights\r\nDelimiters are now rendered like operators","3":"Improved readability in search highlights\r\nDelimiters are now rendered like operators","package":"herald.vim","4":"herald.vim","src_id":"11712","5":"11712","creation_date":"1258030605","6":"1258030605"},{"0":"2684","vim_version":"6.0","1":"6.0","script_version":"0.2.0","2":"0.2.0","version_comment":"Support for 8 and 16 color modes;\r\nFixed completion menu colors;\r\nImproved readability for Visual mode;\r\nSpecified highlighting for all the most common Vim syntax groups;\r\n","3":"Support for 8 and 16 color modes;\r\nFixed completion menu colors;\r\nImproved readability for Visual mode;\r\nSpecified highlighting for all the most common Vim syntax groups;\r\n","package":"herald.vim","4":"herald.vim","src_id":"10889","5":"10889","creation_date":"1245767598","6":"1245767598"},{"0":"2684","vim_version":"6.0","1":"6.0","script_version":"0.1.0","2":"0.1.0","version_comment":"Initial upload","3":"Initial upload","package":"herald.vim","4":"herald.vim","src_id":"10862","5":"10862","creation_date":"1245242294","6":"1245242294"}]},"2683":{"script_id":"2683","0":"2683","script_name":"FastLadder.vim","1":"FastLadder.vim","script_type":"utility","2":"utility","summary":"vimscript for fastladder","3":"vimscript for fastladder","description":"This is vimscript for fastladder (http:\/\/fastladder.com\/)\n\nUsage:\n\n  :FastLadder\n\nKeyBinding:\n  [LIST]\n  type <c-n> to goto next and open entry\n  type <c-p> to goto prev and open entry\n  type <cr> to show entry\n  type <c-a> to show all list\n  type <s-a> to show unread list\n  type *     to toggle pin\n  type r to reload entries\n  type q to close window\n\n  [CONTENT]\n  type <c-n> to show next entry\n  type <c-p> to show previous entry\n  type <c-i> to open URL with browser\n  type q to close window\n\n  type ? to show help list\n\nRequire:\n  curl command (http:\/\/curl.haxx.se\/)\n","4":"This is vimscript for fastladder (http:\/\/fastladder.com\/)\n\nUsage:\n\n  :FastLadder\n\nKeyBinding:\n  [LIST]\n  type <c-n> to goto next and open entry\n  type <c-p> to goto prev and open entry\n  type <cr> to show entry\n  type <c-a> to show all list\n  type <s-a> to show unread list\n  type *     to toggle pin\n  type r to reload entries\n  type q to close window\n\n  [CONTENT]\n  type <c-n> to show next entry\n  type <c-p> to show previous entry\n  type <c-i> to open URL with browser\n  type q to close window\n\n  type ? to show help list\n\nRequire:\n  curl command (http:\/\/curl.haxx.se\/)\n","install_details":"copy it to your plugin directory.\n","5":"copy it to your plugin directory.\n","first_name":"Yasuhiro","6":"Yasuhiro","last_name":"Matsumoto","7":"Matsumoto","releases":[{"0":"2683","vim_version":"7.0","1":"7.0","script_version":"0.9","2":"0.9","version_comment":"This is an upgrade for FastLadder.vim: does not work correctoly. invalid token.\n","3":"This is an upgrade for FastLadder.vim: does not work correctoly. invalid token.\n","package":"fastladder.vim","4":"fastladder.vim","src_id":"10882","5":"10882","creation_date":"1245513563","6":"1245513563"},{"0":"2683","vim_version":"7.0","1":"7.0","script_version":"0.8","2":"0.8","version_comment":"This is an upgrade for FastLadder.vim: does not work correctoly. and can't open browser on linux.\n","3":"This is an upgrade for FastLadder.vim: does not work correctoly. and can't open browser on linux.\n","package":"fastladder.vim","4":"fastladder.vim","src_id":"10881","5":"10881","creation_date":"1245506467","6":"1245506467"},{"0":"2683","vim_version":"7.0","1":"7.0","script_version":"0.7","2":"0.7","version_comment":"This is an upgrade for FastLadder.vim: support livedoor reader!\n","3":"This is an upgrade for FastLadder.vim: support livedoor reader!\n","package":"fastladder.vim","4":"fastladder.vim","src_id":"10875","5":"10875","creation_date":"1245422085","6":"1245422085"},{"0":"2683","vim_version":"7.0","1":"7.0","script_version":"0.6","2":"0.6","version_comment":"This is an upgrade for FastLadder.vim: <c-t> goes that touch all entries.\n","3":"This is an upgrade for FastLadder.vim: <c-t> goes that touch all entries.\n","package":"fastladder.vim","4":"fastladder.vim","src_id":"10870","5":"10870","creation_date":"1245303477","6":"1245303477"}]},"2682":{"script_id":"2682","0":"2682","script_name":"colorsupport.vim","1":"colorsupport.vim","script_type":"utility","2":"utility","summary":"Use colorschemes written for gvim in color terminals.","3":"Use colorschemes written for gvim in color terminals.","description":"colorsupport.vim\r\n================\r\nUse colorschemes written for gvim in color terminals.\r\nTested with many colorschemes including color sampler pack (vimscript #625)\r\n\r\nTo set up a 256-color terminal, see\r\n\r\n- http:\/\/push.cx\/2008\/256-color-xterms-in-ubuntu\r\n- http:\/\/robotsrule.us\/vim\/\r\n\r\nAnd don't forget to rate ;^)\r\n\r\nSimple usage\r\n------------\r\n- Drop 'colorsupport.vim' in '~\/.vim\/plugin'.\r\n\r\n  At next startup, colorscheme loaded by '.vimrc' will be reloaded with gui\r\n  colors mapped to terminal palette.  That is, if you already have gvim\r\n  colorscheme set in '~\/.vimrc', then it'll work as soon as you install the\r\n  'colorsupport.vim' script.\r\n\r\n- Browse and preview colorschemes in your &runtimepath by\r\n  ':ColorSchemeBrowse'.  You can also manually try colorschemes using\r\n  ':ColorScheme', just like ':colorscheme'.\r\n\r\n- On slow systems, it can take long to convert colorscheme every time vim\r\n  starts up.  For faster start-up, save last colorscheme by ':ColorSchemeSave'.\r\n\r\n  By default, this saves last colorscheme loaded by ':ColorScheme' in the first \r\n  &runtimepath (usually, ~\/.vim\/colors on Unix).\r\n\r\n  If last colorscheme is already from '~\/.vim\/colors', error will occur,  and\r\n  you should use ':ColorSchemeSave <new-colorscheme-name>' instead.\r\n\r\nUpgrade\r\n-------\r\nWhen upgrading colorsupport.vim, additional color groups can be set, \r\nbut color schemes saved by :ColorSchemeSave passes conversion by :ColorScheme.\r\nDelete old (converted and saved) color schemes if you want re-convert.\r\n\r\nCustomization\r\n-------------\r\n- g:colorsupport_palette_name (one of \"tango\" (default), \"console\", \"xterm\", \"rxvt\")\r\n- g:colorsupport_palette (e.g., ['#000000',  ...]. (length better be =16))\r\n\r\n- g:colorsupport_cube_name (one of \"xterm256\", \"xterm88\", \"konsole\", \"eterm\")\r\n- g:colorsupport_cube (e.g. [0x00, 0x2A, 0x55, 0xAA, 0xD4])\r\n\r\n- g:colorsupport_grey (e.g., range(0x1C, 0xFF, 30))\r\n\r\n- g:colorsupport_rgbs (e.g., ['\/usr\/X11\/share\/X11'])\r\n\r\nKeep {len(g:colorsupport_palette) + len(g:colorsupport_cube)^3 + len(g:colorsupport_grey) == &t_Co}\r\n\r\nCommands\r\n--------\r\n- Highlight ... \r\n\r\n  Arguments are the same as :highlight\r\n  Set 'cterm', 'ctermfg', 'ctermbg' based on 'gui', 'guifg', 'guibg',\r\n  respectively.  Note that given 'cterm.*' settings are ignored.\r\n\r\n- ColorScheme <path-or-name>\r\n\r\n  Load a colorscheme using ':Highlight', instead of ':highlight'.\r\n  Unlike colorscheme, path is accepted as well as colorscheme name.\r\n\r\n- ColorSchemeBrowse [<path>]\r\n\r\n  Browse colorschemes in <path> (or &runtimepath, if no arguments given)\r\n\r\n- ColorSchemeSave [<name>]\r\n\r\n  Save last colorscheme loaded by ':ColorScheme' (or, equivalently, browsed by\r\n  ':ColorSchemeViewer') in the first &runtimepath.  If <name> is not given,\r\n  original name of last colorscheme is used.\r\n\r\n\r\nComparison\r\n----------\r\nAt the time that I uploaded this script, I was unaware of other color conversion scripts.\r\nAnd I've tried them later.\r\n\r\nvimscript #2390. (Thank you marty)\r\n\r\nKey difference is that vimscript #2390 practically requires gvim installed.\r\nAnd major difficulty (and dirty tricks) of this script was to get gui \r\nattributes from colorschemes, which are not obtainable from series of \r\nsynIDxxx() functions without +gui feature.  \r\n\r\nvimscript #1809\r\n\r\nvimscript #1809 tries to extract hilight information by string match.\r\n(I assume that this approach is what most conversion script have took)\r\nBy contrast, colorsupport.vim actually run the original color scheme \r\nwith highlight command substituted with Highlight command.\r\nLater works better because many color schemes have highlights\r\nin conditional block, which should not be extracted.\r\n\r\nFurthermore, vimscript #1809 does not support color names.","4":"colorsupport.vim\r\n================\r\nUse colorschemes written for gvim in color terminals.\r\nTested with many colorschemes including color sampler pack (vimscript #625)\r\n\r\nTo set up a 256-color terminal, see\r\n\r\n- http:\/\/push.cx\/2008\/256-color-xterms-in-ubuntu\r\n- http:\/\/robotsrule.us\/vim\/\r\n\r\nAnd don't forget to rate ;^)\r\n\r\nSimple usage\r\n------------\r\n- Drop 'colorsupport.vim' in '~\/.vim\/plugin'.\r\n\r\n  At next startup, colorscheme loaded by '.vimrc' will be reloaded with gui\r\n  colors mapped to terminal palette.  That is, if you already have gvim\r\n  colorscheme set in '~\/.vimrc', then it'll work as soon as you install the\r\n  'colorsupport.vim' script.\r\n\r\n- Browse and preview colorschemes in your &runtimepath by\r\n  ':ColorSchemeBrowse'.  You can also manually try colorschemes using\r\n  ':ColorScheme', just like ':colorscheme'.\r\n\r\n- On slow systems, it can take long to convert colorscheme every time vim\r\n  starts up.  For faster start-up, save last colorscheme by ':ColorSchemeSave'.\r\n\r\n  By default, this saves last colorscheme loaded by ':ColorScheme' in the first \r\n  &runtimepath (usually, ~\/.vim\/colors on Unix).\r\n\r\n  If last colorscheme is already from '~\/.vim\/colors', error will occur,  and\r\n  you should use ':ColorSchemeSave <new-colorscheme-name>' instead.\r\n\r\nUpgrade\r\n-------\r\nWhen upgrading colorsupport.vim, additional color groups can be set, \r\nbut color schemes saved by :ColorSchemeSave passes conversion by :ColorScheme.\r\nDelete old (converted and saved) color schemes if you want re-convert.\r\n\r\nCustomization\r\n-------------\r\n- g:colorsupport_palette_name (one of \"tango\" (default), \"console\", \"xterm\", \"rxvt\")\r\n- g:colorsupport_palette (e.g., ['#000000',  ...]. (length better be =16))\r\n\r\n- g:colorsupport_cube_name (one of \"xterm256\", \"xterm88\", \"konsole\", \"eterm\")\r\n- g:colorsupport_cube (e.g. [0x00, 0x2A, 0x55, 0xAA, 0xD4])\r\n\r\n- g:colorsupport_grey (e.g., range(0x1C, 0xFF, 30))\r\n\r\n- g:colorsupport_rgbs (e.g., ['\/usr\/X11\/share\/X11'])\r\n\r\nKeep {len(g:colorsupport_palette) + len(g:colorsupport_cube)^3 + len(g:colorsupport_grey) == &t_Co}\r\n\r\nCommands\r\n--------\r\n- Highlight ... \r\n\r\n  Arguments are the same as :highlight\r\n  Set 'cterm', 'ctermfg', 'ctermbg' based on 'gui', 'guifg', 'guibg',\r\n  respectively.  Note that given 'cterm.*' settings are ignored.\r\n\r\n- ColorScheme <path-or-name>\r\n\r\n  Load a colorscheme using ':Highlight', instead of ':highlight'.\r\n  Unlike colorscheme, path is accepted as well as colorscheme name.\r\n\r\n- ColorSchemeBrowse [<path>]\r\n\r\n  Browse colorschemes in <path> (or &runtimepath, if no arguments given)\r\n\r\n- ColorSchemeSave [<name>]\r\n\r\n  Save last colorscheme loaded by ':ColorScheme' (or, equivalently, browsed by\r\n  ':ColorSchemeViewer') in the first &runtimepath.  If <name> is not given,\r\n  original name of last colorscheme is used.\r\n\r\n\r\nComparison\r\n----------\r\nAt the time that I uploaded this script, I was unaware of other color conversion scripts.\r\nAnd I've tried them later.\r\n\r\nvimscript #2390. (Thank you marty)\r\n\r\nKey difference is that vimscript #2390 practically requires gvim installed.\r\nAnd major difficulty (and dirty tricks) of this script was to get gui \r\nattributes from colorschemes, which are not obtainable from series of \r\nsynIDxxx() functions without +gui feature.  \r\n\r\nvimscript #1809\r\n\r\nvimscript #1809 tries to extract hilight information by string match.\r\n(I assume that this approach is what most conversion script have took)\r\nBy contrast, colorsupport.vim actually run the original color scheme \r\nwith highlight command substituted with Highlight command.\r\nLater works better because many color schemes have highlights\r\nin conditional block, which should not be extracted.\r\n\r\nFurthermore, vimscript #1809 does not support color names.","install_details":"mv colorsupport.vim ~\/.vim\/plugin","5":"mv colorsupport.vim ~\/.vim\/plugin","first_name":"JiHwan","6":"JiHwan","last_name":"Lee","7":"Lee","releases":[{"0":"2682","vim_version":"7.0","1":"7.0","script_version":"1.0.5","2":"1.0.5","version_comment":"- Fix a bug that ignores background setting.\r\n- Fix an error which happens when colorscheme does not set g:colors_name.","3":"- Fix a bug that ignores background setting.\r\n- Fix an error which happens when colorscheme does not set g:colors_name.","package":"colorsupport.vim","4":"colorsupport.vim","src_id":"20938","5":"20938","creation_date":"1382290886","6":"1382290886"},{"0":"2682","vim_version":"7.0","1":"7.0","script_version":"1.0.4","2":"1.0.4","version_comment":"Bug fix:\r\n- Use NONE instead of none for transparent gui color to avoid gvim errors.\r\n- Fix an issue that wrong colors (especially background colors) are chosen.","3":"Bug fix:\r\n- Use NONE instead of none for transparent gui color to avoid gvim errors.\r\n- Fix an issue that wrong colors (especially background colors) are chosen.","package":"colorsupport.vim","4":"colorsupport.vim","src_id":"20926","5":"20926","creation_date":"1382028317","6":"1382028317"},{"0":"2682","vim_version":"7.0","1":"7.0","script_version":"1.0.3","2":"1.0.3","version_comment":"minor improvements and bug fixes, including\r\n- handles \"hilight\" with bang(!)\r\n- fix a bug that g:colors_name goes wrong when &background set after g:colors_name\r\n- lazy load script variables for faster start-up","3":"minor improvements and bug fixes, including\r\n- handles \"hilight\" with bang(!)\r\n- fix a bug that g:colors_name goes wrong when &background set after g:colors_name\r\n- lazy load script variables for faster start-up","package":"colorsupport.vim","4":"colorsupport.vim","src_id":"14828","5":"14828","creation_date":"1295725935","6":"1295725935"},{"0":"2682","vim_version":"7.0","1":"7.0","script_version":"1.0.2","2":"1.0.2","version_comment":"Added hard-coded default color groups.\r\nMap guisp to ctermbg.","3":"Added hard-coded default color groups.\r\nMap guisp to ctermbg.","package":"colorsupport.vim","4":"colorsupport.vim","src_id":"10892","5":"10892","creation_date":"1245902788","6":"1245902788"},{"0":"2682","vim_version":"7.0","1":"7.0","script_version":"1.0.1","2":"1.0.1","version_comment":"Added konsole and eterm color cube.\r\nGeneralize user customization.","3":"Added konsole and eterm color cube.\r\nGeneralize user customization.","package":"colorsupport.vim","4":"colorsupport.vim","src_id":"10863","5":"10863","creation_date":"1245248609","6":"1245248609"},{"0":"2682","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"colorsupport.vim","4":"colorsupport.vim","src_id":"10851","5":"10851","creation_date":"1245169024","6":"1245169024"}]},"2681":{"script_id":"2681","0":"2681","script_name":"Colorzone","1":"Colorzone","script_type":"color scheme","2":"color scheme","summary":"Colorscheme Use More Soft Colors","3":"Colorscheme Use More Soft Colors","description":"Colorzone use more soft colors for read comfortably but isn't dazzling .\r\n\r\nBased on \"tango-morning\" and \"wargreycolorscheme\" color scheme.\r\n\r\nMaybe has display problem in other file types, can works with both GUI and console.\r\nYou can chose another color for pop up menu.\r\n\r\nI want change the colors to suitable for Tango Icon Theme Guidelines in the future.\r\nhttp:\/\/tango.freedesktop.org\/Tango_Icon_Theme_Guidelines\r\n\r\nScreen Shots:\r\nhttp:\/\/farm5.static.flickr.com\/4042\/4686809567_b2972b033c_b.jpg\r\n\r\nIf your terminal can use RGB colors, use this escape sequence colors:\r\nff888a85,ffef2929,ff8ae234,ffe9b96e,ff00bfff,ffda70d6,ff87ceeb,ffeeeeec\r\ngray     red      green    yellow   blue     magenta  cyan     white\r\nThe Terminal colors and GUI colors are different.","4":"Colorzone use more soft colors for read comfortably but isn't dazzling .\r\n\r\nBased on \"tango-morning\" and \"wargreycolorscheme\" color scheme.\r\n\r\nMaybe has display problem in other file types, can works with both GUI and console.\r\nYou can chose another color for pop up menu.\r\n\r\nI want change the colors to suitable for Tango Icon Theme Guidelines in the future.\r\nhttp:\/\/tango.freedesktop.org\/Tango_Icon_Theme_Guidelines\r\n\r\nScreen Shots:\r\nhttp:\/\/farm5.static.flickr.com\/4042\/4686809567_b2972b033c_b.jpg\r\n\r\nIf your terminal can use RGB colors, use this escape sequence colors:\r\nff888a85,ffef2929,ff8ae234,ffe9b96e,ff00bfff,ffda70d6,ff87ceeb,ffeeeeec\r\ngray     red      green    yellow   blue     magenta  cyan     white\r\nThe Terminal colors and GUI colors are different.","install_details":"Drop the file into vim\/colors\/ or vimfiles\/colors\/.\r\n\r\nHere also has some highlighting effect for status line, release comments in color scheme and add these into vimrc:\r\n\r\nset statusline=\r\n\"set statusline+=%#StatuslineBufNr#%-1.2n\\                        \" buffer number\r\nset statusline+=%h%#StatuslineFlag#%m%r%w                         \" flags\r\nset statusline+=%#StatuslinePath#\\ %-0.20{StatusLineGetPath()}%0* \" path\r\nset statusline+=%#StatuslineFileName#\\\/%t\\                        \" file name \r\nset statusline+=%#StatuslineFileType#\\ %{strlen(&ft)?&ft:'**'}    \" filetype\r\nset statusline+=%#StatuslineFileType#\\ %{&fileformat}             \" file format\r\nset statusline+=%#StatuslineFileEnc#\\ %{&encoding}                \" encoding\r\nset statusline+=%#StatuslineFileEnc#\\ X:%-2B\\ %0*                 \" current char\r\nset statusline+=%#StatuslinePosition#\\L:%l\\ C:%c\\                 \"line\r\nset statusline+=%#StatuslinePercent#\\ TL:%L\\ %P\\                  \"position percentage\r\nset statusline+=%#StatuslineCapsBuddy#%{exists('*CapsLockSTATUSLINE')?CapsLockSTATUSLINE():''} \"Caps\r\nset statusline+=%#StatuslineCapsBuddy#\\ %{VimBuddy()}             \"Buddy\r\nset statusline+=%#StatuslineTime#%{strftime(\\\"%m-%d\\ %H:%M\\\")}    \" current time\r\n\r\nfunction! StatusLineGetPath() \"{{{\r\n  let g:Statusline_Max_Path = 20\r\n  let p = expand('%:.:h') \"relative to current path, and head path only\r\n  let p = substitute(p,'\\','\/','g')\r\n  let p = substitute(p, '^\\V' . $HOME, '~', '')\r\n  if len(p) > g:Statusline_Max_Path \r\n    let p = simplify(p)\r\n    let p = pathshorten(p)\r\n  endif\r\n  return p\r\nendfunction \"}}}","5":"Drop the file into vim\/colors\/ or vimfiles\/colors\/.\r\n\r\nHere also has some highlighting effect for status line, release comments in color scheme and add these into vimrc:\r\n\r\nset statusline=\r\n\"set statusline+=%#StatuslineBufNr#%-1.2n\\                        \" buffer number\r\nset statusline+=%h%#StatuslineFlag#%m%r%w                         \" flags\r\nset statusline+=%#StatuslinePath#\\ %-0.20{StatusLineGetPath()}%0* \" path\r\nset statusline+=%#StatuslineFileName#\\\/%t\\                        \" file name \r\nset statusline+=%#StatuslineFileType#\\ %{strlen(&ft)?&ft:'**'}    \" filetype\r\nset statusline+=%#StatuslineFileType#\\ %{&fileformat}             \" file format\r\nset statusline+=%#StatuslineFileEnc#\\ %{&encoding}                \" encoding\r\nset statusline+=%#StatuslineFileEnc#\\ X:%-2B\\ %0*                 \" current char\r\nset statusline+=%#StatuslinePosition#\\L:%l\\ C:%c\\                 \"line\r\nset statusline+=%#StatuslinePercent#\\ TL:%L\\ %P\\                  \"position percentage\r\nset statusline+=%#StatuslineCapsBuddy#%{exists('*CapsLockSTATUSLINE')?CapsLockSTATUSLINE():''} \"Caps\r\nset statusline+=%#StatuslineCapsBuddy#\\ %{VimBuddy()}             \"Buddy\r\nset statusline+=%#StatuslineTime#%{strftime(\\\"%m-%d\\ %H:%M\\\")}    \" current time\r\n\r\nfunction! StatusLineGetPath() \"{{{\r\n  let g:Statusline_Max_Path = 20\r\n  let p = expand('%:.:h') \"relative to current path, and head path only\r\n  let p = substitute(p,'\\','\/','g')\r\n  let p = substitute(p, '^\\V' . $HOME, '~', '')\r\n  if len(p) > g:Statusline_Max_Path \r\n    let p = simplify(p)\r\n    let p = pathshorten(p)\r\n  endif\r\n  return p\r\nendfunction \"}}}","first_name":"Ricky","6":"Ricky","last_name":"Wu","7":"Wu","releases":[{"0":"2681","vim_version":"7.0","1":"7.0","script_version":"1.2","2":"1.2","version_comment":"optimize for go language version 1","3":"optimize for go language version 1","package":"colorzone.vim","4":"colorzone.vim","src_id":"17972","5":"17972","creation_date":"1337149741","6":"1337149741"},{"0":"2681","vim_version":"7.0","1":"7.0","script_version":"1.1","2":"1.1","version_comment":"minor changes","3":"minor changes","package":"colorzone.vim","4":"colorzone.vim","src_id":"17960","5":"17960","creation_date":"1337079251","6":"1337079251"},{"0":"2681","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Optimize cterm colors and changes for GUI, fix some confusion for MatchParen etc.","3":"Optimize cterm colors and changes for GUI, fix some confusion for MatchParen etc.","package":"colorzone.vim","4":"colorzone.vim","src_id":"13153","5":"13153","creation_date":"1276145774","6":"1276145774"}]},"2680":{"script_id":"2680","0":"2680","script_name":"cursoroverdictionary","1":"cursoroverdictionary","script_type":"utility","2":"utility","summary":"Look up word or phrase in English-Japanese Dictionary","3":"Look up word or phrase in English-Japanese Dictionary","description":"cursoroverdictionary is a Vim plugin to look up word or idiom in English-Japanese Dictionary.\r\n(For a beginner of English such as me.)\r\n\r\nScreencast: http:\/\/www.youtube.com\/watch?v=eb8khHL8I7Q\r\n\r\nRequirements:\r\n- Vim 7.0 or later\r\n- Python\r\nhttp:\/\/www.python.org\/download\/\r\n- Dictionary data(PDIC 1 line text format)\r\n","4":"cursoroverdictionary is a Vim plugin to look up word or idiom in English-Japanese Dictionary.\r\n(For a beginner of English such as me.)\r\n\r\nScreencast: http:\/\/www.youtube.com\/watch?v=eb8khHL8I7Q\r\n\r\nRequirements:\r\n- Vim 7.0 or later\r\n- Python\r\nhttp:\/\/www.python.org\/download\/\r\n- Dictionary data(PDIC 1 line text format)\r\n","install_details":"Download cursoroverdictionary*.zip, and extract your ~\/.vim directory.\r\n\r\nFor more information about installation, please see ~\/.vim\/doc\/cursoroverdictionary.txt.\r\nThis document is written in Japanese, because intended user of this plugin is the Japanese.\r\n","5":"Download cursoroverdictionary*.zip, and extract your ~\/.vim directory.\r\n\r\nFor more information about installation, please see ~\/.vim\/doc\/cursoroverdictionary.txt.\r\nThis document is written in Japanese, because intended user of this plugin is the Japanese.\r\n","first_name":"John","6":"John","last_name":"Yanagiya","7":"Yanagiya","releases":[{"0":"2680","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Several features added.","3":"Several features added.","package":"cursoroverdictionary0_1.zip","4":"cursoroverdictionary0_1.zip","src_id":"11580","5":"11580","creation_date":"1256395106","6":"1256395106"},{"0":"2680","vim_version":"7.0","1":"7.0","script_version":"0.0.9","2":"0.0.9","version_comment":"Add external search result cache.","3":"Add external search result cache.","package":"cursoroverdictionary0_0_9.zip","4":"cursoroverdictionary0_0_9.zip","src_id":"11502","5":"11502","creation_date":"1255086460","6":"1255086460"},{"0":"2680","vim_version":"7.0","1":"7.0","script_version":"0.0.8","2":"0.0.8","version_comment":"Bugfix for garbled message","3":"Bugfix for garbled message","package":"cursoroverdictionary0_0_8.zip","4":"cursoroverdictionary0_0_8.zip","src_id":"11485","5":"11485","creation_date":"1254712178","6":"1254712178"},{"0":"2680","vim_version":"7.0","1":"7.0","script_version":"0.0.7","2":"0.0.7","version_comment":"bug fix","3":"bug fix","package":"cursoroverdictionary0_0_7.zip","4":"cursoroverdictionary0_0_7.zip","src_id":"11474","5":"11474","creation_date":"1254575316","6":"1254575316"},{"0":"2680","vim_version":"7.0","1":"7.0","script_version":"0.0.5","2":"0.0.5","version_comment":"Several features added.","3":"Several features added.","package":"cursoroverdictionary0_0_5.zip","4":"cursoroverdictionary0_0_5.zip","src_id":"11471","5":"11471","creation_date":"1254474219","6":"1254474219"},{"0":"2680","vim_version":"7.0","1":"7.0","script_version":"0.0.2","2":"0.0.2","version_comment":"Initial upload","3":"Initial upload","package":"cursoroverdictionary0_0_2.zip","4":"cursoroverdictionary0_0_2.zip","src_id":"10847","5":"10847","creation_date":"1245152573","6":"1245152573"}]},"2679":{"script_id":"2679","0":"2679","script_name":"textobj-verticalbar","1":"textobj-verticalbar","script_type":"utility","2":"utility","summary":"Text objects for vertical bar","3":"Text objects for vertical bar","description":"textobj-verticalbar is a Vim plugin to provide text objects to select wiki's table cell.\r\n\r\nFor example, if the content of a buffer as follows:\r\n(here \"*\" means the cursor)\r\n\r\n\t|| Header 1*|| Header 2 || Header 3 ||\r\n\t|| Row1 || Cell1-2 || Cell1-3 ||\r\n\t|| Row2 || Cell2-2 || Cell2-3 ||\r\n\r\n\r\n|<Plug>(textobj-verticalbar-a)| will select columns as follows:\r\n(here \"<\" and \">\" indicates the selected range)\r\n\r\n\t||<Header 1>|| Header 2 || Header 3 ||\r\n\t|| Row1 || Cell1-2 || Cell1-3 ||\r\n\t|| Row2 || Cell2-2 || Cell2-3 ||\r\n\r\n|<Plug>(textobj-verticalbar-i)| will select columns as follows:\r\n(here \"<\" and \">\" indicates the selected range)\r\n\r\n\t|<| Header 1 |>| Header 2 || Header 3 ||\r\n\t\t--------- \r\n\t|| Row1 || Cell1-2 || Cell1-3 ||\r\n\t|| Row2 || Cell2-2 || Cell2-3 ||\r\n\r\nRequirements:\r\n- Vim 7.2 or later\r\n- textobj-user 0.3.7 or later (vimscript#2100)\r\n\r\n","4":"textobj-verticalbar is a Vim plugin to provide text objects to select wiki's table cell.\r\n\r\nFor example, if the content of a buffer as follows:\r\n(here \"*\" means the cursor)\r\n\r\n\t|| Header 1*|| Header 2 || Header 3 ||\r\n\t|| Row1 || Cell1-2 || Cell1-3 ||\r\n\t|| Row2 || Cell2-2 || Cell2-3 ||\r\n\r\n\r\n|<Plug>(textobj-verticalbar-a)| will select columns as follows:\r\n(here \"<\" and \">\" indicates the selected range)\r\n\r\n\t||<Header 1>|| Header 2 || Header 3 ||\r\n\t|| Row1 || Cell1-2 || Cell1-3 ||\r\n\t|| Row2 || Cell2-2 || Cell2-3 ||\r\n\r\n|<Plug>(textobj-verticalbar-i)| will select columns as follows:\r\n(here \"<\" and \">\" indicates the selected range)\r\n\r\n\t|<| Header 1 |>| Header 2 || Header 3 ||\r\n\t\t--------- \r\n\t|| Row1 || Cell1-2 || Cell1-3 ||\r\n\t|| Row2 || Cell2-2 || Cell2-3 ||\r\n\r\nRequirements:\r\n- Vim 7.2 or later\r\n- textobj-user 0.3.7 or later (vimscript#2100)\r\n\r\n","install_details":"Download textobj-verticalbar-*.zip, and extract your ~\/.vim directory.\r\n","5":"Download textobj-verticalbar-*.zip, and extract your ~\/.vim directory.\r\n","first_name":"John","6":"John","last_name":"Yanagiya","7":"Yanagiya","releases":[{"0":"2679","vim_version":"7.0","1":"7.0","script_version":"0.0.3","2":"0.0.3","version_comment":"Fixed bug with multi-byte characters.","3":"Fixed bug with multi-byte characters.","package":"textobj-verticalbar_0.0.3.zip","4":"textobj-verticalbar_0.0.3.zip","src_id":"11503","5":"11503","creation_date":"1255087213","6":"1255087213"},{"0":"2679","vim_version":"7.2","1":"7.2","script_version":"0.0.2","2":"0.0.2","version_comment":"Initial upload","3":"Initial upload","package":"textobj-verticalbar-0.0.2.zip","4":"textobj-verticalbar-0.0.2.zip","src_id":"10846","5":"10846","creation_date":"1245152129","6":"1245152129"}]},"2678":{"script_id":"2678","0":"2678","script_name":"GoogleReader.vim","1":"GoogleReader.vim","script_type":"utility","2":"utility","summary":"vimscript for googlereader","3":"vimscript for googlereader","description":"This is vimscript for googlereader (http:\/\/www.google.com\/reader\/)\n\nUsage:\n\n  :GoogleReader\n\nKeyBinding:\n  [LIST]\n  type <c-n> to goto next and open entry\n  type <c-p> to goto prev and open entry\n  type <cr> to show entry\n  type <c-a> to show all list\n  type <s-a> to show unread list\n  type +     to toggle read\/unread mark\n  type *     to toggle star\/unstar mark\n  type r to reload entries\n  type q to close window\n\n  [CONTENT]\n  type <c-n> to show next entry\n  type <c-p> to show previous entry\n  type <c-i> to open URL with browser\n  type q to close window\n\n  type ? to show help list\n\nRequire:\n  curl command (http:\/\/curl.haxx.se\/)\n","4":"This is vimscript for googlereader (http:\/\/www.google.com\/reader\/)\n\nUsage:\n\n  :GoogleReader\n\nKeyBinding:\n  [LIST]\n  type <c-n> to goto next and open entry\n  type <c-p> to goto prev and open entry\n  type <cr> to show entry\n  type <c-a> to show all list\n  type <s-a> to show unread list\n  type +     to toggle read\/unread mark\n  type *     to toggle star\/unstar mark\n  type r to reload entries\n  type q to close window\n\n  [CONTENT]\n  type <c-n> to show next entry\n  type <c-p> to show previous entry\n  type <c-i> to open URL with browser\n  type q to close window\n\n  type ? to show help list\n\nRequire:\n  curl command (http:\/\/curl.haxx.se\/)\n","install_details":"copy it to your plugin directory.\n","5":"copy it to your plugin directory.\n","first_name":"Yasuhiro","6":"Yasuhiro","last_name":"Matsumoto","7":"Matsumoto","releases":[{"0":"2678","vim_version":"7.0","1":"7.0","script_version":"2.2","2":"2.2","version_comment":"This is an upgrade for GoogleReader.vim: fixed authentication problem. added Authorization header.\n","3":"This is an upgrade for GoogleReader.vim: fixed authentication problem. added Authorization header.\n","package":"googlereader.vim","4":"googlereader.vim","src_id":"13267","5":"13267","creation_date":"1277892004","6":"1277892004"},{"0":"2678","vim_version":"7.0","1":"7.0","script_version":"2.1","2":"2.1","version_comment":"This is an upgrade for GoogleReader.vim: added script type header for Vimana. change default browser to 'x-www-browser'. set nolist in entries.\n","3":"This is an upgrade for GoogleReader.vim: added script type header for Vimana. change default browser to 'x-www-browser'. set nolist in entries.\n","package":"googlereader.vim","4":"googlereader.vim","src_id":"12301","5":"12301","creation_date":"1265245279","6":"1265245279"},{"0":"2678","vim_version":"7.0","1":"7.0","script_version":"2.0","2":"2.0","version_comment":"This is an upgrade for GoogleReader.vim: does not work correctoly. invalid token.\n","3":"This is an upgrade for GoogleReader.vim: does not work correctoly. invalid token.\n","package":"googlereader.vim","4":"googlereader.vim","src_id":"10883","5":"10883","creation_date":"1245513575","6":"1245513575"},{"0":"2678","vim_version":"7.0","1":"7.0","script_version":"1.9","2":"1.9","version_comment":"This is an upgrade for GoogleReader.vim: does not work correctoly. and can't open browser on linux.\n","3":"This is an upgrade for GoogleReader.vim: does not work correctoly. and can't open browser on linux.\n","package":"googlereader.vim","4":"googlereader.vim","src_id":"10880","5":"10880","creation_date":"1245506318","6":"1245506318"},{"0":"2678","vim_version":"7.0","1":"7.0","script_version":"1.8","2":"1.8","version_comment":"This is an upgrade for GoogleReader.vim: handle error of authentication.\n","3":"This is an upgrade for GoogleReader.vim: handle error of authentication.\n","package":"googlereader.vim","4":"googlereader.vim","src_id":"10874","5":"10874","creation_date":"1245422058","6":"1245422058"},{"0":"2678","vim_version":"7.0","1":"7.0","script_version":"1.7","2":"1.7","version_comment":"This is an upgrade for GoogleReader.vim: show wrapped text in context window.\n","3":"This is an upgrade for GoogleReader.vim: show wrapped text in context window.\n","package":"googlereader.vim","4":"googlereader.vim","src_id":"10869","5":"10869","creation_date":"1245296753","6":"1245296753"}]},"2677":{"script_id":"2677","0":"2677","script_name":"nature.vim","1":"nature.vim","script_type":"color scheme","2":"color scheme","summary":"colorscheme with nature tones","3":"colorscheme with nature tones","description":"This is a very simple color scheme.\r\nFeatures:\r\n* Black background\r\n* Green and blue with a touch of yellow and magenta\r\n* Tango palette\r\n* Color difference between [Conditional] and [Repeat] statements\r\n* Dark gray comments\r\n* PINK ERRORS!!!!!!!!1!\r\n* Works with both GUI and console\r\n! Does not support transparency (intentional).\r\nScreenshots here: http:\/\/picasaweb.google.com\/elfakyn\/Vim\r\n\r\nI think I should get a job in advertising :).\r\nEnjoy!","4":"This is a very simple color scheme.\r\nFeatures:\r\n* Black background\r\n* Green and blue with a touch of yellow and magenta\r\n* Tango palette\r\n* Color difference between [Conditional] and [Repeat] statements\r\n* Dark gray comments\r\n* PINK ERRORS!!!!!!!!1!\r\n* Works with both GUI and console\r\n! Does not support transparency (intentional).\r\nScreenshots here: http:\/\/picasaweb.google.com\/elfakyn\/Vim\r\n\r\nI think I should get a job in advertising :).\r\nEnjoy!","install_details":"Place the file into ~\/.vim\/colors\/ and you're good to go!","5":"Place the file into ~\/.vim\/colors\/ and you're good to go!","first_name":"Mihai","6":"Mihai","last_name":"Popescu","7":"Popescu","releases":[{"0":"2677","vim_version":"6.0","1":"6.0","script_version":"0.4","2":"0.4","version_comment":"corrected a big small bug in the GUI version of this theme. Kinda slow, but it appears in vim 7.2 and I didn't notice it.\r\nOh yes, and now the errors are white on pink in the GUI version. It should be more obvious to the eye.","3":"corrected a big small bug in the GUI version of this theme. Kinda slow, but it appears in vim 7.2 and I didn't notice it.\r\nOh yes, and now the errors are white on pink in the GUI version. It should be more obvious to the eye.","package":"nature.vim","4":"nature.vim","src_id":"12543","5":"12543","creation_date":"1267557084","6":"1267557084"},{"0":"2677","vim_version":"6.0","1":"6.0","script_version":"0.3","2":"0.3","version_comment":"Initial upload","3":"Initial upload","package":"nature.vim","4":"nature.vim","src_id":"10827","5":"10827","creation_date":"1245009843","6":"1245009843"}]},"2676":{"script_id":"2676","0":"2676","script_name":"supercat.vim","1":"supercat.vim","script_type":"syntax","2":"syntax","summary":"Syntax for supercat configuration files","3":"Syntax for supercat configuration files","description":"Add colors to your Supercat ( http:\/\/supercat.nosredna.net ) configuration files.\r\n\r\nHere's one example of the results:\r\n\r\nhttp:\/\/img146.imageshack.us\/img146\/6496\/supercatsyntax.png\r\n\r\nOf course, you can set the colors to whatever you like.","4":"Add colors to your Supercat ( http:\/\/supercat.nosredna.net ) configuration files.\r\n\r\nHere's one example of the results:\r\n\r\nhttp:\/\/img146.imageshack.us\/img146\/6496\/supercatsyntax.png\r\n\r\nOf course, you can set the colors to whatever you like.","install_details":"1 - Put the supercat.vim file in to your $HOME\/.vim\/after\/syntax directory. \r\n2 - Put this line in to your $HOME\/.vimrc: \r\n\r\n     set syntax on \r\n\r\n3 - Put the following line in your supercat config file: \r\n\r\n     # vim: filetype=supercat\r\n\r\n4 - Quit and restart vim","5":"1 - Put the supercat.vim file in to your $HOME\/.vim\/after\/syntax directory. \r\n2 - Put this line in to your $HOME\/.vimrc: \r\n\r\n     set syntax on \r\n\r\n3 - Put the following line in your supercat config file: \r\n\r\n     # vim: filetype=supercat\r\n\r\n4 - Quit and restart vim","first_name":"Gnosis","6":"Gnosis","last_name":"Ouroubouros","7":"Ouroubouros","releases":[{"0":"2676","vim_version":"7.0","1":"7.0","script_version":"1.1","2":"1.1","version_comment":"Fixed extraneous highlighting of elements that weren't part of any group.","3":"Fixed extraneous highlighting of elements that weren't part of any group.","package":"supercat.vim","4":"supercat.vim","src_id":"10826","5":"10826","creation_date":"1245004964","6":"1245004964"},{"0":"2676","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"supercat.vim","4":"supercat.vim","src_id":"10825","5":"10825","creation_date":"1245002298","6":"1245002298"}]},"2675":{"script_id":"2675","0":"2675","script_name":"altercmd","1":"altercmd","script_type":"utility","2":"utility","summary":"Alter built-in Ex commands by your own ones","3":"Alter built-in Ex commands by your own ones","description":"*altercmd* is a Vim plugin to provide an easy way to alternate built-in Ex\r\ncommands by user-defined Ex commands.  This plugin provides |:AlterCommand|\r\nfor this purpose.  For example, if you define :CD, a custom version of |:cd|,\r\nadd the following in your vimrc.\r\n\r\n\tAlterCommand cd  CD\r\n\r\nWith the above setting, you can use :cd as if it is :CD.  It means that :CD\r\nwill be automatically inserted if you type :cd as an Ex command, so you don't\r\nhave to type :CD to use :cd and you'll never encounter mistyping :cd and :CD.\r\n\r\n:AlterCommand also supports partial command names.  For example, |:help| can\r\nbe invoked with :h, :he, :hel or :help.\r\n\r\n\tAlterCommand h[elp]  HELP\r\n\r\nWith the above setting, you can use :h, :he, :hel and :help as if they are\r\n:HELP, your own version of :help.\r\n\r\n\r\nRequirements:\r\n- Vim 7.2 or later\r\n\r\nLatest version:\r\nhttp:\/\/github.com\/kana\/vim-altercmd\r\n\r\nDocument in HTML format:\r\nhttp:\/\/kana.github.com\/config\/vim\/altercmd.html","4":"*altercmd* is a Vim plugin to provide an easy way to alternate built-in Ex\r\ncommands by user-defined Ex commands.  This plugin provides |:AlterCommand|\r\nfor this purpose.  For example, if you define :CD, a custom version of |:cd|,\r\nadd the following in your vimrc.\r\n\r\n\tAlterCommand cd  CD\r\n\r\nWith the above setting, you can use :cd as if it is :CD.  It means that :CD\r\nwill be automatically inserted if you type :cd as an Ex command, so you don't\r\nhave to type :CD to use :cd and you'll never encounter mistyping :cd and :CD.\r\n\r\n:AlterCommand also supports partial command names.  For example, |:help| can\r\nbe invoked with :h, :he, :hel or :help.\r\n\r\n\tAlterCommand h[elp]  HELP\r\n\r\nWith the above setting, you can use :h, :he, :hel and :help as if they are\r\n:HELP, your own version of :help.\r\n\r\n\r\nRequirements:\r\n- Vim 7.2 or later\r\n\r\nLatest version:\r\nhttp:\/\/github.com\/kana\/vim-altercmd\r\n\r\nDocument in HTML format:\r\nhttp:\/\/kana.github.com\/config\/vim\/altercmd.html","install_details":"...","5":"...","first_name":"Kana","6":"Kana","last_name":"Natsuno","7":"Natsuno","releases":[{"0":"2675","vim_version":"7.0","1":"7.0","script_version":"0.0.0","2":"0.0.0","version_comment":"- Initial version.","3":"- Initial version.","package":"vim-altercmd-0.0.0.zip","4":"vim-altercmd-0.0.0.zip","src_id":"10823","5":"10823","creation_date":"1244969116","6":"1244969116"}]},"2674":{"script_id":"2674","0":"2674","script_name":"cocoa.vim","1":"cocoa.vim","script_type":"utility","2":"utility","summary":"Plugin for Cocoa\/Objective-C development","3":"Plugin for Cocoa\/Objective-C development","description":"Cocoa.vim is a collection of scripts designed to make it easier to develop Cocoa\/Objective-C applications. It includes enhanced syntax highlighting, code completion, documentation lookup, as well as a number of other features that can be used to integrate Vim with Xcode, allowing you to essentially replace Xcode's editor with Vim.\r\n\r\nThis plugin includes the following features:\r\n\t1. Enhanced syntax highlighting \u00e2\u0080\u0094 Vim's syntax highlighting for Objective-C seemed incomplete to me, so I have added a few niceties, such as highlighting Cocoa keywords and differentiating the method name and passed objects in method calls and definitions. You can see a before & after screenshot here: http:\/\/imgur.com\/AGpoL.png\r\n\t2. Xcode-like mappings (where convenient) \u00e2\u0080\u0094 mappings such as ⌘R to build & run and ⌘0 to switch to the project window (provided you are using a GUI such as MacVim) as well as many others help to integrate Xcode and Vim.\r\n\t3. Methods, functions, and #pragma marks for the current file can be listed and navigated to with the :ListMethods command.\r\n\t4. A template of methods declared in a header file (.h) can be built in an implementation file (.m) with :BuildMethods.\r\n\t5. Cocoa and C Documentation can be looked up with the :CocoaDoc command, or with Vim's K.\r\n\t6. Code completion for classes, methods, functions, constants, types, and notifications can be invoked with <c-x><c-o>. Parameters for methods and functions are automatically converted to snippets to <tab> over if snipMate is installed.\r\n\r\nAlthough cocoa.vim is usable, it is still very much in the beta stage. In particular, code completion still needs much work to match Xcode's editor. Also, if anyone has suggestions as for how to add breakpoints or lookup header definitions from within Vim I would very much appreciate it.\r\n\r\nBug reports can be submitted on the issue tracker: http:\/\/code.google.com\/p\/cocoa-dot-vim\/issues\/list\r\nDevelopment can be followed on GitHub: http:\/\/github.com\/msanders\/cocoa.vim\r\n\r\nHope you find it useful!","4":"Cocoa.vim is a collection of scripts designed to make it easier to develop Cocoa\/Objective-C applications. It includes enhanced syntax highlighting, code completion, documentation lookup, as well as a number of other features that can be used to integrate Vim with Xcode, allowing you to essentially replace Xcode's editor with Vim.\r\n\r\nThis plugin includes the following features:\r\n\t1. Enhanced syntax highlighting \u00e2\u0080\u0094 Vim's syntax highlighting for Objective-C seemed incomplete to me, so I have added a few niceties, such as highlighting Cocoa keywords and differentiating the method name and passed objects in method calls and definitions. You can see a before & after screenshot here: http:\/\/imgur.com\/AGpoL.png\r\n\t2. Xcode-like mappings (where convenient) \u00e2\u0080\u0094 mappings such as ⌘R to build & run and ⌘0 to switch to the project window (provided you are using a GUI such as MacVim) as well as many others help to integrate Xcode and Vim.\r\n\t3. Methods, functions, and #pragma marks for the current file can be listed and navigated to with the :ListMethods command.\r\n\t4. A template of methods declared in a header file (.h) can be built in an implementation file (.m) with :BuildMethods.\r\n\t5. Cocoa and C Documentation can be looked up with the :CocoaDoc command, or with Vim's K.\r\n\t6. Code completion for classes, methods, functions, constants, types, and notifications can be invoked with <c-x><c-o>. Parameters for methods and functions are automatically converted to snippets to <tab> over if snipMate is installed.\r\n\r\nAlthough cocoa.vim is usable, it is still very much in the beta stage. In particular, code completion still needs much work to match Xcode's editor. Also, if anyone has suggestions as for how to add breakpoints or lookup header definitions from within Vim I would very much appreciate it.\r\n\r\nBug reports can be submitted on the issue tracker: http:\/\/code.google.com\/p\/cocoa-dot-vim\/issues\/list\r\nDevelopment can be followed on GitHub: http:\/\/github.com\/msanders\/cocoa.vim\r\n\r\nHope you find it useful!","install_details":"unzip cocoa.zip -d ~\/.vim\r\n:helptags ~\/.vim\/doc (to enable the help)\r\n\r\nDocumentation lookup and code completion for Cocoa.vim are currently Leopard-only (although the other parts should work on any platform).\r\n\r\nTo replace Xcode's editor with MacVim: In Xcode, go to Preferences > File Types, then expand file -> text. Click on the second column (\"Preferred Editor\") of the \"source code\" entry, select \"External editor -> other\" and navigate to MacVim.\r\n\r\nThe code completion in cocoa.vim uses snipMate (vimscript#2540), if it is installed, to allow you to conveniently <tab> over the parameters in functions and methods, so it is recommended you install that as well if you want to get the most out of this plugin.\r\n\r\nLastly, since cocoa.vim opens Cocoa documentation in the browser, you may want to see this page to remove the annoying Leopard security alert: http:\/\/tinyurl.com\/remove-annoying-alert","5":"unzip cocoa.zip -d ~\/.vim\r\n:helptags ~\/.vim\/doc (to enable the help)\r\n\r\nDocumentation lookup and code completion for Cocoa.vim are currently Leopard-only (although the other parts should work on any platform).\r\n\r\nTo replace Xcode's editor with MacVim: In Xcode, go to Preferences > File Types, then expand file -> text. Click on the second column (\"Preferred Editor\") of the \"source code\" entry, select \"External editor -> other\" and navigate to MacVim.\r\n\r\nThe code completion in cocoa.vim uses snipMate (vimscript#2540), if it is installed, to allow you to conveniently <tab> over the parameters in functions and methods, so it is recommended you install that as well if you want to get the most out of this plugin.\r\n\r\nLastly, since cocoa.vim opens Cocoa documentation in the browser, you may want to see this page to remove the annoying Leopard security alert: http:\/\/tinyurl.com\/remove-annoying-alert","first_name":"Michael","6":"Michael","last_name":"Sanders","7":"Sanders","releases":[{"0":"2674","vim_version":"7.0","1":"7.0","script_version":"0.4","2":"0.4","version_comment":"Many bug fixes and miscellaneous improvements.","3":"Many bug fixes and miscellaneous improvements.","package":"cocoa.zip","4":"cocoa.zip","src_id":"12748","5":"12748","creation_date":"1270000982","6":"1270000982"},{"0":"2674","vim_version":"7.0","1":"7.0","script_version":"0.3","2":"0.3","version_comment":"Fixed a number of bugs, and added support for the iPhone SDK and Snow Leopard.","3":"Fixed a number of bugs, and added support for the iPhone SDK and Snow Leopard.","package":"cocoa.zip","4":"cocoa.zip","src_id":"11971","5":"11971","creation_date":"1262020657","6":"1262020657"},{"0":"2674","vim_version":"7.0","1":"7.0","script_version":"0.2","2":"0.2","version_comment":"Many, many bug fixes and improvements, including multi-line message highlighting, multi-line documentation message lookup, automatic detection of ivar classes for completion, support for #pragma marks in :ListMethods, and many other things.","3":"Many, many bug fixes and improvements, including multi-line message highlighting, multi-line documentation message lookup, automatic detection of ivar classes for completion, support for #pragma marks in :ListMethods, and many other things.","package":"cocoa.zip","4":"cocoa.zip","src_id":"10919","5":"10919","creation_date":"1246477807","6":"1246477807"},{"0":"2674","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"cocoa.zip","4":"cocoa.zip","src_id":"10813","5":"10813","creation_date":"1244858241","6":"1244858241"}]},"2673":{"script_id":"2673","0":"2673","script_name":"smarttill","1":"smarttill","script_type":"utility","2":"utility","summary":"Smart motions, till before\/after a punctuation","3":"Smart motions, till before\/after a punctuation","description":"*smarttill* is a Vim plugin to provide {motion}s like |t| and |T|, but they\r\nare smarter than the built-in ones in some sense.  For example, if you edit\r\nthe following text and you want to delete a partial text from the cursor till\r\nbefore a comma, you have to type \"dt,\" (here \"|\" means the cursor position):\r\n\r\n\t\t...|Yo DJ, pump this party! ...\r\n\t\t    ^^^^^\r\n\r\nBut it's somewhat annoying to type another character to specify where the\r\ncursor should be moved to explicitly.  It's useful if there is a motion to\r\nmove the cursor till before comma, period or other punctuations without\r\nspecifying a character.  smarttill provides the features as\r\n|<Plug>(smarttill-t)| and |<Plug>(smarttill-T)|.\r\n\r\nSee also |smarttill-examples| for customization.\r\n\r\n\r\nRequirements:\r\n- Vim 7.2 or later\r\n\r\nLatest version:\r\nhttp:\/\/github.com\/kana\/vim-smarttill\r\n\r\nDocument in HTML format:\r\nhttp:\/\/kana.github.com\/config\/vim\/smarttill.html","4":"*smarttill* is a Vim plugin to provide {motion}s like |t| and |T|, but they\r\nare smarter than the built-in ones in some sense.  For example, if you edit\r\nthe following text and you want to delete a partial text from the cursor till\r\nbefore a comma, you have to type \"dt,\" (here \"|\" means the cursor position):\r\n\r\n\t\t...|Yo DJ, pump this party! ...\r\n\t\t    ^^^^^\r\n\r\nBut it's somewhat annoying to type another character to specify where the\r\ncursor should be moved to explicitly.  It's useful if there is a motion to\r\nmove the cursor till before comma, period or other punctuations without\r\nspecifying a character.  smarttill provides the features as\r\n|<Plug>(smarttill-t)| and |<Plug>(smarttill-T)|.\r\n\r\nSee also |smarttill-examples| for customization.\r\n\r\n\r\nRequirements:\r\n- Vim 7.2 or later\r\n\r\nLatest version:\r\nhttp:\/\/github.com\/kana\/vim-smarttill\r\n\r\nDocument in HTML format:\r\nhttp:\/\/kana.github.com\/config\/vim\/smarttill.html","install_details":"...","5":"...","first_name":"Kana","6":"Kana","last_name":"Natsuno","7":"Natsuno","releases":[{"0":"2673","vim_version":"7.0","1":"7.0","script_version":"0.0.0","2":"0.0.0","version_comment":"Initial upload","3":"Initial upload","package":"vim-smarttill-0.0.0.zip","4":"vim-smarttill-0.0.0.zip","src_id":"10805","5":"10805","creation_date":"1244737497","6":"1244737497"}]},"2672":{"script_id":"2672","0":"2672","script_name":"Hoogle","1":"Hoogle","script_type":"utility","2":"utility","summary":"Add commands to use Hoogle within vim","3":"Add commands to use Hoogle within vim","description":"This plugin query hoogle for you and display the results in a special window. Commands are provided to quickly open\/close the window.\r\n\r\nGitHub : https:\/\/github.com\/Twinside\/vim-hoogle","4":"This plugin query hoogle for you and display the results in a special window. Commands are provided to quickly open\/close the window.\r\n\r\nGitHub : https:\/\/github.com\/Twinside\/vim-hoogle","install_details":"Unzip Hoogle.zip in your .vim or vimfiles folder (or in your\r\nbundle directory if using pathogen)\r\n\r\nTo understand how to use it, go to :\r\n:help hoogle","5":"Unzip Hoogle.zip in your .vim or vimfiles folder (or in your\r\nbundle directory if using pathogen)\r\n\r\nTo understand how to use it, go to :\r\n:help hoogle","first_name":"Vincent","6":"Vincent","last_name":"B","7":"B","releases":[{"0":"2672","vim_version":"7.2","1":"7.2","script_version":"1.3","2":"1.3","version_comment":"Updated for latest version of Hoogle","3":"Updated for latest version of Hoogle","package":"vim-hoogle.zip","4":"vim-hoogle.zip","src_id":"15024","5":"15024","creation_date":"1297852930","6":"1297852930"},{"0":"2672","vim_version":"7.0","1":"7.0","script_version":"1.2","2":"1.2","version_comment":"Removed folding for hoogle window.","3":"Removed folding for hoogle window.","package":"Hoogle.vba","4":"Hoogle.vba","src_id":"11865","5":"11865","creation_date":"1259957798","6":"1259957798"},{"0":"2672","vim_version":"7.0","1":"7.0","script_version":"1.1","2":"1.1","version_comment":"Added automatic resize in function of hoogle result count.","3":"Added automatic resize in function of hoogle result count.","package":"Hoogle.vba","4":"Hoogle.vba","src_id":"11677","5":"11677","creation_date":"1257602023","6":"1257602023"},{"0":"2672","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"Hoogle.vba","4":"Hoogle.vba","src_id":"10803","5":"10803","creation_date":"1244725771","6":"1244725771"}]},"2671":{"script_id":"2671","0":"2671","script_name":"tango-desert.vim","1":"tango-desert.vim","script_type":"color scheme","2":"color scheme","summary":"Dark Color scheme based on tango palette and desert","3":"Dark Color scheme based on tango palette and desert","description":"This dark color scheme is based on tango color palette ( http:\/\/tango.freedesktop.org\/Tango_Icon_Theme_Guidelines#Color_Palette ) & desert color scheme by Hans Fugal.\r\n\r\nscreenshots : http:\/\/rand-tech.blogspot.com\/2009\/06\/tango-desert-colorscheme-vim.html","4":"This dark color scheme is based on tango color palette ( http:\/\/tango.freedesktop.org\/Tango_Icon_Theme_Guidelines#Color_Palette ) & desert color scheme by Hans Fugal.\r\n\r\nscreenshots : http:\/\/rand-tech.blogspot.com\/2009\/06\/tango-desert-colorscheme-vim.html","install_details":"install details\r\n=== Linux  ===\r\nmkdir ~\/.vim\/colors\r\ncp tango-desert.vim  ~\/.vim\/colors\r\n\r\n=== Windows ===\r\ncopy the file tango-desert.vim to vim7x\/colors\/\r\n\r\n=== Usage ===\r\nTo use the color scheme,\r\n:colorscheme tango-desert","5":"install details\r\n=== Linux  ===\r\nmkdir ~\/.vim\/colors\r\ncp tango-desert.vim  ~\/.vim\/colors\r\n\r\n=== Windows ===\r\ncopy the file tango-desert.vim to vim7x\/colors\/\r\n\r\n=== Usage ===\r\nTo use the color scheme,\r\n:colorscheme tango-desert","first_name":"vineeth","6":"vineeth","last_name":"n","7":"n","releases":[{"0":"2671","vim_version":"7.0","1":"7.0","script_version":"1.1","2":"1.1","version_comment":"Fix in contrast of autocomplete menu; Aluminum replaced with Plum palette colors","3":"Fix in contrast of autocomplete menu; Aluminum replaced with Plum palette colors","package":"tango-desert.vim","4":"tango-desert.vim","src_id":"10807","5":"10807","creation_date":"1244783540","6":"1244783540"},{"0":"2671","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"tango-desert.vim","4":"tango-desert.vim","src_id":"10802","5":"10802","creation_date":"1244717368","6":"1244717368"}]},"2670":{"script_id":"2670","0":"2670","script_name":"TuttiColori Colorscheme","1":"TuttiColori Colorscheme","script_type":"color scheme","2":"color scheme","summary":"A port of the Tutti Colori theme from the Espresso editor","3":"A port of the Tutti Colori theme from the Espresso editor","description":"A light, candy colored theme, ported from the default theme shipped with the Espresso editor for OS X (http:\/\/macrabbit.com\/espresso)\r\n\r\nThe canonical version is available on git-hub, with a screenshot at: http:\/\/github.com\/lygaret\/vimscripts","4":"A light, candy colored theme, ported from the default theme shipped with the Espresso editor for OS X (http:\/\/macrabbit.com\/espresso)\r\n\r\nThe canonical version is available on git-hub, with a screenshot at: http:\/\/github.com\/lygaret\/vimscripts","install_details":"","5":"","first_name":"Jon","6":"Jon","last_name":"Raphaelson","7":"Raphaelson","releases":[{"0":"2670","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"tutticolori.vim","4":"tutticolori.vim","src_id":"10785","5":"10785","creation_date":"1244532152","6":"1244532152"}]},"2669":{"script_id":"2669","0":"2669","script_name":"fastlane","1":"fastlane","script_type":"utility","2":"utility","summary":"a tool to help you quick edit and save abbreviation, snippets .etc","3":"a tool to help you quick edit and save abbreviation, snippets .etc","description":"what is ?\r\na tool to help you quick edit and save abbreviation, snippets .etc\r\n\r\nhow to install?\r\nmaybe you  want install snippetEmu first.\r\n\r\nunzip the file of you down, copy fastlane.vim to plugin directory, copy example_snippets.vim to you snippets directory if the file is not exist. write \"let g:iwn_snippet_dir = your snippets directory\"  to your  .vimrc file .  you are done!\r\n\r\noptions you can set the  .vimrc for a example:\r\nlet iwn_default_module = 'php'\r\nlet iwn_include_modules = {'php': ['javascript'], 'symfony': ['javascript', 'php']}\r\n\r\nhow to use?\r\n:IwnCreateModule test\r\ncreate a module named test\r\n\r\n:IwnUseModule test\r\nuse the  test module\r\n\r\n:IwnAddAbb hello hello, world\r\ncreate a abbreviation for \"hello, world\", try input \"hello<space>\" \r\n\r\ninput these text:\r\n  hello,world\r\n  yes\r\n  no <sni>hello<\/sni>\r\n  hello <sni><\/sni>  \r\nselect these text, and execute :IwnAddSnippet hello\r\nyou will create a snippet named hello, try input \"hello<tab>\"\r\n\r\nsome examples fo other command:\r\nIwnRemoveModule test\r\nIwnRemoveAbb hello\r\nIwnRemoveSnippet hello\r\n\r\nthat's all, fun happing!\r\n\r\n\r\n\r\n","4":"what is ?\r\na tool to help you quick edit and save abbreviation, snippets .etc\r\n\r\nhow to install?\r\nmaybe you  want install snippetEmu first.\r\n\r\nunzip the file of you down, copy fastlane.vim to plugin directory, copy example_snippets.vim to you snippets directory if the file is not exist. write \"let g:iwn_snippet_dir = your snippets directory\"  to your  .vimrc file .  you are done!\r\n\r\noptions you can set the  .vimrc for a example:\r\nlet iwn_default_module = 'php'\r\nlet iwn_include_modules = {'php': ['javascript'], 'symfony': ['javascript', 'php']}\r\n\r\nhow to use?\r\n:IwnCreateModule test\r\ncreate a module named test\r\n\r\n:IwnUseModule test\r\nuse the  test module\r\n\r\n:IwnAddAbb hello hello, world\r\ncreate a abbreviation for \"hello, world\", try input \"hello<space>\" \r\n\r\ninput these text:\r\n  hello,world\r\n  yes\r\n  no <sni>hello<\/sni>\r\n  hello <sni><\/sni>  \r\nselect these text, and execute :IwnAddSnippet hello\r\nyou will create a snippet named hello, try input \"hello<tab>\"\r\n\r\nsome examples fo other command:\r\nIwnRemoveModule test\r\nIwnRemoveAbb hello\r\nIwnRemoveSnippet hello\r\n\r\nthat's all, fun happing!\r\n\r\n\r\n\r\n","install_details":"","5":"","first_name":"dong","6":"dong","last_name":"hongbo","7":"hongbo","releases":[{"0":"2669","vim_version":"7.0","1":"7.0","script_version":"0.21","2":"0.21","version_comment":"bug fix","3":"bug fix","package":"fastlane.zip","4":"fastlane.zip","src_id":"10860","5":"10860","creation_date":"1245222727","6":"1245222727"},{"0":"2669","vim_version":"7.0","1":"7.0","script_version":"0.2","2":"0.2","version_comment":"bug fix","3":"bug fix","package":"fastlane.zip","4":"fastlane.zip","src_id":"10859","5":"10859","creation_date":"1245222387","6":"1245222387"},{"0":"2669","vim_version":"7.2","1":"7.2","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"fastlane.zip","4":"fastlane.zip","src_id":"10784","5":"10784","creation_date":"1244521281","6":"1244521281"}]},"2668":{"script_id":"2668","0":"2668","script_name":"shell_it","1":"shell_it","script_type":"ftplugin","2":"ftplugin","summary":"No use No use","3":"No use No use","description":"No use No use","4":"No use No use","install_details":"","5":"","first_name":"su","6":"su","last_name":"su","7":"su","releases":[{"0":"2668","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"shell_it.vim","4":"shell_it.vim","src_id":"10769","5":"10769","creation_date":"1244387850","6":"1244387850"}]},"2667":{"script_id":"2667","0":"2667","script_name":"setget","1":"setget","script_type":"utility","2":"utility","summary":"setter and getter for php","3":"setter and getter for php","description":"This script automatically inserts setter, getter or both for php files.\r\nJust type instance variable then :call PHP_setget() and choose from list if you want\r\nsetter, getter or both.\r\n\r\n- if you have any suggestions, bugs etc. drop me an email (it\\'s in the file)\r\n- I'd like to add more files, not just php, later\r\n","4":"This script automatically inserts setter, getter or both for php files.\r\nJust type instance variable then :call PHP_setget() and choose from list if you want\r\nsetter, getter or both.\r\n\r\n- if you have any suggestions, bugs etc. drop me an email (it\\'s in the file)\r\n- I'd like to add more files, not just php, later\r\n","install_details":"Just drop the file in the plugin directory.","5":"Just drop the file in the plugin directory.","first_name":"pete","6":"pete","last_name":"rei","7":"rei","releases":[{"0":"2667","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"setget.vim","4":"setget.vim","src_id":"10768","5":"10768","creation_date":"1244382809","6":"1244382809"}]},"2666":{"script_id":"2666","0":"2666","script_name":"Mark","1":"Mark","script_type":"utility","2":"utility","summary":"Highlight several words in different colors simultaneously. (#1238 continued)","3":"Highlight several words in different colors simultaneously. (#1238 continued)","description":"DESCRIPTION\r\nThis plugin adds mappings and a :Mark command to highlight several words in\r\ndifferent colors simultaneously, similar to the built-in 'hlsearch'\r\nhighlighting of search results and the * star command. For example, when you\r\nare browsing a big program file, you could highlight multiple identifiers in\r\nparallel. This will make it easier to trace the source code.\r\n\r\nThis is a continuation of vimscript #1238 by Yuheng Xie, who doesn't maintain\r\nhis original version anymore and recommends switching to this fork. This\r\nplugin offers the following advantages over the original:\r\n- Much faster, all colored words can now be highlighted, no more clashes with\r\n  syntax highlighting (due to use of matchadd()).\r\n- Many bug fixes.\r\n- Jumps behave like the built-in search, including wrap and error messages.\r\n- Like the built-in commands, jumps take an optional [count] to quickly skip\r\n  over some marks.\r\n- Marks can be persisted, and patterns can be added \/ subtracted from\r\n  mark highlight groups.\r\n\r\nSEE ALSO\r\n- SearchAlternatives.vim (vimscript #4146) provides mappings and commands to\r\n  add and subtract alternative branches to the current search pattern.\r\n- SearchHighlighting.vim (vimscript #4320) can change the semantics of the\r\n  start command *, extends it to visual mode (like Mark) and has auto-search\r\n  functionality which instantly highlights the word under the cursor when\r\n  typing or moving around, like in many IDEs.\r\n- MarkMarkup.vim (vimscript #5777) extends mark.vim with rendering the\r\n  highlightings as markup directly inside the text: as HTML <span> tags that\r\n  reproduce the mark's colors, or as appended numbers or symbols and a legend\r\n  to look up the mark names. Any markup-based export format can be defined.\r\n\r\nRELATED WORKS\r\n- MultipleSearch (vimscript #479) can highlight in a single window and in all\r\n  buffers, but still relies on the :syntax highlighting method, which is\r\n  slower and less reliable.\r\n- http:\/\/vim.wikia.com\/wiki\/Highlight_multiple_words offers control over the\r\n  color used by mapping the 1-9 keys on the numeric keypad, persistence, and\r\n  highlights only a single window.\r\n- highlight.vim (vimscript #1599) highlights lines or patterns of interest in\r\n  different colors, using mappings that start with CTRL-H and work on cword.\r\n- quickhl.vim (vimscript #3692) can also list the matches with colors and in\r\n  addition offers on-the-fly highlighting of the current word (like many IDEs\r\n  do).\r\n- Highlight (http:\/\/www.drchip.org\/astronaut\/vim\/index.html#HIGHLIGHT) has\r\n  commands and mappings for highlighting and searching, uses matchadd(), but\r\n  limits the scope of highlightings to the current window.\r\n- TempKeyword (vimscript #4636) is a simple plugin that can matchadd() the\r\n  word under the cursor with \\0 - \\9 mappings. (And clear with \\c0 etc.)\r\n- simple_highlighting (vimscript #4688) has commands and mappings to highlight\r\n  8 different slots in all buffers.\r\n- searchmatch (vimscript #4869) has commands and mappings for :[1,2,3]match,\r\n  in the current window only.\r\n- highlight-groups.vim (vimscript #5612) can do buffer-local as well as\r\n  tab-scoped highlighting via :syntax, and has multiple groups whose\r\n  highlighting is defined in an external CSV file.\r\n- Syntax match (vimscript #5376) provides various (color-based) shortcut\r\n  commands for :syntax match, and saves and restores those definitions, for\r\n  text and log files.\r\n- SelX (vimscript #5875) provides multiple multi-colored highlights per-tab\r\n  (that can be stored in a session), mappings that mirror the built-in search\r\n  commands, as a special feature automatically displays a Highlight Usage Map.\r\n- hi (vimscript #5887) highlights words, sentences or regular expressions\r\n  using many configured colors, and can search; also offers separate windows\r\n  for filtering and configuration editing catered towards log analysis.\r\n- vim-highlight-hero (vimscript #5922) can also highlight the current word or\r\n  selection, has some flexibility with regard to whitespace matching, is\r\n  limited to the current window.\r\n\r\nUSAGE\r\nHIGHLIGHTING\r\n<Leader>m               Mark the word under the cursor, similar to the star\r\n                        command. The next free highlight group is used.\r\n                        If already on a mark: Clear the mark, like\r\n                        <Leader>n.\r\n{Visual}<Leader>m       Mark or unmark the visual selection.\r\n{N}<Leader>m            With {N}, mark the word under the cursor with the\r\n                        named highlight group {N}. When that group is not\r\n                        empty, the word is added as an alternative match, so\r\n                        you can highlight multiple words with the same color.\r\n                        When the word is already contained in the list of\r\n                        alternatives, it is removed.\r\n\r\n                        When {N} is greater than the number of defined mark\r\n                        groups, a summary of marks is printed. Active mark\r\n                        groups are prefixed with \"*\" (or \"M*\" when there are\r\n                        M pattern alternatives), the default next group with\r\n                        \">\", the last used search with \"\/\" (like :Marks\r\n                        does). Input the mark group, accept the default with\r\n                        <CR>, or abort with <Esc> or any other key.\r\n                        This way, when unsure about which number represents\r\n                        which color, just use 99<Leader>n and pick the color\r\n                        interactively!\r\n\r\n{Visual}[N]<Leader>m    Ditto, based on the visual selection.\r\n\r\n[N]<Leader>r            Manually input a regular expression to mark.\r\n{Visual}[N]<Leader>r    Ditto, based on the visual selection.\r\n\r\n                        In accordance with the built-in star command,\r\n                        all these mappings use 'ignorecase', but not\r\n                        'smartcase'.\r\n\r\n<Leader>n               Clear the mark under the cursor.\r\n                        If not on a mark: Disable all marks, similar to\r\n                        :nohlsearch.\r\n                        Note: Marks that span multiple lines are not detected,\r\n                        so the use of <Leader>n on such a mark will\r\n                        unintentionally disable all marks! Use\r\n                        {Visual}<Leader>r or :Mark {pattern} to clear\r\n                        multi-line marks (or pass [N] if you happen to know\r\n                        the group number).\r\n{N}<Leader>n            Clear the marks represented by highlight group {N}.\r\n\r\n:{N}Mark                Clear the marks represented by highlight group {N}.\r\n:[N]Mark[!] [\/]{pattern}[\/]\r\n                        Mark or unmark {pattern}. Unless [N] is given, the\r\n                        next free highlight group is used for marking.\r\n                        With [N], mark {pattern} with the named highlight\r\n                        group [N]. When that group is not empty, the word is\r\n                        added as an alternative match, so you can highlight\r\n                        multiple words with the same color, unless [!] is\r\n                        given; then, {pattern} overrides the existing mark.\r\n                        When the word is already contained in the list of\r\n                        alternatives, it is removed.\r\n                        For implementation reasons, {pattern} cannot use the\r\n                        'smartcase' setting, only 'ignorecase'.\r\n                        Without [\/], only literal whole words are matched.\r\n                        :search-args\r\n:Mark                   Disable all marks, similar to :nohlsearch. Marks\r\n                        will automatically re-enable when a mark is added or\r\n                        removed, or a search for marks is performed.\r\n\r\n:MarkClear              Clear all marks. In contrast to disabling marks, the\r\n                        actual mark information is cleared, the next mark will\r\n                        use the first highlight group. This cannot be undone.\r\n\r\n:[N]Mark[!] \/{pattern}\/ as [name]\r\n                        Mark or unmark {pattern}, and give it [name].\r\n:{N}MarkName [name]\r\n                        Give [name] to mark group {N}.\r\n:MarkName!              Clear names for all mark groups.\r\n\r\nSEARCHING\r\n[count]*         [count]#\r\n[count]<Leader>* [count]<Leader>#\r\n[count]<Leader>\/ [count]<Leader>?\r\n                        Use these six keys to jump to the [count]'th next \/\r\n                        previous occurrence of a mark.\r\n                        You could also use Vim's \/ and ? to search, since the\r\n                        mark patterns are (optionally, see configuration)\r\n                        added to the search history, too.\r\n\r\n            Cursor over mark                    Cursor not over mark\r\n ---------------------------------------------------------------------------\r\n  <Leader>* Jump to the next occurrence of      Jump to the next occurrence of\r\n            current mark, and remember it       \"last mark\".\r\n            as \"last mark\".\r\n\r\n  <Leader>\/ Jump to the next occurrence of      Same as left.\r\n            ANY mark.\r\n\r\n   *        If <Leader>* is the most recently   Do Vim's original * command.\r\n            used, do a <Leader>*; otherwise\r\n            (<Leader>\/ is the most recently\r\n            used), do a <Leader>\/.\r\n\r\n                        Note: When the cursor is on a mark, the backwards\r\n                        search does not jump to the beginning of the current\r\n                        mark (like the built-in search), but to the previous\r\n                        mark. The entire mark text is treated as one entity.\r\n\r\n                        You can use Vim's jumplist to go back to previous\r\n                        mark matches and the position before a mark search.\r\n\r\nIf you work with multiple highlight groups and assign special meaning to them\r\n(e.g. group 1 for notable functions, 2 for variables, 3 for includes), you can\r\nuse the 1-9 keys on the numerical keypad to jump to occurrences of a\r\nparticular highlight group. With the general * and # commands above, you'd\r\nfirst need to locate a nearby occurrence of the desired highlight group if\r\nit's not the last mark used.\r\n\r\n<k1> .. <k9>            Jump to the [count]'th next occurrence of the mark\r\n                        belonging to highlight group 1..9.\r\n<C-k1> .. <C-k9>        Jump to the [count]'th previous occurrence of the mark\r\n                        belonging to highlight group 1..9.\r\n                        Note that these commands only work in GVIM or if your\r\n                        terminal sends different key codes; sadly, most still\r\n                        don't.\r\n                        https:\/\/unix.stackexchange.com\/questions\/552297\/make-gnome-terminal-send-correct-numeric-keypad-keycodes-to-vim\r\n                        The \"Num Lock\" indicator of your keyboard has\r\n                        to be ON; otherwise, the keypad is used for cursor\r\n                        movement. If the keypad doesn't work for you, you can\r\n                        still remap these mappings to alternatives; see below.\r\nAlternatively, you can set up mappings to search in a next \/ previous used\r\ngroup, see mark-group-cycle.\r\n\r\n[...]\r\nAfter a stop, retriggering the cascaded search in the same buffer and window\r\nmoves to the next used group (you can jump inside the current buffer to choose\r\na different starting point first). If you instead switch to another window or\r\nbuffer, the current mark group continues to be searched (to allow you to\r\nkeep searching for the current group in other locations, until those are all\r\nexhausted too).\r\n\r\nMARK PERSISTENCE\r\nThe marks can be kept and restored across Vim sessions, using the viminfo\r\nfile. For this to work, the \"!\" flag must be part of the 'viminfo' setting:\r\n    set viminfo^=!  \" Save and restore global variables.\r\n\r\n:MarkLoad               Restore the marks from the previous Vim session. All\r\n                        current marks are discarded.\r\n:MarkLoad {slot}        Restore the marks stored in the named {slot}. All\r\n                        current marks are discarded.\r\n\r\n:MarkSave               Save the currently defined marks (or clear the\r\n                        persisted marks if no marks are currently defined) for\r\n                        use in a future Vim session.\r\n:MarkSave {slot}        Save the currently defined marks in the named {slot}.\r\n                        If {slot} is all UPPERCASE, the marks are persisted\r\n                        and can be |:MarkLoad|ed in a future Vim session (to\r\n                        persist without closing Vim, use :wviminfo; an\r\n                        already running Vim session can import marks via\r\n                        :rviminfo followed by :MarkLoad).\r\n                        If {slot} contains lowercase letters, you can just\r\n                        recall within the current session. When no marks are\r\n                        currently defined, the {slot} is cleared.\r\n\r\nBy default, automatic persistence is enabled (so you don't need to explicitly\r\n:MarkSave), but you have to explicitly load the persisted marks in a new Vim\r\nsession via :MarkLoad, to avoid that you accidentally drag along outdated\r\nhighlightings from Vim session to session, and be surprised by the arbitrary\r\nhighlight groups and occasional appearance of forgotten marks. If you want\r\njust that though and automatically restore any marks, set g:mwAutoLoadMarks.\r\n\r\nYou can also initialize some marks (even using particular highlight groups) to\r\nstatic values, e.g. by including this in vimrc:\r\n    runtime plugin\/mark.vim\r\n    silent MarkClear\r\n    silent 5Mark foo\r\n    silent 6Mark \/bar\/\r\nOr you can define custom commands that preset certain marks:\r\n    command -bar MyMarks exe '5Mark! foo' | exe '6Mark! \/bar\/'\r\nOr a command that adds to the existing marks and then toggles them:\r\n    command -bar ToggleFooBarMarks exe 'Mark foo' | exe 'Mark \/bar\/'\r\nThe following commands help with setting these up:\r\n\r\n:MarkYankDefinitions [x]\r\n                        Place definitions for all current marks into the\r\n                        default register \/ [x], like this:\r\n                            1Mark! \/\\<foo\\>\/\r\n                            2Mark! \/bar\/\r\n                            9Mark! \/quux\/\r\n:MarkYankDefinitionsOneLiner [x]\r\n                        Like :MarkYankDefinitions, but place all definitions\r\n                        into a single line, like this:\r\n                        exe '1Mark! \/\\<foo\\>\/' | exe '2Mark! \/bar\/' | exe '9Mark! \/quux\/'\r\nAlternatively, the mark#GetDefinitionCommands(isOneLiner) function can be used\r\nto obtain a List of :Mark commands instead of using a register. With that,\r\nyou could for example build a custom alternative to :MarkSave that stores\r\nMarks in separate files (using writefile(), read by :source or even\r\nautomatically via a local vimrc plugin) instead of the viminfo file.\r\n\r\nMARK INFORMATION\r\nBoth mark-highlighting and mark-searching commands print information about\r\nthe mark and search pattern, e.g.\r\n        mark-1\/\\<pattern\\>\r\nThis is especially useful when you want to add or subtract patterns to a mark\r\nhighlight group via [N].\r\n\r\n:Marks                  List all mark highlight groups and the search patterns\r\n                        defined for them.\r\n                        The group that will be used for the next :Mark or\r\n                        <Leader>m command (with [N]) is shown with a \">\".\r\n                        The last mark used for a search (via <Leader>*) is\r\n                        shown with a \"\/\".\r\n\r\nMARK HIGHLIGHTING PALETTES\r\nThe plugin comes with three predefined palettes: original, extended, and\r\nmaximum. You can dynamically toggle between them, e.g. when you need more\r\nmarks or a different set of colors.\r\n\r\n:MarkPalette {palette}  Highlight existing and future marks with the colors\r\n                        defined in {palette}. If the new palette contains less\r\n                        mark groups than the current one, the additional marks\r\n                        are lost.\r\n                        You can use :command-completion for {palette}.\r\n\r\nSee g:mwDefaultHighlightingPalette for how to change the default palette,\r\nand mark-palette-define for how to add your own custom palettes.","4":"DESCRIPTION\r\nThis plugin adds mappings and a :Mark command to highlight several words in\r\ndifferent colors simultaneously, similar to the built-in 'hlsearch'\r\nhighlighting of search results and the * star command. For example, when you\r\nare browsing a big program file, you could highlight multiple identifiers in\r\nparallel. This will make it easier to trace the source code.\r\n\r\nThis is a continuation of vimscript #1238 by Yuheng Xie, who doesn't maintain\r\nhis original version anymore and recommends switching to this fork. This\r\nplugin offers the following advantages over the original:\r\n- Much faster, all colored words can now be highlighted, no more clashes with\r\n  syntax highlighting (due to use of matchadd()).\r\n- Many bug fixes.\r\n- Jumps behave like the built-in search, including wrap and error messages.\r\n- Like the built-in commands, jumps take an optional [count] to quickly skip\r\n  over some marks.\r\n- Marks can be persisted, and patterns can be added \/ subtracted from\r\n  mark highlight groups.\r\n\r\nSEE ALSO\r\n- SearchAlternatives.vim (vimscript #4146) provides mappings and commands to\r\n  add and subtract alternative branches to the current search pattern.\r\n- SearchHighlighting.vim (vimscript #4320) can change the semantics of the\r\n  start command *, extends it to visual mode (like Mark) and has auto-search\r\n  functionality which instantly highlights the word under the cursor when\r\n  typing or moving around, like in many IDEs.\r\n- MarkMarkup.vim (vimscript #5777) extends mark.vim with rendering the\r\n  highlightings as markup directly inside the text: as HTML <span> tags that\r\n  reproduce the mark's colors, or as appended numbers or symbols and a legend\r\n  to look up the mark names. Any markup-based export format can be defined.\r\n\r\nRELATED WORKS\r\n- MultipleSearch (vimscript #479) can highlight in a single window and in all\r\n  buffers, but still relies on the :syntax highlighting method, which is\r\n  slower and less reliable.\r\n- http:\/\/vim.wikia.com\/wiki\/Highlight_multiple_words offers control over the\r\n  color used by mapping the 1-9 keys on the numeric keypad, persistence, and\r\n  highlights only a single window.\r\n- highlight.vim (vimscript #1599) highlights lines or patterns of interest in\r\n  different colors, using mappings that start with CTRL-H and work on cword.\r\n- quickhl.vim (vimscript #3692) can also list the matches with colors and in\r\n  addition offers on-the-fly highlighting of the current word (like many IDEs\r\n  do).\r\n- Highlight (http:\/\/www.drchip.org\/astronaut\/vim\/index.html#HIGHLIGHT) has\r\n  commands and mappings for highlighting and searching, uses matchadd(), but\r\n  limits the scope of highlightings to the current window.\r\n- TempKeyword (vimscript #4636) is a simple plugin that can matchadd() the\r\n  word under the cursor with \\0 - \\9 mappings. (And clear with \\c0 etc.)\r\n- simple_highlighting (vimscript #4688) has commands and mappings to highlight\r\n  8 different slots in all buffers.\r\n- searchmatch (vimscript #4869) has commands and mappings for :[1,2,3]match,\r\n  in the current window only.\r\n- highlight-groups.vim (vimscript #5612) can do buffer-local as well as\r\n  tab-scoped highlighting via :syntax, and has multiple groups whose\r\n  highlighting is defined in an external CSV file.\r\n- Syntax match (vimscript #5376) provides various (color-based) shortcut\r\n  commands for :syntax match, and saves and restores those definitions, for\r\n  text and log files.\r\n- SelX (vimscript #5875) provides multiple multi-colored highlights per-tab\r\n  (that can be stored in a session), mappings that mirror the built-in search\r\n  commands, as a special feature automatically displays a Highlight Usage Map.\r\n- hi (vimscript #5887) highlights words, sentences or regular expressions\r\n  using many configured colors, and can search; also offers separate windows\r\n  for filtering and configuration editing catered towards log analysis.\r\n- vim-highlight-hero (vimscript #5922) can also highlight the current word or\r\n  selection, has some flexibility with regard to whitespace matching, is\r\n  limited to the current window.\r\n\r\nUSAGE\r\nHIGHLIGHTING\r\n<Leader>m               Mark the word under the cursor, similar to the star\r\n                        command. The next free highlight group is used.\r\n                        If already on a mark: Clear the mark, like\r\n                        <Leader>n.\r\n{Visual}<Leader>m       Mark or unmark the visual selection.\r\n{N}<Leader>m            With {N}, mark the word under the cursor with the\r\n                        named highlight group {N}. When that group is not\r\n                        empty, the word is added as an alternative match, so\r\n                        you can highlight multiple words with the same color.\r\n                        When the word is already contained in the list of\r\n                        alternatives, it is removed.\r\n\r\n                        When {N} is greater than the number of defined mark\r\n                        groups, a summary of marks is printed. Active mark\r\n                        groups are prefixed with \"*\" (or \"M*\" when there are\r\n                        M pattern alternatives), the default next group with\r\n                        \">\", the last used search with \"\/\" (like :Marks\r\n                        does). Input the mark group, accept the default with\r\n                        <CR>, or abort with <Esc> or any other key.\r\n                        This way, when unsure about which number represents\r\n                        which color, just use 99<Leader>n and pick the color\r\n                        interactively!\r\n\r\n{Visual}[N]<Leader>m    Ditto, based on the visual selection.\r\n\r\n[N]<Leader>r            Manually input a regular expression to mark.\r\n{Visual}[N]<Leader>r    Ditto, based on the visual selection.\r\n\r\n                        In accordance with the built-in star command,\r\n                        all these mappings use 'ignorecase', but not\r\n                        'smartcase'.\r\n\r\n<Leader>n               Clear the mark under the cursor.\r\n                        If not on a mark: Disable all marks, similar to\r\n                        :nohlsearch.\r\n                        Note: Marks that span multiple lines are not detected,\r\n                        so the use of <Leader>n on such a mark will\r\n                        unintentionally disable all marks! Use\r\n                        {Visual}<Leader>r or :Mark {pattern} to clear\r\n                        multi-line marks (or pass [N] if you happen to know\r\n                        the group number).\r\n{N}<Leader>n            Clear the marks represented by highlight group {N}.\r\n\r\n:{N}Mark                Clear the marks represented by highlight group {N}.\r\n:[N]Mark[!] [\/]{pattern}[\/]\r\n                        Mark or unmark {pattern}. Unless [N] is given, the\r\n                        next free highlight group is used for marking.\r\n                        With [N], mark {pattern} with the named highlight\r\n                        group [N]. When that group is not empty, the word is\r\n                        added as an alternative match, so you can highlight\r\n                        multiple words with the same color, unless [!] is\r\n                        given; then, {pattern} overrides the existing mark.\r\n                        When the word is already contained in the list of\r\n                        alternatives, it is removed.\r\n                        For implementation reasons, {pattern} cannot use the\r\n                        'smartcase' setting, only 'ignorecase'.\r\n                        Without [\/], only literal whole words are matched.\r\n                        :search-args\r\n:Mark                   Disable all marks, similar to :nohlsearch. Marks\r\n                        will automatically re-enable when a mark is added or\r\n                        removed, or a search for marks is performed.\r\n\r\n:MarkClear              Clear all marks. In contrast to disabling marks, the\r\n                        actual mark information is cleared, the next mark will\r\n                        use the first highlight group. This cannot be undone.\r\n\r\n:[N]Mark[!] \/{pattern}\/ as [name]\r\n                        Mark or unmark {pattern}, and give it [name].\r\n:{N}MarkName [name]\r\n                        Give [name] to mark group {N}.\r\n:MarkName!              Clear names for all mark groups.\r\n\r\nSEARCHING\r\n[count]*         [count]#\r\n[count]<Leader>* [count]<Leader>#\r\n[count]<Leader>\/ [count]<Leader>?\r\n                        Use these six keys to jump to the [count]'th next \/\r\n                        previous occurrence of a mark.\r\n                        You could also use Vim's \/ and ? to search, since the\r\n                        mark patterns are (optionally, see configuration)\r\n                        added to the search history, too.\r\n\r\n            Cursor over mark                    Cursor not over mark\r\n ---------------------------------------------------------------------------\r\n  <Leader>* Jump to the next occurrence of      Jump to the next occurrence of\r\n            current mark, and remember it       \"last mark\".\r\n            as \"last mark\".\r\n\r\n  <Leader>\/ Jump to the next occurrence of      Same as left.\r\n            ANY mark.\r\n\r\n   *        If <Leader>* is the most recently   Do Vim's original * command.\r\n            used, do a <Leader>*; otherwise\r\n            (<Leader>\/ is the most recently\r\n            used), do a <Leader>\/.\r\n\r\n                        Note: When the cursor is on a mark, the backwards\r\n                        search does not jump to the beginning of the current\r\n                        mark (like the built-in search), but to the previous\r\n                        mark. The entire mark text is treated as one entity.\r\n\r\n                        You can use Vim's jumplist to go back to previous\r\n                        mark matches and the position before a mark search.\r\n\r\nIf you work with multiple highlight groups and assign special meaning to them\r\n(e.g. group 1 for notable functions, 2 for variables, 3 for includes), you can\r\nuse the 1-9 keys on the numerical keypad to jump to occurrences of a\r\nparticular highlight group. With the general * and # commands above, you'd\r\nfirst need to locate a nearby occurrence of the desired highlight group if\r\nit's not the last mark used.\r\n\r\n<k1> .. <k9>            Jump to the [count]'th next occurrence of the mark\r\n                        belonging to highlight group 1..9.\r\n<C-k1> .. <C-k9>        Jump to the [count]'th previous occurrence of the mark\r\n                        belonging to highlight group 1..9.\r\n                        Note that these commands only work in GVIM or if your\r\n                        terminal sends different key codes; sadly, most still\r\n                        don't.\r\n                        https:\/\/unix.stackexchange.com\/questions\/552297\/make-gnome-terminal-send-correct-numeric-keypad-keycodes-to-vim\r\n                        The \"Num Lock\" indicator of your keyboard has\r\n                        to be ON; otherwise, the keypad is used for cursor\r\n                        movement. If the keypad doesn't work for you, you can\r\n                        still remap these mappings to alternatives; see below.\r\nAlternatively, you can set up mappings to search in a next \/ previous used\r\ngroup, see mark-group-cycle.\r\n\r\n[...]\r\nAfter a stop, retriggering the cascaded search in the same buffer and window\r\nmoves to the next used group (you can jump inside the current buffer to choose\r\na different starting point first). If you instead switch to another window or\r\nbuffer, the current mark group continues to be searched (to allow you to\r\nkeep searching for the current group in other locations, until those are all\r\nexhausted too).\r\n\r\nMARK PERSISTENCE\r\nThe marks can be kept and restored across Vim sessions, using the viminfo\r\nfile. For this to work, the \"!\" flag must be part of the 'viminfo' setting:\r\n    set viminfo^=!  \" Save and restore global variables.\r\n\r\n:MarkLoad               Restore the marks from the previous Vim session. All\r\n                        current marks are discarded.\r\n:MarkLoad {slot}        Restore the marks stored in the named {slot}. All\r\n                        current marks are discarded.\r\n\r\n:MarkSave               Save the currently defined marks (or clear the\r\n                        persisted marks if no marks are currently defined) for\r\n                        use in a future Vim session.\r\n:MarkSave {slot}        Save the currently defined marks in the named {slot}.\r\n                        If {slot} is all UPPERCASE, the marks are persisted\r\n                        and can be |:MarkLoad|ed in a future Vim session (to\r\n                        persist without closing Vim, use :wviminfo; an\r\n                        already running Vim session can import marks via\r\n                        :rviminfo followed by :MarkLoad).\r\n                        If {slot} contains lowercase letters, you can just\r\n                        recall within the current session. When no marks are\r\n                        currently defined, the {slot} is cleared.\r\n\r\nBy default, automatic persistence is enabled (so you don't need to explicitly\r\n:MarkSave), but you have to explicitly load the persisted marks in a new Vim\r\nsession via :MarkLoad, to avoid that you accidentally drag along outdated\r\nhighlightings from Vim session to session, and be surprised by the arbitrary\r\nhighlight groups and occasional appearance of forgotten marks. If you want\r\njust that though and automatically restore any marks, set g:mwAutoLoadMarks.\r\n\r\nYou can also initialize some marks (even using particular highlight groups) to\r\nstatic values, e.g. by including this in vimrc:\r\n    runtime plugin\/mark.vim\r\n    silent MarkClear\r\n    silent 5Mark foo\r\n    silent 6Mark \/bar\/\r\nOr you can define custom commands that preset certain marks:\r\n    command -bar MyMarks exe '5Mark! foo' | exe '6Mark! \/bar\/'\r\nOr a command that adds to the existing marks and then toggles them:\r\n    command -bar ToggleFooBarMarks exe 'Mark foo' | exe 'Mark \/bar\/'\r\nThe following commands help with setting these up:\r\n\r\n:MarkYankDefinitions [x]\r\n                        Place definitions for all current marks into the\r\n                        default register \/ [x], like this:\r\n                            1Mark! \/\\<foo\\>\/\r\n                            2Mark! \/bar\/\r\n                            9Mark! \/quux\/\r\n:MarkYankDefinitionsOneLiner [x]\r\n                        Like :MarkYankDefinitions, but place all definitions\r\n                        into a single line, like this:\r\n                        exe '1Mark! \/\\<foo\\>\/' | exe '2Mark! \/bar\/' | exe '9Mark! \/quux\/'\r\nAlternatively, the mark#GetDefinitionCommands(isOneLiner) function can be used\r\nto obtain a List of :Mark commands instead of using a register. With that,\r\nyou could for example build a custom alternative to :MarkSave that stores\r\nMarks in separate files (using writefile(), read by :source or even\r\nautomatically via a local vimrc plugin) instead of the viminfo file.\r\n\r\nMARK INFORMATION\r\nBoth mark-highlighting and mark-searching commands print information about\r\nthe mark and search pattern, e.g.\r\n        mark-1\/\\<pattern\\>\r\nThis is especially useful when you want to add or subtract patterns to a mark\r\nhighlight group via [N].\r\n\r\n:Marks                  List all mark highlight groups and the search patterns\r\n                        defined for them.\r\n                        The group that will be used for the next :Mark or\r\n                        <Leader>m command (with [N]) is shown with a \">\".\r\n                        The last mark used for a search (via <Leader>*) is\r\n                        shown with a \"\/\".\r\n\r\nMARK HIGHLIGHTING PALETTES\r\nThe plugin comes with three predefined palettes: original, extended, and\r\nmaximum. You can dynamically toggle between them, e.g. when you need more\r\nmarks or a different set of colors.\r\n\r\n:MarkPalette {palette}  Highlight existing and future marks with the colors\r\n                        defined in {palette}. If the new palette contains less\r\n                        mark groups than the current one, the additional marks\r\n                        are lost.\r\n                        You can use :command-completion for {palette}.\r\n\r\nSee g:mwDefaultHighlightingPalette for how to change the default palette,\r\nand mark-palette-define for how to add your own custom palettes.","install_details":"INSTALLATION\r\nThe code is hosted in a Git repo at\r\n    https:\/\/github.com\/inkarkat\/vim-mark\r\nYou can use your favorite plugin manager, or \"git clone\" into a directory used\r\nfor Vim packages. Releases are on the \"stable\" branch, the latest unstable\r\ndevelopment snapshot on \"master\".\r\n\r\nThis script is also packaged as a vimball. If you have the \"gunzip\"\r\ndecompressor in your PATH, simply edit the *.vmb.gz package in Vim; otherwise,\r\ndecompress the archive first, e.g. using WinZip. Inside Vim, install by\r\nsourcing the vimball or via the :UseVimball command.\r\n    vim mark*.vmb.gz\r\n    :so %\r\nTo uninstall, use the :RmVimball command.\r\n\r\nDEPENDENCIES\r\n- Requires Vim 7.1 with matchadd(), or Vim 7.2 or higher.\r\n- Requires the ingo-library.vim plugin (vimscript #4433), version 1.043 or\r\n  higher.\r\n\r\nCONFIGURATION\r\nFor a permanent configuration, put the following commands into your vimrc.\r\n\r\nThis plugin defines 6 mark groups:\r\n    1: Cyan  2:Green  3:Yellow  4:Red  5:Magenta  6:Blue\r\nHigher numbers always take precedence and are displayed above lower ones.\r\n\r\nEspecially if you use GVIM, you can switch to a richer palette of up to 18\r\ncolors:\r\n    let g:mwDefaultHighlightingPalette = 'extended'\r\nOr, if you have both good eyes and display, you can try a palette that defines\r\n27, 58, or even 77 colors, depending on the number of available colors:\r\n    let g:mwDefaultHighlightingPalette = 'maximum'\r\nNote: This only works for built-in palettes and those that you define prior to\r\nrunning the plugin. If you extend the built-ins after plugin initialization\r\n(mark-palette-define), use :MarkPalette instead.\r\n\r\nIf you like the additional colors, but don't need that many of them, restrict\r\ntheir number via:\r\n        let g:mwDefaultHighlightingNum = 9\r\n\r\nIf none of the default highlightings suits you, define your own colors in your\r\nvimrc file (or anywhere before this plugin is sourced, but after any\r\n:colorscheme), in the following form (where N = 1..):\r\n    highlight MarkWordN ctermbg=Cyan ctermfg=Black guibg=#8CCBEA guifg=Black\r\nYou can also use this form to redefine only some of the default highlightings.\r\nIf you want to avoid losing the highlightings on :colorscheme commands, you\r\nneed to re-apply your highlights on the ColorScheme event, similar to how\r\nthis plugin does. Or you define the palette not via :highlight commands, but\r\nuse the plugin's infrastructure:\r\n    let g:mwDefaultHighlightingPalette = [\r\n    \\   { 'ctermbg':'Cyan', 'ctermfg':'Black', 'guibg':'#8CCBEA', 'guifg':'Black' },\r\n    \\   ...\r\n    \\]\r\n\r\nIf you want to switch multiple palettes during runtime, you need to define\r\nthem as proper palettes.\r\na) To add your palette to the existing ones, do this _after_ the default\r\n   palette has been defined (e.g. in ~\/.vim\/after\/plugin\/mark.vim):\r\n    if ! exists('g:mwPalettes') \" (Optional) guard if the plugin isn't properly installed.\r\n        finish\r\n    endif\r\n\r\n    let g:mwPalettes['mypalette'] = [\r\n    \\   { 'ctermbg':'Cyan', 'ctermfg':'Black', 'guibg':'#8CCBEA', 'guifg':'Black' },\r\n    \\   ...\r\n    \\]\r\n    let g:mwPalettes['other'] = [ ... ]\r\n\r\n    \" Make it the default; you cannot use g:mwDefaultHighlightingPalette\r\n    here, as the Mark plugin has already been initialized:\r\n    MarkPalette mypalette\r\nb) Alternatively, you can completely override all built-in palettes in your\r\n   vimrc:\r\n    let g:mwPalettes = {\r\n    \\   'mypalette': [\r\n    \\       { 'ctermbg':'Cyan', 'ctermfg':'Black', 'guibg':'#8CCBEA', 'guifg':'Black' },\r\n    \\       ...\r\n    \\   ]\r\n    \\}\r\n\r\n    \" Make it the default:\r\n    let g:mwDefaultHighlightingPalette = 'mypalette'\r\n\r\nThe search type highlighting (in the search message) can be changed via:\r\n    highlight link SearchSpecialSearchType MoreMsg\r\n\r\nBy default, any marked words are also added to the search (\/) and input (@)\r\nhistory; if you don't want that, remove the corresponding symbols from:\r\n    let g:mwHistAdd = '\/@'\r\n\r\nTo enable the automatic restore of marks from a previous Vim session:\r\n    let g:mwAutoLoadMarks = 1\r\n\r\nTo turn off the automatic persistence of marks across Vim sessions:\r\n    let g:mwAutoSaveMarks = 0\r\nYou can still explicitly save marks via :MarkSave.\r\n\r\nIf you have set 'ignorecase', but want marks to be case-insensitive, you can\r\noverride the default behavior of using 'ignorecase' by setting:\r\n        let g:mwIgnoreCase = 0\r\n\r\nTo exclude some tab pages, windows, or buffers \/ filetypes from showing mark\r\nhighlightings (you can still \"blindly\" navigate to marks in there with the\r\ncorresponding mappings), you can define a List of expressions or Funcrefs that\r\nare evaluated in every window; if one returns 1, the window will not show\r\nmarks.\r\n    \" Don't mark temp files, Python filetype, and scratch files as defined by\r\n    \" a custom function.\r\n    let g:mwExclusionPredicates =\r\n    \\   ['expand(\"%:p\") =~# \"\/tmp\"', '&filetype == \"python\", function('ExcludeScratchFiles')]\r\n\r\nBy default, tab pages \/ windows \/ buffers that have t:nomarks \/ w:nomarks \/\r\nb:nomarks with a true value are excluded. Therefore, to suppress mark\r\nhighlighting in a buffer, you can simply\r\n    :let b:nomarks = 1\r\nIf the predicate changes after a window has already been visible, you can\r\nupdate the mark highlighting by either:\r\n- switching tab pages back and forth\r\n- toggling marks on \/ off (via <Plug>MarkToggle)\r\n- :call mark#UpdateMark() (for current buffer)\r\n- :call mark#UpdateScope() (for all windows in the current tab page)\r\n\r\nThis plugin uses matchadd() for the highlightings. Each mark group has its\r\nown priority, with higher group values having higher priority; i.e. going \"on\r\ntop\". The maximum priority (used for the last defined mark group) can be\r\nchanged via:\r\n    let g:mwMaxMatchPriority = -10\r\nFor example when another plugin or customization also uses matches and you\r\nwould like to change their relative priorities. The default is negative to\r\nstep back behind the default search highlighting.\r\n\r\nIf you want no or only a few of the available mappings, you can completely\r\nturn off the creation of the default mappings by defining:\r\n    :let g:mw_no_mappings = 1\r\nThis saves you from mapping dummy keys to all unwanted mapping targets.\r\n\r\nYou can use different mappings by mapping to the <Plug>Mark... mappings (use\r\n\":map <Plug>Mark\" to list them all) before this plugin is sourced.\r\n\r\nThere are no default mappings for toggling all marks and for the :MarkClear\r\ncommand, but you can define some yourself:\r\n    nmap <Leader>M <Plug>MarkToggle\r\n    nmap <Leader>N <Plug>MarkAllClear\r\nAs the latter is irreversible, there's also an alternative with an additional\r\nconfirmation:\r\n    nmap <Leader>N <Plug>MarkConfirmAllClear\r\n\r\nTo remove the default overriding of * and #, use:\r\n    nmap <Plug>IgnoreMarkSearchNext <Plug>MarkSearchNext\r\n    nmap <Plug>IgnoreMarkSearchPrev <Plug>MarkSearchPrev\r\n\r\nIf you don't want the * and # mappings remember the last search type and\r\ninstead always search for the next occurrence of the current mark, with a\r\nfallback to Vim's original * command, use:\r\n    nmap * <Plug>MarkSearchOrCurNext\r\n    nmap # <Plug>MarkSearchOrCurPrev\r\nOr for search for the next occurrence of any mark with fallback to *:\r\n    nmap * <Plug>MarkSearchOrAnyNext\r\n    nmap # <Plug>MarkSearchOrAnyPrev\r\n\r\nMark searches could also be combined with the built-in search. This mapping\r\noverloads the default |n|\/|N| commands to search for any mark if there is any\r\nmark defined and marks are enabled, and fall back to the default search if\r\nnot:\r\n    nmap n <Plug>MarkSearchAnyOrDefaultNext\r\n    nmap N <Plug>MarkSearchAnyOrDefaultPrev\r\n\r\nThe search mappings (*, #, etc.) interpret [count] as the number of\r\noccurrences to jump over. If you don't want to use the separate\r\nmark-keypad-searching mappings, and rather want [count] select the highlight\r\ngroup to target (and you can live with jumps restricted to the very next\r\nmatch), (re-)define to these mapping targets:\r\n    nmap * <Plug>MarkSearchGroupNext\r\n    nmap # <Plug>MarkSearchGroupPrev\r\n\r\nYou can remap the direct group searches (by default via the keypad 1-9 keys):\r\n    nmap <Leader>1  <Plug>MarkSearchGroup1Next\r\n    nmap <Leader>!  <Plug>MarkSearchGroup1Prev\r\n\r\nIf you need more \/ less groups, this can be configured via:\r\n    let g:mwDirectGroupJumpMappingNum = 20\r\nSet to 0 to completely turn off the keypad mappings. This is easier than\r\nremapping all <Plug>-mappings.\r\n\r\nAs an alternative to the direct group searches, you can also define mappings\r\nthat search a next \/ previous used group:\r\n    nmap <Leader>+* <Plug>MarkSearchUsedGroupNext\r\n    nmap <Leader>-* <Plug>MarkSearchUsedGroupPrev\r\n\r\nSome people like to create a mark based on the visual selection, like\r\nv_<Leader>m, but have whitespace in the selection match any whitespace when\r\nsearching (searching for \"hello world\" will also find \"hello<Tab>world\" as\r\nwell as \"hello\" at the end of a line, with \"world\" at the start of the next\r\nline). The Vim Tips Wiki describes such a setup for the built-in search at\r\n    http:\/\/vim.wikia.com\/wiki\/Search_for_visually_selected_text\r\nYou can achieve the same with the Mark plugin through the <Plug>MarkIWhiteSet\r\nmapping target: Using this, you can assign a new visual mode mapping <Leader>*\r\n    xmap <Leader>* <Plug>MarkIWhiteSet\r\nor override the default v_<Leader>m mapping, in case you always want this\r\nbehavior:\r\n    vmap <Plug>IgnoreMarkSet <Plug>MarkSet\r\n    xmap <Leader>m <Plug>MarkIWhiteSet\r\n\r\nINTEGRATION\r\nThe following functions offer (read-only) access to the script's internals:\r\n- mark#GetGroupNum(): number of available groups\r\n- mark#GetCount(): number of defined marks\r\n- mark#GetPattern([{index}]): search regular expression for an individual mark\r\n- mark#GetMarkNumber({pattern}, {isLiteral}, {isConsiderAlternatives}): mark\r\n  number of a pattern \/ literal text","5":"INSTALLATION\r\nThe code is hosted in a Git repo at\r\n    https:\/\/github.com\/inkarkat\/vim-mark\r\nYou can use your favorite plugin manager, or \"git clone\" into a directory used\r\nfor Vim packages. Releases are on the \"stable\" branch, the latest unstable\r\ndevelopment snapshot on \"master\".\r\n\r\nThis script is also packaged as a vimball. If you have the \"gunzip\"\r\ndecompressor in your PATH, simply edit the *.vmb.gz package in Vim; otherwise,\r\ndecompress the archive first, e.g. using WinZip. Inside Vim, install by\r\nsourcing the vimball or via the :UseVimball command.\r\n    vim mark*.vmb.gz\r\n    :so %\r\nTo uninstall, use the :RmVimball command.\r\n\r\nDEPENDENCIES\r\n- Requires Vim 7.1 with matchadd(), or Vim 7.2 or higher.\r\n- Requires the ingo-library.vim plugin (vimscript #4433), version 1.043 or\r\n  higher.\r\n\r\nCONFIGURATION\r\nFor a permanent configuration, put the following commands into your vimrc.\r\n\r\nThis plugin defines 6 mark groups:\r\n    1: Cyan  2:Green  3:Yellow  4:Red  5:Magenta  6:Blue\r\nHigher numbers always take precedence and are displayed above lower ones.\r\n\r\nEspecially if you use GVIM, you can switch to a richer palette of up to 18\r\ncolors:\r\n    let g:mwDefaultHighlightingPalette = 'extended'\r\nOr, if you have both good eyes and display, you can try a palette that defines\r\n27, 58, or even 77 colors, depending on the number of available colors:\r\n    let g:mwDefaultHighlightingPalette = 'maximum'\r\nNote: This only works for built-in palettes and those that you define prior to\r\nrunning the plugin. If you extend the built-ins after plugin initialization\r\n(mark-palette-define), use :MarkPalette instead.\r\n\r\nIf you like the additional colors, but don't need that many of them, restrict\r\ntheir number via:\r\n        let g:mwDefaultHighlightingNum = 9\r\n\r\nIf none of the default highlightings suits you, define your own colors in your\r\nvimrc file (or anywhere before this plugin is sourced, but after any\r\n:colorscheme), in the following form (where N = 1..):\r\n    highlight MarkWordN ctermbg=Cyan ctermfg=Black guibg=#8CCBEA guifg=Black\r\nYou can also use this form to redefine only some of the default highlightings.\r\nIf you want to avoid losing the highlightings on :colorscheme commands, you\r\nneed to re-apply your highlights on the ColorScheme event, similar to how\r\nthis plugin does. Or you define the palette not via :highlight commands, but\r\nuse the plugin's infrastructure:\r\n    let g:mwDefaultHighlightingPalette = [\r\n    \\   { 'ctermbg':'Cyan', 'ctermfg':'Black', 'guibg':'#8CCBEA', 'guifg':'Black' },\r\n    \\   ...\r\n    \\]\r\n\r\nIf you want to switch multiple palettes during runtime, you need to define\r\nthem as proper palettes.\r\na) To add your palette to the existing ones, do this _after_ the default\r\n   palette has been defined (e.g. in ~\/.vim\/after\/plugin\/mark.vim):\r\n    if ! exists('g:mwPalettes') \" (Optional) guard if the plugin isn't properly installed.\r\n        finish\r\n    endif\r\n\r\n    let g:mwPalettes['mypalette'] = [\r\n    \\   { 'ctermbg':'Cyan', 'ctermfg':'Black', 'guibg':'#8CCBEA', 'guifg':'Black' },\r\n    \\   ...\r\n    \\]\r\n    let g:mwPalettes['other'] = [ ... ]\r\n\r\n    \" Make it the default; you cannot use g:mwDefaultHighlightingPalette\r\n    here, as the Mark plugin has already been initialized:\r\n    MarkPalette mypalette\r\nb) Alternatively, you can completely override all built-in palettes in your\r\n   vimrc:\r\n    let g:mwPalettes = {\r\n    \\   'mypalette': [\r\n    \\       { 'ctermbg':'Cyan', 'ctermfg':'Black', 'guibg':'#8CCBEA', 'guifg':'Black' },\r\n    \\       ...\r\n    \\   ]\r\n    \\}\r\n\r\n    \" Make it the default:\r\n    let g:mwDefaultHighlightingPalette = 'mypalette'\r\n\r\nThe search type highlighting (in the search message) can be changed via:\r\n    highlight link SearchSpecialSearchType MoreMsg\r\n\r\nBy default, any marked words are also added to the search (\/) and input (@)\r\nhistory; if you don't want that, remove the corresponding symbols from:\r\n    let g:mwHistAdd = '\/@'\r\n\r\nTo enable the automatic restore of marks from a previous Vim session:\r\n    let g:mwAutoLoadMarks = 1\r\n\r\nTo turn off the automatic persistence of marks across Vim sessions:\r\n    let g:mwAutoSaveMarks = 0\r\nYou can still explicitly save marks via :MarkSave.\r\n\r\nIf you have set 'ignorecase', but want marks to be case-insensitive, you can\r\noverride the default behavior of using 'ignorecase' by setting:\r\n        let g:mwIgnoreCase = 0\r\n\r\nTo exclude some tab pages, windows, or buffers \/ filetypes from showing mark\r\nhighlightings (you can still \"blindly\" navigate to marks in there with the\r\ncorresponding mappings), you can define a List of expressions or Funcrefs that\r\nare evaluated in every window; if one returns 1, the window will not show\r\nmarks.\r\n    \" Don't mark temp files, Python filetype, and scratch files as defined by\r\n    \" a custom function.\r\n    let g:mwExclusionPredicates =\r\n    \\   ['expand(\"%:p\") =~# \"\/tmp\"', '&filetype == \"python\", function('ExcludeScratchFiles')]\r\n\r\nBy default, tab pages \/ windows \/ buffers that have t:nomarks \/ w:nomarks \/\r\nb:nomarks with a true value are excluded. Therefore, to suppress mark\r\nhighlighting in a buffer, you can simply\r\n    :let b:nomarks = 1\r\nIf the predicate changes after a window has already been visible, you can\r\nupdate the mark highlighting by either:\r\n- switching tab pages back and forth\r\n- toggling marks on \/ off (via <Plug>MarkToggle)\r\n- :call mark#UpdateMark() (for current buffer)\r\n- :call mark#UpdateScope() (for all windows in the current tab page)\r\n\r\nThis plugin uses matchadd() for the highlightings. Each mark group has its\r\nown priority, with higher group values having higher priority; i.e. going \"on\r\ntop\". The maximum priority (used for the last defined mark group) can be\r\nchanged via:\r\n    let g:mwMaxMatchPriority = -10\r\nFor example when another plugin or customization also uses matches and you\r\nwould like to change their relative priorities. The default is negative to\r\nstep back behind the default search highlighting.\r\n\r\nIf you want no or only a few of the available mappings, you can completely\r\nturn off the creation of the default mappings by defining:\r\n    :let g:mw_no_mappings = 1\r\nThis saves you from mapping dummy keys to all unwanted mapping targets.\r\n\r\nYou can use different mappings by mapping to the <Plug>Mark... mappings (use\r\n\":map <Plug>Mark\" to list them all) before this plugin is sourced.\r\n\r\nThere are no default mappings for toggling all marks and for the :MarkClear\r\ncommand, but you can define some yourself:\r\n    nmap <Leader>M <Plug>MarkToggle\r\n    nmap <Leader>N <Plug>MarkAllClear\r\nAs the latter is irreversible, there's also an alternative with an additional\r\nconfirmation:\r\n    nmap <Leader>N <Plug>MarkConfirmAllClear\r\n\r\nTo remove the default overriding of * and #, use:\r\n    nmap <Plug>IgnoreMarkSearchNext <Plug>MarkSearchNext\r\n    nmap <Plug>IgnoreMarkSearchPrev <Plug>MarkSearchPrev\r\n\r\nIf you don't want the * and # mappings remember the last search type and\r\ninstead always search for the next occurrence of the current mark, with a\r\nfallback to Vim's original * command, use:\r\n    nmap * <Plug>MarkSearchOrCurNext\r\n    nmap # <Plug>MarkSearchOrCurPrev\r\nOr for search for the next occurrence of any mark with fallback to *:\r\n    nmap * <Plug>MarkSearchOrAnyNext\r\n    nmap # <Plug>MarkSearchOrAnyPrev\r\n\r\nMark searches could also be combined with the built-in search. This mapping\r\noverloads the default |n|\/|N| commands to search for any mark if there is any\r\nmark defined and marks are enabled, and fall back to the default search if\r\nnot:\r\n    nmap n <Plug>MarkSearchAnyOrDefaultNext\r\n    nmap N <Plug>MarkSearchAnyOrDefaultPrev\r\n\r\nThe search mappings (*, #, etc.) interpret [count] as the number of\r\noccurrences to jump over. If you don't want to use the separate\r\nmark-keypad-searching mappings, and rather want [count] select the highlight\r\ngroup to target (and you can live with jumps restricted to the very next\r\nmatch), (re-)define to these mapping targets:\r\n    nmap * <Plug>MarkSearchGroupNext\r\n    nmap # <Plug>MarkSearchGroupPrev\r\n\r\nYou can remap the direct group searches (by default via the keypad 1-9 keys):\r\n    nmap <Leader>1  <Plug>MarkSearchGroup1Next\r\n    nmap <Leader>!  <Plug>MarkSearchGroup1Prev\r\n\r\nIf you need more \/ less groups, this can be configured via:\r\n    let g:mwDirectGroupJumpMappingNum = 20\r\nSet to 0 to completely turn off the keypad mappings. This is easier than\r\nremapping all <Plug>-mappings.\r\n\r\nAs an alternative to the direct group searches, you can also define mappings\r\nthat search a next \/ previous used group:\r\n    nmap <Leader>+* <Plug>MarkSearchUsedGroupNext\r\n    nmap <Leader>-* <Plug>MarkSearchUsedGroupPrev\r\n\r\nSome people like to create a mark based on the visual selection, like\r\nv_<Leader>m, but have whitespace in the selection match any whitespace when\r\nsearching (searching for \"hello world\" will also find \"hello<Tab>world\" as\r\nwell as \"hello\" at the end of a line, with \"world\" at the start of the next\r\nline). The Vim Tips Wiki describes such a setup for the built-in search at\r\n    http:\/\/vim.wikia.com\/wiki\/Search_for_visually_selected_text\r\nYou can achieve the same with the Mark plugin through the <Plug>MarkIWhiteSet\r\nmapping target: Using this, you can assign a new visual mode mapping <Leader>*\r\n    xmap <Leader>* <Plug>MarkIWhiteSet\r\nor override the default v_<Leader>m mapping, in case you always want this\r\nbehavior:\r\n    vmap <Plug>IgnoreMarkSet <Plug>MarkSet\r\n    xmap <Leader>m <Plug>MarkIWhiteSet\r\n\r\nINTEGRATION\r\nThe following functions offer (read-only) access to the script's internals:\r\n- mark#GetGroupNum(): number of available groups\r\n- mark#GetCount(): number of defined marks\r\n- mark#GetPattern([{index}]): search regular expression for an individual mark\r\n- mark#GetMarkNumber({pattern}, {isLiteral}, {isConsiderAlternatives}): mark\r\n  number of a pattern \/ literal text","first_name":"Ingo","6":"Ingo","last_name":"Karkat","7":"Karkat","releases":[{"0":"2666","vim_version":"7.2","1":"7.2","script_version":"3.2.0","2":"3.2.0","version_comment":"- Add mark#GetMarkNumber(), based on feedback by Snorch in #36.\r\n- Mark updates across windows now use win_execute() (since Vim 8.1.1418) instead of :windo. This hopefully addresses the changes in window sizes that have been reported (e.g. in #34).\r\n- Add <Plug>MarkSearchAnyOrDefaultNext and <Plug>MarkSearchAnyOrDefaultPrev for an any-mark search with fallback to the built-in search pattern. Suggested by Denis Kasak. *** You need to update to ingo-library (vimscript #4433) version 1.043! ***","3":"- Add mark#GetMarkNumber(), based on feedback by Snorch in #36.\r\n- Mark updates across windows now use win_execute() (since Vim 8.1.1418) instead of :windo. This hopefully addresses the changes in window sizes that have been reported (e.g. in #34).\r\n- Add <Plug>MarkSearchAnyOrDefaultNext and <Plug>MarkSearchAnyOrDefaultPrev for an any-mark search with fallback to the built-in search pattern. Suggested by Denis Kasak. *** You need to update to ingo-library (vimscript #4433) version 1.043! ***","package":"mark-3.2.0.vmb.gz","4":"mark-3.2.0.vmb.gz","src_id":"27948","5":"27948","creation_date":"1644949202","6":"1644949202"},{"0":"2666","vim_version":"7.2","1":"7.2","script_version":"3.1.1","2":"3.1.1","version_comment":"- Compatibility: After Vim 8.1.1241, a :range outside the number of buffers (e.g. :99Mark[Name]) causes an error.\r\n- ENH: Add (GUI-only) additional palettes \"soft\" and \"softer\" that are variants of \"extended\" with less saturation \/ higher brightness of background colors (for when the default colors are too distracting).\r\n- ENH: Marks that cover multiple lines (created through a visual selection or |:Mark| \/{pattern}\/) now also can be jumped to when the cursor is not on the mark's first line. *** You need to update to ingo-library (vimscript #4433) version 1.042! ***","3":"- Compatibility: After Vim 8.1.1241, a :range outside the number of buffers (e.g. :99Mark[Name]) causes an error.\r\n- ENH: Add (GUI-only) additional palettes \"soft\" and \"softer\" that are variants of \"extended\" with less saturation \/ higher brightness of background colors (for when the default colors are too distracting).\r\n- ENH: Marks that cover multiple lines (created through a visual selection or |:Mark| \/{pattern}\/) now also can be jumped to when the cursor is not on the mark's first line. *** You need to update to ingo-library (vimscript #4433) version 1.042! ***","package":"mark-3.1.1.vmb.gz","4":"mark-3.1.1.vmb.gz","src_id":"27263","5":"27263","creation_date":"1596498321","6":"1596498321"},{"0":"2666","vim_version":"7.2","1":"7.2","script_version":"3.1.0","2":"3.1.0","version_comment":"- ENH: Handle magicness atoms (\\V, \\m) in regexps entered via <Leader>r or :Mark \/{pattern}\/.\r\n- ENH: Choose a more correct insertion point with multiple alternatives for a mark by projecting the length of the existing and alternatives and the added pattern.\r\n- BUG: Regression: <Leader>n without {N} and not on an existing mark prints error \"Do not pass empty pattern to disable all marks\".\r\n- ENH: Allow to exclude certain tab pages, windows, or buffers \/ filetypes from showing mark highlightings via g:mwExclusionPredicates or (with the default predicate) t:nomarks \/ w:nomarks \/ b:nomarks flags.\r\n- ENH: Allow to tweak the maximum match priority via g:mwMaxMatchPriority for better coexistence with other customizations that use :match \/ matchadd().\r\n- ENH: Allow to disable all default mappings via a single g:mw_no_mappings configuration flag.\r\n- ENH: Appended (strong) green and yellow highlightings to the extended palette.\r\n- Refactoring: Move mark persistence implementation to ingo-library. No need to serialize into String type for viminfo beyond Vim 7.3.030.\r\n- BUG: Avoid creating jump when updating marks. Need to use :keepjumps windo. Reported by epheien. *** You need to update to ingo-library (vimscript #4433) version 1.036! ***","3":"- ENH: Handle magicness atoms (\\V, \\m) in regexps entered via <Leader>r or :Mark \/{pattern}\/.\r\n- ENH: Choose a more correct insertion point with multiple alternatives for a mark by projecting the length of the existing and alternatives and the added pattern.\r\n- BUG: Regression: <Leader>n without {N} and not on an existing mark prints error \"Do not pass empty pattern to disable all marks\".\r\n- ENH: Allow to exclude certain tab pages, windows, or buffers \/ filetypes from showing mark highlightings via g:mwExclusionPredicates or (with the default predicate) t:nomarks \/ w:nomarks \/ b:nomarks flags.\r\n- ENH: Allow to tweak the maximum match priority via g:mwMaxMatchPriority for better coexistence with other customizations that use :match \/ matchadd().\r\n- ENH: Allow to disable all default mappings via a single g:mw_no_mappings configuration flag.\r\n- ENH: Appended (strong) green and yellow highlightings to the extended palette.\r\n- Refactoring: Move mark persistence implementation to ingo-library. No need to serialize into String type for viminfo beyond Vim 7.3.030.\r\n- BUG: Avoid creating jump when updating marks. Need to use :keepjumps windo. Reported by epheien. *** You need to update to ingo-library (vimscript #4433) version 1.036! ***","package":"mark-3.1.0.vmb.gz","4":"mark-3.1.0.vmb.gz","src_id":"26431","5":"26431","creation_date":"1553398352","6":"1553398352"},{"0":"2666","vim_version":"7.0","1":"7.0","script_version":"3.0.0","2":"3.0.0","version_comment":"- CHG: Parse :Mark arguments as either \/{pattern}\/ or whole {word}. This better addresses the common use case of searching for whole words, and is consistent with built-in commands like :djump.\r\n- ENH: Keep previous (last accessed) window on :windo.\r\n- Consistently use :noautocmd during window iteration.\r\n- ENH: Add :MarkYankDefinitions and :MarkYankDefinitionsOneLiner commands. These make it easier to persist marks for specific files (e.g. by putting the :Mark commands into a local vimrc) or occasions (by defining a custom command or mapping with these commands), and are an alternative to :MarkSave\/Load.\r\n- ENH: Add <Plug>MarkSearchUsedGroupNext and <Plug>MarkSearchUsedGroupPrev to search in a next \/ previous used group. Suggested by Louis Pan.\r\n- ENH: Add <Plug>MarkSearchCascadeStartWithStop, <Plug>MarkSearchCascadeNextWithStop, <Plug>MarkSearchCascadeStartNoStop, <Plug>MarkSearchCascadeNextNoStop to search in cascading mark groups, i.e. first all matches for group 1, then all for group 2, and so on.\r\n- CHG: Duplicate mark#GetNum() and mark#GetGroupNum(). Rename the former into mark#GetCount() and have it return the number of actually defined (i.e. non-empty) marks.\r\n- ENH: Allow to give names to mark groups via :MarkName and new :Mark \/{pattern}\/ as {name} command syntax. Names will be shown during searching, and persisted together with the marks. This makes it easier to handle several marks and enforce custom semantics for particular groups.\r\n- Properly abort on error by using :echoerr.\r\n- Add dependency to ingo-library (vimscript #4433). *** You need to separately install ingo-library (vimscript #4433) version 1.020 (or higher)! ***","3":"- CHG: Parse :Mark arguments as either \/{pattern}\/ or whole {word}. This better addresses the common use case of searching for whole words, and is consistent with built-in commands like :djump.\r\n- ENH: Keep previous (last accessed) window on :windo.\r\n- Consistently use :noautocmd during window iteration.\r\n- ENH: Add :MarkYankDefinitions and :MarkYankDefinitionsOneLiner commands. These make it easier to persist marks for specific files (e.g. by putting the :Mark commands into a local vimrc) or occasions (by defining a custom command or mapping with these commands), and are an alternative to :MarkSave\/Load.\r\n- ENH: Add <Plug>MarkSearchUsedGroupNext and <Plug>MarkSearchUsedGroupPrev to search in a next \/ previous used group. Suggested by Louis Pan.\r\n- ENH: Add <Plug>MarkSearchCascadeStartWithStop, <Plug>MarkSearchCascadeNextWithStop, <Plug>MarkSearchCascadeStartNoStop, <Plug>MarkSearchCascadeNextNoStop to search in cascading mark groups, i.e. first all matches for group 1, then all for group 2, and so on.\r\n- CHG: Duplicate mark#GetNum() and mark#GetGroupNum(). Rename the former into mark#GetCount() and have it return the number of actually defined (i.e. non-empty) marks.\r\n- ENH: Allow to give names to mark groups via :MarkName and new :Mark \/{pattern}\/ as {name} command syntax. Names will be shown during searching, and persisted together with the marks. This makes it easier to handle several marks and enforce custom semantics for particular groups.\r\n- Properly abort on error by using :echoerr.\r\n- Add dependency to ingo-library (vimscript #4433). *** You need to separately install ingo-library (vimscript #4433) version 1.020 (or higher)! ***","package":"mark-3.0.0.vmb.gz","4":"mark-3.0.0.vmb.gz","src_id":"25574","5":"25574","creation_date":"1505730755","6":"1505730755"},{"0":"2666","vim_version":"7.0","1":"7.0","script_version":"2.8.5","2":"2.8.5","version_comment":"- ENH: Add alternative <Plug>MarkConfirmAllClear optional command that works like <Plug>MarkAllClear, but with confirmation. Thanks to Marcelo Montu for suggesting this!","3":"- ENH: Add alternative <Plug>MarkConfirmAllClear optional command that works like <Plug>MarkAllClear, but with confirmation. Thanks to Marcelo Montu for suggesting this!","package":"mark-2.8.5.vmb.gz","4":"mark-2.8.5.vmb.gz","src_id":"22582","5":"22582","creation_date":"1414579089","6":"1414579089"},{"0":"2666","vim_version":"7.0","1":"7.0","script_version":"2.8.4","2":"2.8.4","version_comment":"- To avoid accepting an invalid regular expression (e.g. \"\\(blah\") and then causing ugly errors on every mark update, check the patterns passed by the user for validity.\r\n- CHG: The :Mark command doesn't query for a mark when the passed mark group doesn't exist (interactivity in Ex commands is unexpected). Instead, it returns an error.","3":"- To avoid accepting an invalid regular expression (e.g. \"\\(blah\") and then causing ugly errors on every mark update, check the patterns passed by the user for validity.\r\n- CHG: The :Mark command doesn't query for a mark when the passed mark group doesn't exist (interactivity in Ex commands is unexpected). Instead, it returns an error.","package":"mark-2.8.4.vmb.gz","4":"mark-2.8.4.vmb.gz","src_id":"22066","5":"22066","creation_date":"1403252606","6":"1403252606"},{"0":"2666","vim_version":"7.2","1":"7.2","script_version":"2.8.3","2":"2.8.3","version_comment":"- The additional mapping described under :help mark-whitespace-indifferent got broken again by the refactoring of mark#DoMark() on 31-Jan-2013. Finally include this in the script as <Plug>MarkIWhiteSet and mark#GetVisualSelectionAsLiteralWhitespaceIndifferentPattern(). Thanks to Greg Klein for noticing and prodding me to include it.","3":"- The additional mapping described under :help mark-whitespace-indifferent got broken again by the refactoring of mark#DoMark() on 31-Jan-2013. Finally include this in the script as <Plug>MarkIWhiteSet and mark#GetVisualSelectionAsLiteralWhitespaceIndifferentPattern(). Thanks to Greg Klein for noticing and prodding me to include it.","package":"mark-2.8.3.vmb.gz","4":"mark-2.8.3.vmb.gz","src_id":"21926","5":"21926","creation_date":"1400841277","6":"1400841277"},{"0":"2666","vim_version":"7.2","1":"7.2","script_version":"2.8.2","2":"2.8.2","version_comment":"- BUG: :Mark cannot highlight patterns starting with a number. Use -range=0 instead of -count. Thanks to Vladimir Marek for reporting this.","3":"- BUG: :Mark cannot highlight patterns starting with a number. Use -range=0 instead of -count. Thanks to Vladimir Marek for reporting this.","package":"mark-2.8.2.vmb.gz","4":"mark-2.8.2.vmb.gz","src_id":"21202","5":"21202","creation_date":"1387230806","6":"1387230806"},{"0":"2666","vim_version":"7.2","1":"7.2","script_version":"2.8.1","2":"2.8.1","version_comment":"- Allow to override the adding to existing marks via :[N]Mark! {pattern}.\r\n- ENH: Implement command completion for :[N]Mark that offers existing mark patterns (from group [N] \/ all groups), both as one regular expression and individual alternatives. The leading \\< can be omitted.","3":"- Allow to override the adding to existing marks via :[N]Mark! {pattern}.\r\n- ENH: Implement command completion for :[N]Mark that offers existing mark patterns (from group [N] \/ all groups), both as one regular expression and individual alternatives. The leading \\< can be omitted.","package":"mark-2.8.1.vmb.gz","4":"mark-2.8.1.vmb.gz","src_id":"21093","5":"21093","creation_date":"1385133593","6":"1385133593"},{"0":"2666","vim_version":"7.2","1":"7.2","script_version":"2.8.0","2":"2.8.0","version_comment":"- Also allow a [count] for <Leader>r to select (or query for) a mark group, as with <Leader>m.\r\n- CHG: Also set the current mark to the used mark group when a mark was set via <Leader>r and :Mark so that it is easier to determine whether the entered pattern actually matches anywhere. Thanks to Xiaopan Zhang for notifying me about this problem.\r\n- Add <Plug>MarkSearchGroupNext \/ <Plug>MarkSearchGroupPrev to enable searching for particular mark groups. Thanks to Xiaopan Zhang for the suggestion.\r\n- Define default mappings for keys 1-9 on the numerical keypad to jump to a particular group (backwards with <C-kN>). Their definition is controlled by the new g:mwDirectGroupJumpMappingNum variable.\r\n- ENH: Allow to store an arbitrary number of marks via named slots that can optionally be passed to :MarkLoad \/ :MarkSave. If the slot is all-uppercase, the marks will also be persisted across Vim invocations.","3":"- Also allow a [count] for <Leader>r to select (or query for) a mark group, as with <Leader>m.\r\n- CHG: Also set the current mark to the used mark group when a mark was set via <Leader>r and :Mark so that it is easier to determine whether the entered pattern actually matches anywhere. Thanks to Xiaopan Zhang for notifying me about this problem.\r\n- Add <Plug>MarkSearchGroupNext \/ <Plug>MarkSearchGroupPrev to enable searching for particular mark groups. Thanks to Xiaopan Zhang for the suggestion.\r\n- Define default mappings for keys 1-9 on the numerical keypad to jump to a particular group (backwards with <C-kN>). Their definition is controlled by the new g:mwDirectGroupJumpMappingNum variable.\r\n- ENH: Allow to store an arbitrary number of marks via named slots that can optionally be passed to :MarkLoad \/ :MarkSave. If the slot is all-uppercase, the marks will also be persisted across Vim invocations.","package":"mark-2.8.0.vmb.gz","4":"mark-2.8.0.vmb.gz","src_id":"20254","5":"20254","creation_date":"1370081479","6":"1370081479"},{"0":"2666","vim_version":"7.2","1":"7.2","script_version":"2.7.2","2":"2.7.2","version_comment":"- Issue an error message \"No marks defined\" instead of moving the cursor by one character when there are no marks (e.g. initially or after :MarkClear).\r\n- Enable custom integrations via new mark#GetNum() and mark#GetPattern() functions.","3":"- Issue an error message \"No marks defined\" instead of moving the cursor by one character when there are no marks (e.g. initially or after :MarkClear).\r\n- Enable custom integrations via new mark#GetNum() and mark#GetPattern() functions.","package":"mark-2.7.2.vmb.gz","4":"mark-2.7.2.vmb.gz","src_id":"18811","5":"18811","creation_date":"1350308340","6":"1350308340"},{"0":"2666","vim_version":"7.2","1":"7.2","script_version":"2.7.1","2":"2.7.1","version_comment":"- Enable alternative * \/ # mappings that do not remember the last search type through new <Plug>MarkSearchOrCurNext, <Plug>MarkSearchOrCurPrev, <Plug>MarkSearchOrAnyNext, <Plug>MarkSearchOrAnyPrev mappings. Based on an inquiry from Kevin Huanpeng Du.","3":"- Enable alternative * \/ # mappings that do not remember the last search type through new <Plug>MarkSearchOrCurNext, <Plug>MarkSearchOrCurPrev, <Plug>MarkSearchOrAnyNext, <Plug>MarkSearchOrAnyPrev mappings. Based on an inquiry from Kevin Huanpeng Du.","package":"mark-2.7.1.vmb.gz","4":"mark-2.7.1.vmb.gz","src_id":"18598","5":"18598","creation_date":"1347632152","6":"1347632152"},{"0":"2666","vim_version":"7.2","1":"7.2","script_version":"2.7.0","2":"2.7.0","version_comment":"- ENH: Implement :MarkPalette command to switch mark highlighting on-the-fly during runtime.\r\n- Add \"maximum\" palette contributed by rockybalboa4.","3":"- ENH: Implement :MarkPalette command to switch mark highlighting on-the-fly during runtime.\r\n- Add \"maximum\" palette contributed by rockybalboa4.","package":"mark.vba.gz","4":"mark.vba.gz","src_id":"18218","5":"18218","creation_date":"1341413692","6":"1341413692"},{"0":"2666","vim_version":"7.2","1":"7.2","script_version":"2.6.5","2":"2.6.5","version_comment":"Don't define the default <Leader>m and <Leader>r mappings in select mode, just visual mode. Thanks to rockybalboa4 for pointing this out.","3":"Don't define the default <Leader>m and <Leader>r mappings in select mode, just visual mode. Thanks to rockybalboa4 for pointing this out.","package":"mark.vba.gz","4":"mark.vba.gz","src_id":"18184","5":"18184","creation_date":"1340542617","6":"1340542617"},{"0":"2666","vim_version":"7.2","1":"7.2","script_version":"2.6.4","2":"2.6.4","version_comment":"- Allow to override 'ignorecase' setting via g:mwIgnoreCase. Thanks to fanhe for the idea and sending a patch.","3":"- Allow to override 'ignorecase' setting via g:mwIgnoreCase. Thanks to fanhe for the idea and sending a patch.","package":"mark.vba.gz","4":"mark.vba.gz","src_id":"17810","5":"17810","creation_date":"1335165107","6":"1335165107"},{"0":"2666","vim_version":"7.2","1":"7.2","script_version":"2.6.3","2":"2.6.3","version_comment":"- ENH: Allow choosing of palette and limiting of default mark highlight groups via g:mwDefaultHighlightingPalette and g:mwDefaultHighlightingNum.\r\n- ENH: Offer an extended color palette in addition to the original 6-color one. Enable this via :let g:mwDefaultHighlightingPalette = \"extended\" in your vimrc.","3":"- ENH: Allow choosing of palette and limiting of default mark highlight groups via g:mwDefaultHighlightingPalette and g:mwDefaultHighlightingNum.\r\n- ENH: Offer an extended color palette in addition to the original 6-color one. Enable this via :let g:mwDefaultHighlightingPalette = \"extended\" in your vimrc.","package":"mark.vba.gz","4":"mark.vba.gz","src_id":"17666","5":"17666","creation_date":"1332851452","6":"1332851452"},{"0":"2666","vim_version":"7.2","1":"7.2","script_version":"2.6.2","2":"2.6.2","version_comment":"- ENH: When a [count] exceeding the number of available mark groups is given, a summary of marks is given and the user is asked to select a mark group. This allows to interactively choose a color via 99<Leader>m.\r\n- ENH: Include count of alternative patterns in :Marks list.\r\n- CHG: Use \">\" for next mark and \"\/\" for last search in :Marks.","3":"- ENH: When a [count] exceeding the number of available mark groups is given, a summary of marks is given and the user is asked to select a mark group. This allows to interactively choose a color via 99<Leader>m.\r\n- ENH: Include count of alternative patterns in :Marks list.\r\n- CHG: Use \">\" for next mark and \"\/\" for last search in :Marks.","package":"mark.vba.gz","4":"mark.vba.gz","src_id":"17661","5":"17661","creation_date":"1332766519","6":"1332766519"},{"0":"2666","vim_version":"7.2","1":"7.2","script_version":"2.6.1","2":"2.6.1","version_comment":"- ENH: Add :Marks command that prints all mark highlight groups and their search patterns, plus information about the current search mark, next mark group, and whether marks are disabled.\r\n- ENH: Show which mark group a pattern was set \/ added \/ removed \/ cleared.\r\n- FIX: When the cursor is positioned on the current mark, [N]<Leader>n \/ <Plug>MarkClear with [N] appended the pattern for the current mark (again and again) instead of clearing it. Must not pass current mark pattern when [N] is given.\r\n- CHG: Show mark group number in same-mark search and rename search types from \"any-mark\", \"same-mark\", and \"new-mark\" to the shorter \"mark-*\", \"mark-N\", and \"mark-N!\", respectively.","3":"- ENH: Add :Marks command that prints all mark highlight groups and their search patterns, plus information about the current search mark, next mark group, and whether marks are disabled.\r\n- ENH: Show which mark group a pattern was set \/ added \/ removed \/ cleared.\r\n- FIX: When the cursor is positioned on the current mark, [N]<Leader>n \/ <Plug>MarkClear with [N] appended the pattern for the current mark (again and again) instead of clearing it. Must not pass current mark pattern when [N] is given.\r\n- CHG: Show mark group number in same-mark search and rename search types from \"any-mark\", \"same-mark\", and \"new-mark\" to the shorter \"mark-*\", \"mark-N\", and \"mark-N!\", respectively.","package":"mark.vba.gz","4":"mark.vba.gz","src_id":"17644","5":"17644","creation_date":"1332522200","6":"1332522200"},{"0":"2666","vim_version":"7.2","1":"7.2","script_version":"2.6.0","2":"2.6.0","version_comment":"- ENH: Allow [count] for <Leader>m and :Mark to add \/ subtract match to \/ from highlight group [count], and use [count]<Leader>n to clear only highlight group [count]. This was also requested by Philipp Marek.\r\n- FIX: :Mark and <Leader>n actually toggled marks back on when they were already off. Now, they stay off on multiple invocations. Use :call mark#Toggle() \/ <Plug>MarkToggle if you want toggling.","3":"- ENH: Allow [count] for <Leader>m and :Mark to add \/ subtract match to \/ from highlight group [count], and use [count]<Leader>n to clear only highlight group [count]. This was also requested by Philipp Marek.\r\n- FIX: :Mark and <Leader>n actually toggled marks back on when they were already off. Now, they stay off on multiple invocations. Use :call mark#Toggle() \/ <Plug>MarkToggle if you want toggling.","package":"mark.vba.gz","4":"mark.vba.gz","src_id":"17638","5":"17638","creation_date":"1332435941","6":"1332435941"},{"0":"2666","vim_version":"7.2","1":"7.2","script_version":"2.5.3","2":"2.5.3","version_comment":"- BUG: Version check mistakenly excluded Vim 7.1 versions that do have the matchadd() function. Thanks to Philipp Marek for sending a patch. ","3":"- BUG: Version check mistakenly excluded Vim 7.1 versions that do have the matchadd() function. Thanks to Philipp Marek for sending a patch. ","package":"mark.vba.gz","4":"mark.vba.gz","src_id":"17554","5":"17554","creation_date":"1330698577","6":"1330698577"},{"0":"2666","vim_version":"7.2","1":"7.2","script_version":"2.5.2","2":"2.5.2","version_comment":"Fixed various problems with wrap-around warnings: \r\n- BUG: With a single match and 'wrapscan' set, a search error was issued. \r\n- FIX: Backwards search with single match leads to wrong error message instead. \r\n- FIX: Wrong logic for determining l:isWrapped lets wrap-around go undetected. ","3":"Fixed various problems with wrap-around warnings: \r\n- BUG: With a single match and 'wrapscan' set, a search error was issued. \r\n- FIX: Backwards search with single match leads to wrong error message instead. \r\n- FIX: Wrong logic for determining l:isWrapped lets wrap-around go undetected. ","package":"mark.vba.gz","4":"mark.vba.gz","src_id":"16840","5":"16840","creation_date":"1320854334","6":"1320854334"},{"0":"2666","vim_version":"7.2","1":"7.2","script_version":"2.5.1","2":"2.5.1","version_comment":"- FIX: == comparison in s:DoMark() leads to wrong regexp (\\A vs. \\a) being cleared when 'ignorecase' is set. Use case-sensitive comparison ==# instead. \r\n- Refine :MarkLoad messages \r\n- Add whitespace-indifferent visual mark configuration example. Thanks to Greg Klein for the suggestion. ","3":"- FIX: == comparison in s:DoMark() leads to wrong regexp (\\A vs. \\a) being cleared when 'ignorecase' is set. Use case-sensitive comparison ==# instead. \r\n- Refine :MarkLoad messages \r\n- Add whitespace-indifferent visual mark configuration example. Thanks to Greg Klein for the suggestion. ","package":"mark.vba.gz","4":"mark.vba.gz","src_id":"15663","5":"15663","creation_date":"1305644428","6":"1305644428"},{"0":"2666","vim_version":"7.2","1":"7.2","script_version":"2.5.0","2":"2.5.0","version_comment":"- ENH: Add explicit mark persistence via :MarkLoad and :MarkSave commands and automatic persistence via the g:mwAutoLoadMarks and g:mwAutoSaveMarks configuration flags. (Request from Mun Johl, 16-Apr-2010) \r\n- Expose toggling of mark display (keeping the mark patterns) via new <Plug>MarkToggle mapping. Offer :MarkClear command as a replacement for the old argumentless :Mark command, which now just disables, but not clears all marks. ","3":"- ENH: Add explicit mark persistence via :MarkLoad and :MarkSave commands and automatic persistence via the g:mwAutoLoadMarks and g:mwAutoSaveMarks configuration flags. (Request from Mun Johl, 16-Apr-2010) \r\n- Expose toggling of mark display (keeping the mark patterns) via new <Plug>MarkToggle mapping. Offer :MarkClear command as a replacement for the old argumentless :Mark command, which now just disables, but not clears all marks. ","package":"mark.vba.gz","4":"mark.vba.gz","src_id":"15603","5":"15603","creation_date":"1304776603","6":"1304776603"},{"0":"2666","vim_version":"7.0","1":"7.0","script_version":"2.4.4","2":"2.4.4","version_comment":"- BUG: Include trailing newline character in check for current mark, so that a mark that matches the entire line (e.g. created by V<Leader>m) can be cleared via <Leader>n. Thanks to ping for reporting this. \r\n- FIX: On overlapping marks, mark#CurrentMark() returned the lowest, not the highest visible mark. So on overlapping marks, the one that was not visible at the cursor position was removed; very confusing! Use reverse iteration order.  \r\n- FIX: To avoid an arbitrary ordering of highlightings when the highlighting group names roll over, and to avoid order inconsistencies across different windows and tabs, we assign a different priority based on the highlighting group. ","3":"- BUG: Include trailing newline character in check for current mark, so that a mark that matches the entire line (e.g. created by V<Leader>m) can be cleared via <Leader>n. Thanks to ping for reporting this. \r\n- FIX: On overlapping marks, mark#CurrentMark() returned the lowest, not the highest visible mark. So on overlapping marks, the one that was not visible at the cursor position was removed; very confusing! Use reverse iteration order.  \r\n- FIX: To avoid an arbitrary ordering of highlightings when the highlighting group names roll over, and to avoid order inconsistencies across different windows and tabs, we assign a different priority based on the highlighting group. ","package":"mark.vba.gz","4":"mark.vba.gz","src_id":"15477","5":"15477","creation_date":"1303193550","6":"1303193550"},{"0":"2666","vim_version":"7.0","1":"7.0","script_version":"2.4.3","2":"2.4.3","version_comment":"- Avoid losing the mark highlightings on :syn on or :colorscheme commands. Thanks to Zhou YiChao for alerting me to this issue and suggesting a fix. \r\n- Made the script more robust when somehow no highlightings have been defined or when the window-local reckoning of match IDs got lost. I had very occasionally encountered such script errors in the past. \r\n- Made global housekeeping variables script-local, only g:mwHistAdd is used for configuration. \r\n- FIX: Capturing the visual selection could still clobber the blockwise yank mode of the unnamed register. ","3":"- Avoid losing the mark highlightings on :syn on or :colorscheme commands. Thanks to Zhou YiChao for alerting me to this issue and suggesting a fix. \r\n- Made the script more robust when somehow no highlightings have been defined or when the window-local reckoning of match IDs got lost. I had very occasionally encountered such script errors in the past. \r\n- Made global housekeeping variables script-local, only g:mwHistAdd is used for configuration. \r\n- FIX: Capturing the visual selection could still clobber the blockwise yank mode of the unnamed register. ","package":"mark.vba.gz","4":"mark.vba.gz","src_id":"15459","5":"15459","creation_date":"1302984588","6":"1302984588"},{"0":"2666","vim_version":"7.2","1":"7.2","script_version":"2.4.1","2":"2.4.1","version_comment":"- FIX: Using a named register for capturing the visual selection on {Visual}<Leader>m and {Visual}<Leader>r clobbered the unnamed register. Now using the unnamed register. ","3":"- FIX: Using a named register for capturing the visual selection on {Visual}<Leader>m and {Visual}<Leader>r clobbered the unnamed register. Now using the unnamed register. ","package":"mark.vba.gz","4":"mark.vba.gz","src_id":"14741","5":"14741","creation_date":"1294930144","6":"1294930144"},{"0":"2666","vim_version":"7.0","1":"7.0","script_version":"2.4.0","2":"2.4.0","version_comment":"ENH: The MarkSearch mappings (<Leader>[*#\/?]) add the original cursor position to the jump list, like the built-in [\/?*#nN] commands. This allows to use the regular jump commands for mark matches, like with regular search matches. ","3":"ENH: The MarkSearch mappings (<Leader>[*#\/?]) add the original cursor position to the jump list, like the built-in [\/?*#nN] commands. This allows to use the regular jump commands for mark matches, like with regular search matches. ","package":"mark.vba.gz","4":"mark.vba.gz","src_id":"13424","5":"13424","creation_date":"1280385668","6":"1280385668"},{"0":"2666","vim_version":"7.0","1":"7.0","script_version":"2.3.3","2":"2.3.3","version_comment":"- BUG: Clearing of an accidental zero-width match (e.g. via :Mark \\zs) results in endless loop. Thanks to Andy Wokula for the patch. ","3":"- BUG: Clearing of an accidental zero-width match (e.g. via :Mark \\zs) results in endless loop. Thanks to Andy Wokula for the patch. ","package":"mark.vba.gz","4":"mark.vba.gz","src_id":"12423","5":"12423","creation_date":"1266580151","6":"1266580151"},{"0":"2666","vim_version":"7.0","1":"7.0","script_version":"2.3.2","2":"2.3.2","version_comment":"BUG: Creation of literal pattern via '\\V' in {Visual}<Leader>m mapping collided with individual escaping done in <Leader>m mapping so that an escaped '\\*' would be interpreted as a multi item when both modes are used for marking. Thanks to Andy Wokula for the patch. ","3":"BUG: Creation of literal pattern via '\\V' in {Visual}<Leader>m mapping collided with individual escaping done in <Leader>m mapping so that an escaped '\\*' would be interpreted as a multi item when both modes are used for marking. Thanks to Andy Wokula for the patch. ","package":"mark.vba.gz","4":"mark.vba.gz","src_id":"11744","5":"11744","creation_date":"1258447239","6":"1258447239"},{"0":"2666","vim_version":"7.0","1":"7.0","script_version":"2.3.1","2":"2.3.1","version_comment":"- Now working correctly when 'smartcase' is set. All mappings and the :Mark command use 'ignorecase', but not 'smartcase'. ","3":"- Now working correctly when 'smartcase' is set. All mappings and the :Mark command use 'ignorecase', but not 'smartcase'. ","package":"mark.vba.gz","4":"mark.vba.gz","src_id":"11122","5":"11122","creation_date":"1249300661","6":"1249300661"},{"0":"2666","vim_version":"7.0","1":"7.0","script_version":"2.3.0","2":"2.3.0","version_comment":"- All jump commands now take an optional [count], so you can quickly skip over some marks, as with the built-in *\/# and n\/N commands. For this, the entire core search algorithm has been rewritten. The script's logic has been simplified through the use of Vim 7 features like Lists. \r\n- Now also printing a Vim-alike search error message when 'nowrapscan' is set. ","3":"- All jump commands now take an optional [count], so you can quickly skip over some marks, as with the built-in *\/# and n\/N commands. For this, the entire core search algorithm has been rewritten. The script's logic has been simplified through the use of Vim 7 features like Lists. \r\n- Now also printing a Vim-alike search error message when 'nowrapscan' is set. ","package":"mark.vba.gz","4":"mark.vba.gz","src_id":"10956","5":"10956","creation_date":"1246874931","6":"1246874931"},{"0":"2666","vim_version":"7.0","1":"7.0","script_version":"2.2.0","2":"2.2.0","version_comment":"- Split off functions into autoload script. \r\n- Initialization of global variables and autocommands is now done lazily on\r\n  the first use, not during loading of the plugin. This reduces Vim startup\r\n  time and footprint as long as the functionality isn't yet used. \r\n- Split off documentation into separate help file. Now packaging as VimBall.","3":"- Split off functions into autoload script. \r\n- Initialization of global variables and autocommands is now done lazily on\r\n  the first use, not during loading of the plugin. This reduces Vim startup\r\n  time and footprint as long as the functionality isn't yet used. \r\n- Split off documentation into separate help file. Now packaging as VimBall.","package":"mark.vba.gz","4":"mark.vba.gz","src_id":"10947","5":"10947","creation_date":"1246782999","6":"1246782999"},{"0":"2666","vim_version":"7.0","1":"7.0","script_version":"2.1.0","2":"2.1.0","version_comment":"THIS VERSION REQUIRES VIM 7.2 \/ 7.1 with patches, BUT IT'S WORTH UPDATING! \r\n- Replaced highlighting via :syntax with matchadd() \/ matchdelete(). This\r\n  requires Vim 7.2 \/ 7.1 with patches. This method is faster, there are no\r\n  more clashes with syntax highlighting (:match always has preference), and\r\n  the background highlighting does not disappear under 'cursorline'. \r\n- Using winrestcmd() to fix effects of :windo: By entering a window, its\r\n  height is potentially increased from 0 to 1. \r\n- Handling multiple tabs by calling s:UpdateScope() on the TabEnter event. ","3":"THIS VERSION REQUIRES VIM 7.2 \/ 7.1 with patches, BUT IT'S WORTH UPDATING! \r\n- Replaced highlighting via :syntax with matchadd() \/ matchdelete(). This\r\n  requires Vim 7.2 \/ 7.1 with patches. This method is faster, there are no\r\n  more clashes with syntax highlighting (:match always has preference), and\r\n  the background highlighting does not disappear under 'cursorline'. \r\n- Using winrestcmd() to fix effects of :windo: By entering a window, its\r\n  height is potentially increased from 0 to 1. \r\n- Handling multiple tabs by calling s:UpdateScope() on the TabEnter event. ","package":"mark.vim","4":"mark.vim","src_id":"10928","5":"10928","creation_date":"1246536160","6":"1246536160"},{"0":"2666","vim_version":"7.0","1":"7.0","script_version":"2.0.0","2":"2.0.0","version_comment":"THIS VERSION REQUIRES VIM 7.0! \r\n- Now using Vim List for g:mwWord and thus requiring Vim 7. g:mwCycle is now zero-based, but the syntax groups \"MarkWordx\" are still one-based. \r\n- Factored :syntax operations out of s:DoMark() and s:UpdateMark() so that they can all be done in a single :windo. \r\n- Normal mode <Plug>MarkSet now has the same semantics as its visual mode cousin: If the cursor is on an existing mark, the mark is removed. Beforehand, one could only remove a visually selected mark via again selecting it. Now, one simply can invoke the mapping when on such a mark. ","3":"THIS VERSION REQUIRES VIM 7.0! \r\n- Now using Vim List for g:mwWord and thus requiring Vim 7. g:mwCycle is now zero-based, but the syntax groups \"MarkWordx\" are still one-based. \r\n- Factored :syntax operations out of s:DoMark() and s:UpdateMark() so that they can all be done in a single :windo. \r\n- Normal mode <Plug>MarkSet now has the same semantics as its visual mode cousin: If the cursor is on an existing mark, the mark is removed. Beforehand, one could only remove a visually selected mark via again selecting it. Now, one simply can invoke the mapping when on such a mark. ","package":"mark.vim","4":"mark.vim","src_id":"10774","5":"10774","creation_date":"1244454480","6":"1244454480"},{"0":"2666","vim_version":"6.0","1":"6.0","script_version":"1.6.1","2":"1.6.1","version_comment":"Initial upload","3":"Initial upload","package":"mark.vim","4":"mark.vim","src_id":"10766","5":"10766","creation_date":"1244365848","6":"1244365848"}]},"2665":{"script_id":"2665","0":"2665","script_name":"HtmlHelper","1":"HtmlHelper","script_type":"ftplugin","2":"ftplugin","summary":"Html macros and mappings","3":"Html macros and mappings","description":"\" Html macros and mappings for:\r\n\" ------------------------------------------\r\n\"\r\n\"    *  Closing        an opening tag\r\n\"    *  Wrapping     text with tags\r\n\"    *  Increasing    the weight of header tags (<h1>...)\r\n\"    *  Formatting    text inside a pair of tags\r\n\"    *  Rearranging  <tag> content <\/tag> vertically\r\n\"    *  Stripping       outer tags\r\n\"    *  'Spacing'       vertically the content of a pair of tags\r\n\"\r\n\" 1. Close an opening tag\r\n\" -----------------------\r\n\"\r\n\"     >> : <tag> newline <\/tag> (write quickly a second > after the first one)\r\n\"     >\/ : <tag>         <\/tag>\r\n\"     <? : <?php             ?>\r\n\"\r\n\" 2. Wrapping:\r\n\" ------------\r\n\"\r\n\"         +-----------+-------------------+\r\n\"         | paragraph | WORD or selection |\r\n\" +-------+-----------+-------------------+\r\n\" | <ul>  |    @u     |        \\u         |\r\n\" | <ol>  |    @o     |        \\o         |\r\n\" | <p>   |    @p     |        \\p         |\r\n\" | <div> |    @d     |        \\d         |\r\n\" +-------+-----------+-------------------+\r\n\"\r\n\" Note: \\u and \\o work on fully selected lines only\r\n\"\r\n\" Note: mnemo for paragraphs and lines: wrap @ll\r\n\"\r\n\" Note: You can use a count with the \\ mappings\r\n\"\r\n\"              +------+-------------------+\r\n\"              | line | WORD or selection |\r\n\" +------------+------+-------------------+\r\n\" | <td>       |  @t  |        \\t         |\r\n\" | <a>        |  @a  |        \\a         |\r\n\" | <span>     |  @s  |        \\s         |\r\n\" | <h1>       |  @h  |        \\h         |\r\n\" | <li>       |  @l  |        \\l         |\r\n\" | <!-- -->   |  @c  |        \\c         |\r\n\" | <em>       |  @e  |        \\e         |\r\n\" | <strong>   |  @b  |        \\b         |\r\n\" +------------+------+-------------------+\r\n\"\r\n\" 3. Insert an image\r\n\" ------------------\r\n\"\r\n\"     @i (<img src='X' alt='' title='' \/>)\r\n\"\r\n\" 4. Set the class of a tag\r\n\" -------------------------\r\n\"\r\n\"     :Class ul         -> <ul>                 (default)\r\n\"     :Class ul bg_blue -> <ul class='bg_blue'>\r\n\"\r\n\" Note: Try using :C or :Cl or... instead of :Class. Depending on the\r\n\"       installed plugins, a shorter or longer abbreviation might work.\r\n\"\r\n\" Shortcuts: (:C shortcut)\r\n\"     d,   s,    u,  o,  h,  l,  t,  i,   e,  b\r\n\"     div, span, ul, ol, h1, li, td, img, em, strong\r\n\"\r\n\" Note: If you don't want to write a tag manually, you can use <tab>\r\n\"       after :Class to autocomplete your tag.\r\n\"       (put a space after :Class before hitting <tab>)\r\n\"\r\n\" 5. <hn -> <hn+1 (Use after a @h or \\h)\r\n\" --------------------------------------\r\n\"\r\n\"     @j (mnemo: j is just besides h on the keyboard)\r\n\"\r\n\" 6. gq inside a pair of tags\r\n\" ---------------------------\r\n\"\r\n\"     @g for standard tags\r\n\"     \\g for <!-- --> or <?php ?>\r\n\"\r\n\" 7. Rearrange <tag> content <\/tag> vertically\r\n\" --------------------------------------------\r\n\"\r\n\"     @r for standard tags\r\n\"     \\r for <!-- --> or <?php ?>\r\n\"\r\n\" 8. Strip outer tags\r\n\" -------------------\r\n\"\r\n\"     @x for standard tags\r\n\"     \\x for <!-- --> or <?php ?>\r\n\"\r\n\" 9. 'Space' vertically the content of a pair of tags\r\n\" ---------------------------------------------------\r\n\"\r\n\"     @m for standard tags        (mnemo: \r\n)\r\n\"     \\m for <!-- --> or <?php ?>\r\n\"\r\n\" A detailed help is in the comments of the file itself!","4":"\" Html macros and mappings for:\r\n\" ------------------------------------------\r\n\"\r\n\"    *  Closing        an opening tag\r\n\"    *  Wrapping     text with tags\r\n\"    *  Increasing    the weight of header tags (<h1>...)\r\n\"    *  Formatting    text inside a pair of tags\r\n\"    *  Rearranging  <tag> content <\/tag> vertically\r\n\"    *  Stripping       outer tags\r\n\"    *  'Spacing'       vertically the content of a pair of tags\r\n\"\r\n\" 1. Close an opening tag\r\n\" -----------------------\r\n\"\r\n\"     >> : <tag> newline <\/tag> (write quickly a second > after the first one)\r\n\"     >\/ : <tag>         <\/tag>\r\n\"     <? : <?php             ?>\r\n\"\r\n\" 2. Wrapping:\r\n\" ------------\r\n\"\r\n\"         +-----------+-------------------+\r\n\"         | paragraph | WORD or selection |\r\n\" +-------+-----------+-------------------+\r\n\" | <ul>  |    @u     |        \\u         |\r\n\" | <ol>  |    @o     |        \\o         |\r\n\" | <p>   |    @p     |        \\p         |\r\n\" | <div> |    @d     |        \\d         |\r\n\" +-------+-----------+-------------------+\r\n\"\r\n\" Note: \\u and \\o work on fully selected lines only\r\n\"\r\n\" Note: mnemo for paragraphs and lines: wrap @ll\r\n\"\r\n\" Note: You can use a count with the \\ mappings\r\n\"\r\n\"              +------+-------------------+\r\n\"              | line | WORD or selection |\r\n\" +------------+------+-------------------+\r\n\" | <td>       |  @t  |        \\t         |\r\n\" | <a>        |  @a  |        \\a         |\r\n\" | <span>     |  @s  |        \\s         |\r\n\" | <h1>       |  @h  |        \\h         |\r\n\" | <li>       |  @l  |        \\l         |\r\n\" | <!-- -->   |  @c  |        \\c         |\r\n\" | <em>       |  @e  |        \\e         |\r\n\" | <strong>   |  @b  |        \\b         |\r\n\" +------------+------+-------------------+\r\n\"\r\n\" 3. Insert an image\r\n\" ------------------\r\n\"\r\n\"     @i (<img src='X' alt='' title='' \/>)\r\n\"\r\n\" 4. Set the class of a tag\r\n\" -------------------------\r\n\"\r\n\"     :Class ul         -> <ul>                 (default)\r\n\"     :Class ul bg_blue -> <ul class='bg_blue'>\r\n\"\r\n\" Note: Try using :C or :Cl or... instead of :Class. Depending on the\r\n\"       installed plugins, a shorter or longer abbreviation might work.\r\n\"\r\n\" Shortcuts: (:C shortcut)\r\n\"     d,   s,    u,  o,  h,  l,  t,  i,   e,  b\r\n\"     div, span, ul, ol, h1, li, td, img, em, strong\r\n\"\r\n\" Note: If you don't want to write a tag manually, you can use <tab>\r\n\"       after :Class to autocomplete your tag.\r\n\"       (put a space after :Class before hitting <tab>)\r\n\"\r\n\" 5. <hn -> <hn+1 (Use after a @h or \\h)\r\n\" --------------------------------------\r\n\"\r\n\"     @j (mnemo: j is just besides h on the keyboard)\r\n\"\r\n\" 6. gq inside a pair of tags\r\n\" ---------------------------\r\n\"\r\n\"     @g for standard tags\r\n\"     \\g for <!-- --> or <?php ?>\r\n\"\r\n\" 7. Rearrange <tag> content <\/tag> vertically\r\n\" --------------------------------------------\r\n\"\r\n\"     @r for standard tags\r\n\"     \\r for <!-- --> or <?php ?>\r\n\"\r\n\" 8. Strip outer tags\r\n\" -------------------\r\n\"\r\n\"     @x for standard tags\r\n\"     \\x for <!-- --> or <?php ?>\r\n\"\r\n\" 9. 'Space' vertically the content of a pair of tags\r\n\" ---------------------------------------------------\r\n\"\r\n\"     @m for standard tags        (mnemo: \r\n)\r\n\"     \\m for <!-- --> or <?php ?>\r\n\"\r\n\" A detailed help is in the comments of the file itself!","install_details":"HtmlHelper - Install in:\r\n\r\n              ~\/.vim\/ftplugin\/html.vim\r\n       ln -s ~\/.vim\/ftplugin\/html.vim phtml.vim\r\n       ln -s ~\/.vim\/ftplugin\/html.vim xml.vim\r\n\r\nTabular.vim: (http:\/\/github.com\/godlygeek\/tabular\/tree\/master)\r\n\r\n             ~\/.vim\/autoload\/tabular.vim\r\n             ~\/.vim\/after\/plugin\/myTabularMaps.vim (to be created, see above)\r\n             ~\/.vim\/plugin\/Tabular.vim\r\n             ~\/.vim\/plugin\/TabularMaps.vim","5":"HtmlHelper - Install in:\r\n\r\n              ~\/.vim\/ftplugin\/html.vim\r\n       ln -s ~\/.vim\/ftplugin\/html.vim phtml.vim\r\n       ln -s ~\/.vim\/ftplugin\/html.vim xml.vim\r\n\r\nTabular.vim: (http:\/\/github.com\/godlygeek\/tabular\/tree\/master)\r\n\r\n             ~\/.vim\/autoload\/tabular.vim\r\n             ~\/.vim\/after\/plugin\/myTabularMaps.vim (to be created, see above)\r\n             ~\/.vim\/plugin\/Tabular.vim\r\n             ~\/.vim\/plugin\/TabularMaps.vim","first_name":"Dimitar","6":"Dimitar","last_name":"Dimitrov","7":"Dimitrov","releases":[{"0":"2665","vim_version":"7.0","1":"7.0","script_version":"2.2","2":"2.2","version_comment":"Some minor changes","3":"Some minor changes","package":"html.vim","4":"html.vim","src_id":"13815","5":"13815","creation_date":"1284386098","6":"1284386098"},{"0":"2665","vim_version":"7.0","1":"7.0","script_version":"2.1","2":"2.1","version_comment":"@e will now correctly use the class set with :C em ...","3":"@e will now correctly use the class set with :C em ...","package":"html.vim.tar.gz","4":"html.vim.tar.gz","src_id":"11443","5":"11443","creation_date":"1254065093","6":"1254065093"},{"0":"2665","vim_version":"7.0","1":"7.0","script_version":"2.0","2":"2.0","version_comment":"Changes:\r\n\r\n    @i -> <img> instead if <i> (not valid XHTML 1.1 strict)\r\n    @b -> <strong> instead of <b> (not valid XHTML 1.1 strict)\r\n    @e -> <em>\r\n\r\n    :Class can be invoked with these shortcuts now:\r\n\r\n    d,   s,    u,  o,  h,  l,  t,  i,   e,  b\r\n    div, span, ul, ol, h1, li, td, img, em, strong\r\n\r\n    Pointed out a limitation:\r\n\r\n    7@p won't work if one of the paragraphs starts with a one letter word\r\n    (ex: I). Same for <> 7 or another macro or on words.\r\n\r\n    TODO:\r\n\r\n    <fieldset> |  @f\r\n    <kbd>      |  @k\r\n    <noscript> |  @n\r\n    <var>      |  @v\r\n\r\n    <meta>     -> @m\r\n","3":"Changes:\r\n\r\n    @i -> <img> instead if <i> (not valid XHTML 1.1 strict)\r\n    @b -> <strong> instead of <b> (not valid XHTML 1.1 strict)\r\n    @e -> <em>\r\n\r\n    :Class can be invoked with these shortcuts now:\r\n\r\n    d,   s,    u,  o,  h,  l,  t,  i,   e,  b\r\n    div, span, ul, ol, h1, li, td, img, em, strong\r\n\r\n    Pointed out a limitation:\r\n\r\n    7@p won't work if one of the paragraphs starts with a one letter word\r\n    (ex: I). Same for <> 7 or another macro or on words.\r\n\r\n    TODO:\r\n\r\n    <fieldset> |  @f\r\n    <kbd>      |  @k\r\n    <noscript> |  @n\r\n    <var>      |  @v\r\n\r\n    <meta>     -> @m\r\n","package":"html.vim","4":"html.vim","src_id":"11439","5":"11439","creation_date":"1254058442","6":"1254058442"},{"0":"2665","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"html.vim.tar.gz","4":"html.vim.tar.gz","src_id":"10765","5":"10765","creation_date":"1244364097","6":"1244364097"}]},"2663":{"script_id":"2663","0":"2663","script_name":"mako.vim","1":"mako.vim","script_type":"indent","2":"indent","summary":"Adds indenting support for Mako HTML templates","3":"Adds indenting support for Mako HTML templates","description":"Adds indenting support for the mako python template engine to vim. Indents inside of Mako control blocks, which improves the readability of the source template (although at the possible expense of the readability of the output code).\r\n\r\nFor best results, use in conjunction with mako syntax highlighting: vimscript #1858.\r\n\r\nMako: http:\/\/www.makotemplates.org\/","4":"Adds indenting support for the mako python template engine to vim. Indents inside of Mako control blocks, which improves the readability of the source template (although at the possible expense of the readability of the output code).\r\n\r\nFor best results, use in conjunction with mako syntax highlighting: vimscript #1858.\r\n\r\nMako: http:\/\/www.makotemplates.org\/","install_details":"Copy into ~\/.vim\/indent. No dependencies.","5":"Copy into ~\/.vim\/indent. No dependencies.","first_name":"Scott","6":"Scott","last_name":"Torborg","7":"Torborg","releases":[{"0":"2663","vim_version":"7.0","1":"7.0","script_version":"0.4","2":"0.4","version_comment":"- Added license information for WTFPL","3":"- Added license information for WTFPL","package":"mako.vim","4":"mako.vim","src_id":"12560","5":"12560","creation_date":"1267830255","6":"1267830255"},{"0":"2663","vim_version":"7.0","1":"7.0","script_version":"0.3","2":"0.3","version_comment":"- Added explicit support for ## comments, fixed unindenting count. Thanks to Mike Lewis (@MikeRLewis)","3":"- Added explicit support for ## comments, fixed unindenting count. Thanks to Mike Lewis (@MikeRLewis)","package":"mako.vim","4":"mako.vim","src_id":"11380","5":"11380","creation_date":"1253035558","6":"1253035558"},{"0":"2663","vim_version":"7.0","1":"7.0","script_version":"0.2","2":"0.2","version_comment":"- Fixed issue where opening and closing mako tags on the same line would cause incorrect indenting","3":"- Fixed issue where opening and closing mako tags on the same line would cause incorrect indenting","package":"mako.vim","4":"mako.vim","src_id":"10838","5":"10838","creation_date":"1245099548","6":"1245099548"},{"0":"2663","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"mako.vim","4":"mako.vim","src_id":"10749","5":"10749","creation_date":"1244263113","6":"1244263113"}]},"2662":{"script_id":"2662","0":"2662","script_name":"ywvim","1":"ywvim","script_type":"utility","2":"utility","summary":"Another input method(IM) for VIM, supports all modes.","3":"Another input method(IM) for VIM, supports all modes.","description":"介绍：\r\n======= Chinese version =======\r\n注意!!!\r\n=======\r\n如果你是 ywvim 的老用户, 在升级到新版本前, 请注意你的旧版本到新版本间*所有*的发布公告和已知 bugs, 然后查找对应设置的说明, 以免不兼容的改变给你带来不便.\r\n如果你在使用中发现了问题, 在报告之前, 请先查看下面的\"已知问题\"部分, 确定是否为已知 bug.\r\n\r\n下载最新脚本(1.33): https:\/\/www.vim.org\/scripts\/download_script.php?src_id=27354\r\n下载最新码表(1.15): https:\/\/www.vim.org\/scripts\/download_script.php?src_id=27224\r\n\r\n介绍:\r\n=====\r\nywvim 是一款不依赖外部输入法的, 在 vim 里输入中文的工具. 支持在 vim 的所有模式下输入中文. 它面向的对象主要为形码用户, 对于拼音用户, 你可以试试有更多功能的 vimim[http:\/\/www.vim.org\/scripts\/script.php?script_id=2506].\r\n坏消息: ywvim 和 vimim 的键绑定冲突, 你必须在两者中做出选择.\r\n\r\n.vimrc 里的设置:\r\n================\r\n把下面的几行放到你的 .vimrc 中:\r\n\r\n-----\r\nlet g:ywvim_ims=[ \r\n            \\['wb', '五笔', 'wubi.ywvim'], \r\n            \\['py', '拼音', 'pinyin.ywvim'], \r\n            \\['cj', '仓颉', 'cangjie.ywvim'], \r\n            \\['wb98', '五笔98', 'wubi98.ywvim'], \r\n            \\['zm', '郑码', 'zhengma.ywvim'], \r\n            \\['zy', '注音', 'zhuyin.ywvim'], \r\n            \\['ar30', '行列', 'array30.ywvim'], \r\n            \\]\r\n\r\nlet g:ywvim_py = { 'helpim':'wb', 'gb':0 }\r\n\r\nlet g:ywvim_zhpunc = 1\r\nlet g:ywvim_listmax = 5\r\nlet g:ywvim_esc_autoff = 0\r\nlet g:ywvim_autoinput = 0\r\nlet g:ywvim_intelligent_punc=1\r\nlet g:ywvim_circlecandidates = 1\r\nlet g:ywvim_helpim_on = 0\r\nlet g:ywvim_matchexact = 0\r\nlet g:ywvim_chinesecode = 1\r\nlet g:ywvim_gb = 0\r\nlet g:ywvim_preconv = 'g2b'\r\nlet g:ywvim_conv = ''\r\nlet g:ywvim_lockb = 1\r\n-----\r\n\r\n使用:\r\n=====\r\n<Ctrl-Space>, <Ctrl-Shift-Space>, <Ctrl-@>, <Ctrl-\\> 输入法开关.\r\n\r\n;(分号) 临时英文.\r\n\r\nz, ` 临时拼音.（需要输入法变量 g:ywvim_ims 里有一个 'py' 拼音简称的码表）\r\n\r\n<Ctrl-^> 设置输入法:\r\n    码表切换.\r\n    中英标点切换.\r\n    候选项个数: 候选项个数.\r\n    最大词长: 你想输入的最长的词. 设为 1 为单字模试.\r\n    简繁转换开关.\r\n    只输入GB2312.\r\n    辅助编码提示开关.\r\n\r\n,.-=    上下翻页.\r\n\r\n空格或数字选字, 回车输英文.\r\n; 分号选择第二候选词. (感谢在 www.newsmth.net 的 vace 的建议.)\r\n\r\n注音用户注意!!!:\r\n两次空格为翻页.\r\n回车为输入默认汉字.\r\n默认没有绑任何键到临英和临拼(你可以更改).\r\n\r\n详情:\r\n=====\r\n\r\n所有变量中, 只有 g:ywvim_ims 是必须要设置的.\r\n\r\n1. g:ywvim_ims 是注册你的输入法的变量, 格式为:\r\n\r\n      \\['输入法的拼音简称', '输入法的中文名称', '码表文件']\r\n            \r\n比如 \\['wb', '五笔', 'wubi.ywvim'], 可以读为: 五笔输入法, 简称为 wb, 码表文件为 wubi.ywvim.\r\nywvim 会自动扫描 ywvim.vim 的同一目录及其子目录, 如果有同名文件, 以第一个优先.\r\n第一行的为默认输入法.\r\n你可以把你不需要的输入法的行删去.\r\n\r\n2. let g:ywvim_py = { 'helpim':'wb', 'gb':0 }\r\n\r\n单独设置每个码表的参数, 码表级别优先于全局级别. 码表级别的参数设置格式是:\r\n \r\n    g:ywvim_{输入法的简称} = {'参数':'参数设置'}\r\n\r\n目前有这几个参数支持局部设置:\r\nlistmax: 候选框数目.\r\nmaxphraselength: 最大词长.\r\nhelpim: 反查码表的简称.\r\nzhpunc: 中文标点开关.\r\nmatchexact: 精确匹配开关.\r\ngb: 只输入 gb2312 范围汉字.\r\n \r\n比如你可以这样设:\r\n\r\n    let g:ywvim_zy = {'listmax':6, 'maxphraselength':1, 'gb':0}\r\n\r\n意思是, 对于注音(zy)输入法, 候选框个数(listmax)为 6, 最大词长(maxphraselength)为 1, 只输入在 gb2312 范围的汉字('gb':0).\r\n\r\n你也可以全局设置某个变量, 格式是 let g:ywvim_listmax = 5, 这样就不用为每个码表都设相同的设置了. 下面都是全局变量.\r\n\r\n3. g:ywvim_zhpunc: 设置默认中文标点输入开关, 1 为开, 默认打开拼音输入, 2 为关.\r\n\r\n4. g:ywvim_listmax: 候选项个数.\r\n\r\n5. g:ywvim_esc_autoff: 设置离开插入模式时是否自动关闭 ywvim. 1 为自动, 0 为手动.\r\n(感谢在 #arch-cn@irc.oftc.net 的 snow 提的要求.)\r\n\r\n6. let g:ywvim_autoinput = 1: 支持两种程度的自动模式. 设为 2 为重度自动, 任何单码字都自动上屏. 2 为中度自动, 只在翻页时出现的单码字才上屏.\r\n(感谢在 #arch-cn@irc.oftc.net 上的 medicalwei 提供的建议)\r\n\r\n7. let g:ywvim_circlecandidates = 1: 设为 1 表示可以在候选页中循环翻页.\r\n(感谢在 #arch-cn@irc.oftc.net 上的 medicalwei 提供的建议)\r\n\r\n8. let g:ywvim_helpim_on = 0: 设为 1 表示打开反查码表的功能.\r\n\r\n    警告: 对于大码表会导致其速度降低.\r\n\r\n9. let g:ywvim_matchexact = 0: 设为 1 表示只显示全码匹配的字.\r\n(感谢在 #arch-cn@irc.oftc.net 上的 medicalwei 提供的建议)\r\n\r\n10. let g:ywvim_chinesecode = 1: 对于有中文字母的输入法(比如注音, 仓颉),\r\n已键入的字母用中文字母来显示, 而不是英文字母. 比如在注音里, 你输入 ji3 后,\r\n显示的是 ㄨㄛˇ, 而不是 ji3\r\n(感谢在 #arch-cn@irc.oftc.net 上的 medicalwei 提供的建议)\r\n\r\n11. let g:ywvim_gb = 1, 设为 1 为只输入 gb2312 范围汉字.\r\n\r\n12. let g:ywvim_preconv = 'g2b', 默认简繁转换方向.\r\n\r\n13. let g:ywvim_conv = 'g2b', 設置簡繁轉換方向, 'g2b' 為簡軟繁, 'b2g' 為繁轉簡, ''(留空)為關閉\r\n(感谢在 www.newsmth.net 上的 vace 提供的建议)\r\n\r\n14. let g:ywvim_lockb = 0, 为 0 时, 在空码是不锁定键盘.\r\n\r\n15. let g:ywvim_theme = 'light', 设置输入栏主题颜色, 可选 'light' 或 'dark'.\r\n\r\n16. let g:ywvim_intelligent_punc=1，打开智能标点，在数字后输入标点，默认输入英文状态标点，快速再输入同一个标点时，会替换成中文标点。\r\n    let g:ywvim_intelligent_punclist='.,:' 设置支持智能标点的标点符号。\r\n\r\n17. let g:ywvim_popupwin=1 使用vim8.2以上的弹窗特性显示候选项。\r\n    let g:ywvim_popupwin_follow_cursor=1 设置候选项弹窗为光标跟随。\r\n    let g:ywvim_popupwin_horizontal=1 设置弹窗的候选项水平排列。\r\n    let g:ywvim_popupwin_force_cmdline 在cmdline时强制使用popupwin特性。\r\n\r\n已知问题:\r\n=========\r\n1. 反查码表对于大码表反应速度过慢. 临时解决方案, 换词汇量较小的码表或者把 listmax 设小一点.\r\n\r\n2. cmdline中无法正常关闭popupwin。\r\n\r\n3. 窗口布局变化时（如Ctrl-w o）不能更新输入法状态提示。\r\n\r\n问题与建议反馈:\r\n=====\r\n请发反馈, 补丁或建议到 ywupub AT 163 DOT com.\r\n\r\n待做:\r\n============\r\n\r\n码表格式:\r\n=========\r\nywvim 用的码表是最简单的普通文本, 所以你可以很容易的定制出自己的码表. 请确保你的码表以 utf-8 的编码保存.\r\n\r\n分四部分:[Description], [CharDefinition], [Punctuation] 和 [Main]. 顺序不能颠倒:\r\n[Description]是输入法的一般参数.\r\n[CharDefinition] 是给像注音, 仓颉等有中文字母的输入法用的.\r\n[Punctuation]是标点, [Main]是主码表.\r\n\r\n[Description]\r\nName=倉頡五代   <== 码表名称.\r\nMaxCodes=5      <== 最大码长.\r\nMaxElement=1  <== 最大词长. 感谢在 www.newsmth.net 的 vace 的建议.\r\nUsedCodes=abcdefghijklmnopqrstuvwxyz <== 输入法所用到的键位\r\nEnChar=;    <= 临时输入英文的切换键.\r\nPyChar=z    <= 临时输入拼音键.\r\nInputZhSecKeys=; <= 输入第二重码键.\r\n下面选项均为注音用户所设, 其他输入法不必设置.\r\nEndCodes=  <= 结束字码的键位.\r\nInputZhKeys=  <= 输入中文的按键\r\nInputEnKeys=  <= 输入英文的按键\r\nAltPageUpKeys= <= 其他上翻页键\r\nAltPageDnkeys= <= 其他下翻页键\r\n\r\n[CharDefinition]\r\na 日  <== 中文字母的定义在这里定义. 如果没有, 留空即可.\r\n\r\n[Punctuation]\r\n{ 『\r\n\" \u00e2\u0080\u009c \u00e2\u0080\u009d\r\n\r\n[Main]\r\na 日 曰 <== 由字码和汉字组成一行.\r\n\r\n常见问题:\r\n============\r\nQ: 增加模糊查找? 增加自动调频?\r\nA: 对于像作者一样的单字形码用户, 模糊查找是完全用不到的功能, 所以没有兴趣也没有时间开发. 如果你希望有该特性, 请发补丁给我.\r\n而自动调频对于形码来说, 简直就是灾难, 但对音码来说可能很有用. 如果你觉得有用, 你也可以发补丁给我. 谢谢.\r\n\r\n======= English version =======\r\n=======\r\nNOTE!!!\r\n=======\r\nIf you are a ywvim's old user, before upgrade to the latest version, please have a look at *all* of the release notes and known bugs then look for the more details about the corresponding part of them in the description, because maybe some imcompatible changes have been made between your old version and the latest one.\r\nIf you find a bug when using, please look at the \"known bugs\" section to make sure whether it's a know bug before you report.\r\n\r\nDownload the lastest script(1.33): https:\/\/www.vim.org\/scripts\/download_script.php?src_id=27354\r\nDownload the lastest mabiao(1.15): https:\/\/www.vim.org\/scripts\/download_script.php?src_id=27224\r\n\r\nIntroduce:\r\n==========\r\nywvim is an input method for vim without the help of any external input method tools, it can input chinese in all modes of vim. Its target user is mainly of 形码, and lacks many fancy features for 拼音 users, for such a featureful IM, please have a look at vimim[http:\/\/www.vim.org\/scripts\/script.php?script_id=2506].\r\nBad news: ywvim's key mappings conflict with vimim, you have to make a choice between them.\r\n\r\nsettings in .vimrc:\r\n===================\r\nput some lines like the following into your ~\/.vimrc:\r\n\r\n-----\r\nlet g:ywvim_ims=[ \r\n            \\['wb', '五笔', 'wubi.ywvim'], \r\n            \\['py', '拼音', 'pinyin.ywvim'], \r\n            \\['cj', '仓颉', 'cangjie.ywvim'], \r\n            \\['wb98', '五笔98', 'wubi98.ywvim'], \r\n            \\['zm', '郑码', 'zhengma.ywvim'], \r\n            \\['zy', '注音', 'zhuyin.ywvim'], \r\n            \\['ar30', '行列', 'array30.ywvim'], \r\n            \\]\r\n\r\nlet g:ywvim_py = { 'helpim':'wb', 'gb':0 }\r\nlet g:ywvim_zhpunc = 1\r\nlet g:ywvim_listmax = 5\r\nlet g:ywvim_esc_autoff = 0\r\nlet g:ywvim_autoinput = 1\r\nlet g:ywvim_intelligent_punc=1\r\nlet g:ywvim_circlecandidates = 1\r\nlet g:ywvim_helpim_on = 0\r\nlet g:ywvim_matchexact = 0\r\nlet g:ywvim_chinesecode = 1\r\nlet g:ywvim_gb = 0\r\nlet g:ywvim_preconv = 'g2b'\r\nlet g:ywvim_conv = ''\r\nlet g:ywvim_lockb = 0\r\n-----\r\n\r\nUsage:\r\n======\r\n<Ctrl-Space>, <Ctrl-Shift-Space>, <Ctrl-@>, <Ctrl-\\>    Toggle ywvim between on and off.\r\n\r\n;(semicolon)    Temporary English key.\r\n\r\nz, `            Temporary pinyin input key. (need a abbrev name 'py' pinyin mabiao in g:ywvim_ims)\r\n\r\n<Ctrl-^> setup ywvim:\r\n    码表切换.\r\n    中英标点切换.\r\n    候选项个数: candidates number.\r\n    最大词长: max pharase length.\r\n    简繁转换开关.\r\n    只输入GB2312.\r\n    辅助编码提示开关.\r\n\r\n,.-=        Pageup\/pagedown.\r\n\r\nspace or num key for input Chinese, Enter inputs English.\r\n; Select the second candiate. Thanks for vace on www.newsmth.net's suggestion.)\r\n\r\nNOTE for zhuyin users!!!:\r\ntwo continual space is pagedown.\r\nEnter is to select the defaut Chinese charator.\r\nEnglish key and Pinyin key don't be bond to any keys by default(you can configure it).\r\n\r\nDetails:\r\n============\r\n\r\ng:ywvim_ims is a must-have variable among so many options.\r\n\r\n1. g:ywvim_ims is the variable that registers your input methods, the format is:\r\n\r\n      \\['English_abbreviation_for_IM', 'Chinese_name_of_IM', 'mabiao_file']\r\n\r\nFor example, \\['wb', '五笔', 'wubi.ywvim'], can be described as: wubi input method, English abbreviation is wb, mabiao file is wubi.ywvim.\r\nywvim will try to search the dir and subdirs under it, and use the first one if there are files shared with the same name..\r\nthe first one is the defaut one.\r\nYou can delete the lines of IM that you don't need at all.\r\n\r\n2. let g:ywvim_py = { 'helpim':'wb', 'gb':0 }\r\n\r\nYou can setup a parameter which only has effect on a particular IM, IM's has higher priority on global's. Its format is:\r\n \r\n    g:ywvim_{English_abbreviation_for_IM} = {'parameter':'setting'}\r\n\r\nThese parameters support local effect:\r\nlistmax: candidates max number.\r\nmaxphraselength: max length of phrase.\r\nhelpim: help IM's English abbreviation.\r\nzhpunc: Input Chinese punctuations.\r\nmatchexact: show only the exact matched.\r\ngb: set it to 1 means only input Chinese in gb2312.\r\n \r\nFor instance you can setup like this:\r\n\r\n    let g:ywvim_zy = {'listmax':6, 'maxphraselength':1, 'gb':0}\r\n\r\nit means, for zhuyin(zy) IM, candidates max rumber(maxlist) is 6, max phrase(maxphraselength) is 1, only input Chinese in gb2312('gb':0).\r\n\r\nYou also can setup a parameter globally, format is let g:ywvim_listmax = 5, so you can setup a parameter easily for every IM.\r\n\r\n3. g:ywvim_zhpunc: toggle the default Chinese punctuation on(1) or off(0).\r\n\r\n4. g:ywvim_listmax: maxmum number of candidates.\r\n\r\n5. g:ywvim_esc_autoff: whether auto toggle ywvim to be off when escaping from insertmode, 1 means yes, 0 no.\r\n(Thanks to snow on #arch-cn@irc.oftc.net who gave this feature request.)\r\n\r\n6. let g:ywvim_autoinput = 1:  supports two extends of auto input, set it to 2 is high auto, every singe candiate is auto inputted, 1 is media auto, just auto input when pageup\/down.\r\n(Thanks for medicalwei on #arch-cn@irc.oftc.net's suggestion.)\r\n\r\n7. let g:ywvim_circlecandidates = 1: set to 1 means circle pages when reaching the end.\r\n(Thanks for medicalwei on #arch-cn@irc.oftc.net's suggestion.)\r\n\r\n8. let g:ywvim_helpim_on = 0: set it to 1 means support of help mabiao.\r\n\r\n    Warn: The speed is terrible slow for extremly large mabiao.\r\n\r\n9. let g:ywvim_matchexact = 0: set to 1 means only show the exact matched Chinese.\r\n(Thanks for medicalwei on #arch-cn@irc.oftc.net's suggestion.)\r\n\r\n10. let g:ywvim_chinesecode = 1: when set, show the Chinese alphabets instead of English.\r\n(Thanks for medicalwei on #arch-cn@irc.oftc.net's suggestion.)\r\n\r\n11. let g:ywvim_gb = 1, set it to 1 means only input Chinese in range of gb2312.\r\n\r\n12. let g:ywvim_preconv = 'g2b', define the preferred simplified-traditional conversion direction.\r\n\r\n13. let g:ywvim_conv = 'g2b', direction of auto convertion bwtween Simplified and Traditional Chinese. 'g2b' Simplified -> Traditional, 'b2g' Traditional -> Simplified, '' (Leave it blank) disables feature.\r\n(Thanks for vace on www.newsmth.net's suggestion.)\r\n\r\n14. let g:ywvim_lockb = 0, 0 means not to lock up the keyboard when there's no charactor matched with.\r\n\r\n15. let g:ywvim_theme = 'light', set color theme of IM bar, value should be 'light' or 'dark'.\r\n\r\n16. let g:ywvim_intelligent_punc=1 Turn on intelligent punctation support, when you input a punctation after numbers, the punctuation will be English punctuation, after input the same punctuation once more time quickly, the English punctuation will be replaced by Chinese one.\r\n    let g:ywvim_intelligent_punclist='.,:' Set up the punctuations that support the intelligent function.\r\n\r\n17. let g:ywvim_popupwin=1 candidate list supports popupwin feature of vim 8.2。\r\n    let g:ywvim_popupwin_follow_cursor=1 set the popupwin follows cursor.\r\n    let g:ywvim_popupwin_horizontal=1 set the candidate list in popupwin arranged horizontally.\r\n    let g:ywvim_popupwin_force_cmdline force to turn on the popupwin feature when at cmdline.\r\n\r\nKnown Bugs:\r\n===========\r\n1. Slow issue on big help mabiao. Workaround: use a relative small mabiao, or set the listmax to a smaller value.\r\n\r\n2. popupwin can't be closed when at cmdline (statusbar).\r\n\r\n3. Can't update the im indicator display when window layout changes (eg Ctrl-w o).\r\n\r\nFeedback:\r\n=========\r\nPlease send the feedback, patch or advice to ywupub AT 163 DOT com.\r\n\r\nTODO:\r\n======\r\n\r\nFAQ:\r\n============\r\nQ: Supports fuzzy searching? Supports auto frequency?\r\nA: Author doesn't use fuzzy searching at all, but if you have patch, please send\r\nit to me.\r\nAbout auto frequency, it's a hell for shape input method, but maybe useful for pinyin users. If you can patch it, please do it and send the patch to the author. Thanks.\r\n\r\nMabiao file format:\r\n===================\r\nThe mabiao which ywvim uses is just plaintext, so everyone can create his own mabiao easily. Please make sure the mabiao is in utf-8 fileencoding.\r\n\r\nContains four fields: [Description], [CharDefinition], [Punctuation] and [Main]. They must be appeared in fire in sequences:\r\n[Description] general parameter of a input method.\r\n[CharDefinition] For the IM like zhuyin and cangjie that have Chinese alphabets.\r\n[Punctuation] contains punctuations, [Main] is the main part.\r\n\r\n[Description]\r\nName=倉頡五代   <== mabiao's name.\r\nMaxCodes=5      <== Max code number.\r\nMaxElement=1  <== max phase length. Thanks for vace on www.newsmth.net's suggestion.\r\nUsedCodes=abcdefghijklmnopqrstuvwxyz <== All keys that needs to triggle IM input.\r\nEnChar=;    <= occasional English key.\r\nPyChar=z    <= occasional PinYin key.\r\nInputZhSecKeys=; <= Key for input the second candidate.\r\nFollowing is for ZhuYin alike IM, other IM don't need to set them at all.\r\nEndCodes=  <= Why keys mean input Chinese has ended.\r\nInputZhKeys=  <= Input Chinese's key.\r\nInputEnKeys=  <= Input English's key.\r\nAltPageUpKeys= <= Alternative keys for pageup.\r\nAltPageDnKeys= <= Alternative keys for pagedown.\r\n\r\n[CharDefinition]\r\na 日  <== Definition of Chinese alphabets. If hasn't, leave it blank.\r\n\r\n[Punctuation]\r\n{ 『\r\n\" \u00e2\u0080\u009c \u00e2\u0080\u009d\r\n\r\n[Main]\r\na 日 曰 <== Char code and Chinese Charactors.","4":"介绍：\r\n======= Chinese version =======\r\n注意!!!\r\n=======\r\n如果你是 ywvim 的老用户, 在升级到新版本前, 请注意你的旧版本到新版本间*所有*的发布公告和已知 bugs, 然后查找对应设置的说明, 以免不兼容的改变给你带来不便.\r\n如果你在使用中发现了问题, 在报告之前, 请先查看下面的\"已知问题\"部分, 确定是否为已知 bug.\r\n\r\n下载最新脚本(1.33): https:\/\/www.vim.org\/scripts\/download_script.php?src_id=27354\r\n下载最新码表(1.15): https:\/\/www.vim.org\/scripts\/download_script.php?src_id=27224\r\n\r\n介绍:\r\n=====\r\nywvim 是一款不依赖外部输入法的, 在 vim 里输入中文的工具. 支持在 vim 的所有模式下输入中文. 它面向的对象主要为形码用户, 对于拼音用户, 你可以试试有更多功能的 vimim[http:\/\/www.vim.org\/scripts\/script.php?script_id=2506].\r\n坏消息: ywvim 和 vimim 的键绑定冲突, 你必须在两者中做出选择.\r\n\r\n.vimrc 里的设置:\r\n================\r\n把下面的几行放到你的 .vimrc 中:\r\n\r\n-----\r\nlet g:ywvim_ims=[ \r\n            \\['wb', '五笔', 'wubi.ywvim'], \r\n            \\['py', '拼音', 'pinyin.ywvim'], \r\n            \\['cj', '仓颉', 'cangjie.ywvim'], \r\n            \\['wb98', '五笔98', 'wubi98.ywvim'], \r\n            \\['zm', '郑码', 'zhengma.ywvim'], \r\n            \\['zy', '注音', 'zhuyin.ywvim'], \r\n            \\['ar30', '行列', 'array30.ywvim'], \r\n            \\]\r\n\r\nlet g:ywvim_py = { 'helpim':'wb', 'gb':0 }\r\n\r\nlet g:ywvim_zhpunc = 1\r\nlet g:ywvim_listmax = 5\r\nlet g:ywvim_esc_autoff = 0\r\nlet g:ywvim_autoinput = 0\r\nlet g:ywvim_intelligent_punc=1\r\nlet g:ywvim_circlecandidates = 1\r\nlet g:ywvim_helpim_on = 0\r\nlet g:ywvim_matchexact = 0\r\nlet g:ywvim_chinesecode = 1\r\nlet g:ywvim_gb = 0\r\nlet g:ywvim_preconv = 'g2b'\r\nlet g:ywvim_conv = ''\r\nlet g:ywvim_lockb = 1\r\n-----\r\n\r\n使用:\r\n=====\r\n<Ctrl-Space>, <Ctrl-Shift-Space>, <Ctrl-@>, <Ctrl-\\> 输入法开关.\r\n\r\n;(分号) 临时英文.\r\n\r\nz, ` 临时拼音.（需要输入法变量 g:ywvim_ims 里有一个 'py' 拼音简称的码表）\r\n\r\n<Ctrl-^> 设置输入法:\r\n    码表切换.\r\n    中英标点切换.\r\n    候选项个数: 候选项个数.\r\n    最大词长: 你想输入的最长的词. 设为 1 为单字模试.\r\n    简繁转换开关.\r\n    只输入GB2312.\r\n    辅助编码提示开关.\r\n\r\n,.-=    上下翻页.\r\n\r\n空格或数字选字, 回车输英文.\r\n; 分号选择第二候选词. (感谢在 www.newsmth.net 的 vace 的建议.)\r\n\r\n注音用户注意!!!:\r\n两次空格为翻页.\r\n回车为输入默认汉字.\r\n默认没有绑任何键到临英和临拼(你可以更改).\r\n\r\n详情:\r\n=====\r\n\r\n所有变量中, 只有 g:ywvim_ims 是必须要设置的.\r\n\r\n1. g:ywvim_ims 是注册你的输入法的变量, 格式为:\r\n\r\n      \\['输入法的拼音简称', '输入法的中文名称', '码表文件']\r\n            \r\n比如 \\['wb', '五笔', 'wubi.ywvim'], 可以读为: 五笔输入法, 简称为 wb, 码表文件为 wubi.ywvim.\r\nywvim 会自动扫描 ywvim.vim 的同一目录及其子目录, 如果有同名文件, 以第一个优先.\r\n第一行的为默认输入法.\r\n你可以把你不需要的输入法的行删去.\r\n\r\n2. let g:ywvim_py = { 'helpim':'wb', 'gb':0 }\r\n\r\n单独设置每个码表的参数, 码表级别优先于全局级别. 码表级别的参数设置格式是:\r\n \r\n    g:ywvim_{输入法的简称} = {'参数':'参数设置'}\r\n\r\n目前有这几个参数支持局部设置:\r\nlistmax: 候选框数目.\r\nmaxphraselength: 最大词长.\r\nhelpim: 反查码表的简称.\r\nzhpunc: 中文标点开关.\r\nmatchexact: 精确匹配开关.\r\ngb: 只输入 gb2312 范围汉字.\r\n \r\n比如你可以这样设:\r\n\r\n    let g:ywvim_zy = {'listmax':6, 'maxphraselength':1, 'gb':0}\r\n\r\n意思是, 对于注音(zy)输入法, 候选框个数(listmax)为 6, 最大词长(maxphraselength)为 1, 只输入在 gb2312 范围的汉字('gb':0).\r\n\r\n你也可以全局设置某个变量, 格式是 let g:ywvim_listmax = 5, 这样就不用为每个码表都设相同的设置了. 下面都是全局变量.\r\n\r\n3. g:ywvim_zhpunc: 设置默认中文标点输入开关, 1 为开, 默认打开拼音输入, 2 为关.\r\n\r\n4. g:ywvim_listmax: 候选项个数.\r\n\r\n5. g:ywvim_esc_autoff: 设置离开插入模式时是否自动关闭 ywvim. 1 为自动, 0 为手动.\r\n(感谢在 #arch-cn@irc.oftc.net 的 snow 提的要求.)\r\n\r\n6. let g:ywvim_autoinput = 1: 支持两种程度的自动模式. 设为 2 为重度自动, 任何单码字都自动上屏. 2 为中度自动, 只在翻页时出现的单码字才上屏.\r\n(感谢在 #arch-cn@irc.oftc.net 上的 medicalwei 提供的建议)\r\n\r\n7. let g:ywvim_circlecandidates = 1: 设为 1 表示可以在候选页中循环翻页.\r\n(感谢在 #arch-cn@irc.oftc.net 上的 medicalwei 提供的建议)\r\n\r\n8. let g:ywvim_helpim_on = 0: 设为 1 表示打开反查码表的功能.\r\n\r\n    警告: 对于大码表会导致其速度降低.\r\n\r\n9. let g:ywvim_matchexact = 0: 设为 1 表示只显示全码匹配的字.\r\n(感谢在 #arch-cn@irc.oftc.net 上的 medicalwei 提供的建议)\r\n\r\n10. let g:ywvim_chinesecode = 1: 对于有中文字母的输入法(比如注音, 仓颉),\r\n已键入的字母用中文字母来显示, 而不是英文字母. 比如在注音里, 你输入 ji3 后,\r\n显示的是 ㄨㄛˇ, 而不是 ji3\r\n(感谢在 #arch-cn@irc.oftc.net 上的 medicalwei 提供的建议)\r\n\r\n11. let g:ywvim_gb = 1, 设为 1 为只输入 gb2312 范围汉字.\r\n\r\n12. let g:ywvim_preconv = 'g2b', 默认简繁转换方向.\r\n\r\n13. let g:ywvim_conv = 'g2b', 設置簡繁轉換方向, 'g2b' 為簡軟繁, 'b2g' 為繁轉簡, ''(留空)為關閉\r\n(感谢在 www.newsmth.net 上的 vace 提供的建议)\r\n\r\n14. let g:ywvim_lockb = 0, 为 0 时, 在空码是不锁定键盘.\r\n\r\n15. let g:ywvim_theme = 'light', 设置输入栏主题颜色, 可选 'light' 或 'dark'.\r\n\r\n16. let g:ywvim_intelligent_punc=1，打开智能标点，在数字后输入标点，默认输入英文状态标点，快速再输入同一个标点时，会替换成中文标点。\r\n    let g:ywvim_intelligent_punclist='.,:' 设置支持智能标点的标点符号。\r\n\r\n17. let g:ywvim_popupwin=1 使用vim8.2以上的弹窗特性显示候选项。\r\n    let g:ywvim_popupwin_follow_cursor=1 设置候选项弹窗为光标跟随。\r\n    let g:ywvim_popupwin_horizontal=1 设置弹窗的候选项水平排列。\r\n    let g:ywvim_popupwin_force_cmdline 在cmdline时强制使用popupwin特性。\r\n\r\n已知问题:\r\n=========\r\n1. 反查码表对于大码表反应速度过慢. 临时解决方案, 换词汇量较小的码表或者把 listmax 设小一点.\r\n\r\n2. cmdline中无法正常关闭popupwin。\r\n\r\n3. 窗口布局变化时（如Ctrl-w o）不能更新输入法状态提示。\r\n\r\n问题与建议反馈:\r\n=====\r\n请发反馈, 补丁或建议到 ywupub AT 163 DOT com.\r\n\r\n待做:\r\n============\r\n\r\n码表格式:\r\n=========\r\nywvim 用的码表是最简单的普通文本, 所以你可以很容易的定制出自己的码表. 请确保你的码表以 utf-8 的编码保存.\r\n\r\n分四部分:[Description], [CharDefinition], [Punctuation] 和 [Main]. 顺序不能颠倒:\r\n[Description]是输入法的一般参数.\r\n[CharDefinition] 是给像注音, 仓颉等有中文字母的输入法用的.\r\n[Punctuation]是标点, [Main]是主码表.\r\n\r\n[Description]\r\nName=倉頡五代   <== 码表名称.\r\nMaxCodes=5      <== 最大码长.\r\nMaxElement=1  <== 最大词长. 感谢在 www.newsmth.net 的 vace 的建议.\r\nUsedCodes=abcdefghijklmnopqrstuvwxyz <== 输入法所用到的键位\r\nEnChar=;    <= 临时输入英文的切换键.\r\nPyChar=z    <= 临时输入拼音键.\r\nInputZhSecKeys=; <= 输入第二重码键.\r\n下面选项均为注音用户所设, 其他输入法不必设置.\r\nEndCodes=  <= 结束字码的键位.\r\nInputZhKeys=  <= 输入中文的按键\r\nInputEnKeys=  <= 输入英文的按键\r\nAltPageUpKeys= <= 其他上翻页键\r\nAltPageDnkeys= <= 其他下翻页键\r\n\r\n[CharDefinition]\r\na 日  <== 中文字母的定义在这里定义. 如果没有, 留空即可.\r\n\r\n[Punctuation]\r\n{ 『\r\n\" \u00e2\u0080\u009c \u00e2\u0080\u009d\r\n\r\n[Main]\r\na 日 曰 <== 由字码和汉字组成一行.\r\n\r\n常见问题:\r\n============\r\nQ: 增加模糊查找? 增加自动调频?\r\nA: 对于像作者一样的单字形码用户, 模糊查找是完全用不到的功能, 所以没有兴趣也没有时间开发. 如果你希望有该特性, 请发补丁给我.\r\n而自动调频对于形码来说, 简直就是灾难, 但对音码来说可能很有用. 如果你觉得有用, 你也可以发补丁给我. 谢谢.\r\n\r\n======= English version =======\r\n=======\r\nNOTE!!!\r\n=======\r\nIf you are a ywvim's old user, before upgrade to the latest version, please have a look at *all* of the release notes and known bugs then look for the more details about the corresponding part of them in the description, because maybe some imcompatible changes have been made between your old version and the latest one.\r\nIf you find a bug when using, please look at the \"known bugs\" section to make sure whether it's a know bug before you report.\r\n\r\nDownload the lastest script(1.33): https:\/\/www.vim.org\/scripts\/download_script.php?src_id=27354\r\nDownload the lastest mabiao(1.15): https:\/\/www.vim.org\/scripts\/download_script.php?src_id=27224\r\n\r\nIntroduce:\r\n==========\r\nywvim is an input method for vim without the help of any external input method tools, it can input chinese in all modes of vim. Its target user is mainly of 形码, and lacks many fancy features for 拼音 users, for such a featureful IM, please have a look at vimim[http:\/\/www.vim.org\/scripts\/script.php?script_id=2506].\r\nBad news: ywvim's key mappings conflict with vimim, you have to make a choice between them.\r\n\r\nsettings in .vimrc:\r\n===================\r\nput some lines like the following into your ~\/.vimrc:\r\n\r\n-----\r\nlet g:ywvim_ims=[ \r\n            \\['wb', '五笔', 'wubi.ywvim'], \r\n            \\['py', '拼音', 'pinyin.ywvim'], \r\n            \\['cj', '仓颉', 'cangjie.ywvim'], \r\n            \\['wb98', '五笔98', 'wubi98.ywvim'], \r\n            \\['zm', '郑码', 'zhengma.ywvim'], \r\n            \\['zy', '注音', 'zhuyin.ywvim'], \r\n            \\['ar30', '行列', 'array30.ywvim'], \r\n            \\]\r\n\r\nlet g:ywvim_py = { 'helpim':'wb', 'gb':0 }\r\nlet g:ywvim_zhpunc = 1\r\nlet g:ywvim_listmax = 5\r\nlet g:ywvim_esc_autoff = 0\r\nlet g:ywvim_autoinput = 1\r\nlet g:ywvim_intelligent_punc=1\r\nlet g:ywvim_circlecandidates = 1\r\nlet g:ywvim_helpim_on = 0\r\nlet g:ywvim_matchexact = 0\r\nlet g:ywvim_chinesecode = 1\r\nlet g:ywvim_gb = 0\r\nlet g:ywvim_preconv = 'g2b'\r\nlet g:ywvim_conv = ''\r\nlet g:ywvim_lockb = 0\r\n-----\r\n\r\nUsage:\r\n======\r\n<Ctrl-Space>, <Ctrl-Shift-Space>, <Ctrl-@>, <Ctrl-\\>    Toggle ywvim between on and off.\r\n\r\n;(semicolon)    Temporary English key.\r\n\r\nz, `            Temporary pinyin input key. (need a abbrev name 'py' pinyin mabiao in g:ywvim_ims)\r\n\r\n<Ctrl-^> setup ywvim:\r\n    码表切换.\r\n    中英标点切换.\r\n    候选项个数: candidates number.\r\n    最大词长: max pharase length.\r\n    简繁转换开关.\r\n    只输入GB2312.\r\n    辅助编码提示开关.\r\n\r\n,.-=        Pageup\/pagedown.\r\n\r\nspace or num key for input Chinese, Enter inputs English.\r\n; Select the second candiate. Thanks for vace on www.newsmth.net's suggestion.)\r\n\r\nNOTE for zhuyin users!!!:\r\ntwo continual space is pagedown.\r\nEnter is to select the defaut Chinese charator.\r\nEnglish key and Pinyin key don't be bond to any keys by default(you can configure it).\r\n\r\nDetails:\r\n============\r\n\r\ng:ywvim_ims is a must-have variable among so many options.\r\n\r\n1. g:ywvim_ims is the variable that registers your input methods, the format is:\r\n\r\n      \\['English_abbreviation_for_IM', 'Chinese_name_of_IM', 'mabiao_file']\r\n\r\nFor example, \\['wb', '五笔', 'wubi.ywvim'], can be described as: wubi input method, English abbreviation is wb, mabiao file is wubi.ywvim.\r\nywvim will try to search the dir and subdirs under it, and use the first one if there are files shared with the same name..\r\nthe first one is the defaut one.\r\nYou can delete the lines of IM that you don't need at all.\r\n\r\n2. let g:ywvim_py = { 'helpim':'wb', 'gb':0 }\r\n\r\nYou can setup a parameter which only has effect on a particular IM, IM's has higher priority on global's. Its format is:\r\n \r\n    g:ywvim_{English_abbreviation_for_IM} = {'parameter':'setting'}\r\n\r\nThese parameters support local effect:\r\nlistmax: candidates max number.\r\nmaxphraselength: max length of phrase.\r\nhelpim: help IM's English abbreviation.\r\nzhpunc: Input Chinese punctuations.\r\nmatchexact: show only the exact matched.\r\ngb: set it to 1 means only input Chinese in gb2312.\r\n \r\nFor instance you can setup like this:\r\n\r\n    let g:ywvim_zy = {'listmax':6, 'maxphraselength':1, 'gb':0}\r\n\r\nit means, for zhuyin(zy) IM, candidates max rumber(maxlist) is 6, max phrase(maxphraselength) is 1, only input Chinese in gb2312('gb':0).\r\n\r\nYou also can setup a parameter globally, format is let g:ywvim_listmax = 5, so you can setup a parameter easily for every IM.\r\n\r\n3. g:ywvim_zhpunc: toggle the default Chinese punctuation on(1) or off(0).\r\n\r\n4. g:ywvim_listmax: maxmum number of candidates.\r\n\r\n5. g:ywvim_esc_autoff: whether auto toggle ywvim to be off when escaping from insertmode, 1 means yes, 0 no.\r\n(Thanks to snow on #arch-cn@irc.oftc.net who gave this feature request.)\r\n\r\n6. let g:ywvim_autoinput = 1:  supports two extends of auto input, set it to 2 is high auto, every singe candiate is auto inputted, 1 is media auto, just auto input when pageup\/down.\r\n(Thanks for medicalwei on #arch-cn@irc.oftc.net's suggestion.)\r\n\r\n7. let g:ywvim_circlecandidates = 1: set to 1 means circle pages when reaching the end.\r\n(Thanks for medicalwei on #arch-cn@irc.oftc.net's suggestion.)\r\n\r\n8. let g:ywvim_helpim_on = 0: set it to 1 means support of help mabiao.\r\n\r\n    Warn: The speed is terrible slow for extremly large mabiao.\r\n\r\n9. let g:ywvim_matchexact = 0: set to 1 means only show the exact matched Chinese.\r\n(Thanks for medicalwei on #arch-cn@irc.oftc.net's suggestion.)\r\n\r\n10. let g:ywvim_chinesecode = 1: when set, show the Chinese alphabets instead of English.\r\n(Thanks for medicalwei on #arch-cn@irc.oftc.net's suggestion.)\r\n\r\n11. let g:ywvim_gb = 1, set it to 1 means only input Chinese in range of gb2312.\r\n\r\n12. let g:ywvim_preconv = 'g2b', define the preferred simplified-traditional conversion direction.\r\n\r\n13. let g:ywvim_conv = 'g2b', direction of auto convertion bwtween Simplified and Traditional Chinese. 'g2b' Simplified -> Traditional, 'b2g' Traditional -> Simplified, '' (Leave it blank) disables feature.\r\n(Thanks for vace on www.newsmth.net's suggestion.)\r\n\r\n14. let g:ywvim_lockb = 0, 0 means not to lock up the keyboard when there's no charactor matched with.\r\n\r\n15. let g:ywvim_theme = 'light', set color theme of IM bar, value should be 'light' or 'dark'.\r\n\r\n16. let g:ywvim_intelligent_punc=1 Turn on intelligent punctation support, when you input a punctation after numbers, the punctuation will be English punctuation, after input the same punctuation once more time quickly, the English punctuation will be replaced by Chinese one.\r\n    let g:ywvim_intelligent_punclist='.,:' Set up the punctuations that support the intelligent function.\r\n\r\n17. let g:ywvim_popupwin=1 candidate list supports popupwin feature of vim 8.2。\r\n    let g:ywvim_popupwin_follow_cursor=1 set the popupwin follows cursor.\r\n    let g:ywvim_popupwin_horizontal=1 set the candidate list in popupwin arranged horizontally.\r\n    let g:ywvim_popupwin_force_cmdline force to turn on the popupwin feature when at cmdline.\r\n\r\nKnown Bugs:\r\n===========\r\n1. Slow issue on big help mabiao. Workaround: use a relative small mabiao, or set the listmax to a smaller value.\r\n\r\n2. popupwin can't be closed when at cmdline (statusbar).\r\n\r\n3. Can't update the im indicator display when window layout changes (eg Ctrl-w o).\r\n\r\nFeedback:\r\n=========\r\nPlease send the feedback, patch or advice to ywupub AT 163 DOT com.\r\n\r\nTODO:\r\n======\r\n\r\nFAQ:\r\n============\r\nQ: Supports fuzzy searching? Supports auto frequency?\r\nA: Author doesn't use fuzzy searching at all, but if you have patch, please send\r\nit to me.\r\nAbout auto frequency, it's a hell for shape input method, but maybe useful for pinyin users. If you can patch it, please do it and send the patch to the author. Thanks.\r\n\r\nMabiao file format:\r\n===================\r\nThe mabiao which ywvim uses is just plaintext, so everyone can create his own mabiao easily. Please make sure the mabiao is in utf-8 fileencoding.\r\n\r\nContains four fields: [Description], [CharDefinition], [Punctuation] and [Main]. They must be appeared in fire in sequences:\r\n[Description] general parameter of a input method.\r\n[CharDefinition] For the IM like zhuyin and cangjie that have Chinese alphabets.\r\n[Punctuation] contains punctuations, [Main] is the main part.\r\n\r\n[Description]\r\nName=倉頡五代   <== mabiao's name.\r\nMaxCodes=5      <== Max code number.\r\nMaxElement=1  <== max phase length. Thanks for vace on www.newsmth.net's suggestion.\r\nUsedCodes=abcdefghijklmnopqrstuvwxyz <== All keys that needs to triggle IM input.\r\nEnChar=;    <= occasional English key.\r\nPyChar=z    <= occasional PinYin key.\r\nInputZhSecKeys=; <= Key for input the second candidate.\r\nFollowing is for ZhuYin alike IM, other IM don't need to set them at all.\r\nEndCodes=  <= Why keys mean input Chinese has ended.\r\nInputZhKeys=  <= Input Chinese's key.\r\nInputEnKeys=  <= Input English's key.\r\nAltPageUpKeys= <= Alternative keys for pageup.\r\nAltPageDnKeys= <= Alternative keys for pagedown.\r\n\r\n[CharDefinition]\r\na 日  <== Definition of Chinese alphabets. If hasn't, leave it blank.\r\n\r\n[Punctuation]\r\n{ 『\r\n\" \u00e2\u0080\u009c \u00e2\u0080\u009d\r\n\r\n[Main]\r\na 日 曰 <== Char code and Chinese Charactors.","install_details":"安装:\r\n=====\r\n要使用 ywvim, 你需要 ywvim.vim 脚本和至少一个码表. 要使用简繁转换功能, 你需要 g2b 简繁转换表. 要使用只输入 gb2312 里汉字功能, 你需要 gb2312 范围的汉字列表.\r\n\r\n当 ywvim 有新版本时, 一般只需更新脚本即可, 除非有专门通知提示你码表需要更新. 请确保你下的是最新的脚本和码表(版本不一定相同.)\r\n\r\n安装 ywvim：\r\n附件 ywvim.vim-<version>.tar.bz2 是 ywvim 脚本.\r\n\r\n解压脚本到你的 ~\/.vim\/plugin 目录下(windows 为 $VIM\/vimfiles\/plugin).\r\n\r\n        $ cd ~\/.vim\/plugin\r\n        $ unzip ywvim.vim.tar.bz2\r\n\r\n安装 ywvim 码表：\r\n附件 ywvim_mb-<version>.tar.bz2 包含了常用码表, 有注音, 行列, 仓颉, 拼音, 郑码, 五笔86 和 98 的码表, 一个 gb2312 范围的汉字列表, g2b 简繁转换表.\r\n(感谢在 #arch-cn@irc.oftc.net 上的 medicalwei 对注音提供的建议.)\r\n(感谢在 newsmth.net 上的 vace 对 g2b 提供的信息)\r\n\r\n解压码表到你的 ~\/.vim\/plugin 目录下(windows 为 vimfiles\/plugin).\r\n\r\n        $ cd ~\/.vim\/plugin\r\n        $ unzip ywvim_mb.tar.bz2\r\n\r\nInstall:\r\n========\r\nYou need both script and at least one of mabiao in order to make ywvim to work. You needs g2b.ywvim for simplified-traditional convertion. You needs gb2312 charactors list for inputing charactors only in gb2312 ranges.\r\n\r\nWhen ywvim has new version, it's general enough to update only the ywvim script, unless there is announcing that info you should need to update the mabiao. Please make sure you use the lastest version of script and mabiao(the version may not be the same).\r\n\r\nInstall ywvim:\r\nThe attachment ywvim.vim-<version>.tar.bz2 is the ywvim script itselt.\r\n\r\nUnpack the script into your ~\/.vim\/plugin.\r\n\r\n        $ cd ~\/.vim\/plugin\r\n        $ unzip ywvim.vim.tar.bz2\r\n\r\nInstall ywvim mabiao:\r\n\r\nThe attachment ywvim_mb-<version>.tar.bz2 contains some common input methods mabiao(码表): zhuyin, array, cangjie, pinyin, zhengma, wubi 86\/98, a gb2312 charactors list, g2b Simplified and Traditional Chinese convertion list.\r\n(Thanks for medicalwei on #arch-cn@irc.oftc.net's suggestion on zhuyin.)\r\n(Thanks for vace on newsmth.net's info on g2b.)\r\n\r\nUnpack the mabiaos into your ~\/.vim\/plugin.\r\n\r\n        $ cd ~\/.vim\/plugin\r\n        $ unzip ywvim_mb.tar.bz2\r\n","5":"安装:\r\n=====\r\n要使用 ywvim, 你需要 ywvim.vim 脚本和至少一个码表. 要使用简繁转换功能, 你需要 g2b 简繁转换表. 要使用只输入 gb2312 里汉字功能, 你需要 gb2312 范围的汉字列表.\r\n\r\n当 ywvim 有新版本时, 一般只需更新脚本即可, 除非有专门通知提示你码表需要更新. 请确保你下的是最新的脚本和码表(版本不一定相同.)\r\n\r\n安装 ywvim：\r\n附件 ywvim.vim-<version>.tar.bz2 是 ywvim 脚本.\r\n\r\n解压脚本到你的 ~\/.vim\/plugin 目录下(windows 为 $VIM\/vimfiles\/plugin).\r\n\r\n        $ cd ~\/.vim\/plugin\r\n        $ unzip ywvim.vim.tar.bz2\r\n\r\n安装 ywvim 码表：\r\n附件 ywvim_mb-<version>.tar.bz2 包含了常用码表, 有注音, 行列, 仓颉, 拼音, 郑码, 五笔86 和 98 的码表, 一个 gb2312 范围的汉字列表, g2b 简繁转换表.\r\n(感谢在 #arch-cn@irc.oftc.net 上的 medicalwei 对注音提供的建议.)\r\n(感谢在 newsmth.net 上的 vace 对 g2b 提供的信息)\r\n\r\n解压码表到你的 ~\/.vim\/plugin 目录下(windows 为 vimfiles\/plugin).\r\n\r\n        $ cd ~\/.vim\/plugin\r\n        $ unzip ywvim_mb.tar.bz2\r\n\r\nInstall:\r\n========\r\nYou need both script and at least one of mabiao in order to make ywvim to work. You needs g2b.ywvim for simplified-traditional convertion. You needs gb2312 charactors list for inputing charactors only in gb2312 ranges.\r\n\r\nWhen ywvim has new version, it's general enough to update only the ywvim script, unless there is announcing that info you should need to update the mabiao. Please make sure you use the lastest version of script and mabiao(the version may not be the same).\r\n\r\nInstall ywvim:\r\nThe attachment ywvim.vim-<version>.tar.bz2 is the ywvim script itselt.\r\n\r\nUnpack the script into your ~\/.vim\/plugin.\r\n\r\n        $ cd ~\/.vim\/plugin\r\n        $ unzip ywvim.vim.tar.bz2\r\n\r\nInstall ywvim mabiao:\r\n\r\nThe attachment ywvim_mb-<version>.tar.bz2 contains some common input methods mabiao(码表): zhuyin, array, cangjie, pinyin, zhengma, wubi 86\/98, a gb2312 charactors list, g2b Simplified and Traditional Chinese convertion list.\r\n(Thanks for medicalwei on #arch-cn@irc.oftc.net's suggestion on zhuyin.)\r\n(Thanks for vace on newsmth.net's info on g2b.)\r\n\r\nUnpack the mabiaos into your ~\/.vim\/plugin.\r\n\r\n        $ cd ~\/.vim\/plugin\r\n        $ unzip ywvim_mb.tar.bz2\r\n","first_name":"Yue","6":"Yue","last_name":"Wu","7":"Wu","releases":[{"0":"2662","vim_version":"7.0","1":"7.0","script_version":"1.33","2":"1.33","version_comment":"修复和改进光标显示错误。\r\nfixed and improved highlight cursor.","3":"修复和改进光标显示错误。\r\nfixed and improved highlight cursor.","package":"ywvim1.33.zip","4":"ywvim1.33.zip","src_id":"27354","5":"27354","creation_date":"1604341973","6":"1604341973"},{"0":"2662","vim_version":"7.0","1":"7.0","script_version":"1.32","2":"1.32","version_comment":"1. 重写临时英文模块。\r\n1. rewritten enmode.\r\n2. 修复智能标点bug。\r\n2. Fixed annoying intelligent punctuation bugs.\r\n3. 中英模式使用不同光标颜色（待完善）。\r\n3. Highlight cursor (buggy).","3":"1. 重写临时英文模块。\r\n1. rewritten enmode.\r\n2. 修复智能标点bug。\r\n2. Fixed annoying intelligent punctuation bugs.\r\n3. 中英模式使用不同光标颜色（待完善）。\r\n3. Highlight cursor (buggy).","package":"ywvim1.32.zip","4":"ywvim1.32.zip","src_id":"27352","5":"27352","creation_date":"1604181635","6":"1604181635"},{"0":"2662","vim_version":"7.0","1":"7.0","script_version":"1.15","2":"1.15","version_comment":"删掉文件中多余的行尾空格和^。\r\nDeleted redundant space and ^ in the files.","3":"删掉文件中多余的行尾空格和^。\r\nDeleted redundant space and ^ in the files.","package":"ywvim_mb-1.15.zip","4":"ywvim_mb-1.15.zip","src_id":"27224","5":"27224","creation_date":"1593784178","6":"1593784178"},{"0":"2662","vim_version":"7.0","1":"7.0","script_version":"1.31","2":"1.31","version_comment":"1. 修复空码时显示码表最后一行的bug。\r\n1. Fixed blank code matching the last line of the mabiao file. Thanks newsmth rekanda's report.\r\n2. 修复多余候选项的bug。\r\n2. Fixed redundant candidates. Thanks newsmth rekanda's report.\r\n3. 修复标点'~'的错误提示。\r\n3. Fixed bug of punctuation '~'.","3":"1. 修复空码时显示码表最后一行的bug。\r\n1. Fixed blank code matching the last line of the mabiao file. Thanks newsmth rekanda's report.\r\n2. 修复多余候选项的bug。\r\n2. Fixed redundant candidates. Thanks newsmth rekanda's report.\r\n3. 修复标点'~'的错误提示。\r\n3. Fixed bug of punctuation '~'.","package":"ywvim1.31.zip","4":"ywvim1.31.zip","src_id":"27223","5":"27223","creation_date":"1593783766","6":"1593783766"},{"0":"2662","vim_version":"7.0","1":"7.0","script_version":"1.30","2":"1.30","version_comment":"1. 修复智能标点误删字符bug，智能标点默认打开。\r\n1. Fixed bug of intelligent punctation feature。let g:ywvim_intelligent_punc=1 by default.\r\n2. 修复lockb的问题。\r\n2. Fixed lockb issues.\r\n3. 修复一些字打不出来的问题。\r\n3. Fixed input issues.","3":"1. 修复智能标点误删字符bug，智能标点默认打开。\r\n1. Fixed bug of intelligent punctation feature。let g:ywvim_intelligent_punc=1 by default.\r\n2. 修复lockb的问题。\r\n2. Fixed lockb issues.\r\n3. 修复一些字打不出来的问题。\r\n3. Fixed input issues.","package":"ywvim1.30.zip","4":"ywvim1.30.zip","src_id":"27080","5":"27080","creation_date":"1584449719","6":"1584449719"},{"0":"2662","vim_version":"7.0","1":"7.0","script_version":"1.29","2":"1.29","version_comment":"1. 调整默认配色。\r\n1. Adjust default theme.\r\n2. 修复EnMode后不能正常切换输入法的bug。\r\n2. Fix the bug when at EnMode switching IM behave incorrectly.","3":"1. 调整默认配色。\r\n1. Adjust default theme.\r\n2. 修复EnMode后不能正常切换输入法的bug。\r\n2. Fix the bug when at EnMode switching IM behave incorrectly.","package":"ywvim1.29.zip","4":"ywvim1.29.zip","src_id":"26963","5":"26963","creation_date":"1580927338","6":"1580927338"},{"0":"2662","vim_version":"7.0","1":"7.0","script_version":"1.28","2":"1.28","version_comment":"1. 修复popupwin时cmdline的刷新问题.\r\n1. Fixed cmdline's redraw issue when popupwin is on.\r\n2. 修复只有1个候选字时，按第二候选词键会报错错误.\r\n2. Fixed bug: the key for inputing the second candidate got error when has only one candidate. \r\n3. 全新的临时英文模块，修复临时英文错误.\r\n3. EnMode rewritten completely, fixed bugs on EnMode.","3":"1. 修复popupwin时cmdline的刷新问题.\r\n1. Fixed cmdline's redraw issue when popupwin is on.\r\n2. 修复只有1个候选字时，按第二候选词键会报错错误.\r\n2. Fixed bug: the key for inputing the second candidate got error when has only one candidate. \r\n3. 全新的临时英文模块，修复临时英文错误.\r\n3. EnMode rewritten completely, fixed bugs on EnMode.","package":"ywvim1.28.zip","4":"ywvim1.28.zip","src_id":"26918","5":"26918","creation_date":"1579034565","6":"1579034565"},{"0":"2662","vim_version":"7.0","1":"7.0","script_version":"1.27","2":"1.27","version_comment":"1. 改进了popupwin的支持, 在窗口太窄时候选栏自动换行.\r\n1. Improved popupwin feature, autowrap when window is too narrow.\r\n\r\n2. 由于在cmdline输入时无法关闭popwin窗口，取消了cmdline的popupwin支持. 若想体验, 可设置 g:ywvim_popupwin_force_cmdline=1.\r\n2. FIXME Disable popupwin when at cmdline because popupwin can't be closed when inputing at cmdline. You still can have a try the bug, set g:ywvim_popupwin_force_cmdline=1\r\n\r\n3. 修复命令行输入时的显示问题, 不再需要设置ywvim_dirty_redraw.\r\n3. Fixed redrawing issue at cmdline, no need to set g:ywvim_dirty_redraw anymore.","3":"1. 改进了popupwin的支持, 在窗口太窄时候选栏自动换行.\r\n1. Improved popupwin feature, autowrap when window is too narrow.\r\n\r\n2. 由于在cmdline输入时无法关闭popwin窗口，取消了cmdline的popupwin支持. 若想体验, 可设置 g:ywvim_popupwin_force_cmdline=1.\r\n2. FIXME Disable popupwin when at cmdline because popupwin can't be closed when inputing at cmdline. You still can have a try the bug, set g:ywvim_popupwin_force_cmdline=1\r\n\r\n3. 修复命令行输入时的显示问题, 不再需要设置ywvim_dirty_redraw.\r\n3. Fixed redrawing issue at cmdline, no need to set g:ywvim_dirty_redraw anymore.","package":"ywvim1.27.zip","4":"ywvim1.27.zip","src_id":"26889","5":"26889","creation_date":"1578087160","6":"1578087160"},{"0":"2662","vim_version":"7.0","1":"7.0","script_version":"1.26","2":"1.26","version_comment":"1. 尝试修复cmdline hit-enter-prompt.\r\n1. Try to prevent hit-enter-prompt.\r\n\r\n2. 智能标点默认关闭。\r\n2. Feature intelligent_punc is off by default.\r\n\r\n3. ywvim_dirty_redraw默认开启。\r\n3. By default g:ywvim_dirty_redraw is on. let g:ywvim_dirty_redraw=1\r\n\r\n4. 支持vim8.2的弹窗特性。感谢QQ KnightG的建议。\r\n4. Added support for popupwin feature of vim 8.2. let g:ywvim_popupwin=1\r\nThanks KnightG at qq.\r\n\r\n5. 默认候选项弹窗为光标跟随。\r\n5. By default popupwin follows cursor. let g:ywvim_popupwin_follow_cursor=1\r\n\r\n6. 默认弹窗候选项水平排列。\r\n6. By default candidates in popupwin arranged horizontally. let g:ywvim_popupwin_horizontal=1","3":"1. 尝试修复cmdline hit-enter-prompt.\r\n1. Try to prevent hit-enter-prompt.\r\n\r\n2. 智能标点默认关闭。\r\n2. Feature intelligent_punc is off by default.\r\n\r\n3. ywvim_dirty_redraw默认开启。\r\n3. By default g:ywvim_dirty_redraw is on. let g:ywvim_dirty_redraw=1\r\n\r\n4. 支持vim8.2的弹窗特性。感谢QQ KnightG的建议。\r\n4. Added support for popupwin feature of vim 8.2. let g:ywvim_popupwin=1\r\nThanks KnightG at qq.\r\n\r\n5. 默认候选项弹窗为光标跟随。\r\n5. By default popupwin follows cursor. let g:ywvim_popupwin_follow_cursor=1\r\n\r\n6. 默认弹窗候选项水平排列。\r\n6. By default candidates in popupwin arranged horizontally. let g:ywvim_popupwin_horizontal=1","package":"ywvim1.26.zip","4":"ywvim1.26.zip","src_id":"26888","5":"26888","creation_date":"1577972644","6":"1577972644"},{"0":"2662","vim_version":"7.0","1":"7.0","script_version":"1.25","2":"1.25","version_comment":"1. 支持智能标点. Added support for intelligent punctuations. let g:ywvim_intelligent_punc=1. let g:ywvim_intelligent_punclist='.,:'\r\n2. 增加特殊符号，可以像普通码元一样有选字栏选多个符号。Added support on SpecialPunctuation= in mabiao file to allow the punctation treated as normal code.\r\n3. 增加普通模式的切换键。Added key mapping to toggle im in normal mode. <C-\\>\r\n4. 增加选项解决cmdline选字栏显示问题。Added option g:ywvim_dirty_redraw to dirty fix the display on cmdline.\r\n5. 修复\\键bug。fixed bug of mapping \\. thanks zcallme & wuming.\r\n6. 解决replace模式时选字栏的残留问题。Fixed the candidate bar doesn't disappear properly when in repace mode. Thanks KnightG.","3":"1. 支持智能标点. Added support for intelligent punctuations. let g:ywvim_intelligent_punc=1. let g:ywvim_intelligent_punclist='.,:'\r\n2. 增加特殊符号，可以像普通码元一样有选字栏选多个符号。Added support on SpecialPunctuation= in mabiao file to allow the punctation treated as normal code.\r\n3. 增加普通模式的切换键。Added key mapping to toggle im in normal mode. <C-\\>\r\n4. 增加选项解决cmdline选字栏显示问题。Added option g:ywvim_dirty_redraw to dirty fix the display on cmdline.\r\n5. 修复\\键bug。fixed bug of mapping \\. thanks zcallme & wuming.\r\n6. 解决replace模式时选字栏的残留问题。Fixed the candidate bar doesn't disappear properly when in repace mode. Thanks KnightG.","package":"ywvim1.25.zip","4":"ywvim1.25.zip","src_id":"26267","5":"26267","creation_date":"1541840085","6":"1541840085"},{"0":"2662","vim_version":"7.0","1":"7.0","script_version":"1.14","2":"1.14","version_comment":"增加仓颉3码表。Added cangjie3 mabiao. Thanks Arthurmcarthur.\r\n","3":"增加仓颉3码表。Added cangjie3 mabiao. Thanks Arthurmcarthur.\r\n","package":"ywvim_mb-1.14.zip","4":"ywvim_mb-1.14.zip","src_id":"26266","5":"26266","creation_date":"1541838641","6":"1541838641"},{"0":"2662","vim_version":"7.0","1":"7.0","script_version":"1.24","2":"1.24","version_comment":"fixed keymapping bug for option ywvim_esc_autoff. 修复ywvim_esc_autoff的bug,感谢wuming的反馈。","3":"fixed keymapping bug for option ywvim_esc_autoff. 修复ywvim_esc_autoff的bug,感谢wuming的反馈。","package":"ywvim1.24.zip","4":"ywvim1.24.zip","src_id":"22903","5":"22903","creation_date":"1423639877","6":"1423639877"},{"0":"2662","vim_version":"7.0","1":"7.0","script_version":"1.23","2":"1.23","version_comment":"1. 增加输入法切换键 <C-@>。Added imap\/cmap <C-@> for im switching.\r\n2. 修正 Replacing 模式下的 bug。Fixed bug of Replacing mode.\r\n3. 重写了中文补全模块。Rewritten IM module.\r\n4. 重写 gb2312 模块(慢),只在 utf-8 下工作。Improved GB2312 filter module (but slow!), only work for &encoding == 'utf-8'.\r\n5. 修正 -More- 和 hit-enter-prompt 的提示。Fixed unexpected messges of -More- and hit-enter-prompt.\r\n6. 修正进入新 buffer 时,状态栏中 (lang) 的错误提示。Fixed statusbar's bug of (lang) in new buffer.\r\n7. 在输入法设置项中增加候选项数目。Added UI setting for candidate length.\r\n8. 增加选项:g:ywvim_theme,改善输入栏显示。Added option g:ywvim_theme, improved IM bar displaying.\r\n9. 其它修复和改进。Many other bug fixes and improvements.","3":"1. 增加输入法切换键 <C-@>。Added imap\/cmap <C-@> for im switching.\r\n2. 修正 Replacing 模式下的 bug。Fixed bug of Replacing mode.\r\n3. 重写了中文补全模块。Rewritten IM module.\r\n4. 重写 gb2312 模块(慢),只在 utf-8 下工作。Improved GB2312 filter module (but slow!), only work for &encoding == 'utf-8'.\r\n5. 修正 -More- 和 hit-enter-prompt 的提示。Fixed unexpected messges of -More- and hit-enter-prompt.\r\n6. 修正进入新 buffer 时,状态栏中 (lang) 的错误提示。Fixed statusbar's bug of (lang) in new buffer.\r\n7. 在输入法设置项中增加候选项数目。Added UI setting for candidate length.\r\n8. 增加选项:g:ywvim_theme,改善输入栏显示。Added option g:ywvim_theme, improved IM bar displaying.\r\n9. 其它修复和改进。Many other bug fixes and improvements.","package":"ywvim1.23.zip","4":"ywvim1.23.zip","src_id":"21747","5":"21747","creation_date":"1396916242","6":"1396916242"},{"0":"2662","vim_version":"7.0","1":"7.0","script_version":"1.22","2":"1.22","version_comment":"1) 修复了 buffer encoding 改变时不工作。\r\nFixed not working when buffer encoding changed.\r\n2) 改善了插入模式下 cmdheight 改变时的使用。\r\nImproved usage when cmdheight changed in insert mode.\r\n3) 修复 g:ywuvim_lockb 特性。\r\nFixed g:ywuvim_lockb feature.\r\n4) 修复对以符号 (`, \\) 作为临时输入拼音键的支持。\r\nFixed support to use symbols as pychar support (`, \\).\r\n5) 增加用 0 键取消当前中文输入(感谢蒋国华的补丁)。\r\nAdded: key 0 to cancel Chinese input (Thanks 蒋国华's patch).\r\n6) 改善:防止当取消当前中文输入后会使当前文件被改变(感谢蒋国华的补丁)。\r\nImproved: Prevent file from getting modified if a Chinese input was canceled (Thanks 蒋国华's patch).","3":"1) 修复了 buffer encoding 改变时不工作。\r\nFixed not working when buffer encoding changed.\r\n2) 改善了插入模式下 cmdheight 改变时的使用。\r\nImproved usage when cmdheight changed in insert mode.\r\n3) 修复 g:ywuvim_lockb 特性。\r\nFixed g:ywuvim_lockb feature.\r\n4) 修复对以符号 (`, \\) 作为临时输入拼音键的支持。\r\nFixed support to use symbols as pychar support (`, \\).\r\n5) 增加用 0 键取消当前中文输入(感谢蒋国华的补丁)。\r\nAdded: key 0 to cancel Chinese input (Thanks 蒋国华's patch).\r\n6) 改善:防止当取消当前中文输入后会使当前文件被改变(感谢蒋国华的补丁)。\r\nImproved: Prevent file from getting modified if a Chinese input was canceled (Thanks 蒋国华's patch).","package":"ywvim1.22.zip","4":"ywvim1.22.zip","src_id":"18941","5":"18941","creation_date":"1351908932","6":"1351908932"},{"0":"2662","vim_version":"7.0","1":"7.0","script_version":"1.21","2":"1.21","version_comment":"1. 修正缺失 g2b.ywvim 和 gb2312.ywvim 文件时导致的错误, 谢谢 Pan Shizhu 的指正.\r\n1. Fixed error when no g2b.ywvim and gb2312.ywvim existed, thanks Pan Shizhu for the report.\r\n\r\n2. 修正 '\"\\ 不能正常工作。\r\n2. Fixed not working keys ('\"\\).\r\n\r\n3. 变量名称改变:g:ywvim_pagec -> g:ywvim_circlecandidates. maxelement -> maxphraselength. PageUpExtraKeys -> AltPageUpKeys, PageDnExtraKeys -> AltPageDnkeys.\r\n3. Variables' name changed: g:ywvim_pagec -> g:ywvim_circlecandidates. maxelement -> maxphraselength. PageUpExtraKeys -> AltPageUpKeys, PageDnExtraKeys -> AltPageDnkeys.\r\n\r\n4. 设置 'cmdheight' 防止 hit-enter-prompt.\r\n4. Set the 'cmdheight' to prevent hit-enter-prompt.\r\n\r\n5. 修正汉字上屏后的屏幕闪动。\r\n5. Fixed refreshing the screen after inputing.\r\n\r\n6. 增加切换输入法快捷键 <C-S-Space>。\r\n6. Added keymap <C-S-Space> to invoke ywvim.\r\n\r\n7. 改善对非 UTF8 编码系统的支持。\r\n7. Improved support for non-utf8 encodings.\r\n\r\n8. 其他改善和修正。\r\n8. Other impovements and bug fixings.","3":"1. 修正缺失 g2b.ywvim 和 gb2312.ywvim 文件时导致的错误, 谢谢 Pan Shizhu 的指正.\r\n1. Fixed error when no g2b.ywvim and gb2312.ywvim existed, thanks Pan Shizhu for the report.\r\n\r\n2. 修正 '\"\\ 不能正常工作。\r\n2. Fixed not working keys ('\"\\).\r\n\r\n3. 变量名称改变:g:ywvim_pagec -> g:ywvim_circlecandidates. maxelement -> maxphraselength. PageUpExtraKeys -> AltPageUpKeys, PageDnExtraKeys -> AltPageDnkeys.\r\n3. Variables' name changed: g:ywvim_pagec -> g:ywvim_circlecandidates. maxelement -> maxphraselength. PageUpExtraKeys -> AltPageUpKeys, PageDnExtraKeys -> AltPageDnkeys.\r\n\r\n4. 设置 'cmdheight' 防止 hit-enter-prompt.\r\n4. Set the 'cmdheight' to prevent hit-enter-prompt.\r\n\r\n5. 修正汉字上屏后的屏幕闪动。\r\n5. Fixed refreshing the screen after inputing.\r\n\r\n6. 增加切换输入法快捷键 <C-S-Space>。\r\n6. Added keymap <C-S-Space> to invoke ywvim.\r\n\r\n7. 改善对非 UTF8 编码系统的支持。\r\n7. Improved support for non-utf8 encodings.\r\n\r\n8. 其他改善和修正。\r\n8. Other impovements and bug fixings.","package":"ywvim.vim_1.21.zip","4":"ywvim.vim_1.21.zip","src_id":"18177","5":"18177","creation_date":"1340353941","6":"1340353941"},{"0":"2662","vim_version":"7.0","1":"7.0","script_version":"1.20","2":"1.20","version_comment":"为\"空码不锁键盘\"优化了快捷键<C-w>的表现.\r\nImproved key map <C-w> behavior for the 'unlocked keyboard'.","3":"为\"空码不锁键盘\"优化了快捷键<C-w>的表现.\r\nImproved key map <C-w> behavior for the 'unlocked keyboard'.","package":"ywvim.vim_1.20.tar.bz2","4":"ywvim.vim_1.20.tar.bz2","src_id":"11117","5":"11117","creation_date":"1249183810","6":"1249183810"},{"0":"2662","vim_version":"7.0","1":"7.0","script_version":"1.19","2":"1.19","version_comment":"增加 added:\r\n1. 默认的简繁转换方向. Preferred simplified-traditonal conv direction: \r\n    let g:ywvim_preconv = 'g2b'\r\n2. 空码时不锁定键盘设置. Don't lock keyboard when no matched:\r\n    let g:ywvim_lockb = 0","3":"增加 added:\r\n1. 默认的简繁转换方向. Preferred simplified-traditonal conv direction: \r\n    let g:ywvim_preconv = 'g2b'\r\n2. 空码时不锁定键盘设置. Don't lock keyboard when no matched:\r\n    let g:ywvim_lockb = 0","package":"ywvim.vim_1.19.tar.bz2","4":"ywvim.vim_1.19.tar.bz2","src_id":"11116","5":"11116","creation_date":"1249116017","6":"1249116017"},{"0":"2662","vim_version":"7.0","1":"7.0","script_version":"1.18","2":"1.18","version_comment":"解决了 enmode 与中文标点冲突 bug.\r\nWorkaround for enmode conflicts with Chinese punctuations' bug.","3":"解决了 enmode 与中文标点冲突 bug.\r\nWorkaround for enmode conflicts with Chinese punctuations' bug.","package":"ywvim.vim-1.18.tar.bz2","4":"ywvim.vim-1.18.tar.bz2","src_id":"11063","5":"11063","creation_date":"1248499253","6":"1248499253"},{"0":"2662","vim_version":"7.0","1":"7.0","script_version":"1.17","2":"1.17","version_comment":"1. 修正在 windows 上的命令行显示 bug.\r\n(感谢在 newsmth.net 上的 vace 的报告)\r\n2. g:ywvim_chinesepunc 改名为 g:ywvim_zhpunc.\r\n\r\n1. Fix cmdline display bug on windows.\r\n(Thanks to vace on newsmth.net who catch this bug.)\r\n2. g:ywvim_chinesepunc was renamed to g:ywvim_zhpunc.","3":"1. 修正在 windows 上的命令行显示 bug.\r\n(感谢在 newsmth.net 上的 vace 的报告)\r\n2. g:ywvim_chinesepunc 改名为 g:ywvim_zhpunc.\r\n\r\n1. Fix cmdline display bug on windows.\r\n(Thanks to vace on newsmth.net who catch this bug.)\r\n2. g:ywvim_chinesepunc was renamed to g:ywvim_zhpunc.","package":"ywvim.vim-1.17.tar.bz2","4":"ywvim.vim-1.17.tar.bz2","src_id":"10890","5":"10890","creation_date":"1245832721","6":"1245832721"},{"0":"2662","vim_version":"7.0","1":"7.0","script_version":"1.16","2":"1.16","version_comment":"绕过在 windows 下的 E341 的 bug(这是 vim 的 bug..).\r\nAvoid bug of E341 on windows.(It's a vim's bug..).","3":"绕过在 windows 下的 E341 的 bug(这是 vim 的 bug..).\r\nAvoid bug of E341 on windows.(It's a vim's bug..).","package":"ywvim.vim-1.16.tar.bz2","4":"ywvim.vim-1.16.tar.bz2","src_id":"10798","5":"10798","creation_date":"1244679604","6":"1244679604"},{"0":"2662","vim_version":"7.0","1":"7.0","script_version":"1.15","2":"1.15","version_comment":"1. 修复非插入模式依赖于插入模式的 bug. 现在可以随时随地在任何模式使用 ywvim 了!\r\nFixed non insert mode depended on insert mode's bug, now you can toggle ywvim unlimitedly in every mode as you like!\r\n\r\n2. 改善了在非插入模式时的显示.\r\nImproved displaying when in non insert modes.","3":"1. 修复非插入模式依赖于插入模式的 bug. 现在可以随时随地在任何模式使用 ywvim 了!\r\nFixed non insert mode depended on insert mode's bug, now you can toggle ywvim unlimitedly in every mode as you like!\r\n\r\n2. 改善了在非插入模式时的显示.\r\nImproved displaying when in non insert modes.","package":"ywvim.vim-1.15.tar.bz2","4":"ywvim.vim-1.15.tar.bz2","src_id":"10792","5":"10792","creation_date":"1244564792","6":"1244564792"},{"0":"2662","vim_version":"7.0","1":"7.0","script_version":"1.14","2":"1.14","version_comment":"修复简繁转换在非 utf-8 下失效问题.\r\n(感谢在 newsmth.net 上的 vace 的报告)\r\n\r\nFixed Sim. <-> Trad. can't work on non utf-8 encoding.\r\n(Thanks to vace on newsmth.net who catch this bug.)","3":"修复简繁转换在非 utf-8 下失效问题.\r\n(感谢在 newsmth.net 上的 vace 的报告)\r\n\r\nFixed Sim. <-> Trad. can't work on non utf-8 encoding.\r\n(Thanks to vace on newsmth.net who catch this bug.)","package":"ywvim.vim-1.14.tar.bz2","4":"ywvim.vim-1.14.tar.bz2","src_id":"10788","5":"10788","creation_date":"1244546824","6":"1244546824"},{"0":"2662","vim_version":"7.0","1":"7.0","script_version":"1.13","2":"1.13","version_comment":"1. g:ywvim_helpmbstatus 改名为 g:ywvim_helpim_on.\r\n1. g:ywvim_helpmbstatus is renamed to g:ywvim_helpim_on.\r\n\r\n2. 改善了状态栏的颜色显示效果.\r\n2. Improved some hightlights of statusline.","3":"1. g:ywvim_helpmbstatus 改名为 g:ywvim_helpim_on.\r\n1. g:ywvim_helpmbstatus is renamed to g:ywvim_helpim_on.\r\n\r\n2. 改善了状态栏的颜色显示效果.\r\n2. Improved some hightlights of statusline.","package":"ywvim.vim-1.13.tar.bz2","4":"ywvim.vim-1.13.tar.bz2","src_id":"10787","5":"10787","creation_date":"1244544986","6":"1244544986"},{"0":"2662","vim_version":"7.0","1":"7.0","script_version":"1.13","2":"1.13","version_comment":"码表更新!\r\ng2b.ywvim 简繁词量增加 2466 -> 3145.\r\n(感谢在 newsmth.net 上的 vace 提供信息)\r\nMabiao updated!\r\nNumber of g2b.ywvim's charcotr 2466 -> 3145.\r\n(Thanks for vace on newsmth.net's info.)","3":"码表更新!\r\ng2b.ywvim 简繁词量增加 2466 -> 3145.\r\n(感谢在 newsmth.net 上的 vace 提供信息)\r\nMabiao updated!\r\nNumber of g2b.ywvim's charcotr 2466 -> 3145.\r\n(Thanks for vace on newsmth.net's info.)","package":"ywvim_mb-1.13.tar.bz2","4":"ywvim_mb-1.13.tar.bz2","src_id":"10786","5":"10786","creation_date":"1244544938","6":"1244544938"},{"0":"2662","vim_version":"7.0","1":"7.0","script_version":"1.12","2":"1.12","version_comment":"修复 简繁转换 bug.\r\n(感谢在 newsmth.net 上的 vace 的反饋)\r\nfixed bug on Sim. -> Tra.\r\n(Thanks to vace on newsmth.net who catch this bug.)","3":"修复 简繁转换 bug.\r\n(感谢在 newsmth.net 上的 vace 的反饋)\r\nfixed bug on Sim. -> Tra.\r\n(Thanks to vace on newsmth.net who catch this bug.)","package":"ywvim.vim-1.12.tar.bz2","4":"ywvim.vim-1.12.tar.bz2","src_id":"10783","5":"10783","creation_date":"1244500931","6":"1244500931"},{"0":"2662","vim_version":"7.0","1":"7.0","script_version":"1.11","2":"1.11","version_comment":"1. 取消 g:ywvim_whitelstfile, 取消码表级别变量: whitelstfile, wlst. 增加 g:ywvim_gb 和码表级别变量 gb.\r\n1. Abandon g:ywvim_whitelstfile, abandon local varible: whitelstfile, wlst. added g:ywvim_gb and local variable gb.\r\n\r\n2. added g:ywvim_conv.\r\n2. added g:ywvim_conv.\r\n\r\n3. 取消 <C-m> 切换白名单. 增加 <C-^> g 切换 gb\/gbk.\r\n3. Adandon: <C-m> for toggling white list. Added <C-^> g to toggle gb\/gbk.\r\n\r\n4. 修复 gbk encoding 输入法名称乱码 bug.\r\n(感谢在 www.newsmth.net 上的 vace 反馈)\r\n4. Fix bug on gbk encoding.\r\n(Thanks for vace on www.newsmth.net's report.)\r\n","3":"1. 取消 g:ywvim_whitelstfile, 取消码表级别变量: whitelstfile, wlst. 增加 g:ywvim_gb 和码表级别变量 gb.\r\n1. Abandon g:ywvim_whitelstfile, abandon local varible: whitelstfile, wlst. added g:ywvim_gb and local variable gb.\r\n\r\n2. added g:ywvim_conv.\r\n2. added g:ywvim_conv.\r\n\r\n3. 取消 <C-m> 切换白名单. 增加 <C-^> g 切换 gb\/gbk.\r\n3. Adandon: <C-m> for toggling white list. Added <C-^> g to toggle gb\/gbk.\r\n\r\n4. 修复 gbk encoding 输入法名称乱码 bug.\r\n(感谢在 www.newsmth.net 上的 vace 反馈)\r\n4. Fix bug on gbk encoding.\r\n(Thanks for vace on www.newsmth.net's report.)\r\n","package":"ywvim.vim-1.11.tar.bz2","4":"ywvim.vim-1.11.tar.bz2","src_id":"10782","5":"10782","creation_date":"1244496721","6":"1244496721"},{"0":"2662","vim_version":"7.0","1":"7.0","script_version":"1.11","2":"1.11","version_comment":"碼表更新!\r\nmabiao updated!\r\n增加 g2b.ywvim, 簡繁轉換訶典.\r\nAdd a g2b.ywvim, for converting between Simplified and Traditional Chinese.","3":"碼表更新!\r\nmabiao updated!\r\n增加 g2b.ywvim, 簡繁轉換訶典.\r\nAdd a g2b.ywvim, for converting between Simplified and Traditional Chinese.","package":"ywvim_mb-1.11.tar.bz2","4":"ywvim_mb-1.11.tar.bz2","src_id":"10781","5":"10781","creation_date":"1244496674","6":"1244496674"},{"0":"2662","vim_version":"7.0","1":"7.0","script_version":"1.10","2":"1.10","version_comment":"1. <C-m> 切换白名单.\r\n1. <C-m> toggles whitelist.\r\n\r\n2. 状态栏输入法名称用不同颜色提示白名单开启状态.\r\n(感谢在 newsmth.net 上的 vace 提供的建议)\r\n2. use different color for differ the status of whitelist.\r\n(Thanks for vace on newsmth.net's suggestion.)\r\n\r\n3. 修复 windowns gbk 环境乱码.\r\n3. fix garbled charactor on windows gbk encoding.","3":"1. <C-m> 切换白名单.\r\n1. <C-m> toggles whitelist.\r\n\r\n2. 状态栏输入法名称用不同颜色提示白名单开启状态.\r\n(感谢在 newsmth.net 上的 vace 提供的建议)\r\n2. use different color for differ the status of whitelist.\r\n(Thanks for vace on newsmth.net's suggestion.)\r\n\r\n3. 修复 windowns gbk 环境乱码.\r\n3. fix garbled charactor on windows gbk encoding.","package":"ywvim.vim-1.10.tar.bz2","4":"ywvim.vim-1.10.tar.bz2","src_id":"10771","5":"10771","creation_date":"1244441979","6":"1244441979"},{"0":"2662","vim_version":"7.0","1":"7.0","script_version":"1.9","2":"1.9","version_comment":"1. g:ywvim_ims 的格式改变, 请务必要更改格式(详见说明)!\r\n1. Format of g:ywvim_ims has been changed, you must adjust it!\r\n\r\n2. 可以单独设置每个码表的参数. 码表级别优先(详见说明).\r\n2. Most variables can be locale on IM now.\r\n\r\n3. 增加 g:ywvim_wlst_on, 控制白名单开关.\r\nAdded g:ywvim_wlst_on, for controling while list support.\r\n\r\n4. 增加 g:ywvim_whitelstfile, 设置白名件文件.\r\nAdded g:ywvim_whitelstfile, for setup while list file.\r\n\r\n5. 修复精确匹配开启时的空码输出出错的 bug.\r\nfixed a bug which is introduce from matchexact.","3":"1. g:ywvim_ims 的格式改变, 请务必要更改格式(详见说明)!\r\n1. Format of g:ywvim_ims has been changed, you must adjust it!\r\n\r\n2. 可以单独设置每个码表的参数. 码表级别优先(详见说明).\r\n2. Most variables can be locale on IM now.\r\n\r\n3. 增加 g:ywvim_wlst_on, 控制白名单开关.\r\nAdded g:ywvim_wlst_on, for controling while list support.\r\n\r\n4. 增加 g:ywvim_whitelstfile, 设置白名件文件.\r\nAdded g:ywvim_whitelstfile, for setup while list file.\r\n\r\n5. 修复精确匹配开启时的空码输出出错的 bug.\r\nfixed a bug which is introduce from matchexact.","package":"ywvim.vim-1.9.tar.bz2","4":"ywvim.vim-1.9.tar.bz2","src_id":"10770","5":"10770","creation_date":"1244391750","6":"1244391750"},{"0":"2662","vim_version":"7.0","1":"7.0","script_version":"1.8","2":"1.8","version_comment":"1. 去掉从中文标点转到英文标点错误的虫子.\r\n(感谢在 #arch-cn@irc.oftc.net 上的 medicalwei 提供的信息.)\r\n1. Fix a bug when switch punctuation from chinese to English.\r\n(Thanks for medicalwei on #arch-cn@irc.oftc.net's catch.)\r\n\r\n2. 增加只显示全码匹配的字 let g:ywvim_matchexact = 1\r\n2. Add a feature for showing the exact matched Chinese. g:ywvim_matchexact = 1.\r\n\r\n3. 增加中文字母显示支持: let g:ywvim_chinesecode = 1\r\n3. Add a feature for displaying Chinese alphabets instead of English.","3":"1. 去掉从中文标点转到英文标点错误的虫子.\r\n(感谢在 #arch-cn@irc.oftc.net 上的 medicalwei 提供的信息.)\r\n1. Fix a bug when switch punctuation from chinese to English.\r\n(Thanks for medicalwei on #arch-cn@irc.oftc.net's catch.)\r\n\r\n2. 增加只显示全码匹配的字 let g:ywvim_matchexact = 1\r\n2. Add a feature for showing the exact matched Chinese. g:ywvim_matchexact = 1.\r\n\r\n3. 增加中文字母显示支持: let g:ywvim_chinesecode = 1\r\n3. Add a feature for displaying Chinese alphabets instead of English.","package":"ywvim.vim-1.8.tar.bz2","4":"ywvim.vim-1.8.tar.bz2","src_id":"10763","5":"10763","creation_date":"1244358759","6":"1244358759"},{"0":"2662","vim_version":"7.0","1":"7.0","script_version":"1.8","2":"1.8","version_comment":"码表更新.\r\n1. 增加了 [CharDefinition] 区域.\r\nAdded a field of [CharDefinition].","3":"码表更新.\r\n1. 增加了 [CharDefinition] 区域.\r\nAdded a field of [CharDefinition].","package":"ywvim_mb-1.8.tar.bz2","4":"ywvim_mb-1.8.tar.bz2","src_id":"10762","5":"10762","creation_date":"1244358458","6":"1244358458"},{"0":"2662","vim_version":"7.0","1":"7.0","script_version":"1.7","2":"1.7","version_comment":"1. 修复了 g:ywvim_autoinput 在注音上的 bug. (感谢在 #arch@irc.oftc.net 上的 medicalwei 提供的线索)\r\n1. Fix g:ywvim_autoinput bug when using zhuyin.(Thanks to medicalwei on #arch-cn@irc.oftc.net who catch this bug.)\r\n\r\n2. g:ywvim_autoinput 现在支持两种程度的自动模式. 设为 2 为重度自动, 任何单码字都自动上屏. 2 为中度自动, 只在翻页时出现的单码字才上屏.\r\n2. g:ywvim_autoinput now supports two extends of auto input, set it to 2 is high auto, every singe candiate is auto inputted, 1 is media auto, just auto input when pageup\/down.","3":"1. 修复了 g:ywvim_autoinput 在注音上的 bug. (感谢在 #arch@irc.oftc.net 上的 medicalwei 提供的线索)\r\n1. Fix g:ywvim_autoinput bug when using zhuyin.(Thanks to medicalwei on #arch-cn@irc.oftc.net who catch this bug.)\r\n\r\n2. g:ywvim_autoinput 现在支持两种程度的自动模式. 设为 2 为重度自动, 任何单码字都自动上屏. 2 为中度自动, 只在翻页时出现的单码字才上屏.\r\n2. g:ywvim_autoinput now supports two extends of auto input, set it to 2 is high auto, every singe candiate is auto inputted, 1 is media auto, just auto input when pageup\/down.","package":"ywvim.vim-1.7.tar.bz2","4":"ywvim.vim-1.7.tar.bz2","src_id":"10760","5":"10760","creation_date":"1244346281","6":"1244346281"},{"0":"2662","vim_version":"7.0","1":"7.0","script_version":"1.7","2":"1.7","version_comment":"Mabiaos are packed by tar and bzip.","3":"Mabiaos are packed by tar and bzip.","package":"ywvim_mb-1.7.tar.bz2","4":"ywvim_mb-1.7.tar.bz2","src_id":"10759","5":"10759","creation_date":"1244345933","6":"1244345933"},{"0":"2662","vim_version":"7.0","1":"7.0","script_version":"1.6","2":"1.6","version_comment":"1. 废除 g:ywvim_phasemaxlen.\r\n1. abandon g:ywvim_phasemaxlen.\r\n\r\n2. 增加 g:ywvim_helpmbstatus 控制反查码表开启.\r\n2. Add g:ywvim_helpmbstatus for controling help mabiao.\r\n\r\n3. 增加 ; 选择第二候选词功能.\r\n3. Add using ; to select the second candiate.","3":"1. 废除 g:ywvim_phasemaxlen.\r\n1. abandon g:ywvim_phasemaxlen.\r\n\r\n2. 增加 g:ywvim_helpmbstatus 控制反查码表开启.\r\n2. Add g:ywvim_helpmbstatus for controling help mabiao.\r\n\r\n3. 增加 ; 选择第二候选词功能.\r\n3. Add using ; to select the second candiate.","package":"ywvim.vim-1.6.rar","4":"ywvim.vim-1.6.rar","src_id":"10758","5":"10758","creation_date":"1244340267","6":"1244340267"},{"0":"2662","vim_version":"7.0","1":"7.0","script_version":"1.6","2":"1.6","version_comment":"1. 码表更新.\r\n增加 MaxElement 的支持. 需要全局改变最大词长设置的请修改这行, 临时改变可以通过 <C-^> 设置.\r\n1. mabiao updated.\r\nadd MaxElement support, now you need to modify this line for changing global setting for max phase length, for local setting, use <C-^>.\r\n\r\n2. 修改了行列码表的错误.\r\n2. fix bug in arrary30.ywvim.\r\n\r\n3. 在码表的每一行增加一个空格暂时解决反查码表不能在非 utf-8 下工作的问题.\r\n3. Add a space in each line for dirty workaround help mabiao not working on non-utf8 encoding.","3":"1. 码表更新.\r\n增加 MaxElement 的支持. 需要全局改变最大词长设置的请修改这行, 临时改变可以通过 <C-^> 设置.\r\n1. mabiao updated.\r\nadd MaxElement support, now you need to modify this line for changing global setting for max phase length, for local setting, use <C-^>.\r\n\r\n2. 修改了行列码表的错误.\r\n2. fix bug in arrary30.ywvim.\r\n\r\n3. 在码表的每一行增加一个空格暂时解决反查码表不能在非 utf-8 下工作的问题.\r\n3. Add a space in each line for dirty workaround help mabiao not working on non-utf8 encoding.","package":"ywvim_mb-1.6.rar","4":"ywvim_mb-1.6.rar","src_id":"10757","5":"10757","creation_date":"1244340106","6":"1244340106"},{"0":"2662","vim_version":"7.0","1":"7.0","script_version":"1.5","2":"1.5","version_comment":"1. Add let g:ywvim_autoinput = 1\r\n    auto input the only candidate.\r\n    增加自动上屏选项.\r\n2. Add let g:ywvim_pagec = 1\r\n    circle pageup\/pagedown.\r\n    增加翻页循环.","3":"1. Add let g:ywvim_autoinput = 1\r\n    auto input the only candidate.\r\n    增加自动上屏选项.\r\n2. Add let g:ywvim_pagec = 1\r\n    circle pageup\/pagedown.\r\n    增加翻页循环.","package":"ywvim.vim-1.5.tar.bz2","4":"ywvim.vim-1.5.tar.bz2","src_id":"10753","5":"10753","creation_date":"1244275450","6":"1244275450"},{"0":"2662","vim_version":"7.0","1":"7.0","script_version":"1.4","2":"1.4","version_comment":"1. 注音 support is added.\r\n   增加注音支持.\r\n2. Support for new options in mabiao is added.\r\n   支持新增的码表选项.","3":"1. 注音 support is added.\r\n   增加注音支持.\r\n2. Support for new options in mabiao is added.\r\n   支持新增的码表选项.","package":"ywvim.vim_1.4.tar.bz2","4":"ywvim.vim_1.4.tar.bz2","src_id":"10752","5":"10752","creation_date":"1244271971","6":"1244271971"},{"0":"2662","vim_version":"7.0","1":"7.0","script_version":"1.4","2":"1.4","version_comment":"1. 注音 mabiao is added.\r\n    增加了注音码表的支持.\r\n2. mabiao file supports more options:\r\n    码表文件支持更多的选项:\r\nEndCodes=\r\nInputZhKeys=\r\nInputEnKeys=\r\nPageUpExtraKeys=\r\nPageDnExtraKeys=","3":"1. 注音 mabiao is added.\r\n    增加了注音码表的支持.\r\n2. mabiao file supports more options:\r\n    码表文件支持更多的选项:\r\nEndCodes=\r\nInputZhKeys=\r\nInputEnKeys=\r\nPageUpExtraKeys=\r\nPageDnExtraKeys=","package":"ywvim_mb_1.4.tar.bz2","4":"ywvim_mb_1.4.tar.bz2","src_id":"10751","5":"10751","creation_date":"1244271838","6":"1244271838"},{"0":"2662","vim_version":"7.0","1":"7.0","script_version":"1.3","2":"1.3","version_comment":"(1) remove the limitation of whitelist only works for utf-8 encoding.\r\n去除了白名单的 utf-8 encoding 限制.\r\n(2) Fixed bug that whitelist has no effect.\r\n去除了白名单失效的虫子.\r\n","3":"(1) remove the limitation of whitelist only works for utf-8 encoding.\r\n去除了白名单的 utf-8 encoding 限制.\r\n(2) Fixed bug that whitelist has no effect.\r\n去除了白名单失效的虫子.\r\n","package":"ywvim.vim-1.3.tar.bz2","4":"ywvim.vim-1.3.tar.bz2","src_id":"10747","5":"10747","creation_date":"1244217636","6":"1244217636"},{"0":"2662","vim_version":"7.0","1":"7.0","script_version":"1.2","2":"1.2","version_comment":"Add an option: g:ywvim_esc_autoff, now you can set it to 1 to let vim auto toggle the IM to be off when escape from insert mode.","3":"Add an option: g:ywvim_esc_autoff, now you can set it to 1 to let vim auto toggle the IM to be off when escape from insert mode.","package":"ywvim.vim-1.2.tar.bz2","4":"ywvim.vim-1.2.tar.bz2","src_id":"10744","5":"10744","creation_date":"1244208117","6":"1244208117"},{"0":"2662","vim_version":"7.0","1":"7.0","script_version":"1.1","2":"1.1","version_comment":"format of g:ywvim_ims has been changed for convenient usage.","3":"format of g:ywvim_ims has been changed for convenient usage.","package":"ywvim.vim-1.1.tar.bz2","4":"ywvim.vim-1.1.tar.bz2","src_id":"10742","5":"10742","creation_date":"1244204806","6":"1244204806"}]},"2661":{"script_id":"2661","0":"2661","script_name":"plumbing.vim","1":"plumbing.vim","script_type":"syntax","2":"syntax","summary":"Syntax highlighting for Plan 9 plumbing files","3":"Syntax highlighting for Plan 9 plumbing files","description":"This script will color highlight Plan 9's plumber configuration files (plumbing).\r\n\r\nAll of the different elements of a plumbing file can be colored separately, per your own preference.  Here is an example:\r\n\r\nhttp:\/\/img194.imageshack.us\/img194\/4161\/plumbingvimsyntax.png","4":"This script will color highlight Plan 9's plumber configuration files (plumbing).\r\n\r\nAll of the different elements of a plumbing file can be colored separately, per your own preference.  Here is an example:\r\n\r\nhttp:\/\/img194.imageshack.us\/img194\/4161\/plumbingvimsyntax.png","install_details":"1 - Put the plumbing.vim file in to your $HOME\/.vim\/after\/syntax directory.\r\n2 - Put this line in to your $HOME\/.vimrc:\r\n\r\n     set syntax on\r\n\r\n3 - Put the following line in your plumbing file:\r\n\r\n     # vim: filetype=plumbing\r\n\r\n4 - Quit and restart vim","5":"1 - Put the plumbing.vim file in to your $HOME\/.vim\/after\/syntax directory.\r\n2 - Put this line in to your $HOME\/.vimrc:\r\n\r\n     set syntax on\r\n\r\n3 - Put the following line in your plumbing file:\r\n\r\n     # vim: filetype=plumbing\r\n\r\n4 - Quit and restart vim","first_name":"Gnosis","6":"Gnosis","last_name":"Ouroubouros","7":"Ouroubouros","releases":[{"0":"2661","vim_version":"7.0","1":"7.0","script_version":"1.2","2":"1.2","version_comment":"Two bugfixes: 1 - variables werent' being highlighted separately when part of a \"start\" verb.  2 - the arguments to the \"isFile\" verb weren't being highlighted at all.","3":"Two bugfixes: 1 - variables werent' being highlighted separately when part of a \"start\" verb.  2 - the arguments to the \"isFile\" verb weren't being highlighted at all.","package":"plumbing.vim","4":"plumbing.vim","src_id":"10735","5":"10735","creation_date":"1244140058","6":"1244140058"},{"0":"2661","vim_version":"7.0","1":"7.0","script_version":"1.1","2":"1.1","version_comment":"Fixed a minor bug that was keep variables from being highlighted separately when they were part of the arguments to the \"set\" verb.","3":"Fixed a minor bug that was keep variables from being highlighted separately when they were part of the arguments to the \"set\" verb.","package":"plumbing.vim","4":"plumbing.vim","src_id":"10734","5":"10734","creation_date":"1244139007","6":"1244139007"},{"0":"2661","vim_version":"7.2","1":"7.2","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"plumbing.vim","4":"plumbing.vim","src_id":"10732","5":"10732","creation_date":"1244137376","6":"1244137376"}]},"2660":{"script_id":"2660","0":"2660","script_name":"clips.vim","1":"clips.vim","script_type":"syntax","2":"syntax","summary":"Syntax highlighting for CLIPS","3":"Syntax highlighting for CLIPS","description":"Syntax file for CLIPS, C Language Integrated Production System","4":"Syntax file for CLIPS, C Language Integrated Production System","install_details":"put in ~\/.vim\/syntax","5":"put in ~\/.vim\/syntax","first_name":"Artem","6":"Artem","last_name":"Novikov","7":"Novikov","releases":[{"0":"2660","vim_version":"7.0","1":"7.0","script_version":"0.3","2":"0.3","version_comment":"Some changes","3":"Some changes","package":"clips.vim","4":"clips.vim","src_id":"11333","5":"11333","creation_date":"1252287163","6":"1252287163"},{"0":"2660","vim_version":"7.0","1":"7.0","script_version":"0.2","2":"0.2","version_comment":"Some changes","3":"Some changes","package":"clips.vim","4":"clips.vim","src_id":"10709","5":"10709","creation_date":"1243818609","6":"1243818609"},{"0":"2660","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"clips.vim","4":"clips.vim","src_id":"10700","5":"10700","creation_date":"1243575964","6":"1243575964"}]},"2659":{"script_id":"2659","0":"2659","script_name":"g15vim","1":"g15vim","script_type":"utility","2":"utility","summary":"Display on the Logitech G15 keyboard LCD screen.","3":"Display on the Logitech G15 keyboard LCD screen.","description":"This script can display on the Logitech G15 keyboard LCD screen information about the current cursor position (line and col) and the current buffer name.","4":"This script can display on the Logitech G15 keyboard LCD screen information about the current cursor position (line and col) and the current buffer name.","install_details":"Just put the 2 files:\r\n-draw-on-g15\r\n-g15vim.vim\r\ninto the folder ~\/.vim\/plugin\r\n\r\nYou need :\r\n-libg15 1.2.7\r\n-libg15render 1.2\r\n-g15Daemon 1.9.5.3\r\nAll are available on: http:\/\/www.g15tools.com\/\r\n-vim 7.2.018\r\nIt is available on: http:\/\/www.vim.org\/","5":"Just put the 2 files:\r\n-draw-on-g15\r\n-g15vim.vim\r\ninto the folder ~\/.vim\/plugin\r\n\r\nYou need :\r\n-libg15 1.2.7\r\n-libg15render 1.2\r\n-g15Daemon 1.9.5.3\r\nAll are available on: http:\/\/www.g15tools.com\/\r\n-vim 7.2.018\r\nIt is available on: http:\/\/www.vim.org\/","first_name":"YuGiOhJCJ","6":"YuGiOhJCJ","last_name":"YuGiOhJCJ","7":"YuGiOhJCJ","releases":[{"0":"2659","vim_version":"7.2","1":"7.2","script_version":"20110722","2":"20110722","version_comment":"ChangeLog: Respect the GNU Coding Standards. draw-on-g15: Update to draw-on-g15 version 20110716. g15vim.vim: The first message displays the website URL.  g15vim.vim: Add the \":G15vim\" command. gpl-3.0.txt: Rename to COPYING. README: Update the vim version to 7.2.445. README: Explain how to use the new G15vim command. TODO: New file (the things to do for the next releases).","3":"ChangeLog: Respect the GNU Coding Standards. draw-on-g15: Update to draw-on-g15 version 20110716. g15vim.vim: The first message displays the website URL.  g15vim.vim: Add the \":G15vim\" command. gpl-3.0.txt: Rename to COPYING. README: Update the vim version to 7.2.445. README: Explain how to use the new G15vim command. TODO: New file (the things to do for the next releases).","package":"g15vim-20110722.tar.xz","4":"g15vim-20110722.tar.xz","src_id":"16128","5":"16128","creation_date":"1311347719","6":"1311347719"},{"0":"2659","vim_version":"7.0","1":"7.0","script_version":"20090608","2":"20090608","version_comment":"Add ChangeLog file. Redirect the standard error output stream to the null\r\ndevice.","3":"Add ChangeLog file. Redirect the standard error output stream to the null\r\ndevice.","package":"g15vim-20090608.tar.gz","4":"g15vim-20090608.tar.gz","src_id":"10776","5":"10776","creation_date":"1244459991","6":"1244459991"},{"0":"2659","vim_version":"7.2","1":"7.2","script_version":"20090528","2":"20090528","version_comment":"Initial upload","3":"Initial upload","package":"g15vim-20090528.tar.gz","4":"g15vim-20090528.tar.gz","src_id":"10691","5":"10691","creation_date":"1243503115","6":"1243503115"}]},"2658":{"script_id":"2658","0":"2658","script_name":"Auto Changing color script","1":"Auto Changing color script","script_type":"color scheme","2":"color scheme","summary":"Syntax highlight colors change gradually based on minutes of hour","3":"Syntax highlight colors change gradually based on minutes of hour","description":"Why not try my customising Vim help page:\r\nhttp:\/\/www.ezrider.co.uk\/VimTagsHelp\/\r\n\r\nWARNING: script allocates highlight groups over and over if you find colors go black just restart.  You won't lose anything. Normally only happens if you leave script running for hours.\r\n\r\nAim is to make colour schemes liven up by looping colors gently around the hour.  \r\n\r\nPermanent (fixed) scheme takes over when you edit.  By default it's \"darkblue\".  You can have your own:\r\ne.g.\r\n  let permanentColorScheme = \"{YOURFAVCOLORSCHEME}\"\r\n- in your _vimrc makes edit color scheme (before save) {YOURFAVCOLORSCHEME}\r\n\r\nBy default friendly reminders gently remind you about not saving, and not moving for a certain time.\r\nBy default it's 8 minutes.\r\nYou can change it easily:\r\ne.g.\r\n  let n_friendlyReminderTimeout = 30\r\n- in your _vimrc makes it after 30 minutes\r\n","4":"Why not try my customising Vim help page:\r\nhttp:\/\/www.ezrider.co.uk\/VimTagsHelp\/\r\n\r\nWARNING: script allocates highlight groups over and over if you find colors go black just restart.  You won't lose anything. Normally only happens if you leave script running for hours.\r\n\r\nAim is to make colour schemes liven up by looping colors gently around the hour.  \r\n\r\nPermanent (fixed) scheme takes over when you edit.  By default it's \"darkblue\".  You can have your own:\r\ne.g.\r\n  let permanentColorScheme = \"{YOURFAVCOLORSCHEME}\"\r\n- in your _vimrc makes edit color scheme (before save) {YOURFAVCOLORSCHEME}\r\n\r\nBy default friendly reminders gently remind you about not saving, and not moving for a certain time.\r\nBy default it's 8 minutes.\r\nYou can change it easily:\r\ne.g.\r\n  let n_friendlyReminderTimeout = 30\r\n- in your _vimrc makes it after 30 minutes\r\n","install_details":"Open changingColor.vmb \/ vba in VIM, do a :so % on the command line.  Restart VIM completely.  Chaging color starts working ~ ten seconds.  Installs 4 files, changingColor.vim, changingColorHelp.txt, changingColorTags, and timer.vim.\r\n\r\nTO REMOVE: easy, just do a :RmVimball changingColor and restart.  No need to put .vmb \/ vba at the end.  Once you restart it's gone completely.\r\n\r\nCutomise with\r\n   let permanentColorScheme = \"{YOURFAVCOLORSCHEME}\"\r\n   n_friendlyReminderTimeout = {MYTIMEOUTVALUE]\r\nin your _vimrc if you wish","5":"Open changingColor.vmb \/ vba in VIM, do a :so % on the command line.  Restart VIM completely.  Chaging color starts working ~ ten seconds.  Installs 4 files, changingColor.vim, changingColorHelp.txt, changingColorTags, and timer.vim.\r\n\r\nTO REMOVE: easy, just do a :RmVimball changingColor and restart.  No need to put .vmb \/ vba at the end.  Once you restart it's gone completely.\r\n\r\nCutomise with\r\n   let permanentColorScheme = \"{YOURFAVCOLORSCHEME}\"\r\n   n_friendlyReminderTimeout = {MYTIMEOUTVALUE]\r\nin your _vimrc if you wish","first_name":"Paul","6":"Paul","last_name":"Contreras","7":"Contreras","releases":[{"0":"2658","vim_version":"7.0","1":"7.0","script_version":"23.21","2":"23.21","version_comment":"fixed a little bug preventing friendly reminders from showing if you took long to save your file beyond the specified n_friendlyReminderTimeout.  Just a mistaken variable name.  Fixed :D","3":"fixed a little bug preventing friendly reminders from showing if you took long to save your file beyond the specified n_friendlyReminderTimeout.  Just a mistaken variable name.  Fixed :D","package":"changingColor.vmb","4":"changingColor.vmb","src_id":"25516","5":"25516","creation_date":"1502988892","6":"1502988892"},{"0":"2658","vim_version":"7.0","1":"7.0","script_version":"23.2","2":"23.2","version_comment":"Made the man wave after you have left Vim unantended for more then 8 mins when you press something.  Added new wave so if you spend more than 8 minutes without write little man gives a little wave.","3":"Made the man wave after you have left Vim unantended for more then 8 mins when you press something.  Added new wave so if you spend more than 8 minutes without write little man gives a little wave.","package":"changingColor.vmb","4":"changingColor.vmb","src_id":"25515","5":"25515","creation_date":"1502976292","6":"1502976292"},{"0":"2658","vim_version":"7.0","1":"7.0","script_version":"23.1","2":"23.1","version_comment":"Made waving man really friendly but not too annoying I hope :\/","3":"Made waving man really friendly but not too annoying I hope :\/","package":"changingColor.vmb","4":"changingColor.vmb","src_id":"25486","5":"25486","creation_date":"1502120932","6":"1502120932"},{"0":"2658","vim_version":"7.0","1":"7.0","script_version":"23.0","2":"23.0","version_comment":"Made the greeting message more friendly by doing hands in the air motions etc.. no really it's just a little hand wave animation but I think it adds a little color","3":"Made the greeting message more friendly by doing hands in the air motions etc.. no really it's just a little hand wave animation but I think it adds a little color","package":"changingColor.vmb","4":"changingColor.vmb","src_id":"25483","5":"25483","creation_date":"1502062447","6":"1502062447"},{"0":"2658","vim_version":"7.0","1":"7.0","script_version":"22.5","2":"22.5","version_comment":"Made initial greeting message clear. it now appears in color and remains visible longer plus made a re-welcome if you leave the text file you were editing > 30 min which then cues right into the changing color\r\n","3":"Made initial greeting message clear. it now appears in color and remains visible longer plus made a re-welcome if you leave the text file you were editing > 30 min which then cues right into the changing color\r\n","package":"changingColor.vmb","4":"changingColor.vmb","src_id":"25402","5":"25402","creation_date":"1499968784","6":"1499968784"},{"0":"2658","vim_version":"7.0","1":"7.0","script_version":"22.4","2":"22.4","version_comment":"Added a little greeting message the first time Changing Color script runs which also informs you of the current date and time.","3":"Added a little greeting message the first time Changing Color script runs which also informs you of the current date and time.","package":"changingColor.vmb","4":"changingColor.vmb","src_id":"25388","5":"25388","creation_date":"1499700461","6":"1499700461"},{"0":"2658","vim_version":"7.0","1":"7.0","script_version":"22.3","2":"22.3","version_comment":"Took off some not necessary highlights to conserve as much resources as possible.  Added this missing SpecialChar which is the format specifier in C scanf family functions.\r\n","3":"Took off some not necessary highlights to conserve as much resources as possible.  Added this missing SpecialChar which is the format specifier in C scanf family functions.\r\n","package":"changingColor.vmb","4":"changingColor.vmb","src_id":"25333","5":"25333","creation_date":"1498138571","6":"1498138571"},{"0":"2658","vim_version":"7.0","1":"7.0","script_version":"22.2","2":"22.2","version_comment":"Included Number, seems this is in MacVim not in Win Vim which was weird because the number constants remained the same.  Also tweaks to Normal to remain more stable  Fixed an attempted fix in 22.0 of Operator which forgot to add at the end :$ but through testing found it.  Operator, SpecialKey and with temp variables.  Now everything is just added to one big variable and done in one go.  It's also a lot more clearer to read.","3":"Included Number, seems this is in MacVim not in Win Vim which was weird because the number constants remained the same.  Also tweaks to Normal to remain more stable  Fixed an attempted fix in 22.0 of Operator which forgot to add at the end :$ but through testing found it.  Operator, SpecialKey and with temp variables.  Now everything is just added to one big variable and done in one go.  It's also a lot more clearer to read.","package":"changingColor.vmb","4":"changingColor.vmb","src_id":"25296","5":"25296","creation_date":"1497016650","6":"1497016650"},{"0":"2658","vim_version":"7.0","1":"7.0","script_version":"22.1","2":"22.1","version_comment":"made the timing mechanism more smooth.  Now the highlights are only ever touched when there's really going to be a change to them.  actually there was just an exit clause 'if it wasn't time' yet but now that's gone instead you just get a smooth call to the function only when it's time to do something.","3":"made the timing mechanism more smooth.  Now the highlights are only ever touched when there's really going to be a change to them.  actually there was just an exit clause 'if it wasn't time' yet but now that's gone instead you just get a smooth call to the function only when it's time to do something.","package":"changingColor.vmb","4":"changingColor.vmb","src_id":"25293","5":"25293","creation_date":"1496944727","6":"1496944727"},{"0":"2658","vim_version":"7.0","1":"7.0","script_version":"22.0","2":"22.0","version_comment":"Operator highlight group did not have a definition\r\nsorted this out temporarily so that it works \r\nnice enough,>:P but I know this sucks\r\nlater gonna add a proper nice green color for it.","3":"Operator highlight group did not have a definition\r\nsorted this out temporarily so that it works \r\nnice enough,>:P but I know this sucks\r\nlater gonna add a proper nice green color for it.","package":"changingColor.vmb","4":"changingColor.vmb","src_id":"25292","5":"25292","creation_date":"1496941541","6":"1496941541"},{"0":"2658","vim_version":"7.0","1":"7.0","script_version":"21.1","2":"21.1","version_comment":"The Normal forground was adjusted.  All I did was moved the adjustment for lighter background down a bit so as to be less agressive because it wasn't making it much clearer!","3":"The Normal forground was adjusted.  All I did was moved the adjustment for lighter background down a bit so as to be less agressive because it wasn't making it much clearer!","package":"changingColor.vba","4":"changingColor.vba","src_id":"23948","5":"23948","creation_date":"1453732023","6":"1453732023"},{"0":"2658","vim_version":"7.0","1":"7.0","script_version":"21.0","2":"21.0","version_comment":"There's two things here.  First of all I removed a rather ugly feature.  But more importantly is the TAGS i've used to do this.  Basically, in the code where the main change happened I've added a TAG and this steps you through hand-holding style through the changes I've made in the script.  It's how VIM is fundamentally made.  That's it's power. That and combined with it's incredible :help system make it the best editor in the business, and maybe one of the greatest of ALL TIME ever created! I like it because it takes someone rather like me, not that clever, and gives them power tools for logic (TAGS) ability to bundle language help (:help) as well as a nice code editor and sit back and enjoy. I need a few hits on this so you could help and you might learn something.  please check out: http:\/\/www.ezrider.co.uk\/VimTagsHelp -A.N.Other Spanish guy trying to rule the WORLD argh.. (it even might be good if there weren't 1000's of us all plotting and scheming the same thing arghh.... should have just stuck to writing Quill adventures!)","3":"There's two things here.  First of all I removed a rather ugly feature.  But more importantly is the TAGS i've used to do this.  Basically, in the code where the main change happened I've added a TAG and this steps you through hand-holding style through the changes I've made in the script.  It's how VIM is fundamentally made.  That's it's power. That and combined with it's incredible :help system make it the best editor in the business, and maybe one of the greatest of ALL TIME ever created! I like it because it takes someone rather like me, not that clever, and gives them power tools for logic (TAGS) ability to bundle language help (:help) as well as a nice code editor and sit back and enjoy. I need a few hits on this so you could help and you might learn something.  please check out: http:\/\/www.ezrider.co.uk\/VimTagsHelp -A.N.Other Spanish guy trying to rule the WORLD argh.. (it even might be good if there weren't 1000's of us all plotting and scheming the same thing arghh.... should have just stuck to writing Quill adventures!)","package":"changingColor.vba","4":"changingColor.vba","src_id":"23910","5":"23910","creation_date":"1452879984","6":"1452879984"},{"0":"2658","vim_version":"7.0","1":"7.0","script_version":"20.7","2":"20.7","version_comment":"Slight improvements to Constant esp. at high light settings.","3":"Slight improvements to Constant esp. at high light settings.","package":"changingColor.vba","4":"changingColor.vba","src_id":"22950","5":"22950","creation_date":"1424826292","6":"1424826292"},{"0":"2658","vim_version":"7.0","1":"7.0","script_version":"20.6","2":"20.6","version_comment":"Further gave tweaks to Comment because there were effects that were making it worse.  Cleaned it up.","3":"Further gave tweaks to Comment because there were effects that were making it worse.  Cleaned it up.","package":"changingColor.vba","4":"changingColor.vba","src_id":"22949","5":"22949","creation_date":"1424817406","6":"1424817406"},{"0":"2658","vim_version":"7.0","1":"7.0","script_version":"20.5","2":"20.5","version_comment":"Gave Comment a tweak at high brightness backgrounds because it looked to much like Normal in this.","3":"Gave Comment a tweak at high brightness backgrounds because it looked to much like Normal in this.","package":"changingColor.vba","4":"changingColor.vba","src_id":"22947","5":"22947","creation_date":"1424801548","6":"1424801548"},{"0":"2658","vim_version":"7.0","1":"7.0","script_version":"20.4","2":"20.4","version_comment":"Gave Constant and Identifier a bit of a tweak at high brightness background.  The green of Identifier also looks nice and flouro at low light backgrounds.  You  can actually see the green still at light backgrounds.","3":"Gave Constant and Identifier a bit of a tweak at high brightness background.  The green of Identifier also looks nice and flouro at low light backgrounds.  You  can actually see the green still at light backgrounds.","package":"changingColor.vba","4":"changingColor.vba","src_id":"22942","5":"22942","creation_date":"1424742313","6":"1424742313"},{"0":"2658","vim_version":"7.0","1":"7.0","script_version":"20.3","2":"20.3","version_comment":"I forgot the vital tags files, only really useful if you wanna see help on it.  This does not affect the scripts at all.  If you've previously installed it just make sure you run :RmVimball changingColor and just re-install it by loading changingColor.vba and doing :so %.  That will get rid of any rubbish.","3":"I forgot the vital tags files, only really useful if you wanna see help on it.  This does not affect the scripts at all.  If you've previously installed it just make sure you run :RmVimball changingColor and just re-install it by loading changingColor.vba and doing :so %.  That will get rid of any rubbish.","package":"changingColor.vba","4":"changingColor.vba","src_id":"22904","5":"22904","creation_date":"1423667652","6":"1423667652"},{"0":"2658","vim_version":"7.0","1":"7.0","script_version":"20.2","2":"20.2","version_comment":"Had a third look and decided about 33% should do it.  That is about 33% of the shades are no good.  That's roughly 1\/3 so sounds about right.  They are just too \"in the grey area\" to be clear highlight.  They needed to be removed. ","3":"Had a third look and decided about 33% should do it.  That is about 33% of the shades are no good.  That's roughly 1\/3 so sounds about right.  They are just too \"in the grey area\" to be clear highlight.  They needed to be removed. ","package":"changingColor.vba","4":"changingColor.vba","src_id":"22902","5":"22902","creation_date":"1423601777","6":"1423601777"},{"0":"2658","vim_version":"7.0","1":"7.0","script_version":"20.1","2":"20.1","version_comment":"Had a look at it and decided ~25% was still too low and there were still some murky shades too difficult to see.  I didn't want to cut too much of the continuity but I think 30% is a necessary step towards improvement","3":"Had a look at it and decided ~25% was still too low and there were still some murky shades too difficult to see.  I didn't want to cut too much of the continuity but I think 30% is a necessary step towards improvement","package":"changingColor.vba","4":"changingColor.vba","src_id":"22862","5":"22862","creation_date":"1422991599","6":"1422991599"},{"0":"2658","vim_version":"7.0","1":"7.0","script_version":"20.0","2":"20.0","version_comment":"After careful consideration have decided that some of the shades in my script are too difficult to see.  I was trying to have one smooth continuum between light and dark but the exact middle point is always making me strain to read no matter what I do, and this looks poor compared to other color schemes so I decided to create a ramped \"jump over\" the exact mid-point. You will still see constant changes but when it gets to a certain mid point it will jump about 20% of the murky shades to the next point after that.\r\n","3":"After careful consideration have decided that some of the shades in my script are too difficult to see.  I was trying to have one smooth continuum between light and dark but the exact middle point is always making me strain to read no matter what I do, and this looks poor compared to other color schemes so I decided to create a ramped \"jump over\" the exact mid-point. You will still see constant changes but when it gets to a certain mid point it will jump about 20% of the murky shades to the next point after that.\r\n","package":"changingColor.vba","4":"changingColor.vba","src_id":"22860","5":"22860","creation_date":"1422988151","6":"1422988151"},{"0":"2658","vim_version":"7.0","1":"7.0","script_version":"19.3","2":"19.3","version_comment":"Tweaked visibility of Normal, edge case.  It appears that due to a calibration issue I was having with my monitor I'd got this wrong previously.  I had thought that it was massively out but it was a \"Power Saving feature of my EeePC that made it look hard to read. Not generally applicable in most cases.  Fixed to be similar to what it was in 19.0. ","3":"Tweaked visibility of Normal, edge case.  It appears that due to a calibration issue I was having with my monitor I'd got this wrong previously.  I had thought that it was massively out but it was a \"Power Saving feature of my EeePC that made it look hard to read. Not generally applicable in most cases.  Fixed to be similar to what it was in 19.0. ","package":"changingColor.vba","4":"changingColor.vba","src_id":"22667","5":"22667","creation_date":"1417618962","6":"1417618962"}]},"2657":{"script_id":"2657","0":"2657","script_name":"VOoM","1":"VOoM","script_type":"utility","2":"utility","summary":"Vim two-pane outliner","3":"Vim two-pane outliner","description":"VOoM (Vim Outliner of Markups) is a plugin for Vim that emulates a two-pane text outliner.\r\n\r\nHome page: http:\/\/www.vim.org\/scripts\/script.php?script_id=2657\r\nGitHub mirror: https:\/\/github.com\/vim-voom\/VOoM\r\nScreenshots and an animation: https:\/\/vim-voom.github.io\/\r\nBug reports, questions, requests: https:\/\/github.com\/vim-voom\/vim-voom.github.com\/issues\r\nSupplementary Materials: https:\/\/github.com\/vim-voom\/VOoM_extras\r\n\r\nVOoM was originally written to work with start fold markers with level numbers, that is {{{1, {{{2, {{{3, etc. This is the most versatile outline markup -- it is suitable for organizing all kinds of files, including the source code, and it allows features not possible with other markups. (See :help fold-marker. Markers are specified by option 'foldmarker'. End fold markers with levels, }}}3, }}}2, etc. are not supported.)\r\n\r\nVOoM can currently handle >20 markup formats that have headlines and support an outline structure, including popular lightweight markup languages such as reST, Markdown, Pandoc, AsciiDoc, Org-mode, Wiki, LaTeX, etc. (Headlines are also called headings, headers, section headers, titles.)\r\nThe following markup modes are available:\r\n        * fmr (Default Mode)  -- Start fold markers with levels: {{{1, {{{2, {{{3, etc. Headline text is before the marker.\r\n        * fmr1, fmr2, fmr3  -- Start fold markers with levels. Variations of the Default Mode.\r\n        * wiki  -- MediaWiki, headlines are surrounded by '='.\r\n        * vimwiki  -- Vimwiki plugin, vimscript #2226.\r\n        * viki  -- Viki\/Deplate plugin, vimscript #861.\r\n        * cwiki  -- vimscript #2176.\r\n        * org  -- Emacs Org-mode.\r\n        * rest  -- reStructuredText section titles.\r\n        * markdown  -- Markdown headers, both Setext-style and Atx-style.\r\n        * pandoc  -- Pandoc Markdown. Headlines inside fenced code blocks are ignored, which makes this mode suitable for MultiMarkdown, GitHub Markdown, R Markdown, etc.\r\n        * hashes  -- #, ##, ###, etc. Atx-style headers, a subset of Markdown format.\r\n        * txt2tags  -- txt2tags titles and numbered titles.\r\n        * asciidoc  -- AsciiDoc document and section titles, both styles.\r\n        * latex  -- LaTeX sectioning and some other commands.\r\n        * latexDtx  -- Same as LaTeX but for .dtx files (Documented LaTeX sources).\r\n        * dokuwiki  -- DokuWiki.\r\n        * inverseAtx -- Inverse Atx-style headers.\r\n        * html  -- HTML heading tags, single line only.\r\n        * thevimoutliner  -- The Vim Outliner plugin (vimscript #517).\r\n        * vimoutliner  -- VimOutliner plugin (vimscript #3515).\r\n        * taskpaper  -- TaskPaper (vimscript #2027).\r\n        * python  -- Python code browser. Blocks between \"class\" and \"def\" are also nodes.\r\n        * paragraphBlank, paragraphIndent, paragraphNoIndent  -- For working with paragraphs. Handy for sorting blocks of lines.\r\n\r\nAn outline of the current buffer is created by the command\r\n        :Voom [MarkupMode]\r\nwhere MarkupMode is one of the listed above. There is argument completion -- type \":Voom \" and press <Tab> or <C-d>.\r\nFor Markdown file:\r\n        :Voom markdown\r\nFor Pandoc Markdown:\r\n        :Voom pandoc\r\nFor LaTeX file:\r\n        :Voom latex\r\nFor Orgmode file:\r\n        :Voom org\r\nAnd so on.  To delete outline, press \"q\" while in the outline pane (Tree buffer).\r\nNOTE that by default the command \":Voom\" is equivalent to \":Voom fmr\" -- outline is created from lines with {{{1, {{{2, {{{3, etc. (the marker is specified by Vim option 'fmr'). This can be customized, see help for g:voom_ft_modes and g:voom_default_mode. The name of the current markup mode is noted on the first line of the Tree buffer. The command \":Voominfo [all]\" will show more details.\r\n\r\n\r\nFEATURES AND BENEFITS:\r\n        + VOoM is a full-featured outliner. It has a complete set of commands for outline structure manipulation: move nodes up\/down, promote\/demote, copy\/cut\/paste, insert new node, sort in various ways, randomize.\r\n        + There are many one-character mappings for efficient outline navigation which can be combined into complex commands, e.g., \"UVD\" selects all siblings of the current node.\r\n        + VOoM is mice-friendly: outlines can be browsed with a mouse.\r\n        + An outline can be searched (:Voomgrep). Boolean AND\/NOT searches (OR is provided by Vim's \\|). Hierarchical searches (tag inheritance).\r\n        + Outline is updated automagically on entering the corresponding Tree buffer.\r\n        + VOoM works with Vim buffers, not with files on disk as ctags-based tools.\r\n        + VOoM is not a 'filetype' plugin. It has almost no side effects on the buffer being outlined.\r\n        + VOoM is not tied to a particular outline format. It works with many popular light-weight markup languages.\r\n        + VOoM is fast and efficient enough to handle MB-sized files with >1000 headlines. (Some markup modes are slower than other.)\r\n\r\n\r\nThere are four main Ex commands: Voom, Voomhelp, Voomexec, Voomlog.\r\n\r\n:Voom {MarkupMode}\r\n        Create outline of the current buffer. The current buffer is scanned for headlines. Headlines are displayed in the outline pane (Tree buffer). The format of headlines is specified by {MarkupMode}. See above for available markups. There is argument completion: type \":Voom \" and press <Tab> or <C-d> to see all installed markup modes.\r\n        The outline is displayed in a special buffer in a separate window which emulates the tree pane of a two-pane outliner. Such buffers are referred to as Tree buffers. The current buffer becomes a Body buffer. Each Tree line is associated with a region (node) of the corresponding source buffer (Body). Nodes can be navigated and manipulated in the Tree: moved up\/down, promoted\/demoted, copied\/cut\/pasted, sorted, etc.\r\n\r\n:Voom\r\n        Use the default markup mode, which by default is \"fmr\" mode: headlines are lines with a start fold marker (specified by Vim option 'foldmarker') followed by level number, that is {{{1, {{{2, {{{3, etc. Headline's level is the number after the marker. Headline's text is the part before the marker.\r\n\r\n:Voomhelp\r\n        Open help file voom.txt as an outline in a new tabpage.\r\n\r\n:Voomexec [vim|py]\r\n        Execute the contents of the current node or fold as a Vim script or Python script. This is useful for testing code snippets and for organizing short scripts by segregating them into nodes or folds. This command can be used independently of the outlining functionality provided by the command :Voom.\r\n\r\n:Voomlog\r\n        Create scratch buffer __PyLog__ and redirect Python's sys.stdout and sys.stderr to it. This is useful when developing Python scripts and when scripting Vim with Python. This feature is completely independent from the rest of the plugin.\r\n\r\n(Commands :Voomexec and :Voomlog attempt to emulate similar features of Leo outlining editor. A Python file with code snippets organized via fold markers, plus the command :Voomexec, plus the PyLog buffer is an alternative to Python's interactive interpreter.)\r\n\r\n\r\nFor a quick introduction to VOoM outlining, see section \"Quick Start\" in the help file (|voom-quickstart|).\r\nFor a concise list of all VOoM commands (cheat sheet), see section \"ALL MAPPINGS & COMMANDS\" in the help file (|voom-map|).","4":"VOoM (Vim Outliner of Markups) is a plugin for Vim that emulates a two-pane text outliner.\r\n\r\nHome page: http:\/\/www.vim.org\/scripts\/script.php?script_id=2657\r\nGitHub mirror: https:\/\/github.com\/vim-voom\/VOoM\r\nScreenshots and an animation: https:\/\/vim-voom.github.io\/\r\nBug reports, questions, requests: https:\/\/github.com\/vim-voom\/vim-voom.github.com\/issues\r\nSupplementary Materials: https:\/\/github.com\/vim-voom\/VOoM_extras\r\n\r\nVOoM was originally written to work with start fold markers with level numbers, that is {{{1, {{{2, {{{3, etc. This is the most versatile outline markup -- it is suitable for organizing all kinds of files, including the source code, and it allows features not possible with other markups. (See :help fold-marker. Markers are specified by option 'foldmarker'. End fold markers with levels, }}}3, }}}2, etc. are not supported.)\r\n\r\nVOoM can currently handle >20 markup formats that have headlines and support an outline structure, including popular lightweight markup languages such as reST, Markdown, Pandoc, AsciiDoc, Org-mode, Wiki, LaTeX, etc. (Headlines are also called headings, headers, section headers, titles.)\r\nThe following markup modes are available:\r\n        * fmr (Default Mode)  -- Start fold markers with levels: {{{1, {{{2, {{{3, etc. Headline text is before the marker.\r\n        * fmr1, fmr2, fmr3  -- Start fold markers with levels. Variations of the Default Mode.\r\n        * wiki  -- MediaWiki, headlines are surrounded by '='.\r\n        * vimwiki  -- Vimwiki plugin, vimscript #2226.\r\n        * viki  -- Viki\/Deplate plugin, vimscript #861.\r\n        * cwiki  -- vimscript #2176.\r\n        * org  -- Emacs Org-mode.\r\n        * rest  -- reStructuredText section titles.\r\n        * markdown  -- Markdown headers, both Setext-style and Atx-style.\r\n        * pandoc  -- Pandoc Markdown. Headlines inside fenced code blocks are ignored, which makes this mode suitable for MultiMarkdown, GitHub Markdown, R Markdown, etc.\r\n        * hashes  -- #, ##, ###, etc. Atx-style headers, a subset of Markdown format.\r\n        * txt2tags  -- txt2tags titles and numbered titles.\r\n        * asciidoc  -- AsciiDoc document and section titles, both styles.\r\n        * latex  -- LaTeX sectioning and some other commands.\r\n        * latexDtx  -- Same as LaTeX but for .dtx files (Documented LaTeX sources).\r\n        * dokuwiki  -- DokuWiki.\r\n        * inverseAtx -- Inverse Atx-style headers.\r\n        * html  -- HTML heading tags, single line only.\r\n        * thevimoutliner  -- The Vim Outliner plugin (vimscript #517).\r\n        * vimoutliner  -- VimOutliner plugin (vimscript #3515).\r\n        * taskpaper  -- TaskPaper (vimscript #2027).\r\n        * python  -- Python code browser. Blocks between \"class\" and \"def\" are also nodes.\r\n        * paragraphBlank, paragraphIndent, paragraphNoIndent  -- For working with paragraphs. Handy for sorting blocks of lines.\r\n\r\nAn outline of the current buffer is created by the command\r\n        :Voom [MarkupMode]\r\nwhere MarkupMode is one of the listed above. There is argument completion -- type \":Voom \" and press <Tab> or <C-d>.\r\nFor Markdown file:\r\n        :Voom markdown\r\nFor Pandoc Markdown:\r\n        :Voom pandoc\r\nFor LaTeX file:\r\n        :Voom latex\r\nFor Orgmode file:\r\n        :Voom org\r\nAnd so on.  To delete outline, press \"q\" while in the outline pane (Tree buffer).\r\nNOTE that by default the command \":Voom\" is equivalent to \":Voom fmr\" -- outline is created from lines with {{{1, {{{2, {{{3, etc. (the marker is specified by Vim option 'fmr'). This can be customized, see help for g:voom_ft_modes and g:voom_default_mode. The name of the current markup mode is noted on the first line of the Tree buffer. The command \":Voominfo [all]\" will show more details.\r\n\r\n\r\nFEATURES AND BENEFITS:\r\n        + VOoM is a full-featured outliner. It has a complete set of commands for outline structure manipulation: move nodes up\/down, promote\/demote, copy\/cut\/paste, insert new node, sort in various ways, randomize.\r\n        + There are many one-character mappings for efficient outline navigation which can be combined into complex commands, e.g., \"UVD\" selects all siblings of the current node.\r\n        + VOoM is mice-friendly: outlines can be browsed with a mouse.\r\n        + An outline can be searched (:Voomgrep). Boolean AND\/NOT searches (OR is provided by Vim's \\|). Hierarchical searches (tag inheritance).\r\n        + Outline is updated automagically on entering the corresponding Tree buffer.\r\n        + VOoM works with Vim buffers, not with files on disk as ctags-based tools.\r\n        + VOoM is not a 'filetype' plugin. It has almost no side effects on the buffer being outlined.\r\n        + VOoM is not tied to a particular outline format. It works with many popular light-weight markup languages.\r\n        + VOoM is fast and efficient enough to handle MB-sized files with >1000 headlines. (Some markup modes are slower than other.)\r\n\r\n\r\nThere are four main Ex commands: Voom, Voomhelp, Voomexec, Voomlog.\r\n\r\n:Voom {MarkupMode}\r\n        Create outline of the current buffer. The current buffer is scanned for headlines. Headlines are displayed in the outline pane (Tree buffer). The format of headlines is specified by {MarkupMode}. See above for available markups. There is argument completion: type \":Voom \" and press <Tab> or <C-d> to see all installed markup modes.\r\n        The outline is displayed in a special buffer in a separate window which emulates the tree pane of a two-pane outliner. Such buffers are referred to as Tree buffers. The current buffer becomes a Body buffer. Each Tree line is associated with a region (node) of the corresponding source buffer (Body). Nodes can be navigated and manipulated in the Tree: moved up\/down, promoted\/demoted, copied\/cut\/pasted, sorted, etc.\r\n\r\n:Voom\r\n        Use the default markup mode, which by default is \"fmr\" mode: headlines are lines with a start fold marker (specified by Vim option 'foldmarker') followed by level number, that is {{{1, {{{2, {{{3, etc. Headline's level is the number after the marker. Headline's text is the part before the marker.\r\n\r\n:Voomhelp\r\n        Open help file voom.txt as an outline in a new tabpage.\r\n\r\n:Voomexec [vim|py]\r\n        Execute the contents of the current node or fold as a Vim script or Python script. This is useful for testing code snippets and for organizing short scripts by segregating them into nodes or folds. This command can be used independently of the outlining functionality provided by the command :Voom.\r\n\r\n:Voomlog\r\n        Create scratch buffer __PyLog__ and redirect Python's sys.stdout and sys.stderr to it. This is useful when developing Python scripts and when scripting Vim with Python. This feature is completely independent from the rest of the plugin.\r\n\r\n(Commands :Voomexec and :Voomlog attempt to emulate similar features of Leo outlining editor. A Python file with code snippets organized via fold markers, plus the command :Voomexec, plus the PyLog buffer is an alternative to Python's interactive interpreter.)\r\n\r\n\r\nFor a quick introduction to VOoM outlining, see section \"Quick Start\" in the help file (|voom-quickstart|).\r\nFor a concise list of all VOoM commands (cheat sheet), see section \"ALL MAPPINGS & COMMANDS\" in the help file (|voom-map|).","install_details":"**REQUIREMENTS**\r\nVOoM uses Python and requires Python-enabled Vim, that is Vim compiled with the Python interface. Both GUI Vim and terminal Vim are supported. Vim  version should be >=7.2. Normal or bigger feature set is required. Both Python 2 and Python 3 are supported.\r\nTo check if Vim has Python 2 support:\r\n        :py print 2**0.5\r\n        :py import sys; print sys.version\r\nTo check if Vim has Python 3 support:\r\n        :py3 print(2**0.5)\r\n        :py3 import sys; print(sys.version)\r\n\r\nBy default VOoM will use the first available Python version: Python 2 is tried first, Python 3 is tried next.\r\nTo always use Python 2, add to .vimrc:\r\n        let g:voom_python_versions = [2]\r\nTo always use Python 3, add to .vimrc:\r\n        let g:voom_python_versions = [3]\r\nTo first try Python 3, then Python 2, add to .vimrc:\r\n        let g:voom_python_versions = [3,2]\r\nTo first try Python 2, then Pythons 3, then Python 4, then Python 5, then Pythons 6 to 666:\r\n        let g:voom_python_versions = range(2,666)\r\n\r\nTo see which Python version is currently used by VOoM, execute command \":Voominfo [all]\".\r\n\r\n**INSTALLATION**\r\nTo install the VOoM plugin manually:\r\n1) Move the contents of folders \"autoload\", \"doc\", \"plugin\" into the respective folders in your local Vim directory:\r\n        $HOME\/vimfiles\/       (Windows)\r\n        $HOME\/.vim\/           (Unix)\r\nThis should make commands :Voom, :Voomhelp, :Voomexec, :Voomlog available in all buffers. (Do \":echo $HOME\" to find out what Vim sees as $HOME.)\r\n2) Execute the :helptags command to update help tags:\r\n        :helptags $HOME\/vimfiles\/doc       (Windows)\r\n        :helptags $HOME\/.vim\/doc           (Unix)\r\n\r\nTo uninstall: all VOoM file and directory names start with \"voom\", so search for \"voom\" and delete, then update help tags.\r\n\r\nAlternatively, use Pathogen (vimscript #2332) and install VOoM as a bundle, or use a Vim plugin manager.\r\n","5":"**REQUIREMENTS**\r\nVOoM uses Python and requires Python-enabled Vim, that is Vim compiled with the Python interface. Both GUI Vim and terminal Vim are supported. Vim  version should be >=7.2. Normal or bigger feature set is required. Both Python 2 and Python 3 are supported.\r\nTo check if Vim has Python 2 support:\r\n        :py print 2**0.5\r\n        :py import sys; print sys.version\r\nTo check if Vim has Python 3 support:\r\n        :py3 print(2**0.5)\r\n        :py3 import sys; print(sys.version)\r\n\r\nBy default VOoM will use the first available Python version: Python 2 is tried first, Python 3 is tried next.\r\nTo always use Python 2, add to .vimrc:\r\n        let g:voom_python_versions = [2]\r\nTo always use Python 3, add to .vimrc:\r\n        let g:voom_python_versions = [3]\r\nTo first try Python 3, then Python 2, add to .vimrc:\r\n        let g:voom_python_versions = [3,2]\r\nTo first try Python 2, then Pythons 3, then Python 4, then Python 5, then Pythons 6 to 666:\r\n        let g:voom_python_versions = range(2,666)\r\n\r\nTo see which Python version is currently used by VOoM, execute command \":Voominfo [all]\".\r\n\r\n**INSTALLATION**\r\nTo install the VOoM plugin manually:\r\n1) Move the contents of folders \"autoload\", \"doc\", \"plugin\" into the respective folders in your local Vim directory:\r\n        $HOME\/vimfiles\/       (Windows)\r\n        $HOME\/.vim\/           (Unix)\r\nThis should make commands :Voom, :Voomhelp, :Voomexec, :Voomlog available in all buffers. (Do \":echo $HOME\" to find out what Vim sees as $HOME.)\r\n2) Execute the :helptags command to update help tags:\r\n        :helptags $HOME\/vimfiles\/doc       (Windows)\r\n        :helptags $HOME\/.vim\/doc           (Unix)\r\n\r\nTo uninstall: all VOoM file and directory names start with \"voom\", so search for \"voom\" and delete, then update help tags.\r\n\r\nAlternatively, use Pathogen (vimscript #2332) and install VOoM as a bundle, or use a Vim plugin manager.\r\n","first_name":"Vlad","6":"Vlad","last_name":"Irnov","7":"Irnov","releases":[{"0":"2657","vim_version":"7.0","1":"7.0","script_version":"5.3","2":"5.3","version_comment":"Minor bug fixes.","3":"Minor bug fixes.","package":"VOoM-5.3.zip","4":"VOoM-5.3.zip","src_id":"25011","5":"25011","creation_date":"1488749368","6":"1488749368"},{"0":"2657","vim_version":"7.0","1":"7.0","script_version":"5.2","2":"5.2","version_comment":"* Python 3 is now supported. New option g:voom_python_versions.\r\n* New markup modes: latexDtx, fmr3, paragraphBlank, paragraphIndent, paragraphNoIndent.\r\n* VOoM Python modules are now in directory ..\/autoload\/voom\/voom_vimplugin2657\/ and are imported as a package. Custom markup modes must be placed there. Because directory structure has changed, previous VOoM version should be removed before installing this one. \r\n* VoomSort: Option \"u\" was removed. Option \"bytes\" was added. Headlines are now always sorted as Python Unicode strings unless option \"bytes\" is given.\r\n* Other small changes.","3":"* Python 3 is now supported. New option g:voom_python_versions.\r\n* New markup modes: latexDtx, fmr3, paragraphBlank, paragraphIndent, paragraphNoIndent.\r\n* VOoM Python modules are now in directory ..\/autoload\/voom\/voom_vimplugin2657\/ and are imported as a package. Custom markup modes must be placed there. Because directory structure has changed, previous VOoM version should be removed before installing this one. \r\n* VoomSort: Option \"u\" was removed. Option \"bytes\" was added. Headlines are now always sorted as Python Unicode strings unless option \"bytes\" is given.\r\n* Other small changes.","package":"VOoM-5.2.zip","4":"VOoM-5.2.zip","src_id":"24917","5":"24917","creation_date":"1485126362","6":"1485126362"},{"0":"2657","vim_version":"7.0","1":"7.0","script_version":"5.1","2":"5.1","version_comment":"* New markup mode: dokuwiki.\r\n* Python markup mode: better handling of decorative comment lines (separators and pretty headers).\r\n* :Voomgrep improvements.\r\n* Some internal improvements.","3":"* New markup mode: dokuwiki.\r\n* Python markup mode: better handling of decorative comment lines (separators and pretty headers).\r\n* :Voomgrep improvements.\r\n* Some internal improvements.","package":"VOoM-5.1.zip","4":"VOoM-5.1.zip","src_id":"22082","5":"22082","creation_date":"1403472649","6":"1403472649"},{"0":"2657","vim_version":"7.0","1":"7.0","script_version":"5.0","2":"5.0","version_comment":"* The code and directory structure have been reorganized. Please remove the previous version before installing this one. Delete folder plugin\/voom. If you use VOoM functions, calls to Voom_... need to be changed to voom#...\r\n* The command :Voomgrep can now perform hierarchical searches (tag inheritance).\r\n* New option g:voom_always_allow_move_left.\r\n* New option g:voom_clipboard_register. Copy\/Cut\/Paste now use the \"o register if Vim does not have clipboard support.\r\n* New markup modes: pandoc, inverseAtx.\r\n* Python markup mode: better handling of decorators.\r\n* Markdown, AsciiDoc, reST modes: small improvements and bug fixes.\r\n","3":"* The code and directory structure have been reorganized. Please remove the previous version before installing this one. Delete folder plugin\/voom. If you use VOoM functions, calls to Voom_... need to be changed to voom#...\r\n* The command :Voomgrep can now perform hierarchical searches (tag inheritance).\r\n* New option g:voom_always_allow_move_left.\r\n* New option g:voom_clipboard_register. Copy\/Cut\/Paste now use the \"o register if Vim does not have clipboard support.\r\n* New markup modes: pandoc, inverseAtx.\r\n* Python markup mode: better handling of decorators.\r\n* Markdown, AsciiDoc, reST modes: small improvements and bug fixes.\r\n","package":"VOoM-5.0.zip","4":"VOoM-5.0.zip","src_id":"21112","5":"21112","creation_date":"1385443482","6":"1385443482"},{"0":"2657","vim_version":"7.0","1":"7.0","script_version":"4.7","2":"4.7","version_comment":"* New markup mode: TaskPaper.\r\n* Fixed problems with some external autocommands such as automatic write on BufLeave.\r\n* License changed to CC0.\r\n","3":"* New markup mode: TaskPaper.\r\n* Fixed problems with some external autocommands such as automatic write on BufLeave.\r\n* License changed to CC0.\r\n","package":"VOoM-4.7.zip","4":"VOoM-4.7.zip","src_id":"19447","5":"19447","creation_date":"1359429567","6":"1359429567"},{"0":"2657","vim_version":"7.0","1":"7.0","script_version":"4.6","2":"4.6","version_comment":"* Warning message is no longer displayed when a markup mode is invoked.\r\n* New command :Voominfo [all] prints information about the current outline and VOoM internals.","3":"* Warning message is no longer displayed when a markup mode is invoked.\r\n* New command :Voominfo [all] prints information about the current outline and VOoM internals.","package":"VOoM-4.6.zip","4":"VOoM-4.6.zip","src_id":"19087","5":"19087","creation_date":"1354513283","6":"1354513283"},{"0":"2657","vim_version":"7.0","1":"7.0","script_version":"4.5","2":"4.5","version_comment":"* New Tree mapping: \"I\" jumps to the last line of the current node.\r\n* Improved txt2tags mode.\r\n* Fixed a bug in :Voomgrep search.\r\n* Improved display of :Voomgrep results.\r\n","3":"* New Tree mapping: \"I\" jumps to the last line of the current node.\r\n* Improved txt2tags mode.\r\n* Fixed a bug in :Voomgrep search.\r\n* Improved display of :Voomgrep results.\r\n","package":"VOoM-4.5.zip","4":"VOoM-4.5.zip","src_id":"18972","5":"18972","creation_date":"1352809948","6":"1352809948"},{"0":"2657","vim_version":"7.0","1":"7.0","script_version":"4.4","2":"4.4","version_comment":"* Added LaTeX mode: |voom_mode_latex|.\r\n* Better mappings for Insert New Headline: \"aa\", \"AA\". <LocalLeader>i\/I were changed to <LocalLeader>a\/A.\r\n* Other small improvements.","3":"* Added LaTeX mode: |voom_mode_latex|.\r\n* Better mappings for Insert New Headline: \"aa\", \"AA\". <LocalLeader>i\/I were changed to <LocalLeader>a\/A.\r\n* Other small improvements.","package":"VOoM-4.4.zip","4":"VOoM-4.4.zip","src_id":"18088","5":"18088","creation_date":"1338777709","6":"1338777709"},{"0":"2657","vim_version":"7.0","1":"7.0","script_version":"4.3","2":"4.3","version_comment":"* Fixed problems with file names containing %, #, spaces, etc.\r\n* New markup mode: hashes (atx-style headers).","3":"* Fixed problems with file names containing %, #, spaces, etc.\r\n* New markup mode: hashes (atx-style headers).","package":"VOoM-4.3.zip","4":"VOoM-4.3.zip","src_id":"17887","5":"17887","creation_date":"1336359816","6":"1336359816"},{"0":"2657","vim_version":"7.0","1":"7.0","script_version":"4.2","2":"4.2","version_comment":"* New commands for quitting and toggling outline window (|voom_quit|): \"q\", VoomToggle, Voomtoggle, Voomquit, VoomQuitAll.\r\n* New Tree mappings ^^ (Move Up) and __ (Move Down) for symmetry with << and >>.\r\n* Added support for \"fmr\" modes (|voom_mode_fmr|). Modes fmr, fmr1, fmr2.\r\n* New options |g:voom_ft_modes|, |g:voom_default_mode| allow automatic selection of markup mode according to filetype of the source buffer.\r\n* Improved asciidoc mode.\r\n* :Voomexec now executes Python scripts via \"exec\" instead of execfile(). Temp file plugin\/voom\/_voomScript_.py is no longer created and should be deleted.\r\n* Various internal code changes.\r\n","3":"* New commands for quitting and toggling outline window (|voom_quit|): \"q\", VoomToggle, Voomtoggle, Voomquit, VoomQuitAll.\r\n* New Tree mappings ^^ (Move Up) and __ (Move Down) for symmetry with << and >>.\r\n* Added support for \"fmr\" modes (|voom_mode_fmr|). Modes fmr, fmr1, fmr2.\r\n* New options |g:voom_ft_modes|, |g:voom_default_mode| allow automatic selection of markup mode according to filetype of the source buffer.\r\n* Improved asciidoc mode.\r\n* :Voomexec now executes Python scripts via \"exec\" instead of execfile(). Temp file plugin\/voom\/_voomScript_.py is no longer created and should be deleted.\r\n* Various internal code changes.\r\n","package":"VOoM-4.2.zip","4":"VOoM-4.2.zip","src_id":"17720","5":"17720","creation_date":"1333571759","6":"1333571759"},{"0":"2657","vim_version":"7.0","1":"7.0","script_version":"4.1","2":"4.1","version_comment":"Fix for Vim 7.3 versions: Tree mappings J\/K did not accept a count.","3":"Fix for Vim 7.3 versions: Tree mappings J\/K did not accept a count.","package":"VOoM-4.1.zip","4":"VOoM-4.1.zip","src_id":"16986","5":"16986","creation_date":"1322448720","6":"1322448720"},{"0":"2657","vim_version":"7.0","1":"7.0","script_version":"4.0","2":"4.0","version_comment":"New markup modes: asciidoc, org, cwiki. Viki mode now ignores special regions.\r\nNew Tree mapping: \"R\" selects corresponding range in the source buffer.\r\n","3":"New markup modes: asciidoc, org, cwiki. Viki mode now ignores special regions.\r\nNew Tree mapping: \"R\" selects corresponding range in the source buffer.\r\n","package":"VOoM-4.0.zip","4":"VOoM-4.0.zip","src_id":"16818","5":"16818","creation_date":"1320627711","6":"1320627711"},{"0":"2657","vim_version":"7.0","1":"7.0","script_version":"4.0b5","2":"4.0b5","version_comment":"* New markup mode: txt2tags.\r\n* Added support for sessions (:mksession).\r\n* Fixed some bugs.","3":"* New markup mode: txt2tags.\r\n* Added support for sessions (:mksession).\r\n* Fixed some bugs.","package":"VOoM-4.0b5.zip","4":"VOoM-4.0b5.zip","src_id":"15284","5":"15284","creation_date":"1300985470","6":"1300985470"},{"0":"2657","vim_version":"7.0","1":"7.0","script_version":"4.0b4","2":"4.0b4","version_comment":"* New Tree mappings for navigating outline:\r\n    P (go to parent node),\r\n    c (go to parent and contract it),\r\n    C (contract siblings or everything in Visual selection),\r\n    o (go to first child),\r\n    O (expand siblings or everything in Visual selection),\r\n    K\/J\/U\/D (go to previous\/next\/uppermost\/downmost sibling),\r\n    s (show headline text), S (show UNL).\r\n* Fixed some bugs.","3":"* New Tree mappings for navigating outline:\r\n    P (go to parent node),\r\n    c (go to parent and contract it),\r\n    C (contract siblings or everything in Visual selection),\r\n    o (go to first child),\r\n    O (expand siblings or everything in Visual selection),\r\n    K\/J\/U\/D (go to previous\/next\/uppermost\/downmost sibling),\r\n    s (show headline text), S (show UNL).\r\n* Fixed some bugs.","package":"VOoM-4.0b4.zip","4":"VOoM-4.0b4.zip","src_id":"14922","5":"14922","creation_date":"1296447056","6":"1296447056"},{"0":"2657","vim_version":"7.0","1":"7.0","script_version":"4.0b3","2":"4.0b3","version_comment":"* Added mode for Markdown markup.\r\n* Fixed severe bug in reST mode.\r\n* Sorting can now be done for any range of sibling nodes.","3":"* Added mode for Markdown markup.\r\n* Fixed severe bug in reST mode.\r\n* Sorting can now be done for any range of sibling nodes.","package":"VOoM-4.0b3.zip","4":"VOoM-4.0b3.zip","src_id":"14681","5":"14681","creation_date":"1294196558","6":"1294196558"},{"0":"2657","vim_version":"7.0","1":"7.0","script_version":"4.0b2","2":"4.0b2","version_comment":"* Added support for the following markups: reStructuredText, Python code, The Vim Outliner, VimOutliner.\r\n* BUG FIX: indiscriminate use of 'noautocmd' was screwing up some autocommands.\r\n* Option g:voom_verify_oop is now enabled by default.\r\n* Option g:voom_rstrip_chars (dictionary) has been removed. Instead there are options g:voom_rstrip_chars_{filetype} for each filetype of interest.\r\n* See CHANGELOG for other changes.\r\n","3":"* Added support for the following markups: reStructuredText, Python code, The Vim Outliner, VimOutliner.\r\n* BUG FIX: indiscriminate use of 'noautocmd' was screwing up some autocommands.\r\n* Option g:voom_verify_oop is now enabled by default.\r\n* Option g:voom_rstrip_chars (dictionary) has been removed. Instead there are options g:voom_rstrip_chars_{filetype} for each filetype of interest.\r\n* See CHANGELOG for other changes.\r\n","package":"VOoM-4.0b2.zip","4":"VOoM-4.0b2.zip","src_id":"14109","5":"14109","creation_date":"1287934465","6":"1287934465"},{"0":"2657","vim_version":"7.0","1":"7.0","script_version":"4.0b1","2":"4.0b1","version_comment":"* Added support for headline markups other than start fold markers with levels. Available markup modes: wiki, vimwiki, viki, html.\r\n\r\n* Changed plugin directory structure. All Python files are now located in folder plugin\/voom. You should delete old files in plugin folder: plugin\/voom.py, plugin\/voom.pyc, plugin\/voomScript.py.","3":"* Added support for headline markups other than start fold markers with levels. Available markup modes: wiki, vimwiki, viki, html.\r\n\r\n* Changed plugin directory structure. All Python files are now located in folder plugin\/voom. You should delete old files in plugin folder: plugin\/voom.py, plugin\/voom.pyc, plugin\/voomScript.py.","package":"VOoM-4.0b1.zip","4":"VOoM-4.0b1.zip","src_id":"13879","5":"13879","creation_date":"1285042212","6":"1285042212"},{"0":"2657","vim_version":"7.0","1":"7.0","script_version":"3.0","2":"3.0","version_comment":"* New command :VoomSort [options] for sorting outline.\r\n\r\n* Outline buffer (Tree) is no longer automatically wiped out when the source buffer (Body) is unloaded, deleted, or wiped out. Instead, outline is locked until the source buffer is loaded again. This change was necessary to eliminate crashes after :q, :q! and similar problems. This can also make working with outlines easier when buffers routinely get unloaded, as when 'hidden' or 'bufhidden' are not set.\r\n\r\n* Option 'bufhidden' for Tree and PyLog buffers is set to \"wipe\" instead of \"hide\".\r\n\r\n* Various glitches fixed. Memory usage reduced, especially when outlining large buffers.\r\n","3":"* New command :VoomSort [options] for sorting outline.\r\n\r\n* Outline buffer (Tree) is no longer automatically wiped out when the source buffer (Body) is unloaded, deleted, or wiped out. Instead, outline is locked until the source buffer is loaded again. This change was necessary to eliminate crashes after :q, :q! and similar problems. This can also make working with outlines easier when buffers routinely get unloaded, as when 'hidden' or 'bufhidden' are not set.\r\n\r\n* Option 'bufhidden' for Tree and PyLog buffers is set to \"wipe\" instead of \"hide\".\r\n\r\n* Various glitches fixed. Memory usage reduced, especially when outlining large buffers.\r\n","package":"VOoM-3.0.zip","4":"VOoM-3.0.zip","src_id":"13454","5":"13454","creation_date":"1280686523","6":"1280686523"},{"0":"2657","vim_version":"7.0","1":"7.0","script_version":"2.1","2":"2.1","version_comment":"* It's now possible to customize how Tree headline text is constructed for individual filetypes:\r\n - 'commentstring' and new user option g:voom_rstrip_chars control which characters are stripped from the right side of headlines when default procedure is used.\r\n - The default procedure for Tree headline text construction can be replaced with user-defined functions via an add-on. Sample add-on is included.\r\n\r\n* Fixed bug in PyLog buffer: original sys.stdout and sys.stderr could be lost after some actions.\r\n","3":"* It's now possible to customize how Tree headline text is constructed for individual filetypes:\r\n - 'commentstring' and new user option g:voom_rstrip_chars control which characters are stripped from the right side of headlines when default procedure is used.\r\n - The default procedure for Tree headline text construction can be replaced with user-defined functions via an add-on. Sample add-on is included.\r\n\r\n* Fixed bug in PyLog buffer: original sys.stdout and sys.stderr could be lost after some actions.\r\n","package":"VOoM-2.1.zip","4":"VOoM-2.1.zip","src_id":"13082","5":"13082","creation_date":"1275415164","6":"1275415164"},{"0":"2657","vim_version":"7.0","1":"7.0","script_version":"2.0","2":"2.0","version_comment":"- This plugin was renamed from VOOF to VOoM. All commands start with \"Voom\" instead of \"Voof\", files were renamed, and so on. Please see Install section for instructions on how to upgrade from previous versions.\r\n- Added rudimentary support for add-ons, a sample add-on. Fixed probable bug in mouse click mapping.","3":"- This plugin was renamed from VOOF to VOoM. All commands start with \"Voom\" instead of \"Voof\", files were renamed, and so on. Please see Install section for instructions on how to upgrade from previous versions.\r\n- Added rudimentary support for add-ons, a sample add-on. Fixed probable bug in mouse click mapping.","package":"VOoM-2.0.zip","4":"VOoM-2.0.zip","src_id":"12762","5":"12762","creation_date":"1270145407","6":"1270145407"},{"0":"2657","vim_version":"7.0","1":"7.0","script_version":"1.92","2":"1.92","version_comment":"Improved performance of several outline operations when working with very large outlines. Optimized some code.","3":"Improved performance of several outline operations when working with very large outlines. Optimized some code.","package":"VOOF-1.92.zip","4":"VOOF-1.92.zip","src_id":"12547","5":"12547","creation_date":"1267589917","6":"1267589917"},{"0":"2657","vim_version":"7.0","1":"7.0","script_version":"1.91","2":"1.91","version_comment":"Voofgrep can perform boolean AND and NOT searches.","3":"Voofgrep can perform boolean AND and NOT searches.","package":"VOOF-1.91.zip","4":"VOOF-1.91.zip","src_id":"12325","5":"12325","creation_date":"1265509798","6":"1265509798"},{"0":"2657","vim_version":"7.0","1":"7.0","script_version":"1.9","2":"1.9","version_comment":"It's now possible to save and restore Tree buffer folding.\r\nCommand \"Voofrun\" was renamed \"Voofexec\".\r\nSeveral other small changes.","3":"It's now possible to save and restore Tree buffer folding.\r\nCommand \"Voofrun\" was renamed \"Voofexec\".\r\nSeveral other small changes.","package":"VOOF-1.9.zip","4":"VOOF-1.9.zip","src_id":"11927","5":"11927","creation_date":"1261241622","6":"1261241622"},{"0":"2657","vim_version":"7.0","1":"7.0","script_version":"1.8","2":"1.8","version_comment":"Fixed bug in mappings.\r\nAdded highlighting for warnings and other messages.\r\nDistribution now follows Vim directory structure: there are plugin and doc folders.\r\nChanged license to WTFPL, version 2.\r\n","3":"Fixed bug in mappings.\r\nAdded highlighting for warnings and other messages.\r\nDistribution now follows Vim directory structure: there are plugin and doc folders.\r\nChanged license to WTFPL, version 2.\r\n","package":"VOOF-1.8.zip","4":"VOOF-1.8.zip","src_id":"11407","5":"11407","creation_date":"1253299249","6":"1253299249"},{"0":"2657","vim_version":"7.0","1":"7.0","script_version":"1.7","2":"1.7","version_comment":"more foolproofing","3":"more foolproofing","package":"VOOF-1.7.zip","4":"VOOF-1.7.zip","src_id":"11295","5":"11295","creation_date":"1251737766","6":"1251737766"},{"0":"2657","vim_version":"7.0","1":"7.0","script_version":"1.6","2":"1.6","version_comment":"Added defensive measures that prevent data corruption when outline update fails for any reason.\r\nFixed some bugs.","3":"Added defensive measures that prevent data corruption when outline update fails for any reason.\r\nFixed some bugs.","package":"VOOF-1.6.zip","4":"VOOF-1.6.zip","src_id":"11238","5":"11238","creation_date":"1251035459","6":"1251035459"},{"0":"2657","vim_version":"7.0","1":"7.0","script_version":"1.5","2":"1.5","version_comment":"New commands: Voofgrep, Voofunl.\r\nFixed bug in \"Move Down\" outline operation.\r\nVarious improvements.","3":"New commands: Voofgrep, Voofunl.\r\nFixed bug in \"Move Down\" outline operation.\r\nVarious improvements.","package":"VOOF-1.5.zip","4":"VOOF-1.5.zip","src_id":"11192","5":"11192","creation_date":"1250305855","6":"1250305855"},{"0":"2657","vim_version":"7.0","1":"7.0","script_version":"1.4","2":"1.4","version_comment":"New Tree navigation commands: go to next\/previous marked node. Various small changes and fixes.","3":"New Tree navigation commands: go to next\/previous marked node. Various small changes and fixes.","package":"VOOF_14.zip","4":"VOOF_14.zip","src_id":"11001","5":"11001","creation_date":"1247447828","6":"1247447828"},{"0":"2657","vim_version":"7.0","1":"7.0","script_version":"1.3","2":"1.3","version_comment":"Added support for non-default start fold markers specified by 'foldmarker' option. Various other small improvements and fixes.","3":"Added support for non-default start fold markers specified by 'foldmarker' option. Various other small improvements and fixes.","package":"VOOF_13.zip","4":"VOOF_13.zip","src_id":"10748","5":"10748","creation_date":"1244253942","6":"1244253942"},{"0":"2657","vim_version":"7.0","1":"7.0","script_version":"1.2","2":"1.2","version_comment":"Minor bug fixes and edits. See CHANGELOG node in voof.txt.","3":"Minor bug fixes and edits. See CHANGELOG node in voof.txt.","package":"VOOF_12.zip","4":"VOOF_12.zip","src_id":"10704","5":"10704","creation_date":"1243659468","6":"1243659468"},{"0":"2657","vim_version":"7.0","1":"7.0","script_version":"1.1","2":"1.1","version_comment":"Bug fix involving nomodifiable and readonly buffers.","3":"Bug fix involving nomodifiable and readonly buffers.","package":"VOOF_11.zip","4":"VOOF_11.zip","src_id":"10682","5":"10682","creation_date":"1243394281","6":"1243394281"},{"0":"2657","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"VOOF.zip","4":"VOOF.zip","src_id":"10679","5":"10679","creation_date":"1243298663","6":"1243298663"}]},"2656":{"script_id":"2656","0":"2656","script_name":"Simple R Omni Completion","1":"Simple R Omni Completion","script_type":"ftplugin","2":"ftplugin","summary":"Auto completes R identifiers from the current file and the included libraries","3":"Auto completes R identifiers from the current file and the included libraries","description":"Scans the current buffer for R identifiers and library() calls, offers autocompletion, first on the identifiers in the current file, than on the ones in the library.\r\nIdentifiers within the current file are ordered by distance to the current line, standoffs are resolved by first suggesting those before the current line.\r\n\r\nSee also vimscript #2628 for a different approach to this.","4":"Scans the current buffer for R identifiers and library() calls, offers autocompletion, first on the identifiers in the current file, than on the ones in the library.\r\nIdentifiers within the current file are ordered by distance to the current line, standoffs are resolved by first suggesting those before the current line.\r\n\r\nSee also vimscript #2628 for a different approach to this.","install_details":"drop into ~\/.vim\/ftplugin","5":"drop into ~\/.vim\/ftplugin","first_name":"Tyberius","6":"Tyberius","last_name":"Prime","7":"Prime","releases":[{"0":"2656","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"r_omni.vim","4":"r_omni.vim","src_id":"10676","5":"10676","creation_date":"1243247760","6":"1243247760"}]},"2655":{"script_id":"2655","0":"2655","script_name":"squirrel.vim","1":"squirrel.vim","script_type":"syntax","2":"syntax","summary":"Squirrel Language syntax file","3":"Squirrel Language syntax file","description":"syntax file for Squirrel (http:\/\/squirrel-lang.org\/default.aspx) ","4":"syntax file for Squirrel (http:\/\/squirrel-lang.org\/default.aspx) ","install_details":"Expand squirrel.tar.gz, squirre.vim the folder into the syntax please","5":"Expand squirrel.tar.gz, squirre.vim the folder into the syntax please","first_name":"Yasuhiro","6":"Yasuhiro","last_name":"Kanda","7":"Kanda","releases":[{"0":"2655","vim_version":"7.0","1":"7.0","script_version":"0.2","2":"0.2","version_comment":"# update\r\n# add squirrel script sample (squirrel.nut) ","3":"# update\r\n# add squirrel script sample (squirrel.nut) ","package":"squirrel.0.2.tar.gz","4":"squirrel.0.2.tar.gz","src_id":"12575","5":"12575","creation_date":"1267977536","6":"1267977536"},{"0":"2655","vim_version":"7.2","1":"7.2","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"squirrel.tar.gz","4":"squirrel.tar.gz","src_id":"10675","5":"10675","creation_date":"1243235624","6":"1243235624"}]},"2654":{"script_id":"2654","0":"2654","script_name":"Arduino syntax file","1":"Arduino syntax file","script_type":"syntax","2":"syntax","summary":"Syntax file for Arduino .PDE files","3":"Syntax file for Arduino .PDE files","description":"This syntax file provides syntax highlighting like the Arduino IDE. That is, Arduino specific names like digitalWrite is highlighted in addition to C++ syntax.\r\n\r\nThe syntax file is automatically generated by my script at http:\/\/bitbucket.org\/johannes\/arduino-vim-syntax\r\n\r\nLicensed under the vim license: http:\/\/groups.google.com\/group\/vim_use\/browse_thread\/thread\/bdb036cd8acda1ba\/75b353c598a0cd6f?lnk=gst&q=license#75b353c598a0cd6f","4":"This syntax file provides syntax highlighting like the Arduino IDE. That is, Arduino specific names like digitalWrite is highlighted in addition to C++ syntax.\r\n\r\nThe syntax file is automatically generated by my script at http:\/\/bitbucket.org\/johannes\/arduino-vim-syntax\r\n\r\nLicensed under the vim license: http:\/\/groups.google.com\/group\/vim_use\/browse_thread\/thread\/bdb036cd8acda1ba\/75b353c598a0cd6f?lnk=gst&q=license#75b353c598a0cd6f","install_details":"Just put the file in your vimfiles\/syntax folder. To automatically use it on PDE files, add the following line to your vimrc file (or e.g filetype.vim to install it for all users) :\r\n\r\nautocmd! BufNewFile,BufRead *.pde setlocal ft=arduino","5":"Just put the file in your vimfiles\/syntax folder. To automatically use it on PDE files, add the following line to your vimrc file (or e.g filetype.vim to install it for all users) :\r\n\r\nautocmd! BufNewFile,BufRead *.pde setlocal ft=arduino","first_name":"Johannes","6":"Johannes","last_name":"Hoff","7":"Hoff","releases":[{"0":"2654","vim_version":"7.0","1":"7.0","script_version":"9","2":"9","version_comment":"Update to version 1.6.4 (thanks for the patch, Niall Parker)","3":"Update to version 1.6.4 (thanks for the patch, Niall Parker)","package":"arduino.vim","4":"arduino.vim","src_id":"23284","5":"23284","creation_date":"1431929969","6":"1431929969"},{"0":"2654","vim_version":"7.0","1":"7.0","script_version":"8","2":"8","version_comment":"Update to Arduino version 1.0. (Thanks for the reminder, Claus K\u00c3\u00bchnel)","3":"Update to Arduino version 1.0. (Thanks for the reminder, Claus K\u00c3\u00bchnel)","package":"arduino.vim","4":"arduino.vim","src_id":"17108","5":"17108","creation_date":"1324645663","6":"1324645663"},{"0":"2654","vim_version":"6.0","1":"6.0","script_version":"7","2":"7","version_comment":"Update to Arduino version 0022. File is now automatically generated.","3":"Update to Arduino version 0022. File is now automatically generated.","package":"arduino.vim","4":"arduino.vim","src_id":"15821","5":"15821","creation_date":"1307363744","6":"1307363744"},{"0":"2654","vim_version":"6.0","1":"6.0","script_version":"6","2":"6","version_comment":"Fix spelling of INTERNAL, plus added some new keywords (thanks to Graeme Cross)","3":"Fix spelling of INTERNAL, plus added some new keywords (thanks to Graeme Cross)","package":"arduino.vim","4":"arduino.vim","src_id":"15799","5":"15799","creation_date":"1307098469","6":"1307098469"},{"0":"2654","vim_version":"6.0","1":"6.0","script_version":"5","2":"5","version_comment":"Add a license (the vim license)","3":"Add a license (the vim license)","package":"arduino.vim","4":"arduino.vim","src_id":"14412","5":"14412","creation_date":"1291229119","6":"1291229119"},{"0":"2654","vim_version":"6.0","1":"6.0","script_version":"4","2":"4","version_comment":"Updated keywords to Arduino version 21 (thanks Adam Obeng)","3":"Updated keywords to Arduino version 21 (thanks Adam Obeng)","package":"arduino.vim","4":"arduino.vim","src_id":"14379","5":"14379","creation_date":"1290773754","6":"1290773754"},{"0":"2654","vim_version":"6.0","1":"6.0","script_version":"3","2":"3","version_comment":"Change to unix line endings as in version 1 (thanks Erik Nomitch)","3":"Change to unix line endings as in version 1 (thanks Erik Nomitch)","package":"arduino.vim","4":"arduino.vim","src_id":"12993","5":"12993","creation_date":"1273677158","6":"1273677158"},{"0":"2654","vim_version":"6.0","1":"6.0","script_version":"2","2":"2","version_comment":"Cleaning up and adding new keywords (thanks to Rik)","3":"Cleaning up and adding new keywords (thanks to Rik)","package":"arduino.vim","4":"arduino.vim","src_id":"12786","5":"12786","creation_date":"1270488544","6":"1270488544"},{"0":"2654","vim_version":"6.0","1":"6.0","script_version":"1","2":"1","version_comment":"Initial upload","3":"Initial upload","package":"arduino.vim","4":"arduino.vim","src_id":"10674","5":"10674","creation_date":"1243184803","6":"1243184803"}]},"2653":{"script_id":"2653","0":"2653","script_name":"cuteErrorMarker","1":"cuteErrorMarker","script_type":"utility","2":"utility","summary":"Display error marks on line which contain errors after compilation","3":"Display error marks on line which contain errors after compilation","description":"Display a mark on lines which contain compilation errors listed on the quickfix window.\r\n\r\nGithub : https:\/\/github.com\/Twinside\/vim-cuteErrorMarker\r\nScreenshots : http:\/\/twinside.github.com\/vim-cuteErrorMarker\/\r\n\r\nTested on :\r\n- Ubuntu 9.04 (GVim && vim)\r\n- Windows XP\/Vista\/7","4":"Display a mark on lines which contain compilation errors listed on the quickfix window.\r\n\r\nGithub : https:\/\/github.com\/Twinside\/vim-cuteErrorMarker\r\nScreenshots : http:\/\/twinside.github.com\/vim-cuteErrorMarker\/\r\n\r\nTested on :\r\n- Ubuntu 9.04 (GVim && vim)\r\n- Windows XP\/Vista\/7","install_details":"drop the files in your ~\/.vim or ~\/vimfiles\r\n(can work in $VIM and $VIMRUNTIME folder, but favor dropping it in your profile dir)","5":"drop the files in your ~\/.vim or ~\/vimfiles\r\n(can work in $VIM and $VIMRUNTIME folder, but favor dropping it in your profile dir)","first_name":"Vincent","6":"Vincent","last_name":"B","7":"B","releases":[{"0":"2653","vim_version":"7.2","1":"7.2","script_version":"1.5","2":"1.5","version_comment":"Added sign placing on :grep operations\r\nAdded more highlighting for console version","3":"Added sign placing on :grep operations\r\nAdded more highlighting for console version","package":"cuteErrorMarker.zip","4":"cuteErrorMarker.zip","src_id":"14050","5":"14050","creation_date":"1286961271","6":"1286961271"}]},"2652":{"script_id":"2652","0":"2652","script_name":"bblean.vim","1":"bblean.vim","script_type":"syntax","2":"syntax","summary":"detect keyword in bblean resource file","3":"detect keyword in bblean resource file","description":"detect for\r\n  menu.rc\r\n  blackbox.rc\r\n  extensions.rc","4":"detect for\r\n  menu.rc\r\n  blackbox.rc\r\n  extensions.rc","install_details":"put in $VIM\\vimfiles\\syntax\\\r\nand \"set syntax=bblean\" every time, \r\nor write \" vim:syntax=bblean \" your script .","5":"put in $VIM\\vimfiles\\syntax\\\r\nand \"set syntax=bblean\" every time, \r\nor write \" vim:syntax=bblean \" your script .","first_name":"masami","6":"masami","last_name":"ito","7":"ito","releases":[{"0":"2652","vim_version":"7.0","1":"7.0","script_version":"1.1","2":"1.1","version_comment":"bug fix","3":"bug fix","package":"bblean.vim","4":"bblean.vim","src_id":"10669","5":"10669","creation_date":"1243076207","6":"1243076207"},{"0":"2652","vim_version":"7.2","1":"7.2","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"bblean.vim","4":"bblean.vim","src_id":"10668","5":"10668","creation_date":"1243068579","6":"1243068579"}]},"2651":{"script_id":"2651","0":"2651","script_name":"fitnesse.vim","1":"fitnesse.vim","script_type":"syntax","2":"syntax","summary":"Syntax coloring for FitNesse Wiki Pages","3":"Syntax coloring for FitNesse Wiki Pages","description":"fitnesse.vim is a syntax file (and eventually some filetype specific functions) \r\nfor editing FitNesse tests using Vim.  It was created to make it easier to work\r\nwith FitNesse files.  It works great in conjunction with \"It's All Text\" a \r\nplugin for FireFox (found at https:\/\/addons.mozilla.org\/en-US\/firefox\/addon\/4125). \r\n\r\nFitNesse is a collaborative testing tool that uses Wiki markup to create test \r\nscripts as web pages.  See http:\/\/fitnesse.org for more information.\r\n\r\nSyntax coloring supports:\r\n      * Numerous keywords in Slim and FitNesse are supported:\r\n         scenario, script, Query:, start, check, reject, show, Comment, comment, \r\n         !see, !include, !See, null, !define, !include\r\n      * Simple collapsible sections (with folding enabled)  !** *!, !**> *!\r\n      * Table cell delimiter \"|\"\r\n      * Cell contents\r\n      * Incomplete cell is error\r\n      * !style_(class) \r\n      * Strings in Quotes\r\n      * Scenario variables @parametername\r\n      * Symbols $symbolname\r\n      * Simple WikiWord support","4":"fitnesse.vim is a syntax file (and eventually some filetype specific functions) \r\nfor editing FitNesse tests using Vim.  It was created to make it easier to work\r\nwith FitNesse files.  It works great in conjunction with \"It's All Text\" a \r\nplugin for FireFox (found at https:\/\/addons.mozilla.org\/en-US\/firefox\/addon\/4125). \r\n\r\nFitNesse is a collaborative testing tool that uses Wiki markup to create test \r\nscripts as web pages.  See http:\/\/fitnesse.org for more information.\r\n\r\nSyntax coloring supports:\r\n      * Numerous keywords in Slim and FitNesse are supported:\r\n         scenario, script, Query:, start, check, reject, show, Comment, comment, \r\n         !see, !include, !See, null, !define, !include\r\n      * Simple collapsible sections (with folding enabled)  !** *!, !**> *!\r\n      * Table cell delimiter \"|\"\r\n      * Cell contents\r\n      * Incomplete cell is error\r\n      * !style_(class) \r\n      * Strings in Quotes\r\n      * Scenario variables @parametername\r\n      * Symbols $symbolname\r\n      * Simple WikiWord support","install_details":"The files in the Zip file are stored in the same folders they need to be \r\nplaced in under the vimfiles folder ( $HOME\/.vim\/ or %VIM%\\vimfils depending\r\non your OS).\r\n\r\n1) Unzip the fitnesse.vim.zip file to the vimfiles folder.  Unless you are \r\n   customizing the file, you should be OK to overwrite the files.\r\n  \r\n2) Syntax coloring support must be enabled. \r\n      \r\n      You can do this by adding :syntax enable to your _vimrc or .vimrc file.\r\n\r\n3) If you want automatic detection you will need to:\r\n\r\n      a) Check to see if you have a scripts.vim file already in place.  This \r\n         file allows post loading checking of files to execute scripts.  \r\n\r\n      b) If you do not have a scripts.vim file in your vimfiles folder, rename\r\n         the scripts.vim.add file to scripts.vim.\r\n\r\n      c) If you do have a scripts.vim file; open the scripts.vim.fitnesse_add \r\n         file and copy the text in that file to your scripts.vim file.","5":"The files in the Zip file are stored in the same folders they need to be \r\nplaced in under the vimfiles folder ( $HOME\/.vim\/ or %VIM%\\vimfils depending\r\non your OS).\r\n\r\n1) Unzip the fitnesse.vim.zip file to the vimfiles folder.  Unless you are \r\n   customizing the file, you should be OK to overwrite the files.\r\n  \r\n2) Syntax coloring support must be enabled. \r\n      \r\n      You can do this by adding :syntax enable to your _vimrc or .vimrc file.\r\n\r\n3) If you want automatic detection you will need to:\r\n\r\n      a) Check to see if you have a scripts.vim file already in place.  This \r\n         file allows post loading checking of files to execute scripts.  \r\n\r\n      b) If you do not have a scripts.vim file in your vimfiles folder, rename\r\n         the scripts.vim.add file to scripts.vim.\r\n\r\n      c) If you do have a scripts.vim file; open the scripts.vim.fitnesse_add \r\n         file and copy the text in that file to your scripts.vim file.","first_name":"Dan","6":"Dan","last_name":"Woodward","7":"Woodward","releases":[{"0":"2651","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"fitnesse.vim.zip","4":"fitnesse.vim.zip","src_id":"10658","5":"10658","creation_date":"1243011539","6":"1243011539"}]},"2650":{"script_id":"2650","0":"2650","script_name":"\u2605darkZ\u2605","1":"★darkZ★","script_type":"color scheme","2":"color scheme","summary":"★★Try my best to make it looks more comfortable:P","3":"★★Try my best to make it looks more comfortable:P","description":"Try my best to make this color theme looks more comfortable:P","4":"Try my best to make this color theme looks more comfortable:P","install_details":"Used with the Monaco font, that would be nice~","5":"Used with the Monaco font, that would be nice~","first_name":"andy","6":"andy","last_name":"au","7":"au","releases":[{"0":"2650","vim_version":"6.0","1":"6.0","script_version":"1.1","2":"1.1","version_comment":"Looks more comfortable:P","3":"Looks more comfortable:P","package":"darkZ.vim","4":"darkZ.vim","src_id":"15436","5":"15436","creation_date":"1302598805","6":"1302598805"},{"0":"2650","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"darkZ.vim","4":"darkZ.vim","src_id":"10656","5":"10656","creation_date":"1242951200","6":"1242951200"}]},"2649":{"script_id":"2649","0":"2649","script_name":"PBASIC syntax","1":"PBASIC syntax","script_type":"syntax","2":"syntax","summary":"PBASIC syntax file","3":"PBASIC syntax file","description":"Syntax file for PBASIC 2.5; should work for older versions.","4":"Syntax file for PBASIC 2.5; should work for older versions.","install_details":"UNIX: ~\/.vim\/syntax\/pbasic.bs2\r\nWindows: $VIMRUNTIME\/syntax\/pbasic.bs2\r\n\r\nCreate a file with the following lines:\r\nau BufRead,BufNewFile *.[Bb][Ss][12] set filetype=pbasic\r\nau BufRead,BufNewFile *.[Bb][Ss][12]p set filetype=pbasic\r\nau BufRead,BufNewFile *.[Bb][Ss][12]p[ex] set filetype=pbasic\r\nau BufRead,BufNewFile *.[Bb][Ss][12]sx set filetype=pbasic\r\n\r\n...and save it to ~\/.vim\/ftdetect\/bs2.vim","5":"UNIX: ~\/.vim\/syntax\/pbasic.bs2\r\nWindows: $VIMRUNTIME\/syntax\/pbasic.bs2\r\n\r\nCreate a file with the following lines:\r\nau BufRead,BufNewFile *.[Bb][Ss][12] set filetype=pbasic\r\nau BufRead,BufNewFile *.[Bb][Ss][12]p set filetype=pbasic\r\nau BufRead,BufNewFile *.[Bb][Ss][12]p[ex] set filetype=pbasic\r\nau BufRead,BufNewFile *.[Bb][Ss][12]sx set filetype=pbasic\r\n\r\n...and save it to ~\/.vim\/ftdetect\/bs2.vim","first_name":"Nicholas","6":"Nicholas","last_name":"De Cicco","7":"De Cicco","releases":[{"0":"2649","vim_version":"6.0","1":"6.0","script_version":"1.2","2":"1.2","version_comment":"#ELSEIF ... #THEN is now colored as PreCondit","3":"#ELSEIF ... #THEN is now colored as PreCondit","package":"pbasic.vim","4":"pbasic.vim","src_id":"11584","5":"11584","creation_date":"1256432203","6":"1256432203"},{"0":"2649","vim_version":"6.0","1":"6.0","script_version":"1.1","2":"1.1","version_comment":"Fixed the patterns for PBASIC version and port declarations","3":"Fixed the patterns for PBASIC version and port declarations","package":"pbasic.vim","4":"pbasic.vim","src_id":"11339","5":"11339","creation_date":"1252338292","6":"1252338292"},{"0":"2649","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"pbasic.vim","4":"pbasic.vim","src_id":"10655","5":"10655","creation_date":"1242940980","6":"1242940980"}]},"2648":{"script_id":"2648","0":"2648","script_name":"darkburn","1":"darkburn","script_type":"color scheme","2":"color scheme","summary":"Darkburn: A darker mod of Zenburn","3":"Darkburn: A darker mod of Zenburn","description":"darkburn is a mod of zenburn vimscript#415 by Jani Nurminen. I added more contrast and brighter colors. \r\nI hope you will enjoy it.","4":"darkburn is a mod of zenburn vimscript#415 by Jani Nurminen. I added more contrast and brighter colors. \r\nI hope you will enjoy it.","install_details":"Copy the file to ~\/.vim\/colors and :colorscheme darkburn","5":"Copy the file to ~\/.vim\/colors and :colorscheme darkburn","first_name":"Taurus","6":"Taurus","last_name":"Olson","7":"Olson","releases":[{"0":"2648","vim_version":"7.0","1":"7.0","script_version":"1.2","2":"1.2","version_comment":"Modified the names of some global variables to prevent conflict between darkburn and zenburn.","3":"Modified the names of some global variables to prevent conflict between darkburn and zenburn.","package":"darkburn.vim","4":"darkburn.vim","src_id":"10756","5":"10756","creation_date":"1244316397","6":"1244316397"},{"0":"2648","vim_version":"7.0","1":"7.0","script_version":"1.1","2":"1.1","version_comment":"Modified g:colors_name. Thanks to Hosup Chung.","3":"Modified g:colors_name. Thanks to Hosup Chung.","package":"darkburn.vim","4":"darkburn.vim","src_id":"10662","5":"10662","creation_date":"1243017046","6":"1243017046"},{"0":"2648","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"darkburn.vim","4":"darkburn.vim","src_id":"10651","5":"10651","creation_date":"1242917455","6":"1242917455"}]},"2647":{"script_id":"2647","0":"2647","script_name":"Templates for Files and Function Groups","1":"Templates for Files and Function Groups","script_type":"utility","2":"utility","summary":"Yet another file template script.","3":"Yet another file template script.","description":"Dr. Beco has a newer and better maintained version of this plugin available here: https:\/\/github.com\/drbeco\/vimtemplates\r\n\r\nThis script is a modified version of the template plugin documented here: http:\/\/lucumr.pocoo.org\/cogitations\/2007\/08\/03\/vim-file-templates\/.\r\n\r\nKey features:\r\n\r\nMultiple templates (optionally with a default) for any file type; for example, you can have a template for a given file type and for each project you're working on or company you're working for.\r\n\r\nSupport for automatic population of certain parameters, such as the file name, the year, the date or an upper case version of the basename etc etc (more can be added very easily).\r\n\r\nOther parameters can be included and a dialog box will pop up to ask for the value.  The last-used value (from this Vim session) will be remembered as the default.\r\nSupport for fixed-width entries.\r\n\r\nA template is just a source file stored in ~\/.vim\/templates or vimfiles\/templates (depending on OS) with some identifiers inserted in appropriate places.  An identifier starts with \"<+\" and ends with \"+>\".  In the identifier, there can be:\r\n\r\nKeywords surrounded by '$' signs: these are automatically expanded.  Supported keywords are (examples shown for file Flash.c):\r\n\r\n$BASENAME$ (e.g. Flash)\r\n$UBASENAME$ (e.g. FLASH)\r\n$LBASENAME$ (e.g. flash)\r\n$FILENAME$ (e.g. Flash.c)\r\n$YEAR$ (e.g. 2008)\r\n$DATE$ (e.g. 3\/9\/2008)\r\n\r\nKeywords surrounded by '#' signs: the user will be asked what these mean (the same replacement will be used for all entries in the file).  For example, you may want to have:\r\n\r\n#MODULE_TITLE#\r\n#PROJECT_TITLE#\r\n\r\nA semicolon followed by an 'R' and then zero or more '+' signs.  This provides a fixed-width entry.  See the included examples for details.\r\n\r\nThere are example C source and header templates included in the distribution.\r\n\r\nAfter creating a new file and setting the file name, the template is loaded with the command\r\n\r\n:LoadFileTemplate <TemplateName>\r\n\r\nWhere <TemplateName> should be replaced by the name of your template (e.g. \":LoadFileTemplate Example\" for the example template).  If you're editing a '.c' file, example.c will be loaded and if you're editing a '.h' file, example.h will be loaded.  If you add an entry in .vimrc to set the global variable g:file_template_default, it is then possible to simply run \":LoadFileTemplate\" and the default will be used.\r\n\r\nIn addition, you can use the command:\r\n\r\n:AddTemplate <TemplateName>\r\n\r\nto add a template at the current location in the current file.  I use this (for example) to add a circular buffer to an existing module.  Again, it will differentiate by extension, so you can have a template for the code implementation and the header definitions.\r\n\r\n\r\nMore details available at:\r\n\r\nhttps:\/\/sites.google.com\/site\/abudden\/contents\/Vim-Scripts\/file-templates\r\n","4":"Dr. Beco has a newer and better maintained version of this plugin available here: https:\/\/github.com\/drbeco\/vimtemplates\r\n\r\nThis script is a modified version of the template plugin documented here: http:\/\/lucumr.pocoo.org\/cogitations\/2007\/08\/03\/vim-file-templates\/.\r\n\r\nKey features:\r\n\r\nMultiple templates (optionally with a default) for any file type; for example, you can have a template for a given file type and for each project you're working on or company you're working for.\r\n\r\nSupport for automatic population of certain parameters, such as the file name, the year, the date or an upper case version of the basename etc etc (more can be added very easily).\r\n\r\nOther parameters can be included and a dialog box will pop up to ask for the value.  The last-used value (from this Vim session) will be remembered as the default.\r\nSupport for fixed-width entries.\r\n\r\nA template is just a source file stored in ~\/.vim\/templates or vimfiles\/templates (depending on OS) with some identifiers inserted in appropriate places.  An identifier starts with \"<+\" and ends with \"+>\".  In the identifier, there can be:\r\n\r\nKeywords surrounded by '$' signs: these are automatically expanded.  Supported keywords are (examples shown for file Flash.c):\r\n\r\n$BASENAME$ (e.g. Flash)\r\n$UBASENAME$ (e.g. FLASH)\r\n$LBASENAME$ (e.g. flash)\r\n$FILENAME$ (e.g. Flash.c)\r\n$YEAR$ (e.g. 2008)\r\n$DATE$ (e.g. 3\/9\/2008)\r\n\r\nKeywords surrounded by '#' signs: the user will be asked what these mean (the same replacement will be used for all entries in the file).  For example, you may want to have:\r\n\r\n#MODULE_TITLE#\r\n#PROJECT_TITLE#\r\n\r\nA semicolon followed by an 'R' and then zero or more '+' signs.  This provides a fixed-width entry.  See the included examples for details.\r\n\r\nThere are example C source and header templates included in the distribution.\r\n\r\nAfter creating a new file and setting the file name, the template is loaded with the command\r\n\r\n:LoadFileTemplate <TemplateName>\r\n\r\nWhere <TemplateName> should be replaced by the name of your template (e.g. \":LoadFileTemplate Example\" for the example template).  If you're editing a '.c' file, example.c will be loaded and if you're editing a '.h' file, example.h will be loaded.  If you add an entry in .vimrc to set the global variable g:file_template_default, it is then possible to simply run \":LoadFileTemplate\" and the default will be used.\r\n\r\nIn addition, you can use the command:\r\n\r\n:AddTemplate <TemplateName>\r\n\r\nto add a template at the current location in the current file.  I use this (for example) to add a circular buffer to an existing module.  Again, it will differentiate by extension, so you can have a template for the code implementation and the header definitions.\r\n\r\n\r\nMore details available at:\r\n\r\nhttps:\/\/sites.google.com\/site\/abudden\/contents\/Vim-Scripts\/file-templates\r\n","install_details":"","5":"","first_name":"Al","6":"Al","last_name":"Budden","7":"Budden","releases":[{"0":"2647","vim_version":"7.0","1":"7.0","script_version":"r630","2":"r630","version_comment":"Removed dependency on VIMFILESDIR being defined: find the templates directory using globdir.","3":"Removed dependency on VIMFILESDIR being defined: find the templates directory using globdir.","package":"file_templates.vba","4":"file_templates.vba","src_id":"17301","5":"17301","creation_date":"1327308795","6":"1327308795"},{"0":"2647","vim_version":"7.0","1":"7.0","script_version":"r233","2":"r233","version_comment":"Initial upload","3":"Initial upload","package":"file_templates.vba","4":"file_templates.vba","src_id":"10650","5":"10650","creation_date":"1242911772","6":"1242911772"}]},"2646":{"script_id":"2646","0":"2646","script_name":"TagHighlight","1":"TagHighlight","script_type":"ftplugin","2":"ftplugin","summary":"Extra highlighting of typedefs, enumerations etc (based on ctags)","3":"Extra highlighting of typedefs, enumerations etc (based on ctags)","description":"TagHighlight is a plugin that highlights names of classes, variables, types etc in source code in Vim.  This makes it quicker and easier to spot errors in your code.  By using exuberant ctags and parsing the output, the typedefs, #defines, enumerated names etc are all clearly highlighted in different colours.  As standard, it supports the following languages (but it's very easy to add more):\r\n\r\n* C\/C++ (most of the testing has been with these)\r\n* C#\r\n* Java\r\n* Javascript\r\n* Matlab (if your version of ctags supports it)\r\n* Perl\r\n* PHP\r\n* Python\r\n* Ruby\r\n* Scala\r\n* Fortran\r\n* Go (if your version of ctags supports it)\r\n* VHDL (if your version of ctags supports it)\r\n\r\nAdding more languages is extremely simple.\r\n\r\nTo show the benefit of this plugin, there are some screenshots and a more detailed description at the following website:\r\n\r\nhttp:\/\/www.cgtk.co.uk\/taghighlight\r\n\r\n---------------------------------------------------------------------------------------------------------------------------------------------------------------------\r\n\r\nThis version replaces the previous \"CTAGS Highlighting\" script and it is necessary to uninstall that plugin in order to upgrade to the new version.  Detailed instructions are on the website or in the enclosed documentation.\r\n\r\nThe source is now maintained on heptapod (https:\/\/heptapod.host\/cgtk\/taghighlight).  There is also a mirror on github (https:\/\/github.com\/abudden\/taghighlight-automirror), although I can't guarantee this will be as up to date as the heptapod version.","4":"TagHighlight is a plugin that highlights names of classes, variables, types etc in source code in Vim.  This makes it quicker and easier to spot errors in your code.  By using exuberant ctags and parsing the output, the typedefs, #defines, enumerated names etc are all clearly highlighted in different colours.  As standard, it supports the following languages (but it's very easy to add more):\r\n\r\n* C\/C++ (most of the testing has been with these)\r\n* C#\r\n* Java\r\n* Javascript\r\n* Matlab (if your version of ctags supports it)\r\n* Perl\r\n* PHP\r\n* Python\r\n* Ruby\r\n* Scala\r\n* Fortran\r\n* Go (if your version of ctags supports it)\r\n* VHDL (if your version of ctags supports it)\r\n\r\nAdding more languages is extremely simple.\r\n\r\nTo show the benefit of this plugin, there are some screenshots and a more detailed description at the following website:\r\n\r\nhttp:\/\/www.cgtk.co.uk\/taghighlight\r\n\r\n---------------------------------------------------------------------------------------------------------------------------------------------------------------------\r\n\r\nThis version replaces the previous \"CTAGS Highlighting\" script and it is necessary to uninstall that plugin in order to upgrade to the new version.  Detailed instructions are on the website or in the enclosed documentation.\r\n\r\nThe source is now maintained on heptapod (https:\/\/heptapod.host\/cgtk\/taghighlight).  There is also a mirror on github (https:\/\/github.com\/abudden\/taghighlight-automirror), although I can't guarantee this will be as up to date as the heptapod version.","install_details":"Uses python 2.6+ (including 3.0+), but if you don't have python, there is a compiled (for Windows or Linux) version of that part of the plugin available on the website:\r\n\r\nhttp:\/\/www.cgtk.co.uk\/taghighlight\r\n\r\nIt also requires a few extra highlighting groups to be defined (using :highlight).  See the documentation for details.  Alternatively, install the Bandit colour scheme from vimscript #2645 (or http:\/\/www.cgtk.co.uk\/bandit): this provides all the groups by default.  You can easily customise this if you don't like the colours.","5":"Uses python 2.6+ (including 3.0+), but if you don't have python, there is a compiled (for Windows or Linux) version of that part of the plugin available on the website:\r\n\r\nhttp:\/\/www.cgtk.co.uk\/taghighlight\r\n\r\nIt also requires a few extra highlighting groups to be defined (using :highlight).  See the documentation for details.  Alternatively, install the Bandit colour scheme from vimscript #2645 (or http:\/\/www.cgtk.co.uk\/bandit): this provides all the groups by default.  You can easily customise this if you don't like the colours.","first_name":"Al","6":"Al","last_name":"Budden","7":"Budden","releases":[{"0":"2646","vim_version":"7.0","1":"7.0","script_version":"2.1.4","2":"2.1.4","version_comment":"2.1.4 changes: Added support for Go Programming Language (thanks to Ali Hamdi) and improved internal modeline to make adding new languages easier.\r\n\r\n2.1.3 changes (not uploaded to this site): Fix to make TagHighlight work with pre-7.3-288 versions of Vim (bug in has() function).  Added support for Fortran (thanks to Oleg Lebedev).","3":"2.1.4 changes: Added support for Go Programming Language (thanks to Ali Hamdi) and improved internal modeline to make adding new languages easier.\r\n\r\n2.1.3 changes (not uploaded to this site): Fix to make TagHighlight work with pre-7.3-288 versions of Vim (bug in has() function).  Added support for Fortran (thanks to Oleg Lebedev).","package":"taghighlight_r2.1.4.zip","4":"taghighlight_r2.1.4.zip","src_id":"17066","5":"17066","creation_date":"1323942213","6":"1323942213"},{"0":"2646","vim_version":"7.0","1":"7.0","script_version":"2.1.2","2":"2.1.2","version_comment":"Allow overriding the file-language relationship without having to edit the language definitions.  Added support for Matlab (if your version of ctags supports it).  Added support for .hh extension for C\/C++ headers.  Fixed bug with highlight priority for non-specified types.\r\n","3":"Allow overriding the file-language relationship without having to edit the language definitions.  Added support for Matlab (if your version of ctags supports it).  Added support for .hh extension for C\/C++ headers.  Fixed bug with highlight priority for non-specified types.\r\n","package":"taghighlight_r2.1.2.zip","4":"taghighlight_r2.1.2.zip","src_id":"16402","5":"16402","creation_date":"1314709546","6":"1314709546"},{"0":"2646","vim_version":"7.0","1":"7.0","script_version":"2.1.1","2":"2.1.1","version_comment":"Addition of LanguageDetectionMethods option to allow loading of types when FileType or Syntax are set (thanks to Hong Xu for the suggestion).  This also involved addition of syntax and filetype definitions to all languages.  Prevent Vim from repeatedly loading autocmds in plugin development mode.  Don't overwrite Cursor colour definitions with SQL cursor colouring (thanks again to Hong Xu for reporting this bug).\r\n","3":"Addition of LanguageDetectionMethods option to allow loading of types when FileType or Syntax are set (thanks to Hong Xu for the suggestion).  This also involved addition of syntax and filetype definitions to all languages.  Prevent Vim from repeatedly loading autocmds in plugin development mode.  Don't overwrite Cursor colour definitions with SQL cursor colouring (thanks again to Hong Xu for reporting this bug).\r\n","package":"taghighlight_r2.1.1.zip","4":"taghighlight_r2.1.1.zip","src_id":"16334","5":"16334","creation_date":"1314105394","6":"1314105394"},{"0":"2646","vim_version":"7.0","1":"7.0","script_version":"2.1.0","2":"2.1.0","version_comment":"This is a replacement for the previous \"ctags_highlighter\" script that I wrote a while ago, with quite a few changes\/improvements:\r\n\r\n* Now works well even if you don't keep the current directory at the root of your project;\r\n* Recursive by default (rather than with '!' on command);\r\n* Works with any recent python (2.6+, 3.0+), with or without the Vim python interface; alternatively a binary version is available for Linux or Windows if you don't have a recent version of python installed;\r\n* MUCH more customisable and project options are easier to set;\r\n* Better standard library support (e.g. highlight of tag names for Qt4, JDK, Android, wxWidgets etc) with a separate download from the (new)  website - much easier to create new standard libraries;\r\n* Support for user libraries (highlighting of tag names for your own library\r\n* Much easier to add support for new programming languages - all defined with a single text file (assuming ctags supports the language);\r\n* Uses Vim's autoload mechanism, so should be quicker to load;\r\n* Uses a dictionary for settings, so less namespace clutter;\r\n* Support for pre- and post- update and read hooks in case you really want to do something clever;\r\n* New website (http:\/\/www.cgtk.co.uk\/taghighlight)\r\n\r\nThis is the first release of the new version.  I would like to extend my gratitude to Aleksey Baibarin, Marcus Martin, Mishail, Prasun Ratn and Yongwei Wu for their help testing all the various pre-releases of the new version.  Without their help, there would be a LOT more bugs in this version than there are now!","3":"This is a replacement for the previous \"ctags_highlighter\" script that I wrote a while ago, with quite a few changes\/improvements:\r\n\r\n* Now works well even if you don't keep the current directory at the root of your project;\r\n* Recursive by default (rather than with '!' on command);\r\n* Works with any recent python (2.6+, 3.0+), with or without the Vim python interface; alternatively a binary version is available for Linux or Windows if you don't have a recent version of python installed;\r\n* MUCH more customisable and project options are easier to set;\r\n* Better standard library support (e.g. highlight of tag names for Qt4, JDK, Android, wxWidgets etc) with a separate download from the (new)  website - much easier to create new standard libraries;\r\n* Support for user libraries (highlighting of tag names for your own library\r\n* Much easier to add support for new programming languages - all defined with a single text file (assuming ctags supports the language);\r\n* Uses Vim's autoload mechanism, so should be quicker to load;\r\n* Uses a dictionary for settings, so less namespace clutter;\r\n* Support for pre- and post- update and read hooks in case you really want to do something clever;\r\n* New website (http:\/\/www.cgtk.co.uk\/taghighlight)\r\n\r\nThis is the first release of the new version.  I would like to extend my gratitude to Aleksey Baibarin, Marcus Martin, Mishail, Prasun Ratn and Yongwei Wu for their help testing all the various pre-releases of the new version.  Without their help, there would be a LOT more bugs in this version than there are now!","package":"taghighlight_r2.1.0.zip","4":"taghighlight_r2.1.0.zip","src_id":"16328","5":"16328","creation_date":"1313999078","6":"1313999078"},{"0":"2646","vim_version":"7.0","1":"7.0","script_version":"r458","2":"r458","version_comment":"Inclusion of vim keywords controlled by separate option.","3":"Inclusion of vim keywords controlled by separate option.","package":"ctags_highlighting.vba","4":"ctags_highlighting.vba","src_id":"15406","5":"15406","creation_date":"1302160446","6":"1302160446"},{"0":"2646","vim_version":"7.0","1":"7.0","script_version":"r456","2":"r456","version_comment":"Fixed accidental change of line-endings.","3":"Fixed accidental change of line-endings.","package":"ctags_highlighting.vba","4":"ctags_highlighting.vba","src_id":"15401","5":"15401","creation_date":"1302087557","6":"1302087557"},{"0":"2646","vim_version":"7.0","1":"7.0","script_version":"r454","2":"r454","version_comment":"Fixed accidental change of file-type.","3":"Fixed accidental change of file-type.","package":"ctags_highlighting.vba","4":"ctags_highlighting.vba","src_id":"15400","5":"15400","creation_date":"1302085307","6":"1302085307"},{"0":"2646","vim_version":"7.0","1":"7.0","script_version":"r452","2":"r452","version_comment":"Better handling of unknown ctags tag kinds.","3":"Better handling of unknown ctags tag kinds.","package":"ctags_highlighting.vba","4":"ctags_highlighting.vba","src_id":"15399","5":"15399","creation_date":"1302075720","6":"1302075720"},{"0":"2646","vim_version":"7.0","1":"7.0","script_version":"r443","2":"r443","version_comment":"Allow customisation of the filenames used for tags and types files (thanks to Sung Pae).","3":"Allow customisation of the filenames used for tags and types files (thanks to Sung Pae).","package":"ctags_highlighting.vba","4":"ctags_highlighting.vba","src_id":"15071","5":"15071","creation_date":"1298378195","6":"1298378195"},{"0":"2646","vim_version":"7.0","1":"7.0","script_version":"r442","2":"r442","version_comment":"Improved type prioritisation for object-oriented languages.","3":"Improved type prioritisation for object-oriented languages.","package":"ctags_highlighting.vba","4":"ctags_highlighting.vba","src_id":"15027","5":"15027","creation_date":"1297864214","6":"1297864214"},{"0":"2646","vim_version":"7.0","1":"7.0","script_version":"r440","2":"r440","version_comment":"Added better support for different C++ extensions and to avoid conflicts with C# files.","3":"Added better support for different C++ extensions and to avoid conflicts with C# files.","package":"ctags_highlighting.vba","4":"ctags_highlighting.vba","src_id":"15026","5":"15026","creation_date":"1297860802","6":"1297860802"},{"0":"2646","vim_version":"7.0","1":"7.0","script_version":"r435","2":"r435","version_comment":"Changed default to not include syntax matches unless either g:TypesFileIncludeSynMatches or b:TypesFileIncludeSynMatches is set to 1 (this makes the highlighting much faster for large projects).","3":"Changed default to not include syntax matches unless either g:TypesFileIncludeSynMatches or b:TypesFileIncludeSynMatches is set to 1 (this makes the highlighting much faster for large projects).","package":"ctags_highlighting.vba","4":"ctags_highlighting.vba","src_id":"14737","5":"14737","creation_date":"1294841029","6":"1294841029"},{"0":"2646","vim_version":"7.0","1":"7.0","script_version":"r431","2":"r431","version_comment":"Better support for paths with spaces in them.  Added support for Android SDK and Java JDK (requires latest gui_types_and_tags from the website).  Optional local variable highlighting (see caveats on the website) for Java, C# and C++ as well as C.","3":"Better support for paths with spaces in them.  Added support for Android SDK and Java JDK (requires latest gui_types_and_tags from the website).  Optional local variable highlighting (see caveats on the website) for Java, C# and C++ as well as C.","package":"ctags_highlighting.vba","4":"ctags_highlighting.vba","src_id":"14422","5":"14422","creation_date":"1291369346","6":"1291369346"},{"0":"2646","vim_version":"7.0","1":"7.0","script_version":"r398","2":"r398","version_comment":"Added support for ctags 'import' type in python.","3":"Added support for ctags 'import' type in python.","package":"ctags_highlighting.vba","4":"ctags_highlighting.vba","src_id":"12740","5":"12740","creation_date":"1269933496","6":"1269933496"},{"0":"2646","vim_version":"7.0","1":"7.0","script_version":"r396","2":"r396","version_comment":"Significantly improved support for languages other than C.  Factored out redundant ctags_* intermediate highlight groups.","3":"Significantly improved support for languages other than C.  Factored out redundant ctags_* intermediate highlight groups.","package":"ctags_highlighting.vba","4":"ctags_highlighting.vba","src_id":"12734","5":"12734","creation_date":"1269862952","6":"1269862952"},{"0":"2646","vim_version":"7.0","1":"7.0","script_version":"r391","2":"r391","version_comment":"Better support for different languages including support for C# (thanks to Aleksey Baibarin).","3":"Better support for different languages including support for C# (thanks to Aleksey Baibarin).","package":"ctags_highlighting.vba","4":"ctags_highlighting.vba","src_id":"12550","5":"12550","creation_date":"1267622304","6":"1267622304"},{"0":"2646","vim_version":"7.0","1":"7.0","script_version":"387","2":"387","version_comment":"Fixed bug in new vimfiles location operation.","3":"Fixed bug in new vimfiles location operation.","package":"ctags_highlighting.vba","4":"ctags_highlighting.vba","src_id":"12432","5":"12432","creation_date":"1266594637","6":"1266594637"},{"0":"2646","vim_version":"7.0","1":"7.0","script_version":"r384","2":"r384","version_comment":"Improvements to VIMFILESDIR identification.  Re-architecture of type definitions to make them more sensitive to different ctags \"kinds\" for different languages.  Note that Enumerator has been renamed to EnumerationValue: the latest Bandit Colour Scheme supports this.  Fixed escaping of paths and operation of ReadTypes when not in an autocommand.","3":"Improvements to VIMFILESDIR identification.  Re-architecture of type definitions to make them more sensitive to different ctags \"kinds\" for different languages.  Note that Enumerator has been renamed to EnumerationValue: the latest Bandit Colour Scheme supports this.  Fixed escaping of paths and operation of ReadTypes when not in an autocommand.","package":"ctags_highlighting.vba","4":"ctags_highlighting.vba","src_id":"12430","5":"12430","creation_date":"1266594213","6":"1266594213"},{"0":"2646","vim_version":"7.0","1":"7.0","script_version":"r340","2":"r340","version_comment":"Added missing winrestview() call (thanks to Yongwei Wu for reporting this).","3":"Added missing winrestview() call (thanks to Yongwei Wu for reporting this).","package":"ctags_highlighting.vba","4":"ctags_highlighting.vba","src_id":"11648","5":"11648","creation_date":"1257150622","6":"1257150622"},{"0":"2646","vim_version":"7.0","1":"7.0","script_version":"r309","2":"r309","version_comment":"Added experimental PHP support and a lot more documentation.","3":"Added experimental PHP support and a lot more documentation.","package":"ctags_highlighting.vba","4":"ctags_highlighting.vba","src_id":"11207","5":"11207","creation_date":"1250579975","6":"1250579975"},{"0":"2646","vim_version":"7.0","1":"7.0","script_version":"r301","2":"r301","version_comment":"Added shellescape() to GUI types and tags files and moved them out of the main distribution (see update 7th August 2009 on the website).","3":"Added shellescape() to GUI types and tags files and moved them out of the main distribution (see update 7th August 2009 on the website).","package":"ctags_highlighting.vba","4":"ctags_highlighting.vba","src_id":"11145","5":"11145","creation_date":"1249631217","6":"1249631217"},{"0":"2646","vim_version":"7.0","1":"7.0","script_version":"r292","2":"r292","version_comment":"Fixed bug with (optional) cscope database generation.","3":"Fixed bug with (optional) cscope database generation.","package":"ctags_highlighting.vba","4":"ctags_highlighting.vba","src_id":"11121","5":"11121","creation_date":"1249293922","6":"1249293922"},{"0":"2646","vim_version":"7.0","1":"7.0","script_version":"r286","2":"r286","version_comment":"Fix for Linux spaced paths (Mikhail Stepura).","3":"Fix for Linux spaced paths (Mikhail Stepura).","package":"ctags_highlighting.vba","4":"ctags_highlighting.vba","src_id":"11069","5":"11069","creation_date":"1248680242","6":"1248680242"},{"0":"2646","vim_version":"7.0","1":"7.0","script_version":"r285","2":"r285","version_comment":"Added support for ctags being stored in a path with spaces and other odd characters (thanks to Mikhail Stepura).","3":"Added support for ctags being stored in a path with spaces and other odd characters (thanks to Mikhail Stepura).","package":"ctags_highlighting.vba","4":"ctags_highlighting.vba","src_id":"11068","5":"11068","creation_date":"1248679956","6":"1248679956"},{"0":"2646","vim_version":"7.0","1":"7.0","script_version":"r262","2":"r262","version_comment":"Changed some of the defaults to the python script (so fewer options need to be passed by UpdateTypesFile).  It should now be possible to generate the types file simply by running \"mktypes.py\" or \"mktypes.py -r\" in the project directory.  Of course, UpdateTypesFile still works too.  Added UpdateTypesFileOnly command for projects in which the tags file is updated externally (e.g. the Linux kernel source).  Removed regular expression matches by default: this is much quicker for large projects.  Also added more screenshots to the website.","3":"Changed some of the defaults to the python script (so fewer options need to be passed by UpdateTypesFile).  It should now be possible to generate the types file simply by running \"mktypes.py\" or \"mktypes.py -r\" in the project directory.  Of course, UpdateTypesFile still works too.  Added UpdateTypesFileOnly command for projects in which the tags file is updated externally (e.g. the Linux kernel source).  Removed regular expression matches by default: this is much quicker for large projects.  Also added more screenshots to the website.","package":"ctags_highlighting.vba","4":"ctags_highlighting.vba","src_id":"10671","5":"10671","creation_date":"1243098258","6":"1243098258"},{"0":"2646","vim_version":"7.0","1":"7.0","script_version":"r233","2":"r233","version_comment":"Initial upload","3":"Initial upload","package":"ctags_highlighting.vba","4":"ctags_highlighting.vba","src_id":"10649","5":"10649","creation_date":"1242911528","6":"1242911528"}]},"2645":{"script_id":"2645","0":"2645","script_name":"bandit.vim","1":"bandit.vim","script_type":"color scheme","2":"color scheme","summary":"Colour Scheme","3":"Colour Scheme","description":"This is the colour scheme that I use for all editing tasks.  It is primarily designed for use with a dark background (as I find this easier on the eyes), but I'm gradually adding more support for light backgrounds as well.  It makes full use of the available colour palette, so looks better in gvim than in console vim (although I still like the console version).\r\n\r\nMore details (and screenshots) at https:\/\/sites.google.com\/site\/abudden\/contents\/Vim-Scripts\/bandit-colour-scheme\r\n\r\nUnusual Features\r\n\r\nThe colour scheme has a few slightly unusual features as Vim colour schemes go:\r\n\r\nSupport for a lot more highlighting groups than most colour schemes (including the result of the ctags-based highlighter: vimscript#2646, and Dr Chip's rainbow.vim).\r\n\r\nRequires Vim 7 or above (I got irritated by the syntax for colour schemes, so I made my own) If you install the associated syntax file, it is self colouring, so you can see the colour scheme clearly when viewing the source file (the 'ColourAssignment' text is highlighted appropriately: see the screenshots on the website).\r\n\r\nSemi-automatic generation of light background colour choices (see website)","4":"This is the colour scheme that I use for all editing tasks.  It is primarily designed for use with a dark background (as I find this easier on the eyes), but I'm gradually adding more support for light backgrounds as well.  It makes full use of the available colour palette, so looks better in gvim than in console vim (although I still like the console version).\r\n\r\nMore details (and screenshots) at https:\/\/sites.google.com\/site\/abudden\/contents\/Vim-Scripts\/bandit-colour-scheme\r\n\r\nUnusual Features\r\n\r\nThe colour scheme has a few slightly unusual features as Vim colour schemes go:\r\n\r\nSupport for a lot more highlighting groups than most colour schemes (including the result of the ctags-based highlighter: vimscript#2646, and Dr Chip's rainbow.vim).\r\n\r\nRequires Vim 7 or above (I got irritated by the syntax for colour schemes, so I made my own) If you install the associated syntax file, it is self colouring, so you can see the colour scheme clearly when viewing the source file (the 'ColourAssignment' text is highlighted appropriately: see the screenshots on the website).\r\n\r\nSemi-automatic generation of light background colour choices (see website)","install_details":"","5":"","first_name":"Al","6":"Al","last_name":"Budden","7":"Budden","releases":[{"0":"2645","vim_version":"7.0","1":"7.0","script_version":"r425","2":"r425","version_comment":"Added support for latest CTagsHighlighter and Java bracket highlighting","3":"Added support for latest CTagsHighlighter and Java bracket highlighting","package":"colourscheme_bandit.vba","4":"colourscheme_bandit.vba","src_id":"14421","5":"14421","creation_date":"1291369253","6":"1291369253"},{"0":"2645","vim_version":"7.0","1":"7.0","script_version":"r391","2":"r391","version_comment":"Better support for latest ctags highlighter.","3":"Better support for latest ctags highlighter.","package":"colourscheme_bandit.vba","4":"colourscheme_bandit.vba","src_id":"12549","5":"12549","creation_date":"1267622239","6":"1267622239"},{"0":"2645","vim_version":"7.0","1":"7.0","script_version":"r384","2":"r384","version_comment":"Added support for latest ctags highlighter (which uses EnumerationValue instead of Enumerator).","3":"Added support for latest ctags highlighter (which uses EnumerationValue instead of Enumerator).","package":"colourscheme_bandit.vba","4":"colourscheme_bandit.vba","src_id":"12429","5":"12429","creation_date":"1266594137","6":"1266594137"},{"0":"2645","vim_version":"7.0","1":"7.0","script_version":"r341","2":"r341","version_comment":"Added some protection against creating erroneous highlight groups.","3":"Added some protection against creating erroneous highlight groups.","package":"colourscheme_bandit.vba","4":"colourscheme_bandit.vba","src_id":"11649","5":"11649","creation_date":"1257172997","6":"1257172997"},{"0":"2645","vim_version":"7.0","1":"7.0","script_version":"r290","2":"r290","version_comment":"Added more colour groups and automatic reloading of colour scheme when changes are written.","3":"Added more colour groups and automatic reloading of colour scheme when changes are written.","package":"colourscheme_bandit.vba","4":"colourscheme_bandit.vba","src_id":"11082","5":"11082","creation_date":"1248876320","6":"1248876320"},{"0":"2645","vim_version":"7.0","1":"7.0","script_version":"r274","2":"r274","version_comment":"Added colouring of sign column and splits.","3":"Added colouring of sign column and splits.","package":"colourscheme_bandit.vba","4":"colourscheme_bandit.vba","src_id":"10977","5":"10977","creation_date":"1247128480","6":"1247128480"},{"0":"2645","vim_version":"7.0","1":"7.0","script_version":"r264","2":"r264","version_comment":"Added custom colouring of more groups, including the status line and the line numbering area.","3":"Added custom colouring of more groups, including the status line and the line numbering area.","package":"colourscheme_bandit.vba","4":"colourscheme_bandit.vba","src_id":"10835","5":"10835","creation_date":"1245077105","6":"1245077105"},{"0":"2645","vim_version":"7.0","1":"7.0","script_version":"r233","2":"r233","version_comment":"Initial upload","3":"Initial upload","package":"colourscheme_bandit.vba","4":"colourscheme_bandit.vba","src_id":"10648","5":"10648","creation_date":"1242911181","6":"1242911181"}]},"2644":{"script_id":"2644","0":"2644","script_name":"Erlang_detectVariable","1":"Erlang_detectVariable","script_type":"syntax","2":"syntax","summary":"detect Erlang variables","3":"detect Erlang variables","description":"Erlang variables are formated in '[A-Z]\\+[a-zA-Z0-9]*'.\r\nbecause, enhace default erlang.vm.\r\n\r\nsee below:\r\n----------------------------------------------------------------------------\r\nsyn match   erlangVariable         \/[A-Z]\\+[a-zA-Z0-9]*\/\r\nhi erlangVariable guifg=#23BF73\r\n----------------------------------------------------------------------------","4":"Erlang variables are formated in '[A-Z]\\+[a-zA-Z0-9]*'.\r\nbecause, enhace default erlang.vm.\r\n\r\nsee below:\r\n----------------------------------------------------------------------------\r\nsyn match   erlangVariable         \/[A-Z]\\+[a-zA-Z0-9]*\/\r\nhi erlangVariable guifg=#23BF73\r\n----------------------------------------------------------------------------","install_details":"put in $VIM\\vimfiles\\after\\syntax\\\r\n\r\n( or more low grade runtimepath. if you understand this mean, show runtimepath option \":set runtimepath\" ) ","5":"put in $VIM\\vimfiles\\after\\syntax\\\r\n\r\n( or more low grade runtimepath. if you understand this mean, show runtimepath option \":set runtimepath\" ) ","first_name":"masami","6":"masami","last_name":"ito","7":"ito","releases":[{"0":"2644","vim_version":"7.0","1":"7.0","script_version":"1.1","2":"1.1","version_comment":"this syntax file enhanced erlang-syntax and set color. put in $VIM\\vimfiles\\after\\syntax ( or more low grade runtimepath. if you understand this mean, show runtimepath option \":set runtimepath\" )\r\n\r\nremove erlang_detectVariable 1.0.","3":"this syntax file enhanced erlang-syntax and set color. put in $VIM\\vimfiles\\after\\syntax ( or more low grade runtimepath. if you understand this mean, show runtimepath option \":set runtimepath\" )\r\n\r\nremove erlang_detectVariable 1.0.","package":"erlang_detectVariables.zip","4":"erlang_detectVariables.zip","src_id":"10665","5":"10665","creation_date":"1243060593","6":"1243060593"},{"0":"2644","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"i got wrong about 'initial script version' meaning.. orz","3":"i got wrong about 'initial script version' meaning.. orz","package":"erlang_detectVariables.zip","4":"erlang_detectVariables.zip","src_id":"10644","5":"10644","creation_date":"1242837597","6":"1242837597"}]},"2643":{"script_id":"2643","0":"2643","script_name":"python_coverage.vim","1":"python_coverage.vim","script_type":"syntax","2":"syntax","summary":"syntax highlighting for python coverage files","3":"syntax highlighting for python coverage files","description":"highlights `.cover` files as made by `coverage.py` and `figleaf`","4":"highlights `.cover` files as made by `coverage.py` and `figleaf`","install_details":"","5":"","first_name":"Dan","6":"Dan","last_name":"Buch","7":"Buch","releases":[{"0":"2643","vim_version":"6.0","1":"6.0","script_version":"0.1.0","2":"0.1.0","version_comment":"Initial upload","3":"Initial upload","package":"python_coverage.vim","4":"python_coverage.vim","src_id":"10641","5":"10641","creation_date":"1242834857","6":"1242834857"}]},"2642":{"script_id":"2642","0":"2642","script_name":"PLI Auto Complete","1":"PLI Auto Complete","script_type":"ftplugin","2":"ftplugin","summary":"Complete Member Variable For z\/OS Enterprise Compiler PLI","3":"Complete Member Variable For z\/OS Enterprise Compiler PLI","description":"Complete member variable for PL\/I filetype on mainframe, inlcude variables in copybooks.\r\nCurrently support 2 types of copybook, e.g. normal copybook and maps in diffrent folders.\r\n\r\nStep 1\r\nChange .vimrc:\r\nlet g:CpyCompleteInd     = 1            \"Enable complete for copybook, other value will disable\r\nlet g:CpyIdentification  = \"CPY\"        \"Copybook Include Method\r\nlet g:CpyDir             = \"Folder1\"    \"Folder Of Copybook, Include The Last \/\r\nlet g:MapIdentification  = \"MAP\"        \"Maps Include Method\r\nlet g:MapDir             = \"Folder2\"    \"Folder Of Maps, Include The Last \/\r\nif has(\"autocmd\")\r\n   au FileType pli setl cfu=plicomplete#Complete\r\nendif\r\n\r\nThe Include Method should be change base on yours, \r\nlike %INCLUDE CPY(COPYBOOK); it should be CPY\r\n\r\nStep 2\r\nPress <C-X><C-U> after type one dot,the variables should be poped up.\r\n\r\nScreen Shot:http:\/\/photo1.bababian.com\/upload13\/20090505\/F9FC04A492D5138A202EA67F368AF38F.jpg","4":"Complete member variable for PL\/I filetype on mainframe, inlcude variables in copybooks.\r\nCurrently support 2 types of copybook, e.g. normal copybook and maps in diffrent folders.\r\n\r\nStep 1\r\nChange .vimrc:\r\nlet g:CpyCompleteInd     = 1            \"Enable complete for copybook, other value will disable\r\nlet g:CpyIdentification  = \"CPY\"        \"Copybook Include Method\r\nlet g:CpyDir             = \"Folder1\"    \"Folder Of Copybook, Include The Last \/\r\nlet g:MapIdentification  = \"MAP\"        \"Maps Include Method\r\nlet g:MapDir             = \"Folder2\"    \"Folder Of Maps, Include The Last \/\r\nif has(\"autocmd\")\r\n   au FileType pli setl cfu=plicomplete#Complete\r\nendif\r\n\r\nThe Include Method should be change base on yours, \r\nlike %INCLUDE CPY(COPYBOOK); it should be CPY\r\n\r\nStep 2\r\nPress <C-X><C-U> after type one dot,the variables should be poped up.\r\n\r\nScreen Shot:http:\/\/photo1.bababian.com\/upload13\/20090505\/F9FC04A492D5138A202EA67F368AF38F.jpg","install_details":"Put it into $VIM\/vimfiles\/autoload","5":"Put it into $VIM\/vimfiles\/autoload","first_name":"Ricky","6":"Ricky","last_name":"Wu","7":"Wu","releases":[{"0":"2642","vim_version":"7.0","1":"7.0","script_version":"0.2","2":"0.2","version_comment":"More easy to setup. Only need add global var.","3":"More easy to setup. Only need add global var.","package":"plicomplete.vim","4":"plicomplete.vim","src_id":"10681","5":"10681","creation_date":"1243346790","6":"1243346790"},{"0":"2642","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"plicomplete.vim","4":"plicomplete.vim","src_id":"10638","5":"10638","creation_date":"1242828964","6":"1242828964"}]},"2641":{"script_id":"2641","0":"2641","script_name":"haskell.vim","1":"haskell.vim","script_type":"syntax","2":"syntax","summary":"Updated with `for` in standalone deriving.","3":"Updated with `for` in standalone deriving.","description":"Variation of the original `haskell.vim` that recognizes `for` as a keyword (due to its use in standalone deriving declarations).","4":"Variation of the original `haskell.vim` that recognizes `for` as a keyword (due to its use in standalone deriving declarations).","install_details":"","5":"","first_name":"Jason","6":"Jason","last_name":"Dusek","7":"Dusek","releases":[{"0":"2641","vim_version":"7.0","1":"7.0","script_version":"1.2.1","2":"1.2.1","version_comment":"Initial upload","3":"Initial upload","package":"haskell.vim","4":"haskell.vim","src_id":"10635","5":"10635","creation_date":"1242768321","6":"1242768321"}]},"2640":{"script_id":"2640","0":"2640","script_name":"tango-morning.vim","1":"tango-morning.vim","script_type":"color scheme","2":"color scheme","summary":"Light Grey Tango color theme based on Morning","3":"Light Grey Tango color theme based on Morning","description":"\"tango-morning\" is a colorscheme inspired by the \"morning\" colorscheme by Bram.\r\nThe gui colors use the Tango Color palette, while the terminal colors are retained from the \"morning\" colorscheme.\r\nThe \"morning\" color scheme has problems in displaying diffs, which this theme tries to address, and uses elegant soft shades.\r\n\r\nSample Screenshot :http:\/\/img190.imageshack.us\/img190\/1848\/vimtangomorningtheme.png","4":"\"tango-morning\" is a colorscheme inspired by the \"morning\" colorscheme by Bram.\r\nThe gui colors use the Tango Color palette, while the terminal colors are retained from the \"morning\" colorscheme.\r\nThe \"morning\" color scheme has problems in displaying diffs, which this theme tries to address, and uses elegant soft shades.\r\n\r\nSample Screenshot :http:\/\/img190.imageshack.us\/img190\/1848\/vimtangomorningtheme.png","install_details":"=== Linux  ===\r\nmkdir ~\/.vim\/colors\r\ncp tango-morning.vim  ~\/.vim\/colors\r\n\r\n=== Windows ===\r\ncopy the file tango-morning.vim to vim7x\/colors\/\r\n\r\n=== Usage ===\r\nTo use the color scheme, \r\n:colorscheme tango-morning","5":"=== Linux  ===\r\nmkdir ~\/.vim\/colors\r\ncp tango-morning.vim  ~\/.vim\/colors\r\n\r\n=== Windows ===\r\ncopy the file tango-morning.vim to vim7x\/colors\/\r\n\r\n=== Usage ===\r\nTo use the color scheme, \r\n:colorscheme tango-morning","first_name":"vineeth","6":"vineeth","last_name":"n","7":"n","releases":[{"0":"2640","vim_version":"7.0","1":"7.0","script_version":"0.3","2":"0.3","version_comment":"Fix color for FoldColumn, ParenMatch","3":"Fix color for FoldColumn, ParenMatch","package":"tango-morning.vim","4":"tango-morning.vim","src_id":"10685","5":"10685","creation_date":"1243432120","6":"1243432120"},{"0":"2640","vim_version":"7.0","1":"7.0","script_version":"0.2","2":"0.2","version_comment":"Fixes for Auto completion dropdown menu, NonText region","3":"Fixes for Auto completion dropdown menu, NonText region","package":"tango-morning.vim","4":"tango-morning.vim","src_id":"10640","5":"10640","creation_date":"1242833729","6":"1242833729"},{"0":"2640","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"tango-morning.vim","4":"tango-morning.vim","src_id":"10633","5":"10633","creation_date":"1242750018","6":"1242750018"}]},"2639":{"script_id":"2639","0":"2639","script_name":"jlj.vim","1":"jlj.vim","script_type":"syntax","2":"syntax","summary":"Syntax for JLJ Post files","3":"Syntax for JLJ Post files","description":"A syntax file for the files used by JLJ (http:\/\/umlautllama.com\/projects\/perl\/#jlj), a LiveJournal entry system for the terminal.\r\n\r\nEasily supports including either HTML or Markdown (see http:\/\/www.vim.org\/scripts\/script.php?script_id=1242) syntax, and adding your own should be easy as well.","4":"A syntax file for the files used by JLJ (http:\/\/umlautllama.com\/projects\/perl\/#jlj), a LiveJournal entry system for the terminal.\r\n\r\nEasily supports including either HTML or Markdown (see http:\/\/www.vim.org\/scripts\/script.php?script_id=1242) syntax, and adding your own should be easy as well.","install_details":"Unpack the tarball into ~\/.vim\r\n\r\nYou may wish to edit ~\/.vim\/syntax\/jlj.vim to set the included highlighting for the formatter you use (HTML is the default).","5":"Unpack the tarball into ~\/.vim\r\n\r\nYou may wish to edit ~\/.vim\/syntax\/jlj.vim to set the included highlighting for the formatter you use (HTML is the default).","first_name":"Marc","6":"Marc","last_name":"Hartstein","7":"Hartstein","releases":[{"0":"2639","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"jlj.tar.gz","4":"jlj.tar.gz","src_id":"10631","5":"10631","creation_date":"1242682041","6":"1242682041"}]},"2638":{"script_id":"2638","0":"2638","script_name":"blogger","1":"blogger","script_type":"utility","2":"utility","summary":"The only one vim script which handles Blogger. Powered by Metarw.","3":"The only one vim script which handles Blogger. Powered by Metarw.","description":"See http:\/\/github.com\/ujihisa\/blogger.vim","4":"See http:\/\/github.com\/ujihisa\/blogger.vim","install_details":"","5":"","first_name":"ujihisa","6":"ujihisa","last_name":".","7":".","releases":[{"0":"2638","vim_version":"7.0","1":"7.0","script_version":"2.5","2":"2.5","version_comment":"* [Feature] Supports draft on blogger. (thanks to @mahm!)\n","3":"* [Feature] Supports draft on blogger. (thanks to @mahm!)\n","package":"blogger-2.5.zip","4":"blogger-2.5.zip","src_id":"14878","5":"14878","creation_date":"1296086880","6":"1296086880"},{"0":"2638","vim_version":"7.0","1":"7.0","script_version":"2.4","2":"2.4","version_comment":"* Removing peg-markdown Rubygems library dependency\n","3":"* Removing peg-markdown Rubygems library dependency\n","package":"blogger-2.4.zip","4":"blogger-2.4.zip","src_id":"14247","5":"14247","creation_date":"1289635830","6":"1289635830"},{"0":"2638","vim_version":"7.0","1":"7.0","script_version":"2.3","2":"2.3","version_comment":"* [Bugfix] Supports rpeg-markdown without rubygems\n* [Feature] g:blogger_ruby_path for ~\/.vimrc\n","3":"* [Bugfix] Supports rpeg-markdown without rubygems\n* [Feature] g:blogger_ruby_path for ~\/.vimrc\n","package":"blogger-2.3.zip","4":"blogger-2.3.zip","src_id":"13583","5":"13583","creation_date":"1281904513","6":"1281904513"},{"0":"2638","vim_version":"7.0","1":"7.0","script_version":"2.2","2":"2.2","version_comment":"* [Bugfix] Follows changes in nokogiri or blogger; you can edit posts again.\n","3":"* [Bugfix] Follows changes in nokogiri or blogger; you can edit posts again.\n","package":"blogger-2.2.zip","4":"blogger-2.2.zip","src_id":"13346","5":"13346","creation_date":"1279398308","6":"1279398308"},{"0":"2638","vim_version":"7.0","1":"7.0","script_version":"2.1","2":"2.1","version_comment":"* [Bugfix] Supports bloggers who use \"summarize\" feature\n","3":"* [Bugfix] Supports bloggers who use \"summarize\" feature\n","package":"blogger-2.1.zip","4":"blogger-2.1.zip","src_id":"12612","5":"12612","creation_date":"1268431421","6":"1268431421"},{"0":"2638","vim_version":"7.0","1":"7.0","script_version":"2.0","2":"2.0","version_comment":"* [Feature] Gist support. (Greatefully thanks to Sora Harakami!)\n* `let g:blogger_gist = 1` allows you to post long code into gist automatically.\n","3":"* [Feature] Gist support. (Greatefully thanks to Sora Harakami!)\n* `let g:blogger_gist = 1` allows you to post long code into gist automatically.\n","package":"blogger-2.0.zip","4":"blogger-2.0.zip","src_id":"12567","5":"12567","creation_date":"1267837769","6":"1267837769"},{"0":"2638","vim_version":"7.0","1":"7.0","script_version":"1.6","2":"1.6","version_comment":"* [Feature] Uses gem net-https-wrapper\n* [Feature] Ignores Hashes and Spaces before the title\n","3":"* [Feature] Uses gem net-https-wrapper\n* [Feature] Ignores Hashes and Spaces before the title\n","package":"blogger-1.6.zip","4":"blogger-1.6.zip","src_id":"11232","5":"11232","creation_date":"1250893314","6":"1250893314"},{"0":"2638","vim_version":"7.0","1":"7.0","script_version":"1.5","2":"1.5","version_comment":"* [Feature] Longer blogger:list\n","3":"* [Feature] Longer blogger:list\n","package":"blogger-1.5.zip","4":"blogger-1.5.zip","src_id":"11079","5":"11079","creation_date":"1248814523","6":"1248814523"},{"0":"2638","vim_version":"7.0","1":"7.0","script_version":"1.4","2":"1.4","version_comment":"* [Bugfix] Enable to handle an old entry in show and update\n* [Bugfix] Remove the last image which is automatically added by blogger web service\n* [Bugfix] Automatically setl mkd filetype\n","3":"* [Bugfix] Enable to handle an old entry in show and update\n* [Bugfix] Remove the last image which is automatically added by blogger web service\n* [Bugfix] Automatically setl mkd filetype\n","package":"blogger-1.4.zip","4":"blogger-1.4.zip","src_id":"11074","5":"11074","creation_date":"1248762160","6":"1248762160"},{"0":"2638","vim_version":"7.0","1":"7.0","script_version":"1.3","2":"1.3","version_comment":"* [Feature] Copy the new blog post URI into clipboard automaticaly in OS X\n* [Feature] Switch to use pandoc from html2text\n* [Bugfix] All bugs by html2text was solved\n","3":"* [Feature] Copy the new blog post URI into clipboard automaticaly in OS X\n* [Feature] Switch to use pandoc from html2text\n* [Bugfix] All bugs by html2text was solved\n","package":"blogger-1.3.zip","4":"blogger-1.3.zip","src_id":"10887","5":"10887","creation_date":"1245668442","6":"1245668442"},{"0":"2638","vim_version":"7.0","1":"7.0","script_version":"1.2","2":"1.2","version_comment":"* [Feature] Automatically rename the fakepath after creating a blog post.\n* [Bugfix] Enabled to post with Inline HTML\n* [Feature] Added Rakefile for an installer (Thanks From Kyushu!)\n* [Bugfix] Fixed the wrong install document (Thanks Karl Schudt!)\n","3":"* [Feature] Automatically rename the fakepath after creating a blog post.\n* [Bugfix] Enabled to post with Inline HTML\n* [Feature] Added Rakefile for an installer (Thanks From Kyushu!)\n* [Bugfix] Fixed the wrong install document (Thanks Karl Schudt!)\n","package":"blogger-1.2.zip","4":"blogger-1.2.zip","src_id":"10772","5":"10772","creation_date":"1244444656","6":"1244444656"},{"0":"2638","vim_version":"7.0","1":"7.0","script_version":"1.1","2":"1.1","version_comment":"* [Feature] Changed the fakepath scheme of metarw\n  * blogger:{blogid}:something -> blogger:something\n  * This change needs you to add g:blogger_blogid on your vimrc\n* [Bugfix] The bug which occurs in updating an exist blog post was fixed\n* [Bugfix] The bug of the ways of handling the multi line codes of  html2text code was fixed\n","3":"* [Feature] Changed the fakepath scheme of metarw\n  * blogger:{blogid}:something -> blogger:something\n  * This change needs you to add g:blogger_blogid on your vimrc\n* [Bugfix] The bug which occurs in updating an exist blog post was fixed\n* [Bugfix] The bug of the ways of handling the multi line codes of  html2text code was fixed\n","package":"blogger-1.1.zip","4":"blogger-1.1.zip","src_id":"10647","5":"10647","creation_date":"1242887298","6":"1242887298"},{"0":"2638","vim_version":"7.2","1":"7.2","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"blogger.vim.zip","4":"blogger.vim.zip","src_id":"10624","5":"10624","creation_date":"1242626691","6":"1242626691"}]},"2637":{"script_id":"2637","0":"2637","script_name":"ScmFrontEnd (former name: MinSCM)","1":"ScmFrontEnd (former name: MinSCM)","script_type":"utility","2":"utility","summary":"An abstract front-end for Mercurial\/Git\/Bazaar","3":"An abstract front-end for Mercurial\/Git\/Bazaar","description":"Repository:\r\n  http:\/\/bitbucket.org\/ns9tks\/vim-scmfrontend\/\r\n\r\nIssues:\r\n  http:\/\/bitbucket.org\/ns9tks\/vim-scmfrontend\/issues\/\r\n\r\nDownload latest(development) version\r\n  https:\/\/bitbucket.org\/ns9tks\/vim-scmfrontend\/get\/tip.zip\r\n\r\nScreenshots:\r\n  http:\/\/bitbucket.org\/ns9tks\/vim-scmfrontend\/wiki\/Screenshots\r\n\r\n==============================================================================\r\nINTRODUCTION                                             *minscm-introduction*\r\n\r\nMinSCM is a plugin to manage your repositories of various SCM system (VCS).\r\nMinSCM provides an abstract interface, so you can manage repositories without\r\nbeing aware of differences between SCM systems.\r\n\r\nFeatures:\r\n  - Mercurial support\r\n  - Git support\r\n  - Bazaar support\r\n  - Abstract interface\r\n  - Many commands\r\n  - Syntax highlighting for status and diff in commit buffer.\r\n  - Syntax highlighting for annotate buffer\r\n  - Completion of revision\/branch names\r\n  - Completion of locations for pull\/push\r\n  - Repositories report on status line\r\n  - Collaboration with Fuzzyfinder plugin\r\n\r\n\r\n==============================================================================\r\nINSTALLATION                                             *minscm-installation*\r\n\r\nPut all files into your runtime directory. If you have the zip file, extract\r\nit to your runtime directory.\r\n\r\nYou should place the files as follows:\r\n>\r\n        <your runtime directory>\/plugin\/minscm.vim\r\n        <your runtime directory>\/autoload\/minscm.vim\r\n        <your runtime directory>\/autoload\/minscm\/mercurial.vim\r\n        ...\r\n<\r\nAnd then update your help tags files to enable MinSCM help. See\r\n|add-local-help| for details.\r\n\r\n==============================================================================\r\nUSAGE                                                           *minscm-usage*\r\n\r\nSee |minscm-commands|.\r\n\r\n                                                           *minscm-statusline*\r\n                                                        *g:minscm_getStatus()*\r\nTo Show Repositories Information In Status Line ~\r\n\r\nUse g:minscm_getStatus(). (see also: |'statusline'|)\r\n\r\n                                                          *minscm-fuzzyfinder*\r\nFuzzyfinder Plugin ~\r\n\r\nMinSCM uses APIs of fuzzyfinder.vim. Following commands are dependent on\r\nfuzzyfinder.vim:\r\n\r\n        :MinSCMFindFile\r\n\r\nfuzzyfinder.vim is available at\r\nhttp:\/\/www.vim.org\/scripts\/script.php?script_id=1984 .\r\n\r\n==============================================================================\r\nCOMMANDS                                                     *minscm-commands*\r\n\r\nAll commands is for a reposity including a file of current buffer.\r\n\r\nIf MinSCM command was executed with a ! modifier, the priority of SCM systems\r\nis reversed.\r\n\r\n                                                              *:MinSCMCommand*\r\n:MinSCMCommand[!]               (Default mapping: \\s:)\r\n\r\n        Executes any command you input.\r\n\r\n                                                           *:MinSCMCommitFile*\r\n:MinSCMCommitFile[!]            (Default mapping: \\sC)\r\n\r\n        Opens temporary buffer for you to enter commit message. Write the\r\n        commit buffer and a file whose buffer was current before is committed.\r\n\r\n\r\n                Used SCM commands ~\r\n                hg  : commit\r\n                git : commit\r\n                bzr : commit\r\n\r\n                                                        *:MinSCMCommitTracked*\r\n:MinSCMCommitTracked[!]         (Default mapping: \\s<C-c>)\r\n\r\n        Opens temporary buffer for you to enter commit message. Write the\r\n        commit buffer and all tracked files are committed.\r\n\r\n                Used SCM commands ~\r\n                hg  : commit\r\n                git : commit -a\r\n                bzr : commit\r\n\r\n                                                            *:MinSCMCommitAll*\r\n:MinSCMCommitAll[!]             (Default mapping: \\sc)\r\n\r\n        Opens temporary buffer for you to enter commit message. Write the\r\n        commit buffer and all files in a working directory of a current\r\n        repository are committed.\r\n\r\n        This command is different from |:MinSCMCommitTracked| in adding\r\n        untracked files to the current repository.\r\n\r\n                Used SCM commands ~\r\n                hg  : commit -A\r\n                git : add -a && commit -a\r\n                bzr : add && commit\r\n\r\n                                                             *:MinSCMCheckout*\r\n:MinSCMCheckout[!]              (Default mapping: \\so)\r\n\r\n        Checkouts specified revision.\r\n\r\n                Used SCM commands ~\r\n                hg  : update\r\n                git : checkout\r\n                bzr : (unavailable)\r\n\r\n                                                                *:MinSCMMerge*\r\n:MinSCMMerge[!]                 (Default mapping: \\sm)\r\n\r\n        Merges working directory of a current repository with specified\r\n        revision.\r\n\r\n                Used SCM commands ~\r\n                hg  : merge\r\n                git : merge\r\n                bzr : (unavailable)\r\n\r\n                                                               *:MinSCMBranch*\r\n:MinSCMBranch[!]                (Default mapping: \\sb)\r\n\r\n        Creates new branch.\r\n\r\n                Used SCM commands ~\r\n                hg  : branch\r\n                git : checkout -b\r\n                bzr : (unavailable)\r\n\r\n                                                         *:MinSCMBranchDelete*\r\n:MinSCMBranchDelete[!]          (Default mapping: \\sB)\r\n\r\n        Deletes a branch.\r\n\r\n                Used SCM commands ~\r\n                hg  : (unavailable)\r\n                git : branch -d\r\n                bzr : (unavailable)\r\n\r\n                                                               *:MinSCMRebase*\r\n:MinSCMRebase[!]                (Default mapping: \\sr)\r\n\r\n        Moves changeset onto specified revision.\r\n\r\n                Used SCM commands ~\r\n                hg  : rebase --keep -b\r\n                git : rebase\r\n                bzr : (unavailable)\r\n\r\n                                                                 *:MinSCMPull*\r\n:MinSCMPull[!]                  (Default mapping: \\s[)\r\n\r\n        Pulls changes from specified repository.\r\n\r\n                Used SCM commands ~\r\n                hg  : pull\r\n                git : pull\r\n                bzr : pull\r\n\r\n                                                                 *:MinSCMPush*\r\n:MinSCMPush[!]                  (Default mapping: \\s])\r\n\r\n        Pushes changes to specified repository.\r\n\r\n                Used SCM commands ~\r\n                hg  : push\r\n                git : push\r\n                bzr : push\r\n\r\n                                                             *:MinSCMDiffFile*\r\n:MinSCMDiffFile[!]              (Default mapping: \\sD)\r\n\r\n        Starts diff mode (like vimdiff) in new tabpage between a file of a\r\n        current buffer and its version of specified revision.\r\n\r\n                Used SCM commands ~\r\n                hg  : cat\r\n                git : cat-file -p\r\n                bzr : cat\r\n\r\n                                                              *:MinSCMDiffAll*\r\n:MinSCMDiffAll[!]               (Default mapping: \\sd)\r\n\r\n        Shows differences between all files in a working directory of a\r\n        current repository and specified revision.\r\n\r\n                Used SCM commands ~\r\n                hg  : diff\r\n                git : diff\r\n                bzr : diff\r\n\r\n                                                              *:MinSCMLogFile*\r\n:MinSCMLogFile[!]               (Default mapping: \\sL)\r\n\r\n        Shows revision history related to a file of a current buffer. (see\r\n        also: |g:minscm_hgLogOption| |g:minscm_gitLogOption|\r\n        |g:minscm_bzrLogOption|)\r\n\r\n                Used SCM commands ~\r\n                hg  : glog\r\n                git : log\r\n                bzr : log\r\n\r\n                                                               *:MinSCMLogAll*\r\n:MinSCMLogAll[!]                (Default mapping: \\sl)\r\n\r\n        Shows revision history. (see also: |g:minscm_hgLogOption|\r\n        |g:minscm_gitLogOption| |g:minscm_bzrLogOption|)\r\n\r\n                Used SCM commands ~\r\n                hg  : glog\r\n                git : log\r\n                bzr : log\r\n\r\n                                                         *:MinSCMAnnotateFile*\r\n:MinSCMAnnotateFile[!]          (Default mapping: \\sn)\r\n\r\n        Shows commit information per file line.\r\n\r\n        Lines which were modified at the commit of specified revision or added\r\n        at the initial commit are highlighted.\r\n\r\n                Used SCM commands ~\r\n                hg  : annotate -nudq\r\n                git : blame\r\n                bzr : annotate --all --long\r\n\r\n                                                               *:MinSCMStatus*\r\n:MinSCMStatus[!]                (Default mapping: \\ss)\r\n\r\n        Shows a list of changed files.\r\n\r\n                Used SCM commands ~\r\n                hg  : status\r\n                git : diff --name-status && ls-files --exclude-standard -o\r\n                bzr : status\r\n\r\n                                                                 *:MinSCMGrep*\r\n:MinSCMGrep[!]                  (Default mapping: \\sg)\r\n\r\n        Searches for specified pattern and creates a |quickfix| list.\r\n\r\n                Used SCM commands ~\r\n                hg  : grep -n\r\n                git : grep -n -e\r\n                bzr : (unavailable)\r\n\r\n                                                         *:MinSCMLoadModified*\r\n:MinSCMLoadModified[!]          (Default mapping: \\s!)\r\n\r\n        Loads all modified files with vim after unloading (by :bdelete)\r\n        buffers which are not modified files.\r\n\r\n                Used SCM commands ~\r\n                hg  : status -mn\r\n                git : ls-files -m\r\n                bzr : status -SV\r\n\r\n                                                              *:MinSCMLoadAll*\r\n:MinSCMLoadAll[!]               (Default mapping: \\s<CR>)\r\n\r\n        Loads all tracked files with vim after unloading (by :bdelete) buffers\r\n        which are not tracked files.\r\n\r\n                Used SCM commands ~\r\n                hg  : locate -f\r\n                git : ls-files\r\n                bzr : ls\r\n\r\n                                                             *:MinSCMFindFile*\r\n:MinSCMFindFile[!]              (Default mapping: \\sf)\r\n\r\n        Opens a selected file from all tracked files using Fuzzyfinder. \r\n        (see also: |minscm-fuzzyfinder|)\r\n\r\n                Used SCM commands ~\r\n                hg  : locate -f\r\n                git : ls-files\r\n                bzr : ls\r\n\r\n==============================================================================\r\n","4":"Repository:\r\n  http:\/\/bitbucket.org\/ns9tks\/vim-scmfrontend\/\r\n\r\nIssues:\r\n  http:\/\/bitbucket.org\/ns9tks\/vim-scmfrontend\/issues\/\r\n\r\nDownload latest(development) version\r\n  https:\/\/bitbucket.org\/ns9tks\/vim-scmfrontend\/get\/tip.zip\r\n\r\nScreenshots:\r\n  http:\/\/bitbucket.org\/ns9tks\/vim-scmfrontend\/wiki\/Screenshots\r\n\r\n==============================================================================\r\nINTRODUCTION                                             *minscm-introduction*\r\n\r\nMinSCM is a plugin to manage your repositories of various SCM system (VCS).\r\nMinSCM provides an abstract interface, so you can manage repositories without\r\nbeing aware of differences between SCM systems.\r\n\r\nFeatures:\r\n  - Mercurial support\r\n  - Git support\r\n  - Bazaar support\r\n  - Abstract interface\r\n  - Many commands\r\n  - Syntax highlighting for status and diff in commit buffer.\r\n  - Syntax highlighting for annotate buffer\r\n  - Completion of revision\/branch names\r\n  - Completion of locations for pull\/push\r\n  - Repositories report on status line\r\n  - Collaboration with Fuzzyfinder plugin\r\n\r\n\r\n==============================================================================\r\nINSTALLATION                                             *minscm-installation*\r\n\r\nPut all files into your runtime directory. If you have the zip file, extract\r\nit to your runtime directory.\r\n\r\nYou should place the files as follows:\r\n>\r\n        <your runtime directory>\/plugin\/minscm.vim\r\n        <your runtime directory>\/autoload\/minscm.vim\r\n        <your runtime directory>\/autoload\/minscm\/mercurial.vim\r\n        ...\r\n<\r\nAnd then update your help tags files to enable MinSCM help. See\r\n|add-local-help| for details.\r\n\r\n==============================================================================\r\nUSAGE                                                           *minscm-usage*\r\n\r\nSee |minscm-commands|.\r\n\r\n                                                           *minscm-statusline*\r\n                                                        *g:minscm_getStatus()*\r\nTo Show Repositories Information In Status Line ~\r\n\r\nUse g:minscm_getStatus(). (see also: |'statusline'|)\r\n\r\n                                                          *minscm-fuzzyfinder*\r\nFuzzyfinder Plugin ~\r\n\r\nMinSCM uses APIs of fuzzyfinder.vim. Following commands are dependent on\r\nfuzzyfinder.vim:\r\n\r\n        :MinSCMFindFile\r\n\r\nfuzzyfinder.vim is available at\r\nhttp:\/\/www.vim.org\/scripts\/script.php?script_id=1984 .\r\n\r\n==============================================================================\r\nCOMMANDS                                                     *minscm-commands*\r\n\r\nAll commands is for a reposity including a file of current buffer.\r\n\r\nIf MinSCM command was executed with a ! modifier, the priority of SCM systems\r\nis reversed.\r\n\r\n                                                              *:MinSCMCommand*\r\n:MinSCMCommand[!]               (Default mapping: \\s:)\r\n\r\n        Executes any command you input.\r\n\r\n                                                           *:MinSCMCommitFile*\r\n:MinSCMCommitFile[!]            (Default mapping: \\sC)\r\n\r\n        Opens temporary buffer for you to enter commit message. Write the\r\n        commit buffer and a file whose buffer was current before is committed.\r\n\r\n\r\n                Used SCM commands ~\r\n                hg  : commit\r\n                git : commit\r\n                bzr : commit\r\n\r\n                                                        *:MinSCMCommitTracked*\r\n:MinSCMCommitTracked[!]         (Default mapping: \\s<C-c>)\r\n\r\n        Opens temporary buffer for you to enter commit message. Write the\r\n        commit buffer and all tracked files are committed.\r\n\r\n                Used SCM commands ~\r\n                hg  : commit\r\n                git : commit -a\r\n                bzr : commit\r\n\r\n                                                            *:MinSCMCommitAll*\r\n:MinSCMCommitAll[!]             (Default mapping: \\sc)\r\n\r\n        Opens temporary buffer for you to enter commit message. Write the\r\n        commit buffer and all files in a working directory of a current\r\n        repository are committed.\r\n\r\n        This command is different from |:MinSCMCommitTracked| in adding\r\n        untracked files to the current repository.\r\n\r\n                Used SCM commands ~\r\n                hg  : commit -A\r\n                git : add -a && commit -a\r\n                bzr : add && commit\r\n\r\n                                                             *:MinSCMCheckout*\r\n:MinSCMCheckout[!]              (Default mapping: \\so)\r\n\r\n        Checkouts specified revision.\r\n\r\n                Used SCM commands ~\r\n                hg  : update\r\n                git : checkout\r\n                bzr : (unavailable)\r\n\r\n                                                                *:MinSCMMerge*\r\n:MinSCMMerge[!]                 (Default mapping: \\sm)\r\n\r\n        Merges working directory of a current repository with specified\r\n        revision.\r\n\r\n                Used SCM commands ~\r\n                hg  : merge\r\n                git : merge\r\n                bzr : (unavailable)\r\n\r\n                                                               *:MinSCMBranch*\r\n:MinSCMBranch[!]                (Default mapping: \\sb)\r\n\r\n        Creates new branch.\r\n\r\n                Used SCM commands ~\r\n                hg  : branch\r\n                git : checkout -b\r\n                bzr : (unavailable)\r\n\r\n                                                         *:MinSCMBranchDelete*\r\n:MinSCMBranchDelete[!]          (Default mapping: \\sB)\r\n\r\n        Deletes a branch.\r\n\r\n                Used SCM commands ~\r\n                hg  : (unavailable)\r\n                git : branch -d\r\n                bzr : (unavailable)\r\n\r\n                                                               *:MinSCMRebase*\r\n:MinSCMRebase[!]                (Default mapping: \\sr)\r\n\r\n        Moves changeset onto specified revision.\r\n\r\n                Used SCM commands ~\r\n                hg  : rebase --keep -b\r\n                git : rebase\r\n                bzr : (unavailable)\r\n\r\n                                                                 *:MinSCMPull*\r\n:MinSCMPull[!]                  (Default mapping: \\s[)\r\n\r\n        Pulls changes from specified repository.\r\n\r\n                Used SCM commands ~\r\n                hg  : pull\r\n                git : pull\r\n                bzr : pull\r\n\r\n                                                                 *:MinSCMPush*\r\n:MinSCMPush[!]                  (Default mapping: \\s])\r\n\r\n        Pushes changes to specified repository.\r\n\r\n                Used SCM commands ~\r\n                hg  : push\r\n                git : push\r\n                bzr : push\r\n\r\n                                                             *:MinSCMDiffFile*\r\n:MinSCMDiffFile[!]              (Default mapping: \\sD)\r\n\r\n        Starts diff mode (like vimdiff) in new tabpage between a file of a\r\n        current buffer and its version of specified revision.\r\n\r\n                Used SCM commands ~\r\n                hg  : cat\r\n                git : cat-file -p\r\n                bzr : cat\r\n\r\n                                                              *:MinSCMDiffAll*\r\n:MinSCMDiffAll[!]               (Default mapping: \\sd)\r\n\r\n        Shows differences between all files in a working directory of a\r\n        current repository and specified revision.\r\n\r\n                Used SCM commands ~\r\n                hg  : diff\r\n                git : diff\r\n                bzr : diff\r\n\r\n                                                              *:MinSCMLogFile*\r\n:MinSCMLogFile[!]               (Default mapping: \\sL)\r\n\r\n        Shows revision history related to a file of a current buffer. (see\r\n        also: |g:minscm_hgLogOption| |g:minscm_gitLogOption|\r\n        |g:minscm_bzrLogOption|)\r\n\r\n                Used SCM commands ~\r\n                hg  : glog\r\n                git : log\r\n                bzr : log\r\n\r\n                                                               *:MinSCMLogAll*\r\n:MinSCMLogAll[!]                (Default mapping: \\sl)\r\n\r\n        Shows revision history. (see also: |g:minscm_hgLogOption|\r\n        |g:minscm_gitLogOption| |g:minscm_bzrLogOption|)\r\n\r\n                Used SCM commands ~\r\n                hg  : glog\r\n                git : log\r\n                bzr : log\r\n\r\n                                                         *:MinSCMAnnotateFile*\r\n:MinSCMAnnotateFile[!]          (Default mapping: \\sn)\r\n\r\n        Shows commit information per file line.\r\n\r\n        Lines which were modified at the commit of specified revision or added\r\n        at the initial commit are highlighted.\r\n\r\n                Used SCM commands ~\r\n                hg  : annotate -nudq\r\n                git : blame\r\n                bzr : annotate --all --long\r\n\r\n                                                               *:MinSCMStatus*\r\n:MinSCMStatus[!]                (Default mapping: \\ss)\r\n\r\n        Shows a list of changed files.\r\n\r\n                Used SCM commands ~\r\n                hg  : status\r\n                git : diff --name-status && ls-files --exclude-standard -o\r\n                bzr : status\r\n\r\n                                                                 *:MinSCMGrep*\r\n:MinSCMGrep[!]                  (Default mapping: \\sg)\r\n\r\n        Searches for specified pattern and creates a |quickfix| list.\r\n\r\n                Used SCM commands ~\r\n                hg  : grep -n\r\n                git : grep -n -e\r\n                bzr : (unavailable)\r\n\r\n                                                         *:MinSCMLoadModified*\r\n:MinSCMLoadModified[!]          (Default mapping: \\s!)\r\n\r\n        Loads all modified files with vim after unloading (by :bdelete)\r\n        buffers which are not modified files.\r\n\r\n                Used SCM commands ~\r\n                hg  : status -mn\r\n                git : ls-files -m\r\n                bzr : status -SV\r\n\r\n                                                              *:MinSCMLoadAll*\r\n:MinSCMLoadAll[!]               (Default mapping: \\s<CR>)\r\n\r\n        Loads all tracked files with vim after unloading (by :bdelete) buffers\r\n        which are not tracked files.\r\n\r\n                Used SCM commands ~\r\n                hg  : locate -f\r\n                git : ls-files\r\n                bzr : ls\r\n\r\n                                                             *:MinSCMFindFile*\r\n:MinSCMFindFile[!]              (Default mapping: \\sf)\r\n\r\n        Opens a selected file from all tracked files using Fuzzyfinder. \r\n        (see also: |minscm-fuzzyfinder|)\r\n\r\n                Used SCM commands ~\r\n                hg  : locate -f\r\n                git : ls-files\r\n                bzr : ls\r\n\r\n==============================================================================\r\n","install_details":"","5":"","first_name":"Takeshi","6":"Takeshi","last_name":"NISHIDA","7":"NISHIDA","releases":[{"0":"2637","vim_version":"7.0","1":"7.0","script_version":"0.7.2","2":"0.7.2","version_comment":"- Fixed to correspond to API of Fuzzyfinder version 3.2.","3":"- Fixed to correspond to API of Fuzzyfinder version 3.2.","package":"vim-minscm.zip","4":"vim-minscm.zip","src_id":"11367","5":"11367","creation_date":"1252835951","6":"1252835951"},{"0":"2637","vim_version":"7.0","1":"7.0","script_version":"0.7.1","2":"0.7.1","version_comment":"- Fixed to correspond to API of Fuzzyfinder version 3.0.","3":"- Fixed to correspond to API of Fuzzyfinder version 3.0.","package":"vim-minscm.zip","4":"vim-minscm.zip","src_id":"11321","5":"11321","creation_date":"1252069311","6":"1252069311"},{"0":"2637","vim_version":"7.0","1":"7.0","script_version":"0.6.0","2":"0.6.0","version_comment":"- Added MinSCMLogFile command.\r\n- Added MinSCMLoadPull command.\r\n- Added MinSCMLoadPush command.\r\n- Added g:minscm_hgLocations option.\r\n- Added g:minscm_gitLocations option.\r\n- Added g:minscm_bzrLocations option.\r\n- Added g:minscm_hgPullIsFetch option.\r\n- Renamed MinSCMLog command to MinSCMLogAll.\r\n- Changed MinSCMCommand command to use :! command instead of system()\r\n  function.\r\n","3":"- Added MinSCMLogFile command.\r\n- Added MinSCMLoadPull command.\r\n- Added MinSCMLoadPush command.\r\n- Added g:minscm_hgLocations option.\r\n- Added g:minscm_gitLocations option.\r\n- Added g:minscm_bzrLocations option.\r\n- Added g:minscm_hgPullIsFetch option.\r\n- Renamed MinSCMLog command to MinSCMLogAll.\r\n- Changed MinSCMCommand command to use :! command instead of system()\r\n  function.\r\n","package":"vim-minscm.zip","4":"vim-minscm.zip","src_id":"10836","5":"10836","creation_date":"1245081391","6":"1245081391"},{"0":"2637","vim_version":"7.0","1":"7.0","script_version":"0.5.0","2":"0.5.0","version_comment":"- Added MinSCMLoadModified command.\r\n- Improved MinSCMAnnotateFile command to highlight lines which were modified\r\n  at the commit of specified revision or added at the initial commit.\r\n- Changed default values of g:minscm_hgLogOption, g:minscm_gitLogOption, and\r\n  g:minscm_bzrLogOption to limit a number of revisions to show.\r\n","3":"- Added MinSCMLoadModified command.\r\n- Improved MinSCMAnnotateFile command to highlight lines which were modified\r\n  at the commit of specified revision or added at the initial commit.\r\n- Changed default values of g:minscm_hgLogOption, g:minscm_gitLogOption, and\r\n  g:minscm_bzrLogOption to limit a number of revisions to show.\r\n","package":"vim-minscm.zip","4":"vim-minscm.zip","src_id":"10815","5":"10815","creation_date":"1244899894","6":"1244899894"},{"0":"2637","vim_version":"7.0","1":"7.0","script_version":"0.4.0","2":"0.4.0","version_comment":"- Added MinSCMAnnotateFile command.\r\n- Added g:minscm_mapKeyCommand, g:minscm_mapKeyCommitFile,\r\n  g:minscm_mapKeyCommitTracked, g:minscm_mapKeyCommitAll,\r\n  g:minscm_mapKeyCheckout, g:minscm_mapKeyMerge, g:minscm_mapKeyBranch,\r\n  g:minscm_mapKeyBranchDelete, g:minscm_mapKeyRebase,\r\n  g:minscm_mapKeyDiffFile, g:minscm_mapKeyDiffAll, g:minscm_mapKeyLog,\r\n  g:minscm_mapKeyAnnotateFile, g:minscm_mapKeyStatus, g:minscm_mapKeyGrep,\r\n  g:minscm_mapKeyLoadAll, and g:minscm_mapKeyFindFile options.\r\n","3":"- Added MinSCMAnnotateFile command.\r\n- Added g:minscm_mapKeyCommand, g:minscm_mapKeyCommitFile,\r\n  g:minscm_mapKeyCommitTracked, g:minscm_mapKeyCommitAll,\r\n  g:minscm_mapKeyCheckout, g:minscm_mapKeyMerge, g:minscm_mapKeyBranch,\r\n  g:minscm_mapKeyBranchDelete, g:minscm_mapKeyRebase,\r\n  g:minscm_mapKeyDiffFile, g:minscm_mapKeyDiffAll, g:minscm_mapKeyLog,\r\n  g:minscm_mapKeyAnnotateFile, g:minscm_mapKeyStatus, g:minscm_mapKeyGrep,\r\n  g:minscm_mapKeyLoadAll, and g:minscm_mapKeyFindFile options.\r\n","package":"vim-minscm.zip","4":"vim-minscm.zip","src_id":"10804","5":"10804","creation_date":"1244735701","6":"1244735701"},{"0":"2637","vim_version":"7.0","1":"7.0","script_version":"0.3.0","2":"0.3.0","version_comment":"- Added g:minscm_hgLogOption, g:minscm_gitLogOption, and\r\n  g:minscm_bzrLogOption options.\r\n- Improved MinSCMGrep command and now it creates a quickfix list.\r\n- Changed default log style for Mercurial repositories.\r\n- Fixed a bug that MinSCMLog command for Mercurial repositories could not\r\n  show graph log in some environments (thanks to mii for the patch).\r\n- Fixed a bug that MinSCMCommitFile, MinSCMCommitTracked, and\r\n  MinSCMCommitAll commands for repositories which had not been committed\r\n  didn't work.\r\n","3":"- Added g:minscm_hgLogOption, g:minscm_gitLogOption, and\r\n  g:minscm_bzrLogOption options.\r\n- Improved MinSCMGrep command and now it creates a quickfix list.\r\n- Changed default log style for Mercurial repositories.\r\n- Fixed a bug that MinSCMLog command for Mercurial repositories could not\r\n  show graph log in some environments (thanks to mii for the patch).\r\n- Fixed a bug that MinSCMCommitFile, MinSCMCommitTracked, and\r\n  MinSCMCommitAll commands for repositories which had not been committed\r\n  didn't work.\r\n","package":"vim-minscm.zip","4":"vim-minscm.zip","src_id":"10796","5":"10796","creation_date":"1244636408","6":"1244636408"},{"0":"2637","vim_version":"7.0","1":"7.0","script_version":"0.2.1","2":"0.2.1","version_comment":"- Fixed a bug that the log command for Mercurial repositories didn't work on\r\n  Windows.\r\n","3":"- Fixed a bug that the log command for Mercurial repositories didn't work on\r\n  Windows.\r\n","package":"vim-minscm.zip","4":"vim-minscm.zip","src_id":"10790","5":"10790","creation_date":"1244558076","6":"1244558076"},{"0":"2637","vim_version":"7.0","1":"7.0","script_version":"0.2.0","2":"0.2.0","version_comment":"- Changed not to show modified files number on a status line.\r\n- Changed highlight of a commit buffer.\r\n- Added MinSCMFindFile command.\r\n- Added Japanese help (doc\/minscm.jax).\r\n","3":"- Changed not to show modified files number on a status line.\r\n- Changed highlight of a commit buffer.\r\n- Added MinSCMFindFile command.\r\n- Added Japanese help (doc\/minscm.jax).\r\n","package":"vim-minscm.zip","4":"vim-minscm.zip","src_id":"10745","5":"10745","creation_date":"1244210145","6":"1244210145"},{"0":"2637","vim_version":"7.2","1":"7.2","script_version":"0.1.0","2":"0.1.0","version_comment":"Initial upload","3":"Initial upload","package":"vim-minscm.zip","4":"vim-minscm.zip","src_id":"10622","5":"10622","creation_date":"1242585645","6":"1242585645"}]},"2636":{"script_id":"2636","0":"2636","script_name":"google.vim","1":"google.vim","script_type":"indent","2":"indent","summary":"Indent file for Google C++ Coding Style","3":"Indent file for Google C++ Coding Style","description":"!!!Deprecated!!!\r\nIndenting of C++ namespaces added in 7.3.202.\r\n\r\nInspired by Google C++ Coding Style (http:\/\/google-styleguide.googlecode.com\/svn\/trunk\/cppguide.xml)","4":"!!!Deprecated!!!\r\nIndenting of C++ namespaces added in 7.3.202.\r\n\r\nInspired by Google C++ Coding Style (http:\/\/google-styleguide.googlecode.com\/svn\/trunk\/cppguide.xml)","install_details":"Move google.vim to ~\/.vim\/indent as cpp.vim\r\n\r\nIf you use csindent plug-in (vimscript #2633), then move google.vim to ~\/.vim\/csindent\/cpp\/","5":"Move google.vim to ~\/.vim\/indent as cpp.vim\r\n\r\nIf you use csindent plug-in (vimscript #2633), then move google.vim to ~\/.vim\/csindent\/cpp\/","first_name":"Konstantin","6":"Konstantin","last_name":"Lepa","7":"Lepa","releases":[{"0":"2636","vim_version":"7.0","1":"7.0","script_version":"1.1.0","2":"1.1.0","version_comment":"Refactored source code.\r\nSome fixes.","3":"Refactored source code.\r\nSome fixes.","package":"google.vim","4":"google.vim","src_id":"14772","5":"14772","creation_date":"1295271771","6":"1295271771"},{"0":"2636","vim_version":"7.0","1":"7.0","script_version":"1.0.1","2":"1.0.1","version_comment":" Added some changes. Thanks to Eric Rannaud <eric.rannaud@gmail.com>","3":" Added some changes. Thanks to Eric Rannaud <eric.rannaud@gmail.com>","package":"cpp.vim","4":"cpp.vim","src_id":"13033","5":"13033","creation_date":"1274363735","6":"1274363735"},{"0":"2636","vim_version":"7.0","1":"7.0","script_version":"1.0.0","2":"1.0.0","version_comment":"Initial upload","3":"Initial upload","package":"cpp.vim","4":"cpp.vim","src_id":"10618","5":"10618","creation_date":"1242560563","6":"1242560563"}]},"2635":{"script_id":"2635","0":"2635","script_name":"smartmatcheol.vim","1":"smartmatcheol.vim","script_type":"utility","2":"utility","summary":"Smart matching of trailing whitespace","3":"Smart matching of trailing whitespace","description":"If you don't want to highlight trailing whitespaces in all filetypes, then you can use the plug-in.\r\n\r\nNB: If you are using `textwidth' option, then plug-in will highlight all characters after `textwidth' length.\r\n\r\n","4":"If you don't want to highlight trailing whitespaces in all filetypes, then you can use the plug-in.\r\n\r\nNB: If you are using `textwidth' option, then plug-in will highlight all characters after `textwidth' length.\r\n\r\n","install_details":"1. Move smartmatcheol.vim into ~\/.vim\/plugin\/\r\n2. Define g:sme_extlist and g:sme_filelist in ~\/.vimrc for highlighting. For example:\r\nlet g:sme_extlist = [ \"c\", \"h\", \"py\", \"cc\", \"cpp\", \"hpp\", \"xml\", \"xslt\", \"vim\"]\r\nlet g:sme_filelist = [ \"CMakeLists.txt\", \"vimrc\" ]","5":"1. Move smartmatcheol.vim into ~\/.vim\/plugin\/\r\n2. Define g:sme_extlist and g:sme_filelist in ~\/.vimrc for highlighting. For example:\r\nlet g:sme_extlist = [ \"c\", \"h\", \"py\", \"cc\", \"cpp\", \"hpp\", \"xml\", \"xslt\", \"vim\"]\r\nlet g:sme_filelist = [ \"CMakeLists.txt\", \"vimrc\" ]","first_name":"Konstantin","6":"Konstantin","last_name":"Lepa","7":"Lepa","releases":[{"0":"2635","vim_version":"7.0","1":"7.0","script_version":"1.0.1","2":"1.0.1","version_comment":"Fixed bug in parsing g:sme_filelist.","3":"Fixed bug in parsing g:sme_filelist.","package":"smartmatcheol.vim","4":"smartmatcheol.vim","src_id":"10615","5":"10615","creation_date":"1242505023","6":"1242505023"},{"0":"2635","vim_version":"7.0","1":"7.0","script_version":"1.0.0","2":"1.0.0","version_comment":"Initial upload","3":"Initial upload","package":"smartmatcheol.vim","4":"smartmatcheol.vim","src_id":"10610","5":"10610","creation_date":"1242473225","6":"1242473225"}]},"2634":{"script_id":"2634","0":"2634","script_name":"SearchPosition","1":"SearchPosition","script_type":"utility","2":"utility","summary":"Show relation to search pattern matches in range or buffer. ","3":"Show relation to search pattern matches in range or buffer. ","description":"DESCRIPTION\r\nThe mappings, command and operator provided by this plugin search a range or\r\nthe entire buffer for a pattern (defaulting to the last search pattern),\r\nand print a summary of the number of occurrences above, below and on the\r\ncurrent line, e.g.:\r\n    1 match after cursor in this line, 8 following, 2 in previous lines;\r\n        total 10 within 11,42 for \/\\<SearchPosition\\>\/\r\n\r\n    5 matches in this fold, 9 before, 6 following; total 21 spanning the\r\n    entire buffer for \/endif\/\r\n\r\n    On sole match in this line, 40 in following lines within 24,171 for \/let\/\r\n\r\n    :144,172 7 matches in this fold for \/let\/\r\n\r\nThis provides better orientation in a buffer without having to first jump from\r\nsearch result to search result.\r\n\r\nMOTIVATION\r\nIn its simplest implementation\r\n    :nnoremap <A-n> :%s\/\/\/gn<CR>\r\n   41 matches on 17 lines\r\nprints the number of matches for the last search pattern. This plugin\r\nbuilds on top of this by providing more context with regards to the current\r\ncursor position plus additional information.\r\n\r\nThis plugin is similar to IndexedSearch.vim (vimscript #1682) by Yakov Lerner.\r\n\r\nUSAGE\r\n:[range]SearchPosition [\/][{pattern}][\/]\r\n                        Show position of the search results for {pattern} (or\r\n                        the last search pattern (quote\/) if {pattern} is\r\n                        omitted). Without [\/], only literal whole words are\r\n                        matched. :search-args\r\n                        All lines in [range] (or the entire buffer\r\n                        if omitted) are considered, and the number of matches\r\n                        in relation to the current cursor position is echoed\r\n                        to the command line.\r\n\r\n:[range]SearchPositionMultiple \/{pattern1}\/,\/{pattern2}\/[,...]\r\n:[range]SearchPositionMultiple {word1},{word2}[,...]\r\n                        Show positions and tallies of the search results for\r\n                        {pattern1}, {pattern2}, ... Without [\/] delimiters,\r\n                        only literal whole {word1}, {word2}, ... are matched.\r\n                        :search-args Useful to compare the number of\r\n                        occurrences for multiple variants.\r\n\r\n:[range]WinSearchPosition[!] [\/][{pattern}][\/]\r\n                        Show number and distribution of the search results\r\n                        in all buffers shown in the current tab page. With\r\n                        [!], shows a verbose report with match statistics\r\n                        about every covered buffer, not just a summary.\r\n                        If [range] is given only in windows for which the\r\n                        window number lies in the [range].\r\n\r\n:[range]TabSearchPosition[!] [\/][{pattern}][\/]\r\n                        Show number and distribution of the search results\r\n                        in all buffers shown in all tab pages. With [!], shows\r\n                        a verbose report with match statistics about every\r\n                        covered buffer, not just a summary. If [range] is\r\n                        given only in tab pages for which the tab page number\r\n                        lies in the [range].\r\n\r\n:[range]ArgSearchPosition[!] [\/][{pattern}][\/]\r\n                        Show number and distribution of the search results\r\n                        in all buffers in the argument-list. With [!], shows\r\n                        a verbose report with match statistics about every\r\n                        covered buffer, not just a summary. If [range] is\r\n                        given only covers those arguments.\r\n\r\n:[range]BufSearchPosition[!] [\/][{pattern}][\/]\r\n                        Show number and distribution of the search results\r\n                        in all listed buffers. With [!], shows a verbose\r\n                        report with match statistics about every covered\r\n                        buffer, not just a summary. If [range] is given only\r\n                        covers those buffers.\r\n\r\n<Leader>ALT-n{motion}   Show position for the last search pattern in the\r\n                        lines covered by {motion}.\r\n[count]ALT-n            Show position for the last search pattern in the\r\n                        entire buffer, or [count] following lines.\r\n{Visual}ALT-n           Show position for the last search pattern in the\r\n                        selected lines.\r\n\r\n                        The default mapping ALT-n was chosen because one often\r\n                        invokes this when jumping to matches via n\/N, so ALT-n\r\n                        is easy to reach. Imagine 'n' stood for \"next\r\n                        searches\".\r\n\r\n[count]ALT-m            Show position for the whole word under the cursor in\r\n                        the entire buffer, or [count] following lines.\r\n                        Only whole keywords are searched for, like with the\r\n                        star command.\r\n[count]g_ALT-m          Show position for the word under the cursor in the\r\n                        entire buffer, or [count] following lines.\r\n                        Also finds contained matches, like gstar.\r\n                        When repeated at the same position, switches to\r\n                        verbose reporting, like g_ALT-N.\r\n\r\n{Visual}ALT-m           Show position for the selected text in the entire\r\n                        buffer.\r\n\r\n                        Imagine 'm' stood for \"more occurrences\".\r\n                        These mappings reuse the last used <cword> when issued\r\n                        on a blank line.\r\n\r\n[count],_ALT-m          Show position for the whole (i.e. delimited by\r\n                        whitespace) WORD under the cursor in the entire\r\n                        buffer, or [count] following lines.\r\n[count]g,_ALT-m         Show position for the WORD under the cursor in the\r\n                        entire buffer, or [count] following lines.\r\n                        Also finds contained matches, like gstar.\r\n                        When repeated at the same position, switches to\r\n                        verbose reporting, like g_ALT-N.\r\n\r\n                        These mappings reuse the last used <cWORD> when issued\r\n                        on a blank line.\r\n\r\n                        Repeats of any of the mappings at the same position\r\n                        will extend the reporting to other (i.e. excluding the\r\n                        current one)\r\n                        - windows (:WinSearchPosition)\r\n                        - tab pages (:TabSearchPosition)\r\n                        - arguments (:ArgSearchPosition)\r\n                        - loaded buffers (:BufSearchPosition)\r\n                        skipping those sources that do not exist.\r\n\r\ng_ALT-n                 A repeat with a \"g\" prefix at the same position will\r\ng_ALT-m                 show a verbose report that shows match statistics\r\ng_,ALT-m                about every covered buffer, not just a summary.\r\n                        g_ALT-n can also be used anywhere to start a verbose\r\n                        report for all windows; g_ALT-m \/ g,_ALT-m cannot,\r\n                        because they are overloaded with showing the position\r\n                        of the word \/ WORD under the cursor.","4":"DESCRIPTION\r\nThe mappings, command and operator provided by this plugin search a range or\r\nthe entire buffer for a pattern (defaulting to the last search pattern),\r\nand print a summary of the number of occurrences above, below and on the\r\ncurrent line, e.g.:\r\n    1 match after cursor in this line, 8 following, 2 in previous lines;\r\n        total 10 within 11,42 for \/\\<SearchPosition\\>\/\r\n\r\n    5 matches in this fold, 9 before, 6 following; total 21 spanning the\r\n    entire buffer for \/endif\/\r\n\r\n    On sole match in this line, 40 in following lines within 24,171 for \/let\/\r\n\r\n    :144,172 7 matches in this fold for \/let\/\r\n\r\nThis provides better orientation in a buffer without having to first jump from\r\nsearch result to search result.\r\n\r\nMOTIVATION\r\nIn its simplest implementation\r\n    :nnoremap <A-n> :%s\/\/\/gn<CR>\r\n   41 matches on 17 lines\r\nprints the number of matches for the last search pattern. This plugin\r\nbuilds on top of this by providing more context with regards to the current\r\ncursor position plus additional information.\r\n\r\nThis plugin is similar to IndexedSearch.vim (vimscript #1682) by Yakov Lerner.\r\n\r\nUSAGE\r\n:[range]SearchPosition [\/][{pattern}][\/]\r\n                        Show position of the search results for {pattern} (or\r\n                        the last search pattern (quote\/) if {pattern} is\r\n                        omitted). Without [\/], only literal whole words are\r\n                        matched. :search-args\r\n                        All lines in [range] (or the entire buffer\r\n                        if omitted) are considered, and the number of matches\r\n                        in relation to the current cursor position is echoed\r\n                        to the command line.\r\n\r\n:[range]SearchPositionMultiple \/{pattern1}\/,\/{pattern2}\/[,...]\r\n:[range]SearchPositionMultiple {word1},{word2}[,...]\r\n                        Show positions and tallies of the search results for\r\n                        {pattern1}, {pattern2}, ... Without [\/] delimiters,\r\n                        only literal whole {word1}, {word2}, ... are matched.\r\n                        :search-args Useful to compare the number of\r\n                        occurrences for multiple variants.\r\n\r\n:[range]WinSearchPosition[!] [\/][{pattern}][\/]\r\n                        Show number and distribution of the search results\r\n                        in all buffers shown in the current tab page. With\r\n                        [!], shows a verbose report with match statistics\r\n                        about every covered buffer, not just a summary.\r\n                        If [range] is given only in windows for which the\r\n                        window number lies in the [range].\r\n\r\n:[range]TabSearchPosition[!] [\/][{pattern}][\/]\r\n                        Show number and distribution of the search results\r\n                        in all buffers shown in all tab pages. With [!], shows\r\n                        a verbose report with match statistics about every\r\n                        covered buffer, not just a summary. If [range] is\r\n                        given only in tab pages for which the tab page number\r\n                        lies in the [range].\r\n\r\n:[range]ArgSearchPosition[!] [\/][{pattern}][\/]\r\n                        Show number and distribution of the search results\r\n                        in all buffers in the argument-list. With [!], shows\r\n                        a verbose report with match statistics about every\r\n                        covered buffer, not just a summary. If [range] is\r\n                        given only covers those arguments.\r\n\r\n:[range]BufSearchPosition[!] [\/][{pattern}][\/]\r\n                        Show number and distribution of the search results\r\n                        in all listed buffers. With [!], shows a verbose\r\n                        report with match statistics about every covered\r\n                        buffer, not just a summary. If [range] is given only\r\n                        covers those buffers.\r\n\r\n<Leader>ALT-n{motion}   Show position for the last search pattern in the\r\n                        lines covered by {motion}.\r\n[count]ALT-n            Show position for the last search pattern in the\r\n                        entire buffer, or [count] following lines.\r\n{Visual}ALT-n           Show position for the last search pattern in the\r\n                        selected lines.\r\n\r\n                        The default mapping ALT-n was chosen because one often\r\n                        invokes this when jumping to matches via n\/N, so ALT-n\r\n                        is easy to reach. Imagine 'n' stood for \"next\r\n                        searches\".\r\n\r\n[count]ALT-m            Show position for the whole word under the cursor in\r\n                        the entire buffer, or [count] following lines.\r\n                        Only whole keywords are searched for, like with the\r\n                        star command.\r\n[count]g_ALT-m          Show position for the word under the cursor in the\r\n                        entire buffer, or [count] following lines.\r\n                        Also finds contained matches, like gstar.\r\n                        When repeated at the same position, switches to\r\n                        verbose reporting, like g_ALT-N.\r\n\r\n{Visual}ALT-m           Show position for the selected text in the entire\r\n                        buffer.\r\n\r\n                        Imagine 'm' stood for \"more occurrences\".\r\n                        These mappings reuse the last used <cword> when issued\r\n                        on a blank line.\r\n\r\n[count],_ALT-m          Show position for the whole (i.e. delimited by\r\n                        whitespace) WORD under the cursor in the entire\r\n                        buffer, or [count] following lines.\r\n[count]g,_ALT-m         Show position for the WORD under the cursor in the\r\n                        entire buffer, or [count] following lines.\r\n                        Also finds contained matches, like gstar.\r\n                        When repeated at the same position, switches to\r\n                        verbose reporting, like g_ALT-N.\r\n\r\n                        These mappings reuse the last used <cWORD> when issued\r\n                        on a blank line.\r\n\r\n                        Repeats of any of the mappings at the same position\r\n                        will extend the reporting to other (i.e. excluding the\r\n                        current one)\r\n                        - windows (:WinSearchPosition)\r\n                        - tab pages (:TabSearchPosition)\r\n                        - arguments (:ArgSearchPosition)\r\n                        - loaded buffers (:BufSearchPosition)\r\n                        skipping those sources that do not exist.\r\n\r\ng_ALT-n                 A repeat with a \"g\" prefix at the same position will\r\ng_ALT-m                 show a verbose report that shows match statistics\r\ng_,ALT-m                about every covered buffer, not just a summary.\r\n                        g_ALT-n can also be used anywhere to start a verbose\r\n                        report for all windows; g_ALT-m \/ g,_ALT-m cannot,\r\n                        because they are overloaded with showing the position\r\n                        of the word \/ WORD under the cursor.","install_details":"INSTALLATION\r\nThe code is hosted in a Git repo at\r\n    https:\/\/github.com\/inkarkat\/vim-SearchPosition\r\nYou can use your favorite plugin manager, or \"git clone\" into a directory used\r\nfor Vim packages. Releases are on the \"stable\" branch, the latest unstable\r\ndevelopment snapshot on \"master\".\r\n\r\nThis script is also packaged as a vimball. If you have the \"gunzip\"\r\ndecompressor in your PATH, simply edit the *.vmb.gz package in Vim; otherwise,\r\ndecompress the archive first, e.g. using WinZip. Inside Vim, install by\r\nsourcing the vimball or via the :UseVimball command.\r\n    vim SearchPosition*.vmb.gz\r\n    :so %\r\nTo uninstall, use the :RmVimball command.\r\n\r\nDEPENDENCIES\r\n- Requires Vim 7.0 or higher.\r\n- Requires the ingo-library.vim plugin (vimscript #4433), version 1.036 or\r\n  higher.\r\n\r\nCONFIGURATION\r\nFor a permanent configuration, put the following commands into your vimrc:\r\n\r\nThe highlight group for the report message can be set via\r\n    let g:SearchPosition_HighlightGroup = 'ModeMsg'\r\n\r\nTo shorten the report message, the [range] and used search pattern can be\r\nomitted from the message; by default, both are included in the message text:\r\n    let g:SearchPosition_ShowRange = 1\r\n    let g:SearchPosition_ShowPattern = 1\r\n\r\nThe report also shows in which range the matches fall. To turn this off:\r\n    let g:SearchPosition_ShowMatchRange = 1\r\n\r\nIf the range falls entirely into the lines that are shown in the current\r\nwindow, a relative range is used. To prefer a fixed threshold, or to turn this\r\noff, use:\r\n    let g:SearchPosition_MatchRangeShowRelativeThreshold = 10\r\nThe relative threshold at the end is determined via:\r\n    let g:SearchPosition_MatchRangeShowRelativeEndThreshold = 10\r\n\r\nIf you want to use different mappings, map your keys to the\r\n<Plug>SearchPosition* mapping targets _before_ sourcing the script (e.g. in\r\nyour vimrc):\r\n    nmap <Leader>,n <Plug>SearchPositionOperator\r\n    nmap <Leader>n <Plug>SearchPositionCurrent\r\n    vmap <Leader>n <Plug>SearchPositionCurrent\r\n    nmap <Leader>m <Plug>SearchPositionWholeCword\r\n    vmap <Leader>m <Plug>SearchPositionCword\r\n    nmap <Leader>M <Plug>SearchPositionCword\r\n    nmap <Leader>w <Plug>SearchPositionWholeCWORD\r\n    nmap <Leader>W <Plug>SearchPositionCWORD","5":"INSTALLATION\r\nThe code is hosted in a Git repo at\r\n    https:\/\/github.com\/inkarkat\/vim-SearchPosition\r\nYou can use your favorite plugin manager, or \"git clone\" into a directory used\r\nfor Vim packages. Releases are on the \"stable\" branch, the latest unstable\r\ndevelopment snapshot on \"master\".\r\n\r\nThis script is also packaged as a vimball. If you have the \"gunzip\"\r\ndecompressor in your PATH, simply edit the *.vmb.gz package in Vim; otherwise,\r\ndecompress the archive first, e.g. using WinZip. Inside Vim, install by\r\nsourcing the vimball or via the :UseVimball command.\r\n    vim SearchPosition*.vmb.gz\r\n    :so %\r\nTo uninstall, use the :RmVimball command.\r\n\r\nDEPENDENCIES\r\n- Requires Vim 7.0 or higher.\r\n- Requires the ingo-library.vim plugin (vimscript #4433), version 1.036 or\r\n  higher.\r\n\r\nCONFIGURATION\r\nFor a permanent configuration, put the following commands into your vimrc:\r\n\r\nThe highlight group for the report message can be set via\r\n    let g:SearchPosition_HighlightGroup = 'ModeMsg'\r\n\r\nTo shorten the report message, the [range] and used search pattern can be\r\nomitted from the message; by default, both are included in the message text:\r\n    let g:SearchPosition_ShowRange = 1\r\n    let g:SearchPosition_ShowPattern = 1\r\n\r\nThe report also shows in which range the matches fall. To turn this off:\r\n    let g:SearchPosition_ShowMatchRange = 1\r\n\r\nIf the range falls entirely into the lines that are shown in the current\r\nwindow, a relative range is used. To prefer a fixed threshold, or to turn this\r\noff, use:\r\n    let g:SearchPosition_MatchRangeShowRelativeThreshold = 10\r\nThe relative threshold at the end is determined via:\r\n    let g:SearchPosition_MatchRangeShowRelativeEndThreshold = 10\r\n\r\nIf you want to use different mappings, map your keys to the\r\n<Plug>SearchPosition* mapping targets _before_ sourcing the script (e.g. in\r\nyour vimrc):\r\n    nmap <Leader>,n <Plug>SearchPositionOperator\r\n    nmap <Leader>n <Plug>SearchPositionCurrent\r\n    vmap <Leader>n <Plug>SearchPositionCurrent\r\n    nmap <Leader>m <Plug>SearchPositionWholeCword\r\n    vmap <Leader>m <Plug>SearchPositionCword\r\n    nmap <Leader>M <Plug>SearchPositionCword\r\n    nmap <Leader>w <Plug>SearchPositionWholeCWORD\r\n    nmap <Leader>W <Plug>SearchPositionCWORD","first_name":"Ingo","6":"Ingo","last_name":"Karkat","7":"Karkat","releases":[{"0":"2634","vim_version":"7.0","1":"7.0","script_version":"2.00","2":"2.00","version_comment":"- ENH: Add widening of search scope on mapping repeat at the same position, and verbose search result reporting.\r\n- Add :WinSearchPosition, :TabSearchPosition, :ArgSearchPosition, :BufSearchPosition commands.\r\n- BUG: {Visual}<A-m> uses selected text as pattern, not as literal text. Add escaping.\r\n- ENH: Add [g],<A-m> variants of [g]<A-m> that use (whole) WORD instead of word. *** You need to update to ingo-library (vimscript #4433) version 1.036! ***","3":"- ENH: Add widening of search scope on mapping repeat at the same position, and verbose search result reporting.\r\n- Add :WinSearchPosition, :TabSearchPosition, :ArgSearchPosition, :BufSearchPosition commands.\r\n- BUG: {Visual}<A-m> uses selected text as pattern, not as literal text. Add escaping.\r\n- ENH: Add [g],<A-m> variants of [g]<A-m> that use (whole) WORD instead of word. *** You need to update to ingo-library (vimscript #4433) version 1.036! ***","package":"SearchPosition-2.00.vmb.gz","4":"SearchPosition-2.00.vmb.gz","src_id":"27099","5":"27099","creation_date":"1585970254","6":"1585970254"},{"0":"2634","vim_version":"7.0","1":"7.0","script_version":"1.30","2":"1.30","version_comment":"- BUG: Also need to account for cursor within closed fold for the start line number, not just the end.\r\n- Also submit the plugin's result message (in unhighlighted form) to the message history (for recall and comparison).\r\n- Add :SearchPositionMultiple command.\r\n- Tweak s:TranslateLocation() for line 1:  :2 looks better than :.+1 there.\r\n- Tweak s:TranslateLocation() for last line and use :$-N instead of :.-N there.\r\n- BUG: Incorrect de-pluralization of \"11 match[es]\". *** You need to update to ingo-library (vimscript #4433) version 1.022! ***","3":"- BUG: Also need to account for cursor within closed fold for the start line number, not just the end.\r\n- Also submit the plugin's result message (in unhighlighted form) to the message history (for recall and comparison).\r\n- Add :SearchPositionMultiple command.\r\n- Tweak s:TranslateLocation() for line 1:  :2 looks better than :.+1 there.\r\n- Tweak s:TranslateLocation() for last line and use :$-N instead of :.-N there.\r\n- BUG: Incorrect de-pluralization of \"11 match[es]\". *** You need to update to ingo-library (vimscript #4433) version 1.022! ***","package":"SearchPosition-1.30.vmb.gz","4":"SearchPosition-1.30.vmb.gz","src_id":"23216","5":"23216","creation_date":"1429789395","6":"1429789395"},{"0":"2634","vim_version":"7.0","1":"7.0","script_version":"1.21","2":"1.21","version_comment":"- ENH: Show relative range when the lines are shown in the current window with a new default configuration value of \"visible\" for g:SearchPosition_MatchRangeShowRelativeThreshold. Use separate g:SearchPosition_MatchRangeShowRelativeEndThreshold for threshold at the end.\r\n- FIX: After \"Special atoms have distorted the tally\" warning, an additional stray (last actual) error is repeated. s:Report() also needs to return 1 after such warning.\r\n- BUG: \"Special atoms have distorted the tally\" warning instead of \"No matches\" when on first line. Must not allow previous matching line when that is identical to 0, the return value of search() when it fails.\r\n- BUG: \"Special atoms have distorted the tally\" when doing :SearchPosition\/\\n\\n\/ on empty line. The special case for \\n matching is actually more complex; need to also ensure that the match doesn't lie completely on the previous line, and retry without the \"c\" search flag if it does.","3":"- ENH: Show relative range when the lines are shown in the current window with a new default configuration value of \"visible\" for g:SearchPosition_MatchRangeShowRelativeThreshold. Use separate g:SearchPosition_MatchRangeShowRelativeEndThreshold for threshold at the end.\r\n- FIX: After \"Special atoms have distorted the tally\" warning, an additional stray (last actual) error is repeated. s:Report() also needs to return 1 after such warning.\r\n- BUG: \"Special atoms have distorted the tally\" warning instead of \"No matches\" when on first line. Must not allow previous matching line when that is identical to 0, the return value of search() when it fails.\r\n- BUG: \"Special atoms have distorted the tally\" when doing :SearchPosition\/\\n\\n\/ on empty line. The special case for \\n matching is actually more complex; need to also ensure that the match doesn't lie completely on the previous line, and retry without the \"c\" search flag if it does.","package":"SearchPosition-1.21.vmb.gz","4":"SearchPosition-1.21.vmb.gz","src_id":"22991","5":"22991","creation_date":"1425845301","6":"1425845301"},{"0":"2634","vim_version":"7.0","1":"7.0","script_version":"1.20","2":"1.20","version_comment":"- Abort commands and mappings on error.\r\n- Use SearchPosition#OperatorExpr() to also handle [count] before the operator mapping.\r\n- CHG: Also allow :[range]SearchPosition \/{pattern}\/ argument syntax; make previous :SearchPosition {pattern} do a literal whole word search.\r\n- ENH: Also show range that the matches fall into; locations close to the current line in relative form.\r\n- Add dependency to ingo-library (vimscript #4433). *** You need to separately install ingo-library (vimscript #4433) version 1.020 (or higher)! ***","3":"- Abort commands and mappings on error.\r\n- Use SearchPosition#OperatorExpr() to also handle [count] before the operator mapping.\r\n- CHG: Also allow :[range]SearchPosition \/{pattern}\/ argument syntax; make previous :SearchPosition {pattern} do a literal whole word search.\r\n- ENH: Also show range that the matches fall into; locations close to the current line in relative form.\r\n- Add dependency to ingo-library (vimscript #4433). *** You need to separately install ingo-library (vimscript #4433) version 1.020 (or higher)! ***","package":"SearchPosition-1.20.vmb.gz","4":"SearchPosition-1.20.vmb.gz","src_id":"22059","5":"22059","creation_date":"1403204194","6":"1403204194"},{"0":"2634","vim_version":"7.0","1":"7.0","script_version":"1.13","2":"1.13","version_comment":"- BUG: The previous fix for the incorrect reporting of sole match in folded line was susceptible to non-local matches when current line is the first line. ","3":"- BUG: The previous fix for the incorrect reporting of sole match in folded line was susceptible to non-local matches when current line is the first line. ","package":"SearchPosition.vba.gz","4":"SearchPosition.vba.gz","src_id":"14028","5":"14028","creation_date":"1286550320","6":"1286550320"},{"0":"2634","vim_version":"7.0","1":"7.0","script_version":"1.12","2":"1.12","version_comment":"- BUG: Visual mode <A-m> \/Plug>SearchPositionCword mapping on multi-line selection searched for ^@, not the newline character \\n. \r\n- BUG: Incorrect reporting of sole match in folded line when the current line is empty and the pattern starts matching a newline character.\r\n- Using SearchPosition#SavePosition() instead ofVim version-dependent) mark to keep the cursor at the position where the operator was invokedonly necessary with a backward {motion}). ","3":"- BUG: Visual mode <A-m> \/Plug>SearchPositionCword mapping on multi-line selection searched for ^@, not the newline character \\n. \r\n- BUG: Incorrect reporting of sole match in folded line when the current line is empty and the pattern starts matching a newline character.\r\n- Using SearchPosition#SavePosition() instead ofVim version-dependent) mark to keep the cursor at the position where the operator was invokedonly necessary with a backward {motion}). ","package":"SearchPosition.vba.gz","4":"SearchPosition.vba.gz","src_id":"14027","5":"14027","creation_date":"1286548872","6":"1286548872"},{"0":"2634","vim_version":"7.0","1":"7.0","script_version":"1.11","2":"1.11","version_comment":"Appended \"; total N\" to evaluations that excluded the match on the cursor from the \"overall\" count, as it was misleading what \"overall\" meant in this context.","3":"Appended \"; total N\" to evaluations that excluded the match on the cursor from the \"overall\" count, as it was misleading what \"overall\" meant in this context.","package":"SearchPosition.vba.gz","4":"SearchPosition.vba.gz","src_id":"13087","5":"13087","creation_date":"1275492844","6":"1275492844"},{"0":"2634","vim_version":"7.0","1":"7.0","script_version":"1.10","2":"1.10","version_comment":"- Moved functions from plugin to separate autoload script.\r\n- BUG: Wrong reporting of additional occurrences when the current line is outside the passed range. \r\n- BUG: Catch non-existing items in evaluations that can be caused by e.g having \\%# inside the search pattern. Warn about \"special atoms have distorted the tally\" in such cases. ","3":"- Moved functions from plugin to separate autoload script.\r\n- BUG: Wrong reporting of additional occurrences when the current line is outside the passed range. \r\n- BUG: Catch non-existing items in evaluations that can be caused by e.g having \\%# inside the search pattern. Warn about \"special atoms have distorted the tally\" in such cases. ","package":"SearchPosition.vba.gz","4":"SearchPosition.vba.gz","src_id":"12033","5":"12033","creation_date":"1262987960","6":"1262987960"},{"0":"2634","vim_version":"7.0","1":"7.0","script_version":"1.03","2":"1.03","version_comment":"ENH: Offering a whole-word ALT-M mapping in addition to the former literal search (which is now mapped to g_ALT-M), like the |star| and |gstar| commands. ","3":"ENH: Offering a whole-word ALT-M mapping in addition to the former literal search (which is now mapped to g_ALT-M), like the |star| and |gstar| commands. ","package":"SearchPosition.vba.gz","4":"SearchPosition.vba.gz","src_id":"12018","5":"12018","creation_date":"1262726259","6":"1262726259"},{"0":"2634","vim_version":"7.0","1":"7.0","script_version":"1.02","2":"1.02","version_comment":"BUG: Cannot set mark \" in Vim 7.0 and 7.1; using mark z instead. This only affected the <Leader><A-n>{motion} command. ","3":"BUG: Cannot set mark \" in Vim 7.0 and 7.1; using mark z instead. This only affected the <Leader><A-n>{motion} command. ","package":"SearchPosition.vba.gz","4":"SearchPosition.vba.gz","src_id":"11358","5":"11358","creation_date":"1252674673","6":"1252674673"},{"0":"2634","vim_version":"7.0","1":"7.0","script_version":"1.01","2":"1.01","version_comment":"The jumplist is not clobbered anymore by the :SearchPosition command. ","3":"The jumplist is not clobbered anymore by the :SearchPosition command. ","package":"SearchPosition.vba.gz","4":"SearchPosition.vba.gz","src_id":"10876","5":"10876","creation_date":"1245442386","6":"1245442386"},{"0":"2634","vim_version":"7.0","1":"7.0","script_version":"1.00","2":"1.00","version_comment":"Initial upload","3":"Initial upload","package":"SearchPosition.vba.gz","4":"SearchPosition.vba.gz","src_id":"10606","5":"10606","creation_date":"1242420348","6":"1242420348"}]},"2633":{"script_id":"2633","0":"2633","script_name":"csindent.vim","1":"csindent.vim","script_type":"indent","2":"indent","summary":"Indent file per project","3":"Indent file per project","description":"How to use the plug-in:\r\n1. Create `~\/.vim_csindent.ini' (default value of `g:csindent_ini') with\r\n   format:\r\n       '[' <FILETYPE_NAME> [':' <DEFAULT_INDENT_NAME> ] ']'\r\n       <INDENT_NAME> '=' <PATH>\r\n\r\n   <INDENT_NAME> is common indent file without '.vim' suffix.\r\n   <PATH> is your path of project.\r\n\r\n   If exists <DEFAULT_INDENT_NAME>, then <DEFAULT_INDENT_NAME>.vim file is\r\n   default indent file for this filetype.\r\n\r\n   For example:\r\n       [cpp:shetukhin]\r\n       google = $HOME\/work\/pyctpp2\r\n\r\n       [c]\r\n       linux = $HOME\/work\/kernels\/\r\n       gnu = $HOME\/work\/hurd\r\n\r\n2. Create `~\/.vim\/csindent\/<FILETYPE_NAME>\/<INDENT_NAME>.vim'\r\n   (instead of `~\/.vim\/csindent` you can use any path from 'runtimepath').\r\n   For example:\r\n        ~\/.vim\/csindent\/cpp\/shetukhin.vim\r\n        ~\/.vim\/csindent\/cpp\/google.vim\r\n        ~\/.vim\/csindent\/c\/linux.vim\r\n        ~\/.vim\/csindent\/c\/gnu.vim\r\n\r\nNote 1: This script is compatible with `filetype indent`.\r\n        See `:help filetype`.\r\n\r\nNote 2: You can use more informative status line using CodingStyleIndent().\r\n        For example:\r\n            set statusline=%<%f%h%m%r%=style=%{CodingStyleIndent()}\r\n            \\ %15(L%l,C%c%V%)\\ %3P","4":"How to use the plug-in:\r\n1. Create `~\/.vim_csindent.ini' (default value of `g:csindent_ini') with\r\n   format:\r\n       '[' <FILETYPE_NAME> [':' <DEFAULT_INDENT_NAME> ] ']'\r\n       <INDENT_NAME> '=' <PATH>\r\n\r\n   <INDENT_NAME> is common indent file without '.vim' suffix.\r\n   <PATH> is your path of project.\r\n\r\n   If exists <DEFAULT_INDENT_NAME>, then <DEFAULT_INDENT_NAME>.vim file is\r\n   default indent file for this filetype.\r\n\r\n   For example:\r\n       [cpp:shetukhin]\r\n       google = $HOME\/work\/pyctpp2\r\n\r\n       [c]\r\n       linux = $HOME\/work\/kernels\/\r\n       gnu = $HOME\/work\/hurd\r\n\r\n2. Create `~\/.vim\/csindent\/<FILETYPE_NAME>\/<INDENT_NAME>.vim'\r\n   (instead of `~\/.vim\/csindent` you can use any path from 'runtimepath').\r\n   For example:\r\n        ~\/.vim\/csindent\/cpp\/shetukhin.vim\r\n        ~\/.vim\/csindent\/cpp\/google.vim\r\n        ~\/.vim\/csindent\/c\/linux.vim\r\n        ~\/.vim\/csindent\/c\/gnu.vim\r\n\r\nNote 1: This script is compatible with `filetype indent`.\r\n        See `:help filetype`.\r\n\r\nNote 2: You can use more informative status line using CodingStyleIndent().\r\n        For example:\r\n            set statusline=%<%f%h%m%r%=style=%{CodingStyleIndent()}\r\n            \\ %15(L%l,C%c%V%)\\ %3P","install_details":"Move csindent.vim to '~\/.vim\/plugin`.\r\n","5":"Move csindent.vim to '~\/.vim\/plugin`.\r\n","first_name":"Konstantin","6":"Konstantin","last_name":"Lepa","7":"Lepa","releases":[{"0":"2633","vim_version":"7.0","1":"7.0","script_version":"1.2.0","2":"1.2.0","version_comment":"Added support of Windows.\r\nRemoved g:csindent_dir. Used 'runtimepath' instead it.\r\nAdded support of expanding environment variables in g:csindent_ini.","3":"Added support of Windows.\r\nRemoved g:csindent_dir. Used 'runtimepath' instead it.\r\nAdded support of expanding environment variables in g:csindent_ini.","package":"csindent.vim","4":"csindent.vim","src_id":"14936","5":"14936","creation_date":"1296569592","6":"1296569592"},{"0":"2633","vim_version":"7.0","1":"7.0","script_version":"1.1.2","2":"1.1.2","version_comment":"Fixed syntax errors in SelectCodingStyleIndent().","3":"Fixed syntax errors in SelectCodingStyleIndent().","package":"csindent.vim","4":"csindent.vim","src_id":"14774","5":"14774","creation_date":"1295272806","6":"1295272806"},{"0":"2633","vim_version":"7.0","1":"7.0","script_version":"1.1.1","2":"1.1.1","version_comment":"Fixed problem of detecting of invalid indent filename.","3":"Fixed problem of detecting of invalid indent filename.","package":"csindent.vim","4":"csindent.vim","src_id":"14771","5":"14771","creation_date":"1295271649","6":"1295271649"},{"0":"2633","vim_version":"7.0","1":"7.0","script_version":"1.1.0","2":"1.1.0","version_comment":"Renamed script name from coding_style to csindent.\r\nAdded support of default coding style.\r\nAdded support of `filetype indent on` by default.\r\nRenamed g:coding_style_ini to g:csindent_ini (~\/.vim_csindent.ini).\r\nRenamed g:coding_style_dir to g:csindent_dir (~\/.vim\/csindent).\r\nChanged indent file path to `g:csindent_dir` + `filetype` + `indent file`.\r\nChanged comment char from '#' to ';' in g:csindent_ini file.","3":"Renamed script name from coding_style to csindent.\r\nAdded support of default coding style.\r\nAdded support of `filetype indent on` by default.\r\nRenamed g:coding_style_ini to g:csindent_ini (~\/.vim_csindent.ini).\r\nRenamed g:coding_style_dir to g:csindent_dir (~\/.vim\/csindent).\r\nChanged indent file path to `g:csindent_dir` + `filetype` + `indent file`.\r\nChanged comment char from '#' to ';' in g:csindent_ini file.","package":"csindent.vim","4":"csindent.vim","src_id":"14761","5":"14761","creation_date":"1295184407","6":"1295184407"},{"0":"2633","vim_version":"7.0","1":"7.0","script_version":"1.0.3","2":"1.0.3","version_comment":"Added support of comments in the g:coding_style_ini file.","3":"Added support of comments in the g:coding_style_ini file.","package":"coding_style.vim","4":"coding_style.vim","src_id":"11753","5":"11753","creation_date":"1258540194","6":"1258540194"},{"0":"2633","vim_version":"7.0","1":"7.0","script_version":"1.0.2","2":"1.0.2","version_comment":"Renamed the folder cs_indent to coding_styles.\r\nRemoved styles.txt.\r\nAdded g:coding_style_ini (default ~\/.coding_style.ini).\r\nAdded g:coding_style_dir (default ~\/.vim\/coding_styles).","3":"Renamed the folder cs_indent to coding_styles.\r\nRemoved styles.txt.\r\nAdded g:coding_style_ini (default ~\/.coding_style.ini).\r\nAdded g:coding_style_dir (default ~\/.vim\/coding_styles).","package":"coding_style.vim","4":"coding_style.vim","src_id":"10619","5":"10619","creation_date":"1242561085","6":"1242561085"},{"0":"2633","vim_version":"7.0","1":"7.0","script_version":"1.0.1","2":"1.0.1","version_comment":"Added CodingStyle() for checking of current coding style.","3":"Added CodingStyle() for checking of current coding style.","package":"coding_style.vim","4":"coding_style.vim","src_id":"10611","5":"10611","creation_date":"1242474230","6":"1242474230"},{"0":"2633","vim_version":"7.0","1":"7.0","script_version":"1.0.0","2":"1.0.0","version_comment":"Initial upload","3":"Initial upload","package":"coding_style.vim","4":"coding_style.vim","src_id":"10605","5":"10605","creation_date":"1242414009","6":"1242414009"}]},"2632":{"script_id":"2632","0":"2632","script_name":"nimrod.vim","1":"nimrod.vim","script_type":"syntax","2":"syntax","summary":"(DEPRECATED) Nimrod syntax support","3":"(DEPRECATED) Nimrod syntax support","description":"Do not use this!\r\n\r\nRather use the one at https:\/\/github.com\/zah\/nimrod.vim","4":"Do not use this!\r\n\r\nRather use the one at https:\/\/github.com\/zah\/nimrod.vim","install_details":"","5":"","first_name":"Kearn","6":"Kearn","last_name":"Holliday","7":"Holliday","releases":[{"0":"2632","vim_version":"6.0","1":"6.0","script_version":"1.1","2":"1.1","version_comment":"hopefully this one actually works now, removed pesky ^M chars","3":"hopefully this one actually works now, removed pesky ^M chars","package":"nimrod.vim","4":"nimrod.vim","src_id":"10607","5":"10607","creation_date":"1242420766","6":"1242420766"},{"0":"2632","vim_version":"6.0","1":"6.0","script_version":"1.1","2":"1.1","version_comment":"removed single quotes matching for strings","3":"removed single quotes matching for strings","package":"nimrod.vim","4":"nimrod.vim","src_id":"10598","5":"10598","creation_date":"1242382611","6":"1242382611"},{"0":"2632","vim_version":"6.0","1":"6.0","script_version":"1.1","2":"1.1","version_comment":"the builtin 'contains' was was conflicting with a vim reserved word, fixed by changing to 'syn match'","3":"the builtin 'contains' was was conflicting with a vim reserved word, fixed by changing to 'syn match'","package":"nimrod.vim","4":"nimrod.vim","src_id":"10597","5":"10597","creation_date":"1242382411","6":"1242382411"},{"0":"2632","vim_version":"5.7","1":"5.7","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"nimrod.vim","4":"nimrod.vim","src_id":"10591","5":"10591","creation_date":"1242337843","6":"1242337843"}]},"2631":{"script_id":"2631","0":"2631","script_name":"dosbatch indent","1":"dosbatch indent","script_type":"indent","2":"indent","summary":"Indenting for filetype dosbatch","3":"Indenting for filetype dosbatch","description":"I couldn't find an indent script for DOS batch files so I wrote a simple one.  It just follows these rules:\r\n - generally keep the indent of the previous line \r\n - if previous line is not a comment and has ( and no matching ), increase indent\r\n - if this line starts with ), decrease indent\r\n\r\nI started by cutting down and modifying Erik Janssen's awk.vim.","4":"I couldn't find an indent script for DOS batch files so I wrote a simple one.  It just follows these rules:\r\n - generally keep the indent of the previous line \r\n - if previous line is not a comment and has ( and no matching ), increase indent\r\n - if this line starts with ), decrease indent\r\n\r\nI started by cutting down and modifying Erik Janssen's awk.vim.","install_details":"Copy the file into one of the indent directories in your runtime path (see :help 'runtimepath'), personally I put it in c:\\program files\\vim\\vimfiles\\indent\\\r\n\r\nMake sure filetype-specific indenting is switched on (see :help filetype), personally I put this in my _vimrc file\r\n\r\n:filetype indent on","5":"Copy the file into one of the indent directories in your runtime path (see :help 'runtimepath'), personally I put it in c:\\program files\\vim\\vimfiles\\indent\\\r\n\r\nMake sure filetype-specific indenting is switched on (see :help filetype), personally I put this in my _vimrc file\r\n\r\n:filetype indent on","first_name":"Geoff","6":"Geoff","last_name":"Wood","7":"Wood","releases":[{"0":"2631","vim_version":"6.0","1":"6.0","script_version":"1","2":"1","version_comment":"Initial upload","3":"Initial upload","package":"dosbatch.vim","4":"dosbatch.vim","src_id":"10590","5":"10590","creation_date":"1242304612","6":"1242304612"}]},"2630":{"script_id":"2630","0":"2630","script_name":"compiler\/jsl.vim","1":"compiler\/jsl.vim","script_type":"ftplugin","2":"ftplugin","summary":"Compiler plugin for JavaScript Lint. ","3":"Compiler plugin for JavaScript Lint. ","description":"Compiler plugin for JavaScript Lint (http:\/\/www.javascriptlint.com), an (open\r\nsource) checker for JavaScript syntax and coding techniques based on the Mozilla\r\nFirefox JavaScript engine. \r\n\r\nThis is similar to vimscript #2578 and vimscript #2729, but this script uses\r\nVim's compiler infrastructure (so checks are triggered by the :make command),\r\nmaking its use consistent with syntax checkers for other languages. ","4":"Compiler plugin for JavaScript Lint (http:\/\/www.javascriptlint.com), an (open\r\nsource) checker for JavaScript syntax and coding techniques based on the Mozilla\r\nFirefox JavaScript engine. \r\n\r\nThis is similar to vimscript #2578 and vimscript #2729, but this script uses\r\nVim's compiler infrastructure (so checks are triggered by the :make command),\r\nmaking its use consistent with syntax checkers for other languages. ","install_details":"JavaScript Lint must be installed and available through $PATH. \r\n\r\nPut the script into your user or system Vim compiler directory\r\n(e.g. ~\/.vim\/compiler). \r\n\r\nTo automatically select this compiler for all JavaScript files, put the\r\nfollowing snippet into ~\/.vim\/after\/ftplugin\/javascript.vim:\r\n\r\n\" Set JavaScript Lint as compiler. \r\nif ! exists('b:current_compiler')\r\n    compiler jsl\r\nendif\r\n\r\nCONFIGURATION\r\nThe optional jsl configuration must either reside in this script's directory as\r\n'jsl.conf', or its filespec can be specified in g:jsl_config.  ","5":"JavaScript Lint must be installed and available through $PATH. \r\n\r\nPut the script into your user or system Vim compiler directory\r\n(e.g. ~\/.vim\/compiler). \r\n\r\nTo automatically select this compiler for all JavaScript files, put the\r\nfollowing snippet into ~\/.vim\/after\/ftplugin\/javascript.vim:\r\n\r\n\" Set JavaScript Lint as compiler. \r\nif ! exists('b:current_compiler')\r\n    compiler jsl\r\nendif\r\n\r\nCONFIGURATION\r\nThe optional jsl configuration must either reside in this script's directory as\r\n'jsl.conf', or its filespec can be specified in g:jsl_config.  ","first_name":"Ingo","6":"Ingo","last_name":"Karkat","7":"Karkat","releases":[{"0":"2630","vim_version":"6.0","1":"6.0","script_version":"1.00.003","2":"1.00.003","version_comment":"Initial upload (2) - Added license and modeline. ","3":"Initial upload (2) - Added license and modeline. ","package":"jsl.vim","4":"jsl.vim","src_id":"10576","5":"10576","creation_date":"1242044815","6":"1242044815"}]},"2629":{"script_id":"2629","0":"2629","script_name":"explorer","1":"explorer","script_type":"utility","2":"utility","summary":"Filesystem explorer","3":"Filesystem explorer","description":"This is the original explorer.vim plugin from Vim 6.4. As of Vim 7.0 this functionality is provided by the netrw.vim plugin but I prefer the original.","4":"This is the original explorer.vim plugin from Vim 6.4. As of Vim 7.0 this functionality is provided by the netrw.vim plugin but I prefer the original.","install_details":"mkdir -p ~\/.vim\/plugin\r\ncp explorer.vim !$\r\n\r\nAdd the following to your vimrc:\r\nlet loaded_netrw=1\r\nlet loaded_netrwPlugin=1","5":"mkdir -p ~\/.vim\/plugin\r\ncp explorer.vim !$\r\n\r\nAdd the following to your vimrc:\r\nlet loaded_netrw=1\r\nlet loaded_netrwPlugin=1","first_name":"Paddy","6":"Paddy","last_name":"Newman","7":"Newman","releases":[{"0":"2629","vim_version":"6.0","1":"6.0","script_version":"2.5","2":"2.5","version_comment":"Initial upload","3":"Initial upload","package":"explorer.vim","4":"explorer.vim","src_id":"10565","5":"10565","creation_date":"1241891584","6":"1241891584"}]},"2628":{"script_id":"2628","0":"2628","script_name":"Nvim-R","1":"Nvim-R","script_type":"ftplugin","2":"ftplugin","summary":"Plugin to work with R","3":"Plugin to work with R","description":"This plugin improves Vim's support for editing R code and makes it possible to integrate Vim with R.\r\n\r\nDevelopment code and bug report: https:\/\/github.com\/jalvesaq\/Nvim-R\r\n\r\nStable version: https:\/\/github.com\/jalvesaq\/Nvim-R\/tree\/stable\r\n\r\nMAIN FEATURES:\r\n\r\n  * Communication with R.\r\n  * Omni completion (auto-completion) for R objects and function arguments.\r\n  * Ability to see R's documentation in a Vim's buffer.\r\n  * Object Browser.\r\n  * Most of the plugin's behavior is customizable.","4":"This plugin improves Vim's support for editing R code and makes it possible to integrate Vim with R.\r\n\r\nDevelopment code and bug report: https:\/\/github.com\/jalvesaq\/Nvim-R\r\n\r\nStable version: https:\/\/github.com\/jalvesaq\/Nvim-R\/tree\/stable\r\n\r\nMAIN FEATURES:\r\n\r\n  * Communication with R.\r\n  * Omni completion (auto-completion) for R objects and function arguments.\r\n  * Ability to see R's documentation in a Vim's buffer.\r\n  * Object Browser.\r\n  * Most of the plugin's behavior is customizable.","install_details":"See https:\/\/raw.githubusercontent.com\/jalvesaq\/Nvim-R\/master\/doc\/Nvim-R.txt","5":"See https:\/\/raw.githubusercontent.com\/jalvesaq\/Nvim-R\/master\/doc\/Nvim-R.txt","first_name":"Jakson","6":"Jakson","last_name":"Aquino","7":"Aquino","releases":[{"0":"2628","vim_version":"8.2","1":"8.2","script_version":"0.9.17","2":"0.9.17","version_comment":"* Require either Neovim 0.5.0 or Vim 8.2.84.\r\n* New options: R_set_omnifunc, R_auto_omni, R_rmarkdown_args, R_objbr_auto_start, R_quarto_render_args, and R_quarto_preview_args, R_debug_center, R_term_title.\r\n* Delete options: R_omni_tmp_file and R_omni_size.","3":"* Require either Neovim 0.5.0 or Vim 8.2.84.\r\n* New options: R_set_omnifunc, R_auto_omni, R_rmarkdown_args, R_objbr_auto_start, R_quarto_render_args, and R_quarto_preview_args, R_debug_center, R_term_title.\r\n* Delete options: R_omni_tmp_file and R_omni_size.","package":"Nvim-R-0.9.17.zip","4":"Nvim-R-0.9.17.zip","src_id":"28193","5":"28193","creation_date":"1664480348","6":"1664480348"},{"0":"2628","vim_version":"8.2","1":"8.2","script_version":"0.9.16","2":"0.9.16","version_comment":"* Minor bug fixes.\r\n* New options: R_omni_size and R_omni_tmp_file.","3":"* Minor bug fixes.\r\n* New options: R_omni_size and R_omni_tmp_file.","package":"Nvim-R-0.9.16.zip","4":"Nvim-R-0.9.16.zip","src_id":"27581","5":"27581","creation_date":"1619762271","6":"1619762271"},{"0":"2628","vim_version":"8.2","1":"8.2","script_version":"0.9.15","2":"0.9.15","version_comment":"* Delete options R_ls_env_tol, R_objbr_labelerr, R_show_arg_help.\r\n* New options: R_clear_console, R_debug, R_auto_start, R_dbg_jump.\r\n* Replace options R_in_buffer, R_term and R_term_cmd with a single option: R_external_term.\r\n* Make R_rmdchunk more flexible.\r\n* Change default key binding for calling debug() from \\db to \\bg to avoid conflict with \\d (send line).\r\n* Require either Neovim >= 0.4.3 or Vim >= 8.1.1705.\r\n","3":"* Delete options R_ls_env_tol, R_objbr_labelerr, R_show_arg_help.\r\n* New options: R_clear_console, R_debug, R_auto_start, R_dbg_jump.\r\n* Replace options R_in_buffer, R_term and R_term_cmd with a single option: R_external_term.\r\n* Make R_rmdchunk more flexible.\r\n* Change default key binding for calling debug() from \\db to \\bg to avoid conflict with \\d (send line).\r\n* Require either Neovim >= 0.4.3 or Vim >= 8.1.1705.\r\n","package":"Nvim-R.zip","4":"Nvim-R.zip","src_id":"27572","5":"27572","creation_date":"1618545070","6":"1618545070"},{"0":"2628","vim_version":"8.0","1":"8.0","script_version":"0.9.14","2":"0.9.14","version_comment":" * New command \\su (send all lines above the current one).\r\n * New command \\m (send lines from motion command).\r\n * New option: R_disable_cmds.\r\n * New option: R_after_ob_open.\r\n * R_after_start is a list now.\r\n * Recommend Visidata and delete option R_csv_warn.\r\n * Delete command triggered by `<LocalLeader>tp`.\r\n * Delete options R_args_in_stline, R_sttline_fmt, R_show_args, R_complete and Rtools_path.\r\n * Limited support for debugging R functions.","3":" * New command \\su (send all lines above the current one).\r\n * New command \\m (send lines from motion command).\r\n * New option: R_disable_cmds.\r\n * New option: R_after_ob_open.\r\n * R_after_start is a list now.\r\n * Recommend Visidata and delete option R_csv_warn.\r\n * Delete command triggered by `<LocalLeader>tp`.\r\n * Delete options R_args_in_stline, R_sttline_fmt, R_show_args, R_complete and Rtools_path.\r\n * Limited support for debugging R functions.","package":"Nvim-R.vmb","4":"Nvim-R.vmb","src_id":"27185","5":"27185","creation_date":"1591060271","6":"1591060271"},{"0":"2628","vim_version":"8.0","1":"8.0","script_version":"0.9.13","2":"0.9.13","version_comment":"* Support for Python code in knitr chunks: integration with the R package reticulate and with the jedi-vim plugin.\r\n* New options: R_editing_mode, R_buffer_opts.\r\n* Minor bug fixes.","3":"* Support for Python code in knitr chunks: integration with the R package reticulate and with the jedi-vim plugin.\r\n* New options: R_editing_mode, R_buffer_opts.\r\n* Minor bug fixes.","package":"Nvim-R.vmb","4":"Nvim-R.vmb","src_id":"26482","5":"26482","creation_date":"1557093617","6":"1557093617"},{"0":"2628","vim_version":"8.0","1":"8.0","script_version":"0.9.12","2":"0.9.12","version_comment":"* Minor bug fixes.\r\n* Bibliographic completion for Rmd.\r\n* New command:  :RDebugInfo\r\n* New options: R_hi_fun_globenv, R_auto_scroll, R_ls_env_tol, R_non_r_compl, R_cite_pattern.\r\n* Accept prefix \"terminal:\" in `R_csv_app`.\r\n* Remove option R_tmux_split.\r\n* Changes:\r\n   - If the Object Browser is already open, \\ro will close it.\r\n   - The values \"bottom\" and \"top\" are no longer valid for R_objbr_place (use \"below\" and \"above\" instead).","3":"* Minor bug fixes.\r\n* Bibliographic completion for Rmd.\r\n* New command:  :RDebugInfo\r\n* New options: R_hi_fun_globenv, R_auto_scroll, R_ls_env_tol, R_non_r_compl, R_cite_pattern.\r\n* Accept prefix \"terminal:\" in `R_csv_app`.\r\n* Remove option R_tmux_split.\r\n* Changes:\r\n   - If the Object Browser is already open, \\ro will close it.\r\n   - The values \"bottom\" and \"top\" are no longer valid for R_objbr_place (use \"below\" and \"above\" instead).","package":"Nvim-R.vmb","4":"Nvim-R.vmb","src_id":"26185","5":"26185","creation_date":"1534710638","6":"1534710638"},{"0":"2628","vim_version":"8.0","1":"8.0","script_version":"0.9.11","2":"0.9.11","version_comment":"* The option R_latexcmd now is a list and the option R_latexmk no longer exists. By default, latexmk and xelatex will be called to compile pdf documents.\r\n* Arguments completion is now done by CTRL-X CTRL-O.\r\n* New options: R_OutDec, R_csv_delim, R_rmdchunk, R_parenblock, R_bracketed_paste, R_complete.\r\n* New command: `:RSend`.","3":"* The option R_latexcmd now is a list and the option R_latexmk no longer exists. By default, latexmk and xelatex will be called to compile pdf documents.\r\n* Arguments completion is now done by CTRL-X CTRL-O.\r\n* New options: R_OutDec, R_csv_delim, R_rmdchunk, R_parenblock, R_bracketed_paste, R_complete.\r\n* New command: `:RSend`.","package":"Nvim-R.vmb","4":"Nvim-R.vmb","src_id":"25807","5":"25807","creation_date":"1517271011","6":"1517271011"},{"0":"2628","vim_version":"8.0","1":"8.0","script_version":"0.9.10","2":"0.9.10","version_comment":"* Change command \\dt to \\td and \\pt to \\tp.\r\n* New default value for R_show_args = 1.\r\n* New options: R_hi_fun_paren, R_show_arg_help,R_sttline_fmt and R_set_sttline_cmd.\r\n* Minor bug fixes.","3":"* Change command \\dt to \\td and \\pt to \\tp.\r\n* New default value for R_show_args = 1.\r\n* New options: R_hi_fun_paren, R_show_arg_help,R_sttline_fmt and R_set_sttline_cmd.\r\n* Minor bug fixes.","package":"Nvim-R.vmb","4":"Nvim-R.vmb","src_id":"25557","5":"25557","creation_date":"1504917462","6":"1504917462"},{"0":"2628","vim_version":"8.0","1":"8.0","script_version":"0.9.9","2":"0.9.9","version_comment":" * Delete option R_vsplit.\r\n * New options: R_min_editor_width and R_wait_reply, Rtools_path, R_remote_tmpdir, R_nvimcom_home, R_paragraph_begin.\r\n * Rename option R_ca_ck as R_clear_line\r\n * Change in \\pp behavior.\r\n * Minor bug fixes.","3":" * Delete option R_vsplit.\r\n * New options: R_min_editor_width and R_wait_reply, Rtools_path, R_remote_tmpdir, R_nvimcom_home, R_paragraph_begin.\r\n * Rename option R_ca_ck as R_clear_line\r\n * Change in \\pp behavior.\r\n * Minor bug fixes.","package":"Nvim-R.vmb","4":"Nvim-R.vmb","src_id":"25087","5":"25087","creation_date":"1492868730","6":"1492868730"},{"0":"2628","vim_version":"8.0","1":"8.0","script_version":"0.9.8","2":"0.9.8","version_comment":"* Minor bug fixes.\r\n* New commands: \\dt and \\pt","3":"* Minor bug fixes.\r\n* New commands: \\dt and \\pt","package":"Nvim-R.vmb","4":"Nvim-R.vmb","src_id":"24795","5":"24795","creation_date":"1481395492","6":"1481395492"},{"0":"2628","vim_version":"8.0","1":"8.0","script_version":"0.9.7","2":"0.9.7","version_comment":"* Require Vim >= 8.0.0 or Neovim >= 0.1.5.\r\n* Replaced R_nvimcom_wait (time in miliseconds) with R_wait (time in seconds).\r\n* Minor bug fixes.","3":"* Require Vim >= 8.0.0 or Neovim >= 0.1.5.\r\n* Replaced R_nvimcom_wait (time in miliseconds) with R_wait (time in seconds).\r\n* Minor bug fixes.","package":"Nvim-R.vmb","4":"Nvim-R.vmb","src_id":"24563","5":"24563","creation_date":"1474925207","6":"1474925207"},{"0":"2628","vim_version":"7.4","1":"7.4","script_version":"0.9.6","2":"0.9.6","version_comment":"* New option: R_open_example.\r\n* Change default value of R_source_args to \"print.eval=TRUE\".\r\n* Change in \\aa and \\ae: do not save the buffer before sending the whole file to R.\r\n* Minor bug fixes.","3":"* New option: R_open_example.\r\n* Change default value of R_source_args to \"print.eval=TRUE\".\r\n* Change in \\aa and \\ae: do not save the buffer before sending the whole file to R.\r\n* Minor bug fixes.","package":"Nvim-R.vmb","4":"Nvim-R.vmb","src_id":"24438","5":"24438","creation_date":"1470841091","6":"1470841091"},{"0":"2628","vim_version":"7.4","1":"7.4","script_version":"0.9.5","2":"0.9.5","version_comment":"* Ask whether R_LIBS_USER directory should be created.","3":"* Ask whether R_LIBS_USER directory should be created.","package":"Nvim-R.vmb","4":"Nvim-R.vmb","src_id":"24255","5":"24255","creation_date":"1463563519","6":"1463563519"},{"0":"2628","vim_version":"7.4","1":"7.4","script_version":"0.9.4","2":"0.9.4","version_comment":"* Delete option R_tmux_ob. The Object Browser will always start in a Vim split window, not in a Tmux split pane.\r\n* New option: R_cmd.\r\n* Minor bug fixes.\r\n* Require Neovim >= 0.1.4 or Vim >= 7.4.1829.","3":"* Delete option R_tmux_ob. The Object Browser will always start in a Vim split window, not in a Tmux split pane.\r\n* New option: R_cmd.\r\n* Minor bug fixes.\r\n* Require Neovim >= 0.1.4 or Vim >= 7.4.1829.","package":"Nvim-R.vmb","4":"Nvim-R.vmb","src_id":"24251","5":"24251","creation_date":"1463436039","6":"1463436039"},{"0":"2628","vim_version":"7.4","1":"7.4","script_version":"0.9.3","2":"0.9.3","version_comment":"* Build nvimcom even when Nvim-R directory in non-writable.","3":"* Build nvimcom even when Nvim-R directory in non-writable.","package":"Nvim-R.vmb","4":"Nvim-R.vmb","src_id":"24132","5":"24132","creation_date":"1458814003","6":"1458814003"},{"0":"2628","vim_version":"7.4","1":"7.4","script_version":"0.9.2","2":"0.9.2","version_comment":"- The plugin now is from a new git repository: Nvim-R.\r\n- Support both Vim and Neovim.\r\n- Change option prefix from vimrplugin_ to R_.\r\n- New option: R_app.","3":"- The plugin now is from a new git repository: Nvim-R.\r\n- Support both Vim and Neovim.\r\n- Change option prefix from vimrplugin_ to R_.\r\n- New option: R_app.","package":"Nvim-R.vmb","4":"Nvim-R.vmb","src_id":"24121","5":"24121","creation_date":"1458397265","6":"1458397265"},{"0":"2628","vim_version":"7.4","1":"7.4","script_version":"1.3.1","2":"1.3.1","version_comment":"* Require vimcom 1.3-1 and Vim 7.4.1579.","3":"* Require vimcom 1.3-1 and Vim 7.4.1579.","package":"Vim-R-plugin.vmb","4":"Vim-R-plugin.vmb","src_id":"24107","5":"24107","creation_date":"1458132548","6":"1458132548"},{"0":"2628","vim_version":"7.4","1":"7.4","script_version":"1.3.0","2":"1.3.0","version_comment":"* Fix missing files in vimball: r-plugin\/tmux.vim, r-plugin\/tmux_split.vim and r-plugin\/extern_term.vim.","3":"* Fix missing files in vimball: r-plugin\/tmux.vim, r-plugin\/tmux_split.vim and r-plugin\/extern_term.vim.","package":"Vim-R-plugin.vmb","4":"Vim-R-plugin.vmb","src_id":"24092","5":"24092","creation_date":"1457778633","6":"1457778633"},{"0":"2628","vim_version":"7.4","1":"7.4","script_version":"1.2.9","2":"1.2.9","version_comment":"* Delete option vimrplugin_restart\r\n* Use the +channel and +job features instead of +clientserver.\r\n","3":"* Delete option vimrplugin_restart\r\n* Use the +channel and +job features instead of +clientserver.\r\n","package":"Vim-R-plugin.vmb","4":"Vim-R-plugin.vmb","src_id":"24089","5":"24089","creation_date":"1457731349","6":"1457731349"},{"0":"2628","vim_version":"7.4","1":"7.4","script_version":"1.2.8","2":"1.2.8","version_comment":" * New option (Windows only): vimrplugin_set_home_env.\r\n * Fix bug on Windows: R starting minimized after trying to quit R minimized.","3":" * New option (Windows only): vimrplugin_set_home_env.\r\n * Fix bug on Windows: R starting minimized after trying to quit R minimized.","package":"Vim-R-plugin.vmb","4":"Vim-R-plugin.vmb","src_id":"24027","5":"24027","creation_date":"1455990461","6":"1455990461"},{"0":"2628","vim_version":"7.4","1":"7.4","script_version":"1.2.7","2":"1.2.7","version_comment":"* Fix incompatibility with Tmux 2.1.","3":"* Fix incompatibility with Tmux 2.1.","package":"Vim-R-plugin.vmb","4":"Vim-R-plugin.vmb","src_id":"23760","5":"23760","creation_date":"1448621633","6":"1448621633"},{"0":"2628","vim_version":"7.4","1":"7.4","script_version":"1.2.6","2":"1.2.6","version_comment":"* Improve support for lazy load objects in the Object Browser.\r\n* Remove option vimrplugin_vim_window (use $WINDOWID instead).\r\n* Fix bug that prevented GVim 64 bit of finding libVimR.dll.","3":"* Improve support for lazy load objects in the Object Browser.\r\n* Remove option vimrplugin_vim_window (use $WINDOWID instead).\r\n* Fix bug that prevented GVim 64 bit of finding libVimR.dll.","package":"Vim-R-plugin.vmb","4":"Vim-R-plugin.vmb","src_id":"23382","5":"23382","creation_date":"1434121017","6":"1434121017"},{"0":"2628","vim_version":"7.4","1":"7.4","script_version":"1.2.5","2":"1.2.5","version_comment":"* New command to evaluate selection and get output in newtab: \\so\r\n* The command \\ao no longer blocks Vim.\r\n* New command (\\rv) and new options (vimrplugin_csv_warn, vimrplugin_csv_app and vimrplugin_df_viewer).\r\n* Bring back the \"echo\" send commands because some users need them.","3":"* New command to evaluate selection and get output in newtab: \\so\r\n* The command \\ao no longer blocks Vim.\r\n* New command (\\rv) and new options (vimrplugin_csv_warn, vimrplugin_csv_app and vimrplugin_df_viewer).\r\n* Bring back the \"echo\" send commands because some users need them.","package":"Vim-R-plugin.vmb","4":"Vim-R-plugin.vmb","src_id":"23263","5":"23263","creation_date":"1430918111","6":"1430918111"},{"0":"2628","vim_version":"7.4","1":"7.4","script_version":"1.2.4","2":"1.2.4","version_comment":"* Deleted r-plugin\/global_R_plugin.vim. See: https:\/\/github.com\/jalvesaq\/vimcmdline","3":"* Deleted r-plugin\/global_R_plugin.vim. See: https:\/\/github.com\/jalvesaq\/vimcmdline","package":"Vim-R-plugin.vmb","4":"Vim-R-plugin.vmb","src_id":"23207","5":"23207","creation_date":"1429720377","6":"1429720377"},{"0":"2628","vim_version":"7.4","1":"7.4","script_version":"1.2.3","2":"1.2.3","version_comment":"* Official runtime files were deleted. See: https:\/\/github.com\/jalvesaq\/R-Vim-runtime\r\n* News options to control the Object Browser: vimrplugin_objbr_opendf, vimrplugin_objbr_openlist, vimrplugin_objbr_allnames and vimrplugin_objbr_labelerr.\r\n* New option to control LaTeX compilation: vimrplugin_texerr.\r\n* Fix setting of R working directory on Mac OS X.","3":"* Official runtime files were deleted. See: https:\/\/github.com\/jalvesaq\/R-Vim-runtime\r\n* News options to control the Object Browser: vimrplugin_objbr_opendf, vimrplugin_objbr_openlist, vimrplugin_objbr_allnames and vimrplugin_objbr_labelerr.\r\n* New option to control LaTeX compilation: vimrplugin_texerr.\r\n* Fix setting of R working directory on Mac OS X.","package":"Vim-R-plugin.vmb","4":"Vim-R-plugin.vmb","src_id":"23155","5":"23155","creation_date":"1428616142","6":"1428616142"},{"0":"2628","vim_version":"7.4","1":"7.4","script_version":"1.2.2","2":"1.2.2","version_comment":"* Remove option to start R with the --vanilla argument. See vimrplugin_r_args for an alternative.\r\n* Minor bug fixes.","3":"* Remove option to start R with the --vanilla argument. See vimrplugin_r_args for an alternative.\r\n* Minor bug fixes.","package":"Vim-R-plugin.vmb","4":"Vim-R-plugin.vmb","src_id":"23093","5":"23093","creation_date":"1427202504","6":"1427202504"},{"0":"2628","vim_version":"7.4","1":"7.4","script_version":"1.2.1","2":"1.2.1","version_comment":"* Minor bug fixes.\r\n* New options: vimrplugin_after_start, vimrplugin_args_in_stline, vimrplugin_save_win_pos and vimrplugin_arrange_windows.\r\n* Remove option vimrplugin_maxdeparse, remove the \"echo\" send commands and add the option vimrplugin_source_args.","3":"* Minor bug fixes.\r\n* New options: vimrplugin_after_start, vimrplugin_args_in_stline, vimrplugin_save_win_pos and vimrplugin_arrange_windows.\r\n* Remove option vimrplugin_maxdeparse, remove the \"echo\" send commands and add the option vimrplugin_source_args.","package":"Vim-R-plugin.vmb","4":"Vim-R-plugin.vmb","src_id":"22981","5":"22981","creation_date":"1425578003","6":"1425578003"},{"0":"2628","vim_version":"7.4","1":"7.4","script_version":"1.2","2":"1.2","version_comment":"* Remove support for Neovim. See: https:\/\/github.com\/jalvesaq\/Nvim-R\r\n* Remove command :RpluginConfig.\r\n* Remove option vimrplugin_Rterm.\r\n* Change commands gn and gN to <LocalLeader>gn and <LocalLeader>gN.\r\n* Change default value of vimrplugin_openpdf to 2.\r\n* Options vimrplugin_sleeptime now should be in miliseconds.\r\n* Replace option vimrplugin_external_ob with vimrplugin_tmux_ob.\r\n* Rename vimrplugin_permanent_libs to vimrplugin_start_libs.\r\n* Rename vimrplugin_routmorecolors to Rout_more_colors.\r\n* New command: :RStop.\r\n* No longer require +python feature; require +libcall instead.\r\n* Support for SyncTeX on Windows and Mac OS X.\r\n* New option: vimrplugin_latexmk","3":"* Remove support for Neovim. See: https:\/\/github.com\/jalvesaq\/Nvim-R\r\n* Remove command :RpluginConfig.\r\n* Remove option vimrplugin_Rterm.\r\n* Change commands gn and gN to <LocalLeader>gn and <LocalLeader>gN.\r\n* Change default value of vimrplugin_openpdf to 2.\r\n* Options vimrplugin_sleeptime now should be in miliseconds.\r\n* Replace option vimrplugin_external_ob with vimrplugin_tmux_ob.\r\n* Rename vimrplugin_permanent_libs to vimrplugin_start_libs.\r\n* Rename vimrplugin_routmorecolors to Rout_more_colors.\r\n* New command: :RStop.\r\n* No longer require +python feature; require +libcall instead.\r\n* Support for SyncTeX on Windows and Mac OS X.\r\n* New option: vimrplugin_latexmk","package":"Vim-R-plugin.vmb","4":"Vim-R-plugin.vmb","src_id":"22808","5":"22808","creation_date":"1421614715","6":"1421614715"},{"0":"2628","vim_version":"7.4","1":"7.4","script_version":"1.1","2":"1.1","version_comment":"* Version update for Linux\/Unix only. May not work on Windows or Mac.\r\n* Minor bug fixes.\r\n* The option vimrplugin_assign now accepts the values 0, 1 and 2.\r\n* SyncTeX support (Evince, Okular and Zathura):\r\n   - New options: vimrplugin_synctex and vimrplugin_vim_window.\r\n   - Deprecated option: vimrplugin_openpdf_quietly","3":"* Version update for Linux\/Unix only. May not work on Windows or Mac.\r\n* Minor bug fixes.\r\n* The option vimrplugin_assign now accepts the values 0, 1 and 2.\r\n* SyncTeX support (Evince, Okular and Zathura):\r\n   - New options: vimrplugin_synctex and vimrplugin_vim_window.\r\n   - Deprecated option: vimrplugin_openpdf_quietly","package":"Vim-R-plugin.vmb","4":"Vim-R-plugin.vmb","src_id":"22615","5":"22615","creation_date":"1415935956","6":"1415935956"},{"0":"2628","vim_version":"7.4","1":"7.4","script_version":"1.0","2":"1.0","version_comment":" * The package now depends on vimcom (which is fully featured and is no longer on CRAN).\r\n * Neovim support.\r\n * vimrplugin_openpdf now accepts three values: 0, 1 and 2.\r\n * New command \\o evaluates current line in R and inserts the output in the script.\r\n * New options: vimrplugin_vimcom_wait, vimrplugin_vim_wd, and vimrplugin_tmux_title.\r\n * Minor bug fixes.","3":" * The package now depends on vimcom (which is fully featured and is no longer on CRAN).\r\n * Neovim support.\r\n * vimrplugin_openpdf now accepts three values: 0, 1 and 2.\r\n * New command \\o evaluates current line in R and inserts the output in the script.\r\n * New options: vimrplugin_vimcom_wait, vimrplugin_vim_wd, and vimrplugin_tmux_title.\r\n * Minor bug fixes.","package":"Vim-R-plugin.vmb","4":"Vim-R-plugin.vmb","src_id":"22118","5":"22118","creation_date":"1404321844","6":"1404321844"},{"0":"2628","vim_version":"7.3","1":"7.3","script_version":"0.9.9.9","2":"0.9.9.9","version_comment":"* Minor bug fixes.\r\n* Delete temporary files on VimLeave event.\r\n* Support to R package slidify (thanks to Michael Lerch).\r\n* New option: vimrplugin_rcomment_string.","3":"* Minor bug fixes.\r\n* Delete temporary files on VimLeave event.\r\n* Support to R package slidify (thanks to Michael Lerch).\r\n* New option: vimrplugin_rcomment_string.","package":"Vim-R-plugin.vmb","4":"Vim-R-plugin.vmb","src_id":"21414","5":"21414","creation_date":"1391268243","6":"1391268243"},{"0":"2628","vim_version":"7.3","1":"7.3","script_version":"0.9.9.8","2":"0.9.9.8","version_comment":" * The list of objects for omnicompletion and the list of functions for syntax highlight now are built dynamically. Deprecated commands and options: :RUpdateObjList, :RAddLibToList, vimrplugin_buildwait. New option: vimrplugin_permanent_libs.\r\n * New options: vimrplugin_show_args.\r\n * New command \\ch: send to R Console all R code from the first chunk up to this line.\r\n * Remove toolbar icons (they still may be added back manually by interested users).\r\n * If latexmk is installed, use it by default to compile the pdf.","3":" * The list of objects for omnicompletion and the list of functions for syntax highlight now are built dynamically. Deprecated commands and options: :RUpdateObjList, :RAddLibToList, vimrplugin_buildwait. New option: vimrplugin_permanent_libs.\r\n * New options: vimrplugin_show_args.\r\n * New command \\ch: send to R Console all R code from the first chunk up to this line.\r\n * Remove toolbar icons (they still may be added back manually by interested users).\r\n * If latexmk is installed, use it by default to compile the pdf.","package":"Vim-R-plugin.vmb","4":"Vim-R-plugin.vmb","src_id":"21131","5":"21131","creation_date":"1385809958","6":"1385809958"},{"0":"2628","vim_version":"7.3","1":"7.3","script_version":"0.9.9.7","2":"0.9.9.7","version_comment":"* Minor bug fixes.","3":"* Minor bug fixes.","package":"vim-r-plugin-0.9.9.7.zip","4":"vim-r-plugin-0.9.9.7.zip","src_id":"20996","5":"20996","creation_date":"1383442672","6":"1383442672"},{"0":"2628","vim_version":"7.3","1":"7.3","script_version":"0.9.9.6","2":"0.9.9.6","version_comment":"* Minor bug fixes.","3":"* Minor bug fixes.","package":"vim-r-plugin-0.9.9.6.zip","4":"vim-r-plugin-0.9.9.6.zip","src_id":"20986","5":"20986","creation_date":"1383221073","6":"1383221073"},{"0":"2628","vim_version":"7.0","1":"7.0","script_version":"0.9.9.5","2":"0.9.9.5","version_comment":"* Minor bug fixes.","3":"* Minor bug fixes.","package":"vim-r-plugin-0.9.9.5.zip","4":"vim-r-plugin-0.9.9.5.zip","src_id":"20916","5":"20916","creation_date":"1381602207","6":"1381602207"},{"0":"2628","vim_version":"7.3","1":"7.3","script_version":"0.9.9.4","2":"0.9.9.4","version_comment":"* The package now depends on vimcom.plus.\r\n* The support to GNU Screen, VimShell and Conque Shell was dropped. The screen plugin no longer is used.\r\n* The delete command was removed from the Object Browser.\r\n* New options: vimrplugin_vsplit, vimrplugin_rconsole_height and vimrplugin_rconsole_width.\r\n* New option: vimrplugin_restart.\r\n* Show elements of S4 objects in the Object Browser.","3":"* The package now depends on vimcom.plus.\r\n* The support to GNU Screen, VimShell and Conque Shell was dropped. The screen plugin no longer is used.\r\n* The delete command was removed from the Object Browser.\r\n* New options: vimrplugin_vsplit, vimrplugin_rconsole_height and vimrplugin_rconsole_width.\r\n* New option: vimrplugin_restart.\r\n* Show elements of S4 objects in the Object Browser.","package":"vim-r-plugin-0.9.9.4.zip","4":"vim-r-plugin-0.9.9.4.zip","src_id":"20838","5":"20838","creation_date":"1380025683","6":"1380025683"},{"0":"2628","vim_version":"7.3","1":"7.3","script_version":"0.9.9.3","2":"0.9.9.3","version_comment":"* New option: vimrplugin_source.\r\n* Minor bug fixes.","3":"* New option: vimrplugin_source.\r\n* Minor bug fixes.","package":"vim-r-plugin-0.9.9.3.zip","4":"vim-r-plugin-0.9.9.3.zip","src_id":"19802","5":"19802","creation_date":"1365680315","6":"1365680315"},{"0":"2628","vim_version":"7.3","1":"7.3","script_version":"0.9.9.2","2":"0.9.9.2","version_comment":"* Update vimcom version requirement to 0.9-7 (fix incompatibility with tcltk package on Unix).\r\n* Change the default value of vimrplugin_rmhidden to 0.\r\n* New option for Windows: vimrplugin_Rterm.\r\n* New simpler un\/comment commands: <LocalLeader>xc and <LocalLeader>xu.\r\n* Remove options vimrplugin_nosingler and vimrplugin_by_vim_instance.","3":"* Update vimcom version requirement to 0.9-7 (fix incompatibility with tcltk package on Unix).\r\n* Change the default value of vimrplugin_rmhidden to 0.\r\n* New option for Windows: vimrplugin_Rterm.\r\n* New simpler un\/comment commands: <LocalLeader>xc and <LocalLeader>xu.\r\n* Remove options vimrplugin_nosingler and vimrplugin_by_vim_instance.","package":"vim-r-plugin-0.9.9.2.zip","4":"vim-r-plugin-0.9.9.2.zip","src_id":"19461","5":"19461","creation_date":"1359753531","6":"1359753531"},{"0":"2628","vim_version":"7.3","1":"7.3","script_version":"0.9.9.1","2":"0.9.9.1","version_comment":"* Enable mouse on Tmux again.","3":"* Enable mouse on Tmux again.","package":"vim-r-plugin-0.9.9.1.zip","4":"vim-r-plugin-0.9.9.1.zip","src_id":"19164","5":"19164","creation_date":"1355241516","6":"1355241516"},{"0":"2628","vim_version":"7.3","1":"7.3","script_version":"0.9.9","2":"0.9.9","version_comment":"* New commands:  :Rinsert  and  :Rformat.\r\n* Automatically update the Object Browser in GVim.\r\n* On MS Windows, don't raise the R Console before sending CTRL-V to it.\r\n* Search for vimcom in both IPv4 and IPv6 ports (thanks to Z\u00c3\u00a9 Loff for writing the patch).","3":"* New commands:  :Rinsert  and  :Rformat.\r\n* Automatically update the Object Browser in GVim.\r\n* On MS Windows, don't raise the R Console before sending CTRL-V to it.\r\n* Search for vimcom in both IPv4 and IPv6 ports (thanks to Z\u00c3\u00a9 Loff for writing the patch).","package":"vim-r-plugin-0.9.9.zip","4":"vim-r-plugin-0.9.9.zip","src_id":"19097","5":"19097","creation_date":"1354581218","6":"1354581218"},{"0":"2628","vim_version":"7.3","1":"7.3","script_version":"0.9.8","2":"0.9.8","version_comment":"* Open PDF automatically after processing Rnoweb file if vimrplugin_openpdf = 1 (thanks to Tomaz Ficko for suggesting the feature). Open it quietly if vimrplugin_openpdf_quietly = 1. Open it manually with \\op.\r\n * Open HTML automatically after processing either Rmd or Rrst file if vimrplugin_openhtml = 1. Generate strict rst code if vimrplugin_strict_rst = 1.\r\n * Remove option vimrplugin_knitargs.\r\n * Start last R if there is more than one installed on Windows (thanks to Alex Zvoleff for reporting the bug and writing the patch).\r\n * Alex Zvoleff added support to Rrst file type.\r\n * michelk added support to Rmd file type.\r\n * For Rnoweb, Rmd and Rrst file types, CTRL-X CTRL-A completes knitr chunk options if the cursor is inside the chunk header.\r\n * New option: vimrplugin_rmhidden.\r\n * New option: vimrplugin_insert_mode_cmds (thanks to Charles R. Hogg III).\r\n * New command  :RAddLibToList  to add the objects of specific libraries to omnicompletion.\r\n * Thanks to genrich and NagatoPain for other bug fixes and code improvements.\r\n * New option: vimrplugin_assign_map. The option vimrplugin_underscore was renamed to vimrplugin_assign","3":"* Open PDF automatically after processing Rnoweb file if vimrplugin_openpdf = 1 (thanks to Tomaz Ficko for suggesting the feature). Open it quietly if vimrplugin_openpdf_quietly = 1. Open it manually with \\op.\r\n * Open HTML automatically after processing either Rmd or Rrst file if vimrplugin_openhtml = 1. Generate strict rst code if vimrplugin_strict_rst = 1.\r\n * Remove option vimrplugin_knitargs.\r\n * Start last R if there is more than one installed on Windows (thanks to Alex Zvoleff for reporting the bug and writing the patch).\r\n * Alex Zvoleff added support to Rrst file type.\r\n * michelk added support to Rmd file type.\r\n * For Rnoweb, Rmd and Rrst file types, CTRL-X CTRL-A completes knitr chunk options if the cursor is inside the chunk header.\r\n * New option: vimrplugin_rmhidden.\r\n * New option: vimrplugin_insert_mode_cmds (thanks to Charles R. Hogg III).\r\n * New command  :RAddLibToList  to add the objects of specific libraries to omnicompletion.\r\n * Thanks to genrich and NagatoPain for other bug fixes and code improvements.\r\n * New option: vimrplugin_assign_map. The option vimrplugin_underscore was renamed to vimrplugin_assign","package":"vim-r-plugin-0.9.8.zip","4":"vim-r-plugin-0.9.8.zip","src_id":"18795","5":"18795","creation_date":"1350139037","6":"1350139037"},{"0":"2628","vim_version":"7.3","1":"7.3","script_version":"0.9.7","2":"0.9.7","version_comment":" * Use the R package vimcom:\r\n     - Automatic update of the Object Browser when running R in a Tmux session.\r\n     - The following options are now set on the vimcom R: allnames, open_df, and open_list.\r\n     - New command in normal and visual modes when on the Object Browser: \"d\" deletes objects and detach libraries.\r\n     - New option: vimrplugin_ob_sleep.\r\n * New option, vimrplugin_external_ob, to open the Object Browser in a Tmux pane in the external terminal running R.\r\n * New command  :Rhelp (thanks for Nir Atias for suggesting the new feature).\r\n * Remove the command  :RUpdateObjListAll  because Vim may not load the syntax file if it is too big.\r\n * Add support to knitr package.\r\n * New command  :RSourceDir.\r\n * New key bindings \\r<Left> and \\r<Right>.\r\n * Correctly send selected blocks.\r\n","3":" * Use the R package vimcom:\r\n     - Automatic update of the Object Browser when running R in a Tmux session.\r\n     - The following options are now set on the vimcom R: allnames, open_df, and open_list.\r\n     - New command in normal and visual modes when on the Object Browser: \"d\" deletes objects and detach libraries.\r\n     - New option: vimrplugin_ob_sleep.\r\n * New option, vimrplugin_external_ob, to open the Object Browser in a Tmux pane in the external terminal running R.\r\n * New command  :Rhelp (thanks for Nir Atias for suggesting the new feature).\r\n * Remove the command  :RUpdateObjListAll  because Vim may not load the syntax file if it is too big.\r\n * Add support to knitr package.\r\n * New command  :RSourceDir.\r\n * New key bindings \\r<Left> and \\r<Right>.\r\n * Correctly send selected blocks.\r\n","package":"vim-r-plugin-0.9.7.zip","4":"vim-r-plugin-0.9.7.zip","src_id":"17871","5":"17871","creation_date":"1336178022","6":"1336178022"},{"0":"2628","vim_version":"7.3","1":"7.3","script_version":"0.9.6","2":"0.9.6","version_comment":"* Fix path to R source() command on Windows.\r\n* New default value of vimrplugin_vimpager = \"tab\".\r\n* New default value of vimrplugin_objbr_place = \"editor,right\"\r\n* Autocompletion of function arguments with <C-X><C-A>.","3":"* Fix path to R source() command on Windows.\r\n* New default value of vimrplugin_vimpager = \"tab\".\r\n* New default value of vimrplugin_objbr_place = \"editor,right\"\r\n* Autocompletion of function arguments with <C-X><C-A>.","package":"vim-r-plugin-0.9.6.zip","4":"vim-r-plugin-0.9.6.zip","src_id":"17059","5":"17059","creation_date":"1323817925","6":"1323817925"},{"0":"2628","vim_version":"7.3","1":"7.3","script_version":"0.9.5","2":"0.9.5","version_comment":"* Changed the way that blocks are sent to R.\r\n* Added \"terminal\" to the list of known terminal emulators (thanks for \"i5m\" for the patch).\r\n* Use Tmux to start the Object Browser beside the R console if vimrplugin_objbr_place =~ \"console\".","3":"* Changed the way that blocks are sent to R.\r\n* Added \"terminal\" to the list of known terminal emulators (thanks for \"i5m\" for the patch).\r\n* Use Tmux to start the Object Browser beside the R console if vimrplugin_objbr_place =~ \"console\".","package":"vim-r-plugin-0.9.5.zip","4":"vim-r-plugin-0.9.5.zip","src_id":"17032","5":"17032","creation_date":"1323278789","6":"1323278789"},{"0":"2628","vim_version":"7.3","1":"7.3","script_version":"111114","2":"111114","version_comment":"* Changed key binding for commenting\/uncommenting code from \\cc to \\xx.\r\n* Added function SendChunkToR() and its corresponding key bindings: \\cc, \\ce, \\cd and \\ca (thanks to Xavier Fern\u00c3\u00a1ndez i Mar\u00c3\u00adn for suggesting the feature).\r\n* New option (vimrplugin_ca_ck) was created to fix bug reported by Xavier Fern\u00c3\u00a1ndez i Mar\u00c3\u00adn: spurious ^A^K being added to lines sent to R.\r\n* Don't blink the menu and toolbar buttons when doing omni completion.\r\n* Use Tmux to run R in an external terminal emulator.\r\n","3":"* Changed key binding for commenting\/uncommenting code from \\cc to \\xx.\r\n* Added function SendChunkToR() and its corresponding key bindings: \\cc, \\ce, \\cd and \\ca (thanks to Xavier Fern\u00c3\u00a1ndez i Mar\u00c3\u00adn for suggesting the feature).\r\n* New option (vimrplugin_ca_ck) was created to fix bug reported by Xavier Fern\u00c3\u00a1ndez i Mar\u00c3\u00adn: spurious ^A^K being added to lines sent to R.\r\n* Don't blink the menu and toolbar buttons when doing omni completion.\r\n* Use Tmux to run R in an external terminal emulator.\r\n","package":"vim-r-plugin-111114.zip","4":"vim-r-plugin-111114.zip","src_id":"16862","5":"16862","creation_date":"1321275457","6":"1321275457"},{"0":"2628","vim_version":"7.3","1":"7.3","script_version":"111014","2":"111014","version_comment":"Fix bug in function that send commands.","3":"Fix bug in function that send commands.","package":"vim-r-plugin-111014.zip","4":"vim-r-plugin-111014.zip","src_id":"16673","5":"16673","creation_date":"1318632267","6":"1318632267"},{"0":"2628","vim_version":"7.3","1":"7.3","script_version":"111014","2":"111014","version_comment":"* Fixed spell check bug in R documentation files (.Rd).\r\n* Fixed beep bug when sending commands to R.\r\n* New option: vimrplugin_notmuxconf.\r\n* Fixed bug when starting tmux before vim: the environment variable VIMRPLUGIN_TMPDIR was not being set. Thanks to Michel Lang for reporting the bug and helping to track its source, and thanks to Eric Dewoestine for explaining how to fix the bug.\r\n* Fixed bug in code indentation after unbalanced brackets and parenthesis when r_indent_align_args = 0 (thanks to Chris Neff and Peng Yu for reporting the bugs).\r\n* Really make the use of AppleScript the default on OS X (thanks for Jason for reporting the bug).\r\n","3":"* Fixed spell check bug in R documentation files (.Rd).\r\n* Fixed beep bug when sending commands to R.\r\n* New option: vimrplugin_notmuxconf.\r\n* Fixed bug when starting tmux before vim: the environment variable VIMRPLUGIN_TMPDIR was not being set. Thanks to Michel Lang for reporting the bug and helping to track its source, and thanks to Eric Dewoestine for explaining how to fix the bug.\r\n* Fixed bug in code indentation after unbalanced brackets and parenthesis when r_indent_align_args = 0 (thanks to Chris Neff and Peng Yu for reporting the bugs).\r\n* Really make the use of AppleScript the default on OS X (thanks for Jason for reporting the bug).\r\n","package":"vim-r-plugin-111014.zip","4":"vim-r-plugin-111014.zip","src_id":"16671","5":"16671","creation_date":"1318608202","6":"1318608202"},{"0":"2628","vim_version":"7.3","1":"7.3","script_version":"110805","2":"110805","version_comment":"* New option: vimrplugin_tmux.\r\n* Set Tmux as the default instead of either GNU Screen or Conque Shell.\r\n* Document Tmux as the preferred way of running the plugin on Linux.\r\n* Vim-LaTeX-suite plugin can be used with Rnoweb files without any additional configuration. The necessary code was added to the ftplugin\/rnoweb.vim.\r\n* Added count argument to normal mode commands gn and gN (thanks to Ivan Bezerra for the suggestion).\r\n","3":"* New option: vimrplugin_tmux.\r\n* Set Tmux as the default instead of either GNU Screen or Conque Shell.\r\n* Document Tmux as the preferred way of running the plugin on Linux.\r\n* Vim-LaTeX-suite plugin can be used with Rnoweb files without any additional configuration. The necessary code was added to the ftplugin\/rnoweb.vim.\r\n* Added count argument to normal mode commands gn and gN (thanks to Ivan Bezerra for the suggestion).\r\n","package":"vim-r-plugin-110805.zip","4":"vim-r-plugin-110805.zip","src_id":"16200","5":"16200","creation_date":"1312543349","6":"1312543349"},{"0":"2628","vim_version":"7.3","1":"7.3","script_version":"110614","2":"110614","version_comment":"* When doing the command \\rh, the plugin tries to show the help for the method corresponding to the class of the object passed as argument to the function. The same with \\rp (thanks to Thomas Scheike for suggesting the feature).\r\n* Removed scipt rpager.sh.\r\n* Added script global_r_plugin.vim to allow the use of the plugin with any file type.","3":"* When doing the command \\rh, the plugin tries to show the help for the method corresponding to the class of the object passed as argument to the function. The same with \\rp (thanks to Thomas Scheike for suggesting the feature).\r\n* Removed scipt rpager.sh.\r\n* Added script global_r_plugin.vim to allow the use of the plugin with any file type.","package":"vim-r-plugin-110614.zip","4":"vim-r-plugin-110614.zip","src_id":"15883","5":"15883","creation_date":"1308051224","6":"1308051224"},{"0":"2628","vim_version":"7.3","1":"7.3","script_version":"110222","2":"110222","version_comment":"* Added syntax\/rhelp.vim.\r\n* New command for rnoweb files: BibTeX current file (\\sb).\r\n* New commands for the object browser: open visible lists (\\r=) and close visible lists (\\r-).\r\n* Reorganization of the GUI menu.","3":"* Added syntax\/rhelp.vim.\r\n* New command for rnoweb files: BibTeX current file (\\sb).\r\n* New commands for the object browser: open visible lists (\\r=) and close visible lists (\\r-).\r\n* Reorganization of the GUI menu.","package":"vim-r-plugin-110222.zip","4":"vim-r-plugin-110222.zip","src_id":"15089","5":"15089","creation_date":"1298417066","6":"1298417066"},{"0":"2628","vim_version":"7.3","1":"7.3","script_version":"110208","2":"110208","version_comment":"* Fixed bug in \"else if\" constructions (thanks to Dan Kelley for reporting the bug).\r\n* Support for commenting\/uncommenting lines.","3":"* Fixed bug in \"else if\" constructions (thanks to Dan Kelley for reporting the bug).\r\n* Support for commenting\/uncommenting lines.","package":"vim-r-plugin-110208.zip","4":"vim-r-plugin-110208.zip","src_id":"14985","5":"14985","creation_date":"1297171119","6":"1297171119"},{"0":"2628","vim_version":"7.3","1":"7.3","script_version":"110203","2":"110203","version_comment":"* Fixed bug in  :RUpdateObjList  when the function arguments included S4 objects (thanks to Gerhard Sch\u00c3\u00b6fl for reporting the bug).\r\n* Improvements in indentation of R code (thanks to Dan Kelley for finding and reporting indentation bugs and testing many versions of indent\/r.vim).\r\n* New indentation options: r_indent_align_args, r_indent_ess_comments, r_indent_comment_column, and r_indent_ess_compatible.\r\n* New file: indent\/rhelp.vim.\r\n","3":"* Fixed bug in  :RUpdateObjList  when the function arguments included S4 objects (thanks to Gerhard Sch\u00c3\u00b6fl for reporting the bug).\r\n* Improvements in indentation of R code (thanks to Dan Kelley for finding and reporting indentation bugs and testing many versions of indent\/r.vim).\r\n* New indentation options: r_indent_align_args, r_indent_ess_comments, r_indent_comment_column, and r_indent_ess_compatible.\r\n* New file: indent\/rhelp.vim.\r\n","package":"vim-r-plugin-110203.zip","4":"vim-r-plugin-110203.zip","src_id":"14950","5":"14950","creation_date":"1296776381","6":"1296776381"},{"0":"2628","vim_version":"7.3","1":"7.3","script_version":"110117","2":"110117","version_comment":"* Fixed indentation bug in Rnoweb files (thanks to Dan Kelley for reporting the bug).","3":"* Fixed indentation bug in Rnoweb files (thanks to Dan Kelley for reporting the bug).","package":"vim-r-plugin-110117.zip","4":"vim-r-plugin-110117.zip","src_id":"14770","5":"14770","creation_date":"1295265023","6":"1295265023"},{"0":"2628","vim_version":"7.3","1":"7.3","script_version":"101217","2":"101217","version_comment":"* Renamed the function SendCmdToScreen to SendCmdToR.\r\n* Clear the current line in the R console before sending a new line.\r\n* Always starts R on the script's directory.\r\n* Don't send \"^@$\" as part of a paragraph in rnoweb files (thanks to Fabio Correa for reporting the bug).\r\n* More useful warning message when PyWin32 isn't installed.\r\n* Initial support to Apple Script on Mac OS X (thanks to Vincent Nijs for writing and testing the code).","3":"* Renamed the function SendCmdToScreen to SendCmdToR.\r\n* Clear the current line in the R console before sending a new line.\r\n* Always starts R on the script's directory.\r\n* Don't send \"^@$\" as part of a paragraph in rnoweb files (thanks to Fabio Correa for reporting the bug).\r\n* More useful warning message when PyWin32 isn't installed.\r\n* Initial support to Apple Script on Mac OS X (thanks to Vincent Nijs for writing and testing the code).","package":"vim-r-plugin-101217.zip","4":"vim-r-plugin-101217.zip","src_id":"14550","5":"14550","creation_date":"1292619509","6":"1292619509"},{"0":"2628","vim_version":"7.3","1":"7.3","script_version":"101121","2":"101121","version_comment":"* Fix for when whoami returns domain name on Windows (thanks to \"Si\" for fixing the bug).\r\n","3":"* Fix for when whoami returns domain name on Windows (thanks to \"Si\" for fixing the bug).\r\n","package":"vim-r-plugin-101121.zip","4":"vim-r-plugin-101121.zip","src_id":"14337","5":"14337","creation_date":"1290341200","6":"1290341200"},{"0":"2628","vim_version":"7.3","1":"7.3","script_version":"101118","2":"101118","version_comment":"* New command:  :RUpdateObjListAll.\r\n* New option: vimrplugin_allnames.\r\n* Allow the use of Python 3.1 on Windows.\r\n* Minor improvements in indentation of R code.\r\n* The file r-plugin\/omni_list was renamed to r-plugin\/omniList because its field separator changed to \";\".\r\n* Fixed bug that was causing ^H to be exhibited in the R documentation in some systems. (Thanks to Helge Liebert for reporting the problem).\r\n","3":"* New command:  :RUpdateObjListAll.\r\n* New option: vimrplugin_allnames.\r\n* Allow the use of Python 3.1 on Windows.\r\n* Minor improvements in indentation of R code.\r\n* The file r-plugin\/omni_list was renamed to r-plugin\/omniList because its field separator changed to \";\".\r\n* Fixed bug that was causing ^H to be exhibited in the R documentation in some systems. (Thanks to Helge Liebert for reporting the problem).\r\n","package":"vim-r-plugin-101118.zip","4":"vim-r-plugin-101118.zip","src_id":"14296","5":"14296","creation_date":"1290073464","6":"1290073464"},{"0":"2628","vim_version":"7.3","1":"7.3","script_version":"101107","2":"101107","version_comment":"* New feature: complete chunk block when '<' is pressed in rnoweb files.\r\n* New option: vimrplugin_rnowebchunk.\r\n* New key bindings in Normal mode for Rnoweb files: gn (go to next R code chunk) and gN (go to previous R code chunk).\r\n* New command:  :RBuildTags.\r\n* Added fold capability to syntax\/r.vim.\r\n* Improved indentation of rnoweb files: thanks to Johannes Tanzler for writing the tex.vim indent script and for permitting its inclusion in the Vim-R-plugin.\r\n* R CMD BATCH now is called with --no-restore --no-save (key binding \\ro).\r\n* The file r-plugin\/omnilist now has an additional field and was renamed as omni_list.\r\n* Use 64 bit version of R by default on Windows if the directory bin\/x64 exists.\r\n* New Windows only option: vimrplugin_i386.\r\n","3":"* New feature: complete chunk block when '<' is pressed in rnoweb files.\r\n* New option: vimrplugin_rnowebchunk.\r\n* New key bindings in Normal mode for Rnoweb files: gn (go to next R code chunk) and gN (go to previous R code chunk).\r\n* New command:  :RBuildTags.\r\n* Added fold capability to syntax\/r.vim.\r\n* Improved indentation of rnoweb files: thanks to Johannes Tanzler for writing the tex.vim indent script and for permitting its inclusion in the Vim-R-plugin.\r\n* R CMD BATCH now is called with --no-restore --no-save (key binding \\ro).\r\n* The file r-plugin\/omnilist now has an additional field and was renamed as omni_list.\r\n* Use 64 bit version of R by default on Windows if the directory bin\/x64 exists.\r\n* New Windows only option: vimrplugin_i386.\r\n","package":"vim-r-plugin-101107.zip","4":"vim-r-plugin-101107.zip","src_id":"14203","5":"14203","creation_date":"1289147785","6":"1289147785"},{"0":"2628","vim_version":"7.3","1":"7.3","script_version":"101025","2":"101025","version_comment":"* New option: vimrplugin_routmorecolors.\r\n* Fixed bug in the object browser when a data.frame or list had just one element (thanks to Jan Larres for reporting the bug).\r\n* Do not copy omnilist and functions.vim to ~\/.vim\/r-plugin if the directory where the plugin is installed is writable (thanks to Jan Larres for the suggestion).","3":"* New option: vimrplugin_routmorecolors.\r\n* Fixed bug in the object browser when a data.frame or list had just one element (thanks to Jan Larres for reporting the bug).\r\n* Do not copy omnilist and functions.vim to ~\/.vim\/r-plugin if the directory where the plugin is installed is writable (thanks to Jan Larres for the suggestion).","package":"vim-r-plugin-101025.zip","4":"vim-r-plugin-101025.zip","src_id":"14115","5":"14115","creation_date":"1288010614","6":"1288010614"},{"0":"2628","vim_version":"7.3","1":"7.3","script_version":"101023","2":"101023","version_comment":"* New options: vimrplugin_objbr_place and vimrplugin_objbr_w.\r\n* New default value: vimrplugin_vimpager = \"vertical\"\r\n* The R help can now be seen in a Vim buffer on MS Windows.\r\n* Fix width of help text when R version >= 2.12.0.\r\n* Implemented actions in the object browser: summary, print, etc...\r\n* Browse libraries objects in object browser.","3":"* New options: vimrplugin_objbr_place and vimrplugin_objbr_w.\r\n* New default value: vimrplugin_vimpager = \"vertical\"\r\n* The R help can now be seen in a Vim buffer on MS Windows.\r\n* Fix width of help text when R version >= 2.12.0.\r\n* Implemented actions in the object browser: summary, print, etc...\r\n* Browse libraries objects in object browser.","package":"vim-r-plugin2-101023.zip","4":"vim-r-plugin2-101023.zip","src_id":"14103","5":"14103","creation_date":"1287866126","6":"1287866126"},{"0":"2628","vim_version":"7.3","1":"7.3","script_version":"101016","2":"101016","version_comment":"* Minor bug fixes in the object browser.","3":"* Minor bug fixes in the object browser.","package":"vim-r-plugin2-101016.zip","4":"vim-r-plugin2-101016.zip","src_id":"14066","5":"14066","creation_date":"1287267687","6":"1287267687"},{"0":"2628","vim_version":"7.3","1":"7.3","script_version":"101015","2":"101015","version_comment":"* New feature: Object browser.\r\n* Conque Shell will be used if installed unless explicitly told otherwise in the vimrc.\r\n* New valid value for vimrplugin_vimpager: \"tabnew\"\r\n\r\n","3":"* New feature: Object browser.\r\n* Conque Shell will be used if installed unless explicitly told otherwise in the vimrc.\r\n* New valid value for vimrplugin_vimpager: \"tabnew\"\r\n\r\n","package":"vim-r-plugin2-101015.zip","4":"vim-r-plugin2-101015.zip","src_id":"14061","5":"14061","creation_date":"1287183680","6":"1287183680"},{"0":"2628","vim_version":"7.3","1":"7.3","script_version":"100923","2":"100923","version_comment":"* New option: vimrplugin_vimpager.\r\n* Do not let Vim translate \"File\" in R menu.\r\n* Fixed bug when the option vimrplugin_r_path was used (thanks to Asis Hallab for reporting the bug),\r\n* Fixed bug (E687) when user created custom key binding (thanks to Philippe Glaziou for reporting the bug).\r\n","3":"* New option: vimrplugin_vimpager.\r\n* Do not let Vim translate \"File\" in R menu.\r\n* Fixed bug when the option vimrplugin_r_path was used (thanks to Asis Hallab for reporting the bug),\r\n* Fixed bug (E687) when user created custom key binding (thanks to Philippe Glaziou for reporting the bug).\r\n","package":"vim-r-plugin2-100923.zip","4":"vim-r-plugin2-100923.zip","src_id":"13892","5":"13892","creation_date":"1285240310","6":"1285240310"},{"0":"2628","vim_version":"7.3","1":"7.3","script_version":"100917","2":"100917","version_comment":"* Changed the use of vimrplugin_r_path: now the option includes only the directory part of the path.\r\n* Initial support to Conque Shell plugin. Thanks to \"il_principe orange\" for suggesting the use of Conque Shell, \"ZyX-I\" for writing the initial code to use Conque Shell, and Nico Raffo for writing the plugin and additional code to integrate both plugins.\r\n* New options: vimrplugin_conqueplugin and vimrplugin_conquevsplit, vimrplugin_r_args.\r\n* Initial support for Vim-R communication on Windows using Python.\r\n* Fixed bug when the plugin was installed in a directory other than ~\/.vim (thanks to Tom Link).\r\n","3":"* Changed the use of vimrplugin_r_path: now the option includes only the directory part of the path.\r\n* Initial support to Conque Shell plugin. Thanks to \"il_principe orange\" for suggesting the use of Conque Shell, \"ZyX-I\" for writing the initial code to use Conque Shell, and Nico Raffo for writing the plugin and additional code to integrate both plugins.\r\n* New options: vimrplugin_conqueplugin and vimrplugin_conquevsplit, vimrplugin_r_args.\r\n* Initial support for Vim-R communication on Windows using Python.\r\n* Fixed bug when the plugin was installed in a directory other than ~\/.vim (thanks to Tom Link).\r\n","package":"vim-r-plugin2-100917.zip","4":"vim-r-plugin2-100917.zip","src_id":"13850","5":"13850","creation_date":"1284760723","6":"1284760723"},{"0":"2628","vim_version":"7.3","1":"7.3","script_version":"100825","2":"100825","version_comment":"* Minor improvements in syntax highlighting.\r\n* New option: vimrplugin_buildwait.\r\n* New option: vimrplugin_r_path (thanks to Asis Hallab).","3":"* Minor improvements in syntax highlighting.\r\n* New option: vimrplugin_buildwait.\r\n* New option: vimrplugin_r_path (thanks to Asis Hallab).","package":"vim-r-plugin2-100825.zip","4":"vim-r-plugin2-100825.zip","src_id":"13672","5":"13672","creation_date":"1282735158","6":"1282735158"},{"0":"2628","vim_version":"7.0","1":"7.0","script_version":"100803","2":"100803","version_comment":"* Fixed bug in .Rsource name making in some systems.","3":"* Fixed bug in .Rsource name making in some systems.","package":"vim-r-plugin2-100803.zip","4":"vim-r-plugin2-100803.zip","src_id":"13467","5":"13467","creation_date":"1280845898","6":"1280845898"},{"0":"2628","vim_version":"7.0","1":"7.0","script_version":"100801","2":"100801","version_comment":"* Dropped options vimrplugin_hstart and vimrplugin_browser_time.\r\n* If ~\/.vim\/r-plugin\/functions.vim is not found, try to copy it from  \/usr\/share\/vim\/addons\/r-plugin\/functions.vim.\r\n* Minor bug fixes.\r\n","3":"* Dropped options vimrplugin_hstart and vimrplugin_browser_time.\r\n* If ~\/.vim\/r-plugin\/functions.vim is not found, try to copy it from  \/usr\/share\/vim\/addons\/r-plugin\/functions.vim.\r\n* Minor bug fixes.\r\n","package":"vim-r-plugin2-100801.zip","4":"vim-r-plugin2-100801.zip","src_id":"13452","5":"13452","creation_date":"1280666900","6":"1280666900"},{"0":"2628","vim_version":"7.0","1":"7.0","script_version":"100730","2":"100730","version_comment":"* Added menu item and key binding for run \"R CMD BATCH\" and open the resulting \".Rout\" file.\r\n * Fixed bug when more than one Vim instance used the same file to send multiple lines of code to R (thanks to Bart for reporting the bug).","3":"* Added menu item and key binding for run \"R CMD BATCH\" and open the resulting \".Rout\" file.\r\n * Fixed bug when more than one Vim instance used the same file to send multiple lines of code to R (thanks to Bart for reporting the bug).","package":"vim-r-plugin2-100730.zip","4":"vim-r-plugin2-100730.zip","src_id":"13444","5":"13444","creation_date":"1280539740","6":"1280539740"},{"0":"2628","vim_version":"7.0","1":"7.0","script_version":"100728","2":"100728","version_comment":"* Adapted the code to build a Debian package.","3":"* Adapted the code to build a Debian package.","package":"vim-r-plugin2-100728.zip","4":"vim-r-plugin2-100728.zip","src_id":"13423","5":"13423","creation_date":"1280361319","6":"1280361319"},{"0":"2628","vim_version":"7.0","1":"7.0","script_version":"100719","2":"100719","version_comment":"* Renamed the directory \"tools\" and some files.\r\n* Added options vimrplugin_listmethods and vimrplugin_specialplot.\r\n* Improved syntax highlight of R batch output (.Rout files).\r\n* No longer uses the external programs grep, awk and sed to build the additional syntax file containing the list of functions.","3":"* Renamed the directory \"tools\" and some files.\r\n* Added options vimrplugin_listmethods and vimrplugin_specialplot.\r\n* Improved syntax highlight of R batch output (.Rout files).\r\n* No longer uses the external programs grep, awk and sed to build the additional syntax file containing the list of functions.","package":"vim-r-plugin2-100719.zip","4":"vim-r-plugin2-100719.zip","src_id":"13353","5":"13353","creation_date":"1279567392","6":"1279567392"},{"0":"2628","vim_version":"7.0","1":"7.0","script_version":"100710","2":"100710","version_comment":"* Fixed :RUpdateObjList bug when list had length 0.","3":"* Fixed :RUpdateObjList bug when list had length 0.","package":"vim-r-plugin2-100710.tar.gz","4":"vim-r-plugin2-100710.tar.gz","src_id":"13317","5":"13317","creation_date":"1278796842","6":"1278796842"},{"0":"2628","vim_version":"7.0","1":"7.0","script_version":"100707","2":"100707","version_comment":" * Fixed 'E329: No menu \"R\"' when more than one file were loaded simultaneously by calling vim with either -p or -o parameters. Thanks to Peng Yu for reporting the bug.\r\n * Correctly recognize a newly created file with extension \".R\" as an R script file.\r\n","3":" * Fixed 'E329: No menu \"R\"' when more than one file were loaded simultaneously by calling vim with either -p or -o parameters. Thanks to Peng Yu for reporting the bug.\r\n * Correctly recognize a newly created file with extension \".R\" as an R script file.\r\n","package":"vim-r-plugin2-100707.tar.gz","4":"vim-r-plugin2-100707.tar.gz","src_id":"13306","5":"13306","creation_date":"1278543312","6":"1278543312"},{"0":"2628","vim_version":"7.0","1":"7.0","script_version":"100521","2":"100521","version_comment":"* Replaced \"-t\" with \"--title\" to make xfce4-terminal work again.","3":"* Replaced \"-t\" with \"--title\" to make xfce4-terminal work again.","package":"vim-r-plugin2-100521.tar.gz","4":"vim-r-plugin2-100521.tar.gz","src_id":"13040","5":"13040","creation_date":"1274448366","6":"1274448366"},{"0":"2628","vim_version":"7.0","1":"7.0","script_version":"100512","2":"100512","version_comment":"* Thanks to Tortonesi Mauro who wrote a patch to make the plugin work with pathogen.vim.\r\n* Added simple syntax hightlight for .Rout files.\r\n* Increased the time limit of RUpdateObjList to two minutes.\r\n* Improvement in the syntax highlight based on code written by Zhuojun Chen.\r\n* Thanks to Scott Kostyshak who helped to improve the documentation.\r\n* Iago Mosqueira suggested that the plugin should be able to run one R process for each Vim instance, and his suggestion was implemented with the option g:vimrplugin_by_vim_instance.\r\n","3":"* Thanks to Tortonesi Mauro who wrote a patch to make the plugin work with pathogen.vim.\r\n* Added simple syntax hightlight for .Rout files.\r\n* Increased the time limit of RUpdateObjList to two minutes.\r\n* Improvement in the syntax highlight based on code written by Zhuojun Chen.\r\n* Thanks to Scott Kostyshak who helped to improve the documentation.\r\n* Iago Mosqueira suggested that the plugin should be able to run one R process for each Vim instance, and his suggestion was implemented with the option g:vimrplugin_by_vim_instance.\r\n","package":"vim-r-plugin2-100512.tar.gz","4":"vim-r-plugin2-100512.tar.gz","src_id":"12991","5":"12991","creation_date":"1273664684","6":"1273664684"},{"0":"2628","vim_version":"7.0","1":"7.0","script_version":"091223","2":"091223","version_comment":"* Changes in omni completion: now using two tags files, one for .GlobalEnv and other for all other environments. The command :RUpdateObjList must be used to update the list of objects that are not in .Globalenv. Arguments of functions are displayed in a scratch window.\r\n* Syntax highlight for R functions. The command :RUpdateObjList must be used to update the list of functions to be highlighted.","3":"* Changes in omni completion: now using two tags files, one for .GlobalEnv and other for all other environments. The command :RUpdateObjList must be used to update the list of objects that are not in .Globalenv. Arguments of functions are displayed in a scratch window.\r\n* Syntax highlight for R functions. The command :RUpdateObjList must be used to update the list of functions to be highlighted.","package":"vim-r-plugin2-091223.tar.gz","4":"vim-r-plugin2-091223.tar.gz","src_id":"11943","5":"11943","creation_date":"1261575650","6":"1261575650"},{"0":"2628","vim_version":"7.0","1":"7.0","script_version":"091016","2":"091016","version_comment":"* The plugin now can run together with screen.vim, thanks to Eric Van Dewoestine, the author of screen.vim, who added script integration to screen.vim.\r\n* Andy Choens has made many improvements on the documentation.\r\n* Added the possibility of custom key binding creation to call any R function with the word under cursor as argument.\r\n* The key bindings related with Sweave are activated even if the file type is not rnoweb.\r\n* Replaced <Leader> with <LocalLeader> in the key bindings.\r\n* Added \"Send Paragraph\" commands.","3":"* The plugin now can run together with screen.vim, thanks to Eric Van Dewoestine, the author of screen.vim, who added script integration to screen.vim.\r\n* Andy Choens has made many improvements on the documentation.\r\n* Added the possibility of custom key binding creation to call any R function with the word under cursor as argument.\r\n* The key bindings related with Sweave are activated even if the file type is not rnoweb.\r\n* Replaced <Leader> with <LocalLeader> in the key bindings.\r\n* Added \"Send Paragraph\" commands.","package":"vim-r-plugin2-091016.tar.gz","4":"vim-r-plugin2-091016.tar.gz","src_id":"11535","5":"11535","creation_date":"1255732042","6":"1255732042"},{"0":"2628","vim_version":"7.0","1":"7.0","script_version":"091004","2":"091004","version_comment":"* Jos\u00c3\u00a9 Cl\u00c3\u00a1udio Faria has began to work in the project as co-author.\r\n* Some ideas from Tinn-R project were ported to the plugin.\r\n* The main menu has new items and the toolbar new icons.\r\n* Documentation improvements.","3":"* Jos\u00c3\u00a9 Cl\u00c3\u00a1udio Faria has began to work in the project as co-author.\r\n* Some ideas from Tinn-R project were ported to the plugin.\r\n* The main menu has new items and the toolbar new icons.\r\n* Documentation improvements.","package":"vim-r-plugin2-091004.tar.gz","4":"vim-r-plugin2-091004.tar.gz","src_id":"11484","5":"11484","creation_date":"1254704393","6":"1254704393"},{"0":"2628","vim_version":"7.0","1":"7.0","script_version":"090828","2":"090828","version_comment":" * Faster startup.\r\n * Better support for Rnoweb files: the cursor goes to '^<<' if the sent line is '^@$'.","3":" * Faster startup.\r\n * Better support for Rnoweb files: the cursor goes to '^<<' if the sent line is '^@$'.","package":"vim-r-plugin2-090828.tar.gz","4":"vim-r-plugin2-090828.tar.gz","src_id":"11283","5":"11283","creation_date":"1251485397","6":"1251485397"},{"0":"2628","vim_version":"7.0","1":"7.0","script_version":"090811","2":"090811","version_comment":" * Now use screen instead of funnel.pl. The bugs and limitations related with funnel.pl are solved.\r\n * Deleted key binding for R-devel.\r\n * Automatically detect available terminal emulators and choose one of them.\r\n * By default, no longer calls help.start() the first time that <C-H> is pressed.","3":" * Now use screen instead of funnel.pl. The bugs and limitations related with funnel.pl are solved.\r\n * Deleted key binding for R-devel.\r\n * Automatically detect available terminal emulators and choose one of them.\r\n * By default, no longer calls help.start() the first time that <C-H> is pressed.","package":"vim-r-plugin2-090811.tar.gz","4":"vim-r-plugin2-090811.tar.gz","src_id":"11178","5":"11178","creation_date":"1250044695","6":"1250044695"},{"0":"2628","vim_version":"7.0","1":"7.0","script_version":"090810","2":"090810","version_comment":" * Added R icons for some terminal emulators.\r\n * Removed the script open-gvim-here. You may use Vim's option autochdir.\r\n * Added option g:vimrplugin_term.\r\n * Improved indentation script.\r\n * Changed key binding from <S-Enter>, which doesn't work in any terminal, to <M-Enter>, which at least works in xterm.","3":" * Added R icons for some terminal emulators.\r\n * Removed the script open-gvim-here. You may use Vim's option autochdir.\r\n * Added option g:vimrplugin_term.\r\n * Improved indentation script.\r\n * Changed key binding from <S-Enter>, which doesn't work in any terminal, to <M-Enter>, which at least works in xterm.","package":"vim-r-plugin2-090810.tar.gz","4":"vim-r-plugin2-090810.tar.gz","src_id":"11169","5":"11169","creation_date":"1249902891","6":"1249902891"},{"0":"2628","vim_version":"7.0","1":"7.0","script_version":"090610","2":"090610","version_comment":"The options expandtab, shiftwidth and tabstop are no longer set by the plugin. Better word detection before calling R's help(). Fixed bug in underscore replacement. Fixed small bug in code indentation. Added scipt rpager.sh. Added two new plugin options: no underscore replacement and fixed name for the pipe file instead of random one.","3":"The options expandtab, shiftwidth and tabstop are no longer set by the plugin. Better word detection before calling R's help(). Fixed bug in underscore replacement. Fixed small bug in code indentation. Added scipt rpager.sh. Added two new plugin options: no underscore replacement and fixed name for the pipe file instead of random one.","package":"vim-r-plugin2-090610.tar.gz","4":"vim-r-plugin2-090610.tar.gz","src_id":"10799","5":"10799","creation_date":"1244680710","6":"1244680710"},{"0":"2628","vim_version":"7.0","1":"7.0","script_version":"090523","2":"090523","version_comment":"* Key bindings now are customizable.\r\n* Default key binding for calling R's args() changed to <S-F1>.\r\n* New R script rargs.R gives better results for generic functions than R's args() called directly.","3":"* Key bindings now are customizable.\r\n* Default key binding for calling R's args() changed to <S-F1>.\r\n* New R script rargs.R gives better results for generic functions than R's args() called directly.","package":"vim-r-plugin2-090523.tar.gz","4":"vim-r-plugin2-090523.tar.gz","src_id":"10672","5":"10672","creation_date":"1243121608","6":"1243121608"},{"0":"2628","vim_version":"7.0","1":"7.0","script_version":"090519","2":"090519","version_comment":"* Don't send large blocks of code to R to avoid xterm freezing.\r\n* Automatically call help.start() after <C-H> is pressed for the first time, and wait 4 seconds for the browser start before calling R's help(). These features are customizable.\r\n* Fixed tags file script.","3":"* Don't send large blocks of code to R to avoid xterm freezing.\r\n* Automatically call help.start() after <C-H> is pressed for the first time, and wait 4 seconds for the browser start before calling R's help(). These features are customizable.\r\n* Fixed tags file script.","package":"vim-r-plugin2-090519.tar.gz","4":"vim-r-plugin2-090519.tar.gz","src_id":"10637","5":"10637","creation_date":"1242784299","6":"1242784299"},{"0":"2628","vim_version":"7.0","1":"7.0","script_version":"090516","2":"090516","version_comment":"* Added documentation.\r\n* Added ability to send function to R, revert the automatic convertion of \"_\" into \"<-\" and call R's help().\r\n* Added archive with some files to ease desktop integration, if desired.\r\n","3":"* Added documentation.\r\n* Added ability to send function to R, revert the automatic convertion of \"_\" into \"<-\" and call R's help().\r\n* Added archive with some files to ease desktop integration, if desired.\r\n","package":"vim-r-plugin2-090516.tar.gz","4":"vim-r-plugin2-090516.tar.gz","src_id":"10612","5":"10612","creation_date":"1242477191","6":"1242477191"},{"0":"2628","vim_version":"7.2","1":"7.2","script_version":"090507","2":"090507","version_comment":"Initial upload","3":"Initial upload","package":"vim-r-plugin2-090507.tar.gz","4":"vim-r-plugin2-090507.tar.gz","src_id":"10562","5":"10562","creation_date":"1241807754","6":"1241807754"}]},"2627":{"script_id":"2627","0":"2627","script_name":"exVim","1":"exVim","script_type":"utility","2":"utility","summary":"Turn Vim better than IDE!","3":"Turn Vim better than IDE!","description":"# Sites\r\n\r\nOfficial Page:         http:\/\/exvim.github.io\r\nexVim on Github:   http:\/\/github.com\/exvim\/main\r\n\r\n# Intro\r\n\r\nexVim is a project to turn Vim into a nice programming environment. This project makes you \r\npossible to apply different Vim settings, plugin settings and even plugins by different projects. \r\nIn this way, it makes Vim become the best IDE in the world!\r\n\r\n**WHAT EVEN COOL IS --- WE USE EXVIM DEVELOP EXVIM! (\\\\(-_-)\/)**\r\n\r\n### Features ###\r\n\r\n- Manage your project with `.exvim` setting file.\r\n- Update your project files by single command. (tags, cscope-db, search-index, makefile, ...)\r\n- Project files store in one place (in the folder `.\/.exvim.your_project_name\/` under your project).\r\n- Load Vim-plugin on demand for different projects based on your `.exvim` settings.\r\n- Better management of plugin windows in Vim. (avoid multiple plugin windows mess up in Vim)  \r\n- Browse and operate your project files and folders in project window.\r\n- Class, variable and function tags jumpping.\r\n- Global search in project scope. \r\n- Global search engine customization (user can choose grep, idutils even his own one)\r\n- A powful way to filter your global search result. \r\n- Generate classes hierarchy pictures. \r\n- Enhanced quick-fix window.\r\n- Popular Vim-plugin integrated.\r\n\r\n### How does it work? ###\r\n\r\nBy edit and save your project settings in `your_project_name.exvim` file and open it with Vim, the exVim plugins \r\nwill be loaded.  It will parse the `your_project_name..exvim` file and apply settings for your project after Vim \r\nstarted.\r\n\r\nThe settings include:\r\n\r\n- The window layout of your Vim. (Where to open the plugin window, initial opened window, last time layout...)\r\n- File and Folder filter.\r\n- Plugin you wish to use in the project.\r\n- Plugin settings for the project.\r\n- External tools. Such as grep, idutils, ctags, cscope,...\r\n- External tools settings for the project.\r\n- Your extension settings.\r\n- ...\r\n\r\nexVim also make sure project files store in one place ( in the folder `.\/.exvim.your_project_name\/` under your project ). \r\nThis makes your project clean and much better work with external tools. These project files can be:\r\n\r\n- global search index and results (idutils)\r\n- tags\r\n- cscope files\r\n- hierarchy graph pictures\r\n- error message\r\n- temporary files\r\n- ...\r\n\r\nAfter Vim loaded `your_project_name.exvim` and start, exVim helps you update project files and you are now happy\r\nto use your favor plugins with these files.\r\n\r\n### How do you integrate Vim-plugins? ###\r\n\r\nexVim aims to implement as much as possible of the functions and features in **pure Vim language**. \r\nWe try to avoid reinvent the wheel. As a result, we carefully select and integrate popular Vim-plugins in the world  \r\nfor some of the tasks. For those features lack of or for those features we think we can do it better, \r\nwe develop by ourself in put them in the [exVim organization](https:\/\/github.com\/exvim) on GitHub.\r\n\r\nHere is the standards we pick, patches and develop for a vim-plugin:\r\n\r\n- Develop by pure Vim language\r\n- Follow the unix philosophy: do one thing well \r\n- Less dependencies \r\n- High quality of the code and good performance\r\n- Highly active community\r\n- Can be installed with a variety of plugin managers, Vundle or pathogen. (Repo in GitHub, standard runtime path structure)\r\n\r\n## Repositories in exVim Organization \r\n\r\nThis is the main entry point for exVim project. This repo contains the essential `.vimrc` configuration\r\nfor running exVim.  Other ex-vim-plugins can be found in exVim organization. They are installed by \r\nVundle by `.vimrc` file here. The repository also contains our customized scripts for external tools, and\r\nsome useful shell scripts for developing exVim.\r\n","4":"# Sites\r\n\r\nOfficial Page:         http:\/\/exvim.github.io\r\nexVim on Github:   http:\/\/github.com\/exvim\/main\r\n\r\n# Intro\r\n\r\nexVim is a project to turn Vim into a nice programming environment. This project makes you \r\npossible to apply different Vim settings, plugin settings and even plugins by different projects. \r\nIn this way, it makes Vim become the best IDE in the world!\r\n\r\n**WHAT EVEN COOL IS --- WE USE EXVIM DEVELOP EXVIM! (\\\\(-_-)\/)**\r\n\r\n### Features ###\r\n\r\n- Manage your project with `.exvim` setting file.\r\n- Update your project files by single command. (tags, cscope-db, search-index, makefile, ...)\r\n- Project files store in one place (in the folder `.\/.exvim.your_project_name\/` under your project).\r\n- Load Vim-plugin on demand for different projects based on your `.exvim` settings.\r\n- Better management of plugin windows in Vim. (avoid multiple plugin windows mess up in Vim)  \r\n- Browse and operate your project files and folders in project window.\r\n- Class, variable and function tags jumpping.\r\n- Global search in project scope. \r\n- Global search engine customization (user can choose grep, idutils even his own one)\r\n- A powful way to filter your global search result. \r\n- Generate classes hierarchy pictures. \r\n- Enhanced quick-fix window.\r\n- Popular Vim-plugin integrated.\r\n\r\n### How does it work? ###\r\n\r\nBy edit and save your project settings in `your_project_name.exvim` file and open it with Vim, the exVim plugins \r\nwill be loaded.  It will parse the `your_project_name..exvim` file and apply settings for your project after Vim \r\nstarted.\r\n\r\nThe settings include:\r\n\r\n- The window layout of your Vim. (Where to open the plugin window, initial opened window, last time layout...)\r\n- File and Folder filter.\r\n- Plugin you wish to use in the project.\r\n- Plugin settings for the project.\r\n- External tools. Such as grep, idutils, ctags, cscope,...\r\n- External tools settings for the project.\r\n- Your extension settings.\r\n- ...\r\n\r\nexVim also make sure project files store in one place ( in the folder `.\/.exvim.your_project_name\/` under your project ). \r\nThis makes your project clean and much better work with external tools. These project files can be:\r\n\r\n- global search index and results (idutils)\r\n- tags\r\n- cscope files\r\n- hierarchy graph pictures\r\n- error message\r\n- temporary files\r\n- ...\r\n\r\nAfter Vim loaded `your_project_name.exvim` and start, exVim helps you update project files and you are now happy\r\nto use your favor plugins with these files.\r\n\r\n### How do you integrate Vim-plugins? ###\r\n\r\nexVim aims to implement as much as possible of the functions and features in **pure Vim language**. \r\nWe try to avoid reinvent the wheel. As a result, we carefully select and integrate popular Vim-plugins in the world  \r\nfor some of the tasks. For those features lack of or for those features we think we can do it better, \r\nwe develop by ourself in put them in the [exVim organization](https:\/\/github.com\/exvim) on GitHub.\r\n\r\nHere is the standards we pick, patches and develop for a vim-plugin:\r\n\r\n- Develop by pure Vim language\r\n- Follow the unix philosophy: do one thing well \r\n- Less dependencies \r\n- High quality of the code and good performance\r\n- Highly active community\r\n- Can be installed with a variety of plugin managers, Vundle or pathogen. (Repo in GitHub, standard runtime path structure)\r\n\r\n## Repositories in exVim Organization \r\n\r\nThis is the main entry point for exVim project. This repo contains the essential `.vimrc` configuration\r\nfor running exVim.  Other ex-vim-plugins can be found in exVim organization. They are installed by \r\nVundle by `.vimrc` file here. The repository also contains our customized scripts for external tools, and\r\nsome useful shell scripts for developing exVim.\r\n","install_details":"Install: http:\/\/exvim.github.io\/docs\/install\/\r\nGetting Start: http:\/\/exvim.github.io\/docs\/getting-start\/\r\n\r\n## Requirements\r\n\r\n- Vim 7.3 or higher.\r\n- [Vundle](https:\/\/github.com\/gmarik\/vundle) or [Pathogen](https:\/\/github.com\/tpope\/vim-pathogen)\r\n","5":"Install: http:\/\/exvim.github.io\/docs\/install\/\r\nGetting Start: http:\/\/exvim.github.io\/docs\/getting-start\/\r\n\r\n## Requirements\r\n\r\n- Vim 7.3 or higher.\r\n- [Vundle](https:\/\/github.com\/gmarik\/vundle) or [Pathogen](https:\/\/github.com\/tpope\/vim-pathogen)\r\n","first_name":"Jie","6":"Jie","last_name":"Wu","7":"Wu","releases":[{"0":"2627","vim_version":"7.0","1":"7.0","script_version":"v0.2.0","2":"v0.2.0","version_comment":"## New Features\r\n\r\n- Integrate Taglist and Tagbar.\r\n- Add online help toggle option `g:ex_{plugin}_enable_help` for on\/off help text in ex-plugins.\r\n- Add mkview and loadview in ex-project, this will allow ex-project keep the folding state.\r\n\r\n## Changes\r\n\r\n- Refine the script to help ex-project become a standalone plugin.\r\n- Add options in ctags shell to help generate namespaces tags.\r\n\r\n## Bug Fixes\r\n\r\n- Fix target line highlight will not clear when we use `:q` or `:close` close ex-plugin window.\r\n- Fix zoom window toggle will not reset when close ex-plugin window.\r\n- Fix ex-plugin focus error when editing multiple splitted buffer.\r\n- Fix after close a splitted window, ex-plugin will always open with a splitted buffer.\r\n- Fix when there is no edit window, ex-plugin window open will mess up.\r\n- Fix `<leader>bd` will close unsaved buffer without warning.\r\n- Fix ex-project will not keep fold state when close and re-open.\r\n","3":"## New Features\r\n\r\n- Integrate Taglist and Tagbar.\r\n- Add online help toggle option `g:ex_{plugin}_enable_help` for on\/off help text in ex-plugins.\r\n- Add mkview and loadview in ex-project, this will allow ex-project keep the folding state.\r\n\r\n## Changes\r\n\r\n- Refine the script to help ex-project become a standalone plugin.\r\n- Add options in ctags shell to help generate namespaces tags.\r\n\r\n## Bug Fixes\r\n\r\n- Fix target line highlight will not clear when we use `:q` or `:close` close ex-plugin window.\r\n- Fix zoom window toggle will not reset when close ex-plugin window.\r\n- Fix ex-plugin focus error when editing multiple splitted buffer.\r\n- Fix after close a splitted window, ex-plugin will always open with a splitted buffer.\r\n- Fix when there is no edit window, ex-plugin window open will mess up.\r\n- Fix `<leader>bd` will close unsaved buffer without warning.\r\n- Fix ex-project will not keep fold state when close and re-open.\r\n","package":"exvim-v0.2.0.tar.gz","4":"exvim-v0.2.0.tar.gz","src_id":"21840","5":"21840","creation_date":"1398760689","6":"1398760689"},{"0":"2627","vim_version":"7.0","1":"7.0","script_version":"v0.1.0","2":"v0.1.0","version_comment":"v0.1.0 Release Note\r\n\r\n## New Features\r\n\r\n - Add ex-symbol plugin\r\n - Add id-lang-autogen.map support when generate idutils shells with file_filter\r\n - Add type-script support by plugin typescript-vim\r\n - Add switch between NERDTree and ex-project window by <c-tab>\r\n\r\n## Changes\r\n\r\n - Change cwd from absolute directory to \".\/\".\r\n\r\n## Bug Fixes\r\n\r\n - Fixed :Update error when file_filter has value\r\n - Fixed white space path error\r\n - Fixed switch .exvim project will overwrite the old .exvim's auto commands\r\n - Fixed gsearch jumps will keepjumps which will lead to <ctrl-o> jump back to wrong position","3":"v0.1.0 Release Note\r\n\r\n## New Features\r\n\r\n - Add ex-symbol plugin\r\n - Add id-lang-autogen.map support when generate idutils shells with file_filter\r\n - Add type-script support by plugin typescript-vim\r\n - Add switch between NERDTree and ex-project window by <c-tab>\r\n\r\n## Changes\r\n\r\n - Change cwd from absolute directory to \".\/\".\r\n\r\n## Bug Fixes\r\n\r\n - Fixed :Update error when file_filter has value\r\n - Fixed white space path error\r\n - Fixed switch .exvim project will overwrite the old .exvim's auto commands\r\n - Fixed gsearch jumps will keepjumps which will lead to <ctrl-o> jump back to wrong position","package":"exvim-main-0.1.0.zip","4":"exvim-main-0.1.0.zip","src_id":"21781","5":"21781","creation_date":"1397639989","6":"1397639989"},{"0":"2627","vim_version":"7.0","1":"7.0","script_version":"Latest","2":"Latest","version_comment":"We are one github (https:\/\/github.com\/exvim\/main) under actively development. Join us! We need your advice, tests, issues and any ideas to make it better and better!","3":"We are one github (https:\/\/github.com\/exvim\/main) under actively development. Join us! We need your advice, tests, issues and any ideas to make it better and better!","package":"exVim_on_github","4":"exVim_on_github","src_id":"21652","5":"21652","creation_date":"1395552799","6":"1395552799"},{"0":"2627","vim_version":"7.3","1":"7.3","script_version":"8.05_b2","2":"8.05_b2","version_comment":"The package is used in unix, linux, mac-osx","3":"The package is used in unix, linux, mac-osx","package":"ex_plugins_package-unix-8.05_b2.zip","4":"ex_plugins_package-unix-8.05_b2.zip","src_id":"14684","5":"14684","creation_date":"1294220677","6":"1294220677"},{"0":"2627","vim_version":"7.3","1":"7.3","script_version":"8.05_b2","2":"8.05_b2","version_comment":"* New features\r\n** upgrade vim from 7.2 to 7.3\r\n** add javascript indent plugin. http:\/\/www.vim.org\/scripts\/script.php?script_id=1936\r\n** add AutoComplPop-2.14.1 plugin. http:\/\/www.vim.org\/scripts\/script.php?script_id=1879  \r\n** add EXTC command for easy writting extern \"C\" { } code block in c\/cpp files. \r\n* Changes\r\n** update .vimentry version from '24' to '25'.\r\n** disable auto-comment in javascript.\r\n** make vimwiki as an option plugin for user.\r\n** update zencoding to 0.43.\r\n** remove django syntax (not too much use).\r\n** update surround to 1.90.\r\n** set default encoding to utf-8.\r\n* Bug fix\r\n** fix visual studio unicode encoding error.\r\n** fix GSF,GSFW result can't jump.\r\n** fix acp conflict with lookupfile.\r\n** fix tag select can't parse lua function with white space\r\n** fix vimentryRefs not working in linux and mac OS.","3":"* New features\r\n** upgrade vim from 7.2 to 7.3\r\n** add javascript indent plugin. http:\/\/www.vim.org\/scripts\/script.php?script_id=1936\r\n** add AutoComplPop-2.14.1 plugin. http:\/\/www.vim.org\/scripts\/script.php?script_id=1879  \r\n** add EXTC command for easy writting extern \"C\" { } code block in c\/cpp files. \r\n* Changes\r\n** update .vimentry version from '24' to '25'.\r\n** disable auto-comment in javascript.\r\n** make vimwiki as an option plugin for user.\r\n** update zencoding to 0.43.\r\n** remove django syntax (not too much use).\r\n** update surround to 1.90.\r\n** set default encoding to utf-8.\r\n* Bug fix\r\n** fix visual studio unicode encoding error.\r\n** fix GSF,GSFW result can't jump.\r\n** fix acp conflict with lookupfile.\r\n** fix tag select can't parse lua function with white space\r\n** fix vimentryRefs not working in linux and mac OS.","package":"ex_plugins_package-win-8.05_b2.zip","4":"ex_plugins_package-win-8.05_b2.zip","src_id":"14683","5":"14683","creation_date":"1294220561","6":"1294220561"},{"0":"2627","vim_version":"7.0","1":"7.0","script_version":"8.04","2":"8.04","version_comment":"\r\n * New features\r\n\r\n   * support swig error format.\r\n   * add swig syntax highlight.\r\n   * add csharp syntax highlight for special mark labels.\r\n   * add zencoding plugin.\r\n   * add matchit plugin.\r\n   * add django syntax highlight.\r\n   * add sphinx document compile support.\r\n\r\n * Changes\r\n\r\n   * update vimwiki to 1.0.0.\r\n   * update cscope to 15.7a.\r\n   * refine gcc makefiles.\r\n   * let EnhancedCommentify support swig.\r\n   * disable auto-comment for c# language.\r\n   * always show status-line.\r\n   * change comment mathod for c in EnhancedCommentify, instead of using ``\/**\/`` we use ``\/\/`` like cpp. \r\n   * change guifont in win32 to Bitstream_Vera_Sans_Mono:h10.\r\n   * Not allow exGlobalSearch running in stand-alone mode, this prevent exGlobalSearch show error message.\r\n   * let exQuickFix support cs error format. \r\n   * change ``_vimfiles`` folder to .vimfiles\r\n   * change ``_vimfiles\/_hierarchies`` folder to .vimfiles\/.hierarchies\r\n   * change ``_vimfiles\/_temp`` folder to .vimfiles\/.temp\r\n   * change vimwiki _doc folder to wiki_src\r\n   * let exProject ignore checking .vimfiles folders when browsing.\r\n   * generate header.tpl use dest file's encoding.\r\n   * update gvim.exe link with python26.dll in windows.\r\n   * add ex_try, ex_catch, ex_catch_exp, ex_throw, ex_safe_delete, ex_safe_free... syntax highlight.\r\n   * add my method to judge if it is objc or mathlab files.\r\n   * add key-world TEST, PATCH, FIXME, BUG, TIPS, HINT\r\n   * add ``<leader>sub`` for quick substitue word_highlight_1 to word_highlight_2\r\n   * add signal, slots, emit qt keywords for highlighting\r\n   * disable maximize window when openning vim.\r\n\r\n * Bug fix\r\n\r\n   * fix exQuickFix open a file another programme already editing issue.\r\n   * fix exTagSelect show tags error when read preview from a file that already not exists.\r\n","3":"\r\n * New features\r\n\r\n   * support swig error format.\r\n   * add swig syntax highlight.\r\n   * add csharp syntax highlight for special mark labels.\r\n   * add zencoding plugin.\r\n   * add matchit plugin.\r\n   * add django syntax highlight.\r\n   * add sphinx document compile support.\r\n\r\n * Changes\r\n\r\n   * update vimwiki to 1.0.0.\r\n   * update cscope to 15.7a.\r\n   * refine gcc makefiles.\r\n   * let EnhancedCommentify support swig.\r\n   * disable auto-comment for c# language.\r\n   * always show status-line.\r\n   * change comment mathod for c in EnhancedCommentify, instead of using ``\/**\/`` we use ``\/\/`` like cpp. \r\n   * change guifont in win32 to Bitstream_Vera_Sans_Mono:h10.\r\n   * Not allow exGlobalSearch running in stand-alone mode, this prevent exGlobalSearch show error message.\r\n   * let exQuickFix support cs error format. \r\n   * change ``_vimfiles`` folder to .vimfiles\r\n   * change ``_vimfiles\/_hierarchies`` folder to .vimfiles\/.hierarchies\r\n   * change ``_vimfiles\/_temp`` folder to .vimfiles\/.temp\r\n   * change vimwiki _doc folder to wiki_src\r\n   * let exProject ignore checking .vimfiles folders when browsing.\r\n   * generate header.tpl use dest file's encoding.\r\n   * update gvim.exe link with python26.dll in windows.\r\n   * add ex_try, ex_catch, ex_catch_exp, ex_throw, ex_safe_delete, ex_safe_free... syntax highlight.\r\n   * add my method to judge if it is objc or mathlab files.\r\n   * add key-world TEST, PATCH, FIXME, BUG, TIPS, HINT\r\n   * add ``<leader>sub`` for quick substitue word_highlight_1 to word_highlight_2\r\n   * add signal, slots, emit qt keywords for highlighting\r\n   * disable maximize window when openning vim.\r\n\r\n * Bug fix\r\n\r\n   * fix exQuickFix open a file another programme already editing issue.\r\n   * fix exTagSelect show tags error when read preview from a file that already not exists.\r\n","package":"ex-plugins-package-8.04.zip","4":"ex-plugins-package-8.04.zip","src_id":"13057","5":"13057","creation_date":"1274866634","6":"1274866634"},{"0":"2627","vim_version":"7.0","1":"7.0","script_version":"8.03","2":"8.03","version_comment":" * New features\r\n    * let make syntax support external comments.\r\n    * refine install method for unix\/linux.\r\n    * support Mac OS X.\r\n * Changes\r\n    * support matlab\/octave language\r\n    * support maxscript language\r\n    * move data\/backup and data\/swap directory to $HOME\/.data\/backup $HOME\/.data\/swap\r\n    * change default toolkit_path to $HOME\/.toolkit\/ for unix\r\n    * enlarge the font size, re-adjust default windows width increment\r\n    * update cTags to 5.8\r\n    * update SyntaxHighliter to 2.1.364\r\n    * update vimwiki to 0.9.6\r\n    * update NERD_tree to 4.1.0\r\n    * update genutils to 2.5\r\n * Bug fix\r\n    * fix the filter format shows wrong syntax in dialog\r\n    * fix bracket \"()\" in directory name does not work.\r\n    * fix gcc_rule can't compile source file have same name but in different directory.\r\n    * fix PutHeader will show time in local encoding. Force to set it in English.\r\n    * fix exQuickFix can't jump msvc error message when use single core cpu. ( those message don't have \"1>\" at the beginning )\r\n    * fix exQuickfix can't select multi-core and single-core jump in msvc2005\r\n    * fix quick_gen_project.sh file_filter syntax error in unix\/linux.\r\n    * add protection for ImageViewer and WebBrowser\r\n","3":" * New features\r\n    * let make syntax support external comments.\r\n    * refine install method for unix\/linux.\r\n    * support Mac OS X.\r\n * Changes\r\n    * support matlab\/octave language\r\n    * support maxscript language\r\n    * move data\/backup and data\/swap directory to $HOME\/.data\/backup $HOME\/.data\/swap\r\n    * change default toolkit_path to $HOME\/.toolkit\/ for unix\r\n    * enlarge the font size, re-adjust default windows width increment\r\n    * update cTags to 5.8\r\n    * update SyntaxHighliter to 2.1.364\r\n    * update vimwiki to 0.9.6\r\n    * update NERD_tree to 4.1.0\r\n    * update genutils to 2.5\r\n * Bug fix\r\n    * fix the filter format shows wrong syntax in dialog\r\n    * fix bracket \"()\" in directory name does not work.\r\n    * fix gcc_rule can't compile source file have same name but in different directory.\r\n    * fix PutHeader will show time in local encoding. Force to set it in English.\r\n    * fix exQuickFix can't jump msvc error message when use single core cpu. ( those message don't have \"1>\" at the beginning )\r\n    * fix exQuickfix can't select multi-core and single-core jump in msvc2005\r\n    * fix quick_gen_project.sh file_filter syntax error in unix\/linux.\r\n    * add protection for ImageViewer and WebBrowser\r\n","package":"ex-plugins-package-8.03.zip","4":"ex-plugins-package-8.03.zip","src_id":"11842","5":"11842","creation_date":"1259758918","6":"1259758918"},{"0":"2627","vim_version":"7.0","1":"7.0","script_version":"8.02","2":"8.02","version_comment":"    * New features\r\n    * Changes\r\n          o let title show vimentry name first, so that you can select project with a clear name in task bar.\r\n          o add qt language map ( qt: qrc, pro, pri ) \r\n    * Bug fix\r\n          o fix exJumpStack jump error when we do tg word1, gg word2 then tg word1 again.\r\n          o fix inherit image can't show when path have white-space.\r\n          o fix exQuickFix loose fix when we load another quickfix list, and try to use the exQuickFix again.\r\n          o fix multiple gcc project makefile clean-deps error.\r\n          o fix lookupfile re-open deleted buffer will not show in the minibufexpl. (thanks vxzhong)\r\n          o fix minibufexpl mouse click open will not open in edit-buffer. (thanks ozgezer) ","3":"    * New features\r\n    * Changes\r\n          o let title show vimentry name first, so that you can select project with a clear name in task bar.\r\n          o add qt language map ( qt: qrc, pro, pri ) \r\n    * Bug fix\r\n          o fix exJumpStack jump error when we do tg word1, gg word2 then tg word1 again.\r\n          o fix inherit image can't show when path have white-space.\r\n          o fix exQuickFix loose fix when we load another quickfix list, and try to use the exQuickFix again.\r\n          o fix multiple gcc project makefile clean-deps error.\r\n          o fix lookupfile re-open deleted buffer will not show in the minibufexpl. (thanks vxzhong)\r\n          o fix minibufexpl mouse click open will not open in edit-buffer. (thanks ozgezer) ","package":"ex-plugins-package-8.02.zip","4":"ex-plugins-package-8.02.zip","src_id":"11081","5":"11081","creation_date":"1248871503","6":"1248871503"},{"0":"2627","vim_version":"7.0","1":"7.0","script_version":"8.02c","2":"8.02c","version_comment":"    * New features\r\n          o Temp highlight words under current cursor when cursor holds. \r\n    * Changes\r\n          o let exQuickFix can jump template sub-errors in msvc. \r\n    * Bug fix\r\n          o fix quick gen project can't generate cscope database. (thanks ozgezer)\r\n          o fix exBufExplorer save list buffers in bookmarks if we don't have a bookmarks file.\r\n          o fix quick_gen_project.sh filenamelist generation errors in unix like system. (thanks oz","3":"    * New features\r\n          o Temp highlight words under current cursor when cursor holds. \r\n    * Changes\r\n          o let exQuickFix can jump template sub-errors in msvc. \r\n    * Bug fix\r\n          o fix quick gen project can't generate cscope database. (thanks ozgezer)\r\n          o fix exBufExplorer save list buffers in bookmarks if we don't have a bookmarks file.\r\n          o fix quick_gen_project.sh filenamelist generation errors in unix like system. (thanks oz","package":"ex-plugins-package-8.02c.zip","4":"ex-plugins-package-8.02c.zip","src_id":"10945","5":"10945","creation_date":"1246753738","6":"1246753738"},{"0":"2627","vim_version":"7.0","1":"7.0","script_version":"8.02b","2":"8.02b","version_comment":"    * New features\r\n          o add exBufExplorer.\r\n          o add bookmarks in exBufExplorer.\r\n          o When cursor hold in exProject window, it will echo the full path in the cursor line.\r\n          o add ex_toolkit_path so user can install toolkit folder in a specific path.\r\n          o user delete bookmark directly in exBufExplorer. \r\n    * Changes\r\n          o change gf function to use lookupfile plugin.\r\n          o add SS command for filtering symbol table search result \r\n    * Bug fix\r\n          o fix quickgen bash script if statement syntax error.\r\n          o fix fail to run quick_gen_project script in csh shell.\r\n          o fix !FreeBSD ctags can't be detected correctly.\r\n          o fix buffer delete mess the window layout when there have several window opened.\r\n          o fix \\ff,\\fd search error, new method can even use smart case for search.\r\n          o fix ctrl-left\/right will go to the next buffer in plugin window, mess-up the window layout.\r\n          o fix exCscope syntax file name syntax highlight beyond the range.\r\n          o fix restore buffer never execute auto-command in last edit-buffer.\r\n          o only do search jump when current line not matched with the pattern in exJumpStack ","3":"    * New features\r\n          o add exBufExplorer.\r\n          o add bookmarks in exBufExplorer.\r\n          o When cursor hold in exProject window, it will echo the full path in the cursor line.\r\n          o add ex_toolkit_path so user can install toolkit folder in a specific path.\r\n          o user delete bookmark directly in exBufExplorer. \r\n    * Changes\r\n          o change gf function to use lookupfile plugin.\r\n          o add SS command for filtering symbol table search result \r\n    * Bug fix\r\n          o fix quickgen bash script if statement syntax error.\r\n          o fix fail to run quick_gen_project script in csh shell.\r\n          o fix !FreeBSD ctags can't be detected correctly.\r\n          o fix buffer delete mess the window layout when there have several window opened.\r\n          o fix \\ff,\\fd search error, new method can even use smart case for search.\r\n          o fix ctrl-left\/right will go to the next buffer in plugin window, mess-up the window layout.\r\n          o fix exCscope syntax file name syntax highlight beyond the range.\r\n          o fix restore buffer never execute auto-command in last edit-buffer.\r\n          o only do search jump when current line not matched with the pattern in exJumpStack ","package":"ex-plugins-package-8.02b.zip","4":"ex-plugins-package-8.02b.zip","src_id":"10903","5":"10903","creation_date":"1246069214","6":"1246069214"},{"0":"2627","vim_version":"7.0","1":"7.0","script_version":"8.02a","2":"8.02a","version_comment":"    * New features\r\n          o let exProject support file with no-suffix (NULL filetype).\r\n          o let cscope can parse by specific language type.\r\n          o add DirDiff and snipMate plugin.\r\n          o add pythoncomplete plugin.\r\n          o add exBufExplorer (exProject quick-view window) for exploring and editing opened buffers. \r\n    * Changes\r\n          o add backspace navigate and alt+left\/right navigate for exJumpStack.\r\n          o let EnhComment support snippet file.\r\n          o change ex_plugin_list to ex_plugin_registered_bufnames,ex_plugin_registered_filetypes to enhance the register-plugin.\r\n          o let exProject and NERDtree can switch.\r\n          o remove _vimfiles* folders when list project tree in exProject window. \r\n    * Bug fix\r\n          o fix Mark Text can't be lower case.\r\n          o fix lots of exCscope problem.\r\n          o fix cscope syntax highlight.\r\n          o fix showmarks conflict with snipMate plugin,\r\n          o fix color scheme will be dark when there is no colorscheme set in _vimrc.\r\n          o fix taglist,NERD_tree,minibufexpl opens window not take the position when there already have ex-plugin window.\r\n          o let exJumpStack can recognize all registered plugin window.\r\n          o fix findfile in g:exES_CWD reports wrong result when directory name have space\r\n          o remove hard code in detecting ctags and cscope support.\r\n          o fix cursor can't move to the edit-buffer when use restore buffer. ","3":"    * New features\r\n          o let exProject support file with no-suffix (NULL filetype).\r\n          o let cscope can parse by specific language type.\r\n          o add DirDiff and snipMate plugin.\r\n          o add pythoncomplete plugin.\r\n          o add exBufExplorer (exProject quick-view window) for exploring and editing opened buffers. \r\n    * Changes\r\n          o add backspace navigate and alt+left\/right navigate for exJumpStack.\r\n          o let EnhComment support snippet file.\r\n          o change ex_plugin_list to ex_plugin_registered_bufnames,ex_plugin_registered_filetypes to enhance the register-plugin.\r\n          o let exProject and NERDtree can switch.\r\n          o remove _vimfiles* folders when list project tree in exProject window. \r\n    * Bug fix\r\n          o fix Mark Text can't be lower case.\r\n          o fix lots of exCscope problem.\r\n          o fix cscope syntax highlight.\r\n          o fix showmarks conflict with snipMate plugin,\r\n          o fix color scheme will be dark when there is no colorscheme set in _vimrc.\r\n          o fix taglist,NERD_tree,minibufexpl opens window not take the position when there already have ex-plugin window.\r\n          o let exJumpStack can recognize all registered plugin window.\r\n          o fix findfile in g:exES_CWD reports wrong result when directory name have space\r\n          o remove hard code in detecting ctags and cscope support.\r\n          o fix cursor can't move to the edit-buffer when use restore buffer. ","package":"ex-plugins-package-8.02a.zip","4":"ex-plugins-package-8.02a.zip","src_id":"10879","5":"10879","creation_date":"1245495046","6":"1245495046"},{"0":"2627","vim_version":"7.0","1":"7.0","script_version":"8.01b","2":"8.01b","version_comment":"    * New features\r\n          o let quick_gen_project can update filenametags\r\n          o let exCscope support find g method \r\n    * Changes\r\n          o make exSearchComplete disable in unix\/linux terminal.\r\n          o let lookupfile, taglist use the same key map settings as ex-plugins have.\r\n          o use pattern instead of preview for exJumpStack, the preview will be generate dynamically.\r\n          o use pattern locate the jump result, so that even you changes some of the line between the jump result, it still have chance to locate to the exact position.\r\n          o add quick_gen_project_pre_custom and quick_gen_project_post_custom when update project.\r\n          o when doing stack jump, use keepjumps.\r\n          o Add protect codes for moving project files.\r\n          o add cscope file name highlight \r\n    * Bug fix\r\n          o fix the EX_DEV been overwritten in linux.\r\n          o fix highlight error of key word \"class::define\" in exJumpStack.\r\n          o fix exJumpStack when poping up stack, reset wrong tag index.\r\n          o fix EX_DEV setting error in windows, when there is no EX_DEV environment variable.\r\n          o fix cscope filter search error.\r\n          o fix EX_DEV setting error in windows, when there is no EX_DEV environment variable.\r\n          o fix exJumpStack can't locate empty line or line with only space, tab problem ","3":"    * New features\r\n          o let quick_gen_project can update filenametags\r\n          o let exCscope support find g method \r\n    * Changes\r\n          o make exSearchComplete disable in unix\/linux terminal.\r\n          o let lookupfile, taglist use the same key map settings as ex-plugins have.\r\n          o use pattern instead of preview for exJumpStack, the preview will be generate dynamically.\r\n          o use pattern locate the jump result, so that even you changes some of the line between the jump result, it still have chance to locate to the exact position.\r\n          o add quick_gen_project_pre_custom and quick_gen_project_post_custom when update project.\r\n          o when doing stack jump, use keepjumps.\r\n          o Add protect codes for moving project files.\r\n          o add cscope file name highlight \r\n    * Bug fix\r\n          o fix the EX_DEV been overwritten in linux.\r\n          o fix highlight error of key word \"class::define\" in exJumpStack.\r\n          o fix exJumpStack when poping up stack, reset wrong tag index.\r\n          o fix EX_DEV setting error in windows, when there is no EX_DEV environment variable.\r\n          o fix cscope filter search error.\r\n          o fix EX_DEV setting error in windows, when there is no EX_DEV environment variable.\r\n          o fix exJumpStack can't locate empty line or line with only space, tab problem ","package":"ex-plugins-package-8.01b.zip","4":"ex-plugins-package-8.01b.zip","src_id":"10824","5":"10824","creation_date":"1244994429","6":"1244994429"},{"0":"2627","vim_version":"7.0","1":"7.0","script_version":"8.01a","2":"8.01a","version_comment":"    * New features\r\n          o add ex_lightgray color scheme.\r\n          o Support search result sorting for exGlobalSearch.\r\n                + add g:exGS_auto_sort, g:exGS_lines_for_autosort settings\r\n                + add \\sr operations for force sort search result. \r\n          o Support general key map settings for ex-plugin.\r\n          o add exJumpStack \r\n    * Changes\r\n          o add errorformat support for exGlobalSearch result. (People may copy the exGlobaSearch result from global search window to quickfix window)\r\n          o in old version, exQF_PasteQuickFixResult? can only use \\p. now you can use p or \\p to accomplish the task.\r\n          o add warnning when use visual p,\\p to paste a result to quickfix window, it will switch to normal p,\\p operation.\r\n          o add EX_DEV environment support in unix\/linux.\r\n          o let taglist support hlsl language.\r\n          o let root directory dialog only show up in exProject standalone version.\r\n          o add compile error support for hlsl in exQuickFix.\r\n          o remove tag stack in exTagSelect, use exJumpStack instead. \r\n    * Bug fix\r\n          o fix cscope can't parse file name with space.\r\n          o fix switch window can't keep the same window size problem.\r\n          o fix macro highlight ignore case for macro\r\n          o fix arrow key can't be used in terminal version of unix\/linux\r\n          o fix macro highlight highlight error when the macro #if is not at the beginning of the line. ","3":"    * New features\r\n          o add ex_lightgray color scheme.\r\n          o Support search result sorting for exGlobalSearch.\r\n                + add g:exGS_auto_sort, g:exGS_lines_for_autosort settings\r\n                + add \\sr operations for force sort search result. \r\n          o Support general key map settings for ex-plugin.\r\n          o add exJumpStack \r\n    * Changes\r\n          o add errorformat support for exGlobalSearch result. (People may copy the exGlobaSearch result from global search window to quickfix window)\r\n          o in old version, exQF_PasteQuickFixResult? can only use \\p. now you can use p or \\p to accomplish the task.\r\n          o add warnning when use visual p,\\p to paste a result to quickfix window, it will switch to normal p,\\p operation.\r\n          o add EX_DEV environment support in unix\/linux.\r\n          o let taglist support hlsl language.\r\n          o let root directory dialog only show up in exProject standalone version.\r\n          o add compile error support for hlsl in exQuickFix.\r\n          o remove tag stack in exTagSelect, use exJumpStack instead. \r\n    * Bug fix\r\n          o fix cscope can't parse file name with space.\r\n          o fix switch window can't keep the same window size problem.\r\n          o fix macro highlight ignore case for macro\r\n          o fix arrow key can't be used in terminal version of unix\/linux\r\n          o fix macro highlight highlight error when the macro #if is not at the beginning of the line. ","package":"ex-plugins-package-8.01a.zip","4":"ex-plugins-package-8.01a.zip","src_id":"10764","5":"10764","creation_date":"1244362345","6":"1244362345"},{"0":"2627","vim_version":"7.0","1":"7.0","script_version":"7.05","2":"7.05","version_comment":"\r\n    * New features\r\n          o add \\ve to quick edit current vimentry file.\r\n          o add vimentry name check when open vimentry file. if vimentry name is not the same with the value VimEntryName in vimentry file, it will lead to a vimentry re-write.\r\n          o add paste quickfix result from register '*'.\r\n          o add exUtility#CloseAllExpluginWindow() function\r\n          o add s:ex_lang_map for exVim. you can use exUtility#RestLangMap and exUtility#AddLangMap function to create your own language maps.\r\n                + remove g:exPJ_default_filter variable. use g:ex_default_langs instead.\r\n                + add ExpjUpdateFilters command\r\n                + add g:exES_LangType? set project filter process in exEnvironment\r\n                + let exUtility#GetLangType and exUtility#GetCtagsOption support s:ex_lang_map \r\n          o add darkscheme support \r\n    * Changes\r\n          o change the id language custom map from id-lang.map to id-lang-custom.map.\r\n          o disable move\/del command shows information in quick_gen_project.bat by add > nul\r\n          o change g:exES_vimfile_dir to g:exES_vimfiles_dirname.\r\n          o change exProject filetype from ft_exproject to ex_filetype\r\n          o change g:exUT_plugin_list to g:ex_plugin_list \r\n    * Bug fix\r\n          o fix \\fc can't work outside edit window.\r\n          o fix \"<args>\" can't accept win32 path problem. by replace all \"<args>\" to '<args>'\r\n          o use :e xxx.vimentry when you already in another vimentry, the project settings will not be switch.\r\n                + fix :EXProject <filename> will not close old project file when the <filename> is not the same.\r\n                + fix exSymbolTable and exMacroHighlight can't load new file when they already load one. \r\n          o fix \\cf error.\r\n          o fix toggle window can't let the cursor focus on it. ","3":"\r\n    * New features\r\n          o add \\ve to quick edit current vimentry file.\r\n          o add vimentry name check when open vimentry file. if vimentry name is not the same with the value VimEntryName in vimentry file, it will lead to a vimentry re-write.\r\n          o add paste quickfix result from register '*'.\r\n          o add exUtility#CloseAllExpluginWindow() function\r\n          o add s:ex_lang_map for exVim. you can use exUtility#RestLangMap and exUtility#AddLangMap function to create your own language maps.\r\n                + remove g:exPJ_default_filter variable. use g:ex_default_langs instead.\r\n                + add ExpjUpdateFilters command\r\n                + add g:exES_LangType? set project filter process in exEnvironment\r\n                + let exUtility#GetLangType and exUtility#GetCtagsOption support s:ex_lang_map \r\n          o add darkscheme support \r\n    * Changes\r\n          o change the id language custom map from id-lang.map to id-lang-custom.map.\r\n          o disable move\/del command shows information in quick_gen_project.bat by add > nul\r\n          o change g:exES_vimfile_dir to g:exES_vimfiles_dirname.\r\n          o change exProject filetype from ft_exproject to ex_filetype\r\n          o change g:exUT_plugin_list to g:ex_plugin_list \r\n    * Bug fix\r\n          o fix \\fc can't work outside edit window.\r\n          o fix \"<args>\" can't accept win32 path problem. by replace all \"<args>\" to '<args>'\r\n          o use :e xxx.vimentry when you already in another vimentry, the project settings will not be switch.\r\n                + fix :EXProject <filename> will not close old project file when the <filename> is not the same.\r\n                + fix exSymbolTable and exMacroHighlight can't load new file when they already load one. \r\n          o fix \\cf error.\r\n          o fix toggle window can't let the cursor focus on it. ","package":"ex-plugins-package-7.05.zip","4":"ex-plugins-package-7.05.zip","src_id":"10703","5":"10703","creation_date":"1243655770","6":"1243655770"},{"0":"2627","vim_version":"7.0","1":"7.0","script_version":"7.05b","2":"7.05b","version_comment":" * New features\r\n    * Support more than one \".vimentry\" in same directory. \r\n    * add \"!VimEntryName\" and \"!VimfilesDirName\" in `.vimentry` file.\r\n * Changes\r\n    * add \"autogen settings (DO NOT MODIFY)\" comments in the vimentry file.\r\n    * `.vimentry` version number update to 21. ( you will loose your old .vimentry file settings when open an old project ) \r\n    * disable move\/del command shows information in quick_gen_project.bat by add `> nul`\r\n    * change g:exPJ_defualt_filter to g:exPJ_default_filter.\r\n    * remove g:exES_default_vimfiles, now the vimfiles dirname will be generate automatically by the vimentry name.\r\n * Bug fix\r\n    * fix exEnvironment use getcwd as g:exES_CWD bug. Instead, we use the folder path of `.vimentry` file \r\n    * fix exGlobalSearch <c-left>, <c-right> will go to edit buffer \r\n    * fix visual studio.py can't load unicode solution name\r\n    * fix open `.vimentry` failed from vim in different path than the path of `.vimentry`\r\n","3":" * New features\r\n    * Support more than one \".vimentry\" in same directory. \r\n    * add \"!VimEntryName\" and \"!VimfilesDirName\" in `.vimentry` file.\r\n * Changes\r\n    * add \"autogen settings (DO NOT MODIFY)\" comments in the vimentry file.\r\n    * `.vimentry` version number update to 21. ( you will loose your old .vimentry file settings when open an old project ) \r\n    * disable move\/del command shows information in quick_gen_project.bat by add `> nul`\r\n    * change g:exPJ_defualt_filter to g:exPJ_default_filter.\r\n    * remove g:exES_default_vimfiles, now the vimfiles dirname will be generate automatically by the vimentry name.\r\n * Bug fix\r\n    * fix exEnvironment use getcwd as g:exES_CWD bug. Instead, we use the folder path of `.vimentry` file \r\n    * fix exGlobalSearch <c-left>, <c-right> will go to edit buffer \r\n    * fix visual studio.py can't load unicode solution name\r\n    * fix open `.vimentry` failed from vim in different path than the path of `.vimentry`\r\n","package":"ex-plugins-package-7.05b.zip","4":"ex-plugins-package-7.05b.zip","src_id":"10673","5":"10673","creation_date":"1243176216","6":"1243176216"},{"0":"2627","vim_version":"7.0","1":"7.0","script_version":"7.05a","2":"7.05a","version_comment":"    * New features\r\n          o Restore last edit buffer.\r\n          o Update project depends on project files ( file_filter and dir_filter ).\r\n                + add filenamelist generate script in quick_gen_project.bat\/sh.\r\n                + update ctags use option -L filenamelist instead of -R.\r\n                + update cscope use filenamelist instead of dir \/s \/b whole directory.\r\n                + add trace log for quick_gen_project script. \r\n          o Support multi-language type for project.\r\n          o Support choose language type automatically. (depends on your file_filter input) \r\n    * Changes\r\n          o change exProject file filter and dir filter syntax\r\n                + file filter = type1,type2,type3,...,\r\n                + dir filter = dir1,dir2,dir3,...,\r\n                + NOTE: you need to remove the original *.exproject files for this change, or you will meet unwanted errors during refresh project and update project. \r\n          o Automatically generate quick_gen_project-auto.bat\/sh instead of copying one from toolkit\/quickgen.\r\n          o Remove quick_gen_project_xxx_only.bat\/sh scripts. (since we use quick_gen_project-auto and -custom)\r\n          o .vimentry version number update to 17. ( you will loose your old .vimentry file settings when open an old project ) \r\n    * Bug fix\r\n          o Fix exMacroHighlight syntax highlight disappear when no any c-like file loaded. ","3":"    * New features\r\n          o Restore last edit buffer.\r\n          o Update project depends on project files ( file_filter and dir_filter ).\r\n                + add filenamelist generate script in quick_gen_project.bat\/sh.\r\n                + update ctags use option -L filenamelist instead of -R.\r\n                + update cscope use filenamelist instead of dir \/s \/b whole directory.\r\n                + add trace log for quick_gen_project script. \r\n          o Support multi-language type for project.\r\n          o Support choose language type automatically. (depends on your file_filter input) \r\n    * Changes\r\n          o change exProject file filter and dir filter syntax\r\n                + file filter = type1,type2,type3,...,\r\n                + dir filter = dir1,dir2,dir3,...,\r\n                + NOTE: you need to remove the original *.exproject files for this change, or you will meet unwanted errors during refresh project and update project. \r\n          o Automatically generate quick_gen_project-auto.bat\/sh instead of copying one from toolkit\/quickgen.\r\n          o Remove quick_gen_project_xxx_only.bat\/sh scripts. (since we use quick_gen_project-auto and -custom)\r\n          o .vimentry version number update to 17. ( you will loose your old .vimentry file settings when open an old project ) \r\n    * Bug fix\r\n          o Fix exMacroHighlight syntax highlight disappear when no any c-like file loaded. ","package":"ex-plugins-package-7.05a.zip","4":"ex-plugins-package-7.05a.zip","src_id":"10627","5":"10627","creation_date":"1242660032","6":"1242660032"},{"0":"2627","vim_version":"7.0","1":"7.0","script_version":"2.0","2":"2.0","version_comment":"the patched third part plugins","3":"the patched third part plugins","package":"patched-plugins-package.zip","4":"patched-plugins-package.zip","src_id":"10571","5":"10571","creation_date":"1241964589","6":"1241964589"},{"0":"2627","vim_version":"7.0","1":"7.0","script_version":"7.04a","2":"7.04a","version_comment":"fix some bugs","3":"fix some bugs","package":"ex-plugins-package-7.04a.zip","4":"ex-plugins-package-7.04a.zip","src_id":"10570","5":"10570","creation_date":"1241964520","6":"1241964520"},{"0":"2627","vim_version":"7.0","1":"7.0","script_version":"7.0","2":"7.0","version_comment":"Initial upload","3":"Initial upload","package":"ex_plugin_only-7.0.7z","4":"ex_plugin_only-7.0.7z","src_id":"10546","5":"10546","creation_date":"1241613372","6":"1241613372"}]},"2626":{"script_id":"2626","0":"2626","script_name":"Vimya","1":"Vimya","script_type":"utility","2":"utility","summary":"Evaluate buffer content as Python or MEL script in Autodesk\u00c2\u00ae Maya\u00c2\u00ae","3":"Evaluate buffer content as Python or MEL script in Autodesk\u00c2\u00ae Maya\u00c2\u00ae","description":"Vimya can be used to execute the contents of a Vim buffer, the current visual selection or a single command in Autodesk Maya. The plugin will save the commands to be executed in a temporary file and tell Maya via the command port to source this file. Both MEL and Python scripts are supported, Maya's log can optionally be opened in a separate preview window or tab in Vim (requires the Tail Bundle plugin: vimscript #1714).\r\n\r\nImportant: You need a Vim version with built-in Python support to run this plugin!\r\n\r\n* news: http:\/\/subtype.de\/category\/vimya\/\r\n* news feed: http:\/\/subtype.de\/category\/vimya\/index.atom\r\n* Git repository: https:\/\/gitlab.com\/goeb\/vimya\/\r\n* bug tracker: https:\/\/gitlab.com\/goeb\/vimya\/issues\/","4":"Vimya can be used to execute the contents of a Vim buffer, the current visual selection or a single command in Autodesk Maya. The plugin will save the commands to be executed in a temporary file and tell Maya via the command port to source this file. Both MEL and Python scripts are supported, Maya's log can optionally be opened in a separate preview window or tab in Vim (requires the Tail Bundle plugin: vimscript #1714).\r\n\r\nImportant: You need a Vim version with built-in Python support to run this plugin!\r\n\r\n* news: http:\/\/subtype.de\/category\/vimya\/\r\n* news feed: http:\/\/subtype.de\/category\/vimya\/index.atom\r\n* Git repository: https:\/\/gitlab.com\/goeb\/vimya\/\r\n* bug tracker: https:\/\/gitlab.com\/goeb\/vimya\/issues\/","install_details":"Starting with version 0.3, a VimBall is provided for easy installation (requires vimscript #1502). Download the VBA file, open it in Vim and run \":so %\" to install it.\r\n\r\nAlternatively, download and extract the ZIP archive in your runtimepath, usually ~\/.vim\/. A help file is included, run the :helptags command to update the tag list (eg. \":helptags ~\/.vim\/doc\/\").\r\n\r\nSee \":help vimya\" for usage instructions.","5":"Starting with version 0.3, a VimBall is provided for easy installation (requires vimscript #1502). Download the VBA file, open it in Vim and run \":so %\" to install it.\r\n\r\nAlternatively, download and extract the ZIP archive in your runtimepath, usually ~\/.vim\/. A help file is included, run the :helptags command to update the tag list (eg. \":helptags ~\/.vim\/doc\/\").\r\n\r\nSee \":help vimya\" for usage instructions.","first_name":"Stefan","6":"Stefan","last_name":"G\u00c3\u00b6bel","7":"G\u00c3\u00b6bel","releases":[{"0":"2626","vim_version":"8.0","1":"8.0","script_version":"0.6","2":"0.6","version_comment":"Same as below, as VimBall.","3":"Same as below, as VimBall.","package":"vimya-0.6.vba","4":"vimya-0.6.vba","src_id":"27759","5":"27759","creation_date":"1633062204","6":"1633062204"},{"0":"2626","vim_version":"8.0","1":"8.0","script_version":"0.6","2":"0.6","version_comment":"Merged Talha Ahmed's VimyaWhatIs functionality.","3":"Merged Talha Ahmed's VimyaWhatIs functionality.","package":"vimya-0.6.zip","4":"vimya-0.6.zip","src_id":"27758","5":"27758","creation_date":"1633062182","6":"1633062182"},{"0":"2626","vim_version":"7.0","1":"7.0","script_version":"0.5","2":"0.5","version_comment":"Same as below, as VimBall.","3":"Same as below, as VimBall.","package":"vimya-0.5.vba","4":"vimya-0.5.vba","src_id":"21933","5":"21933","creation_date":"1400862761","6":"1400862761"},{"0":"2626","vim_version":"7.0","1":"7.0","script_version":"0.5","2":"0.5","version_comment":"Rewrite of most code. Includes some new functions, options and Ex commands. Please see the changelog in doc\/vimya.txt for more details.","3":"Rewrite of most code. Includes some new functions, options and Ex commands. Please see the changelog in doc\/vimya.txt for more details.","package":"vimya-0.5.zip","4":"vimya-0.5.zip","src_id":"21932","5":"21932","creation_date":"1400862738","6":"1400862738"},{"0":"2626","vim_version":"7.0","1":"7.0","script_version":"0.4","2":"0.4","version_comment":"Same as below, as VimBall.","3":"Same as below, as VimBall.","package":"vimya-0.4.vba","4":"vimya-0.4.vba","src_id":"21473","5":"21473","creation_date":"1392221531","6":"1392221531"},{"0":"2626","vim_version":"7.0","1":"7.0","script_version":"0.4","2":"0.4","version_comment":"Added the vimyaTempDir and vimyaTailCommand options.","3":"Added the vimyaTempDir and vimyaTailCommand options.","package":"vimya-0.4.zip","4":"vimya-0.4.zip","src_id":"21472","5":"21472","creation_date":"1392221507","6":"1392221507"},{"0":"2626","vim_version":"7.0","1":"7.0","script_version":"0.3","2":"0.3","version_comment":"Same as below, as VimBall.","3":"Same as below, as VimBall.","package":"vimya-0.3.vba","4":"vimya-0.3.vba","src_id":"19455","5":"19455","creation_date":"1359547667","6":"1359547667"},{"0":"2626","vim_version":"7.0","1":"7.0","script_version":"0.3","2":"0.3","version_comment":"Added userCmd parameter to sendBufferToMaya() function.","3":"Added userCmd parameter to sendBufferToMaya() function.","package":"vimya-0.3.zip","4":"vimya-0.3.zip","src_id":"19454","5":"19454","creation_date":"1359547505","6":"1359547505"},{"0":"2626","vim_version":"7.0","1":"7.0","script_version":"0.2","2":"0.2","version_comment":"The plugin should work on Windows now. Also, deleting temporary files did not always work as expected, this should also be fixed now.","3":"The plugin should work on Windows now. Also, deleting temporary files did not always work as expected, this should also be fixed now.","package":"vimya-0.2.zip","4":"vimya-0.2.zip","src_id":"11966","5":"11966","creation_date":"1261947799","6":"1261947799"},{"0":"2626","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"vimya-0.1.zip","4":"vimya-0.1.zip","src_id":"10538","5":"10538","creation_date":"1241569725","6":"1241569725"}]},"2625":{"script_id":"2625","0":"2625","script_name":"Cabal.vim","1":"Cabal.vim","script_type":"syntax","2":"syntax","summary":"Cabal, haskell's build system syntax coloration","3":"Cabal, haskell's build system syntax coloration","description":"Syntax for the cabal build system.\r\nAlso contain a ftdetect file to associate all *.cabal files with the syntax\r\nShould recognize all commands of the current version.\r\n\r\n\r\nGitHub: https:\/\/github.com\/Twinside\/vim-syntax-haskell-cabal\r\n\r\nCheckout http:\/\/www.vim.org\/scripts\/script.php?script_id=2611 for some cabal snippets","4":"Syntax for the cabal build system.\r\nAlso contain a ftdetect file to associate all *.cabal files with the syntax\r\nShould recognize all commands of the current version.\r\n\r\n\r\nGitHub: https:\/\/github.com\/Twinside\/vim-syntax-haskell-cabal\r\n\r\nCheckout http:\/\/www.vim.org\/scripts\/script.php?script_id=2611 for some cabal snippets","install_details":" *Just drop syntax\/cabal.vim in your ~\/.vim\/syntax or ~\/vimfiles\/syntax\r\n * or use pathogen and clone the github repository in your ~\/.vim\/bundle or ~\/vimfiles\/bundle\r\n","5":" *Just drop syntax\/cabal.vim in your ~\/.vim\/syntax or ~\/vimfiles\/syntax\r\n * or use pathogen and clone the github repository in your ~\/.vim\/bundle or ~\/vimfiles\/bundle\r\n","first_name":"Vincent","6":"Vincent","last_name":"B","7":"B","releases":[{"0":"2625","vim_version":"7.0","1":"7.0","script_version":"1,4","2":"1,4","version_comment":"Add benchmark support, thanks to Simon Meier","3":"Add benchmark support, thanks to Simon Meier","package":"cabal.vim","4":"cabal.vim","src_id":"16755","5":"16755","creation_date":"1319739562","6":"1319739562"},{"0":"2625","vim_version":"7.0","1":"7.0","script_version":"1.3","2":"1.3","version_comment":"Updated to the last version of cabal. Added more highlighting for cabal function, true\/false and version number. Also added missing comment highlighting. Cabal's known compiler are highlighted too.\r\n","3":"Updated to the last version of cabal. Added more highlighting for cabal function, true\/false and version number. Also added missing comment highlighting. Cabal's known compiler are highlighted too.\r\n","package":"cabal.vba","4":"cabal.vba","src_id":"12173","5":"12173","creation_date":"1264339532","6":"1264339532"}]},"2624":{"script_id":"2624","0":"2624","script_name":"ProtoDef","1":"ProtoDef","script_type":"utility","2":"utility","summary":"Tool to help create skeleton implementations of c++ function prototypes","3":"Tool to help create skeleton implementations of c++ function prototypes","description":"Requires:\r\n- ctags 5.7 or greater\r\n- PERL (just PERL, you don't need to have Vim compiled with PERL support)\r\n- FSwitch Vim utility (vimscript #2590)\r\n\r\nCheck out the video demo at: http:\/\/www.vimeo.com\/4448265\r\n\r\nYou've got a C++ header file and you've got some prototypes declared in there.  Now you need to create some definitions in a C++ implementation file.  What do you do?  Yank and paste?  Naw :)  Use this plugin instead...\r\n\r\nThe concept is pretty simple: while in the implementation file, you hit a key and all of the currently undefined function prototypes in the header file are automatically pulled in to the implementation file and inserted at the current cursor position.\r\n\r\n- Pure virtual functions are ignored\r\n- Functions that are already defined in the header file are ignored\r\n- Free functions are brought in\r\n- Class name is automatically prefixed to member functions\r\n- Constructors and Destructors sort first\r\n- Only the missing items are pulled in so you can use this utility to bring the implementation file up to match the contents of the header file\r\n- However you format the prototype shouldn't really make a difference.  ProtoDef endeavours to reduce all declarations to a canonical form.\r\n\r\nProtoDef can now be found on GitHub: http:\/\/github.com\/derekwyatt\/vim-protodef","4":"Requires:\r\n- ctags 5.7 or greater\r\n- PERL (just PERL, you don't need to have Vim compiled with PERL support)\r\n- FSwitch Vim utility (vimscript #2590)\r\n\r\nCheck out the video demo at: http:\/\/www.vimeo.com\/4448265\r\n\r\nYou've got a C++ header file and you've got some prototypes declared in there.  Now you need to create some definitions in a C++ implementation file.  What do you do?  Yank and paste?  Naw :)  Use this plugin instead...\r\n\r\nThe concept is pretty simple: while in the implementation file, you hit a key and all of the currently undefined function prototypes in the header file are automatically pulled in to the implementation file and inserted at the current cursor position.\r\n\r\n- Pure virtual functions are ignored\r\n- Functions that are already defined in the header file are ignored\r\n- Free functions are brought in\r\n- Class name is automatically prefixed to member functions\r\n- Constructors and Destructors sort first\r\n- Only the missing items are pulled in so you can use this utility to bring the implementation file up to match the contents of the header file\r\n- However you format the prototype shouldn't really make a difference.  ProtoDef endeavours to reduce all declarations to a canonical form.\r\n\r\nProtoDef can now be found on GitHub: http:\/\/github.com\/derekwyatt\/vim-protodef","install_details":"- Extract the archive.\r\n- put doc\/protodef.txt into ~\/.vim\/doc\r\n- put plugin\/protodef.vim into ~\/.vim\/plugin\r\n- :helptags ~\/.vim\/doc\r\n- read protodef.txt and follow what's in the Setup section to understand what to do with the pullproto.pl file.","5":"- Extract the archive.\r\n- put doc\/protodef.txt into ~\/.vim\/doc\r\n- put plugin\/protodef.vim into ~\/.vim\/plugin\r\n- :helptags ~\/.vim\/doc\r\n- read protodef.txt and follow what's in the Setup section to understand what to do with the pullproto.pl file.","first_name":"Derek","6":"Derek","last_name":"Wyatt","7":"Wyatt","releases":[{"0":"2624","vim_version":"7.0","1":"7.0","script_version":"0.9.5","2":"0.9.5","version_comment":"Fixed up a regular expression so it matches pointers and references better (pointers and references attached to the name instead of the type, which is hideous).  (Paolo Capriotti)","3":"Fixed up a regular expression so it matches pointers and references better (pointers and references attached to the name instead of the type, which is hideous).  (Paolo Capriotti)","package":"protodef-0.9.5.zip","4":"protodef-0.9.5.zip","src_id":"14138","5":"14138","creation_date":"1288259468","6":"1288259468"},{"0":"2624","vim_version":"7.0","1":"7.0","script_version":"0.9.4","2":"0.9.4","version_comment":"\t- Made sure that we need at least 7.0 (Timon Kelter)\r\n\t- Introduced the disable_protodef_sorting variable.\r\n\t- Added a fix to deal with default parameters that were class\r\n\t  instances (e.g. MyClass()) (Matt Spear)\r\n\t- Fixed function prototype parsing in pullproto.pl such that regex\r\n\t  special characters are deal with nicely (Matt Spear)\r\n\t- Handle template specializations properly (Matt Spear)\r\n\t- Ensure that implementations in the header file but outside the class\r\n\t  definition are not brought in to the implementation (Dmitry Bashkatov)\r\n","3":"\t- Made sure that we need at least 7.0 (Timon Kelter)\r\n\t- Introduced the disable_protodef_sorting variable.\r\n\t- Added a fix to deal with default parameters that were class\r\n\t  instances (e.g. MyClass()) (Matt Spear)\r\n\t- Fixed function prototype parsing in pullproto.pl such that regex\r\n\t  special characters are deal with nicely (Matt Spear)\r\n\t- Handle template specializations properly (Matt Spear)\r\n\t- Ensure that implementations in the header file but outside the class\r\n\t  definition are not brought in to the implementation (Dmitry Bashkatov)\r\n","package":"protodef-0.9.4.zip","4":"protodef-0.9.4.zip","src_id":"14048","5":"14048","creation_date":"1286929535","6":"1286929535"},{"0":"2624","vim_version":"7.0","1":"7.0","script_version":"0.9.3","2":"0.9.3","version_comment":"Fixed a bug in the autocmd where the \".C\" extension was written as \",C\"","3":"Fixed a bug in the autocmd where the \".C\" extension was written as \",C\"","package":"protodef-0.9.3.tar.gz","4":"protodef-0.9.3.tar.gz","src_id":"11376","5":"11376","creation_date":"1252970174","6":"1252970174"},{"0":"2624","vim_version":"7.0","1":"7.0","script_version":"0.9.2","2":"0.9.2","version_comment":"Added the ability to ignore the namespace (e.g. if you define a namespace block and don't need the prototypes to be prefixed with the namespace).","3":"Added the ability to ignore the namespace (e.g. if you define a namespace block and don't need the prototypes to be prefixed with the namespace).","package":"protodef_0.9.2.tar.gz","4":"protodef_0.9.2.tar.gz","src_id":"11241","5":"11241","creation_date":"1251065045","6":"1251065045"},{"0":"2624","vim_version":"7.0","1":"7.0","script_version":"0.9.1","2":"0.9.1","version_comment":"Fixed issue with nested classes.","3":"Fixed issue with nested classes.","package":"protodef_0.9.1.tar.gz","4":"protodef_0.9.1.tar.gz","src_id":"10537","5":"10537","creation_date":"1241565290","6":"1241565290"},{"0":"2624","vim_version":"7.2","1":"7.2","script_version":"0.9.0","2":"0.9.0","version_comment":"Initial upload","3":"Initial upload","package":"protodef_0.9.0.tar.gz","4":"protodef_0.9.0.tar.gz","src_id":"10507","5":"10507","creation_date":"1241284422","6":"1241284422"}]},"2623":{"script_id":"2623","0":"2623","script_name":"TODO List","1":"TODO List","script_type":"syntax","2":"syntax","summary":"Syntax highlighting for a todo list","3":"Syntax highlighting for a todo list","description":"Highlights a basic todo list  \r\n\r\nDates of the form dd\/mm\/yy are highlighted\r\n\r\nMajor comments are marked with ==> at the begining of the item\r\nMinor comments are marked with --> at the begining of the item\r\n\r\nTODO, INPROGRESS  and DONE are all highlighted differently and if comments are required with the status then these can be highlighted by writing in the form:\r\n\r\n**DONE this job is done and this is its comment**\r\n\r\nfor an example look at\r\nhttp:\/\/www.mth.kcl.ac.uk\/~matturry\/todo.png","4":"Highlights a basic todo list  \r\n\r\nDates of the form dd\/mm\/yy are highlighted\r\n\r\nMajor comments are marked with ==> at the begining of the item\r\nMinor comments are marked with --> at the begining of the item\r\n\r\nTODO, INPROGRESS  and DONE are all highlighted differently and if comments are required with the status then these can be highlighted by writing in the form:\r\n\r\n**DONE this job is done and this is its comment**\r\n\r\nfor an example look at\r\nhttp:\/\/www.mth.kcl.ac.uk\/~matturry\/todo.png","install_details":"copy to syntax folder\r\n\r\nto set highlighting of the file to be todo use the command\r\n':set syntax=todo'\r\n","5":"copy to syntax folder\r\n\r\nto set highlighting of the file to be todo use the command\r\n':set syntax=todo'\r\n","first_name":"Matthew","6":"Matthew","last_name":"Urry","7":"Urry","releases":[{"0":"2623","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"todo.vim","4":"todo.vim","src_id":"10488","5":"10488","creation_date":"1241007137","6":"1241007137"}]},"2622":{"script_id":"2622","0":"2622","script_name":"ku-quickfix","1":"ku-quickfix","script_type":"utility","2":"utility","summary":"ku source: quickfix","3":"ku source: quickfix","description":"*ku-quickfix* is a source for |ku| to deal with |quickfix|.  You can choose\r\none from many files in the current quickfix list and do some action on it.\r\n\r\n\r\nRequirements:\r\n- Vim 7.2 or later\r\n- |ku| 0.2.0 or later (vimscript#2337)\r\n\r\nLatest version:\r\nhttp:\/\/github.com\/kana\/vim-ku-quickfix\r\n\r\nDocument in HTML format:\r\nhttp:\/\/kana.github.com\/config\/vim\/ku-quickfix.html","4":"*ku-quickfix* is a source for |ku| to deal with |quickfix|.  You can choose\r\none from many files in the current quickfix list and do some action on it.\r\n\r\n\r\nRequirements:\r\n- Vim 7.2 or later\r\n- |ku| 0.2.0 or later (vimscript#2337)\r\n\r\nLatest version:\r\nhttp:\/\/github.com\/kana\/vim-ku-quickfix\r\n\r\nDocument in HTML format:\r\nhttp:\/\/kana.github.com\/config\/vim\/ku-quickfix.html","install_details":"...","5":"...","first_name":"Kana","6":"Kana","last_name":"Natsuno","7":"Natsuno","releases":[{"0":"2622","vim_version":"7.0","1":"7.0","script_version":"0.1.1","2":"0.1.1","version_comment":"- Update for ku 0.2.1.\n- Refactor a bit.","3":"- Update for ku 0.2.1.\n- Refactor a bit.","package":"vim-ku-quickfix-0.1.1.zip","4":"vim-ku-quickfix-0.1.1.zip","src_id":"10514","5":"10514","creation_date":"1241374557","6":"1241374557"},{"0":"2622","vim_version":"7.0","1":"7.0","script_version":"0.1.0","2":"0.1.0","version_comment":"Initial upload","3":"Initial upload","package":"vim-ku-quickfix-0.1.0.zip","4":"vim-ku-quickfix-0.1.0.zip","src_id":"10478","5":"10478","creation_date":"1240919856","6":"1240919856"}]},"2621":{"script_id":"2621","0":"2621","script_name":"up2picasaweb","1":"up2picasaweb","script_type":"utility","2":"utility","summary":"upload image to picasaweb with vim","3":"upload image to picasaweb with vim","description":"upload a image file with vim form local to your picasaweb ablum using the Picasa Web Albums Data API and return the url of your upoad file which can be embed in html","4":"upload a image file with vim form local to your picasaweb ablum using the Picasa Web Albums Data API and return the url of your upoad file which can be embed in html","install_details":"you must have python and python-gdata installed  \r\nput it into your ~\/.vim\/plugin dirctory \"\r\nedit the setting section in line 33-35","5":"you must have python and python-gdata installed  \r\nput it into your ~\/.vim\/plugin dirctory \"\r\nedit the setting section in line 33-35","first_name":"Tensecor","6":"Tensecor","last_name":"Yin","7":"Yin","releases":[{"0":"2621","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"update","3":"update","package":"up2picasaweb.vim","4":"up2picasaweb.vim","src_id":"10473","5":"10473","creation_date":"1240918506","6":"1240918506"}]},"2620":{"script_id":"2620","0":"2620","script_name":"neocomplcache","1":"neocomplcache","script_type":"utility","2":"utility","summary":"Ultimate auto completion system for Vim","3":"Ultimate auto completion system for Vim","description":"The latest version is in github.\r\nhttp:\/\/github.com\/Shougo\/neocomplcache\/tree\/master\r\n\r\nScreen shots:\r\nOriginal filename completion.\r\nhttp:\/\/1.bp.blogspot.com\/_ci2yBnqzJgM\/TD1O5_bOQ2I\/AAAAAAAAADE\/vHf9Xg_mrTI\/s1600\/filename_complete.png\r\nOmni completion.\r\nhttp:\/\/2.bp.blogspot.com\/_ci2yBnqzJgM\/TD1PTolkTBI\/AAAAAAAAADU\/knJ3eniuHWI\/s1600\/omni_complete.png\r\nCompletion with vimshell(http:\/\/github.com\/Shougo\/vimshell).\r\nhttp:\/\/1.bp.blogspot.com\/_ci2yBnqzJgM\/TD1PLfdQrwI\/AAAAAAAAADM\/2pSFRTHwYOY\/s1600\/neocomplcache_with_vimshell.png\r\nVim completion.\r\nhttp:\/\/1.bp.blogspot.com\/_ci2yBnqzJgM\/TD1PfKTlwnI\/AAAAAAAAADs\/nOGWTRLuae8\/s1600\/vim_complete.png\r\n\r\nSetting examples:\r\n\" Disable AutoComplPop.\r\nlet g:acp_enableAtStartup = 0\r\n\" Use neocomplcache.\r\nlet g:neocomplcache_enable_at_startup = 1\r\n\" Use smartcase.\r\nlet g:neocomplcache_enable_smart_case = 1\r\n\" Use camel case completion.\r\nlet g:neocomplcache_enable_camel_case_completion = 1\r\n\" Use underbar completion.\r\nlet g:neocomplcache_enable_underbar_completion = 1\r\n\" Set minimum syntax keyword length.\r\nlet g:neocomplcache_min_syntax_length = 3\r\nlet g:neocomplcache_lock_buffer_name_pattern = '\\*ku\\*'\r\n\r\n\" Define dictionary.\r\nlet g:neocomplcache_dictionary_filetype_lists = {\r\n    \\ 'default' : '',\r\n    \\ 'vimshell' : $HOME.'\/.vimshell_hist',\r\n    \\ 'scheme' : $HOME.'\/.gosh_completions'\r\n    \\ }\r\n\t\t\r\n\" Define keyword.\r\nif !exists('g:neocomplcache_keyword_patterns')\r\n    let g:neocomplcache_keyword_patterns = {}\r\nendif\r\nlet g:neocomplcache_keyword_patterns['default'] = '\\h\\w*'\r\n\r\n\" Plugin key-mappings.\r\ninoremap <expr><C-g>     neocomplcache#undo_completion()\r\ninoremap <expr><C-l>     neocomplcache#complete_common_string()\r\n\r\n\" Recommended key-mappings.\r\n\" <CR>: close popup and save indent.\r\ninoremap <expr><CR>  neocomplcache#smart_close_popup() . \"\\<CR>\"\r\n\" <TAB>: completion.\r\ninoremap <expr><TAB>  pumvisible() ? \"\\<C-n>\" : \"\\<TAB>\"\r\n\" <C-h>, <BS>: close popup and delete backword char.\r\ninoremap <expr><C-h> neocomplcache#smart_close_popup().\"\\<C-h>\"\r\ninoremap <expr><BS> neocomplcache#smart_close_popup().\"\\<C-h>\"\r\ninoremap <expr><C-y>  neocomplcache#close_popup()\r\ninoremap <expr><C-e>  neocomplcache#cancel_popup()\r\n\r\n\" AutoComplPop like behavior.\r\n\"let g:neocomplcache_enable_auto_select = 1\r\n\t\r\n\" Shell like behavior(not recommended).\r\n\"set completeopt+=longest\r\n\"let g:neocomplcache_enable_auto_select = 1\r\n\"let g:neocomplcache_disable_auto_complete = 1\r\n\"inoremap <expr><TAB>  pumvisible() ? \"\\<Down>\" : \"\\<TAB>\"\r\n\"inoremap <expr><CR>  neocomplcache#smart_close_popup() . \"\\<CR>\"","4":"The latest version is in github.\r\nhttp:\/\/github.com\/Shougo\/neocomplcache\/tree\/master\r\n\r\nScreen shots:\r\nOriginal filename completion.\r\nhttp:\/\/1.bp.blogspot.com\/_ci2yBnqzJgM\/TD1O5_bOQ2I\/AAAAAAAAADE\/vHf9Xg_mrTI\/s1600\/filename_complete.png\r\nOmni completion.\r\nhttp:\/\/2.bp.blogspot.com\/_ci2yBnqzJgM\/TD1PTolkTBI\/AAAAAAAAADU\/knJ3eniuHWI\/s1600\/omni_complete.png\r\nCompletion with vimshell(http:\/\/github.com\/Shougo\/vimshell).\r\nhttp:\/\/1.bp.blogspot.com\/_ci2yBnqzJgM\/TD1PLfdQrwI\/AAAAAAAAADM\/2pSFRTHwYOY\/s1600\/neocomplcache_with_vimshell.png\r\nVim completion.\r\nhttp:\/\/1.bp.blogspot.com\/_ci2yBnqzJgM\/TD1PfKTlwnI\/AAAAAAAAADs\/nOGWTRLuae8\/s1600\/vim_complete.png\r\n\r\nSetting examples:\r\n\" Disable AutoComplPop.\r\nlet g:acp_enableAtStartup = 0\r\n\" Use neocomplcache.\r\nlet g:neocomplcache_enable_at_startup = 1\r\n\" Use smartcase.\r\nlet g:neocomplcache_enable_smart_case = 1\r\n\" Use camel case completion.\r\nlet g:neocomplcache_enable_camel_case_completion = 1\r\n\" Use underbar completion.\r\nlet g:neocomplcache_enable_underbar_completion = 1\r\n\" Set minimum syntax keyword length.\r\nlet g:neocomplcache_min_syntax_length = 3\r\nlet g:neocomplcache_lock_buffer_name_pattern = '\\*ku\\*'\r\n\r\n\" Define dictionary.\r\nlet g:neocomplcache_dictionary_filetype_lists = {\r\n    \\ 'default' : '',\r\n    \\ 'vimshell' : $HOME.'\/.vimshell_hist',\r\n    \\ 'scheme' : $HOME.'\/.gosh_completions'\r\n    \\ }\r\n\t\t\r\n\" Define keyword.\r\nif !exists('g:neocomplcache_keyword_patterns')\r\n    let g:neocomplcache_keyword_patterns = {}\r\nendif\r\nlet g:neocomplcache_keyword_patterns['default'] = '\\h\\w*'\r\n\r\n\" Plugin key-mappings.\r\ninoremap <expr><C-g>     neocomplcache#undo_completion()\r\ninoremap <expr><C-l>     neocomplcache#complete_common_string()\r\n\r\n\" Recommended key-mappings.\r\n\" <CR>: close popup and save indent.\r\ninoremap <expr><CR>  neocomplcache#smart_close_popup() . \"\\<CR>\"\r\n\" <TAB>: completion.\r\ninoremap <expr><TAB>  pumvisible() ? \"\\<C-n>\" : \"\\<TAB>\"\r\n\" <C-h>, <BS>: close popup and delete backword char.\r\ninoremap <expr><C-h> neocomplcache#smart_close_popup().\"\\<C-h>\"\r\ninoremap <expr><BS> neocomplcache#smart_close_popup().\"\\<C-h>\"\r\ninoremap <expr><C-y>  neocomplcache#close_popup()\r\ninoremap <expr><C-e>  neocomplcache#cancel_popup()\r\n\r\n\" AutoComplPop like behavior.\r\n\"let g:neocomplcache_enable_auto_select = 1\r\n\t\r\n\" Shell like behavior(not recommended).\r\n\"set completeopt+=longest\r\n\"let g:neocomplcache_enable_auto_select = 1\r\n\"let g:neocomplcache_disable_auto_complete = 1\r\n\"inoremap <expr><TAB>  pumvisible() ? \"\\<Down>\" : \"\\<TAB>\"\r\n\"inoremap <expr><CR>  neocomplcache#smart_close_popup() . \"\\<CR>\"","install_details":"1: Extract .zip file and install to your $VIMRUNTIME.\r\n2: Execute :NeoComplCacheEnable command or \r\nlet g:neocomplcache_enable_at_startup = 1\r\nin your .vimrc.\r\n","5":"1: Extract .zip file and install to your $VIMRUNTIME.\r\n2: Execute :NeoComplCacheEnable command or \r\nlet g:neocomplcache_enable_at_startup = 1\r\nin your .vimrc.\r\n","first_name":"Shougo","6":"Shougo","last_name":"Matsushita","7":"Matsushita","releases":[{"0":"2620","vim_version":"7.2","1":"7.2","script_version":"8.0","2":"8.0","version_comment":"- Added :NeoComplCacheClean command.\r\n- Added sorter_length.\r\n- Changed default rank in omni_complete.\r\n- Changed filename_complete behavior.\r\n- Changed g:neocomplcache_enable_auto_close_preview default value.\r\n- Changed g:neocomplcache_temporary_dir default value.\r\n- Deleted abbrev_complete source.\r\n- Deleted debug message.\r\n- Disabled restore of foldinfo.\r\n- Fixed completion error in vim_complete.\r\n- Fixed g:neocomplcache_same_filetype_lists error.\r\n- Fixed initialization problem using neocomplcache#initialize().\r\n- Fixed neocomplcache initialization.\r\n- Fixed refresh behavior.\r\n- Fixed search patterns behavior.\r\n- Improved cache behavior.\r\n- Improved compare_rank.\r\n- Improved complete words behavior.\r\n- Improved documentation.\r\n- Improved rank behavior.\r\n- Improved remove next keyword behavior.\r\n- Improved restore of window position.\r\n- Improved save foldinfo feature.\r\n- Optimised memory.\r\n- Supported string cache.","3":"- Added :NeoComplCacheClean command.\r\n- Added sorter_length.\r\n- Changed default rank in omni_complete.\r\n- Changed filename_complete behavior.\r\n- Changed g:neocomplcache_enable_auto_close_preview default value.\r\n- Changed g:neocomplcache_temporary_dir default value.\r\n- Deleted abbrev_complete source.\r\n- Deleted debug message.\r\n- Disabled restore of foldinfo.\r\n- Fixed completion error in vim_complete.\r\n- Fixed g:neocomplcache_same_filetype_lists error.\r\n- Fixed initialization problem using neocomplcache#initialize().\r\n- Fixed neocomplcache initialization.\r\n- Fixed refresh behavior.\r\n- Fixed search patterns behavior.\r\n- Improved cache behavior.\r\n- Improved compare_rank.\r\n- Improved complete words behavior.\r\n- Improved documentation.\r\n- Improved rank behavior.\r\n- Improved remove next keyword behavior.\r\n- Improved restore of window position.\r\n- Improved save foldinfo feature.\r\n- Optimised memory.\r\n- Supported string cache.","package":"neocomplcache-8.0.zip","4":"neocomplcache-8.0.zip","src_id":"20093","5":"20093","creation_date":"1368315690","6":"1368315690"},{"0":"2620","vim_version":"7.2","1":"7.2","script_version":"7.2","2":"7.2","version_comment":"- Added \/ delimiter for filename_complete.\r\n- Added FAQ section.\r\n- Added b:neocomplcache_sources_list.\r\n- Added default include files in include_file.\r\n- Added filename_include source.\r\n- Added g:neocomplcache_disabled_sources_list option.\r\n- Added g:neocomplcache_enable_auto_close_preview.\r\n- Added g:neocomplcache_force_omni_patterns variable.\r\n- Added g:neocomplcache_skip_auto_completion_time option.\r\n- Added g:neocomplcache_sources_list option.\r\n- Added g:neocomplcache_wildcard_characters option.\r\n- Added less support.\r\n- Added neocomplcache#compare_human compare function.\r\n- Added neocomplcache#disable_default_dictionary().\r\n- Added neocomplcache#get_context_filetype_range().\r\n- Added neocomplcache#initialize().\r\n- Added neocomplcache#is_enabled_source().\r\n- Added neocomplcache__convertable attribute.\r\n- Added skip message in skip completion.\r\n- Added todo section.\r\n- Changed check_source() behavior in buffer_complete.\r\n- Changed default cache lines in nofile buffer.\r\n- Changed g:neocomplcache_enable_underbar_completion and\r\n- Changed g:neocomplcache_same_filetype_lists initialization.\r\n- Changed neocomplcache#get_context_filetype_range() behavior.\r\n- Changed underbar completion and camel case completion behaviors.\r\n- Check source is enabled in include_complete.\r\n- Convert to full path in dictionary_complete.\r\n- Deleted :NeoComplCacheSaveCache command.\r\n- Deleted <Plug>(neocomplcache_start_unite_snippet) mapping.\r\n- Deleted keyword_complete source.\r\n- Deleted neocomplcache#prev_word().\r\n- Deleted omni_complete wildcard support.\r\n- Deleted save cache behavior.\r\n- Disabled vim include functions.\r\n- Don't delete longest completeopt.\r\n- Fixed \"skipped\" behavior.\r\n- Fixed :NeoComplCacheAutoCompletionLength documentation.\r\n- Fixed autocmd initialization.\r\n- Fixed buffer cache.\r\n- Fixed caching behavior.\r\n- Fixed check force_omni_patterns.\r\n- Fixed complete variables in vim_complete.\r\n- Fixed complete_common_string.\r\n- Fixed completefunc return value.\r\n- Fixed completion problem in InsertCharPre.\r\n- Fixed context filetype range.\r\n- Fixed cur_text problem.\r\n- Fixed delimiter.\r\n- Fixed documentation for neosnippet.\r\n- Fixed error in neocomplcache#initialize().\r\n- Fixed error in vim_complete.\r\n- Fixed foldmethod problem.\r\n- Fixed for camel case completion.\r\n- Fixed for check sources.\r\n- Fixed for eskk integration problem.\r\n- Fixed for eskk.\r\n- Fixed for foldmethod.\r\n- Fixed for formatoptions.\r\n- Fixed for malloc in include_complete.\r\n- Fixed for prefetch check.\r\n- Fixed for prefetch.\r\n- Fixed for textwidth.\r\n- Fixed force omni patterns.\r\n- Fixed force omnifunc problem.\r\n- Fixed include pattern.\r\n- Fixed include_complete error.\r\n- Fixed include_complete initialization.\r\n- Fixed initialization.\r\n- Fixed keyword escape error.\r\n- Fixed member_complete error.\r\n- Fixed neocomplcache enabled check.\r\n- Fixed neocomplcache#complete_common_string().\r\n- Fixed omni_complete error.\r\n- Fixed opening folds' bug.\r\n- Fixed python default include paths.\r\n- Fixed skip auto completion behavior.\r\n- Fixed skip behavior.\r\n- Fixed source initialization for lazy loading.\r\n- Fixed start omni complete.\r\n- Fixed toggle lock.\r\n- Fixed underbar completion and camel case completion.\r\n- Fixed undo completion behavior.\r\n- Fixed vim_complete behavior.\r\n- Fixed vim_complete error.\r\n- Implemented refresh automatically.\r\n- Improved :NeoComplCacheCachingBuffer behavior.\r\n- Improved <Plug>(neocomplcache_start_auto_complete).\r\n- Improved C# support.\r\n- Improved FAQ section.\r\n- Improved auto completion.\r\n- Improved check of omnifunc.\r\n- Improved commands definitions.\r\n- Improved completeopt behavior.\r\n- Improved completion_length.\r\n- Improved context filetype initialization.\r\n- Improved default pattern behavior.\r\n- Improved default sort behavior.\r\n- Improved delimiter patterns behavior.\r\n- Improved detect paste behavior.\r\n- Improved documentation.\r\n- Improved filename delimiter behavior.\r\n- Improved filename pattern in filename_complete.\r\n- Improved filename pattern.\r\n- Improved for caching buffer.\r\n- Improved for foldmethod.\r\n- Improved for wildcard.\r\n- Improved fuzzy search behavior.\r\n- Improved g:neocomplcache_same_filetype_lists.\r\n- Improved initialization timing.\r\n- Improved initialization.\r\n- Improved keymappings.\r\n- Improved lock behavior.\r\n- Improved lock sources behavior.\r\n- Improved making cache behavior(testing).\r\n- Improved manual complete.\r\n- Improved member completion.\r\n- Improved neocomplcache initialization.\r\n- Improved neocomplcache#check_invalid_omnifunc().\r\n- Improved neocomplcache#sources#buffer_complete#caching_current_line().\r\n- Improved neocomplcache#sources#include_complete#get_include_files()\r\n- Improved recache behavior.\r\n- Improved save foldinfo behavior.\r\n- Improved search base path.\r\n- Improved set dictionary helper.\r\n- Improved skip auto completion.\r\n- Improved skip complete behavior.\r\n- Improved skip completion behavior.\r\n- Improved skip next complete behavior.\r\n- Improved source initialization.\r\n- Improved sudo check.\r\n- Improved text mode.\r\n- Improved unpack behavior.\r\n- Improved vim_complete.\r\n- Open folds in InsertEnter.\r\n- Optimised fuzzy completion.\r\n- Optimised match filter.\r\n- Optimised vim_complete.\r\n- Refactored script variables.\r\n- Refactored skip next completion feature.\r\n- Save foldmethod automatically.\r\n- Skip omni_complete in string literal.\r\n- Supported 7.3.768.\r\n- Supported require_relative in filename_complete.\r\n- Supported sass omni completion.\r\n- Supported scss.\r\n- Updated vital.\r\n- Use fnameescape().\r\n- Use partial match in <Plug>(neocomplcache_start_unite_complete).","3":"- Added \/ delimiter for filename_complete.\r\n- Added FAQ section.\r\n- Added b:neocomplcache_sources_list.\r\n- Added default include files in include_file.\r\n- Added filename_include source.\r\n- Added g:neocomplcache_disabled_sources_list option.\r\n- Added g:neocomplcache_enable_auto_close_preview.\r\n- Added g:neocomplcache_force_omni_patterns variable.\r\n- Added g:neocomplcache_skip_auto_completion_time option.\r\n- Added g:neocomplcache_sources_list option.\r\n- Added g:neocomplcache_wildcard_characters option.\r\n- Added less support.\r\n- Added neocomplcache#compare_human compare function.\r\n- Added neocomplcache#disable_default_dictionary().\r\n- Added neocomplcache#get_context_filetype_range().\r\n- Added neocomplcache#initialize().\r\n- Added neocomplcache#is_enabled_source().\r\n- Added neocomplcache__convertable attribute.\r\n- Added skip message in skip completion.\r\n- Added todo section.\r\n- Changed check_source() behavior in buffer_complete.\r\n- Changed default cache lines in nofile buffer.\r\n- Changed g:neocomplcache_enable_underbar_completion and\r\n- Changed g:neocomplcache_same_filetype_lists initialization.\r\n- Changed neocomplcache#get_context_filetype_range() behavior.\r\n- Changed underbar completion and camel case completion behaviors.\r\n- Check source is enabled in include_complete.\r\n- Convert to full path in dictionary_complete.\r\n- Deleted :NeoComplCacheSaveCache command.\r\n- Deleted <Plug>(neocomplcache_start_unite_snippet) mapping.\r\n- Deleted keyword_complete source.\r\n- Deleted neocomplcache#prev_word().\r\n- Deleted omni_complete wildcard support.\r\n- Deleted save cache behavior.\r\n- Disabled vim include functions.\r\n- Don't delete longest completeopt.\r\n- Fixed \"skipped\" behavior.\r\n- Fixed :NeoComplCacheAutoCompletionLength documentation.\r\n- Fixed autocmd initialization.\r\n- Fixed buffer cache.\r\n- Fixed caching behavior.\r\n- Fixed check force_omni_patterns.\r\n- Fixed complete variables in vim_complete.\r\n- Fixed complete_common_string.\r\n- Fixed completefunc return value.\r\n- Fixed completion problem in InsertCharPre.\r\n- Fixed context filetype range.\r\n- Fixed cur_text problem.\r\n- Fixed delimiter.\r\n- Fixed documentation for neosnippet.\r\n- Fixed error in neocomplcache#initialize().\r\n- Fixed error in vim_complete.\r\n- Fixed foldmethod problem.\r\n- Fixed for camel case completion.\r\n- Fixed for check sources.\r\n- Fixed for eskk integration problem.\r\n- Fixed for eskk.\r\n- Fixed for foldmethod.\r\n- Fixed for formatoptions.\r\n- Fixed for malloc in include_complete.\r\n- Fixed for prefetch check.\r\n- Fixed for prefetch.\r\n- Fixed for textwidth.\r\n- Fixed force omni patterns.\r\n- Fixed force omnifunc problem.\r\n- Fixed include pattern.\r\n- Fixed include_complete error.\r\n- Fixed include_complete initialization.\r\n- Fixed initialization.\r\n- Fixed keyword escape error.\r\n- Fixed member_complete error.\r\n- Fixed neocomplcache enabled check.\r\n- Fixed neocomplcache#complete_common_string().\r\n- Fixed omni_complete error.\r\n- Fixed opening folds' bug.\r\n- Fixed python default include paths.\r\n- Fixed skip auto completion behavior.\r\n- Fixed skip behavior.\r\n- Fixed source initialization for lazy loading.\r\n- Fixed start omni complete.\r\n- Fixed toggle lock.\r\n- Fixed underbar completion and camel case completion.\r\n- Fixed undo completion behavior.\r\n- Fixed vim_complete behavior.\r\n- Fixed vim_complete error.\r\n- Implemented refresh automatically.\r\n- Improved :NeoComplCacheCachingBuffer behavior.\r\n- Improved <Plug>(neocomplcache_start_auto_complete).\r\n- Improved C# support.\r\n- Improved FAQ section.\r\n- Improved auto completion.\r\n- Improved check of omnifunc.\r\n- Improved commands definitions.\r\n- Improved completeopt behavior.\r\n- Improved completion_length.\r\n- Improved context filetype initialization.\r\n- Improved default pattern behavior.\r\n- Improved default sort behavior.\r\n- Improved delimiter patterns behavior.\r\n- Improved detect paste behavior.\r\n- Improved documentation.\r\n- Improved filename delimiter behavior.\r\n- Improved filename pattern in filename_complete.\r\n- Improved filename pattern.\r\n- Improved for caching buffer.\r\n- Improved for foldmethod.\r\n- Improved for wildcard.\r\n- Improved fuzzy search behavior.\r\n- Improved g:neocomplcache_same_filetype_lists.\r\n- Improved initialization timing.\r\n- Improved initialization.\r\n- Improved keymappings.\r\n- Improved lock behavior.\r\n- Improved lock sources behavior.\r\n- Improved making cache behavior(testing).\r\n- Improved manual complete.\r\n- Improved member completion.\r\n- Improved neocomplcache initialization.\r\n- Improved neocomplcache#check_invalid_omnifunc().\r\n- Improved neocomplcache#sources#buffer_complete#caching_current_line().\r\n- Improved neocomplcache#sources#include_complete#get_include_files()\r\n- Improved recache behavior.\r\n- Improved save foldinfo behavior.\r\n- Improved search base path.\r\n- Improved set dictionary helper.\r\n- Improved skip auto completion.\r\n- Improved skip complete behavior.\r\n- Improved skip completion behavior.\r\n- Improved skip next complete behavior.\r\n- Improved source initialization.\r\n- Improved sudo check.\r\n- Improved text mode.\r\n- Improved unpack behavior.\r\n- Improved vim_complete.\r\n- Open folds in InsertEnter.\r\n- Optimised fuzzy completion.\r\n- Optimised match filter.\r\n- Optimised vim_complete.\r\n- Refactored script variables.\r\n- Refactored skip next completion feature.\r\n- Save foldmethod automatically.\r\n- Skip omni_complete in string literal.\r\n- Supported 7.3.768.\r\n- Supported require_relative in filename_complete.\r\n- Supported sass omni completion.\r\n- Supported scss.\r\n- Updated vital.\r\n- Use fnameescape().\r\n- Use partial match in <Plug>(neocomplcache_start_unite_complete).","package":"neocomplcache-7.2.zip","4":"neocomplcache-7.2.zip","src_id":"19580","5":"19580","creation_date":"1362198824","6":"1362198824"},{"0":"2620","vim_version":"7.2","1":"7.2","script_version":"7.1","2":"7.1","version_comment":"- Added :NeoComplCacheSetFileType command.\r\n- Added FAQ.\r\n- Added _ omnifunc.\r\n- Added g:neocomplcache_tags_caching_limit_file_size variable.\r\n- Added g:neocomplcache_use_vimproc option.\r\n- Added neocomplcache#complete_check().\r\n- Added word order function.\r\n- Change g:neocomplcache_enable_prefetch default value.\r\n- Changed filename_complete default rank.\r\n- Deleted completefunc_complete source.\r\n- Fixed for css omni_complete.\r\n- Fixed for fuzzyfinder.\r\n- Fixed for g:neocomplcache_enable_insert_char_pre.\r\n- Fixed for tags_complete.\r\n- Fixed for vimshell.\r\n- Fixed g:neocomplcache_disable_auto_complete problem.\r\n- Fixed g:neocomplcache_enable_prefetch initialization.\r\n- Fixed include filename completion.\r\n- Fixed neocomplcache#complete_common_string().\r\n- Fixed neocomplcache#is_plugin_locked() error.\r\n- Fixed omni patterns for c and cpp.\r\n- Fixed omni_complete error.\r\n- Fixed skip filename patterns.\r\n- Fixed tags_complete problem.\r\n- Fixed warning mappings.\r\n- Ignore document tags in tags_complete.\r\n- Refactored cache.vim.\r\n- Set refresh always.\r\n- Silent mapping.\r\n- Supported Vim 7.3.519 feature.\r\n- Supported python3.\r\n- Supported wildcard import in include_complete.\r\n- Updated examples.\r\n- Updated features dict.\r\n- Updated vital.","3":"- Added :NeoComplCacheSetFileType command.\r\n- Added FAQ.\r\n- Added _ omnifunc.\r\n- Added g:neocomplcache_tags_caching_limit_file_size variable.\r\n- Added g:neocomplcache_use_vimproc option.\r\n- Added neocomplcache#complete_check().\r\n- Added word order function.\r\n- Change g:neocomplcache_enable_prefetch default value.\r\n- Changed filename_complete default rank.\r\n- Deleted completefunc_complete source.\r\n- Fixed for css omni_complete.\r\n- Fixed for fuzzyfinder.\r\n- Fixed for g:neocomplcache_enable_insert_char_pre.\r\n- Fixed for tags_complete.\r\n- Fixed for vimshell.\r\n- Fixed g:neocomplcache_disable_auto_complete problem.\r\n- Fixed g:neocomplcache_enable_prefetch initialization.\r\n- Fixed include filename completion.\r\n- Fixed neocomplcache#complete_common_string().\r\n- Fixed neocomplcache#is_plugin_locked() error.\r\n- Fixed omni patterns for c and cpp.\r\n- Fixed omni_complete error.\r\n- Fixed skip filename patterns.\r\n- Fixed tags_complete problem.\r\n- Fixed warning mappings.\r\n- Ignore document tags in tags_complete.\r\n- Refactored cache.vim.\r\n- Set refresh always.\r\n- Silent mapping.\r\n- Supported Vim 7.3.519 feature.\r\n- Supported python3.\r\n- Supported wildcard import in include_complete.\r\n- Updated examples.\r\n- Updated features dict.\r\n- Updated vital.","package":"neocomplcache-7.1.zip","4":"neocomplcache-7.1.zip","src_id":"18521","5":"18521","creation_date":"1346508181","6":"1346508181"},{"0":"2620","vim_version":"7.0","1":"7.0","script_version":"7.0","2":"7.0","version_comment":"- Added :NeoComplCacheLockSource and :NeoComplCacheUnLockSource commands.\r\n- Added g:neocomplcache_enable_insert_char_pre option.\r\n- Added g:neocomplcache_fuzzy_completion_start_length option.\r\n- Added g:neocomplcache_lock_iminsert option.\r\n- Added g:neocomplcache_release_cache_time option.\r\n- Changed g:neocomplcache_enable_prefetch default value.\r\n- Changed g:neocomplcache_manual_completion_start_length default value.\r\n- Check device file in filename_complete.\r\n- Deleted Japanese documentation.\r\n- Deleted local var_dictionary completion in vim_complete.\r\n- Deleted snippet source.\r\n- Deleted vimshell omni fuction pattern.\r\n- Do not set refresh key.\r\n- Enabled beep.\r\n- Fixed Vim search.\r\n- Fixed abbr error in vim_complete source.\r\n- Fixed asynchronous load.\r\n- Fixed asyncronous cache bug.\r\n- Fixed bell problem.\r\n- Fixed buffer_complete cache problem.\r\n- Fixed caching.\r\n- Fixed changed buffer problem.\r\n- Fixed command definition.\r\n- Fixed completion bug.\r\n- Fixed cur_text bug.\r\n- Fixed cur_text check.\r\n- Fixed documentaion.\r\n- Fixed expand().\r\n- Fixed feedkeys() problem.\r\n- Fixed filename escape.\r\n- Fixed filename_complete behavior.\r\n- Fixed filetype error in dictionary_complete source.\r\n- Fixed for g:neocomplcache_enable_prefetch default value.\r\n- Fixed g:neocomplcache_enable_cursor_hold_i behavior.\r\n- Fixed g:neocomplcache_enable_fuzzy_completion documentaion.\r\n- Fixed get_cur_text().\r\n- Fixed make cache bug.\r\n- Fixed on_insert_enter().\r\n- Fixed save cache error.\r\n- Fixed temporary directory initialization.\r\n- Fixed vb keyword pattern.\r\n- Fixed vim keyword pattern.\r\n- Implemented release cache in include_complete.\r\n- Improved :NeoComplCacheToggle behavior.\r\n- Improved Vim version check.\r\n- Improved asyncronous caching behavior.\r\n- Improved asyncronous caching check timing.\r\n- Improved auto caching.\r\n- Improved buffer_complete behavior.\r\n- Improved buffer_complete.\r\n- Improved cache behavior.\r\n- Improved cache event.\r\n- Improved completion source.\r\n- Improved context filetype.\r\n- Improved documentation.\r\n- Improved escape filename.\r\n- Improved filename escape.\r\n- Improved filename pattern.\r\n- Improved filter behavior.\r\n- Improved fuzzy completion behavior.\r\n- Improved g:neocomplcache_cursor_hold_i_time behavior.\r\n- Improved helper function.\r\n- Improved include_complete.\r\n- Improved make cache behavior.\r\n- Improved member_complete behavior.\r\n- Improved omni_complete behavior.\r\n- Improved omnifunc error detection.\r\n- Improved snippets_complete changes description.\r\n- Improved sudo check.\r\n- Improved temporary directory behavior.\r\n- Improved version check.\r\n- Refactored is_windows.\r\n- Renamed g:neocomplcache_filetype_include_lists as g:neocomplcache_context_filetype_lists.\r\n- Renamed g:neocomplcache_plugin_completion_length as g:neocomplcache_source_completion_length.\r\n- Renamed g:neocomplcache_plugin_disable as g:neocomplcache_source_disable.\r\n- Renamed g:neocomplcache_plugin_rank as g:neocomplcache_source_rank.\r\n- Revised documentation.\r\n- Splited snippets_complete.\r\n- Supported Ctrl-x mode fix.\r\n- Updated examples.\r\n- Updated vital.\r\n- Warning if using obsolute mappings.","3":"- Added :NeoComplCacheLockSource and :NeoComplCacheUnLockSource commands.\r\n- Added g:neocomplcache_enable_insert_char_pre option.\r\n- Added g:neocomplcache_fuzzy_completion_start_length option.\r\n- Added g:neocomplcache_lock_iminsert option.\r\n- Added g:neocomplcache_release_cache_time option.\r\n- Changed g:neocomplcache_enable_prefetch default value.\r\n- Changed g:neocomplcache_manual_completion_start_length default value.\r\n- Check device file in filename_complete.\r\n- Deleted Japanese documentation.\r\n- Deleted local var_dictionary completion in vim_complete.\r\n- Deleted snippet source.\r\n- Deleted vimshell omni fuction pattern.\r\n- Do not set refresh key.\r\n- Enabled beep.\r\n- Fixed Vim search.\r\n- Fixed abbr error in vim_complete source.\r\n- Fixed asynchronous load.\r\n- Fixed asyncronous cache bug.\r\n- Fixed bell problem.\r\n- Fixed buffer_complete cache problem.\r\n- Fixed caching.\r\n- Fixed changed buffer problem.\r\n- Fixed command definition.\r\n- Fixed completion bug.\r\n- Fixed cur_text bug.\r\n- Fixed cur_text check.\r\n- Fixed documentaion.\r\n- Fixed expand().\r\n- Fixed feedkeys() problem.\r\n- Fixed filename escape.\r\n- Fixed filename_complete behavior.\r\n- Fixed filetype error in dictionary_complete source.\r\n- Fixed for g:neocomplcache_enable_prefetch default value.\r\n- Fixed g:neocomplcache_enable_cursor_hold_i behavior.\r\n- Fixed g:neocomplcache_enable_fuzzy_completion documentaion.\r\n- Fixed get_cur_text().\r\n- Fixed make cache bug.\r\n- Fixed on_insert_enter().\r\n- Fixed save cache error.\r\n- Fixed temporary directory initialization.\r\n- Fixed vb keyword pattern.\r\n- Fixed vim keyword pattern.\r\n- Implemented release cache in include_complete.\r\n- Improved :NeoComplCacheToggle behavior.\r\n- Improved Vim version check.\r\n- Improved asyncronous caching behavior.\r\n- Improved asyncronous caching check timing.\r\n- Improved auto caching.\r\n- Improved buffer_complete behavior.\r\n- Improved buffer_complete.\r\n- Improved cache behavior.\r\n- Improved cache event.\r\n- Improved completion source.\r\n- Improved context filetype.\r\n- Improved documentation.\r\n- Improved escape filename.\r\n- Improved filename escape.\r\n- Improved filename pattern.\r\n- Improved filter behavior.\r\n- Improved fuzzy completion behavior.\r\n- Improved g:neocomplcache_cursor_hold_i_time behavior.\r\n- Improved helper function.\r\n- Improved include_complete.\r\n- Improved make cache behavior.\r\n- Improved member_complete behavior.\r\n- Improved omni_complete behavior.\r\n- Improved omnifunc error detection.\r\n- Improved snippets_complete changes description.\r\n- Improved sudo check.\r\n- Improved temporary directory behavior.\r\n- Improved version check.\r\n- Refactored is_windows.\r\n- Renamed g:neocomplcache_filetype_include_lists as g:neocomplcache_context_filetype_lists.\r\n- Renamed g:neocomplcache_plugin_completion_length as g:neocomplcache_source_completion_length.\r\n- Renamed g:neocomplcache_plugin_disable as g:neocomplcache_source_disable.\r\n- Renamed g:neocomplcache_plugin_rank as g:neocomplcache_source_rank.\r\n- Revised documentation.\r\n- Splited snippets_complete.\r\n- Supported Ctrl-x mode fix.\r\n- Updated examples.\r\n- Updated vital.\r\n- Warning if using obsolute mappings.","package":"neocomplcache-7.0.zip","4":"neocomplcache-7.0.zip","src_id":"17867","5":"17867","creation_date":"1336145661","6":"1336145661"},{"0":"2620","vim_version":"7.2","1":"7.2","script_version":"6.2","2":"6.2","version_comment":"- Added <Nop> in vim_complete.\r\n- Added <Plug>(neocomplcache_start_unite_quick_match) mapping.\r\n- Added C++11 snippets.\r\n- Added documentation.\r\n- Added g:neocomplcache_compare_function option.\r\n- Added g:neocomplcache_enable_fuzzy_completion option.\r\n- Added g:neocomplcache_enable_prefetch option.\r\n- Added g:neocomplcache_filename_include_exprs option.\r\n- Added g:neocomplcache_filename_include_exts option.\r\n- Added g:neocomplcache_include_functions option.\r\n- Added g:neocomplcache_member_patterns option.\r\n- Added member_complete source.\r\n- Added neocomplcache print debug message.\r\n- Added neocomplcache#sources#include_complete#get_current_include_files().\r\n- Added neocomplcache#start_manual_complete().\r\n- Added neocomplcache#util#get_last_status() function.\r\n- Added tcl support.\r\n- Added vim snippet.\r\n- Applied omni_complete patch(experimental).\r\n- Changed default plugins rank.\r\n- Changed g:neocomplcache_enable_prefetch behavior default value.\r\n- Changed syntax highlight name.\r\n- Check if \"vim\" command is executable.\r\n- Deleted g:neocomplcache_disable_auto_select_buffer_name_pattern option.\r\n- Deleted g:neocomplcache_force_caching_buffer_name_pattern option.\r\n- Deleted obsolute features.\r\n- Deleted obsolute learning.\r\n- Deleted quick match feature.\r\n- Detect sudo vim.\r\n- Disabled refresh by resolved repeat-register problem.\r\n- Fixed Japanese documentation.\r\n- Fixed Vim keyword pattern.\r\n- Fixed auto complete behavior.\r\n- Fixed auto complete flicker.\r\n- Fixed auto select.\r\n- Fixed autocmd args error.\r\n- Fixed buffer_complete bug.\r\n- Fixed conceal syntax.\r\n- Fixed css omni completion pattern.\r\n- Fixed cur_keyword_pos problem.\r\n- Fixed d snippets.\r\n- Fixed detect completefunc.\r\n- Fixed dictionary_complete behavior.\r\n- Fixed examples.\r\n- Fixed expand snippet.\r\n- Fixed expand() problem.\r\n- Fixed feedkeys().\r\n- Fixed file_include source.\r\n- Fixed filename complete escape.\r\n- Fixed filename include complete.\r\n- Fixed filename_complete.\r\n- Fixed filter.\r\n- Fixed finalize error.\r\n- Fixed for IM Problem.\r\n- Fixed for Vim 7.2.\r\n- Fixed for Vim 7.3.319.\r\n- Fixed for eskk.\r\n- Fixed for g:neocomplcache_enable_auto_select.\r\n- Fixed for gdefault option.\r\n- Fixed for refresh always problem(experimental).\r\n- Fixed for rubycomplete.vim.\r\n- Fixed fuzzy completion error.\r\n- Fixed g:neocomplcache_enable_prefetch behavior.\r\n- Fixed g:neocomplcache_text_mode_filetypes default value.\r\n- Fixed get member list error.\r\n- Fixed icase in text mode.\r\n- Fixed include_complete error.\r\n- Fixed member completion.\r\n- Fixed member_complete.\r\n- Fixed modifiable error.\r\n- Fixed neocomplcache#get_complete_results_pos().\r\n- Fixed neocomplcache#sources#snippets_complete#get_snippets().\r\n- Fixed omni_complete preview window.\r\n- Fixed overwrite manual complete.\r\n- Fixed path separator error.\r\n- Fixed php snippet.\r\n- Fixed prefetch problem.\r\n- Fixed prefetch.\r\n- Fixed remove_next_keyword.\r\n- Fixed restore completefunc problem.\r\n- Fixed restore function.\r\n- Fixed ruby omni complete default pattern.\r\n- Fixed s:cur_keyword_str.\r\n- Fixed setline() problem.\r\n- Fixed snippet description.\r\n- Fixed tex snippets.\r\n- Fixed text mode.\r\n- Fixed unite source.\r\n- Fixed updatetime problem.\r\n- Fixed variables initialize.\r\n- Fixed vim keyword pattern.\r\n- Fixed warning.\r\n- Force use glob().\r\n- Improved a bit.\r\n- Improved async from tags.\r\n- Improved c snippet.\r\n- Improved cache check.\r\n- Improved cache.\r\n- Improved caching buffer.\r\n- Improved caching current line.\r\n- Improved calc frequencies.\r\n- Improved check im.\r\n- Improved default rank.\r\n- Improved documentation.\r\n- Improved eval snippet behavior.\r\n- Improved examples.\r\n- Improved expand home.\r\n- Improved filename_complete behavior.\r\n- Improved filename_complete mark.\r\n- Improved filename_complete parse include.\r\n- Improved filtering behavior.\r\n- Improved for learning.\r\n- Improved g:neocomplcache_enable_prefetch behavior.\r\n- Improved gather candidates interface.\r\n- Improved javascript snippets.\r\n- Improved mappings dictionary.\r\n- Improved neocomplcache#get_source_filetypes().\r\n- Improved prefetch.\r\n- Improved python keyword pattern.\r\n- Improved snippet eval.\r\n- Improved snippets delete behavior.\r\n- Improved snippets_complete rank.\r\n- Improved some snippets.\r\n- Improved syntax_complete caching behavior.\r\n- Improved syntax_complete caching.\r\n- Improved tex keyword pattern.\r\n- Improved tex snippets.\r\n- Improved text mode.\r\n- Improved unite#sources#neocomplcache#start_complete() behavior.\r\n- Improved unite#sources#snippet#start_complete()\r\n- Improved vim_complete variables anaylze.\r\n- Improved vim_complete.\r\n- Re-implemented neocomplcache#start_manual_complete().\r\n- Refactored local variable names.\r\n- Refactoringed.\r\n- Renamed g:neocomplcache_max_filename_width to g:neocomplcache_max_menu_width.\r\n- Set :scriptencoding.\r\n- Supported Rhino.\r\n- Supported complete_check().\r\n- Supported conceal feature in snippet_complete(experimental).\r\n- Supported info in omni_complete.\r\n- Supported nyaos.\r\n- Supported php interpreter.\r\n- Use sandbox in eval snippet.\r\n- Use unite#start_complete().\r\n- Use vital.vim cache module.","3":"- Added <Nop> in vim_complete.\r\n- Added <Plug>(neocomplcache_start_unite_quick_match) mapping.\r\n- Added C++11 snippets.\r\n- Added documentation.\r\n- Added g:neocomplcache_compare_function option.\r\n- Added g:neocomplcache_enable_fuzzy_completion option.\r\n- Added g:neocomplcache_enable_prefetch option.\r\n- Added g:neocomplcache_filename_include_exprs option.\r\n- Added g:neocomplcache_filename_include_exts option.\r\n- Added g:neocomplcache_include_functions option.\r\n- Added g:neocomplcache_member_patterns option.\r\n- Added member_complete source.\r\n- Added neocomplcache print debug message.\r\n- Added neocomplcache#sources#include_complete#get_current_include_files().\r\n- Added neocomplcache#start_manual_complete().\r\n- Added neocomplcache#util#get_last_status() function.\r\n- Added tcl support.\r\n- Added vim snippet.\r\n- Applied omni_complete patch(experimental).\r\n- Changed default plugins rank.\r\n- Changed g:neocomplcache_enable_prefetch behavior default value.\r\n- Changed syntax highlight name.\r\n- Check if \"vim\" command is executable.\r\n- Deleted g:neocomplcache_disable_auto_select_buffer_name_pattern option.\r\n- Deleted g:neocomplcache_force_caching_buffer_name_pattern option.\r\n- Deleted obsolute features.\r\n- Deleted obsolute learning.\r\n- Deleted quick match feature.\r\n- Detect sudo vim.\r\n- Disabled refresh by resolved repeat-register problem.\r\n- Fixed Japanese documentation.\r\n- Fixed Vim keyword pattern.\r\n- Fixed auto complete behavior.\r\n- Fixed auto complete flicker.\r\n- Fixed auto select.\r\n- Fixed autocmd args error.\r\n- Fixed buffer_complete bug.\r\n- Fixed conceal syntax.\r\n- Fixed css omni completion pattern.\r\n- Fixed cur_keyword_pos problem.\r\n- Fixed d snippets.\r\n- Fixed detect completefunc.\r\n- Fixed dictionary_complete behavior.\r\n- Fixed examples.\r\n- Fixed expand snippet.\r\n- Fixed expand() problem.\r\n- Fixed feedkeys().\r\n- Fixed file_include source.\r\n- Fixed filename complete escape.\r\n- Fixed filename include complete.\r\n- Fixed filename_complete.\r\n- Fixed filter.\r\n- Fixed finalize error.\r\n- Fixed for IM Problem.\r\n- Fixed for Vim 7.2.\r\n- Fixed for Vim 7.3.319.\r\n- Fixed for eskk.\r\n- Fixed for g:neocomplcache_enable_auto_select.\r\n- Fixed for gdefault option.\r\n- Fixed for refresh always problem(experimental).\r\n- Fixed for rubycomplete.vim.\r\n- Fixed fuzzy completion error.\r\n- Fixed g:neocomplcache_enable_prefetch behavior.\r\n- Fixed g:neocomplcache_text_mode_filetypes default value.\r\n- Fixed get member list error.\r\n- Fixed icase in text mode.\r\n- Fixed include_complete error.\r\n- Fixed member completion.\r\n- Fixed member_complete.\r\n- Fixed modifiable error.\r\n- Fixed neocomplcache#get_complete_results_pos().\r\n- Fixed neocomplcache#sources#snippets_complete#get_snippets().\r\n- Fixed omni_complete preview window.\r\n- Fixed overwrite manual complete.\r\n- Fixed path separator error.\r\n- Fixed php snippet.\r\n- Fixed prefetch problem.\r\n- Fixed prefetch.\r\n- Fixed remove_next_keyword.\r\n- Fixed restore completefunc problem.\r\n- Fixed restore function.\r\n- Fixed ruby omni complete default pattern.\r\n- Fixed s:cur_keyword_str.\r\n- Fixed setline() problem.\r\n- Fixed snippet description.\r\n- Fixed tex snippets.\r\n- Fixed text mode.\r\n- Fixed unite source.\r\n- Fixed updatetime problem.\r\n- Fixed variables initialize.\r\n- Fixed vim keyword pattern.\r\n- Fixed warning.\r\n- Force use glob().\r\n- Improved a bit.\r\n- Improved async from tags.\r\n- Improved c snippet.\r\n- Improved cache check.\r\n- Improved cache.\r\n- Improved caching buffer.\r\n- Improved caching current line.\r\n- Improved calc frequencies.\r\n- Improved check im.\r\n- Improved default rank.\r\n- Improved documentation.\r\n- Improved eval snippet behavior.\r\n- Improved examples.\r\n- Improved expand home.\r\n- Improved filename_complete behavior.\r\n- Improved filename_complete mark.\r\n- Improved filename_complete parse include.\r\n- Improved filtering behavior.\r\n- Improved for learning.\r\n- Improved g:neocomplcache_enable_prefetch behavior.\r\n- Improved gather candidates interface.\r\n- Improved javascript snippets.\r\n- Improved mappings dictionary.\r\n- Improved neocomplcache#get_source_filetypes().\r\n- Improved prefetch.\r\n- Improved python keyword pattern.\r\n- Improved snippet eval.\r\n- Improved snippets delete behavior.\r\n- Improved snippets_complete rank.\r\n- Improved some snippets.\r\n- Improved syntax_complete caching behavior.\r\n- Improved syntax_complete caching.\r\n- Improved tex keyword pattern.\r\n- Improved tex snippets.\r\n- Improved text mode.\r\n- Improved unite#sources#neocomplcache#start_complete() behavior.\r\n- Improved unite#sources#snippet#start_complete()\r\n- Improved vim_complete variables anaylze.\r\n- Improved vim_complete.\r\n- Re-implemented neocomplcache#start_manual_complete().\r\n- Refactored local variable names.\r\n- Refactoringed.\r\n- Renamed g:neocomplcache_max_filename_width to g:neocomplcache_max_menu_width.\r\n- Set :scriptencoding.\r\n- Supported Rhino.\r\n- Supported complete_check().\r\n- Supported conceal feature in snippet_complete(experimental).\r\n- Supported info in omni_complete.\r\n- Supported nyaos.\r\n- Supported php interpreter.\r\n- Use sandbox in eval snippet.\r\n- Use unite#start_complete().\r\n- Use vital.vim cache module.","package":"neocomplcache-6.2.zip","4":"neocomplcache-6.2.zip","src_id":"17365","5":"17365","creation_date":"1328154927","6":"1328154927"},{"0":"2620","vim_version":"7.0","1":"7.0","script_version":"6.1","2":"6.1","version_comment":"zipped version.","3":"zipped version.","package":"neocomplcache-6.1.zip","4":"neocomplcache-6.1.zip","src_id":"16394","5":"16394","creation_date":"1314593347","6":"1314593347"},{"0":"2620","vim_version":"7.0","1":"7.0","script_version":"6.1","2":"6.1","version_comment":"- Added :NeoComplCacheCachingDictionary in Japanese documentation.\r\n- Added :NeoComplCacheCachingSnippets command.\r\n- Added :NeoComplCacheLockPlugin and :NeoComplCacheUnlockPlugin commands.\r\n- Added g:neocomplcache_dictionary_patterns option.\r\n- Added g:neocomplcache_force_overwrite_completefunc option.\r\n- Added g:neocomplcache_include_max_processes option.\r\n- Added g:neocomplcache_snippets_complete_disable_runtime_snippets option.\r\n- Added neocomplcache#sources#filename_complete#get_complete_words().\r\n- Changed :NeoComplCacheEditRuntimeSnippets and :NeoComplCacheEditSnippets split behavior.\r\n- Changed caching conditions.\r\n- Changed caching timing.\r\n- Changed g:neocomplcache_enable_cursor_hold_i behavior.\r\n- Changed keyword_pattern(experimental).\r\n- Deleted obsolute variable.\r\n- Deleted underbar completion enhancements.\r\n- Disabled auto caching in include_complete when vimproc is not installed.\r\n- Don't caching when open buffer in preview window.\r\n- Don't split when execute :NeoComplCacheEditRuntimeSnippets and :NeoComplCacheEditSnippets commands.\r\n- Don't use swapfile in asyncronous caching.\r\n- Enabled auto-preview.\r\n- Fixed asyn caching error.\r\n- Fixed asyncronous caching bug.\r\n- Fixed check uname.\r\n- Fixed dictionary_complete.\r\n- Fixed doc.\r\n- Fixed filename_complete.\r\n- Fixed g:snips_author problem.\r\n- Fixed get_cur_text error.\r\n- Fixed include complete caching.\r\n- Fixed include_complete caching.\r\n- Fixed include_complete error.\r\n- Fixed include_complete freeze in Windows environment.\r\n- Fixed is_text_mode.\r\n- Fixed keyword pattern.\r\n- Fixed load_from_tags() error.\r\n- Fixed menu problem.\r\n- Fixed neocomplcache snippet sample.\r\n- Fixed neocomplcache#check_match_filter() behavior.\r\n- Fixed path search.\r\n- Fixed php delimiter pattern.\r\n- Fixed rails snippet.\r\n- Fixed snippet like multi snippet behavior.\r\n- Fixed snippets expand behavior.\r\n- Fixed tag caching error.\r\n- Fixed tags caching error.\r\n- Fixed unite source error.\r\n- Fixed vim_complete error.\r\n- Fixed vim_complete.\r\n- Genetate relative path in include_complete.\r\n- Implemented asyncronous caching in include_complete.\r\n- Implemented asyncronous caching in tags_complete.\r\n- Improved :NeoComplCacheToggle, :NeoComplCacheLock, :NeoComplCacheUnlock commands.\r\n- Improved async tags.\r\n- Improved asyncronous tags caching.\r\n- Improved autocmd completion.\r\n- Improved cache loading.\r\n- Improved default keyword patterns.\r\n- Improved execute completion.\r\n- Improved features dictionary.\r\n- Improved filename_complete.\r\n- Improved help include filetype.\r\n- Improved include filename complete.\r\n- Improved include_complete source caching timing.\r\n- Improved mapping completion.\r\n- Improved multi snippet description.\r\n- Improved neocomplcache documentation.\r\n- Improved neocomplcache#get_source_filetypes().\r\n- Improved neocomplcache#get_syn_name().\r\n- Improved python include filetype.\r\n- Improved quick match behavior.\r\n- Improved snippet source description.\r\n- Improved snippet unite source.\r\n- Improved snippet_complete.\r\n- Improved snippets action pattern.\r\n- Improved snippets_complete highlights.\r\n- Improved snippets_complete.\r\n- Improved syntax_complete cache.\r\n- Improved underbar completion.\r\n- Improved variable analyze.\r\n- Improved vim_complete.\r\n- Improved warning message.\r\n- Optimized dictionary filter.\r\n- Optimized filename_complete.\r\n- Optimized memory usage.\r\n- Renamed g:neocomplcache_snippets_complete_disable_runtime_snippets to g:neocomplcache_snippets_disable_runtime_snippets.\r\n- Set tabstop in ftplugin\/snippet.vim.\r\n- Substitute \"namespace foobar\" to \"foobar <namespace>\".\r\n- Supported coq keyword pattern.\r\n- Supported earthquake.\r\n- Supported stylus syntax.\r\n- Supported vcs.vim.\r\n- Vitalized.","3":"- Added :NeoComplCacheCachingDictionary in Japanese documentation.\r\n- Added :NeoComplCacheCachingSnippets command.\r\n- Added :NeoComplCacheLockPlugin and :NeoComplCacheUnlockPlugin commands.\r\n- Added g:neocomplcache_dictionary_patterns option.\r\n- Added g:neocomplcache_force_overwrite_completefunc option.\r\n- Added g:neocomplcache_include_max_processes option.\r\n- Added g:neocomplcache_snippets_complete_disable_runtime_snippets option.\r\n- Added neocomplcache#sources#filename_complete#get_complete_words().\r\n- Changed :NeoComplCacheEditRuntimeSnippets and :NeoComplCacheEditSnippets split behavior.\r\n- Changed caching conditions.\r\n- Changed caching timing.\r\n- Changed g:neocomplcache_enable_cursor_hold_i behavior.\r\n- Changed keyword_pattern(experimental).\r\n- Deleted obsolute variable.\r\n- Deleted underbar completion enhancements.\r\n- Disabled auto caching in include_complete when vimproc is not installed.\r\n- Don't caching when open buffer in preview window.\r\n- Don't split when execute :NeoComplCacheEditRuntimeSnippets and :NeoComplCacheEditSnippets commands.\r\n- Don't use swapfile in asyncronous caching.\r\n- Enabled auto-preview.\r\n- Fixed asyn caching error.\r\n- Fixed asyncronous caching bug.\r\n- Fixed check uname.\r\n- Fixed dictionary_complete.\r\n- Fixed doc.\r\n- Fixed filename_complete.\r\n- Fixed g:snips_author problem.\r\n- Fixed get_cur_text error.\r\n- Fixed include complete caching.\r\n- Fixed include_complete caching.\r\n- Fixed include_complete error.\r\n- Fixed include_complete freeze in Windows environment.\r\n- Fixed is_text_mode.\r\n- Fixed keyword pattern.\r\n- Fixed load_from_tags() error.\r\n- Fixed menu problem.\r\n- Fixed neocomplcache snippet sample.\r\n- Fixed neocomplcache#check_match_filter() behavior.\r\n- Fixed path search.\r\n- Fixed php delimiter pattern.\r\n- Fixed rails snippet.\r\n- Fixed snippet like multi snippet behavior.\r\n- Fixed snippets expand behavior.\r\n- Fixed tag caching error.\r\n- Fixed tags caching error.\r\n- Fixed unite source error.\r\n- Fixed vim_complete error.\r\n- Fixed vim_complete.\r\n- Genetate relative path in include_complete.\r\n- Implemented asyncronous caching in include_complete.\r\n- Implemented asyncronous caching in tags_complete.\r\n- Improved :NeoComplCacheToggle, :NeoComplCacheLock, :NeoComplCacheUnlock commands.\r\n- Improved async tags.\r\n- Improved asyncronous tags caching.\r\n- Improved autocmd completion.\r\n- Improved cache loading.\r\n- Improved default keyword patterns.\r\n- Improved execute completion.\r\n- Improved features dictionary.\r\n- Improved filename_complete.\r\n- Improved help include filetype.\r\n- Improved include filename complete.\r\n- Improved include_complete source caching timing.\r\n- Improved mapping completion.\r\n- Improved multi snippet description.\r\n- Improved neocomplcache documentation.\r\n- Improved neocomplcache#get_source_filetypes().\r\n- Improved neocomplcache#get_syn_name().\r\n- Improved python include filetype.\r\n- Improved quick match behavior.\r\n- Improved snippet source description.\r\n- Improved snippet unite source.\r\n- Improved snippet_complete.\r\n- Improved snippets action pattern.\r\n- Improved snippets_complete highlights.\r\n- Improved snippets_complete.\r\n- Improved syntax_complete cache.\r\n- Improved underbar completion.\r\n- Improved variable analyze.\r\n- Improved vim_complete.\r\n- Improved warning message.\r\n- Optimized dictionary filter.\r\n- Optimized filename_complete.\r\n- Optimized memory usage.\r\n- Renamed g:neocomplcache_snippets_complete_disable_runtime_snippets to g:neocomplcache_snippets_disable_runtime_snippets.\r\n- Set tabstop in ftplugin\/snippet.vim.\r\n- Substitute \"namespace foobar\" to \"foobar <namespace>\".\r\n- Supported coq keyword pattern.\r\n- Supported earthquake.\r\n- Supported stylus syntax.\r\n- Supported vcs.vim.\r\n- Vitalized.","package":"neocomplcache-6.1.vba","4":"neocomplcache-6.1.vba","src_id":"16345","5":"16345","creation_date":"1314246779","6":"1314246779"},{"0":"2620","vim_version":"7.0","1":"7.0","script_version":"6.0","2":"6.0","version_comment":"- Added <Plug>(neocomplcache_snippets_force_expand) keymapping.\r\n- Added <Plug>(neocomplcache_snippets_force_jump) keymapping.\r\n- Added <Plug>(neocomplcache_start_unite_complete) mapping.\r\n- Added English snippet manual.\r\n- Added README.\r\n- Added file_include source.\r\n- Added ftplugin.\r\n- Added g:neocomplcache_disable_caching_file_path_pattern option.\r\n- Added neco-ruby description.\r\n- Added neocomplcache asyncronous description.\r\n- Added neocomplcache snippet source.\r\n- Added neocomplcache#get_next_keyword().\r\n- Added neocomplcache#is_buffer_complete_enabled().\r\n- Added tex same filetype.\r\n- Added unite source(experimental).\r\n- Call neocomplcache completion when eskk is ascii mode.\r\n- Changed <Plug>(neocomplcache_snippets_expand) behavior.\r\n- Changed <Plug>(neocomplcache_snippets_jump) keymapping.\r\n- Changed neocomplcache#sources#snippets_complete#expandable().\r\n- Check unite.vim version.\r\n- Deleted :NeoComplCachePrintSnippets command.\r\n- Deleted g:neocomplcache_disable_caching_buffer_name_pattern option.\r\n- Deleted register snippets.\r\n- Fixed async_cache.\r\n- Fixed asynchronous caching encoding bug.\r\n- Fixed buffer_complete error when keyword complete is disabled.\r\n- Fixed buffer_complete error.\r\n- Fixed caching bug.\r\n- Fixed comment typo.\r\n- Fixed completefunc issue.\r\n- Fixed completeopt bug.\r\n- Fixed dictionary_complete bug.\r\n- Fixed expand snippet error.\r\n- Fixed expand snippet.\r\n- Fixed filename_complete bugs.\r\n- Fixed include_complete error.\r\n- Fixed indent file.\r\n- Fixed javascript snippet.\r\n- Fixed manual completion error.\r\n- Fixed preview window problem.\r\n- Fixed quick match bugs.\r\n- Fixed snippet documentation.\r\n- Fixed snippet jump bug.\r\n- Fixed snippets expand pattern.\r\n- Fixed snippets_complete error.\r\n- Fixed tags.\r\n- Fixed unite completion source.\r\n- Ignore caching command line window.\r\n- Implemented alternative buffer completion in cmdwin.\r\n- Implemented async_cache.vim(testing).\r\n- Implemented asyncronous caching in buffer_complete.\r\n- Implemented include path complete in filename_complete.\r\n- Improved Japanese snippet manual.\r\n- Improved async_cache debug support.\r\n- Improved buffer_name.\r\n- Improved cache.\r\n- Improved caching event.\r\n- Improved check dup.\r\n- Improved close popup.\r\n- Improved compare ranks.\r\n- Improved compare_rank().\r\n- Improved completion length.\r\n- Improved context filetype.\r\n- Improved default completeopt set.\r\n- Improved detect completefunc.\r\n- Improved detect paste.\r\n- Improved error messages.\r\n- Improved examples.\r\n- Improved expand snippet.\r\n- Improved feedkeys().\r\n- Improved filename_complete.\r\n- Improved filetype completion.\r\n- Improved g:neocomplcache_ctags_arguments_list option.\r\n- Improved g:neocomplcache_omni_patterns examples.\r\n- Improved get_cur_text().\r\n- Improved hash function.\r\n- Improved include_complete behavior for echodoc.\r\n- Improved neocomplcache#cache#async_load_from_file().\r\n- Improved neocomplcache#get_keyword_pattern().\r\n- Improved neocomplcache#is_eskk_enabled().\r\n- Improved omni_complete.\r\n- Improved snippets_complete.\r\n- Improved tags_complete.\r\n- Improved tex keyword pattern.\r\n- Improved unite source.\r\n- Improved unite-neocomplcache source.\r\n- Improved vim_complete check.\r\n- Improved vimshell include filetype setting.\r\n- Open fold when expand snippet.\r\n- Optimized cache load routine.\r\n- Refactored.\r\n- Refactoringed caching routine.\r\n- Refctoringed snippets_complete.\r\n- Set cpoptions.\r\n- Supported cobol.\r\n- Supported g:eskk#start_completion_length.\r\n- Supported unite.vim.","3":"- Added <Plug>(neocomplcache_snippets_force_expand) keymapping.\r\n- Added <Plug>(neocomplcache_snippets_force_jump) keymapping.\r\n- Added <Plug>(neocomplcache_start_unite_complete) mapping.\r\n- Added English snippet manual.\r\n- Added README.\r\n- Added file_include source.\r\n- Added ftplugin.\r\n- Added g:neocomplcache_disable_caching_file_path_pattern option.\r\n- Added neco-ruby description.\r\n- Added neocomplcache asyncronous description.\r\n- Added neocomplcache snippet source.\r\n- Added neocomplcache#get_next_keyword().\r\n- Added neocomplcache#is_buffer_complete_enabled().\r\n- Added tex same filetype.\r\n- Added unite source(experimental).\r\n- Call neocomplcache completion when eskk is ascii mode.\r\n- Changed <Plug>(neocomplcache_snippets_expand) behavior.\r\n- Changed <Plug>(neocomplcache_snippets_jump) keymapping.\r\n- Changed neocomplcache#sources#snippets_complete#expandable().\r\n- Check unite.vim version.\r\n- Deleted :NeoComplCachePrintSnippets command.\r\n- Deleted g:neocomplcache_disable_caching_buffer_name_pattern option.\r\n- Deleted register snippets.\r\n- Fixed async_cache.\r\n- Fixed asynchronous caching encoding bug.\r\n- Fixed buffer_complete error when keyword complete is disabled.\r\n- Fixed buffer_complete error.\r\n- Fixed caching bug.\r\n- Fixed comment typo.\r\n- Fixed completefunc issue.\r\n- Fixed completeopt bug.\r\n- Fixed dictionary_complete bug.\r\n- Fixed expand snippet error.\r\n- Fixed expand snippet.\r\n- Fixed filename_complete bugs.\r\n- Fixed include_complete error.\r\n- Fixed indent file.\r\n- Fixed javascript snippet.\r\n- Fixed manual completion error.\r\n- Fixed preview window problem.\r\n- Fixed quick match bugs.\r\n- Fixed snippet documentation.\r\n- Fixed snippet jump bug.\r\n- Fixed snippets expand pattern.\r\n- Fixed snippets_complete error.\r\n- Fixed tags.\r\n- Fixed unite completion source.\r\n- Ignore caching command line window.\r\n- Implemented alternative buffer completion in cmdwin.\r\n- Implemented async_cache.vim(testing).\r\n- Implemented asyncronous caching in buffer_complete.\r\n- Implemented include path complete in filename_complete.\r\n- Improved Japanese snippet manual.\r\n- Improved async_cache debug support.\r\n- Improved buffer_name.\r\n- Improved cache.\r\n- Improved caching event.\r\n- Improved check dup.\r\n- Improved close popup.\r\n- Improved compare ranks.\r\n- Improved compare_rank().\r\n- Improved completion length.\r\n- Improved context filetype.\r\n- Improved default completeopt set.\r\n- Improved detect completefunc.\r\n- Improved detect paste.\r\n- Improved error messages.\r\n- Improved examples.\r\n- Improved expand snippet.\r\n- Improved feedkeys().\r\n- Improved filename_complete.\r\n- Improved filetype completion.\r\n- Improved g:neocomplcache_ctags_arguments_list option.\r\n- Improved g:neocomplcache_omni_patterns examples.\r\n- Improved get_cur_text().\r\n- Improved hash function.\r\n- Improved include_complete behavior for echodoc.\r\n- Improved neocomplcache#cache#async_load_from_file().\r\n- Improved neocomplcache#get_keyword_pattern().\r\n- Improved neocomplcache#is_eskk_enabled().\r\n- Improved omni_complete.\r\n- Improved snippets_complete.\r\n- Improved tags_complete.\r\n- Improved tex keyword pattern.\r\n- Improved unite source.\r\n- Improved unite-neocomplcache source.\r\n- Improved vim_complete check.\r\n- Improved vimshell include filetype setting.\r\n- Open fold when expand snippet.\r\n- Optimized cache load routine.\r\n- Refactored.\r\n- Refactoringed caching routine.\r\n- Refctoringed snippets_complete.\r\n- Set cpoptions.\r\n- Supported cobol.\r\n- Supported g:eskk#start_completion_length.\r\n- Supported unite.vim.","package":"neocomplcache-6.0.vba","4":"neocomplcache-6.0.vba","src_id":"15559","5":"15559","creation_date":"1304228482","6":"1304228482"},{"0":"2620","vim_version":"7.0","1":"7.0","script_version":"5.3","2":"5.3","version_comment":"- Added zimbu support.\r\n- Fixed :Neco.\r\n- Fixed :NeoComplCacheEnableCaching error.\r\n- Fixed buffer caching bug.\r\n- Fixed examples.\r\n- Fixed g:neocomplcache_plugin_rank error.\r\n- Fixed vim_complete error.\r\n- Implemented colorscheme completion.\r\n- Implemented ignore source.\r\n- Improved Perl6 support.\r\n- Improved clojure and lisp support.\r\n- Improved error check.\r\n- Improved g:neocomplcache_omni_patterns description.\r\n- Improved haskell keyword pattern.\r\n- Improved modeline.\r\n- Improved python snippets.\r\n- Improved sid functions support.\r\n- Improved snippet_complete manual.\r\n- Improved snippets expand.\r\n- Improved snippets include syntax.\r\n- Improved snippets search.\r\n- Improved vim keyword pattern.\r\n- Independent +reltime.\r\n- Supported Konoha language.","3":"- Added zimbu support.\r\n- Fixed :Neco.\r\n- Fixed :NeoComplCacheEnableCaching error.\r\n- Fixed buffer caching bug.\r\n- Fixed examples.\r\n- Fixed g:neocomplcache_plugin_rank error.\r\n- Fixed vim_complete error.\r\n- Implemented colorscheme completion.\r\n- Implemented ignore source.\r\n- Improved Perl6 support.\r\n- Improved clojure and lisp support.\r\n- Improved error check.\r\n- Improved g:neocomplcache_omni_patterns description.\r\n- Improved haskell keyword pattern.\r\n- Improved modeline.\r\n- Improved python snippets.\r\n- Improved sid functions support.\r\n- Improved snippet_complete manual.\r\n- Improved snippets expand.\r\n- Improved snippets include syntax.\r\n- Improved snippets search.\r\n- Improved vim keyword pattern.\r\n- Independent +reltime.\r\n- Supported Konoha language.","package":"neocomplcache-5.3.vba","4":"neocomplcache-5.3.vba","src_id":"14464","5":"14464","creation_date":"1291956974","6":"1291956974"},{"0":"2620","vim_version":"7.0","1":"7.0","script_version":"5.2","2":"5.2","version_comment":"- Added :Neco animation.\r\n- Added NeoComplCacheCachingInclude description.\r\n- Added g:neocomplcache_disable_auto_select_buffer_name_pattern option.\r\n- Added g:neocomplcache_enable_auto_delimiter option.\r\n- Added g:neocomplcache_enable_caching_message option.\r\n- Added g:neocomplcache_force_caching_buffer_name_pattern option.\r\n- Added ghc_complete description.\r\n- Added install description.\r\n- Added objj support.\r\n- Added shell like behavior settings.\r\n- Deleted g:neocomplcache_enable_display_parameter option.\r\n- Deleted member filter.\r\n- Detect duplicated snippet name.\r\n- Fixed :Neco.\r\n- Fixed abbrev_complete redir bug.\r\n- Fixed abbrev_complete.\r\n- Fixed caching bug.\r\n- Fixed caching timing.\r\n- Fixed context filetype bug in filetype plugin.\r\n- Fixed delimiter.\r\n- Fixed echodoc in include_complete.\r\n- Fixed examples.\r\n- Fixed filename_complete.\r\n- Fixed filter bug.\r\n- Fixed filtering.\r\n- Fixed for Vim 7.0.\r\n- Fixed get_cur_text() bug.\r\n- Fixed get_cur_text() in snippets_complete.\r\n- Fixed include_complete bugs.\r\n- Fixed include_complete error in echodoc.\r\n- Fixed is_enabled error.\r\n- Fixed java snippet warning.\r\n- Fixed keyword pattern.\r\n- Fixed mac check.\r\n- Fixed multibyte check.\r\n- Fixed nasm error.\r\n- Fixed plugin manual.\r\n- Fixed snippets analyze.\r\n- Fixed var_dictionary complete in vim_complete.\r\n- Fixed vim_complete cur_keyword_str bug.\r\n- Fixed vim_complete kind bug.\r\n- Fixed xhtml snippet error.\r\n- Implemented escaped ` in snippets_complete.\r\n- Implemented member completion in buffer_complete.\r\n- Implemented neocomplcache enabled check.\r\n- Implemented neocomplcache#do_auto_complete().\r\n- Improved :Neco.\r\n- Improved c++ completion.\r\n- Improved cache timing.\r\n- Improved caching algorithm.\r\n- Improved caching message.\r\n- Improved ctags arguments for mac.\r\n- Improved ctags arguments.\r\n- Improved d snippet.\r\n- Improved delimiter.\r\n- Improved echo.\r\n- Improved error catch.\r\n- Improved eskk support.\r\n- Improved filename complete.\r\n- Improved filename pattern.\r\n- Improved for echodoc.\r\n- Improved g:neocomplcache_ctags_arguments_list.\r\n- Improved gas syntax.\r\n- Improved get_cur_text().\r\n- Improved include cache.\r\n- Improved keyword patterns.\r\n- Improved lock.\r\n- Improved omni_complete default pattern.\r\n- Improved php delimiter.\r\n- Improved plugin error catch.\r\n- Improved print caching.\r\n- Improved snippet syntax.\r\n- Improved vim_complete check.\r\n- Refactoringed :Neco command.\r\n- Revised documentation.\r\n- Supported Vim7.3 in vim_complete.\r\n- Supported echodoc in snippets_complete.\r\n- Supported echodoc in vim_complete.\r\n- Supported lua.\r\n- Supported php namespace.","3":"- Added :Neco animation.\r\n- Added NeoComplCacheCachingInclude description.\r\n- Added g:neocomplcache_disable_auto_select_buffer_name_pattern option.\r\n- Added g:neocomplcache_enable_auto_delimiter option.\r\n- Added g:neocomplcache_enable_caching_message option.\r\n- Added g:neocomplcache_force_caching_buffer_name_pattern option.\r\n- Added ghc_complete description.\r\n- Added install description.\r\n- Added objj support.\r\n- Added shell like behavior settings.\r\n- Deleted g:neocomplcache_enable_display_parameter option.\r\n- Deleted member filter.\r\n- Detect duplicated snippet name.\r\n- Fixed :Neco.\r\n- Fixed abbrev_complete redir bug.\r\n- Fixed abbrev_complete.\r\n- Fixed caching bug.\r\n- Fixed caching timing.\r\n- Fixed context filetype bug in filetype plugin.\r\n- Fixed delimiter.\r\n- Fixed echodoc in include_complete.\r\n- Fixed examples.\r\n- Fixed filename_complete.\r\n- Fixed filter bug.\r\n- Fixed filtering.\r\n- Fixed for Vim 7.0.\r\n- Fixed get_cur_text() bug.\r\n- Fixed get_cur_text() in snippets_complete.\r\n- Fixed include_complete bugs.\r\n- Fixed include_complete error in echodoc.\r\n- Fixed is_enabled error.\r\n- Fixed java snippet warning.\r\n- Fixed keyword pattern.\r\n- Fixed mac check.\r\n- Fixed multibyte check.\r\n- Fixed nasm error.\r\n- Fixed plugin manual.\r\n- Fixed snippets analyze.\r\n- Fixed var_dictionary complete in vim_complete.\r\n- Fixed vim_complete cur_keyword_str bug.\r\n- Fixed vim_complete kind bug.\r\n- Fixed xhtml snippet error.\r\n- Implemented escaped ` in snippets_complete.\r\n- Implemented member completion in buffer_complete.\r\n- Implemented neocomplcache enabled check.\r\n- Implemented neocomplcache#do_auto_complete().\r\n- Improved :Neco.\r\n- Improved c++ completion.\r\n- Improved cache timing.\r\n- Improved caching algorithm.\r\n- Improved caching message.\r\n- Improved ctags arguments for mac.\r\n- Improved ctags arguments.\r\n- Improved d snippet.\r\n- Improved delimiter.\r\n- Improved echo.\r\n- Improved error catch.\r\n- Improved eskk support.\r\n- Improved filename complete.\r\n- Improved filename pattern.\r\n- Improved for echodoc.\r\n- Improved g:neocomplcache_ctags_arguments_list.\r\n- Improved gas syntax.\r\n- Improved get_cur_text().\r\n- Improved include cache.\r\n- Improved keyword patterns.\r\n- Improved lock.\r\n- Improved omni_complete default pattern.\r\n- Improved php delimiter.\r\n- Improved plugin error catch.\r\n- Improved print caching.\r\n- Improved snippet syntax.\r\n- Improved vim_complete check.\r\n- Refactoringed :Neco command.\r\n- Revised documentation.\r\n- Supported Vim7.3 in vim_complete.\r\n- Supported echodoc in snippets_complete.\r\n- Supported echodoc in vim_complete.\r\n- Supported lua.\r\n- Supported php namespace.","package":"neocomplcache-ver.5.2.vba","4":"neocomplcache-ver.5.2.vba","src_id":"13978","5":"13978","creation_date":"1286030298","6":"1286030298"},{"0":"2620","vim_version":"7.0","1":"7.0","script_version":"5.1","2":"5.1","version_comment":"- Added \"nothing\" in text mode filetype.\r\n- Added :NeoComplCacheCachingDictionary discription.\r\n- Added g:neocomplcache_quick_match_table.\r\n- Added g:neocomplcache_text_mode_filetypes option.\r\n- Added neocomplcache#set_completion_length().\r\n- Added neocomplcache#smart_close_popup().\r\n- Added omni completion examples.\r\n- Added tex in text mode filetypes.\r\n- Allow blank line in snippet.\r\n- Changed neocomplcache#set_dictionary_helper().\r\n- Changed vim_complete marker.\r\n- Deleted obsolute functions.\r\n- Deleted spell_complete.\r\n- Disabled Ruby omni completion.\r\n- Disabled keyword_complete when eskk is enabled.\r\n- Fixed :NeoComplCacheToggle.\r\n- Fixed analyzing function.\r\n- Fixed autocompletion freeze.\r\n- Fixed context filetype bug.\r\n- Fixed css snippet.\r\n- Fixed documentation.\r\n- Fixed environments parse bug.\r\n- Fixed error when complete directory.\r\n- Fixed error when local variable completion.\r\n- Fixed eskk check.\r\n- Fixed eskk omni completion bug.\r\n- Fixed example.\r\n- Fixed ftplugin bug.\r\n- Fixed get filetype timing in snippets_complete.\r\n- Fixed neocomplcache#complete_common_string() bug.\r\n- Fixed neocomplcache#match_word() bug.\r\n- Fixed neocomplcache#system().\r\n- Fixed omni completion bug.\r\n- Fixed quick match bug.\r\n- Fixed quickmatch error.\r\n- Fixed quickmatch selection.\r\n- Fixed snippet parse.\r\n- Fixed snippets expand error.\r\n- Fixed vim_complete commands.dict.\r\n- Fixed vim_complete error.\r\n- Implemented dictionary plugins.\r\n- Implemented expand completion.\r\n- Implemented filetype plugin.\r\n- Implemented set rank helper.\r\n- Implemented syntax attr helper.\r\n- Implemented text mode.\r\n- Improved :NeoComplCacheAutoCompletionLength behavior.\r\n- Improved autoload plugins.\r\n- Improved buffer caching.\r\n- Improved caching.\r\n- Improved check wildcard.\r\n- Improved context filetype.\r\n- Improved css keyword pattern.\r\n- Improved detect completefunc.\r\n- Improved eskk and vimproc check.\r\n- Improved examples.\r\n- Improved filetype completion.\r\n- Improved g:neocomplcache_omni_patterns description.\r\n- Improved g:neocomplcache_plugin_disable behavior.\r\n- Improved haskell keyword pattern.\r\n- Improved include check.\r\n- Improved include_complete.\r\n- Improved integrated completion.\r\n- Improved interactive termtter pattern.\r\n- Improved javascript support.\r\n- Improved local variable analysis.\r\n- Improved member filter.\r\n- Improved multibyte trunk.\r\n- Improved neocomplcache#close_popup().\r\n- Improved neocomplcache#filetype_complete().\r\n- Improved neocomplcache#get_auto_completion_length().\r\n- Improved neocomplcache#snippets_complete#expandable().\r\n- Improved print error.\r\n- Improved quickmatch selection.\r\n- Improved snippet alias pattern.\r\n- Improved startup.\r\n- Improved termtter keywords.\r\n- Improved text mode.\r\n- Improved tilde substitution.\r\n- Improved truncate filename.\r\n- Improved vim keyword pattern.\r\n- Improved vim_complete.\r\n- Improved vimshell pattern.\r\n- Optimized match.\r\n- Refactoringed vim_complete.\r\n- Skip filename completion when too many candidates.\r\n- Supported GetLatestVimScripts.\r\n- Supported coffee script.\r\n- Supported gdb keyword.\r\n- Supported inline assembly language.\r\n- Supported union.","3":"- Added \"nothing\" in text mode filetype.\r\n- Added :NeoComplCacheCachingDictionary discription.\r\n- Added g:neocomplcache_quick_match_table.\r\n- Added g:neocomplcache_text_mode_filetypes option.\r\n- Added neocomplcache#set_completion_length().\r\n- Added neocomplcache#smart_close_popup().\r\n- Added omni completion examples.\r\n- Added tex in text mode filetypes.\r\n- Allow blank line in snippet.\r\n- Changed neocomplcache#set_dictionary_helper().\r\n- Changed vim_complete marker.\r\n- Deleted obsolute functions.\r\n- Deleted spell_complete.\r\n- Disabled Ruby omni completion.\r\n- Disabled keyword_complete when eskk is enabled.\r\n- Fixed :NeoComplCacheToggle.\r\n- Fixed analyzing function.\r\n- Fixed autocompletion freeze.\r\n- Fixed context filetype bug.\r\n- Fixed css snippet.\r\n- Fixed documentation.\r\n- Fixed environments parse bug.\r\n- Fixed error when complete directory.\r\n- Fixed error when local variable completion.\r\n- Fixed eskk check.\r\n- Fixed eskk omni completion bug.\r\n- Fixed example.\r\n- Fixed ftplugin bug.\r\n- Fixed get filetype timing in snippets_complete.\r\n- Fixed neocomplcache#complete_common_string() bug.\r\n- Fixed neocomplcache#match_word() bug.\r\n- Fixed neocomplcache#system().\r\n- Fixed omni completion bug.\r\n- Fixed quick match bug.\r\n- Fixed quickmatch error.\r\n- Fixed quickmatch selection.\r\n- Fixed snippet parse.\r\n- Fixed snippets expand error.\r\n- Fixed vim_complete commands.dict.\r\n- Fixed vim_complete error.\r\n- Implemented dictionary plugins.\r\n- Implemented expand completion.\r\n- Implemented filetype plugin.\r\n- Implemented set rank helper.\r\n- Implemented syntax attr helper.\r\n- Implemented text mode.\r\n- Improved :NeoComplCacheAutoCompletionLength behavior.\r\n- Improved autoload plugins.\r\n- Improved buffer caching.\r\n- Improved caching.\r\n- Improved check wildcard.\r\n- Improved context filetype.\r\n- Improved css keyword pattern.\r\n- Improved detect completefunc.\r\n- Improved eskk and vimproc check.\r\n- Improved examples.\r\n- Improved filetype completion.\r\n- Improved g:neocomplcache_omni_patterns description.\r\n- Improved g:neocomplcache_plugin_disable behavior.\r\n- Improved haskell keyword pattern.\r\n- Improved include check.\r\n- Improved include_complete.\r\n- Improved integrated completion.\r\n- Improved interactive termtter pattern.\r\n- Improved javascript support.\r\n- Improved local variable analysis.\r\n- Improved member filter.\r\n- Improved multibyte trunk.\r\n- Improved neocomplcache#close_popup().\r\n- Improved neocomplcache#filetype_complete().\r\n- Improved neocomplcache#get_auto_completion_length().\r\n- Improved neocomplcache#snippets_complete#expandable().\r\n- Improved print error.\r\n- Improved quickmatch selection.\r\n- Improved snippet alias pattern.\r\n- Improved startup.\r\n- Improved termtter keywords.\r\n- Improved text mode.\r\n- Improved tilde substitution.\r\n- Improved truncate filename.\r\n- Improved vim keyword pattern.\r\n- Improved vim_complete.\r\n- Improved vimshell pattern.\r\n- Optimized match.\r\n- Refactoringed vim_complete.\r\n- Skip filename completion when too many candidates.\r\n- Supported GetLatestVimScripts.\r\n- Supported coffee script.\r\n- Supported gdb keyword.\r\n- Supported inline assembly language.\r\n- Supported union.","package":"neocomplcache-5.1.vba","4":"neocomplcache-5.1.vba","src_id":"13456","5":"13456","creation_date":"1280727006","6":"1280727006"},{"0":"2620","vim_version":"7.0","1":"7.0","script_version":"5.0","2":"5.0","version_comment":"- Added abbrev_complete plugin.\r\n- Added eskk omni completion support.\r\n- Added g:neocomplcache_delimiter_patterns option.\r\n- Added g:neocomplcache_filetype_include_lists option.\r\n- Added g:neocomplcache_omni_function_list option.\r\n- Added g:neocomplcache_plugin_rank option.\r\n- Added g:neocomplcache_vim_completefuncs option.\r\n- Added neocomplcache#cancel_popup().\r\n- Added objc omni completion support.\r\n- Added pasm and pir support.\r\n- Allow snipMate like snippet.\r\n- Changed NeoComplCacheCachingDisable into NeoComplCacheDisableCaching.\r\n- Changed NeoComplCacheCachingEnable into NeoComplCacheEnableCaching.\r\n- Changed g:neocomplcache_alphabetical_order into g:neocomplcache_enable_alphabetical_order.\r\n- Changed g:neocomplcache_caching_disable_pattern into g:neocomplcache_disable_caching_buffer_name_pattern.\r\n- Changed g:neocomplcache_caching_limit_file_size default value.\r\n- Changed g:neocomplcache_enable_cursor_hold_i_time into g:neocomplcache_cursor_hold_i_time.\r\n- Changed g:neocomplcache_enable_quick_match default value.\r\n- Changed g:neocomplcache_lock_buffer_name_pattern into g:neocomplcache_lock_buffer_name_pattern.\r\n- Changed g:neocomplcache_omni_function_list as g:neocomplcache_omni_functions.\r\n- Changed g:neocomplcache_plugin_completion_length into g:neocomplcache_plugin_completion_length.\r\n- Changed variables name dramatically.\r\n- Check obsolute options.\r\n- Deleted g:neocomplcache_cache_line_count variable.\r\n- Deleted g:neocomplcache_caching_percent_in_statusline option.\r\n- Deleted g:neocomplcache_enable_alphabetical_order option.\r\n- Deleted g:neocomplcache_enable_randomize option.\r\n- Deleted neocomplcache#caching_percent().\r\n- Deleted neocomplcache#cancel_popup().\r\n- Fixed abbrev_complete bug.\r\n- Fixed abbrev_complete check.\r\n- Fixed command line window error.\r\n- Fixed context filetype bug.\r\n- Fixed delete cache bug.\r\n- Fixed disable AutoComplPop.\r\n- Fixed dup problem in snippets_complete.\r\n- Fixed eruby and ruby pattern.\r\n- Fixed examples.\r\n- Fixed expand a snippet contained blank line bug.\r\n- Fixed filename_complete rank.\r\n- Fixed g:neocomplcache_enable_cursor_hold_i bug.\r\n- Fixed help file caching bug.\r\n- Fixed icase bug.\r\n- Fixed include_complete error.\r\n- Fixed manual completion freeze bug.\r\n- Fixed multibyte problems.\r\n- Fixed nested snippet bug.\r\n- Fixed obsolute settings.\r\n- Fixed presentation file.\r\n- Fixed rank bug.\r\n- Fixed save cache error.\r\n- Fixed sort bug.\r\n- Fixed vim_complete freeze.\r\n- Implemented customlist completion in vim_complete.\r\n- Implemented delemiter completion.\r\n- Improved abbr check.\r\n- Improved abbr.\r\n- Improved cache timing.\r\n- Improved caching message.\r\n- Improved caching timing.\r\n- Improved clojure support.\r\n- Improved context filetype.\r\n- Improved cur_text.\r\n- Improved d and java keyword patterns.\r\n- Improved dummy move.\r\n- Improved erlang keyword pattern.\r\n- Improved eruby support.\r\n- Improved eskk support.\r\n- Improved expand snippet.\r\n- Improved filename_complete.\r\n- Improved filter.\r\n- Improved garbage collect and calc rank.\r\n- Improved help.\r\n- Improved icase.\r\n- Improved keyword pattern.\r\n- Improved keyword patterns.\r\n- Improved masm and nasm keyword pattern.\r\n- Improved ruby keyword.\r\n- Improved snippets expand.\r\n- Improved syntax_complete.\r\n- Improved vim_complete.\r\n- Introduced thinca's script.\r\n- Optimized cache.\r\n- Optimized caching.\r\n- Optimized completion.\r\n- Optimized frequencies.\r\n- Optimized memory when loaded cache.\r\n- Optimized sort.\r\n- Refactoringed keyword_complete.\r\n- Refactoringed neocomplcache#start_manual_complete().\r\n- Refixed help caching bug.\r\n- Refixed help file caching bug.\r\n- Reimplemented neocomplcache#close_popup().\r\n- Renamed g:neocomplcache_disable_plugin_list as g:neocomplcache_plugin_disable.\r\n- Renamed g:neocomplcache_plugin_completion_length_list as g:neocomplcache_plugin_completion_length.\r\n- Supported H8-300 keyword pattern.\r\n- dictionary_complete use dictionary option.","3":"- Added abbrev_complete plugin.\r\n- Added eskk omni completion support.\r\n- Added g:neocomplcache_delimiter_patterns option.\r\n- Added g:neocomplcache_filetype_include_lists option.\r\n- Added g:neocomplcache_omni_function_list option.\r\n- Added g:neocomplcache_plugin_rank option.\r\n- Added g:neocomplcache_vim_completefuncs option.\r\n- Added neocomplcache#cancel_popup().\r\n- Added objc omni completion support.\r\n- Added pasm and pir support.\r\n- Allow snipMate like snippet.\r\n- Changed NeoComplCacheCachingDisable into NeoComplCacheDisableCaching.\r\n- Changed NeoComplCacheCachingEnable into NeoComplCacheEnableCaching.\r\n- Changed g:neocomplcache_alphabetical_order into g:neocomplcache_enable_alphabetical_order.\r\n- Changed g:neocomplcache_caching_disable_pattern into g:neocomplcache_disable_caching_buffer_name_pattern.\r\n- Changed g:neocomplcache_caching_limit_file_size default value.\r\n- Changed g:neocomplcache_enable_cursor_hold_i_time into g:neocomplcache_cursor_hold_i_time.\r\n- Changed g:neocomplcache_enable_quick_match default value.\r\n- Changed g:neocomplcache_lock_buffer_name_pattern into g:neocomplcache_lock_buffer_name_pattern.\r\n- Changed g:neocomplcache_omni_function_list as g:neocomplcache_omni_functions.\r\n- Changed g:neocomplcache_plugin_completion_length into g:neocomplcache_plugin_completion_length.\r\n- Changed variables name dramatically.\r\n- Check obsolute options.\r\n- Deleted g:neocomplcache_cache_line_count variable.\r\n- Deleted g:neocomplcache_caching_percent_in_statusline option.\r\n- Deleted g:neocomplcache_enable_alphabetical_order option.\r\n- Deleted g:neocomplcache_enable_randomize option.\r\n- Deleted neocomplcache#caching_percent().\r\n- Deleted neocomplcache#cancel_popup().\r\n- Fixed abbrev_complete bug.\r\n- Fixed abbrev_complete check.\r\n- Fixed command line window error.\r\n- Fixed context filetype bug.\r\n- Fixed delete cache bug.\r\n- Fixed disable AutoComplPop.\r\n- Fixed dup problem in snippets_complete.\r\n- Fixed eruby and ruby pattern.\r\n- Fixed examples.\r\n- Fixed expand a snippet contained blank line bug.\r\n- Fixed filename_complete rank.\r\n- Fixed g:neocomplcache_enable_cursor_hold_i bug.\r\n- Fixed help file caching bug.\r\n- Fixed icase bug.\r\n- Fixed include_complete error.\r\n- Fixed manual completion freeze bug.\r\n- Fixed multibyte problems.\r\n- Fixed nested snippet bug.\r\n- Fixed obsolute settings.\r\n- Fixed presentation file.\r\n- Fixed rank bug.\r\n- Fixed save cache error.\r\n- Fixed sort bug.\r\n- Fixed vim_complete freeze.\r\n- Implemented customlist completion in vim_complete.\r\n- Implemented delemiter completion.\r\n- Improved abbr check.\r\n- Improved abbr.\r\n- Improved cache timing.\r\n- Improved caching message.\r\n- Improved caching timing.\r\n- Improved clojure support.\r\n- Improved context filetype.\r\n- Improved cur_text.\r\n- Improved d and java keyword patterns.\r\n- Improved dummy move.\r\n- Improved erlang keyword pattern.\r\n- Improved eruby support.\r\n- Improved eskk support.\r\n- Improved expand snippet.\r\n- Improved filename_complete.\r\n- Improved filter.\r\n- Improved garbage collect and calc rank.\r\n- Improved help.\r\n- Improved icase.\r\n- Improved keyword pattern.\r\n- Improved keyword patterns.\r\n- Improved masm and nasm keyword pattern.\r\n- Improved ruby keyword.\r\n- Improved snippets expand.\r\n- Improved syntax_complete.\r\n- Improved vim_complete.\r\n- Introduced thinca's script.\r\n- Optimized cache.\r\n- Optimized caching.\r\n- Optimized completion.\r\n- Optimized frequencies.\r\n- Optimized memory when loaded cache.\r\n- Optimized sort.\r\n- Refactoringed keyword_complete.\r\n- Refactoringed neocomplcache#start_manual_complete().\r\n- Refixed help caching bug.\r\n- Refixed help file caching bug.\r\n- Reimplemented neocomplcache#close_popup().\r\n- Renamed g:neocomplcache_disable_plugin_list as g:neocomplcache_plugin_disable.\r\n- Renamed g:neocomplcache_plugin_completion_length_list as g:neocomplcache_plugin_completion_length.\r\n- Supported H8-300 keyword pattern.\r\n- dictionary_complete use dictionary option.","package":"neocomplcache-ver.5.0.zip","4":"neocomplcache-ver.5.0.zip","src_id":"13243","5":"13243","creation_date":"1277551674","6":"1277551674"},{"0":"2620","vim_version":"7.0","1":"7.0","script_version":"4.30a","2":"4.30a","version_comment":"- Fixed critical popup bug.","3":"- Fixed critical popup bug.","package":"neocomplcache-4.30a.zip","4":"neocomplcache-4.30a.zip","src_id":"13084","5":"13084","creation_date":"1275443713","6":"1275443713"},{"0":"2620","vim_version":"7.0","1":"7.0","script_version":"4.30","2":"4.30","version_comment":"* Added g:NeoComplCache_EnableAutoSelect option.\r\n* Added g:NeoComplCache_EnableCursorHoldI and g:NeoComplCache_CursorHoldITime options.\r\n* Deleted g:NeoComplCache_EnableSkipCompletion and g:NeoComplCache_SkipCompletionTime options.\r\n* Deleted mapping check.\r\n* Detect conflicted plugin.\r\n* Detect text was changed.\r\n* Disabled C\/C++ Omni patterns.\r\n* Enable cache in \"[Command line]\" buffer.\r\n* Enable spell_complete in manual_complete.\r\n* Fixed g:NeoComplCache_IgnoreCase bug.\r\n* Fixed html next keyword pattern.\r\n* Fixed neocomplcache#complete_common_string() bug.\r\n* Fixed quickmatch behaivior.\r\n* Fixed quickmatch keyword position bug.\r\n* Fixed vim completion bug.\r\n* Fixed vim_complete bugs.\r\n* If <CR> is mapped, g:NeoComplCache_EnableAutoSelect option does not work to avoid a side effect.\r\n* Ignore command line window caching.\r\n* Implemented CursorHoldI completion.\r\n* Implemented dictionary completion in vim_complete.\r\n* Implemented lazy caching in vim_complete.\r\n* Improved disable bell.\r\n* Improved filename pattern.\r\n* Improved filename_complete.\r\n* Improved for skk.vim.\r\n* Improved g:NeoComplCache_MaxKeywordWidth.\r\n* Improved neocomplcache#close_popup().\r\n* Improved print prototype behaivior when g:NeoComplCache_CursorHoldITime.\r\n* Improved print prototype in vim_complete.\r\n* Improved quickmatch.\r\n* Improved redraw.\r\n* Improved user commands analsze in vim_complete.\r\n* Improved vim_complete analyse.\r\n* Improved vim_complete. Recognize context.\r\n* Improved vimproc#system().\r\n* Revised completion.\r\n* Use b:changedtick.\r\n* neocomplcache disables bell.\r\n- '#' as wildcard in vim_complete.\r\n- Added AutoComplPop like behavior settings.\r\n- Added ml keyword pattern.\r\n- Caching readonly buffer.\r\n- Changed check buflisted() into bufloaded().\r\n- Deleted keyword cache in omni_complete.\r\n- Deleted obsolute functions.\r\n- Deleted obsolute internal variable.\r\n- Detect AutoComplPop.\r\n- Disabled php omni completion.\r\n- Fixed completion length bugs.\r\n- Fixed custom and customlist error in vim_complete.\r\n- Fixed error when NeoComplCacheDisable.\r\n- Fixed menu bug in buffer_complete.\r\n- Fixed prototype in vim_complete.\r\n- Fixed quickmatch bugs.\r\n- Implemented ambiguous command completion.\r\n- Implemented ~Username\/ completion in filename_complete.\r\n- Improved buffer cache timing.\r\n- Improved caching timing in buffer_complete.\r\n- Improved caching.\r\n- Improved directory completion in vim_complete.\r\n- Improved dummy move.\r\n- Improved filtering.\r\n- Improved function display in vim_complete.\r\n- Improved help file.\r\n- Improved ocaml keyword pattern.\r\n- Improved recaching behaivior.\r\n- Improved vim_complete.\r\n- Improved wildcard check.\r\n- Refactoringed.\r\n- Revised example settings.\r\n- Supported '<,'>command...\r\n- Use 'path' in filename_complete.\r\n- cd source path when searching include files.","3":"* Added g:NeoComplCache_EnableAutoSelect option.\r\n* Added g:NeoComplCache_EnableCursorHoldI and g:NeoComplCache_CursorHoldITime options.\r\n* Deleted g:NeoComplCache_EnableSkipCompletion and g:NeoComplCache_SkipCompletionTime options.\r\n* Deleted mapping check.\r\n* Detect conflicted plugin.\r\n* Detect text was changed.\r\n* Disabled C\/C++ Omni patterns.\r\n* Enable cache in \"[Command line]\" buffer.\r\n* Enable spell_complete in manual_complete.\r\n* Fixed g:NeoComplCache_IgnoreCase bug.\r\n* Fixed html next keyword pattern.\r\n* Fixed neocomplcache#complete_common_string() bug.\r\n* Fixed quickmatch behaivior.\r\n* Fixed quickmatch keyword position bug.\r\n* Fixed vim completion bug.\r\n* Fixed vim_complete bugs.\r\n* If <CR> is mapped, g:NeoComplCache_EnableAutoSelect option does not work to avoid a side effect.\r\n* Ignore command line window caching.\r\n* Implemented CursorHoldI completion.\r\n* Implemented dictionary completion in vim_complete.\r\n* Implemented lazy caching in vim_complete.\r\n* Improved disable bell.\r\n* Improved filename pattern.\r\n* Improved filename_complete.\r\n* Improved for skk.vim.\r\n* Improved g:NeoComplCache_MaxKeywordWidth.\r\n* Improved neocomplcache#close_popup().\r\n* Improved print prototype behaivior when g:NeoComplCache_CursorHoldITime.\r\n* Improved print prototype in vim_complete.\r\n* Improved quickmatch.\r\n* Improved redraw.\r\n* Improved user commands analsze in vim_complete.\r\n* Improved vim_complete analyse.\r\n* Improved vim_complete. Recognize context.\r\n* Improved vimproc#system().\r\n* Revised completion.\r\n* Use b:changedtick.\r\n* neocomplcache disables bell.\r\n- '#' as wildcard in vim_complete.\r\n- Added AutoComplPop like behavior settings.\r\n- Added ml keyword pattern.\r\n- Caching readonly buffer.\r\n- Changed check buflisted() into bufloaded().\r\n- Deleted keyword cache in omni_complete.\r\n- Deleted obsolute functions.\r\n- Deleted obsolute internal variable.\r\n- Detect AutoComplPop.\r\n- Disabled php omni completion.\r\n- Fixed completion length bugs.\r\n- Fixed custom and customlist error in vim_complete.\r\n- Fixed error when NeoComplCacheDisable.\r\n- Fixed menu bug in buffer_complete.\r\n- Fixed prototype in vim_complete.\r\n- Fixed quickmatch bugs.\r\n- Implemented ambiguous command completion.\r\n- Implemented ~Username\/ completion in filename_complete.\r\n- Improved buffer cache timing.\r\n- Improved caching timing in buffer_complete.\r\n- Improved caching.\r\n- Improved directory completion in vim_complete.\r\n- Improved dummy move.\r\n- Improved filtering.\r\n- Improved function display in vim_complete.\r\n- Improved help file.\r\n- Improved ocaml keyword pattern.\r\n- Improved recaching behaivior.\r\n- Improved vim_complete.\r\n- Improved wildcard check.\r\n- Refactoringed.\r\n- Revised example settings.\r\n- Supported '<,'>command...\r\n- Use 'path' in filename_complete.\r\n- cd source path when searching include files.","package":"neocomplcache-ver.4.30.zip","4":"neocomplcache-ver.4.30.zip","src_id":"13074","5":"13074","creation_date":"1275279420","6":"1275279420"},{"0":"2620","vim_version":"7.0","1":"7.0","script_version":"4.20","2":"4.20","version_comment":"* Added snippets_complete help in Japanese.\r\n* Added variables dictionary.\r\n* Caching disable when bufname is '[Command line]'\r\n* Changed default value of g:NeoComplCache_IgnoreCase.\r\n* Completed prototype dictionary.\r\n* Deleted obsolute variables.\r\n* Fixed filename pattern.\r\n* Fixed interactive filetype.\r\n* Fixed manual completion bug.\r\n* Fixed quickmatch bug.\r\n* Fixed quickmatch bug.\r\n* Fixed quickmatch bug.\r\n* Fixed snippets expand bug.\r\n* Highlight color when print prototype.\r\n* Improved _ snippets.\r\n* Improved buffer caching.\r\n* Improved caching print.\r\n* Improved command completion in vim_complete.\r\n* Improved command completion text.\r\n* Improved command name search.\r\n* Improved command prototype dictionary in vim_complete.\r\n* Improved for skk.vim.\r\n* Improved frequency garbage collect.\r\n* Improved keyword_filter.\r\n* Improved manual complete.\r\n* Improved mappings dictionary.\r\n* Improved vim_complete performance.\r\n* Improved vim_complete.\r\n* Incleased omni completion rank.\r\n* Lazy caching environment variables.\r\n* Skip head digits in vim_complete.\r\n* Use neocomplcache#escape_match().","3":"* Added snippets_complete help in Japanese.\r\n* Added variables dictionary.\r\n* Caching disable when bufname is '[Command line]'\r\n* Changed default value of g:NeoComplCache_IgnoreCase.\r\n* Completed prototype dictionary.\r\n* Deleted obsolute variables.\r\n* Fixed filename pattern.\r\n* Fixed interactive filetype.\r\n* Fixed manual completion bug.\r\n* Fixed quickmatch bug.\r\n* Fixed quickmatch bug.\r\n* Fixed quickmatch bug.\r\n* Fixed snippets expand bug.\r\n* Highlight color when print prototype.\r\n* Improved _ snippets.\r\n* Improved buffer caching.\r\n* Improved caching print.\r\n* Improved command completion in vim_complete.\r\n* Improved command completion text.\r\n* Improved command name search.\r\n* Improved command prototype dictionary in vim_complete.\r\n* Improved for skk.vim.\r\n* Improved frequency garbage collect.\r\n* Improved keyword_filter.\r\n* Improved manual complete.\r\n* Improved mappings dictionary.\r\n* Improved vim_complete performance.\r\n* Improved vim_complete.\r\n* Incleased omni completion rank.\r\n* Lazy caching environment variables.\r\n* Skip head digits in vim_complete.\r\n* Use neocomplcache#escape_match().","package":"neocomplcache-ver.4.20.zip","4":"neocomplcache-ver.4.20.zip","src_id":"12832","5":"12832","creation_date":"1271305042","6":"1271305042"},{"0":"2620","vim_version":"7.0","1":"7.0","script_version":"4.09","2":"4.09","version_comment":"- Added completefunc_complete.\r\n- Added g:NeoComplCache_CtagsProgram option.\r\n- Added interactive termtter keyword.\r\n- Added keyword pattern of batch file.\r\n- Added same filetype lists for vimshell iexe.\r\n- Added snippet files(Thanks mfumi!).\r\n- Added syntax pattern for vimshell iexe.\r\n- Added vimshell omni completion support.\r\n- Deleted '...' pattern.\r\n- Deleted g:NeoComplCache_NonBufferFileTypeDetect option.\r\n- Disabled filename_complete in vimshell.\r\n- Don't fnamemodify in omni_complete.\r\n- Fixed analyzing bug in vim_complete.\r\n- Fixed complete common string bug.\r\n- Fixed complete length bug in omni_complete.\r\n- Fixed complete length bug in omni_complete.\r\n- Fixed ctags execution bug.\r\n- Fixed filename completion bug.\r\n- Fixed functions_prototype bug in vim_complete.\r\n- Fixed indent.\r\n- Fixed multibyte input bug.\r\n- Fixed neocomplcache#get_cur_text() bug.\r\n- Fixed neocomplcache#system.\r\n- Fixed pattern match error.\r\n- Fixed snippet newline expand in snippets_complete.\r\n- Fixed unpack dictionary bug in tags_complete.\r\n- Fixed wildcard bug.\r\n- Fixed wildcard freeze in filename_complete.\r\n- Implemented dictionary_complete.vim.\r\n- Improved NeoComplCachePrintSnippets command.\r\n- Improved analyzing extra args in vim_complete.\r\n- Improved check match filter.\r\n- Improved command completion in snippets_complete.\r\n- Improved composition filetype keyword support.\r\n- Improved filaname pattern.\r\n- Improved filetype completion.\r\n- Improved filtering word.\r\n- Improved head match.\r\n- Improved keywords in vim_complete.\r\n- Improved quickmatch behaivior.\r\n- Improved same filetype.\r\n- Improved skip directory in filename_complete.\r\n- Improved snippet alias.\r\n- Improved syntax detect in snippets_complete.\r\n- Improved syntax highlight in snippets_complete.\r\n- Improved tex pattern.\r\n- Improved trunk filename in filename_complete.\r\n- Optimized buffer_complete.\r\n- Optimized filename_complete.\r\n- Supported Visual Basic.\r\n- Supported interactive ocaml.\r\n- Supported lingr-vim.\r\n- Supported omnifunc name pattern in omni_complete.\r\n- Update lines number in buffer_complete.","3":"- Added completefunc_complete.\r\n- Added g:NeoComplCache_CtagsProgram option.\r\n- Added interactive termtter keyword.\r\n- Added keyword pattern of batch file.\r\n- Added same filetype lists for vimshell iexe.\r\n- Added snippet files(Thanks mfumi!).\r\n- Added syntax pattern for vimshell iexe.\r\n- Added vimshell omni completion support.\r\n- Deleted '...' pattern.\r\n- Deleted g:NeoComplCache_NonBufferFileTypeDetect option.\r\n- Disabled filename_complete in vimshell.\r\n- Don't fnamemodify in omni_complete.\r\n- Fixed analyzing bug in vim_complete.\r\n- Fixed complete common string bug.\r\n- Fixed complete length bug in omni_complete.\r\n- Fixed complete length bug in omni_complete.\r\n- Fixed ctags execution bug.\r\n- Fixed filename completion bug.\r\n- Fixed functions_prototype bug in vim_complete.\r\n- Fixed indent.\r\n- Fixed multibyte input bug.\r\n- Fixed neocomplcache#get_cur_text() bug.\r\n- Fixed neocomplcache#system.\r\n- Fixed pattern match error.\r\n- Fixed snippet newline expand in snippets_complete.\r\n- Fixed unpack dictionary bug in tags_complete.\r\n- Fixed wildcard bug.\r\n- Fixed wildcard freeze in filename_complete.\r\n- Implemented dictionary_complete.vim.\r\n- Improved NeoComplCachePrintSnippets command.\r\n- Improved analyzing extra args in vim_complete.\r\n- Improved check match filter.\r\n- Improved command completion in snippets_complete.\r\n- Improved composition filetype keyword support.\r\n- Improved filaname pattern.\r\n- Improved filetype completion.\r\n- Improved filtering word.\r\n- Improved head match.\r\n- Improved keywords in vim_complete.\r\n- Improved quickmatch behaivior.\r\n- Improved same filetype.\r\n- Improved skip directory in filename_complete.\r\n- Improved snippet alias.\r\n- Improved syntax detect in snippets_complete.\r\n- Improved syntax highlight in snippets_complete.\r\n- Improved tex pattern.\r\n- Improved trunk filename in filename_complete.\r\n- Optimized buffer_complete.\r\n- Optimized filename_complete.\r\n- Supported Visual Basic.\r\n- Supported interactive ocaml.\r\n- Supported lingr-vim.\r\n- Supported omnifunc name pattern in omni_complete.\r\n- Update lines number in buffer_complete.","package":"neocomplcache-4.09.zip","4":"neocomplcache-4.09.zip","src_id":"12350","5":"12350","creation_date":"1265783210","6":"1265783210"},{"0":"2620","vim_version":"7.0","1":"7.0","script_version":"4.02","2":"4.02","version_comment":"- Added C\/C++ support in omni_complete.\r\n- Added NeoComplCacheCachingDictionary command.\r\n- Added Python snippet.\r\n- Added filename pattern.\r\n- Added g:NeoComplCache_EnableDispalyParameter option.\r\n- Added g:NeoComplCache_QuickMatchPatterns option.\r\n- Added g:NeoComplCache_TagsFilterPatterns option.\r\n- Added markdown snippet.\r\n- Added same filetype.\r\n- Allow keyword trigger in snippets_complete.\r\n- Caching current buffer in include_complete.\r\n- Catch error in omni_complete.\r\n- Catch eval error in snippets_complete.\r\n- Changed g:NeoComplCache_CalcRankRandomize option as g:NeoComplCache_EnableRandomize.\r\n- Delete dup check in buffer_complete.\r\n- Deleted Filename() and g:snips_author in snippets_complete.\r\n- Deleted \\v pattern.\r\n- Deleted caching current buffer in include_complete.\r\n- Deleted caching when BufWritePost in include_complete.\r\n- Deleted calc_rank().\r\n- Deleted dup in include_complete.\r\n- Deleted g:NeoComplCache_EnableInfo option.\r\n- Deleted g:NeoComplCache_PreviousKeywordCompletion. It's default.\r\n- Deleted g:NeoComplCache_SkipInputTime option.\r\n- Deleted prev_rank.\r\n- Deleted regacy option.\r\n- Don't cache huge file in include_complete.\r\n- Don't complete within comment in vim_complete.\r\n- Don't expand environment variable in filename_complete.\r\n- Don't save empty tags file.\r\n- Don't set dup when match with next keyword.\r\n- Fixed NeoComplCacheEditRuntimeSnippets bug.\r\n- Fixed PHP pattern bug in omni_complete.\r\n- Fixed caching error in tags_complete(Thanks tosik).\r\n- Fixed disable expand when buftype is 'nofile' bug in snippets_complete.\r\n- Fixed error when execute NeoComplCacheDisable.\r\n- Fixed error when load file in include_complete.\r\n- Fixed error; when open the file of the filetype that g:NeoComplCache_KeywordPatterns does not have in include_complete.\r\n- Fixed executable bug in filename_complete.\r\n- Fixed expand snippets bug.\r\n- Fixed fatal buffer_complete bug.\r\n- Fixed fatal include_complete error.\r\n- Fixed fatal manual completion bug.\r\n- Fixed filetype bug in include_complete.\r\n- Fixed finalize error.\r\n- Fixed freeze bug in filename_complete.\r\n- Fixed haskell and ocaml patterns.\r\n- Fixed in TeX behaviour in filename_complete.\r\n- Fixed keyword bug in vim_complete.\r\n- Fixed manual completion error in omni_complete.\r\n- Fixed manual completion error.\r\n- Fixed manual completion error.\r\n- Fixed member fileter error.\r\n- Fixed output keyword error.\r\n- Fixed prefix bug.\r\n- Fixed quickmatch bug in omni_complete.\r\n- Fixed quickmatch list bug.\r\n- Fixed ruby omni_complete bug.\r\n- Fixed save cache error.\r\n- Fixed set completeopt bug.\r\n- Fixed set path pattern in Python.\r\n- Fixed snippet expand bug in snippets_complete.\r\n- Fixed tags_complete caching error.\r\n- Formatted help files.\r\n- Ignore space in snippets_complete.\r\n- Implemented <Plug>(neocomplcache_snippets_jump) in snippets_complete.\r\n- Implemented Filename() and g:snips_author for snipMate.\r\n- Implemented auto cache in tags_complete.\r\n- Implemented buffer local autocomplete lock.\r\n- Implemented environment variable completion in vim_complete.\r\n- Implemented hard tab expand in vim_complete.\r\n- Implemented intellisense like prototype echo in vim_complete.\r\n- Implemented keyword cache in omni_complete.\r\n- Implemented pseudo animation.\r\n- Implemented skip directory in filename_complete.\r\n- Implemented the static model recognition in vim_complete.\r\n- Implemented vim_complete(testing).\r\n- Improved analyze in syntax_complete.\r\n- Improved backslash escape in filename_complete.\r\n- Improved buffer caching.\r\n- Improved buffer caching.\r\n- Improved caching print.\r\n- Improved caching speed when FileType in include_complete.\r\n- Improved calc frequency.\r\n- Improved complete option in vim_complete.\r\n- Improved garbage collect in buffer_complete.\r\n- Improved garbage collect.\r\n- Improved get keyword pattern.\r\n- Improved global caching in vim_complete.\r\n- Improved html and vim keyword pattern.\r\n- Improved load complfuncs.\r\n- Improved manual completion.\r\n- Improved next keyword completion.\r\n- Improved omni patterns in omni_complete.\r\n- Improved option in vim_complete.\r\n- Improved print prototype in vim_complete.\r\n- Improved randomize.\r\n- Improved shortcut filename completion in filename_complete.\r\n- Improved skip completion.\r\n- Improved tex keyword pattern.\r\n- Improved wildcard.\r\n- Optimized speed.\r\n- Refactoringed set pattern.\r\n- Reinforced vim_complete.vim.\r\n- Restore cursor position in omni_complete.\r\n- Revised English help.\r\n- Supported backslash in vim_complete.\r\n- Supported manual plugin complete.\r\n- Supported mark down filetype.\r\n- Supported nested include file in C\/C++ filetype in include_complete.\r\n- Supported next keyword completion in filename_complete.\r\n- Supported string and dictionary candidates in omni_complete.\r\n- Supported wildcard in vim_complete and omni_complete.\r\n- Syntax_complete disabled in vim.\r\n- Use \/dev\/stdout in Linux and Mac in include_complete.\r\n- Use caching helper in plugins.\r\n- Use g:NeoComplCache_TagsFilterPatterns in omni_complete.\r\n- Use include_complete's cache in omni_complete.","3":"- Added C\/C++ support in omni_complete.\r\n- Added NeoComplCacheCachingDictionary command.\r\n- Added Python snippet.\r\n- Added filename pattern.\r\n- Added g:NeoComplCache_EnableDispalyParameter option.\r\n- Added g:NeoComplCache_QuickMatchPatterns option.\r\n- Added g:NeoComplCache_TagsFilterPatterns option.\r\n- Added markdown snippet.\r\n- Added same filetype.\r\n- Allow keyword trigger in snippets_complete.\r\n- Caching current buffer in include_complete.\r\n- Catch error in omni_complete.\r\n- Catch eval error in snippets_complete.\r\n- Changed g:NeoComplCache_CalcRankRandomize option as g:NeoComplCache_EnableRandomize.\r\n- Delete dup check in buffer_complete.\r\n- Deleted Filename() and g:snips_author in snippets_complete.\r\n- Deleted \\v pattern.\r\n- Deleted caching current buffer in include_complete.\r\n- Deleted caching when BufWritePost in include_complete.\r\n- Deleted calc_rank().\r\n- Deleted dup in include_complete.\r\n- Deleted g:NeoComplCache_EnableInfo option.\r\n- Deleted g:NeoComplCache_PreviousKeywordCompletion. It's default.\r\n- Deleted g:NeoComplCache_SkipInputTime option.\r\n- Deleted prev_rank.\r\n- Deleted regacy option.\r\n- Don't cache huge file in include_complete.\r\n- Don't complete within comment in vim_complete.\r\n- Don't expand environment variable in filename_complete.\r\n- Don't save empty tags file.\r\n- Don't set dup when match with next keyword.\r\n- Fixed NeoComplCacheEditRuntimeSnippets bug.\r\n- Fixed PHP pattern bug in omni_complete.\r\n- Fixed caching error in tags_complete(Thanks tosik).\r\n- Fixed disable expand when buftype is 'nofile' bug in snippets_complete.\r\n- Fixed error when execute NeoComplCacheDisable.\r\n- Fixed error when load file in include_complete.\r\n- Fixed error; when open the file of the filetype that g:NeoComplCache_KeywordPatterns does not have in include_complete.\r\n- Fixed executable bug in filename_complete.\r\n- Fixed expand snippets bug.\r\n- Fixed fatal buffer_complete bug.\r\n- Fixed fatal include_complete error.\r\n- Fixed fatal manual completion bug.\r\n- Fixed filetype bug in include_complete.\r\n- Fixed finalize error.\r\n- Fixed freeze bug in filename_complete.\r\n- Fixed haskell and ocaml patterns.\r\n- Fixed in TeX behaviour in filename_complete.\r\n- Fixed keyword bug in vim_complete.\r\n- Fixed manual completion error in omni_complete.\r\n- Fixed manual completion error.\r\n- Fixed manual completion error.\r\n- Fixed member fileter error.\r\n- Fixed output keyword error.\r\n- Fixed prefix bug.\r\n- Fixed quickmatch bug in omni_complete.\r\n- Fixed quickmatch list bug.\r\n- Fixed ruby omni_complete bug.\r\n- Fixed save cache error.\r\n- Fixed set completeopt bug.\r\n- Fixed set path pattern in Python.\r\n- Fixed snippet expand bug in snippets_complete.\r\n- Fixed tags_complete caching error.\r\n- Formatted help files.\r\n- Ignore space in snippets_complete.\r\n- Implemented <Plug>(neocomplcache_snippets_jump) in snippets_complete.\r\n- Implemented Filename() and g:snips_author for snipMate.\r\n- Implemented auto cache in tags_complete.\r\n- Implemented buffer local autocomplete lock.\r\n- Implemented environment variable completion in vim_complete.\r\n- Implemented hard tab expand in vim_complete.\r\n- Implemented intellisense like prototype echo in vim_complete.\r\n- Implemented keyword cache in omni_complete.\r\n- Implemented pseudo animation.\r\n- Implemented skip directory in filename_complete.\r\n- Implemented the static model recognition in vim_complete.\r\n- Implemented vim_complete(testing).\r\n- Improved analyze in syntax_complete.\r\n- Improved backslash escape in filename_complete.\r\n- Improved buffer caching.\r\n- Improved buffer caching.\r\n- Improved caching print.\r\n- Improved caching speed when FileType in include_complete.\r\n- Improved calc frequency.\r\n- Improved complete option in vim_complete.\r\n- Improved garbage collect in buffer_complete.\r\n- Improved garbage collect.\r\n- Improved get keyword pattern.\r\n- Improved global caching in vim_complete.\r\n- Improved html and vim keyword pattern.\r\n- Improved load complfuncs.\r\n- Improved manual completion.\r\n- Improved next keyword completion.\r\n- Improved omni patterns in omni_complete.\r\n- Improved option in vim_complete.\r\n- Improved print prototype in vim_complete.\r\n- Improved randomize.\r\n- Improved shortcut filename completion in filename_complete.\r\n- Improved skip completion.\r\n- Improved tex keyword pattern.\r\n- Improved wildcard.\r\n- Optimized speed.\r\n- Refactoringed set pattern.\r\n- Reinforced vim_complete.vim.\r\n- Restore cursor position in omni_complete.\r\n- Revised English help.\r\n- Supported backslash in vim_complete.\r\n- Supported manual plugin complete.\r\n- Supported mark down filetype.\r\n- Supported nested include file in C\/C++ filetype in include_complete.\r\n- Supported next keyword completion in filename_complete.\r\n- Supported string and dictionary candidates in omni_complete.\r\n- Supported wildcard in vim_complete and omni_complete.\r\n- Syntax_complete disabled in vim.\r\n- Use \/dev\/stdout in Linux and Mac in include_complete.\r\n- Use caching helper in plugins.\r\n- Use g:NeoComplCache_TagsFilterPatterns in omni_complete.\r\n- Use include_complete's cache in omni_complete.","package":"neocomplcache-4.02.zip","4":"neocomplcache-4.02.zip","src_id":"11902","5":"11902","creation_date":"1260846800","6":"1260846800"},{"0":"2620","vim_version":"7.0","1":"7.0","script_version":"3.14","2":"3.14","version_comment":"*Fatal: Fixed fatal buffer and dictionary cache bug. *\r\n    - Fixed disable auto completion bug if bugtype contains 'nofile'.\r\n    - Ignore no suffixes file in include_complete.\r\n    - Fixed snippet merge bug in snippets_complete.\r\n    - Fixed break buffer and dictionary cache bug.","3":"*Fatal: Fixed fatal buffer and dictionary cache bug. *\r\n    - Fixed disable auto completion bug if bugtype contains 'nofile'.\r\n    - Ignore no suffixes file in include_complete.\r\n    - Fixed snippet merge bug in snippets_complete.\r\n    - Fixed break buffer and dictionary cache bug.","package":"neocomplcache-3.14.zip","4":"neocomplcache-3.14.zip","src_id":"11738","5":"11738","creation_date":"1258353271","6":"1258353271"},{"0":"2620","vim_version":"7.0","1":"7.0","script_version":"3.13","2":"3.13","version_comment":"- Add '*' to a delimiter in filename_complete.\r\n- Added g:NeoComplCache_DisablePluginList option.\r\n- Added g:NeoComplCache_EnableAutoSelect option.\r\n- Added g:NeoComplCache_IncludeSuffixes option. \r\n- Added snippet indent file.\r\n- Allow dup and improved menu in omni_complete.\r\n- Allow dup in include_complete and tags_complete.\r\n- Caching buffer when CursorHold.\r\n- Changed cache file syntax.\r\n- Complfunc supported g:NeoComplCache_PluginCompletionLength option.\r\n- Deleted C omni completion support.\r\n- Deleted cpp omni support.\r\n- Deleted g:NeoComplCache_TagsAutoUpdate option.\r\n- Disable auto caching in tags_complete.\r\n- Disabled '-' wildcard.\r\n- Disabled partial match.\r\n- Don't caching readonly buffer in include_complete.\r\n- Echo error when you use old Vim.\r\n- Echo filename when caching.\r\n- Enable auto-complete in tags_complete.\r\n- Expand tilde.\r\n- Filtering same word.\r\n- Fixed auto completion bug in filename_complete.\r\n- Fixed disable completion bug.\r\n- Fixed dup check bug in syntax_complete.\r\n- Fixed error when includeexpr is empty in include_complete.\r\n- Fixed error when omnifunc is empty.\r\n- Fixed eval snippet bug.\r\n- Fixed executable bug in filename_complete.\r\n- Fixed filter bug in include_complete.\r\n- Fixed filtering bug.\r\n- Fixed keyword pattern error in include_complete.\r\n- Fixed manual completion bug.\r\n- Fixed manual completion error.\r\n- Fixed manual omni_complete error.\r\n- Fixed matchstr timing in include_complete.\r\n- Fixed menu in buffer_complete.\r\n- Fixed quick match dup bug.\r\n- Fixed regex escape bug in snippets_complete.\r\n- Fixed skip error.\r\n- Fixed tags caching bug.\r\n- Fixed wildcard bug when auto completion.\r\n- Fixed wildcard bug.\r\n- Implemented NeoComplCacheCachingTags command.\r\n- Implemented cache in tags_complete.\r\n- Implemented completion skip if previous completion is empty.\r\n- Implemented complfunc rank.\r\n- Implemented fast search.\r\n- Implemented include_complete.\r\n- Implemented member filter.\r\n- Improved buffer caching timing.\r\n- Improved caching in tags_complete and include_complete.\r\n- Improved caching timing.\r\n- Improved ctags arguments patterns.\r\n- Improved filename completion.\r\n- Improved html's keyword pattern.\r\n- Improved keyword patterns.\r\n- Improved manual completion.\r\n- Improved omni completion pattern.\r\n- Improved ps1 keyword.\r\n- Improved remove next keyword.\r\n- Improved wildcard behaivior.\r\n- Integrated complfuncs.\r\n- Open popup menu when modified.\r\n- Optimized keyword_complete.\r\n- Optimized tags_complete.\r\n- Print error when cache file is wrong.\r\n- Print filename when caching.\r\n- Recognized snippets directory of snipMate automatically.\r\n- Reimplemented g:NeoComplCache_SkipInputTime option.\r\n- Reimplemented quickmatch.\r\n- Save error log when analyzing tags.\r\n- Set completeopt-=longest.\r\n- Skip completion if too many candidates.\r\n- Split nicely when edit snippets_file.\r\n- Use complete_check().\r\n- Implemented filename wildcard.\r\n- Set completeopt-=menuone.","3":"- Add '*' to a delimiter in filename_complete.\r\n- Added g:NeoComplCache_DisablePluginList option.\r\n- Added g:NeoComplCache_EnableAutoSelect option.\r\n- Added g:NeoComplCache_IncludeSuffixes option. \r\n- Added snippet indent file.\r\n- Allow dup and improved menu in omni_complete.\r\n- Allow dup in include_complete and tags_complete.\r\n- Caching buffer when CursorHold.\r\n- Changed cache file syntax.\r\n- Complfunc supported g:NeoComplCache_PluginCompletionLength option.\r\n- Deleted C omni completion support.\r\n- Deleted cpp omni support.\r\n- Deleted g:NeoComplCache_TagsAutoUpdate option.\r\n- Disable auto caching in tags_complete.\r\n- Disabled '-' wildcard.\r\n- Disabled partial match.\r\n- Don't caching readonly buffer in include_complete.\r\n- Echo error when you use old Vim.\r\n- Echo filename when caching.\r\n- Enable auto-complete in tags_complete.\r\n- Expand tilde.\r\n- Filtering same word.\r\n- Fixed auto completion bug in filename_complete.\r\n- Fixed disable completion bug.\r\n- Fixed dup check bug in syntax_complete.\r\n- Fixed error when includeexpr is empty in include_complete.\r\n- Fixed error when omnifunc is empty.\r\n- Fixed eval snippet bug.\r\n- Fixed executable bug in filename_complete.\r\n- Fixed filter bug in include_complete.\r\n- Fixed filtering bug.\r\n- Fixed keyword pattern error in include_complete.\r\n- Fixed manual completion bug.\r\n- Fixed manual completion error.\r\n- Fixed manual omni_complete error.\r\n- Fixed matchstr timing in include_complete.\r\n- Fixed menu in buffer_complete.\r\n- Fixed quick match dup bug.\r\n- Fixed regex escape bug in snippets_complete.\r\n- Fixed skip error.\r\n- Fixed tags caching bug.\r\n- Fixed wildcard bug when auto completion.\r\n- Fixed wildcard bug.\r\n- Implemented NeoComplCacheCachingTags command.\r\n- Implemented cache in tags_complete.\r\n- Implemented completion skip if previous completion is empty.\r\n- Implemented complfunc rank.\r\n- Implemented fast search.\r\n- Implemented include_complete.\r\n- Implemented member filter.\r\n- Improved buffer caching timing.\r\n- Improved caching in tags_complete and include_complete.\r\n- Improved caching timing.\r\n- Improved ctags arguments patterns.\r\n- Improved filename completion.\r\n- Improved html's keyword pattern.\r\n- Improved keyword patterns.\r\n- Improved manual completion.\r\n- Improved omni completion pattern.\r\n- Improved ps1 keyword.\r\n- Improved remove next keyword.\r\n- Improved wildcard behaivior.\r\n- Integrated complfuncs.\r\n- Open popup menu when modified.\r\n- Optimized keyword_complete.\r\n- Optimized tags_complete.\r\n- Print error when cache file is wrong.\r\n- Print filename when caching.\r\n- Recognized snippets directory of snipMate automatically.\r\n- Reimplemented g:NeoComplCache_SkipInputTime option.\r\n- Reimplemented quickmatch.\r\n- Save error log when analyzing tags.\r\n- Set completeopt-=longest.\r\n- Skip completion if too many candidates.\r\n- Split nicely when edit snippets_file.\r\n- Use complete_check().\r\n- Implemented filename wildcard.\r\n- Set completeopt-=menuone.","package":"neocomplcache-3.13.zip","4":"neocomplcache-3.13.zip","src_id":"11715","5":"11715","creation_date":"1258082904","6":"1258082904"},{"0":"2620","vim_version":"7.0","1":"7.0","script_version":"3.03a","2":"3.03a","version_comment":"- Added ActionScript support in omni_complete.\r\n- Added NeoComplCachePrintSnippets command.\r\n- Added g:NeoComplCache_CachingPercentInStatusline option.\r\n- Added registers snippet.\r\n- Added scala support.\r\n- Added select mode mappings in snippets_complete.\r\n- Added snippet indent file.\r\n- Added xhtml snippet(Thanks just!).\r\n- Call multiple complefunc if cur_keyword_pos is equal.\r\n- Changed buffer_complete cache directory.\r\n- Clear numbered list when close popup.\r\n- Clear quickmatch cache when auto complete is skipped.\r\n- Deleted cdpath completion.\r\n- Don't select in manual completion.\r\n- Expand tilde.\r\n- Expandable a snippet including sign.\r\n- Fixed completion column bug.\r\n- Fixed css error.\r\n- Fixed cursor pos bug.\r\n- Fixed error in snippets_complete.\r\n- Fixed error when sh\/zsh file opened.\r\n- Fixed escape bug in filename_complete.\r\n- Fixed escape bug.\r\n- Fixed expand cursor bug in snippets_complete.\r\n- Fixed fatal bug when snippet expand.\r\n- Fixed fatal caching bug.\r\n- Fixed marker substitute bug.\r\n- Fixed neocomplcache#plugin#snippets_complete#expandable()'s error.\r\n- Fixed next keyword completion bug.\r\n- Fixed non-initialize error.\r\n- Fixed wildcard bug.\r\n- Implemented completion undo.\r\n- Implemented condition in snippets_complete.\r\n- Implemented fast filter.\r\n- Implemented filetype completion.\r\n- Implemented multiple keyword.\r\n- Implemented optional placeholder.\r\n- Implemented sync placeholder.\r\n- Improved caching message.\r\n- Improved caching.\r\n- Improved command's completion.\r\n- Improved filename completion.\r\n- Improved get cur_text in snippets_complete.\r\n- Improved html keyword completion.\r\n- Improved html\/xhtml keyword pattern.\r\n- Improved keymapping in snippets_complete.\r\n- Improved no new line snippet expand.\r\n- Improved quickmatch behaivior.\r\n- Improved remove next keyword.\r\n- Improved skip completion.\r\n- Improved snippet menu.\r\n- Renamed keyword_complete.vim as buffer_complete.vim.\r\n- Sort alphabetical order in snippets_complete.\r\n- Splitted filename completion and omni completion and keyword completion.\r\n- Supported abbr in omni completion.\r\n- Supported placeholder 0.\r\n- Supported same filetype lists in snippets_complete.\r\n- Supported snipMate's multi snippet.","3":"- Added ActionScript support in omni_complete.\r\n- Added NeoComplCachePrintSnippets command.\r\n- Added g:NeoComplCache_CachingPercentInStatusline option.\r\n- Added registers snippet.\r\n- Added scala support.\r\n- Added select mode mappings in snippets_complete.\r\n- Added snippet indent file.\r\n- Added xhtml snippet(Thanks just!).\r\n- Call multiple complefunc if cur_keyword_pos is equal.\r\n- Changed buffer_complete cache directory.\r\n- Clear numbered list when close popup.\r\n- Clear quickmatch cache when auto complete is skipped.\r\n- Deleted cdpath completion.\r\n- Don't select in manual completion.\r\n- Expand tilde.\r\n- Expandable a snippet including sign.\r\n- Fixed completion column bug.\r\n- Fixed css error.\r\n- Fixed cursor pos bug.\r\n- Fixed error in snippets_complete.\r\n- Fixed error when sh\/zsh file opened.\r\n- Fixed escape bug in filename_complete.\r\n- Fixed escape bug.\r\n- Fixed expand cursor bug in snippets_complete.\r\n- Fixed fatal bug when snippet expand.\r\n- Fixed fatal caching bug.\r\n- Fixed marker substitute bug.\r\n- Fixed neocomplcache#plugin#snippets_complete#expandable()'s error.\r\n- Fixed next keyword completion bug.\r\n- Fixed non-initialize error.\r\n- Fixed wildcard bug.\r\n- Implemented completion undo.\r\n- Implemented condition in snippets_complete.\r\n- Implemented fast filter.\r\n- Implemented filetype completion.\r\n- Implemented multiple keyword.\r\n- Implemented optional placeholder.\r\n- Implemented sync placeholder.\r\n- Improved caching message.\r\n- Improved caching.\r\n- Improved command's completion.\r\n- Improved filename completion.\r\n- Improved get cur_text in snippets_complete.\r\n- Improved html keyword completion.\r\n- Improved html\/xhtml keyword pattern.\r\n- Improved keymapping in snippets_complete.\r\n- Improved no new line snippet expand.\r\n- Improved quickmatch behaivior.\r\n- Improved remove next keyword.\r\n- Improved skip completion.\r\n- Improved snippet menu.\r\n- Renamed keyword_complete.vim as buffer_complete.vim.\r\n- Sort alphabetical order in snippets_complete.\r\n- Splitted filename completion and omni completion and keyword completion.\r\n- Supported abbr in omni completion.\r\n- Supported placeholder 0.\r\n- Supported same filetype lists in snippets_complete.\r\n- Supported snipMate's multi snippet.","package":"neocomplcache-3.03a.zip","4":"neocomplcache-3.03a.zip","src_id":"11522","5":"11522","creation_date":"1255425028","6":"1255425028"},{"0":"2620","vim_version":"7.0","1":"7.0","script_version":"2.75a","2":"2.75a","version_comment":"- Don't select in manual completion.\r\n- Add rank if match next keyword.\r\n- Added ChangeLog.\r\n- Added NeoComplCacheCachingSyntax command.\r\n- Added Objective-C\/C++ support.\r\n- Added css support.\r\n- Added g:NeoComplCache_PluginCompletionLength option.\r\n- Added snippet file snippet.\r\n- Caching from cache in syntax_complete.\r\n- Check cdpath in filename completion.\r\n- Convert string omni completion.\r\n- Create g:NeoComplCache_SnippetsDir directory if not exists.\r\n- Create g:NeoComplCache_TemporaryDir directory if not exists.\r\n- Delete quick match cache when BufWinEnter.\r\n- Deleted g:NeoComplCache_FilenameCompletionSkipItems option.\r\n- Dispay 'cdpath' files in filename completion.\r\n- Dispay 'w:vimshell_directory_stack' files in filename completion.\r\n- Display readonly files.\r\n- Fixed dup bug in snippets_complete.\r\n- Fixed error in manual omni completion when omnifunc is empty.\r\n- Fixed expand jump bug in snippets completion.\r\n- Fixed expand() bug in snippets_complete.\r\n- Fixed filename completion bug when environment variable used.\r\n- Fixed filename completion bug.\r\n- Fixed html omni completion error.\r\n- Fixed manual_complete wildcard bug.\r\n- Fixed no new line snippet expand bug in snippet completion.\r\n- Fixed prefix bug in filename completion.\r\n- Fixed snippet without default value expand bug.\r\n- Ignore japanese syntax message in syntax completion.\r\n- Implemented direct expantion in snippet complete.\r\n- Implemented short filename completion.\r\n- Implemented snippet alias in snippet complete.\r\n- Improved check candidate.\r\n- Improved filename completion.\r\n- Improved filename completion.\r\n- Improved g:NeoComplCache_CtagsArgumentsList in vim filetype.\r\n- Improved get cursour word.\r\n- Improved html omni completion pattern.\r\n- Improved keyword pattern.\r\n- Improved manual completion.\r\n- Improved next keyword completion.\r\n- Improved omni completion.\r\n- Improved omni completion.\r\n- Improved quick match in filename completion.\r\n- Improved quick match.\r\n- Improved quickmatch behaivior.\r\n- Improved skipped behaivior.\r\n- Improved tex keyword.\r\n- Improved vim keyword.\r\n- Insert quickmatched candidate immediately.\r\n- No ignorecase in next keyword completion.\r\n- Optimized filename completion.\r\n- Recognize next keyword in omni completion.\r\n- Search quick match if no keyword match.\r\n- Substitute $HOME into '~' in filename completion.\r\n- The quick match input does not make a cash.","3":"- Don't select in manual completion.\r\n- Add rank if match next keyword.\r\n- Added ChangeLog.\r\n- Added NeoComplCacheCachingSyntax command.\r\n- Added Objective-C\/C++ support.\r\n- Added css support.\r\n- Added g:NeoComplCache_PluginCompletionLength option.\r\n- Added snippet file snippet.\r\n- Caching from cache in syntax_complete.\r\n- Check cdpath in filename completion.\r\n- Convert string omni completion.\r\n- Create g:NeoComplCache_SnippetsDir directory if not exists.\r\n- Create g:NeoComplCache_TemporaryDir directory if not exists.\r\n- Delete quick match cache when BufWinEnter.\r\n- Deleted g:NeoComplCache_FilenameCompletionSkipItems option.\r\n- Dispay 'cdpath' files in filename completion.\r\n- Dispay 'w:vimshell_directory_stack' files in filename completion.\r\n- Display readonly files.\r\n- Fixed dup bug in snippets_complete.\r\n- Fixed error in manual omni completion when omnifunc is empty.\r\n- Fixed expand jump bug in snippets completion.\r\n- Fixed expand() bug in snippets_complete.\r\n- Fixed filename completion bug when environment variable used.\r\n- Fixed filename completion bug.\r\n- Fixed html omni completion error.\r\n- Fixed manual_complete wildcard bug.\r\n- Fixed no new line snippet expand bug in snippet completion.\r\n- Fixed prefix bug in filename completion.\r\n- Fixed snippet without default value expand bug.\r\n- Ignore japanese syntax message in syntax completion.\r\n- Implemented direct expantion in snippet complete.\r\n- Implemented short filename completion.\r\n- Implemented snippet alias in snippet complete.\r\n- Improved check candidate.\r\n- Improved filename completion.\r\n- Improved filename completion.\r\n- Improved g:NeoComplCache_CtagsArgumentsList in vim filetype.\r\n- Improved get cursour word.\r\n- Improved html omni completion pattern.\r\n- Improved keyword pattern.\r\n- Improved manual completion.\r\n- Improved next keyword completion.\r\n- Improved omni completion.\r\n- Improved omni completion.\r\n- Improved quick match in filename completion.\r\n- Improved quick match.\r\n- Improved quickmatch behaivior.\r\n- Improved skipped behaivior.\r\n- Improved tex keyword.\r\n- Improved vim keyword.\r\n- Insert quickmatched candidate immediately.\r\n- No ignorecase in next keyword completion.\r\n- Optimized filename completion.\r\n- Recognize next keyword in omni completion.\r\n- Search quick match if no keyword match.\r\n- Substitute $HOME into '~' in filename completion.\r\n- The quick match input does not make a cash.","package":"neocomplcache-2.75a.zip","4":"neocomplcache-2.75a.zip","src_id":"11351","5":"11351","creation_date":"1252554736","6":"1252554736"},{"0":"2620","vim_version":"6.0","1":"6.0","script_version":"2.66a","2":"2.66a","version_comment":"- Added English manual.\r\n- Added g:NeoComplCache_CachingDisablePattern option.\r\n- Added g:NeoComplCache_CachingLimitFileSize option.\r\n- Added snippet delete.\r\n- Caching snippets when file open.\r\n- Callable get_complete_words() and word_caching_current_line() function.\r\n- Changed short filename into ~.\r\n- Deleted wildcard from filename completion.\r\n- Don't caching readonly file.\r\n- Erb is same filetype with ruby.\r\n- Fixed ATOK X3 on when snippets expanded.\r\n- Fixed snippet expand bugs.\r\n- Fixed snippet without default value expand bug.\r\n- Fixed syntax match timing(Thanks thinca!).\r\n- Improved NeoComplCacheCachingBuffer command.\r\n- Improved css omni completion.\r\n- Improved erb snippets.\r\n- Improved filename completion.\r\n- Improved html and erb filetype.\r\n- Improved neocomplcache#keyword_complete#caching_percent.\r\n- Improved set complete function timing.\r\n- Improved vimshell keyword pattern.\r\n- Improved vimshell keyword pattern.\r\n- Substitute ... -> ..\/.. .\r\n- Substitute \\ -> \/ in Windows.\r\n- Supported escape sequence in filename completion.\r\n- g:NeoComplCache_SnippetsDir is comma-separated list.","3":"- Added English manual.\r\n- Added g:NeoComplCache_CachingDisablePattern option.\r\n- Added g:NeoComplCache_CachingLimitFileSize option.\r\n- Added snippet delete.\r\n- Caching snippets when file open.\r\n- Callable get_complete_words() and word_caching_current_line() function.\r\n- Changed short filename into ~.\r\n- Deleted wildcard from filename completion.\r\n- Don't caching readonly file.\r\n- Erb is same filetype with ruby.\r\n- Fixed ATOK X3 on when snippets expanded.\r\n- Fixed snippet expand bugs.\r\n- Fixed snippet without default value expand bug.\r\n- Fixed syntax match timing(Thanks thinca!).\r\n- Improved NeoComplCacheCachingBuffer command.\r\n- Improved css omni completion.\r\n- Improved erb snippets.\r\n- Improved filename completion.\r\n- Improved html and erb filetype.\r\n- Improved neocomplcache#keyword_complete#caching_percent.\r\n- Improved set complete function timing.\r\n- Improved vimshell keyword pattern.\r\n- Improved vimshell keyword pattern.\r\n- Substitute ... -> ..\/.. .\r\n- Substitute \\ -> \/ in Windows.\r\n- Supported escape sequence in filename completion.\r\n- g:NeoComplCache_SnippetsDir is comma-separated list.","package":"neocomplcache-2.66a.zip","4":"neocomplcache-2.66a.zip","src_id":"11164","5":"11164","creation_date":"1249874759","6":"1249874759"},{"0":"2620","vim_version":"7.0","1":"7.0","script_version":"Ver.2.62","2":"Ver.2.62","version_comment":"- Added g:NeoComplCache_FilenameCompletionSkipItems option.\r\n- Added make syntax.\r\n- Draw executable files in filename completion.\r\n- Fixed ATOK X3 on when snippets expanded.\r\n- Fixed filename completion bug on enable quick match.\r\n- Fixed keyword sort bug.\r\n- Improved filtering.\r\n- Improved long filename view.\r\n- Improved skip completion.\r\n- Improved vimshell syntax.\r\n- Put up the priority of directory in filename completion.","3":"- Added g:NeoComplCache_FilenameCompletionSkipItems option.\r\n- Added make syntax.\r\n- Draw executable files in filename completion.\r\n- Fixed ATOK X3 on when snippets expanded.\r\n- Fixed filename completion bug on enable quick match.\r\n- Fixed keyword sort bug.\r\n- Improved filtering.\r\n- Improved long filename view.\r\n- Improved skip completion.\r\n- Improved vimshell syntax.\r\n- Put up the priority of directory in filename completion.","package":"neocomplcache-2.62.zip","4":"neocomplcache-2.62.zip","src_id":"11002","5":"11002","creation_date":"1247461356","6":"1247461356"},{"0":"2620","vim_version":"7.0","1":"7.0","script_version":"2.59","2":"2.59","version_comment":"- Added g:NeoComplCache_TemporaryDir option.\r\n- Changed g:NeoComplCache_PartialCompletionStartLength default value.\r\n- Changed g:NeoComplCache_PreviousKeywordCompletion default value.\r\n- Don't caching when not buflisted in syntax complete.\r\n- Fixed E220 in tex filetype.\r\n- Fixed NeoComplCacheDisable bug.\r\n- Fixed add rank bug in snippet completion.\r\n- Fixed analyze caching bug.\r\n- Fixed caching bug.\r\n- Fixed feedkeys.\r\n- Fixed neocomplcache#keyword_complete#caching_percent() bug.\r\n- Fixed quick match.\r\n- Implemented _ snippets in snippet completion.\r\n- Implemented filename completion.\r\n- Implemented neocomplcache#manual_filename_complete().\r\n- Improved caching timing.\r\n- Improved camel case completion and underbar completion.\r\n- Improved edit snippet.\r\n- Improved filename toriming.\r\n- Improved garbage collect.\r\n- Improved skip completion.\r\n- Improved snippets_complete.\r\n- Improved wildcard.\r\n- Loadable snipMate snippets file in snippet completion.\r\n- Optimized caching.","3":"- Added g:NeoComplCache_TemporaryDir option.\r\n- Changed g:NeoComplCache_PartialCompletionStartLength default value.\r\n- Changed g:NeoComplCache_PreviousKeywordCompletion default value.\r\n- Don't caching when not buflisted in syntax complete.\r\n- Fixed E220 in tex filetype.\r\n- Fixed NeoComplCacheDisable bug.\r\n- Fixed add rank bug in snippet completion.\r\n- Fixed analyze caching bug.\r\n- Fixed caching bug.\r\n- Fixed feedkeys.\r\n- Fixed neocomplcache#keyword_complete#caching_percent() bug.\r\n- Fixed quick match.\r\n- Implemented _ snippets in snippet completion.\r\n- Implemented filename completion.\r\n- Implemented neocomplcache#manual_filename_complete().\r\n- Improved caching timing.\r\n- Improved camel case completion and underbar completion.\r\n- Improved edit snippet.\r\n- Improved filename toriming.\r\n- Improved garbage collect.\r\n- Improved skip completion.\r\n- Improved snippets_complete.\r\n- Improved wildcard.\r\n- Loadable snipMate snippets file in snippet completion.\r\n- Optimized caching.","package":"neocomplcache-2.59.zip","4":"neocomplcache-2.59.zip","src_id":"10773","5":"10773","creation_date":"1244452776","6":"1244452776"},{"0":"2620","vim_version":"7.0","1":"7.0","script_version":"2.52","2":"2.52","version_comment":"- Changed g:NeoComplCache_PreviousKeywordCompletion default value.\r\n- Improved wildcard.\r\n- Don't caching on BufEnter.\r\n- Optimized manual_complete behaivior.\r\n- Optimized NeoComplCacheCachingBuffer.\r\n- Caching on editing file.\r\n- Implemented neocomplcache#close_popup() and neocomplcache#cansel_popup().\r\n- Don't save info in keyword completion.\r\n- Improved popup menu in tags completion.\r\n- Changed 'abbr_save' into 'abbr'.\r\n- Call completefunc when original completefunc.\r\n- Implemented underbar completion.\r\n\r\n- Added g:NeoComplCache_ManualCompletionStartLength option.\r\n- Added g:NeoComplCache_EnableUnderbarCompletion option.\r\n- Added g:NeoComplCache_TryFilenameCompletion option.\r\n\r\n- Deleted g:NeoComplCache_MaxTryKeywordLength options.\r\n- Deleted NeoComplCacheCachingDictionary command.\r\n- Deleted g:NeoComplCache_TryKeywordCompletion and g:NeoComplCache_TryDefaultCompletion options.\r\n- Deleted g:NeoComplCache_MaxInfoList and g:NeoComplCache_DeleteRank0 option.\r\n\r\n- Fixed NeoComplCacheDisable bug.\r\n- Fixed neocomplcache#keyword_complete#caching_percent() bug.\r\n- Fixed analyze caching bug.\r\n- Fixed quick match.\r\n- Fixed abbr_save error.\r\n- Fixed next keyword completion bug.\r\n- Fixed caching initialize bug.\r\n- Fixed on InsertLeave error.\r\n- Fixed ignore case behaivior.\r\n- Fixed escape error.\r\n- Fixed help.\r\n- Fixed :NeoComplCacheCachingBuffer bug.\r\n- Fixed menu padding.\r\n- Fixed caching error.","3":"- Changed g:NeoComplCache_PreviousKeywordCompletion default value.\r\n- Improved wildcard.\r\n- Don't caching on BufEnter.\r\n- Optimized manual_complete behaivior.\r\n- Optimized NeoComplCacheCachingBuffer.\r\n- Caching on editing file.\r\n- Implemented neocomplcache#close_popup() and neocomplcache#cansel_popup().\r\n- Don't save info in keyword completion.\r\n- Improved popup menu in tags completion.\r\n- Changed 'abbr_save' into 'abbr'.\r\n- Call completefunc when original completefunc.\r\n- Implemented underbar completion.\r\n\r\n- Added g:NeoComplCache_ManualCompletionStartLength option.\r\n- Added g:NeoComplCache_EnableUnderbarCompletion option.\r\n- Added g:NeoComplCache_TryFilenameCompletion option.\r\n\r\n- Deleted g:NeoComplCache_MaxTryKeywordLength options.\r\n- Deleted NeoComplCacheCachingDictionary command.\r\n- Deleted g:NeoComplCache_TryKeywordCompletion and g:NeoComplCache_TryDefaultCompletion options.\r\n- Deleted g:NeoComplCache_MaxInfoList and g:NeoComplCache_DeleteRank0 option.\r\n\r\n- Fixed NeoComplCacheDisable bug.\r\n- Fixed neocomplcache#keyword_complete#caching_percent() bug.\r\n- Fixed analyze caching bug.\r\n- Fixed quick match.\r\n- Fixed abbr_save error.\r\n- Fixed next keyword completion bug.\r\n- Fixed caching initialize bug.\r\n- Fixed on InsertLeave error.\r\n- Fixed ignore case behaivior.\r\n- Fixed escape error.\r\n- Fixed help.\r\n- Fixed :NeoComplCacheCachingBuffer bug.\r\n- Fixed menu padding.\r\n- Fixed caching error.","package":"neocomplcache-2.52.zip","4":"neocomplcache-2.52.zip","src_id":"10625","5":"10625","creation_date":"1242633904","6":"1242633904"},{"0":"2620","vim_version":"7.0","1":"7.0","script_version":"2.41","2":"2.41","version_comment":"- Improved empty check.\r\n- Fixed eval bug in snippet complete.\r\n- Fixed include bug in snippet complete.","3":"- Improved empty check.\r\n- Fixed eval bug in snippet complete.\r\n- Fixed include bug in snippet complete.","package":"neocomplcache-2.41.zip","4":"neocomplcache-2.41.zip","src_id":"10556","5":"10556","creation_date":"1241682325","6":"1241682325"},{"0":"2620","vim_version":"7.0","1":"7.0","script_version":"2.40","2":"2.40","version_comment":"Upload zip version.","3":"Upload zip version.","package":"neocomplcache-2.40.zip","4":"neocomplcache-2.40.zip","src_id":"10554","5":"10554","creation_date":"1241663991","6":"1241663991"},{"0":"2620","vim_version":"7.0","1":"7.0","script_version":"2.40","2":"2.40","version_comment":"- Optimized caching in small files.\r\n- Deleted buffer dictionary.\r\n- Display cached from buffer.\r\n- Changed g:NeoComplCache_MaxInfoList default value.\r\n- Improved calc rank.\r\n- Improved caching timing.\r\n- Added NeoComplCacheCachingDisable and g:NeoComplCacheCachingEnable commands.\r\n- Fixed commentout bug in snippet complete.\r\n- Fixed syntax highlight.\r\n- Overwrite snippet if name is same.\r\n- Caching on InsertLeave.\r\n- Manual completion add wildcard when input non alphabetical character.\r\n- Fixed menu error in syntax complete.\r\n- Fixed typo.\r\n- Optimized caching.\r\n- Added g:NeoComplCache_SkipCompletionTime option.\r\n- Added g:NeoComplCache_SkipInputTime option.\r\n- Changed g:NeoComplCache_SlowCompleteSkip option into g:NeoComplCache_EnableSkipCompletion.\r\n- Improved ruby omni pattern.\r\n- Optimized syntax complete.\r\n- Delete command abbreviations in vim filetype.","3":"- Optimized caching in small files.\r\n- Deleted buffer dictionary.\r\n- Display cached from buffer.\r\n- Changed g:NeoComplCache_MaxInfoList default value.\r\n- Improved calc rank.\r\n- Improved caching timing.\r\n- Added NeoComplCacheCachingDisable and g:NeoComplCacheCachingEnable commands.\r\n- Fixed commentout bug in snippet complete.\r\n- Fixed syntax highlight.\r\n- Overwrite snippet if name is same.\r\n- Caching on InsertLeave.\r\n- Manual completion add wildcard when input non alphabetical character.\r\n- Fixed menu error in syntax complete.\r\n- Fixed typo.\r\n- Optimized caching.\r\n- Added g:NeoComplCache_SkipCompletionTime option.\r\n- Added g:NeoComplCache_SkipInputTime option.\r\n- Changed g:NeoComplCache_SlowCompleteSkip option into g:NeoComplCache_EnableSkipCompletion.\r\n- Improved ruby omni pattern.\r\n- Optimized syntax complete.\r\n- Delete command abbreviations in vim filetype.","package":"neocomplcache-2.40.tar.gz","4":"neocomplcache-2.40.tar.gz","src_id":"10541","5":"10541","creation_date":"1241578890","6":"1241578890"},{"0":"2620","vim_version":"7.0","1":"7.0","script_version":"2.36","2":"2.36","version_comment":"Initial version.","3":"Initial version.","package":"neocomplcache-2.36.tar.gz","4":"neocomplcache-2.36.tar.gz","src_id":"10461","5":"10461","creation_date":"1240806439","6":"1240806439"}]},"2619":{"script_id":"2619","0":"2619","script_name":"textobj-function","1":"textobj-function","script_type":"utility","2":"utility","summary":"Text object for a function","3":"Text object for a function","description":"*textobj-function* is a Vim plugin to provide universal text objects for\r\nvarious kinds of functions.  For example, you can select any function with\r\n|<Plug>(textobj-function-a)| \/ |<Plug>(textobj-function-i)| (default key\r\nbindings: af \/ if).\r\n\r\nThe definition of a \"function\" is usually differed depending on what you are\r\nediting, so at first, you have to tell the definition of what kind of function\r\nyou want to select to textobj-function.  By default, textobj-function knows\r\nabout functions in the following languages:\r\n\t\t\t\t\t    *textobj-function-known-languages*\r\n- C language\t\t|textobj-function-c|\r\n- Vim script\t\t|textobj-function-vim|\r\n\r\nIf you want to tell about more functions in other languages, see\r\n|textobj-function-customizing| for how to tell and\r\nafter\/ftplugin\/*\/textobj-function.vim for the samples.\r\n\r\nRequirements:\r\n- Vim 7.2 or later\r\n- |textobj-user| 0.3.7 or later (vimscript#2100)\r\n\r\nLatest version:\r\nhttp:\/\/github.com\/kana\/vim-textobj-function\r\n\r\nDocument in HTML format:\r\nhttp:\/\/kana.github.com\/config\/vim\/textobj-function.html","4":"*textobj-function* is a Vim plugin to provide universal text objects for\r\nvarious kinds of functions.  For example, you can select any function with\r\n|<Plug>(textobj-function-a)| \/ |<Plug>(textobj-function-i)| (default key\r\nbindings: af \/ if).\r\n\r\nThe definition of a \"function\" is usually differed depending on what you are\r\nediting, so at first, you have to tell the definition of what kind of function\r\nyou want to select to textobj-function.  By default, textobj-function knows\r\nabout functions in the following languages:\r\n\t\t\t\t\t    *textobj-function-known-languages*\r\n- C language\t\t|textobj-function-c|\r\n- Vim script\t\t|textobj-function-vim|\r\n\r\nIf you want to tell about more functions in other languages, see\r\n|textobj-function-customizing| for how to tell and\r\nafter\/ftplugin\/*\/textobj-function.vim for the samples.\r\n\r\nRequirements:\r\n- Vim 7.2 or later\r\n- |textobj-user| 0.3.7 or later (vimscript#2100)\r\n\r\nLatest version:\r\nhttp:\/\/github.com\/kana\/vim-textobj-function\r\n\r\nDocument in HTML format:\r\nhttp:\/\/kana.github.com\/config\/vim\/textobj-function.html","install_details":"...","5":"...","first_name":"Kana","6":"Kana","last_name":"Natsuno","7":"Natsuno","releases":[{"0":"2619","vim_version":"7.0","1":"7.0","script_version":"0.1.0","2":"0.1.0","version_comment":"Initial upload","3":"Initial upload","package":"vim-textobj-function-0.1.0.zip","4":"vim-textobj-function-0.1.0.zip","src_id":"10453","5":"10453","creation_date":"1240663033","6":"1240663033"}]},"2618":{"script_id":"2618","0":"2618","script_name":"ctk.vim","1":"ctk.vim","script_type":"utility","2":"utility","summary":"a fast compile and run plugin for Vim","3":"a fast compile and run plugin for Vim","description":"ctk is a fast compile and run plugin for Vim. \r\n\r\n-- you can add a modeline in your source code to modifie the behavior of ctk. \r\n-- you can press a hotkey to invoke compiler.\r\n-- you can press a key to compiler and run your program.\r\n-- you can add some trigger word to change your compiler's behavior. just like :CC debug\r\n\r\ninstall it, and press :h ctk to see details help","4":"ctk is a fast compile and run plugin for Vim. \r\n\r\n-- you can add a modeline in your source code to modifie the behavior of ctk. \r\n-- you can press a hotkey to invoke compiler.\r\n-- you can press a key to compiler and run your program.\r\n-- you can add some trigger word to change your compiler's behavior. just like :CC debug\r\n\r\ninstall it, and press :h ctk to see details help","install_details":"1. use Vim to open ctk.vba, and press :so%<CR> (that <CR> means return key).\r\n2. drop .compiler_info to your runtimepath folder, see the output of \":ec &rtp\". try :h 'rtp' to get help.","5":"1. use Vim to open ctk.vba, and press :so%<CR> (that <CR> means return key).\r\n2. drop .compiler_info to your runtimepath folder, see the output of \":ec &rtp\". try :h 'rtp' to get help.","first_name":"Wxyarv","6":"Wxyarv","last_name":"Wang","7":"Wang","releases":[{"0":"2618","vim_version":"7.2","1":"7.2","script_version":"0.6","2":"0.6","version_comment":"fix bugs","3":"fix bugs","package":"ctk.vba","4":"ctk.vba","src_id":"15260","5":"15260","creation_date":"1300634365","6":"1300634365"},{"0":"2618","vim_version":"7.0","1":"7.0","script_version":"0.5","2":"0.5","version_comment":"  - support upcase letter placeholder\r\n  - remain placeholder will substitute environment variables. add a option ctk_envvarfmt to detect the variable formant.\r\n  - add RefreshCTK command, and auto refresh all buffer after EditCompilerInfo command.\r\n","3":"  - support upcase letter placeholder\r\n  - remain placeholder will substitute environment variables. add a option ctk_envvarfmt to detect the variable formant.\r\n  - add RefreshCTK command, and auto refresh all buffer after EditCompilerInfo command.\r\n","package":"ctk.vba","4":"ctk.vba","src_id":"12207","5":"12207","creation_date":"1264685480","6":"1264685480"},{"0":"2618","vim_version":"7.0","1":"7.0","script_version":"0.4-bugfix","2":"0.4-bugfix","version_comment":"NOTE: if you have you own .compiler_info file, please backup it and install new version, and you can diff two info file and decide how to merge them.\r\n\r\n  - add python support in .compiler_info file\r\n  - add a new \"#RUN_DIRECT\" syntax for support script file. see .compiler_info \"Python\" section and :h ctk-run-direct.\r\n  - fix the encoding conversion error in previous version","3":"NOTE: if you have you own .compiler_info file, please backup it and install new version, and you can diff two info file and decide how to merge them.\r\n\r\n  - add python support in .compiler_info file\r\n  - add a new \"#RUN_DIRECT\" syntax for support script file. see .compiler_info \"Python\" section and :h ctk-run-direct.\r\n  - fix the encoding conversion error in previous version","package":"ctk.vba","4":"ctk.vba","src_id":"11554","5":"11554","creation_date":"1256107402","6":"1256107402"},{"0":"2618","vim_version":"7.0","1":"7.0","script_version":"0.4-bugfix","2":"0.4-bugfix","version_comment":"  - add option g:ctk_cmdenc\r\n  - add discribes of using :silent\/:redir command in cmd or run in doc\r\n  - fix the bug when compile multi-times, the += operator in modeline acts incorrect.","3":"  - add option g:ctk_cmdenc\r\n  - add discribes of using :silent\/:redir command in cmd or run in doc\r\n  - fix the bug when compile multi-times, the += operator in modeline acts incorrect.","package":"ctk.vba","4":"ctk.vba","src_id":"11128","5":"11128","creation_date":"1249357394","6":"1249357394"},{"0":"2618","vim_version":"7.0","1":"7.0","script_version":"0.4","2":"0.4","version_comment":"  - fix the bug StopCTK doesn't stop ctk.\r\n  - change the usage of some command, see :h ctk-usage for details.\r\n  - add command \":SetExtensionName\" command.\r\n  - modfiy the document.","3":"  - fix the bug StopCTK doesn't stop ctk.\r\n  - change the usage of some command, see :h ctk-usage for details.\r\n  - add command \":SetExtensionName\" command.\r\n  - modfiy the document.","package":"ctk.vba","4":"ctk.vba","src_id":"11052","5":"11052","creation_date":"1248266370","6":"1248266370"},{"0":"2618","vim_version":"7.0","1":"7.0","script_version":"0.3-bugfix","2":"0.3-bugfix","version_comment":"-- fix the bug 'gc' and 'gC' use previous entry (it's quite sick!)\r\n-- fix the bug when the program name is same as Unix standard program (e.g. test), the Unix program will be run instead of ours. ","3":"-- fix the bug 'gc' and 'gC' use previous entry (it's quite sick!)\r\n-- fix the bug when the program name is same as Unix standard program (e.g. test), the Unix program will be run instead of ours. ","package":"ctk.vba","4":"ctk.vba","src_id":"10996","5":"10996","creation_date":"1247318826","6":"1247318826"},{"0":"2618","vim_version":"7.0","1":"7.0","script_version":"0.3-bugfix","2":"0.3-bugfix","version_comment":"-- fixed the syntax error in doc file :-) thanks to yiran.\r\n-- fixed the issue that ctk raise error when :RUN asm.\r\n-- add quoted place-holder's doc describe.\r\n","3":"-- fixed the syntax error in doc file :-) thanks to yiran.\r\n-- fixed the issue that ctk raise error when :RUN asm.\r\n-- add quoted place-holder's doc describe.\r\n","package":"ctk.vba","4":"ctk.vba","src_id":"10988","5":"10988","creation_date":"1247248877","6":"1247248877"},{"0":"2618","vim_version":"7.0","1":"7.0","script_version":"0.3-bugfix","2":"0.3-bugfix","version_comment":"-- fix the bug when you press \"gc\" and there isn't any window has b:compiler_info, ctk will raise a error.\r\n-- remove the process of autocmd FuncUndefined\r\n-- remove s:find_source() function, and just find b:compiler_info when needed.","3":"-- fix the bug when you press \"gc\" and there isn't any window has b:compiler_info, ctk will raise a error.\r\n-- remove the process of autocmd FuncUndefined\r\n-- remove s:find_source() function, and just find b:compiler_info when needed.","package":"ctk.vba","4":"ctk.vba","src_id":"10984","5":"10984","creation_date":"1247199747","6":"1247199747"},{"0":"2618","vim_version":"7.0","1":"7.0","script_version":"0.3-bugfix","2":"0.3-bugfix","version_comment":"  - thanks to lee, change a syntax error :-)\r\n  - correct all wrong marks in script.\r\n  - in linux console, the RUN can't stop after program runs, so didn't redraw in linux console.","3":"  - thanks to lee, change a syntax error :-)\r\n  - correct all wrong marks in script.\r\n  - in linux console, the RUN can't stop after program runs, so didn't redraw in linux console.","package":"ctk.vba","4":"ctk.vba","src_id":"10946","5":"10946","creation_date":"1246765563","6":"1246765563"},{"0":"2618","vim_version":"7.0","1":"7.0","script_version":"0.3-bugfix","2":"0.3-bugfix","version_comment":"just bugfix. and fix some issues in Windows.","3":"just bugfix. and fix some issues in Windows.","package":"ctk.vba","4":"ctk.vba","src_id":"10898","5":"10898","creation_date":"1246025771","6":"1246025771"},{"0":"2618","vim_version":"7.0","1":"7.0","script_version":"0.3","2":"0.3","version_comment":"-- add a quoted tag support\r\n-- changed document\r\n-- make info line's syntax be the same as the modeline's\r\n-- remove the '*' command-type. you can use :call foobar() to replace it.","3":"-- add a quoted tag support\r\n-- changed document\r\n-- make info line's syntax be the same as the modeline's\r\n-- remove the '*' command-type. you can use :call foobar() to replace it.","package":"ctk.vba","4":"ctk.vba","src_id":"10567","5":"10567","creation_date":"1241937729","6":"1241937729"},{"0":"2618","vim_version":"7.0","1":"7.0","script_version":"0.2-bugfix","2":"0.2-bugfix","version_comment":"bugfix: autonamed file didn't use default output name.","3":"bugfix: autonamed file didn't use default output name.","package":"ctk.vba","4":"ctk.vba","src_id":"10561","5":"10561","creation_date":"1241775127","6":"1241775127"},{"0":"2618","vim_version":"7.0","1":"7.0","script_version":"0.2-bugfix","2":"0.2-bugfix","version_comment":"-- fix the bug that quickfix window won't close when compiling success.","3":"-- fix the bug that quickfix window won't close when compiling success.","package":"ctk.vba","4":"ctk.vba","src_id":"10483","5":"10483","creation_date":"1240976592","6":"1240976592"},{"0":"2618","vim_version":"7.0","1":"7.0","script_version":"0.2-bugfix","2":"0.2-bugfix","version_comment":"-- change the way to calculate the index of temporary file.\r\n-- change the way to rename file. the file has its name won't rename now (it's my mistake...)","3":"-- change the way to calculate the index of temporary file.\r\n-- change the way to rename file. the file has its name won't rename now (it's my mistake...)","package":"ctk.vba","4":"ctk.vba","src_id":"10472","5":"10472","creation_date":"1240915418","6":"1240915418"},{"0":"2618","vim_version":"7.0","1":"7.0","script_version":"0.2-bugfix","2":"0.2-bugfix","version_comment":"sorry for forgot to turn-off the debug message...","3":"sorry for forgot to turn-off the debug message...","package":"ctk.vba","4":"ctk.vba","src_id":"10458","5":"10458","creation_date":"1240785841","6":"1240785841"},{"0":"2618","vim_version":"7.0","1":"7.0","script_version":"0.2-bugfix","2":"0.2-bugfix","version_comment":"add some stuff in doc, and changed the behavior of :CC\r\n\r\nif your compile command is \":foobar\" (that is, a Vim command instead of a shell command), the output will disappear at command line. see :h :RUN","3":"add some stuff in doc, and changed the behavior of :CC\r\n\r\nif your compile command is \":foobar\" (that is, a Vim command instead of a shell command), the output will disappear at command line. see :h :RUN","package":"ctk.vba","4":"ctk.vba","src_id":"10456","5":"10456","creation_date":"1240727916","6":"1240727916"},{"0":"2618","vim_version":"7.0","1":"7.0","script_version":"0.2","2":"0.2","version_comment":"Initial upload","3":"Initial upload","package":"ctk.vba","4":"ctk.vba","src_id":"10451","5":"10451","creation_date":"1240660325","6":"1240660325"}]},"2617":{"script_id":"2617","0":"2617","script_name":"SpamAssassin syntax","1":"SpamAssassin syntax","script_type":"syntax","2":"syntax","summary":"Syntax highlighting for SpamAssassin config files","3":"Syntax highlighting for SpamAssassin config files","description":"* Regular expression highlighting (from perl)\r\n* COMPLETE recognition of all settings with a good understanding of syntax\r\n* Settings recognized include all plugins shipped with SA plus a few 3rd-party plugins.\r\n\r\nSpell-check is enabled on various pieces for which it is appropriate (vim 7+, you must turn it on first).\r\n\r\nThis has also been posted to the spamassassin users mailing list.","4":"* Regular expression highlighting (from perl)\r\n* COMPLETE recognition of all settings with a good understanding of syntax\r\n* Settings recognized include all plugins shipped with SA plus a few 3rd-party plugins.\r\n\r\nSpell-check is enabled on various pieces for which it is appropriate (vim 7+, you must turn it on first).\r\n\r\nThis has also been posted to the spamassassin users mailing list.","install_details":"Just like any syntax file.\r\n\r\nSave this file to ~\/.vim\/syntax\/spamassassin.vim and add the following to your ~\/.vim\/filetype.vim:\r\n\r\naugroup filedetect\r\n    au BufRead,BufNewFile user_prefs,*.cf,*.pre setfiletype spamassassin\r\naugroup END\r\n\r\nNote that this will override Postfix's main.cf and Sendmail's sendmail.cf ... I'm not sure how to rectify that.\r\n\r\nTo install it system-wide, save the attached file as \/usr\/share\/vim\/vim[0-9]*\/syntax\/spamassassin.vim and edit\r\n\/usr\/share\/vim\/vim[0-9]*\/filetype.vim in a manner similar to the local filetype.vim edit noted above.","5":"Just like any syntax file.\r\n\r\nSave this file to ~\/.vim\/syntax\/spamassassin.vim and add the following to your ~\/.vim\/filetype.vim:\r\n\r\naugroup filedetect\r\n    au BufRead,BufNewFile user_prefs,*.cf,*.pre setfiletype spamassassin\r\naugroup END\r\n\r\nNote that this will override Postfix's main.cf and Sendmail's sendmail.cf ... I'm not sure how to rectify that.\r\n\r\nTo install it system-wide, save the attached file as \/usr\/share\/vim\/vim[0-9]*\/syntax\/spamassassin.vim and edit\r\n\/usr\/share\/vim\/vim[0-9]*\/filetype.vim in a manner similar to the local filetype.vim edit noted above.","first_name":"Adam","6":"Adam","last_name":"Katz","7":"Katz","releases":[{"0":"2617","vim_version":"6.0","1":"6.0","script_version":"3.3","2":"3.3","version_comment":"Mark any non-comment following a regex as an error, fix bug with comment recognition.  I'm now date-stamping my versions (see file comments) so that unpublished edits can be tracked without destroying the published versions.","3":"Mark any non-comment following a regex as an error, fix bug with comment recognition.  I'm now date-stamping my versions (see file comments) so that unpublished edits can be tracked without destroying the published versions.","package":"spamassassin.vim","4":"spamassassin.vim","src_id":"15948","5":"15948","creation_date":"1308691908","6":"1308691908"},{"0":"2617","vim_version":"6.0","1":"6.0","script_version":"3.2","2":"3.2","version_comment":"Fixed saFunction (it needs to be in a cluster after all, I was previously highlighting \/anything\/ that looked like a function).  Added support for new 'reuse' option.","3":"Fixed saFunction (it needs to be in a cluster after all, I was previously highlighting \/anything\/ that looked like a function).  Added support for new 'reuse' option.","package":"spamassassin.vim","4":"spamassassin.vim","src_id":"14189","5":"14189","creation_date":"1289006526","6":"1289006526"},{"0":"2617","vim_version":"6.0","1":"6.0","script_version":"3.1","2":"3.1","version_comment":"Extensive use of syn-cluster makes this more easily abstracted for additional plugins.  Plugin section broken into how it ships; enabled, disabled, not (third-party).  Each plugin section is fully independent and therefore can easily be deactivated or used as a model for a new plugin.  Rewrapped to wider view since lines were way over the 80-col size anyway.  Things are more properly contained now as well.  Removed abstraction for highlighting due to increased version dependency.  Added support for sa3.3 plugins and the remaining missing shipped plugins, plus iXhash.  Fixed regex detection (m\/\/ and friends were broken in 3.0).","3":"Extensive use of syn-cluster makes this more easily abstracted for additional plugins.  Plugin section broken into how it ships; enabled, disabled, not (third-party).  Each plugin section is fully independent and therefore can easily be deactivated or used as a model for a new plugin.  Rewrapped to wider view since lines were way over the 80-col size anyway.  Things are more properly contained now as well.  Removed abstraction for highlighting due to increased version dependency.  Added support for sa3.3 plugins and the remaining missing shipped plugins, plus iXhash.  Fixed regex detection (m\/\/ and friends were broken in 3.0).","package":"spamassassin.vim","4":"spamassassin.vim","src_id":"14169","5":"14169","creation_date":"1288746081","6":"1288746081"},{"0":"2617","vim_version":"6.0","1":"6.0","script_version":"3.0","2":"3.0","version_comment":"MAJOR efficiency increase.  This is now usable on large files.  \r\n\r\nRemoved most \\%(inefficient zero-width lookbehind\\)\\@<= portions in favor of using nextgroup since \\%(this zero-width lookbehind can't contain ANY highlighting\\)\\zs  also fixed several outstanding minor bugs and added a few new highlighted areas (specifically for meta rules).  \r\n\r\nNow that I've tested this with a genuine vim 5.8, I'm pretty sure it never worked.  Required vim version bumped to 6.0.  \r\n\r\nOffline edits put this at 2.8 before 3.0, though 2.6+ were all very minor and I tend to err on the side of bumping up the version when my systems are out of sync.","3":"MAJOR efficiency increase.  This is now usable on large files.  \r\n\r\nRemoved most \\%(inefficient zero-width lookbehind\\)\\@<= portions in favor of using nextgroup since \\%(this zero-width lookbehind can't contain ANY highlighting\\)\\zs  also fixed several outstanding minor bugs and added a few new highlighted areas (specifically for meta rules).  \r\n\r\nNow that I've tested this with a genuine vim 5.8, I'm pretty sure it never worked.  Required vim version bumped to 6.0.  \r\n\r\nOffline edits put this at 2.8 before 3.0, though 2.6+ were all very minor and I tend to err on the side of bumping up the version when my systems are out of sync.","package":"spamassassin.vim","4":"spamassassin.vim","src_id":"14164","5":"14164","creation_date":"1288662481","6":"1288662481"},{"0":"2617","vim_version":"5.7","1":"5.7","script_version":"2.0","2":"2.0","version_comment":"Cleanup; no longer taking perl.vim wholesale (by require), now importing only the regexp matcher.  Also made other regexp tweaks.  Version bump to a .0-release to indicate pseudo-independence from perl syntax garbage (no more dependency and version mismatches), also indicating the parts newly implemented from scratch rather than free from perl.vim.","3":"Cleanup; no longer taking perl.vim wholesale (by require), now importing only the regexp matcher.  Also made other regexp tweaks.  Version bump to a .0-release to indicate pseudo-independence from perl syntax garbage (no more dependency and version mismatches), also indicating the parts newly implemented from scratch rather than free from perl.vim.","package":"spamassassin.vim","4":"spamassassin.vim","src_id":"11655","5":"11655","creation_date":"1257294616","6":"1257294616"},{"0":"2617","vim_version":"5.7","1":"5.7","script_version":"1.11","2":"1.11","version_comment":"Fixed syntax clearing bug found in 7.0 (but not 6.x or 7.1+)","3":"Fixed syntax clearing bug found in 7.0 (but not 6.x or 7.1+)","package":"spamassassin.vim","4":"spamassassin.vim","src_id":"11653","5":"11653","creation_date":"1257207930","6":"1257207930"},{"0":"2617","vim_version":"5.7","1":"5.7","script_version":"1.10","2":"1.10","version_comment":"fix bug introduced in 1.9 (header regexps using just \/\/ weren't colored)","3":"fix bug introduced in 1.9 (header regexps using just \/\/ weren't colored)","package":"spamassassin.vim","4":"spamassassin.vim","src_id":"11617","5":"11617","creation_date":"1256778012","6":"1256778012"},{"0":"2617","vim_version":"5.7","1":"5.7","script_version":"1.9","2":"1.9","version_comment":"Updates include fixed alt regexp handling, support for :name and the like, if-unset, SA pseudo-headers, better handling of exists and eval.","3":"Updates include fixed alt regexp handling, support for :name and the like, if-unset, SA pseudo-headers, better handling of exists and eval.","package":"spamassassin.vim","4":"spamassassin.vim","src_id":"11616","5":"11616","creation_date":"1256777003","6":"1256777003"},{"0":"2617","vim_version":"5.7","1":"5.7","script_version":"1.8","2":"1.8","version_comment":"Faster regexs using \\%(query\\) notation (equiv to perl's (?:query) notation) and other extremely minor tweaks like 'exists' no longer accepting functions.  I haven't touched this since 5\/4\/9, as reflected in internal release date, but I (wrongly) figured I'd tweak it more before another release.  It's pretty much done now, so I don't expect more releases.  There are two remaining TODO items:  one for reorganization (code cleanup) which is mostly unnecessary, and one assuming there is more perl highlighting to disable\/tweak (though I haven't seen any evidence recently).  One more TODO is the recognition of regexs using alternate bounding characters like apostrophe instead of slash.","3":"Faster regexs using \\%(query\\) notation (equiv to perl's (?:query) notation) and other extremely minor tweaks like 'exists' no longer accepting functions.  I haven't touched this since 5\/4\/9, as reflected in internal release date, but I (wrongly) figured I'd tweak it more before another release.  It's pretty much done now, so I don't expect more releases.  There are two remaining TODO items:  one for reorganization (code cleanup) which is mostly unnecessary, and one assuming there is more perl highlighting to disable\/tweak (though I haven't seen any evidence recently).  One more TODO is the recognition of regexs using alternate bounding characters like apostrophe instead of slash.","package":"spamassassin.vim","4":"spamassassin.vim","src_id":"10917","5":"10917","creation_date":"1246460268","6":"1246460268"},{"0":"2617","vim_version":"5.7","1":"5.7","script_version":"1.7","2":"1.7","version_comment":"Oops, there were some things unique to vim6+ and 7+ in there (removed perl syntax groups).  I've cleaned that up.  This has been tested with vim7.1, vim7.0, vim6.0, and vim6.0 with the perl.vim syntax from vim5.5.","3":"Oops, there were some things unique to vim6+ and 7+ in there (removed perl syntax groups).  I've cleaned that up.  This has been tested with vim7.1, vim7.0, vim6.0, and vim6.0 with the perl.vim syntax from vim5.5.","package":"spamassassin.vim","4":"spamassassin.vim","src_id":"10504","5":"10504","creation_date":"1241193119","6":"1241193119"},{"0":"2617","vim_version":"5.7","1":"5.7","script_version":"1.6","2":"1.6","version_comment":"Fixed remaining known bugs.  Template Tags are now contained in the header-modifying portions only.  Functions are now colored properly, with known common ones showing a different color (but do we care?).  Arguments to functions are better handled.  Parentheses are now colored.  Operators in meta lines are now colored.  URIBL types are recognized.","3":"Fixed remaining known bugs.  Template Tags are now contained in the header-modifying portions only.  Functions are now colored properly, with known common ones showing a different color (but do we care?).  Arguments to functions are better handled.  Parentheses are now colored.  Operators in meta lines are now colored.  URIBL types are recognized.","package":"spamassassin.vim","4":"spamassassin.vim","src_id":"10500","5":"10500","creation_date":"1241140025","6":"1241140025"},{"0":"2617","vim_version":"5.7","1":"5.7","script_version":"1.5","2":"1.5","version_comment":"Added the missing two plugins, better clearing of unwanted perl bits, fixed path and IP address recognizing, better handling of spelling on overflowed describe lines, and support for 3rd-party plugins URICountry (thanks Stefan Luetje) and SAGrey.","3":"Added the missing two plugins, better clearing of unwanted perl bits, fixed path and IP address recognizing, better handling of spelling on overflowed describe lines, and support for 3rd-party plugins URICountry (thanks Stefan Luetje) and SAGrey.","package":"spamassassin.vim","4":"spamassassin.vim","src_id":"10466","5":"10466","creation_date":"1240884401","6":"1240884401"},{"0":"2617","vim_version":"5.7","1":"5.7","script_version":"1.2","2":"1.2","version_comment":"Initial upload","3":"Initial upload","package":"spamassassin.vim","4":"spamassassin.vim","src_id":"10443","5":"10443","creation_date":"1240525902","6":"1240525902"}]},"2616":{"script_id":"2616","0":"2616","script_name":"graywh","1":"graywh","script_type":"color scheme","2":"color scheme","summary":"My personal colorscheme","3":"My personal colorscheme","description":"This colorscheme defines gui and 16-color terminal settings.  For 88 or 256-color terminals, use CSApprox.vim (vimscript #2390).\r\n\r\nhttps:\/\/github.com\/graywh\/dotfiles\/blob\/master\/.vim\/colors\/graywh.vim","4":"This colorscheme defines gui and 16-color terminal settings.  For 88 or 256-color terminals, use CSApprox.vim (vimscript #2390).\r\n\r\nhttps:\/\/github.com\/graywh\/dotfiles\/blob\/master\/.vim\/colors\/graywh.vim","install_details":"Drop into the 'colors' directory of your vim config.","5":"Drop into the 'colors' directory of your vim config.","first_name":"Will","6":"Will","last_name":"Gray","7":"Gray","releases":[{"0":"2616","vim_version":"6.0","1":"6.0","script_version":"2","2":"2","version_comment":" ","3":" ","package":"graywh.vim","4":"graywh.vim","src_id":"13081","5":"13081","creation_date":"1275413003","6":"1275413003"},{"0":"2616","vim_version":"6.0","1":"6.0","script_version":"1","2":"1","version_comment":"Initial upload","3":"Initial upload","package":"graywh.vim","4":"graywh.vim","src_id":"10438","5":"10438","creation_date":"1240437377","6":"1240437377"}]},"2615":{"script_id":"2615","0":"2615","script_name":"vimtemplate","1":"vimtemplate","script_type":"utility","2":"utility","summary":"MRU-like simple template management plugin","3":"MRU-like simple template management plugin","description":"see latest version at http:\/\/github.com\/tyru\/vimtemplate.vim\/\r\nand if you know more about template syntax, see my template files in .vim at http:\/\/github.com\/tyru\/dotfiles\/\r\n\r\nMy .vimrc setting:\r\n  let g:vt_template_dir_path = expand(\"$HOME\/.vim\/template\")\r\n  let g:vt_command = \"\"\r\n  let g:vt_author = \"tyru\"\r\n  let g:vt_email = \"tyru.exe@gmail.com\"\r\n\r\n  let s:files_tmp = {\r\n      \\'cppsrc.cpp'    : \"cpp\",\r\n      \\'csharp.cs'     : \"cs\",\r\n      \\'csrc.c'        : \"c\",\r\n      \\'header.h'      : \"c\",\r\n      \\'hina.html'     : \"html\",\r\n      \\'javasrc.java'  : \"java\",\r\n      \\'perl.pl'       : \"perl\",\r\n      \\'perlmodule.pm' : \"perl\",\r\n      \\'python.py'     : \"python\",\r\n      \\'scala.scala'   : \"scala\",\r\n      \\'scheme.scm'    : \"scheme\",\r\n      \\'vimscript.vim' : \"vim\"\r\n  \\}\r\n  let g:vt_filetype_files = join(map(keys(s:files_tmp), 'v:val . \"=\" . s:files_tmp[v:val]'), ',')\r\n  unlet s:files_tmp\r\n\r\nUsage:\r\n  COMMANDS:\r\n      VimTemplate\r\n          open template files list.\r\n\r\n  MAPPING:\r\n      gt\r\n          open template files list.\r\n\r\n  GLOBAL VARIABLES:\r\n      g:vt_template_dir_path (default:\"$HOME\/.vim\/template\")\r\n          search files in this dir.\r\n          to specify multi-dirs, set paths joined with \",\".\r\n\r\n      g:vt_command (default:\"VimTemplate\")\r\n          command name.\r\n          if this is empty string, won't define the command.\r\n\r\n      g:vt_mapping (default:\"gt\")\r\n          mapping.\r\n          if this is empty string, won't define the mapping.\r\n\r\n      g:vt_list_buf_height (default:7)\r\n          height of list buffer.\r\n          buffer shows you list of template files.\r\n\r\n      g:vt_filetype_files (default: \"\")\r\n          when you load one of these files or exec :setlocal ft=<filetype>.\r\n          search these files in your g:vt_template_dir_path.\r\n          e.g.: \"java_template.java=java,cpp_template.cpp=cpp\"\r\n\r\n      g:vt_author\r\n          expand <%author%> to this value.\r\n\r\n      g:vt_email\r\n          expand <%email%> to this value.\r\n\r\n  TEMPLATE SYNTAX:\r\n      please open the list buffer\r\n      after naming current buffer by\r\n\r\n      :e[dit] filename\r\n      or\r\n      :f[ile] filename\r\n\r\n      if you didn't, this script uses template file path.\r\n      and you don't have to delete whitespace in <%%>.\r\n      this plugin also allows both <%filename%> and <% filename %>.\r\n\r\n\r\n      <%eval:code%>\r\n          will expand into result value of code.\r\n\r\n      <%path%>\r\n          will expand into current path.\r\n          same as <%eval:expand('%')%>.\r\n\r\n      <%filename%>\r\n          will expand into current file name.\r\n          same as <%eval:expand('%:t')%>.\r\n\r\n      <%filename_noext%>\r\n          will expand into current file name without extension.\r\n          same as <%eval:expand('%:t:r')%>.\r\n\r\n      <%filename_ext%>\r\n          will expand into current filename's extension.\r\n          same as <%eval:expand('%:e')%>.\r\n\r\n      <%filename_camel%>\r\n        will expand into camel case of expand('%:t:r').\r\n        so extension is not added to result.\r\n\r\n        e.g.:\r\n            foo-bar.baz => FooBar\r\n            foo_bar.baz => FooBar\r\n\r\n      <%filename_snake%>\r\n        will expand into snake case of expand('%:t:r').\r\n        so extension is not added to result.\r\n\r\n        e.g.: FooBar.baz => foo_bar\r\n\r\n      <%parent_dir%>\r\n          will expand into current file's dir.\r\n          same as <%eval:expand('%:p:h')%>.\r\n\r\n      <%author%>\r\n          same as <% eval: g:vt_author %>.\r\n\r\n      <%email%>\r\n          same as <% eval: g:vt_email %>.\r\n\r\n","4":"see latest version at http:\/\/github.com\/tyru\/vimtemplate.vim\/\r\nand if you know more about template syntax, see my template files in .vim at http:\/\/github.com\/tyru\/dotfiles\/\r\n\r\nMy .vimrc setting:\r\n  let g:vt_template_dir_path = expand(\"$HOME\/.vim\/template\")\r\n  let g:vt_command = \"\"\r\n  let g:vt_author = \"tyru\"\r\n  let g:vt_email = \"tyru.exe@gmail.com\"\r\n\r\n  let s:files_tmp = {\r\n      \\'cppsrc.cpp'    : \"cpp\",\r\n      \\'csharp.cs'     : \"cs\",\r\n      \\'csrc.c'        : \"c\",\r\n      \\'header.h'      : \"c\",\r\n      \\'hina.html'     : \"html\",\r\n      \\'javasrc.java'  : \"java\",\r\n      \\'perl.pl'       : \"perl\",\r\n      \\'perlmodule.pm' : \"perl\",\r\n      \\'python.py'     : \"python\",\r\n      \\'scala.scala'   : \"scala\",\r\n      \\'scheme.scm'    : \"scheme\",\r\n      \\'vimscript.vim' : \"vim\"\r\n  \\}\r\n  let g:vt_filetype_files = join(map(keys(s:files_tmp), 'v:val . \"=\" . s:files_tmp[v:val]'), ',')\r\n  unlet s:files_tmp\r\n\r\nUsage:\r\n  COMMANDS:\r\n      VimTemplate\r\n          open template files list.\r\n\r\n  MAPPING:\r\n      gt\r\n          open template files list.\r\n\r\n  GLOBAL VARIABLES:\r\n      g:vt_template_dir_path (default:\"$HOME\/.vim\/template\")\r\n          search files in this dir.\r\n          to specify multi-dirs, set paths joined with \",\".\r\n\r\n      g:vt_command (default:\"VimTemplate\")\r\n          command name.\r\n          if this is empty string, won't define the command.\r\n\r\n      g:vt_mapping (default:\"gt\")\r\n          mapping.\r\n          if this is empty string, won't define the mapping.\r\n\r\n      g:vt_list_buf_height (default:7)\r\n          height of list buffer.\r\n          buffer shows you list of template files.\r\n\r\n      g:vt_filetype_files (default: \"\")\r\n          when you load one of these files or exec :setlocal ft=<filetype>.\r\n          search these files in your g:vt_template_dir_path.\r\n          e.g.: \"java_template.java=java,cpp_template.cpp=cpp\"\r\n\r\n      g:vt_author\r\n          expand <%author%> to this value.\r\n\r\n      g:vt_email\r\n          expand <%email%> to this value.\r\n\r\n  TEMPLATE SYNTAX:\r\n      please open the list buffer\r\n      after naming current buffer by\r\n\r\n      :e[dit] filename\r\n      or\r\n      :f[ile] filename\r\n\r\n      if you didn't, this script uses template file path.\r\n      and you don't have to delete whitespace in <%%>.\r\n      this plugin also allows both <%filename%> and <% filename %>.\r\n\r\n\r\n      <%eval:code%>\r\n          will expand into result value of code.\r\n\r\n      <%path%>\r\n          will expand into current path.\r\n          same as <%eval:expand('%')%>.\r\n\r\n      <%filename%>\r\n          will expand into current file name.\r\n          same as <%eval:expand('%:t')%>.\r\n\r\n      <%filename_noext%>\r\n          will expand into current file name without extension.\r\n          same as <%eval:expand('%:t:r')%>.\r\n\r\n      <%filename_ext%>\r\n          will expand into current filename's extension.\r\n          same as <%eval:expand('%:e')%>.\r\n\r\n      <%filename_camel%>\r\n        will expand into camel case of expand('%:t:r').\r\n        so extension is not added to result.\r\n\r\n        e.g.:\r\n            foo-bar.baz => FooBar\r\n            foo_bar.baz => FooBar\r\n\r\n      <%filename_snake%>\r\n        will expand into snake case of expand('%:t:r').\r\n        so extension is not added to result.\r\n\r\n        e.g.: FooBar.baz => foo_bar\r\n\r\n      <%parent_dir%>\r\n          will expand into current file's dir.\r\n          same as <%eval:expand('%:p:h')%>.\r\n\r\n      <%author%>\r\n          same as <% eval: g:vt_author %>.\r\n\r\n      <%email%>\r\n          same as <% eval: g:vt_email %>.\r\n\r\n","install_details":"move into your plugin folder.","5":"move into your plugin folder.","first_name":"tyru","6":"tyru","last_name":" ","7":" ","releases":[{"0":"2615","vim_version":"6.0","1":"6.0","script_version":"0.0.6","2":"0.0.6","version_comment":"\r\n- fix bugs:\r\n    - did not ignore whitespaces in <% ... %>\r\n    - if filename is 'FooBar.baz',\r\n      <%filename_snake%> was expanded to '_foo_bar'.\r\n      now is expanded to 'foo_bar'.\r\n- more speed optimization\r\n- <%filename_camel%> now supports '-' and '_' in filename\r\n- implement <%filename_ext%> as template syntax\r\n","3":"\r\n- fix bugs:\r\n    - did not ignore whitespaces in <% ... %>\r\n    - if filename is 'FooBar.baz',\r\n      <%filename_snake%> was expanded to '_foo_bar'.\r\n      now is expanded to 'foo_bar'.\r\n- more speed optimization\r\n- <%filename_camel%> now supports '-' and '_' in filename\r\n- implement <%filename_ext%> as template syntax\r\n","package":"vimtemplate.vim","4":"vimtemplate.vim","src_id":"11368","5":"11368","creation_date":"1252837201","6":"1252837201"},{"0":"2615","vim_version":"6.0","1":"6.0","script_version":"0.0.5","2":"0.0.5","version_comment":"speed optimization and fix bugs.","3":"speed optimization and fix bugs.","package":"vimtemplate.vim","4":"vimtemplate.vim","src_id":"11357","5":"11357","creation_date":"1252648408","6":"1252648408"},{"0":"2615","vim_version":"6.0","1":"6.0","script_version":"0.0.4","2":"0.0.4","version_comment":"0.0.4: delete g:vt_files_using_template. and support modeline in template file.\r\n","3":"0.0.4: delete g:vt_files_using_template. and support modeline in template file.\r\n","package":"vimtemplate.vim","4":"vimtemplate.vim","src_id":"10708","5":"10708","creation_date":"1243770415","6":"1243770415"},{"0":"2615","vim_version":"6.0","1":"6.0","script_version":"0.0.3","2":"0.0.3","version_comment":"add <%author%>, <%email%>, <%filename_camel%>, <%filename_snake%>","3":"add <%author%>, <%email%>, <%filename_camel%>, <%filename_snake%>","package":"vimtemplate.vim","4":"vimtemplate.vim","src_id":"10707","5":"10707","creation_date":"1243766470","6":"1243766470"},{"0":"2615","vim_version":"6.0","1":"6.0","script_version":"0.0.2","2":"0.0.2","version_comment":"fix bug that vimtemplate won't inline\r\nand delete g:vt_support_command and g:vt_support_mapping.\r\nnot to define\/map command\/mapping.\r\nlet g:vt_command\/g:vt_mapping be empty.\r\n\r\n","3":"fix bug that vimtemplate won't inline\r\nand delete g:vt_support_command and g:vt_support_mapping.\r\nnot to define\/map command\/mapping.\r\nlet g:vt_command\/g:vt_mapping be empty.\r\n\r\n","package":"vimtemplate.vim","4":"vimtemplate.vim","src_id":"10693","5":"10693","creation_date":"1243506935","6":"1243506935"},{"0":"2615","vim_version":"6.0","1":"6.0","script_version":"0.0.1","2":"0.0.1","version_comment":"implement g:vt_files_using_template and its template syntax.\r\n","3":"implement g:vt_files_using_template and its template syntax.\r\n","package":"vimtemplate.vim","4":"vimtemplate.vim","src_id":"10442","5":"10442","creation_date":"1240504435","6":"1240504435"},{"0":"2615","vim_version":"6.0","1":"6.0","script_version":"0.0.0","2":"0.0.0","version_comment":"Initial upload","3":"Initial upload","package":"vimtemplate.vim","4":"vimtemplate.vim","src_id":"10431","5":"10431","creation_date":"1240328660","6":"1240328660"}]},"2614":{"script_id":"2614","0":"2614","script_name":"sdticket","1":"sdticket","script_type":"syntax","2":"syntax","summary":"syntax support of sd (p2p bug tracking system)","3":"syntax support of sd (p2p bug tracking system)","description":"this supports sd (peer-to-peer bug tracking system) ticket syntax.\r\n\r\nhttp:\/\/syncwith.us\/ \r\nhttp:\/\/github.com\/obra\/sd","4":"this supports sd (peer-to-peer bug tracking system) ticket syntax.\r\n\r\nhttp:\/\/syncwith.us\/ \r\nhttp:\/\/github.com\/obra\/sd","install_details":"put the sdticket.vim to ~\/.vim\/syntax\/\r\n\r\nand add the below settings to your .vimrc\r\n\r\n au BufNewFile,BufRead *\r\n     \\ if getline(1) =~ \"required ticket metadata\" |\r\n     \\   setf sdticket |\r\n     \\ endif\r\n","5":"put the sdticket.vim to ~\/.vim\/syntax\/\r\n\r\nand add the below settings to your .vimrc\r\n\r\n au BufNewFile,BufRead *\r\n     \\ if getline(1) =~ \"required ticket metadata\" |\r\n     \\   setf sdticket |\r\n     \\ endif\r\n","first_name":"Yo-An","6":"Yo-An","last_name":"Lin","7":"Lin","releases":[{"0":"2614","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"sdticket.vim","4":"sdticket.vim","src_id":"10430","5":"10430","creation_date":"1240327954","6":"1240327954"}]},"2613":{"script_id":"2613","0":"2613","script_name":"vimstall","1":"vimstall","script_type":"utility","2":"utility","summary":"vimstall is a shell script to install vim plugins from vim.org automatically","3":"vimstall is a shell script to install vim plugins from vim.org automatically","description":"Vimstall is a script to install vim plugins automatically.\r\n\r\nSyntax:\r\n\tvimstall.sh <filename>|<dirname>\r\n\r\nIf you run the script on filename it is treated as vim plugin, if run on directory\r\nit will try to install all files from this directory like they all are vim plugins.\r\n\r\nVimstall supports vimballs (vim is run to install them), simple vim files\r\n(they are treated as sinlge plugin and are copied into ~\/.vim\/plugin\/ directory\r\nand packed files (zips & tarballs) in which case archive must contain either\r\nvim\/vimball file or packed installation of a plugin (i.e. directories to put into\r\n~\/.vim like `doc', `plugin', `autoload' etc.)\r\n\r\nIf during installation process the script runs into some unknown file, it will\r\nreport this file's name into stderr.\r\n\r\nThis script can be used with `downloadvimscripts' script to update & install\r\nvim plugins automatically.\r\n\r\nPlease note: this script is *beta* and not well tested in all configurations.\r\nI tried to handle most package types met on vim.org, so it should work fine\r\nmost of time (and it works for me :), but it is strongly advised to backup\r\nyour ~\/.vim directory before you run this script.\r\n\r\nBest used with downloadvimscripts (http:\/\/www.vim.org\/scripts\/script.php?script_id=2444).\r\n","4":"Vimstall is a script to install vim plugins automatically.\r\n\r\nSyntax:\r\n\tvimstall.sh <filename>|<dirname>\r\n\r\nIf you run the script on filename it is treated as vim plugin, if run on directory\r\nit will try to install all files from this directory like they all are vim plugins.\r\n\r\nVimstall supports vimballs (vim is run to install them), simple vim files\r\n(they are treated as sinlge plugin and are copied into ~\/.vim\/plugin\/ directory\r\nand packed files (zips & tarballs) in which case archive must contain either\r\nvim\/vimball file or packed installation of a plugin (i.e. directories to put into\r\n~\/.vim like `doc', `plugin', `autoload' etc.)\r\n\r\nIf during installation process the script runs into some unknown file, it will\r\nreport this file's name into stderr.\r\n\r\nThis script can be used with `downloadvimscripts' script to update & install\r\nvim plugins automatically.\r\n\r\nPlease note: this script is *beta* and not well tested in all configurations.\r\nI tried to handle most package types met on vim.org, so it should work fine\r\nmost of time (and it works for me :), but it is strongly advised to backup\r\nyour ~\/.vim directory before you run this script.\r\n\r\nBest used with downloadvimscripts (http:\/\/www.vim.org\/scripts\/script.php?script_id=2444).\r\n","install_details":"Put this script in any directory you like (I keep it in ~\/.vim\/scripts\/)\r\nand make it executable (chmod a+x vimstall.sh) and you are ready!\r\n\r\nYou may wish to make backup copy of your ~\/.vim before first usage\r\n(see notes above). To use it on a bunch of just downloaded vim plugins\r\nyou can do following (I consider you put downloaded scripts into\r\n~\/.vim\/update\/ and keep vimstall.sh in ~\/.vim\/scripts\/, if not, adjust\r\ncommands according your case):\r\n\r\n$ cd ~\/.vim\/update\/\r\n$ ..\/scripts\/vimstall.sh .\r\n\r\nWait a little and check if all plugins are installed\/updated.\r\nIf vimstall.sh meet some files he don't know how to handle, it will (or at\r\nleast should) cry about it into stderr.\r\n\r\nIf anything went wrong, email me at kstep<at>p-nut<dot>info,\r\nwith detailed bug description and a way to reproduce it.\r\nI'll be happy to fix it.\r\n","5":"Put this script in any directory you like (I keep it in ~\/.vim\/scripts\/)\r\nand make it executable (chmod a+x vimstall.sh) and you are ready!\r\n\r\nYou may wish to make backup copy of your ~\/.vim before first usage\r\n(see notes above). To use it on a bunch of just downloaded vim plugins\r\nyou can do following (I consider you put downloaded scripts into\r\n~\/.vim\/update\/ and keep vimstall.sh in ~\/.vim\/scripts\/, if not, adjust\r\ncommands according your case):\r\n\r\n$ cd ~\/.vim\/update\/\r\n$ ..\/scripts\/vimstall.sh .\r\n\r\nWait a little and check if all plugins are installed\/updated.\r\nIf vimstall.sh meet some files he don't know how to handle, it will (or at\r\nleast should) cry about it into stderr.\r\n\r\nIf anything went wrong, email me at kstep<at>p-nut<dot>info,\r\nwith detailed bug description and a way to reproduce it.\r\nI'll be happy to fix it.\r\n","first_name":"Konstantin","6":"Konstantin","last_name":"Stepanov","7":"Stepanov","releases":[{"0":"2613","vim_version":"6.0","1":"6.0","script_version":"1.0beta","2":"1.0beta","version_comment":"Initial upload","3":"Initial upload","package":"vimstall.sh","4":"vimstall.sh","src_id":"10422","5":"10422","creation_date":"1240179985","6":"1240179985"}]},"2612":{"script_id":"2612","0":"2612","script_name":"Rubytest.vim","1":"Rubytest.vim","script_type":"utility","2":"utility","summary":"Run ruby tests in vim","3":"Run ruby tests in vim","description":"Rubytest.vim will help you to run ruby test (including vanilla test, rspec, shoulda etc.) in vim.\r\n\r\nInstallation\r\n------------\r\n\r\nUnzip downloaded file and copy rubytest.vim to your ~\/.vim\/plugin directory.\r\n\r\nUsage\r\n-----\r\n\r\nAfter installation, press <Leader>t will run the test under your cursor if you are editing a ruby test file.\r\n\r\nexample:\r\n\r\n$ cd <your rails\/merb root>\r\n$ vim test\/unit\/user_test.rb\r\n(move cursor into a test case, press <Leader>t)\r\n\r\n(<Leader> is mapping to '\\\\' by default in vim)\r\n\r\nBe default, the plugin will print output in terminal. You can change this behavior by putting this line in your vimrc file:\r\n\r\n  let g:rubytest_in_quickfix = 1\r\n\r\nWith this set, test errors will be displayed in quickfix window, and you can jump to the error location quickly by select the error message and hit return (or 'Ctrl-w return' to open it in new window).\r\n\r\nYou can customize the command which will be used to run the test case by settting these options in your vimrc file:\r\n\r\n  let g:rubytest_cmd_test = \"ruby %p\"\r\n  let g:rubytest_cmd_testcase = \"ruby %p -n '\/%c\/'\"\r\n  let g:rubytest_cmd_spec = \"spec -f specdoc %p\"\r\n  let g:rubytest_cmd_example = \"spec -f specdoc %p -e '%c'\"\r\n  let g:rubytest_cmd_feature = \"cucumber %p\"\r\n  let g:rubytest_cmd_story = \"cucumber %p -n '%c'\"\r\n\r\n(%p will be replaced by the path of test file, %c will be replaced by the name of test case under cursor)\r\n\r\nDefault Key Bindings\r\n--------------------\r\n\r\n<Leader>t: run test case under cursor\r\n<Leader>T: run all tests in file\r\n<Leader>l: run the last test, from any buffer\r\n\r\nYou can change default key bindings:\r\n\r\n  map <Leader>\\ <Plug>RubyTestRun \" change from <Leader>t to <Leader>\\\r\n  map <Leader>] <Plug>RubyFileRun \" change from <Leader>T to <Leader>]\r\n  map <Leader>\/ <Plug>RubyTestRunLast \" change from <Leader>l to <Leader>\/\r\n\r\nThe latest code is hosted on http:\/\/github.com\/janx\/vim-rubytest\/tree\/master\r\n\r\nTip\r\n----\r\n\r\n* rubytest.vim works perfectly with vim-localvimrc, which enables you to set different test run command for different projects. Check details at: https:\/\/github.com\/embear\/vim-localvimrc","4":"Rubytest.vim will help you to run ruby test (including vanilla test, rspec, shoulda etc.) in vim.\r\n\r\nInstallation\r\n------------\r\n\r\nUnzip downloaded file and copy rubytest.vim to your ~\/.vim\/plugin directory.\r\n\r\nUsage\r\n-----\r\n\r\nAfter installation, press <Leader>t will run the test under your cursor if you are editing a ruby test file.\r\n\r\nexample:\r\n\r\n$ cd <your rails\/merb root>\r\n$ vim test\/unit\/user_test.rb\r\n(move cursor into a test case, press <Leader>t)\r\n\r\n(<Leader> is mapping to '\\\\' by default in vim)\r\n\r\nBe default, the plugin will print output in terminal. You can change this behavior by putting this line in your vimrc file:\r\n\r\n  let g:rubytest_in_quickfix = 1\r\n\r\nWith this set, test errors will be displayed in quickfix window, and you can jump to the error location quickly by select the error message and hit return (or 'Ctrl-w return' to open it in new window).\r\n\r\nYou can customize the command which will be used to run the test case by settting these options in your vimrc file:\r\n\r\n  let g:rubytest_cmd_test = \"ruby %p\"\r\n  let g:rubytest_cmd_testcase = \"ruby %p -n '\/%c\/'\"\r\n  let g:rubytest_cmd_spec = \"spec -f specdoc %p\"\r\n  let g:rubytest_cmd_example = \"spec -f specdoc %p -e '%c'\"\r\n  let g:rubytest_cmd_feature = \"cucumber %p\"\r\n  let g:rubytest_cmd_story = \"cucumber %p -n '%c'\"\r\n\r\n(%p will be replaced by the path of test file, %c will be replaced by the name of test case under cursor)\r\n\r\nDefault Key Bindings\r\n--------------------\r\n\r\n<Leader>t: run test case under cursor\r\n<Leader>T: run all tests in file\r\n<Leader>l: run the last test, from any buffer\r\n\r\nYou can change default key bindings:\r\n\r\n  map <Leader>\\ <Plug>RubyTestRun \" change from <Leader>t to <Leader>\\\r\n  map <Leader>] <Plug>RubyFileRun \" change from <Leader>T to <Leader>]\r\n  map <Leader>\/ <Plug>RubyTestRunLast \" change from <Leader>l to <Leader>\/\r\n\r\nThe latest code is hosted on http:\/\/github.com\/janx\/vim-rubytest\/tree\/master\r\n\r\nTip\r\n----\r\n\r\n* rubytest.vim works perfectly with vim-localvimrc, which enables you to set different test run command for different projects. Check details at: https:\/\/github.com\/embear\/vim-localvimrc","install_details":"Unzip downloaded file and copy rubytest.vim to your ~\/.vim\/plugin directory.","5":"Unzip downloaded file and copy rubytest.vim to your ~\/.vim\/plugin directory.","first_name":"jan","6":"jan","last_name":" ","7":" ","releases":[{"0":"2612","vim_version":"7.0","1":"7.0","script_version":"1.3.0","2":"1.3.0","version_comment":"* add new placeholder %s\r\n* update for MiniTest\r\n* better quickfix mode\r\n* default to use new rspec command line","3":"* add new placeholder %s\r\n* update for MiniTest\r\n* better quickfix mode\r\n* default to use new rspec command line","package":"rubytest.tar.bz2","4":"rubytest.tar.bz2","src_id":"23899","5":"23899","creation_date":"1452734433","6":"1452734433"},{"0":"2612","vim_version":"7.0","1":"7.0","script_version":"1.2.1","2":"1.2.1","version_comment":"* Use exact case match for minitest\r\n* support for capybara steak-like dsl (feature\/scenario)","3":"* Use exact case match for minitest\r\n* support for capybara steak-like dsl (feature\/scenario)","package":"rubytest.tar.bz2","4":"rubytest.tar.bz2","src_id":"19670","5":"19670","creation_date":"1363834835","6":"1363834835"},{"0":"2612","vim_version":"7.0","1":"7.0","script_version":"1.2.0","2":"1.2.0","version_comment":"* Add Scenario Outline keyword to test cases (Ben Simpson)\r\n* Run minitest in RSpec-like DSL (alexbel)\r\n* Escape pound symbol in test name\r\n* Global substitution for %c and %p in customized command (Ivan Tkalin)","3":"* Add Scenario Outline keyword to test cases (Ben Simpson)\r\n* Run minitest in RSpec-like DSL (alexbel)\r\n* Escape pound symbol in test name\r\n* Global substitution for %c and %p in customized command (Ivan Tkalin)","package":"rubytest.tar.bz2","4":"rubytest.tar.bz2","src_id":"19592","5":"19592","creation_date":"1362446648","6":"1362446648"},{"0":"2612","vim_version":"7.0","1":"7.0","script_version":"1.1.0","2":"1.1.0","version_comment":"* Remember last run: <Leader>l to run last run test\r\n* Default support to rspec2. You need to customize g:rubytest_cmd_spec to work with rspec 1.*","3":"* Remember last run: <Leader>l to run last run test\r\n* Default support to rspec2. You need to customize g:rubytest_cmd_spec to work with rspec 1.*","package":"rubytest.tar.bz2","4":"rubytest.tar.bz2","src_id":"15911","5":"15911","creation_date":"1308300272","6":"1308300272"},{"0":"2612","vim_version":"7.0","1":"7.0","script_version":"1.0.2","2":"1.0.2","version_comment":"fix testunit result display in quickfix; Added describe|context patterns so we can run examples under a grouping of describe or context.","3":"fix testunit result display in quickfix; Added describe|context patterns so we can run examples under a grouping of describe or context.","package":"rubytest.tar.bz2","4":"rubytest.tar.bz2","src_id":"13145","5":"13145","creation_date":"1275991987","6":"1275991987"},{"0":"2612","vim_version":"7.0","1":"7.0","script_version":"1.0.1","2":"1.0.1","version_comment":"show full result by default","3":"show full result by default","package":"rubytest.tar.bz2","4":"rubytest.tar.bz2","src_id":"12735","5":"12735","creation_date":"1269865098","6":"1269865098"},{"0":"2612","vim_version":"7.0","1":"7.0","script_version":"1.0.0","2":"1.0.0","version_comment":"There's many changes in this new release:\r\n* Support cucumber features\r\n* Support rspec drb mode\r\n* fix serveral bugs","3":"There's many changes in this new release:\r\n* Support cucumber features\r\n* Support rspec drb mode\r\n* fix serveral bugs","package":"rubytest.tar.bz2","4":"rubytest.tar.bz2","src_id":"12596","5":"12596","creation_date":"1268282904","6":"1268282904"},{"0":"2612","vim_version":"7.0","1":"7.0","script_version":"0.9.7","2":"0.9.7","version_comment":"fixed escape bug on windows. (bogdan)","3":"fixed escape bug on windows. (bogdan)","package":"rubytest.tar.bz2","4":"rubytest.tar.bz2","src_id":"11409","5":"11409","creation_date":"1253371947","6":"1253371947"},{"0":"2612","vim_version":"7.0","1":"7.0","script_version":"0.9.6","2":"0.9.6","version_comment":"improved support for rspec","3":"improved support for rspec","package":"rubytest.tar.bz2","4":"rubytest.tar.bz2","src_id":"10830","5":"10830","creation_date":"1245057866","6":"1245057866"},{"0":"2612","vim_version":"7.0","1":"7.0","script_version":"0.9.5","2":"0.9.5","version_comment":"add quickfix support","3":"add quickfix support","package":"rubytest.tar.bz2","4":"rubytest.tar.bz2","src_id":"10585","5":"10585","creation_date":"1242186425","6":"1242186425"},{"0":"2612","vim_version":"7.0","1":"7.0","script_version":"0.9.1","2":"0.9.1","version_comment":"fix test case finder","3":"fix test case finder","package":"rubytest.tar.bz2","4":"rubytest.tar.bz2","src_id":"10462","5":"10462","creation_date":"1240842498","6":"1240842498"},{"0":"2612","vim_version":"7.0","1":"7.0","script_version":"0.9.0","2":"0.9.0","version_comment":"Initial upload","3":"Initial upload","package":"rubytest.tar.bz2","4":"rubytest.tar.bz2","src_id":"10418","5":"10418","creation_date":"1240133216","6":"1240133216"}]},"2611":{"script_id":"2611","0":"2611","script_name":"xptemplate","1":"xptemplate","script_type":"utility","2":"utility","summary":"XP's Snippet Template engine for vim","3":"XP's Snippet Template engine for vim","description":"Code snippets engine for Vim, with snippets library.\r\nXPTemplate let you write codes in a smooth, quick and comfortable way.\r\n\r\n=======================   Usage   =======================\r\n\r\nvim xpt.c\r\n\/\/ Type  \"for<C-\\>\" :\r\nfor (i = 0; i < len; ++i) {\r\n   \/* cursor *\/\r\n}\r\nPress <tab>,<tab>.. to navigate through \"i\", \"0\", \"len\". Cursor will finally stops at \"\/* cursor *\/\".\r\n\r\n\r\n=======================   Features   =======================\r\n\r\n* Live update while typing\r\n* Navigate forward and backward. <Tab> and <S-Tab>\r\n* Embed language support like JAVASCRIPT in HTML. Or HTML in PHP\r\n* Wrapper\r\n* Smart indent\r\n* Spacing and line-break of snippet can be easily changed to fit your coding style\r\n* Pop up menu friendly\r\n\r\n\r\n=======================   Resources   =======================\r\n\r\nScreencast : 0.3.9 :  http:\/\/code.google.com\/p\/xptemplate\/wiki\/ScreenCasts;\r\n\r\nGet From GIT: git:\/\/github.com\/drmingdrmer\/xptemplate.git;\r\nProject Home : https:\/\/github.com\/drmingdrmer\/xptemplate;\r\nFollow me: http:\/\/twitter.com\/xptemplate;\r\n\r\n*** Troubleshoot \/ supertab support \/ bracket complete \/ other question ***\r\nhttps:\/\/github.com\/drmingdrmer\/xptemplate#faq\r\n\r\n\r\n=======================   Compatibilities   =======================\r\n\r\nSupported platform:  Linux, WinXP, \/\/ [g]vim 7.2\r\nSupported Language:  ada c cabal cpp cs css dot erlang gitconfig gnuplot haskell html java javascript lex lua make ocaml perl php ps1 python r ruby(eruby) scheme sh tcl tex vim xml xpt xslt yacc\r\n\r\n**Bundles: c_autoimplem cpp_autoimplem javascript_jquery\r\n\r\n\r\nSpecial Thanks to ^0^ : \r\nChristian.Coutinho  Vincent Berthoux  Fabio  Simon Ruderich","4":"Code snippets engine for Vim, with snippets library.\r\nXPTemplate let you write codes in a smooth, quick and comfortable way.\r\n\r\n=======================   Usage   =======================\r\n\r\nvim xpt.c\r\n\/\/ Type  \"for<C-\\>\" :\r\nfor (i = 0; i < len; ++i) {\r\n   \/* cursor *\/\r\n}\r\nPress <tab>,<tab>.. to navigate through \"i\", \"0\", \"len\". Cursor will finally stops at \"\/* cursor *\/\".\r\n\r\n\r\n=======================   Features   =======================\r\n\r\n* Live update while typing\r\n* Navigate forward and backward. <Tab> and <S-Tab>\r\n* Embed language support like JAVASCRIPT in HTML. Or HTML in PHP\r\n* Wrapper\r\n* Smart indent\r\n* Spacing and line-break of snippet can be easily changed to fit your coding style\r\n* Pop up menu friendly\r\n\r\n\r\n=======================   Resources   =======================\r\n\r\nScreencast : 0.3.9 :  http:\/\/code.google.com\/p\/xptemplate\/wiki\/ScreenCasts;\r\n\r\nGet From GIT: git:\/\/github.com\/drmingdrmer\/xptemplate.git;\r\nProject Home : https:\/\/github.com\/drmingdrmer\/xptemplate;\r\nFollow me: http:\/\/twitter.com\/xptemplate;\r\n\r\n*** Troubleshoot \/ supertab support \/ bracket complete \/ other question ***\r\nhttps:\/\/github.com\/drmingdrmer\/xptemplate#faq\r\n\r\n\r\n=======================   Compatibilities   =======================\r\n\r\nSupported platform:  Linux, WinXP, \/\/ [g]vim 7.2\r\nSupported Language:  ada c cabal cpp cs css dot erlang gitconfig gnuplot haskell html java javascript lex lua make ocaml perl php ps1 python r ruby(eruby) scheme sh tcl tex vim xml xpt xslt yacc\r\n\r\n**Bundles: c_autoimplem cpp_autoimplem javascript_jquery\r\n\r\n\r\nSpecial Thanks to ^0^ : \r\nChristian.Coutinho  Vincent Berthoux  Fabio  Simon Ruderich","install_details":"copy files(xpt\/*) into runtime path(.vim\/).\r\n:helptags path_to_xpt\/doc\r\n:help xpt\r\n\r\nAnd you need at least turn on these 2 settings in \".vimrc\" :\r\nset nocompatible\r\nfiletype plugin  on\r\n\r\n","5":"copy files(xpt\/*) into runtime path(.vim\/).\r\n:helptags path_to_xpt\/doc\r\n:help xpt\r\n\r\nAnd you need at least turn on these 2 settings in \".vimrc\" :\r\nset nocompatible\r\nfiletype plugin  on\r\n\r\n","first_name":"drdr","6":"drdr","last_name":"xp","7":"xp","releases":[{"0":"2611","vim_version":"7.2","1":"7.2","script_version":"0.4.8.1313","2":"0.4.8.1313","version_comment":"fix over strict filetype regexp. Thanks to Krzysztof","3":"fix over strict filetype regexp. Thanks to Krzysztof","package":"xpt-0.4.8.120113-ac4a53d.tgz","4":"xpt-0.4.8.120113-ac4a53d.tgz","src_id":"17190","5":"17190","creation_date":"1326390124","6":"1326390124"},{"0":"2611","vim_version":"7.2","1":"7.2","script_version":"0.4.8.1220","2":"0.4.8.1220","version_comment":"fix python::def snippet bug thanks to daethorian","3":"fix python::def snippet bug thanks to daethorian","package":"xpt-0.4.8.111220-4ec4b29.tgz","4":"xpt-0.4.8.111220-4ec4b29.tgz","src_id":"17090","5":"17090","creation_date":"1324317586","6":"1324317586"},{"0":"2611","vim_version":"7.2","1":"7.2","script_version":"0.4.8.0707","2":"0.4.8.0707","version_comment":"Fix cindent problem with indentkeys","3":"Fix cindent problem with indentkeys","package":"xpt-0.4.8.110707-5e60ef1.tgz","4":"xpt-0.4.8.110707-5e60ef1.tgz","src_id":"16050","5":"16050","creation_date":"1310046485","6":"1310046485"},{"0":"2611","vim_version":"7.2","1":"7.2","script_version":"0.4.8.0705","2":"0.4.8.0705","version_comment":"Fixed a lot bugs. Thanks to adshuangjoh@gmail.com and Kirill Klenov","3":"Fixed a lot bugs. Thanks to adshuangjoh@gmail.com and Kirill Klenov","package":"xpt-0.4.8.110705-eb168de.tgz","4":"xpt-0.4.8.110705-eb168de.tgz","src_id":"16034","5":"16034","creation_date":"1309882617","6":"1309882617"},{"0":"2611","vim_version":"7.2","1":"7.2","script_version":"0.4.8-1031","2":"0.4.8-1031","version_comment":"fix bug that with \"fo+=ta\" xpreplace messes up text. Reported by koelner.r","3":"fix bug that with \"fo+=ta\" xpreplace messes up text. Reported by koelner.r","package":"xpt-0.4.8-r1031.tgz","4":"xpt-0.4.8-r1031.tgz","src_id":"14395","5":"14395","creation_date":"1291052814","6":"1291052814"},{"0":"2611","vim_version":"7.2","1":"7.2","script_version":"0.4.8-r994","2":"0.4.8-r994","version_comment":"Fix: bug of converting space to tab","3":"Fix: bug of converting space to tab","package":"xpt-0.4.8-r994.tgz","4":"xpt-0.4.8-r994.tgz","src_id":"13740","5":"13740","creation_date":"1283360287","6":"1283360287"},{"0":"2611","vim_version":"7.2","1":"7.2","script_version":"0.4.8-r976","2":"0.4.8-r976","version_comment":"Fix: mistakingly using SPop as SParg in bracket completion. ","3":"Fix: mistakingly using SPop as SParg in bracket completion. ","package":"xpt-0.4.8-r976.tgz","4":"xpt-0.4.8-r976.tgz","src_id":"13728","5":"13728","creation_date":"1283178526","6":"1283178526"},{"0":"2611","vim_version":"7.2","1":"7.2","script_version":"0.4.8-r962","2":"0.4.8-r962","version_comment":"Fix: bracket following multi-bytes char breaks the previous char","3":"Fix: bracket following multi-bytes char breaks the previous char","package":"xpt-0.4.8-r962.tgz","4":"xpt-0.4.8-r962.tgz","src_id":"13698","5":"13698","creation_date":"1282928681","6":"1282928681"},{"0":"2611","vim_version":"7.2","1":"7.2","script_version":"0.4.8-r957","2":"0.4.8-r957","version_comment":"Fix bug that xpreplace sometimes removes chars if folding enabled.\r\n\r\nFix nav-key issue with selection set to be exclusive.\r\n","3":"Fix bug that xpreplace sometimes removes chars if folding enabled.\r\n\r\nFix nav-key issue with selection set to be exclusive.\r\n","package":"xpt-0.4.8-r957.tgz","4":"xpt-0.4.8-r957.tgz","src_id":"13681","5":"13681","creation_date":"1282828909","6":"1282828909"},{"0":"2611","vim_version":"7.0","1":"7.0","script_version":"0.4.8-r911","2":"0.4.8-r911","version_comment":"fix problem that pressing <Tab> with pum unclosed gets chars lost","3":"fix problem that pressing <Tab> with pum unclosed gets chars lost","package":"xpt-0.4.8-r911.tgz","4":"xpt-0.4.8-r911.tgz","src_id":"13402","5":"13402","creation_date":"1280048569","6":"1280048569"},{"0":"2611","vim_version":"7.0","1":"7.0","script_version":"0.4.8-r899","2":"0.4.8-r899","version_comment":"Fix: brace completion bug with pop up menu opened. Thanks to yeskky reporting this issue.\r\n\r\nAdd: 3 new filetypes : gitconfig, gnuplot, r. Simple and useful. Thanks to Vicent B","3":"Fix: brace completion bug with pop up menu opened. Thanks to yeskky reporting this issue.\r\n\r\nAdd: 3 new filetypes : gitconfig, gnuplot, r. Simple and useful. Thanks to Vicent B","package":"xpt-0.4.8-r899.tgz","4":"xpt-0.4.8-r899.tgz","src_id":"13312","5":"13312","creation_date":"1278773092","6":"1278773092"},{"0":"2611","vim_version":"7.0","1":"7.0","script_version":"0.4.8-r860","2":"0.4.8-r860","version_comment":"Fix some mistakes in doc. \r\nFix but with repetition started at the first char.\r\nFix <expr> mapping bug","3":"Fix some mistakes in doc. \r\nFix but with repetition started at the first char.\r\nFix <expr> mapping bug","package":"xpt-0.4.8-r860.tgz","4":"xpt-0.4.8-r860.tgz","src_id":"13051","5":"13051","creation_date":"1274722725","6":"1274722725"},{"0":"2611","vim_version":"7.0","1":"7.0","script_version":"0.4.8-r852","2":"0.4.8-r852","version_comment":"Add: autoimplemen bundle for c and cpp.\r\nFix: cross-line place holder is created incorrectly.\r\n\r\nPlenty Thanks to  Vincent B and Simon Ruderich.","3":"Add: autoimplemen bundle for c and cpp.\r\nFix: cross-line place holder is created incorrectly.\r\n\r\nPlenty Thanks to  Vincent B and Simon Ruderich.","package":"xpt-0.4.8-r852.tgz","4":"xpt-0.4.8-r852.tgz","src_id":"13045","5":"13045","creation_date":"1274624881","6":"1274624881"},{"0":"2611","vim_version":"7.0","1":"7.0","script_version":"0.4.8-r842","2":"0.4.8-r842","version_comment":"Fix: auto-indent bug","3":"Fix: auto-indent bug","package":"xpt-0.4.8-r842.tgz","4":"xpt-0.4.8-r842.tgz","src_id":"13018","5":"13018","creation_date":"1274066567","6":"1274066567"},{"0":"2611","vim_version":"7.0","1":"7.0","script_version":"0.4.7-r807","2":"0.4.7-r807","version_comment":"fix: improve non-word char snippet name support\r\nfix: when <tab> pressed to go to next, pum does not close and it swallows some chars\r\nfix: removes all XPTemplateDef command\r\nfix: supertab does not work well\r\nfix: pum bug mess text.\r\nfix: edges with quotes are wrongly evaluated.\r\n","3":"fix: improve non-word char snippet name support\r\nfix: when <tab> pressed to go to next, pum does not close and it swallows some chars\r\nfix: removes all XPTemplateDef command\r\nfix: supertab does not work well\r\nfix: pum bug mess text.\r\nfix: edges with quotes are wrongly evaluated.\r\n","package":"xpt-0.4.7.tgz","4":"xpt-0.4.7.tgz","src_id":"12910","5":"12910","creation_date":"1272438786","6":"1272438786"},{"0":"2611","vim_version":"7.0","1":"7.0","script_version":"0.3.9.98","2":"0.3.9.98","version_comment":"Fix : vim halts when XPT searching for keywords","3":"Fix : vim halts when XPT searching for keywords","package":"xpt-0.3.9.98.tgz","4":"xpt-0.3.9.98.tgz","src_id":"11899","5":"11899","creation_date":"1260786012","6":"1260786012"}]},"2610":{"script_id":"2610","0":"2610","script_name":"textobj-entire","1":"textobj-entire","script_type":"utility","2":"utility","summary":"Text objects for entire buffer","3":"Text objects for entire buffer","description":"*textobj-entire* is a Vim plugin to provide text objects to select the entire\r\ncontent of a buffer.\r\n\r\n\r\nRequirements:\r\n- Vim 7.2 or later\r\n- |textobj-user| 0.3.7 or later (vimscript#2100)\r\n\r\nLatest version:\r\nhttp:\/\/github.com\/kana\/vim-textobj-entire","4":"*textobj-entire* is a Vim plugin to provide text objects to select the entire\r\ncontent of a buffer.\r\n\r\n\r\nRequirements:\r\n- Vim 7.2 or later\r\n- |textobj-user| 0.3.7 or later (vimscript#2100)\r\n\r\nLatest version:\r\nhttp:\/\/github.com\/kana\/vim-textobj-entire","install_details":"...","5":"...","first_name":"Kana","6":"Kana","last_name":"Natsuno","7":"Natsuno","releases":[{"0":"2610","vim_version":"7.0","1":"7.0","script_version":"0.0.1","2":"0.0.1","version_comment":"- Fix a typo on the name of a variable.","3":"- Fix a typo on the name of a variable.","package":"vim-textobj-entire-0.0.1.zip","4":"vim-textobj-entire-0.0.1.zip","src_id":"11182","5":"11182","creation_date":"1250166272","6":"1250166272"},{"0":"2610","vim_version":"7.0","1":"7.0","script_version":"0.0.0","2":"0.0.0","version_comment":"Initial upload","3":"Initial upload","package":"vim-textobj-entire-0.0.0.zip","4":"vim-textobj-entire-0.0.0.zip","src_id":"10407","5":"10407","creation_date":"1239894609","6":"1239894609"}]},"2609":{"script_id":"2609","0":"2609","script_name":"PA_translator","1":"PA_translator","script_type":"utility","2":"utility","summary":"Plugin for easily translating single word or sentences without leaving your Vim","3":"Plugin for easily translating single word or sentences without leaving your Vim","description":"   So, you are working with any document in foreign language and some word is unknown to you. In normal mode, put cursor on this word and press ,tr (in previous versions: <A-Space>) buttons. The translation of the word will appear in command screan. If word can not be translated you will receive message: 'The `your_word` can not be translated'.\r\n   To translate range of the words (sentences), go to visual mode by pressing <Esc>,<v> buttons. Select desired text, for instance, by <Shift-V>, and after that press ,tr (in previous versions: <A-Space>).\r\n","4":"   So, you are working with any document in foreign language and some word is unknown to you. In normal mode, put cursor on this word and press ,tr (in previous versions: <A-Space>) buttons. The translation of the word will appear in command screan. If word can not be translated you will receive message: 'The `your_word` can not be translated'.\r\n   To translate range of the words (sentences), go to visual mode by pressing <Esc>,<v> buttons. Select desired text, for instance, by <Shift-V>, and after that press ,tr (in previous versions: <A-Space>).\r\n","install_details":"To install:\r\n  - Download the PA_translator.zip.\r\n  - Extract the zip archive into your runtime directory. The archive contains plugin\/PA_translator.vim, and doc\/PA_translator.txt.\r\n  - Start Vim or go to an existing instance of Vim.\r\n  - Execute the following command:\r\n\r\n      :helptag <your runtime directory\/doc\r\n\r\n    This will generate all the help tags for any file located in the doc directory.\r\n  - By default plugin translate from English into Ukrainian (it is my native language). You can change them by adding to your .vimrc:\r\n\r\n       let g:PA_translator_from_lang = 'your_from_language_code'\r\n       let g:PA_translator_to_lang = 'your_to_language_code'\r\n\r\n    Language codes are google translator API language codes.\r\n\r\n   This plugin is only available if 'compatible' is not set and vim has been compiled with RUBY language support.\r\n    It also requires access to network.\r\n","5":"To install:\r\n  - Download the PA_translator.zip.\r\n  - Extract the zip archive into your runtime directory. The archive contains plugin\/PA_translator.vim, and doc\/PA_translator.txt.\r\n  - Start Vim or go to an existing instance of Vim.\r\n  - Execute the following command:\r\n\r\n      :helptag <your runtime directory\/doc\r\n\r\n    This will generate all the help tags for any file located in the doc directory.\r\n  - By default plugin translate from English into Ukrainian (it is my native language). You can change them by adding to your .vimrc:\r\n\r\n       let g:PA_translator_from_lang = 'your_from_language_code'\r\n       let g:PA_translator_to_lang = 'your_to_language_code'\r\n\r\n    Language codes are google translator API language codes.\r\n\r\n   This plugin is only available if 'compatible' is not set and vim has been compiled with RUBY language support.\r\n    It also requires access to network.\r\n","first_name":"Andrij","6":"Andrij","last_name":"Pukalskyy","7":"Pukalskyy","releases":[{"0":"2609","vim_version":"7.0","1":"7.0","script_version":"0.0.4","2":"0.0.4","version_comment":"Fixing according to updated translate.google","3":"Fixing according to updated translate.google","package":"PA_translator.zip","4":"PA_translator.zip","src_id":"12685","5":"12685","creation_date":"1269362794","6":"1269362794"},{"0":"2609","vim_version":"7.0","1":"7.0","script_version":"0.0.3","2":"0.0.3","version_comment":"Bug fixing: \r\n1. IP host resolving fixed for linux\/freebsd OS;\r\n2. `^M` unix\/windows bug fixed;\r\n3. Default maps changed from <A-Space> to ,tr because many OS reserve such shortcuts;\r\n","3":"Bug fixing: \r\n1. IP host resolving fixed for linux\/freebsd OS;\r\n2. `^M` unix\/windows bug fixed;\r\n3. Default maps changed from <A-Space> to ,tr because many OS reserve such shortcuts;\r\n","package":"PA_translator.zip","4":"PA_translator.zip","src_id":"10941","5":"10941","creation_date":"1246717540","6":"1246717540"},{"0":"2609","vim_version":"7.0","1":"7.0","script_version":"0.0.2","2":"0.0.2","version_comment":"Bug fixing","3":"Bug fixing","package":"PA_translator.zip","4":"PA_translator.zip","src_id":"10891","5":"10891","creation_date":"1245861804","6":"1245861804"},{"0":"2609","vim_version":"7.0","1":"7.0","script_version":"0.0.1","2":"0.0.1","version_comment":"Initial upload","3":"Initial upload","package":"PA_translator.zip","4":"PA_translator.zip","src_id":"10406","5":"10406","creation_date":"1239864327","6":"1239864327"}]},"2608":{"script_id":"2608","0":"2608","script_name":"send.vim","1":"send.vim","script_type":"utility","2":"utility","summary":"Send current range to STDIN of arbitrary program","3":"Send current range to STDIN of arbitrary program","description":"Send the current range to the STDIN of an arbitrary command line program. Special support for sending text to an ipython interpreter running inside screen (via my send2screen.py script)\r\nhttp:\/\/users.physik.fu-berlin.de\/~goerz\/blog\/2008\/09\/integrating-vim-with-ipython\/","4":"Send the current range to the STDIN of an arbitrary command line program. Special support for sending text to an ipython interpreter running inside screen (via my send2screen.py script)\r\nhttp:\/\/users.physik.fu-berlin.de\/~goerz\/blog\/2008\/09\/integrating-vim-with-ipython\/","install_details":"Put the send.vim file into your ~\/.vim\/plugins folder. You need to have python compiled into vim in order for this plugin to work.\r\n\r\nYou probably also want to get my send2screen.py script:\r\nhttp:\/\/users.physik.fu-berlin.de\/~goerz\/blog\/2008\/09\/integrating-vim-with-ipython\/\r\n\r\nRead the comments in the send.vim file for documentation.\r\n\r\nChange settings in your vimrc:\r\n\r\nMap keys as you like (see example at the end of the send.vim file)\r\n\r\nSuggestion: enable ipython mode when you're in python files: add\r\n      let b:sendToProgramMode=\"ipython\"\r\nto your python.vim ftplugin, or add\r\n      autocmd BufNewFile,BufRead *.py let b:sendToProgramMode=\"ipython\"\r\nto your .vimrc\r\n","5":"Put the send.vim file into your ~\/.vim\/plugins folder. You need to have python compiled into vim in order for this plugin to work.\r\n\r\nYou probably also want to get my send2screen.py script:\r\nhttp:\/\/users.physik.fu-berlin.de\/~goerz\/blog\/2008\/09\/integrating-vim-with-ipython\/\r\n\r\nRead the comments in the send.vim file for documentation.\r\n\r\nChange settings in your vimrc:\r\n\r\nMap keys as you like (see example at the end of the send.vim file)\r\n\r\nSuggestion: enable ipython mode when you're in python files: add\r\n      let b:sendToProgramMode=\"ipython\"\r\nto your python.vim ftplugin, or add\r\n      autocmd BufNewFile,BufRead *.py let b:sendToProgramMode=\"ipython\"\r\nto your .vimrc\r\n","first_name":"Michael","6":"Michael","last_name":"Goerz","7":"Goerz","releases":[{"0":"2608","vim_version":"7.0","1":"7.0","script_version":"2.0","2":"2.0","version_comment":"Initial upload","3":"Initial upload","package":"send.vim","4":"send.vim","src_id":"10401","5":"10401","creation_date":"1239794420","6":"1239794420"}]},"2607":{"script_id":"2607","0":"2607","script_name":"TaskList.vim","1":"TaskList.vim","script_type":"utility","2":"utility","summary":"Eclipse like task list","3":"Eclipse like task list","description":"This script is based on the eclipse Task List. It will search the file for FIXME, TODO, and XXX (or a custom list) and put them in a handy list for you to browse which at the same time will update the location in the document so you can see exactly where the tag is located. Something like an interactive 'cw'\r\n\r\nCheck out this page for a screen shot of the script in action.\r\nhttp:\/\/juan.boxfi.com\/vim-plugins\/#tasklist","4":"This script is based on the eclipse Task List. It will search the file for FIXME, TODO, and XXX (or a custom list) and put them in a handy list for you to browse which at the same time will update the location in the document so you can see exactly where the tag is located. Something like an interactive 'cw'\r\n\r\nCheck out this page for a screen shot of the script in action.\r\nhttp:\/\/juan.boxfi.com\/vim-plugins\/#tasklist","install_details":"Drop into your plugin directory","5":"Drop into your plugin directory","first_name":"Juan","6":"Juan","last_name":"Frias","7":"Frias","releases":[{"0":"2607","vim_version":"7.0","1":"7.0","script_version":"1.0.1","2":"1.0.1","version_comment":"Minor message change.","3":"Minor message change.","package":"tasklist.vim","4":"tasklist.vim","src_id":"10388","5":"10388","creation_date":"1239518899","6":"1239518899"}]},"2606":{"script_id":"2606","0":"2606","script_name":"vimuiex","1":"vimuiex","script_type":"utility","2":"utility","summary":"Vim UI extensions: a pack of plugins that use an overlapping  popup list","3":"Vim UI extensions: a pack of plugins that use an overlapping  popup list","description":"Vim user interface extension\r\n\r\nrequires: VxLib (vimscript#3061)\r\n\r\nThe plugin implements a popup listbox (an overlapping window). The listbox can display an array of stirng items and can be navigated with the usual Vim keys. The list can be narrowed by interactively applying a filter.\r\n\r\nThe listbox is available in console when Vim is built with \"+python\" and the Python curses library is available. For GVim a patch that adds the feature \"+python_screen\" is required (see below).\r\n\r\nScreenshots: http:\/\/vimuiex.sourceforge.net\/screenshot\/tvimmenu.png.html \r\n\r\nThe commands defined by the plugin are listed below. When a popup listbox appears, you can pres F1 to display the list of keys\/commands that are active in the listbox. You can always close a listbox with Esc or q in default mode. The basic operation is described at:\r\nhttp:\/\/vimuiex.sourceforge.net\/vimdoc\/vimuiex.html#vimuiex-operation\r\n\r\nOpening files, selecting buffers:\r\n   * VxBufListSelect:\r\n     Buffer explorer\/manager.\r\n     http:\/\/vimuiex.sourceforge.net\/vimdoc\/vimuiex_plugins.html#vimuiex-vxbuflistselect;\r\n   * VxOpenRecentFile:\r\n     Display a list of recent files, open selected file.\r\n   * VxFileBrowser:\r\n     Browse the local filesystem to open some files.  Recent directory list is available to find files faster.\r\n   * VxFileFilter:\r\n     Display a list of files in current directory and subdirectories to a certain depth to open some files.\r\n\r\nFinding text:\r\n   * VxOccurRegex:\r\n     Display all occurences of a string in the listbox. The search range can be a buffer, a directory or a directory with its subdirectories. Uses vimgrep or external grep for directory searches.\r\n     http:\/\/vimuiex.sourceforge.net\/vimdoc\/vimuiex_plugins.html#vimuiex-vxoccur;\r\n   * VxOccurCurrent:\r\n     Capture output from [I and show it in the listbox.\r\n   * VxOccurTags:\r\n     Process current file with ctags, show results in the listbox.\r\n   * VxOccurRutines:\r\n     Display the lines that match a predefined regular expression for current filetype. Example implementations for: Vim, Python, D, LaTeX, BibTex, Html, Slice.\r\n   * VxSourceTasks:\r\n     Display TODO\/Task items in source files. The search range can be defined like with VxOccurRegex.\r\n   \r\n   Every command in this section stores its results in vxoccur history. A recent set of search results can be activated with :VxOccurSelectHist without running an expensive search command again.The commands :VxCPrev and :VxCNext select items while the list is closed. The command :VxOccurHist redisplays the active list.\r\n\r\n   A helper plugin VxMap enables a faster navigation through the list of results (and also the following: buffers, tabs, errorlist, locationlist).\r\n   http:\/\/vimuiex.sourceforge.net\/vimdoc\/vimuiex_plugins.html#vimuiex-vxmap;\r\n\r\nExtended builtin commands:\r\n   * VxTextMenu:\r\n     Display the Vim menu in the listbox, select items from menu.\r\n   * VxDisplay:\r\n     Display the output of :display, insert or execute selected register.\r\n   * VxMarks:\r\n     Display the output of :marks, jump to mark\r\n   * VxCmd:\r\n     Display the output of any command in a listbox\r\n   * The file vxcmdhist.vim:\r\n     Implements a function that displays the command line history in a listbox when PgUp is pressed\r\n\r\nMoving around:\r\n   Commands require \"+python_screen\" (download the patch below):\r\n   * VxLineJump:\r\n     Display lables in the line-number area and jump to selected label.\r\n   * VxWindowJump:\r\n     Display a label in the center of every window and jump to selected window.\r\n\r\nLinks:\r\n\r\nPatch and prebuilt binaries: http:\/\/sourceforge.net\/projects\/vimuiex\/files\/\r\nDetailed descriptions: http:\/\/vimuiex.sourceforge.net\/plugins.html\r\nExample keymap: http:\/\/vimuiex.sourceforge.net\/vimmapexmpl.html\r\n\r\n","4":"Vim user interface extension\r\n\r\nrequires: VxLib (vimscript#3061)\r\n\r\nThe plugin implements a popup listbox (an overlapping window). The listbox can display an array of stirng items and can be navigated with the usual Vim keys. The list can be narrowed by interactively applying a filter.\r\n\r\nThe listbox is available in console when Vim is built with \"+python\" and the Python curses library is available. For GVim a patch that adds the feature \"+python_screen\" is required (see below).\r\n\r\nScreenshots: http:\/\/vimuiex.sourceforge.net\/screenshot\/tvimmenu.png.html \r\n\r\nThe commands defined by the plugin are listed below. When a popup listbox appears, you can pres F1 to display the list of keys\/commands that are active in the listbox. You can always close a listbox with Esc or q in default mode. The basic operation is described at:\r\nhttp:\/\/vimuiex.sourceforge.net\/vimdoc\/vimuiex.html#vimuiex-operation\r\n\r\nOpening files, selecting buffers:\r\n   * VxBufListSelect:\r\n     Buffer explorer\/manager.\r\n     http:\/\/vimuiex.sourceforge.net\/vimdoc\/vimuiex_plugins.html#vimuiex-vxbuflistselect;\r\n   * VxOpenRecentFile:\r\n     Display a list of recent files, open selected file.\r\n   * VxFileBrowser:\r\n     Browse the local filesystem to open some files.  Recent directory list is available to find files faster.\r\n   * VxFileFilter:\r\n     Display a list of files in current directory and subdirectories to a certain depth to open some files.\r\n\r\nFinding text:\r\n   * VxOccurRegex:\r\n     Display all occurences of a string in the listbox. The search range can be a buffer, a directory or a directory with its subdirectories. Uses vimgrep or external grep for directory searches.\r\n     http:\/\/vimuiex.sourceforge.net\/vimdoc\/vimuiex_plugins.html#vimuiex-vxoccur;\r\n   * VxOccurCurrent:\r\n     Capture output from [I and show it in the listbox.\r\n   * VxOccurTags:\r\n     Process current file with ctags, show results in the listbox.\r\n   * VxOccurRutines:\r\n     Display the lines that match a predefined regular expression for current filetype. Example implementations for: Vim, Python, D, LaTeX, BibTex, Html, Slice.\r\n   * VxSourceTasks:\r\n     Display TODO\/Task items in source files. The search range can be defined like with VxOccurRegex.\r\n   \r\n   Every command in this section stores its results in vxoccur history. A recent set of search results can be activated with :VxOccurSelectHist without running an expensive search command again.The commands :VxCPrev and :VxCNext select items while the list is closed. The command :VxOccurHist redisplays the active list.\r\n\r\n   A helper plugin VxMap enables a faster navigation through the list of results (and also the following: buffers, tabs, errorlist, locationlist).\r\n   http:\/\/vimuiex.sourceforge.net\/vimdoc\/vimuiex_plugins.html#vimuiex-vxmap;\r\n\r\nExtended builtin commands:\r\n   * VxTextMenu:\r\n     Display the Vim menu in the listbox, select items from menu.\r\n   * VxDisplay:\r\n     Display the output of :display, insert or execute selected register.\r\n   * VxMarks:\r\n     Display the output of :marks, jump to mark\r\n   * VxCmd:\r\n     Display the output of any command in a listbox\r\n   * The file vxcmdhist.vim:\r\n     Implements a function that displays the command line history in a listbox when PgUp is pressed\r\n\r\nMoving around:\r\n   Commands require \"+python_screen\" (download the patch below):\r\n   * VxLineJump:\r\n     Display lables in the line-number area and jump to selected label.\r\n   * VxWindowJump:\r\n     Display a label in the center of every window and jump to selected window.\r\n\r\nLinks:\r\n\r\nPatch and prebuilt binaries: http:\/\/sourceforge.net\/projects\/vimuiex\/files\/\r\nDetailed descriptions: http:\/\/vimuiex.sourceforge.net\/plugins.html\r\nExample keymap: http:\/\/vimuiex.sourceforge.net\/vimmapexmpl.html\r\n\r\n","install_details":"Prerequisites:\r\n  - Install Python 2.6\r\n  - Install vimscript#3061 (VxLib, 0.7.0 or newer)\r\n\r\nTo install:\r\n  - Download vimuiex.zip\r\n  - Extract the zip archive into your runtime directory (eg. ~\/.vim).\r\n  - To regenerate the documentation start Vim and execute:\r\n      :helptag <your runtime directory>\/doc\r\n\r\nMost of the plugins will work in Linux console Vim (using the Python Curses library).\r\nOther versions must use the vim internal implementation for drawing windows, for which a patch must be applied to Vim.\r\nThe patch and the prebuilt binaries for Windows are available at:\r\nhttp:\/\/sourceforge.net\/projects\/vimuiex\/files\/\r\n\r\n","5":"Prerequisites:\r\n  - Install Python 2.6\r\n  - Install vimscript#3061 (VxLib, 0.7.0 or newer)\r\n\r\nTo install:\r\n  - Download vimuiex.zip\r\n  - Extract the zip archive into your runtime directory (eg. ~\/.vim).\r\n  - To regenerate the documentation start Vim and execute:\r\n      :helptag <your runtime directory>\/doc\r\n\r\nMost of the plugins will work in Linux console Vim (using the Python Curses library).\r\nOther versions must use the vim internal implementation for drawing windows, for which a patch must be applied to Vim.\r\nThe patch and the prebuilt binaries for Windows are available at:\r\nhttp:\/\/sourceforge.net\/projects\/vimuiex\/files\/\r\n\r\n","first_name":"Marko","6":"Marko","last_name":"Mahni\u010d","7":"Mahnič","releases":[{"0":"2606","vim_version":"7.0","1":"7.0","script_version":"0.7.0","2":"0.7.0","version_comment":"* F1 displays mapped keys for current listbox\r\n* VxOccur can use find\/xargs\/grep\r\n* Recent searches are stored in memory for later use with VxOccurHist, VxOccurSelectHist\r\n* VxCNext\/VxCPrev to move through last search results\r\n* VxOccurRoutines supports D\r\n* Keymaps: <Plug> versions added for most Vx commands\r\n* VxLib installed separately","3":"* F1 displays mapped keys for current listbox\r\n* VxOccur can use find\/xargs\/grep\r\n* Recent searches are stored in memory for later use with VxOccurHist, VxOccurSelectHist\r\n* VxCNext\/VxCPrev to move through last search results\r\n* VxOccurRoutines supports D\r\n* Keymaps: <Plug> versions added for most Vx commands\r\n* VxLib installed separately","package":"vimuiex.zip","4":"vimuiex.zip","src_id":"13761","5":"13761","creation_date":"1283688178","6":"1283688178"},{"0":"2606","vim_version":"7.0","1":"7.0","script_version":"0.6.6","2":"0.6.6","version_comment":"* tested and fixed on windows (binaries for Python 2.6 uploaded to SF)\r\n* VxFileFilter: memory consumption reduced 50%\r\n* VxFileFilter: add pending items every 3-5s (gvim only)\r\n* fix in textfilter\r\n","3":"* tested and fixed on windows (binaries for Python 2.6 uploaded to SF)\r\n* VxFileFilter: memory consumption reduced 50%\r\n* VxFileFilter: add pending items every 3-5s (gvim only)\r\n* fix in textfilter\r\n","package":"vimuiex.zip","4":"vimuiex.zip","src_id":"12722","5":"12722","creation_date":"1269791167","6":"1269791167"},{"0":"2606","vim_version":"7.0","1":"7.0","script_version":"0.6.5","2":"0.6.5","version_comment":"* new command: VxFileFilter\r\n* filesystem scanned in a background thread\r\n* VxOccurRoutines: defaults for latex added\r\n* fix: crash after ou in VxBufferList\r\n ","3":"* new command: VxFileFilter\r\n* filesystem scanned in a background thread\r\n* VxOccurRoutines: defaults for latex added\r\n* fix: crash after ou in VxBufferList\r\n ","package":"vimuiex.zip","4":"vimuiex.zip","src_id":"12705","5":"12705","creation_date":"1269546132","6":"1269546132"},{"0":"2606","vim_version":"7.0","1":"7.0","script_version":"0.6.4","2":"0.6.4","version_comment":"* fix: colour of first listbox line was wrong in curses\r\n* fix: locale was not set properly in curses ","3":"* fix: colour of first listbox line was wrong in curses\r\n* fix: locale was not set properly in curses ","package":"vimuiex.zip","4":"vimuiex.zip","src_id":"12450","5":"12450","creation_date":"1266680598","6":"1266680598"},{"0":"2606","vim_version":"7.0","1":"7.0","script_version":"0.6.3","2":"0.6.3","version_comment":"* fix: colors were not defined in curses (I should test more!)\r\n* fix: catch vim.errors in textmenu\r\n* VxOccur: special treatment of displayed filenames: new color; when filtering hide if no items match\r\n","3":"* fix: colors were not defined in curses (I should test more!)\r\n* fix: catch vim.errors in textmenu\r\n* VxOccur: special treatment of displayed filenames: new color; when filtering hide if no items match\r\n","package":"vimuiex.zip","4":"vimuiex.zip","src_id":"12218","5":"12218","creation_date":"1264709158","6":"1264709158"},{"0":"2606","vim_version":"7.0","1":"7.0","script_version":"0.6.2","2":"0.6.2","version_comment":"* VxOccur, VxSourceTasks: also search in files; see docs.\r\n* VxDired: open multiple marked files\r\n* VxDisplay: execute register with @\r\n* VxMan: set MANWIDTH\r\n* fix: default color attributes after colorscheme change\r\n* fix: quickfixpreview - map keys locally ","3":"* VxOccur, VxSourceTasks: also search in files; see docs.\r\n* VxDired: open multiple marked files\r\n* VxDisplay: execute register with @\r\n* VxMan: set MANWIDTH\r\n* fix: default color attributes after colorscheme change\r\n* fix: quickfixpreview - map keys locally ","package":"vimuiex.zip","4":"vimuiex.zip","src_id":"12196","5":"12196","creation_date":"1264539899","6":"1264539899"},{"0":"2606","vim_version":"7.0","1":"7.0","script_version":"0.6.1","2":"0.6.1","version_comment":"* fix: handle E490 in EditLine\r\n* listbox filter: multiple terms separated with ','; negate term with '-'","3":"* fix: handle E490 in EditLine\r\n* listbox filter: multiple terms separated with ','; negate term with '-'","package":"vimuiex.zip","4":"vimuiex.zip","src_id":"12089","5":"12089","creation_date":"1263454589","6":"1263454589"},{"0":"2606","vim_version":"6.0","1":"6.0","script_version":"0.6","2":"0.6","version_comment":"* items in a list can be marked (map: m)\r\n* VxBufferList: change sort order; open with split, vsplit, tab; delete\/wipeout buffer; sort list; split-display marked buffers\r\n* VxRecentFiles: open multiple marked recent files; split\/vsplit\/tab-open\r\n* VxDired: respect browsedir setting; display\/open files from subdirectories \r\n* VxTextMenu: load menus.vim if not loaded\r\n* list contents is displayed using &encoding; (warning: double-width characers may cause wrong display; tested only with UTF)\r\n* vxlib plugin for previewing from QuickFix (map: <space>)\r\n","3":"* items in a list can be marked (map: m)\r\n* VxBufferList: change sort order; open with split, vsplit, tab; delete\/wipeout buffer; sort list; split-display marked buffers\r\n* VxRecentFiles: open multiple marked recent files; split\/vsplit\/tab-open\r\n* VxDired: respect browsedir setting; display\/open files from subdirectories \r\n* VxTextMenu: load menus.vim if not loaded\r\n* list contents is displayed using &encoding; (warning: double-width characers may cause wrong display; tested only with UTF)\r\n* vxlib plugin for previewing from QuickFix (map: <space>)\r\n","package":"vimuiex.zip","4":"vimuiex.zip","src_id":"12024","5":"12024","creation_date":"1262866184","6":"1262866184"},{"0":"2606","vim_version":"7.0","1":"7.0","script_version":"0.5","2":"0.5","version_comment":"* term and screen backends merged; wx deprecated\r\n* added listbox commands: 'i' - numeric item selection\r\n* command \"prevpage\" also key 'b'; \"nextpage\" also on 'space'\r\n* directory browser added (vxdired) with recent directory list (d)\r\n* other new plugins: vxjump, vxcapture, vxoccur, vxcmd\r\n* python modules reorganized\r\n* utility functions moved to vxlib:\r\n   - Vim Plugin Generator (python script)\r\n   - history manager for input() command\r\n   - ...\r\n","3":"* term and screen backends merged; wx deprecated\r\n* added listbox commands: 'i' - numeric item selection\r\n* command \"prevpage\" also key 'b'; \"nextpage\" also on 'space'\r\n* directory browser added (vxdired) with recent directory list (d)\r\n* other new plugins: vxjump, vxcapture, vxoccur, vxcmd\r\n* python modules reorganized\r\n* utility functions moved to vxlib:\r\n   - Vim Plugin Generator (python script)\r\n   - history manager for input() command\r\n   - ...\r\n","package":"vimuiex.zip","4":"vimuiex.zip","src_id":"11826","5":"11826","creation_date":"1259498979","6":"1259498979"},{"0":"2606","vim_version":"7.0","1":"7.0","script_version":"0.4","2":"0.4","version_comment":"* new backend - vim screen (requires vim patch)\r\n* menu shortcuts in term\/screen backends\r\n* recent file list plugin\r\n* plugin scripts renamed (py->vx); functions renamed (Py->Vx)\r\n* hilight objects added for popup list","3":"* new backend - vim screen (requires vim patch)\r\n* menu shortcuts in term\/screen backends\r\n* recent file list plugin\r\n* plugin scripts renamed (py->vx); functions renamed (Py->Vx)\r\n* hilight objects added for popup list","package":"vimuiex.zip","4":"vimuiex.zip","src_id":"10688","5":"10688","creation_date":"1243449918","6":"1243449918"},{"0":"2606","vim_version":"7.0","1":"7.0","script_version":"0.4p","2":"0.4p","version_comment":"* vim patch for screen backend","3":"* vim patch for screen backend","package":"vimpatch.zip","4":"vimpatch.zip","src_id":"10687","5":"10687","creation_date":"1243449855","6":"1243449855"}]},"2605":{"script_id":"2605","0":"2605","script_name":"nextfile","1":"nextfile","script_type":"utility","2":"utility","summary":"open the next or previous file","3":"open the next or previous file","description":"Usage:\r\n\r\n  COMMANDS:\r\n      :NFLoadGlob\r\n          load globbed files.\r\n          this command just load files to buffers, does not edit them.\r\n          options do NOT influence globbed file's list.\r\n              :NFLoadGlob *   \" to load all files in current directory.\r\n              :NFLoadGlob .*  \" to load all dotfiles in current directory.\r\n\r\n  MAPPING:\r\n      default:\r\n          <Leader>n - open the next file\r\n          <Leader>p - open the previous file\r\n\r\n  GLOBAL VARIABLES:\r\n      g:nf_map_next (default: '<Leader>n')\r\n          open the next file.\r\n\r\n      g:nf_map_previous (default: '<Leader>p')\r\n          open the previous file.\r\n\r\n      g:nf_include_dotfiles (default: 0)\r\n          if true, open the next dotfile.\r\n          if false, skip the next dotfile.\r\n\r\n      g:nf_open_command (default: 'edit')\r\n          open the (next|previous) file with this command.\r\n\r\n      g:nf_loop_files (default: 0)\r\n          if true, loop when reached the end.\r\n\r\n      g:nf_ignore_dir (default: 1)\r\n          if true, skip directory.\r\n\r\n      g:nf_ignore_ext (default: [])\r\n          ignore files of these extensions.\r\n          e.g.: \"o\", \"obj\", \"exe\"\r\n\r\n      g:nf_disable_if_empty_name (default: 0)\r\n          do not run mapping if current file name is empty.\r\n          behave like old version if this is true.\r\n\r\n      g:nf_commands (default: see below)\r\n          command's names.\r\n          if you do not want to define some commands,\r\n          please leave '' in command's value.\r\n              e.g.: let g:nf_commands = {'NFLoadGlob': ''}\r\n\r\n          default value:\r\n              let g:nf_commands = {\r\n              \\   'NFLoadGlob' : 'NFLoadGlob',\r\n              \\ }\r\n\r\n      g:nf_sort_funcref (default: '<SID>sort_compare')\r\n          function string or Funcref passed to sort().\r\n\r\n          default function's definition:\r\n              func! s:sort_compare(i, j)\r\n                  \" alphabetically\r\n                  return a:i > a:j\r\n              endfunc","4":"Usage:\r\n\r\n  COMMANDS:\r\n      :NFLoadGlob\r\n          load globbed files.\r\n          this command just load files to buffers, does not edit them.\r\n          options do NOT influence globbed file's list.\r\n              :NFLoadGlob *   \" to load all files in current directory.\r\n              :NFLoadGlob .*  \" to load all dotfiles in current directory.\r\n\r\n  MAPPING:\r\n      default:\r\n          <Leader>n - open the next file\r\n          <Leader>p - open the previous file\r\n\r\n  GLOBAL VARIABLES:\r\n      g:nf_map_next (default: '<Leader>n')\r\n          open the next file.\r\n\r\n      g:nf_map_previous (default: '<Leader>p')\r\n          open the previous file.\r\n\r\n      g:nf_include_dotfiles (default: 0)\r\n          if true, open the next dotfile.\r\n          if false, skip the next dotfile.\r\n\r\n      g:nf_open_command (default: 'edit')\r\n          open the (next|previous) file with this command.\r\n\r\n      g:nf_loop_files (default: 0)\r\n          if true, loop when reached the end.\r\n\r\n      g:nf_ignore_dir (default: 1)\r\n          if true, skip directory.\r\n\r\n      g:nf_ignore_ext (default: [])\r\n          ignore files of these extensions.\r\n          e.g.: \"o\", \"obj\", \"exe\"\r\n\r\n      g:nf_disable_if_empty_name (default: 0)\r\n          do not run mapping if current file name is empty.\r\n          behave like old version if this is true.\r\n\r\n      g:nf_commands (default: see below)\r\n          command's names.\r\n          if you do not want to define some commands,\r\n          please leave '' in command's value.\r\n              e.g.: let g:nf_commands = {'NFLoadGlob': ''}\r\n\r\n          default value:\r\n              let g:nf_commands = {\r\n              \\   'NFLoadGlob' : 'NFLoadGlob',\r\n              \\ }\r\n\r\n      g:nf_sort_funcref (default: '<SID>sort_compare')\r\n          function string or Funcref passed to sort().\r\n\r\n          default function's definition:\r\n              func! s:sort_compare(i, j)\r\n                  \" alphabetically\r\n                  return a:i > a:j\r\n              endfunc","install_details":"move into your ~\/.vim\/plugin","5":"move into your ~\/.vim\/plugin","first_name":"tyru","6":"tyru","last_name":" ","7":" ","releases":[{"0":"2605","vim_version":"7.0","1":"7.0","script_version":"0.0.3","2":"0.0.3","version_comment":"- fix edge case bug\r\n- add command :NFLoadGlob\r\n- mappings support range\r\n  ('10<Leader>n' opens a file which is 10 files away from current file.\r\n   '10<Leader>p' is reverse sequence)\r\n- add options g:nf_disable_if_empty_name, g:nf_sort_funcref, g:nf_commands\r\n- etc.","3":"- fix edge case bug\r\n- add command :NFLoadGlob\r\n- mappings support range\r\n  ('10<Leader>n' opens a file which is 10 files away from current file.\r\n   '10<Leader>p' is reverse sequence)\r\n- add options g:nf_disable_if_empty_name, g:nf_sort_funcref, g:nf_commands\r\n- etc.","package":"nextfile.vim","4":"nextfile.vim","src_id":"11755","5":"11755","creation_date":"1258552417","6":"1258552417"},{"0":"2605","vim_version":"6.0","1":"6.0","script_version":"0.0.2","2":"0.0.2","version_comment":"implement g:nf_ignore_ext.","3":"implement g:nf_ignore_ext.","package":"nextfile.vim","4":"nextfile.vim","src_id":"10791","5":"10791","creation_date":"1244563778","6":"1244563778"},{"0":"2605","vim_version":"6.0","1":"6.0","script_version":"0.0.1","2":"0.0.1","version_comment":"add g:nf_ignore_dir","3":"add g:nf_ignore_dir","package":"nextfile.vim","4":"nextfile.vim","src_id":"10376","5":"10376","creation_date":"1239367395","6":"1239367395"},{"0":"2605","vim_version":"6.0","1":"6.0","script_version":"0.0.0","2":"0.0.0","version_comment":"Initial upload","3":"Initial upload","package":"nextfile.vim","4":"nextfile.vim","src_id":"10371","5":"10371","creation_date":"1239273785","6":"1239273785"}]},"2604":{"script_id":"2604","0":"2604","script_name":"svk","1":"svk","script_type":"utility","2":"utility","summary":"syntax and a couple of useful commands for svk commit files","3":"syntax and a couple of useful commands for svk commit files","description":"Package includes syntax file for svk commit file and  two functions for adding files that are not under source control to commit (and vice-versa)","4":"Package includes syntax file for svk commit file and  two functions for adding files that are not under source control to commit (and vice-versa)","install_details":"- Copy the svk.tar.gz to $HOME\/.vim\/ and run\r\n    tar xvfz svk.tar.gz \r\n\r\n- Make sure filetype plugin is ON by issuing :filetype command and if it's off put following line in the beginning of .vimrc: \r\n    filetype plugin on\r\n\r\n- Enable autodetection of svk commit files by adding following  \r\n    au BufNewFile,BufRead svk-commit*.tmp   setf svk","5":"- Copy the svk.tar.gz to $HOME\/.vim\/ and run\r\n    tar xvfz svk.tar.gz \r\n\r\n- Make sure filetype plugin is ON by issuing :filetype command and if it's off put following line in the beginning of .vimrc: \r\n    filetype plugin on\r\n\r\n- Enable autodetection of svk commit files by adding following  \r\n    au BufNewFile,BufRead svk-commit*.tmp   setf svk","first_name":"Oleksandr","6":"Oleksandr","last_name":"Tymoshenko","7":"Tymoshenko","releases":[{"0":"2604","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"svk.tar.gz","4":"svk.tar.gz","src_id":"10366","5":"10366","creation_date":"1239243626","6":"1239243626"}]},"2603":{"script_id":"2603","0":"2603","script_name":"Haskell Cuteness","1":"Haskell Cuteness","script_type":"ftplugin","2":"ftplugin","summary":"Unicode cuteness for Haskell source","3":"Unicode cuteness for Haskell source","description":"This script is inspired by emacs's haskell-unicode-cuteness and based on vimscript #284 by Jos van den Oever.\r\nConverts all lambdas, equality, non-equality, get, let and arrows (<-, ->) to correspoding unicode symbols. If you think that I should add more characters, please feel free to email me or post your wishes in comments.\r\n\r\nUPDATE: The updated version of the script is at https:\/\/github.com\/frerich\/unicode-haskell maintained by Frerich Raabe.","4":"This script is inspired by emacs's haskell-unicode-cuteness and based on vimscript #284 by Jos van den Oever.\r\nConverts all lambdas, equality, non-equality, get, let and arrows (<-, ->) to correspoding unicode symbols. If you think that I should add more characters, please feel free to email me or post your wishes in comments.\r\n\r\nUPDATE: The updated version of the script is at https:\/\/github.com\/frerich\/unicode-haskell maintained by Frerich Raabe.","install_details":"Put it in your ftplugin\/haskell dir and edit your haskell source with cute unicode symbols","5":"Put it in your ftplugin\/haskell dir and edit your haskell source with cute unicode symbols","first_name":"Andrey","6":"Andrey","last_name":"Popp","7":"Popp","releases":[{"0":"2603","vim_version":"7.0","1":"7.0","script_version":"0.1.3","2":"0.1.3","version_comment":"added more mappings and fixed bug in HaskellSrcToUTF8, thanks to edwardkmett at Reddit","3":"added more mappings and fixed bug in HaskellSrcToUTF8, thanks to edwardkmett at Reddit","package":"haskell.vim","4":"haskell.vim","src_id":"10391","5":"10391","creation_date":"1239651810","6":"1239651810"},{"0":"2603","vim_version":"7.0","1":"7.0","script_version":"0.1.2","2":"0.1.2","version_comment":"Added syntax hightlighting as suggested by sfvisser at Reddit","3":"Added syntax hightlighting as suggested by sfvisser at Reddit","package":"haskell.vim","4":"haskell.vim","src_id":"10386","5":"10386","creation_date":"1239483318","6":"1239483318"},{"0":"2603","vim_version":"7.0","1":"7.0","script_version":"0.1.1","2":"0.1.1","version_comment":"Some bug fixed :)","3":"Some bug fixed :)","package":"haskell.vim","4":"haskell.vim","src_id":"10361","5":"10361","creation_date":"1239114927","6":"1239114927"}]},"2602":{"script_id":"2602","0":"2602","script_name":"paster.vim","1":"paster.vim","script_type":"utility","2":"utility","summary":"paster.vim - A configurable Vim plugin for posting text to a public pastebin","3":"paster.vim - A configurable Vim plugin for posting text to a public pastebin","description":"Paste text from the current document onto a public pastebin or board.  This \r\nimplementation is written in vim to reduce external dependencies to Python or\r\nPerl.  The only external dependency is cURL (e.g. \/usr\/bin\/curl in UNIX-like\r\nsystems) as an HTTP posting tool.  This posting tool, and all its command line\r\nparameters are configurable by the user.\r\n\r\nFeatures:\r\n\r\n* Pastes to any pastebin with a public API\r\n* The end-user's nick is configurable per use, or via .vimrc\r\n* Sends syntax highlighting information if the target supports it\r\n* Uses standard vim range commands for its use\r\n* Copies the URL where the text was pasted to the system clipboard and the\r\n  status line\r\n* Opens a web browser at the page where the paste was posted (v1.2)\r\n\r\nUsage\r\n\r\nInstall paster.vim to the appropriate default vim scripts directory for your\r\nconfiguration, normally $HOME\/.vim\/plugin \r\n\r\nOnce installed, the Paste[bin] command may be invoked in any of these patterns:\r\n\r\n- :.Paste -- paste the current line\r\n- :%Paste -- paste the entire document\r\n- :42,69Paste -- paste lines 42 through 69, inclusive\r\n\r\nThe Paste command will work with selections made in visual mode as well.\r\n\r\nPaste will prompt for a value if the user hasn't defined a \/nick or ID prior\r\nto the command's first invocation. \r\n\r\nUpon successful completion, Paste will display the URL to the paste.  Paste will also copy it to the window manager's clipboard under\r\nMacVim and gvim.\r\n\r\nProject page:  http:\/\/github.com\/pr3d4t0r\/paster\r\n","4":"Paste text from the current document onto a public pastebin or board.  This \r\nimplementation is written in vim to reduce external dependencies to Python or\r\nPerl.  The only external dependency is cURL (e.g. \/usr\/bin\/curl in UNIX-like\r\nsystems) as an HTTP posting tool.  This posting tool, and all its command line\r\nparameters are configurable by the user.\r\n\r\nFeatures:\r\n\r\n* Pastes to any pastebin with a public API\r\n* The end-user's nick is configurable per use, or via .vimrc\r\n* Sends syntax highlighting information if the target supports it\r\n* Uses standard vim range commands for its use\r\n* Copies the URL where the text was pasted to the system clipboard and the\r\n  status line\r\n* Opens a web browser at the page where the paste was posted (v1.2)\r\n\r\nUsage\r\n\r\nInstall paster.vim to the appropriate default vim scripts directory for your\r\nconfiguration, normally $HOME\/.vim\/plugin \r\n\r\nOnce installed, the Paste[bin] command may be invoked in any of these patterns:\r\n\r\n- :.Paste -- paste the current line\r\n- :%Paste -- paste the entire document\r\n- :42,69Paste -- paste lines 42 through 69, inclusive\r\n\r\nThe Paste command will work with selections made in visual mode as well.\r\n\r\nPaste will prompt for a value if the user hasn't defined a \/nick or ID prior\r\nto the command's first invocation. \r\n\r\nUpon successful completion, Paste will display the URL to the paste.  Paste will also copy it to the window manager's clipboard under\r\nMacVim and gvim.\r\n\r\nProject page:  http:\/\/github.com\/pr3d4t0r\/paster\r\n","install_details":"UNIX-like systems:\r\n\r\ncd ~\/.vim\r\n\r\nunzip \/path\/to\/paster.zip\r\n\r\nvi\r\n:helptags ~\/.vim\/doc\r\n\r\n\r\nWindows systems:\r\n\r\nUnpack the .zip file and copy the files to your\r\ngvim or vim configuration directory, then:\r\n\r\nvi\r\n:helptags C:\/path\/to\/doc\r\n","5":"UNIX-like systems:\r\n\r\ncd ~\/.vim\r\n\r\nunzip \/path\/to\/paster.zip\r\n\r\nvi\r\n:helptags ~\/.vim\/doc\r\n\r\n\r\nWindows systems:\r\n\r\nUnpack the .zip file and copy the files to your\r\ngvim or vim configuration directory, then:\r\n\r\nvi\r\n:helptags C:\/path\/to\/doc\r\n","first_name":"Eugene","6":"Eugene","last_name":"Ciurana","7":"Ciurana","releases":[{"0":"2602","vim_version":"7.0","1":"7.0","script_version":"1.2","2":"1.2","version_comment":"Option to open a web browser after the paste is posted to the pastebin site.  See the paster-config.vim file for details.  Set the g:PASTER_BROWSER_COMMAND variable in .vimrc with the command for opening the browser.\r\n\r\nMichael Jansen provided a pastey bug fix and ideas for creating the browser interface.","3":"Option to open a web browser after the paste is posted to the pastebin site.  See the paster-config.vim file for details.  Set the g:PASTER_BROWSER_COMMAND variable in .vimrc with the command for opening the browser.\r\n\r\nMichael Jansen provided a pastey bug fix and ideas for creating the browser interface.","package":"paster_vim-1_2.zip","4":"paster_vim-1_2.zip","src_id":"11515","5":"11515","creation_date":"1255266215","6":"1255266215"},{"0":"2602","vim_version":"7.0","1":"7.0","script_version":"1.1","2":"1.1","version_comment":"Will Gray provided the configuration for using pastey.net with paster.vim\r\nSeparated the configuration portion from the main script in paster-config.vim\r\n\r\nThere are no operational changes.  The installation and usage instructions are unchanged.","3":"Will Gray provided the configuration for using pastey.net with paster.vim\r\nSeparated the configuration portion from the main script in paster-config.vim\r\n\r\nThere are no operational changes.  The installation and usage instructions are unchanged.","package":"paster.zip","4":"paster.zip","src_id":"10455","5":"10455","creation_date":"1240683779","6":"1240683779"}]},"2601":{"script_id":"2601","0":"2601","script_name":"wargreycolorscheme","1":"wargreycolorscheme","script_type":"color scheme","2":"color scheme","summary":"Dark color scheme for terminal with full options","3":"Dark color scheme for terminal with full options","description":"I like to use vim in the terminal rather than with GUI front-end. So this plugin is only used in terminal and all the GUI settings are the same as the cterm.\r\n\r\nBTW:Let the terminal background transparent. You will feel more comfortable.\r\n\r\nScreenshots：http:\/\/wargrey.yo2.cn\/2009\/04\/05\/25586\/\r\n(Maybe you should save them to local to view the full version)","4":"I like to use vim in the terminal rather than with GUI front-end. So this plugin is only used in terminal and all the GUI settings are the same as the cterm.\r\n\r\nBTW:Let the terminal background transparent. You will feel more comfortable.\r\n\r\nScreenshots：http:\/\/wargrey.yo2.cn\/2009\/04\/05\/25586\/\r\n(Maybe you should save them to local to view the full version)","install_details":"Just throw it into the colors directory in your runtimepath.","5":"Just throw it into the colors directory in your runtimepath.","first_name":"Zhenliang","6":"Zhenliang","last_name":"Ju","7":"Ju","releases":[{"0":"2601","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"wargrey.vim","4":"wargrey.vim","src_id":"10350","5":"10350","creation_date":"1238932040","6":"1238932040"}]},"2600":{"script_id":"2600","0":"2600","script_name":"Symfony","1":"Symfony","script_type":"color scheme","2":"color scheme","summary":"Color scheme based on symfony php framework documentation","3":"Color scheme based on symfony php framework documentation","description":"I created this color scheme based on the Documenation of Symfony PHP Framework. This color scheme supports a 256 color terminal too, but it hasn\u00e2\u0080\u0099t been heavily tested. \r\n\r\nCheck out some screen shots of what it looks like with Vim script, Java and PHP\r\nhttp:\/\/juan.boxfi.com\/vim-color-schemes\/#symfony\r\n ","4":"I created this color scheme based on the Documenation of Symfony PHP Framework. This color scheme supports a 256 color terminal too, but it hasn\u00e2\u0080\u0099t been heavily tested. \r\n\r\nCheck out some screen shots of what it looks like with Vim script, Java and PHP\r\nhttp:\/\/juan.boxfi.com\/vim-color-schemes\/#symfony\r\n ","install_details":"Just drop into your colors directory.","5":"Just drop into your colors directory.","first_name":"Juan","6":"Juan","last_name":"Frias","7":"Frias","releases":[{"0":"2600","vim_version":"6.0","1":"6.0","script_version":"1.0.0","2":"1.0.0","version_comment":"Initial upload","3":"Initial upload","package":"symfony.vim","4":"symfony.vim","src_id":"10348","5":"10348","creation_date":"1238881839","6":"1238881839"}]},"2599":{"script_id":"2599","0":"2599","script_name":"todolist.vim","1":"todolist.vim","script_type":"syntax","2":"syntax","summary":"Highlights a plain-text to-do list to keep it manageable","3":"Highlights a plain-text to-do list to keep it manageable","description":"I use my to-do list as a dumping ground for text and notes, so as long-term ideas pile up my lists will inevitably blow up into hundreds or thousands of lines. This is the natural order of things, and vim with proper highlighting and formatting makes it manageable. I also prefer my text lit up like a Christmas tree.\r\n\r\nHighlighted:\r\n -  lines ending with a colon (\":\")\r\n -  lines prefixed by an asterisk (\"*\")\r\n -  from a left curly brace (\"{\") to the end of the line\r\n -  numbers\r\n -  standard panic words: TODO, XXX, and others\r\n -  a few common words that merit emphasis (yes, no, not, ...)\r\n -  a personalized list of words, e.g. names of friends and co-workers (customizing this will be made easier in a later release)\r\n\r\nFollowing the GTD approach is possible:\r\n\r\n    project -- end the line with a colon, and indent the tasks\r\n\r\n    tasks -- plain text, or starting with a dash, it doesn't matter.\r\n            (copy and paste is expected to work without reformatting.)\r\n\r\n    note -- prefix the line with an asterisk to highlight it in the\r\n            same style as source code comments. (for 1-liners.)\r\n\r\n    contexts -- I keep project definitions small and group them under\r\n            categories that can be used as keywords. Specifically, I\r\n            start a new category with a line of underscores and a curly\r\n            brace before the category name(s) and tags. The }} and {{\r\n            vim keybindings then work as expected, and * and # work for\r\n            finding matching category tags within other text.\r\n","4":"I use my to-do list as a dumping ground for text and notes, so as long-term ideas pile up my lists will inevitably blow up into hundreds or thousands of lines. This is the natural order of things, and vim with proper highlighting and formatting makes it manageable. I also prefer my text lit up like a Christmas tree.\r\n\r\nHighlighted:\r\n -  lines ending with a colon (\":\")\r\n -  lines prefixed by an asterisk (\"*\")\r\n -  from a left curly brace (\"{\") to the end of the line\r\n -  numbers\r\n -  standard panic words: TODO, XXX, and others\r\n -  a few common words that merit emphasis (yes, no, not, ...)\r\n -  a personalized list of words, e.g. names of friends and co-workers (customizing this will be made easier in a later release)\r\n\r\nFollowing the GTD approach is possible:\r\n\r\n    project -- end the line with a colon, and indent the tasks\r\n\r\n    tasks -- plain text, or starting with a dash, it doesn't matter.\r\n            (copy and paste is expected to work without reformatting.)\r\n\r\n    note -- prefix the line with an asterisk to highlight it in the\r\n            same style as source code comments. (for 1-liners.)\r\n\r\n    contexts -- I keep project definitions small and group them under\r\n            categories that can be used as keywords. Specifically, I\r\n            start a new category with a line of underscores and a curly\r\n            brace before the category name(s) and tags. The }} and {{\r\n            vim keybindings then work as expected, and * and # work for\r\n            finding matching category tags within other text.\r\n","install_details":"Copy the file todolist.vim into your ~\/.vim\/syntax directory. To trigger automatic highlighting, write the following line at the bottom of a file:\r\n\r\nvim: ft=todolist\r\n\r\nThe extension of your file doesn't matter, just the content.","5":"Copy the file todolist.vim into your ~\/.vim\/syntax directory. To trigger automatic highlighting, write the following line at the bottom of a file:\r\n\r\nvim: ft=todolist\r\n\r\nThe extension of your file doesn't matter, just the content.","first_name":"Eric","6":"Eric","last_name":"Talevich","7":"Talevich","releases":[{"0":"2599","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"todolist.vim","4":"todolist.vim","src_id":"10341","5":"10341","creation_date":"1238713121","6":"1238713121"}]},"2598":{"script_id":"2598","0":"2598","script_name":"reorder.vim","1":"reorder.vim","script_type":"utility","2":"utility","summary":"Reorder the items in natural language lists","3":"Reorder the items in natural language lists","description":"Supposing you have a list \"foo, bar, and baz\" in English where all of the elements are separated by commas and there's the word \"and\" or \"or\" before the last item in the list.\r\n\r\nThe attached Reorder plugin works as follows: Select the list you want to reorder in visual mode (like \"foo, bar, and baz\") then run :Reorder 3,2,1 (or :'<,'>Reorder 3,2,1 --- the line numbers are ignored for your convenience, since Vim puts them in anyway), and watch Vim reorder your list to \"baz, bar, and foo\".\r\n\r\nRequires Ruby support, and the facets gem installed.","4":"Supposing you have a list \"foo, bar, and baz\" in English where all of the elements are separated by commas and there's the word \"and\" or \"or\" before the last item in the list.\r\n\r\nThe attached Reorder plugin works as follows: Select the list you want to reorder in visual mode (like \"foo, bar, and baz\") then run :Reorder 3,2,1 (or :'<,'>Reorder 3,2,1 --- the line numbers are ignored for your convenience, since Vim puts them in anyway), and watch Vim reorder your list to \"baz, bar, and foo\".\r\n\r\nRequires Ruby support, and the facets gem installed.","install_details":"","5":"","first_name":"Ken","6":"Ken","last_name":"Bloom","7":"Bloom","releases":[{"0":"2598","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"reorder.vim","4":"reorder.vim","src_id":"10340","5":"10340","creation_date":"1238698036","6":"1238698036"}]},"2597":{"script_id":"2597","0":"2597","script_name":"lighttpd syntax","1":"lighttpd syntax","script_type":"syntax","2":"syntax","summary":"syntax highlighting for lighttpd config files","3":"syntax highlighting for lighttpd config files","description":"syntax highlighting for lighttpd config files.\r\n\r\nlighttpd (lighty) is lightweight open-source web server: http:\/\/www.lighttpd.net\/\r\n\r\nalways recent version can be grabbed from: http:\/\/cvs.pld-linux.org\/cgi-bin\/cvsweb.cgi\/packages\/vim-syntax-lighttpd\/lighttpd.vim","4":"syntax highlighting for lighttpd config files.\r\n\r\nlighttpd (lighty) is lightweight open-source web server: http:\/\/www.lighttpd.net\/\r\n\r\nalways recent version can be grabbed from: http:\/\/cvs.pld-linux.org\/cgi-bin\/cvsweb.cgi\/packages\/vim-syntax-lighttpd\/lighttpd.vim","install_details":"- for local install \r\nPREFIX=~\/.vim \r\n \r\n- for global install (requries root privileges) \r\nPREFIX=\/usr\/share\/vim\/vimfiles \r\n \r\n- and then run: \r\nmkdir -p $PREFIX\/{syntax,ftdetect} \r\ncp lighttpd.vim $PREFIX\/syntax\/lighttpd.vim \r\ncat > $PREFIX\/ftdetect\/lighttpd.vim <<-EOF \r\n\" lighttpd config\r\nau BufNewFile,BufRead \/etc\/lighttpd\/*.conf,lighttpd.conf set filetype=lighttpd\r\nEOF \r\n   ","5":"- for local install \r\nPREFIX=~\/.vim \r\n \r\n- for global install (requries root privileges) \r\nPREFIX=\/usr\/share\/vim\/vimfiles \r\n \r\n- and then run: \r\nmkdir -p $PREFIX\/{syntax,ftdetect} \r\ncp lighttpd.vim $PREFIX\/syntax\/lighttpd.vim \r\ncat > $PREFIX\/ftdetect\/lighttpd.vim <<-EOF \r\n\" lighttpd config\r\nau BufNewFile,BufRead \/etc\/lighttpd\/*.conf,lighttpd.conf set filetype=lighttpd\r\nEOF \r\n   ","first_name":"Elan","6":"Elan","last_name":"Ruusam\u00c3\u00a4e","7":"Ruusam\u00c3\u00a4e","releases":[{"0":"2597","vim_version":"6.0","1":"6.0","script_version":"1.16","2":"1.16","version_comment":"update with new keywords","3":"update with new keywords","package":"lighttpd.vim","4":"lighttpd.vim","src_id":"11697","5":"11697","creation_date":"1257771569","6":"1257771569"},{"0":"2597","vim_version":"6.0","1":"6.0","script_version":"1.11","2":"1.11","version_comment":"Initial upload","3":"Initial upload","package":"lighttpd.vim","4":"lighttpd.vim","src_id":"10332","5":"10332","creation_date":"1238595276","6":"1238595276"}]},"2596":{"script_id":"2596","0":"2596","script_name":"gvimfullscreen_win32","1":"gvimfullscreen_win32","script_type":"utility","2":"utility","summary":"Put gvim in full screen on Windows","3":"Put gvim in full screen on Windows","description":"Allows you to run gvim in full screen on Windows on a single monitor.\r\n\r\nThis is a copy of Yasuhiro Matsumoto's VimTweak's EnableMaximize functionality modified to deal with window borders and allowing the window to overlap the task bar.\r\n\r\nSource code included and also available on GitHub: http:\/\/github.com\/derekmcloughlin\/gvimfullscreen_win32\/tree\/master","4":"Allows you to run gvim in full screen on Windows on a single monitor.\r\n\r\nThis is a copy of Yasuhiro Matsumoto's VimTweak's EnableMaximize functionality modified to deal with window borders and allowing the window to overlap the task bar.\r\n\r\nSource code included and also available on GitHub: http:\/\/github.com\/derekmcloughlin\/gvimfullscreen_win32\/tree\/master","install_details":"Unzip the gvimfullscreen_win32.zip file. Copy the DLL to the folder where GVIM.EXE is located.\r\n\r\nCall directly:\r\n:call libcallnr(\"gvimfullscreen.dll\", \"ToggleFullScreen\", 0)<CR>\r\n\r\nMap a function key:\r\nmap <F11> <Esc>:call libcallnr(\"gvimfullscreen.dll\", \"ToggleFullScreen\", 0)<CR>\r\n\r\n\r\n","5":"Unzip the gvimfullscreen_win32.zip file. Copy the DLL to the folder where GVIM.EXE is located.\r\n\r\nCall directly:\r\n:call libcallnr(\"gvimfullscreen.dll\", \"ToggleFullScreen\", 0)<CR>\r\n\r\nMap a function key:\r\nmap <F11> <Esc>:call libcallnr(\"gvimfullscreen.dll\", \"ToggleFullScreen\", 0)<CR>\r\n\r\n\r\n","first_name":"Derek","6":"Derek","last_name":"McLoughlin","7":"McLoughlin","releases":[{"0":"2596","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"gvimfullscreen_win32.zip","4":"gvimfullscreen_win32.zip","src_id":"10328","5":"10328","creation_date":"1238502834","6":"1238502834"}]},"2595":{"script_id":"2595","0":"2595","script_name":"Skittles Dark","1":"Skittles Dark","script_type":"color scheme","2":"color scheme","summary":"Dark, colorful scheme","3":"Dark, colorful scheme","description":"Used the molokai color scheme as a template to build off then completely recolored almost everything to be a bit more colorful while still being quite readable.\r\n\r\nhttp:\/\/shawnbiddle.com\/devblog\/archive\/skittles-dark-a-vim-colorscheme\r\nScreenshot (PHP): http:\/\/shawnbiddle.com\/files\/skittles_php.png\r\nScreenshot (C++): http:\/\/shawnbiddle.com\/files\/skittles_cpp.png\r\n\r\n(Note: PHP Docblock highlighting in screenshot from custom php.vim syntax modifications, it will not be enabled by the theme)","4":"Used the molokai color scheme as a template to build off then completely recolored almost everything to be a bit more colorful while still being quite readable.\r\n\r\nhttp:\/\/shawnbiddle.com\/devblog\/archive\/skittles-dark-a-vim-colorscheme\r\nScreenshot (PHP): http:\/\/shawnbiddle.com\/files\/skittles_php.png\r\nScreenshot (C++): http:\/\/shawnbiddle.com\/files\/skittles_cpp.png\r\n\r\n(Note: PHP Docblock highlighting in screenshot from custom php.vim syntax modifications, it will not be enabled by the theme)","install_details":"","5":"","first_name":"Shawn","6":"Shawn","last_name":"Biddle","7":"Biddle","releases":[{"0":"2595","vim_version":"7.0","1":"7.0","script_version":"1.4","2":"1.4","version_comment":"Slight color updates, and cleaned up the script.","3":"Slight color updates, and cleaned up the script.","package":"skittles_dark.vim","4":"skittles_dark.vim","src_id":"13199","5":"13199","creation_date":"1276706450","6":"1276706450"},{"0":"2595","vim_version":"7.0","1":"7.0","script_version":"1.3","2":"1.3","version_comment":"Updated to have its own cterm defines instead of relying on the GuiColorScheme plugin.","3":"Updated to have its own cterm defines instead of relying on the GuiColorScheme plugin.","package":"skittles_dark.vim","4":"skittles_dark.vim","src_id":"12022","5":"12022","creation_date":"1262807663","6":"1262807663"},{"0":"2595","vim_version":"7.0","1":"7.0","script_version":"1.2","2":"1.2","version_comment":"Slight color changes to better support 256 color terms with the GuiColorScheme plugin. They should match almost identically now.","3":"Slight color changes to better support 256 color terms with the GuiColorScheme plugin. They should match almost identically now.","package":"skittles_dark.vim","4":"skittles_dark.vim","src_id":"11835","5":"11835","creation_date":"1259681648","6":"1259681648"},{"0":"2595","vim_version":"7.0","1":"7.0","script_version":"1.1","2":"1.1","version_comment":"Updates to the background color, line numbering and html tags for a bit more readability.","3":"Updates to the background color, line numbering and html tags for a bit more readability.","package":"skittles_dark.vim","4":"skittles_dark.vim","src_id":"10531","5":"10531","creation_date":"1241536991","6":"1241536991"},{"0":"2595","vim_version":"7.0","1":"7.0","script_version":"1","2":"1","version_comment":"Initial upload","3":"Initial upload","package":"skittles_dark.vim","4":"skittles_dark.vim","src_id":"10323","5":"10323","creation_date":"1238429466","6":"1238429466"}]},"2594":{"script_id":"2594","0":"2594","script_name":"tmarks","1":"tmarks","script_type":"utility","2":"utility","summary":"Browse, place, & delete marks","3":"Browse, place, & delete marks","description":"Also available via git: http:\/\/github.com\/tomtom\/tmarks_vim\r\n\r\nThis plugin provides commands to browse and to manipulate (place & \r\ndelete) marks.\r\n\r\n:TMarks\r\n    Browse all marks.\r\n\r\n:{range}TMarksPlace\r\n    Place the next available a-z mark at the specified line.\r\n\r\n:{range}TMarksDelete\r\n    Delete all a-z marks in range.\r\n\r\n:TMarksDeleteAll\r\n    Delete all a-z marks in the current buffer.\r\n\r\nYou can use vimscript #2584 to display the marks as signs.\r\n","4":"Also available via git: http:\/\/github.com\/tomtom\/tmarks_vim\r\n\r\nThis plugin provides commands to browse and to manipulate (place & \r\ndelete) marks.\r\n\r\n:TMarks\r\n    Browse all marks.\r\n\r\n:{range}TMarksPlace\r\n    Place the next available a-z mark at the specified line.\r\n\r\n:{range}TMarksDelete\r\n    Delete all a-z marks in range.\r\n\r\n:TMarksDeleteAll\r\n    Delete all a-z marks in the current buffer.\r\n\r\nYou can use vimscript #2584 to display the marks as signs.\r\n","install_details":"Edit the vba file and type:\r\n\r\n    :so %\r\n\r\nSee :help vimball for details. If you have difficulties or use vim 7.0, \r\nplease make sure, you have the current version of vimball\r\n(vimscript #1502) installed or update your runtime.\r\n\r\nThis script requires tlib (vimscript #1863) to be installed.","5":"Edit the vba file and type:\r\n\r\n    :so %\r\n\r\nSee :help vimball for details. If you have difficulties or use vim 7.0, \r\nplease make sure, you have the current version of vimball\r\n(vimscript #1502) installed or update your runtime.\r\n\r\nThis script requires tlib (vimscript #1863) to be installed.","first_name":"Tom","6":"Tom","last_name":"Link","7":"Link","releases":[{"0":"2594","vim_version":"7.0","1":"7.0","script_version":"0.2","2":"0.2","version_comment":"Please see http:\/\/github.com\/tomtom\/tmarks_vim\/commits\/master\/\nMD5 Checksum: 99db23f144800ee39e376b8bbb2ee5cf","3":"Please see http:\/\/github.com\/tomtom\/tmarks_vim\/commits\/master\/\nMD5 Checksum: 99db23f144800ee39e376b8bbb2ee5cf","package":"tmarks.vba","4":"tmarks.vba","src_id":"14161","5":"14161","creation_date":"1288626422","6":"1288626422"},{"0":"2594","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"tmarks.vba.gz","4":"tmarks.vba.gz","src_id":"10314","5":"10314","creation_date":"1238346481","6":"1238346481"}]},"2593":{"script_id":"2593","0":"2593","script_name":"LBufWin","1":"LBufWin","script_type":"utility","2":"utility","summary":"List loaded buffers in a location list.","3":"List loaded buffers in a location list.","description":"This plugin contains one command:                                             \r\n                                                                              \r\n:Ls |pattern|                                                                 \r\n                                                                              \r\nThe command creates a location list containing all of the currently loaded    \r\nbuffers in vim.  It takes one (optional) argument.  If it is supplied, it is  \r\ntreated as a pattern, and only buffers matching that pattern will be          \r\ndisplayed.                                                                    \r\n                                                                              \r\nLocation lists are a feature of Vim 7 and up.  Please see :he location-list if\r\nyou are curious.                                                              \r\n\r\nA blog post with more information and a video demo are at http:\/\/blog.coryechols.net\/2009\/03\/vim-script-buffer-select-in-window.html","4":"This plugin contains one command:                                             \r\n                                                                              \r\n:Ls |pattern|                                                                 \r\n                                                                              \r\nThe command creates a location list containing all of the currently loaded    \r\nbuffers in vim.  It takes one (optional) argument.  If it is supplied, it is  \r\ntreated as a pattern, and only buffers matching that pattern will be          \r\ndisplayed.                                                                    \r\n                                                                              \r\nLocation lists are a feature of Vim 7 and up.  Please see :he location-list if\r\nyou are curious.                                                              \r\n\r\nA blog post with more information and a video demo are at http:\/\/blog.coryechols.net\/2009\/03\/vim-script-buffer-select-in-window.html","install_details":"Just drop it into your ~\/.vim\/plugin folder.","5":"Just drop it into your ~\/.vim\/plugin folder.","first_name":"Cory","6":"Cory","last_name":"Echols","7":"Echols","releases":[{"0":"2593","vim_version":"7.0","1":"7.0","script_version":"1","2":"1","version_comment":"Initial upload","3":"Initial upload","package":"LBufWin.vim","4":"LBufWin.vim","src_id":"10308","5":"10308","creation_date":"1238185733","6":"1238185733"}]},"2592":{"script_id":"2592","0":"2592","script_name":"Zmrok","1":"Zmrok","script_type":"color scheme","2":"color scheme","summary":"Dark, warm color scheme","3":"Dark, warm color scheme","description":"This color scheme is somehow inspired by TextMate\\\\\\'s twilight.\r\nYou can see screenshot at http:\/\/krzysiek-goj.blogspot.com\/2009\/03\/introducing-zmrok.html","4":"This color scheme is somehow inspired by TextMate\\\\\\'s twilight.\r\nYou can see screenshot at http:\/\/krzysiek-goj.blogspot.com\/2009\/03\/introducing-zmrok.html","install_details":"put it in ~\/.vim\/colors\/","5":"put it in ~\/.vim\/colors\/","first_name":"Krzysiek","6":"Krzysiek","last_name":"Goj","7":"Goj","releases":[{"0":"2592","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"zmrok.vim","4":"zmrok.vim","src_id":"10304","5":"10304","creation_date":"1238167088","6":"1238167088"}]},"2591":{"script_id":"2591","0":"2591","script_name":"HTML AutoCloseTag","1":"HTML AutoCloseTag","script_type":"ftplugin","2":"ftplugin","summary":"Automatically closes HTML tags once you finish typing them.","3":"Automatically closes HTML tags once you finish typing them.","description":"Automatically closes HTML tag once you finish typing it with >. It is also smart enough to not autoclose tags when in a comment, when they are self-closing, or when they have already been closed.\r\n\r\nSo, <body id=\"foo\">, upon typing >, will become <body id=\"foo\">|<\/body>, where | is the cursor.\r\nBut, if you type <img src=\"bar.png\">, the script knows to keep it the same.","4":"Automatically closes HTML tag once you finish typing it with >. It is also smart enough to not autoclose tags when in a comment, when they are self-closing, or when they have already been closed.\r\n\r\nSo, <body id=\"foo\">, upon typing >, will become <body id=\"foo\">|<\/body>, where | is the cursor.\r\nBut, if you type <img src=\"bar.png\">, the script knows to keep it the same.","install_details":"Move html_autoclosetag.vim to ~\/.vim\/ftplugin (or equivalent, e.g. $HOME\\vimfiles\\ftplugin on Windows)\r\n\r\nTo enable for xhtml\/xml files, remember to add this to your .vimrc:\r\nau FileType xhtml,xml so ~\/.vim\/ftplugin\/html_autoclosetag.vim (or wherever you put it)","5":"Move html_autoclosetag.vim to ~\/.vim\/ftplugin (or equivalent, e.g. $HOME\\vimfiles\\ftplugin on Windows)\r\n\r\nTo enable for xhtml\/xml files, remember to add this to your .vimrc:\r\nau FileType xhtml,xml so ~\/.vim\/ftplugin\/html_autoclosetag.vim (or wherever you put it)","first_name":"Michael","6":"Michael","last_name":"Sanders","7":"Sanders","releases":[{"0":"2591","vim_version":"7.0","1":"7.0","script_version":"0.3","2":"0.3","version_comment":"Fixed bug with closing tag when on the start of the line, and cleaned up the code a bit.","3":"Fixed bug with closing tag when on the start of the line, and cleaned up the code a bit.","package":"html_autoclosetag.vim","4":"html_autoclosetag.vim","src_id":"10609","5":"10609","creation_date":"1242444201","6":"1242444201"},{"0":"2591","vim_version":"7.0","1":"7.0","script_version":"0.2","2":"0.2","version_comment":"Initial upload","3":"Initial upload","package":"html_autoclosetag.vim","4":"html_autoclosetag.vim","src_id":"10296","5":"10296","creation_date":"1238120211","6":"1238120211"}]},"2590":{"script_id":"2590","0":"2590","script_name":"FSwitch","1":"FSwitch","script_type":"utility","2":"utility","summary":"Allows switching between companion source files (like a.vim)","3":"Allows switching between companion source files (like a.vim)","description":"This script is designed to switch between companion files much like vimscript #31 (a.vim).\r\n\r\nOut of the box it will support C and C++ for most usages, unless you've got an interesting setup I haven't guessed.\r\n\r\nYou can:\r\n\r\n  - switch the file and keep it in the current window with :FSHere\r\n\r\n  - switch the file and put it in the window to the left with :FSLeft\r\n  - switch the file, split the window to the left and put it there with :FSSwitchLeft\r\n\r\n  - the same can be done with Right, Above and Below.\r\n\r\nThe switch function should be easy enough to call in different ways that give you more exotic behaviour.\r\n\r\nUsing the location directive, you can be quite specific about how the companion file is resolved and, more importantly how it's created when it doesn't exist.  This latter bit was apparently a sore point with a.vim and I hope that it's acceptable in FSwitch.\r\n\r\nYou can state locations as being the result of\r\n\r\n- a regular expression substitution\r\n- a globbed match\r\n- a relative path (either unconditionally or only if the current buffer's path matches a required pattern)\r\n- an absolute path (either unconditionally or only if the current buffer's path matches a required pattern)\r\n\r\nUsing an autocmd to set the buffer-local variables allows you great flexibility in specializing the behaviour of FSwitch.\r\n\r\nThere are also a couple of public functions you can use to retrieve the companion file for use in your own functions as well.\r\n\r\nThis script is now maintained at https:\/\/github.com\/derekwyatt\/vim-fswitch","4":"This script is designed to switch between companion files much like vimscript #31 (a.vim).\r\n\r\nOut of the box it will support C and C++ for most usages, unless you've got an interesting setup I haven't guessed.\r\n\r\nYou can:\r\n\r\n  - switch the file and keep it in the current window with :FSHere\r\n\r\n  - switch the file and put it in the window to the left with :FSLeft\r\n  - switch the file, split the window to the left and put it there with :FSSwitchLeft\r\n\r\n  - the same can be done with Right, Above and Below.\r\n\r\nThe switch function should be easy enough to call in different ways that give you more exotic behaviour.\r\n\r\nUsing the location directive, you can be quite specific about how the companion file is resolved and, more importantly how it's created when it doesn't exist.  This latter bit was apparently a sore point with a.vim and I hope that it's acceptable in FSwitch.\r\n\r\nYou can state locations as being the result of\r\n\r\n- a regular expression substitution\r\n- a globbed match\r\n- a relative path (either unconditionally or only if the current buffer's path matches a required pattern)\r\n- an absolute path (either unconditionally or only if the current buffer's path matches a required pattern)\r\n\r\nUsing an autocmd to set the buffer-local variables allows you great flexibility in specializing the behaviour of FSwitch.\r\n\r\nThere are also a couple of public functions you can use to retrieve the companion file for use in your own functions as well.\r\n\r\nThis script is now maintained at https:\/\/github.com\/derekwyatt\/vim-fswitch","install_details":"I've put this in a format that's easiest to use with pathogen (vimscript #2332).  Just unzip it in the right spot (say, ~\/.vim\/bundle) or unzip it and copy the 'plugin' and 'doc' directories into the right spot in the runtime path (say, ~\/.vim).\r\n\r\nYou can also use package managers that work with GitHub by using the repo https:\/\/github.com\/derekwyatt\/vim-fswitch","5":"I've put this in a format that's easiest to use with pathogen (vimscript #2332).  Just unzip it in the right spot (say, ~\/.vim\/bundle) or unzip it and copy the 'plugin' and 'doc' directories into the right spot in the runtime path (say, ~\/.vim).\r\n\r\nYou can also use package managers that work with GitHub by using the repo https:\/\/github.com\/derekwyatt\/vim-fswitch","first_name":"Derek","6":"Derek","last_name":"Wyatt","7":"Wyatt","releases":[{"0":"2590","vim_version":"7.0","1":"7.0","script_version":"0.9.3","2":"0.9.3","version_comment":"Small fix to check for Vim version (Timon Kelter)","3":"Small fix to check for Vim version (Timon Kelter)","package":"fswitch-0.9.3.zip","4":"fswitch-0.9.3.zip","src_id":"14047","5":"14047","creation_date":"1286922690","6":"1286922690"},{"0":"2590","vim_version":"7.0","1":"7.0","script_version":"0.9.2","2":"0.9.2","version_comment":"Fix to the split commands (Thanks to Michael Henry)","3":"Fix to the split commands (Thanks to Michael Henry)","package":"FSwitch-0.9.2.vba","4":"FSwitch-0.9.2.vba","src_id":"11504","5":"11504","creation_date":"1255175676","6":"1255175676"},{"0":"2590","vim_version":"7.0","1":"7.0","script_version":"0.9.1","2":"0.9.1","version_comment":"See :h fswitch-changes\r\n\r\nAdded :ifrel and :ifabs location directives\r\nExposed two public functions for retrieving the companion file in a script\r\nChanged defaults for c\/c++ code to use :ifrel instead of :rel","3":"See :h fswitch-changes\r\n\r\nAdded :ifrel and :ifabs location directives\r\nExposed two public functions for retrieving the companion file in a script\r\nChanged defaults for c\/c++ code to use :ifrel instead of :rel","package":"FSwitch-0.9.1.vba","4":"FSwitch-0.9.1.vba","src_id":"10277","5":"10277","creation_date":"1237985479","6":"1237985479"},{"0":"2590","vim_version":"7.2","1":"7.2","script_version":"0.9.0","2":"0.9.0","version_comment":"Initial upload","3":"Initial upload","package":"FSwitch-0.9.0.vba","4":"FSwitch-0.9.0.vba","src_id":"10275","5":"10275","creation_date":"1237853746","6":"1237853746"}]},"2589":{"script_id":"2589","0":"2589","script_name":"vylight","1":"vylight","script_type":"color scheme","2":"color scheme","summary":"A color scheme that integrates well with OS X. Light background.","3":"A color scheme that integrates well with OS X. Light background.","description":"This color scheme was designed to look good on an OS X desktop. It has a light background, and colors that fit in well with aqua.\r\n\r\nThis color scheme is meant for use with a gui version of Vim.\r\n\r\nPreview screenshots:\r\n\r\nhttp:\/\/www.node.mu\/images\/vy-color-schemes\/vylight.png\r\nhttp:\/\/www.node.mu\/images\/vy-color-schemes\/vylight_js.png\r\nhttp:\/\/www.node.mu\/images\/vy-color-schemes\/vylight_ruby.png","4":"This color scheme was designed to look good on an OS X desktop. It has a light background, and colors that fit in well with aqua.\r\n\r\nThis color scheme is meant for use with a gui version of Vim.\r\n\r\nPreview screenshots:\r\n\r\nhttp:\/\/www.node.mu\/images\/vy-color-schemes\/vylight.png\r\nhttp:\/\/www.node.mu\/images\/vy-color-schemes\/vylight_js.png\r\nhttp:\/\/www.node.mu\/images\/vy-color-schemes\/vylight_ruby.png","install_details":"Download the script and copy it to your ~\/.vim\/colors\/ directory. To tell Vim to use the color scheme, \":colorscheme vylight\".","5":"Download the script and copy it to your ~\/.vim\/colors\/ directory. To tell Vim to use the color scheme, \":colorscheme vylight\".","first_name":"Vy-Shane","6":"Vy-Shane","last_name":"Sin Fat","7":"Sin Fat","releases":[{"0":"2589","vim_version":"7.3","1":"7.3","script_version":"1.4","2":"1.4","version_comment":"Added colours for code folds.","3":"Added colours for code folds.","package":"vylight.vim","4":"vylight.vim","src_id":"15760","5":"15760","creation_date":"1306724693","6":"1306724693"},{"0":"2589","vim_version":"7.3","1":"7.3","script_version":"1.3","2":"1.3","version_comment":"Increased contrast slightly. Tweaks for better syntax colouring in ruby.","3":"Increased contrast slightly. Tweaks for better syntax colouring in ruby.","package":"vylight.vim","4":"vylight.vim","src_id":"14175","5":"14175","creation_date":"1288851192","6":"1288851192"},{"0":"2589","vim_version":"7.3","1":"7.3","script_version":"1.2","2":"1.2","version_comment":"Changed comment colours to grey.\r\nAdded support for ColorColumn.\r\nIncreased contrast slightly for normal text.","3":"Changed comment colours to grey.\r\nAdded support for ColorColumn.\r\nIncreased contrast slightly for normal text.","package":"vylight.vim","4":"vylight.vim","src_id":"13880","5":"13880","creation_date":"1285121254","6":"1285121254"},{"0":"2589","vim_version":"7.0","1":"7.0","script_version":"1.1","2":"1.1","version_comment":"Updated colours for vertical split windows.","3":"Updated colours for vertical split windows.","package":"vylight.vim","4":"vylight.vim","src_id":"11767","5":"11767","creation_date":"1258697352","6":"1258697352"},{"0":"2589","vim_version":"7.2","1":"7.2","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"vylight.vim","4":"vylight.vim","src_id":"10266","5":"10266","creation_date":"1237781591","6":"1237781591"}]},"2588":{"script_id":"2588","0":"2588","script_name":"glimpse","1":"glimpse","script_type":"utility","2":"utility","summary":"Use Glimpse searching easily from Vim.","3":"Use Glimpse searching easily from Vim.","description":"Glimpse is a powerful indexing and query system, free for personal use.\r\n\thttp:\/\/www.webglimpse.net\r\n\r\nVimGlimpse is a basic Glimpse interface within Vim, based on a Vim Tip from\r\nJean-Rene David. \r\n\thttp:\/\/vim.wikia.com\/wiki\/Use_glimpse_from_within_Vim\r\n\r\nVimGlimpse retains normal Vim :grep functionality, and provides\r\nadditional Glimpse features outside of what :grepprg can allow.  By\r\ndefault, VimGlimpse only searches within your current working directory,\r\nmaking it ideal for near instantaneous searches across a project.\r\n\r\nExamples:\r\n\r\n    :Glimpse porksausage\r\n\r\n\t\tFind porksausage across all files in the current working directory.\r\n\r\n    :Glimpse needle haystack.h$\r\n\r\n\t\tFinds all needles in all haystack.h's files.\r\n\r\n\t:let g:glimpseFlags = \"-iny -2\"\r\n\t:Glimpse Anestesiology html \r\n\r\n\t\tOutputs all occurrences of  Anestesiology  with  two  errors  in\r\n\t\tfiles with html somewhere in their full name.\r\n\r\n\t:Glimpse windsurfing;Arizona mail;1993\r\n\r\n\t\tFinds  all lines containing windsurfing and Arizona in all files\r\n\t\thaving `mail' and '1993' somewhere in their full name.\r\n\r\nResults are placed into the |quickfix| window.  Additionally, the 'q' key is\r\nbound to the window so you can close it again quickly. \r\n\r\n","4":"Glimpse is a powerful indexing and query system, free for personal use.\r\n\thttp:\/\/www.webglimpse.net\r\n\r\nVimGlimpse is a basic Glimpse interface within Vim, based on a Vim Tip from\r\nJean-Rene David. \r\n\thttp:\/\/vim.wikia.com\/wiki\/Use_glimpse_from_within_Vim\r\n\r\nVimGlimpse retains normal Vim :grep functionality, and provides\r\nadditional Glimpse features outside of what :grepprg can allow.  By\r\ndefault, VimGlimpse only searches within your current working directory,\r\nmaking it ideal for near instantaneous searches across a project.\r\n\r\nExamples:\r\n\r\n    :Glimpse porksausage\r\n\r\n\t\tFind porksausage across all files in the current working directory.\r\n\r\n    :Glimpse needle haystack.h$\r\n\r\n\t\tFinds all needles in all haystack.h's files.\r\n\r\n\t:let g:glimpseFlags = \"-iny -2\"\r\n\t:Glimpse Anestesiology html \r\n\r\n\t\tOutputs all occurrences of  Anestesiology  with  two  errors  in\r\n\t\tfiles with html somewhere in their full name.\r\n\r\n\t:Glimpse windsurfing;Arizona mail;1993\r\n\r\n\t\tFinds  all lines containing windsurfing and Arizona in all files\r\n\t\thaving `mail' and '1993' somewhere in their full name.\r\n\r\nResults are placed into the |quickfix| window.  Additionally, the 'q' key is\r\nbound to the window so you can close it again quickly. \r\n\r\n","install_details":"Install the VimBall plugin (vimscript #1502) if you don't already have it.\r\n\r\nThen open glimpse.vba from within vim.\r\n\r\n    :so %\r\n\r\nRestart vim, read the the docs (:help glimpse), and enjoy.","5":"Install the VimBall plugin (vimscript #1502) if you don't already have it.\r\n\r\nThen open glimpse.vba from within vim.\r\n\r\n    :so %\r\n\r\nRestart vim, read the the docs (:help glimpse), and enjoy.","first_name":"Mahlon","6":"Mahlon","last_name":"Smith","7":"Smith","releases":[{"0":"2588","vim_version":"7.0","1":"7.0","script_version":"0.3","2":"0.3","version_comment":"Fixed :GlimpseIndex problems for the vast majority of error cases.  If indexing still doesn't work, now display the error for easier user debugging instead of silently eating it.","3":"Fixed :GlimpseIndex problems for the vast majority of error cases.  If indexing still doesn't work, now display the error for easier user debugging instead of silently eating it.","package":"glimpse.vba.gz","4":"glimpse.vba.gz","src_id":"11103","5":"11103","creation_date":"1248975822","6":"1248975822"},{"0":"2588","vim_version":"7.0","1":"7.0","script_version":"0.2","2":"0.2","version_comment":"Fix the \"pattern too long has > 32 chars\" error.  (Empty boolean search for filename paths.)","3":"Fix the \"pattern too long has > 32 chars\" error.  (Empty boolean search for filename paths.)","package":"glimpse.vba","4":"glimpse.vba","src_id":"10309","5":"10309","creation_date":"1238209188","6":"1238209188"},{"0":"2588","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"glimpse.vba","4":"glimpse.vba","src_id":"10250","5":"10250","creation_date":"1237480975","6":"1237480975"}]},"2587":{"script_id":"2587","0":"2587","script_name":"PDV revised","1":"PDV revised","script_type":"utility","2":"utility","summary":"revised, fixed and more featured version of pdv","3":"revised, fixed and more featured version of pdv","description":"originally the 2005 PDV phpDocumentor for VIM tool (http:\/\/www.vim.org\/scripts\/script.php?script_id=1355)\r\n\r\n- fixed bugs w\/ parameters not finding booleans\r\n- added folding marker comment functionality\r\n","4":"originally the 2005 PDV phpDocumentor for VIM tool (http:\/\/www.vim.org\/scripts\/script.php?script_id=1355)\r\n\r\n- fixed bugs w\/ parameters not finding booleans\r\n- added folding marker comment functionality\r\n","install_details":"inoremap <C-P> <ESC>:call PhpDocSingle()<CR>i\r\nnnoremap <C-P> :call PhpDocSingle()<CR>\r\nvnoremap <C-P> :call PhpDocRange()<CR>\r\n","5":"inoremap <C-P> <ESC>:call PhpDocSingle()<CR>i\r\nnnoremap <C-P> :call PhpDocSingle()<CR>\r\nvnoremap <C-P> :call PhpDocRange()<CR>\r\n","first_name":"kevin","6":"kevin","last_name":"olson","7":"olson","releases":[{"0":"2587","vim_version":"7.0","1":"7.0","script_version":"1.1.3","2":"1.1.3","version_comment":"fixed a couple indentation bugs","3":"fixed a couple indentation bugs","package":"php-doc.vim","4":"php-doc.vim","src_id":"10247","5":"10247","creation_date":"1237452467","6":"1237452467"}]},"2586":{"script_id":"2586","0":"2586","script_name":"upAndDown","1":"upAndDown","script_type":"utility","2":"utility","summary":"Swapping a line with the line directly above or below","3":"Swapping a line with the line directly above or below","description":"Swapping a line with the line directly above or below it is a common task when writing computer software.\r\nThis script provides some mappings for normal, insert and visual modes which make this more easily accomplished.\r\nUsing it allows you to move a line (or multiple lines) of text up or down within a document using the <S> and <Up>\/<Down> arrow keys.\r\nThis is similar to the <Alt> and <Up>\/<Down> arrow text movement feature in Eclipse.\r\nThanks to tips http:\/\/vim.wikia.com\/wiki\/VimTip191.","4":"Swapping a line with the line directly above or below it is a common task when writing computer software.\r\nThis script provides some mappings for normal, insert and visual modes which make this more easily accomplished.\r\nUsing it allows you to move a line (or multiple lines) of text up or down within a document using the <S> and <Up>\/<Down> arrow keys.\r\nThis is similar to the <Alt> and <Up>\/<Down> arrow text movement feature in Eclipse.\r\nThanks to tips http:\/\/vim.wikia.com\/wiki\/VimTip191.","install_details":"Download vimball, open it with vim, and do :so %.\r\nBy default, use <S-Up> and <S-Down> to move line or block of lines.\r\nYou can override this with remapping of :\r\n<Plug>upAndDownUp\r\n<Plug>upAndDownDown\r\n<Plug>upAndDownInsertUp\r\n<Plug>upAndDownInsertDown\r\n<Plug>upAndDownVisualUp\r\n<Plug>upAndDownVisualDown\r\n","5":"Download vimball, open it with vim, and do :so %.\r\nBy default, use <S-Up> and <S-Down> to move line or block of lines.\r\nYou can override this with remapping of :\r\n<Plug>upAndDownUp\r\n<Plug>upAndDownDown\r\n<Plug>upAndDownInsertUp\r\n<Plug>upAndDownInsertDown\r\n<Plug>upAndDownVisualUp\r\n<Plug>upAndDownVisualDown\r\n","first_name":"Frederic","6":"Frederic","last_name":"Hardy","7":"Hardy","releases":[{"0":"2586","vim_version":"7.0","1":"7.0","script_version":"0.0.3","2":"0.0.3","version_comment":"Fix a strange behavior with MacVim 7.4 related to folds.","3":"Fix a strange behavior with MacVim 7.4 related to folds.","package":"upAndDown.vim","4":"upAndDown.vim","src_id":"23374","5":"23374","creation_date":"1433936044","6":"1433936044"},{"0":"2586","vim_version":"6.0","1":"6.0","script_version":"0.0.2","2":"0.0.2","version_comment":"Add GLVS support.","3":"Add GLVS support.","package":"upAndDown.vba","4":"upAndDown.vba","src_id":"10241","5":"10241","creation_date":"1237375722","6":"1237375722"},{"0":"2586","vim_version":"6.0","1":"6.0","script_version":"0.0.1","2":"0.0.1","version_comment":"Initial upload","3":"Initial upload","package":"upAndDown.vba","4":"upAndDown.vba","src_id":"10240","5":"10240","creation_date":"1237375560","6":"1237375560"}]},"2585":{"script_id":"2585","0":"2585","script_name":"lilydjwg_dark","1":"lilydjwg_dark","script_type":"color scheme","2":"color scheme","summary":"A color scheme with dark background.","3":"A color scheme with dark background.","description":"This is a color scheme with dark background (mainly #222222), and colorful foreground colors.\r\nScreenshot:\r\nhttp:\/\/missyou11.blog.163.com\/prevPhoto.do?photoId=3357662616&albumId=90019764\r\nterminal version:http:\/\/missyou11.blog.163.com\/prevPhoto.do?photoId=3357662648&albumId=90019764","4":"This is a color scheme with dark background (mainly #222222), and colorful foreground colors.\r\nScreenshot:\r\nhttp:\/\/missyou11.blog.163.com\/prevPhoto.do?photoId=3357662616&albumId=90019764\r\nterminal version:http:\/\/missyou11.blog.163.com\/prevPhoto.do?photoId=3357662648&albumId=90019764","install_details":"Just put it in your ~\/.vim\/colors (Linux) or $VIM\\vimfiles (Windows).","5":"Just put it in your ~\/.vim\/colors (Linux) or $VIM\\vimfiles (Windows).","first_name":"lilydjwg","6":"lilydjwg","last_name":" ","7":" ","releases":[{"0":"2585","vim_version":"7.0","1":"7.0","script_version":"1.3","2":"1.3","version_comment":"fix Visual highlighting with vim 9.1.61.","3":"fix Visual highlighting with vim 9.1.61.","package":"lilydjwg_dark.vim","4":"lilydjwg_dark.vim","src_id":"28599","5":"28599","creation_date":"1706676158","6":"1706676158"},{"0":"2585","vim_version":"7.0","1":"7.0","script_version":"1.2","2":"1.2","version_comment":"* support for newly added CursorLineNr group","3":"* support for newly added CursorLineNr group","package":"lilydjwg_dark.vim","4":"lilydjwg_dark.vim","src_id":"17645","5":"17645","creation_date":"1332522273","6":"1332522273"},{"0":"2585","vim_version":"7.0","1":"7.0","script_version":"1.1","2":"1.1","version_comment":"Add 256-color term support; modified pop-up menu colors; modified diff colors.","3":"Add 256-color term support; modified pop-up menu colors; modified diff colors.","package":"lilydjwg_dark.vim","4":"lilydjwg_dark.vim","src_id":"10626","5":"10626","creation_date":"1242656684","6":"1242656684"},{"0":"2585","vim_version":"7.0","1":"7.0","script_version":"1.0.1","2":"1.0.1","version_comment":"A few small improvements.","3":"A few small improvements.","package":"lilydjwg_dark.vim","4":"lilydjwg_dark.vim","src_id":"10383","5":"10383","creation_date":"1239459060","6":"1239459060"},{"0":"2585","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"lilydjwg_dark.vim","4":"lilydjwg_dark.vim","src_id":"10236","5":"10236","creation_date":"1237344600","6":"1237344600"}]},"2584":{"script_id":"2584","0":"2584","script_name":"quickfixsigns","1":"quickfixsigns","script_type":"utility","2":"utility","summary":"Show signs at lines with quickfix items (e.g. errors), VCS diffs & marks etc.","3":"Show signs at lines with quickfix items (e.g. errors), VCS diffs & marks etc.","description":"http:\/\/github.com\/tomtom\/quickfixsigns_vim\r\n\r\nDisplay |signs| at interesting lines:\r\n\r\n    - items in the |quickfix| and |location-lists| (e.g. compilation errors)\r\n    - |marks| a-zA-Z\r\n    - changes (given the file is under a VCS like git, svn, mercurial, \r\n      or bazaar -- see |g:tlib#vcs#def| for a list of supported VCSs)\r\n    - breakpoints: vim\r\n    - cursor position\r\n    - relative line numbers (show numbers only until the cursor moves; \r\n      this requires that you add the following command to |vimrc|:\r\n        noremap <silent> <leader><c-l> :call quickfixsigns#RelNumbersOnce()<cr>\r\n    - etc.\r\n\r\nOther lists can be configured via the |g:quickfixsigns_lists| variable.\r\n\r\nThe text attached to a quickfix or location-list entry is displayed in a \r\nballoon via 'balloonexpr'.\r\nNOTE: This could cause a conflict with other plugins that make use of \r\nballoons.\r\n\r\nIf you want nicer looking images instead of the ASCII markers, you have \r\nto change the following signs' definition either in your |vimrc| file or \r\nin $VIMFILES\/after\/plugin\/quickfixsigns.vim (by use of |sign-define|):\r\n\r\n    QFS_QFL ... Entries in the |quickfix| list\r\n    QFS_LOC ... Entries in the |location-list|\r\n    QFS_Mark_[a-zA-Z] ... Marks\r\n    QFS_CURSOR ... Current cursor position\r\n    QFS_BREAKPOINT ... Breakpoints\r\n    QFS_REL_x ... Relative line numbers\r\n    QFS_VCS_{ADD,DEL,CHANGE} ... VCS changes (see also \r\n            |g:quickfixsigns#vcsdiff#highlight|)\r\n\r\nCREDITS:\r\nquickfixsigns includes some icons from the open icon library. See \r\nhttp:\/\/openiconlibrary.sourceforge.net for details.\r\n","4":"http:\/\/github.com\/tomtom\/quickfixsigns_vim\r\n\r\nDisplay |signs| at interesting lines:\r\n\r\n    - items in the |quickfix| and |location-lists| (e.g. compilation errors)\r\n    - |marks| a-zA-Z\r\n    - changes (given the file is under a VCS like git, svn, mercurial, \r\n      or bazaar -- see |g:tlib#vcs#def| for a list of supported VCSs)\r\n    - breakpoints: vim\r\n    - cursor position\r\n    - relative line numbers (show numbers only until the cursor moves; \r\n      this requires that you add the following command to |vimrc|:\r\n        noremap <silent> <leader><c-l> :call quickfixsigns#RelNumbersOnce()<cr>\r\n    - etc.\r\n\r\nOther lists can be configured via the |g:quickfixsigns_lists| variable.\r\n\r\nThe text attached to a quickfix or location-list entry is displayed in a \r\nballoon via 'balloonexpr'.\r\nNOTE: This could cause a conflict with other plugins that make use of \r\nballoons.\r\n\r\nIf you want nicer looking images instead of the ASCII markers, you have \r\nto change the following signs' definition either in your |vimrc| file or \r\nin $VIMFILES\/after\/plugin\/quickfixsigns.vim (by use of |sign-define|):\r\n\r\n    QFS_QFL ... Entries in the |quickfix| list\r\n    QFS_LOC ... Entries in the |location-list|\r\n    QFS_Mark_[a-zA-Z] ... Marks\r\n    QFS_CURSOR ... Current cursor position\r\n    QFS_BREAKPOINT ... Breakpoints\r\n    QFS_REL_x ... Relative line numbers\r\n    QFS_VCS_{ADD,DEL,CHANGE} ... VCS changes (see also \r\n            |g:quickfixsigns#vcsdiff#highlight|)\r\n\r\nCREDITS:\r\nquickfixsigns includes some icons from the open icon library. See \r\nhttp:\/\/openiconlibrary.sourceforge.net for details.\r\n","install_details":"Requirements: has('signs')\r\n\r\nEdit the vba file and type: >\r\n\r\n    :so %\r\n\r\nSee :help vimball (vimscript #1502) for details.","5":"Requirements: has('signs')\r\n\r\nEdit the vba file and type: >\r\n\r\n    :so %\r\n\r\nSee :help vimball (vimscript #1502) for details.","first_name":"Tom","6":"Tom","last_name":"Link","7":"Link","releases":[{"0":"2584","vim_version":"7.0","1":"7.0","script_version":"1.05","2":"1.05","version_comment":"- FIX: regexp-related error @ windows: properly escape backslashes\nMD5 checksum: 7e465b9bdccd1736746d8f02ba4637e9","3":"- FIX: regexp-related error @ windows: properly escape backslashes\nMD5 checksum: 7e465b9bdccd1736746d8f02ba4637e9","package":"quickfixsigns.vba","4":"quickfixsigns.vba","src_id":"21712","5":"21712","creation_date":"1396458235","6":"1396458235"},{"0":"2584","vim_version":"7.0","1":"7.0","script_version":"1.04","2":"1.04","version_comment":"- FIX #48: Omit 3rd arg for getbufvar() (vim 7.3 compatibility)\nMD5 checksum: 556e79d0556d77801d76c634f7a3be50","3":"- FIX #48: Omit 3rd arg for getbufvar() (vim 7.3 compatibility)\nMD5 checksum: 556e79d0556d77801d76c634f7a3be50","package":"quickfixsigns.vba","4":"quickfixsigns.vba","src_id":"21677","5":"21677","creation_date":"1395942293","6":"1395942293"},{"0":"2584","vim_version":"7.0","1":"7.0","script_version":"1.03","2":"1.03","version_comment":"- FIX: set quickfix signs when loaded after vim_starting\n- Additional icon files from the open icon library\n- Use different signs for errors & warnings (closes #42)\n- g:quickfixsign_type_rx: patch suboptimal 'errorformat' definitions (fix #42)\n- Changed icons\n- FIX #42: Use \"*\" if &ft is empty (it is never unset)\n- Configurable g:quickfixsign_timeout (default value for timeout option)\n- Remove InsertChange from g:quickfixsigns_events\n- g:quickfixsigns_blacklist_buffer matches full filename (don't check buffers with empty filenames)\n- Minor improvements to avoid unnecessary updates (fix #43)\n- Call s:UpdateLineNumbers() only if necessary\n- g:quickfixsign_use_dummy: Option to set dummy sign (fix #44)\n- Make sure to use new IDs for dummy signs\n- Set the dummy sign ID correctly\n- g:quickfixsign_use_dummy defaults to 1\n- g:quickfixsigns_class_vcsdiff: Update on FocusGained events\n- Add -bar to command definitions\n- Call s:UpdateLineNumbers() only when the list has actually changed\n- g:quickfixsigns_class_vcsdiff: Remove FocusGained event Caused infinite loop when calling git etc.\n- doc: fix grammar\/typos with \"Adding new sign classes\"\n- :QuickfixsignsSet: Takes sign classes as optional arguments\n- quickfixsigns_register is script-local; FIX #47: Use g:quickfixsigns_lists to toggle state\n- Call RemoveBuffer on BufDelete, not BufUnload (fix #46)\nMD5 checksum: 415d45c58cbbce01e276d80685ce3096","3":"- FIX: set quickfix signs when loaded after vim_starting\n- Additional icon files from the open icon library\n- Use different signs for errors & warnings (closes #42)\n- g:quickfixsign_type_rx: patch suboptimal 'errorformat' definitions (fix #42)\n- Changed icons\n- FIX #42: Use \"*\" if &ft is empty (it is never unset)\n- Configurable g:quickfixsign_timeout (default value for timeout option)\n- Remove InsertChange from g:quickfixsigns_events\n- g:quickfixsigns_blacklist_buffer matches full filename (don't check buffers with empty filenames)\n- Minor improvements to avoid unnecessary updates (fix #43)\n- Call s:UpdateLineNumbers() only if necessary\n- g:quickfixsign_use_dummy: Option to set dummy sign (fix #44)\n- Make sure to use new IDs for dummy signs\n- Set the dummy sign ID correctly\n- g:quickfixsign_use_dummy defaults to 1\n- g:quickfixsigns_class_vcsdiff: Update on FocusGained events\n- Add -bar to command definitions\n- Call s:UpdateLineNumbers() only when the list has actually changed\n- g:quickfixsigns_class_vcsdiff: Remove FocusGained event Caused infinite loop when calling git etc.\n- doc: fix grammar\/typos with \"Adding new sign classes\"\n- :QuickfixsignsSet: Takes sign classes as optional arguments\n- quickfixsigns_register is script-local; FIX #47: Use g:quickfixsigns_lists to toggle state\n- Call RemoveBuffer on BufDelete, not BufUnload (fix #46)\nMD5 checksum: 415d45c58cbbce01e276d80685ce3096","package":"quickfixsigns.vba","4":"quickfixsigns.vba","src_id":"21673","5":"21673","creation_date":"1395839692","6":"1395839692"},{"0":"2584","vim_version":"7.0","1":"7.0","script_version":"1.02","2":"1.02","version_comment":"- vcsdiff: Trigger on BufRead instead of BufEnter events (fixes #30)\n- vcsdiff: Trigger update on FocusGained events\n- vcsdiff: cache intermediate results\n- quickfixsigns#vcsdiff#GetList(): Make sure to return a list (fixes #32)\n- vcsdiff: Change signs to be more like diff -y\n- vcsdiff: Removed FocusGained event (fixes #33)\n- Don't unplace signs on BufUnload events\n- Merge branch 'master' of https:\/\/github.com\/Chronial\/vim-quickfixsigns into vcsdiff_deletes\n- vcsdiff: Support for alternative list display (see https:\/\/github.com\/Chronial\/vim-quickfixsigns\/commit\/1cf739c790746157c3cb9b6234c1454333397c9e)\n- QuickfixsignsBalloon(): use elseif\n- Help template\n- Blacklist unite buffers\n- Provide an example with \"Sign Regexp\" input\n- Fix off-by-one error\n- Display debug message, if quickfixsigns_max is reached\n- Merge branch 'debug-info-with-max-reached' of https:\/\/github.com\/blueyed\/quickfixsigns_vim\n- Support for setting maxsigns per class (closes #38)\n- g:quickfixsigns#vcsdiff#list_type defaults to 1; use scriptencoding\n- g:quickfixsigns#vcsdiff#del_numbered: If enabled, add a number to DEL signs to indicate the number of deleted lines (fixes #37)\n- Use own colors\nMD5 checksum: df86c09e3a6fca2f363fcfd2af7d9fd5","3":"- vcsdiff: Trigger on BufRead instead of BufEnter events (fixes #30)\n- vcsdiff: Trigger update on FocusGained events\n- vcsdiff: cache intermediate results\n- quickfixsigns#vcsdiff#GetList(): Make sure to return a list (fixes #32)\n- vcsdiff: Change signs to be more like diff -y\n- vcsdiff: Removed FocusGained event (fixes #33)\n- Don't unplace signs on BufUnload events\n- Merge branch 'master' of https:\/\/github.com\/Chronial\/vim-quickfixsigns into vcsdiff_deletes\n- vcsdiff: Support for alternative list display (see https:\/\/github.com\/Chronial\/vim-quickfixsigns\/commit\/1cf739c790746157c3cb9b6234c1454333397c9e)\n- QuickfixsignsBalloon(): use elseif\n- Help template\n- Blacklist unite buffers\n- Provide an example with \"Sign Regexp\" input\n- Fix off-by-one error\n- Display debug message, if quickfixsigns_max is reached\n- Merge branch 'debug-info-with-max-reached' of https:\/\/github.com\/blueyed\/quickfixsigns_vim\n- Support for setting maxsigns per class (closes #38)\n- g:quickfixsigns#vcsdiff#list_type defaults to 1; use scriptencoding\n- g:quickfixsigns#vcsdiff#del_numbered: If enabled, add a number to DEL signs to indicate the number of deleted lines (fixes #37)\n- Use own colors\nMD5 checksum: df86c09e3a6fca2f363fcfd2af7d9fd5","package":"quickfixsigns.vba","4":"quickfixsigns.vba","src_id":"21529","5":"21529","creation_date":"1393264669","6":"1393264669"},{"0":"2584","vim_version":"7.0","1":"7.0","script_version":"1.01","2":"1.01","version_comment":"- Debug: Removed check for invalid line numbers (e.g. fugitive's Glog uses qfl for file lists only)\n- QuickfixsignsRemoveBuffer(): take a bufnr as argument (not a bufname)\n- Rename QuickfixsignsRemoveBuffer() to s:RemoveBuffer()\n- Call s:PurgeRegister() on BufLeave events (not CursorHold)\n- quickfixsigns#AssertUniqueSigns(): Additional debug message: Empty bsign1\n- s:Redir(): Protect against verbose != 0\n- QuickfixsignsUnique(): Collapse multiple items at one line\n- QuickfixsignsBalloon(): Make sure the balloon text doesn't include \\n if !has('balloon_multiline')\n- s:UpdateLineNumbers(): Don't update line numbers if bufnr <= 0\n- g:quickfixsigns_class_loc: Update on QuickFixCmdPost events\n- QuickfixsignsSelect(): Clear unselected signs\n- QuickfixsignsSet(): match g:quickfixsigns_blacklist_buffer against the base filename\n- QuickfixsignsToggle command\n- s:Redir: Deal with :redir bug\n- Merge branch 'toggle' of https:\/\/github.com\/iNecas\/quickfixsigns_vim\n- Blacklist buffers used by nerdtree & minibufferexplorer (fixes #23).\n- Optional enhancement: use tinykeymap (vimscript #4199) to move between signs\/sign groups (closes #24)\n- quickfixsigns#AssertUniqueSigns(): buffer sign is a dictionary now; use bsign.sign\n- readme: don't mention tlib as dependency (fixes #25)\n- UpdateLineNumbers(): bufnrsigns[sign.id] = sign.lnum\n- b:quickfixsigns_ignore: Ignore sign classes per buffer\n- addon-info\n- allow to customize QFS_VCS_* signs\n- Avoid irrelevant checks when no buffer signs will be displayed\nMD5 checksum: 8dbfd054978cc99491cf9fbe150cd636","3":"- Debug: Removed check for invalid line numbers (e.g. fugitive's Glog uses qfl for file lists only)\n- QuickfixsignsRemoveBuffer(): take a bufnr as argument (not a bufname)\n- Rename QuickfixsignsRemoveBuffer() to s:RemoveBuffer()\n- Call s:PurgeRegister() on BufLeave events (not CursorHold)\n- quickfixsigns#AssertUniqueSigns(): Additional debug message: Empty bsign1\n- s:Redir(): Protect against verbose != 0\n- QuickfixsignsUnique(): Collapse multiple items at one line\n- QuickfixsignsBalloon(): Make sure the balloon text doesn't include \\n if !has('balloon_multiline')\n- s:UpdateLineNumbers(): Don't update line numbers if bufnr <= 0\n- g:quickfixsigns_class_loc: Update on QuickFixCmdPost events\n- QuickfixsignsSelect(): Clear unselected signs\n- QuickfixsignsSet(): match g:quickfixsigns_blacklist_buffer against the base filename\n- QuickfixsignsToggle command\n- s:Redir: Deal with :redir bug\n- Merge branch 'toggle' of https:\/\/github.com\/iNecas\/quickfixsigns_vim\n- Blacklist buffers used by nerdtree & minibufferexplorer (fixes #23).\n- Optional enhancement: use tinykeymap (vimscript #4199) to move between signs\/sign groups (closes #24)\n- quickfixsigns#AssertUniqueSigns(): buffer sign is a dictionary now; use bsign.sign\n- readme: don't mention tlib as dependency (fixes #25)\n- UpdateLineNumbers(): bufnrsigns[sign.id] = sign.lnum\n- b:quickfixsigns_ignore: Ignore sign classes per buffer\n- addon-info\n- allow to customize QFS_VCS_* signs\n- Avoid irrelevant checks when no buffer signs will be displayed\nMD5 checksum: 8dbfd054978cc99491cf9fbe150cd636","package":"quickfixsigns.vba","4":"quickfixsigns.vba","src_id":"19711","5":"19711","creation_date":"1364408992","6":"1364408992"},{"0":"2584","vim_version":"7.0","1":"7.0","script_version":"1.00","2":"1.00","version_comment":"- g:quickfixsigns_debug, quickfixsigns#AssertUniqueSigns()\n- Be smarter at detecting old signs that already exist: s:SignExistsAt() etc.\n- debugging\n- if !exists('g:quickfixsigns_class_rel2')\n- QuickfixsignsSet: clean up\n- QuickfixsignsDisable, QuickfixsignsEnable commands (fixes #12)\n- Don't call QuickfixsignsSet during startup (fixes #13)\n- Use full filenames\n- GetLocList(): call getloclist with the window number\n- quickfixsigns#AssertUniqueSigns: Debug message includes bufnr\n- s:GetScopeTest(): Build query in advance if possible\n- QuickfixsignsRemoveBuffer() on BufDelete events\n- don't allow external diff applications for git\n- Make the highlight group for mark sign user configurable (teranex)\n- Distinguish between buffer-local and global marks\n- Try 1 to fix SetItemId etc.\n- Explicitely set the sign level for most sign classes\n- Make sure item.sign is the actual sign (not a generator function)\n- Events for \"cursor\" class: BufEnter, CursorHoldI?, CursorMovedI?\n- Removed use of always_new\n- vcsdiff: Changed how DEL lines are displayed\n- Remove s:PruneRegister()\n- Debug: quickfixsigns#CheckBuffers()\n- autocmd BufDelete: Forgot the pattern\n- Don't place signs for unloaded buffers\n- call QuickfixsignsRemoveBuffer() also on BufUnload\n- Rename quickfixsigns#CheckBuffers() -> quickfixsigns#AssertNoObsoleteBuffers(register)\n- Update line numbers in order to avoid unnecessarily setting signs\n- s:UpdateLineNumbers(): Debug messages on internal errors\n- g:quickfixsigns#use_relativenumber = v:version >= 703\n- Call cd only for diff command (don't cd vim's dir; fixes #15)\n- Reset ikey after updating line numbers (avoid inconsistent registry entries & duplicate signs)\n- Call QuickfixsignsRemoveBuffer() also on BufWipeout events\n- Call s:PurgeRegister() on CursorHoldI? events\n- s:BufferSigns(): Return empty list if :sign-place returns fewer than 2 lines\n- BufferSigns(): Show debug message only if g:quickfixsigns_debug is true\n- Update signs also in QuickfixsignsBalloon()\n- Update signs also in QuickfixsignsBalloon()\n- QuickfixsignsBalloon(): Don't update signs (undo previous change)\n- Guess vcs type (replaced g:quickfixsigns#vcsdiff#cmds with g:quickfixsigns#vcsdiff#vcs)\n- Search for guess vcs type only once.\n- quickfixsigns#vcsdiff#GetList(): Set last_del also on CHANGEs\n- Consistently use bufloaded\n- UpdateLineNumbers(): Remove old items only when the items match\n- Display \"Invalid lnum\" message only when g:quickfixsigns_debug is set (fixes #16)\n- UpdateLineNumbers(): Avoid duplicate signs\n- Support for bzr\n- quickfixsigns#vcsdiff#GuessType(): Make sure to pick the lower repo directory\n- Run brz diff with -U0\n- Show diffs on first and last line\n- Make svn diff use \"diff -U0\"\n- UpdateLineNumbers(): Use str2nr(), not char2nr()\nMD5 checksum: 00e4af7843f2619e55ee3cee3e614240","3":"- g:quickfixsigns_debug, quickfixsigns#AssertUniqueSigns()\n- Be smarter at detecting old signs that already exist: s:SignExistsAt() etc.\n- debugging\n- if !exists('g:quickfixsigns_class_rel2')\n- QuickfixsignsSet: clean up\n- QuickfixsignsDisable, QuickfixsignsEnable commands (fixes #12)\n- Don't call QuickfixsignsSet during startup (fixes #13)\n- Use full filenames\n- GetLocList(): call getloclist with the window number\n- quickfixsigns#AssertUniqueSigns: Debug message includes bufnr\n- s:GetScopeTest(): Build query in advance if possible\n- QuickfixsignsRemoveBuffer() on BufDelete events\n- don't allow external diff applications for git\n- Make the highlight group for mark sign user configurable (teranex)\n- Distinguish between buffer-local and global marks\n- Try 1 to fix SetItemId etc.\n- Explicitely set the sign level for most sign classes\n- Make sure item.sign is the actual sign (not a generator function)\n- Events for \"cursor\" class: BufEnter, CursorHoldI?, CursorMovedI?\n- Removed use of always_new\n- vcsdiff: Changed how DEL lines are displayed\n- Remove s:PruneRegister()\n- Debug: quickfixsigns#CheckBuffers()\n- autocmd BufDelete: Forgot the pattern\n- Don't place signs for unloaded buffers\n- call QuickfixsignsRemoveBuffer() also on BufUnload\n- Rename quickfixsigns#CheckBuffers() -> quickfixsigns#AssertNoObsoleteBuffers(register)\n- Update line numbers in order to avoid unnecessarily setting signs\n- s:UpdateLineNumbers(): Debug messages on internal errors\n- g:quickfixsigns#use_relativenumber = v:version >= 703\n- Call cd only for diff command (don't cd vim's dir; fixes #15)\n- Reset ikey after updating line numbers (avoid inconsistent registry entries & duplicate signs)\n- Call QuickfixsignsRemoveBuffer() also on BufWipeout events\n- Call s:PurgeRegister() on CursorHoldI? events\n- s:BufferSigns(): Return empty list if :sign-place returns fewer than 2 lines\n- BufferSigns(): Show debug message only if g:quickfixsigns_debug is true\n- Update signs also in QuickfixsignsBalloon()\n- Update signs also in QuickfixsignsBalloon()\n- QuickfixsignsBalloon(): Don't update signs (undo previous change)\n- Guess vcs type (replaced g:quickfixsigns#vcsdiff#cmds with g:quickfixsigns#vcsdiff#vcs)\n- Search for guess vcs type only once.\n- quickfixsigns#vcsdiff#GetList(): Set last_del also on CHANGEs\n- Consistently use bufloaded\n- UpdateLineNumbers(): Remove old items only when the items match\n- Display \"Invalid lnum\" message only when g:quickfixsigns_debug is set (fixes #16)\n- UpdateLineNumbers(): Avoid duplicate signs\n- Support for bzr\n- quickfixsigns#vcsdiff#GuessType(): Make sure to pick the lower repo directory\n- Run brz diff with -U0\n- Show diffs on first and last line\n- Make svn diff use \"diff -U0\"\n- UpdateLineNumbers(): Use str2nr(), not char2nr()\nMD5 checksum: 00e4af7843f2619e55ee3cee3e614240","package":"quickfixsigns.vba","4":"quickfixsigns.vba","src_id":"17377","5":"17377","creation_date":"1328263431","6":"1328263431"},{"0":"2584","vim_version":"7.0","1":"7.0","script_version":"0.14","2":"0.14","version_comment":"- Take more care to run autocommands on the right buffer\n- vcsdiff: always run the vcs command in the buffer's directory\n- make last_run buffer-local\n- make last_run buffer-local\n- QuickfixsignsBalloon: Error after recent change\n- .gitignore\n- Merge branch 'master' of github.com:tomtom\/quickfixsigns_vim\n- Support for git combined diff format\n- Don't run vcsdiff#GetList() in special buffers (reported by rememberthemer)\n- Doc review\n- Do not change directory to current buffer's.\n- Included the doc fixes by blueyed into the doc template.\n- Merge git:\/\/github.com\/blueyed\/quickfixsigns_vim\n- quickfixsigns#vcsdiff#GetList(): Ignore files that are not readable\n- s:PlaceSign(): E706: Variable type mismatch for: item https:\/\/github.com\/tomtom\/quickfixsigns_vim\/issues\/#issue\/7\n- s:SetItemId() returns {} if item.bufnr == -1 (fix issue #7?)\n- quickfixsigns#RelNumbersOnce(): temporarily enable &cul and &cuc\n- s:ClearBuffer(): Check bufnr(def.bufnr) != -1 (issue #9)\n- quickfixsigns#RelNumbersOnce(): Remove highlighting also on TabLeave and WinLeave events\n- Clear*(): duplicate code\n- always_new: avoid wrong optimizations for certain sign classes (e.g. vcsdiff), fixes #10\nMD5 checksum: 542b6deeb5a0505f5bd6cfcaaeca9c57","3":"- Take more care to run autocommands on the right buffer\n- vcsdiff: always run the vcs command in the buffer's directory\n- make last_run buffer-local\n- make last_run buffer-local\n- QuickfixsignsBalloon: Error after recent change\n- .gitignore\n- Merge branch 'master' of github.com:tomtom\/quickfixsigns_vim\n- Support for git combined diff format\n- Don't run vcsdiff#GetList() in special buffers (reported by rememberthemer)\n- Doc review\n- Do not change directory to current buffer's.\n- Included the doc fixes by blueyed into the doc template.\n- Merge git:\/\/github.com\/blueyed\/quickfixsigns_vim\n- quickfixsigns#vcsdiff#GetList(): Ignore files that are not readable\n- s:PlaceSign(): E706: Variable type mismatch for: item https:\/\/github.com\/tomtom\/quickfixsigns_vim\/issues\/#issue\/7\n- s:SetItemId() returns {} if item.bufnr == -1 (fix issue #7?)\n- quickfixsigns#RelNumbersOnce(): temporarily enable &cul and &cuc\n- s:ClearBuffer(): Check bufnr(def.bufnr) != -1 (issue #9)\n- quickfixsigns#RelNumbersOnce(): Remove highlighting also on TabLeave and WinLeave events\n- Clear*(): duplicate code\n- always_new: avoid wrong optimizations for certain sign classes (e.g. vcsdiff), fixes #10\nMD5 checksum: 542b6deeb5a0505f5bd6cfcaaeca9c57","package":"quickfixsigns.vba","4":"quickfixsigns.vba","src_id":"15669","5":"15669","creation_date":"1305744045","6":"1305744045"},{"0":"2584","vim_version":"7.0","1":"7.0","script_version":"0.13","2":"0.13","version_comment":"- QuickfixsignsSelect(): check if g:quickfixsigns_class_{what} exists\nMD5 checksum: 833e1a48f7a3d7460ae29795fb328be4","3":"- QuickfixsignsSelect(): check if g:quickfixsigns_class_{what} exists\nMD5 checksum: 833e1a48f7a3d7460ae29795fb328be4","package":"quickfixsigns.vba","4":"quickfixsigns.vba","src_id":"14643","5":"14643","creation_date":"1293603782","6":"1293603782"},{"0":"2584","vim_version":"7.0","1":"7.0","script_version":"0.12","2":"0.12","version_comment":"- 'test' field; additional test if a sign should be updated (e.g. update _cursor only if lnum has changed)\n- breakpoints (currently vim only)\n- set g:quickfixsigns#vcsdiff#loaded\n- g:quickfixsigns_class_cursor: remove test (interferes with put & delete-like commands)\n- breakpoints: test for a known filetype\n- QuickfixsignsSet(event, ?classes=[])\n- Disable the 'cursor' class by default.\n- Set b:quickfixsigns_last_line\nMD5 checksum: 936abcfd67be7efe52fb0f85481c8665","3":"- 'test' field; additional test if a sign should be updated (e.g. update _cursor only if lnum has changed)\n- breakpoints (currently vim only)\n- set g:quickfixsigns#vcsdiff#loaded\n- g:quickfixsigns_class_cursor: remove test (interferes with put & delete-like commands)\n- breakpoints: test for a known filetype\n- QuickfixsignsSet(event, ?classes=[])\n- Disable the 'cursor' class by default.\n- Set b:quickfixsigns_last_line\nMD5 checksum: 936abcfd67be7efe52fb0f85481c8665","package":"quickfixsigns.vba","4":"quickfixsigns.vba","src_id":"14638","5":"14638","creation_date":"1293566106","6":"1293566106"},{"0":"2584","vim_version":"7.0","1":"7.0","script_version":"0.11","2":"0.11","version_comment":"- Don't check the buffer number in s:ClearBuffer()\n- Improved handling of scopes (vim, buffer)\n- Always include the bufnr in the ID\n- FIX: upper case marks\n- Increase g:quickfixsigns_max = 500\nMD5 checksum: 6fa3a5dd60e62af094f7f7fe41d8695f","3":"- Don't check the buffer number in s:ClearBuffer()\n- Improved handling of scopes (vim, buffer)\n- Always include the bufnr in the ID\n- FIX: upper case marks\n- Increase g:quickfixsigns_max = 500\nMD5 checksum: 6fa3a5dd60e62af094f7f7fe41d8695f","package":"quickfixsigns.vba","4":"quickfixsigns.vba","src_id":"14264","5":"14264","creation_date":"1289810747","6":"1289810747"},{"0":"2584","vim_version":"7.0","1":"7.0","script_version":"0.10","2":"0.10","version_comment":"- quickfixsigns#vcsdiff#GuessType(): use b:git_dir if set (by fugitive)\n- vcsdiff: Support for hg, svn\n- run qfl\/loc checks more also on CursorHold & QuickfixCommandPost events\n- Experimental support for icons (currently assumes that gnome icons 16x16 are ok)\n- Support for sign classes that affect all buffers (all_buffers != 0)\n- Avoid unnecessary updates\n- Simplify handling of ids (construct a global id based on the sign definition)\n- Include icons from the open icon library\n- marks: Don't use own ID generator\n- s:PruneRegister()\n- Don't display icons on windows\nMD5 checksum: 2ba95f98307ea61db8de28d6e60fb61b","3":"- quickfixsigns#vcsdiff#GuessType(): use b:git_dir if set (by fugitive)\n- vcsdiff: Support for hg, svn\n- run qfl\/loc checks more also on CursorHold & QuickfixCommandPost events\n- Experimental support for icons (currently assumes that gnome icons 16x16 are ok)\n- Support for sign classes that affect all buffers (all_buffers != 0)\n- Avoid unnecessary updates\n- Simplify handling of ids (construct a global id based on the sign definition)\n- Include icons from the open icon library\n- marks: Don't use own ID generator\n- s:PruneRegister()\n- Don't display icons on windows\nMD5 checksum: 2ba95f98307ea61db8de28d6e60fb61b","package":"quickfixsigns.vba","4":"quickfixsigns.vba","src_id":"14238","5":"14238","creation_date":"1289499483","6":"1289499483"},{"0":"2584","vim_version":"7.0","1":"7.0","script_version":"0.9","2":"0.9","version_comment":"- Don't require qfl.item.text to be set\r\n- b:noquickfixsigns: If true, disable quickfixsigns for the current buffer (patch by Sergey Khorev; must be set before entering a buffer)\r\n- b:quickfixsigns_ignore_marks: A list of ignored marks (per buffer)\r\n- Support for relative line numbers\r\n- QuickfixsignsSet command\r\n- quickfixsigns#RelNumbersOnce()\r\n- Support for vcs diff (this requires either b:vcs_type or b:VCSCommandVCSType to be set to a supported vcs, e.g. git)\r\n","3":"- Don't require qfl.item.text to be set\r\n- b:noquickfixsigns: If true, disable quickfixsigns for the current buffer (patch by Sergey Khorev; must be set before entering a buffer)\r\n- b:quickfixsigns_ignore_marks: A list of ignored marks (per buffer)\r\n- Support for relative line numbers\r\n- QuickfixsignsSet command\r\n- quickfixsigns#RelNumbersOnce()\r\n- Support for vcs diff (this requires either b:vcs_type or b:VCSCommandVCSType to be set to a supported vcs, e.g. git)\r\n","package":"quickfixsigns.vba","4":"quickfixsigns.vba","src_id":"13975","5":"13975","creation_date":"1286009995","6":"1286009995"},{"0":"2584","vim_version":"7.0","1":"7.0","script_version":"0.5","2":"0.5","version_comment":"- Set balloonexpr only if empty (don't try to be smart)\r\n- Disable CursorMoved(I) events, when &lazyredraw isn't set.\r\n","3":"- Set balloonexpr only if empty (don't try to be smart)\r\n- Disable CursorMoved(I) events, when &lazyredraw isn't set.\r\n","package":"quickfixsigns.vba.gz","4":"quickfixsigns.vba.gz","src_id":"11434","5":"11434","creation_date":"1253941367","6":"1253941367"},{"0":"2584","vim_version":"7.0","1":"7.0","script_version":"0.4","2":"0.4","version_comment":"- FIX: Error when g:quickfixsigns_marks = [] (thanks Ingo Karkat)\r\n- s:ClearBuffer: removed old code\r\n- QuickfixsignsMarks(state): Switch the display of marks on\/off.\r\n","3":"- FIX: Error when g:quickfixsigns_marks = [] (thanks Ingo Karkat)\r\n- s:ClearBuffer: removed old code\r\n- QuickfixsignsMarks(state): Switch the display of marks on\/off.\r\n","package":"quickfixsigns.vba.gz","4":"quickfixsigns.vba.gz","src_id":"10313","5":"10313","creation_date":"1238346144","6":"1238346144"},{"0":"2584","vim_version":"7.0","1":"7.0","script_version":"0.3","2":"0.3","version_comment":"- Old signs weren't always removed\r\n- Avoid \"flicker\" etc.\r\n- g:quickfixsigns_max: Don't display signs if the list is longer than n items.\r\n\r\nIncompatible changes:\r\n- Removed g:quickfixsigns_show_marks variable\r\n- g:quickfixsigns_marks: Marks that should be used for signs\r\n- g:quickfixsigns_lists: event field is a list\r\n- g:quickfixsigns_lists: timeout field: don't re-display this list more often than n seconds\r\n","3":"- Old signs weren't always removed\r\n- Avoid \"flicker\" etc.\r\n- g:quickfixsigns_max: Don't display signs if the list is longer than n items.\r\n\r\nIncompatible changes:\r\n- Removed g:quickfixsigns_show_marks variable\r\n- g:quickfixsigns_marks: Marks that should be used for signs\r\n- g:quickfixsigns_lists: event field is a list\r\n- g:quickfixsigns_lists: timeout field: don't re-display this list more often than n seconds\r\n","package":"quickfixsigns.vba.gz","4":"quickfixsigns.vba.gz","src_id":"10312","5":"10312","creation_date":"1238319131","6":"1238319131"},{"0":"2584","vim_version":"7.0","1":"7.0","script_version":"0.2","2":"0.2","version_comment":"GLVS, minor fix","3":"GLVS, minor fix","package":"quickfixsigns.vba.gz","4":"quickfixsigns.vba.gz","src_id":"10233","5":"10233","creation_date":"1237291124","6":"1237291124"}]},"2583":{"script_id":"2583","0":"2583","script_name":"popup_it","1":"popup_it","script_type":"utility","2":"utility","summary":"a easy config auto complete popup","3":"a easy config auto complete popup","description":" a easy config auto complete popup plugin\r\n\r\n\"             You can put a user auto popup table in you .vimrc like this:\r\n\"             let useTable[filetype] = [[auto_exec_complete1, key_word], ...]\r\n\"\r\n\"             This is a example for c file.\r\n\"             let usrTable = {}\r\n\"             let usrTable[\"c\"] = [\r\n\"                         \\ [\"\\<c-x>\\<c-o>\",'\\k.','\\k->',\r\n\"                         \\ 'gtk_\\k\\{2,\\}','GTK_\\k\\{1,\\}','Gtk\\k\\{1,\\}',\r\n\"                         \\ 'g_\\k\\{2,\\}', 'G_\\k\\{1,\\}'],\r\n\"                         \\ [\"\\<c-n>\",'\\k\\{3,\\}'],\r\n\"                         \\]\r\n\"             When you type . -> gtk_(>2char) GTK_(>1char) Gtk_(>1char) \r\n\"             g_(>2char) G_(>1char) than <c-x><c-o> exec.\r\n\"             When you type >3char <c-n> exec.\r\n\r\nBlow is default auto popup table\r\n\"defTable: {{{1\r\nlet s:defTable = {}\r\nlet s:defTable[\"*\"]    = [\r\n            \\ [\"\\<c-n>\",'\\k\\{3,\\}']\r\n            \\]\r\nlet s:defTable[\"c\"]    = [\r\n            \\ [\"\\<c-x>\\<c-o>\",'\\k.','\\k->'],\r\n            \\ [\"\\<c-n>\",'\\k\\{3,\\}'],\r\n            \\]\r\nlet s:defTable[\"tex\"]  = [\r\n            \\ [\"\\<c-n>\",'\\\\\\k\\{2,\\}','\\([\\|{\\)\\.\\*\\k\\{2,\\}'],\r\n            \\]\r\nlet s:defTable[\"html\"] = [\r\n            \\ [\"\\<c-x>\\<c-o>\",'<','<\/','<\\.\\*\\s\\+\\k','<\\.\\*\\k\\+\\s\\*=\"\\k'],\r\n            \\]\r\n\r\n","4":" a easy config auto complete popup plugin\r\n\r\n\"             You can put a user auto popup table in you .vimrc like this:\r\n\"             let useTable[filetype] = [[auto_exec_complete1, key_word], ...]\r\n\"\r\n\"             This is a example for c file.\r\n\"             let usrTable = {}\r\n\"             let usrTable[\"c\"] = [\r\n\"                         \\ [\"\\<c-x>\\<c-o>\",'\\k.','\\k->',\r\n\"                         \\ 'gtk_\\k\\{2,\\}','GTK_\\k\\{1,\\}','Gtk\\k\\{1,\\}',\r\n\"                         \\ 'g_\\k\\{2,\\}', 'G_\\k\\{1,\\}'],\r\n\"                         \\ [\"\\<c-n>\",'\\k\\{3,\\}'],\r\n\"                         \\]\r\n\"             When you type . -> gtk_(>2char) GTK_(>1char) Gtk_(>1char) \r\n\"             g_(>2char) G_(>1char) than <c-x><c-o> exec.\r\n\"             When you type >3char <c-n> exec.\r\n\r\nBlow is default auto popup table\r\n\"defTable: {{{1\r\nlet s:defTable = {}\r\nlet s:defTable[\"*\"]    = [\r\n            \\ [\"\\<c-n>\",'\\k\\{3,\\}']\r\n            \\]\r\nlet s:defTable[\"c\"]    = [\r\n            \\ [\"\\<c-x>\\<c-o>\",'\\k.','\\k->'],\r\n            \\ [\"\\<c-n>\",'\\k\\{3,\\}'],\r\n            \\]\r\nlet s:defTable[\"tex\"]  = [\r\n            \\ [\"\\<c-n>\",'\\\\\\k\\{2,\\}','\\([\\|{\\)\\.\\*\\k\\{2,\\}'],\r\n            \\]\r\nlet s:defTable[\"html\"] = [\r\n            \\ [\"\\<c-x>\\<c-o>\",'<','<\/','<\\.\\*\\s\\+\\k','<\\.\\*\\k\\+\\s\\*=\"\\k'],\r\n            \\]\r\n\r\n","install_details":"Put this file in your VIM plugin dir  \r\n","5":"Put this file in your VIM plugin dir  \r\n","first_name":"777","6":"777","last_name":"us","7":"us","releases":[{"0":"2583","vim_version":"6.0","1":"6.0","script_version":"01","2":"01","version_comment":"Initial upload","3":"Initial upload","package":"popup_it.vim","4":"popup_it.vim","src_id":"10206","5":"10206","creation_date":"1237038281","6":"1237038281"}]},"2582":{"script_id":"2582","0":"2582","script_name":"blogit.vim","1":"blogit.vim","script_type":"utility","2":"utility","summary":"A\u00c2\u00a0script to blog on wordpress","3":"A\u00c2\u00a0script to blog on wordpress","description":"This script allows you to list, edit, write and publish articles on Wordpress. It uses the XML-RPC API and provides the following commands:\r\n\r\n\":Blogit ls [blog_name]\"\r\n Lists all articles in the blog\r\n\":Blogit new [blog_name]\"\r\n Opens page to write new article\r\n\":Blogit edit <id> [blog_name]\"\r\n Opens the article <id> for edition\r\n\":Blogit page <id> [blog_name]\"\r\n  Edit a blog page\r\n\":Blogit commit\"\r\n Saves the article to the blog\r\n\":Blogit push\"\r\n Publish article\r\n\":Blogit unpush\"\r\n Unpublish article\r\n\":Blogit rm <id>\"\r\n Remove an article\r\n\":Blogit tags\"\r\n  Show tags and categories list\r\n\":Blogit this\"\r\n  Create a blog post from current buffer\r\n\":Blogit preview\"\r\n  Preview current post locally\r\n\":Blogit help\"\r\n Display help\r\n\r\nEdited articles are displayed like mails.\r\n\r\nWebsite: http:\/\/symlink.me\/wiki\/blogit","4":"This script allows you to list, edit, write and publish articles on Wordpress. It uses the XML-RPC API and provides the following commands:\r\n\r\n\":Blogit ls [blog_name]\"\r\n Lists all articles in the blog\r\n\":Blogit new [blog_name]\"\r\n Opens page to write new article\r\n\":Blogit edit <id> [blog_name]\"\r\n Opens the article <id> for edition\r\n\":Blogit page <id> [blog_name]\"\r\n  Edit a blog page\r\n\":Blogit commit\"\r\n Saves the article to the blog\r\n\":Blogit push\"\r\n Publish article\r\n\":Blogit unpush\"\r\n Unpublish article\r\n\":Blogit rm <id>\"\r\n Remove an article\r\n\":Blogit tags\"\r\n  Show tags and categories list\r\n\":Blogit this\"\r\n  Create a blog post from current buffer\r\n\":Blogit preview\"\r\n  Preview current post locally\r\n\":Blogit help\"\r\n Display help\r\n\r\nEdited articles are displayed like mails.\r\n\r\nWebsite: http:\/\/symlink.me\/wiki\/blogit","install_details":"Get package and uncompress it in your ~\/.vim directory. \r\n\r\nCreate a file called passwords.vim somewhere in your 'runtimepath'\r\n(preferred location is \"~\/.vim\/\"). Don't forget to set the permissions so\r\nonly you can read it. This file should include:\r\n\r\n    let blogit_username='Your blog user name'\r\n    let blogit_password='Your blog password. Not the API-key.'\r\n    let blogit_url='https:\/\/your.path.to\/xmlrpc.php'\r\n\r\nIn addition you can set these settings in your vimrc:\r\n\r\n    let blogit_unformat='pandoc --from=html --to=rst --reference-links'\r\n    let blogit_format='pandoc --from=rst --to=html --no-wrap'\r\n\r\nThe blogit_format and blogit_unformat each contain a shell command to\r\nfilter the blog entry text (no meta data) before a commit and after an\r\nedit, respectively. In the example we use pandoc[1] to edit the blog in\r\nreStructuredText[2].\r\n\r\nIf you have multible blogs replace 'blogit' in 'blogit_username' etc. by a\r\nname of your choice (e.g. 'your_blog_name') and use:\r\n\r\n    let blog_name='your_blog_name'\r\nor\r\n    let b:blog_name='your_blog_name'\r\n\r\nto switch which is used by default. If a blog post\/comment\/list is open in\r\nthe current buffer that is used instead. To explicitly select which blog\r\nshould be used with the commands ls, new, this and edit add your_blog_name\r\nas and aditional argument, e.g.:\r\n\r\n    Blogit edit 42 your_blog_name","5":"Get package and uncompress it in your ~\/.vim directory. \r\n\r\nCreate a file called passwords.vim somewhere in your 'runtimepath'\r\n(preferred location is \"~\/.vim\/\"). Don't forget to set the permissions so\r\nonly you can read it. This file should include:\r\n\r\n    let blogit_username='Your blog user name'\r\n    let blogit_password='Your blog password. Not the API-key.'\r\n    let blogit_url='https:\/\/your.path.to\/xmlrpc.php'\r\n\r\nIn addition you can set these settings in your vimrc:\r\n\r\n    let blogit_unformat='pandoc --from=html --to=rst --reference-links'\r\n    let blogit_format='pandoc --from=rst --to=html --no-wrap'\r\n\r\nThe blogit_format and blogit_unformat each contain a shell command to\r\nfilter the blog entry text (no meta data) before a commit and after an\r\nedit, respectively. In the example we use pandoc[1] to edit the blog in\r\nreStructuredText[2].\r\n\r\nIf you have multible blogs replace 'blogit' in 'blogit_username' etc. by a\r\nname of your choice (e.g. 'your_blog_name') and use:\r\n\r\n    let blog_name='your_blog_name'\r\nor\r\n    let b:blog_name='your_blog_name'\r\n\r\nto switch which is used by default. If a blog post\/comment\/list is open in\r\nthe current buffer that is used instead. To explicitly select which blog\r\nshould be used with the commands ls, new, this and edit add your_blog_name\r\nas and aditional argument, e.g.:\r\n\r\n    Blogit edit 42 your_blog_name","first_name":"Romain","6":"Romain","last_name":"Bignon","7":"Bignon","releases":[{"0":"2582","vim_version":"7.0","1":"7.0","script_version":"1.4.3","2":"1.4.3","version_comment":"* Added infrastructure for acceptance tests;\r\n* Added gettext i18n;\r\n* Fixed pep8 compliance;\r\n* Fixed setting date on \":Blogit commit\" and \"push\";\r\n* Fixed time in blog posts;\r\n* Improved help file.","3":"* Added infrastructure for acceptance tests;\r\n* Added gettext i18n;\r\n* Fixed pep8 compliance;\r\n* Fixed setting date on \":Blogit commit\" and \"push\";\r\n* Fixed time in blog posts;\r\n* Improved help file.","package":"blogit-1.4.3.tar.bz2","4":"blogit-1.4.3.tar.bz2","src_id":"12000","5":"12000","creation_date":"1262424907","6":"1262424907"},{"0":"2582","vim_version":"7.0","1":"7.0","script_version":"1.4.2","2":"1.4.2","version_comment":"Minor bugfixes:\r\n\r\n* Fixed encoding issues;\r\n* Fixed omnicomplete issues.","3":"Minor bugfixes:\r\n\r\n* Fixed encoding issues;\r\n* Fixed omnicomplete issues.","package":"blogit-1.4.2.tar.bz2","4":"blogit-1.4.2.tar.bz2","src_id":"11608","5":"11608","creation_date":"1256743335","6":"1256743335"},{"0":"2582","vim_version":"7.0","1":"7.0","script_version":"1.4.1","2":"1.4.1","version_comment":"This minor release fixes some bugs:\r\n\r\n* Implemented sending new pages;\r\n* Implemented (un)pushing of pages;\r\n* Fixed dates.","3":"This minor release fixes some bugs:\r\n\r\n* Implemented sending new pages;\r\n* Implemented (un)pushing of pages;\r\n* Fixed dates.","package":"blogit-1.4.1.tar.bz2","4":"blogit-1.4.1.tar.bz2","src_id":"11408","5":"11408","creation_date":"1253363378","6":"1253363378"},{"0":"2582","vim_version":"7.0","1":"7.0","script_version":"1.4","2":"1.4","version_comment":"This is probably the final stable release of the 1.x branch. Here is changelog:\r\n\r\n* Introduced the *Blogit page* command to edit a page content (closes #134);\r\n* Ability to give the blog name to edit\/ls\/new\/this commands;\r\n* Fixed non-ascii problem with datetimes;\r\n* Fixed \"variables not updated when switching blogs\" (closes #144);\r\n* Several other minors fixes;\r\n* Added vim documentation file for blogit.\r\n* Code refactoring;\r\n* Better unitary tests system.\r\n\r\nReally thanks to Adam who has still done a lot of work.\r\n","3":"This is probably the final stable release of the 1.x branch. Here is changelog:\r\n\r\n* Introduced the *Blogit page* command to edit a page content (closes #134);\r\n* Ability to give the blog name to edit\/ls\/new\/this commands;\r\n* Fixed non-ascii problem with datetimes;\r\n* Fixed \"variables not updated when switching blogs\" (closes #144);\r\n* Several other minors fixes;\r\n* Added vim documentation file for blogit.\r\n* Code refactoring;\r\n* Better unitary tests system.\r\n\r\nReally thanks to Adam who has still done a lot of work.\r\n","package":"blogit-1.4.tar.bz2","4":"blogit-1.4.tar.bz2","src_id":"11355","5":"11355","creation_date":"1252602256","6":"1252602256"},{"0":"2582","vim_version":"7.0","1":"7.0","script_version":"1.3","2":"1.3","version_comment":"This release is mostly a bugfix release:\r\n\r\n* Finished up displaying comments;\r\n* Fixed order of comments;\r\n* Fixed comment count;\r\n* Support shortening of Blogit-commands;\r\n* Update comments via \":Blogit commit\";\r\n* Fixed using multible buffers;\r\n* Added command \"preview\";\r\n* Code cleanup.","3":"This release is mostly a bugfix release:\r\n\r\n* Finished up displaying comments;\r\n* Fixed order of comments;\r\n* Fixed comment count;\r\n* Support shortening of Blogit-commands;\r\n* Update comments via \":Blogit commit\";\r\n* Fixed using multible buffers;\r\n* Added command \"preview\";\r\n* Code cleanup.","package":"blogit-1.3.tar.bz2","4":"blogit-1.3.tar.bz2","src_id":"11195","5":"11195","creation_date":"1250416231","6":"1250416231"},{"0":"2582","vim_version":"7.0","1":"7.0","script_version":"1.2","2":"1.2","version_comment":"This new release of blogit.vim introduces this new features:\r\n\r\n* Added the \u00e2\u0080\u009c:Blogit this\u00e2\u0080\u009d command to create a blog post from the current vim buffer;\r\n* The \u00e2\u0080\u009c:Blogit categories\u00e2\u0080\u009d command is merged into the \u00e2\u0080\u009c:Blogit tags\u00e2\u0080\u009d command;\r\n* Comments can be displayed with \u00e2\u0080\u009cgf\u00e2\u0080\u009d on \u00e2\u0080\u009cStatus\u00e2\u0080\u009d,\r\n\r\nThere is also some minor (or less minors) bugfixes.\r\n\r\nThanks to Adam Schmalhofer for contributing.","3":"This new release of blogit.vim introduces this new features:\r\n\r\n* Added the \u00e2\u0080\u009c:Blogit this\u00e2\u0080\u009d command to create a blog post from the current vim buffer;\r\n* The \u00e2\u0080\u009c:Blogit categories\u00e2\u0080\u009d command is merged into the \u00e2\u0080\u009c:Blogit tags\u00e2\u0080\u009d command;\r\n* Comments can be displayed with \u00e2\u0080\u009cgf\u00e2\u0080\u009d on \u00e2\u0080\u009cStatus\u00e2\u0080\u009d,\r\n\r\nThere is also some minor (or less minors) bugfixes.\r\n\r\nThanks to Adam Schmalhofer for contributing.","package":"blogit-1.2.tar.bz2","4":"blogit-1.2.tar.bz2","src_id":"11033","5":"11033","creation_date":"1247948158","6":"1247948158"},{"0":"2582","vim_version":"6.0","1":"6.0","script_version":"1.1","2":"1.1","version_comment":"The blogit.vim 1.1 release's changes are: \r\n* Use a separated file to set blogit.vim settings. \r\n* Use of filter to get\/post text. Default is pandoc, to display text as ReST. \r\n* Multi-blogs support. \r\n* Localized timestamps. \r\n* Date\/times are displayed in users preferred time format. \r\n* Omni-complete categories and tags. \r\n \r\nThere are also some bug fixes, and code cleanup. \r\n \r\nThanks to Adam Schmalhofer for his patches.","3":"The blogit.vim 1.1 release's changes are: \r\n* Use a separated file to set blogit.vim settings. \r\n* Use of filter to get\/post text. Default is pandoc, to display text as ReST. \r\n* Multi-blogs support. \r\n* Localized timestamps. \r\n* Date\/times are displayed in users preferred time format. \r\n* Omni-complete categories and tags. \r\n \r\nThere are also some bug fixes, and code cleanup. \r\n \r\nThanks to Adam Schmalhofer for his patches.","package":"blogit-1.1.tar.bz2","4":"blogit-1.1.tar.bz2","src_id":"10886","5":"10886","creation_date":"1245595149","6":"1245595149"},{"0":"2582","vim_version":"7.0","1":"7.0","script_version":"1.0.1","2":"1.0.1","version_comment":"The blogit.vim 1.0.1 release fixes these issues:\r\n* option to disable tags (which are a wordpress plugin)\r\n* datetime issues (datetime is now UTC)","3":"The blogit.vim 1.0.1 release fixes these issues:\r\n* option to disable tags (which are a wordpress plugin)\r\n* datetime issues (datetime is now UTC)","package":"blogit-1.0.1.tar.bz2","4":"blogit-1.0.1.tar.bz2","src_id":"10382","5":"10382","creation_date":"1239445097","6":"1239445097"},{"0":"2582","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial version.","3":"Initial version.","package":"blogit-1.0.tar.bz2","4":"blogit-1.0.tar.bz2","src_id":"10381","5":"10381","creation_date":"1239433605","6":"1239433605"}]},"2581":{"script_id":"2581","0":"2581","script_name":"Fdgrep","1":"Fdgrep","script_type":"utility","2":"utility","summary":"Find a function declaration matching a given pattern","3":"Find a function declaration matching a given pattern","description":"This is a script that uses a grep-like regex to find a function declaration in the current file\/buffer that matches a given regular expression.\r\n\r\nIf called like: Fdgrep(-1) the function will ask the user for a pattern to search for.  It will then search the current file buffer for function declarations that contain the given pattern.  If no pattern is given, it will prompt the user again.  If no pattern is given the second time, it will do a search that should match any function declaration.\r\n\r\nIf called like: Fdgrep(0) the function will ask search for the last-used pattern (like hitting n after a normal search). If there is no last-used pattern in memory it will prompt the user for a pattern, which can be ignored as stated above to match any function declaration.\r\n\r\nThis will work with most C, C++, Objective-C, and Python function declarations that I have seen in my own code or at my job (we have a _very_ large C codebase).","4":"This is a script that uses a grep-like regex to find a function declaration in the current file\/buffer that matches a given regular expression.\r\n\r\nIf called like: Fdgrep(-1) the function will ask the user for a pattern to search for.  It will then search the current file buffer for function declarations that contain the given pattern.  If no pattern is given, it will prompt the user again.  If no pattern is given the second time, it will do a search that should match any function declaration.\r\n\r\nIf called like: Fdgrep(0) the function will ask search for the last-used pattern (like hitting n after a normal search). If there is no last-used pattern in memory it will prompt the user for a pattern, which can be ignored as stated above to match any function declaration.\r\n\r\nThis will work with most C, C++, Objective-C, and Python function declarations that I have seen in my own code or at my job (we have a _very_ large C codebase).","install_details":"place the file in your plugin directory.\r\n\r\nI use mappings in my .vimrc to make it easier to use, like so:\r\n\r\nmap \\fdg :call Fdgrep(-1)<CR>  \" calls Fdgrep with -1 to get a pattern prompt\r\nmap \\fdn :call Fdgrep(0)<CR> \" calls Fdgrep with 0 to use last pattern","5":"place the file in your plugin directory.\r\n\r\nI use mappings in my .vimrc to make it easier to use, like so:\r\n\r\nmap \\fdg :call Fdgrep(-1)<CR>  \" calls Fdgrep with -1 to get a pattern prompt\r\nmap \\fdn :call Fdgrep(0)<CR> \" calls Fdgrep with 0 to use last pattern","first_name":"Alex","6":"Alex","last_name":"Esplin","7":"Esplin","releases":[{"0":"2581","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"fdgrep.vim","4":"fdgrep.vim","src_id":"10195","5":"10195","creation_date":"1236927014","6":"1236927014"}]},"2580":{"script_id":"2580","0":"2580","script_name":"spec.vim","1":"spec.vim","script_type":"utility","2":"utility","summary":"Behaviour-driven design\/testing for VIM script","3":"Behaviour-driven design\/testing for VIM script","description":"This plugin provides a small set of commands to facilitate \r\nbehaviour-driven design of vim plugins. It basically consists of two \r\nparts:\r\n\r\n    spec   ... BDD-related commands\r\n    should ... Convenience functions for testing\r\n\r\nAccording to BDD theory, you are supposed to write a specification first \r\nand then make the code fulfill that specification. If you don't believe \r\nin BDD, you could also think of spec.vim as a more convenient approach \r\nto unit testing.\r\n\r\nAn example specification could look like this:\r\n\r\n    SpecBegin 'title': 'Foo', 'sfile': 'autoload\/foo.vim'\r\n\r\n    It should add numbers.\r\n    Should be equal foo#Add(1, 2), 3\r\n    \r\n    It should not add values of incompatible types.\r\n    Should throw something 'foo#Add(\"1\", 2)'\r\n\r\nSpecification scripts basically are normal vim scripts but must be run \r\nby the |:Spec| command.\r\n\r\n    :Spec[!] [PATH]\r\n        Run one or more specification files.\r\n        PATH can be either a file or a directory.\r\n\r\nEach specification file should contain a :SpecBegin command that defines \r\nthe title, and optionally the script context, before\/after commands, the \r\ncontents of a scratch buffer, option sets etc.\r\n\r\n    :SpecBegin [ARGUMENTS AS INNER DICTIONNARY]\r\n        Establish the environment for the current specification.\r\n        Known keys for ARGUMENTS:\r\n        \r\n          title   ... The test's title.\r\n          file    ... The script context.\r\n          before  ... Code to be run before each test\r\n          after   ... Code to be run after each test\r\n          scratch ... Run spec in scratch buffer\r\n          cleanup ... A list of function names that will be removed\r\n          options ... Run the spec against different option sets\r\n\r\nExamples:\r\nhttp:\/\/github.com\/tomtom\/vimtlib\/tree\/master\/spec\/\r\n","4":"This plugin provides a small set of commands to facilitate \r\nbehaviour-driven design of vim plugins. It basically consists of two \r\nparts:\r\n\r\n    spec   ... BDD-related commands\r\n    should ... Convenience functions for testing\r\n\r\nAccording to BDD theory, you are supposed to write a specification first \r\nand then make the code fulfill that specification. If you don't believe \r\nin BDD, you could also think of spec.vim as a more convenient approach \r\nto unit testing.\r\n\r\nAn example specification could look like this:\r\n\r\n    SpecBegin 'title': 'Foo', 'sfile': 'autoload\/foo.vim'\r\n\r\n    It should add numbers.\r\n    Should be equal foo#Add(1, 2), 3\r\n    \r\n    It should not add values of incompatible types.\r\n    Should throw something 'foo#Add(\"1\", 2)'\r\n\r\nSpecification scripts basically are normal vim scripts but must be run \r\nby the |:Spec| command.\r\n\r\n    :Spec[!] [PATH]\r\n        Run one or more specification files.\r\n        PATH can be either a file or a directory.\r\n\r\nEach specification file should contain a :SpecBegin command that defines \r\nthe title, and optionally the script context, before\/after commands, the \r\ncontents of a scratch buffer, option sets etc.\r\n\r\n    :SpecBegin [ARGUMENTS AS INNER DICTIONNARY]\r\n        Establish the environment for the current specification.\r\n        Known keys for ARGUMENTS:\r\n        \r\n          title   ... The test's title.\r\n          file    ... The script context.\r\n          before  ... Code to be run before each test\r\n          after   ... Code to be run after each test\r\n          scratch ... Run spec in scratch buffer\r\n          cleanup ... A list of function names that will be removed\r\n          options ... Run the spec against different option sets\r\n\r\nExamples:\r\nhttp:\/\/github.com\/tomtom\/vimtlib\/tree\/master\/spec\/\r\n","install_details":"Edit the vba file and type: >\r\n\r\n    :so %\r\n\r\nSee :help vimball for details. If you have difficulties or use vim 7.0, \r\nplease make sure, you have the current version of vimball\r\n(vimscript #1502) installed or update your runtime.\r\n\r\nOptional: Some \"should\"-functions require tlib (vimscript #1863) to be installed.\r\n\r\nAlso available via git\r\nhttp:\/\/github.com\/tomtom\/spec_vim","5":"Edit the vba file and type: >\r\n\r\n    :so %\r\n\r\nSee :help vimball for details. If you have difficulties or use vim 7.0, \r\nplease make sure, you have the current version of vimball\r\n(vimscript #1502) installed or update your runtime.\r\n\r\nOptional: Some \"should\"-functions require tlib (vimscript #1863) to be installed.\r\n\r\nAlso available via git\r\nhttp:\/\/github.com\/tomtom\/spec_vim","first_name":"Tom","6":"Tom","last_name":"Link","7":"Link","releases":[{"0":"2580","vim_version":"7.0","1":"7.0","script_version":"0.2","2":"0.2","version_comment":"- Display a message after having run all specs\r\n- Raise an error when :SpecBegin is not called in a spec context (i.e. via the :Spec command)\r\n","3":"- Display a message after having run all specs\r\n- Raise an error when :SpecBegin is not called in a spec context (i.e. via the :Spec command)\r\n","package":"spec.vba","4":"spec.vba","src_id":"12615","5":"12615","creation_date":"1268461317","6":"1268461317"},{"0":"2580","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"spec.vba.gz","4":"spec.vba.gz","src_id":"10173","5":"10173","creation_date":"1236778972","6":"1236778972"}]},"2579":{"script_id":"2579","0":"2579","script_name":"Session manager","1":"Session manager","script_type":"utility","2":"utility","summary":"Plugin for easy session management","3":"Plugin for easy session management","description":"Usage:\r\n\r\n  :call SessionManagerToggle() - open session manager\r\n      \r\n <Return> - load selected session file\r\n        o - load selected session file\r\n        s - save current session\r\n        n - create new session\r\n        d - delete selected session\r\n        q - close session manager","4":"Usage:\r\n\r\n  :call SessionManagerToggle() - open session manager\r\n      \r\n <Return> - load selected session file\r\n        o - load selected session file\r\n        s - save current session\r\n        n - create new session\r\n        d - delete selected session\r\n        q - close session manager","install_details":"Just put plugin file into your ~\/.vim\/plugin directory and create ~\/.vim_sessions directory.","5":"Just put plugin file into your ~\/.vim\/plugin directory and create ~\/.vim_sessions directory.","first_name":"Piotr","6":"Piotr","last_name":"Husiatynski","7":"Husiatynski","releases":[{"0":"2579","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"session_manager.vim","4":"session_manager.vim","src_id":"10165","5":"10165","creation_date":"1236720945","6":"1236720945"}]},"2578":{"script_id":"2578","0":"2578","script_name":"lint.vim","1":"lint.vim","script_type":"utility","2":"utility","summary":"JSHint integration with quickfix window","3":"JSHint integration with quickfix window","description":"Facilitates tight integration between JSHint and Vim.\r\n\r\nJavaScript files are automatically passed through JSHint when a buffer is saved, placing any warnings in the quickfix window for easy navigation to the source of the warning. To achieve acceptable performance, Google's V8 Engine is used for JavaScript execution.\r\n\r\nThis project is maintained on github: https:\/\/github.com\/joestelmach\/lint.vim.","4":"Facilitates tight integration between JSHint and Vim.\r\n\r\nJavaScript files are automatically passed through JSHint when a buffer is saved, placing any warnings in the quickfix window for easy navigation to the source of the warning. To achieve acceptable performance, Google's V8 Engine is used for JavaScript execution.\r\n\r\nThis project is maintained on github: https:\/\/github.com\/joestelmach\/lint.vim.","install_details":"The d8 executable must be found in your classpath.  See: http:\/\/code.google.com\/p\/v8\/","5":"The d8 executable must be found in your classpath.  See: http:\/\/code.google.com\/p\/v8\/","first_name":"Joe","6":"Joe","last_name":"Stelmach","7":"Stelmach","releases":[{"0":"2578","vim_version":"7.0","1":"7.0","script_version":"0.3","2":"0.3","version_comment":"switched to JSHint + V8","3":"switched to JSHint + V8","package":"lint.vim.zip","4":"lint.vim.zip","src_id":"18001","5":"18001","creation_date":"1337519262","6":"1337519262"},{"0":"2578","vim_version":"6.0","1":"6.0","script_version":"0.2","2":"0.2","version_comment":"* Explicitly specifying the errorformat (Thanks Jonathan del Strother)\r\n* Ability to disable the highlight color using \"unlet jslint_highlight_color\" (Thanks Gregory Mullegger)\r\n* Fixed bug that would close an unrelated quickfix window when saving.","3":"* Explicitly specifying the errorformat (Thanks Jonathan del Strother)\r\n* Ability to disable the highlight color using \"unlet jslint_highlight_color\" (Thanks Gregory Mullegger)\r\n* Fixed bug that would close an unrelated quickfix window when saving.","package":"javaScriptLint.vim","4":"javaScriptLint.vim","src_id":"10540","5":"10540","creation_date":"1241578413","6":"1241578413"},{"0":"2578","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"javaScriptLint.vim","4":"javaScriptLint.vim","src_id":"10158","5":"10158","creation_date":"1236652749","6":"1236652749"}]},"2577":{"script_id":"2577","0":"2577","script_name":"summerfruit256.vim","1":"summerfruit256.vim","script_type":"color scheme","2":"color scheme","summary":"summerfruit color scheme in 256 colors","3":"summerfruit color scheme in 256 colors","description":"A 88\/256 color version of Armin Ronacher's summerfruit color scheme (vimscript #1872).  I used Henry So Jr.'s color approximation (vimscript #1243) for the color conversion.\r\n\r\nYou can find a screenshot here: http:\/\/blisqu.wordpress.com\/2012\/02\/02\/summerfruit256-light-vim-color-scheme-in-256-colors\/","4":"A 88\/256 color version of Armin Ronacher's summerfruit color scheme (vimscript #1872).  I used Henry So Jr.'s color approximation (vimscript #1243) for the color conversion.\r\n\r\nYou can find a screenshot here: http:\/\/blisqu.wordpress.com\/2012\/02\/02\/summerfruit256-light-vim-color-scheme-in-256-colors\/","install_details":"1. copy to ~\/.vim\/colors (or $VIM\/vimfiles\/colors on Windows)\r\n2. add the following to your vimrc:\r\nset t_Co=256  \" make use of 256 terminal colors\r\ncolor summerfruit256","5":"1. copy to ~\/.vim\/colors (or $VIM\/vimfiles\/colors on Windows)\r\n2. add the following to your vimrc:\r\nset t_Co=256  \" make use of 256 terminal colors\r\ncolor summerfruit256","first_name":"Martin","6":"Martin","last_name":"Baeuml","7":"Baeuml","releases":[{"0":"2577","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"summerfruit256.vim","4":"summerfruit256.vim","src_id":"10153","5":"10153","creation_date":"1236624202","6":"1236624202"}]},"2576":{"script_id":"2576","0":"2576","script_name":"WinMove","1":"WinMove","script_type":"utility","2":"utility","summary":"Move your gVim","3":"Move your gVim","description":"Usage:\r\n  MAPPING:\r\n      <Up>        move your gVim up.\r\n      <Right>    move your gVim right.\r\n      <Down>   move your gVim down.\r\n      <Left>      move your gVim left.\r\n\r\n  GLOBAL VARIABLES:\r\n      g:wm_move_up (default:'<Up>')\r\n          if empty string, no mapping is defined.\r\n\r\n      g:wm_move_right (default:'<Right>')\r\n          if empty string, no mapping is defined.\r\n\r\n      g:wm_move_down (default:'<Down>')\r\n          if empty string, no mapping is defined.\r\n\r\n      g:wm_move_left (default:'<Left>')\r\n          if empty string, no mapping is defined.\r\n\r\n      g:wm_move_x (default:20)\r\n          gVim use this when move left or right.\r\n\r\n      g:wm_move_y (default:15)\r\n          gVim use this when move up or down.\r\n","4":"Usage:\r\n  MAPPING:\r\n      <Up>        move your gVim up.\r\n      <Right>    move your gVim right.\r\n      <Down>   move your gVim down.\r\n      <Left>      move your gVim left.\r\n\r\n  GLOBAL VARIABLES:\r\n      g:wm_move_up (default:'<Up>')\r\n          if empty string, no mapping is defined.\r\n\r\n      g:wm_move_right (default:'<Right>')\r\n          if empty string, no mapping is defined.\r\n\r\n      g:wm_move_down (default:'<Down>')\r\n          if empty string, no mapping is defined.\r\n\r\n      g:wm_move_left (default:'<Left>')\r\n          if empty string, no mapping is defined.\r\n\r\n      g:wm_move_x (default:20)\r\n          gVim use this when move left or right.\r\n\r\n      g:wm_move_y (default:15)\r\n          gVim use this when move up or down.\r\n","install_details":"Just move this into your plugin's directory","5":"Just move this into your plugin's directory","first_name":"tyru","6":"tyru","last_name":" ","7":" ","releases":[{"0":"2576","vim_version":"7.0","1":"7.0","script_version":"0.0.4","2":"0.0.4","version_comment":"Fix bug: :winpos raised an error\r\nbecause :winpos is not available at startup.\r\n(the problem occurred on gVim Windows XP)\r\n","3":"Fix bug: :winpos raised an error\r\nbecause :winpos is not available at startup.\r\n(the problem occurred on gVim Windows XP)\r\n","package":"winmove.zip","4":"winmove.zip","src_id":"14626","5":"14626","creation_date":"1293415627","6":"1293415627"},{"0":"2576","vim_version":"7.0","1":"7.0","script_version":"0.0.3","2":"0.0.3","version_comment":"Fix bug: gvim moves oppositely on MacVim. Thanks ujihisa for the patch.\r\n","3":"Fix bug: gvim moves oppositely on MacVim. Thanks ujihisa for the patch.\r\n","package":"winmove.vim","4":"winmove.vim","src_id":"14227","5":"14227","creation_date":"1289438389","6":"1289438389"},{"0":"2576","vim_version":"7.0","1":"7.0","script_version":"0.0.2","2":"0.0.2","version_comment":"Allow range before mappings.\r\ne.g.: '10<Up>' moves gVim window to the upper 10 times","3":"Allow range before mappings.\r\ne.g.: '10<Up>' moves gVim window to the upper 10 times","package":"winmove.vim","4":"winmove.vim","src_id":"11745","5":"11745","creation_date":"1258457561","6":"1258457561"},{"0":"2576","vim_version":"6.0","1":"6.0","script_version":"0.0.1","2":"0.0.1","version_comment":"my e-mail address was wrong :p","3":"my e-mail address was wrong :p","package":"winmove.vim","4":"winmove.vim","src_id":"10372","5":"10372","creation_date":"1239273869","6":"1239273869"},{"0":"2576","vim_version":"7.0","1":"7.0","script_version":"0.0.0","2":"0.0.0","version_comment":"Initial upload","3":"Initial upload","package":"winmove.vim","4":"winmove.vim","src_id":"10144","5":"10144","creation_date":"1236593809","6":"1236593809"}]},"2575":{"script_id":"2575","0":"2575","script_name":"std includes","1":"std includes","script_type":"utility","2":"utility","summary":"Add std:: includes to your file according to what you have used.","3":"Add std:: includes to your file according to what you have used.","description":"Add c++ std includes to your c++ file.\r\n\r\nexecute\r\n:StdIncludes\r\nto add includes.\r\n\r\nYour code should use std:: explicitly.\r\n\r\nScreen shots:\r\nhttp:\/\/www.railmoon.com\/vim-std-includes\/vim-std-includes\r\n\r\nPlease email me problems or suggestions.","4":"Add c++ std includes to your c++ file.\r\n\r\nexecute\r\n:StdIncludes\r\nto add includes.\r\n\r\nYour code should use std:: explicitly.\r\n\r\nScreen shots:\r\nhttp:\/\/www.railmoon.com\/vim-std-includes\/vim-std-includes\r\n\r\nPlease email me problems or suggestions.","install_details":"put to your vim plugin dir ( ~\/.vim\/plugin for nix like systems )","5":"put to your vim plugin dir ( ~\/.vim\/plugin for nix like systems )","first_name":"Mykola","6":"Mykola","last_name":"Golubyev","7":"Golubyev","releases":[{"0":"2575","vim_version":"7.0","1":"7.0","script_version":"0.4.1","2":"0.4.1","version_comment":"Less empty lines when perform :StdIncludes without any header.","3":"Less empty lines when perform :StdIncludes without any header.","package":"std_includes.vim","4":"std_includes.vim","src_id":"10189","5":"10189","creation_date":"1236888275","6":"1236888275"},{"0":"2575","vim_version":"7.0","1":"7.0","script_version":"0.4","2":"0.4","version_comment":"Initial upload","3":"Initial upload","package":"std_includes.vim","4":"std_includes.vim","src_id":"10141","5":"10141","creation_date":"1236548245","6":"1236548245"}]},"2574":{"script_id":"2574","0":"2574","script_name":"codeburn","1":"codeburn","script_type":"color scheme","2":"color scheme","summary":"light scheme optimized for ruby, haml","3":"light scheme optimized for ruby, haml","description":"http:\/\/img17.imageshack.us\/my.php?image=picture1rhj.png","4":"http:\/\/img17.imageshack.us\/my.php?image=picture1rhj.png","install_details":"Save file to\r\n\r\n~\/.vim\/colors\/codeburn.vim\r\n\r\nTo use scheme while in gvim (macvim)\r\n\r\n:colo codeburn\r\n\r\nTo use as default scheme, edit ~\/.gvimrc\r\n\r\ncolors codeburn ","5":"Save file to\r\n\r\n~\/.vim\/colors\/codeburn.vim\r\n\r\nTo use scheme while in gvim (macvim)\r\n\r\n:colo codeburn\r\n\r\nTo use as default scheme, edit ~\/.gvimrc\r\n\r\ncolors codeburn ","first_name":"Mario","6":"Mario","last_name":"Gutierrez","7":"Gutierrez","releases":[{"0":"2574","vim_version":"7.0","1":"7.0","script_version":"0.2","2":"0.2","version_comment":"lighter; more vibrant","3":"lighter; more vibrant","package":"codeburn.vim","4":"codeburn.vim","src_id":"10187","5":"10187","creation_date":"1236872078","6":"1236872078"},{"0":"2574","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"codeburn.vim","4":"codeburn.vim","src_id":"10137","5":"10137","creation_date":"1236469171","6":"1236469171"}]},"2573":{"script_id":"2573","0":"2573","script_name":"Darkdevel","1":"Darkdevel","script_type":"color scheme","2":"color scheme","summary":"Vim colorscheme","3":"Vim colorscheme","description":"Darkdevel Vim colorscheme.","4":"Darkdevel Vim colorscheme.","install_details":"You cant install this color scheme downloading the Vimball gzipped from script\r\n[page][1] and type de command:\r\n\r\n    vim -ne darkdevel-<version>.vba.gz +'source %' +'quit'\r\n\r\nOr checkout the Git repository hosted on [Github][2]:\r\n\r\n    git clone --branch develop http:\/\/github.com\/depuracao\/vim-darkdevel.git\r\n    cd vim-darkdevel\r\n    make install\r\n\r\nIf you want other method, try the [pathogen plugin][3]:\r\n\r\n    cd ~\/.vim\/bundle\r\n    git clone --branch master http:\/\/github.com\/depuracao\/vim-darkdevel.git\r\n\r\n[1]: http:\/\/www.vim.org\/scripts\/script.php?script_id=2573\r\n  \"Vim - Darkdevel script page\"\r\n[2]: http:\/\/github.com\/depuracao\/vim-darkdevel\r\n  \"Vim -Darkdevel repository\"\r\n[3]: http:\/\/github.com\/tpope\/vim-pathogen\r\n  \"Vim - Pathogen to bundle plugins\"\r\n\r\nThis plugin is distributed under the Vim License terms. See `:help license`.\r\n","5":"You cant install this color scheme downloading the Vimball gzipped from script\r\n[page][1] and type de command:\r\n\r\n    vim -ne darkdevel-<version>.vba.gz +'source %' +'quit'\r\n\r\nOr checkout the Git repository hosted on [Github][2]:\r\n\r\n    git clone --branch develop http:\/\/github.com\/depuracao\/vim-darkdevel.git\r\n    cd vim-darkdevel\r\n    make install\r\n\r\nIf you want other method, try the [pathogen plugin][3]:\r\n\r\n    cd ~\/.vim\/bundle\r\n    git clone --branch master http:\/\/github.com\/depuracao\/vim-darkdevel.git\r\n\r\n[1]: http:\/\/www.vim.org\/scripts\/script.php?script_id=2573\r\n  \"Vim - Darkdevel script page\"\r\n[2]: http:\/\/github.com\/depuracao\/vim-darkdevel\r\n  \"Vim -Darkdevel repository\"\r\n[3]: http:\/\/github.com\/tpope\/vim-pathogen\r\n  \"Vim - Pathogen to bundle plugins\"\r\n\r\nThis plugin is distributed under the Vim License terms. See `:help license`.\r\n","first_name":"Hallison","6":"Hallison","last_name":"Batista","7":"Batista","releases":[{"0":"2573","vim_version":"6.0","1":"6.0","script_version":"2.0.0","2":"2.0.0","version_comment":"* Fully rewritten to support 8, 16 and 256 colors in XTerm.\r\n* New development structure.","3":"* Fully rewritten to support 8, 16 and 256 colors in XTerm.\r\n* New development structure.","package":"darkdevel-2.0.0.vba.gz","4":"darkdevel-2.0.0.vba.gz","src_id":"17516","5":"17516","creation_date":"1329969439","6":"1329969439"},{"0":"2573","vim_version":"7.0","1":"7.0","script_version":"1.1.2","2":"1.1.2","version_comment":"Bug fixes.\r\n\r\nmd5sum: d189df7babb22987979aefd559693c82","3":"Bug fixes.\r\n\r\nmd5sum: d189df7babb22987979aefd559693c82","package":"darkdevel-1.1.2.zip","4":"darkdevel-1.1.2.zip","src_id":"10291","5":"10291","creation_date":"1238096731","6":"1238096731"},{"0":"2573","vim_version":"7.0","1":"7.0","script_version":"1.1.1","2":"1.1.1","version_comment":"Released version 1.1.1\r\n\r\n* Colors fixes\r\n* Improve color cursor line\r\n","3":"Released version 1.1.1\r\n\r\n* Colors fixes\r\n* Improve color cursor line\r\n","package":"darkdevel-1.1.1.zip","4":"darkdevel-1.1.1.zip","src_id":"10234","5":"10234","creation_date":"1237302395","6":"1237302395"},{"0":"2573","vim_version":"7.0","1":"7.0","script_version":"1.1.0","2":"1.1.0","version_comment":"Update colors and adding new files.\r\n\r\n  * The color of column and row of the cursor were darkened.\r\n  * A script was added for packaging.\r\n\r\nVisit GitHub.com for more informations.","3":"Update colors and adding new files.\r\n\r\n  * The color of column and row of the cursor were darkened.\r\n  * A script was added for packaging.\r\n\r\nVisit GitHub.com for more informations.","package":"darkdevel-1.1.0.zip","4":"darkdevel-1.1.0.zip","src_id":"10225","5":"10225","creation_date":"1237235984","6":"1237235984"},{"0":"2573","vim_version":"7.0","1":"7.0","script_version":"1.0.0","2":"1.0.0","version_comment":"Initial upload","3":"Initial upload","package":"darkdevel-1.0.0.zip","4":"darkdevel-1.0.0.zip","src_id":"10134","5":"10134","creation_date":"1236354217","6":"1236354217"}]},"2572":{"script_id":"2572","0":"2572","script_name":"ack.vim","1":"ack.vim","script_type":"utility","2":"utility","summary":"Plugin for the Perl module \/ CLI script 'ack'","3":"Plugin for the Perl module \/ CLI script 'ack'","description":"This plugin is a front for the Perl module App::Ack. Ack can be used as a replacement for 99% of the uses of grep. This plugin will allow you to run ack from vim, and shows the results in a split window.\r\n\r\nSearch recursively in {directory} (which defaults to the current directory) for the {pattern}.\r\n\r\nFiles containing the search term will be listed in the split window, along with the line number of the occurrence, once for each occurrence. [Enter] on a line in this window will open the file, and place the cursor on the matching line.\r\n\r\nWhere you would use :grep, :grepadd, :lgrep, and :lgrepadd, you can use :Ack, :AckAdd, :LAck, and :LAckAdd respectively.\r\n\r\nFor more information, and to check out the unstable, development version of the plugin, go here: http:\/\/github.com\/mileszs\/ack.vim\/tree\/master\r\n\r\nThis Vim plugin is derived (and by derived, I mean copied, essentially) from Antoine Imbert's blog post Ack and Vim Integration (http:\/\/blog.ant0ine.com\/2007\/03\/ack_and_vim_integration.html) (in particular, the function at the bottom of the post).","4":"This plugin is a front for the Perl module App::Ack. Ack can be used as a replacement for 99% of the uses of grep. This plugin will allow you to run ack from vim, and shows the results in a split window.\r\n\r\nSearch recursively in {directory} (which defaults to the current directory) for the {pattern}.\r\n\r\nFiles containing the search term will be listed in the split window, along with the line number of the occurrence, once for each occurrence. [Enter] on a line in this window will open the file, and place the cursor on the matching line.\r\n\r\nWhere you would use :grep, :grepadd, :lgrep, and :lgrepadd, you can use :Ack, :AckAdd, :LAck, and :LAckAdd respectively.\r\n\r\nFor more information, and to check out the unstable, development version of the plugin, go here: http:\/\/github.com\/mileszs\/ack.vim\/tree\/master\r\n\r\nThis Vim plugin is derived (and by derived, I mean copied, essentially) from Antoine Imbert's blog post Ack and Vim Integration (http:\/\/blog.ant0ine.com\/2007\/03\/ack_and_vim_integration.html) (in particular, the function at the bottom of the post).","install_details":"Ack\r\n\r\nYou have to install ack, of course.\r\n\r\nInstall on Ubuntu with:\r\n\r\nsudo apt-get install ack-grep\r\n\r\nInstall on Gentoo with:\r\n\r\nsudo emerge ack\r\n\r\nInstall with MacPorts:\r\n\r\nsudo port install p5-app-ack\r\n\r\nInstall with Gentoo Prefix\r\n\r\nemerge ack\r\n\r\nOtherwise, you are on your own.\r\n\r\nThe Plugin\r\n\r\nUnpack the gzipped archive from within ~\/.vim, and you should be good to go. \r\n\r\nmv ack.tar.gz ~\/.vim\r\ncd ~\/.vim\r\ntar xvzf ack.tar.gz\r\n\r\nOtherwise, the file ack.vim goes in ~\/.vim\/plugin, and the ack.txt file belongs in ~\/.vim\/doc. \r\n\r\nBe sure to run\r\n\r\n:helptags ~\/.vim\/doc\r\n\r\nafterwards.","5":"Ack\r\n\r\nYou have to install ack, of course.\r\n\r\nInstall on Ubuntu with:\r\n\r\nsudo apt-get install ack-grep\r\n\r\nInstall on Gentoo with:\r\n\r\nsudo emerge ack\r\n\r\nInstall with MacPorts:\r\n\r\nsudo port install p5-app-ack\r\n\r\nInstall with Gentoo Prefix\r\n\r\nemerge ack\r\n\r\nOtherwise, you are on your own.\r\n\r\nThe Plugin\r\n\r\nUnpack the gzipped archive from within ~\/.vim, and you should be good to go. \r\n\r\nmv ack.tar.gz ~\/.vim\r\ncd ~\/.vim\r\ntar xvzf ack.tar.gz\r\n\r\nOtherwise, the file ack.vim goes in ~\/.vim\/plugin, and the ack.txt file belongs in ~\/.vim\/doc. \r\n\r\nBe sure to run\r\n\r\n:helptags ~\/.vim\/doc\r\n\r\nafterwards.","first_name":"Miles","6":"Miles","last_name":"Sterrett","7":"Sterrett","releases":[{"0":"2572","vim_version":"6.0","1":"6.0","script_version":"0.3.1","2":"0.3.1","version_comment":"Added :redraw!","3":"Added :redraw!","package":"ack.tar.gz","4":"ack.tar.gz","src_id":"10433","5":"10433","creation_date":"1240333813","6":"1240333813"},{"0":"2572","vim_version":"6.0","1":"6.0","script_version":"0.3","2":"0.3","version_comment":"Initial upload","3":"Initial upload","package":"ack.tar.gz","4":"ack.tar.gz","src_id":"10129","5":"10129","creation_date":"1236288138","6":"1236288138"}]},"2571":{"script_id":"2571","0":"2571","script_name":"apidock.vim","1":"apidock.vim","script_type":"utility","2":"utility","summary":"Plugin that searches http:\/\/apidock.com Rails\/Ruby\/RSpec docs","3":"Plugin that searches http:\/\/apidock.com Rails\/Ruby\/RSpec docs","description":"This plugin allows you to browse APIdock's Ruby, Rails, and RSpec docs from within Vim. It will invoke Firefox from the command line, and open the query in a new tab.\r\n\r\nThe plugin uses the command 'firefox', which it expects to be in your path, and executable from your shell. See 'Customization' below if you need some other behavior. (In particular, all of you OSX users will have to make a small change.) This should work out of the box on Ubuntu, and most other Linux-based systems on which Firefox is installed.\r\n\r\nUsage\r\n\r\n    *  RR - Search the Rails docs for the word under the cursor.\r\n    *  RB - Search the Ruby docs for the word under the cursor.\r\n    *  RS - Search the RSpec docs for the word under the cursor.\r\n\r\nMore info, as well as the unstable, development version is available here: http:\/\/github.com\/mileszs\/apidock.vim\/tree\/master","4":"This plugin allows you to browse APIdock's Ruby, Rails, and RSpec docs from within Vim. It will invoke Firefox from the command line, and open the query in a new tab.\r\n\r\nThe plugin uses the command 'firefox', which it expects to be in your path, and executable from your shell. See 'Customization' below if you need some other behavior. (In particular, all of you OSX users will have to make a small change.) This should work out of the box on Ubuntu, and most other Linux-based systems on which Firefox is installed.\r\n\r\nUsage\r\n\r\n    *  RR - Search the Rails docs for the word under the cursor.\r\n    *  RB - Search the Ruby docs for the word under the cursor.\r\n    *  RS - Search the RSpec docs for the word under the cursor.\r\n\r\nMore info, as well as the unstable, development version is available here: http:\/\/github.com\/mileszs\/apidock.vim\/tree\/master","install_details":"Unpack the gzipped archive from within ~\/.vim, and you should be good to go.\r\n\r\nOtherwise, the file apidock.vim goes in ~\/.vim\/plugin, and the apidock.txt file belongs in ~\/.vim\/doc. Be sure to run\r\n\r\n:helptags ~\/.vim\/doc\r\n\r\nafterwards.","5":"Unpack the gzipped archive from within ~\/.vim, and you should be good to go.\r\n\r\nOtherwise, the file apidock.vim goes in ~\/.vim\/plugin, and the apidock.txt file belongs in ~\/.vim\/doc. Be sure to run\r\n\r\n:helptags ~\/.vim\/doc\r\n\r\nafterwards.","first_name":"Miles","6":"Miles","last_name":"Sterrett","7":"Sterrett","releases":[{"0":"2571","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Actual fix of the directory structure.","3":"Actual fix of the directory structure.","package":"apidock.tar.gz","4":"apidock.tar.gz","src_id":"10128","5":"10128","creation_date":"1236287602","6":"1236287602"}]},"2570":{"script_id":"2570","0":"2570","script_name":"vimdecdef","1":"vimdecdef","script_type":"ftplugin","2":"ftplugin","summary":"Switch between C++ declarations and definitions","3":"Switch between C++ declarations and definitions","description":"http:\/\/github.com\/eddic\/vimdecdef\r\n\r\nFirst off I would grab the vimdecdef.vim file from the above address\r\ninstead of the tarballed one as it may be out of date.\r\n\r\nvimdecdef is a simple vim script that facilitates transitioning between\r\ndeclarations and definitions in C++. The script can take a declaration and\r\neither find it's definition or create one if it doens't exist. The definitions\r\nwill take into account scope and template. All script actions will utilize one\r\nof two files. The header file and the source file. Initilially one should\r\nalways load a header file. If for example one executed ':e include\/file.hpp'\r\nthen the script will automatically assume that the source file is located at\r\nsrc\/file.cpp. The script has a single bindable command that preforms the\r\nfollowing functions based on it's situation:\r\n\r\n * If the cursor is on a normal function activating the script will search the\r\n   source file for it's definition. If the definition does not exist, it will\r\n   append one at the bottom of the source file and leave the cursor there.\r\n * If the cursor is on an inline or template function activating the script will\r\n   search the source file for it's definition. If it is found in the source\r\n   file, the cursor will be positioned there. If the definition is not found in\r\n   the source file the script will try to find it in the header file. If it is\r\n   found in the header file, the cursor will be positioned there. If it is not\r\n   found, one will be appended to the bottom of the header file insuring that it\r\n   stays within any closing #endif that may exist.\r\n * If the cursor is on a global object or static data member the script will\r\n   search the source file for it's definition. If the definition does not exist,\r\n   it will append one at the bottom of the source file and leave the cursor\r\n   there.\r\n * If the script's last action ended in a definition in the header file,\r\n   activating it again will move the cursor back to the original declaration\r\n   that caused the previous move regardless of the cursors current position.\r\n * Activating the script at any point in the header file that doesn't fall under\r\n   any of the above circumstances will result in switching to the source file at\r\n   it's last cursor position.\r\n * Activating the script while in the source file will always result in\r\n   switching back to the header file at it's last cursor position.","4":"http:\/\/github.com\/eddic\/vimdecdef\r\n\r\nFirst off I would grab the vimdecdef.vim file from the above address\r\ninstead of the tarballed one as it may be out of date.\r\n\r\nvimdecdef is a simple vim script that facilitates transitioning between\r\ndeclarations and definitions in C++. The script can take a declaration and\r\neither find it's definition or create one if it doens't exist. The definitions\r\nwill take into account scope and template. All script actions will utilize one\r\nof two files. The header file and the source file. Initilially one should\r\nalways load a header file. If for example one executed ':e include\/file.hpp'\r\nthen the script will automatically assume that the source file is located at\r\nsrc\/file.cpp. The script has a single bindable command that preforms the\r\nfollowing functions based on it's situation:\r\n\r\n * If the cursor is on a normal function activating the script will search the\r\n   source file for it's definition. If the definition does not exist, it will\r\n   append one at the bottom of the source file and leave the cursor there.\r\n * If the cursor is on an inline or template function activating the script will\r\n   search the source file for it's definition. If it is found in the source\r\n   file, the cursor will be positioned there. If the definition is not found in\r\n   the source file the script will try to find it in the header file. If it is\r\n   found in the header file, the cursor will be positioned there. If it is not\r\n   found, one will be appended to the bottom of the header file insuring that it\r\n   stays within any closing #endif that may exist.\r\n * If the cursor is on a global object or static data member the script will\r\n   search the source file for it's definition. If the definition does not exist,\r\n   it will append one at the bottom of the source file and leave the cursor\r\n   there.\r\n * If the script's last action ended in a definition in the header file,\r\n   activating it again will move the cursor back to the original declaration\r\n   that caused the previous move regardless of the cursors current position.\r\n * Activating the script at any point in the header file that doesn't fall under\r\n   any of the above circumstances will result in switching to the source file at\r\n   it's last cursor position.\r\n * Activating the script while in the source file will always result in\r\n   switching back to the header file at it's last cursor position.","install_details":"First copy vimdecdef.vim into your ~\/.vim\/ftplugin\/cpp directory. You may want\r\nto enable hidden (:set hidden) while using the script as it tends to work in a\r\nprettier way. You will want to set up a map for the command. I like having it\r\nbound to <F7> so to accomplish that it's a simple matter of:\r\n\r\nmap <silent> <F7> <Plug>vimdecdef\r\n\r\nWith everything setup we can get started. Note all paths are relative. Say we\r\nhave a header file located at include\/somelibrary\/file.hpp. Our first step\r\nwill be to load it into vim. Always load the header file first.\r\n\r\nvim include\/somelibrary\/file.hpp\r\n\r\nNow the script will assume the source file is located at src\/file.cpp. Simple\r\npress <F7> at a blank line and the source file will be loaded. Press it again\r\nand you will switch back to the header file. Hit <F7> at a declaration, and\r\nspecial things discussed above will happen.\r\n\r\nThere are two customizable options: source file prefix and source file\r\nextension. The default definitions follow.\r\n\r\nlet g:vimdecdefSourceExtension = \"cpp\"\r\nlet g:vimdecdefSourcePrefix = \"src\/\"","5":"First copy vimdecdef.vim into your ~\/.vim\/ftplugin\/cpp directory. You may want\r\nto enable hidden (:set hidden) while using the script as it tends to work in a\r\nprettier way. You will want to set up a map for the command. I like having it\r\nbound to <F7> so to accomplish that it's a simple matter of:\r\n\r\nmap <silent> <F7> <Plug>vimdecdef\r\n\r\nWith everything setup we can get started. Note all paths are relative. Say we\r\nhave a header file located at include\/somelibrary\/file.hpp. Our first step\r\nwill be to load it into vim. Always load the header file first.\r\n\r\nvim include\/somelibrary\/file.hpp\r\n\r\nNow the script will assume the source file is located at src\/file.cpp. Simple\r\npress <F7> at a blank line and the source file will be loaded. Press it again\r\nand you will switch back to the header file. Hit <F7> at a declaration, and\r\nspecial things discussed above will happen.\r\n\r\nThere are two customizable options: source file prefix and source file\r\nextension. The default definitions follow.\r\n\r\nlet g:vimdecdefSourceExtension = \"cpp\"\r\nlet g:vimdecdefSourcePrefix = \"src\/\"","first_name":"Eddie","6":"Eddie","last_name":"Carle","7":"Carle","releases":[{"0":"2570","vim_version":"7.0","1":"7.0","script_version":"1.01","2":"1.01","version_comment":"To appease the windows users","3":"To appease the windows users","package":"vimdecdef.zip","4":"vimdecdef.zip","src_id":"10126","5":"10126","creation_date":"1236286119","6":"1236286119"}]},"2569":{"script_id":"2569","0":"2569","script_name":"LogMgr","1":"LogMgr","script_type":"utility","2":"utility","summary":"A simple log viewing script","3":"A simple log viewing script","description":"Log Mgr is a very simple script to tail logs while editing files. It does the following:\r\n\r\n1. Sources a global variable to create key bindings to log files\r\n2. A user can use the key bindings to see a buffer of the log\r\n3. The user can refresh this buffer\r\n\r\nMore complex versions are planned for the future, until then any suggestions are welcome","4":"Log Mgr is a very simple script to tail logs while editing files. It does the following:\r\n\r\n1. Sources a global variable to create key bindings to log files\r\n2. A user can use the key bindings to see a buffer of the log\r\n3. The user can refresh this buffer\r\n\r\nMore complex versions are planned for the future, until then any suggestions are welcome","install_details":"Then open logmgr.vba from within vim.\r\n\r\n    :so %\r\n\r\nComplete!","5":"Then open logmgr.vba from within vim.\r\n\r\n    :so %\r\n\r\nComplete!","first_name":"Logan","6":"Logan","last_name":"Bell","7":"Bell","releases":[{"0":"2569","vim_version":"6.0","1":"6.0","script_version":".01","2":".01","version_comment":"Initial upload","3":"Initial upload","package":"logmgr.tar.gz","4":"logmgr.tar.gz","src_id":"10112","5":"10112","creation_date":"1236213989","6":"1236213989"}]},"2568":{"script_id":"2568","0":"2568","script_name":"Blazer","1":"Blazer","script_type":"color scheme","2":"color scheme","summary":"Awesome Color scheme","3":"Awesome Color scheme","description":"Screenshot can be found here: http:\/\/mitkokostov.info\/resources\/images\/blazer.png","4":"Screenshot can be found here: http:\/\/mitkokostov.info\/resources\/images\/blazer.png","install_details":"","5":"","first_name":"Mitko","6":"Mitko","last_name":"Kostov","7":"Kostov","releases":[{"0":"2568","vim_version":"7.0","1":"7.0","script_version":"0.3","2":"0.3","version_comment":"Beautiful vim colorscheme mainly used for Ruby and Clojure code","3":"Beautiful vim colorscheme mainly used for Ruby and Clojure code","package":"blazer.vim","4":"blazer.vim","src_id":"13072","5":"13072","creation_date":"1275179427","6":"1275179427"},{"0":"2568","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload, after rename","3":"Initial upload, after rename","package":"blazer.vim","4":"blazer.vim","src_id":"12481","5":"12481","creation_date":"1266994919","6":"1266994919"}]},"2567":{"script_id":"2567","0":"2567","script_name":"Vim Rspec","1":"Vim Rspec","script_type":"utility","2":"utility","summary":"Enable the use of the spec command inside Vim","3":"Enable the use of the spec command inside Vim","description":"This plugin make easy to run the spec command inside Vim. You need Hpricot (http:\/\/wiki.github.com\/why\/hpricot)  OR xsltproc (http:\/\/www.xmlsoft.org\/XSLT\/xsltproc2.html) and grep (http:\/\/www.gnu.org\/software\/grep) to use it. Hpricot takes precedence over xsltproc. \r\nThere are four files on the package: the Vim script, the Ruby script, the XSL file and the syntax file.\r\n\r\nThere are two commands available: \r\n\r\nYou can run RunSpec and spec will run with the current file (if it's a *_spec.rb file) \r\nYou can run RunSpecs and spec will run with all the files inside the spec directory. \r\n\r\nAfter some of the commands above runs, it will open a new window with the result, where you can click on the error lines where there's a file path with the line number and it will open on a new window, moving the cursor to the line where the error is.\r\n\r\nOf course, you can create some mappings to make easier to call the commands.\r\n\r\nThe project is hosted at Github: http:\/\/github.com\/taq\/vim-rspec","4":"This plugin make easy to run the spec command inside Vim. You need Hpricot (http:\/\/wiki.github.com\/why\/hpricot)  OR xsltproc (http:\/\/www.xmlsoft.org\/XSLT\/xsltproc2.html) and grep (http:\/\/www.gnu.org\/software\/grep) to use it. Hpricot takes precedence over xsltproc. \r\nThere are four files on the package: the Vim script, the Ruby script, the XSL file and the syntax file.\r\n\r\nThere are two commands available: \r\n\r\nYou can run RunSpec and spec will run with the current file (if it's a *_spec.rb file) \r\nYou can run RunSpecs and spec will run with all the files inside the spec directory. \r\n\r\nAfter some of the commands above runs, it will open a new window with the result, where you can click on the error lines where there's a file path with the line number and it will open on a new window, moving the cursor to the line where the error is.\r\n\r\nOf course, you can create some mappings to make easier to call the commands.\r\n\r\nThe project is hosted at Github: http:\/\/github.com\/taq\/vim-rspec","install_details":"To install, unpack the files on your ~\/.vim directory and source it to make it available. You can also use the Makefile to install the files, just type:\r\nmake install\r\n","5":"To install, unpack the files on your ~\/.vim directory and source it to make it available. You can also use the Makefile to install the files, just type:\r\nmake install\r\n","first_name":"Eustaquio","6":"Eustaquio","last_name":"Rangel de Oliveira Jr.","7":"Rangel de Oliveira Jr.","releases":[{"0":"2567","vim_version":"7.0","1":"7.0","script_version":"0.0.6","2":"0.0.6","version_comment":"Finds the current Rspec (spec or rspec) and have options now to customize commands and files.","3":"Finds the current Rspec (spec or rspec) and have options now to customize commands and files.","package":"vim-rspec-0.0.6.zip","4":"vim-rspec-0.0.6.zip","src_id":"14141","5":"14141","creation_date":"1288290732","6":"1288290732"},{"0":"2567","vim_version":"7.0","1":"7.0","script_version":"0.0.5","2":"0.0.5","version_comment":"Added folding to the passed specs.","3":"Added folding to the passed specs.","package":"vim-rspec-0.0.5.zip","4":"vim-rspec-0.0.5.zip","src_id":"10130","5":"10130","creation_date":"1236313965","6":"1236313965"},{"0":"2567","vim_version":"7.0","1":"7.0","script_version":"0.0.4","2":"0.0.4","version_comment":"Implemented parsing with hpricot.","3":"Implemented parsing with hpricot.","package":"vim-rspec-0.0.4.zip","4":"vim-rspec-0.0.4.zip","src_id":"10113","5":"10113","creation_date":"1236219983","6":"1236219983"},{"0":"2567","vim_version":"7.0","1":"7.0","script_version":"0.0.3","2":"0.0.3","version_comment":"Implemented the 'not implemented' status.","3":"Implemented the 'not implemented' status.","package":"vim-rspec-0.0.3.zip","4":"vim-rspec-0.0.3.zip","src_id":"10096","5":"10096","creation_date":"1236129889","6":"1236129889"},{"0":"2567","vim_version":"7.2","1":"7.2","script_version":"0.0.2","2":"0.0.2","version_comment":"Initial upload","3":"Initial upload","package":"vim-rspec-0.0.2.zip","4":"vim-rspec-0.0.2.zip","src_id":"10091","5":"10091","creation_date":"1236090202","6":"1236090202"}]},"2566":{"script_id":"2566","0":"2566","script_name":"utf8-math","1":"utf8-math","script_type":"ftplugin","2":"ftplugin","summary":"Keyboard shortcuts for math UTF-8 symbols","3":"Keyboard shortcuts for math UTF-8 symbols","description":"This package provides keyboard shortcuts for various UTF-8 mathematical symbols. Some of this is based on LaTeX (e.g., \"\\ldots\" ↦ \"\u00e2\u0080\u00a6\", \"\\beta\" ↦ β, \"\\mapsto\" ↦ \"↦\"); then there are some other shortcuts (e.g., arrows, quotation marks, dashes.)","4":"This package provides keyboard shortcuts for various UTF-8 mathematical symbols. Some of this is based on LaTeX (e.g., \"\\ldots\" ↦ \"\u00e2\u0080\u00a6\", \"\\beta\" ↦ β, \"\\mapsto\" ↦ \"↦\"); then there are some other shortcuts (e.g., arrows, quotation marks, dashes.)","install_details":"Drop it under .vim\/ftplugin, and \":setf utf8\" to use it.","5":"Drop it under .vim\/ftplugin, and \":setf utf8\" to use it.","first_name":"Steve","6":"Steve","last_name":"Dee","7":"Dee","releases":[{"0":"2566","vim_version":"6.0","1":"6.0","script_version":"0.2","2":"0.2","version_comment":"Added \\qed, changed current \\phi to \\varphi, and added new \\phi.","3":"Added \\qed, changed current \\phi to \\varphi, and added new \\phi.","package":"utf8.vim","4":"utf8.vim","src_id":"10264","5":"10264","creation_date":"1237765460","6":"1237765460"},{"0":"2566","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"utf8.vim","4":"utf8.vim","src_id":"10087","5":"10087","creation_date":"1236037152","6":"1236037152"}]},"2565":{"script_id":"2565","0":"2565","script_name":"runVimTests","1":"runVimTests","script_type":"utility","2":"utility","summary":"A testing framework for Vim. ","3":"A testing framework for Vim. ","description":"Every script writer knows how tedious it is to update a published plugin. In\r\naddition to the basic functionality, many corner cases (empty line, last line,\r\netc.) and failures (invalid filename, nomodifiable buffer) need to be tested,\r\nand people use Vim on different platforms (Windows \/ Linux), UIs (Console \/\r\nGUI), with different sets of settings (.vimrc) and other loaded plugins.\r\nThere already exist multiple unit test plugins and assertion facilities [1],\r\nwhich are good for checking invariants and verifying side effect-free\r\nimplementation functions, but it is still hard to verify the complete plugin\r\nfunctionality because custom commands and mappings typically change the buffer\r\ncontents, open additional windows, or produce other side effects.\r\n\r\nThis work aims to show that Vim, together with a shell script driver built\r\naround it, allows to write succinct, fully automated regression test suites\r\nthrough a combination of these verification methods:\r\n- Comparing buffer contents with a predefined nominal file.\r\n- Matching actual Vim message output with a set of expected messages.\r\n- Running unit tests or assertions inside Vim and evaluating the test results.\r\n\r\nWith this testing framework, Test-Driven Development can finally be practiced\r\nfor Vim plugins, too. If you have existing plugins, just add a couple of basic\r\ntest cases for a start. Soon, further updates and modifications can be done\r\nmuch more rapidly with reduced testing effort, and you can finally tackle that\r\nbig refactoring that you've been wanting to do all the time, but were too\r\nafraid of because of the testing effort. The author has been following both\r\napproaches with great success.\r\n\r\n[1]\r\n- vimUnit (by Staale Flock), vimscript #1125\r\n- tAssert (by Tom Link), vimscript #1730\r\n- VimTAP (by Meikel Brandmeyer), vimscript #2213\r\n- spec.vim (by Tom Link), vimscript #2580\r\n- UT (by Luc Hermitte), http:\/\/code.google.com\/p\/lh-vim\/wiki\/UT\r\n- vim-unittest (by h1mesuke), https:\/\/github.com\/h1mesuke\/vim-unittest\r\n- Ultimate Test Utility (by Kevin Biskar), vimscript #4724 is a pure Vimscript\r\n  implementation providing various test grouping and assertion functions.\r\n\r\nRELATED WORKS\r\n- robot-vim (https:\/\/github.com\/mrmargolis\/robot-vim) by Matt Margolis allows\r\n  to TDD Vim scripts using Ruby scripts that launch Vim instances, pass text,\r\n  execute commands and then run assertions against the buffer text in Ruby.\r\n- vspec (vimscript #3012) by Kana Natsuno allows to write tests BDD-style with\r\n  custom matchers, and is driven by a small Bash script.\r\n- Vader (vimscript #4832) by Junegunn Choi implements BDD-style testing from\r\n  within Vim via a test script in a custom syntax.\r\n\r\nEXAMPLE\r\nSpecify an expected output, e.g. in file 'test001.ok'\r\n    expected output\r\n    and more\r\n    expected output\r\nand\/or specify expected messages in file 'test001.msgok'\r\n    \/\\d\\+ lines changed\/\r\nuse an input file 'test001.in'\r\n    ExPeCteD OuTpUt\r\n    AND MORE\r\n    ExPeCteD OuTpUt\r\nwrite a short test script 'test001.vim'\r\n    edit test001.in\r\n    normal! gg3gugu\r\n    write test001.out\r\n    quit!\r\ncall the test runner\r\n    $ runVimTests test001.vim\r\nand the framework invokes the test(s) [suites], compares the actual with the\r\nexpected output, checks that the messages match, and prints any failures and a\r\ntest summary:\r\n    1 file with 2 tests; 0 skipped, 2 run: 2 OK, 0 failures, 0 errors.\r\n\r\n\r\nDESCRIPTION\r\nrunVimTests implements a testing framework for Vim.\r\n\r\nSimilar to the tests that are part of Vim's source distribution, each test\r\nconsists of a testXXX.vim file which is executed in a a separate Vim instance.\r\nThe outcome of a test can be determined by a combination of the following\r\nmethods:\r\n\r\nSAVED BUFFER OUTPUT\r\nIf a testXXX.ok file is provided, the testXXX.vim should save a testXXX.out\r\nfile at the end of its execution. The contents of the testXXX.out test file\r\nmust be identical to the provided testXXX.ok file for the test to succeed. The\r\ntest can either generate the test output itself, or start by editing a\r\ntestXXX.in (or similar) file and doing modifications to it.\r\nUse this method to test commands or mappings that modify buffer contents.\r\n\r\nCAPTURED MESSAGES\r\nIf a testXXX.msgok file is provided, the testXXX.vim file should generate Vim\r\nmessages (from built-in Vim commands, or via :echo[msg]), which are captured\r\nduring test execution in a testXXX.msgout file. The testXXX.msgok file\r\ncontains multiple message assertions (separated by empty lines), each of which\r\nis compiled into a Vim regexp and then matched against the captured messages.\r\nEach assertion can match exactly once, and all assertions must match in the\r\nsame order in the captured Vim messages. (But there can be additional Vim\r\nmessages before, after and in between matches, so that you can omit irrelevant\r\nor platform-specific messages from the testXXX.msgok file.) For details, see\r\nrunVimMsgFilter.\r\nThis method can verify that errors are reported correctly. Also use this\r\nmethod to test commands or mappings that print informational messages.\r\n\r\nTAP UNIT TESTS\r\nIf a testXXX.tap file exists at the end of a test execution, it is assumed to\r\nrepresent unit test output in the Test Anything Protocol [2], which is then\r\nparsed and incorporated into the test run. This method allows detailed\r\nverification of custom commands, mappings as well as internal functions; the\r\nentire determination of the test result is done in Vim script. Each TAP unit\r\ntest counts as one test, even though all those test results are produced by a\r\nsingle testXXX.vim file. If a plan announced more or less tests than what was\r\nfound in the test output, the test is assumed to be erroneous.\r\nUse this method to test the internal implementation functions, or to verify\r\nthings that can be checked easily with Vim script.\r\n\r\n[2]\r\nweb site: http:\/\/testanything.org,\r\noriginal implementation: http:\/\/search.cpan.org\/~petdance\/TAP-1.00\/TAP.pm,\r\nTAP protocol for Vim: http:\/\/www.vim.org\/scripts\/script.php?script_id=2213\r\n\r\nA test causes an error if none of these ok-files exist for a test, and no\r\ntestXXX.tap file was generated (so actually no verification is possible), or\r\nif the test execution does not produce the corresponding output files.\r\n\r\nUSAGE\r\nA test run is started through the \"runVimTests.(sh|cmd)\" script:\r\n    $ runVimTests [{options}] test001.vim|testsuite.txt|path\/to\/testdir\/ [...]\r\n\r\nThe tests are specified through these three methods, which can be combined:\r\n- Directly specify the filespec of testXXX.vim test script file(s).\r\n- Specify a directory; all *.vim files inside this directory (except for an\r\n  optional special _setup.vim file) will be used as test scripts.\r\n- A test suite is a text file containing (relative or absolute) filespecs to\r\n  test scripts, directories or other test suites, one filespec per line.\r\n  (Commented lines start with #.)\r\n\r\nThe script returns 0 if all tests were successful, 1 if any errors or failures\r\noccurred, 2 if it wasn't invoked correctly (i.e. bad or missing command-line\r\narguments) or prerequisites weren't met, 3 in case of an internal error.\r\n\r\nAfter test execution, a summary is printed like this:\r\n    20 files with 33 tests; 2 skipped, 27 run: 16 OK, 11 failures, 6 errors.\r\n    Tests with skips: test006.vim\r\n    Skipped tests: test007.vim\r\n        2 SKIP (tap): Need 'autochdir' option\r\n    Failed tests: test002.vim test012.vim test014.vim test022.vim test032.vim\r\n    Tests with errors: test003.vim test013.vim test023.vim test033.vim\r\n","4":"Every script writer knows how tedious it is to update a published plugin. In\r\naddition to the basic functionality, many corner cases (empty line, last line,\r\netc.) and failures (invalid filename, nomodifiable buffer) need to be tested,\r\nand people use Vim on different platforms (Windows \/ Linux), UIs (Console \/\r\nGUI), with different sets of settings (.vimrc) and other loaded plugins.\r\nThere already exist multiple unit test plugins and assertion facilities [1],\r\nwhich are good for checking invariants and verifying side effect-free\r\nimplementation functions, but it is still hard to verify the complete plugin\r\nfunctionality because custom commands and mappings typically change the buffer\r\ncontents, open additional windows, or produce other side effects.\r\n\r\nThis work aims to show that Vim, together with a shell script driver built\r\naround it, allows to write succinct, fully automated regression test suites\r\nthrough a combination of these verification methods:\r\n- Comparing buffer contents with a predefined nominal file.\r\n- Matching actual Vim message output with a set of expected messages.\r\n- Running unit tests or assertions inside Vim and evaluating the test results.\r\n\r\nWith this testing framework, Test-Driven Development can finally be practiced\r\nfor Vim plugins, too. If you have existing plugins, just add a couple of basic\r\ntest cases for a start. Soon, further updates and modifications can be done\r\nmuch more rapidly with reduced testing effort, and you can finally tackle that\r\nbig refactoring that you've been wanting to do all the time, but were too\r\nafraid of because of the testing effort. The author has been following both\r\napproaches with great success.\r\n\r\n[1]\r\n- vimUnit (by Staale Flock), vimscript #1125\r\n- tAssert (by Tom Link), vimscript #1730\r\n- VimTAP (by Meikel Brandmeyer), vimscript #2213\r\n- spec.vim (by Tom Link), vimscript #2580\r\n- UT (by Luc Hermitte), http:\/\/code.google.com\/p\/lh-vim\/wiki\/UT\r\n- vim-unittest (by h1mesuke), https:\/\/github.com\/h1mesuke\/vim-unittest\r\n- Ultimate Test Utility (by Kevin Biskar), vimscript #4724 is a pure Vimscript\r\n  implementation providing various test grouping and assertion functions.\r\n\r\nRELATED WORKS\r\n- robot-vim (https:\/\/github.com\/mrmargolis\/robot-vim) by Matt Margolis allows\r\n  to TDD Vim scripts using Ruby scripts that launch Vim instances, pass text,\r\n  execute commands and then run assertions against the buffer text in Ruby.\r\n- vspec (vimscript #3012) by Kana Natsuno allows to write tests BDD-style with\r\n  custom matchers, and is driven by a small Bash script.\r\n- Vader (vimscript #4832) by Junegunn Choi implements BDD-style testing from\r\n  within Vim via a test script in a custom syntax.\r\n\r\nEXAMPLE\r\nSpecify an expected output, e.g. in file 'test001.ok'\r\n    expected output\r\n    and more\r\n    expected output\r\nand\/or specify expected messages in file 'test001.msgok'\r\n    \/\\d\\+ lines changed\/\r\nuse an input file 'test001.in'\r\n    ExPeCteD OuTpUt\r\n    AND MORE\r\n    ExPeCteD OuTpUt\r\nwrite a short test script 'test001.vim'\r\n    edit test001.in\r\n    normal! gg3gugu\r\n    write test001.out\r\n    quit!\r\ncall the test runner\r\n    $ runVimTests test001.vim\r\nand the framework invokes the test(s) [suites], compares the actual with the\r\nexpected output, checks that the messages match, and prints any failures and a\r\ntest summary:\r\n    1 file with 2 tests; 0 skipped, 2 run: 2 OK, 0 failures, 0 errors.\r\n\r\n\r\nDESCRIPTION\r\nrunVimTests implements a testing framework for Vim.\r\n\r\nSimilar to the tests that are part of Vim's source distribution, each test\r\nconsists of a testXXX.vim file which is executed in a a separate Vim instance.\r\nThe outcome of a test can be determined by a combination of the following\r\nmethods:\r\n\r\nSAVED BUFFER OUTPUT\r\nIf a testXXX.ok file is provided, the testXXX.vim should save a testXXX.out\r\nfile at the end of its execution. The contents of the testXXX.out test file\r\nmust be identical to the provided testXXX.ok file for the test to succeed. The\r\ntest can either generate the test output itself, or start by editing a\r\ntestXXX.in (or similar) file and doing modifications to it.\r\nUse this method to test commands or mappings that modify buffer contents.\r\n\r\nCAPTURED MESSAGES\r\nIf a testXXX.msgok file is provided, the testXXX.vim file should generate Vim\r\nmessages (from built-in Vim commands, or via :echo[msg]), which are captured\r\nduring test execution in a testXXX.msgout file. The testXXX.msgok file\r\ncontains multiple message assertions (separated by empty lines), each of which\r\nis compiled into a Vim regexp and then matched against the captured messages.\r\nEach assertion can match exactly once, and all assertions must match in the\r\nsame order in the captured Vim messages. (But there can be additional Vim\r\nmessages before, after and in between matches, so that you can omit irrelevant\r\nor platform-specific messages from the testXXX.msgok file.) For details, see\r\nrunVimMsgFilter.\r\nThis method can verify that errors are reported correctly. Also use this\r\nmethod to test commands or mappings that print informational messages.\r\n\r\nTAP UNIT TESTS\r\nIf a testXXX.tap file exists at the end of a test execution, it is assumed to\r\nrepresent unit test output in the Test Anything Protocol [2], which is then\r\nparsed and incorporated into the test run. This method allows detailed\r\nverification of custom commands, mappings as well as internal functions; the\r\nentire determination of the test result is done in Vim script. Each TAP unit\r\ntest counts as one test, even though all those test results are produced by a\r\nsingle testXXX.vim file. If a plan announced more or less tests than what was\r\nfound in the test output, the test is assumed to be erroneous.\r\nUse this method to test the internal implementation functions, or to verify\r\nthings that can be checked easily with Vim script.\r\n\r\n[2]\r\nweb site: http:\/\/testanything.org,\r\noriginal implementation: http:\/\/search.cpan.org\/~petdance\/TAP-1.00\/TAP.pm,\r\nTAP protocol for Vim: http:\/\/www.vim.org\/scripts\/script.php?script_id=2213\r\n\r\nA test causes an error if none of these ok-files exist for a test, and no\r\ntestXXX.tap file was generated (so actually no verification is possible), or\r\nif the test execution does not produce the corresponding output files.\r\n\r\nUSAGE\r\nA test run is started through the \"runVimTests.(sh|cmd)\" script:\r\n    $ runVimTests [{options}] test001.vim|testsuite.txt|path\/to\/testdir\/ [...]\r\n\r\nThe tests are specified through these three methods, which can be combined:\r\n- Directly specify the filespec of testXXX.vim test script file(s).\r\n- Specify a directory; all *.vim files inside this directory (except for an\r\n  optional special _setup.vim file) will be used as test scripts.\r\n- A test suite is a text file containing (relative or absolute) filespecs to\r\n  test scripts, directories or other test suites, one filespec per line.\r\n  (Commented lines start with #.)\r\n\r\nThe script returns 0 if all tests were successful, 1 if any errors or failures\r\noccurred, 2 if it wasn't invoked correctly (i.e. bad or missing command-line\r\narguments) or prerequisites weren't met, 3 in case of an internal error.\r\n\r\nAfter test execution, a summary is printed like this:\r\n    20 files with 33 tests; 2 skipped, 27 run: 16 OK, 11 failures, 6 errors.\r\n    Tests with skips: test006.vim\r\n    Skipped tests: test007.vim\r\n        2 SKIP (tap): Need 'autochdir' option\r\n    Failed tests: test002.vim test012.vim test014.vim test022.vim test032.vim\r\n    Tests with errors: test003.vim test013.vim test023.vim test033.vim\r\n","install_details":"INSTALLATION\r\nThis framework is packaged as a ZIP archive. You can unpack it directly into\r\nyour-runtime-dir (~\/.vim), but you can also install the script executables\r\nsomewhere else.\r\n\r\nThe script executables are in the bin\/ subdirectory:\r\n    bin\/runVimTests.cmd\r\n    bin\/runVimTests.sh\r\n    bin\/runVimMsgFilter.vim\r\nThey can be put anywhere (preferably somewhere in $PATH for easy invocation).\r\nrunVimMsgFilter.vim must be in the same directory as the shell script.\r\n\r\nThe doc\/ subdirectory contains the documentation. Put the files into\r\n~\/.vim\/doc and execute :helptags ~\/.vim\/doc to re-generate the help tags.\r\n\r\nThe autoload\/ subdirectory contains optional convenience and helper functions.\r\n(E.g. vimtest#Quit(), vimtest#SaveOut(), vimtest#RequestInput(), and\r\nmore. See vimtest-usage for a full reference.)\r\nTheir use is not required, but they simplify the writing of tests.\r\n\r\nThe VimTAP plugin (vimscript #2213) needs to be installed separately.\r\nThe examples here use the API of version 0.3.0; version 0.4.0 of the plugin\r\nintroduced compatibility-breaking changes, which I don't like; the functions\r\nare now cumbersome to use, and the added commands don't offer much\r\nconvenience, but pollute the test environment in my opinion. If you like, you\r\ncan use my own fork of version 0.3.0:\r\n    https:\/\/github.com\/inkarkat\/VimTAP\r\nNote that nothing prevents you from using the latest, original version for\r\nyour own tests. The default runVimTestsSetup.vim will automatically include\r\nVimTAP into 'runtimepath' if it's located in a repository next to runVimTests.\r\n\r\nThe tests\/ subdirectory contains example test suites and a self-test of the\r\ntest framework. For a simple sanity check, execute:\r\n    $ runVimTests tests\/runVimTests\/successful.suite\r\nwhich should print something like:\r\n    9 files with 19 tests; 0 skipped, 19 run: 19 OK, 0 failures, 0 errors.\r\nIf this is the case, you can start exploring the example tests (in the\r\ntests\/example\/ subdirectory) or just start writing your own\r\nrunVimTests-testscripts!\r\n\r\nDEPENDENCIES\r\n- Requires Vim 7.2 or higher as the default Vim found in $PATH (which is\r\n  always used for the matching of Vim message output against the captured\r\n  messages). You can use a different Vim version to execute the tests, but at\r\n  least Vim 7.0 is required to use captured messages (as this depends on the\r\n  'verbosefile' option) and TAP unit tests (vimtap.vim is an autoload script).\r\n  The saved buffer output method even works with Vim 6, but the driver will\r\n  generate errors in that case.\r\n\r\nThe Windows version requires (* = optional) these ported Unix tools:\r\n- grep, sed, diff, sort(*), uniq(*)\r\nWindows binaries can be downloaded from the GnuWin32 project:\r\n    http:\/\/gnuwin32.sourceforge.net\/\r\nThese binaries must be accessible through %PATH%. Alternatively, you can just\r\nmake accessible an Windows shell script named \"unix.cmd\", which is then\r\nsourced in order to modify %PATH% to include the Unix tools. This way, you can\r\navoid to permanently place these Unix tools into %PATH%.\r\n\r\n- Requires the ingo-library.vim plugin (vimscript #4433), version 1.012 or\r\n  higher, only for Vim 7.0 and 7.1.\r\n\r\nCONTRIBUTING\r\nThe code is hosted in a Git repo at https:\/\/github.com\/inkarkat\/runVimTests\r\nReport any bugs, send patches, or suggest features via email (address below),\r\nor via the issue tracker at https:\/\/github.com\/inkarkat\/runVimTests\/issues","5":"INSTALLATION\r\nThis framework is packaged as a ZIP archive. You can unpack it directly into\r\nyour-runtime-dir (~\/.vim), but you can also install the script executables\r\nsomewhere else.\r\n\r\nThe script executables are in the bin\/ subdirectory:\r\n    bin\/runVimTests.cmd\r\n    bin\/runVimTests.sh\r\n    bin\/runVimMsgFilter.vim\r\nThey can be put anywhere (preferably somewhere in $PATH for easy invocation).\r\nrunVimMsgFilter.vim must be in the same directory as the shell script.\r\n\r\nThe doc\/ subdirectory contains the documentation. Put the files into\r\n~\/.vim\/doc and execute :helptags ~\/.vim\/doc to re-generate the help tags.\r\n\r\nThe autoload\/ subdirectory contains optional convenience and helper functions.\r\n(E.g. vimtest#Quit(), vimtest#SaveOut(), vimtest#RequestInput(), and\r\nmore. See vimtest-usage for a full reference.)\r\nTheir use is not required, but they simplify the writing of tests.\r\n\r\nThe VimTAP plugin (vimscript #2213) needs to be installed separately.\r\nThe examples here use the API of version 0.3.0; version 0.4.0 of the plugin\r\nintroduced compatibility-breaking changes, which I don't like; the functions\r\nare now cumbersome to use, and the added commands don't offer much\r\nconvenience, but pollute the test environment in my opinion. If you like, you\r\ncan use my own fork of version 0.3.0:\r\n    https:\/\/github.com\/inkarkat\/VimTAP\r\nNote that nothing prevents you from using the latest, original version for\r\nyour own tests. The default runVimTestsSetup.vim will automatically include\r\nVimTAP into 'runtimepath' if it's located in a repository next to runVimTests.\r\n\r\nThe tests\/ subdirectory contains example test suites and a self-test of the\r\ntest framework. For a simple sanity check, execute:\r\n    $ runVimTests tests\/runVimTests\/successful.suite\r\nwhich should print something like:\r\n    9 files with 19 tests; 0 skipped, 19 run: 19 OK, 0 failures, 0 errors.\r\nIf this is the case, you can start exploring the example tests (in the\r\ntests\/example\/ subdirectory) or just start writing your own\r\nrunVimTests-testscripts!\r\n\r\nDEPENDENCIES\r\n- Requires Vim 7.2 or higher as the default Vim found in $PATH (which is\r\n  always used for the matching of Vim message output against the captured\r\n  messages). You can use a different Vim version to execute the tests, but at\r\n  least Vim 7.0 is required to use captured messages (as this depends on the\r\n  'verbosefile' option) and TAP unit tests (vimtap.vim is an autoload script).\r\n  The saved buffer output method even works with Vim 6, but the driver will\r\n  generate errors in that case.\r\n\r\nThe Windows version requires (* = optional) these ported Unix tools:\r\n- grep, sed, diff, sort(*), uniq(*)\r\nWindows binaries can be downloaded from the GnuWin32 project:\r\n    http:\/\/gnuwin32.sourceforge.net\/\r\nThese binaries must be accessible through %PATH%. Alternatively, you can just\r\nmake accessible an Windows shell script named \"unix.cmd\", which is then\r\nsourced in order to modify %PATH% to include the Unix tools. This way, you can\r\navoid to permanently place these Unix tools into %PATH%.\r\n\r\n- Requires the ingo-library.vim plugin (vimscript #4433), version 1.012 or\r\n  higher, only for Vim 7.0 and 7.1.\r\n\r\nCONTRIBUTING\r\nThe code is hosted in a Git repo at https:\/\/github.com\/inkarkat\/runVimTests\r\nReport any bugs, send patches, or suggest features via email (address below),\r\nor via the issue tracker at https:\/\/github.com\/inkarkat\/runVimTests\/issues","first_name":"Ingo","6":"Ingo","last_name":"Karkat","7":"Karkat","releases":[{"0":"2565","vim_version":"7.2","1":"7.2","script_version":"1.30","2":"1.30","version_comment":"- Add vimtest#AddDependency() and vimtest#features#SupportsNormalWithCount().\r\n- CHG: Print full absolute path to tests instead of just the test name itself. When running complete suites or tests with subdirectories, it is difficult to locate a failing test with just the name.\r\n- ENH: Add -o|--output parameter that redirects all script output into a FILESPEC or &N file descriptor. Piping the entire output of runVimTests is problematic because the started Vim instances expect to write the UI to stdout; without that, the screen does not update \/ is messed up, and you cannot do debugging in there.","3":"- Add vimtest#AddDependency() and vimtest#features#SupportsNormalWithCount().\r\n- CHG: Print full absolute path to tests instead of just the test name itself. When running complete suites or tests with subdirectories, it is difficult to locate a failing test with just the name.\r\n- ENH: Add -o|--output parameter that redirects all script output into a FILESPEC or &N file descriptor. Piping the entire output of runVimTests is problematic because the started Vim instances expect to write the UI to stdout; without that, the screen does not update \/ is messed up, and you cannot do debugging in there.","package":"runVimTests-1.30.zip","4":"runVimTests-1.30.zip","src_id":"26954","5":"26954","creation_date":"1580762496","6":"1580762496"},{"0":"2565","vim_version":"7.0","1":"7.0","script_version":"1.25","2":"1.25","version_comment":"- vimtest#Quit(): Don't exit Vim when not running inside the runVimTests test framework. This is better behavior when accidentally (or for testing) executing the test script in plain Vim.\r\n- FIX: \"cd\" might print the path when CDPATH is set; discard it. Thanks to Raimondi for sending a pull request. https:\/\/github.com\/inkarkat\/runVimTests\/pull\/11\r\n- ENH: Make runVimTestsSetup.vim accept any directory starting with VimTAP; thanks to Marcelo Montu for the pull request. https:\/\/github.com\/inkarkat\/runVimTests\/pull\/9\r\n- With -1 \/ --default, newer Vim versions still pick up user plugins from the ~\/.vim\/pack directory. Temporarily modify 'packpath' during Vim startup to avoid that.","3":"- vimtest#Quit(): Don't exit Vim when not running inside the runVimTests test framework. This is better behavior when accidentally (or for testing) executing the test script in plain Vim.\r\n- FIX: \"cd\" might print the path when CDPATH is set; discard it. Thanks to Raimondi for sending a pull request. https:\/\/github.com\/inkarkat\/runVimTests\/pull\/11\r\n- ENH: Make runVimTestsSetup.vim accept any directory starting with VimTAP; thanks to Marcelo Montu for the pull request. https:\/\/github.com\/inkarkat\/runVimTests\/pull\/9\r\n- With -1 \/ --default, newer Vim versions still pick up user plugins from the ~\/.vim\/pack directory. Temporarily modify 'packpath' during Vim startup to avoid that.","package":"runVimTests-1.25.zip","4":"runVimTests-1.25.zip","src_id":"25182","5":"25182","creation_date":"1494345739","6":"1494345739"},{"0":"2565","vim_version":"7.0","1":"7.0","script_version":"1.24","2":"1.24","version_comment":"- Don't clobber the default viminfo file with the test results; use a special ~\/.vimtestinfo value for the actual test run (to enable tests that use viminfo), and no viminfo for the checking and processing steps.\r\n- Show _all_ global, non-test-specific Vim arguments in the initial message.\r\n- Convert the filespec passed to --source to an absolute one; relative ones only work when the test driver script doesn't cd into a different directory.\r\n- BUG: runVimTestsSetup.vim isn't sourced on Unix when invoked through runVimTests.sh (with the .sh file extension). Reported by Ryan Carney. https:\/\/github.com\/inkarkat\/runVimTests\/issues\/6\r\n- Replace the distributed escapings.vim autoload script with an optional dependency (for Vim 7.0 and 7.1) to the ingo-library. *** You need to separately install ingo-library (vimscript #4433) version 1.012 (or higher)! ***","3":"- Don't clobber the default viminfo file with the test results; use a special ~\/.vimtestinfo value for the actual test run (to enable tests that use viminfo), and no viminfo for the checking and processing steps.\r\n- Show _all_ global, non-test-specific Vim arguments in the initial message.\r\n- Convert the filespec passed to --source to an absolute one; relative ones only work when the test driver script doesn't cd into a different directory.\r\n- BUG: runVimTestsSetup.vim isn't sourced on Unix when invoked through runVimTests.sh (with the .sh file extension). Reported by Ryan Carney. https:\/\/github.com\/inkarkat\/runVimTests\/issues\/6\r\n- Replace the distributed escapings.vim autoload script with an optional dependency (for Vim 7.0 and 7.1) to the ingo-library. *** You need to separately install ingo-library (vimscript #4433) version 1.012 (or higher)! ***","package":"runVimTests-1.24.zip","4":"runVimTests-1.24.zip","src_id":"21404","5":"21404","creation_date":"1391029575","6":"1391029575"},{"0":"2565","vim_version":"7.0","1":"7.0","script_version":"1.23","2":"1.23","version_comment":"- Add support for Mac OS X; thanks to Israel Chauca Fuentes for sending a pull request. https:\/\/github.com\/inkarkat\/runVimTests\/pull\/1\r\n- Add support for BSD (tested on PC-BSD 9.1).","3":"- Add support for Mac OS X; thanks to Israel Chauca Fuentes for sending a pull request. https:\/\/github.com\/inkarkat\/runVimTests\/pull\/1\r\n- Add support for BSD (tested on PC-BSD 9.1).","package":"runVimTests-1.23.zip","4":"runVimTests-1.23.zip","src_id":"19706","5":"19706","creation_date":"1364290304","6":"1364290304"},{"0":"2565","vim_version":"7.0","1":"7.0","script_version":"1.22","2":"1.22","version_comment":"- Include the version 1.21 changes in the Windows runVimTests.cmd, too.\r\n- Switch to Git for the plugin's development to prevent such omissions (caused by my manual syncing, which is more complex in this case with files distributed over many different directory trees).","3":"- Include the version 1.21 changes in the Windows runVimTests.cmd, too.\r\n- Switch to Git for the plugin's development to prevent such omissions (caused by my manual syncing, which is more complex in this case with files distributed over many different directory trees).","package":"runVimTests-1.22.zip","4":"runVimTests-1.22.zip","src_id":"19650","5":"19650","creation_date":"1363355075","6":"1363355075"},{"0":"2565","vim_version":"7.0","1":"7.0","script_version":"1.21","2":"1.21","version_comment":"- FIX: Prevent script errors when the error message containing the full command line from a failing vimtest#System() contains characters like ['\"()].\r\n- CHG: Drop comma in the lists of failed \/ skipped \/ errored test and add .vim extension, so that the file list can be copy-and-pasted to another runVimTests invocation or :argedit'ed in Vim.\r\n- CHG: Change default mode from \"user\" to \"default\"; this is what I use all the time, anyway, as the \"user\" mode is too susceptible to incompatible customizations.","3":"- FIX: Prevent script errors when the error message containing the full command line from a failing vimtest#System() contains characters like ['\"()].\r\n- CHG: Drop comma in the lists of failed \/ skipped \/ errored test and add .vim extension, so that the file list can be copy-and-pasted to another runVimTests invocation or :argedit'ed in Vim.\r\n- CHG: Change default mode from \"user\" to \"default\"; this is what I use all the time, anyway, as the \"user\" mode is too susceptible to incompatible customizations.","package":"runVimTests-1.21.zip","4":"runVimTests-1.21.zip","src_id":"19604","5":"19604","creation_date":"1362659175","6":"1362659175"},{"0":"2565","vim_version":"7.0","1":"7.0","script_version":"1.20","2":"1.20","version_comment":"- ENH: Handle file globs in the passed tests and in suite entries on Windows, too. (In contrast to the Unix shell, these must be explicitly expanded on Windows.)\r\n- BUG: In the Windows test runner, remove duplicate quoting when vimExecutable isn't found. This actually prevented execution when passing --vimexecutable \"C:\\Program Files (x86)\\vim\\vim73\\vim.exe\"","3":"- ENH: Handle file globs in the passed tests and in suite entries on Windows, too. (In contrast to the Unix shell, these must be explicitly expanded on Windows.)\r\n- BUG: In the Windows test runner, remove duplicate quoting when vimExecutable isn't found. This actually prevented execution when passing --vimexecutable \"C:\\Program Files (x86)\\vim\\vim73\\vim.exe\"","package":"runVimTests.zip","4":"runVimTests.zip","src_id":"18326","5":"18326","creation_date":"1343389563","6":"1343389563"},{"0":"2565","vim_version":"7.0","1":"7.0","script_version":"1.18","2":"1.18","version_comment":"- BUG: When everything is skipped and no TAP tests have been run, this would be reported as a \"No test results at all\" error. \r\n- CHG: Bail out only aborts from the current recursion level, i.e. it skips further tests in the same directory, suite, or passed arguments, but not testing entirely. Otherwise, a super-suite that includes individual suites would be aborted by a single bail out. ","3":"- BUG: When everything is skipped and no TAP tests have been run, this would be reported as a \"No test results at all\" error. \r\n- CHG: Bail out only aborts from the current recursion level, i.e. it skips further tests in the same directory, suite, or passed arguments, but not testing entirely. Otherwise, a super-suite that includes individual suites would be aborted by a single bail out. ","package":"runVimTests.zip","4":"runVimTests.zip","src_id":"16706","5":"16706","creation_date":"1319039383","6":"1319039383"},{"0":"2565","vim_version":"7.0","1":"7.0","script_version":"1.17","2":"1.17","version_comment":"- BUG: When runVimTests.sh is invoked via a relative filespec, $scriptDir is relative and this makes the message output comparison (but not the prerequisite check) fail with \"ERROR (msgout): Evaluation of test messages failed.\" when CWD has changed into $testDirspec. Thanks to Javier Rojas for sending a patch. ","3":"- BUG: When runVimTests.sh is invoked via a relative filespec, $scriptDir is relative and this makes the message output comparison (but not the prerequisite check) fail with \"ERROR (msgout): Evaluation of test messages failed.\" when CWD has changed into $testDirspec. Thanks to Javier Rojas for sending a patch. ","package":"runVimTests.zip","4":"runVimTests.zip","src_id":"16464","5":"16464","creation_date":"1315168617","6":"1315168617"},{"0":"2565","vim_version":"7.0","1":"7.0","script_version":"1.16","2":"1.16","version_comment":"- Minor bugfixes and tweaks to the self-test. \r\n- Renamed directory that the tests reside in from \"test\/\" to \"tests\/\". This is just a personal preference, you can still put the tests into whatever directory structure. \r\n- ENH: Added vimtest#ErrorAndQuit() for convenience. \r\n- bugfix and enhancement to the vimtest#System() function. ","3":"- Minor bugfixes and tweaks to the self-test. \r\n- Renamed directory that the tests reside in from \"test\/\" to \"tests\/\". This is just a personal preference, you can still put the tests into whatever directory structure. \r\n- ENH: Added vimtest#ErrorAndQuit() for convenience. \r\n- bugfix and enhancement to the vimtest#System() function. ","package":"runVimTests.zip","4":"runVimTests.zip","src_id":"15135","5":"15135","creation_date":"1298898809","6":"1298898809"},{"0":"2565","vim_version":"7.0","1":"7.0","script_version":"1.13","2":"1.13","version_comment":"ENH: Now including SKIP reasons in the summary (identical reasons are\r\ncondensed and counted) when not running with verbose output. I always wanted\r\nto know why certain tests were skipped. (This requires GNU sort and uniq on\r\nWindows.) ","3":"ENH: Now including SKIP reasons in the summary (identical reasons are\r\ncondensed and counted) when not running with verbose output. I always wanted\r\nto know why certain tests were skipped. (This requires GNU sort and uniq on\r\nWindows.) ","package":"runVimTests.zip","4":"runVimTests.zip","src_id":"10702","5":"10702","creation_date":"1243598377","6":"1243598377"},{"0":"2565","vim_version":"7.0","1":"7.0","script_version":"1.12","2":"1.12","version_comment":"- Added quoting of regexp in runVimTests.sh, which is needed in bash 3.0 and 3.1. Thanks to Anders Th\u00c3\u00b8gersen for the patch. \r\n- Now checking bash version. \r\n- Only exiting with exit code 1 in case of test failures; using code 2 for invocation errors (i.e. wrong command-line arguments) and code 3 for internal errors.  ","3":"- Added quoting of regexp in runVimTests.sh, which is needed in bash 3.0 and 3.1. Thanks to Anders Th\u00c3\u00b8gersen for the patch. \r\n- Now checking bash version. \r\n- Only exiting with exit code 1 in case of test failures; using code 2 for invocation errors (i.e. wrong command-line arguments) and code 3 for internal errors.  ","package":"runVimTests.zip","4":"runVimTests.zip","src_id":"10208","5":"10208","creation_date":"1237057604","6":"1237057604"},{"0":"2565","vim_version":"7.0","1":"7.0","script_version":"1.11","2":"1.11","version_comment":"- TAP output is now parsed for SKIP and TODO directives, and the \"Bail out\" message. \r\n- TODO TAP tests are included in the test output like failing tests. ","3":"- TAP output is now parsed for SKIP and TODO directives, and the \"Bail out\" message. \r\n- TODO TAP tests are included in the test output like failing tests. ","package":"runVimTests.zip","4":"runVimTests.zip","src_id":"10190","5":"10190","creation_date":"1236895824","6":"1236895824"},{"0":"2565","vim_version":"7.0","1":"7.0","script_version":"1.10","2":"1.10","version_comment":"- runVimTests drivers now also count test files (*.vim). \r\n- ENH: Message output is now parsed for signals to the test driver. Implemented signals: BAILOUT!, ERROR, SKIP, SKIP(out), SKIP(msgout), SKIP(tap). ","3":"- runVimTests drivers now also count test files (*.vim). \r\n- ENH: Message output is now parsed for signals to the test driver. Implemented signals: BAILOUT!, ERROR, SKIP, SKIP(out), SKIP(msgout), SKIP(tap). ","package":"runVimTests.zip","4":"runVimTests.zip","src_id":"10177","5":"10177","creation_date":"1236783289","6":"1236783289"},{"0":"2565","vim_version":"7.0","1":"7.0","script_version":"1.01","2":"1.01","version_comment":"Added annotated example tests. ","3":"Added annotated example tests. ","package":"runVimTests.zip","4":"runVimTests.zip","src_id":"10094","5":"10094","creation_date":"1236109055","6":"1236109055"},{"0":"2565","vim_version":"7.0","1":"7.0","script_version":"1.00","2":"1.00","version_comment":"Initial upload","3":"Initial upload","package":"runVimTests.zip","4":"runVimTests.zip","src_id":"10086","5":"10086","creation_date":"1236010602","6":"1236010602"}]},"2564":{"script_id":"2564","0":"2564","script_name":"simple_comments.vim","1":"simple_comments.vim","script_type":"utility","2":"utility","summary":"Add and remove comments from lines","3":"Add and remove comments from lines","description":"This is a plugin to comment out or remove comments from\r\nlines in sourcecode using the comments in the commentsring\r\nvariable. It is intended to be as simple as possible and can only\r\nhandle the commenting or removal of comments from whole \r\nlines.\r\n\r\nThere are much more sofisticated comment scripts on vim.org, but \r\nI wanted something simple, so this script was created.\r\n\r\ngithub: https:\/\/github.com\/aklt\/vim-simple_comments\r\n","4":"This is a plugin to comment out or remove comments from\r\nlines in sourcecode using the comments in the commentsring\r\nvariable. It is intended to be as simple as possible and can only\r\nhandle the commenting or removal of comments from whole \r\nlines.\r\n\r\nThere are much more sofisticated comment scripts on vim.org, but \r\nI wanted something simple, so this script was created.\r\n\r\ngithub: https:\/\/github.com\/aklt\/vim-simple_comments\r\n","install_details":"Uznip simple_comments.vba.zip, open the file and source it.  Installation requires the VimBall plugin.","5":"Uznip simple_comments.vba.zip, open the file and source it.  Installation requires the VimBall plugin.","first_name":"Anders","6":"Anders","last_name":"Th\u00c3\u00b8gersen","7":"Th\u00c3\u00b8gersen","releases":[{"0":"2564","vim_version":"7.0","1":"7.0","script_version":"1.2","2":"1.2","version_comment":"Updated comment text and put script on github","3":"Updated comment text and put script on github","package":"simple_comments.vba.gz","4":"simple_comments.vba.gz","src_id":"14667","5":"14667","creation_date":"1293809764","6":"1293809764"},{"0":"2564","vim_version":"7.0","1":"7.0","script_version":"1.1","2":"1.1","version_comment":"Changed version numbering and added use of GetLatestVimScripts","3":"Changed version numbering and added use of GetLatestVimScripts","package":"simple_comments.vba.gz","4":"simple_comments.vba.gz","src_id":"10092","5":"10092","creation_date":"1236092857","6":"1236092857"},{"0":"2564","vim_version":"7.0","1":"7.0","script_version":"253","2":"253","version_comment":"Added syntax specific commenting.  If a dictionary contains an entry for the current filetype then syntax comments will be used instead. This is useful when editing html or php files that may contain languages requiring more than one type of comment... Script s still simple, though :-)","3":"Added syntax specific commenting.  If a dictionary contains an entry for the current filetype then syntax comments will be used instead. This is useful when editing html or php files that may contain languages requiring more than one type of comment... Script s still simple, though :-)","package":"simple_comments.vba.zip","4":"simple_comments.vba.zip","src_id":"10089","5":"10089","creation_date":"1236052707","6":"1236052707"},{"0":"2564","vim_version":"6.0","1":"6.0","script_version":"249","2":"249","version_comment":"Bugfix.  Spaces are now handled correctly","3":"Bugfix.  Spaces are now handled correctly","package":"simple_comments.vba.zip","4":"simple_comments.vba.zip","src_id":"10076","5":"10076","creation_date":"1235957541","6":"1235957541"}]},"2563":{"script_id":"2563","0":"2563","script_name":"bufMenuToo","1":"bufMenuToo","script_type":"utility","2":"utility","summary":"keeps buffer menu at constant length, for tearoff usage","3":"keeps buffer menu at constant length, for tearoff usage","description":"The BufMenuToo Plugin makes the Buffer Menu remain a constant size for\r\nuse as tearoff menu. Now it can permanently stay open to show your \r\nbuffers and still keeps a minimum size.\r\n\r\nversion: 0.0.1\r\n\r\nINCOMPATIBLE with MiniBufExplorer","4":"The BufMenuToo Plugin makes the Buffer Menu remain a constant size for\r\nuse as tearoff menu. Now it can permanently stay open to show your \r\nbuffers and still keeps a minimum size.\r\n\r\nversion: 0.0.1\r\n\r\nINCOMPATIBLE with MiniBufExplorer","install_details":"just drop it in your .vim\/plugin folder","5":"just drop it in your .vim\/plugin folder","first_name":"joe","6":"joe","last_name":"richter","7":"richter","releases":[{"0":"2563","vim_version":"7.0","1":"7.0","script_version":"0.0.1","2":"0.0.1","version_comment":"Initial upload","3":"Initial upload","package":"bufMenuToo.vim","4":"bufMenuToo.vim","src_id":"10068","5":"10068","creation_date":"1235942926","6":"1235942926"}]},"2562":{"script_id":"2562","0":"2562","script_name":"ansi_blows.vim","1":"ansi_blows.vim","script_type":"color scheme","2":"color scheme","summary":"Matching ANSI colorscheme for gVim and vim","3":"Matching ANSI colorscheme for gVim and vim","description":"This is a color scheme that I use to make my gVim identical (other than spell highlighting) to Vim.  In order to do this, I set the variables in the ansi_blows.vim colorscheme to exactly match the colors that my terminal emulator uses.  I've tweaked these values in both places to be very readable, to me.  Of course I suggest tweaking them for your own needs, or to match the colors that you are used to in your terminal emulator.  For convenience, I've included in comments some common color sets that I'm aware of.\r\n\r\nNote, I made this on vim 7.2, it may not work on any prior versions, but it probably does.","4":"This is a color scheme that I use to make my gVim identical (other than spell highlighting) to Vim.  In order to do this, I set the variables in the ansi_blows.vim colorscheme to exactly match the colors that my terminal emulator uses.  I've tweaked these values in both places to be very readable, to me.  Of course I suggest tweaking them for your own needs, or to match the colors that you are used to in your terminal emulator.  For convenience, I've included in comments some common color sets that I'm aware of.\r\n\r\nNote, I made this on vim 7.2, it may not work on any prior versions, but it probably does.","install_details":"Copy the script to ~\/.vim\/colors\r\nTweak the color variables defined near the top of the script\r\nAdd \"colors ansi_blows\" to your .vimrc (and, if they are separate, your .gvimrc).\r\nEnjoy a consistent vim environment.","5":"Copy the script to ~\/.vim\/colors\r\nTweak the color variables defined near the top of the script\r\nAdd \"colors ansi_blows\" to your .vimrc (and, if they are separate, your .gvimrc).\r\nEnjoy a consistent vim environment.","first_name":"Brandon","6":"Brandon","last_name":"Low","7":"Low","releases":[{"0":"2562","vim_version":"7.0","1":"7.0","script_version":"0.6","2":"0.6","version_comment":"Added Rasterman's colors to the example color sets.","3":"Added Rasterman's colors to the example color sets.","package":"ansi_blows.vim","4":"ansi_blows.vim","src_id":"10067","5":"10067","creation_date":"1235938095","6":"1235938095"},{"0":"2562","vim_version":"7.2","1":"7.2","script_version":"0.5","2":"0.5","version_comment":"Initial upload","3":"Initial upload","package":"ansi_blows.vim","4":"ansi_blows.vim","src_id":"10065","5":"10065","creation_date":"1235871811","6":"1235871811"}]},"2561":{"script_id":"2561","0":"2561","script_name":"NumberToEnglish","1":"NumberToEnglish","script_type":"utility","2":"utility","summary":"Converts Arabic numerals to English","3":"Converts Arabic numerals to English","description":"Converts a number (such as -1234) to English (negative one thousand two hundred thirty four); handles the biggest integer Vim can work with (billions).\r\n\r\nThis actually figures out the English value by crunching the numbers (not through abbreviations) and thus doesn't have any startup overhead.\r\n\r\nUsage: call the function NumberToEnglish and pass it the number; optionally, a second parameter can be passed in which, if not 1, will cause the return\r\nvalue's first letter to be capitalized (Two hundred thirty four vs. two hundred thirty four).\r\n\r\nTwo insert-mode mappings have been provided for convenience to make this happen on the currently typed number while typing.\r\n\r\n<Plug>NumberToEnglish: converts the (positive only) number to English\r\n\r\n<Plug>CNumberToEnglish: converts the (positive only) number to English, capitalizing the first letter\r\n\r\nTwo identical version of these mappings that start with a D (for \"Detailed\") will append the original number in parentheses after the expansion.","4":"Converts a number (such as -1234) to English (negative one thousand two hundred thirty four); handles the biggest integer Vim can work with (billions).\r\n\r\nThis actually figures out the English value by crunching the numbers (not through abbreviations) and thus doesn't have any startup overhead.\r\n\r\nUsage: call the function NumberToEnglish and pass it the number; optionally, a second parameter can be passed in which, if not 1, will cause the return\r\nvalue's first letter to be capitalized (Two hundred thirty four vs. two hundred thirty four).\r\n\r\nTwo insert-mode mappings have been provided for convenience to make this happen on the currently typed number while typing.\r\n\r\n<Plug>NumberToEnglish: converts the (positive only) number to English\r\n\r\n<Plug>CNumberToEnglish: converts the (positive only) number to English, capitalizing the first letter\r\n\r\nTwo identical version of these mappings that start with a D (for \"Detailed\") will append the original number in parentheses after the expansion.","install_details":"Just drop it into your plugin directory and, if you like, set up the mappings; for example:\r\n\r\nimap <leader>ne <Plug>NumberToEnglish\r\nimap <leader>nd <Plug>DNumberToEnglish\r\nimap <leader>nE <Plug>CNumberToEnglish\r\nimap <leader>nD <Plug>DCNumberToEnglish\r\n\r\nSee the notes for version 1.3 if the introduction of another language is desired; the system isn't perfect, but should work for most Indo-European languages that follow the same basic numbering scheme as English (French is provided as an example).\r\n\r\nNote: Requires the use of GetVar (http:\/\/vim.sourceforge.net\/scripts\/script.php?script_id=353).","5":"Just drop it into your plugin directory and, if you like, set up the mappings; for example:\r\n\r\nimap <leader>ne <Plug>NumberToEnglish\r\nimap <leader>nd <Plug>DNumberToEnglish\r\nimap <leader>nE <Plug>CNumberToEnglish\r\nimap <leader>nD <Plug>DCNumberToEnglish\r\n\r\nSee the notes for version 1.3 if the introduction of another language is desired; the system isn't perfect, but should work for most Indo-European languages that follow the same basic numbering scheme as English (French is provided as an example).\r\n\r\nNote: Requires the use of GetVar (http:\/\/vim.sourceforge.net\/scripts\/script.php?script_id=353).","first_name":"Salman","6":"Salman","last_name":"Halim","7":"Halim","releases":[{"0":"2561","vim_version":"7.0","1":"7.0","script_version":"1.5","2":"1.5","version_comment":"Significant number of changes; all credit goes to Ingo Karkat--thank you, Ingo:\r\n\r\n- Added parallel function and mappings for ordinal numbers (\"forty-second\"), also configurable via g:numberToEnglish_ordinal_... variables.\r\n- Made remaining hard-coded words configurable via variables g:numberToEnglish_zero, g:numberToEnglish_negative.\r\n- Allowed to use hyphen separator for numbers in range 21-99; g:numberToEnglish_useHyphen.\r\n- Split into plugin and autoload script to minimize footprint.\r\n- Change default to let g:numberToEnglish_useAnd = 1\r\n- Fix additional comma in \"one thousand, and one\".\r\n","3":"Significant number of changes; all credit goes to Ingo Karkat--thank you, Ingo:\r\n\r\n- Added parallel function and mappings for ordinal numbers (\"forty-second\"), also configurable via g:numberToEnglish_ordinal_... variables.\r\n- Made remaining hard-coded words configurable via variables g:numberToEnglish_zero, g:numberToEnglish_negative.\r\n- Allowed to use hyphen separator for numbers in range 21-99; g:numberToEnglish_useHyphen.\r\n- Split into plugin and autoload script to minimize footprint.\r\n- Change default to let g:numberToEnglish_useAnd = 1\r\n- Fix additional comma in \"one thousand, and one\".\r\n","package":"NumberToEnglish enh-ordinal.zip","4":"NumberToEnglish enh-ordinal.zip","src_id":"17784","5":"17784","creation_date":"1334683480","6":"1334683480"},{"0":"2561","vim_version":"7.0","1":"7.0","script_version":"1.4","2":"1.4","version_comment":"Version 1.4\r\n\r\nAdded an option to put in the word \"and\" (nine hundred AND twenty); off by default to retain old behavior:\r\n\r\nlet g:numberToEnglish_useAnd = 1\r\n\r\nAdded another configuration variable (French, in this example):\r\n\r\nlet g:numberToEnglish_and = \"et\"\r\n\r\nSections are now separated by commas; for example, \"12345\" becomes \"twelve thousand, three hundred and forty five\"","3":"Version 1.4\r\n\r\nAdded an option to put in the word \"and\" (nine hundred AND twenty); off by default to retain old behavior:\r\n\r\nlet g:numberToEnglish_useAnd = 1\r\n\r\nAdded another configuration variable (French, in this example):\r\n\r\nlet g:numberToEnglish_and = \"et\"\r\n\r\nSections are now separated by commas; for example, \"12345\" becomes \"twelve thousand, three hundred and forty five\"","package":"NumberToEnglish.vim","4":"NumberToEnglish.vim","src_id":"13994","5":"13994","creation_date":"1286289196","6":"1286289196"},{"0":"2561","vim_version":"7.0","1":"7.0","script_version":"1.3","2":"1.3","version_comment":"Made the plugin accept global values for overriding the returned string; useful for changing the language, for example. Place the following in your _vimrc for\r\nFrench:\r\n\r\nlet g:numberToEnglish_digits = [ \"\", \"un\",   \"deux\",  \"trois\",  \"quatre\",   \"cinq\",      \"six\",      \"sept\",         \"huit\",         \"neuf\" ]\r\nlet g:numberToEnglish_teens  = [ \"\", \"onze\", \"douze\", \"treize\", \"quatorze\", \"quinze\",    \"seize\",    \"dix-sept\",     \"dix-huit\",     \"dix-neuf\" ]\r\nlet g:numberToEnglish_tens   = [ \"\", \"dix\",  \"vingt\", \"trente\", \"quarante\", \"cinquante\", \"soixante\", \"soixante dix\", \"quatre vingt\", \"quatre vingt dix\" ]\r\n\r\nlet g:numberToEnglish_scale = [ \"\", \"mille\", \"million\", \"billion\" ]\r\n\r\nlet g:numberToEnglish_hundred = \"cent\"\r\n\r\nThis change necessitates the use of GetVar (http:\/\/vim.sourceforge.net\/scripts\/script.php?script_id=353). Technically, the usage of GetVar allows the setting\r\nof any combination of these variables on a per-window, buffer or tab level (allowing different languages, capitalizations, etc., depending upon the buffer\r\ntype, for example).\r\n","3":"Made the plugin accept global values for overriding the returned string; useful for changing the language, for example. Place the following in your _vimrc for\r\nFrench:\r\n\r\nlet g:numberToEnglish_digits = [ \"\", \"un\",   \"deux\",  \"trois\",  \"quatre\",   \"cinq\",      \"six\",      \"sept\",         \"huit\",         \"neuf\" ]\r\nlet g:numberToEnglish_teens  = [ \"\", \"onze\", \"douze\", \"treize\", \"quatorze\", \"quinze\",    \"seize\",    \"dix-sept\",     \"dix-huit\",     \"dix-neuf\" ]\r\nlet g:numberToEnglish_tens   = [ \"\", \"dix\",  \"vingt\", \"trente\", \"quarante\", \"cinquante\", \"soixante\", \"soixante dix\", \"quatre vingt\", \"quatre vingt dix\" ]\r\n\r\nlet g:numberToEnglish_scale = [ \"\", \"mille\", \"million\", \"billion\" ]\r\n\r\nlet g:numberToEnglish_hundred = \"cent\"\r\n\r\nThis change necessitates the use of GetVar (http:\/\/vim.sourceforge.net\/scripts\/script.php?script_id=353). Technically, the usage of GetVar allows the setting\r\nof any combination of these variables on a per-window, buffer or tab level (allowing different languages, capitalizations, etc., depending upon the buffer\r\ntype, for example).\r\n","package":"NumberToEnglish.vim","4":"NumberToEnglish.vim","src_id":"10133","5":"10133","creation_date":"1236350551","6":"1236350551"},{"0":"2561","vim_version":"7.0","1":"7.0","script_version":"1.2","2":"1.2","version_comment":"Added two new mappings:\r\n\r\n<Plug>DNumberToEnglish and <Plug>DCNumberToEnglish -- the D is short for \"Detailed\".\r\n\r\nDiffers from the versions without the D in that it places the original number at the end of the expanded version:\r\n\r\nThus, 12341234 becomes twelve million three hundred forty one thousand two hundred thirty four (12341234).\r\n\r\nVersion 1.1 (not uploaded):\r\n\r\nTook the hard-coded values out of the functions into script-local variables -- no sense defining them every time.\r\n","3":"Added two new mappings:\r\n\r\n<Plug>DNumberToEnglish and <Plug>DCNumberToEnglish -- the D is short for \"Detailed\".\r\n\r\nDiffers from the versions without the D in that it places the original number at the end of the expanded version:\r\n\r\nThus, 12341234 becomes twelve million three hundred forty one thousand two hundred thirty four (12341234).\r\n\r\nVersion 1.1 (not uploaded):\r\n\r\nTook the hard-coded values out of the functions into script-local variables -- no sense defining them every time.\r\n","package":"NumberToEnglish.vim","4":"NumberToEnglish.vim","src_id":"10090","5":"10090","creation_date":"1236054524","6":"1236054524"},{"0":"2561","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"NumberToEnglish.vim","4":"NumberToEnglish.vim","src_id":"10059","5":"10059","creation_date":"1235756466","6":"1235756466"}]},"2560":{"script_id":"2560","0":"2560","script_name":"numbertotext","1":"numbertotext","script_type":"utility","2":"utility","summary":"replace the numbers with the equivalent text to it","3":"replace the numbers with the equivalent text to it","description":"When you want the number to be converted to its relevant text\/string, it does that for you. Say 781 need to be converted to \"seven hundred eighty one\". \r\n\r\nJust type _781 which will be replaced by seven hundred eighty one.\r\n\r\nThis script can be used for making this kind of conversion for the numbers 1 to 10000.\r\n\r\nWARNING:\r\nAs this file contains 10000 abbreviation, it will take a couple of seconds to process when you open a file in vim editor.\r\n\r\nSUGGESTION:\r\nso disable this plugin whenever not needed.\r\n( comment the pasted line in .vimrc file )","4":"When you want the number to be converted to its relevant text\/string, it does that for you. Say 781 need to be converted to \"seven hundred eighty one\". \r\n\r\nJust type _781 which will be replaced by seven hundred eighty one.\r\n\r\nThis script can be used for making this kind of conversion for the numbers 1 to 10000.\r\n\r\nWARNING:\r\nAs this file contains 10000 abbreviation, it will take a couple of seconds to process when you open a file in vim editor.\r\n\r\nSUGGESTION:\r\nso disable this plugin whenever not needed.\r\n( comment the pasted line in .vimrc file )","install_details":"Copy the zip archive numbertotext.zip  to $HOME\/.vim\/ and run\r\n        unzip numbertotext.zip\r\nAdd the following line in $HOME\/.vimrc,\r\n        source $HOME\/.vim\/numbertotext.vim","5":"Copy the zip archive numbertotext.zip  to $HOME\/.vim\/ and run\r\n        unzip numbertotext.zip\r\nAdd the following line in $HOME\/.vimrc,\r\n        source $HOME\/.vim\/numbertotext.vim","first_name":"sathiyamoorthy","6":"sathiyamoorthy","last_name":"subramanian","7":"subramanian","releases":[{"0":"2560","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"numbertotext.zip","4":"numbertotext.zip","src_id":"10057","5":"10057","creation_date":"1235750218","6":"1235750218"}]},"2559":{"script_id":"2559","0":"2559","script_name":"gams.vim","1":"gams.vim","script_type":"syntax","2":"syntax","summary":"Simple syntax highlighting for GAMS modelling software (www.gams.com)","3":"Simple syntax highlighting for GAMS modelling software (www.gams.com)","description":"As far as I know, there is no syntax highlighting for GAMS modeling language in vim. Here goes one, works with gvim. No other functionality, just the highlighting. ","4":"As far as I know, there is no syntax highlighting for GAMS modeling language in vim. Here goes one, works with gvim. No other functionality, just the highlighting. ","install_details":"Put\r\n\r\nau BufEnter *.gms set ft=gams\r\n\r\nin your .vimrc, or run \r\n\r\nset ft=gams\r\n\r\nafter opening your .gms file.","5":"Put\r\n\r\nau BufEnter *.gms set ft=gams\r\n\r\nin your .vimrc, or run \r\n\r\nset ft=gams\r\n\r\nafter opening your .gms file.","first_name":"David","6":"David","last_name":"Vonka","7":"Vonka","releases":[{"0":"2559","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"gams.vim","4":"gams.vim","src_id":"10052","5":"10052","creation_date":"1235743479","6":"1235743479"}]},"2558":{"script_id":"2558","0":"2558","script_name":"Match Bracket for Objective-C","1":"Match Bracket for Objective-C","script_type":"ftplugin","2":"ftplugin","summary":"Automatically inserts matching starting bracket when ] is pressed.","3":"Automatically inserts matching starting bracket when ] is pressed.","description":"This is essentially TextMate's \"Insert Matching Start Bracket\" feature implemented in vim script. Makes it a lot more pleasant to write Objective-C.\r\n\r\nJust type ] in insert mode after an object or method you want to wrap in brackets and this will wrap it appropriately; to escape out of it once you're finished, simply type ] again.\r\n\r\nFor instance, where | is the cursor:\r\n\r\n\"foo|\" becomes \"[foo |]\" after ] is pressed.\r\n\"foo bar|\" becomes \"[foo bar]|\"\r\n\"foo: bar|\" becomes \"foo: [bar |]\"\r\n\"foo bar: baz|\" becomes \"[foo bar: baz]|\"\r\n\r\nCertain useful keywords are also wrapped intelligently, for example:\r\n\"return foo|\" becomes \"return [foo ]|\"\r\n\"@selector: foo|\" becomes \"[@selector: foo]|\"\r\n\r\nHope you like it!","4":"This is essentially TextMate's \"Insert Matching Start Bracket\" feature implemented in vim script. Makes it a lot more pleasant to write Objective-C.\r\n\r\nJust type ] in insert mode after an object or method you want to wrap in brackets and this will wrap it appropriately; to escape out of it once you're finished, simply type ] again.\r\n\r\nFor instance, where | is the cursor:\r\n\r\n\"foo|\" becomes \"[foo |]\" after ] is pressed.\r\n\"foo bar|\" becomes \"[foo bar]|\"\r\n\"foo: bar|\" becomes \"foo: [bar |]\"\r\n\"foo bar: baz|\" becomes \"[foo bar: baz]|\"\r\n\r\nCertain useful keywords are also wrapped intelligently, for example:\r\n\"return foo|\" becomes \"return [foo ]|\"\r\n\"@selector: foo|\" becomes \"[@selector: foo]|\"\r\n\r\nHope you like it!","install_details":"Move objc_matchbracket.vim to ~\/.vim\/ftplugin or equivalent.","5":"Move objc_matchbracket.vim to ~\/.vim\/ftplugin or equivalent.","first_name":"Michael","6":"Michael","last_name":"Sanders","7":"Sanders","releases":[{"0":"2558","vim_version":"7.0","1":"7.0","script_version":"0.8","2":"0.8","version_comment":"Fixed behavior when dealing with colons (e.g. \"foo bar: baz]\") and when popup menu is visible.","3":"Fixed behavior when dealing with colons (e.g. \"foo bar: baz]\") and when popup menu is visible.","package":"objc_matchbracket.vim","4":"objc_matchbracket.vim","src_id":"10794","5":"10794","creation_date":"1244585601","6":"1244585601"},{"0":"2558","vim_version":"7.0","1":"7.0","script_version":"0.5","2":"0.5","version_comment":"Fixed some bugs, and fixed behavior when wrapping past a symbols such as \"!\" (e.g. !foo bar -> ![foo bar]).","3":"Fixed some bugs, and fixed behavior when wrapping past a symbols such as \"!\" (e.g. !foo bar -> ![foo bar]).","package":"objc_matchbracket.vim","4":"objc_matchbracket.vim","src_id":"10517","5":"10517","creation_date":"1241379911","6":"1241379911"},{"0":"2558","vim_version":"7.0","1":"7.0","script_version":"0.3","2":"0.3","version_comment":"Fixed a bug when inserting ] after \"return\" or inside braces or parentheses (e.g., \"if (foo])\"), and fixed behavior when inserting ] with no text.","3":"Fixed a bug when inserting ] after \"return\" or inside braces or parentheses (e.g., \"if (foo])\"), and fixed behavior when inserting ] with no text.","package":"objc_matchbracket.vim","4":"objc_matchbracket.vim","src_id":"10327","5":"10327","creation_date":"1238458637","6":"1238458637"},{"0":"2558","vim_version":"7.0","1":"7.0","script_version":"0.2","2":"0.2","version_comment":"Initial upload","3":"Initial upload","package":"objc_matchbracket.vim","4":"objc_matchbracket.vim","src_id":"10048","5":"10048","creation_date":"1235700766","6":"1235700766"}]},"2557":{"script_id":"2557","0":"2557","script_name":"gitignore","1":"gitignore","script_type":"utility","2":"utility","summary":"Set 'wildignore' from .\/.gitignore","3":"Set 'wildignore' from .\/.gitignore","description":"Another one from StackOverflow.\r\n\r\nIt will read your .gitignore file from the directory where you launch vim and parse it, transforming its format into one suitable for wildignore, and then set that option.  Thus, tab-completion won't present those files as options when using vim commands that expect a filename.\r\n\r\nLimitations:\r\n * This will read the .gitignore file from the directory where you launch vim. No effort is made to look for other .gitignore files and parse them. Alternatively, you could specify an absolute path to a file on the first line.\r\n * The wildignore option in vim doesn't support the notion of negating ignores like you can in a .gitignore file. That is, you can't say :set wildignore=*.html,!foo.html to have it ignore all html files except foo.html. Therefore, .gitignore lines that start with ! are simply ignored.","4":"Another one from StackOverflow.\r\n\r\nIt will read your .gitignore file from the directory where you launch vim and parse it, transforming its format into one suitable for wildignore, and then set that option.  Thus, tab-completion won't present those files as options when using vim commands that expect a filename.\r\n\r\nLimitations:\r\n * This will read the .gitignore file from the directory where you launch vim. No effort is made to look for other .gitignore files and parse them. Alternatively, you could specify an absolute path to a file on the first line.\r\n * The wildignore option in vim doesn't support the notion of negating ignores like you can in a .gitignore file. That is, you can't say :set wildignore=*.html,!foo.html to have it ignore all html files except foo.html. Therefore, .gitignore lines that start with ! are simply ignored.","install_details":"Place the file in your plugin directory, such as ~\/.vim\/plugin\/","5":"Place the file in your plugin directory, such as ~\/.vim\/plugin\/","first_name":"Adam","6":"Adam","last_name":"Bellaire","7":"Bellaire","releases":[{"0":"2557","vim_version":"7.0","1":"7.0","script_version":"0.4","2":"0.4","version_comment":"Incorporates fix by Lukas Erlacher to escape commas found in gitignore","3":"Incorporates fix by Lukas Erlacher to escape commas found in gitignore","package":"gitignore.vim","4":"gitignore.vim","src_id":"25252","5":"25252","creation_date":"1495724496","6":"1495724496"},{"0":"2557","vim_version":"7.0","1":"7.0","script_version":"0.3","2":"0.3","version_comment":"Fixes for spaces in filenames from Lukas Erlacher","3":"Fixes for spaces in filenames from Lukas Erlacher","package":"gitignore.vim","4":"gitignore.vim","src_id":"24530","5":"24530","creation_date":"1473862166","6":"1473862166"},{"0":"2557","vim_version":"7.0","1":"7.0","script_version":"0.2","2":"0.2","version_comment":"New functionality by Giuseppe Rota, includes fugitive integration and moves behavior into a callable\/mappable function.","3":"New functionality by Giuseppe Rota, includes fugitive integration and moves behavior into a callable\/mappable function.","package":"gitignore.vim","4":"gitignore.vim","src_id":"18551","5":"18551","creation_date":"1346853233","6":"1346853233"},{"0":"2557","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"gitignore.vim","4":"gitignore.vim","src_id":"10040","5":"10040","creation_date":"1235648576","6":"1235648576"}]},"2556":{"script_id":"2556","0":"2556","script_name":"myprojects","1":"myprojects","script_type":"utility","2":"utility","summary":"Organize\/Navigate projects of files (like IDE\/buffer explorer\/project.vim) ","3":"Organize\/Navigate projects of files (like IDE\/buffer explorer\/project.vim) ","description":"You can use it to set up a list of frequently-accessed files for easy navigation.\r\nThe list of files will be displayed in a window on the left side of the Vim window.\r\nUnlike project.vim, myprojects.vim use indentation instead of mark to define folder.\r\nMain features are file exploration, tags generation, filtering, working directory definition, vim session management, F1 to F12 mapping definition, make definition, errorformat definition, buffers explorer and svn checkout\/update\/add\/commit\/revert\/diff\/blame\/info\/resolved\/log support.\r\nPlease, report any bug to myprojects.vim[..at..]mageekbox.net.\r\nHelp for debug is welcome !","4":"You can use it to set up a list of frequently-accessed files for easy navigation.\r\nThe list of files will be displayed in a window on the left side of the Vim window.\r\nUnlike project.vim, myprojects.vim use indentation instead of mark to define folder.\r\nMain features are file exploration, tags generation, filtering, working directory definition, vim session management, F1 to F12 mapping definition, make definition, errorformat definition, buffers explorer and svn checkout\/update\/add\/commit\/revert\/diff\/blame\/info\/resolved\/log support.\r\nPlease, report any bug to myprojects.vim[..at..]mageekbox.net.\r\nHelp for debug is welcome !","install_details":"Download vimball, open it with vim, and do :so %.\r\nAfter that, reopen vim and do <leader>p (ie \\p if <leader> has its default value) or :MyProjectsToggle.\r\nIt's an alpha-version (release early, release often), so do regular :GLVS to be up-to-date (see :h GLVS for more information).\r\n<leader>-p open panel like command :MyProjectsToggle.\r\nYou can also map \"<Plug>MyProjectsToggle\" to open panel : map <silent> <Tab> <Plug>MyProjectsToggle.\r\nIn panel :\r\n<Return> open file or folder under cursor.\r\n<2-Leftmouse> open file or folder under mouse cursor.\r\n<S-Return> open file or folder under cursor in an horizontaly splitted window.\r\n<S-2-Leftmouse> open file or folder under mouse cursor in an horizontaly splitted window.\r\n<C-Return> open file or folder under cursor in a verticaly splitted window.\r\n<C-2-Leftmouse> open file or folder under mouse cursor in a verticaly splitted window.\r\n<C-Tab> go to previous window.\r\n<C-Right> increase panel size of g:myprojects_resize_step.\r\n<C-l> increase panel size of g:myprojects_resize_step.\r\n<C-Left> decrease panel size of g:myprojects_resize_step.\r\n<C-h> decrease panel size of g:myprojects_resize_step.\r\n<C-Space> set panel fullscreen, or set it to its size before <C-Space>.\r\n<LocalLeader>d delete file under cursor.\r\n<LocalLeader>c create a project.\r\n<LocalLeader>r refresh line where is cursor.\r\n<LocalLeader>R refresh folder where is cursor.\r\n<LocalLeader>g make grep against folder where is cursor.\r\n<LocalLeader>t generate tags file for project where is cursor.\r\n<LocalLeader>e explore folder where is cursor.\r\n<LocalLeader>E explore folder where is cursor in an horizontaly splitted window.\r\n<LocalLeader>a append file under cursor to buffer in previous window.\r\n<LocalLeader>s save session for project where is cursor.\r\n<LocalLeader>S load session for project where is cursor.\r\n<LocalLeader><A-s> delete session for project where is cursor.\r\n<LocalLeader>p set path for file or folder under cursor.\r\n<LocalLeader>P update nested path for file or folder under cursor.\r\n<LocalLeader>f set filter for folder where is curosr.\r\n<LocalLeader>F update nested filter for file or folder where is cursor.\r\n<LocalLeader>w set workigng directory for file or folder where is cursor.\r\n<LocalLeader>W update nested working directory for folder where is cursor.\r\n<LocalLeader>m set F1 to F12 mappings for file or folder where is cursor.\r\n<LocalLeader>M update nested mappings for file or folder where is cursor.\r\n<LocalLeader>i display in status line path of filer or folder under cursor.\r\n<LocalLeader>v display in status line myprojects.vim's version.\r\n<LocalLeader>V display in status line myprojects.vim's file.\r\n<LocalLeader>b display buffers of project where is cursor.\r\n<LocalLeader>ss do a svn status for file or folder under cursor and display result in a separate window.\r\n<LocalLeader>sc do a svn commit for file or folder under cursor, you can select file and define log message in a separate window.\r\n<LocalLeader>su do a svn update for file or folder under cursor and display result in a separate window.\r\n<LocalLeader>sd do a svn diff for file under cursor and display result in two separate window in diff mode.\r\n<LocalLeader>sb do a svn blame for file under cursor and display result in a window.\r\n<LocalLeader>sr do a svn revert for file under cursor and display result in a separate window.\r\n<LocalLeader>sa do a svn add for file under cursor and display result in a separate window.\r\n<LocalLeader>sC do a svn checkout and create the corresponding project.\r\n<LocalLeader>si do a svn info on current file or folder.\r\n<LocalLeader>sl do a svn log on current file or folder.\r\n<LocalLeader>src do a svn resolved on current file or folder.\r\n<LocalLeader>k define make program (see :h :make for more informations) for current file\/folder.\r\n<LocalLeader>K update make program (see :h :make for more informations) for current file\/folder.\r\n<LocalLeader>ef define errorformat (see :h errorformat for more informations) for current file\/folder.\r\n<LocalLeader>Ef update errorformat (see :h errorformat for more informations) for current file\/folder.\r\n<LocalLeader>df define project type's preferences (path, working directory, mappings, etc).\r\n<LocalLeader>te set test attribute value, use to find test file of a file open from myprojects.\r\n<LocalLeader>Te update test attribute value. \r\n<LocalLeader>et from a file opened from myprojects open its test file (if 'foo.php' was opened from myprojects.vim and test attribute's value is '.test.php', <localLeader>et open the file 'foot.test.php' in a horizontaly splitted window).\r\nYou can open file in svn window like in myproject's panel.\r\nYou can do a diff from working window with <A-d>.\r\nBy default, LocalLeader is '\\\\'.\r\nYou can remap it with \"let maplocalleader = ','\" in your .vimrc, for example.\r\nFolder can have filters against file on your hard drive.\r\nFilters are vim patterns (see :h patterns for more informations).\r\nIf a working directory is defined on a folder or its parents, a \"cd\" vim command is done when a file in the folder is open, see :h :cd for more informations.\r\nMoreover, you can define normal mapping for <F1> to <F12> for each folder in a project.\r\nFor example, you can map F10 with :!php -l %:p 2>&1<CR> to check php syntax of a php file opened with myprojects.\r\nYou can also define make and errorformat for each file or folder, see :h make and :h errorformat for more information.\r\nGetLatestVimScripts is also supported, see :h GLVS for more information about it.\r\ng:myprojects_width variable set the panel's width, default is 30.\r\ng:myprojects_file variable set the myproject's file name, default is ~\/.myprojects.\r\ng:myprojects_tags_file variable set the tags file name, default is .tags.\r\ng:myprojects_auto_close variable close the panel when a file is open, default is 0.\r\ng:myprojects_auto_open variable open automaticaly myprojects.vim at vim startup.\r\ng:myprojects_syntax variable activate syntax highlighting, default is 1.\r\ng:myprojects_display_empty_folder variable display empty folder, default is 0.\r\ng:myprojects_auto_resize variable resize the panel to its default size when a file is open, default is 0.\r\ng:myprojects_resize_step define the step used to resize panel with <C-Left> and <C-Right>, default is 10.\r\ng:myprojects_display_number display line number in panel, default is 0.\r\ng:myprojects_display_path_in_statusline display path of current file in status line, default is 1.\r\ng:myprojects_cursorline display cursor line, default is 1.\r\ng:myprojects_cursorcolumn display cursor column, default is 1.\r\ng:myprojects_foldcolumn display folder column, default is 0, see :h foldcolumn for more informations.\r\nctags or exctags must be installed to generate tags file.\r\ng:myprojects_tags_generator define tag generator utility, default is 'exctags'.\r\ng:myprojects_new_file_on_bottom add new file on bottom of folder on refresh, default is 1.\r\ng:myprojects_svn_sort sort path in svn window, default is 1.\r\ng:myprojects_autowrite auto save g:myprojects_file after refresh, default is 1.\r\nYou can override default value of these variables with \"let g:myprojects_svn_sort = 0\" in your .vimrc, for example.","5":"Download vimball, open it with vim, and do :so %.\r\nAfter that, reopen vim and do <leader>p (ie \\p if <leader> has its default value) or :MyProjectsToggle.\r\nIt's an alpha-version (release early, release often), so do regular :GLVS to be up-to-date (see :h GLVS for more information).\r\n<leader>-p open panel like command :MyProjectsToggle.\r\nYou can also map \"<Plug>MyProjectsToggle\" to open panel : map <silent> <Tab> <Plug>MyProjectsToggle.\r\nIn panel :\r\n<Return> open file or folder under cursor.\r\n<2-Leftmouse> open file or folder under mouse cursor.\r\n<S-Return> open file or folder under cursor in an horizontaly splitted window.\r\n<S-2-Leftmouse> open file or folder under mouse cursor in an horizontaly splitted window.\r\n<C-Return> open file or folder under cursor in a verticaly splitted window.\r\n<C-2-Leftmouse> open file or folder under mouse cursor in a verticaly splitted window.\r\n<C-Tab> go to previous window.\r\n<C-Right> increase panel size of g:myprojects_resize_step.\r\n<C-l> increase panel size of g:myprojects_resize_step.\r\n<C-Left> decrease panel size of g:myprojects_resize_step.\r\n<C-h> decrease panel size of g:myprojects_resize_step.\r\n<C-Space> set panel fullscreen, or set it to its size before <C-Space>.\r\n<LocalLeader>d delete file under cursor.\r\n<LocalLeader>c create a project.\r\n<LocalLeader>r refresh line where is cursor.\r\n<LocalLeader>R refresh folder where is cursor.\r\n<LocalLeader>g make grep against folder where is cursor.\r\n<LocalLeader>t generate tags file for project where is cursor.\r\n<LocalLeader>e explore folder where is cursor.\r\n<LocalLeader>E explore folder where is cursor in an horizontaly splitted window.\r\n<LocalLeader>a append file under cursor to buffer in previous window.\r\n<LocalLeader>s save session for project where is cursor.\r\n<LocalLeader>S load session for project where is cursor.\r\n<LocalLeader><A-s> delete session for project where is cursor.\r\n<LocalLeader>p set path for file or folder under cursor.\r\n<LocalLeader>P update nested path for file or folder under cursor.\r\n<LocalLeader>f set filter for folder where is curosr.\r\n<LocalLeader>F update nested filter for file or folder where is cursor.\r\n<LocalLeader>w set workigng directory for file or folder where is cursor.\r\n<LocalLeader>W update nested working directory for folder where is cursor.\r\n<LocalLeader>m set F1 to F12 mappings for file or folder where is cursor.\r\n<LocalLeader>M update nested mappings for file or folder where is cursor.\r\n<LocalLeader>i display in status line path of filer or folder under cursor.\r\n<LocalLeader>v display in status line myprojects.vim's version.\r\n<LocalLeader>V display in status line myprojects.vim's file.\r\n<LocalLeader>b display buffers of project where is cursor.\r\n<LocalLeader>ss do a svn status for file or folder under cursor and display result in a separate window.\r\n<LocalLeader>sc do a svn commit for file or folder under cursor, you can select file and define log message in a separate window.\r\n<LocalLeader>su do a svn update for file or folder under cursor and display result in a separate window.\r\n<LocalLeader>sd do a svn diff for file under cursor and display result in two separate window in diff mode.\r\n<LocalLeader>sb do a svn blame for file under cursor and display result in a window.\r\n<LocalLeader>sr do a svn revert for file under cursor and display result in a separate window.\r\n<LocalLeader>sa do a svn add for file under cursor and display result in a separate window.\r\n<LocalLeader>sC do a svn checkout and create the corresponding project.\r\n<LocalLeader>si do a svn info on current file or folder.\r\n<LocalLeader>sl do a svn log on current file or folder.\r\n<LocalLeader>src do a svn resolved on current file or folder.\r\n<LocalLeader>k define make program (see :h :make for more informations) for current file\/folder.\r\n<LocalLeader>K update make program (see :h :make for more informations) for current file\/folder.\r\n<LocalLeader>ef define errorformat (see :h errorformat for more informations) for current file\/folder.\r\n<LocalLeader>Ef update errorformat (see :h errorformat for more informations) for current file\/folder.\r\n<LocalLeader>df define project type's preferences (path, working directory, mappings, etc).\r\n<LocalLeader>te set test attribute value, use to find test file of a file open from myprojects.\r\n<LocalLeader>Te update test attribute value. \r\n<LocalLeader>et from a file opened from myprojects open its test file (if 'foo.php' was opened from myprojects.vim and test attribute's value is '.test.php', <localLeader>et open the file 'foot.test.php' in a horizontaly splitted window).\r\nYou can open file in svn window like in myproject's panel.\r\nYou can do a diff from working window with <A-d>.\r\nBy default, LocalLeader is '\\\\'.\r\nYou can remap it with \"let maplocalleader = ','\" in your .vimrc, for example.\r\nFolder can have filters against file on your hard drive.\r\nFilters are vim patterns (see :h patterns for more informations).\r\nIf a working directory is defined on a folder or its parents, a \"cd\" vim command is done when a file in the folder is open, see :h :cd for more informations.\r\nMoreover, you can define normal mapping for <F1> to <F12> for each folder in a project.\r\nFor example, you can map F10 with :!php -l %:p 2>&1<CR> to check php syntax of a php file opened with myprojects.\r\nYou can also define make and errorformat for each file or folder, see :h make and :h errorformat for more information.\r\nGetLatestVimScripts is also supported, see :h GLVS for more information about it.\r\ng:myprojects_width variable set the panel's width, default is 30.\r\ng:myprojects_file variable set the myproject's file name, default is ~\/.myprojects.\r\ng:myprojects_tags_file variable set the tags file name, default is .tags.\r\ng:myprojects_auto_close variable close the panel when a file is open, default is 0.\r\ng:myprojects_auto_open variable open automaticaly myprojects.vim at vim startup.\r\ng:myprojects_syntax variable activate syntax highlighting, default is 1.\r\ng:myprojects_display_empty_folder variable display empty folder, default is 0.\r\ng:myprojects_auto_resize variable resize the panel to its default size when a file is open, default is 0.\r\ng:myprojects_resize_step define the step used to resize panel with <C-Left> and <C-Right>, default is 10.\r\ng:myprojects_display_number display line number in panel, default is 0.\r\ng:myprojects_display_path_in_statusline display path of current file in status line, default is 1.\r\ng:myprojects_cursorline display cursor line, default is 1.\r\ng:myprojects_cursorcolumn display cursor column, default is 1.\r\ng:myprojects_foldcolumn display folder column, default is 0, see :h foldcolumn for more informations.\r\nctags or exctags must be installed to generate tags file.\r\ng:myprojects_tags_generator define tag generator utility, default is 'exctags'.\r\ng:myprojects_new_file_on_bottom add new file on bottom of folder on refresh, default is 1.\r\ng:myprojects_svn_sort sort path in svn window, default is 1.\r\ng:myprojects_autowrite auto save g:myprojects_file after refresh, default is 1.\r\nYou can override default value of these variables with \"let g:myprojects_svn_sort = 0\" in your .vimrc, for example.","first_name":"Frederic","6":"Frederic","last_name":"Hardy","7":"Hardy","releases":[{"0":"2556","vim_version":"7.0","1":"7.0","script_version":"0.0.107","2":"0.0.107","version_comment":"All my apologize, the previous vimball was incorrect.","3":"All my apologize, the previous vimball was incorrect.","package":"myprojects.vba","4":"myprojects.vba","src_id":"11227","5":"11227","creation_date":"1250853097","6":"1250853097"},{"0":"2556","vim_version":"7.0","1":"7.0","script_version":"0.0.105","2":"0.0.105","version_comment":"Remove bug in svn blame.","3":"Remove bug in svn blame.","package":"myprojects.vba","4":"myprojects.vba","src_id":"10713","5":"10713","creation_date":"1243939522","6":"1243939522"},{"0":"2556","vim_version":"7.0","1":"7.0","script_version":"0.0.104","2":"0.0.104","version_comment":"Remove bug in update of mappings.","3":"Remove bug in update of mappings.","package":"myprojects.vba","4":"myprojects.vba","src_id":"10684","5":"10684","creation_date":"1243422770","6":"1243422770"},{"0":"2556","vim_version":"7.0","1":"7.0","script_version":"0.0.103","2":"0.0.103","version_comment":"Improve svn checkout which now use preferences.","3":"Improve svn checkout which now use preferences.","package":"myprojects.vba","4":"myprojects.vba","src_id":"10596","5":"10596","creation_date":"1242380985","6":"1242380985"},{"0":"2556","vim_version":"7.0","1":"7.0","script_version":"0.0.102","2":"0.0.102","version_comment":"Remove bug in svn checkout processus.","3":"Remove bug in svn checkout processus.","package":"myprojects.vba","4":"myprojects.vba","src_id":"10595","5":"10595","creation_date":"1242379046","6":"1242379046"},{"0":"2556","vim_version":"7.0","1":"7.0","script_version":"0.0.101","2":"0.0.101","version_comment":"Remove bug in svn conflict resolution, file can now be opened from svn conflict window.\r\nRemove bug in grep.","3":"Remove bug in svn conflict resolution, file can now be opened from svn conflict window.\r\nRemove bug in grep.","package":"myprojects.vba","4":"myprojects.vba","src_id":"10586","5":"10586","creation_date":"1242200306","6":"1242200306"},{"0":"2556","vim_version":"7.0","1":"7.0","script_version":"0.0.100","2":"0.0.100","version_comment":"Add autowrite management after set or update of an attribute (path, cd, make, errorformat, mappings, etc).\r\n\"|\" are now correclty escaped in mappings.","3":"Add autowrite management after set or update of an attribute (path, cd, make, errorformat, mappings, etc).\r\n\"|\" are now correclty escaped in mappings.","package":"myprojects.vba","4":"myprojects.vba","src_id":"10555","5":"10555","creation_date":"1241679997","6":"1241679997"},{"0":"2556","vim_version":"7.0","1":"7.0","script_version":"0.0.99","2":"0.0.99","version_comment":"Improve speed.","3":"Improve speed.","package":"myprojects.vba","4":"myprojects.vba","src_id":"10549","5":"10549","creation_date":"1241616394","6":"1241616394"},{"0":"2556","vim_version":"7.0","1":"7.0","script_version":"0.0.98","2":"0.0.98","version_comment":"Remove bugs in loadMyProjectsAttribute() and svnDiff().","3":"Remove bugs in loadMyProjectsAttribute() and svnDiff().","package":"myprojects.vba","4":"myprojects.vba","src_id":"10545","5":"10545","creation_date":"1241601033","6":"1241601033"},{"0":"2556","vim_version":"7.0","1":"7.0","script_version":"0.0.97","2":"0.0.97","version_comment":"Remove bug in buffer management.\r\nAdd autowrite on refresh with g:myprojets_autowrite.","3":"Remove bug in buffer management.\r\nAdd autowrite on refresh with g:myprojets_autowrite.","package":"myprojects.vba","4":"myprojects.vba","src_id":"10544","5":"10544","creation_date":"1241594242","6":"1241594242"},{"0":"2556","vim_version":"7.0","1":"7.0","script_version":"0.0.96","2":"0.0.96","version_comment":"Remove bug in svn log.","3":"Remove bug in svn log.","package":"myprojects.vba","4":"myprojects.vba","src_id":"10522","5":"10522","creation_date":"1241443766","6":"1241443766"},{"0":"2556","vim_version":"7.0","1":"7.0","script_version":"0.0.95","2":"0.0.95","version_comment":"Add svn log support with <LocalLeader>sl.","3":"Add svn log support with <LocalLeader>sl.","package":"myprojects.vba","4":"myprojects.vba","src_id":"10521","5":"10521","creation_date":"1241440625","6":"1241440625"},{"0":"2556","vim_version":"7.0","1":"7.0","script_version":"0.0.94","2":"0.0.94","version_comment":"Remove bug about test in project creation, thanks to alexis for its feedback about that.","3":"Remove bug about test in project creation, thanks to alexis for its feedback about that.","package":"myprojects.vba","4":"myprojects.vba","src_id":"10519","5":"10519","creation_date":"1241420186","6":"1241420186"},{"0":"2556","vim_version":"7.0","1":"7.0","script_version":"0.0.93","2":"0.0.93","version_comment":"If there are several potential test file for the current file, a list is submitted to user to choose the right file.","3":"If there are several potential test file for the current file, a list is submitted to user to choose the right file.","package":"myprojects.vba","4":"myprojects.vba","src_id":"10497","5":"10497","creation_date":"1241086568","6":"1241086568"},{"0":"2556","vim_version":"7.0","1":"7.0","script_version":"0.0.92","2":"0.0.92","version_comment":"Remove bug in test file searching.","3":"Remove bug in test file searching.","package":"myprojects.vba","4":"myprojects.vba","src_id":"10495","5":"10495","creation_date":"1241082345","6":"1241082345"},{"0":"2556","vim_version":"7.0","1":"7.0","script_version":"0.0.91","2":"0.0.91","version_comment":"Test extension is managed in preferences.","3":"Test extension is managed in preferences.","package":"myprojects.vba","4":"myprojects.vba","src_id":"10494","5":"10494","creation_date":"1241080695","6":"1241080695"},{"0":"2556","vim_version":"7.0","1":"7.0","script_version":"0.0.90","2":"0.0.90","version_comment":"Remove bug in project buffer management.","3":"Remove bug in project buffer management.","package":"myprojects.vba","4":"myprojects.vba","src_id":"10492","5":"10492","creation_date":"1241076586","6":"1241076586"},{"0":"2556","vim_version":"7.0","1":"7.0","script_version":"0.0.88","2":"0.0.88","version_comment":"Remove bug in window management (thanks to alexis).\r\nRemove bug in refresh management.\r\nUpgrade from any previous version is very recommanded.\r\nAdd test file support.\r\nIf test attribute is defined on a file or a folder, <LocalLeader>et in a file opened from myprojects.vim open the associated test file.\r\nFor example, if opened file is 'foo.php', and test attribute value is 'Test.php', <LocalLeader>et open the file 'fooTest.php' if it exists in myprojects.vim panel.\r\n<LocalLeader>te set test attribute value.\r\n<LocalLeader>Te update test attribute value.\r\nThis attribute is not currently supported in preferences. ","3":"Remove bug in window management (thanks to alexis).\r\nRemove bug in refresh management.\r\nUpgrade from any previous version is very recommanded.\r\nAdd test file support.\r\nIf test attribute is defined on a file or a folder, <LocalLeader>et in a file opened from myprojects.vim open the associated test file.\r\nFor example, if opened file is 'foo.php', and test attribute value is 'Test.php', <LocalLeader>et open the file 'fooTest.php' if it exists in myprojects.vim panel.\r\n<LocalLeader>te set test attribute value.\r\n<LocalLeader>Te update test attribute value.\r\nThis attribute is not currently supported in preferences. ","package":"myprojects.vba","4":"myprojects.vba","src_id":"10486","5":"10486","creation_date":"1240994181","6":"1240994181"},{"0":"2556","vim_version":"7.0","1":"7.0","script_version":"0.0.87","2":"0.0.87","version_comment":"Remove bug in refresh method to keep make and errorformat attribute.\r\nAdd <LocalLeader>ra to refresh attributes in a file open with myprojects.","3":"Remove bug in refresh method to keep make and errorformat attribute.\r\nAdd <LocalLeader>ra to refresh attributes in a file open with myprojects.","package":"myprojects.vba","4":"myprojects.vba","src_id":"10469","5":"10469","creation_date":"1240902113","6":"1240902113"},{"0":"2556","vim_version":"7.0","1":"7.0","script_version":"0.0.80","2":"0.0.80","version_comment":"Use inputsecret() to get svn password on checkout.\r\nDeleted files in myprojects are not re-add on refresh (if you want to re-add them, remove refresh attribute).\r\n","3":"Use inputsecret() to get svn password on checkout.\r\nDeleted files in myprojects are not re-add on refresh (if you want to re-add them, remove refresh attribute).\r\n","package":"myprojects.vba","4":"myprojects.vba","src_id":"10409","5":"10409","creation_date":"1239967032","6":"1239967032"},{"0":"2556","vim_version":"7.0","1":"7.0","script_version":"0.0.70","2":"0.0.70","version_comment":"Remapping of <LeftMouse> and <S-LeftMouse> to display path in status line only if g:myprojects_display_path_in_statusline is set to 1.","3":"Remapping of <LeftMouse> and <S-LeftMouse> to display path in status line only if g:myprojects_display_path_in_statusline is set to 1.","package":"myprojects.vba","4":"myprojects.vba","src_id":"10352","5":"10352","creation_date":"1239002606","6":"1239002606"},{"0":"2556","vim_version":"7.0","1":"7.0","script_version":"0.0.60","2":"0.0.60","version_comment":"Optimization in session management.\r\nRemove bug in buffer deletion in project's buffer.","3":"Optimization in session management.\r\nRemove bug in buffer deletion in project's buffer.","package":"myprojects.vba","4":"myprojects.vba","src_id":"10303","5":"10303","creation_date":"1238160721","6":"1238160721"},{"0":"2556","vim_version":"7.0","1":"7.0","script_version":"0.0.50","2":"0.0.50","version_comment":"Add svn add (<A-a>) and svn revert (<A-r>) support.","3":"Add svn add (<A-a>) and svn revert (<A-r>) support.","package":"myprojects.vba","4":"myprojects.vba","src_id":"10270","5":"10270","creation_date":"1237819346","6":"1237819346"},{"0":"2556","vim_version":"7.0","1":"7.0","script_version":"0.0.30","2":"0.0.30","version_comment":"Add appendFile() method.\r\n<C-a> on a file in panel now append its content to file in previous window.\r\nRemove a bug in session management.\r\nMoreover, if a file in panel does not exist on your hard drive when you open it, its buffer will be created.","3":"Add appendFile() method.\r\n<C-a> on a file in panel now append its content to file in previous window.\r\nRemove a bug in session management.\r\nMoreover, if a file in panel does not exist on your hard drive when you open it, its buffer will be created.","package":"myprojects.vba","4":"myprojects.vba","src_id":"10183","5":"10183","creation_date":"1236855569","6":"1236855569"},{"0":"2556","vim_version":"7.0","1":"7.0","script_version":"0.0.20","2":"0.0.20","version_comment":"Project creation now works from an empty file.\r\nChanging working directory when a file is opened now works.\r\nThanks to seeschloss and jeff ;) which have detected these bugs.\r\n","3":"Project creation now works from an empty file.\r\nChanging working directory when a file is opened now works.\r\nThanks to seeschloss and jeff ;) which have detected these bugs.\r\n","package":"myprojects.vba","4":"myprojects.vba","src_id":"10150","5":"10150","creation_date":"1236615551","6":"1236615551"},{"0":"2556","vim_version":"7.0","1":"7.0","script_version":"0.0.10","2":"0.0.10","version_comment":"Remove a bug in s:open() about mapping.","3":"Remove a bug in s:open() about mapping.","package":"myprojects.vim","4":"myprojects.vim","src_id":"10080","5":"10080","creation_date":"1235983110","6":"1235983110"},{"0":"2556","vim_version":"7.2","1":"7.2","script_version":"0.0.1","2":"0.0.1","version_comment":"Initial upload","3":"Initial upload","package":"myprojects.vim","4":"myprojects.vim","src_id":"10039","5":"10039","creation_date":"1235636607","6":"1235636607"}]},"2555":{"script_id":"2555","0":"2555","script_name":"jellybeans.vim","1":"jellybeans.vim","script_type":"color scheme","2":"color scheme","summary":"Colorful, dark color scheme","3":"Colorful, dark color scheme","description":"A colorful, dark color scheme, inspired by ir_black and twilight (vimscript #1677).\r\n\r\nScreenshots: https:\/\/nanotech.nanotechcorp.net\/downloads\/jellybeans-preview.png\r\n\r\nDesigned primarily for a graphical Vim, but includes support for 24-bit (termguicolors), 256, 88, 16, and 8 color terminals. On a 16 or 8 color terminal, replace its colors with these for best results: https:\/\/raw.github.com\/nanotech\/jellybeans.vim\/master\/ansi-term-colors.txt\r\n\r\nIf you can\u00e2\u0080\u0099t change your terminal\u00e2\u0080\u0099s colors, set g:jellybeans_use_lowcolor_black to zero in your .vimrc to render \u00e2\u0080\u0098black\u00e2\u0080\u0099 text as grey.\r\n\r\nSee https:\/\/github.com\/nanotech\/jellybeans.vim for full option documentation. Issues and pull requests are welcomed.","4":"A colorful, dark color scheme, inspired by ir_black and twilight (vimscript #1677).\r\n\r\nScreenshots: https:\/\/nanotech.nanotechcorp.net\/downloads\/jellybeans-preview.png\r\n\r\nDesigned primarily for a graphical Vim, but includes support for 24-bit (termguicolors), 256, 88, 16, and 8 color terminals. On a 16 or 8 color terminal, replace its colors with these for best results: https:\/\/raw.github.com\/nanotech\/jellybeans.vim\/master\/ansi-term-colors.txt\r\n\r\nIf you can\u00e2\u0080\u0099t change your terminal\u00e2\u0080\u0099s colors, set g:jellybeans_use_lowcolor_black to zero in your .vimrc to render \u00e2\u0080\u0098black\u00e2\u0080\u0099 text as grey.\r\n\r\nSee https:\/\/github.com\/nanotech\/jellybeans.vim for full option documentation. Issues and pull requests are welcomed.","install_details":"vim-plug:\r\nPlug 'nanotech\/jellybeans.vim', { 'tag': 'v1.7' }\r\n\r\nVundle:\r\nPlugin 'nanotech\/jellybeans.vim'\r\n\r\nPathogen:\r\ncd ~\/.vim\/bundle && git clone --branch v1.7 https:\/\/github.com\/nanotech\/jellybeans.vim.git\r\n\r\nOtherwise, copy into \"~\/.vim\/colors\".\r\n\r\nOnce installed, run \":colorscheme jellybeans\" to switch immediately and add \"colorscheme jellybeans\" to your .vimrc to persist the setting.","5":"vim-plug:\r\nPlug 'nanotech\/jellybeans.vim', { 'tag': 'v1.7' }\r\n\r\nVundle:\r\nPlugin 'nanotech\/jellybeans.vim'\r\n\r\nPathogen:\r\ncd ~\/.vim\/bundle && git clone --branch v1.7 https:\/\/github.com\/nanotech\/jellybeans.vim.git\r\n\r\nOtherwise, copy into \"~\/.vim\/colors\".\r\n\r\nOnce installed, run \":colorscheme jellybeans\" to switch immediately and add \"colorscheme jellybeans\" to your .vimrc to persist the setting.","first_name":"NanoTech","6":"NanoTech","last_name":" ","7":" ","releases":[{"0":"2555","vim_version":"7.0","1":"7.0","script_version":"1.7","2":"1.7","version_comment":"Improved load time, termguicolors support, g:jellybeans_use_lowcolor_black is now disabled by default, new MatchParen colors on some terminals (see README)","3":"Improved load time, termguicolors support, g:jellybeans_use_lowcolor_black is now disabled by default, new MatchParen colors on some terminals (see README)","package":"jellybeans.vim","4":"jellybeans.vim","src_id":"26557","5":"26557","creation_date":"1561194373","6":"1561194373"},{"0":"2555","vim_version":"7.0","1":"7.0","script_version":"1.6","2":"1.6","version_comment":"Colors added for Erlang, Elixir, CursorLineNr, and Conceal. Improved colors for Python, C, Haskell, PHP, HTML, XML, JavaScript, IndentGuides, TODOs, Cursor, MatchParen, and 256-color terminals. New options for enabling and disabling italics, and defining custom highlight overrides.","3":"Colors added for Erlang, Elixir, CursorLineNr, and Conceal. Improved colors for Python, C, Haskell, PHP, HTML, XML, JavaScript, IndentGuides, TODOs, Cursor, MatchParen, and 256-color terminals. New options for enabling and disabling italics, and defining custom highlight overrides.","package":"jellybeans.vim","4":"jellybeans.vim","src_id":"24649","5":"24649","creation_date":"1476841820","6":"1476841820"},{"0":"2555","vim_version":"7.0","1":"7.0","script_version":"1.5","2":"1.5","version_comment":"Colors added for Debugger.vim, Lua, ColorColumn, and vim-indent-guides. Improved colors for diff, FoldColumn, SignColumn, Objective-C, and terminal Vim. New option to disable use of foreground black on 16 and 8 color terms (let g:jellybeans_use_lowcolor_black = 0).","3":"Colors added for Debugger.vim, Lua, ColorColumn, and vim-indent-guides. Improved colors for diff, FoldColumn, SignColumn, Objective-C, and terminal Vim. New option to disable use of foreground black on 16 and 8 color terms (let g:jellybeans_use_lowcolor_black = 0).","package":"jellybeans.vim","4":"jellybeans.vim","src_id":"17225","5":"17225","creation_date":"1326691354","6":"1326691354"},{"0":"2555","vim_version":"7.0","1":"7.0","script_version":"1.4","2":"1.4","version_comment":"Colors added for WildMenu, spell checking, MoreMsg, Question, CoffeeScript, and PreciseJump. Improved colors for the auto-complete menu, diff, Ruby, and 256 and 16 color modes. Various other tweaks and fixes.","3":"Colors added for WildMenu, spell checking, MoreMsg, Question, CoffeeScript, and PreciseJump. Improved colors for the auto-complete menu, diff, Ruby, and 256 and 16 color modes. Various other tweaks and fixes.","package":"jellybeans.vim","4":"jellybeans.vim","src_id":"15432","5":"15432","creation_date":"1302565749","6":"1302565749"},{"0":"2555","vim_version":"7.0","1":"7.0","script_version":"1.3","2":"1.3","version_comment":"Improved coloring of C, Objective-C, splits, and non-printable characters.","3":"Improved coloring of C, Objective-C, splits, and non-printable characters.","package":"jellybeans.vim","4":"jellybeans.vim","src_id":"14121","5":"14121","creation_date":"1288051360","6":"1288051360"},{"0":"2555","vim_version":"7.0","1":"7.0","script_version":"1.2","2":"1.2","version_comment":"Added support for 256-color terminals.","3":"Added support for 256-color terminals.","package":"jellybeans.vim","4":"jellybeans.vim","src_id":"10690","5":"10690","creation_date":"1243468951","6":"1243468951"},{"0":"2555","vim_version":"7.0","1":"7.0","script_version":"1.1","2":"1.1","version_comment":"Clean up, added JavaScript, updated PHP, added a header block, embedded the LICENSE.","3":"Clean up, added JavaScript, updated PHP, added a header block, embedded the LICENSE.","package":"jellybeans.vim","4":"jellybeans.vim","src_id":"10664","5":"10664","creation_date":"1243046969","6":"1243046969"},{"0":"2555","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"jellybeans.vim","4":"jellybeans.vim","src_id":"10037","5":"10037","creation_date":"1235616570","6":"1235616570"}]},"2554":{"script_id":"2554","0":"2554","script_name":"CommentAnyWay","1":"CommentAnyWay","script_type":"utility","2":"utility","summary":"THIS IS BUGGY DO NOT USE THIS","3":"THIS IS BUGGY DO NOT USE THIS","description":"\r\nGet latest version from vimscript#5383.\r\n\r\n=========================================\r\n\r\nthis explanation is only about mappings and its action.\r\nif you get interested in this script and you want to know more,\r\ndetailed explanation is written in its script.\r\n\r\n\r\n\r\nMAPPING:\r\n\r\n  In normal mode:\r\n    If you typed digits string([1-9]) before typing these mappings,\r\n    behave like in visual mode.\r\n    so you want to see when you gave digits string, see \"In visual mode\".\r\n\r\n    gcc\r\n        if default. this is the same as |gct|.\r\n    gcI\r\n        add one-line comment to the beginning of line.\r\n    gci\r\n        add one-line comment to the beginning of non-space string(\\S).\r\n    gca\r\n        add one-line comment to the end of line.\r\n    gcu{type}\r\n        type is one of 'c I i a'.\r\n        remove one-line comment.\r\n    gcw\r\n        add one-line comment to wrap the line.\r\n    gct\r\n        toggle comment\/uncomment.\r\n    gcv{wrap}{action}\r\n        add various comment.\r\n    gco\r\n        jump(o) before add comment.\r\n    gcO\r\n        jump(O) before add comment.\r\n    gcmm\r\n        add multi-comment.\r\n    gcmi\r\n        add if statement.\r\n    gcmw\r\n        add while statement.\r\n    gcmf\r\n        add for statement.\r\n    gcms\r\n        add switch statement.\r\n    gcmd\r\n        add do ~ while statement.\r\n    gcmt\r\n        add try ~ catch statement.\r\n\r\n\r\n  In visual mode:\r\n\r\n    gcc\r\n        if default. this is the same as |gct|.\r\n    gcI\r\n        add one-line comment to the beginning of line.\r\n    gci\r\n        add one-line comment to the beginning of non-space string(\\S).\r\n    gca\r\n        add one-line comment to the end of line.\r\n    gcu{type}\r\n        type is one of 'I i a w'.\r\n        remove one-line comment.\r\n    gcw\r\n        add one-line comment to wrap the line.\r\n    gct\r\n        toggle comment\/uncomment.\r\n    gcv{string}\r\n        add various comments.\r\n    gcmm\r\n        add multi-comment.\r\n    gcmi\r\n        add if statement.\r\n    gcmw\r\n        add while statement.\r\n    gcmf\r\n        add for statement.\r\n    gcms\r\n        add switch statement.\r\n    gcmd\r\n        add do ~ while statement.\r\n    gcmt\r\n        add try ~ catch statement.\r\n\r\n    And these are default mappings.\r\n    you can define all mappings what you want.\r\n\r\n\r\n\r\nEXAMPLES:\r\n\r\n    If global variables are all default value...\r\n    \r\n    |gcI|\r\n      before:\r\n          '   testtesttest'\r\n      after:\r\n          '#    testtesttest'\r\n    \r\n    |gci|\r\n      before:\r\n          '   <- inserted here'\r\n      after:\r\n          '   # <- inserted here'\r\n    \r\n    |gca|\r\n      before:\r\n          'aaaaaaa'\r\n      after:\r\n          'aaaaaaa    # '\r\n    \r\n    |gcw|\r\n      before:\r\n          'aaaaaaa'\r\n      after:\r\n          '\/* aaaaaaa *\/'\r\n    \r\n    |gcv|\r\n      before:\r\n          '   some code here'\r\n      after:\r\n          you type 'gcv', and '\/\/ XXX:<CR>i'\r\n          '   \/\/ XXX: some code here'\r\n    \r\n    |gco|\r\n      before:\r\n          '   func1();'\r\n      after:\r\n          you type 'gco', and 'func2();'\r\n          '   func1()'\r\n          '   \/\/ func2();'\r\n    \r\n    |gcO|\r\n      before:\r\n          '   func1();'\r\n      after:\r\n          you type 'gcO', and 'call func1()'\r\n          '   \/\/ call func1()'\r\n          '   func1();'\r\n    \r\n    multiline mappings(gcm*) insert the comments or the statements.\r\n    \r\n    global variables change detailed behavior.\r\n    and all these mappings are also available in visual mode.","4":"\r\nGet latest version from vimscript#5383.\r\n\r\n=========================================\r\n\r\nthis explanation is only about mappings and its action.\r\nif you get interested in this script and you want to know more,\r\ndetailed explanation is written in its script.\r\n\r\n\r\n\r\nMAPPING:\r\n\r\n  In normal mode:\r\n    If you typed digits string([1-9]) before typing these mappings,\r\n    behave like in visual mode.\r\n    so you want to see when you gave digits string, see \"In visual mode\".\r\n\r\n    gcc\r\n        if default. this is the same as |gct|.\r\n    gcI\r\n        add one-line comment to the beginning of line.\r\n    gci\r\n        add one-line comment to the beginning of non-space string(\\S).\r\n    gca\r\n        add one-line comment to the end of line.\r\n    gcu{type}\r\n        type is one of 'c I i a'.\r\n        remove one-line comment.\r\n    gcw\r\n        add one-line comment to wrap the line.\r\n    gct\r\n        toggle comment\/uncomment.\r\n    gcv{wrap}{action}\r\n        add various comment.\r\n    gco\r\n        jump(o) before add comment.\r\n    gcO\r\n        jump(O) before add comment.\r\n    gcmm\r\n        add multi-comment.\r\n    gcmi\r\n        add if statement.\r\n    gcmw\r\n        add while statement.\r\n    gcmf\r\n        add for statement.\r\n    gcms\r\n        add switch statement.\r\n    gcmd\r\n        add do ~ while statement.\r\n    gcmt\r\n        add try ~ catch statement.\r\n\r\n\r\n  In visual mode:\r\n\r\n    gcc\r\n        if default. this is the same as |gct|.\r\n    gcI\r\n        add one-line comment to the beginning of line.\r\n    gci\r\n        add one-line comment to the beginning of non-space string(\\S).\r\n    gca\r\n        add one-line comment to the end of line.\r\n    gcu{type}\r\n        type is one of 'I i a w'.\r\n        remove one-line comment.\r\n    gcw\r\n        add one-line comment to wrap the line.\r\n    gct\r\n        toggle comment\/uncomment.\r\n    gcv{string}\r\n        add various comments.\r\n    gcmm\r\n        add multi-comment.\r\n    gcmi\r\n        add if statement.\r\n    gcmw\r\n        add while statement.\r\n    gcmf\r\n        add for statement.\r\n    gcms\r\n        add switch statement.\r\n    gcmd\r\n        add do ~ while statement.\r\n    gcmt\r\n        add try ~ catch statement.\r\n\r\n    And these are default mappings.\r\n    you can define all mappings what you want.\r\n\r\n\r\n\r\nEXAMPLES:\r\n\r\n    If global variables are all default value...\r\n    \r\n    |gcI|\r\n      before:\r\n          '   testtesttest'\r\n      after:\r\n          '#    testtesttest'\r\n    \r\n    |gci|\r\n      before:\r\n          '   <- inserted here'\r\n      after:\r\n          '   # <- inserted here'\r\n    \r\n    |gca|\r\n      before:\r\n          'aaaaaaa'\r\n      after:\r\n          'aaaaaaa    # '\r\n    \r\n    |gcw|\r\n      before:\r\n          'aaaaaaa'\r\n      after:\r\n          '\/* aaaaaaa *\/'\r\n    \r\n    |gcv|\r\n      before:\r\n          '   some code here'\r\n      after:\r\n          you type 'gcv', and '\/\/ XXX:<CR>i'\r\n          '   \/\/ XXX: some code here'\r\n    \r\n    |gco|\r\n      before:\r\n          '   func1();'\r\n      after:\r\n          you type 'gco', and 'func2();'\r\n          '   func1()'\r\n          '   \/\/ func2();'\r\n    \r\n    |gcO|\r\n      before:\r\n          '   func1();'\r\n      after:\r\n          you type 'gcO', and 'call func1()'\r\n          '   \/\/ call func1()'\r\n          '   func1();'\r\n    \r\n    multiline mappings(gcm*) insert the comments or the statements.\r\n    \r\n    global variables change detailed behavior.\r\n    and all these mappings are also available in visual mode.","install_details":"Just move it into ~\/.vim\/plugin","5":"Just move it into ~\/.vim\/plugin","first_name":"tyru","6":"tyru","last_name":" ","7":" ","releases":[{"0":"2554","vim_version":"7.0","1":"7.0","script_version":"1.0.1","2":"1.0.1","version_comment":"Fix bug that CommentAnyWay.Base.GetIndent() can't get proper indent num.","3":"Fix bug that CommentAnyWay.Base.GetIndent() can't get proper indent num.","package":"CommentAnyWay.vim","4":"CommentAnyWay.vim","src_id":"10088","5":"10088","creation_date":"1236047951","6":"1236047951"},{"0":"2554","vim_version":"7.0","1":"7.0","script_version":"1.0.0","2":"1.0.0","version_comment":"Initial upload","3":"Initial upload","package":"CommentAnyWay.vim","4":"CommentAnyWay.vim","src_id":"10030","5":"10030","creation_date":"1235544248","6":"1235544248"}]},"2553":{"script_id":"2553","0":"2553","script_name":"irssilog.vim","1":"irssilog.vim","script_type":"syntax","2":"syntax","summary":"Syntax for viewing Irssi logs","3":"Syntax for viewing Irssi logs","description":"A syntax file for Irssi logs.  The script can also read your .irssi\/saved_colors file (from nickcolor.pl) to colorize your friends' names.","4":"A syntax file for Irssi logs.  The script can also read your .irssi\/saved_colors file (from nickcolor.pl) to colorize your friends' names.","install_details":"Drop into the 'syntax' directory of your vim config.","5":"Drop into the 'syntax' directory of your vim config.","first_name":"Will","6":"Will","last_name":"Gray","7":"Gray","releases":[{"0":"2553","vim_version":"6.0","1":"6.0","script_version":"1.1","2":"1.1","version_comment":"Missed { and } being valid for a nick.","3":"Missed { and } being valid for a nick.","package":"irssilog.vim","4":"irssilog.vim","src_id":"10584","5":"10584","creation_date":"1242158074","6":"1242158074"},{"0":"2553","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"irssilog.vim","4":"irssilog.vim","src_id":"10024","5":"10024","creation_date":"1235502920","6":"1235502920"}]},"2552":{"script_id":"2552","0":"2552","script_name":"jam.vim","1":"jam.vim","script_type":"syntax","2":"syntax","summary":"Jam (or Boost.Build) syntax","3":"Jam (or Boost.Build) syntax","description":"I love Jam, but I hated staring at plain text.  I based this off of something by Matt Armstrong (see source).  This is best effort only.  Jam is also known as bjam and Boost.Jam.","4":"I love Jam, but I hated staring at plain text.  I based this off of something by Matt Armstrong (see source).  This is best effort only.  Jam is also known as bjam and Boost.Jam.","install_details":"To install, I put it in ~\/.vim\/syntax and put the following to ~\/.vim\/filetype.vim:\r\n\r\nif exists(\"did_load_filetypes\")\r\n        finish\r\nendif\r\n\r\n\" jam detection\r\naugroup filetypedetect\r\n        au! BufRead,BufNewFile Jamroot        setfiletype jam\r\naugroup END","5":"To install, I put it in ~\/.vim\/syntax and put the following to ~\/.vim\/filetype.vim:\r\n\r\nif exists(\"did_load_filetypes\")\r\n        finish\r\nendif\r\n\r\n\" jam detection\r\naugroup filetypedetect\r\n        au! BufRead,BufNewFile Jamroot        setfiletype jam\r\naugroup END","first_name":"Markus","6":"Markus","last_name":"Peloquin","7":"Peloquin","releases":[{"0":"2552","vim_version":"6.0","1":"6.0","script_version":"0.3","2":"0.3","version_comment":"I reworked the set of keywords.","3":"I reworked the set of keywords.","package":"jam.vim","4":"jam.vim","src_id":"10632","5":"10632","creation_date":"1242692781","6":"1242692781"},{"0":"2552","vim_version":"6.0","1":"6.0","script_version":"0.2","2":"0.2","version_comment":"Fixed a small bug with comment detection.","3":"Fixed a small bug with comment detection.","package":"jam.vim","4":"jam.vim","src_id":"10025","5":"10025","creation_date":"1235513275","6":"1235513275"}]},"2551":{"script_id":"2551","0":"2551","script_name":"Vicle","1":"Vicle","script_type":"utility","2":"utility","summary":"Vim - Interpreter Command Line Editor. Like Chimp or Slimv.","3":"Vim - Interpreter Command Line Editor. Like Chimp or Slimv.","description":"Vim - Interpreter Command Line Editor. Use vim like a front-end for edit commands and send it to an interactive interpreter open in a GNU Screen session or tmux session.\r\n\r\nFeatures:\r\n\r\n- Command History, just like a shell\r\n- History save\/load\r\n- Can send only selected text or custom selection\r\n\r\nI have been using Python, Ruby, Common Lisp, Scheme, Clojure, Ksh, and others interpreters through Vim and Vicle (and GNU Screen or tmux).\r\n\r\nUsage:\r\n\r\n- Load a Screen session and then load an interpreter (ipython, irb, shell,\r\n  sbcl, clisp, clojure,  etc.) in the shell:\r\n  % screen -S rubySession\r\n  % irb\r\n  >>\r\n\r\n- Open Vim with the vicle plugin and type a command (without press ENTER):\r\n  puts \"Ruby interpreter\"\r\n\r\n- Type <C-c><C-c>  or <C-CR> or :VicleSend  to send to the interpreter the\r\n  current line (that can be changed by setting other Selection String).\r\n\r\n- If the identifiers of the screen are not set, you are going be asked for\r\n  it (put the session name and window number where your interpreter are.\r\n  All the windows in a Screen session have a unique number.\r\n  You can use TAB key for completion in the Session name):\r\n\r\n  Session name: rubySession\r\n  Window number: 0\r\n\r\n  In the screen window you are going to see:\r\n  >> puts \"Ruby interpreter\"\r\n  Ruby interpreter\r\n  => nil\r\n\r\n  If you disable the Edition Mode by calling the command :VicleEditionToggle\r\n  the <C-CR> and the other shortcut are going to send all the content of the\r\n  screen and after that, the screen of Vim are going to be cleared, just\r\n  like a normal command line.\r\n\r\n- You scroll through the commands with the key <C-Up> and <C-Down>   just\r\n  like the history of the shell.\r\n\r\n- Edition Mode\r\n  This mode do not clear the screen after send the command. Also, it send a\r\n  command selected by a custom Selection String that is in the variable\r\n\r\n  w:vicle_selection_string\r\n\r\n  Edition Mode is 1 (ON) by default.\r\n\r\n  By default, vicle in Edition mode send the current line.\r\n  Toggle the Edition Mode using the command :VicleEditionToggle\r\n\r\n  The selection string is by default \"0v$y\": go to column 0, enter visual\r\n  mode, go to the end of line and yank. Always is necesary to end with the\r\n  yank command \"y\".\r\n  It can be set to \"{v}y\" to select the current paragraph\r\n\r\n- Sending selected text using Vim's Visual Mode\r\n  Just select the text and press <C-CR> or <C-c><C-c> to send the selected\r\n  text without clear the screen. It is the same in Vicle Edition Mode and\r\n  Vicle Not Edicion Mode (send command and clear vim screen)\r\n\r\n  Just select the text. Vicle are going to yank it.\r\n\r\n- Usefull commands for manage the history. Use absolute paths for history files:\r\n  :VicleHistoryToggle   \" activate or deactivate history\r\n  :VicleHistoryClear\r\n  :VicleHistorySize\r\n  :VicleHistorySave\r\n  :VicleHistoryLoad\r\n\r\n- To change the screen name and window name use the command\r\n  :VicleSession\r\n\r\n- Some global variables that you can define in your .vimrc:\r\n\r\n  let g:vicle_session_sn    = 'normal_session_name'\r\n  let g:vicle_session_wn  = 'normal_session_window'\r\n   let g:vicle_use               = 'screen'       \" Can be 'screen' or 'tmux'\r\n   let g:vicle_escape_caret      = 0    \" If defined as 1 then the characters ^ will be escaped as \\^\r\n\r\n  let g:vicle_history_active   = 0 \" deactivate history\r\n  let g:vicle_edition_mode     = 1 \" active edition mode\r\n  let g:vicle_selection_string = \"0v$y\"  \" yank current line\r\n\r\n  let g:vicle_hcs             = '~~~your_command_separator~~~'\r\n  let g:vicle_max_buffer        = 300  \" work for OSX\r\n\r\nTips:\r\n\r\n- If you want to send commands to a Ruby interpreter (irb), open a file like\r\n  work.rb or other with the extension .rb  or set the filetype manually\r\n  :set filetype=ruby\r\n\r\n This apply to other languages supported by vim.\r\n\r\n- For use Vicle with diferent languages\r\n\r\n  autocmd FileType python let w:vicle_selection_string = \"0v}y\"\r\n  autocmd FileType lisp let w:vicle_edition_mode = 1 | let w:vicle_history_active = 0 | let w:vicle_selection_string = \"v%y\"\r\n  autocmd FileType clojure let t:vicle_edition_mode = 1 | let t:vicle_history_active = 0 | let t:vicle_selection_string = \"v%y\" | let t:vicle_session_sn =\"session_name\" | let t:vicle_session_wn= \"window_name.pane_index\"\r\n\r\n- Use of rlwrap to run the interpreter\r\n\r\n  It is known that by trying and testing that running the interpreter with rlwrap improves the performances of vicle.\r\n\r\n  Clojure with rlwrap:\r\n  screen -S clojure rlwrap java -cp clojure.jar clojure.main\r\n\r\n  Clojure with tmux:\r\n  tmux new-session -s code -n clojure    # session name: code, window name: clojure\r\n   \"   In vim, session = code, window=clojure.2   if working in pane 2 of window named \"clojure\".\r\n\r\n- About the limit of size for the buffers to send\r\n\r\n  Vicle call many times to Screen when the buffer to send its bigger than 1000 characters. This let vicle to send really big buffers.\r\n\r\n\r\nInspired On:\r\n\r\n  Slime for Vim from Jonathan Palardy\r\n  http:\/\/technotales.wordpress.com\/2007\/10\/03\/like-slime-for-vim\/\r\n  and the work of Jerris Welt\r\n  http:\/\/www.jerri.de\/blog\/archives\/2006\/05\/02\/scripting_screen_for_fun_and_profit\/\r\n","4":"Vim - Interpreter Command Line Editor. Use vim like a front-end for edit commands and send it to an interactive interpreter open in a GNU Screen session or tmux session.\r\n\r\nFeatures:\r\n\r\n- Command History, just like a shell\r\n- History save\/load\r\n- Can send only selected text or custom selection\r\n\r\nI have been using Python, Ruby, Common Lisp, Scheme, Clojure, Ksh, and others interpreters through Vim and Vicle (and GNU Screen or tmux).\r\n\r\nUsage:\r\n\r\n- Load a Screen session and then load an interpreter (ipython, irb, shell,\r\n  sbcl, clisp, clojure,  etc.) in the shell:\r\n  % screen -S rubySession\r\n  % irb\r\n  >>\r\n\r\n- Open Vim with the vicle plugin and type a command (without press ENTER):\r\n  puts \"Ruby interpreter\"\r\n\r\n- Type <C-c><C-c>  or <C-CR> or :VicleSend  to send to the interpreter the\r\n  current line (that can be changed by setting other Selection String).\r\n\r\n- If the identifiers of the screen are not set, you are going be asked for\r\n  it (put the session name and window number where your interpreter are.\r\n  All the windows in a Screen session have a unique number.\r\n  You can use TAB key for completion in the Session name):\r\n\r\n  Session name: rubySession\r\n  Window number: 0\r\n\r\n  In the screen window you are going to see:\r\n  >> puts \"Ruby interpreter\"\r\n  Ruby interpreter\r\n  => nil\r\n\r\n  If you disable the Edition Mode by calling the command :VicleEditionToggle\r\n  the <C-CR> and the other shortcut are going to send all the content of the\r\n  screen and after that, the screen of Vim are going to be cleared, just\r\n  like a normal command line.\r\n\r\n- You scroll through the commands with the key <C-Up> and <C-Down>   just\r\n  like the history of the shell.\r\n\r\n- Edition Mode\r\n  This mode do not clear the screen after send the command. Also, it send a\r\n  command selected by a custom Selection String that is in the variable\r\n\r\n  w:vicle_selection_string\r\n\r\n  Edition Mode is 1 (ON) by default.\r\n\r\n  By default, vicle in Edition mode send the current line.\r\n  Toggle the Edition Mode using the command :VicleEditionToggle\r\n\r\n  The selection string is by default \"0v$y\": go to column 0, enter visual\r\n  mode, go to the end of line and yank. Always is necesary to end with the\r\n  yank command \"y\".\r\n  It can be set to \"{v}y\" to select the current paragraph\r\n\r\n- Sending selected text using Vim's Visual Mode\r\n  Just select the text and press <C-CR> or <C-c><C-c> to send the selected\r\n  text without clear the screen. It is the same in Vicle Edition Mode and\r\n  Vicle Not Edicion Mode (send command and clear vim screen)\r\n\r\n  Just select the text. Vicle are going to yank it.\r\n\r\n- Usefull commands for manage the history. Use absolute paths for history files:\r\n  :VicleHistoryToggle   \" activate or deactivate history\r\n  :VicleHistoryClear\r\n  :VicleHistorySize\r\n  :VicleHistorySave\r\n  :VicleHistoryLoad\r\n\r\n- To change the screen name and window name use the command\r\n  :VicleSession\r\n\r\n- Some global variables that you can define in your .vimrc:\r\n\r\n  let g:vicle_session_sn    = 'normal_session_name'\r\n  let g:vicle_session_wn  = 'normal_session_window'\r\n   let g:vicle_use               = 'screen'       \" Can be 'screen' or 'tmux'\r\n   let g:vicle_escape_caret      = 0    \" If defined as 1 then the characters ^ will be escaped as \\^\r\n\r\n  let g:vicle_history_active   = 0 \" deactivate history\r\n  let g:vicle_edition_mode     = 1 \" active edition mode\r\n  let g:vicle_selection_string = \"0v$y\"  \" yank current line\r\n\r\n  let g:vicle_hcs             = '~~~your_command_separator~~~'\r\n  let g:vicle_max_buffer        = 300  \" work for OSX\r\n\r\nTips:\r\n\r\n- If you want to send commands to a Ruby interpreter (irb), open a file like\r\n  work.rb or other with the extension .rb  or set the filetype manually\r\n  :set filetype=ruby\r\n\r\n This apply to other languages supported by vim.\r\n\r\n- For use Vicle with diferent languages\r\n\r\n  autocmd FileType python let w:vicle_selection_string = \"0v}y\"\r\n  autocmd FileType lisp let w:vicle_edition_mode = 1 | let w:vicle_history_active = 0 | let w:vicle_selection_string = \"v%y\"\r\n  autocmd FileType clojure let t:vicle_edition_mode = 1 | let t:vicle_history_active = 0 | let t:vicle_selection_string = \"v%y\" | let t:vicle_session_sn =\"session_name\" | let t:vicle_session_wn= \"window_name.pane_index\"\r\n\r\n- Use of rlwrap to run the interpreter\r\n\r\n  It is known that by trying and testing that running the interpreter with rlwrap improves the performances of vicle.\r\n\r\n  Clojure with rlwrap:\r\n  screen -S clojure rlwrap java -cp clojure.jar clojure.main\r\n\r\n  Clojure with tmux:\r\n  tmux new-session -s code -n clojure    # session name: code, window name: clojure\r\n   \"   In vim, session = code, window=clojure.2   if working in pane 2 of window named \"clojure\".\r\n\r\n- About the limit of size for the buffers to send\r\n\r\n  Vicle call many times to Screen when the buffer to send its bigger than 1000 characters. This let vicle to send really big buffers.\r\n\r\n\r\nInspired On:\r\n\r\n  Slime for Vim from Jonathan Palardy\r\n  http:\/\/technotales.wordpress.com\/2007\/10\/03\/like-slime-for-vim\/\r\n  and the work of Jerris Welt\r\n  http:\/\/www.jerri.de\/blog\/archives\/2006\/05\/02\/scripting_screen_for_fun_and_profit\/\r\n","install_details":"Just put it in your vim's plugins directory.\r\n\r\nThis plugin doesn't work in Windows, as far as I know. I tried to run it on Cygwin but nothing.","5":"Just put it in your vim's plugins directory.\r\n\r\nThis plugin doesn't work in Windows, as far as I know. I tried to run it on Cygwin but nothing.","first_name":"Jose","6":"Jose","last_name":"Figueroa Martinez","7":"Figueroa Martinez","releases":[{"0":"2551","vim_version":"7.0","1":"7.0","script_version":"1.3.0","2":"1.3.0","version_comment":"- New parameters to select screen or tmux terminal emulators and to know if the caret character (^) must be escaped or not (problem reported by  Stephan Sahm.\r\n- Changed the name of some parameters:\r\n     t:vicle_screen_sn to t:vicle_session_sn\r\n     t:vicle_screen_wn to t:vicle_session_wn","3":"- New parameters to select screen or tmux terminal emulators and to know if the caret character (^) must be escaped or not (problem reported by  Stephan Sahm.\r\n- Changed the name of some parameters:\r\n     t:vicle_screen_sn to t:vicle_session_sn\r\n     t:vicle_screen_wn to t:vicle_session_wn","package":"vicle.vim","4":"vicle.vim","src_id":"22472","5":"22472","creation_date":"1412201291","6":"1412201291"},{"0":"2551","vim_version":"7.0","1":"7.0","script_version":"1.2.2","2":"1.2.2","version_comment":"- Bugfix by Markus Dobler from informatik.uni-tuebingen.de, related to the error behavior (\"E484: Can't open file \/tmp\/vXXXXXX\/1\").Tested on linux. May need to be tested on OSX and BSD systems.","3":"- Bugfix by Markus Dobler from informatik.uni-tuebingen.de, related to the error behavior (\"E484: Can't open file \/tmp\/vXXXXXX\/1\").Tested on linux. May need to be tested on OSX and BSD systems.","package":"vicle.vim","4":"vicle.vim","src_id":"16197","5":"16197","creation_date":"1312495934","6":"1312495934"},{"0":"2551","vim_version":"7.0","1":"7.0","script_version":"1.2.1","2":"1.2.1","version_comment":"Fix for OSX reported by Guy Haskin F:\r\n  \"It seems like anything greater than about 380 characters fails to send\r\n   corretly.\"\r\n\r\nChanges:\r\n  \" You can put this definition in your .vimrc to fix the reported problem in OSX.\r\n  let g:vicle_max_buffer  = 300","3":"Fix for OSX reported by Guy Haskin F:\r\n  \"It seems like anything greater than about 380 characters fails to send\r\n   corretly.\"\r\n\r\nChanges:\r\n  \" You can put this definition in your .vimrc to fix the reported problem in OSX.\r\n  let g:vicle_max_buffer  = 300","package":"vicle.vim","4":"vicle.vim","src_id":"14060","5":"14060","creation_date":"1287175530","6":"1287175530"},{"0":"2551","vim_version":"7.0","1":"7.0","script_version":"1.2","2":"1.2","version_comment":"- Removed the size limit for the buffer to send by calling \"screen\" multiple times.\r\n- Fixed behavior with multiple tabs.\r\n- Tip: It is better to run the interpreter under \"rlwrap\".\r\n- Limitation: Sending to much text can be slow.","3":"- Removed the size limit for the buffer to send by calling \"screen\" multiple times.\r\n- Fixed behavior with multiple tabs.\r\n- Tip: It is better to run the interpreter under \"rlwrap\".\r\n- Limitation: Sending to much text can be slow.","package":"vicle.vim","4":"vicle.vim","src_id":"12818","5":"12818","creation_date":"1271072768","6":"1271072768"},{"0":"2551","vim_version":"7.0","1":"7.0","script_version":"1.1.3","2":"1.1.3","version_comment":"Fixed copying multiple times the same selection when sending a selected text","3":"Fixed copying multiple times the same selection when sending a selected text","package":"vicle.vim","4":"vicle.vim","src_id":"11523","5":"11523","creation_date":"1255431958","6":"1255431958"},{"0":"2551","vim_version":"7.0","1":"7.0","script_version":"1.1.2","2":"1.1.2","version_comment":"Fixed cursor return to the last position when sending a command","3":"Fixed cursor return to the last position when sending a command","package":"vicle.vim","4":"vicle.vim","src_id":"11520","5":"11520","creation_date":"1255366096","6":"1255366096"},{"0":"2551","vim_version":"7.0","1":"7.0","script_version":"1.1.1","2":"1.1.1","version_comment":"- Edition Mode are 1 (On) by default.\r\n- Fixed the annoying \"Press ENTER ....\" that happend when yank send more than 2 lines to Screen.\r\n- More documentation","3":"- Edition Mode are 1 (On) by default.\r\n- Fixed the annoying \"Press ENTER ....\" that happend when yank send more than 2 lines to Screen.\r\n- More documentation","package":"vicle.vim","4":"vicle.vim","src_id":"11483","5":"11483","creation_date":"1254694481","6":"1254694481"},{"0":"2551","vim_version":"7.0","1":"7.0","script_version":"1.1","2":"1.1","version_comment":"- Added a Edition Mode that not clear the Vim screen and send only a custom selection of text. By default, the current line.\r\n- Added the feature for send selected text using the Vim's Visual Mode\r\n- Added more tips to use vicle with more than one language","3":"- Added a Edition Mode that not clear the Vim screen and send only a custom selection of text. By default, the current line.\r\n- Added the feature for send selected text using the Vim's Visual Mode\r\n- Added more tips to use vicle with more than one language","package":"vicle.vim","4":"vicle.vim","src_id":"11473","5":"11473","creation_date":"1254505070","6":"1254505070"},{"0":"2551","vim_version":"7.0","1":"7.0","script_version":"1.0.1","2":"1.0.1","version_comment":"Fix problem with load\/saving history commands, removed some doc, a command for send the content.\r\nThe previous version are for Vim7 too. Sorry for the mistake.","3":"Fix problem with load\/saving history commands, removed some doc, a command for send the content.\r\nThe previous version are for Vim7 too. Sorry for the mistake.","package":"vicle.vim","4":"vicle.vim","src_id":"10019","5":"10019","creation_date":"1235469573","6":"1235469573"},{"0":"2551","vim_version":"6.0","1":"6.0","script_version":"1.0.0","2":"1.0.0","version_comment":"Initial upload","3":"Initial upload","package":"vicle.vim","4":"vicle.vim","src_id":"10015","5":"10015","creation_date":"1235429875","6":"1235429875"}]},"2550":{"script_id":"2550","0":"2550","script_name":"wps.vim","1":"wps.vim","script_type":"syntax","2":"syntax","summary":"Syntax for Rockbox WPS","3":"Syntax for Rockbox WPS","description":"Syntax highlighting for Rockbox WPS (While Playing Screen) definitions. \r\n\r\nThe versions here are obsolete; the latest version can now be found in the Rockbox source tree under utils\/editors.\r\n\r\nDirect links:\r\nSummary: http:\/\/svn.rockbox.org\/viewvc.cgi\/trunk\/utils\/editors\/wps.vim?view=log\r\nLatest version: http:\/\/svn.rockbox.org\/viewvc.cgi\/trunk\/utils\/editors\/wps.vim","4":"Syntax highlighting for Rockbox WPS (While Playing Screen) definitions. \r\n\r\nThe versions here are obsolete; the latest version can now be found in the Rockbox source tree under utils\/editors.\r\n\r\nDirect links:\r\nSummary: http:\/\/svn.rockbox.org\/viewvc.cgi\/trunk\/utils\/editors\/wps.vim?view=log\r\nLatest version: http:\/\/svn.rockbox.org\/viewvc.cgi\/trunk\/utils\/editors\/wps.vim","install_details":"","5":"","first_name":"Kevin","6":"Kevin","last_name":"Schoedel","7":"Schoedel","releases":[{"0":"2550","vim_version":"7.0","1":"7.0","script_version":"1.2","2":"1.2","version_comment":"Patch from Tomer Shalev -- Sx, Sr","3":"Patch from Tomer Shalev -- Sx, Sr","package":"wps.vim","4":"wps.vim","src_id":"11855","5":"11855","creation_date":"1259859190","6":"1259859190"},{"0":"2550","vim_version":"7.0","1":"7.0","script_version":"1.1","2":"1.1","version_comment":"Added missing %ck","3":"Added missing %ck","package":"wps.vim","4":"wps.vim","src_id":"10235","5":"10235","creation_date":"1237307177","6":"1237307177"},{"0":"2550","vim_version":"7.2","1":"7.2","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"wps.vim","4":"wps.vim","src_id":"10007","5":"10007","creation_date":"1235328775","6":"1235328775"}]},"2549":{"script_id":"2549","0":"2549","script_name":"BusyBee","1":"BusyBee","script_type":"color scheme","2":"color scheme","summary":"a dark color scheme (modification of Mustang.vim)","3":"a dark color scheme (modification of Mustang.vim)","description":"I like Mustang.vim colour scheme (http:\/\/hcalves.deviantart.com\/art\/Mustang-Vim-Colorscheme-98974484).\r\n\r\nIt was still to vivid for my eyes, so I modified it slightly.","4":"I like Mustang.vim colour scheme (http:\/\/hcalves.deviantart.com\/art\/Mustang-Vim-Colorscheme-98974484).\r\n\r\nIt was still to vivid for my eyes, so I modified it slightly.","install_details":"Copy to ~\/.vim\/colors","5":"Copy to ~\/.vim\/colors","first_name":"Patrick","6":"Patrick","last_name":"Anderson","7":"Anderson","releases":[{"0":"2549","vim_version":"7.0","1":"7.0","script_version":"1.0.1","2":"1.0.1","version_comment":"Added a few colours (to the custom Python syntax by Dmitry Vasiliev <dima@hlabs.spb.ru>)","3":"Added a few colours (to the custom Python syntax by Dmitry Vasiliev <dima@hlabs.spb.ru>)","package":"BusyBee.vim","4":"BusyBee.vim","src_id":"10016","5":"10016","creation_date":"1235443051","6":"1235443051"},{"0":"2549","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"BusyBee.vim","4":"BusyBee.vim","src_id":"10006","5":"10006","creation_date":"1235323620","6":"1235323620"}]},"2548":{"script_id":"2548","0":"2548","script_name":"php.vim","1":"php.vim","script_type":"syntax","2":"syntax","summary":"phpDoc Syntax Highlighting for PHP","3":"phpDoc Syntax Highlighting for PHP","description":"Extends the PHP syntax highlighting, changing comments when using phpDoc tags to resemble the highlighting found in the Vim Java syntax.\r\n\r\nhttps:\/\/github.com\/tetsuo13\/Vim-PHP-Doc","4":"Extends the PHP syntax highlighting, changing comments when using phpDoc tags to resemble the highlighting found in the Vim Java syntax.\r\n\r\nhttps:\/\/github.com\/tetsuo13\/Vim-PHP-Doc","install_details":"Copy the php.vim file to:\r\nUnix: ~\/.vim\/after\/syntax\r\nWindows: C:\\vimfiles\\after\\syntax","5":"Copy the php.vim file to:\r\nUnix: ~\/.vim\/after\/syntax\r\nWindows: C:\\vimfiles\\after\\syntax","first_name":"Andrei","6":"Andrei","last_name":"Nicholson","7":"Nicholson","releases":[{"0":"2548","vim_version":"6.0","1":"6.0","script_version":"1.1","2":"1.1","version_comment":"Sync with GitHub.","3":"Sync with GitHub.","package":"php.vim","4":"php.vim","src_id":"15402","5":"15402","creation_date":"1302100035","6":"1302100035"},{"0":"2548","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"php.vim","4":"php.vim","src_id":"10005","5":"10005","creation_date":"1235263494","6":"1235263494"}]},"2547":{"script_id":"2547","0":"2547","script_name":"xsltassistant.vim","1":"xsltassistant.vim","script_type":"ftplugin","2":"ftplugin","summary":"xsltassistant.vim helps you write the XSLT file","3":"xsltassistant.vim helps you write the XSLT file","description":"A plugin works with the help of the xml.vim(http:\/\/www.vim.org\/scripts\/script.php?script_id=1397).\r\nXSLT keywords may be accessed by its short cut,for example,under insert mode,insert the \",sty\" will result in \r\n<?xml version=\"1.0\"?>\r\n<xsl:stylesheet\r\n\tversion=\"1.0\"\r\n\txmlns:xsl=\"http:\/\/www.w3.org\/1999\/XSL\/Transform\">\r\n\r\n<\/xsl:stylesheet>\r\nFor more short cuts,check the head of the xsltassistant.vim.","4":"A plugin works with the help of the xml.vim(http:\/\/www.vim.org\/scripts\/script.php?script_id=1397).\r\nXSLT keywords may be accessed by its short cut,for example,under insert mode,insert the \",sty\" will result in \r\n<?xml version=\"1.0\"?>\r\n<xsl:stylesheet\r\n\tversion=\"1.0\"\r\n\txmlns:xsl=\"http:\/\/www.w3.org\/1999\/XSL\/Transform\">\r\n\r\n<\/xsl:stylesheet>\r\nFor more short cuts,check the head of the xsltassistant.vim.","install_details":"extract the file to your .vim\/ftplugin directory.(xml.vim mentioned above needed)","5":"extract the file to your .vim\/ftplugin directory.(xml.vim mentioned above needed)","first_name":"wyw","6":"wyw","last_name":"acczy","7":"acczy","releases":[{"0":"2547","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"xslt.tar.gz","4":"xslt.tar.gz","src_id":"9999","5":"9999","creation_date":"1235145347","6":"1235145347"}]},"2546":{"script_id":"2546","0":"2546","script_name":"repy.vim","1":"repy.vim","script_type":"syntax","2":"syntax","summary":"Syntax Coloring for Restricted Python","3":"Syntax Coloring for Restricted Python","description":"This is the syntax file for RePy - https:\/\/seattle.cs.washington.edu\/wiki\/RepyLibrary\r\n\r\nIt needs the python.vim from Dmitry Vasiliev found at http:\/\/www.vim.org\/scripts\/script.php?script_id=790\r\n","4":"This is the syntax file for RePy - https:\/\/seattle.cs.washington.edu\/wiki\/RepyLibrary\r\n\r\nIt needs the python.vim from Dmitry Vasiliev found at http:\/\/www.vim.org\/scripts\/script.php?script_id=790\r\n","install_details":"Step 0 - If you don't have it already, get the python.vim syntax plugin at: http:\/\/www.vim.org\/scripts\/script.php?script_id=790\r\n\r\nStep 1 - Copy repy.vim into ~\/.vim\/syntax.\r\n\r\nStep 2 - Add the following line to ~\/.vimrc:\r\nau! BufRead,BufNewFile *.repy  setfiletype repy","5":"Step 0 - If you don't have it already, get the python.vim syntax plugin at: http:\/\/www.vim.org\/scripts\/script.php?script_id=790\r\n\r\nStep 1 - Copy repy.vim into ~\/.vim\/syntax.\r\n\r\nStep 2 - Add the following line to ~\/.vimrc:\r\nau! BufRead,BufNewFile *.repy  setfiletype repy","first_name":"Joao","6":"Joao","last_name":"Moreno","7":"Moreno","releases":[{"0":"2546","vim_version":"6.0","1":"6.0","script_version":"1.1","2":"1.1","version_comment":"* Added 'import' as a forbidden expression.\r\n* Added Thanks","3":"* Added 'import' as a forbidden expression.\r\n* Added Thanks","package":"repy.vim","4":"repy.vim","src_id":"9998","5":"9998","creation_date":"1235070210","6":"1235070210"},{"0":"2546","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"repy.vim","4":"repy.vim","src_id":"9997","5":"9997","creation_date":"1235067157","6":"1235067157"}]},"2545":{"script_id":"2545","0":"2545","script_name":"Buffer grep","1":"Buffer grep","script_type":"utility","2":"utility","summary":"A :vimgrep for buffers.","3":"A :vimgrep for buffers.","description":"Use \r\n  Bgrep \/expression\/ \r\nto search all buffers for an expression and put it in a new quickfix list.","4":"Use \r\n  Bgrep \/expression\/ \r\nto search all buffers for an expression and put it in a new quickfix list.","install_details":"Install as a plugin.","5":"Install as a plugin.","first_name":"Michael","6":"Michael","last_name":"Geddes","7":"Geddes","releases":[{"0":"2545","vim_version":"6.0","1":"6.0","script_version":"0.3","2":"0.3","version_comment":"Fix up error when there is no \/\/\r\nFix up handling of windows in some edge cases.\r\n","3":"Fix up error when there is no \/\/\r\nFix up handling of windows in some edge cases.\r\n","package":"bufgrep.vim","4":"bufgrep.vim","src_id":"11126","5":"11126","creation_date":"1249351186","6":"1249351186"},{"0":"2545","vim_version":"6.0","1":"6.0","script_version":"0.2","2":"0.2","version_comment":"fixed a couple of issues with  Bgrep word","3":"fixed a couple of issues with  Bgrep word","package":"bufgrep.vim","4":"bufgrep.vim","src_id":"10795","5":"10795","creation_date":"1244588428","6":"1244588428"},{"0":"2545","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"bufgrep.vim","4":"bufgrep.vim","src_id":"9993","5":"9993","creation_date":"1235010871","6":"1235010871"}]},"2544":{"script_id":"2544","0":"2544","script_name":"EditSimilar","1":"EditSimilar","script_type":"utility","2":"utility","summary":"Commands to edit files with a similar filename. ","3":"Commands to edit files with a similar filename. ","description":"DESCRIPTION\r\nFiles edited in Vim often relate to one another; maybe they just differ in\r\nfile extensions, are numbered sequentially, or contain common patterns. One\r\ncan use the built-in cmdline-completion  or filename-modifiers like %:r to\r\nquickly edit a similar file, or even use special plugins, e.g. to alternate\r\nbetween source and header files (vimscript #31).\r\n\r\nThis plugin provides custom versions of\r\nthe|:edit|,|:view|,|:split|,|:vsplit|,|:sview|,|:file|,|:write| and|:saveas|\r\ncommands which facilitate quick and simple editing of similarly named files.\r\nTo quickly edit another file based on the current file, one can:\r\n- substitute {old} with {new}                      EditSimilar-substitutions\r\n- go to previous\/next numbered file or                    EditSimilar-offset\r\n  add any offset to the number\r\n- go to succeeding \/ preceding files in the same directory  EditSimilar-next\r\n- change the file extension                                 EditSimilar-root\r\n\r\nTo open a set of similar files, it is possible to:\r\n- open all files matching a pattern in split windows     EditSimilar-pattern\r\n\r\nSEE ALSO\r\n- The PatternsOnText.vim plugin (vimscript #4602) applies the\r\n  {text}={replacement} of :EditSubstitute via :substitute to the text in the\r\n  buffer with :SubstituteWildcard.\r\n\r\nRELATED WORKS\r\n- altr (vimscript #4202) lets you set up custom (per-filetype) rules and then\r\n  opens related files through two forward \/ backward mappings, e.g. allowing\r\n  you to open the autoload file from the plugin.\r\n- nextfile (vimscript #4698) has definitions of related files (like Rails\r\n  controllers, views, model, tests), and can edit a next file via a mapping.\r\n- projectile (https:\/\/github.com\/tpope\/vim-projectile) allows you to define\r\n  per-project settings and navigation commands, e.g. :Eplugin and :Edoc.\r\n- unimpaired.vim (vimscript #1590) has (among many other, largely unrelated)\r\n  [f \/ ]f mappings that work like :EditPrevious \/ :EditNext.\r\n\r\nUSAGE\r\nSUBSTITUTE\r\nChange all occurrences via {text}={replacement} in the currently edited file\r\n(modeled after the Korn shell's \"cd {old} {new}\" command). This can also be\r\nachieved with the built-in filename-modifiers:\r\n    :edit %:gs?pattern?replacement?\r\nbut the syntax is difficult to memorize (it's subtly different from :s) and\r\nharder to type (because one has to use regular expressions instead of the\r\nsimpler file wildcards).\r\n\r\n:EditSubstitute[!] {text}={replacement} [{text}={replacement} [...]]\r\n\r\n:ViewSubstitute[!] {text}={replacement} [{text}={replacement} [...]]\r\n\r\n:SplitSubstitute[!] {text}={replacement} [{text}={replacement} [...]]\r\n\r\n:VSplitSubstitute[!] {text}={replacement} [{text}={replacement} [...]]\r\n\r\n:SViewSubstitute[!] {text}={replacement} [{text}={replacement} [...]]\r\n\r\n:DiffSplitSubstitute[!] {text}={replacement} [{text}={replacement} [...]]\r\n                        Replaces all literal occurrences of {text} in the\r\n                        currently edited file with {replacement}, and opens the\r\n                        resulting file. If all substitutions can be made on the\r\n                        filename, the pathspec is left alone (so you don't get\r\n                        any false replacements on a long pathspec). Otherwise,\r\n                        the substitutions that weren't applicable to the\r\n                        filename are done to the full absolute pathspec.\r\n                        Finally, substitutions spanning both pathspec and\r\n                        filename are made.\r\n\r\n                        By taking advantage of these substitution scopes, you\r\n                        can substitute occurrences in both path and filename\r\n                        by specifying the same substitution twice:\r\n                            \/etc\/test\/superapp\/test001.cfg\r\n                            :EditSubstitute test=prod\r\n                            \/etc\/test\/superapp\/prod001.cfg\r\n                            :EditSubstitute test=prod test=prod\r\n                            \/etc\/prod\/superapp\/prod001.cfg\r\n                       Or perform different substitutions on filename and\r\n                        pathspec:\r\n                            \/etc\/test\/superapp\/test001.cfg\r\n                            :EditSubstitute test=prod test=production\r\n                            \/etc\/production\/superapp\/prod001.cfg\r\n                       Or across the entire filespec: >\r\n                            \/etc\/test\/superapp\/test001.cfg\r\n                            :EditSubstitute superapp\/test=normalapp\/prod\r\n                            \/etc\/test\/normalapp\/prod001.cfg\r\n\r\n                       Both {text} and {replacement} can include the usual\r\n                        file wildcards (?, *, ** and [...], cp. file-pattern)\r\n                        to save typing; however, the file-pattern must resolve\r\n                        to exactly one filespec, as the underlying Ex commands\r\n                        can only open a single file.\r\n                            \/etc\/test\/superapp\/test001.cfg\r\n                            :EditSubstitute test=p* test=p*\r\n                            \/etc\/production\/superapp\/prod001.cfg\r\n                            :EditSubstitute **=\/tmp [01]=X\r\n                            \/tmp\/prodXXX.cfg\r\n                       Add [!] to create a new file when the substituted file\r\n                        does not exist.\r\n                        With the special {text}=?{replacement} syntax, you can\r\n                        define optional substitutions that if done don't count\r\n                        yet as a successful substitution; another\r\n                        {text2}={replacement2} must still happen (to edit the\r\n                        file \/ create a new file with [!]). This allows you to\r\n                        define switch commands that only happen when the\r\n                        crucial substitution can be done, yet still do other\r\n                        adaptations as well.\r\n\r\n:FileSubstitute {text}={replacement} [{text}={replacement} [...]]\r\n\r\n:[range]WriteSubstitute[!] {text}={replacement} [{text}={replacement} [...]]\r\n\r\n:SaveSubstitute[!] {text}={replacement} [{text}={replacement} [...]]\r\n                        Replaces all occurrences of {text} in the currently\r\n                        edited file with {replacement}, and sets \/ writes the\r\n                        resulting file. Wildcards can be used here, too.\r\n                        The [!] is needed to overwrite an existing file.\r\n\r\n:BDeleteSubstitute[!] {text}={replacement} [{text}={replacement} [...]]\r\n                        Replaces all occurrences of {text} in the currently\r\n                        edited file with {replacement}, and deletes the\r\n                        resulting buffer. Wildcards can be used here, too.\r\n                        The [!] is needed to delete a changed buffer.\r\n\r\nPLUS MINUS\r\nAdd an offset to the last (decimal) number in the currently edited file.\r\n\r\n:[N]EditPlus[!] [N]\r\n:[N]EditMinus[!] [N]\r\n\r\n:[N]ViewPlus[!] [N]\r\n:[N]ViewMinus[!] [N]\r\n\r\n:[N]SplitPlus[!] [N]\r\n:[N]SplitMinus[!] [N]\r\n\r\n:[N]VSplitPlus[!] [N]\r\n:[N]VSplitMinus[!] [N]\r\n\r\n:[N]SViewPlus[!] [N]\r\n:[N]SViewMinus[!] [N]\r\n\r\n:[N]DiffSplitPlus[!] [N]\r\n:[N]DiffSplitMinus[!] [N]\r\n                        Increases \/ decreases the last number found inside the\r\n                        full absolute filespec of the currently edited file by\r\n                        [N]. This works best on fixed-width numbers which are\r\n                        padded with leading zeros: 001, 011, 123, etc.\r\n                        If a file with that number does not exist, the\r\n                        substitution is retried with larger (no [N]) or\r\n                        smaller ([N] given) offsets, unless [!] is specified.\r\n                        This way, you can easily skip to the last \/ first\r\n                        numbered file by specifying a sufficiently large [N],\r\n                        (e.g. :99EditPlus), while zooming over gaps in the\r\n                        numbering via a simple :EditPlus.\r\n                        With [!], no skipping over non-existing numbers takes\r\n                        place; instead, a new file is created when the\r\n                        substituted file does not exist.\r\n                        When jumping to previous numbers, the resulting number\r\n                        will never be negative. A jump with [!] and [N] > 1 will\r\n                        create a file with number 1, not 0, but you can still\r\n                        create number 0 by repeating the command with [N] = 1.\r\n                        Examples:\r\n                        test007.txt in a directory also containing 003-013.\r\n                        :EditPlus      -> test008.txt\r\n                        :99EditPlus    -> test013.txt\r\n                        :99EditPlus!   -> test106.txt [New File]\r\n                        :99Eprev       -> test003.txt\r\n                        :99Eprev!      -> test001.txt [New File]\r\n                        :EditPlus      -> test003.txt\r\n\r\n:[N]FilePlus[!] [N]\r\n:[N]FileMinus[!] [N]\r\n\r\n:[range]WritePlus[!] [N]\r\n:[range]WriteMinus[!] [N]\r\n\r\n:[N]SavePlus[!] [N]\r\n:[N]SaveMinus[!] [N]\r\n                        Increases \/ decreases the last number found inside the\r\n                        full absolute filespec of the currently edited file by\r\n                        [N] and sets \/ writes that file. (A fixed number width\r\n                        via padding with leading zeros is maintained.)\r\n                        When [N] is given and no [!] is given, an existing\r\n                        file with an offset of [N] or smaller is searched, and\r\n                        if such an offset is found, that offset incremented by\r\n                        one is used. This lets you use a large [N] to write\r\n                        the file with the next number within [N] for which no\r\n                        file exists yet.\r\n                        When [!] is given, the file with the added offset is\r\n                        written, plain and simple. [!] is also needed to\r\n                        overwrite an existing file.\r\n                        Examples:\r\n                        test007.txt in a directory also containing 003-013.\r\n                        :WritePlus     -> file exists\r\n                        :WritePlus!    -> test008.txt\r\n                        :WritePlus 99  -> test014.txt [New File]\r\n                        :WritePlus! 99 -> test106.txt [New File]\r\n\r\n:[N]BDeletePlus[!] [N]\r\n:[N]BDeleteMinus[!] [N]\r\n                        Increases \/ decreases the last number found inside the\r\n                        full absolute filespec of the currently edited file by\r\n                        [N] and deletes that buffer.\r\n\r\nNEXT PREVIOUS\r\nIn the directory listing of the current file, go to succeeding \/ preceding\r\nfile entries.\r\n\r\n:[N]EditNext[!] [{filelist}]\r\n:[N]EditPrevious[!] [{filelist}]\r\n\r\n:[N]ViewNext[!] [{filelist}]\r\n:[N]ViewPrevious[!] [{filelist}]\r\n\r\n:[N]SplitNext[!] [{filelist}]\r\n:[N]SplitPrevious[!] [{filelist}]\r\n\r\n:[N]VSplitNext[!] [{filelist}]\r\n:[N]VSplitPrevious[!] [{filelist}]\r\n\r\n:[N]SViewNext[!] [{filelist}]\r\n:[N]SViewPrevious[!] [{filelist}]\r\n\r\n:[N]DiffSplitNext[!] [{filelist}]\r\n:[N]DiffSplitPrevious[!] [{filelist}]\r\n                        From the files in the same directory as the current\r\n                        file, go to a succeeding \/ preceding one. If\r\n                        {filelist} is specified (typically not via separate\r\n                        files, but a file glob like foo*.txt), only those\r\n                        files matching the glob are considered. Otherwise,\r\n                        is used, i.e. all files not starting with \".\" are\r\n                        considered. To consider really all files, pass .*\r\n                        The 'wildignore' setting applies; matching files are\r\n                        ignored, as well as any subdirectories.\r\n                        The order of files is determined by the order in\r\n                        {filelist} and the operating system \/ file system's\r\n                        resolution of the glob, as elsewhere in Vim.\r\n                        The current buffer must be contained in {filelist} for\r\n                        the commands to work.\r\n\r\n:[N]BDeleteNext[!] [{filelist}]\r\n:[N]BDeletePrevious[!] [{filelist}]\r\n                        Delete a succeeding \/ preceding buffer.\r\n\r\nROOT\r\nChange the file extension in the currently edited file. This is an enhanced\r\nversion of the built-in:\r\n    :edit %:r.{extension}\r\n\r\n:EditRoot[!] {extension}\r\n\r\n:ViewRoot[!] {extension}\r\n\r\n:SplitRoot[!] {extension}\r\n\r\n:VSplitRoot[!] {extension}\r\n\r\n:SViewRoot[!] {extension}\r\n\r\n:DiffSplitRoot[!] {extension}\r\n                        Switches the current file's extension:\r\n                        Edits a file with the current file's path and name, but\r\n                        replaces the file extension with the passed one. The\r\n                        leading '.' in {extension} is optional; use either\r\n                        .txt or txt. To get a file without an extension, use .\r\n                            :EditRoot .\r\n                            myfile\r\n                       To replace (or remove) multiple extensions, prepend a\r\n                        . for each one:\r\n                            myfile.txt.bak\r\n                            :EditRoot ..cpp\r\n                            myfile.cpp\r\n\r\n                        The {extension} can include the usual file wildcards\r\n                        (?, *, cp. file-pattern) to save typing; however, the\r\n                        file-pattern must resolve to exactly one existing\r\n                        file, as the underlying Ex commands can only open one\r\n                        single file.\r\n\r\n                        Add [!] to create a new file when the substituted file\r\n                        does not exist.\r\n\r\n:FileRoot {extension}\r\n\r\n:[range]WriteRoot[!] {extension}\r\n\r\n:SaveRoot[!] {extension}\r\n                        Sets \/ saves a file with the current file's path and\r\n                        name, but replaces the file extension with the passed\r\n                        one.\r\n                        The [!] is needed to overwrite an existing file.\r\n\r\n:BDeleteRoot[!] {extension}\r\n                        Deletes a buffer with a different file extension.\r\n\r\nPATTERN\r\nOpen all files matching the file-pattern (actually a file glob) in split\r\nwindows, similar to how |:argadd|{name} adds all matching files to the\r\nargument list.\r\n\r\n:SplitPattern [++opt] [+cmd] {file-pattern} [{file-pattern} ...]\r\n\r\n:VSplitPattern [++opt] [+cmd] {file-pattern} [{file-pattern} ...]\r\n\r\n:SViewPattern [++opt] [+cmd] {file-pattern} [{file-pattern} ...]\r\n\r\n:DiffSplitPattern [++opt] [+cmd] {file-pattern} [{file-pattern} ...]\r\n                        Open all files matching {file-pattern} in split windows.\r\n                        If one of the files is already open, no second split is\r\n                        generated.\r\n                        The {file-pattern} can include the usual file wildcards\r\n                        (?, *, cp. file-pattern).\r\n                        Makes all windows the same size if more than one has\r\n                        been opened.\r\n\r\n:BDeletePattern {file-pattern} [{file-pattern} ...]\r\n                        Delete all buffers matching {file-pattern}.\r\n\r\nSUPPORTING COMMANDS\r\n:SaveOverBufferAs[!] [++opt] {file}\r\n                        Like :saveas, but with [!] also suppresses the\r\n                        E139: \"File is loaded in another buffer\" error by\r\n                        forcibly deleting the buffer (any unpersisted changes\r\n                        there will be lost). With this plugin, one often\r\n                        (re-)updates similar files that are already loaded in\r\n                        Vim. This command (which is also used in the :Save...\r\n                        commands) avoids the need to issue a separate\r\n                            :BDelete... | Save...\r\n\r\n:[range]WriteOverBuffer[!] [++opt] {file}\r\n                        Like :write, but with [!] also suppresses the\r\n                        E139: \"File is loaded in another buffer\" error by\r\n                        forcibly deleting the buffer (any unpersisted changes\r\n                        there will be lost). Used in the :Write... commands.","4":"DESCRIPTION\r\nFiles edited in Vim often relate to one another; maybe they just differ in\r\nfile extensions, are numbered sequentially, or contain common patterns. One\r\ncan use the built-in cmdline-completion  or filename-modifiers like %:r to\r\nquickly edit a similar file, or even use special plugins, e.g. to alternate\r\nbetween source and header files (vimscript #31).\r\n\r\nThis plugin provides custom versions of\r\nthe|:edit|,|:view|,|:split|,|:vsplit|,|:sview|,|:file|,|:write| and|:saveas|\r\ncommands which facilitate quick and simple editing of similarly named files.\r\nTo quickly edit another file based on the current file, one can:\r\n- substitute {old} with {new}                      EditSimilar-substitutions\r\n- go to previous\/next numbered file or                    EditSimilar-offset\r\n  add any offset to the number\r\n- go to succeeding \/ preceding files in the same directory  EditSimilar-next\r\n- change the file extension                                 EditSimilar-root\r\n\r\nTo open a set of similar files, it is possible to:\r\n- open all files matching a pattern in split windows     EditSimilar-pattern\r\n\r\nSEE ALSO\r\n- The PatternsOnText.vim plugin (vimscript #4602) applies the\r\n  {text}={replacement} of :EditSubstitute via :substitute to the text in the\r\n  buffer with :SubstituteWildcard.\r\n\r\nRELATED WORKS\r\n- altr (vimscript #4202) lets you set up custom (per-filetype) rules and then\r\n  opens related files through two forward \/ backward mappings, e.g. allowing\r\n  you to open the autoload file from the plugin.\r\n- nextfile (vimscript #4698) has definitions of related files (like Rails\r\n  controllers, views, model, tests), and can edit a next file via a mapping.\r\n- projectile (https:\/\/github.com\/tpope\/vim-projectile) allows you to define\r\n  per-project settings and navigation commands, e.g. :Eplugin and :Edoc.\r\n- unimpaired.vim (vimscript #1590) has (among many other, largely unrelated)\r\n  [f \/ ]f mappings that work like :EditPrevious \/ :EditNext.\r\n\r\nUSAGE\r\nSUBSTITUTE\r\nChange all occurrences via {text}={replacement} in the currently edited file\r\n(modeled after the Korn shell's \"cd {old} {new}\" command). This can also be\r\nachieved with the built-in filename-modifiers:\r\n    :edit %:gs?pattern?replacement?\r\nbut the syntax is difficult to memorize (it's subtly different from :s) and\r\nharder to type (because one has to use regular expressions instead of the\r\nsimpler file wildcards).\r\n\r\n:EditSubstitute[!] {text}={replacement} [{text}={replacement} [...]]\r\n\r\n:ViewSubstitute[!] {text}={replacement} [{text}={replacement} [...]]\r\n\r\n:SplitSubstitute[!] {text}={replacement} [{text}={replacement} [...]]\r\n\r\n:VSplitSubstitute[!] {text}={replacement} [{text}={replacement} [...]]\r\n\r\n:SViewSubstitute[!] {text}={replacement} [{text}={replacement} [...]]\r\n\r\n:DiffSplitSubstitute[!] {text}={replacement} [{text}={replacement} [...]]\r\n                        Replaces all literal occurrences of {text} in the\r\n                        currently edited file with {replacement}, and opens the\r\n                        resulting file. If all substitutions can be made on the\r\n                        filename, the pathspec is left alone (so you don't get\r\n                        any false replacements on a long pathspec). Otherwise,\r\n                        the substitutions that weren't applicable to the\r\n                        filename are done to the full absolute pathspec.\r\n                        Finally, substitutions spanning both pathspec and\r\n                        filename are made.\r\n\r\n                        By taking advantage of these substitution scopes, you\r\n                        can substitute occurrences in both path and filename\r\n                        by specifying the same substitution twice:\r\n                            \/etc\/test\/superapp\/test001.cfg\r\n                            :EditSubstitute test=prod\r\n                            \/etc\/test\/superapp\/prod001.cfg\r\n                            :EditSubstitute test=prod test=prod\r\n                            \/etc\/prod\/superapp\/prod001.cfg\r\n                       Or perform different substitutions on filename and\r\n                        pathspec:\r\n                            \/etc\/test\/superapp\/test001.cfg\r\n                            :EditSubstitute test=prod test=production\r\n                            \/etc\/production\/superapp\/prod001.cfg\r\n                       Or across the entire filespec: >\r\n                            \/etc\/test\/superapp\/test001.cfg\r\n                            :EditSubstitute superapp\/test=normalapp\/prod\r\n                            \/etc\/test\/normalapp\/prod001.cfg\r\n\r\n                       Both {text} and {replacement} can include the usual\r\n                        file wildcards (?, *, ** and [...], cp. file-pattern)\r\n                        to save typing; however, the file-pattern must resolve\r\n                        to exactly one filespec, as the underlying Ex commands\r\n                        can only open a single file.\r\n                            \/etc\/test\/superapp\/test001.cfg\r\n                            :EditSubstitute test=p* test=p*\r\n                            \/etc\/production\/superapp\/prod001.cfg\r\n                            :EditSubstitute **=\/tmp [01]=X\r\n                            \/tmp\/prodXXX.cfg\r\n                       Add [!] to create a new file when the substituted file\r\n                        does not exist.\r\n                        With the special {text}=?{replacement} syntax, you can\r\n                        define optional substitutions that if done don't count\r\n                        yet as a successful substitution; another\r\n                        {text2}={replacement2} must still happen (to edit the\r\n                        file \/ create a new file with [!]). This allows you to\r\n                        define switch commands that only happen when the\r\n                        crucial substitution can be done, yet still do other\r\n                        adaptations as well.\r\n\r\n:FileSubstitute {text}={replacement} [{text}={replacement} [...]]\r\n\r\n:[range]WriteSubstitute[!] {text}={replacement} [{text}={replacement} [...]]\r\n\r\n:SaveSubstitute[!] {text}={replacement} [{text}={replacement} [...]]\r\n                        Replaces all occurrences of {text} in the currently\r\n                        edited file with {replacement}, and sets \/ writes the\r\n                        resulting file. Wildcards can be used here, too.\r\n                        The [!] is needed to overwrite an existing file.\r\n\r\n:BDeleteSubstitute[!] {text}={replacement} [{text}={replacement} [...]]\r\n                        Replaces all occurrences of {text} in the currently\r\n                        edited file with {replacement}, and deletes the\r\n                        resulting buffer. Wildcards can be used here, too.\r\n                        The [!] is needed to delete a changed buffer.\r\n\r\nPLUS MINUS\r\nAdd an offset to the last (decimal) number in the currently edited file.\r\n\r\n:[N]EditPlus[!] [N]\r\n:[N]EditMinus[!] [N]\r\n\r\n:[N]ViewPlus[!] [N]\r\n:[N]ViewMinus[!] [N]\r\n\r\n:[N]SplitPlus[!] [N]\r\n:[N]SplitMinus[!] [N]\r\n\r\n:[N]VSplitPlus[!] [N]\r\n:[N]VSplitMinus[!] [N]\r\n\r\n:[N]SViewPlus[!] [N]\r\n:[N]SViewMinus[!] [N]\r\n\r\n:[N]DiffSplitPlus[!] [N]\r\n:[N]DiffSplitMinus[!] [N]\r\n                        Increases \/ decreases the last number found inside the\r\n                        full absolute filespec of the currently edited file by\r\n                        [N]. This works best on fixed-width numbers which are\r\n                        padded with leading zeros: 001, 011, 123, etc.\r\n                        If a file with that number does not exist, the\r\n                        substitution is retried with larger (no [N]) or\r\n                        smaller ([N] given) offsets, unless [!] is specified.\r\n                        This way, you can easily skip to the last \/ first\r\n                        numbered file by specifying a sufficiently large [N],\r\n                        (e.g. :99EditPlus), while zooming over gaps in the\r\n                        numbering via a simple :EditPlus.\r\n                        With [!], no skipping over non-existing numbers takes\r\n                        place; instead, a new file is created when the\r\n                        substituted file does not exist.\r\n                        When jumping to previous numbers, the resulting number\r\n                        will never be negative. A jump with [!] and [N] > 1 will\r\n                        create a file with number 1, not 0, but you can still\r\n                        create number 0 by repeating the command with [N] = 1.\r\n                        Examples:\r\n                        test007.txt in a directory also containing 003-013.\r\n                        :EditPlus      -> test008.txt\r\n                        :99EditPlus    -> test013.txt\r\n                        :99EditPlus!   -> test106.txt [New File]\r\n                        :99Eprev       -> test003.txt\r\n                        :99Eprev!      -> test001.txt [New File]\r\n                        :EditPlus      -> test003.txt\r\n\r\n:[N]FilePlus[!] [N]\r\n:[N]FileMinus[!] [N]\r\n\r\n:[range]WritePlus[!] [N]\r\n:[range]WriteMinus[!] [N]\r\n\r\n:[N]SavePlus[!] [N]\r\n:[N]SaveMinus[!] [N]\r\n                        Increases \/ decreases the last number found inside the\r\n                        full absolute filespec of the currently edited file by\r\n                        [N] and sets \/ writes that file. (A fixed number width\r\n                        via padding with leading zeros is maintained.)\r\n                        When [N] is given and no [!] is given, an existing\r\n                        file with an offset of [N] or smaller is searched, and\r\n                        if such an offset is found, that offset incremented by\r\n                        one is used. This lets you use a large [N] to write\r\n                        the file with the next number within [N] for which no\r\n                        file exists yet.\r\n                        When [!] is given, the file with the added offset is\r\n                        written, plain and simple. [!] is also needed to\r\n                        overwrite an existing file.\r\n                        Examples:\r\n                        test007.txt in a directory also containing 003-013.\r\n                        :WritePlus     -> file exists\r\n                        :WritePlus!    -> test008.txt\r\n                        :WritePlus 99  -> test014.txt [New File]\r\n                        :WritePlus! 99 -> test106.txt [New File]\r\n\r\n:[N]BDeletePlus[!] [N]\r\n:[N]BDeleteMinus[!] [N]\r\n                        Increases \/ decreases the last number found inside the\r\n                        full absolute filespec of the currently edited file by\r\n                        [N] and deletes that buffer.\r\n\r\nNEXT PREVIOUS\r\nIn the directory listing of the current file, go to succeeding \/ preceding\r\nfile entries.\r\n\r\n:[N]EditNext[!] [{filelist}]\r\n:[N]EditPrevious[!] [{filelist}]\r\n\r\n:[N]ViewNext[!] [{filelist}]\r\n:[N]ViewPrevious[!] [{filelist}]\r\n\r\n:[N]SplitNext[!] [{filelist}]\r\n:[N]SplitPrevious[!] [{filelist}]\r\n\r\n:[N]VSplitNext[!] [{filelist}]\r\n:[N]VSplitPrevious[!] [{filelist}]\r\n\r\n:[N]SViewNext[!] [{filelist}]\r\n:[N]SViewPrevious[!] [{filelist}]\r\n\r\n:[N]DiffSplitNext[!] [{filelist}]\r\n:[N]DiffSplitPrevious[!] [{filelist}]\r\n                        From the files in the same directory as the current\r\n                        file, go to a succeeding \/ preceding one. If\r\n                        {filelist} is specified (typically not via separate\r\n                        files, but a file glob like foo*.txt), only those\r\n                        files matching the glob are considered. Otherwise,\r\n                        is used, i.e. all files not starting with \".\" are\r\n                        considered. To consider really all files, pass .*\r\n                        The 'wildignore' setting applies; matching files are\r\n                        ignored, as well as any subdirectories.\r\n                        The order of files is determined by the order in\r\n                        {filelist} and the operating system \/ file system's\r\n                        resolution of the glob, as elsewhere in Vim.\r\n                        The current buffer must be contained in {filelist} for\r\n                        the commands to work.\r\n\r\n:[N]BDeleteNext[!] [{filelist}]\r\n:[N]BDeletePrevious[!] [{filelist}]\r\n                        Delete a succeeding \/ preceding buffer.\r\n\r\nROOT\r\nChange the file extension in the currently edited file. This is an enhanced\r\nversion of the built-in:\r\n    :edit %:r.{extension}\r\n\r\n:EditRoot[!] {extension}\r\n\r\n:ViewRoot[!] {extension}\r\n\r\n:SplitRoot[!] {extension}\r\n\r\n:VSplitRoot[!] {extension}\r\n\r\n:SViewRoot[!] {extension}\r\n\r\n:DiffSplitRoot[!] {extension}\r\n                        Switches the current file's extension:\r\n                        Edits a file with the current file's path and name, but\r\n                        replaces the file extension with the passed one. The\r\n                        leading '.' in {extension} is optional; use either\r\n                        .txt or txt. To get a file without an extension, use .\r\n                            :EditRoot .\r\n                            myfile\r\n                       To replace (or remove) multiple extensions, prepend a\r\n                        . for each one:\r\n                            myfile.txt.bak\r\n                            :EditRoot ..cpp\r\n                            myfile.cpp\r\n\r\n                        The {extension} can include the usual file wildcards\r\n                        (?, *, cp. file-pattern) to save typing; however, the\r\n                        file-pattern must resolve to exactly one existing\r\n                        file, as the underlying Ex commands can only open one\r\n                        single file.\r\n\r\n                        Add [!] to create a new file when the substituted file\r\n                        does not exist.\r\n\r\n:FileRoot {extension}\r\n\r\n:[range]WriteRoot[!] {extension}\r\n\r\n:SaveRoot[!] {extension}\r\n                        Sets \/ saves a file with the current file's path and\r\n                        name, but replaces the file extension with the passed\r\n                        one.\r\n                        The [!] is needed to overwrite an existing file.\r\n\r\n:BDeleteRoot[!] {extension}\r\n                        Deletes a buffer with a different file extension.\r\n\r\nPATTERN\r\nOpen all files matching the file-pattern (actually a file glob) in split\r\nwindows, similar to how |:argadd|{name} adds all matching files to the\r\nargument list.\r\n\r\n:SplitPattern [++opt] [+cmd] {file-pattern} [{file-pattern} ...]\r\n\r\n:VSplitPattern [++opt] [+cmd] {file-pattern} [{file-pattern} ...]\r\n\r\n:SViewPattern [++opt] [+cmd] {file-pattern} [{file-pattern} ...]\r\n\r\n:DiffSplitPattern [++opt] [+cmd] {file-pattern} [{file-pattern} ...]\r\n                        Open all files matching {file-pattern} in split windows.\r\n                        If one of the files is already open, no second split is\r\n                        generated.\r\n                        The {file-pattern} can include the usual file wildcards\r\n                        (?, *, cp. file-pattern).\r\n                        Makes all windows the same size if more than one has\r\n                        been opened.\r\n\r\n:BDeletePattern {file-pattern} [{file-pattern} ...]\r\n                        Delete all buffers matching {file-pattern}.\r\n\r\nSUPPORTING COMMANDS\r\n:SaveOverBufferAs[!] [++opt] {file}\r\n                        Like :saveas, but with [!] also suppresses the\r\n                        E139: \"File is loaded in another buffer\" error by\r\n                        forcibly deleting the buffer (any unpersisted changes\r\n                        there will be lost). With this plugin, one often\r\n                        (re-)updates similar files that are already loaded in\r\n                        Vim. This command (which is also used in the :Save...\r\n                        commands) avoids the need to issue a separate\r\n                            :BDelete... | Save...\r\n\r\n:[range]WriteOverBuffer[!] [++opt] {file}\r\n                        Like :write, but with [!] also suppresses the\r\n                        E139: \"File is loaded in another buffer\" error by\r\n                        forcibly deleting the buffer (any unpersisted changes\r\n                        there will be lost). Used in the :Write... commands.","install_details":"INSTALLATION\r\nThe code is hosted in a Git repo at\r\n    https:\/\/github.com\/inkarkat\/vim-EditSimilar\r\nYou can use your favorite plugin manager, or \"git clone\" into a directory used\r\nfor Vim packages. Releases are on the \"stable\" branch, the latest unstable\r\ndevelopment snapshot on \"master\".\r\n\r\nThis script is also packaged as a vimball. If you have the \"gunzip\"\r\ndecompressor in your PATH, simply edit the *.vmb.gz package in Vim; otherwise,\r\ndecompress the archive first, e.g. using WinZip. Inside Vim, install by\r\nsourcing the vimball or via the :UseVimball command.\r\n    vim EditSimilar*.vmb.gz\r\n    :so %\r\nTo uninstall, use the :RmVimball command.\r\n\r\nDEPENDENCIES\r\n- Requires Vim 7.0 or higher.\r\n- Requires the ingo-library.vim plugin (vimscript #4433), version 1.025 or\r\n  higher.\r\n- Optional, recommended: cmdalias plugin (vimscript #746)\r\n\r\nCONFIGURATION\r\nFor a permanent configuration, put the following commands into your vimrc:\r\n\r\nAll these edit commands are about speed; after all, they vie to be a faster\r\nalternative to the built-in commands that take a complete filename. Each\r\nuser's Vim setup and behavior is different. Therefore, the previously defined\r\nshort command forms :Esubst, :Enext, etc. are gone in version 1.20. Instead,\r\nyou are encouraged to define your own shortcuts, depending on your preferences\r\nand needs. A great way to do this (because it allows the definition of pure\r\nlowercase commands) is defining short aliases through the cmdalias plugin\r\n(vimscript #746), like this:\r\n    \" Shorten the most frequently used commands from EditSimilar.vim.\r\n    Alias es  EditSubstitute\r\n    Alias sps SplitSubstitute\r\n    Alias epl EditPlus\r\n    Alias emi EditMinus\r\n    Alias en  EditNext\r\n    Alias ep  EditPrevious\r\n    Alias er  EditRoot\r\n    Alias spr SplitRoot\r\n    Alias spp SplitPattern\r\n\r\nAll :Split..., :VSplit..., :SView, and :DiffSplit... commands obey the default\r\n'splitbelow' and 'splitright' settings. If you want different behavior, you\r\ncan insert the appropriate split modifier command via:\r\n    let g:EditSimilar_splitmode = 'rightbelow'\r\n    let g:EditSimilar_vsplitmode = 'rightbelow'\r\n    let g:EditSimilar_diffsplitmode = 'rightbelow'","5":"INSTALLATION\r\nThe code is hosted in a Git repo at\r\n    https:\/\/github.com\/inkarkat\/vim-EditSimilar\r\nYou can use your favorite plugin manager, or \"git clone\" into a directory used\r\nfor Vim packages. Releases are on the \"stable\" branch, the latest unstable\r\ndevelopment snapshot on \"master\".\r\n\r\nThis script is also packaged as a vimball. If you have the \"gunzip\"\r\ndecompressor in your PATH, simply edit the *.vmb.gz package in Vim; otherwise,\r\ndecompress the archive first, e.g. using WinZip. Inside Vim, install by\r\nsourcing the vimball or via the :UseVimball command.\r\n    vim EditSimilar*.vmb.gz\r\n    :so %\r\nTo uninstall, use the :RmVimball command.\r\n\r\nDEPENDENCIES\r\n- Requires Vim 7.0 or higher.\r\n- Requires the ingo-library.vim plugin (vimscript #4433), version 1.025 or\r\n  higher.\r\n- Optional, recommended: cmdalias plugin (vimscript #746)\r\n\r\nCONFIGURATION\r\nFor a permanent configuration, put the following commands into your vimrc:\r\n\r\nAll these edit commands are about speed; after all, they vie to be a faster\r\nalternative to the built-in commands that take a complete filename. Each\r\nuser's Vim setup and behavior is different. Therefore, the previously defined\r\nshort command forms :Esubst, :Enext, etc. are gone in version 1.20. Instead,\r\nyou are encouraged to define your own shortcuts, depending on your preferences\r\nand needs. A great way to do this (because it allows the definition of pure\r\nlowercase commands) is defining short aliases through the cmdalias plugin\r\n(vimscript #746), like this:\r\n    \" Shorten the most frequently used commands from EditSimilar.vim.\r\n    Alias es  EditSubstitute\r\n    Alias sps SplitSubstitute\r\n    Alias epl EditPlus\r\n    Alias emi EditMinus\r\n    Alias en  EditNext\r\n    Alias ep  EditPrevious\r\n    Alias er  EditRoot\r\n    Alias spr SplitRoot\r\n    Alias spp SplitPattern\r\n\r\nAll :Split..., :VSplit..., :SView, and :DiffSplit... commands obey the default\r\n'splitbelow' and 'splitright' settings. If you want different behavior, you\r\ncan insert the appropriate split modifier command via:\r\n    let g:EditSimilar_splitmode = 'rightbelow'\r\n    let g:EditSimilar_vsplitmode = 'rightbelow'\r\n    let g:EditSimilar_diffsplitmode = 'rightbelow'","first_name":"Ingo","6":"Ingo","last_name":"Karkat","7":"Karkat","releases":[{"0":"2544","vim_version":"7.0","1":"7.0","script_version":"2.50","2":"2.50","version_comment":"- ENH: Also support optional {text}=?{replacement} that if done don't count yet as a successful substitution; another {text2}={replacement2} must still happen.\r\n- FIX: :SaveOverBufferAs and :WriteOverBuffer don't handle files with spaces. Need to define them with -nargs=+ to keep Vim from unescaping the filespec. *** You need to update to ingo-library (vimscript #4433) version 1.025! ***","3":"- ENH: Also support optional {text}=?{replacement} that if done don't count yet as a successful substitution; another {text2}={replacement2} must still happen.\r\n- FIX: :SaveOverBufferAs and :WriteOverBuffer don't handle files with spaces. Need to define them with -nargs=+ to keep Vim from unescaping the filespec. *** You need to update to ingo-library (vimscript #4433) version 1.025! ***","package":"EditSimilar-2.50.vmb.gz","4":"EditSimilar-2.50.vmb.gz","src_id":"26228","5":"26228","creation_date":"1537762107","6":"1537762107"},{"0":"2544","vim_version":"7.0","1":"7.0","script_version":"2.41","2":"2.41","version_comment":"- BUG: :{range}WritePlus 999 doesn't actually work, because it executes as 999,999WriteOverBuffer.\r\n- Refactoring: Use ingo#fs#path#Exists(). *** You need to update to ingo-library (vimscript #4433) version 1.019! ***","3":"- BUG: :{range}WritePlus 999 doesn't actually work, because it executes as 999,999WriteOverBuffer.\r\n- Refactoring: Use ingo#fs#path#Exists(). *** You need to update to ingo-library (vimscript #4433) version 1.019! ***","package":"EditSimilar-2.41.vmb.gz","4":"EditSimilar-2.41.vmb.gz","src_id":"22067","5":"22067","creation_date":"1403252760","6":"1403252760"},{"0":"2544","vim_version":"7.0","1":"7.0","script_version":"2.40","2":"2.40","version_comment":"- Add :BDelete... comands, which are especially useful for when \"E139: File is loaded in another buffer\" is given.\r\n- Add :DiffSplit... comands.\r\n- For next files, escape the dirspec for wildcards to handle peculiar directories.\r\n- Allow to :write partial buffer contents by defining -range=% on :Write... commands that do not yet use the count.\r\n- Add :SaveOverBufferAs and :WriteOverBuffer commands (that with [!] also :bdelete an existing buffer with the same name) and use those in the :Save... and :Write... commands.\r\n- All commands now properly abort on error. *** You need to update to ingo-library (vimscript #4433) version 1.018! ***","3":"- Add :BDelete... comands, which are especially useful for when \"E139: File is loaded in another buffer\" is given.\r\n- Add :DiffSplit... comands.\r\n- For next files, escape the dirspec for wildcards to handle peculiar directories.\r\n- Allow to :write partial buffer contents by defining -range=% on :Write... commands that do not yet use the count.\r\n- Add :SaveOverBufferAs and :WriteOverBuffer commands (that with [!] also :bdelete an existing buffer with the same name) and use those in the :Save... and :Write... commands.\r\n- All commands now properly abort on error. *** You need to update to ingo-library (vimscript #4433) version 1.018! ***","package":"EditSimilar-2.40.vmb.gz","4":"EditSimilar-2.40.vmb.gz","src_id":"21783","5":"21783","creation_date":"1397651696","6":"1397651696"},{"0":"2544","vim_version":"7.0","1":"7.0","script_version":"2.32","2":"2.32","version_comment":"- Handle dot prefixes (e.g. \".txt\") in root completion.\r\n- Also offer multi-extension roots (e.g. \".orig.txt\") in root completion, and correctly handle existing roots (e.g. \".orig.t\").\r\n- Add workaround for editing via :pedit, which uses the CWD of existing preview window instead of the CWD of the current window; leading to wrong not-existing files being opened when :set autochdir. Work around this by always passing a full absolute filespec. *** You need to update to ingo-library (vimscript #4433) version 1.017! ***","3":"- Handle dot prefixes (e.g. \".txt\") in root completion.\r\n- Also offer multi-extension roots (e.g. \".orig.txt\") in root completion, and correctly handle existing roots (e.g. \".orig.t\").\r\n- Add workaround for editing via :pedit, which uses the CWD of existing preview window instead of the CWD of the current window; leading to wrong not-existing files being opened when :set autochdir. Work around this by always passing a full absolute filespec. *** You need to update to ingo-library (vimscript #4433) version 1.017! ***","package":"EditSimilar-2.32.vmb.gz","4":"EditSimilar-2.32.vmb.gz","src_id":"21610","5":"21610","creation_date":"1394704349","6":"1394704349"},{"0":"2544","vim_version":"7.0","1":"7.0","script_version":"2.31","2":"2.31","version_comment":"- Minor: Also handle :echoerr errors, which don't have an E... number prepended.\r\n- FIX: Non-any completion can yield duplicate roots, too (e.g. foobar.orig.txt + foobar.txt).\r\n- Add dependency to ingo-library (vimscript #4433). *** You need to separately install ingo-library (vimscript #4433) version 1.014 (or higher)! ***","3":"- Minor: Also handle :echoerr errors, which don't have an E... number prepended.\r\n- FIX: Non-any completion can yield duplicate roots, too (e.g. foobar.orig.txt + foobar.txt).\r\n- Add dependency to ingo-library (vimscript #4433). *** You need to separately install ingo-library (vimscript #4433) version 1.014 (or higher)! ***","package":"EditSimilar-2.31.vmb.gz","4":"EditSimilar-2.31.vmb.gz","src_id":"21061","5":"21061","creation_date":"1384856550","6":"1384856550"},{"0":"2544","vim_version":"7.0","1":"7.0","script_version":"2.30","2":"2.30","version_comment":"CHG: For :FilePlus, :WritePlus, :SavePlus, when a [count] but no [!] is given, try to create an offset one more than an existing file between the current and the passed offset. This lets you use a large [N] to write the file with the next number within [N] for which no file exists yet. Change inspired by\r\nhttp:\/\/stackoverflow.com\/questions\/13778322\/vimscript-code-to-create-a-new-numbered-file","3":"CHG: For :FilePlus, :WritePlus, :SavePlus, when a [count] but no [!] is given, try to create an offset one more than an existing file between the current and the passed offset. This lets you use a large [N] to write the file with the next number within [N] for which no file exists yet. Change inspired by\r\nhttp:\/\/stackoverflow.com\/questions\/13778322\/vimscript-code-to-create-a-new-numbered-file","package":"EditSimilar-2.30.vmb.gz","4":"EditSimilar-2.30.vmb.gz","src_id":"19152","5":"19152","creation_date":"1355052316","6":"1355052316"},{"0":"2544","vim_version":"7.0","1":"7.0","script_version":"2.20","2":"2.20","version_comment":"- Allow passing of multiple {file-pattern} to :SplitPattern et al. and enable file completion for them.\r\n- Handle optional ++opt +cmd file options and commands in :SplitPattern et al.","3":"- Allow passing of multiple {file-pattern} to :SplitPattern et al. and enable file completion for them.\r\n- Handle optional ++opt +cmd file options and commands in :SplitPattern et al.","package":"EditSimilar-2.20.vmb.gz","4":"EditSimilar-2.20.vmb.gz","src_id":"18505","5":"18505","creation_date":"1346154230","6":"1346154230"},{"0":"2544","vim_version":"7.0","1":"7.0","script_version":"2.10","2":"2.10","version_comment":"ENH: Complete file extensions for any files found in the file's directory for those commands that most of the time are used to create new files; the default search for the current filename's extensions won't yield anything there.","3":"ENH: Complete file extensions for any files found in the file's directory for those commands that most of the time are used to create new files; the default search for the current filename's extensions won't yield anything there.","package":"EditSimilar.vba.gz","4":"EditSimilar.vba.gz","src_id":"18315","5":"18315","creation_date":"1343303774","6":"1343303774"},{"0":"2544","vim_version":"7.0","1":"7.0","script_version":"2.01","2":"2.01","version_comment":"FIX: To avoid issues with differing forward slash \/ backslash path separator components, canonicalize the glob pattern and filespec. This avoids a \"Cannot locate current file\" error when there is a mismatch.","3":"FIX: To avoid issues with differing forward slash \/ backslash path separator components, canonicalize the glob pattern and filespec. This avoids a \"Cannot locate current file\" error when there is a mismatch.","package":"EditSimilar.vba.gz","4":"EditSimilar.vba.gz","src_id":"18131","5":"18131","creation_date":"1339765856","6":"1339765856"},{"0":"2544","vim_version":"7.0","1":"7.0","script_version":"2.00","2":"2.00","version_comment":"- Rename the :EditNext \/ :EditPrevious commands to :EditPlus \/ :EditMinus and redefine them to operate on directory contents instead of numerical offsets. *** PLEASE USE THE NEW RENAMED COMMANDS AND UPDATE ANY USAGES IN SCRIPTS AND MAPPINGS ***\r\n- Better modularization of the different similarities.\r\n- BUG: Substituted filenames that only exist in an unpersisted Vim buffer cause a \"file does not exist\" error when a:isCreateNew isn't set. Also check Vim buffers for a match.","3":"- Rename the :EditNext \/ :EditPrevious commands to :EditPlus \/ :EditMinus and redefine them to operate on directory contents instead of numerical offsets. *** PLEASE USE THE NEW RENAMED COMMANDS AND UPDATE ANY USAGES IN SCRIPTS AND MAPPINGS ***\r\n- Better modularization of the different similarities.\r\n- BUG: Substituted filenames that only exist in an unpersisted Vim buffer cause a \"file does not exist\" error when a:isCreateNew isn't set. Also check Vim buffers for a match.","package":"EditSimilar.vba.gz","4":"EditSimilar.vba.gz","src_id":"18114","5":"18114","creation_date":"1339418330","6":"1339418330"},{"0":"2544","vim_version":"7.0","1":"7.0","script_version":"1.22","2":"1.22","version_comment":"- ENH: Allow [v]split mode different than determined by 'splitbelow' \/ 'splitright' via configuration. \r\n- Refactoring: Move file extension completion to EditSimilar#Root#Complete() and create the root commands also in the command builder. \r\n- ENH: Omit current buffer's file extension from the completion for EditSimilar-root commands. \r\n- Obsolete the short command forms :Esubst, :Enext, :Eprev; the starting uppercase letter makes them still awkward to type, there's more likely a conflict with other custom commands (e.g. :En -> :Encode, :Enext), and I now believe aliasing via cmdalias.vim is the better way to provide personal shortcuts, instead of polluting the command namespace with all these duplicates. \r\n- Rename :Vsplit... -> :VSplit... and :Sview... -> :SView... as I think this is a more intuitive long form. (And now that the user is encouraged to create his own custom short aliases, anyway.) The only other plugin with similar commands that I know is bufexplorer with its :VSBufExplorer. ","3":"- ENH: Allow [v]split mode different than determined by 'splitbelow' \/ 'splitright' via configuration. \r\n- Refactoring: Move file extension completion to EditSimilar#Root#Complete() and create the root commands also in the command builder. \r\n- ENH: Omit current buffer's file extension from the completion for EditSimilar-root commands. \r\n- Obsolete the short command forms :Esubst, :Enext, :Eprev; the starting uppercase letter makes them still awkward to type, there's more likely a conflict with other custom commands (e.g. :En -> :Encode, :Enext), and I now believe aliasing via cmdalias.vim is the better way to provide personal shortcuts, instead of polluting the command namespace with all these duplicates. \r\n- Rename :Vsplit... -> :VSplit... and :Sview... -> :SView... as I think this is a more intuitive long form. (And now that the user is encouraged to create his own custom short aliases, anyway.) The only other plugin with similar commands that I know is bufexplorer with its :VSBufExplorer. ","package":"EditSimilar.vba.gz","4":"EditSimilar.vba.gz","src_id":"17422","5":"17422","creation_date":"1328884783","6":"1328884783"},{"0":"2544","vim_version":"7.0","1":"7.0","script_version":"1.19","2":"1.19","version_comment":"Avoid that :SplitPattern usually opens splits in reverse glob order (with default 'nosplitbelow' \/ 'nosplitright') by forcing :belowright splitting for all splits after the first. I.e. behave more like vim -o {pattern}. ","3":"Avoid that :SplitPattern usually opens splits in reverse glob order (with default 'nosplitbelow' \/ 'nosplitright') by forcing :belowright splitting for all splits after the first. I.e. behave more like vim -o {pattern}. ","package":"EditSimilar.vba.gz","4":"EditSimilar.vba.gz","src_id":"16136","5":"16136","creation_date":"1311605716","6":"1311605716"},{"0":"2544","vim_version":"7.0","1":"7.0","script_version":"1.18","2":"1.18","version_comment":"ENH: Implement completion of file extensions for EditSimilar-root commands like :EditRoot. ","3":"ENH: Implement completion of file extensions for EditSimilar-root commands like :EditRoot. ","package":"EditSimilar.vba.gz","4":"EditSimilar.vba.gz","src_id":"15963","5":"15963","creation_date":"1308853356","6":"1308853356"},{"0":"2544","vim_version":"7.0","1":"7.0","script_version":"1.17","2":"1.17","version_comment":"BUG: :999EditPrevious on 'file00' caused E121: Undefined variable: l:replacement. ","3":"BUG: :999EditPrevious on 'file00' caused E121: Undefined variable: l:replacement. ","package":"EditSimilar.vba.gz","4":"EditSimilar.vba.gz","src_id":"12494","5":"12494","creation_date":"1267108178","6":"1267108178"},{"0":"2544","vim_version":"7.0","1":"7.0","script_version":"1.16","2":"1.16","version_comment":"BUG: Next \/ previous commands interpreted files such as 'C406' as hexadecimal. Thanks to Andy Wokula for sending a patch. ","3":"BUG: Next \/ previous commands interpreted files such as 'C406' as hexadecimal. Thanks to Andy Wokula for sending a patch. ","package":"EditSimilar.vba.gz","4":"EditSimilar.vba.gz","src_id":"11708","5":"11708","creation_date":"1257951584","6":"1257951584"},{"0":"2544","vim_version":"7.0","1":"7.0","script_version":"1.15","2":"1.15","version_comment":"Offset commands (:EditNext et al.) now check that the digit pattern does not\r\naccidentally match inside a hexadecimal number (which are unsupported). ","3":"Offset commands (:EditNext et al.) now check that the digit pattern does not\r\naccidentally match inside a hexadecimal number (which are unsupported). ","package":"EditSimilar.vba.gz","4":"EditSimilar.vba.gz","src_id":"11350","5":"11350","creation_date":"1252503265","6":"1252503265"},{"0":"2544","vim_version":"7.0","1":"7.0","script_version":"1.14","2":"1.14","version_comment":"- BF: :[N]EditPrevious with supplied [N] would skip over existing smaller number file and would claim that no substituted file existed. \r\n- BF: :[N]EditPrevious with supplied large [N] together with a low original number hogs the CPU because the loop iterates over the entire number range where the resulting offset would be negative.","3":"- BF: :[N]EditPrevious with supplied [N] would skip over existing smaller number file and would claim that no substituted file existed. \r\n- BF: :[N]EditPrevious with supplied large [N] together with a low original number hogs the CPU because the loop iterates over the entire number range where the resulting offset would be negative.","package":"EditSimilar.vba.gz","4":"EditSimilar.vba.gz","src_id":"11229","5":"11229","creation_date":"1250861965","6":"1250861965"},{"0":"2544","vim_version":"7.0","1":"7.0","script_version":"1.13","2":"1.13","version_comment":"ENH: :EditNext \/ :EditPrevious without the optional [count] now skip over gaps\r\nin numbering. ","3":"ENH: :EditNext \/ :EditPrevious without the optional [count] now skip over gaps\r\nin numbering. ","package":"EditSimilar.vba.gz","4":"EditSimilar.vba.gz","src_id":"10913","5":"10913","creation_date":"1246364785","6":"1246364785"},{"0":"2544","vim_version":"7.0","1":"7.0","script_version":"1.12","2":"1.12","version_comment":"- ENH: {text} in :EditSubstitute can now also contain file wildcards (?, *, **\r\n  and [...]) to save typing. \r\n- ENH: On Windows, {text} in :EditSubstitute can now also use forward slashes\r\n  as path separators (as an alternative to the usual backslashes). \r\n- ENH: Supporting substitutions spanning both pathspec and filename by finally\r\n  applying failed replacements of multi-path elements to the entire filespec. \r\n- Added \":ViewSimilar\" and \":SviewSimilar\" commands to open similar files in\r\n  read-only mode. ","3":"- ENH: {text} in :EditSubstitute can now also contain file wildcards (?, *, **\r\n  and [...]) to save typing. \r\n- ENH: On Windows, {text} in :EditSubstitute can now also use forward slashes\r\n  as path separators (as an alternative to the usual backslashes). \r\n- ENH: Supporting substitutions spanning both pathspec and filename by finally\r\n  applying failed replacements of multi-path elements to the entire filespec. \r\n- Added \":ViewSimilar\" and \":SviewSimilar\" commands to open similar files in\r\n  read-only mode. ","package":"EditSimilar.vba.gz","4":"EditSimilar.vba.gz","src_id":"10589","5":"10589","creation_date":"1242246336","6":"1242246336"},{"0":"2544","vim_version":"7.0","1":"7.0","script_version":"1.10","2":"1.10","version_comment":"ENH: {replacement} in :EditSubstitute and {extension} in :EditRoot can now\r\ncontain file wildcards to save typing. ","3":"ENH: {replacement} in :EditSubstitute and {extension} in :EditRoot can now\r\ncontain file wildcards to save typing. ","package":"EditSimilar.vba.gz","4":"EditSimilar.vba.gz","src_id":"10018","5":"10018","creation_date":"1235466918","6":"1235466918"},{"0":"2544","vim_version":"7.0","1":"7.0","script_version":"1.00","2":"1.00","version_comment":"Initial upload","3":"Initial upload","package":"EditSimilar.vba.gz","4":"EditSimilar.vba.gz","src_id":"9992","5":"9992","creation_date":"1234955841","6":"1234955841"}]},"2543":{"script_id":"2543","0":"2543","script_name":"SearchCols.vim","1":"SearchCols.vim","script_type":"utility","2":"utility","summary":"Search within fixed width data column-by-column, rather than row-by-row","3":"Search within fixed width data column-by-column, rather than row-by-row","description":"This script was inspired by a question on StackOverflow.com.  It's my first vim script, and is likely very bad, however I've made my best efforts to have it play nicely.\r\n\r\nCreates a command :SearchCols <string>, which can be used to search for the string in fixed-width columns so that the search looks in the first column first, then the second column, etc. rather than the row-by-row search which is standard for vim.  Repeat the command via @: and then @@ since it's a colon-command.\r\n\r\nRequirements:\r\n - This script requires the multvals.vim plugin: http:\/\/www.vim.org\/scripts\/script.php?script_id=171\r\n\r\nAssumptions:\r\n - Assumes that your file is formatted with whitespace-delimited fixed width columns, i.e. there are no spaces inside the data items, only in between them.\r\n - Assumes that the first line of your file is formatted so that the column widths can be deduced from it.","4":"This script was inspired by a question on StackOverflow.com.  It's my first vim script, and is likely very bad, however I've made my best efforts to have it play nicely.\r\n\r\nCreates a command :SearchCols <string>, which can be used to search for the string in fixed-width columns so that the search looks in the first column first, then the second column, etc. rather than the row-by-row search which is standard for vim.  Repeat the command via @: and then @@ since it's a colon-command.\r\n\r\nRequirements:\r\n - This script requires the multvals.vim plugin: http:\/\/www.vim.org\/scripts\/script.php?script_id=171\r\n\r\nAssumptions:\r\n - Assumes that your file is formatted with whitespace-delimited fixed width columns, i.e. there are no spaces inside the data items, only in between them.\r\n - Assumes that the first line of your file is formatted so that the column widths can be deduced from it.","install_details":"Place the script in your .vim\/plugin\/ directory","5":"Place the script in your .vim\/plugin\/ directory","first_name":"Adam","6":"Adam","last_name":"Bellaire","7":"Bellaire","releases":[{"0":"2543","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"SearchCols.vim","4":"SearchCols.vim","src_id":"9979","5":"9979","creation_date":"1234791688","6":"1234791688"}]},"2542":{"script_id":"2542","0":"2542","script_name":"StarRange","1":"StarRange","script_type":"utility","2":"utility","summary":"Searches a string that you selected in visual mode with * or #.","3":"Searches a string that you selected in visual mode with * or #.","description":"This plugin also runs on Vim 6.4.\r\n\r\nUsage:\r\n  [Settings]\r\n\r\n  Change mappings (source code).\r\n\r\n  [Usual]\r\n\r\n  Select a string in visual mode. Press * or # key.\r\n\r\nRepository:\r\n  https:\/\/bitbucket.org\/shu\/starrange\/","4":"This plugin also runs on Vim 6.4.\r\n\r\nUsage:\r\n  [Settings]\r\n\r\n  Change mappings (source code).\r\n\r\n  [Usual]\r\n\r\n  Select a string in visual mode. Press * or # key.\r\n\r\nRepository:\r\n  https:\/\/bitbucket.org\/shu\/starrange\/","install_details":"Just source this file. (Put this file into the plugin directory.)\r\n","5":"Just source this file. (Put this file into the plugin directory.)\r\n","first_name":"Shuhei","6":"Shuhei","last_name":"Kubota","7":"Kubota","releases":[{"0":"2542","vim_version":"7.0","1":"7.0","script_version":"1.2","2":"1.2","version_comment":"* now it works only in visual-mode. (not works in select-mode)","3":"* now it works only in visual-mode. (not works in select-mode)","package":"starrange.vim","4":"starrange.vim","src_id":"17189","5":"17189","creation_date":"1326367221","6":"1326367221"},{"0":"2542","vim_version":"7.0","1":"7.0","script_version":"1.1","2":"1.1","version_comment":"Bug fix (treatment of the '\/' char) and newline supports.","3":"Bug fix (treatment of the '\/' char) and newline supports.","package":"starrange.vim","4":"starrange.vim","src_id":"10936","5":"10936","creation_date":"1246634128","6":"1246634128"},{"0":"2542","vim_version":"7.2","1":"7.2","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"starrange.vim","4":"starrange.vim","src_id":"9955","5":"9955","creation_date":"1234431139","6":"1234431139"}]},"2541":{"script_id":"2541","0":"2541","script_name":"Mastermind board game","1":"Mastermind board game","script_type":"game","2":"game","summary":"The board game ","3":"The board game ","description":"Mastermind, if you are not familiar, is a game of guesses. You have to guess a N-digit (N selectable from 1-9, 5 being the default) code based on clues. After you have entered a line, the clue is shown with characters 'X' and 'x'. X means the number (or color) and position is right. x means number is right but position is incorrect.\r\n\r\nPlease note that, the position of X\/x in the clue area has no correspondence with the actual numbers. In other words a X in the clue box means one of the numbers you have guessed is right and in the correct position. It does not tell you which one; that is where the fun is!\r\n\r\nHere is some more info about the game.\r\nhttp:\/\/en.wikipedia.org\/wiki\/Mastermind_(board_game)","4":"Mastermind, if you are not familiar, is a game of guesses. You have to guess a N-digit (N selectable from 1-9, 5 being the default) code based on clues. After you have entered a line, the clue is shown with characters 'X' and 'x'. X means the number (or color) and position is right. x means number is right but position is incorrect.\r\n\r\nPlease note that, the position of X\/x in the clue area has no correspondence with the actual numbers. In other words a X in the clue box means one of the numbers you have guessed is right and in the correct position. It does not tell you which one; that is where the fun is!\r\n\r\nHere is some more info about the game.\r\nhttp:\/\/en.wikipedia.org\/wiki\/Mastermind_(board_game)","install_details":"drop the file under the plugin directory (unix, it is $HOME\/.vim\/plugin)\r\n\r\nHit \\mm to start the game (<mapleader>mm)\r\n\r\nPress q to stop.\r\n\r\nHere are the key mappings:\r\n\r\n\"     <keys 1-9> : Enters respective key\r\n\"        <enter> : Press this, when done with the current line\r\n\"        <space> : Skip to enter next number\r\n\"    <backspace> : Skip to enter previous number\r\n\"          <c-r> : Restart the game\r\n\"          <c-n> : Change the number of digits to guess (1-9)\r\n\"          <c-g> : Change the number of guesses (1-20)\r\n\"              q : To quit the game\r\n\"              b : Boss Key (switches b\/w first buffer and game)\r\n","5":"drop the file under the plugin directory (unix, it is $HOME\/.vim\/plugin)\r\n\r\nHit \\mm to start the game (<mapleader>mm)\r\n\r\nPress q to stop.\r\n\r\nHere are the key mappings:\r\n\r\n\"     <keys 1-9> : Enters respective key\r\n\"        <enter> : Press this, when done with the current line\r\n\"        <space> : Skip to enter next number\r\n\"    <backspace> : Skip to enter previous number\r\n\"          <c-r> : Restart the game\r\n\"          <c-n> : Change the number of digits to guess (1-9)\r\n\"          <c-g> : Change the number of guesses (1-20)\r\n\"              q : To quit the game\r\n\"              b : Boss Key (switches b\/w first buffer and game)\r\n","first_name":"Arun","6":"Arun","last_name":"E","7":"E","releases":[{"0":"2541","vim_version":"7.0","1":"7.0","script_version":"1.00","2":"1.00","version_comment":"Initial upload","3":"Initial upload","package":"mastermind.vim","4":"mastermind.vim","src_id":"9953","5":"9953","creation_date":"1234410050","6":"1234410050"}]},"2540":{"script_id":"2540","0":"2540","script_name":"snipMate","1":"snipMate","script_type":"utility","2":"utility","summary":"TextMate-style snippets for Vim","3":"TextMate-style snippets for Vim","description":"snipMate.vim aims to be an unobtrusive, concise vim script that implements some of TextMate's snippets features in Vim. A snippet is a piece of often-typed text that you can insert into your document using a trigger word followed by a <tab>.\r\n\r\nFor instance, in a C file using the default installation of snipMate.vim, if you type \"for<tab>\" in insert mode, it will expand a typical for loop in C:\r\n\r\n for (i = 0; i < count; i++) {\r\n\r\n }\r\n\r\nTo go to the next item in the loop, simply <tab> over to it; if there is repeated code, such as the \"i\" variable in this example, you can simply start typing once it's highlighted and all the matches specified in the snippet will be updated.\r\n\r\nRequires Vim 7 or higher.\r\nFor a quick introduction, see this screencast: http:\/\/vimeo.com\/3535418\r\nFor more help see the documentation that comes with snipMate in ~\/.vim\/doc\/snipMate.txt.\r\n\r\nsnipMate.vim has the following features among others:\r\n  - The syntax of snippets is very similar to TextMate's, allowing easy conversion.\r\n  - The position of the snippet is kept transparently (i.e., it does not use marks\/placeholders inserted into the buffer), allowing you to escape out of an incomplete snippet, something particularly useful in Vim.\r\n  - Variables in snippets are updated as-you-type.\r\n  - Snippets can have multiple matches.\r\n  - Snippets can be out of order. For instance, in a do...while loop, the condition can be added before the code.\r\n\r\nThe latest version of snipMate is available here: https:\/\/github.com\/garbas\/vim-snipmate\r\n\r\nEnjoy!","4":"snipMate.vim aims to be an unobtrusive, concise vim script that implements some of TextMate's snippets features in Vim. A snippet is a piece of often-typed text that you can insert into your document using a trigger word followed by a <tab>.\r\n\r\nFor instance, in a C file using the default installation of snipMate.vim, if you type \"for<tab>\" in insert mode, it will expand a typical for loop in C:\r\n\r\n for (i = 0; i < count; i++) {\r\n\r\n }\r\n\r\nTo go to the next item in the loop, simply <tab> over to it; if there is repeated code, such as the \"i\" variable in this example, you can simply start typing once it's highlighted and all the matches specified in the snippet will be updated.\r\n\r\nRequires Vim 7 or higher.\r\nFor a quick introduction, see this screencast: http:\/\/vimeo.com\/3535418\r\nFor more help see the documentation that comes with snipMate in ~\/.vim\/doc\/snipMate.txt.\r\n\r\nsnipMate.vim has the following features among others:\r\n  - The syntax of snippets is very similar to TextMate's, allowing easy conversion.\r\n  - The position of the snippet is kept transparently (i.e., it does not use marks\/placeholders inserted into the buffer), allowing you to escape out of an incomplete snippet, something particularly useful in Vim.\r\n  - Variables in snippets are updated as-you-type.\r\n  - Snippets can have multiple matches.\r\n  - Snippets can be out of order. For instance, in a do...while loop, the condition can be added before the code.\r\n\r\nThe latest version of snipMate is available here: https:\/\/github.com\/garbas\/vim-snipmate\r\n\r\nEnjoy!","install_details":"See https:\/\/github.com\/garbas\/vim-snipmate#installing-snipmate to install the latest version.\r\n\r\nNOTE: remember to add \":filetype plugin on\" to your .vimrc, otherwise snippets will not work! This is one of the most common issue new users face when trying snipMate.\r\n\r\nRemember to run \":helptags ~\/.vim\/doc\" to enable the help.","5":"See https:\/\/github.com\/garbas\/vim-snipmate#installing-snipmate to install the latest version.\r\n\r\nNOTE: remember to add \":filetype plugin on\" to your .vimrc, otherwise snippets will not work! This is one of the most common issue new users face when trying snipMate.\r\n\r\nRemember to run \":helptags ~\/.vim\/doc\" to enable the help.","first_name":"Michael","6":"Michael","last_name":"Sanders","7":"Sanders","releases":[{"0":"2540","vim_version":"7.0","1":"7.0","script_version":"0.83","2":"0.83","version_comment":"Fixed bug when leaving snippet for another buffer, having a variable at the end of a line in a snippet, or typing certain characters in select mode, and (finally) added support for <shift-tab> to go back a tab stop. Also added snippets for zsh (thanks israelchauca) and mako (thanks \"iElectric\"), and updated C, Obj-C, and C++ snippets.","3":"Fixed bug when leaving snippet for another buffer, having a variable at the end of a line in a snippet, or typing certain characters in select mode, and (finally) added support for <shift-tab> to go back a tab stop. Also added snippets for zsh (thanks israelchauca) and mako (thanks \"iElectric\"), and updated C, Obj-C, and C++ snippets.","package":"snipMate.zip","4":"snipMate.zip","src_id":"11006","5":"11006","creation_date":"1247500879","6":"1247500879"},{"0":"2540","vim_version":"7.0","1":"7.0","script_version":"0.82","2":"0.82","version_comment":"Fixed a bug with <c-r><tab>, placeholders, or having more than 9 tab stops on the same line, and added a Python snippet for the lambda (thanks voyeg3r), as well as snippets for the Tcl (thanks israelchauca) and AutoIt (thanks Angel Ezquerra Moreu) filetypes.","3":"Fixed a bug with <c-r><tab>, placeholders, or having more than 9 tab stops on the same line, and added a Python snippet for the lambda (thanks voyeg3r), as well as snippets for the Tcl (thanks israelchauca) and AutoIt (thanks Angel Ezquerra Moreu) filetypes.","package":"snipMate.zip","4":"snipMate.zip","src_id":"10801","5":"10801","creation_date":"1244685539","6":"1244685539"},{"0":"2540","vim_version":"7.0","1":"7.0","script_version":"0.81","2":"0.81","version_comment":"Added syntax highlighting to show errors in snippet files, fixed typos in certain snippets, fixed a bug with \"&\" in placeholders, fixed a bug when canceling multi-snippets, and fixed a bug when inserting a new line in a snippet.","3":"Added syntax highlighting to show errors in snippet files, fixed typos in certain snippets, fixed a bug with \"&\" in placeholders, fixed a bug when canceling multi-snippets, and fixed a bug when inserting a new line in a snippet.","package":"snipMate.zip","4":"snipMate.zip","src_id":"10608","5":"10608","creation_date":"1242443581","6":"1242443581"},{"0":"2540","vim_version":"7.0","1":"7.0","script_version":"0.8","2":"0.8","version_comment":"Added & fixed some snippets, and added a menu that displays all snippets for the current buffer when <c-r><tab> is typed in insert mode. \r\n\r\nI've removed convertSnip.py from this release since most snippets should be converted by now; if you still need it, just grab it from an earlier release.","3":"Added & fixed some snippets, and added a menu that displays all snippets for the current buffer when <c-r><tab> is typed in insert mode. \r\n\r\nI've removed convertSnip.py from this release since most snippets should be converted by now; if you still need it, just grab it from an earlier release.","package":"snipMate.zip","4":"snipMate.zip","src_id":"10516","5":"10516","creation_date":"1241377923","6":"1241377923"},{"0":"2540","vim_version":"7.0","1":"7.0","script_version":"0.79","2":"0.79","version_comment":"Added support for more than 9 tab stops, fixed typos in certain snippets, and cleaned up the code a bit.","3":"Added support for more than 9 tab stops, fixed typos in certain snippets, and cleaned up the code a bit.","package":"snipMate.zip","4":"snipMate.zip","src_id":"10393","5":"10393","creation_date":"1239670528","6":"1239670528"},{"0":"2540","vim_version":"7.0","1":"7.0","script_version":"0.78","2":"0.78","version_comment":"Fixed bug with aliased filetypes (e.g. loading C snippets for Obj-C files), updating placeholders on separate lines, and extracting snippets on Windows. Also added a few more Python, C, and Obj-C snippets, and fixed some typos in the Latex and C++ snippets.","3":"Fixed bug with aliased filetypes (e.g. loading C snippets for Obj-C files), updating placeholders on separate lines, and extracting snippets on Windows. Also added a few more Python, C, and Obj-C snippets, and fixed some typos in the Latex and C++ snippets.","package":"snipMate.zip","4":"snipMate.zip","src_id":"10357","5":"10357","creation_date":"1239061202","6":"1239061202"},{"0":"2540","vim_version":"7.0","1":"7.0","script_version":"0.77","2":"0.77","version_comment":"Fixed bug with single quotes (') in snippet triggers, and hyphenated global snippets (e.g., _-mysnips.snippets).","3":"Fixed bug with single quotes (') in snippet triggers, and hyphenated global snippets (e.g., _-mysnips.snippets).","package":"snipMate.zip","4":"snipMate.zip","src_id":"10317","5":"10317","creation_date":"1238379216","6":"1238379216"},{"0":"2540","vim_version":"7.0","1":"7.0","script_version":"0.76","2":"0.76","version_comment":"Fixed bug with extracting snippet files on Windows, folding, and a minor bug with supertab.","3":"Fixed bug with extracting snippet files on Windows, folding, and a minor bug with supertab.","package":"snipMate.zip","4":"snipMate.zip","src_id":"10316","5":"10316","creation_date":"1238357673","6":"1238357673"},{"0":"2540","vim_version":"7.0","1":"7.0","script_version":"0.75","2":"0.75","version_comment":"Added fix for hyphenated *.snippets files.","3":"Added fix for hyphenated *.snippets files.","package":"snipMate.zip","4":"snipMate.zip","src_id":"10307","5":"10307","creation_date":"1238176499","6":"1238176499"},{"0":"2540","vim_version":"7.0","1":"7.0","script_version":"0.74","2":"0.74","version_comment":"This release completely eliminates command-based snippets in favor of a new, easier to read & maintain syntax. A python script, convertSnip.py, has been included in this release to make it easier to migrate. For more information, see :h snippet-syntax; it's not very complicated, so it shouldn't take too much time to understand. \r\n\r\nThis release also fixes a number of bugs, including: support for supertab, special characters in snippet variables, the popup-menu, and adds support for hyphened snippet folders (e.g. snippets\/c-snippets\/ for C).","3":"This release completely eliminates command-based snippets in favor of a new, easier to read & maintain syntax. A python script, convertSnip.py, has been included in this release to make it easier to migrate. For more information, see :h snippet-syntax; it's not very complicated, so it shouldn't take too much time to understand. \r\n\r\nThis release also fixes a number of bugs, including: support for supertab, special characters in snippet variables, the popup-menu, and adds support for hyphened snippet folders (e.g. snippets\/c-snippets\/ for C).","package":"snipMate.zip","4":"snipMate.zip","src_id":"10293","5":"10293","creation_date":"1238098096","6":"1238098096"},{"0":"2540","vim_version":"7.0","1":"7.0","script_version":"0.73","2":"0.73","version_comment":"Fixed bug with redefinition of C++ snippets, fixed a bug when using the completion menu, added support for the 'shellslash' option (thanks Derek Wyatt), and added support for buffer-local snippets (thanks Meikel Brandmeyer).","3":"Fixed bug with redefinition of C++ snippets, fixed a bug when using the completion menu, added support for the 'shellslash' option (thanks Derek Wyatt), and added support for buffer-local snippets (thanks Meikel Brandmeyer).","package":"snipMate.zip","4":"snipMate.zip","src_id":"10214","5":"10214","creation_date":"1237158510","6":"1237158510"},{"0":"2540","vim_version":"7.0","1":"7.0","script_version":"0.72","2":"0.72","version_comment":"Fixed a bug with variables inside placeholders (e.g. \"${1:foo} ${2:$1bar}\").","3":"Fixed a bug with variables inside placeholders (e.g. \"${1:foo} ${2:$1bar}\").","package":"snipMate.zip","4":"snipMate.zip","src_id":"10161","5":"10161","creation_date":"1236698256","6":"1236698256"},{"0":"2540","vim_version":"7.0","1":"7.0","script_version":"0.71","2":"0.71","version_comment":"First and foremost, the code has been significantly re-factored; it is a bit longer now, but hopefully at the sake of being much easier to read and maintain.\r\n\r\nThis release also adds: support for file-based snippets, support for delimiters before snippet triggers (e.g., \"bar.foo\" could expand \"foo\"), and bug fixes.","3":"First and foremost, the code has been significantly re-factored; it is a bit longer now, but hopefully at the sake of being much easier to read and maintain.\r\n\r\nThis release also adds: support for file-based snippets, support for delimiters before snippet triggers (e.g., \"bar.foo\" could expand \"foo\"), and bug fixes.","package":"snipMate.zip","4":"snipMate.zip","src_id":"10143","5":"10143","creation_date":"1236564543","6":"1236564543"},{"0":"2540","vim_version":"7.0","1":"7.0","script_version":"0.6956","2":"0.6956","version_comment":"Forgot a backslash in the supertab.vim fix.","3":"Forgot a backslash in the supertab.vim fix.","package":"snipMate.zip","4":"snipMate.zip","src_id":"10028","5":"10028","creation_date":"1235524849","6":"1235524849"},{"0":"2540","vim_version":"7.0","1":"7.0","script_version":"0.6955","2":"0.6955","version_comment":"Actually fixed the supertab bug (thanks Asher VanBrunt); also added some more Objective-C snippets, and fixed another bug with expanding snippets before text introduced in the previous version.","3":"Actually fixed the supertab bug (thanks Asher VanBrunt); also added some more Objective-C snippets, and fixed another bug with expanding snippets before text introduced in the previous version.","package":"snipMate.zip","4":"snipMate.zip","src_id":"10026","5":"10026","creation_date":"1235518746","6":"1235518746"},{"0":"2540","vim_version":"7.0","1":"7.0","script_version":"0.6954","2":"0.6954","version_comment":"Fixed a bug when expanding snippets with text after them, and a bug with expanding evals (`...`) that prevented substitutions containing \"\\=\" such as substitute('foo', '.*', '\\=toupper(submatch(0))') from working.\r\n\r\nAlso fixed another typo in the Python snippets, and supertab compatibility.","3":"Fixed a bug when expanding snippets with text after them, and a bug with expanding evals (`...`) that prevented substitutions containing \"\\=\" such as substitute('foo', '.*', '\\=toupper(submatch(0))') from working.\r\n\r\nAlso fixed another typo in the Python snippets, and supertab compatibility.","package":"snipMate.zip","4":"snipMate.zip","src_id":"10021","5":"10021","creation_date":"1235496656","6":"1235496656"},{"0":"2540","vim_version":"7.0","1":"7.0","script_version":"0.6942","2":"0.6942","version_comment":"Fixed some typos in LaTeX and Python snippets, and added a snippet for the HTML 5 doctype. \r\n\r\nAlso added support for cycling through completions using supertab, and using completions to expand placeholder text.\r\n\r\nThe indentation amount for 'expandtab' also now defaults to 'sw' if 'sts' is not set.","3":"Fixed some typos in LaTeX and Python snippets, and added a snippet for the HTML 5 doctype. \r\n\r\nAlso added support for cycling through completions using supertab, and using completions to expand placeholder text.\r\n\r\nThe indentation amount for 'expandtab' also now defaults to 'sw' if 'sts' is not set.","package":"snipMate.zip","4":"snipMate.zip","src_id":"10003","5":"10003","creation_date":"1235243462","6":"1235243462"},{"0":"2540","vim_version":"7.0","1":"7.0","script_version":"0.61803399","2":"0.61803399","version_comment":"I apparently forgot to update the \"Snip!\" commands to \"Snipp!\" in the last version; this update takes care of that (thanks Martin Krauskopf for the bug report). The regex command to update these should actually be \":%s\/exe \\(.\\)Snip\\( \\|!\\)\/exe \\1Snipp\\2\".\r\n\r\nThis update also fixes a typo in the \"def\" ruby snippet (thanks Reza Jelveh & Jan Andersson).","3":"I apparently forgot to update the \"Snip!\" commands to \"Snipp!\" in the last version; this update takes care of that (thanks Martin Krauskopf for the bug report). The regex command to update these should actually be \":%s\/exe \\(.\\)Snip\\( \\|!\\)\/exe \\1Snipp\\2\".\r\n\r\nThis update also fixes a typo in the \"def\" ruby snippet (thanks Reza Jelveh & Jan Andersson).","package":"snipMate.zip","4":"snipMate.zip","src_id":"9981","5":"9981","creation_date":"1234799296","6":"1234799296"},{"0":"2540","vim_version":"7.0","1":"7.0","script_version":"0.6180339","2":"0.6180339","version_comment":"Added support for 'virtualedit=all' and 'virtualedit=onemore'. Thanks Mikhail Daen for the bug report.","3":"Added support for 'virtualedit=all' and 'virtualedit=onemore'. Thanks Mikhail Daen for the bug report.","package":"snipMate.zip","4":"snipMate.zip","src_id":"9975","5":"9975","creation_date":"1234731283","6":"1234731283"},{"0":"2540","vim_version":"7.0","1":"7.0","script_version":"0.618033","2":"0.618033","version_comment":"Fixed another bug concerning loading a filetype more than once.","3":"Fixed another bug concerning loading a filetype more than once.","package":"snipMate.zip","4":"snipMate.zip","src_id":"9968","5":"9968","creation_date":"1234580834","6":"1234580834"},{"0":"2540","vim_version":"7.0","1":"7.0","script_version":"0.61803","2":"0.61803","version_comment":"Fixed some other bugs for compatibility with supertab.vim and 'set expandtab' and added check to ensure snippets are not loaded twice.\r\n\r\nI also changed the \"Snip\" command to \"Snipp\" to maintain compatibility with vimscript #244 (imaps.vim). Unfortunately this breaks backward compatibility; to update any snippets you have added, just execute this regex on the appropriate files: \":%s\/exe \\(.\\)Snip \/exe \\1Snipp \/g\"","3":"Fixed some other bugs for compatibility with supertab.vim and 'set expandtab' and added check to ensure snippets are not loaded twice.\r\n\r\nI also changed the \"Snip\" command to \"Snipp\" to maintain compatibility with vimscript #244 (imaps.vim). Unfortunately this breaks backward compatibility; to update any snippets you have added, just execute this regex on the appropriate files: \":%s\/exe \\(.\\)Snip \/exe \\1Snipp \/g\"","package":"snipMate.zip","4":"snipMate.zip","src_id":"9966","5":"9966","creation_date":"1234563846","6":"1234563846"},{"0":"2540","vim_version":"7.0","1":"7.0","script_version":"0.6180","2":"0.6180","version_comment":"Added support for 'set expandtab', supertab.vim, and fixed some bugs.","3":"Added support for 'set expandtab', supertab.vim, and fixed some bugs.","package":"snipMate.zip","4":"snipMate.zip","src_id":"9961","5":"9961","creation_date":"1234496808","6":"1234496808"},{"0":"2540","vim_version":"7.0","1":"7.0","script_version":"0.42","2":"0.42","version_comment":"Initial upload","3":"Initial upload","package":"snipMate.zip","4":"snipMate.zip","src_id":"9952","5":"9952","creation_date":"1234392548","6":"1234392548"}]},"2539":{"script_id":"2539","0":"2539","script_name":"css color preview","1":"css color preview","script_type":"syntax","2":"syntax","summary":"the script made changes from the css.vim combined with css color preview","3":"the script made changes from the css.vim combined with css color preview","description":"使用vim写CSS代码，那些乱乱的颜色代码很难记忆吧。可以将6位或者3位的十六进制代码表示的颜色显示出来。从本站下载了css color preview，但是我发现这个东西在7.2上面不能用，于是把其中的代码复制到了css.vim中，整合成了这个，所有代码均是从css color preview当中剪切然后粘贴到css.vim中的。 \r\n如果不能显示的话，请使用:set t_Co=256，需要256色。\r\ncss color preview 原版见\r\nhttp:\/\/www.vim.org\/scripts\/script.php?script_id=2150","4":"使用vim写CSS代码，那些乱乱的颜色代码很难记忆吧。可以将6位或者3位的十六进制代码表示的颜色显示出来。从本站下载了css color preview，但是我发现这个东西在7.2上面不能用，于是把其中的代码复制到了css.vim中，整合成了这个，所有代码均是从css color preview当中剪切然后粘贴到css.vim中的。 \r\n如果不能显示的话，请使用:set t_Co=256，需要256色。\r\ncss color preview 原版见\r\nhttp:\/\/www.vim.org\/scripts\/script.php?script_id=2150","install_details":"","5":"","first_name":"yingda","6":"yingda","last_name":"zhang","7":"zhang","releases":[{"0":"2539","vim_version":"7.2","1":"7.2","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"css.vim","4":"css.vim","src_id":"9949","5":"9949","creation_date":"1234339549","6":"1234339549"}]},"2538":{"script_id":"2538","0":"2538","script_name":"ashen.vim","1":"ashen.vim","script_type":"color scheme","2":"color scheme","summary":"Grayish colorscheme for GVim","3":"Grayish colorscheme for GVim","description":"This colorscheme is inspired by the syntax highlighting found on http:\/\/maemo.org\/ training material.","4":"This colorscheme is inspired by the syntax highlighting found on http:\/\/maemo.org\/ training material.","install_details":"Put the file in your ~\/.vim\/colors","5":"Put the file in your ~\/.vim\/colors","first_name":"Tuomas","6":"Tuomas","last_name":"Kasmra","7":"Kasmra","releases":[{"0":"2538","vim_version":"7.0","1":"7.0","script_version":"0.3","2":"0.3","version_comment":"Initial upload","3":"Initial upload","package":"ashen.vim","4":"ashen.vim","src_id":"9943","5":"9943","creation_date":"1234252884","6":"1234252884"}]},"2537":{"script_id":"2537","0":"2537","script_name":"earthburn","1":"earthburn","script_type":"color scheme","2":"color scheme","summary":"light, earthy, low contrast colorscheme for ruby coding","3":"light, earthy, low contrast colorscheme for ruby coding","description":"My other desktop apps have a light background and using a dark scheme for coding hurts the eyes when multiple apps are open.\r\n\r\nScreen\r\n  OSX: http:\/\/img18.imageshack.us\/my.php?image=picture4xs5.png\r\n\r\nNOTE: This will NOT look good if you use a thin font like Terminus. In general, smaller, thinner fonts require schemes with higher contrast and color. Subtle schemes like earthburn work best with antialiasing and larger type---Bitstream Vera Sans Mono, Consolas and Monaco.","4":"My other desktop apps have a light background and using a dark scheme for coding hurts the eyes when multiple apps are open.\r\n\r\nScreen\r\n  OSX: http:\/\/img18.imageshack.us\/my.php?image=picture4xs5.png\r\n\r\nNOTE: This will NOT look good if you use a thin font like Terminus. In general, smaller, thinner fonts require schemes with higher contrast and color. Subtle schemes like earthburn work best with antialiasing and larger type---Bitstream Vera Sans Mono, Consolas and Monaco.","install_details":"Save file to\r\n\r\n~\/.vim\/colors\/earthburn.vim\r\n\r\nTo use scheme while in gvim (macvim)\r\n\r\n:colo earthburn\r\n\r\nTo use as default scheme, edit ~\/.gvimrc\r\n\r\ncolors earthburn\r\n\r\n","5":"Save file to\r\n\r\n~\/.vim\/colors\/earthburn.vim\r\n\r\nTo use scheme while in gvim (macvim)\r\n\r\n:colo earthburn\r\n\r\nTo use as default scheme, edit ~\/.gvimrc\r\n\r\ncolors earthburn\r\n\r\n","first_name":"Mario","6":"Mario","last_name":"Gutierrez","7":"Gutierrez","releases":[{"0":"2537","vim_version":"7.0","1":"7.0","script_version":".4a","2":".4a","version_comment":"comment color, a touch lighter","3":"comment color, a touch lighter","package":"earthburn.vim","4":"earthburn.vim","src_id":"9942","5":"9942","creation_date":"1234212664","6":"1234212664"},{"0":"2537","vim_version":"7.0","1":"7.0","script_version":".3b","2":".3b","version_comment":"colors for haml, html, tags and fixed help characters","3":"colors for haml, html, tags and fixed help characters","package":"earthburn.vim","4":"earthburn.vim","src_id":"9935","5":"9935","creation_date":"1234146089","6":"1234146089"},{"0":"2537","vim_version":"7.0","1":"7.0","script_version":".3","2":".3","version_comment":"Made it a touch darker. Changed visual hilighting to cyanish color.","3":"Made it a touch darker. Changed visual hilighting to cyanish color.","package":"earthburn.vim","4":"earthburn.vim","src_id":"9932","5":"9932","creation_date":"1234060682","6":"1234060682"},{"0":"2537","vim_version":"7.0","1":"7.0","script_version":".2b","2":".2b","version_comment":"fold color","3":"fold color","package":"earthburn.vim","4":"earthburn.vim","src_id":"9928","5":"9928","creation_date":"1233959922","6":"1233959922"},{"0":"2537","vim_version":"6.0","1":"6.0","script_version":".1","2":".1","version_comment":"Initial upload","3":"Initial upload","package":"earthburn.vim","4":"earthburn.vim","src_id":"9919","5":"9919","creation_date":"1233865455","6":"1233865455"}]},"2536":{"script_id":"2536","0":"2536","script_name":"Lucius","1":"Lucius","script_type":"color scheme","2":"color scheme","summary":"Light and dark color scheme for GUI and 256 color terminal.","3":"Light and dark color scheme for GUI and 256 color terminal.","description":"There are several options available to customize the color scheme to your own tastes. This is particularly useful when you have to work in different environments at different times (home, work, day, night, etc).\r\n\r\nThe GUI and 256 color terminal versions of this color scheme are identical.\r\n\r\nYou can set up the color scheme by manually setting the options you want or by choosing one of the presets defined. These presets are loaded after you first source the color scheme file and are all commands that start with 'Lucius'.\r\n\r\nI have also started to create color schemes for different applications. I have been using them for PuTTY, iTerm2, and Visual Studio, but will keep adding more as I go along. You can find the files for these on Github:\r\n\r\nhttps:\/\/github.com\/jonathanfilip\/lucius\r\n\r\nYou can also clone the following repository if you use Pathogen or something similar. It holds the vim color scheme in a 'colors' directory:\r\n\r\nhttps:\/\/github.com\/jonathanfilip\/vim-lucius\r\n\r\n\r\nPresets:\r\n\r\nThere are several presets available that will set all the options for you. There are screenshots of each preset below:\r\n\r\n* LuciusDark (dark default): http:\/\/i.imgur.com\/LsZbF.png\r\n* LuciusDarkHighContrast: http:\/\/i.imgur.com\/e70i9.png\r\n* LuciusDarkLowContrast: http:\/\/i.imgur.com\/Hmw8s.png\r\n* LuciusBlack: http:\/\/i.imgur.com\/iD4ri.png\r\n* LuciusBlackHighContrast: http:\/\/i.imgur.com\/lHvTJ.png\r\n* LuciusBlackLowContrast: http:\/\/i.imgur.com\/oZLkg.png\r\n\r\n* LuciusLight (light default): http:\/\/i.imgur.com\/soYD8.png\r\n* LuciusLightLowContrast: http:\/\/i.imgur.com\/95I86.png\r\n* LuciusWhite: http:\/\/i.imgur.com\/wDzkz.png\r\n* LuciusWhiteLowContrast: http:\/\/i.imgur.com\/jlUf4.png\r\n\r\nTo use the presets, you just need to set the color scheme first. In your vimrc, you can just do this:\r\n\r\ncolorscheme lucius\r\nLuciusBlack\r\n\r\nYou can still just set the background variable and then set the color scheme. This will default to LuciusDark for 'dark' and LuciusLight for 'light'.\r\n\r\n\r\nOptions:\r\n\r\nThe presets available cover most of the options. You can, however, customize things by setting the following variables yourself:\r\n\r\ng:lucius_style  (default: 'dark')\r\n\r\nSet this option to either 'light' or 'dark' for your desired color scheme. It has the same effect as setting the background.\r\n\r\ng:lucius_contrast  (default: 'normal')\r\n\r\nThis option determines the contrast to use for text\/ui elements. It can be set to 'low', 'normal', or 'high'. At this time there is no 'high' for the light scheme.\r\n\r\ng:lucius_contrast_bg  (default: 'normal')\r\n\r\nSetting this option makes the background a higher contrast. Current settings are 'normal' and 'high'.\r\n\r\ng:lucius_use_bold (default: 1)\r\n\r\nSetting this will cause the color scheme to use bold fonts for some items.\r\n\r\ng:lucius_use_underline (default: 1)\r\n\r\nSetting this will cause the color scheme to use underlined fonts for some items.","4":"There are several options available to customize the color scheme to your own tastes. This is particularly useful when you have to work in different environments at different times (home, work, day, night, etc).\r\n\r\nThe GUI and 256 color terminal versions of this color scheme are identical.\r\n\r\nYou can set up the color scheme by manually setting the options you want or by choosing one of the presets defined. These presets are loaded after you first source the color scheme file and are all commands that start with 'Lucius'.\r\n\r\nI have also started to create color schemes for different applications. I have been using them for PuTTY, iTerm2, and Visual Studio, but will keep adding more as I go along. You can find the files for these on Github:\r\n\r\nhttps:\/\/github.com\/jonathanfilip\/lucius\r\n\r\nYou can also clone the following repository if you use Pathogen or something similar. It holds the vim color scheme in a 'colors' directory:\r\n\r\nhttps:\/\/github.com\/jonathanfilip\/vim-lucius\r\n\r\n\r\nPresets:\r\n\r\nThere are several presets available that will set all the options for you. There are screenshots of each preset below:\r\n\r\n* LuciusDark (dark default): http:\/\/i.imgur.com\/LsZbF.png\r\n* LuciusDarkHighContrast: http:\/\/i.imgur.com\/e70i9.png\r\n* LuciusDarkLowContrast: http:\/\/i.imgur.com\/Hmw8s.png\r\n* LuciusBlack: http:\/\/i.imgur.com\/iD4ri.png\r\n* LuciusBlackHighContrast: http:\/\/i.imgur.com\/lHvTJ.png\r\n* LuciusBlackLowContrast: http:\/\/i.imgur.com\/oZLkg.png\r\n\r\n* LuciusLight (light default): http:\/\/i.imgur.com\/soYD8.png\r\n* LuciusLightLowContrast: http:\/\/i.imgur.com\/95I86.png\r\n* LuciusWhite: http:\/\/i.imgur.com\/wDzkz.png\r\n* LuciusWhiteLowContrast: http:\/\/i.imgur.com\/jlUf4.png\r\n\r\nTo use the presets, you just need to set the color scheme first. In your vimrc, you can just do this:\r\n\r\ncolorscheme lucius\r\nLuciusBlack\r\n\r\nYou can still just set the background variable and then set the color scheme. This will default to LuciusDark for 'dark' and LuciusLight for 'light'.\r\n\r\n\r\nOptions:\r\n\r\nThe presets available cover most of the options. You can, however, customize things by setting the following variables yourself:\r\n\r\ng:lucius_style  (default: 'dark')\r\n\r\nSet this option to either 'light' or 'dark' for your desired color scheme. It has the same effect as setting the background.\r\n\r\ng:lucius_contrast  (default: 'normal')\r\n\r\nThis option determines the contrast to use for text\/ui elements. It can be set to 'low', 'normal', or 'high'. At this time there is no 'high' for the light scheme.\r\n\r\ng:lucius_contrast_bg  (default: 'normal')\r\n\r\nSetting this option makes the background a higher contrast. Current settings are 'normal' and 'high'.\r\n\r\ng:lucius_use_bold (default: 1)\r\n\r\nSetting this will cause the color scheme to use bold fonts for some items.\r\n\r\ng:lucius_use_underline (default: 1)\r\n\r\nSetting this will cause the color scheme to use underlined fonts for some items.","install_details":"Copy the file to your vim colors directory and then type :colorscheme lucius. You can also any of the presets defined above.","5":"Copy the file to your vim colors directory and then type :colorscheme lucius. You can also any of the presets defined above.","first_name":"Jonathan","6":"Jonathan","last_name":"Filip","7":"Filip","releases":[{"0":"2536","vim_version":"7.0","1":"7.0","script_version":"8.1.7","2":"8.1.7","version_comment":"Changed the MatchParen on the dark version to help out with an issue where certain terminals would make the text invisible.","3":"Changed the MatchParen on the dark version to help out with an issue where certain terminals would make the text invisible.","package":"lucius.vim","4":"lucius.vim","src_id":"23000","5":"23000","creation_date":"1425924441","6":"1425924441"},{"0":"2536","vim_version":"7.0","1":"7.0","script_version":"8.1.4","2":"8.1.4","version_comment":"Added 'lucius_no_term_bg' option:\r\nSetting this will cause the color scheme to not set a background color in the terminal (useful for transparency or terminals with different background colors).","3":"Added 'lucius_no_term_bg' option:\r\nSetting this will cause the color scheme to not set a background color in the terminal (useful for transparency or terminals with different background colors).","package":"lucius.vim","4":"lucius.vim","src_id":"20356","5":"20356","creation_date":"1371145245","6":"1371145245"},{"0":"2536","vim_version":"7.0","1":"7.0","script_version":"8.1.3","2":"8.1.3","version_comment":"Changed ColorColumn to be more subtle (only slightly different from the background).","3":"Changed ColorColumn to be more subtle (only slightly different from the background).","package":"lucius.vim","4":"lucius.vim","src_id":"20309","5":"20309","creation_date":"1370552256","6":"1370552256"},{"0":"2536","vim_version":"7.0","1":"7.0","script_version":"8.1.2","2":"8.1.2","version_comment":"Fixed some issues that arise from setting Normal at different times in the file. This basically always caused the \"background\" option to be set to \"light\".","3":"Fixed some issues that arise from setting Normal at different times in the file. This basically always caused the \"background\" option to be set to \"light\".","package":"lucius.vim","4":"lucius.vim","src_id":"18554","5":"18554","creation_date":"1346869208","6":"1346869208"},{"0":"2536","vim_version":"7.0","1":"7.0","script_version":"8.1.1","2":"8.1.1","version_comment":"Fixed a bug pointed out by github user lyokha where I wasn't properly scoping the 'item' variable used in for loops. This caused an issue where their own 'item' variable was defined elsewhere.","3":"Fixed a bug pointed out by github user lyokha where I wasn't properly scoping the 'item' variable used in for loops. This caused an issue where their own 'item' variable was defined elsewhere.","package":"lucius.vim","4":"lucius.vim","src_id":"18481","5":"18481","creation_date":"1345819090","6":"1345819090"},{"0":"2536","vim_version":"7.0","1":"7.0","script_version":"8.1.0","2":"8.1.0","version_comment":"After some initial feedback, I reworked the script some more to try to make the options easier to understand: \r\n\r\n* Changed 'high_contrast' and 'high_contrast_bg' settings to just 'contrast' and 'contrast_bg'. These settings now have values of 'high', 'low', or 'normal' (instead of the integer values). \r\n* Simplified documentation \r\n* Changed preset names so they are more descriptive and easier to understand","3":"After some initial feedback, I reworked the script some more to try to make the options easier to understand: \r\n\r\n* Changed 'high_contrast' and 'high_contrast_bg' settings to just 'contrast' and 'contrast_bg'. These settings now have values of 'high', 'low', or 'normal' (instead of the integer values). \r\n* Simplified documentation \r\n* Changed preset names so they are more descriptive and easier to understand","package":"lucius.vim","4":"lucius.vim","src_id":"18477","5":"18477","creation_date":"1345778272","6":"1345778272"},{"0":"2536","vim_version":"7.0","1":"7.0","script_version":"8.0.1","2":"8.0.1","version_comment":"* Fixed a bug where the color scheme wouldn't load if you hadn't set g:lucius_style.\r\n* Added some more high contrast highlights for dark schemes (presets LuciusDark2 and LuciusBlack2).","3":"* Fixed a bug where the color scheme wouldn't load if you hadn't set g:lucius_style.\r\n* Added some more high contrast highlights for dark schemes (presets LuciusDark2 and LuciusBlack2).","package":"lucius.vim","4":"lucius.vim","src_id":"18470","5":"18470","creation_date":"1345755980","6":"1345755980"},{"0":"2536","vim_version":"7.0","1":"7.0","script_version":"8.0.0","2":"8.0.0","version_comment":"Rewrote the color scheme to allow for more customization. There are now options for contrast, background contrast, bold, underline, etc. The presets that exist now are Light, LightBright, White, WhiteBright, Dark, DarkDim, Black, and BlackDim. Light and Dark exist from previous versions, whereas White and Black are new. The Bright variants for light are lower contrast options for the light background. Also put color files for iTerm2 and PuTTY on Github.","3":"Rewrote the color scheme to allow for more customization. There are now options for contrast, background contrast, bold, underline, etc. The presets that exist now are Light, LightBright, White, WhiteBright, Dark, DarkDim, Black, and BlackDim. Light and Dark exist from previous versions, whereas White and Black are new. The Bright variants for light are lower contrast options for the light background. Also put color files for iTerm2 and PuTTY on Github.","package":"lucius.vim","4":"lucius.vim","src_id":"18462","5":"18462","creation_date":"1345735659","6":"1345735659"},{"0":"2536","vim_version":"7.0","1":"7.0","script_version":"7.1.1","2":"7.1.1","version_comment":"* Toned down the Error and Todo colors for the light scheme.\r\n* Made the Normal foreground one step lighter for the light scheme.\r\n* Added definitions for CursorLineNr (thanks to Michael W.).","3":"* Toned down the Error and Todo colors for the light scheme.\r\n* Made the Normal foreground one step lighter for the light scheme.\r\n* Added definitions for CursorLineNr (thanks to Michael W.).","package":"lucius.vim","4":"lucius.vim","src_id":"17749","5":"17749","creation_date":"1334072440","6":"1334072440"},{"0":"2536","vim_version":"7.0","1":"7.0","script_version":"7.1.0","2":"7.1.0","version_comment":"Added a \"DarkDim\" variant that is similar to the regular dark scheme, but has a bit less contrast. Changed the cterm spelling highlights to use underline.\r\n","3":"Added a \"DarkDim\" variant that is similar to the regular dark scheme, but has a bit less contrast. Changed the cterm spelling highlights to use underline.\r\n","package":"lucius.vim","4":"lucius.vim","src_id":"17668","5":"17668","creation_date":"1332857956","6":"1332857956"},{"0":"2536","vim_version":"7.0","1":"7.0","script_version":"7.0.0","2":"7.0.0","version_comment":"Version 7 has unified the 256 color terminal and GUI versions (the GUI version only uses colors available on the 256 color terminal). The overall colors were also toned down a little bit (light version is now a light gray instead of white and the dark version is slightly lighter) to make it easier on the eyes.\r\n","3":"Version 7 has unified the 256 color terminal and GUI versions (the GUI version only uses colors available on the 256 color terminal). The overall colors were also toned down a little bit (light version is now a light gray instead of white and the dark version is slightly lighter) to make it easier on the eyes.\r\n","package":"lucius.vim","4":"lucius.vim","src_id":"17543","5":"17543","creation_date":"1330446490","6":"1330446490"},{"0":"2536","vim_version":"7.0","1":"7.0","script_version":"6.1.0","2":"6.1.0","version_comment":"Switched around some of the main highlight colors. Instead of using a green for constants, I switched it to be the yellow\/orange. This makes constants more distinguishable from other highlights (identifier, statement, preproc, and type are now all some sort of blue or green). Also tweaked a few other settings. The \"blue\" style is kind of back, but is actually just the dark style with a more blue background.","3":"Switched around some of the main highlight colors. Instead of using a green for constants, I switched it to be the yellow\/orange. This makes constants more distinguishable from other highlights (identifier, statement, preproc, and type are now all some sort of blue or green). Also tweaked a few other settings. The \"blue\" style is kind of back, but is actually just the dark style with a more blue background.","package":"lucius.vim","4":"lucius.vim","src_id":"16615","5":"16615","creation_date":"1317654899","6":"1317654899"},{"0":"2536","vim_version":"7.0","1":"7.0","script_version":"6.03","2":"6.03","version_comment":"Added some more contrast to the dark version's syntax highlighting and diff rows. Tweaked the light colors slightly and changed the Title color.","3":"Added some more contrast to the dark version's syntax highlighting and diff rows. Tweaked the light colors slightly and changed the Title color.","package":"lucius.vim","4":"lucius.vim","src_id":"16288","5":"16288","creation_date":"1313594899","6":"1313594899"},{"0":"2536","vim_version":"7.0","1":"7.0","script_version":"6.02","2":"6.02","version_comment":"Changed the difftext on the light version to stand out more. Also removed a typo \":\" in the file.","3":"Changed the difftext on the light version to stand out more. Also removed a typo \":\" in the file.","package":"lucius.vim","4":"lucius.vim","src_id":"16194","5":"16194","creation_date":"1312468775","6":"1312468775"},{"0":"2536","vim_version":"7.0","1":"7.0","script_version":"6.01","2":"6.01","version_comment":"Changed the diff colors so syntax highlighting is disabled on diff lines and the colors were tweaked.","3":"Changed the diff colors so syntax highlighting is disabled on diff lines and the colors were tweaked.","package":"lucius.vim","4":"lucius.vim","src_id":"16179","5":"16179","creation_date":"1312228200","6":"1312228200"},{"0":"2536","vim_version":"7.0","1":"7.0","script_version":"6.0","2":"6.0","version_comment":"See script description. The theme has been revamped a bit to unify colors and provide better contrast between text and interface elements.","3":"See script description. The theme has been revamped a bit to unify colors and provide better contrast between text and interface elements.","package":"lucius.vim","4":"lucius.vim","src_id":"16176","5":"16176","creation_date":"1312211559","6":"1312211559"},{"0":"2536","vim_version":"7.0","1":"7.0","script_version":"5Final","2":"5Final","version_comment":"Final version of the old styles.","3":"Final version of the old styles.","package":"lucius.vim","4":"lucius.vim","src_id":"16175","5":"16175","creation_date":"1312211491","6":"1312211491"},{"0":"2536","vim_version":"7.0","1":"7.0","script_version":"5.2","2":"5.2","version_comment":"Tried to port the blue scheme to 256 colors, however it mostly stayed similar to the dark one with some adjustments for the text highlighting (not enough choices in 256 colors to match the blues that are used). Changed a few more colors on the light scheme as well.","3":"Tried to port the blue scheme to 256 colors, however it mostly stayed similar to the dark one with some adjustments for the text highlighting (not enough choices in 256 colors to match the blues that are used). Changed a few more colors on the light scheme as well.","package":"lucius.vim","4":"lucius.vim","src_id":"15197","5":"15197","creation_date":"1299873305","6":"1299873305"},{"0":"2536","vim_version":"7.0","1":"7.0","script_version":"5.1","2":"5.1","version_comment":"Finished making changes to the light version. Also added a blue variant of the normal, dark scheme. Removed the non-primary highlight groups (Label, Operator, etc) to make the file a little smaller. Also added commands to change between the different schemes (LuciusLight, LuciusDark, LuciusBlue).","3":"Finished making changes to the light version. Also added a blue variant of the normal, dark scheme. Removed the non-primary highlight groups (Label, Operator, etc) to make the file a little smaller. Also added commands to change between the different schemes (LuciusLight, LuciusDark, LuciusBlue).","package":"lucius.vim","4":"lucius.vim","src_id":"15158","5":"15158","creation_date":"1299246876","6":"1299246876"},{"0":"2536","vim_version":"7.0","1":"7.0","script_version":"5.03","2":"5.03","version_comment":"A few more tweaks to colors for the light version. Also changed the MatchParen to use a background color. ","3":"A few more tweaks to colors for the light version. Also changed the MatchParen to use a background color. ","package":"lucius.vim","4":"lucius.vim","src_id":"15100","5":"15100","creation_date":"1298472235","6":"1298472235"},{"0":"2536","vim_version":"7.0","1":"7.0","script_version":"5.02","2":"5.02","version_comment":"Tweaked the colors some more and refreshed the 256 term colors to match the new settings (for the light version only)","3":"Tweaked the colors some more and refreshed the 256 term colors to match the new settings (for the light version only)","package":"lucius.vim","4":"lucius.vim","src_id":"15028","5":"15028","creation_date":"1297867230","6":"1297867230"},{"0":"2536","vim_version":"7.0","1":"7.0","script_version":"5.01","2":"5.01","version_comment":"Some changes to colors in the light version","3":"Some changes to colors in the light version","package":"lucius.vim","4":"lucius.vim","src_id":"15008","5":"15008","creation_date":"1297709333","6":"1297709333"},{"0":"2536","vim_version":"7.0","1":"7.0","script_version":"5.0","2":"5.0","version_comment":"Added a light colorscheme option. This still defaults to the dark version, but you can set g:lucius_style to \"light\" for a light background scheme. More tweaks will come as I continue to use it.","3":"Added a light colorscheme option. This still defaults to the dark version, but you can set g:lucius_style to \"light\" for a light background scheme. More tweaks will come as I continue to use it.","package":"lucius.vim","4":"lucius.vim","src_id":"14971","5":"14971","creation_date":"1297087014","6":"1297087014"},{"0":"2536","vim_version":"7.0","1":"7.0","script_version":"4.0","2":"4.0","version_comment":"This version is tweaked a bit. I muted the colors a little and also eliminated some of the lower spectrum highlighting in favor of more blues and greens. This seems to be easier to look at, in my opinion. I also added some custom highlights for the vimwiki script (vimscript #2226).\r\n","3":"This version is tweaked a bit. I muted the colors a little and also eliminated some of the lower spectrum highlighting in favor of more blues and greens. This seems to be easier to look at, in my opinion. I also added some custom highlights for the vimwiki script (vimscript #2226).\r\n","package":"lucius.vim","4":"lucius.vim","src_id":"14531","5":"14531","creation_date":"1292509610","6":"1292509610"},{"0":"2536","vim_version":"7.0","1":"7.0","script_version":"3.6.1","2":"3.6.1","version_comment":"Added ColorColumn for Vim 7.3","3":"Added ColorColumn for Vim 7.3","package":"lucius.vim","4":"lucius.vim","src_id":"13588","5":"13588","creation_date":"1281977990","6":"1281977990"},{"0":"2536","vim_version":"7.0","1":"7.0","script_version":"3.6","2":"3.6","version_comment":"- Changed the cursor line\/column to be a little more visible\r\n- Updated the fold line","3":"- Changed the cursor line\/column to be a little more visible\r\n- Updated the fold line","package":"lucius.vim","4":"lucius.vim","src_id":"13089","5":"13089","creation_date":"1275497677","6":"1275497677"},{"0":"2536","vim_version":"7.0","1":"7.0","script_version":"3.5","2":"3.5","version_comment":"Updated some of the cterm colors after applying colorsupport.vim to the scheme.","3":"Updated some of the cterm colors after applying colorsupport.vim to the scheme.","package":"lucius.vim","4":"lucius.vim","src_id":"12868","5":"12868","creation_date":"1271690843","6":"1271690843"},{"0":"2536","vim_version":"7.0","1":"7.0","script_version":"3.2","2":"3.2","version_comment":"A few minor updates (SpecialKey, Identifier, PreProc)","3":"A few minor updates (SpecialKey, Identifier, PreProc)","package":"lucius.vim","4":"lucius.vim","src_id":"12154","5":"12154","creation_date":"1264093205","6":"1264093205"},{"0":"2536","vim_version":"7.0","1":"7.0","script_version":"3.1","2":"3.1","version_comment":"Got rid of bold for CursorLine and Pmenu stuff","3":"Got rid of bold for CursorLine and Pmenu stuff","package":"lucius.vim","4":"lucius.vim","src_id":"11556","5":"11556","creation_date":"1256143374","6":"1256143374"},{"0":"2536","vim_version":"7.0","1":"7.0","script_version":"3.0","2":"3.0","version_comment":"This version has a lot of small changes. The colors are toned down some more and new colors exist for diffs, status line, popup menu, wild menu, cursor line and column, error, line numbers, splits, folds, etc. Many of the new colors are similar to what they were before, but work a little better with the scheme now.","3":"This version has a lot of small changes. The colors are toned down some more and new colors exist for diffs, status line, popup menu, wild menu, cursor line and column, error, line numbers, splits, folds, etc. Many of the new colors are similar to what they were before, but work a little better with the scheme now.","package":"lucius.vim","4":"lucius.vim","src_id":"11449","5":"11449","creation_date":"1254146384","6":"1254146384"},{"0":"2536","vim_version":"7.0","1":"7.0","script_version":"2.6","2":"2.6","version_comment":"Toned down the saturation of some of the colors; other minor things","3":"Toned down the saturation of some of the colors; other minor things","package":"lucius.vim","4":"lucius.vim","src_id":"11010","5":"11010","creation_date":"1247576818","6":"1247576818"},{"0":"2536","vim_version":"7.0","1":"7.0","script_version":"2.5","2":"2.5","version_comment":"Minor tweak to VertSplit","3":"Minor tweak to VertSplit","package":"lucius.vim","4":"lucius.vim","src_id":"10333","5":"10333","creation_date":"1238598242","6":"1238598242"},{"0":"2536","vim_version":"7.0","1":"7.0","script_version":"2.4","2":"2.4","version_comment":"Modified CursorColumn, CursorLine, and CursorIM","3":"Modified CursorColumn, CursorLine, and CursorIM","package":"lucius.vim","4":"lucius.vim","src_id":"10269","5":"10269","creation_date":"1237813788","6":"1237813788"},{"0":"2536","vim_version":"7.0","1":"7.0","script_version":"2.3","2":"2.3","version_comment":"Changed the search highlight to something more visible.","3":"Changed the search highlight to something more visible.","package":"lucius.vim","4":"lucius.vim","src_id":"10203","5":"10203","creation_date":"1236957966","6":"1236957966"},{"0":"2536","vim_version":"7.0","1":"7.0","script_version":"2.2","2":"2.2","version_comment":"Made the normal GUI text slightly brighter","3":"Made the normal GUI text slightly brighter","package":"lucius.vim","4":"lucius.vim","src_id":"10152","5":"10152","creation_date":"1236618357","6":"1236618357"},{"0":"2536","vim_version":"7.0","1":"7.0","script_version":"2.1","2":"2.1","version_comment":"- Fixed the normal fg and bg for cterm \r\n- Removed yellow tint from normal text\r\n- Fixed status line in cterm","3":"- Fixed the normal fg and bg for cterm \r\n- Removed yellow tint from normal text\r\n- Fixed status line in cterm","package":"lucius.vim","4":"lucius.vim","src_id":"10033","5":"10033","creation_date":"1235573977","6":"1235573977"},{"0":"2536","vim_version":"7.0","1":"7.0","script_version":"2.0","2":"2.0","version_comment":"Added 256 color terminal support.","3":"Added 256 color terminal support.","package":"lucius.vim","4":"lucius.vim","src_id":"10020","5":"10020","creation_date":"1235488785","6":"1235488785"},{"0":"2536","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"lucius.vim","4":"lucius.vim","src_id":"9911","5":"9911","creation_date":"1233759266","6":"1233759266"}]},"2535":{"script_id":"2535","0":"2535","script_name":"cca.vim","1":"cca.vim","script_type":"utility","2":"utility","summary":"code_complete_again: a complete plugin mixed the code_complete and snippetsEmu","3":"code_complete_again: a complete plugin mixed the code_complete and snippetsEmu","description":"homepage: http:\/\/code.google.com\/p\/vim-cca\/\r\nnow you can use cca.vim and ctk.vim (http:\/\/vim-cca.googlecode.com\/files\/ctk.vim) implements all features of c.vim\r\n\r\nyou can add yourself compiler at snippets file, and all the compilers can invoked by ctk.vim.\r\n\r\nin windows, you can compile and run, but now in unix, you can only compile : i can find a way to execute a program in a true-terminal. next version will solve this problem.\r\n\r\nctk.vim is only in beta version now.\r\n\r\nif you have any good idea, please tell me at here: http:\/\/code.google.com\/p\/vim-cca\/issues\/list\r\n\r\n\r\nUseage:                                                                          \r\n                                                                                 \r\n    this is a re-code version of code_complete(new update)                       \r\n    (vimscript#2427) the                   \r\n    original version of code_complete is write by mingbai, at                    \r\n    (vimscript#1764)                       \r\n                                                                                 \r\n    this plugin mix the features of code_complete and snippetEmu,              \r\n    you can put the snippet file in the cca_snippets_folder (defaultly           \r\n    \"snippets\"), and put template file in cca_template_folder                    \r\n    (defaultly \"templates\"). then you can input a tigger word and a              \r\n    hotkey to complete. e.g: if the hotkey is <m-d> (Alt+d or Meta+d,            \r\n    i found this combine-key is easy to press :) ) and you has a                 \r\n    snippet named foo, when you input the \"foo<m-d>\", it maybe changed           \r\n    to: (which \"|\" is the position of your cursor)                               \r\n                                                                                 \r\n        foobar|                                                                  \r\n                                                                                 \r\n    cca support snippetsEmu-style named tag and command tag in your              \r\n    snippet (and template file). you can define the tag-mark youself,            \r\n    and it will be highlighted (if you open the built-in highlight               \r\n    function of Vim). this is a summary of the kinds of tag. (the tags           \r\n    will be highlighted special, if you open highlight. and suppose              \r\n    the cca_tagstart is \"<{\". the tagcommand is ':',  and the tagend             \r\n    is \"}>\")                                                                     \r\n                                                                                 \r\n        - cursor tag:   <{}> or <{:}> if you press hotkey, and next              \r\n                        tag is a empty tag, the cursor will move to              \r\n                        there.                                                   \r\n        - named tag:    <{foo}> after you press hotkey, the name of              \r\n                        the tag will selected, and if you input a text           \r\n                        to replace it, all tag has the same name with            \r\n                        current tag will be replaced to the same                 \r\n                        value.  e.g:  (the pipe is position of cursor)           \r\n                                                                                 \r\n                        |   <{foo:1}> is a <{foo:2}>.                            \r\n                                                                                 \r\n                        after you press <a-d> and input \"bar\"                    \r\n                        directly, it will changed to:                            \r\n                                                                                 \r\n                        bar| is a bar.                                           \r\n                                                                                 \r\n                        the :1 and :2 mark is for sign tags for                  \r\n                        regconize it when you make nest tags.                    \r\n                                                                                 \r\n        - identifier tag:                                                        \r\n                        cca must register tag's name and command for             \r\n                        replace nest tag correctlly.  if you can sure            \r\n                        the tag is only for name replace, user won't             \r\n                        make complete in it (that is, it will never be           \r\n                        a nest tag), and it didn't have any command,             \r\n                        you can just add a \"cmd\" mark after                      \r\n                        identifier.  e.g: <{i:}>. and cca won't                  \r\n                        register this tag.                                       \r\n                                                                                 \r\n        - command tag:  <{foo:1}>, or <{:1}> where \"1\" may be any                \r\n                        number. this is the command number in                    \r\n                        dictionary b:cca.tag_table. if this is a                 \r\n                        noname command tag, the command will calculate           \r\n                        immediately. and if it has a name, it will act           \r\n                        as a named tag, and calculate the command when           \r\n                        you leave the tag (goto the next tag).  the              \r\n                        \"xt\" snippet in common.vim is a noname command           \r\n                        tag, and \"printf\" in c_snippets.vim is a named           \r\n                        command tag.                                             \r\n                                                                                 \r\n                XXX:    you can complete at normal, select and insert            \r\n                        mode, but you must notice that the first char            \r\n                        of tag is not \"in\" the tag.  e.g: |<{A}> now             \r\n                        cursor is NOT in the tag A. so it is in normal           \r\n                        mode, so if you want to jump to next tag, you            \r\n                        should make sure the cursor is just in the tag           \r\n                                                                                 \r\nOptions:                                                                         \r\n                                                                                 \r\n        cca_hotkey      this defined the hotkey for complete                     \r\n                                                                                 \r\n        cca_submitkey   this defined the submitkey.(that is, jump over           \r\n                        a line, and leave all tags in this line into             \r\n                        its default value).                                      \r\n                                                                                 \r\n        cca_tagstart                                                             \r\n        cca_tagend                                                               \r\n        cca_tagcommand  this defined the tag mark. and you can                   \r\n                        define them as buffer-variables.                         \r\n                                                                                 \r\n        cca_search_range                                                         \r\n                        this define the search range for tag jump.               \r\n                        defaultly it is 100, it means just search the            \r\n                        tags in 100 line under current line. if it set           \r\n                        to zero, only search tags in screen.                     \r\n                                                                                 \r\n        cca_filetype_ext_var                                                     \r\n                        this define the filetype buffer variable name.           \r\n                        snippets support this name to show the ext               \r\n                        name for specific filetype. it defaultly                 \r\n                        \"ft_ext\", and b:ft_ext will be used as a                 \r\n                        ext-name specified variable name.                        \r\n                                                                                 \r\n        cca_locale_tag_var                                                       \r\n                        this is a dictionary name for snippets file              \r\n                        show its locale tag marks. it has three item:            \r\n                        start, end and cmd. it defined tagstart,                 \r\n                        tagend and tagcommand in specified snippets              \r\n                        file.                                                    \r\n                                                                                 \r\n                XXX:    to use cca_filetype_ext_var and                          \r\n                        cca_locale_tag_var, see the specified snippets           \r\n                        files.                                                   \r\n                                                                                 \r\n        cca_snippets_folder                                                      \r\n        cca_template_folder                                                      \r\n                        these define the default folder where cca to             \r\n                        find the snippets files and template files. it           \r\n                        must be found at 'runtimepath'.                          \r\n                                                                                 \r\n        cca_auto_indent no use in this version                                   \r\n                                                                                 \r\nCommand:                                                                         \r\n                                                                                 \r\n        StartComplete                                                            \r\n        StopComplete                                                             \r\n                        Start and stop the complete this will register           \r\n                        or unregister the key map and do some                    \r\n                        initialliztion or clean work.                            \r\n                                                                                 \r\n        DefineSnippet   define the snippets. each snippets file are              \r\n                        all combined with this command. the format is:           \r\n                        DefineSnippet {trigger word}: {complete text}            \r\n                        trigger word can be anything. it can have                \r\n                        space, can be a symbol. but if it have space             \r\n                        and have more than one symbol, when you input            \r\n                        it, you should add a \"#\" before it. e.g: now             \r\n                        we define a sinppet:                                     \r\n                                                                                 \r\n                DefineSnippet trigger with word: this is a trigger with <{}>word \r\n                                                                                 \r\n                        then we can input:                                       \r\n                        #trigger with word<m-d>                                  \r\n                                                                                 \r\n                        then it will change to:                                  \r\n                        this is a trigger with |word                             \r\n                                                                                 \r\n                        the cursor is before \"word\"                              \r\n                                                                                 \r\n        RefreshSnippets refresh the current snippets file. if no                 \r\n                        filetype is set, this command will load                  \r\n                        \"common.vim\" in snippets folder. the snippets            \r\n                        file is under \"filetype\" folder in snippets              \r\n                        folder, or named \"filetype_others.vim\", which            \r\n                        others can be any words. all of snippets file            \r\n                        will load in.                                            \r\n","4":"homepage: http:\/\/code.google.com\/p\/vim-cca\/\r\nnow you can use cca.vim and ctk.vim (http:\/\/vim-cca.googlecode.com\/files\/ctk.vim) implements all features of c.vim\r\n\r\nyou can add yourself compiler at snippets file, and all the compilers can invoked by ctk.vim.\r\n\r\nin windows, you can compile and run, but now in unix, you can only compile : i can find a way to execute a program in a true-terminal. next version will solve this problem.\r\n\r\nctk.vim is only in beta version now.\r\n\r\nif you have any good idea, please tell me at here: http:\/\/code.google.com\/p\/vim-cca\/issues\/list\r\n\r\n\r\nUseage:                                                                          \r\n                                                                                 \r\n    this is a re-code version of code_complete(new update)                       \r\n    (vimscript#2427) the                   \r\n    original version of code_complete is write by mingbai, at                    \r\n    (vimscript#1764)                       \r\n                                                                                 \r\n    this plugin mix the features of code_complete and snippetEmu,              \r\n    you can put the snippet file in the cca_snippets_folder (defaultly           \r\n    \"snippets\"), and put template file in cca_template_folder                    \r\n    (defaultly \"templates\"). then you can input a tigger word and a              \r\n    hotkey to complete. e.g: if the hotkey is <m-d> (Alt+d or Meta+d,            \r\n    i found this combine-key is easy to press :) ) and you has a                 \r\n    snippet named foo, when you input the \"foo<m-d>\", it maybe changed           \r\n    to: (which \"|\" is the position of your cursor)                               \r\n                                                                                 \r\n        foobar|                                                                  \r\n                                                                                 \r\n    cca support snippetsEmu-style named tag and command tag in your              \r\n    snippet (and template file). you can define the tag-mark youself,            \r\n    and it will be highlighted (if you open the built-in highlight               \r\n    function of Vim). this is a summary of the kinds of tag. (the tags           \r\n    will be highlighted special, if you open highlight. and suppose              \r\n    the cca_tagstart is \"<{\". the tagcommand is ':',  and the tagend             \r\n    is \"}>\")                                                                     \r\n                                                                                 \r\n        - cursor tag:   <{}> or <{:}> if you press hotkey, and next              \r\n                        tag is a empty tag, the cursor will move to              \r\n                        there.                                                   \r\n        - named tag:    <{foo}> after you press hotkey, the name of              \r\n                        the tag will selected, and if you input a text           \r\n                        to replace it, all tag has the same name with            \r\n                        current tag will be replaced to the same                 \r\n                        value.  e.g:  (the pipe is position of cursor)           \r\n                                                                                 \r\n                        |   <{foo:1}> is a <{foo:2}>.                            \r\n                                                                                 \r\n                        after you press <a-d> and input \"bar\"                    \r\n                        directly, it will changed to:                            \r\n                                                                                 \r\n                        bar| is a bar.                                           \r\n                                                                                 \r\n                        the :1 and :2 mark is for sign tags for                  \r\n                        regconize it when you make nest tags.                    \r\n                                                                                 \r\n        - identifier tag:                                                        \r\n                        cca must register tag's name and command for             \r\n                        replace nest tag correctlly.  if you can sure            \r\n                        the tag is only for name replace, user won't             \r\n                        make complete in it (that is, it will never be           \r\n                        a nest tag), and it didn't have any command,             \r\n                        you can just add a \"cmd\" mark after                      \r\n                        identifier.  e.g: <{i:}>. and cca won't                  \r\n                        register this tag.                                       \r\n                                                                                 \r\n        - command tag:  <{foo:1}>, or <{:1}> where \"1\" may be any                \r\n                        number. this is the command number in                    \r\n                        dictionary b:cca.tag_table. if this is a                 \r\n                        noname command tag, the command will calculate           \r\n                        immediately. and if it has a name, it will act           \r\n                        as a named tag, and calculate the command when           \r\n                        you leave the tag (goto the next tag).  the              \r\n                        \"xt\" snippet in common.vim is a noname command           \r\n                        tag, and \"printf\" in c_snippets.vim is a named           \r\n                        command tag.                                             \r\n                                                                                 \r\n                XXX:    you can complete at normal, select and insert            \r\n                        mode, but you must notice that the first char            \r\n                        of tag is not \"in\" the tag.  e.g: |<{A}> now             \r\n                        cursor is NOT in the tag A. so it is in normal           \r\n                        mode, so if you want to jump to next tag, you            \r\n                        should make sure the cursor is just in the tag           \r\n                                                                                 \r\nOptions:                                                                         \r\n                                                                                 \r\n        cca_hotkey      this defined the hotkey for complete                     \r\n                                                                                 \r\n        cca_submitkey   this defined the submitkey.(that is, jump over           \r\n                        a line, and leave all tags in this line into             \r\n                        its default value).                                      \r\n                                                                                 \r\n        cca_tagstart                                                             \r\n        cca_tagend                                                               \r\n        cca_tagcommand  this defined the tag mark. and you can                   \r\n                        define them as buffer-variables.                         \r\n                                                                                 \r\n        cca_search_range                                                         \r\n                        this define the search range for tag jump.               \r\n                        defaultly it is 100, it means just search the            \r\n                        tags in 100 line under current line. if it set           \r\n                        to zero, only search tags in screen.                     \r\n                                                                                 \r\n        cca_filetype_ext_var                                                     \r\n                        this define the filetype buffer variable name.           \r\n                        snippets support this name to show the ext               \r\n                        name for specific filetype. it defaultly                 \r\n                        \"ft_ext\", and b:ft_ext will be used as a                 \r\n                        ext-name specified variable name.                        \r\n                                                                                 \r\n        cca_locale_tag_var                                                       \r\n                        this is a dictionary name for snippets file              \r\n                        show its locale tag marks. it has three item:            \r\n                        start, end and cmd. it defined tagstart,                 \r\n                        tagend and tagcommand in specified snippets              \r\n                        file.                                                    \r\n                                                                                 \r\n                XXX:    to use cca_filetype_ext_var and                          \r\n                        cca_locale_tag_var, see the specified snippets           \r\n                        files.                                                   \r\n                                                                                 \r\n        cca_snippets_folder                                                      \r\n        cca_template_folder                                                      \r\n                        these define the default folder where cca to             \r\n                        find the snippets files and template files. it           \r\n                        must be found at 'runtimepath'.                          \r\n                                                                                 \r\n        cca_auto_indent no use in this version                                   \r\n                                                                                 \r\nCommand:                                                                         \r\n                                                                                 \r\n        StartComplete                                                            \r\n        StopComplete                                                             \r\n                        Start and stop the complete this will register           \r\n                        or unregister the key map and do some                    \r\n                        initialliztion or clean work.                            \r\n                                                                                 \r\n        DefineSnippet   define the snippets. each snippets file are              \r\n                        all combined with this command. the format is:           \r\n                        DefineSnippet {trigger word}: {complete text}            \r\n                        trigger word can be anything. it can have                \r\n                        space, can be a symbol. but if it have space             \r\n                        and have more than one symbol, when you input            \r\n                        it, you should add a \"#\" before it. e.g: now             \r\n                        we define a sinppet:                                     \r\n                                                                                 \r\n                DefineSnippet trigger with word: this is a trigger with <{}>word \r\n                                                                                 \r\n                        then we can input:                                       \r\n                        #trigger with word<m-d>                                  \r\n                                                                                 \r\n                        then it will change to:                                  \r\n                        this is a trigger with |word                             \r\n                                                                                 \r\n                        the cursor is before \"word\"                              \r\n                                                                                 \r\n        RefreshSnippets refresh the current snippets file. if no                 \r\n                        filetype is set, this command will load                  \r\n                        \"common.vim\" in snippets folder. the snippets            \r\n                        file is under \"filetype\" folder in snippets              \r\n                        folder, or named \"filetype_others.vim\", which            \r\n                        others can be any words. all of snippets file            \r\n                        will load in.                                            \r\n","install_details":"for cca.vba: open with vim, and press :so%<CR> (<CR> means enter button)\r\nfor cca.vim: just drop it in your plugin folder, it should be ~\/.vim\/plugin (in *nix) or $VIM\/vimfiles\/plugin (in windows).\r\nfor cca-bundles.zip: unzip it, and put snippets folder into your vim folder (just the parent folder of plugin folder above)\r\n","5":"for cca.vba: open with vim, and press :so%<CR> (<CR> means enter button)\r\nfor cca.vim: just drop it in your plugin folder, it should be ~\/.vim\/plugin (in *nix) or $VIM\/vimfiles\/plugin (in windows).\r\nfor cca-bundles.zip: unzip it, and put snippets folder into your vim folder (just the parent folder of plugin folder above)\r\n","first_name":"Wxyarv","6":"Wxyarv","last_name":"Wang","7":"Wang","releases":[{"0":"2535","vim_version":"7.0","1":"7.0","script_version":"0.2","2":"0.2","version_comment":"i forgot comment the debug option...","3":"i forgot comment the debug option...","package":"cca.vim","4":"cca.vim","src_id":"10043","5":"10043","creation_date":"1235665098","6":"1235665098"},{"0":"2535","vim_version":"7.0","1":"7.0","script_version":"0.2","2":"0.2","version_comment":"bugfix - make function complete more useful.","3":"bugfix - make function complete more useful.","package":"cca.vim","4":"cca.vim","src_id":"9996","5":"9996","creation_date":"1235047724","6":"1235047724"},{"0":"2535","vim_version":"7.0","1":"7.0","script_version":"0.2","2":"0.2","version_comment":"this is a complete package, containing cca.vim, ctk.vim and snippets files. just :so% it if you hasn't installed cca yet.","3":"this is a complete package, containing cca.vim, ctk.vim and snippets files. just :so% it if you hasn't installed cca yet.","package":"cca.vba","4":"cca.vba","src_id":"9995","5":"9995","creation_date":"1235019087","6":"1235019087"},{"0":"2535","vim_version":"7.0","1":"7.0","script_version":"0.2","2":"0.2","version_comment":"still bugfix, and some new features.\r\n\r\nnow you can add a \"!\" before the tag-command, that means the result of the command may be the new text for next tag.\r\n\r\ne.g: after you enter \"def\",\r\n    <{a:'abc'}> <{a}>\r\nturns to\r\n    abc def\r\nand\r\n    <{a:!\u00e2\u0080\u0098abc'}> <{a}>\r\nturns to\r\n    abc abc","3":"still bugfix, and some new features.\r\n\r\nnow you can add a \"!\" before the tag-command, that means the result of the command may be the new text for next tag.\r\n\r\ne.g: after you enter \"def\",\r\n    <{a:'abc'}> <{a}>\r\nturns to\r\n    abc def\r\nand\r\n    <{a:!\u00e2\u0080\u0098abc'}> <{a}>\r\nturns to\r\n    abc abc","package":"cca.vim","4":"cca.vim","src_id":"9989","5":"9989","creation_date":"1234874393","6":"1234874393"},{"0":"2535","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"the bundles of snippets file. directly converse from the snippetsEmu (http:\/\/www.vim.org\/scripts\/script.php?script_id=1318). so it maybe has many bugs, if it is, please tell me at: http:\/\/code.google.com\/p\/vim-cca\/issues\/list , thank you for use!","3":"the bundles of snippets file. directly converse from the snippetsEmu (http:\/\/www.vim.org\/scripts\/script.php?script_id=1318). so it maybe has many bugs, if it is, please tell me at: http:\/\/code.google.com\/p\/vim-cca\/issues\/list , thank you for use!","package":"cca_bundles.zip","4":"cca_bundles.zip","src_id":"9987","5":"9987","creation_date":"1234873223","6":"1234873223"}]},"2534":{"script_id":"2534","0":"2534","script_name":"d.vim","1":"d.vim","script_type":"ftplugin","2":"ftplugin","summary":"Filetype plugin for D","3":"Filetype plugin for D","description":"Not much is done yet. It has the following features:\r\n- Autoimport. Searches the tags file for the symbol under the cursor and adds import to the module where it is declared. Default keybinding is <LocalLeader>i\r\n- OrganizeImports. Removes duplicates, groups imports by root packages and sorts them alphabetically. It won't break your selective and renamed imports and won't touch versioned imports. Default keybinding is <LocalLeader>o\r\n\r\nTo include libraries in import search put symlinks to them in your project directory so that ctags can find the sources.","4":"Not much is done yet. It has the following features:\r\n- Autoimport. Searches the tags file for the symbol under the cursor and adds import to the module where it is declared. Default keybinding is <LocalLeader>i\r\n- OrganizeImports. Removes duplicates, groups imports by root packages and sorts them alphabetically. It won't break your selective and renamed imports and won't touch versioned imports. Default keybinding is <LocalLeader>o\r\n\r\nTo include libraries in import search put symlinks to them in your project directory so that ctags can find the sources.","install_details":"Unpack to $HOME\/.vim or %HOME%\\vimfiles\r\n\r\nYou'll need patched ctags for it to work. The patch is here: http:\/\/www.prowiki.org\/wiki4d\/wiki.cgi?ReferenceForTools\/ExuberantCtags","5":"Unpack to $HOME\/.vim or %HOME%\\vimfiles\r\n\r\nYou'll need patched ctags for it to work. The patch is here: http:\/\/www.prowiki.org\/wiki4d\/wiki.cgi?ReferenceForTools\/ExuberantCtags","first_name":"Alexander","6":"Alexander","last_name":"Suhoverhov","7":"Suhoverhov","releases":[{"0":"2534","vim_version":"7.0","1":"7.0","script_version":"0.0.1","2":"0.0.1","version_comment":"Initial upload","3":"Initial upload","package":"d-0.0.1.tar.bz2","4":"d-0.0.1.tar.bz2","src_id":"9896","5":"9896","creation_date":"1233515175","6":"1233515175"}]},"2533":{"script_id":"2533","0":"2533","script_name":"muttaliasescomplete.vim","1":"muttaliasescomplete.vim","script_type":"utility","2":"utility","summary":"Omnicompletion for mutt aliases","3":"Omnicompletion for mutt aliases","description":"This script adds an omnicompletion function that gets completion entries from a mutt aliases file. I tested only on GNU\/Linux with vim 7.2, but it should work on other systems.\r\n\r\nPlease send comments, suggestions and patches to \"dotfiles at kb dot ccchl dot de\".","4":"This script adds an omnicompletion function that gets completion entries from a mutt aliases file. I tested only on GNU\/Linux with vim 7.2, but it should work on other systems.\r\n\r\nPlease send comments, suggestions and patches to \"dotfiles at kb dot ccchl dot de\".","install_details":"Edit the following line in script:\r\nlet g:aliases_file = glob('~\/.mutt\/aliases')\r\n\r\nYour .vimrc:\r\nautocmd FileType mail set omnifunc=muttaliasescomplete#Complete\r\nsource path\/to\/muttaliasescomplete.vim","5":"Edit the following line in script:\r\nlet g:aliases_file = glob('~\/.mutt\/aliases')\r\n\r\nYour .vimrc:\r\nautocmd FileType mail set omnifunc=muttaliasescomplete#Complete\r\nsource path\/to\/muttaliasescomplete.vim","first_name":"Karsten","6":"Karsten","last_name":"B","7":"B","releases":[{"0":"2533","vim_version":"7.0","1":"7.0","script_version":"0.2","2":"0.2","version_comment":"Several input files and improved file reading. Thanks to Valentin for the patch!","3":"Several input files and improved file reading. Thanks to Valentin for the patch!","package":"muttaliasescomplete.vim","4":"muttaliasescomplete.vim","src_id":"11299","5":"11299","creation_date":"1251822659","6":"1251822659"},{"0":"2533","vim_version":"7.2","1":"7.2","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"muttaliasescomplete.vim","4":"muttaliasescomplete.vim","src_id":"9895","5":"9895","creation_date":"1233500102","6":"1233500102"}]},"2532":{"script_id":"2532","0":"2532","script_name":"nxc.vim","1":"nxc.vim","script_type":"syntax","2":"syntax","summary":"Syntax highlighter for NXC language on Lego NXT System","3":"Syntax highlighter for NXC language on Lego NXT System","description":"http:\/\/www.csupomona.edu\/~almendez\/research\/robotics\/nxc.html","4":"http:\/\/www.csupomona.edu\/~almendez\/research\/robotics\/nxc.html","install_details":"   1.  Make a directory ~\/.vim\/syntax. \"~\" Refers to your home directory.\r\n   2. Copy nxc.vim from where you downloaded it to into this directory.\r\n   3. Make sure you have \":set syntax\" in your .vimrc file.\r\n   4. Start up Vim and type \":set syntax=nxc\".\r\n   5. Your syntax coloring will now be set for the NXC language for this buffer.","5":"   1.  Make a directory ~\/.vim\/syntax. \"~\" Refers to your home directory.\r\n   2. Copy nxc.vim from where you downloaded it to into this directory.\r\n   3. Make sure you have \":set syntax\" in your .vimrc file.\r\n   4. Start up Vim and type \":set syntax=nxc\".\r\n   5. Your syntax coloring will now be set for the NXC language for this buffer.","first_name":"Anthony","6":"Anthony","last_name":"Mendez","7":"Mendez","releases":[{"0":"2532","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"nxc.vim","4":"nxc.vim","src_id":"9893","5":"9893","creation_date":"1233441344","6":"1233441344"}]},"2531":{"script_id":"2531","0":"2531","script_name":"slimv.vim","1":"slimv.vim","script_type":"utility","2":"utility","summary":"Superior Lisp Interaction Mode for Vim ('SLIME for Vim')","3":"Superior Lisp Interaction Mode for Vim ('SLIME for Vim')","description":"Slimv is a SWANK client for Vim, similarly to SLIME for Emacs. SWANK is a TCP server for Emacs, which runs a Common Lisp, Clojure or Scheme REPL and provides a socket interface for evaluating, compiling, debugging, profiling lisp code. The SWANK server is embedded in Slimv, but you can also use your own SWANK installation.\r\n\r\nSlimv opens the lisp REPL (Read-Eval-Print Loop) inside a Vim buffer. Lisp commands may be entered and executed in the REPL buffer, just as in a regular REPL.\r\n\r\nSlimv supports SLIME's debugger, inspector, profiler, cross reference, arglist, indentation, symbol name completion functions. The script also has a Common Lisp Hyperspec lookup feature and it is able to lookup symbols in the Clojure API, as well as in JavaDoc.\r\n\r\nSlimv comes with Paredit Mode, which is similar to the functionality of paredit.el in Emacs. Paredit Mode tries to maintain the balanced state of matched characters (parenthesis marks, square and curly braces, double quotes). Matched characters are inserted and removed in pairs, also when working with a block of text (well, mostly). Slimv also implements many paredit.el s-expression handling functions, like Split\/Join\/Wrap\/Splice\/Raise. Slurpage and Barfage known from Emacs is also possible but in a different fashion: you don't move the list element in or out of the list, rather you move the opening or closing parenthesis over the element or sub-list.\r\n\r\nPlease visit the Slimv Tutorial for a more complete introduction:\r\nhttps:\/\/kovisoft.bitbucket.io\/tutorial.html\r\n\r\nPlease find the most recent development version in the repository:\r\nhttps:\/\/github.com\/kovisoft\/slimv\r\n\r\nHere follows a list of Slimv commands, any similarity with SLIME's menu is not coincidental. :)\r\n\r\nEdit commands:\r\n    *  Close Form\r\n    *  Complete Symbol\r\n    *  Function Arglist\r\n    *  Paredit Toggle\r\n\r\nEvaluation commands:\r\n    *  Eval Defun\r\n    *  Eval Current Expression\r\n    *  Eval Region\r\n    *  Eval Buffer\r\n    *  Interactive Eval\r\n    *  Undefine Function\r\n\r\nDebug commands:\r\n    *  Macroexpand-1\r\n    *  Macroexpand All\r\n    *  Toggle Trace\r\n    *  Untrace All\r\n    *  Disassemble\r\n    *  Set Breakpoint\r\n    *  Break on Exception\r\n    *  Inspect\r\n    *  Abort\r\n    *  Quit to Toplevel\r\n    *  Continue\r\n    *  Restart Frame\r\n    *  List Threads\r\n    *  Kill Thread\r\n    *  Debug Thread\r\n\r\nCompile commands:\r\n    *  Compile Defun\r\n    *  Compile and Load File\r\n    *  Compile File\r\n    *  Compile Region\r\n\r\nCross Reference commands\r\n    *  Who Calls\r\n    *  Who References\r\n    *  Who Sets\r\n    *  Who Binds\r\n    *  Who Macroexpands\r\n    *  Who Specializes\r\n    *  List Callers\r\n    *  List Callees\r\n\r\nProfile commands:\r\n    *  Toggle Profile\r\n    *  Profile by Substring\r\n    *  Unprofile All\r\n    *  Show Profiled\r\n    *  Profile Report\r\n    *  Profile Reset\r\n\r\nDocumentation commands:\r\n    *  Describe Symbol\r\n    *  Apropos\r\n    *  Hyperspec\r\n    *  Generate Tags\r\n\r\nREPL commands:\r\n    *  Connect to Server\r\n    *  Interrupt Lisp Process\r\n    *  Send Input\r\n    *  Close and Send Input\r\n    *  Set Package\r\n    *  Previous Input\r\n    *  Next Input\r\n    *  Clear REPL\r\n\r\nFor more information see the included documentation.","4":"Slimv is a SWANK client for Vim, similarly to SLIME for Emacs. SWANK is a TCP server for Emacs, which runs a Common Lisp, Clojure or Scheme REPL and provides a socket interface for evaluating, compiling, debugging, profiling lisp code. The SWANK server is embedded in Slimv, but you can also use your own SWANK installation.\r\n\r\nSlimv opens the lisp REPL (Read-Eval-Print Loop) inside a Vim buffer. Lisp commands may be entered and executed in the REPL buffer, just as in a regular REPL.\r\n\r\nSlimv supports SLIME's debugger, inspector, profiler, cross reference, arglist, indentation, symbol name completion functions. The script also has a Common Lisp Hyperspec lookup feature and it is able to lookup symbols in the Clojure API, as well as in JavaDoc.\r\n\r\nSlimv comes with Paredit Mode, which is similar to the functionality of paredit.el in Emacs. Paredit Mode tries to maintain the balanced state of matched characters (parenthesis marks, square and curly braces, double quotes). Matched characters are inserted and removed in pairs, also when working with a block of text (well, mostly). Slimv also implements many paredit.el s-expression handling functions, like Split\/Join\/Wrap\/Splice\/Raise. Slurpage and Barfage known from Emacs is also possible but in a different fashion: you don't move the list element in or out of the list, rather you move the opening or closing parenthesis over the element or sub-list.\r\n\r\nPlease visit the Slimv Tutorial for a more complete introduction:\r\nhttps:\/\/kovisoft.bitbucket.io\/tutorial.html\r\n\r\nPlease find the most recent development version in the repository:\r\nhttps:\/\/github.com\/kovisoft\/slimv\r\n\r\nHere follows a list of Slimv commands, any similarity with SLIME's menu is not coincidental. :)\r\n\r\nEdit commands:\r\n    *  Close Form\r\n    *  Complete Symbol\r\n    *  Function Arglist\r\n    *  Paredit Toggle\r\n\r\nEvaluation commands:\r\n    *  Eval Defun\r\n    *  Eval Current Expression\r\n    *  Eval Region\r\n    *  Eval Buffer\r\n    *  Interactive Eval\r\n    *  Undefine Function\r\n\r\nDebug commands:\r\n    *  Macroexpand-1\r\n    *  Macroexpand All\r\n    *  Toggle Trace\r\n    *  Untrace All\r\n    *  Disassemble\r\n    *  Set Breakpoint\r\n    *  Break on Exception\r\n    *  Inspect\r\n    *  Abort\r\n    *  Quit to Toplevel\r\n    *  Continue\r\n    *  Restart Frame\r\n    *  List Threads\r\n    *  Kill Thread\r\n    *  Debug Thread\r\n\r\nCompile commands:\r\n    *  Compile Defun\r\n    *  Compile and Load File\r\n    *  Compile File\r\n    *  Compile Region\r\n\r\nCross Reference commands\r\n    *  Who Calls\r\n    *  Who References\r\n    *  Who Sets\r\n    *  Who Binds\r\n    *  Who Macroexpands\r\n    *  Who Specializes\r\n    *  List Callers\r\n    *  List Callees\r\n\r\nProfile commands:\r\n    *  Toggle Profile\r\n    *  Profile by Substring\r\n    *  Unprofile All\r\n    *  Show Profiled\r\n    *  Profile Report\r\n    *  Profile Reset\r\n\r\nDocumentation commands:\r\n    *  Describe Symbol\r\n    *  Apropos\r\n    *  Hyperspec\r\n    *  Generate Tags\r\n\r\nREPL commands:\r\n    *  Connect to Server\r\n    *  Interrupt Lisp Process\r\n    *  Send Input\r\n    *  Close and Send Input\r\n    *  Set Package\r\n    *  Previous Input\r\n    *  Next Input\r\n    *  Clear REPL\r\n\r\nFor more information see the included documentation.","install_details":"Extract the zip archive into your vimfiles or runtime directory.\r\n\r\nSlimv works on Windows, Linux and Mac OS X (via Terminal.app), Cygwin is supported. The script requires the following programs installed on your system:\r\n    *  Vim with Python feature enabled\r\n    *  Python (must be the same Python version that was Vim compiled against)\r\n    *  Lisp (any Common Lisp with SLIME support) or Clojure or MIT Scheme (Linux only)\r\n\r\nVim's Python version can be identified with the :ver command, look for the -DDYNAMIC_PYTHON_DLL=\\\"pythonXX\\\" string (if you have it). Another way of determining Vim's Python version:\r\n\r\n:python import sys; print(sys.version)\r\n\r\nSlimv tries to autodetect your Lisp\/Clojure\/Slime installation directories. If it fails to determine the correct directories, then you need to enter the command to start the SWANK server into your vimrc file.\r\n\r\nLinux example:\r\n    let g:slimv_swank_cmd = '! xterm -e sbcl --load \/usr\/share\/common-lisp\/source\/slime\/start-swank.lisp &'\r\n\r\nWindows example:\r\n    let g:slimv_swank_cmd = '!start \"c:\/Program Files\/Lisp Cabinet\/bin\/ccl\/wx86cl.exe\" -l \"c:\/Program Files\/Lisp Cabinet\/site\/lisp\/slime\/start-swank.lisp\"'\r\n\r\nMac OS X example:\r\n    let g:slimv_swank_cmd = '!osascript -e \"tell application \\\"Terminal\\\" to do script \\\"sbcl --load ~\/.vim\/slime\/start-swank.lisp\\\"\"'\r\n\r\nFor Clojure use the g:slimv_swank_clojure option, e.g.:\r\n    let g:slimv_swank_clojure = '! xterm -e lein swank &' \r\n\r\n\r\n- For pure text-based console without XTerm\r\n\r\nIf you only have `SSH` and can not use `XTerm`, you can use `tmux` or `screen` instead.\r\n\r\nLinux example with `tmux`:\r\n    let g:slimv_swank_cmd = '! tmux new-window -d -n REPL-SBCL \"sbcl --load ~\/.vim\/bundle\/slimv\/slime\/start-swank.lisp\"'\r\n\r\nLinux example with `screen`:\r\n    let g:slimv_swank_cmd = '! screen -d -m -t REPL-SBCL sbcl --load ~\/.vim\/bundle\/slimv\/slime\/start-swank.lisp'\r\n\r\nMac OS X example with `tmux`:\r\n    let g:slimv_swank_cmd = '!osascript -e \"! tmux new-window -d -n REPL-SBCL \"sbcl --load ~\/.vim\/bundle\/slimv\/slime\/start-swank.lisp\"'\r\n\r\n\r\nSee the included documentation for more complete installation and customization instructions.","5":"Extract the zip archive into your vimfiles or runtime directory.\r\n\r\nSlimv works on Windows, Linux and Mac OS X (via Terminal.app), Cygwin is supported. The script requires the following programs installed on your system:\r\n    *  Vim with Python feature enabled\r\n    *  Python (must be the same Python version that was Vim compiled against)\r\n    *  Lisp (any Common Lisp with SLIME support) or Clojure or MIT Scheme (Linux only)\r\n\r\nVim's Python version can be identified with the :ver command, look for the -DDYNAMIC_PYTHON_DLL=\\\"pythonXX\\\" string (if you have it). Another way of determining Vim's Python version:\r\n\r\n:python import sys; print(sys.version)\r\n\r\nSlimv tries to autodetect your Lisp\/Clojure\/Slime installation directories. If it fails to determine the correct directories, then you need to enter the command to start the SWANK server into your vimrc file.\r\n\r\nLinux example:\r\n    let g:slimv_swank_cmd = '! xterm -e sbcl --load \/usr\/share\/common-lisp\/source\/slime\/start-swank.lisp &'\r\n\r\nWindows example:\r\n    let g:slimv_swank_cmd = '!start \"c:\/Program Files\/Lisp Cabinet\/bin\/ccl\/wx86cl.exe\" -l \"c:\/Program Files\/Lisp Cabinet\/site\/lisp\/slime\/start-swank.lisp\"'\r\n\r\nMac OS X example:\r\n    let g:slimv_swank_cmd = '!osascript -e \"tell application \\\"Terminal\\\" to do script \\\"sbcl --load ~\/.vim\/slime\/start-swank.lisp\\\"\"'\r\n\r\nFor Clojure use the g:slimv_swank_clojure option, e.g.:\r\n    let g:slimv_swank_clojure = '! xterm -e lein swank &' \r\n\r\n\r\n- For pure text-based console without XTerm\r\n\r\nIf you only have `SSH` and can not use `XTerm`, you can use `tmux` or `screen` instead.\r\n\r\nLinux example with `tmux`:\r\n    let g:slimv_swank_cmd = '! tmux new-window -d -n REPL-SBCL \"sbcl --load ~\/.vim\/bundle\/slimv\/slime\/start-swank.lisp\"'\r\n\r\nLinux example with `screen`:\r\n    let g:slimv_swank_cmd = '! screen -d -m -t REPL-SBCL sbcl --load ~\/.vim\/bundle\/slimv\/slime\/start-swank.lisp'\r\n\r\nMac OS X example with `tmux`:\r\n    let g:slimv_swank_cmd = '!osascript -e \"! tmux new-window -d -n REPL-SBCL \"sbcl --load ~\/.vim\/bundle\/slimv\/slime\/start-swank.lisp\"'\r\n\r\n\r\nSee the included documentation for more complete installation and customization instructions.","first_name":"Tamas","6":"Tamas","last_name":"Kovacs","7":"Kovacs","releases":[{"0":"2531","vim_version":"7.0","1":"7.0","script_version":"0.9.13","2":"0.9.13","version_comment":"This is a huge update after more than 3 years. For a detailed list of changes please visit the changelog section of the documentation.","3":"This is a huge update after more than 3 years. For a detailed list of changes please visit the changelog section of the documentation.","package":"slimv0913.zip","4":"slimv0913.zip","src_id":"25041","5":"25041","creation_date":"1489937155","6":"1489937155"},{"0":"2531","vim_version":"7.0","1":"7.0","script_version":"0.9.12","2":"0.9.12","version_comment":"Added support for the R language via swank-R (by Philipp Marek).\r\nTest form for SlimvEvalTestExp() may wrap the selected s-expression.\r\nAdded Shift+Tab mapping for cycling backwards in the completion popup menu.\r\nUser defined REPL buffer name may contain some special characters.\r\nPass port number to the swank server in SWANK_PORT environent variable on Linux (by Glen Gibb and Federico Churca-Torrusio).\r\nAutodetect wx86cl64.exe (Clozure CL) on 64 bit Windows.\r\nAdded applescript support for starting swank through iTerm (by Seth Price).\r\nAdd Racket support for delimiter '[]' and '{}' (by Jimmy Lu).\r\nBugfixes: If the user started a normal mode command prefixed with a count, then the count was cleared by the REPL refresh timer.\r\nCursorHold trigger ignore mappings to prevent collisions with other plugins.\r\nPreselect function name before starting swank server in the Disassemble command.\r\nDo not append '>' at the prompt if it already ends with it.\r\nPackage name not found when 'noignorecase' was set.\r\nParedit ,< and ,> when 'whichwrap' contains 'h' and 'l'.\r\nKeep multi-line SLDB abort messages commented all throughout (by Federico Churca-Torrusio).\r\nPrevent call to frame-call on AllegroCL (by Robert Kerr).\r\nTag lookup (Ctrl+]) added garbage to symbol name.\r\nParsing arrays (and other prefixed forms) returned from the swank server.\r\nPrevent accidental multiple registration of slimv autocommands.\r\nDisable autocommands for the REPL update, make sure 'updatetime' is not too low.","3":"Added support for the R language via swank-R (by Philipp Marek).\r\nTest form for SlimvEvalTestExp() may wrap the selected s-expression.\r\nAdded Shift+Tab mapping for cycling backwards in the completion popup menu.\r\nUser defined REPL buffer name may contain some special characters.\r\nPass port number to the swank server in SWANK_PORT environent variable on Linux (by Glen Gibb and Federico Churca-Torrusio).\r\nAutodetect wx86cl64.exe (Clozure CL) on 64 bit Windows.\r\nAdded applescript support for starting swank through iTerm (by Seth Price).\r\nAdd Racket support for delimiter '[]' and '{}' (by Jimmy Lu).\r\nBugfixes: If the user started a normal mode command prefixed with a count, then the count was cleared by the REPL refresh timer.\r\nCursorHold trigger ignore mappings to prevent collisions with other plugins.\r\nPreselect function name before starting swank server in the Disassemble command.\r\nDo not append '>' at the prompt if it already ends with it.\r\nPackage name not found when 'noignorecase' was set.\r\nParedit ,< and ,> when 'whichwrap' contains 'h' and 'l'.\r\nKeep multi-line SLDB abort messages commented all throughout (by Federico Churca-Torrusio).\r\nPrevent call to frame-call on AllegroCL (by Robert Kerr).\r\nTag lookup (Ctrl+]) added garbage to symbol name.\r\nParsing arrays (and other prefixed forms) returned from the swank server.\r\nPrevent accidental multiple registration of slimv autocommands.\r\nDisable autocommands for the REPL update, make sure 'updatetime' is not too low.","package":"slimv0912.zip","4":"slimv0912.zip","src_id":"21253","5":"21253","creation_date":"1388314789","6":"1388314789"},{"0":"2531","vim_version":"7.0","1":"7.0","script_version":"0.9.11","2":"0.9.11","version_comment":"Entering some text in REPL command history, then pressing <Up>\/<Down> searches for matching lines only. Changed lisp syntax for #\\( and #\\) to \"string\". Handle three or more windows layout: assign an id to each slimv window, reuse slimv windows. Support for built-in or third party clojure syntax file. Indent with tabs when 'noexpandtab' set after file is loaded. Added options g:paredit_disable_clojure, g:paredit_disable_lisp, g:paredit_disable_scheme. Added repeat.vim support to many Paredit modification actions (by Logan Campbell). Returning cursor to start position after Paredit \" wrap (by Logan Campbell). Paredit: do not insert newline if item is selected in completion popup menu by pressing <CR>. Paredit: delete into the \"*\" register when option clipboard=unnamed. Paredit: handle #\"\" regexp syntax definition also when searching for paren matches. Defined <Leader>- mapping (Clear-REPL) for all source buffers. Escape double quotes in text input into (read) in the REPL buffer. Bugfixes: Indentation after multi-line string. Paredit Wrap accomodates strings (thanks to Colin Jones). Fixed error messages when compiling or describing before connected to swank server. Fixed some indentation issues with multi-line arguments involved. Fixing buffer confusion when filename contains 'repl'. Don't move cursor for Paredit v) when selection mode is inclusive (by John Szakmeister). Syntax highlighting in clojure REPL for forms containing \">\" in the function name.","3":"Entering some text in REPL command history, then pressing <Up>\/<Down> searches for matching lines only. Changed lisp syntax for #\\( and #\\) to \"string\". Handle three or more windows layout: assign an id to each slimv window, reuse slimv windows. Support for built-in or third party clojure syntax file. Indent with tabs when 'noexpandtab' set after file is loaded. Added options g:paredit_disable_clojure, g:paredit_disable_lisp, g:paredit_disable_scheme. Added repeat.vim support to many Paredit modification actions (by Logan Campbell). Returning cursor to start position after Paredit \" wrap (by Logan Campbell). Paredit: do not insert newline if item is selected in completion popup menu by pressing <CR>. Paredit: delete into the \"*\" register when option clipboard=unnamed. Paredit: handle #\"\" regexp syntax definition also when searching for paren matches. Defined <Leader>- mapping (Clear-REPL) for all source buffers. Escape double quotes in text input into (read) in the REPL buffer. Bugfixes: Indentation after multi-line string. Paredit Wrap accomodates strings (thanks to Colin Jones). Fixed error messages when compiling or describing before connected to swank server. Fixed some indentation issues with multi-line arguments involved. Fixing buffer confusion when filename contains 'repl'. Don't move cursor for Paredit v) when selection mode is inclusive (by John Szakmeister). Syntax highlighting in clojure REPL for forms containing \">\" in the function name.","package":"slimv0911.zip","4":"slimv0911.zip","src_id":"20777","5":"20777","creation_date":"1378761529","6":"1378761529"},{"0":"2531","vim_version":"7.0","1":"7.0","script_version":"0.9.10","2":"0.9.10","version_comment":"Replaced 'readonly' flag with 'nomodifiable' for SLDB, Inspect, Threads buffers. Restore window and buffer if SLDB is activated during completion. Allow using Slimv and VimClojure (or other clojure filetype plugin) together. Added Restart-Frame command (thanks to Philipp Marek). Added defn- to clojure keywords (thanks to David Soria Parra). Paredit initialization on filetype instead of filename extension. Do not permanently set 'iskeyword' in paredit.vim. Paredit: added '^' macro prefix, treat #_(...) type of clojure comments as regular forms, handle VimClojure's #\"\" regexp syntax definition. It is now possible to remove plugin\/paredit.vim. Bugfixes: Fixed missing variable error message. REPL prompt position corruption problems. Cursor positioning problems when displaying arglist. Paredit 'cc', 'Vc' did not delete line. Paredit 'd', 'c', 'vc', 'cW' cursor positioning problems. Paredit 'C' extra whitespace and trailing \". Reset indent after paredit 'cc'. Paredit 'dd', ',>' EOL problem. paredit indentation when 'indentexpr' takes no argument (thanks to Tim Pope). Keep cursor inside \"\" when deleting over trailing \" via paredit 'cW', 'C', etc. Use &ft instead of SlimvGetFiletype() in paredit.vim.","3":"Replaced 'readonly' flag with 'nomodifiable' for SLDB, Inspect, Threads buffers. Restore window and buffer if SLDB is activated during completion. Allow using Slimv and VimClojure (or other clojure filetype plugin) together. Added Restart-Frame command (thanks to Philipp Marek). Added defn- to clojure keywords (thanks to David Soria Parra). Paredit initialization on filetype instead of filename extension. Do not permanently set 'iskeyword' in paredit.vim. Paredit: added '^' macro prefix, treat #_(...) type of clojure comments as regular forms, handle VimClojure's #\"\" regexp syntax definition. It is now possible to remove plugin\/paredit.vim. Bugfixes: Fixed missing variable error message. REPL prompt position corruption problems. Cursor positioning problems when displaying arglist. Paredit 'cc', 'Vc' did not delete line. Paredit 'd', 'c', 'vc', 'cW' cursor positioning problems. Paredit 'C' extra whitespace and trailing \". Reset indent after paredit 'cc'. Paredit 'dd', ',>' EOL problem. paredit indentation when 'indentexpr' takes no argument (thanks to Tim Pope). Keep cursor inside \"\" when deleting over trailing \" via paredit 'cW', 'C', etc. Use &ft instead of SlimvGetFiletype() in paredit.vim.","package":"slimv0910.zip","4":"slimv0910.zip","src_id":"19750","5":"19750","creation_date":"1364923339","6":"1364923339"},{"0":"2531","vim_version":"7.0","1":"7.0","script_version":"0.9.9","2":"0.9.9","version_comment":"Added Paredit functions to Slimv menu (thanks to Conrad Schuler). Inspector: Use the same package when pressing [--more--], speeding up multi-part object processing, save\/restore cursor position for previously visited pages. ,rc was doubly mapped, use ,- for REPL Clear. Autodetect ritz-swank. Added Break-on-Exception function for ritz-swank. Added minibuffer operations, this enables [set value] in Inspector. Added smartjumping for Clojure (thanks to dgrnbrg on bitbucket.org). Disable indenting on \"set noautoindent\". Pass python output to Vim script in variable instead of redirecting stdout (hopefully solves 64-bit MacVim problems). Handle [] and {} delimiters in Scheme like in Clojure. Paredit: ignore (, [, or { when preceded by \\. Bugfixes: Arglist on Space after pressing 'I' in visual block mode. Indentation after multi-line subform. Problems with finding function name for arglist. Corruption when pasting large text into console Vim. Cursor positioning in REPL buffer when virtualedit=all. Multi-line entry name parsing in Inspector.","3":"Added Paredit functions to Slimv menu (thanks to Conrad Schuler). Inspector: Use the same package when pressing [--more--], speeding up multi-part object processing, save\/restore cursor position for previously visited pages. ,rc was doubly mapped, use ,- for REPL Clear. Autodetect ritz-swank. Added Break-on-Exception function for ritz-swank. Added minibuffer operations, this enables [set value] in Inspector. Added smartjumping for Clojure (thanks to dgrnbrg on bitbucket.org). Disable indenting on \"set noautoindent\". Pass python output to Vim script in variable instead of redirecting stdout (hopefully solves 64-bit MacVim problems). Handle [] and {} delimiters in Scheme like in Clojure. Paredit: ignore (, [, or { when preceded by \\. Bugfixes: Arglist on Space after pressing 'I' in visual block mode. Indentation after multi-line subform. Problems with finding function name for arglist. Corruption when pasting large text into console Vim. Cursor positioning in REPL buffer when virtualedit=all. Multi-line entry name parsing in Inspector.","package":"slimv099.zip","4":"slimv099.zip","src_id":"19000","5":"19000","creation_date":"1353400022","6":"1353400022"},{"0":"2531","vim_version":"7.0","1":"7.0","script_version":"0.9.8","2":"0.9.8","version_comment":"Added autodetection for 'ccl'. Delete empty lines when re-gathering Electric Returns. Inspector: put multiple items in one line (like in Slime), highlight selectable parts and actions, hide item id-s, display \"path\" of inspected object. Don't extend s-expression with prefix when macroexpanding. Don't evaluate or compile the REPL buffer. Added device to the path when loading pretty printer patches for SBCL (thanks to Andrew Lyon). Added option g:slimv_repl_simple_eval and Electric Return for REPL buffer. Print arglist when pressing Space after closing parens or double quotes, also when pressing Enter. Added \"Clear REPL\" entry to the REPL menu (mapped to <Leader>-). Paredit: special handling of cw, cb, ciw, caw supporting repeat ('.'). Do not describe empty symbol. Prefer selecting symbol to the left when cursor is on whitespace. Added \".\" character to iskeyword for Lisp. Removed \".\" when selecting symbol for completion for Clojure. Increased fuzzy completion limit. Bugfixes: Find package\/namespace when current form is in a fold. PareditToggle ckecks if buffer was registered for Paredit. Electric Return re-gathering at end of line with no virtualedit. Extra character at the end of selection using 'v('. Garbage upon pressing ')' or Enter in completion popup. Paredit 'x' at end of line when 'whichwrap' includes h,l. Arglist sometimes not displayed. Paredit Wrap when line ends in a multibyte character (thanks to Sung Pae).","3":"Added autodetection for 'ccl'. Delete empty lines when re-gathering Electric Returns. Inspector: put multiple items in one line (like in Slime), highlight selectable parts and actions, hide item id-s, display \"path\" of inspected object. Don't extend s-expression with prefix when macroexpanding. Don't evaluate or compile the REPL buffer. Added device to the path when loading pretty printer patches for SBCL (thanks to Andrew Lyon). Added option g:slimv_repl_simple_eval and Electric Return for REPL buffer. Print arglist when pressing Space after closing parens or double quotes, also when pressing Enter. Added \"Clear REPL\" entry to the REPL menu (mapped to <Leader>-). Paredit: special handling of cw, cb, ciw, caw supporting repeat ('.'). Do not describe empty symbol. Prefer selecting symbol to the left when cursor is on whitespace. Added \".\" character to iskeyword for Lisp. Removed \".\" when selecting symbol for completion for Clojure. Increased fuzzy completion limit. Bugfixes: Find package\/namespace when current form is in a fold. PareditToggle ckecks if buffer was registered for Paredit. Electric Return re-gathering at end of line with no virtualedit. Extra character at the end of selection using 'v('. Garbage upon pressing ')' or Enter in completion popup. Paredit 'x' at end of line when 'whichwrap' includes h,l. Arglist sometimes not displayed. Paredit Wrap when line ends in a multibyte character (thanks to Sung Pae).","package":"slimv098.zip","4":"slimv098.zip","src_id":"18425","5":"18425","creation_date":"1345306538","6":"1345306538"},{"0":"2531","vim_version":"7.0","1":"7.0","script_version":"0.9.7","2":"0.9.7","version_comment":"Keep cursor position on expanding [--more--] in the Inspector. Added [--all---] to Inspector for fetching all parts. Don't explicitly check for pythonXX.dll, rely on has('python'). Require 'swank-repl' for slime version above 2011-12-04 in case contribs are disabled. Identify VimClojure REPL prompt position for paredit (thanks to David Greenberg). Paredit: added <leader><Up> for Splice-killing-backward, <leader><Down> for Splice-killing-forward, <leader>I for Raise. Paredit: added 'Electric Return' feature and new option g:paredit_electric_return. Increased the distance to search for the defun start to 200 lines. Bugfixes: Positioning the cursor at the end of REPL prompt in insert mode. Handle restart\/frame number above 999 (thanks to Philipp Marek). Form selection when cursor is next to the opening paren. Indentation of multi-line strings. Indentation of lines with multi-byte characters. Cursor movement while indenting.","3":"Keep cursor position on expanding [--more--] in the Inspector. Added [--all---] to Inspector for fetching all parts. Don't explicitly check for pythonXX.dll, rely on has('python'). Require 'swank-repl' for slime version above 2011-12-04 in case contribs are disabled. Identify VimClojure REPL prompt position for paredit (thanks to David Greenberg). Paredit: added <leader><Up> for Splice-killing-backward, <leader><Down> for Splice-killing-forward, <leader>I for Raise. Paredit: added 'Electric Return' feature and new option g:paredit_electric_return. Increased the distance to search for the defun start to 200 lines. Bugfixes: Positioning the cursor at the end of REPL prompt in insert mode. Handle restart\/frame number above 999 (thanks to Philipp Marek). Form selection when cursor is next to the opening paren. Indentation of multi-line strings. Indentation of lines with multi-byte characters. Cursor movement while indenting.","package":"slimv097.zip","4":"slimv097.zip","src_id":"18062","5":"18062","creation_date":"1338321279","6":"1338321279"},{"0":"2531","vim_version":"7.0","1":"7.0","script_version":"0.9.6","2":"0.9.6","version_comment":"Perform indenting when Tab pressed on whitespace. Added support for newer swank message length counting in bytes. Updated Lisp swank server to version 2012-03-06. Updated Clojure API reference to version 1.3. Identify .cljs files as Clojure type. Enable g:slimv_repl_syntax by default. Restart parenthesis highlighting at each REPL prompt. Scheme: eval buffer and region in a (begin ...) block. Added option g:scheme_builtin_swank for enabling MIT scheme's built-in swank server. Added syntax highlight for Scheme quoted symbol. Keep SLDB buffer if swank stays in debugger upon selecting a restart. When reconnecting the swank server wait for disconnection first. Fixed REPL buffer slowdown caused by re-assigning autocommands. Fixed detection of string and comment when no syntax loaded. Fixed Scheme syntax highlight problems in the REPL buffer. Call :frame-source-location and :frame-call only if swank supports them.","3":"Perform indenting when Tab pressed on whitespace. Added support for newer swank message length counting in bytes. Updated Lisp swank server to version 2012-03-06. Updated Clojure API reference to version 1.3. Identify .cljs files as Clojure type. Enable g:slimv_repl_syntax by default. Restart parenthesis highlighting at each REPL prompt. Scheme: eval buffer and region in a (begin ...) block. Added option g:scheme_builtin_swank for enabling MIT scheme's built-in swank server. Added syntax highlight for Scheme quoted symbol. Keep SLDB buffer if swank stays in debugger upon selecting a restart. When reconnecting the swank server wait for disconnection first. Fixed REPL buffer slowdown caused by re-assigning autocommands. Fixed detection of string and comment when no syntax loaded. Fixed Scheme syntax highlight problems in the REPL buffer. Call :frame-source-location and :frame-call only if swank supports them.","package":"slimv096.zip","4":"slimv096.zip","src_id":"17697","5":"17697","creation_date":"1333212281","6":"1333212281"},{"0":"2531","vim_version":"7.0","1":"7.0","script_version":"0.9.5","2":"0.9.5","version_comment":"Use correct SLDB level when invoking restart. Autodetect tmux session on Linux (thanks to Brett Kosinski). Enable syntax only once to avoid reload of syntax plugins. Added option g:slimv_browser_cmd_suffix. Skip syntax and indent file for disabled filetypes. Check the presence of X on Linux. Indentation fixes: keywords, gap after '(', defsystem, defmacro, symbol-macrolet. Use winsaveview()\/winrestview() for remembering current view when moving around (e.g. searching for package). Find package for arglist and completion. Ignore mapleader when it's <Space>. Print SLDB error description also into the REPL buffer. Evaluate keyword if using Eval-Defun outside of s-expression. Disable unsupported swank features for Scheme. Bugfixes: Paredit 'cw' at the end of line. Omit REPL prompt from Eval-Defun and Eval-Expression. Printing of '\\n' and other escaped characters. Paredit delete and put corrupted the \"0 register.","3":"Use correct SLDB level when invoking restart. Autodetect tmux session on Linux (thanks to Brett Kosinski). Enable syntax only once to avoid reload of syntax plugins. Added option g:slimv_browser_cmd_suffix. Skip syntax and indent file for disabled filetypes. Check the presence of X on Linux. Indentation fixes: keywords, gap after '(', defsystem, defmacro, symbol-macrolet. Use winsaveview()\/winrestview() for remembering current view when moving around (e.g. searching for package). Find package for arglist and completion. Ignore mapleader when it's <Space>. Print SLDB error description also into the REPL buffer. Evaluate keyword if using Eval-Defun outside of s-expression. Disable unsupported swank features for Scheme. Bugfixes: Paredit 'cw' at the end of line. Omit REPL prompt from Eval-Defun and Eval-Expression. Printing of '\\n' and other escaped characters. Paredit delete and put corrupted the \"0 register.","package":"slimv095.zip","4":"slimv095.zip","src_id":"17579","5":"17579","creation_date":"1331379693","6":"1331379693"},{"0":"2531","vim_version":"7.0","1":"7.0","script_version":"0.9.4","2":"0.9.4","version_comment":"Added highlighting of square and curly brackets for Clojure. Added options to disable Slimv for specific filetypes: g:slimv_disable_clojure, g:slimv_disable_lisp, g:slimv_disable_scheme. Added option g:slimv_indent_keylists (thanks to Andrew Smirnoff). Added \"set hidden\" for safe switching of modified buffers. Added Help to Inspect and Threads buffers. Evaluate register contents if Eval-Region prefixed by [\"x]. Store form in register if Eval-Defun or Eval-Exp prefixed by [\"x]. Increased timeout for :create-repl. Stay in REPL buffer if Macroexpand performed in REPL. Search for either (in-ns) or (ns) for Clojure, remove quote character from namespace name. Added SlimvEvalTestDefun() and SlimvEvalTestExp() for immediate testing of the form(s) being evaluated. Bugfixes: Various indentation issues (function name is a subform, let, let*, do, defpackage, defsystem, and [] for Clojure). Eval-Range problem in visual mode. SLDB parsing problem with newlines in description of restarts. REPL autoscroll incidentally stopping (thanks to Andrew Lyon). Added some index out of range checks (thanks to Philipp Marek).","3":"Added highlighting of square and curly brackets for Clojure. Added options to disable Slimv for specific filetypes: g:slimv_disable_clojure, g:slimv_disable_lisp, g:slimv_disable_scheme. Added option g:slimv_indent_keylists (thanks to Andrew Smirnoff). Added \"set hidden\" for safe switching of modified buffers. Added Help to Inspect and Threads buffers. Evaluate register contents if Eval-Region prefixed by [\"x]. Store form in register if Eval-Defun or Eval-Exp prefixed by [\"x]. Increased timeout for :create-repl. Stay in REPL buffer if Macroexpand performed in REPL. Search for either (in-ns) or (ns) for Clojure, remove quote character from namespace name. Added SlimvEvalTestDefun() and SlimvEvalTestExp() for immediate testing of the form(s) being evaluated. Bugfixes: Various indentation issues (function name is a subform, let, let*, do, defpackage, defsystem, and [] for Clojure). Eval-Range problem in visual mode. SLDB parsing problem with newlines in description of restarts. REPL autoscroll incidentally stopping (thanks to Andrew Lyon). Added some index out of range checks (thanks to Philipp Marek).","package":"slimv094.zip","4":"slimv094.zip","src_id":"17305","5":"17305","creation_date":"1327335317","6":"1327335317"},{"0":"2531","vim_version":"7.0","1":"7.0","script_version":"0.9.3","2":"0.9.3","version_comment":"Start Swank server in virtual terminal when running in GNU screen on Linux (thanks to Oleg Terenchuk). Reuse a window for slimv also when there are three or more windows open. Don't go to end of REPL buffer if user moved the cursor away from EOF. Use xdg-open for default browser in Linux. Removed option g:slimv_python. Added option g:slimv_repl_max_len for limiting the number of lines in the REPL buffer. Added option g:slimv_preferred to choose preferred lisp implementation. Query additional parts of big inspected object upon pressing Enter on [--more--]. Thread List is displayed and handled in a separate Threads buffer. Bugfixes: Window navigation problems between source\/REPL\/SLDB\/etc. Error messages when Swank server window is closed. Return control to vim after starting browser defined by g:slimv_browser_cmd. Fixed indentation of arguments before &body argument. Autocomplete for dotted package\/namespace names. Indentation of aif.","3":"Start Swank server in virtual terminal when running in GNU screen on Linux (thanks to Oleg Terenchuk). Reuse a window for slimv also when there are three or more windows open. Don't go to end of REPL buffer if user moved the cursor away from EOF. Use xdg-open for default browser in Linux. Removed option g:slimv_python. Added option g:slimv_repl_max_len for limiting the number of lines in the REPL buffer. Added option g:slimv_preferred to choose preferred lisp implementation. Query additional parts of big inspected object upon pressing Enter on [--more--]. Thread List is displayed and handled in a separate Threads buffer. Bugfixes: Window navigation problems between source\/REPL\/SLDB\/etc. Error messages when Swank server window is closed. Return control to vim after starting browser defined by g:slimv_browser_cmd. Fixed indentation of arguments before &body argument. Autocomplete for dotted package\/namespace names. Indentation of aif.","package":"slimv093.zip","4":"slimv093.zip","src_id":"17107","5":"17107","creation_date":"1324644584","6":"1324644584"},{"0":"2531","vim_version":"7.0","1":"7.0","script_version":"0.9.2","2":"0.9.2","version_comment":"Added option g:swank_log to enable swank debug log. Added options g:slimv_repl_name, g:slimv_sldb_name, g:slimv_inspect_name. Added option g:slimv_indent_maxlines. Changed Debug-Thread mapping to <leader>dT (g:slimv_keybindings=2) due to conflict with Generate-Tags. Label thread ID in thread list (by Philipp Marek). Set balloonexpr for all buffers (thanks to Philipp Marek). Connect swank server when needed instead of printing an error message (by Philipp Marek). Set expandtab for lisp and clojure files. Kill-Thread kills all threads in the selected range (by Philipp Marek). Bugfixes: Added missing parts of Set-Breakpoint introduced in 0.9.1. Test source lookup (upon pressing Enter) before testing fold toggle in SLDB (by Philipp Marek). Indentation of flet, labels, macrolet. Kill-Thread now really kills thread (by Philipp Marek). Inspect gensyms in frame (by Philipp Marek).","3":"Added option g:swank_log to enable swank debug log. Added options g:slimv_repl_name, g:slimv_sldb_name, g:slimv_inspect_name. Added option g:slimv_indent_maxlines. Changed Debug-Thread mapping to <leader>dT (g:slimv_keybindings=2) due to conflict with Generate-Tags. Label thread ID in thread list (by Philipp Marek). Set balloonexpr for all buffers (thanks to Philipp Marek). Connect swank server when needed instead of printing an error message (by Philipp Marek). Set expandtab for lisp and clojure files. Kill-Thread kills all threads in the selected range (by Philipp Marek). Bugfixes: Added missing parts of Set-Breakpoint introduced in 0.9.1. Test source lookup (upon pressing Enter) before testing fold toggle in SLDB (by Philipp Marek). Indentation of flet, labels, macrolet. Kill-Thread now really kills thread (by Philipp Marek). Inspect gensyms in frame (by Philipp Marek).","package":"slimv092.zip","4":"slimv092.zip","src_id":"16821","5":"16821","creation_date":"1320671160","6":"1320671160"},{"0":"2531","vim_version":"7.0","1":"7.0","script_version":"0.9.1","2":"0.9.1","version_comment":"Improved frame number identification in SLDB buffer. Moved frame source location above frame locals in SLDB. Fold frame source location if more than 2 lines. Inspect-In-Frame: preselect symbol under cursor only in variable lines, open Inspector in the other window. Improved XRef file location parsing. Use current paragraph when no range set for Eval-Region and Compile-Region. Added option g:slimv_sldb_wrap, do not set wrap for source buffers. Added Set-Breakpoint command mapped to <leader>B (thanks to Philipp Marek), changed Profile-By-Substring mapping to <leader>P. Set Lisp keyword characters also in SLDB buffer. Bugfixes: Error messages at Connect-Server. Error message for frame source location without filename. XRef output sometimes cut.","3":"Improved frame number identification in SLDB buffer. Moved frame source location above frame locals in SLDB. Fold frame source location if more than 2 lines. Inspect-In-Frame: preselect symbol under cursor only in variable lines, open Inspector in the other window. Improved XRef file location parsing. Use current paragraph when no range set for Eval-Region and Compile-Region. Added option g:slimv_sldb_wrap, do not set wrap for source buffers. Added Set-Breakpoint command mapped to <leader>B (thanks to Philipp Marek), changed Profile-By-Substring mapping to <leader>P. Set Lisp keyword characters also in SLDB buffer. Bugfixes: Error messages at Connect-Server. Error message for frame source location without filename. XRef output sometimes cut.","package":"slimv091.zip","4":"slimv091.zip","src_id":"16661","5":"16661","creation_date":"1318507218","6":"1318507218"},{"0":"2531","vim_version":"7.0","1":"7.0","script_version":"0.9.0","2":"0.9.0","version_comment":"Separate buffers for SLDB and Inspector, toggle frame information in SLDB buffer by pressing Enter, look up source when pressing Enter on filename with location in SLDB, added option g:swank_block_size to override Swank output buffer size (thanks to stassats on #lisp and Philipp Marek), removed old non-swank functionality, removed option g:slimv_repl_open, paredit: new mappings [[ and ]] for previous and next defun, bugfixes: various refresh problems (thanks to Philipp Marek), disable debug mode when reconnecting Swank (by Philipp Marek), display multi-line debug condition and frame source location, quote characters in compile (by Philipp Marek), use proper SLDB level when invoking restart (by Philipp Marek), restore all lisp keyword characters in iskeyword, indentation of defgeneric, use proper filename and location when compiling defun or region, buffer corruption when re-triggering timer in insert mode, <End> moved cursor to the right edge of screen in REPL buffer when virtualmode=all.","3":"Separate buffers for SLDB and Inspector, toggle frame information in SLDB buffer by pressing Enter, look up source when pressing Enter on filename with location in SLDB, added option g:swank_block_size to override Swank output buffer size (thanks to stassats on #lisp and Philipp Marek), removed old non-swank functionality, removed option g:slimv_repl_open, paredit: new mappings [[ and ]] for previous and next defun, bugfixes: various refresh problems (thanks to Philipp Marek), disable debug mode when reconnecting Swank (by Philipp Marek), display multi-line debug condition and frame source location, quote characters in compile (by Philipp Marek), use proper SLDB level when invoking restart (by Philipp Marek), restore all lisp keyword characters in iskeyword, indentation of defgeneric, use proper filename and location when compiling defun or region, buffer corruption when re-triggering timer in insert mode, <End> moved cursor to the right edge of screen in REPL buffer when virtualmode=all.","package":"slimv090.zip","4":"slimv090.zip","src_id":"16623","5":"16623","creation_date":"1317826625","6":"1317826625"},{"0":"2531","vim_version":"7.0","1":"7.0","script_version":"0.8.6","2":"0.8.6","version_comment":"Handle cl:in-package, common-lisp:in-package (thanks to Philipp Marek), added option g:swank_host to allow connecting to remote Swank server, autodetection of Cake for Clojure (thanks to Chris Cahoon), set paredit mode also for .cl and .rkt files, recognise domain reversed package names in form com.gigamonkeys.pathnames (thanks to has2k1), added curly braces rainbow parenthesis for Clojure, added paredit handling of curly braces for Clojure, use SlimvIndent also for Clojure, handle line number returned in :compilation-result, bugfixes: removed double newline in :read-string (text input), when editing with cw in paredit mode, keep ending whitespaces (thanks to Mats Rauhala), compilation error when Swank does not return file name, skip dot character when Swank returns a dotted pair (a . b).","3":"Handle cl:in-package, common-lisp:in-package (thanks to Philipp Marek), added option g:swank_host to allow connecting to remote Swank server, autodetection of Cake for Clojure (thanks to Chris Cahoon), set paredit mode also for .cl and .rkt files, recognise domain reversed package names in form com.gigamonkeys.pathnames (thanks to has2k1), added curly braces rainbow parenthesis for Clojure, added paredit handling of curly braces for Clojure, use SlimvIndent also for Clojure, handle line number returned in :compilation-result, bugfixes: removed double newline in :read-string (text input), when editing with cw in paredit mode, keep ending whitespaces (thanks to Mats Rauhala), compilation error when Swank does not return file name, skip dot character when Swank returns a dotted pair (a . b).","package":"slimv086.zip","4":"slimv086.zip","src_id":"16353","5":"16353","creation_date":"1314301859","6":"1314301859"},{"0":"2531","vim_version":"7.0","1":"7.0","script_version":"0.8.5","2":"0.8.5","version_comment":"Switch on indent plugins, do not complete empty string on <Tab>, added Clojure keywords to syntax plugin, use -i option to load swank-clojure, implementation specific REPL initialization, for Clojure it imports source, apropos, javadoc, etc. (thanks to \u00c3\u0096mer Sinan Agacan), print Lisp version at REPL startup, added List-Threads, Kill-Thread, Debug-Thread (thanks to Philipp Marek), write prompt after Toggle-Trace, display list of untraced functions for Untrace-All, when in SLDB, Interactive-Eval evaluates expressions in the frame, Inspect inspects objects in the frame, changed g:slimv_echolines logic: set 0 for no lines, -1 for all lines, bugfixes: removed extra linebreak between chunks of long output, indentation problems for symbols with package specification (thanks to Philipp Marek), indentation of Clojure's defn, plist indentation (thanks to Philipp Marek), occasional few seconds delay in swank response, running Swank server on Mac OS X (on behalf of Tobias Pflug).","3":"Switch on indent plugins, do not complete empty string on <Tab>, added Clojure keywords to syntax plugin, use -i option to load swank-clojure, implementation specific REPL initialization, for Clojure it imports source, apropos, javadoc, etc. (thanks to \u00c3\u0096mer Sinan Agacan), print Lisp version at REPL startup, added List-Threads, Kill-Thread, Debug-Thread (thanks to Philipp Marek), write prompt after Toggle-Trace, display list of untraced functions for Untrace-All, when in SLDB, Interactive-Eval evaluates expressions in the frame, Inspect inspects objects in the frame, changed g:slimv_echolines logic: set 0 for no lines, -1 for all lines, bugfixes: removed extra linebreak between chunks of long output, indentation problems for symbols with package specification (thanks to Philipp Marek), indentation of Clojure's defn, plist indentation (thanks to Philipp Marek), occasional few seconds delay in swank response, running Swank server on Mac OS X (on behalf of Tobias Pflug).","package":"slimv085.zip","4":"slimv085.zip","src_id":"16193","5":"16193","creation_date":"1312404593","6":"1312404593"},{"0":"2531","vim_version":"7.0","1":"7.0","script_version":"0.8.4","2":"0.8.4","version_comment":"Added handling for Unicode characters, truncate arglist output to fit in the status line, added debugger keybindings: ,a for abort ,q for quit ,n for continue, changed keybinding for apropos to ,A, added compiler error messages to quickfix list, map insert mode <Space> and <Tab> only for lisp (and dialects) buffers, bugfixes: wait for the response to :create-repl before calling :swank-require (thanks to Philipp Marek), indentation problems with unbalanced parens in comment, arglist ate the <Space> when virtualedit was off.","3":"Added handling for Unicode characters, truncate arglist output to fit in the status line, added debugger keybindings: ,a for abort ,q for quit ,n for continue, changed keybinding for apropos to ,A, added compiler error messages to quickfix list, map insert mode <Space> and <Tab> only for lisp (and dialects) buffers, bugfixes: wait for the response to :create-repl before calling :swank-require (thanks to Philipp Marek), indentation problems with unbalanced parens in comment, arglist ate the <Space> when virtualedit was off.","package":"slimv084.zip","4":"slimv084.zip","src_id":"15909","5":"15909","creation_date":"1308256432","6":"1308256432"},{"0":"2531","vim_version":"7.0","1":"7.0","script_version":"0.8.3","2":"0.8.3","version_comment":"Added top\/bottom\/left\/right directions to g:slimv_repl_split, added :Lisp (and an equivalent :Eval) command with completion, added g:slimv_leader and g:paredit_leader options, added g:slimv_echolines to echo only the first few lines of the form being evaluated, added fuzzy completion and option g:slimv_simple_compl (by Philipp Marek), indent macros with &body argument by two spaces when connected to swank (thanks to Philipp Marek and Andreas Fredriksson), special indentation for flet, labels and macrolet, default for Set-Package is current package (thanks to Philipp Marek), bugfixes: REPL output ordering problems, problem with inserting Space into visual block, blinking when g:slimv_repl_syntax is on, entering incomplete form in REPL command line, close form when inside comment, string, or with mixed ([.","3":"Added top\/bottom\/left\/right directions to g:slimv_repl_split, added :Lisp (and an equivalent :Eval) command with completion, added g:slimv_leader and g:paredit_leader options, added g:slimv_echolines to echo only the first few lines of the form being evaluated, added fuzzy completion and option g:slimv_simple_compl (by Philipp Marek), indent macros with &body argument by two spaces when connected to swank (thanks to Philipp Marek and Andreas Fredriksson), special indentation for flet, labels and macrolet, default for Set-Package is current package (thanks to Philipp Marek), bugfixes: REPL output ordering problems, problem with inserting Space into visual block, blinking when g:slimv_repl_syntax is on, entering incomplete form in REPL command line, close form when inside comment, string, or with mixed ([.","package":"slimv083.zip","4":"slimv083.zip","src_id":"15665","5":"15665","creation_date":"1305704313","6":"1305704313"},{"0":"2531","vim_version":"7.0","1":"7.0","script_version":"0.8.2","2":"0.8.2","version_comment":"Added Paredit and g:lisp_rainbow support for Scheme files, added SWANK support for MIT Scheme on Linux, added frame call information to SLDB (thanks to Philipp Marek), check for unbalanced form before evaluation, reconnect SWANK server in Connect-Server if already connected (thanks to Philipp Marek), select current form instead of top level form in Macroexpand, bugfixes: Paredit handling of escaped matched characters (e.g. \\\"), cursor positioning problems when debugger activated, print prompt after Describe.","3":"Added Paredit and g:lisp_rainbow support for Scheme files, added SWANK support for MIT Scheme on Linux, added frame call information to SLDB (thanks to Philipp Marek), check for unbalanced form before evaluation, reconnect SWANK server in Connect-Server if already connected (thanks to Philipp Marek), select current form instead of top level form in Macroexpand, bugfixes: Paredit handling of escaped matched characters (e.g. \\\"), cursor positioning problems when debugger activated, print prompt after Describe.","package":"slimv082.zip","4":"slimv082.zip","src_id":"15563","5":"15563","creation_date":"1304254629","6":"1304254629"},{"0":"2531","vim_version":"7.0","1":"7.0","script_version":"0.8.1","2":"0.8.1","version_comment":"Added action handling to Inspector, fixed Inspector output, bugfixes: read-string mode was stuck, buffer corruption with two source windows (thanks to Philipp Marek), eliminate multiple CursorHold autocommands (thanks to Philipp Marek), completion with special characters in symbol name (thanks to Philipp Marek), sometimes cursor went to the start of line in insert mode, syntax error in Untrace All (thanks to Philipp Marek), removed ' prefix from symbol selection (except for Inspect), keep cursor position in Describe and Compile-Region.","3":"Added action handling to Inspector, fixed Inspector output, bugfixes: read-string mode was stuck, buffer corruption with two source windows (thanks to Philipp Marek), eliminate multiple CursorHold autocommands (thanks to Philipp Marek), completion with special characters in symbol name (thanks to Philipp Marek), sometimes cursor went to the start of line in insert mode, syntax error in Untrace All (thanks to Philipp Marek), removed ' prefix from symbol selection (except for Inspect), keep cursor position in Describe and Compile-Region.","package":"slimv081.zip","4":"slimv081.zip","src_id":"15486","5":"15486","creation_date":"1303284425","6":"1303284425"},{"0":"2531","vim_version":"7.0","1":"7.0","script_version":"0.8.0","2":"0.8.0","version_comment":"Major update: added SWANK client (many thanks to Philipp Marek), additional changes: split documentation into three parts, added keymapping hints to GUI menu items, renamed Eval-Last-Expression to Eval-Current-Expression, REPL buffer is not syntax highlighted anymore, switch on filetype plugins, autodetection for Allegro CL, Lisp Cabinet and Leiningen, ask for save before compiling file, map <Tab> for completion, bugfixes: finding start of keyword in completion, deleting escaped \" inside string, Up\/Down\/Enter handling in popup menu.","3":"Major update: added SWANK client (many thanks to Philipp Marek), additional changes: split documentation into three parts, added keymapping hints to GUI menu items, renamed Eval-Last-Expression to Eval-Current-Expression, REPL buffer is not syntax highlighted anymore, switch on filetype plugins, autodetection for Allegro CL, Lisp Cabinet and Leiningen, ask for save before compiling file, map <Tab> for completion, bugfixes: finding start of keyword in completion, deleting escaped \" inside string, Up\/Down\/Enter handling in popup menu.","package":"slimv080.zip","4":"slimv080.zip","src_id":"15451","5":"15451","creation_date":"1302850532","6":"1302850532"},{"0":"2531","vim_version":"7.0","1":"7.0","script_version":"0.7.5","2":"0.7.5","version_comment":"Added Cygwin compatibility using the Windows Python (thanks to Jerome Baum), display client error message when eval was not successful, form is passed to client via stdin instead of temp file, bugfixes: automatic reconnection when server closed and reopened, delete and yank also via named registers in paredit.vim, handle double quotes in Compile-Defun and Compile-Region.","3":"Added Cygwin compatibility using the Windows Python (thanks to Jerome Baum), display client error message when eval was not successful, form is passed to client via stdin instead of temp file, bugfixes: automatic reconnection when server closed and reopened, delete and yank also via named registers in paredit.vim, handle double quotes in Compile-Defun and Compile-Region.","package":"Slimv075.zip","4":"Slimv075.zip","src_id":"14687","5":"14687","creation_date":"1294262831","6":"1294262831"},{"0":"2531","vim_version":"7.0","1":"7.0","script_version":"0.7.4","2":"0.7.4","version_comment":"Added autodetection for simple 'clojure' command on Linux, removed duplicates from history of commands entered in REPL buffer (those recallable with <Up>), bugfixes: infinite loop during eval when 'in-package' or 'in-ns' was in comment, Lisp prompt identification problems in REPL buffer, input line duplication in SBCL on Linux (assigned \"*debug-io*\" to stdin), Eval Defun sometimes missed last \")\".","3":"Added autodetection for simple 'clojure' command on Linux, removed duplicates from history of commands entered in REPL buffer (those recallable with <Up>), bugfixes: infinite loop during eval when 'in-package' or 'in-ns' was in comment, Lisp prompt identification problems in REPL buffer, input line duplication in SBCL on Linux (assigned \"*debug-io*\" to stdin), Eval Defun sometimes missed last \")\".","package":"Slimv074.zip","4":"Slimv074.zip","src_id":"14527","5":"14527","creation_date":"1292491526","6":"1292491526"},{"0":"2531","vim_version":"7.0","1":"7.0","script_version":"0.7.3","2":"0.7.3","version_comment":"Added compatibility with Python 3.x, bugfixes: input lines for REPL were doubled on Linux (thanks to Andrew Hills), however not yet fixed for SBCL, enclose Slimv path in double quotes if contains space, select form when standing on prefix character (e.g. ' or `).","3":"Added compatibility with Python 3.x, bugfixes: input lines for REPL were doubled on Linux (thanks to Andrew Hills), however not yet fixed for SBCL, enclose Slimv path in double quotes if contains space, select form when standing on prefix character (e.g. ' or `).","package":"Slimv073.zip","4":"Slimv073.zip","src_id":"14445","5":"14445","creation_date":"1291586254","6":"1291586254"},{"0":"2531","vim_version":"7.0","1":"7.0","script_version":"0.7.2","2":"0.7.2","version_comment":"Added autodetection for \/usr\/local\/bin\/clojure on Linux, added special characters to Lisp keyword selection (iskeyword), run Vim's original ftplugin\/lisp.vim for Clojure filetype, bugfixes: PareditWrap error when g:paredit_shortmaps=1 (thanks to Jon Thacker), buffer selection problems in case of three of more buffers (thanks to Philipp Marek), conflicting keybindings for SlimvGenerateTags, unmap error messages when g:paredit_mode=0.","3":"Added autodetection for \/usr\/local\/bin\/clojure on Linux, added special characters to Lisp keyword selection (iskeyword), run Vim's original ftplugin\/lisp.vim for Clojure filetype, bugfixes: PareditWrap error when g:paredit_shortmaps=1 (thanks to Jon Thacker), buffer selection problems in case of three of more buffers (thanks to Philipp Marek), conflicting keybindings for SlimvGenerateTags, unmap error messages when g:paredit_mode=0.","package":"Slimv072.zip","4":"Slimv072.zip","src_id":"14276","5":"14276","creation_date":"1289946435","6":"1289946435"},{"0":"2531","vim_version":"7.0","1":"7.0","script_version":"0.7.1","2":"0.7.1","version_comment":"Added option g:slimv_browser_cmd for opening hyperspec in a custom webbrowser (on behalf of Andreas Salwasser), added paredit handling for d<motion>, c<motion>, p and P commands: keep paren balance when deleting and pasting text, Paredit Toggle function removes and re-adds paredit keybindings, bugfix: D and C deleted till beginning of line if () or [] found, handle escaped \\\" characters inside string.","3":"Added option g:slimv_browser_cmd for opening hyperspec in a custom webbrowser (on behalf of Andreas Salwasser), added paredit handling for d<motion>, c<motion>, p and P commands: keep paren balance when deleting and pasting text, Paredit Toggle function removes and re-adds paredit keybindings, bugfix: D and C deleted till beginning of line if () or [] found, handle escaped \\\" characters inside string.","package":"Slimv071.zip","4":"Slimv071.zip","src_id":"14202","5":"14202","creation_date":"1289139269","6":"1289139269"},{"0":"2531","vim_version":"7.0","1":"7.0","script_version":"0.7.0","2":"0.7.0","version_comment":"Added package\/namespace support, new way of refreshing the REPL buffer via autocommands, removed 'RUNNING' mode, cursor stays in the current buffer at evaluation, added option g:slimv_updatetime, removed options related to the old way of refreshing (g:slimv_repl_return and g:slimv_repl_wait), removed debug logging, updated Clojure API to version 1.2, extended keyword definition when selecting symbols, bugfix: defmacro detection problem (again).","3":"Added package\/namespace support, new way of refreshing the REPL buffer via autocommands, removed 'RUNNING' mode, cursor stays in the current buffer at evaluation, added option g:slimv_updatetime, removed options related to the old way of refreshing (g:slimv_repl_return and g:slimv_repl_wait), removed debug logging, updated Clojure API to version 1.2, extended keyword definition when selecting symbols, bugfix: defmacro detection problem (again).","package":"Slimv070.zip","4":"Slimv070.zip","src_id":"13980","5":"13980","creation_date":"1286051843","6":"1286051843"},{"0":"2531","vim_version":"7.0","1":"7.0","script_version":"0.6.0","2":"0.6.0","version_comment":"Added paredit mode, set wrap for REPL buffer.","3":"Added paredit mode, set wrap for REPL buffer.","package":"Slimv060.zip","4":"Slimv060.zip","src_id":"12829","5":"12829","creation_date":"1271267121","6":"1271267121"},{"0":"2531","vim_version":"7.0","1":"7.0","script_version":"0.5.0","2":"0.5.0","version_comment":"Major project reorganization: Slimv is now a Lisp and Clojure filetype plugin; added Common Lisp Hyperspec, Clojure API and JavaDoc lookup; separate menu for REPL buffer; menu items work in every Vim mode; fixed mark 's usage bug.","3":"Major project reorganization: Slimv is now a Lisp and Clojure filetype plugin; added Common Lisp Hyperspec, Clojure API and JavaDoc lookup; separate menu for REPL buffer; menu items work in every Vim mode; fixed mark 's usage bug.","package":"Slimv050.zip","4":"Slimv050.zip","src_id":"10420","5":"10420","creation_date":"1240155112","6":"1240155112"},{"0":"2531","vim_version":"7.0","1":"7.0","script_version":"0.4.0","2":"0.4.0","version_comment":"Added SLIME's profiling tool with support from Slimv, added command to generate tags file, fixed eval problems of large buffers, fixed Compile And Load filename problems with '\\' on Windows, recycle old REPL temporary file at next server startup.","3":"Added SLIME's profiling tool with support from Slimv, added command to generate tags file, fixed eval problems of large buffers, fixed Compile And Load filename problems with '\\' on Windows, recycle old REPL temporary file at next server startup.","package":"Slimv040.zip","4":"Slimv040.zip","src_id":"10263","5":"10263","creation_date":"1237728281","6":"1237728281"},{"0":"2531","vim_version":"7.0","1":"7.0","script_version":"0.3.0","2":"0.3.0","version_comment":"REPL buffer enhancements: added syntax highlighting and automatic indentation, it is possible to enter a multi-line command, Ctrl-C is working; server REPL window performance enhancement on Linux.","3":"REPL buffer enhancements: added syntax highlighting and automatic indentation, it is possible to enter a multi-line command, Ctrl-C is working; server REPL window performance enhancement on Linux.","package":"Slimv030.zip","4":"Slimv030.zip","src_id":"10230","5":"10230","creation_date":"1237240208","6":"1237240208"},{"0":"2531","vim_version":"7.0","1":"7.0","script_version":"0.2.0","2":"0.2.0","version_comment":"Major update: Lisp REPL inside a Vim buffer","3":"Major update: Lisp REPL inside a Vim buffer","package":"Slimv020.zip","4":"Slimv020.zip","src_id":"10062","5":"10062","creation_date":"1235852850","6":"1235852850"},{"0":"2531","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"Slimv.zip","4":"Slimv.zip","src_id":"9892","5":"9892","creation_date":"1233415907","6":"1233415907"}]},"2530":{"script_id":"2530","0":"2530","script_name":"po.vim","1":"po.vim","script_type":"ftplugin","2":"ftplugin","summary":"This script is a fork version of Aleksandar Jelenak's script.","3":"This script is a fork version of Aleksandar Jelenak's script.","description":"This script is a fork version of Aleksandar Jelenak's script. It's a ftplugin for PO file (GNU gettext) editing. I fixed two bugs and add three other functions and remapped the keys. Thanks to Aleksandar Jelenak a lot. Detailed description can be found in the source file.","4":"This script is a fork version of Aleksandar Jelenak's script. It's a ftplugin for PO file (GNU gettext) editing. I fixed two bugs and add three other functions and remapped the keys. Thanks to Aleksandar Jelenak a lot. Detailed description can be found in the source file.","install_details":"Put the po.vim file in a Vim ftplugin directory. On UNIX computers it is usually either \"~\/.vim\/ftplugin\" or \"~\/.vim\/after\/ftplugin\". On Windows computers, the defaults are \"$VIM\\vimfiles\\ftplugin\" or \"$VIM\\vimfiles\\after\\ftplugin\". For more information consult the Vim help, \":help 'ftplugin'\" and \":help 'runtimepath'\". Put the po.txt file in the doc folder. It will be ok if you just extract the tarball under ~\/.vim","5":"Put the po.vim file in a Vim ftplugin directory. On UNIX computers it is usually either \"~\/.vim\/ftplugin\" or \"~\/.vim\/after\/ftplugin\". On Windows computers, the defaults are \"$VIM\\vimfiles\\ftplugin\" or \"$VIM\\vimfiles\\after\\ftplugin\". For more information consult the Vim help, \":help 'ftplugin'\" and \":help 'runtimepath'\". Put the po.txt file in the doc folder. It will be ok if you just extract the tarball under ~\/.vim","first_name":"grissiom","6":"grissiom","last_name":"gray","7":"gray","releases":[{"0":"2530","vim_version":"6.0","1":"6.0","script_version":"1.1","2":"1.1","version_comment":"Add help doc. Great thanks to Emmanuel Trillaud.\r\n    Now the package have two file: ftplugin\/po.vim and doc\/po.txt. Just extract them to ~\/.vim. Don't forget to :helptags ;)","3":"Add help doc. Great thanks to Emmanuel Trillaud.\r\n    Now the package have two file: ftplugin\/po.vim and doc\/po.txt. Just extract them to ~\/.vim. Don't forget to :helptags ;)","package":"po.tar","4":"po.tar","src_id":"11839","5":"11839","creation_date":"1259731304","6":"1259731304"},{"0":"2530","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"po.vim","4":"po.vim","src_id":"9888","5":"9888","creation_date":"1233298580","6":"1233298580"}]},"2529":{"script_id":"2529","0":"2529","script_name":"IndentCommentPrefix","1":"IndentCommentPrefix","script_type":"utility","2":"utility","summary":"Keep comment prefix in column 1 when indenting. ","3":"Keep comment prefix in column 1 when indenting. ","description":"DESCRIPTION\r\nIndent commands like >>, << and i_CTRL-T, i_CTRL-D in insert mode\r\nindent the entire line. For some kinds of comments, like the big boilerplate\r\nat the file header etc., the comment prefix (e.g. # for Perl scripts) should\r\nremain at the first column, though.\r\nThis plugin modifies these indent commands so that the comment prefix remains\r\nin the first column, and the indenting takes place between the comment prefix\r\nand the comment text. For that, it uses the comment configuration provided by\r\nthe buffer's 'comment' option, which is set by most filetype plugins; this can\r\nbe tweaked via plugin configuration.\r\n\r\nUSAGE\r\nOn a line like this:\r\n# My comment.\r\n\r\nThe >> command now keeps the # prefix in column 1, and just indents the\r\ncomment text:\r\n#       My comment.\r\n\r\nThis only works if there is at least one whitespace character after the prefix\r\n(so that comments like ###### do not become #       ######).\r\nProgressive de-indenting will remove all whitespace between prefix and comment\r\ntext, or leave a single space in between if the 'comments' setting requires a\r\nblank after the comment prefix.\r\n\r\nAn optional [count] of lines can be supplied to the >> and << commands, as\r\nbefore.\r\nIn visual mode, the optional [count] specifies how many 'shiftwidth's should\r\nbe indented; the v_> and v_< commands operate on all highlighted lines.\r\n\r\nWith the optional repeat.vim script, the commands can also be repeated via ..\r\n\r\nThe same behavior is available in insert mode via the i_CTRL-T and\r\ni_CTRL-D mappings:\r\n\r\nCTRL-T          Insert one shiftwidth of indent at the start of the current\r\n                line, after any comment prefix. The indent is always rounded\r\n                to a 'shiftwidth'.\r\n\r\nCTRL-D          Delete one shiftwidth of indent at the start of the current\r\n                line, after any comment prefix. The indent is always rounded\r\n                to a 'shiftwidth'.\r\n\r\nCTRL-G CTRL-T   Insert a single space of indent at the start of the current\r\n                line, after any comment prefix, and toggle the behavior of\r\n                i_CTRL-D to continue inserting a single space instead of one\r\n                shiftwidth.\r\n\r\nCTRL-G CTRL-D   Delete a single space of indent at the start of the current\r\n                line, after any comment prefix, and toggle the behavior of\r\n                i_CTRL-D to continue deleting a single space instead of one\r\n                shiftwidth.\r\n\r\nGETTING BACK THE ORIGINAL BEHAVIOR\r\ng>>\r\n{Visual}g>\r\ng<<\r\n{Visual}g<\r\nIn case you want to indent lines including the comment prefix, the original\r\nindent behavior is mapped to g>> in normal mode and g> in visual mode.\r\nThere's only a need for the corresponding g<< dedent mappings when using the\r\ng:IndentCommentPrefix_Whitelist, because those prefixes will work not just\r\nin column 1 (where dedenting is not possible), but in any column.\r\nAlternatively, you could also use the >{motion} command, as the > and <\r\noperators aren't modified by this plugin.","4":"DESCRIPTION\r\nIndent commands like >>, << and i_CTRL-T, i_CTRL-D in insert mode\r\nindent the entire line. For some kinds of comments, like the big boilerplate\r\nat the file header etc., the comment prefix (e.g. # for Perl scripts) should\r\nremain at the first column, though.\r\nThis plugin modifies these indent commands so that the comment prefix remains\r\nin the first column, and the indenting takes place between the comment prefix\r\nand the comment text. For that, it uses the comment configuration provided by\r\nthe buffer's 'comment' option, which is set by most filetype plugins; this can\r\nbe tweaked via plugin configuration.\r\n\r\nUSAGE\r\nOn a line like this:\r\n# My comment.\r\n\r\nThe >> command now keeps the # prefix in column 1, and just indents the\r\ncomment text:\r\n#       My comment.\r\n\r\nThis only works if there is at least one whitespace character after the prefix\r\n(so that comments like ###### do not become #       ######).\r\nProgressive de-indenting will remove all whitespace between prefix and comment\r\ntext, or leave a single space in between if the 'comments' setting requires a\r\nblank after the comment prefix.\r\n\r\nAn optional [count] of lines can be supplied to the >> and << commands, as\r\nbefore.\r\nIn visual mode, the optional [count] specifies how many 'shiftwidth's should\r\nbe indented; the v_> and v_< commands operate on all highlighted lines.\r\n\r\nWith the optional repeat.vim script, the commands can also be repeated via ..\r\n\r\nThe same behavior is available in insert mode via the i_CTRL-T and\r\ni_CTRL-D mappings:\r\n\r\nCTRL-T          Insert one shiftwidth of indent at the start of the current\r\n                line, after any comment prefix. The indent is always rounded\r\n                to a 'shiftwidth'.\r\n\r\nCTRL-D          Delete one shiftwidth of indent at the start of the current\r\n                line, after any comment prefix. The indent is always rounded\r\n                to a 'shiftwidth'.\r\n\r\nCTRL-G CTRL-T   Insert a single space of indent at the start of the current\r\n                line, after any comment prefix, and toggle the behavior of\r\n                i_CTRL-D to continue inserting a single space instead of one\r\n                shiftwidth.\r\n\r\nCTRL-G CTRL-D   Delete a single space of indent at the start of the current\r\n                line, after any comment prefix, and toggle the behavior of\r\n                i_CTRL-D to continue deleting a single space instead of one\r\n                shiftwidth.\r\n\r\nGETTING BACK THE ORIGINAL BEHAVIOR\r\ng>>\r\n{Visual}g>\r\ng<<\r\n{Visual}g<\r\nIn case you want to indent lines including the comment prefix, the original\r\nindent behavior is mapped to g>> in normal mode and g> in visual mode.\r\nThere's only a need for the corresponding g<< dedent mappings when using the\r\ng:IndentCommentPrefix_Whitelist, because those prefixes will work not just\r\nin column 1 (where dedenting is not possible), but in any column.\r\nAlternatively, you could also use the >{motion} command, as the > and <\r\noperators aren't modified by this plugin.","install_details":"INSTALLATION\r\nThe code is hosted in a Git repo at\r\n    https:\/\/github.com\/inkarkat\/vim-IndentCommentPrefix\r\nYou can use your favorite plugin manager, or \"git clone\" into a directory used\r\nfor Vim packages. Releases are on the \"stable\" branch, the latest unstable\r\ndevelopment snapshot on \"master\".\r\n\r\nThis script is also packaged as a vimball. If you have the \"gunzip\"\r\ndecompressor in your PATH, simply edit the *.vmb.gz package in Vim; otherwise,\r\ndecompress the archive first, e.g. using WinZip. Inside Vim, install by\r\nsourcing the vimball or via the :UseVimball command.\r\n    vim IndentCommentPrefix*.vmb.gz\r\n    :so %\r\nTo uninstall, use the :RmVimball command.\r\n\r\nDEPENDENCIES\r\n- Requires Vim 7.0 or higher.\r\n- Requires the ingo-library.vim plugin (vimscript #4433), version 1.005 or\r\n  higher.\r\n- repeat.vim (vimscript #2136) plugin (optional)\r\n\r\nCONFIGURATION\r\nFor a permanent configuration, put the following commands into your vimrc:\r\n\r\nBy default, indenting behavior with all comment prefixes defined in the\r\n'comments' option is modified. To disable the keeping in column 1 for some\r\nprefixes, add each prefix to the following (buffer-local or global) List\r\nvariable:\r\n    let g:IndentCommentPrefix_Blacklist = ['#', '>']\r\n\r\nIf you want to modify the indenting behavior for certain prefixes not just in\r\ncolumn 1, but with any existing indent, add each prefix to the following\r\n(buffer-local or global) List variable. These prefixes do not need to be\r\ncontained in 'comments' then.\r\n    let g:IndentCommentPrefix_Whitelist = ['REMARK:']\r\n\r\nYou may want to use a different 'shiftwidth' or 'expandtab' setting for\r\nindenting with a comment prefix (vs. \"normal\" indenting without comments), you\r\ncan define the settings globally (or alternatively for the current buffer)\r\nvia:\r\n    let g:IndentCommentPrefix_IndentSettingsOverride = 'shiftwidth=3 expandtab'\r\n\r\nIf you want to use different mappings instead of overriding the default\r\ncommands, map your keys to the <Plug>IndentCommentPrefix... mapping targets\r\n_before_ sourcing the script (e.g. in your vimrc):\r\n    imap <C-t> <Plug>IndentCommentPrefixIndent\r\n    imap <C-d> <Plug>IndentCommentPrefixDedent\r\n    nmap <Leader>>     <Plug>IndentCommentPrefix0\r\n    vmap <Leader>>     <Plug>IndentCommentPrefix0\r\n    nmap <Leader><lt>  <Plug>IndentCommentPrefix1\r\n    vmap <Leader><lt>  <Plug>IndentCommentPrefix1\r\n\r\nIf you don't want the alternative g>> and g<< mappings for the original indent\r\ncommands, set the following variable _before_ sourcing the plugin:\r\n    let g:IndentCommentPrefix_alternativeOriginalCommands = 0","5":"INSTALLATION\r\nThe code is hosted in a Git repo at\r\n    https:\/\/github.com\/inkarkat\/vim-IndentCommentPrefix\r\nYou can use your favorite plugin manager, or \"git clone\" into a directory used\r\nfor Vim packages. Releases are on the \"stable\" branch, the latest unstable\r\ndevelopment snapshot on \"master\".\r\n\r\nThis script is also packaged as a vimball. If you have the \"gunzip\"\r\ndecompressor in your PATH, simply edit the *.vmb.gz package in Vim; otherwise,\r\ndecompress the archive first, e.g. using WinZip. Inside Vim, install by\r\nsourcing the vimball or via the :UseVimball command.\r\n    vim IndentCommentPrefix*.vmb.gz\r\n    :so %\r\nTo uninstall, use the :RmVimball command.\r\n\r\nDEPENDENCIES\r\n- Requires Vim 7.0 or higher.\r\n- Requires the ingo-library.vim plugin (vimscript #4433), version 1.005 or\r\n  higher.\r\n- repeat.vim (vimscript #2136) plugin (optional)\r\n\r\nCONFIGURATION\r\nFor a permanent configuration, put the following commands into your vimrc:\r\n\r\nBy default, indenting behavior with all comment prefixes defined in the\r\n'comments' option is modified. To disable the keeping in column 1 for some\r\nprefixes, add each prefix to the following (buffer-local or global) List\r\nvariable:\r\n    let g:IndentCommentPrefix_Blacklist = ['#', '>']\r\n\r\nIf you want to modify the indenting behavior for certain prefixes not just in\r\ncolumn 1, but with any existing indent, add each prefix to the following\r\n(buffer-local or global) List variable. These prefixes do not need to be\r\ncontained in 'comments' then.\r\n    let g:IndentCommentPrefix_Whitelist = ['REMARK:']\r\n\r\nYou may want to use a different 'shiftwidth' or 'expandtab' setting for\r\nindenting with a comment prefix (vs. \"normal\" indenting without comments), you\r\ncan define the settings globally (or alternatively for the current buffer)\r\nvia:\r\n    let g:IndentCommentPrefix_IndentSettingsOverride = 'shiftwidth=3 expandtab'\r\n\r\nIf you want to use different mappings instead of overriding the default\r\ncommands, map your keys to the <Plug>IndentCommentPrefix... mapping targets\r\n_before_ sourcing the script (e.g. in your vimrc):\r\n    imap <C-t> <Plug>IndentCommentPrefixIndent\r\n    imap <C-d> <Plug>IndentCommentPrefixDedent\r\n    nmap <Leader>>     <Plug>IndentCommentPrefix0\r\n    vmap <Leader>>     <Plug>IndentCommentPrefix0\r\n    nmap <Leader><lt>  <Plug>IndentCommentPrefix1\r\n    vmap <Leader><lt>  <Plug>IndentCommentPrefix1\r\n\r\nIf you don't want the alternative g>> and g<< mappings for the original indent\r\ncommands, set the following variable _before_ sourcing the plugin:\r\n    let g:IndentCommentPrefix_alternativeOriginalCommands = 0","first_name":"Ingo","6":"Ingo","last_name":"Karkat","7":"Karkat","releases":[{"0":"2529","vim_version":"7.0","1":"7.0","script_version":"1.40","2":"1.40","version_comment":"- Supply 'i' flag (since Vim 7.4.601) to execute the insert mode in\/dedent before typeahead (to avoid breaking macro playbacks).\r\n- ENH: Define <Plug>-imaps for <C-d> \/ <C-t> to allow remapping of those, too.\r\n- ENH: Add IndentCommentPrefix#InsertToggled() wrapper for IndentCommentPrefix#InsertMode() that implements toggling of 'shiftwidth' \/ single space indenting via a separate toggle mapping.\r\n- ENH: Allow overriding the 'shiftwidth' and 'expandtab' indent settings for indenting of comment prefixes via","3":"- Supply 'i' flag (since Vim 7.4.601) to execute the insert mode in\/dedent before typeahead (to avoid breaking macro playbacks).\r\n- ENH: Define <Plug>-imaps for <C-d> \/ <C-t> to allow remapping of those, too.\r\n- ENH: Add IndentCommentPrefix#InsertToggled() wrapper for IndentCommentPrefix#InsertMode() that implements toggling of 'shiftwidth' \/ single space indenting via a separate toggle mapping.\r\n- ENH: Allow overriding the 'shiftwidth' and 'expandtab' indent settings for indenting of comment prefixes via","package":"IndentCommentPrefix-1.40.vmb.gz","4":"IndentCommentPrefix-1.40.vmb.gz","src_id":"25731","5":"25731","creation_date":"1514025439","6":"1514025439"},{"0":"2529","vim_version":"7.0","1":"7.0","script_version":"1.32","2":"1.32","version_comment":"- Add special case to handle the (rather obscure) |i_0_CTRL-D| and |i_^_CTRL-D| commands, which were broken by the plugin's insert mode mapping.\r\n- Add dependency to ingo-library (vimscript #4433). *** You need to separately install ingo-library (vimscript #4433) version 1.005 (or higher)! ***","3":"- Add special case to handle the (rather obscure) |i_0_CTRL-D| and |i_^_CTRL-D| commands, which were broken by the plugin's insert mode mapping.\r\n- Add dependency to ingo-library (vimscript #4433). *** You need to separately install ingo-library (vimscript #4433) version 1.005 (or higher)! ***","package":"IndentCommentPrefix-1.32.vmb.gz","4":"IndentCommentPrefix-1.32.vmb.gz","src_id":"21063","5":"21063","creation_date":"1384858151","6":"1384858151"},{"0":"2529","vim_version":"7.0","1":"7.0","script_version":"1.31","2":"1.31","version_comment":"Also define opposite g<< commands with g:IndentCommentPrefix_alternativeOriginalCommands. It's good for consistency (my muscle memory often cannot distingish indenting from dedenting), and necessary when using the g:IndentCommentPrefix_Whitelist, because those work not just in column 1 (where dedenting is not possible), but in any column.","3":"Also define opposite g<< commands with g:IndentCommentPrefix_alternativeOriginalCommands. It's good for consistency (my muscle memory often cannot distingish indenting from dedenting), and necessary when using the g:IndentCommentPrefix_Whitelist, because those work not just in column 1 (where dedenting is not possible), but in any column.","package":"IndentCommentPrefix-1.31.vmb.gz","4":"IndentCommentPrefix-1.31.vmb.gz","src_id":"19432","5":"19432","creation_date":"1359119655","6":"1359119655"},{"0":"2529","vim_version":"7.0","1":"7.0","script_version":"1.30","2":"1.30","version_comment":"- ENH: Add global and buffer-local whitelists \/ blacklists to explicitly include \/ exclude certain comment prefixes.\r\n- Handle readonly and nomodifiable buffers by printing just the warning \/ error, without the multi-line function error.\r\n- FIX: Now handling three-piece comments correctly. The start may set a positive indent offset for the middle and end comment prefixes that must be considered.\r\n- FIX: Suppress 'ignorecase' in s:Literal().","3":"- ENH: Add global and buffer-local whitelists \/ blacklists to explicitly include \/ exclude certain comment prefixes.\r\n- Handle readonly and nomodifiable buffers by printing just the warning \/ error, without the multi-line function error.\r\n- FIX: Now handling three-piece comments correctly. The start may set a positive indent offset for the middle and end comment prefixes that must be considered.\r\n- FIX: Suppress 'ignorecase' in s:Literal().","package":"IndentCommentPrefix-1.30.vmb.gz","4":"IndentCommentPrefix-1.30.vmb.gz","src_id":"19177","5":"19177","creation_date":"1355407092","6":"1355407092"},{"0":"2529","vim_version":"7.0","1":"7.0","script_version":"1.10","2":"1.10","version_comment":"- Split off separate documentation and autoload script. Now publishing as Vimball. \r\n- BUG: Only report changes if more than 'report' lines where indented; I got the meaning of 'report' wrong the first time. \r\n- BUG: Could not use 999>> to indent all remaining lines. \r\n- BUG: Normal-mode mapping didn't necessarily put the cursor on the first non-blank character after the comment prefix if 'nostartofline' is set. \r\n- ENH: In normal and visual mode, set the change marks '[ and ]' similar to what Vim does. ","3":"- Split off separate documentation and autoload script. Now publishing as Vimball. \r\n- BUG: Only report changes if more than 'report' lines where indented; I got the meaning of 'report' wrong the first time. \r\n- BUG: Could not use 999>> to indent all remaining lines. \r\n- BUG: Normal-mode mapping didn't necessarily put the cursor on the first non-blank character after the comment prefix if 'nostartofline' is set. \r\n- ENH: In normal and visual mode, set the change marks '[ and ]' similar to what Vim does. ","package":"IndentCommentPrefix.vba.gz","4":"IndentCommentPrefix.vba.gz","src_id":"15338","5":"15338","creation_date":"1301470118","6":"1301470118"},{"0":"2529","vim_version":"7.0","1":"7.0","script_version":"1.02","2":"1.02","version_comment":"Do not define mappings for select mode; printable characters should start insert mode. ","3":"Do not define mappings for select mode; printable characters should start insert mode. ","package":"IndentCommentPrefix.vim","4":"IndentCommentPrefix.vim","src_id":"11491","5":"11491","creation_date":"1254835579","6":"1254835579"},{"0":"2529","vim_version":"7.0","1":"7.0","script_version":"1.01.009","2":"1.01.009","version_comment":"BF: When 'report' is less than the default 2, the :substitute and << \/ >> commands created additional messages, causing a hit-enter prompt.  Now also reporting a single-line change when 'report' is 0 (to be consistent with the built-in indent commands). ","3":"BF: When 'report' is less than the default 2, the :substitute and << \/ >> commands created additional messages, causing a hit-enter prompt.  Now also reporting a single-line change when 'report' is 0 (to be consistent with the built-in indent commands). ","package":"IndentCommentPrefix.vim","4":"IndentCommentPrefix.vim","src_id":"10953","5":"10953","creation_date":"1246829679","6":"1246829679"},{"0":"2529","vim_version":"7.0","1":"7.0","script_version":"1.00.008","2":"1.00.008","version_comment":"BF: Fixed \"E61: Nested *\" that occurred when shifting a line with a comment prefix containing multiple asterisks in a row (e.g. '**'). \r\nBF: Info message (given when indenting multiple lines) always printed \"1 time\" even when a [count] was specified in visual mode. ","3":"BF: Fixed \"E61: Nested *\" that occurred when shifting a line with a comment prefix containing multiple asterisks in a row (e.g. '**'). \r\nBF: Info message (given when indenting multiple lines) always printed \"1 time\" even when a [count] was specified in visual mode. ","package":"IndentCommentPrefix.vim","4":"IndentCommentPrefix.vim","src_id":"10011","5":"10011","creation_date":"1235397917","6":"1235397917"},{"0":"2529","vim_version":"7.0","1":"7.0","script_version":"1.00.007","2":"1.00.007","version_comment":"Initial upload","3":"Initial upload","package":"IndentCommentPrefix.vim","4":"IndentCommentPrefix.vim","src_id":"9885","5":"9885","creation_date":"1233261921","6":"1233261921"}]},"2528":{"script_id":"2528","0":"2528","script_name":"Thesaurus","1":"Thesaurus","script_type":"utility","2":"utility","summary":"Thesaurus suggestion script","3":"Thesaurus suggestion script","description":"Usage:\r\n   Use the Thesaurus normal mode command to find the synonyms for the word\r\n   under the cursor. The plugin requires vim to be build with python support,\r\n   and uses the nltk python module for stemming the words. You can obtain\r\n   nltk from http:\/\/www.nltk.org, or via easy_install.\r\n\r\n   The plugin defaults to using the en_US thesaurus files, usually installed\r\n   with Openoffice.org. These files can be located in\r\n   \/usr\/share\/myspell\/dicts. A different thesaurus file can be specified via\r\n   the g:thesaurus_file variable. It expects the full path to the files,\r\n   without the extension. If none is specified, a value of\r\n   '\/usr\/share\/myspell\/dicts\/th_en_US_v2' is assumed.","4":"Usage:\r\n   Use the Thesaurus normal mode command to find the synonyms for the word\r\n   under the cursor. The plugin requires vim to be build with python support,\r\n   and uses the nltk python module for stemming the words. You can obtain\r\n   nltk from http:\/\/www.nltk.org, or via easy_install.\r\n\r\n   The plugin defaults to using the en_US thesaurus files, usually installed\r\n   with Openoffice.org. These files can be located in\r\n   \/usr\/share\/myspell\/dicts. A different thesaurus file can be specified via\r\n   the g:thesaurus_file variable. It expects the full path to the files,\r\n   without the extension. If none is specified, a value of\r\n   '\/usr\/share\/myspell\/dicts\/th_en_US_v2' is assumed.","install_details":"Drop it in ~\/.vim\/plugins","5":"Drop it in ~\/.vim\/plugins","first_name":"Viktor","6":"Viktor","last_name":"Kojouharov","7":"Kojouharov","releases":[{"0":"2528","vim_version":"7.0","1":"7.0","script_version":"0.2","2":"0.2","version_comment":"cleanups and more visual  descriptions","3":"cleanups and more visual  descriptions","package":"thesaurus.vim","4":"thesaurus.vim","src_id":"11075","5":"11075","creation_date":"1248780985","6":"1248780985"},{"0":"2528","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"thesaurus.vim","4":"thesaurus.vim","src_id":"9875","5":"9875","creation_date":"1233078096","6":"1233078096"}]},"2527":{"script_id":"2527","0":"2527","script_name":"jpythonfold.vim","1":"jpythonfold.vim","script_type":"syntax","2":"syntax","summary":"A better python fold script","3":"A better python fold script","description":"This script allows automatically folding of Python code.\r\nIt completely rewritten from Jorrit Wiersma's script (vimscript #515; other competitors are vimscript#781 and vimscript#2002).\r\nThe folding and fold text are completely rewritten: the algorithm systematically set up, so it behaves as accurate as possible (at the cost of some speed).\r\nMain feature of this script is that it folds empty space, saving lots of screen space (although you can turn it off, see below).\r\nClasses and defs are folded, of course.\r\nIndent zero comments separating classes and defs are not folded, so you see the global divisions in your code.\r\nGlobal code is folded in blocks (separated by comments).\r\n\r\nThere are three options. To use them, check the script:\r\n- Keep empty lines out of a fold (giving more readable classes with folded functions, but using more screen space).\r\n- Ignore non-python files.\r\n- Allow for multiline class definitions (at the cost of folding comments starting with the word \"class\") or stricter def checking (missing multiline defs).\r\n\r\nKnown bug:\r\n- multiline strings that look like code are handled as such (basically unfixable, actually)\r\n\r\nExample: \r\n------------------------\r\n#unfolded comment\r\ndef foo:\r\n#folded comment\r\n    #also folded\r\n    bar = 5\r\n\r\n#unfolded, but the empty line above this one is folded with the function\r\n#code below will be folded\r\na = 5\r\nb = 6","4":"This script allows automatically folding of Python code.\r\nIt completely rewritten from Jorrit Wiersma's script (vimscript #515; other competitors are vimscript#781 and vimscript#2002).\r\nThe folding and fold text are completely rewritten: the algorithm systematically set up, so it behaves as accurate as possible (at the cost of some speed).\r\nMain feature of this script is that it folds empty space, saving lots of screen space (although you can turn it off, see below).\r\nClasses and defs are folded, of course.\r\nIndent zero comments separating classes and defs are not folded, so you see the global divisions in your code.\r\nGlobal code is folded in blocks (separated by comments).\r\n\r\nThere are three options. To use them, check the script:\r\n- Keep empty lines out of a fold (giving more readable classes with folded functions, but using more screen space).\r\n- Ignore non-python files.\r\n- Allow for multiline class definitions (at the cost of folding comments starting with the word \"class\") or stricter def checking (missing multiline defs).\r\n\r\nKnown bug:\r\n- multiline strings that look like code are handled as such (basically unfixable, actually)\r\n\r\nExample: \r\n------------------------\r\n#unfolded comment\r\ndef foo:\r\n#folded comment\r\n    #also folded\r\n    bar = 5\r\n\r\n#unfolded, but the empty line above this one is folded with the function\r\n#code below will be folded\r\na = 5\r\nb = 6","install_details":"Either save it in a file and source that file whenever you want to use the folding, or save it in your ftplugin directory (for example, ~\/.vim\/ftplugin\/python.vim) and it should load every time you edit python code.\r\nIf you want it to autodetect python code and ignore other code (which is probably what you want if you installed it in the ftplugin directory), uncomment the three lines denoted as such.\r\n","5":"Either save it in a file and source that file whenever you want to use the folding, or save it in your ftplugin directory (for example, ~\/.vim\/ftplugin\/python.vim) and it should load every time you edit python code.\r\nIf you want it to autodetect python code and ignore other code (which is probably what you want if you installed it in the ftplugin directory), uncomment the three lines denoted as such.\r\n","first_name":"Jurjen","6":"Jurjen","last_name":"Bos","7":"Bos","releases":[{"0":"2527","vim_version":"6.0","1":"6.0","script_version":"3.2","2":"3.2","version_comment":"Improved decorator recognition: now works with doxygen. (Thanks, Grissiom)\r\nBug removed. (Thanks, Andrew)","3":"Improved decorator recognition: now works with doxygen. (Thanks, Grissiom)\r\nBug removed. (Thanks, Andrew)","package":"jpythonfold.vim","4":"jpythonfold.vim","src_id":"10034","5":"10034","creation_date":"1235585593","6":"1235585593"},{"0":"2527","vim_version":"6.0","1":"6.0","script_version":"3.1","2":"3.1","version_comment":"Now also folds decorated functions and classes properly. Thanks for the idea, Kai.","3":"Now also folds decorated functions and classes properly. Thanks for the idea, Kai.","package":"jpythonfold.vim","4":"jpythonfold.vim","src_id":"9986","5":"9986","creation_date":"1234856525","6":"1234856525"},{"0":"2527","vim_version":"6.0","1":"6.0","script_version":"3.0.3","2":"3.0.3","version_comment":"Anothter bugfix: except\/else in global code doesn't introduce extra folds anymore. Thanks, Grissiom","3":"Anothter bugfix: except\/else in global code doesn't introduce extra folds anymore. Thanks, Grissiom","package":"jpythonfold.vim","4":"jpythonfold.vim","src_id":"9972","5":"9972","creation_date":"1234688683","6":"1234688683"},{"0":"2527","vim_version":"6.0","1":"6.0","script_version":"3.0.2","2":"3.0.2","version_comment":"Another bugfix: debug code removed. Thanks, Andrew","3":"Another bugfix: debug code removed. Thanks, Andrew","package":"jpythonfold.vim","4":"jpythonfold.vim","src_id":"9969","5":"9969","creation_date":"1234601660","6":"1234601660"},{"0":"2527","vim_version":"6.0","1":"6.0","script_version":"3.0.1","2":"3.0.1","version_comment":"Refactored everything again. Now not only faster, but also systematically set up. \r\nI actually try to explain everything in the script, in case you are interested :-) \r\nMinor bug fix over 3.0; thanks, Grissiom","3":"Refactored everything again. Now not only faster, but also systematically set up. \r\nI actually try to explain everything in the script, in case you are interested :-) \r\nMinor bug fix over 3.0; thanks, Grissiom","package":"jpythonfold.vim","4":"jpythonfold.vim","src_id":"9939","5":"9939","creation_date":"1234185503","6":"1234185503"},{"0":"2527","vim_version":"6.0","1":"6.0","script_version":"2.5","2":"2.5","version_comment":"Found a tiny bug: a function whose first line is a comment got folded wrong. Fixed it by removing (!) some code.","3":"Found a tiny bug: a function whose first line is a comment got folded wrong. Fixed it by removing (!) some code.","package":"jpythonfold.vim","4":"jpythonfold.vim","src_id":"9929","5":"9929","creation_date":"1234021726","6":"1234021726"},{"0":"2527","vim_version":"6.0","1":"6.0","script_version":"2.4","2":"2.4","version_comment":"Now expects a colon in a class definition, but not in a function definition, allowing for multiline defs (with explanation if you happen to disagree).\r\nStamped out a bug where sometimes global code gets folded in a class.\r\nSpeeded up a bit.","3":"Now expects a colon in a class definition, but not in a function definition, allowing for multiline defs (with explanation if you happen to disagree).\r\nStamped out a bug where sometimes global code gets folded in a class.\r\nSpeeded up a bit.","package":"jpythonfold.vim","4":"jpythonfold.vim","src_id":"9922","5":"9922","creation_date":"1233908173","6":"1233908173"},{"0":"2527","vim_version":"6.0","1":"6.0","script_version":"2.3","2":"2.3","version_comment":"Thanks to many helpful comment a brand new version, a bit less slow than 2.2.\r\nFolding accuracy is improved thanks to my quality control system (i.e. I made a test Python file handling all cases :-)","3":"Thanks to many helpful comment a brand new version, a bit less slow than 2.2.\r\nFolding accuracy is improved thanks to my quality control system (i.e. I made a test Python file handling all cases :-)","package":"jpythonfold.vim","4":"jpythonfold.vim","src_id":"9910","5":"9910","creation_date":"1233734723","6":"1233734723"},{"0":"2527","vim_version":"6.0","1":"6.0","script_version":"2.2","2":"2.2","version_comment":"Two silly bugs removed in foldtext, making version 2.1 unbearable.\r\nImproved script layout a bit.","3":"Two silly bugs removed in foldtext, making version 2.1 unbearable.\r\nImproved script layout a bit.","package":"jpythonfold.vim","4":"jpythonfold.vim","src_id":"9908","5":"9908","creation_date":"1233646823","6":"1233646823"},{"0":"2527","vim_version":"6.0","1":"6.0","script_version":"2.1","2":"2.1","version_comment":"(2.0 was too buggy)\r\nMajor rewrite; behaves more consistently in many borderline cases. Made more readable using an extra function. \r\nAlso handles docstrings with single quotes.","3":"(2.0 was too buggy)\r\nMajor rewrite; behaves more consistently in many borderline cases. Made more readable using an extra function. \r\nAlso handles docstrings with single quotes.","package":"jpythonfold.vim","4":"jpythonfold.vim","src_id":"9907","5":"9907","creation_date":"1233639320","6":"1233639320"},{"0":"2527","vim_version":"6.0","1":"6.0","script_version":"1.4","2":"1.4","version_comment":"Bugfix release: handles files with tabs, works even when foldcolumn or number is set.","3":"Bugfix release: handles files with tabs, works even when foldcolumn or number is set.","package":"jpythonfold.vim","4":"jpythonfold.vim","src_id":"9904","5":"9904","creation_date":"1233565541","6":"1233565541"},{"0":"2527","vim_version":"6.0","1":"6.0","script_version":"1.3","2":"1.3","version_comment":"Minor improvement giving dots between text and line count.","3":"Minor improvement giving dots between text and line count.","package":"jpythonfold.vim","4":"jpythonfold.vim","src_id":"9899","5":"9899","creation_date":"1233522700","6":"1233522700"},{"0":"2527","vim_version":"6.0","1":"6.0","script_version":"1.1","2":"1.1","version_comment":"Thanks to a few useful reactions, here is a new version.\r\n- It doesn't crash anymore if the script ends in empty lines or comments\r\n- There is (commented out) code for detecting and ignoring non-python scripts\r\n\r\n","3":"Thanks to a few useful reactions, here is a new version.\r\n- It doesn't crash anymore if the script ends in empty lines or comments\r\n- There is (commented out) code for detecting and ignoring non-python scripts\r\n\r\n","package":"jpythonfold.vim","4":"jpythonfold.vim","src_id":"9894","5":"9894","creation_date":"1233480377","6":"1233480377"}]},"2526":{"script_id":"2526","0":"2526","script_name":"Perl MooseX::Declare Syntax","1":"Perl MooseX::Declare Syntax","script_type":"syntax","2":"syntax","summary":"perl syntax with Moose and MooseX::Declare keywords","3":"perl syntax with Moose and MooseX::Declare keywords","description":"This is now a fork of alester's vim-perl at http:\/\/github.com\/petdance\/vim-perl\r\n\r\nOn GitHub: http:\/\/github.com\/rkitover\/perl-vim-mxd","4":"This is now a fork of alester's vim-perl at http:\/\/github.com\/petdance\/vim-perl\r\n\r\nOn GitHub: http:\/\/github.com\/rkitover\/perl-vim-mxd","install_details":"unzip into ~\/.vim","5":"unzip into ~\/.vim","first_name":"Rafael","6":"Rafael","last_name":"Kitover","7":"Kitover","releases":[{"0":"2526","vim_version":"7.0","1":"7.0","script_version":"0.23","2":"0.23","version_comment":"* merged upstream","3":"* merged upstream","package":"perl_vim.zip","4":"perl_vim.zip","src_id":"23277","5":"23277","creation_date":"1431741346","6":"1431741346"},{"0":"2526","vim_version":"7.0","1":"7.0","script_version":"0.22","2":"0.22","version_comment":"* merged upstream\r\n* add fc and evalbytes keywords (zdm) (Github issue #15)","3":"* merged upstream\r\n* add fc and evalbytes keywords (zdm) (Github issue #15)","package":"perl_vim.zip","4":"perl_vim.zip","src_id":"21231","5":"21231","creation_date":"1387797378","6":"1387797378"},{"0":"2526","vim_version":"7.0","1":"7.0","script_version":"0.21","2":"0.21","version_comment":"* match commas in perlcritic policy defs (zdm) #13","3":"* match commas in perlcritic policy defs (zdm) #13","package":"perl_vim.zip","4":"perl_vim.zip","src_id":"20721","5":"20721","creation_date":"1377644874","6":"1377644874"},{"0":"2526","vim_version":"7.0","1":"7.0","script_version":"0.20","2":"0.20","version_comment":"* merge latest vim-perl\r\n* perltidy and perlcritic highlights from zdm #13","3":"* merge latest vim-perl\r\n* perltidy and perlcritic highlights from zdm #13","package":"perl_vim.zip","4":"perl_vim.zip","src_id":"20703","5":"20703","creation_date":"1377221608","6":"1377221608"},{"0":"2526","vim_version":"7.0","1":"7.0","script_version":"0.19","2":"0.19","version_comment":"* merge latest vim-perl\r\n* add keywords from Error\/Error::Simple (cub-uanic)","3":"* merge latest vim-perl\r\n* add keywords from Error\/Error::Simple (cub-uanic)","package":"perl_vim.zip","4":"perl_vim.zip","src_id":"19995","5":"19995","creation_date":"1367431125","6":"1367431125"},{"0":"2526","vim_version":"7.0","1":"7.0","script_version":"0.18","2":"0.18","version_comment":"* merge latest vim-perl\r\n* keywords from Test::Deep (cubuanic)","3":"* merge latest vim-perl\r\n* keywords from Test::Deep (cubuanic)","package":"perl_vim.zip","4":"perl_vim.zip","src_id":"17757","5":"17757","creation_date":"1334171228","6":"1334171228"},{"0":"2526","vim_version":"7.0","1":"7.0","script_version":"0.17","2":"0.17","version_comment":"* add some missing Moose keywords\r\n* merge latest vim-perl\r\n* automatically turn on syn sync fromstart for small files","3":"* add some missing Moose keywords\r\n* merge latest vim-perl\r\n* automatically turn on syn sync fromstart for small files","package":"perl_vim.zip","4":"perl_vim.zip","src_id":"16856","5":"16856","creation_date":"1321130212","6":"1321130212"},{"0":"2526","vim_version":"6.0","1":"6.0","script_version":"0.16","2":"0.16","version_comment":"* fix comments before opening brace after a sub declaration","3":"* fix comments before opening brace after a sub declaration","package":"perl_vim.zip","4":"perl_vim.zip","src_id":"15500","5":"15500","creation_date":"1303431394","6":"1303431394"},{"0":"2526","vim_version":"6.0","1":"6.0","script_version":"0.15","2":"0.15","version_comment":"* fix comments before opening brace after a method signature","3":"* fix comments before opening brace after a method signature","package":"perl_vim.zip","4":"perl_vim.zip","src_id":"15494","5":"15494","creation_date":"1303396515","6":"1303396515"},{"0":"2526","vim_version":"6.0","1":"6.0","script_version":"0.14","2":"0.14","version_comment":"* merged with http:\/\/github.com\/petdance\/vim-perl\r\n* better support for parameterized roles (github issue #7)","3":"* merged with http:\/\/github.com\/petdance\/vim-perl\r\n* better support for parameterized roles (github issue #7)","package":"perl_vim.zip","4":"perl_vim.zip","src_id":"15275","5":"15275","creation_date":"1300786885","6":"1300786885"},{"0":"2526","vim_version":"6.0","1":"6.0","script_version":"0.13","2":"0.13","version_comment":"* more Test::* keywords","3":"* more Test::* keywords","package":"perl_vim.zip","4":"perl_vim.zip","src_id":"14793","5":"14793","creation_date":"1295473512","6":"1295473512"},{"0":"2526","vim_version":"6.0","1":"6.0","script_version":"0.12","2":"0.12","version_comment":"* better POD highlighting from cub-uanic","3":"* better POD highlighting from cub-uanic","package":"perl_vim.zip","4":"perl_vim.zip","src_id":"14682","5":"14682","creation_date":"1294199850","6":"1294199850"},{"0":"2526","vim_version":"6.0","1":"6.0","script_version":"0.11","2":"0.11","version_comment":"* some new keywords from cub-uanic on github","3":"* some new keywords from cub-uanic on github","package":"perl.vim","4":"perl.vim","src_id":"14528","5":"14528","creation_date":"1292497484","6":"1292497484"},{"0":"2526","vim_version":"6.0","1":"6.0","script_version":"0.10","2":"0.10","version_comment":"* fix using a variable as method name (xenoterracide)\r\n* add Try::Tiny keywords","3":"* fix using a variable as method name (xenoterracide)\r\n* add Try::Tiny keywords","package":"perl.vim","4":"perl.vim","src_id":"13403","5":"13403","creation_date":"1280049077","6":"1280049077"},{"0":"2526","vim_version":"6.0","1":"6.0","script_version":"0.09","2":"0.09","version_comment":"Fixed POD sync bug.","3":"Fixed POD sync bug.","package":"perl.vim","4":"perl.vim","src_id":"11458","5":"11458","creation_date":"1254290654","6":"1254290654"},{"0":"2526","vim_version":"6.0","1":"6.0","script_version":"0.08","2":"0.08","version_comment":"Better defaults, added Test::* keywords","3":"Better defaults, added Test::* keywords","package":"perl.vim","4":"perl.vim","src_id":"10594","5":"10594","creation_date":"1242359298","6":"1242359298"},{"0":"2526","vim_version":"6.0","1":"6.0","script_version":"0.07","2":"0.07","version_comment":"Added a couple more keywords..","3":"Added a couple more keywords..","package":"perl.vim","4":"perl.vim","src_id":"10548","5":"10548","creation_date":"1241615838","6":"1241615838"},{"0":"2526","vim_version":"6.0","1":"6.0","script_version":"0.06","2":"0.06","version_comment":"Moved all Moose stuff to it's own section at the top of file. Fixed quoted method modifiers.","3":"Moved all Moose stuff to it's own section at the top of file. Fixed quoted method modifiers.","package":"perl.vim","4":"perl.vim","src_id":"10539","5":"10539","creation_date":"1241572369","6":"1241572369"},{"0":"2526","vim_version":"6.0","1":"6.0","script_version":"0.05","2":"0.05","version_comment":"Fixed code attributes on methods, added type library keywords.","3":"Fixed code attributes on methods, added type library keywords.","package":"perl.vim","4":"perl.vim","src_id":"10526","5":"10526","creation_date":"1241477830","6":"1241477830"}]},"2525":{"script_id":"2525","0":"2525","script_name":"Thousand separator","1":"Thousand separator","script_type":"utility","2":"utility","summary":"Vim script to put thousand separator in between numbers.","3":"Vim script to put thousand separator in between numbers.","description":"Vim script to put thousand separator in between numbers to make them more readable. E.g. 125668899 => 125 668 899 \r\n","4":"Vim script to put thousand separator in between numbers to make them more readable. E.g. 125668899 => 125 668 899 \r\n","install_details":"No installation required. Run it with :so","5":"No installation required. Run it with :so","first_name":"Lubomir","6":"Lubomir","last_name":"Husar","7":"Husar","releases":[{"0":"2525","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"number_thousands_separator.vim","4":"number_thousands_separator.vim","src_id":"9864","5":"9864","creation_date":"1232984798","6":"1232984798"}]},"2524":{"script_id":"2524","0":"2524","script_name":"Scratch*","1":"Scratch*","script_type":"utility","2":"utility","summary":"Create and use scratch buffers in useful ways","3":"Create and use scratch buffers in useful ways","description":"Short (< 50 lines) plugin to create scratch buffers.\r\n\r\nScratch buffers are used to create new commands:\r\n\r\n* ScratchDiff ... compare current buffer against new scratch\r\n* ScratchFind ... runs a \"find\" command and outputs result in a new scratch\r\n\r\nScratchFind is used to emulate most of the functionality of command-t in TextMate.\r\n\r\nConfigure ScratchFind's behavior with the g:scratch_find_command variable.\r\n\r\nReview the code: http:\/\/github.com\/jpalardy\/etc_config\/blob\/dce22368aacc842ef6db058280e5fdf3057c0b12\/vim\/plugin\/scratch.vim","4":"Short (< 50 lines) plugin to create scratch buffers.\r\n\r\nScratch buffers are used to create new commands:\r\n\r\n* ScratchDiff ... compare current buffer against new scratch\r\n* ScratchFind ... runs a \"find\" command and outputs result in a new scratch\r\n\r\nScratchFind is used to emulate most of the functionality of command-t in TextMate.\r\n\r\nConfigure ScratchFind's behavior with the g:scratch_find_command variable.\r\n\r\nReview the code: http:\/\/github.com\/jpalardy\/etc_config\/blob\/dce22368aacc842ef6db058280e5fdf3057c0b12\/vim\/plugin\/scratch.vim","install_details":"Drop in ~\/.vim\/plugin","5":"Drop in ~\/.vim\/plugin","first_name":"Jonathan","6":"Jonathan","last_name":"Palardy","7":"Palardy","releases":[{"0":"2524","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"scratch.vim","4":"scratch.vim","src_id":"9859","5":"9859","creation_date":"1232898156","6":"1232898156"}]},"2523":{"script_id":"2523","0":"2523","script_name":"Jifty syntax","1":"Jifty syntax","script_type":"syntax","2":"syntax","summary":"syntax file for jifty web framework","3":"syntax file for jifty web framework","description":"syntax support of jifty web framework ( http:\/\/search.cpan.org\/~sartak\/Jifty-0.80408\/ )\r\n\r\n  * template syntax , folding\r\n  * model \/ action schema syntax , folding\r\n  * schema keywords\r\n  * functions keywords\r\n  * syntax highlight for sql, js , html embedded hereDoc\r\n\r\nto turn on the syntax folding to fold template and schema columns:\r\n\r\n  set fdm=syntax\r\n\r\noptions: you can choose what you want to fold, append following lines to your .vimrc\r\n\r\n   let jifty_fold_schema = 1\r\n   let jifty_fold_schema_column = 1\r\n   let jifty_fold_template = 1\r\n   let jifty_fold_tags = 1\r\n   let jifty_fold_dispatcher = 1\r\n\r\nSupports sql,javascript,html embedded hereDoc string:\r\n  you can add prefix to the identifier like SQL.. , HTML... , JS...\r\n  e.g.\r\n\r\n  $sql =<<SQL123\r\n    select * from books\r\nSQL123\r\n  \r\n  or \r\n\r\n  $html =<<HTML123\r\n  <html>\r\n      <h1>Jifty<\/h1>\r\n  <\/html>\r\nHTML123\r\n\r\n\r\npatches are welcome.  :)\r\n\r\ncornelius.howl+vim {at} gmail.com\r\n","4":"syntax support of jifty web framework ( http:\/\/search.cpan.org\/~sartak\/Jifty-0.80408\/ )\r\n\r\n  * template syntax , folding\r\n  * model \/ action schema syntax , folding\r\n  * schema keywords\r\n  * functions keywords\r\n  * syntax highlight for sql, js , html embedded hereDoc\r\n\r\nto turn on the syntax folding to fold template and schema columns:\r\n\r\n  set fdm=syntax\r\n\r\noptions: you can choose what you want to fold, append following lines to your .vimrc\r\n\r\n   let jifty_fold_schema = 1\r\n   let jifty_fold_schema_column = 1\r\n   let jifty_fold_template = 1\r\n   let jifty_fold_tags = 1\r\n   let jifty_fold_dispatcher = 1\r\n\r\nSupports sql,javascript,html embedded hereDoc string:\r\n  you can add prefix to the identifier like SQL.. , HTML... , JS...\r\n  e.g.\r\n\r\n  $sql =<<SQL123\r\n    select * from books\r\nSQL123\r\n  \r\n  or \r\n\r\n  $html =<<HTML123\r\n  <html>\r\n      <h1>Jifty<\/h1>\r\n  <\/html>\r\nHTML123\r\n\r\n\r\npatches are welcome.  :)\r\n\r\ncornelius.howl+vim {at} gmail.com\r\n","install_details":"Download the tarball to your home , then untar it\r\n\r\ntar xvf jifty.tar.gz\r\n\r\nthis will extract files to \r\n\r\n  ~\/.vim\/after\/syntax\/perl\/jifty.vim\r\n  ~\/.vim\/syntax\/perl.vim\r\n\r\nmake sure that your files wont be overwrited.\r\n","5":"Download the tarball to your home , then untar it\r\n\r\ntar xvf jifty.tar.gz\r\n\r\nthis will extract files to \r\n\r\n  ~\/.vim\/after\/syntax\/perl\/jifty.vim\r\n  ~\/.vim\/syntax\/perl.vim\r\n\r\nmake sure that your files wont be overwrited.\r\n","first_name":"Yo-An","6":"Yo-An","last_name":"Lin","7":"Lin","releases":[{"0":"2523","vim_version":"6.0","1":"6.0","script_version":"0.22","2":"0.22","version_comment":"highlight quoted identifier of heredoc.","3":"highlight quoted identifier of heredoc.","package":"jifty.tar.gz","4":"jifty.tar.gz","src_id":"9868","5":"9868","creation_date":"1233029292","6":"1233029292"},{"0":"2523","vim_version":"6.0","1":"6.0","script_version":"0.21","2":"0.21","version_comment":"* provide dispatcher folding\r\n* fix html embedded heredoc syntax highlight","3":"* provide dispatcher folding\r\n* fix html embedded heredoc syntax highlight","package":"jifty.tar.gz","4":"jifty.tar.gz","src_id":"9860","5":"9860","creation_date":"1232901234","6":"1232901234"},{"0":"2523","vim_version":"6.0","1":"6.0","script_version":"0.2","2":"0.2","version_comment":"* let heredoc supports sql, javascript, html syntax.\r\n* fold div , table , form ..tags\r\n* provide options for folding , you can choose what you want to fold\r\n   let jifty_fold_schema = 1\r\n   let jifty_fold_schema_column = 1\r\n   let jifty_fold_template = 1\r\n   let jifty_fold_tags = 1\r\n* move jifty.vim to ~\/.vim\/after\/syntax\/perl\/jifty.vim , not\r\n       ~\/.vim\/after\/syntax\/jifty.vim\r\n","3":"* let heredoc supports sql, javascript, html syntax.\r\n* fold div , table , form ..tags\r\n* provide options for folding , you can choose what you want to fold\r\n   let jifty_fold_schema = 1\r\n   let jifty_fold_schema_column = 1\r\n   let jifty_fold_template = 1\r\n   let jifty_fold_tags = 1\r\n* move jifty.vim to ~\/.vim\/after\/syntax\/perl\/jifty.vim , not\r\n       ~\/.vim\/after\/syntax\/jifty.vim\r\n","package":"jifty.tar.gz","4":"jifty.tar.gz","src_id":"9858","5":"9858","creation_date":"1232897439","6":"1232897439"},{"0":"2523","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"fix syntax error.","3":"fix syntax error.","package":"jifty.vim","4":"jifty.vim","src_id":"9857","5":"9857","creation_date":"1232865646","6":"1232865646"}]},"2522":{"script_id":"2522","0":"2522","script_name":"wokmarks.vim","1":"wokmarks.vim","script_type":"utility","2":"utility","summary":"local marks usage more similar to other editors","3":"local marks usage more similar to other editors","description":"Lets you set and toggle a mark on a line without specifying which mark to use exactly.  wokmarks will choose an unused mark from a pool of allowed marks.  The script is quite verbose: you will get info which mark was set, removed or jumped to.\r\n\r\n\r\nUsage: (default keys)\r\n\r\ntm\r\nset pool mark for current line (if no local mark exists)\r\n\r\ntt\r\ntoggle pool mark for current line\r\n\r\ntk\r\ntj\r\njump to the [count]th local mark above\/below the cursor position (like [' and ]' which are less verbose).\r\nWithout count, the search for marks wraps around the buffer boundaries.\r\n\r\ntl\r\nlist local marks\r\n\r\ntD\r\nremove all pool marks from the buffer or pool marks in range\r\n\r\n\"t\" actually is a built-in command; see below if you want to map other keys in the vimrc.\r\nLocal marks = pool marks + user marks.  User marks will not be set or removed by the script.\r\n\r\nv0.3: The toggle hook will be executed whenever wokmarks adds or removes marks.  Purpose is to be able to update external marks highlighting etc.  Add a command to the hook:\r\n\r\n     :autocmd User WokmarksChange   :MyMarksHighlightingUpdate\r\n\r\nThis must not be wrapped in an augroup -- this way you can define the autocmd before wokmarks is loaded.\r\n\r\n\r\nCustomization:\r\n\r\n:let g:wokmarks_pool = \"abcdfghijklmnopqrtuvwxyz\"\r\n(string)\r\nPool of allowed marks.  The marks s and e excluded here (user marks), they are commonly used for start and end positions.\r\n\r\n:let g:wokmarks_do_maps = 1\r\n(number)\r\nValues:\r\n0    don't map any keys\r\n1    map the default keys\r\n2    map Ctrl-F2 to toggle a mark, and  F2 \/ Shift-F2 to jump to the next or previous mark\r\n\r\nThe default keys are being mapped this way:\r\n:map tk <Plug>PrevMarkWok\r\n:map tj <Plug>NextMarkWok\r\n:nmap tt <Plug>ToggleMarkWok\r\n:nmap tm <Plug>SetMarkWok\r\n:map tD <Plug>KillMarksWok\r\n:nnoremap <silent> tl :marks abcdefghijklmnopqrstuvwxyz<CR>\r\n\r\n\r\nCredits must go to vimscript #66\r\n\r\n2010 Mar 28","4":"Lets you set and toggle a mark on a line without specifying which mark to use exactly.  wokmarks will choose an unused mark from a pool of allowed marks.  The script is quite verbose: you will get info which mark was set, removed or jumped to.\r\n\r\n\r\nUsage: (default keys)\r\n\r\ntm\r\nset pool mark for current line (if no local mark exists)\r\n\r\ntt\r\ntoggle pool mark for current line\r\n\r\ntk\r\ntj\r\njump to the [count]th local mark above\/below the cursor position (like [' and ]' which are less verbose).\r\nWithout count, the search for marks wraps around the buffer boundaries.\r\n\r\ntl\r\nlist local marks\r\n\r\ntD\r\nremove all pool marks from the buffer or pool marks in range\r\n\r\n\"t\" actually is a built-in command; see below if you want to map other keys in the vimrc.\r\nLocal marks = pool marks + user marks.  User marks will not be set or removed by the script.\r\n\r\nv0.3: The toggle hook will be executed whenever wokmarks adds or removes marks.  Purpose is to be able to update external marks highlighting etc.  Add a command to the hook:\r\n\r\n     :autocmd User WokmarksChange   :MyMarksHighlightingUpdate\r\n\r\nThis must not be wrapped in an augroup -- this way you can define the autocmd before wokmarks is loaded.\r\n\r\n\r\nCustomization:\r\n\r\n:let g:wokmarks_pool = \"abcdfghijklmnopqrtuvwxyz\"\r\n(string)\r\nPool of allowed marks.  The marks s and e excluded here (user marks), they are commonly used for start and end positions.\r\n\r\n:let g:wokmarks_do_maps = 1\r\n(number)\r\nValues:\r\n0    don't map any keys\r\n1    map the default keys\r\n2    map Ctrl-F2 to toggle a mark, and  F2 \/ Shift-F2 to jump to the next or previous mark\r\n\r\nThe default keys are being mapped this way:\r\n:map tk <Plug>PrevMarkWok\r\n:map tj <Plug>NextMarkWok\r\n:nmap tt <Plug>ToggleMarkWok\r\n:nmap tm <Plug>SetMarkWok\r\n:map tD <Plug>KillMarksWok\r\n:nnoremap <silent> tl :marks abcdefghijklmnopqrstuvwxyz<CR>\r\n\r\n\r\nCredits must go to vimscript #66\r\n\r\n2010 Mar 28","install_details":"rename the file to wokmarks.vim\r\nthis is a global plugin, :h add-plugin","5":"rename the file to wokmarks.vim\r\nthis is a global plugin, :h add-plugin","first_name":"Andy","6":"Andy","last_name":"Wokula","7":"Wokula","releases":[{"0":"2522","vim_version":"7.0","1":"7.0","script_version":"0.3.1","2":"0.3.1","version_comment":"- fix: the hook executed modelines (via :doautocmd, wtf?); reset 'modeline'","3":"- fix: the hook executed modelines (via :doautocmd, wtf?); reset 'modeline'","package":"wokmarks_0.3.1.vim","4":"wokmarks_0.3.1.vim","src_id":"13601","5":"13601","creation_date":"1282065900","6":"1282065900"},{"0":"2522","vim_version":"7.0","1":"7.0","script_version":"0.3","2":"0.3","version_comment":"- added toggle hook (:au User WokmarksChange) (Tom Link)\r\n- added Wokmarks_GetLocalMarks() ","3":"- added toggle hook (:au User WokmarksChange) (Tom Link)\r\n- added Wokmarks_GetLocalMarks() ","package":"wokmarks_0.3.vim","4":"wokmarks_0.3.vim","src_id":"12731","5":"12731","creation_date":"1269810182","6":"1269810182"},{"0":"2522","vim_version":"7.0","1":"7.0","script_version":"0.2","2":"0.2","version_comment":"- tj tk set the ' mark, to allow jumping back with CTRL-O\r\n- added Omap mode for <Plug>NextMarkWok, <Plug>PrevMarkWok\r\n- let Wokmarks_GetMark() also accept \".\", \"$\", etc.\r\n- if g:wokmarks_do_maps == 2, then F2 maps are used (Tom Link)\r\n- prev\/next mark searches wrap around (Tom Link)","3":"- tj tk set the ' mark, to allow jumping back with CTRL-O\r\n- added Omap mode for <Plug>NextMarkWok, <Plug>PrevMarkWok\r\n- let Wokmarks_GetMark() also accept \".\", \"$\", etc.\r\n- if g:wokmarks_do_maps == 2, then F2 maps are used (Tom Link)\r\n- prev\/next mark searches wrap around (Tom Link)","package":"wokmarks_0.2.vim","4":"wokmarks_0.2.vim","src_id":"11643","5":"11643","creation_date":"1257117267","6":"1257117267"},{"0":"2522","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"wokmarks_0.1.vim","4":"wokmarks_0.1.vim","src_id":"9851","5":"9851","creation_date":"1232640937","6":"1232640937"}]},"2521":{"script_id":"2521","0":"2521","script_name":"searchfold.vim","1":"searchfold.vim","script_type":"utility","2":"utility","summary":"Fold away lines not matching the last search pattern","3":"Fold away lines not matching the last search pattern","description":"This script is an improved version of  f.vim  (vimscript #318).\r\n\r\nImprovements: folding depth is limited, previous fold settings can be restored, pattern is always the last search pattern.\r\n\r\nScript uses manual folds.  The user's manual folds are not preserved (unlike vimscript #2302 does it).\r\n\r\n\r\nUsage:\r\n\r\n<Leader>z\r\nfold away lines not matching the last search pattern.\r\nWith [count], change the initial foldlevel to ([count] minus one).  The setting will be stored in g:searchfold_foldlevel and will be used when [count] is omitted.\r\n\r\n<Leader>iz\r\nfold away lines that do match the last search pattern (inverse folding).\r\n\r\n<Leader>Z\r\ntry hard to restore the previous fold settings\r\n\r\n\r\n\r\nCustomization:\r\n\r\n:let g:searchfold_maxdepth = 7\r\n(number) maximum fold depth\r\n\r\n:let g:searchfold_usestep = 1\r\n(boolean)\r\nControls how folds are organized: If 1 (default), each \"zr\" (after \"\\z\") unfolds the same amount of lines above and below a match.  If 0, only one more line is unfolded above a match.  This applies for next \"\\z\" or \"\\iz\".\r\n\r\n:let g:searchfold_postZ_do_zv = 1\r\n(boolean)\r\nIf 1, execute \"zv\" (view cursor line) after <Leader>Z.\r\n\r\n:let g:searchfold_foldlevel = 0\r\n(number)\r\nInitial 'foldlevel' to set for <Leader>z and <Leader>iz\r\n\r\n:let g:searchfold_do_maps = 1\r\n(boolean)\r\nWhether to map the default keys or not.\r\n\r\n\r\n\r\nA few more links to check out:\r\n- http:\/\/www.noah.org\/wiki\/Vim#Folding\r\n- vimscript #158 (foldutil.vim)\r\n- vimscript #578 (allfold.tar.gz)\r\n\r\n2011 May 24","4":"This script is an improved version of  f.vim  (vimscript #318).\r\n\r\nImprovements: folding depth is limited, previous fold settings can be restored, pattern is always the last search pattern.\r\n\r\nScript uses manual folds.  The user's manual folds are not preserved (unlike vimscript #2302 does it).\r\n\r\n\r\nUsage:\r\n\r\n<Leader>z\r\nfold away lines not matching the last search pattern.\r\nWith [count], change the initial foldlevel to ([count] minus one).  The setting will be stored in g:searchfold_foldlevel and will be used when [count] is omitted.\r\n\r\n<Leader>iz\r\nfold away lines that do match the last search pattern (inverse folding).\r\n\r\n<Leader>Z\r\ntry hard to restore the previous fold settings\r\n\r\n\r\n\r\nCustomization:\r\n\r\n:let g:searchfold_maxdepth = 7\r\n(number) maximum fold depth\r\n\r\n:let g:searchfold_usestep = 1\r\n(boolean)\r\nControls how folds are organized: If 1 (default), each \"zr\" (after \"\\z\") unfolds the same amount of lines above and below a match.  If 0, only one more line is unfolded above a match.  This applies for next \"\\z\" or \"\\iz\".\r\n\r\n:let g:searchfold_postZ_do_zv = 1\r\n(boolean)\r\nIf 1, execute \"zv\" (view cursor line) after <Leader>Z.\r\n\r\n:let g:searchfold_foldlevel = 0\r\n(number)\r\nInitial 'foldlevel' to set for <Leader>z and <Leader>iz\r\n\r\n:let g:searchfold_do_maps = 1\r\n(boolean)\r\nWhether to map the default keys or not.\r\n\r\n\r\n\r\nA few more links to check out:\r\n- http:\/\/www.noah.org\/wiki\/Vim#Folding\r\n- vimscript #158 (foldutil.vim)\r\n- vimscript #578 (allfold.tar.gz)\r\n\r\n2011 May 24","install_details":"this is a global plugin, :h add-plugin\r\n\r\nwhich means:\r\n- remove the version part \"_0.9\" from the file name (optional)\r\n- drop the script file into your plugin folder (e.g. ~\/vimfiles\/plugin) and restart Vim, or :source the script manually","5":"this is a global plugin, :h add-plugin\r\n\r\nwhich means:\r\n- remove the version part \"_0.9\" from the file name (optional)\r\n- drop the script file into your plugin folder (e.g. ~\/vimfiles\/plugin) and restart Vim, or :source the script manually","first_name":"Andy","6":"Andy","last_name":"Wokula","7":"Wokula","releases":[{"0":"2521","vim_version":"7.0","1":"7.0","script_version":"0.9","2":"0.9","version_comment":"renamed <Plug>SearchFoldDisable, fixed g:searchfold_usestep description (wrong default), removed annoying redraw","3":"renamed <Plug>SearchFoldDisable, fixed g:searchfold_usestep description (wrong default), removed annoying redraw","package":"searchfold_0.9.vim","4":"searchfold_0.9.vim","src_id":"15711","5":"15711","creation_date":"1306246015","6":"1306246015"},{"0":"2521","vim_version":"7.0","1":"7.0","script_version":"0.8","2":"0.8","version_comment":"added inverse folding (<Leader>iz), g:searchfold_foldlevel, count for <Leader>z, <Plug> mappings, disabled F(), minor fixes","3":"added inverse folding (<Leader>iz), g:searchfold_foldlevel, count for <Leader>z, <Plug> mappings, disabled F(), minor fixes","package":"searchfold_0.8.vim","4":"searchfold_0.8.vim","src_id":"13960","5":"13960","creation_date":"1285848967","6":"1285848967"},{"0":"2521","vim_version":"7.0","1":"7.0","script_version":"0.7","2":"0.7","version_comment":"Initial upload","3":"Initial upload","package":"searchfold_0.7.vim","4":"searchfold_0.7.vim","src_id":"9850","5":"9850","creation_date":"1232640026","6":"1232640026"}]},"2520":{"script_id":"2520","0":"2520","script_name":"reorder tabs","1":"reorder tabs","script_type":"utility","2":"utility","summary":"Reorder your tabs in a simple way.","3":"Reorder your tabs in a simple way.","description":"Use <M-PageUp> and <M-PageDown> to move the current tab to the next position.","4":"Use <M-PageUp> and <M-PageDown> to move the current tab to the next position.","install_details":"Put this file (reorder_tabs.vim) in your plugin directory.","5":"Put this file (reorder_tabs.vim) in your plugin directory.","first_name":"Gregor","6":"Gregor","last_name":"M\u00c3\u00bcllegger","7":"M\u00c3\u00bcllegger","releases":[{"0":"2520","vim_version":"6.0","1":"6.0","script_version":"0.1.0","2":"0.1.0","version_comment":"Initial upload","3":"Initial upload","package":"reorder_tabs.vim","4":"reorder_tabs.vim","src_id":"9846","5":"9846","creation_date":"1232412420","6":"1232412420"}]},"2519":{"script_id":"2519","0":"2519","script_name":"Dpaste.com Plugin","1":"Dpaste.com Plugin","script_type":"utility","2":"utility","summary":"A simple script to send your buffer or selection to Dpaste.com and returns a url","3":"A simple script to send your buffer or selection to Dpaste.com and returns a url","description":"dpaste.vim is a vim plugin for pasting to dpaste.com (#django's favourite paste bin!)\r\n\r\nThe core of the script was inspired by LodgeIt.vim, which is also for a paste bin site. \r\n\r\nThanks to Paul Bissex (or pbx on irc) for creating dpaste.\r\n\r\nUsage:\r\n- :Dpaste  (create a paste from the current buffer or selection)\r\n\r\nYou can also map paste to CTRL + P, just add this to your .vimrc:\r\nmap ^P :Dpaste<CR>\r\n(where ^P is entered using CTRL + V, CTRL + P in Vim)\r\n","4":"dpaste.vim is a vim plugin for pasting to dpaste.com (#django's favourite paste bin!)\r\n\r\nThe core of the script was inspired by LodgeIt.vim, which is also for a paste bin site. \r\n\r\nThanks to Paul Bissex (or pbx on irc) for creating dpaste.\r\n\r\nUsage:\r\n- :Dpaste  (create a paste from the current buffer or selection)\r\n\r\nYou can also map paste to CTRL + P, just add this to your .vimrc:\r\nmap ^P :Dpaste<CR>\r\n(where ^P is entered using CTRL + V, CTRL + P in Vim)\r\n","install_details":"Place dpaste.vim in your ~\/.vim\/plugin directory","5":"Place dpaste.vim in your ~\/.vim\/plugin directory","first_name":"Bartek","6":"Bartek","last_name":"Ciszkowski","7":"Ciszkowski","releases":[{"0":"2519","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial version, has been fixed up since last time a bit more :)","3":"Initial version, has been fixed up since last time a bit more :)","package":"dpaste.vim","4":"dpaste.vim","src_id":"10222","5":"10222","creation_date":"1237205394","6":"1237205394"}]},"2518":{"script_id":"2518","0":"2518","script_name":"WOIM.vim","1":"WOIM.vim","script_type":"ftplugin","2":"ftplugin","summary":"WOIM outliner (replaced by HyperList: Script# 4006)","3":"WOIM outliner (replaced by HyperList: Script# 4006)","description":"THIS PLUGIN HAS BEEN REPLACED WITH THE HYPERLIST PLUGIN - SEE: http:\/\/www.vim.org\/scripts\/script.php?script_id=4006\r\n\r\n\r\n\r\nIt's an Outliner, a TODO-list solution, a project management tool, a Business Process Management aid, a data modeler, a Use Case facilitator, a way to describe the human DNA or the history of the universe ;) It can also encrypt your lists and be used as a very structured  password safe.\r\n\r\nWOIM is a methodology to describe anything - any state, item(s), pattern, action, process, transition, program, instruction set etc.\r\n\r\nThis plugin does both highlighting and various automatic handling of WOIM lists, like collapsing lists or parts of lists in a sophisticated way.\r\n\r\nThe plugin incorporates encryption. You can encrypt any part of a WOIM list or take advantage of the autoencryption feature by making the WOIM list a dot file - i.e. prefixing the file name with a dot (such as \".test.woim\"). You can use this plugin to make a password safe - it turns off viminfo and swap files to ensure security.\r\n\r\nFor information on WOIM, read the WOIM description in full:\r\n\r\n http:\/\/isene.com\/woim.pdf\r\n\r\nINSTRUCTIONS\r\n\r\nUse tabs\/shifts or * for indentations\r\n\r\nUse <SPACE> to toggle one fold\r\nUse \\0 to \\9, \\a, \\b, \\c, \\d, \\e, \\f to show up to 15 levels expanded\r\n\r\nUse <leader>s to remove underlining of States (prefixed with S:)\r\nUse <leader>S to add underlining of States (prefixed with S:)\r\nUse <leader>t to remove underlining of Transitions (prefixed with T:)\r\nUse <leader>T to add underlining of Transitions (prefixed with T:)\r\n\r\nUse <leader>v to add a checkbox at start of item or to toggle a checkbox\r\nUse <leader>V to add\/toggle a checkbox with a date stamp for completion\r\n\r\nUse \"gr\" (without the quotation marks, signifies \"Goto Ref\") while the cursor is on a WOIM reference to jump to that destination in a WOIM list. Use \"n\" after a \"gr\" to verify that the reference destination is unique. A reference can be in the list or to a file by the use of #file:\/pathto\/filename, #file:~\/filename or #file:filename.\r\n\r\nUse <leader><SPACE> to go to the next open template element (a template element is a WOIM item ending in an equal sign)\r\n\r\nAs a sort of \"presentation mode\", you can traverse a WOIM list by using g<DOWN> or g<UP> to view only the current line and its ancestors. An alternative is <leader><DOWN> and <leader><UP> to open more levels down.\r\n\r\nUse <leader>L to convert the entire document to LaTaX\r\n\r\nThe LaTeX conversion includes color coding of the various elements similar to the colors used for WOIM files within VIM.\r\n\r\nUse <leader>z to encrypt the current line (including all sublevels if folded)\r\nUse <leader>Z to encrypt the current file (all lines)\r\nUse <leader>x to decrypt the current line (mark all subsequent encrypted lines)\r\nUse <leader>X to decrypt the current file (all lines)\r\n\r\nIf you want a WOIM list to be automatically encrypted upon saving and decrypted upon opening it, just prefix the filename with a dot (like \".test.woim\").\r\n\r\nWhen using encryption in a WOIM list or for the whole file, you will be asked for a password - twice when saving the file and once when opening it. You must have OpenSSL in your path to take advantage of these features.\r\n\r\nSyntax updated at start and every time you leave Insert mode\r\n\r\nTo use a WOIM list within any other file type, you can use nested syntax. Add the following to that other syntax highlighting plugin file:\r\n\r\n  syn include @WOIM ~\/.vim\/syntax\/woim.vim\r\n  syn region WoimSnip matchgroup=Snip start=\"WOIMstart\" end=\"WOIMend\" contains=@WOIM\r\n  hi link Snip SpecialComment\r\n\r\nIf you add those three lines in your .vim\/syntax\/txt.vim you will be able to include WOIM lists in files with a .txt extension like this:\r\n\r\nWOIMstart\r\nThis is a WOIM test list\r\n  Here is a child to the above item\r\n    Here is \"grand child\"\r\n  Here we are one level back\r\n    And here's another level down\r\n    [5] Dance steps\r\n    [3] Hurray\r\n    Smile\r\nWOIMend\r\n\r\nThe \"WOIMstart\" and \"WOIMend\" must be at the start of the line.\r\n","4":"THIS PLUGIN HAS BEEN REPLACED WITH THE HYPERLIST PLUGIN - SEE: http:\/\/www.vim.org\/scripts\/script.php?script_id=4006\r\n\r\n\r\n\r\nIt's an Outliner, a TODO-list solution, a project management tool, a Business Process Management aid, a data modeler, a Use Case facilitator, a way to describe the human DNA or the history of the universe ;) It can also encrypt your lists and be used as a very structured  password safe.\r\n\r\nWOIM is a methodology to describe anything - any state, item(s), pattern, action, process, transition, program, instruction set etc.\r\n\r\nThis plugin does both highlighting and various automatic handling of WOIM lists, like collapsing lists or parts of lists in a sophisticated way.\r\n\r\nThe plugin incorporates encryption. You can encrypt any part of a WOIM list or take advantage of the autoencryption feature by making the WOIM list a dot file - i.e. prefixing the file name with a dot (such as \".test.woim\"). You can use this plugin to make a password safe - it turns off viminfo and swap files to ensure security.\r\n\r\nFor information on WOIM, read the WOIM description in full:\r\n\r\n http:\/\/isene.com\/woim.pdf\r\n\r\nINSTRUCTIONS\r\n\r\nUse tabs\/shifts or * for indentations\r\n\r\nUse <SPACE> to toggle one fold\r\nUse \\0 to \\9, \\a, \\b, \\c, \\d, \\e, \\f to show up to 15 levels expanded\r\n\r\nUse <leader>s to remove underlining of States (prefixed with S:)\r\nUse <leader>S to add underlining of States (prefixed with S:)\r\nUse <leader>t to remove underlining of Transitions (prefixed with T:)\r\nUse <leader>T to add underlining of Transitions (prefixed with T:)\r\n\r\nUse <leader>v to add a checkbox at start of item or to toggle a checkbox\r\nUse <leader>V to add\/toggle a checkbox with a date stamp for completion\r\n\r\nUse \"gr\" (without the quotation marks, signifies \"Goto Ref\") while the cursor is on a WOIM reference to jump to that destination in a WOIM list. Use \"n\" after a \"gr\" to verify that the reference destination is unique. A reference can be in the list or to a file by the use of #file:\/pathto\/filename, #file:~\/filename or #file:filename.\r\n\r\nUse <leader><SPACE> to go to the next open template element (a template element is a WOIM item ending in an equal sign)\r\n\r\nAs a sort of \"presentation mode\", you can traverse a WOIM list by using g<DOWN> or g<UP> to view only the current line and its ancestors. An alternative is <leader><DOWN> and <leader><UP> to open more levels down.\r\n\r\nUse <leader>L to convert the entire document to LaTaX\r\n\r\nThe LaTeX conversion includes color coding of the various elements similar to the colors used for WOIM files within VIM.\r\n\r\nUse <leader>z to encrypt the current line (including all sublevels if folded)\r\nUse <leader>Z to encrypt the current file (all lines)\r\nUse <leader>x to decrypt the current line (mark all subsequent encrypted lines)\r\nUse <leader>X to decrypt the current file (all lines)\r\n\r\nIf you want a WOIM list to be automatically encrypted upon saving and decrypted upon opening it, just prefix the filename with a dot (like \".test.woim\").\r\n\r\nWhen using encryption in a WOIM list or for the whole file, you will be asked for a password - twice when saving the file and once when opening it. You must have OpenSSL in your path to take advantage of these features.\r\n\r\nSyntax updated at start and every time you leave Insert mode\r\n\r\nTo use a WOIM list within any other file type, you can use nested syntax. Add the following to that other syntax highlighting plugin file:\r\n\r\n  syn include @WOIM ~\/.vim\/syntax\/woim.vim\r\n  syn region WoimSnip matchgroup=Snip start=\"WOIMstart\" end=\"WOIMend\" contains=@WOIM\r\n  hi link Snip SpecialComment\r\n\r\nIf you add those three lines in your .vim\/syntax\/txt.vim you will be able to include WOIM lists in files with a .txt extension like this:\r\n\r\nWOIMstart\r\nThis is a WOIM test list\r\n  Here is a child to the above item\r\n    Here is \"grand child\"\r\n  Here we are one level back\r\n    And here's another level down\r\n    [5] Dance steps\r\n    [3] Hurray\r\n    Smile\r\nWOIMend\r\n\r\nThe \"WOIMstart\" and \"WOIMend\" must be at the start of the line.\r\n","install_details":"Download woim.vba. Then do:\r\n\r\nvim woim.vba\r\n:so %\r\n:q\r\n\r\nThen read the file README_WOIM that appears in your .vim directory.","5":"Download woim.vba. Then do:\r\n\r\nvim woim.vba\r\n:so %\r\n:q\r\n\r\nThen read the file README_WOIM that appears in your .vim directory.","first_name":"Geir","6":"Geir","last_name":"Isene","7":"Isene","releases":[{"0":"2518","vim_version":"7.0","1":"7.0","script_version":"2.0","2":"2.0","version_comment":"WOIM has become HyperList. This version (2.0) is the same as the initial upload of the new HyperList project. WOIM is now deprecated. Long live HyperList: http:\/\/vim.sourceforge.net\/scripts\/script.php?script_id=4006","3":"WOIM has become HyperList. This version (2.0) is the same as the initial upload of the new HyperList project. WOIM is now deprecated. Long live HyperList: http:\/\/vim.sourceforge.net\/scripts\/script.php?script_id=4006","package":"hyperlist.vba","4":"hyperlist.vba","src_id":"17729","5":"17729","creation_date":"1333638328","6":"1333638328"},{"0":"2518","vim_version":"7.0","1":"7.0","script_version":"1.7","2":"1.7","version_comment":"Plugin compatible with the newly released WOIM version 1.7 which includes several real life examples of WOIM use. See http:\/\/isene.com\/woim.pdf for the newest version.\r\n\r\nRelease notes:\r\nExpanded \"gr\" (Goto Reference): Made it possible to reference external files by the use of #file:\/pathto\/filename, #file:~\/filename or #file:filename As long as the reference is prefixed with \"file:\" after the \"#\", the command \"gr\" will open the referenced file.\r\nAdded HTML conversion vith the use of <leader>H.\r\nImproved LaTeX conversion.\r\nAfter an HTML\/LaTeX conversion, filetype is set to html\/tex.\r\nChanged the color of multi-indicator (+) from red to purple.\r\n","3":"Plugin compatible with the newly released WOIM version 1.7 which includes several real life examples of WOIM use. See http:\/\/isene.com\/woim.pdf for the newest version.\r\n\r\nRelease notes:\r\nExpanded \"gr\" (Goto Reference): Made it possible to reference external files by the use of #file:\/pathto\/filename, #file:~\/filename or #file:filename As long as the reference is prefixed with \"file:\" after the \"#\", the command \"gr\" will open the referenced file.\r\nAdded HTML conversion vith the use of <leader>H.\r\nImproved LaTeX conversion.\r\nAfter an HTML\/LaTeX conversion, filetype is set to html\/tex.\r\nChanged the color of multi-indicator (+) from red to purple.\r\n","package":"woim.vba","4":"woim.vba","src_id":"17143","5":"17143","creation_date":"1325508654","6":"1325508654"},{"0":"2518","vim_version":"7.0","1":"7.0","script_version":"1.6","2":"1.6","version_comment":"Changes since previous version:\r\nAdded marking of literal regions with special marking of start\/end (\"\/\")\r\nAdded <leader><DOWN> and <leader><UP>\r\nFixed syntax marking for State\/Transitions where indent is an asterisk (\"*\")\r\nFixed escaping \"\\\", \"{\" and \"}\" for LaTeX conversion","3":"Changes since previous version:\r\nAdded marking of literal regions with special marking of start\/end (\"\/\")\r\nAdded <leader><DOWN> and <leader><UP>\r\nFixed syntax marking for State\/Transitions where indent is an asterisk (\"*\")\r\nFixed escaping \"\\\", \"{\" and \"}\" for LaTeX conversion","package":"woim.vba","4":"woim.vba","src_id":"17041","5":"17041","creation_date":"1323378631","6":"1323378631"},{"0":"2518","vim_version":"7.0","1":"7.0","script_version":"1.5.3","2":"1.5.3","version_comment":"New feature: LaTeX conversion: Turn your WOIM list into a LaTeX document. Mapped to <leader>L (feature suggested by  Shantanu Kulkarni). Added \"set autoindent\" to plugin settings (thanks to Shantanu Kulkarni). Minor fixes. Updated documentation.\r\n","3":"New feature: LaTeX conversion: Turn your WOIM list into a LaTeX document. Mapped to <leader>L (feature suggested by  Shantanu Kulkarni). Added \"set autoindent\" to plugin settings (thanks to Shantanu Kulkarni). Minor fixes. Updated documentation.\r\n","package":"woim.vba","4":"woim.vba","src_id":"16548","5":"16548","creation_date":"1316351192","6":"1316351192"},{"0":"2518","vim_version":"7.0","1":"7.0","script_version":"1.5.2","2":"1.5.2","version_comment":"  Changes:\r\n  Added \"presentation mode\" where you can traverse a WOIM list with \"g<DOWN>\" or \"g<UP>\" to view only the current line and its ancestors.\r\n  Changed Quotes and Comments to only cover one line (before when it covered several lines, the plugin became very slow for large lists).\r\n  Added instructions in doc file on using WOIM list in other file types.","3":"  Changes:\r\n  Added \"presentation mode\" where you can traverse a WOIM list with \"g<DOWN>\" or \"g<UP>\" to view only the current line and its ancestors.\r\n  Changed Quotes and Comments to only cover one line (before when it covered several lines, the plugin became very slow for large lists).\r\n  Added instructions in doc file on using WOIM list in other file types.","package":"woim.vba","4":"woim.vba","src_id":"16492","5":"16492","creation_date":"1315497263","6":"1315497263"},{"0":"2518","vim_version":"7.0","1":"7.0","script_version":"1.5.1","2":"1.5.1","version_comment":"Changes:\r\nMinor updates to the documentation.\r\n","3":"Changes:\r\nMinor updates to the documentation.\r\n","package":"woim.vba","4":"woim.vba","src_id":"16341","5":"16341","creation_date":"1314203948","6":"1314203948"},{"0":"2518","vim_version":"7.0","1":"7.0","script_version":"1.5.0","2":"1.5.0","version_comment":"Added encryption - both manual and automatic via OpenSSL:\r\n\r\n  <leader>z encrypts the current line (including all sublevels if folded)\r\n  <leader>Z encrypts the current file (all lines)\r\n  <leader>x decrypts the current line\r\n  <leader>X decrypts the current file (all lines)\r\n\r\nA dot file (file name starts with a \".\" such as .test.woim) is automatically encrypted on save and decrypted on opening. You can now use this plugin for encrypted lists or a very structured password safe.\r\n","3":"Added encryption - both manual and automatic via OpenSSL:\r\n\r\n  <leader>z encrypts the current line (including all sublevels if folded)\r\n  <leader>Z encrypts the current file (all lines)\r\n  <leader>x decrypts the current line\r\n  <leader>X decrypts the current file (all lines)\r\n\r\nA dot file (file name starts with a \".\" such as .test.woim) is automatically encrypted on save and decrypted on opening. You can now use this plugin for encrypted lists or a very structured password safe.\r\n","package":"woim.vba","4":"woim.vba","src_id":"16270","5":"16270","creation_date":"1313447855","6":"1313447855"},{"0":"2518","vim_version":"7.3","1":"7.3","script_version":"1.4.7","2":"1.4.7","version_comment":"Changes:\r\n Modified the GotoRef function (fixed a bug and included feed back)\r\n Better syntax highlighting for folding in gvim\r\n Updating the README_WOIM and documentation files + other cosmetic changes\r\n Added the possibility of disabling\/overriding the WOIM plugin key mapping\r\n Added an ftdetect file into woim.vba\r\n (Thanks to Sergey Khorev for the last two improvements)","3":"Changes:\r\n Modified the GotoRef function (fixed a bug and included feed back)\r\n Better syntax highlighting for folding in gvim\r\n Updating the README_WOIM and documentation files + other cosmetic changes\r\n Added the possibility of disabling\/overriding the WOIM plugin key mapping\r\n Added an ftdetect file into woim.vba\r\n (Thanks to Sergey Khorev for the last two improvements)","package":"woim.vba","4":"woim.vba","src_id":"15796","5":"15796","creation_date":"1307054326","6":"1307054326"},{"0":"2518","vim_version":"7.3","1":"7.3","script_version":"1,4,6","2":"1,4,6","version_comment":"Perfection:   Minor fixes due to a bout of perfectionism.\r\n\r\nAt this point I have nothing on the todo list - no fixes to be done and no features I want to implement.\r\nSo, I am looking for your input as inspiration to take this even further :)","3":"Perfection:   Minor fixes due to a bout of perfectionism.\r\n\r\nAt this point I have nothing on the todo list - no fixes to be done and no features I want to implement.\r\nSo, I am looking for your input as inspiration to take this even further :)","package":"woim.vba","4":"woim.vba","src_id":"15787","5":"15787","creation_date":"1306880712","6":"1306880712"},{"0":"2518","vim_version":"7.3","1":"7.3","script_version":"1.4.5","2":"1.4.5","version_comment":"Major Update; \r\n\r\nOverhaul:\r\n\r\nCreated the documentation, includin the whole WOIM definition to make it\r\neasily accessible within VIM.  Added the INSTALL and README files.\r\n\r\nCreated a Vimball file (\"woim.vba\") for easy install. Simply do:\r\n\r\nvim woim.vba\r\n:so %\r\n:q","3":"Major Update; \r\n\r\nOverhaul:\r\n\r\nCreated the documentation, includin the whole WOIM definition to make it\r\neasily accessible within VIM.  Added the INSTALL and README files.\r\n\r\nCreated a Vimball file (\"woim.vba\") for easy install. Simply do:\r\n\r\nvim woim.vba\r\n:so %\r\n:q","package":"woim.vba","4":"woim.vba","src_id":"15768","5":"15768","creation_date":"1306792200","6":"1306792200"},{"0":"2518","vim_version":"5.7","1":"5.7","script_version":"1.4.2","2":"1.4.2","version_comment":"Fixes in 1.4.2:\r\n\r\nFixed \"gr\" (Goto Ref) for references with single quotes ('')\r\n\r\nAdded the search pattern from \"gr\" to the search register (\"\/) so that \"n\" can successively be used to test if the referenced destination is unique (which it should be). ","3":"Fixes in 1.4.2:\r\n\r\nFixed \"gr\" (Goto Ref) for references with single quotes ('')\r\n\r\nAdded the search pattern from \"gr\" to the search register (\"\/) so that \"n\" can successively be used to test if the referenced destination is unique (which it should be). ","package":"woim.vim","4":"woim.vim","src_id":"15758","5":"15758","creation_date":"1306702185","6":"1306702185"},{"0":"2518","vim_version":"5.7","1":"5.7","script_version":"1.4.1","2":"1.4.1","version_comment":"New feature: \r\n\r\nGoto Reference: With the cursor at a WOIM reference, press \"gr\" to jump to that reference in the WOIM list.\r\n\r\nNow you can navigate more easily in WOIM lists.","3":"New feature: \r\n\r\nGoto Reference: With the cursor at a WOIM reference, press \"gr\" to jump to that reference in the WOIM list.\r\n\r\nNow you can navigate more easily in WOIM lists.","package":"woim.vim","4":"woim.vim","src_id":"15743","5":"15743","creation_date":"1306506572","6":"1306506572"},{"0":"2518","vim_version":"5.7","1":"5.7","script_version":"1.4","2":"1.4","version_comment":"This could have been the long awaited version 1.0 - but instead I decided to synchronize the version numbering of this VIM plugin and the WOIM description itself. From now on the releases will be synchronized, with minor fixes in the VIM plugin released as minor releases (i.e. a fix to 1.4 would be 1.4.1 and would still be on par with the WOIM definition version 1.4). The version 1.4 of the WOIM definition adds time repetition as well as \"checking\" of todo-list items.\r\n\r\nThis release:\r\n\r\nNew feature: Added the option of checkboxes for items (Thanks to Christopher Truett (VIM script #3584). You can now easily add a checkbox in front of any item by <leader>v and subsequently toggle that checkbox via the same (<leader>v) or <leader>V if you want to add a time stamp to a box that you \"check\" (this also toggles the timestamp if you \"uncheck\" the item).\r\n\r\nFixes: Some minor cleanup.","3":"This could have been the long awaited version 1.0 - but instead I decided to synchronize the version numbering of this VIM plugin and the WOIM description itself. From now on the releases will be synchronized, with minor fixes in the VIM plugin released as minor releases (i.e. a fix to 1.4 would be 1.4.1 and would still be on par with the WOIM definition version 1.4). The version 1.4 of the WOIM definition adds time repetition as well as \"checking\" of todo-list items.\r\n\r\nThis release:\r\n\r\nNew feature: Added the option of checkboxes for items (Thanks to Christopher Truett (VIM script #3584). You can now easily add a checkbox in front of any item by <leader>v and subsequently toggle that checkbox via the same (<leader>v) or <leader>V if you want to add a time stamp to a box that you \"check\" (this also toggles the timestamp if you \"uncheck\" the item).\r\n\r\nFixes: Some minor cleanup.","package":"woim.vim","4":"woim.vim","src_id":"15699","5":"15699","creation_date":"1306157062","6":"1306157062"},{"0":"2518","vim_version":"6.0","1":"6.0","script_version":"0.9.9","2":"0.9.9","version_comment":"Fix: Fixed interference between Operators and Tags\r\n\r\n(with the advent of WOIM 1.4 [soon], this syntax\/filetype plugin should reach the long awaited version 1.0)","3":"Fix: Fixed interference between Operators and Tags\r\n\r\n(with the advent of WOIM 1.4 [soon], this syntax\/filetype plugin should reach the long awaited version 1.0)","package":"woim.vim","4":"woim.vim","src_id":"15465","5":"15465","creation_date":"1303048907","6":"1303048907"},{"0":"2518","vim_version":"5.7","1":"5.7","script_version":"0.9.8","2":"0.9.8","version_comment":"Feature: States (S:) is underlined by default.  <leader>s removes the underlining, while <leader>S turns on underlining of States.  Transitions are not underlined by default.  <leader>T turns on underlining, while <leader>t removes the underlining of Transitions.\r\nFix: Removed unnecessary \"contained\" to make lists syntax marked even within stub lists.\r\nFix: Small fixes in grouping and containing of elements.\r\n","3":"Feature: States (S:) is underlined by default.  <leader>s removes the underlining, while <leader>S turns on underlining of States.  Transitions are not underlined by default.  <leader>T turns on underlining, while <leader>t removes the underlining of Transitions.\r\nFix: Removed unnecessary \"contained\" to make lists syntax marked even within stub lists.\r\nFix: Small fixes in grouping and containing of elements.\r\n","package":"woim.vim","4":"woim.vim","src_id":"14516","5":"14516","creation_date":"1292351044","6":"1292351044"},{"0":"2518","vim_version":"5.7","1":"5.7","script_version":"0.9.6","2":"0.9.6","version_comment":"Feature: Added \"*\" as possible indentation\r\nFix:         Changed Multiline indicator from \"*\" to \"+\"\r\n\r\nNow compatible with WOIM v. 1.2\r\n","3":"Feature: Added \"*\" as possible indentation\r\nFix:         Changed Multiline indicator from \"*\" to \"+\"\r\n\r\nNow compatible with WOIM v. 1.2\r\n","package":"woim.vim","4":"woim.vim","src_id":"14425","5":"14425","creation_date":"1291392037","6":"1291392037"},{"0":"2518","vim_version":"6.0","1":"6.0","script_version":"0.9.3","2":"0.9.3","version_comment":"Christian Bryn caught an important bug\/lacking setting. The syntax file now sets noexpandtab.","3":"Christian Bryn caught an important bug\/lacking setting. The syntax file now sets noexpandtab.","package":"woim.vim","4":"woim.vim","src_id":"11891","5":"11891","creation_date":"1260573761","6":"1260573761"},{"0":"2518","vim_version":"6.0","1":"6.0","script_version":"0.9.2","2":"0.9.2","version_comment":"A few needed minor fixes.","3":"A few needed minor fixes.","package":"woim.vim","4":"woim.vim","src_id":"11589","5":"11589","creation_date":"1256508822","6":"1256508822"},{"0":"2518","vim_version":"6.0","1":"6.0","script_version":"0.9.1","2":"0.9.1","version_comment":"New_feature:\r\nAdded highlighting of item motions:\r\n<<          means \"delete this item\" (put at the end of a line)\r\n>>#1.1. means \"move this item to after item 1.1.\"\r\n->           means \"indent item right\"\r\n<-<-       means \"indent item two left\"\r\n>>#1.-> means \"move item to after item 1. and indent right\"\r\n\r\n","3":"New_feature:\r\nAdded highlighting of item motions:\r\n<<          means \"delete this item\" (put at the end of a line)\r\n>>#1.1. means \"move this item to after item 1.1.\"\r\n->           means \"indent item right\"\r\n<-<-       means \"indent item two left\"\r\n>>#1.-> means \"move item to after item 1. and indent right\"\r\n\r\n","package":"woim.vim","4":"woim.vim","src_id":"11231","5":"11231","creation_date":"1250883582","6":"1250883582"},{"0":"2518","vim_version":"6.0","1":"6.0","script_version":"0.9","2":"0.9","version_comment":"New_feature: Accommodated for the use of subroutine calls (##ref)\r\nFix: Cleaned up syntax variable names to fit modern WOIM\r\nFix: Multi-lines have consecutive lines start with a <space>\r\nFix: Quotes or Comment can now span several lines\r\nFix: Comments allowed in Operators\r\nFix: Comments and references allowed inside Qualifiers\r\nFix: Identifier must end in a period and then a space\r\nBug_fix: Allowing a period to be part of a tag\r\nBug_fix: Fixed wrong markup for astrices not used for multi-line","3":"New_feature: Accommodated for the use of subroutine calls (##ref)\r\nFix: Cleaned up syntax variable names to fit modern WOIM\r\nFix: Multi-lines have consecutive lines start with a <space>\r\nFix: Quotes or Comment can now span several lines\r\nFix: Comments allowed in Operators\r\nFix: Comments and references allowed inside Qualifiers\r\nFix: Identifier must end in a period and then a space\r\nBug_fix: Allowing a period to be part of a tag\r\nBug_fix: Fixed wrong markup for astrices not used for multi-line","package":"woim.vim","4":"woim.vim","src_id":"11168","5":"11168","creation_date":"1249900456","6":"1249900456"},{"0":"2518","vim_version":"6.0","1":"6.0","script_version":"0.8.6","2":"0.8.6","version_comment":"Bug fix: Corrected attributes ending in capitals that was treated as a WOIMkey\r\nBug fix: Fixed references containing a hyphen\r\n","3":"Bug fix: Corrected attributes ending in capitals that was treated as a WOIMkey\r\nBug fix: Fixed references containing a hyphen\r\n","package":"woim.vim","4":"woim.vim","src_id":"11058","5":"11058","creation_date":"1248428259","6":"1248428259"},{"0":"2518","vim_version":"6.0","1":"6.0","script_version":"0.8.5","2":"0.8.5","version_comment":"New feature: Expanded Attributes to include relative times and greater\/smaller than.\r\nNew feature: References with spaces are now accommodated for by putting it in quotes.\r\nNew feature: Made references in attributes possible.\r\nBug fix: Fixed references that includes ampersands (\"&\").\r\n","3":"New feature: Expanded Attributes to include relative times and greater\/smaller than.\r\nNew feature: References with spaces are now accommodated for by putting it in quotes.\r\nNew feature: Made references in attributes possible.\r\nBug fix: Fixed references that includes ampersands (\"&\").\r\n","package":"woim.vim","4":"woim.vim","src_id":"11055","5":"11055","creation_date":"1248380871","6":"1248380871"},{"0":"2518","vim_version":"6.0","1":"6.0","script_version":"0.8.1","2":"0.8.1","version_comment":"Bug fix: Fixed highlighting of attributes with a colon (like time stamps)","3":"Bug fix: Fixed highlighting of attributes with a colon (like time stamps)","package":"woim.vim","4":"woim.vim","src_id":"11053","5":"11053","creation_date":"1248290320","6":"1248290320"},{"0":"2518","vim_version":"6.0","1":"6.0","script_version":"0.8","2":"0.8","version_comment":"New feature: Expanded folding to a maximum of 15 levels with folding levels set with <leader>a to <leader>f for levels 10 to 15.\r\nImprovement: Better syntax highlighting for indexes\r\nBug fix: Fixed syntax syncing when entering the document in the first place","3":"New feature: Expanded folding to a maximum of 15 levels with folding levels set with <leader>a to <leader>f for levels 10 to 15.\r\nImprovement: Better syntax highlighting for indexes\r\nBug fix: Fixed syntax syncing when entering the document in the first place","package":"woim.vim","4":"woim.vim","src_id":"11047","5":"11047","creation_date":"1248190023","6":"1248190023"},{"0":"2518","vim_version":"6.0","1":"6.0","script_version":"0.7.2","2":"0.7.2","version_comment":"Better syntax highlighting for references.\r\nAdded unobtrusive highlighting of vim bottom set-lines.","3":"Better syntax highlighting for references.\r\nAdded unobtrusive highlighting of vim bottom set-lines.","package":"woim.vim","4":"woim.vim","src_id":"11013","5":"11013","creation_date":"1247665564","6":"1247665564"},{"0":"2518","vim_version":"6.0","1":"6.0","script_version":"0.7.1","2":"0.7.1","version_comment":"Bug fix: Fixed an error in syntax highlighting properties containing a \"-\" (like ISO dates).","3":"Bug fix: Fixed an error in syntax highlighting properties containing a \"-\" (like ISO dates).","package":"woim.vim","4":"woim.vim","src_id":"10850","5":"10850","creation_date":"1245163081","6":"1245163081"},{"0":"2518","vim_version":"6.0","1":"6.0","script_version":"0.7","2":"0.7","version_comment":"Added macro to jump to next point in a template and fill in the value. A template item is an item that ends in an equal sign and where the value after the equal sign is to be filled out. Example:\r\n\r\nExampleTask\r\n   Task name = \r\n   Responsible person =\r\n   Deadline = ","3":"Added macro to jump to next point in a template and fill in the value. A template item is an item that ends in an equal sign and where the value after the equal sign is to be filled out. Example:\r\n\r\nExampleTask\r\n   Task name = \r\n   Responsible person =\r\n   Deadline = ","package":"woim.vim","4":"woim.vim","src_id":"10818","5":"10818","creation_date":"1244932975","6":"1244932975"},{"0":"2518","vim_version":"6.0","1":"6.0","script_version":"0.6","2":"0.6","version_comment":"Some minor adjustments, but a needed upgrade if you are a WOIM user.\r\n(WOIM = task list, descriptive system, process description, state description... it can describe anything,)","3":"Some minor adjustments, but a needed upgrade if you are a WOIM user.\r\n(WOIM = task list, descriptive system, process description, state description... it can describe anything,)","package":"woim.vim","4":"woim.vim","src_id":"10392","5":"10392","creation_date":"1239662686","6":"1239662686"},{"0":"2518","vim_version":"6.0","1":"6.0","script_version":"0.4","2":"0.4","version_comment":"Initial upload","3":"Initial upload","package":"WOIM.vim","4":"WOIM.vim","src_id":"9833","5":"9833","creation_date":"1232139141","6":"1232139141"}]},"2517":{"script_id":"2517","0":"2517","script_name":"norwaytoday","1":"norwaytoday","script_type":"color scheme","2":"color scheme","summary":"Norway Today Netbeans theme for Vim (GUI Only)","3":"Norway Today Netbeans theme for Vim (GUI Only)","description":"A colorscheme based on the Netbeans Norway Today theme.  It has been tested with Vim 7.2 and Ruby.\r\n\r\nGitHub: http:\/\/github.com\/jpo\/vim-norwaytoday-theme\/tree\/master","4":"A colorscheme based on the Netbeans Norway Today theme.  It has been tested with Vim 7.2 and Ruby.\r\n\r\nGitHub: http:\/\/github.com\/jpo\/vim-norwaytoday-theme\/tree\/master","install_details":"Just copy it into ~\/.vim\/colors\/ (*nix) or vimfiles\/colors\/ (Windows) as with other color schemes.\r\nType \"colorscheme railscasts\" into your vimrc file.","5":"Just copy it into ~\/.vim\/colors\/ (*nix) or vimfiles\/colors\/ (Windows) as with other color schemes.\r\nType \"colorscheme railscasts\" into your vimrc file.","first_name":"Josh","6":"Josh","last_name":"O'Rourke","7":"O'Rourke","releases":[{"0":"2517","vim_version":"7.0","1":"7.0","script_version":"0.8","2":"0.8","version_comment":"Changed fold colors.  (Thanks to Raimon Grau)","3":"Changed fold colors.  (Thanks to Raimon Grau)","package":"norwaytoday.vim","4":"norwaytoday.vim","src_id":"9948","5":"9948","creation_date":"1234287188","6":"1234287188"},{"0":"2517","vim_version":"7.0","1":"7.0","script_version":"0.7","2":"0.7","version_comment":"Changed colors of the autocomplete menu to make it easier on the eyes.  \r\n(Thanks to Raimon Grau) ","3":"Changed colors of the autocomplete menu to make it easier on the eyes.  \r\n(Thanks to Raimon Grau) ","package":"norwaytoday.vim","4":"norwaytoday.vim","src_id":"9884","5":"9884","creation_date":"1233246857","6":"1233246857"},{"0":"2517","vim_version":"7.0","1":"7.0","script_version":"0.6","2":"0.6","version_comment":"Fixed a few syntax problems.  Added better HTML support.","3":"Fixed a few syntax problems.  Added better HTML support.","package":"norwaytoday.vim","4":"norwaytoday.vim","src_id":"9821","5":"9821","creation_date":"1231972301","6":"1231972301"},{"0":"2517","vim_version":"7.2","1":"7.2","script_version":"0.5","2":"0.5","version_comment":"Initial upload","3":"Initial upload","package":"norwaytoday.vim","4":"norwaytoday.vim","src_id":"9819","5":"9819","creation_date":"1231961128","6":"1231961128"}]},"2516":{"script_id":"2516","0":"2516","script_name":"lilydjwg_green","1":"lilydjwg_green","script_type":"color scheme","2":"color scheme","summary":"A light-green background color scheme.","3":"A light-green background color scheme.","description":"Mainly light-blue and green on a light-green background.\r\nIt is my first vim color scheme, and I don't know much about colors, so it may be not so good as I have expected. But I wish it is useful. Any suggestion, please email me.","4":"Mainly light-blue and green on a light-green background.\r\nIt is my first vim color scheme, and I don't know much about colors, so it may be not so good as I have expected. But I wish it is useful. Any suggestion, please email me.","install_details":"","5":"","first_name":"lilydjwg","6":"lilydjwg","last_name":" ","7":" ","releases":[{"0":"2516","vim_version":"7.0","1":"7.0","script_version":"1.6","2":"1.6","version_comment":"* support for newly added CursorLineNr group","3":"* support for newly added CursorLineNr group","package":"lilydjwg_green.vim","4":"lilydjwg_green.vim","src_id":"17646","5":"17646","creation_date":"1332522298","6":"1332522298"},{"0":"2516","vim_version":"6.0","1":"6.0","script_version":"1.5","2":"1.5","version_comment":"Add support for 256 color terminal.","3":"Add support for 256 color terminal.","package":"lilydjwg_green.vim","4":"lilydjwg_green.vim","src_id":"11328","5":"11328","creation_date":"1252158892","6":"1252158892"},{"0":"2516","vim_version":"7.0","1":"7.0","script_version":"1.3","2":"1.3","version_comment":"Much better readability and fix some bugs.For GUI only.","3":"Much better readability and fix some bugs.For GUI only.","package":"lilydjwg_green.vim","4":"lilydjwg_green.vim","src_id":"9976","5":"9976","creation_date":"1234775428","6":"1234775428"},{"0":"2516","vim_version":"7.2","1":"7.2","script_version":"1.1","2":"1.1","version_comment":"Initial upload","3":"Initial upload","package":"lilydjwg_green.vim","4":"lilydjwg_green.vim","src_id":"9812","5":"9812","creation_date":"1231914038","6":"1231914038"}]},"2515":{"script_id":"2515","0":"2515","script_name":"widower.vim","1":"widower.vim","script_type":"color scheme","2":"color scheme","summary":"color scheme mostly red on black background","3":"color scheme mostly red on black background","description":"Was having trouble finding a red based color scheme so i made a relatively simple one. This is the color scheme i use for programming. It is mostly red on a black background (which matches my computer's color scheme), with some oranges and other colors as well. Happy viming!","4":"Was having trouble finding a red based color scheme so i made a relatively simple one. This is the color scheme i use for programming. It is mostly red on a black background (which matches my computer's color scheme), with some oranges and other colors as well. Happy viming!","install_details":"Place file in your color subfolder. To make this the default color, make sure your .vimrc file contains colorscheme widower.\r\n\r\n","5":"Place file in your color subfolder. To make this the default color, make sure your .vimrc file contains colorscheme widower.\r\n\r\n","first_name":"greg","6":"greg","last_name":"frohring","7":"frohring","releases":[{"0":"2515","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"widower.vim","4":"widower.vim","src_id":"9811","5":"9811","creation_date":"1231870054","6":"1231870054"}]},"2514":{"script_id":"2514","0":"2514","script_name":"ctxabbr","1":"ctxabbr","script_type":"utility","2":"utility","summary":"Context-sensitive abbreviations","3":"Context-sensitive abbreviations","description":"*ctxabbr* is a Vim plugin to provide a convenient way to define a variant of\r\nnormal |abbreviations|, called as \"context-sensitive abbreviations\".\r\nNormal abbreviations are short words which will be replaced with the words\r\nthey stand for whenever you enter the short words.\r\nBut sometimes, it is useful to replace such abbreviations\r\nwith some text according to the context - text around the cursor.\r\n\r\nFor example,\r\n\r\n\tcall ctxabbr#define('sc', 'System.Collections', '<using')\r\n\r\nWith the above setting, whenever you enter \"sc\", it is replaced with\r\n\"System.Collections\" if it is entered after a word \"using\", or\r\n\"sc\" otherwise.  It is illustrated as follows:\r\n\r\n\tusing sc       ==>    using System.Collections\r\n\t\/\/ sc sc sc    ==>    \/\/ sc sc sc\r\n\r\n\r\n\r\nRequirements:\r\n- Vim 7.2 or later\r\n\r\nLatest version:\r\nhttp:\/\/github.com\/kana\/vim-ctxabbr","4":"*ctxabbr* is a Vim plugin to provide a convenient way to define a variant of\r\nnormal |abbreviations|, called as \"context-sensitive abbreviations\".\r\nNormal abbreviations are short words which will be replaced with the words\r\nthey stand for whenever you enter the short words.\r\nBut sometimes, it is useful to replace such abbreviations\r\nwith some text according to the context - text around the cursor.\r\n\r\nFor example,\r\n\r\n\tcall ctxabbr#define('sc', 'System.Collections', '<using')\r\n\r\nWith the above setting, whenever you enter \"sc\", it is replaced with\r\n\"System.Collections\" if it is entered after a word \"using\", or\r\n\"sc\" otherwise.  It is illustrated as follows:\r\n\r\n\tusing sc       ==>    using System.Collections\r\n\t\/\/ sc sc sc    ==>    \/\/ sc sc sc\r\n\r\n\r\n\r\nRequirements:\r\n- Vim 7.2 or later\r\n\r\nLatest version:\r\nhttp:\/\/github.com\/kana\/vim-ctxabbr","install_details":"...","5":"...","first_name":"Kana","6":"Kana","last_name":"Natsuno","7":"Natsuno","releases":[{"0":"2514","vim_version":"7.0","1":"7.0","script_version":"0.0.2","2":"0.0.2","version_comment":"- Support buffer-local abbreviations.\n- Add |ctxabbr#reset()|.","3":"- Support buffer-local abbreviations.\n- Add |ctxabbr#reset()|.","package":"vim-ctxabbr-0.0.2.zip","4":"vim-ctxabbr-0.0.2.zip","src_id":"9792","5":"9792","creation_date":"1231566639","6":"1231566639"},{"0":"2514","vim_version":"7.0","1":"7.0","script_version":"0.0.1","2":"0.0.1","version_comment":"- Remove unintentionally remained :echomsg for debugging.\n- |ctxabbr#define()|: Add \"!\" condition.","3":"- Remove unintentionally remained :echomsg for debugging.\n- |ctxabbr#define()|: Add \"!\" condition.","package":"vim-ctxabbr-0.0.1.zip","4":"vim-ctxabbr-0.0.1.zip","src_id":"9791","5":"9791","creation_date":"1231563448","6":"1231563448"},{"0":"2514","vim_version":"7.0","1":"7.0","script_version":"0.0.0","2":"0.0.0","version_comment":"Initial upload","3":"Initial upload","package":"vim-ctxabbr-0.0.0.zip","4":"vim-ctxabbr-0.0.0.zip","src_id":"9785","5":"9785","creation_date":"1231528946","6":"1231528946"}]},"2513":{"script_id":"2513","0":"2513","script_name":"charged-256.vim","1":"charged-256.vim","script_type":"color scheme","2":"color scheme","summary":"256 color colorsheme to supplement dark colorschemes.","3":"256 color colorsheme to supplement dark colorschemes.","description":"There are a lot of good color schemes out there, but not many use good colors for vim itself (split, tabs, line numbers, etc...). This colorscheme is meant to be used in conjunction with an existing color scheme. It only highlights vim itself (not any code).\r\n\r\nScreenshot: http:\/\/chargedsoftware.com\/~charged2885\/files\/charged-256.png","4":"There are a lot of good color schemes out there, but not many use good colors for vim itself (split, tabs, line numbers, etc...). This colorscheme is meant to be used in conjunction with an existing color scheme. It only highlights vim itself (not any code).\r\n\r\nScreenshot: http:\/\/chargedsoftware.com\/~charged2885\/files\/charged-256.png","install_details":"Put it in ~\/.vim\/colors and :colorscheme your_favorite_colorscheme then :colorscheme charged-256.","5":"Put it in ~\/.vim\/colors and :colorscheme your_favorite_colorscheme then :colorscheme charged-256.","first_name":"Todd","6":"Todd","last_name":"Boland","7":"Boland","releases":[{"0":"2513","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"charged-256.vim","4":"charged-256.vim","src_id":"9784","5":"9784","creation_date":"1231515136","6":"1231515136"}]},"2512":{"script_id":"2512","0":"2512","script_name":"guepardo.vim","1":"guepardo.vim","script_type":"color scheme","2":"color scheme","summary":"Color scheme inspired by OSX Leopard with a little bit of Python","3":"Color scheme inspired by OSX Leopard with a little bit of Python","description":"This scheme was inspired by OSX Leopard colors. Is light, blue-greyish and very clean. Though designed for general use, some attention was paid to make it Pythonic.\r\n\r\nhttp:\/\/img258.imageshack.us\/img258\/4890\/picture13vn4.png\r\n\r\nHope You like it.\r\n\r\nSince I can't update this file using this site (update doesn  work) you can have the latest version form:\r\n\r\nhttp:\/\/svn.pixagora.com\/vim\r\n","4":"This scheme was inspired by OSX Leopard colors. Is light, blue-greyish and very clean. Though designed for general use, some attention was paid to make it Pythonic.\r\n\r\nhttp:\/\/img258.imageshack.us\/img258\/4890\/picture13vn4.png\r\n\r\nHope You like it.\r\n\r\nSince I can't update this file using this site (update doesn  work) you can have the latest version form:\r\n\r\nhttp:\/\/svn.pixagora.com\/vim\r\n","install_details":"","5":"","first_name":"Omar","6":"Omar","last_name":"Gomez","7":"Gomez","releases":[{"0":"2512","vim_version":"6.0","1":"6.0","script_version":"1.0.1","2":"1.0.1","version_comment":"Minor fix","3":"Minor fix","package":"guepardo.vim","4":"guepardo.vim","src_id":"10274","5":"10274","creation_date":"1237845615","6":"1237845615"},{"0":"2512","vim_version":"5.7","1":"5.7","script_version":"1.0.1","2":"1.0.1","version_comment":"Minor fix","3":"Minor fix","package":"guepardo.vim","4":"guepardo.vim","src_id":"10273","5":"10273","creation_date":"1237845551","6":"1237845551"},{"0":"2512","vim_version":"6.0","1":"6.0","script_version":"1.0.1","2":"1.0.1","version_comment":"Minor fix","3":"Minor fix","package":"guepardo.vim","4":"guepardo.vim","src_id":"10272","5":"10272","creation_date":"1237845460","6":"1237845460"},{"0":"2512","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"guepardo.vim","4":"guepardo.vim","src_id":"9783","5":"9783","creation_date":"1231513168","6":"1231513168"}]},"2511":{"script_id":"2511","0":"2511","script_name":"RunView","1":"RunView","script_type":"utility","2":"utility","summary":"Run scripts through filter and display output in separate window","3":"Run scripts through filter and display output in separate window","description":"RunView runs user-selected lines, selected either via a range provided to the RunView command or by visual-line selection (V), through a filter.  By default, the filter is ksh; however, the runview-filtcmd can be set (let g:runview_filtcmd=\"someotherfilter\") in your <.vimrc> to override this.  The RunView command lets you specify the filter on the command line, too.\r\n\r\nThe output is placed in a separate window; it is horizontally or vertically placed.  Source code is left unchanged and visible.\r\n\r\nWithout the !, the RunView command uses horizontally adjacent windows.  With the !, the RunView command uses vertically stacked windows.\r\n\r\nAs an example, consider the file:\r\n\techo \"one\"\r\n\techo \"two\"\r\n\techo \"three\"\r\nUsing\r\n\t:%RunView! ksh\r\nthe source code window is left on top, but the results of filtering the three lines is shown below it: \r\n\techo \"one\"\r\n\techo \"two\"\r\n\techo \"three\"\r\n\t-------------\r\n\tRunView ksh Output Window\r\n\t=== 01\/02\/05 06:07:08 ===\r\n\tone\r\n\ttwo\r\n\tthree\r\nRunView provides a title and a separator.  Subsequent applications of RunView will append a new separator line plus the new filter output.\r\n\r\n(alpha\/beta version available at http:\/\/www.drchip.org\/astronaut\/vim\/index.html#RUNVIEW)\r\n","4":"RunView runs user-selected lines, selected either via a range provided to the RunView command or by visual-line selection (V), through a filter.  By default, the filter is ksh; however, the runview-filtcmd can be set (let g:runview_filtcmd=\"someotherfilter\") in your <.vimrc> to override this.  The RunView command lets you specify the filter on the command line, too.\r\n\r\nThe output is placed in a separate window; it is horizontally or vertically placed.  Source code is left unchanged and visible.\r\n\r\nWithout the !, the RunView command uses horizontally adjacent windows.  With the !, the RunView command uses vertically stacked windows.\r\n\r\nAs an example, consider the file:\r\n\techo \"one\"\r\n\techo \"two\"\r\n\techo \"three\"\r\nUsing\r\n\t:%RunView! ksh\r\nthe source code window is left on top, but the results of filtering the three lines is shown below it: \r\n\techo \"one\"\r\n\techo \"two\"\r\n\techo \"three\"\r\n\t-------------\r\n\tRunView ksh Output Window\r\n\t=== 01\/02\/05 06:07:08 ===\r\n\tone\r\n\ttwo\r\n\tthree\r\nRunView provides a title and a separator.  Subsequent applications of RunView will append a new separator line plus the new filter output.\r\n\r\n(alpha\/beta version available at http:\/\/www.drchip.org\/astronaut\/vim\/index.html#RUNVIEW)\r\n","install_details":"vi RunView.vba.gz\r\n:so %\r\n\r\n(you need to have   filetype plugin on   in your .vimrc, too)","5":"vi RunView.vba.gz\r\n:so %\r\n\r\n(you need to have   filetype plugin on   in your .vimrc, too)","first_name":"Charles","6":"Charles","last_name":"Campbell","7":"Campbell","releases":[{"0":"2511","vim_version":"7.3","1":"7.3","script_version":"3","2":"3","version_comment":"various bugfixes","3":"various bugfixes","package":"RunView.vba.gz","4":"RunView.vba.gz","src_id":"21107","5":"21107","creation_date":"1385414728","6":"1385414728"},{"0":"2511","vim_version":"7.0","1":"7.0","script_version":"2","2":"2","version_comment":"some bug fixes.\r\n","3":"some bug fixes.\r\n","package":"RunView.vba.gz","4":"RunView.vba.gz","src_id":"9905","5":"9905","creation_date":"1233600881","6":"1233600881"}]},"2510":{"script_id":"2510","0":"2510","script_name":"proton","1":"proton","script_type":"color scheme","2":"color scheme","summary":"Another light colorscheme","3":"Another light colorscheme","description":"See http:\/\/www.leetless.de\/vim.html for a screenshot.\r\n","4":"See http:\/\/www.leetless.de\/vim.html for a screenshot.\r\n","install_details":"Put into ~\/.vim\/colors and type \":colorscheme proton\" in vim.","5":"Put into ~\/.vim\/colors and type \":colorscheme proton\" in vim.","first_name":"Henning","6":"Henning","last_name":"Hasemann","7":"Hasemann","releases":[{"0":"2510","vim_version":"6.0","1":"6.0","script_version":"0.3","2":"0.3","version_comment":"Some more fixes & beautifyings","3":"Some more fixes & beautifyings","package":"proton.vim","4":"proton.vim","src_id":"9818","5":"9818","creation_date":"1231959571","6":"1231959571"},{"0":"2510","vim_version":"6.0","1":"6.0","script_version":"0.2","2":"0.2","version_comment":"Fixed wrong\/undefined background color for lots of important Highlighting groups","3":"Fixed wrong\/undefined background color for lots of important Highlighting groups","package":"proton.vim","4":"proton.vim","src_id":"9817","5":"9817","creation_date":"1231958854","6":"1231958854"},{"0":"2510","vim_version":"6.0","1":"6.0","script_version":"0.1real","2":"0.1real","version_comment":"The correct script (the first upload was only html junk, sorry for that)","3":"The correct script (the first upload was only html junk, sorry for that)","package":"proton.vim","4":"proton.vim","src_id":"9803","5":"9803","creation_date":"1231751075","6":"1231751075"}]},"2509":{"script_id":"2509","0":"2509","script_name":"Spiderhawk","1":"Spiderhawk","script_type":"color scheme","2":"color scheme","summary":"Initial Upload","3":"Initial Upload","description":"This is the color scheme I use for coding.\r\n\r\nIt is very basic, but that is what I like. I will make additions and improvements as I find the need.\r\n\r\nI am also open to suggestions.","4":"This is the color scheme I use for coding.\r\n\r\nIt is very basic, but that is what I like. I will make additions and improvements as I find the need.\r\n\r\nI am also open to suggestions.","install_details":"Copy the file to your Vim colors directory.\r\nAdd or change this line in your vimrc file:\r\ncolorscheme spiderhawk","5":"Copy the file to your Vim colors directory.\r\nAdd or change this line in your vimrc file:\r\ncolorscheme spiderhawk","first_name":"Art","6":"Art","last_name":"Cowles","7":"Cowles","releases":[{"0":"2509","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"spiderhawk.vim","4":"spiderhawk.vim","src_id":"9769","5":"9769","creation_date":"1231295664","6":"1231295664"}]},"2508":{"script_id":"2508","0":"2508","script_name":"DBGp Remote Debugger Interface","1":"DBGp Remote Debugger Interface","script_type":"utility","2":"utility","summary":"Debugging interface\/client for DBGp protocol","3":"Debugging interface\/client for DBGp protocol","description":"these are updates for Sam Ghods script\r\nhttp:\/\/www.vim.org\/scripts\/script.php?script_id=1929\r\n\r\nbased on Seung Woo Shin script\r\nhttp:\/\/www.vim.org\/scripts\/script.php?script_id=1152\r\n\r\nbasically just I add tab-page editing support to the original plugin which based on vim 6.0 below is list of changes made to the python script.\r\n\r\n- when multiple tab-page loaded, it will remember the initial tab-page \r\n  which start the debugging session. every debugging command will \r\n  make sure that you are debugging on that initial tab, \r\n  so debugging session wont mess other tab.\r\n- when debugging session ends on multi tab-page window, other \r\n  tab-page is no longer being duplicated, it will only restore debugging tab\r\n\r\nI've send sam a diff's for this plugin, it seems he's a bit busy, and can't reply my email (yet), it's ok anyway cause I'm planning to add more common feature to the script, \r\n\r\nplease if you find any bug, made a patch, diffs, etc, let me know...\r\n\r\n\r\n ","4":"these are updates for Sam Ghods script\r\nhttp:\/\/www.vim.org\/scripts\/script.php?script_id=1929\r\n\r\nbased on Seung Woo Shin script\r\nhttp:\/\/www.vim.org\/scripts\/script.php?script_id=1152\r\n\r\nbasically just I add tab-page editing support to the original plugin which based on vim 6.0 below is list of changes made to the python script.\r\n\r\n- when multiple tab-page loaded, it will remember the initial tab-page \r\n  which start the debugging session. every debugging command will \r\n  make sure that you are debugging on that initial tab, \r\n  so debugging session wont mess other tab.\r\n- when debugging session ends on multi tab-page window, other \r\n  tab-page is no longer being duplicated, it will only restore debugging tab\r\n\r\nI've send sam a diff's for this plugin, it seems he's a bit busy, and can't reply my email (yet), it's ok anyway cause I'm planning to add more common feature to the script, \r\n\r\nplease if you find any bug, made a patch, diffs, etc, let me know...\r\n\r\n\r\n ","install_details":"just copy the debugger.py and debugger.vim to the plugin directory in your home directory\r\n\r\n$ tar -xzvf debugger.tar.gz\r\n$ cp plugin\/debugger.*  ~\/.vim\/plugin\/","5":"just copy the debugger.py and debugger.vim to the plugin directory in your home directory\r\n\r\n$ tar -xzvf debugger.tar.gz\r\n$ cp plugin\/debugger.*  ~\/.vim\/plugin\/","first_name":"Hadi","6":"Hadi","last_name":"Zeftin","7":"Zeftin","releases":[{"0":"2508","vim_version":"7.0","1":"7.0","script_version":"1.0.2","2":"1.0.2","version_comment":"- remove bug about file path for windows\r\n- other info, question, suggestion, please see\r\nhttp:\/\/slackdna.blogspot.com\/search\/label\/vim-dbgpclient","3":"- remove bug about file path for windows\r\n- other info, question, suggestion, please see\r\nhttp:\/\/slackdna.blogspot.com\/search\/label\/vim-dbgpclient","package":"debugger.tar.gz","4":"debugger.tar.gz","src_id":"9793","5":"9793","creation_date":"1231606506","6":"1231606506"},{"0":"2508","vim_version":"7.0","1":"7.0","script_version":"1.0.1","2":"1.0.1","version_comment":"- add dedicated debugging tab\r\n- info, suggestion, and question see\r\nhttp:\/\/slackdna.blogspot.com\/search\/label\/vim-dbgpclient","3":"- add dedicated debugging tab\r\n- info, suggestion, and question see\r\nhttp:\/\/slackdna.blogspot.com\/search\/label\/vim-dbgpclient","package":"debugger.tar.gz","4":"debugger.tar.gz","src_id":"9781","5":"9781","creation_date":"1231470109","6":"1231470109"},{"0":"2508","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"debugger.tar.gz","4":"debugger.tar.gz","src_id":"9766","5":"9766","creation_date":"1231251168","6":"1231251168"}]},"2507":{"script_id":"2507","0":"2507","script_name":"0scan","1":"0scan","script_type":"utility","2":"utility","summary":"Tags based search for any things you might want to find(ctags, buffers,...).","3":"Tags based search for any things you might want to find(ctags, buffers,...).","description":"Scan the entities with one \"Tags Based\" common interface.\r\n\r\nScan:\r\nbuffers to switch to;\r\nfiles to open;\r\nwindows and tabs to switch to;\r\nfiles like c++, python, vim, sco, html and more ( on request ) to jump to things like \"constructors\", \"objects\", \"methods\", etc;\r\nyour ctags database to browse source code;\r\ndefinition and declaration of method;\r\nvim's registers to paste text;\r\ncurrent file changes to move to;\r\nvim marks to jump to;\r\n\r\nand more ( on request )\r\n\r\nCreate your own scans to browse things related to your work flow.\r\nTo look at sample how to create your own scan just select any file at ~\/.vim\/autoload\/railmoon\/oscan\/extractor\/\r\nfor example:  ~\/.vim\/autoload\/railmoon\/oscan\/extractor\/buffers.vim\r\n\r\nDetailed description:\r\nhttp:\/\/www.railmoon.com\/vim_plugins\/0scan\/Entries\/2009\/9\/26_Introduction.html\r\n\r\nDo not hesitate to email me problems or suggestions.\r\n ","4":"Scan the entities with one \"Tags Based\" common interface.\r\n\r\nScan:\r\nbuffers to switch to;\r\nfiles to open;\r\nwindows and tabs to switch to;\r\nfiles like c++, python, vim, sco, html and more ( on request ) to jump to things like \"constructors\", \"objects\", \"methods\", etc;\r\nyour ctags database to browse source code;\r\ndefinition and declaration of method;\r\nvim's registers to paste text;\r\ncurrent file changes to move to;\r\nvim marks to jump to;\r\n\r\nand more ( on request )\r\n\r\nCreate your own scans to browse things related to your work flow.\r\nTo look at sample how to create your own scan just select any file at ~\/.vim\/autoload\/railmoon\/oscan\/extractor\/\r\nfor example:  ~\/.vim\/autoload\/railmoon\/oscan\/extractor\/buffers.vim\r\n\r\nDetailed description:\r\nhttp:\/\/www.railmoon.com\/vim_plugins\/0scan\/Entries\/2009\/9\/26_Introduction.html\r\n\r\nDo not hesitate to email me problems or suggestions.\r\n ","install_details":"unzip into ~\/.vim","5":"unzip into ~\/.vim","first_name":"Mykola","6":"Mykola","last_name":"Golubyev","7":"Golubyev","releases":[{"0":"2507","vim_version":"7.0","1":"7.0","script_version":"0.5.2","2":"0.5.2","version_comment":"Added Files scan to open files from the current file dir( http:\/\/www.railmoon.com\/0scan\/scan-files ). \r\nTags are always case insensitive now ( were depend on ignorecase option ). Windows scan had a little bug.   \r\n-- thanks to Raimon Grau for feedback.\r\n\r\n","3":"Added Files scan to open files from the current file dir( http:\/\/www.railmoon.com\/0scan\/scan-files ). \r\nTags are always case insensitive now ( were depend on ignorecase option ). Windows scan had a little bug.   \r\n-- thanks to Raimon Grau for feedback.\r\n\r\n","package":"0scan.zip","4":"0scan.zip","src_id":"9916","5":"9916","creation_date":"1233785115","6":"1233785115"},{"0":"2507","vim_version":"7.0","1":"7.0","script_version":"0.5.1","2":"0.5.1","version_comment":"Added \"Changes\" scan( http:\/\/www.railmoon.com\/0scan\/scan-changes ). Changed \"Registers\" scan to show no more then 5 lines from register.","3":"Added \"Changes\" scan( http:\/\/www.railmoon.com\/0scan\/scan-changes ). Changed \"Registers\" scan to show no more then 5 lines from register.","package":"0scan.zip","4":"0scan.zip","src_id":"9897","5":"9897","creation_date":"1233517625","6":"1233517625"},{"0":"2507","vim_version":"7.0","1":"7.0","script_version":"0.5","2":"0.5","version_comment":"Added Registers Scan to find text through all your registers to paste. \r\nhttp:\/\/www.railmoon.com\/0scan\/scan-registers\r\n\r\nMinor re-factoring.","3":"Added Registers Scan to find text through all your registers to paste. \r\nhttp:\/\/www.railmoon.com\/0scan\/scan-registers\r\n\r\nMinor re-factoring.","package":"0scan.zip","4":"0scan.zip","src_id":"9861","5":"9861","creation_date":"1232902322","6":"1232902322"},{"0":"2507","vim_version":"7.0","1":"7.0","script_version":"0.4.4","2":"0.4.4","version_comment":"Fixed problem with autocomplpop.vim ( sometimes it stayed turned off after 0scan ). Added html ctags scan.","3":"Fixed problem with autocomplpop.vim ( sometimes it stayed turned off after 0scan ). Added html ctags scan.","package":"0scan.zip","4":"0scan.zip","src_id":"9799","5":"9799","creation_date":"1231698923","6":"1231698923"},{"0":"2507","vim_version":"7.0","1":"7.0","script_version":"0.4.3","2":"0.4.3","version_comment":"Added python ctags scan support. Keys <C-n>, <C-j>, <C-p>, <C-k> can now be used to select appropriate result line ( Thanks Vincent Wang for feedback )","3":"Added python ctags scan support. Keys <C-n>, <C-j>, <C-p>, <C-k> can now be used to select appropriate result line ( Thanks Vincent Wang for feedback )","package":"0scan.zip","4":"0scan.zip","src_id":"9782","5":"9782","creation_date":"1231498841","6":"1231498841"},{"0":"2507","vim_version":"7.0","1":"7.0","script_version":"0.4.2","2":"0.4.2","version_comment":":OScan<CR> now lists all available scans. :OScan <Tab> now complete with available scans. Thanks Vasilii Pascal for feedback.","3":":OScan<CR> now lists all available scans. :OScan <Tab> now complete with available scans. Thanks Vasilii Pascal for feedback.","package":"0scan.zip","4":"0scan.zip","src_id":"9770","5":"9770","creation_date":"1231344491","6":"1231344491"},{"0":"2507","vim_version":"7.0","1":"7.0","script_version":"0.4.1","2":"0.4.1","version_comment":"clean up zip archive from swap files.","3":"clean up zip archive from swap files.","package":"0scan.zip","4":"0scan.zip","src_id":"9756","5":"9756","creation_date":"1231093053","6":"1231093053"},{"0":"2507","vim_version":"7.0","1":"7.0","script_version":"0.4","2":"0.4","version_comment":"Initial upload","3":"Initial upload","package":"0scan.zip","4":"0scan.zip","src_id":"9755","5":"9755","creation_date":"1231081612","6":"1231081612"}]},"2506":{"script_id":"2506","0":"2506","script_name":"VimIM","1":"VimIM","script_type":"utility","2":"utility","summary":"Vim Input Method -- Vim 中文输入法","3":"Vim Input Method -- Vim 中文输入法","description":"The VimIM is a Vim plugin designed as an independent IM (Input Method)\r\n to support CJK search and CJK input, with or without vim omni popup window.\r\n 　\r\nVimIM 是一个基于Vim的嵌入式中文输入法。\r\n\r\n不启动中文输入法，不换模式，就可以输入中文。\r\n不打开弹出式菜单，不敲中文，也可以搜索中文。\r\n　　　　\r\n中文输入与英文输入不再相互折腾。\r\n中文搜索与英文搜索不再分为彼此。\r\n\r\n　　\r\n正常模式： 　gi  　      无菜单窗中文输入   Insert text ... 　　\r\n正常模式： 　n      　   无菜单窗中文搜索   Repeat the latest \"\/\" or \"?\" ...\r\n插入模式： i_CTRL-_   开关中文输入法      Switch between languages ...\r\n插入模式： i_CTRL-^    切换中文输入法      Toggle the use of language ...　\r\n　　　　　　\r\nGitHub: https:\/\/github.com\/vimim\/vimim\r\n\r\n标准字库： http:\/\/vimim.googlecode.com\/svn\/trunk\/plugin\/vimim.cjk.txt\r\n海量词库： http:\/\/vimim.googlecode.com\/svn\/trunk\/plugin\/vimim.gbk.bsddb\r\n英文词库： http:\/\/vimim.googlecode.com\/svn\/trunk\/plugin\/vimim.txt\r\n民间词库： http:\/\/vimim-data.googlecode.com\r\n　　　　　　　\r\n　　　　　　　　　　　　　　　　　　　　　　　\r\nvim　i　vimim　CTRL-^　CTRL-^　　\r\n　　　　　　　　\r\n日期：公元2012年7月4日　星期三 \r\n电脑：win32  0.011714 seconds \r\n版本：gvim.exe=703 \r\n编码：utf-8　ucs-bom,utf8,chinese,gb18030 \r\n环境：English_United States.1252 \r\n词库：标准字库：C:\/var\/mobile\/vim\/vimfiles\/plugin\/vimim.cjk.txt \r\n词库：英文词库：C:\/var\/mobile\/vim\/vimfiles\/plugin\/vimim.txt \r\n词库：拼音词库：C:\/var\/mobile\/vim\/vimfiles\/plugin\/vimim.gbk.bsddb \r\n词库：云词库：谷歌云　搜狗云　 \r\n联网：Python2 Interface to Vim \r\n输入：VimIM　拼音　四角号码　英文　 \r\n选项：vimimrc \r\n    :let g:vimim_cloud = 'google,sogou,baidu,qq'  \r\n    :let g:vimim_map = 'tab_as_gi'  \r\n  \" :let g:vimim_mode = 'dynamic'  \r\n  \" :let g:vimim_mycloud = 0  \r\n  \" :let g:vimim_plugin = 'C:\/var\/mobile\/vim\/vimfiles\/plugin'  \r\n  \" :let g:vimim_punctuation = 2  \r\n  \" :let g:vimim_shuangpin = 0  \r\n  \" :let g:vimim_toggle = 'pinyin,google,sogou' \r\n　","4":"The VimIM is a Vim plugin designed as an independent IM (Input Method)\r\n to support CJK search and CJK input, with or without vim omni popup window.\r\n 　\r\nVimIM 是一个基于Vim的嵌入式中文输入法。\r\n\r\n不启动中文输入法，不换模式，就可以输入中文。\r\n不打开弹出式菜单，不敲中文，也可以搜索中文。\r\n　　　　\r\n中文输入与英文输入不再相互折腾。\r\n中文搜索与英文搜索不再分为彼此。\r\n\r\n　　\r\n正常模式： 　gi  　      无菜单窗中文输入   Insert text ... 　　\r\n正常模式： 　n      　   无菜单窗中文搜索   Repeat the latest \"\/\" or \"?\" ...\r\n插入模式： i_CTRL-_   开关中文输入法      Switch between languages ...\r\n插入模式： i_CTRL-^    切换中文输入法      Toggle the use of language ...　\r\n　　　　　　\r\nGitHub: https:\/\/github.com\/vimim\/vimim\r\n\r\n标准字库： http:\/\/vimim.googlecode.com\/svn\/trunk\/plugin\/vimim.cjk.txt\r\n海量词库： http:\/\/vimim.googlecode.com\/svn\/trunk\/plugin\/vimim.gbk.bsddb\r\n英文词库： http:\/\/vimim.googlecode.com\/svn\/trunk\/plugin\/vimim.txt\r\n民间词库： http:\/\/vimim-data.googlecode.com\r\n　　　　　　　\r\n　　　　　　　　　　　　　　　　　　　　　　　\r\nvim　i　vimim　CTRL-^　CTRL-^　　\r\n　　　　　　　　\r\n日期：公元2012年7月4日　星期三 \r\n电脑：win32  0.011714 seconds \r\n版本：gvim.exe=703 \r\n编码：utf-8　ucs-bom,utf8,chinese,gb18030 \r\n环境：English_United States.1252 \r\n词库：标准字库：C:\/var\/mobile\/vim\/vimfiles\/plugin\/vimim.cjk.txt \r\n词库：英文词库：C:\/var\/mobile\/vim\/vimfiles\/plugin\/vimim.txt \r\n词库：拼音词库：C:\/var\/mobile\/vim\/vimfiles\/plugin\/vimim.gbk.bsddb \r\n词库：云词库：谷歌云　搜狗云　 \r\n联网：Python2 Interface to Vim \r\n输入：VimIM　拼音　四角号码　英文　 \r\n选项：vimimrc \r\n    :let g:vimim_cloud = 'google,sogou,baidu,qq'  \r\n    :let g:vimim_map = 'tab_as_gi'  \r\n  \" :let g:vimim_mode = 'dynamic'  \r\n  \" :let g:vimim_mycloud = 0  \r\n  \" :let g:vimim_plugin = 'C:\/var\/mobile\/vim\/vimfiles\/plugin'  \r\n  \" :let g:vimim_punctuation = 2  \r\n  \" :let g:vimim_shuangpin = 0  \r\n  \" :let g:vimim_toggle = 'pinyin,google,sogou' \r\n　","install_details":"　　　　\r\n【操作示范】\r\n　　　\r\n体验\u00e2\u0080\u009c点石成金\u00e2\u0080\u009d（英文字母为\u00e2\u0080\u009c石\u00e2\u0080\u009d，中文汉字为\u00e2\u0080\u009c金\u00e2\u0080\u009d）\r\n　　　　\r\n　安装：\r\n　　　　(1)　下载插件　vimim.vim\r\n　　　　(2)　把插件扔到vim的plugin文件夹里面\r\n　彩蛋：\r\n　　　　(1)　进入vim, 进入插入模式\r\n　　　　(2)　输入彩蛋　vimim\r\n　　　　(3)　按 CTRL-^，显示菜单\r\n　　　　(4)　按 h，切换菜单左右排列\r\n　　　　(5)　按 j， 下移光标　\r\n　　　　(6)　按 k，上移光标　\r\n　　　　(7)　按 l， 切换菜单上下排列\r\n　　　　(8)　按 CTRL-^，输出菜单\r\n　输入：\r\n　　　　(1)　进入vim, 进入插入模式 \r\n　　　　(2)　输入 dscj \r\n　　　　(3)　按 CTRL-^\r\n　　　　(4)　验证：\u00e2\u0080\u009c点石成金\u00e2\u0080\u009d出现在菜单　\r\n　搜索：\r\n　　　　(1)　进入vim \r\n　　　　(2)　输入 \/dscj 回车\r\n　　　　(3)　按 n\r\n　　　　(4)　验证：\u00e2\u0080\u009c点石成金\u00e2\u0080\u009d四个字被搜索\r\n　　　　\r\n　　　　\r\n体验\u00e2\u0080\u009c彩云飘飘\u00e2\u0080\u009d（多种云输入）\r\n　　　　　　　　　　　\r\n　安装：\r\n　　　　(1)　下载插件　vimim.vim\r\n　　　　(2)　(Windows) 安装 Python2或Python3 或wget或curl\r\n　彩蛋：\r\n　　　　(1)　进入vim, 进入插入模式\r\n　　　　(2)　输入彩蛋　dscj''''\r\n　　　　(3)　按 CTRL-^，显示四朵云输入结果　\r\n　　　　(4)　按 CTRL-^，输出四朵云输入结果　\r\n　输入：\r\n　　　　(1)　进入vim, 进入插入模式\r\n　　　　(2)　按 CTRL-_，进入谷歌云输入\r\n　　　　(3)　按 CTRL-_，退出谷歌云输入 　　　　　\r\n　　　　　　　\r\n　　　　　　　　　　　　　　　\r\n体验\u00e2\u0080\u009c输入法切换\u00e2\u0080\u009d（包括切换四种云输入） \r\n　　　　　\r\n　安装：\r\n　　　　(1)　下载插件　vimim.vim\r\n　　　　(2)　(option) 下载一个五笔文本文件，例如　vimim.wubi.txt\r\n　　　　(3)　(option) 下载一个拼音文本文件，例如　vimim.pinyin.txt\r\n　　　　(4)　把上述文件扔到vim的plugin文件夹里面　　　　　　\r\n　玩法：\r\n　　　　(1)　进入VimIM （插入模式：CTRL-_）（正常模式：gi） \r\n　　　　(2)　按 CTRL-^，进入五笔输入\r\n　　　　(3)　按 CTRL-^，进入拼音输入\r\n　　　　(4)　按 CTRL-^，进入谷歌云输入 \r\n　　　　(5)　按 CTRL-^，进入搜狗云输入 \r\n　　　　(6)　按 CTRL-^，进入百度云输入\r\n　　　　(7)　按 CTRL-^，进入ＱＱ云输入　\r\n　　　　　\r\n　　　\r\n体验\u00e2\u0080\u009c海量词库\u00e2\u0080\u009d（百万词条，即插即用，想删就删） \r\n　　　　　\r\n　安装：\r\n　　　　(1)　安装 Python2\r\n　　　　(2)　下载47MB拼音数据库　vimim.gbk.bsddb\r\n　　　　(3)　把插件和数据库扔到vim的plugin文件夹里面　\r\n　玩法：\r\n　　　　(1)　进入vim, 进入插入模式\r\n　　　　(2)　按 CTRL-_，进入拼音输入\r\n　　　　(3)　按 CTRL-_，退出拼音输入 \r\n　　　　　　　\r\n　　　　　　　　　　　　　　　　　　　　　\r\n体验\u00e2\u0080\u009c无菜单窗中文输入\u00e2\u0080\u009d（敲中文犹如敲英文）\r\n　　　　　　　\r\n　范例：\r\n　　　　(1)　英文：She has ten dreams. （字母加空格：20键）\r\n　　　　(2)　中文：她有十个梦。　　　  （字母加空格：22键）　　　　　　　　　　　　　　　　　　　　　　　\r\n　玩法：\r\n　　　　(1)　进入vim, 输入 gi\r\n　　　　(2)　输入 ta　　按空格，按空格，出\u00e2\u0080\u009c她\u00e2\u0080\u009d\r\n　　　　(3)　输入 you　 按空格，出\u00e2\u0080\u009c有\u00e2\u0080\u009d\r\n　　　　(4)　输入 shige  按空格，按空格，按空格，出\u00e2\u0080\u009c十个\u00e2\u0080\u009d\r\n　　　　(5)　输入 meng  按空格，出\u00e2\u0080\u009c梦\u00e2\u0080\u009d\r\n　　　　(6)　输入　.　　按空格，出句号。 　　　　　　　　　　　　\r\n　背景：　　　　　　　　　\r\n　　　　(1) 候选窗：无菜单之菜单显示在窗口标题或者状态栏之上\r\n　　　　(2) 数字键：选词：1 用于刷新 234567890 用于选词\r\n　拼音：　　　　　　　　　\r\n　　　　(1) 空格键：既可上字又可选词\r\n　　　　(2) 回车键：取消无菜单选择状态 (stop active completion)\r\n　五笔：　　　　　　　　　\r\n　　　　(1) 空格键：上字（取消无菜单选择状态）或空格\r\n　　　　(2) 打英文：建议在vimrc中设置 :set pastetoggle=<C-H>　　　　　　　　　　　\r\n　　　　　　　　\r\n　　　　　　　\r\nhttp:\/\/code.google.com\/p\/vimim\/issues\/detail?id=207\r\n会玩VimIM的，没有理由不\u00e2\u0080\u009c白领\u00e2\u0080\u009d。 ","5":"　　　　\r\n【操作示范】\r\n　　　\r\n体验\u00e2\u0080\u009c点石成金\u00e2\u0080\u009d（英文字母为\u00e2\u0080\u009c石\u00e2\u0080\u009d，中文汉字为\u00e2\u0080\u009c金\u00e2\u0080\u009d）\r\n　　　　\r\n　安装：\r\n　　　　(1)　下载插件　vimim.vim\r\n　　　　(2)　把插件扔到vim的plugin文件夹里面\r\n　彩蛋：\r\n　　　　(1)　进入vim, 进入插入模式\r\n　　　　(2)　输入彩蛋　vimim\r\n　　　　(3)　按 CTRL-^，显示菜单\r\n　　　　(4)　按 h，切换菜单左右排列\r\n　　　　(5)　按 j， 下移光标　\r\n　　　　(6)　按 k，上移光标　\r\n　　　　(7)　按 l， 切换菜单上下排列\r\n　　　　(8)　按 CTRL-^，输出菜单\r\n　输入：\r\n　　　　(1)　进入vim, 进入插入模式 \r\n　　　　(2)　输入 dscj \r\n　　　　(3)　按 CTRL-^\r\n　　　　(4)　验证：\u00e2\u0080\u009c点石成金\u00e2\u0080\u009d出现在菜单　\r\n　搜索：\r\n　　　　(1)　进入vim \r\n　　　　(2)　输入 \/dscj 回车\r\n　　　　(3)　按 n\r\n　　　　(4)　验证：\u00e2\u0080\u009c点石成金\u00e2\u0080\u009d四个字被搜索\r\n　　　　\r\n　　　　\r\n体验\u00e2\u0080\u009c彩云飘飘\u00e2\u0080\u009d（多种云输入）\r\n　　　　　　　　　　　\r\n　安装：\r\n　　　　(1)　下载插件　vimim.vim\r\n　　　　(2)　(Windows) 安装 Python2或Python3 或wget或curl\r\n　彩蛋：\r\n　　　　(1)　进入vim, 进入插入模式\r\n　　　　(2)　输入彩蛋　dscj''''\r\n　　　　(3)　按 CTRL-^，显示四朵云输入结果　\r\n　　　　(4)　按 CTRL-^，输出四朵云输入结果　\r\n　输入：\r\n　　　　(1)　进入vim, 进入插入模式\r\n　　　　(2)　按 CTRL-_，进入谷歌云输入\r\n　　　　(3)　按 CTRL-_，退出谷歌云输入 　　　　　\r\n　　　　　　　\r\n　　　　　　　　　　　　　　　\r\n体验\u00e2\u0080\u009c输入法切换\u00e2\u0080\u009d（包括切换四种云输入） \r\n　　　　　\r\n　安装：\r\n　　　　(1)　下载插件　vimim.vim\r\n　　　　(2)　(option) 下载一个五笔文本文件，例如　vimim.wubi.txt\r\n　　　　(3)　(option) 下载一个拼音文本文件，例如　vimim.pinyin.txt\r\n　　　　(4)　把上述文件扔到vim的plugin文件夹里面　　　　　　\r\n　玩法：\r\n　　　　(1)　进入VimIM （插入模式：CTRL-_）（正常模式：gi） \r\n　　　　(2)　按 CTRL-^，进入五笔输入\r\n　　　　(3)　按 CTRL-^，进入拼音输入\r\n　　　　(4)　按 CTRL-^，进入谷歌云输入 \r\n　　　　(5)　按 CTRL-^，进入搜狗云输入 \r\n　　　　(6)　按 CTRL-^，进入百度云输入\r\n　　　　(7)　按 CTRL-^，进入ＱＱ云输入　\r\n　　　　　\r\n　　　\r\n体验\u00e2\u0080\u009c海量词库\u00e2\u0080\u009d（百万词条，即插即用，想删就删） \r\n　　　　　\r\n　安装：\r\n　　　　(1)　安装 Python2\r\n　　　　(2)　下载47MB拼音数据库　vimim.gbk.bsddb\r\n　　　　(3)　把插件和数据库扔到vim的plugin文件夹里面　\r\n　玩法：\r\n　　　　(1)　进入vim, 进入插入模式\r\n　　　　(2)　按 CTRL-_，进入拼音输入\r\n　　　　(3)　按 CTRL-_，退出拼音输入 \r\n　　　　　　　\r\n　　　　　　　　　　　　　　　　　　　　　\r\n体验\u00e2\u0080\u009c无菜单窗中文输入\u00e2\u0080\u009d（敲中文犹如敲英文）\r\n　　　　　　　\r\n　范例：\r\n　　　　(1)　英文：She has ten dreams. （字母加空格：20键）\r\n　　　　(2)　中文：她有十个梦。　　　  （字母加空格：22键）　　　　　　　　　　　　　　　　　　　　　　　\r\n　玩法：\r\n　　　　(1)　进入vim, 输入 gi\r\n　　　　(2)　输入 ta　　按空格，按空格，出\u00e2\u0080\u009c她\u00e2\u0080\u009d\r\n　　　　(3)　输入 you　 按空格，出\u00e2\u0080\u009c有\u00e2\u0080\u009d\r\n　　　　(4)　输入 shige  按空格，按空格，按空格，出\u00e2\u0080\u009c十个\u00e2\u0080\u009d\r\n　　　　(5)　输入 meng  按空格，出\u00e2\u0080\u009c梦\u00e2\u0080\u009d\r\n　　　　(6)　输入　.　　按空格，出句号。 　　　　　　　　　　　　\r\n　背景：　　　　　　　　　\r\n　　　　(1) 候选窗：无菜单之菜单显示在窗口标题或者状态栏之上\r\n　　　　(2) 数字键：选词：1 用于刷新 234567890 用于选词\r\n　拼音：　　　　　　　　　\r\n　　　　(1) 空格键：既可上字又可选词\r\n　　　　(2) 回车键：取消无菜单选择状态 (stop active completion)\r\n　五笔：　　　　　　　　　\r\n　　　　(1) 空格键：上字（取消无菜单选择状态）或空格\r\n　　　　(2) 打英文：建议在vimrc中设置 :set pastetoggle=<C-H>　　　　　　　　　　　\r\n　　　　　　　　\r\n　　　　　　　\r\nhttp:\/\/code.google.com\/p\/vimim\/issues\/detail?id=207\r\n会玩VimIM的，没有理由不\u00e2\u0080\u009c白领\u00e2\u0080\u009d。 ","first_name":"Vim","6":"Vim","last_name":"IM","7":"IM","releases":[{"0":"2506","vim_version":"7.0","1":"7.0","script_version":"1.0.0.1","2":"1.0.0.1","version_comment":"just made it work for the latest version of vim ...","3":"just made it work for the latest version of vim ...","package":"vimim.vim","4":"vimim.vim","src_id":"23122","5":"23122","creation_date":"1427956169","6":"1427956169"},{"0":"2506","vim_version":"7.0","1":"7.0","script_version":"1.0.0.0.0","2":"1.0.0.0.0","version_comment":"Happy 4th of July from VimIM.","3":"Happy 4th of July from VimIM.","package":"vimim.vim","4":"vimim.vim","src_id":"18217","5":"18217","creation_date":"1341384674","6":"1341384674"},{"0":"2506","vim_version":"7.0","1":"7.0","script_version":"0.9.9.9.9","2":"0.9.9.9.9","version_comment":"Happy 3 year Anniversary to VimIM! ","3":"Happy 3 year Anniversary to VimIM! ","package":"vimim.vim","4":"vimim.vim","src_id":"17150","5":"17150","creation_date":"1325658098","6":"1325658098"},{"0":"2506","vim_version":"7.0","1":"7.0","script_version":"0.9.9.9.8","2":"0.9.9.9.8","version_comment":"removed over 1000 lines and finalized hotkey definitions, following the same way as Vim does: http:\/\/code.google.com\/p\/vimim\/issues\/detail?id=203","3":"removed over 1000 lines and finalized hotkey definitions, following the same way as Vim does: http:\/\/code.google.com\/p\/vimim\/issues\/detail?id=203","package":"vimim.vim","4":"vimim.vim","src_id":"16843","5":"16843","creation_date":"1320906553","6":"1320906553"},{"0":"2506","vim_version":"7.0","1":"7.0","script_version":"0.9.9.9.7","2":"0.9.9.9.7","version_comment":"#1 VimIM does menuless: http:\/\/code.google.com\/p\/vimim\/issues\/detail?id=182\r\n#2 Less codes with more features: http:\/\/vimim.googlecode.com\/svn\/vimim\/vimim.html#what-is-new\r\n","3":"#1 VimIM does menuless: http:\/\/code.google.com\/p\/vimim\/issues\/detail?id=182\r\n#2 Less codes with more features: http:\/\/vimim.googlecode.com\/svn\/vimim\/vimim.html#what-is-new\r\n","package":"vimim.vim","4":"vimim.vim","src_id":"16646","5":"16646","creation_date":"1318230958","6":"1318230958"},{"0":"2506","vim_version":"7.0","1":"7.0","script_version":"0.9.9.9.6","2":"0.9.9.9.6","version_comment":"Midas touch: http:\/\/code.google.com\/p\/vimim\/issues\/detail?id=172","3":"Midas touch: http:\/\/code.google.com\/p\/vimim\/issues\/detail?id=172","package":"vimim.vim","4":"vimim.vim","src_id":"16369","5":"16369","creation_date":"1314426784","6":"1314426784"},{"0":"2506","vim_version":"7.0","1":"7.0","script_version":"0.9.9.9.5","2":"0.9.9.9.5","version_comment":"plug and play huge datafile: vimim.pinyin.db","3":"plug and play huge datafile: vimim.pinyin.db","package":"vimim.vim","4":"vimim.vim","src_id":"16198","5":"16198","creation_date":"1312507843","6":"1312507843"},{"0":"2506","vim_version":"7.0","1":"7.0","script_version":"0.9.9.9","2":"0.9.9.9","version_comment":"VimIM July 4th release for supporting Google\/Baidu\/Sogou\/QQ clouds:\r\ncaiyunpiaopiao''''<C-6>\r\nhttp:\/\/code.google.com\/p\/vimim\/issues\/detail?id=142\r\nhttp:\/\/vimim.googlecode.com\/svn\/vimim\/vimim.html#what-is-new","3":"VimIM July 4th release for supporting Google\/Baidu\/Sogou\/QQ clouds:\r\ncaiyunpiaopiao''''<C-6>\r\nhttp:\/\/code.google.com\/p\/vimim\/issues\/detail?id=142\r\nhttp:\/\/vimim.googlecode.com\/svn\/vimim\/vimim.html#what-is-new","package":"vimim.vim","4":"vimim.vim","src_id":"16028","5":"16028","creation_date":"1309761267","6":"1309761267"},{"0":"2506","vim_version":"7.0","1":"7.0","script_version":"0.9.9.8","2":"0.9.9.8","version_comment":"tiny bug fixes, plus support for today\/itoday and now\/inow  0.9.9.8\r\nhttp:\/\/code.google.com\/p\/vimim\/issues\/detail?id=142","3":"tiny bug fixes, plus support for today\/itoday and now\/inow  0.9.9.8\r\nhttp:\/\/code.google.com\/p\/vimim\/issues\/detail?id=142","package":"vimim.vim","4":"vimim.vim","src_id":"15691","5":"15691","creation_date":"1305946465","6":"1305946465"},{"0":"2506","vim_version":"7.0","1":"7.0","script_version":"0.9.9.7","2":"0.9.9.7","version_comment":"tiny bug fixes (issues 132 to 137)\r\nhttp:\/\/vimim.googlecode.com\/svn\/vimim\/vimim.html#what-is-new ","3":"tiny bug fixes (issues 132 to 137)\r\nhttp:\/\/vimim.googlecode.com\/svn\/vimim\/vimim.html#what-is-new ","package":"vimim.vim","4":"vimim.vim","src_id":"15604","5":"15604","creation_date":"1304803398","6":"1304803398"},{"0":"2506","vim_version":"7.0","1":"7.0","script_version":"0.9.9.6","2":"0.9.9.6","version_comment":"tiny bug fixes (issues 124 to 131)","3":"tiny bug fixes (issues 124 to 131)","package":"vimim.vim","4":"vimim.vim","src_id":"15496","5":"15496","creation_date":"1303406590","6":"1303406590"},{"0":"2506","vim_version":"7.0","1":"7.0","script_version":"0.9.9.5","2":"0.9.9.5","version_comment":"http:\/\/vimim.googlecode.com\/svn\/vimim\/vimim.html#what-is-new\r\nhttp:\/\/vimim.googlecode.com\/svn\/vimim\/vimim.html#game","3":"http:\/\/vimim.googlecode.com\/svn\/vimim\/vimim.html#what-is-new\r\nhttp:\/\/vimim.googlecode.com\/svn\/vimim\/vimim.html#game","package":"vimim.vim","4":"vimim.vim","src_id":"15397","5":"15397","creation_date":"1302065402","6":"1302065402"},{"0":"2506","vim_version":"7.0","1":"7.0","script_version":"0.9.9","2":"0.9.9","version_comment":"Happy New Year Of the Rabbit! \r\nhttp:\/\/vimim.googlecode.com\/svn\/vimim\/vimim.html#what-is-new\r\nhttp:\/\/code.google.com\/p\/vimim\/issues\/detail?id=113\r\nNow, \"OneKey\" can do both hit-and-run and OneKeyNonStop using hjkl","3":"Happy New Year Of the Rabbit! \r\nhttp:\/\/vimim.googlecode.com\/svn\/vimim\/vimim.html#what-is-new\r\nhttp:\/\/code.google.com\/p\/vimim\/issues\/detail?id=113\r\nNow, \"OneKey\" can do both hit-and-run and OneKeyNonStop using hjkl","package":"vimim.vim","4":"vimim.vim","src_id":"14757","5":"14757","creation_date":"1295132692","6":"1295132692"},{"0":"2506","vim_version":"7.0","1":"7.0","script_version":"0.9.8","2":"0.9.8","version_comment":"fine-tune:  http:\/\/code.google.com\/p\/vimim\/issues\/detail?id=112","3":"fine-tune:  http:\/\/code.google.com\/p\/vimim\/issues\/detail?id=112","package":"vimim.vim","4":"vimim.vim","src_id":"14672","5":"14672","creation_date":"1294030445","6":"1294030445"},{"0":"2506","vim_version":"7.0","1":"7.0","script_version":"0.9.7.1","2":"0.9.7.1","version_comment":"bug-fix: http:\/\/code.google.com\/p\/vimim\/issues\/detail?id=109","3":"bug-fix: http:\/\/code.google.com\/p\/vimim\/issues\/detail?id=109","package":"vimim.vim","4":"vimim.vim","src_id":"14494","5":"14494","creation_date":"1292218560","6":"1292218560"},{"0":"2506","vim_version":"7.0","1":"7.0","script_version":"0.9.7","2":"0.9.7","version_comment":"Welcome to VimIM Chapter 2.\r\nhttp:\/\/vimim.googlecode.com\/svn\/vimim\/vimim.html#what-is-new","3":"Welcome to VimIM Chapter 2.\r\nhttp:\/\/vimim.googlecode.com\/svn\/vimim\/vimim.html#what-is-new","package":"vimim.vim","4":"vimim.vim","src_id":"14419","5":"14419","creation_date":"1291341001","6":"1291341001"},{"0":"2506","vim_version":"7.0","1":"7.0","script_version":"0.9.6","2":"0.9.6","version_comment":"http:\/\/vimim.googlecode.com\/svn\/vimim\/vimim.html#what-is-new","3":"http:\/\/vimim.googlecode.com\/svn\/vimim\/vimim.html#what-is-new","package":"vimim.vim","4":"vimim.vim","src_id":"13043","5":"13043","creation_date":"1274487032","6":"1274487032"},{"0":"2506","vim_version":"7.0","1":"7.0","script_version":"0.9.5","2":"0.9.5","version_comment":"VimIM Cloud access is alive again:\r\nhttp:\/\/code.google.com\/p\/vimim\/wiki\/ChangeLog\r\nhttp:\/\/code.google.com\/p\/vimim\/wiki\/QuickStart","3":"VimIM Cloud access is alive again:\r\nhttp:\/\/code.google.com\/p\/vimim\/wiki\/ChangeLog\r\nhttp:\/\/code.google.com\/p\/vimim\/wiki\/QuickStart","package":"vimim.vim","4":"vimim.vim","src_id":"12730","5":"12730","creation_date":"1269806322","6":"1269806322"},{"0":"2506","vim_version":"7.0","1":"7.0","script_version":"3414","2":"3414","version_comment":"Happy New Year Of the Tiger!\r\nhttp:\/\/vimim.googlecode.com\/svn\/vimim\/vimim.html#changes-in-2010\r\n","3":"Happy New Year Of the Tiger!\r\nhttp:\/\/vimim.googlecode.com\/svn\/vimim\/vimim.html#changes-in-2010\r\n","package":"vimim.vim","4":"vimim.vim","src_id":"12308","5":"12308","creation_date":"1265320412","6":"1265320412"},{"0":"2506","vim_version":"7.0","1":"7.0","script_version":"20100104","2":"20100104","version_comment":"Happy Anniversary to VimIM!\r\nhttp:\/\/vimim.googlecode.com\/svn\/vimim\/vimim.html#the-highest-realm","3":"Happy Anniversary to VimIM!\r\nhttp:\/\/vimim.googlecode.com\/svn\/vimim\/vimim.html#the-highest-realm","package":"vimim.vim","4":"vimim.vim","src_id":"12011","5":"12011","creation_date":"1262625153","6":"1262625153"},{"0":"2506","vim_version":"7.0","1":"7.0","script_version":"3038","2":"3038","version_comment":"Merry Christmas to all VimIM fans!","3":"Merry Christmas to all VimIM fans!","package":"vimim.vim","4":"vimim.vim","src_id":"11949","5":"11949","creation_date":"1261698769","6":"1261698769"},{"0":"2506","vim_version":"7.0","1":"7.0","script_version":"2858","2":"2858","version_comment":"Happy Brithday to You, Angelina!\r\nhttp:\/\/vimim.googlecode.com\/svn\/vimim\/vimim.html#cloud\r\n","3":"Happy Brithday to You, Angelina!\r\nhttp:\/\/vimim.googlecode.com\/svn\/vimim\/vimim.html#cloud\r\n","package":"vimim.vim","4":"vimim.vim","src_id":"11892","5":"11892","creation_date":"1260583359","6":"1260583359"},{"0":"2506","vim_version":"7.0","1":"7.0","script_version":"2686","2":"2686","version_comment":"Support wubi to join the CLOUD party\r\n","3":"Support wubi to join the CLOUD party\r\n","package":"vimim.vim","4":"vimim.vim","src_id":"11825","5":"11825","creation_date":"1259484839","6":"1259484839"},{"0":"2506","vim_version":"7.0","1":"7.0","script_version":"20091126","2":"20091126","version_comment":"CLOUD is colorful now. Happy Thanksgiving!","3":"CLOUD is colorful now. Happy Thanksgiving!","package":"vimim.vim","4":"vimim.vim","src_id":"11809","5":"11809","creation_date":"1259215329","6":"1259215329"},{"0":"2506","vim_version":"7.0","1":"7.0","script_version":"2429","2":"2429","version_comment":"To CLOUD, or not to CLOUD, that is not a question:\r\nhttp:\/\/vimim.googlecode.com\/svn\/vimim\/vimim.html#id36\r\n","3":"To CLOUD, or not to CLOUD, that is not a question:\r\nhttp:\/\/vimim.googlecode.com\/svn\/vimim\/vimim.html#id36\r\n","package":"vimim.vim","4":"vimim.vim","src_id":"11760","5":"11760","creation_date":"1258592873","6":"1258592873"},{"0":"2506","vim_version":"7.0","1":"7.0","script_version":"2410","2":"2410","version_comment":"CLOUD works by \"plug & play\" under Windows and Linux.","3":"CLOUD works by \"plug & play\" under Windows and Linux.","package":"vimim.vim","4":"vimim.vim","src_id":"11743","5":"11743","creation_date":"1258442442","6":"1258442442"},{"0":"2506","vim_version":"7.0","1":"7.0","script_version":"2388","2":"2388","version_comment":"VimIM is promoting \"CLOUD\" input, along with ShuangPin.\r\nhttp:\/\/maxiangjiang.googlepages.com\/vimim.html#id35","3":"VimIM is promoting \"CLOUD\" input, along with ShuangPin.\r\nhttp:\/\/maxiangjiang.googlepages.com\/vimim.html#id35","package":"vimim.vim","4":"vimim.vim","src_id":"11737","5":"11737","creation_date":"1258353071","6":"1258353071"},{"0":"2506","vim_version":"7.0","1":"7.0","script_version":"2323","2":"2323","version_comment":"VimIM is selling dummy \"modeless\" whole sentence input in various \"language\":  http:\/\/maxiangjiang.googlepages.com\/vimim.html#id45 \r\n\r\nAs always, \"what is new\" can be found from the end of manual:  http:\/\/maxiangjiang.googlepages.com\/vimim.html#what-is-new","3":"VimIM is selling dummy \"modeless\" whole sentence input in various \"language\":  http:\/\/maxiangjiang.googlepages.com\/vimim.html#id45 \r\n\r\nAs always, \"what is new\" can be found from the end of manual:  http:\/\/maxiangjiang.googlepages.com\/vimim.html#what-is-new","package":"vimim.vim","4":"vimim.vim","src_id":"11707","5":"11707","creation_date":"1257915947","6":"1257915947"},{"0":"2506","vim_version":"7.0","1":"7.0","script_version":"2111","2":"2111","version_comment":"At last, VimIM has a business model:\r\nhttp:\/\/code.google.com\/p\/vimim\/wiki\/VimIM_Business_Model\r\n","3":"At last, VimIM has a business model:\r\nhttp:\/\/code.google.com\/p\/vimim\/wiki\/VimIM_Business_Model\r\n","package":"vimim.vim","4":"vimim.vim","src_id":"11603","5":"11603","creation_date":"1256613978","6":"1256613978"},{"0":"2506","vim_version":"7.0","1":"7.0","script_version":"1949","2":"1949","version_comment":"On October 1, I found that vimim.vim was downloaded by 1949.\r\n","3":"On October 1, I found that vimim.vim was downloaded by 1949.\r\n","package":"vimim.vim","4":"vimim.vim","src_id":"11468","5":"11468","creation_date":"1254454560","6":"1254454560"},{"0":"2506","vim_version":"7.0","1":"7.0","script_version":"1802","2":"1802","version_comment":"[what's new]   http:\/\/hi.baidu.com\/maxiangjiang\/blog\/item\/64f93a0338b11681d53f7c67.html\r\n","3":"[what's new]   http:\/\/hi.baidu.com\/maxiangjiang\/blog\/item\/64f93a0338b11681d53f7c67.html\r\n","package":"vimim.vim","4":"vimim.vim","src_id":"11305","5":"11305","creation_date":"1251952966","6":"1251952966"},{"0":"2506","vim_version":"7.0","1":"7.0","script_version":"20090714","2":"20090714","version_comment":"(1) ATTENTION: finalized option naming convention\r\n(2) all: http:\/\/maxiangjiang.googlepages.com\/vimim.html \r\n(3) new: http:\/\/vimim.blogspot.com\/2009\/07\/vimim_13.html\r\n","3":"(1) ATTENTION: finalized option naming convention\r\n(2) all: http:\/\/maxiangjiang.googlepages.com\/vimim.html \r\n(3) new: http:\/\/vimim.blogspot.com\/2009\/07\/vimim_13.html\r\n","package":"vimim.vim","4":"vimim.vim","src_id":"11008","5":"11008","creation_date":"1247545429","6":"1247545429"},{"0":"2506","vim_version":"7.0","1":"7.0","script_version":"20090604","2":"20090604","version_comment":"Introduced many new features, and doubled the GDP (line of codes).\r\nNew features:  http:\/\/maxiangjiang.googlepages.com\/vimim.html\r\nNew codes:     http:\/\/maxiangjiang.googlepages.com\/vimim.vim.html\r\n","3":"Introduced many new features, and doubled the GDP (line of codes).\r\nNew features:  http:\/\/maxiangjiang.googlepages.com\/vimim.html\r\nNew codes:     http:\/\/maxiangjiang.googlepages.com\/vimim.vim.html\r\n","package":"vimim.vim","4":"vimim.vim","src_id":"10730","5":"10730","creation_date":"1244090427","6":"1244090427"},{"0":"2506","vim_version":"7.0","1":"7.0","script_version":"3.7","2":"3.7","version_comment":"#1 (new feature) picking up char by word using brackets\r\n#2 fine tunning: Enter=>English, seamless connection\r\n#3 [dynamic] fix regression","3":"#1 (new feature) picking up char by word using brackets\r\n#2 fine tunning: Enter=>English, seamless connection\r\n#3 [dynamic] fix regression","package":"vimim.vim","4":"vimim.vim","src_id":"10435","5":"10435","creation_date":"1240352529","6":"1240352529"},{"0":"2506","vim_version":"7.0","1":"7.0","script_version":"3.6","2":"3.6","version_comment":"#1 finalize the default [chinese input mode] as [dynamic]\r\n#2 finalize the default [dynamic] input style\r\n#3 finalize the default [UI] with better user experiences\r\n#4 [WuBi] support \"non-stop typing\" and \"chinese punctuation\"\r\n#5 [ErBi] start to support ErBi using 31 keys","3":"#1 finalize the default [chinese input mode] as [dynamic]\r\n#2 finalize the default [dynamic] input style\r\n#3 finalize the default [UI] with better user experiences\r\n#4 [WuBi] support \"non-stop typing\" and \"chinese punctuation\"\r\n#5 [ErBi] start to support ErBi using 31 keys","package":"vimim.vim","4":"vimim.vim","src_id":"10425","5":"10425","creation_date":"1240202557","6":"1240202557"},{"0":"2506","vim_version":"7.0","1":"7.0","script_version":"3.5","2":"3.5","version_comment":"#1 finalized \"chinese mode\" toogle key as CTRL-^, to be consistent with Vim\r\n#2 [OneKey] default becomes CTRL-\\, but can be set as CTRL-^ or <Tab>\r\n#3 [OneKey][static] support classic vi key (hjkl) navigation in popup window \r\n#4 [OneKey][static] can \"translate\" English punctuation into Chinese one","3":"#1 finalized \"chinese mode\" toogle key as CTRL-^, to be consistent with Vim\r\n#2 [OneKey] default becomes CTRL-\\, but can be set as CTRL-^ or <Tab>\r\n#3 [OneKey][static] support classic vi key (hjkl) navigation in popup window \r\n#4 [OneKey][static] can \"translate\" English punctuation into Chinese one","package":"vimim.vim","4":"vimim.vim","src_id":"10377","5":"10377","creation_date":"1239396413","6":"1239396413"},{"0":"2506","vim_version":"7.0","1":"7.0","script_version":"3.4","2":"3.4","version_comment":"#1 [static mode] support \"no extra space\" when mixing Chinese and English\r\n#2 [static mode] Chinese punctuation is ON by default","3":"#1 [static mode] support \"no extra space\" when mixing Chinese and English\r\n#2 [static mode] Chinese punctuation is ON by default","package":"vimim.vim","4":"vimim.vim","src_id":"10345","5":"10345","creation_date":"1238817899","6":"1238817899"},{"0":"2506","vim_version":"7.0","1":"7.0","script_version":"3.3","2":"3.3","version_comment":"fix regression on selection by number","3":"fix regression on selection by number","package":"vimim.vim","4":"vimim.vim","src_id":"10311","5":"10311","creation_date":"1238307169","6":"1238307169"},{"0":"2506","vim_version":"7.0","1":"7.0","script_version":"3.2","2":"3.2","version_comment":"# make \"static mode\" as default; better user experience: <Space> => Chinese; <Tab> => English\r\n# to enable \"dynamic mode\": :let g:vimim_enable_dynamic_menu=1\r\n# support \"Double Pinyin (ShangPin) Input Method\" and upload sample datafile, double_pinyin.txt\r\n# add one more easter egg as tradition: **credits","3":"# make \"static mode\" as default; better user experience: <Space> => Chinese; <Tab> => English\r\n# to enable \"dynamic mode\": :let g:vimim_enable_dynamic_menu=1\r\n# support \"Double Pinyin (ShangPin) Input Method\" and upload sample datafile, double_pinyin.txt\r\n# add one more easter egg as tradition: **credits","package":"vimim.vim","4":"vimim.vim","src_id":"10310","5":"10310","creation_date":"1238214511","6":"1238214511"},{"0":"2506","vim_version":"7.0","1":"7.0","script_version":"3.1","2":"3.1","version_comment":"# full support of direct CJK input using Unicode number, integer or hex, as updated at http:\/\/zh.wikipedia.org\/wiki\/Unicode\r\n# add support \"Phonetic Input Method\", which is auto enabled when datafile has \"phonetic\" like sample datafile, vimim.phonetic.txt \r\n","3":"# full support of direct CJK input using Unicode number, integer or hex, as updated at http:\/\/zh.wikipedia.org\/wiki\/Unicode\r\n# add support \"Phonetic Input Method\", which is auto enabled when datafile has \"phonetic\" like sample datafile, vimim.phonetic.txt \r\n","package":"vimim.vim","4":"vimim.vim","src_id":"10258","5":"10258","creation_date":"1237615535","6":"1237615535"},{"0":"2506","vim_version":"7.0","1":"7.0","script_version":"3.0","2":"3.0","version_comment":"# add support \"array input method\", including special char like .,;\/?\r\n# it is auto enabled when datafile has \"array\" like sample datafile, vimim.array30.txt\r\n","3":"# add support \"array input method\", including special char like .,;\/?\r\n# it is auto enabled when datafile has \"array\" like sample datafile, vimim.array30.txt\r\n","package":"vimim.vim","4":"vimim.vim","src_id":"10205","5":"10205","creation_date":"1237010441","6":"1237010441"},{"0":"2506","vim_version":"7.0","1":"7.0","script_version":"2.9","2":"2.9","version_comment":"(1) better user experience for static \"VimIM Chinese Input Mode\" by\r\nsetting let g:vimim_disable_dynamic_menu=1\r\n(2) upload a better\/cleaner pinyin datafile: vimim.pinyin.txt","3":"(1) better user experience for static \"VimIM Chinese Input Mode\" by\r\nsetting let g:vimim_disable_dynamic_menu=1\r\n(2) upload a better\/cleaner pinyin datafile: vimim.pinyin.txt","package":"vimim.vim","4":"vimim.vim","src_id":"10139","5":"10139","creation_date":"1236489742","6":"1236489742"},{"0":"2506","vim_version":"7.0","1":"7.0","script_version":"2.8","2":"2.8","version_comment":"# make VimIM \"easter egg\" permanent, regardless of encoding and datafile. Four key strokes, \"vim<C-^>\", can guarantee that VimIM is working.\r\n","3":"# make VimIM \"easter egg\" permanent, regardless of encoding and datafile. Four key strokes, \"vim<C-^>\", can guarantee that VimIM is working.\r\n","package":"vimim.vim","4":"vimim.vim","src_id":"10074","5":"10074","creation_date":"1235950845","6":"1235950845"},{"0":"2506","vim_version":"7.0","1":"7.0","script_version":"2.7","2":"2.7","version_comment":"add visual pleasure: green cursor indicates vimim Chinese Input Mode","3":"add visual pleasure: green cursor indicates vimim Chinese Input Mode","package":"vimim.vim","4":"vimim.vim","src_id":"10066","5":"10066","creation_date":"1235894446","6":"1235894446"},{"0":"2506","vim_version":"7.0","1":"7.0","script_version":"2.6","2":"2.6","version_comment":"(1) make dynamic-order-sequence persistent\r\n(2) add one super option for XingMa, which can be auto set\r\n(3) build crash-proof logic to get rid of full table scan\r\n(4) optimize search algorithm: faster with less CPU & memory\r\n","3":"(1) make dynamic-order-sequence persistent\r\n(2) add one super option for XingMa, which can be auto set\r\n(3) build crash-proof logic to get rid of full table scan\r\n(4) optimize search algorithm: faster with less CPU & memory\r\n","package":"vimim.vim","4":"vimim.vim","src_id":"10064","5":"10064","creation_date":"1235859375","6":"1235859375"},{"0":"2506","vim_version":"7.0","1":"7.0","script_version":"2.5","2":"2.5","version_comment":"(1) add a new feature: dynamically-adjust-menu-order on past usage frequency\r\n(2) enable direct email\/web addresses input using wildcard prefix\r\n(3) standardize data file name with \"txt\" as filename extension\r\n","3":"(1) add a new feature: dynamically-adjust-menu-order on past usage frequency\r\n(2) enable direct email\/web addresses input using wildcard prefix\r\n(3) standardize data file name with \"txt\" as filename extension\r\n","package":"vimim.vim","4":"vimim.vim","src_id":"9985","5":"9985","creation_date":"1234828612","6":"1234828612"},{"0":"2506","vim_version":"7.0","1":"7.0","script_version":"2.4","2":"2.4","version_comment":"add a dummy English to Chinese translator, showing the potential.\r\nhttp:\/\/maxiangjiang.googlepages.com\/vimim_translator.gif","3":"add a dummy English to Chinese translator, showing the potential.\r\nhttp:\/\/maxiangjiang.googlepages.com\/vimim_translator.gif","package":"vimim.vim","4":"vimim.vim","src_id":"9970","5":"9970","creation_date":"1234603463","6":"1234603463"},{"0":"2506","vim_version":"7.0","1":"7.0","script_version":"2.3","2":"2.3","version_comment":"enable signature by using wildcard *sign","3":"enable signature by using wildcard *sign","package":"vimim.vim","4":"vimim.vim","src_id":"9954","5":"9954","creation_date":"1234416207","6":"1234416207"},{"0":"2506","vim_version":"7.0","1":"7.0","script_version":"2.2","2":"2.2","version_comment":"(1) add support for direct CJK input using unicode number\r\n(2) add option g:enable_pinyin_tone_input for pinyin tone\r\n","3":"(1) add support for direct CJK input using unicode number\r\n(2) add option g:enable_pinyin_tone_input for pinyin tone\r\n","package":"vimim.vim","4":"vimim.vim","src_id":"9930","5":"9930","creation_date":"1234048564","6":"1234048564"},{"0":"2506","vim_version":"7.0","1":"7.0","script_version":"2.1","2":"2.1","version_comment":"(1) add \"easter eggs\"\r\n(2) add dynamic menu\r\n(3) add quick English input\r\n(4) support fuzzy search\r\n(5) support fuzzy pinyin\r\n(6) support \"auto spell\"\r\n(7) enable all common options by default\r\n(8) all options can be explicitly closed\r\n","3":"(1) add \"easter eggs\"\r\n(2) add dynamic menu\r\n(3) add quick English input\r\n(4) support fuzzy search\r\n(5) support fuzzy pinyin\r\n(6) support \"auto spell\"\r\n(7) enable all common options by default\r\n(8) all options can be explicitly closed\r\n","package":"vimim.vim","4":"vimim.vim","src_id":"9901","5":"9901","creation_date":"1233530562","6":"1233530562"},{"0":"2506","vim_version":"7.0","1":"7.0","script_version":"2.0","2":"2.0","version_comment":" (1) relieve UTF-8 encoding restriction\r\n (2) support all power wildcard *\r\n (3) support labeling on menu\r\n","3":" (1) relieve UTF-8 encoding restriction\r\n (2) support all power wildcard *\r\n (3) support labeling on menu\r\n","package":"vimim.vim","4":"vimim.vim","src_id":"9838","5":"9838","creation_date":"1232306524","6":"1232306524"},{"0":"2506","vim_version":"7.0","1":"7.0","script_version":"1.9","2":"1.9","version_comment":"(1) finalized naming: vimim\r\n(2) made data file format simple and flexible\r\n(3) offered 5 data files\r\n(4) fix bugs","3":"(1) finalized naming: vimim\r\n(2) made data file format simple and flexible\r\n(3) offered 5 data files\r\n(4) fix bugs","package":"vimim.vim","4":"vimim.vim","src_id":"9786","5":"9786","creation_date":"1231553932","6":"1231553932"},{"0":"2506","vim_version":"7.0","1":"7.0","script_version":"1.8","2":"1.8","version_comment":"(1) Made new naming\r\n(2) Added quick demo\r\n(3) Showing more information on the popup menu:\r\n(4) In ChineseIM_InsertMode, made punctuation intelligent\r\n","3":"(1) Made new naming\r\n(2) Added quick demo\r\n(3) Showing more information on the popup menu:\r\n(4) In ChineseIM_InsertMode, made punctuation intelligent\r\n","package":"ChineseIM.vim","4":"ChineseIM.vim","src_id":"9768","5":"9768","creation_date":"1231292442","6":"1231292442"},{"0":"2506","vim_version":"7.0","1":"7.0","script_version":"1.7","2":"1.7","version_comment":"Improvement performance when searching started with one or two alphabets.\r\n","3":"Improvement performance when searching started with one or two alphabets.\r\n","package":"ChineseIME.vim","4":"ChineseIME.vim","src_id":"9765","5":"9765","creation_date":"1231228237","6":"1231228237"},{"0":"2506","vim_version":"7.0","1":"7.0","script_version":"1.6","2":"1.6","version_comment":"(1) i_<C-\\>  IME Insert Mode has more default settings\r\n(2) optional comments can be added at the middle on each line of the data file\r\n","3":"(1) i_<C-\\>  IME Insert Mode has more default settings\r\n(2) optional comments can be added at the middle on each line of the data file\r\n","package":"ChineseIME.vim","4":"ChineseIME.vim","src_id":"9764","5":"9764","creation_date":"1231216787","6":"1231216787"},{"0":"2506","vim_version":"7.0","1":"7.0","script_version":"1.5","2":"1.5","version_comment":"Two cosmetical modification:\r\n(1) g:ChineseIME_Toggle_InertMode (i_<C-\\> as default)\r\n(2) g:ChineseIME_Toggle_i_Ctrl6\r\n","3":"Two cosmetical modification:\r\n(1) g:ChineseIME_Toggle_InertMode (i_<C-\\> as default)\r\n(2) g:ChineseIME_Toggle_i_Ctrl6\r\n","package":"ChineseIME.vim","4":"ChineseIME.vim","src_id":"9762","5":"9762","creation_date":"1231177744","6":"1231177744"},{"0":"2506","vim_version":"7.0","1":"7.0","script_version":"1.4","2":"1.4","version_comment":"g:ChineseIMESpaceToggle:\r\n  toggle punctuation \r\n  toggle the use of <Space> to trigger popup\r\n  toggle cursor color to identify the 'IME mode'\r\n","3":"g:ChineseIMESpaceToggle:\r\n  toggle punctuation \r\n  toggle the use of <Space> to trigger popup\r\n  toggle cursor color to identify the 'IME mode'\r\n","package":"ChineseIME.vim","4":"ChineseIME.vim","src_id":"9760","5":"9760","creation_date":"1231135079","6":"1231135079"},{"0":"2506","vim_version":"7.0","1":"7.0","script_version":"1.3","2":"1.3","version_comment":"Performance is boosted.\r\nNo more cache, no more full table scan, after the data file is sorted first.","3":"Performance is boosted.\r\nNo more cache, no more full table scan, after the data file is sorted first.","package":"ChineseIME.vim","4":"ChineseIME.vim","src_id":"9759","5":"9759","creation_date":"1231126942","6":"1231126942"},{"0":"2506","vim_version":"7.0","1":"7.0","script_version":"1.2","2":"1.2","version_comment":" (1) to speed up performance\r\n     let g:CacheIMEDataAtStartup=1\r\n (2) map i_<C-^> to pick up the default right away\r\n     let g:ChineseIMEMappingCtrl6=1\r\n (3) map i_<Tab> to make <Space> \"intelligent\"\r\n     let g:ChineseIMESpaceToggle=1","3":" (1) to speed up performance\r\n     let g:CacheIMEDataAtStartup=1\r\n (2) map i_<C-^> to pick up the default right away\r\n     let g:ChineseIMEMappingCtrl6=1\r\n (3) map i_<Tab> to make <Space> \"intelligent\"\r\n     let g:ChineseIMESpaceToggle=1","package":"ChineseIME.vim","4":"ChineseIME.vim","src_id":"9757","5":"9757","creation_date":"1231113067","6":"1231113067"},{"0":"2506","vim_version":"7.0","1":"7.0","script_version":"1.1","2":"1.1","version_comment":"(1) fix completion hanging after starting from non-word characters \r\n(2) add pumheight=10 to limit the height of popup menu\r\n(3) add two entries on data file for testing datafile:\r\n       (3.1) english<C-^> should show Chinese translation for \"English\"\r\n       (3.2) chinese<C-^> should show Chiense translation for \"Chinese\"","3":"(1) fix completion hanging after starting from non-word characters \r\n(2) add pumheight=10 to limit the height of popup menu\r\n(3) add two entries on data file for testing datafile:\r\n       (3.1) english<C-^> should show Chinese translation for \"English\"\r\n       (3.2) chinese<C-^> should show Chiense translation for \"Chinese\"","package":"ChineseIME.vim","4":"ChineseIME.vim","src_id":"9752","5":"9752","creation_date":"1231051391","6":"1231051391"},{"0":"2506","vim_version":"7.2","1":"7.2","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"ChineseIME.vim","4":"ChineseIME.vim","src_id":"9751","5":"9751","creation_date":"1231035981","6":"1231035981"}]},"2505":{"script_id":"2505","0":"2505","script_name":"tetragrammaton","1":"tetragrammaton","script_type":"color scheme","2":"color scheme","summary":"dark gvim color scheme","3":"dark gvim color scheme","description":"A dark gvim color scheme. Includes coloring for bufexplorer and taglist. Screenshot at http:\/\/tower.sourceforge.net\/tetra.jpg","4":"A dark gvim color scheme. Includes coloring for bufexplorer and taglist. Screenshot at http:\/\/tower.sourceforge.net\/tetra.jpg","install_details":"Put in ~\/.vim\/colors and add \":colors tetragrammaton\" to your .vimrc.","5":"Put in ~\/.vim\/colors and add \":colors tetragrammaton\" to your .vimrc.","first_name":"john","6":"john","last_name":"white","7":"white","releases":[{"0":"2505","vim_version":"6.0","1":"6.0","script_version":"1","2":"1","version_comment":"Initial upload","3":"Initial upload","package":"tetragrammaton.vim","4":"tetragrammaton.vim","src_id":"9745","5":"9745","creation_date":"1230877362","6":"1230877362"}]},"2504":{"script_id":"2504","0":"2504","script_name":"vanzan_color","1":"vanzan_color","script_type":"color scheme","2":"color scheme","summary":"A dark blue (nearly black) color scheme","3":"A dark blue (nearly black) color scheme","description":"Edit: I stopped improving\/caring about this theme. If you were a fan of it and  it hurts you to hear that, find my contact information on http:\/\/leetless.de and tell me so.","4":"Edit: I stopped improving\/caring about this theme. If you were a fan of it and  it hurts you to hear that, find my contact information on http:\/\/leetless.de and tell me so.","install_details":"Put into ~\/.vim\/colors and type :colorscheme vanzan_color","5":"Put into ~\/.vim\/colors and type :colorscheme vanzan_color","first_name":"Henning","6":"Henning","last_name":"Hasemann","7":"Hasemann","releases":[{"0":"2504","vim_version":"6.0","1":"6.0","script_version":"0.2","2":"0.2","version_comment":"Substituted the relatively ugly brown blocks with blueish ones","3":"Substituted the relatively ugly brown blocks with blueish ones","package":"vanzan_color.vim","4":"vanzan_color.vim","src_id":"9863","5":"9863","creation_date":"1232960884","6":"1232960884"},{"0":"2504","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"vanzan_color.vim","4":"vanzan_color.vim","src_id":"9743","5":"9743","creation_date":"1230832617","6":"1230832617"}]},"2503":{"script_id":"2503","0":"2503","script_name":"lightcolors","1":"lightcolors","script_type":"color scheme","2":"color scheme","summary":"Another light colorscheme","3":"Another light colorscheme","description":"Edit: I dropped support of this theme. If you like it and want me to continue working on it, contact me via http:\/\/leetless.de","4":"Edit: I dropped support of this theme. If you like it and want me to continue working on it, contact me via http:\/\/leetless.de","install_details":"Put into ~\/.vim\/colors\/ and use it with :colorscheme lightcolors","5":"Put into ~\/.vim\/colors\/ and use it with :colorscheme lightcolors","first_name":"Henning","6":"Henning","last_name":"Hasemann","7":"Hasemann","releases":[{"0":"2503","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"lightcolors.vim","4":"lightcolors.vim","src_id":"9742","5":"9742","creation_date":"1230832507","6":"1230832507"}]},"2502":{"script_id":"2502","0":"2502","script_name":"fly.vim","1":"fly.vim","script_type":"utility","2":"utility","summary":"An integrated code development environment (incl. Cscope, Web Search, Man Pages)","3":"An integrated code development environment (incl. Cscope, Web Search, Man Pages)","description":"User Guide: \r\n        http:\/\/www.scribd.com\/doc\/9662346\/flyvim\r\n        Also included in the tar ball.\r\n\r\nSummary:\r\n\r\nfly.vim is a vim plugin that may enhance your vim experience (and productivity) with an integrated code development environment. The plugin facilitates rapid code-walkthrough (or flythrough as I call it), enables instant symbol searches and cross references in a large code base, manages stacks of multiple files, includes buffer and directory explorer and integrates code reviews and compilation, all within a simple and intuitive user interface.\r\n\r\nfly.vim integrates seamlessly with source code index databases (Cscope for now), web search engines (Google and Yahoo) and UNIX man pages. Most functions are mapped to shortcut keys, allowing you to fly through a large code base or web in a convenient manner. Using the shortcut mappings, you may search for symbols (or multi-word phrases) after visually highlighting them, or by typing them on vim command line or by taking the cursor to the symbol in a vim window.\r\n\r\nAlthough there are quite a few features to talk about as you will find in the User Guide, it is very easy to get started,\r\n\r\n\u00e2\u0080\u00a2\tDownload and place the fly.vim in your $HOME\/.vim\/plugin\r\n\u00e2\u0080\u00a2\tChange directory (cd) to the root of the source tree (or subtree)\r\n\u00e2\u0080\u00a2\tLaunch vim. Start using the plugin.\r\n\r\nThe plugin has been in use on Linux and FreeBSD with vim 6.x and 7.y.","4":"User Guide: \r\n        http:\/\/www.scribd.com\/doc\/9662346\/flyvim\r\n        Also included in the tar ball.\r\n\r\nSummary:\r\n\r\nfly.vim is a vim plugin that may enhance your vim experience (and productivity) with an integrated code development environment. The plugin facilitates rapid code-walkthrough (or flythrough as I call it), enables instant symbol searches and cross references in a large code base, manages stacks of multiple files, includes buffer and directory explorer and integrates code reviews and compilation, all within a simple and intuitive user interface.\r\n\r\nfly.vim integrates seamlessly with source code index databases (Cscope for now), web search engines (Google and Yahoo) and UNIX man pages. Most functions are mapped to shortcut keys, allowing you to fly through a large code base or web in a convenient manner. Using the shortcut mappings, you may search for symbols (or multi-word phrases) after visually highlighting them, or by typing them on vim command line or by taking the cursor to the symbol in a vim window.\r\n\r\nAlthough there are quite a few features to talk about as you will find in the User Guide, it is very easy to get started,\r\n\r\n\u00e2\u0080\u00a2\tDownload and place the fly.vim in your $HOME\/.vim\/plugin\r\n\u00e2\u0080\u00a2\tChange directory (cd) to the root of the source tree (or subtree)\r\n\u00e2\u0080\u00a2\tLaunch vim. Start using the plugin.\r\n\r\nThe plugin has been in use on Linux and FreeBSD with vim 6.x and 7.y.","install_details":"The tar ball contains fly.vim (the plugin) and the User Guide. After inflating the tar ball, the plugin needs to be placed in $HOME\/.vim\/plugin.\r\n\r\nAfter the installation please follow the steps in chapter 7 (of the User Guide) to get started. You may use chapter 6 as a Quick Reference Sheet for features.","5":"The tar ball contains fly.vim (the plugin) and the User Guide. After inflating the tar ball, the plugin needs to be placed in $HOME\/.vim\/plugin.\r\n\r\nAfter the installation please follow the steps in chapter 7 (of the User Guide) to get started. You may use chapter 6 as a Quick Reference Sheet for features.","first_name":"fly","6":"fly","last_name":"vim","7":"vim","releases":[{"0":"2502","vim_version":"6.0","1":"6.0","script_version":"1.16","2":"1.16","version_comment":"Incorporated received comments, fixed a bug and added cursorline for vim 7+.","3":"Incorporated received comments, fixed a bug and added cursorline for vim 7+.","package":"fly.tgz","4":"fly.tgz","src_id":"9767","5":"9767","creation_date":"1231257712","6":"1231257712"},{"0":"2502","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"fly.tgz","4":"fly.tgz","src_id":"9741","5":"9741","creation_date":"1230830789","6":"1230830789"}]},"2501":{"script_id":"2501","0":"2501","script_name":"VimClojure","1":"VimClojure","script_type":"ftplugin","2":"ftplugin","summary":"A filetype, syntax and indent plugin for Clojure","3":"A filetype, syntax and indent plugin for Clojure","description":"This package contains a filetype, a syntax and an indent plugin\r\nfor the Clojure (http:\/\/clojure.org) programming language.\r\n\r\nSince version 2.0, it also contains the interactive part formerly known as \"Gorilla\".\r\nThis includes:\r\n* docstring lookup\r\n* javadoc lookup\r\n* repl in a vim buffer\r\n* omni completion\r\n\r\n","4":"This package contains a filetype, a syntax and an indent plugin\r\nfor the Clojure (http:\/\/clojure.org) programming language.\r\n\r\nSince version 2.0, it also contains the interactive part formerly known as \"Gorilla\".\r\nThis includes:\r\n* docstring lookup\r\n* javadoc lookup\r\n* repl in a vim buffer\r\n* omni completion\r\n\r\n","install_details":"Extract the archive into your .vim (or vimfiles) directory. Enable syntax highlighting and filetype plugins in your .vimrc.","5":"Extract the archive into your .vim (or vimfiles) directory. Enable syntax highlighting and filetype plugins in your .vimrc.","first_name":"Meikel","6":"Meikel","last_name":"Brandmeyer","7":"Brandmeyer","releases":[{"0":"2501","vim_version":"7.3","1":"7.3","script_version":"2.3.6","2":"2.3.6","version_comment":"Fixed more problems with result window handling. This time hopefully a real fix. Reported by Perry Trolard.","3":"Fixed more problems with result window handling. This time hopefully a real fix. Reported by Perry Trolard.","package":"vimclojure-2.3.6.zip","4":"vimclojure-2.3.6.zip","src_id":"18485","5":"18485","creation_date":"1345838694","6":"1345838694"},{"0":"2501","vim_version":"7.3","1":"7.3","script_version":"2.3.5","2":"2.3.5","version_comment":"Bugfix release:\r\n\r\n* Fixing serious regression in result window handling introduced in v2.3.4 (reported by Wolodja Wentland)\r\n* Fix indentation issue with multibyte function names (patch by Sung Pae)\r\n","3":"Bugfix release:\r\n\r\n* Fixing serious regression in result window handling introduced in v2.3.4 (reported by Wolodja Wentland)\r\n* Fix indentation issue with multibyte function names (patch by Sung Pae)\r\n","package":"vimclojure-2.3.5.zip","4":"vimclojure-2.3.5.zip","src_id":"18412","5":"18412","creation_date":"1345062484","6":"1345062484"},{"0":"2501","vim_version":"7.3","1":"7.3","script_version":"2.3.4","2":"2.3.4","version_comment":"Bugfix release:\r\n\r\n* Fixed some typos in the documentation (thanks to Ambrose Bonnaire-Sergeant)\r\n* Mark temporary vimclojure buffers with vimclojure filetype (patch by Krisa Jenkins)\r\n* Reworked window handling of vimclojure temporary buffers\r\n* Fixed indentation of functions with multibyte names (patch by Sung Pae)\r\n","3":"Bugfix release:\r\n\r\n* Fixed some typos in the documentation (thanks to Ambrose Bonnaire-Sergeant)\r\n* Mark temporary vimclojure buffers with vimclojure filetype (patch by Krisa Jenkins)\r\n* Reworked window handling of vimclojure temporary buffers\r\n* Fixed indentation of functions with multibyte names (patch by Sung Pae)\r\n","package":"vimclojure-2.3.4.zip","4":"vimclojure-2.3.4.zip","src_id":"18380","5":"18380","creation_date":"1344460521","6":"1344460521"},{"0":"2501","vim_version":"7.2","1":"7.2","script_version":"v2.3.3","2":"v2.3.3","version_comment":"v2.3.2 introduced a serious regression concerning key mappings. This releases fixes this regression.\r\n\r\nAdditionally - as a consolation so to say - custom fuzzy indent pattern are introduced.\r\n","3":"v2.3.2 introduced a serious regression concerning key mappings. This releases fixes this regression.\r\n\r\nAdditionally - as a consolation so to say - custom fuzzy indent pattern are introduced.\r\n","package":"vimclojure-2.3.3.zip","4":"vimclojure-2.3.3.zip","src_id":"18115","5":"18115","creation_date":"1339449558","6":"1339449558"},{"0":"2501","vim_version":"7.0","1":"7.0","script_version":"2.3.2","2":"2.3.2","version_comment":"Bugfix release with various fixes.\r\n\r\n* Disambiguate <Plug> names (reported by Sung Pae)\r\n* Fixed slow down of indentation for large files (reported by Brandon Bloom)\r\n* Fixed clear() method for Repl\r\n* Fixed repetition for block functions (patch by Sung Pae)\r\n* Send only exact visual block for evaluation (reported by Perry Trolard)\r\n* Made keymappings configurable (incl. whitelisting of keymappings)\r\n* Delete old autocmds for adding new ones (reported by Sung Pae)\r\n* Fixed indentation of extend in letfn heuristic\r\n* Include forms starting in let in fuzzy indentation\r\n* Fixed highlighting of keywords (reported by Gianni Chiapetta)\r\n* Fixed (hopefully) carriage returns on Windows (reported by vitalyper)\r\n* Fixed highlighting of new meta reader macro (reported by Gianni Chiapetta)\r\n","3":"Bugfix release with various fixes.\r\n\r\n* Disambiguate <Plug> names (reported by Sung Pae)\r\n* Fixed slow down of indentation for large files (reported by Brandon Bloom)\r\n* Fixed clear() method for Repl\r\n* Fixed repetition for block functions (patch by Sung Pae)\r\n* Send only exact visual block for evaluation (reported by Perry Trolard)\r\n* Made keymappings configurable (incl. whitelisting of keymappings)\r\n* Delete old autocmds for adding new ones (reported by Sung Pae)\r\n* Fixed indentation of extend in letfn heuristic\r\n* Include forms starting in let in fuzzy indentation\r\n* Fixed highlighting of keywords (reported by Gianni Chiapetta)\r\n* Fixed (hopefully) carriage returns on Windows (reported by vitalyper)\r\n* Fixed highlighting of new meta reader macro (reported by Gianni Chiapetta)\r\n","package":"vimclojure-2.3.2.zip","4":"vimclojure-2.3.2.zip","src_id":"18091","5":"18091","creation_date":"1338846359","6":"1338846359"},{"0":"2501","vim_version":"7.3","1":"7.3","script_version":"2.3.1","2":"2.3.1","version_comment":"Bugfix release with various fixes.\r\n\r\n* Fixed regression in highlighting of numeric functions. (Reported by Ogino-san.)\r\n* Restore various registers correctly after yanking. (Reported by Dave Ray.)\r\n* Improved fuzzy indent heuristic and fixed special case for with-meta.\r\n* Removed highlighting of the comment form. It's broken and unlikely to be ever fixed. (Reported by Dave Ray.)\r\n* Fixed version range for the clojure dependency. [1.2,1.5)\r\n* Removed usages of anonymous functions. This caused a small delay when using 'o' or 'O' commands. (Interestingly only then but with a normal carriage return\u00e2\u0080\u00a6) This problem was a long lasting issue for several years. A big big thank you to Dave Ray for tracking this down!\r\n* Loads the user.clj if found on the classpath of the server.\r\n* Fixed problems with result buffers when issuing certain sequences of commands. (Reported by Dave Ray.)\r\n* Made gradle plugin milestone 6 compatible.\r\n","3":"Bugfix release with various fixes.\r\n\r\n* Fixed regression in highlighting of numeric functions. (Reported by Ogino-san.)\r\n* Restore various registers correctly after yanking. (Reported by Dave Ray.)\r\n* Improved fuzzy indent heuristic and fixed special case for with-meta.\r\n* Removed highlighting of the comment form. It's broken and unlikely to be ever fixed. (Reported by Dave Ray.)\r\n* Fixed version range for the clojure dependency. [1.2,1.5)\r\n* Removed usages of anonymous functions. This caused a small delay when using 'o' or 'O' commands. (Interestingly only then but with a normal carriage return\u00e2\u0080\u00a6) This problem was a long lasting issue for several years. A big big thank you to Dave Ray for tracking this down!\r\n* Loads the user.clj if found on the classpath of the server.\r\n* Fixed problems with result buffers when issuing certain sequences of commands. (Reported by Dave Ray.)\r\n* Made gradle plugin milestone 6 compatible.\r\n","package":"vimclojure-2.3.1.zip","4":"vimclojure-2.3.1.zip","src_id":"17125","5":"17125","creation_date":"1325112456","6":"1325112456"},{"0":"2501","vim_version":"7.3","1":"7.3","script_version":"2.3.0","2":"2.3.0","version_comment":"* The nailgun server and port may now be configured.\r\n* Rainbow parens may be toggled on or off.\r\n* The fuzzy indent option improves indentation based on the form name.\r\n* The Repl now always enters a newline on <CR>. <C-CR> submits the expression. This can be easily flipped if desired.","3":"* The nailgun server and port may now be configured.\r\n* Rainbow parens may be toggled on or off.\r\n* The fuzzy indent option improves indentation based on the form name.\r\n* The Repl now always enters a newline on <CR>. <C-CR> submits the expression. This can be easily flipped if desired.","package":"vimclojure-2.3.0.zip","4":"vimclojure-2.3.0.zip","src_id":"16625","5":"16625","creation_date":"1317845299","6":"1317845299"},{"0":"2501","vim_version":"7.3","1":"7.3","script_version":"2.2.0","2":"2.2.0","version_comment":"Finally a new release. Bringing VimClojure up to date with 1.2 and 1.3 alpha. Please consult the README in the zip file for further installation instructions.","3":"Finally a new release. Bringing VimClojure up to date with 1.2 and 1.3 alpha. Please consult the README in the zip file for further installation instructions.","package":"vimclojure-2.2.0.zip","4":"vimclojure-2.2.0.zip","src_id":"13986","5":"13986","creation_date":"1286221329","6":"1286221329"},{"0":"2501","vim_version":"7.0","1":"7.0","script_version":"2.1.2","2":"2.1.2","version_comment":"This release is compatible with Clojure 1.0 and\r\nClojure-Contrib 919 (in old SVN terms). Other\r\npre-GTIC contrib versions from Github should also\r\nwork. For Clojure(-Contrib) head consider using the\r\nbleeding-edge branch from the repository.\r\n\r\nThe Ivy configuration will fetch an known-to-work\r\nClojure(-Contrib) version. For manual compilation,\r\nyou have to care for that yourself. A compiled jar\r\nis already included in the distribution in the build\r\nsubdirectory.\r\n\r\nChanges since v2.1.1:\r\n\r\n* Fixed a regression of qualified keywords highlighting\r\n* Fixed a infinite loop if there is no prompt in the Repl buffer\r\n* Made compilation of ng client a bit more comfortable\r\n* Added library configuration for OpenSolaris (thanks to Richard Newman)\r\n* Changed normal invokations to ignore keymappings (reported by James Reeves)\r\n* Fixed typo in lispwords: defmethod -> defmulti\r\n* Added letfn to lispwords\r\n* Added c.c.def\/defnk to lispwords\r\n* Added #_ and #! as comment indicators to syntax highlighting\r\n  (currently only the #_ is marked as comment, the following form\r\n  is still highlighted normally.)\r\n* Fixed annoying o\/O delay bug\r\n* Simplified plugin installation","3":"This release is compatible with Clojure 1.0 and\r\nClojure-Contrib 919 (in old SVN terms). Other\r\npre-GTIC contrib versions from Github should also\r\nwork. For Clojure(-Contrib) head consider using the\r\nbleeding-edge branch from the repository.\r\n\r\nThe Ivy configuration will fetch an known-to-work\r\nClojure(-Contrib) version. For manual compilation,\r\nyou have to care for that yourself. A compiled jar\r\nis already included in the distribution in the build\r\nsubdirectory.\r\n\r\nChanges since v2.1.1:\r\n\r\n* Fixed a regression of qualified keywords highlighting\r\n* Fixed a infinite loop if there is no prompt in the Repl buffer\r\n* Made compilation of ng client a bit more comfortable\r\n* Added library configuration for OpenSolaris (thanks to Richard Newman)\r\n* Changed normal invokations to ignore keymappings (reported by James Reeves)\r\n* Fixed typo in lispwords: defmethod -> defmulti\r\n* Added letfn to lispwords\r\n* Added c.c.def\/defnk to lispwords\r\n* Added #_ and #! as comment indicators to syntax highlighting\r\n  (currently only the #_ is marked as comment, the following form\r\n  is still highlighted normally.)\r\n* Fixed annoying o\/O delay bug\r\n* Simplified plugin installation","package":"vimclojure-2.1.2.zip","4":"vimclojure-2.1.2.zip","src_id":"11066","5":"11066","creation_date":"1248599283","6":"1248599283"},{"0":"2501","vim_version":"7.0","1":"7.0","script_version":"2.1.1","2":"2.1.1","version_comment":"This is a bugfix release.\r\n\r\n* fixed syntax highlighting of strings with escaped quotes\r\n* added syntax highlighting of numbers in radixR format\r\n* added missing clojure names to highlighting\r\n* fixed keyword highlighting\r\n* fixed find invocation in launcher\r\n* fixed spurious -1 in EvalLine\r\n\r\n","3":"This is a bugfix release.\r\n\r\n* fixed syntax highlighting of strings with escaped quotes\r\n* added syntax highlighting of numbers in radixR format\r\n* added missing clojure names to highlighting\r\n* fixed keyword highlighting\r\n* fixed find invocation in launcher\r\n* fixed spurious -1 in EvalLine\r\n\r\n","package":"vimclojure-2.1.1.zip","4":"vimclojure-2.1.1.zip","src_id":"10755","5":"10755","creation_date":"1244276956","6":"1244276956"},{"0":"2501","vim_version":"7.0","1":"7.0","script_version":"2.1.0","2":"2.1.0","version_comment":"New features: \r\n* improved completion \r\n* goto source \r\n* show source \r\n* stacktrace short-cuts for the Repl \r\n* more robust in case of not running server \r\n* improved error messages \r\n* dynamic syntax highlighting for use'd and alias'd namespaces \r\n* pretty printing of macros expansions \r\n* improved build system with optional Ivy dependency resolution \r\n* simplification of plugin installation procedure \r\n\r\nFixed many bugs, in particular: \r\n* resizing windows when executing nails \r\n* EvalToplevel evaluated more than one expression \r\n* Line and File number information is now correctly when sending expressions ","3":"New features: \r\n* improved completion \r\n* goto source \r\n* show source \r\n* stacktrace short-cuts for the Repl \r\n* more robust in case of not running server \r\n* improved error messages \r\n* dynamic syntax highlighting for use'd and alias'd namespaces \r\n* pretty printing of macros expansions \r\n* improved build system with optional Ivy dependency resolution \r\n* simplification of plugin installation procedure \r\n\r\nFixed many bugs, in particular: \r\n* resizing windows when executing nails \r\n* EvalToplevel evaluated more than one expression \r\n* Line and File number information is now correctly when sending expressions ","package":"vimclojure-2.1.0.zip","4":"vimclojure-2.1.0.zip","src_id":"10405","5":"10405","creation_date":"1239813109","6":"1239813109"},{"0":"2501","vim_version":"7.0","1":"7.0","script_version":"2.0.0","2":"2.0.0","version_comment":"Updated for latest Clojure SVN. Merged with Gorilla.","3":"Updated for latest Clojure SVN. Merged with Gorilla.","package":"vimclojure-2.0.0.tar.gz","4":"vimclojure-2.0.0.tar.gz","src_id":"10166","5":"10166","creation_date":"1236728130","6":"1236728130"},{"0":"2501","vim_version":"7.2","1":"7.2","script_version":"1.3.0","2":"1.3.0","version_comment":"Initial upload","3":"Initial upload","package":"vimclojure-1.3.0.tar.gz","4":"vimclojure-1.3.0.tar.gz","src_id":"9740","5":"9740","creation_date":"1230826065","6":"1230826065"}]},"2500":{"script_id":"2500","0":"2500","script_name":"TUT (toggle_unit_tests)","1":"TUT (toggle_unit_tests)","script_type":"utility","2":"utility","summary":"A plug-in for toggling between source and unit test files","3":"A plug-in for toggling between source and unit test files","description":"Usage:\r\n\r\nUse this plug-in when you are doing Test-Driven Development [TDD] in any\r\nlanguage to quickly switch between unit-test and production code. To make this\r\nreally fast bind the Toggle function to a function key in your .vimrc:\r\n\r\n    \"   [F3]    toggles between (header, ) source and test files.\r\n    nnoremap    <F3> :<C-U>TUT<CR>\r\n\r\nThis plug-in assumes source and unit test files are in the same directory.\r\n\r\nCommands:\r\n\r\n:TUT\r\n    Toggles betwixt source and unit test file\r\n\r\nMappings:\r\n\r\n<Leader>tut\r\n    Calls :TUT\r\n\r\nSettings:\r\n\r\nBy default, unit-test filenames are deemed to begin with 't_'.\r\n\r\nTell toggle_unit_tests.vim your own prefix by setting the following global\r\nvariable, perhaps in your .vimrc:\r\n\r\n    let g:unit_test_prefix='test_'\r\n\r\nUpdate:\r\n\r\nYou can now grab the latest version, submit an improvement or report a bug on\r\nGitHub:\r\n\r\n    http:\/\/github.com\/johnsyweb\/vim-tut\/\r\n","4":"Usage:\r\n\r\nUse this plug-in when you are doing Test-Driven Development [TDD] in any\r\nlanguage to quickly switch between unit-test and production code. To make this\r\nreally fast bind the Toggle function to a function key in your .vimrc:\r\n\r\n    \"   [F3]    toggles between (header, ) source and test files.\r\n    nnoremap    <F3> :<C-U>TUT<CR>\r\n\r\nThis plug-in assumes source and unit test files are in the same directory.\r\n\r\nCommands:\r\n\r\n:TUT\r\n    Toggles betwixt source and unit test file\r\n\r\nMappings:\r\n\r\n<Leader>tut\r\n    Calls :TUT\r\n\r\nSettings:\r\n\r\nBy default, unit-test filenames are deemed to begin with 't_'.\r\n\r\nTell toggle_unit_tests.vim your own prefix by setting the following global\r\nvariable, perhaps in your .vimrc:\r\n\r\n    let g:unit_test_prefix='test_'\r\n\r\nUpdate:\r\n\r\nYou can now grab the latest version, submit an improvement or report a bug on\r\nGitHub:\r\n\r\n    http:\/\/github.com\/johnsyweb\/vim-tut\/\r\n","install_details":"I recommend installing pathogen.vim (vimscript#2332), and then simply copy and paste: \r\n\r\n    cd ~\/.vim\/bundle\r\n    git clone git:\/\/github.com\/johnsyweb\/vim-tut.git\r\n    vim -cHelptags -cq\r\n\r\nOnce help tags have been generated, you can view the manual with:\r\n\r\n    :help toggle_unit_tests\r\n\r\nAlternatively, just unzip the file into your 'runtimepath' and run :helptags.","5":"I recommend installing pathogen.vim (vimscript#2332), and then simply copy and paste: \r\n\r\n    cd ~\/.vim\/bundle\r\n    git clone git:\/\/github.com\/johnsyweb\/vim-tut.git\r\n    vim -cHelptags -cq\r\n\r\nOnce help tags have been generated, you can view the manual with:\r\n\r\n    :help toggle_unit_tests\r\n\r\nAlternatively, just unzip the file into your 'runtimepath' and run :helptags.","first_name":"Pete","6":"Pete","last_name":"Johns","7":"Johns","releases":[{"0":"2500","vim_version":"7.0","1":"7.0","script_version":"1.2","2":"1.2","version_comment":"https:\/\/github.com\/johnsyweb\/vim-tut\/compare\/1.1...1.2","3":"https:\/\/github.com\/johnsyweb\/vim-tut\/compare\/1.1...1.2","package":"vim-tut-1.2.zip","4":"vim-tut-1.2.zip","src_id":"21541","5":"21541","creation_date":"1393496127","6":"1393496127"},{"0":"2500","vim_version":"7.0","1":"7.0","script_version":"1.1","2":"1.1","version_comment":"Fixed annoying bug where if a file was already loaded into a buffer, the cursor would move to the top when switching.\r\n\r\nRefactored code to make easier to read and maintain.\r\n","3":"Fixed annoying bug where if a file was already loaded into a buffer, the cursor would move to the top when switching.\r\n\r\nRefactored code to make easier to read and maintain.\r\n","package":"toggle_unit_tests.vba","4":"toggle_unit_tests.vba","src_id":"11130","5":"11130","creation_date":"1249439414","6":"1249439414"},{"0":"2500","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"toggle_unit_tests.vba","4":"toggle_unit_tests.vba","src_id":"9739","5":"9739","creation_date":"1230807422","6":"1230807422"}]},"2499":{"script_id":"2499","0":"2499","script_name":"blood","1":"blood","script_type":"color scheme","2":"color scheme","summary":"A dark red, still somewhat colorful colorscheme","3":"A dark red, still somewhat colorful colorscheme","description":"This colorscheme uses a dark background with a slight red tint.\r\nThe syntax elements have colors mostly different from red so its easy for the eye to catch different elements.\r\n\r\nI mostly use it for python\/d code. As this theme is still very new, there might be some important highlighting groups missing atm, sorry for that.\r\n\r\nEdit: Support for this theme is discontinued. If you are really a fan of it, contact me via http:\/\/leetless.de, if I see some request for this theme I might continue to support it.","4":"This colorscheme uses a dark background with a slight red tint.\r\nThe syntax elements have colors mostly different from red so its easy for the eye to catch different elements.\r\n\r\nI mostly use it for python\/d code. As this theme is still very new, there might be some important highlighting groups missing atm, sorry for that.\r\n\r\nEdit: Support for this theme is discontinued. If you are really a fan of it, contact me via http:\/\/leetless.de, if I see some request for this theme I might continue to support it.","install_details":"Copy to ~\/.vim\/colors\/ and type :colors blood","5":"Copy to ~\/.vim\/colors\/ and type :colors blood","first_name":"Henning","6":"Henning","last_name":"Hasemann","7":"Hasemann","releases":[{"0":"2499","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"asmanian_blood.vim","4":"asmanian_blood.vim","src_id":"9736","5":"9736","creation_date":"1230740222","6":"1230740222"}]},"2498":{"script_id":"2498","0":"2498","script_name":"note","1":"note","script_type":"patch","2":"patch","summary":"hjhjhj","3":"hjhjhj","description":"hjhj","4":"hjhj","install_details":"","5":"","first_name":"m","6":"m","last_name":"pb","7":"pb","releases":[{"0":"2498","vim_version":"6.0","1":"6.0","script_version":"jhj","2":"jhj","version_comment":"Initial upload","3":"Initial upload","package":"UUrlFetch.class","4":"UUrlFetch.class","src_id":"9735","5":"9735","creation_date":"1230722032","6":"1230722032"}]},"2497":{"script_id":"2497","0":"2497","script_name":"shellinsidevim.vim","1":"shellinsidevim.vim","script_type":"utility","2":"utility","summary":"Let you execute the shell command without leaving vim","3":"Let you execute the shell command without leaving vim","description":"New version has combined into http:\/\/www.vim.org\/scripts\/script.php?script_id=2793\r\n\r\n --Typing the Ex command \"Shell\" will also allow you to run a Shell which you\r\n   give and pass up to 20 parameters to that shell.\r\n\r\n   Sample syntax...\r\n       :Shell ps -e\r\n\r\n --Pressing \"F4\" will toggle the display of a buffer containing the output\r\n   produced when running the shell command.\r\n\r\n **************************Some special syntax format**************************\r\n\r\n --If a Shell command starts with \":\", this Shell will be executed as a vim Ex\r\n  command, this is convenience if you map this command to a shortcut such as:\r\n\r\n  map <CR> :Shell\r\n\r\n  Then you could use this script to execute all the normal command directly.\r\n\r\n  --If a Shell command starts with \">\", this Shell will be executed with inputs\r\n  which come from a file, which name is \".VIM_STD_IN\". If the input file dose\r\n not exsits, you could give the inputs line by line by typing directly.\r\n\r\n  --If a Shell command ends with \";\", this Shell will be executed as a program\r\n  development tool. You could use this script for your development, then you \r\n  could pass the compile or interpret command as the Shell parameters with \";\"\r\n  followed. When the command finished it will jump to the first error line if\r\n  there are some errors. Of caurse you should special a compiler first.","4":"New version has combined into http:\/\/www.vim.org\/scripts\/script.php?script_id=2793\r\n\r\n --Typing the Ex command \"Shell\" will also allow you to run a Shell which you\r\n   give and pass up to 20 parameters to that shell.\r\n\r\n   Sample syntax...\r\n       :Shell ps -e\r\n\r\n --Pressing \"F4\" will toggle the display of a buffer containing the output\r\n   produced when running the shell command.\r\n\r\n **************************Some special syntax format**************************\r\n\r\n --If a Shell command starts with \":\", this Shell will be executed as a vim Ex\r\n  command, this is convenience if you map this command to a shortcut such as:\r\n\r\n  map <CR> :Shell\r\n\r\n  Then you could use this script to execute all the normal command directly.\r\n\r\n  --If a Shell command starts with \">\", this Shell will be executed with inputs\r\n  which come from a file, which name is \".VIM_STD_IN\". If the input file dose\r\n not exsits, you could give the inputs line by line by typing directly.\r\n\r\n  --If a Shell command ends with \";\", this Shell will be executed as a program\r\n  development tool. You could use this script for your development, then you \r\n  could pass the compile or interpret command as the Shell parameters with \";\"\r\n  followed. When the command finished it will jump to the first error line if\r\n  there are some errors. Of caurse you should special a compiler first.","install_details":"","5":"","first_name":"Zhenliang","6":"Zhenliang","last_name":"Ju","7":"Ju","releases":[{"0":"2497","vim_version":"7.0","1":"7.0","script_version":"2.7","2":"2.7","version_comment":"In some different platforms, the vim may not support the feature '@+'.\r\nSo these vimers will not use the result of the shell command in the System Clipboard.\r\n\r\nBTW: This function of the plugin is unpublicized before.","3":"In some different platforms, the vim may not support the feature '@+'.\r\nSo these vimers will not use the result of the shell command in the System Clipboard.\r\n\r\nBTW: This function of the plugin is unpublicized before.","package":"shellinsidevim.tar.bz2","4":"shellinsidevim.tar.bz2","src_id":"11424","5":"11424","creation_date":"1253768869","6":"1253768869"},{"0":"2497","vim_version":"7.0","1":"7.0","script_version":"2.6","2":"2.6","version_comment":"support the 'cd' command to change the current directory\r\nAnother fine adjustment","3":"support the 'cd' command to change the current directory\r\nAnother fine adjustment","package":"shellinsidevim.tar.bz2","4":"shellinsidevim.tar.bz2","src_id":"11417","5":"11417","creation_date":"1253689218","6":"1253689218"},{"0":"2497","vim_version":"7.0","1":"7.0","script_version":"2.4","2":"2.4","version_comment":"Changed:\r\nThis version, you can put them into any plugin directory of your runtime path.\r\nThe old version only can find the common.vim if it is in the vim root plugin directory.","3":"Changed:\r\nThis version, you can put them into any plugin directory of your runtime path.\r\nThe old version only can find the common.vim if it is in the vim root plugin directory.","package":"shellinsidevim.tbz2","4":"shellinsidevim.tbz2","src_id":"10142","5":"10142","creation_date":"1236562897","6":"1236562897"},{"0":"2497","vim_version":"7.0","1":"7.0","script_version":"2.3","2":"2.3","version_comment":"Updated:\r\n1.Add three global variables:\r\na. g:ShowOutputWindowWhenVimLaunched. \r\nIf its value gather then 0, The output window will open. The default value is 1.\r\nb. g:AutoShowOutputWindow.\r\nif its value is non-zero, the output window will open after command executing if it was closed.\r\nc. g:ShowOutputInCommandline\r\nIf its value is non-zero, the outputs from system() will also echoed at the vim command line.\r\n\r\n2.You can use \"clear\" shell command to clear the output windows","3":"Updated:\r\n1.Add three global variables:\r\na. g:ShowOutputWindowWhenVimLaunched. \r\nIf its value gather then 0, The output window will open. The default value is 1.\r\nb. g:AutoShowOutputWindow.\r\nif its value is non-zero, the output window will open after command executing if it was closed.\r\nc. g:ShowOutputInCommandline\r\nIf its value is non-zero, the outputs from system() will also echoed at the vim command line.\r\n\r\n2.You can use \"clear\" shell command to clear the output windows","package":"shellinsidevim.tbz2","4":"shellinsidevim.tbz2","src_id":"10138","5":"10138","creation_date":"1236485682","6":"1236485682"},{"0":"2497","vim_version":"7.0","1":"7.0","script_version":"2.2","2":"2.2","version_comment":"Divide the common functions into a single vim file.","3":"Divide the common functions into a single vim file.","package":"shellinsidevim.tbz2","4":"shellinsidevim.tbz2","src_id":"10114","5":"10114","creation_date":"1236229113","6":"1236229113"},{"0":"2497","vim_version":"7.0","1":"7.0","script_version":"2.2","2":"2.2","version_comment":"changed:\r\nCatch the exception from system(), this is useful when you interrupt the shell.\r\n\r\nGive some more variables for controlling the output.\r\n","3":"changed:\r\nCatch the exception from system(), this is useful when you interrupt the shell.\r\n\r\nGive some more variables for controlling the output.\r\n","package":"shellinsidevim.vim","4":"shellinsidevim.vim","src_id":"10109","5":"10109","creation_date":"1236172967","6":"1236172967"},{"0":"2497","vim_version":"7.0","1":"7.0","script_version":"2.1","2":"2.1","version_comment":"fixed bug：\r\nThe shell with input file by invoking system(exp,input) does not work, maybe this is a bug of vim itself.\r\n\r\nupdate:\r\nThe message in the output window is highlighted for reading.\r\n\r\nchanged:\r\nThe input file has a fixed name called \".VIM_STD_IN\", the orig variable g:VIM_STD_IN_FILE has been deleted.\r\n\r\nOther:\r\nlast version I gave an error email , this is a correct one","3":"fixed bug：\r\nThe shell with input file by invoking system(exp,input) does not work, maybe this is a bug of vim itself.\r\n\r\nupdate:\r\nThe message in the output window is highlighted for reading.\r\n\r\nchanged:\r\nThe input file has a fixed name called \".VIM_STD_IN\", the orig variable g:VIM_STD_IN_FILE has been deleted.\r\n\r\nOther:\r\nlast version I gave an error email , this is a correct one","package":"shellinsidevim.vim","4":"shellinsidevim.vim","src_id":"9790","5":"9790","creation_date":"1231558711","6":"1231558711"},{"0":"2497","vim_version":"7.2","1":"7.2","script_version":"2.0","2":"2.0","version_comment":"Initial upload","3":"Initial upload","package":"shellinsidevim.vim","4":"shellinsidevim.vim","src_id":"9729","5":"9729","creation_date":"1230512671","6":"1230512671"}]},"2496":{"script_id":"2496","0":"2496","script_name":"Changed","1":"Changed","script_type":"utility","2":"utility","summary":"Displays signs on changed lines.","3":"Displays signs on changed lines.","description":"Description:\r\n  Displays signs on changed lines.\r\nRequirements:\r\n  * +signs (appears in :version)\r\n  * diff command\r\n  * setting &termencoding\r\nUsage:\r\n  [Settings]\r\n                                                                                                         \r\n  1. Setting &termencoding\r\n      Set &termencoding option according to your terminal encoding. \r\n      Its default value is same as &encoding.\r\n      example:\r\n          set termencoding=cp932\r\n                                                                                                         \r\n  2. Changing signs\r\n      To change signs, re-define signs after sourcing this script.\r\n      example (changing text):\r\n          sign define SIGN_CHANGED_DELETED_VIM text=D texthl=ChangedDefaultHl\r\n          sign define SIGN_CHANGED_ADDED_VIM   text=A texthl=ChangedDefaultHl\r\n          sign define SIGN_CHANGED_VIM         text=M texthl=ChangedDefaultHl\r\n      example (changin highlight @gvimrc):\r\n          highlight ChangedDefaultHl cterm=bold ctermbg=red ctermfg=white gui=bold guibg=red guifg=white\r\n                                                                                                         \r\n  [Usual]\r\n                                                                                                         \r\n  Edit a buffer and wait seconds or execute :Changed.\r\n  Then signs appear on changed lines.\r\n","4":"Description:\r\n  Displays signs on changed lines.\r\nRequirements:\r\n  * +signs (appears in :version)\r\n  * diff command\r\n  * setting &termencoding\r\nUsage:\r\n  [Settings]\r\n                                                                                                         \r\n  1. Setting &termencoding\r\n      Set &termencoding option according to your terminal encoding. \r\n      Its default value is same as &encoding.\r\n      example:\r\n          set termencoding=cp932\r\n                                                                                                         \r\n  2. Changing signs\r\n      To change signs, re-define signs after sourcing this script.\r\n      example (changing text):\r\n          sign define SIGN_CHANGED_DELETED_VIM text=D texthl=ChangedDefaultHl\r\n          sign define SIGN_CHANGED_ADDED_VIM   text=A texthl=ChangedDefaultHl\r\n          sign define SIGN_CHANGED_VIM         text=M texthl=ChangedDefaultHl\r\n      example (changin highlight @gvimrc):\r\n          highlight ChangedDefaultHl cterm=bold ctermbg=red ctermfg=white gui=bold guibg=red guifg=white\r\n                                                                                                         \r\n  [Usual]\r\n                                                                                                         \r\n  Edit a buffer and wait seconds or execute :Changed.\r\n  Then signs appear on changed lines.\r\n","install_details":"Just source this file. (Put this file into the plugin directory.)","5":"Just source this file. (Put this file into the plugin directory.)","first_name":"Shuhei","6":"Shuhei","last_name":"Kubota","7":"Kubota","releases":[{"0":"2496","vim_version":"7.0","1":"7.0","script_version":"1.1","2":"1.1","version_comment":"Added support for multi-byte file name.\r\n","3":"Added support for multi-byte file name.\r\n","package":"changed.vim","4":"changed.vim","src_id":"9835","5":"9835","creation_date":"1232180596","6":"1232180596"},{"0":"2496","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"changed.vim","4":"changed.vim","src_id":"9727","5":"9727","creation_date":"1230445511","6":"1230445511"}]},"2495":{"script_id":"2495","0":"2495","script_name":"Pimp","1":"Pimp","script_type":"ftplugin","2":"ftplugin","summary":"Pimp provides a python shell in order to support REPL style development","3":"Pimp provides a python shell in order to support REPL style development","description":"Pimp (Python Chimp) is based on (blatantly copied from) the Chimp plugin\r\n(vimscript #2348).  It provides a very simple REPL mechanism by allowing you to\r\nevaluate the contents of the active vim buffer in a running python console and\r\ninteract with the results.\r\n\r\n=Screenshots=\r\nhttp:\/\/www.flickr.com\/photos\/nushoin\/3121961021\/sizes\/o\/\r\nhttp:\/\/www.flickr.com\/photos\/nushoin\/3121961023\/sizes\/o\/\r\n\r\nTo use the plugin you have to open a terminal (e.g. xterm) and run one of the\r\ntwo scripts provided in the 'bin' directory.  For a split screen configuration\r\nrun ~\/.vim\/bin\/vimPython.bash. For a gvim session interacting with a python\r\ninterpreter running in another window run ~\/.vim\/bin\/gvimPython.bash. Note that\r\nyou have to *execute* the scripts, not source them.\r\n\r\nNow open a python source file or set the filetype to python (:set ft=python).\r\nEnter some python code, then hit <Esc> for normal mode, followed by <Leader>pf.\r\nThe contents of the buffer should now be evaluated in the python console.\r\n\r\n*Note*\r\nThe launching scripts try to run gvim, either in the terminal version (gvim -v,\r\nin the vimPython.bash script) or the gui version (gvimPython.bash). It is\r\npossible to run pimp with the non-gui version of vim by changing vimPython.bash.\r\nHowever in this case evaluating marked text in visual mode will not work.\r\n\r\n=Default bindings=\r\nAssuming that your <Leader> key is '\\':\r\n\\pf Evaluate the current buffer (normal mode)\r\n\\pb Evaluate the marked code (visual mode).\r\n\r\n=Tips=\r\n - To move between the windows in the split screen configuration hit <Ctrl>-a\r\n   <Tab> (<Ctrl>-a is the escape key of gnu screen). \r\n - To resize the window hit <Ctrl>-a followed by :resize N<Enter> where N is the\r\n   number of lines, E.g.  <Ctrl>-a:resize 10<Enter>. \r\n - To scroll back hit <Ctrl>-a<Esc>. That enters screen's copy mode (similar to\r\n   vim's visual mode). To exit that mode hit <Esc>.\r\n - *New* As of Pimp version 0.5, evaluation of code selected in visual mode\r\n   actually works! Try using the right-extended visual block mode (Ctrl-v $) to\r\n   mark indented code (e.g. inside a function) in order to evaluate it. Take\r\n   advantage of the visual block mode to mark the code without the indentation\r\n   of course.\r\n - The code is evaluated in IPython's namespace. That makes it possible to\r\n   access previously defined variables, functions etc. The reverse is true as\r\n   well - it's possible to switch to the IPython window and interact with the\r\n   results of the evaluated code, invoke functions etc.\r\n - IPython has an abundance of 'magic' commands. For example it's possible to\r\n   'cd', 'pwd' etc. from within IPython. Check the IPython documentation for\r\n   details.\r\n\r\nIt is advised to read the gnu screen manual (man screen) for additional\r\ninformation about gnu screen's options and capabilities.\r\n","4":"Pimp (Python Chimp) is based on (blatantly copied from) the Chimp plugin\r\n(vimscript #2348).  It provides a very simple REPL mechanism by allowing you to\r\nevaluate the contents of the active vim buffer in a running python console and\r\ninteract with the results.\r\n\r\n=Screenshots=\r\nhttp:\/\/www.flickr.com\/photos\/nushoin\/3121961021\/sizes\/o\/\r\nhttp:\/\/www.flickr.com\/photos\/nushoin\/3121961023\/sizes\/o\/\r\n\r\nTo use the plugin you have to open a terminal (e.g. xterm) and run one of the\r\ntwo scripts provided in the 'bin' directory.  For a split screen configuration\r\nrun ~\/.vim\/bin\/vimPython.bash. For a gvim session interacting with a python\r\ninterpreter running in another window run ~\/.vim\/bin\/gvimPython.bash. Note that\r\nyou have to *execute* the scripts, not source them.\r\n\r\nNow open a python source file or set the filetype to python (:set ft=python).\r\nEnter some python code, then hit <Esc> for normal mode, followed by <Leader>pf.\r\nThe contents of the buffer should now be evaluated in the python console.\r\n\r\n*Note*\r\nThe launching scripts try to run gvim, either in the terminal version (gvim -v,\r\nin the vimPython.bash script) or the gui version (gvimPython.bash). It is\r\npossible to run pimp with the non-gui version of vim by changing vimPython.bash.\r\nHowever in this case evaluating marked text in visual mode will not work.\r\n\r\n=Default bindings=\r\nAssuming that your <Leader> key is '\\':\r\n\\pf Evaluate the current buffer (normal mode)\r\n\\pb Evaluate the marked code (visual mode).\r\n\r\n=Tips=\r\n - To move between the windows in the split screen configuration hit <Ctrl>-a\r\n   <Tab> (<Ctrl>-a is the escape key of gnu screen). \r\n - To resize the window hit <Ctrl>-a followed by :resize N<Enter> where N is the\r\n   number of lines, E.g.  <Ctrl>-a:resize 10<Enter>. \r\n - To scroll back hit <Ctrl>-a<Esc>. That enters screen's copy mode (similar to\r\n   vim's visual mode). To exit that mode hit <Esc>.\r\n - *New* As of Pimp version 0.5, evaluation of code selected in visual mode\r\n   actually works! Try using the right-extended visual block mode (Ctrl-v $) to\r\n   mark indented code (e.g. inside a function) in order to evaluate it. Take\r\n   advantage of the visual block mode to mark the code without the indentation\r\n   of course.\r\n - The code is evaluated in IPython's namespace. That makes it possible to\r\n   access previously defined variables, functions etc. The reverse is true as\r\n   well - it's possible to switch to the IPython window and interact with the\r\n   results of the evaluated code, invoke functions etc.\r\n - IPython has an abundance of 'magic' commands. For example it's possible to\r\n   'cd', 'pwd' etc. from within IPython. Check the IPython documentation for\r\n   details.\r\n\r\nIt is advised to read the gnu screen manual (man screen) for additional\r\ninformation about gnu screen's options and capabilities.\r\n","install_details":"Pimp depends on IPython (http:\/\/ipython.scipy.org) as the python shell and on\r\ngnu screen (http:\/\/www.gnu.org\/software\/screen) for it's operation. It is also\r\nrecommended to install the full version of vim (the package is named vim-gnome \r\nunder Ubuntu and vim-enhanced in Fedora).\r\n\r\nUnder Debian\/Ubuntu:\r\nsudo apt-get install ipython screen vim-gnome\r\nUnder Fedora:\r\nyum install ipython screen vim-enhanced\r\n\r\n=Installing the plugin=\r\nmkdir ~\/.vim\r\ncd ~\/.vim\r\ntar -xvzf \/path\/to\/Pimp.tar.gz\r\nchmod +x ~\/.vim\/bin\/*.bash\r\n\r\nAdd the following to your ~\/.vimrc file:\r\nfiletype plugin on\r\n\r\n=Keyboard bindings=\r\nYou may override the default keyboard bindings in your .vimrc file. For example\r\nto bind Ctrl-e add the following lines to your .vimrc file:\r\nmap <c-e> <Plug>PimpEvalFile\r\nimap <c-e> <Esc><Plug>PimpEvalFilea\r\nvmap <c-e> <Plug>PimpEvalBlock\r\n\r\n=Problems and solutions=\r\nWhen working in the split screen configuration, vim is run under a gnu screen\r\nsession.  gnu screen itself runs inside a terminal emulator, e.g. konsole. Both\r\ngnu screen and the terminal it is run in can cause various problems. Those\r\nproblems include trapping of keyboard shortcuts, wrong handling of colors\r\n(relevant to users of CSApprox - vimscript #2390) etc. Please refer to the file\r\n~\/.vim\/reference\/pimp\/PimpCaveats.README for details.\r\n\r\n=Testing=\r\nThis plugin has been tested on Ubuntu 8.10 and Fedora 9. If you can test it on\r\nother platforms I'll be happy to hear about any platform related bugs and\r\nsolutions, and will integrate the fix into the next version.\r\n\r\nPlease send me an email if you have any problem installing or using the plugin.\r\nMy email is listed on my profile page.\r\n","5":"Pimp depends on IPython (http:\/\/ipython.scipy.org) as the python shell and on\r\ngnu screen (http:\/\/www.gnu.org\/software\/screen) for it's operation. It is also\r\nrecommended to install the full version of vim (the package is named vim-gnome \r\nunder Ubuntu and vim-enhanced in Fedora).\r\n\r\nUnder Debian\/Ubuntu:\r\nsudo apt-get install ipython screen vim-gnome\r\nUnder Fedora:\r\nyum install ipython screen vim-enhanced\r\n\r\n=Installing the plugin=\r\nmkdir ~\/.vim\r\ncd ~\/.vim\r\ntar -xvzf \/path\/to\/Pimp.tar.gz\r\nchmod +x ~\/.vim\/bin\/*.bash\r\n\r\nAdd the following to your ~\/.vimrc file:\r\nfiletype plugin on\r\n\r\n=Keyboard bindings=\r\nYou may override the default keyboard bindings in your .vimrc file. For example\r\nto bind Ctrl-e add the following lines to your .vimrc file:\r\nmap <c-e> <Plug>PimpEvalFile\r\nimap <c-e> <Esc><Plug>PimpEvalFilea\r\nvmap <c-e> <Plug>PimpEvalBlock\r\n\r\n=Problems and solutions=\r\nWhen working in the split screen configuration, vim is run under a gnu screen\r\nsession.  gnu screen itself runs inside a terminal emulator, e.g. konsole. Both\r\ngnu screen and the terminal it is run in can cause various problems. Those\r\nproblems include trapping of keyboard shortcuts, wrong handling of colors\r\n(relevant to users of CSApprox - vimscript #2390) etc. Please refer to the file\r\n~\/.vim\/reference\/pimp\/PimpCaveats.README for details.\r\n\r\n=Testing=\r\nThis plugin has been tested on Ubuntu 8.10 and Fedora 9. If you can test it on\r\nother platforms I'll be happy to hear about any platform related bugs and\r\nsolutions, and will integrate the fix into the next version.\r\n\r\nPlease send me an email if you have any problem installing or using the plugin.\r\nMy email is listed on my profile page.\r\n","first_name":"Yariv","6":"Yariv","last_name":"Barkan","7":"Barkan","releases":[{"0":"2495","vim_version":"7.0","1":"7.0","script_version":"0.5","2":"0.5","version_comment":"Evaluation of code now works in all visual modes, some bugfixes and enhancements.","3":"Evaluation of code now works in all visual modes, some bugfixes and enhancements.","package":"Pimp-0.5.tar.gz","4":"Pimp-0.5.tar.gz","src_id":"9720","5":"9720","creation_date":"1230073552","6":"1230073552"},{"0":"2495","vim_version":"7.0","1":"7.0","script_version":"0.4","2":"0.4","version_comment":"Initial upload","3":"Initial upload","package":"Pimp.tar.gz","4":"Pimp.tar.gz","src_id":"9714","5":"9714","creation_date":"1229856146","6":"1229856146"}]},"2494":{"script_id":"2494","0":"2494","script_name":"Fruidle","1":"Fruidle","script_type":"color scheme","2":"color scheme","summary":"White background, happy colors, good usability","3":"White background, happy colors, good usability","description":"A light color scheme inspired by the Fruit color scheme and Python's Idle.","4":"A light color scheme inspired by the Fruit color scheme and Python's Idle.","install_details":"Place fruidle.vim in your colors directory at ~\/.vim\/colors (may be different if using a non-linux platform).  Add the following lines to your ~\/.vimrc file to use this colorscheme by default on startup:\r\n\r\n:syntax on\r\n:colorscheme fruidle\r\n\r\n--\r\nScreenshots\r\n\r\nv1.0 and v1.1:\r\nhttp:\/\/img519.imageshack.us\/img519\/8906\/fruidlescreenlf3.png\r\n\r\nv1.2:\r\nhttp:\/\/img132.imageshack.us\/img132\/7686\/fruidlescreenshotvl4.png\r\n\r\n","5":"Place fruidle.vim in your colors directory at ~\/.vim\/colors (may be different if using a non-linux platform).  Add the following lines to your ~\/.vimrc file to use this colorscheme by default on startup:\r\n\r\n:syntax on\r\n:colorscheme fruidle\r\n\r\n--\r\nScreenshots\r\n\r\nv1.0 and v1.1:\r\nhttp:\/\/img519.imageshack.us\/img519\/8906\/fruidlescreenlf3.png\r\n\r\nv1.2:\r\nhttp:\/\/img132.imageshack.us\/img132\/7686\/fruidlescreenshotvl4.png\r\n\r\n","first_name":"Andr\u00c3\u00a9s","6":"Andr\u00c3\u00a9s","last_name":"Su\u00c3\u00a1rez","7":"Su\u00c3\u00a1rez","releases":[{"0":"2494","vim_version":"7.0","1":"7.0","script_version":"1.2","2":"1.2","version_comment":"Changed some colors: it's more similar to Python IDLE.\r\n-- \r\nScreenshot: \r\n\r\nhttp:\/\/img132.imageshack.us\/img132\/7686\/fruidlescreenshotvl4.png","3":"Changed some colors: it's more similar to Python IDLE.\r\n-- \r\nScreenshot: \r\n\r\nhttp:\/\/img132.imageshack.us\/img132\/7686\/fruidlescreenshotvl4.png","package":"fruidle.vim","4":"fruidle.vim","src_id":"9947","5":"9947","creation_date":"1234281541","6":"1234281541"},{"0":"2494","vim_version":"6.0","1":"6.0","script_version":"1.1","2":"1.1","version_comment":"Cleaned up end of line using dos2unix.\r\n\r\nThanks to Terry Michaels.","3":"Cleaned up end of line using dos2unix.\r\n\r\nThanks to Terry Michaels.","package":"fruidle.vim","4":"fruidle.vim","src_id":"9719","5":"9719","creation_date":"1230025979","6":"1230025979"},{"0":"2494","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"fruidle.vim","4":"fruidle.vim","src_id":"9713","5":"9713","creation_date":"1229812162","6":"1229812162"}]},"2493":{"script_id":"2493","0":"2493","script_name":"pty.vim","1":"pty.vim","script_type":"utility","2":"utility","summary":"Remote terminal support for vim thanks to python.  ","3":"Remote terminal support for vim thanks to python.  ","description":"Remote terminal support for vim thanks to python.\r\n\r\n\r\nYou need VIM with python support and urxvt (rxvt-unicode) to use this script.\r\n<http:\/\/software.schmorp.de\/pkg\/rxvt-unicode.html>\r\n\r\nFurthermore this script only provides python functions, so some knowledge about\r\nthis (very fine) language is usefull, but not required to benefit from it.\r\n\r\nCalling the python function rxvtSend('text','cmd') the first time will spawn\r\na subprocesses given by the shell command 'cmd' in a new terminal window and\r\npass 'text' to it. Subsequent calls with the same 'cmd' argument will send further\r\ntext to the this subprocess. If you close the terminal window, the child\r\nprocess stays alive and the next call of 'rxvtSend' opens a new terminal and\r\nconnects to it again. If you want to kill the child, call 'rxvtKill()'. \r\n\r\n","4":"Remote terminal support for vim thanks to python.\r\n\r\n\r\nYou need VIM with python support and urxvt (rxvt-unicode) to use this script.\r\n<http:\/\/software.schmorp.de\/pkg\/rxvt-unicode.html>\r\n\r\nFurthermore this script only provides python functions, so some knowledge about\r\nthis (very fine) language is usefull, but not required to benefit from it.\r\n\r\nCalling the python function rxvtSend('text','cmd') the first time will spawn\r\na subprocesses given by the shell command 'cmd' in a new terminal window and\r\npass 'text' to it. Subsequent calls with the same 'cmd' argument will send further\r\ntext to the this subprocess. If you close the terminal window, the child\r\nprocess stays alive and the next call of 'rxvtSend' opens a new terminal and\r\nconnects to it again. If you want to kill the child, call 'rxvtKill()'. \r\n\r\n","install_details":"It's a vimball archive, you only have to source it.\r\nFor requirements see above.","5":"It's a vimball archive, you only have to source it.\r\nFor requirements see above.","first_name":"Johann","6":"Johann","last_name":"Giwer","7":"Giwer","releases":[{"0":"2493","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"pty.vba","4":"pty.vba","src_id":"9709","5":"9709","creation_date":"1229739664","6":"1229739664"}]},"2492":{"script_id":"2492","0":"2492","script_name":"ViBlip","1":"ViBlip","script_type":"game","2":"game","summary":"ViBlip allows to use Blip! (polish microblogging service)","3":"ViBlip allows to use Blip! (polish microblogging service)","description":"Read and write to Blip! (polish microblogging service) with ViBlip!\r\nHome@GitHub: https:\/\/github.com\/msztolcman\/viblip\r\nAfter installing, run vim, and type:\r\n:Blip some blip status\r\nor:\r\n:Blip >recipient: some message\r\n\r\nto create new status. If you want to read 20 last statuses from your dashboard, just type:\r\n:DBlip\r\nIf you rather want to read your friend statuses:\r\n:DBlip friend_name\r\nYou can specify how many statuses from dashboard want to download. From your dashboard:\r\n:DBlip 5\r\nFrom friend's dashboard:\r\nDBlip friend_name\/5\r\n\r\nTo read private messages:\r\n:PBlip\r\n:PBlip 10\r\nDefault PBlip read 5 last Private Messages, second line will download 10 messages.\r\n\r\nTo read single status:\r\n:MBlip id\r\nWhere id is single status id. You can also specify what type of status want to read:\r\n:MBlip id\/st\r\n:MBlip id\/dm\r\n:MBlip id\/pm\r\n\r\nFirst line read normal statuses, second - directed messages, and third - private messages.\r\n\r\nSometimes you may have some problems with network connection, and connection to Blip is lost - in this case you can now reconnect:\r\n:RBlip","4":"Read and write to Blip! (polish microblogging service) with ViBlip!\r\nHome@GitHub: https:\/\/github.com\/msztolcman\/viblip\r\nAfter installing, run vim, and type:\r\n:Blip some blip status\r\nor:\r\n:Blip >recipient: some message\r\n\r\nto create new status. If you want to read 20 last statuses from your dashboard, just type:\r\n:DBlip\r\nIf you rather want to read your friend statuses:\r\n:DBlip friend_name\r\nYou can specify how many statuses from dashboard want to download. From your dashboard:\r\n:DBlip 5\r\nFrom friend's dashboard:\r\nDBlip friend_name\/5\r\n\r\nTo read private messages:\r\n:PBlip\r\n:PBlip 10\r\nDefault PBlip read 5 last Private Messages, second line will download 10 messages.\r\n\r\nTo read single status:\r\n:MBlip id\r\nWhere id is single status id. You can also specify what type of status want to read:\r\n:MBlip id\/st\r\n:MBlip id\/dm\r\n:MBlip id\/pm\r\n\r\nFirst line read normal statuses, second - directed messages, and third - private messages.\r\n\r\nSometimes you may have some problems with network connection, and connection to Blip is lost - in this case you can now reconnect:\r\n:RBlip","install_details":"Put blip.vim into ~\/.vim\/plugin and create ~\/.vibliprc with content:\r\nblip_login\r\nblip_password","5":"Put blip.vim into ~\/.vim\/plugin and create ~\/.vibliprc with content:\r\nblip_login\r\nblip_password","first_name":"Marcin","6":"Marcin","last_name":"Sztolcman","7":"Sztolcman","releases":[{"0":"2492","vim_version":"7.0","1":"7.0","script_version":"0.4","2":"0.4","version_comment":"- Rewrite some parts of code\r\n- ability to use json module\r\n- new command: RBlip - reconnecting\r\n- new method: read - unified GET\r\n- dashboard - can get specified quant of statuses, from yourself dashboard or from specified user\r\n- message - can read statuses, directed or private messages","3":"- Rewrite some parts of code\r\n- ability to use json module\r\n- new command: RBlip - reconnecting\r\n- new method: read - unified GET\r\n- dashboard - can get specified quant of statuses, from yourself dashboard or from specified user\r\n- message - can read statuses, directed or private messages","package":"blip.vim","4":"blip.vim","src_id":"10573","5":"10573","creation_date":"1241992266","6":"1241992266"},{"0":"2492","vim_version":"7.0","1":"7.0","script_version":"0.2","2":"0.2","version_comment":"Added methods for read private messages, and single status.\r\nSome fixes too.","3":"Added methods for read private messages, and single status.\r\nSome fixes too.","package":"blip.vim","4":"blip.vim","src_id":"9710","5":"9710","creation_date":"1229767398","6":"1229767398"},{"0":"2492","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"blip.vim","4":"blip.vim","src_id":"9706","5":"9706","creation_date":"1229731444","6":"1229731444"}]},"2491":{"script_id":"2491","0":"2491","script_name":"maroloccio3","1":"maroloccio3","script_type":"color scheme","2":"color scheme","summary":"A monochromatic colour scheme for Vim in GUI mode.","3":"A monochromatic colour scheme for Vim in GUI mode.","description":"A monochromatic colour scheme for Vim in GUI mode.","4":"A monochromatic colour scheme for Vim in GUI mode.","install_details":"Copy to colour scheme directory.\r\n","5":"Copy to colour scheme directory.\r\n","first_name":"Marco","6":"Marco","last_name":"Ippolito","7":"Ippolito","releases":[{"0":"2491","vim_version":"7.0","1":"7.0","script_version":"0.1.0","2":"0.1.0","version_comment":"Initial upload to vim.org","3":"Initial upload to vim.org","package":"maroloccio3-v0.1.0.png","4":"maroloccio3-v0.1.0.png","src_id":"9704","5":"9704","creation_date":"1229699516","6":"1229699516"},{"0":"2491","vim_version":"7.0","1":"7.0","script_version":"0.1.0","2":"0.1.0","version_comment":"Initial upload","3":"Initial upload","package":"maroloccio3.vim","4":"maroloccio3.vim","src_id":"9703","5":"9703","creation_date":"1229699248","6":"1229699248"}]},"2490":{"script_id":"2490","0":"2490","script_name":"eclm_wombat.vim","1":"eclm_wombat.vim","script_type":"color scheme","2":"color scheme","summary":"Colour scheme based on ECLM and wombat schemes","3":"Colour scheme based on ECLM and wombat schemes","description":"This is based largely on the gorgeous ECLM textmate theme from eclips3.media and I used the wombat scheme file as a starting point. \r\n\r\nPreview:\r\nhttp:\/\/img78.imageshack.us\/img78\/279\/eclmwombatre3.png\r\n\r\nEnjoy!","4":"This is based largely on the gorgeous ECLM textmate theme from eclips3.media and I used the wombat scheme file as a starting point. \r\n\r\nPreview:\r\nhttp:\/\/img78.imageshack.us\/img78\/279\/eclmwombatre3.png\r\n\r\nEnjoy!","install_details":"Put eclm_wombat.vim into ~\/.vim\/colors\/ \r\n\r\nPut colorscheme eclm_wombat into .gvimrc or .vimrc.","5":"Put eclm_wombat.vim into ~\/.vim\/colors\/ \r\n\r\nPut colorscheme eclm_wombat into .gvimrc or .vimrc.","first_name":"some","6":"some","last_name":"one","7":"one","releases":[{"0":"2490","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"eclm_wombat.vim","4":"eclm_wombat.vim","src_id":"9702","5":"9702","creation_date":"1229683086","6":"1229683086"}]},"2489":{"script_id":"2489","0":"2489","script_name":"maroloccio2","1":"maroloccio2","script_type":"color scheme","2":"color scheme","summary":"Works only in GUI mode (gVim, mVim, etc.).","3":"Works only in GUI mode (gVim, mVim, etc.).","description":"A dark background, very easy-on-the-eyes colour scheme for Vim. GUI mode only. ","4":"A dark background, very easy-on-the-eyes colour scheme for Vim. GUI mode only. ","install_details":"Copy to colour scheme directory.","5":"Copy to colour scheme directory.","first_name":"Marco","6":"Marco","last_name":"Ippolito","7":"Ippolito","releases":[{"0":"2489","vim_version":"7.0","1":"7.0","script_version":"0.1.0","2":"0.1.0","version_comment":"Screenshot v0.1.0","3":"Screenshot v0.1.0","package":"maroloccio2-0.1.0.png","4":"maroloccio2-0.1.0.png","src_id":"9699","5":"9699","creation_date":"1229644237","6":"1229644237"},{"0":"2489","vim_version":"7.0","1":"7.0","script_version":"0.1.0","2":"0.1.0","version_comment":"Initial upload","3":"Initial upload","package":"maroloccio2.vim","4":"maroloccio2.vim","src_id":"9698","5":"9698","creation_date":"1229644098","6":"1229644098"}]},"2488":{"script_id":"2488","0":"2488","script_name":"Rack::Builder syntax","1":"Rack::Builder syntax","script_type":"syntax","2":"syntax","summary":"Syntax file for the Rack::Builder DSL","3":"Syntax file for the Rack::Builder DSL","description":"This provides syntax highlighting for the most basic Rack keywords.\r\n\r\nhttp:\/\/github.com\/dasch\/vim-rack","4":"This provides syntax highlighting for the most basic Rack keywords.\r\n\r\nhttp:\/\/github.com\/dasch\/vim-rack","install_details":"Unpack in ~\/.vim\/","5":"Unpack in ~\/.vim\/","first_name":"Daniel","6":"Daniel","last_name":"Schierbeck","7":"Schierbeck","releases":[{"0":"2488","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"rack.zip","4":"rack.zip","src_id":"9697","5":"9697","creation_date":"1229626999","6":"1229626999"}]},"2487":{"script_id":"2487","0":"2487","script_name":"fortran_codecomplete.vim","1":"fortran_codecomplete.vim","script_type":"ftplugin","2":"ftplugin","summary":"Complete fortran constructs with <F7>","3":"Complete fortran constructs with <F7>","description":"This script allows you to complete Fortran 90 structures by pressing <F7>.\r\n\r\nThe plugin in written in python, so you need to have your vim compiled with python support in order to use it.\r\n\r\nThe intention is to complete \u00e2\u0080\u009cprogram\u00e2\u0080\u009d, \u00e2\u0080\u009ctype\u00e2\u0080\u009d, \u00e2\u0080\u009cinterface\u00e2\u0080\u009d, \u00e2\u0080\u009cmodule\u00e2\u0080\u009d, \u00e2\u0080\u009csubroutine\u00e2\u0080\u009d, \u00e2\u0080\u009cfunction\u00e2\u0080\u009d, \u00e2\u0080\u009cdo\u00e2\u0080\u009d, and \u00e2\u0080\u009cselect\u00e2\u0080\u009d constructs. You write the first line of such a construct (e.g. \u00e2\u0080\u009csubroutine foo(a, b)\u00e2\u0080\u009d, then press <F7>, and the script will add the closing line \u00e2\u0080\u009cend subroutine foo\u00e2\u0080\u009d and put the cursor between the two lines, indented by one level.","4":"This script allows you to complete Fortran 90 structures by pressing <F7>.\r\n\r\nThe plugin in written in python, so you need to have your vim compiled with python support in order to use it.\r\n\r\nThe intention is to complete \u00e2\u0080\u009cprogram\u00e2\u0080\u009d, \u00e2\u0080\u009ctype\u00e2\u0080\u009d, \u00e2\u0080\u009cinterface\u00e2\u0080\u009d, \u00e2\u0080\u009cmodule\u00e2\u0080\u009d, \u00e2\u0080\u009csubroutine\u00e2\u0080\u009d, \u00e2\u0080\u009cfunction\u00e2\u0080\u009d, \u00e2\u0080\u009cdo\u00e2\u0080\u009d, and \u00e2\u0080\u009cselect\u00e2\u0080\u009d constructs. You write the first line of such a construct (e.g. \u00e2\u0080\u009csubroutine foo(a, b)\u00e2\u0080\u009d, then press <F7>, and the script will add the closing line \u00e2\u0080\u009cend subroutine foo\u00e2\u0080\u009d and put the cursor between the two lines, indented by one level.","install_details":"Put the file in ~\/.vim\/ftplugin","5":"Put the file in ~\/.vim\/ftplugin","first_name":"Michael","6":"Michael","last_name":"Goerz","7":"Goerz","releases":[{"0":"2487","vim_version":"7.0","1":"7.0","script_version":"0.9","2":"0.9","version_comment":"Initial upload","3":"Initial upload","package":"fortran_codecomplete.vim","4":"fortran_codecomplete.vim","src_id":"9688","5":"9688","creation_date":"1229553311","6":"1229553311"}]},"2486":{"script_id":"2486","0":"2486","script_name":"proc.vim","1":"proc.vim","script_type":"utility","2":"utility","summary":"a system task manager ","3":"a system task manager ","description":"This is a fronted for the *nix commands 'ps' and 'kill' and  a more comfortable replacement for 'top'.\r\n\r\nBy calling Ps() you get a view of the current system processes in a new buffer. \r\n\r\nKeybindings exist for sorting, marking and killing.\r\n","4":"This is a fronted for the *nix commands 'ps' and 'kill' and  a more comfortable replacement for 'top'.\r\n\r\nBy calling Ps() you get a view of the current system processes in a new buffer. \r\n\r\nKeybindings exist for sorting, marking and killing.\r\n","install_details":"Its a vimball archive.\r\nLoad it into vim and source it.\r\n\r\nThis script should run on every *nix like system that provides the commands 'ps' and 'kill', but is only tested on linux.","5":"Its a vimball archive.\r\nLoad it into vim and source it.\r\n\r\nThis script should run on every *nix like system that provides the commands 'ps' and 'kill', but is only tested on linux.","first_name":"Johann","6":"Johann","last_name":"Giwer","7":"Giwer","releases":[{"0":"2486","vim_version":"6.0","1":"6.0","script_version":"0.1.1","2":"0.1.1","version_comment":"fixed some typos","3":"fixed some typos","package":"proc.vba","4":"proc.vba","src_id":"9683","5":"9683","creation_date":"1229471396","6":"1229471396"},{"0":"2486","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"proc.vba","4":"proc.vba","src_id":"9682","5":"9682","creation_date":"1229451129","6":"1229451129"}]},"2485":{"script_id":"2485","0":"2485","script_name":"python_check_syntax.vim","1":"python_check_syntax.vim","script_type":"ftplugin","2":"ftplugin","summary":"a script that check the syntax of a python file by pyflakes","3":"a script that check the syntax of a python file by pyflakes","description":"You can check the syntax of a python file if you install pyflakes module in you system. It call pyflakes function to check the current python file and display error messages in quickfix window in vim. You can browse the error by usual quickfix command like 'cc' ,'cn' etc.\r\n\r\nThere are two global variant which you maybe want to define in your .vimrc\r\n\r\ng:pcs_hotkey      # run the checker, the default is  <localleader>cs\r\ng:pcs_check_when_saving   # when true, the checker automaticlly run while saving, the default is true\r\n\r\nWARNING: \r\n\r\n1. Vim compiled with +python\r\n2. Must install pyflakes in your system. The note is that the old version(<=0.2.1) is too old to identify the new syntax of python2.5, 2.6, so svn version is recomend.","4":"You can check the syntax of a python file if you install pyflakes module in you system. It call pyflakes function to check the current python file and display error messages in quickfix window in vim. You can browse the error by usual quickfix command like 'cc' ,'cn' etc.\r\n\r\nThere are two global variant which you maybe want to define in your .vimrc\r\n\r\ng:pcs_hotkey      # run the checker, the default is  <localleader>cs\r\ng:pcs_check_when_saving   # when true, the checker automaticlly run while saving, the default is true\r\n\r\nWARNING: \r\n\r\n1. Vim compiled with +python\r\n2. Must install pyflakes in your system. The note is that the old version(<=0.2.1) is too old to identify the new syntax of python2.5, 2.6, so svn version is recomend.","install_details":"copy the python_check_syntax.vim into ~\/.vim\/ftplugin","5":"copy the python_check_syntax.vim into ~\/.vim\/ftplugin","first_name":"tocer","6":"tocer","last_name":"deng","7":"deng","releases":[{"0":"2485","vim_version":"6.0","1":"6.0","script_version":"0.6.4","2":"0.6.4","version_comment":"bug fixed. Thanks for Marius Gedminas","3":"bug fixed. Thanks for Marius Gedminas","package":"python_check_syntax.vim","4":"python_check_syntax.vim","src_id":"10370","5":"10370","creation_date":"1239270247","6":"1239270247"},{"0":"2485","vim_version":"6.0","1":"6.0","script_version":"0.6","2":"0.6","version_comment":"Initial upload","3":"Initial upload","package":"python_check_syntax.vim","4":"python_check_syntax.vim","src_id":"9677","5":"9677","creation_date":"1229328667","6":"1229328667"}]},"2484":{"script_id":"2484","0":"2484","script_name":"textobj-indent","1":"textobj-indent","script_type":"utility","2":"utility","summary":"Text objects for indented blocks of lines","3":"Text objects for indented blocks of lines","description":"*textobj-indent* is a Vim plugin to provide text objects to select a block of\r\nlines which are similarly indented to the current line.\r\n\r\nFor example, if the content of a buffer as follows:\r\n(here \">\" means the current line under the cursor,\r\nand \"_\" means a space to indent)\r\n\r\n\t  if some_condition_is_satisfied\r\n\t> __if another_condition_is_satisfied\r\n\t  ____call s:do_x()\r\n\t  __endif\r\n\r\n\t  __...\r\n\t  __endif\r\n\t  else\r\n\t  __...\r\n\t  endif\r\n\r\n|<Plug>(textobj-indent-a)| will select lines as follows:\r\n(here \"|\" indicates the selected line)\r\n\r\n\t  if some_condition_is_satisfied\r\n\t>|__if another_condition_is_satisfied\r\n\t |____call s:do_x()\r\n\t |__endif\r\n\t |\r\n\t |__...\r\n\t |__endif\r\n\t  else\r\n\t  __...\r\n\t  endif\r\n\r\n|<Plug>(textobj-indent-i)| will select lines as follows:\r\n\r\n\t  if some_condition_is_satisfied\r\n\t>|__if another_condition_is_satisfied\r\n\t |____call s:do_x()\r\n\t |__endif\r\n\r\n\t  __...\r\n\t  __endif\r\n\t  else\r\n\t  __...\r\n\t  endif\r\n\r\nMore variants are also available.  See |textobj-indnet-mapping| for the\r\ndetails.\r\n\r\n\r\nRequirements:\r\n- Vim 7.2 or later\r\n- |textobj-user| 0.3.8 or later (vimscript#2100)\r\n\r\nLatest version:\r\nhttp:\/\/github.com\/kana\/vim-textobj-indent\r\n\r\nDocument in HTML format:\r\nhttp:\/\/kana.github.com\/config\/vim\/textobj-indent.html","4":"*textobj-indent* is a Vim plugin to provide text objects to select a block of\r\nlines which are similarly indented to the current line.\r\n\r\nFor example, if the content of a buffer as follows:\r\n(here \">\" means the current line under the cursor,\r\nand \"_\" means a space to indent)\r\n\r\n\t  if some_condition_is_satisfied\r\n\t> __if another_condition_is_satisfied\r\n\t  ____call s:do_x()\r\n\t  __endif\r\n\r\n\t  __...\r\n\t  __endif\r\n\t  else\r\n\t  __...\r\n\t  endif\r\n\r\n|<Plug>(textobj-indent-a)| will select lines as follows:\r\n(here \"|\" indicates the selected line)\r\n\r\n\t  if some_condition_is_satisfied\r\n\t>|__if another_condition_is_satisfied\r\n\t |____call s:do_x()\r\n\t |__endif\r\n\t |\r\n\t |__...\r\n\t |__endif\r\n\t  else\r\n\t  __...\r\n\t  endif\r\n\r\n|<Plug>(textobj-indent-i)| will select lines as follows:\r\n\r\n\t  if some_condition_is_satisfied\r\n\t>|__if another_condition_is_satisfied\r\n\t |____call s:do_x()\r\n\t |__endif\r\n\r\n\t  __...\r\n\t  __endif\r\n\t  else\r\n\t  __...\r\n\t  endif\r\n\r\nMore variants are also available.  See |textobj-indnet-mapping| for the\r\ndetails.\r\n\r\n\r\nRequirements:\r\n- Vim 7.2 or later\r\n- |textobj-user| 0.3.8 or later (vimscript#2100)\r\n\r\nLatest version:\r\nhttp:\/\/github.com\/kana\/vim-textobj-indent\r\n\r\nDocument in HTML format:\r\nhttp:\/\/kana.github.com\/config\/vim\/textobj-indent.html","install_details":"...","5":"...","first_name":"Kana","6":"Kana","last_name":"Natsuno","7":"Natsuno","releases":[{"0":"2484","vim_version":"7.0","1":"7.0","script_version":"0.0.3","2":"0.0.3","version_comment":"Incompatible changes:\n- Requrie |textobj-user| 0.3.8 or later.\n\nMajor improvements:\n- Add |<Plug>(textobj-indent-same-a)| and |<Plug>(textobj-indent-same-i)|.\n\nMinor improvements:\n- Revise the document a bit.\n- Add tests.\n- Fix a minor bug.\n- Revise to be autoloaded.","3":"Incompatible changes:\n- Requrie |textobj-user| 0.3.8 or later.\n\nMajor improvements:\n- Add |<Plug>(textobj-indent-same-a)| and |<Plug>(textobj-indent-same-i)|.\n\nMinor improvements:\n- Revise the document a bit.\n- Add tests.\n- Fix a minor bug.\n- Revise to be autoloaded.","package":"vim-textobj-indent-0.0.3.zip","4":"vim-textobj-indent-0.0.3.zip","src_id":"11291","5":"11291","creation_date":"1251635037","6":"1251635037"},{"0":"2484","vim_version":"7.0","1":"7.0","script_version":"0.0.2","2":"0.0.2","version_comment":"- Fix the bug to calculate indentation levels.  Now these text objects target a set of lines with the same indentation as you see.","3":"- Fix the bug to calculate indentation levels.  Now these text objects target a set of lines with the same indentation as you see.","package":"vim-textobj-indent-0.0.2.zip","4":"vim-textobj-indent-0.0.2.zip","src_id":"10410","5":"10410","creation_date":"1239967269","6":"1239967269"},{"0":"2484","vim_version":"7.0","1":"7.0","script_version":"0.0.1","2":"0.0.1","version_comment":"- Add |<Plug>(textobj-indent-a)| and |<Plug>(textobj-indent-i)|.\n- Remove |<Plug>(textobj-indent)|.  Use |<Plug>(textobj-indent-a)| instead.","3":"- Add |<Plug>(textobj-indent-a)| and |<Plug>(textobj-indent-i)|.\n- Remove |<Plug>(textobj-indent)|.  Use |<Plug>(textobj-indent-a)| instead.","package":"vim-textobj-indent-0.0.1.zip","4":"vim-textobj-indent-0.0.1.zip","src_id":"10049","5":"10049","creation_date":"1235710744","6":"1235710744"},{"0":"2484","vim_version":"7.0","1":"7.0","script_version":"0.0.0","2":"0.0.0","version_comment":"Initial upload","3":"Initial upload","package":"vim-textobj-indent-0.0.0.zip","4":"vim-textobj-indent-0.0.0.zip","src_id":"9659","5":"9659","creation_date":"1229184166","6":"1229184166"}]},"2483":{"script_id":"2483","0":"2483","script_name":"Gorilla","1":"Gorilla","script_type":"ftplugin","2":"ftplugin","summary":"a SLIME like environment for the Clojure programming language","3":"a SLIME like environment for the Clojure programming language","description":"Gorilla is now merged with VimClojure (vimscript #2501).","4":"Gorilla is now merged with VimClojure (vimscript #2501).","install_details":"","5":"","first_name":"Meikel","6":"Meikel","last_name":"Brandmeyer","7":"Brandmeyer","releases":[{"0":"2483","vim_version":"7.0","1":"7.0","script_version":"1.1.1","2":"1.1.1","version_comment":"This is a compatibility release for Clojure >= SVN rev1192 and Clojure Contrib >= SVN rev331.\r\nIf you are using earlier revisions of Clojure and Contrib, eg. the December Release of Clojure\r\nyou don't need this release.","3":"This is a compatibility release for Clojure >= SVN rev1192 and Clojure Contrib >= SVN rev331.\r\nIf you are using earlier revisions of Clojure and Contrib, eg. the December Release of Clojure\r\nyou don't need this release.","package":"gorilla-1.1.1.tar.gz","4":"gorilla-1.1.1.tar.gz","src_id":"9734","5":"9734","creation_date":"1230719992","6":"1230719992"}]},"2482":{"script_id":"2482","0":"2482","script_name":"Quagmire","1":"Quagmire","script_type":"color scheme","2":"color scheme","summary":"Army style color scheme","3":"Army style color scheme","description":"This is as close a port as I could manage of the camouflage-inspired (and inexplicably named) Glitterbomb theme for TextMate. Due to some fundamental differences in the way the two editors handle syntax highlighting, it's more or less impossible to make it a perfect match, but it's close enough to look fairly nice in most circumstances.\r\n\r\nBy the way, the original can be found on the TextMate wiki: http:\/\/wiki.macromates.com\/Themes\/UserSubmittedThemes\r\n\r\n","4":"This is as close a port as I could manage of the camouflage-inspired (and inexplicably named) Glitterbomb theme for TextMate. Due to some fundamental differences in the way the two editors handle syntax highlighting, it's more or less impossible to make it a perfect match, but it's close enough to look fairly nice in most circumstances.\r\n\r\nBy the way, the original can be found on the TextMate wiki: http:\/\/wiki.macromates.com\/Themes\/UserSubmittedThemes\r\n\r\n","install_details":"Put it wherever. You know what you doing.","5":"Put it wherever. You know what you doing.","first_name":"Streak","6":"Streak","last_name":"Porchfleece","7":"Porchfleece","releases":[{"0":"2482","vim_version":"7.0","1":"7.0","script_version":"0.3","2":"0.3","version_comment":"Initial upload","3":"Initial upload","package":"quagmire.vim","4":"quagmire.vim","src_id":"9654","5":"9654","creation_date":"1229100156","6":"1229100156"}]},"2481":{"script_id":"2481","0":"2481","script_name":"pygtk_syntax","1":"pygtk_syntax","script_type":"syntax","2":"syntax","summary":"Syntax Highlighting for pygtk and friends in python","3":"Syntax Highlighting for pygtk and friends in python","description":"This script adds python syntax highlighting for:\r\n gtk gtk.gdk gtk.glade gobject rsvg atk cairo pango gnome\r\n\r\nAll highlighted items will only show up after a \".\" character. (e.g. threads_init() will not be highlighted but gtk.gdk.threads_init() will be)\r\n\r\ngtk functions and gtk objects can be set to have different highlight values by adding \r\nIncludedFunction\r\nIncludedFunction2\r\nhighlight groups in your colorscheme file.\r\n","4":"This script adds python syntax highlighting for:\r\n gtk gtk.gdk gtk.glade gobject rsvg atk cairo pango gnome\r\n\r\nAll highlighted items will only show up after a \".\" character. (e.g. threads_init() will not be highlighted but gtk.gdk.threads_init() will be)\r\n\r\ngtk functions and gtk objects can be set to have different highlight values by adding \r\nIncludedFunction\r\nIncludedFunction2\r\nhighlight groups in your colorscheme file.\r\n","install_details":"Extract to ~\/.vim\/after\/syntax\/","5":"Extract to ~\/.vim\/after\/syntax\/","first_name":"Jason","6":"Jason","last_name":"Siefken","7":"Siefken","releases":[{"0":"2481","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"pygtk_syntax.tar.bz2","4":"pygtk_syntax.tar.bz2","src_id":"9653","5":"9653","creation_date":"1229074260","6":"1229074260"}]},"2480":{"script_id":"2480","0":"2480","script_name":"maroloccio","1":"maroloccio","script_type":"color scheme","2":"color scheme","summary":"An easy-on-the-eyes dark background colour scheme. ","3":"An easy-on-the-eyes dark background colour scheme. ","description":"An easy-on-the-eyes dark background colour scheme.\r\n\r\nNow with 256 colours support!\r\n\r\nScreenshots:\r\n\r\nGUI mode: http:\/\/picasaweb.google.com\/lh\/photo\/InGod978VFzY144k3-ZrxA\r\ncterm (256 colours): http:\/\/picasaweb.google.com\/lh\/photo\/E5Nb1dltZxIoCtrFZ-OlnA\r\ncterm (8 colours): http:\/\/picasaweb.google.com\/lh\/photo\/j_VMoZ20KLJaTq2YYeAdfg\r\n\r\nDownload from:\r\n\r\nVim.org: http:\/\/www.vim.org\/scripts\/script.php?script_id=2480\r\nEasy-to-remember URL: http:\/\/bit.ly\/maroloccio_vim\r\n\r\nPlease send feeback to the author! maroloccio[at]gmail.com\r\n\r\n--\r\nPS: Eclipse user? Check out this as well:\r\n\r\nEclipse colour scheme: http:\/\/docs.google.com\/View?id=dd6g79bh_15f2jhs9f8\r\nScreenshot: http:\/\/picasaweb.google.com\/lh\/photo\/o7mWcx9G8TMXoU80S--_uw","4":"An easy-on-the-eyes dark background colour scheme.\r\n\r\nNow with 256 colours support!\r\n\r\nScreenshots:\r\n\r\nGUI mode: http:\/\/picasaweb.google.com\/lh\/photo\/InGod978VFzY144k3-ZrxA\r\ncterm (256 colours): http:\/\/picasaweb.google.com\/lh\/photo\/E5Nb1dltZxIoCtrFZ-OlnA\r\ncterm (8 colours): http:\/\/picasaweb.google.com\/lh\/photo\/j_VMoZ20KLJaTq2YYeAdfg\r\n\r\nDownload from:\r\n\r\nVim.org: http:\/\/www.vim.org\/scripts\/script.php?script_id=2480\r\nEasy-to-remember URL: http:\/\/bit.ly\/maroloccio_vim\r\n\r\nPlease send feeback to the author! maroloccio[at]gmail.com\r\n\r\n--\r\nPS: Eclipse user? Check out this as well:\r\n\r\nEclipse colour scheme: http:\/\/docs.google.com\/View?id=dd6g79bh_15f2jhs9f8\r\nScreenshot: http:\/\/picasaweb.google.com\/lh\/photo\/o7mWcx9G8TMXoU80S--_uw","install_details":"Copy to colour scheme directory.","5":"Copy to colour scheme directory.","first_name":"Marco","6":"Marco","last_name":"Ippolito","7":"Ippolito","releases":[{"0":"2480","vim_version":"7.0","1":"7.0","script_version":"0.3.2","2":"0.3.2","version_comment":"Published to GitHub: https:\/\/github.com\/Maroloccio\/maroloccio-vim","3":"Published to GitHub: https:\/\/github.com\/Maroloccio\/maroloccio-vim","package":"maroloccio.vim","4":"maroloccio.vim","src_id":"20074","5":"20074","creation_date":"1368044534","6":"1368044534"},{"0":"2480","vim_version":"7.0","1":"7.0","script_version":"0.3.1","2":"0.3.1","version_comment":"Updated licensing and author's contact details to receive feedback.","3":"Updated licensing and author's contact details to receive feedback.","package":"maroloccio.vim","4":"maroloccio.vim","src_id":"12609","5":"12609","creation_date":"1268359113","6":"1268359113"},{"0":"2480","vim_version":"7.0","1":"7.0","script_version":"0.3.0","2":"0.3.0","version_comment":"Try it! Updated 256 colours terminal support!","3":"Try it! Updated 256 colours terminal support!","package":"maroloccio.vim","4":"maroloccio.vim","src_id":"10543","5":"10543","creation_date":"1241587986","6":"1241587986"},{"0":"2480","vim_version":"7.0","1":"7.0","script_version":"0.2.9","2":"0.2.9","version_comment":"Improved readability of cterm searches for dark backgrounds .","3":"Improved readability of cterm searches for dark backgrounds .","package":"maroloccio.vim","4":"maroloccio.vim","src_id":"10334","5":"10334","creation_date":"1238637225","6":"1238637225"},{"0":"2480","vim_version":"7.0","1":"7.0","script_version":"0.2.8","2":"0.2.8","version_comment":"Added VimDiff colouring","3":"Added VimDiff colouring","package":"maroloccio.vim","4":"maroloccio.vim","src_id":"10231","5":"10231","creation_date":"1237278147","6":"1237278147"}]},"2479":{"script_id":"2479","0":"2479","script_name":"grsecurity.vim","1":"grsecurity.vim","script_type":"syntax","2":"syntax","summary":"grsecurity policy syntax definition","3":"grsecurity policy syntax definition","description":"This is a syntax definition for grsecurity policy files. Basic syntax highlighting of the policy file and folding works at the moment.\r\n\r\nGIT Repository: https:\/\/github.com\/verbosemode\/grsecurity.vim\r\ngit clone git:\/\/github.com\/verbosemode\/grsecurity.vim.git\r\n\r\nScreenshot: http:\/\/picasaweb.google.com\/lh\/photo\/Le_YL0dQt59AlPluaVUwNw\r\nPolicy language documentation: http:\/\/en.wikibooks.org\/wiki\/Grsecurity\r\nThere is also a ftplugin: vimscript #3027","4":"This is a syntax definition for grsecurity policy files. Basic syntax highlighting of the policy file and folding works at the moment.\r\n\r\nGIT Repository: https:\/\/github.com\/verbosemode\/grsecurity.vim\r\ngit clone git:\/\/github.com\/verbosemode\/grsecurity.vim.git\r\n\r\nScreenshot: http:\/\/picasaweb.google.com\/lh\/photo\/Le_YL0dQt59AlPluaVUwNw\r\nPolicy language documentation: http:\/\/en.wikibooks.org\/wiki\/Grsecurity\r\nThere is also a ftplugin: vimscript #3027","install_details":"Place grsecurity.vim file in ~\/.vim\/syntax\/ folder.\r\n\r\nset filetype=grsecurity","5":"Place grsecurity.vim file in ~\/.vim\/syntax\/ folder.\r\n\r\nset filetype=grsecurity","first_name":"Bernd","6":"Bernd","last_name":"Brot","7":"Brot","releases":[{"0":"2479","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"grsecurity.vim","4":"grsecurity.vim","src_id":"9645","5":"9645","creation_date":"1228940471","6":"1228940471"}]},"2478":{"script_id":"2478","0":"2478","script_name":"ActionScript 3 Omnicomplete","1":"ActionScript 3 Omnicomplete","script_type":"ftplugin","2":"ftplugin","summary":"Omnicompletion plug-in for ActionScript 3","3":"Omnicompletion plug-in for ActionScript 3","description":"This plug-in will enable omnicompletion for ActionScript 3 files.\r\n\r\nIt covers the majority of classes in the \\'flash\\' package but still lacks those found in \\'mx\\', \\'air\\', and \\'flashx\\'.\r\n\r\nObviously, a work in progress.","4":"This plug-in will enable omnicompletion for ActionScript 3 files.\r\n\r\nIt covers the majority of classes in the \\'flash\\' package but still lacks those found in \\'mx\\', \\'air\\', and \\'flashx\\'.\r\n\r\nObviously, a work in progress.","install_details":"Copy \\'actionscriptcomplete.vim\\' to the \\'autoload\\' directory and \\'actionscript.vim\\' to \\'ftplugin\\'. ","5":"Copy \\'actionscriptcomplete.vim\\' to the \\'autoload\\' directory and \\'actionscript.vim\\' to \\'ftplugin\\'. ","first_name":"Phil","6":"Phil","last_name":"Peron","7":"Peron","releases":[{"0":"2478","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"as3_omnicomplete.zip","4":"as3_omnicomplete.zip","src_id":"9644","5":"9644","creation_date":"1228922849","6":"1228922849"}]},"2477":{"script_id":"2477","0":"2477","script_name":"Persistent Abbreviations","1":"Persistent Abbreviations","script_type":"utility","2":"utility","summary":"Persistent abbreviations","3":"Persistent abbreviations","description":"This was designed for Medical Transcription work. \r\n\r\nAbbreviations can be added dynamically as you go, and will persist. They are also case smart:\r\nIf you add an abbreviation such as   \r\n\twrt=with respect to\r\nthen a corresponding abbreviation \r\n\tWrt=With respect to\r\nis also created.","4":"This was designed for Medical Transcription work. \r\n\r\nAbbreviations can be added dynamically as you go, and will persist. They are also case smart:\r\nIf you add an abbreviation such as   \r\n\twrt=with respect to\r\nthen a corresponding abbreviation \r\n\tWrt=With respect to\r\nis also created.","install_details":"Add as a plugin in the plugin directory.  ~\/.vim\/plugin","5":"Add as a plugin in the plugin directory.  ~\/.vim\/plugin","first_name":"Michael","6":"Michael","last_name":"Geddes","7":"Geddes","releases":[{"0":"2477","vim_version":"6.0","1":"6.0","script_version":"0.1.1","2":"0.1.1","version_comment":"Comments only","3":"Comments only","package":"abbrevlist.vim","4":"abbrevlist.vim","src_id":"9642","5":"9642","creation_date":"1228874063","6":"1228874063"}]},"2476":{"script_id":"2476","0":"2476","script_name":"cbackup.vim","1":"cbackup.vim","script_type":"utility","2":"utility","summary":"Use VMS style versioned backup with centralized backup directory","3":"Use VMS style versioned backup with centralized backup directory","description":"This is a modification of vimscript #1537 to make it work with centralized backup directories. Backups are saved by default in $HOME\/.backups, with recursive subdirectories reflecting the original location of the file being saved, using the VMS versioning system.\r\n\r\nParts of the script running under VMS were not changed. Script was tested on Linux, and should work in other environments too (Windows, Mac).","4":"This is a modification of vimscript #1537 to make it work with centralized backup directories. Backups are saved by default in $HOME\/.backups, with recursive subdirectories reflecting the original location of the file being saved, using the VMS versioning system.\r\n\r\nParts of the script running under VMS were not changed. Script was tested on Linux, and should work in other environments too (Windows, Mac).","install_details":"Download the script and put it in your ~\/.vim\/plugin\/ directory.\r\n\r\nConfiguration:\r\n\r\ng:backup_directory - the root of the backup directory structure, by default it's set to \"$HOME\/.backups\". It will be automatically created if not found.\r\n\r\ng:backup_purge - number of files to preserve during write, by default 10. Older files will be automatically removed.\r\n","5":"Download the script and put it in your ~\/.vim\/plugin\/ directory.\r\n\r\nConfiguration:\r\n\r\ng:backup_directory - the root of the backup directory structure, by default it's set to \"$HOME\/.backups\". It will be automatically created if not found.\r\n\r\ng:backup_purge - number of files to preserve during write, by default 10. Older files will be automatically removed.\r\n","first_name":"Maciej","6":"Maciej","last_name":"Delmanowski","7":"Delmanowski","releases":[{"0":"2476","vim_version":"7.0","1":"7.0","script_version":"2.2.1","2":"2.2.1","version_comment":"Initial upload","3":"Initial upload","package":"cbackup.vim","4":"cbackup.vim","src_id":"9634","5":"9634","creation_date":"1228775873","6":"1228775873"}]},"2475":{"script_id":"2475","0":"2475","script_name":"ini syntax definition","1":"ini syntax definition","script_type":"syntax","2":"syntax","summary":"A syntax definition for ini files, including hgrc files.","3":"A syntax definition for ini files, including hgrc files.","description":"This is a syntax definition for configuration files in the ini format, common on Windows and for software written in Python. This includes the popular version-control system Mercurial, whose hgrc configuration files are ini files.\r\n\r\nMercurial repository for this syntax definition: http:\/\/bitbucket.org\/boredzo\/vim-ini-syntax\/\r\n\r\n","4":"This is a syntax definition for configuration files in the ini format, common on Windows and for software written in Python. This includes the popular version-control system Mercurial, whose hgrc configuration files are ini files.\r\n\r\nMercurial repository for this syntax definition: http:\/\/bitbucket.org\/boredzo\/vim-ini-syntax\/\r\n\r\n","install_details":"First, copy this file to ~\/.vim\/syntax\/ini.vim. (You will need to create that directory, if you haven't already.)\r\n\r\nThen, to make vim automatically use that syntax definition for .ini and hgrc files, you'll need to add this to your ~\/.vim\/filetype.vim file (which you will need to create, if you haven't already):\r\n\r\nau BufNewFile,BufRead *.ini,*\/.hgrc,*\/.hg\/hgrc setf ini\r\n\r\n","5":"First, copy this file to ~\/.vim\/syntax\/ini.vim. (You will need to create that directory, if you haven't already.)\r\n\r\nThen, to make vim automatically use that syntax definition for .ini and hgrc files, you'll need to add this to your ~\/.vim\/filetype.vim file (which you will need to create, if you haven't already):\r\n\r\nau BufNewFile,BufRead *.ini,*\/.hgrc,*\/.hg\/hgrc setf ini\r\n\r\n","first_name":"Peter","6":"Peter","last_name":"Hosey","7":"Hosey","releases":[{"0":"2475","vim_version":"7.0","1":"7.0","script_version":"03","2":"03","version_comment":"Same as v2, which was missing its ini.vim file for some reason (?!).","3":"Same as v2, which was missing its ini.vim file for some reason (?!).","package":"vim-ini-syntax-03.zip","4":"vim-ini-syntax-03.zip","src_id":"10629","5":"10629","creation_date":"1242663754","6":"1242663754"},{"0":"2475","vim_version":"7.0","1":"7.0","script_version":"02","2":"02","version_comment":"Added support for comments.","3":"Added support for comments.","package":"vim-ini-syntax-02.zip","4":"vim-ini-syntax-02.zip","src_id":"9633","5":"9633","creation_date":"1228765329","6":"1228765329"},{"0":"2475","vim_version":"7.2","1":"7.2","script_version":"01","2":"01","version_comment":"Initial upload","3":"Initial upload","package":"vim-ini-syntax-01.zip","4":"vim-ini-syntax-01.zip","src_id":"9632","5":"9632","creation_date":"1228763795","6":"1228763795"}]},"2474":{"script_id":"2474","0":"2474","script_name":"Gentooish","1":"Gentooish","script_type":"color scheme","2":"color scheme","summary":"Dark, moderately-saturated color scheme with greens and purples","3":"Dark, moderately-saturated color scheme with greens and purples","description":"This is a dark color scheme vaguely inspired by the colors of Gentoo Linux, i.e. lots of purples and greens.  But lots of other colors too.  The colors are saturated and different enough to tell things apart at a glance, without being so bright that your eyes bleed.\r\n\r\nThe colors look OK in a GUI and 256 color terminal.  (Terminal version was dumped via  vimscript #2390, then cleaned up a bit.)\r\n\r\nScreenshot: http:\/\/briancarper.net\/vim\/gentooish.png","4":"This is a dark color scheme vaguely inspired by the colors of Gentoo Linux, i.e. lots of purples and greens.  But lots of other colors too.  The colors are saturated and different enough to tell things apart at a glance, without being so bright that your eyes bleed.\r\n\r\nThe colors look OK in a GUI and 256 color terminal.  (Terminal version was dumped via  vimscript #2390, then cleaned up a bit.)\r\n\r\nScreenshot: http:\/\/briancarper.net\/vim\/gentooish.png","install_details":"Put into ~\/.vim\/colors, then :colo gentooish.","5":"Put into ~\/.vim\/colors, then :colo gentooish.","first_name":"Brian","6":"Brian","last_name":"Carper","7":"Carper","releases":[{"0":"2474","vim_version":"7.0","1":"7.0","script_version":"0.3","2":"0.3","version_comment":"Initial upload","3":"Initial upload","package":"gentooish.vim","4":"gentooish.vim","src_id":"9630","5":"9630","creation_date":"1228695566","6":"1228695566"}]},"2473":{"script_id":"2473","0":"2473","script_name":"python_open_module","1":"python_open_module","script_type":"ftplugin","2":"ftplugin","summary":"open the python module file below the cursor when coding python","3":"open the python module file below the cursor when coding python","description":"the python_open_module.vim is the script that allows you open the module file  below the cursor when coding python. It's easy to use. For example, you can create a new python file and input:\r\n\r\nimport string\r\n\r\nmove the cursor above \"string\" and press \"<LocalLeader>oo\"(\"\\oo\" in common in vim) in normal mode You could see the string.py file opened in current window. you can continue to input:\r\n\r\nstring.lower\r\n\r\ndo same above and you can see string.py file opened the cursor jump into lower function.\r\n\r\nthe open fail if the module is buildin such as 'sys' or is not available.\r\n\r\nThere are three options for mapping key, you can chang it to any other key:\r\n\r\npom_key_open='<LocalLeader>oo'              # open module file in the current window\r\npom_key_open_in_win='<LocalLeader>ow'             # open module file in a new window\r\npom_key_open_in_tab='<LocalLeader>ot'               # open module file in a tab\r\n\r\n\r\nWORNING: Required vim compiled with +python\r\n","4":"the python_open_module.vim is the script that allows you open the module file  below the cursor when coding python. It's easy to use. For example, you can create a new python file and input:\r\n\r\nimport string\r\n\r\nmove the cursor above \"string\" and press \"<LocalLeader>oo\"(\"\\oo\" in common in vim) in normal mode You could see the string.py file opened in current window. you can continue to input:\r\n\r\nstring.lower\r\n\r\ndo same above and you can see string.py file opened the cursor jump into lower function.\r\n\r\nthe open fail if the module is buildin such as 'sys' or is not available.\r\n\r\nThere are three options for mapping key, you can chang it to any other key:\r\n\r\npom_key_open='<LocalLeader>oo'              # open module file in the current window\r\npom_key_open_in_win='<LocalLeader>ow'             # open module file in a new window\r\npom_key_open_in_tab='<LocalLeader>ot'               # open module file in a tab\r\n\r\n\r\nWORNING: Required vim compiled with +python\r\n","install_details":"copy the script into ~\/.vim\/ftplugin","5":"copy the script into ~\/.vim\/ftplugin","first_name":"tocer","6":"tocer","last_name":"deng","7":"deng","releases":[{"0":"2473","vim_version":"6.0","1":"6.0","script_version":"1.0.2","2":"1.0.2","version_comment":"Fixed it can't open the module file in current window if the current buffer is changed.","3":"Fixed it can't open the module file in current window if the current buffer is changed.","package":"python_open_module.vim","4":"python_open_module.vim","src_id":"9680","5":"9680","creation_date":"1229436709","6":"1229436709"},{"0":"2473","vim_version":"6.0","1":"6.0","script_version":"1.0.1","2":"1.0.1","version_comment":"fixed a bug","3":"fixed a bug","package":"python_open_module.vim","4":"python_open_module.vim","src_id":"9676","5":"9676","creation_date":"1229322031","6":"1229322031"},{"0":"2473","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"* rename python_jumper.vim to python_open_module.vim.\r\n* allow map key youself, cancel old map key such as 'gf'\r\n* increasing identification of module name\r\n* bug fixed","3":"* rename python_jumper.vim to python_open_module.vim.\r\n* allow map key youself, cancel old map key such as 'gf'\r\n* increasing identification of module name\r\n* bug fixed","package":"python_open_module.vim","4":"python_open_module.vim","src_id":"9673","5":"9673","creation_date":"1229265168","6":"1229265168"},{"0":"2473","vim_version":"6.0","1":"6.0","script_version":"0.6","2":"0.6","version_comment":"Initial upload","3":"Initial upload","package":"python_jumper.vim","4":"python_jumper.vim","src_id":"9625","5":"9625","creation_date":"1228620133","6":"1228620133"}]},"2472":{"script_id":"2472","0":"2472","script_name":"Csound compiler plugin","1":"Csound compiler plugin","script_type":"ftplugin","2":"ftplugin","summary":"Csound compiler plugin","3":"Csound compiler plugin","description":"This ftplugin will compile 2 csound files (orchestra file and scores file ) or csd file and plays compiled sound\r\n\r\nWhen compiling orc or sco file it does not matter which of them you try to compile, but files must have\r\nthe same name and different extension\r\n","4":"This ftplugin will compile 2 csound files (orchestra file and scores file ) or csd file and plays compiled sound\r\n\r\nWhen compiling orc or sco file it does not matter which of them you try to compile, but files must have\r\nthe same name and different extension\r\n","install_details":"Just drop it this file in your compiler plugin folder\/directory.\r\n\r\nUse this for example to auto select compiler\r\n:autocmd BufNewFile,BufRead *.orc,*.sco compiler csound\r\n","5":"Just drop it this file in your compiler plugin folder\/directory.\r\n\r\nUse this for example to auto select compiler\r\n:autocmd BufNewFile,BufRead *.orc,*.sco compiler csound\r\n","first_name":"Olexiy","6":"Olexiy","last_name":"Zamkoviy","7":"Zamkoviy","releases":[{"0":"2472","vim_version":"7.0","1":"7.0","script_version":"0.2","2":"0.2","version_comment":"Lines of code replaced with one string ! :) Now the script is more easy, handles csd files as well as orc and sco, added playing sound after compiling","3":"Lines of code replaced with one string ! :) Now the script is more easy, handles csd files as well as orc and sco, added playing sound after compiling","package":"csound.vim","4":"csound.vim","src_id":"9635","5":"9635","creation_date":"1228780974","6":"1228780974"},{"0":"2472","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"csound.vim","4":"csound.vim","src_id":"9624","5":"9624","creation_date":"1228604852","6":"1228604852"}]},"2471":{"script_id":"2471","0":"2471","script_name":"paintbox","1":"paintbox","script_type":"color scheme","2":"color scheme","summary":"A colourful, happy scheme with high contrast","3":"A colourful, happy scheme with high contrast","description":"A colourful, happy scheme with high contrast.\r\nhttp:\/\/img176.imageshack.us\/img176\/8033\/vimpaintboxcc4.png","4":"A colourful, happy scheme with high contrast.\r\nhttp:\/\/img176.imageshack.us\/img176\/8033\/vimpaintboxcc4.png","install_details":"Place in your Vim colour schemes directory (probably ~\/.vim\/colors) for autoloading on startup and :source it or restart Vim, or just anywhere and :source it.","5":"Place in your Vim colour schemes directory (probably ~\/.vim\/colors) for autoloading on startup and :source it or restart Vim, or just anywhere and :source it.","first_name":"kamil","6":"kamil","last_name":"stachowski","7":"stachowski","releases":[{"0":"2471","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"paintbox.vim","4":"paintbox.vim","src_id":"9616","5":"9616","creation_date":"1228500337","6":"1228500337"}]},"2470":{"script_id":"2470","0":"2470","script_name":"smartword","1":"smartword","script_type":"utility","2":"utility","summary":"Smart motions on words","3":"Smart motions on words","description":"*smartword* is a Vim plugin to provide {motion}s on |word|s which are smarter\r\nthan the built-in ones in some sense.  For example, |w| moves the cursor to\r\nthe next word as follows (here \"#\" means a position to which |w| moves the\r\ncursor for each time):\r\n\r\n\t<a href=\"http:\/\/www.vim.org\/\">www.vim.org<\/a>\r\n\t # #   # #   #  #  ##  ##  #  #  ##  ##  # #\r\n\r\nBecause there are two types of words and |w| moves to the next word which can\r\nbe the both types.  Let's call \"L\" for a type of words and \"P\" for another\r\ntype of words, where \"L\" means a word which consists of a sequence of letters\r\n(which are defined by 'iskeyword' option) and \"P\" means a word which consists\r\nof a sequence of other non-blank characters.\r\n\r\nIn many cases, you might want to move to the next \"L\", not \"P\".  This plugin\r\nprovides {motion}s to behave so.  For example, |<Plug>(smartword-w)| which is\r\ncorresponding to |w| moves the cursor as follows:\r\n\r\n\t<a href=\"http:\/\/www.vim.org\/\">www.vim.org<\/a>\r\n\t # #     #      #   #   #     #   #   #    #\r\n\r\nSee also |smartword-examples| for customization.\r\n\r\nSee also the following image if the above figures aren't correctly displayed:\r\nhttp:\/\/gyazo.com\/bc7887d9bb0f6aa3eee1e67b0d756b2e.png\r\n\r\n\r\nRequirements:\r\n- Vim 7.2 or later\r\n\r\nLatest version:\r\nhttp:\/\/github.com\/kana\/vim-smartword\r\n\r\nDocument in HTML format:\r\nhttp:\/\/kana.github.com\/config\/vim\/smartword.html","4":"*smartword* is a Vim plugin to provide {motion}s on |word|s which are smarter\r\nthan the built-in ones in some sense.  For example, |w| moves the cursor to\r\nthe next word as follows (here \"#\" means a position to which |w| moves the\r\ncursor for each time):\r\n\r\n\t<a href=\"http:\/\/www.vim.org\/\">www.vim.org<\/a>\r\n\t # #   # #   #  #  ##  ##  #  #  ##  ##  # #\r\n\r\nBecause there are two types of words and |w| moves to the next word which can\r\nbe the both types.  Let's call \"L\" for a type of words and \"P\" for another\r\ntype of words, where \"L\" means a word which consists of a sequence of letters\r\n(which are defined by 'iskeyword' option) and \"P\" means a word which consists\r\nof a sequence of other non-blank characters.\r\n\r\nIn many cases, you might want to move to the next \"L\", not \"P\".  This plugin\r\nprovides {motion}s to behave so.  For example, |<Plug>(smartword-w)| which is\r\ncorresponding to |w| moves the cursor as follows:\r\n\r\n\t<a href=\"http:\/\/www.vim.org\/\">www.vim.org<\/a>\r\n\t # #     #      #   #   #     #   #   #    #\r\n\r\nSee also |smartword-examples| for customization.\r\n\r\nSee also the following image if the above figures aren't correctly displayed:\r\nhttp:\/\/gyazo.com\/bc7887d9bb0f6aa3eee1e67b0d756b2e.png\r\n\r\n\r\nRequirements:\r\n- Vim 7.2 or later\r\n\r\nLatest version:\r\nhttp:\/\/github.com\/kana\/vim-smartword\r\n\r\nDocument in HTML format:\r\nhttp:\/\/kana.github.com\/config\/vim\/smartword.html","install_details":"...","5":"...","first_name":"Kana","6":"Kana","last_name":"Natsuno","7":"Natsuno","releases":[{"0":"2470","vim_version":"7.0","1":"7.0","script_version":"0.0.2","2":"0.0.2","version_comment":"- Fix the document a bit.\n- Revise the treatment on 'iskeyword'.\n- Fix 2 bugs on |<Plug>(smartword-e)| and |<Plug>(smartword-ge)| with |o_v|.  These bugs are appeared only in Vim with the patch (*).","3":"- Fix the document a bit.\n- Revise the treatment on 'iskeyword'.\n- Fix 2 bugs on |<Plug>(smartword-e)| and |<Plug>(smartword-ge)| with |o_v|.  These bugs are appeared only in Vim with the patch (*).","package":"vim-smartword-0.0.2.zip","4":"vim-smartword-0.0.2.zip","src_id":"9853","5":"9853","creation_date":"1232719849","6":"1232719849"},{"0":"2470","vim_version":"7.0","1":"7.0","script_version":"0.0.1","2":"0.0.1","version_comment":"- Fix |<Plug>(smartword-e)| and |<Plug>(smartword-ge)| to be\n  |inclusive| as same as |e| and |ge|.","3":"- Fix |<Plug>(smartword-e)| and |<Plug>(smartword-ge)| to be\n  |inclusive| as same as |e| and |ge|.","package":"vim-smartword-0.0.1.zip","4":"vim-smartword-0.0.1.zip","src_id":"9621","5":"9621","creation_date":"1228555122","6":"1228555122"},{"0":"2470","vim_version":"7.0","1":"7.0","script_version":"0.0.0","2":"0.0.0","version_comment":"Initial upload","3":"Initial upload","package":"vim-smartword-0.0.0.zip","4":"vim-smartword-0.0.0.zip","src_id":"9615","5":"9615","creation_date":"1228487674","6":"1228487674"}]},"2469":{"script_id":"2469","0":"2469","script_name":"translit","1":"translit","script_type":"utility","2":"utility","summary":"Transliteration mode for Vim (russian, greek)","3":"Transliteration mode for Vim (russian, greek)","description":"http:\/\/github.com\/einars\/translit.vim\r\n\r\nThis plugin allows you to write texts in transliterated russian (or any other language you'll write a definition for). That means, you write \"Cheburashka\" and it gets automagically converted to \"Чебурашка\", or write \"Ellada\" and it converts to \"Ελλαδα\"\r\n\r\nThis plugin is loosely based on russian_plansliterated.vim plugin by Krzystof Goj (http:\/\/www.vim.org\/scripts\/script.php?script_id=2401) and was used as my playground for learning vimscript.\r\n\r\nBasic Usage:\r\nDrop plugin under ~\/.vim\/plugins and switch translit mode on\/off with Ctrl-Shift-t.\r\n\r\nRead the file for more help on configuration and usage.\r\n","4":"http:\/\/github.com\/einars\/translit.vim\r\n\r\nThis plugin allows you to write texts in transliterated russian (or any other language you'll write a definition for). That means, you write \"Cheburashka\" and it gets automagically converted to \"Чебурашка\", or write \"Ellada\" and it converts to \"Ελλαδα\"\r\n\r\nThis plugin is loosely based on russian_plansliterated.vim plugin by Krzystof Goj (http:\/\/www.vim.org\/scripts\/script.php?script_id=2401) and was used as my playground for learning vimscript.\r\n\r\nBasic Usage:\r\nDrop plugin under ~\/.vim\/plugins and switch translit mode on\/off with Ctrl-Shift-t.\r\n\r\nRead the file for more help on configuration and usage.\r\n","install_details":"Drop plugin under ~\/.vim\/plugins and switch translit mode on\/off with Ctrl-Shift-t.\r\n","5":"Drop plugin under ~\/.vim\/plugins and switch translit mode on\/off with Ctrl-Shift-t.\r\n","first_name":"Einar","6":"Einar","last_name":"Lielmanis","7":"Lielmanis","releases":[{"0":"2469","vim_version":"7.0","1":"7.0","script_version":"1.52","2":"1.52","version_comment":"Minor changes in description and configuration.","3":"Minor changes in description and configuration.","package":"translit.vim","4":"translit.vim","src_id":"9610","5":"9610","creation_date":"1228378001","6":"1228378001"},{"0":"2469","vim_version":"7.0","1":"7.0","script_version":"1.51","2":"1.51","version_comment":"Greek characters input mapping (no keyboard shortcut by default, though)\r\nMultiple transliterations are now supported.","3":"Greek characters input mapping (no keyboard shortcut by default, though)\r\nMultiple transliterations are now supported.","package":"translit.vim","4":"translit.vim","src_id":"9608","5":"9608","creation_date":"1228338489","6":"1228338489"},{"0":"2469","vim_version":"7.0","1":"7.0","script_version":"1.01","2":"1.01","version_comment":"Added some missing transliterations for translit.ru.","3":"Added some missing transliterations for translit.ru.","package":"translit.vim","4":"translit.vim","src_id":"9605","5":"9605","creation_date":"1228329303","6":"1228329303"},{"0":"2469","vim_version":"7.2","1":"7.2","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"translit.vim","4":"translit.vim","src_id":"9603","5":"9603","creation_date":"1228305744","6":"1228305744"}]},"2468":{"script_id":"2468","0":"2468","script_name":"sandbox","1":"sandbox","script_type":"utility","2":"utility","summary":"A vim script for managing subversion sandbox.","3":"A vim script for managing subversion sandbox.","description":"After installing this plugin, ':Sandbox <sandbox_directory>' on the command line will create a new buffer\r\nwhich list the currnet status of the sandbox. In the buffer, a few handy mapping are available like diffing, commit, revert, etc. See the help at  the bottom of the buffer.\r\n\r\nScreenshot:\r\nhttp:\/\/files.myopera.com\/wzhliang\/albums\/649613\/sandbox.png\r\n\r\nLinux only!\r\n\r\nDepends on: svn, meld or tkdiff for GUI diffing.\r\n ---------- H E L P -----------\r\n c         Commit a single file or selected files.\r\n d         Diff the file specified in the current line.\r\n e         Open the file in question in a new tab.\r\n r         Revert a single file or selected files.\r\n t         Select\/Unselect a single file.\r\n u, U    Update a single file or update all files.\r\n v        Resolved a single file or selected files.\r\n C-D     Reset selection.\r\n <F5>    Refresh the buffer.\r\n q       Quit\r\n","4":"After installing this plugin, ':Sandbox <sandbox_directory>' on the command line will create a new buffer\r\nwhich list the currnet status of the sandbox. In the buffer, a few handy mapping are available like diffing, commit, revert, etc. See the help at  the bottom of the buffer.\r\n\r\nScreenshot:\r\nhttp:\/\/files.myopera.com\/wzhliang\/albums\/649613\/sandbox.png\r\n\r\nLinux only!\r\n\r\nDepends on: svn, meld or tkdiff for GUI diffing.\r\n ---------- H E L P -----------\r\n c         Commit a single file or selected files.\r\n d         Diff the file specified in the current line.\r\n e         Open the file in question in a new tab.\r\n r         Revert a single file or selected files.\r\n t         Select\/Unselect a single file.\r\n u, U    Update a single file or update all files.\r\n v        Resolved a single file or selected files.\r\n C-D     Reset selection.\r\n <F5>    Refresh the buffer.\r\n q       Quit\r\n","install_details":"This plugin will be distributed as a vimball. So simply edit the vimbal and :so it.","5":"This plugin will be distributed as a vimball. So simply edit the vimbal and :so it.","first_name":"Wenzhi","6":"Wenzhi","last_name":"Liang","7":"Liang","releases":[{"0":"2468","vim_version":"7.0","1":"7.0","script_version":"0.3","2":"0.3","version_comment":"Add F6 to switch between GUI tool and vcscommand.vim.\r\nBetter default behaviour.\r\nMore robust.\r\n","3":"Add F6 to switch between GUI tool and vcscommand.vim.\r\nBetter default behaviour.\r\nMore robust.\r\n","package":"sandbox_0.3.vba","4":"sandbox_0.3.vba","src_id":"13270","5":"13270","creation_date":"1277917786","6":"1277917786"},{"0":"2468","vim_version":"7.0","1":"7.0","script_version":"0.2","2":"0.2","version_comment":"Now svn 1.6 compatible. \r\nAdded support for using vcscommand.vim\r\nSupport multiple sandbox at the same time.\r\nAdded more commands.\r\nSpeed improvements.\r\n","3":"Now svn 1.6 compatible. \r\nAdded support for using vcscommand.vim\r\nSupport multiple sandbox at the same time.\r\nAdded more commands.\r\nSpeed improvements.\r\n","package":"sandbox_0.2.vba","4":"sandbox_0.2.vba","src_id":"10613","5":"10613","creation_date":"1242483924","6":"1242483924"},{"0":"2468","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"sandbox.vba","4":"sandbox.vba","src_id":"9600","5":"9600","creation_date":"1228254741","6":"1228254741"}]},"2467":{"script_id":"2467","0":"2467","script_name":"submode","1":"submode","script_type":"utility","2":"utility","summary":"Create your own submodes","3":"Create your own submodes","description":"*submode* is a Vim plugin to provide the way to define \"submodes\" to the\r\nbuilt-in |vim-modes|.  For example, whenever you type |g-| and\/or |g+| to\r\nundo\/redo many times, don't you want to type \"g++--++...\" instead\r\n\"g+g+g-g-g+g+...\"?  With this plugin, you can define such interface with the\r\nfollowing settings:\r\n\r\n\tcall submode#enter_with('undo\/redo', 'n', '', 'g-', 'g-')\r\n\tcall submode#enter_with('undo\/redo', 'n', '', 'g+', 'g+')\r\n\tcall submode#leave_with('undo\/redo', 'n', '', '<Esc>')\r\n\tcall submode#map('undo\/redo', 'n', '', '-', 'g-')\r\n\tcall submode#map('undo\/redo', 'n', '', '+', 'g+')\r\n\r\nThe above settings mean:\r\n- Define a new submode named \"undo\/redo\".\r\n- Define \"g-\" and \"g+\" as key sequences to enter the submode \"undo\/redo\" from\r\n  Normal mode.  Aditionally, they does undo\/redo before entering the submode\r\n  \"undo\/redo\".\r\n- In the submode \"undo\/redo\", \"-\" and \"+\" do undo\/redo.\r\n- In the submode \"undo\/redo\", \"<Esc>\" leaves the submode.\r\n\r\n\t\t\t\t\t\t*submode-leaving*\r\nBy default, <Esc> is automatically defined as a key to leave any submode.\r\nSo you don't have to explicitly define like the above example.\r\nThere are also 2 ways to leave submodes:\r\n- Type any key sequence which is not mapped in the submode.\r\n- Don't type any key for a long time.  See |submode-variables| to configure\r\n  the details of this time out.\r\n\r\n\r\nRequirements:\r\n- Vim 7.2 or later\r\n\r\nLatest version:\r\nhttp:\/\/github.com\/kana\/vim-submode\r\n\r\nDocument in HTML format:\r\nhttp:\/\/kana.github.com\/config\/vim\/submode.html","4":"*submode* is a Vim plugin to provide the way to define \"submodes\" to the\r\nbuilt-in |vim-modes|.  For example, whenever you type |g-| and\/or |g+| to\r\nundo\/redo many times, don't you want to type \"g++--++...\" instead\r\n\"g+g+g-g-g+g+...\"?  With this plugin, you can define such interface with the\r\nfollowing settings:\r\n\r\n\tcall submode#enter_with('undo\/redo', 'n', '', 'g-', 'g-')\r\n\tcall submode#enter_with('undo\/redo', 'n', '', 'g+', 'g+')\r\n\tcall submode#leave_with('undo\/redo', 'n', '', '<Esc>')\r\n\tcall submode#map('undo\/redo', 'n', '', '-', 'g-')\r\n\tcall submode#map('undo\/redo', 'n', '', '+', 'g+')\r\n\r\nThe above settings mean:\r\n- Define a new submode named \"undo\/redo\".\r\n- Define \"g-\" and \"g+\" as key sequences to enter the submode \"undo\/redo\" from\r\n  Normal mode.  Aditionally, they does undo\/redo before entering the submode\r\n  \"undo\/redo\".\r\n- In the submode \"undo\/redo\", \"-\" and \"+\" do undo\/redo.\r\n- In the submode \"undo\/redo\", \"<Esc>\" leaves the submode.\r\n\r\n\t\t\t\t\t\t*submode-leaving*\r\nBy default, <Esc> is automatically defined as a key to leave any submode.\r\nSo you don't have to explicitly define like the above example.\r\nThere are also 2 ways to leave submodes:\r\n- Type any key sequence which is not mapped in the submode.\r\n- Don't type any key for a long time.  See |submode-variables| to configure\r\n  the details of this time out.\r\n\r\n\r\nRequirements:\r\n- Vim 7.2 or later\r\n\r\nLatest version:\r\nhttp:\/\/github.com\/kana\/vim-submode\r\n\r\nDocument in HTML format:\r\nhttp:\/\/kana.github.com\/config\/vim\/submode.html","install_details":"...","5":"...","first_name":"Kana","6":"Kana","last_name":"Natsuno","7":"Natsuno","releases":[{"0":"2467","vim_version":"7.0","1":"7.0","script_version":"0.0.0","2":"0.0.0","version_comment":"Initial upload","3":"Initial upload","package":"vim-submode-0.0.0.zip","4":"vim-submode-0.0.0.zip","src_id":"9591","5":"9591","creation_date":"1228151772","6":"1228151772"}]},"2466":{"script_id":"2466","0":"2466","script_name":"cdargs","1":"cdargs","script_type":"utility","2":"utility","summary":"Directory bookmarking based on CDargs","3":"Directory bookmarking based on CDargs","description":"Reads your cdargs bookmark file (\"~\/.cdargs\") and provides a couple commands:\r\n  Cdb - Change directory to bookmark\r\n  Eb - Edit file in bookmark directory\r\n  Tb - Edit file in a new tab\r\n\r\nHomepage: http:\/\/github.com\/gaffneyc\/vim-cdargs\/\r\n\r\nCDargs: http:\/\/www.skamphausen.de\/cgi-bin\/ska\/CDargs\r\n\r\n","4":"Reads your cdargs bookmark file (\"~\/.cdargs\") and provides a couple commands:\r\n  Cdb - Change directory to bookmark\r\n  Eb - Edit file in bookmark directory\r\n  Tb - Edit file in a new tab\r\n\r\nHomepage: http:\/\/github.com\/gaffneyc\/vim-cdargs\/\r\n\r\nCDargs: http:\/\/www.skamphausen.de\/cgi-bin\/ska\/CDargs\r\n\r\n","install_details":"To install copy cdargs.vim to ~\/.vim\/plugins\/","5":"To install copy cdargs.vim to ~\/.vim\/plugins\/","first_name":"Chris","6":"Chris","last_name":"Gaffney","7":"Gaffney","releases":[{"0":"2466","vim_version":"7.0","1":"7.0","script_version":"1.2","2":"1.2","version_comment":"1.1\r\n  Added Tb command\r\n\r\n1.2\r\n  Fix bookmarks that have a space in their path\r\n  Better error handling if a subpath cannot be found","3":"1.1\r\n  Added Tb command\r\n\r\n1.2\r\n  Fix bookmarks that have a space in their path\r\n  Better error handling if a subpath cannot be found","package":"cdargs.vim","4":"cdargs.vim","src_id":"13100","5":"13100","creation_date":"1275576219","6":"1275576219"},{"0":"2466","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"cdargs.vim","4":"cdargs.vim","src_id":"9588","5":"9588","creation_date":"1227942285","6":"1227942285"}]},"2465":{"script_id":"2465","0":"2465","script_name":"wombat256.vim","1":"wombat256.vim","script_type":"color scheme","2":"color scheme","summary":"Wombat for 256 color xterms","3":"Wombat for 256 color xterms","description":"This is a version of Wombat (vimscript #1778) by Lars Nielsen that also works on xterms with 256 colors.\r\n\r\nA customized version is also available, with additional highlighting groups for diff mode and search.","4":"This is a version of Wombat (vimscript #1778) by Lars Nielsen that also works on xterms with 256 colors.\r\n\r\nA customized version is also available, with additional highlighting groups for diff mode and search.","install_details":"Put the script into your Vim 'colors' directory (e.g. ~\/.vim\/colors), and load it with the command :colorscheme wombat256 or :colorscheme wombat256mod","5":"Put the script into your Vim 'colors' directory (e.g. ~\/.vim\/colors), and load it with the command :colorscheme wombat256 or :colorscheme wombat256mod","first_name":"David","6":"David","last_name":"Liang","7":"Liang","releases":[{"0":"2465","vim_version":"7.0","1":"7.0","script_version":"2.0mod","2":"2.0mod","version_comment":"Version with some modifications to the original color scheme. In addition, the following highlight groups have been added: Cursor, VisualNOS, Search, WarningMsg, ErrorMsg, DiffAdd, DiffDelete, DiffText, DiffChange.","3":"Version with some modifications to the original color scheme. In addition, the following highlight groups have been added: Cursor, VisualNOS, Search, WarningMsg, ErrorMsg, DiffAdd, DiffDelete, DiffText, DiffChange.","package":"wombat256mod.vim","4":"wombat256mod.vim","src_id":"13400","5":"13400","creation_date":"1279923400","6":"1279923400"},{"0":"2465","vim_version":"7.0","1":"7.0","script_version":"2.0","2":"2.0","version_comment":"New version by Danila Bespalov follows the original colors from wombat.vim; can be used as a replacement for wombat.vim, since the GUI portion is the same.","3":"New version by Danila Bespalov follows the original colors from wombat.vim; can be used as a replacement for wombat.vim, since the GUI portion is the same.","package":"wombat256.vim","4":"wombat256.vim","src_id":"13397","5":"13397","creation_date":"1279918994","6":"1279918994"},{"0":"2465","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"wombat256.vim","4":"wombat256.vim","src_id":"9587","5":"9587","creation_date":"1227937403","6":"1227937403"}]},"2464":{"script_id":"2464","0":"2464","script_name":"session_dialog.vim","1":"session_dialog.vim","script_type":"utility","2":"utility","summary":"manage vim sessions using dialogs and the command line","3":"manage vim sessions using dialogs and the command line","description":"session_dialog.vim provides a simple dialog and command-line based\r\ninterface to Vim's :mksession feature. There are commands to save sessions\r\nand restore, delete, and list sessions from multiple locations. It works\r\nwell with the terminal as well as console dialogs in GVIM (set\r\nguioptions+=c), and provides command-line completion of session names.\r\n\r\nUsage:\r\n:SessionSave [SESSION]\r\n  With no arguments, displays the save dialog. Otherwise, saves a new\r\n  session with the given name in SessionSaveDirectory. The session file on\r\n  disk will have the SessionFilePrefix and SessionFileSuffix attached (see\r\n  \"Options\" below). Spaces are allowed in the sesison name.\r\n  e.g. :SessionSave foo bar creates the session \"foo bar\"\r\n\r\n:SessionRestore [GLOB_PATTERN]\r\n  With no arguments, displays the restore dialog. Otherwise searches for a\r\n  session to load in SessionPath. If more than one session was found (if\r\n  sessions with the same name were found in different paths or if the\r\n  given pattern matched multiple sessions), you will be prompted to choose\r\n  one.\r\n  e.g. :SessionRestore foo*\r\n\r\n:SessionDelete [SESSION|GLOB_PATTERN]...\r\n  Displays the delete session dialog if no arguments were given, otherwise\r\n  deletes all the sessions that match the arguments. Spaces need to be\r\n  escaped since they would otherwise separate the arguments.\r\n  e.g. :SessionDelete foo will delete the session named \"foo\". If more\r\n  than one session is named \"foo\", you will be prompted to select one. You\r\n  can also use a pattern (e.g. :SessionDelete foo*). This will delete all\r\n  sessions beginning with \"foo\".\r\n\r\n:SessionList [GLOB_PATTERN]...\r\n  Prints a list of all the sessions and their locations in SessionPath if\r\n  no arguments were given. Otherwise prints a list of sessions that match\r\n  the arguments.\r\n  e.g. :SessionList foo bar* *baz will show all the sessions named foo,\r\n  starting with bar, or ending with baz.\r\n\r\nZS ZR ZD ZL\r\n  The default normal mode mappings for :SessionSave, :SessionRestore,\r\n  :SessionDelete, and :SessionList, respectively. These can be disabled\r\n  with the option SessionCreateDefaultMaps. Note that these will time out,\r\n  unlike native commands such as ZZ. (see :help 'timeoutlen')\r\n\r\nYou can also map the commands yourself using:\r\n  <Plug>SessionSave\r\n  <Plug>SessionRestore\r\n  <Plug>SessionDelete\r\n  <Plug>SessionList\r\n\r\nOptions:\r\ng:SessionSaveDirectory\r\n  Default is \"$HOME\"\r\n  Where to save new sessions. This can be set in your vimrc or while Vim\r\n  is running. For example, to get the default behavior of :mksession,\r\n       let SessionSaveDirectory = \".\"\r\n\r\ng:SessionPath\r\n  Default is set to the initial value of SessionSaveDirectory\r\n  A comma-separated list of paths in which to look for session files to\r\n  restore or delete.\r\n  e.g. let SessionPath = \".,~,~\/.vim\/sessions\"\r\n\r\ng:SessionFilePrefix\r\n  Default is \".vimsession_\" (on Windows, \"_vimsession_\")\r\n\r\ng:SessionFileSuffix\r\n  Default is \"\" (on Windows, \".vim\")\r\n\r\n  Strings to prepend and append to session names when saving to\r\n  SessionSaveDirectory. All files found in SessionPath with these\r\n  attributes will be identified as sessions, so the combination of the two\r\n  should uniquely identify session files (unless all files found in\r\n  SessionPath will be Vim sessions).\r\n\r\ng:SessionDefault\r\n  Unset by default\r\n  The default session name to save to or restore from. This is overridden\r\n  by v:this_session. If both are unset, the Vim server name (v:servername)\r\n  will be used as the default.\r\n\r\ng:SessionConfirmOverwrite\r\n  0 or 1 (default)\r\n  Set this to 0 to save over an existing session file without asking for\r\n  confirmation.\r\n\r\ng:SessionQuitAfterSave\r\n  1 or 0 (default)\r\n  Whether to exit Vim after saving a new session.\r\n\r\ng:SessionCreateDefaultMaps\r\n  0 or 1 (default)\r\n  Whether to create the default normal mode mappings (ZS, ZR, ZD, and ZL).\r\n","4":"session_dialog.vim provides a simple dialog and command-line based\r\ninterface to Vim's :mksession feature. There are commands to save sessions\r\nand restore, delete, and list sessions from multiple locations. It works\r\nwell with the terminal as well as console dialogs in GVIM (set\r\nguioptions+=c), and provides command-line completion of session names.\r\n\r\nUsage:\r\n:SessionSave [SESSION]\r\n  With no arguments, displays the save dialog. Otherwise, saves a new\r\n  session with the given name in SessionSaveDirectory. The session file on\r\n  disk will have the SessionFilePrefix and SessionFileSuffix attached (see\r\n  \"Options\" below). Spaces are allowed in the sesison name.\r\n  e.g. :SessionSave foo bar creates the session \"foo bar\"\r\n\r\n:SessionRestore [GLOB_PATTERN]\r\n  With no arguments, displays the restore dialog. Otherwise searches for a\r\n  session to load in SessionPath. If more than one session was found (if\r\n  sessions with the same name were found in different paths or if the\r\n  given pattern matched multiple sessions), you will be prompted to choose\r\n  one.\r\n  e.g. :SessionRestore foo*\r\n\r\n:SessionDelete [SESSION|GLOB_PATTERN]...\r\n  Displays the delete session dialog if no arguments were given, otherwise\r\n  deletes all the sessions that match the arguments. Spaces need to be\r\n  escaped since they would otherwise separate the arguments.\r\n  e.g. :SessionDelete foo will delete the session named \"foo\". If more\r\n  than one session is named \"foo\", you will be prompted to select one. You\r\n  can also use a pattern (e.g. :SessionDelete foo*). This will delete all\r\n  sessions beginning with \"foo\".\r\n\r\n:SessionList [GLOB_PATTERN]...\r\n  Prints a list of all the sessions and their locations in SessionPath if\r\n  no arguments were given. Otherwise prints a list of sessions that match\r\n  the arguments.\r\n  e.g. :SessionList foo bar* *baz will show all the sessions named foo,\r\n  starting with bar, or ending with baz.\r\n\r\nZS ZR ZD ZL\r\n  The default normal mode mappings for :SessionSave, :SessionRestore,\r\n  :SessionDelete, and :SessionList, respectively. These can be disabled\r\n  with the option SessionCreateDefaultMaps. Note that these will time out,\r\n  unlike native commands such as ZZ. (see :help 'timeoutlen')\r\n\r\nYou can also map the commands yourself using:\r\n  <Plug>SessionSave\r\n  <Plug>SessionRestore\r\n  <Plug>SessionDelete\r\n  <Plug>SessionList\r\n\r\nOptions:\r\ng:SessionSaveDirectory\r\n  Default is \"$HOME\"\r\n  Where to save new sessions. This can be set in your vimrc or while Vim\r\n  is running. For example, to get the default behavior of :mksession,\r\n       let SessionSaveDirectory = \".\"\r\n\r\ng:SessionPath\r\n  Default is set to the initial value of SessionSaveDirectory\r\n  A comma-separated list of paths in which to look for session files to\r\n  restore or delete.\r\n  e.g. let SessionPath = \".,~,~\/.vim\/sessions\"\r\n\r\ng:SessionFilePrefix\r\n  Default is \".vimsession_\" (on Windows, \"_vimsession_\")\r\n\r\ng:SessionFileSuffix\r\n  Default is \"\" (on Windows, \".vim\")\r\n\r\n  Strings to prepend and append to session names when saving to\r\n  SessionSaveDirectory. All files found in SessionPath with these\r\n  attributes will be identified as sessions, so the combination of the two\r\n  should uniquely identify session files (unless all files found in\r\n  SessionPath will be Vim sessions).\r\n\r\ng:SessionDefault\r\n  Unset by default\r\n  The default session name to save to or restore from. This is overridden\r\n  by v:this_session. If both are unset, the Vim server name (v:servername)\r\n  will be used as the default.\r\n\r\ng:SessionConfirmOverwrite\r\n  0 or 1 (default)\r\n  Set this to 0 to save over an existing session file without asking for\r\n  confirmation.\r\n\r\ng:SessionQuitAfterSave\r\n  1 or 0 (default)\r\n  Whether to exit Vim after saving a new session.\r\n\r\ng:SessionCreateDefaultMaps\r\n  0 or 1 (default)\r\n  Whether to create the default normal mode mappings (ZS, ZR, ZD, and ZL).\r\n","install_details":"Put the file in your Vim 'plugin' directory (usually ~\/.vim\/plugin, or Program Files\/Vim\/vimfiles on Windows)","5":"Put the file in your Vim 'plugin' directory (usually ~\/.vim\/plugin, or Program Files\/Vim\/vimfiles on Windows)","first_name":"David","6":"David","last_name":"Liang","7":"Liang","releases":[{"0":"2464","vim_version":"7.0","1":"7.0","script_version":"1.2","2":"1.2","version_comment":"Added confirmation messages and <Plug> mappings","3":"Added confirmation messages and <Plug> mappings","package":"session_dialog.vim","4":"session_dialog.vim","src_id":"13405","5":"13405","creation_date":"1280121414","6":"1280121414"},{"0":"2464","vim_version":"7.0","1":"7.0","script_version":"1.03","2":"1.03","version_comment":"Use a default name when running Vim from terminal.","3":"Use a default name when running Vim from terminal.","package":"session_dialog.vim","4":"session_dialog.vim","src_id":"10448","5":"10448","creation_date":"1240652331","6":"1240652331"},{"0":"2464","vim_version":"7.0","1":"7.0","script_version":"1.02","2":"1.02","version_comment":"Better error handling","3":"Better error handling","package":"session_dialog.vim","4":"session_dialog.vim","src_id":"9749","5":"9749","creation_date":"1230929871","6":"1230929871"},{"0":"2464","vim_version":"7.0","1":"7.0","script_version":"1.01","2":"1.01","version_comment":"New option g:SessionConfirmOverwrite; new mapping ZL for :SessionList","3":"New option g:SessionConfirmOverwrite; new mapping ZL for :SessionList","package":"session_dialog.vim","4":"session_dialog.vim","src_id":"9638","5":"9638","creation_date":"1228787590","6":"1228787590"},{"0":"2464","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"session_dialog.vim","4":"session_dialog.vim","src_id":"9586","5":"9586","creation_date":"1227935890","6":"1227935890"}]},"2463":{"script_id":"2463","0":"2463","script_name":"kellys","1":"kellys","script_type":"color scheme","2":"color scheme","summary":"A colour scheme inspired by Kellys bicycles","3":"A colour scheme inspired by Kellys bicycles","description":"A colour scheme inspired by Kellys bicycles: a dark background with quite intense colours, mainly blue, orange and green. Pretty good contrast, but not so much as to hurt the eyes.\r\nA screenshot available at: http:\/\/img291.imageshack.us\/my.php?image=vimkellys03fd0.png.","4":"A colour scheme inspired by Kellys bicycles: a dark background with quite intense colours, mainly blue, orange and green. Pretty good contrast, but not so much as to hurt the eyes.\r\nA screenshot available at: http:\/\/img291.imageshack.us\/my.php?image=vimkellys03fd0.png.","install_details":"Place in your Vim colour schemes directory (probably ~\/.vim\/colors) for autoloading on startup and :source it or restart Vim, or just anywhere and :source it.","5":"Place in your Vim colour schemes directory (probably ~\/.vim\/colors) for autoloading on startup and :source it or restart Vim, or just anywhere and :source it.","first_name":"kamil","6":"kamil","last_name":"stachowski","7":"stachowski","releases":[{"0":"2463","vim_version":"7.3","1":"7.3","script_version":"0.4","2":"0.4","version_comment":"fixed 256-colour, improved php and TeX, added Conceal, added netrw, some minor modifications","3":"fixed 256-colour, improved php and TeX, added Conceal, added netrw, some minor modifications","package":"kellys.vim","4":"kellys.vim","src_id":"14726","5":"14726","creation_date":"1294702179","6":"1294702179"},{"0":"2463","vim_version":"7.0","1":"7.0","script_version":"0.3","2":"0.3","version_comment":"finished ada, haskell, html, lisp, pascal, php, python, ruby, scheme, sh, xml and vim\r\nchanged preproc to slightly darker\r\nchanged statement to bold\r\n","3":"finished ada, haskell, html, lisp, pascal, php, python, ruby, scheme, sh, xml and vim\r\nchanged preproc to slightly darker\r\nchanged statement to bold\r\n","package":"kellys.vim","4":"kellys.vim","src_id":"9626","5":"9626","creation_date":"1228649079","6":"1228649079"},{"0":"2463","vim_version":"6.0","1":"6.0","script_version":"0.2","2":"0.2","version_comment":"added support for 256-colour terminal\r\nadded diff*, pmenu* and wildmenu\r\nadded some cpp, java*, python*, some sh and ruby*\r\nremoved italic from comments and made them slightly lighter","3":"added support for 256-colour terminal\r\nadded diff*, pmenu* and wildmenu\r\nadded some cpp, java*, python*, some sh and ruby*\r\nremoved italic from comments and made them slightly lighter","package":"kellys.vim","4":"kellys.vim","src_id":"9598","5":"9598","creation_date":"1228217181","6":"1228217181"},{"0":"2463","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"kellys.vim","4":"kellys.vim","src_id":"9585","5":"9585","creation_date":"1227904988","6":"1227904988"}]},"2462":{"script_id":"2462","0":"2462","script_name":"Python Syntax Folding","1":"Python Syntax Folding","script_type":"syntax","2":"syntax","summary":"Python syntax file with support for folding functions\/classes","3":"Python syntax file with support for folding functions\/classes","description":"This python syntax file provides support for folding function\/class definitions. ","4":"This python syntax file provides support for folding function\/class definitions. ","install_details":"place the file into your ~\/.vim\/syntax\/ folder","5":"place the file into your ~\/.vim\/syntax\/ folder","first_name":"Samuel","6":"Samuel","last_name":"Hoffstaetter","7":"Hoffstaetter","releases":[{"0":"2462","vim_version":"5.7","1":"5.7","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"python.vim","4":"python.vim","src_id":"9584","5":"9584","creation_date":"1227894277","6":"1227894277"}]},"2461":{"script_id":"2461","0":"2461","script_name":"AutoTmpl","1":"AutoTmpl","script_type":"utility","2":"utility","summary":"Plugin for using templates when editing new files","3":"Plugin for using templates when editing new files","description":"This plugin has been uploaded twice by error and might be outdated, please go to vimscript #2460 to get the maintained version.","4":"This plugin has been uploaded twice by error and might be outdated, please go to vimscript #2460 to get the maintained version.","install_details":"","5":"","first_name":"Lluis","6":"Lluis","last_name":"Vilanova","7":"Vilanova","releases":[{"0":"2461","vim_version":"6.0","1":"6.0","script_version":"1","2":"1","version_comment":"Initial upload","3":"Initial upload","package":"AutoTmpl.tar.gz","4":"AutoTmpl.tar.gz","src_id":"9582","5":"9582","creation_date":"1227809872","6":"1227809872"}]},"2460":{"script_id":"2460","0":"2460","script_name":"AutoTmpl","1":"AutoTmpl","script_type":"utility","2":"utility","summary":"Plugin for using templates when editing new files","3":"Plugin for using templates when editing new files","description":"The purpose of this script is to automatically load predefined template files\r\nwhen editing new files.\r\n\r\nThe templates can contain fields that are dynamically filled in order to customize\r\nthem at creation time (e.g. date of creation).\r\n\r\nCurrently, templates are provided for:\r\n - C\r\n - C++\r\n - C\/C++ headers\r\n - Python\r\n - Shell scripts\r\n - Vim plugins\r\n\r\nThe plugins use some variables that can be defined in your .vimrc:\r\n - let g:author = \"your name\"\r\n - let g:email = \"your email\"\r\n - let g:footer = \"the footer you want vim to use for your files (e.g. tabstop=4 textwidth=100)\"\r\n\r\nPlease send me an email with any improvements you think are worth.","4":"The purpose of this script is to automatically load predefined template files\r\nwhen editing new files.\r\n\r\nThe templates can contain fields that are dynamically filled in order to customize\r\nthem at creation time (e.g. date of creation).\r\n\r\nCurrently, templates are provided for:\r\n - C\r\n - C++\r\n - C\/C++ headers\r\n - Python\r\n - Shell scripts\r\n - Vim plugins\r\n\r\nThe plugins use some variables that can be defined in your .vimrc:\r\n - let g:author = \"your name\"\r\n - let g:email = \"your email\"\r\n - let g:footer = \"the footer you want vim to use for your files (e.g. tabstop=4 textwidth=100)\"\r\n\r\nPlease send me an email with any improvements you think are worth.","install_details":"To install it for the first time, download the plugin and\r\ndecompress it into your local vim directory (~\/.vim).\r\n\r\nOnce installed you can update it with vimscript #642.\r\n\r\nIn order to update your help tags you have to run >\r\n        :helptags ~\/.vim\/doc\r\n<\r\n\r\nYou can see this help with >\r\n        help AutoTmpl\r\n>","5":"To install it for the first time, download the plugin and\r\ndecompress it into your local vim directory (~\/.vim).\r\n\r\nOnce installed you can update it with vimscript #642.\r\n\r\nIn order to update your help tags you have to run >\r\n        :helptags ~\/.vim\/doc\r\n<\r\n\r\nYou can see this help with >\r\n        help AutoTmpl\r\n>","first_name":"Lluis","6":"Lluis","last_name":"Vilanova","7":"Vilanova","releases":[{"0":"2460","vim_version":"6.0","1":"6.0","script_version":"1","2":"1","version_comment":"Initial upload","3":"Initial upload","package":"AutoTmpl.tar.gz","4":"AutoTmpl.tar.gz","src_id":"9581","5":"9581","creation_date":"1227809844","6":"1227809844"}]},"2459":{"script_id":"2459","0":"2459","script_name":"enzyme.vim","1":"enzyme.vim","script_type":"color scheme","2":"color scheme","summary":"A color scheme optimized for viewing in Terminal.app","3":"A color scheme optimized for viewing in Terminal.app","description":"After getting sick of unreadable color schemes because of OS X's Terminal.app color rendition I decided to make my own scheme. The focus is on providing readable combinations of colors.\r\n\r\nThis may also look okay in other terminals, but I haven't really tested it there so far.\r\n\r\nCurrently it does nothing special for Gvim.\r\n\r\nIf you would like to leave comments or make suggestions for this color scheme, please visit my blog: http:\/\/kamilkisiel.blogspot.com\/2008\/11\/enzymevim-terminalapp-friendly-color.html","4":"After getting sick of unreadable color schemes because of OS X's Terminal.app color rendition I decided to make my own scheme. The focus is on providing readable combinations of colors.\r\n\r\nThis may also look okay in other terminals, but I haven't really tested it there so far.\r\n\r\nCurrently it does nothing special for Gvim.\r\n\r\nIf you would like to leave comments or make suggestions for this color scheme, please visit my blog: http:\/\/kamilkisiel.blogspot.com\/2008\/11\/enzymevim-terminalapp-friendly-color.html","install_details":"To use, set a dark (black works well) background in Terminal.app and enable the \"Display ANSI colors\", \"Use bold fonts\", and \"Use bright colors for blod text\" options in the Settings dialog. \r\n\r\nPlace the script your '~\/.vim\/colors\/' directory and use ':colorscheme enzyme in Vim.\r\n\r\n\r\n","5":"To use, set a dark (black works well) background in Terminal.app and enable the \"Display ANSI colors\", \"Use bold fonts\", and \"Use bright colors for blod text\" options in the Settings dialog. \r\n\r\nPlace the script your '~\/.vim\/colors\/' directory and use ':colorscheme enzyme in Vim.\r\n\r\n\r\n","first_name":"Kamil","6":"Kamil","last_name":"Kisiel","7":"Kisiel","releases":[{"0":"2459","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"enzyme.vim","4":"enzyme.vim","src_id":"9575","5":"9575","creation_date":"1227742520","6":"1227742520"}]},"2458":{"script_id":"2458","0":"2458","script_name":"unibox","1":"unibox","script_type":"utility","2":"utility","summary":"Draws boxes in different line styles and in all languages","3":"Draws boxes in different line styles and in all languages","description":"The script draws line boxes in styles in various languages.\r\n\r\nYou can get all kinds of lines supported in your local system.  For Chinese, Japanese, and Korean (CJK), the program will be fully featured with various pre-defined lines.  Other encoding will have degraded lines.  For example, if you have not 3-dot line in your system, a solid line will be used.  In the worst case, characters (+,-,|) will be applied.\r\n\r\nIn case a visual selection cover an existing box, there are 2 modes for processing the intersection, unite mode and overwrite mode.  In unite mode, lines are joined at intersections. This is why the script is call unibox..\r\n\r\nKey mappings:\r\n\r\n    <leader>du    uses it after you change you encoding\r\n    <leader>d     the default draw mode, same as <leader>d1\r\n    <leader>d1    draws with thin lines\r\n    <leader>d2     with bold lines\r\n    <leader>d3     with 3-dot thin lines\r\n    <leader>d4     with 4-dot thin lines\r\n    <leader>d5     with double lines\r\n    <leader>d6     with 3-dot bold lines\r\n    <leader>dr     sam as <leader>dr1\r\n    <leader>dr1    with round corners and thin lines\r\n    <leader>dr3    with round corners and 3-dot thin lines\r\n    <leader>dr4    with round corners and 4-dot thin lines\r\n    <leader>d8     with round corners and 4-dot bold lines\r\n    <leader>dc    clear the box\r\n\r\n    <leader>dd    The followings correspond the above but in a overwrite mode\r\n    <leader>dd1   \r\n    <leader>dd2   \r\n    <leader>dd3   \r\n    <leader>dd4   \r\n    <leader>dd5   \r\n    <leader>dd6   \r\n    <leader>ddr   \r\n    <leader>ddr1  \r\n    <leader>ddr3  \r\n    <leader>ddr4  \r\n    <leader>dd8   \r\n    <leader>ddC  \r\n\r\nTips:\r\n\r\n1.Try the following if you encounter wierd lines:\r\n        set ambiwith=single\r\n  or   set ambiwith=double\r\n\r\n2.To change the encoding, use\r\n        set enc=...\r\n  and type\r\n        <leader>du\r\n  to reset the drawing system.\r\n","4":"The script draws line boxes in styles in various languages.\r\n\r\nYou can get all kinds of lines supported in your local system.  For Chinese, Japanese, and Korean (CJK), the program will be fully featured with various pre-defined lines.  Other encoding will have degraded lines.  For example, if you have not 3-dot line in your system, a solid line will be used.  In the worst case, characters (+,-,|) will be applied.\r\n\r\nIn case a visual selection cover an existing box, there are 2 modes for processing the intersection, unite mode and overwrite mode.  In unite mode, lines are joined at intersections. This is why the script is call unibox..\r\n\r\nKey mappings:\r\n\r\n    <leader>du    uses it after you change you encoding\r\n    <leader>d     the default draw mode, same as <leader>d1\r\n    <leader>d1    draws with thin lines\r\n    <leader>d2     with bold lines\r\n    <leader>d3     with 3-dot thin lines\r\n    <leader>d4     with 4-dot thin lines\r\n    <leader>d5     with double lines\r\n    <leader>d6     with 3-dot bold lines\r\n    <leader>dr     sam as <leader>dr1\r\n    <leader>dr1    with round corners and thin lines\r\n    <leader>dr3    with round corners and 3-dot thin lines\r\n    <leader>dr4    with round corners and 4-dot thin lines\r\n    <leader>d8     with round corners and 4-dot bold lines\r\n    <leader>dc    clear the box\r\n\r\n    <leader>dd    The followings correspond the above but in a overwrite mode\r\n    <leader>dd1   \r\n    <leader>dd2   \r\n    <leader>dd3   \r\n    <leader>dd4   \r\n    <leader>dd5   \r\n    <leader>dd6   \r\n    <leader>ddr   \r\n    <leader>ddr1  \r\n    <leader>ddr3  \r\n    <leader>ddr4  \r\n    <leader>dd8   \r\n    <leader>ddC  \r\n\r\nTips:\r\n\r\n1.Try the following if you encounter wierd lines:\r\n        set ambiwith=single\r\n  or   set ambiwith=double\r\n\r\n2.To change the encoding, use\r\n        set enc=...\r\n  and type\r\n        <leader>du\r\n  to reset the drawing system.\r\n","install_details":"Copy the file to your favorite directory and source it when you need it.\r\nFor example, in vim, use command:\r\n:so unibox.vim","5":"Copy the file to your favorite directory and source it when you need it.\r\nFor example, in vim, use command:\r\n:so unibox.vim","first_name":"Garrison","6":"Garrison","last_name":"Yu","7":"Yu","releases":[{"0":"2458","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"documents added","3":"documents added","package":"unibox.vim","4":"unibox.vim","src_id":"9570","5":"9570","creation_date":"1227682725","6":"1227682725"}]},"2457":{"script_id":"2457","0":"2457","script_name":"mty\\'s vimrc","1":"mty\\'s vimrc","script_type":"syntax","2":"syntax","summary":"just another vimrc","3":"just another vimrc","description":"It\\'s just my vimrc, it contains scripts I wrote, mostly, but also some stuff I found around the web...","4":"It\\'s just my vimrc, it contains scripts I wrote, mostly, but also some stuff I found around the web...","install_details":"","5":"","first_name":"mty","6":"mty","last_name":"lty","7":"lty","releases":[{"0":"2457","vim_version":"7.0","1":"7.0","script_version":"0.0001","2":"0.0001","version_comment":"Initial upload","3":"Initial upload","package":"vimrc","4":"vimrc","src_id":"9568","5":"9568","creation_date":"1227645002","6":"1227645002"}]},"2456":{"script_id":"2456","0":"2456","script_name":"test","1":"test","script_type":"syntax","2":"syntax","summary":"xzczc","3":"xzczc","description":"cxzccz","4":"cxzccz","install_details":"","5":"","first_name":"rits","6":"rits","last_name":"ranj","7":"ranj","releases":[{"0":"2456","vim_version":"6.0","1":"6.0","script_version":"2","2":"2","version_comment":"Initial upload","3":"Initial upload","package":"carrier.plist","4":"carrier.plist","src_id":"9553","5":"9553","creation_date":"1227521840","6":"1227521840"}]},"2455":{"script_id":"2455","0":"2455","script_name":"outputz","1":"outputz","script_type":"utility","2":"utility","summary":"outputz interface for Vim","3":"outputz interface for Vim","description":"*outputz* is a Vim plugin to provide the feature that the number of bytes you\r\ninputted will be automatically posted to outputz.com whenever a whole buffer\r\nis written to a file.\r\n\r\nNote that this is just a prototype.  The interface should be improved for the\r\nfuture.\r\n\r\nRequirements:\r\n- Vim 7.2 or later\r\n- curl - http:\/\/curl.haxx.se\/\r\n\r\nLatest version:\r\nhttp:\/\/github.com\/kana\/vim-outputz","4":"*outputz* is a Vim plugin to provide the feature that the number of bytes you\r\ninputted will be automatically posted to outputz.com whenever a whole buffer\r\nis written to a file.\r\n\r\nNote that this is just a prototype.  The interface should be improved for the\r\nfuture.\r\n\r\nRequirements:\r\n- Vim 7.2 or later\r\n- curl - http:\/\/curl.haxx.se\/\r\n\r\nLatest version:\r\nhttp:\/\/github.com\/kana\/vim-outputz","install_details":"...","5":"...","first_name":"Kana","6":"Kana","last_name":"Natsuno","7":"Natsuno","releases":[{"0":"2455","vim_version":"7.0","1":"7.0","script_version":"0.0.1","2":"0.0.1","version_comment":"- Replace g:outputz_uri with |g:outputz_uri_function|.","3":"- Replace g:outputz_uri with |g:outputz_uri_function|.","package":"vim-outputz-0.0.1.zip","4":"vim-outputz-0.0.1.zip","src_id":"9544","5":"9544","creation_date":"1227366004","6":"1227366004"},{"0":"2455","vim_version":"7.0","1":"7.0","script_version":"0.0.0","2":"0.0.0","version_comment":"Initial upload","3":"Initial upload","package":"vim-outputz-0.0.0.zip","4":"vim-outputz-0.0.0.zip","src_id":"9542","5":"9542","creation_date":"1227322018","6":"1227322018"}]},"2454":{"script_id":"2454","0":"2454","script_name":"google","1":"google","script_type":"color scheme","2":"color scheme","summary":"A colour scheme based on Google's","3":"A colour scheme based on Google's","description":"A colour scheme based on Google's. Much blue, a little green, all on a light background with high contrast.","4":"A colour scheme based on Google's. Much blue, a little green, all on a light background with high contrast.","install_details":"Place in your Vim colour schemes directory (probably ~\/.vim\/colors) for autoloading on startup and :source it or restart Vim, or just anywhere and :source it.","5":"Place in your Vim colour schemes directory (probably ~\/.vim\/colors) for autoloading on startup and :source it or restart Vim, or just anywhere and :source it.","first_name":"kamil","6":"kamil","last_name":"stachowski","7":"stachowski","releases":[{"0":"2454","vim_version":"6.0","1":"6.0","script_version":"0.2","2":"0.2","version_comment":"changed MatchParen to link to Type (thanks to Jarosław Mężyk)\r\nadded Diff","3":"changed MatchParen to link to Type (thanks to Jarosław Mężyk)\r\nadded Diff","package":"google.vim","4":"google.vim","src_id":"9579","5":"9579","creation_date":"1227780516","6":"1227780516"},{"0":"2454","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"google.vim","4":"google.vim","src_id":"9532","5":"9532","creation_date":"1227194188","6":"1227194188"}]},"2453":{"script_id":"2453","0":"2453","script_name":"eyapp","1":"eyapp","script_type":"syntax","2":"syntax","summary":"Syntax highlighting for Parse::Eyapp and Parse::Yapp","3":"Syntax highlighting for Parse::Eyapp and Parse::Yapp","description":"Parse::Eyapp and Parse::Yapp (see http:\/\/search.cpan.org\/dist\/Parse-Eyapp\/) are\r\nyacc-like parser generators for Perl. \r\nThe syntax file eyapp.vim provides syntax highlighting for the yapp and eyapp languages \r\n(see http:\/\/search.cpan.org\/dist\/Parse-Eyapp\/)","4":"Parse::Eyapp and Parse::Yapp (see http:\/\/search.cpan.org\/dist\/Parse-Eyapp\/) are\r\nyacc-like parser generators for Perl. \r\nThe syntax file eyapp.vim provides syntax highlighting for the yapp and eyapp languages \r\n(see http:\/\/search.cpan.org\/dist\/Parse-Eyapp\/)","install_details":"Just add to your ~\/.vim\/filetype the lines that associate *.eyp and *.yp files with the eyapp language:\r\n\r\n ~\/.vim$ cat filetype.vim\r\n\" my filetype file\r\nif exists(\"did_load_filetypes\")\r\nfinish\r\nendif\r\naugroup filetypedetect\r\n  \"eyapp and yapp programs\r\n  au BufRead,BufNewFile *.yp           setfiletype eyapp\r\n  au BufRead,BufNewFile *.eyp         setfiletype eyapp\r\naugroup END\r\n","5":"Just add to your ~\/.vim\/filetype the lines that associate *.eyp and *.yp files with the eyapp language:\r\n\r\n ~\/.vim$ cat filetype.vim\r\n\" my filetype file\r\nif exists(\"did_load_filetypes\")\r\nfinish\r\nendif\r\naugroup filetypedetect\r\n  \"eyapp and yapp programs\r\n  au BufRead,BufNewFile *.yp           setfiletype eyapp\r\n  au BufRead,BufNewFile *.eyp         setfiletype eyapp\r\naugroup END\r\n","first_name":"Casiano","6":"Casiano","last_name":"Rodriguez-Leon","7":"Rodriguez-Leon","releases":[{"0":"2453","vim_version":"6.0","1":"6.0","script_version":"2","2":"2","version_comment":"fixed bug in regexp for C comments","3":"fixed bug in regexp for C comments","package":"eyapp.vim","4":"eyapp.vim","src_id":"9613","5":"9613","creation_date":"1228468175","6":"1228468175"},{"0":"2453","vim_version":"6.0","1":"6.0","script_version":"1","2":"1","version_comment":"Initial upload","3":"Initial upload","package":"eyapp.vim","4":"eyapp.vim","src_id":"9530","5":"9530","creation_date":"1227170589","6":"1227170589"}]},"2452":{"script_id":"2452","0":"2452","script_name":"miko","1":"miko","script_type":"color scheme","2":"color scheme","summary":"Elegant blues and yellows on black","3":"Elegant blues and yellows on black","description":"Custom color scheme for 256 color terminals that I've personally used and tuned since I created it in February.  I'm a perfectionist when it comes to this kind of thing, and I've spent a LOT of time fine tuning the colors to be both functional and pleasing to the eye.\r\n\r\nDoes not currently support the gvim or instances of vim based in a GUI.","4":"Custom color scheme for 256 color terminals that I've personally used and tuned since I created it in February.  I'm a perfectionist when it comes to this kind of thing, and I've spent a LOT of time fine tuning the colors to be both functional and pleasing to the eye.\r\n\r\nDoes not currently support the gvim or instances of vim based in a GUI.","install_details":"Place miko.vim in your colors directory at ~\/.vim\/colors (may be different if using a non-linux platform).  Add the following lines to your ~\/.vimrc file to use this colorscheme by default on startup:\r\n\r\n:syntax on\r\n:colorscheme miko","5":"Place miko.vim in your colors directory at ~\/.vim\/colors (may be different if using a non-linux platform).  Add the following lines to your ~\/.vimrc file to use this colorscheme by default on startup:\r\n\r\n:syntax on\r\n:colorscheme miko","first_name":"Mike","6":"Mike","last_name":"Zazaian","7":"Zazaian","releases":[{"0":"2452","vim_version":"7.0","1":"7.0","script_version":"0.0.5","2":"0.0.5","version_comment":"* Reconciled all shades of yellow to a common, lighter shade.","3":"* Reconciled all shades of yellow to a common, lighter shade.","package":"miko.vim","4":"miko.vim","src_id":"10710","5":"10710","creation_date":"1243875503","6":"1243875503"},{"0":"2452","vim_version":"7.0","1":"7.0","script_version":"0.0.4","2":"0.0.4","version_comment":"* Updated #Comment color to a more pleasing, pale red color\r\n* Changed #PreProc colors to a brighter yellow to distinguish from constants, and give function definitions a more distinct apperarance.\r\n* Should be used against a dark gray or black BG.","3":"* Updated #Comment color to a more pleasing, pale red color\r\n* Changed #PreProc colors to a brighter yellow to distinguish from constants, and give function definitions a more distinct apperarance.\r\n* Should be used against a dark gray or black BG.","package":"miko.vim","4":"miko.vim","src_id":"10705","5":"10705","creation_date":"1243666470","6":"1243666470"},{"0":"2452","vim_version":"7.0","1":"7.0","script_version":"0.0.3","2":"0.0.3","version_comment":"Initial upload","3":"Initial upload","package":"miko.vim","4":"miko.vim","src_id":"9529","5":"9529","creation_date":"1227170189","6":"1227170189"}]},"2451":{"script_id":"2451","0":"2451","script_name":"nightsky","1":"nightsky","script_type":"color scheme","2":"color scheme","summary":"Black background, good usability.","3":"Black background, good usability.","description":"Based on northsky from Sergey Khorev which was recommended to me by Bram. Changed a few things to make it more pleasant and usable.","4":"Based on northsky from Sergey Khorev which was recommended to me by Bram. Changed a few things to make it more pleasant and usable.","install_details":"copy file to your ~\/.vim\/colors\/ or equivalent based on your OS.","5":"copy file to your ~\/.vim\/colors\/ or equivalent based on your OS.","first_name":"Ian","6":"Ian","last_name":"Kelling","7":"Kelling","releases":[{"0":"2451","vim_version":"7.0","1":"7.0","script_version":"1","2":"1","version_comment":"Initial upload","3":"Initial upload","package":"nightsky.vim","4":"nightsky.vim","src_id":"9526","5":"9526","creation_date":"1227120117","6":"1227120117"}]},"2450":{"script_id":"2450","0":"2450","script_name":"msdn_help.vim","1":"msdn_help.vim","script_type":"utility","2":"utility","summary":"Lookup MSDN help","3":"Lookup MSDN help","description":"This plugin provide display help text on dexplorer(MSDN help).\r\n'dexplorer.exe' process must be started in advance.\r\n\r\nRequirements:\r\n- Vim7.1 or later.\r\n- Python\r\nhttp:\/\/www.python.org\/download\/\r\n- Python Win32 Extension\r\nhttp:\/\/sourceforge.net\/project\/showfiles.php?group_id=78018\r\n\r\nKey mapping:\r\nIn normal mode\r\n<space>h  Search the word under the cursor.\r\nIn visual mode\r\n<space>h Search the text selected in visual mode.\r\n\r\n","4":"This plugin provide display help text on dexplorer(MSDN help).\r\n'dexplorer.exe' process must be started in advance.\r\n\r\nRequirements:\r\n- Vim7.1 or later.\r\n- Python\r\nhttp:\/\/www.python.org\/download\/\r\n- Python Win32 Extension\r\nhttp:\/\/sourceforge.net\/project\/showfiles.php?group_id=78018\r\n\r\nKey mapping:\r\nIn normal mode\r\n<space>h  Search the word under the cursor.\r\nIn visual mode\r\n<space>h Search the text selected in visual mode.\r\n\r\n","install_details":"Download msdn_help-0_0_1.zip, and extract your ~\/vimfiles directory.\r\n","5":"Download msdn_help-0_0_1.zip, and extract your ~\/vimfiles directory.\r\n","first_name":"John","6":"John","last_name":"Yanagiya","7":"Yanagiya","releases":[{"0":"2450","vim_version":"7.0","1":"7.0","script_version":"0.0.1","2":"0.0.1","version_comment":"Initial upload","3":"Initial upload","package":"msdn_help-0_0_1.zip","4":"msdn_help-0_0_1.zip","src_id":"9522","5":"9522","creation_date":"1227108805","6":"1227108805"}]},"2449":{"script_id":"2449","0":"2449","script_name":"sqlserver.vim","1":"sqlserver.vim","script_type":"syntax","2":"syntax","summary":"Syntax file for SQL Server 2005\/2008","3":"Syntax file for SQL Server 2005\/2008","description":"This is a syntax file for SQL Server 2005\/2008.  All TSQL and ODBC keywords are included, as well as a comprehensive list of functions, system variables, system stored procedures, server options, and future keywords (as defined by Microsoft).\r\n\r\nFor complete source history or to file a bug report\/issue (please use Wiki tab for this), please visit:\r\nhttp:\/\/github.com\/hoffstein\/vim-tsql\/tree\/master","4":"This is a syntax file for SQL Server 2005\/2008.  All TSQL and ODBC keywords are included, as well as a comprehensive list of functions, system variables, system stored procedures, server options, and future keywords (as defined by Microsoft).\r\n\r\nFor complete source history or to file a bug report\/issue (please use Wiki tab for this), please visit:\r\nhttp:\/\/github.com\/hoffstein\/vim-tsql\/tree\/master","install_details":"1)  Put the sqlserver.vim file in your syntax directory.\r\n\r\nOn Windows, this is $VIM\/vimfiles\/syntax or $HOME\/vimfiles\/syntax.\r\nOn Linux, this is $HOME\/.vim\/syntax or $VIM\/vimfiles\/syntax.\r\n\r\n2) If you want to make this your default syntax file for .sql files, add the following to your vimrc:\r\n    \r\n    let g:sql_type_default = \"sqlserver\"\r\n\r\n3) If you want to associate this syntax file with another extension, add the following to your vimrc (replace \"ext\" with the desired extension):\r\n\r\n    au BufNewFile,BufRead *.ext set filetype=sqlserver\r\n\r\n4) The file contains instructions for enabling\/disabling several highlighting options (for example, system stored procedures).  By default, all syntax is highlighted.","5":"1)  Put the sqlserver.vim file in your syntax directory.\r\n\r\nOn Windows, this is $VIM\/vimfiles\/syntax or $HOME\/vimfiles\/syntax.\r\nOn Linux, this is $HOME\/.vim\/syntax or $VIM\/vimfiles\/syntax.\r\n\r\n2) If you want to make this your default syntax file for .sql files, add the following to your vimrc:\r\n    \r\n    let g:sql_type_default = \"sqlserver\"\r\n\r\n3) If you want to associate this syntax file with another extension, add the following to your vimrc (replace \"ext\" with the desired extension):\r\n\r\n    au BufNewFile,BufRead *.ext set filetype=sqlserver\r\n\r\n4) The file contains instructions for enabling\/disabling several highlighting options (for example, system stored procedures).  By default, all syntax is highlighted.","first_name":"Benjamin","6":"Benjamin","last_name":"Hoffstein","7":"Hoffstein","releases":[{"0":"2449","vim_version":"6.0","1":"6.0","script_version":"1.0.2","2":"1.0.2","version_comment":"Corrected highlighting of DATEPART function parameters.","3":"Corrected highlighting of DATEPART function parameters.","package":"sqlserver.vim","4":"sqlserver.vim","src_id":"9810","5":"9810","creation_date":"1231866253","6":"1231866253"},{"0":"2449","vim_version":"6.0","1":"6.0","script_version":"1.0.1","2":"1.0.1","version_comment":"Added a few missing keywords (PERSISTED, OPENXML), reorganized source file with folding, and updated fileformat to unix.","3":"Added a few missing keywords (PERSISTED, OPENXML), reorganized source file with folding, and updated fileformat to unix.","package":"sqlserver.vim","4":"sqlserver.vim","src_id":"9611","5":"9611","creation_date":"1228424746","6":"1228424746"},{"0":"2449","vim_version":"6.0","1":"6.0","script_version":"1.0.0","2":"1.0.0","version_comment":"Initial upload","3":"Initial upload","package":"sqlserver.vim","4":"sqlserver.vim","src_id":"9519","5":"9519","creation_date":"1227044495","6":"1227044495"}]},"2448":{"script_id":"2448","0":"2448","script_name":"PylonsCommand","1":"PylonsCommand","script_type":"utility","2":"utility","summary":"Run Pylons' commands from Vim","3":"Run Pylons' commands from Vim","description":"Requirements: Linux(not tested on Windows), Pylons\r\nDescription:\r\nThis is plugin to invoke Pylons' commands from Vim\r\n\r\nA little theory now:\r\nDefault Pylons project looks like this:\r\n\r\n       MyProject\/\r\n               myproject\/\r\n               myproject.egg-info\/\r\n               data\/\r\n               docs\/\r\n               developement.ini\r\n               MANIFEST.in\r\n               README.txt\r\n               setup.cfg\r\n               setup.py\r\n               test.ini\r\n\r\n      Now, what is what?\r\n       g:PylonsProjectDir = path\/to\/MyProject\/\r\n       g:PylonsProjectName = myproject\/\r\n\r\n      To start using this plugin you have to 'open' Pylon project with:\r\n               :PylonsOpen path\/to\/MyProject\/myproject\/\r\n       if everything goes well you should see:\r\n               Project set: \/absolute\/path\/to\/MyProject\/myproject\r\n\r\n       Now you can use following functions:\r\n       PylonsOpen <dir> : open another project, current (if any) will be lost\r\n       PylonsServer [start|stop|restart] : start, stop, restart paster server\r\n       PylonsCreate [project|controller|template]:\r\n               project : Create new project TODO: not implemented yet\r\n               controller : Create new controler. It will as you for name.\r\n               template : Create new template. It will as you for name.\r\n               Note: you can use:\r\n                      PylonsCreate template\r\n                       'Template: path\/to\/template.mako'\r\n                       ['Template: path\/to\/template will' work the same]\r\n               This will create template.mako in\r\n                               \/absolute\/path\/to\/MyProject\/myproject\/tempates\/path\/to\/\r\n       PylonsPreview : this will open localhost:5000 with default browser (set in g:PylonsBrowser)\r\n\r\n Notes:\r\nI know that code can be buggy. It's my first vim-script.","4":"Requirements: Linux(not tested on Windows), Pylons\r\nDescription:\r\nThis is plugin to invoke Pylons' commands from Vim\r\n\r\nA little theory now:\r\nDefault Pylons project looks like this:\r\n\r\n       MyProject\/\r\n               myproject\/\r\n               myproject.egg-info\/\r\n               data\/\r\n               docs\/\r\n               developement.ini\r\n               MANIFEST.in\r\n               README.txt\r\n               setup.cfg\r\n               setup.py\r\n               test.ini\r\n\r\n      Now, what is what?\r\n       g:PylonsProjectDir = path\/to\/MyProject\/\r\n       g:PylonsProjectName = myproject\/\r\n\r\n      To start using this plugin you have to 'open' Pylon project with:\r\n               :PylonsOpen path\/to\/MyProject\/myproject\/\r\n       if everything goes well you should see:\r\n               Project set: \/absolute\/path\/to\/MyProject\/myproject\r\n\r\n       Now you can use following functions:\r\n       PylonsOpen <dir> : open another project, current (if any) will be lost\r\n       PylonsServer [start|stop|restart] : start, stop, restart paster server\r\n       PylonsCreate [project|controller|template]:\r\n               project : Create new project TODO: not implemented yet\r\n               controller : Create new controler. It will as you for name.\r\n               template : Create new template. It will as you for name.\r\n               Note: you can use:\r\n                      PylonsCreate template\r\n                       'Template: path\/to\/template.mako'\r\n                       ['Template: path\/to\/template will' work the same]\r\n               This will create template.mako in\r\n                               \/absolute\/path\/to\/MyProject\/myproject\/tempates\/path\/to\/\r\n       PylonsPreview : this will open localhost:5000 with default browser (set in g:PylonsBrowser)\r\n\r\n Notes:\r\nI know that code can be buggy. It's my first vim-script.","install_details":"copy pylonscommand.vim to ~\/.vim\/plugin\/\r\nand start using it with :PylonsOpen project\/dir\/and\/name","5":"copy pylonscommand.vim to ~\/.vim\/plugin\/\r\nand start using it with :PylonsOpen project\/dir\/and\/name","first_name":"Bartek","6":"Bartek","last_name":"Chaber","7":"Chaber","releases":[{"0":"2448","vim_version":"6.0","1":"6.0","script_version":"0.01","2":"0.01","version_comment":"Initial upload","3":"Initial upload","package":"pylonscommand.vim","4":"pylonscommand.vim","src_id":"9517","5":"9517","creation_date":"1227040846","6":"1227040846"}]},"2447":{"script_id":"2447","0":"2447","script_name":"Pago","1":"Pago","script_type":"ftplugin","2":"ftplugin","summary":"Powerful Screenplay Formatting","3":"Powerful Screenplay Formatting","description":"Pago is probably the most powerful terminal-based screenwriting script available for any platform, and allows the use of vim as a fully-functional piece of screenwriting software such as Final Draft or Celtx.  While some elements of the script are unstable, it undergoes daily testing and revision, becoming more mature as I use it every day for my own screenwriting projects.\r\n\r\nPLEASE PROVIDE ME WITH FEEDBACK if you use or test this software -- any comments or requested features will be given full consideration.  (zazaian (at) gmail (dot) com).  Your thoughts are essential to developing this program into a piece of software that best serves the open source community.\r\n\r\nOverview\r\n========\r\n* Supports all major formatting elements of a screenplay, based on both logical and commonly accepted conventions of the screenplay form.\r\n* Automatically enforces all boundaries within each screenplay element, ensuring proper formatting to the exact specifications of a screenplay.\r\n* Allows access to all six available screenplay ELEMENTS without any complex keyboard shortcuts or commands, using only the keys <Backspace>, <Tab>, <Enter>, <Up>, <Down>, <Left>, <Right>.\r\n* Allows easy cycling through blank screenplay elements using both the <Tab> and <Backspace> keys.\r\n\r\n  Features\r\n  ========\r\n  * Pressing TAB cycles through empty screenplay elements in the order:\r\n\r\n    ACTION --> DIALOGUE --> PARENTHETICAL --> CHARACTER --> TRANSITION --> ACTION\r\n\r\n    * Pressing <Tab> from a blank TRANSITION element will cycle back to the\r\n      beginning of the line, triggering a blank ACTION element.\r\n\r\n    * Parentheses are automatically inserted when calling a blank PARENTHETICAL\r\n      element.  Pressing <Tab> from within blank parentheses will automatically\r\n      delete the parentheses and jump to a blank CHARACTER element.\r\n\r\n    * A colon (\":\") is automatically inserted at the end of the line when an\r\n      TRANSITION element is called.  The cursor remains at the spot of the colon\r\n      when text is either entered or deleted.\r\n      \r\n      * Text typed within a TRANSITION element is automatically RIGHT-JUSTIFIED.\r\n\r\n      * Pressing <Enter> from a TRANSITION element jumps two lines down the page\r\n        and prompts a blank SCENE HEADING element.\r\n\r\n  * Pressing <Backspace> on an empty line cycles through empty screenplay elements\r\n    in the reverse order:\r\n\r\n    TRANSITION --> CHARACTER --> PARENTHETICAL --> DIALOGUE --> ACTION\r\n    --> END OF PREVIOUS ELEMENT\r\n\r\n    * Pressing <Backspace> from a blank line jumps to the end of the previous\r\n      element or, if the above two lines are blank, will create a blank ACTION\r\n      element two lines above the previous cursorline.\r\n    \r\n    * Pressing <Backspace> on a line with text will delete the character to the\r\n      left of the cursor.\r\n\r\n  * All text typed with a SCENE HEADING, CHARACTER, or TRANSITION element will be\r\n    automatically CAPITALIZED.\r\n\r\n  * To create a SCENE HEADING element, press enter while in a blank ACTION element.\r\n    The Cursorline will be HIGHLIGHTED and all text typed within the element will\r\n    be CAPITALIZED.\r\n\r\n  * While in a blank SCENE HEADING element:\r\n    * Press the <Space> bar to cycle through the common prefixes INT., EXT., and\r\n      INT.\/EXT.\r\n    * Press <Enter> to jump down two lines to a new, blank ACTION element.\r\n\r\n  * Active screenplay element is displayed in CAPS in the status bar.\r\n\r\n  * Page number is displayed in the status bar.  This estimates the number of pages\r\n    within your screeplay using a 56-line-per-page standard.\r\n\r\n  * Pressing <Up> in either INSERT or NORMAL modes jumps to the beginning of the\r\n    line above the cursorline.\r\n\r\n  * Pressing <Down> in either INSERT or NORMAL modes jumps to the end of the\r\n    line above the cursorline.\r\n\r\n  * Holding <Left> in either INSERT or NORMAL modes scrolls through to the\r\n    beginning of the current element, then jumps to the end of the previous\r\n    element.\r\n\r\n  * Holding <Right> in either INSERT or NORMAL modes scrolls through to the\r\n    end of the current element, then jumps to the beginning of the next\r\n    element.\r\n\r\n  * Typing text within a screenplay element such as DIALOGUE or ACTION will\r\n    automatically reformat the paragraph if text exceeds the preset end of the\r\n    line.  This improves upon use of the :tw (text width) and :wrap commands by\r\n    formatting text that is typed within a paragraph, rather than simply at the end\r\n    of it.\r\n\r\n\r\nPlanned Features\r\n==============\r\n* Easily output text file to a fully-formatted .PDF file.\r\n* Drop-Down lists for previously used:\r\n  * Character Names\r\n  * Character Parentheticals (O.S., O.C., V.O., CONT'D)\r\n  * Scene Headings\r\n* Integrated version control using the Bazaar version control system.\r\n  * Allows the use of a single file for a screenplay, rather than keeping multiple copies.\r\n  * Easily discern the differences between various writing sessions.\r\n  * Retain deleted scenes, lines and actions from various writing sessions.\r\n* Command-line abbreviations will simplify both version control and other useful features.\r\n* Optional syntax highlighting\r\n* Character and scene reports","4":"Pago is probably the most powerful terminal-based screenwriting script available for any platform, and allows the use of vim as a fully-functional piece of screenwriting software such as Final Draft or Celtx.  While some elements of the script are unstable, it undergoes daily testing and revision, becoming more mature as I use it every day for my own screenwriting projects.\r\n\r\nPLEASE PROVIDE ME WITH FEEDBACK if you use or test this software -- any comments or requested features will be given full consideration.  (zazaian (at) gmail (dot) com).  Your thoughts are essential to developing this program into a piece of software that best serves the open source community.\r\n\r\nOverview\r\n========\r\n* Supports all major formatting elements of a screenplay, based on both logical and commonly accepted conventions of the screenplay form.\r\n* Automatically enforces all boundaries within each screenplay element, ensuring proper formatting to the exact specifications of a screenplay.\r\n* Allows access to all six available screenplay ELEMENTS without any complex keyboard shortcuts or commands, using only the keys <Backspace>, <Tab>, <Enter>, <Up>, <Down>, <Left>, <Right>.\r\n* Allows easy cycling through blank screenplay elements using both the <Tab> and <Backspace> keys.\r\n\r\n  Features\r\n  ========\r\n  * Pressing TAB cycles through empty screenplay elements in the order:\r\n\r\n    ACTION --> DIALOGUE --> PARENTHETICAL --> CHARACTER --> TRANSITION --> ACTION\r\n\r\n    * Pressing <Tab> from a blank TRANSITION element will cycle back to the\r\n      beginning of the line, triggering a blank ACTION element.\r\n\r\n    * Parentheses are automatically inserted when calling a blank PARENTHETICAL\r\n      element.  Pressing <Tab> from within blank parentheses will automatically\r\n      delete the parentheses and jump to a blank CHARACTER element.\r\n\r\n    * A colon (\":\") is automatically inserted at the end of the line when an\r\n      TRANSITION element is called.  The cursor remains at the spot of the colon\r\n      when text is either entered or deleted.\r\n      \r\n      * Text typed within a TRANSITION element is automatically RIGHT-JUSTIFIED.\r\n\r\n      * Pressing <Enter> from a TRANSITION element jumps two lines down the page\r\n        and prompts a blank SCENE HEADING element.\r\n\r\n  * Pressing <Backspace> on an empty line cycles through empty screenplay elements\r\n    in the reverse order:\r\n\r\n    TRANSITION --> CHARACTER --> PARENTHETICAL --> DIALOGUE --> ACTION\r\n    --> END OF PREVIOUS ELEMENT\r\n\r\n    * Pressing <Backspace> from a blank line jumps to the end of the previous\r\n      element or, if the above two lines are blank, will create a blank ACTION\r\n      element two lines above the previous cursorline.\r\n    \r\n    * Pressing <Backspace> on a line with text will delete the character to the\r\n      left of the cursor.\r\n\r\n  * All text typed with a SCENE HEADING, CHARACTER, or TRANSITION element will be\r\n    automatically CAPITALIZED.\r\n\r\n  * To create a SCENE HEADING element, press enter while in a blank ACTION element.\r\n    The Cursorline will be HIGHLIGHTED and all text typed within the element will\r\n    be CAPITALIZED.\r\n\r\n  * While in a blank SCENE HEADING element:\r\n    * Press the <Space> bar to cycle through the common prefixes INT., EXT., and\r\n      INT.\/EXT.\r\n    * Press <Enter> to jump down two lines to a new, blank ACTION element.\r\n\r\n  * Active screenplay element is displayed in CAPS in the status bar.\r\n\r\n  * Page number is displayed in the status bar.  This estimates the number of pages\r\n    within your screeplay using a 56-line-per-page standard.\r\n\r\n  * Pressing <Up> in either INSERT or NORMAL modes jumps to the beginning of the\r\n    line above the cursorline.\r\n\r\n  * Pressing <Down> in either INSERT or NORMAL modes jumps to the end of the\r\n    line above the cursorline.\r\n\r\n  * Holding <Left> in either INSERT or NORMAL modes scrolls through to the\r\n    beginning of the current element, then jumps to the end of the previous\r\n    element.\r\n\r\n  * Holding <Right> in either INSERT or NORMAL modes scrolls through to the\r\n    end of the current element, then jumps to the beginning of the next\r\n    element.\r\n\r\n  * Typing text within a screenplay element such as DIALOGUE or ACTION will\r\n    automatically reformat the paragraph if text exceeds the preset end of the\r\n    line.  This improves upon use of the :tw (text width) and :wrap commands by\r\n    formatting text that is typed within a paragraph, rather than simply at the end\r\n    of it.\r\n\r\n\r\nPlanned Features\r\n==============\r\n* Easily output text file to a fully-formatted .PDF file.\r\n* Drop-Down lists for previously used:\r\n  * Character Names\r\n  * Character Parentheticals (O.S., O.C., V.O., CONT'D)\r\n  * Scene Headings\r\n* Integrated version control using the Bazaar version control system.\r\n  * Allows the use of a single file for a screenplay, rather than keeping multiple copies.\r\n  * Easily discern the differences between various writing sessions.\r\n  * Retain deleted scenes, lines and actions from various writing sessions.\r\n* Command-line abbreviations will simplify both version control and other useful features.\r\n* Optional syntax highlighting\r\n* Character and scene reports","install_details":"* Drop this file in your ${VIMRUNTIME}\/ftplugin\/ directory, which is likely located at ~\/.vim\/ftplugin\/ \r\n\r\n* add the following lines to your ~\/.vimrc file:\r\n  :filetype on\r\n  :filetype plugin on\r\n  :au BufRead,BufNewFile *.pago    set filetype=pago\r\n\r\n* Ensure the suffix the file you are editing is .pago.","5":"* Drop this file in your ${VIMRUNTIME}\/ftplugin\/ directory, which is likely located at ~\/.vim\/ftplugin\/ \r\n\r\n* add the following lines to your ~\/.vimrc file:\r\n  :filetype on\r\n  :filetype plugin on\r\n  :au BufRead,BufNewFile *.pago    set filetype=pago\r\n\r\n* Ensure the suffix the file you are editing is .pago.","first_name":"Mike","6":"Mike","last_name":"Zazaian","7":"Zazaian","releases":[{"0":"2447","vim_version":"7.0","1":"7.0","script_version":"0.2.31","2":"0.2.31","version_comment":"* Completed function wherein pressing Enter from a dialogue element creates a parenthetical\r\n    on the next line.  If it is left empty, pressing enter again deletes the empty brackets and\r\n    creates a new character element two lines down.","3":"* Completed function wherein pressing Enter from a dialogue element creates a parenthetical\r\n    on the next line.  If it is left empty, pressing enter again deletes the empty brackets and\r\n    creates a new character element two lines down.","package":"pago.vim","4":"pago.vim","src_id":"9807","5":"9807","creation_date":"1231830261","6":"1231830261"},{"0":"2447","vim_version":"6.0","1":"6.0","script_version":"0.2.29","2":"0.2.29","version_comment":"Fixed a number of bus related to auto-formatting.","3":"Fixed a number of bus related to auto-formatting.","package":"pago.vim","4":"pago.vim","src_id":"9797","5":"9797","creation_date":"1231655196","6":"1231655196"},{"0":"2447","vim_version":"7.0","1":"7.0","script_version":"0.2.25","2":"0.2.25","version_comment":"* Temporarily reverted to the gw}a style of paragraph formatting while the more elaborate formatting function is being tested and developed further.","3":"* Temporarily reverted to the gw}a style of paragraph formatting while the more elaborate formatting function is being tested and developed further.","package":"pago.vim","4":"pago.vim","src_id":"9567","5":"9567","creation_date":"1227627444","6":"1227627444"},{"0":"2447","vim_version":"7.0","1":"7.0","script_version":"0.2.24","2":"0.2.24","version_comment":"* Adjusted new auto-formatting function to accommodate backspacing.","3":"* Adjusted new auto-formatting function to accommodate backspacing.","package":"pago.vim","4":"pago.vim","src_id":"9566","5":"9566","creation_date":"1227625115","6":"1227625115"},{"0":"2447","vim_version":"7.0","1":"7.0","script_version":"0.2.23","2":"0.2.23","version_comment":"* Marked improvements in the auto-formatting function, using a filter of the fmt unix command.","3":"* Marked improvements in the auto-formatting function, using a filter of the fmt unix command.","package":"pago.vim","4":"pago.vim","src_id":"9565","5":"9565","creation_date":"1227624225","6":"1227624225"},{"0":"2447","vim_version":"7.0","1":"7.0","script_version":"0.2.22","2":"0.2.22","version_comment":"* Status bar is activated on script initialization.","3":"* Status bar is activated on script initialization.","package":"pago.vim","4":"pago.vim","src_id":"9562","5":"9562","creation_date":"1227566485","6":"1227566485"},{"0":"2447","vim_version":"7.0","1":"7.0","script_version":"0.2.21","2":"0.2.21","version_comment":"* Fixed small bug from version 0.2.19 that effected formatting of PARENTHETICAL elements.","3":"* Fixed small bug from version 0.2.19 that effected formatting of PARENTHETICAL elements.","package":"pago.vim","4":"pago.vim","src_id":"9561","5":"9561","creation_date":"1227565931","6":"1227565931"},{"0":"2447","vim_version":"7.0","1":"7.0","script_version":"0.2.20","2":"0.2.20","version_comment":"* <PageUp> and <PageDown> keys now detect the screenplay elements they land on as per the other direction and navigation keys.","3":"* <PageUp> and <PageDown> keys now detect the screenplay elements they land on as per the other direction and navigation keys.","package":"pago.vim","4":"pago.vim","src_id":"9560","5":"9560","creation_date":"1227565500","6":"1227565500"},{"0":"2447","vim_version":"7.0","1":"7.0","script_version":"0.2.19","2":"0.2.19","version_comment":"* Fixed bug that affected automatic formatting of PARENTHETICAL elements.","3":"* Fixed bug that affected automatic formatting of PARENTHETICAL elements.","package":"pago.vim","4":"pago.vim","src_id":"9559","5":"9559","creation_date":"1227562661","6":"1227562661"},{"0":"2447","vim_version":"7.0","1":"7.0","script_version":"0.2.18","2":"0.2.18","version_comment":"* Empty files now start properly indented on an ACTION element.","3":"* Empty files now start properly indented on an ACTION element.","package":"pago.vim","4":"pago.vim","src_id":"9550","5":"9550","creation_date":"1227431726","6":"1227431726"},{"0":"2447","vim_version":"7.0","1":"7.0","script_version":"0.2.17","2":"0.2.17","version_comment":"* Fixed major bug of auto-formatting functionality that considered all ELEMENTS not seperated by a black line to be the same paragraph.  Consequently, PARENTHETICAL elements would be formatted into a DIALOGUE element if dialogue was added above or below the PARENTHETICAL element.","3":"* Fixed major bug of auto-formatting functionality that considered all ELEMENTS not seperated by a black line to be the same paragraph.  Consequently, PARENTHETICAL elements would be formatted into a DIALOGUE element if dialogue was added above or below the PARENTHETICAL element.","package":"pago.vim","4":"pago.vim","src_id":"9548","5":"9548","creation_date":"1227414069","6":"1227414069"},{"0":"2447","vim_version":"7.0","1":"7.0","script_version":"0.2.16","2":"0.2.16","version_comment":"* Fixed bug in which current screenplay ELEMENT isn't established on script init.","3":"* Fixed bug in which current screenplay ELEMENT isn't established on script init.","package":"pago.vim","4":"pago.vim","src_id":"9547","5":"9547","creation_date":"1227391699","6":"1227391699"},{"0":"2447","vim_version":"7.0","1":"7.0","script_version":"0.2.15","2":"0.2.15","version_comment":"* Fixed issues with <Space> bar not shifting text to the left when used within the TRANSITION element.\r\n* Fixed issues with <Backspace> deleting all text when used within the TRANSITION element.","3":"* Fixed issues with <Space> bar not shifting text to the left when used within the TRANSITION element.\r\n* Fixed issues with <Backspace> deleting all text when used within the TRANSITION element.","package":"pago.vim","4":"pago.vim","src_id":"9541","5":"9541","creation_date":"1227306976","6":"1227306976"},{"0":"2447","vim_version":"7.0","1":"7.0","script_version":"0.2.14","2":"0.2.14","version_comment":"Fixed bug: pressing backspace from the beginning of an action line containing text now brings the text from that line to the previous line and automatically formats the ACTION element.  This action would previously backspace the text beyond the 10-space padding for ACTION elements. ","3":"Fixed bug: pressing backspace from the beginning of an action line containing text now brings the text from that line to the previous line and automatically formats the ACTION element.  This action would previously backspace the text beyond the 10-space padding for ACTION elements. ","package":"pago.vim","4":"pago.vim","src_id":"9533","5":"9533","creation_date":"1227231957","6":"1227231957"},{"0":"2447","vim_version":"7.2","1":"7.2","script_version":"0.2.13","2":"0.2.13","version_comment":"Initial upload","3":"Initial upload","package":"pago.vim","4":"pago.vim","src_id":"9515","5":"9515","creation_date":"1226973218","6":"1226973218"}]},"2446":{"script_id":"2446","0":"2446","script_name":"narrow","1":"narrow","script_type":"utility","2":"utility","summary":"Another plugin that emulates emacs' narrowing feature.","3":"Another plugin that emulates emacs' narrowing feature.","description":"This plugin allows you to zoom into regions of a buffer by hiding everything outside the selection. Global operations like global search\/replace etc. only apply to the selected region, until you widen the view again. This is useful when you have a very long function that doesn't fit the screen, and you end up in another function when searching whithout noticing (as an example). With this plugin you can zoom to that function and be sure that you keep inside it, no matter what you do.\r\n\r\nCommands:\r\n:Narrow (takes a region, zooms to it)\r\n:Widen (inserts the hidden parts again)\r\n\r\nNotes:\r\nAs the Narrow function actually deletes the hidden text from the buffer temporarily, this action can be undone manually by the user (using \"u\", \":undo\", \":earlier\", \"g-\", ...), which will break the :Widen function. For this reason, the 'u' key is remapped to a \"safe\" undo function. Still, there are other ways to undo the narrowing, so be careful!\r\nAlso, when in a narrowed buffer, the auto-command \"BufWriteCmd\" is set to a function that saves the whole file, so not only the narrowed region is saved on \".w\". Don't mess with this auto-command, or you'll probably lose data!","4":"This plugin allows you to zoom into regions of a buffer by hiding everything outside the selection. Global operations like global search\/replace etc. only apply to the selected region, until you widen the view again. This is useful when you have a very long function that doesn't fit the screen, and you end up in another function when searching whithout noticing (as an example). With this plugin you can zoom to that function and be sure that you keep inside it, no matter what you do.\r\n\r\nCommands:\r\n:Narrow (takes a region, zooms to it)\r\n:Widen (inserts the hidden parts again)\r\n\r\nNotes:\r\nAs the Narrow function actually deletes the hidden text from the buffer temporarily, this action can be undone manually by the user (using \"u\", \":undo\", \":earlier\", \"g-\", ...), which will break the :Widen function. For this reason, the 'u' key is remapped to a \"safe\" undo function. Still, there are other ways to undo the narrowing, so be careful!\r\nAlso, when in a narrowed buffer, the auto-command \"BufWriteCmd\" is set to a function that saves the whole file, so not only the narrowed region is saved on \".w\". Don't mess with this auto-command, or you'll probably lose data!","install_details":"Just copy the script in your plugin folder.\r\n\r\nThe latest version can also be checked out of the Git repository at http:\/\/github.com\/jkramer\/vim-narrow\/tree\/master","5":"Just copy the script in your plugin folder.\r\n\r\nThe latest version can also be checked out of the Git repository at http:\/\/github.com\/jkramer\/vim-narrow\/tree\/master","first_name":"Jonas","6":"Jonas","last_name":"Kramer","7":"Kramer","releases":[{"0":"2446","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"narrow.vim","4":"narrow.vim","src_id":"9513","5":"9513","creation_date":"1226918129","6":"1226918129"}]},"2445":{"script_id":"2445","0":"2445","script_name":"UpdateDNSSerial","1":"UpdateDNSSerial","script_type":"utility","2":"utility","summary":"Update automatically the serial of DNS Zone","3":"Update automatically the serial of DNS Zone","description":"This script help you to update automatically the serial of SOA when editing a DNS zone with vim. It find the serial, increment or update with the current time as : YYYYMMDDNU where YYYY=year, MM: month, DD:day, NU:number version.","4":"This script help you to update automatically the serial of SOA when editing a DNS zone with vim. It find the serial, increment or update with the current time as : YYYYMMDDNU where YYYY=year, MM: month, DD:day, NU:number version.","install_details":"Juste add the file in your .vim\/plugin directory. To apply it on your file type :call UpdateDNSSerial() or add a shortcut in .vimrc.","5":"Juste add the file in your .vim\/plugin directory. To apply it on your file type :call UpdateDNSSerial() or add a shortcut in .vimrc.","first_name":"Alexandre","6":"Alexandre","last_name":"MOREL","7":"MOREL","releases":[{"0":"2445","vim_version":"7.0","1":"7.0","script_version":"0.2","2":"0.2","version_comment":"A new version of this vim script contributed by Wouter D'Haeseleer that use regex in order to match the serial DNS.","3":"A new version of this vim script contributed by Wouter D'Haeseleer that use regex in order to match the serial DNS.","package":"UpdateDNSSerial.vim","4":"UpdateDNSSerial.vim","src_id":"15874","5":"15874","creation_date":"1307989807","6":"1307989807"},{"0":"2445","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"UpdateDNSSerial.vim","4":"UpdateDNSSerial.vim","src_id":"9512","5":"9512","creation_date":"1226856288","6":"1226856288"}]},"2444":{"script_id":"2444","0":"2444","script_name":"Download Vim Scripts as Cron Task","1":"Download Vim Scripts as Cron Task","script_type":"utility","2":"utility","summary":"Similar as GetLatestVimScripts, but this bash script can run as a cron task","3":"Similar as GetLatestVimScripts, but this bash script can run as a cron task","description":"Here is a simple bash script with similar function as \"GetLatestVimScripts\" plugin (vimscript#642):\r\n\r\n    (1) It will check whether a new version of local vim script are released, if it is available, automatically download it to assigned directory, otherwise, nothing will be done;\r\n    (2) It will update version information of the downloaded files into the list file.\r\n\r\n1. Why you need this script?\r\n --------------------------------------\r\nIn fact, core algorithm of this script is same with \"GetLatestVimScripts\". But the \"GetLatestVimScripts\" need to be run under vim platform, if you want it to be executed by some scheduler (for instance \"cron\" or \"at\") in background, it will not work!\r\n\r\nTry to launch a shell command as below:\r\n                               $ ex +\"GetLatestVimScripts\" &\r\nand what did you see? Yes, this background job cannot run, not even to run as a cron task.\r\n\r\nSo, if you are lazy to update your vim plugins manually, and need a program to execute it as a schedule, download and enjoy this script.\r\n\r\n2. Usage\r\n------------\r\nThis is a bash script:\r\n                         $ .\/downloadvimscripts [-o restore_dir] scripts_list_file\r\n\r\nNOTE:\r\n    (1) use option \"-o\"  to assign a directory to restore your vim scripts. If it is absent, vim scripts will be downloaded to the same directory of \"scripts_list_file\";\r\n    (2) \"scripts_list_file\" has same format of \"GetLatestVimScripts.dat\";\r\n    (3) it will check whether the restore_dir is writable before downloading.\r\n\r\n3. Format of \"scripts_list_file\"\r\n----------------------------------------\r\nAs mentioned above, \"scripts_list_file\" has same format as \"GetLatestVimScripts.dat\", it has three fields:\r\n                                    ScriptID SourceID ScriptName.\r\n\r\nwhere,\r\n    (1) ScriptID: you'll see it on the top of your browser in its \"Location:\" box whenever you click on the script at http:\/\/vim.sf.net\/;\r\n    (2) SourceID: start it off with a \"1\"; this script will download the file and keep this entry updated automatically;\r\n    (3) ScriptName: the name or title of the script (may have spaces, etc).\r\n\r\nI've provided an example of \"scripts_list_file\" in zip package, please research and reconfigure it for yourself.\r\n\r\n4. Dependency\r\n---------------------\r\nFor portability, assure these programs are installed in your system:\r\n    (1) bash (version >= 3.0)\r\n    (2) grep\r\n    (3) sed\r\n    (4) awk\r\n    (5) wget or curl","4":"Here is a simple bash script with similar function as \"GetLatestVimScripts\" plugin (vimscript#642):\r\n\r\n    (1) It will check whether a new version of local vim script are released, if it is available, automatically download it to assigned directory, otherwise, nothing will be done;\r\n    (2) It will update version information of the downloaded files into the list file.\r\n\r\n1. Why you need this script?\r\n --------------------------------------\r\nIn fact, core algorithm of this script is same with \"GetLatestVimScripts\". But the \"GetLatestVimScripts\" need to be run under vim platform, if you want it to be executed by some scheduler (for instance \"cron\" or \"at\") in background, it will not work!\r\n\r\nTry to launch a shell command as below:\r\n                               $ ex +\"GetLatestVimScripts\" &\r\nand what did you see? Yes, this background job cannot run, not even to run as a cron task.\r\n\r\nSo, if you are lazy to update your vim plugins manually, and need a program to execute it as a schedule, download and enjoy this script.\r\n\r\n2. Usage\r\n------------\r\nThis is a bash script:\r\n                         $ .\/downloadvimscripts [-o restore_dir] scripts_list_file\r\n\r\nNOTE:\r\n    (1) use option \"-o\"  to assign a directory to restore your vim scripts. If it is absent, vim scripts will be downloaded to the same directory of \"scripts_list_file\";\r\n    (2) \"scripts_list_file\" has same format of \"GetLatestVimScripts.dat\";\r\n    (3) it will check whether the restore_dir is writable before downloading.\r\n\r\n3. Format of \"scripts_list_file\"\r\n----------------------------------------\r\nAs mentioned above, \"scripts_list_file\" has same format as \"GetLatestVimScripts.dat\", it has three fields:\r\n                                    ScriptID SourceID ScriptName.\r\n\r\nwhere,\r\n    (1) ScriptID: you'll see it on the top of your browser in its \"Location:\" box whenever you click on the script at http:\/\/vim.sf.net\/;\r\n    (2) SourceID: start it off with a \"1\"; this script will download the file and keep this entry updated automatically;\r\n    (3) ScriptName: the name or title of the script (may have spaces, etc).\r\n\r\nI've provided an example of \"scripts_list_file\" in zip package, please research and reconfigure it for yourself.\r\n\r\n4. Dependency\r\n---------------------\r\nFor portability, assure these programs are installed in your system:\r\n    (1) bash (version >= 3.0)\r\n    (2) grep\r\n    (3) sed\r\n    (4) awk\r\n    (5) wget or curl","install_details":"Make it executable,  and create a crontab task to schedule it, for instance:\r\n                                 $ crontab -e\r\nthen add a new item:\r\n                                 0 20 1 * * path\/to\/downloadvimscripts -o restore_dir path\/to\/scripts_list","5":"Make it executable,  and create a crontab task to schedule it, for instance:\r\n                                 $ crontab -e\r\nthen add a new item:\r\n                                 0 20 1 * * path\/to\/downloadvimscripts -o restore_dir path\/to\/scripts_list","first_name":"Frank","6":"Frank","last_name":"Sun","7":"Sun","releases":[{"0":"2444","vim_version":"7.0","1":"7.0","script_version":"1.5.6","2":"1.5.6","version_comment":"- FIXED improper regular express of sed \r\n+ ADD dependency check function","3":"- FIXED improper regular express of sed \r\n+ ADD dependency check function","package":"downloadvimscripts_bash.zip","4":"downloadvimscripts_bash.zip","src_id":"13046","5":"13046","creation_date":"1274631663","6":"1274631663"},{"0":"2444","vim_version":"7.0","1":"7.0","script_version":"1.5.4","2":"1.5.4","version_comment":"+ ADD: show message to tell user how many packages were downloaded if their new version were found. \r\n- Fix BUG: make script run successfully even if it could not get source_id which caused by poor internet environment.","3":"+ ADD: show message to tell user how many packages were downloaded if their new version were found. \r\n- Fix BUG: make script run successfully even if it could not get source_id which caused by poor internet environment.","package":"downloadvimscripts_bash.zip","4":"downloadvimscripts_bash.zip","src_id":"10454","5":"10454","creation_date":"1240664755","6":"1240664755"},{"0":"2444","vim_version":"7.0","1":"7.0","script_version":"1.5.3","2":"1.5.3","version_comment":"-Fix a stupid bug in main body.","3":"-Fix a stupid bug in main body.","package":"downloadvimscripts_bash.zip","4":"downloadvimscripts_bash.zip","src_id":"9665","5":"9665","creation_date":"1229239349","6":"1229239349"},{"0":"2444","vim_version":"7.0","1":"7.0","script_version":"1.5.2","2":"1.5.2","version_comment":"＋ADD curl as optional download tool","3":"＋ADD curl as optional download tool","package":"downloadvimscripts.zip","4":"downloadvimscripts.zip","src_id":"9521","5":"9521","creation_date":"1227100880","6":"1227100880"},{"0":"2444","vim_version":"7.0","1":"7.0","script_version":"1.5","2":"1.5","version_comment":"Initial upload","3":"Initial upload","package":"downloadvimscripts_bash.zip","4":"downloadvimscripts_bash.zip","src_id":"9508","5":"9508","creation_date":"1226744343","6":"1226744343"}]},"2443":{"script_id":"2443","0":"2443","script_name":"Python Documentation","1":"Python Documentation","script_type":"ftplugin","2":"ftplugin","summary":"Python Documentation in Vim","3":"Python Documentation in Vim","description":"Shows Python documentation inside Vim either use the function :Pyhelp module, OR select the module in visual mode and then either use the map pw or the function :PyHelp. \r\n\r\nCurrently only works for stuff like os.path.abspath (complete modules not as variables) for example doing g = os.path and then trying to find the documentation for g.abspath won't work. So in the future I'd like that to work. ","4":"Shows Python documentation inside Vim either use the function :Pyhelp module, OR select the module in visual mode and then either use the map pw or the function :PyHelp. \r\n\r\nCurrently only works for stuff like os.path.abspath (complete modules not as variables) for example doing g = os.path and then trying to find the documentation for g.abspath won't work. So in the future I'd like that to work. ","install_details":"Move to your ~\/.vim\/ftplugin\/python or ~\/.vim\/plugin if you want it loaded for all filetypes\/modes.","5":"Move to your ~\/.vim\/ftplugin\/python or ~\/.vim\/plugin if you want it loaded for all filetypes\/modes.","first_name":"Travis","6":"Travis","last_name":"Jeffery","7":"Jeffery","releases":[{"0":"2443","vim_version":"7.0","1":"7.0","script_version":"2.0","2":"2.0","version_comment":"Complete rewrite. Now works by doing K while the cursor is over stuff like \"\\n\".join(string), or even when you create a variable ie my_str = \"\\n\".join(string) and then putting the cursor over s and doing K\r\n","3":"Complete rewrite. Now works by doing K while the cursor is over stuff like \"\\n\".join(string), or even when you create a variable ie my_str = \"\\n\".join(string) and then putting the cursor over s and doing K\r\n","package":"pyhelp.vim","4":"pyhelp.vim","src_id":"9658","5":"9658","creation_date":"1229136047","6":"1229136047"},{"0":"2443","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"pyhelp.vim","4":"pyhelp.vim","src_id":"9507","5":"9507","creation_date":"1226739635","6":"1226739635"}]},"2442":{"script_id":"2442","0":"2442","script_name":"VimLocalHistory","1":"VimLocalHistory","script_type":"utility","2":"utility","summary":"Automatic backup and poor man's revision control.","3":"Automatic backup and poor man's revision control.","description":"VLH automatically saves buffers on write using git.  This provides a convenient, automatic backup system of, e.g. files in \/etc that are modified, as well as a poor man's \"local history\" (a l\u00c3\u00a1 the eclipse feature with the same name).\r\n\r\nFeedback, bug reports and suggestions gratefully accepted at <vlh@hjdivad.com>.\r\n\r\n\r\nTo use, install, configure g:vlh_repository_dir and then use vim normally.  Every time you write a buffer whose path is on the local filesystem, a copy is saved in a git repository.\r\n\r\nYou can open, diff or restore older versions of files with the commands VLHOpen, VLHDiff and VLHReplace.\r\n\r\nsource code is available from github at http:\/\/github.com\/hjdivad\/vimlocalhistory\/tree\/master","4":"VLH automatically saves buffers on write using git.  This provides a convenient, automatic backup system of, e.g. files in \/etc that are modified, as well as a poor man's \"local history\" (a l\u00c3\u00a1 the eclipse feature with the same name).\r\n\r\nFeedback, bug reports and suggestions gratefully accepted at <vlh@hjdivad.com>.\r\n\r\n\r\nTo use, install, configure g:vlh_repository_dir and then use vim normally.  Every time you write a buffer whose path is on the local filesystem, a copy is saved in a git repository.\r\n\r\nYou can open, diff or restore older versions of files with the commands VLHOpen, VLHDiff and VLHReplace.\r\n\r\nsource code is available from github at http:\/\/github.com\/hjdivad\/vimlocalhistory\/tree\/master","install_details":"To install from a tarball:\r\n\r\n\tAfter ensuring that you meet the requirements, copy the contents of\r\n\tplugin to user-specific vim plugin directory, probably ~\/.vim\/plugin\/\r\n\r\n\tTo install documentation, copy README (this file) to your vim\r\n\tdocumentations directory, such as ~\/.vim\/doc\/vlh.txt.  After copying\r\n\tthe documentation, execute \":helptags ~\/.vim\/doc\" from within vim to\r\n\tmake the documentation accessible.\r\n\r\nTo install from source:\r\n\r\n\tInstall the requirements, additionally installing rake version 0.8.1\r\n\tor higher, and then execute\r\n\r\n\t\trake install\r\n\r\n\twhich will install the plugin and documentation.\r\n\r\n\r\nOnce VLH is installed, make sure to edit your ~\/.vimrc to include\r\n\r\n\tlet g:vlh_repository_dir = \"\/path\/where\/youd\/like\/to\/store\/localhistory\"\r\n\r\nI suggest using ~\/.vim\/localhistory.\r\n\r\n","5":"To install from a tarball:\r\n\r\n\tAfter ensuring that you meet the requirements, copy the contents of\r\n\tplugin to user-specific vim plugin directory, probably ~\/.vim\/plugin\/\r\n\r\n\tTo install documentation, copy README (this file) to your vim\r\n\tdocumentations directory, such as ~\/.vim\/doc\/vlh.txt.  After copying\r\n\tthe documentation, execute \":helptags ~\/.vim\/doc\" from within vim to\r\n\tmake the documentation accessible.\r\n\r\nTo install from source:\r\n\r\n\tInstall the requirements, additionally installing rake version 0.8.1\r\n\tor higher, and then execute\r\n\r\n\t\trake install\r\n\r\n\twhich will install the plugin and documentation.\r\n\r\n\r\nOnce VLH is installed, make sure to edit your ~\/.vimrc to include\r\n\r\n\tlet g:vlh_repository_dir = \"\/path\/where\/youd\/like\/to\/store\/localhistory\"\r\n\r\nI suggest using ~\/.vim\/localhistory.\r\n\r\n","first_name":"David","6":"David","last_name":"JH","7":"JH","releases":[{"0":"2442","vim_version":"7.0","1":"7.0","script_version":"0.2","2":"0.2","version_comment":"Initial upload","3":"Initial upload","package":"vimlocalhistory-0.2.tar.gz","4":"vimlocalhistory-0.2.tar.gz","src_id":"9505","5":"9505","creation_date":"1226722119","6":"1226722119"}]},"2441":{"script_id":"2441","0":"2441","script_name":"pyflakes.vim","1":"pyflakes.vim","script_type":"ftplugin","2":"ftplugin","summary":"PyFlakes on-the-fly Python code checking","3":"PyFlakes on-the-fly Python code checking","description":"like\/use\/enjoy\/need\/jonesfor pyflakes.vim? donate a little cash here to help me keep improving it: http:\/\/bit.ly\/gp4FCA\r\n\r\nIMPORTANT: Your vim must have Python 2.5, at least. Enter \":python import sys; print sys.version\" to see which version you have.  The newest version of Vim, 7.3, comes bundled with Python 2.7 support.\r\n\r\npyflakes-vim highlights common Python errors like misspelling a variable name on the fly. It also warns about unused imports, redefined functions, etc.\r\n\r\nThis plugin is fast enough that it registers itself with vim hooks for leaving insert mode and saving a buffer, so that the warnings are always up to date. See pyflakes.vim if you want to change this behavior.\r\n\r\nNOTES:\r\n * an improved pyflakes module is INCLUDED with this plugin, so you don't need to install it separately\r\n * quickfix entries are created for each error, so you can use commands like :cc to jump to errors.\r\n * this plugin uses the SpellBad highlight to show errors. if you'd like to change the color or style of this highlight, you can do something like this in your .vimrc:\r\n\r\n      if has(\"gui_running\") \r\n          highlight SpellBad term=underline gui=undercurl guisp=Orange \r\n      endif \r\n\r\nTo stay up on development, you can watch the public repos at\r\n\r\nhttp:\/\/github.com\/kevinw\/pyflakes-vim\r\nhttp:\/\/github.com\/kevinw\/pyflakes\r\n\r\nKNOWN ISSUES\r\n\r\n- The highlighting for syntax errors is often way off, and results in no other errors being detected.\r\n- In Python 2.5, typing a with statement before you have from __future__ import with results in a vim error\r\n","4":"like\/use\/enjoy\/need\/jonesfor pyflakes.vim? donate a little cash here to help me keep improving it: http:\/\/bit.ly\/gp4FCA\r\n\r\nIMPORTANT: Your vim must have Python 2.5, at least. Enter \":python import sys; print sys.version\" to see which version you have.  The newest version of Vim, 7.3, comes bundled with Python 2.7 support.\r\n\r\npyflakes-vim highlights common Python errors like misspelling a variable name on the fly. It also warns about unused imports, redefined functions, etc.\r\n\r\nThis plugin is fast enough that it registers itself with vim hooks for leaving insert mode and saving a buffer, so that the warnings are always up to date. See pyflakes.vim if you want to change this behavior.\r\n\r\nNOTES:\r\n * an improved pyflakes module is INCLUDED with this plugin, so you don't need to install it separately\r\n * quickfix entries are created for each error, so you can use commands like :cc to jump to errors.\r\n * this plugin uses the SpellBad highlight to show errors. if you'd like to change the color or style of this highlight, you can do something like this in your .vimrc:\r\n\r\n      if has(\"gui_running\") \r\n          highlight SpellBad term=underline gui=undercurl guisp=Orange \r\n      endif \r\n\r\nTo stay up on development, you can watch the public repos at\r\n\r\nhttp:\/\/github.com\/kevinw\/pyflakes-vim\r\nhttp:\/\/github.com\/kevinw\/pyflakes\r\n\r\nKNOWN ISSUES\r\n\r\n- The highlighting for syntax errors is often way off, and results in no other errors being detected.\r\n- In Python 2.5, typing a with statement before you have from __future__ import with results in a vim error\r\n","install_details":"1. Make sure your vimrc has \"filetype plugin indent on\" so that pyflake-vim's ftplugin files are loaded automatically when you open a Python buffer.\r\n2. Drop extracted files in ~\/.vim\/ftplugin\/python.\r\n3. That's it!\r\n\r\nSee the README for more info.\r\n","5":"1. Make sure your vimrc has \"filetype plugin indent on\" so that pyflake-vim's ftplugin files are loaded automatically when you open a Python buffer.\r\n2. Drop extracted files in ~\/.vim\/ftplugin\/python.\r\n3. That's it!\r\n\r\nSee the README for more info.\r\n","first_name":"@kevinwatters","6":"@kevinwatters","last_name":" ","7":" ","releases":[{"0":"2441","vim_version":"7.0","1":"7.0","script_version":"3.01","2":"3.01","version_comment":"Add __file__ as an automatic builtin.\r\n\r\nhttps:\/\/github.com\/kevinw\/pyflakes-vim\/commit\/5dc4416f6434fd0db12d21b6c1f4d0764c8757fe\r\n\r\nMove pyflakes.vim and pyflakes library into ftplugin\/python for easier pathogen installation.\r\n\r\nhttps:\/\/github.com\/kevinw\/pyflakes-vim\/commit\/086d5e1d5f87f7cdd0588f8149bf08115a8ae229","3":"Add __file__ as an automatic builtin.\r\n\r\nhttps:\/\/github.com\/kevinw\/pyflakes-vim\/commit\/5dc4416f6434fd0db12d21b6c1f4d0764c8757fe\r\n\r\nMove pyflakes.vim and pyflakes library into ftplugin\/python for easier pathogen installation.\r\n\r\nhttps:\/\/github.com\/kevinw\/pyflakes-vim\/commit\/086d5e1d5f87f7cdd0588f8149bf08115a8ae229","package":"pyflakes-vim.zip","4":"pyflakes-vim.zip","src_id":"14403","5":"14403","creation_date":"1291133695","6":"1291133695"},{"0":"2441","vim_version":"7.0","1":"7.0","script_version":"3.0","2":"3.0","version_comment":"Upgraded the included pyflakes module to trunk r17946 from http:\/\/divmod.org\/trac\/wiki\/DivmodPyflakes, which adds support for Python 2.7 constructs like set comprehensions and dict comprehensions.  Modified pyflakes 0.4.0 to retain column information.\r\n\r\nModified pyflakes.vim to be compatible with \"stock\" PyFlakes.\r\n\r\nChanges in pyflakes.vim: https:\/\/github.com\/kevinw\/pyflakes-vim\/commit\/8a7e19b6578b0986cb7a88a6c10d6cd907af2057\r\n\r\nChanges to stock PyFlakes 0.4.0: https:\/\/github.com\/kevinw\/pyflakes\/commit\/8f62656c96b7cf66b7ad6cac0d9e3881e55f389f#","3":"Upgraded the included pyflakes module to trunk r17946 from http:\/\/divmod.org\/trac\/wiki\/DivmodPyflakes, which adds support for Python 2.7 constructs like set comprehensions and dict comprehensions.  Modified pyflakes 0.4.0 to retain column information.\r\n\r\nModified pyflakes.vim to be compatible with \"stock\" PyFlakes.\r\n\r\nChanges in pyflakes.vim: https:\/\/github.com\/kevinw\/pyflakes-vim\/commit\/8a7e19b6578b0986cb7a88a6c10d6cd907af2057\r\n\r\nChanges to stock PyFlakes 0.4.0: https:\/\/github.com\/kevinw\/pyflakes\/commit\/8f62656c96b7cf66b7ad6cac0d9e3881e55f389f#","package":"pyflakes-vim.zip","4":"pyflakes-vim.zip","src_id":"14288","5":"14288","creation_date":"1290023403","6":"1290023403"},{"0":"2441","vim_version":"7.0","1":"7.0","script_version":"2.02","2":"2.02","version_comment":"Avoid a \"Press ENTER\" prompt when showing long error messages in narrow windows by truncating them to the number of columns. \r\n\r\nhttps:\/\/github.com\/kevinw\/pyflakes-vim\/commit\/ddeb0bf2d7db7916a62339f42c18c7a12468cd37","3":"Avoid a \"Press ENTER\" prompt when showing long error messages in narrow windows by truncating them to the number of columns. \r\n\r\nhttps:\/\/github.com\/kevinw\/pyflakes-vim\/commit\/ddeb0bf2d7db7916a62339f42c18c7a12468cd37","package":"pyflakes-vim.zip","4":"pyflakes-vim.zip","src_id":"14215","5":"14215","creation_date":"1289322024","6":"1289322024"},{"0":"2441","vim_version":"7.0","1":"7.0","script_version":"2.01","2":"2.01","version_comment":"Add configuration option g:pyflakes_use_quickfix. Add\r\n\r\nlet g:pyflakes_use_quickfix = 0\r\n\r\nto disable quickfix support.\r\n\r\nhttp:\/\/github.com\/kevinw\/pyflakes-vim\/commit\/10fb7c382ce94470ae47848d1ac84925381c036f","3":"Add configuration option g:pyflakes_use_quickfix. Add\r\n\r\nlet g:pyflakes_use_quickfix = 0\r\n\r\nto disable quickfix support.\r\n\r\nhttp:\/\/github.com\/kevinw\/pyflakes-vim\/commit\/10fb7c382ce94470ae47848d1ac84925381c036f","package":"pyflakes-vim.zip","4":"pyflakes-vim.zip","src_id":"14045","5":"14045","creation_date":"1286895642","6":"1286895642"},{"0":"2441","vim_version":"7.0","1":"7.0","script_version":"2.0","2":"2.0","version_comment":"Add quickfix support! Thanks Phui Hock.\r\n\r\nYou can now use quickfix commands like :cc to jump to errors.\r\n\r\nhttp:\/\/github.com\/kevinw\/pyflakes-vim\/commit\/64ebcffe3de49fe34ca12b11292b792dc323709f","3":"Add quickfix support! Thanks Phui Hock.\r\n\r\nYou can now use quickfix commands like :cc to jump to errors.\r\n\r\nhttp:\/\/github.com\/kevinw\/pyflakes-vim\/commit\/64ebcffe3de49fe34ca12b11292b792dc323709f","package":"pyflakes-vim.zip","4":"pyflakes-vim.zip","src_id":"13378","5":"13378","creation_date":"1279744439","6":"1279744439"},{"0":"2441","vim_version":"7.0","1":"7.0","script_version":"1.64","2":"1.64","version_comment":"Do not decode source code encoding line and the lines preceed it, if found.\r\n\r\nThanks phuihock.\r\n\r\nhttp:\/\/github.com\/kevinw\/pyflakes-vim\/commit\/1dffdbe91034f7a2bb6a16efe43d9bd9a466d11a","3":"Do not decode source code encoding line and the lines preceed it, if found.\r\n\r\nThanks phuihock.\r\n\r\nhttp:\/\/github.com\/kevinw\/pyflakes-vim\/commit\/1dffdbe91034f7a2bb6a16efe43d9bd9a466d11a","package":"pyflakes-vim.zip","4":"pyflakes-vim.zip","src_id":"13300","5":"13300","creation_date":"1278516488","6":"1278516488"},{"0":"2441","vim_version":"7.0","1":"7.0","script_version":"1.63","2":"1.63","version_comment":"Don't warn about duplicate functions with property decorators @prop.setter and @prop.deleter.","3":"Don't warn about duplicate functions with property decorators @prop.setter and @prop.deleter.","package":"pyflakes-vim.zip","4":"pyflakes-vim.zip","src_id":"13229","5":"13229","creation_date":"1277142950","6":"1277142950"},{"0":"2441","vim_version":"7.0","1":"7.0","script_version":"1.62","2":"1.62","version_comment":"Minor 2.5 compatibility fix.","3":"Minor 2.5 compatibility fix.","package":"pyflakes-vim.zip","4":"pyflakes-vim.zip","src_id":"13208","5":"13208","creation_date":"1276788859","6":"1276788859"},{"0":"2441","vim_version":"6.0","1":"6.0","script_version":"1.61","2":"1.61","version_comment":"Don't miss class decorators when walking the AST.","3":"Don't miss class decorators when walking the AST.","package":"pyflakes-vim.zip","4":"pyflakes-vim.zip","src_id":"13200","5":"13200","creation_date":"1276722628","6":"1276722628"},{"0":"2441","vim_version":"7.0","1":"7.0","script_version":"1.60","2":"1.60","version_comment":"Show a clear error message if vim was compiled without Python, or with a version of Python older than 2.5.\r\n\r\nhttp:\/\/github.com\/kevinw\/pyflakes-vim\/commit\/5eaf3bc1d7508da2994657c4f77458f4064d26e2","3":"Show a clear error message if vim was compiled without Python, or with a version of Python older than 2.5.\r\n\r\nhttp:\/\/github.com\/kevinw\/pyflakes-vim\/commit\/5eaf3bc1d7508da2994657c4f77458f4064d26e2","package":"pyflakes-vim.zip","4":"pyflakes-vim.zip","src_id":"12763","5":"12763","creation_date":"1270151727","6":"1270151727"},{"0":"2441","vim_version":"7.0","1":"7.0","script_version":"1.59","2":"1.59","version_comment":"Minor fix for an exception when opening files.\r\n\r\nhttp:\/\/github.com\/kevinw\/pyflakes-vim\/commit\/783b3aa3de1fddb082f0810300bac5a831a97941","3":"Minor fix for an exception when opening files.\r\n\r\nhttp:\/\/github.com\/kevinw\/pyflakes-vim\/commit\/783b3aa3de1fddb082f0810300bac5a831a97941","package":"pyflakes-vim.zip","4":"pyflakes-vim.zip","src_id":"12555","5":"12555","creation_date":"1267728765","6":"1267728765"},{"0":"2441","vim_version":"7.0","1":"7.0","script_version":"1.58","2":"1.58","version_comment":"Fix for 1.57 file encoding exception.","3":"Fix for 1.57 file encoding exception.","package":"pyflakes-vim.zip","4":"pyflakes-vim.zip","src_id":"12009","5":"12009","creation_date":"1262617452","6":"1262617452"},{"0":"2441","vim_version":"6.0","1":"6.0","script_version":"1.57","2":"1.57","version_comment":"Fixes http:\/\/github.com\/kevinw\/pyflakes-vim\/issues\/#issue\/7 and http:\/\/github.com\/kevinw\/pyflakes-vim\/issues\/#issue\/8\r\n\r\nFiles in unusual encodings should open correctly now.\r\nFiles ending with a trailing comment and no newline should also compile correctly now.","3":"Fixes http:\/\/github.com\/kevinw\/pyflakes-vim\/issues\/#issue\/7 and http:\/\/github.com\/kevinw\/pyflakes-vim\/issues\/#issue\/8\r\n\r\nFiles in unusual encodings should open correctly now.\r\nFiles ending with a trailing comment and no newline should also compile correctly now.","package":"pyflakes-vim.zip","4":"pyflakes-vim.zip","src_id":"11978","5":"11978","creation_date":"1262060490","6":"1262060490"},{"0":"2441","vim_version":"7.0","1":"7.0","script_version":"1.56","2":"1.56","version_comment":"http:\/\/github.com\/kevinw\/pyflakes-vim\/commit\/f12c0881f83964e35b2d3ad2299d111cec53dd9f\r\n\r\nFixes http:\/\/github.com\/kevinw\/pyflakes\/issues#issue\/1\r\n\r\nApparently CursorMoved can get called early, before RunPyflakes has run. \r\nIf this happens, just return.\r\n\r\nThanks EnTeQuAk.","3":"http:\/\/github.com\/kevinw\/pyflakes-vim\/commit\/f12c0881f83964e35b2d3ad2299d111cec53dd9f\r\n\r\nFixes http:\/\/github.com\/kevinw\/pyflakes\/issues#issue\/1\r\n\r\nApparently CursorMoved can get called early, before RunPyflakes has run. \r\nIf this happens, just return.\r\n\r\nThanks EnTeQuAk.","package":"pyflakes-vim.zip","4":"pyflakes-vim.zip","src_id":"11524","5":"11524","creation_date":"1255439904","6":"1255439904"},{"0":"2441","vim_version":"7.0","1":"7.0","script_version":"1.55","2":"1.55","version_comment":"http:\/\/github.com\/kevinw\/pyflakes-vim\/commit\/083bc2e65649a9cf10a7c1bcd22151a4083ddeb7\r\n\r\nHighlight the whole line for SyntaxErrors.","3":"http:\/\/github.com\/kevinw\/pyflakes-vim\/commit\/083bc2e65649a9cf10a7c1bcd22151a4083ddeb7\r\n\r\nHighlight the whole line for SyntaxErrors.","package":"pyflakes-vim.zip","4":"pyflakes-vim.zip","src_id":"11396","5":"11396","creation_date":"1253196410","6":"1253196410"},{"0":"2441","vim_version":"7.0","1":"7.0","script_version":"1.5","2":"1.5","version_comment":"http:\/\/github.com\/kevinw\/pyflakes-vim\/commit\/b8f2f366b1322a5ffefede30ddb3339102d2f28c\r\n\r\nIgnore stderr during ast.parse, since it will otherwise show as VIM error \r\nmessages. Thanks Denis Bilenko.\r\n\r\nEventually we should parse some of the warnings. For example:\r\n\r\n  foo.py:33: Warning: 'as' will become a reserved keyword in Python 2.6\r\n\r\nThis could become a visible warning.","3":"http:\/\/github.com\/kevinw\/pyflakes-vim\/commit\/b8f2f366b1322a5ffefede30ddb3339102d2f28c\r\n\r\nIgnore stderr during ast.parse, since it will otherwise show as VIM error \r\nmessages. Thanks Denis Bilenko.\r\n\r\nEventually we should parse some of the warnings. For example:\r\n\r\n  foo.py:33: Warning: 'as' will become a reserved keyword in Python 2.6\r\n\r\nThis could become a visible warning.","package":"pyflakes-vim.zip","4":"pyflakes-vim.zip","src_id":"10971","5":"10971","creation_date":"1247082100","6":"1247082100"},{"0":"2441","vim_version":"7.0","1":"7.0","script_version":"1.4","2":"1.4","version_comment":"http:\/\/github.com\/kevinw\/pyflakes-vim\/commit\/6ec1fbbce32876e315b370409ca55c97d232d125\r\n\r\nRestrict dd, dw, etc mappings to the local Python buffer.","3":"http:\/\/github.com\/kevinw\/pyflakes-vim\/commit\/6ec1fbbce32876e315b370409ca55c97d232d125\r\n\r\nRestrict dd, dw, etc mappings to the local Python buffer.","package":"pyflakes-vim.zip","4":"pyflakes-vim.zip","src_id":"10551","5":"10551","creation_date":"1241628046","6":"1241628046"},{"0":"2441","vim_version":"7.0","1":"7.0","script_version":"1.3","2":"1.3","version_comment":"Some fixes based on suggestions from Brandon Low:\r\n\r\n - changed highlight call from hard coding a curly underline to linking with the \"SpellBad\" style. This is more friendly vim on terminals. If you'd like the old brighter orange undercurl from previous versions, add the following to your .vimrc:\r\n\r\n    if has(\"gui_running\")\r\n        highlight SpellBad term=underline gui=undercurl guisp=Orange\r\n    endif\r\n\r\n - added the :PyflakesUpdate command (runs pyflakes and updates the message area)\r\n - hooked dd, dw, u, and <C-R> to also call :PyflakesUpdate so common text operations will invoke PyFlakes\r\n","3":"Some fixes based on suggestions from Brandon Low:\r\n\r\n - changed highlight call from hard coding a curly underline to linking with the \"SpellBad\" style. This is more friendly vim on terminals. If you'd like the old brighter orange undercurl from previous versions, add the following to your .vimrc:\r\n\r\n    if has(\"gui_running\")\r\n        highlight SpellBad term=underline gui=undercurl guisp=Orange\r\n    endif\r\n\r\n - added the :PyflakesUpdate command (runs pyflakes and updates the message area)\r\n - hooked dd, dw, u, and <C-R> to also call :PyflakesUpdate so common text operations will invoke PyFlakes\r\n","package":"pyflakes-vim.zip","4":"pyflakes-vim.zip","src_id":"10434","5":"10434","creation_date":"1240344146","6":"1240344146"},{"0":"2441","vim_version":"7.0","1":"7.0","script_version":"1.2","2":"1.2","version_comment":"- Include compatibility fixes for Python 2.6's _ast changes in visit_FunctionDef and for visit_ExceptHandler. Thanks Herve Cauwelier. \r\n- Include pyflakes.scripts in the \"packages\" option for setup. Thanks Herve Cauwelier. \r\n- Fix for names incorrectly marked undefined in nested list comprehensions. \r\n- Add \"__builtins__\" to the list of predefined names. \r\n- Bind names for *args and **kwargs in functions and lambdas. ","3":"- Include compatibility fixes for Python 2.6's _ast changes in visit_FunctionDef and for visit_ExceptHandler. Thanks Herve Cauwelier. \r\n- Include pyflakes.scripts in the \"packages\" option for setup. Thanks Herve Cauwelier. \r\n- Fix for names incorrectly marked undefined in nested list comprehensions. \r\n- Add \"__builtins__\" to the list of predefined names. \r\n- Bind names for *args and **kwargs in functions and lambdas. ","package":"pyflakes-vim.zip","4":"pyflakes-vim.zip","src_id":"10193","5":"10193","creation_date":"1236901434","6":"1236901434"},{"0":"2441","vim_version":"7.0","1":"7.0","script_version":"1.1","2":"1.1","version_comment":"Updated pyflakes\/checker.py to fix AST fixes from http:\/\/github.com\/kevinw\/pyflakes\/commit\/bdc1acde85df3bf0a8f5ef1ec26e9121667c9d0a","3":"Updated pyflakes\/checker.py to fix AST fixes from http:\/\/github.com\/kevinw\/pyflakes\/commit\/bdc1acde85df3bf0a8f5ef1ec26e9121667c9d0a","package":"pyflakes-vim.zip","4":"pyflakes-vim.zip","src_id":"9528","5":"9528","creation_date":"1227138837","6":"1227138837"},{"0":"2441","vim_version":"7.2","1":"7.2","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"pyflakes-vim.zip","4":"pyflakes-vim.zip","src_id":"9503","5":"9503","creation_date":"1226710399","6":"1226710399"}]},"2440":{"script_id":"2440","0":"2440","script_name":"TagManager (BETA)","1":"TagManager (BETA)","script_type":"utility","2":"utility","summary":"Build, manage and keep tag databases up-to-date within Vim","3":"Build, manage and keep tag databases up-to-date within Vim","description":"Screenshots: http:\/\/sites.google.com\/site\/vimcctree\/other-plugins\r\n\r\n     Plugin provides an integrated environment within Vim for building, maintaining,\r\n     and using tag databases.\r\n                                                                                         \r\n     Features:\r\n         * Specify a list of files or regex file search patterns for inclusion\r\n           in tags database\r\n         * Support for multiple databases\r\n         * Build and track tag databases for freshness\r\n             + Tracks new file creations when using regex file patterns                 \r\n             + Update tag databases on every file save with\r\n               efficient incremental updates\r\n             + Tracks file changes outside of Vim\r\n                                                                                         \r\n     Limitations:\r\n         * Might slow-up with huge databases because of  Vim scripting\r\n           speed and API limitations\r\n             - Recommended method is to split multiple tag databases for \r\n               each sub-directory\r\n\r\n\r\n\r\nUsage:\r\n                                                                               \r\n     Commands:\r\n      :TagManagerAddDb  <tagDB name> <filelist\/pattern> [directory]\r\n         Illustration:\r\n         :TagManagerAddDb tags *.[ch] \r\n         :TagManagerAddDb tags *.[ch] .\r\n         [Note that both commands do the same, the directory is optional;\r\n         if omitted, the current directory is used]\r\n                                                                               \r\n         :TagManagerAddDb tags **\/*.[ch] \r\n           Recursively add all .c and .h files in the current directory and\r\n           directories under it. More complicated search patterns are\r\n           possible with the \"**\" operator. For more help, please see :help **\r\n                                                                               \r\n         :TagManagerAddDb tags **\/*.[ch] .\/dir1\/,.\/dir2\/,.\/dir3\/\r\n           Selectively build individual tags in each of these directories\r\n           recusively. Paths are relative to current directory. It is also \r\n           possible to specify the absolute paths\r\n                                                                               \r\n         The sequence of commands has the same effect as the previous\r\n         command\r\n         :TagManagerAddDb tags **\/*.[ch] .\/dir1\r\n         :TagManagerAddDb tags **\/*.[ch] .\/dir2\r\n         :TagManagerAddDb tags **\/*.[ch] .\/dir3\r\n         :TagManagerAddDb tags  *\/*.[ch] .\/dir4    [not recursive]\r\n                                                                               \r\n                                                                               \r\n         Using file lists\r\n         :TagManagerAddDb tags files.lst dir1\r\n             Uses the \"files.lst\" file in directory \"dir1\" for the database\r\n             creation. Instead of using regex patterns, file lists can also\r\n             specified. Note that these files must be created manually\r\n             before-hand.\r\n                     \r\n      :TagManagerShowDbs\r\n         Shows the current loaded Dbs and their internal index\r\n                                                                               \r\n      :TagManagerRemoveDb <index>\r\n          Use it to remove already loaded Tag Dbs. Index must be\r\n          obtained from the show command\r\n                                                                               \r\n      Debugging:\r\n                                                                               \r\n         :TagManagerShowDbDetail <index>\r\n             Show more details of the database: i.e., list of files tracked\r\n                \r\n         :TagManagerShowLog\r\n             Internal debug log; displays the sequence of\r\n             actions\/events\/system commands executed. In case of anomalous\r\n             behavior, please log this.\r\n                                                                               \r\n      Configuration:      \r\n          :let g:TagMgr_CtagsProgName = 'ctags'\r\n             Specify the executable for the tag generation application.\r\n             \r\n          :let g:TagMgr_CtagsProgDir = ''\r\n             Specify the directory in which the ctags app can be found. If\r\n             it is on the path, then it can be left empty.\r\n                 \r\n          :let g:TagMgr_CtagsExtraOpts = ''\r\n             Extra options for building the database. A better option is to\r\n             use the ~\/.ctagsrc file to specify extra options; this will be\r\n             automatically used for every ctags run.\r\n                                                                               \r\n          :let g:TagMgr_AutoTrackDbs = 1\r\n             Disable (0) or enable (1). TagManager will automatically setup\r\n             the Vim 'tags' variable to reflect the current paths. (More to\r\n             come later for this feature)\r\n                                                                               \r\n          :let g:TagMgr_LogMaxLines = 30\r\n             Internal debug log. Sets the limit for the number of lines.\r\n                                                                               \r\n          :let g:TagMgr_SourceListFile = 'files.lst'\r\n             When using a regex for file specification, TagManager will\r\n             create a file list with this name and then pass it to ctags.\r\n","4":"Screenshots: http:\/\/sites.google.com\/site\/vimcctree\/other-plugins\r\n\r\n     Plugin provides an integrated environment within Vim for building, maintaining,\r\n     and using tag databases.\r\n                                                                                         \r\n     Features:\r\n         * Specify a list of files or regex file search patterns for inclusion\r\n           in tags database\r\n         * Support for multiple databases\r\n         * Build and track tag databases for freshness\r\n             + Tracks new file creations when using regex file patterns                 \r\n             + Update tag databases on every file save with\r\n               efficient incremental updates\r\n             + Tracks file changes outside of Vim\r\n                                                                                         \r\n     Limitations:\r\n         * Might slow-up with huge databases because of  Vim scripting\r\n           speed and API limitations\r\n             - Recommended method is to split multiple tag databases for \r\n               each sub-directory\r\n\r\n\r\n\r\nUsage:\r\n                                                                               \r\n     Commands:\r\n      :TagManagerAddDb  <tagDB name> <filelist\/pattern> [directory]\r\n         Illustration:\r\n         :TagManagerAddDb tags *.[ch] \r\n         :TagManagerAddDb tags *.[ch] .\r\n         [Note that both commands do the same, the directory is optional;\r\n         if omitted, the current directory is used]\r\n                                                                               \r\n         :TagManagerAddDb tags **\/*.[ch] \r\n           Recursively add all .c and .h files in the current directory and\r\n           directories under it. More complicated search patterns are\r\n           possible with the \"**\" operator. For more help, please see :help **\r\n                                                                               \r\n         :TagManagerAddDb tags **\/*.[ch] .\/dir1\/,.\/dir2\/,.\/dir3\/\r\n           Selectively build individual tags in each of these directories\r\n           recusively. Paths are relative to current directory. It is also \r\n           possible to specify the absolute paths\r\n                                                                               \r\n         The sequence of commands has the same effect as the previous\r\n         command\r\n         :TagManagerAddDb tags **\/*.[ch] .\/dir1\r\n         :TagManagerAddDb tags **\/*.[ch] .\/dir2\r\n         :TagManagerAddDb tags **\/*.[ch] .\/dir3\r\n         :TagManagerAddDb tags  *\/*.[ch] .\/dir4    [not recursive]\r\n                                                                               \r\n                                                                               \r\n         Using file lists\r\n         :TagManagerAddDb tags files.lst dir1\r\n             Uses the \"files.lst\" file in directory \"dir1\" for the database\r\n             creation. Instead of using regex patterns, file lists can also\r\n             specified. Note that these files must be created manually\r\n             before-hand.\r\n                     \r\n      :TagManagerShowDbs\r\n         Shows the current loaded Dbs and their internal index\r\n                                                                               \r\n      :TagManagerRemoveDb <index>\r\n          Use it to remove already loaded Tag Dbs. Index must be\r\n          obtained from the show command\r\n                                                                               \r\n      Debugging:\r\n                                                                               \r\n         :TagManagerShowDbDetail <index>\r\n             Show more details of the database: i.e., list of files tracked\r\n                \r\n         :TagManagerShowLog\r\n             Internal debug log; displays the sequence of\r\n             actions\/events\/system commands executed. In case of anomalous\r\n             behavior, please log this.\r\n                                                                               \r\n      Configuration:      \r\n          :let g:TagMgr_CtagsProgName = 'ctags'\r\n             Specify the executable for the tag generation application.\r\n             \r\n          :let g:TagMgr_CtagsProgDir = ''\r\n             Specify the directory in which the ctags app can be found. If\r\n             it is on the path, then it can be left empty.\r\n                 \r\n          :let g:TagMgr_CtagsExtraOpts = ''\r\n             Extra options for building the database. A better option is to\r\n             use the ~\/.ctagsrc file to specify extra options; this will be\r\n             automatically used for every ctags run.\r\n                                                                               \r\n          :let g:TagMgr_AutoTrackDbs = 1\r\n             Disable (0) or enable (1). TagManager will automatically setup\r\n             the Vim 'tags' variable to reflect the current paths. (More to\r\n             come later for this feature)\r\n                                                                               \r\n          :let g:TagMgr_LogMaxLines = 30\r\n             Internal debug log. Sets the limit for the number of lines.\r\n                                                                               \r\n          :let g:TagMgr_SourceListFile = 'files.lst'\r\n             When using a regex for file specification, TagManager will\r\n             create a file list with this name and then pass it to ctags.\r\n","install_details":"             Copy this file to ~\/.vim\/plugins\/\r\n             or to \/vimfiles\/plugins\/  (on Win32 platforms) \r\n                                                                             \r\nQuickStart:\r\n        1) Add the following to one of the following files:\r\n             (a) ~\/.gvimrc, or \r\n             (b)  ~\/.vim\/after\/plugin\/tagmgr.vim  (filename has to be the same!)\r\n                 Windows: $VIM\\vimfiles\\after\\plugin\\tagmgr.vim\r\n                                                                                 \r\n            NOTE: Adding to .vimrc will *NOT* work. Only GVim will use\r\n                  .gvimrc file for startup. If you use console Vim, then\r\n                  use the 'after' option.\r\n                                                                                 \r\n            TagManagerAddDb tags *.[ch]  <change as per source language )\r\n            (or)\r\n            TagMangerAddDb tags **\/*.[ch]  <Recursive; use only if there are\r\n            directories> \r\n                                                                                 \r\n                                                                                 \r\n        2. Launch vim from the project root directory.\r\n                                                                                 \r\n        NOTE: The commands can be run from within Vim on the project root\r\n              directory without using the start-up scripts.\r\n\r\nNOTE: This is a BETA version. Feedback is appreciated. Thanks!","5":"             Copy this file to ~\/.vim\/plugins\/\r\n             or to \/vimfiles\/plugins\/  (on Win32 platforms) \r\n                                                                             \r\nQuickStart:\r\n        1) Add the following to one of the following files:\r\n             (a) ~\/.gvimrc, or \r\n             (b)  ~\/.vim\/after\/plugin\/tagmgr.vim  (filename has to be the same!)\r\n                 Windows: $VIM\\vimfiles\\after\\plugin\\tagmgr.vim\r\n                                                                                 \r\n            NOTE: Adding to .vimrc will *NOT* work. Only GVim will use\r\n                  .gvimrc file for startup. If you use console Vim, then\r\n                  use the 'after' option.\r\n                                                                                 \r\n            TagManagerAddDb tags *.[ch]  <change as per source language )\r\n            (or)\r\n            TagMangerAddDb tags **\/*.[ch]  <Recursive; use only if there are\r\n            directories> \r\n                                                                                 \r\n                                                                                 \r\n        2. Launch vim from the project root directory.\r\n                                                                                 \r\n        NOTE: The commands can be run from within Vim on the project root\r\n              directory without using the start-up scripts.\r\n\r\nNOTE: This is a BETA version. Feedback is appreciated. Thanks!","first_name":"Hari","6":"Hari","last_name":"Rangarajan","7":"Rangarajan","releases":[{"0":"2440","vim_version":"7.0","1":"7.0","script_version":"0.02","2":"0.02","version_comment":"Initial upload","3":"Initial upload","package":"tagmgr.vim","4":"tagmgr.vim","src_id":"9500","5":"9500","creation_date":"1226641821","6":"1226641821"}]},"2439":{"script_id":"2439","0":"2439","script_name":"Php Doc","1":"Php Doc","script_type":"ftplugin","2":"ftplugin","summary":"Open's PHP Documentation in Web Browser","3":"Open's PHP Documentation in Web Browser","description":"Open's your default Web Browser to the word\/function under the cursor by hitting K.","4":"Open's your default Web Browser to the word\/function under the cursor by hitting K.","install_details":"Put php_doc.vim to your ~\/.vim\/ftplugin folder.","5":"Put php_doc.vim to your ~\/.vim\/ftplugin folder.","first_name":"Travis","6":"Travis","last_name":"Jeffery","7":"Jeffery","releases":[{"0":"2439","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"php_doc.vim","4":"php_doc.vim","src_id":"9494","5":"9494","creation_date":"1226554377","6":"1226554377"}]},"2438":{"script_id":"2438","0":"2438","script_name":"EasyGrep","1":"EasyGrep","script_type":"utility","2":"utility","summary":"Fast and Easy Find and Replace Across Multiple Files","3":"Fast and Easy Find and Replace Across Multiple Files","description":"EasyGrep is a plugin for performing search and replace operations through multiple files. Vim already has builtin support for searching through files with its 'vimgrep' and 'grep' commands, but EasyGrep makes using them much, much easier. It also provides a powerful \"Replace in Files\" operation, something that is not very easy to do in Vim by default. With EasyGrep, you can specify with high-precision exactly the type of files you want to search, whether it be all files, only open buffers, only files matching a pattern, etc. Additionally, you can easily specify searching through hidden files, case-sensitivity, performing a recursive search, and many more options that make searching more easy.\r\n\r\nEasyGrep provides both key mappings and commands to make search and replace easy. When using EasyGrep, searching for a word is as easy as typing <leader>vv (v v, not double-u) over the word for which you want to search.  This search can also be accomplished with the :Grep command and a user-specified pattern. Performing a \"replace in files\" is similar; type <leader>vr or use the :Replace command. Setting options is easy, simply type <leader>vo or :GrepOptions.  EasyGrep provides a great set of defaults but can also be configured to start up just how you like it; see the script for these options.  Most vimgrep (and grepprg) options are supported.  \r\n\r\nFor an in-development version of EasyGrep go to http:\/\/github.com\/dkprice\/vim-easygrep \r\n\r\nKeymappings:\r\n\r\n    <Leader>vv  - Grep for the word under the cursor, match all occurences,\r\n                  like |gstar|\r\n    <Leader>vV  - Grep for the word under the cursor, match whole word, like \r\n                  |star|\r\n    <Leader>va  - Like vv, but add to existing list\r\n    <Leader>vA  - Like vV, but add to existing list\r\n    <Leader>vr  - Perform a global search search on the word under the cursor\r\n                  and prompt for a pattern with which to replace it.\r\n    <Leader>vo  - Select the files to search in and set grep options\r\n\r\nCommands:\r\n\r\n    :Grep [arg]\r\n        Search for the specified arg, like <Leader>vv.  When an ! is added,\r\n        search like <Leader>vV\r\n\r\n    :GrepAdd [arg]\r\n        Search for the specified arg, add to existing file list, as in\r\n        <Leader>va.  When an ! is added, search like <Leader>vA\r\n\r\n    :Replace [target] [replacement]\r\n        Perform a global search and replace.  The function searches\r\n        the same set of files a grep for the desired target and opens a dialog to\r\n        confirm replacement.\r\n    \r\n    :ReplaceUndo\r\n        Undoes the last :Replace operation.  Does not stack successive\r\n        searches; only the last replace may be undone.  This function may not\r\n        work well when edits are made between a call to Replace and a call to\r\n        ReplaceUndo.\r\n\r\n    :GrepOptions [arg]\r\n        Open a window to set grep options.","4":"EasyGrep is a plugin for performing search and replace operations through multiple files. Vim already has builtin support for searching through files with its 'vimgrep' and 'grep' commands, but EasyGrep makes using them much, much easier. It also provides a powerful \"Replace in Files\" operation, something that is not very easy to do in Vim by default. With EasyGrep, you can specify with high-precision exactly the type of files you want to search, whether it be all files, only open buffers, only files matching a pattern, etc. Additionally, you can easily specify searching through hidden files, case-sensitivity, performing a recursive search, and many more options that make searching more easy.\r\n\r\nEasyGrep provides both key mappings and commands to make search and replace easy. When using EasyGrep, searching for a word is as easy as typing <leader>vv (v v, not double-u) over the word for which you want to search.  This search can also be accomplished with the :Grep command and a user-specified pattern. Performing a \"replace in files\" is similar; type <leader>vr or use the :Replace command. Setting options is easy, simply type <leader>vo or :GrepOptions.  EasyGrep provides a great set of defaults but can also be configured to start up just how you like it; see the script for these options.  Most vimgrep (and grepprg) options are supported.  \r\n\r\nFor an in-development version of EasyGrep go to http:\/\/github.com\/dkprice\/vim-easygrep \r\n\r\nKeymappings:\r\n\r\n    <Leader>vv  - Grep for the word under the cursor, match all occurences,\r\n                  like |gstar|\r\n    <Leader>vV  - Grep for the word under the cursor, match whole word, like \r\n                  |star|\r\n    <Leader>va  - Like vv, but add to existing list\r\n    <Leader>vA  - Like vV, but add to existing list\r\n    <Leader>vr  - Perform a global search search on the word under the cursor\r\n                  and prompt for a pattern with which to replace it.\r\n    <Leader>vo  - Select the files to search in and set grep options\r\n\r\nCommands:\r\n\r\n    :Grep [arg]\r\n        Search for the specified arg, like <Leader>vv.  When an ! is added,\r\n        search like <Leader>vV\r\n\r\n    :GrepAdd [arg]\r\n        Search for the specified arg, add to existing file list, as in\r\n        <Leader>va.  When an ! is added, search like <Leader>vA\r\n\r\n    :Replace [target] [replacement]\r\n        Perform a global search and replace.  The function searches\r\n        the same set of files a grep for the desired target and opens a dialog to\r\n        confirm replacement.\r\n    \r\n    :ReplaceUndo\r\n        Undoes the last :Replace operation.  Does not stack successive\r\n        searches; only the last replace may be undone.  This function may not\r\n        work well when edits are made between a call to Replace and a call to\r\n        ReplaceUndo.\r\n\r\n    :GrepOptions [arg]\r\n        Open a window to set grep options.","install_details":"Copy EasyGrep.vim and EasyGrepFileAssociations to your plugin directory; copy EasyGrep.txt to your doc directory.  Run helptags on your doc directory.","5":"Copy EasyGrep.vim and EasyGrepFileAssociations to your plugin directory; copy EasyGrep.txt to your doc directory.  Run helptags on your doc directory.","first_name":"Daniel","6":"Daniel","last_name":"Price","7":"Price","releases":[{"0":"2438","vim_version":"7.0","1":"7.0","script_version":"1.1","2":"1.1","version_comment":"Improved: much better support when grepprg is ack or grep. These tools can search much more quickly than vimgrep and so may be preferable to some users.\r\nFeature: added a mapping to echo the command that EasyGrep will issue (see 'v' in the options explorer)\r\nFeature: Added keymap toggle for EasyGrepSearchCurrentBufferDir\r\nFixed: command line parsing of Grep command discarded spaces\r\nFeature: added support for grep exclusions when grepprg is grep or ack\r\nFeature: Added EasyGrepDefaultUserPattern option.  Thanks to Jesus Barcons for the suggestion.\r\nImproved: Cleaned up the documentation\r\nImproved: Cleaned up the internals of the script substantially\r\nImproved: Formalized multi-select mode, which is when multiple file extensions are selected from the options explorer\r\nImproved: lots of misc fixes","3":"Improved: much better support when grepprg is ack or grep. These tools can search much more quickly than vimgrep and so may be preferable to some users.\r\nFeature: added a mapping to echo the command that EasyGrep will issue (see 'v' in the options explorer)\r\nFeature: Added keymap toggle for EasyGrepSearchCurrentBufferDir\r\nFixed: command line parsing of Grep command discarded spaces\r\nFeature: added support for grep exclusions when grepprg is grep or ack\r\nFeature: Added EasyGrepDefaultUserPattern option.  Thanks to Jesus Barcons for the suggestion.\r\nImproved: Cleaned up the documentation\r\nImproved: Cleaned up the internals of the script substantially\r\nImproved: Formalized multi-select mode, which is when multiple file extensions are selected from the options explorer\r\nImproved: lots of misc fixes","package":"EasyGrep.zip","4":"EasyGrep.zip","src_id":"19531","5":"19531","creation_date":"1361078437","6":"1361078437"},{"0":"2438","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Documentation: Added a help tag for each of the commands so that you can\r\n    look up more information on them.\r\nImproved: Cleaned up the internals of the script substantially\r\nImproved: Changed the name of FilterErrorList to ResultListFilter\r\nFeature: Added ResultListOpen command to open all of the files in the\r\n    result list (aka error list)\r\nFixed: Added -- to signify the end of the command line options. Grepping \r\n    for patterns such as '->var' are now possible with ':Grep -- ->var'","3":"Documentation: Added a help tag for each of the commands so that you can\r\n    look up more information on them.\r\nImproved: Cleaned up the internals of the script substantially\r\nImproved: Changed the name of FilterErrorList to ResultListFilter\r\nFeature: Added ResultListOpen command to open all of the files in the\r\n    result list (aka error list)\r\nFixed: Added -- to signify the end of the command line options. Grepping \r\n    for patterns such as '->var' are now possible with ':Grep -- ->var'","package":"EasyGrep.zip","4":"EasyGrep.zip","src_id":"16713","5":"16713","creation_date":"1319160557","6":"1319160557"},{"0":"2438","vim_version":"7.0","1":"7.0","script_version":"0.98","2":"0.98","version_comment":"Highlight: The Replace and ReplaceUndo commands were reimplemented.  The granularity of matches inside of a Replace call were improved so that you can now decide replacements individually per line.\r\n    Additionally, Complex operations such as replacing x[i][j][k] with x(i,j,k) and following it up with a ReplaceUndo are now possible.\r\n\r\n    e.g.\r\n    :Replace \/x\\[\\([^]]\\+\\)\\]\\[\\([^]]\\+\\)\\]\\[\\([^]]\\+\\)\\]\/x(\\1,\\2,\\3)\/\r\n    :ReplaceUndo\r\n\r\n    Please report any regressions with either of these functions.\r\n\r\nFeature: Added count command line option (-m 4 or -4)\r\nFeature: Improved Grep options window keybindings; searching within the options explorer window is now possible\r\nFeature: Expanded searches to include all of the active buffers' directories\r\nBugfix:  Fixed recursive operation and expanded search from reporting duplicate results\r\nBugfix:  Fixed <C-e> and <C-y> in replace mode\r\nFeature: Added EasyGrepWindowPosition for specifying where the error list window will be opened\r\nFeature: Added FilterErrorlist command for filtering the results within the quickfix or location list windows\r\nFeature: Improved printout when no matches are found\r\nFeature: Improved searching when an entire line is selected","3":"Highlight: The Replace and ReplaceUndo commands were reimplemented.  The granularity of matches inside of a Replace call were improved so that you can now decide replacements individually per line.\r\n    Additionally, Complex operations such as replacing x[i][j][k] with x(i,j,k) and following it up with a ReplaceUndo are now possible.\r\n\r\n    e.g.\r\n    :Replace \/x\\[\\([^]]\\+\\)\\]\\[\\([^]]\\+\\)\\]\\[\\([^]]\\+\\)\\]\/x(\\1,\\2,\\3)\/\r\n    :ReplaceUndo\r\n\r\n    Please report any regressions with either of these functions.\r\n\r\nFeature: Added count command line option (-m 4 or -4)\r\nFeature: Improved Grep options window keybindings; searching within the options explorer window is now possible\r\nFeature: Expanded searches to include all of the active buffers' directories\r\nBugfix:  Fixed recursive operation and expanded search from reporting duplicate results\r\nBugfix:  Fixed <C-e> and <C-y> in replace mode\r\nFeature: Added EasyGrepWindowPosition for specifying where the error list window will be opened\r\nFeature: Added FilterErrorlist command for filtering the results within the quickfix or location list windows\r\nFeature: Improved printout when no matches are found\r\nFeature: Improved searching when an entire line is selected","package":"EasyGrep.zip","4":"EasyGrep.zip","src_id":"14198","5":"14198","creation_date":"1289074252","6":"1289074252"},{"0":"2438","vim_version":"7.0","1":"7.0","script_version":".96","2":".96","version_comment":"Feature: Expanded upon the list of file associations \r\nFeature: Expanded searches to the current buffer's directory in addition to the current working directory \r\nFeature: Added command line arguments to :Grep and :Replace for recursive searches and case sensitivity \r\nFeature: Added toggle for window replace mode \r\nFeature: Added toggle for showing file associations list in options explorer \r\nBugfix: Case insensitivity would fail in replacing some patterns","3":"Feature: Expanded upon the list of file associations \r\nFeature: Expanded searches to the current buffer's directory in addition to the current working directory \r\nFeature: Added command line arguments to :Grep and :Replace for recursive searches and case sensitivity \r\nFeature: Added toggle for window replace mode \r\nFeature: Added toggle for showing file associations list in options explorer \r\nBugfix: Case insensitivity would fail in replacing some patterns","package":"EasyGrep.zip","4":"EasyGrep.zip","src_id":"11717","5":"11717","creation_date":"1258092243","6":"1258092243"},{"0":"2438","vim_version":"7.0","1":"7.0","script_version":"0.951","2":"0.951","version_comment":"Update to 0.95: Fixed an error in calling ReplaceCurrentWord identified by Eric Ho.\r\n\r\nFeature: Added search and replace on visual selections. \r\nFeature: Improved Grepping for items that can be interpreted as regular expressions.  Selections are assumed to be literal, whereas explicit commands are assumed to be regular expressions. \r\nFeature: Removed option g:EasyGrepNoDirectMappings in favor of g:EasyGrepOptionPrefix, which allows the option prefix to be changed. \r\nBugfix:  The tracked extension would sometimes fail to be updated when switching between buffers \r\nDocumentation: Split the documentation into its own file; greatly expanded upon its contents. \r\nChange: Activating a mode that is already activated will no longer deactivate it. \r\nChange: GrepOptions no longer accepts an argument; use user mode instead. \r\nChange: Clarified mapping names; custom mappings will need to be reset.","3":"Update to 0.95: Fixed an error in calling ReplaceCurrentWord identified by Eric Ho.\r\n\r\nFeature: Added search and replace on visual selections. \r\nFeature: Improved Grepping for items that can be interpreted as regular expressions.  Selections are assumed to be literal, whereas explicit commands are assumed to be regular expressions. \r\nFeature: Removed option g:EasyGrepNoDirectMappings in favor of g:EasyGrepOptionPrefix, which allows the option prefix to be changed. \r\nBugfix:  The tracked extension would sometimes fail to be updated when switching between buffers \r\nDocumentation: Split the documentation into its own file; greatly expanded upon its contents. \r\nChange: Activating a mode that is already activated will no longer deactivate it. \r\nChange: GrepOptions no longer accepts an argument; use user mode instead. \r\nChange: Clarified mapping names; custom mappings will need to be reset.","package":"EasyGrep.zip","4":"EasyGrep.zip","src_id":"10265","5":"10265","creation_date":"1237773414","6":"1237773414"},{"0":"2438","vim_version":"7.0","1":"7.0","script_version":"0.9","2":"0.9","version_comment":"Feature: Added forward slash delineated pattern to the Replace command\r\ne.g. :Replace \/target\/replacement\/\r\nthat allows more complicated replacements; you can now work with\r\npatterns that have spaces in them.\r\nBugfix: If cursorline is off at the start of a replace, now ensuring that cursorline is turned off for all buffers, and not just the last one\r\nBugfix: fixed an issue with an extra tab being opened during a replacement","3":"Feature: Added forward slash delineated pattern to the Replace command\r\ne.g. :Replace \/target\/replacement\/\r\nthat allows more complicated replacements; you can now work with\r\npatterns that have spaces in them.\r\nBugfix: If cursorline is off at the start of a replace, now ensuring that cursorline is turned off for all buffers, and not just the last one\r\nBugfix: fixed an issue with an extra tab being opened during a replacement","package":"EasyGrep.zip","4":"EasyGrep.zip","src_id":"9869","5":"9869","creation_date":"1233034910","6":"1233034910"},{"0":"2438","vim_version":"7.0","1":"7.0","script_version":"0.8","2":"0.8","version_comment":"Implemented case sensitivity that is independent of ignorecase; thanks to Doro Wu for contributing to this functionality\r\nChanged shortcut key for hidden files from 'i' to 'h'","3":"Implemented case sensitivity that is independent of ignorecase; thanks to Doro Wu for contributing to this functionality\r\nChanged shortcut key for hidden files from 'i' to 'h'","package":"EasyGrep.zip","4":"EasyGrep.zip","src_id":"9800","5":"9800","creation_date":"1231701998","6":"1231701998"},{"0":"2438","vim_version":"7.0","1":"7.0","script_version":"0.7","2":"0.7","version_comment":"Expanded search of EasyGrepFileAssociations list to every component of 'runtimepath'.  This solves a starting message for those who placed EasyGrepFileAssociations in a location other than the first location in 'runtimepath'.","3":"Expanded search of EasyGrepFileAssociations list to every component of 'runtimepath'.  This solves a starting message for those who placed EasyGrepFileAssociations in a location other than the first location in 'runtimepath'.","package":"EasyGrep.zip","4":"EasyGrep.zip","src_id":"9724","5":"9724","creation_date":"1230305563","6":"1230305563"},{"0":"2438","vim_version":"7.0","1":"7.0","script_version":"0.6","2":"0.6","version_comment":"Fixed paths with spaces in them\r\nFolds will now be disabled where replacements are to be made\r\nFixed an error with checking for extra warnings\r\nBetter highlighting while replacing\r\nRecursive mode can no longer be activated when Buffers mode is activated","3":"Fixed paths with spaces in them\r\nFolds will now be disabled where replacements are to be made\r\nFixed an error with checking for extra warnings\r\nBetter highlighting while replacing\r\nRecursive mode can no longer be activated when Buffers mode is activated","package":"EasyGrep.zip","4":"EasyGrep.zip","src_id":"9639","5":"9639","creation_date":"1228794986","6":"1228794986"},{"0":"2438","vim_version":"7.0","1":"7.0","script_version":"0.5","2":"0.5","version_comment":"Fixed an issue with tracking the file extension where sometimes the desired extension wouldn't be registered.\r\nBetter reporting when no files match.\r\nNow warning when searching from a working directory that doesn't match the current file's directory.\r\nAdded g:EasyGrepExtraWarnings option.","3":"Fixed an issue with tracking the file extension where sometimes the desired extension wouldn't be registered.\r\nBetter reporting when no files match.\r\nNow warning when searching from a working directory that doesn't match the current file's directory.\r\nAdded g:EasyGrepExtraWarnings option.","package":"EasyGrep.zip","4":"EasyGrep.zip","src_id":"9552","5":"9552","creation_date":"1227499372","6":"1227499372"},{"0":"2438","vim_version":"7.0","1":"7.0","script_version":"0.4","2":"0.4","version_comment":"Improved Replace and ReplaceUndo\r\nAdded two configurable modes for how the windows operate when doing a global replace.\r\nFixed an issue with linked filetypes.","3":"Improved Replace and ReplaceUndo\r\nAdded two configurable modes for how the windows operate when doing a global replace.\r\nFixed an issue with linked filetypes.","package":"EasyGrep.zip","4":"EasyGrep.zip","src_id":"9534","5":"9534","creation_date":"1227234302","6":"1227234302"},{"0":"2438","vim_version":"7.0","1":"7.0","script_version":"0.3","2":"0.3","version_comment":"Added experimental :Replace and :ReplaceUndo commands; keymapped <leader>vr for :Replace\r\nImproved response when no matches","3":"Added experimental :Replace and :ReplaceUndo commands; keymapped <leader>vr for :Replace\r\nImproved response when no matches","package":"EasyGrep.zip","4":"EasyGrep.zip","src_id":"9520","5":"9520","creation_date":"1227070904","6":"1227070904"},{"0":"2438","vim_version":"7.0","1":"7.0","script_version":"0.2","2":"0.2","version_comment":"Added option to toggle showing fewer or more options; showing fewer options by default.\r\nAdded option '?' to print the current configuration and save it to a register.\r\nNow creating direct mapping by default; see g:EasyGrepNoDirectMappings to turn this off.\r\n","3":"Added option to toggle showing fewer or more options; showing fewer options by default.\r\nAdded option '?' to print the current configuration and save it to a register.\r\nNow creating direct mapping by default; see g:EasyGrepNoDirectMappings to turn this off.\r\n","package":"EasyGrep.zip","4":"EasyGrep.zip","src_id":"9509","5":"9509","creation_date":"1226773501","6":"1226773501"},{"0":"2438","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"EasyGrep.zip","4":"EasyGrep.zip","src_id":"9493","5":"9493","creation_date":"1226542913","6":"1226542913"}]},"2437":{"script_id":"2437","0":"2437","script_name":"shymenu","1":"shymenu","script_type":"utility","2":"utility","summary":"Show the menu bar only when pressing an accelerator key","3":"Show the menu bar only when pressing an accelerator key","description":"shymenu will show the menu bar only when the user presses an accelerator \r\nkey. The menu will be hidden again after an item was selected.\r\nshymenu achieves this by defining key maps for those accelerator keys \r\n(see 'winaltkeys') that would normaly activate a menu.\r\n\r\nOn a terminal, shymenu will define accelerator keys for the |:emenu| \r\ncommand.\r\n\r\nSee also:\r\nhttp:\/\/groups.google.com\/group\/vim_use\/browse_frm\/thread\/44c870c1e930bcc0\r\n","4":"shymenu will show the menu bar only when the user presses an accelerator \r\nkey. The menu will be hidden again after an item was selected.\r\nshymenu achieves this by defining key maps for those accelerator keys \r\n(see 'winaltkeys') that would normaly activate a menu.\r\n\r\nOn a terminal, shymenu will define accelerator keys for the |:emenu| \r\ncommand.\r\n\r\nSee also:\r\nhttp:\/\/groups.google.com\/group\/vim_use\/browse_frm\/thread\/44c870c1e930bcc0\r\n","install_details":"shymenu is only effective when the menubar is hidden. To to this, \r\nadd this line to your vimrc file:\r\n\r\n  set guioptions-=m\r\n\r\nEdit the vba file and type: >\r\n\r\n    :so %\r\n\r\nSee :help vimball for details. If you have difficulties or use vim 7.0, \r\nplease make sure, you have the current version of vimball\r\n(vimscript #1502) installed or update your runtime.\r\n\r\n\r\nAlso available via git\r\nhttp:\/\/github.com\/tomtom\/shymenu_vim","5":"shymenu is only effective when the menubar is hidden. To to this, \r\nadd this line to your vimrc file:\r\n\r\n  set guioptions-=m\r\n\r\nEdit the vba file and type: >\r\n\r\n    :so %\r\n\r\nSee :help vimball for details. If you have difficulties or use vim 7.0, \r\nplease make sure, you have the current version of vimball\r\n(vimscript #1502) installed or update your runtime.\r\n\r\n\r\nAlso available via git\r\nhttp:\/\/github.com\/tomtom\/shymenu_vim","first_name":"Tom","6":"Tom","last_name":"Link","7":"Link","releases":[{"0":"2437","vim_version":"7.0","1":"7.0","script_version":"0.3","2":"0.3","version_comment":"- Correct line offset if necessary\r\n- Set g:shymenu_wildcharm from &wildcharm\r\n","3":"- Correct line offset if necessary\r\n- Set g:shymenu_wildcharm from &wildcharm\r\n","package":"shymenu.vba.gz","4":"shymenu.vba.gz","src_id":"9516","5":"9516","creation_date":"1226994801","6":"1226994801"},{"0":"2437","vim_version":"7.0","1":"7.0","script_version":"0.2","2":"0.2","version_comment":"Disable insert mode maps by default (conflict with international characters). Set g:shymenu_modes = \"ni\" to re-enable them.","3":"Disable insert mode maps by default (conflict with international characters). Set g:shymenu_modes = \"ni\" to re-enable them.","package":"shymenu.vba.gz","4":"shymenu.vba.gz","src_id":"9495","5":"9495","creation_date":"1226558283","6":"1226558283"},{"0":"2437","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"shymenu.vba.gz","4":"shymenu.vba.gz","src_id":"9491","5":"9491","creation_date":"1226507539","6":"1226507539"}]},"2436":{"script_id":"2436","0":"2436","script_name":"fuzzyjump.vim","1":"fuzzyjump.vim","script_type":"utility","2":"utility","summary":"Jump to where you (almost) want","3":"Jump to where you (almost) want","description":"FuzzyJump is a Vim plugin to jump the cursor where you want like a pointing\r\ndevice such as a mouse.  This plugin maps most of keys on a keyboard to\r\nrelative positions in the current buffer.  For example. if your screen looks\r\nlike:\r\n\r\nmapping image of buffer and keyboard:\r\nhttp:\/\/farm4.static.flickr.com\/3253\/3021764786_5cf2efe7d5_o.png\r\n\r\n\t+-----------------------------------------------------+\r\n\t|if where git &>\/dev\/null; then                       |\r\n\t|  function prompt-git-head-name() {                  |\r\n\t|    if ! [ -d .git ]; then                           |\r\n\t|      return 1                                       |\r\n\t|    fi                                               |\r\n\t|    local head_name                                  |\r\n\t|    head_name=\"$(git branch | sed -e 's\/^\\* \/\/;t;d')\"|\r\n\t|\"foo.sh\" [New file]                                  |\r\n\t+-----------------------------------------------------+\r\n\r\nthen the correspondences of keys and positions are as follow (where {X} means\r\nthat key \"X\" is corresponding to the position where it is written).\r\n\r\n\t+-----------------------------------------------------+\r\n\t|{1}wh{2} g{3}&>{4}v\/{5}l;{6}en{7}  {8}  {9}  {0}  {-}|\r\n\t|  function prompt-git-head-name() {                  |\r\n\t|{q} i{w} [{e} .{r} ]{t}he{y}  {u}  {i}  {o}  {p}  {@}|\r\n\t|      return 1                                       |\r\n        |{a} f{s}  {d}  {f}  {g}  {h}  {j}  {k}  {l}  {;}  {:}|\r\n\t|    local head_name                                  |\r\n\t|{z} h{x}_n{c}=\"{v}it{b}an{n}| {m} -{,}s\/{.} \/{\/};d{\\}|\r\n\t|\"foo.sh\" [New file]                                  |\r\n\t+-----------------------------------------------------+\r\n\r\nBy default, this plugin defined 2-stroke key mappings to jump to one of the\r\nabove positions.  The key mappings consist of the common prefix \";\" (which can\r\nbe customized to any key sequence; see |<Plug>(fuzzyjump-prefix)|) and one of\r\nthe above keys.  For example, if you type \";1\", the cursor will move to the\r\nposition near {1} in the above figure.  For some keys such as {9}, there is no\r\ntext and it's not possible to move the cursor to the position, if so, this\r\nplugin moves the cursor to one of the most useful positions near the specified\r\nposition.\r\n\r\nNote that the original author doesn't consider about keyboard layouts other\r\nthan JIS layout.  So the above figure and the default key mappings are\r\nsomewhat strange for non-Japanese users.\r\nhttp:\/\/en.wikipedia.org\/wiki\/Image:KB_Japanese.svg\r\n\r\n* I'm using japanese layout keyboard, so I don't know how does it work in other layout keyboard.\r\n\r\nBlog entry:\r\n[English] http:\/\/blog.endflow.net\/?p=175〈=en\r\n[Japanese] http:\/\/blog.endflow.net\/?p=175〈=ja\r\n\r\nRequirements:\r\n- Vim 7.1 or later\r\n\r\nSpecial thanks:\r\n-kana [http:\/\/whileimautomaton.net\/]: bugfix & help file in 0.1.1\r\n\r\n","4":"FuzzyJump is a Vim plugin to jump the cursor where you want like a pointing\r\ndevice such as a mouse.  This plugin maps most of keys on a keyboard to\r\nrelative positions in the current buffer.  For example. if your screen looks\r\nlike:\r\n\r\nmapping image of buffer and keyboard:\r\nhttp:\/\/farm4.static.flickr.com\/3253\/3021764786_5cf2efe7d5_o.png\r\n\r\n\t+-----------------------------------------------------+\r\n\t|if where git &>\/dev\/null; then                       |\r\n\t|  function prompt-git-head-name() {                  |\r\n\t|    if ! [ -d .git ]; then                           |\r\n\t|      return 1                                       |\r\n\t|    fi                                               |\r\n\t|    local head_name                                  |\r\n\t|    head_name=\"$(git branch | sed -e 's\/^\\* \/\/;t;d')\"|\r\n\t|\"foo.sh\" [New file]                                  |\r\n\t+-----------------------------------------------------+\r\n\r\nthen the correspondences of keys and positions are as follow (where {X} means\r\nthat key \"X\" is corresponding to the position where it is written).\r\n\r\n\t+-----------------------------------------------------+\r\n\t|{1}wh{2} g{3}&>{4}v\/{5}l;{6}en{7}  {8}  {9}  {0}  {-}|\r\n\t|  function prompt-git-head-name() {                  |\r\n\t|{q} i{w} [{e} .{r} ]{t}he{y}  {u}  {i}  {o}  {p}  {@}|\r\n\t|      return 1                                       |\r\n        |{a} f{s}  {d}  {f}  {g}  {h}  {j}  {k}  {l}  {;}  {:}|\r\n\t|    local head_name                                  |\r\n\t|{z} h{x}_n{c}=\"{v}it{b}an{n}| {m} -{,}s\/{.} \/{\/};d{\\}|\r\n\t|\"foo.sh\" [New file]                                  |\r\n\t+-----------------------------------------------------+\r\n\r\nBy default, this plugin defined 2-stroke key mappings to jump to one of the\r\nabove positions.  The key mappings consist of the common prefix \";\" (which can\r\nbe customized to any key sequence; see |<Plug>(fuzzyjump-prefix)|) and one of\r\nthe above keys.  For example, if you type \";1\", the cursor will move to the\r\nposition near {1} in the above figure.  For some keys such as {9}, there is no\r\ntext and it's not possible to move the cursor to the position, if so, this\r\nplugin moves the cursor to one of the most useful positions near the specified\r\nposition.\r\n\r\nNote that the original author doesn't consider about keyboard layouts other\r\nthan JIS layout.  So the above figure and the default key mappings are\r\nsomewhat strange for non-Japanese users.\r\nhttp:\/\/en.wikipedia.org\/wiki\/Image:KB_Japanese.svg\r\n\r\n* I'm using japanese layout keyboard, so I don't know how does it work in other layout keyboard.\r\n\r\nBlog entry:\r\n[English] http:\/\/blog.endflow.net\/?p=175〈=en\r\n[Japanese] http:\/\/blog.endflow.net\/?p=175〈=ja\r\n\r\nRequirements:\r\n- Vim 7.1 or later\r\n\r\nSpecial thanks:\r\n-kana [http:\/\/whileimautomaton.net\/]: bugfix & help file in 0.1.1\r\n\r\n","install_details":"Extract zip archive to your .vim directory.","5":"Extract zip archive to your .vim directory.","first_name":"Yuki ","6":"Yuki ","last_name":"KODAMA","7":"KODAMA","releases":[{"0":"2436","vim_version":"7.0","1":"7.0","script_version":"0.1.1","2":"0.1.1","version_comment":"- Add |<Plug>(fuzzyjump-prefix)| to customize and remove other stuffs to customize.\r\n- Fix the following bugs:\r\n-- Remove unnecessary variables.\r\n-- Fix key mappings to move the cursor which didn't properly work if [count] is given.\r\n-- Fix key mappings to move the cursor which weren't also defined in Visual mode and Operator-pending mode.\r\n\r\n","3":"- Add |<Plug>(fuzzyjump-prefix)| to customize and remove other stuffs to customize.\r\n- Fix the following bugs:\r\n-- Remove unnecessary variables.\r\n-- Fix key mappings to move the cursor which didn't properly work if [count] is given.\r\n-- Fix key mappings to move the cursor which weren't also defined in Visual mode and Operator-pending mode.\r\n\r\n","package":"fuzzyjump.zip","4":"fuzzyjump.zip","src_id":"9511","5":"9511","creation_date":"1226855128","6":"1226855128"},{"0":"2436","vim_version":"7.0","1":"7.0","script_version":"0.1.0","2":"0.1.0","version_comment":"Initial upload","3":"Initial upload","package":"fuzzyjump.vim","4":"fuzzyjump.vim","src_id":"9483","5":"9483","creation_date":"1226388829","6":"1226388829"}]},"2435":{"script_id":"2435","0":"2435","script_name":"Php Doc","1":"Php Doc","script_type":"ftplugin","2":"ftplugin","summary":"Open's PHP Documentation in Web Browser","3":"Open's PHP Documentation in Web Browser","description":"This script will open the current word\/function underneath the cursor in your default Web Browser.","4":"This script will open the current word\/function underneath the cursor in your default Web Browser.","install_details":"Must have vim with +python. Place php_doc.vim into your ~\/.vim\/ftplugin folder.","5":"Must have vim with +python. Place php_doc.vim into your ~\/.vim\/ftplugin folder.","first_name":"Travis","6":"Travis","last_name":"Jeffery","7":"Jeffery","releases":[{"0":"2435","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"php_doc.vim","4":"php_doc.vim","src_id":"9482","5":"9482","creation_date":"1226388803","6":"1226388803"}]},"2434":{"script_id":"2434","0":"2434","script_name":"Side-C","1":"Side-C","script_type":"utility","2":"utility","summary":"a simple IDE for C\/C++","3":"a simple IDE for C\/C++","description":"Side-C is a small plug-in implementing basic IDE functionality for developing one-file C or C++ programs.  It automates the following actions.\r\n\r\n* Finding the program file among several open (so that to know what to compile or what and where to run).\r\n\r\n* Building a program from its source.  The error message ('quickfix') window is being shown or hidden as needed.\r\n\r\n* Running a program from wherever it resides.  Building it first if necessary.\r\n\r\n* Running a program with redirecting its standard input, output, or both.\r\n\r\n* Opening a browser for the directory of the currently edited file.\r\n\r\n* Running an o.s. command shell in the directory of the currently edited file.\r\n\r\nThe plug-in is designed and tested to work on Linux and MS DOS\/MS Windows, using gcc on both (DJGPP in the case of MS Windows).  It should work on other Unix systems as well.  With small changes, it should be possible to tailor it to other operating systems and compilers.\r\n\r\nSee the comments in the plug-in itself for more details.","4":"Side-C is a small plug-in implementing basic IDE functionality for developing one-file C or C++ programs.  It automates the following actions.\r\n\r\n* Finding the program file among several open (so that to know what to compile or what and where to run).\r\n\r\n* Building a program from its source.  The error message ('quickfix') window is being shown or hidden as needed.\r\n\r\n* Running a program from wherever it resides.  Building it first if necessary.\r\n\r\n* Running a program with redirecting its standard input, output, or both.\r\n\r\n* Opening a browser for the directory of the currently edited file.\r\n\r\n* Running an o.s. command shell in the directory of the currently edited file.\r\n\r\nThe plug-in is designed and tested to work on Linux and MS DOS\/MS Windows, using gcc on both (DJGPP in the case of MS Windows).  It should work on other Unix systems as well.  With small changes, it should be possible to tailor it to other operating systems and compilers.\r\n\r\nSee the comments in the plug-in itself for more details.","install_details":"Put the file in a plug-in directory, or source it directly","5":"Put the file in a plug-in directory, or source it directly","first_name":"Boyko","6":"Boyko","last_name":"Bantchev","7":"Bantchev","releases":[{"0":"2434","vim_version":"7.0","1":"7.0","script_version":"1.1+(3)","2":"1.1+(3)","version_comment":"small additions and corrections","3":"small additions and corrections","package":"side-c.vim","4":"side-c.vim","src_id":"14903","5":"14903","creation_date":"1296298137","6":"1296298137"},{"0":"2434","vim_version":"7.0","1":"7.0","script_version":"1.1+","2":"1.1+","version_comment":"a bug fixed that prevented the quickfix list from properly creating & displaying","3":"a bug fixed that prevented the quickfix list from properly creating & displaying","package":"side-c.vim","4":"side-c.vim","src_id":"9678","5":"9678","creation_date":"1229329660","6":"1229329660"},{"0":"2434","vim_version":"7.0","1":"7.0","script_version":"1.1","2":"1.1","version_comment":"bugs removed, doc typos corrected, some improvements made ","3":"bugs removed, doc typos corrected, some improvements made ","package":"side-c.vim","4":"side-c.vim","src_id":"9490","5":"9490","creation_date":"1226483169","6":"1226483169"},{"0":"2434","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"side-c.vim","4":"side-c.vim","src_id":"9472","5":"9472","creation_date":"1226258091","6":"1226258091"}]},"2433":{"script_id":"2433","0":"2433","script_name":"W3AF script syntax file","1":"W3AF script syntax file","script_type":"syntax","2":"syntax","summary":"Script syntax file for  w3af (Web Application Attack and Audit Framework)","3":"Script syntax file for  w3af (Web Application Attack and Audit Framework)","description":"Script syntax file for  w3af (Web Application Attack and Audit Framework)\r\nhttp:\/\/w3af.sourceforge.net\/","4":"Script syntax file for  w3af (Web Application Attack and Audit Framework)\r\nhttp:\/\/w3af.sourceforge.net\/","install_details":"Simply copy it to your ~\/.vim\/syntax folder and add\r\n\r\n\" Filetipes\r\nau BufRead,BufNewFile *.w3af\t\tset filetype=w3af\r\n\r\nto your ~\/.vimrc\r\n","5":"Simply copy it to your ~\/.vim\/syntax folder and add\r\n\r\n\" Filetipes\r\nau BufRead,BufNewFile *.w3af\t\tset filetype=w3af\r\n\r\nto your ~\/.vimrc\r\n","first_name":"pento","6":"pento","last_name":"pento","7":"pento","releases":[{"0":"2433","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"w3af.vim","4":"w3af.vim","src_id":"9469","5":"9469","creation_date":"1226244841","6":"1226244841"}]},"2432":{"script_id":"2432","0":"2432","script_name":"corporation","1":"corporation","script_type":"color scheme","2":"color scheme","summary":"A dark grey, yellow and blue theme that doesn't hurt the eyes.","3":"A dark grey, yellow and blue theme that doesn't hurt the eyes.","description":"A dark grey, yellow, blue and a little orange scheme that is easy on the eyes and quite readable imho.\r\n\r\nBased on julievonderropp's corporation available on kuler.adobe.com.\r\n\r\nI have a very strong feeling it reminds of the colours of some logo, but I can't remember which. I have the impression it had the head of an eagle in it but I'm not sure. If anybody knows what I'm thinking about, pleaeaease drop me a line!","4":"A dark grey, yellow, blue and a little orange scheme that is easy on the eyes and quite readable imho.\r\n\r\nBased on julievonderropp's corporation available on kuler.adobe.com.\r\n\r\nI have a very strong feeling it reminds of the colours of some logo, but I can't remember which. I have the impression it had the head of an eagle in it but I'm not sure. If anybody knows what I'm thinking about, pleaeaease drop me a line!","install_details":"Place in your Vim colour schemes directory (probably ~\/.vim\/colors) for autoloading on startup and :source it or restart Vim, or just anywhere and :source it.","5":"Place in your Vim colour schemes directory (probably ~\/.vim\/colors) for autoloading on startup and :source it or restart Vim, or just anywhere and :source it.","first_name":"kamil","6":"kamil","last_name":"stachowski","7":"stachowski","releases":[{"0":"2432","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"corporation.vim","4":"corporation.vim","src_id":"9465","5":"9465","creation_date":"1226176876","6":"1226176876"}]},"2431":{"script_id":"2431","0":"2431","script_name":"commentToggle","1":"commentToggle","script_type":"utility","2":"utility","summary":"A simple line-based comment toggler.","3":"A simple line-based comment toggler.","description":"Toggles comment for selected lines. If the selection is commented, commentToggle uncomments it; if it\u00e2\u0080\u0099s not commented, commetToggle comments it; if it\u00e2\u0080\u0099s mixed, the above is applied on a per-line basis. Very useful. I know, there are plenty of commenters out there, but this one\u00e2\u0080\u0099s mine. And it\u00e2\u0080\u0099s much simpler. One shortcut (<Leader>;) and that\u00e2\u0080\u0099s that.","4":"Toggles comment for selected lines. If the selection is commented, commentToggle uncomments it; if it\u00e2\u0080\u0099s not commented, commetToggle comments it; if it\u00e2\u0080\u0099s mixed, the above is applied on a per-line basis. Very useful. I know, there are plenty of commenters out there, but this one\u00e2\u0080\u0099s mine. And it\u00e2\u0080\u0099s much simpler. One shortcut (<Leader>;) and that\u00e2\u0080\u0099s that.","install_details":"Copy to your plugins directory (probably ~\/.vim\/plugins) and restart Vim or place anywhere and :source it.\r\nOr use this address with your favourite package manager: https:\/\/github.com\/kamwitsta\/commentToggle","5":"Copy to your plugins directory (probably ~\/.vim\/plugins) and restart Vim or place anywhere and :source it.\r\nOr use this address with your favourite package manager: https:\/\/github.com\/kamwitsta\/commentToggle","first_name":"kamil","6":"kamil","last_name":"stachowski","7":"stachowski","releases":[{"0":"2431","vim_version":"7.0","1":"7.0","script_version":"0.3","2":"0.3","version_comment":"a bit of a rewrite, now uses commentstring (duh\u00e2\u0080\u00a6)","3":"a bit of a rewrite, now uses commentstring (duh\u00e2\u0080\u00a6)","package":"commentToggle.vim","4":"commentToggle.vim","src_id":"24691","5":"24691","creation_date":"1477956761","6":"1477956761"},{"0":"2431","vim_version":"6.0","1":"6.0","script_version":"0.2","2":"0.2","version_comment":"improved whitespace handling (now prettier than ever ;)\r\nadded 37 new languages (total 93)","3":"improved whitespace handling (now prettier than ever ;)\r\nadded 37 new languages (total 93)","package":"commentToggle.vim","4":"commentToggle.vim","src_id":"9481","5":"9481","creation_date":"1226359692","6":"1226359692"},{"0":"2431","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"commentToggle.vim","4":"commentToggle.vim","src_id":"9464","5":"9464","creation_date":"1226170112","6":"1226170112"}]},"2430":{"script_id":"2430","0":"2430","script_name":"literal_tango.vim","1":"literal_tango.vim","script_type":"color scheme","2":"color scheme","summary":"A Tango-based colorscheme with good contrast, yet easy on the eyes","3":"A Tango-based colorscheme with good contrast, yet easy on the eyes","description":"A color scheme with good contrast, yet easy on the eyes.\r\nLooks the same in the GUI as it does on a 16 color terminal.\r\nUses the Tango color palette (http:\/\/tango.freedesktop.org).\r\n\r\nhttp:\/\/img134.imageshack.us\/img134\/9471\/literaltango.png\r\n\r\nTerminal users:\r\nIntended for display on a black (#000000) background with a text color\r\nof #d3d7cf. Also make sure your terminal is using the Tango color \r\npalette. GNOME Terminal uses it by default. Linux console users, see\r\nhttp:\/\/search.cpan.org\/perldoc?conpalette\r\nAlso make sure that background=dark in vim.","4":"A color scheme with good contrast, yet easy on the eyes.\r\nLooks the same in the GUI as it does on a 16 color terminal.\r\nUses the Tango color palette (http:\/\/tango.freedesktop.org).\r\n\r\nhttp:\/\/img134.imageshack.us\/img134\/9471\/literaltango.png\r\n\r\nTerminal users:\r\nIntended for display on a black (#000000) background with a text color\r\nof #d3d7cf. Also make sure your terminal is using the Tango color \r\npalette. GNOME Terminal uses it by default. Linux console users, see\r\nhttp:\/\/search.cpan.org\/perldoc?conpalette\r\nAlso make sure that background=dark in vim.","install_details":"Drop this file in your $VIMRUNTIME\/colors\/ directory","5":"Drop this file in your $VIMRUNTIME\/colors\/ directory","first_name":"Hinrik \u00c3\u0096rn","6":"Hinrik \u00c3\u0096rn","last_name":"Sigur\u00c3\u00b0sson","7":"Sigur\u00c3\u00b0sson","releases":[{"0":"2430","vim_version":"6.0","1":"6.0","script_version":"1.7","2":"1.7","version_comment":"Used a brighter color for Include\r\nMade Function look distinct from Identifier","3":"Used a brighter color for Include\r\nMade Function look distinct from Identifier","package":"literal_tango.vim","4":"literal_tango.vim","src_id":"10374","5":"10374","creation_date":"1239339299","6":"1239339299"},{"0":"2430","vim_version":"6.0","1":"6.0","script_version":"1.6","2":"1.6","version_comment":"Changed 'Label', 'SpecialKey', 'Type', 'SpecialChar', 'Delimiter', and 'Exception'","3":"Changed 'Label', 'SpecialKey', 'Type', 'SpecialChar', 'Delimiter', and 'Exception'","package":"literal_tango.vim","4":"literal_tango.vim","src_id":"9694","5":"9694","creation_date":"1229575093","6":"1229575093"},{"0":"2430","vim_version":"6.0","1":"6.0","script_version":"1.5","2":"1.5","version_comment":"Use a brighter color for 'Special' to make it more distinct","3":"Use a brighter color for 'Special' to make it more distinct","package":"literal_tango.vim","4":"literal_tango.vim","src_id":"9476","5":"9476","creation_date":"1226309103","6":"1226309103"},{"0":"2430","vim_version":"6.0","1":"6.0","script_version":"1.4","2":"1.4","version_comment":"Now looks right on a linux console regardless of 'background' setting","3":"Now looks right on a linux console regardless of 'background' setting","package":"literal_tango.vim","4":"literal_tango.vim","src_id":"9474","5":"9474","creation_date":"1226261679","6":"1226261679"},{"0":"2430","vim_version":"6.0","1":"6.0","script_version":"1.3","2":"1.3","version_comment":"Made 'WildMenu' look consistent in GUI\/terminal\r\nMade 'Title', 'Directory', and 'SpecialKey' look more readable","3":"Made 'WildMenu' look consistent in GUI\/terminal\r\nMade 'Title', 'Directory', and 'SpecialKey' look more readable","package":"literal_tango.vim","4":"literal_tango.vim","src_id":"9471","5":"9471","creation_date":"1226247444","6":"1226247444"},{"0":"2430","vim_version":"6.0","1":"6.0","script_version":"1.2","2":"1.2","version_comment":"Use darker colors for diffs, popup menus, vertical splits,\r\nmatched parens, fold columns, and the status line.","3":"Use darker colors for diffs, popup menus, vertical splits,\r\nmatched parens, fold columns, and the status line.","package":"literal_tango.vim","4":"literal_tango.vim","src_id":"9468","5":"9468","creation_date":"1226240605","6":"1226240605"},{"0":"2430","vim_version":"6.0","1":"6.0","script_version":"1.1","2":"1.1","version_comment":"Gave 'Type' a color\r\nLinked 'Repeat' and 'Conditional' to 'Statement' again\r\nFixed a few GUI<->terminal inconsistencies","3":"Gave 'Type' a color\r\nLinked 'Repeat' and 'Conditional' to 'Statement' again\r\nFixed a few GUI<->terminal inconsistencies","package":"literal_tango.vim","4":"literal_tango.vim","src_id":"9467","5":"9467","creation_date":"1226230316","6":"1226230316"},{"0":"2430","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"literal_tango.vim","4":"literal_tango.vim","src_id":"9463","5":"9463","creation_date":"1226163454","6":"1226163454"}]},"2429":{"script_id":"2429","0":"2429","script_name":"autocorrect.vim","1":"autocorrect.vim","script_type":"utility","2":"utility","summary":"Correct common typos and misspellings as you type","3":"Correct common typos and misspellings as you type","description":"Looking through the examples in Vim, there are examples of correcting typos and misspellings like:\r\n\r\niabbrev teh the\r\niabbrev het the\r\n...\r\n\r\nHowever, it is very time-consuming to create this list by hand.  You also have to enter the correct capitalization, which is a pain.  ('teh->the' is not equal to 'Teh->The')\r\n\r\nIt seems silly for everyone to create their own autocorrect file, so hopefully we can work together to make a sweet list.  I found a nice list from Wikipedia and cleaned it up a bit as a basis, and incorporated the typo fixes from Vim Cream.  I also added some words that I commonly misspelled or mistyped, and have taken additional contributions from users of the script.\r\n\r\nI'm sure there are some mistakes, or common mistakes that aren't in here yet, so if you find any, please contact me and I will gladly change things.  There are some additional details or thoughts as well as a shortcut to a word-processing mode at http:\/\/22ideastreet.com\/blog\/2008\/11\/06\/vim-word-processing.\r\n\r\nI find this script invaluable when using Mozex to edit forms online (blog posts, web mail, etc.)\r\n\r\nThere is a GitHub repository that you can contribute to at http:\/\/github.com\/panozzaj\/vim-autocorrect\/tree\/master","4":"Looking through the examples in Vim, there are examples of correcting typos and misspellings like:\r\n\r\niabbrev teh the\r\niabbrev het the\r\n...\r\n\r\nHowever, it is very time-consuming to create this list by hand.  You also have to enter the correct capitalization, which is a pain.  ('teh->the' is not equal to 'Teh->The')\r\n\r\nIt seems silly for everyone to create their own autocorrect file, so hopefully we can work together to make a sweet list.  I found a nice list from Wikipedia and cleaned it up a bit as a basis, and incorporated the typo fixes from Vim Cream.  I also added some words that I commonly misspelled or mistyped, and have taken additional contributions from users of the script.\r\n\r\nI'm sure there are some mistakes, or common mistakes that aren't in here yet, so if you find any, please contact me and I will gladly change things.  There are some additional details or thoughts as well as a shortcut to a word-processing mode at http:\/\/22ideastreet.com\/blog\/2008\/11\/06\/vim-word-processing.\r\n\r\nI find this script invaluable when using Mozex to edit forms online (blog posts, web mail, etc.)\r\n\r\nThere is a GitHub repository that you can contribute to at http:\/\/github.com\/panozzaj\/vim-autocorrect\/tree\/master","install_details":"You can just type :source \/path\/to\/the\/autocorrect.vim to load up the corrections.\r\n\r\nI recommend putting autocorrect.vim in your vimfiles directory somewhere and then sourcing it when you want autocorrect to be enabled.  The other two files included in the .tar file are just to generate the list.  I would not recommend adding directly to autocorrect.vim, as these changes will get wiped out whenever you regenerate.  Ruby is necessary to generate from the data file, but a generated file is included in the .tar, so you can start immediately!","5":"You can just type :source \/path\/to\/the\/autocorrect.vim to load up the corrections.\r\n\r\nI recommend putting autocorrect.vim in your vimfiles directory somewhere and then sourcing it when you want autocorrect to be enabled.  The other two files included in the .tar file are just to generate the list.  I would not recommend adding directly to autocorrect.vim, as these changes will get wiped out whenever you regenerate.  Ruby is necessary to generate from the data file, but a generated file is included in the .tar, so you can start immediately!","first_name":"Anthony","6":"Anthony","last_name":"Panozzo","7":"Panozzo","releases":[{"0":"2429","vim_version":"6.0","1":"6.0","script_version":"1.03","2":"1.03","version_comment":"Thanks to Gilles Bertrand for sending me a list containing a bunch of new corrections!  Many of the corrections are longer or more technical in nature.  In addition, I created a file in the GitHub repository that contains multiple word corrections in case this is ever easy to do in the future with Vim.  I also added a README in the tar file itself.","3":"Thanks to Gilles Bertrand for sending me a list containing a bunch of new corrections!  Many of the corrections are longer or more technical in nature.  In addition, I created a file in the GitHub repository that contains multiple word corrections in case this is ever easy to do in the future with Vim.  I also added a README in the tar file itself.","package":"autocorrect.tar","4":"autocorrect.tar","src_id":"10423","5":"10423","creation_date":"1240182033","6":"1240182033"},{"0":"2429","vim_version":"6.0","1":"6.0","script_version":"1.02","2":"1.02","version_comment":"Found that Cream had an abbreviation file, so I took any words that were in there that I didn't already have and added them (about thirty, with some day of the week capitalization.)  Changed output of generator to recognize when a fix was just a capitalization.  Reduced size of final file by changing from 'iabbrev' to 'ia' (8000*5 characters!)  Also went through and deleted corrections of dubious quality and fixed some problems in the source file.  Added a couple of things that I've made mistakes on in the past two months.  All in all, a bunch of nice changes, less lines and size and more autocorrectionness.","3":"Found that Cream had an abbreviation file, so I took any words that were in there that I didn't already have and added them (about thirty, with some day of the week capitalization.)  Changed output of generator to recognize when a fix was just a capitalization.  Reduced size of final file by changing from 'iabbrev' to 'ia' (8000*5 characters!)  Also went through and deleted corrections of dubious quality and fixed some problems in the source file.  Added a couple of things that I've made mistakes on in the past two months.  All in all, a bunch of nice changes, less lines and size and more autocorrectionness.","package":"autocorrect.tar","4":"autocorrect.tar","src_id":"9900","5":"9900","creation_date":"1233525861","6":"1233525861"},{"0":"2429","vim_version":"6.0","1":"6.0","script_version":"1.01","2":"1.01","version_comment":"Added mistakes that I have made over the last month that should have been autocorrected.\r\n\r\nConverted from dos line endings to unix ones.  Before I did this, it worked fine on the Windows box, but would cause a line break to be inserted on other operating systems when space was pressed.","3":"Added mistakes that I have made over the last month that should have been autocorrected.\r\n\r\nConverted from dos line endings to unix ones.  Before I did this, it worked fine on the Windows box, but would cause a line break to be inserted on other operating systems when space was pressed.","package":"autocorrect.tar","4":"autocorrect.tar","src_id":"9618","5":"9618","creation_date":"1228533294","6":"1228533294"},{"0":"2429","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"autocorrect.tar","4":"autocorrect.tar","src_id":"9446","5":"9446","creation_date":"1226028432","6":"1226028432"}]},"2428":{"script_id":"2428","0":"2428","script_name":"LineCommenter","1":"LineCommenter","script_type":"utility","2":"utility","summary":"Toggle Comment state of line.(C\/C++\/Java\/perl\/python\/ruby\/awk\/sh\/104 languages)","3":"Toggle Comment state of line.(C\/C++\/Java\/perl\/python\/ruby\/awk\/sh\/104 languages)","description":"Toggle Comment state of line.(C\/C++\/Java\/perl\/python\/ruby\/awk\/sh\/104 languages)\r\n\r\n<Esc>cc     Toggle comment state of the current line\r\n<Esc>ncc   Toggle n straight lines.\r\n\r\nSupported file type:    Over 104 languages\r\n\r\n   \/\/:        C, C++, java, javascript, etc.\r\n   #:        awk, makefile, perl, python, ruby, sed, sh, etc.\r\n   \":         vim\r\n   ':         asp, basic, vbscript\r\n   ;:         asm, ini, etc.\r\n   rem :  bat\r\n   --:       sql, etc.\r\n   %:      matlab, tex, etc.\r\n...\r\n","4":"Toggle Comment state of line.(C\/C++\/Java\/perl\/python\/ruby\/awk\/sh\/104 languages)\r\n\r\n<Esc>cc     Toggle comment state of the current line\r\n<Esc>ncc   Toggle n straight lines.\r\n\r\nSupported file type:    Over 104 languages\r\n\r\n   \/\/:        C, C++, java, javascript, etc.\r\n   #:        awk, makefile, perl, python, ruby, sed, sh, etc.\r\n   \":         vim\r\n   ':         asp, basic, vbscript\r\n   ;:         asm, ini, etc.\r\n   rem :  bat\r\n   --:       sql, etc.\r\n   %:      matlab, tex, etc.\r\n...\r\n","install_details":"Just drop this script file into vim's plugin directory.","5":"Just drop this script file into vim's plugin directory.","first_name":"x","6":"x","last_name":"sq","7":"sq","releases":[{"0":"2428","vim_version":"7.0","1":"7.0","script_version":"2.0.0","2":"2.0.0","version_comment":"1.Some optimization\r\n2.Add some new languages,  total 104 languages","3":"1.Some optimization\r\n2.Add some new languages,  total 104 languages","package":"LineCommenter.vim","4":"LineCommenter.vim","src_id":"9489","5":"9489","creation_date":"1226477304","6":"1226477304"}]},"2427":{"script_id":"2427","0":"2427","script_name":"code_complete (new update)","1":"code_complete (new update)","script_type":"utility","2":"utility","summary":"function parameter complete, code snippets, and much more. ","3":"function parameter complete, code snippets, and much more. ","description":"see the origin script here:vimscript #1764\r\nand there is a screenshot: http:\/\/files.myopera.com\/mbbill\/files\/code_complete.gif\r\n\r\nInstall:          1.  Put code_complete.vim and my_snippets.template\r\n                       to plugin directory.\r\n                     2.  Use the command below to create tags file\r\n                       including signature field.\r\n                       ctags -R --c-kinds=+p --fields=+S .\r\n\r\n Usage:\r\n                   hotkey:\r\n\r\n                       \"<A-d>\" (default value of g:CodeCompl_Hotkey)\r\n                       we DON'T use <tab>, because it comflict with\r\n                       superstab.vim, you will quickly find Alt-S\r\n                       will be a good choice.  Do all the jobs with\r\n                       this key, see example:\r\n                       press <A-d> after function name and (\r\n                           foo ( <A-d>\r\n                       becomes:\r\n                           foo ( `<first param>`,`<second param>` )\r\n                       press <A-D> after code template\r\n                           if <A-d>\r\n                       becomes:\r\n                           if( `<...>` )\r\n                           {\r\n                               `<...>`\r\n                           }\r\n\r\n\r\n                   variables:\r\n\r\n                       g:CodeCompl_Hotkey\r\n                           the key used to complete function\r\n                           parameters and key words. after you press\r\n                           ths key AFTER you input the complete-word,\r\n                           the word will be spreaded. you can see the\r\n                           paragraph above for detail features.\r\n\r\n                       g:CodeCompl_RegionStart g:CodeCompl_RegionEnd\r\n                           region start and stop you can change them\r\n                           as you like.  but you must be careful,\r\n                           because we use them to detemin marks in\r\n                           your template files(not complete file), so\r\n                           if you change it, maybe you must\r\n                           substitute all marks in your template\r\n                           files. after you change them, maybe you\r\n                           should update your template file, you can\r\n                           use this command:\r\n                           :UpdateTemplate<CR>\r\n\r\n                       g:CodeCompl_Template_Forechar\r\n                           you can use template file with\r\n                           template-forechar, you can create a file\r\n                           named 'complete-word.filetype',\r\n                           and drop it in\r\n                           g:CodeCompl_Template_Folder(default, it's\r\n                           'templates' in your runtimepath, e.g.\r\n                           D:\\Vim\\vimfiles\\templates in windows, or\r\n                           \/root\/.vim\/templates in linux\/unix.\r\n                           after you create file, you can input\r\n                           forechar + complete-word to include the\r\n                           whole file. e.g. '#stdc' to include stdc.c\r\n                           if your current filetype is 'c'.\r\n\r\n                       g:CodeCompl_Template_Folder\r\n                           see paragraph above. the folder default is\r\n                           'templates'.\r\n\r\n                       g:CodeCompl_Complete_File\r\n                           file name of users defined snippets.  now\r\n                           it named 'my_snippets.template', use this\r\n                           postfix to prevent Vim load it\r\n                           automatically\r\n\r\n                       g:CodeCompl_ClearWhenUpdate\r\n                           see the Option section\r\n\r\n                       g:CodeCompl_SaveListInBuffer\r\n                            Save complete list and template file list only in buffer\r\n\r\n\r\n                   global helper functions:\r\n                       \r\n                       MakeRegion\r\n                           same as g:CodeCompl_RegionStart . 'your\r\n                           text' . g:CodeCompl_RegionEnd, but input a\r\n                           little easily, but there are other helper\r\n                           function and variables in your complete\r\n\r\n                           file(defaults is my_snippets.template in\r\n                           your plugin folder)\r\n\r\n                   default complete-words:\r\n                           see \"my_snippets.template\" file.\r\n","4":"see the origin script here:vimscript #1764\r\nand there is a screenshot: http:\/\/files.myopera.com\/mbbill\/files\/code_complete.gif\r\n\r\nInstall:          1.  Put code_complete.vim and my_snippets.template\r\n                       to plugin directory.\r\n                     2.  Use the command below to create tags file\r\n                       including signature field.\r\n                       ctags -R --c-kinds=+p --fields=+S .\r\n\r\n Usage:\r\n                   hotkey:\r\n\r\n                       \"<A-d>\" (default value of g:CodeCompl_Hotkey)\r\n                       we DON'T use <tab>, because it comflict with\r\n                       superstab.vim, you will quickly find Alt-S\r\n                       will be a good choice.  Do all the jobs with\r\n                       this key, see example:\r\n                       press <A-d> after function name and (\r\n                           foo ( <A-d>\r\n                       becomes:\r\n                           foo ( `<first param>`,`<second param>` )\r\n                       press <A-D> after code template\r\n                           if <A-d>\r\n                       becomes:\r\n                           if( `<...>` )\r\n                           {\r\n                               `<...>`\r\n                           }\r\n\r\n\r\n                   variables:\r\n\r\n                       g:CodeCompl_Hotkey\r\n                           the key used to complete function\r\n                           parameters and key words. after you press\r\n                           ths key AFTER you input the complete-word,\r\n                           the word will be spreaded. you can see the\r\n                           paragraph above for detail features.\r\n\r\n                       g:CodeCompl_RegionStart g:CodeCompl_RegionEnd\r\n                           region start and stop you can change them\r\n                           as you like.  but you must be careful,\r\n                           because we use them to detemin marks in\r\n                           your template files(not complete file), so\r\n                           if you change it, maybe you must\r\n                           substitute all marks in your template\r\n                           files. after you change them, maybe you\r\n                           should update your template file, you can\r\n                           use this command:\r\n                           :UpdateTemplate<CR>\r\n\r\n                       g:CodeCompl_Template_Forechar\r\n                           you can use template file with\r\n                           template-forechar, you can create a file\r\n                           named 'complete-word.filetype',\r\n                           and drop it in\r\n                           g:CodeCompl_Template_Folder(default, it's\r\n                           'templates' in your runtimepath, e.g.\r\n                           D:\\Vim\\vimfiles\\templates in windows, or\r\n                           \/root\/.vim\/templates in linux\/unix.\r\n                           after you create file, you can input\r\n                           forechar + complete-word to include the\r\n                           whole file. e.g. '#stdc' to include stdc.c\r\n                           if your current filetype is 'c'.\r\n\r\n                       g:CodeCompl_Template_Folder\r\n                           see paragraph above. the folder default is\r\n                           'templates'.\r\n\r\n                       g:CodeCompl_Complete_File\r\n                           file name of users defined snippets.  now\r\n                           it named 'my_snippets.template', use this\r\n                           postfix to prevent Vim load it\r\n                           automatically\r\n\r\n                       g:CodeCompl_ClearWhenUpdate\r\n                           see the Option section\r\n\r\n                       g:CodeCompl_SaveListInBuffer\r\n                            Save complete list and template file list only in buffer\r\n\r\n\r\n                   global helper functions:\r\n                       \r\n                       MakeRegion\r\n                           same as g:CodeCompl_RegionStart . 'your\r\n                           text' . g:CodeCompl_RegionEnd, but input a\r\n                           little easily, but there are other helper\r\n                           function and variables in your complete\r\n\r\n                           file(defaults is my_snippets.template in\r\n                           your plugin folder)\r\n\r\n                   default complete-words:\r\n                           see \"my_snippets.template\" file.\r\n","install_details":"Open .vba file with Vim, and type :so %.\r\n\r\nor unwind it, and put templates folder into your .vim folder(or vimfiles folder in windows), put *.vim and *.template file into your plugin folder.\r\n\r\nif you don't know Vimball, read this: vimscript #1502","5":"Open .vba file with Vim, and type :so %.\r\n\r\nor unwind it, and put templates folder into your .vim folder(or vimfiles folder in windows), put *.vim and *.template file into your plugin folder.\r\n\r\nif you don't know Vimball, read this: vimscript #1502","first_name":"Wxyarv","6":"Wxyarv","last_name":"Wang","7":"Wang","releases":[{"0":"2427","vim_version":"7.0","1":"7.0","script_version":"2.8.1","2":"2.8.1","version_comment":"bugfix, and change template marks diffevent with snippets marks. thanks to Scott Prager","3":"bugfix, and change template marks diffevent with snippets marks. thanks to Scott Prager","package":"code_complete.vba","4":"code_complete.vba","src_id":"9601","5":"9601","creation_date":"1228283747","6":"1228283747"},{"0":"2427","vim_version":"7.0","1":"7.0","script_version":"2.8.1","2":"2.8.1","version_comment":"add some helper function to build yourself snippets. and add some funny and useful snippets such as malloc, calloc and printf, you can try it youself, notice that they're only available when you set your filetype to c or cpp.\r\n\r\nadd some snippet for coding vim script.\r\n\r\nall in all, this is just a little upgrade for more comfortable experience.","3":"add some helper function to build yourself snippets. and add some funny and useful snippets such as malloc, calloc and printf, you can try it youself, notice that they're only available when you set your filetype to c or cpp.\r\n\r\nadd some snippet for coding vim script.\r\n\r\nall in all, this is just a little upgrade for more comfortable experience.","package":"code_complete.vba","4":"code_complete.vba","src_id":"9546","5":"9546","creation_date":"1227384939","6":"1227384939"},{"0":"2427","vim_version":"7.0","1":"7.0","script_version":"2.8.1","2":"2.8.1","version_comment":"bugfix, and remove g:CodeCompl_UpdateAlways\r\n\r\nmake g:CodeCompl_SaveListInBuffer work, it replaced g:CodeCompl_UpdateAlways","3":"bugfix, and remove g:CodeCompl_UpdateAlways\r\n\r\nmake g:CodeCompl_SaveListInBuffer work, it replaced g:CodeCompl_UpdateAlways","package":"code_complete.vba","4":"code_complete.vba","src_id":"9486","5":"9486","creation_date":"1226405486","6":"1226405486"},{"0":"2427","vim_version":"7.0","1":"7.0","script_version":"2.8","2":"2.8","version_comment":"still bugfix, now can input function declare like\"func(int(*)(int,int),int) correctly.\r\n\r\nchange some snippets in my_snippets.template, but you'd better backup yourself snippet file.\r\n\r\nadd some user-command, you can read a short details in script file.\r\n\r\nnext version will make \"save dict in global\" work, but at least this is a stable version.","3":"still bugfix, now can input function declare like\"func(int(*)(int,int),int) correctly.\r\n\r\nchange some snippets in my_snippets.template, but you'd better backup yourself snippet file.\r\n\r\nadd some user-command, you can read a short details in script file.\r\n\r\nnext version will make \"save dict in global\" work, but at least this is a stable version.","package":"code_complete.vba","4":"code_complete.vba","src_id":"9462","5":"9462","creation_date":"1226154894","6":"1226154894"},{"0":"2427","vim_version":"7.0","1":"7.0","script_version":"2.8","2":"2.8","version_comment":"Initial upload","3":"Initial upload","package":"code_complete.zip","4":"code_complete.zip","src_id":"9441","5":"9441","creation_date":"1225970809","6":"1225970809"}]},"2426":{"script_id":"2426","0":"2426","script_name":"nour.vim","1":"nour.vim","script_type":"color scheme","2":"color scheme","summary":"a set of highlights that extend dw_green for a better look","3":"a set of highlights that extend dw_green for a better look","description":"I basically copy and pasted dw_green into the top of this colorscheme and added some custom highlights. Screenshot while it's still up can be seen at http:\/\/foo.quran.com\/vim.png","4":"I basically copy and pasted dw_green into the top of this colorscheme and added some custom highlights. Screenshot while it's still up can be seen at http:\/\/foo.quran.com\/vim.png","install_details":"","5":"","first_name":"nour","6":"nour","last_name":"sharabash","7":"sharabash","releases":[{"0":"2426","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"nour.vim","4":"nour.vim","src_id":"9437","5":"9437","creation_date":"1225943112","6":"1225943112"}]},"2425":{"script_id":"2425","0":"2425","script_name":"arpeggio","1":"arpeggio","script_type":"utility","2":"utility","summary":"Key mappings for simultaneously pressed keys","3":"Key mappings for simultaneously pressed keys","description":"*arpeggio* is a Vim plugin to define another type of |key-mapping| called\n*arpeggio-key-mapping* -- it consists of 2 or more keys ({lhs}) and it will be\nexpanded to another key sequence ({rhs}) whenever all keys in {lhs} are\nsimultaneously pressed.  For example:\n\n\tArpeggio inoremap jk  <Esc>\n\t\" OR\n\tcall arpeggio#map('i', '', 0, 'jk', '<Esc>')\n\nWith the above definition, you can input <Esc> in Insert mode by pressing \"j\"\nand \"k\" simultaneously, while you can move the cursor by pressing \"j\" or \"k\"\nsolely.\n\nThe concept of this plugin is derived from Emacs' key-chord.el (*1), but there\nare the following differences:\n\n- Number of keys to be simultaneously pressed is unlimited.\n\n- Custom delay for each key is supported (see |g:arpeggio_timeoutlens|).\n  This is a generalization of space-chord.el (*2).\n\n(*1) http:\/\/www.emacswiki.org\/emacs\/key-chord.el\n(*2) http:\/\/www.emacswiki.org\/emacs\/space-chord.el\n\n\nRequirements:\n- Vim 7.2 or later\n\nLatest version:\nhttp:\/\/github.com\/kana\/vim-arpeggio\n\nDocument in HTML format:\nhttp:\/\/kana.github.com\/config\/vim\/arpeggio.html","4":"*arpeggio* is a Vim plugin to define another type of |key-mapping| called\n*arpeggio-key-mapping* -- it consists of 2 or more keys ({lhs}) and it will be\nexpanded to another key sequence ({rhs}) whenever all keys in {lhs} are\nsimultaneously pressed.  For example:\n\n\tArpeggio inoremap jk  <Esc>\n\t\" OR\n\tcall arpeggio#map('i', '', 0, 'jk', '<Esc>')\n\nWith the above definition, you can input <Esc> in Insert mode by pressing \"j\"\nand \"k\" simultaneously, while you can move the cursor by pressing \"j\" or \"k\"\nsolely.\n\nThe concept of this plugin is derived from Emacs' key-chord.el (*1), but there\nare the following differences:\n\n- Number of keys to be simultaneously pressed is unlimited.\n\n- Custom delay for each key is supported (see |g:arpeggio_timeoutlens|).\n  This is a generalization of space-chord.el (*2).\n\n(*1) http:\/\/www.emacswiki.org\/emacs\/key-chord.el\n(*2) http:\/\/www.emacswiki.org\/emacs\/space-chord.el\n\n\nRequirements:\n- Vim 7.2 or later\n\nLatest version:\nhttp:\/\/github.com\/kana\/vim-arpeggio\n\nDocument in HTML format:\nhttp:\/\/kana.github.com\/config\/vim\/arpeggio.html","install_details":"...","5":"...","first_name":"Kana","6":"Kana","last_name":"Natsuno","7":"Natsuno","releases":[{"0":"2425","vim_version":"7.0","1":"7.0","script_version":"0.0.6","2":"0.0.6","version_comment":"- Fix |arpeggio-commands| to behave the same as |:map| commands.  In other words, \" and keys after \" in {rhs} for |arpeggio-commands| are treated as a part of {rhs}.  Old versions don't behave so.\n- Fix minor bugs.\n- Revise the document a bit.\n- Revise additional syntax highlighting a bit.","3":"- Fix |arpeggio-commands| to behave the same as |:map| commands.  In other words, \" and keys after \" in {rhs} for |arpeggio-commands| are treated as a part of {rhs}.  Old versions don't behave so.\n- Fix minor bugs.\n- Revise the document a bit.\n- Revise additional syntax highlighting a bit.","package":"vim-arpeggio-0.0.6.zip","4":"vim-arpeggio-0.0.6.zip","src_id":"12873","5":"12873","creation_date":"1271734461","6":"1271734461"},{"0":"2425","vim_version":"7.0","1":"7.0","script_version":"0.0.5","2":"0.0.5","version_comment":"- Remove the assumption on 'timeout' and 'ttimeout'.  Old version\n  assumes that \"set timeout notimeout\", but now their values can be\n  arbitrary.\n- Fix the bug that 'ttimeoutlen' can be interpreted as an unexpected\n  value because of the adjustment of 'timeout' and 'timeoutlen' for\n  arpeggio key mappings.","3":"- Remove the assumption on 'timeout' and 'ttimeout'.  Old version\n  assumes that \"set timeout notimeout\", but now their values can be\n  arbitrary.\n- Fix the bug that 'ttimeoutlen' can be interpreted as an unexpected\n  value because of the adjustment of 'timeout' and 'timeoutlen' for\n  arpeggio key mappings.","package":"vim-arpeggio-0.0.5.zip","4":"vim-arpeggio-0.0.5.zip","src_id":"9622","5":"9622","creation_date":"1228555497","6":"1228555497"},{"0":"2425","vim_version":"7.0","1":"7.0","script_version":"0.0.4","2":"0.0.4","version_comment":"- Add syntax highlighting for |arpeggio-commands|.\n- Fix bugs of \"noremap\" version of |arpeggio-commands| such as\n  |:Arpeggionoremap| that {rhs} are remapped despite the meaning of\n  the commands.  (Thanks for id:ampmmn)","3":"- Add syntax highlighting for |arpeggio-commands|.\n- Fix bugs of \"noremap\" version of |arpeggio-commands| such as\n  |:Arpeggionoremap| that {rhs} are remapped despite the meaning of\n  the commands.  (Thanks for id:ampmmn)","package":"vim-arpeggio-0.0.4.zip","4":"vim-arpeggio-0.0.4.zip","src_id":"9488","5":"9488","creation_date":"1226439522","6":"1226439522"},{"0":"2425","vim_version":"7.0","1":"7.0","script_version":"0.0.3","2":"0.0.3","version_comment":"- Add |:Arpeggio|.\n- Support |:map-<unique>| for |arpeggio#map()| and other commands.\n- In |arpeggio#map()| and other commands, warn if a key in {lhs} is\n  already mapped to something other than a part of another\n  |arpeggio-key-mapping|.\n- Add custom 'timeoutlen' per key.  See |g:arpeggio_timeoutlens|.\n- Add a bit of completion for |arpeggio-commands|.","3":"- Add |:Arpeggio|.\n- Support |:map-<unique>| for |arpeggio#map()| and other commands.\n- In |arpeggio#map()| and other commands, warn if a key in {lhs} is\n  already mapped to something other than a part of another\n  |arpeggio-key-mapping|.\n- Add custom 'timeoutlen' per key.  See |g:arpeggio_timeoutlens|.\n- Add a bit of completion for |arpeggio-commands|.","package":"vim-arpeggio-0.0.3.zip","4":"vim-arpeggio-0.0.3.zip","src_id":"9466","5":"9466","creation_date":"1226210229","6":"1226210229"},{"0":"2425","vim_version":"7.0","1":"7.0","script_version":"0.0.2","2":"0.0.2","version_comment":"- Fix |:Arpeggionoremap| that allowed remapping but it should not do\n  so.  (Thanks for id:ampmmn)\n- Define |arpeggio-commands| and |arpeggio-variables| automatically\n  for interactive or other use.  (But you still have to call\n  |arpeggio#load()| to use them in vimrc.)","3":"- Fix |:Arpeggionoremap| that allowed remapping but it should not do\n  so.  (Thanks for id:ampmmn)\n- Define |arpeggio-commands| and |arpeggio-variables| automatically\n  for interactive or other use.  (But you still have to call\n  |arpeggio#load()| to use them in vimrc.)","package":"vim-arpeggio-0.0.2.zip","4":"vim-arpeggio-0.0.2.zip","src_id":"9457","5":"9457","creation_date":"1226069160","6":"1226069160"},{"0":"2425","vim_version":"7.0","1":"7.0","script_version":"0.0.1","2":"0.0.1","version_comment":"- Implement |arpeggio-commands|.\n- Add missing |arpeggio#list()|.\n- Revise minor stuffs.","3":"- Implement |arpeggio-commands|.\n- Add missing |arpeggio#list()|.\n- Revise minor stuffs.","package":"vim-arpeggio-0.0.1.zip","4":"vim-arpeggio-0.0.1.zip","src_id":"9435","5":"9435","creation_date":"1225932718","6":"1225932718"},{"0":"2425","vim_version":"7.0","1":"7.0","script_version":"0.0.0","2":"0.0.0","version_comment":"Initial upload","3":"Initial upload","package":"vim-arpeggio-0.0.0.zip","4":"vim-arpeggio-0.0.0.zip","src_id":"9434","5":"9434","creation_date":"1225902299","6":"1225902299"}]},"2424":{"script_id":"2424","0":"2424","script_name":"Transmit FTP","1":"Transmit FTP","script_type":"utility","2":"utility","summary":"Integrates Transmit FTP (Mac) with Vim","3":"Integrates Transmit FTP (Mac) with Vim","description":"This script allows you to upload the current file via Transmit directly from Vim. For it to work, you need to be working on a file that's tied to a Transmit connection, and this connection must have \"DockSend\" enabled.\r\n\r\nThe default key combination is Control + U to upload the active file.\r\n\r\nProject Integration\r\n------------------------\r\nTake a look at proj.vim, which includes a \"docksend\" option that uploads files immediately on save: http:\/\/www.vim.org\/scripts\/script.php?script_id=2719","4":"This script allows you to upload the current file via Transmit directly from Vim. For it to work, you need to be working on a file that's tied to a Transmit connection, and this connection must have \"DockSend\" enabled.\r\n\r\nThe default key combination is Control + U to upload the active file.\r\n\r\nProject Integration\r\n------------------------\r\nTake a look at proj.vim, which includes a \"docksend\" option that uploads files immediately on save: http:\/\/www.vim.org\/scripts\/script.php?script_id=2719","install_details":"Installation \r\n----------------------------\r\nUnzip TransmitFTP and then\r\n* Move the \"apple\" directory into your \"~\/.vim\" folder.\r\n* Move \"transmitftp.vim\" from \"plugin\" to \"~\/.vim\/plugin\"\r\n\r\nKeymapping:\r\n----------------------------\r\nMap any keys to \"TransmitFtpSendFile\" like so:\r\nnnoremap <C-A> :call TransmitFtpSendFile()<CR>\r\n\r\nBy default, <C-U> (Control + U) uploads the current file.","5":"Installation \r\n----------------------------\r\nUnzip TransmitFTP and then\r\n* Move the \"apple\" directory into your \"~\/.vim\" folder.\r\n* Move \"transmitftp.vim\" from \"plugin\" to \"~\/.vim\/plugin\"\r\n\r\nKeymapping:\r\n----------------------------\r\nMap any keys to \"TransmitFtpSendFile\" like so:\r\nnnoremap <C-A> :call TransmitFtpSendFile()<CR>\r\n\r\nBy default, <C-U> (Control + U) uploads the current file.","first_name":"Thomas","6":"Thomas","last_name":"Allen","7":"Allen","releases":[{"0":"2424","vim_version":"6.0","1":"6.0","script_version":"1.0a","2":"1.0a","version_comment":"Initial upload","3":"Initial upload","package":"TransmitFTP.zip","4":"TransmitFTP.zip","src_id":"9431","5":"9431","creation_date":"1225859255","6":"1225859255"}]},"2423":{"script_id":"2423","0":"2423","script_name":"Gist.vim","1":"Gist.vim","script_type":"utility","2":"utility","summary":"vimscript for gist","3":"vimscript for gist","description":"This is vimscript for gist (http:\/\/gist.github.com)\n\nUsage:\n\n  :Gist\n    post whole text to gist.\n\n  :'<,'>Gist\n    post selected text to gist.\n\n  :Gist -p\n    post whole text to gist with private.\n    if you got empty gist list, try :Gist --abandon \n\n  :Gist -a\n    post whole text to gist with anonymous.\n\n  :Gist -m\n    post multi buffer to gist.\n\n  :Gist -e\n    edit the gist. (shoud be work on gist buffer)\n    you can update the gist with :w command on gist buffer.\n\n  :Gist -e foo.js\n    edit the gist with name 'foo.js'. (shoud be work on gist buffer)\n\n  :Gist -d\n    delete the gist. (should be work on gist buffer)\n    password authentication is needed.\n\n  :Gist -f\n    fork the gist. (should be work on gist buffer)\n    password authentication is needed.\n\n  :Gist XXXXX\n    get gist XXXXX.\n\n  :Gist -c XXXXX.\n    get gist XXXXX and put to clipboard.\n\n  :Gist -l\n    list gists from mine.\n\n  :Gist -la\n    list gists from all.\n\nTips:\n  if set g:gist_clip_command, gist.vim will copy the gist code\n    with option '-c'.\n\n    # mac\n    let g:gist_clip_command = 'pbcopy'\n\n    # linux\n    let g:gist_clip_command = 'xclip -selection clipboard'\n\n    # others(cygwin?)\n    let g:gist_clip_command = 'putclip'\n\n  if you want to detect filetype from filename...\n\n    let g:gist_detect_filetype = 1\n\n  if you want to open browser after the post...\n\n    let g:gist_open_browser_after_post = 1\n\n  if you want to change the browser...\n\n    let g:gist_browser_command = 'w3m %URL%'\n\n      or\n\n    let g:gist_browser_command = 'opera %URL% &'\n\n    on windows, should work with original setting.\n\nRequire:\n  curl command (http:\/\/curl.haxx.se\/)\n  and if you want to use profile of git, it require git command.\n","4":"This is vimscript for gist (http:\/\/gist.github.com)\n\nUsage:\n\n  :Gist\n    post whole text to gist.\n\n  :'<,'>Gist\n    post selected text to gist.\n\n  :Gist -p\n    post whole text to gist with private.\n    if you got empty gist list, try :Gist --abandon \n\n  :Gist -a\n    post whole text to gist with anonymous.\n\n  :Gist -m\n    post multi buffer to gist.\n\n  :Gist -e\n    edit the gist. (shoud be work on gist buffer)\n    you can update the gist with :w command on gist buffer.\n\n  :Gist -e foo.js\n    edit the gist with name 'foo.js'. (shoud be work on gist buffer)\n\n  :Gist -d\n    delete the gist. (should be work on gist buffer)\n    password authentication is needed.\n\n  :Gist -f\n    fork the gist. (should be work on gist buffer)\n    password authentication is needed.\n\n  :Gist XXXXX\n    get gist XXXXX.\n\n  :Gist -c XXXXX.\n    get gist XXXXX and put to clipboard.\n\n  :Gist -l\n    list gists from mine.\n\n  :Gist -la\n    list gists from all.\n\nTips:\n  if set g:gist_clip_command, gist.vim will copy the gist code\n    with option '-c'.\n\n    # mac\n    let g:gist_clip_command = 'pbcopy'\n\n    # linux\n    let g:gist_clip_command = 'xclip -selection clipboard'\n\n    # others(cygwin?)\n    let g:gist_clip_command = 'putclip'\n\n  if you want to detect filetype from filename...\n\n    let g:gist_detect_filetype = 1\n\n  if you want to open browser after the post...\n\n    let g:gist_open_browser_after_post = 1\n\n  if you want to change the browser...\n\n    let g:gist_browser_command = 'w3m %URL%'\n\n      or\n\n    let g:gist_browser_command = 'opera %URL% &'\n\n    on windows, should work with original setting.\n\nRequire:\n  curl command (http:\/\/curl.haxx.se\/)\n  and if you want to use profile of git, it require git command.\n","install_details":"copy it to your plugin directory.\n\ngist.vim leave cookie-jar file into runtimepath.\n\nrtp:\n  plugin\/gist.vim\n  cookies\/github\n\nif you want to uninstall gist.vim, you have better to remove 'cookies\/github'.\n\nfor using gist.vim, you should install git. or set g:github_user and g:github_token into your vimrc.\nnote that g:github_token is NOT a your password.\n\nhow get your token.\n  1. login to github.\n  2. click \"Account Settings\"\n  3. click \"Account Admin\"\n  4. you'll see it at following of 'API Token'.\n\nSee also: https:\/\/github.com\/mattn\/gist-vim\/blob\/master\/README.mkd\n","5":"copy it to your plugin directory.\n\ngist.vim leave cookie-jar file into runtimepath.\n\nrtp:\n  plugin\/gist.vim\n  cookies\/github\n\nif you want to uninstall gist.vim, you have better to remove 'cookies\/github'.\n\nfor using gist.vim, you should install git. or set g:github_user and g:github_token into your vimrc.\nnote that g:github_token is NOT a your password.\n\nhow get your token.\n  1. login to github.\n  2. click \"Account Settings\"\n  3. click \"Account Admin\"\n  4. you'll see it at following of 'API Token'.\n\nSee also: https:\/\/github.com\/mattn\/gist-vim\/blob\/master\/README.mkd\n","first_name":"Yasuhiro","6":"Yasuhiro","last_name":"Matsumoto","7":"Matsumoto","releases":[{"0":"2423","vim_version":"7.0","1":"7.0","script_version":"7.2","2":"7.2","version_comment":"This is an upgrade for Gist.vim: fixed many bugs.\n","3":"This is an upgrade for Gist.vim: fixed many bugs.\n","package":"gist-vim.zip","4":"gist-vim.zip","src_id":"22543","5":"22543","creation_date":"1413685909","6":"1413685909"},{"0":"2423","vim_version":"7.0","1":"7.0","script_version":"7.1","2":"7.1","version_comment":"This is an upgrade for Gist.vim: updated installation notes.\n","3":"This is an upgrade for Gist.vim: updated installation notes.\n","package":"gist-vim.zip","4":"gist-vim.zip","src_id":"19176","5":"19176","creation_date":"1355358871","6":"1355358871"},{"0":"2423","vim_version":"7.0","1":"7.0","script_version":"7.0","2":"7.0","version_comment":"This is an upgrade for Gist.vim: fixed few bugs.\n","3":"This is an upgrade for Gist.vim: fixed few bugs.\n","package":"gist-vim.zip","4":"gist-vim.zip","src_id":"18697","5":"18697","creation_date":"1348703043","6":"1348703043"},{"0":"2423","vim_version":"7.0","1":"7.0","script_version":"6.9","2":"6.9","version_comment":"This is an upgrade for Gist.vim: fixed few bugs.\n","3":"This is an upgrade for Gist.vim: fixed few bugs.\n","package":"gist-vim.zip","4":"gist-vim.zip","src_id":"18558","5":"18558","creation_date":"1346985484","6":"1346985484"},{"0":"2423","vim_version":"7.0","1":"7.0","script_version":"6.8","2":"6.8","version_comment":"This is an upgrade for Gist.vim: changed authentication. removed password authentication. if you want to keep using password authentication, let gist_use_password_in_gitconfig to 1.\n","3":"This is an upgrade for Gist.vim: changed authentication. removed password authentication. if you want to keep using password authentication, let gist_use_password_in_gitconfig to 1.\n","package":"gist-vim.zip","4":"gist-vim.zip","src_id":"18235","5":"18235","creation_date":"1341806191","6":"1341806191"},{"0":"2423","vim_version":"7.0","1":"7.0","script_version":"6.7","2":"6.7","version_comment":"This is an upgrade for Gist.vim: fix behavior of g:gist_browser_command = ':OpenBrowser %URL%'.\n","3":"This is an upgrade for Gist.vim: fix behavior of g:gist_browser_command = ':OpenBrowser %URL%'.\n","package":"gist-vim.zip","4":"gist-vim.zip","src_id":"18053","5":"18053","creation_date":"1338203349","6":"1338203349"},{"0":"2423","vim_version":"7.0","1":"7.0","script_version":"6.6","2":"6.6","version_comment":"This is an upgrade for Gist.vim: fixed detecting filetype.\n","3":"This is an upgrade for Gist.vim: fixed detecting filetype.\n","package":"gist-vim.zip","4":"gist-vim.zip","src_id":"17853","5":"17853","creation_date":"1335929708","6":"1335929708"},{"0":"2423","vim_version":"7.0","1":"7.0","script_version":"6.5","2":"6.5","version_comment":"This is an upgrade for Gist.vim: use webapi namespace. NOTE: please upgrade webapi-vim also.\n","3":"This is an upgrade for Gist.vim: use webapi namespace. NOTE: please upgrade webapi-vim also.\n","package":"gist-vim.zip","4":"gist-vim.zip","src_id":"17779","5":"17779","creation_date":"1334504128","6":"1334504128"},{"0":"2423","vim_version":"7.0","1":"7.0","script_version":"6.4","2":"6.4","version_comment":"This is an upgrade for Gist.vim: fixed updating with description.\n","3":"This is an upgrade for Gist.vim: fixed updating with description.\n","package":"gist-vim.zip","4":"gist-vim.zip","src_id":"17734","5":"17734","creation_date":"1333817596","6":"1333817596"},{"0":"2423","vim_version":"7.0","1":"7.0","script_version":"6.3","2":"6.3","version_comment":"This is an upgrade for Gist.vim: fixed typos.\n","3":"This is an upgrade for Gist.vim: fixed typos.\n","package":"gist-vim.zip","4":"gist-vim.zip","src_id":"17706","5":"17706","creation_date":"1333412642","6":"1333412642"},{"0":"2423","vim_version":"7.0","1":"7.0","script_version":"6.2","2":"6.2","version_comment":"This is an upgrade for Gist.vim: fixed some bugs.\n","3":"This is an upgrade for Gist.vim: fixed some bugs.\n","package":"gist-vim.zip","4":"gist-vim.zip","src_id":"17701","5":"17701","creation_date":"1333351735","6":"1333351735"},{"0":"2423","vim_version":"7.0","1":"7.0","script_version":"6.1","2":"6.1","version_comment":"This is an upgrade for Gist.vim: fixed opening browser.\n","3":"This is an upgrade for Gist.vim: fixed opening browser.\n","package":"gist-vim.zip","4":"gist-vim.zip","src_id":"17696","5":"17696","creation_date":"1333207989","6":"1333207989"},{"0":"2423","vim_version":"7.0","1":"7.0","script_version":"6.0","2":"6.0","version_comment":"This is an upgrade for Gist.vim: changed to use github APIs. Note to remove cookies directory if you used.\n","3":"This is an upgrade for Gist.vim: changed to use github APIs. Note to remove cookies directory if you used.\n","package":"gist-vim.zip","4":"gist-vim.zip","src_id":"17695","5":"17695","creation_date":"1333199173","6":"1333199173"},{"0":"2423","vim_version":"7.0","1":"7.0","script_version":"5.9","2":"5.9","version_comment":"This is an upgrade for Gist.vim: add support anonymous post. fixed many bugs.\n","3":"This is an upgrade for Gist.vim: add support anonymous post. fixed many bugs.\n","package":"gist-vim.zip","4":"gist-vim.zip","src_id":"17345","5":"17345","creation_date":"1327985661","6":"1327985661"},{"0":"2423","vim_version":"7.0","1":"7.0","script_version":"5.8","2":"5.8","version_comment":"This is an upgrade for Gist.vim: add support for description. you can post description using -s option.\n","3":"This is an upgrade for Gist.vim: add support for description. you can post description using -s option.\n","package":"gist-vim.zip","4":"gist-vim.zip","src_id":"17027","5":"17027","creation_date":"1323068142","6":"1323068142"},{"0":"2423","vim_version":"7.0","1":"7.0","script_version":"5.7","2":"5.7","version_comment":"This is an upgrade for Gist.vim: post with filetype more cleverly.\n","3":"This is an upgrade for Gist.vim: post with filetype more cleverly.\n","package":"gist-vim.zip","4":"gist-vim.zip","src_id":"16938","5":"16938","creation_date":"1321960963","6":"1321960963"},{"0":"2423","vim_version":"7.0","1":"7.0","script_version":"5.6","2":"5.6","version_comment":"This is an upgrade for Gist.vim: fix '--abandon'.\n","3":"This is an upgrade for Gist.vim: fix '--abandon'.\n","package":"gist-vim.zip","4":"gist-vim.zip","src_id":"16912","5":"16912","creation_date":"1321836898","6":"1321836898"},{"0":"2423","vim_version":"7.0","1":"7.0","script_version":"5.5","2":"5.5","version_comment":"This is an upgrade for Gist.vim: fix: forgot to upload autoload\/gist.vim.\n","3":"This is an upgrade for Gist.vim: fix: forgot to upload autoload\/gist.vim.\n","package":"gist-vim.zip","4":"gist-vim.zip","src_id":"16692","5":"16692","creation_date":"1318899461","6":"1318899461"},{"0":"2423","vim_version":"7.0","1":"7.0","script_version":"5.4","2":"5.4","version_comment":"This is an upgrade for Gist.vim: fix: does not work correctly with blockwize selection.\n","3":"This is an upgrade for Gist.vim: fix: does not work correctly with blockwize selection.\n","package":"gist.vim","4":"gist.vim","src_id":"16668","5":"16668","creation_date":"1318553735","6":"1318553735"},{"0":"2423","vim_version":"7.0","1":"7.0","script_version":"5.3","2":"5.3","version_comment":"This is an upgrade for Gist.vim: upd: support autoload.\n","3":"This is an upgrade for Gist.vim: upd: support autoload.\n","package":"gist.vim","4":"gist.vim","src_id":"16663","5":"16663","creation_date":"1318512425","6":"1318512425"},{"0":"2423","vim_version":"7.0","1":"7.0","script_version":"5.2","2":"5.2","version_comment":"This is an upgrade for Gist.vim: add: support block-wise selection.\n","3":"This is an upgrade for Gist.vim: add: support block-wise selection.\n","package":"gist.vim","4":"gist.vim","src_id":"16660","5":"16660","creation_date":"1318502032","6":"1318502032"},{"0":"2423","vim_version":"7.0","1":"7.0","script_version":"5.1","2":"5.1","version_comment":"This is an upgrade for Gist.vim: fixed: can't update privates.\n","3":"This is an upgrade for Gist.vim: fixed: can't update privates.\n","package":"gist.vim","4":"gist.vim","src_id":"16533","5":"16533","creation_date":"1316134239","6":"1316134239"},{"0":"2423","vim_version":"7.0","1":"7.0","script_version":"5.0","2":"5.0","version_comment":"This is an upgrade for Gist.vim: follow update of gist.github.com\n","3":"This is an upgrade for Gist.vim: follow update of gist.github.com\n","package":"gist.vim","4":"gist.vim","src_id":"15897","5":"15897","creation_date":"1308130349","6":"1308130349"},{"0":"2423","vim_version":"7.0","1":"7.0","script_version":"4.9","2":"4.9","version_comment":"fix: don't add new line after \"Done: xxx\".\nfix: show WHY FAILED' when failed to post.\nadd: support for :OpenBrowser.\nadd: new option 'gist_curl_options'.\n","3":"fix: don't add new line after \"Done: xxx\".\nfix: show WHY FAILED' when failed to post.\nadd: support for :OpenBrowser.\nadd: new option 'gist_curl_options'.\n","package":"gist.vim","4":"gist.vim","src_id":"15452","5":"15452","creation_date":"1302853815","6":"1302853815"}]},"2422":{"script_id":"2422","0":"2422","script_name":"Wordnet.vim","1":"Wordnet.vim","script_type":"utility","2":"utility","summary":"wordnet.vim","3":"wordnet.vim","description":"\" wordnet.vim\r\n\" By Tim Harper (http:\/\/tim.theenchanter.com\/)\r\n\"\r\n\" OVERVIEW:\r\n\" Easily look up the definition of the word under your cursor via wordnet\r\n\" (http:\/\/wordnet.princeton.edu\/). Definition is shown in a new region, with\r\n\" syntax highlighting for easier reading.\r\n\"\r\n\" INSTRUCTIONS:\r\n\" 1) Configure your wordnet path, if it's in a non-standard path (in your\r\n\" vimrc)\r\n\" let g:wordnet_path = \"\/usr\/local\/WordNet-3.0\/bin\/\"\r\n\"\r\n\" 2) highlight or put your cursor over a word, and:\r\n\" <Leader>wnd - Define the word\r\n\" <Leader>wnb - Launch the wordnet browser for the word.\r\n\r\n","4":"\" wordnet.vim\r\n\" By Tim Harper (http:\/\/tim.theenchanter.com\/)\r\n\"\r\n\" OVERVIEW:\r\n\" Easily look up the definition of the word under your cursor via wordnet\r\n\" (http:\/\/wordnet.princeton.edu\/). Definition is shown in a new region, with\r\n\" syntax highlighting for easier reading.\r\n\"\r\n\" INSTRUCTIONS:\r\n\" 1) Configure your wordnet path, if it's in a non-standard path (in your\r\n\" vimrc)\r\n\" let g:wordnet_path = \"\/usr\/local\/WordNet-3.0\/bin\/\"\r\n\"\r\n\" 2) highlight or put your cursor over a word, and:\r\n\" <Leader>wnd - Define the word\r\n\" <Leader>wnb - Launch the wordnet browser for the word.\r\n\r\n","install_details":"Unpack to ~\/.vim\/","5":"Unpack to ~\/.vim\/","first_name":"Tim","6":"Tim","last_name":"Harper","7":"Harper","releases":[{"0":"2422","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"wordnet-0.1.zip","4":"wordnet-0.1.zip","src_id":"9428","5":"9428","creation_date":"1225721002","6":"1225721002"}]},"2421":{"script_id":"2421","0":"2421","script_name":"PySmell","1":"PySmell","script_type":"utility","2":"utility","summary":"A Python omnicompletion utility","3":"A Python omnicompletion utility","description":"PySmell is an alternative omnicompletion library for Python.\r\n\r\nIt has two parts: The Python library that does the analyzing, and the Vim script that calls into the library. \r\n\r\nIt works by analyzing your codebase once, saving information in a TAGS file, and using that to provide context-aware completions. \r\n\r\nThere is more documentation in the README and in pysmell.vim\r\n\r\nThe project is hosted at http:\/\/code.google.com\/p\/pysmell\r\nThe code repo is at http:\/\/github.com\/orestis\/pysmell\r\nFollow news at http:\/\/orestis.gr","4":"PySmell is an alternative omnicompletion library for Python.\r\n\r\nIt has two parts: The Python library that does the analyzing, and the Vim script that calls into the library. \r\n\r\nIt works by analyzing your codebase once, saving information in a TAGS file, and using that to provide context-aware completions. \r\n\r\nThere is more documentation in the README and in pysmell.vim\r\n\r\nThe project is hosted at http:\/\/code.google.com\/p\/pysmell\r\nThe code repo is at http:\/\/github.com\/orestis\/pysmell\r\nFollow news at http:\/\/orestis.gr","install_details":"Uninstall the .tar.gz, cd into it and do:\r\n\r\npython setup.py install\r\n\r\nTo use PySmell omnicompletion from inside Vim, you have to have:\r\n\r\n1. Python support in vim (`:echo has('python')`)\r\n2. The pysmell package in the PYTHONPATH that Vim uses: `python import pysmell` should work.\r\n3. Drop pysmell.vim in ~\/.vim\/plugins\r\n4. `:setlocal omnifunc=pysmell#Complete` Note: If you want to always use pysmell for python, do: `autocmd FileType python setlocal omnifunc=pysmell#Complete`\r\n5. [OPTIONAL] Select a matcher of your liking - look at pysmell.vim for\r\noptions. Eg: `:let g:pysmell_matcher='camel-case'`\r\n\r\n","5":"Uninstall the .tar.gz, cd into it and do:\r\n\r\npython setup.py install\r\n\r\nTo use PySmell omnicompletion from inside Vim, you have to have:\r\n\r\n1. Python support in vim (`:echo has('python')`)\r\n2. The pysmell package in the PYTHONPATH that Vim uses: `python import pysmell` should work.\r\n3. Drop pysmell.vim in ~\/.vim\/plugins\r\n4. `:setlocal omnifunc=pysmell#Complete` Note: If you want to always use pysmell for python, do: `autocmd FileType python setlocal omnifunc=pysmell#Complete`\r\n5. [OPTIONAL] Select a matcher of your liking - look at pysmell.vim for\r\noptions. Eg: `:let g:pysmell_matcher='camel-case'`\r\n\r\n","first_name":"Orestis","6":"Orestis","last_name":"Markou","7":"Markou","releases":[{"0":"2421","vim_version":"7.0","1":"7.0","script_version":"0.7","2":"0.7","version_comment":"Initial upload","3":"Initial upload","package":"pysmell-0.7.tar.gz","4":"pysmell-0.7.tar.gz","src_id":"9423","5":"9423","creation_date":"1225665378","6":"1225665378"}]},"2420":{"script_id":"2420","0":"2420","script_name":"gadgetxml.vim","1":"gadgetxml.vim","script_type":"syntax","2":"syntax","summary":"opensocial gadget xml syntax","3":"opensocial gadget xml syntax","description":"Hightlights the contents of <Content type=\"html\"> as HTML.","4":"Hightlights the contents of <Content type=\"html\"> as HTML.","install_details":"","5":"","first_name":"M\u00c3\u00a1rton","6":"M\u00c3\u00a1rton","last_name":"Salomv\u00c3\u00a1ry","7":"Salomv\u00c3\u00a1ry","releases":[{"0":"2420","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"gadgetxml.vim","4":"gadgetxml.vim","src_id":"9422","5":"9422","creation_date":"1225660127","6":"1225660127"}]},"2419":{"script_id":"2419","0":"2419","script_name":"quickrun","1":"quickrun","script_type":"utility","2":"utility","summary":"run a command and show its result quickly","3":"run a command and show its result quickly","description":"http:\/\/github.com\/ujihisa\/quickrun\/\r\nrun a command and show its result quickly\r\n","4":"http:\/\/github.com\/ujihisa\/quickrun\/\r\nrun a command and show its result quickly\r\n","install_details":"mv quickrun.vim ~\/.vim\/plugin\/","5":"mv quickrun.vim ~\/.vim\/plugin\/","first_name":"ujihisa","6":"ujihisa","last_name":".","7":".","releases":[{"0":"2419","vim_version":"6.0","1":"6.0","script_version":"1.2","2":"1.2","version_comment":"see http:\/\/github.com\/ujihisa\/quickrun\/tree\/master","3":"see http:\/\/github.com\/ujihisa\/quickrun\/tree\/master","package":"quickrun.vim","4":"quickrun.vim","src_id":"11077","5":"11077","creation_date":"1248802331","6":"1248802331"},{"0":"2419","vim_version":"6.0","1":"6.0","script_version":"1.1","2":"1.1","version_comment":"see http:\/\/github.com\/ujihisa\/quickrun\/tree\/master","3":"see http:\/\/github.com\/ujihisa\/quickrun\/tree\/master","package":"quickrun.vim","4":"quickrun.vim","src_id":"10552","5":"10552","creation_date":"1241635394","6":"1241635394"},{"0":"2419","vim_version":"7.2","1":"7.2","script_version":"1.0.0","2":"1.0.0","version_comment":"Initial upload","3":"Initial upload","package":"quickrun.vim","4":"quickrun.vim","src_id":"9417","5":"9417","creation_date":"1225385234","6":"1225385234"}]},"2418":{"script_id":"2418","0":"2418","script_name":"Format Helper","1":"Format Helper","script_type":"utility","2":"utility","summary":"format functions: count doc-infor, add & del list and block, etc.","3":"format functions: count doc-infor, add & del list and block, etc.","description":"    This script provides some format functions, such as, document information statistics, list addition and deletion, text block addition and deletion, head line and foot line addition, matched parenthesis auto-completion and omni-completion enhancement. Both this functions can be used for plain text, or process comment for programming file.\r\n\r\n\r\nMAINPAGE\r\n=========\r\n\r\n    http:\/\/franksun.blogbus.com\/logs\/30678478.html\r\n\r\n    Most of these functionss are illustrated by some screenshots in above page.\r\n\r\n\r\nFUNCTIONS OUTLINE\r\n==================\r\n\r\n1. Doc-info statistics\r\n----------------------------\r\n\r\n    A command is provided to calculate doc-info, such as, number of characters (both with space and no-space), words, and lines (both empty and nonempty) within your selected area.\r\n\r\n        ++++++++++++++++++++\r\n        +      :[range]Statistics      +\r\n        ++++++++++++++++++++\r\n\r\n* Detail:\r\n\r\n    [range] - same usage as in command line, such as, '%' (or \"0,$\") means whole file, '.' means current line, etc. If range field is empty, then it counts current line's information by default.\r\n\r\n* NOTE: \r\n\r\n    (1) It can handle wide (2 or 3 bytes) character languages (for instance, Chinese, Japanese, Korean, etc.). If &encoding=='utf-8', width of wide character is set to 3, otherwise 2.\r\n    (2) As my tests show, precision of this function is better than Win-Word's \"word count\" tool, which only identifies space as word-delimiter, meanwhile, this script takes all non-word characters ('\\W') into account. Unfortunately, it is not as efficient as win-word when handles large files (to handle a file with 30,000 lines, win-word costs about 3.5 seconds, and this script costs about 9 seconds).\r\n\r\n2. Number list addition and deletion\r\n-------------------------------------------------\r\n\r\n    This is a cute function:\r\n\r\n    (1) You can set the format of item head to any style as you wish, such as, (1), [1], {1}, 1., -1-, etc. And them can also be deleted by this script.\r\n    (2) It will acquire the head of the last item in previous number list, and make the first index of current list continue with the previous list's last index.\r\n\r\n    Two command are provided:\r\n\r\n        ++++++++++++++++++++++++++++++++\r\n        +      :[range]AddNumberList {format}      +\r\n        +      :[range]DelNumberList {format}       +\r\n        ++++++++++++++++++++++++++++++++\r\n\r\n* Detail:\r\n\r\n    [range] - same usage as Statistics.\r\n    {format} - includes three segments: a presegment, a number or a question mark ('?'), and a postsegment. You can set presegment and postsegment to any style you like. If a number is located in between presegment and postsegment, then the first index of number list is set to the number. Otherwise, if a qusetion mark is located there, script will automatically acquire the last index of previous number list and continue with it.\r\n\r\n* NOTE:\r\n\r\n    (1) If a question mark is neighboring with numbers in a style, the index will be continued with previous list.\r\n\r\n* Control parameters: some global variables to control format function\r\n\r\n    g:format_list_ceil (default 0): empty lines from above content to the first line of list.\r\n    g:format_list_floor (default 0): empty lines form the last line of list to below content.\r\n    g:format_list_indent (default 0): indent spaces from beginning of current line to the item head.\r\n    g:format_list_max_scope (default 100): max lines to search the last index of previous number list from assigned line number.\r\n\r\n* Example:\r\n\r\n    Here are selected lines:\r\n\r\n#line\r\n          ##############\r\n    1    #   this is line1    #\r\n    2    #   this is line2    #\r\n          #   ......                  #\r\n   10   #   this is line10  #\r\n          ##############\r\n\r\nIf you input a command:\r\n\r\n    :1,5 AddNumberList (1)\r\n\r\nthey will be changed to:\r\n\r\n#line\r\n         ################\r\n    1   #   (1) this is line1   #\r\n         #    ......                     #\r\n    5   #   (5) this is line2   #\r\n    6   #   this is line6         #\r\n         #    ......                     #\r\n   10  #   this is line10      #\r\n         ################\r\n\r\nIf you want to continue this list across 3 lines, add line 9 and line 10 to the number list, you have two approaches--first one, you can assign the index of new head manually, for instance, you've already remembered the last index of previous number list was '5', then you should input:\r\n\r\n    :9,10 AddNumberList (6)\r\n\r\nthe other one is to call script to automatically acquire a continuous index, here, you should use question mark '?':\r\n\r\n    :9,10 AddNumberList (?)\r\n\r\nboth of these two approaches will change file to below:\r\n\r\n#line\r\n         ################\r\n    1   #   (1) this is line1    #\r\n         #    ......                      #\r\n    5   #   (5) this is line2    #\r\n    6   #   this is line6          #\r\n    7   #   this is line7          #\r\n    8   #   this is line8          #\r\n    9   #   (6) this is line9    #\r\n   10  #   (7) this is line10  #\r\n         #################\r\n\r\nIf you want to cancel this number list, just input a command:\r\n\r\n    :1,10 DelNumberList (?)\r\n\r\n3. Auto-fit alignation\r\n---------------------------\r\n\r\n    Vim provide three command to align line, :left, :center and :right, but these command cannot align line to correct position. It is caused by some factors, such as, different size of users' screen, different size of gvim's window, and the most important factor--the 'textwidth' is equal to 80 by default. \r\n    Here provide three new commands that auto-fit different size of screen or window, and handle alignations correctly.\r\n\r\n        ++++++++++++++++++\r\n        +      :[range]Left           +\r\n        +      :[range]Center      +\r\n        +      :[range]Right         +\r\n        ++++++++++++++++++\r\n\r\n4. Enumerate list addition and deletion\r\n-----------------------------------------------------\r\n\r\n    Same usage as :AddNumberList and :DelNumberList, but I think these commands will be more useful than number list, as you can set comments for any programming language, means, set the head style to comment leader.\r\n\r\n        ++++++++++++++++++++++++++++++++\r\n        +      :[range]AddEnumerateList {style}      +\r\n        +      :[range]DelEnumerateList {style}       +\r\n        ++++++++++++++++++++++++++++++++\r\n\r\n* NOTE: \r\n\r\n    (1) This fucntion can be used to add or delete comments for any programming languages\r\n\r\n* Control parameters: some global variables to control format function\r\n\r\n    g:format_list_ceil (default 0): empty lines from above content to the first line of list.\r\n    g:format_list_floor (default 0): empty lines form the last line of list to below content.\r\n    g:format_list_indent (default 0): indent spaces from beginning of current line to the item head.\r\n \r\n* Example:\r\n\r\n    If you want to comment lines from line 19 to line 82 in a C++ file, just input:\r\n    \r\n    :19,82 AddEnumerateList \/\/\r\n\r\ninput below command to cancel this enumerate list:\r\n\r\n    :19,82 DelEnumerateList \/\/\r\n\r\n5. Text block addition and deletion\r\n-----------------------------------------------\r\n\r\n    Two commands are provided to add text block with selected lines and delete this block.\r\n\r\n        +++++++++++++++++++++++++++++++\r\n        +      :[range]AddTextBlock {symbol}      +\r\n        +      :[range]DelTextBlock {symbol}        +\r\n        +++++++++++++++++++++++++++++++\r\n\r\n* Detail:\r\n\r\n    [range] - same usage as Statistics.\r\n    {symbol} - script will use this character to construct broader of boundary.\r\n\r\n* NOTE: \r\n\r\n    (1) This fucntion can be commbined with enumerate list to add or delete comment for any programming language.\r\n\r\n* Control parameters: some global variables to control format function\r\n\r\n    g:format_block_ceil (default 0): empty lines from above content to the boundary of block.\r\n    g:format_block_floor (default 0): empty lines form the boundary of block to below content.\r\n    g:format_block_indent (default 0): indent spaces from beginning of current line to left boundary of block.\r\n    g:format_block_internal_ceil (default 0): empty lines form ceiling boundary to the first line of block contents.\r\n    g:format_block_internal_floor (default 0):  empty line form the last line of block contents to floor boundary.\r\n\r\n* Example:\r\n\r\n    Here are lines to add in text block:\r\n\r\n####################\r\n#      (above contents)      #\r\n#                                         #\r\n#      block contents          #\r\n#                                         #\r\n#      (below contents)       #\r\n####################\r\n\r\nIf you input a command (all parameters by default values):\r\n\r\n    :'<,'> AddTextBlock *\r\n\r\nthen we have:\r\n\r\n#########################\r\n#      (above contents)                 #\r\n#                                                    #\r\n#      **************************       #\r\n#      *      block contents      *      #\r\n#      **************************       #\r\n#                                                    #\r\n#      (below contents)                  #\r\n#########################\r\n\r\nif you input:\r\n\r\n    :'<,'> DelTextBlock *\r\n\r\nwe have:\r\n\r\n####################\r\n#      (above contents)      #\r\n#                                         #\r\n#                                         #\r\n#      block contents          #\r\n#                                         #\r\n#                                         #\r\n#      (below contents)       #\r\n####################\r\n\r\n6. Auto-complete matched pair parenthesis\r\n------------------------------------------------------------\r\n\r\n    Here provides a function to auto-complete match parenthesis in your insert mode. It completes matched pairs of (), [], {}, and <>, and immediately move cursor leftwards to the middle of pairs. If you input anti-parenthesis, it will erase the extra one.\r\n    \r\n7. Headline and footline addition\r\n--------------------------------------------\r\n\r\n    Do you see previous line? Yeah, it was made by command \":footlilne-\". It will draw head line or foot line whose length is equal to current line.\r\n\r\n\r\n        ++++++++++++++++++++++++++++++++\r\n        +      :[line number] HeadLine {symbol}      +\r\n        +      :[line number] FootLine {symbol}        +\r\n        ++++++++++++++++++++++++++++++++\r\n\r\n* Detail:\r\n\r\n    {symbol} - head line or foot line are made with this character.\r\n\r\n8. Enhance completion function\r\n-------------------------------------------\r\n    \r\n    Here provides a function to binding completion with <Tab> key. When you hit <Tab> in the insert mode, it will complete your content by your omni-function if you set your own omni-function, otherwise, the nearest known words or keywords of the dictionary you set (control by option 'dictionary') will be completed.\r\n\r\n\r\nUPGRADE\r\n=========\r\n\r\nBy default, GetLatestVimScripts plugin is included in Vim installation package, whose version is higher than v7. So you can use it to auto-download the newest package. Add below line into file \"GetLatestVimScripts.dat\":\r\n\r\n                           2418 1 format-helper\r\n\r\nand use this command \":GetLatestVimScripts\" to upgrade it.\r\n\r\n\r\n********************\r\n*      NOTICE      *\r\n********************\r\n\r\n      When you want to hack this script, please make sure that the option 'Tlist_Show_Menu' is closed (set its value as 0) if \"Taglist\" plugin was installed in your Vim. Otherwise, it will popup an annoyed message \"E792: Empty menu name\".","4":"    This script provides some format functions, such as, document information statistics, list addition and deletion, text block addition and deletion, head line and foot line addition, matched parenthesis auto-completion and omni-completion enhancement. Both this functions can be used for plain text, or process comment for programming file.\r\n\r\n\r\nMAINPAGE\r\n=========\r\n\r\n    http:\/\/franksun.blogbus.com\/logs\/30678478.html\r\n\r\n    Most of these functionss are illustrated by some screenshots in above page.\r\n\r\n\r\nFUNCTIONS OUTLINE\r\n==================\r\n\r\n1. Doc-info statistics\r\n----------------------------\r\n\r\n    A command is provided to calculate doc-info, such as, number of characters (both with space and no-space), words, and lines (both empty and nonempty) within your selected area.\r\n\r\n        ++++++++++++++++++++\r\n        +      :[range]Statistics      +\r\n        ++++++++++++++++++++\r\n\r\n* Detail:\r\n\r\n    [range] - same usage as in command line, such as, '%' (or \"0,$\") means whole file, '.' means current line, etc. If range field is empty, then it counts current line's information by default.\r\n\r\n* NOTE: \r\n\r\n    (1) It can handle wide (2 or 3 bytes) character languages (for instance, Chinese, Japanese, Korean, etc.). If &encoding=='utf-8', width of wide character is set to 3, otherwise 2.\r\n    (2) As my tests show, precision of this function is better than Win-Word's \"word count\" tool, which only identifies space as word-delimiter, meanwhile, this script takes all non-word characters ('\\W') into account. Unfortunately, it is not as efficient as win-word when handles large files (to handle a file with 30,000 lines, win-word costs about 3.5 seconds, and this script costs about 9 seconds).\r\n\r\n2. Number list addition and deletion\r\n-------------------------------------------------\r\n\r\n    This is a cute function:\r\n\r\n    (1) You can set the format of item head to any style as you wish, such as, (1), [1], {1}, 1., -1-, etc. And them can also be deleted by this script.\r\n    (2) It will acquire the head of the last item in previous number list, and make the first index of current list continue with the previous list's last index.\r\n\r\n    Two command are provided:\r\n\r\n        ++++++++++++++++++++++++++++++++\r\n        +      :[range]AddNumberList {format}      +\r\n        +      :[range]DelNumberList {format}       +\r\n        ++++++++++++++++++++++++++++++++\r\n\r\n* Detail:\r\n\r\n    [range] - same usage as Statistics.\r\n    {format} - includes three segments: a presegment, a number or a question mark ('?'), and a postsegment. You can set presegment and postsegment to any style you like. If a number is located in between presegment and postsegment, then the first index of number list is set to the number. Otherwise, if a qusetion mark is located there, script will automatically acquire the last index of previous number list and continue with it.\r\n\r\n* NOTE:\r\n\r\n    (1) If a question mark is neighboring with numbers in a style, the index will be continued with previous list.\r\n\r\n* Control parameters: some global variables to control format function\r\n\r\n    g:format_list_ceil (default 0): empty lines from above content to the first line of list.\r\n    g:format_list_floor (default 0): empty lines form the last line of list to below content.\r\n    g:format_list_indent (default 0): indent spaces from beginning of current line to the item head.\r\n    g:format_list_max_scope (default 100): max lines to search the last index of previous number list from assigned line number.\r\n\r\n* Example:\r\n\r\n    Here are selected lines:\r\n\r\n#line\r\n          ##############\r\n    1    #   this is line1    #\r\n    2    #   this is line2    #\r\n          #   ......                  #\r\n   10   #   this is line10  #\r\n          ##############\r\n\r\nIf you input a command:\r\n\r\n    :1,5 AddNumberList (1)\r\n\r\nthey will be changed to:\r\n\r\n#line\r\n         ################\r\n    1   #   (1) this is line1   #\r\n         #    ......                     #\r\n    5   #   (5) this is line2   #\r\n    6   #   this is line6         #\r\n         #    ......                     #\r\n   10  #   this is line10      #\r\n         ################\r\n\r\nIf you want to continue this list across 3 lines, add line 9 and line 10 to the number list, you have two approaches--first one, you can assign the index of new head manually, for instance, you've already remembered the last index of previous number list was '5', then you should input:\r\n\r\n    :9,10 AddNumberList (6)\r\n\r\nthe other one is to call script to automatically acquire a continuous index, here, you should use question mark '?':\r\n\r\n    :9,10 AddNumberList (?)\r\n\r\nboth of these two approaches will change file to below:\r\n\r\n#line\r\n         ################\r\n    1   #   (1) this is line1    #\r\n         #    ......                      #\r\n    5   #   (5) this is line2    #\r\n    6   #   this is line6          #\r\n    7   #   this is line7          #\r\n    8   #   this is line8          #\r\n    9   #   (6) this is line9    #\r\n   10  #   (7) this is line10  #\r\n         #################\r\n\r\nIf you want to cancel this number list, just input a command:\r\n\r\n    :1,10 DelNumberList (?)\r\n\r\n3. Auto-fit alignation\r\n---------------------------\r\n\r\n    Vim provide three command to align line, :left, :center and :right, but these command cannot align line to correct position. It is caused by some factors, such as, different size of users' screen, different size of gvim's window, and the most important factor--the 'textwidth' is equal to 80 by default. \r\n    Here provide three new commands that auto-fit different size of screen or window, and handle alignations correctly.\r\n\r\n        ++++++++++++++++++\r\n        +      :[range]Left           +\r\n        +      :[range]Center      +\r\n        +      :[range]Right         +\r\n        ++++++++++++++++++\r\n\r\n4. Enumerate list addition and deletion\r\n-----------------------------------------------------\r\n\r\n    Same usage as :AddNumberList and :DelNumberList, but I think these commands will be more useful than number list, as you can set comments for any programming language, means, set the head style to comment leader.\r\n\r\n        ++++++++++++++++++++++++++++++++\r\n        +      :[range]AddEnumerateList {style}      +\r\n        +      :[range]DelEnumerateList {style}       +\r\n        ++++++++++++++++++++++++++++++++\r\n\r\n* NOTE: \r\n\r\n    (1) This fucntion can be used to add or delete comments for any programming languages\r\n\r\n* Control parameters: some global variables to control format function\r\n\r\n    g:format_list_ceil (default 0): empty lines from above content to the first line of list.\r\n    g:format_list_floor (default 0): empty lines form the last line of list to below content.\r\n    g:format_list_indent (default 0): indent spaces from beginning of current line to the item head.\r\n \r\n* Example:\r\n\r\n    If you want to comment lines from line 19 to line 82 in a C++ file, just input:\r\n    \r\n    :19,82 AddEnumerateList \/\/\r\n\r\ninput below command to cancel this enumerate list:\r\n\r\n    :19,82 DelEnumerateList \/\/\r\n\r\n5. Text block addition and deletion\r\n-----------------------------------------------\r\n\r\n    Two commands are provided to add text block with selected lines and delete this block.\r\n\r\n        +++++++++++++++++++++++++++++++\r\n        +      :[range]AddTextBlock {symbol}      +\r\n        +      :[range]DelTextBlock {symbol}        +\r\n        +++++++++++++++++++++++++++++++\r\n\r\n* Detail:\r\n\r\n    [range] - same usage as Statistics.\r\n    {symbol} - script will use this character to construct broader of boundary.\r\n\r\n* NOTE: \r\n\r\n    (1) This fucntion can be commbined with enumerate list to add or delete comment for any programming language.\r\n\r\n* Control parameters: some global variables to control format function\r\n\r\n    g:format_block_ceil (default 0): empty lines from above content to the boundary of block.\r\n    g:format_block_floor (default 0): empty lines form the boundary of block to below content.\r\n    g:format_block_indent (default 0): indent spaces from beginning of current line to left boundary of block.\r\n    g:format_block_internal_ceil (default 0): empty lines form ceiling boundary to the first line of block contents.\r\n    g:format_block_internal_floor (default 0):  empty line form the last line of block contents to floor boundary.\r\n\r\n* Example:\r\n\r\n    Here are lines to add in text block:\r\n\r\n####################\r\n#      (above contents)      #\r\n#                                         #\r\n#      block contents          #\r\n#                                         #\r\n#      (below contents)       #\r\n####################\r\n\r\nIf you input a command (all parameters by default values):\r\n\r\n    :'<,'> AddTextBlock *\r\n\r\nthen we have:\r\n\r\n#########################\r\n#      (above contents)                 #\r\n#                                                    #\r\n#      **************************       #\r\n#      *      block contents      *      #\r\n#      **************************       #\r\n#                                                    #\r\n#      (below contents)                  #\r\n#########################\r\n\r\nif you input:\r\n\r\n    :'<,'> DelTextBlock *\r\n\r\nwe have:\r\n\r\n####################\r\n#      (above contents)      #\r\n#                                         #\r\n#                                         #\r\n#      block contents          #\r\n#                                         #\r\n#                                         #\r\n#      (below contents)       #\r\n####################\r\n\r\n6. Auto-complete matched pair parenthesis\r\n------------------------------------------------------------\r\n\r\n    Here provides a function to auto-complete match parenthesis in your insert mode. It completes matched pairs of (), [], {}, and <>, and immediately move cursor leftwards to the middle of pairs. If you input anti-parenthesis, it will erase the extra one.\r\n    \r\n7. Headline and footline addition\r\n--------------------------------------------\r\n\r\n    Do you see previous line? Yeah, it was made by command \":footlilne-\". It will draw head line or foot line whose length is equal to current line.\r\n\r\n\r\n        ++++++++++++++++++++++++++++++++\r\n        +      :[line number] HeadLine {symbol}      +\r\n        +      :[line number] FootLine {symbol}        +\r\n        ++++++++++++++++++++++++++++++++\r\n\r\n* Detail:\r\n\r\n    {symbol} - head line or foot line are made with this character.\r\n\r\n8. Enhance completion function\r\n-------------------------------------------\r\n    \r\n    Here provides a function to binding completion with <Tab> key. When you hit <Tab> in the insert mode, it will complete your content by your omni-function if you set your own omni-function, otherwise, the nearest known words or keywords of the dictionary you set (control by option 'dictionary') will be completed.\r\n\r\n\r\nUPGRADE\r\n=========\r\n\r\nBy default, GetLatestVimScripts plugin is included in Vim installation package, whose version is higher than v7. So you can use it to auto-download the newest package. Add below line into file \"GetLatestVimScripts.dat\":\r\n\r\n                           2418 1 format-helper\r\n\r\nand use this command \":GetLatestVimScripts\" to upgrade it.\r\n\r\n\r\n********************\r\n*      NOTICE      *\r\n********************\r\n\r\n      When you want to hack this script, please make sure that the option 'Tlist_Show_Menu' is closed (set its value as 0) if \"Taglist\" plugin was installed in your Vim. Otherwise, it will popup an annoyed message \"E792: Empty menu name\".","install_details":"(1) For Unix: Copy \"format_helper.vim\" script to $HOME\/.vim\/plugin\/\r\n\r\n(2) For Windows: Copy \"format_helper.vim\" to $VIM\\vimfiles\\plugin\\","5":"(1) For Unix: Copy \"format_helper.vim\" script to $HOME\/.vim\/plugin\/\r\n\r\n(2) For Windows: Copy \"format_helper.vim\" to $VIM\\vimfiles\\plugin\\","first_name":"Frank","6":"Frank","last_name":"Sun","7":"Sun","releases":[{"0":"2418","vim_version":"7.0","1":"7.0","script_version":"1.7.8","2":"1.7.8","version_comment":"+ Support to handle wide character language (such as Chinese, Japanese, etc): (1) \":HeadLine\" and \":FootLine\"; (2) \":AddTextBlock\".","3":"+ Support to handle wide character language (such as Chinese, Japanese, etc): (1) \":HeadLine\" and \":FootLine\"; (2) \":AddTextBlock\".","package":"format-helper.zip","4":"format-helper.zip","src_id":"9447","5":"9447","creation_date":"1226032789","6":"1226032789"},{"0":"2418","vim_version":"7.0","1":"7.0","script_version":"1.7.6","2":"1.7.6","version_comment":"+ Enhance character counting and word counting of Statistics() to support wide character such as Chinese, Japanese, etc.\r\n+ Enhance Enumeratelist.Del(), Numberlist.Del() and Textblock.Del() to keep original indent width when their head were deleted.\r\n- Fix BUGs in Numberlist.Del().","3":"+ Enhance character counting and word counting of Statistics() to support wide character such as Chinese, Japanese, etc.\r\n+ Enhance Enumeratelist.Del(), Numberlist.Del() and Textblock.Del() to keep original indent width when their head were deleted.\r\n- Fix BUGs in Numberlist.Del().","package":"format-helper.zip","4":"format-helper.zip","src_id":"9436","5":"9436","creation_date":"1225938142","6":"1225938142"},{"0":"2418","vim_version":"7.0","1":"7.0","script_version":"1.7.2","2":"1.7.2","version_comment":"+ In order to enhance stability of script, change all global \"interval\" variables to script variables (remark with 's:').\r\n\r\n- Fixed BUGs in Numberlist.Del(), LastNumberList(), Enumeratelist.Del().","3":"+ In order to enhance stability of script, change all global \"interval\" variables to script variables (remark with 's:').\r\n\r\n- Fixed BUGs in Numberlist.Del(), LastNumberList(), Enumeratelist.Del().","package":"format-helper.zip","4":"format-helper.zip","src_id":"9411","5":"9411","creation_date":"1225248976","6":"1225248976"},{"0":"2418","vim_version":"7.0","1":"7.0","script_version":"1.7","2":"1.7","version_comment":"+ Enhance AddNumberList to support assigned beginning index number or automatically continue with the last index of previous number list in above context.","3":"+ Enhance AddNumberList to support assigned beginning index number or automatically continue with the last index of previous number list in above context.","package":"format-helper.zip","4":"format-helper.zip","src_id":"9407","5":"9407","creation_date":"1225173112","6":"1225173112"},{"0":"2418","vim_version":"7.0","1":"7.0","script_version":"1.51","2":"1.51","version_comment":"- Fixed a BUG in AddTextBlock to handle '\\t';\r\n+ Modified readme.txt;","3":"- Fixed a BUG in AddTextBlock to handle '\\t';\r\n+ Modified readme.txt;","package":"format-helper.zip","4":"format-helper.zip","src_id":"9404","5":"9404","creation_date":"1225095692","6":"1225095692"}]},"2417":{"script_id":"2417","0":"2417","script_name":"Merb & Datamapper","1":"Merb & Datamapper","script_type":"syntax","2":"syntax","summary":"Syntax files for Merb and Datamapper","3":"Syntax files for Merb and Datamapper","description":"This is a set of vim plugins for Merb, including Datamapper, jQuery and features.\r\nCurrently, it's mostly composed of syntax files for Vim coloration.\r\n\r\nAdditional links\r\n\r\n * The syntax file for HAML can be found here: http:\/\/www.vim.org\/scripts\/script.php?script_id=1773\r\n * If you prefer Rspec stories to cucumber feature, you can use the vim-story plugin: http:\/\/github.com\/agile\/vim-story\/tree\r\n * Thanks to Tim Pope for its incredible Rails.vim: http:\/\/rails.vim.tpope.net\/\r\n\r\nIf you want to follow this plugin, you can do it on http:\/\/github.com\/nono\/merb.vim\/tree\/master.","4":"This is a set of vim plugins for Merb, including Datamapper, jQuery and features.\r\nCurrently, it's mostly composed of syntax files for Vim coloration.\r\n\r\nAdditional links\r\n\r\n * The syntax file for HAML can be found here: http:\/\/www.vim.org\/scripts\/script.php?script_id=1773\r\n * If you prefer Rspec stories to cucumber feature, you can use the vim-story plugin: http:\/\/github.com\/agile\/vim-story\/tree\r\n * Thanks to Tim Pope for its incredible Rails.vim: http:\/\/rails.vim.tpope.net\/\r\n\r\nIf you want to follow this plugin, you can do it on http:\/\/github.com\/nono\/merb.vim\/tree\/master.","install_details":"You can install it with `rake install`, or simply copy file to your vim directory.","5":"You can install it with `rake install`, or simply copy file to your vim directory.","first_name":"Bruno","6":"Bruno","last_name":"Michel","7":"Michel","releases":[{"0":"2417","vim_version":"6.0","1":"6.0","script_version":"0.1.0","2":"0.1.0","version_comment":"Initial upload","3":"Initial upload","package":"merb.vim.tgz","4":"merb.vim.tgz","src_id":"9399","5":"9399","creation_date":"1224893816","6":"1224893816"}]},"2416":{"script_id":"2416","0":"2416","script_name":"jQuery","1":"jQuery","script_type":"syntax","2":"syntax","summary":"Syntax file for jQuery","3":"Syntax file for jQuery","description":"jQuery is a fast and concise JavaScript Library that simplifies HTML document traversing, event handling, animating, and Ajax interactions for rapid web development. jQuery is designed to change the way that you write JavaScript. See http:\/\/jquery.com\/ for more details.\r\n\r\nThe syntax file for Vim add some colorations for jQuery keywords (empty clone hasClass hide show animate ...) and for CSS selectors (:empty :hidden :selected :first ...).","4":"jQuery is a fast and concise JavaScript Library that simplifies HTML document traversing, event handling, animating, and Ajax interactions for rapid web development. jQuery is designed to change the way that you write JavaScript. See http:\/\/jquery.com\/ for more details.\r\n\r\nThe syntax file for Vim add some colorations for jQuery keywords (empty clone hasClass hide show animate ...) and for CSS selectors (:empty :hidden :selected :first ...).","install_details":"Copy the jquery.vim file to $HOME\/.vim\/syntax\/ and add the following line to your vimrc:\r\nau BufRead,BufNewFile jquery.*.js set ft=javascript syntax=jquery","5":"Copy the jquery.vim file to $HOME\/.vim\/syntax\/ and add the following line to your vimrc:\r\nau BufRead,BufNewFile jquery.*.js set ft=javascript syntax=jquery","first_name":"Bruno","6":"Bruno","last_name":"Michel","7":"Michel","releases":[{"0":"2416","vim_version":"7.0","1":"7.0","script_version":"0.5.2","2":"0.5.2","version_comment":"Fix an invalid regular expression","3":"Fix an invalid regular expression","package":"jquery.vim","4":"jquery.vim","src_id":"15752","5":"15752","creation_date":"1306662716","6":"1306662716"},{"0":"2416","vim_version":"7.0","1":"7.0","script_version":"0.5.1","2":"0.5.1","version_comment":"Fix an error with contains (it's a reserved keyword for Vim).","3":"Fix an error with contains (it's a reserved keyword for Vim).","package":"jquery.vim","4":"jquery.vim","src_id":"15632","5":"15632","creation_date":"1305312475","6":"1305312475"},{"0":"2416","vim_version":"7.0","1":"7.0","script_version":"0.5","2":"0.5","version_comment":"Upgrade to match jquery 1.6 keywords","3":"Upgrade to match jquery 1.6 keywords","package":"jquery.vim","4":"jquery.vim","src_id":"15583","5":"15583","creation_date":"1304547276","6":"1304547276"},{"0":"2416","vim_version":"6.0","1":"6.0","script_version":"0.4","2":"0.4","version_comment":"Avoid the dotted filetype syntax. Thanks Jeremy Cantrell for the patch.","3":"Avoid the dotted filetype syntax. Thanks Jeremy Cantrell for the patch.","package":"jquery.vim","4":"jquery.vim","src_id":"12276","5":"12276","creation_date":"1265145900","6":"1265145900"},{"0":"2416","vim_version":"7.0","1":"7.0","script_version":"0.3","2":"0.3","version_comment":"Recognize new keywords for jQuery 1.4","3":"Recognize new keywords for jQuery 1.4","package":"jquery.vim","4":"jquery.vim","src_id":"12107","5":"12107","creation_date":"1263519010","6":"1263519010"},{"0":"2416","vim_version":"6.0","1":"6.0","script_version":"0.3","2":"0.3","version_comment":"Some fixes to jquery.vim by Taylon","3":"Some fixes to jquery.vim by Taylon","package":"jquery.vim","4":"jquery.vim","src_id":"11482","5":"11482","creation_date":"1254692128","6":"1254692128"},{"0":"2416","vim_version":"7.0","1":"7.0","script_version":"0.2","2":"0.2","version_comment":"Upgrade jquery.vim to match jquery 1.3","3":"Upgrade jquery.vim to match jquery 1.3","package":"jquery.vim","4":"jquery.vim","src_id":"11415","5":"11415","creation_date":"1253476757","6":"1253476757"},{"0":"2416","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"jquery.vim","4":"jquery.vim","src_id":"9398","5":"9398","creation_date":"1224893045","6":"1224893045"}]},"2415":{"script_id":"2415","0":"2415","script_name":"textobj-diff","1":"textobj-diff","script_type":"utility","2":"utility","summary":"Text objects for ouputs of diff(1)","3":"Text objects for ouputs of diff(1)","description":"*textobj-diff* is a Vim plugin to provide text objects for outputs of diff(1).\r\nCurrently it supports the following formats:\r\n- diff --context\r\n- diff --unified\r\n- git diff\r\n\r\n\r\nRequirements:\r\n- Vim 7.2 or later\r\n- |textobj-user| 0.3.7 or later (vimscript#2100)\r\n\r\nLatest version:\r\nhttp:\/\/github.com\/kana\/vim-textobj-diff\r\n\r\nDocument in HTML format:\r\nhttp:\/\/kana.github.com\/config\/vim\/textobj-diff.html","4":"*textobj-diff* is a Vim plugin to provide text objects for outputs of diff(1).\r\nCurrently it supports the following formats:\r\n- diff --context\r\n- diff --unified\r\n- git diff\r\n\r\n\r\nRequirements:\r\n- Vim 7.2 or later\r\n- |textobj-user| 0.3.7 or later (vimscript#2100)\r\n\r\nLatest version:\r\nhttp:\/\/github.com\/kana\/vim-textobj-diff\r\n\r\nDocument in HTML format:\r\nhttp:\/\/kana.github.com\/config\/vim\/textobj-diff.html","install_details":"...","5":"...","first_name":"Kana","6":"Kana","last_name":"Natsuno","7":"Natsuno","releases":[{"0":"2415","vim_version":"7.0","1":"7.0","script_version":"0.0.0","2":"0.0.0","version_comment":"Initial upload","3":"Initial upload","package":"vim-textobj-diff-0.0.0.zip","4":"vim-textobj-diff-0.0.0.zip","src_id":"9392","5":"9392","creation_date":"1224794185","6":"1224794185"}]},"2414":{"script_id":"2414","0":"2414","script_name":"Tango2 ","1":"Tango2 ","script_type":"color scheme","2":"color scheme","summary":"A Tango based colour theme for Vim (ported from gedit)","3":"A Tango based colour theme for Vim (ported from gedit)","description":"This is a colour scheme based on the tango colour palette. \r\n\r\nA screenshot can be found at\r\n   http:\/\/www.cse.iitm.ac.in\/~spranesh\/tango2\/vim.html\r\n\r\n","4":"This is a colour scheme based on the tango colour palette. \r\n\r\nA screenshot can be found at\r\n   http:\/\/www.cse.iitm.ac.in\/~spranesh\/tango2\/vim.html\r\n\r\n","install_details":"Put tango2.vim\r\n\r\nin $VIM\/colors\/\r\n\r\nand restart vim","5":"Put tango2.vim\r\n\r\nin $VIM\/colors\/\r\n\r\nand restart vim","first_name":"Pranesh","6":"Pranesh","last_name":"Srinivasan","7":"Srinivasan","releases":[{"0":"2414","vim_version":"6.0","1":"6.0","script_version":"0.4","2":"0.4","version_comment":"Initial upload","3":"Initial upload","package":"tango2.vim","4":"tango2.vim","src_id":"9387","5":"9387","creation_date":"1224773918","6":"1224773918"}]},"2413":{"script_id":"2413","0":"2413","script_name":"Miranda syntax highlighting","1":"Miranda syntax highlighting","script_type":"syntax","2":"syntax","summary":"Miranda syntax highlighting","3":"Miranda syntax highlighting","description":"This file is very beta, if there any mistakes, welcome to point out.","4":"This file is very beta, if there any mistakes, welcome to point out.","install_details":"1. copy to <runtimepath>\/syntax\/\r\n2. add the lines in filetype.vim to <runtimepath>\/filetype.vim or just overwrite it if you don't care.\r\n\r\nPS:to find out runtimepath, use \":set runtimepath\" in vim.\r\nPS2:link vim to Miranda as default editor using \"\/editor vim --cmd \"set ff=unix\" +! %\" in Miranda ","5":"1. copy to <runtimepath>\/syntax\/\r\n2. add the lines in filetype.vim to <runtimepath>\/filetype.vim or just overwrite it if you don't care.\r\n\r\nPS:to find out runtimepath, use \":set runtimepath\" in vim.\r\nPS2:link vim to Miranda as default editor using \"\/editor vim --cmd \"set ff=unix\" +! %\" in Miranda ","first_name":"Wei","6":"Wei","last_name":"Chen","7":"Chen","releases":[{"0":"2413","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"minor problem fixed","3":"minor problem fixed","package":"Miranda.vim","4":"Miranda.vim","src_id":"9385","5":"9385","creation_date":"1224663001","6":"1224663001"},{"0":"2413","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"filetype.vim","3":"filetype.vim","package":"filetype.vim","4":"filetype.vim","src_id":"9382","5":"9382","creation_date":"1224655799","6":"1224655799"}]},"2412":{"script_id":"2412","0":"2412","script_name":"lastchange","1":"lastchange","script_type":"utility","2":"utility","summary":"Auto write last change time","3":"Auto write last change time","description":"example:\r\n    before script run:\r\n        \/*\r\n         *       Filename: example.h\r\n         *           Create: 2008-8-8, 00:00:00\r\n         * Last Change: \r\n         *\/\r\n     after script run:\r\n        \/*\r\n         *       Filename: example.h\r\n         *           Create: 2008-8-8, 00:00:00\r\n         * Last Change: 2008-8-8, 11:11:11\r\n         *\/\r\n\r\ng:lastChangeName: default is 'Last Change:'\r\n    script will search this and put now time behind this.\r\n\r\ng:lastChangeSearchStart: default is 1\r\n    search range.\r\ng:lastChangeSearchEnd: default is 5\r\n    search range.\r\n\r\ng:lastChangeAutoWrite: default is 0 (false)\r\n    if this is true(1),script will run when you are saving and file is matching of g:lastChangeAutoWriteFile.\r\n\r\ng:lastChangeAutoWriteFile: default is '*.c,*.C,*.cpp,*.cxx,*.h,*.hpp,*.hxx,*.java,*.py'","4":"example:\r\n    before script run:\r\n        \/*\r\n         *       Filename: example.h\r\n         *           Create: 2008-8-8, 00:00:00\r\n         * Last Change: \r\n         *\/\r\n     after script run:\r\n        \/*\r\n         *       Filename: example.h\r\n         *           Create: 2008-8-8, 00:00:00\r\n         * Last Change: 2008-8-8, 11:11:11\r\n         *\/\r\n\r\ng:lastChangeName: default is 'Last Change:'\r\n    script will search this and put now time behind this.\r\n\r\ng:lastChangeSearchStart: default is 1\r\n    search range.\r\ng:lastChangeSearchEnd: default is 5\r\n    search range.\r\n\r\ng:lastChangeAutoWrite: default is 0 (false)\r\n    if this is true(1),script will run when you are saving and file is matching of g:lastChangeAutoWriteFile.\r\n\r\ng:lastChangeAutoWriteFile: default is '*.c,*.C,*.cpp,*.cxx,*.h,*.hpp,*.hxx,*.java,*.py'","install_details":"copy to the $VIMFILES\/plugin directory.","5":"copy to the $VIMFILES\/plugin directory.","first_name":"kangzhi","6":"kangzhi","last_name":"shi","7":"shi","releases":[{"0":"2412","vim_version":"6.0","1":"6.0","script_version":"1.1","2":"1.1","version_comment":"FIX if you are using fold and find the g:lastChangeName in a closed fold,script will replace this fold.","3":"FIX if you are using fold and find the g:lastChangeName in a closed fold,script will replace this fold.","package":"lastchange.vim","4":"lastchange.vim","src_id":"9408","5":"9408","creation_date":"1225190970","6":"1225190970"},{"0":"2412","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"lastchange.vim","4":"lastchange.vim","src_id":"9380","5":"9380","creation_date":"1224653355","6":"1224653355"}]},"2411":{"script_id":"2411","0":"2411","script_name":"Yow","1":"Yow","script_type":"game","2":"game","summary":"Random Zippy The Pinhead quotes.  A port of Emacs' M-x yow.","3":"Random Zippy The Pinhead quotes.  A port of Emacs' M-x yow.","description":"A port of the M-x yow feature in Emacs.  Entering the command :Yow earns you a random Zippy The Pinhead quote.\r\n\r\nThe quotes are stored in the file \"yow.lines\", which i borrowed from Emacs.\r\n\r\nDefining your own quotes is possible by changing yow.lines.  The format is explained in the yow.lines file.","4":"A port of the M-x yow feature in Emacs.  Entering the command :Yow earns you a random Zippy The Pinhead quote.\r\n\r\nThe quotes are stored in the file \"yow.lines\", which i borrowed from Emacs.\r\n\r\nDefining your own quotes is possible by changing yow.lines.  The format is explained in the yow.lines file.","install_details":"Download yow.vba, open in vim, run :so %.\r\n\r\nThe following files are installed:\r\n\r\nplugin\/yow.vim\r\nyow.lines\r\ndoc\/yow.txt\r\n\r\nall with respect to your runtime path.  If you get permission errors, you may need to create the directory .vim in your home directory, and check it is in your runtimepath.\r\n\r\nEnter :h Yow for help.\r\n\r\n\r\n\r\n\r\n\r\nVote for ME -- I'm well-tapered, half-cocked, ill-conceived and TAX-DEFERRED!","5":"Download yow.vba, open in vim, run :so %.\r\n\r\nThe following files are installed:\r\n\r\nplugin\/yow.vim\r\nyow.lines\r\ndoc\/yow.txt\r\n\r\nall with respect to your runtime path.  If you get permission errors, you may need to create the directory .vim in your home directory, and check it is in your runtimepath.\r\n\r\nEnter :h Yow for help.\r\n\r\n\r\n\r\n\r\n\r\nVote for ME -- I'm well-tapered, half-cocked, ill-conceived and TAX-DEFERRED!","first_name":"Matthew","6":"Matthew","last_name":"Hague","7":"Hague","releases":[{"0":"2411","vim_version":"7.0","1":"7.0","script_version":"1","2":"1","version_comment":"Initial upload","3":"Initial upload","package":"yow.vba","4":"yow.vba","src_id":"9379","5":"9379","creation_date":"1224632252","6":"1224632252"}]},"2410":{"script_id":"2410","0":"2410","script_name":"ku-args","1":"ku-args","script_type":"utility","2":"utility","summary":"ku source: args","3":"ku source: args","description":"*ku-args* is a source for |ku| to deal with |argument-list|.  You can choose\r\none from many files in the argument list and do some action on it.\r\n\r\n\r\nRequirements:\r\n- Vim 7.2 or later\r\n- |ku| 0.2.0 or later (vimscript#2337)\r\n\r\nLatest version:\r\nhttp:\/\/github.com\/kana\/vim-ku-args\r\n\r\nDocument in HTML format:\r\nhttp:\/\/kana.github.com\/config\/vim\/ku-args.html","4":"*ku-args* is a source for |ku| to deal with |argument-list|.  You can choose\r\none from many files in the argument list and do some action on it.\r\n\r\n\r\nRequirements:\r\n- Vim 7.2 or later\r\n- |ku| 0.2.0 or later (vimscript#2337)\r\n\r\nLatest version:\r\nhttp:\/\/github.com\/kana\/vim-ku-args\r\n\r\nDocument in HTML format:\r\nhttp:\/\/kana.github.com\/config\/vim\/ku-args.html","install_details":"...","5":"...","first_name":"Kana","6":"Kana","last_name":"Natsuno","7":"Natsuno","releases":[{"0":"2410","vim_version":"7.0","1":"7.0","script_version":"0.1.1","2":"0.1.1","version_comment":"- Update for ku 0.2.1.","3":"- Update for ku 0.2.1.","package":"vim-ku-args-0.1.1.zip","4":"vim-ku-args-0.1.1.zip","src_id":"10511","5":"10511","creation_date":"1241374406","6":"1241374406"},{"0":"2410","vim_version":"7.0","1":"7.0","script_version":"0.1.0","2":"0.1.0","version_comment":"- Update for ku 0.2.0.","3":"- Update for ku 0.2.0.","package":"vim-ku-args-0.1.0.zip","4":"vim-ku-args-0.1.0.zip","src_id":"10475","5":"10475","creation_date":"1240919630","6":"1240919630"},{"0":"2410","vim_version":"7.0","1":"7.0","script_version":"0.0.1","2":"0.0.1","version_comment":"- Rewrite |ku-args-action-table| and |ku-args-key-table|.  Old ones\n  did not properly work.","3":"- Rewrite |ku-args-action-table| and |ku-args-key-table|.  Old ones\n  did not properly work.","package":"vim-ku-args-0.0.1.zip","4":"vim-ku-args-0.0.1.zip","src_id":"9376","5":"9376","creation_date":"1224552807","6":"1224552807"},{"0":"2410","vim_version":"7.0","1":"7.0","script_version":"0.0.0","2":"0.0.0","version_comment":"Initial upload","3":"Initial upload","package":"vim-ku-args-0.0.0.zip","4":"vim-ku-args-0.0.0.zip","src_id":"9373","5":"9373","creation_date":"1224434294","6":"1224434294"}]},"2409":{"script_id":"2409","0":"2409","script_name":"sql_iabbr 2","1":"sql_iabbr 2","script_type":"ftplugin","2":"ftplugin","summary":"convert SQL keywords uppercase automatically. ","3":"convert SQL keywords uppercase automatically. ","description":"With this ftplugin you can type \"create table foo (foo_id int);\" and get \"CREATE TABLE foo (foo_id INT);\".  It is based on both sql.vim and the output from postgresql's \\dT command while in psql.  That makes it a tad bit tailored to postgresql, but it will work with any SQL compliant dbms. \r\n\r\nI probably won't upload every update I make immediately so the most current version may be found on github.\r\nhttp:\/\/github.com\/xenoterracide\/sql_iabbr\/tree\/master\r\ngit:\/\/github.com\/xenoterracide\/sql_iabbr.git\r\n\r\nearlier versions of this plugin are here http:\/\/www.vim.org\/scripts\/script.php?script_id=305 I am unable to contact Michael Brailsford so have forked the script with my changes. Changes have currently amounted to adding reserved words that weren't present.","4":"With this ftplugin you can type \"create table foo (foo_id int);\" and get \"CREATE TABLE foo (foo_id INT);\".  It is based on both sql.vim and the output from postgresql's \\dT command while in psql.  That makes it a tad bit tailored to postgresql, but it will work with any SQL compliant dbms. \r\n\r\nI probably won't upload every update I make immediately so the most current version may be found on github.\r\nhttp:\/\/github.com\/xenoterracide\/sql_iabbr\/tree\/master\r\ngit:\/\/github.com\/xenoterracide\/sql_iabbr.git\r\n\r\nearlier versions of this plugin are here http:\/\/www.vim.org\/scripts\/script.php?script_id=305 I am unable to contact Michael Brailsford so have forked the script with my changes. Changes have currently amounted to adding reserved words that weren't present.","install_details":"copy to ~\/.vim\/ftplugin\/sql, and you're good to go.  ","5":"copy to ~\/.vim\/ftplugin\/sql, and you're good to go.  ","first_name":"Caleb","6":"Caleb","last_name":"Cushing","7":"Cushing","releases":[{"0":"2409","vim_version":"6.0","1":"6.0","script_version":"2.0.1","2":"2.0.1","version_comment":"just updating download urls and version.","3":"just updating download urls and version.","package":"sql_iabbr.vim","4":"sql_iabbr.vim","src_id":"9374","5":"9374","creation_date":"1224446395","6":"1224446395"},{"0":"2409","vim_version":"6.0","1":"6.0","script_version":"2.0.0","2":"2.0.0","version_comment":"Initial upload","3":"Initial upload","package":"sql_iabbr.vim","4":"sql_iabbr.vim","src_id":"9372","5":"9372","creation_date":"1224418698","6":"1224418698"}]},"2408":{"script_id":"2408","0":"2408","script_name":"Refactor Color Scheme","1":"Refactor Color Scheme","script_type":"color scheme","2":"color scheme","summary":"Refactor Color Scheme","3":"Refactor Color Scheme","description":"A simple colorscheme made with the help of http:\/\/yukihiro.nakadaira.googlepages.com\/vim-color.html\r\nand based on the color scheme used in the snippet code of http:\/\/refactormycode.com\/\r\n\r\nEnjoy!","4":"A simple colorscheme made with the help of http:\/\/yukihiro.nakadaira.googlepages.com\/vim-color.html\r\nand based on the color scheme used in the snippet code of http:\/\/refactormycode.com\/\r\n\r\nEnjoy!","install_details":"Put it in the ~\/.vim\/colors folder an then load it with \r\n:colorscheme refactor \r\nor by putting \r\ncolorscheme refactor\r\non your [g]vimrc file","5":"Put it in the ~\/.vim\/colors folder an then load it with \r\n:colorscheme refactor \r\nor by putting \r\ncolorscheme refactor\r\non your [g]vimrc file","first_name":"Gabriele","6":"Gabriele","last_name":"Fontana","7":"Fontana","releases":[{"0":"2408","vim_version":"6.0","1":"6.0","script_version":"1","2":"1","version_comment":"Initial upload","3":"Initial upload","package":"refactor.vim","4":"refactor.vim","src_id":"9366","5":"9366","creation_date":"1224266974","6":"1224266974"}]},"2407":{"script_id":"2407","0":"2407","script_name":"MatlabFilesEdition","1":"MatlabFilesEdition","script_type":"utility","2":"utility","summary":"A set of files useful to edit Matlab files (indent, syntax,tags , mlint use...)","3":"A set of files useful to edit Matlab files (indent, syntax,tags , mlint use...)","description":"Contains a set of files useful to edit Matlab files.\r\n\r\nIncluded is :\r\n1) Syntax highlighting\r\n2) Correct setting to use the matchit.vim script (extension of the % command to match if\/end, for\/end,... blocks)\r\n3) Correct indentation\r\n4) Integration of mlint (Matlab code checker) with the :make command\r\n5)Tag support\r\n6) Help file\r\n\r\n\r\n\r\n1) Syntax highlighting\r\n\r\nsyntax\/matlab.vim : Updates the matlab.vim syntax file provided in the vim distribution :\r\n- highlights keywords dealing with exceptions : try \/ catch \/ rethrow\r\n- highlights keywords dealing with class definitions : classdef \/ properties \/ methods \/ events\r\n- highlights most Matlab functions\r\n\r\n2) Correct settings in order to use the matchit.vim script \r\n\r\nThe matchit.vim extends the % matching and enables to jump through matching groups such as \"if\/end\" or \"swicth\/end\" blocks (see :help matchit in vim)\r\n\r\nftplugin\/matlab.m provides the suitable definition for b:match_words in order to jump between if\/end, classdef\/end, methods\/end, events\/end, properties\/end, while\/end, for\/end, switch\/end, try\/end, function\/end blocks\r\n\r\n3) Correct indentation\r\nindent\/matlab.vim : Updates the matlab.vim indention file provided in the vim distribution.\r\nThis script provides a correct indentation for :\r\n- switch \/ end, try \/ catch blocks\r\n- classdef \/ methods \/ properties \/ events\r\n- mutli-line (lines with line continuation operator (...))\r\n\r\nThis script has been tested with the Matlab R2008a release on many files and the result of indentation compared to the one provided by the Matlab Editor (with 'indent all functions' option set)\r\n\r\nNOTE : to work correctly, this script need the matchit.vim (vimscript#39) to be installed.\r\n\r\n4) Integration of mlint (Matlab code checker) with the :make command\r\n\r\ncompiler\/mlint.m provides the settings to use mlint (Matlab code ckecker) and puts the messages reported in the quickfix buffer.\r\n\r\nWhenever you want to check your code, just type :make and then :copen and vim opens a quickfix buffer which enables to jump to errors (using :cn, :cp or Enter to jump to the error under the cursor : see :help quickfix in vim)\r\n\r\n5)Tag support\r\nThe .ctags file (in the matlab.tar.gz) defines the Matlab language so that the exuberant ctags (http:\/\/ctags.sourceforge.net ) can construct the tag file : you can now jump to tags (using CTRL-] (or CTRL-$ if using Windows) and go back again (CTRL-T)\r\nSee also :help tags in vim.\r\n\r\n\r\nThese scipts have been tested using gvim 7.2 and Matlab R2008a on Windows.\r\n\r\n\r\n\r\n","4":"Contains a set of files useful to edit Matlab files.\r\n\r\nIncluded is :\r\n1) Syntax highlighting\r\n2) Correct setting to use the matchit.vim script (extension of the % command to match if\/end, for\/end,... blocks)\r\n3) Correct indentation\r\n4) Integration of mlint (Matlab code checker) with the :make command\r\n5)Tag support\r\n6) Help file\r\n\r\n\r\n\r\n1) Syntax highlighting\r\n\r\nsyntax\/matlab.vim : Updates the matlab.vim syntax file provided in the vim distribution :\r\n- highlights keywords dealing with exceptions : try \/ catch \/ rethrow\r\n- highlights keywords dealing with class definitions : classdef \/ properties \/ methods \/ events\r\n- highlights most Matlab functions\r\n\r\n2) Correct settings in order to use the matchit.vim script \r\n\r\nThe matchit.vim extends the % matching and enables to jump through matching groups such as \"if\/end\" or \"swicth\/end\" blocks (see :help matchit in vim)\r\n\r\nftplugin\/matlab.m provides the suitable definition for b:match_words in order to jump between if\/end, classdef\/end, methods\/end, events\/end, properties\/end, while\/end, for\/end, switch\/end, try\/end, function\/end blocks\r\n\r\n3) Correct indentation\r\nindent\/matlab.vim : Updates the matlab.vim indention file provided in the vim distribution.\r\nThis script provides a correct indentation for :\r\n- switch \/ end, try \/ catch blocks\r\n- classdef \/ methods \/ properties \/ events\r\n- mutli-line (lines with line continuation operator (...))\r\n\r\nThis script has been tested with the Matlab R2008a release on many files and the result of indentation compared to the one provided by the Matlab Editor (with 'indent all functions' option set)\r\n\r\nNOTE : to work correctly, this script need the matchit.vim (vimscript#39) to be installed.\r\n\r\n4) Integration of mlint (Matlab code checker) with the :make command\r\n\r\ncompiler\/mlint.m provides the settings to use mlint (Matlab code ckecker) and puts the messages reported in the quickfix buffer.\r\n\r\nWhenever you want to check your code, just type :make and then :copen and vim opens a quickfix buffer which enables to jump to errors (using :cn, :cp or Enter to jump to the error under the cursor : see :help quickfix in vim)\r\n\r\n5)Tag support\r\nThe .ctags file (in the matlab.tar.gz) defines the Matlab language so that the exuberant ctags (http:\/\/ctags.sourceforge.net ) can construct the tag file : you can now jump to tags (using CTRL-] (or CTRL-$ if using Windows) and go back again (CTRL-T)\r\nSee also :help tags in vim.\r\n\r\n\r\nThese scipts have been tested using gvim 7.2 and Matlab R2008a on Windows.\r\n\r\n\r\n\r\n","install_details":"The package is matlab.zip : just unzip it to extract the files.\r\n\r\n1) Syntax highlighting\r\nCopy syntax\/matlab.vim to your $HOME\/vimfiles\/syntax directory\r\n\r\n2) Correct settings in order to use the matchit.vim script \r\nIn your vimrc file, add the following line :\r\nsource $VIMRUNTIME\/macros\/matchit.vim\r\n\r\nAnd copy ftplugin\/matlab.vim to your $HOME\/vimfiles\/ftplugin directory\r\n\r\n3) Correct indentation\r\nIn your vimrc file, add the following line :\r\nsource $VIMRUNTIME\/macros\/matchit.vim\r\n\r\nAnd copy indent\/matlab.vim to your $HOME\/vimfiles\/indent directory\r\n\r\n4) Integration of the mlint Matlab code checker with the :make command\r\n\r\nAdd the following line to your vimrc file :\r\nautocmd BufEnter *.m    compiler mlint \r\n\r\nAnd copy compiler\/mlint.vim to your $HOME\/vimfiles\/compiler directory\r\n\r\n5)Tag support\r\nCopy the .ctags to your $HOME directory.\r\nAnd then run the command to create tour tags file : for example :\r\nctags -R *\r\n\r\n6) help file\r\nCopy doc\/matlab.txt to your $HOME\/vimfiles\/doc directory\r\nAnd then run the command to create help for matlab :\r\n:helptags $HOME\/vimfiles\/doc\r\n\r\nAnd then the command\r\n:help matlab\r\nis available.\r\n\r\n","5":"The package is matlab.zip : just unzip it to extract the files.\r\n\r\n1) Syntax highlighting\r\nCopy syntax\/matlab.vim to your $HOME\/vimfiles\/syntax directory\r\n\r\n2) Correct settings in order to use the matchit.vim script \r\nIn your vimrc file, add the following line :\r\nsource $VIMRUNTIME\/macros\/matchit.vim\r\n\r\nAnd copy ftplugin\/matlab.vim to your $HOME\/vimfiles\/ftplugin directory\r\n\r\n3) Correct indentation\r\nIn your vimrc file, add the following line :\r\nsource $VIMRUNTIME\/macros\/matchit.vim\r\n\r\nAnd copy indent\/matlab.vim to your $HOME\/vimfiles\/indent directory\r\n\r\n4) Integration of the mlint Matlab code checker with the :make command\r\n\r\nAdd the following line to your vimrc file :\r\nautocmd BufEnter *.m    compiler mlint \r\n\r\nAnd copy compiler\/mlint.vim to your $HOME\/vimfiles\/compiler directory\r\n\r\n5)Tag support\r\nCopy the .ctags to your $HOME directory.\r\nAnd then run the command to create tour tags file : for example :\r\nctags -R *\r\n\r\n6) help file\r\nCopy doc\/matlab.txt to your $HOME\/vimfiles\/doc directory\r\nAnd then run the command to create help for matlab :\r\n:helptags $HOME\/vimfiles\/doc\r\n\r\nAnd then the command\r\n:help matlab\r\nis available.\r\n\r\n","first_name":"Fabrice","6":"Fabrice","last_name":"Guy","7":"Guy","releases":[{"0":"2407","vim_version":"7.0","1":"7.0","script_version":"1.1","2":"1.1","version_comment":"- Added support for indentation of if\/end blocks on the same line (and while\/end, for\/end,... blocks)\r\n- Changes in functions indentation : the behavior of the indentation is now the same as the 'indent all function' option in the Matlab Editor,\r\n- Insertion of comment line now inserts a comment header (%) at the beginning of a new comment","3":"- Added support for indentation of if\/end blocks on the same line (and while\/end, for\/end,... blocks)\r\n- Changes in functions indentation : the behavior of the indentation is now the same as the 'indent all function' option in the Matlab Editor,\r\n- Insertion of comment line now inserts a comment header (%) at the beginning of a new comment","package":"matlab.zip","4":"matlab.zip","src_id":"11789","5":"11789","creation_date":"1258972807","6":"1258972807"},{"0":"2407","vim_version":"7.0","1":"7.0","script_version":"1.1","2":"1.1","version_comment":"Enhanced syntax highligting for Matlab m-files : most Matlab builtin functions are now highlighted","3":"Enhanced syntax highligting for Matlab m-files : most Matlab builtin functions are now highlighted","package":"matlab.zip","4":"matlab.zip","src_id":"9409","5":"9409","creation_date":"1225205151","6":"1225205151"},{"0":"2407","vim_version":"7.0","1":"7.0","script_version":"1.0.2","2":"1.0.2","version_comment":"Wrong indentation of subfunctions without matching 'end' has been fixed","3":"Wrong indentation of subfunctions without matching 'end' has been fixed","package":"matlab.zip","4":"matlab.zip","src_id":"9396","5":"9396","creation_date":"1224851866","6":"1224851866"},{"0":"2407","vim_version":"7.0","1":"7.0","script_version":"1.0.1","2":"1.0.1","version_comment":"As pointed out by Tobias Wolf : \r\n- renamed the package to .zip\r\n- replaced the DOS endings by CR line endings\r\n\r\nAdded a help file (matlab.txt)","3":"As pointed out by Tobias Wolf : \r\n- renamed the package to .zip\r\n- replaced the DOS endings by CR line endings\r\n\r\nAdded a help file (matlab.txt)","package":"matlab.zip","4":"matlab.zip","src_id":"9377","5":"9377","creation_date":"1224580476","6":"1224580476"},{"0":"2407","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"matlab.tar.gz","4":"matlab.tar.gz","src_id":"9365","5":"9365","creation_date":"1224264239","6":"1224264239"}]},"2406":{"script_id":"2406","0":"2406","script_name":"Lissard syntax","1":"Lissard syntax","script_type":"syntax","2":"syntax","summary":"Adds Lissard syntax support to Vim.","3":"Adds Lissard syntax support to Vim.","description":"This script adds syntax for Lissard to Vim.\r\nLissard templating system: http:\/\/tweekedideas.com\/pages\/lissard","4":"This script adds syntax for Lissard to Vim.\r\nLissard templating system: http:\/\/tweekedideas.com\/pages\/lissard","install_details":"Copy into ~\/.vim\/syntax. Requires html.vim and python.vim to work.\r\nFor more info about adding new filetypes, see :he new-filetype.","5":"Copy into ~\/.vim\/syntax. Requires html.vim and python.vim to work.\r\nFor more info about adding new filetypes, see :he new-filetype.","first_name":"Jarkko","6":"Jarkko","last_name":"Piiroinen","7":"Piiroinen","releases":[{"0":"2406","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"lissard.vim","4":"lissard.vim","src_id":"9362","5":"9362","creation_date":"1224178582","6":"1224178582"}]},"2405":{"script_id":"2405","0":"2405","script_name":"Robotbattle Scripting Language","1":"Robotbattle Scripting Language","script_type":"syntax","2":"syntax","summary":"Syntax highlight for Robotbattle Scripting Language","3":"Syntax highlight for Robotbattle Scripting Language","description":"Syntax highlight for Robotbattle Scripting Language","4":"Syntax highlight for Robotbattle Scripting Language","install_details":"","5":"","first_name":"Mizard","6":"Mizard","last_name":"X","7":"X","releases":[{"0":"2405","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"rsl.vim","4":"rsl.vim","src_id":"9354","5":"9354","creation_date":"1224086776","6":"1224086776"}]},"2404":{"script_id":"2404","0":"2404","script_name":"Pit Configuration","1":"Pit Configuration","script_type":"utility","2":"utility","summary":"pit configuration library for vim","3":"pit configuration library for vim","description":"pitconfig.vim can load vim's variables from pit configurations. you can hide secret variables(ex: password) in your vimrc. pitconfig.vim set variable into vim's global scope.\r\n\r\nex)\r\n# vim\r\n:echo mypassword\r\nxxxxxx\r\n:PitAdd mypassword\r\n:e ~\/.vimrc\r\n\" remove mypassword setting in your vimrc\r\n:wq!\r\n\r\n# vim\r\n:echo mypassword\r\nxxxxxx\r\n\r\n\r\n---------------------------------\r\n:PitReload\r\n  reload pit config named as g:pitconfig_default\r\n\r\n:PitLoad profile\r\n  load pit config named as 'profile'\r\n\r\n:PitShow\r\n  show current pit config named as g:pitconfig_default\r\n:PitShow profile\r\n  show current pit config named as 'profile'\r\n\r\n:PitSave\r\n  save current variables to pit config which named as g:pitconfig_default\r\n:PitSave profile\r\n  save current variables to pit config which named as 'profile'\r\n\r\n:PitAdd varname\r\n  add variable to current pit config.\r\n\r\n:PitDel varname\r\n  delete variable from current pit config.\r\n","4":"pitconfig.vim can load vim's variables from pit configurations. you can hide secret variables(ex: password) in your vimrc. pitconfig.vim set variable into vim's global scope.\r\n\r\nex)\r\n# vim\r\n:echo mypassword\r\nxxxxxx\r\n:PitAdd mypassword\r\n:e ~\/.vimrc\r\n\" remove mypassword setting in your vimrc\r\n:wq!\r\n\r\n# vim\r\n:echo mypassword\r\nxxxxxx\r\n\r\n\r\n---------------------------------\r\n:PitReload\r\n  reload pit config named as g:pitconfig_default\r\n\r\n:PitLoad profile\r\n  load pit config named as 'profile'\r\n\r\n:PitShow\r\n  show current pit config named as g:pitconfig_default\r\n:PitShow profile\r\n  show current pit config named as 'profile'\r\n\r\n:PitSave\r\n  save current variables to pit config which named as g:pitconfig_default\r\n:PitSave profile\r\n  save current variables to pit config which named as 'profile'\r\n\r\n:PitAdd varname\r\n  add variable to current pit config.\r\n\r\n:PitDel varname\r\n  delete variable from current pit config.\r\n","install_details":"copy pitconfig.vim to your plugin directory. pitconfig.vim require perl interface and Config::Pit module on cpan.\r\n","5":"copy pitconfig.vim to your plugin directory. pitconfig.vim require perl interface and Config::Pit module on cpan.\r\n","first_name":"Yasuhiro","6":"Yasuhiro","last_name":"Matsumoto","7":"Matsumoto","releases":[{"0":"2404","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"pitconfig.vim","4":"pitconfig.vim","src_id":"9348","5":"9348","creation_date":"1223952704","6":"1223952704"}]},"2403":{"script_id":"2403","0":"2403","script_name":"stackreg","1":"stackreg","script_type":"utility","2":"utility","summary":"Vz-like stackable registers","3":"Vz-like stackable registers","description":"*stackreg* is a Vim plugin to provide stackable registers.  If you delete or\r\nyank a text without specifying a register, the text will be pushed into\r\na stack.  If you put without specifying a register, a text will be popped from\r\nthe stack then it will be put.\r\n\r\nThe concept of stackable registers is derived from Vz which is an editor for\r\nMS-DOS and it was widely used in Japan since 1989.\r\n\r\nRequirements:\r\n- Vim 7.2 or later\r\n- |advice| 0.0.0 or later (vimscript#2402)\r\n\r\nLatest version:\r\nhttp:\/\/github.com\/kana\/vim-stackreg","4":"*stackreg* is a Vim plugin to provide stackable registers.  If you delete or\r\nyank a text without specifying a register, the text will be pushed into\r\na stack.  If you put without specifying a register, a text will be popped from\r\nthe stack then it will be put.\r\n\r\nThe concept of stackable registers is derived from Vz which is an editor for\r\nMS-DOS and it was widely used in Japan since 1989.\r\n\r\nRequirements:\r\n- Vim 7.2 or later\r\n- |advice| 0.0.0 or later (vimscript#2402)\r\n\r\nLatest version:\r\nhttp:\/\/github.com\/kana\/vim-stackreg","install_details":"...","5":"...","first_name":"Kana","6":"Kana","last_name":"Natsuno","7":"Natsuno","releases":[{"0":"2403","vim_version":"7.0","1":"7.0","script_version":"0.0.0","2":"0.0.0","version_comment":"Initial upload","3":"Initial upload","package":"vim-stackreg-0.0.0.zip","4":"vim-stackreg-0.0.0.zip","src_id":"9346","5":"9346","creation_date":"1223886080","6":"1223886080"}]},"2402":{"script_id":"2402","0":"2402","script_name":"advice","1":"advice","script_type":"utility","2":"utility","summary":"alter the behavior of a command in modular way","3":"alter the behavior of a command in modular way","description":"*advice* is a library for Vim scripts to provide a modular way to alter the\r\nbehavior of a command.\r\n\r\nFor example, if you want to change the default register for the command |C| to\r\n\"_ (|quote_|), you have to write a new operator then map |C| to execute the\r\noperator, i.e., redefine the whole command.  But how about if you also want to\r\nchange |C| in Visual mode to always behave as same as the default |C| in\r\n|blockwise-visual| mode?  How about if you want to disable one of the altered\r\nbehaviors afterwards?  Therefore, redefining the whole command is not elegant\r\nway.\r\n\r\nADVICE provides useful API to do such customization.\r\n\r\nThe concept of ADVICE is derived from the one of Emacs.  See also:\r\nhttp:\/\/www.gnu.org\/software\/emacs\/elisp\/html_node\/Advising-Functions.html .\r\nNote that there are some differences from the one of Emacs, especially: there\r\nis no activation and ADVICE supports \"usual\" commands only (see\r\n|advice-Normal-command|).  Because Ex commands and functions cannot be\r\nsupported only by Vim script.\r\n\r\nRequirements:\r\n- Vim 7.2 or later\r\n\r\nLatest version:\r\nhttp:\/\/github.com\/kana\/vim-advice","4":"*advice* is a library for Vim scripts to provide a modular way to alter the\r\nbehavior of a command.\r\n\r\nFor example, if you want to change the default register for the command |C| to\r\n\"_ (|quote_|), you have to write a new operator then map |C| to execute the\r\noperator, i.e., redefine the whole command.  But how about if you also want to\r\nchange |C| in Visual mode to always behave as same as the default |C| in\r\n|blockwise-visual| mode?  How about if you want to disable one of the altered\r\nbehaviors afterwards?  Therefore, redefining the whole command is not elegant\r\nway.\r\n\r\nADVICE provides useful API to do such customization.\r\n\r\nThe concept of ADVICE is derived from the one of Emacs.  See also:\r\nhttp:\/\/www.gnu.org\/software\/emacs\/elisp\/html_node\/Advising-Functions.html .\r\nNote that there are some differences from the one of Emacs, especially: there\r\nis no activation and ADVICE supports \"usual\" commands only (see\r\n|advice-Normal-command|).  Because Ex commands and functions cannot be\r\nsupported only by Vim script.\r\n\r\nRequirements:\r\n- Vim 7.2 or later\r\n\r\nLatest version:\r\nhttp:\/\/github.com\/kana\/vim-advice","install_details":"...","5":"...","first_name":"Kana","6":"Kana","last_name":"Natsuno","7":"Natsuno","releases":[{"0":"2402","vim_version":"7.0","1":"7.0","script_version":"0.0.0","2":"0.0.0","version_comment":"Initial upload","3":"Initial upload","package":"vim-advice-0.0.0.zip","4":"vim-advice-0.0.0.zip","src_id":"9344","5":"9344","creation_date":"1223885870","6":"1223885870"}]},"2401":{"script_id":"2401","0":"2401","script_name":"Russian PLansliterated","1":"Russian PLansliterated","script_type":"utility","2":"utility","summary":"Transliterated Russian without breaking normal-mode","3":"Transliterated Russian without breaking normal-mode","description":"Check out translit.vim (vimscript #2469), which should be considered as a successor of this plugin.\r\n\r\n-------------------------------\r\n\r\nThis plug-in allows you to write transliterated Russian (Cyrillic alphabet)\r\nin insert and replace mode. Other modes are unaffected and just work (which\r\nmakes it superior to relying on GTK's input methods).\r\n                                                                                      \r\nTransliteration is heavily biased towards Polish orthography and phonetics,\r\neg. \"ч\" is spelled as \"cz\" (not \"ch\"), \"Я\" is \"Ja\", not 'Ya', etc. This is\r\nwhy it's called PLansliterated :) It's quite trivial to turn this plug-in\r\ninto english transliteration, CZransliteration, FRansliteration, etc. If\r\nyou do so for your 'source' language of choice, feel free to post your work\r\non vim.org or just drop me a line.\r\n                                                                                      \r\nUsage:\r\nTurn transliteration on and off by :RussianOn, :RussianOff or :ToggleRussian\r\ncommands. You can also use CTRL+q (both in insert and normal mode) for\r\ntoggling.\r\n                                                                                      \r\nMost of characters should be quite intuitive (at least if you're Polish).\r\nI decided to make both \"e\" and \"je\" represent Cyrillic \"е\".\r\nUse \"e'\" to get 'э'. \"'\" stands for \"ь\" and \"`\" is for \"ъ\". Prefix with\r\ntilde to get uppercase variants of твердый and мягкий знак, eg. \"~`\" for \"Ъ\".\r\n\r\nIf you need several Latin letters for one uppercase Cyrillic, you can use\r\nboth all-uppercase, or only the first one capitalised, like \"SZCZ\" or \"Szcz\" for \"Щ\".\r\n                                                                                      \r\nSet g:cursor_follows_alphabet to make cursor color change when alphabet is\r\nswitched.\r\n                                                                                      \r\nUse the source when in doubt.\r\n                                                                                      \r\nBlablabla:\r\nHave fun using this plug-in!\r\nComments are welcome.","4":"Check out translit.vim (vimscript #2469), which should be considered as a successor of this plugin.\r\n\r\n-------------------------------\r\n\r\nThis plug-in allows you to write transliterated Russian (Cyrillic alphabet)\r\nin insert and replace mode. Other modes are unaffected and just work (which\r\nmakes it superior to relying on GTK's input methods).\r\n                                                                                      \r\nTransliteration is heavily biased towards Polish orthography and phonetics,\r\neg. \"ч\" is spelled as \"cz\" (not \"ch\"), \"Я\" is \"Ja\", not 'Ya', etc. This is\r\nwhy it's called PLansliterated :) It's quite trivial to turn this plug-in\r\ninto english transliteration, CZransliteration, FRansliteration, etc. If\r\nyou do so for your 'source' language of choice, feel free to post your work\r\non vim.org or just drop me a line.\r\n                                                                                      \r\nUsage:\r\nTurn transliteration on and off by :RussianOn, :RussianOff or :ToggleRussian\r\ncommands. You can also use CTRL+q (both in insert and normal mode) for\r\ntoggling.\r\n                                                                                      \r\nMost of characters should be quite intuitive (at least if you're Polish).\r\nI decided to make both \"e\" and \"je\" represent Cyrillic \"е\".\r\nUse \"e'\" to get 'э'. \"'\" stands for \"ь\" and \"`\" is for \"ъ\". Prefix with\r\ntilde to get uppercase variants of твердый and мягкий знак, eg. \"~`\" for \"Ъ\".\r\n\r\nIf you need several Latin letters for one uppercase Cyrillic, you can use\r\nboth all-uppercase, or only the first one capitalised, like \"SZCZ\" or \"Szcz\" for \"Щ\".\r\n                                                                                      \r\nSet g:cursor_follows_alphabet to make cursor color change when alphabet is\r\nswitched.\r\n                                                                                      \r\nUse the source when in doubt.\r\n                                                                                      \r\nBlablabla:\r\nHave fun using this plug-in!\r\nComments are welcome.","install_details":"Put it into ~\/.vim\/plugin","5":"Put it into ~\/.vim\/plugin","first_name":"Krzysiek","6":"Krzysiek","last_name":"Goj","7":"Goj","releases":[{"0":"2401","vim_version":"7.2","1":"7.2","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"russian_plansliterated.vim","4":"russian_plansliterated.vim","src_id":"9338","5":"9338","creation_date":"1223819541","6":"1223819541"}]},"2400":{"script_id":"2400","0":"2400","script_name":"sql\/plsql","1":"sql\/plsql","script_type":"color scheme","2":"color scheme","summary":"Good for sql and pl\/sql coding","3":"Good for sql and pl\/sql coding","description":"I have been using this vimrc file  for  coding sql\/plsql ","4":"I have been using this vimrc file  for  coding sql\/plsql ","install_details":"replace the _vimrc file","5":"replace the _vimrc file","first_name":"somesh","6":"somesh","last_name":"m","7":"m","releases":[{"0":"2400","vim_version":"6.0","1":"6.0","script_version":"6","2":"6","version_comment":"Initial upload","3":"Initial upload","package":"_vimrc","4":"_vimrc","src_id":"9337","5":"9337","creation_date":"1223801833","6":"1223801833"}]},"2399":{"script_id":"2399","0":"2399","script_name":"cheat","1":"cheat","script_type":"syntax","2":"syntax","summary":"Yac (Yet Another Cheat)","3":"Yac (Yet Another Cheat)","description":"== What's Yac\r\n Yet Another Cheet (Powered By Ruby)\r\n== What's the script\r\n the Syntax Highlight\r\n== How To Use The Yac\r\n\r\n=== To initialize repositories:\r\n    $ yac init\r\n=== To get a cheat sheet:\r\n    $ yac [cheatsheet]\r\n=== To edit a cheat sheet\r\n    $ yac edit [cheatsheet]\r\n=== To add a cheat sheet\r\n    $ yac add [cheatsheet]\r\n=== To rm a cheat sheet\r\n    $ yac rm [cheatsheet]\r\n=== Search according the sheets name\r\n    $ yac name [keyword]\r\n=== Search according the sheets content\r\n    $ yac content [keyword]\r\n=== Update repositories\r\n    $ yac update main  => Update main repository\r\n    $ yac update private => Update private repository\r\n    $ yac update => Update All\r\n=== Help\r\n    $ yac help\r\n=== Shell\r\n    $ yac shell main => Open the main repository's shell\r\n    $ yac shell => Open the private repository's shell\r\n=== Documents format\r\n   Use .ch as the suffix ,At the beginning of the row,plus N = for the N-class title\r\n   Use '#' at the beginning of a row to comment the line,You can use '\\#' to get '#'\r\n   Use three @ wrap some words to highlight it,for example: @@\\@ HI @@\\@ (remove the \\) will highlight HI\r\n=== Set the color of highlight\r\n   Default use .yacrc under home directory to set,, details, see the example file under the resources directory\r\n=== Others\r\n   Add @ before [cheatsheet]\/[keyword] will only search the main depot\r\n   See also the source code to get more sexy ways\r\n\r\n== Author: Jinzhu Zhang : http:\/\/www.zhangjinzhu.com \/  wosmvp (no-spam) gmail (no-spam) com\r\n\r\n","4":"== What's Yac\r\n Yet Another Cheet (Powered By Ruby)\r\n== What's the script\r\n the Syntax Highlight\r\n== How To Use The Yac\r\n\r\n=== To initialize repositories:\r\n    $ yac init\r\n=== To get a cheat sheet:\r\n    $ yac [cheatsheet]\r\n=== To edit a cheat sheet\r\n    $ yac edit [cheatsheet]\r\n=== To add a cheat sheet\r\n    $ yac add [cheatsheet]\r\n=== To rm a cheat sheet\r\n    $ yac rm [cheatsheet]\r\n=== Search according the sheets name\r\n    $ yac name [keyword]\r\n=== Search according the sheets content\r\n    $ yac content [keyword]\r\n=== Update repositories\r\n    $ yac update main  => Update main repository\r\n    $ yac update private => Update private repository\r\n    $ yac update => Update All\r\n=== Help\r\n    $ yac help\r\n=== Shell\r\n    $ yac shell main => Open the main repository's shell\r\n    $ yac shell => Open the private repository's shell\r\n=== Documents format\r\n   Use .ch as the suffix ,At the beginning of the row,plus N = for the N-class title\r\n   Use '#' at the beginning of a row to comment the line,You can use '\\#' to get '#'\r\n   Use three @ wrap some words to highlight it,for example: @@\\@ HI @@\\@ (remove the \\) will highlight HI\r\n=== Set the color of highlight\r\n   Default use .yacrc under home directory to set,, details, see the example file under the resources directory\r\n=== Others\r\n   Add @ before [cheatsheet]\/[keyword] will only search the main depot\r\n   See also the source code to get more sexy ways\r\n\r\n== Author: Jinzhu Zhang : http:\/\/www.zhangjinzhu.com \/  wosmvp (no-spam) gmail (no-spam) com\r\n\r\n","install_details":"drop it to syntax directory\r\n\r\nadd below to vimrc\r\n\r\naugroup filetypedetect\r\nau! BufNewFile,BufRead *.ch setf cheat\r\naugroup END\r\n","5":"drop it to syntax directory\r\n\r\nadd below to vimrc\r\n\r\naugroup filetypedetect\r\nau! BufNewFile,BufRead *.ch setf cheat\r\naugroup END\r\n","first_name":"Jinzhu","6":"Jinzhu","last_name":"Zhang","7":"Zhang","releases":[{"0":"2399","vim_version":"7.0","1":"7.0","script_version":"0.2","2":"0.2","version_comment":"Update for new version yac.","3":"Update for new version yac.","package":"cheat.vim","4":"cheat.vim","src_id":"9531","5":"9531","creation_date":"1227188442","6":"1227188442"},{"0":"2399","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"cheat.vim","4":"cheat.vim","src_id":"9332","5":"9332","creation_date":"1223699548","6":"1223699548"}]},"2398":{"script_id":"2398","0":"2398","script_name":"hfile","1":"hfile","script_type":"utility","2":"utility","summary":"Boilerplate code for .h files","3":"Boilerplate code for .h files","description":"It includes the boiler plate #ifndef\/#define code into new .h files. ","4":"It includes the boiler plate #ifndef\/#define code into new .h files. ","install_details":"Just add the file to your plugin folder.","5":"Just add the file to your plugin folder.","first_name":"Victor","6":"Victor","last_name":"Bogado da Silva Lins","7":"Bogado da Silva Lins","releases":[{"0":"2398","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"hfile.vim","4":"hfile.vim","src_id":"9328","5":"9328","creation_date":"1223643873","6":"1223643873"}]},"2397":{"script_id":"2397","0":"2397","script_name":"Fly Between Projects","1":"Fly Between Projects","script_type":"utility","2":"utility","summary":"Quick Selection Between projects","3":"Quick Selection Between projects","description":"Quickly interchange between different projects,Modify file according to your need selfreqfiles.txt\r\n\r\nMenu selection Hl Word <> Def project dir <> Default file to be opend\r\n(Single space between fields\r\n\r\nPRJ1 c:\\PRJ1DIR1 DEFFILEPRJ1.C\r\nPRJ2 c:\\PRJ1DIR2 DEFFILEPRJ2.C","4":"Quickly interchange between different projects,Modify file according to your need selfreqfiles.txt\r\n\r\nMenu selection Hl Word <> Def project dir <> Default file to be opend\r\n(Single space between fields\r\n\r\nPRJ1 c:\\PRJ1DIR1 DEFFILEPRJ1.C\r\nPRJ2 c:\\PRJ1DIR2 DEFFILEPRJ2.C","install_details":"Drop them into plugin directory and press F1 or Sft-F1,","5":"Drop them into plugin directory and press F1 or Sft-F1,","first_name":"vijayandra","6":"vijayandra","last_name":"singh","7":"singh","releases":[{"0":"2397","vim_version":"6.0","1":"6.0","script_version":"1.02","2":"1.02","version_comment":"New Field been added, Press F1 for selecting project and F2 opens files present in current directory using wild char supplied in text file as shown following.\r\n\r\nF1 Select Project\r\nF2 Select files in sub project\r\n\r\nPRJ1 c:\\PRJ1DIR1 DEFFILEPRJ1.C *.C\r\nPRJ2 c:\\PRJ1DIR2 DEFFILEPRJ2.C *.CPP\r\n","3":"New Field been added, Press F1 for selecting project and F2 opens files present in current directory using wild char supplied in text file as shown following.\r\n\r\nF1 Select Project\r\nF2 Select files in sub project\r\n\r\nPRJ1 c:\\PRJ1DIR1 DEFFILEPRJ1.C *.C\r\nPRJ2 c:\\PRJ1DIR2 DEFFILEPRJ2.C *.CPP\r\n","package":"selfreqfiles.zip","4":"selfreqfiles.zip","src_id":"9330","5":"9330","creation_date":"1223687735","6":"1223687735"}]},"2396":{"script_id":"2396","0":"2396","script_name":"Cutting and pasting txt file in middle","1":"Cutting and pasting txt file in middle","script_type":"utility","2":"utility","summary":"Cut and Paste vertical","3":"Cut and Paste vertical","description":"Some times you want to cut text file from A colomn to B colomn for N number of rows, rather then making a awk\/sed secript try this script for vertical copy and paster,\r\n\r\n  Move curser where you want to perform rectangle copy press Ctrl-C and move again your curser to place where to you want to copy to buffer Press Ctrl-C again.\r\n\r\n  Now you take curser to line where you want to paste it vertically and press Ctrl-Y.","4":"Some times you want to cut text file from A colomn to B colomn for N number of rows, rather then making a awk\/sed secript try this script for vertical copy and paster,\r\n\r\n  Move curser where you want to perform rectangle copy press Ctrl-C and move again your curser to place where to you want to copy to buffer Press Ctrl-C again.\r\n\r\n  Now you take curser to line where you want to paste it vertically and press Ctrl-Y.","install_details":"Drop this file in your plugin directory","5":"Drop this file in your plugin directory","first_name":"vijayandra","6":"vijayandra","last_name":"singh","7":"singh","releases":[{"0":"2396","vim_version":"6.0","1":"6.0","script_version":"1.00","2":"1.00","version_comment":"Initial upload","3":"Initial upload","package":"v_cp_pst.vim","4":"v_cp_pst.vim","src_id":"9323","5":"9323","creation_date":"1223563623","6":"1223563623"}]},"2395":{"script_id":"2395","0":"2395","script_name":"Fly Between Projects","1":"Fly Between Projects","script_type":"utility","2":"utility","summary":"Quick Selection Between projects","3":"Quick Selection Between projects","description":"Unzip both files in plugin directory of VIM, modify \"selfreqfiles.txt\" to meet your need. PRJ1\/PRJ2 is menu selection will pop up when F1 or Sft-F1 pressed on key board, Default file name will be opened in respective directory upon selection so dont forget to modify it according to your need, \r\n(This is first version it does not like if there is more then one space between names)\r\n\r\nPRJ1 c:\\PRJ1DIR1 DEFFILEPRJ1.C\r\nPRJ2 c:\\PRJ1DIR2 DEFFILEPRJ2.C","4":"Unzip both files in plugin directory of VIM, modify \"selfreqfiles.txt\" to meet your need. PRJ1\/PRJ2 is menu selection will pop up when F1 or Sft-F1 pressed on key board, Default file name will be opened in respective directory upon selection so dont forget to modify it according to your need, \r\n(This is first version it does not like if there is more then one space between names)\r\n\r\nPRJ1 c:\\PRJ1DIR1 DEFFILEPRJ1.C\r\nPRJ2 c:\\PRJ1DIR2 DEFFILEPRJ2.C","install_details":"Unzip and drop them in plugin directory and modify \"selfreqfiles.txt\" according to your most active projects. It saves time when going between projects when working on multiple projects and dont have time to tweak hotkeys.","5":"Unzip and drop them in plugin directory and modify \"selfreqfiles.txt\" according to your most active projects. It saves time when going between projects when working on multiple projects and dont have time to tweak hotkeys.","first_name":"vijayandra","6":"vijayandra","last_name":"singh","7":"singh","releases":[{"0":"2395","vim_version":"6.0","1":"6.0","script_version":"1.00","2":"1.00","version_comment":"Initial upload","3":"Initial upload","package":"selfreqfiles.zip","4":"selfreqfiles.zip","src_id":"9322","5":"9322","creation_date":"1223563242","6":"1223563242"}]},"2394":{"script_id":"2394","0":"2394","script_name":"darkeclipse.vim","1":"darkeclipse.vim","script_type":"color scheme","2":"color scheme","summary":"A dark color scheme for the GUI","3":"A dark color scheme for the GUI","description":"A dark color scheme for the GUI.\r\nScreenshot at http:\/\/jstap.web.fc2.com\/darkeclipse.html","4":"A dark color scheme for the GUI.\r\nScreenshot at http:\/\/jstap.web.fc2.com\/darkeclipse.html","install_details":"Put it in one of your colors directories.\r\nThen, just do :colorscheme darkeclipse","5":"Put it in one of your colors directories.\r\nThen, just do :colorscheme darkeclipse","first_name":"Kojo","6":"Kojo","last_name":"Sugita","7":"Sugita","releases":[{"0":"2394","vim_version":"7.0","1":"7.0","script_version":"1.2","2":"1.2","version_comment":"Added \"CursorColumn\". ","3":"Added \"CursorColumn\". ","package":"darkeclipse.vim","4":"darkeclipse.vim","src_id":"10979","5":"10979","creation_date":"1247148539","6":"1247148539"},{"0":"2394","vim_version":"7.0","1":"7.0","script_version":"1.1","2":"1.1","version_comment":"Added \"CursorLine\"","3":"Added \"CursorLine\"","package":"darkeclipse.vim","4":"darkeclipse.vim","src_id":"9538","5":"9538","creation_date":"1227286627","6":"1227286627"},{"0":"2394","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"darkeclipse.vim","4":"darkeclipse.vim","src_id":"9320","5":"9320","creation_date":"1223477456","6":"1223477456"}]},"2393":{"script_id":"2393","0":"2393","script_name":"QuickTemplate","1":"QuickTemplate","script_type":"utility","2":"utility","summary":"create new files from existing templates on-the-fly","3":"create new files from existing templates on-the-fly","description":"create new files from existing templates on-the-fly","4":"create new files from existing templates on-the-fly","install_details":"download the source code, extract it to the directory. Reboot vim, input\r\n\r\n:NewTemplate xhtml\r\n\r\nto create XHTML template. there is another command for vim above 7.0:\r\n\r\n:NewTemplateTab xhtml\r\n\r\nby using this command you can create file in new tab. Of course, you can define key mapping to create\r\ncommon types of files, for instance,\r\n\r\nmap nn :NewTemplateTab xhtml<cr>\r\n\r\npress n twice under normal mode to create xhtml file in new tab.\r\n\r\nthe directory for this plugin is:\r\n\r\n$VIMRUNTIME\/plugin\/Template.vim\r\n\r\nand it has two default configure options\r\n\r\nlet g:TemplatePath=$VIM.'\/vimfiles\/template\/'\r\nlet g:TemplateCursorFlag='#cursor#'\r\n\r\nAmong the 2 options, g:TemplatePath is the path for the templates, whereas the g:TemplatePathCursorFlag is the position for the mouse cursor to be moved to when the new template is built( moving to the bottom of the file by default).\r\n\r\nAdding templates\r\n\r\nCreating new template is supported by the script. First, find the path for the xhtml.tpl in g:TemplatePath. Then read the following content,\r\n\r\n<html>\r\n...\r\n    <body>\r\n        #cursor#\r\n    <\/body>\r\n<\/html>\r\n\r\nit is easy to understand. If you are to build a python template, you can create python.tpl in g:TemplatePath and add the #cursor# in the appropriate position.\r\n\r\nPlease do not hesitate to throw your comments and suggestions here: http:\/\/www.gracecode.com\/Archive\/Display\/2414","5":"download the source code, extract it to the directory. Reboot vim, input\r\n\r\n:NewTemplate xhtml\r\n\r\nto create XHTML template. there is another command for vim above 7.0:\r\n\r\n:NewTemplateTab xhtml\r\n\r\nby using this command you can create file in new tab. Of course, you can define key mapping to create\r\ncommon types of files, for instance,\r\n\r\nmap nn :NewTemplateTab xhtml<cr>\r\n\r\npress n twice under normal mode to create xhtml file in new tab.\r\n\r\nthe directory for this plugin is:\r\n\r\n$VIMRUNTIME\/plugin\/Template.vim\r\n\r\nand it has two default configure options\r\n\r\nlet g:TemplatePath=$VIM.'\/vimfiles\/template\/'\r\nlet g:TemplateCursorFlag='#cursor#'\r\n\r\nAmong the 2 options, g:TemplatePath is the path for the templates, whereas the g:TemplatePathCursorFlag is the position for the mouse cursor to be moved to when the new template is built( moving to the bottom of the file by default).\r\n\r\nAdding templates\r\n\r\nCreating new template is supported by the script. First, find the path for the xhtml.tpl in g:TemplatePath. Then read the following content,\r\n\r\n<html>\r\n...\r\n    <body>\r\n        #cursor#\r\n    <\/body>\r\n<\/html>\r\n\r\nit is easy to understand. If you are to build a python template, you can create python.tpl in g:TemplatePath and add the #cursor# in the appropriate position.\r\n\r\nPlease do not hesitate to throw your comments and suggestions here: http:\/\/www.gracecode.com\/Archive\/Display\/2414","first_name":"ming","6":"ming","last_name":"cheng","7":"cheng","releases":[{"0":"2393","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"_vim_Template_20081008.7z","4":"_vim_Template_20081008.7z","src_id":"9319","5":"9319","creation_date":"1223466658","6":"1223466658"}]},"2392":{"script_id":"2392","0":"2392","script_name":"Django Projects","1":"Django Projects","script_type":"utility","2":"utility","summary":"Allows you to use django management commands from within vim","3":"Allows you to use django management commands from within vim","description":"Author: Gregor M\u00c3\u00bcllegger <gregor@muellegger.de>\r\nVersion: 0.1.0\r\n\r\nDescription:\r\n  Use the script to run simple django specific tasks. You can run management\r\n  commands from in vim.\r\n\r\nUsage:\r\n  When you have specified all your django projects you can now tell the script\r\n  that you want now to work with one of them. Let's expect you want to work\r\n  with your 'fancyblog' project.\r\n  \r\n  At first you have to initalize this project:\r\n    :DjangoInit fancyblog\r\n\r\n  Now you can use all the cool commands to work with your project. Use\r\n  `:DjangoManage <command>` to execute a command with your manage.py file.\r\n\r\n    :DjangoManage syncdb\r\n\r\n  Use the `:DjangoTerminalManage <command>` command to execute a manage.py\r\n  command in an external terminal to free the vim command line for new\r\n  commands. This can be used to run django's development server from within\r\n  vim.\r\n\r\nConfiguration:\r\n  There are a few global variables you can change to fit the script your\r\n  preferences:\r\n\r\n  g:django_terminal_program\r\n    Set this variable to a terminal programm which shall execute the commands\r\n    in :DjangoTerminalManage. Default is 'xterm -e'.\r\n\r\nShortcuts:\r\n  There are already shortcuts for every builtin command to prevent you from\r\n  performing too many keystrokes:\r\n\r\n    :DjangoAdminindex\r\n    :DjangoCleanup\r\n    :DjangoCompileMessages\r\n    :DjangoCreateCachetable\r\n    :DjangoCreateSuperuser\r\n    :DjangoDBShell\r\n    :DjangoDiffsettings\r\n    :DjangoDumpdata\r\n    :DjangoFlush\r\n    :DjangoHelp command\r\n    :DjangoInspectDB\r\n    :DjangoLoaddata\r\n    :DjangoMakeMessages\r\n    :DjangoReset appname\r\n    :DjangoRunfcgi\r\n    :DjangoRunserver\r\n    :DjangoShell\r\n    :DjangoSql\r\n    :DjangoSqlall\r\n    :DjangoSqlclear\r\n    :DjangoSqlcustom\r\n    :DjangoSqlflush\r\n    :DjangoSqlindexes\r\n    :DjangoSqlinitialdata\r\n    :DjangoSqlreset\r\n    :DjangoSqlsequencereset\r\n    :DjangoStartapp newappname\r\n    :DjangoSyncdb\r\n    :DjangoTest [appnames]\r\n    :DjangoTestserver\r\n    :DjangoValidate\r\n\r\n  You can also use the commands from the django-commands-extension app if you\r\n  have installed it.\r\n\r\n    :DjangoCreateapp\r\n    :DjangoCreatecommand\r\n    :DjangoCreatejobs\r\n    :DjangoDescribeform\r\n    :DjangoDumpscript\r\n    :DjangoExportemails\r\n    :DjangoGenerateSecretKey\r\n    :DjangoGraphmodels\r\n    :DjangoPasswd\r\n    :DjangoPrintUserForSession\r\n    :DjangoResetDB\r\n    :DjangoRunjob\r\n    :DjangoRunjobs\r\n    :DjangoRunprofile\r\n    :DjangoRunscript\r\n    :DjangoRunserverPlus\r\n    :DjangoSetfakepasswords\r\n    :DjangoShellPlus\r\n    :DjangoShowurls\r\n    :DjangoSqldiff","4":"Author: Gregor M\u00c3\u00bcllegger <gregor@muellegger.de>\r\nVersion: 0.1.0\r\n\r\nDescription:\r\n  Use the script to run simple django specific tasks. You can run management\r\n  commands from in vim.\r\n\r\nUsage:\r\n  When you have specified all your django projects you can now tell the script\r\n  that you want now to work with one of them. Let's expect you want to work\r\n  with your 'fancyblog' project.\r\n  \r\n  At first you have to initalize this project:\r\n    :DjangoInit fancyblog\r\n\r\n  Now you can use all the cool commands to work with your project. Use\r\n  `:DjangoManage <command>` to execute a command with your manage.py file.\r\n\r\n    :DjangoManage syncdb\r\n\r\n  Use the `:DjangoTerminalManage <command>` command to execute a manage.py\r\n  command in an external terminal to free the vim command line for new\r\n  commands. This can be used to run django's development server from within\r\n  vim.\r\n\r\nConfiguration:\r\n  There are a few global variables you can change to fit the script your\r\n  preferences:\r\n\r\n  g:django_terminal_program\r\n    Set this variable to a terminal programm which shall execute the commands\r\n    in :DjangoTerminalManage. Default is 'xterm -e'.\r\n\r\nShortcuts:\r\n  There are already shortcuts for every builtin command to prevent you from\r\n  performing too many keystrokes:\r\n\r\n    :DjangoAdminindex\r\n    :DjangoCleanup\r\n    :DjangoCompileMessages\r\n    :DjangoCreateCachetable\r\n    :DjangoCreateSuperuser\r\n    :DjangoDBShell\r\n    :DjangoDiffsettings\r\n    :DjangoDumpdata\r\n    :DjangoFlush\r\n    :DjangoHelp command\r\n    :DjangoInspectDB\r\n    :DjangoLoaddata\r\n    :DjangoMakeMessages\r\n    :DjangoReset appname\r\n    :DjangoRunfcgi\r\n    :DjangoRunserver\r\n    :DjangoShell\r\n    :DjangoSql\r\n    :DjangoSqlall\r\n    :DjangoSqlclear\r\n    :DjangoSqlcustom\r\n    :DjangoSqlflush\r\n    :DjangoSqlindexes\r\n    :DjangoSqlinitialdata\r\n    :DjangoSqlreset\r\n    :DjangoSqlsequencereset\r\n    :DjangoStartapp newappname\r\n    :DjangoSyncdb\r\n    :DjangoTest [appnames]\r\n    :DjangoTestserver\r\n    :DjangoValidate\r\n\r\n  You can also use the commands from the django-commands-extension app if you\r\n  have installed it.\r\n\r\n    :DjangoCreateapp\r\n    :DjangoCreatecommand\r\n    :DjangoCreatejobs\r\n    :DjangoDescribeform\r\n    :DjangoDumpscript\r\n    :DjangoExportemails\r\n    :DjangoGenerateSecretKey\r\n    :DjangoGraphmodels\r\n    :DjangoPasswd\r\n    :DjangoPrintUserForSession\r\n    :DjangoResetDB\r\n    :DjangoRunjob\r\n    :DjangoRunjobs\r\n    :DjangoRunprofile\r\n    :DjangoRunscript\r\n    :DjangoRunserverPlus\r\n    :DjangoSetfakepasswords\r\n    :DjangoShellPlus\r\n    :DjangoShowurls\r\n    :DjangoSqldiff","install_details":"Requirements:\r\n  The script will only work on a unix-like system.\r\n\r\nInstallation:\r\n  Put this file (django_projects.vim) in your plugin directory and tell the\r\n  script what django projects you are working on.\r\n  \r\n  To install a single django project use the g:DjangoInstall() function. Put a\r\n  lines similar to the following in your vimrc file:\r\n\r\n    call g:DjangoInstall('myproject', '\/home\/username\/projects\/myproject\/', 'settings', 'manage.py', ['\/usr\/local\/pythonlibs', 'apps\/'], '.')\r\n\r\n  The arguments mean the following things:\r\n    1. argument (name): This is the projects name. It is used with the DjangoInit\r\n    command to tell the script on which project you work on.\r\n\r\n    2. argument (project root): This should be an absolute path to your \r\n    project. It is used to complete relative paths in the `manage_file`,\r\n    `paths` and `cd` argument. This argument must end with a slash.\r\n\r\n    3. argument (settings module): Specify here the name of your settings\r\n    module. This value is used to set the $DJANGO_SETTINGS_MODULE variable.\r\n\r\n    4. argument (manage.py file): Specify here the path of your manage.py\r\n    file. The project root path is prepended to this argument if a relative\r\n    path is given (e.g. the argument does not start with '\/')\r\n\r\n    5. argument (python paths): This argument must be a list of strings. The\r\n    script will add these paths to your sys.path variable. If a path is\r\n    relative, the project root argument will be prepended.\r\n\r\n    6. argument (cd): Specify a directory in which the script will jump while\r\n    calling g:DjangoInit('myproject'). If not specified (e.g. it is an empty\r\n    string) no cd is performed.\r\n\r\n  Note: Maybe you need to include the source of this file into your .vimrc\r\n  (if the plugin is loaded after your g:DjangoInstall() calls). The simplest\r\n  way to do this is to put this line right before your g:DjangoInstall\r\n  calls:\r\n\r\n    source ~\/.vim\/plugin\/django_projects.vim","5":"Requirements:\r\n  The script will only work on a unix-like system.\r\n\r\nInstallation:\r\n  Put this file (django_projects.vim) in your plugin directory and tell the\r\n  script what django projects you are working on.\r\n  \r\n  To install a single django project use the g:DjangoInstall() function. Put a\r\n  lines similar to the following in your vimrc file:\r\n\r\n    call g:DjangoInstall('myproject', '\/home\/username\/projects\/myproject\/', 'settings', 'manage.py', ['\/usr\/local\/pythonlibs', 'apps\/'], '.')\r\n\r\n  The arguments mean the following things:\r\n    1. argument (name): This is the projects name. It is used with the DjangoInit\r\n    command to tell the script on which project you work on.\r\n\r\n    2. argument (project root): This should be an absolute path to your \r\n    project. It is used to complete relative paths in the `manage_file`,\r\n    `paths` and `cd` argument. This argument must end with a slash.\r\n\r\n    3. argument (settings module): Specify here the name of your settings\r\n    module. This value is used to set the $DJANGO_SETTINGS_MODULE variable.\r\n\r\n    4. argument (manage.py file): Specify here the path of your manage.py\r\n    file. The project root path is prepended to this argument if a relative\r\n    path is given (e.g. the argument does not start with '\/')\r\n\r\n    5. argument (python paths): This argument must be a list of strings. The\r\n    script will add these paths to your sys.path variable. If a path is\r\n    relative, the project root argument will be prepended.\r\n\r\n    6. argument (cd): Specify a directory in which the script will jump while\r\n    calling g:DjangoInit('myproject'). If not specified (e.g. it is an empty\r\n    string) no cd is performed.\r\n\r\n  Note: Maybe you need to include the source of this file into your .vimrc\r\n  (if the plugin is loaded after your g:DjangoInstall() calls). The simplest\r\n  way to do this is to put this line right before your g:DjangoInstall\r\n  calls:\r\n\r\n    source ~\/.vim\/plugin\/django_projects.vim","first_name":"Gregor","6":"Gregor","last_name":"M\u00c3\u00bcllegger","7":"M\u00c3\u00bcllegger","releases":[{"0":"2392","vim_version":"6.0","1":"6.0","script_version":"0.1.0","2":"0.1.0","version_comment":"Initial upload","3":"Initial upload","package":"django_projects.vim","4":"django_projects.vim","src_id":"9318","5":"9318","creation_date":"1223373333","6":"1223373333"}]},"2391":{"script_id":"2391","0":"2391","script_name":"MPC syntax","1":"MPC syntax","script_type":"syntax","2":"syntax","summary":"Syntax Highlight for MakeProjectCreator files","3":"Syntax Highlight for MakeProjectCreator files","description":"Syntax Highlight for Makefile, Project, and Workspace Creator (http:\/\/www.ociweb.com\/products\/mpc).\r\n","4":"Syntax Highlight for Makefile, Project, and Workspace Creator (http:\/\/www.ociweb.com\/products\/mpc).\r\n","install_details":"Put it into syntax directory (e.g. ~\/.vim\/syntax) and add mpc filetype \r\n\r\nau BufNewFile,BufRead *.m\\(wb\\|wc\\|pb\\|pc\\) setf mpc\r\n\r\nin your filetype.vim or ~\/.vimrc","5":"Put it into syntax directory (e.g. ~\/.vim\/syntax) and add mpc filetype \r\n\r\nau BufNewFile,BufRead *.m\\(wb\\|wc\\|pb\\|pc\\) setf mpc\r\n\r\nin your filetype.vim or ~\/.vimrc","first_name":"Like","6":"Like","last_name":"Ma","7":"Ma","releases":[{"0":"2391","vim_version":"7.0","1":"7.0","script_version":"0.1.5","2":"0.1.5","version_comment":"Add some keywords according to the new version of MPC","3":"Add some keywords according to the new version of MPC","package":"mpc.vim","4":"mpc.vim","src_id":"24308","5":"24308","creation_date":"1465235106","6":"1465235106"},{"0":"2391","vim_version":"7.0","1":"7.0","script_version":"0.1.4","2":"0.1.4","version_comment":"Update mpc keyword according to http:\/\/downloads.ociweb.com\/MPC\/docs\/html\/MakeProjectCreator.html","3":"Update mpc keyword according to http:\/\/downloads.ociweb.com\/MPC\/docs\/html\/MakeProjectCreator.html","package":"mpc.vim","4":"mpc.vim","src_id":"17110","5":"17110","creation_date":"1324655858","6":"1324655858"},{"0":"2391","vim_version":"7.0","1":"7.0","script_version":"0.1.3","2":"0.1.3","version_comment":"Update mpc structure and keyword according to http:\/\/downloads.ociweb.com\/MPC\/docs\/html\/MakeProjectCreator.html","3":"Update mpc structure and keyword according to http:\/\/downloads.ociweb.com\/MPC\/docs\/html\/MakeProjectCreator.html","package":"mpc.vim","4":"mpc.vim","src_id":"14632","5":"14632","creation_date":"1293467131","6":"1293467131"},{"0":"2391","vim_version":"7.0","1":"7.0","script_version":"0.1.2","2":"0.1.2","version_comment":"Fix loading failed on Vim 7.1 Kubuntu 7.04 by converting this script file format from dos to unix.","3":"Fix loading failed on Vim 7.1 Kubuntu 7.04 by converting this script file format from dos to unix.","package":"mpc.vim","4":"mpc.vim","src_id":"9336","5":"9336","creation_date":"1223796078","6":"1223796078"},{"0":"2391","vim_version":"7.0","1":"7.0","script_version":"0.1.1","2":"0.1.1","version_comment":"Initial upload","3":"Initial upload","package":"mpc.vim","4":"mpc.vim","src_id":"9312","5":"9312","creation_date":"1223209934","6":"1223209934"}]},"2390":{"script_id":"2390","0":"2390","script_name":"CSApprox","1":"CSApprox","script_type":"utility","2":"utility","summary":"Make gvim-only colorschemes work transparently in terminal vim","3":"Make gvim-only colorschemes work transparently in terminal vim","description":"CSApprox.vim\r\n\r\n============\r\nDESCRIPTION\r\n============\r\n\r\nIt's hard to find colorschemes for terminal Vim.  Most colorschemes are\r\nwritten to only support GVim, and don't work at all in terminal Vim.\r\n\r\nThis plugin makes GVim-only colorschemes Just Work in terminal Vim, as long\r\nas the terminal supports 88 or 256 colors - and most do these days.  This\r\nusually requires no user interaction (but see the help for what to do if\r\nthings don't Just Work).  After getting this plugin happily installed, any\r\ntime you use :colorscheme it will do its magic and make the colorscheme Just\r\nWork.\r\n\r\nWhenever you change colorschemes using the :colorscheme command this script\r\nwill be executed.  It will take the colors that the scheme specified for use\r\nin the GUI and use an approximation algorithm to try to gracefully degrade\r\nthem to the closest color available in your terminal.  If you are running in\r\na GUI or if your terminal doesn't support 88 or 256 colors, no changes are\r\nmade.  Also, no changes will be made if the colorscheme seems to have been\r\nhigh color already.\r\n\r\nIf for some reason this transparent method isn't suitable to you (for instance\r\nif your environment can't be configured to meet the |csapprox-requirements|,\r\nor you need to work in Vim 6), another option is also available: using the\r\n|:CSApproxSnapshot| command to create a new GUI\/88-\/256-color terminal\r\ncolorscheme.  To use this command, a user would generally start GVim, choose a\r\ncolorscheme that sets up the desired colors, and then use |:CSApproxSnapshot|\r\nto create a new colorscheme based on those colors that works in high color\r\nterminals.  This method is more flexible than the transparent mode and works\r\nin more places, but also requires more user intervention, and makes it harder\r\nto deal with colorschemes being updated and such.\r\n\r\n======\r\nNOTES\r\n======\r\n\r\nIdeally, this plugin should require absolutely no configuration, but you may\r\nneed some tweaking to make sure vim realizes that your terminal supports more\r\nthan 16 colors.  Also, konsole and Eterm users will want to make sure that\r\nthis plugin realizes that the terminal does not use colors that are exactly\r\nxterm-compatible; they will want to skim through the help articles\r\n|csapprox-palettes| and |csapprox-configuration| for a better end result.\r\n\r\n==============\r\nSCREENSHOTS\r\n==============\r\n\r\nSome quick side-by-side screenshots can be found at\r\nhttp:\/\/www.cs.drexel.edu\/~mjw452\/CSApprox\/","4":"CSApprox.vim\r\n\r\n============\r\nDESCRIPTION\r\n============\r\n\r\nIt's hard to find colorschemes for terminal Vim.  Most colorschemes are\r\nwritten to only support GVim, and don't work at all in terminal Vim.\r\n\r\nThis plugin makes GVim-only colorschemes Just Work in terminal Vim, as long\r\nas the terminal supports 88 or 256 colors - and most do these days.  This\r\nusually requires no user interaction (but see the help for what to do if\r\nthings don't Just Work).  After getting this plugin happily installed, any\r\ntime you use :colorscheme it will do its magic and make the colorscheme Just\r\nWork.\r\n\r\nWhenever you change colorschemes using the :colorscheme command this script\r\nwill be executed.  It will take the colors that the scheme specified for use\r\nin the GUI and use an approximation algorithm to try to gracefully degrade\r\nthem to the closest color available in your terminal.  If you are running in\r\na GUI or if your terminal doesn't support 88 or 256 colors, no changes are\r\nmade.  Also, no changes will be made if the colorscheme seems to have been\r\nhigh color already.\r\n\r\nIf for some reason this transparent method isn't suitable to you (for instance\r\nif your environment can't be configured to meet the |csapprox-requirements|,\r\nor you need to work in Vim 6), another option is also available: using the\r\n|:CSApproxSnapshot| command to create a new GUI\/88-\/256-color terminal\r\ncolorscheme.  To use this command, a user would generally start GVim, choose a\r\ncolorscheme that sets up the desired colors, and then use |:CSApproxSnapshot|\r\nto create a new colorscheme based on those colors that works in high color\r\nterminals.  This method is more flexible than the transparent mode and works\r\nin more places, but also requires more user intervention, and makes it harder\r\nto deal with colorschemes being updated and such.\r\n\r\n======\r\nNOTES\r\n======\r\n\r\nIdeally, this plugin should require absolutely no configuration, but you may\r\nneed some tweaking to make sure vim realizes that your terminal supports more\r\nthan 16 colors.  Also, konsole and Eterm users will want to make sure that\r\nthis plugin realizes that the terminal does not use colors that are exactly\r\nxterm-compatible; they will want to skim through the help articles\r\n|csapprox-palettes| and |csapprox-configuration| for a better end result.\r\n\r\n==============\r\nSCREENSHOTS\r\n==============\r\n\r\nSome quick side-by-side screenshots can be found at\r\nhttp:\/\/www.cs.drexel.edu\/~mjw452\/CSApprox\/","install_details":"Install like most other vim scripts:\r\nmkdir ~\/.vim\r\ncd ~\/.vim\r\nunzip \/path\/to\/CSApprox.zip\r\nvim -c 'helptags ~\/.vim\/doc'","5":"Install like most other vim scripts:\r\nmkdir ~\/.vim\r\ncd ~\/.vim\r\nunzip \/path\/to\/CSApprox.zip\r\nvim -c 'helptags ~\/.vim\/doc'","first_name":"Matt","6":"Matt","last_name":"Wozniski","7":"Wozniski","releases":[{"0":"2390","vim_version":"7.0","1":"7.0","script_version":"4.00","2":"4.00","version_comment":"Fix CSApprox to not fail in vim 7.3 if not +gui, now that vim behaves properly even without +gui\r\n\r\nProvide the :CSApprox command to re-run CSApprox's approximation algorithm even if the colorscheme hasn't changed - useful for when the user has tweaked some colors manually.\r\n\r\nBetter handling for the inverse (aka reverse) attribute for terminals that actually support it - and add the g:CSApprox_fake_reverse config variable to allow switching back to the old behavior for terminals that don't support real reverse video.\r\n\r\nFix an issue where CSApprox would unconditionally leave 'background' set to \"light\" - now it will leave 'background' unchanged when it runs.\r\n\r\nChange the handling for Konsole to use the xterm palette by for KDE versions >= 2.2.0 - Konsole itself was changed to drop its old, slightly incompatible palette in KDE 2.2.0\r\n\r\nFix a minor issue where running vim in recovery mode with -r would result in a complaint from CSApprox that the terminal didn't have enough colors even when it did.\r\n\r\nFix an issue where, even if CSApprox had been disabled by setting g:CSApprox_loaded, a CSApprox error message could still be displayed.","3":"Fix CSApprox to not fail in vim 7.3 if not +gui, now that vim behaves properly even without +gui\r\n\r\nProvide the :CSApprox command to re-run CSApprox's approximation algorithm even if the colorscheme hasn't changed - useful for when the user has tweaked some colors manually.\r\n\r\nBetter handling for the inverse (aka reverse) attribute for terminals that actually support it - and add the g:CSApprox_fake_reverse config variable to allow switching back to the old behavior for terminals that don't support real reverse video.\r\n\r\nFix an issue where CSApprox would unconditionally leave 'background' set to \"light\" - now it will leave 'background' unchanged when it runs.\r\n\r\nChange the handling for Konsole to use the xterm palette by for KDE versions >= 2.2.0 - Konsole itself was changed to drop its old, slightly incompatible palette in KDE 2.2.0\r\n\r\nFix a minor issue where running vim in recovery mode with -r would result in a complaint from CSApprox that the terminal didn't have enough colors even when it did.\r\n\r\nFix an issue where, even if CSApprox had been disabled by setting g:CSApprox_loaded, a CSApprox error message could still be displayed.","package":"CSApprox.zip","4":"CSApprox.zip","src_id":"18594","5":"18594","creation_date":"1347605634","6":"1347605634"},{"0":"2390","vim_version":"7.0","1":"7.0","script_version":"3.50","2":"3.50","version_comment":"Fix a major regression that prevented the Eterm and Konsole colors from being correctly snapshotted\r\n\r\nFix a related bug causing incorrect terminal colors after calling :CSApproxSnapshot\r\n\r\nFix a bug causing black to be used instead of dark grey\r\n\r\nHave snapshots calculate g:colors_name programmatically\r\n\r\nIntroduce many tweaks for better speed\r\n\r\nClarify some things at :help csapprox-terminal-example\r\n\r\nDefault to using our own list of rgb.txt colors rather than searching, for performance.  Add a new variable, g:CSApprox_use_showrgb, which forces us to try finding the colors using the \"showrgb\" program instead, and fall back on our own list if it isn't available\r\n\r\nRemove g:CSApprox_extra_rgb_txt_dirs - not needed in light of the above change","3":"Fix a major regression that prevented the Eterm and Konsole colors from being correctly snapshotted\r\n\r\nFix a related bug causing incorrect terminal colors after calling :CSApproxSnapshot\r\n\r\nFix a bug causing black to be used instead of dark grey\r\n\r\nHave snapshots calculate g:colors_name programmatically\r\n\r\nIntroduce many tweaks for better speed\r\n\r\nClarify some things at :help csapprox-terminal-example\r\n\r\nDefault to using our own list of rgb.txt colors rather than searching, for performance.  Add a new variable, g:CSApprox_use_showrgb, which forces us to try finding the colors using the \"showrgb\" program instead, and fall back on our own list if it isn't available\r\n\r\nRemove g:CSApprox_extra_rgb_txt_dirs - not needed in light of the above change","package":"CSApprox.zip","4":"CSApprox.zip","src_id":"10336","5":"10336","creation_date":"1238658729","6":"1238658729"},{"0":"2390","vim_version":"7.0","1":"7.0","script_version":"3.05","2":"3.05","version_comment":"Fix a harmless \"Undefined variable\" error in :CSApproxSnapshot\r\n\r\nFix a behavioral bug when dumping out colors defined external to the scheme.","3":"Fix a harmless \"Undefined variable\" error in :CSApproxSnapshot\r\n\r\nFix a behavioral bug when dumping out colors defined external to the scheme.","package":"CSApprox.zip","4":"CSApprox.zip","src_id":"9891","5":"9891","creation_date":"1233393867","6":"1233393867"},{"0":"2390","vim_version":"7.0","1":"7.0","script_version":"3.00","2":"3.00","version_comment":"Update the docs for better info on :CSApproxSnapshot\r\n\r\nAllow snapshotted schemes to work on Vim 6, and work properly in Konsole and Eterm (thanks David Majnemer!)\r\n\r\nFix a bug causing a syntax error when using GVim while CSApprox was loaded.  (thanks again, David Majnemer!)","3":"Update the docs for better info on :CSApproxSnapshot\r\n\r\nAllow snapshotted schemes to work on Vim 6, and work properly in Konsole and Eterm (thanks David Majnemer!)\r\n\r\nFix a bug causing a syntax error when using GVim while CSApprox was loaded.  (thanks again, David Majnemer!)","package":"CSApprox.zip","4":"CSApprox.zip","src_id":"9849","5":"9849","creation_date":"1232586616","6":"1232586616"},{"0":"2390","vim_version":"7.0","1":"7.0","script_version":"2.00","2":"2.00","version_comment":"Add a hooks system, allowing users to specify a command to run, either before or after the approximation algorithm is run, for all schemes or one specific one.\r\n\r\nAlso rewrite :CSApproxSnapshot to be more maintainable and less of a hack, and fix several bugs that it contained.\r\n","3":"Add a hooks system, allowing users to specify a command to run, either before or after the approximation algorithm is run, for all schemes or one specific one.\r\n\r\nAlso rewrite :CSApproxSnapshot to be more maintainable and less of a hack, and fix several bugs that it contained.\r\n","package":"CSApprox.zip","4":"CSApprox.zip","src_id":"9666","5":"9666","creation_date":"1229254739","6":"1229254739"},{"0":"2390","vim_version":"7.0","1":"7.0","script_version":"1.50","2":"1.50","version_comment":"Add :CSApproxSnapshot for writing out a colorscheme file representing the current colors that will work in gvim, 88 color vim, or 256 color vim, even without +gui.  See :help :CSApproxSnapshot","3":"Add :CSApproxSnapshot for writing out a colorscheme file representing the current colors that will work in gvim, 88 color vim, or 256 color vim, even without +gui.  See :help :CSApproxSnapshot","package":"CSApprox.zip","4":"CSApprox.zip","src_id":"9525","5":"9525","creation_date":"1227118828","6":"1227118828"},{"0":"2390","vim_version":"7.0","1":"7.0","script_version":"1.10","2":"1.10","version_comment":"Distribute an rgb.txt along with CSApprox, so that CSApprox can still be used on distributions where no rgb.txt is provided with the X server (like Ubuntu Intrepid Ibex).  Thanks to Penn Su for finding this!","3":"Distribute an rgb.txt along with CSApprox, so that CSApprox can still be used on distributions where no rgb.txt is provided with the X server (like Ubuntu Intrepid Ibex).  Thanks to Penn Su for finding this!","package":"CSApprox.zip","4":"CSApprox.zip","src_id":"9406","5":"9406","creation_date":"1225172773","6":"1225172773"},{"0":"2390","vim_version":"7.0","1":"7.0","script_version":"1.00","2":"1.00","version_comment":"Initial upload","3":"Initial upload","package":"CSApprox.zip","4":"CSApprox.zip","src_id":"9308","5":"9308","creation_date":"1223183915","6":"1223183915"}]},"2389":{"script_id":"2389","0":"2389","script_name":"pdc.vim","1":"pdc.vim","script_type":"syntax","2":"syntax","summary":"Syntax file for Pandoc ","3":"Syntax file for Pandoc ","description":"Syntax file for Pandoc, file structure is similar to markdown, but it allows for LaTeX and other features. \r\n\r\nIt can read markdown and (subsets of) reStructuredText, HTML, and LaTeX, and it can write markdown, reStructuredText, HTML, LaTeX, ConTeXt, PDF, RTF, DocBook XML, OpenDocument XML, ODT, GNU Texinfo, MediaWiki markup, groff man pages, and S5 HTML slide shows.\r\n\r\nSee http:\/\/johnmacfarlane.net\/pandoc\/","4":"Syntax file for Pandoc, file structure is similar to markdown, but it allows for LaTeX and other features. \r\n\r\nIt can read markdown and (subsets of) reStructuredText, HTML, and LaTeX, and it can write markdown, reStructuredText, HTML, LaTeX, ConTeXt, PDF, RTF, DocBook XML, OpenDocument XML, ODT, GNU Texinfo, MediaWiki markup, groff man pages, and S5 HTML slide shows.\r\n\r\nSee http:\/\/johnmacfarlane.net\/pandoc\/","install_details":"Save the file in your ~\/.vim\/syntax\/ directory.\r\n\r\nIn vim use :set syntax=pdc \r\n\r\nor \r\n\r\nAdd create a file in ~\/.vim\/ftdetect\/ called pdc.vim, that contains:\r\n\" Pandoc\r\nau! Bufread,BufNewFile *.pdc    set filetype=pdc","5":"Save the file in your ~\/.vim\/syntax\/ directory.\r\n\r\nIn vim use :set syntax=pdc \r\n\r\nor \r\n\r\nAdd create a file in ~\/.vim\/ftdetect\/ called pdc.vim, that contains:\r\n\" Pandoc\r\nau! Bufread,BufNewFile *.pdc    set filetype=pdc","first_name":"jeremy","6":"jeremy","last_name":"schultz","7":"schultz","releases":[{"0":"2389","vim_version":"6.0","1":"6.0","script_version":"1.2","2":"1.2","version_comment":"-   Fixed an issue with Block elements (header) not being highlighted when placed on the first or second line of the file\r\n-   Fixed multi line HTML comment block\r\n-   Fixed lowercase list items\r\n-   Fixed list items gobbling to many empty lines\r\n-   Added highlight support to identify newline (2 spaces)\r\n-   Fixed HTML highlight, ignore if the first character in the angle brackets is not a letter \r\n-   Fixed Emphasis highlighting when it contained multiple spaces","3":"-   Fixed an issue with Block elements (header) not being highlighted when placed on the first or second line of the file\r\n-   Fixed multi line HTML comment block\r\n-   Fixed lowercase list items\r\n-   Fixed list items gobbling to many empty lines\r\n-   Added highlight support to identify newline (2 spaces)\r\n-   Fixed HTML highlight, ignore if the first character in the angle brackets is not a letter \r\n-   Fixed Emphasis highlighting when it contained multiple spaces","package":"pdc.vim","4":"pdc.vim","src_id":"9430","5":"9430","creation_date":"1225820914","6":"1225820914"},{"0":"2389","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"pdc.vim","4":"pdc.vim","src_id":"9302","5":"9302","creation_date":"1222981461","6":"1222981461"}]},"2388":{"script_id":"2388","0":"2388","script_name":"conomode.vim","1":"conomode.vim","script_type":"utility","2":"utility","summary":"Vi-style editing for the command line","3":"Vi-style editing for the command line","description":"Continued here: https:\/\/github.com\/Houl\/conomode-vim (2017 Aug 06)\r\n\r\nImplements a kind of Normal mode ( \"Cmdline-Normal mode\" ) on top of the Command line.  Purpose is similar to the cmdline-window (q:), but navigation and editing can be done in-place.  Of course the cmdline-window is much more powerful.\r\n\r\nConomode does not replace Vim's native emacs-style command line editing, it just adds one key: CTRL-O (see below).\r\n\r\n- enter with c_<C-O>   (press CTRL-O while in Command-line mode)\r\n- mode indicator is a colon \":\", moved along with the cursor, hiding the char under it\r\n- quit to Cmdline-mode with I, i, a, A, : or any unmapped key (which then executes or inserts itself), or wait 60 seconds.\r\n- quit to Normal mode with Esc\r\n\r\nFeatures So Far:\r\n- Motions: h l w b e W B E 0 ^ $ f{char} F{char} t{char} T{char} ; , %    also in Operator pending mode\r\n- Operators: d y c    these write to the unnamed register; c prompts for input()\r\n- Shortcuts: yy dd D x X s C    yy -> y_, dd -> d_, D -> d$, x -> dl, X -> dh, s -> cl, C -> c$\r\n- Simple Changes: ~ r{char}\r\n- Putting: P p     put the unnamed register\r\n- Repeating: .     repeatable commands: d r c ~ o   also: I i a A\r\n- Macros: q @      q starts[\/stops] recording, @ executes, no register involved\r\n- Mode Switching:  I i a A - back to Cmdline (with positioned cursor),  <Esc> - back to Normal mode, <CR> - execute Cmdline, : - back to Cmdline (remove all text)\r\n- Insert: o        input() version of i (accepts a count and is recordable)\r\n- Undo: u U        redo with \"U\" (to keep c_CTRL-R working); undo information survives mode switching (!); undo is yet unlimited\r\n- Count: can be given for most commands\r\n- Misc: <C-L> - redraw the Cmdline\r\n\r\nNotes:\r\n- the mode indicator makes UTF-8 characters look garbled - it's only a display problem; press Ctrl-L to redraw the Cmdline; I'd rather not use conomode with UTF-8, sorry ...\r\n\r\nFeedback is welcome (bugs, usage improvements, does it feel like vi?, etc.)\r\n\r\nHave fun!\r\n\r\n2012 Apr 14","4":"Continued here: https:\/\/github.com\/Houl\/conomode-vim (2017 Aug 06)\r\n\r\nImplements a kind of Normal mode ( \"Cmdline-Normal mode\" ) on top of the Command line.  Purpose is similar to the cmdline-window (q:), but navigation and editing can be done in-place.  Of course the cmdline-window is much more powerful.\r\n\r\nConomode does not replace Vim's native emacs-style command line editing, it just adds one key: CTRL-O (see below).\r\n\r\n- enter with c_<C-O>   (press CTRL-O while in Command-line mode)\r\n- mode indicator is a colon \":\", moved along with the cursor, hiding the char under it\r\n- quit to Cmdline-mode with I, i, a, A, : or any unmapped key (which then executes or inserts itself), or wait 60 seconds.\r\n- quit to Normal mode with Esc\r\n\r\nFeatures So Far:\r\n- Motions: h l w b e W B E 0 ^ $ f{char} F{char} t{char} T{char} ; , %    also in Operator pending mode\r\n- Operators: d y c    these write to the unnamed register; c prompts for input()\r\n- Shortcuts: yy dd D x X s C    yy -> y_, dd -> d_, D -> d$, x -> dl, X -> dh, s -> cl, C -> c$\r\n- Simple Changes: ~ r{char}\r\n- Putting: P p     put the unnamed register\r\n- Repeating: .     repeatable commands: d r c ~ o   also: I i a A\r\n- Macros: q @      q starts[\/stops] recording, @ executes, no register involved\r\n- Mode Switching:  I i a A - back to Cmdline (with positioned cursor),  <Esc> - back to Normal mode, <CR> - execute Cmdline, : - back to Cmdline (remove all text)\r\n- Insert: o        input() version of i (accepts a count and is recordable)\r\n- Undo: u U        redo with \"U\" (to keep c_CTRL-R working); undo information survives mode switching (!); undo is yet unlimited\r\n- Count: can be given for most commands\r\n- Misc: <C-L> - redraw the Cmdline\r\n\r\nNotes:\r\n- the mode indicator makes UTF-8 characters look garbled - it's only a display problem; press Ctrl-L to redraw the Cmdline; I'd rather not use conomode with UTF-8, sorry ...\r\n\r\nFeedback is welcome (bugs, usage improvements, does it feel like vi?, etc.)\r\n\r\nHave fun!\r\n\r\n2012 Apr 14","install_details":":source conomode.vim\r\n\r\nCan be used as a plugin.\r\n\r\nNote: Vim7.3 is recommended, older Vims are likely to crash due to a bug in getcmdline()\r\n\r\nThe plugin defines a lot of mappings for Cmdline-mode, but these are local to the script -- so except for <C-O>, there cannot be a conflict with other mappings.\r\n\r\n\r\nHint:\r\nto autoload the plugin when pressing <C-O> the first time, you can create a \"macros\" folder, put the script file there and add the following code to your vimrc:\r\n\" vimrc:\r\ncmap <C-O> <C-R>=<sid>LoadConoMode()<CR><C-O>\r\nfunc! <sid>LoadConoMode()\r\n    cunmap <C-O>\r\n    verbose runtime macros\/conomode.vim\r\n    redraw\r\n    return \"\"\r\nendfunc\r\n\r\n2012 Apr 14","5":":source conomode.vim\r\n\r\nCan be used as a plugin.\r\n\r\nNote: Vim7.3 is recommended, older Vims are likely to crash due to a bug in getcmdline()\r\n\r\nThe plugin defines a lot of mappings for Cmdline-mode, but these are local to the script -- so except for <C-O>, there cannot be a conflict with other mappings.\r\n\r\n\r\nHint:\r\nto autoload the plugin when pressing <C-O> the first time, you can create a \"macros\" folder, put the script file there and add the following code to your vimrc:\r\n\" vimrc:\r\ncmap <C-O> <C-R>=<sid>LoadConoMode()<CR><C-O>\r\nfunc! <sid>LoadConoMode()\r\n    cunmap <C-O>\r\n    verbose runtime macros\/conomode.vim\r\n    redraw\r\n    return \"\"\r\nendfunc\r\n\r\n2012 Apr 14","first_name":"Andy","6":"Andy","last_name":"Wokula","7":"Wokula","releases":[{"0":"2388","vim_version":"7.3","1":"7.3","script_version":"0.6.1","2":"0.6.1","version_comment":"BF: fixed dumb error with cw (was ok in v0.4)\r\nBF: now conomode also disabled for :debug and <C-R>=","3":"BF: fixed dumb error with cw (was ok in v0.4)\r\nBF: now conomode also disabled for :debug and <C-R>=","package":"conomode.vim","4":"conomode.vim","src_id":"17340","5":"17340","creation_date":"1327941823","6":"1327941823"},{"0":"2388","vim_version":"7.3","1":"7.3","script_version":"0.6","2":"0.6","version_comment":"Note: default key changed to CTRL-O\r\nInsert keys I i a A no longer prompt for input()\r\nNF: added motions %, | (bar), t and T\r\nNF: separate undo stacks, per cmdtype\r\nNF: g:conomode_emacs_keys to enable a few Emacs keys, Ctrl-W, Ctrl-Y (disabled per default)\r\nNF: (non-vi) gX to cut older undo states\r\nBF: added init folklore\r\nBF: better escaping when recording c{text}<Enter>\r\nBF: removed count limits for h and l motions\r\nBF: yy, dd, cc now use whole-line text object (matters for repeat)\r\nBF: f now inclusive","3":"Note: default key changed to CTRL-O\r\nInsert keys I i a A no longer prompt for input()\r\nNF: added motions %, | (bar), t and T\r\nNF: separate undo stacks, per cmdtype\r\nNF: g:conomode_emacs_keys to enable a few Emacs keys, Ctrl-W, Ctrl-Y (disabled per default)\r\nNF: (non-vi) gX to cut older undo states\r\nBF: added init folklore\r\nBF: better escaping when recording c{text}<Enter>\r\nBF: removed count limits for h and l motions\r\nBF: yy, dd, cc now use whole-line text object (matters for repeat)\r\nBF: f now inclusive","package":"conomode.vim","4":"conomode.vim","src_id":"17328","5":"17328","creation_date":"1327782812","6":"1327782812"},{"0":"2388","vim_version":"7.3","1":"7.3","script_version":"0.4","2":"0.4","version_comment":"NF: Macro recording: q @\r\nNF: undo survives mode switching\r\nNF: Tilde command: ~\r\nNF: Insert commands: I i a A (now prompt for input())\r\nNF: <Esc> (and o O ) switches to the Cmdline (not Normal mode)\r\nNF: more verbose now\r\nBF: disallowed recursive Conomode\r\nBF: better multi-byte support","3":"NF: Macro recording: q @\r\nNF: undo survives mode switching\r\nNF: Tilde command: ~\r\nNF: Insert commands: I i a A (now prompt for input())\r\nNF: <Esc> (and o O ) switches to the Cmdline (not Normal mode)\r\nNF: more verbose now\r\nBF: disallowed recursive Conomode\r\nBF: better multi-byte support","package":"conomode.vim","4":"conomode.vim","src_id":"13637","5":"13637","creation_date":"1282345472","6":"1282345472"},{"0":"2388","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"conomode.vim","4":"conomode.vim","src_id":"9301","5":"9301","creation_date":"1222978583","6":"1222978583"}]},"2387":{"script_id":"2387","0":"2387","script_name":"cern_root.vim","1":"cern_root.vim","script_type":"syntax","2":"syntax","summary":"Basic syntax highlighting for ROOT","3":"Basic syntax highlighting for ROOT","description":"Basic syntax highlighting for the ROOT Data Analysis Framework\r\nhttp:\/\/root.cern.ch","4":"Basic syntax highlighting for the ROOT Data Analysis Framework\r\nhttp:\/\/root.cern.ch","install_details":"Put file or copy contents in ~\/.vim\/after\/syntax\/c.vim","5":"Put file or copy contents in ~\/.vim\/after\/syntax\/c.vim","first_name":"Theo","6":"Theo","last_name":"Christoudias","7":"Christoudias","releases":[{"0":"2387","vim_version":"6.0","1":"6.0","script_version":"0.4.1","2":"0.4.1","version_comment":"Added option to turn off for non-ROOT C\/Cpp files (:let c_no_cern_root=1)","3":"Added option to turn off for non-ROOT C\/Cpp files (:let c_no_cern_root=1)","package":"cern_root.vim","4":"cern_root.vim","src_id":"12875","5":"12875","creation_date":"1271745007","6":"1271745007"}]},"2386":{"script_id":"2386","0":"2386","script_name":"endwise.vim","1":"endwise.vim","script_type":"utility","2":"utility","summary":"Wisely add ","3":"Wisely add ","description":"This is a simple plugin that helps to end certain structures automatically.  In Ruby, this means adding \"end\" after \"if\", \"do\", \"def\" and several other keywords. In Vim Script, this amounts to appropriately adding \"endfunction\", \"endif\", etc.  There's also VB support (don't ask), Bourne shell, C\/C++ preprocessor, Objective C, Lua, Elixir, and more.\r\n\r\nA primary guiding principle in designing this plugin was that an erroneous insertion is never acceptable.  The behavior is only triggered once pressing enter on the end of the line.  When this happens, endwise searches for a matching end structure and only adds one if none is found.\r\n\r\nWhile the goal was to make it customizable, this turned out to be a tall order.  Every language has vastly different requirements.  Nonetheless, for those bold enough to attempt it, you can follow the model of the autocmds in the plugin to set the three magic variables governing endwise's behavior.\r\n\r\nhttps:\/\/github.com\/tpope\/vim-endwise","4":"This is a simple plugin that helps to end certain structures automatically.  In Ruby, this means adding \"end\" after \"if\", \"do\", \"def\" and several other keywords. In Vim Script, this amounts to appropriately adding \"endfunction\", \"endif\", etc.  There's also VB support (don't ask), Bourne shell, C\/C++ preprocessor, Objective C, Lua, Elixir, and more.\r\n\r\nA primary guiding principle in designing this plugin was that an erroneous insertion is never acceptable.  The behavior is only triggered once pressing enter on the end of the line.  When this happens, endwise searches for a matching end structure and only adds one if none is found.\r\n\r\nWhile the goal was to make it customizable, this turned out to be a tall order.  Every language has vastly different requirements.  Nonetheless, for those bold enough to attempt it, you can follow the model of the autocmds in the plugin to set the three magic variables governing endwise's behavior.\r\n\r\nhttps:\/\/github.com\/tpope\/vim-endwise","install_details":"Install in ~\/.vim\/plugin (~\\vimfiles\\plugin on Windows)","5":"Install in ~\/.vim\/plugin (~\\vimfiles\\plugin on Windows)","first_name":"Tim","6":"Tim","last_name":"Pope","7":"Pope","releases":[{"0":"2386","vim_version":"7.4","1":"7.4","script_version":"1.3","2":"1.3","version_comment":"Better support for automatically combining with other <CR> maps.\r\nBetter support for manually creating combined <CR> maps.\r\nAdd support for filetype=crystal.\r\nAdd support for filetype=htmldjango.\r\nAdd support for filetype=jinja.html and filetype=htmijinja.\r\nAdd support for filetype=make.\r\nAdd support for filetype=verilog.\r\nAdd support for filetype=bash (alias for sh).\r\nAdd support for filetype=haskell (C preprocessor only).\r\nAdd support for filetype=snippets from utilsnips.\r\nMiscellaneous improvements to various filetype support.\r\nFix issues with <CR> map in command-line window.","3":"Better support for automatically combining with other <CR> maps.\r\nBetter support for manually creating combined <CR> maps.\r\nAdd support for filetype=crystal.\r\nAdd support for filetype=htmldjango.\r\nAdd support for filetype=jinja.html and filetype=htmijinja.\r\nAdd support for filetype=make.\r\nAdd support for filetype=verilog.\r\nAdd support for filetype=bash (alias for sh).\r\nAdd support for filetype=haskell (C preprocessor only).\r\nAdd support for filetype=snippets from utilsnips.\r\nMiscellaneous improvements to various filetype support.\r\nFix issues with <CR> map in command-line window.","package":"endwise.zip","4":"endwise.zip","src_id":"27968","5":"27968","creation_date":"1648159150","6":"1648159150"},{"0":"2386","vim_version":"7.0","1":"7.0","script_version":"1.2","2":"1.2","version_comment":"Elixer support.\r\nMATLAB file support.\r\nObjective C support.\r\nClose after Ruby assignment and def modifiers.\r\nAdd support for Lua local functions.\r\nUse then not if to trigger fi for sh.\r\nFix C match detection.\r\nFix false positives on certain file types.\r\nFix duplicates on <C-X><CR>.\r\nRemove unrelated <M-o> map.\r\nAllow chaining any <Plug>...CR mappings.","3":"Elixer support.\r\nMATLAB file support.\r\nObjective C support.\r\nClose after Ruby assignment and def modifiers.\r\nAdd support for Lua local functions.\r\nUse then not if to trigger fi for sh.\r\nFix C match detection.\r\nFix false positives on certain file types.\r\nFix duplicates on <C-X><CR>.\r\nRemove unrelated <M-o> map.\r\nAllow chaining any <Plug>...CR mappings.","package":"endwise.zip","4":"endwise.zip","src_id":"21704","5":"21704","creation_date":"1396333617","6":"1396333617"},{"0":"2386","vim_version":"7.0","1":"7.0","script_version":"1.1","2":"1.1","version_comment":"Add support for Lua, Bourne shell, and C preprocessor.\r\nDetect delimitMate mapping and append accordingly.\r\nAdd `g:endwise_no_mappings` to allow skipping maps.","3":"Add support for Lua, Bourne shell, and C preprocessor.\r\nDetect delimitMate mapping and append accordingly.\r\nAdd `g:endwise_no_mappings` to allow skipping maps.","package":"endwise.zip","4":"endwise.zip","src_id":"19291","5":"19291","creation_date":"1357080786","6":"1357080786"},{"0":"2386","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"endwise.vim","4":"endwise.vim","src_id":"9299","5":"9299","creation_date":"1222918254","6":"1222918254"}]},"2385":{"script_id":"2385","0":"2385","script_name":"sqlite_c","1":"sqlite_c","script_type":"syntax","2":"syntax","summary":"SQLite C interface Vim syntax file.","3":"SQLite C interface Vim syntax file.","description":"This script provides SQLite C\/C++ interface syntax highlighting.","4":"This script provides SQLite C\/C++ interface syntax highlighting.","install_details":"1. extract the zip in ~\/.vim (Unix) or <user home>\\vimfile (Windows)\r\n2. Add following line in ~\/.vim\/after\/syntax\/c.vim (create one if you don't have this file).\r\n  runtime! syntax\/sqlite_c.vim\r\n \r\n3. Enjoy.","5":"1. extract the zip in ~\/.vim (Unix) or <user home>\\vimfile (Windows)\r\n2. Add following line in ~\/.vim\/after\/syntax\/c.vim (create one if you don't have this file).\r\n  runtime! syntax\/sqlite_c.vim\r\n \r\n3. Enjoy.","first_name":"Ding-Yi","6":"Ding-Yi","last_name":"Chen","7":"Chen","releases":[{"0":"2385","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"sqlite_c-0.1.zip","4":"sqlite_c-0.1.zip","src_id":"9295","5":"9295","creation_date":"1222760228","6":"1222760228"}]},"2384":{"script_id":"2384","0":"2384","script_name":"buf2html.vim","1":"buf2html.vim","script_type":"utility","2":"utility","summary":"beta** - generate HTML\/XHTML+CSS from a Vim buffer","3":"beta** - generate HTML\/XHTML+CSS from a Vim buffer","description":"This is the next evolution of the script formerly known as \"code2html.vim\" and before that \"2html.vim\" (the latter being still a part of the standard Vim release runtime collection). See http:\/\/www.vim.org\/scripts\/script.php?script_id=330.\r\n\r\nThis is considered beta-quality code at this time.\r\n\r\nAccomplished goals (so far) for this release include:\r\n\r\n  * Let it produce correct output for all option variants including with\/out-line-numbering, with\/out-using-css, etc.\r\n\r\n * Try to create an HTML comment line that records the SHA1 sum for the buffer data input. Could be useful in future scenarios.\r\n\r\n * Clean up the markup so that interstitial spaces in code (not being purposely verbose here, I don't know what else to call them right now) between highlighted identifiers is *not* marked up with redundant default bg\/fg color specifiers. This is a huge weakness of the original script.\r\n\r\n * Create a visible symbolic (and easily understood) markup in the output when the source is a Makefile, to display where each TAB (ascii \\011) was.\r\n\r\nLeft to do is more debugging; at least 1 known bug exists in that an occasional character will disappear from the output ;-(. And optimization.  And restoring the functionality that was once working in the script in its previous incarnation as code2html.vim, working out a list of system-installed mono fonts and including those in the CSS style declaration.\r\n\r\nThis script was developed to meet the author's needs. It might not meet yours. If you can improve on it without clobbering the author's needs, however, your patches are welcome. In any event, the customary legalese-ish disclaimer about \"FITNESS FOR ANY PURPOSE\" applies.\r\n\r\nThe result of running this script on itself can be viewed at http:\/\/intrepid.perlmonk.org\/apropos.vim\/buf2html\/current\/myself.html\r\n\r\nAs always, credit to Bram Moolenaar and David Nečas (Yeti) for the original script and Christian Hujer for his later contribution.","4":"This is the next evolution of the script formerly known as \"code2html.vim\" and before that \"2html.vim\" (the latter being still a part of the standard Vim release runtime collection). See http:\/\/www.vim.org\/scripts\/script.php?script_id=330.\r\n\r\nThis is considered beta-quality code at this time.\r\n\r\nAccomplished goals (so far) for this release include:\r\n\r\n  * Let it produce correct output for all option variants including with\/out-line-numbering, with\/out-using-css, etc.\r\n\r\n * Try to create an HTML comment line that records the SHA1 sum for the buffer data input. Could be useful in future scenarios.\r\n\r\n * Clean up the markup so that interstitial spaces in code (not being purposely verbose here, I don't know what else to call them right now) between highlighted identifiers is *not* marked up with redundant default bg\/fg color specifiers. This is a huge weakness of the original script.\r\n\r\n * Create a visible symbolic (and easily understood) markup in the output when the source is a Makefile, to display where each TAB (ascii \\011) was.\r\n\r\nLeft to do is more debugging; at least 1 known bug exists in that an occasional character will disappear from the output ;-(. And optimization.  And restoring the functionality that was once working in the script in its previous incarnation as code2html.vim, working out a list of system-installed mono fonts and including those in the CSS style declaration.\r\n\r\nThis script was developed to meet the author's needs. It might not meet yours. If you can improve on it without clobbering the author's needs, however, your patches are welcome. In any event, the customary legalese-ish disclaimer about \"FITNESS FOR ANY PURPOSE\" applies.\r\n\r\nThe result of running this script on itself can be viewed at http:\/\/intrepid.perlmonk.org\/apropos.vim\/buf2html\/current\/myself.html\r\n\r\nAs always, credit to Bram Moolenaar and David Nečas (Yeti) for the original script and Christian Hujer for his later contribution.","install_details":"Installation is left to the user to decide upon. This being a script, not a plugin, it can be saved in any convenient directory. The author favors ~\/scripts on his accounts. It's always called by  :source'ing it anyhow.\r\n\r\nNote well: like its predecessor scripts, this script only really works well when used with the GUI variant of Vim (gVim).\r\n","5":"Installation is left to the user to decide upon. This being a script, not a plugin, it can be saved in any convenient directory. The author favors ~\/scripts on his accounts. It's always called by  :source'ing it anyhow.\r\n\r\nNote well: like its predecessor scripts, this script only really works well when used with the GUI variant of Vim (gVim).\r\n","first_name":"S\u00c3\u00b6ren","6":"S\u00c3\u00b6ren","last_name":"Andersen","7":"Andersen","releases":[{"0":"2384","vim_version":"7.0","1":"7.0","script_version":"2.0b2","2":"2.0b2","version_comment":"May have fixed the character-eating problem ;-\/. Lacking time right now to check many different files.","3":"May have fixed the character-eating problem ;-\/. Lacking time right now to check many different files.","package":"buf2html.zip","4":"buf2html.zip","src_id":"9369","5":"9369","creation_date":"1224366346","6":"1224366346"},{"0":"2384","vim_version":"7.0","1":"7.0","script_version":"2.0b1","2":"2.0b1","version_comment":"Initial upload","3":"Initial upload","package":"buf2html.zip","4":"buf2html.zip","src_id":"9287","5":"9287","creation_date":"1222515836","6":"1222515836"}]},"2383":{"script_id":"2383","0":"2383","script_name":"winter.vim","1":"winter.vim","script_type":"color scheme","2":"color scheme","summary":"light gray style","3":"light gray style","description":"The winter.vim is a color sheme file (only for GVIM) which uses a light grey background makes the VIM look like the scenes of winter.","4":"The winter.vim is a color sheme file (only for GVIM) which uses a light grey background makes the VIM look like the scenes of winter.","install_details":"1\\ Copy the winter.vim to the colors directory of Vimfiles, such as ~\/.vim\/colors\/ \r\n\r\n2\\ Add one command in your _vimrc or .vimrc: color winter\r\n\r\n3\\ Enjoy vimming:-)","5":"1\\ Copy the winter.vim to the colors directory of Vimfiles, such as ~\/.vim\/colors\/ \r\n\r\n2\\ Add one command in your _vimrc or .vimrc: color winter\r\n\r\n3\\ Enjoy vimming:-)","first_name":"Wenlong","6":"Wenlong","last_name":"Che","7":"Che","releases":[{"0":"2383","vim_version":"7.0","1":"7.0","script_version":"1.3","2":"1.3","version_comment":"Modified the RGB values of the LineNr and Cursor.","3":"Modified the RGB values of the LineNr and Cursor.","package":"winter.vim","4":"winter.vim","src_id":"10041","5":"10041","creation_date":"1235653072","6":"1235653072"},{"0":"2383","vim_version":"7.0","1":"7.0","script_version":"1.2","2":"1.2","version_comment":"Change some details about GUI colors","3":"Change some details about GUI colors","package":"winter.vim","4":"winter.vim","src_id":"9984","5":"9984","creation_date":"1234827145","6":"1234827145"},{"0":"2383","vim_version":"7.0","1":"7.0","script_version":"1.1","2":"1.1","version_comment":"More beautiful... ( At least I think so :-) )","3":"More beautiful... ( At least I think so :-) )","package":"winter.vim","4":"winter.vim","src_id":"9956","5":"9956","creation_date":"1234439641","6":"1234439641"},{"0":"2383","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"winter.vim","4":"winter.vim","src_id":"9286","5":"9286","creation_date":"1222432951","6":"1222432951"}]},"2382":{"script_id":"2382","0":"2382","script_name":"Note Maker","1":"Note Maker","script_type":"syntax","2":"syntax","summary":"Syntax highlighter for personal notes","3":"Syntax highlighter for personal notes","description":"This syntax file will allow text regions to be coloured differently in case of section\/subsection headings, italicize text or make it bold, highlight text regions, and more depending on the structure. For those who make notes in vim, refering to them later will become faster and more efficient.\r\n\r\nScreenshots:\r\nThe plain file:\r\nhttp:\/\/www.cse.iitb.ac.in\/~samhita\/vim\/noteMakerDemoPlain.html\r\nWith the syntax file:\r\nhttp:\/\/www.cse.iitb.ac.in\/~samhita\/vim\/noteMakerDemo.html","4":"This syntax file will allow text regions to be coloured differently in case of section\/subsection headings, italicize text or make it bold, highlight text regions, and more depending on the structure. For those who make notes in vim, refering to them later will become faster and more efficient.\r\n\r\nScreenshots:\r\nThe plain file:\r\nhttp:\/\/www.cse.iitb.ac.in\/~samhita\/vim\/noteMakerDemoPlain.html\r\nWith the syntax file:\r\nhttp:\/\/www.cse.iitb.ac.in\/~samhita\/vim\/noteMakerDemo.html","install_details":"Extract the package in your .vim folder.\r\nThe default filetype is .notes.\r\nDetailed instructions for automatic file type detection are given in the readme file.","5":"Extract the package in your .vim folder.\r\nThe default filetype is .notes.\r\nDetailed instructions for automatic file type detection are given in the readme file.","first_name":"Samhita","6":"Samhita","last_name":"Kasula","7":"Kasula","releases":[{"0":"2382","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"noteMaker.tar.gz","4":"noteMaker.tar.gz","src_id":"9285","5":"9285","creation_date":"1222425808","6":"1222425808"}]},"2381":{"script_id":"2381","0":"2381","script_name":"RemoveIfdef","1":"RemoveIfdef","script_type":"utility","2":"utility","summary":"remove ifdef macro of C\/C++ program","3":"remove ifdef macro of C\/C++ program","description":"Description:\r\n  This script finds #ifdef\/#else\/#endif keyword, and removes undefined area.\r\n  And display the defined macros in your source code after executing.\r\n\r\n  When we analysis the source code written by another person, a lot of\r\n  #ifdef are troublesome very much.  This script helps you to analysis it by\r\n  removing undefined area.\r\n  Please see the example. It helps you to understand this script work.\r\n\r\nInstructions:\r\n  1 - Put in your plugin directory, and open the C\/C++ file\r\n  2 - Type :RemoveIfdef\r\n  3 - This script finds ifdef macro and remove undefined area\r\n  If you want to add the macros, add them to this script' argument.\r\n\r\nFeature:\r\n  - support the comment (\/\/ and \/* ... *\/)\r\n  - decide macro keyword from file extension (support C\/C++ and Verilog)\r\n\r\nArgument:\r\n  <None> : Remove undefined area by the macro defined in just source file.\r\n  [-n]   : Print code with original source code line. This argument should\r\n           be specified at first.\r\n           ex) #define AAA\r\n               #ifdef AAA\r\n               \/\/ comment\r\n               #endif\r\n                 ===>\r\n               1 #define AAA\r\n               3 \/\/ comment\r\n  String : Add these strings into macro list\r\n\r\nNote:\r\n 1. This script changes the C\/C++ source code directly. If you want to\r\n    cancel, please undo (u).\r\n 2. If some macro are defined in the include files, this script doesn't\r\n    work exactly.\r\n\r\nExamples:\r\n  - example source code\r\n      #define AAA\r\n      \/\/ comment 1\r\n      #ifdef BBB\r\n      #ifdef AAA\r\n      \/\/ comment 2\r\n      #else \/\/ AAA\r\n      \/\/ comment 3\r\n      #endif \/\/ AAA\r\n      #else \/\/ BBB\r\n      #ifdef AAA\r\n      \/\/ comment 4\r\n      #else \/\/ AAA\r\n      \/\/ comment 5\r\n      #endif \/\/ AAA\r\n      #endif \/\/ BBB\r\n\r\n  - Type RemoveIfdef\r\n      -> \/\/ comment 1\r\n         \/\/ comment 4\r\n\r\n  - Type RemoveIfdef BBB\r\n      -> \/\/ comment 1\r\n         \/\/ comment 2\r\n\r\nKnown Bug:\r\n - Does not support include\r\n - There are some bugs about \/* ... *\/ comment analysis","4":"Description:\r\n  This script finds #ifdef\/#else\/#endif keyword, and removes undefined area.\r\n  And display the defined macros in your source code after executing.\r\n\r\n  When we analysis the source code written by another person, a lot of\r\n  #ifdef are troublesome very much.  This script helps you to analysis it by\r\n  removing undefined area.\r\n  Please see the example. It helps you to understand this script work.\r\n\r\nInstructions:\r\n  1 - Put in your plugin directory, and open the C\/C++ file\r\n  2 - Type :RemoveIfdef\r\n  3 - This script finds ifdef macro and remove undefined area\r\n  If you want to add the macros, add them to this script' argument.\r\n\r\nFeature:\r\n  - support the comment (\/\/ and \/* ... *\/)\r\n  - decide macro keyword from file extension (support C\/C++ and Verilog)\r\n\r\nArgument:\r\n  <None> : Remove undefined area by the macro defined in just source file.\r\n  [-n]   : Print code with original source code line. This argument should\r\n           be specified at first.\r\n           ex) #define AAA\r\n               #ifdef AAA\r\n               \/\/ comment\r\n               #endif\r\n                 ===>\r\n               1 #define AAA\r\n               3 \/\/ comment\r\n  String : Add these strings into macro list\r\n\r\nNote:\r\n 1. This script changes the C\/C++ source code directly. If you want to\r\n    cancel, please undo (u).\r\n 2. If some macro are defined in the include files, this script doesn't\r\n    work exactly.\r\n\r\nExamples:\r\n  - example source code\r\n      #define AAA\r\n      \/\/ comment 1\r\n      #ifdef BBB\r\n      #ifdef AAA\r\n      \/\/ comment 2\r\n      #else \/\/ AAA\r\n      \/\/ comment 3\r\n      #endif \/\/ AAA\r\n      #else \/\/ BBB\r\n      #ifdef AAA\r\n      \/\/ comment 4\r\n      #else \/\/ AAA\r\n      \/\/ comment 5\r\n      #endif \/\/ AAA\r\n      #endif \/\/ BBB\r\n\r\n  - Type RemoveIfdef\r\n      -> \/\/ comment 1\r\n         \/\/ comment 4\r\n\r\n  - Type RemoveIfdef BBB\r\n      -> \/\/ comment 1\r\n         \/\/ comment 2\r\n\r\nKnown Bug:\r\n - Does not support include\r\n - There are some bugs about \/* ... *\/ comment analysis","install_details":"","5":"","first_name":"Masashi","6":"Masashi","last_name":"Watanabe","7":"Watanabe","releases":[{"0":"2381","vim_version":"7.0","1":"7.0","script_version":"0.42","2":"0.42","version_comment":"Initial upload","3":"Initial upload","package":"removeifdef.vim","4":"removeifdef.vim","src_id":"9284","5":"9284","creation_date":"1222376359","6":"1222376359"}]},"2380":{"script_id":"2380","0":"2380","script_name":"Verilog constructs plugin","1":"Verilog constructs plugin","script_type":"utility","2":"utility","summary":"Plugin to insert Verilog Constructs","3":"Plugin to insert Verilog Constructs","description":"This plugin is for those guys who forget the syntax of different constructs in Verilog.This plugin will add a new menu to GVIM. The sub menus when clicked insert appropriate templates.\r\nThis is developed only for GVIM and has key mappings to use with plain VIM. Also its written with windows in mind, so unix user excuse me.\r\n","4":"This plugin is for those guys who forget the syntax of different constructs in Verilog.This plugin will add a new menu to GVIM. The sub menus when clicked insert appropriate templates.\r\nThis is developed only for GVIM and has key mappings to use with plain VIM. Also its written with windows in mind, so unix user excuse me.\r\n","install_details":"====================================================================\r\n  INSTALLATION\r\n==================================================================== \r\n(1) Copy the zip archive  vlog-support.zip to ($VIM\/vimfiles) and run\r\n \r\n      unzip vlog-support.zip\r\n      (Winzip -> Extract here)\r\n \r\n(2) Set at least some personal details into $VIM\/_vimrc\r\n      Here the minimal personalization \r\n \r\n  let g:VERILOG_AuthorName   = \"T. Anil Kumar\"     \r\n  let g:VERILOG_AuthorRef    = \"MTS\"                         \r\n  let g:VERILOG_Email        = \"anilk_tallaprada@yahoo.com\"            \r\n \r\n3) Restart gVim and generate the help tags \r\n \r\n  :helptags $VIM\/vimfiles\/doc (Windows)\r\n \r\nand look at the VerilogSupport help with\r\n \r\n  :help vlogsupport \r\n \r\n \r\nPlease see \u00e2\u0080\u009cAdditional Tips\u00e2\u0080\u009d section in README.vlogsupport for some cool tips\r\n","5":"====================================================================\r\n  INSTALLATION\r\n==================================================================== \r\n(1) Copy the zip archive  vlog-support.zip to ($VIM\/vimfiles) and run\r\n \r\n      unzip vlog-support.zip\r\n      (Winzip -> Extract here)\r\n \r\n(2) Set at least some personal details into $VIM\/_vimrc\r\n      Here the minimal personalization \r\n \r\n  let g:VERILOG_AuthorName   = \"T. Anil Kumar\"     \r\n  let g:VERILOG_AuthorRef    = \"MTS\"                         \r\n  let g:VERILOG_Email        = \"anilk_tallaprada@yahoo.com\"            \r\n \r\n3) Restart gVim and generate the help tags \r\n \r\n  :helptags $VIM\/vimfiles\/doc (Windows)\r\n \r\nand look at the VerilogSupport help with\r\n \r\n  :help vlogsupport \r\n \r\n \r\nPlease see \u00e2\u0080\u009cAdditional Tips\u00e2\u0080\u009d section in README.vlogsupport for some cool tips\r\n","first_name":"Anil","6":"Anil","last_name":"Tallapragada","7":"Tallapragada","releases":[{"0":"2380","vim_version":"7.2","1":"7.2","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"vlog-support.zip","4":"vlog-support.zip","src_id":"9283","5":"9283","creation_date":"1222349806","6":"1222349806"}]},"2379":{"script_id":"2379","0":"2379","script_name":" win9xblueback.vim","1":" win9xblueback.vim","script_type":"color scheme","2":"color scheme","summary":"Windows9x blue back screen like colorscheme","3":"Windows9x blue back screen like colorscheme","description":"Windows9x blue back screen like colorscheme for the GUI.\r\nScreenshot at http:\/\/jstap.web.fc2.com\/win9xblueback.html","4":"Windows9x blue back screen like colorscheme for the GUI.\r\nScreenshot at http:\/\/jstap.web.fc2.com\/win9xblueback.html","install_details":"Put it in one of your colors directories.\r\nThen, just do :colorscheme win9xblueback","5":"Put it in one of your colors directories.\r\nThen, just do :colorscheme win9xblueback","first_name":"Kojo","6":"Kojo","last_name":"Sugita","7":"Sugita","releases":[{"0":"2379","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"win9xblueback.vim","4":"win9xblueback.vim","src_id":"9281","5":"9281","creation_date":"1222347119","6":"1222347119"}]},"2378":{"script_id":"2378","0":"2378","script_name":"mlint.vim","1":"mlint.vim","script_type":"ftplugin","2":"ftplugin","summary":"Runs Matlab's mlint program and highlights the code appropriately","3":"Runs Matlab's mlint program and highlights the code appropriately","description":"This is a filetype plugin for Matlab .m files. It runs Matlab's mlint function at appropriate times, parses the output and highlights the code in a similar fashion to the Matlab editor.\r\n\r\nThe script maps <LocalLeader>l to its RunLint() function, so you can run the mlint tool at other times other than the automatic ones.\r\n\r\n<LocalLeader>m gives the messages from mlint on the status line for the line that the cursor is on.\r\n\r\nTo view all the messages for a file, use <LocalLeader>o to bring up the quickfix list.\r\n\r\nOn windows the automatic updating can get quite annoying because it pops up a command window everytime it runs mlint, even if only briefly. I would like to call mlint using \"start \/b mlint\" which should prevent this, however there is a bug in Vim which stops me being able to do this. So as a workaround you can optionally disable running mlint on hover by putting this line in your .vimrc:\r\nlet mlint_hover = 0","4":"This is a filetype plugin for Matlab .m files. It runs Matlab's mlint function at appropriate times, parses the output and highlights the code in a similar fashion to the Matlab editor.\r\n\r\nThe script maps <LocalLeader>l to its RunLint() function, so you can run the mlint tool at other times other than the automatic ones.\r\n\r\n<LocalLeader>m gives the messages from mlint on the status line for the line that the cursor is on.\r\n\r\nTo view all the messages for a file, use <LocalLeader>o to bring up the quickfix list.\r\n\r\nOn windows the automatic updating can get quite annoying because it pops up a command window everytime it runs mlint, even if only briefly. I would like to call mlint using \"start \/b mlint\" which should prevent this, however there is a bug in Vim which stops me being able to do this. So as a workaround you can optionally disable running mlint on hover by putting this line in your .vimrc:\r\nlet mlint_hover = 0","install_details":"Put matlab.vim in vimfiles\/after\/ftplugin or in $HOME\/.vim\/after\/ftplugin.\r\nRestart vim.","5":"Put matlab.vim in vimfiles\/after\/ftplugin or in $HOME\/.vim\/after\/ftplugin.\r\nRestart vim.","first_name":"Thomas","6":"Thomas","last_name":"Ibbotson","7":"Ibbotson","releases":[{"0":"2378","vim_version":"7.0","1":"7.0","script_version":"0.6.1","2":"0.6.1","version_comment":"Now uses the quickfix list with <LocalLeader>o","3":"Now uses the quickfix list with <LocalLeader>o","package":"matlab.vim","4":"matlab.vim","src_id":"16722","5":"16722","creation_date":"1319280387","6":"1319280387"},{"0":"2378","vim_version":"7.0","1":"7.0","script_version":"0.6","2":"0.6","version_comment":"Add an outline window to show all mlint messages for the file, using <LocalLeader>o.","3":"Add an outline window to show all mlint messages for the file, using <LocalLeader>o.","package":"matlab.vim","4":"matlab.vim","src_id":"16719","5":"16719","creation_date":"1319232587","6":"1319232587"},{"0":"2378","vim_version":"7.0","1":"7.0","script_version":"0.5","2":"0.5","version_comment":"Ben Fritz: This fixes that Windows does stupid things with shellescape() if\r\nshellslash is set.","3":"Ben Fritz: This fixes that Windows does stupid things with shellescape() if\r\nshellslash is set.","package":"matlab.vim","4":"matlab.vim","src_id":"16718","5":"16718","creation_date":"1319230664","6":"1319230664"},{"0":"2378","vim_version":"7.0","1":"7.0","script_version":"0.4","2":"0.4","version_comment":"Ben Fritz:\r\nRunLint() only called on a cursorhold event if the buffer has been changed.","3":"Ben Fritz:\r\nRunLint() only called on a cursorhold event if the buffer has been changed.","package":"matlab.vim","4":"matlab.vim","src_id":"11210","5":"11210","creation_date":"1250601516","6":"1250601516"},{"0":"2378","vim_version":"7.0","1":"7.0","script_version":"0.3.1","2":"0.3.1","version_comment":"Another bug fix for deleting the temporary directory. Directory deletion was failing as there was still a '.m~' file in the directory. This is now deleted, allowing the directory to be deleted.","3":"Another bug fix for deleting the temporary directory. Directory deletion was failing as there was still a '.m~' file in the directory. This is now deleted, allowing the directory to be deleted.","package":"matlab.vim","4":"matlab.vim","src_id":"10701","5":"10701","creation_date":"1243590372","6":"1243590372"},{"0":"2378","vim_version":"7.0","1":"7.0","script_version":"0.3","2":"0.3","version_comment":"More fixes from Benjamin Fritz:\r\n1.) File names with spaces handled properly\r\n2.) fnameescape and shellescape now used properly\r\n3.) allowed user to specify path to mlint in case it isn't in the system path\r\n4.) detect failure deleting temp directory by checking for existence\r\nof the directory after the deletion\r\n5.) show messages that mlint gives about line 0 (the filename)","3":"More fixes from Benjamin Fritz:\r\n1.) File names with spaces handled properly\r\n2.) fnameescape and shellescape now used properly\r\n3.) allowed user to specify path to mlint in case it isn't in the system path\r\n4.) detect failure deleting temp directory by checking for existence\r\nof the directory after the deletion\r\n5.) show messages that mlint gives about line 0 (the filename)","package":"matlab.vim","4":"matlab.vim","src_id":"9352","5":"9352","creation_date":"1224020838","6":"1224020838"},{"0":"2378","vim_version":"7.0","1":"7.0","script_version":"0.2.1","2":"0.2.1","version_comment":"Fixed temporary directory deletion bug (as far as I have tested it).","3":"Fixed temporary directory deletion bug (as far as I have tested it).","package":"matlab.vim","4":"matlab.vim","src_id":"9347","5":"9347","creation_date":"1223896018","6":"1223896018"},{"0":"2378","vim_version":"7.0","1":"7.0","script_version":"0.2","2":"0.2","version_comment":"Added significant changes made by Benjamin Fritz. Now deletes the temporary folders it creates. the clearLint() function now only deletes the MLint matches rather than all of them as it had previously. Known bug: on unloading the buffer the temporary directory is deleted, reloading the buffer causes the script to error as it can't find the directory. I am working on a fix for this and should upload it soon. Also note that the script will on work with Vim 7.1 or higher.","3":"Added significant changes made by Benjamin Fritz. Now deletes the temporary folders it creates. the clearLint() function now only deletes the MLint matches rather than all of them as it had previously. Known bug: on unloading the buffer the temporary directory is deleted, reloading the buffer causes the script to error as it can't find the directory. I am working on a fix for this and should upload it soon. Also note that the script will on work with Vim 7.1 or higher.","package":"matlab.vim","4":"matlab.vim","src_id":"9342","5":"9342","creation_date":"1223860305","6":"1223860305"},{"0":"2378","vim_version":"7.2","1":"7.2","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"mlint.vim","4":"mlint.vim","src_id":"9280","5":"9280","creation_date":"1222334879","6":"1222334879"}]},"2377":{"script_id":"2377","0":"2377","script_name":"htmlspecialchars","1":"htmlspecialchars","script_type":"ftplugin","2":"ftplugin","summary":"Convert special characters to HTML entities.","3":"Convert special characters to HTML entities.","description":"This plugin provides commands to convert special characters of HTML to entities.\r\n\r\nUsage:\r\n\t:[range]HTMLSpecialChars\r\n\t:[range]HTMLSpecialCharsDecode\r\n\r\nManual:\r\n\t:help htmlspecialchars.txt\r\n","4":"This plugin provides commands to convert special characters of HTML to entities.\r\n\r\nUsage:\r\n\t:[range]HTMLSpecialChars\r\n\t:[range]HTMLSpecialCharsDecode\r\n\r\nManual:\r\n\t:help htmlspecialchars.txt\r\n","install_details":"The plugin uses Vimball plugin archive format.\r\nTo install the package, load the file to Vim and run command\r\n\r\n    :source %\r\n\r\nTo remove the plugin, type\r\n\r\n    :RmVimball htmlspecialchars","5":"The plugin uses Vimball plugin archive format.\r\nTo install the package, load the file to Vim and run command\r\n\r\n    :source %\r\n\r\nTo remove the plugin, type\r\n\r\n    :RmVimball htmlspecialchars","first_name":"Taku","6":"Taku","last_name":"Amano","7":"Amano","releases":[{"0":"2377","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"htmlspecialchars.vba","4":"htmlspecialchars.vba","src_id":"9255","5":"9255","creation_date":"1221491462","6":"1221491462"}]},"2376":{"script_id":"2376","0":"2376","script_name":"vim-addon-sql","1":"vim-addon-sql","script_type":"utility","2":"utility","summary":"alias sensitive SQL completion (MySQL, Postgresql, SQLite)","3":"alias sensitive SQL completion (MySQL, Postgresql, SQLite)","description":"KISS implementation of SQL completion for Vim:\r\n\r\nFirst you have to connect to a database. Examples:\r\n\r\n  MySQL:\r\n  call vim_addon_sql#Connect('mysql',{'host':'127.0.0.1','database':'DATABASE', 'user':'USER', 'password' : 'PASSWORT'})\r\n\r\n  SQLITE:\r\n  call vim_addon_sql#Connect('mysql',{'database':'filepath'})\r\n\r\n  Postgresql (see code)\r\n\r\nA connection only initializes b:db_conn which is a Vim object providing\r\nfunctions for querying the database.\r\n\r\nSetup mappings by calling this function:\r\n  call vim_addon_sql#UI()\r\n\r\nIn non visual mode the query start \/ end is determined by either ; or empty lines.\r\nIn visual mode the selection will be executed\r\n\r\nExecution is done by command line tools (psql, mysql, sqlite(3))\r\nThe result of those queries is parsed by Vim to fill alias aware completion.\r\n\r\nExample:\r\n\r\n1)\r\n  SELECT *, CURSOR FROM table1, table2\r\n  Now CURSOR will only contain fields found in either table1 or table2\r\n\r\n2)\r\n  SELECT *, a.CURSOR FROM table1 as a, table2\r\n  Now the completion will only contain fields of table1\r\n\r\nExpect some minor bugs - however this it works quite nicely in practise.\r\n\r\ncamel case like completion is also supported. eg d_u -> db_users\r\n\r\nAlso completes MySQL internal functions\r\n\r\nIf you have any questions contact me.","4":"KISS implementation of SQL completion for Vim:\r\n\r\nFirst you have to connect to a database. Examples:\r\n\r\n  MySQL:\r\n  call vim_addon_sql#Connect('mysql',{'host':'127.0.0.1','database':'DATABASE', 'user':'USER', 'password' : 'PASSWORT'})\r\n\r\n  SQLITE:\r\n  call vim_addon_sql#Connect('mysql',{'database':'filepath'})\r\n\r\n  Postgresql (see code)\r\n\r\nA connection only initializes b:db_conn which is a Vim object providing\r\nfunctions for querying the database.\r\n\r\nSetup mappings by calling this function:\r\n  call vim_addon_sql#UI()\r\n\r\nIn non visual mode the query start \/ end is determined by either ; or empty lines.\r\nIn visual mode the selection will be executed\r\n\r\nExecution is done by command line tools (psql, mysql, sqlite(3))\r\nThe result of those queries is parsed by Vim to fill alias aware completion.\r\n\r\nExample:\r\n\r\n1)\r\n  SELECT *, CURSOR FROM table1, table2\r\n  Now CURSOR will only contain fields found in either table1 or table2\r\n\r\n2)\r\n  SELECT *, a.CURSOR FROM table1 as a, table2\r\n  Now the completion will only contain fields of table1\r\n\r\nExpect some minor bugs - however this it works quite nicely in practise.\r\n\r\ncamel case like completion is also supported. eg d_u -> db_users\r\n\r\nAlso completes MySQL internal functions\r\n\r\nIf you have any questions contact me.","install_details":"The *info* file in the top level directory contains all dependencies. I recommend using vim-addon-manager to install them all at once","5":"The *info* file in the top level directory contains all dependencies. I recommend using vim-addon-manager to install them all at once","first_name":"Marc","6":"Marc","last_name":"Weber","7":"Weber","releases":[{"0":"2376","vim_version":"7.0","1":"7.0","script_version":"0.2.4","2":"0.2.4","version_comment":"firebird support","3":"firebird support","package":"vim-addon-sql-0.2.4.zip","4":"vim-addon-sql-0.2.4.zip","src_id":"15618","5":"15618","creation_date":"1304997880","6":"1304997880"},{"0":"2376","vim_version":"7.0","1":"7.0","script_version":"0.2.3","2":"0.2.3","version_comment":"mysql: also complete function names","3":"mysql: also complete function names","package":"vim-addon-sql-0.2.3.zip","4":"vim-addon-sql-0.2.3.zip","src_id":"15225","5":"15225","creation_date":"1300167358","6":"1300167358"},{"0":"2376","vim_version":"7.0","1":"7.0","script_version":"0.2.2","2":"0.2.2","version_comment":"fix CamelCase alias field completion. Allow _ in names. Close error buffer if no error occured","3":"fix CamelCase alias field completion. Allow _ in names. Close error buffer if no error occured","package":"vim-addon-sql-0.2.2.zip","4":"vim-addon-sql-0.2.2.zip","src_id":"14957","5":"14957","creation_date":"1296867641","6":"1296867641"},{"0":"2376","vim_version":"7.0","1":"7.0","script_version":"0.2.1","2":"0.2.1","version_comment":"bugfix on aliases","3":"bugfix on aliases","package":"vim-addon-sql-0.2.1.zip","4":"vim-addon-sql-0.2.1.zip","src_id":"14637","5":"14637","creation_date":"1293550953","6":"1293550953"},{"0":"2376","vim_version":"7.0","1":"7.0","script_version":"0.2","2":"0.2","version_comment":"new release as vim-addon-sql. Sqlite and Postgres are supported. Code import from tovl","3":"new release as vim-addon-sql. Sqlite and Postgres are supported. Code import from tovl","package":"vim-addon-sql-0.2.zip","4":"vim-addon-sql-0.2.zip","src_id":"13942","5":"13942","creation_date":"1285609854","6":"1285609854"},{"0":"2376","vim_version":"7.0","1":"7.0","script_version":"0.0","2":"0.0","version_comment":"fixed quoting of *, using stdin now to pass SQL command, vl#dev#sql#sql#ThisSQLCommand()\r\n can be overridden now","3":"fixed quoting of *, using stdin now to pass SQL command, vl#dev#sql#sql#ThisSQLCommand()\r\n can be overridden now","package":"vimlib_sql_installer_sourceme.zip","4":"vimlib_sql_installer_sourceme.zip","src_id":"9251","5":"9251","creation_date":"1221416339","6":"1221416339"}]},"2375":{"script_id":"2375","0":"2375","script_name":"if_v8","1":"if_v8","script_type":"game","2":"game","summary":"V8 interface to Vim","3":"V8 interface to Vim","description":"V8 is Google's open source JavaScript engine.\r\n\r\nRequirements:\r\n  linux or windows.\r\n  Vim executable file with some exported symbol that if_v8 requires.\r\n    On linux:\r\n      Compile with gcc's -rdynamic option.\r\n    On windows (msvc):\r\n      Use vim_export.def and add linker flag \"\/DEF:vim_export.def\".\r\n      nmake -f Make_mvc.mak linkdebug=\/DEF:vim_export.def\r\n\r\nUsage:\r\n  :source \/path\/to\/if_v8\/init.vim\r\n  :V8 print('hello, world')\r\n  => hello, world\r\n  :V8 3 + 4\r\n  => 7\r\n  :V8 vim.execute('version')\r\n  => ... version message\r\n  :V8 var tw = vim.eval('&tw')\r\n  :V8 tw\r\n  => 78\r\n  :V8 vim.let('&tw', '40')\r\n  :echo &tw\r\n  => 40\r\n  :V8 load('foo.js')","4":"V8 is Google's open source JavaScript engine.\r\n\r\nRequirements:\r\n  linux or windows.\r\n  Vim executable file with some exported symbol that if_v8 requires.\r\n    On linux:\r\n      Compile with gcc's -rdynamic option.\r\n    On windows (msvc):\r\n      Use vim_export.def and add linker flag \"\/DEF:vim_export.def\".\r\n      nmake -f Make_mvc.mak linkdebug=\/DEF:vim_export.def\r\n\r\nUsage:\r\n  :source \/path\/to\/if_v8\/init.vim\r\n  :V8 print('hello, world')\r\n  => hello, world\r\n  :V8 3 + 4\r\n  => 7\r\n  :V8 vim.execute('version')\r\n  => ... version message\r\n  :V8 var tw = vim.eval('&tw')\r\n  :V8 tw\r\n  => 78\r\n  :V8 vim.let('&tw', '40')\r\n  :echo &tw\r\n  => 40\r\n  :V8 load('foo.js')","install_details":"Latest source: svn checkout http:\/\/vim-soko.googlecode.com\/svn\/trunk\/if_v8","5":"Latest source: svn checkout http:\/\/vim-soko.googlecode.com\/svn\/trunk\/if_v8","first_name":"Yukihiro","6":"Yukihiro","last_name":"Nakadaira","7":"Nakadaira","releases":[{"0":"2375","vim_version":"7.4","1":"7.4","script_version":"0.7","2":"0.7","version_comment":"update for latest v8 version","3":"update for latest v8 version","package":"if_v8.zip","4":"if_v8.zip","src_id":"22640","5":"22640","creation_date":"1416735480","6":"1416735480"},{"0":"2375","vim_version":"7.0","1":"7.0","script_version":"0.6","2":"0.6","version_comment":"maintenance release","3":"maintenance release","package":"if_v8.zip","4":"if_v8.zip","src_id":"13343","5":"13343","creation_date":"1279328404","6":"1279328404"},{"0":"2375","vim_version":"7.0","1":"7.0","script_version":"0.5.1","2":"0.5.1","version_comment":"Added gc()","3":"Added gc()","package":"if_v8.zip","4":"if_v8.zip","src_id":"10487","5":"10487","creation_date":"1241000692","6":"1241000692"},{"0":"2375","vim_version":"7.0","1":"7.0","script_version":"0.5","2":"0.5","version_comment":"Added Funcref.","3":"Added Funcref.","package":"if_v8.zip","4":"if_v8.zip","src_id":"9836","5":"9836","creation_date":"1232193140","6":"1232193140"},{"0":"2375","vim_version":"7.0","1":"7.0","script_version":"0.4.1","2":"0.4.1","version_comment":"bug fix","3":"bug fix","package":"if_v8.zip","4":"if_v8.zip","src_id":"9754","5":"9754","creation_date":"1231081000","6":"1231081000"},{"0":"2375","vim_version":"7.0","1":"7.0","script_version":"0.4","2":"0.4","version_comment":"Added Vim's builtin functions.\r\nAdded VimList\/VimDict class to provide direct access to VimL variable.","3":"Added Vim's builtin functions.\r\nAdded VimList\/VimDict class to provide direct access to VimL variable.","package":"if_v8.zip","4":"if_v8.zip","src_id":"9753","5":"9753","creation_date":"1231053674","6":"1231053674"},{"0":"2375","vim_version":"7.0","1":"7.0","script_version":"0.3","2":"0.3","version_comment":"Added windows support.","3":"Added windows support.","package":"if_v8.zip","4":"if_v8.zip","src_id":"9663","5":"9663","creation_date":"1229211940","6":"1229211940"},{"0":"2375","vim_version":"7.0","1":"7.0","script_version":"0.2","2":"0.2","version_comment":"Removed FEAT_PYTHON dependency.","3":"Removed FEAT_PYTHON dependency.","package":"if_v8.zip","4":"if_v8.zip","src_id":"9254","5":"9254","creation_date":"1221453100","6":"1221453100"},{"0":"2375","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"if_v8.zip","4":"if_v8.zip","src_id":"9249","5":"9249","creation_date":"1221378888","6":"1221378888"}]},"2374":{"script_id":"2374","0":"2374","script_name":"dokuwiki.vim","1":"dokuwiki.vim","script_type":"syntax","2":"syntax","summary":"A simple syntax file for DokuWiki.","3":"A simple syntax file for DokuWiki.","description":"A simple syntax file for DokuWiki.\r\n\r\nThis consists completely of slight modifications to wikipedia.vim, vimscript #1787, so you'll need to get\r\nthat script too, or not much will happen.\r\n\r\nI'm no expert, so do let me know if you find any mistakes. My email is in both files. Thanks. :)\r\n\r\nThis file also provides a few mappings for doing those pesky headers.\r\n\r\n,,h1 through ,,h6 will give you a header. This should allow you to press \",,h1\" in INSERT mode, then type your header, then press <C-j> to \r\njump to the next line. \r\n\r\n(If <C-j> doesn't jump for you, let me know; this may require latex-suite\r\n(http:\/\/vim-latex.sf.net), but that would be a hefty thing to download just for this.)\r\n\r\nYou can also use ,,hd to demote a header, and ,,hp to promote it.","4":"A simple syntax file for DokuWiki.\r\n\r\nThis consists completely of slight modifications to wikipedia.vim, vimscript #1787, so you'll need to get\r\nthat script too, or not much will happen.\r\n\r\nI'm no expert, so do let me know if you find any mistakes. My email is in both files. Thanks. :)\r\n\r\nThis file also provides a few mappings for doing those pesky headers.\r\n\r\n,,h1 through ,,h6 will give you a header. This should allow you to press \",,h1\" in INSERT mode, then type your header, then press <C-j> to \r\njump to the next line. \r\n\r\n(If <C-j> doesn't jump for you, let me know; this may require latex-suite\r\n(http:\/\/vim-latex.sf.net), but that would be a hefty thing to download just for this.)\r\n\r\nYou can also use ,,hd to demote a header, and ,,hp to promote it.","install_details":"First get Wikimedia.vim (vimscript #1787).\r\n\r\nThen, just copy dokuwiki.vim to your $HOME\/.vim\/syntax\/ directory.\r\n\r\nAt present, you have to activate this highlighting manually.\r\n\r\n:se ft=dokuwiki\r\n\r\nbecause there isn't a canonical extension for DokuWiki files (at least, that I know of). However, you can set all *.txt files to automatically be set to DokuWiki if you wish.\r\n\r\nMake or edit $HOME\/.vim\/ftdetect\/txt.vim:\r\n\r\n\" Taken from http:\/\/en.wikipedia.org\/wiki\/Wikipedia:Text_editor_support#Vim\r\n\" \tIan Tegebo <ian.tegebo@gmail.com>\r\n\r\naugroup filetypedetect\r\n\tau BufNewFile,BufRead *.txt,*.wiki setf dokuwiki\r\naugroup END\r\n\r\nNow any *txt or *wiki file should open as dokuwiki.","5":"First get Wikimedia.vim (vimscript #1787).\r\n\r\nThen, just copy dokuwiki.vim to your $HOME\/.vim\/syntax\/ directory.\r\n\r\nAt present, you have to activate this highlighting manually.\r\n\r\n:se ft=dokuwiki\r\n\r\nbecause there isn't a canonical extension for DokuWiki files (at least, that I know of). However, you can set all *.txt files to automatically be set to DokuWiki if you wish.\r\n\r\nMake or edit $HOME\/.vim\/ftdetect\/txt.vim:\r\n\r\n\" Taken from http:\/\/en.wikipedia.org\/wiki\/Wikipedia:Text_editor_support#Vim\r\n\" \tIan Tegebo <ian.tegebo@gmail.com>\r\n\r\naugroup filetypedetect\r\n\tau BufNewFile,BufRead *.txt,*.wiki setf dokuwiki\r\naugroup END\r\n\r\nNow any *txt or *wiki file should open as dokuwiki.","first_name":"Bill","6":"Bill","last_name":"Powell","7":"Powell","releases":[{"0":"2374","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"dokuwiki.vim","4":"dokuwiki.vim","src_id":"9241","5":"9241","creation_date":"1221127552","6":"1221127552"}]},"2373":{"script_id":"2373","0":"2373","script_name":"ClosePairs","1":"ClosePairs","script_type":"utility","2":"utility","summary":"Auto closes pairs of characters","3":"Auto closes pairs of characters","description":"Autocloses pairs of chararacters as seen in TextMate or Scribes.\r\n\r\nI couldn't find a script that worked as I liked, so here's my very simple attempt :)\r\n\r\nPairs are (), [], {}, '', \"\"\r\n\r\nFeatures\r\n=======\r\n\r\n1) in INSERT mode, typing the closing character let the cursor \"escape\" the pair \r\n\r\ne.g.: (cursor represented with a pipe, on the left what you type, on the right what you get)\r\n\" -> \"|\"\r\nsome text -> \"some text|\"\r\n\" -> \"some text\"|\r\n\r\n* useful when typing an open\/close bracket pair as in foo()\r\n\r\n* works with already existing text\r\ne.g.:\r\n(move cursor) -> \"this is a string|\"\r\n\" -> \"this is a string\"|\r\n\r\n\r\n2) \"atomic\" deletion of a pair\r\n()|<bs> -> |\r\n(|)<bs> -> |\r\n* won't work with <del> (use <del> when you don't want the closing bracket\/quote)\r\n\r\n3) experimental support for visual mode\r\n\r\nselect abc \r\ntype <leader>\" -> \"abc\"\r\n\r\n\r\ntested with vim 7; might work with earlier versions, though\r\nhope you'll like it, let me know!\r\nyou can comment here: http:\/\/www.flatpress.org\/home\/?entry=entry080910-135006\r\n\r\n\r\nUPDATE: since you made me notice, here's the other scripts dealing with the same problem\r\n\r\n* vimscript #1849 - AutoClose by Karl Guertin\r\n* vimscript #2009 - AutoClose by Thiago Alvares\r\n\r\nthey all differs for little, the first is a bit simpler; the latter is probably the most configurable.\r\n\r\nPick your favorite :)\r\n\r\n\r\n","4":"Autocloses pairs of chararacters as seen in TextMate or Scribes.\r\n\r\nI couldn't find a script that worked as I liked, so here's my very simple attempt :)\r\n\r\nPairs are (), [], {}, '', \"\"\r\n\r\nFeatures\r\n=======\r\n\r\n1) in INSERT mode, typing the closing character let the cursor \"escape\" the pair \r\n\r\ne.g.: (cursor represented with a pipe, on the left what you type, on the right what you get)\r\n\" -> \"|\"\r\nsome text -> \"some text|\"\r\n\" -> \"some text\"|\r\n\r\n* useful when typing an open\/close bracket pair as in foo()\r\n\r\n* works with already existing text\r\ne.g.:\r\n(move cursor) -> \"this is a string|\"\r\n\" -> \"this is a string\"|\r\n\r\n\r\n2) \"atomic\" deletion of a pair\r\n()|<bs> -> |\r\n(|)<bs> -> |\r\n* won't work with <del> (use <del> when you don't want the closing bracket\/quote)\r\n\r\n3) experimental support for visual mode\r\n\r\nselect abc \r\ntype <leader>\" -> \"abc\"\r\n\r\n\r\ntested with vim 7; might work with earlier versions, though\r\nhope you'll like it, let me know!\r\nyou can comment here: http:\/\/www.flatpress.org\/home\/?entry=entry080910-135006\r\n\r\n\r\nUPDATE: since you made me notice, here's the other scripts dealing with the same problem\r\n\r\n* vimscript #1849 - AutoClose by Karl Guertin\r\n* vimscript #2009 - AutoClose by Thiago Alvares\r\n\r\nthey all differs for little, the first is a bit simpler; the latter is probably the most configurable.\r\n\r\nPick your favorite :)\r\n\r\n\r\n","install_details":"","5":"","first_name":"Edoardo","6":"Edoardo","last_name":"Vacchi","7":"Vacchi","releases":[{"0":"2373","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"closepairs.vim","4":"closepairs.vim","src_id":"9239","5":"9239","creation_date":"1221020182","6":"1221020182"}]},"2372":{"script_id":"2372","0":"2372","script_name":"automatic for Verilog","1":"automatic for Verilog","script_type":"ftplugin","2":"ftplugin","summary":"Automatic generator for Verilog HDL","3":"Automatic generator for Verilog HDL","description":"Support Automatic functions like Emacs for Verilog HDL\r\nFeature list:\r\n1) Auto Argument (the same as Emacs)\r\n2) Auto Instance (power than Emacs)\r\n3) Auto Define Signals\r\n4) Auto unit delay \"<=\" to \"<= #`FFD\"\r\n5) Auto always block\r\n6) Auto header\r\n7) Auto comment\r\nMy blog: http:\/\/blog.sina.com.cn\/arrowroothover\r\nMy E-mail: arrowroothover@hotmail.com","4":"Support Automatic functions like Emacs for Verilog HDL\r\nFeature list:\r\n1) Auto Argument (the same as Emacs)\r\n2) Auto Instance (power than Emacs)\r\n3) Auto Define Signals\r\n4) Auto unit delay \"<=\" to \"<= #`FFD\"\r\n5) Auto always block\r\n6) Auto header\r\n7) Auto comment\r\nMy blog: http:\/\/blog.sina.com.cn\/arrowroothover\r\nMy E-mail: arrowroothover@hotmail.com","install_details":"put the automatic.vim in .vim\/ftplugin\/vlog\/\r\nbefor.v: a Verilog example before run auto functions\r\nafter.v: a Verilog example after run auto functions","5":"put the automatic.vim in .vim\/ftplugin\/vlog\/\r\nbefor.v: a Verilog example before run auto functions\r\nafter.v: a Verilog example after run auto functions","first_name":"gavin","6":"gavin","last_name":"ge","7":"ge","releases":[{"0":"2372","vim_version":"7.0","1":"7.0","script_version":"1.55","2":"1.55","version_comment":"Fix bugs, compatiable with designware IP.","3":"Fix bugs, compatiable with designware IP.","package":"automatic.vim","4":"automatic.vim","src_id":"9296","5":"9296","creation_date":"1222828795","6":"1222828795"},{"0":"2372","vim_version":"7.0","1":"7.0","script_version":"1.50","2":"1.50","version_comment":"Fix some bugs, support two styles of port declaration. \r\nAdd a new feature: automatic sensitive list, which is helpful for those do not support verilog 2001 yet.\r\nGive examples for all automatice functions.","3":"Fix some bugs, support two styles of port declaration. \r\nAdd a new feature: automatic sensitive list, which is helpful for those do not support verilog 2001 yet.\r\nGive examples for all automatice functions.","package":"vim.rar","4":"vim.rar","src_id":"9243","5":"9243","creation_date":"1221164447","6":"1221164447"},{"0":"2372","vim_version":"7.0","1":"7.0","script_version":"1.00","2":"1.00","version_comment":"Initial upload","3":"Initial upload","package":"plugin.rar","4":"plugin.rar","src_id":"9230","5":"9230","creation_date":"1220839792","6":"1220839792"}]},"2371":{"script_id":"2371","0":"2371","script_name":"sqloracle.vim","1":"sqloracle.vim","script_type":"syntax","2":"syntax","summary":"color codes SQL keywords from Oracle 11g","3":"color codes SQL keywords from Oracle 11g","description":"An earlier version of this script (valid for Oracle keywords from Oracle 8i) is included in the Vim 7.2 release. This version has been upgraded to include Oracle functions, and keywords from Oracle 11g.","4":"An earlier version of this script (valid for Oracle keywords from Oracle 8i) is included in the Vim 7.2 release. This version has been upgraded to include Oracle functions, and keywords from Oracle 11g.","install_details":"Install in the Vim\\vimfiles\\syntax directory","5":"Install in the Vim\\vimfiles\\syntax directory","first_name":"Alvin","6":"Alvin","last_name":"Steele","7":"Steele","releases":[{"0":"2371","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"sqloracle.vim","4":"sqloracle.vim","src_id":"9226","5":"9226","creation_date":"1220623874","6":"1220623874"}]},"2370":{"script_id":"2370","0":"2370","script_name":"Duplicated","1":"Duplicated","script_type":"utility","2":"utility","summary":"Sorry. Duplicated. Please remove.","3":"Sorry. Duplicated. Please remove.","description":"Duplicated","4":"Duplicated","install_details":"","5":"","first_name":"Xin","6":"Xin","last_name":"Wang","7":"Wang","releases":[{"0":"2370","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"vimmp-0.1.tgz","4":"vimmp-0.1.tgz","src_id":"9219","5":"9219","creation_date":"1220417746","6":"1220417746"}]},"2369":{"script_id":"2369","0":"2369","script_name":"vimmp","1":"vimmp","script_type":"utility","2":"utility","summary":"An XMMS2 and MPD client for Vim","3":"An XMMS2 and MPD client for Vim","description":"This plugin is based on vimscript #2363, and add MPD support.\r\n\r\nRequirements\r\n============\r\n    Vim with +python support.\r\n    FOR XMMS2: XMMS2 with the Python interface.\r\n    FOR MPD: MPD and python-mpd.\r\n\r\nUsage\r\n=====\r\n    Using <leader>x to toggle the play window.\r\n\r\n    Also the following key shorts are available. Most key maps start with\r\n    c(Control) or l(playList).\r\n\r\n      <space>    Play the song under cursor.\r\n      <cr>       Same as <space>.\r\n      cs         Stop.\r\n      cp         Pause.\r\n      cr         Select a repeat mode.\r\n                 There are three modes for XMMS2: one, all, off.\r\n                 For MPD, there are two: off, all. So there command just toggle.\r\n      -          Decrease volume.\r\n      =          Increase volume.\r\n      r          Refresh window manually.\r\n      la         Add a file or directory to playlist.\r\n      lc         Clear the playlist.\r\n      ld         Remove the song under cursor from current playlist.\r\n      lf         Shuffer the list.\r\n      ll         Load a playlist.\r\n      ln         Create a new playlist, and save current contents to it.\r\n      ls         Sort the playlist, by artist, title or filename.\r\n                 Only available for XMMS2.\r\n\r\n\r\nCustomization\r\n=============\r\n    Specify the id3's encoding. This option is only for XMMS2, i.e\r\n        let g:xmms_id3_encoding=\"gbk\"\r\n\r\n    Specify the play window's width:\r\n        let g:xmms_window_width=30\r\n\r\n    Specify the playlist format, default is \"%artist - %title\", %album\r\n    is also avaiable.\r\n        let g:xmms_playlist_format=\"%title\"\r\n\r\n\r\nNotes for MPD users\r\n===================\r\n    - There's only one playlist which MPD uses to play, users can only load\r\n      other playlists' contents to that list. So the playlist name displayed\r\n      in the status line is just the playlist's version number.\r\n    - Currently, this plugin only support localhost mpd server.\r\n\r\n\r\nTips\r\n====\r\n    When adding music file or directory, you can use Ctrl-D to show all \r\n    candidates. Also, you can use arrow keys to navigate the history.\r\n\r\nLeave your comments in following link, or just mail me.\r\nhttp:\/\/danran.72pines.com\/vimmp","4":"This plugin is based on vimscript #2363, and add MPD support.\r\n\r\nRequirements\r\n============\r\n    Vim with +python support.\r\n    FOR XMMS2: XMMS2 with the Python interface.\r\n    FOR MPD: MPD and python-mpd.\r\n\r\nUsage\r\n=====\r\n    Using <leader>x to toggle the play window.\r\n\r\n    Also the following key shorts are available. Most key maps start with\r\n    c(Control) or l(playList).\r\n\r\n      <space>    Play the song under cursor.\r\n      <cr>       Same as <space>.\r\n      cs         Stop.\r\n      cp         Pause.\r\n      cr         Select a repeat mode.\r\n                 There are three modes for XMMS2: one, all, off.\r\n                 For MPD, there are two: off, all. So there command just toggle.\r\n      -          Decrease volume.\r\n      =          Increase volume.\r\n      r          Refresh window manually.\r\n      la         Add a file or directory to playlist.\r\n      lc         Clear the playlist.\r\n      ld         Remove the song under cursor from current playlist.\r\n      lf         Shuffer the list.\r\n      ll         Load a playlist.\r\n      ln         Create a new playlist, and save current contents to it.\r\n      ls         Sort the playlist, by artist, title or filename.\r\n                 Only available for XMMS2.\r\n\r\n\r\nCustomization\r\n=============\r\n    Specify the id3's encoding. This option is only for XMMS2, i.e\r\n        let g:xmms_id3_encoding=\"gbk\"\r\n\r\n    Specify the play window's width:\r\n        let g:xmms_window_width=30\r\n\r\n    Specify the playlist format, default is \"%artist - %title\", %album\r\n    is also avaiable.\r\n        let g:xmms_playlist_format=\"%title\"\r\n\r\n\r\nNotes for MPD users\r\n===================\r\n    - There's only one playlist which MPD uses to play, users can only load\r\n      other playlists' contents to that list. So the playlist name displayed\r\n      in the status line is just the playlist's version number.\r\n    - Currently, this plugin only support localhost mpd server.\r\n\r\n\r\nTips\r\n====\r\n    When adding music file or directory, you can use Ctrl-D to show all \r\n    candidates. Also, you can use arrow keys to navigate the history.\r\n\r\nLeave your comments in following link, or just mail me.\r\nhttp:\/\/danran.72pines.com\/vimmp","install_details":"    Putting following lines into your .vimrc\r\n\r\n        if has('python')\r\n            py import os, sys\r\n            py sys.path.append(os.path.expanduser(\"\/path\/to\/the\/vimmp\/dir\/\"))\r\n            pyf \/path\/to\/main.py\r\n        endif\r\n\r\n    For example, I put the vimmp dir in ~\/.vim, so the lines will be:\r\n\r\n        if has('python')\r\n            py import os, sys\r\n            py sys.path.append(os.path.expanduser(\"~\/.vim\/vimmp\"))\r\n            pyf ~\/.vim\/vimmp\/main.py\r\n        endif\r\n\r\n    Then specify what server you are using, \"xmms2\" or \"mpd\". (Although\r\n    the script will try to guess, but it's better to set it manually.)\r\n        let g:vimmp_server_type=\"xmms2\"\r\n\r\n    Also, add following map into .vimrc\r\n\r\n        nmap <silent> <leader>x :py vimmp_toggle()<cr>\r\n\r\n    FOR MPD USERS\r\n    -------------\r\n    In addtion to above settings, you also have to set the music and\r\n    playlist directory. They should be the same as in \/etc\/mpd.conf. i.e.\r\n        let g:mpd_music_directory=\"~\/music\"\r\n        let g:mpd_playlist_directory=\"~\/.mpd\/playlists\"\r\n\r\n","5":"    Putting following lines into your .vimrc\r\n\r\n        if has('python')\r\n            py import os, sys\r\n            py sys.path.append(os.path.expanduser(\"\/path\/to\/the\/vimmp\/dir\/\"))\r\n            pyf \/path\/to\/main.py\r\n        endif\r\n\r\n    For example, I put the vimmp dir in ~\/.vim, so the lines will be:\r\n\r\n        if has('python')\r\n            py import os, sys\r\n            py sys.path.append(os.path.expanduser(\"~\/.vim\/vimmp\"))\r\n            pyf ~\/.vim\/vimmp\/main.py\r\n        endif\r\n\r\n    Then specify what server you are using, \"xmms2\" or \"mpd\". (Although\r\n    the script will try to guess, but it's better to set it manually.)\r\n        let g:vimmp_server_type=\"xmms2\"\r\n\r\n    Also, add following map into .vimrc\r\n\r\n        nmap <silent> <leader>x :py vimmp_toggle()<cr>\r\n\r\n    FOR MPD USERS\r\n    -------------\r\n    In addtion to above settings, you also have to set the music and\r\n    playlist directory. They should be the same as in \/etc\/mpd.conf. i.e.\r\n        let g:mpd_music_directory=\"~\/music\"\r\n        let g:mpd_playlist_directory=\"~\/.mpd\/playlists\"\r\n\r\n","first_name":"Xin","6":"Xin","last_name":"Wang","7":"Wang","releases":[{"0":"2369","vim_version":"7.0","1":"7.0","script_version":"0.1.1","2":"0.1.1","version_comment":"Add description about the important g:vimmp_server_type option in the document.","3":"Add description about the important g:vimmp_server_type option in the document.","package":"vimmp-0.1.1.tgz","4":"vimmp-0.1.1.tgz","src_id":"9222","5":"9222","creation_date":"1220460558","6":"1220460558"},{"0":"2369","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"vimmp-0.1.tgz","4":"vimmp-0.1.tgz","src_id":"9218","5":"9218","creation_date":"1220417653","6":"1220417653"}]},"2368":{"script_id":"2368","0":"2368","script_name":"CCTree","1":"CCTree","script_type":"ftplugin","2":"ftplugin","summary":"C Call-Tree Explorer -- Cscope based source-code browser; code flow analyzer","3":"C Call-Tree Explorer -- Cscope based source-code browser; code flow analyzer","description":"Description:\r\n       Plugin generates symbol dependency tree (aka call tree, call graph) in real-time inside Vim using a Cscope database. Basic support for functions and macros; global variables, enums, typedefs can be cross-reference with additional processing. Functionality similar to that of tools and IDE's like CBrowser, Kscope, Source navigator, Eclipse, Source Insight. \r\n\r\nCurrently supported language: C. \r\nRequirements: Cscope, Vim 7.xx \r\n\r\nProject details\/Screenshots:  http:\/\/sites.google.com\/site\/vimcctree\/ \r\nCheck out  http:\/\/sourceforge.net\/projects\/ccglue\/ for an external tool that can produce cross-reference files from cscope [and ctags] databases that CCTree can load directly from disk.\r\n\r\nContributions or discussions are welcome at https:\/\/github.com\/hari-rangarajan\/CCTree\/\r\n ","4":"Description:\r\n       Plugin generates symbol dependency tree (aka call tree, call graph) in real-time inside Vim using a Cscope database. Basic support for functions and macros; global variables, enums, typedefs can be cross-reference with additional processing. Functionality similar to that of tools and IDE's like CBrowser, Kscope, Source navigator, Eclipse, Source Insight. \r\n\r\nCurrently supported language: C. \r\nRequirements: Cscope, Vim 7.xx \r\n\r\nProject details\/Screenshots:  http:\/\/sites.google.com\/site\/vimcctree\/ \r\nCheck out  http:\/\/sourceforge.net\/projects\/ccglue\/ for an external tool that can produce cross-reference files from cscope [and ctags] databases that CCTree can load directly from disk.\r\n\r\nContributions or discussions are welcome at https:\/\/github.com\/hari-rangarajan\/CCTree\/\r\n ","install_details":"Install details\r\n  Installation:\r\n               Copy this file to ~\/.vim\/plugins\/\r\n               or to \/vimfiles\/plugins\/  (on Win32 platforms)\r\n\r\n               It might also be possible to load it as a filetype plugin\r\n               ~\/.vim\/ftplugin\/c\/\r\n\r\n               Need to set :filetype plugin on\r\n          \r\nA help file is now available here: http:\/\/sites.google.com\/site\/vimcctree\/cctree.txt . Refer to help on building help tags.\r\n\r\n","5":"Install details\r\n  Installation:\r\n               Copy this file to ~\/.vim\/plugins\/\r\n               or to \/vimfiles\/plugins\/  (on Win32 platforms)\r\n\r\n               It might also be possible to load it as a filetype plugin\r\n               ~\/.vim\/ftplugin\/c\/\r\n\r\n               Need to set :filetype plugin on\r\n          \r\nA help file is now available here: http:\/\/sites.google.com\/site\/vimcctree\/cctree.txt . Refer to help on building help tags.\r\n\r\n","first_name":"Hari","6":"Hari","last_name":"Rangarajan","7":"Rangarajan","releases":[{"0":"2368","vim_version":"7.0","1":"7.0","script_version":"1.61","2":"1.61","version_comment":"Compatibility patch to allow use with change in xref tag file format as of of ccglue version 0.6.0.\r\n","3":"Compatibility patch to allow use with change in xref tag file format as of of ccglue version 0.6.0.\r\n","package":"cctree.vim","4":"cctree.vim","src_id":"18112","5":"18112","creation_date":"1339358976","6":"1339358976"},{"0":"2368","vim_version":"7.0","1":"7.0","script_version":"1.60","2":"1.60","version_comment":"Performance speed-up for tree depth manipulation using incremental updates.","3":"Performance speed-up for tree depth manipulation using incremental updates.","package":"cctree.vim","4":"cctree.vim","src_id":"16077","5":"16077","creation_date":"1310665255","6":"1310665255"},{"0":"2368","vim_version":"7.0","1":"7.0","script_version":"1.55","2":"1.55","version_comment":"Speed-up syntax highlighting (Note: To export to HTML, run TOhtml command on cctree window copy to get complete highlighted call-tree) \r\n","3":"Speed-up syntax highlighting (Note: To export to HTML, run TOhtml command on cctree window copy to get complete highlighted call-tree) \r\n","package":"cctree.vim","4":"cctree.vim","src_id":"15941","5":"15941","creation_date":"1308611520","6":"1308611520"},{"0":"2368","vim_version":"7.0","1":"7.0","script_version":"1.53","2":"1.53","version_comment":"1. Fix bugs related to database append, xrefdb load","3":"1. Fix bugs related to database append, xrefdb load","package":"cctree.vim","4":"cctree.vim","src_id":"15920","5":"15920","creation_date":"1308332427","6":"1308332427"},{"0":"2368","vim_version":"7.0","1":"7.0","script_version":"1.51","2":"1.51","version_comment":"Robust error reporting when external utils (split\/cat) fail.","3":"Robust error reporting when external utils (split\/cat) fail.","package":"cctree.vim","4":"cctree.vim","src_id":"15668","5":"15668","creation_date":"1305738939","6":"1305738939"},{"0":"2368","vim_version":"7.0","1":"7.0","script_version":"1.50","2":"1.50","version_comment":"Supports cross-referencing  of global variables, enums, typedefs, and macros.","3":"Supports cross-referencing  of global variables, enums, typedefs, and macros.","package":"cctree.vim","4":"cctree.vim","src_id":"15625","5":"15625","creation_date":"1305072378","6":"1305072378"},{"0":"2368","vim_version":"7.0","1":"7.0","script_version":"1.40","2":"1.40","version_comment":"Maintain order of function calls during forward traces.","3":"Maintain order of function calls during forward traces.","package":"cctree.vim","4":"cctree.vim","src_id":"15507","5":"15507","creation_date":"1303521296","6":"1303521296"},{"0":"2368","vim_version":"7.0","1":"7.0","script_version":"1.39","2":"1.39","version_comment":"Add support for (+conceal) feature. \r\n\r\n","3":"Add support for (+conceal) feature. \r\n\r\n","package":"cctree.vim","4":"cctree.vim","src_id":"15489","5":"15489","creation_date":"1303322777","6":"1303322777"},{"0":"2368","vim_version":"7.0","1":"7.0","script_version":"1.33","2":"1.33","version_comment":"1. Load and trace CCTree native XRefDb directly from disk ( :CCTreeLoadXRefDBFromDisk )\r\n(Note: Earlier saved xref db's had an issue with tabs in the tag file; its probably better to  use xref db's generated by version 1.33).\r\n2. Fix AppendDB command when 'ignorecase' is set.\r\n","3":"1. Load and trace CCTree native XRefDb directly from disk ( :CCTreeLoadXRefDBFromDisk )\r\n(Note: Earlier saved xref db's had an issue with tabs in the tag file; its probably better to  use xref db's generated by version 1.33).\r\n2. Fix AppendDB command when 'ignorecase' is set.\r\n","package":"cctree.vim","4":"cctree.vim","src_id":"15404","5":"15404","creation_date":"1302125281","6":"1302125281"},{"0":"2368","vim_version":"7.0","1":"7.0","script_version":"1.26","2":"1.26","version_comment":"1. Fix macro cross-referencing limitation\r\n2. Correct native xref file format\r\n","3":"1. Fix macro cross-referencing limitation\r\n2. Correct native xref file format\r\n","package":"cctree.vim","4":"cctree.vim","src_id":"15329","5":"15329","creation_date":"1301411074","6":"1301411074"},{"0":"2368","vim_version":"7.0","1":"7.0","script_version":"1.21","2":"1.21","version_comment":"1. Support serialization of loaded cscope databases (for faster loading)","3":"1. Support serialization of loaded cscope databases (for faster loading)","package":"cctree.vim","4":"cctree.vim","src_id":"15272","5":"15272","creation_date":"1300749418","6":"1300749418"},{"0":"2368","vim_version":"7.0","1":"7.0","script_version":"1.07","2":"1.07","version_comment":" 1. Fix new keymaps incorrectly applied to buffer\r\n 2. CCTreeOptsToggle command for toggling options\r\n","3":" 1. Fix new keymaps incorrectly applied to buffer\r\n 2. CCTreeOptsToggle command for toggling options\r\n","package":"cctree.vim","4":"cctree.vim","src_id":"15185","5":"15185","creation_date":"1299719345","6":"1299719345"},{"0":"2368","vim_version":"7.0","1":"7.0","script_version":"1.04","2":"1.04","version_comment":"1. Customization for key mappings\r\n2. Dynamic configuration of UI variables\r\n3. Folding long call-trees to show current path dynamically","3":"1. Customization for key mappings\r\n2. Dynamic configuration of UI variables\r\n3. Folding long call-trees to show current path dynamically","package":"cctree.vim","4":"cctree.vim","src_id":"15170","5":"15170","creation_date":"1299471730","6":"1299471730"},{"0":"2368","vim_version":"7.0","1":"7.0","script_version":"1.00","2":"1.00","version_comment":"1. Staging release for upcoming features\r\n          - Complete refactoring of code to take advantage of VimScript's OO features\r\n2. Faster decompression of symbols\r\n3. Display related changes\r\n          - Use of unicode symbols for tree\r\n4. Bugfixes related to multi-database loading","3":"1. Staging release for upcoming features\r\n          - Complete refactoring of code to take advantage of VimScript's OO features\r\n2. Faster decompression of symbols\r\n3. Display related changes\r\n          - Use of unicode symbols for tree\r\n4. Bugfixes related to multi-database loading","package":"cctree.vim","4":"cctree.vim","src_id":"15155","5":"15155","creation_date":"1299202412","6":"1299202412"},{"0":"2368","vim_version":"7.0","1":"7.0","script_version":"0.90","2":"0.90","version_comment":"1. Support for large database files using external split utility or in-built perl interpreter interface","3":"1. Support for large database files using external split utility or in-built perl interpreter interface","package":"cctree.vim","4":"cctree.vim","src_id":"15043","5":"15043","creation_date":"1298099288","6":"1298099288"},{"0":"2368","vim_version":"7.0","1":"7.0","script_version":"0.85","2":"0.85","version_comment":"Major increase in database loading\/decompression speeds","3":"Major increase in database loading\/decompression speeds","package":"cctree.vim","4":"cctree.vim","src_id":"15005","5":"15005","creation_date":"1297707335","6":"1297707335"},{"0":"2368","vim_version":"7.0","1":"7.0","script_version":"0.80","2":"0.80","version_comment":"Reduce memory usage by removing unused xref symbols\r\nMinor bug fixes","3":"Reduce memory usage by removing unused xref symbols\r\nMinor bug fixes","package":"cctree.vim","4":"cctree.vim","src_id":"14966","5":"14966","creation_date":"1297043736","6":"1297043736"},{"0":"2368","vim_version":"7.0","1":"7.0","script_version":"0.75","2":"0.75","version_comment":"Allow CCTree windows to be \"saved\".\r\nMultiple instances of CCTree preview windows can now exist.\r\nUse \"<Ctrl-\\>y\" or \":CCTreeWindowSaveCopy\" to save the current view.","3":"Allow CCTree windows to be \"saved\".\r\nMultiple instances of CCTree preview windows can now exist.\r\nUse \"<Ctrl-\\>y\" or \":CCTreeWindowSaveCopy\" to save the current view.","package":"cctree.vim","4":"cctree.vim","src_id":"13250","5":"13250","creation_date":"1277614329","6":"1277614329"},{"0":"2368","vim_version":"7.0","1":"7.0","script_version":"0.71","2":"0.71","version_comment":"Obsoletes 0.70 which had a script bug.\r\nAdded support for multiple cscope databases.","3":"Obsoletes 0.70 which had a script bug.\r\nAdded support for multiple cscope databases.","package":"cctree.vim","4":"cctree.vim","src_id":"12989","5":"12989","creation_date":"1273591643","6":"1273591643"},{"0":"2368","vim_version":"7.0","1":"7.0","script_version":"0.65","2":"0.65","version_comment":"Added CCTree preview window toggle function (shortcut: <C-\\>w )\r\n","3":"Added CCTree preview window toggle function (shortcut: <C-\\>w )\r\n","package":"cctree.vim","4":"cctree.vim","src_id":"11005","5":"11005","creation_date":"1247497282","6":"1247497282"},{"0":"2368","vim_version":"7.0","1":"7.0","script_version":".61","2":".61","version_comment":"Bug fix release","3":"Bug fix release","package":"cctree.vim","4":"cctree.vim","src_id":"9730","5":"9730","creation_date":"1230535444","6":"1230535444"},{"0":"2368","vim_version":"7.0","1":"7.0","script_version":"0.60","2":"0.60","version_comment":"Added support for source-file dependency tree","3":"Added support for source-file dependency tree","package":"cctree.vim","4":"cctree.vim","src_id":"9583","5":"9583","creation_date":"1227856736","6":"1227856736"},{"0":"2368","vim_version":"7.0","1":"7.0","script_version":"0.50","2":"0.50","version_comment":"Optimizations for compact memory foot-print and improved compressed-database load speeds","3":"Optimizations for compact memory foot-print and improved compressed-database load speeds","package":"cctree.vim","4":"cctree.vim","src_id":"9371","5":"9371","creation_date":"1224383436","6":"1224383436"},{"0":"2368","vim_version":"7.0","1":"7.0","script_version":"0.41","2":"0.41","version_comment":"(Minor fix) Compressed cscope databases will load incorrectly if encoding is not 8-bit","3":"(Minor fix) Compressed cscope databases will load incorrectly if encoding is not 8-bit","package":"cctree.vim","4":"cctree.vim","src_id":"9317","5":"9317","creation_date":"1223353310","6":"1223353310"},{"0":"2368","vim_version":"7.0","1":"7.0","script_version":"0.4","2":"0.4","version_comment":"1. Rewrite of \"tree-display\" code\r\n2. New syntax hightlighting\r\n3. Dynamic highlighting for call-trees\r\n4. Support for new window modes (vertical, horizontal)  \r\n5. New display format option for compact or wide call-trees\r\n","3":"1. Rewrite of \"tree-display\" code\r\n2. New syntax hightlighting\r\n3. Dynamic highlighting for call-trees\r\n4. Support for new window modes (vertical, horizontal)  \r\n5. New display format option for compact or wide call-trees\r\n","package":"cctree.vim","4":"cctree.vim","src_id":"9307","5":"9307","creation_date":"1223147791","6":"1223147791"},{"0":"2368","vim_version":"7.0","1":"7.0","script_version":"0.3","2":"0.3","version_comment":"1. Support compressed cscope databases\r\n2. Display window related bugs fixed\r\n3. More intuitive display and folding capabilities","3":"1. Support compressed cscope databases\r\n2. Display window related bugs fixed\r\n3. More intuitive display and folding capabilities","package":"cctree.vim","4":"cctree.vim","src_id":"9273","5":"9273","creation_date":"1222130270","6":"1222130270"},{"0":"2368","vim_version":"7.0","1":"7.0","script_version":"0.2","2":"0.2","version_comment":"Patch from Yegappan Lakshmanan\r\n1. Support for using the plugin in Vi-compatible mode.\r\n2. Filtering out unwanted lines before processing the db.\r\n3. Command-line completion for the commands.\r\n4. Using the cscope db from any directory.\r\n\r\n(Disables perl interface; native VIM database loads are very fast, thanks to\r\nfix #2)\r\n\r\n","3":"Patch from Yegappan Lakshmanan\r\n1. Support for using the plugin in Vi-compatible mode.\r\n2. Filtering out unwanted lines before processing the db.\r\n3. Command-line completion for the commands.\r\n4. Using the cscope db from any directory.\r\n\r\n(Disables perl interface; native VIM database loads are very fast, thanks to\r\nfix #2)\r\n\r\n","package":"cctree.vim","4":"cctree.vim","src_id":"9245","5":"9245","creation_date":"1221258532","6":"1221258532"},{"0":"2368","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"cctree.vim","4":"cctree.vim","src_id":"9216","5":"9216","creation_date":"1220392512","6":"1220392512"}]},"2367":{"script_id":"2367","0":"2367","script_name":"darkbone.vim","1":"darkbone.vim","script_type":"color scheme","2":"color scheme","summary":"This is a dark background color scheme for the GUI.","3":"This is a dark background color scheme for the GUI.","description":"This is a dark background color scheme for the GUI.\r\nScreenshot at http:\/\/jstap.web.fc2.com\/darkbone.html","4":"This is a dark background color scheme for the GUI.\r\nScreenshot at http:\/\/jstap.web.fc2.com\/darkbone.html","install_details":"Put it in one of your colors directories.\r\nThen, just do :colorscheme darkbone","5":"Put it in one of your colors directories.\r\nThen, just do :colorscheme darkbone","first_name":"Kojo","6":"Kojo","last_name":"Sugita","7":"Sugita","releases":[{"0":"2367","vim_version":"7.0","1":"7.0","script_version":"1.2","2":"1.2","version_comment":"Added \"CursorColumn\"","3":"Added \"CursorColumn\"","package":"darkbone.vim","4":"darkbone.vim","src_id":"10980","5":"10980","creation_date":"1247148639","6":"1247148639"},{"0":"2367","vim_version":"7.0","1":"7.0","script_version":"1.1","2":"1.1","version_comment":"Added \"CursorLine\"","3":"Added \"CursorLine\"","package":"darkbone.vim","4":"darkbone.vim","src_id":"9537","5":"9537","creation_date":"1227286602","6":"1227286602"},{"0":"2367","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"darkbone.vim","4":"darkbone.vim","src_id":"9214","5":"9214","creation_date":"1220333379","6":"1220333379"}]},"2366":{"script_id":"2366","0":"2366","script_name":"vcsc.py","1":"vcsc.py","script_type":"utility","2":"utility","summary":"Convert a GUI only vim colorscheme file to a gui\/256xterm compatible version","3":"Convert a GUI only vim colorscheme file to a gui\/256xterm compatible version","description":"There are may existing colorscheme is GUI only.\r\n\r\nThis script can convert a GUI only colorscheme to a 256xterm compatible version.","4":"There are may existing colorscheme is GUI only.\r\n\r\nThis script can convert a GUI only colorscheme to a 256xterm compatible version.","install_details":"","5":"","first_name":"Kanru","6":"Kanru","last_name":"Chen","7":"Chen","releases":[{"0":"2366","vim_version":"6.0","1":"6.0","script_version":"0.01","2":"0.01","version_comment":"Initial upload","3":"Initial upload","package":"vcsc.py","4":"vcsc.py","src_id":"9207","5":"9207","creation_date":"1220251709","6":"1220251709"}]},"2365":{"script_id":"2365","0":"2365","script_name":"ScopeVerilog","1":"ScopeVerilog","script_type":"utility","2":"utility","summary":"allows you to know the curent scope from the info.txt file created by veratags","3":"allows you to know the curent scope from the info.txt file created by veratags","description":"Veratags is a cool utility(available at http:\/\/webpages.charter.net\/jeffkoehler\/jeffkoehler_com\/tools\/veratags\/veratags.html)\r\nIt can create an ascii hierachy of ur design and creates tag for the verilog files as well.\r\nUse this script(hierarchy.vim) to know the current scope (based on where ur cursor is) in the \r\ninfo.txt file\r\n\r\nYou may want set ur status line to\r\nset statusline=%{Verilog_get_hierarchy()}\r\n\r\nPlease update the file as per ur convenience, I am new to vim programming so might have done a buggy coding","4":"Veratags is a cool utility(available at http:\/\/webpages.charter.net\/jeffkoehler\/jeffkoehler_com\/tools\/veratags\/veratags.html)\r\nIt can create an ascii hierachy of ur design and creates tag for the verilog files as well.\r\nUse this script(hierarchy.vim) to know the current scope (based on where ur cursor is) in the \r\ninfo.txt file\r\n\r\nYou may want set ur status line to\r\nset statusline=%{Verilog_get_hierarchy()}\r\n\r\nPlease update the file as per ur convenience, I am new to vim programming so might have done a buggy coding","install_details":"just copy to ur plugin directory","5":"just copy to ur plugin directory","first_name":"Pushkar","6":"Pushkar","last_name":"Sareen","7":"Sareen","releases":[{"0":"2365","vim_version":"5.7","1":"5.7","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"hierarchy.vim","4":"hierarchy.vim","src_id":"9205","5":"9205","creation_date":"1220229258","6":"1220229258"}]},"2364":{"script_id":"2364","0":"2364","script_name":"autoincludex.vim","1":"autoincludex.vim","script_type":"utility","2":"utility","summary":"This script allows automatically insert statements like #include or import","3":"This script allows automatically insert statements like #include or import","description":"Place the cursor on the type you need to include. If it is your class,\r\nfor example MyClass, enter in Normal mode:\r\n       :call AutoIncludeCC()\r\nThe string #include \"myclass.h\" will be inserted in file.\r\nFor type from library, for example STL, enter:\r\n       :call AutoIncludeLib(\"stl\")\r\n At first time you well be prompted to enter the correct header. You\r\nshould enter full text for include statement, i.e. with < >. In next\r\ntime this header will be inserted automatically even after reloading of   vim.\r\nYou can also place the special marks into file. For you types this is\r\nthe \"project headers\". In this case #include will be inserted after\r\nline with this text:\r\n   \/\/project headers\r\n   #include \"myclass.h\"\r\nFor type from the libraries this text is the \"libname headers\", where libname\r\nis name of library:\r\n   \/\/stl headers\r\n   #include <vector>\r\n\r\n   \/\/wx headers\r\n   #include <wx\/menu.h>\r\n\r\n Of course, you can create map for calling of this function:\r\nmap ;; :call AutoIncludeCC()<cr>\r\nmap ;;w :call AutoIncludeLib(\"wx\")<cr>","4":"Place the cursor on the type you need to include. If it is your class,\r\nfor example MyClass, enter in Normal mode:\r\n       :call AutoIncludeCC()\r\nThe string #include \"myclass.h\" will be inserted in file.\r\nFor type from library, for example STL, enter:\r\n       :call AutoIncludeLib(\"stl\")\r\n At first time you well be prompted to enter the correct header. You\r\nshould enter full text for include statement, i.e. with < >. In next\r\ntime this header will be inserted automatically even after reloading of   vim.\r\nYou can also place the special marks into file. For you types this is\r\nthe \"project headers\". In this case #include will be inserted after\r\nline with this text:\r\n   \/\/project headers\r\n   #include \"myclass.h\"\r\nFor type from the libraries this text is the \"libname headers\", where libname\r\nis name of library:\r\n   \/\/stl headers\r\n   #include <vector>\r\n\r\n   \/\/wx headers\r\n   #include <wx\/menu.h>\r\n\r\n Of course, you can create map for calling of this function:\r\nmap ;; :call AutoIncludeCC()<cr>\r\nmap ;;w :call AutoIncludeLib(\"wx\")<cr>","install_details":"Put autoincludex.vim file in your ~\/.vim\/plugin. Create directory \r\n ~\/.vim\/includesdb where databases of headers will be saved. You can use\r\n any directory, but in this case you should set the variable\r\n g:dict_inc_db_path in correct value.\r\n","5":"Put autoincludex.vim file in your ~\/.vim\/plugin. Create directory \r\n ~\/.vim\/includesdb where databases of headers will be saved. You can use\r\n any directory, but in this case you should set the variable\r\n g:dict_inc_db_path in correct value.\r\n","first_name":"Vadim","6":"Vadim","last_name":"Khohlov","7":"Khohlov","releases":[{"0":"2364","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"- bugfix of processing headers with \\ and \/\r\n- Added options g:ainc_header_prefix and g:ainc_header_suffix. This options allows you to use script for other languages, such as php, python and so on. See description in comments.","3":"- bugfix of processing headers with \\ and \/\r\n- Added options g:ainc_header_prefix and g:ainc_header_suffix. This options allows you to use script for other languages, such as php, python and so on. See description in comments.","package":"autoincludex.vim","4":"autoincludex.vim","src_id":"9210","5":"9210","creation_date":"1220275773","6":"1220275773"},{"0":"2364","vim_version":"6.0","1":"6.0","script_version":"0.9","2":"0.9","version_comment":"Initial upload","3":"Initial upload","package":"autoincludex.vim","4":"autoincludex.vim","src_id":"9202","5":"9202","creation_date":"1220190865","6":"1220190865"}]},"2363":{"script_id":"2363","0":"2363","script_name":"vimxmms2","1":"vimxmms2","script_type":"utility","2":"utility","summary":"An XMMS2 client for Vim.","3":"An XMMS2 client for Vim.","description":"This script will not be updated anymore. Please see vimscript #2369.\r\n\r\nRequire:\r\n    vim with +python support.\r\n    xmms2 with the python interface.\r\n\r\nUsage:\r\n    Using <leader>x to toogle the play window.\r\n\r\n    Also the following keyshorts are avaiable. Most key maps start with\r\n    c(Contrl) or l(playList).\r\n\r\n      <space>    Play the song under cursor.\r\n      <cr>       Same as <space>.\r\n      cs         Stop.\r\n      cp         Pause.\r\n      cr         Select a repeat mode, repeat one track or all.\r\n      -          Decrease volume.\r\n      =          Increase volume.\r\n      r          Refresh window manually.\r\n      la         Add a file or directory to playlist.\r\n      lc         Clear the playlist.\r\n      ld         Remove the song under cursor from current playlist.\r\n      lf         Shuffer the list.\r\n      ll         Load a playlist.\r\n      ln         Create a new playlist, and save current contents to it.\r\n      ls         Sort the playlist, by artist, title or filename.\r\n\r\nCustomize:\r\n    Specify the id3's encoding. For example:\r\n        let g:xmms_id3_encoding=\"gbk\"\r\n\r\n    Specify the play window's width:\r\n        let g:xmms_window_width=30\r\n\r\n    Specify the playlist format, default is \"%artist - %title\", %album is also avaiable.\r\n        let g:xmms_playlist_format=\"%title\"\r\n\r\nTips:\r\n    When adding music file or directory, you can use Ctrl-D to show all \r\n    candidates. Also, you can use arrow keys to navigate the historys.\r\n\r\nLeave your comments in following link, or just mail me. :)\r\nhttp:\/\/danran.72pines.com\/vimxmms2\r\n","4":"This script will not be updated anymore. Please see vimscript #2369.\r\n\r\nRequire:\r\n    vim with +python support.\r\n    xmms2 with the python interface.\r\n\r\nUsage:\r\n    Using <leader>x to toogle the play window.\r\n\r\n    Also the following keyshorts are avaiable. Most key maps start with\r\n    c(Contrl) or l(playList).\r\n\r\n      <space>    Play the song under cursor.\r\n      <cr>       Same as <space>.\r\n      cs         Stop.\r\n      cp         Pause.\r\n      cr         Select a repeat mode, repeat one track or all.\r\n      -          Decrease volume.\r\n      =          Increase volume.\r\n      r          Refresh window manually.\r\n      la         Add a file or directory to playlist.\r\n      lc         Clear the playlist.\r\n      ld         Remove the song under cursor from current playlist.\r\n      lf         Shuffer the list.\r\n      ll         Load a playlist.\r\n      ln         Create a new playlist, and save current contents to it.\r\n      ls         Sort the playlist, by artist, title or filename.\r\n\r\nCustomize:\r\n    Specify the id3's encoding. For example:\r\n        let g:xmms_id3_encoding=\"gbk\"\r\n\r\n    Specify the play window's width:\r\n        let g:xmms_window_width=30\r\n\r\n    Specify the playlist format, default is \"%artist - %title\", %album is also avaiable.\r\n        let g:xmms_playlist_format=\"%title\"\r\n\r\nTips:\r\n    When adding music file or directory, you can use Ctrl-D to show all \r\n    candidates. Also, you can use arrow keys to navigate the historys.\r\n\r\nLeave your comments in following link, or just mail me. :)\r\nhttp:\/\/danran.72pines.com\/vimxmms2\r\n","install_details":"Putting following lines into your .vimrc\r\n    if has('python')\r\n        pyf \/path\/to\/vimxmms2.py\r\n    endif\r\n\r\n    nmap <silent> <leader>x :py xmms_toggle()<cr>","5":"Putting following lines into your .vimrc\r\n    if has('python')\r\n        pyf \/path\/to\/vimxmms2.py\r\n    endif\r\n\r\n    nmap <silent> <leader>x :py xmms_toggle()<cr>","first_name":"Xin","6":"Xin","last_name":"Wang","7":"Wang","releases":[{"0":"2363","vim_version":"7.0","1":"7.0","script_version":"0.4","2":"0.4","version_comment":"- Auto refresh play window using CursorHold event.\r\n- Now user can customize the playlist format.\r\n","3":"- Auto refresh play window using CursorHold event.\r\n- Now user can customize the playlist format.\r\n","package":"vimxmms2.py","4":"vimxmms2.py","src_id":"9211","5":"9211","creation_date":"1220324580","6":"1220324580"},{"0":"2363","vim_version":"7.0","1":"7.0","script_version":"0.3","2":"0.3","version_comment":"- Add basic playlist save and load support.\r\n- Show current playlist and volume in statusline.\r\n- Add shuffle, repeat command.\r\n- Add playlist sort command.\r\n- The key map are mostly redefined.\r\n","3":"- Add basic playlist save and load support.\r\n- Show current playlist and volume in statusline.\r\n- Add shuffle, repeat command.\r\n- Add playlist sort command.\r\n- The key map are mostly redefined.\r\n","package":"vimxmms2.py","4":"vimxmms2.py","src_id":"9206","5":"9206","creation_date":"1220248258","6":"1220248258"},{"0":"2363","vim_version":"7.0","1":"7.0","script_version":"0.2","2":"0.2","version_comment":"- Change from XMMSSync to XMMS to gain more control.\r\n- Fix a bug when play the last song in the playlist, remove any entry will cause an out of range error.\r\n- When encouter encoding or decoding error of id3, use file name instead.\r\n","3":"- Change from XMMSSync to XMMS to gain more control.\r\n- Fix a bug when play the last song in the playlist, remove any entry will cause an out of range error.\r\n- When encouter encoding or decoding error of id3, use file name instead.\r\n","package":"vimxmms2.py","4":"vimxmms2.py","src_id":"9204","5":"9204","creation_date":"1220201463","6":"1220201463"},{"0":"2363","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"vimxmms2.py","4":"vimxmms2.py","src_id":"9198","5":"9198","creation_date":"1220131266","6":"1220131266"}]},"2362":{"script_id":"2362","0":"2362","script_name":"simplewhite.vim","1":"simplewhite.vim","script_type":"color scheme","2":"color scheme","summary":"A light background color scheme","3":"A light background color scheme","description":"This is a color scheme for light background for the GUI.\r\nIt is based on the louver color scheme(vimscript#2360).\r\n\r\nScreenshot at http:\/\/jstap.web.fc2.com\/simplewhite.html","4":"This is a color scheme for light background for the GUI.\r\nIt is based on the louver color scheme(vimscript#2360).\r\n\r\nScreenshot at http:\/\/jstap.web.fc2.com\/simplewhite.html","install_details":"Put it in one of your colors directories.\r\nThen, just do :colorscheme simplewhite.","5":"Put it in one of your colors directories.\r\nThen, just do :colorscheme simplewhite.","first_name":"Kojo","6":"Kojo","last_name":"Sugita","7":"Sugita","releases":[{"0":"2362","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"simplewhite.vim","4":"simplewhite.vim","src_id":"9193","5":"9193","creation_date":"1219985907","6":"1219985907"}]},"2361":{"script_id":"2361","0":"2361","script_name":"diff_navigator","1":"diff_navigator","script_type":"ftplugin","2":"ftplugin","summary":"Helps navigation in unified diffs","3":"Helps navigation in unified diffs","description":"*** IMPORTANT ***: the script is no longer maintained here. It has been taken over by Matěj Cepl and is now maintained at\r\nhttps:\/\/gitlab.com\/mcepl\/vim-diff_navigator . Please get the script from there.\r\n\r\nSimple script that helps navigation in unified diffs (patches).\r\n\r\nTogether with external utility filterdiff (part of patchutils) it provides DiffAnnotate command that tags all hunks with their number and name of the changed file.\r\n\r\nDiffShowHunk command displays annotation of the current hunk (useful when inside a big hunk).\r\n\r\nDiffNextFile and DiffPrevFile command can be used to quickly skip to next\/previous changed file.\r\n\r\nDiffNextHunk and DiffPrevHunk quickly skips to next\/previous hunk.\r\n\r\nDiffSplitHunk splits the hunk under the cursor, fixing previous hunk header.\r\n\r\nDiffDeleteHunk deletes the hunk under the cursor and fixes all hunks to have correct headers.","4":"*** IMPORTANT ***: the script is no longer maintained here. It has been taken over by Matěj Cepl and is now maintained at\r\nhttps:\/\/gitlab.com\/mcepl\/vim-diff_navigator . Please get the script from there.\r\n\r\nSimple script that helps navigation in unified diffs (patches).\r\n\r\nTogether with external utility filterdiff (part of patchutils) it provides DiffAnnotate command that tags all hunks with their number and name of the changed file.\r\n\r\nDiffShowHunk command displays annotation of the current hunk (useful when inside a big hunk).\r\n\r\nDiffNextFile and DiffPrevFile command can be used to quickly skip to next\/previous changed file.\r\n\r\nDiffNextHunk and DiffPrevHunk quickly skips to next\/previous hunk.\r\n\r\nDiffSplitHunk splits the hunk under the cursor, fixing previous hunk header.\r\n\r\nDiffDeleteHunk deletes the hunk under the cursor and fixes all hunks to have correct headers.","install_details":"git clone  https:\/\/gitlab.com\/mcepl\/vim-diff_navigator.git (vim-pathogen [1] is recommended)\r\n\r\nAlso make sure that filterdiff (should be in patchutils package) program is installed somewhere in your $PATH.\r\n\r\n[1] https:\/\/github.com\/tpope\/vim-pathogen","5":"git clone  https:\/\/gitlab.com\/mcepl\/vim-diff_navigator.git (vim-pathogen [1] is recommended)\r\n\r\nAlso make sure that filterdiff (should be in patchutils package) program is installed somewhere in your $PATH.\r\n\r\n[1] https:\/\/github.com\/tpope\/vim-pathogen","first_name":"Petr","6":"Petr","last_name":"Uzel","7":"Uzel","releases":[{"0":"2361","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"diff_navigator.vim","4":"diff_navigator.vim","src_id":"9184","5":"9184","creation_date":"1219893113","6":"1219893113"}]},"2360":{"script_id":"2360","0":"2360","script_name":"louver.vim","1":"louver.vim","script_type":"color scheme","2":"color scheme","summary":"A light background color scheme","3":"A light background color scheme","description":"A light background color scheme for the GUI. .\r\nScreenshot at http:\/\/jstap.web.fc2.com\/louver.html","4":"A light background color scheme for the GUI. .\r\nScreenshot at http:\/\/jstap.web.fc2.com\/louver.html","install_details":"Put it in one of your colors directories.\r\nThen, just do :colorscheme louver","5":"Put it in one of your colors directories.\r\nThen, just do :colorscheme louver","first_name":"Kojo","6":"Kojo","last_name":"Sugita","7":"Sugita","releases":[{"0":"2360","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"louver.vim","4":"louver.vim","src_id":"9181","5":"9181","creation_date":"1219818528","6":"1219818528"}]},"2359":{"script_id":"2359","0":"2359","script_name":"clue","1":"clue","script_type":"color scheme","2":"color scheme","summary":"a colour scheme with a blue background","3":"a colour scheme with a blue background","description":"Clue is a redesign of the \"blue\" colour scheme -- hence the name ;) -- with many colours changed and several new syntax categories added.\r\nThe cterm version uses a smaller number of colours and has a black background.","4":"Clue is a redesign of the \"blue\" colour scheme -- hence the name ;) -- with many colours changed and several new syntax categories added.\r\nThe cterm version uses a smaller number of colours and has a black background.","install_details":"Put the file into your \"colors\" directory.","5":"Put the file into your \"colors\" directory.","first_name":"Boyko","6":"Boyko","last_name":"Bantchev","7":"Bantchev","releases":[{"0":"2359","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"clue.vim","4":"clue.vim","src_id":"9179","5":"9179","creation_date":"1219817071","6":"1219817071"}]},"2358":{"script_id":"2358","0":"2358","script_name":"tags for std c++ (STL, streams, ...)","1":"tags for std c++ (STL, streams, ...)","script_type":"utility","2":"utility","summary":"Modified libstdc++ headers for use with ctags","3":"Modified libstdc++ headers for use with ctags","description":"This is a slightly modified version of the libstdc++ headers which can be used with ctags. STL, streams and other standard cpp stuff can now be completed with omnicpp complete:\r\nhttp:\/\/www.vim.org\/scripts\/script.php?script_id=1520","4":"This is a slightly modified version of the libstdc++ headers which can be used with ctags. STL, streams and other standard cpp stuff can now be completed with omnicpp complete:\r\nhttp:\/\/www.vim.org\/scripts\/script.php?script_id=1520","install_details":"1. unpack\r\n\r\n2. run\r\n$ ctags -R --c++-kinds=+p --fields=+iaS --extra=+q --language-force=C++ cpp_src\r\n$ mv tags cpp # or whatever\r\n\r\n3. In Vim:\r\nset tags+=\/my\/path\/to\/tags\/cpp\r\n\r\n---\r\n\r\nA more detailed tutorial in getting c++ code completion to work can be found in the vim wiki:\r\nhttp:\/\/vim.wikia.com\/wiki\/C++_code_completion","5":"1. unpack\r\n\r\n2. run\r\n$ ctags -R --c++-kinds=+p --fields=+iaS --extra=+q --language-force=C++ cpp_src\r\n$ mv tags cpp # or whatever\r\n\r\n3. In Vim:\r\nset tags+=\/my\/path\/to\/tags\/cpp\r\n\r\n---\r\n\r\nA more detailed tutorial in getting c++ code completion to work can be found in the vim wiki:\r\nhttp:\/\/vim.wikia.com\/wiki\/C++_code_completion","first_name":"Roland","6":"Roland","last_name":"Lei\u00c3\u009fa","7":"Lei\u00c3\u009fa","releases":[{"0":"2358","vim_version":"7.0","1":"7.0","script_version":"0.9","2":"0.9","version_comment":"Initial upload","3":"Initial upload","package":"cpp_src.tar.bz2","4":"cpp_src.tar.bz2","src_id":"9178","5":"9178","creation_date":"1219772047","6":"1219772047"}]},"2357":{"script_id":"2357","0":"2357","script_name":"Nekthuth","1":"Nekthuth","script_type":"utility","2":"utility","summary":"Connection with a Lisp","3":"Connection with a Lisp","description":"Nekthuth is simultaneously a plugin for vim and library for Comon Lisp that allows developers to interact with a running interpreter from inside their editor.\r\n\r\nFeatures include:\r\n\r\n    * Form evaluation\r\n    * Tab completion\r\n    * Quick macroexpansion\r\n    * Extension to syntax highlighting\r\n    * Basic Debugger\r\n    * On the fly hyperspec rendering inside the vim window\r\n    * Extensible plugin architecture\r\n    * Connect to a remote lisp or boot one from inside vim\r\n    * Find and open source location of symbols under cursor\r\n\r\nCurrent limitations include:\r\n\r\n    * Requires SBCL with threads\r\n    * Requires vim > 7.0 with +python3\r\n    * Requires asdf\r\n\r\nSee http:\/\/nekthuth.com for more information","4":"Nekthuth is simultaneously a plugin for vim and library for Comon Lisp that allows developers to interact with a running interpreter from inside their editor.\r\n\r\nFeatures include:\r\n\r\n    * Form evaluation\r\n    * Tab completion\r\n    * Quick macroexpansion\r\n    * Extension to syntax highlighting\r\n    * Basic Debugger\r\n    * On the fly hyperspec rendering inside the vim window\r\n    * Extensible plugin architecture\r\n    * Connect to a remote lisp or boot one from inside vim\r\n    * Find and open source location of symbols under cursor\r\n\r\nCurrent limitations include:\r\n\r\n    * Requires SBCL with threads\r\n    * Requires vim > 7.0 with +python3\r\n    * Requires asdf\r\n\r\nSee http:\/\/nekthuth.com for more information","install_details":"See http:\/\/nekthuth.com\/doc.html#starting\r\n\r\nYou can optionally follow it's instructions to get the latest version of this plugin, or just get the latest one here.  However, you will need to install an sbcl component using asdf-install (or manually through just asdf).","5":"See http:\/\/nekthuth.com\/doc.html#starting\r\n\r\nYou can optionally follow it's instructions to get the latest version of this plugin, or just get the latest one here.  However, you will need to install an sbcl component using asdf-install (or manually through just asdf).","first_name":"Frank","6":"Frank","last_name":"Duncan","7":"Duncan","releases":[{"0":"2357","vim_version":"7.0","1":"7.0","script_version":"0.4.0","2":"0.4.0","version_comment":"* Added consoles window for subservient windows. Functions that now use console window:\r\n  * Restart Manager\r\n  * Source code lookup\r\n  * Macro expand\r\n  * HyperSpec help\r\n* Created throwaway buffers for transient responses from lisp (currently used by macroexpand). Uses console buffer\r\n* Upgraded vim portion to python3\r\n* HyperSpec lookup no longer uses tags, and is more reliable, fixing bug where reopening help on same subject cleared the screen\r\n* Fixed bugs with closed connections borking the lisp process\r\n* Opening Nekthuth in a new vim tab just reuses the buffer in a new window in this tab, rather than attempting to open a new lisp process\r\n* Made restart manager slightly less horrendous in console window\r\n","3":"* Added consoles window for subservient windows. Functions that now use console window:\r\n  * Restart Manager\r\n  * Source code lookup\r\n  * Macro expand\r\n  * HyperSpec help\r\n* Created throwaway buffers for transient responses from lisp (currently used by macroexpand). Uses console buffer\r\n* Upgraded vim portion to python3\r\n* HyperSpec lookup no longer uses tags, and is more reliable, fixing bug where reopening help on same subject cleared the screen\r\n* Fixed bugs with closed connections borking the lisp process\r\n* Opening Nekthuth in a new vim tab just reuses the buffer in a new window in this tab, rather than attempting to open a new lisp process\r\n* Made restart manager slightly less horrendous in console window\r\n","package":"nekthuth-vim_0.4.0.tar.gz","4":"nekthuth-vim_0.4.0.tar.gz","src_id":"21621","5":"21621","creation_date":"1394989051","6":"1394989051"},{"0":"2357","vim_version":"7.0","1":"7.0","script_version":"0.3.4","2":"0.3.4","version_comment":"    * Fixed some bugs in the connection code for NekthuthRemote.\r\n    * Made it so window splitting is based on how wide your window currently is\r\n    * Added g:nekthuth_updatetime (default 500) - sets how long vim waits when not moving cursor to check","3":"    * Fixed some bugs in the connection code for NekthuthRemote.\r\n    * Made it so window splitting is based on how wide your window currently is\r\n    * Added g:nekthuth_updatetime (default 500) - sets how long vim waits when not moving cursor to check","package":"nekthuth-vim_0.3.4.tar.gz","4":"nekthuth-vim_0.3.4.tar.gz","src_id":"14775","5":"14775","creation_date":"1295281291","6":"1295281291"},{"0":"2357","vim_version":"7.0","1":"7.0","script_version":"0.3.2","2":"0.3.2","version_comment":" * Another bug where mcclim confused vim with syntax additions. Functions with ] or [ in them will no longer show up as highlighted.\r\n * Install.sh in the vim plugin was using the wrong environment variable","3":" * Another bug where mcclim confused vim with syntax additions. Functions with ] or [ in them will no longer show up as highlighted.\r\n * Install.sh in the vim plugin was using the wrong environment variable","package":"nekthuth-vim_0.3.2.tar.gz","4":"nekthuth-vim_0.3.2.tar.gz","src_id":"10981","5":"10981","creation_date":"1247158876","6":"1247158876"},{"0":"2357","vim_version":"7.0","1":"7.0","script_version":"0.3.1","2":"0.3.1","version_comment":"* Fixed a bug where loading up packages that defined symboles such as \\ and ' would cause syntax additions to fail\r\n* Added plugin installation.\r\n* Fixed how the main thread and repl thread share sender data, which should translate into faster bootup times.","3":"* Fixed a bug where loading up packages that defined symboles such as \\ and ' would cause syntax additions to fail\r\n* Added plugin installation.\r\n* Fixed how the main thread and repl thread share sender data, which should translate into faster bootup times.","package":"nekthuth-vim_0.3.1.tar.gz","4":"nekthuth-vim_0.3.1.tar.gz","src_id":"10906","5":"10906","creation_date":"1246136236","6":"1246136236"},{"0":"2357","vim_version":"7.0","1":"7.0","script_version":"0.3","2":"0.3","version_comment":"    * Multiple return value (using values, such as in #'get-decoded-time) prints correctly in buffer\r\n    * Fixed NekthuthInterrupt (0.2 broke it)\r\n    * Function coloring and complete added for *package* functions and transitively used packages\r\n    * Remote connection now checks the version correctly. This may be useful someday.\r\n    * Added #'nekthuth:stop-remote to shut down the remote listener.\r\n    * Find and open source locaton of symbol under cursor.","3":"    * Multiple return value (using values, such as in #'get-decoded-time) prints correctly in buffer\r\n    * Fixed NekthuthInterrupt (0.2 broke it)\r\n    * Function coloring and complete added for *package* functions and transitively used packages\r\n    * Remote connection now checks the version correctly. This may be useful someday.\r\n    * Added #'nekthuth:stop-remote to shut down the remote listener.\r\n    * Find and open source locaton of symbol under cursor.","package":"nekthuth-vim_0.3.tar.gz","4":"nekthuth-vim_0.3.tar.gz","src_id":"10358","5":"10358","creation_date":"1239083900","6":"1239083900"},{"0":"2357","vim_version":"7.0","1":"7.0","script_version":"0.2","2":"0.2","version_comment":"* Remote execution in an already running sbcl instance. See setup in the manual for more information.\r\n* Fixed ClHelp not opening a window upon failure","3":"* Remote execution in an already running sbcl instance. See setup in the manual for more information.\r\n* Fixed ClHelp not opening a window upon failure","package":"nekthuth-vim_0.2.tar.gz","4":"nekthuth-vim_0.2.tar.gz","src_id":"9758","5":"9758","creation_date":"1231123269","6":"1231123269"},{"0":"2357","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"nekthuth-vim_0.1.tar.gz","4":"nekthuth-vim_0.1.tar.gz","src_id":"9173","5":"9173","creation_date":"1219732478","6":"1219732478"}]},"2356":{"script_id":"2356","0":"2356","script_name":"Superior Haskell Interaction Mode (SHIM)","1":"Superior Haskell Interaction Mode (SHIM)","script_type":"utility","2":"utility","summary":"GHCi integration for VIM","3":"GHCi integration for VIM","description":"Superior Haskell Interaction Mode (SHIM) integrates GHCi with VIM, allowing you to quickly load files or individual lines into the interpreter, interact with the interpreter like you would in a normal terminal, and quickly pinpoint error locations. It was inspired by Emacs' Haskell mode.\r\n\r\nThe script uses Ruby to spawn a GHCi process and communicate with it through pipes, reading from VIM and writing the output into a dedicated GHCi window. It is integrated with quickfix to allow you to maintain a list of errors and move among them.\r\n\r\nRequires VIM with Ruby support, Ruby with pty extension (Unix), and GHCi.","4":"Superior Haskell Interaction Mode (SHIM) integrates GHCi with VIM, allowing you to quickly load files or individual lines into the interpreter, interact with the interpreter like you would in a normal terminal, and quickly pinpoint error locations. It was inspired by Emacs' Haskell mode.\r\n\r\nThe script uses Ruby to spawn a GHCi process and communicate with it through pipes, reading from VIM and writing the output into a dedicated GHCi window. It is integrated with quickfix to allow you to maintain a list of errors and move among them.\r\n\r\nRequires VIM with Ruby support, Ruby with pty extension (Unix), and GHCi.","install_details":"Put shim.vim into your VIM plugins directory or source the file manually. That's it.\r\n\r\nYou can map the functions \"GhciFile\", \"GhciRange <range>\", and \"GhciReload\" to key combinations of your preference for faster acess. Take a look at the source file for the options you may want to customize.","5":"Put shim.vim into your VIM plugins directory or source the file manually. That's it.\r\n\r\nYou can map the functions \"GhciFile\", \"GhciRange <range>\", and \"GhciReload\" to key combinations of your preference for faster acess. Take a look at the source file for the options you may want to customize.","first_name":"Lars","6":"Lars","last_name":"Kotthoff","7":"Kotthoff","releases":[{"0":"2356","vim_version":"7.0","1":"7.0","script_version":"0.3.7","2":"0.3.7","version_comment":"Update to work with Ruby versions >1.8.","3":"Update to work with Ruby versions >1.8.","package":"shim.vim","4":"shim.vim","src_id":"20377","5":"20377","creation_date":"1371739213","6":"1371739213"},{"0":"2356","vim_version":"7.0","1":"7.0","script_version":"0.3.6","2":"0.3.6","version_comment":"Work around a bug in more recent versions of Vim where the buffer number can't be determined.","3":"Work around a bug in more recent versions of Vim where the buffer number can't be determined.","package":"shim.vim","4":"shim.vim","src_id":"15004","5":"15004","creation_date":"1297706337","6":"1297706337"},{"0":"2356","vim_version":"7.0","1":"7.0","script_version":"0.3.5","2":"0.3.5","version_comment":"fixed requirements","3":"fixed requirements","package":"shim.vim","4":"shim.vim","src_id":"13472","5":"13472","creation_date":"1280940499","6":"1280940499"},{"0":"2356","vim_version":"7.0","1":"7.0","script_version":"0.3.4","2":"0.3.4","version_comment":"Allowing for digits in module names.","3":"Allowing for digits in module names.","package":"shim.vim","4":"shim.vim","src_id":"11836","5":"11836","creation_date":"1259690902","6":"1259690902"},{"0":"2356","vim_version":"7.0","1":"7.0","script_version":"0.3.3","2":"0.3.3","version_comment":"Fixed a bug in the previous release and exposed GhciInit command to set up the buffer, window, and GHCi.","3":"Fixed a bug in the previous release and exposed GhciInit command to set up the buffer, window, and GHCi.","package":"shim.vim","4":"shim.vim","src_id":"11728","5":"11728","creation_date":"1258207580","6":"1258207580"},{"0":"2356","vim_version":"7.0","1":"7.0","script_version":"0.3.2","2":"0.3.2","version_comment":"Changes to the GHCi arguments are now taken into account when GHCi is reloaded.","3":"Changes to the GHCi arguments are now taken into account when GHCi is reloaded.","package":"shim.vim","4":"shim.vim","src_id":"11675","5":"11675","creation_date":"1257596808","6":"1257596808"},{"0":"2356","vim_version":"7.0","1":"7.0","script_version":"0.3.1","2":"0.3.1","version_comment":"Added option to specify any extra arguments to GHCi.","3":"Added option to specify any extra arguments to GHCi.","package":"shim.vim","4":"shim.vim","src_id":"11061","5":"11061","creation_date":"1248452226","6":"1248452226"},{"0":"2356","vim_version":"7.0","1":"7.0","script_version":"0.3","2":"0.3","version_comment":"SHIM now deals with GHCi having gone away (restarts it) and the ghci buffer not being visible when e.g. loading a file.","3":"SHIM now deals with GHCi having gone away (restarts it) and the ghci buffer not being visible when e.g. loading a file.","package":"shim.vim","4":"shim.vim","src_id":"10419","5":"10419","creation_date":"1240149282","6":"1240149282"},{"0":"2356","vim_version":"7.0","1":"7.0","script_version":"0.2","2":"0.2","version_comment":"Tweaked the regular expression to match the GHCi prompt again and added a function to kill and restart GHCi if something goes wrong.","3":"Tweaked the regular expression to match the GHCi prompt again and added a function to kill and restart GHCi if something goes wrong.","package":"shim.vim","4":"shim.vim","src_id":"10305","5":"10305","creation_date":"1238167832","6":"1238167832"},{"0":"2356","vim_version":"7.0","1":"7.0","script_version":"0.1.1","2":"0.1.1","version_comment":"Changing regular expression to match ghci prompt. For some error messages it would incorrectly match part of the error message as the prompt.","3":"Changing regular expression to match ghci prompt. For some error messages it would incorrectly match part of the error message as the prompt.","package":"shim.vim","4":"shim.vim","src_id":"9711","5":"9711","creation_date":"1229793391","6":"1229793391"},{"0":"2356","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"shim.vim","4":"shim.vim","src_id":"9167","5":"9167","creation_date":"1219643498","6":"1219643498"}]},"2355":{"script_id":"2355","0":"2355","script_name":"textobj-lastpat","1":"textobj-lastpat","script_type":"utility","2":"utility","summary":"Text objects for the last searched pattern","3":"Text objects for the last searched pattern","description":"*textobj-lastpat* is a Vim plugin to provide text objects to select an area\r\n which is matched to |last-pattern|.\r\n\r\n\r\nRequirements:\r\n- Vim 7.2 or later\r\n- |textobj-user| 0.3.5 or later (vimscript#2100)\r\n\r\nLatest version:\r\nhttp:\/\/github.com\/kana\/vim-textobj-lastpat\r\n\r\nDocument in HTML format:\r\nhttp:\/\/kana.github.com\/config\/vim\/textobj-lastpat.html","4":"*textobj-lastpat* is a Vim plugin to provide text objects to select an area\r\n which is matched to |last-pattern|.\r\n\r\n\r\nRequirements:\r\n- Vim 7.2 or later\r\n- |textobj-user| 0.3.5 or later (vimscript#2100)\r\n\r\nLatest version:\r\nhttp:\/\/github.com\/kana\/vim-textobj-lastpat\r\n\r\nDocument in HTML format:\r\nhttp:\/\/kana.github.com\/config\/vim\/textobj-lastpat.html","install_details":"...","5":"...","first_name":"Kana","6":"Kana","last_name":"Natsuno","7":"Natsuno","releases":[{"0":"2355","vim_version":"7.0","1":"7.0","script_version":"0.0.0","2":"0.0.0","version_comment":"Initial upload","3":"Initial upload","package":"vim-textobj-lastpat-0.0.0.zip","4":"vim-textobj-lastpat-0.0.0.zip","src_id":"9166","5":"9166","creation_date":"1219639409","6":"1219639409"}]},"2354":{"script_id":"2354","0":"2354","script_name":"FastGrep","1":"FastGrep","script_type":"utility","2":"utility","summary":"FastGrep for a string using native linux commands in Ruby on Rails projects.","3":"FastGrep for a string using native linux commands in Ruby on Rails projects.","description":"Usage:\r\n  Define a hotkey to call FastGrep() function to search for a string in your project like this:\r\n\r\n  map <F12> :call FastGrep()<CR>\r\n\r\n  The search result will come back in a window that can be customized to be vertical or horizontal\r\n  using this flag:\r\n\r\n  let g:fgVertSplit = 1\r\n\r\n  If is defined, the result window will be vertical, horizontal if not.\r\n\r\n  In the result window can use 'e' and 'r' keys to cycle between results lines and 'q' to close the window.\r\n  If put the cursor over the filename in the result window, can use gF to go to the file and line number.\r\n\r\n  This script used some code burrowed from Specky! [1] and a TextMate bundle [2]\r\n\r\n  Happy coding !\r\n\r\n  [1] http:\/\/vim.sourceforge.net\/scripts\/script.php?script_id=2286\r\n  [2] http:\/\/gist.github.com\/4291\/\r\n","4":"Usage:\r\n  Define a hotkey to call FastGrep() function to search for a string in your project like this:\r\n\r\n  map <F12> :call FastGrep()<CR>\r\n\r\n  The search result will come back in a window that can be customized to be vertical or horizontal\r\n  using this flag:\r\n\r\n  let g:fgVertSplit = 1\r\n\r\n  If is defined, the result window will be vertical, horizontal if not.\r\n\r\n  In the result window can use 'e' and 'r' keys to cycle between results lines and 'q' to close the window.\r\n  If put the cursor over the filename in the result window, can use gF to go to the file and line number.\r\n\r\n  This script used some code burrowed from Specky! [1] and a TextMate bundle [2]\r\n\r\n  Happy coding !\r\n\r\n  [1] http:\/\/vim.sourceforge.net\/scripts\/script.php?script_id=2286\r\n  [2] http:\/\/gist.github.com\/4291\/\r\n","install_details":"For installation untar the package over the .vim directory.\r\n","5":"For installation untar the package over the .vim directory.\r\n","first_name":"Nelson","6":"Nelson","last_name":"Fernandez","7":"Fernandez","releases":[{"0":"2354","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"fastgrep_01.tar.gz","4":"fastgrep_01.tar.gz","src_id":"9161","5":"9161","creation_date":"1219268445","6":"1219268445"}]},"2353":{"script_id":"2353","0":"2353","script_name":"stlrefvim","1":"stlrefvim","script_type":"utility","2":"utility","summary":"A C++ Standard Template Library reference manual","3":"A C++ Standard Template Library reference manual","description":"This plugin aims to provide a reference manual for the C++ standard template library (STL).  Based heavily off of the well-regarded SGI-STL documentation, this script puts the power of this documentation into your vim workflow.  Lookups can easily be done with user-configurable key mappings.\r\n\r\nFor example, in the expression:\r\n    std::for_each(start, end, PrintFunc)\r\nplace the cursor over for_each and type <Leader>tr to go to documentation for this function.  Type <Leader>te to go to an example that uses this function.\r\n\r\nMany thanks must go to Christian Habermann's for his crefvim plugin (http:\/\/www.vim.org\/scripts\/script.php?script_id=614) that formed the basis of and was the inspiration for this plugin.","4":"This plugin aims to provide a reference manual for the C++ standard template library (STL).  Based heavily off of the well-regarded SGI-STL documentation, this script puts the power of this documentation into your vim workflow.  Lookups can easily be done with user-configurable key mappings.\r\n\r\nFor example, in the expression:\r\n    std::for_each(start, end, PrintFunc)\r\nplace the cursor over for_each and type <Leader>tr to go to documentation for this function.  Type <Leader>te to go to an example that uses this function.\r\n\r\nMany thanks must go to Christian Habermann's for his crefvim plugin (http:\/\/www.vim.org\/scripts\/script.php?script_id=614) that formed the basis of and was the inspiration for this plugin.","install_details":"stlrefvim consists of two files: the script 'stlrefvim.vim' and its documentation 'stlrefvim.txt'.\r\n\r\nTo use the script copy it into your local plugin-directory\r\n  Unix:    ~\/.vim\/plugin\r\n  Windows: c:\\vimfiles\\plugin\r\n\r\nYou have to add this documentation and the STL-reference to Vim's help system. To do this, copy 'stlrefvim.txt' to your local doc-directory:\r\n  Unix:    ~\/.vim\/doc\r\n  Windows: c:\\vimfiles\\doc\r\n\r\nThen start Vim and do:\r\n  :helptags ~\/.vim\/doc   (or :helptags c:\\vimfiles\\doc for Windows)","5":"stlrefvim consists of two files: the script 'stlrefvim.vim' and its documentation 'stlrefvim.txt'.\r\n\r\nTo use the script copy it into your local plugin-directory\r\n  Unix:    ~\/.vim\/plugin\r\n  Windows: c:\\vimfiles\\plugin\r\n\r\nYou have to add this documentation and the STL-reference to Vim's help system. To do this, copy 'stlrefvim.txt' to your local doc-directory:\r\n  Unix:    ~\/.vim\/doc\r\n  Windows: c:\\vimfiles\\doc\r\n\r\nThen start Vim and do:\r\n  :helptags ~\/.vim\/doc   (or :helptags c:\\vimfiles\\doc for Windows)","first_name":"Daniel","6":"Daniel","last_name":"Price","7":"Price","releases":[{"0":"2353","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"stlrefvim.tar.gz","4":"stlrefvim.tar.gz","src_id":"9160","5":"9160","creation_date":"1219262549","6":"1219262549"}]},"2352":{"script_id":"2352","0":"2352","script_name":"wrap.vim","1":"wrap.vim","script_type":"utility","2":"utility","summary":"Word Wrap for Vim","3":"Word Wrap for Vim","description":"Don't download this!\r\n\r\nUse this instead (add these lines to _vimrc):-\r\n\r\n          \"F7 WordProcessorOn\r\n          :map <F7> :set linebreak <CR> :set display+=lastline <CR> :set wrap <CR> :setlocal spell spelllang=en_gb <CR>\r\n          \"F8 WordProcessorOff\r\n          :map <F8> :set nowrap <CR> :set nospell <CR>\r\n\r\nRestart, and to toggle between a decent Word Processor Mode, just press F7 and F8.\r\nNOTE\/ Remember to change spelllang to your local language.\r\n","4":"Don't download this!\r\n\r\nUse this instead (add these lines to _vimrc):-\r\n\r\n          \"F7 WordProcessorOn\r\n          :map <F7> :set linebreak <CR> :set display+=lastline <CR> :set wrap <CR> :setlocal spell spelllang=en_gb <CR>\r\n          \"F8 WordProcessorOff\r\n          :map <F8> :set nowrap <CR> :set nospell <CR>\r\n\r\nRestart, and to toggle between a decent Word Processor Mode, just press F7 and F8.\r\nNOTE\/ Remember to change spelllang to your local language.\r\n","install_details":"","5":"","first_name":"Roy","6":"Roy","last_name":"Mathur","7":"Mathur","releases":[{"0":"2352","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"wrap.vim","4":"wrap.vim","src_id":"9156","5":"9156","creation_date":"1219181691","6":"1219181691"}]},"2351":{"script_id":"2351","0":"2351","script_name":"RltvNmbr.vim","1":"RltvNmbr.vim","script_type":"utility","2":"utility","summary":"Display relative line numbers","3":"Display relative line numbers","description":"The RltvNmbr plugin uses the signs feature to display the line numbering relative to the current line.  A number of commands take [count] arguments for which this is helpful.\r\n\r\n:RltvNmbr\r\n    This command turns relative line numbering on.\r\n\r\n:RltvNmbr!\r\n    This command turns relative line numbering off.\r\n\r\nCAVEAT:\r\n    Your vim must have the signs feature compiled in!  This typically means that your vim has been configured and compiled to be \"huge\":\r\n        configure --with-features=huge\r\n        compile\r\n        install\r\n\r\n\tTo check this:\r\n\t\t:echo has(\"signs\")\r\n\tshould show a \"1\".  Alternatively, look at the output of  :version  and see if you have +signs listed.\r\n\r\n(alpha\/beta version available at http:\/\/www.drchip.org\/astronaut\/vim\/index.html#RLTVNMBR)\r\n","4":"The RltvNmbr plugin uses the signs feature to display the line numbering relative to the current line.  A number of commands take [count] arguments for which this is helpful.\r\n\r\n:RltvNmbr\r\n    This command turns relative line numbering on.\r\n\r\n:RltvNmbr!\r\n    This command turns relative line numbering off.\r\n\r\nCAVEAT:\r\n    Your vim must have the signs feature compiled in!  This typically means that your vim has been configured and compiled to be \"huge\":\r\n        configure --with-features=huge\r\n        compile\r\n        install\r\n\r\n\tTo check this:\r\n\t\t:echo has(\"signs\")\r\n\tshould show a \"1\".  Alternatively, look at the output of  :version  and see if you have +signs listed.\r\n\r\n(alpha\/beta version available at http:\/\/www.drchip.org\/astronaut\/vim\/index.html#RLTVNMBR)\r\n","install_details":"vim RltvNmbr.vba.gz\r\n:so %\r\n\r\n(assuming you have vim 7.1 or later; with vim 7.0, you'll need to upgrade your vimball plugin)","5":"vim RltvNmbr.vba.gz\r\n:so %\r\n\r\n(assuming you have vim 7.1 or later; with vim 7.0, you'll need to upgrade your vimball plugin)","first_name":"Charles","6":"Charles","last_name":"Campbell","7":"Campbell","releases":[{"0":"2351","vim_version":"7.0","1":"7.0","script_version":"3","2":"3","version_comment":"* Speeded up sign unplacing\r\n* Included g:rltvnmbrmode to report en\/dis-ablement of relative numbering\r\n* Includes some more autocmds for relative number updating\r\n","3":"* Speeded up sign unplacing\r\n* Included g:rltvnmbrmode to report en\/dis-ablement of relative numbering\r\n* Includes some more autocmds for relative number updating\r\n","package":"RltvNmbr.vba.gz","4":"RltvNmbr.vba.gz","src_id":"9540","5":"9540","creation_date":"1227289209","6":"1227289209"},{"0":"2351","vim_version":"7.0","1":"7.0","script_version":"2","2":"2","version_comment":"Been a number of requests to provide a toggling command, and so:  :RN  will toggle RltvNmbr'ing.  Plus a few more events will redraw the relative numbering signs.","3":"Been a number of requests to provide a toggling command, and so:  :RN  will toggle RltvNmbr'ing.  Plus a few more events will redraw the relative numbering signs.","package":"RltvNmbr.vba.gz","4":"RltvNmbr.vba.gz","src_id":"9159","5":"9159","creation_date":"1219222207","6":"1219222207"},{"0":"2351","vim_version":"7.0","1":"7.0","script_version":"1","2":"1","version_comment":"Displays line numbers relative to the current line -- helpful with commands that use [count]s.","3":"Displays line numbers relative to the current line -- helpful with commands that use [count]s.","package":"RltvNmbr.vba.gz","4":"RltvNmbr.vba.gz","src_id":"9155","5":"9155","creation_date":"1219129064","6":"1219129064"}]},"2350":{"script_id":"2350","0":"2350","script_name":"rootwater.vim","1":"rootwater.vim","script_type":"color scheme","2":"color scheme","summary":"A dark color scheme","3":"A dark color scheme","description":"A dark color scheme for the GUI.\r\n\r\nScreenshot at http:\/\/jstap.web.fc2.com\/rootwater.html\r\n","4":"A dark color scheme for the GUI.\r\n\r\nScreenshot at http:\/\/jstap.web.fc2.com\/rootwater.html\r\n","install_details":"Put it in one of your colors directories.\r\nThen, just do :colorscheme rootwater\r\n","5":"Put it in one of your colors directories.\r\nThen, just do :colorscheme rootwater\r\n","first_name":"Kojo","6":"Kojo","last_name":"Sugita","7":"Sugita","releases":[{"0":"2350","vim_version":"7.0","1":"7.0","script_version":"1.3","2":"1.3","version_comment":"Added \"CursorColumn\".\r\nThanks to Beno\u00c3\u00aet PIERRE.","3":"Added \"CursorColumn\".\r\nThanks to Beno\u00c3\u00aet PIERRE.","package":"rootwater.vim","4":"rootwater.vim","src_id":"10978","5":"10978","creation_date":"1247148421","6":"1247148421"},{"0":"2350","vim_version":"7.0","1":"7.0","script_version":"1.2","2":"1.2","version_comment":"Changed \"Comment\", Added \"CursorLine\".\r\nThanks to Gavin van Lelyveld.","3":"Changed \"Comment\", Added \"CursorLine\".\r\nThanks to Gavin van Lelyveld.","package":"rootwater.vim","4":"rootwater.vim","src_id":"9539","5":"9539","creation_date":"1227286922","6":"1227286922"},{"0":"2350","vim_version":"7.0","1":"7.0","script_version":"1.1","2":"1.1","version_comment":"Changed \"Title\" \"Todo\", Added \"MatchParen\"","3":"Changed \"Title\" \"Todo\", Added \"MatchParen\"","package":"rootwater.vim","4":"rootwater.vim","src_id":"9180","5":"9180","creation_date":"1219818310","6":"1219818310"},{"0":"2350","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"rootwater.vim","4":"rootwater.vim","src_id":"9152","5":"9152","creation_date":"1219126541","6":"1219126541"}]},"2349":{"script_id":"2349","0":"2349","script_name":"indent\/genie.vim","1":"indent\/genie.vim","script_type":"indent","2":"indent","summary":"Indent script for the genie (vala flavour) language","3":"Indent script for the genie (vala flavour) language","description":"A vim indent script for the genie programming language. http:\/\/live.gnome.org\/Genie \r\n\r\nThe script is derived from the python indent script.","4":"A vim indent script for the genie programming language. http:\/\/live.gnome.org\/Genie \r\n\r\nThe script is derived from the python indent script.","install_details":"copy genie.vim to ~\/.vim\/indent\/. Add:\r\n\r\naugroup setgenie\r\n  au!\r\n  au BufNewFile *.gs setlocal filetype=\"genie\"\r\n  au BufRead *.gs setlocal filetype=\"genie\"\r\naugroup END\r\n\r\nto your ~\/.vimrc file.\r\n\r\n","5":"copy genie.vim to ~\/.vim\/indent\/. Add:\r\n\r\naugroup setgenie\r\n  au!\r\n  au BufNewFile *.gs setlocal filetype=\"genie\"\r\n  au BufRead *.gs setlocal filetype=\"genie\"\r\naugroup END\r\n\r\nto your ~\/.vimrc file.\r\n\r\n","first_name":"ha","6":"ha","last_name":"shao","7":"shao","releases":[{"0":"2349","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"genie.vim","4":"genie.vim","src_id":"9150","5":"9150","creation_date":"1219096591","6":"1219096591"}]},"2348":{"script_id":"2348","0":"2348","script_name":"Chimp","1":"Chimp","script_type":"utility","2":"utility","summary":"Chimp talks to external interpreters from inside Vim","3":"Chimp talks to external interpreters from inside Vim","description":"Chimp uses screen to talk to external interpreters. The basic screen driver\r\nis language agnostic and is intended to be used as backend for filetype\r\nplugins, which comprise the intelligence of the system.\r\n\r\nAn example filetype plugin for Clojure is included. There are several ways\r\nto extract code and send it to a running Clojure in a screen.\r\n\r\nThe coupling is very loose on purpose! Eg. one can send from several Vims\r\nto the same screen. However this leads to a certain fragileness. The Clojure\r\nplugin takes care of automatically switching namespaces for the different\r\nfiles being edited. However, nothing prevents the user from interacting\r\nwith the REPL directly messing up the namespace sync between Chimp in Vim\r\nand Clojure.\r\n\r\nChimp should also work on Windows with Cygwin.\r\n\r\nYou will also need the VimClojure filetype plugin for\r\nthe Clojure frontend.\r\n\r\nhttp:\/\/kotka.de\/projects\/clojure\/vimclojure.html\r\n\r\nSimilar scripts:\r\n - VILisp (vimscript #221)\r\n - Limp (vimscript #2219)\r\n - http:\/\/technotales.wordpress.com\/2007\/10\/03\/like-slime-for-vim\/\r\n\r\n","4":"Chimp uses screen to talk to external interpreters. The basic screen driver\r\nis language agnostic and is intended to be used as backend for filetype\r\nplugins, which comprise the intelligence of the system.\r\n\r\nAn example filetype plugin for Clojure is included. There are several ways\r\nto extract code and send it to a running Clojure in a screen.\r\n\r\nThe coupling is very loose on purpose! Eg. one can send from several Vims\r\nto the same screen. However this leads to a certain fragileness. The Clojure\r\nplugin takes care of automatically switching namespaces for the different\r\nfiles being edited. However, nothing prevents the user from interacting\r\nwith the REPL directly messing up the namespace sync between Chimp in Vim\r\nand Clojure.\r\n\r\nChimp should also work on Windows with Cygwin.\r\n\r\nYou will also need the VimClojure filetype plugin for\r\nthe Clojure frontend.\r\n\r\nhttp:\/\/kotka.de\/projects\/clojure\/vimclojure.html\r\n\r\nSimilar scripts:\r\n - VILisp (vimscript #221)\r\n - Limp (vimscript #2219)\r\n - http:\/\/technotales.wordpress.com\/2007\/10\/03\/like-slime-for-vim\/\r\n\r\n","install_details":"For installation put the extracted subdirectory in your .vim directory.\r\nStart your interpreter with the chimp.sh wrapper from the bin\/ subdir.\r\nIt tells you a \"Chimp Id\" in the bottom line of the screen. Supply this\r\nto the glue functions. The Clojure plugin will ask you the first time\r\nyou send data and will further cache the Id.\r\n\r\n","5":"For installation put the extracted subdirectory in your .vim directory.\r\nStart your interpreter with the chimp.sh wrapper from the bin\/ subdir.\r\nIt tells you a \"Chimp Id\" in the bottom line of the screen. Supply this\r\nto the glue functions. The Clojure plugin will ask you the first time\r\nyou send data and will further cache the Id.\r\n\r\n","first_name":"Meikel","6":"Meikel","last_name":"Brandmeyer","7":"Brandmeyer","releases":[{"0":"2348","vim_version":"7.0","1":"7.0","script_version":"1.2.0","2":"1.2.0","version_comment":"Added more functions for the Clojure frontend:\r\n- dw to look up documentation for word under the cursor\r\n- ld to look up arbitrary documentation\r\n- fd to find documentation via find-doc\r\n\r\nFixed a bug with an obsolete argument to EvalFile","3":"Added more functions for the Clojure frontend:\r\n- dw to look up documentation for word under the cursor\r\n- ld to look up arbitrary documentation\r\n- fd to find documentation via find-doc\r\n\r\nFixed a bug with an obsolete argument to EvalFile","package":"chimp-1.2.0.tar.gz","4":"chimp-1.2.0.tar.gz","src_id":"9368","5":"9368","creation_date":"1224363807","6":"1224363807"},{"0":"2348","vim_version":"7.0","1":"7.0","script_version":"1.1.0","2":"1.1.0","version_comment":"- Mostly clean-up release.\r\n- Now recognises new clojure\/ns function.\r\n- Requires VimClojure >= 1.2.1 for the Clojure frontend.","3":"- Mostly clean-up release.\r\n- Now recognises new clojure\/ns function.\r\n- Requires VimClojure >= 1.2.1 for the Clojure frontend.","package":"chimp-1.1.0.tar.gz","4":"chimp-1.1.0.tar.gz","src_id":"9215","5":"9215","creation_date":"1220368177","6":"1220368177"},{"0":"2348","vim_version":"7.0","1":"7.0","script_version":"1.0.0","2":"1.0.0","version_comment":"Initial upload","3":"Initial upload","package":"chimp-1.0.0.tar.gz","4":"chimp-1.0.0.tar.gz","src_id":"9149","5":"9149","creation_date":"1219072953","6":"1219072953"}]},"2347":{"script_id":"2347","0":"2347","script_name":"Trinity","1":"Trinity","script_type":"utility","2":"utility","summary":"An IDE: the Trinity of taglist, NERDtree and SrcExpl","3":"An IDE: the Trinity of taglist, NERDtree and SrcExpl","description":"[GitHub]\r\n\r\nThe latest dev version of Trinity and screenshots can be downloaded from GitHub Homepage:\r\n\r\nhttps:\/\/github.com\/wesleyche\/Trinity\r\n\r\n[Introduction]\r\n\r\nThe Trinity plugin manages Source Explorer, Taglist and NERD Tree, and build them as a great IDE.\r\n\r\n[Features]\r\n\r\n1\\ Automatic Display of Declarations in the Context Window on the bottom in the (G)VIM window using the script named 'Source Explorer(srcexpl.vim)' :\r\nhttps:\/\/www.vim.org\/scripts\/script.php?script_id=2179\r\n\r\n2\\ Symbol Windows For Each File on the left in the (G)VIM window (G)VIM using the script named 'taglist.vim':\r\nhttps:\/\/www.vim.org\/scripts\/script.php?script_id=273\r\n\r\n3\\ Quick Access to All Files on the right in the (G)VIM window using the script named 'The NERD tree(NERD_tree.vim)':\r\nhttps:\/\/www.vim.org\/scripts\/script.php?script_id=1658\r\n\r\n4\\ You can change various options of each plugin in trinity.vim according to you request.\r\n\r\n[Declaration]\r\n\r\nIn order to build such an IDE that implement the main functions(function list, definition and context explorer, file brower), I had modified the source code of 'NERD_tree.zip 2.13.0'. You would note the comments which begin with 'Wenlong Che add\/delete for trinity.vim' in the NERD_tree.vim.","4":"[GitHub]\r\n\r\nThe latest dev version of Trinity and screenshots can be downloaded from GitHub Homepage:\r\n\r\nhttps:\/\/github.com\/wesleyche\/Trinity\r\n\r\n[Introduction]\r\n\r\nThe Trinity plugin manages Source Explorer, Taglist and NERD Tree, and build them as a great IDE.\r\n\r\n[Features]\r\n\r\n1\\ Automatic Display of Declarations in the Context Window on the bottom in the (G)VIM window using the script named 'Source Explorer(srcexpl.vim)' :\r\nhttps:\/\/www.vim.org\/scripts\/script.php?script_id=2179\r\n\r\n2\\ Symbol Windows For Each File on the left in the (G)VIM window (G)VIM using the script named 'taglist.vim':\r\nhttps:\/\/www.vim.org\/scripts\/script.php?script_id=273\r\n\r\n3\\ Quick Access to All Files on the right in the (G)VIM window using the script named 'The NERD tree(NERD_tree.vim)':\r\nhttps:\/\/www.vim.org\/scripts\/script.php?script_id=1658\r\n\r\n4\\ You can change various options of each plugin in trinity.vim according to you request.\r\n\r\n[Declaration]\r\n\r\nIn order to build such an IDE that implement the main functions(function list, definition and context explorer, file brower), I had modified the source code of 'NERD_tree.zip 2.13.0'. You would note the comments which begin with 'Wenlong Che add\/delete for trinity.vim' in the NERD_tree.vim.","install_details":"1\\ Unzip the 'Trinity-2.2.zip', and copy all the script files into to the plugin directory of Vimfiles, such as ~\/.vim\/plugin\/ \r\n\r\n2\\ Add the followings in your .vimrc or _vimrc and change them by yourself\r\n\r\n\" Open and close all the three plugins on the same time\r\nnmap <F8>   :TrinityToggleAll<CR>\r\n\r\n\" Open and close the srcexpl.vim separately\r\nnmap <F9>   :TrinityToggleSourceExplorer<CR>\r\n\r\n\" Open and close the taglist.vim separately\r\nnmap <F10>  :TrinityToggleTagList<CR>\r\n\r\n\" Open and close the NERD_tree.vim separately\r\nnmap <F11>  :TrinityToggleNERDTree<CR>\r\n\r\n3\\ Enjoy vimming :-) ","5":"1\\ Unzip the 'Trinity-2.2.zip', and copy all the script files into to the plugin directory of Vimfiles, such as ~\/.vim\/plugin\/ \r\n\r\n2\\ Add the followings in your .vimrc or _vimrc and change them by yourself\r\n\r\n\" Open and close all the three plugins on the same time\r\nnmap <F8>   :TrinityToggleAll<CR>\r\n\r\n\" Open and close the srcexpl.vim separately\r\nnmap <F9>   :TrinityToggleSourceExplorer<CR>\r\n\r\n\" Open and close the taglist.vim separately\r\nnmap <F10>  :TrinityToggleTagList<CR>\r\n\r\n\" Open and close the NERD_tree.vim separately\r\nnmap <F11>  :TrinityToggleNERDTree<CR>\r\n\r\n3\\ Enjoy vimming :-) ","first_name":"Wenlong","6":"Wenlong","last_name":"Che","7":"Che","releases":[{"0":"2347","vim_version":"7.0","1":"7.0","script_version":"2.2","2":"2.2","version_comment":"Add the configurations for supporting Source Explorer v6.0. More details, please refer to the Change Log via https:\/\/github.com\/wesleyche\/SrcExpl","3":"Add the configurations for supporting Source Explorer v6.0. More details, please refer to the Change Log via https:\/\/github.com\/wesleyche\/SrcExpl","package":"Trinity-2.2.zip","4":"Trinity-2.2.zip","src_id":"26063","5":"26063","creation_date":"1529408552","6":"1529408552"},{"0":"2347","vim_version":"7.0","1":"7.0","script_version":"2.1","2":"2.1","version_comment":"Add the default keys for Source Explorer's fast way to multi-defs jumping. More details, please refer to the Change Log via https:\/\/github.com\/wesleyche\/SrcExpl","3":"Add the default keys for Source Explorer's fast way to multi-defs jumping. More details, please refer to the Change Log via https:\/\/github.com\/wesleyche\/SrcExpl","package":"Trinity-2.1.zip","4":"Trinity-2.1.zip","src_id":"19683","5":"19683","creation_date":"1363961236","6":"1363961236"},{"0":"2347","vim_version":"7.0","1":"7.0","script_version":"2.0","2":"2.0","version_comment":"2.0\r\nSupport the Named Buffer Version of Source Explorer (v5.1 and above).","3":"2.0\r\nSupport the Named Buffer Version of Source Explorer (v5.1 and above).","package":"Trinity-2.0.zip","4":"Trinity-2.0.zip","src_id":"18643","5":"18643","creation_date":"1348145290","6":"1348145290"},{"0":"2347","vim_version":"7.0","1":"7.0","script_version":"1.6","2":"1.6","version_comment":"Add one new user interface named 'TrinityUpdateWindow' for updating Trinity window positions. e.g. when you use Quickfix together with Trinity, you may need to call this function for recover the window positions.","3":"Add one new user interface named 'TrinityUpdateWindow' for updating Trinity window positions. e.g. when you use Quickfix together with Trinity, you may need to call this function for recover the window positions.","package":"trinity.zip","4":"trinity.zip","src_id":"17519","5":"17519","creation_date":"1330053712","6":"1330053712"},{"0":"2347","vim_version":"6.0","1":"6.0","script_version":"1.5","2":"1.5","version_comment":"I modified the options of 'ctags' program for Source Explorer (srcexpl.vim) V4.0. \r\nThe response time was less than 0.2 second each tagging with the new version. The environment I tested is below: \r\nsource code: linux-2.6.25 (17308 files) \r\nsize of tags: 60.1MB (691327 lines) ","3":"I modified the options of 'ctags' program for Source Explorer (srcexpl.vim) V4.0. \r\nThe response time was less than 0.2 second each tagging with the new version. The environment I tested is below: \r\nsource code: linux-2.6.25 (17308 files) \r\nsize of tags: 60.1MB (691327 lines) ","package":"trinity.zip","4":"trinity.zip","src_id":"11988","5":"11988","creation_date":"1262260465","6":"1262260465"},{"0":"2347","vim_version":"7.0","1":"7.0","script_version":"1.4","2":"1.4","version_comment":"Add a new configure global variable named g:SrcExpl_updateTagsKey for the Source Explorer (srcexpl.vim) V3.9 when initializing the trinity plugin.","3":"Add a new configure global variable named g:SrcExpl_updateTagsKey for the Source Explorer (srcexpl.vim) V3.9 when initializing the trinity plugin.","package":"trinity.vim","4":"trinity.vim","src_id":"10102","5":"10102","creation_date":"1236168234","6":"1236168234"},{"0":"2347","vim_version":"7.0","1":"7.0","script_version":"1.3","2":"1.3","version_comment":"Modified some configure global values of the Source Explorer 3.6 (srcexpl.vim) when initializing the trinity plugin.","3":"Modified some configure global values of the Source Explorer 3.6 (srcexpl.vim) when initializing the trinity plugin.","package":"trinity.vim","4":"trinity.vim","src_id":"9946","5":"9946","creation_date":"1234269178","6":"1234269178"}]},"2346":{"script_id":"2346","0":"2346","script_name":"bufmru.vim","1":"bufmru.vim","script_type":"utility","2":"utility","summary":"switch to a most recently used buffer quickly","3":"switch to a most recently used buffer quickly","description":"Switch between MRU buffers from the current session. Like CTRL-^, but reach\r\nmore buffers (and maintain only one global list, not one list per window).\r\n\r\nUsage:\r\n\r\n  Press  <Space>  to show the most recently used buffer and enter Bufmru mode.\r\n\r\n  In Bufmru mode:\r\n  Press  f  or  b  (forward\/backward) to reach more MRU buffers.\r\n  Press  e  or  <Enter>  to accept the current choice.\r\n  Press  q  or  <Esc>  to quit the mode and to go back to the start buffer\r\n  Press  y  to copy a file name\r\n\r\nConfiguration:\r\n  :let g:bufmru_switchkey = \"<Space>\"\r\n      (checked once) Key to enter Bufmru mode.\r\n\r\n  :let g:bufmru_confclose = 0\r\n      (always) Use :confirm (1) when abandoning a modified buffer.\r\n      Otherwise (0, default) you'll get an error message, unless 'hidden'\r\n      is set.\r\n\r\n  :let g:bufmru_bnrs = []\r\n      (always) The internal stack of buffer numbers.  Normally, you'll\r\n      leave this alone, but you can manually add or remove buffer numbers\r\n      or initialize the list.  Don't worry about wrong numbers.\r\n\r\n  :let g:bufmru_read_nummarks = 0\r\n      (once) Put the number mark '0 ... '9 buffers in g:bufmru_bnrs.  This adds\r\n      buffers to the buffer list!\r\n\r\nwildmenu version only:\r\n\r\n  g:bufmru_wildmenu   (dictionary, initially not defined)\r\n      (always) Instance of autoload\/wildmenu.vim to show buffer names in a\r\n      wildmenu-like list.  If not defined, bufmru tries to load the autoload\r\n      script.  If that fails the value becomes empty ({}) -- and bufmru\r\n      quite unusable.\r\n\r\n  :let g:bufmru_wilditems = \"bufnr,shortpath\"\r\n      (always) How to display entries in the \"wildmenu\":\r\n      \"bufnr\"         with prepended buffer number\r\n      \"shortpath\"     with pathshorten() applied to the bufname()\r\n      There is no error message for wrong items.\r\n\r\nsplashbufs version only:\r\n\r\n  :let g:bufmru_lazy_filetype = 0\r\n      (checked always) If 1, do lazy filetype detection when going through\r\n      the buffers with f and b.  Not used if 'hidden' is set.\r\n\r\n\r\nspecial buffer: 'buftype' not empty or 'previewwindow' set\r\n\r\nRelated:\r\nhttp:\/\/vim.wikia.com\/wiki\/Easier_buffer_switching\r\n\r\nWhere it began:\r\nhttp:\/\/groups.google.com\/group\/vim_use\/msg\/adb4f35772ecbcbe\r\n\r\nAnother MRU buffers script!  But it requires Ruby (that I haven't installed):\r\nLustyJuggler vimscript #2050","4":"Switch between MRU buffers from the current session. Like CTRL-^, but reach\r\nmore buffers (and maintain only one global list, not one list per window).\r\n\r\nUsage:\r\n\r\n  Press  <Space>  to show the most recently used buffer and enter Bufmru mode.\r\n\r\n  In Bufmru mode:\r\n  Press  f  or  b  (forward\/backward) to reach more MRU buffers.\r\n  Press  e  or  <Enter>  to accept the current choice.\r\n  Press  q  or  <Esc>  to quit the mode and to go back to the start buffer\r\n  Press  y  to copy a file name\r\n\r\nConfiguration:\r\n  :let g:bufmru_switchkey = \"<Space>\"\r\n      (checked once) Key to enter Bufmru mode.\r\n\r\n  :let g:bufmru_confclose = 0\r\n      (always) Use :confirm (1) when abandoning a modified buffer.\r\n      Otherwise (0, default) you'll get an error message, unless 'hidden'\r\n      is set.\r\n\r\n  :let g:bufmru_bnrs = []\r\n      (always) The internal stack of buffer numbers.  Normally, you'll\r\n      leave this alone, but you can manually add or remove buffer numbers\r\n      or initialize the list.  Don't worry about wrong numbers.\r\n\r\n  :let g:bufmru_read_nummarks = 0\r\n      (once) Put the number mark '0 ... '9 buffers in g:bufmru_bnrs.  This adds\r\n      buffers to the buffer list!\r\n\r\nwildmenu version only:\r\n\r\n  g:bufmru_wildmenu   (dictionary, initially not defined)\r\n      (always) Instance of autoload\/wildmenu.vim to show buffer names in a\r\n      wildmenu-like list.  If not defined, bufmru tries to load the autoload\r\n      script.  If that fails the value becomes empty ({}) -- and bufmru\r\n      quite unusable.\r\n\r\n  :let g:bufmru_wilditems = \"bufnr,shortpath\"\r\n      (always) How to display entries in the \"wildmenu\":\r\n      \"bufnr\"         with prepended buffer number\r\n      \"shortpath\"     with pathshorten() applied to the bufname()\r\n      There is no error message for wrong items.\r\n\r\nsplashbufs version only:\r\n\r\n  :let g:bufmru_lazy_filetype = 0\r\n      (checked always) If 1, do lazy filetype detection when going through\r\n      the buffers with f and b.  Not used if 'hidden' is set.\r\n\r\n\r\nspecial buffer: 'buftype' not empty or 'previewwindow' set\r\n\r\nRelated:\r\nhttp:\/\/vim.wikia.com\/wiki\/Easier_buffer_switching\r\n\r\nWhere it began:\r\nhttp:\/\/groups.google.com\/group\/vim_use\/msg\/adb4f35772ecbcbe\r\n\r\nAnother MRU buffers script!  But it requires Ruby (that I haven't installed):\r\nLustyJuggler vimscript #2050","install_details":"bufmru 2.x\r\n        wildmenu version.  Buffers are shown in a wildmenu like list in the\r\n        cmdline area.\r\n        Unpack the archive into ~\\vimfiles or a similar folder from your\r\n        'runtimepath'.  Files in the archive:\r\n            plugin\/bufmru.vim\r\n            autoload\/anwolib.vim\r\n            autoload\/wildmenu.vim\r\n            doc\/bufmru.txt\r\n\r\nbufmru 3.x\r\n        splashbufs version.  It is just the plugin file without external\r\n        dependencies.  Buffers are switched instantly like with CTRL-^; but\r\n        switching is meant to be a preview as long as Bufmru is active.\r\n        Copy bufmru.vim to ~\\vimfiles\\plugin or a similar plugin folder.\r\n","5":"bufmru 2.x\r\n        wildmenu version.  Buffers are shown in a wildmenu like list in the\r\n        cmdline area.\r\n        Unpack the archive into ~\\vimfiles or a similar folder from your\r\n        'runtimepath'.  Files in the archive:\r\n            plugin\/bufmru.vim\r\n            autoload\/anwolib.vim\r\n            autoload\/wildmenu.vim\r\n            doc\/bufmru.txt\r\n\r\nbufmru 3.x\r\n        splashbufs version.  It is just the plugin file without external\r\n        dependencies.  Buffers are switched instantly like with CTRL-^; but\r\n        switching is meant to be a preview as long as Bufmru is active.\r\n        Copy bufmru.vim to ~\\vimfiles\\plugin or a similar plugin folder.\r\n","first_name":"Andy","6":"Andy","last_name":"Wokula","7":"Wokula","releases":[{"0":"2346","vim_version":"7.0","1":"7.0","script_version":"3.3","2":"3.3","version_comment":"splashbufs only version, option g:splashbufs gone\r\nsimilar to v2.7, but no change of 'timeoutlen' for Bufmru mode\r\nNF: variable g:bufmru_lazy_filetype","3":"splashbufs only version, option g:splashbufs gone\r\nsimilar to v2.7, but no change of 'timeoutlen' for Bufmru mode\r\nNF: variable g:bufmru_lazy_filetype","package":"bufmru.vim","4":"bufmru.vim","src_id":"10574","5":"10574","creation_date":"1241992528","6":"1241992528"},{"0":"2346","vim_version":"7.0","1":"7.0","script_version":"2.7","2":"2.7","version_comment":"wildmenu only version, option g:splashbufs gone\r\nBF: 'fileformat' of wildmenu.vim and anwolib.vim set to unix !\r\nBF: now works better with 'lazyredraw' set\r\nBF: g:bufmru_limit=0 now means unlimited (0 makes no sense otherwise)\r\nNF: variable g:bufmru_wilditems to customize wildmenu entries\r\nNF: 'timeoutlen' of Bufmru Mode set to 60000 ms","3":"wildmenu only version, option g:splashbufs gone\r\nBF: 'fileformat' of wildmenu.vim and anwolib.vim set to unix !\r\nBF: now works better with 'lazyredraw' set\r\nBF: g:bufmru_limit=0 now means unlimited (0 makes no sense otherwise)\r\nNF: variable g:bufmru_wilditems to customize wildmenu entries\r\nNF: 'timeoutlen' of Bufmru Mode set to 60000 ms","package":"bufmru_2.7.zip","4":"bufmru_2.7.zip","src_id":"10572","5":"10572","creation_date":"1241990861","6":"1241990861"},{"0":"2346","vim_version":"7.0","1":"7.0","script_version":"2.0","2":"2.0","version_comment":"like 1.0 but includes a help file and uses autoload\/wildmenu.vim to show buffer names in a wildmenu like list","3":"like 1.0 but includes a help file and uses autoload\/wildmenu.vim to show buffer names in a wildmenu like list","package":"bufmru_2.0.zip","4":"bufmru_2.0.zip","src_id":"10122","5":"10122","creation_date":"1236274431","6":"1236274431"},{"0":"2346","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"New Variables: g:bufmru_splashbufs\r\nChanged Variables: g:bufmru_confclose, g:bufmru_nummarks renamed to g:bufmru_read_nummarks\r\nAdded Keys: y  !  f\r\nChanged Keys: <Space> replaced with  f  in Bufmru mode\r\nNew Functions: Bufmru_Read_Nummarks()\r\nBehaviour:\r\n* no more cycling: going forward\/backward stops at either end of the MRU list\r\n* Valid buffer number: now also 'buflisted' required\r\nBug fixes ...\r\n","3":"New Variables: g:bufmru_splashbufs\r\nChanged Variables: g:bufmru_confclose, g:bufmru_nummarks renamed to g:bufmru_read_nummarks\r\nAdded Keys: y  !  f\r\nChanged Keys: <Space> replaced with  f  in Bufmru mode\r\nNew Functions: Bufmru_Read_Nummarks()\r\nBehaviour:\r\n* no more cycling: going forward\/backward stops at either end of the MRU list\r\n* Valid buffer number: now also 'buflisted' required\r\nBug fixes ...\r\n","package":"bufmru.vim","4":"bufmru.vim","src_id":"10121","5":"10121","creation_date":"1236274220","6":"1236274220"},{"0":"2346","vim_version":"7.0","1":"7.0","script_version":"0.3","2":"0.3","version_comment":"now truncates too long buffer names\r\nadded g:bufmru_nummarks","3":"now truncates too long buffer names\r\nadded g:bufmru_nummarks","package":"bufmru.vim","4":"bufmru.vim","src_id":"9194","5":"9194","creation_date":"1220010593","6":"1220010593"},{"0":"2346","vim_version":"7.0","1":"7.0","script_version":"0.2","2":"0.2","version_comment":"some config added, keys added, some obvious bugs fixed. recommended update","3":"some config added, keys added, some obvious bugs fixed. recommended update","package":"bufmru.vim","4":"bufmru.vim","src_id":"9153","5":"9153","creation_date":"1219127799","6":"1219127799"},{"0":"2346","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"bufmru.vim","4":"bufmru.vim","src_id":"9140","5":"9140","creation_date":"1219035958","6":"1219035958"}]},"2345":{"script_id":"2345","0":"2345","script_name":"Vimchant","1":"Vimchant","script_type":"utility","2":"utility","summary":"Fast on-the-fly spell-checker based on Enchant","3":"Fast on-the-fly spell-checker based on Enchant","description":"Note: This plugin is not maintained.\r\n\r\nVim 7.0 introduced excellent spell-checking features which made external spell-checker plugins pretty much obsolete. Unfortunately not all languages can be supported through Vim\u00e2\u0080\u0099s dictionary format. Either the language is morphologically too complex or better custom solutions exist already for some languages\u00e2\u0080\u0094solutions which are not compatible with Vim\u00e2\u0080\u0099s spelling checker. Finnish, for example, is a language which doesn\u00e2\u0080\u0099t currently benefit from Vim\u00e2\u0080\u0099s spell-checking features.\r\n\r\nThis plugin (Vimchant) provides a simple but fast on-the-fly spelling checker which uses Enchant as its back-end program. Enchant is a spell-checker library and utility included in modern GNU\/Linux systems. Enchant itself is only a front-end for many different spell-checkers, including Voikko, Zemberek, Hunspell, Hspell, Uspell, Myspell, Aspell and Ispell. All the spell-checkers and languages which can be supported through Enchant are available to Vim through this plugin.\r\n\r\nManual for Vimchant is included, just type\r\n\r\n    :help vimchant.txt\r\n\r\nThe most interesting commands are \\ss (spell-checker on\/off) and \\sl (change language). The default interval period before running the spell-check is rather long (4 seconds). To make the spell-checker respond faster (1 second, for example) add the following line to your .vimrc file:\r\n\r\n    set updatetime=1000\r\n\r\nSee the manual for more info. See also the Enchant homepage:\r\n\r\n    http:\/\/www.abisource.com\/projects\/enchant\/\r\n","4":"Note: This plugin is not maintained.\r\n\r\nVim 7.0 introduced excellent spell-checking features which made external spell-checker plugins pretty much obsolete. Unfortunately not all languages can be supported through Vim\u00e2\u0080\u0099s dictionary format. Either the language is morphologically too complex or better custom solutions exist already for some languages\u00e2\u0080\u0094solutions which are not compatible with Vim\u00e2\u0080\u0099s spelling checker. Finnish, for example, is a language which doesn\u00e2\u0080\u0099t currently benefit from Vim\u00e2\u0080\u0099s spell-checking features.\r\n\r\nThis plugin (Vimchant) provides a simple but fast on-the-fly spelling checker which uses Enchant as its back-end program. Enchant is a spell-checker library and utility included in modern GNU\/Linux systems. Enchant itself is only a front-end for many different spell-checkers, including Voikko, Zemberek, Hunspell, Hspell, Uspell, Myspell, Aspell and Ispell. All the spell-checkers and languages which can be supported through Enchant are available to Vim through this plugin.\r\n\r\nManual for Vimchant is included, just type\r\n\r\n    :help vimchant.txt\r\n\r\nThe most interesting commands are \\ss (spell-checker on\/off) and \\sl (change language). The default interval period before running the spell-check is rather long (4 seconds). To make the spell-checker respond faster (1 second, for example) add the following line to your .vimrc file:\r\n\r\n    set updatetime=1000\r\n\r\nSee the manual for more info. See also the Enchant homepage:\r\n\r\n    http:\/\/www.abisource.com\/projects\/enchant\/\r\n","install_details":"Requirements:\r\n\r\n    \u00e2\u0080\u0093 Vim 7.1.040 or later\r\n    \u00e2\u0080\u0093 Enchant (possibly included in libenchant package in GNU\/Linux distributions)\r\n\r\nThe plugin uses Vimball plugin archive format (vimscript#1502). To install the package, load the file to Vim and run command\r\n\r\n    :source %\r\n\r\nTo remove the plugin, type\r\n\r\n    :RmVimball vimchant","5":"Requirements:\r\n\r\n    \u00e2\u0080\u0093 Vim 7.1.040 or later\r\n    \u00e2\u0080\u0093 Enchant (possibly included in libenchant package in GNU\/Linux distributions)\r\n\r\nThe plugin uses Vimball plugin archive format (vimscript#1502). To install the package, load the file to Vim and run command\r\n\r\n    :source %\r\n\r\nTo remove the plugin, type\r\n\r\n    :RmVimball vimchant","first_name":"Teemu","6":"Teemu","last_name":"Likonen","7":"Likonen","releases":[{"0":"2345","vim_version":"7.0","1":"7.0","script_version":"1.1","2":"1.1","version_comment":"Move the most part of the plugin to autoload directory. Now only the very minimum of this plugin is loaded automatically when Vim is started and the rest is loaded when the spell-checker is used for the first time.","3":"Move the most part of the plugin to autoload directory. Now only the very minimum of this plugin is loaded automatically when Vim is started and the rest is loaded when the spell-checker is used for the first time.","package":"vimchant.vba","4":"vimchant.vba","src_id":"9199","5":"9199","creation_date":"1220140952","6":"1220140952"}]},"2344":{"script_id":"2344","0":"2344","script_name":"ku-metarw","1":"ku-metarw","script_type":"utility","2":"utility","summary":"ku source: metarw","3":"ku source: metarw","description":"*ku-metarw* is a source for |ku| to deal with |metarw-fakepath|.  You can\r\nchoose one from many fakepaths and do some action to it.\r\n\r\n\r\nRequirements:\r\n- Vim 7.1 or later\r\n- |ku| 0.2.2 or later (vimscript#2337)\r\n- |metarw| 0.0.1 or later (vimscript#2335)\r\n- |metarw-scheme-script| such as |metarw-git| (vimscript#2336)\r\n\r\nLatest version:\r\nhttp:\/\/github.com\/kana\/vim-ku-metarw\r\n\r\nDocument in HTML format:\r\nhttp:\/\/kana.github.com\/config\/vim\/ku-metarw.html","4":"*ku-metarw* is a source for |ku| to deal with |metarw-fakepath|.  You can\r\nchoose one from many fakepaths and do some action to it.\r\n\r\n\r\nRequirements:\r\n- Vim 7.1 or later\r\n- |ku| 0.2.2 or later (vimscript#2337)\r\n- |metarw| 0.0.1 or later (vimscript#2335)\r\n- |metarw-scheme-script| such as |metarw-git| (vimscript#2336)\r\n\r\nLatest version:\r\nhttp:\/\/github.com\/kana\/vim-ku-metarw\r\n\r\nDocument in HTML format:\r\nhttp:\/\/kana.github.com\/config\/vim\/ku-metarw.html","install_details":"...","5":"...","first_name":"Kana","6":"Kana","last_name":"Natsuno","7":"Natsuno","releases":[{"0":"2344","vim_version":"7.0","1":"7.0","script_version":"0.1.2","2":"0.1.2","version_comment":"Bug fixes:\n- Fix an assumption that the separator for pathes is \"\/\".  This assumption causes unexpected behavior on some environments such as Microsoft Windows.\n\nIncompatible changes:\n- Require ku 0.2.2.","3":"Bug fixes:\n- Fix an assumption that the separator for pathes is \"\/\".  This assumption causes unexpected behavior on some environments such as Microsoft Windows.\n\nIncompatible changes:\n- Require ku 0.2.2.","package":"vim-ku-metarw-0.1.2.zip","4":"vim-ku-metarw-0.1.2.zip","src_id":"10602","5":"10602","creation_date":"1242398185","6":"1242398185"},{"0":"2344","vim_version":"7.0","1":"7.0","script_version":"0.1.1","2":"0.1.1","version_comment":"- Update for ku 0.2.1.","3":"- Update for ku 0.2.1.","package":"vim-ku-metarw-0.1.1.zip","4":"vim-ku-metarw-0.1.1.zip","src_id":"10513","5":"10513","creation_date":"1241374448","6":"1241374448"},{"0":"2344","vim_version":"7.0","1":"7.0","script_version":"0.1.0","2":"0.1.0","version_comment":"- Update for ku 0.2.0.","3":"- Update for ku 0.2.0.","package":"vim-ku-metarw-0.1.0.zip","4":"vim-ku-metarw-0.1.0.zip","src_id":"10477","5":"10477","creation_date":"1240919667","6":"1240919667"},{"0":"2344","vim_version":"7.0","1":"7.0","script_version":"0.0.1","2":"0.0.1","version_comment":"- Update for ku 0.1.3.","3":"- Update for ku 0.1.3.","package":"vim-ku-metarw-0.0.1.zip","4":"vim-ku-metarw-0.0.1.zip","src_id":"9291","5":"9291","creation_date":"1222605298","6":"1222605298"},{"0":"2344","vim_version":"7.0","1":"7.0","script_version":"0.0.0","2":"0.0.0","version_comment":"Initial upload","3":"Initial upload","package":"vim-ku-metarw-0.0.0.zip","4":"vim-ku-metarw-0.0.0.zip","src_id":"9137","5":"9137","creation_date":"1218924152","6":"1218924152"}]},"2343":{"script_id":"2343","0":"2343","script_name":"ku-bundle","1":"ku-bundle","script_type":"utility","2":"utility","summary":"ku source: bundle","3":"ku source: bundle","description":"*ku-bundle* is a source for |ku| to deal with bundles for a Vim plugin\r\n|bundle|.  You can choose one from many bundles and do some action to it.\r\n\r\n\r\nRequirements:\r\n- Vim 7.1 or later\r\n- |bundle| 0.0.2 or later (vimscript#2338)\r\n- |ku| 0.2.0 or later (vimscript#2337)\r\n\r\nLatest version:\r\nhttp:\/\/github.com\/kana\/vim-ku-bundle\r\n\r\nDocument in HTML format:\r\nhttp:\/\/kana.github.com\/config\/vim\/ku-bundle.html","4":"*ku-bundle* is a source for |ku| to deal with bundles for a Vim plugin\r\n|bundle|.  You can choose one from many bundles and do some action to it.\r\n\r\n\r\nRequirements:\r\n- Vim 7.1 or later\r\n- |bundle| 0.0.2 or later (vimscript#2338)\r\n- |ku| 0.2.0 or later (vimscript#2337)\r\n\r\nLatest version:\r\nhttp:\/\/github.com\/kana\/vim-ku-bundle\r\n\r\nDocument in HTML format:\r\nhttp:\/\/kana.github.com\/config\/vim\/ku-bundle.html","install_details":"...","5":"...","first_name":"Kana","6":"Kana","last_name":"Natsuno","7":"Natsuno","releases":[{"0":"2343","vim_version":"7.0","1":"7.0","script_version":"0.1.1","2":"0.1.1","version_comment":"- Update for ku 0.2.1.","3":"- Update for ku 0.2.1.","package":"vim-ku-bundle-0.1.1.zip","4":"vim-ku-bundle-0.1.1.zip","src_id":"10512","5":"10512","creation_date":"1241374428","6":"1241374428"},{"0":"2343","vim_version":"7.0","1":"7.0","script_version":"0.1.0","2":"0.1.0","version_comment":"- Update for ku 0.2.0.","3":"- Update for ku 0.2.0.","package":"vim-ku-bundle-0.1.0.zip","4":"vim-ku-bundle-0.1.0.zip","src_id":"10476","5":"10476","creation_date":"1240919650","6":"1240919650"},{"0":"2343","vim_version":"7.0","1":"7.0","script_version":"0.0.2","2":"0.0.2","version_comment":"- Change |ku-bundle-action-default|.  Now it does the same as |ku-bundle-action-args| instead of |ku-bundle-action-load-or-args|.","3":"- Change |ku-bundle-action-default|.  Now it does the same as |ku-bundle-action-args| instead of |ku-bundle-action-load-or-args|.","package":"vim-ku-bundle-0.0.2.zip","4":"vim-ku-bundle-0.0.2.zip","src_id":"9722","5":"9722","creation_date":"1230109270","6":"1230109270"},{"0":"2343","vim_version":"7.0","1":"7.0","script_version":"0.0.1","2":"0.0.1","version_comment":"Initial upload","3":"Initial upload","package":"vim-ku-bundle-0.0.1.zip","4":"vim-ku-bundle-0.0.1.zip","src_id":"9136","5":"9136","creation_date":"1218924065","6":"1218924065"}]},"2342":{"script_id":"2342","0":"2342","script_name":"dictview.vim","1":"dictview.vim","script_type":"utility","2":"utility","summary":"print the contents of a variable","3":"print the contents of a variable","description":"Print the contents of a variable (or any expression), useful for lists and dictionaries.\r\n\r\nAdds the command\r\n    :DictView {expr}\r\n\r\nExamples:\r\n:let mylist = [\"foo\",\"bar\"]\r\n:DictView mylist\r\n* [\r\n    'foo'\r\n    'bar'\r\n* ]\r\n:DictView {1: mylist}\r\n* {\r\n*   1:\r\n    [\r\n      'foo'\r\n      'bar'\r\n    ]\r\n* }\r\n\r\nCustom variables:\r\ng:dictview_shiftwidth (default 2)\r\ng:dictview_maxlevel (default 10)\r\n\r\nGlobal functions:\r\nfunc! DictView_PrintList(value, ...)\r\nfunc! DictView_Print(value)\r\n\r\n2009 Nov 21 also check out: PrettyPrint  vimscript #2860, it is much better","4":"Print the contents of a variable (or any expression), useful for lists and dictionaries.\r\n\r\nAdds the command\r\n    :DictView {expr}\r\n\r\nExamples:\r\n:let mylist = [\"foo\",\"bar\"]\r\n:DictView mylist\r\n* [\r\n    'foo'\r\n    'bar'\r\n* ]\r\n:DictView {1: mylist}\r\n* {\r\n*   1:\r\n    [\r\n      'foo'\r\n      'bar'\r\n    ]\r\n* }\r\n\r\nCustom variables:\r\ng:dictview_shiftwidth (default 2)\r\ng:dictview_maxlevel (default 10)\r\n\r\nGlobal functions:\r\nfunc! DictView_PrintList(value, ...)\r\nfunc! DictView_Print(value)\r\n\r\n2009 Nov 21 also check out: PrettyPrint  vimscript #2860, it is much better","install_details":"copy to plugin folder (e.g. ~\\vimfiles\\plugin)","5":"copy to plugin folder (e.g. ~\\vimfiles\\plugin)","first_name":"Andy","6":"Andy","last_name":"Wokula","7":"Wokula","releases":[{"0":"2342","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"dictview.vim","4":"dictview.vim","src_id":"9124","5":"9124","creation_date":"1218690970","6":"1218690970"}]},"2341":{"script_id":"2341","0":"2341","script_name":"postmail.vim","1":"postmail.vim","script_type":"utility","2":"utility","summary":"mail message posting plugin. (python required)","3":"mail message posting plugin. (python required)","description":"Send 'current editing buffer', or 'selected area of text' with email.\r\nMost simplest usage is to execute :Mail command.\r\n\r\nSupported Mail Auth type is\r\n    - basic SMTP password Auth\r\n    - POP before STMP Auth\r\n    - Outbound Port 25 Blocking\r\n    - GMail\r\n\r\nThis plugin needs '+python', '+iconv', '+multi_byte' and\r\nPython is installed, and $PATH is appropriately set.\r\n\r\nUSAGE\r\nYou can use :Mail command to send email.\r\nSee also postmail-example .\r\n\r\n:[range]Mail\r\n        send mail message.\r\n        if [range] is selected, send selected text.\r\n        if [range] is not selected, send current buffer.\r\n\r\n:[range]Mail {to_mailaddress}\r\n        send mail message to {to_mailaddress}.\r\n        if [range] is selected, send selected text.\r\n        if [range] is not selected, send current buffer.\r\n\r\n:[range]Mail {to_mailaddress1} {to_mailaddress2}, {to_mailaddress3}\r\n        send mail message to {to_mailaddress1}, {to_mailaddress2}, and\r\n        {to_mailaddress2}.\r\n        if [range] is selected, send selected text.\r\n        if [range] is not selected, send current buffer.\r\n\r\nCOMMAND USAGE EXAMPLE\r\n:Mail\r\n        send mail message.\r\n        message is current buffer text.\r\n\r\n:Mail mail@nanasi.jp\r\n        send current buffer text to 'mail@nanasi.jp' address.\r\n\r\n:6,20Mail mail@nanasi.jp\r\n        send from line 6 to line 20 text to 'mail@nanasi.jp' address.\r\n","4":"Send 'current editing buffer', or 'selected area of text' with email.\r\nMost simplest usage is to execute :Mail command.\r\n\r\nSupported Mail Auth type is\r\n    - basic SMTP password Auth\r\n    - POP before STMP Auth\r\n    - Outbound Port 25 Blocking\r\n    - GMail\r\n\r\nThis plugin needs '+python', '+iconv', '+multi_byte' and\r\nPython is installed, and $PATH is appropriately set.\r\n\r\nUSAGE\r\nYou can use :Mail command to send email.\r\nSee also postmail-example .\r\n\r\n:[range]Mail\r\n        send mail message.\r\n        if [range] is selected, send selected text.\r\n        if [range] is not selected, send current buffer.\r\n\r\n:[range]Mail {to_mailaddress}\r\n        send mail message to {to_mailaddress}.\r\n        if [range] is selected, send selected text.\r\n        if [range] is not selected, send current buffer.\r\n\r\n:[range]Mail {to_mailaddress1} {to_mailaddress2}, {to_mailaddress3}\r\n        send mail message to {to_mailaddress1}, {to_mailaddress2}, and\r\n        {to_mailaddress2}.\r\n        if [range] is selected, send selected text.\r\n        if [range] is not selected, send current buffer.\r\n\r\nCOMMAND USAGE EXAMPLE\r\n:Mail\r\n        send mail message.\r\n        message is current buffer text.\r\n\r\n:Mail mail@nanasi.jp\r\n        send current buffer text to 'mail@nanasi.jp' address.\r\n\r\n:6,20Mail mail@nanasi.jp\r\n        send from line 6 to line 20 text to 'mail@nanasi.jp' address.\r\n","install_details":"1. Unzip postmail-vim-plugin.zip, and copy to 'plugin', 'doc' directory in\r\n   your 'runtimepath' directory.\r\n\r\n    $HOME\/vimfiles (Windows)\r\n    $HOME\/.vim\/ (Unix)\r\n\r\n2. Edit 'postmail.conf' and setup mail server configuration.\r\n    postmail.conf file encoding is same with &encoding value.\r\n\r\n    :echo &encoding\r\n\r\n3. Execute ':helptags' command to your runtimepath 'doc' directory.\r\n\r\n    :helptags $HOME\/vimfiles\/doc (Windows)\r\n    :helptags $HOME\/.vim\/doc (Unix)\r\n\r\nCONFIGURATION\r\npostmail.conf file is mail server configuration file.\r\nsimply configuration file setup is to comment out, and replace some\r\nconfiguration setting. See postmail.conf in your plugin directory.\r\n","5":"1. Unzip postmail-vim-plugin.zip, and copy to 'plugin', 'doc' directory in\r\n   your 'runtimepath' directory.\r\n\r\n    $HOME\/vimfiles (Windows)\r\n    $HOME\/.vim\/ (Unix)\r\n\r\n2. Edit 'postmail.conf' and setup mail server configuration.\r\n    postmail.conf file encoding is same with &encoding value.\r\n\r\n    :echo &encoding\r\n\r\n3. Execute ':helptags' command to your runtimepath 'doc' directory.\r\n\r\n    :helptags $HOME\/vimfiles\/doc (Windows)\r\n    :helptags $HOME\/.vim\/doc (Unix)\r\n\r\nCONFIGURATION\r\npostmail.conf file is mail server configuration file.\r\nsimply configuration file setup is to comment out, and replace some\r\nconfiguration setting. See postmail.conf in your plugin directory.\r\n","first_name":"omi","6":"omi","last_name":"taku","7":"taku","releases":[{"0":"2341","vim_version":"7.0","1":"7.0","script_version":"0.6","2":"0.6","version_comment":"refactoring plugin, and more easy setupable.\r\n","3":"refactoring plugin, and more easy setupable.\r\n","package":"postmail-vim-plugin.zip","4":"postmail-vim-plugin.zip","src_id":"11857","5":"11857","creation_date":"1259914527","6":"1259914527"},{"0":"2341","vim_version":"7.0","1":"7.0","script_version":"0.5.3","2":"0.5.3","version_comment":"plugin\/postmail.vim\r\n- Add escape code if mail_encoding is 'ISO-2022-JP'.","3":"plugin\/postmail.vim\r\n- Add escape code if mail_encoding is 'ISO-2022-JP'.","package":"postmail.zip","4":"postmail.zip","src_id":"9147","5":"9147","creation_date":"1219068011","6":"1219068011"},{"0":"2341","vim_version":"7.0","1":"7.0","script_version":"0.5.2","2":"0.5.2","version_comment":"- Change script name from 'sendmail' to 'postmail'.\r\n- Change from 'Vimball' to 'zip' archive distribution.\r\n\r\n","3":"- Change script name from 'sendmail' to 'postmail'.\r\n- Change from 'Vimball' to 'zip' archive distribution.\r\n\r\n","package":"postmail.zip","4":"postmail.zip","src_id":"9132","5":"9132","creation_date":"1218863578","6":"1218863578"},{"0":"2341","vim_version":"7.0","1":"7.0","script_version":"0.5.1","2":"0.5.1","version_comment":"version : 0.5.1\r\n\r\nplugin\/sendmail.vim\r\n- Remove document. Move to document directory.\r\n- Fix error check logic, 'sendmail.conf is not configured.'.\r\n\r\ndoc\/sendmail.txt\r\n- Created.\r\n\r\nplugin\/sendmail.py\r\n- Send mail in background.\r\n\r\nplugin\/sendmail.conf\r\n- Removed.\r\n\r\n","3":"version : 0.5.1\r\n\r\nplugin\/sendmail.vim\r\n- Remove document. Move to document directory.\r\n- Fix error check logic, 'sendmail.conf is not configured.'.\r\n\r\ndoc\/sendmail.txt\r\n- Created.\r\n\r\nplugin\/sendmail.py\r\n- Send mail in background.\r\n\r\nplugin\/sendmail.conf\r\n- Removed.\r\n\r\n","package":"sendmail.vba.zip","4":"sendmail.vba.zip","src_id":"9126","5":"9126","creation_date":"1218698026","6":"1218698026"},{"0":"2341","vim_version":"7.0","1":"7.0","script_version":"0.5.1","2":"0.5.1","version_comment":"Help Document In Japanese.","3":"Help Document In Japanese.","package":"sendmail_doc_ja.zip","4":"sendmail_doc_ja.zip","src_id":"9125","5":"9125","creation_date":"1218697970","6":"1218697970"},{"0":"2341","vim_version":"7.0","1":"7.0","script_version":"0.5","2":"0.5","version_comment":"Initial upload","3":"Initial upload","package":"sendmail.vba","4":"sendmail.vba","src_id":"9121","5":"9121","creation_date":"1218658519","6":"1218658519"}]},"2340":{"script_id":"2340","0":"2340","script_name":"molokai","1":"molokai","script_type":"color scheme","2":"color scheme","summary":"A port of the monokai scheme for TextMate","3":"A port of the monokai scheme for TextMate","description":"Molokai is a Vim port of the monokai theme for TextMate originally created by Wimer Hazenberg.\r\n\r\nBy default, it has a dark gray background based on the version created by Hamish Stuart Macpherson for the E editor.\r\n\r\nYou can see screenshots of the scheme at http:\/\/winterdom.com\/2008\/08\/molokaiforvim\r\n\r\n256-Color terminals are also supported, though there are some differences with the Gui version. Only the dark gray background style is supported on terminal vim at this time.\r\n\r\nMost up to date version can be found in the github repository: https:\/\/github.com\/tomasr\/molokai","4":"Molokai is a Vim port of the monokai theme for TextMate originally created by Wimer Hazenberg.\r\n\r\nBy default, it has a dark gray background based on the version created by Hamish Stuart Macpherson for the E editor.\r\n\r\nYou can see screenshots of the scheme at http:\/\/winterdom.com\/2008\/08\/molokaiforvim\r\n\r\n256-Color terminals are also supported, though there are some differences with the Gui version. Only the dark gray background style is supported on terminal vim at this time.\r\n\r\nMost up to date version can be found in the github repository: https:\/\/github.com\/tomasr\/molokai","install_details":"Just copy the file to your .vim\/colors folder. \r\n\r\nIf you prefer the scheme to match the original monokai background color, put this in your .vimrc file:\r\nlet g:molokai_original = 1","5":"Just copy the file to your .vim\/colors folder. \r\n\r\nIf you prefer the scheme to match the original monokai background color, put this in your .vimrc file:\r\nlet g:molokai_original = 1","first_name":"Tomas","6":"Tomas","last_name":"Restrepo","7":"Restrepo","releases":[{"0":"2340","vim_version":"7.0","1":"7.0","script_version":"1.1","2":"1.1","version_comment":"Added support for terminal version of Vim on terminals with 256-color support","3":"Added support for terminal version of Vim on terminals with 256-color support","package":"molokai.vim","4":"molokai.vim","src_id":"9750","5":"9750","creation_date":"1231035764","6":"1231035764"},{"0":"2340","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"molokai.vim","4":"molokai.vim","src_id":"9114","5":"9114","creation_date":"1218570380","6":"1218570380"}]},"2339":{"script_id":"2339","0":"2339","script_name":"simple pairs","1":"simple pairs","script_type":"utility","2":"utility","summary":"TextMate-like insert closing pair for brackets, parens, quotes (needs python)","3":"TextMate-like insert closing pair for brackets, parens, quotes (needs python)","description":"This is my first attempt at writing a vim script. It needs python support, and it's tested only in >7.1, but it should work in earlier versions as well. Drop me a line if it does and I'll update this description!\r\n\r\nIt will insert a closing pair when you type a quote (single and double), bracket, parenthesis, brace. It will also move over when you type the closing pair, and it will delete empty pairs when you hit backspace. This broadly mimics TextMate's behaviour for pairs of characters.\r\n\r\nIts main difference from all the others is that it is it not aggressive at all! It will try to do so only when it makes sense, that is:\r\n\r\n* at the end of the line\r\n* when the next character is one of: <space>,.: \r\n\r\nThat, simple as it looks, means that it will do its job when you're writing new code, but it will not mess up when you are editing code. \r\n\r\nIt's heavily biased towards Python, so if anybody has other use cases please send me an email!","4":"This is my first attempt at writing a vim script. It needs python support, and it's tested only in >7.1, but it should work in earlier versions as well. Drop me a line if it does and I'll update this description!\r\n\r\nIt will insert a closing pair when you type a quote (single and double), bracket, parenthesis, brace. It will also move over when you type the closing pair, and it will delete empty pairs when you hit backspace. This broadly mimics TextMate's behaviour for pairs of characters.\r\n\r\nIts main difference from all the others is that it is it not aggressive at all! It will try to do so only when it makes sense, that is:\r\n\r\n* at the end of the line\r\n* when the next character is one of: <space>,.: \r\n\r\nThat, simple as it looks, means that it will do its job when you're writing new code, but it will not mess up when you are editing code. \r\n\r\nIt's heavily biased towards Python, so if anybody has other use cases please send me an email!","install_details":"Put it in your .vim\/plugin directory and it should work.","5":"Put it in your .vim\/plugin directory and it should work.","first_name":"Orestis","6":"Orestis","last_name":"Markou","7":"Markou","releases":[{"0":"2339","vim_version":"7.0","1":"7.0","script_version":"0.2","2":"0.2","version_comment":"Version that actually works if it's the only python plugin you're using - sorry!","3":"Version that actually works if it's the only python plugin you're using - sorry!","package":"simple_pairs.vim","4":"simple_pairs.vim","src_id":"9107","5":"9107","creation_date":"1218379412","6":"1218379412"},{"0":"2339","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"simple_pairs.vim","4":"simple_pairs.vim","src_id":"9105","5":"9105","creation_date":"1218363345","6":"1218363345"}]},"2338":{"script_id":"2338","0":"2338","script_name":"bundle","1":"bundle","script_type":"utility","2":"utility","summary":"Load a series of files easily","3":"Load a series of files easily","description":"*bundle* is a Vim plugin to easily load a series of files which is called as\r\n\"bundle\".  For example, if you often edit files foo.c, bar.txt and baz.vim in\r\nproject named \"qux\", you can use \"|:LoadBundle| qux\" to load the files.\r\n\r\nThe correspondence of bundle names and lists of files can be configured by\r\nstatic way (|g:bundle_dictionary|) and dynamic way (|bundle-events|).\r\n\r\n\r\nRequirements:\r\n- Vim 7.1.299 or later\r\n\r\nLatest version:\r\nhttp:\/\/github.com\/kana\/vim-bundle\r\n\r\nDocument in HTML format:\r\nhttp:\/\/kana.github.com\/config\/vim\/bundle.html","4":"*bundle* is a Vim plugin to easily load a series of files which is called as\r\n\"bundle\".  For example, if you often edit files foo.c, bar.txt and baz.vim in\r\nproject named \"qux\", you can use \"|:LoadBundle| qux\" to load the files.\r\n\r\nThe correspondence of bundle names and lists of files can be configured by\r\nstatic way (|g:bundle_dictionary|) and dynamic way (|bundle-events|).\r\n\r\n\r\nRequirements:\r\n- Vim 7.1.299 or later\r\n\r\nLatest version:\r\nhttp:\/\/github.com\/kana\/vim-bundle\r\n\r\nDocument in HTML format:\r\nhttp:\/\/kana.github.com\/config\/vim\/bundle.html","install_details":"...","5":"...","first_name":"Kana","6":"Kana","last_name":"Natsuno","7":"Natsuno","releases":[{"0":"2338","vim_version":"7.0","1":"7.0","script_version":"0.0.2","2":"0.0.2","version_comment":"- Add |bundle#available_bundles()|.","3":"- Add |bundle#available_bundles()|.","package":"vim-bundle-0.0.2.zip","4":"vim-bundle-0.0.2.zip","src_id":"9133","5":"9133","creation_date":"1218923468","6":"1218923468"},{"0":"2338","vim_version":"7.0","1":"7.0","script_version":"0.0.1","2":"0.0.1","version_comment":"- Change the required version of Vim - 7.1.299 or later.\r\n- Add |:ArgsBundle|, |bundle#args()| and |bundle#files()|.","3":"- Change the required version of Vim - 7.1.299 or later.\r\n- Add |:ArgsBundle|, |bundle#args()| and |bundle#files()|.","package":"vim-bundle-0.0.1.zip","4":"vim-bundle-0.0.1.zip","src_id":"9101","5":"9101","creation_date":"1218339917","6":"1218339917"},{"0":"2338","vim_version":"7.0","1":"7.0","script_version":"0.0.0","2":"0.0.0","version_comment":"Initial upload","3":"Initial upload","package":"vim-bundle-0.0.0.zip","4":"vim-bundle-0.0.0.zip","src_id":"9093","5":"9093","creation_date":"1218258644","6":"1218258644"}]},"2337":{"script_id":"2337","0":"2337","script_name":"ku","1":"ku","script_type":"utility","2":"utility","summary":"An interface for anything","3":"An interface for anything","description":"*ku* is a Vim plugin to provide new interface for Vim.  With ku,\r\n\r\n- You can choose many items from various sources such as buffers, files and\r\n  others.  This selection is very efficient, because ku supports it by\r\n  automatic and elegant completion, so that you don't have to type much.\r\n\r\n- Then you can take an action on the selected item.  Various actions are\r\n  available for each kind of items.\r\n\r\n\r\nTo start a selection, execute |:Ku| or |ku#start()|.  |the-ku-window| will be\r\nopened at the top of the current tabpage.  The window is to select items and\r\nto do an action on a selected item.  In the window,\r\n\r\n- |ins-completion-menu| is automatically appeared to show available items.\r\n  As you input a character, the menu is updated to show more proper items for\r\n  the given input.\r\n\r\n  If you want to know how ku interpret what you input,\r\n  see |ku-pattern|, |ku-auto-component-completion| and |ku-prefix-expansion|.\r\n\r\n- If you find what you want in the menu, select it with <C-n> or <C-p>.  If\r\n  the first item in the menu is what you want, you don't have to select it.\r\n\r\n- Then you can take an action on the selected item with <Enter> or <Tab>.\r\n\r\n  - With <Enter>, ku executes the default action for the item.\r\n\r\n  - With <Tab>, ku shows a list of available actions for the item.  Each\r\n    action is labeled with a key to execute it.  If you type one of the keys,\r\n    the corresponding action will be executed.\r\n\r\n  <Enter> and <Tab> are just the default key bindings.  You can customize\r\n  them, of course.  See |ku-key-mappings| and |ku#default_key_mappings()|.\r\n  If you want to customize key bindings in a list of actions by <Tab>, see\r\n  |ku#custom_key()|, |ku-default-key-table| and |ku-key-table|.\r\n\r\n- If you don't want to take any action and stop to select, type <C-c> in any\r\n  mode.  The window is closed and the current tabpage is restored to the\r\n  previous state.\r\n\r\n\r\nIn ku, a kind of items is called \"source\".  Some sources are available by\r\ndefault.  See |ku-default-sources| for the details.  You can write your own\r\nsources if you want to select and to take action on something which is not\r\nprovided by the default sources.  To add sources, put the corresponding\r\nscripts into \"autoload\/ku\/\" directories in 'runtimepath'.  As scripts are put,\r\nku recognizes them automatically, so that you don't have to reboot Vim.  See\r\nalsso |ku-sources| for the details.\r\n\r\n\r\nScreenshots:\r\nhttp:\/\/www.flickr.com\/photos\/whileimautomaton\/tags\/vim-ku\/\r\n\r\nDemonstration movie:\r\nhttp:\/\/www.screencast.com\/t\/P6nJkJ0DE\r\n\r\n\r\nRequirements:\r\n- Vim 7.1.299 or later\r\n\r\nSources and related scripts:\r\nhttp:\/\/www.vim.org\/scripts\/script_search_results.php?keywords=ku\r\n\r\nLatest version:\r\nhttp:\/\/github.com\/kana\/vim-ku\r\n\r\nDocument in HTML format:\r\nhttp:\/\/kana.github.com\/config\/vim\/ku.html","4":"*ku* is a Vim plugin to provide new interface for Vim.  With ku,\r\n\r\n- You can choose many items from various sources such as buffers, files and\r\n  others.  This selection is very efficient, because ku supports it by\r\n  automatic and elegant completion, so that you don't have to type much.\r\n\r\n- Then you can take an action on the selected item.  Various actions are\r\n  available for each kind of items.\r\n\r\n\r\nTo start a selection, execute |:Ku| or |ku#start()|.  |the-ku-window| will be\r\nopened at the top of the current tabpage.  The window is to select items and\r\nto do an action on a selected item.  In the window,\r\n\r\n- |ins-completion-menu| is automatically appeared to show available items.\r\n  As you input a character, the menu is updated to show more proper items for\r\n  the given input.\r\n\r\n  If you want to know how ku interpret what you input,\r\n  see |ku-pattern|, |ku-auto-component-completion| and |ku-prefix-expansion|.\r\n\r\n- If you find what you want in the menu, select it with <C-n> or <C-p>.  If\r\n  the first item in the menu is what you want, you don't have to select it.\r\n\r\n- Then you can take an action on the selected item with <Enter> or <Tab>.\r\n\r\n  - With <Enter>, ku executes the default action for the item.\r\n\r\n  - With <Tab>, ku shows a list of available actions for the item.  Each\r\n    action is labeled with a key to execute it.  If you type one of the keys,\r\n    the corresponding action will be executed.\r\n\r\n  <Enter> and <Tab> are just the default key bindings.  You can customize\r\n  them, of course.  See |ku-key-mappings| and |ku#default_key_mappings()|.\r\n  If you want to customize key bindings in a list of actions by <Tab>, see\r\n  |ku#custom_key()|, |ku-default-key-table| and |ku-key-table|.\r\n\r\n- If you don't want to take any action and stop to select, type <C-c> in any\r\n  mode.  The window is closed and the current tabpage is restored to the\r\n  previous state.\r\n\r\n\r\nIn ku, a kind of items is called \"source\".  Some sources are available by\r\ndefault.  See |ku-default-sources| for the details.  You can write your own\r\nsources if you want to select and to take action on something which is not\r\nprovided by the default sources.  To add sources, put the corresponding\r\nscripts into \"autoload\/ku\/\" directories in 'runtimepath'.  As scripts are put,\r\nku recognizes them automatically, so that you don't have to reboot Vim.  See\r\nalsso |ku-sources| for the details.\r\n\r\n\r\nScreenshots:\r\nhttp:\/\/www.flickr.com\/photos\/whileimautomaton\/tags\/vim-ku\/\r\n\r\nDemonstration movie:\r\nhttp:\/\/www.screencast.com\/t\/P6nJkJ0DE\r\n\r\n\r\nRequirements:\r\n- Vim 7.1.299 or later\r\n\r\nSources and related scripts:\r\nhttp:\/\/www.vim.org\/scripts\/script_search_results.php?keywords=ku\r\n\r\nLatest version:\r\nhttp:\/\/github.com\/kana\/vim-ku\r\n\r\nDocument in HTML format:\r\nhttp:\/\/kana.github.com\/config\/vim\/ku.html","install_details":"...","5":"...","first_name":"Kana","6":"Kana","last_name":"Natsuno","7":"Natsuno","releases":[{"0":"2337","vim_version":"7.0","1":"7.0","script_version":"0.2.4.1","2":"0.2.4.1","version_comment":"Bug fixes:\n- |ku-file|: Fix a serious bug which was mixed in ku source file version 0.1.3.  See |ku-file-changelog-0.1.4| for the details.","3":"Bug fixes:\n- |ku-file|: Fix a serious bug which was mixed in ku source file version 0.1.3.  See |ku-file-changelog-0.1.4| for the details.","package":"vim-ku-0.2.4.1.zip","4":"vim-ku-0.2.4.1.zip","src_id":"10699","5":"10699","creation_date":"1243556989","6":"1243556989"},{"0":"2337","vim_version":"7.0","1":"7.0","script_version":"0.2.4","2":"0.2.4","version_comment":"Feature enhancements:\n- |ku-file|: Support to deal with files in archives.  See also |ku-file-changelog-0.1.3| for the details.\n\nMisc. improvements:\n- |filetype-ku|: Modify the default initialization on |the-ku-buffer|.  Old versions don't override existing key mappings.  New versions now override existing key mappings.  It is convenient for starters to use ku without any configuration.\n\n  For example, many people customize <Tab> to complete something in\n  Insert mode.  In such cases, old versions don't override <Tab> to\n  |<Plug>(ku-choose-an-action)|, but it's very inconvenient to use ku.\n  All key mappings defined by |ku#default_key_mappings()| are local to\n  a buffer, so that it's not necessary to avoid overriding.\n\n  Thanks to rphillips and other persons for reporting this problem.\n\nBug fixes:\n- |ku#restart()|: Fix a bug that is caused by a change in the previous version.  As ku#restart() is called, the prompt character will be inserted many times.","3":"Feature enhancements:\n- |ku-file|: Support to deal with files in archives.  See also |ku-file-changelog-0.1.3| for the details.\n\nMisc. improvements:\n- |filetype-ku|: Modify the default initialization on |the-ku-buffer|.  Old versions don't override existing key mappings.  New versions now override existing key mappings.  It is convenient for starters to use ku without any configuration.\n\n  For example, many people customize <Tab> to complete something in\n  Insert mode.  In such cases, old versions don't override <Tab> to\n  |<Plug>(ku-choose-an-action)|, but it's very inconvenient to use ku.\n  All key mappings defined by |ku#default_key_mappings()| are local to\n  a buffer, so that it's not necessary to avoid overriding.\n\n  Thanks to rphillips and other persons for reporting this problem.\n\nBug fixes:\n- |ku#restart()|: Fix a bug that is caused by a change in the previous version.  As ku#restart() is called, the prompt character will be inserted many times.","package":"vim-ku-0.2.4.zip","4":"vim-ku-0.2.4.zip","src_id":"10697","5":"10697","creation_date":"1243529040","6":"1243529040"},{"0":"2337","vim_version":"7.0","1":"7.0","script_version":"0.2.3","2":"0.2.3","version_comment":"Feature enhancements:\n- Add |g:ku_personal_runtime| to customize where information such as |ku-input-history| to be saved.\n- Add |:KuReload| and |ku#reload()| to reload the whole system of ku.\n\nMisc. improvements:\n- Improve an error message.\n- Add tests, not perfect yet.\n- |ku-input-history|: Change the directory to save input history.  Use the first directory in the default value of 'runtimepath', instead of the current value of 'runtimepath'.  Because some users customize 'runtimepath', and the first directory in such values may not refer a directory for personal settings.\n\nBug fixes:\n- Fix a bug that ku list the same sources many times if there are 2 or more source scripts which filenames are the same in 'runtimepath'.\n- Fix bugs that ku may be confuse if typeahead buffer is not empty at the beginning of a |ku-session|.\n- |ku#set_the_current_input_pattern()|:\n  - Fix a wrong description in the document.\n  - Fix a bug on the treatment of a given string.  If a given string starts with the same character as the prompt, that character is treated as the prompt and not a part of the given string, so it's not easy to set such strings.\n  - Fix a bug on the automatic completion.  The cursor position may be altered in several cases.\n\nSee also:\n- |ku-source-changelog-0.1.2|","3":"Feature enhancements:\n- Add |g:ku_personal_runtime| to customize where information such as |ku-input-history| to be saved.\n- Add |:KuReload| and |ku#reload()| to reload the whole system of ku.\n\nMisc. improvements:\n- Improve an error message.\n- Add tests, not perfect yet.\n- |ku-input-history|: Change the directory to save input history.  Use the first directory in the default value of 'runtimepath', instead of the current value of 'runtimepath'.  Because some users customize 'runtimepath', and the first directory in such values may not refer a directory for personal settings.\n\nBug fixes:\n- Fix a bug that ku list the same sources many times if there are 2 or more source scripts which filenames are the same in 'runtimepath'.\n- Fix bugs that ku may be confuse if typeahead buffer is not empty at the beginning of a |ku-session|.\n- |ku#set_the_current_input_pattern()|:\n  - Fix a wrong description in the document.\n  - Fix a bug on the treatment of a given string.  If a given string starts with the same character as the prompt, that character is treated as the prompt and not a part of the given string, so it's not easy to set such strings.\n  - Fix a bug on the automatic completion.  The cursor position may be altered in several cases.\n\nSee also:\n- |ku-source-changelog-0.1.2|","package":"vim-ku-0.2.3.zip","4":"vim-ku-0.2.3.zip","src_id":"10657","5":"10657","creation_date":"1242997924","6":"1242997924"},{"0":"2337","vim_version":"7.0","1":"7.0","script_version":"0.2.2","2":"0.2.2","version_comment":"Bug fixes:\n- Fix an assumption that the separator for pathes is \"\/\".  This assumption causes unexpected behavior on some environments such as Microsoft Windows.\n- Fix a wrong condition to use 'shellslash'.\n\nFeature enhancements:\n- Add API functions to deal with pathes.  See also:\n  - |ku#make_path()|\n  - |ku#path_separator()|\n\nSee also:\n- |ku-file-changelog-0.1.2|","3":"Bug fixes:\n- Fix an assumption that the separator for pathes is \"\/\".  This assumption causes unexpected behavior on some environments such as Microsoft Windows.\n- Fix a wrong condition to use 'shellslash'.\n\nFeature enhancements:\n- Add API functions to deal with pathes.  See also:\n  - |ku#make_path()|\n  - |ku#path_separator()|\n\nSee also:\n- |ku-file-changelog-0.1.2|","package":"vim-ku-0.2.2.zip","4":"vim-ku-0.2.2.zip","src_id":"10601","5":"10601","creation_date":"1242398147","6":"1242398147"},{"0":"2337","vim_version":"7.0","1":"7.0","script_version":"0.2.1","2":"0.2.1","version_comment":"Bug fixes:\n- |<Plug>(ku-choose-action)|: Fix a bug that an error message is displayed unexpectedly, whenever a key which is not associated with any action is pressed.\n- Fix a bug that the current source name in |the-ku-buffer| is not highlighted correctly in some cases.\n- Document: Fix a wrong description on the default value of |g:ku_history_reloading_style|.  It is \"idle\", not \"once\".\n- |ku__source|: Fix a bug that it doesn't exist for items which are not completed by ku.\n- |ku-action-left| and other actions: Fix a bug that they don't close a window or a tab page created by them even if |ku-action-default| is failed.\n\nIncompatible changes:\n- Change the behavior not to take any action if an input pattern is empty and there is no item, because there is nothing to do in such case.\n- Change the specification on |ku-action|.  Now the function corresponding to an action must return 0 if it succeeds, or a string which represents an error message if it fails.  Old versions don't touch on return values.\n\nMisc.:\n- Refactor the core.","3":"Bug fixes:\n- |<Plug>(ku-choose-action)|: Fix a bug that an error message is displayed unexpectedly, whenever a key which is not associated with any action is pressed.\n- Fix a bug that the current source name in |the-ku-buffer| is not highlighted correctly in some cases.\n- Document: Fix a wrong description on the default value of |g:ku_history_reloading_style|.  It is \"idle\", not \"once\".\n- |ku__source|: Fix a bug that it doesn't exist for items which are not completed by ku.\n- |ku-action-left| and other actions: Fix a bug that they don't close a window or a tab page created by them even if |ku-action-default| is failed.\n\nIncompatible changes:\n- Change the behavior not to take any action if an input pattern is empty and there is no item, because there is nothing to do in such case.\n- Change the specification on |ku-action|.  Now the function corresponding to an action must return 0 if it succeeds, or a string which represents an error message if it fails.  Old versions don't touch on return values.\n\nMisc.:\n- Refactor the core.","package":"vim-ku-0.2.1.zip","4":"vim-ku-0.2.1.zip","src_id":"10510","5":"10510","creation_date":"1241374374","6":"1241374374"},{"0":"2337","vim_version":"7.0","1":"7.0","script_version":"0.2.0","2":"0.2.0","version_comment":"- Add |ku__source|.\n- Fix a few assumptions on path separator.\n- Improve the performance to complete items.  Now it is 10 times faster than old versions.\n- Modify the sorting order of items.  If an item contains any character of |g:ku_component_separators|, it is prior to other items which don't contain that characters.  For example, if there are two items \"foo\/bar\" and \"foo-bar\", new versions put \"foo\/bar\" before \"foo-bar\", while old versions put \"foo-bar\" before \"foo\/bar\".  This change is to avoid selecting unexpected item with |ku-auto-component-completion|.\n- |ku-auto-component-completion|:\n  - Improve the conditions to activate.  Now it is not unexpectedly activated for some cases.\n  - Improve how many components to be completed.\n- |g:ku_acc_style|: New.\n\nIncompatible changes:\n- Change many points about |ku-sources| and |ku-action|.\n  - Sources for 0.1.x are not compatible with 0.2.x.\n  - |ku#{source}#gather_items()|:\n    - Change the naming rules about additional entries for each item: Old versions use \"_{source}_...\" and \"_ku_...\".  New versions use \"ku_{source}_...\" and \"ku__...\" instead.\n    - Add several rules on return values.\n  - |ku#{source}#gather_items()|: New API to implement.\n  - |ku#{source}#acc_valid_p()|: Change the default value if it is not defined.  Old versions always return true.  New versions always return false.\n  - |ku-special-sources|: Delete this concept.  Now all source scripts may provide more than one sources.\n  - |ku#{source}#available_sources()|: New function to implement.\n  - |ku-source-api|: Most of functions must take an additional argument about source name.\n  - |ku#{source}#event_handler()|: Delete.  This function is now split into the following functions:\n    - |ku#{source}#on_before_action()|\n    - |ku#{source}#on_source_enter()|\n    - |ku#{source}#on_source_leave()|\n- |ku-pattern|:\n  - Change the definition of \"word\" pattern.  Old versions use spaces and slashes as wildcards.  New versions use only spaces as wildcards.\n  - Add an assumption - see |ku-pattern-prefix-assumption|.","3":"- Add |ku__source|.\n- Fix a few assumptions on path separator.\n- Improve the performance to complete items.  Now it is 10 times faster than old versions.\n- Modify the sorting order of items.  If an item contains any character of |g:ku_component_separators|, it is prior to other items which don't contain that characters.  For example, if there are two items \"foo\/bar\" and \"foo-bar\", new versions put \"foo\/bar\" before \"foo-bar\", while old versions put \"foo-bar\" before \"foo\/bar\".  This change is to avoid selecting unexpected item with |ku-auto-component-completion|.\n- |ku-auto-component-completion|:\n  - Improve the conditions to activate.  Now it is not unexpectedly activated for some cases.\n  - Improve how many components to be completed.\n- |g:ku_acc_style|: New.\n\nIncompatible changes:\n- Change many points about |ku-sources| and |ku-action|.\n  - Sources for 0.1.x are not compatible with 0.2.x.\n  - |ku#{source}#gather_items()|:\n    - Change the naming rules about additional entries for each item: Old versions use \"_{source}_...\" and \"_ku_...\".  New versions use \"ku_{source}_...\" and \"ku__...\" instead.\n    - Add several rules on return values.\n  - |ku#{source}#gather_items()|: New API to implement.\n  - |ku#{source}#acc_valid_p()|: Change the default value if it is not defined.  Old versions always return true.  New versions always return false.\n  - |ku-special-sources|: Delete this concept.  Now all source scripts may provide more than one sources.\n  - |ku#{source}#available_sources()|: New function to implement.\n  - |ku-source-api|: Most of functions must take an additional argument about source name.\n  - |ku#{source}#event_handler()|: Delete.  This function is now split into the following functions:\n    - |ku#{source}#on_before_action()|\n    - |ku#{source}#on_source_enter()|\n    - |ku#{source}#on_source_leave()|\n- |ku-pattern|:\n  - Change the definition of \"word\" pattern.  Old versions use spaces and slashes as wildcards.  New versions use only spaces as wildcards.\n  - Add an assumption - see |ku-pattern-prefix-assumption|.","package":"vim-ku-0.2.0.zip","4":"vim-ku-0.2.0.zip","src_id":"10479","5":"10479","creation_date":"1240920762","6":"1240920762"},{"0":"2337","vim_version":"7.0","1":"7.0","script_version":"0.1.9","2":"0.1.9","version_comment":"- Add |g:ku_history_reloading_style|.\n- Change the default timings to reload and to save |ku-input-history|.  See also \"idle\" on |g:ku_history_reloading_style|.  Old versions use \"each\", but \"idle\" is used instead from now on.","3":"- Add |g:ku_history_reloading_style|.\n- Change the default timings to reload and to save |ku-input-history|.  See also \"idle\" on |g:ku_history_reloading_style|.  Old versions use \"each\", but \"idle\" is used instead from now on.","package":"vim-ku-0.1.9.zip","4":"vim-ku-0.1.9.zip","src_id":"9733","5":"9733","creation_date":"1230674035","6":"1230674035"},{"0":"2337","vim_version":"7.0","1":"7.0","script_version":"0.1.8","2":"0.1.8","version_comment":"- Add |g:ku_choosing_actions_sorting_style|.\n- Change the sorting style of |<Plug>(ku-choose-an-action)|.  See also |g:ku_choosing_actions_sorting_style|.\n- Fix some bugs - see |ku-buffer-changelog| and |ku-file-changelog|.","3":"- Add |g:ku_choosing_actions_sorting_style|.\n- Change the sorting style of |<Plug>(ku-choose-an-action)|.  See also |g:ku_choosing_actions_sorting_style|.\n- Fix some bugs - see |ku-buffer-changelog| and |ku-file-changelog|.","package":"vim-ku-0.1.8.zip","4":"vim-ku-0.1.8.zip","src_id":"9721","5":"9721","creation_date":"1230109236","6":"1230109236"},{"0":"2337","vim_version":"7.0","1":"7.0","script_version":"0.1.7","2":"0.1.7","version_comment":"- Include new source |ku-source|.\n- Change the default value of |g:ku_history_added_p|.  Now it also omits patterns for source |ku-source|.\n- Add |<Plug>(ku-choose-source)| and the default key mapping for it (see |ku#default_key_mappings()|).\n- Add |ku#get_the_current_input_pattern()|.\n- Add |ku#set_the_current_input_pattern()|.\n- Fix typos in this document.\n- Revise the internal stuffs.\n- Change |ku#restart()| to use the last inputted pattern and the last active source.  Old versions don't use ones if a selection is canceled by |<Plug>(ku-cancel)|.\n- Add |ku-action-selection| and the entry for it in |ku-default-key-table|.\n- Show an additional message while choosing an action for |<Plug>(ku-do-persistent-action)|.  In older versions, it cannot be distinct from a message either |<Plug>(ku-do-persistent-action)| or |<Plug>(choose-an-action)| is used.\n\nIncompatible changes:\n- Remove |ku-action-persistent|; use |<Plug>(ku-do-persistent-action)| instead.\n- Change |ku-action-cancel| - now it cannot be overridden, though it should not be overridden from the beginning.\n- Don't add the current input pattern into |ku-input-history| if the action to be taken is |ku-action-cancel|.  Old versions do add, but it seems to be unexpected behabior.","3":"- Include new source |ku-source|.\n- Change the default value of |g:ku_history_added_p|.  Now it also omits patterns for source |ku-source|.\n- Add |<Plug>(ku-choose-source)| and the default key mapping for it (see |ku#default_key_mappings()|).\n- Add |ku#get_the_current_input_pattern()|.\n- Add |ku#set_the_current_input_pattern()|.\n- Fix typos in this document.\n- Revise the internal stuffs.\n- Change |ku#restart()| to use the last inputted pattern and the last active source.  Old versions don't use ones if a selection is canceled by |<Plug>(ku-cancel)|.\n- Add |ku-action-selection| and the entry for it in |ku-default-key-table|.\n- Show an additional message while choosing an action for |<Plug>(ku-do-persistent-action)|.  In older versions, it cannot be distinct from a message either |<Plug>(ku-do-persistent-action)| or |<Plug>(choose-an-action)| is used.\n\nIncompatible changes:\n- Remove |ku-action-persistent|; use |<Plug>(ku-do-persistent-action)| instead.\n- Change |ku-action-cancel| - now it cannot be overridden, though it should not be overridden from the beginning.\n- Don't add the current input pattern into |ku-input-history| if the action to be taken is |ku-action-cancel|.  Old versions do add, but it seems to be unexpected behabior.","package":"vim-ku-0.1.7.zip","4":"vim-ku-0.1.7.zip","src_id":"9646","5":"9646","creation_date":"1228982974","6":"1228982974"},{"0":"2337","vim_version":"7.0","1":"7.0","script_version":"0.1.6","2":"0.1.6","version_comment":"- Add |ku#switch_source()|.\n- Add |ku-action-persistent|, |<Plug>(ku-do-persistent-action)| and the default key mapping for it (see |ku#default_key_mappings()|).\n- Include new source |ku-history|.\n- Add |ku#available_source_p()|.\n- Change the default value of |g:ku_history_added_p|.  Now it also omits patterns for source |ku-history|.\n\nIncompatible changes:\n- Change the behavior of |:Ku| and |ku#start()| if ku is already active.  Old ones change the current source to the specified source.  New ones don't nothing.  Use |ku#switch_source()| to change the current source.\n- Change the specification of |g:ku_history_added_p|.  It took a single argument, but now, it takes 2 arguments.","3":"- Add |ku#switch_source()|.\n- Add |ku-action-persistent|, |<Plug>(ku-do-persistent-action)| and the default key mapping for it (see |ku#default_key_mappings()|).\n- Include new source |ku-history|.\n- Add |ku#available_source_p()|.\n- Change the default value of |g:ku_history_added_p|.  Now it also omits patterns for source |ku-history|.\n\nIncompatible changes:\n- Change the behavior of |:Ku| and |ku#start()| if ku is already active.  Old ones change the current source to the specified source.  New ones don't nothing.  Use |ku#switch_source()| to change the current source.\n- Change the specification of |g:ku_history_added_p|.  It took a single argument, but now, it takes 2 arguments.","package":"vim-ku-0.1.6.zip","4":"vim-ku-0.1.6.zip","src_id":"9631","5":"9631","creation_date":"1228744096","6":"1228744096"},{"0":"2337","vim_version":"7.0","1":"7.0","script_version":"0.1.5","2":"0.1.5","version_comment":"- Show the information about |ku-input-history| in |the-ku-buffer|.\n- |ku#custom_action()|: Accept \"common\" for {source2} to specify an\n  action from the default action table for all sources.  For example:\n>\n  call ku#custom_action('buffer', 'xyzzy', 'common', 'tab-Right')\n<\n- Modify |ku-action-right| and other actions to refer \"default\" action\n  from the default action table of the current source.  Because they\n  may fall into infinite loop if user-defined \"default\" action refers\n  \"default\" action.\n- Add |g:ku_history_size|.\n- Add |<Plug>(ku-older-history-and-source)| and\n  |<Plug>(ku-newer-history-and-source)|.\n- Add |<Plug>(ku-history-source)|.\n\nIncompatible changes:\n- Change the format of value returned by |ku#input_history()|.\n  Now it is a list of dictionaries, not a list of strings.","3":"- Show the information about |ku-input-history| in |the-ku-buffer|.\n- |ku#custom_action()|: Accept \"common\" for {source2} to specify an\n  action from the default action table for all sources.  For example:\n>\n  call ku#custom_action('buffer', 'xyzzy', 'common', 'tab-Right')\n<\n- Modify |ku-action-right| and other actions to refer \"default\" action\n  from the default action table of the current source.  Because they\n  may fall into infinite loop if user-defined \"default\" action refers\n  \"default\" action.\n- Add |g:ku_history_size|.\n- Add |<Plug>(ku-older-history-and-source)| and\n  |<Plug>(ku-newer-history-and-source)|.\n- Add |<Plug>(ku-history-source)|.\n\nIncompatible changes:\n- Change the format of value returned by |ku#input_history()|.\n  Now it is a list of dictionaries, not a list of strings.","package":"vim-ku-0.1.5.zip","4":"vim-ku-0.1.5.zip","src_id":"9629","5":"9629","creation_date":"1228667964","6":"1228667964"},{"0":"2337","vim_version":"7.0","1":"7.0","script_version":"0.1.4","2":"0.1.4","version_comment":"- Add |ku#{source}#acc_valid_p()| to filter items for\n  |ku-auto-component-completion|.\n- Add |g:ku_history_added_p|.\n- Fix an error when input history becomes larger than its maximum\n  size.\n- Add a way to disable a specific action.  See |ku-disable-action|.\n- Set 'filetype' of |the-ku-buffer| to \"ku\".\n- Add syntax highlighting for |the-ku-buffer| and messages by\n  |<Plug>(ku-choose-an-action)|.\n- Refactor on minor stuffs.\n\nIncompatible changes:\n- Don't publish \"User plugin-ku-buffer-initialized\".\n  Use \"FileType ku\" and\/or filetype plugin instead.","3":"- Add |ku#{source}#acc_valid_p()| to filter items for\n  |ku-auto-component-completion|.\n- Add |g:ku_history_added_p|.\n- Fix an error when input history becomes larger than its maximum\n  size.\n- Add a way to disable a specific action.  See |ku-disable-action|.\n- Set 'filetype' of |the-ku-buffer| to \"ku\".\n- Add syntax highlighting for |the-ku-buffer| and messages by\n  |<Plug>(ku-choose-an-action)|.\n- Refactor on minor stuffs.\n\nIncompatible changes:\n- Don't publish \"User plugin-ku-buffer-initialized\".\n  Use \"FileType ku\" and\/or filetype plugin instead.","package":"vim-ku-0.1.4.zip","4":"vim-ku-0.1.4.zip","src_id":"9351","5":"9351","creation_date":"1223994713","6":"1223994713"},{"0":"2337","vim_version":"7.0","1":"7.0","script_version":"0.1.3","2":"0.1.3","version_comment":"- Inconpatible change:\n  - For |ku-special-sources|, |ku-source-api| takes the name of the\n    current source as the 1st argument.\n  - |ku-SourceEnter| and |ku-SourceLeave| don't take extra argument.\n- |ku#custom_action()|: Add new way to specify {function}.\n- |ku#start()|: Add {initial-pattern}.\n- Show some information on the selected item while choosing action.\n- Add |ku-input-history|.\n- Add |ku#restart()|.\n- Add source-specific priority on sorting items.  See\n  |_ku_sort_priority| for the detail.","3":"- Inconpatible change:\n  - For |ku-special-sources|, |ku-source-api| takes the name of the\n    current source as the 1st argument.\n  - |ku-SourceEnter| and |ku-SourceLeave| don't take extra argument.\n- |ku#custom_action()|: Add new way to specify {function}.\n- |ku#start()|: Add {initial-pattern}.\n- Show some information on the selected item while choosing action.\n- Add |ku-input-history|.\n- Add |ku#restart()|.\n- Add source-specific priority on sorting items.  See\n  |_ku_sort_priority| for the detail.","package":"vim-ku-0.1.3.zip","4":"vim-ku-0.1.3.zip","src_id":"9290","5":"9290","creation_date":"1222604900","6":"1222604900"},{"0":"2337","vim_version":"7.0","1":"7.0","script_version":"0.1.2","2":"0.1.2","version_comment":"- Fix a bug in |ku-prefix-expansion| - it didn't expand proper prefix if there are 2 or more prefixes which have the same head part.  For example, if there are prefixes \"ab\", \"abc\", \"abcd\" and so forth, it is not possible to predict which prefix will be expanded for user input \"abcd\/efgh\".  It should expand \"abcd\", but it may use \"abc\" or \"ab\" instead.\r\n- Add |ku-assumptions|.\r\n- Change the name of the ku buffer for Microsoft Windows to avoid unexpected behavior (see |g:ku_buffer_name| for the detail).\r\n- Add |g:ku_buffer_name|.\r\n- Improve |ku-auto-directory-completion|.  Now the feature is called as |ku-auto-component-completion|.\r\n- Fix a bug in |ku-auto-directory-completion|.  It may raise an error if user input contains a special character.\r\n- Add |ku-prefix-expansion|.\r\n- Fix |:KuDoAction| to check whether ku is active or not.\r\n- Improve the performance of |ku#available_sources()|.\r\n- Add priorities for |ku-sources-list|.\r\n","3":"- Fix a bug in |ku-prefix-expansion| - it didn't expand proper prefix if there are 2 or more prefixes which have the same head part.  For example, if there are prefixes \"ab\", \"abc\", \"abcd\" and so forth, it is not possible to predict which prefix will be expanded for user input \"abcd\/efgh\".  It should expand \"abcd\", but it may use \"abc\" or \"ab\" instead.\r\n- Add |ku-assumptions|.\r\n- Change the name of the ku buffer for Microsoft Windows to avoid unexpected behavior (see |g:ku_buffer_name| for the detail).\r\n- Add |g:ku_buffer_name|.\r\n- Improve |ku-auto-directory-completion|.  Now the feature is called as |ku-auto-component-completion|.\r\n- Fix a bug in |ku-auto-directory-completion|.  It may raise an error if user input contains a special character.\r\n- Add |ku-prefix-expansion|.\r\n- Fix |:KuDoAction| to check whether ku is active or not.\r\n- Improve the performance of |ku#available_sources()|.\r\n- Add priorities for |ku-sources-list|.\r\n","package":"vim-ku-0.1.2.zip","4":"vim-ku-0.1.2.zip","src_id":"9134","5":"9134","creation_date":"1218923554","6":"1218923554"},{"0":"2337","vim_version":"7.0","1":"7.0","script_version":"0.1.1","2":"0.1.1","version_comment":"- Add |ku-special-sources|.\r\n- Remove the feature to provide |metarw-schemes| as |ku-sources|.\r\n  This feature is implemented as a special source and it is included\r\n  in |metarw| 0.0.1 or later.\r\n- Fix requirements - ku uses |fnameescape()| which is added since Vim\r\n  7.1.299.  (thanks to id:thinca)","3":"- Add |ku-special-sources|.\r\n- Remove the feature to provide |metarw-schemes| as |ku-sources|.\r\n  This feature is implemented as a special source and it is included\r\n  in |metarw| 0.0.1 or later.\r\n- Fix requirements - ku uses |fnameescape()| which is added since Vim\r\n  7.1.299.  (thanks to id:thinca)","package":"vim-ku-0.1.1.zip","4":"vim-ku-0.1.1.zip","src_id":"9102","5":"9102","creation_date":"1218340093","6":"1218340093"},{"0":"2337","vim_version":"7.0","1":"7.0","script_version":"0.1.0","2":"0.1.0","version_comment":"Initial upload.","3":"Initial upload.","package":"vim-ku-0.1.0.zip","4":"vim-ku-0.1.0.zip","src_id":"9097","5":"9097","creation_date":"1218259334","6":"1218259334"}]},"2336":{"script_id":"2336","0":"2336","script_name":"metarw-git","1":"metarw-git","script_type":"utility","2":"utility","summary":"metarw scheme: git","3":"metarw scheme: git","description":"*metarw-git* is a scheme for |metarw| to read or to browse various objects in\r\na git repository with fakepaths like \"git:HEAD~3:src\/ui.c\".\r\n\r\nNote that this scheme just supports reading from an object.  Writing to an\r\nobject is not supported.\r\n\r\n\r\nRequirements:\r\n- Vim 7.1.299 or later\r\n- metarw 0.0.0 or later (vimscript#2335)\r\n\r\nLatest version:\r\nhttp:\/\/github.com\/kana\/vim-metarw-git\r\n\r\nDocument in HTML format:\r\nhttp:\/\/kana.github.com\/config\/vim\/metarw-git.html","4":"*metarw-git* is a scheme for |metarw| to read or to browse various objects in\r\na git repository with fakepaths like \"git:HEAD~3:src\/ui.c\".\r\n\r\nNote that this scheme just supports reading from an object.  Writing to an\r\nobject is not supported.\r\n\r\n\r\nRequirements:\r\n- Vim 7.1.299 or later\r\n- metarw 0.0.0 or later (vimscript#2335)\r\n\r\nLatest version:\r\nhttp:\/\/github.com\/kana\/vim-metarw-git\r\n\r\nDocument in HTML format:\r\nhttp:\/\/kana.github.com\/config\/vim\/metarw-git.html","install_details":"...","5":"...","first_name":"Kana","6":"Kana","last_name":"Natsuno","7":"Natsuno","releases":[{"0":"2336","vim_version":"7.0","1":"7.0","script_version":"0.0.3","2":"0.0.3","version_comment":"- When completing branches, remove \"remotes\/\" prefix from remote-tracking branches.\n- Fix not to complete wrong or unnecessary stuffs as branches.  For example, \"(no branch)\", \"origin\/HEAD -> origin\/master\", etc.","3":"- When completing branches, remove \"remotes\/\" prefix from remote-tracking branches.\n- Fix not to complete wrong or unnecessary stuffs as branches.  For example, \"(no branch)\", \"origin\/HEAD -> origin\/master\", etc.","package":"vim-metarw-git-0.0.3.zip","4":"vim-metarw-git-0.0.3.zip","src_id":"10583","5":"10583","creation_date":"1242147205","6":"1242147205"},{"0":"2336","vim_version":"7.0","1":"7.0","script_version":"0.0.2","2":"0.0.2","version_comment":"- Fix a bug that metarw-git uses wrong function to escape file-like arguments to shells.  Thanks @thinca for reporting this.","3":"- Fix a bug that metarw-git uses wrong function to escape file-like arguments to shells.  Thanks @thinca for reporting this.","package":"vim-metarw-git-0.0.2.zip","4":"vim-metarw-git-0.0.2.zip","src_id":"10536","5":"10536","creation_date":"1241548930","6":"1241548930"},{"0":"2336","vim_version":"7.0","1":"7.0","script_version":"0.0.1","2":"0.0.1","version_comment":"- Fix requirements - metarw-git uses |fnameescape()| which is added\r\n  since Vim 7.1.299.  (thanks to id:thinca)","3":"- Fix requirements - metarw-git uses |fnameescape()| which is added\r\n  since Vim 7.1.299.  (thanks to id:thinca)","package":"vim-metarw-git-0.0.1.zip","4":"vim-metarw-git-0.0.1.zip","src_id":"9104","5":"9104","creation_date":"1218340324","6":"1218340324"},{"0":"2336","vim_version":"7.0","1":"7.0","script_version":"0.0.0","2":"0.0.0","version_comment":"Initial upload.","3":"Initial upload.","package":"vim-metarw-git-0.0.0.zip","4":"vim-metarw-git-0.0.0.zip","src_id":"9095","5":"9095","creation_date":"1218259273","6":"1218259273"}]},"2335":{"script_id":"2335","0":"2335","script_name":"metarw","1":"metarw","script_type":"utility","2":"utility","summary":"a framework to read\/write a fake:path","3":"a framework to read\/write a fake:path","description":"*metarw* is a Vim plugin to provide a framework to read\/write a file-like\r\nargument of which name is written in URI-like notation such as\r\n\"git:master:src\/ui.c\".  metarw also provides content browser like |netrw|'s\r\none for some sorts of argumetns if they are given to :edit or other command.\r\n\r\n\r\nRequirements:\r\n- Vim 7.1.299 or later\r\n\r\nOptionals:\r\n- |metarw-scheme-script| such as |metarw-git| (vimscript#2336)\r\n- |ku| (vimscript#2337) and |ku-metarw| (vimscript#2344)\r\n\r\nDemo:\r\n- http:\/\/www.screencast.com\/t\/fCc8cFaiQj\r\n\r\nLatest version:\r\nhttp:\/\/github.com\/kana\/vim-metarw\r\n\r\nDocument in HTML format:\r\nhttp:\/\/kana.github.com\/config\/vim\/metarw.html","4":"*metarw* is a Vim plugin to provide a framework to read\/write a file-like\r\nargument of which name is written in URI-like notation such as\r\n\"git:master:src\/ui.c\".  metarw also provides content browser like |netrw|'s\r\none for some sorts of argumetns if they are given to :edit or other command.\r\n\r\n\r\nRequirements:\r\n- Vim 7.1.299 or later\r\n\r\nOptionals:\r\n- |metarw-scheme-script| such as |metarw-git| (vimscript#2336)\r\n- |ku| (vimscript#2337) and |ku-metarw| (vimscript#2344)\r\n\r\nDemo:\r\n- http:\/\/www.screencast.com\/t\/fCc8cFaiQj\r\n\r\nLatest version:\r\nhttp:\/\/github.com\/kana\/vim-metarw\r\n\r\nDocument in HTML format:\r\nhttp:\/\/kana.github.com\/config\/vim\/metarw.html","install_details":"...","5":"...","first_name":"Kana","6":"Kana","last_name":"Natsuno","7":"Natsuno","releases":[{"0":"2335","vim_version":"7.0","1":"7.0","script_version":"0.0.4","2":"0.0.4","version_comment":"- Refine the document.\n- |metarw#{scheme}#write()|:\n  - Fix a bug that some kind of errors are not handled properly.\n  - Add a way to execute a script after writing.  See |metarw#{scheme}#write()-write| for the details.","3":"- Refine the document.\n- |metarw#{scheme}#write()|:\n  - Fix a bug that some kind of errors are not handled properly.\n  - Add a way to execute a script after writing.  See |metarw#{scheme}#write()-write| for the details.","package":"vim-metarw-0.0.4.zip","4":"vim-metarw-0.0.4.zip","src_id":"10667","5":"10667","creation_date":"1243067637","6":"1243067637"},{"0":"2335","vim_version":"7.0","1":"7.0","script_version":"0.0.3","2":"0.0.3","version_comment":"- |metarw#{scheme}#write()|:\n  - Fix wrong implementation.\n  - Add new type of return value \"done\".","3":"- |metarw#{scheme}#write()|:\n  - Fix wrong implementation.\n  - Add new type of return value \"done\".","package":"vim-metarw-0.0.3.zip","4":"vim-metarw-0.0.3.zip","src_id":"9208","5":"9208","creation_date":"1220267892","6":"1220267892"},{"0":"2335","vim_version":"7.0","1":"7.0","script_version":"0.0.2","2":"0.0.2","version_comment":"- Separate |ku-source-metarw| as a independent package.","3":"- Separate |ku-source-metarw| as a independent package.","package":"vim-metarw-0.0.2.zip","4":"vim-metarw-0.0.2.zip","src_id":"9135","5":"9135","creation_date":"1218923964","6":"1218923964"},{"0":"2335","vim_version":"7.0","1":"7.0","script_version":"0.0.1","2":"0.0.1","version_comment":"- Add a special source of ku (see |metarw-schemes-as-ku-sources|).\r\n- Fix autocommands not to hook fakepaths with any schene name which\r\n  consists of less than 2 characters.  Old definitions incorrectly\r\n  recognized paths with a drive letter in Microsoft Windows\r\n  environment as a fakepath.  (thanks to id:thinca)\r\n- Add 2 rules on the name of a scheme (see |metarw-scheme|).\r\n- Fix plugin\/metarw.vim to be properly reloadable.\r\n- Fix requirements - metarw uses |fnameescape()| which is added since\r\n  Vim 7.1.299.  (thanks to id:thinca)","3":"- Add a special source of ku (see |metarw-schemes-as-ku-sources|).\r\n- Fix autocommands not to hook fakepaths with any schene name which\r\n  consists of less than 2 characters.  Old definitions incorrectly\r\n  recognized paths with a drive letter in Microsoft Windows\r\n  environment as a fakepath.  (thanks to id:thinca)\r\n- Add 2 rules on the name of a scheme (see |metarw-scheme|).\r\n- Fix plugin\/metarw.vim to be properly reloadable.\r\n- Fix requirements - metarw uses |fnameescape()| which is added since\r\n  Vim 7.1.299.  (thanks to id:thinca)","package":"vim-metarw-0.0.1.zip","4":"vim-metarw-0.0.1.zip","src_id":"9103","5":"9103","creation_date":"1218340243","6":"1218340243"},{"0":"2335","vim_version":"7.0","1":"7.0","script_version":"0.0.0","2":"0.0.0","version_comment":"Initial upload.","3":"Initial upload.","package":"vim-metarw-0.0.0.zip","4":"vim-metarw-0.0.0.zip","src_id":"9094","5":"9094","creation_date":"1218259232","6":"1218259232"}]},"2334":{"script_id":"2334","0":"2334","script_name":"backup.vim","1":"backup.vim","script_type":"utility","2":"utility","summary":"Puts backups where they belong: out of the way","3":"Puts backups where they belong: out of the way","description":"backup.vim stores backups out of the way in the ~\/.vim_plugins\/vim_backup directory.\r\n\r\nEach file is split into it\\'s file name and path, the md5sum of the path is used to create a unique subfolder in ~\/.vim_plugins\/vim_backup, and the files are backed up into that folder.  This ensures that your files are backed up, that your directories are not cluttered with *~ files, and that each file that you edit has it\\'s own unique backup.\r\n","4":"backup.vim stores backups out of the way in the ~\/.vim_plugins\/vim_backup directory.\r\n\r\nEach file is split into it\\'s file name and path, the md5sum of the path is used to create a unique subfolder in ~\/.vim_plugins\/vim_backup, and the files are backed up into that folder.  This ensures that your files are backed up, that your directories are not cluttered with *~ files, and that each file that you edit has it\\'s own unique backup.\r\n","install_details":"This script requires that vim was built with python enabled\r\n\r\nSimply copy backup.vim to ${HOME}\/.vim\/plugin\/","5":"This script requires that vim was built with python enabled\r\n\r\nSimply copy backup.vim to ${HOME}\/.vim\/plugin\/","first_name":"Nathan","6":"Nathan","last_name":"Lawrence","7":"Lawrence","releases":[{"0":"2334","vim_version":"7.0","1":"7.0","script_version":"0.4","2":"0.4","version_comment":"Initial upload","3":"Initial upload","package":"backup.vim","4":"backup.vim","src_id":"9089","5":"9089","creation_date":"1218194464","6":"1218194464"}]},"2333":{"script_id":"2333","0":"2333","script_name":"session.vim","1":"session.vim","script_type":"utility","2":"utility","summary":"A simple, automatic, no-nonsense, out of your way session manager","3":"A simple, automatic, no-nonsense, out of your way session manager","description":"session.vim is the easy way to do vim sessions.  A session is automatically started or restored whenever you open vim with a single file, or no files.\r\n\r\nTo delete a session, type :Sdelete, and the session will be deleted upon exiting vim.\r\n\r\nTo prevent a session from starting, use the g:session_blacklist variable:\r\nlet g:session_blacklist = ['\\.swp$','\\.tmp$','^\\.']\r\n\r\nThere is also a g:session_whitelist variable for easy refinement.\r\nlet g:session_whitelist = ['^\\.vimrc$']","4":"session.vim is the easy way to do vim sessions.  A session is automatically started or restored whenever you open vim with a single file, or no files.\r\n\r\nTo delete a session, type :Sdelete, and the session will be deleted upon exiting vim.\r\n\r\nTo prevent a session from starting, use the g:session_blacklist variable:\r\nlet g:session_blacklist = ['\\.swp$','\\.tmp$','^\\.']\r\n\r\nThere is also a g:session_whitelist variable for easy refinement.\r\nlet g:session_whitelist = ['^\\.vimrc$']","install_details":"This script requires that vim was built with python enabled.\r\n\r\nSimply copy session.vim to ${HOME}\/.vim\/plugin.","5":"This script requires that vim was built with python enabled.\r\n\r\nSimply copy session.vim to ${HOME}\/.vim\/plugin.","first_name":"Nathan","6":"Nathan","last_name":"Lawrence","7":"Lawrence","releases":[{"0":"2333","vim_version":"7.0","1":"7.0","script_version":"0.9","2":"0.9","version_comment":"Initial upload","3":"Initial upload","package":"session.vim","4":"session.vim","src_id":"9088","5":"9088","creation_date":"1218193964","6":"1218193964"}]},"2332":{"script_id":"2332","0":"2332","script_name":"pathogen.vim","1":"pathogen.vim","script_type":"utility","2":"utility","summary":"Poor man's package manager. Easy manipulation of 'runtimepath' et al","3":"Poor man's package manager. Easy manipulation of 'runtimepath' et al","description":"Manage your 'runtimepath' with ease.  In practical terms, pathogen.vim makes it super easy to install plugins and runtime files in their own private directories.\r\n\r\nAdd this to your vimrc:\r\n\r\n    execute pathogen#infect()\r\n\r\nNow any plugins you wish to install can be extracted to a subdirectory under ~\/.vim\/bundle, and they will be added to the 'runtimepath'.\r\n\r\nUse :Helptags to run :helptags on every doc\/ directory in your 'runtimepath'.\r\n\r\nFor more detailed, better formatted documentation, see the README on GitHub:\r\n\r\nhttp:\/\/github.com\/tpope\/vim-pathogen","4":"Manage your 'runtimepath' with ease.  In practical terms, pathogen.vim makes it super easy to install plugins and runtime files in their own private directories.\r\n\r\nAdd this to your vimrc:\r\n\r\n    execute pathogen#infect()\r\n\r\nNow any plugins you wish to install can be extracted to a subdirectory under ~\/.vim\/bundle, and they will be added to the 'runtimepath'.\r\n\r\nUse :Helptags to run :helptags on every doc\/ directory in your 'runtimepath'.\r\n\r\nFor more detailed, better formatted documentation, see the README on GitHub:\r\n\r\nhttp:\/\/github.com\/tpope\/vim-pathogen","install_details":"Install in ~\/.vim\/autoload (~\\vimfiles\\autoload on Windows). Or copy and paste:\r\n\r\nmkdir -p ~\/.vim\/autoload ~\/.vim\/bundle\r\ncurl -LSso ~\/.vim\/autoload\/pathogen.vim https:\/\/tpo.pe\/pathogen.vim","5":"Install in ~\/.vim\/autoload (~\\vimfiles\\autoload on Windows). Or copy and paste:\r\n\r\nmkdir -p ~\/.vim\/autoload ~\/.vim\/bundle\r\ncurl -LSso ~\/.vim\/autoload\/pathogen.vim https:\/\/tpo.pe\/pathogen.vim","first_name":"Tim","6":"Tim","last_name":"Pope","7":"Pope","releases":[{"0":"2332","vim_version":"7.0","1":"7.0","script_version":"2.4","2":"2.4","version_comment":"Use $VIMBLACKLIST to temporarily disable bundles.\r\nAllow disabling rest of vimrc by adding it to blacklist.\r\nExpand bundle\/{a,b} as bundle\/a and bundle\/b.\r\nExperimental: Support \"vimfiles\" subdirectory.\r\nWork around weird lockup on ancient Vim.\r\nRestore disabling of paths ending in ~.","3":"Use $VIMBLACKLIST to temporarily disable bundles.\r\nAllow disabling rest of vimrc by adding it to blacklist.\r\nExpand bundle\/{a,b} as bundle\/a and bundle\/b.\r\nExperimental: Support \"vimfiles\" subdirectory.\r\nWork around weird lockup on ancient Vim.\r\nRestore disabling of paths ending in ~.","package":"pathogen.zip","4":"pathogen.zip","src_id":"23828","5":"23828","creation_date":"1451088842","6":"1451088842"},{"0":"2332","vim_version":"7.0","1":"7.0","script_version":"2.3","2":"2.3","version_comment":"Deprecation warnings.\r\nIntroduce pathogen#interpose() to replace incubate().\r\nFix glob issues with fish shell.\r\nSilence all errors in :helptags.","3":"Deprecation warnings.\r\nIntroduce pathogen#interpose() to replace incubate().\r\nFix glob issues with fish shell.\r\nSilence all errors in :helptags.","package":"pathogen.zip","4":"pathogen.zip","src_id":"21650","5":"21650","creation_date":"1395433039","6":"1395433039"},{"0":"2332","vim_version":"7.0","1":"7.0","script_version":"2.2","2":"2.2","version_comment":"Accept multiple arguments to pathogen#infect().\r\nFix errors in deprecated methods.","3":"Accept multiple arguments to pathogen#infect().\r\nFix errors in deprecated methods.","package":"pathogen.vim","4":"pathogen.vim","src_id":"19375","5":"19375","creation_date":"1358204488","6":"1358204488"},{"0":"2332","vim_version":"7.0","1":"7.0","script_version":"2.1","2":"2.1","version_comment":"Deprecate :Vopen commands in favor of vimscript #4394.\r\nDeprecate pathogen#infect() calls on paths without explicit globs. (Change pathogen#infect('bundle') to pathogen#infect('bundle\/*')).\r\nIntroduce pathogen#incubate() to replace pathogen#runtime_append_all_bundles().\r\nIntroduce pathogen#surround() to replace pathogen#runtime_prepend_subdirectories().\r\nAllow absolute paths in g:pathogen_disabled.","3":"Deprecate :Vopen commands in favor of vimscript #4394.\r\nDeprecate pathogen#infect() calls on paths without explicit globs. (Change pathogen#infect('bundle') to pathogen#infect('bundle\/*')).\r\nIntroduce pathogen#incubate() to replace pathogen#runtime_append_all_bundles().\r\nIntroduce pathogen#surround() to replace pathogen#runtime_prepend_subdirectories().\r\nAllow absolute paths in g:pathogen_disabled.","package":"pathogen.vim","4":"pathogen.vim","src_id":"19365","5":"19365","creation_date":"1358127628","6":"1358127628"},{"0":"2332","vim_version":"7.0","1":"7.0","script_version":"2.0","2":"2.0","version_comment":"Add pathogen#infect() as primary entry point for basic setup.\r\nProvide :Helptags to generate all help tags.\r\nProvide :Vedit and related commands for editing runtime files.","3":"Add pathogen#infect() as primary entry point for basic setup.\r\nProvide :Helptags to generate all help tags.\r\nProvide :Vedit and related commands for editing runtime files.","package":"pathogen.vim","4":"pathogen.vim","src_id":"16224","5":"16224","creation_date":"1312934431","6":"1312934431"},{"0":"2332","vim_version":"7.0","1":"7.0","script_version":"1.3","2":"1.3","version_comment":"Allow disabling bundles with g:pathogen_disabled.\r\nFix appending \"after\" directories on Windows.","3":"Allow disabling bundles with g:pathogen_disabled.\r\nFix appending \"after\" directories on Windows.","package":"pathogen.vim","4":"pathogen.vim","src_id":"15192","5":"15192","creation_date":"1299797638","6":"1299797638"},{"0":"2332","vim_version":"7.0","1":"7.0","script_version":"1.2","2":"1.2","version_comment":"Add pathogen#legacyjoin() which escapes spaces for older options like 'path' and 'tags'.\r\nFix pathogen#join() to not escape spaces (caused problems on many Windows setups).\r\nAdd pathogen#uniq() to filter out duplicates.\r\nAdd pathogen#helptags() to generate helptags for everything in 'runtimepath'.","3":"Add pathogen#legacyjoin() which escapes spaces for older options like 'path' and 'tags'.\r\nFix pathogen#join() to not escape spaces (caused problems on many Windows setups).\r\nAdd pathogen#uniq() to filter out duplicates.\r\nAdd pathogen#helptags() to generate helptags for everything in 'runtimepath'.","package":"pathogen.vim","4":"pathogen.vim","src_id":"12116","5":"12116","creation_date":"1263688758","6":"1263688758"},{"0":"2332","vim_version":"7.0","1":"7.0","script_version":"1.1","2":"1.1","version_comment":"Properly escape spaces in paths","3":"Properly escape spaces in paths","package":"pathogen.vim","4":"pathogen.vim","src_id":"9394","5":"9394","creation_date":"1224812370","6":"1224812370"},{"0":"2332","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"pathogen.vim","4":"pathogen.vim","src_id":"9085","5":"9085","creation_date":"1218091814","6":"1218091814"}]},"2331":{"script_id":"2331","0":"2331","script_name":"chlordane.vim","1":"chlordane.vim","script_type":"color scheme","2":"color scheme","summary":"GHOST IN THE SHELL like colorscheme","3":"GHOST IN THE SHELL like colorscheme","description":"GHOST IN THE SHELL like colorscheme for the GUI.\r\nIt is inspired by the matrix colorscheme(vimscript#669).\r\n\r\nScreenshot at http:\/\/jstap.web.fc2.com\/chlordane.html","4":"GHOST IN THE SHELL like colorscheme for the GUI.\r\nIt is inspired by the matrix colorscheme(vimscript#669).\r\n\r\nScreenshot at http:\/\/jstap.web.fc2.com\/chlordane.html","install_details":"Put it in one of your colors directories.\r\nThen, just do :colorscheme chlordane","5":"Put it in one of your colors directories.\r\nThen, just do :colorscheme chlordane","first_name":"Kojo","6":"Kojo","last_name":"Sugita","7":"Sugita","releases":[{"0":"2331","vim_version":"7.0","1":"7.0","script_version":"1.2","2":"1.2","version_comment":"Added \"CursorLine\"","3":"Added \"CursorLine\"","package":"chlordane.vim","4":"chlordane.vim","src_id":"9536","5":"9536","creation_date":"1227286508","6":"1227286508"},{"0":"2331","vim_version":"7.0","1":"7.0","script_version":"1.1","2":"1.1","version_comment":"Changed TabLine","3":"Changed TabLine","package":"chlordane.vim","4":"chlordane.vim","src_id":"9141","5":"9141","creation_date":"1219037285","6":"1219037285"},{"0":"2331","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"chlordane.vim","4":"chlordane.vim","src_id":"9081","5":"9081","creation_date":"1218007896","6":"1218007896"}]},"2330":{"script_id":"2330","0":"2330","script_name":"log.vim","1":"log.vim","script_type":"utility","2":"utility","summary":"logging library","3":"logging library","description":"Usage:\r\n  \" in .vimrc\r\n  call log#init('ALL', ['\/dev\/stdout', '~\/.vim\/log.txt'])\r\n\r\n  \" in script\r\n  let s:log = log#getLogger(expand('<sfile>:t'))\r\n\r\n  function s:func()\r\n    call s:log.trace('start of func()')\r\n    if s:log.isDebugEnabled()\r\n      call s:log.debug('debug information')\r\n    endif\r\n    call s:log.trace('end of func()')\r\n  endfunction\r\n\r\n  \" If you want to distribute your script without log.vim, use :silent! or\r\n  \" exists().\r\n  silent! let s:log = log#getLogger(expand('<sfile>:t'))\r\n  function s:func()\r\n    silent! call s:log.info('aaa')\r\n    if exists('s:log')\r\n      call s:log.info('bbb')\r\n    endif\r\n  endfunction\r\n\r\nReference:\r\n\r\n  function log#init(level, targets [, format [, filter]])\r\n  @param level [String]\r\n    Log level.  One of 'ALL|TRACE|DEBUG|INFO|WARN|ERROR|FATAL|NONE'.\r\n    For example, when level is 'WARN', output of log.warn(), log.error() and\r\n    log.fatal() will appear in log.\r\n  @param targets [mixed]\r\n    Output target.  Filename or Function or Dictionary or List of these\r\n    values.\r\n    Filename:\r\n      Log is appended to the file.\r\n    Function:\r\n      function Log(str)\r\n        echo a:str\r\n      endfunction\r\n    Dictionary:\r\n      let Log = {}\r\n      function Log.__call__(str)\r\n        echohl Error\r\n        echo a:str\r\n        echohl None\r\n      endfunction\r\n  @param format [String]\r\n    Log format.  {expr} is replaced by eval(expr).  For example, {getpid()}\r\n    is useful to detect session.  Following special variables are available.\r\n    {level}   log level like DEBUG, INFO, etc...\r\n    {name}    log name specified by log#getLogger(name)\r\n    {msg}     log message\r\n    If this is 0, '', [] or {} (empty(format) is true), default is used.\r\n    default:  [{level}][{strftime(\"%Y-%m-%d %H:%M:%S\")}][{name}] {msg}\r\n  @param filter [mixed]\r\n    Pattern (String) or Function or Dictionary to filter log session.\r\n    Filter is applied to name that specified by log#getLogger(name).  If\r\n    result is false, logging session do not output any text.\r\n    Pattern (String):\r\n      name =~ Pattern\r\n    Function:\r\n      function Filter(name)\r\n        return a:name == 'mylib'\r\n      endfunction\r\n    Dictionary:\r\n      let Filter = {}\r\n      let Filter.filter = ['alib', 'blib', 'clib']\r\n      function Filter.__call__(name)\r\n        return index(self.filter, a:name) != -1\r\n      endfunction\r\n  @return void\r\n\r\n  function log#getLogger(name)\r\n  @param name [String] Log name\r\n  @return Logger object","4":"Usage:\r\n  \" in .vimrc\r\n  call log#init('ALL', ['\/dev\/stdout', '~\/.vim\/log.txt'])\r\n\r\n  \" in script\r\n  let s:log = log#getLogger(expand('<sfile>:t'))\r\n\r\n  function s:func()\r\n    call s:log.trace('start of func()')\r\n    if s:log.isDebugEnabled()\r\n      call s:log.debug('debug information')\r\n    endif\r\n    call s:log.trace('end of func()')\r\n  endfunction\r\n\r\n  \" If you want to distribute your script without log.vim, use :silent! or\r\n  \" exists().\r\n  silent! let s:log = log#getLogger(expand('<sfile>:t'))\r\n  function s:func()\r\n    silent! call s:log.info('aaa')\r\n    if exists('s:log')\r\n      call s:log.info('bbb')\r\n    endif\r\n  endfunction\r\n\r\nReference:\r\n\r\n  function log#init(level, targets [, format [, filter]])\r\n  @param level [String]\r\n    Log level.  One of 'ALL|TRACE|DEBUG|INFO|WARN|ERROR|FATAL|NONE'.\r\n    For example, when level is 'WARN', output of log.warn(), log.error() and\r\n    log.fatal() will appear in log.\r\n  @param targets [mixed]\r\n    Output target.  Filename or Function or Dictionary or List of these\r\n    values.\r\n    Filename:\r\n      Log is appended to the file.\r\n    Function:\r\n      function Log(str)\r\n        echo a:str\r\n      endfunction\r\n    Dictionary:\r\n      let Log = {}\r\n      function Log.__call__(str)\r\n        echohl Error\r\n        echo a:str\r\n        echohl None\r\n      endfunction\r\n  @param format [String]\r\n    Log format.  {expr} is replaced by eval(expr).  For example, {getpid()}\r\n    is useful to detect session.  Following special variables are available.\r\n    {level}   log level like DEBUG, INFO, etc...\r\n    {name}    log name specified by log#getLogger(name)\r\n    {msg}     log message\r\n    If this is 0, '', [] or {} (empty(format) is true), default is used.\r\n    default:  [{level}][{strftime(\"%Y-%m-%d %H:%M:%S\")}][{name}] {msg}\r\n  @param filter [mixed]\r\n    Pattern (String) or Function or Dictionary to filter log session.\r\n    Filter is applied to name that specified by log#getLogger(name).  If\r\n    result is false, logging session do not output any text.\r\n    Pattern (String):\r\n      name =~ Pattern\r\n    Function:\r\n      function Filter(name)\r\n        return a:name == 'mylib'\r\n      endfunction\r\n    Dictionary:\r\n      let Filter = {}\r\n      let Filter.filter = ['alib', 'blib', 'clib']\r\n      function Filter.__call__(name)\r\n        return index(self.filter, a:name) != -1\r\n      endfunction\r\n  @return void\r\n\r\n  function log#getLogger(name)\r\n  @param name [String] Log name\r\n  @return Logger object","install_details":"Put this file in autoload directory in your 'runtimepath'.","5":"Put this file in autoload directory in your 'runtimepath'.","first_name":"Yukihiro","6":"Yukihiro","last_name":"Nakadaira","7":"Nakadaira","releases":[{"0":"2330","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"log.vim","4":"log.vim","src_id":"9075","5":"9075","creation_date":"1217922156","6":"1217922156"}]},"2329":{"script_id":"2329","0":"2329","script_name":"Tumblr","1":"Tumblr","script_type":"utility","2":"utility","summary":"Post to Tumblr","3":"Post to Tumblr","description":"Script that allows you to post regular type posts to Tumblr.\r\n\r\nBegin a new post by opening a buffer and using the :TumblrNew command, when finished use the :TumblrPost command.\r\n","4":"Script that allows you to post regular type posts to Tumblr.\r\n\r\nBegin a new post by opening a buffer and using the :TumblrNew command, when finished use the :TumblrPost command.\r\n","install_details":"How: Add 'let tumblr_email=\"INSERT EMAIL\"' and 'let tumblr_password=\"INSERT PASSWORD\"' to your .vimrc, obviously putting in the correct email and password for your account.\r\n\r\nMove the file to your ~\/.vim\/plugin folder.","5":"How: Add 'let tumblr_email=\"INSERT EMAIL\"' and 'let tumblr_password=\"INSERT PASSWORD\"' to your .vimrc, obviously putting in the correct email and password for your account.\r\n\r\nMove the file to your ~\/.vim\/plugin folder.","first_name":"Travis","6":"Travis","last_name":"Jeffery","7":"Jeffery","releases":[{"0":"2329","vim_version":"7.0","1":"7.0","script_version":"0.11","2":"0.11","version_comment":"Peter Hoffman wanted to be able to post a range and sent some code so now post a range by selected at least least 2 lines where the first line is the title and the rest is the body.","3":"Peter Hoffman wanted to be able to post a range and sent some code so now post a range by selected at least least 2 lines where the first line is the title and the rest is the body.","package":"tumblr.vim","4":"tumblr.vim","src_id":"9209","5":"9209","creation_date":"1220273574","6":"1220273574"},{"0":"2329","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"tumblr.vim","4":"tumblr.vim","src_id":"9073","5":"9073","creation_date":"1217897330","6":"1217897330"}]},"2328":{"script_id":"2328","0":"2328","script_name":"nopaste.vim","1":"nopaste.vim","script_type":"utility","2":"utility","summary":"Nopaste interface to http:\/\/www.rafb.net\/ from inside vim","3":"Nopaste interface to http:\/\/www.rafb.net\/ from inside vim","description":"This is a simple interface to http:\/\/www.rafb.net\/ which need vim's python interface as a dependency. Edit a file, then issue the command \r\n:Paste \r\nand it will post the whole file on rafb. The link will come in your clipboard(* and +) as default, so you can post it with Ctrl + v or middle mouse button somewhere on IRC, browsers, etc. I also have that map in my ~\/.vimrc\r\nvnoremap <leader>paste y:call Paste('<C-R>\"')<cr><cr>\r\nwith which you can paste just a snippet from the file. Just select the block\/text in VISUAL mode and hit <leader>paste this will copy the text to the site, note <leader> is \\ as default in vim.\r\n","4":"This is a simple interface to http:\/\/www.rafb.net\/ which need vim's python interface as a dependency. Edit a file, then issue the command \r\n:Paste \r\nand it will post the whole file on rafb. The link will come in your clipboard(* and +) as default, so you can post it with Ctrl + v or middle mouse button somewhere on IRC, browsers, etc. I also have that map in my ~\/.vimrc\r\nvnoremap <leader>paste y:call Paste('<C-R>\"')<cr><cr>\r\nwith which you can paste just a snippet from the file. Just select the block\/text in VISUAL mode and hit <leader>paste this will copy the text to the site, note <leader> is \\ as default in vim.\r\n","install_details":"Put the vim file in your ~\/.vim\/plugin on Unix and ~\/vimfiles\/plugin on Windows.\r\nYou should also set g:nickname to your nickname with something like this\r\nlet g:nickname = \"nikolavp\"","5":"Put the vim file in your ~\/.vim\/plugin on Unix and ~\/vimfiles\/plugin on Windows.\r\nYou should also set g:nickname to your nickname with something like this\r\nlet g:nickname = \"nikolavp\"","first_name":"Nikola","6":"Nikola","last_name":"Petrov","7":"Petrov","releases":[{"0":"2328","vim_version":"6.0","1":"6.0","script_version":"0.02","2":"0.02","version_comment":"Exit the script if we are in compitable mode or we don't have +python support. Also added some license comments, etc.","3":"Exit the script if we are in compitable mode or we don't have +python support. Also added some license comments, etc.","package":"nopaste.vim","4":"nopaste.vim","src_id":"9077","5":"9077","creation_date":"1217937752","6":"1217937752"},{"0":"2328","vim_version":"7.0","1":"7.0","script_version":"0.01","2":"0.01","version_comment":"Initial upload","3":"Initial upload","package":"nopaste.vim","4":"nopaste.vim","src_id":"9072","5":"9072","creation_date":"1217850504","6":"1217850504"}]},"2327":{"script_id":"2327","0":"2327","script_name":"catn.vim","1":"catn.vim","script_type":"utility","2":"utility","summary":"insert formatted numbering text.","3":"insert formatted numbering text.","description":"Insert formatted text with number at selected area.\r\nYou can select \"text format\", \"starting number\", and \"insert area\".\r\n\r\nDefault value of option are\r\ntext format     : \"%d \"\r\nstarting number : 1\r\ninsert area     : current line only\r\n\r\n------------------------------------------------------------------------------\r\n\r\n[command format]\r\n\r\n:'<,'>Catn {text format} {starting number}\r\n\r\n:'<,'>Catn [{starting number}]\r\n\r\n({text format} ... see \":help printf()\", available format is written there.)\r\n\r\n------------------------------------------------------------------------------\r\n\r\n[command example]\r\n\r\n(Insert number at selected area. 1, 2, 3, ....)\r\n:'<,'>Catn\r\n\r\n(Insert number at selected area. 1000, 1001, 1002, ....)\r\n:'<,'>Catn 1000\r\n\r\n(Insert formatted number text at selected area. 0000500, 0000501, 0000502, ....)\r\n:'<,'>Catn %08d\\  500\r\n\r\n","4":"Insert formatted text with number at selected area.\r\nYou can select \"text format\", \"starting number\", and \"insert area\".\r\n\r\nDefault value of option are\r\ntext format     : \"%d \"\r\nstarting number : 1\r\ninsert area     : current line only\r\n\r\n------------------------------------------------------------------------------\r\n\r\n[command format]\r\n\r\n:'<,'>Catn {text format} {starting number}\r\n\r\n:'<,'>Catn [{starting number}]\r\n\r\n({text format} ... see \":help printf()\", available format is written there.)\r\n\r\n------------------------------------------------------------------------------\r\n\r\n[command example]\r\n\r\n(Insert number at selected area. 1, 2, 3, ....)\r\n:'<,'>Catn\r\n\r\n(Insert number at selected area. 1000, 1001, 1002, ....)\r\n:'<,'>Catn 1000\r\n\r\n(Insert formatted number text at selected area. 0000500, 0000501, 0000502, ....)\r\n:'<,'>Catn %08d\\  500\r\n\r\n","install_details":"1. Copy the catn.vim script to\r\n   $HOME\/vimfiles\/plugin or $HOME\/.vim\/plugin directory.\r\n   Refer to ':help add-plugin', ':help add-global-plugin' and\r\n   ':help runtimepath' for more details about Vim plugins.\r\n\r\n2. Restart Vim.\r\n\r\n","5":"1. Copy the catn.vim script to\r\n   $HOME\/vimfiles\/plugin or $HOME\/.vim\/plugin directory.\r\n   Refer to ':help add-plugin', ':help add-global-plugin' and\r\n   ':help runtimepath' for more details about Vim plugins.\r\n\r\n2. Restart Vim.\r\n\r\n","first_name":"omi","6":"omi","last_name":"taku","7":"taku","releases":[{"0":"2327","vim_version":"7.0","1":"7.0","script_version":"0.5","2":"0.5","version_comment":"Initial upload","3":"Initial upload","package":"catn.vim","4":"catn.vim","src_id":"9067","5":"9067","creation_date":"1217656025","6":"1217656025"}]},"2326":{"script_id":"2326","0":"2326","script_name":"batch.vim","1":"batch.vim","script_type":"utility","2":"utility","summary":"execute vim script in selected area.","3":"execute vim script in selected area.","description":"Execute vim script in selected area (with Visual Mode).\r\nPlugin copy selected area text to a temporary file,\r\nand execute temporary file as vim script file.\r\n\r\nThis plugin will be used for\r\n    testing vim script file,\r\n    debuging vim script,\r\n    or loading selected vim editor options,,,,\r\n\r\n------------------------------------------------------------------------------\r\n\r\n[command format]\r\n\r\n:'<,'>Batch\r\n\r\n","4":"Execute vim script in selected area (with Visual Mode).\r\nPlugin copy selected area text to a temporary file,\r\nand execute temporary file as vim script file.\r\n\r\nThis plugin will be used for\r\n    testing vim script file,\r\n    debuging vim script,\r\n    or loading selected vim editor options,,,,\r\n\r\n------------------------------------------------------------------------------\r\n\r\n[command format]\r\n\r\n:'<,'>Batch\r\n\r\n","install_details":"1. Copy the batch.vim script to\r\n   $HOME\/vimfiles\/plugin or $HOME\/.vim\/plugin directory.\r\n   Refer to ':help add-plugin', ':help add-global-plugin' and\r\n   ':help runtimepath' for more details about Vim plugins.\r\n\r\n2. Restart Vim.\r\n\r\n","5":"1. Copy the batch.vim script to\r\n   $HOME\/vimfiles\/plugin or $HOME\/.vim\/plugin directory.\r\n   Refer to ':help add-plugin', ':help add-global-plugin' and\r\n   ':help runtimepath' for more details about Vim plugins.\r\n\r\n2. Restart Vim.\r\n\r\n","first_name":"omi","6":"omi","last_name":"taku","7":"taku","releases":[{"0":"2326","vim_version":"7.0","1":"7.0","script_version":"0.5","2":"0.5","version_comment":"Initial upload","3":"Initial upload","package":"batch.vim","4":"batch.vim","src_id":"9066","5":"9066","creation_date":"1217655951","6":"1217655951"}]},"2325":{"script_id":"2325","0":"2325","script_name":"LaTeX error filter","1":"LaTeX error filter","script_type":"utility","2":"utility","summary":"Filters latex log file to get errors and warnings","3":"Filters latex log file to get errors and warnings","description":"The script is a utility that can be used to glean warning\/error information from a latex compile. It will format the output into a format that is easy to read by VIM in the quickfix mode. This utility is useful for people who use VIM to edit LaTeX files, and don't use the VIM-Latex suite (the suite has already the quickfix capability). I don't use it because I think it is making things more complicated rather than simplifying it.\r\n\r\nAn alternative to using this script is to setup the errorformat variable for latex (see \":help errorformat-latex\"), and use the vimlatex script available on this site too (to avoid the problem of broken numbers, and to help vim recognize filenames). But the messages are not as compact as those produced by this script.\r\n\r\nNote 1: The filter needs awk to run.\r\nNote 2: Even though the script is especially useful for people who don't use vim-latex, it is also useful for those who do -- It makes the messages more meaningful (e.g, 1 or 3, instead of 32 or 54, when there are actually only 3 messages on 54 lines). ","4":"The script is a utility that can be used to glean warning\/error information from a latex compile. It will format the output into a format that is easy to read by VIM in the quickfix mode. This utility is useful for people who use VIM to edit LaTeX files, and don't use the VIM-Latex suite (the suite has already the quickfix capability). I don't use it because I think it is making things more complicated rather than simplifying it.\r\n\r\nAn alternative to using this script is to setup the errorformat variable for latex (see \":help errorformat-latex\"), and use the vimlatex script available on this site too (to avoid the problem of broken numbers, and to help vim recognize filenames). But the messages are not as compact as those produced by this script.\r\n\r\nNote 1: The filter needs awk to run.\r\nNote 2: Even though the script is especially useful for people who don't use vim-latex, it is also useful for those who do -- It makes the messages more meaningful (e.g, 1 or 3, instead of 32 or 54, when there are actually only 3 messages on 54 lines). ","install_details":"1. Save the script and make sure that it is in the executable path, and is executable. \r\n\r\n2. Put these lines in your .vim\/ftplugin\/tex.vim file\r\n\"------------\r\nset errorformat=%f:%l:%c:%m\r\nfunction Latex()\r\n    update\r\n    let file=expand('%:t:r')\r\n    let errors=system('latex --interaction nonstopmode '.file.' |latex-errorfilter')\r\n    if errors==\"\"\r\n        echo 'LaTeX ok: No warning\/error'\r\n    else\r\n        cexpr errors\r\n    endif\r\nendfunction\r\n\r\nmap <F4> :call Latex()<CR>\r\nmap <F6> :cprev<CR>\r\nmap <F7> :cnext<CR>\r\nmap <F8> :clist<CR>\r\n\"------------\r\n\r\n3. In VIM, hit F4 to compile the latex file and show errors\/warnings if any. F6 and F7 will show previous\/next message, and F8 will list all messages. ","5":"1. Save the script and make sure that it is in the executable path, and is executable. \r\n\r\n2. Put these lines in your .vim\/ftplugin\/tex.vim file\r\n\"------------\r\nset errorformat=%f:%l:%c:%m\r\nfunction Latex()\r\n    update\r\n    let file=expand('%:t:r')\r\n    let errors=system('latex --interaction nonstopmode '.file.' |latex-errorfilter')\r\n    if errors==\"\"\r\n        echo 'LaTeX ok: No warning\/error'\r\n    else\r\n        cexpr errors\r\n    endif\r\nendfunction\r\n\r\nmap <F4> :call Latex()<CR>\r\nmap <F6> :cprev<CR>\r\nmap <F7> :cnext<CR>\r\nmap <F8> :clist<CR>\r\n\"------------\r\n\r\n3. In VIM, hit F4 to compile the latex file and show errors\/warnings if any. F6 and F7 will show previous\/next message, and F8 will list all messages. ","first_name":"Zhengdao","6":"Zhengdao","last_name":"Wang","7":"Wang","releases":[{"0":"2325","vim_version":"6.0","1":"6.0","script_version":"0.2","2":"0.2","version_comment":"column support.","3":"column support.","package":"latex-errorfilter","4":"latex-errorfilter","src_id":"9106","5":"9106","creation_date":"1218364420","6":"1218364420"}]},"2324":{"script_id":"2324","0":"2324","script_name":"TextFormat","1":"TextFormat","script_type":"utility","2":"utility","summary":"Quickly align and format paragraphs and text areas: left, right, justify, center","3":"Quickly align and format paragraphs and text areas: left, right, justify, center","description":"Note: This plugin is not maintained.\r\n\r\nThis plugin provides commands and key mappings to quickly align and format text. Text can be easily reformatted and aligned to either left or right margin or justified to both margins or centered. The text formatting commands provided by this plugin are a bit more automatic and more intelligent than those integrated to Vim. Together they make more powerful command set for formatting text.\r\n\r\nManual is included, just type\r\n\r\n    :help textformat.txt\r\n\r\nDefault keymappings:\r\n\r\n    \\al     Left-align and reformat\r\n    \\ar     Right-align\r\n    \\aj     Left-right justify and reformat\r\n    \\ac     Center lines\r\n\r\nThe prefix key is actually <Leader> key. It's backlash by default but it is configurable.\r\n","4":"Note: This plugin is not maintained.\r\n\r\nThis plugin provides commands and key mappings to quickly align and format text. Text can be easily reformatted and aligned to either left or right margin or justified to both margins or centered. The text formatting commands provided by this plugin are a bit more automatic and more intelligent than those integrated to Vim. Together they make more powerful command set for formatting text.\r\n\r\nManual is included, just type\r\n\r\n    :help textformat.txt\r\n\r\nDefault keymappings:\r\n\r\n    \\al     Left-align and reformat\r\n    \\ar     Right-align\r\n    \\aj     Left-right justify and reformat\r\n    \\ac     Center lines\r\n\r\nThe prefix key is actually <Leader> key. It's backlash by default but it is configurable.\r\n","install_details":"The plugin uses Vimball plugin archive format (vimscript#1502). To install the package, load the file to Vim and run command\r\n\r\n    :source %\r\n\r\nTo remove the plugin, type\r\n\r\n    :RmVimball textformat","5":"The plugin uses Vimball plugin archive format (vimscript#1502). To install the package, load the file to Vim and run command\r\n\r\n    :source %\r\n\r\nTo remove the plugin, type\r\n\r\n    :RmVimball textformat","first_name":"Teemu","6":"Teemu","last_name":"Likonen","7":"Likonen","releases":[{"0":"2324","vim_version":"7.0","1":"7.0","script_version":"2.1","2":"2.1","version_comment":"Minor internal cleanup","3":"Minor internal cleanup","package":"textformat.vba","4":"textformat.vba","src_id":"9247","5":"9247","creation_date":"1221293905","6":"1221293905"},{"0":"2324","vim_version":"7.0","1":"7.0","script_version":"2.0","2":"2.0","version_comment":"* \\al and \\aj now reformat text also in visual mode.\r\n* \\al and \\aj honor \"w\" in 'formatoptions' and detect paragraph boundaries accordingly.\r\n* :AlignLeft, :AlignJustify, \\al and \\aj recognize several paragraphs within the range and detect indent for each paragraph separately.\r\n* Add logic to load the plugin script only once.\r\n","3":"* \\al and \\aj now reformat text also in visual mode.\r\n* \\al and \\aj honor \"w\" in 'formatoptions' and detect paragraph boundaries accordingly.\r\n* :AlignLeft, :AlignJustify, \\al and \\aj recognize several paragraphs within the range and detect indent for each paragraph separately.\r\n* Add logic to load the plugin script only once.\r\n","package":"textformat.vba","4":"textformat.vba","src_id":"9100","5":"9100","creation_date":"1218327529","6":"1218327529"},{"0":"2324","vim_version":"7.0","1":"7.0","script_version":"1.1","2":"1.1","version_comment":"-- Keep cursor position more accurately when formatting a paragraph with \\al and \\aj.\r\n-- When 'joinspaces' is set insert two spaces after .?! punctuation with left-right justify. This is now similar to other commands.\r\n","3":"-- Keep cursor position more accurately when formatting a paragraph with \\al and \\aj.\r\n-- When 'joinspaces' is set insert two spaces after .?! punctuation with left-right justify. This is now similar to other commands.\r\n","package":"textformat.vba","4":"textformat.vba","src_id":"9069","5":"9069","creation_date":"1217801104","6":"1217801104"},{"0":"2324","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"-- All the commands now follow user's 'expandtab' setting and print leading whitespaces accordingly. Now this works just like :left, :right and :center commands. -- The left-aligned last line in justified paragraph did not honor 'joinspaces'. Fixed.\r\n","3":"-- All the commands now follow user's 'expandtab' setting and print leading whitespaces accordingly. Now this works just like :left, :right and :center commands. -- The left-aligned last line in justified paragraph did not honor 'joinspaces'. Fixed.\r\n","package":"textformat.vba","4":"textformat.vba","src_id":"9068","5":"9068","creation_date":"1217714077","6":"1217714077"},{"0":"2324","vim_version":"7.0","1":"7.0","script_version":"0.9","2":"0.9","version_comment":"Initial upload","3":"Initial upload","package":"textformat.vba","4":"textformat.vba","src_id":"9063","5":"9063","creation_date":"1217572851","6":"1217572851"}]},"2323":{"script_id":"2323","0":"2323","script_name":"PHP Scripts -> Advertisement \/ Internet","1":"PHP Scripts -> Advertisement \/ Internet","script_type":"utility","2":"utility","summary":"Start your own Url Rotator Service","3":"Start your own Url Rotator Service","description":"URL rotation can be one of the most useful tools for a webmaster.\r\nIf you have multiple products or affiliate programs to promote with not enough time to promote them all, the rotator can be your best friend.\r\nThis will allow you to add as many URL's as you wish to the rotation and is fully maintained through an easy to use admin panel, which gives you full control over the settings.","4":"URL rotation can be one of the most useful tools for a webmaster.\r\nIf you have multiple products or affiliate programs to promote with not enough time to promote them all, the rotator can be your best friend.\r\nThis will allow you to add as many URL's as you wish to the rotation and is fully maintained through an easy to use admin panel, which gives you full control over the settings.","install_details":"","5":"","first_name":"rohit","6":"rohit","last_name":"seth","7":"seth","releases":[{"0":"2323","vim_version":"5.7","1":"5.7","script_version":"1.1","2":"1.1","version_comment":"Initial upload","3":"Initial upload","package":"New Text Document.txt","4":"New Text Document.txt","src_id":"9062","5":"9062","creation_date":"1217543806","6":"1217543806"}]},"2322":{"script_id":"2322","0":"2322","script_name":"zshr.vim","1":"zshr.vim","script_type":"utility","2":"utility","summary":"substitute and execute previous command.","3":"substitute and execute previous command.","description":"Substitute previous command string, and execute substituted command.\r\nThis plugin add \":R\" command to your vim environment.\r\n\r\n------------------------------------------------------------------------------\r\n[command syntax]\r\n\r\n:R {old}={new}\r\n:R {old1}={new1} [{old2}={new2} {old3}={new3} ...]\r\n\r\n------------------------------------------------------------------------------\r\n[command example - 1]\r\n1. Execute a command.\r\n\r\n    :%s\/aaabbbccc\/xxxyyyzzz\/g\r\n\r\n\r\n2. Execute \":R\" command with replacement parameters.\r\n\r\n    :R a=m\r\n\r\n   (find \"a\" in last command, and replace \"a\" to \"m\".)\r\n\r\n\r\n3. Vim editor execute this command.\r\n\r\n    :%s\/mmmbbbccc\/xxxyyyzzz\/g\r\n\r\n\r\n------------------------------------------------------------------------------\r\n[command example - 2]\r\n4. You want to use multiple replacement parameters,\r\n   you execute command this example.\r\n\r\n    :R a=m ccc=xyz bb=123\r\n\r\n   (find \"a\" in last command, and replace \"a\" to \"m\".\r\n    find \"ccc\" in last command, and replace \"ccc\" to \"xyz\".\r\n    find \"bb\" in last command, and replace \"bb\" to \"123\".)\r\n\r\n","4":"Substitute previous command string, and execute substituted command.\r\nThis plugin add \":R\" command to your vim environment.\r\n\r\n------------------------------------------------------------------------------\r\n[command syntax]\r\n\r\n:R {old}={new}\r\n:R {old1}={new1} [{old2}={new2} {old3}={new3} ...]\r\n\r\n------------------------------------------------------------------------------\r\n[command example - 1]\r\n1. Execute a command.\r\n\r\n    :%s\/aaabbbccc\/xxxyyyzzz\/g\r\n\r\n\r\n2. Execute \":R\" command with replacement parameters.\r\n\r\n    :R a=m\r\n\r\n   (find \"a\" in last command, and replace \"a\" to \"m\".)\r\n\r\n\r\n3. Vim editor execute this command.\r\n\r\n    :%s\/mmmbbbccc\/xxxyyyzzz\/g\r\n\r\n\r\n------------------------------------------------------------------------------\r\n[command example - 2]\r\n4. You want to use multiple replacement parameters,\r\n   you execute command this example.\r\n\r\n    :R a=m ccc=xyz bb=123\r\n\r\n   (find \"a\" in last command, and replace \"a\" to \"m\".\r\n    find \"ccc\" in last command, and replace \"ccc\" to \"xyz\".\r\n    find \"bb\" in last command, and replace \"bb\" to \"123\".)\r\n\r\n","install_details":"1. Copy the zshr.vim script to\r\n   $HOME\/vimfiles\/plugin or $HOME\/.vim\/plugin directory.\r\n   Refer to ':help add-plugin', ':help add-global-plugin' and\r\n   ':help runtimepath' for more details about Vim plugins.\r\n\r\n2. Restart Vim.\r\n\r\n3. \"zshr.vim\" plugin add \":R\" command to your vim environment.\r\n\r\n","5":"1. Copy the zshr.vim script to\r\n   $HOME\/vimfiles\/plugin or $HOME\/.vim\/plugin directory.\r\n   Refer to ':help add-plugin', ':help add-global-plugin' and\r\n   ':help runtimepath' for more details about Vim plugins.\r\n\r\n2. Restart Vim.\r\n\r\n3. \"zshr.vim\" plugin add \":R\" command to your vim environment.\r\n\r\n","first_name":"omi","6":"omi","last_name":"taku","7":"taku","releases":[{"0":"2322","vim_version":"7.0","1":"7.0","script_version":"0.5","2":"0.5","version_comment":"Initial upload","3":"Initial upload","package":"zshr.vim","4":"zshr.vim","src_id":"9056","5":"9056","creation_date":"1217473936","6":"1217473936"}]},"2321":{"script_id":"2321","0":"2321","script_name":"zoom.vim","1":"zoom.vim","script_type":"utility","2":"utility","summary":"control gui font size with \"+\" or \"-\" keys.","3":"control gui font size with \"+\" or \"-\" keys.","description":"Control Vim editor font size with key \"+\", or key \"-\".\r\nPress \"+\" key, Vim editor gui font size will change bigger.\r\nAnd, press \"-\" key, Vim editor gui font size will change smaller.\r\n\r\nThis plugin is for GUI only.\r\n\r\n\r\nNormal Mode:\r\n    +                  ... change font size bigger\r\n    -                  ... change font size smaller\r\n\r\nCommand-line Mode:\r\n    :ZoomIn            ... change font size bigger\r\n    :ZoomOut           ... change font size smaller\r\n    :ZoomReset         ... reset font size changes.\r\n\r\n","4":"Control Vim editor font size with key \"+\", or key \"-\".\r\nPress \"+\" key, Vim editor gui font size will change bigger.\r\nAnd, press \"-\" key, Vim editor gui font size will change smaller.\r\n\r\nThis plugin is for GUI only.\r\n\r\n\r\nNormal Mode:\r\n    +                  ... change font size bigger\r\n    -                  ... change font size smaller\r\n\r\nCommand-line Mode:\r\n    :ZoomIn            ... change font size bigger\r\n    :ZoomOut           ... change font size smaller\r\n    :ZoomReset         ... reset font size changes.\r\n\r\n","install_details":"1. Copy the zoom.vim script to\r\n   $HOME\/vimfiles\/plugin or $HOME\/.vim\/plugin directory.\r\n   Refer to ':help add-plugin', ':help add-global-plugin' and\r\n   ':help runtimepath' for more details about Vim plugins.\r\n\r\n2. Restart Vim.\r\n\r\n","5":"1. Copy the zoom.vim script to\r\n   $HOME\/vimfiles\/plugin or $HOME\/.vim\/plugin directory.\r\n   Refer to ':help add-plugin', ':help add-global-plugin' and\r\n   ':help runtimepath' for more details about Vim plugins.\r\n\r\n2. Restart Vim.\r\n\r\n","first_name":"omi","6":"omi","last_name":"taku","7":"taku","releases":[{"0":"2321","vim_version":"7.0","1":"7.0","script_version":"0.5","2":"0.5","version_comment":"Initial upload","3":"Initial upload","package":"zoom.vim","4":"zoom.vim","src_id":"9055","5":"9055","creation_date":"1217472314","6":"1217472314"}]},"2320":{"script_id":"2320","0":"2320","script_name":"auto_wc.vim","1":"auto_wc.vim","script_type":"utility","2":"utility","summary":"update total character count of current editing file automatically.","3":"update total character count of current editing file automatically.","description":"For writers.\r\n\r\nWrite your document \"WC:[0\/5000]\",\r\nand so,\r\nleft number that is total char count of current editing file\r\nwill be updated when you are saving file.\r\n\r\nRight number is free number space.\r\nFor example,\r\nyou use right number space to write max char count.\r\n\r\n","4":"For writers.\r\n\r\nWrite your document \"WC:[0\/5000]\",\r\nand so,\r\nleft number that is total char count of current editing file\r\nwill be updated when you are saving file.\r\n\r\nRight number is free number space.\r\nFor example,\r\nyou use right number space to write max char count.\r\n\r\n","install_details":"1. Copy the auto_wc.vim script to\r\n   $HOME\/vimfiles\/plugin or $HOME\/.vim\/plugin directory.\r\n   Refer to ':help add-plugin', ':help add-global-plugin' and\r\n   ':help runtimepath' for more details about Vim plugins.\r\n\r\n2. Restart Vim.\r\n","5":"1. Copy the auto_wc.vim script to\r\n   $HOME\/vimfiles\/plugin or $HOME\/.vim\/plugin directory.\r\n   Refer to ':help add-plugin', ':help add-global-plugin' and\r\n   ':help runtimepath' for more details about Vim plugins.\r\n\r\n2. Restart Vim.\r\n","first_name":"omi","6":"omi","last_name":"taku","7":"taku","releases":[{"0":"2320","vim_version":"7.0","1":"7.0","script_version":"0.5","2":"0.5","version_comment":"Initial upload","3":"Initial upload","package":"auto_wc.vim","4":"auto_wc.vim","src_id":"9054","5":"9054","creation_date":"1217470541","6":"1217470541"}]},"2319":{"script_id":"2319","0":"2319","script_name":"thegoodluck","1":"thegoodluck","script_type":"color scheme","2":"color scheme","summary":"Contrast colourful light-background scheme","3":"Contrast colourful light-background scheme","description":"tGL - the Good Luck\r\nMy personal light colorscheme for gvim.\r\nI prefere to decrease screen brightness at my worktime to the value, when the white color not tire my eyes. So the colorscheme is comfortable for long time working for me.\r\n\r\nScreenshot: http:\/\/img-fotki.yandex.ru\/get\/31\/shvechikov.0\/0_12c07_6929a9d3_orig.jpg","4":"tGL - the Good Luck\r\nMy personal light colorscheme for gvim.\r\nI prefere to decrease screen brightness at my worktime to the value, when the white color not tire my eyes. So the colorscheme is comfortable for long time working for me.\r\n\r\nScreenshot: http:\/\/img-fotki.yandex.ru\/get\/31\/shvechikov.0\/0_12c07_6929a9d3_orig.jpg","install_details":"Copy to your Vim colors directory.","5":"Copy to your Vim colors directory.","first_name":"Leonid","6":"Leonid","last_name":"Shvechikov","7":"Shvechikov","releases":[{"0":"2319","vim_version":"7.0","1":"7.0","script_version":"0.7","2":"0.7","version_comment":"Initial upload","3":"Initial upload","package":"thegoodluck.vim","4":"thegoodluck.vim","src_id":"9052","5":"9052","creation_date":"1217463289","6":"1217463289"}]},"2318":{"script_id":"2318","0":"2318","script_name":"Short Url Script","1":"Short Url Script","script_type":"utility","2":"utility","summary":"Start your own Short Url Service","3":"Start your own Short Url Service","description":"Short Url Service with Url Tracker can be one of the most useful tools for any online marketer.\r\nMost of the online marketers don't want to send emails with URLs that break making the recipient have to go through the work of copying and pasting it into there browser window.\r\nMost of them don't want to use one program to create a tiny url and than having to access another one to track it .\r\nThis will allow you to add as many URL's to shorten as you wants and provides you with detailed stats which gives you full control over the settings.","4":"Short Url Service with Url Tracker can be one of the most useful tools for any online marketer.\r\nMost of the online marketers don't want to send emails with URLs that break making the recipient have to go through the work of copying and pasting it into there browser window.\r\nMost of them don't want to use one program to create a tiny url and than having to access another one to track it .\r\nThis will allow you to add as many URL's to shorten as you wants and provides you with detailed stats which gives you full control over the settings.","install_details":"","5":"","first_name":"rohit","6":"rohit","last_name":"seth","7":"seth","releases":[{"0":"2318","vim_version":"5.7","1":"5.7","script_version":"1.1","2":"1.1","version_comment":"Initial upload","3":"Initial upload","package":"New Text Document.txt","4":"New Text Document.txt","src_id":"9051","5":"9051","creation_date":"1217453515","6":"1217453515"}]},"2317":{"script_id":"2317","0":"2317","script_name":"QuickName","1":"QuickName","script_type":"utility","2":"utility","summary":"The most convenient way navigating opened buffers, incremental search by name","3":"The most convenient way navigating opened buffers, incremental search by name","description":"The most convenient way to navigate currently opened buffers.\r\n\r\nDefault hot key is F3.\r\n\r\nInitially, QuickName display the full list of opened buffers in a compact way (multi-column) inside command area. As you type, QuickName narrows the list to only buffers with matched name. Hit <Enter> to open selected buffer. Hit <Esc> or hot key (default F3) again to close QuickName.\r\n\r\nWhen QuickName is active, arrow keys and backspace function as expected.\r\n\r\nMatching rule: thefile.vim can be matched with any of thefil, thefi.vim, thfl.vm. Guess why!\r\n\r\nShould QuickName integrate with QuickBuf, and how?\r\nAny ideas and bug reports, please send to palnart@gmail.com.\r\n","4":"The most convenient way to navigate currently opened buffers.\r\n\r\nDefault hot key is F3.\r\n\r\nInitially, QuickName display the full list of opened buffers in a compact way (multi-column) inside command area. As you type, QuickName narrows the list to only buffers with matched name. Hit <Enter> to open selected buffer. Hit <Esc> or hot key (default F3) again to close QuickName.\r\n\r\nWhen QuickName is active, arrow keys and backspace function as expected.\r\n\r\nMatching rule: thefile.vim can be matched with any of thefil, thefi.vim, thfl.vm. Guess why!\r\n\r\nShould QuickName integrate with QuickBuf, and how?\r\nAny ideas and bug reports, please send to palnart@gmail.com.\r\n","install_details":"Put qname.vim in plugin directory, or source it via Vim startup script.\r\n\r\nTo set QuickName hot key to <key>, put this line in your Vim startup script:\r\n    let g:qname_hotkey = \"<key>\"\r\nBy default, hot key is <F3>, as if in your startup script has the line:\r\n    let g:qname_hotkey = \"<F3>\"\r\n","5":"Put qname.vim in plugin directory, or source it via Vim startup script.\r\n\r\nTo set QuickName hot key to <key>, put this line in your Vim startup script:\r\n    let g:qname_hotkey = \"<key>\"\r\nBy default, hot key is <F3>, as if in your startup script has the line:\r\n    let g:qname_hotkey = \"<F3>\"\r\n","first_name":"pal","6":"pal","last_name":"nart","7":"nart","releases":[{"0":"2317","vim_version":"7.0","1":"7.0","script_version":"1.2","2":"1.2","version_comment":"ADD: <Tab> and <S-Tab> moves selection like <Up> and <Down>\r\nADD: Use <silent> mapping to keep cmdline clear\r\nFIX: Catch interrupt (<C-C> or <Esc> keypress) and restore cmd line\r\nFIX: Use case-sensitive string comparisons to afford immunity from\r\nvalue of 'ignorecase'\r\nFIX: Do not clobber contents of @y register\r\n---\r\nThanks to Erik Falor for all above changes","3":"ADD: <Tab> and <S-Tab> moves selection like <Up> and <Down>\r\nADD: Use <silent> mapping to keep cmdline clear\r\nFIX: Catch interrupt (<C-C> or <Esc> keypress) and restore cmd line\r\nFIX: Use case-sensitive string comparisons to afford immunity from\r\nvalue of 'ignorecase'\r\nFIX: Do not clobber contents of @y register\r\n---\r\nThanks to Erik Falor for all above changes","package":"qname.1.2.vim","4":"qname.1.2.vim","src_id":"19467","5":"19467","creation_date":"1359870207","6":"1359870207"},{"0":"2317","vim_version":"7.0","1":"7.0","script_version":"1.1","2":"1.1","version_comment":"ADD: Key Shift+Enter open buffer in a new horizontally split window. Thanks to contribution by Salman Halim\r\nADD: Key Ctrl+U reset input line and show all buffers\r\nFIX: If a buffer is already associated with a window, navigate to that window instead of opening in current window","3":"ADD: Key Shift+Enter open buffer in a new horizontally split window. Thanks to contribution by Salman Halim\r\nADD: Key Ctrl+U reset input line and show all buffers\r\nFIX: If a buffer is already associated with a window, navigate to that window instead of opening in current window","package":"qname.vim","4":"qname.vim","src_id":"11036","5":"11036","creation_date":"1247975663","6":"1247975663"},{"0":"2317","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"qname.vim","4":"qname.vim","src_id":"9047","5":"9047","creation_date":"1217424118","6":"1217424118"}]},"2316":{"script_id":"2316","0":"2316","script_name":"Viral Marketing Script","1":"Viral Marketing Script","script_type":"utility","2":"utility","summary":"Attract A Load Of Traffic To Your Web Site With Little Or No Effort!","3":"Attract A Load Of Traffic To Your Web Site With Little Or No Effort!","description":"Viral Traffic Marketing script can generate tonnes of traffic to your site in next to no time. It easily installs on your web server and you can offer the program to your site visitors to join free. Not only will you receive targeted traffic, but it will also increase exponentially!\r\n\r\nIt's very simple. When someone visits your web site and they see they can join your viral marketing program free to increase the traffic to their web site, they need to go through our ingenious signup process.","4":"Viral Traffic Marketing script can generate tonnes of traffic to your site in next to no time. It easily installs on your web server and you can offer the program to your site visitors to join free. Not only will you receive targeted traffic, but it will also increase exponentially!\r\n\r\nIt's very simple. When someone visits your web site and they see they can join your viral marketing program free to increase the traffic to their web site, they need to go through our ingenious signup process.","install_details":"","5":"","first_name":"rohit","6":"rohit","last_name":"seth","7":"seth","releases":[{"0":"2316","vim_version":"5.7","1":"5.7","script_version":"1.1","2":"1.1","version_comment":"Initial upload","3":"Initial upload","package":"haha.txt","4":"haha.txt","src_id":"9039","5":"9039","creation_date":"1217322282","6":"1217322282"}]},"2315":{"script_id":"2315","0":"2315","script_name":"sofu.vim","1":"sofu.vim","script_type":"syntax","2":"syntax","summary":"Highlighting for sofu files","3":"Highlighting for sofu files","description":"Provides simple highlighting for sofu files, which are used in some projects:\r\nFor more information on sofu see http:\/\/sofu.sf.net\r\n\r\nNormaly these files get autodetected as \"conf\", which is o.k., but this script provides a better highlighting.\r\n\r\nBased somewhat on the included conf.vim","4":"Provides simple highlighting for sofu files, which are used in some projects:\r\nFor more information on sofu see http:\/\/sofu.sf.net\r\n\r\nNormaly these files get autodetected as \"conf\", which is o.k., but this script provides a better highlighting.\r\n\r\nBased somewhat on the included conf.vim","install_details":"Just copy into the global syntax folder or your private one and if you want auto-detection add\r\n\r\nau BufRead,BufNewFile *.sofu\t\t\tsetf sofu\r\n\r\nin either filetype.vim or your own ftdetect\/sofu.vim\r\n\r\n","5":"Just copy into the global syntax folder or your private one and if you want auto-detection add\r\n\r\nau BufRead,BufNewFile *.sofu\t\t\tsetf sofu\r\n\r\nin either filetype.vim or your own ftdetect\/sofu.vim\r\n\r\n","first_name":"Marc","6":"Marc","last_name":"Lucksch","7":"Lucksch","releases":[{"0":"2315","vim_version":"7.0","1":"7.0","script_version":"0.23","2":"0.23","version_comment":"Initial upload","3":"Initial upload","package":"sofu.vim","4":"sofu.vim","src_id":"9036","5":"9036","creation_date":"1217246973","6":"1217246973"}]},"2314":{"script_id":"2314","0":"2314","script_name":"softlight.vim","1":"softlight.vim","script_type":"color scheme","2":"color scheme","summary":"it's a soft and easy-on-eyes colorscheme.","3":"it's a soft and easy-on-eyes colorscheme.","description":"a soft and easy-on-eyes colorscheme taken from Kate ( KDE Advanced Text Editor ).  I like Kate's colors so I thought I would make a similar one!! :)  hope you like it!","4":"a soft and easy-on-eyes colorscheme taken from Kate ( KDE Advanced Text Editor ).  I like Kate's colors so I thought I would make a similar one!! :)  hope you like it!","install_details":"download the script softlight.vim\r\ncopy it to ~\/.vim\/colors\/ folder.  If such a directory doesn't exist, you can create it!","5":"download the script softlight.vim\r\ncopy it to ~\/.vim\/colors\/ folder.  If such a directory doesn't exist, you can create it!","first_name":"feng","6":"feng","last_name":"shaun","7":"shaun","releases":[{"0":"2314","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"softlight.vim","4":"softlight.vim","src_id":"9034","5":"9034","creation_date":"1217153710","6":"1217153710"}]},"2313":{"script_id":"2313","0":"2313","script_name":"Banner Management script","1":"Banner Management script","script_type":"utility","2":"utility","summary":"Start Selling Banner Ads on multiple websites from 1 place","3":"Start Selling Banner Ads on multiple websites from 1 place","description":"Banner Management script allows you to sell banner ads on multiple websites from 1 place only. You can provide your advertisers with real time stats of impressions and hits.\r\n \r\nThis script is easy to install and comes with a Free Installation so if you need any help in installations we will install it for no extra cost.","4":"Banner Management script allows you to sell banner ads on multiple websites from 1 place only. You can provide your advertisers with real time stats of impressions and hits.\r\n \r\nThis script is easy to install and comes with a Free Installation so if you need any help in installations we will install it for no extra cost.","install_details":"","5":"","first_name":"rohit","6":"rohit","last_name":"seth","7":"seth","releases":[{"0":"2313","vim_version":"5.7","1":"5.7","script_version":"1.1","2":"1.1","version_comment":"Initial upload","3":"Initial upload","package":"haha.txt","4":"haha.txt","src_id":"9033","5":"9033","creation_date":"1217137648","6":"1217137648"}]},"2312":{"script_id":"2312","0":"2312","script_name":"Indent Highlight","1":"Indent Highlight","script_type":"indent","2":"indent","summary":"Yet another indentation (scope) highlighting","3":"Yet another indentation (scope) highlighting","description":"This plugin provides a function that will highlight (or remove\r\nhighlighting ) of the current scope and parent scope based on difference in\r\nindentation. It can be very usefull for languages that use indentation to\r\ndefine the scope ( python, rubby, etc. )\r\n\r\nI wrote this script so that I could quickly restore visual stack when\r\ncoding in python. So for python I created the following mapping in my vimrc:\r\n\r\nmap <silent> <Leader>ih :call IHighlight( 1, \"\\^[[:space:]]*\\\\(def\\\\\\\\|class\\\\)[[:space:]]\\\\+\" )<CR> \r\nmap <silent> <Leader>is :call IHighlight( 0, \"\\^[[:space:]]*\\\\(def\\\\\\\\|class\\\\)[[:space:]]\\\\+\" )<CR>\r\n\r\nwhich allows me by entering \\ih (or \\is) to highlihgt current scope along\r\nwith the parent scope and than by entering \\ih (or \\is) again remove the\r\nhighlighting\r\n\r\nthe difference between \\ih and \\is is that\r\nthe first one (\\ih) will turn off all syntax highlighting untill indentation highlighting is active\r\nthe syntax highlighting will be turned back on when you enter \\ih again turning the indentation highlighting off\r\nthe second one (\\is) will apply indentation highlighting on top of existing syntax highlighting\r\n\r\none can extend this functionality and provide bindings for movement keys so\r\nthat highlighting follows the cursor position","4":"This plugin provides a function that will highlight (or remove\r\nhighlighting ) of the current scope and parent scope based on difference in\r\nindentation. It can be very usefull for languages that use indentation to\r\ndefine the scope ( python, rubby, etc. )\r\n\r\nI wrote this script so that I could quickly restore visual stack when\r\ncoding in python. So for python I created the following mapping in my vimrc:\r\n\r\nmap <silent> <Leader>ih :call IHighlight( 1, \"\\^[[:space:]]*\\\\(def\\\\\\\\|class\\\\)[[:space:]]\\\\+\" )<CR> \r\nmap <silent> <Leader>is :call IHighlight( 0, \"\\^[[:space:]]*\\\\(def\\\\\\\\|class\\\\)[[:space:]]\\\\+\" )<CR>\r\n\r\nwhich allows me by entering \\ih (or \\is) to highlihgt current scope along\r\nwith the parent scope and than by entering \\ih (or \\is) again remove the\r\nhighlighting\r\n\r\nthe difference between \\ih and \\is is that\r\nthe first one (\\ih) will turn off all syntax highlighting untill indentation highlighting is active\r\nthe syntax highlighting will be turned back on when you enter \\ih again turning the indentation highlighting off\r\nthe second one (\\is) will apply indentation highlighting on top of existing syntax highlighting\r\n\r\none can extend this functionality and provide bindings for movement keys so\r\nthat highlighting follows the cursor position","install_details":"just drop it in your plugin directory and you can start using IHightlight function\r\n\r\nFor a specific language I would recommend to add specific mapping in your vimrc file\r\nsomething like this: \r\nmap <silent> <Leader>ih :call IHighlight( 1, regexp )<CR>\r\nor this: \r\nmap <silent> <Leader>is :call IHighlight( 0, regexp )<CR>\r\n where regexp is the regexp that matches language specific scope identifiers such as \"class\", \"method\", \"def\" and etc. This really depends on the language.\r\n\r\nFor python I use these mappings: \r\nmap <silent> <Leader>ih :call IHighlight( 1, \"\\^[[:space:]]*\\\\(def\\\\\\\\|class\\\\)[[:space:]]\\\\+\" )<CR> \r\nmap <silent> <Leader>is :call IHighlight( 0, \"\\^[[:space:]]*\\\\(def\\\\\\\\|class\\\\)[[:space:]]\\\\+\" )<CR>\r\n","5":"just drop it in your plugin directory and you can start using IHightlight function\r\n\r\nFor a specific language I would recommend to add specific mapping in your vimrc file\r\nsomething like this: \r\nmap <silent> <Leader>ih :call IHighlight( 1, regexp )<CR>\r\nor this: \r\nmap <silent> <Leader>is :call IHighlight( 0, regexp )<CR>\r\n where regexp is the regexp that matches language specific scope identifiers such as \"class\", \"method\", \"def\" and etc. This really depends on the language.\r\n\r\nFor python I use these mappings: \r\nmap <silent> <Leader>ih :call IHighlight( 1, \"\\^[[:space:]]*\\\\(def\\\\\\\\|class\\\\)[[:space:]]\\\\+\" )<CR> \r\nmap <silent> <Leader>is :call IHighlight( 0, \"\\^[[:space:]]*\\\\(def\\\\\\\\|class\\\\)[[:space:]]\\\\+\" )<CR>\r\n","first_name":"Andrey","6":"Andrey","last_name":"Tsiporukha","7":"Tsiporukha","releases":[{"0":"2312","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"indent_highlight.vim","4":"indent_highlight.vim","src_id":"9029","5":"9029","creation_date":"1217060639","6":"1217060639"}]},"2311":{"script_id":"2311","0":"2311","script_name":"GoogleSearchVIM","1":"GoogleSearchVIM","script_type":"utility","2":"utility","summary":"Search for keywords with the Google Desktop Search engine from inside VIM","3":"Search for keywords with the Google Desktop Search engine from inside VIM","description":" This plugin allows you to use Google Desktop Search engine to search text\r\n files on your hard drives (or network drives if configured in GDS) from within VIM. \r\n This requires python, pygoogledesktop script, python windows extensions, and Google Desktop Search engine installed.\r\n Right now, this is a Windows only program, until I find time to modify it\r\n for other OS's.\r\n\r\nThis might get you quicker results instead of using vimgrep or grep.\r\n","4":" This plugin allows you to use Google Desktop Search engine to search text\r\n files on your hard drives (or network drives if configured in GDS) from within VIM. \r\n This requires python, pygoogledesktop script, python windows extensions, and Google Desktop Search engine installed.\r\n Right now, this is a Windows only program, until I find time to modify it\r\n for other OS's.\r\n\r\nThis might get you quicker results instead of using vimgrep or grep.\r\n","install_details":"Make sure you have the latest Google Desktop Search engine installed for Windows!\r\n\r\nMake sure the correct version of Python is installed on your machine that\r\nVIM supports.  Type :version and you should see a \"+python\" or \"+python\/dyn\"\r\nIf it is not there, then you cannot use this script.\r\nAlso in that same version command, check for \"DFEAT_PYTHON\" to see\r\nwhere python is installed for VIM to use and make sure your python is\r\nlocated there.\r\n\r\nMake sure you have a copy of PyGoogleDesktop python package installed\r\nas well. \"http:\/\/code.google.com\/p\/pythongoogledesktop\" or if you have\r\nsetuptools, do \"easy_install pygoogledesktop\" to install.  The easy_install should download the pywin32 extensions if you don't have them.\r\n\r\nNOTE: Make sure that the (PythonInstallDirectory)\\PythonXX\\Scripts directory is in your PYTHONPATH.  Hopefully I'll have this fixed soon!\r\n\r\nInstall googlesearch.vim into your plugin directory\r\n","5":"Make sure you have the latest Google Desktop Search engine installed for Windows!\r\n\r\nMake sure the correct version of Python is installed on your machine that\r\nVIM supports.  Type :version and you should see a \"+python\" or \"+python\/dyn\"\r\nIf it is not there, then you cannot use this script.\r\nAlso in that same version command, check for \"DFEAT_PYTHON\" to see\r\nwhere python is installed for VIM to use and make sure your python is\r\nlocated there.\r\n\r\nMake sure you have a copy of PyGoogleDesktop python package installed\r\nas well. \"http:\/\/code.google.com\/p\/pythongoogledesktop\" or if you have\r\nsetuptools, do \"easy_install pygoogledesktop\" to install.  The easy_install should download the pywin32 extensions if you don't have them.\r\n\r\nNOTE: Make sure that the (PythonInstallDirectory)\\PythonXX\\Scripts directory is in your PYTHONPATH.  Hopefully I'll have this fixed soon!\r\n\r\nInstall googlesearch.vim into your plugin directory\r\n","first_name":"Jack","6":"Jack","last_name":"Atkinson","7":"Atkinson","releases":[{"0":"2311","vim_version":"7.0","1":"7.0","script_version":"0.4","2":"0.4","version_comment":"Fixed a little problem with the results buffer acting like a file wanting to be saved.  Changed the buffer type, so it will no longer prompt you to save it, so you can use \"gf\" to jump to the file.","3":"Fixed a little problem with the results buffer acting like a file wanting to be saved.  Changed the buffer type, so it will no longer prompt you to save it, so you can use \"gf\" to jump to the file.","package":"googlesearch.vim","4":"googlesearch.vim","src_id":"9197","5":"9197","creation_date":"1220047026","6":"1220047026"},{"0":"2311","vim_version":"7.0","1":"7.0","script_version":"0.3","2":"0.3","version_comment":"trying to fix some result buffer problems","3":"trying to fix some result buffer problems","package":"googlesearch.vim","4":"googlesearch.vim","src_id":"9026","5":"9026","creation_date":"1217011203","6":"1217011203"},{"0":"2311","vim_version":"7.0","1":"7.0","script_version":"0.2","2":"0.2","version_comment":"Initial upload","3":"Initial upload","package":"googlesearch.vim","4":"googlesearch.vim","src_id":"9025","5":"9025","creation_date":"1216986286","6":"1216986286"}]},"2310":{"script_id":"2310","0":"2310","script_name":"portablemsys","1":"portablemsys","script_type":"utility","2":"utility","summary":"Use msys as Portable GVim's shell","3":"Use msys as Portable GVim's shell","description":"This plugin automatically sets the shell option to point to msys location.\r\nIt lets you have both Portable GVim and msys+MinGW on your portable usb stick, without needing to set the path every time you plug in the usb stick, thus giving you portable compiling powers :-)\r\n","4":"This plugin automatically sets the shell option to point to msys location.\r\nIt lets you have both Portable GVim and msys+MinGW on your portable usb stick, without needing to set the path every time you plug in the usb stick, thus giving you portable compiling powers :-)\r\n","install_details":"1. Place portablemsys.vim inside your Portable GVim's plugin folder\r\n2. Edit your vimrc file to include the line:\r\n        let Msys='PortableApps\\msys'\r\n    or wherever your msys is located at (in relation to GVim's drive letter).\r\n3. Remove the following line from your msys\\etc\\profile file:\r\n        cd $HOME\r\n    or any other directory changes.\r\n4. Enjoy.","5":"1. Place portablemsys.vim inside your Portable GVim's plugin folder\r\n2. Edit your vimrc file to include the line:\r\n        let Msys='PortableApps\\msys'\r\n    or wherever your msys is located at (in relation to GVim's drive letter).\r\n3. Remove the following line from your msys\\etc\\profile file:\r\n        cd $HOME\r\n    or any other directory changes.\r\n4. Enjoy.","first_name":"ron","6":"ron","last_name":"h","7":"h","releases":[{"0":"2310","vim_version":"6.0","1":"6.0","script_version":"1.0.3","2":"1.0.3","version_comment":"PortableMsys now sets the makeef option to let make create an error file without problems.\r\n","3":"PortableMsys now sets the makeef option to let make create an error file without problems.\r\n","package":"portablemsys.vim","4":"portablemsys.vim","src_id":"12001","5":"12001","creation_date":"1262428439","6":"1262428439"},{"0":"2310","vim_version":"7.0","1":"7.0","script_version":"1.0.2","2":"1.0.2","version_comment":"Added support for a fixed path if you decide to save your Portable GVim to hdd. eg:    let Msys='C:\\msys' ","3":"Added support for a fixed path if you decide to save your Portable GVim to hdd. eg:    let Msys='C:\\msys' ","package":"portablemsys.vim","4":"portablemsys.vim","src_id":"9962","5":"9962","creation_date":"1234517797","6":"1234517797"},{"0":"2310","vim_version":"7.0","1":"7.0","script_version":"1.0.1","2":"1.0.1","version_comment":"Fixed problem where :shell will not bring up the Msys shell.","3":"Fixed problem where :shell will not bring up the Msys shell.","package":"portablemsys.vim","4":"portablemsys.vim","src_id":"9040","5":"9040","creation_date":"1217326276","6":"1217326276"},{"0":"2310","vim_version":"7.0","1":"7.0","script_version":"1.0.0","2":"1.0.0","version_comment":"Initial upload","3":"Initial upload","package":"portablemsys.vim","4":"portablemsys.vim","src_id":"9024","5":"9024","creation_date":"1216963415","6":"1216963415"}]},"2309":{"script_id":"2309","0":"2309","script_name":"Easy List-Builder & Autoresponder Script","1":"Easy List-Builder & Autoresponder Script","script_type":"utility","2":"utility","summary":"Effectively Build A Hugely Profitable & Responsive List Quickly & Easily!","3":"Effectively Build A Hugely Profitable & Responsive List Quickly & Easily!","description":"You've probably heard the saying, \"The money is in the list\", and it's 100% true. Without a list, you'll either have to use free resources that are overwhelmed with similar offers that don't get read, or dig deep into your pockets to pay hand over fist to market your opportunities..","4":"You've probably heard the saying, \"The money is in the list\", and it's 100% true. Without a list, you'll either have to use free resources that are overwhelmed with similar offers that don't get read, or dig deep into your pockets to pay hand over fist to market your opportunities..","install_details":"","5":"","first_name":"rohit","6":"rohit","last_name":"seth","7":"seth","releases":[{"0":"2309","vim_version":"5.7","1":"5.7","script_version":"1.1","2":"1.1","version_comment":"Initial upload","3":"Initial upload","package":"haha.txt","4":"haha.txt","src_id":"9021","5":"9021","creation_date":"1216944555","6":"1216944555"}]},"2308":{"script_id":"2308","0":"2308","script_name":"Clever Tabs","1":"Clever Tabs","script_type":"indent","2":"indent","summary":"Using tabs for indent only on start of line","3":"Using tabs for indent only on start of line","description":"\" Script solving indentation problem. Main idea is\r\n\" have tabs (\"\\t\") at the beginning of line and \r\n\" after first another character like \"\\t\" use spaces (like expandtab).\r\n\" This is useful for code readability. I'm trying to join these two ways:\r\n\" * http:\/\/www.movement.uklinux.net\/docs\/whytabs\/\r\n\" * http:\/\/www.derkarl.org\/why_to_tabs.html\r\n\" with using the best ideas from both.\r\n\"\r\n\" main() {\r\n\"     printf(\"hello\");    \/\/my comment\r\n\"     printf(\"world!\");   \/\/my comment 2\r\n\" }\r\n\" \r\n\" Before printf are tabs (this is block) anda before comments\r\n\" are tabs converted into spaces. After you change \r\n\" tabstop (for tabelator size), part with comments will \r\n\" have still same format, becuase tabs are only on line beginnig.\r\n\"\r\n\" note:    parameter for CleverTabs is shiftwidth in spaces\r\n\" note2:   this is my first script in vim, please be patient\r\n\"\r\n\" special thanks to james pickard for useful advices","4":"\" Script solving indentation problem. Main idea is\r\n\" have tabs (\"\\t\") at the beginning of line and \r\n\" after first another character like \"\\t\" use spaces (like expandtab).\r\n\" This is useful for code readability. I'm trying to join these two ways:\r\n\" * http:\/\/www.movement.uklinux.net\/docs\/whytabs\/\r\n\" * http:\/\/www.derkarl.org\/why_to_tabs.html\r\n\" with using the best ideas from both.\r\n\"\r\n\" main() {\r\n\"     printf(\"hello\");    \/\/my comment\r\n\"     printf(\"world!\");   \/\/my comment 2\r\n\" }\r\n\" \r\n\" Before printf are tabs (this is block) anda before comments\r\n\" are tabs converted into spaces. After you change \r\n\" tabstop (for tabelator size), part with comments will \r\n\" have still same format, becuase tabs are only on line beginnig.\r\n\"\r\n\" note:    parameter for CleverTabs is shiftwidth in spaces\r\n\" note2:   this is my first script in vim, please be patient\r\n\"\r\n\" special thanks to james pickard for useful advices","install_details":"\" instalation:\r\n\" paste content from CleverTabs.vim into .vimrc \r\n\" (or use vim\/plugin directory)","5":"\" instalation:\r\n\" paste content from CleverTabs.vim into .vimrc \r\n\" (or use vim\/plugin directory)","first_name":"Martin","6":"Martin","last_name":"Spevak","7":"Spevak","releases":[{"0":"2308","vim_version":"7.0","1":"7.0","script_version":"1.0.2","2":"1.0.2","version_comment":"* using virtcol for counting space tabelator size","3":"* using virtcol for counting space tabelator size","package":"CleverTabs.vim","4":"CleverTabs.vim","src_id":"9057","5":"9057","creation_date":"1217476894","6":"1217476894"},{"0":"2308","vim_version":"7.0","1":"7.0","script_version":"1.0.1","2":"1.0.1","version_comment":"* fixed bug extra space after tab\r\n* using silent mode for function calling","3":"* fixed bug extra space after tab\r\n* using silent mode for function calling","package":"CleverTabs.vim","4":"CleverTabs.vim","src_id":"9053","5":"9053","creation_date":"1217468288","6":"1217468288"},{"0":"2308","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"CleverTabs.vim","4":"CleverTabs.vim","src_id":"9008","5":"9008","creation_date":"1216786943","6":"1216786943"}]},"2307":{"script_id":"2307","0":"2307","script_name":"Text (Especially LaTeX) Formatter","1":"Text (Especially LaTeX) Formatter","script_type":"utility","2":"utility","summary":"Format text or LaTeX text so that lines have approximately equal lengths","3":"Format text or LaTeX text so that lines have approximately equal lengths","description":"This script formats a paragraph of text so that lines have approximately equal length (set by textwidth). It has the following features:\r\n\r\n1. It restores logical cursor location (the number of non-space chars from the start of the formatted text). \r\n\r\n2. It merges multiple blank lines into one.\r\n\r\n3. It is LaTeX aware (many commands and the comments) are recognized (and ignored) so that the source file does not look bad after formatting. It yields better (according to the author :-) results than fmt, or the VIM internal formatter.\r\n\r\n4. It can be modified to adapted to your own likes (eg. more ignored code blocks) quite easily (see the functions s:CanJoin, s:BlockStart, s:BlockEnd). \r\n\r\n5. It merges multiple spaces into one. (neither fmt nor VIM internal formatter does this). \r\n\r\n6. For lines that start with a space\/tab, they are not disturbed. \r\n\r\n7. It is written in VIM script, so no external programs (awk\/fmt\/perl) are necessary. This is probably against the UNIX principle. But now that VIM offers scripting capability, one can argue that a VIM script is \"simpler\" (less reading of disk :-). \r\n\r\n8. It can be quite easily extended to format a larger chunk of data (more than just a paragraph). Using the s:FormatLines function provided.\r\n\r\nComments\/Suggestions\/Improvements are welcomed. You can leave a comment at \r\nvim.wikia.com\/wiki\/User:Lpb612\r\n\r\nNote1:  Also take a look at a similar script, Script 2187 http:\/\/www.vim.org\/scripts\/script.php?script_id=2187\r\n","4":"This script formats a paragraph of text so that lines have approximately equal length (set by textwidth). It has the following features:\r\n\r\n1. It restores logical cursor location (the number of non-space chars from the start of the formatted text). \r\n\r\n2. It merges multiple blank lines into one.\r\n\r\n3. It is LaTeX aware (many commands and the comments) are recognized (and ignored) so that the source file does not look bad after formatting. It yields better (according to the author :-) results than fmt, or the VIM internal formatter.\r\n\r\n4. It can be modified to adapted to your own likes (eg. more ignored code blocks) quite easily (see the functions s:CanJoin, s:BlockStart, s:BlockEnd). \r\n\r\n5. It merges multiple spaces into one. (neither fmt nor VIM internal formatter does this). \r\n\r\n6. For lines that start with a space\/tab, they are not disturbed. \r\n\r\n7. It is written in VIM script, so no external programs (awk\/fmt\/perl) are necessary. This is probably against the UNIX principle. But now that VIM offers scripting capability, one can argue that a VIM script is \"simpler\" (less reading of disk :-). \r\n\r\n8. It can be quite easily extended to format a larger chunk of data (more than just a paragraph). Using the s:FormatLines function provided.\r\n\r\nComments\/Suggestions\/Improvements are welcomed. You can leave a comment at \r\nvim.wikia.com\/wiki\/User:Lpb612\r\n\r\nNote1:  Also take a look at a similar script, Script 2187 http:\/\/www.vim.org\/scripts\/script.php?script_id=2187\r\n","install_details":"Save the file in the plugin directory (for Unix, this is likely ~\/.vim\/plugin).\r\nUse K to format a paragraph in the normal mode. Redefine the mapping in the script (last line) if K is used for something else. \r\n\r\nIf you want to use it to format only .tex files only, then save the file in .\/vim\/ftplugin\/tex.vim (or append to the end of that if it exists already). ","5":"Save the file in the plugin directory (for Unix, this is likely ~\/.vim\/plugin).\r\nUse K to format a paragraph in the normal mode. Redefine the mapping in the script (last line) if K is used for something else. \r\n\r\nIf you want to use it to format only .tex files only, then save the file in .\/vim\/ftplugin\/tex.vim (or append to the end of that if it exists already). ","first_name":"","6":"","last_name":"lpb612","7":"lpb612","releases":[{"0":"2307","vim_version":"6.0","1":"6.0","script_version":"0.32","2":"0.32","version_comment":"a small bug is corrected that affect how many paragraphs are formatted (should be one, but was two).","3":"a small bug is corrected that affect how many paragraphs are formatted (should be one, but was two).","package":"format.vim","4":"format.vim","src_id":"9035","5":"9035","creation_date":"1217155731","6":"1217155731"}]},"2306":{"script_id":"2306","0":"2306","script_name":" Autoresponder Hosting service","1":" Autoresponder Hosting service","script_type":"utility","2":"utility","summary":"Start your own Autoresponder Hosting service","3":"Start your own Autoresponder Hosting service","description":"In this busy internet marketing world, automation scripts are highly sought after and one thing that is a must-have for any successful marketer is an autoresponder script. Becoming a virtual sales team, autoresponders follow-up automatically with prospects to sell your products and services for you 24\/7. Ask any marketer if they use autoresponders and you will find that 10 out of 10 successful marketers will respond with a definite \"Yes\".\r\n\r\nWith such a high demand for quality autoresponder services online, why not consider starting your own autoresponder hosting business? You could be offering your site visitors access to free and pro membership options, while effectively building a customer list AND generating a monthly residual income.\r\n\r\n ","4":"In this busy internet marketing world, automation scripts are highly sought after and one thing that is a must-have for any successful marketer is an autoresponder script. Becoming a virtual sales team, autoresponders follow-up automatically with prospects to sell your products and services for you 24\/7. Ask any marketer if they use autoresponders and you will find that 10 out of 10 successful marketers will respond with a definite \"Yes\".\r\n\r\nWith such a high demand for quality autoresponder services online, why not consider starting your own autoresponder hosting business? You could be offering your site visitors access to free and pro membership options, while effectively building a customer list AND generating a monthly residual income.\r\n\r\n ","install_details":"","5":"","first_name":"rohit","6":"rohit","last_name":"seth","7":"seth","releases":[{"0":"2306","vim_version":"6.0","1":"6.0","script_version":"1.1","2":"1.1","version_comment":"Initial upload","3":"Initial upload","package":"fileeee.txt","4":"fileeee.txt","src_id":"8997","5":"8997","creation_date":"1216720550","6":"1216720550"}]},"2305":{"script_id":"2305","0":"2305","script_name":"Textile for VIM","1":"Textile for VIM","script_type":"ftplugin","2":"ftplugin","summary":"Syntax Highlighting and Textile rendering \/ preview support","3":"Syntax Highlighting and Textile rendering \/ preview support","description":"*textile.txt*              Textile for Vim       Last Change: November 3, 2008\r\n\r\n===============================================================================\r\nREQUIREMENTS                                             *textile-requirements*\r\n\r\n- ruby - http:\/\/ruby-lang.org\/ (seperate executable, not compiled in)\r\n- RedCloth - http:\/\/whytheluckystiff.net\/ruby\/redcloth\/\r\n\r\nFiles with the extension *.textile will auto-detected.  If editing a new file,\r\nor otherwise, run \":setf textile\" to enable textile commands.\r\n\r\n\r\n==============================================================================\r\nCHANGELOG                                                  *textile-changelog*\r\n\r\n0.3     - Fixed keymappings in the documentation\r\n0.2     - Added multiple colors for headers, and alternating colors for list\r\n          items\r\n        - Fixed error in the vim script for TextileRenderBufferToFile\r\n        - Changed shortcut keys from \\tp to \\rp (render preview instead of\r\n          textile preview, since it's file-type specific anyways)\r\n0.1     - Initial Release\r\n\r\n==============================================================================\r\nCOMMANDS                                                    *textile-commands*\r\n\r\nh2. Commands\r\n\r\n:TextilePreview     - Render the current buffer to a temp file, and open it in\r\n                      your web browser (OSX only)\r\n\r\n                      <Leader>rp\r\n\r\n:TextileRenderTab   - ... to a new tab\r\n\r\n                      <Leader>rt\r\n\r\n:TextileRenderFile  - ... to a file\r\n\r\n                      <Leader>rf\r\n\r\n<Leader> is \\ by default, so <Leader>rp == \\rp\r\n\r\n==============================================================================\r\nCREDITS                                                      *textile-credits* \r\n\r\n- \"Dominic Mitchell\":http:\/\/happygiraffe.net\/: initial syntax highlighting\r\n- \"Aaron Bieber\":http:\/\/blog.aaronbieber.com\/: improved syntax highlighting \r\n- \"Tim Harper\":http:\/\/tim.theenchanter.com\/  : improved syntax highlighting,\r\n                                                plugin\r\n\r\nvim:tw=78:noet:wrap:ts=2:expandtab:ft=help:norl:\r\n\r\n","4":"*textile.txt*              Textile for Vim       Last Change: November 3, 2008\r\n\r\n===============================================================================\r\nREQUIREMENTS                                             *textile-requirements*\r\n\r\n- ruby - http:\/\/ruby-lang.org\/ (seperate executable, not compiled in)\r\n- RedCloth - http:\/\/whytheluckystiff.net\/ruby\/redcloth\/\r\n\r\nFiles with the extension *.textile will auto-detected.  If editing a new file,\r\nor otherwise, run \":setf textile\" to enable textile commands.\r\n\r\n\r\n==============================================================================\r\nCHANGELOG                                                  *textile-changelog*\r\n\r\n0.3     - Fixed keymappings in the documentation\r\n0.2     - Added multiple colors for headers, and alternating colors for list\r\n          items\r\n        - Fixed error in the vim script for TextileRenderBufferToFile\r\n        - Changed shortcut keys from \\tp to \\rp (render preview instead of\r\n          textile preview, since it's file-type specific anyways)\r\n0.1     - Initial Release\r\n\r\n==============================================================================\r\nCOMMANDS                                                    *textile-commands*\r\n\r\nh2. Commands\r\n\r\n:TextilePreview     - Render the current buffer to a temp file, and open it in\r\n                      your web browser (OSX only)\r\n\r\n                      <Leader>rp\r\n\r\n:TextileRenderTab   - ... to a new tab\r\n\r\n                      <Leader>rt\r\n\r\n:TextileRenderFile  - ... to a file\r\n\r\n                      <Leader>rf\r\n\r\n<Leader> is \\ by default, so <Leader>rp == \\rp\r\n\r\n==============================================================================\r\nCREDITS                                                      *textile-credits* \r\n\r\n- \"Dominic Mitchell\":http:\/\/happygiraffe.net\/: initial syntax highlighting\r\n- \"Aaron Bieber\":http:\/\/blog.aaronbieber.com\/: improved syntax highlighting \r\n- \"Tim Harper\":http:\/\/tim.theenchanter.com\/  : improved syntax highlighting,\r\n                                                plugin\r\n\r\nvim:tw=78:noet:wrap:ts=2:expandtab:ft=help:norl:\r\n\r\n","install_details":"Unpack to ~\/.vim","5":"Unpack to ~\/.vim","first_name":"Tim","6":"Tim","last_name":"Harper","7":"Harper","releases":[{"0":"2305","vim_version":"7.0","1":"7.0","script_version":"0.3","2":"0.3","version_comment":"Documentation fixes","3":"Documentation fixes","package":"textile-0.3.zip","4":"textile-0.3.zip","src_id":"9427","5":"9427","creation_date":"1225720122","6":"1225720122"},{"0":"2305","vim_version":"7.0","1":"7.0","script_version":"0.2","2":"0.2","version_comment":"- Added multiple colors for headers, and alternating colors for list items \r\n- Fixed error in the vim script for TextileRenderBufferToFile \r\n- Changed shortcut keys from \\\\tp to \\\\rp (render preview instead of textile preview, since it's file-type specific anyways) \r\n\r\n","3":"- Added multiple colors for headers, and alternating colors for list items \r\n- Fixed error in the vim script for TextileRenderBufferToFile \r\n- Changed shortcut keys from \\\\tp to \\\\rp (render preview instead of textile preview, since it's file-type specific anyways) \r\n\r\n","package":"textile-0.2.zip","4":"textile-0.2.zip","src_id":"9177","5":"9177","creation_date":"1219763904","6":"1219763904"},{"0":"2305","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"textile.tar.bz2","4":"textile.tar.bz2","src_id":"8983","5":"8983","creation_date":"1216615565","6":"1216615565"}]},"2304":{"script_id":"2304","0":"2304","script_name":"vimdb.vim","1":"vimdb.vim","script_type":"utility","2":"utility","summary":"Vim plugin to simulate a simple database Table","3":"Vim plugin to simulate a simple database Table","description":"Unfortunatly nobody likes this script; it would be kind of you to let me know why.\r\n\r\nThis plugin is useful to store information in a database-like design.\r\nWhilst opening a *.vimdb file, autocommands will be applied and open two windows. The left window gives a view on the table, the right window shows the record, the cursor is currently over (of course, after heaving created a new *.vimdb file, there will only be two empty windows shown). The first line of the table will become the header, which shows the names of the columns. For full instructions see readme, to have an idea, how a database will look like: look at example database shipped with the package.\r\n\r\nNote:\r\n1.) With the new improved (since version 0.5) TAB key mapping, editing the database will become a pleasure ;). \r\n2.) Cleared many bugs to make script a bit more compatible to Vim movement\/delete commands (cw, dw, D, C),\r\n     which might be useful editing records (But still the mighty TAB key dwarfs them all;).\r\n3.) Im through with bug removal, but there is still one, you should know: The table needs at least two columns to let the TAB key\r\n     work\r\n\r\nBe Warned:\r\nThe development of the script has advanced, but  i would still not recommend to store important data to a *.vimdb file.\r\n\r\n\r\nQuestions\/Suggestions\/Bug reports?\r\nJust compose a mail! (I dont promise to do anything but to be pleased to receive your mail. But just have a try) \r\nbenjaminschnitzler_at_gmail_dot_com","4":"Unfortunatly nobody likes this script; it would be kind of you to let me know why.\r\n\r\nThis plugin is useful to store information in a database-like design.\r\nWhilst opening a *.vimdb file, autocommands will be applied and open two windows. The left window gives a view on the table, the right window shows the record, the cursor is currently over (of course, after heaving created a new *.vimdb file, there will only be two empty windows shown). The first line of the table will become the header, which shows the names of the columns. For full instructions see readme, to have an idea, how a database will look like: look at example database shipped with the package.\r\n\r\nNote:\r\n1.) With the new improved (since version 0.5) TAB key mapping, editing the database will become a pleasure ;). \r\n2.) Cleared many bugs to make script a bit more compatible to Vim movement\/delete commands (cw, dw, D, C),\r\n     which might be useful editing records (But still the mighty TAB key dwarfs them all;).\r\n3.) Im through with bug removal, but there is still one, you should know: The table needs at least two columns to let the TAB key\r\n     work\r\n\r\nBe Warned:\r\nThe development of the script has advanced, but  i would still not recommend to store important data to a *.vimdb file.\r\n\r\n\r\nQuestions\/Suggestions\/Bug reports?\r\nJust compose a mail! (I dont promise to do anything but to be pleased to receive your mail. But just have a try) \r\nbenjaminschnitzler_at_gmail_dot_com","install_details":"- copy script into ~\/.vim\/plugins\r\n- create and edit a *.vimdb file","5":"- copy script into ~\/.vim\/plugins\r\n- create and edit a *.vimdb file","first_name":"Benjamin","6":"Benjamin","last_name":"Schnitzler","7":"Schnitzler","releases":[{"0":"2304","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"- cleared out many many bugs (see readme)\r\n- pushed the version to 1.0","3":"- cleared out many many bugs (see readme)\r\n- pushed the version to 1.0","package":"vimdb.tar","4":"vimdb.tar","src_id":"8992","5":"8992","creation_date":"1216680681","6":"1216680681"},{"0":"2304","vim_version":"6.0","1":"6.0","script_version":"0.5","2":"0.5","version_comment":"- cleared out no bugs this time\r\n- improved feature (see readme)","3":"- cleared out no bugs this time\r\n- improved feature (see readme)","package":"vimdb.tar","4":"vimdb.tar","src_id":"8987","5":"8987","creation_date":"1216661997","6":"1216661997"},{"0":"2304","vim_version":"7.0","1":"7.0","script_version":"0.4","2":"0.4","version_comment":"- cleared out some minor bugs (and maybe created new ones ;)\r\n- added new feature (see readme)\r\n- inserted an example database into the package","3":"- cleared out some minor bugs (and maybe created new ones ;)\r\n- added new feature (see readme)\r\n- inserted an example database into the package","package":"vimdb.tar","4":"vimdb.tar","src_id":"8986","5":"8986","creation_date":"1216656026","6":"1216656026"},{"0":"2304","vim_version":"7.0","1":"7.0","script_version":"0.3","2":"0.3","version_comment":"- corrected some minor bugs\r\n- added new feature (s. readme)\r\n- rewrote broken readme","3":"- corrected some minor bugs\r\n- added new feature (s. readme)\r\n- rewrote broken readme","package":"vimdb.tar","4":"vimdb.tar","src_id":"8985","5":"8985","creation_date":"1216637730","6":"1216637730"},{"0":"2304","vim_version":"7.0","1":"7.0","script_version":"0.2","2":"0.2","version_comment":"Added README file and new features (see readme)","3":"Added README file and new features (see readme)","package":"vimdb.vim.tar","4":"vimdb.vim.tar","src_id":"8984","5":"8984","creation_date":"1216617784","6":"1216617784"},{"0":"2304","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"vimdb.vim","4":"vimdb.vim","src_id":"8980","5":"8980","creation_date":"1216568374","6":"1216568374"}]},"2303":{"script_id":"2303","0":"2303","script_name":"spring.vim","1":"spring.vim","script_type":"color scheme","2":"color scheme","summary":"light green style","3":"light green style","description":"The spring.vim is a color sheme file (only for GVIM), which make the VIM bright with colors. It just like the flowers are in blossom in Spring. Additionally, it is said that there is a kind of light green color (RGB code: #cce8cf) which can avoid the eyestrain, at least make your eyes more comfortable. So the spring.vim was born. \r\n\r\nThere are some screenshots on the website: \r\n\r\nhttp:\/\/srcexpl.blogspot.com\/\r\n\r\n","4":"The spring.vim is a color sheme file (only for GVIM), which make the VIM bright with colors. It just like the flowers are in blossom in Spring. Additionally, it is said that there is a kind of light green color (RGB code: #cce8cf) which can avoid the eyestrain, at least make your eyes more comfortable. So the spring.vim was born. \r\n\r\nThere are some screenshots on the website: \r\n\r\nhttp:\/\/srcexpl.blogspot.com\/\r\n\r\n","install_details":"1\\ Copy the spring.vim to the colors directory of Vimfiles, such as ~\/.vim\/colors\/\r\n\r\n2\\ Add one command in your _vimrc or .vimrc: color spring\r\n\r\n3\\ Enjoy vimming:-)","5":"1\\ Copy the spring.vim to the colors directory of Vimfiles, such as ~\/.vim\/colors\/\r\n\r\n2\\ Add one command in your _vimrc or .vimrc: color spring\r\n\r\n3\\ Enjoy vimming:-)","first_name":"Wenlong","6":"Wenlong","last_name":"Che","7":"Che","releases":[{"0":"2303","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"1\\ Modified the colors of StatusLine, StatusLineNC and VertSplit and made it to be an revivalistic column.\r\n2\\ Add the color of Cursorline.","3":"1\\ Modified the colors of StatusLine, StatusLineNC and VertSplit and made it to be an revivalistic column.\r\n2\\ Add the color of Cursorline.","package":"spring.vim","4":"spring.vim","src_id":"9257","5":"9257","creation_date":"1221541860","6":"1221541860"},{"0":"2303","vim_version":"7.0","1":"7.0","script_version":"0.3","2":"0.3","version_comment":"Added GUI version judgment and modified the guifg and guibg of StatusLine, StatusLineNC and VertSplit.","3":"Added GUI version judgment and modified the guifg and guibg of StatusLine, StatusLineNC and VertSplit.","package":"spring.vim","4":"spring.vim","src_id":"9213","5":"9213","creation_date":"1220332363","6":"1220332363"},{"0":"2303","vim_version":"7.0","1":"7.0","script_version":"0.2","2":"0.2","version_comment":"Just modified some 'gui' options for more useful in the software development.","3":"Just modified some 'gui' options for more useful in the software development.","package":"spring.vim","4":"spring.vim","src_id":"9143","5":"9143","creation_date":"1219037676","6":"1219037676"},{"0":"2303","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"spring.vim","4":"spring.vim","src_id":"8971","5":"8971","creation_date":"1216362527","6":"1216362527"}]},"2302":{"script_id":"2302","0":"2302","script_name":"foldsearch","1":"foldsearch","script_type":"utility","2":"utility","summary":"fold away lines that don't match a given pattern","3":"fold away lines that don't match a given pattern","description":"This plugin provides commands that fold away lines that don't match a specific search pattern. This pattern can be the word under the cursor, the last search pattern, a regular expression or spelling errors. There are also commands to change the context of the shown lines.\r\n\r\nFor more information about the plugin and its commands please go to [GitHub].\r\n\r\n[GitHub]: https:\/\/github.com\/embear\/vim-foldsearch\r\n","4":"This plugin provides commands that fold away lines that don't match a specific search pattern. This pattern can be the word under the cursor, the last search pattern, a regular expression or spelling errors. There are also commands to change the context of the shown lines.\r\n\r\nFor more information about the plugin and its commands please go to [GitHub].\r\n\r\n[GitHub]: https:\/\/github.com\/embear\/vim-foldsearch\r\n","install_details":"foldsearch is now distributed as a vimball (see :help vimball)\r\n\r\nvim foldsearch.vmb\r\n:so %\r\n:q\r\n\r\nand that's all!","5":"foldsearch is now distributed as a vimball (see :help vimball)\r\n\r\nvim foldsearch.vmb\r\n:so %\r\n:q\r\n\r\nand that's all!","first_name":"Markus","6":"Markus","last_name":"Braun","7":"Braun","releases":[{"0":"2302","vim_version":"7.0","1":"7.0","script_version":"1.3.1","2":"1.3.1","version_comment":"- bugfix: repeated call to `:Fe` removed folding markers in file","3":"- bugfix: repeated call to `:Fe` removed folding markers in file","package":"foldsearch.vmb","4":"foldsearch.vmb","src_id":"28679","5":"28679","creation_date":"1714121390","6":"1714121390"},{"0":"2302","vim_version":"7.0","1":"7.0","script_version":"1.3.0","2":"1.3.0","version_comment":"- add ability to toggle between foldsearch and original view with `:Ft`\r\n- respect 'ignorecase' setting for pattern highlighting\r\n- bugfix: refactoring to make `:Fc` work again\r\n- bugfix: disable autocommands when restoring previous view to prevent unexpected side effects\r\n- bugfix: for unnamed buffers folds were not correctly restored when foldsearch is finished","3":"- add ability to toggle between foldsearch and original view with `:Ft`\r\n- respect 'ignorecase' setting for pattern highlighting\r\n- bugfix: refactoring to make `:Fc` work again\r\n- bugfix: disable autocommands when restoring previous view to prevent unexpected side effects\r\n- bugfix: for unnamed buffers folds were not correctly restored when foldsearch is finished","package":"foldsearch.vmb","4":"foldsearch.vmb","src_id":"28678","5":"28678","creation_date":"1714036012","6":"1714036012"},{"0":"2302","vim_version":"7.0","1":"7.0","script_version":"1.2.0","2":"1.2.0","version_comment":"- add abilitiy to choose the scope of foldsearch commands","3":"- add abilitiy to choose the scope of foldsearch commands","package":"foldsearch.vmb","4":"foldsearch.vmb","src_id":"28550","5":"28550","creation_date":"1696170256","6":"1696170256"},{"0":"2302","vim_version":"7.0","1":"7.0","script_version":"1.1.1","2":"1.1.1","version_comment":"- bugfix: add missing 'call' to ex command","3":"- bugfix: add missing 'call' to ex command","package":"foldsearch.vmb","4":"foldsearch.vmb","src_id":"22704","5":"22704","creation_date":"1418802027","6":"1418802027"},{"0":"2302","vim_version":"7.0","1":"7.0","script_version":"1.1.0","2":"1.1.0","version_comment":"- use vim autoload feature to load functions on demand\r\n- better save\/restore of modified options\r\n- added |g:foldsearch_disable_mappings| config variable\r\n- handle multiline regular expressions correctly","3":"- use vim autoload feature to load functions on demand\r\n- better save\/restore of modified options\r\n- added |g:foldsearch_disable_mappings| config variable\r\n- handle multiline regular expressions correctly","package":"foldsearch.vmb","4":"foldsearch.vmb","src_id":"22701","5":"22701","creation_date":"1418633618","6":"1418633618"},{"0":"2302","vim_version":"7.0","1":"7.0","script_version":"2213","2":"2213","version_comment":"- fixed a bug in context handling","3":"- fixed a bug in context handling","package":"foldsearch.vim","4":"foldsearch.vim","src_id":"9027","5":"9027","creation_date":"1217041382","6":"1217041382"},{"0":"2302","vim_version":"7.0","1":"7.0","script_version":"2209","2":"2209","version_comment":"Initial upload","3":"Initial upload","package":"foldsearch.vim","4":"foldsearch.vim","src_id":"8968","5":"8968","creation_date":"1216335212","6":"1216335212"}]},"2301":{"script_id":"2301","0":"2301","script_name":"Gembase dml plugins","1":"Gembase dml plugins","script_type":"utility","2":"utility","summary":"Syntax highlight, auto-indentation and omni-completion for Gembase dml file","3":"Syntax highlight, auto-indentation and omni-completion for Gembase dml file","description":"This package includes three scripts, a syntax script, an auto-indentation file and a ftplugin, which mainly provides omni-completion, suited declaration auto-completion and some accessorial functionalities.\r\n\r\n1. Syntax highlight\r\n-------------------------\r\n\r\nHighlighted language-elements listed as below:\r\n\r\n    (1) preprocessing statement;\r\n    (2) comment;\r\n    (3) six kinds of forms and its end_form keyword;\r\n    (4) six kinds of blocks and its end_block keyword;\r\n    (5) structure such as if, while and case statement, and highlighted their adjacent parenthesis;\r\n    (6) operator, constant and quote;\r\n    (7) system variable and user-defined variable;\r\n    (8) all qualifiers of form and block;\r\n    (9) most of metadata keywords.\r\n\r\n2. Auto-indentation\r\n--------------------------\r\n\r\nIn the insert mode, it will auto-indent form, block, structures and continuous lines marked with character \u00e2\u0080\u009c&\u00e2\u0080\u009d. In the normal mode, you can use it to check codes validity (hit keys: \"gg=G\"). Some mismatched keywords and abuse of character \"&\" were found in dml files when I run it.\r\n\r\nBy default, shiftwidth equals to 4 spaces (If you need a tab with 8 spaces, try to hit \"ctrl + v + tab\u00e2\u0080\u009c), value of syntactic indent equals to shiftwidth, and continue line marked with character \"&\" indents 8 spaces (you can configure it by changing the variable \"s:slip\" in indent script). \r\n\r\n3. ftplugin\r\n-------------\r\n\r\nThis script provides several useful functionalities, the most useful two are:\r\n\r\n     (1) in the insert mode, it provide both omni-completion and known-word-completion functionality by a function \"SuperCleverTab()\". It is very convenient, when you hit key \"Tab\", vim will pop a balloon to lists all candidate keywords, use \"CTRL + N\" or \"CTRL + P\" to move focus, use \"CTRL + Y\" to pick up a candidate and \"CTRL + E\" to return original status. If you want to print a \"Tab\", just try \"CTRL + V + Tab\". You can also manually remap the hot-key, besides, an menu item also provides to execute it;\r\n     (2) in the insert mode, it will auto-complete suited declaration keywords after its beginning was inputed, for instance, if you input string \"BEGIN_BLOCK?\", NOTICE: the keyword must be followed by a question mark \"?\", then hit a space, system will auto-complete \"END_BLOCK\";\r\n\r\nOthers are some accessorial enhancements:\r\n\r\n     (3) set comments to format dashed line with leader character \"!\" when hitting <CR> or using \"o\";\r\n     (4) set hot-keys to support fast jumping among blocks by using \"]]\" (next \"BEGIN_BLOCK\"), \"[[\" (previous \"BEGIN_BLOCK\"), \"][\" (next \"END_BLOCK\"), \"[]\" (previous \"END_BLOCK\"), and among comments by using \"]!\" (next comment) and \"[!\" (previous comment);\r\n     (5) support \"matchit\" plugin to jump between keywords within a structure by hitting key \"%\" in normal mode. Such as \"IF\" -> \"ELSE_IF\" -> \"ELSE\" -> \"END_IF\", etc.\r\n     (6) also provides parenthesis auto-completion;\r\n     (7) if you runs in GUI, it provides a menu column, which lists some functional item;\r\n     (8) if you runs in GUI and made a folder, when cursor hangs over it, then system will display a help tip to show the less than 30 lines within folder;\r\n     (9) provide a quick approach to comment or uncomment selected lines by GUI menu.\r\n\r\n4. Upgrade\r\n---------------\r\n\r\nBy default, GetLatestVimScripts plugin is included in Vim installation package, whose version is higher than v7. So you can use it to auto-download the newest package. Add below line into file \"GetLatestVimScripts.dat\":\r\n\r\n                           2301 1 gembase-plugins\r\n\r\nand use this command \":GetLatestVimScripts\" to upgrade it.\r\n\r\n5. TODO\r\n------------\r\n\r\n     (1) when handling an ending statement, check its mate to decide whether indent;\r\n     (2) support fast jumping and matchit switching between six kinds of forms;\r\n     (3) normalize syntax format of current line before open a new line;\r\n     (4) assemble the results of keyword-completion and context-completion together.\r\n\r\n6. Acknowledgments\r\n----------------------------\r\n\r\nI would like to thank Kim Schulz, without his excellent book \"Hacking Vim\", I can't complete ftplugin script in a few days.","4":"This package includes three scripts, a syntax script, an auto-indentation file and a ftplugin, which mainly provides omni-completion, suited declaration auto-completion and some accessorial functionalities.\r\n\r\n1. Syntax highlight\r\n-------------------------\r\n\r\nHighlighted language-elements listed as below:\r\n\r\n    (1) preprocessing statement;\r\n    (2) comment;\r\n    (3) six kinds of forms and its end_form keyword;\r\n    (4) six kinds of blocks and its end_block keyword;\r\n    (5) structure such as if, while and case statement, and highlighted their adjacent parenthesis;\r\n    (6) operator, constant and quote;\r\n    (7) system variable and user-defined variable;\r\n    (8) all qualifiers of form and block;\r\n    (9) most of metadata keywords.\r\n\r\n2. Auto-indentation\r\n--------------------------\r\n\r\nIn the insert mode, it will auto-indent form, block, structures and continuous lines marked with character \u00e2\u0080\u009c&\u00e2\u0080\u009d. In the normal mode, you can use it to check codes validity (hit keys: \"gg=G\"). Some mismatched keywords and abuse of character \"&\" were found in dml files when I run it.\r\n\r\nBy default, shiftwidth equals to 4 spaces (If you need a tab with 8 spaces, try to hit \"ctrl + v + tab\u00e2\u0080\u009c), value of syntactic indent equals to shiftwidth, and continue line marked with character \"&\" indents 8 spaces (you can configure it by changing the variable \"s:slip\" in indent script). \r\n\r\n3. ftplugin\r\n-------------\r\n\r\nThis script provides several useful functionalities, the most useful two are:\r\n\r\n     (1) in the insert mode, it provide both omni-completion and known-word-completion functionality by a function \"SuperCleverTab()\". It is very convenient, when you hit key \"Tab\", vim will pop a balloon to lists all candidate keywords, use \"CTRL + N\" or \"CTRL + P\" to move focus, use \"CTRL + Y\" to pick up a candidate and \"CTRL + E\" to return original status. If you want to print a \"Tab\", just try \"CTRL + V + Tab\". You can also manually remap the hot-key, besides, an menu item also provides to execute it;\r\n     (2) in the insert mode, it will auto-complete suited declaration keywords after its beginning was inputed, for instance, if you input string \"BEGIN_BLOCK?\", NOTICE: the keyword must be followed by a question mark \"?\", then hit a space, system will auto-complete \"END_BLOCK\";\r\n\r\nOthers are some accessorial enhancements:\r\n\r\n     (3) set comments to format dashed line with leader character \"!\" when hitting <CR> or using \"o\";\r\n     (4) set hot-keys to support fast jumping among blocks by using \"]]\" (next \"BEGIN_BLOCK\"), \"[[\" (previous \"BEGIN_BLOCK\"), \"][\" (next \"END_BLOCK\"), \"[]\" (previous \"END_BLOCK\"), and among comments by using \"]!\" (next comment) and \"[!\" (previous comment);\r\n     (5) support \"matchit\" plugin to jump between keywords within a structure by hitting key \"%\" in normal mode. Such as \"IF\" -> \"ELSE_IF\" -> \"ELSE\" -> \"END_IF\", etc.\r\n     (6) also provides parenthesis auto-completion;\r\n     (7) if you runs in GUI, it provides a menu column, which lists some functional item;\r\n     (8) if you runs in GUI and made a folder, when cursor hangs over it, then system will display a help tip to show the less than 30 lines within folder;\r\n     (9) provide a quick approach to comment or uncomment selected lines by GUI menu.\r\n\r\n4. Upgrade\r\n---------------\r\n\r\nBy default, GetLatestVimScripts plugin is included in Vim installation package, whose version is higher than v7. So you can use it to auto-download the newest package. Add below line into file \"GetLatestVimScripts.dat\":\r\n\r\n                           2301 1 gembase-plugins\r\n\r\nand use this command \":GetLatestVimScripts\" to upgrade it.\r\n\r\n5. TODO\r\n------------\r\n\r\n     (1) when handling an ending statement, check its mate to decide whether indent;\r\n     (2) support fast jumping and matchit switching between six kinds of forms;\r\n     (3) normalize syntax format of current line before open a new line;\r\n     (4) assemble the results of keyword-completion and context-completion together.\r\n\r\n6. Acknowledgments\r\n----------------------------\r\n\r\nI would like to thank Kim Schulz, without his excellent book \"Hacking Vim\", I can't complete ftplugin script in a few days.","install_details":"1. For Unix:\r\n---------------\r\n\r\n          run script \"gembase-unix\" to install or uninstall:\r\n                .\/gembase-unix -i\r\n                .\/gembase-unix -u\r\n\r\n2. For Windows:\r\n----------------------\r\n\r\n          put the filetype script into directory $VIM\\vimfiles\\\r\n          put the syntax script into directory $VIM\\vimfiles\\syntax\\\r\n          put the indent script into directory $VIM\\vimfiles\\indent\\\r\n          put the ftplugin script (dml-windows.vim) into directory $VIM\\vimfiles\\ftplugin\\, and rename it as \"dml.vim\"\r\n          put the file \".\\ftplugin\\gembase\\dict\" into directory $VIM\\vimfiles\\ftplugin\\gembase\\","5":"1. For Unix:\r\n---------------\r\n\r\n          run script \"gembase-unix\" to install or uninstall:\r\n                .\/gembase-unix -i\r\n                .\/gembase-unix -u\r\n\r\n2. For Windows:\r\n----------------------\r\n\r\n          put the filetype script into directory $VIM\\vimfiles\\\r\n          put the syntax script into directory $VIM\\vimfiles\\syntax\\\r\n          put the indent script into directory $VIM\\vimfiles\\indent\\\r\n          put the ftplugin script (dml-windows.vim) into directory $VIM\\vimfiles\\ftplugin\\, and rename it as \"dml.vim\"\r\n          put the file \".\\ftplugin\\gembase\\dict\" into directory $VIM\\vimfiles\\ftplugin\\gembase\\","first_name":"Frank","6":"Frank","last_name":"Sun","7":"Sun","releases":[{"0":"2301","vim_version":"7.0","1":"7.0","script_version":"1.0.5","2":"1.0.5","version_comment":"-Fixed a BUG which made omni-completion instable in last two versions.","3":"-Fixed a BUG which made omni-completion instable in last two versions.","package":"gembase-plugins.zip","4":"gembase-plugins.zip","src_id":"9361","5":"9361","creation_date":"1224176949","6":"1224176949"},{"0":"2301","vim_version":"7.0","1":"7.0","script_version":"1.05","2":"1.05","version_comment":"+ ADD a comment\/uncomment toggle for selected lines;\r\n+ ADD two Gembase menu items for indentation and fold function;\r\n+ Optimize the layout of Gembase menu;\r\n- Fix BUGs for menu items' action;\r\n- Fixed a misprint in CompleteKeywords function which failed omni-completion in unix platfom;\r\n- Fix a BUG in abbreviation that brings an extra space within parentheses.","3":"+ ADD a comment\/uncomment toggle for selected lines;\r\n+ ADD two Gembase menu items for indentation and fold function;\r\n+ Optimize the layout of Gembase menu;\r\n- Fix BUGs for menu items' action;\r\n- Fixed a misprint in CompleteKeywords function which failed omni-completion in unix platfom;\r\n- Fix a BUG in abbreviation that brings an extra space within parentheses.","package":"gembase-plugins.zip","4":"gembase-plugins.zip","src_id":"9357","5":"9357","creation_date":"1224149483","6":"1224149483"},{"0":"2301","vim_version":"7.0","1":"7.0","script_version":"1.02","2":"1.02","version_comment":"+ ADD an installation script for unix.","3":"+ ADD an installation script for unix.","package":"gembase-plugins.zip","4":"gembase-plugins.zip","src_id":"9192","5":"9192","creation_date":"1219979271","6":"1219979271"},{"0":"2301","vim_version":"7.0","1":"7.0","script_version":"1.02","2":"1.02","version_comment":"- Fixed a BUG: change the dict path for unix platform\r\n+ ADD a function: enhance omni-completion to SuperCleverTab(), so as to use \"Tab\" to auto-complete","3":"- Fixed a BUG: change the dict path for unix platform\r\n+ ADD a function: enhance omni-completion to SuperCleverTab(), so as to use \"Tab\" to auto-complete","package":"gembase-plugins.zip","4":"gembase-plugins.zip","src_id":"9013","5":"9013","creation_date":"1216878156","6":"1216878156"},{"0":"2301","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"- Fixed a BUG: suited declaration auto-completion conflicts with comment.\r\n+ ADD: omni-completion functionality.","3":"- Fixed a BUG: suited declaration auto-completion conflicts with comment.\r\n+ ADD: omni-completion functionality.","package":"gembase-plugins.zip","4":"gembase-plugins.zip","src_id":"9007","5":"9007","creation_date":"1216776113","6":"1216776113"},{"0":"2301","vim_version":"7.0","1":"7.0","script_version":"0.9.09","2":"0.9.09","version_comment":"+ auto-complete suited declaration keywords;\r\n+ show help tip balloon when cursor hangs over a folder;\r\n+ parenthesis auto-complete","3":"+ auto-complete suited declaration keywords;\r\n+ show help tip balloon when cursor hangs over a folder;\r\n+ parenthesis auto-complete","package":"gembase-plugins.zip","4":"gembase-plugins.zip","src_id":"8994","5":"8994","creation_date":"1216696640","6":"1216696640"},{"0":"2301","vim_version":"7.0","1":"7.0","script_version":"0.9.06","2":"0.9.06","version_comment":"add a ftplugin script to support:\r\n+ set comments to format dashed line;\r\n+ support fast jumpping among blocks by using \"]]\", etc;\r\n+ support \"matchit\" plugin by hitting key \"%\".\r\n\r\nadd a menu \"Gembase\".","3":"add a ftplugin script to support:\r\n+ set comments to format dashed line;\r\n+ support fast jumpping among blocks by using \"]]\", etc;\r\n+ support \"matchit\" plugin by hitting key \"%\".\r\n\r\nadd a menu \"Gembase\".","package":"gembase-plugins.zip","4":"gembase-plugins.zip","src_id":"8991","5":"8991","creation_date":"1216679871","6":"1216679871"},{"0":"2301","vim_version":"7.0","1":"7.0","script_version":"0.9.03","2":"0.9.03","version_comment":"Add some local vim options into indent script, and most metadata keywords into syntax script.","3":"Add some local vim options into indent script, and most metadata keywords into syntax script.","package":"gembase-plugins.zip","4":"gembase-plugins.zip","src_id":"8972","5":"8972","creation_date":"1216369480","6":"1216369480"}]},"2300":{"script_id":"2300","0":"2300","script_name":"perl-mauke.vim","1":"perl-mauke.vim","script_type":"syntax","2":"syntax","summary":"improved perl syntax highlighting","3":"improved perl syntax highlighting","description":"This file is based on the perl.vim syntax definition that comes with vim, but with some heavy modifications intended to improve vim's perl highlighting.\r\n\r\nThe list of changes includes:\r\n* 'new' and 'croak' are not keywords and no longer highlighted as such\r\n* Special highlighting for pragmas (e.g. \"use warnings\") now applies to all pragmas coming with perl\r\n* Fixed number highlighting (\"0X\" is not a valid hex prefix, \"L\" is not a valid suffix)\r\n* Fixed escape sequence highlighting (\"\\X123\" is not a hex escape, \"\\123\" is limited to three octal digits)\r\n* Lots of improvements in the matching of quoted constructs:\r\n  - vim no longer thinks \"!\" is a quoting operator (so \"!!\" works right)\r\n  - support for arbitrary quoting delimiters (e.g. \"m%...%\" works)\r\n  - I've also tried to make nesting work (e.g. \"s[foo[bar]][b[a]z]g\")\r\n* Full support for subroutine definitions (parsing of prototypes and attributes)\r\n* Recognizes v-strings and statement labels\r\n* \"=>\" quotes its LHS, even if it's a keyword\r\n* Perl 5.10 support: new keywords ('given', 'when', 'default', 'state', 'break') and regexp control operators ('PRUNE', 'SKIP', 'COMMIT', etc.)\r\n","4":"This file is based on the perl.vim syntax definition that comes with vim, but with some heavy modifications intended to improve vim's perl highlighting.\r\n\r\nThe list of changes includes:\r\n* 'new' and 'croak' are not keywords and no longer highlighted as such\r\n* Special highlighting for pragmas (e.g. \"use warnings\") now applies to all pragmas coming with perl\r\n* Fixed number highlighting (\"0X\" is not a valid hex prefix, \"L\" is not a valid suffix)\r\n* Fixed escape sequence highlighting (\"\\X123\" is not a hex escape, \"\\123\" is limited to three octal digits)\r\n* Lots of improvements in the matching of quoted constructs:\r\n  - vim no longer thinks \"!\" is a quoting operator (so \"!!\" works right)\r\n  - support for arbitrary quoting delimiters (e.g. \"m%...%\" works)\r\n  - I've also tried to make nesting work (e.g. \"s[foo[bar]][b[a]z]g\")\r\n* Full support for subroutine definitions (parsing of prototypes and attributes)\r\n* Recognizes v-strings and statement labels\r\n* \"=>\" quotes its LHS, even if it's a keyword\r\n* Perl 5.10 support: new keywords ('given', 'when', 'default', 'state', 'break') and regexp control operators ('PRUNE', 'SKIP', 'COMMIT', etc.)\r\n","install_details":"Copy perl.vim into ~\/.vim\/syntax\/ and vim will find it before the \"standard\" perl syntax file that comes with vim.","5":"Copy perl.vim into ~\/.vim\/syntax\/ and vim will find it before the \"standard\" perl syntax file that comes with vim.","first_name":"Lukas","6":"Lukas","last_name":"Mai","7":"Mai","releases":[{"0":"2300","vim_version":"6.0","1":"6.0","script_version":"0.11","2":"0.11","version_comment":"* fold \"given\" blocks\r\n* highlight \\012 as octal escape in regexes\r\n* fix \"$foo:bar\" highlighting if 'iskeyword' contains \":\"\r\n* switch scope_in_variables and extended_vars on by default","3":"* fold \"given\" blocks\r\n* highlight \\012 as octal escape in regexes\r\n* fix \"$foo:bar\" highlighting if 'iskeyword' contains \":\"\r\n* switch scope_in_variables and extended_vars on by default","package":"perl.vim","4":"perl.vim","src_id":"9087","5":"9087","creation_date":"1218134623","6":"1218134623"},{"0":"2300","vim_version":"6.0","1":"6.0","script_version":"0.10","2":"0.10","version_comment":"Initial upload","3":"Initial upload","package":"perl.vim","4":"perl.vim","src_id":"8956","5":"8956","creation_date":"1216117758","6":"1216117758"}]},"2299":{"script_id":"2299","0":"2299","script_name":"fortran.vim","1":"fortran.vim","script_type":"indent","2":"indent","summary":"Additional indentation rules for Fortran 95 and Fortran 90","3":"Additional indentation rules for Fortran 95 and Fortran 90","description":"This script provides additional indentation rules (continued statements; preprocessor instructions; subroutine, function and forall statements) to Ajit J. Thakkar's Vim indent script for Fortran free source form.","4":"This script provides additional indentation rules (continued statements; preprocessor instructions; subroutine, function and forall statements) to Ajit J. Thakkar's Vim indent script for Fortran free source form.","install_details":"Place the fortran.vim file in the $HOME\/.vim\/after\/indent\/ directory.\r\n\r\nIn order to use this script, you must use Ajit J. Thakkar's Vim scripts for Fortran. Those should already be part of your Vim installation (in the $VIMRUNTIME directory). If not, you may find them at http:\/\/www.unb.ca\/fredericton\/science\/chem\/ajit\/f_vim.htm","5":"Place the fortran.vim file in the $HOME\/.vim\/after\/indent\/ directory.\r\n\r\nIn order to use this script, you must use Ajit J. Thakkar's Vim scripts for Fortran. Those should already be part of your Vim installation (in the $VIMRUNTIME directory). If not, you may find them at http:\/\/www.unb.ca\/fredericton\/science\/chem\/ajit\/f_vim.htm","first_name":"S\u00c3\u00a9bastien","6":"S\u00c3\u00a9bastien","last_name":"Burton","7":"Burton","releases":[{"0":"2299","vim_version":"7.0","1":"7.0","script_version":"0.4","2":"0.4","version_comment":"Update indentation rules for subroutine, function and forall statements (it now supports \"recursive\" statement and \"type function\", thank you Hong Xu!), e.g.: \"recursive pure subroutine\", \"elemental integer(2) function\", \"type(my_type) function\"...","3":"Update indentation rules for subroutine, function and forall statements (it now supports \"recursive\" statement and \"type function\", thank you Hong Xu!), e.g.: \"recursive pure subroutine\", \"elemental integer(2) function\", \"type(my_type) function\"...","package":"fortran.vim","4":"fortran.vim","src_id":"15717","5":"15717","creation_date":"1306282913","6":"1306282913"},{"0":"2299","vim_version":"7.0","1":"7.0","script_version":"0.3.1","2":"0.3.1","version_comment":"Update indentkeys","3":"Update indentkeys","package":"fortran.vim","4":"fortran.vim","src_id":"9268","5":"9268","creation_date":"1222095598","6":"1222095598"},{"0":"2299","vim_version":"7.0","1":"7.0","script_version":"0.3","2":"0.3","version_comment":"Indentation rules for subroutine, function and forall statements. Bug correction in the buffer behaviour.","3":"Indentation rules for subroutine, function and forall statements. Bug correction in the buffer behaviour.","package":"fortran.vim","4":"fortran.vim","src_id":"9267","5":"9267","creation_date":"1222091065","6":"1222091065"}]},"2298":{"script_id":"2298","0":"2298","script_name":"codepad","1":"codepad","script_type":"utility","2":"utility","summary":"Post the contents of your current buffer to the pastebin service at codepad.org","3":"Post the contents of your current buffer to the pastebin service at codepad.org","description":"The plugin adds two new commands:\r\n\r\n:CPPaste\r\n    to send the current buffer to http:\/\/codepad.org, open your pasted code\r\n    in your webbrowser, and copy the URL of the pasted snippet to the\r\n    clipboard.\r\n\r\n\r\n:CPRun\r\n    to send the current buffer to http:\/\/codepad.org, execute it on their server,\r\n    and open both the pasted source and the program output in your browser.\r\n    The URL of the pasted snippets is copied to the clipboard as well.\r\n\r\n\r\nThe correct filetype is automatically detected through the 'filetype' option.","4":"The plugin adds two new commands:\r\n\r\n:CPPaste\r\n    to send the current buffer to http:\/\/codepad.org, open your pasted code\r\n    in your webbrowser, and copy the URL of the pasted snippet to the\r\n    clipboard.\r\n\r\n\r\n:CPRun\r\n    to send the current buffer to http:\/\/codepad.org, execute it on their server,\r\n    and open both the pasted source and the program output in your browser.\r\n    The URL of the pasted snippets is copied to the clipboard as well.\r\n\r\n\r\nThe correct filetype is automatically detected through the 'filetype' option.","install_details":"Copy the script to ~\/.vim\/plugin\/ (OS X, other Unices) or to $HOME\/vimfiles\/plugin (Windows). This requires +python support in vim.","5":"Copy the script to ~\/.vim\/plugin\/ (OS X, other Unices) or to $HOME\/vimfiles\/plugin (Windows). This requires +python support in vim.","first_name":"Nicolas","6":"Nicolas","last_name":"Weber","7":"Weber","releases":[{"0":"2298","vim_version":"7.0","1":"7.0","script_version":"1.4","2":"1.4","version_comment":"Fix uploading of ocaml files. Patch by Johannes Hoff.","3":"Fix uploading of ocaml files. Patch by Johannes Hoff.","package":"codepad.vim","4":"codepad.vim","src_id":"13438","5":"13438","creation_date":"1280499575","6":"1280499575"},{"0":"2298","vim_version":"7.0","1":"7.0","script_version":"1.3","2":"1.3","version_comment":"Also copy URL of pasted code to clipboard.","3":"Also copy URL of pasted code to clipboard.","package":"codepad.vim","4":"codepad.vim","src_id":"9074","5":"9074","creation_date":"1217914325","6":"1217914325"},{"0":"2298","vim_version":"7.0","1":"7.0","script_version":"1.2","2":"1.2","version_comment":"Nicer error message if +python is not available (error message only shown if plugin is used, not when it's loaded).","3":"Nicer error message if +python is not available (error message only shown if plugin is used, not when it's loaded).","package":"codepad.vim","4":"codepad.vim","src_id":"8978","5":"8978","creation_date":"1216537601","6":"1216537601"},{"0":"2298","vim_version":"7.0","1":"7.0","script_version":"1.1","2":"1.1","version_comment":"Make script work with input buffers that contain more than one line.","3":"Make script work with input buffers that contain more than one line.","package":"codepad.vim","4":"codepad.vim","src_id":"8952","5":"8952","creation_date":"1216027475","6":"1216027475"},{"0":"2298","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"codepad.vim","4":"codepad.vim","src_id":"8951","5":"8951","creation_date":"1216027318","6":"1216027318"}]},"2297":{"script_id":"2297","0":"2297","script_name":"sipngrep helper","1":"sipngrep helper","script_type":"ftplugin","2":"ftplugin","summary":"Helper functions for looking through sip packet captures","3":"Helper functions for looking through sip packet captures","description":"Helper functions mapped to\r\n<Plug>SkipToMatchingRequest (standard <LocalLeader>sq)\r\n<Plug>SkipToMatchingResponse (standard <LocalLeader>sr)\r\nWhen used with cursor over a packet, they will find either following matching (by CSeq) response, or previous matching request.\r\n\r\nExpected format of sip capture is the same as produced by `ngrep -q -tt -W byline ....`\r\nWorks on the same captures as syntax sipngrep highlighter: vimscript #2296","4":"Helper functions mapped to\r\n<Plug>SkipToMatchingRequest (standard <LocalLeader>sq)\r\n<Plug>SkipToMatchingResponse (standard <LocalLeader>sr)\r\nWhen used with cursor over a packet, they will find either following matching (by CSeq) response, or previous matching request.\r\n\r\nExpected format of sip capture is the same as produced by `ngrep -q -tt -W byline ....`\r\nWorks on the same captures as syntax sipngrep highlighter: vimscript #2296","install_details":"Put the ftplugin in .vim\/ftplugin\/sipngrep.vim and use `:setf sipngrep`","5":"Put the ftplugin in .vim\/ftplugin\/sipngrep.vim and use `:setf sipngrep`","first_name":"Stanis\u0142aw","6":"Stanisław","last_name":"Pitucha","7":"Pitucha","releases":[{"0":"2297","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"sipngrep.vim","4":"sipngrep.vim","src_id":"8947","5":"8947","creation_date":"1215970580","6":"1215970580"}]},"2296":{"script_id":"2296","0":"2296","script_name":"sipngrep","1":"sipngrep","script_type":"syntax","2":"syntax","summary":"Syntax file for sip captures from ngrep (udp)","3":"Syntax file for sip captures from ngrep (udp)","description":"Syntax includes:\r\n- coloring numbers \/ usernames\r\n- folding with first line of packet in summary\r\n- coloring 'important' and other headers\r\n- coloring for standard possible problems (lack of username or domain, incorrect method, private ips)\r\n- marking 4XX, 5XX, 6XX statuses\r\n\r\nDesigned looking at capture produced by `ngrep -q -tt -W byline udp and port 5060` or similar.","4":"Syntax includes:\r\n- coloring numbers \/ usernames\r\n- folding with first line of packet in summary\r\n- coloring 'important' and other headers\r\n- coloring for standard possible problems (lack of username or domain, incorrect method, private ips)\r\n- marking 4XX, 5XX, 6XX statuses\r\n\r\nDesigned looking at capture produced by `ngrep -q -tt -W byline udp and port 5060` or similar.","install_details":"Put the file in vim directory\/syntax\/sipngrep.vim","5":"Put the file in vim directory\/syntax\/sipngrep.vim","first_name":"Stanis\u0142aw","6":"Stanisław","last_name":"Pitucha","7":"Pitucha","releases":[{"0":"2296","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"sipngrep.vim","4":"sipngrep.vim","src_id":"8946","5":"8946","creation_date":"1215969835","6":"1215969835"}]},"2295":{"script_id":"2295","0":"2295","script_name":"Glob Edit","1":"Glob Edit","script_type":"utility","2":"utility","summary":"Open lots of files at once.","3":"Open lots of files at once.","description":"This script is based on vimtip #146. It enables you to open any amount of files at once using the edit command. You can simply provide multiple parameters or use glob patterns.\r\n\r\nExamples:\r\n\r\n:edit foo.txt bar.txt\r\n:edit foo\/**\/*.txt\r\n\r\nUPDATE:\r\nI just found out that :args does just what this script tries to do.","4":"This script is based on vimtip #146. It enables you to open any amount of files at once using the edit command. You can simply provide multiple parameters or use glob patterns.\r\n\r\nExamples:\r\n\r\n:edit foo.txt bar.txt\r\n:edit foo\/**\/*.txt\r\n\r\nUPDATE:\r\nI just found out that :args does just what this script tries to do.","install_details":"Just place the script in your plugin directory.","5":"Just place the script in your plugin directory.","first_name":"Jonas","6":"Jonas","last_name":"Kramer","7":"Kramer","releases":[{"0":"2295","vim_version":"7.0","1":"7.0","script_version":"0.01","2":"0.01","version_comment":"Initial upload","3":"Initial upload","package":"glob-edit.vim","4":"glob-edit.vim","src_id":"8933","5":"8933","creation_date":"1215838692","6":"1215838692"}]},"2294":{"script_id":"2294","0":"2294","script_name":"SwapIt","1":"SwapIt","script_type":"utility","2":"utility","summary":"Extensible keyword swapper (turn yes to no, True to False and more)","3":"Extensible keyword swapper (turn yes to no, True to False and more)","description":"swapit.vim is a vim plugin designed to make repetitive changes easier.\r\n\r\nOn a current word that is a member of a swap list use the\r\nincrementor\/decrementor keys (:he ctrl-a,ctrl-x). The script\r\nwill cycle through a list of related options.\r\n\r\nA quick tty example is here http:\/\/ttyshare.com\/rec\/michael\/76068689\/\r\n\r\nSwapit now offers omnicomplete based swapping on css files!\r\nCss example plugging into omnicomplete http:\/\/ttyshare.com\/rec\/michael\/76409608\/\r\n\r\nThe repository is here http:\/\/github.com\/mjbrownie\/swapit\/tree\/master. Any list submissions would be appreciated. \r\n\r\nThe idea is to compile a list of common property swaps for various languages\/frameworks \r\n\r\nNOTE: This has been done before in a simpler vimscript#1676 script. This script differs in it's ability to handle phrase swapping eg 'int' to 'unsigned int'. It is also FileType aware.\r\n\r\neg. 1. Boolean\r\n\r\nfoo=true\r\n\r\nin normal mode, pressing ctrl-a on the t will make it\r\n\r\nfoo=false\r\n\r\neg. 2. Multi Word Swaps.\r\n\r\nHello World! is a test multi word swap.\r\n\r\non 'Hello World!' go select in visual (vi'<ctrl-a>) to get\r\n\r\n'GoodBye Cruel World!'\r\n\r\neg 3. Defining custom swaps\r\n\r\nA custom list is defined as follows.\r\n\r\n:SwapList datatypes bool char int float double\r\n\r\nThe first argument is the list name and following args\r\nare members of the list.\r\n\r\nif there is no match then the regular incrementor decrementor\r\nfunction will work on numbers\r\n\r\nAt the bottom of the script I've added some generic stuff but\r\n\r\nYou can create a custom swap file for file types at\r\n\r\n~\/.vim\/after\/ftplugins\/<filetype>_swapit.vim\r\nwith custom execs eg.\r\nexec \"SwapList function_scope private protected public\"\r\n\r\nFor this alpha version multi word swap list is a bit trickier\r\nto to define. You can add to the swap list directly using\r\nvimscript within a after\/ftplugin\/<ft>_swap.vim file\r\n\r\n call extend(g:swap_lists, [{'name':'Multi Word Example',\r\n             \\\\'options': ['swap with spaces',\r\n             \\\\'swap with  @#$@# chars in it' ,\r\n             \\\\'running out of ideas here...']}])\r\n\r\nFuture versions will make this cleaner with a :Command\r\n\r\nAlso if you have a spur of the moment Idea type\r\n:SwapIdea\r\nTo get to the current filetypes swapit file\r\n\r\nNote: This alpha version doesnt create the directory structure\r\n\r\nTo integrate with other incrementor scripts (such as\r\nspeeddating.vim vimscript #2120  or monday.vim vimscript #1046), \r\n:nmap <Plug>SwapItFallbackIncrement and <Plug>SwapItFallbackDecrement\r\nto the keys that should be invoked when swapit doesn't have a\r\nproper option. For example for speeddating.vim:\r\n\r\nnmap <Plug>SwapItFallbackIncrement <Plug>SpeedDatingUp\r\nnmap <Plug>SwapItFallbackDecrement <Plug>SpeedDatingDown\r\n","4":"swapit.vim is a vim plugin designed to make repetitive changes easier.\r\n\r\nOn a current word that is a member of a swap list use the\r\nincrementor\/decrementor keys (:he ctrl-a,ctrl-x). The script\r\nwill cycle through a list of related options.\r\n\r\nA quick tty example is here http:\/\/ttyshare.com\/rec\/michael\/76068689\/\r\n\r\nSwapit now offers omnicomplete based swapping on css files!\r\nCss example plugging into omnicomplete http:\/\/ttyshare.com\/rec\/michael\/76409608\/\r\n\r\nThe repository is here http:\/\/github.com\/mjbrownie\/swapit\/tree\/master. Any list submissions would be appreciated. \r\n\r\nThe idea is to compile a list of common property swaps for various languages\/frameworks \r\n\r\nNOTE: This has been done before in a simpler vimscript#1676 script. This script differs in it's ability to handle phrase swapping eg 'int' to 'unsigned int'. It is also FileType aware.\r\n\r\neg. 1. Boolean\r\n\r\nfoo=true\r\n\r\nin normal mode, pressing ctrl-a on the t will make it\r\n\r\nfoo=false\r\n\r\neg. 2. Multi Word Swaps.\r\n\r\nHello World! is a test multi word swap.\r\n\r\non 'Hello World!' go select in visual (vi'<ctrl-a>) to get\r\n\r\n'GoodBye Cruel World!'\r\n\r\neg 3. Defining custom swaps\r\n\r\nA custom list is defined as follows.\r\n\r\n:SwapList datatypes bool char int float double\r\n\r\nThe first argument is the list name and following args\r\nare members of the list.\r\n\r\nif there is no match then the regular incrementor decrementor\r\nfunction will work on numbers\r\n\r\nAt the bottom of the script I've added some generic stuff but\r\n\r\nYou can create a custom swap file for file types at\r\n\r\n~\/.vim\/after\/ftplugins\/<filetype>_swapit.vim\r\nwith custom execs eg.\r\nexec \"SwapList function_scope private protected public\"\r\n\r\nFor this alpha version multi word swap list is a bit trickier\r\nto to define. You can add to the swap list directly using\r\nvimscript within a after\/ftplugin\/<ft>_swap.vim file\r\n\r\n call extend(g:swap_lists, [{'name':'Multi Word Example',\r\n             \\\\'options': ['swap with spaces',\r\n             \\\\'swap with  @#$@# chars in it' ,\r\n             \\\\'running out of ideas here...']}])\r\n\r\nFuture versions will make this cleaner with a :Command\r\n\r\nAlso if you have a spur of the moment Idea type\r\n:SwapIdea\r\nTo get to the current filetypes swapit file\r\n\r\nNote: This alpha version doesnt create the directory structure\r\n\r\nTo integrate with other incrementor scripts (such as\r\nspeeddating.vim vimscript #2120  or monday.vim vimscript #1046), \r\n:nmap <Plug>SwapItFallbackIncrement and <Plug>SwapItFallbackDecrement\r\nto the keys that should be invoked when swapit doesn't have a\r\nproper option. For example for speeddating.vim:\r\n\r\nnmap <Plug>SwapItFallbackIncrement <Plug>SpeedDatingUp\r\nnmap <Plug>SwapItFallbackDecrement <Plug>SpeedDatingDown\r\n","install_details":"place swapit.vim in plugins directory\r\n\r\n(for extending to filetypes)\r\nmkdir ~\/.vim\/after\/ftplugin\/","5":"place swapit.vim in plugins directory\r\n\r\n(for extending to filetypes)\r\nmkdir ~\/.vim\/after\/ftplugin\/","first_name":"Michael","6":"Michael","last_name":"Brown","7":"Brown","releases":[{"0":"2294","vim_version":"7.0","1":"7.0","script_version":"0.3.5","2":"0.3.5","version_comment":"Added support for repeat.vim . Thanks Hotschke","3":"Added support for repeat.vim . Thanks Hotschke","package":"swapit-0.3.5.zip","4":"swapit-0.3.5.zip","src_id":"23578","5":"23578","creation_date":"1441607796","6":"1441607796"},{"0":"2294","vim_version":"7.0","1":"7.0","script_version":"0.3.4","2":"0.3.4","version_comment":"added lists for Latex file handling. thanks kiryph  ","3":"added lists for Latex file handling. thanks kiryph  ","package":"swapit-0.3.4.zip","4":"swapit-0.3.4.zip","src_id":"22806","5":"22806","creation_date":"1421552916","6":"1421552916"},{"0":"2294","vim_version":"7.0","1":"7.0","script_version":"0.3.3","2":"0.3.3","version_comment":"add ftplugin that cycles through interactive git rebase options.\r\n\r\n#  p, pick = use commit\r\n#  r, reword = use commit, but edit the commit message\r\n#  e, edit = use commit, but stop for amending\r\n#  s, squash = use commit, but meld into previous commit\r\n#  f, fixup = like \"squash\", but discard this commit's log message\r\n#  x, exec = run command (the rest of the line) using shell\r\n\r\nshould work when you type 'git rebase -i' on the command line. ","3":"add ftplugin that cycles through interactive git rebase options.\r\n\r\n#  p, pick = use commit\r\n#  r, reword = use commit, but edit the commit message\r\n#  e, edit = use commit, but stop for amending\r\n#  s, squash = use commit, but meld into previous commit\r\n#  f, fixup = like \"squash\", but discard this commit's log message\r\n#  x, exec = run command (the rest of the line) using shell\r\n\r\nshould work when you type 'git rebase -i' on the command line. ","package":"swapit-master.zip","4":"swapit-master.zip","src_id":"21655","5":"21655","creation_date":"1395645877","6":"1395645877"},{"0":"2294","vim_version":"7.2","1":"7.2","script_version":"0.3.2","2":"0.3.2","version_comment":"Added step feature eg 4Ctrl-a can now jump from 'one' to 'five' \r\nRemoved some register clobbering\r\nThanks Ingo Karkat","3":"Added step feature eg 4Ctrl-a can now jump from 'one' to 'five' \r\nRemoved some register clobbering\r\nThanks Ingo Karkat","package":"swapit-master.zip","4":"swapit-master.zip","src_id":"20893","5":"20893","creation_date":"1381118516","6":"1381118516"},{"0":"2294","vim_version":"7.0","1":"7.0","script_version":"0.3.1","2":"0.3.1","version_comment":"fallback incrementors now work (eg 42<c-a> on an int). Thanks Ingo Karkat ","3":"fallback incrementors now work (eg 42<c-a> on an int). Thanks Ingo Karkat ","package":"mjbrownie-swapit-857ad49.zip","4":"mjbrownie-swapit-857ad49.zip","src_id":"17589","5":"17589","creation_date":"1331604821","6":"1331604821"},{"0":"2294","vim_version":"7.0","1":"7.0","script_version":"0.3","2":"0.3","version_comment":"Added Direct Css omnicomplete swapping (see link in description). Added help file","3":"Added Direct Css omnicomplete swapping (see link in description). Added help file","package":"swapit.0.3.tar.gz","4":"swapit.0.3.tar.gz","src_id":"11298","5":"11298","creation_date":"1251794723","6":"1251794723"},{"0":"2294","vim_version":"7.0","1":"7.0","script_version":"0.2","2":"0.2","version_comment":"Added html tag swap support, support for exclusive mode and some filetype examples","3":"Added html tag swap support, support for exclusive mode and some filetype examples","package":"swapit.0.2.tar.gz","4":"swapit.0.2.tar.gz","src_id":"11277","5":"11277","creation_date":"1251454912","6":"1251454912"},{"0":"2294","vim_version":"7.0","1":"7.0","script_version":"0.1.2","2":"0.1.2","version_comment":"Speed dating compatability enhancements. swap on phrases with visual mode, some bug fixes. Many thanks to Ingo Karkat","3":"Speed dating compatability enhancements. swap on phrases with visual mode, some bug fixes. Many thanks to Ingo Karkat","package":"swapit.vim","4":"swapit.vim","src_id":"8949","5":"8949","creation_date":"1216011210","6":"1216011210"}]},"2293":{"script_id":"2293","0":"2293","script_name":"Resolve","1":"Resolve","script_type":"utility","2":"utility","summary":"DNS resolver for domains or ips under the cursor","3":"DNS resolver for domains or ips under the cursor","description":"Scripts resolves hostname \/ ip under cursor, using `host` command. It can either echo the result (<Leader>re \/ <Leader>rs), or substitute relevant part of the buffer (<Leader>rE \/ <Leader>rS). Currently resolving A \/ SRV \/ PTR is supported, but adding other types should be trivial if anyone needs them.","4":"Scripts resolves hostname \/ ip under cursor, using `host` command. It can either echo the result (<Leader>re \/ <Leader>rs), or substitute relevant part of the buffer (<Leader>rE \/ <Leader>rS). Currently resolving A \/ SRV \/ PTR is supported, but adding other types should be trivial if anyone needs them.","install_details":"Put the script into .vim\/plugins.","5":"Put the script into .vim\/plugins.","first_name":"Stanis\u0142aw","6":"Stanisław","last_name":"Pitucha","7":"Pitucha","releases":[{"0":"2293","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"resolve.vim","4":"resolve.vim","src_id":"8931","5":"8931","creation_date":"1215803995","6":"1215803995"}]},"2292":{"script_id":"2292","0":"2292","script_name":"linglang","1":"linglang","script_type":"utility","2":"utility","summary":"Dynamically switch languages\/settings in multi-lingual documents","3":"Dynamically switch languages\/settings in multi-lingual documents","description":"The command |:Linglang| installs a buffer-local autocommand that checks \r\nthe current line's language. I.e. enabling linglang for the current \r\nbuffer won't affect other buffers. If the language of the line under the \r\ncursor changes, a user-defined action (e.g., set spelllang) will be \r\nexecuted.\r\n\r\n:Linglang[!] [LANGS ...]\r\n    Toggle linglang support for the current buffer.\r\n    With [!], suppress message.\r\n\r\nCurrently supported:\r\n- English\r\n- German (latin1, utf8)\r\n\r\nIn order to add a new language, you'll have to come up with some good \r\nwords\/regexps to identify it.\r\n\r\nLanguage data is stored in ...\/autoload\/linglang\/LANGUAGE.ENCODING\r\nThe fileformat is simple:\r\n\r\n- one word per line (these will be matched against word borders)\r\n- arbitrary regular expressions: \/REGEXP\/\r\n","4":"The command |:Linglang| installs a buffer-local autocommand that checks \r\nthe current line's language. I.e. enabling linglang for the current \r\nbuffer won't affect other buffers. If the language of the line under the \r\ncursor changes, a user-defined action (e.g., set spelllang) will be \r\nexecuted.\r\n\r\n:Linglang[!] [LANGS ...]\r\n    Toggle linglang support for the current buffer.\r\n    With [!], suppress message.\r\n\r\nCurrently supported:\r\n- English\r\n- German (latin1, utf8)\r\n\r\nIn order to add a new language, you'll have to come up with some good \r\nwords\/regexps to identify it.\r\n\r\nLanguage data is stored in ...\/autoload\/linglang\/LANGUAGE.ENCODING\r\nThe fileformat is simple:\r\n\r\n- one word per line (these will be matched against word borders)\r\n- arbitrary regular expressions: \/REGEXP\/\r\n","install_details":"Edit the vba file and type:\r\n\r\n    :so %\r\n\r\nSee :help vimball for details. If you have difficulties or use vim 7.0, \r\nplease make sure, you have the current version of vimball \r\n(vimscript #1502) installed or update your runtime.\r\n\r\nThis script requires hookcursormoved (vimscript #2037) to be installed.\r\n\r\n\r\nAlso available via git\r\nhttp:\/\/github.com\/tomtom\/linglang_vim","5":"Edit the vba file and type:\r\n\r\n    :so %\r\n\r\nSee :help vimball for details. If you have difficulties or use vim 7.0, \r\nplease make sure, you have the current version of vimball \r\n(vimscript #1502) installed or update your runtime.\r\n\r\nThis script requires hookcursormoved (vimscript #2037) to be installed.\r\n\r\n\r\nAlso available via git\r\nhttp:\/\/github.com\/tomtom\/linglang_vim","first_name":"Tom","6":"Tom","last_name":"Link","7":"Link","releases":[{"0":"2292","vim_version":"7.0","1":"7.0","script_version":"0.2","2":"0.2","version_comment":"- Language patterns are stored in ...\/autoload\/linglang\/LANGUAGE.ENCODING\r\n- Respect encoding\r\n- Removed variables: g:linglang_words, g:linglang_patterns, g:linglang_filetypes","3":"- Language patterns are stored in ...\/autoload\/linglang\/LANGUAGE.ENCODING\r\n- Respect encoding\r\n- Removed variables: g:linglang_words, g:linglang_patterns, g:linglang_filetypes","package":"linglang.vba.gz","4":"linglang.vba.gz","src_id":"8942","5":"8942","creation_date":"1215929495","6":"1215929495"},{"0":"2292","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"linglang.vba.gz","4":"linglang.vba.gz","src_id":"8927","5":"8927","creation_date":"1215759845","6":"1215759845"}]},"2291":{"script_id":"2291","0":"2291","script_name":"skeleton","1":"skeleton","script_type":"utility","2":"utility","summary":"Skeleton for newly created buffers","3":"Skeleton for newly created buffers","description":"*skeleton* is a Vim plugin to set up a skeleton for a newly created buffer.\r\nOnce you put skeleton files into specific directories, appropriate ones will\r\nbe automatically expanded for newly created buffers.\r\n\r\n- Skeleton files must be put in a directory named \"xtr\/skeleton\/\" which is\r\n  under any directory listed in 'runtimepath'.\r\n\r\n  For example: ~\/.vim\/xtr\/skeleton\/\r\n\r\n- The name of a skeleton file should be \"{filetype}\" or \"{filetype}-{suffix}\",\r\n  where {filetype} is the 'filetype' for a newly created buffer and {suffix}\r\n  is an arbitrary string.\r\n\r\n  The former \"{filetype}\" is used as the default skeleton file for that\r\n  'filetype'.  The latter \"{filetype}-{suffix}\" is used to override the\r\n  default one for some cases which are speicifed by user.\r\n\r\n  For example: ~\/.vim\/xtr\/skeleton\/vim ~\/.vim\/xtr\/skeleton\/vim-plugin\r\n\r\n- Whenever user starts to edit a file that doesn't exists:\r\n\r\n  1) Skeleton publish a |User:plugin-skeleton-detect| event.  This event can\r\n     be used to |:SkeletonLoad| a special skeleton file other than the default\r\n     one.\r\n\r\n  2) If |:SkeletonLoad| is not done for the previous step, Skeleton executes\r\n     the following command:\r\n\r\n\texecute 'SkeletonLoad' &l:filetype\r\n\r\n     This means a skeleton file named \"{filetype}\" in a directory\r\n     \"xtr\/skeleton\/\" which is under any directory listed in 'runtimepath' is\r\n     loaded as a skeleton file.\r\n\r\n     If there is no such skeleton file, nothing will be happened.\r\n\r\n\r\nRequirements:\r\n- Vim 7.1 or later\r\n\r\nLatest version:\r\nhttp:\/\/github.com\/kana\/vim-skeleton\r\n\r\nDocument in HTML format:\r\nhttp:\/\/kana.github.com\/config\/vim\/skeleton.html","4":"*skeleton* is a Vim plugin to set up a skeleton for a newly created buffer.\r\nOnce you put skeleton files into specific directories, appropriate ones will\r\nbe automatically expanded for newly created buffers.\r\n\r\n- Skeleton files must be put in a directory named \"xtr\/skeleton\/\" which is\r\n  under any directory listed in 'runtimepath'.\r\n\r\n  For example: ~\/.vim\/xtr\/skeleton\/\r\n\r\n- The name of a skeleton file should be \"{filetype}\" or \"{filetype}-{suffix}\",\r\n  where {filetype} is the 'filetype' for a newly created buffer and {suffix}\r\n  is an arbitrary string.\r\n\r\n  The former \"{filetype}\" is used as the default skeleton file for that\r\n  'filetype'.  The latter \"{filetype}-{suffix}\" is used to override the\r\n  default one for some cases which are speicifed by user.\r\n\r\n  For example: ~\/.vim\/xtr\/skeleton\/vim ~\/.vim\/xtr\/skeleton\/vim-plugin\r\n\r\n- Whenever user starts to edit a file that doesn't exists:\r\n\r\n  1) Skeleton publish a |User:plugin-skeleton-detect| event.  This event can\r\n     be used to |:SkeletonLoad| a special skeleton file other than the default\r\n     one.\r\n\r\n  2) If |:SkeletonLoad| is not done for the previous step, Skeleton executes\r\n     the following command:\r\n\r\n\texecute 'SkeletonLoad' &l:filetype\r\n\r\n     This means a skeleton file named \"{filetype}\" in a directory\r\n     \"xtr\/skeleton\/\" which is under any directory listed in 'runtimepath' is\r\n     loaded as a skeleton file.\r\n\r\n     If there is no such skeleton file, nothing will be happened.\r\n\r\n\r\nRequirements:\r\n- Vim 7.1 or later\r\n\r\nLatest version:\r\nhttp:\/\/github.com\/kana\/vim-skeleton\r\n\r\nDocument in HTML format:\r\nhttp:\/\/kana.github.com\/config\/vim\/skeleton.html","install_details":"...","5":"...","first_name":"Kana","6":"Kana","last_name":"Natsuno","7":"Natsuno","releases":[{"0":"2291","vim_version":"7.0","1":"7.0","script_version":"0.0.2","2":"0.0.2","version_comment":"- Refine the document.\n- |:SkeletonLoad|:\n  - Support completion.\n  - Allow to override existing content of a buffer with \"!\".","3":"- Refine the document.\n- |:SkeletonLoad|:\n  - Support completion.\n  - Allow to override existing content of a buffer with \"!\".","package":"vim-skeleton-0.0.2.zip","4":"vim-skeleton-0.0.2.zip","src_id":"10224","5":"10224","creation_date":"1237223547","6":"1237223547"},{"0":"2291","vim_version":"7.0","1":"7.0","script_version":"0.0.1","2":"0.0.1","version_comment":"Fix minor bugs to suppress extra messages which cause hit-enter prompt.","3":"Fix minor bugs to suppress extra messages which cause hit-enter prompt.","package":"vim-skeleton-0.0.1.zip","4":"vim-skeleton-0.0.1.zip","src_id":"8937","5":"8937","creation_date":"1215851096","6":"1215851096"},{"0":"2291","vim_version":"7.0","1":"7.0","script_version":"0.0.0","2":"0.0.0","version_comment":"Initial upload","3":"Initial upload","package":"vim-skeleton-0.0.0.zip","4":"vim-skeleton-0.0.0.zip","src_id":"8924","5":"8924","creation_date":"1215748076","6":"1215748076"}]},"2290":{"script_id":"2290","0":"2290","script_name":"smartchr","1":"smartchr","script_type":"utility","2":"utility","summary":"Insert several candidates with a single key","3":"Insert several candidates with a single key","description":"*smartchr* is a Vim plugin to support input several candidates with a single\r\nkey, like ess-smart-underscore in Emacs Speaks Statistics -- when user types\r\n\"_\" key, it inserts \" <- \" for the first time or it replaces \" <- \" by \"_\" for\r\nthe second time.  This plugin provides functions to support to define such\r\nkey bindings easily.  For example:\r\n\r\n\tinoremap <expr> _  smartchr#one_of(' <- ', '_')\r\n\r\n\r\n\r\nRequirements:\r\n- Vim 7.1 or later\r\n\r\nLatest version:\r\nhttp:\/\/github.com\/kana\/vim-smartchr\r\n\r\nDocument in HTML format:\r\nhttp:\/\/kana.github.com\/config\/vim\/smartchr.html","4":"*smartchr* is a Vim plugin to support input several candidates with a single\r\nkey, like ess-smart-underscore in Emacs Speaks Statistics -- when user types\r\n\"_\" key, it inserts \" <- \" for the first time or it replaces \" <- \" by \"_\" for\r\nthe second time.  This plugin provides functions to support to define such\r\nkey bindings easily.  For example:\r\n\r\n\tinoremap <expr> _  smartchr#one_of(' <- ', '_')\r\n\r\n\r\n\r\nRequirements:\r\n- Vim 7.1 or later\r\n\r\nLatest version:\r\nhttp:\/\/github.com\/kana\/vim-smartchr\r\n\r\nDocument in HTML format:\r\nhttp:\/\/kana.github.com\/config\/vim\/smartchr.html","install_details":"...","5":"...","first_name":"Kana","6":"Kana","last_name":"Natsuno","7":"Natsuno","releases":[{"0":"2290","vim_version":"7.0","1":"7.0","script_version":"0.1.1","2":"0.1.1","version_comment":"- Add |smartchr-context| to enable\/disable |smartchr-functions| in specified context.\n\n  Example configuration:\n  cnoremap <expr> (  smartchr#loop('\\(', '(', {'ctype': '\/?'})","3":"- Add |smartchr-context| to enable\/disable |smartchr-functions| in specified context.\n\n  Example configuration:\n  cnoremap <expr> (  smartchr#loop('\\(', '(', {'ctype': '\/?'})","package":"vim-smartchr-0.1.1.zip","4":"vim-smartchr-0.1.1.zip","src_id":"12455","5":"12455","creation_date":"1266748446","6":"1266748446"},{"0":"2290","vim_version":"7.0","1":"7.0","script_version":"0.1.0","2":"0.1.0","version_comment":"- Support Command-line mode.  (Thanks to Tatsuhiro Ujihisa for reporting this)\n\n  Example configuration:\n  cnoremap <expr> <Bslash>  smartchr#loop('~\/', '<Bslash>')","3":"- Support Command-line mode.  (Thanks to Tatsuhiro Ujihisa for reporting this)\n\n  Example configuration:\n  cnoremap <expr> <Bslash>  smartchr#loop('~\/', '<Bslash>')","package":"vim-smartchr-0.1.0.zip","4":"vim-smartchr-0.1.0.zip","src_id":"12393","5":"12393","creation_date":"1266421881","6":"1266421881"},{"0":"2290","vim_version":"7.0","1":"7.0","script_version":"0.0.1","2":"0.0.1","version_comment":"- Add |smartchr#loop()|.\n","3":"- Add |smartchr#loop()|.\n","package":"vim-smartchr-0.0.1.zip","4":"vim-smartchr-0.0.1.zip","src_id":"9182","5":"9182","creation_date":"1219872903","6":"1219872903"},{"0":"2290","vim_version":"7.0","1":"7.0","script_version":"0.0.0","2":"0.0.0","version_comment":"Initial upload","3":"Initial upload","package":"vim-smartchr-0.0.0.zip","4":"vim-smartchr-0.0.0.zip","src_id":"8923","5":"8923","creation_date":"1215747691","6":"1215747691"}]},"2289":{"script_id":"2289","0":"2289","script_name":"loremipsum","1":"loremipsum","script_type":"utility","2":"utility","summary":"A dummy text generator","3":"A dummy text generator","description":"Insert a dummy text of a certain length. Actually, the text isn't \r\ngenerated but selected from some text. By default, the following text is \r\nused, which is included in the archive:\r\nhttp:\/\/www.lorem-ipsum-dolor-sit-amet.com\/lorem-ipsum-dolor-sit-amet.html\r\n\r\nNOTE: The webpage didn't contain any copyright message but there is a \r\nstatement that one is allowed to paste the text into \"your document\". \r\nI thus assume it's ok to include it in the archive. If not, please let me know.\r\n\r\nCommand:\r\n:Loremipsum[!] [WORDCOUNT] [PARAGRAPH_TEMPLATE] [PREFIX POSTFIX]\r\n    Insert some random text.\r\n\r\n:Loreplace [REPLACEMENT] [PREFIX] [POSTFIX]\r\n    Replace the random text with something else or simply remove it.\r\n","4":"Insert a dummy text of a certain length. Actually, the text isn't \r\ngenerated but selected from some text. By default, the following text is \r\nused, which is included in the archive:\r\nhttp:\/\/www.lorem-ipsum-dolor-sit-amet.com\/lorem-ipsum-dolor-sit-amet.html\r\n\r\nNOTE: The webpage didn't contain any copyright message but there is a \r\nstatement that one is allowed to paste the text into \"your document\". \r\nI thus assume it's ok to include it in the archive. If not, please let me know.\r\n\r\nCommand:\r\n:Loremipsum[!] [WORDCOUNT] [PARAGRAPH_TEMPLATE] [PREFIX POSTFIX]\r\n    Insert some random text.\r\n\r\n:Loreplace [REPLACEMENT] [PREFIX] [POSTFIX]\r\n    Replace the random text with something else or simply remove it.\r\n","install_details":"Edit the vba file and type:\r\n\r\n    :so %\r\n\r\nSee :help vimball for details. If you have difficulties or use vim 7.0, \r\nplease make sure, you have the current version of vimball \r\n(vimscript #1502) installed or update your runtime.\r\n\r\n\r\nAlso available via git\r\nhttp:\/\/github.com\/tomtom\/vimtlib\/tree\/master\r\n","5":"Edit the vba file and type:\r\n\r\n    :so %\r\n\r\nSee :help vimball for details. If you have difficulties or use vim 7.0, \r\nplease make sure, you have the current version of vimball \r\n(vimscript #1502) installed or update your runtime.\r\n\r\n\r\nAlso available via git\r\nhttp:\/\/github.com\/tomtom\/vimtlib\/tree\/master\r\n","first_name":"Tom","6":"Tom","last_name":"Link","7":"Link","releases":[{"0":"2289","vim_version":"7.0","1":"7.0","script_version":"0.2","2":"0.2","version_comment":"- Loremipsum!: With !, insert inline (single paragraph)\r\n- Loreplace: Replace loremipsum text with something else (provided a marker was defined for the current filetype)\r\n- If the template argument is *, don't apply the default paragraph template.\r\n- g:loremipsum_file, b:loremipsum_file","3":"- Loremipsum!: With !, insert inline (single paragraph)\r\n- Loreplace: Replace loremipsum text with something else (provided a marker was defined for the current filetype)\r\n- If the template argument is *, don't apply the default paragraph template.\r\n- g:loremipsum_file, b:loremipsum_file","package":"loremipsum.vba.gz","4":"loremipsum.vba.gz","src_id":"8922","5":"8922","creation_date":"1215732850","6":"1215732850"},{"0":"2289","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"loremipsum.vba.gz","4":"loremipsum.vba.gz","src_id":"8918","5":"8918","creation_date":"1215680589","6":"1215680589"}]},"2288":{"script_id":"2288","0":"2288","script_name":"ctags.exe","1":"ctags.exe","script_type":"utility","2":"utility","summary":"Windows version of ctags for 4GL\/4Js programs","3":"Windows version of ctags for 4GL\/4Js programs","description":"I compiled original Windows ctags source(http:\/\/ctags.sourceforge.net\/) with a 4GL language extension to generate tags for functions(include report function), cursor IDs, prepared statement IDs, and global\/module level variables. It works in XP and Vista according to my test. \r\n\r\nIt's even better when you use it with taglist.vim. It generate tags on the fly when you open 4gl programs in gvim\/vim. For this add the following lines in taglist.vim. (Scroll down the plugin to a section where tag types are defined for different languages:)\r\n------------------------------------------------------------------------------------------------------------------\r\n\" fgl language\r\nlet s:tlist_def_fgl_settings = 'fgl;f:function;c:cursor;s:prepared;v:variable'\r\n------------------------------------------------------------------------------------------------------------------\r\n\r\nIf you want to compile yourself, here is how I compiled:\r\n1. Download and extract, if necessary, BCC55(free Boland compiler) and ctags source for Windows from the web and 4GL extentionfrom \r\n2. Create both bcc32.cfg and ilink.cfg in bin directory of BCC55 using Notepad. The contents of two files are the same as follows(of course, change the path if you have installed it in a different directory). Each file contains two lines.\r\n   -I\"C:\\Borland\\BCC55\\Include\" \r\n   -L\"C:\\Borland\\BCC55\\Lib;C:\\Borland\\BCC55\\Lib\\PSDK\"\r\n3. You will probably have to add a bin path to your system \r\n4. Download 4GL extenion from http:\/\/www.vim.org\/scripts\/script.php?script_id=587,and extract files(fgl.c ...) to your ctags source directory\r\n5. In ctags source directory, type \"make -f mk_bc5.mak\" to build ctags.exe\r\n","4":"I compiled original Windows ctags source(http:\/\/ctags.sourceforge.net\/) with a 4GL language extension to generate tags for functions(include report function), cursor IDs, prepared statement IDs, and global\/module level variables. It works in XP and Vista according to my test. \r\n\r\nIt's even better when you use it with taglist.vim. It generate tags on the fly when you open 4gl programs in gvim\/vim. For this add the following lines in taglist.vim. (Scroll down the plugin to a section where tag types are defined for different languages:)\r\n------------------------------------------------------------------------------------------------------------------\r\n\" fgl language\r\nlet s:tlist_def_fgl_settings = 'fgl;f:function;c:cursor;s:prepared;v:variable'\r\n------------------------------------------------------------------------------------------------------------------\r\n\r\nIf you want to compile yourself, here is how I compiled:\r\n1. Download and extract, if necessary, BCC55(free Boland compiler) and ctags source for Windows from the web and 4GL extentionfrom \r\n2. Create both bcc32.cfg and ilink.cfg in bin directory of BCC55 using Notepad. The contents of two files are the same as follows(of course, change the path if you have installed it in a different directory). Each file contains two lines.\r\n   -I\"C:\\Borland\\BCC55\\Include\" \r\n   -L\"C:\\Borland\\BCC55\\Lib;C:\\Borland\\BCC55\\Lib\\PSDK\"\r\n3. You will probably have to add a bin path to your system \r\n4. Download 4GL extenion from http:\/\/www.vim.org\/scripts\/script.php?script_id=587,and extract files(fgl.c ...) to your ctags source directory\r\n5. In ctags source directory, type \"make -f mk_bc5.mak\" to build ctags.exe\r\n","install_details":"Put ctags.exe in a directory, whose execution path is recognized in Windows. \r\nFor more information, type 'ctags.exe --help'\r\n\r\nIf you are editing files in UNIX thru samba, map a drive and set tag variable in _vimrc or .vimrc in windows","5":"Put ctags.exe in a directory, whose execution path is recognized in Windows. \r\nFor more information, type 'ctags.exe --help'\r\n\r\nIf you are editing files in UNIX thru samba, map a drive and set tag variable in _vimrc or .vimrc in windows","first_name":"Tim","6":"Tim","last_name":"Kim","7":"Kim","releases":[{"0":"2288","vim_version":"6.0","1":"6.0","script_version":"1.5","2":"1.5","version_comment":"Recognize REPORT function name as a tag","3":"Recognize REPORT function name as a tag","package":"ctags.exe","4":"ctags.exe","src_id":"10387","5":"10387","creation_date":"1239488168","6":"1239488168"},{"0":"2288","vim_version":"6.0","1":"6.0","script_version":"1.4","2":"1.4","version_comment":"A bug fix related to curly bracket for comment","3":"A bug fix related to curly bracket for comment","package":"ctags.zip","4":"ctags.zip","src_id":"9617","5":"9617","creation_date":"1228520737","6":"1228520737"},{"0":"2288","vim_version":"6.0","1":"6.0","script_version":"1.3","2":"1.3","version_comment":"a bug fix when comment finishes with a curly bracket","3":"a bug fix when comment finishes with a curly bracket","package":"fgl.zip","4":"fgl.zip","src_id":"8975","5":"8975","creation_date":"1216481109","6":"1216481109"},{"0":"2288","vim_version":"6.0","1":"6.0","script_version":"1.2","2":"1.2","version_comment":"Now it picks up any global\/module vairables to create tag. Reaonably works well.\r\nThe Zip file includs ctags executable, and fgl extention source to ctags.\r\n\r\nI used BC5 compiler to compile the ctags source with this fgl extension both in XP and Vista.","3":"Now it picks up any global\/module vairables to create tag. Reaonably works well.\r\nThe Zip file includs ctags executable, and fgl extention source to ctags.\r\n\r\nI used BC5 compiler to compile the ctags source with this fgl extension both in XP and Vista.","package":"fgl.zip","4":"fgl.zip","src_id":"8941","5":"8941","creation_date":"1215927981","6":"1215927981"},{"0":"2288","vim_version":"6.0","1":"6.0","script_version":"1.1","2":"1.1","version_comment":"fixed a bug","3":"fixed a bug","package":"ctags.exe","4":"ctags.exe","src_id":"8930","5":"8930","creation_date":"1215801804","6":"1215801804"},{"0":"2288","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"ctags.exe","4":"ctags.exe","src_id":"8916","5":"8916","creation_date":"1215623399","6":"1215623399"}]},"2287":{"script_id":"2287","0":"2287","script_name":"fgl.vim","1":"fgl.vim","script_type":"syntax","2":"syntax","summary":"Syntax folding for IBM Informix 4GL or 4J programs","3":"Syntax folding for IBM Informix 4GL or 4J programs","description":"fgl.vim is Informix 4GL syntax file. \r\n\r\n","4":"fgl.vim is Informix 4GL syntax file. \r\n\r\n","install_details":"Drop this script in \\'syntax\\' directory under your vim installation directory.\r\n\r\nPersonally I have the following settings in .vimrc as well\r\n- To set an initial folding level (how much to fold upon opening a 4GL program)\r\n- To map SPACEBAR to toggle between folding and unfolding\r\n- To change a defult vim text on folded line\r\n\r\nFor this, copy the following section to your .vimrc. Folding\/Unfolding is just as easy as pressing SPACEBAR\r\n - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - \r\nset foldlevel=1  \" change the number to set initial folding level\r\nset foldtext=MyFoldText()\r\nnoremap <space> :call ToggleFold() <cr>\r\n\r\nfunction MyFoldText()\r\n   let line = getline(v:foldstart)\r\n   let sub = substitute(line, '\/\\*\\|\\*\/\\|{{{\\d\\=', '', 'g')\r\n   return strpart(v:folddashes, 2, strlen(v:folddashes) - foldlevel(line(\".\"))*3) . sub . \r\n             \\  \" ------ [\" .  (v:foldend - v:foldstart) . \" lines] \"\r\nendfunction\r\n\r\nfun! ToggleFold()\r\n  if foldlevel('.') == 0\r\n      normal! l\r\n  else\r\n     if foldclosed('.') < 0\r\n        .  foldclose\r\n     else\r\n        . foldopen\r\n     endif\r\n  endif\r\n \"  Clear status line\r\n  echo\r\nendfun\r\n- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - \r\n\r\n","5":"Drop this script in \\'syntax\\' directory under your vim installation directory.\r\n\r\nPersonally I have the following settings in .vimrc as well\r\n- To set an initial folding level (how much to fold upon opening a 4GL program)\r\n- To map SPACEBAR to toggle between folding and unfolding\r\n- To change a defult vim text on folded line\r\n\r\nFor this, copy the following section to your .vimrc. Folding\/Unfolding is just as easy as pressing SPACEBAR\r\n - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - \r\nset foldlevel=1  \" change the number to set initial folding level\r\nset foldtext=MyFoldText()\r\nnoremap <space> :call ToggleFold() <cr>\r\n\r\nfunction MyFoldText()\r\n   let line = getline(v:foldstart)\r\n   let sub = substitute(line, '\/\\*\\|\\*\/\\|{{{\\d\\=', '', 'g')\r\n   return strpart(v:folddashes, 2, strlen(v:folddashes) - foldlevel(line(\".\"))*3) . sub . \r\n             \\  \" ------ [\" .  (v:foldend - v:foldstart) . \" lines] \"\r\nendfunction\r\n\r\nfun! ToggleFold()\r\n  if foldlevel('.') == 0\r\n      normal! l\r\n  else\r\n     if foldclosed('.') < 0\r\n        .  foldclose\r\n     else\r\n        . foldopen\r\n     endif\r\n  endif\r\n \"  Clear status line\r\n  echo\r\nendfun\r\n- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - \r\n\r\n","first_name":"Tim","6":"Tim","last_name":"Kim","7":"Kim","releases":[{"0":"2287","vim_version":"6.0","1":"6.0","script_version":"1.4","2":"1.4","version_comment":"A fix for a problm with INPUT statement","3":"A fix for a problm with INPUT statement","package":"fgl.vim","4":"fgl.vim","src_id":"9620","5":"9620","creation_date":"1228535821","6":"1228535821"},{"0":"2287","vim_version":"6.0","1":"6.0","script_version":"1.3","2":"1.3","version_comment":"Fix error with DISPLAY statement","3":"Fix error with DISPLAY statement","package":"fgl.vim","4":"fgl.vim","src_id":"9576","5":"9576","creation_date":"1227744794","6":"1227744794"},{"0":"2287","vim_version":"6.0","1":"6.0","script_version":"1.2","2":"1.2","version_comment":"Fix folding error with INPUT statement\r\nAdded ELSE folding for IF statement","3":"Fix folding error with INPUT statement\r\nAdded ELSE folding for IF statement","package":"fgl.vim","4":"fgl.vim","src_id":"9551","5":"9551","creation_date":"1227480358","6":"1227480358"},{"0":"2287","vim_version":"6.0","1":"6.0","script_version":"1.1","2":"1.1","version_comment":"Fix a bug.\r\nCommented out then\/else block for if statement so that it creates a fold for the whole if block.","3":"Fix a bug.\r\nCommented out then\/else block for if statement so that it creates a fold for the whole if block.","package":"fgl.vim","4":"fgl.vim","src_id":"8948","5":"8948","creation_date":"1215976573","6":"1215976573"},{"0":"2287","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"fgl.vim","4":"fgl.vim","src_id":"8915","5":"8915","creation_date":"1215623006","6":"1215623006"}]},"2286":{"script_id":"2286","0":"2286","script_name":"Specky!","1":"Specky!","script_type":"utility","2":"utility","summary":"Functions to help make behavioral testing easy with ruby and rspec.","3":"Functions to help make behavioral testing easy with ruby and rspec.","description":"Specky is a small collection of Vim functions to help make behavioral testing streamlined and easy when working with ruby and rspec.\r\n\r\nHere are some of the things you can do with Specky, with a single key stroke:\r\n\r\n    * Switch back and forth from code to testing spec\r\n    * Run the spec, with results going to a new, syntax highlighted buffer\r\n    * Jump quickly to spec failures and failure detail\r\n    * View rdoc of the word under the cursor\r\n    * Dynamically switch string types for the word under the cursor (double quoted, quoted, symbol)\r\n    * Create comment banners quickly \r\n\r\nSpecky also includes a couple of conveniences to make your everyday programming tasks smooooth and pleasurable, such as:\r\n\r\n    * File detection for spec files (that are named in the traditional *_spec.rb fashion.)\r\n    * Syntax highlighting for rspec and rdoc\r\n    * \"Snippets\" for rspec, using the Snipmate (vimscript #2540) plugin. \r\n\r\nYou can see a screencast of Specky here: http:\/\/projects.martini.nu\/vim-stuff\/wiki\/SpeckyCast\r\n\r\nThis is my first official VIM plugin.  Advice\/props\/criticisms all equally appreciated, but please let me know if you're using it!  (mahlon@martini.nu)   \r\n","4":"Specky is a small collection of Vim functions to help make behavioral testing streamlined and easy when working with ruby and rspec.\r\n\r\nHere are some of the things you can do with Specky, with a single key stroke:\r\n\r\n    * Switch back and forth from code to testing spec\r\n    * Run the spec, with results going to a new, syntax highlighted buffer\r\n    * Jump quickly to spec failures and failure detail\r\n    * View rdoc of the word under the cursor\r\n    * Dynamically switch string types for the word under the cursor (double quoted, quoted, symbol)\r\n    * Create comment banners quickly \r\n\r\nSpecky also includes a couple of conveniences to make your everyday programming tasks smooooth and pleasurable, such as:\r\n\r\n    * File detection for spec files (that are named in the traditional *_spec.rb fashion.)\r\n    * Syntax highlighting for rspec and rdoc\r\n    * \"Snippets\" for rspec, using the Snipmate (vimscript #2540) plugin. \r\n\r\nYou can see a screencast of Specky here: http:\/\/projects.martini.nu\/vim-stuff\/wiki\/SpeckyCast\r\n\r\nThis is my first official VIM plugin.  Advice\/props\/criticisms all equally appreciated, but please let me know if you're using it!  (mahlon@martini.nu)   \r\n","install_details":"Install the VimBall plugin (vimscript #1502) if you don't already have it.\r\n\r\nThen open specky.vba from within vim.\r\n\r\n    :so %\r\n\r\n\r\nRestart vim, and read the the docs (:help specky) for what to do next!\r\n\r\nEnjoy.\r\n","5":"Install the VimBall plugin (vimscript #1502) if you don't already have it.\r\n\r\nThen open specky.vba from within vim.\r\n\r\n    :so %\r\n\r\n\r\nRestart vim, and read the the docs (:help specky) for what to do next!\r\n\r\nEnjoy.\r\n","first_name":"Mahlon","6":"Mahlon","last_name":"Smith","7":"Smith","releases":[{"0":"2286","vim_version":"7.0","1":"7.0","script_version":"1.6","2":"1.6","version_comment":"Minor updates to get Specky working again with rspec 2.8.","3":"Minor updates to get Specky working again with rspec 2.8.","package":"specky.vba.gz","4":"specky.vba.gz","src_id":"17425","5":"17425","creation_date":"1328919015","6":"1328919015"},{"0":"2286","vim_version":"7.0","1":"7.0","script_version":"1.5","2":"1.5","version_comment":"Emit file\/line in failure detail. (You can use 'gF' to jump straight to it!)  Show context lines for failure detail.  Put the spec summary info at the top of the screen.  Small documentation fixes.  Problems?  Make sure you're running rspec 2.3.x.  Merry X-Mas!","3":"Emit file\/line in failure detail. (You can use 'gF' to jump straight to it!)  Show context lines for failure detail.  Put the spec summary info at the top of the screen.  Small documentation fixes.  Problems?  Make sure you're running rspec 2.3.x.  Merry X-Mas!","package":"specky.vba.gz","4":"specky.vba.gz","src_id":"14615","5":"14615","creation_date":"1293249872","6":"1293249872"},{"0":"2286","vim_version":"7.0","1":"7.0","script_version":"1.4","2":"1.4","version_comment":"This is the Specky \"rspec 2.x\" release, supporting rspec 2 via a new custom rspec formatter.  This is now the default, though rspec 1 is also still supported.  Syntax highlighting and snippets brought up to date with 2.x.  Install instructions have changed, please read the docs for setup information! ","3":"This is the Specky \"rspec 2.x\" release, supporting rspec 2 via a new custom rspec formatter.  This is now the default, though rspec 1 is also still supported.  Syntax highlighting and snippets brought up to date with 2.x.  Install instructions have changed, please read the docs for setup information! ","package":"specky.vba.gz","4":"specky.vba.gz","src_id":"14575","5":"14575","creation_date":"1292747341","6":"1292747341"},{"0":"2286","vim_version":"7.0","1":"7.0","script_version":"1.3","2":"1.3","version_comment":"Minor bump, add rspec 1.26 'expect to' and 'expect to_not' syntax highlights and snippets.","3":"Minor bump, add rspec 1.26 'expect to' and 'expect to_not' syntax highlights and snippets.","package":"specky.vba.gz","4":"specky.vba.gz","src_id":"10852","5":"10852","creation_date":"1245169381","6":"1245169381"},{"0":"2286","vim_version":"7.0","1":"7.0","script_version":"1.2","2":"1.2","version_comment":"Add support for opening spec output and rdoc in a new tab\/horz split\/vert split.  Support syntax highlighting for -implemented- pending specs.  (spec code wrapped in a 'pending' block, vs an 'it' declaration that has no block.)  Allow rdoc lookup from rspec mode.  Banner creation now respects current indent level.","3":"Add support for opening spec output and rdoc in a new tab\/horz split\/vert split.  Support syntax highlighting for -implemented- pending specs.  (spec code wrapped in a 'pending' block, vs an 'it' declaration that has no block.)  Allow rdoc lookup from rspec mode.  Banner creation now respects current indent level.","package":"specky.vba.gz","4":"specky.vba.gz","src_id":"10426","5":"10426","creation_date":"1240203847","6":"1240203847"},{"0":"2286","vim_version":"7.0","1":"7.0","script_version":"1.1","2":"1.1","version_comment":"Provide matchit compatibility functions (piggybacking on the base ruby type) for rspec files.  Many thanks to Douglas McInnes (lloyd at lloydslounge org) for the patch!","3":"Provide matchit compatibility functions (piggybacking on the base ruby type) for rspec files.  Many thanks to Douglas McInnes (lloyd at lloydslounge org) for the patch!","package":"specky.vba.gz","4":"specky.vba.gz","src_id":"10369","5":"10369","creation_date":"1239260448","6":"1239260448"},{"0":"2286","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Fixed rdoc display bug introduced in the last version.  Added new screencast, found here: http:\/\/projects.martini.nu\/vim-stuff\/wiki\/SpeckyCast","3":"Fixed rdoc display bug introduced in the last version.  Added new screencast, found here: http:\/\/projects.martini.nu\/vim-stuff\/wiki\/SpeckyCast","package":"specky.vba.gz","4":"specky.vba.gz","src_id":"10349","5":"10349","creation_date":"1238906413","6":"1238906413"},{"0":"2286","vim_version":"7.0","1":"7.0","script_version":"0.9","2":"0.9","version_comment":"Added file detection and syntax highlighting for spec files, and now distribute an rspec snippet (vimscript #2540) file as part of the package. ","3":"Added file detection and syntax highlighting for spec files, and now distribute an rspec snippet (vimscript #2540) file as part of the package. ","package":"specky.vba.gz","4":"specky.vba.gz","src_id":"10339","5":"10339","creation_date":"1238683351","6":"1238683351"},{"0":"2286","vim_version":"7.0","1":"7.0","script_version":"0.8","2":"0.8","version_comment":"Fixed quote switching so it plays nice with the excellent 'Surround' plugin.  Added comment banner creation.","3":"Fixed quote switching so it plays nice with the excellent 'Surround' plugin.  Added comment banner creation.","package":"specky.vba.gz","4":"specky.vba.gz","src_id":"10262","5":"10262","creation_date":"1237683746","6":"1237683746"},{"0":"2286","vim_version":"7.0","1":"7.0","script_version":"0.7","2":"0.7","version_comment":"Removed the alignment routine completely.  There are far more robust implementations of this sort of thing already. (vimscript #294)","3":"Removed the alignment routine completely.  There are far more robust implementations of this sort of thing already. (vimscript #294)","package":"specky.vba.gz","4":"specky.vba.gz","src_id":"9127","5":"9127","creation_date":"1218782480","6":"1218782480"},{"0":"2286","vim_version":"6.0","1":"6.0","script_version":"0.6","2":"0.6","version_comment":"Added rudamentary syntax highlighting for rdoc output.","3":"Added rudamentary syntax highlighting for rdoc output.","package":"specky.vba","4":"specky.vba","src_id":"9109","5":"9109","creation_date":"1218396540","6":"1218396540"},{"0":"2286","vim_version":"7.0","1":"7.0","script_version":"0.6","2":"0.6","version_comment":"Switched to VimBall packaging.  Added real documentation.  Better whitespace cleanup for 'Align'.  Saner config args for overriding defaults.","3":"Switched to VimBall packaging.  Added real documentation.  Better whitespace cleanup for 'Align'.  Saner config args for overriding defaults.","package":"specky.vba","4":"specky.vba","src_id":"9083","5":"9083","creation_date":"1218028562","6":"1218028562"},{"0":"2286","vim_version":"7.0","1":"7.0","script_version":"0.5","2":"0.5","version_comment":"Add context line padding around assertion failure detail.  Auto switch to spec if run while in code.  Script cleanup. Fixed stupid typo (my vimscript needs rspec!).","3":"Add context line padding around assertion failure detail.  Auto switch to spec if run while in code.  Script cleanup. Fixed stupid typo (my vimscript needs rspec!).","package":"specky.zip","4":"specky.zip","src_id":"9061","5":"9061","creation_date":"1217526463","6":"1217526463"},{"0":"2286","vim_version":"7.0","1":"7.0","script_version":"0.4","2":"0.4","version_comment":"Fix bug with rdoc \"multiple match\" cWORD.","3":"Fix bug with rdoc \"multiple match\" cWORD.","package":"specky.zip","4":"specky.zip","src_id":"9042","5":"9042","creation_date":"1217348134","6":"1217348134"},{"0":"2286","vim_version":"7.0","1":"7.0","script_version":"0.3","2":"0.3","version_comment":"Added assigment and hash key\/value line alignment.","3":"Added assigment and hash key\/value line alignment.","package":"specky.zip","4":"specky.zip","src_id":"9041","5":"9041","creation_date":"1217345895","6":"1217345895"},{"0":"2286","vim_version":"7.0","1":"7.0","script_version":"0.2","2":"0.2","version_comment":"Added syntax highlighting for spec output, and spec assertion failure 'jumping'.  Screencast available for your viewing pleasure.","3":"Added syntax highlighting for spec output, and spec assertion failure 'jumping'.  Screencast available for your viewing pleasure.","package":"specky.zip","4":"specky.zip","src_id":"8911","5":"8911","creation_date":"1215565809","6":"1215565809"},{"0":"2286","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"specky.vim","4":"specky.vim","src_id":"8892","5":"8892","creation_date":"1215380695","6":"1215380695"}]},"2285":{"script_id":"2285","0":"2285","script_name":"vmv","1":"vmv","script_type":"utility","2":"utility","summary":"group rename files from the command prompt with vim","3":"group rename files from the command prompt with vim","description":"vmv - the vim version of the mv command. This script is in intent exactly the same as renamer.vim, rename a mass of files all at once using the full power of vim's editing capabilities.  Usage is much simpler to remember if you haven't used it in months, and the script itself is much shorter. Great for anybody who just ripped a CD to \"track 01.mp3\" through \"track 12.mp3\", or just inherited a collection of mp3's without proper case and with underscores instead of spaces. \r\n\r\nAlso notable is that this will deal with files that start with a - or -- just fine.\r\n\r\n\r\nUsage is simple:\r\n1. Give it a list of files to be renamed.\r\n2. Edit that list to reflect what you want the file names to be.\r\n3. \":wq\" and you're done\r\n\r\nHere's a few examples:\r\n\r\n#Rename all non-hidden files in the current directory\r\nlocalhost~$vmv\r\n\r\n#Rename all mp3 files below the current directory\r\nlocalhost~$find | grep  -i '\\.mp3$' | vmv\r\n\r\n#Rename all files listed in file \"list.txt\"\r\n#Note that the file list.txt will be saved as well as files on disk renamed.\r\nlocalhost~$vmv list.txt\r\n\r\nThere are two \"bugs\" that I know of:\r\n1. It remembers the previous name of the file via line number, so if you add or delete lines bad things may happen.\r\n2. It renames files directly to the destination filename, so trying to swap filenames will instead overwrite the second with the first, and rename the second as the first. Probably not what you wanted, but the fix is too complicated and the case rare enough that I didn't bother to implement it.\r\n3. It's fairly slow when writing large lists of files, even if only a few where modified. Some better way of storing the meta-data (i.e. original name) is needed.\r\n\r\nThere isn't really much error checking. If the original file name doesn't exist, that line will fail with a message, but it will merrily proceed with the rest of the file. If the destination file name already exists it will overwrite without warning. There is no lifeguard, swim at your own risk. I was going to write fixes for those, and also make it check if the file exists when it's first loaded for editing. I changed my mind because, after all, <sarcasm> I know what I'm doing. <\/sarcasm> Yes, the 0.1 version number is correct. It's functional, and does what I need it to do, and little else.\r\n\r\nIf you enjoy this script, and want it improved, your comments would be helpful.","4":"vmv - the vim version of the mv command. This script is in intent exactly the same as renamer.vim, rename a mass of files all at once using the full power of vim's editing capabilities.  Usage is much simpler to remember if you haven't used it in months, and the script itself is much shorter. Great for anybody who just ripped a CD to \"track 01.mp3\" through \"track 12.mp3\", or just inherited a collection of mp3's without proper case and with underscores instead of spaces. \r\n\r\nAlso notable is that this will deal with files that start with a - or -- just fine.\r\n\r\n\r\nUsage is simple:\r\n1. Give it a list of files to be renamed.\r\n2. Edit that list to reflect what you want the file names to be.\r\n3. \":wq\" and you're done\r\n\r\nHere's a few examples:\r\n\r\n#Rename all non-hidden files in the current directory\r\nlocalhost~$vmv\r\n\r\n#Rename all mp3 files below the current directory\r\nlocalhost~$find | grep  -i '\\.mp3$' | vmv\r\n\r\n#Rename all files listed in file \"list.txt\"\r\n#Note that the file list.txt will be saved as well as files on disk renamed.\r\nlocalhost~$vmv list.txt\r\n\r\nThere are two \"bugs\" that I know of:\r\n1. It remembers the previous name of the file via line number, so if you add or delete lines bad things may happen.\r\n2. It renames files directly to the destination filename, so trying to swap filenames will instead overwrite the second with the first, and rename the second as the first. Probably not what you wanted, but the fix is too complicated and the case rare enough that I didn't bother to implement it.\r\n3. It's fairly slow when writing large lists of files, even if only a few where modified. Some better way of storing the meta-data (i.e. original name) is needed.\r\n\r\nThere isn't really much error checking. If the original file name doesn't exist, that line will fail with a message, but it will merrily proceed with the rest of the file. If the destination file name already exists it will overwrite without warning. There is no lifeguard, swim at your own risk. I was going to write fixes for those, and also make it check if the file exists when it's first loaded for editing. I changed my mind because, after all, <sarcasm> I know what I'm doing. <\/sarcasm> Yes, the 0.1 version number is correct. It's functional, and does what I need it to do, and little else.\r\n\r\nIf you enjoy this script, and want it improved, your comments would be helpful.","install_details":"0. ungz and untar the files.\r\n1. Copy the bash script \"vmv\" into a directory in your path.\r\n2. Save the vmv.vim file somewhere.\r\n3. Edit the \"vmv\" bash script to reflect the correct location of vmv.vim.\r\n4. Use as per examples above.\r\n\r\nNote that the suppled shell script uses stty to determine if stdin is a pipe or not, so you'll need a shell and stty to use the script. Most, if not all, unix systems will already have both. The #! at the beginning of the script specifies bash, but it'll probably work with other shell programs as well.","5":"0. ungz and untar the files.\r\n1. Copy the bash script \"vmv\" into a directory in your path.\r\n2. Save the vmv.vim file somewhere.\r\n3. Edit the \"vmv\" bash script to reflect the correct location of vmv.vim.\r\n4. Use as per examples above.\r\n\r\nNote that the suppled shell script uses stty to determine if stdin is a pipe or not, so you'll need a shell and stty to use the script. Most, if not all, unix systems will already have both. The #! at the beginning of the script specifies bash, but it'll probably work with other shell programs as well.","first_name":"john","6":"john","last_name":"gilmore","7":"gilmore","releases":[{"0":"2285","vim_version":"6.0","1":"6.0","script_version":"0.2","2":"0.2","version_comment":"removed some debug \"echo\" statements.","3":"removed some debug \"echo\" statements.","package":"vmv.tar.gz","4":"vmv.tar.gz","src_id":"8891","5":"8891","creation_date":"1215376077","6":"1215376077"},{"0":"2285","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"vmv.tar.gz","4":"vmv.tar.gz","src_id":"8890","5":"8890","creation_date":"1215375679","6":"1215375679"}]},"2284":{"script_id":"2284","0":"2284","script_name":"cup.vim","1":"cup.vim","script_type":"syntax","2":"syntax","summary":"CUP Syntax highlighting","3":"CUP Syntax highlighting","description":"Syntax highlighting for the CUP parser generator, an LALR parser generator for JAVA. See http:\/\/www.cs.princeton.edu\/~appel\/modern\/java\/CUP\/\r\n\r\nThe latest version can be found at http:\/\/www.trapdoor.org\/projects\/4\r\n\r\nPatches are welcome.","4":"Syntax highlighting for the CUP parser generator, an LALR parser generator for JAVA. See http:\/\/www.cs.princeton.edu\/~appel\/modern\/java\/CUP\/\r\n\r\nThe latest version can be found at http:\/\/www.trapdoor.org\/projects\/4\r\n\r\nPatches are welcome.","install_details":"Copy cup.vim to ~\/.vim\/syntax and add the following line to ~\/.vim\/filetype.vim :\r\n\r\nautocmd BufNewFile,BufRead *.cup setf cup","5":"Copy cup.vim to ~\/.vim\/syntax and add the following line to ~\/.vim\/filetype.vim :\r\n\r\nautocmd BufNewFile,BufRead *.cup setf cup","first_name":"Jon","6":"Jon","last_name":"Siddle","7":"Siddle","releases":[{"0":"2284","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"cup.vim","4":"cup.vim","src_id":"8889","5":"8889","creation_date":"1215343203","6":"1215343203"}]},"2283":{"script_id":"2283","0":"2283","script_name":"huerotation.vim","1":"huerotation.vim","script_type":"utility","2":"utility","summary":"rotate hue of current colorscheme (GUI only).","3":"rotate hue of current colorscheme (GUI only).","description":"Hue is one of component of HSV color model. \r\nYou can rotate hue of current colorscheme.\r\n\r\nThis plugin requires vim7.2 for Float feature.\r\n\r\nUsage:\r\n  :call RotateHue(60)\r\n\r\nReference:\r\n  EasyRGB - Color mathematics and conversion formulas.:\r\n    http:\/\/www.easyrgb.com\/math.php\r\n  Wikipedia - HSL and HSV\r\n    http:\/\/en.wikipedia.org\/wiki\/HSL_and_HSV","4":"Hue is one of component of HSV color model. \r\nYou can rotate hue of current colorscheme.\r\n\r\nThis plugin requires vim7.2 for Float feature.\r\n\r\nUsage:\r\n  :call RotateHue(60)\r\n\r\nReference:\r\n  EasyRGB - Color mathematics and conversion formulas.:\r\n    http:\/\/www.easyrgb.com\/math.php\r\n  Wikipedia - HSL and HSV\r\n    http:\/\/en.wikipedia.org\/wiki\/HSL_and_HSV","install_details":"","5":"","first_name":"Yukihiro","6":"Yukihiro","last_name":"Nakadaira","7":"Nakadaira","releases":[{"0":"2283","vim_version":"7.0","1":"7.0","script_version":"1.1","2":"1.1","version_comment":"bug fix: use default color when fg or bg is empty.","3":"bug fix: use default color when fg or bg is empty.","package":"huerotation.vim","4":"huerotation.vim","src_id":"8894","5":"8894","creation_date":"1215412214","6":"1215412214"},{"0":"2283","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"huerotation.vim","4":"huerotation.vim","src_id":"8888","5":"8888","creation_date":"1215338045","6":"1215338045"}]},"2282":{"script_id":"2282","0":"2282","script_name":"brook.vim","1":"brook.vim","script_type":"syntax","2":"syntax","summary":"Brook syntax highlighting","3":"Brook syntax highlighting","description":"Syntax highlighting for the Brook stream programming language, a C-like language with extensions for use with GPUs.  See graphics.stanford.edu\/projects\/brookgpu\/ \r\n\r\nThe latest version can be found at http:\/\/github.com\/rbonvall\/vim-scripts\/tree\/master\/syntax\/brook.vim ; patches are welcome.","4":"Syntax highlighting for the Brook stream programming language, a C-like language with extensions for use with GPUs.  See graphics.stanford.edu\/projects\/brookgpu\/ \r\n\r\nThe latest version can be found at http:\/\/github.com\/rbonvall\/vim-scripts\/tree\/master\/syntax\/brook.vim ; patches are welcome.","install_details":"Copy brook.vim to ~\/.vim\/syntax and add the following line to ~\/.vim\/filetype.vim :\r\n\r\nautocmd BufNewFile,BufRead *.br,*.brh,*.bri  setf brook","5":"Copy brook.vim to ~\/.vim\/syntax and add the following line to ~\/.vim\/filetype.vim :\r\n\r\nautocmd BufNewFile,BufRead *.br,*.brh,*.bri  setf brook","first_name":"Roberto","6":"Roberto","last_name":"Bonvallet","7":"Bonvallet","releases":[{"0":"2282","vim_version":"6.0","1":"6.0","script_version":"1","2":"1","version_comment":"Initial upload","3":"Initial upload","package":"brook.vim","4":"brook.vim","src_id":"8887","5":"8887","creation_date":"1215205858","6":"1215205858"}]},"2281":{"script_id":"2281","0":"2281","script_name":"pink","1":"pink","script_type":"color scheme","2":"color scheme","summary":"Pink colour scheme for 256 colour terminals","3":"Pink colour scheme for 256 colour terminals","description":"Use this if you like tabedit, split\/new, folding, netrw and PINK! It works in terminal and GUI mode. Be warned, your colleagues may take the mickey out of you if you use this.\r\n\r\nScreen shot: http:\/\/picasaweb.google.com\/paddynewman\/Vim\/photo#5221682521676117730","4":"Use this if you like tabedit, split\/new, folding, netrw and PINK! It works in terminal and GUI mode. Be warned, your colleagues may take the mickey out of you if you use this.\r\n\r\nScreen shot: http:\/\/picasaweb.google.com\/paddynewman\/Vim\/photo#5221682521676117730","install_details":"mkdir -p ~\/.vim\/colors\r\ncp pink.vim !$\r\nvim\r\n:set colorscheme pink","5":"mkdir -p ~\/.vim\/colors\r\ncp pink.vim !$\r\nvim\r\n:set colorscheme pink","first_name":"Paddy","6":"Paddy","last_name":"Newman","7":"Newman","releases":[{"0":"2281","vim_version":"6.0","1":"6.0","script_version":"2","2":"2","version_comment":"Set colours for line numbers.","3":"Set colours for line numbers.","package":"pink.vim","4":"pink.vim","src_id":"10566","5":"10566","creation_date":"1241893091","6":"1241893091"},{"0":"2281","vim_version":"7.0","1":"7.0","script_version":"1","2":"1","version_comment":"Initial upload","3":"Initial upload","package":"pink.vim","4":"pink.vim","src_id":"8883","5":"8883","creation_date":"1215071342","6":"1215071342"}]},"2280":{"script_id":"2280","0":"2280","script_name":"blackboard.vim","1":"blackboard.vim","script_type":"color scheme","2":"color scheme","summary":"Clone of the Blackboard theme from textmate","3":"Clone of the Blackboard theme from textmate","description":"A dark theme with golds and oranges.  A port of the blackboard textmate theme.  Still some tweaks need to be made but overall it is acurate.\r\n\r\nOnly works in gui mode for now","4":"A dark theme with golds and oranges.  A port of the blackboard textmate theme.  Still some tweaks need to be made but overall it is acurate.\r\n\r\nOnly works in gui mode for now","install_details":"Put it into ~\/.vim\/colors, then :color blackboard","5":"Put it into ~\/.vim\/colors, then :color blackboard","first_name":"Ben","6":"Ben","last_name":"Wyrosdick","7":"Wyrosdick","releases":[{"0":"2280","vim_version":"6.0","1":"6.0","script_version":"1.4","2":"1.4","version_comment":"Updated Folded colors thanks to Jon McIlwaine\r\n\r\nIncludes some other general cleanup but nothing major","3":"Updated Folded colors thanks to Jon McIlwaine\r\n\r\nIncludes some other general cleanup but nothing major","package":"blackboard.vim","4":"blackboard.vim","src_id":"11225","5":"11225","creation_date":"1250786732","6":"1250786732"},{"0":"2280","vim_version":"6.0","1":"6.0","script_version":"1.1","2":"1.1","version_comment":"Updated colors to link properly and put them in logical groups","3":"Updated colors to link properly and put them in logical groups","package":"blackboard.vim","4":"blackboard.vim","src_id":"8881","5":"8881","creation_date":"1214957071","6":"1214957071"},{"0":"2280","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"blackboard.vim","4":"blackboard.vim","src_id":"8879","5":"8879","creation_date":"1214951115","6":"1214951115"}]},"2279":{"script_id":"2279","0":"2279","script_name":"cmdlinehelp","1":"cmdlinehelp","script_type":"utility","2":"utility","summary":"Display help on the command currently being edited in the command line","3":"Display help on the command currently being edited in the command line","description":"Has this ever happened to you? You are typing a command and cannot remember \r\nwhether that particular option is an \"u\" or an \"o\". cmdlinehelp to the \r\nrescue!\r\n\r\nWhen editing a command line, press <c-o> (see also |g:cmdlinehelpMapView|) \r\nto display help on the command currently being edited.\r\n\r\nUse <c-pageup>\/<c-pagedown> to scroll the help window.\r\n\r\nThis plugin was inspired by a post by Marcel Boon to vim_use:\r\nhttp:\/\/groups.google.com\/group\/vim_use\/browse_frm\/thread\/aaa3d652d7b76d02\r\n","4":"Has this ever happened to you? You are typing a command and cannot remember \r\nwhether that particular option is an \"u\" or an \"o\". cmdlinehelp to the \r\nrescue!\r\n\r\nWhen editing a command line, press <c-o> (see also |g:cmdlinehelpMapView|) \r\nto display help on the command currently being edited.\r\n\r\nUse <c-pageup>\/<c-pagedown> to scroll the help window.\r\n\r\nThis plugin was inspired by a post by Marcel Boon to vim_use:\r\nhttp:\/\/groups.google.com\/group\/vim_use\/browse_frm\/thread\/aaa3d652d7b76d02\r\n","install_details":"Edit the vba file and type:\r\n\r\n    :so %\r\n\r\nSee :help vimball for details. If you have difficulties or use vim 7.0, \r\nplease make sure, you have the current version of vimball (vimscript \r\n#1502) installed or update your runtime.\r\n\r\n\r\nAlso available via git\r\nhttp:\/\/github.com\/tomtom\/cmdlinehelp_vim","5":"Edit the vba file and type:\r\n\r\n    :so %\r\n\r\nSee :help vimball for details. If you have difficulties or use vim 7.0, \r\nplease make sure, you have the current version of vimball (vimscript \r\n#1502) installed or update your runtime.\r\n\r\n\r\nAlso available via git\r\nhttp:\/\/github.com\/tomtom\/cmdlinehelp_vim","first_name":"Tom","6":"Tom","last_name":"Link","7":"Link","releases":[{"0":"2279","vim_version":"7.0","1":"7.0","script_version":"0.5","2":"0.5","version_comment":"- Support for command with a bang [!]\r\n- For :call, :echo[m] show help on the function not the command\r\n- g:cmdlinehelpTable may contain references to custom helper function\r\n- The keys in g:cmdlinehelpTable are regexps\r\n- Don't scroll down one line in the tag preview\r\n","3":"- Support for command with a bang [!]\r\n- For :call, :echo[m] show help on the function not the command\r\n- g:cmdlinehelpTable may contain references to custom helper function\r\n- The keys in g:cmdlinehelpTable are regexps\r\n- Don't scroll down one line in the tag preview\r\n","package":"cmdlinehelp.vba.gz","4":"cmdlinehelp.vba.gz","src_id":"8913","5":"8913","creation_date":"1215583670","6":"1215583670"},{"0":"2279","vim_version":"7.0","1":"7.0","script_version":"0.4","2":"0.4","version_comment":"- For :set, :setlocal, :let show help on the option\/variable, not the command\r\n- Catch e426 error.\r\n- Added debug to g:cmdlinehelpIgnore\r\n","3":"- For :set, :setlocal, :let show help on the option\/variable, not the command\r\n- Catch e426 error.\r\n- Added debug to g:cmdlinehelpIgnore\r\n","package":"cmdlinehelp.vba.gz","4":"cmdlinehelp.vba.gz","src_id":"8880","5":"8880","creation_date":"1214956925","6":"1214956925"},{"0":"2279","vim_version":"7.0","1":"7.0","script_version":"0.3","2":"0.3","version_comment":"- Prefixes for cheat sheets: g:cmdlinehelpPrefixes\r\n- Display the help on the top of the preview window\r\n","3":"- Prefixes for cheat sheets: g:cmdlinehelpPrefixes\r\n- Display the help on the top of the preview window\r\n","package":"cmdlinehelp.vba.gz","4":"cmdlinehelp.vba.gz","src_id":"8878","5":"8878","creation_date":"1214917310","6":"1214917310"},{"0":"2279","vim_version":"7.0","1":"7.0","script_version":"0.2","2":"0.2","version_comment":"- g:cmdlinehelpTable\r\n- FIX: wrong window after scrolling\r\n","3":"- g:cmdlinehelpTable\r\n- FIX: wrong window after scrolling\r\n","package":"cmdlinehelp.vba.gz","4":"cmdlinehelp.vba.gz","src_id":"8875","5":"8875","creation_date":"1214898649","6":"1214898649"}]},"2278":{"script_id":"2278","0":"2278","script_name":"jptemplate","1":"jptemplate","script_type":"ftplugin","2":"ftplugin","summary":"A simple, yet powerful interactive template system for VIM","3":"A simple, yet powerful interactive template system for VIM","description":"You will find a lot of documentation and some demo videos on http:\/\/lunar-linux.org\/~jannis\/jptemplate\/.\r\n\r\nYou can also download the script and its documentation directly from my git repository on http:\/\/git.gezeiten.org\/?p=jptemplate.git.\r\n\r\nPlease send bugs and feature requests to the email address which you will find on my profile page. I especially appreciate ideas for new special variables!","4":"You will find a lot of documentation and some demo videos on http:\/\/lunar-linux.org\/~jannis\/jptemplate\/.\r\n\r\nYou can also download the script and its documentation directly from my git repository on http:\/\/git.gezeiten.org\/?p=jptemplate.git.\r\n\r\nPlease send bugs and feature requests to the email address which you will find on my profile page. I especially appreciate ideas for new special variables!","install_details":"","5":"","first_name":"Jannis","6":"Jannis","last_name":"Pohlmann","7":"Pohlmann","releases":[{"0":"2278","vim_version":"6.0","1":"6.0","script_version":"1.5","2":"1.5","version_comment":"New feature:\r\n  * Use general\/ as a fallback directory for all file types. You can now share templates across file types.\r\n\r\nBugfix:\r\n  * Really fix the cursor placement this time (hopefully).","3":"New feature:\r\n  * Use general\/ as a fallback directory for all file types. You can now share templates across file types.\r\n\r\nBugfix:\r\n  * Really fix the cursor placement this time (hopefully).","package":"jptemplate.vim","4":"jptemplate.vim","src_id":"8905","5":"8905","creation_date":"1215518451","6":"1215518451"},{"0":"2278","vim_version":"7.0","1":"7.0","script_version":"1.4","2":"1.4","version_comment":"New features:\r\n  * New special variables: ${shell:<put shell command here>} and ${interactive_shell:...}\r\n  * Remember last entered value for all non-special variables\r\n  \r\nBugfixes:\r\n  * Allow $ to appear in variable names and values (thanks to John O'Shea for reminding me)\r\n  * Automatically escape &, ~ and \\ in variable values to avoid unexpected behaviour (thanks to Kris Malfettone for spotting this one)\r\n  * Just remove template trigger word if the resulting template is empty","3":"New features:\r\n  * New special variables: ${shell:<put shell command here>} and ${interactive_shell:...}\r\n  * Remember last entered value for all non-special variables\r\n  \r\nBugfixes:\r\n  * Allow $ to appear in variable names and values (thanks to John O'Shea for reminding me)\r\n  * Automatically escape &, ~ and \\ in variable values to avoid unexpected behaviour (thanks to Kris Malfettone for spotting this one)\r\n  * Just remove template trigger word if the resulting template is empty","package":"jptemplate.vim","4":"jptemplate.vim","src_id":"8896","5":"8896","creation_date":"1215436410","6":"1215436410"},{"0":"2278","vim_version":"7.0","1":"7.0","script_version":"1.3","2":"1.3","version_comment":"Bugfixes only","3":"Bugfixes only","package":"jptemplate.vim","4":"jptemplate.vim","src_id":"8873","5":"8873","creation_date":"1214842369","6":"1214842369"},{"0":"2278","vim_version":"7.0","1":"7.0","script_version":"1.2","2":"1.2","version_comment":"New features:\r\n  * Support for special variables (with and without default value)\r\n  * Support for global defaults for user variables\r\n  * New special variable: ${date}","3":"New features:\r\n  * Support for special variables (with and without default value)\r\n  * Support for global defaults for user variables\r\n  * New special variable: ${date}","package":"jptemplate.vim","4":"jptemplate.vim","src_id":"8872","5":"8872","creation_date":"1214838460","6":"1214838460"},{"0":"2278","vim_version":"7.0","1":"7.0","script_version":"1.1","2":"1.1","version_comment":"New features:\r\n  * Configurable keyboard shortcut\r\n  * Default values for variables\r\n\r\nBugfixes:\r\n  * Fix cursor position of templates with ${cursor} not at the end of line (thanks to Fernando H. Silva)\r\n  * Support indentation with tabs (thanks to Mahlon Smith)","3":"New features:\r\n  * Configurable keyboard shortcut\r\n  * Default values for variables\r\n\r\nBugfixes:\r\n  * Fix cursor position of templates with ${cursor} not at the end of line (thanks to Fernando H. Silva)\r\n  * Support indentation with tabs (thanks to Mahlon Smith)","package":"jptemplate.vim","4":"jptemplate.vim","src_id":"8870","5":"8870","creation_date":"1214816923","6":"1214816923"},{"0":"2278","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"jptemplate.vim","4":"jptemplate.vim","src_id":"8863","5":"8863","creation_date":"1214587713","6":"1214587713"}]},"2277":{"script_id":"2277","0":"2277","script_name":"DevEiate theme","1":"DevEiate theme","script_type":"color scheme","2":"color scheme","summary":"A dark theme, mimicing the TextMate theme of the same name.","3":"A dark theme, mimicing the TextMate theme of the same name.","description":"This is a Gvim color definition file, based loosely on Michael Granger's\r\neye-pleasing theme for Textmate of the same name.\r\n\r\nMahlon E. Smith <mahlon@martini.nu>\r\nMichael Granger <ged@faeriemud.org>\r\n\r\nSample screenshot here:\r\nhttp:\/\/projects.martini.nu\/vim-stuff\/chrome\/site\/deveiate.png\r\n","4":"This is a Gvim color definition file, based loosely on Michael Granger's\r\neye-pleasing theme for Textmate of the same name.\r\n\r\nMahlon E. Smith <mahlon@martini.nu>\r\nMichael Granger <ged@faeriemud.org>\r\n\r\nSample screenshot here:\r\nhttp:\/\/projects.martini.nu\/vim-stuff\/chrome\/site\/deveiate.png\r\n","install_details":"Drop this into your ~\/.vim\/colors directory, then load it via \r\n\r\n:colorscheme deveiate\r\n","5":"Drop this into your ~\/.vim\/colors directory, then load it via \r\n\r\n:colorscheme deveiate\r\n","first_name":"Mahlon","6":"Mahlon","last_name":"Smith","7":"Smith","releases":[{"0":"2277","vim_version":"7.0","1":"7.0","script_version":"0.2","2":"0.2","version_comment":"Minor color tweaks to increase visibility.  Designed with guicursor=a:hor1 in mind.","3":"Minor color tweaks to increase visibility.  Designed with guicursor=a:hor1 in mind.","package":"deveiate.vim","4":"deveiate.vim","src_id":"8869","5":"8869","creation_date":"1214767742","6":"1214767742"},{"0":"2277","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"deveiate.vim","4":"deveiate.vim","src_id":"8862","5":"8862","creation_date":"1214570712","6":"1214570712"}]},"2276":{"script_id":"2276","0":"2276","script_name":"textobj-jabraces","1":"textobj-jabraces","script_type":"utility","2":"utility","summary":"Text objects for Japanese braces","3":"Text objects for Japanese braces","description":"*textobj-jabraces* is a Vim plugin to provide text objects for Japanese braces\r\nsuch as 「...」 and 【...】.\r\n\r\n\r\nRequirements:\r\n- Vim 7.0 or later\r\n- |textobj-user| 0.3.3 or later (vimscript#2100)\r\n\r\nLatest version:\r\nhttp:\/\/github.com\/kana\/vim-textobj-jabraces\r\n\r\nDocument in HTML format:\r\nhttp:\/\/kana.github.com\/config\/vim\/textobj-jabraces.html","4":"*textobj-jabraces* is a Vim plugin to provide text objects for Japanese braces\r\nsuch as 「...」 and 【...】.\r\n\r\n\r\nRequirements:\r\n- Vim 7.0 or later\r\n- |textobj-user| 0.3.3 or later (vimscript#2100)\r\n\r\nLatest version:\r\nhttp:\/\/github.com\/kana\/vim-textobj-jabraces\r\n\r\nDocument in HTML format:\r\nhttp:\/\/kana.github.com\/config\/vim\/textobj-jabraces.html","install_details":"...","5":"...","first_name":"Kana","6":"Kana","last_name":"Natsuno","7":"Natsuno","releases":[{"0":"2276","vim_version":"7.0","1":"7.0","script_version":"0.1.1","2":"0.1.1","version_comment":"Initial upload","3":"Initial upload","package":"vim-textobj-jabraces-0.1.1.zip","4":"vim-textobj-jabraces-0.1.1.zip","src_id":"8859","5":"8859","creation_date":"1214460004","6":"1214460004"}]},"2275":{"script_id":"2275","0":"2275","script_name":"textobj-fold","1":"textobj-fold","script_type":"utility","2":"utility","summary":"Text objects for foldings","3":"Text objects for foldings","description":"*textobj-fold* is a Vim plugin to provide text objects for foldings.\r\n\r\n\r\nRequirements:\r\n- Vim 7.0 or later\r\n- |textobj-user| 0.3.5 or later (vimscript#2100)\r\n\r\nLatest version:\r\nhttp:\/\/github.com\/kana\/vim-textobj-fold\r\n\r\nDocument in HTML format:\r\nhttp:\/\/kana.github.com\/config\/vim\/textobj-fold.html","4":"*textobj-fold* is a Vim plugin to provide text objects for foldings.\r\n\r\n\r\nRequirements:\r\n- Vim 7.0 or later\r\n- |textobj-user| 0.3.5 or later (vimscript#2100)\r\n\r\nLatest version:\r\nhttp:\/\/github.com\/kana\/vim-textobj-fold\r\n\r\nDocument in HTML format:\r\nhttp:\/\/kana.github.com\/config\/vim\/textobj-fold.html","install_details":"...","5":"...","first_name":"Kana","6":"Kana","last_name":"Natsuno","7":"Natsuno","releases":[{"0":"2275","vim_version":"7.0","1":"7.0","script_version":"0.1.2","2":"0.1.2","version_comment":"- Use textobj-user 0.3.5 or later.\r\n- Fix the bug that closed foldings were not correctly selected.\r\n","3":"- Use textobj-user 0.3.5 or later.\r\n- Fix the bug that closed foldings were not correctly selected.\r\n","package":"vim-textobj-fold-0.1.2.zip","4":"vim-textobj-fold-0.1.2.zip","src_id":"9165","5":"9165","creation_date":"1219639099","6":"1219639099"},{"0":"2275","vim_version":"7.0","1":"7.0","script_version":"0.1.1","2":"0.1.1","version_comment":"Initial upload","3":"Initial upload","package":"vim-textobj-fold-0.1.1.zip","4":"vim-textobj-fold-0.1.1.zip","src_id":"8858","5":"8858","creation_date":"1214459732","6":"1214459732"}]},"2274":{"script_id":"2274","0":"2274","script_name":"flydiff","1":"flydiff","script_type":"utility","2":"utility","summary":"on-the-fly diff","3":"on-the-fly diff","description":"*flydiff* is a Vim plugin to perform on-the-fly diff on the current buffer\r\nwith some version control system and show the differences in another buffer.\r\n\r\n\r\nRequirements:\r\n- Vim 7.1.299 or later\r\n- Ordinary *nix shells such as bash and zsh\r\n\r\nSupported version control systems:\r\n- git\r\n\r\nLatest version:\r\nhttp:\/\/github.com\/kana\/vim-flydiff\r\n\r\nDocument in HTML format:\r\nhttp:\/\/kana.github.com\/config\/vim\/flydiff.html","4":"*flydiff* is a Vim plugin to perform on-the-fly diff on the current buffer\r\nwith some version control system and show the differences in another buffer.\r\n\r\n\r\nRequirements:\r\n- Vim 7.1.299 or later\r\n- Ordinary *nix shells such as bash and zsh\r\n\r\nSupported version control systems:\r\n- git\r\n\r\nLatest version:\r\nhttp:\/\/github.com\/kana\/vim-flydiff\r\n\r\nDocument in HTML format:\r\nhttp:\/\/kana.github.com\/config\/vim\/flydiff.html","install_details":"...","5":"...","first_name":"Kana","6":"Kana","last_name":"Natsuno","7":"Natsuno","releases":[{"0":"2274","vim_version":"7.0","1":"7.0","script_version":"0.0.1","2":"0.0.1","version_comment":"Fix many minor bugs.","3":"Fix many minor bugs.","package":"vim-flydiff-0.0.1.zip","4":"vim-flydiff-0.0.1.zip","src_id":"8867","5":"8867","creation_date":"1214647900","6":"1214647900"},{"0":"2274","vim_version":"7.0","1":"7.0","script_version":"0.0","2":"0.0","version_comment":"Initial upload","3":"Initial upload","package":"vim-flydiff-0.0.zip","4":"vim-flydiff-0.0.zip","src_id":"8851","5":"8851","creation_date":"1214417407","6":"1214417407"}]},"2273":{"script_id":"2273","0":"2273","script_name":"gladecompletion.vim","1":"gladecompletion.vim","script_type":"utility","2":"utility","summary":"IDE-like completion for projects using the Glade UI designer","3":"IDE-like completion for projects using the Glade UI designer","description":"WHAT IS IT?  Provides an Insert mode completion function which completes names\r\nfrom a .glade file as produced by the Glade UI designer.\r\nhttp:\/\/glade.gnome.org\/\r\n\r\nHOW DOES IT WORK?  The plugin defines a function which scans .glade files in\r\ncurrent buffer's current directory.  The function adds Gtk objects and event\r\nhandlers to the insert mode completion menu\r\n\r\nThe menu is invoked by pressing <C-x><C-u> in insert mode.  Read all about it\r\nat |i_CTRL-X_CTRL-U|.\r\n\r\nEach time the completion function is invoked, it looks at the .glade files in\r\nthe current directory and compares the filesystem's modification timestamp\r\nwith the timestamp value from the previous invocation.  Thus, if you\r\nadd\/change a widget in Glade and save the file, those changes are reflected\r\nimmediately in Vim.\r\n\r\n","4":"WHAT IS IT?  Provides an Insert mode completion function which completes names\r\nfrom a .glade file as produced by the Glade UI designer.\r\nhttp:\/\/glade.gnome.org\/\r\n\r\nHOW DOES IT WORK?  The plugin defines a function which scans .glade files in\r\ncurrent buffer's current directory.  The function adds Gtk objects and event\r\nhandlers to the insert mode completion menu\r\n\r\nThe menu is invoked by pressing <C-x><C-u> in insert mode.  Read all about it\r\nat |i_CTRL-X_CTRL-U|.\r\n\r\nEach time the completion function is invoked, it looks at the .glade files in\r\nthe current directory and compares the filesystem's modification timestamp\r\nwith the timestamp value from the previous invocation.  Thus, if you\r\nadd\/change a widget in Glade and save the file, those changes are reflected\r\nimmediately in Vim.\r\n\r\n","install_details":"To turn it on for all files, all the time, put it in your $HOME\/.vim\/plugins directory.\r\nIf you don't use Glade project files for all of your projects and don't want this plugin\r\nto take up precious memory, put it in your $HOME\/.vim\/macros directory, and add\r\nthis command to any of your ftplugins which you do use with Glade:\r\n:runtime macros\/gladecompletion.vim\r\n","5":"To turn it on for all files, all the time, put it in your $HOME\/.vim\/plugins directory.\r\nIf you don't use Glade project files for all of your projects and don't want this plugin\r\nto take up precious memory, put it in your $HOME\/.vim\/macros directory, and add\r\nthis command to any of your ftplugins which you do use with Glade:\r\n:runtime macros\/gladecompletion.vim\r\n","first_name":"erik","6":"erik","last_name":"falor","7":"falor","releases":[{"0":"2273","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"gladecompletion.vim","4":"gladecompletion.vim","src_id":"8844","5":"8844","creation_date":"1214226432","6":"1214226432"}]},"2272":{"script_id":"2272","0":"2272","script_name":"nightflight2.vim","1":"nightflight2.vim","script_type":"color scheme","2":"color scheme","summary":"A dark color scheme dedicated to Antoine de Saint-Exup\u00c3\u00a9ry","3":"A dark color scheme dedicated to Antoine de Saint-Exup\u00c3\u00a9ry","description":"A dark color scheme dedicated to Antoine de Saint-Exup\u00c3\u00a9ry","4":"A dark color scheme dedicated to Antoine de Saint-Exup\u00c3\u00a9ry","install_details":"","5":"","first_name":"Ralf","6":"Ralf","last_name":"Holly","7":"Holly","releases":[{"0":"2272","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"nightflight2.vim","4":"nightflight2.vim","src_id":"8832","5":"8832","creation_date":"1214034346","6":"1214034346"}]},"2271":{"script_id":"2271","0":"2271","script_name":"AutoInclude","1":"AutoInclude","script_type":"utility","2":"utility","summary":"Automatically add #include statements for c++ files","3":"Automatically add #include statements for c++ files","description":"This script allows you to automatically add the #include statements at the top of you *.{cc,hh} files.\r\nTo use it, place the cursor on the type you need to include, then press <;;> and the corresponding #include statement will be added.\r\nIn *.cc files, the correct #include is added, and in *.hh files, the forward declaration is added.\r\n\r\nExample:\r\nvoid myfunc (Foo* x);\r\n-> if you place the cursor on \"Foo\" and press <;;> (just the 2 semicolons), the #include \"foo.hh\" will be added at the top of the file. (The insertion location is specified by a variable, see Install Details).\r\n\r\nThe naming standard used is \"Foo\" and \"FooBar\", for the FooBar class the #include will be: #include \"foo-bar.hh\".","4":"This script allows you to automatically add the #include statements at the top of you *.{cc,hh} files.\r\nTo use it, place the cursor on the type you need to include, then press <;;> and the corresponding #include statement will be added.\r\nIn *.cc files, the correct #include is added, and in *.hh files, the forward declaration is added.\r\n\r\nExample:\r\nvoid myfunc (Foo* x);\r\n-> if you place the cursor on \"Foo\" and press <;;> (just the 2 semicolons), the #include \"foo.hh\" will be added at the top of the file. (The insertion location is specified by a variable, see Install Details).\r\n\r\nThe naming standard used is \"Foo\" and \"FooBar\", for the FooBar class the #include will be: #include \"foo-bar.hh\".","install_details":"Just put the autoinclude.vim file in your ~\/.vim\/plugin directory.\r\nYou can specify the line where the #include will be added with the g:AutoIncludeLine variable.\r\nJust add this line to your ~\/.vimrc file:\r\nlet g:AutoIncludeLine = 42 \r\nWhere 42 is the line number.","5":"Just put the autoinclude.vim file in your ~\/.vim\/plugin directory.\r\nYou can specify the line where the #include will be added with the g:AutoIncludeLine variable.\r\nJust add this line to your ~\/.vimrc file:\r\nlet g:AutoIncludeLine = 42 \r\nWhere 42 is the line number.","first_name":"Py","6":"Py","last_name":"Rho","7":"Rho","releases":[{"0":"2271","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"autoinclude.vim","4":"autoinclude.vim","src_id":"8830","5":"8830","creation_date":"1213975053","6":"1213975053"}]},"2270":{"script_id":"2270","0":"2270","script_name":"pygdb","1":"pygdb","script_type":"utility","2":"utility","summary":"pygtk interface to gdb in connection with (g)vim","3":"pygtk interface to gdb in connection with (g)vim","description":"pygdb is a pygtk interface to gdb. It offers two terminal windows, one for gdb, one for the process to be debugged. On the top it has standard buttons like run, continue, step in, step over, step out and quit. On a second window you can add watches and breakpoints. Furthermore, you can inspect the backtrace and launch gvim on the current executed line by pressing a button.\r\n\r\npygdb stays synchronized with gvim (by using gvim --servername calls). The package provides a pygdb.vim which enables the user to set (conditional) breakpoints and the current execution line is highlighted as well.\r\n\r\nDefault key mappings:\r\nF5: Run\r\nF8: Toggle breakpoint\r\nS-F8: Conditional breakpoint\r\nF9: Show breakpoints\r\nS-F9: Load config\r\n\r\nThe package is in a very young state but I guess it is more or less usable. You may want to give it a try or look for some screenshots at\r\nhttp:\/\/www.cosy.sbg.ac.at\/~shuber\/code-pygdb.php\r\nat first. This project is somehow similar to vdb (vimscript #1703). The main difference is that vdb tries to integrate gdb completely into vim, in contrast to pygdb. However, under some assumptions on the debugger, other debuggers can be integrated easily as well. (Just inherit the DbgTerminal python class)\r\n\r\nP.S. I don't have gvim-6 -- is anyone experiencing that the script works with vim-6 as well?","4":"pygdb is a pygtk interface to gdb. It offers two terminal windows, one for gdb, one for the process to be debugged. On the top it has standard buttons like run, continue, step in, step over, step out and quit. On a second window you can add watches and breakpoints. Furthermore, you can inspect the backtrace and launch gvim on the current executed line by pressing a button.\r\n\r\npygdb stays synchronized with gvim (by using gvim --servername calls). The package provides a pygdb.vim which enables the user to set (conditional) breakpoints and the current execution line is highlighted as well.\r\n\r\nDefault key mappings:\r\nF5: Run\r\nF8: Toggle breakpoint\r\nS-F8: Conditional breakpoint\r\nF9: Show breakpoints\r\nS-F9: Load config\r\n\r\nThe package is in a very young state but I guess it is more or less usable. You may want to give it a try or look for some screenshots at\r\nhttp:\/\/www.cosy.sbg.ac.at\/~shuber\/code-pygdb.php\r\nat first. This project is somehow similar to vdb (vimscript #1703). The main difference is that vdb tries to integrate gdb completely into vim, in contrast to pygdb. However, under some assumptions on the debugger, other debuggers can be integrated easily as well. (Just inherit the DbgTerminal python class)\r\n\r\nP.S. I don't have gvim-6 -- is anyone experiencing that the script works with vim-6 as well?","install_details":"INSTALL.txt:\r\n\r\n1. Put the pygdb directory to somewhere, lets call it <dir> in this help file.\r\n2. Add the following lines into your ~\/.vimrc:\r\n\r\n      \"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\r\n      \"  pygdb\r\n      \"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\r\n\r\n        autocmd Filetype c,cpp :python import sys\r\n        autocmd Filetype c,cpp :python import vim\r\n        autocmd Filetype c,cpp :python pygdbdir = \"<dir>\"\r\n        autocmd Filetype c,cpp :python sys.path.append(pygdbdir)\r\n        autocmd Filetype c,cpp :python vim.command(\"source %s\/pygdb.vim\" % pygdbdir)\r\n        autocmd Filetype c,cpp call GDBMapDefaults()\r\n\r\n\r\n   where you replace <dir> by the corresponding path of pygdb. You may want to\r\n   add <dir> to the environment variable PATH such that you can call pygdb\r\n   from console directly.","5":"INSTALL.txt:\r\n\r\n1. Put the pygdb directory to somewhere, lets call it <dir> in this help file.\r\n2. Add the following lines into your ~\/.vimrc:\r\n\r\n      \"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\r\n      \"  pygdb\r\n      \"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\r\n\r\n        autocmd Filetype c,cpp :python import sys\r\n        autocmd Filetype c,cpp :python import vim\r\n        autocmd Filetype c,cpp :python pygdbdir = \"<dir>\"\r\n        autocmd Filetype c,cpp :python sys.path.append(pygdbdir)\r\n        autocmd Filetype c,cpp :python vim.command(\"source %s\/pygdb.vim\" % pygdbdir)\r\n        autocmd Filetype c,cpp call GDBMapDefaults()\r\n\r\n\r\n   where you replace <dir> by the corresponding path of pygdb. You may want to\r\n   add <dir> to the environment variable PATH such that you can call pygdb\r\n   from console directly.","first_name":"Stefan","6":"Stefan","last_name":"Huber","7":"Huber","releases":[{"0":"2270","vim_version":"7.0","1":"7.0","script_version":"0.99.4","2":"0.99.4","version_comment":"bug fixes around breakpoint parsing, better backtrace view, dblclick on element navigates vim to source position. NOTE the change in install.txt!","3":"bug fixes around breakpoint parsing, better backtrace view, dblclick on element navigates vim to source position. NOTE the change in install.txt!","package":"pygdb-0.99.4.tar.bz2","4":"pygdb-0.99.4.tar.bz2","src_id":"8885","5":"8885","creation_date":"1215137868","6":"1215137868"},{"0":"2270","vim_version":"7.0","1":"7.0","script_version":"0.99.3","2":"0.99.3","version_comment":"fixing some bugs","3":"fixing some bugs","package":"pygdb-0.99.3.tar.bz2","4":"pygdb-0.99.3.tar.bz2","src_id":"8853","5":"8853","creation_date":"1214446577","6":"1214446577"},{"0":"2270","vim_version":"7.0","1":"7.0","script_version":"0.99.2","2":"0.99.2","version_comment":"scrollbars for terminals, parametrizeable vim-servername, loading python via .vimrc only when filetype matches.","3":"scrollbars for terminals, parametrizeable vim-servername, loading python via .vimrc only when filetype matches.","package":"pygdb-0.99.2.tar.bz2","4":"pygdb-0.99.2.tar.bz2","src_id":"8842","5":"8842","creation_date":"1214204116","6":"1214204116"},{"0":"2270","vim_version":"7.0","1":"7.0","script_version":"0.99.1","2":"0.99.1","version_comment":"Initial upload","3":"Initial upload","package":"pygdb-0.99.1.tar.bz2","4":"pygdb-0.99.1.tar.bz2","src_id":"8829","5":"8829","creation_date":"1213955988","6":"1213955988"}]},"2269":{"script_id":"2269","0":"2269","script_name":"vim-rpcpaste","1":"vim-rpcpaste","script_type":"utility","2":"utility","summary":"A ViM plugin to send code to a pastebin such as paste.debian.net using XML-RPC","3":"A ViM plugin to send code to a pastebin such as paste.debian.net using XML-RPC","description":"A ViM plugin to send code to a pastebin such as paste.debian.net using XML-RPC\r\n\r\nUse F2 in visual select mode to send it the selected text.\r\nUse :PasteFile to send the whole file.\r\nUse :PasteGajim to send the selected text and send the url to one of your gajim contact.\r\n\r\n\r\nThis is my first Vim plugin don't hesitate to send me comments about how I could make it better.","4":"A ViM plugin to send code to a pastebin such as paste.debian.net using XML-RPC\r\n\r\nUse F2 in visual select mode to send it the selected text.\r\nUse :PasteFile to send the whole file.\r\nUse :PasteGajim to send the selected text and send the url to one of your gajim contact.\r\n\r\n\r\nThis is my first Vim plugin don't hesitate to send me comments about how I could make it better.","install_details":"Just copy the file to your .vim\/plugins repertory","5":"Just copy the file to your .vim\/plugins repertory","first_name":"Olivier","6":"Olivier","last_name":"Le Thanh Duong","7":"Le Thanh Duong","releases":[{"0":"2269","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"rpcpaste.vim","4":"rpcpaste.vim","src_id":"8819","5":"8819","creation_date":"1213703653","6":"1213703653"}]},"2268":{"script_id":"2268","0":"2268","script_name":"apachelogs.vim","1":"apachelogs.vim","script_type":"syntax","2":"syntax","summary":"Syntax highlight for apache log files","3":"Syntax highlight for apache log files","description":"Recognizes and differences IP address, referer, error type, date and hour and apache general error log constructions. Very useful for debugging perl via warn + CGI, php, for example, because you can easily identify  whether is and apache notice or a real error, which user agent IP produced it, with wich referer was called, etc... \r\n\r\nFor example a perl module that produces an error will break in the pm, but the caller that produces it is the perl script itself, that in apache is the referer. Both are highlighted differently with this syntax file.","4":"Recognizes and differences IP address, referer, error type, date and hour and apache general error log constructions. Very useful for debugging perl via warn + CGI, php, for example, because you can easily identify  whether is and apache notice or a real error, which user agent IP produced it, with wich referer was called, etc... \r\n\r\nFor example a perl module that produces an error will break in the pm, but the caller that produces it is the perl script itself, that in apache is the referer. Both are highlighted differently with this syntax file.","install_details":"Copy to the syntax directory in the root vim installation","5":"Copy to the syntax directory in the root vim installation","first_name":"Ignacio","6":"Ignacio","last_name":"Javier","7":"Javier","releases":[{"0":"2268","vim_version":"6.0","1":"6.0","script_version":"1.002","2":"1.002","version_comment":"Correct unix line endings","3":"Correct unix line endings","package":"apachelogs.vim","4":"apachelogs.vim","src_id":"8817","5":"8817","creation_date":"1213676058","6":"1213676058"}]},"2267":{"script_id":"2267","0":"2267","script_name":"colorful","1":"colorful","script_type":"color scheme","2":"color scheme","summary":"Colorful scheme with light background","3":"Colorful scheme with light background","description":"- This is modification of the habiLight color scheme by Christian Habermann. habiLight happens to be one of my favorite schemes and this script has a few modifications of it. \r\n- Only works for gvim.\r\n","4":"- This is modification of the habiLight color scheme by Christian Habermann. habiLight happens to be one of my favorite schemes and this script has a few modifications of it. \r\n- Only works for gvim.\r\n","install_details":"Download script to ~\/.vim\/colors dir and type \":color colorful\" in the gvim window. ","5":"Download script to ~\/.vim\/colors dir and type \":color colorful\" in the gvim window. ","first_name":"Dinesh","6":"Dinesh","last_name":".","7":".","releases":[{"0":"2267","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"colorful.vim","4":"colorful.vim","src_id":"8810","5":"8810","creation_date":"1213625028","6":"1213625028"}]},"2266":{"script_id":"2266","0":"2266","script_name":"silent.vim","1":"silent.vim","script_type":"color scheme","2":"color scheme","summary":"Vim, GVim light color scheme","3":"Vim, GVim light color scheme","description":"This is a new GUI light color scheme. \r\nSee screenshots at :\r\n\r\nlatest : http:\/\/img515.imageshack.us\/my.php?image=c17cy9.png\r\nhttp:\/\/img405.imageshack.us\/my.php?image=c13rf1.png\r\nhttp:\/\/img210.imageshack.us\/my.php?image=c14lk3.png\r\n","4":"This is a new GUI light color scheme. \r\nSee screenshots at :\r\n\r\nlatest : http:\/\/img515.imageshack.us\/my.php?image=c17cy9.png\r\nhttp:\/\/img405.imageshack.us\/my.php?image=c13rf1.png\r\nhttp:\/\/img210.imageshack.us\/my.php?image=c14lk3.png\r\n","install_details":"Download the script and put it into ~\/.vim\/colors  or \/usr\/share\/vim\/vim71\/colors\/ directory\r\nType :colo silent.  \r\nGood luck!","5":"Download the script and put it into ~\/.vim\/colors  or \/usr\/share\/vim\/vim71\/colors\/ directory\r\nType :colo silent.  \r\nGood luck!","first_name":"Vasilii","6":"Vasilii","last_name":"Pascal","7":"Pascal","releases":[{"0":"2266","vim_version":"7.0","1":"7.0","script_version":"1.4.2","2":"1.4.2","version_comment":"Final updates for this month :) \r\nThanks for everyone. ","3":"Final updates for this month :) \r\nThanks for everyone. ","package":"silent.vim","4":"silent.vim","src_id":"9876","5":"9876","creation_date":"1233091752","6":"1233091752"},{"0":"2266","vim_version":"7.0","1":"7.0","script_version":"1.4.1","2":"1.4.1","version_comment":"Small fix for cursor , cursor line cursor column . ","3":"Small fix for cursor , cursor line cursor column . ","package":"silent.vim","4":"silent.vim","src_id":"9872","5":"9872","creation_date":"1233044023","6":"1233044023"},{"0":"2266","vim_version":"7.0","1":"7.0","script_version":"1.4","2":"1.4","version_comment":"A GUI light color scheme. It is recommended to use it with http:\/\/www.vim.org\/scripts\/script.php?script_id=2390\r\n CSApprox by Matt Wozniski for console terminals (konsole\/xterm\/eterm etc.).\r\nMade some changes for better  view of  PHP, C, C++ , Python , css  filetypes ,  this version is a bit different to the previous.   ","3":"A GUI light color scheme. It is recommended to use it with http:\/\/www.vim.org\/scripts\/script.php?script_id=2390\r\n CSApprox by Matt Wozniski for console terminals (konsole\/xterm\/eterm etc.).\r\nMade some changes for better  view of  PHP, C, C++ , Python , css  filetypes ,  this version is a bit different to the previous.   ","package":"silent.vim","4":"silent.vim","src_id":"9866","5":"9866","creation_date":"1233005889","6":"1233005889"},{"0":"2266","vim_version":"6.0","1":"6.0","script_version":"1.3.3","2":"1.3.3","version_comment":"Updates for vimdiff gvimdiff colors. ","3":"Updates for vimdiff gvimdiff colors. ","package":"silent.vim","4":"silent.vim","src_id":"9157","5":"9157","creation_date":"1219202359","6":"1219202359"},{"0":"2266","vim_version":"7.0","1":"7.0","script_version":"1.3.2","2":"1.3.2","version_comment":"Some fixes for diff. Thanks to Robe Valentin . Diff colors changed. Do not hesitate to send your comments and notes. Thanx to everyone.","3":"Some fixes for diff. Thanks to Robe Valentin . Diff colors changed. Do not hesitate to send your comments and notes. Thanx to everyone.","package":"silent.vim","4":"silent.vim","src_id":"9022","5":"9022","creation_date":"1216949038","6":"1216949038"},{"0":"2266","vim_version":"7.0","1":"7.0","script_version":"1.3.1","2":"1.3.1","version_comment":"Small changes for light terminal view. \r\nDirectory and errors view improved.\r\n","3":"Small changes for light terminal view. \r\nDirectory and errors view improved.\r\n","package":"silent.vim","4":"silent.vim","src_id":"9014","5":"9014","creation_date":"1216883237","6":"1216883237"},{"0":"2266","vim_version":"7.0","1":"7.0","script_version":"1.3","2":"1.3","version_comment":"Little updates for GUI light      :) \r\n\r\nhttp:\/\/img521.imageshack.us\/my.php?image=c17wu1.png  \r\n\r\nNot tested  for diff yet.  ","3":"Little updates for GUI light      :) \r\n\r\nhttp:\/\/img521.imageshack.us\/my.php?image=c17wu1.png  \r\n\r\nNot tested  for diff yet.  ","package":"silent.vim","4":"silent.vim","src_id":"9012","5":"9012","creation_date":"1216869643","6":"1216869643"},{"0":"2266","vim_version":"7.0","1":"7.0","script_version":"1.2","2":"1.2","version_comment":"Small changes to get this theme work in dark console terminals. \r\nSmall updates for GUI  now underlines matches brackets using \"underline\". \r\nFor a pity light terminal version has not hight contrast black color for \"normal\" text and comments changed to brown. \r\nGood luck!","3":"Small changes to get this theme work in dark console terminals. \r\nSmall updates for GUI  now underlines matches brackets using \"underline\". \r\nFor a pity light terminal version has not hight contrast black color for \"normal\" text and comments changed to brown. \r\nGood luck!","package":"silent.vim","4":"silent.vim","src_id":"8852","5":"8852","creation_date":"1214443503","6":"1214443503"},{"0":"2266","vim_version":"7.0","1":"7.0","script_version":"1.1","2":"1.1","version_comment":"Small changes for GUI version and  small changes for light color terminals. Sorry to people who use dark color terminals i think it will be ready soon. See latest screenshot : http:\/\/img140.imageshack.us\/my.php?image=c15jy7.png\r\nThank you for your voting and downloads.\r\n\r\n\r\n","3":"Small changes for GUI version and  small changes for light color terminals. Sorry to people who use dark color terminals i think it will be ready soon. See latest screenshot : http:\/\/img140.imageshack.us\/my.php?image=c15jy7.png\r\nThank you for your voting and downloads.\r\n\r\n\r\n","package":"silent.vim","4":"silent.vim","src_id":"8822","5":"8822","creation_date":"1213760825","6":"1213760825"},{"0":"2266","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"silent.vim","4":"silent.vim","src_id":"8799","5":"8799","creation_date":"1213328379","6":"1213328379"}]},"2265":{"script_id":"2265","0":"2265","script_name":"vera.vim","1":"vera.vim","script_type":"syntax","2":"syntax","summary":"Syntax for OpenVera language","3":"Syntax for OpenVera language","description":"Vera is a Hardware Verification Language sold by Synopsys.\r\nThis syntax also contains RVM keywords and has been updated for vera 6.3.0 and RVM 8.6\r\n\r\ncheers!\r\n ","4":"Vera is a Hardware Verification Language sold by Synopsys.\r\nThis syntax also contains RVM keywords and has been updated for vera 6.3.0 and RVM 8.6\r\n\r\ncheers!\r\n ","install_details":"Step 1: drop the file in ~\/.vim\/syntax (if the directory does not exist then create it)\r\n             Note: If you are using vim 7.0 or better, you can source vera.vba to autoinstall it regardless of which flavor of\r\n             operating system you are using VIM on!!\r\nStep 2: Append following lines in ~\/.vim\/filetype.vim\r\n\r\n if exists(\"did_load_filetypes\")\r\n          finish\r\n        endif\r\n        augroup filetypedetect\r\n          au! BufRead,BufNewFile *.vr    setfiletype vera\r\n          au! BufRead,BufNewFile *.vrh   setfiletype vera\r\n        augroup END\r\n","5":"Step 1: drop the file in ~\/.vim\/syntax (if the directory does not exist then create it)\r\n             Note: If you are using vim 7.0 or better, you can source vera.vba to autoinstall it regardless of which flavor of\r\n             operating system you are using VIM on!!\r\nStep 2: Append following lines in ~\/.vim\/filetype.vim\r\n\r\n if exists(\"did_load_filetypes\")\r\n          finish\r\n        endif\r\n        augroup filetypedetect\r\n          au! BufRead,BufNewFile *.vr    setfiletype vera\r\n          au! BufRead,BufNewFile *.vrh   setfiletype vera\r\n        augroup END\r\n","first_name":"Aditya","6":"Aditya","last_name":"Kher","7":"Kher","releases":[{"0":"2265","vim_version":"7.0","1":"7.0","script_version":"0.2","2":"0.2","version_comment":"vba for vim 7.0 or better","3":"vba for vim 7.0 or better","package":"vera.vba","4":"vera.vba","src_id":"8793","5":"8793","creation_date":"1213251953","6":"1213251953"},{"0":"2265","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"vera.vim","4":"vera.vim","src_id":"8792","5":"8792","creation_date":"1213251888","6":"1213251888"}]},"2264":{"script_id":"2264","0":"2264","script_name":"EZComment","1":"EZComment","script_type":"utility","2":"utility","summary":"Vim global plugin for manipulating comments","3":"Vim global plugin for manipulating comments","description":"EZComment is a Vim global plugin for manipulating comments\r\nin code.  It tries to both very flexible and very easy to\r\nuse.  EZComment provides mappings for two general kinds of\r\ntasks: inserting and editing text comments, and\r\ncommenting\/uncommenting actual code.\r\n\r\nUse and customization of EZComment is discussed in detail in\r\nthe provided help file.  Here is the quick start information\r\n(from the documentation):\r\n\r\n-------------------------------------------------------------\r\nHere are some -very- brief hints about the mappings to get\r\nstarted quickly.  The mappings try to remind you of standard\r\nVim commands, so just try them!  If something is not\r\nobvious, then check the documentation for details.\r\n\r\nFrom normal mode:\r\nto make new comments |gca|, |gci|, |gco|, |gcO|\r\nto edit comments |gcA|, |gcC|\r\n\r\nFrom visual mode, or from normal mode followed by {motion}:\r\nto comment code |gcc|\r\nto uncomment code |gcuc|\r\n-------------------------------------------------------------\r\n\r\nPlease contact the author with comments, questions, or\r\nsuggestions!\r\n\r\n","4":"EZComment is a Vim global plugin for manipulating comments\r\nin code.  It tries to both very flexible and very easy to\r\nuse.  EZComment provides mappings for two general kinds of\r\ntasks: inserting and editing text comments, and\r\ncommenting\/uncommenting actual code.\r\n\r\nUse and customization of EZComment is discussed in detail in\r\nthe provided help file.  Here is the quick start information\r\n(from the documentation):\r\n\r\n-------------------------------------------------------------\r\nHere are some -very- brief hints about the mappings to get\r\nstarted quickly.  The mappings try to remind you of standard\r\nVim commands, so just try them!  If something is not\r\nobvious, then check the documentation for details.\r\n\r\nFrom normal mode:\r\nto make new comments |gca|, |gci|, |gco|, |gcO|\r\nto edit comments |gcA|, |gcC|\r\n\r\nFrom visual mode, or from normal mode followed by {motion}:\r\nto comment code |gcc|\r\nto uncomment code |gcuc|\r\n-------------------------------------------------------------\r\n\r\nPlease contact the author with comments, questions, or\r\nsuggestions!\r\n\r\n","install_details":"To install, drop ezcomment.zip in your runtime directory\r\n(e.g. ~\/.vim) and unzip it there.  To use the help file,\r\nmake sure to run :helptags ~\/.vim\/doc.\r\n","5":"To install, drop ezcomment.zip in your runtime directory\r\n(e.g. ~\/.vim) and unzip it there.  To use the help file,\r\nmake sure to run :helptags ~\/.vim\/doc.\r\n","first_name":"Mike","6":"Mike","last_name":"Richman","7":"Richman","releases":[{"0":"2264","vim_version":"7.0","1":"7.0","script_version":"0.1.5","2":"0.1.5","version_comment":"Fixed a big oops -- one of the main functions was accidentally deleted in the previous upload.  Now everything should be working normally.","3":"Fixed a big oops -- one of the main functions was accidentally deleted in the previous upload.  Now everything should be working normally.","package":"ezcomment.zip","4":"ezcomment.zip","src_id":"9726","5":"9726","creation_date":"1230407519","6":"1230407519"},{"0":"2264","vim_version":"7.0","1":"7.0","script_version":"0.1.4","2":"0.1.4","version_comment":"Fixed a bug causing incorrect behavior when the cursor was at the end of the line.","3":"Fixed a bug causing incorrect behavior when the cursor was at the end of the line.","package":"ezcomment.zip","4":"ezcomment.zip","src_id":"9725","5":"9725","creation_date":"1230361483","6":"1230361483"},{"0":"2264","vim_version":"7.0","1":"7.0","script_version":"0.1.3","2":"0.1.3","version_comment":"Added ability to position trailing comments for C preprocessor code independently of the position of normal trailing comments.","3":"Added ability to position trailing comments for C preprocessor code independently of the position of normal trailing comments.","package":"ezcomment.zip","4":"ezcomment.zip","src_id":"8850","5":"8850","creation_date":"1214394207","6":"1214394207"},{"0":"2264","vim_version":"7.0","1":"7.0","script_version":"0.1.2","2":"0.1.2","version_comment":"Bug fix: {Visual}gcuc was only was only uncommenting the first line in the selection.  Corrected behavior is to uncomment every line in the selection.","3":"Bug fix: {Visual}gcuc was only was only uncommenting the first line in the selection.  Corrected behavior is to uncomment every line in the selection.","package":"ezcomment.zip","4":"ezcomment.zip","src_id":"8789","5":"8789","creation_date":"1213204980","6":"1213204980"},{"0":"2264","vim_version":"7.0","1":"7.0","script_version":"0.1.1","2":"0.1.1","version_comment":"Changed name to EZComment; updated manual to reflect change.","3":"Changed name to EZComment; updated manual to reflect change.","package":"ezcomment.zip","4":"ezcomment.zip","src_id":"8786","5":"8786","creation_date":"1213173833","6":"1213173833"},{"0":"2264","vim_version":"7.0","1":"7.0","script_version":"0.1.0","2":"0.1.0","version_comment":"Initial upload","3":"Initial upload","package":"ezcom.zip","4":"ezcom.zip","src_id":"8776","5":"8776","creation_date":"1212978704","6":"1212978704"}]},"2263":{"script_id":"2263","0":"2263","script_name":"xtemplate","1":"xtemplate","script_type":"utility","2":"utility","summary":"code template engine","3":"code template engine","description":"USAGE:                                                                         \r\n  1) vim test.js                                                               \r\n  2) type:                                                                     \r\n    for<C-S-j> or <M-space> or <M-S-j>                                                                 \r\n    to generate a for-loop template. then type and use TAB to navigate through \r\n    template                 \r\n  \r\nHow to DEFINE TEMPLATEs \r\n    edit ftplugin\/*\/*.template.vim                                                  \r\n\r\nFEATUREs:\r\n  *-> automatically replace all item with the same name\r\n  *-> user-defined template variable or function can be automatically inserted\r\n  *-> stop position(marked by 'cursor') can be defined to indicate where the cursor stands after template rendering\r\n  *-> completion popup menu hint (NEW!!)\r\n\r\nSCREEN-SHOTs:\r\nhttp:\/\/sites.google.com\/site\/xptemplate\/Home\/screen-shoot\r\n\r\nFEATURE request \/ BUG report : \r\n    I will be so gald to know that this script helps. You can help me to improve.\r\n    drdr.xp@gmail.com","4":"USAGE:                                                                         \r\n  1) vim test.js                                                               \r\n  2) type:                                                                     \r\n    for<C-S-j> or <M-space> or <M-S-j>                                                                 \r\n    to generate a for-loop template. then type and use TAB to navigate through \r\n    template                 \r\n  \r\nHow to DEFINE TEMPLATEs \r\n    edit ftplugin\/*\/*.template.vim                                                  \r\n\r\nFEATUREs:\r\n  *-> automatically replace all item with the same name\r\n  *-> user-defined template variable or function can be automatically inserted\r\n  *-> stop position(marked by 'cursor') can be defined to indicate where the cursor stands after template rendering\r\n  *-> completion popup menu hint (NEW!!)\r\n\r\nSCREEN-SHOTs:\r\nhttp:\/\/sites.google.com\/site\/xptemplate\/Home\/screen-shoot\r\n\r\nFEATURE request \/ BUG report : \r\n    I will be so gald to know that this script helps. You can help me to improve.\r\n    drdr.xp@gmail.com","install_details":" unpack and copy files into vim plugin directory    ","5":" unpack and copy files into vim plugin directory    ","first_name":"drdr","6":"drdr","last_name":"xp","7":"xp","releases":[{"0":"2263","vim_version":"7.0","1":"7.0","script_version":"0.2.2","2":"0.2.2","version_comment":"Fixed fix the bug of some text being selected at start          \r\nFixed bug of cursor at first column not being rendered correctly\r\nFixed fix no item bug.                                          \r\nAdded add default cursor position at template end               \r\n","3":"Fixed fix the bug of some text being selected at start          \r\nFixed bug of cursor at first column not being rendered correctly\r\nFixed fix no item bug.                                          \r\nAdded add default cursor position at template end               \r\n","package":"xt.0.2.2.tar.gz","4":"xt.0.2.2.tar.gz","src_id":"8806","5":"8806","creation_date":"1213493018","6":"1213493018"}]},"2262":{"script_id":"2262","0":"2262","script_name":"occur.vim","1":"occur.vim","script_type":"utility","2":"utility","summary":"Show all lines in the buffer containing word (grep buffer)","3":"Show all lines in the buffer containing word (grep buffer)","description":"This script looks like 'occur' of emacs script.\r\n\r\nCreate a quickfix list using all lines in the buffer containing a match for regexp.\r\nSearch for regexp in the current buffer or all buffers.\r\n\r\nSearch current buffer:\r\n(1) Search the word by '\/' command.\r\n(2)  :Occur\r\n\r\nSearch all buffers:\r\n(1) Search the word by '\/' command.\r\n(2)  :Moccur\r\n\r\nSeach all buffers for occurrence of the word nearest to the cursor:\r\n(1) move the cursor to the word\r\n(2) :StarOccur\r\n\r\nYou can use keymappings of\r\n  <Leader>oc   - Occur\r\n  <Leader>mo   - Moccur\r\n  <Leader>*   - StarOccur\r\n\r\n# The default <Leader> is backslash. (ex: \\* = StarOccur) \r\n# (see :help mapleader)\r\n\r\n[QUICKFIX KEY-MAPPING]\r\nThis plugin enhances quickfix key-mapping.\r\n(when this plugin opens the quickfix window.)\r\n\r\n<Space> : Set current window height to highest.\r\nx : Display the occurence the current line.\r\nq : Quit the quickfix window.\r\n\r\nIf you want to disable this, then you can set the variable in the \"vimrc\".\r\n\r\n  let g:occur_no_quickfix_map = 1\r\n","4":"This script looks like 'occur' of emacs script.\r\n\r\nCreate a quickfix list using all lines in the buffer containing a match for regexp.\r\nSearch for regexp in the current buffer or all buffers.\r\n\r\nSearch current buffer:\r\n(1) Search the word by '\/' command.\r\n(2)  :Occur\r\n\r\nSearch all buffers:\r\n(1) Search the word by '\/' command.\r\n(2)  :Moccur\r\n\r\nSeach all buffers for occurrence of the word nearest to the cursor:\r\n(1) move the cursor to the word\r\n(2) :StarOccur\r\n\r\nYou can use keymappings of\r\n  <Leader>oc   - Occur\r\n  <Leader>mo   - Moccur\r\n  <Leader>*   - StarOccur\r\n\r\n# The default <Leader> is backslash. (ex: \\* = StarOccur) \r\n# (see :help mapleader)\r\n\r\n[QUICKFIX KEY-MAPPING]\r\nThis plugin enhances quickfix key-mapping.\r\n(when this plugin opens the quickfix window.)\r\n\r\n<Space> : Set current window height to highest.\r\nx : Display the occurence the current line.\r\nq : Quit the quickfix window.\r\n\r\nIf you want to disable this, then you can set the variable in the \"vimrc\".\r\n\r\n  let g:occur_no_quickfix_map = 1\r\n","install_details":"Copy occur.vim to your plugin directory.\r\n \r\n\r\n","5":"Copy occur.vim to your plugin directory.\r\n \r\n\r\n","first_name":"Noriyoshi","6":"Noriyoshi","last_name":"Furusawa","7":"Furusawa","releases":[{"0":"2262","vim_version":"7.0","1":"7.0","script_version":"0.03","2":"0.03","version_comment":"add: new command \"StarOccur\"\r\nadd: enhansed quickfix key-mapping","3":"add: new command \"StarOccur\"\r\nadd: enhansed quickfix key-mapping","package":"occur.vim","4":"occur.vim","src_id":"8944","5":"8944","creation_date":"1215939144","6":"1215939144"},{"0":"2262","vim_version":"7.0","1":"7.0","script_version":"0.02","2":"0.02","version_comment":"add: 'errorformat' setting","3":"add: 'errorformat' setting","package":"occur.vim","4":"occur.vim","src_id":"8773","5":"8773","creation_date":"1212941186","6":"1212941186"},{"0":"2262","vim_version":"7.0","1":"7.0","script_version":"0.01","2":"0.01","version_comment":"Initial upload","3":"Initial upload","package":"occur.vim","4":"occur.vim","src_id":"8772","5":"8772","creation_date":"1212912890","6":"1212912890"}]},"2261":{"script_id":"2261","0":"2261","script_name":"nagios syntax","1":"nagios syntax","script_type":"syntax","2":"syntax","summary":"Nagios template object configuration file","3":"Nagios template object configuration file","description":"Nagios <http:\/\/www.nagios.org\/> template object configuration file.\r\n\r\nInitially based on gentoo source http:\/\/dev.gentoo.org\/~ramereth\/vim\/syntax\/nagios.vim\r\nhttp:\/\/bugs.gentoo.org\/show_bug.cgi?id=76712\r\nwhich instead based on http:\/\/katanalynx.dyndns.org\/~ajar\/code :)\r\n\r\nCurrent URL:\r\nhttp:\/\/cvs.pld-linux.org\/cgi-bin\/cvsweb.cgi\/packages\/vim-syntax-nagios\/nagios.vim","4":"Nagios <http:\/\/www.nagios.org\/> template object configuration file.\r\n\r\nInitially based on gentoo source http:\/\/dev.gentoo.org\/~ramereth\/vim\/syntax\/nagios.vim\r\nhttp:\/\/bugs.gentoo.org\/show_bug.cgi?id=76712\r\nwhich instead based on http:\/\/katanalynx.dyndns.org\/~ajar\/code :)\r\n\r\nCurrent URL:\r\nhttp:\/\/cvs.pld-linux.org\/cgi-bin\/cvsweb.cgi\/packages\/vim-syntax-nagios\/nagios.vim","install_details":"- for local install\r\nPREFIX=~\/.vim\r\n\r\n- for global install (requries root privileges)\r\nPREFIX=\/usr\/share\/vim\/vimfiles\r\n\r\n- and then run:\r\nmkdir -p $PREFIX\/{syntax,ftdetect}\r\ncp nagios.vim $PREFIX\/syntax\/nagios.vim\r\ncat > $PREFIX\/ftdetect\/nagios.vim <<-EOF\r\nau BufNewFile,BufRead \/*etc\/nagios\/*.cfg,*sample-config\/template-object\/*.cfg{,.in},\/var\/lib\/nagios\/objects.cache set filetype\r\n=nagios\r\nEOF\r\n","5":"- for local install\r\nPREFIX=~\/.vim\r\n\r\n- for global install (requries root privileges)\r\nPREFIX=\/usr\/share\/vim\/vimfiles\r\n\r\n- and then run:\r\nmkdir -p $PREFIX\/{syntax,ftdetect}\r\ncp nagios.vim $PREFIX\/syntax\/nagios.vim\r\ncat > $PREFIX\/ftdetect\/nagios.vim <<-EOF\r\nau BufNewFile,BufRead \/*etc\/nagios\/*.cfg,*sample-config\/template-object\/*.cfg{,.in},\/var\/lib\/nagios\/objects.cache set filetype\r\n=nagios\r\nEOF\r\n","first_name":"Elan","6":"Elan","last_name":"Ruusam\u00c3\u00a4e","7":"Ruusam\u00c3\u00a4e","releases":[{"0":"2261","vim_version":"6.0","1":"6.0","script_version":"1.8","2":"1.8","version_comment":"Initial upload","3":"Initial upload","package":"nagios.vim","4":"nagios.vim","src_id":"8770","5":"8770","creation_date":"1212896262","6":"1212896262"}]},"2260":{"script_id":"2260","0":"2260","script_name":"Contrasty","1":"Contrasty","script_type":"color scheme","2":"color scheme","summary":"Contrasty colour scheme","3":"Contrasty colour scheme","description":"Aiming to be high contrast, with significantly different hues, and usable in GUI as well as colour terminals. Should be used with a sans-serif font.","4":"Aiming to be high contrast, with significantly different hues, and usable in GUI as well as colour terminals. Should be used with a sans-serif font.","install_details":"","5":"","first_name":"Ben","6":"Ben","last_name":"Schmidt","7":"Schmidt","releases":[{"0":"2260","vim_version":"6.0","1":"6.0","script_version":"3","2":"3","version_comment":"Initial upload","3":"Initial upload","package":"contrasty.vim","4":"contrasty.vim","src_id":"8763","5":"8763","creation_date":"1212741617","6":"1212741617"}]},"2259":{"script_id":"2259","0":"2259","script_name":"Named Buffers","1":"Named Buffers","script_type":"utility","2":"utility","summary":"Give names to buffers","3":"Give names to buffers","description":"This plugin let's you assign names to buffers, which may later on be used to navigate to this buffer\r\nby the assigned name. This is not very sophisticated and there are a lot of other navigation plugins,\r\nbut maybe it fits your need.\r\n\r\n:NameBuffer resp. :NameThisBuffer let's you assign a name to a buffer.\r\n:GotoNamedBuffer navigates to a buffer by name.\r\n:UnnameBuffer remove a previously assigned buffer.\r\n:ListNamedBuffers to see what names you already assigned.","4":"This plugin let's you assign names to buffers, which may later on be used to navigate to this buffer\r\nby the assigned name. This is not very sophisticated and there are a lot of other navigation plugins,\r\nbut maybe it fits your need.\r\n\r\n:NameBuffer resp. :NameThisBuffer let's you assign a name to a buffer.\r\n:GotoNamedBuffer navigates to a buffer by name.\r\n:UnnameBuffer remove a previously assigned buffer.\r\n:ListNamedBuffers to see what names you already assigned.","install_details":"Unzip the files into your ~\/.vim or vimfiles directory. Run :helptags for the doc directory.","5":"Unzip the files into your ~\/.vim or vimfiles directory. Run :helptags for the doc directory.","first_name":"Meikel","6":"Meikel","last_name":"Brandmeyer","7":"Brandmeyer","releases":[{"0":"2259","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"namedbuffers.zip","4":"namedbuffers.zip","src_id":"8757","5":"8757","creation_date":"1212671596","6":"1212671596"}]},"2258":{"script_id":"2258","0":"2258","script_name":"Git Branch Info","1":"Git Branch Info","script_type":"utility","2":"utility","summary":"A plugin for use on your status line to show info about Git branches","3":"A plugin for use on your status line to show info about Git branches","description":"This plugin show branches information on the status line.\r\nTo install, just put this file on ~\/.vim\/plugins and set your status line:\r\n\r\n:set statusline=%{GitBranchInfoString}\r\n\r\nOf course you can append this configuration to an existing one and make all \r\nthe customization you want on the status line, like:\r\n\r\n:set statusline=%#ErrorMsg#%{GitBranchInfoString}%#StatusLine#\r\n\r\nThe command above will show the Git branches info on the same color as the\r\nerror messages. You can choose any color scheme you want to. Use\r\n\r\n:help highlight-groups\r\n\r\nto check for some other options.\r\n\r\nThere are some customization on the result string based on existing variables \r\nlike:\r\n\r\nlet g:git_branch_status_head_current=1\r\nThis will show just the current head branch name \r\n\r\nlet g:git_branch_status_text=\"text\"\r\nThis will show 'text' before the branches. If not set ' Git ' (with a trailing\r\nleft space) will be displayed.\r\n\r\nlet g:git_branch_status_nogit=\"\"\r\nThe message when there is no Git repository on the current dir\r\n\r\nlet g:git_branch_status_around=\"\"\r\nCharacters to put around the branch strings. Need to be a pair or characters,\r\nthe first will be on the beginning of the branch string and the last on the\r\nend.\r\n\r\nlet g:git_branch_status_ignore_remotes=1\r\nIgnore the remote branches. If you don't want information about them, this can\r\nmake things works faster.\r\n\r\nIf you want to make your own customizations, you can use the GitBranchInfoTokens()\r\nfunction. It returns an array with the current branch as the first element and\r\nanother array with the other branches as the second element, like:\r\n\r\n:set statusline=%#ErrorMsg#%{GitBranchInfoTokens()[0]}%#StatusLine#\r\n\r\nor\r\n\r\n:set statusline=%#StatusLineNC#\\ Git\\ %#ErrorMsg#\\ %{GitBranchInfoTokens()[0]}\\ %#StatusLine#\r\n\r\nwill give you a nice custom formatted string.\r\n\r\nThis will show you the current branch only. No prefix text, no characters\r\naround it. You can also make another functions to use the returned array.\r\n\r\nGet the latest code on http:\/\/github.com\/taq\/vim-git-branch-info","4":"This plugin show branches information on the status line.\r\nTo install, just put this file on ~\/.vim\/plugins and set your status line:\r\n\r\n:set statusline=%{GitBranchInfoString}\r\n\r\nOf course you can append this configuration to an existing one and make all \r\nthe customization you want on the status line, like:\r\n\r\n:set statusline=%#ErrorMsg#%{GitBranchInfoString}%#StatusLine#\r\n\r\nThe command above will show the Git branches info on the same color as the\r\nerror messages. You can choose any color scheme you want to. Use\r\n\r\n:help highlight-groups\r\n\r\nto check for some other options.\r\n\r\nThere are some customization on the result string based on existing variables \r\nlike:\r\n\r\nlet g:git_branch_status_head_current=1\r\nThis will show just the current head branch name \r\n\r\nlet g:git_branch_status_text=\"text\"\r\nThis will show 'text' before the branches. If not set ' Git ' (with a trailing\r\nleft space) will be displayed.\r\n\r\nlet g:git_branch_status_nogit=\"\"\r\nThe message when there is no Git repository on the current dir\r\n\r\nlet g:git_branch_status_around=\"\"\r\nCharacters to put around the branch strings. Need to be a pair or characters,\r\nthe first will be on the beginning of the branch string and the last on the\r\nend.\r\n\r\nlet g:git_branch_status_ignore_remotes=1\r\nIgnore the remote branches. If you don't want information about them, this can\r\nmake things works faster.\r\n\r\nIf you want to make your own customizations, you can use the GitBranchInfoTokens()\r\nfunction. It returns an array with the current branch as the first element and\r\nanother array with the other branches as the second element, like:\r\n\r\n:set statusline=%#ErrorMsg#%{GitBranchInfoTokens()[0]}%#StatusLine#\r\n\r\nor\r\n\r\n:set statusline=%#StatusLineNC#\\ Git\\ %#ErrorMsg#\\ %{GitBranchInfoTokens()[0]}\\ %#StatusLine#\r\n\r\nwill give you a nice custom formatted string.\r\n\r\nThis will show you the current branch only. No prefix text, no characters\r\naround it. You can also make another functions to use the returned array.\r\n\r\nGet the latest code on http:\/\/github.com\/taq\/vim-git-branch-info","install_details":"Download the zip file and unzip it on your .vim directory.","5":"Download the zip file and unzip it on your .vim directory.","first_name":"Eustaquio","6":"Eustaquio","last_name":"Rangel de Oliveira Jr.","7":"Rangel de Oliveira Jr.","releases":[{"0":"2258","vim_version":"7.0","1":"7.0","script_version":"0.1.5","2":"0.1.5","version_comment":"- Changed the buffer vars name with the prefix 'gbi' to try to make sure they will not clash with other vars on other scripts. At least now they are declarative to *this* script.\r\n- Functions are now local to the script.\r\n- Changed some functions scope\r\n- Reorganizing functions and moved another one to the public scope.\r\n- Implemented autogroup","3":"- Changed the buffer vars name with the prefix 'gbi' to try to make sure they will not clash with other vars on other scripts. At least now they are declarative to *this* script.\r\n- Functions are now local to the script.\r\n- Changed some functions scope\r\n- Reorganizing functions and moved another one to the public scope.\r\n- Implemented autogroup","package":"vim-git-branch-info.zip","4":"vim-git-branch-info.zip","src_id":"12680","5":"12680","creation_date":"1269285288","6":"1269285288"},{"0":"2258","vim_version":"7.0","1":"7.0","script_version":"0.1.4","2":"0.1.4","version_comment":"Allow for branch names with slashs in them. Thanks to Thomas Adam.","3":"Allow for branch names with slashs in them. Thanks to Thomas Adam.","package":"vim-git-branch-info.zip","4":"vim-git-branch-info.zip","src_id":"11525","5":"11525","creation_date":"1255446340","6":"1255446340"},{"0":"2258","vim_version":"7.0","1":"7.0","script_version":"0.1.3","2":"0.1.3","version_comment":"Fixes bug that prevents git-buffer-info from finding the git-dir. ","3":"Fixes bug that prevents git-buffer-info from finding the git-dir. ","package":"vim-git-branch-info.zip","4":"vim-git-branch-info.zip","src_id":"10711","5":"10711","creation_date":"1243891577","6":"1243891577"},{"0":"2258","vim_version":"7.0","1":"7.0","script_version":"0.1.2","2":"0.1.2","version_comment":"Seems that there were a little bug when loading the file from some other plugin","3":"Seems that there were a little bug when loading the file from some other plugin","package":"vim-git-branch-info.zip","4":"vim-git-branch-info.zip","src_id":"10593","5":"10593","creation_date":"1242355250","6":"1242355250"},{"0":"2258","vim_version":"7.0","1":"7.0","script_version":"0.1.1","2":"0.1.1","version_comment":"Changed the checking about the original branche while saving a file as a optional - and not default - option.","3":"Changed the checking about the original branche while saving a file as a optional - and not default - option.","package":"vim-git-branch-info.zip","4":"vim-git-branch-info.zip","src_id":"10592","5":"10592","creation_date":"1242350825","6":"1242350825"},{"0":"2258","vim_version":"6.0","1":"6.0","script_version":"0.1.0","2":"0.1.0","version_comment":"Fixed the .git relative path, thanks to rtwo for the patch.","3":"Fixed the .git relative path, thanks to rtwo for the patch.","package":"vim-git-branch-info.zip","4":"vim-git-branch-info.zip","src_id":"9329","5":"9329","creation_date":"1223644789","6":"1223644789"},{"0":"2258","vim_version":"7.0","1":"7.0","script_version":"0.0.9","2":"0.0.9","version_comment":"There were a bug when rebasing. On this situation HEAD just have a hash and not the information about the branches the plugin looks for. Thanks for Joachim Bargsten for warning me about this.\r\nI made a double check on the HEAD file. If there is not the information the script wants, a message about the condition is returned. If something also \"explodes\" there, there is a try\/catch block.\r\nIf detect this rebase\/merge\/bisect situation, the file will be always saved without the branch verification.","3":"There were a bug when rebasing. On this situation HEAD just have a hash and not the information about the branches the plugin looks for. Thanks for Joachim Bargsten for warning me about this.\r\nI made a double check on the HEAD file. If there is not the information the script wants, a message about the condition is returned. If something also \"explodes\" there, there is a try\/catch block.\r\nIf detect this rebase\/merge\/bisect situation, the file will be always saved without the branch verification.","package":"vim-git-branch-info.zip","4":"vim-git-branch-info.zip","src_id":"8945","5":"8945","creation_date":"1215942381","6":"1215942381"},{"0":"2258","vim_version":"7.0","1":"7.0","script_version":"0.0.8","2":"0.0.8","version_comment":"Argh, another bug fixed. When trying to write to a file different from the current one, it was not saved. That happened because I was trying to save the file without it's name, presuming if we tell to save to another file with :w the name was correct.It was fixed using expand(\"<afile>\"). Btw, there was another bug when trying to save to an existing file and need to use the bang (!) with write. It was fixed checking if a bang command was used and executing the bang version if needed.","3":"Argh, another bug fixed. When trying to write to a file different from the current one, it was not saved. That happened because I was trying to save the file without it's name, presuming if we tell to save to another file with :w the name was correct.It was fixed using expand(\"<afile>\"). Btw, there was another bug when trying to save to an existing file and need to use the bang (!) with write. It was fixed checking if a bang command was used and executing the bang version if needed.","package":"vim-git-branch-info.zip","4":"vim-git-branch-info.zip","src_id":"8854","5":"8854","creation_date":"1214458728","6":"1214458728"},{"0":"2258","vim_version":"7.0","1":"7.0","script_version":"0.0.7","2":"0.0.7","version_comment":"Found a way of detecting if the file needs to be written. If it's a normal \r\nbuffer, it is written, if not, the GitBranchInfoWriteCheck() skip it. \r\nUseful with other scripts that use temporary buffers like VCSCommand.","3":"Found a way of detecting if the file needs to be written. If it's a normal \r\nbuffer, it is written, if not, the GitBranchInfoWriteCheck() skip it. \r\nUseful with other scripts that use temporary buffers like VCSCommand.","package":"vim-git-branch-info.zip","4":"vim-git-branch-info.zip","src_id":"8826","5":"8826","creation_date":"1213895908","6":"1213895908"},{"0":"2258","vim_version":"7.0","1":"7.0","script_version":"0.0.6","2":"0.0.6","version_comment":"Extra check on permissions of the Git directory.","3":"Extra check on permissions of the Git directory.","package":"vim-git-branch-info.zip","4":"vim-git-branch-info.zip","src_id":"8818","5":"8818","creation_date":"1213690006","6":"1213690006"},{"0":"2258","vim_version":"7.0","1":"7.0","script_version":"0.0.5","2":"0.0.5","version_comment":"Removed remote branches on fetch menu, fetch just the remote repository \r\nreference.","3":"Removed remote branches on fetch menu, fetch just the remote repository \r\nreference.","package":"vim-git-branch-info.zip","4":"vim-git-branch-info.zip","src_id":"8800","5":"8800","creation_date":"1213337051","6":"1213337051"},{"0":"2258","vim_version":"7.0","1":"7.0","script_version":"0.0.4","2":"0.0.4","version_comment":"Some label changes and the fetch remote branches feature. \r\nAdded some variables to store the current buffer Git dir and the branch where the buffer was loaded.\r\nAdded autocmd's to fill the variables above.\r\nAdded an alert when the branch where the file is being saved is different from where it was loaded.\r\nIf the current buffer is not on the local dir, make a CD to the buffer dir when need to make a checkout or a fetch.\r\nChanged to ask if we want to save a file loaded from one branch into another branch.","3":"Some label changes and the fetch remote branches feature. \r\nAdded some variables to store the current buffer Git dir and the branch where the buffer was loaded.\r\nAdded autocmd's to fill the variables above.\r\nAdded an alert when the branch where the file is being saved is different from where it was loaded.\r\nIf the current buffer is not on the local dir, make a CD to the buffer dir when need to make a checkout or a fetch.\r\nChanged to ask if we want to save a file loaded from one branch into another branch.","package":"vim-git-branch-info.zip","4":"vim-git-branch-info.zip","src_id":"8785","5":"8785","creation_date":"1213165727","6":"1213165727"},{"0":"2258","vim_version":"7.0","1":"7.0","script_version":"0.0.3","2":"0.0.3","version_comment":"Added a menu system with some features for branch changing.","3":"Added a menu system with some features for branch changing.","package":"vim-git-branch-info.zip","4":"vim-git-branch-info.zip","src_id":"8764","5":"8764","creation_date":"1212745724","6":"1212745724"},{"0":"2258","vim_version":"7.0","1":"7.0","script_version":"0.0.2","2":"0.0.2","version_comment":"- Changed version number.\r\n- The previous version performance SUCKED a lot. I removed the system() \r\ncall to Vim internal file functions and seems that now things are really faster.\r\n  - Removed the g:git_branch_status_all option and changed to g:git_branch_status_head_current, who just shows the current head branch. This can make things faster because if does not seeks for the other branches and  just show the current branch with GitBranchInfoString.\r\n- Added the feature to find the remote branches (which we're not using right now but I have some plans) and the option g:git_branch_status_ignore_remotes to avoid this feature if you don't need it.\r\n- Fixed some errors on the statusline samples using GitBranchInfoTokens.\r\n- Created the variable to handle the remote list on GitBranchInfoString.\r\n- Changed the way GitBranchInfoString returns the info string, based on the configuration chosen.\r\n- GitBranchInfoTokens() was fully rewritten because of the previous poor performance.","3":"- Changed version number.\r\n- The previous version performance SUCKED a lot. I removed the system() \r\ncall to Vim internal file functions and seems that now things are really faster.\r\n  - Removed the g:git_branch_status_all option and changed to g:git_branch_status_head_current, who just shows the current head branch. This can make things faster because if does not seeks for the other branches and  just show the current branch with GitBranchInfoString.\r\n- Added the feature to find the remote branches (which we're not using right now but I have some plans) and the option g:git_branch_status_ignore_remotes to avoid this feature if you don't need it.\r\n- Fixed some errors on the statusline samples using GitBranchInfoTokens.\r\n- Created the variable to handle the remote list on GitBranchInfoString.\r\n- Changed the way GitBranchInfoString returns the info string, based on the configuration chosen.\r\n- GitBranchInfoTokens() was fully rewritten because of the previous poor performance.","package":"vim-git-branch-info.zip","4":"vim-git-branch-info.zip","src_id":"8758","5":"8758","creation_date":"1212673551","6":"1212673551"},{"0":"2258","vim_version":"7.0","1":"7.0","script_version":"0.0.1","2":"0.0.1","version_comment":"Initial upload","3":"Initial upload","package":"vim-git-branch-info.zip","4":"vim-git-branch-info.zip","src_id":"8756","5":"8756","creation_date":"1212648563","6":"1212648563"}]},"2257":{"script_id":"2257","0":"2257","script_name":"bpel.vim","1":"bpel.vim","script_type":"syntax","2":"syntax","summary":"BPEL, the Business Process Execution Language","3":"BPEL, the Business Process Execution Language","description":"Very simple syntax definition highlighting the BPEL structure and activities.","4":"Very simple syntax definition highlighting the BPEL structure and activities.","install_details":"","5":"","first_name":"Josef","6":"Josef","last_name":"Spillner","7":"Spillner","releases":[{"0":"2257","vim_version":"6.0","1":"6.0","script_version":"0.3","2":"0.3","version_comment":"Special highlighting for BPEL extensions, and generally better coverage of syntax elements and activities.","3":"Special highlighting for BPEL extensions, and generally better coverage of syntax elements and activities.","package":"bpel.vim","4":"bpel.vim","src_id":"10400","5":"10400","creation_date":"1239784882","6":"1239784882"},{"0":"2257","vim_version":"6.0","1":"6.0","script_version":"0.3","2":"0.3","version_comment":"Special highlighting for BPEL extensions, and generally better coverage of syntax elements and activities.","3":"Special highlighting for BPEL extensions, and generally better coverage of syntax elements and activities.","package":"bpel.vim","4":"bpel.vim","src_id":"10399","5":"10399","creation_date":"1239784835","6":"1239784835"},{"0":"2257","vim_version":"6.0","1":"6.0","script_version":"0.3","2":"0.3","version_comment":"Special highlighting for BPEL extensions, and generally better coverage of syntax elements and activities.","3":"Special highlighting for BPEL extensions, and generally better coverage of syntax elements and activities.","package":"bpel.vim","4":"bpel.vim","src_id":"10398","5":"10398","creation_date":"1239784813","6":"1239784813"},{"0":"2257","vim_version":"6.0","1":"6.0","script_version":"0.3","2":"0.3","version_comment":"Special highlighting for BPEL extensions, and generally better coverage of syntax elements and activities.","3":"Special highlighting for BPEL extensions, and generally better coverage of syntax elements and activities.","package":"bpel.vim","4":"bpel.vim","src_id":"10397","5":"10397","creation_date":"1239784762","6":"1239784762"},{"0":"2257","vim_version":"6.0","1":"6.0","script_version":"0.3","2":"0.3","version_comment":"Special highlighting for BPEL extensions, and generally better coverage of syntax elements and activities.","3":"Special highlighting for BPEL extensions, and generally better coverage of syntax elements and activities.","package":"bpel.vim","4":"bpel.vim","src_id":"10396","5":"10396","creation_date":"1239784729","6":"1239784729"},{"0":"2257","vim_version":"6.0","1":"6.0","script_version":"0.2","2":"0.2","version_comment":"Addition of a couple of BPEL 2.0 syntax elements and activities, e.g. import, forEach and exit","3":"Addition of a couple of BPEL 2.0 syntax elements and activities, e.g. import, forEach and exit","package":"bpel.vim","4":"bpel.vim","src_id":"8893","5":"8893","creation_date":"1215391968","6":"1215391968"},{"0":"2257","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"bpel.vim","4":"bpel.vim","src_id":"8753","5":"8753","creation_date":"1212569290","6":"1212569290"}]},"2256":{"script_id":"2256","0":"2256","script_name":"dark ruby","1":"dark ruby","script_type":"color scheme","2":"color scheme","summary":"A dark-background color scheme.","3":"A dark-background color scheme.","description":"A dark-background color scheme.\r\n\r\nPreview: http:\/\/priit.mx.ee\/files\/dark-ruby.png\r\n\r\nNB! It's REALLY alfa release and I'm going to improve it on the way (it might take ages :-). You are welcome to fork and improve it at gitorious.org: http:\/\/gitorious.com\/vim-color-scheme-dark-ruby \r\n","4":"A dark-background color scheme.\r\n\r\nPreview: http:\/\/priit.mx.ee\/files\/dark-ruby.png\r\n\r\nNB! It's REALLY alfa release and I'm going to improve it on the way (it might take ages :-). You are welcome to fork and improve it at gitorious.org: http:\/\/gitorious.com\/vim-color-scheme-dark-ruby \r\n","install_details":"Save it to: ~\/.vim\/colors\/\r\nTurn xterm-256 colors on at your ~\/.vimrc: set term=xterm-256color\r\n\r\nEnamble 256 colors on Ubuntu:\r\nsudo apt-get install ncurses-term\r\n","5":"Save it to: ~\/.vim\/colors\/\r\nTurn xterm-256 colors on at your ~\/.vimrc: set term=xterm-256color\r\n\r\nEnamble 256 colors on Ubuntu:\r\nsudo apt-get install ncurses-term\r\n","first_name":"Priit","6":"Priit","last_name":"Tamboom","7":"Tamboom","releases":[{"0":"2256","vim_version":"7.0","1":"7.0","script_version":"0.2","2":"0.2","version_comment":"Comment color a bit more lighter","3":"Comment color a bit more lighter","package":"dark-ruby.vim","4":"dark-ruby.vim","src_id":"13291","5":"13291","creation_date":"1278239201","6":"1278239201"},{"0":"2256","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"dark-ruby.vim","4":"dark-ruby.vim","src_id":"8750","5":"8750","creation_date":"1212542104","6":"1212542104"}]},"2255":{"script_id":"2255","0":"2255","script_name":"buffergrep","1":"buffergrep","script_type":"utility","2":"utility","summary":"Grep buffers, not files","3":"Grep buffers, not files","description":"Searches for strings in open buffers.  Instead of supplying a filename wildcard to direct the search, the grep command will search in open buffers which may or may not be represented by a file on the disk.  Moreover, since buffers are searched, changes that have not been saved to disk are scanned.  Unlisted, quickfix, and help buffers are skipped.\r\n\r\nEach grep command uses the same syntax as the builtin :vimgrep and :lvimgrep commands.  Results are displayed in the quickfix list.\r\n\r\nThe following commands are defined:\r\n\r\nBgrep - searches all buffers listed with the :buffers command, skipping over unlisted, quickfix, and help buffers.  Analagous to :bufdo.\r\nAgrep - searches all buffers listed with the :args command.  Analagous to :argdo.\r\nWgrep - searches all buffers visible on the screen (current tab page only).  Analagous to :windo.\r\nTgrep - searches all buffers open on any tabpage.  Analagous to :tabdo.\r\n\r\nExample:\r\n\r\nBgrep \/jhonka\/  \"find string 'jhonka' in all loaded buffers.\r\nWgrep |foo|j  \"find string 'foo' in all buffers currently on the screen, but don't jump to first match.\r\nTgrep !bar!g  \"find string 'bar' in all buffers visible in all tabpages, and list each occurance of 'bar', not just the first one on a line.\r\nAgrep baz    \"find string 'baz' in all buffers from the args list; specifying the pattern this way means you can't use flags.\r\n\r\nOf course, the argument isn't just a literal string, it is a regular expression.  You man use any valid Vim regular expression atoms in your search.","4":"Searches for strings in open buffers.  Instead of supplying a filename wildcard to direct the search, the grep command will search in open buffers which may or may not be represented by a file on the disk.  Moreover, since buffers are searched, changes that have not been saved to disk are scanned.  Unlisted, quickfix, and help buffers are skipped.\r\n\r\nEach grep command uses the same syntax as the builtin :vimgrep and :lvimgrep commands.  Results are displayed in the quickfix list.\r\n\r\nThe following commands are defined:\r\n\r\nBgrep - searches all buffers listed with the :buffers command, skipping over unlisted, quickfix, and help buffers.  Analagous to :bufdo.\r\nAgrep - searches all buffers listed with the :args command.  Analagous to :argdo.\r\nWgrep - searches all buffers visible on the screen (current tab page only).  Analagous to :windo.\r\nTgrep - searches all buffers open on any tabpage.  Analagous to :tabdo.\r\n\r\nExample:\r\n\r\nBgrep \/jhonka\/  \"find string 'jhonka' in all loaded buffers.\r\nWgrep |foo|j  \"find string 'foo' in all buffers currently on the screen, but don't jump to first match.\r\nTgrep !bar!g  \"find string 'bar' in all buffers visible in all tabpages, and list each occurance of 'bar', not just the first one on a line.\r\nAgrep baz    \"find string 'baz' in all buffers from the args list; specifying the pattern this way means you can't use flags.\r\n\r\nOf course, the argument isn't just a literal string, it is a regular expression.  You man use any valid Vim regular expression atoms in your search.","install_details":"Copy into $HOME\/.vim\/plugins","5":"Copy into $HOME\/.vim\/plugins","first_name":"erik","6":"erik","last_name":"falor","7":"falor","releases":[{"0":"2255","vim_version":"7.0","1":"7.0","script_version":"1.1","2":"1.1","version_comment":"Bugfixes: TabSearch now reaches all files,\r\nRegex delimiter around arguments now optional\r\n","3":"Bugfixes: TabSearch now reaches all files,\r\nRegex delimiter around arguments now optional\r\n","package":"buffergrep.vim","4":"buffergrep.vim","src_id":"8967","5":"8967","creation_date":"1216290073","6":"1216290073"},{"0":"2255","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"buffergrep.vim","4":"buffergrep.vim","src_id":"8746","5":"8746","creation_date":"1212409347","6":"1212409347"}]},"2254":{"script_id":"2254","0":"2254","script_name":"musicbox.vim","1":"musicbox.vim","script_type":"utility","2":"utility","summary":"musicbox allow you to play music files in vim","3":"musicbox allow you to play music files in vim","description":"musicbox is a vim plugin allowing to play mp3,ogg,wma... files in vim. It's a python plugin requiring gstreamer installed (alpha version, code GPL)","4":"musicbox is a vim plugin allowing to play mp3,ogg,wma... files in vim. It's a python plugin requiring gstreamer installed (alpha version, code GPL)","install_details":"copy musicbox.vim in your plugin directory\r\n(~\/.vim\/plugin)\r\n Then, to try the plugin, just do :\r\n launch vim\r\n :tabe playlist.txt\r\n :r !ls -d \/home\/user\/music\/album\/*\r\n  then press c-h to play file under the cursor\r\n  c-j to pause\r\n  c-k to stop \r\n  c-n to play next file in list\r\n  c-p to play previous file in list\r\n","5":"copy musicbox.vim in your plugin directory\r\n(~\/.vim\/plugin)\r\n Then, to try the plugin, just do :\r\n launch vim\r\n :tabe playlist.txt\r\n :r !ls -d \/home\/user\/music\/album\/*\r\n  then press c-h to play file under the cursor\r\n  c-j to pause\r\n  c-k to stop \r\n  c-n to play next file in list\r\n  c-p to play previous file in list\r\n","first_name":"nicolas","6":"nicolas","last_name":"bigeard","7":"bigeard","releases":[{"0":"2254","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"musicbox.vim","4":"musicbox.vim","src_id":"8738","5":"8738","creation_date":"1211895555","6":"1211895555"}]},"2253":{"script_id":"2253","0":"2253","script_name":"railstab.vim","1":"railstab.vim","script_type":"utility","2":"utility","summary":"Retabbing hacks extracted from rails.vim","3":"Retabbing hacks extracted from rails.vim","description":"This plugin contains the retabbing feature from rails.vim that will be removed in a forthcoming version.  I have provided this plugin as a courtesy to anyone actually relying on it and recommend that potential new users stay away.","4":"This plugin contains the retabbing feature from rails.vim that will be removed in a forthcoming version.  I have provided this plugin as a courtesy to anyone actually relying on it and recommend that potential new users stay away.","install_details":"Install in ~\/.vim\/plugin and set the g:rails_tabstop option to the desired value.\r\n\r\nlet g:rails_tabstop = 4","5":"Install in ~\/.vim\/plugin and set the g:rails_tabstop option to the desired value.\r\n\r\nlet g:rails_tabstop = 4","first_name":"Tim","6":"Tim","last_name":"Pope","7":"Pope","releases":[{"0":"2253","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"railstab.vim","4":"railstab.vim","src_id":"8730","5":"8730","creation_date":"1211826754","6":"1211826754"}]},"2252":{"script_id":"2252","0":"2252","script_name":"publish.vim","1":"publish.vim","script_type":"utility","2":"utility","summary":"Publish hyperlinked, highlighted source code using Vim, 2html.vim and rsync","3":"Publish hyperlinked, highlighted source code using Vim, 2html.vim and rsync","description":"This plug-in uses the 2html.vim script included with Vim's runtime files to publish a collection of syntax highlighted files as HTML documents and then replaces identifiers such as function and variable names in the HTML output with hyper links (based on available tags as generated by Exuberant Ctags). The result is a directory (tree) of syntax highlighted, interlinked HTML documents. I've published the plug-in's source code as a demonstration at http:\/\/peterodding.com\/code\/vim\/profile\/plugin\/publish.vim. For more information about the plug-in please refer to its homepage or the project page on GitHub:\r\n\r\n\u00e2\u0080\u00a2 http:\/\/peterodding.com\/code\/vim\/publish\/\r\n\u00e2\u0080\u00a2 http:\/\/github.com\/xolox\/vim-publish\r\n\r\nIf you have questions, bug reports, suggestions, etc. the author can be contacted at peter@peterodding.com. If you like this plug-in please vote for it below!","4":"This plug-in uses the 2html.vim script included with Vim's runtime files to publish a collection of syntax highlighted files as HTML documents and then replaces identifiers such as function and variable names in the HTML output with hyper links (based on available tags as generated by Exuberant Ctags). The result is a directory (tree) of syntax highlighted, interlinked HTML documents. I've published the plug-in's source code as a demonstration at http:\/\/peterodding.com\/code\/vim\/profile\/plugin\/publish.vim. For more information about the plug-in please refer to its homepage or the project page on GitHub:\r\n\r\n\u00e2\u0080\u00a2 http:\/\/peterodding.com\/code\/vim\/publish\/\r\n\u00e2\u0080\u00a2 http:\/\/github.com\/xolox\/vim-publish\r\n\r\nIf you have questions, bug reports, suggestions, etc. the author can be contacted at peter@peterodding.com. If you like this plug-in please vote for it below!","install_details":"Unzip the most recent ZIP archive file (see below) inside your Vim profile directory (usually this is \"~\/.vim\" on UNIX and \"%USERPROFILE%\\vimfiles\" on Windows), restart Vim and execute the command \":helptags ~\/.vim\/doc\" (use \":helptags ~\\vimfiles\\doc\" instead on Windows).\r\n\r\nAs an example we'll publish the plug-in using itself. First create a tags file that contains entries for the files you want to publish using a shell command such as:\r\n\r\n    ctags -Rf ~\/.publish_tags ~\/.vim\/\r\n\r\nIf this doesn't work because \"ctags\" isn't installed you can download it from the Exuberant Ctags homepage http:\/\/ctags.sourceforge.net\/ or if you're running Debian\/Ubuntu you can install it by executing the following shell command:\r\n\r\n    sudo apt-get install exuberant-ctags\r\n\r\nThe plug-in needs an up-to-date tags file so that it can create hyper links between the published files. Now start Vim and write a script that registers the tags file you just created and calls the function Publish() as follows:\r\n\r\n    set tags=~\/.publish_tags\r\n    let sources = '\/home\/peter\/.vim'\r\n    let target = 'sftp:\/\/peterodding.com\/code\/vim\/profile'\r\n    call Publish(sources, target, [\r\n        \\ 'autoload\/xolox\/escape.vim',\r\n        \\ 'autoload\/xolox\/path.vim',\r\n        \\ 'autoload\/publish.vim',\r\n        \\ 'plugin\/publish.vim',\r\n        \\ ])\r\n\r\nChange the \"sources\" and \"target\" variables to reflect your situation, save the script as \"~\/publish_test.vim\" and execute it in Vim by typing \":source ~\/publish_test.vim\" (without the quotes) and pressing Enter↵. If everything goes well Vim will be busy for a moment and after that you will find a bunch of syntax highlighted, interlinked HTML documents in the target directory!","5":"Unzip the most recent ZIP archive file (see below) inside your Vim profile directory (usually this is \"~\/.vim\" on UNIX and \"%USERPROFILE%\\vimfiles\" on Windows), restart Vim and execute the command \":helptags ~\/.vim\/doc\" (use \":helptags ~\\vimfiles\\doc\" instead on Windows).\r\n\r\nAs an example we'll publish the plug-in using itself. First create a tags file that contains entries for the files you want to publish using a shell command such as:\r\n\r\n    ctags -Rf ~\/.publish_tags ~\/.vim\/\r\n\r\nIf this doesn't work because \"ctags\" isn't installed you can download it from the Exuberant Ctags homepage http:\/\/ctags.sourceforge.net\/ or if you're running Debian\/Ubuntu you can install it by executing the following shell command:\r\n\r\n    sudo apt-get install exuberant-ctags\r\n\r\nThe plug-in needs an up-to-date tags file so that it can create hyper links between the published files. Now start Vim and write a script that registers the tags file you just created and calls the function Publish() as follows:\r\n\r\n    set tags=~\/.publish_tags\r\n    let sources = '\/home\/peter\/.vim'\r\n    let target = 'sftp:\/\/peterodding.com\/code\/vim\/profile'\r\n    call Publish(sources, target, [\r\n        \\ 'autoload\/xolox\/escape.vim',\r\n        \\ 'autoload\/xolox\/path.vim',\r\n        \\ 'autoload\/publish.vim',\r\n        \\ 'plugin\/publish.vim',\r\n        \\ ])\r\n\r\nChange the \"sources\" and \"target\" variables to reflect your situation, save the script as \"~\/publish_test.vim\" and execute it in Vim by typing \":source ~\/publish_test.vim\" (without the quotes) and pressing Enter↵. If everything goes well Vim will be busy for a moment and after that you will find a bunch of syntax highlighted, interlinked HTML documents in the target directory!","first_name":"Peter","6":"Peter","last_name":"Odding","7":"Odding","releases":[{"0":"2252","vim_version":"7.0","1":"7.0","script_version":"1.7.14","2":"1.7.14","version_comment":" \u00e2\u0080\u00a2 Remove compatibility checking of miscellaneous scripts:\n   http:\/\/github.com\/xolox\/vim-publish\/commit\/fecbb5e\n\n \u00e2\u0080\u00a2 Cleaned up old miscellaneous scripts:\n   http:\/\/github.com\/xolox\/vim-publish\/commit\/cc0c218\n\n \u00e2\u0080\u00a2 Document vim-misc as external dependency:\n   http:\/\/github.com\/xolox\/vim-publish\/commit\/4cb3c4c\n\n \u00e2\u0080\u00a2 Make sure vim-misc is installed, politely complain if it isn't:\n   http:\/\/github.com\/xolox\/vim-publish\/commit\/4aa630e","3":" \u00e2\u0080\u00a2 Remove compatibility checking of miscellaneous scripts:\n   http:\/\/github.com\/xolox\/vim-publish\/commit\/fecbb5e\n\n \u00e2\u0080\u00a2 Cleaned up old miscellaneous scripts:\n   http:\/\/github.com\/xolox\/vim-publish\/commit\/cc0c218\n\n \u00e2\u0080\u00a2 Document vim-misc as external dependency:\n   http:\/\/github.com\/xolox\/vim-publish\/commit\/4cb3c4c\n\n \u00e2\u0080\u00a2 Make sure vim-misc is installed, politely complain if it isn't:\n   http:\/\/github.com\/xolox\/vim-publish\/commit\/4aa630e","package":"publish.zip","4":"publish.zip","src_id":"20685","5":"20685","creation_date":"1376940741","6":"1376940741"},{"0":"2252","vim_version":"7.0","1":"7.0","script_version":"1.7.13","2":"1.7.13","version_comment":" \u00e2\u0080\u00a2 Updated miscellaneous scripts:\n   http:\/\/github.com\/xolox\/vim-publish\/commit\/47adaca","3":" \u00e2\u0080\u00a2 Updated miscellaneous scripts:\n   http:\/\/github.com\/xolox\/vim-publish\/commit\/47adaca","package":"publish.zip","4":"publish.zip","src_id":"20181","5":"20181","creation_date":"1369054239","6":"1369054239"},{"0":"2252","vim_version":"7.0","1":"7.0","script_version":"1.7.12","2":"1.7.12","version_comment":" \u00e2\u0080\u00a2 Updated miscellaneous scripts:\n   http:\/\/github.com\/xolox\/vim-publish\/commit\/89cfda3","3":" \u00e2\u0080\u00a2 Updated miscellaneous scripts:\n   http:\/\/github.com\/xolox\/vim-publish\/commit\/89cfda3","package":"publish.zip","4":"publish.zip","src_id":"20169","5":"20169","creation_date":"1369003088","6":"1369003088"},{"0":"2252","vim_version":"7.0","1":"7.0","script_version":"1.7.11","2":"1.7.11","version_comment":" \u00e2\u0080\u00a2 Updated miscellaneous scripts:\n   http:\/\/github.com\/xolox\/vim-publish\/commit\/ace88ae\n   http:\/\/github.com\/xolox\/vim-publish\/commit\/9c88b0e","3":" \u00e2\u0080\u00a2 Updated miscellaneous scripts:\n   http:\/\/github.com\/xolox\/vim-publish\/commit\/ace88ae\n   http:\/\/github.com\/xolox\/vim-publish\/commit\/9c88b0e","package":"publish.zip","4":"publish.zip","src_id":"20123","5":"20123","creation_date":"1368481186","6":"1368481186"},{"0":"2252","vim_version":"7.0","1":"7.0","script_version":"1.7.10","2":"1.7.10","version_comment":" \u00e2\u0080\u00a2 Updated miscellaneous scripts:\n   http:\/\/github.com\/xolox\/vim-publish\/commit\/3ef4495","3":" \u00e2\u0080\u00a2 Updated miscellaneous scripts:\n   http:\/\/github.com\/xolox\/vim-publish\/commit\/3ef4495","package":"publish.zip","4":"publish.zip","src_id":"20006","5":"20006","creation_date":"1367487475","6":"1367487475"},{"0":"2252","vim_version":"7.0","1":"7.0","script_version":"1.7.9","2":"1.7.9","version_comment":" \u00e2\u0080\u00a2 Updated miscellaneous scripts:\n   http:\/\/github.com\/xolox\/vim-publish\/commit\/24c2a1b","3":" \u00e2\u0080\u00a2 Updated miscellaneous scripts:\n   http:\/\/github.com\/xolox\/vim-publish\/commit\/24c2a1b","package":"publish.zip","4":"publish.zip","src_id":"19958","5":"19958","creation_date":"1367159239","6":"1367159239"},{"0":"2252","vim_version":"7.0","1":"7.0","script_version":"1.7.8","2":"1.7.8","version_comment":" \u00e2\u0080\u00a2 Make compatibility with miscellaneous scripts explicit:\n   http:\/\/github.com\/xolox\/vim-publish\/commit\/6e3ba5c","3":" \u00e2\u0080\u00a2 Make compatibility with miscellaneous scripts explicit:\n   http:\/\/github.com\/xolox\/vim-publish\/commit\/6e3ba5c","package":"publish.zip","4":"publish.zip","src_id":"19872","5":"19872","creation_date":"1366502953","6":"1366502953"},{"0":"2252","vim_version":"7.0","1":"7.0","script_version":"1.7.7","2":"1.7.7","version_comment":" \u00e2\u0080\u00a2 Updated miscellaneous scripts:\n   http:\/\/github.com\/xolox\/vim-publish\/commit\/3025ff5\n   http:\/\/github.com\/xolox\/vim-publish\/commit\/5ddefd0\n   http:\/\/github.com\/xolox\/vim-publish\/commit\/9b4c774","3":" \u00e2\u0080\u00a2 Updated miscellaneous scripts:\n   http:\/\/github.com\/xolox\/vim-publish\/commit\/3025ff5\n   http:\/\/github.com\/xolox\/vim-publish\/commit\/5ddefd0\n   http:\/\/github.com\/xolox\/vim-publish\/commit\/9b4c774","package":"publish.zip","4":"publish.zip","src_id":"16970","5":"16970","creation_date":"1322268007","6":"1322268007"},{"0":"2252","vim_version":"7.0","1":"7.0","script_version":"1.7.6","2":"1.7.6","version_comment":" \u00e2\u0080\u00a2 Updated miscellaneous scripts:\n   http:\/\/github.com\/xolox\/vim-publish\/commit\/ca5f8f4","3":" \u00e2\u0080\u00a2 Updated miscellaneous scripts:\n   http:\/\/github.com\/xolox\/vim-publish\/commit\/ca5f8f4","package":"publish.zip","4":"publish.zip","src_id":"16926","5":"16926","creation_date":"1321910711","6":"1321910711"},{"0":"2252","vim_version":"7.0","1":"7.0","script_version":"1.7.5","2":"1.7.5","version_comment":" \u00e2\u0080\u00a2 Updated miscellaneous scripts:\n   http:\/\/github.com\/xolox\/vim-publish\/commit\/8f196b6","3":" \u00e2\u0080\u00a2 Updated miscellaneous scripts:\n   http:\/\/github.com\/xolox\/vim-publish\/commit\/8f196b6","package":"publish.zip","4":"publish.zip","src_id":"16580","5":"16580","creation_date":"1316994711","6":"1316994711"},{"0":"2252","vim_version":"7.0","1":"7.0","script_version":"1.7.4","2":"1.7.4","version_comment":" \u00e2\u0080\u00a2 Move version variable to autoload script, include in every message:\n   http:\/\/github.com\/xolox\/vim-publish\/commit\/f0d2b02\n\n \u00e2\u0080\u00a2 Updated miscellaneous scripts","3":" \u00e2\u0080\u00a2 Move version variable to autoload script, include in every message:\n   http:\/\/github.com\/xolox\/vim-publish\/commit\/f0d2b02\n\n \u00e2\u0080\u00a2 Updated miscellaneous scripts","package":"publish.zip","4":"publish.zip","src_id":"16458","5":"16458","creation_date":"1315145092","6":"1315145092"},{"0":"2252","vim_version":"7.0","1":"7.0","script_version":"1.7.1","2":"1.7.1","version_comment":" \u00e2\u0080\u00a2 Bug fix: Avoid Vim's hit-enter prompt:\r\n   http:\/\/github.com\/xolox\/vim-publish\/commit\/7a2705cbdcefa12116f6ca007af9683729c2b37a\r\n\r\n \u00e2\u0080\u00a2 Instrumented plug-in with xolox#timer#* calls:\r\n   http:\/\/github.com\/xolox\/vim-publish\/commit\/514a5f7be3b5d09dc8a944fd594ce1fbd0e17e1b\r\n\r\n \u00e2\u0080\u00a2 Proper HTML encoding, foolproof publish#customize_html():\r\n   http:\/\/github.com\/xolox\/vim-publish\/commit\/be773a134cf404723cc463ab034eaf0b26f7d279\r\n\r\n \u00e2\u0080\u00a2 Bug fix: Make 2html ignore text folding:\r\n   http:\/\/github.com\/xolox\/vim-publish\/commit\/892be723e17dbfd21bec0d72d600519e26e0f6c1\r\n\r\n \u00e2\u0080\u00a2 Bug fix: Proper escaping in pattern_to_lnum():\r\n   http:\/\/github.com\/xolox\/vim-publish\/commit\/43c57b7a8b2d5b030fc3c539df293d0bb350840b\r\n\r\n \u00e2\u0080\u00a2 Bug fix: Proper escaping in create_subst_cmd() to avoid E33:\r\n   http:\/\/github.com\/xolox\/vim-publish\/commit\/4fa75be69245eb5723279793e4a587bb3848aa6c\r\n\r\n \u00e2\u0080\u00a2 Bug fix for publish#html_encode():\r\n   http:\/\/github.com\/xolox\/vim-publish\/commit\/5df4c3d750654a330e077eb96a781c9b8d4dab7c\r\n\r\n \u00e2\u0080\u00a2 Simplified tags -> hyperlinks conversion hack:\r\n   http:\/\/github.com\/xolox\/vim-publish\/commit\/459b8293a2a85885872603765699a210fe72fb74\r\n\r\n \u00e2\u0080\u00a2 Smarter integration with easytags.vim:\r\n   http:\/\/github.com\/xolox\/vim-publish\/commit\/be98f4328bb631cd4c67d8951ff7c413b7cb6355\r\n\r\n \u00e2\u0080\u00a2 Fixed easytags#update() to overcome argument limit:\r\n   http:\/\/github.com\/xolox\/vim-publish\/commit\/87b0305bd27d4ee3715790cddc76cc2cfead7c14","3":" \u00e2\u0080\u00a2 Bug fix: Avoid Vim's hit-enter prompt:\r\n   http:\/\/github.com\/xolox\/vim-publish\/commit\/7a2705cbdcefa12116f6ca007af9683729c2b37a\r\n\r\n \u00e2\u0080\u00a2 Instrumented plug-in with xolox#timer#* calls:\r\n   http:\/\/github.com\/xolox\/vim-publish\/commit\/514a5f7be3b5d09dc8a944fd594ce1fbd0e17e1b\r\n\r\n \u00e2\u0080\u00a2 Proper HTML encoding, foolproof publish#customize_html():\r\n   http:\/\/github.com\/xolox\/vim-publish\/commit\/be773a134cf404723cc463ab034eaf0b26f7d279\r\n\r\n \u00e2\u0080\u00a2 Bug fix: Make 2html ignore text folding:\r\n   http:\/\/github.com\/xolox\/vim-publish\/commit\/892be723e17dbfd21bec0d72d600519e26e0f6c1\r\n\r\n \u00e2\u0080\u00a2 Bug fix: Proper escaping in pattern_to_lnum():\r\n   http:\/\/github.com\/xolox\/vim-publish\/commit\/43c57b7a8b2d5b030fc3c539df293d0bb350840b\r\n\r\n \u00e2\u0080\u00a2 Bug fix: Proper escaping in create_subst_cmd() to avoid E33:\r\n   http:\/\/github.com\/xolox\/vim-publish\/commit\/4fa75be69245eb5723279793e4a587bb3848aa6c\r\n\r\n \u00e2\u0080\u00a2 Bug fix for publish#html_encode():\r\n   http:\/\/github.com\/xolox\/vim-publish\/commit\/5df4c3d750654a330e077eb96a781c9b8d4dab7c\r\n\r\n \u00e2\u0080\u00a2 Simplified tags -> hyperlinks conversion hack:\r\n   http:\/\/github.com\/xolox\/vim-publish\/commit\/459b8293a2a85885872603765699a210fe72fb74\r\n\r\n \u00e2\u0080\u00a2 Smarter integration with easytags.vim:\r\n   http:\/\/github.com\/xolox\/vim-publish\/commit\/be98f4328bb631cd4c67d8951ff7c413b7cb6355\r\n\r\n \u00e2\u0080\u00a2 Fixed easytags#update() to overcome argument limit:\r\n   http:\/\/github.com\/xolox\/vim-publish\/commit\/87b0305bd27d4ee3715790cddc76cc2cfead7c14","package":"publish.zip","4":"publish.zip","src_id":"13764","5":"13764","creation_date":"1283729400","6":"1283729400"},{"0":"2252","vim_version":"7.0","1":"7.0","script_version":"1.6","2":"1.6","version_comment":"* Bug fix for :doautocmd User PublishPre hook:\r\n  http:\/\/github.com\/xolox\/vim-publish\/commit\/964e4dbb486f203ae7a1cb426af9491f44225db1\r\n\r\n* Bug fix: Escape ~ in tag search patterns:\r\n  http:\/\/github.com\/xolox\/vim-publish\/commit\/2da32565a73c0a9ab25d4fd9b0f6626336202d07\r\n\r\n* Improved handling of VimL script-local functions:\r\n  http:\/\/github.com\/xolox\/vim-publish\/commit\/537fe778d8bec47001367193323a813c3333d038\r\n\r\n* Always prefer earlier tag definitions in the same document:\r\n  http:\/\/github.com\/xolox\/vim-publish\/commit\/17b9e7563464da908baf45870831599e2bc9c809\r\n\r\n* Faster remote publishing using rsync (automatically enabled):\r\n  http:\/\/github.com\/xolox\/vim-publish\/commit\/027a2f0f4f8ccd6a7f1739f023b4825944e71b57","3":"* Bug fix for :doautocmd User PublishPre hook:\r\n  http:\/\/github.com\/xolox\/vim-publish\/commit\/964e4dbb486f203ae7a1cb426af9491f44225db1\r\n\r\n* Bug fix: Escape ~ in tag search patterns:\r\n  http:\/\/github.com\/xolox\/vim-publish\/commit\/2da32565a73c0a9ab25d4fd9b0f6626336202d07\r\n\r\n* Improved handling of VimL script-local functions:\r\n  http:\/\/github.com\/xolox\/vim-publish\/commit\/537fe778d8bec47001367193323a813c3333d038\r\n\r\n* Always prefer earlier tag definitions in the same document:\r\n  http:\/\/github.com\/xolox\/vim-publish\/commit\/17b9e7563464da908baf45870831599e2bc9c809\r\n\r\n* Faster remote publishing using rsync (automatically enabled):\r\n  http:\/\/github.com\/xolox\/vim-publish\/commit\/027a2f0f4f8ccd6a7f1739f023b4825944e71b57","package":"publish.zip","4":"publish.zip","src_id":"13195","5":"13195","creation_date":"1276641969","6":"1276641969"},{"0":"2252","vim_version":"7.0","1":"7.0","script_version":"1.5.2","2":"1.5.2","version_comment":"Now includes generated Vim documentation based on README","3":"Now includes generated Vim documentation based on README","package":"publish.zip","4":"publish.zip","src_id":"13122","5":"13122","creation_date":"1275797377","6":"1275797377"},{"0":"2252","vim_version":"7.0","1":"7.0","script_version":"1.5.1","2":"1.5.1","version_comment":"Bug fix: Fixed usage instructions to include tags generation :-\\\r\nhttp:\/\/github.com\/xolox\/vim-publish\/commit\/8eee22a18373125398d853dc3848d4101865576b","3":"Bug fix: Fixed usage instructions to include tags generation :-\\\r\nhttp:\/\/github.com\/xolox\/vim-publish\/commit\/8eee22a18373125398d853dc3848d4101865576b","package":"publish.zip","4":"publish.zip","src_id":"13115","5":"13115","creation_date":"1275763931","6":"1275763931"},{"0":"2252","vim_version":"7.0","1":"7.0","script_version":"1.5","2":"1.5","version_comment":"Completely switched directions by forgetting about incremental, automatic publishing (which interferes with the user because \"2html.vim\" is too slow) and instead focusing on batch publishing of multiple related files, which means the plug-in can now include hyperlinks between the published files based on tags.","3":"Completely switched directions by forgetting about incremental, automatic publishing (which interferes with the user because \"2html.vim\" is too slow) and instead focusing on batch publishing of multiple related files, which means the plug-in can now include hyperlinks between the published files based on tags.","package":"publish.zip","4":"publish.zip","src_id":"13111","5":"13111","creation_date":"1275716038","6":"1275716038"},{"0":"2252","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"publish.vim","4":"publish.vim","src_id":"8724","5":"8724","creation_date":"1211742196","6":"1211742196"}]},"2251":{"script_id":"2251","0":"2251","script_name":"journal.vim","1":"journal.vim","script_type":"utility","2":"utility","summary":"Encrypted journal based on calendar.vim and gnupg.vim","3":"Encrypted journal based on calendar.vim and gnupg.vim","description":"An encrypted journal with calendar view.","4":"An encrypted journal with calendar view.","install_details":"Extract to ~\/.vim","5":"Extract to ~\/.vim","first_name":"Jeremy","6":"Jeremy","last_name":"Cantrell","7":"Cantrell","releases":[{"0":"2251","vim_version":"7.0","1":"7.0","script_version":"0.2","2":"0.2","version_comment":"Turn encryption off by default","3":"Turn encryption off by default","package":"jmcantrell-vim-journal-f760392.zip","4":"jmcantrell-vim-journal-f760392.zip","src_id":"15174","5":"15174","creation_date":"1299561199","6":"1299561199"},{"0":"2251","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"journal.vim","4":"journal.vim","src_id":"8723","5":"8723","creation_date":"1211720489","6":"1211720489"}]},"2250":{"script_id":"2250","0":"2250","script_name":"common_vimrc","1":"common_vimrc","script_type":"utility","2":"utility","summary":"some setting for vimrc simple.","3":"some setting for vimrc simple.","description":"some setting for vimrc simple.","4":"some setting for vimrc simple.","install_details":"","5":"","first_name":"cn","6":"cn","last_name":"angel","7":"angel","releases":[{"0":"2250","vim_version":"7.0","1":"7.0","script_version":"7.005","2":"7.005","version_comment":"more setting for your editings","3":"more setting for your editings","package":"vimrc.tar.gz","4":"vimrc.tar.gz","src_id":"11594","5":"11594","creation_date":"1256551513","6":"1256551513"},{"0":"2250","vim_version":"7.0","1":"7.0","script_version":"7.002","2":"7.002","version_comment":"Some useful setting.","3":"Some useful setting.","package":"vimrc.tar.gz","4":"vimrc.tar.gz","src_id":"9350","5":"9350","creation_date":"1223966961","6":"1223966961"},{"0":"2250","vim_version":"7.0","1":"7.0","script_version":"7.001","2":"7.001","version_comment":"some adding settings","3":"some adding settings","package":"vimrc.tar.gz","4":"vimrc.tar.gz","src_id":"9190","5":"9190","creation_date":"1219946938","6":"1219946938"},{"0":"2250","vim_version":"7.0","1":"7.0","script_version":"7.0","2":"7.0","version_comment":"Initial upload","3":"Initial upload","package":"vimrc.vim","4":"vimrc.vim","src_id":"8722","5":"8722","creation_date":"1211694456","6":"1211694456"}]},"2249":{"script_id":"2249","0":"2249","script_name":"pac.vim","1":"pac.vim","script_type":"syntax","2":"syntax","summary":"syntax highlighting for proxy .pac files","3":"syntax highlighting for proxy .pac files","description":"This is a simple syntax file for highlighting http proxy .pac files.  The proxy auto-config file defines how web browsers and other user agents can automatically choose the appropriate proxy server (access method) for fetching a given URL.  This script will help to parse these proxy files.  A great example to test it out on is at http:\/\/www.schooner.com\/~loverso\/no-ads\/. where you can find John LoVerso\\'s outstanding no-ads proxy config file.  Let me know what you think, and send comments to my email.  ","4":"This is a simple syntax file for highlighting http proxy .pac files.  The proxy auto-config file defines how web browsers and other user agents can automatically choose the appropriate proxy server (access method) for fetching a given URL.  This script will help to parse these proxy files.  A great example to test it out on is at http:\/\/www.schooner.com\/~loverso\/no-ads\/. where you can find John LoVerso\\'s outstanding no-ads proxy config file.  Let me know what you think, and send comments to my email.  ","install_details":"POSIX:      drop into $HOME\/.vim\/syntax\r\nWindows:  drop into %ProgramFiles%\\\\Vim\\\\vimfiles\\\\syntax\r\nadd this line to your $HOME\/.vimrc or your %ProgramFiles%\\\\Vim\\\\_vimrc:\r\n   au BufNewFile,BufRead *.pac set syntax=pac","5":"POSIX:      drop into $HOME\/.vim\/syntax\r\nWindows:  drop into %ProgramFiles%\\\\Vim\\\\vimfiles\\\\syntax\r\nadd this line to your $HOME\/.vimrc or your %ProgramFiles%\\\\Vim\\\\_vimrc:\r\n   au BufNewFile,BufRead *.pac set syntax=pac","first_name":"Justin","6":"Justin","last_name":"Randall","7":"Randall","releases":[{"0":"2249","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"pac.vim","4":"pac.vim","src_id":"8719","5":"8719","creation_date":"1211570686","6":"1211570686"}]},"2248":{"script_id":"2248","0":"2248","script_name":"xml_taginsert","1":"xml_taginsert","script_type":"ftplugin","2":"ftplugin","summary":"Insert xml tags by pressing <F7>","3":"Insert xml tags by pressing <F7>","description":"This maps the <F7> key to an xml tag inserter. When you press <F7> while to cursor is on or directly after a word, the that word is transformed into an xml tag, complete with closing tag. When the cusor is not over a word, you will be prompted for a tag name. This works in insert and comment mode.\r\n\r\nThis plugin depends on the imaps plugin that comes with the vim latex-suite (vim-latex) or can be downloaded separately at http:\/\/www.vim.org\/scripts\/script.php?script_id=244","4":"This maps the <F7> key to an xml tag inserter. When you press <F7> while to cursor is on or directly after a word, the that word is transformed into an xml tag, complete with closing tag. When the cusor is not over a word, you will be prompted for a tag name. This works in insert and comment mode.\r\n\r\nThis plugin depends on the imaps plugin that comes with the vim latex-suite (vim-latex) or can be downloaded separately at http:\/\/www.vim.org\/scripts\/script.php?script_id=244","install_details":"Copy this file into your ftplugin directory. You may additionally want to create a symlink to it as 'html_taginsert.vim', so that it is also loaded when you edit html files.","5":"Copy this file into your ftplugin directory. You may additionally want to create a symlink to it as 'html_taginsert.vim', so that it is also loaded when you edit html files.","first_name":"Michael","6":"Michael","last_name":"Goerz","7":"Goerz","releases":[{"0":"2248","vim_version":"7.0","1":"7.0","script_version":"0.9","2":"0.9","version_comment":"Initial upload","3":"Initial upload","package":"xml_taginsert.vim","4":"xml_taginsert.vim","src_id":"8718","5":"8718","creation_date":"1211568128","6":"1211568128"}]},"2247":{"script_id":"2247","0":"2247","script_name":"FFeedVim","1":"FFeedVim","script_type":"utility","2":"utility","summary":"Post to Friendfeed from Vim","3":"Post to Friendfeed from Vim","description":"FFeedVim is a Vim plugin that allows you to post messages, links, and images to Friendfeed. Friendfeed is a social network aggregator at http:\/\/friendfeed.com\r\n\r\nSince this is an early release of the plugin, it comes with significant limitations: There is no support for viewing Friendfeed timelines yet. There is also no support for liking or commenting on Friendfeed items, although FFeedVim allows you to add an initial comment when posting an item.\r\n\r\nAfter installing FFeedVim, see :help FFeedVim-manual for a list of commands.\r\n\r\nI'm on Friendfeed at http:\/\/friendfeed.com\/mortonfox if anyone wishes to follow my stream.\r\n","4":"FFeedVim is a Vim plugin that allows you to post messages, links, and images to Friendfeed. Friendfeed is a social network aggregator at http:\/\/friendfeed.com\r\n\r\nSince this is an early release of the plugin, it comes with significant limitations: There is no support for viewing Friendfeed timelines yet. There is also no support for liking or commenting on Friendfeed items, although FFeedVim allows you to add an initial comment when posting an item.\r\n\r\nAfter installing FFeedVim, see :help FFeedVim-manual for a list of commands.\r\n\r\nI'm on Friendfeed at http:\/\/friendfeed.com\/mortonfox if anyone wishes to follow my stream.\r\n","install_details":"==============================================================\r\nOpen the Vimball archive file and then source it. For example:\r\n\r\n    vim ffeedvim.vba\r\n    :source %\r\n\r\nThen see :help FFeedVim-install for further instructions. \r\n==============================================================\r\n","5":"==============================================================\r\nOpen the Vimball archive file and then source it. For example:\r\n\r\n    vim ffeedvim.vba\r\n    :source %\r\n\r\nThen see :help FFeedVim-install for further instructions. \r\n==============================================================\r\n","first_name":"Po Shan","6":"Po Shan","last_name":"Cheah","7":"Cheah","releases":[{"0":"2247","vim_version":"7.0","1":"7.0","script_version":"0.1.0","2":"0.1.0","version_comment":"Initial release.","3":"Initial release.","package":"ffeedvim-0.1.0.vba","4":"ffeedvim-0.1.0.vba","src_id":"8717","5":"8717","creation_date":"1211556257","6":"1211556257"}]},"2246":{"script_id":"2246","0":"2246","script_name":"darkroom","1":"darkroom","script_type":"color scheme","2":"color scheme","summary":"color scheme to mimic writeroom\/darkroom editors","3":"color scheme to mimic writeroom\/darkroom editors","description":"This is my attempt to create a simple WriteRoom\/DarkRoom like environment in Vim. \r\n\r\nIt is probably not ready for prime-time yet. \r\n\r\nIt will almost certainly interact badly with any other plugins\/scripts that hack buffers as it uses two hidden buffers to get the column feel of DarkRoom.\r\n\r\nYou will want to \":set wrap lbr\" for it to work most effectively.\r\nYou will want to maximize vim before calling \":colorscheme darkroom\" for it to look reasonable.\r\nYou will also need to use :qa to exit (or :q several times in succession)\r\n\r\n\r\n","4":"This is my attempt to create a simple WriteRoom\/DarkRoom like environment in Vim. \r\n\r\nIt is probably not ready for prime-time yet. \r\n\r\nIt will almost certainly interact badly with any other plugins\/scripts that hack buffers as it uses two hidden buffers to get the column feel of DarkRoom.\r\n\r\nYou will want to \":set wrap lbr\" for it to work most effectively.\r\nYou will want to maximize vim before calling \":colorscheme darkroom\" for it to look reasonable.\r\nYou will also need to use :qa to exit (or :q several times in succession)\r\n\r\n\r\n","install_details":"Put it in one of your colors directories.\r\n  ex. $HOME\/.vim\/colors\/\r\n  ex. $HOME\\vimfiles\\colors\\\r\n  ex. $VIM\\vimfiles\\colors\\\r\nThen, just do :colorscheme darkroom","5":"Put it in one of your colors directories.\r\n  ex. $HOME\/.vim\/colors\/\r\n  ex. $HOME\\vimfiles\\colors\\\r\n  ex. $VIM\\vimfiles\\colors\\\r\nThen, just do :colorscheme darkroom","first_name":"Connor","6":"Connor","last_name":"Berry","7":"Berry","releases":[{"0":"2246","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"darkroom.vim","4":"darkroom.vim","src_id":"8715","5":"8715","creation_date":"1211532950","6":"1211532950"}]},"2245":{"script_id":"2245","0":"2245","script_name":"upf.vim","1":"upf.vim","script_type":"syntax","2":"syntax","summary":"Syntax for Unified Power Format  files(UPF)","3":"Syntax for Unified Power Format  files(UPF)","description":"UPF provides the ability for electronic systems to be designed with \r\npower as a key consideration early in the process.\r\nThe current Working Group\u00e2\u0080\u0099s website address is  www.accellera.org\/activities\/upf\r\n\r\n","4":"UPF provides the ability for electronic systems to be designed with \r\npower as a key consideration early in the process.\r\nThe current Working Group\u00e2\u0080\u0099s website address is  www.accellera.org\/activities\/upf\r\n\r\n","install_details":"Following steps are valid for UNIX. For windows, suitable equivalents need to be used\r\n\r\nStep 1: Untar the archive upf.tar.gz\r\n \r\n If you already have ~\/.vim ~\/.vim\/syntax and ~\/.vim\/filetype.vim then skip  Step 2\r\n \r\n Step 2: If you don't have ~\/.vim then\r\n         % mv upf_syntax ~\/.vim\r\n         Skip Step 3\r\n \r\n Step 3: Append the lines from upf_syntax\/filetype.vim to ~\/.vim\/filetype.vim\r\n             or  Drop upf_syntax\/syntax\/upf.vim in ~\/.vim\/syntax\/\r\n\r\n          if exists(\"did_load_filetypes\")\r\n          finish\r\n          endif\r\n          augroup filetypedetect\r\n          au! BufRead,BufNewFile *.upf setfiletype upf\r\n          augroup END \r\n\r\n\r\nHappy vimming!!\r\n","5":"Following steps are valid for UNIX. For windows, suitable equivalents need to be used\r\n\r\nStep 1: Untar the archive upf.tar.gz\r\n \r\n If you already have ~\/.vim ~\/.vim\/syntax and ~\/.vim\/filetype.vim then skip  Step 2\r\n \r\n Step 2: If you don't have ~\/.vim then\r\n         % mv upf_syntax ~\/.vim\r\n         Skip Step 3\r\n \r\n Step 3: Append the lines from upf_syntax\/filetype.vim to ~\/.vim\/filetype.vim\r\n             or  Drop upf_syntax\/syntax\/upf.vim in ~\/.vim\/syntax\/\r\n\r\n          if exists(\"did_load_filetypes\")\r\n          finish\r\n          endif\r\n          augroup filetypedetect\r\n          au! BufRead,BufNewFile *.upf setfiletype upf\r\n          augroup END \r\n\r\n\r\nHappy vimming!!\r\n","first_name":"Aditya","6":"Aditya","last_name":"Kher","7":"Kher","releases":[{"0":"2245","vim_version":"7.0","1":"7.0","script_version":"0.2","2":"0.2","version_comment":"vba for vim 7.0 or better","3":"vba for vim 7.0 or better","package":"upf.vba","4":"upf.vba","src_id":"8791","5":"8791","creation_date":"1213251549","6":"1213251549"},{"0":"2245","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"upf.tar.gz","4":"upf.tar.gz","src_id":"8711","5":"8711","creation_date":"1211435431","6":"1211435431"}]},"2244":{"script_id":"2244","0":"2244","script_name":"less.bat","1":"less.bat","script_type":"utility","2":"utility","summary":"Now less is more on Windows, too","3":"Now less is more on Windows, too","description":"Makes Vim into a rewindable, syntax-highlighting, searchable pager on Windows.\r\n\r\nBased upon less.sh from the macros directory of the Vim distribution.\r\nRequires that macros\/less.vim exist in the &runtimepath.\r\nWorks with pipes as well as file names.","4":"Makes Vim into a rewindable, syntax-highlighting, searchable pager on Windows.\r\n\r\nBased upon less.sh from the macros directory of the Vim distribution.\r\nRequires that macros\/less.vim exist in the &runtimepath.\r\nWorks with pipes as well as file names.","install_details":"Place this file somewhere in your %PATH%.","5":"Place this file somewhere in your %PATH%.","first_name":"erik","6":"erik","last_name":"falor","7":"falor","releases":[{"0":"2244","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"less.bat","4":"less.bat","src_id":"8707","5":"8707","creation_date":"1211188065","6":"1211188065"}]},"2243":{"script_id":"2243","0":"2243","script_name":"RemoveDups.VIM","1":"RemoveDups.VIM","script_type":"utility","2":"utility","summary":"Removing duplicates","3":"Removing duplicates","description":"After sorting a file (eg. with the very useful vissort.vim) you can mark an area (line- or blockwise) an remove any lines containing duplicate values within this mark, so making anything in the marked area uinique.\r\n\r\nThs most common use is:\r\nmark a block\r\n:Sort it\r\nRemark the same block using gv\r\n:call RemoveDups()","4":"After sorting a file (eg. with the very useful vissort.vim) you can mark an area (line- or blockwise) an remove any lines containing duplicate values within this mark, so making anything in the marked area uinique.\r\n\r\nThs most common use is:\r\nmark a block\r\n:Sort it\r\nRemark the same block using gv\r\n:call RemoveDups()","install_details":"copy it into plugins\r\n\r\nIf you like you can add a command invoking it; I haven't done yet.","5":"copy it into plugins\r\n\r\nIf you like you can add a command invoking it; I haven't done yet.","first_name":"Michael","6":"Michael","last_name":"Fitz","7":"Fitz","releases":[{"0":"2243","vim_version":"6.0","1":"6.0","script_version":"1","2":"1","version_comment":"Initial upload","3":"Initial upload","package":"RemoveDups.VIM","4":"RemoveDups.VIM","src_id":"8706","5":"8706","creation_date":"1211185112","6":"1211185112"}]},"2242":{"script_id":"2242","0":"2242","script_name":"openser.vim","1":"openser.vim","script_type":"syntax","2":"syntax","summary":"Openser configuration syntax","3":"Openser configuration syntax","description":"Syntax file for Openser configuration. In version 1.00 it includes all core keywords as of version 1.3.X.\r\nWorks in Vim 7.1.","4":"Syntax file for Openser configuration. In version 1.00 it includes all core keywords as of version 1.3.X.\r\nWorks in Vim 7.1.","install_details":"Install script into vim syntax files directory. Switch to openser syntax either with \"setf openser\" or add filetype detection.\r\nThis detection works quite well if used instead of standard *.cfg:\r\n\r\nau BufNewFile,BufRead *.cfg   call s:cfgType()\r\n\r\nfunc! s:cfgType()\r\n   let max = line(\"$\") > 50 ? 50 : line(\"$\")\r\n   for n in range(1, max)\r\n      if getline(n) =~ '^\\s*modparam\\s*('\r\n         setf openser\r\n         return\r\n      elseif getline(n) =~ '^\\s*loadmodule\\s*\"[^\"]\\+.so\"\\s*$'\r\n         setf openser\r\n         return\r\n      elseif getline(n) =~ '^\\s*route\\s*{\\s*'\r\n         setf openser\r\n         return\r\n      endif\r\n   endfor\r\n   setf cfg\r\nendfunc\r\n","5":"Install script into vim syntax files directory. Switch to openser syntax either with \"setf openser\" or add filetype detection.\r\nThis detection works quite well if used instead of standard *.cfg:\r\n\r\nau BufNewFile,BufRead *.cfg   call s:cfgType()\r\n\r\nfunc! s:cfgType()\r\n   let max = line(\"$\") > 50 ? 50 : line(\"$\")\r\n   for n in range(1, max)\r\n      if getline(n) =~ '^\\s*modparam\\s*('\r\n         setf openser\r\n         return\r\n      elseif getline(n) =~ '^\\s*loadmodule\\s*\"[^\"]\\+.so\"\\s*$'\r\n         setf openser\r\n         return\r\n      elseif getline(n) =~ '^\\s*route\\s*{\\s*'\r\n         setf openser\r\n         return\r\n      endif\r\n   endfor\r\n   setf cfg\r\nendfunc\r\n","first_name":"Stanis\u0142aw","6":"Stanisław","last_name":"Pitucha","7":"Pitucha","releases":[{"0":"2242","vim_version":"7.0","1":"7.0","script_version":"1.00","2":"1.00","version_comment":"Initial upload","3":"Initial upload","package":"openser.vim","4":"openser.vim","src_id":"8705","5":"8705","creation_date":"1211125919","6":"1211125919"}]},"2241":{"script_id":"2241","0":"2241","script_name":"vcsbzr.vim","1":"vcsbzr.vim","script_type":"utility","2":"utility","summary":"Bazaar integration for VCSCommand","3":"Bazaar integration for VCSCommand","description":"This is a plugin for VCSCommand (vimscript #90) that integrates the Bazaar version control system (http:\/\/bazaar-vcs.org).  It allows the basic version control commands of VCSCommand to be applied to projects versioned using Bazaar.\r\n\r\nThis script is maintained at http:\/\/launchpad.net\/bzr-vim","4":"This is a plugin for VCSCommand (vimscript #90) that integrates the Bazaar version control system (http:\/\/bazaar-vcs.org).  It allows the basic version control commands of VCSCommand to be applied to projects versioned using Bazaar.\r\n\r\nThis script is maintained at http:\/\/launchpad.net\/bzr-vim","install_details":"After installing VCSCommand (vimscript #90), copy the vcsbzr.vim file to the directory where vcscommmand.vim is located.","5":"After installing VCSCommand (vimscript #90), copy the vcsbzr.vim file to the directory where vcscommmand.vim is located.","first_name":"Neil","6":"Neil","last_name":"Martinsen-Burrell","7":"Martinsen-Burrell","releases":[{"0":"2241","vim_version":"6.0","1":"6.0","script_version":"0.0.1","2":"0.0.1","version_comment":"Initial upload","3":"Initial upload","package":"vcsbzr.vim","4":"vcsbzr.vim","src_id":"8691","5":"8691","creation_date":"1210851432","6":"1210851432"}]},"2240":{"script_id":"2240","0":"2240","script_name":"256-jungle","1":"256-jungle","script_type":"color scheme","2":"color scheme","summary":"Dark-orange colorscheme for 256 color terminals (like xterm).","3":"Dark-orange colorscheme for 256 color terminals (like xterm).","description":"Dark-orange colorscheme for 256 color terminals (like xterm).\r\n\r\n\r\nScreenshots:\r\nhttp:\/\/xs227.xs.to\/xs227\/08202\/2008-05-13_12-05-24_screenshot_scrot222.png\r\nhttp:\/\/xs227.xs.to\/xs227\/08202\/2008-05-13_12-08-36_screenshot_scrot333.png","4":"Dark-orange colorscheme for 256 color terminals (like xterm).\r\n\r\n\r\nScreenshots:\r\nhttp:\/\/xs227.xs.to\/xs227\/08202\/2008-05-13_12-05-24_screenshot_scrot222.png\r\nhttp:\/\/xs227.xs.to\/xs227\/08202\/2008-05-13_12-08-36_screenshot_scrot333.png","install_details":"Put this file into ~\/.vim\/colors  and type \r\n:colorscheme 256-jungle","5":"Put this file into ~\/.vim\/colors  and type \r\n:colorscheme 256-jungle","first_name":"Piotr","6":"Piotr","last_name":"Husiatynski","7":"Husiatynski","releases":[{"0":"2240","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"256-jungle.vim","4":"256-jungle.vim","src_id":"8685","5":"8685","creation_date":"1210648413","6":"1210648413"}]},"2239":{"script_id":"2239","0":"2239","script_name":"darkrobot.vim","1":"darkrobot.vim","script_type":"color scheme","2":"color scheme","summary":"A nice dark colorscheme","3":"A nice dark colorscheme","description":"This is a nice dark colorscheme designed for long code editing sessions.\r\n\r\nA screenshot can be found here:\r\nhttp:\/\/www.flickr.com\/photos\/26471999@N08\/2488920242\/","4":"This is a nice dark colorscheme designed for long code editing sessions.\r\n\r\nA screenshot can be found here:\r\nhttp:\/\/www.flickr.com\/photos\/26471999@N08\/2488920242\/","install_details":"On UNIX-like systems, including Mac OS X or Cygwin, put this file into ~\/.vim\/colors\r\nOn Windows, it should go into C:\\Program Files\\vim(or Vim)\\vimfiles\\colors (something like that)","5":"On UNIX-like systems, including Mac OS X or Cygwin, put this file into ~\/.vim\/colors\r\nOn Windows, it should go into C:\\Program Files\\vim(or Vim)\\vimfiles\\colors (something like that)","first_name":"alex","6":"alex","last_name":"yeh","7":"yeh","releases":[{"0":"2239","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"darkrobot.vim","4":"darkrobot.vim","src_id":"8683","5":"8683","creation_date":"1210630677","6":"1210630677"}]},"2238":{"script_id":"2238","0":"2238","script_name":"StringComplete","1":"StringComplete","script_type":"utility","2":"utility","summary":"Insert-completion for quoted strings","3":"Insert-completion for quoted strings","description":"This script allows you to auto-complete quoted strings (\"...\" and '...') in the same way that you can complete keywords or filenames.\r\n\r\nIf you have any trouble installing or using, email me toomuchphp-vim at yahoo.com.","4":"This script allows you to auto-complete quoted strings (\"...\" and '...') in the same way that you can complete keywords or filenames.\r\n\r\nIf you have any trouble installing or using, email me toomuchphp-vim at yahoo.com.","install_details":"Put StringComplete.vim into ~\/.vim\/autoload\/ or c:\\Program Files\\vim\\vimfiles\\autoload\\\r\n\r\nTo map a keystroke such as CTRL-J to get the list of strings, add the following command to\r\nyour .vimrc:\r\n\r\n  inoremap <C-J> <C-O>:set completefunc=StringComplete#GetList<CR><C-X><C-U>\r\n\r\nAfter pressing CTRL-J in insert mode, the first matching string will be inserted. Then, use\r\nCTRL-N and CTRL-P to cycle through the completion list.\r\n","5":"Put StringComplete.vim into ~\/.vim\/autoload\/ or c:\\Program Files\\vim\\vimfiles\\autoload\\\r\n\r\nTo map a keystroke such as CTRL-J to get the list of strings, add the following command to\r\nyour .vimrc:\r\n\r\n  inoremap <C-J> <C-O>:set completefunc=StringComplete#GetList<CR><C-X><C-U>\r\n\r\nAfter pressing CTRL-J in insert mode, the first matching string will be inserted. Then, use\r\nCTRL-N and CTRL-P to cycle through the completion list.\r\n","first_name":"Peter","6":"Peter","last_name":"Hodge","7":"Hodge","releases":[{"0":"2238","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"StringComplete.vim","4":"StringComplete.vim","src_id":"8682","5":"8682","creation_date":"1210609010","6":"1210609010"}]},"2237":{"script_id":"2237","0":"2237","script_name":"useful optistruct functions","1":"useful optistruct functions","script_type":"utility","2":"utility","summary":"useful optistruct functions","3":"useful optistruct functions","description":"some useful functions for editing optistruct decks, see file comments for examples.","4":"some useful functions for editing optistruct decks, see file comments for examples.","install_details":"copy into plugin directory.","5":"copy into plugin directory.","first_name":"Sam","6":"Sam","last_name":"Patten","7":"Patten","releases":[{"0":"2237","vim_version":"6.0","1":"6.0","script_version":"1","2":"1","version_comment":"Initial upload","3":"Initial upload","package":"os_functions.vim","4":"os_functions.vim","src_id":"8677","5":"8677","creation_date":"1210573584","6":"1210573584"}]},"2236":{"script_id":"2236","0":"2236","script_name":"WarzoneResourceFileSyntax","1":"WarzoneResourceFileSyntax","script_type":"syntax","2":"syntax","summary":"Syntax highlighting for Warzone2100 resource files","3":"Syntax highlighting for Warzone2100 resource files","description":"This script provides syntax highlighting for Warzone 2100's ( http:\/\/wz2100.net\/ ) resource files.","4":"This script provides syntax highlighting for Warzone 2100's ( http:\/\/wz2100.net\/ ) resource files.","install_details":"You will want to extract this script in $HOME\/.vim\/ (Unix systems) or %HOMEPATH%\\vimfiles\\ (Windows).","5":"You will want to extract this script in $HOME\/.vim\/ (Unix systems) or %HOMEPATH%\\vimfiles\\ (Windows).","first_name":"Giel","6":"Giel","last_name":"van Schijndel","7":"van Schijndel","releases":[{"0":"2236","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Add a filetype detection script that uses the filename (*.wrf) to detect the correct filetype.","3":"Add a filetype detection script that uses the filename (*.wrf) to detect the correct filetype.","package":"wrf.zip","4":"wrf.zip","src_id":"8676","5":"8676","creation_date":"1210566394","6":"1210566394"}]},"2235":{"script_id":"2235","0":"2235","script_name":"previewtag","1":"previewtag","script_type":"utility","2":"utility","summary":"preview the definition and switch it to a new window","3":"preview the definition and switch it to a new window","description":"The script opens the definition of functions and variables in the preview window on demand and provides operations to close the preview window, delete the buffer in the preview window and switch the buffer in the preview window to a new window. Quite simple, but useful.\r\n\r\nThe script provides four commands:\r\nPshow: open the definition of the current word in the preview window\r\nPdelete: delete the buffer showing in the preview window\r\nPshowORdelete: if the cursor is in preview window, delete the current buffer (like Pdelete); Otherwise open the definition of current word in preview window\r\nPswitch: if the preview window is open, close it and open the buffer in a new window \r\n\r\nVim also provides a \"pclose\" command to close the preview window, without deleting the buffer.\r\n\r\nIf you want to open the tag preview immediately when you put cursor on a word, please uncomment the last line of the script. However, I found automatically preview is kind of boresome, so I do not provide a switch of auto-preview in the script.\r\n\r\nYou can also refer to another tiny script autopreview at http:\/\/vim.sourceforge.net\/scripts\/script.php?script_id=2228.\r\n\r\nRelated vim docs:\r\n:help ptag\r\n:help previewwindow","4":"The script opens the definition of functions and variables in the preview window on demand and provides operations to close the preview window, delete the buffer in the preview window and switch the buffer in the preview window to a new window. Quite simple, but useful.\r\n\r\nThe script provides four commands:\r\nPshow: open the definition of the current word in the preview window\r\nPdelete: delete the buffer showing in the preview window\r\nPshowORdelete: if the cursor is in preview window, delete the current buffer (like Pdelete); Otherwise open the definition of current word in preview window\r\nPswitch: if the preview window is open, close it and open the buffer in a new window \r\n\r\nVim also provides a \"pclose\" command to close the preview window, without deleting the buffer.\r\n\r\nIf you want to open the tag preview immediately when you put cursor on a word, please uncomment the last line of the script. However, I found automatically preview is kind of boresome, so I do not provide a switch of auto-preview in the script.\r\n\r\nYou can also refer to another tiny script autopreview at http:\/\/vim.sourceforge.net\/scripts\/script.php?script_id=2228.\r\n\r\nRelated vim docs:\r\n:help ptag\r\n:help previewwindow","install_details":"#1 Put previewtag.vim in your vim plugin directory\r\n\r\n#2 Key map is recommended,  for example:\r\n\tmap <F5> :PshowORdelete<CR>\r\n\tmap <S-F5> :Pdelete<CR>\r\n\tmap <C-F5> :pclose<CR>\r\n\tmap <F6> :Pswitch<CR>\r\n","5":"#1 Put previewtag.vim in your vim plugin directory\r\n\r\n#2 Key map is recommended,  for example:\r\n\tmap <F5> :PshowORdelete<CR>\r\n\tmap <S-F5> :Pdelete<CR>\r\n\tmap <C-F5> :pclose<CR>\r\n\tmap <F6> :Pswitch<CR>\r\n","first_name":"Danqi","6":"Danqi","last_name":"Wang","7":"Wang","releases":[{"0":"2235","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"previewtag.vim","4":"previewtag.vim","src_id":"8672","5":"8672","creation_date":"1210552733","6":"1210552733"}]},"2234":{"script_id":"2234","0":"2234","script_name":"rtorrent syntax file","1":"rtorrent syntax file","script_type":"syntax","2":"syntax","summary":"Syntax highlighting for rtorrent.rc files","3":"Syntax highlighting for rtorrent.rc files","description":"Highlighting for the rtorrent.rc file.   Simple and effective.","4":"Highlighting for the rtorrent.rc file.   Simple and effective.","install_details":"Just put the file in $HOM\/.vim\/syntax.   You will also need to add the following line to $VIMRUNTIME\/filetype.vim, or first copy filetype.vim file to $HOME\/.vim, and edit:\r\n\r\nau BufNewFile,BufRead *rtorrent.rc* set filetype=rtorrent\r\n\r\n\r\n","5":"Just put the file in $HOM\/.vim\/syntax.   You will also need to add the following line to $VIMRUNTIME\/filetype.vim, or first copy filetype.vim file to $HOME\/.vim, and edit:\r\n\r\nau BufNewFile,BufRead *rtorrent.rc* set filetype=rtorrent\r\n\r\n\r\n","first_name":"chris","6":"chris","last_name":"carpita","7":"carpita","releases":[{"0":"2234","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"rtorrent.vim","4":"rtorrent.vim","src_id":"8669","5":"8669","creation_date":"1210447717","6":"1210447717"}]},"2233":{"script_id":"2233","0":"2233","script_name":"nc.vim","1":"nc.vim","script_type":"ftplugin","2":"ftplugin","summary":"Neuron C (*.nc) Syntax\/Filetype for Vim","3":"Neuron C (*.nc) Syntax\/Filetype for Vim","description":"This adds the syntax for Echelon Neuron C files (.nc) (see PL3120\/PL3150,PL31XX) chips ","4":"This adds the syntax for Echelon Neuron C files (.nc) (see PL3120\/PL3150,PL31XX) chips ","install_details":"","5":"","first_name":"Florian","6":"Florian","last_name":"Delizy","7":"Delizy","releases":[{"0":"2233","vim_version":"7.0","1":"7.0","script_version":"1.1","2":"1.1","version_comment":"Added the 'online' keyword, updated common errors (no #if 0, no volatile storage modifier)","3":"Added the 'online' keyword, updated common errors (no #if 0, no volatile storage modifier)","package":"nc.vim","4":"nc.vim","src_id":"8780","5":"8780","creation_date":"1213071993","6":"1213071993"},{"0":"2233","vim_version":"7.0","1":"7.0","script_version":"1","2":"1","version_comment":"Initial upload","3":"Initial upload","package":"nc.vim","4":"nc.vim","src_id":"8668","5":"8668","creation_date":"1210407787","6":"1210407787"}]},"2232":{"script_id":"2232","0":"2232","script_name":"h80","1":"h80","script_type":"color scheme","2":"color scheme","summary":"Dark blue background with high-contrast text","3":"Dark blue background with high-contrast text","description":"Green, blue, orange and magenta text.","4":"Green, blue, orange and magenta text.","install_details":"","5":"","first_name":"Helder","6":"Helder","last_name":"Correia","7":"Correia","releases":[{"0":"2232","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"h80.vim","4":"h80.vim","src_id":"8660","5":"8660","creation_date":"1210216437","6":"1210216437"}]},"2231":{"script_id":"2231","0":"2231","script_name":"WriteRoom for Vim","1":"WriteRoom for Vim","script_type":"utility","2":"utility","summary":"A Vim emulation of the minimalistic WriteRoom editor","3":"A Vim emulation of the minimalistic WriteRoom editor","description":"As you probably know, WriteRoom (http:\/\/hogbaysoftware.com\/products\/writeroom) is a very minimalistic text editor, focusing on a clean appearance of just the edited document. This script creates \\'padding\\' around the editing window in gVim and hides the vertical splits and other items to obtain this same effect, while keeping all of Vim\\'s extensive features available. \r\n\r\nUsing the file is simple, just issue a gvim -S ~\/.vim\/writeroom\/writeroom.vim {filename} at the command line to open the file in a very clean, minimalist setup. Perfect for ADD-ers like myself ;-)\r\n\r\nThis file adds the following:\r\n\r\nCommands:\r\n=========\r\n\r\nWriteRoomBG {color} ; sets the background color\r\nWriteRoomFG {color} ; sets the foreground color\r\nWriteRoomFilename {color} ; sets the color for the filename just below the editing window\r\nWriteRoomNonText {color} ; sets the color for non-text characters\r\n\r\nFunctions:\r\n==========\r\n\r\nUpdateScreen() ; updates the screen size and colors\r\n\r\nMappings:\r\n=========\r\n\r\n<F5> toggles visibility of EOL, TAB and tilde lines\r\n\r\n\r\n","4":"As you probably know, WriteRoom (http:\/\/hogbaysoftware.com\/products\/writeroom) is a very minimalistic text editor, focusing on a clean appearance of just the edited document. This script creates \\'padding\\' around the editing window in gVim and hides the vertical splits and other items to obtain this same effect, while keeping all of Vim\\'s extensive features available. \r\n\r\nUsing the file is simple, just issue a gvim -S ~\/.vim\/writeroom\/writeroom.vim {filename} at the command line to open the file in a very clean, minimalist setup. Perfect for ADD-ers like myself ;-)\r\n\r\nThis file adds the following:\r\n\r\nCommands:\r\n=========\r\n\r\nWriteRoomBG {color} ; sets the background color\r\nWriteRoomFG {color} ; sets the foreground color\r\nWriteRoomFilename {color} ; sets the color for the filename just below the editing window\r\nWriteRoomNonText {color} ; sets the color for non-text characters\r\n\r\nFunctions:\r\n==========\r\n\r\nUpdateScreen() ; updates the screen size and colors\r\n\r\nMappings:\r\n=========\r\n\r\n<F5> toggles visibility of EOL, TAB and tilde lines\r\n\r\n\r\n","install_details":"Just extract the tarball to ~\/.vim\/ so that ~\/.vim contains a directory named \\\"writeroom\\\". Edit ~\/.vim\/writeroom\/writeroomrc to your liking. Feel free to experiment. Enjoy!","5":"Just extract the tarball to ~\/.vim\/ so that ~\/.vim contains a directory named \\\"writeroom\\\". Edit ~\/.vim\/writeroom\/writeroomrc to your liking. Feel free to experiment. Enjoy!","first_name":"Marc","6":"Marc","last_name":"van Doornik","7":"van Doornik","releases":[{"0":"2231","vim_version":"7.0","1":"7.0","script_version":"0.01","2":"0.01","version_comment":"Initial upload","3":"Initial upload","package":"writeroom_for_gvim.tar.gz","4":"writeroom_for_gvim.tar.gz","src_id":"8655","5":"8655","creation_date":"1210143255","6":"1210143255"}]},"2230":{"script_id":"2230","0":"2230","script_name":"beachcomber.vim","1":"beachcomber.vim","script_type":"color scheme","2":"color scheme","summary":"A light, sandy, beachy color scheme","3":"A light, sandy, beachy color scheme","description":"This scheme has a light sand-colored background and a colors that might remind one of the beach. Here are some pictures:\r\n\r\nhttp:\/\/www.flickr.com\/photos\/26471999@N08\/2477652354\/\r\nhttp:\/\/www.flickr.com\/photos\/26471999@N08\/2476839901\/\r\nhttp:\/\/www.flickr.com\/photos\/26471999@N08\/2477652186\/","4":"This scheme has a light sand-colored background and a colors that might remind one of the beach. Here are some pictures:\r\n\r\nhttp:\/\/www.flickr.com\/photos\/26471999@N08\/2477652354\/\r\nhttp:\/\/www.flickr.com\/photos\/26471999@N08\/2476839901\/\r\nhttp:\/\/www.flickr.com\/photos\/26471999@N08\/2477652186\/","install_details":"On UNIX-like systems, including Mac OS X or Cygwin, put this file into ~\/.vim\/colors\r\nOn Windows, it should go into C:\\Program Files\\vim(or Vim)\\vimfiles\\colors (something like that)","5":"On UNIX-like systems, including Mac OS X or Cygwin, put this file into ~\/.vim\/colors\r\nOn Windows, it should go into C:\\Program Files\\vim(or Vim)\\vimfiles\\colors (something like that)","first_name":"alex","6":"alex","last_name":"yeh","7":"yeh","releases":[{"0":"2230","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"beachcomber.vim","4":"beachcomber.vim","src_id":"8653","5":"8653","creation_date":"1210118424","6":"1210118424"}]},"2229":{"script_id":"2229","0":"2229","script_name":"pacific.vim","1":"pacific.vim","script_type":"color scheme","2":"color scheme","summary":"A dark, oceany\/beachy color scheme","3":"A dark, oceany\/beachy color scheme","description":"This is a nice dark color scheme that is meant to be reminiscent of the ocean or the beach, and yet not at all like either the ocean or the beach.\r\n\r\nHere are some pictures so you can get an idea what it looks like:\r\nhttp:\/\/www.flickr.com\/photos\/26471999@N08\/2477652644\/\r\nhttp:\/\/www.flickr.com\/photos\/26471999@N08\/2476840217\/\r\nhttp:\/\/www.flickr.com\/photos\/26471999@N08\/2477652478\/","4":"This is a nice dark color scheme that is meant to be reminiscent of the ocean or the beach, and yet not at all like either the ocean or the beach.\r\n\r\nHere are some pictures so you can get an idea what it looks like:\r\nhttp:\/\/www.flickr.com\/photos\/26471999@N08\/2477652644\/\r\nhttp:\/\/www.flickr.com\/photos\/26471999@N08\/2476840217\/\r\nhttp:\/\/www.flickr.com\/photos\/26471999@N08\/2477652478\/","install_details":"On UNIX-like systems, including Mac OS X or Cygwin, put this file into ~\/.vim\/colors\r\nOn Windows, it should go into C:\\Program Files\\vim(or Vim)\\vimfiles\\colors (something like that)","5":"On UNIX-like systems, including Mac OS X or Cygwin, put this file into ~\/.vim\/colors\r\nOn Windows, it should go into C:\\Program Files\\vim(or Vim)\\vimfiles\\colors (something like that)","first_name":"alex","6":"alex","last_name":"yeh","7":"yeh","releases":[{"0":"2229","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"pacific.vim","4":"pacific.vim","src_id":"8652","5":"8652","creation_date":"1210118109","6":"1210118109"}]},"2228":{"script_id":"2228","0":"2228","script_name":"autopreview","1":"autopreview","script_type":"utility","2":"utility","summary":"a light script to immediately preview definitions like source insight","3":"a light script to immediately preview definitions like source insight","description":"The \"autopreview\" plugin is a light script plugin for Vim that could automatically preview the definition of variables or functions in a preview window like source insight.\r\nI think this script should be helpful when you're insighting a lot of code files and wanna to see the definition of a new variable or function in the source codes immediately without having to input \"ptag\" each time.\r\nTaglist plugin is needed for this plugin which is alreasy integrated into the latest version of Gvim.\r\n\r\n#Usage\r\nIf you add \"let g:AutoPreview_enabled = 1\" into your vimrc file, the autopreview window will be open when vim is started; otherwise add \"let g:AutoPreview_enabled = 0\" (which is default if you do not set this value) into your vimrc file, the autopreview window will be open only after you press your mapped hotkey.\r\nAny time you press your mapped hotkey, you could enable or disable the autopreview window\r\n","4":"The \"autopreview\" plugin is a light script plugin for Vim that could automatically preview the definition of variables or functions in a preview window like source insight.\r\nI think this script should be helpful when you're insighting a lot of code files and wanna to see the definition of a new variable or function in the source codes immediately without having to input \"ptag\" each time.\r\nTaglist plugin is needed for this plugin which is alreasy integrated into the latest version of Gvim.\r\n\r\n#Usage\r\nIf you add \"let g:AutoPreview_enabled = 1\" into your vimrc file, the autopreview window will be open when vim is started; otherwise add \"let g:AutoPreview_enabled = 0\" (which is default if you do not set this value) into your vimrc file, the autopreview window will be open only after you press your mapped hotkey.\r\nAny time you press your mapped hotkey, you could enable or disable the autopreview window\r\n","install_details":"If you haven't installed taglist, please install it first: http:\/\/vim.sourceforge.net\/scripts\/script.php?script_id=273\r\n\r\n#1 Download autopreview.vim into your favorite plugin directory or source the script from your .vimrc file (_vimrc for windows)\r\n\r\n#2 Add the following context into your .vimrc file\r\n     \" Automatically enable the preview function with vim starting\r\n     let g:AutoPreview_enabled =1\r\n\r\n     \" make you could press F5 key to enable or disable the preview window, you can also set to other favorite hotkey here\r\n     nnoremap <F5> :AutoPreviewToggle<CR>\r\n     inoremap <F5> <ESC>:AutoPreviewToggle<CR>i\r\n\r\n     \" set the time(ms) break to refresh the preview window, I recommend 500ms~1000ms with good experience\r\n     set updatetime=500\r\n\r\n#3 Restart Vim. \r\n     (Press F5 to enable the plugin if you set \"let g:AutoPreview_enabled =0\")\r\n     Just Enjoy It!","5":"If you haven't installed taglist, please install it first: http:\/\/vim.sourceforge.net\/scripts\/script.php?script_id=273\r\n\r\n#1 Download autopreview.vim into your favorite plugin directory or source the script from your .vimrc file (_vimrc for windows)\r\n\r\n#2 Add the following context into your .vimrc file\r\n     \" Automatically enable the preview function with vim starting\r\n     let g:AutoPreview_enabled =1\r\n\r\n     \" make you could press F5 key to enable or disable the preview window, you can also set to other favorite hotkey here\r\n     nnoremap <F5> :AutoPreviewToggle<CR>\r\n     inoremap <F5> <ESC>:AutoPreviewToggle<CR>i\r\n\r\n     \" set the time(ms) break to refresh the preview window, I recommend 500ms~1000ms with good experience\r\n     set updatetime=500\r\n\r\n#3 Restart Vim. \r\n     (Press F5 to enable the plugin if you set \"let g:AutoPreview_enabled =0\")\r\n     Just Enjoy It!","first_name":"Baohua","6":"Baohua","last_name":"Yang","7":"Yang","releases":[{"0":"2228","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"a stable and total version\r\nseveral changes list below:\r\nadd highlight effect with previewword\r\ndeal with folded codes\r\nsome changes with the use guide document","3":"a stable and total version\r\nseveral changes list below:\r\nadd highlight effect with previewword\r\ndeal with folded codes\r\nsome changes with the use guide document","package":"autopreview.vim","4":"autopreview.vim","src_id":"9037","5":"9037","creation_date":"1217298028","6":"1217298028"},{"0":"2228","vim_version":"7.0","1":"7.0","script_version":"0.2","2":"0.2","version_comment":"Release 0.2: cleanup, optimize and enhance based on release v0.1\r\nThanks to Liu Yubao <yubao.liu@gmail.com>","3":"Release 0.2: cleanup, optimize and enhance based on release v0.1\r\nThanks to Liu Yubao <yubao.liu@gmail.com>","package":"autopreview.vim","4":"autopreview.vim","src_id":"8673","5":"8673","creation_date":"1210553129","6":"1210553129"},{"0":"2228","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"autopreview.vim","4":"autopreview.vim","src_id":"8650","5":"8650","creation_date":"1210070501","6":"1210070501"}]},"2227":{"script_id":"2227","0":"2227","script_name":"browser.vim","1":"browser.vim","script_type":"utility","2":"utility","summary":"a lightweight web browser opening in a split window for wikipedia etc.","3":"a lightweight web browser opening in a split window for wikipedia etc.","description":"               Repo is here. https:\/\/github.com\/mjbrownie\/browser.vim\r\n               \r\n               This plugin opens a website by making a lynx -dump call behind\r\n               the scenes and takes advantage of the dumps link references so\r\n               you can click on links and browse through a site.\r\n\r\n               It seems to work well on wikipedia and any text friendly sites\r\n               when all you want is a quick definition to settle a factual debate... etc. \r\n\r\n               Included are some 'K' keywordprg modifications to give you some ideas. \r\n                (If you have any file type specific suggestions please email them to me)\r\n\r\n               :WebBrowser www.vim.org\r\n               To open a web page\r\n\r\n               :Wikipedia the life of brian\r\n               Will open en.wikipedia.org\/wiki\/<search term> \r\n               :Google <search term>\r\n               Opens google to the search term\r\n\r\n               :GoogleLucky <search term>\r\n               Opens Lucky Google search \r\n\r\n               you can also create your own site specific googling eg.  \r\n               com! -nargs=+ GooglePythonDoc call OpenGoogle(<q-args>, 0 , 'docs.python.org')\r\n               (make the second arg 1 for lucky)\r\n               \r\n               Within the browser view the <tab> key cycles through links and\r\n               pressing <cr> will open a link. \r\n\r\n               the u key seems to work ok as a back button","4":"               Repo is here. https:\/\/github.com\/mjbrownie\/browser.vim\r\n               \r\n               This plugin opens a website by making a lynx -dump call behind\r\n               the scenes and takes advantage of the dumps link references so\r\n               you can click on links and browse through a site.\r\n\r\n               It seems to work well on wikipedia and any text friendly sites\r\n               when all you want is a quick definition to settle a factual debate... etc. \r\n\r\n               Included are some 'K' keywordprg modifications to give you some ideas. \r\n                (If you have any file type specific suggestions please email them to me)\r\n\r\n               :WebBrowser www.vim.org\r\n               To open a web page\r\n\r\n               :Wikipedia the life of brian\r\n               Will open en.wikipedia.org\/wiki\/<search term> \r\n               :Google <search term>\r\n               Opens google to the search term\r\n\r\n               :GoogleLucky <search term>\r\n               Opens Lucky Google search \r\n\r\n               you can also create your own site specific googling eg.  \r\n               com! -nargs=+ GooglePythonDoc call OpenGoogle(<q-args>, 0 , 'docs.python.org')\r\n               (make the second arg 1 for lucky)\r\n               \r\n               Within the browser view the <tab> key cycles through links and\r\n               pressing <cr> will open a link. \r\n\r\n               the u key seems to work ok as a back button","install_details":"This script requires the lynx browser\r\n\r\nPlace browser.vim in your plugin folder\r\n\r\nalso I recommend the pathogen\/vundle plugins for installs\r\n\r\nthen you can just \r\n\r\ngit clone https:\/\/github.com\/mjbrownie\/browser.vim.git ~\/.vim\/bundle\/browser","5":"This script requires the lynx browser\r\n\r\nPlace browser.vim in your plugin folder\r\n\r\nalso I recommend the pathogen\/vundle plugins for installs\r\n\r\nthen you can just \r\n\r\ngit clone https:\/\/github.com\/mjbrownie\/browser.vim.git ~\/.vim\/bundle\/browser","first_name":"Michael","6":"Michael","last_name":"Brown","7":"Brown","releases":[{"0":"2227","vim_version":"6.0","1":"6.0","script_version":"0.1.1","2":"0.1.1","version_comment":"Fixed a bug with Google site: and added an escape for ? affecting zsh. Thanks Rainer","3":"Fixed a bug with Google site: and added an escape for ? affecting zsh. Thanks Rainer","package":"browser.vim","4":"browser.vim","src_id":"8647","5":"8647","creation_date":"1210010537","6":"1210010537"},{"0":"2227","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"browser.vim","4":"browser.vim","src_id":"8645","5":"8645","creation_date":"1209929123","6":"1209929123"}]},"2226":{"script_id":"2226","0":"2226","script_name":"vimwiki","1":"vimwiki","script_type":"utility","2":"utility","summary":"Personal Wiki for Vim","3":"Personal Wiki for Vim","description":"A Personal Wiki For Vim Plugin\r\n==============================================================================\r\nScreenshots are available on http:\/\/code.google.com\/p\/vimwiki\/ \r\nThere are also zipped vimwiki files there in case you do not like vimball archives.\r\n\r\n\r\nPrerequisites\r\n==============================================================================\r\nMake sure you have these settings in your vimrc file: \r\n\r\nset nocompatible\r\nfiletype plugin on\r\nsyntax on\r\n\r\nWithout them Vimwiki will not work properly.\r\n\r\n\r\nIntro\r\n==============================================================================\r\nVimwiki is a personal wiki for Vim -- a number of linked text files that have\r\ntheir own syntax highlighting.\r\n\r\nWith vimwiki you can:\r\n    - organize notes and ideas;\r\n    - manage todo-lists;\r\n    - write documentation.\r\n\r\nTo do a quick start press <Leader>ww (this is usually \\ww) to go to your index\r\nwiki file.  By default it is located in: \r\n    ~\/vimwiki\/index.wiki\r\n\r\nFeed it with the following example:\r\n\r\n= My knowledge base =\r\n    * Tasks -- things to be done _yesterday_!!!\r\n    * Project Gutenberg -- good books are power.\r\n    * Scratchpad -- various temporary stuff.\r\n\r\nPlace your cursor on 'Tasks' and press Enter to create a link.  Once pressed,\r\n'Tasks' will become '[[Tasks]]' -- a vimwiki link.  Press Enter again to\r\nopen it.  Edit the file, save it, and then press Backspace to jump back to your\r\nindex.\r\n\r\nA vimwiki link can be constructed from more than one word.  Just visually\r\nselect the words to be linked and press Enter.  Try it with 'Project\r\nGutenberg'.  The result should look something like:\r\n\r\n= My knowledge base =\r\n    * [[Tasks]] -- things to be done _yesterday_!!!\r\n    * [[Project Gutenberg]] -- good books are power.\r\n    * Scratchpad -- various temporary stuff.\r\n\r\n\r\nFor the various options see :h vimwiki-options.\r\n\r\n\r\nBasic Markup\r\n==============================================================================\r\nsee :h vimwiki-syntax\r\n\r\n*bold* -- bold \r\n_italic_ -- italic \r\n\r\n[[wiki link]] -- link with spaces\r\n[[wiki link|description]] -- link with description\r\n\r\nLists:\r\n* bullet list item 1\r\n    - bullet list item 2\r\n    - bullet list item 3\r\n        * bullet list item 4\r\n        * bullet list item 5\r\n* bullet list item 6\r\n* bullet list item 7\r\n    - bullet list item 8\r\n    - bullet list item 9\r\n\r\n# numbered list item 1\r\n# numbered list item 2\r\n    # numbered list item 3\r\n    # numbered list item 4\r\n\r\n= Header1 =\r\n== Header2 ==\r\n=== Header3 ===\r\n\r\n\r\nKey bindings\r\n==============================================================================\r\nsee :h vimwiki-mappings\r\n\r\nnormal mode: \r\n<Leader>ww -- Open default wiki index file.\r\n<Leader>wt -- Open default wiki index file in a new tab.\r\n<Leader>ws -- Select and open wiki index file.\r\n<Leader>wd -- Delete wiki file you are in.\r\n<Leader>wr -- Rename wiki file you are in.\r\n<Enter> -- Folow\/Create wiki link\r\n<Shift-Enter> -- Split and folow\/create wiki link\r\n<Ctrl-Enter> -- Vertical split and folow\/create wiki link\r\n<Backspace> -- Go back to parent(previous) wiki link\r\n<Tab> -- Find next wiki link\r\n<Shift-Tab> -- Find previous wiki link\r\n\r\n\r\nCommands\r\n==============================================================================\r\n:Vimwiki2HTML -- Convert current wiki link to HTML\r\n:VimwikiAll2HTML -- Convert all your wiki links to HTML\r\n","4":"A Personal Wiki For Vim Plugin\r\n==============================================================================\r\nScreenshots are available on http:\/\/code.google.com\/p\/vimwiki\/ \r\nThere are also zipped vimwiki files there in case you do not like vimball archives.\r\n\r\n\r\nPrerequisites\r\n==============================================================================\r\nMake sure you have these settings in your vimrc file: \r\n\r\nset nocompatible\r\nfiletype plugin on\r\nsyntax on\r\n\r\nWithout them Vimwiki will not work properly.\r\n\r\n\r\nIntro\r\n==============================================================================\r\nVimwiki is a personal wiki for Vim -- a number of linked text files that have\r\ntheir own syntax highlighting.\r\n\r\nWith vimwiki you can:\r\n    - organize notes and ideas;\r\n    - manage todo-lists;\r\n    - write documentation.\r\n\r\nTo do a quick start press <Leader>ww (this is usually \\ww) to go to your index\r\nwiki file.  By default it is located in: \r\n    ~\/vimwiki\/index.wiki\r\n\r\nFeed it with the following example:\r\n\r\n= My knowledge base =\r\n    * Tasks -- things to be done _yesterday_!!!\r\n    * Project Gutenberg -- good books are power.\r\n    * Scratchpad -- various temporary stuff.\r\n\r\nPlace your cursor on 'Tasks' and press Enter to create a link.  Once pressed,\r\n'Tasks' will become '[[Tasks]]' -- a vimwiki link.  Press Enter again to\r\nopen it.  Edit the file, save it, and then press Backspace to jump back to your\r\nindex.\r\n\r\nA vimwiki link can be constructed from more than one word.  Just visually\r\nselect the words to be linked and press Enter.  Try it with 'Project\r\nGutenberg'.  The result should look something like:\r\n\r\n= My knowledge base =\r\n    * [[Tasks]] -- things to be done _yesterday_!!!\r\n    * [[Project Gutenberg]] -- good books are power.\r\n    * Scratchpad -- various temporary stuff.\r\n\r\n\r\nFor the various options see :h vimwiki-options.\r\n\r\n\r\nBasic Markup\r\n==============================================================================\r\nsee :h vimwiki-syntax\r\n\r\n*bold* -- bold \r\n_italic_ -- italic \r\n\r\n[[wiki link]] -- link with spaces\r\n[[wiki link|description]] -- link with description\r\n\r\nLists:\r\n* bullet list item 1\r\n    - bullet list item 2\r\n    - bullet list item 3\r\n        * bullet list item 4\r\n        * bullet list item 5\r\n* bullet list item 6\r\n* bullet list item 7\r\n    - bullet list item 8\r\n    - bullet list item 9\r\n\r\n# numbered list item 1\r\n# numbered list item 2\r\n    # numbered list item 3\r\n    # numbered list item 4\r\n\r\n= Header1 =\r\n== Header2 ==\r\n=== Header3 ===\r\n\r\n\r\nKey bindings\r\n==============================================================================\r\nsee :h vimwiki-mappings\r\n\r\nnormal mode: \r\n<Leader>ww -- Open default wiki index file.\r\n<Leader>wt -- Open default wiki index file in a new tab.\r\n<Leader>ws -- Select and open wiki index file.\r\n<Leader>wd -- Delete wiki file you are in.\r\n<Leader>wr -- Rename wiki file you are in.\r\n<Enter> -- Folow\/Create wiki link\r\n<Shift-Enter> -- Split and folow\/create wiki link\r\n<Ctrl-Enter> -- Vertical split and folow\/create wiki link\r\n<Backspace> -- Go back to parent(previous) wiki link\r\n<Tab> -- Find next wiki link\r\n<Shift-Tab> -- Find previous wiki link\r\n\r\n\r\nCommands\r\n==============================================================================\r\n:Vimwiki2HTML -- Convert current wiki link to HTML\r\n:VimwikiAll2HTML -- Convert all your wiki links to HTML\r\n","install_details":"Windows:\r\n========\r\n1. Unpack. \r\n2. Open vimwiki-N-N.vba with Vim. (N-N is version number ie 1-1) \r\n3. Source it with :so % command \r\n\r\nLinux:\r\n======\r\n1. Open vimwiki-N-N.vba.gz with Vim. (N-N is version number ie 1-1) \r\n2. Source it with :so % command \r\n","5":"Windows:\r\n========\r\n1. Unpack. \r\n2. Open vimwiki-N-N.vba with Vim. (N-N is version number ie 1-1) \r\n3. Source it with :so % command \r\n\r\nLinux:\r\n======\r\n1. Open vimwiki-N-N.vba.gz with Vim. (N-N is version number ie 1-1) \r\n2. Source it with :so % command \r\n","first_name":"Maxim","6":"Maxim","last_name":"Kim","7":"Kim","releases":[{"0":"2226","vim_version":"7.3","1":"7.3","script_version":"2.1","2":"2.1","version_comment":"    * Concealing of links can be turned off - set |g:vimwiki_url_maxsave| to 0.\r\n      The option g:vimwiki_url_mingain was removed\r\n    * |g:vimwiki_folding| also accepts value 'list'; with 'expr' both sections\r\n      and code blocks folded, g:vimwiki_fold_lists option was removed\r\n    * Issue 261: Syntax folding is back. |g:vimwiki_folding| values are\r\n      changed to '', 'expr', 'syntax'.\r\n    * Issue 372: Ignore case in g:vimwiki_valid_html_tags\r\n    * Issue 374: Make autowriteall local to vimwiki. It is not 100% local\r\n      though.\r\n    * Issue 384: Custom_wiki2html script now receives templating arguments\r\n    * Issue 393: Custom_wiki2html script path can contain tilde character\r\n    * Issue 392: Custom_wiki2html arguments are quoted, e.g names with spaces\r\n    * Various small bug fixes.\r\n","3":"    * Concealing of links can be turned off - set |g:vimwiki_url_maxsave| to 0.\r\n      The option g:vimwiki_url_mingain was removed\r\n    * |g:vimwiki_folding| also accepts value 'list'; with 'expr' both sections\r\n      and code blocks folded, g:vimwiki_fold_lists option was removed\r\n    * Issue 261: Syntax folding is back. |g:vimwiki_folding| values are\r\n      changed to '', 'expr', 'syntax'.\r\n    * Issue 372: Ignore case in g:vimwiki_valid_html_tags\r\n    * Issue 374: Make autowriteall local to vimwiki. It is not 100% local\r\n      though.\r\n    * Issue 384: Custom_wiki2html script now receives templating arguments\r\n    * Issue 393: Custom_wiki2html script path can contain tilde character\r\n    * Issue 392: Custom_wiki2html arguments are quoted, e.g names with spaces\r\n    * Various small bug fixes.\r\n","package":"vimwiki-2-1.vba.gz","4":"vimwiki-2-1.vba.gz","src_id":"19815","5":"19815","creation_date":"1365953548","6":"1365953548"},{"0":"2226","vim_version":"7.3","1":"7.3","script_version":"2.0.1.stu","2":"2.0.1.stu","version_comment":"\r\n  * Follow (i.e. open target of) markdown reference-style links.\r\n  * Bug fixes.\r\n","3":"\r\n  * Follow (i.e. open target of) markdown reference-style links.\r\n  * Bug fixes.\r\n","package":"vimwiki-2-0-1.vba.gz","4":"vimwiki-2-0-1.vba.gz","src_id":"18232","5":"18232","creation_date":"1341645395","6":"1341645395"},{"0":"2226","vim_version":"7.3","1":"7.3","script_version":"2.0.stu","2":"2.0.stu","version_comment":"This release is partly incompatible with 1.2.\r\n\r\nYou should delete previous version of vimwiki before install.\r\n\r\n= Summary =\r\n\r\n    * Quick page-link creation.\r\n    * Redesign of link syntaxes (!)\r\n        * No more CamelCase links. Check the ways to convert them http:\/\/goo.gl\/15ctX\r\n        * No more [[link][desc]] links.\r\n        * No more [http:\/\/link description] links.\r\n        * No more plain image links. Use transclusions.\r\n        * No more image links identified by extension. Use transclusions.\r\n    * Interwiki links.\r\n    * Link schemes.\r\n    * Transclusions.\r\n    * Normalize link command.\r\n    * Improved diary organization and generation.\r\n    * List manipulation.\r\n    * Markdown support.\r\n    * Mathjax support.\r\n    * Improved handling of special characters and punctuation in filenames and urls.\r\n    * Back links command: list links referring to the current page.\r\n    * Highlighting nonexisted links are off by default.\r\n    * Table syntax change. Row separator uses | instead of +.\r\n    * Fold multilined list items.\r\n    * Custom wiki to HTML converters.\r\n    * Conceal long weblinks.\r\n    * Option to disable table mappings.\r\n\r\nFor detailed information see issues list on\r\nhttp:\/\/code.google.com\/p\/vimwiki\/issues\/list\r\n","3":"This release is partly incompatible with 1.2.\r\n\r\nYou should delete previous version of vimwiki before install.\r\n\r\n= Summary =\r\n\r\n    * Quick page-link creation.\r\n    * Redesign of link syntaxes (!)\r\n        * No more CamelCase links. Check the ways to convert them http:\/\/goo.gl\/15ctX\r\n        * No more [[link][desc]] links.\r\n        * No more [http:\/\/link description] links.\r\n        * No more plain image links. Use transclusions.\r\n        * No more image links identified by extension. Use transclusions.\r\n    * Interwiki links.\r\n    * Link schemes.\r\n    * Transclusions.\r\n    * Normalize link command.\r\n    * Improved diary organization and generation.\r\n    * List manipulation.\r\n    * Markdown support.\r\n    * Mathjax support.\r\n    * Improved handling of special characters and punctuation in filenames and urls.\r\n    * Back links command: list links referring to the current page.\r\n    * Highlighting nonexisted links are off by default.\r\n    * Table syntax change. Row separator uses | instead of +.\r\n    * Fold multilined list items.\r\n    * Custom wiki to HTML converters.\r\n    * Conceal long weblinks.\r\n    * Option to disable table mappings.\r\n\r\nFor detailed information see issues list on\r\nhttp:\/\/code.google.com\/p\/vimwiki\/issues\/list\r\n","package":"vimwiki-2-0-stu.vba.gz","4":"vimwiki-2-0-stu.vba.gz","src_id":"18100","5":"18100","creation_date":"1339083280","6":"1339083280"},{"0":"2226","vim_version":"7.3","1":"7.3","script_version":"1.2","2":"1.2","version_comment":"= Note =\r\nRemove previous version of vimwiki before install - files in autoload dir is moved\/renamed to autoload\/vimwiki dir. \r\n\r\n= Changelog = \r\n* Issue 70: Table spanning cell support.\r\n* Issue 72: Do not convert again for unchanged file. |:VimwikiAll2HTML|\r\n  converts only changed wiki files.\r\n* Issue 117: |VimwikiDiaryIndex| command that opens diary index wiki page.\r\n* Issue 120: Links in headers are not highlighted in vimwiki but are\r\n  highlighted in HTML.\r\n* Issue 138: Added possibility to remap table-column move bindings. See\r\n  |:VimwikiTableMoveColumnLeft| and |:VimwikiTableMoveColumnRight|\r\n  commands. For remap instructions see |vimwiki_<A-Left>|\r\n  and |vimwiki_<A-Right>|.\r\n* Issue 125: Problem with 'o' command given while at the of the file.\r\n* Issue 131: FileType is not set up when GUIEnter autocommand is used in\r\n  vimrc. Use 'nested' in 'au GUIEnter * nested VimwikiIndex'\r\n* Issue 132: Link to perl (or any non-wiki) file in vimwiki subdirectory\r\n  doesn't work as intended.\r\n* Issue 135: %title and %toc used together cause TOC to appear in an\r\n  unexpected place in HTML.\r\n* Issue 139: |:VimwikiTabnewLink| command is added.\r\n* Fix of g:vimwiki_stripsym = '' (i.e. an empty string) -- it removes bad\r\n  symbols from filenames.\r\n* Issue 145: With modeline 'set ft=vimwiki' links are not correctly\r\n  highlighted when open wiki files. \r\n* Issue 146: Filetype difficulty with \".txt\" as a vimwiki extension.\r\n* Issue 148: There are no mailto links.\r\n* Issue 151: Use location list instead of quickfix list for :VimwikiSearch\r\n  command result. Use :lopen instead of :copen, :lnext instead of :cnext\r\n  etc.\r\n* Issue 152: Add the list of HTML files that would not be deleted after\r\n  |:VimwikiAll2HTML|.\r\n* Issue 153: Delete HTML files that has no corresponding wiki ones with\r\n  |:VimwikiAll2HTML|.\r\n* Issue 156: Add multiple HTML templates. See\r\n  |vimwiki-option-template_path|. Options html_header and html_footer are\r\n  no longer exist.\r\n* Issue 173: When virtualedit=all option is enabled the 'o' command behave\r\n  strange.\r\n* Issue 178: Problem with alike wikie's paths.\r\n* Issue 182: Browser command does not quote url.\r\n* Issue 183: Spelling error highlighting is not possible with nested\r\n  syntaxes.\r\n* Issue 184: Wrong foldlevel in some cases.\r\n* Issue 195: Page renaming issue.\r\n* Issue 196: vim: modeline bug -- syn=vim doesn't work.\r\n* Issue 199: Generated HTML for sublists is invalid.\r\n* Issue 200: Generated HTML for todo lists does not show completion status\r\n  the fix relies on CSS, thus your old stylesheets need to be updated!;\r\n  may not work in obsolete browsers or font-deficient systems.\r\n* Issue 205: Block code: highlighting differs from processing. Inline code\r\n  block {{{ ... }}} is removed. Use `...` instead.\r\n* Issue 208: Default highlight colors are problematic in many\r\n  colorschemes. Headers are highlighted as |hl-Title| by default, use\r\n  |g:vimwiki_hl_headers| to restore previous default Red, Green, Blue or\r\n  custom header colors. Some other changes in highlighting.\r\n* Issue 209: Wild comments slow down html generation. Comments are\r\n  changed, use %% to comment out entire line.\r\n* Issue 210: HTML: para enclose header.\r\n* Issue 214: External links containing Chinese characters get trimmed.\r\n* Issue 218: Command to generate HTML file and open it in webbrowser. See\r\n  |:Vimwiki2HTMLBrowse|(bind to <leader>whh)\r\n* NEW: Added <Leader>wh mapping to call |:Vimwiki2HTML|\r\n","3":"= Note =\r\nRemove previous version of vimwiki before install - files in autoload dir is moved\/renamed to autoload\/vimwiki dir. \r\n\r\n= Changelog = \r\n* Issue 70: Table spanning cell support.\r\n* Issue 72: Do not convert again for unchanged file. |:VimwikiAll2HTML|\r\n  converts only changed wiki files.\r\n* Issue 117: |VimwikiDiaryIndex| command that opens diary index wiki page.\r\n* Issue 120: Links in headers are not highlighted in vimwiki but are\r\n  highlighted in HTML.\r\n* Issue 138: Added possibility to remap table-column move bindings. See\r\n  |:VimwikiTableMoveColumnLeft| and |:VimwikiTableMoveColumnRight|\r\n  commands. For remap instructions see |vimwiki_<A-Left>|\r\n  and |vimwiki_<A-Right>|.\r\n* Issue 125: Problem with 'o' command given while at the of the file.\r\n* Issue 131: FileType is not set up when GUIEnter autocommand is used in\r\n  vimrc. Use 'nested' in 'au GUIEnter * nested VimwikiIndex'\r\n* Issue 132: Link to perl (or any non-wiki) file in vimwiki subdirectory\r\n  doesn't work as intended.\r\n* Issue 135: %title and %toc used together cause TOC to appear in an\r\n  unexpected place in HTML.\r\n* Issue 139: |:VimwikiTabnewLink| command is added.\r\n* Fix of g:vimwiki_stripsym = '' (i.e. an empty string) -- it removes bad\r\n  symbols from filenames.\r\n* Issue 145: With modeline 'set ft=vimwiki' links are not correctly\r\n  highlighted when open wiki files. \r\n* Issue 146: Filetype difficulty with \".txt\" as a vimwiki extension.\r\n* Issue 148: There are no mailto links.\r\n* Issue 151: Use location list instead of quickfix list for :VimwikiSearch\r\n  command result. Use :lopen instead of :copen, :lnext instead of :cnext\r\n  etc.\r\n* Issue 152: Add the list of HTML files that would not be deleted after\r\n  |:VimwikiAll2HTML|.\r\n* Issue 153: Delete HTML files that has no corresponding wiki ones with\r\n  |:VimwikiAll2HTML|.\r\n* Issue 156: Add multiple HTML templates. See\r\n  |vimwiki-option-template_path|. Options html_header and html_footer are\r\n  no longer exist.\r\n* Issue 173: When virtualedit=all option is enabled the 'o' command behave\r\n  strange.\r\n* Issue 178: Problem with alike wikie's paths.\r\n* Issue 182: Browser command does not quote url.\r\n* Issue 183: Spelling error highlighting is not possible with nested\r\n  syntaxes.\r\n* Issue 184: Wrong foldlevel in some cases.\r\n* Issue 195: Page renaming issue.\r\n* Issue 196: vim: modeline bug -- syn=vim doesn't work.\r\n* Issue 199: Generated HTML for sublists is invalid.\r\n* Issue 200: Generated HTML for todo lists does not show completion status\r\n  the fix relies on CSS, thus your old stylesheets need to be updated!;\r\n  may not work in obsolete browsers or font-deficient systems.\r\n* Issue 205: Block code: highlighting differs from processing. Inline code\r\n  block {{{ ... }}} is removed. Use `...` instead.\r\n* Issue 208: Default highlight colors are problematic in many\r\n  colorschemes. Headers are highlighted as |hl-Title| by default, use\r\n  |g:vimwiki_hl_headers| to restore previous default Red, Green, Blue or\r\n  custom header colors. Some other changes in highlighting.\r\n* Issue 209: Wild comments slow down html generation. Comments are\r\n  changed, use %% to comment out entire line.\r\n* Issue 210: HTML: para enclose header.\r\n* Issue 214: External links containing Chinese characters get trimmed.\r\n* Issue 218: Command to generate HTML file and open it in webbrowser. See\r\n  |:Vimwiki2HTMLBrowse|(bind to <leader>whh)\r\n* NEW: Added <Leader>wh mapping to call |:Vimwiki2HTML|\r\n","package":"vimwiki-1-2.vba.gz","4":"vimwiki-1-2.vba.gz","src_id":"15854","5":"15854","creation_date":"1307815838","6":"1307815838"},{"0":"2226","vim_version":"7.0","1":"7.0","script_version":"1.1.1","2":"1.1.1","version_comment":"Follow up bugfix release.\r\n* FIX: Issue 122: Dot character in vimwiki's directory path isn't escaped.\r\n* FIX: Issue 123: Where is Vimwiki2HTML and other commands? Sometimes filetype is not set up to vimwiki.\r\n* FIX: Issue 124: Highlight group not found: Normal","3":"Follow up bugfix release.\r\n* FIX: Issue 122: Dot character in vimwiki's directory path isn't escaped.\r\n* FIX: Issue 123: Where is Vimwiki2HTML and other commands? Sometimes filetype is not set up to vimwiki.\r\n* FIX: Issue 124: Highlight group not found: Normal","package":"vimwiki-1-1-1.vba.gz","4":"vimwiki-1-1-1.vba.gz","src_id":"13756","5":"13756","creation_date":"1283536151","6":"1283536151"},{"0":"2226","vim_version":"7.3","1":"7.3","script_version":"1.1","2":"1.1","version_comment":"\r\n* NEW: Issue 57: Make it possible to have pre block inside list item.\r\n* NEW: Issue 82: Add quick goto command. See |:VimwikiGoto|.\r\n* NEW: Issue 83: Quick switch in diary. See |:VimwikiDiaryNextDay| and\r\n  |:VimwikiDiaryPrevDay| commands.\r\n* FIX: Issue 84: Vimwiki rename removed the WikiWord display name.\r\n* FIX: Issue 85: Errors if you have '~' subdirectory in a wiki directory.\r\n* FIX: Issue 86: Existed links '[[WikiLink1|Alias1]] | [[WikiLink2]]' are\r\n  highlighted as a single link.\r\n* FIX: Issue 88: Underline text. See |g:vimwiki_valid_html_tags|.\r\n* FIX: Issue 92: Wikies in a subdir could be renamed to an empty file.\r\n* FIX: Issue 93: Use alias name in html title. See |vimwiki-title|.\r\n* FIX: Issue 94: Relative links to PHP files are broken. See\r\n  |g:vimwiki_file_exts| for details.\r\n* FIX: Issue 96: Closing bracket at the end of weblink shouldn't be a part\r\n  of that link.\r\n* FIX: Issue 97: Error opening weblink in a browser if it has # inside.\r\n* FIX: Issue 99: Vim is not responing while opening arbitrary wiki file.\r\n* FIX: Issue 100: Additional content on diary index page could be\r\n  corrupted.\r\n* NEW: Issue 101: Customized HTML tags. See |g:vimwiki_valid_html_tags|\r\n* NEW: Issue 102: Conceal feature usage. See |g:vimwiki_conceallevel|.\r\n* FIX: Issue 103: Always highlight links to non-wiki files as existed.\r\n* FIX: Issue 104: vimwiki#nested_syntax needs 'keepend' to avoid contained\r\n  language syntax eat needed '}}}'.\r\n* FIX: Issue 105: <i_CR> on a todo list item with [ ] doesn't create new\r\n  todo list item.\r\n* FIX: Issue 106: With MediaWiki syntax <C-Space> on a child todo list\r\n  item produce errors.\r\n* FIX: Issue 107: With MediaWiki syntax <C-Space> on a list item creates\r\n  todo list item without space between * and [ ].\r\n* FIX: Issue 110: Syntax highlighting doesn't work for indented codeblock.\r\n* FIX: Issue 115: Nested Perl syntax highlighting differs from regular\r\n  one.\r\n* MISC: Many vimwiki commands were renamed from Vimwiki.*Word to\r\n  Vimwiki.*Link. VimwikiGoHome is renamed to VimwikiIndex,\r\n  VimwikiTabGoHome to VimwikiTabIndex.\r\n* MISC: vimwiki-option-gohome is removed.\r\n","3":"\r\n* NEW: Issue 57: Make it possible to have pre block inside list item.\r\n* NEW: Issue 82: Add quick goto command. See |:VimwikiGoto|.\r\n* NEW: Issue 83: Quick switch in diary. See |:VimwikiDiaryNextDay| and\r\n  |:VimwikiDiaryPrevDay| commands.\r\n* FIX: Issue 84: Vimwiki rename removed the WikiWord display name.\r\n* FIX: Issue 85: Errors if you have '~' subdirectory in a wiki directory.\r\n* FIX: Issue 86: Existed links '[[WikiLink1|Alias1]] | [[WikiLink2]]' are\r\n  highlighted as a single link.\r\n* FIX: Issue 88: Underline text. See |g:vimwiki_valid_html_tags|.\r\n* FIX: Issue 92: Wikies in a subdir could be renamed to an empty file.\r\n* FIX: Issue 93: Use alias name in html title. See |vimwiki-title|.\r\n* FIX: Issue 94: Relative links to PHP files are broken. See\r\n  |g:vimwiki_file_exts| for details.\r\n* FIX: Issue 96: Closing bracket at the end of weblink shouldn't be a part\r\n  of that link.\r\n* FIX: Issue 97: Error opening weblink in a browser if it has # inside.\r\n* FIX: Issue 99: Vim is not responing while opening arbitrary wiki file.\r\n* FIX: Issue 100: Additional content on diary index page could be\r\n  corrupted.\r\n* NEW: Issue 101: Customized HTML tags. See |g:vimwiki_valid_html_tags|\r\n* NEW: Issue 102: Conceal feature usage. See |g:vimwiki_conceallevel|.\r\n* FIX: Issue 103: Always highlight links to non-wiki files as existed.\r\n* FIX: Issue 104: vimwiki#nested_syntax needs 'keepend' to avoid contained\r\n  language syntax eat needed '}}}'.\r\n* FIX: Issue 105: <i_CR> on a todo list item with [ ] doesn't create new\r\n  todo list item.\r\n* FIX: Issue 106: With MediaWiki syntax <C-Space> on a child todo list\r\n  item produce errors.\r\n* FIX: Issue 107: With MediaWiki syntax <C-Space> on a list item creates\r\n  todo list item without space between * and [ ].\r\n* FIX: Issue 110: Syntax highlighting doesn't work for indented codeblock.\r\n* FIX: Issue 115: Nested Perl syntax highlighting differs from regular\r\n  one.\r\n* MISC: Many vimwiki commands were renamed from Vimwiki.*Word to\r\n  Vimwiki.*Link. VimwikiGoHome is renamed to VimwikiIndex,\r\n  VimwikiTabGoHome to VimwikiTabIndex.\r\n* MISC: vimwiki-option-gohome is removed.\r\n","package":"vimwiki-1-1.vba.gz","4":"vimwiki-1-1.vba.gz","src_id":"13667","5":"13667","creation_date":"1282674134","6":"1282674134"},{"0":"2226","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"* NEW: Issue 41: Table cell and column text objects. See `vimwiki-text-objects`.\r\n* NEW: Issue 42: Commands to move table columns left and right. See `:VimwikiTableMoveColumnLeft` and `:VimwikiTableMoveColumnRight`.\r\n* NEW: Issue 44: `<S-Tab>` should move cursor to the previous table cell.\r\n* NEW: Issue 45: It should be possible to indent tables. Indented tables are centered in html.\r\n* NEW: Issue 46: Do not htmlize some wiki pages (blacklist). New placeholder is added: `%nohtml`. See `vimwiki-nohtml`.\r\n* FIX: Issue 47: Lists aren't HTMLized properly.\r\n* FIX: Issue 48: With autochdir it is impossible to have path_html such as `d:\\vimwiki\\html\\`\r\n* FIX: Issue 49: Table is not HTMLized properly at the end of wiki page.\r\n* FIX: Issue 50: Inline formatting is not performed in table cells.\r\n* FIX: Issue 51: Cannot insert '-' (minus) into table cells of the first column.\r\n* FIX: Issue 52: Table cell width is incorrect when double wide characters are used (ie. Chinese). Check `g:vimwiki_CJK_length`.\r\n* NEW: Issue 53: Wiki markup can not nested. (Use links and inline markup in Headers).\r\n* NEW: Issue 54: Highlight for placeholders.\r\n* NEW: Issue 56: Directory indexes. See `g:vimwiki_dir_link` option and `:VimwikiGenerateLinks` command.\r\n* NEW: Issue 58: Html new lines with `<br \/>`. Could be inserted with `<S-CR>` in insert mode.\r\n* FIX: Issue 59: List item's text can't be started from `*`.\r\n* NEW: Issue 60: Links inside completed gtd-items.\r\n* NEW: Issue 61: Headers numbering. See `g:vimwiki_html_header_numbering` and `g:vimwiki_html_header_numbering_sym` options.\r\n* FIX: Issue 63: Table cannot have leading empty cells in html.\r\n* FIX: Issue 65: Table separator is not htmlized right if on top of the table.\r\n* FIX: Issue 66: Table empty cells are very small in html.\r\n* FIX: Issue 67: Wrong html conversion of multilined list item with bold text on the start of next line.\r\n* FIX: Issue 68: auto-indent problem with langmap.\r\n* FIX: Issue 73: Link navigation by Tab. \"Escaped\" wiki-word should be skipped for navigation with `<tab>`.\r\n* FIX: Issue 75: `code` syntax doesn't display correctly in toc.\r\n* FIX: Issue 77: Diary index only showing link to today's diary entry file for extensions other than '.wiki'.\r\n* FIX: Issue 79: Further calendar.vim integration -- add sign to calendar date if it has corresponding diary page.\r\n* FIX: Issue 80: Debian Lenny GUI Vim 7.2 has problems with toggling inner todo list items.\r\n* FIX: Issue 81: Don't convert `WikiWord` as a link in html when `let g:vimwiki_camel_case = 0`\r\n","3":"* NEW: Issue 41: Table cell and column text objects. See `vimwiki-text-objects`.\r\n* NEW: Issue 42: Commands to move table columns left and right. See `:VimwikiTableMoveColumnLeft` and `:VimwikiTableMoveColumnRight`.\r\n* NEW: Issue 44: `<S-Tab>` should move cursor to the previous table cell.\r\n* NEW: Issue 45: It should be possible to indent tables. Indented tables are centered in html.\r\n* NEW: Issue 46: Do not htmlize some wiki pages (blacklist). New placeholder is added: `%nohtml`. See `vimwiki-nohtml`.\r\n* FIX: Issue 47: Lists aren't HTMLized properly.\r\n* FIX: Issue 48: With autochdir it is impossible to have path_html such as `d:\\vimwiki\\html\\`\r\n* FIX: Issue 49: Table is not HTMLized properly at the end of wiki page.\r\n* FIX: Issue 50: Inline formatting is not performed in table cells.\r\n* FIX: Issue 51: Cannot insert '-' (minus) into table cells of the first column.\r\n* FIX: Issue 52: Table cell width is incorrect when double wide characters are used (ie. Chinese). Check `g:vimwiki_CJK_length`.\r\n* NEW: Issue 53: Wiki markup can not nested. (Use links and inline markup in Headers).\r\n* NEW: Issue 54: Highlight for placeholders.\r\n* NEW: Issue 56: Directory indexes. See `g:vimwiki_dir_link` option and `:VimwikiGenerateLinks` command.\r\n* NEW: Issue 58: Html new lines with `<br \/>`. Could be inserted with `<S-CR>` in insert mode.\r\n* FIX: Issue 59: List item's text can't be started from `*`.\r\n* NEW: Issue 60: Links inside completed gtd-items.\r\n* NEW: Issue 61: Headers numbering. See `g:vimwiki_html_header_numbering` and `g:vimwiki_html_header_numbering_sym` options.\r\n* FIX: Issue 63: Table cannot have leading empty cells in html.\r\n* FIX: Issue 65: Table separator is not htmlized right if on top of the table.\r\n* FIX: Issue 66: Table empty cells are very small in html.\r\n* FIX: Issue 67: Wrong html conversion of multilined list item with bold text on the start of next line.\r\n* FIX: Issue 68: auto-indent problem with langmap.\r\n* FIX: Issue 73: Link navigation by Tab. \"Escaped\" wiki-word should be skipped for navigation with `<tab>`.\r\n* FIX: Issue 75: `code` syntax doesn't display correctly in toc.\r\n* FIX: Issue 77: Diary index only showing link to today's diary entry file for extensions other than '.wiki'.\r\n* FIX: Issue 79: Further calendar.vim integration -- add sign to calendar date if it has corresponding diary page.\r\n* FIX: Issue 80: Debian Lenny GUI Vim 7.2 has problems with toggling inner todo list items.\r\n* FIX: Issue 81: Don't convert `WikiWord` as a link in html when `let g:vimwiki_camel_case = 0`\r\n","package":"vimwiki-1-0.vba.gz","4":"vimwiki-1-0.vba.gz","src_id":"12995","5":"12995","creation_date":"1273687585","6":"1273687585"},{"0":"2226","vim_version":"7.0","1":"7.0","script_version":"0.9.9","2":"0.9.9","version_comment":"* NEW: Diary. Help in making daily notes. See ':h vimwiki-diary'. Now you\r\n  can really easy add information into vimwiki that should be sorted out\r\n  later.\r\n* NEW: Tables are redesigned. Syntax is changed. Now they are\r\n  auto-formattable. You can navigate them with <tab> and <cr> in insert\r\n  mode. See 'vimwiki-syntax-tables' and 'vimwiki-tables' for more details. \r\n* NEW: Keyword STARTED: is added.\r\n* NEW: Words TODO:, DONE:, STARTED:, XXX:, FIXME:, FIXED: are highlighed\r\n  inside headers.\r\n* FIX: Export to html external links with 'file:\/\/' protocol. Ex:\r\n  '[file:\/\/\/home\/user1\/book.pdf my book]'.\r\n* FIX: Menu is corrupted if wiki's path contains spaces.\r\n* FIX: Settings 'wrap' and 'linebreak' are removed from ftplugin. Add them\r\n  into your personal settings file '.vim\/after\/ftplugin\/vimwiki.vim' if\r\n  needed.\r\n* NEW: Headers are highlighted in different colors by default.  See ':h\r\n  g:vimwiki_hl_headers' to turn it off.\r\n* FIX: Issue 40: Links with russian subdirs don't work.\r\n* NEW: It is now possible to generate HTML files automatically on page\r\n  save. See ':h vimwiki-option-auto_export'.\r\n","3":"* NEW: Diary. Help in making daily notes. See ':h vimwiki-diary'. Now you\r\n  can really easy add information into vimwiki that should be sorted out\r\n  later.\r\n* NEW: Tables are redesigned. Syntax is changed. Now they are\r\n  auto-formattable. You can navigate them with <tab> and <cr> in insert\r\n  mode. See 'vimwiki-syntax-tables' and 'vimwiki-tables' for more details. \r\n* NEW: Keyword STARTED: is added.\r\n* NEW: Words TODO:, DONE:, STARTED:, XXX:, FIXME:, FIXED: are highlighed\r\n  inside headers.\r\n* FIX: Export to html external links with 'file:\/\/' protocol. Ex:\r\n  '[file:\/\/\/home\/user1\/book.pdf my book]'.\r\n* FIX: Menu is corrupted if wiki's path contains spaces.\r\n* FIX: Settings 'wrap' and 'linebreak' are removed from ftplugin. Add them\r\n  into your personal settings file '.vim\/after\/ftplugin\/vimwiki.vim' if\r\n  needed.\r\n* NEW: Headers are highlighted in different colors by default.  See ':h\r\n  g:vimwiki_hl_headers' to turn it off.\r\n* FIX: Issue 40: Links with russian subdirs don't work.\r\n* NEW: It is now possible to generate HTML files automatically on page\r\n  save. See ':h vimwiki-option-auto_export'.\r\n","package":"vimwiki-0-9-9.vba.gz","4":"vimwiki-0-9-9.vba.gz","src_id":"12476","5":"12476","creation_date":"1266955604","6":"1266955604"},{"0":"2226","vim_version":"7.0","1":"7.0","script_version":"0.9.801","2":"0.9.801","version_comment":"* Issue 39:\tNot a critical error in doc\/vimwiki.txt","3":"* Issue 39:\tNot a critical error in doc\/vimwiki.txt","package":"vimwiki-0-9-801.vba.gz","4":"vimwiki-0-9-801.vba.gz","src_id":"12151","5":"12151","creation_date":"1264071112","6":"1264071112"},{"0":"2226","vim_version":"7.0","1":"7.0","script_version":"0.9.8","2":"0.9.8","version_comment":"* NEW: Rename g:vimwiki_fold_empty_lines to g:vimwiki_fold_trailing_empty_lines.\r\n* NEW: One can use - along with * to start unordered list item.\r\n* NEW: List items could be started from the first column.  As a result some\r\n  limitations appeared:\r\n    * a space after *, - or # for a list item is mandatory.\r\n    * g:vimwiki_fold_trailing_empty_lines if set to 0 folds one trailing\r\n      empty line.\r\n* NEW: Folding is off by default. Use g:vimwiki_folding to enable it.\r\n* NEW: Speed up vimwiki's folding a bit. Should lag a bit less in a long todo lists.\r\n* NEW: Centered headers. Start header with at least one space to make it html centered.\r\n* NEW: Change in default css: header's colors.\r\n* NEW: Vimwiki is aware of GetLatestVimScripts now. \r\n* FIX: Use <del> tag instead of custom <span class=\"strike\"> in html.\r\n* FIX: There are no text styling in htmlized quoted text.\r\n* FIX: set default value of g:vimwiki_fold_lists to 0 as written in this help.\r\n* FIX: Issue 33: Folded list items have wrong indentation when 'tabs' are used.\r\n* FIX: Issue 34: vimwiki#subdir got wrong dir when VimwikiGet('path') is a\r\n  symbolic link. Thanks lilydjwg for the patch.\r\n* FIX: Issue 28: todo-list auto-indent enhancement. New item should always be unchecked.\r\n* FIX: Issue 36: Change the name of the :Search command to :VimwikiSearch\r\n  as it conflicts with MultipleSearch. Alias :VWS is also available.\r\n* NEW: You can generate 'Table of contents' of your wiki page. See :h vimwiki-toc for details.","3":"* NEW: Rename g:vimwiki_fold_empty_lines to g:vimwiki_fold_trailing_empty_lines.\r\n* NEW: One can use - along with * to start unordered list item.\r\n* NEW: List items could be started from the first column.  As a result some\r\n  limitations appeared:\r\n    * a space after *, - or # for a list item is mandatory.\r\n    * g:vimwiki_fold_trailing_empty_lines if set to 0 folds one trailing\r\n      empty line.\r\n* NEW: Folding is off by default. Use g:vimwiki_folding to enable it.\r\n* NEW: Speed up vimwiki's folding a bit. Should lag a bit less in a long todo lists.\r\n* NEW: Centered headers. Start header with at least one space to make it html centered.\r\n* NEW: Change in default css: header's colors.\r\n* NEW: Vimwiki is aware of GetLatestVimScripts now. \r\n* FIX: Use <del> tag instead of custom <span class=\"strike\"> in html.\r\n* FIX: There are no text styling in htmlized quoted text.\r\n* FIX: set default value of g:vimwiki_fold_lists to 0 as written in this help.\r\n* FIX: Issue 33: Folded list items have wrong indentation when 'tabs' are used.\r\n* FIX: Issue 34: vimwiki#subdir got wrong dir when VimwikiGet('path') is a\r\n  symbolic link. Thanks lilydjwg for the patch.\r\n* FIX: Issue 28: todo-list auto-indent enhancement. New item should always be unchecked.\r\n* FIX: Issue 36: Change the name of the :Search command to :VimwikiSearch\r\n  as it conflicts with MultipleSearch. Alias :VWS is also available.\r\n* NEW: You can generate 'Table of contents' of your wiki page. See :h vimwiki-toc for details.","package":"vimwiki_0_9_8.vba.gz","4":"vimwiki_0_9_8.vba.gz","src_id":"12137","5":"12137","creation_date":"1264012656","6":"1264012656"},{"0":"2226","vim_version":"7.0","1":"7.0","script_version":"0.9.701","2":"0.9.701","version_comment":"* FIX: Issue 30: Highlighting doesn't work for checked list item.\r\n","3":"* FIX: Issue 30: Highlighting doesn't work for checked list item.\r\n","package":"vimwiki_0_9_701_vba.zip","4":"vimwiki_0_9_701_vba.zip","src_id":"11889","5":"11889","creation_date":"1260561819","6":"1260561819"},{"0":"2226","vim_version":"7.0","1":"7.0","script_version":"0.9.7","2":"0.9.7","version_comment":"* NEW: Default checkbox symbols are changed to [ ], [.], [o], [O], [X].\r\n  You can change them using |g:vimwiki-listsyms| variable.\r\n* NEW: Color group names are renamed from wikiBold, wikiItalic, etc to\r\n  VimwikiBold, VimwikiItalic, etc.\r\n* NEW: Open external links in a browser. There are default browsers\r\n  defined in |g:vimwiki_browsers| list. You can also redefine\r\n  |VimwikiWeblinkHandler| function to open weblinks in other programs.\r\n* NEW: Issue 25: Toggle the states of multiple TODO list items at a time\r\n  (in VISUAL and in VISUAL LINE modes)\r\n* NEW: Issue 26: Highlight code snippets in vimwiki's pre. See\r\n  |vimwiki-option-nested_syntaxes|. Thanks kriomant.\r\n* NEW: Issue 27: Automatic garbage deletion from html directory.\r\n* NEW: Save all open vimwiki buffers before export to html.\r\n* NEW: Issue 29: Custom :Search command.\r\n* NEW: Header text objects are now expandable in VISUAL mode. Tap 'vah' to\r\n  select a header. Tap again 'ah' to expand selection further. Thanks\r\n  Andy Wokula.\r\n* FIX: Folding settings are reset to vim defaults in a new tab (think of\r\n  \\wt) so you cannot hide things in folds.\r\n* FIX: https links in form of [https:\/\/hello.world.com] are not exported\r\n  into html. Thanks Saurabh Sarpal for the patch.\r\n","3":"* NEW: Default checkbox symbols are changed to [ ], [.], [o], [O], [X].\r\n  You can change them using |g:vimwiki-listsyms| variable.\r\n* NEW: Color group names are renamed from wikiBold, wikiItalic, etc to\r\n  VimwikiBold, VimwikiItalic, etc.\r\n* NEW: Open external links in a browser. There are default browsers\r\n  defined in |g:vimwiki_browsers| list. You can also redefine\r\n  |VimwikiWeblinkHandler| function to open weblinks in other programs.\r\n* NEW: Issue 25: Toggle the states of multiple TODO list items at a time\r\n  (in VISUAL and in VISUAL LINE modes)\r\n* NEW: Issue 26: Highlight code snippets in vimwiki's pre. See\r\n  |vimwiki-option-nested_syntaxes|. Thanks kriomant.\r\n* NEW: Issue 27: Automatic garbage deletion from html directory.\r\n* NEW: Save all open vimwiki buffers before export to html.\r\n* NEW: Issue 29: Custom :Search command.\r\n* NEW: Header text objects are now expandable in VISUAL mode. Tap 'vah' to\r\n  select a header. Tap again 'ah' to expand selection further. Thanks\r\n  Andy Wokula.\r\n* FIX: Folding settings are reset to vim defaults in a new tab (think of\r\n  \\wt) so you cannot hide things in folds.\r\n* FIX: https links in form of [https:\/\/hello.world.com] are not exported\r\n  into html. Thanks Saurabh Sarpal for the patch.\r\n","package":"vimwiki_0_9_7_vba.zip","4":"vimwiki_0_9_7_vba.zip","src_id":"11886","5":"11886","creation_date":"1260387485","6":"1260387485"},{"0":"2226","vim_version":"7.0","1":"7.0","script_version":"0.9.6","2":"0.9.6","version_comment":"* NEW: You can have multiline list items. See |vimwiki-syntax-lists|.\r\n* NEW: You can ignore newlines in multiline list items when do export to\r\n  html. See |g:vimwiki_list_ignore_newline| option.\r\n* NEW: Different checkbox symbols [.], [:], [o] are added. See\r\n  |vimwiki-todo-lists|.\r\n* NEW: Now there is no longer syntax of preformatted text that is started\r\n  by a whitespace.\r\n* NEW: Blockquotes. See |vimwiki-syntax-blockquote|.\r\n* NEW: Per wiki folding option (vimwiki-option-folding) is removed. Global\r\n  |g:vimwiki_folding| and |g:vimwiki_fold_lists| are added.\r\n* NEW: Due to being quite slow folding of list items is off by default.\r\n  Use |g:vimwiki_fold_lists| to turn it on.\r\n* NEW: If you want replace some symbols in a wikifilename use\r\n  |g:vimwiki_badsyms| option (Andreas Baldeau).\r\n* FIX: Command |:VimwikiToggleListItem| doesn't work for one of the two\r\n  wikies opened at the same time with different syntaxes.\r\n* FIX: Command |:VimwikiToggleListItem| do not switch parent checkboxes if\r\n  there are non-checkbox list items available.\r\n* FIX: Issue 24: Link error in html when write [[one.two.three]].\r\n* FIX: Rename WikiWord to something with a colon (:) does nasty things.\r\n* FIX: Command |:VimwikiToggleListItem| do not switch right if there are\r\n  list items without checkboxes in the list.\r\n","3":"* NEW: You can have multiline list items. See |vimwiki-syntax-lists|.\r\n* NEW: You can ignore newlines in multiline list items when do export to\r\n  html. See |g:vimwiki_list_ignore_newline| option.\r\n* NEW: Different checkbox symbols [.], [:], [o] are added. See\r\n  |vimwiki-todo-lists|.\r\n* NEW: Now there is no longer syntax of preformatted text that is started\r\n  by a whitespace.\r\n* NEW: Blockquotes. See |vimwiki-syntax-blockquote|.\r\n* NEW: Per wiki folding option (vimwiki-option-folding) is removed. Global\r\n  |g:vimwiki_folding| and |g:vimwiki_fold_lists| are added.\r\n* NEW: Due to being quite slow folding of list items is off by default.\r\n  Use |g:vimwiki_fold_lists| to turn it on.\r\n* NEW: If you want replace some symbols in a wikifilename use\r\n  |g:vimwiki_badsyms| option (Andreas Baldeau).\r\n* FIX: Command |:VimwikiToggleListItem| doesn't work for one of the two\r\n  wikies opened at the same time with different syntaxes.\r\n* FIX: Command |:VimwikiToggleListItem| do not switch parent checkboxes if\r\n  there are non-checkbox list items available.\r\n* FIX: Issue 24: Link error in html when write [[one.two.three]].\r\n* FIX: Rename WikiWord to something with a colon (:) does nasty things.\r\n* FIX: Command |:VimwikiToggleListItem| do not switch right if there are\r\n  list items without checkboxes in the list.\r\n","package":"vimwiki_0_9_6_vba.zip","4":"vimwiki_0_9_6_vba.zip","src_id":"11562","5":"11562","creation_date":"1256237298","6":"1256237298"},{"0":"2226","vim_version":"7.0","1":"7.0","script_version":"0.9.5","2":"0.9.5","version_comment":"  * NEW: Added g:vimwiki_global_ext to control creation of temporary wikies in a dirs that are not listed in g:vimwiki_list.\r\n  * NEW: Added g:vimwiki_hl_headers to highlight headers with different predefined colors.\r\n  * NEW: Checked [x] items are not highlighted with Comment syntax group by default. Use g:vimwiki_hl_cb_checked to turn it on.\r\n  * NEW: Added new syntax for links: [[link address][link description]].\r\n  * NEW: Added <C-@> allias of <C-Space> mapping for *nix systems.\r\n  * NEW: Added g:vimwiki_camel_case. Set it to 0 if you do not want CamelCased WikiWords to be linkified.\r\n  * FIX: Links with g:viwmiki_stripsym (default '_') [[My_Link|Text]] are not highlighted when created.\r\n  * FIX: indent\/vimwiki.vim is obsolete. If you upgrade from previous versions remove it. It causes wrong list indentation if noexpandtab is set.\r\n  * FIX: If tabs and spaces are used to indent list items html export gives error. Thanks Klaus Ethgen for report.\r\n  * FIX: Some html export fixes.","3":"  * NEW: Added g:vimwiki_global_ext to control creation of temporary wikies in a dirs that are not listed in g:vimwiki_list.\r\n  * NEW: Added g:vimwiki_hl_headers to highlight headers with different predefined colors.\r\n  * NEW: Checked [x] items are not highlighted with Comment syntax group by default. Use g:vimwiki_hl_cb_checked to turn it on.\r\n  * NEW: Added new syntax for links: [[link address][link description]].\r\n  * NEW: Added <C-@> allias of <C-Space> mapping for *nix systems.\r\n  * NEW: Added g:vimwiki_camel_case. Set it to 0 if you do not want CamelCased WikiWords to be linkified.\r\n  * FIX: Links with g:viwmiki_stripsym (default '_') [[My_Link|Text]] are not highlighted when created.\r\n  * FIX: indent\/vimwiki.vim is obsolete. If you upgrade from previous versions remove it. It causes wrong list indentation if noexpandtab is set.\r\n  * FIX: If tabs and spaces are used to indent list items html export gives error. Thanks Klaus Ethgen for report.\r\n  * FIX: Some html export fixes.","package":"vimwiki_0_9_5_vba.zip","4":"vimwiki_0_9_5_vba.zip","src_id":"11389","5":"11389","creation_date":"1253115393","6":"1253115393"},{"0":"2226","vim_version":"7.0","1":"7.0","script_version":"0.9.4","2":"0.9.4","version_comment":"  * NEW: Links with directories: [[dir_name\/Link|Text]]. Thanks Jie Wu.\r\n  * NEW: Added %root_path% template variable to get relative root dir of path_html. See vimwiki-option-html_header.\r\n  * FIX: Indent incorrect for vim without \"float\" compile option. Thanks Julian Kooij.\r\n  * FIX: Convert to html doesn't work right with links like [[foo::bar]].\r\n  * FIX: Rename wikiword doesn't work right when rename WikiWord to [[WikiWord blablabla]].\r\n  * FIX: Renaming of links with description doesn't work.\r\n  * FIX: Weblinks with commas are not highlighted.\r\n  * MISC: Some changes in default css file.","3":"  * NEW: Links with directories: [[dir_name\/Link|Text]]. Thanks Jie Wu.\r\n  * NEW: Added %root_path% template variable to get relative root dir of path_html. See vimwiki-option-html_header.\r\n  * FIX: Indent incorrect for vim without \"float\" compile option. Thanks Julian Kooij.\r\n  * FIX: Convert to html doesn't work right with links like [[foo::bar]].\r\n  * FIX: Rename wikiword doesn't work right when rename WikiWord to [[WikiWord blablabla]].\r\n  * FIX: Renaming of links with description doesn't work.\r\n  * FIX: Weblinks with commas are not highlighted.\r\n  * MISC: Some changes in default css file.","package":"vimwiki_0_9_4_vba.zip","4":"vimwiki_0_9_4_vba.zip","src_id":"11076","5":"11076","creation_date":"1248795724","6":"1248795724"},{"0":"2226","vim_version":"7.0","1":"7.0","script_version":"0.9.3","2":"0.9.3","version_comment":"  * NEW: g:vimwiki_menu option is a string which is menu path. So one can use let g:vimwiki_menu = 'Plugin.Vimwiki' to set the menu to the right place.\r\n  * NEW: g:vimwiki_fold_empty_lines -- don't or do fold in empty lines between headers. See :h g:vimwiki_fold_empty_lines\r\n  * FIX: Encoding error when running vimwiki in Windows XP Japanese.  Thanks KarasAya.\r\n","3":"  * NEW: g:vimwiki_menu option is a string which is menu path. So one can use let g:vimwiki_menu = 'Plugin.Vimwiki' to set the menu to the right place.\r\n  * NEW: g:vimwiki_fold_empty_lines -- don't or do fold in empty lines between headers. See :h g:vimwiki_fold_empty_lines\r\n  * FIX: Encoding error when running vimwiki in Windows XP Japanese.  Thanks KarasAya.\r\n","package":"vimwiki_0_9_3_vba.zip","4":"vimwiki_0_9_3_vba.zip","src_id":"10808","5":"10808","creation_date":"1244804308","6":"1244804308"},{"0":"2226","vim_version":"7.0","1":"7.0","script_version":"0.9.2c","2":"0.9.2c","version_comment":"  * FIX: Regression bug. Export to HTML of `[[link|desc]]` is wrong.","3":"  * FIX: Regression bug. Export to HTML of `[[link|desc]]` is wrong.","package":"vimwiki_0_9_2c_vba.zip","4":"vimwiki_0_9_2c_vba.zip","src_id":"10563","5":"10563","creation_date":"1241856986","6":"1241856986"},{"0":"2226","vim_version":"7.0","1":"7.0","script_version":"0.9.2b","2":"0.9.2b","version_comment":"I was playing with python and vimball archives -- as a result CRLFs in a recent vba file. Anyway I hope those evil CRLFs in the past.\r\n\r\n  * FIX: Installation on Linux doesn't work. (Dos line endings in Vimball archive file).\r\n  * FIX: Clear out FlexWiki ftplugin's setup. Now you don't have to hack filetype.vim to get rid of unexpected ':setlocal bomb' from FlexWiki's ftplugin.\r\n  * FIX: When write done: it will show another done: in html file.\r\n","3":"I was playing with python and vimball archives -- as a result CRLFs in a recent vba file. Anyway I hope those evil CRLFs in the past.\r\n\r\n  * FIX: Installation on Linux doesn't work. (Dos line endings in Vimball archive file).\r\n  * FIX: Clear out FlexWiki ftplugin's setup. Now you don't have to hack filetype.vim to get rid of unexpected ':setlocal bomb' from FlexWiki's ftplugin.\r\n  * FIX: When write done: it will show another done: in html file.\r\n","package":"vimwiki_0_9_2b_vba.zip","4":"vimwiki_0_9_2b_vba.zip","src_id":"10532","5":"10532","creation_date":"1241537650","6":"1241537650"},{"0":"2226","vim_version":"7.0","1":"7.0","script_version":"0.9.2a","2":"0.9.2a","version_comment":"FIX: Remove dos line endings from some files.","3":"FIX: Remove dos line endings from some files.","package":"vimwiki_0_9_2a_vba.zip","4":"vimwiki_0_9_2a_vba.zip","src_id":"10518","5":"10518","creation_date":"1241411222","6":"1241411222"},{"0":"2226","vim_version":"7.0","1":"7.0","script_version":"0.9.2","2":"0.9.2","version_comment":"  * NEW: Option 'folding' added to turn folding on\/off.\r\n  * NEW: Header text object. See :h vimwiki-text-objects.\r\n  * NEW: Add\/remove Header levels with '=' and '-'. See :h vimwiki_=.\r\n  * NEW: Vimwiki GUI menu to select available wikies. See :h g:vimwiki_menu.\r\n  * NEW: You can specify the name of your css file now. See :h vimwiki-option-css_name\r\n  * NEW: You can add styles to image links, see :h vimwiki-syntax-links.\r\n  * FIX: History doesn't work after :VimwikiRenameWord.\r\n  * FIX: Some of wikipedia links are not correctly highlighted. Links with parentheses.\r\n  * MISC: Renamed vimwiki_gtd to vimwiki_lst.","3":"  * NEW: Option 'folding' added to turn folding on\/off.\r\n  * NEW: Header text object. See :h vimwiki-text-objects.\r\n  * NEW: Add\/remove Header levels with '=' and '-'. See :h vimwiki_=.\r\n  * NEW: Vimwiki GUI menu to select available wikies. See :h g:vimwiki_menu.\r\n  * NEW: You can specify the name of your css file now. See :h vimwiki-option-css_name\r\n  * NEW: You can add styles to image links, see :h vimwiki-syntax-links.\r\n  * FIX: History doesn't work after :VimwikiRenameWord.\r\n  * FIX: Some of wikipedia links are not correctly highlighted. Links with parentheses.\r\n  * MISC: Renamed vimwiki_gtd to vimwiki_lst.","package":"vimwiki_0_9_2_vba.zip","4":"vimwiki_0_9_2_vba.zip","src_id":"10506","5":"10506","creation_date":"1241244919","6":"1241244919"},{"0":"2226","vim_version":"7.0","1":"7.0","script_version":"0.9.1","2":"0.9.1","version_comment":"  * [new] HTML Table cell text alignment, see :h vimwiki-syntax-tables.\r\n  * [new] Wikipage history simplified. Each vimwiki buffer now holds b:vimwiki_prev_word which is list of [PrevWord, getpos()].\r\n  * [new] If highlight for groups wikiHeader1..wikiHeader6 exist (defined in a colorscheme) -- use it. Otherwise use Title highlight for all Headers.\r\n  * [fix] Warn only once if 'html_header' or 'html_footer' does not exist.\r\n  * [fix] Wrong folding for the text after the last nested list item.\r\n  * [fix] Bold and Italic aren't highlighted in tables without spaces between || and * or _. ||*bold*||_asdf_ || (Thanks Brett Stahlman)","3":"  * [new] HTML Table cell text alignment, see :h vimwiki-syntax-tables.\r\n  * [new] Wikipage history simplified. Each vimwiki buffer now holds b:vimwiki_prev_word which is list of [PrevWord, getpos()].\r\n  * [new] If highlight for groups wikiHeader1..wikiHeader6 exist (defined in a colorscheme) -- use it. Otherwise use Title highlight for all Headers.\r\n  * [fix] Warn only once if 'html_header' or 'html_footer' does not exist.\r\n  * [fix] Wrong folding for the text after the last nested list item.\r\n  * [fix] Bold and Italic aren't highlighted in tables without spaces between || and * or _. ||*bold*||_asdf_ || (Thanks Brett Stahlman)","package":"vimwiki_0_9_1_vba.zip","4":"vimwiki_0_9_1_vba.zip","src_id":"10389","5":"10389","creation_date":"1239523263","6":"1239523263"},{"0":"2226","vim_version":"7.0","1":"7.0","script_version":"0.9","2":"0.9","version_comment":"  * [new] You can add classes to 'pre' tag -- :h vimwiki-syntax-preformatted. This might be useful for coloring some programming code with external js tools like google syntax highlighter.\r\n  * [new] !WikiPage is not highlighted. It is just a plain word WikiPage in HTML, without exclamation mark\r\n  * [new] Definition lists, see :h vimwiki-syntax-lists.\r\n  * [new] New implementation of :h VimwikiRenameWord. CAUTION: It was tested on 2 computers only, backup your wiki before use it. Email me if it doesn't work for you.\r\n  * [new] HTML: convert [ ] to html checkboxes.\r\n  * [new] Default CSS: gray out checked items. \r\n  * [fix] Less than 3 characters are not highlighted in Bold and Italic.\r\n  * [fix] Added vimwiki autocmd group to avoid clashes with user defined autocmds.\r\n  * [fix] Pressing ESC while :h :VimwikiUISelect opens current wiki index file.  Should cancel wiki selection.","3":"  * [new] You can add classes to 'pre' tag -- :h vimwiki-syntax-preformatted. This might be useful for coloring some programming code with external js tools like google syntax highlighter.\r\n  * [new] !WikiPage is not highlighted. It is just a plain word WikiPage in HTML, without exclamation mark\r\n  * [new] Definition lists, see :h vimwiki-syntax-lists.\r\n  * [new] New implementation of :h VimwikiRenameWord. CAUTION: It was tested on 2 computers only, backup your wiki before use it. Email me if it doesn't work for you.\r\n  * [new] HTML: convert [ ] to html checkboxes.\r\n  * [new] Default CSS: gray out checked items. \r\n  * [fix] Less than 3 characters are not highlighted in Bold and Italic.\r\n  * [fix] Added vimwiki autocmd group to avoid clashes with user defined autocmds.\r\n  * [fix] Pressing ESC while :h :VimwikiUISelect opens current wiki index file.  Should cancel wiki selection.","package":"vimwiki_0_9_0_vba.zip","4":"vimwiki_0_9_0_vba.zip","src_id":"10324","5":"10324","creation_date":"1238433600","6":"1238433600"},{"0":"2226","vim_version":"7.0","1":"7.0","script_version":"0.8.3","2":"0.8.3","version_comment":"  * [new] <C-Space> on a list item creates checkbox.\r\n  * [fix] With * in the first column, <CR> shouldn't insert more * (default syntax).\r\n  * [fix] With MediaWiki's ** [ ], <CR> should insert it on the next line.\r\n  * [fix] HTML export should use 'fileencoding' instead of 'encoding'.\r\n  * [fix] Code cleanup.","3":"  * [new] <C-Space> on a list item creates checkbox.\r\n  * [fix] With * in the first column, <CR> shouldn't insert more * (default syntax).\r\n  * [fix] With MediaWiki's ** [ ], <CR> should insert it on the next line.\r\n  * [fix] HTML export should use 'fileencoding' instead of 'encoding'.\r\n  * [fix] Code cleanup.","package":"vimwiki_0_8_3.zip","4":"vimwiki_0_8_3.zip","src_id":"10251","5":"10251","creation_date":"1237488909","6":"1237488909"},{"0":"2226","vim_version":"7.0","1":"7.0","script_version":"0.8.2","2":"0.8.2","version_comment":"  * [del] Removed google syntax file.\r\n  * [new] Default vimwiki syntax is a subset of google's one. Header's has been changed from !Header to =Header=. It is easier to maintain only 2 syntaxes. See :h vimwiki-syntax-headers.\r\n  * [new] Multiline paragraphs -- less longlines.\r\n  * [new] Comments. See :h vimwiki-syntax-comments.\r\n  * [del] Removed setlocal textwidth = 0 from ftplugin.\r\n  * [fix] New regexps for bold, italic, bolditalic.\r\n  * [fix] The last item in List sometimes fold-in incorrectly.\r\n  * [fix] Minor tweaks on default css.","3":"  * [del] Removed google syntax file.\r\n  * [new] Default vimwiki syntax is a subset of google's one. Header's has been changed from !Header to =Header=. It is easier to maintain only 2 syntaxes. See :h vimwiki-syntax-headers.\r\n  * [new] Multiline paragraphs -- less longlines.\r\n  * [new] Comments. See :h vimwiki-syntax-comments.\r\n  * [del] Removed setlocal textwidth = 0 from ftplugin.\r\n  * [fix] New regexps for bold, italic, bolditalic.\r\n  * [fix] The last item in List sometimes fold-in incorrectly.\r\n  * [fix] Minor tweaks on default css.","package":"vimwiki_0_8_2.zip","4":"vimwiki_0_8_2.zip","src_id":"10207","5":"10207","creation_date":"1237050993","6":"1237050993"},{"0":"2226","vim_version":"7.0","1":"7.0","script_version":"0.8.1","2":"0.8.1","version_comment":"  * [new] Vimwiki's foldmethod changed from syntax to expr. Foldtext is changed to be nicer with folded list items.\r\n  * [new] Fold\/outline list items.\r\n  * [new] It is possible now to edit wiki files in arbitrary directories which is not in g:vimwiki_list's paths. New WikiWords are created in the path of the current WikiWord.\r\n  * [new] User can remap Vimwiki's built in mappings.\r\n  * [new] Added g:vimwiki_use_mouse. It is off by default.\r\n  * [fix] Removed <C-h> mapping.\r\n","3":"  * [new] Vimwiki's foldmethod changed from syntax to expr. Foldtext is changed to be nicer with folded list items.\r\n  * [new] Fold\/outline list items.\r\n  * [new] It is possible now to edit wiki files in arbitrary directories which is not in g:vimwiki_list's paths. New WikiWords are created in the path of the current WikiWord.\r\n  * [new] User can remap Vimwiki's built in mappings.\r\n  * [new] Added g:vimwiki_use_mouse. It is off by default.\r\n  * [fix] Removed <C-h> mapping.\r\n","package":"vimwiki_0_8_1.zip","4":"vimwiki_0_8_1.zip","src_id":"10179","5":"10179","creation_date":"1236797707","6":"1236797707"},{"0":"2226","vim_version":"7.0","1":"7.0","script_version":"0.8","2":"0.8","version_comment":"NOTE: g:vimwiki_home is obsolete now!!!\r\n  * NEW Multiple wikies support. A lot of options have been changed, see :h vimwiki-options\r\n  * NEW Auto create directories.\r\n  * NEW Checked list item highlighted as comment.\r\n  * FIX Multiple set ft=vimwiki for each buffer disabled. Vimwiki should load its buffers a bit faster now.\r\n","3":"NOTE: g:vimwiki_home is obsolete now!!!\r\n  * NEW Multiple wikies support. A lot of options have been changed, see :h vimwiki-options\r\n  * NEW Auto create directories.\r\n  * NEW Checked list item highlighted as comment.\r\n  * FIX Multiple set ft=vimwiki for each buffer disabled. Vimwiki should load its buffers a bit faster now.\r\n","package":"vimwiki_0_8.zip","4":"vimwiki_0_8.zip","src_id":"10124","5":"10124","creation_date":"1236281228","6":"1236281228"},{"0":"2226","vim_version":"7.0","1":"7.0","script_version":"0.7.1","2":"0.7.1","version_comment":"* NEW: <Plug>VimwikiToggleListItem added to be able to remap <C-Space> to anything user prefers more.\r\n* FIX: Toggleable list items do not work with MediaWiki markup.\r\n* FIX: Changing g:vimwiki_home_html to path with ~ while vimwiki is loaded gives errors for HTML export.\r\n* DEL: Command :VimwikiExploreHome.\r\n","3":"* NEW: <Plug>VimwikiToggleListItem added to be able to remap <C-Space> to anything user prefers more.\r\n* FIX: Toggleable list items do not work with MediaWiki markup.\r\n* FIX: Changing g:vimwiki_home_html to path with ~ while vimwiki is loaded gives errors for HTML export.\r\n* DEL: Command :VimwikiExploreHome.\r\n","package":"vimwiki_0_7_1.zip","4":"vimwiki_0_7_1.zip","src_id":"10061","5":"10061","creation_date":"1235813557","6":"1235813557"},{"0":"2226","vim_version":"7.0","1":"7.0","script_version":"0.7","2":"0.7","version_comment":" * NEW: GTD stuff -- toggleable list items. See h: vimwiki-gtd.\r\n * FIX: Headers do not fold inner headers. (Thanks Brett Stahlman)\r\n * FIX: Remove last blank lines from preformatted text at the end of file (HTML).\r\n * DEL: Removed g:vimwiki_smartCR option.\r\n","3":" * NEW: GTD stuff -- toggleable list items. See h: vimwiki-gtd.\r\n * FIX: Headers do not fold inner headers. (Thanks Brett Stahlman)\r\n * FIX: Remove last blank lines from preformatted text at the end of file (HTML).\r\n * DEL: Removed g:vimwiki_smartCR option.\r\n","package":"vimwiki_0_7_0.zip","4":"vimwiki_0_7_0.zip","src_id":"10010","5":"10010","creation_date":"1235384540","6":"1235384540"},{"0":"2226","vim_version":"7.0","1":"7.0","script_version":"0.6.2","2":"0.6.2","version_comment":"    * NEW: [[link|description]] is available now.\r\n    * FIX: Barebone links (ie: http:\/\/bla-bla-bla.org\/h.pl?id=98) get extra escaping of ? and friends so they become invalid in HTML.\r\n    * FIX: In linux going to [[wiki with whitespaces]] and then pressing BS to go back to prev wikipage produce error. (Thanks Brendon Bensel for the fix)\r\n    * FIX: Remove setlocal encoding and fileformat from vimwiki ftplugin.\r\n    * FIX: Some tweaks on default style.css\r\n","3":"    * NEW: [[link|description]] is available now.\r\n    * FIX: Barebone links (ie: http:\/\/bla-bla-bla.org\/h.pl?id=98) get extra escaping of ? and friends so they become invalid in HTML.\r\n    * FIX: In linux going to [[wiki with whitespaces]] and then pressing BS to go back to prev wikipage produce error. (Thanks Brendon Bensel for the fix)\r\n    * FIX: Remove setlocal encoding and fileformat from vimwiki ftplugin.\r\n    * FIX: Some tweaks on default style.css\r\n","package":"vimwiki_0_6_2.zip","4":"vimwiki_0_6_2.zip","src_id":"9973","5":"9973","creation_date":"1234720721","6":"1234720721"},{"0":"2226","vim_version":"7.0","1":"7.0","script_version":"0.6.1","2":"0.6.1","version_comment":"    * FIX: [blablabla bla] shouldn't be converted to a link.\r\n    * FIX: Remove extra annoing empty strings from PRE tag made from\r\n      whitespaces in HTML export.\r\n    * FIX: Moved functions related to HTML converting to new autoload module\r\n      to increase a bit vimwiki startup time.\r\n","3":"    * FIX: [blablabla bla] shouldn't be converted to a link.\r\n    * FIX: Remove extra annoing empty strings from PRE tag made from\r\n      whitespaces in HTML export.\r\n    * FIX: Moved functions related to HTML converting to new autoload module\r\n      to increase a bit vimwiki startup time.\r\n","package":"vimwiki_0_6_1.zip","4":"vimwiki_0_6_1.zip","src_id":"9933","5":"9933","creation_date":"1234100488","6":"1234100488"},{"0":"2226","vim_version":"7.0","1":"7.0","script_version":"0.6","2":"0.6","version_comment":" * NEW: Header and footer templates. See g:vimwiki_html_header and g:vimwiki_html_footer in help.\r\n * FIX: :Vimwiki2HTML does not recognize ~ as part of a valid path.","3":" * NEW: Header and footer templates. See g:vimwiki_html_header and g:vimwiki_html_footer in help.\r\n * FIX: :Vimwiki2HTML does not recognize ~ as part of a valid path.","package":"vimwiki_0_6.zip","4":"vimwiki_0_6.zip","src_id":"9912","5":"9912","creation_date":"1233775984","6":"1233775984"},{"0":"2226","vim_version":"7.0","1":"7.0","script_version":"0.5.3","2":"0.5.3","version_comment":"* FIX: Fixed :VimwikiRenameWord. Error when g:vimwiki_home had whitespaces in path.\r\n* FIX: :VimwikiSplitWord and :VimwikiVSplitWord didn't work.","3":"* FIX: Fixed :VimwikiRenameWord. Error when g:vimwiki_home had whitespaces in path.\r\n* FIX: :VimwikiSplitWord and :VimwikiVSplitWord didn't work.","package":"vimwiki_0_5_3.zip","4":"vimwiki_0_5_3.zip","src_id":"9848","5":"9848","creation_date":"1232480997","6":"1232480997"},{"0":"2226","vim_version":"7.0","1":"7.0","script_version":"0.5.2","2":"0.5.2","version_comment":"    * NEW: Added :VimwikiGoHome, :VimwikiTabGoHome and :VimwikiExploreHome commands.\r\n    * NEW: Added <Leader>wt mapping to open vimwiki index file in a new tab.\r\n    * NEW: Added g:vimwiki_gohome option that controls how :VimwikiGoHome works when current buffer is changed. (Thanks Timur Zaripov)\r\n    * FIX: Fixed :VimwikiRenameWord. Very bad behaviour when autochdir isn't set up.\r\n    * FIX: Fixed commands :Wiki2HTML and :WikiAll2HTML to be available only for vimwiki buffers.\r\n    * FIX: Renamed :Wiki2HTML and :WikiAll2HTML to :Vimwiki2HTML and :VimwikiAll2HTML commands.\r\n    * FIX: Help file corrections. ","3":"    * NEW: Added :VimwikiGoHome, :VimwikiTabGoHome and :VimwikiExploreHome commands.\r\n    * NEW: Added <Leader>wt mapping to open vimwiki index file in a new tab.\r\n    * NEW: Added g:vimwiki_gohome option that controls how :VimwikiGoHome works when current buffer is changed. (Thanks Timur Zaripov)\r\n    * FIX: Fixed :VimwikiRenameWord. Very bad behaviour when autochdir isn't set up.\r\n    * FIX: Fixed commands :Wiki2HTML and :WikiAll2HTML to be available only for vimwiki buffers.\r\n    * FIX: Renamed :Wiki2HTML and :WikiAll2HTML to :Vimwiki2HTML and :VimwikiAll2HTML commands.\r\n    * FIX: Help file corrections. ","package":"vimwiki_0_5_2.zip","4":"vimwiki_0_5_2.zip","src_id":"9841","5":"9841","creation_date":"1232366781","6":"1232366781"},{"0":"2226","vim_version":"7.0","1":"7.0","script_version":"0.5.1","2":"0.5.1","version_comment":"  * [new] Help is created.\r\n  * [new] Now you can fold headers.\r\n  * [new] <Plug>VimwikiGoHome and <Plug>VimwikiExploreHome were added.\r\n  * [fix] Bug with {{{HelloWikiWord}}} export to HTML is fixed.\r\n  * [del] Sync option removed from: Syntax highlighting for preformatted text  {{{ }}}.\r\n","3":"  * [new] Help is created.\r\n  * [new] Now you can fold headers.\r\n  * [new] <Plug>VimwikiGoHome and <Plug>VimwikiExploreHome were added.\r\n  * [fix] Bug with {{{HelloWikiWord}}} export to HTML is fixed.\r\n  * [del] Sync option removed from: Syntax highlighting for preformatted text  {{{ }}}.\r\n","package":"vimwiki_0_5_1.zip","4":"vimwiki_0_5_1.zip","src_id":"9604","5":"9604","creation_date":"1228312598","6":"1228312598"},{"0":"2226","vim_version":"7.0","1":"7.0","script_version":"0.5","2":"0.5","version_comment":"  * DONE: vimwiki default markup to HTML conversion improved.\r\n  * DONE: Added basic `GoogleWiki` and `MediaWiki` markup languages.\r\n  * DONE: Chinese `[[complex wiki words]]`.","3":"  * DONE: vimwiki default markup to HTML conversion improved.\r\n  * DONE: Added basic `GoogleWiki` and `MediaWiki` markup languages.\r\n  * DONE: Chinese `[[complex wiki words]]`.","package":"vimwiki_0_5.zip","4":"vimwiki_0_5.zip","src_id":"9253","5":"9253","creation_date":"1221445039","6":"1221445039"},{"0":"2226","vim_version":"7.0","1":"7.0","script_version":"0.4","2":"0.4","version_comment":"  * DONE: vimwiki=>HTML converter in plain vim language.\r\n  * DONE: Plugin autoload.","3":"  * DONE: vimwiki=>HTML converter in plain vim language.\r\n  * DONE: Plugin autoload.","package":"vimwiki_0_4.vba","4":"vimwiki_0_4.vba","src_id":"8744","5":"8744","creation_date":"1212375639","6":"1212375639"},{"0":"2226","vim_version":"7.0","1":"7.0","script_version":"0.3.4","2":"0.3.4","version_comment":"  * FIXED: Backup files (.wiki~) caused a bunch of errors while opening wiki files.","3":"  * FIXED: Backup files (.wiki~) caused a bunch of errors while opening wiki files.","package":"vimwiki_0_3_4.vba","4":"vimwiki_0_3_4.vba","src_id":"8725","5":"8725","creation_date":"1211760120","6":"1211760120"},{"0":"2226","vim_version":"7.0","1":"7.0","script_version":"0.3.3","2":"0.3.3","version_comment":"  * FIXED: `[[wiki word with dots at the end...]]` didn't work.\r\n  * DONE: Added error handling for `delete wiki word` function.\r\n  * DONE: Added keybindings `o` and `O` for list items when g:vimwiki_smartCR=1.\r\n  * DONE: Added keybinding `<Leader>wh` to visit wiki home directory.\r\n","3":"  * FIXED: `[[wiki word with dots at the end...]]` didn't work.\r\n  * DONE: Added error handling for `delete wiki word` function.\r\n  * DONE: Added keybindings `o` and `O` for list items when g:vimwiki_smartCR=1.\r\n  * DONE: Added keybinding `<Leader>wh` to visit wiki home directory.\r\n","package":"vimwiki_0_3_3.vba","4":"vimwiki_0_3_3.vba","src_id":"8714","5":"8714","creation_date":"1211521509","6":"1211521509"},{"0":"2226","vim_version":"7.0","1":"7.0","script_version":"0.3.2","2":"0.3.2","version_comment":"FIXED: Renaming - error if complex wiki word contains %. \r\nFIXED: Syntax highlighting for preformatted text . Sync option added. \r\nFIXED: smartCR bug fix.","3":"FIXED: Renaming - error if complex wiki word contains %. \r\nFIXED: Syntax highlighting for preformatted text . Sync option added. \r\nFIXED: smartCR bug fix.","package":"vimwiki_0_3_2.vba","4":"vimwiki_0_3_2.vba","src_id":"8696","5":"8696","creation_date":"1210923991","6":"1210923991"},{"0":"2226","vim_version":"7.0","1":"7.0","script_version":"0.3.1","2":"0.3.1","version_comment":"DONE: Use mouse to follow links. Left double-click to follow WikiPage, Rightclick then Leftclick to go back.\r\nFIXED: Renaming - [[hello world?]] to [[hello? world]] links are not updated. \r\nFIXED: Buffers menu after renaming is the same as before renaming.","3":"DONE: Use mouse to follow links. Left double-click to follow WikiPage, Rightclick then Leftclick to go back.\r\nFIXED: Renaming - [[hello world?]] to [[hello? world]] links are not updated. \r\nFIXED: Buffers menu after renaming is the same as before renaming.","package":"vimwiki_0_3_1.vba","4":"vimwiki_0_3_1.vba","src_id":"8695","5":"8695","creation_date":"1210908756","6":"1210908756"},{"0":"2226","vim_version":"7.0","1":"7.0","script_version":"0.3","2":"0.3","version_comment":"DONE: - Highlight non-existent WikiWords. \r\nDONE: - delete current WikiWord (<Leader>wd) \r\nDONE: - g:vimwiki_smartCR=2 => use vim comments (see :h comments :h formatoptions) feature to deal with list items. (thx - Dmitry Alexandrov) \r\nDONE: Add highlighting to TODO:, DONE:, FIXED:. \r\nDONE: Rename current WikiWord - be careful on Windows you cannot rename wikiword to WikiWord. After renaming update all links to that renamed WikiWord \r\nFIXED: Bug - do not duplicate WikiWords in wiki history. \r\nFIXED: after renaming [[wiki word]] twice buffers are not deleted \r\nFIXED: when renaming from [[wiki word]] to WikiWord result is [[WikiWord]] \r\nFIXED: more than one complex words on one line is bugging each other when try go to one of them. [[bla bla bla]] [[dodo dodo dodo]] becomes bla bla bla ]] [[dodo dodo dodo","3":"DONE: - Highlight non-existent WikiWords. \r\nDONE: - delete current WikiWord (<Leader>wd) \r\nDONE: - g:vimwiki_smartCR=2 => use vim comments (see :h comments :h formatoptions) feature to deal with list items. (thx - Dmitry Alexandrov) \r\nDONE: Add highlighting to TODO:, DONE:, FIXED:. \r\nDONE: Rename current WikiWord - be careful on Windows you cannot rename wikiword to WikiWord. After renaming update all links to that renamed WikiWord \r\nFIXED: Bug - do not duplicate WikiWords in wiki history. \r\nFIXED: after renaming [[wiki word]] twice buffers are not deleted \r\nFIXED: when renaming from [[wiki word]] to WikiWord result is [[WikiWord]] \r\nFIXED: more than one complex words on one line is bugging each other when try go to one of them. [[bla bla bla]] [[dodo dodo dodo]] becomes bla bla bla ]] [[dodo dodo dodo","package":"vimwiki_0_3.vba","4":"vimwiki_0_3.vba","src_id":"8690","5":"8690","creation_date":"1210847724","6":"1210847724"},{"0":"2226","vim_version":"7.0","1":"7.0","script_version":"0.2.2","2":"0.2.2","version_comment":"Added keybindings to split\/vertsplit when following WikiWords.\r\n<S-CR> - split WikiWord  \r\n<C-CR> - vertical split WikiWord\r\n","3":"Added keybindings to split\/vertsplit when following WikiWords.\r\n<S-CR> - split WikiWord  \r\n<C-CR> - vertical split WikiWord\r\n","package":"vimwiki_0_2_2.vba","4":"vimwiki_0_2_2.vba","src_id":"8657","5":"8657","creation_date":"1210149102","6":"1210149102"},{"0":"2226","vim_version":"7.0","1":"7.0","script_version":"0.2.1","2":"0.2.1","version_comment":"install on linux now works.","3":"install on linux now works.","package":"vimwiki_0_2_1.vba","4":"vimwiki_0_2_1.vba","src_id":"8649","5":"8649","creation_date":"1210038239","6":"1210038239"},{"0":"2226","vim_version":"7.0","1":"7.0","script_version":"0.2","2":"0.2","version_comment":"  * (+) Add part of Google's Wiki syntax.\r\n  * (+) Add auto insert # with ENTER.\r\n  * (+) On\/Off auto insert bullet with ENTER.\r\n  * (+) Strip `[[complex wiki name]]` from symbols that cannot be used in file names.\r\n  * (+) Links to non-wiki files. Non wiki files are files with extensions ie `[[hello world.txt]]` or `[[my homesite.html]]`\r\n","3":"  * (+) Add part of Google's Wiki syntax.\r\n  * (+) Add auto insert # with ENTER.\r\n  * (+) On\/Off auto insert bullet with ENTER.\r\n  * (+) Strip `[[complex wiki name]]` from symbols that cannot be used in file names.\r\n  * (+) Links to non-wiki files. Non wiki files are files with extensions ie `[[hello world.txt]]` or `[[my homesite.html]]`\r\n","package":"vimwiki_0_2.vba","4":"vimwiki_0_2.vba","src_id":"8646","5":"8646","creation_date":"1209976877","6":"1209976877"},{"0":"2226","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"vimwiki_0_1.vba","4":"vimwiki_0_1.vba","src_id":"8644","5":"8644","creation_date":"1209886390","6":"1209886390"}]},"2225":{"script_id":"2225","0":"2225","script_name":"sort python imports","1":"sort python imports","script_type":"utility","2":"utility","summary":"this script allows you to sort python imports alphabetically","3":"this script allows you to sort python imports alphabetically","description":"Keep your imports tidy!\r\nThis script allows you to sort python imports easlily.\r\n\r\nUse :PyFixImports, command to fix imports in the beginning of currently edited file.                                                 \r\nYou can also use visual mode to select range of lines and then use <C-i> to sort imports in those lines.\r\n\r\nNeeds vim compiled with python support!","4":"Keep your imports tidy!\r\nThis script allows you to sort python imports easlily.\r\n\r\nUse :PyFixImports, command to fix imports in the beginning of currently edited file.                                                 \r\nYou can also use visual mode to select range of lines and then use <C-i> to sort imports in those lines.\r\n\r\nNeeds vim compiled with python support!","install_details":"Just put it in your plugin directory.","5":"Just put it in your plugin directory.","first_name":"Krzysiek","6":"Krzysiek","last_name":"Goj","7":"Goj","releases":[{"0":"2225","vim_version":"7.0","1":"7.0","script_version":"1.2","2":"1.2","version_comment":"bugfix: from foo import (bar, baz)\r\nNow requires only python 2.3 (patch from Konrad Delong)","3":"bugfix: from foo import (bar, baz)\r\nNow requires only python 2.3 (patch from Konrad Delong)","package":"sort_python_imports.vim","4":"sort_python_imports.vim","src_id":"8703","5":"8703","creation_date":"1211025923","6":"1211025923"},{"0":"2225","vim_version":"7.0","1":"7.0","script_version":"1.1","2":"1.1","version_comment":"Bugfix: now works for 'from foo.bar import baz' style imports","3":"Bugfix: now works for 'from foo.bar import baz' style imports","package":"sort_python_imports.vim","4":"sort_python_imports.vim","src_id":"8637","5":"8637","creation_date":"1209741814","6":"1209741814"},{"0":"2225","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"sort_python_imports.vim","4":"sort_python_imports.vim","src_id":"8633","5":"8633","creation_date":"1209667288","6":"1209667288"}]},"2224":{"script_id":"2224","0":"2224","script_name":"STL improved","1":"STL improved","script_type":"syntax","2":"syntax","summary":"Improved C++ STL syntax highlighting","3":"Improved C++ STL syntax highlighting","description":"It's based on this syntax file :\r\nhttp:\/\/www.vim.org\/scripts\/script.php?script_id=1640\r\n\r\nI separated types and methods, and also added some missing things.\r\n","4":"It's based on this syntax file :\r\nhttp:\/\/www.vim.org\/scripts\/script.php?script_id=1640\r\n\r\nI separated types and methods, and also added some missing things.\r\n","install_details":"\r\n $ mkdir -p ~\/.vim\/after\/syntax\/cpp\r\n $ cp stl.vim ~\/.vim\/after\/syntax\/cpp\/","5":"\r\n $ mkdir -p ~\/.vim\/after\/syntax\/cpp\r\n $ cp stl.vim ~\/.vim\/after\/syntax\/cpp\/","first_name":"hyke","6":"hyke","last_name":"jekyll","7":"jekyll","releases":[{"0":"2224","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"stl.vim","4":"stl.vim","src_id":"8628","5":"8628","creation_date":"1209629682","6":"1209629682"}]},"2223":{"script_id":"2223","0":"2223","script_name":"tinymode.vim","1":"tinymode.vim","script_type":"utility","2":"utility","summary":"allows definition of tiny modes for Normal mode","3":"allows definition of tiny modes for Normal mode","description":"We cannot add new Vim modes using Vim script.  But we can map keys in a way\r\nthat comes close.  Example:\r\n\r\n    nmap          <C-W>+     <C-W>+<SID>ws\r\n    nmap          <C-W>-     <C-W>-<SID>ws\r\n    nn <script>   <SID>ws+   <C-W>+<SID>ws\r\n    nn <script>   <SID>ws-   <C-W>-<SID>ws\r\n    nmap          <SID>ws    <Nop>\r\n\r\nThese mappings make the builtin CTRL-W_+ and CTRL-W_- (in short ^W+, ^W-)\r\nkeys a little smarter: You can now type ^W++- instead of ^W+^W+^W- to change\r\nthe window size.  It's like ^W+ enters a \"Vim mode\" with the new keys + and - .\r\n\r\ntinymode.vim is not needed to create such mappings, but it adds some\r\nbenefits:\r\n\r\n- tinymode-style notation of the above mappings:\r\n\r\n    call tinymode#EnterMap(\"winsize\", \"<C-W>+\", \"+\")\r\n    call tinymode#EnterMap(\"winsize\", \"<C-W>-\", \"-\")\r\n    call tinymode#Map(\"winsize\", \"+\", \"wincmd +\")\r\n    call tinymode#Map(\"winsize\", \"-\", \"wincmd -\")\r\n\r\nOk, no benefits yet, but read on:\r\n\r\n- you can enable support for a count typed within a mode:\r\n\r\n    call tinymode#ModeArg(\"winsize\", \"owncount\", 1)\r\n\r\n  you need a literal [N] in the commands for the count to be recognized:\r\n\r\n    call tinymode#Map(\"winsize\", \"+\", \"[N]wincmd +\")\r\n    call tinymode#Map(\"winsize\", \"-\", \"[N]wincmd -\")\r\n\r\n- mode message\r\n\r\n    call tinymode#ModeMsg(\"winsize\", \"Change window size +\/-\")\r\n\r\n  The mode message makes it easy to spot that a mode is active.  It is even\r\n  more useful when it shows the available keys.\r\n\r\n- different 'timeoutlen'\r\n\r\n    call tinymode#ModeArg(\"winsize\", \"timeoutlen\", 5000)\r\n\r\n  In most cases, the default 'timeoutlen' of 1000 ms is too short.  That's\r\n  why tinymode sets the default to 3000 ms throughout a mode.  If this is\r\n  not enough, another value can be given.\r\n\r\n- interruption recovery\r\n\r\n    LeaveMode\r\n\r\n  The \"tinymode technique\" has a backdraw: If a command \"beeps\" or you press\r\n  CTRL-C, the chain of mappings is interrupted, which means the necessary\r\n  clean up before leaving a mode is skipped.  \"Clean up\" means to set some\r\n  options back to previous values ('timeoutlen', 'cpo', 'showcmd').\r\n  Unfortunately, a beep cannot be catched like other errors.\r\n\r\n  If you detect this situation, you can start and leave a mode in a clean\r\n  way or execute :LeaveMode .\r\n\r\n- timeout warning\r\n\r\n  Sooner or later a tiny mode times out automatically.  As a visual hint\r\n  that a mode will time out soon the color of the mode message will be\r\n  changed from ModeMsg to Normal.\r\n\r\n(btw: this exact description is not part of the zip package)\r\n\r\n2008 Nov 14\r\n\r\nlooks as if a similar script has been added:\r\nvimscript #2467\r\n","4":"We cannot add new Vim modes using Vim script.  But we can map keys in a way\r\nthat comes close.  Example:\r\n\r\n    nmap          <C-W>+     <C-W>+<SID>ws\r\n    nmap          <C-W>-     <C-W>-<SID>ws\r\n    nn <script>   <SID>ws+   <C-W>+<SID>ws\r\n    nn <script>   <SID>ws-   <C-W>-<SID>ws\r\n    nmap          <SID>ws    <Nop>\r\n\r\nThese mappings make the builtin CTRL-W_+ and CTRL-W_- (in short ^W+, ^W-)\r\nkeys a little smarter: You can now type ^W++- instead of ^W+^W+^W- to change\r\nthe window size.  It's like ^W+ enters a \"Vim mode\" with the new keys + and - .\r\n\r\ntinymode.vim is not needed to create such mappings, but it adds some\r\nbenefits:\r\n\r\n- tinymode-style notation of the above mappings:\r\n\r\n    call tinymode#EnterMap(\"winsize\", \"<C-W>+\", \"+\")\r\n    call tinymode#EnterMap(\"winsize\", \"<C-W>-\", \"-\")\r\n    call tinymode#Map(\"winsize\", \"+\", \"wincmd +\")\r\n    call tinymode#Map(\"winsize\", \"-\", \"wincmd -\")\r\n\r\nOk, no benefits yet, but read on:\r\n\r\n- you can enable support for a count typed within a mode:\r\n\r\n    call tinymode#ModeArg(\"winsize\", \"owncount\", 1)\r\n\r\n  you need a literal [N] in the commands for the count to be recognized:\r\n\r\n    call tinymode#Map(\"winsize\", \"+\", \"[N]wincmd +\")\r\n    call tinymode#Map(\"winsize\", \"-\", \"[N]wincmd -\")\r\n\r\n- mode message\r\n\r\n    call tinymode#ModeMsg(\"winsize\", \"Change window size +\/-\")\r\n\r\n  The mode message makes it easy to spot that a mode is active.  It is even\r\n  more useful when it shows the available keys.\r\n\r\n- different 'timeoutlen'\r\n\r\n    call tinymode#ModeArg(\"winsize\", \"timeoutlen\", 5000)\r\n\r\n  In most cases, the default 'timeoutlen' of 1000 ms is too short.  That's\r\n  why tinymode sets the default to 3000 ms throughout a mode.  If this is\r\n  not enough, another value can be given.\r\n\r\n- interruption recovery\r\n\r\n    LeaveMode\r\n\r\n  The \"tinymode technique\" has a backdraw: If a command \"beeps\" or you press\r\n  CTRL-C, the chain of mappings is interrupted, which means the necessary\r\n  clean up before leaving a mode is skipped.  \"Clean up\" means to set some\r\n  options back to previous values ('timeoutlen', 'cpo', 'showcmd').\r\n  Unfortunately, a beep cannot be catched like other errors.\r\n\r\n  If you detect this situation, you can start and leave a mode in a clean\r\n  way or execute :LeaveMode .\r\n\r\n- timeout warning\r\n\r\n  Sooner or later a tiny mode times out automatically.  As a visual hint\r\n  that a mode will time out soon the color of the mode message will be\r\n  changed from ModeMsg to Normal.\r\n\r\n(btw: this exact description is not part of the zip package)\r\n\r\n2008 Nov 14\r\n\r\nlooks as if a similar script has been added:\r\nvimscript #2467\r\n","install_details":"extract the archive to your vim folder (e.g. ~\/.vim or ~\\vimfiles), files in the archive:\r\n    autoload\\tinymode.vim\r\n    autoload\\tinym_ex.vim\r\n    doc\\tinymode.txt\r\n\r\ntinym_ex.vim is not required, it contains examples.","5":"extract the archive to your vim folder (e.g. ~\/.vim or ~\\vimfiles), files in the archive:\r\n    autoload\\tinymode.vim\r\n    autoload\\tinym_ex.vim\r\n    doc\\tinymode.txt\r\n\r\ntinym_ex.vim is not required, it contains examples.","first_name":"Andy","6":"Andy","last_name":"Wokula","7":"Wokula","releases":[{"0":"2223","vim_version":"7.0","1":"7.0","script_version":"0.5","2":"0.5","version_comment":"still work in progress, but an upload is due:\r\nresets more important options (lz, cpo), custom 'timeoutlen', 2nd timeout step, more mode options, modes no longer quit on (catchable) errors, 0 can be command or count, some more ...","3":"still work in progress, but an upload is due:\r\nresets more important options (lz, cpo), custom 'timeoutlen', 2nd timeout step, more mode options, modes no longer quit on (catchable) errors, 0 can be command or count, some more ...","package":"tinymode_0.5.zip","4":"tinymode_0.5.zip","src_id":"9130","5":"9130","creation_date":"1218799348","6":"1218799348"},{"0":"2223","vim_version":"7.0","1":"7.0","script_version":"0.3","2":"0.3","version_comment":"exec commands when entering\/leaving a mode, via ModeArg()\r\nnow works with i_Ctrl-O\r\nkeep error messages on screen\r\nnow ModeMsg(..., \"\") removes the message entry\r\nfixed init bug with Map() followed by EnterMap() for same key","3":"exec commands when entering\/leaving a mode, via ModeArg()\r\nnow works with i_Ctrl-O\r\nkeep error messages on screen\r\nnow ModeMsg(..., \"\") removes the message entry\r\nfixed init bug with Map() followed by EnterMap() for same key","package":"tinymode.vim","4":"tinymode.vim","src_id":"8688","5":"8688","creation_date":"1210769434","6":"1210769434"},{"0":"2223","vim_version":"7.0","1":"7.0","script_version":"0.2","2":"0.2","version_comment":"added support for the count (both initial v:count and digits typed within the mode)","3":"added support for the count (both initial v:count and digits typed within the mode)","package":"tinymode.zip","4":"tinymode.zip","src_id":"8635","5":"8635","creation_date":"1209703371","6":"1209703371"},{"0":"2223","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"tinymode.zip","4":"tinymode.zip","src_id":"8626","5":"8626","creation_date":"1209616003","6":"1209616003"}]},"2222":{"script_id":"2222","0":"2222","script_name":"CmdlineComplete","1":"CmdlineComplete","script_type":"utility","2":"utility","summary":"complete command-line (: \/ etc.) from the current file","3":"complete command-line (: \/ etc.) from the current file","description":"When editing the command-line (: \/ etc.), press Ctrl-P or Ctrl-N to complete the word before the cursor, using keywords in the current file. E.g: you want to search for \"elephant\" in the buffer, just type \/ele and press Ctrl-P. So long as \"elephant\" is in the buffer, you will get \"ele\" completed into \"elephant\".\r\n\r\nThis script is functional similar with (but far more better than) SearchComplete vimscript #474 (version 1.1).","4":"When editing the command-line (: \/ etc.), press Ctrl-P or Ctrl-N to complete the word before the cursor, using keywords in the current file. E.g: you want to search for \"elephant\" in the buffer, just type \/ele and press Ctrl-P. So long as \"elephant\" is in the buffer, you will get \"ele\" completed into \"elephant\".\r\n\r\nThis script is functional similar with (but far more better than) SearchComplete vimscript #474 (version 1.1).","install_details":"Just drop the script file \"cmdline-complete.vim\" into the plugin directory. Restart VIM.\r\n\r\nIf you want to use other keys instead of default <c-p> <c-n>, you may say in your .vimrc\r\ncmap <c-y> <Plug>CmdlineCompleteBackward\r\ncmap <c-e> <Plug>CmdlineCompleteForward\r\nthis will use Ctrl-Y for search backward and Ctrl-E for search forward.\r\n\r\nNote: I don't think it's good to use Tab and Shift-Tab for completion, since it will disable vim's original cmdline-completion.\r\n\r\nWithout python, speed will be a bit slow with large file (e.g. > 100K). Compile your vim with python is recommended.","5":"Just drop the script file \"cmdline-complete.vim\" into the plugin directory. Restart VIM.\r\n\r\nIf you want to use other keys instead of default <c-p> <c-n>, you may say in your .vimrc\r\ncmap <c-y> <Plug>CmdlineCompleteBackward\r\ncmap <c-e> <Plug>CmdlineCompleteForward\r\nthis will use Ctrl-Y for search backward and Ctrl-E for search forward.\r\n\r\nNote: I don't think it's good to use Tab and Shift-Tab for completion, since it will disable vim's original cmdline-completion.\r\n\r\nWithout python, speed will be a bit slow with large file (e.g. > 100K). Compile your vim with python is recommended.","first_name":"Yuheng","6":"Yuheng","last_name":"Xie","7":"Xie","releases":[{"0":"2222","vim_version":"7.0","1":"7.0","script_version":"1.1.3","2":"1.1.3","version_comment":"added support for 'iskeyword'","3":"added support for 'iskeyword'","package":"cmdline-complete.vim","4":"cmdline-complete.vim","src_id":"8969","5":"8969","creation_date":"1216359928","6":"1216359928"},{"0":"2222","vim_version":"7.0","1":"7.0","script_version":"1.1.2","2":"1.1.2","version_comment":"added support for 'ignorecase' and 'smartcase'","3":"added support for 'ignorecase' and 'smartcase'","package":"cmdline-complete.vim","4":"cmdline-complete.vim","src_id":"8940","5":"8940","creation_date":"1215911942","6":"1215911942"},{"0":"2222","vim_version":"7.0","1":"7.0","script_version":"1.1.1","2":"1.1.1","version_comment":"trival fix for 1.1","3":"trival fix for 1.1","package":"cmdline-complete.vim","4":"cmdline-complete.vim","src_id":"8912","5":"8912","creation_date":"1215571475","6":"1215571475"},{"0":"2222","vim_version":"7.0","1":"7.0","script_version":"1.0.4","2":"1.0.4","version_comment":"fix for environment where python was found without module re","3":"fix for environment where python was found without module re","package":"cmdline-complete.vim","4":"cmdline-complete.vim","src_id":"8662","5":"8662","creation_date":"1210238357","6":"1210238357"}]},"2221":{"script_id":"2221","0":"2221","script_name":"Allegro 4.2 syntax file","1":"Allegro 4.2 syntax file","script_type":"syntax","2":"syntax","summary":"Provides syntax highlighting for Allegro 4.2 API","3":"Provides syntax highlighting for Allegro 4.2 API","description":"Provides syntax highlighting for Allegro 4.2 API","4":"Provides syntax highlighting for Allegro 4.2 API","install_details":"\r\n $ mkdir -p ~\/.vim\/after\/syntax\/c ~\/.vim\/after\/syntax\/cpp\r\n $ cp allegro.vim ~\/.vim\/after\/syntax\/cpp\/\r\n $ cp allegro.vim ~\/.vim\/after\/syntax\/c\/","5":"\r\n $ mkdir -p ~\/.vim\/after\/syntax\/c ~\/.vim\/after\/syntax\/cpp\r\n $ cp allegro.vim ~\/.vim\/after\/syntax\/cpp\/\r\n $ cp allegro.vim ~\/.vim\/after\/syntax\/c\/","first_name":"hyke","6":"hyke","last_name":"jekyll","7":"jekyll","releases":[{"0":"2221","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"allegro.vim","4":"allegro.vim","src_id":"8623","5":"8623","creation_date":"1209579223","6":"1209579223"}]},"2220":{"script_id":"2220","0":"2220","script_name":"bensday","1":"bensday","script_type":"color scheme","2":"color scheme","summary":"Only slightly modified version of the evening color scheme.","3":"Only slightly modified version of the evening color scheme.","description":"This color scheme is based upon the evening color scheme with only slight modifications.\r\nSo most (99%) of the credit for this color scheme belongs to the maintainer\r\nof the original work, Bram Moolenaar.\r\n\r\nThe main differences are: It does not use a black background for some keywords but uses a darker global background even for the cursor line. In gvim it also uses more bold fonts, and the statusline of inactive windows has a different background color than in the original scheme.\r\n\r\nThe name was inspired by a colleague of mine, who preferes dark themes for his desktop and likes to work in dark rooms... no, he does not crumble to dust in sunlight, but he is close to it... ;-)\r\n\r\nI have only tested it with Vim 7.1.","4":"This color scheme is based upon the evening color scheme with only slight modifications.\r\nSo most (99%) of the credit for this color scheme belongs to the maintainer\r\nof the original work, Bram Moolenaar.\r\n\r\nThe main differences are: It does not use a black background for some keywords but uses a darker global background even for the cursor line. In gvim it also uses more bold fonts, and the statusline of inactive windows has a different background color than in the original scheme.\r\n\r\nThe name was inspired by a colleague of mine, who preferes dark themes for his desktop and likes to work in dark rooms... no, he does not crumble to dust in sunlight, but he is close to it... ;-)\r\n\r\nI have only tested it with Vim 7.1.","install_details":"Copy this file into your \"colors\" directory.\r\nYou can reference it in your .vimrc or .gvimrc with: colorscheme bensday\r\n","5":"Copy this file into your \"colors\" directory.\r\nYou can reference it in your .vimrc or .gvimrc with: colorscheme bensday\r\n","first_name":"Christian","6":"Christian","last_name":"Br\u00c3\u00bcssow","7":"Br\u00c3\u00bcssow","releases":[{"0":"2220","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"bensday.vim","4":"bensday.vim","src_id":"8610","5":"8610","creation_date":"1209290904","6":"1209290904"}]},"2219":{"script_id":"2219","0":"2219","script_name":"Limp","1":"Limp","script_type":"utility","2":"utility","summary":"Lisp IDE","3":"Lisp IDE","description":"Limp's goal is to provide a compelling alternative to Slime for Vim. It will let you send s-expressions to a running Lisp.\r\n\r\nIt will do this for you:\r\n\r\n* booting\/attaching\/detaching a Lisp (SBCL) from Vim or a command-line script, optionally specifying a core;\r\n* send code to the attached Lisp (and limited introspection, see Help Describe);\r\n* automatically close brackets;\r\n* ease s-exp navigation and (some) transposing;\r\n* highlight current form under the cursor;\r\n* lookup documentation from the HyperSpec;\r\n* complete (some) names.\r\n\r\nQuickstart (better version with screenshots in the documentation):\r\n\r\nIn a file with \"filetype=lisp\" set, hit <F12> to invoke Limp and start a Lisp or connect to an existing.\r\nWrite a piece of code, e.g.:\r\n\r\n  (defun hello-world (who)\r\n    (format t \"Hello, ~A!~%\" who))\r\n\r\nPlace the cursor at any location inside the code and type <Leader>et (Evaluate Top) to send your code to the running Lisp.\r\n\r\nHit <F12> again to see the results!  Then, by placing the cursor at hello-world and typing <Leader>hd (Help Describe) followed by <F12>, you'll see information about the symbol!\r\n\r\n(Full list of key bindings at http:\/\/mikael.jansson.be\/hacking\/limp\/docs\/#keyboard-reference )\r\n\r\nTo test it, type\r\n\r\n  :Eval (hello-world '|Limp User|)\r\n\r\nfollowed by <Enter> and <F12>.\r\n\r\nMore info in the documentation! \r\nUses code from ViLisp (vimscript #221), AutoClose (vimscript #1849), HiMtchBrkt (vimscript #1435)","4":"Limp's goal is to provide a compelling alternative to Slime for Vim. It will let you send s-expressions to a running Lisp.\r\n\r\nIt will do this for you:\r\n\r\n* booting\/attaching\/detaching a Lisp (SBCL) from Vim or a command-line script, optionally specifying a core;\r\n* send code to the attached Lisp (and limited introspection, see Help Describe);\r\n* automatically close brackets;\r\n* ease s-exp navigation and (some) transposing;\r\n* highlight current form under the cursor;\r\n* lookup documentation from the HyperSpec;\r\n* complete (some) names.\r\n\r\nQuickstart (better version with screenshots in the documentation):\r\n\r\nIn a file with \"filetype=lisp\" set, hit <F12> to invoke Limp and start a Lisp or connect to an existing.\r\nWrite a piece of code, e.g.:\r\n\r\n  (defun hello-world (who)\r\n    (format t \"Hello, ~A!~%\" who))\r\n\r\nPlace the cursor at any location inside the code and type <Leader>et (Evaluate Top) to send your code to the running Lisp.\r\n\r\nHit <F12> again to see the results!  Then, by placing the cursor at hello-world and typing <Leader>hd (Help Describe) followed by <F12>, you'll see information about the symbol!\r\n\r\n(Full list of key bindings at http:\/\/mikael.jansson.be\/hacking\/limp\/docs\/#keyboard-reference )\r\n\r\nTo test it, type\r\n\r\n  :Eval (hello-world '|Limp User|)\r\n\r\nfollowed by <Enter> and <F12>.\r\n\r\nMore info in the documentation! \r\nUses code from ViLisp (vimscript #221), AutoClose (vimscript #1849), HiMtchBrkt (vimscript #1435)","install_details":"See http:\/\/mikael.jansson.be\/hacking\/limp\/docs or the included documentation for complete installation instructions.\r\n\r\nAuthor's setup: Linux\/Ubuntu-7.04, SBCL-1.0.x, GVim\/Vim-7.1 (make sure to install a Vim with +eval, i.e. `sudo aptitude install vim-full`)\r\n\r\nIssue tracker and roadmap at http:\/\/mikael.jansson.be\/hacking\/limp\r\nRepository at https:\/\/svn.jansson.be\/public\/limp","5":"See http:\/\/mikael.jansson.be\/hacking\/limp\/docs or the included documentation for complete installation instructions.\r\n\r\nAuthor's setup: Linux\/Ubuntu-7.04, SBCL-1.0.x, GVim\/Vim-7.1 (make sure to install a Vim with +eval, i.e. `sudo aptitude install vim-full`)\r\n\r\nIssue tracker and roadmap at http:\/\/mikael.jansson.be\/hacking\/limp\r\nRepository at https:\/\/svn.jansson.be\/public\/limp","first_name":"Mikael","6":"Mikael","last_name":"Jansson","7":"Jansson","releases":[{"0":"2219","vim_version":"7.0","1":"7.0","script_version":"0.3.4","2":"0.3.4","version_comment":"Mostly bugfix release, with some extra candy.\r\nFixed bugs: #15 (mappings set twice when navigating Lisp buffers); #16 (more robust startup procedure), #19 (eval working on unsaved buffers).\r\nNew features: #20 (proper installer), #21 (s-exp navigation and (experimental) transposing).","3":"Mostly bugfix release, with some extra candy.\r\nFixed bugs: #15 (mappings set twice when navigating Lisp buffers); #16 (more robust startup procedure), #19 (eval working on unsaved buffers).\r\nNew features: #20 (proper installer), #21 (s-exp navigation and (experimental) transposing).","package":"limp-0.3.4.tar.gz","4":"limp-0.3.4.tar.gz","src_id":"8771","5":"8771","creation_date":"1212897283","6":"1212897283"},{"0":"2219","vim_version":"7.0","1":"7.0","script_version":"0.3.3","2":"0.3.3","version_comment":"* CompileFile\/CompileAndLoadFile now saves the file before telling Lisp to load it (#4).\r\n* New command, :Eval, same functionality as \\ex.\r\n* Easier keyboard configuration (keys.vim)\r\n* It is now a Lisp filetype plugin, so Limp will start automatically for Lisp files. (set filetype=lisp)\r\n* Configurable location of SBCL in lisp.sh\r\n* Updated documentation about Cmd for Fn-keys in OS X","3":"* CompileFile\/CompileAndLoadFile now saves the file before telling Lisp to load it (#4).\r\n* New command, :Eval, same functionality as \\ex.\r\n* Easier keyboard configuration (keys.vim)\r\n* It is now a Lisp filetype plugin, so Limp will start automatically for Lisp files. (set filetype=lisp)\r\n* Configurable location of SBCL in lisp.sh\r\n* Updated documentation about Cmd for Fn-keys in OS X","package":"limp-0.3.3.tar.gz","4":"limp-0.3.3.tar.gz","src_id":"8720","5":"8720","creation_date":"1211603021","6":"1211603021"},{"0":"2219","vim_version":"7.0","1":"7.0","script_version":"0.3.2","2":"0.3.2","version_comment":"* 2008-04-28 by Mikael Jansson <mail@mikael.jansson.be>\r\n\r\n  + **ADDED**: TODO file in the distro.\r\n  + *FIXED*: Last occurance of \"Lim\" found in the HyperSpec helper. Now\r\n    documentation should work properly.\r\n  + TWEAK: Only change colorscheme and nocompatible when not previously set.\r\n\r\n* 2008-04-27 by Mikael Jansson <mail@mikael.jansson.be>\r\n\r\n  + *FIXED*: Connect-or-boot, without a name given to boot.","3":"* 2008-04-28 by Mikael Jansson <mail@mikael.jansson.be>\r\n\r\n  + **ADDED**: TODO file in the distro.\r\n  + *FIXED*: Last occurance of \"Lim\" found in the HyperSpec helper. Now\r\n    documentation should work properly.\r\n  + TWEAK: Only change colorscheme and nocompatible when not previously set.\r\n\r\n* 2008-04-27 by Mikael Jansson <mail@mikael.jansson.be>\r\n\r\n  + *FIXED*: Connect-or-boot, without a name given to boot.","package":"limp-0.3.2.tar.gz","4":"limp-0.3.2.tar.gz","src_id":"8617","5":"8617","creation_date":"1209428438","6":"1209428438"},{"0":"2219","vim_version":"7.0","1":"7.0","script_version":"0.3.1","2":"0.3.1","version_comment":"Initial upload","3":"Initial upload","package":"limp-0.3.1.tar.gz","4":"limp-0.3.1.tar.gz","src_id":"8609","5":"8609","creation_date":"1209275713","6":"1209275713"}]},"2218":{"script_id":"2218","0":"2218","script_name":"debugger.py","1":"debugger.py","script_type":"utility","2":"utility","summary":"remote PHP debugger : remote debugger interface to DBGp protocol w\/ path mapping","3":"remote PHP debugger : remote debugger interface to DBGp protocol w\/ path mapping","description":"This is a small modification to Seung Woo Shin's XDebug remote debugger.  For further instructions, see here: http:\/\/www.vim.org\/scripts\/script.php?script_id=1152\r\n\r\nThe only thing I added is the ability to set path mapping in your .vimrc (or wherever)\r\n\r\nFor example:\r\nlet pathMap=\"\/mnt\/hgfs:\/home\/ethanm\/vmfiles, \/home\/config:\/home\/ethanm\/config\"\r\nwould adjust my xdebug paths so that I could now work with a local editor on files running in my VM.","4":"This is a small modification to Seung Woo Shin's XDebug remote debugger.  For further instructions, see here: http:\/\/www.vim.org\/scripts\/script.php?script_id=1152\r\n\r\nThe only thing I added is the ability to set path mapping in your .vimrc (or wherever)\r\n\r\nFor example:\r\nlet pathMap=\"\/mnt\/hgfs:\/home\/ethanm\/vmfiles, \/home\/config:\/home\/ethanm\/config\"\r\nwould adjust my xdebug paths so that I could now work with a local editor on files running in my VM.","install_details":"just untar these files and place them in your .vim\/plugin directory.","5":"just untar these files and place them in your .vim\/plugin directory.","first_name":"Ethan","6":"Ethan","last_name":"McCreadie","7":"McCreadie","releases":[{"0":"2218","vim_version":"6.0","1":"6.0","script_version":"0.11","2":"0.11","version_comment":"Initial upload","3":"Initial upload","package":"debugger.tar.gz","4":"debugger.tar.gz","src_id":"8605","5":"8605","creation_date":"1209112643","6":"1209112643"}]},"2217":{"script_id":"2217","0":"2217","script_name":"groovy.vim","1":"groovy.vim","script_type":"ftplugin","2":"ftplugin","summary":"Runs or compiles Groovy scripts.","3":"Runs or compiles Groovy scripts.","description":"Runs or compiles Groovy scripts.  Indents code blocks.  Continues comments on adjacent lines.  Provides insert-mode abbreviations.  F2 for plugin help.","4":"Runs or compiles Groovy scripts.  Indents code blocks.  Continues comments on adjacent lines.  Provides insert-mode abbreviations.  F2 for plugin help.","install_details":"Suggested installation at ~\/.vim\/ftplugin, or on Windows at <Vim install directory>\\vimfiles\\ftplugin.\r\n\r\n'filetype plugin on' must be specified in .vimrc or _vimrc.","5":"Suggested installation at ~\/.vim\/ftplugin, or on Windows at <Vim install directory>\\vimfiles\\ftplugin.\r\n\r\n'filetype plugin on' must be specified in .vimrc or _vimrc.","first_name":"Jim","6":"Jim","last_name":"Ruley","7":"Ruley","releases":[{"0":"2217","vim_version":"6.0","1":"6.0","script_version":"0.1.2","2":"0.1.2","version_comment":"Mappings for F4 and F6 fixed.  Indent improved.","3":"Mappings for F4 and F6 fixed.  Indent improved.","package":"groovy.vim","4":"groovy.vim","src_id":"8600","5":"8600","creation_date":"1209022077","6":"1209022077"}]},"2216":{"script_id":"2216","0":"2216","script_name":"qfn","1":"qfn","script_type":"utility","2":"utility","summary":"quickfixnotes: file annotation with quickfix","3":"quickfixnotes: file annotation with quickfix","description":"QuickFixNotes, or QFN, is a quick hack that allows file annotation\r\nbased on |quickfix| functionality.  In particular, this plugin allows the user\r\nto tie comments to a specific source file, line number, and column number\r\nwithout modifying the file being reviewed.  The goal of the plugin is to\r\nprovide a simple and useful mechanism for tracking notes when reviewing any\r\nsort of text file -- from documents and book drafts to source code and\r\nconfiguration files.  Paired with xxd, you can even annotate binary formats\r\nwith it.  qfn is useful any place where inserting comments into the\r\nfile being reviewed is impractical.\r\n\r\nGiven its simplicity, this plugin only supplies a simple set of features:\r\n\r\n    * Add a comment for the given line and column number to the |quickfix| list\r\n    * Save the current |quickfix| list an expected format\r\n    * Provide all functionality without external scripting dependencies\r\n\r\nIn the future, QFN may support more advanced interfaces to the |quickfix|.\r\n\r\nTo use, just map <Plug>QuickFixNote and <Plug>QuickFixSave to keys.  \r\nWhen called, QuickFixNote will add an entry to the quickfix list with a user\r\nsupplied comment for the current cursor's line number, column, and buffer\r\nname. ","4":"QuickFixNotes, or QFN, is a quick hack that allows file annotation\r\nbased on |quickfix| functionality.  In particular, this plugin allows the user\r\nto tie comments to a specific source file, line number, and column number\r\nwithout modifying the file being reviewed.  The goal of the plugin is to\r\nprovide a simple and useful mechanism for tracking notes when reviewing any\r\nsort of text file -- from documents and book drafts to source code and\r\nconfiguration files.  Paired with xxd, you can even annotate binary formats\r\nwith it.  qfn is useful any place where inserting comments into the\r\nfile being reviewed is impractical.\r\n\r\nGiven its simplicity, this plugin only supplies a simple set of features:\r\n\r\n    * Add a comment for the given line and column number to the |quickfix| list\r\n    * Save the current |quickfix| list an expected format\r\n    * Provide all functionality without external scripting dependencies\r\n\r\nIn the future, QFN may support more advanced interfaces to the |quickfix|.\r\n\r\nTo use, just map <Plug>QuickFixNote and <Plug>QuickFixSave to keys.  \r\nWhen called, QuickFixNote will add an entry to the quickfix list with a user\r\nsupplied comment for the current cursor's line number, column, and buffer\r\nname. ","install_details":"1. Download the vimball.\r\n2. Run:   vim qfn.vba\r\n3. Execute the following ex command:\r\n       :so %\r\n4. You should now be able to bind <Plug>QuickFixNote and <Plug>QuickFixSave to\r\n   your preferred key combinations.  You can use the \":help qfn\" command  at any time\r\n   to get more information.\r\n","5":"1. Download the vimball.\r\n2. Run:   vim qfn.vba\r\n3. Execute the following ex command:\r\n       :so %\r\n4. You should now be able to bind <Plug>QuickFixNote and <Plug>QuickFixSave to\r\n   your preferred key combinations.  You can use the \":help qfn\" command  at any time\r\n   to get more information.\r\n","first_name":"Will","6":"Will","last_name":"Drewry","7":"Drewry","releases":[{"0":"2216","vim_version":"7.0","1":"7.0","script_version":"20080420","2":"20080420","version_comment":"Removed included :copen mappingl switched to vimball packaging.","3":"Removed included :copen mappingl switched to vimball packaging.","package":"qfn.vba","4":"qfn.vba","src_id":"8586","5":"8586","creation_date":"1208722269","6":"1208722269"},{"0":"2216","vim_version":"7.0","1":"7.0","script_version":"20080417","2":"20080417","version_comment":"Quick release","3":"Quick release","package":"qfn-20080417.zip","4":"qfn-20080417.zip","src_id":"8573","5":"8573","creation_date":"1208470928","6":"1208470928"}]},"2215":{"script_id":"2215","0":"2215","script_name":"darkspectrum","1":"darkspectrum","script_type":"color scheme","2":"color scheme","summary":"a gvim color scheme based on the oblivion color scheme for gedit","3":"a gvim color scheme based on the oblivion color scheme for gedit","description":"Screenshot:\r\nhttp:\/\/i.imgur.com\/7oVDp.png\r\n\r\nFeaturing:\r\n- STL Highlighting (vimscript#1640 and vimscript#2224)\r\n- Autocomplete Menu\r\n- DiffSplit\r\n- Spelling\r\n\r\nThis color scheme is based on the oblivion color scheme for gedit, but with some language specific additions and a few more tweaks to provide a wider spectrum of colors.\r\n\r\nThanks to junkblocker for pointing out I forgot to make DiffText something useful.","4":"Screenshot:\r\nhttp:\/\/i.imgur.com\/7oVDp.png\r\n\r\nFeaturing:\r\n- STL Highlighting (vimscript#1640 and vimscript#2224)\r\n- Autocomplete Menu\r\n- DiffSplit\r\n- Spelling\r\n\r\nThis color scheme is based on the oblivion color scheme for gedit, but with some language specific additions and a few more tweaks to provide a wider spectrum of colors.\r\n\r\nThanks to junkblocker for pointing out I forgot to make DiffText something useful.","install_details":"Just copy the file to your ~\/.vim\/colors directory\r\n\r\nAlternatively, if you use Vundle, you can make use of the vim-scripts GitHub mirror and do this:\r\nBundle 'darkspectrum'","5":"Just copy the file to your ~\/.vim\/colors directory\r\n\r\nAlternatively, if you use Vundle, you can make use of the vim-scripts GitHub mirror and do this:\r\nBundle 'darkspectrum'","first_name":"Brian","6":"Brian","last_name":"Mock","7":"Mock","releases":[{"0":"2215","vim_version":"7.0","1":"7.0","script_version":"1.8","2":"1.8","version_comment":"Removed hue from greys and blacks in theme","3":"Removed hue from greys and blacks in theme","package":"darkspectrum.vim","4":"darkspectrum.vim","src_id":"9771","5":"9771","creation_date":"1231386412","6":"1231386412"},{"0":"2215","vim_version":"7.0","1":"7.0","script_version":"1.7","2":"1.7","version_comment":"- Pmenu scrollbar now more visible\r\n- Visual selection highlight now more visible (blue background)","3":"- Pmenu scrollbar now more visible\r\n- Visual selection highlight now more visible (blue background)","package":"darkspectrum.vim","4":"darkspectrum.vim","src_id":"9252","5":"9252","creation_date":"1221433767","6":"1221433767"},{"0":"2215","vim_version":"7.0","1":"7.0","script_version":"1.6","2":"1.6","version_comment":"Added colors for spellchecking (the originals did not stand out well on the dark background)","3":"Added colors for spellchecking (the originals did not stand out well on the dark background)","package":"darkspectrum.vim","4":"darkspectrum.vim","src_id":"9131","5":"9131","creation_date":"1218829230","6":"1218829230"},{"0":"2215","vim_version":"7.0","1":"7.0","script_version":"1.5","2":"1.5","version_comment":"Added highlight for STL keywords (refer to STL screenshot above for vim script numbers for the STL syntax files)","3":"Added highlight for STL keywords (refer to STL screenshot above for vim script numbers for the STL syntax files)","package":"darkspectrum.vim","4":"darkspectrum.vim","src_id":"9080","5":"9080","creation_date":"1217968938","6":"1217968938"},{"0":"2215","vim_version":"7.0","1":"7.0","script_version":"1.4","2":"1.4","version_comment":"Made WildMenu colors easier on the eyes.\r\nMade DiffDelete completely black instead of having mild dashed lines.\r\nFixed DiffText so that the individual word changes in a changed line show up.","3":"Made WildMenu colors easier on the eyes.\r\nMade DiffDelete completely black instead of having mild dashed lines.\r\nFixed DiffText so that the individual word changes in a changed line show up.","package":"darkspectrum.vim","4":"darkspectrum.vim","src_id":"9079","5":"9079","creation_date":"1217962787","6":"1217962787"},{"0":"2215","vim_version":"7.0","1":"7.0","script_version":"1.3","2":"1.3","version_comment":"Fixed Pmenu coloring so autocomplete (^N) is pretty","3":"Fixed Pmenu coloring so autocomplete (^N) is pretty","package":"darkspectrum.vim","4":"darkspectrum.vim","src_id":"9065","5":"9065","creation_date":"1217614779","6":"1217614779"},{"0":"2215","vim_version":"7.0","1":"7.0","script_version":"1.2","2":"1.2","version_comment":"Diff coloring is now easier to spot (orange for additions, blue for changes)\r\nVertical splits blend better with the window now\r\nFold colors are now similar to line numbering, but still stand out","3":"Diff coloring is now easier to spot (orange for additions, blue for changes)\r\nVertical splits blend better with the window now\r\nFold colors are now similar to line numbering, but still stand out","package":"darkspectrum.vim","4":"darkspectrum.vim","src_id":"8843","5":"8843","creation_date":"1214226284","6":"1214226284"},{"0":"2215","vim_version":"7.0","1":"7.0","script_version":"1.1","2":"1.1","version_comment":"changed diff highlighting (retains syntax highlighting and readability)","3":"changed diff highlighting (retains syntax highlighting and readability)","package":"darkspectrum.vim","4":"darkspectrum.vim","src_id":"8767","5":"8767","creation_date":"1212769725","6":"1212769725"},{"0":"2215","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"darkspectrum.vim","4":"darkspectrum.vim","src_id":"8557","5":"8557","creation_date":"1208122918","6":"1208122918"}]},"2214":{"script_id":"2214","0":"2214","script_name":"Switch","1":"Switch","script_type":"utility","2":"utility","summary":"Quick toggling of boolean options","3":"Quick toggling of boolean options","description":"This plugin  enables you  to toggle  any Vim boolean  options between  'on' and 'off' using just one key mapping for each of tree possible vim modes.\r\n\r\nBasic usage:\r\n\r\n<C-Q> {optkey} Toggle an option.\r\n<C-Q> <Tab> Print the options list.\r\n<C-Q> <F1> Print help on usage, similar to this paragraph.\r\n<C-Q> <C-Q> {optkey} Print the current value of an option.\r\n<C-Q> <CR> {optkey} Invoke :help on an option.\r\n\r\n\r\n* This plugin is related to the Univrc project (http:\/\/univrc.org)","4":"This plugin  enables you  to toggle  any Vim boolean  options between  'on' and 'off' using just one key mapping for each of tree possible vim modes.\r\n\r\nBasic usage:\r\n\r\n<C-Q> {optkey} Toggle an option.\r\n<C-Q> <Tab> Print the options list.\r\n<C-Q> <F1> Print help on usage, similar to this paragraph.\r\n<C-Q> <C-Q> {optkey} Print the current value of an option.\r\n<C-Q> <CR> {optkey} Invoke :help on an option.\r\n\r\n\r\n* This plugin is related to the Univrc project (http:\/\/univrc.org)","install_details":"","5":"","first_name":"Tom\u00c3\u00a1s","6":"Tom\u00c3\u00a1s","last_name":"RC","7":"RC","releases":[{"0":"2214","vim_version":"7.0","1":"7.0","script_version":"1.00","2":"1.00","version_comment":"Beautifully rewritten by Andy Wokula.","3":"Beautifully rewritten by Andy Wokula.","package":"switch.1.00.zip","4":"switch.1.00.zip","src_id":"11459","5":"11459","creation_date":"1254325847","6":"1254325847"},{"0":"2214","vim_version":"7.0","1":"7.0","script_version":"0.13","2":"0.13","version_comment":"Small improvement on the help options table","3":"Small improvement on the help options table","package":"switch.vim","4":"switch.vim","src_id":"10031","5":"10031","creation_date":"1235549449","6":"1235549449"},{"0":"2214","vim_version":"7.0","1":"7.0","script_version":"0.12","2":"0.12","version_comment":"Added: map keys now can be defined in the configuration section\r\nFixed: one global variable was not being removed","3":"Added: map keys now can be defined in the configuration section\r\nFixed: one global variable was not being removed","package":"switch.vim","4":"switch.vim","src_id":"9049","5":"9049","creation_date":"1217441384","6":"1217441384"},{"0":"2214","vim_version":"7.0","1":"7.0","script_version":"0.11","2":"0.11","version_comment":"1. Now operable in three modes;\r\n2. Now the list of options reflects their state;\r\n3. Now all the global variables are cleaned;\r\n4. Now all configurable variables are kept in one section.","3":"1. Now operable in three modes;\r\n2. Now the list of options reflects their state;\r\n3. Now all the global variables are cleaned;\r\n4. Now all configurable variables are kept in one section.","package":"switch.vim","4":"switch.vim","src_id":"9030","5":"9030","creation_date":"1217082119","6":"1217082119"},{"0":"2214","vim_version":"7.0","1":"7.0","script_version":"0.10","2":"0.10","version_comment":"Loads of nice improvements on its look, feel and control by Andy Wokula.","3":"Loads of nice improvements on its look, feel and control by Andy Wokula.","package":"switch.vim","4":"switch.vim","src_id":"8920","5":"8920","creation_date":"1215691727","6":"1215691727"},{"0":"2214","vim_version":"7.0","1":"7.0","script_version":"0.9.1","2":"0.9.1","version_comment":"Many 'key:option' pairs added to the default boolean options dictionary;\r\nEchoing of the dictionary's keys visually improved;\r\nDictionary's name changed to g:prev_Switch_Dict;","3":"Many 'key:option' pairs added to the default boolean options dictionary;\r\nEchoing of the dictionary's keys visually improved;\r\nDictionary's name changed to g:prev_Switch_Dict;","package":"switch.vim","4":"switch.vim","src_id":"8554","5":"8554","creation_date":"1208101639","6":"1208101639"},{"0":"2214","vim_version":"7.0","1":"7.0","script_version":"0.9","2":"0.9","version_comment":"Initial upload","3":"Initial upload","package":"switch.vim","4":"switch.vim","src_id":"8552","5":"8552","creation_date":"1208044614","6":"1208044614"}]},"2213":{"script_id":"2213","0":"2213","script_name":"VimTAP","1":"VimTAP","script_type":"utility","2":"utility","summary":"Test Anything Protocol for vim","3":"Test Anything Protocol for vim","description":"The Test Anything Protocol makes testing with different languages in the same project\r\neasy. It decouples the tests generating results from the harness interpreting the results.\r\nWith VimTAP we now have TAP for vim.\r\n\r\nFor now the following is implemented:\r\n - Plan\r\n - Ok\r\n - Is & Isnt\r\n - Like & Unlike\r\n - Diag\r\n\r\nDiag is probably not completely functional, yet. \\n, \\r and \\r\\n are all considered to\r\ndelimit lines.\r\n\r\nAlso a driver for running the tests from outside vim is provided. It can be used with\r\nPerl's TAP::Parser runtests utility.\r\n\r\nThis package is still work in progress!","4":"The Test Anything Protocol makes testing with different languages in the same project\r\neasy. It decouples the tests generating results from the harness interpreting the results.\r\nWith VimTAP we now have TAP for vim.\r\n\r\nFor now the following is implemented:\r\n - Plan\r\n - Ok\r\n - Is & Isnt\r\n - Like & Unlike\r\n - Diag\r\n\r\nDiag is probably not completely functional, yet. \\n, \\r and \\r\\n are all considered to\r\ndelimit lines.\r\n\r\nAlso a driver for running the tests from outside vim is provided. It can be used with\r\nPerl's TAP::Parser runtests utility.\r\n\r\nThis package is still work in progress!","install_details":"Unzip the zip file into your .vim\/vimfiles directory.\r\n\r\nOr, preferably, use pathogen: http:\/\/www.vim.org\/scripts\/script.php?script_id=2332","5":"Unzip the zip file into your .vim\/vimfiles directory.\r\n\r\nOr, preferably, use pathogen: http:\/\/www.vim.org\/scripts\/script.php?script_id=2332","first_name":"Meikel","6":"Meikel","last_name":"Brandmeyer","7":"Brandmeyer","releases":[{"0":"2213","vim_version":"7.0","1":"7.0","script_version":"0.4.0","2":"0.4.0","version_comment":"Provide commands for the most commonly used functions. Improve the reporting of the test results.","3":"Provide commands for the most commonly used functions. Improve the reporting of the test results.","package":"vimtap-0.4.0.zip","4":"vimtap-0.4.0.zip","src_id":"18469","5":"18469","creation_date":"1345752195","6":"1345752195"},{"0":"2213","vim_version":"7.0","1":"7.0","script_version":"0.3","2":"0.3","version_comment":"New Features:\r\n * Skip\r\n * Todo\r\n * BailOut\r\n * SetOutputFile\/FlushOutput\r\n\r\nUses now Harnesses under the hood.","3":"New Features:\r\n * Skip\r\n * Todo\r\n * BailOut\r\n * SetOutputFile\/FlushOutput\r\n\r\nUses now Harnesses under the hood.","package":"VimTAP-0.3.zip","4":"VimTAP-0.3.zip","src_id":"10071","5":"10071","creation_date":"1235945246","6":"1235945246"},{"0":"2213","vim_version":"7.0","1":"7.0","script_version":"0.2","2":"0.2","version_comment":"Two new test functions are introduced, Like und Unlike, for use with\r\nregular expressions instead of concrete values for comparison.\r\n\r\nSome online documentation was added.\r\n\r\nThe vtruntest.sh utility was also added to provide a driver, which can\r\nbe used to run tests from outside vim. One possibility is for example\r\nthe runtests of Perl's TAP::Parser: runtests -e 'sh vtruntest.sh'","3":"Two new test functions are introduced, Like und Unlike, for use with\r\nregular expressions instead of concrete values for comparison.\r\n\r\nSome online documentation was added.\r\n\r\nThe vtruntest.sh utility was also added to provide a driver, which can\r\nbe used to run tests from outside vim. One possibility is for example\r\nthe runtests of Perl's TAP::Parser: runtests -e 'sh vtruntest.sh'","package":"VimTAP-0.2.vba","4":"VimTAP-0.2.vba","src_id":"8561","5":"8561","creation_date":"1208186520","6":"1208186520"}]},"2212":{"script_id":"2212","0":"2212","script_name":"Obvious Mode","1":"Obvious Mode","script_type":"ftplugin","2":"ftplugin","summary":"Clearly indicate visually whether Vim is in insert mode","3":"Clearly indicate visually whether Vim is in insert mode","description":"Clearly indicate visually whether Vim is in insert mode via the StatusLine highlight group. [DEPRECATED]\r\n\r\nWhen you go into insert mode, the status line color changes. When you leave insert mode, the status line color changes back.\r\n\r\nGithub repo: https:\/\/github.com\/bsl\/obviousmode\r\n\r\nThis script is deprecated. Please consider using vim-powerline or powerline instead.","4":"Clearly indicate visually whether Vim is in insert mode via the StatusLine highlight group. [DEPRECATED]\r\n\r\nWhen you go into insert mode, the status line color changes. When you leave insert mode, the status line color changes back.\r\n\r\nGithub repo: https:\/\/github.com\/bsl\/obviousmode\r\n\r\nThis script is deprecated. Please consider using vim-powerline or powerline instead.","install_details":"Put obviousmode.vim in plugins\/\r\nYou probably want to\r\n    set laststatus=2\r\n\r\nSee comments for more configuration options.","5":"Put obviousmode.vim in plugins\/\r\nYou probably want to\r\n    set laststatus=2\r\n\r\nSee comments for more configuration options.","first_name":"Brian","6":"Brian","last_name":"Lewis","7":"Lewis","releases":[{"0":"2212","vim_version":"7.0","1":"7.0","script_version":"1.24","2":"1.24","version_comment":"Salman Halim <salmanhalim@gmail.com> contributed a fix for a StatusLineNC parsing bug.","3":"Salman Halim <salmanhalim@gmail.com> contributed a fix for a StatusLineNC parsing bug.","package":"obviousmode.vim","4":"obviousmode.vim","src_id":"16665","5":"16665","creation_date":"1318531211","6":"1318531211"},{"0":"2212","vim_version":"7.0","1":"7.0","script_version":"1.23","2":"1.23","version_comment":"Added GUI colors","3":"Added GUI colors","package":"obviousmode.vim","4":"obviousmode.vim","src_id":"16659","5":"16659","creation_date":"1318446127","6":"1318446127"},{"0":"2212","vim_version":"7.0","1":"7.0","script_version":"1.22","2":"1.22","version_comment":"Various improvements by Sergey Vlasov.","3":"Various improvements by Sergey Vlasov.","package":"obviousmode.vim","4":"obviousmode.vim","src_id":"13954","5":"13954","creation_date":"1285722100","6":"1285722100"},{"0":"2212","vim_version":"6.0","1":"6.0","script_version":"1.21","2":"1.21","version_comment":"fixing documentation error; said \"let laststatus=2\", should have said \"set laststatus=2\"","3":"fixing documentation error; said \"let laststatus=2\", should have said \"set laststatus=2\"","package":"obviousmode.vim","4":"obviousmode.vim","src_id":"8604","5":"8604","creation_date":"1209093715","6":"1209093715"},{"0":"2212","vim_version":"6.0","1":"6.0","script_version":"1.2","2":"1.2","version_comment":"More robust color saving\/restoration due to Erik Falor. Miscellaneous style\/performance improvements.","3":"More robust color saving\/restoration due to Erik Falor. Miscellaneous style\/performance improvements.","package":"obviousmode.vim","4":"obviousmode.vim","src_id":"8597","5":"8597","creation_date":"1208996695","6":"1208996695"},{"0":"2212","vim_version":"6.0","1":"6.0","script_version":"1.1","2":"1.1","version_comment":"Improvements. Thank you to Markus Braun.","3":"Improvements. Thank you to Markus Braun.","package":"obviousmode.vim","4":"obviousmode.vim","src_id":"8589","5":"8589","creation_date":"1208827300","6":"1208827300"},{"0":"2212","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"obviousmode.vim","4":"obviousmode.vim","src_id":"8549","5":"8549","creation_date":"1207991647","6":"1207991647"}]},"2211":{"script_id":"2211","0":"2211","script_name":"seoul","1":"seoul","script_type":"color scheme","2":"color scheme","summary":"Color scheme for use with the 88 color terminals (rxvt-unicode)","3":"Color scheme for use with the 88 color terminals (rxvt-unicode)","description":"A 88 color vim scheme intended for rxvt-unicode terminals. Will also work under xterm's 256 color mode. It uses special higlight groups for Ruby, but should function with other syntaxes as well. The name is inspired from the '88 summer olympics in Seoul, South Korea. The scheme is somewhat inspired by Justin Palmer's Vibrant Ink.\r\n\r\nThe latest version should be available at: http:\/\/redflavor.com\/seoul.vim\r\n\r\nFor a it's appearance check out this screenshot:  http:\/\/redflavor.com\/seoul.png","4":"A 88 color vim scheme intended for rxvt-unicode terminals. Will also work under xterm's 256 color mode. It uses special higlight groups for Ruby, but should function with other syntaxes as well. The name is inspired from the '88 summer olympics in Seoul, South Korea. The scheme is somewhat inspired by Justin Palmer's Vibrant Ink.\r\n\r\nThe latest version should be available at: http:\/\/redflavor.com\/seoul.vim\r\n\r\nFor a it's appearance check out this screenshot:  http:\/\/redflavor.com\/seoul.png","install_details":"1. Drop it into ~\/.vim\/colors\/\r\n2. Execute :colorscheme seoul\r\n3. Alternatively edit ~\/.vimrc and add: colorscheme seoul","5":"1. Drop it into ~\/.vim\/colors\/\r\n2. Execute :colorscheme seoul\r\n3. Alternatively edit ~\/.vimrc and add: colorscheme seoul","first_name":"Eivind","6":"Eivind","last_name":"Uggedal","7":"Uggedal","releases":[{"0":"2211","vim_version":"7.0","1":"7.0","script_version":"1.1","2":"1.1","version_comment":"Conditionals added so that 88 color mode is only enabled when supported.","3":"Conditionals added so that 88 color mode is only enabled when supported.","package":"seoul.vim","4":"seoul.vim","src_id":"8567","5":"8567","creation_date":"1208304170","6":"1208304170"},{"0":"2211","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"seoul.vim","4":"seoul.vim","src_id":"8546","5":"8546","creation_date":"1207878699","6":"1207878699"}]},"2210":{"script_id":"2210","0":"2210","script_name":"Shobogenzo","1":"Shobogenzo","script_type":"color scheme","2":"color scheme","summary":"Medium contrast colorscheme that is easy on the eyes","3":"Medium contrast colorscheme that is easy on the eyes","description":"This colorscheme was inspired by other low\/medium contrast colorschemes. None of them had the kind of colours that were easy on my eyes.\r\n\r\nI strove for a scheme that had a good contrast to make syntax highlighting help with establishing context as well as making sure the colours would not hurt your eyes over a longer period of time.","4":"This colorscheme was inspired by other low\/medium contrast colorschemes. None of them had the kind of colours that were easy on my eyes.\r\n\r\nI strove for a scheme that had a good contrast to make syntax highlighting help with establishing context as well as making sure the colours would not hurt your eyes over a longer period of time.","install_details":"Simply copy this file to your $HOME\/.vim\/colors and within vim do:\r\n\r\n:set colorscheme shobogenzo\r\n\r\nWhen using Gnome terminal you will need to make sure your profile's colors are set to xterm.\r\n","5":"Simply copy this file to your $HOME\/.vim\/colors and within vim do:\r\n\r\n:set colorscheme shobogenzo\r\n\r\nWhen using Gnome terminal you will need to make sure your profile's colors are set to xterm.\r\n","first_name":"Jeroen","6":"Jeroen","last_name":"Ruigrok van der Werven","7":"Ruigrok van der Werven","releases":[{"0":"2210","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"shobogenzo.vim","4":"shobogenzo.vim","src_id":"8537","5":"8537","creation_date":"1207706996","6":"1207706996"}]},"2209":{"script_id":"2209","0":"2209","script_name":"pyrex.vim","1":"pyrex.vim","script_type":"syntax","2":"syntax","summary":"Updated Pyrex.vim with Cython support","3":"Updated Pyrex.vim with Cython support","description":"Vim 7.1 pyrex.vim file with support for Cython (http:\/\/www.cython.org\/) additions.","4":"Vim 7.1 pyrex.vim file with support for Cython (http:\/\/www.cython.org\/) additions.","install_details":"I just replaced my original pyrex.vim, but you should be able to just drop the new one in your system or user specific vim syntax directory.","5":"I just replaced my original pyrex.vim, but you should be able to just drop the new one in your system or user specific vim syntax directory.","first_name":"Greg","6":"Greg","last_name":"Jandl","7":"Jandl","releases":[{"0":"2209","vim_version":"7.0","1":"7.0","script_version":"7.1.01","2":"7.1.01","version_comment":"Initial upload","3":"Initial upload","package":"pyrex.vim","4":"pyrex.vim","src_id":"8535","5":"8535","creation_date":"1207679024","6":"1207679024"}]},"2208":{"script_id":"2208","0":"2208","script_name":"Txtfmt (The Vim Highlighter)","1":"Txtfmt (The Vim Highlighter)","script_type":"utility","2":"utility","summary":"\"Rich text\" highlighting in Vim! (colors, underline, bold, italic, etc...)","3":"\"Rich text\" highlighting in Vim! (colors, underline, bold, italic, etc...)","description":"=== MOTIVATION ===\r\nVim's syntax highlighting is very useful for editing files in a particular programming language such as C or Perl. But what if you are using Vim to edit plain text: e.g., personal journal entries, miscellaneous notes or generic documents? In such cases, Vim's statically defined syntax regions are not very useful. What is really needed is a word processor's ability to apply highlighting to an arbitrary selection of text. \r\n\r\n=== OVERVIEW ===\r\nTxtfmt (The Vim Highlighter) is a combination syntax\/filetype plugin that allows you to highlight plain text in Vim. The highlighting mechanism uses invisible tokens that are inserted into a Txtfmt buffer with the aid of intuitive mappings provided by the filetype plugin. The plugin supports up to 8 configurable foreground and background colors, and all combinations of the following formatting attributes: bold, underline, italic, standout, reverse and undercurl.\r\nNote: Standout, reverse and undercurl are supported only in certain configurations.\r\n    :help txtfmt-'tokrange'\r\n\r\nNearly everything in this plugin is configurable, with defaults that should work for most users \"out of the box\". The following is a *partial* list of things that can be configured:\r\n    mappings\r\n    colors\r\n    range of characters used as (hidden) highlighting tokens\r\n\r\n=== GETTING STARTED ===\r\nThe usage examples below are intended only to give you a basic feel for how highlighting with Txtfmt works. You can find much more detailed documentation in the Txtfmt help file. However, the project's README.md on Github currently provides the best way to get up and running quickly with Txtfmt:\r\n\r\nhttps:\/\/github.com\/bpstahlman\/txtfmt\r\n\r\n=== SCREENSHOTS ===\r\nhttp:\/\/www.txtfmt.webs.com\r\n\r\n=== MANUAL VS AUTO MAPS ===\r\n!!!! NEW FEATURE (introduced in version 3.0) !!!!\r\nPrior to version 3, Txtfmt provided only what are now known as \"manual maps\". Manual maps operate at the level of individual tokens: e.g., insert a new highlighting token or replace an existing one at or near the cursor location. Although there is no highlighting task that cannot be accomplished with manual maps, manual mode forced users to think too much about the details of how to accomplish a particular highlighting task, especially when regions with pre-existing highlighting were involved. To simplify the use-case of highlighting existing text, Txtfmt version 3.0 introduced several new types of maps, known collectively as \"auto maps\". Auto maps fall into 2 basic categories:\r\n\r\n1. Visual maps: operate on the visually selected text\r\n2. Operator maps: operate on the text moved over (or included in a \"text object\")\r\n\r\nDocumentation Note: Auto maps are not yet fully documented in the Txtfmt help file, but their usage is quite simple (simpler than manual maps), so the usage examples below, coupled with the aforementioned README.md on Github, should be more than sufficient for most users to get started.\r\n\r\nThe next few sections give usage examples of visual\/operator auto maps and manual maps.\r\nNote: If you wish to try the examples now, you will need to install and load the plugin. If you're in a hurry, and are familiar with plugin installation, just drop the bundle of files in the proper location, start Vim and execute the following in an empty buffer:\r\n\r\n    :set ft=txtfmt\r\n\r\nThe \"INSTALL DETAILS\" section below discusses plugin load in greater detail...\r\n\r\n=== USAGE EXAMPLE (VISUAL AUTO MAPS) ===\r\nSuppose you wish to make a block of text blue, bold-italic.\r\nSelect the text to be highlighted using either mouse or visual mode (e.g., v or V). Then type...\r\n    \\h\r\nAt the resulting Txtfmt prompt, enter the following and hit Enter:\r\n    f=bi,cb\r\nNote: You could also have typed \"fbi,cb\" (without the `='), which would have *added* bold-italic on top of any existing format attributes.\r\nMnemonic: The `=' causes any existing format attributes to be overwritten; `+' (the default) adds to, and `-' subtracts from the existing attributes. More on this later...\r\n\r\n=== USAGE EXAMPLE (OPERATOR AUTO MAPS) ===\r\nSuppose you wish to make the word under the cursor red, bold-underline.\r\nIn normal mode, with cursor positioned on the word to be highlighted, type...\r\n    \\h\r\nVim is now waiting for a motion or text object. Enter the 'inner word' text object specification:\r\n    iw\r\nAt the resulting Txtfmt prompt, type the following and hit Enter:\r\n    f=bu,cr\r\n\r\nNow, suppose you wish to italicize and underline the line containing the word just highlighted and the subsequent 2 lines. In normal mode, with cursor still on the previously-highlighted word, type...\r\n    \\h\r\nOnce again, Vim awaits a motion. Enter the normal mode command to move down 2 lines:\r\n    2j\r\nAt the resulting Txtfmt prompt, type the following and hit Enter:\r\n    fui\r\nNote: Because you used \"fui\" instead of \"f=ui\", the word you highlighted in the first step has retained the bold attribute.\r\n\r\n=== SELECTIVE HIGHLIGHTING ===\r\nUp until now, we've been applying highlighting to all of the text in a range. But it is also possible to target specific sub-regions within the visually-selected or operated-on text. To apply highlighting selectively, append a `\/` to the highlighting spec, followed by a \"selector pattern expression\": e.g.,\r\n\r\n    <highlighting-spec> \/ <selector-pattern>\r\n\r\nSelector patterns are essentially boolean expressions combining format\/color specs with standard logical operators `&&', `||', `(...)', and `!'.\r\n\r\nExample: Suppose after highlighting many words and phrases in your document with f=b,cr,kg (bold, red text on green background), you decide that f=bi,cb (bold-italic, color blue) would have been a better choice. Making the change manually would be tedious; fortunately, selector patterns provide a better way. Simply select a range of lines containing all the text you wish to change and execute...\r\n    \\h\r\nAt the prompt, type the following and hit Enter:\r\n    f+i,cb,k-\/ fb && cr && kg\r\nExplanation: The highlighting spec adds italic, changes text color to blue and removes background highlighting altogether, but affects *only* bold red text on a green background.\r\n\r\nThe syntax of selector patterns is very similar to that of highlighting specs, and is best explained with examples:\r\n\r\n    fu\/cr\r\n        Action: Add underline attribute\r\n        Applies To: Red text\r\n\r\n    cb\/cr||f&bi\r\n        Action: Make foreground color blue\r\n        Applies To: Text that is red OR has *both* bold *and* italic attributes\r\n        Note: `f&' should be read as \"has *all* of the following attributes\"\r\n\r\n    fu,kg\/cr&&f|bi\r\n        Action: Add underline attribute AND make background color green\r\n        Applies To: Text that is red AND has *either* bold *or* italic attributes\r\n        Note: `f|' should be read as \"has *any* of the following attributes\"\r\n\r\n    fi\/cr||f=bu\r\n        Action: Add italic attribute\r\n        Applies To: Text that is red OR has bold-underline format attributes and no others\r\n\r\n    cb kr f-i \/ fbi & !(cr & k-)\r\n        Action: Set fg color blue, bg color red, and remove italic attribute\r\n        Applies To: Text that is bold-italic AND is NOT red with clear background\r\n\r\n** Points to Note **\r\nTip: Whitespace (ignored by Txtfmt) can be used to make the expressions (both highlighting and selector) easier to read.\r\nCaveat: `f&<attrs>' and `f|<attrs>' are atomic constructs, which do not permit embedded spaces.\r\nTip: For logical AND and OR, you can drop one of the &'s or |'s.\r\nRationale: Logical operators | and & are equivalent to || and &&, respectively, but to avoid confusion with the special `f|' and `f&' primitives, some users may prefer the longer forms.\r\nTip: You can drop the `=' from `f=<attrs>' in a selector expression.\r\nRationale: `=' is the default operator in selector expressions: i.e., f=ub is equivalent to fub.\r\nDistinction: In the auto-map highlighting spec itself (i.e., the \"action\" portion of the spec), f=ub and fub mean different things: the former means set to *exactly* underline-bold, whereas fub is a synonym for f+ub, which means add underline-bold on top of existing format attributes.\r\n\r\n=== USAGE EXAMPLE (MANUAL MAPS) ===\r\nNote: As mentioned earlier, auto maps are much easier to use than manual maps, but for the sake of completeness, here's a walkthrough showing the use of manual maps...\r\n\r\nSuppose you wish to enter some green text...\r\nIn Normal mode, you execute one of Txtfmt's \"insert-token\" mappings (e.g., \\i, \\I, \\a, \\A, \\o, etc.), and enter the following at the prompt:\r\n    cg\r\nMnemonic: color green\r\nThe text you type now is green.\r\n\r\nWhile typing green text, you wish to emphasize a phrase by making it bold-italic. You execute another mapping (e.g., CTRL-\\ CTRL-\\ in insert mode) and enter \"fbi\" or \"fib\" at the prompt.\r\nMnemonic: format bold italic\r\nThe text you type now is green bold-italic.\r\nNote: Inserting the bold-italic token did not affect the text color, because the color and format regions are completely \"orthogonal\".\r\n\r\nNow you wish to switch to a blue background. Execute another mapping (e.g., CTRL-\\ CTRL-\\ in insert mode) and enter \"kb\" at the prompt.\r\nMnemonic: bac_k_ground blue\r\nThe text you type now is green bold-italic on a blue background.\r\n\r\nAt this point, any of the open highlighting regions can be terminated with the corresponding `-' specifier:\r\n    f- (no format attributes)\r\n    c- (no color)\r\n    k- (no background color)\r\n\r\nAlternatively, you can enter a non-terminator highlighting spec to change subsequent highlighting without explicitly terminating the preceding region. Inserting \"cr\", for instance, would switch from green text color to red.\r\n\r\nTo finish the example, let's terminate the 3 active regions by executing the insert-token mapping (CTRL-\\ CTRL-\\) one last time and entering the following at the prompt:\r\n    c-,f-,k-\r\nMnemonic: remove color, remove format, remove bac_k_ground color\r\nNow, the text you type should be plain, unhighlighted text. Notice how multiple format\/color specifiers can be concatenated in a comma (or dot) separated list, thereby reducing the number of times you have to execute the mapping. You can use this feature to insert both the start and end tokens of a region at once: e.g.,\r\n    fbi.f-\r\nThis specifier would enter a bold-italic token, followed immediately by the \"no format\" token, leaving the cursor between the two.\r\nExplanation: Txtfmt lets you replace one of the commas with a dot to indicate where the cursor should be positioned after the token insertion.\r\n\r\n=== EXPORTING HIGHLIGHTED DOCUMENTS ===\r\nIf you wish to make your highlighted documents available to non-Vim users, simply use the :TOhtml command distributed with Vim to output an HTML version of the Txtfmt buffer.\r\n\r\n=== TUTORIAL ===\r\n\r\nhttps:\/\/github.com\/bpstahlman\/txtfmt\r\n\r\n=== BUG REPORTS AND FEATURE REQUESTS ===\r\n\r\nhttps:\/\/github.com\/bpstahlman\/txtfmt\/issues\r\n\r\n=== FEEDBACK ===\r\nI would greatly appreciate your feedback on this plugin:\r\nbrettstahlman AT gmail DOT com\r\n\r\nAlso, please rate this plugin!\r\n\r\n=== SUGGESTED USES ===\r\nThe following applications represent a few of the many possible uses of the Txtfmt plugin:\r\n    -For taking notes (e.g., notes taken while reviewing large programming projects)\r\n    -As part of a personal journaling system\r\n    -For highlighting .otl files created with Ned Konz' TVO (The Vim Outliner) plugin\r\n    -For highlighting files created with 'Notes' (Hari Krishna Dara's lightweight note management plugin)\r\n    -For highlighting text files created with Yongping Guo's TxtBrowser plugin\r\n    -For beautifying block diagrams created with Dr. Charles Campbell's drawit plugin\r\n    -For sprucing up programming language comments\r\n     Don't laugh! You can embed Txtfmt formatting regions within other syntax regions (e.g., C comments)\r\n     :help txtfmt-'nested'\r\n    etc...\r\n\r\n\r\n    vim:et:ts=4:sw=4:tw=0:linebreak\r\n","4":"=== MOTIVATION ===\r\nVim's syntax highlighting is very useful for editing files in a particular programming language such as C or Perl. But what if you are using Vim to edit plain text: e.g., personal journal entries, miscellaneous notes or generic documents? In such cases, Vim's statically defined syntax regions are not very useful. What is really needed is a word processor's ability to apply highlighting to an arbitrary selection of text. \r\n\r\n=== OVERVIEW ===\r\nTxtfmt (The Vim Highlighter) is a combination syntax\/filetype plugin that allows you to highlight plain text in Vim. The highlighting mechanism uses invisible tokens that are inserted into a Txtfmt buffer with the aid of intuitive mappings provided by the filetype plugin. The plugin supports up to 8 configurable foreground and background colors, and all combinations of the following formatting attributes: bold, underline, italic, standout, reverse and undercurl.\r\nNote: Standout, reverse and undercurl are supported only in certain configurations.\r\n    :help txtfmt-'tokrange'\r\n\r\nNearly everything in this plugin is configurable, with defaults that should work for most users \"out of the box\". The following is a *partial* list of things that can be configured:\r\n    mappings\r\n    colors\r\n    range of characters used as (hidden) highlighting tokens\r\n\r\n=== GETTING STARTED ===\r\nThe usage examples below are intended only to give you a basic feel for how highlighting with Txtfmt works. You can find much more detailed documentation in the Txtfmt help file. However, the project's README.md on Github currently provides the best way to get up and running quickly with Txtfmt:\r\n\r\nhttps:\/\/github.com\/bpstahlman\/txtfmt\r\n\r\n=== SCREENSHOTS ===\r\nhttp:\/\/www.txtfmt.webs.com\r\n\r\n=== MANUAL VS AUTO MAPS ===\r\n!!!! NEW FEATURE (introduced in version 3.0) !!!!\r\nPrior to version 3, Txtfmt provided only what are now known as \"manual maps\". Manual maps operate at the level of individual tokens: e.g., insert a new highlighting token or replace an existing one at or near the cursor location. Although there is no highlighting task that cannot be accomplished with manual maps, manual mode forced users to think too much about the details of how to accomplish a particular highlighting task, especially when regions with pre-existing highlighting were involved. To simplify the use-case of highlighting existing text, Txtfmt version 3.0 introduced several new types of maps, known collectively as \"auto maps\". Auto maps fall into 2 basic categories:\r\n\r\n1. Visual maps: operate on the visually selected text\r\n2. Operator maps: operate on the text moved over (or included in a \"text object\")\r\n\r\nDocumentation Note: Auto maps are not yet fully documented in the Txtfmt help file, but their usage is quite simple (simpler than manual maps), so the usage examples below, coupled with the aforementioned README.md on Github, should be more than sufficient for most users to get started.\r\n\r\nThe next few sections give usage examples of visual\/operator auto maps and manual maps.\r\nNote: If you wish to try the examples now, you will need to install and load the plugin. If you're in a hurry, and are familiar with plugin installation, just drop the bundle of files in the proper location, start Vim and execute the following in an empty buffer:\r\n\r\n    :set ft=txtfmt\r\n\r\nThe \"INSTALL DETAILS\" section below discusses plugin load in greater detail...\r\n\r\n=== USAGE EXAMPLE (VISUAL AUTO MAPS) ===\r\nSuppose you wish to make a block of text blue, bold-italic.\r\nSelect the text to be highlighted using either mouse or visual mode (e.g., v or V). Then type...\r\n    \\h\r\nAt the resulting Txtfmt prompt, enter the following and hit Enter:\r\n    f=bi,cb\r\nNote: You could also have typed \"fbi,cb\" (without the `='), which would have *added* bold-italic on top of any existing format attributes.\r\nMnemonic: The `=' causes any existing format attributes to be overwritten; `+' (the default) adds to, and `-' subtracts from the existing attributes. More on this later...\r\n\r\n=== USAGE EXAMPLE (OPERATOR AUTO MAPS) ===\r\nSuppose you wish to make the word under the cursor red, bold-underline.\r\nIn normal mode, with cursor positioned on the word to be highlighted, type...\r\n    \\h\r\nVim is now waiting for a motion or text object. Enter the 'inner word' text object specification:\r\n    iw\r\nAt the resulting Txtfmt prompt, type the following and hit Enter:\r\n    f=bu,cr\r\n\r\nNow, suppose you wish to italicize and underline the line containing the word just highlighted and the subsequent 2 lines. In normal mode, with cursor still on the previously-highlighted word, type...\r\n    \\h\r\nOnce again, Vim awaits a motion. Enter the normal mode command to move down 2 lines:\r\n    2j\r\nAt the resulting Txtfmt prompt, type the following and hit Enter:\r\n    fui\r\nNote: Because you used \"fui\" instead of \"f=ui\", the word you highlighted in the first step has retained the bold attribute.\r\n\r\n=== SELECTIVE HIGHLIGHTING ===\r\nUp until now, we've been applying highlighting to all of the text in a range. But it is also possible to target specific sub-regions within the visually-selected or operated-on text. To apply highlighting selectively, append a `\/` to the highlighting spec, followed by a \"selector pattern expression\": e.g.,\r\n\r\n    <highlighting-spec> \/ <selector-pattern>\r\n\r\nSelector patterns are essentially boolean expressions combining format\/color specs with standard logical operators `&&', `||', `(...)', and `!'.\r\n\r\nExample: Suppose after highlighting many words and phrases in your document with f=b,cr,kg (bold, red text on green background), you decide that f=bi,cb (bold-italic, color blue) would have been a better choice. Making the change manually would be tedious; fortunately, selector patterns provide a better way. Simply select a range of lines containing all the text you wish to change and execute...\r\n    \\h\r\nAt the prompt, type the following and hit Enter:\r\n    f+i,cb,k-\/ fb && cr && kg\r\nExplanation: The highlighting spec adds italic, changes text color to blue and removes background highlighting altogether, but affects *only* bold red text on a green background.\r\n\r\nThe syntax of selector patterns is very similar to that of highlighting specs, and is best explained with examples:\r\n\r\n    fu\/cr\r\n        Action: Add underline attribute\r\n        Applies To: Red text\r\n\r\n    cb\/cr||f&bi\r\n        Action: Make foreground color blue\r\n        Applies To: Text that is red OR has *both* bold *and* italic attributes\r\n        Note: `f&' should be read as \"has *all* of the following attributes\"\r\n\r\n    fu,kg\/cr&&f|bi\r\n        Action: Add underline attribute AND make background color green\r\n        Applies To: Text that is red AND has *either* bold *or* italic attributes\r\n        Note: `f|' should be read as \"has *any* of the following attributes\"\r\n\r\n    fi\/cr||f=bu\r\n        Action: Add italic attribute\r\n        Applies To: Text that is red OR has bold-underline format attributes and no others\r\n\r\n    cb kr f-i \/ fbi & !(cr & k-)\r\n        Action: Set fg color blue, bg color red, and remove italic attribute\r\n        Applies To: Text that is bold-italic AND is NOT red with clear background\r\n\r\n** Points to Note **\r\nTip: Whitespace (ignored by Txtfmt) can be used to make the expressions (both highlighting and selector) easier to read.\r\nCaveat: `f&<attrs>' and `f|<attrs>' are atomic constructs, which do not permit embedded spaces.\r\nTip: For logical AND and OR, you can drop one of the &'s or |'s.\r\nRationale: Logical operators | and & are equivalent to || and &&, respectively, but to avoid confusion with the special `f|' and `f&' primitives, some users may prefer the longer forms.\r\nTip: You can drop the `=' from `f=<attrs>' in a selector expression.\r\nRationale: `=' is the default operator in selector expressions: i.e., f=ub is equivalent to fub.\r\nDistinction: In the auto-map highlighting spec itself (i.e., the \"action\" portion of the spec), f=ub and fub mean different things: the former means set to *exactly* underline-bold, whereas fub is a synonym for f+ub, which means add underline-bold on top of existing format attributes.\r\n\r\n=== USAGE EXAMPLE (MANUAL MAPS) ===\r\nNote: As mentioned earlier, auto maps are much easier to use than manual maps, but for the sake of completeness, here's a walkthrough showing the use of manual maps...\r\n\r\nSuppose you wish to enter some green text...\r\nIn Normal mode, you execute one of Txtfmt's \"insert-token\" mappings (e.g., \\i, \\I, \\a, \\A, \\o, etc.), and enter the following at the prompt:\r\n    cg\r\nMnemonic: color green\r\nThe text you type now is green.\r\n\r\nWhile typing green text, you wish to emphasize a phrase by making it bold-italic. You execute another mapping (e.g., CTRL-\\ CTRL-\\ in insert mode) and enter \"fbi\" or \"fib\" at the prompt.\r\nMnemonic: format bold italic\r\nThe text you type now is green bold-italic.\r\nNote: Inserting the bold-italic token did not affect the text color, because the color and format regions are completely \"orthogonal\".\r\n\r\nNow you wish to switch to a blue background. Execute another mapping (e.g., CTRL-\\ CTRL-\\ in insert mode) and enter \"kb\" at the prompt.\r\nMnemonic: bac_k_ground blue\r\nThe text you type now is green bold-italic on a blue background.\r\n\r\nAt this point, any of the open highlighting regions can be terminated with the corresponding `-' specifier:\r\n    f- (no format attributes)\r\n    c- (no color)\r\n    k- (no background color)\r\n\r\nAlternatively, you can enter a non-terminator highlighting spec to change subsequent highlighting without explicitly terminating the preceding region. Inserting \"cr\", for instance, would switch from green text color to red.\r\n\r\nTo finish the example, let's terminate the 3 active regions by executing the insert-token mapping (CTRL-\\ CTRL-\\) one last time and entering the following at the prompt:\r\n    c-,f-,k-\r\nMnemonic: remove color, remove format, remove bac_k_ground color\r\nNow, the text you type should be plain, unhighlighted text. Notice how multiple format\/color specifiers can be concatenated in a comma (or dot) separated list, thereby reducing the number of times you have to execute the mapping. You can use this feature to insert both the start and end tokens of a region at once: e.g.,\r\n    fbi.f-\r\nThis specifier would enter a bold-italic token, followed immediately by the \"no format\" token, leaving the cursor between the two.\r\nExplanation: Txtfmt lets you replace one of the commas with a dot to indicate where the cursor should be positioned after the token insertion.\r\n\r\n=== EXPORTING HIGHLIGHTED DOCUMENTS ===\r\nIf you wish to make your highlighted documents available to non-Vim users, simply use the :TOhtml command distributed with Vim to output an HTML version of the Txtfmt buffer.\r\n\r\n=== TUTORIAL ===\r\n\r\nhttps:\/\/github.com\/bpstahlman\/txtfmt\r\n\r\n=== BUG REPORTS AND FEATURE REQUESTS ===\r\n\r\nhttps:\/\/github.com\/bpstahlman\/txtfmt\/issues\r\n\r\n=== FEEDBACK ===\r\nI would greatly appreciate your feedback on this plugin:\r\nbrettstahlman AT gmail DOT com\r\n\r\nAlso, please rate this plugin!\r\n\r\n=== SUGGESTED USES ===\r\nThe following applications represent a few of the many possible uses of the Txtfmt plugin:\r\n    -For taking notes (e.g., notes taken while reviewing large programming projects)\r\n    -As part of a personal journaling system\r\n    -For highlighting .otl files created with Ned Konz' TVO (The Vim Outliner) plugin\r\n    -For highlighting files created with 'Notes' (Hari Krishna Dara's lightweight note management plugin)\r\n    -For highlighting text files created with Yongping Guo's TxtBrowser plugin\r\n    -For beautifying block diagrams created with Dr. Charles Campbell's drawit plugin\r\n    -For sprucing up programming language comments\r\n     Don't laugh! You can embed Txtfmt formatting regions within other syntax regions (e.g., C comments)\r\n     :help txtfmt-'nested'\r\n    etc...\r\n\r\n\r\n    vim:et:ts=4:sw=4:tw=0:linebreak\r\n","install_details":"=== DISTRIBUTED FILES ===\r\nThe Txtfmt distribution comprises the following files:\r\n\r\ndoc\/txtfmt.txt\r\n    Txtfmt help file\r\nftplugin\/txtfmt.vim\r\n    Txtfmt filetype plugin (contains mappings for working with Txtfmt tokens)\r\nsyntax\/txtfmt.vim\r\n    Txtfmt syntax file (defines the Txtfmt syntax highlighting)\r\nplugin\/txtfmt.vim\r\n    Txtfmt common configuration code (contains configuration script needed by\r\n    both the filetype and syntax plugins)\r\nindent_patch.txt\r\n    (Not needed by most users)\r\n    Bram Moolenaar's patch to fix indent.vim's handling of dot-separated lists\r\n    in 'filetype' option values (required only if your version of Vim is older\r\n    than 7.2 and you plan to \"nest\" Txtfmt within other filetypes) For details,\r\n        :help txtfmt-combining.\r\n\r\n=== INSTALLATION ===\r\nTxtfmt can be installed using any of the standard Vim plugin mechanisms: e.g., Pathogen, Vundle, etc. If you're not using a plugin manager, simply uncompress the Txtfmt distribution somewhere in your 'runtimepath' (e.g., ~\/.vim\/) and run the following command to prepare the Txtfmt help:\r\n\r\n    :helptags ALL\r\n\r\n=== PLUGIN LOADING ===\r\nCaveat: Like most plugins, Txtfmt requires both filetype detection and syntax highlighting to be enabled, yet neither is enabled in Vim's default configuration; thus, unless you copied the commands from the example vimrc (or source the example file from your own vimrc), you will probably need to add something like the following to your vimrc:\r\n\r\n    syntax on\r\n    filetype plugin on\r\n\r\nAt this point, if the plugin has been properly installed, you can load the plugin manually by executing the following from the Vim command line:\r\n\r\n    :set ft=txtfmt\r\n\r\nA better approach, however, is to ensure that Txtfmt is loaded automatically whenever you open certain files. Several approaches are outlined below...\r\n\r\nMethod 1: Custom filetype.vim\r\n-----------------------------\r\n\r\nIf it doesn't already exist, create your own filetype.vim in the first directory of 'runtimepath' (e.g., ~\/.vim) and add an autocommand that associates txtfmt with the desired file extensions.\r\n\r\nExample:\r\n    \" -- filetype.vim --\r\n    augroup filetypedetect\r\n      \" Treat files with the following extensions as Txtfmt files: .txt, .tf, .jnl\r\n      au! BufRead,BufNewFile *.txt,*.tf,*.jnl    setfiletype txtfmt\r\n    augroup END\r\n\r\nMethod 2: Plugin-specific file in ftdetect\r\n------------------------------------------\r\n\r\nIf it doesn't already exist, create your own \"ftdetect\" folder in the first directory of 'runtimepath' (e.g., ~\/.vim). In ftdetect, create a file called \"txtfmt.vim\" containing an autocommand that associates txtfmt with the desired file extensions.\r\n\r\nExample:\r\n    \" -- ftdetect\/txtfmt.vim --\r\n    \" Treat files with the following extensions as Txtfmt files: .txt, .tf, .jnl\r\n    au! BufRead,BufNewFile *.txt,*.tf,*.jnl    set filetype=txtfmt\r\n\r\nNote: When ftdetect is used, there's no need to wrap your autocommands in an `augroup` block, as your script is sourced from within an autocommand group.\r\n\r\n    :help new-filetype\r\n\r\nMethod 3: Modeline\r\n------------------\r\n\r\nModelines can be used to set filetype=txtfmt when the files you wish to highlight do not share a common extension. Simply add a line like the following to the beginning or end of a file you wish to highlight:\r\n\r\n    vim:ft=txtfmt\r\n\r\nNote: You'll need to close and reopen the file to cause the line to be processed.\r\n\r\n=== COMBINING TXTFMT WITH OTHER FILETYPES ===\r\nIt is quite possible to use Txtfmt highlighting in a file associated with another filetype plugin. For instance, if you're using a plugin that facilitates note-taking or journaling, you may wish to use Txtfmt to highlight the entries. It is even possible to \"nest\" Txtfmt highlighting regions within syntax regions defined by other plugins, but nesting must be enabled explicitly by setting the `txtfmt-'nested'` option.\r\n\r\n    :help txtfmt-combining\r\n    :help txtfmt-nesting\r\n","5":"=== DISTRIBUTED FILES ===\r\nThe Txtfmt distribution comprises the following files:\r\n\r\ndoc\/txtfmt.txt\r\n    Txtfmt help file\r\nftplugin\/txtfmt.vim\r\n    Txtfmt filetype plugin (contains mappings for working with Txtfmt tokens)\r\nsyntax\/txtfmt.vim\r\n    Txtfmt syntax file (defines the Txtfmt syntax highlighting)\r\nplugin\/txtfmt.vim\r\n    Txtfmt common configuration code (contains configuration script needed by\r\n    both the filetype and syntax plugins)\r\nindent_patch.txt\r\n    (Not needed by most users)\r\n    Bram Moolenaar's patch to fix indent.vim's handling of dot-separated lists\r\n    in 'filetype' option values (required only if your version of Vim is older\r\n    than 7.2 and you plan to \"nest\" Txtfmt within other filetypes) For details,\r\n        :help txtfmt-combining.\r\n\r\n=== INSTALLATION ===\r\nTxtfmt can be installed using any of the standard Vim plugin mechanisms: e.g., Pathogen, Vundle, etc. If you're not using a plugin manager, simply uncompress the Txtfmt distribution somewhere in your 'runtimepath' (e.g., ~\/.vim\/) and run the following command to prepare the Txtfmt help:\r\n\r\n    :helptags ALL\r\n\r\n=== PLUGIN LOADING ===\r\nCaveat: Like most plugins, Txtfmt requires both filetype detection and syntax highlighting to be enabled, yet neither is enabled in Vim's default configuration; thus, unless you copied the commands from the example vimrc (or source the example file from your own vimrc), you will probably need to add something like the following to your vimrc:\r\n\r\n    syntax on\r\n    filetype plugin on\r\n\r\nAt this point, if the plugin has been properly installed, you can load the plugin manually by executing the following from the Vim command line:\r\n\r\n    :set ft=txtfmt\r\n\r\nA better approach, however, is to ensure that Txtfmt is loaded automatically whenever you open certain files. Several approaches are outlined below...\r\n\r\nMethod 1: Custom filetype.vim\r\n-----------------------------\r\n\r\nIf it doesn't already exist, create your own filetype.vim in the first directory of 'runtimepath' (e.g., ~\/.vim) and add an autocommand that associates txtfmt with the desired file extensions.\r\n\r\nExample:\r\n    \" -- filetype.vim --\r\n    augroup filetypedetect\r\n      \" Treat files with the following extensions as Txtfmt files: .txt, .tf, .jnl\r\n      au! BufRead,BufNewFile *.txt,*.tf,*.jnl    setfiletype txtfmt\r\n    augroup END\r\n\r\nMethod 2: Plugin-specific file in ftdetect\r\n------------------------------------------\r\n\r\nIf it doesn't already exist, create your own \"ftdetect\" folder in the first directory of 'runtimepath' (e.g., ~\/.vim). In ftdetect, create a file called \"txtfmt.vim\" containing an autocommand that associates txtfmt with the desired file extensions.\r\n\r\nExample:\r\n    \" -- ftdetect\/txtfmt.vim --\r\n    \" Treat files with the following extensions as Txtfmt files: .txt, .tf, .jnl\r\n    au! BufRead,BufNewFile *.txt,*.tf,*.jnl    set filetype=txtfmt\r\n\r\nNote: When ftdetect is used, there's no need to wrap your autocommands in an `augroup` block, as your script is sourced from within an autocommand group.\r\n\r\n    :help new-filetype\r\n\r\nMethod 3: Modeline\r\n------------------\r\n\r\nModelines can be used to set filetype=txtfmt when the files you wish to highlight do not share a common extension. Simply add a line like the following to the beginning or end of a file you wish to highlight:\r\n\r\n    vim:ft=txtfmt\r\n\r\nNote: You'll need to close and reopen the file to cause the line to be processed.\r\n\r\n=== COMBINING TXTFMT WITH OTHER FILETYPES ===\r\nIt is quite possible to use Txtfmt highlighting in a file associated with another filetype plugin. For instance, if you're using a plugin that facilitates note-taking or journaling, you may wish to use Txtfmt to highlight the entries. It is even possible to \"nest\" Txtfmt highlighting regions within syntax regions defined by other plugins, but nesting must be enabled explicitly by setting the `txtfmt-'nested'` option.\r\n\r\n    :help txtfmt-combining\r\n    :help txtfmt-nesting\r\n","first_name":"Brett","6":"Brett","last_name":"Stahlman","7":"Stahlman","releases":[{"0":"2208","vim_version":"7.4","1":"7.4","script_version":"5.0","2":"5.0","version_comment":"Version 5.0\r\n** New Feature: \"Shortcut Maps\"\r\nCustomizable visual maps and operators that let you apply your favorite highlighting combinations with fewer keystrokes and less cognitive load.","3":"Version 5.0\r\n** New Feature: \"Shortcut Maps\"\r\nCustomizable visual maps and operators that let you apply your favorite highlighting combinations with fewer keystrokes and less cognitive load.","package":"txtfmt_v5.0.tar.gz","4":"txtfmt_v5.0.tar.gz","src_id":"28457","5":"28457","creation_date":"1683442432","6":"1683442432"},{"0":"2208","vim_version":"7.4","1":"7.4","script_version":"4.2.1","2":"4.2.1","version_comment":"Version 4.2.1\r\nBugfix: Fixed bug capable of generating error after a highlighting operation on a region beginning at the start of a line.","3":"Version 4.2.1\r\nBugfix: Fixed bug capable of generating error after a highlighting operation on a region beginning at the start of a line.","package":"txtfmt_v4.2.1.tar.gz","4":"txtfmt_v4.2.1.tar.gz","src_id":"28415","5":"28415","creation_date":"1681947606","6":"1681947606"},{"0":"2208","vim_version":"7.4","1":"7.4","script_version":"4.2","2":"4.2","version_comment":"Version 4.2\r\nBugfix: Fixed broken \"smart delete\" operator.\r\nEnhancement: Added logic that treats backslashes specially when escape=bslash, doubling or halving them as necessary to prevent a highlighting or smart delete operation from changing the number of *displayed* backslashes.\r\nEnhancement: Stopped treating CTRL-C cancellation of a highlighting\/delete operation as an error.","3":"Version 4.2\r\nBugfix: Fixed broken \"smart delete\" operator.\r\nEnhancement: Added logic that treats backslashes specially when escape=bslash, doubling or halving them as necessary to prevent a highlighting or smart delete operation from changing the number of *displayed* backslashes.\r\nEnhancement: Stopped treating CTRL-C cancellation of a highlighting\/delete operation as an error.","package":"txtfmt_v4.2.tar.gz","4":"txtfmt_v4.2.tar.gz","src_id":"28412","5":"28412","creation_date":"1681702720","6":"1681702720"},{"0":"2208","vim_version":"7.0","1":"7.0","script_version":"v4.1a","2":"v4.1a","version_comment":"Version 4.1 Alpha release:\r\n** !!! Much Faster Syntax !!!: Eliminated redundant group permutations to\r\nachieve a signficant reduction in the number of syntax groups required for\r\nhighlighting.\r\n** New Feature(s): \"Smart\" versions of indent\/dedent\/retab maps\/commands,\r\nwhich take Txtfmt 'leadingindent' option into account","3":"Version 4.1 Alpha release:\r\n** !!! Much Faster Syntax !!!: Eliminated redundant group permutations to\r\nachieve a signficant reduction in the number of syntax groups required for\r\nhighlighting.\r\n** New Feature(s): \"Smart\" versions of indent\/dedent\/retab maps\/commands,\r\nwhich take Txtfmt 'leadingindent' option into account","package":"txtfmt_v4.1a.tar.gz","4":"txtfmt_v4.1a.tar.gz","src_id":"27162","5":"27162","creation_date":"1589713319","6":"1589713319"},{"0":"2208","vim_version":"7.4","1":"7.4","script_version":"4.0a","2":"4.0a","version_comment":"Version 4.0 Alpha release:\r\n** New Feature: 'leadingindent' option permits suppression of highlighting in whitespace at start of line.\r\n** Syntax Engine Refactor: All syntax now generated dynamically. (Prior to this, certain sections of vimscript were generated offline by an embedded perl script.)","3":"Version 4.0 Alpha release:\r\n** New Feature: 'leadingindent' option permits suppression of highlighting in whitespace at start of line.\r\n** Syntax Engine Refactor: All syntax now generated dynamically. (Prior to this, certain sections of vimscript were generated offline by an embedded perl script.)","package":"txtfmt_v4.0a.tar.gz","4":"txtfmt_v4.0a.tar.gz","src_id":"26288","5":"26288","creation_date":"1543208280","6":"1543208280"},{"0":"2208","vim_version":"7.0","1":"7.0","script_version":"3.1","2":"3.1","version_comment":"Bugfix: In \"linewise visual\" mode only, highlight map (\\h) generated error on attempt to restore selection, and smart delete map (\\d) failed to delete entire selection (left one too many newlines).","3":"Bugfix: In \"linewise visual\" mode only, highlight map (\\h) generated error on attempt to restore selection, and smart delete map (\\d) failed to delete entire selection (left one too many newlines).","package":"txtfmt_v3.1.tar.gz","4":"txtfmt_v3.1.tar.gz","src_id":"24489","5":"24489","creation_date":"1472920041","6":"1472920041"},{"0":"2208","vim_version":"7.0","1":"7.0","script_version":"3.0","2":"3.0","version_comment":"\"Auto Maps\" Formal Release:\r\n-Visual\/operator maps simplify highlighting: visually select (or move over) region to be highlighted, specify desired change, and let Txtfmt \"make it so\". (No more fiddling with start\/end tokens.)\r\n-Selective highlighting via \"selector pattern expressions\": e.g., add italic, but only to text that is currently red-bold; change currently red text to yellow; etc...\r\n-Various minor fixes\/enhancements.\r\n","3":"\"Auto Maps\" Formal Release:\r\n-Visual\/operator maps simplify highlighting: visually select (or move over) region to be highlighted, specify desired change, and let Txtfmt \"make it so\". (No more fiddling with start\/end tokens.)\r\n-Selective highlighting via \"selector pattern expressions\": e.g., add italic, but only to text that is currently red-bold; change currently red text to yellow; etc...\r\n-Various minor fixes\/enhancements.\r\n","package":"txtfmt_v3.0.tar.gz","4":"txtfmt_v3.0.tar.gz","src_id":"24246","5":"24246","creation_date":"1463228292","6":"1463228292"},{"0":"2208","vim_version":"7.0","1":"7.0","script_version":"3.0beta-2","2":"3.0beta-2","version_comment":"Added \"True Color\" support for color terminals in Neovim. (Prior to this, highlighting was invisible in Neovim color terminals when the $NVIM_TUI_ENABLE_TRUE_COLOR env var was used to enable 24-bit \"true color\".)","3":"Added \"True Color\" support for color terminals in Neovim. (Prior to this, highlighting was invisible in Neovim color terminals when the $NVIM_TUI_ENABLE_TRUE_COLOR env var was used to enable 24-bit \"true color\".)","package":"txtfmt_v3.0beta-2.tar.gz","4":"txtfmt_v3.0beta-2.tar.gz","src_id":"24211","5":"24211","creation_date":"1461883450","6":"1461883450"},{"0":"2208","vim_version":"7.0","1":"7.0","script_version":"3.0beta-1","2":"3.0beta-1","version_comment":"\"Auto-maps\" Beta release:\r\n!!! New Feature !!! - \"Selective Highlighting\"\r\nModify highlighting spec with a \"selector pattern\" that targets only a subset of the selection: e.g.,\r\n    f+u \/ cr && fbi\r\n...to add underline attribute, but only to text that is red bold-italic already.\r\n","3":"\"Auto-maps\" Beta release:\r\n!!! New Feature !!! - \"Selective Highlighting\"\r\nModify highlighting spec with a \"selector pattern\" that targets only a subset of the selection: e.g.,\r\n    f+u \/ cr && fbi\r\n...to add underline attribute, but only to text that is red bold-italic already.\r\n","package":"txtfmt_v3.0beta-1.tar.gz","4":"txtfmt_v3.0beta-1.tar.gz","src_id":"24196","5":"24196","creation_date":"1461412610","6":"1461412610"},{"0":"2208","vim_version":"7.0","1":"7.0","script_version":"3.0alpha-6","2":"3.0alpha-6","version_comment":"Bugfix: Automatic line breaking during token insertion breaks auto map highlighting. (Occurs only when 'textwidth' is nonzero, and the tokens inserted by an auto map cause 'textwidth' to be exceeded.)","3":"Bugfix: Automatic line breaking during token insertion breaks auto map highlighting. (Occurs only when 'textwidth' is nonzero, and the tokens inserted by an auto map cause 'textwidth' to be exceeded.)","package":"txtfmt_v3.0alpha-6.tar.gz","4":"txtfmt_v3.0alpha-6.tar.gz","src_id":"24183","5":"24183","creation_date":"1460920603","6":"1460920603"},{"0":"2208","vim_version":"7.0","1":"7.0","script_version":"3.0alpha-5","2":"3.0alpha-5","version_comment":"\"Auto-maps\" alpha release:\r\nBugfix: Calls to s:Contains_hlable were causing cursor to move backwards spuriously (due to failure to restore cursor pos after temporary move), which broke highlighting in certain scenarios (and could conceivably have been preventing timely exit from Vmap_collect search loop).\r\nNote: This release *may* provide a fix for the Annis Monadjem issue.","3":"\"Auto-maps\" alpha release:\r\nBugfix: Calls to s:Contains_hlable were causing cursor to move backwards spuriously (due to failure to restore cursor pos after temporary move), which broke highlighting in certain scenarios (and could conceivably have been preventing timely exit from Vmap_collect search loop).\r\nNote: This release *may* provide a fix for the Annis Monadjem issue.","package":"txtfmt_v3.0alpha-5.tar.gz","4":"txtfmt_v3.0alpha-5.tar.gz","src_id":"24165","5":"24165","creation_date":"1460293646","6":"1460293646"},{"0":"2208","vim_version":"7.0","1":"7.0","script_version":"3.0alpha-4","2":"3.0alpha-4","version_comment":"\"Auto-maps\" alpha release:\r\nMinor change to logic pertaining to cleanup of unnecessary tokens near end of buffer.\r\n","3":"\"Auto-maps\" alpha release:\r\nMinor change to logic pertaining to cleanup of unnecessary tokens near end of buffer.\r\n","package":"txtfmt_v3.0alpha-4.tar.gz","4":"txtfmt_v3.0alpha-4.tar.gz","src_id":"24142","5":"24142","creation_date":"1459120571","6":"1459120571"},{"0":"2208","vim_version":"7.0","1":"7.0","script_version":"3.0alpha-3","2":"3.0alpha-3","version_comment":"\"Auto-maps\" alpha release:\r\nBugfix for issue affecting highlighting of regions near end of buffer.","3":"\"Auto-maps\" alpha release:\r\nBugfix for issue affecting highlighting of regions near end of buffer.","package":"txtfmt_v3.0alpha-3.tar.gz","4":"txtfmt_v3.0alpha-3.tar.gz","src_id":"24141","5":"24141","creation_date":"1459084135","6":"1459084135"},{"0":"2208","vim_version":"7.0","1":"7.0","script_version":"3.0alpha-2","2":"3.0alpha-2","version_comment":"Minor bugfixes and UI tweaks to alpha release of \"auto maps\" feature: e.g., `f-' and `c-' now mean \"clear format\" and \"clear color\", respectively.","3":"Minor bugfixes and UI tweaks to alpha release of \"auto maps\" feature: e.g., `f-' and `c-' now mean \"clear format\" and \"clear color\", respectively.","package":"txtfmt_v3.0alpha-2.tar.gz","4":"txtfmt_v3.0alpha-2.tar.gz","src_id":"24111","5":"24111","creation_date":"1458218003","6":"1458218003"},{"0":"2208","vim_version":"7.0","1":"7.0","script_version":"3.0 alpha","2":"3.0 alpha","version_comment":"Alpha release of \"auto maps\" feature: includes both visual and operator-pending maps for highlighting existing regions. UI not yet frozen. User feedback desired.","3":"Alpha release of \"auto maps\" feature: includes both visual and operator-pending maps for highlighting existing regions. UI not yet frozen. User feedback desired.","package":"txtfmt_v3.0alpha.tar.gz","4":"txtfmt_v3.0alpha.tar.gz","src_id":"23970","5":"23970","creation_date":"1454172335","6":"1454172335"},{"0":"2208","vim_version":"7.0","1":"7.0","script_version":"2.4","2":"2.4","version_comment":"Version 2.4 repackaged in Vimball format\r\n*** TOKENS NOW COMPLETELY CONCEALED (with Vim 7.3) ***\r\nSee original version 2.4 release notes for additional details","3":"Version 2.4 repackaged in Vimball format\r\n*** TOKENS NOW COMPLETELY CONCEALED (with Vim 7.3) ***\r\nSee original version 2.4 release notes for additional details","package":"txtfmt_v24.vba","4":"txtfmt_v24.vba","src_id":"13946","5":"13946","creation_date":"1285644136","6":"1285644136"},{"0":"2208","vim_version":"6.0","1":"6.0","script_version":"2.4","2":"2.4","version_comment":"*** TOKENS NOW COMPLETELY CONCEALED (with Vim 7.3) ***\r\n-Makes using the \"conceal\" feature the default for Vim versions >= 7.3.\r\nImportant Note: If you have legacy files for which you do not wish to use \"conceal\", read the following:\r\n\t:help txtfmt-conceal-history\r\n\t:help txtfmt-viewing-old-files-without-conceal\r\n-Provides more accurate definition of \"turquoise\" color in default color map: LightGreen changed to DarkCyan.\r\n-Fixed handling of bad modeline options.","3":"*** TOKENS NOW COMPLETELY CONCEALED (with Vim 7.3) ***\r\n-Makes using the \"conceal\" feature the default for Vim versions >= 7.3.\r\nImportant Note: If you have legacy files for which you do not wish to use \"conceal\", read the following:\r\n\t:help txtfmt-conceal-history\r\n\t:help txtfmt-viewing-old-files-without-conceal\r\n-Provides more accurate definition of \"turquoise\" color in default color map: LightGreen changed to DarkCyan.\r\n-Fixed handling of bad modeline options.","package":"txtfmt_v2.4.tar.gz","4":"txtfmt_v2.4.tar.gz","src_id":"13856","5":"13856","creation_date":"1284834850","6":"1284834850"},{"0":"2208","vim_version":"6.0","1":"6.0","script_version":"2.3","2":"2.3","version_comment":"Prevents E21 in several scenarios: e.g.,\r\n\t-Txtfmt used within a Vim help buffer (e.g., ft=help.txtfmt)\r\n\t-Txtfmt loaded when 'nomodifiable' is set globally.\r\n","3":"Prevents E21 in several scenarios: e.g.,\r\n\t-Txtfmt used within a Vim help buffer (e.g., ft=help.txtfmt)\r\n\t-Txtfmt loaded when 'nomodifiable' is set globally.\r\n","package":"txtfmt_v2.3.tar.gz","4":"txtfmt_v2.3.tar.gz","src_id":"13144","5":"13144","creation_date":"1275967732","6":"1275967732"},{"0":"2208","vim_version":"6.0","1":"6.0","script_version":"2.2","2":"2.2","version_comment":"-Loading Txtfmt no longer makes all windows the same size when 'equalalways' is set\r\n-Fixed several anomalies caused by Txtfmt load when 'winfixheight' is set:\r\n\t-\"test page\" displayed in 2 windows\r\n\t-chain of errors when initial window contains changes\r\n\t-Txtfmt buffer loaded in 2 windows\r\n-Added logic that attempts to make \"test page\" at least 20 lines high\r\n","3":"-Loading Txtfmt no longer makes all windows the same size when 'equalalways' is set\r\n-Fixed several anomalies caused by Txtfmt load when 'winfixheight' is set:\r\n\t-\"test page\" displayed in 2 windows\r\n\t-chain of errors when initial window contains changes\r\n\t-Txtfmt buffer loaded in 2 windows\r\n-Added logic that attempts to make \"test page\" at least 20 lines high\r\n","package":"txtfmt_v2.2.tar.gz","4":"txtfmt_v2.2.tar.gz","src_id":"12389","5":"12389","creation_date":"1266326235","6":"1266326235"},{"0":"2208","vim_version":"6.0","1":"6.0","script_version":"2.1","2":"2.1","version_comment":"Minor fix in Define_syntax to ensure that 'containedin' clause does not refer to nonexistent \"inner escape\" region when there are no active foreground colors.","3":"Minor fix in Define_syntax to ensure that 'containedin' clause does not refer to nonexistent \"inner escape\" region when there are no active foreground colors.","package":"txtfmt_v2.1.tar.gz","4":"txtfmt_v2.1.tar.gz","src_id":"11802","5":"11802","creation_date":"1259207445","6":"1259207445"},{"0":"2208","vim_version":"6.0","1":"6.0","script_version":"2.0","2":"2.0","version_comment":"!!!!! Formal Release of Version 2.0 (bg color and 'conceal' patch support) !!!!!\r\nIncorporated perl script used to generate large portion of Define_syntax into syntax\/txtfmt.vim, and provided Vim command line used to update the auto-generated script block.\r\n","3":"!!!!! Formal Release of Version 2.0 (bg color and 'conceal' patch support) !!!!!\r\nIncorporated perl script used to generate large portion of Define_syntax into syntax\/txtfmt.vim, and provided Vim command line used to update the auto-generated script block.\r\n","package":"txtfmt_v2.0.tar.gz","4":"txtfmt_v2.0.tar.gz","src_id":"11451","5":"11451","creation_date":"1254193387","6":"1254193387"},{"0":"2208","vim_version":"6.0","1":"6.0","script_version":"2.0b","2":"2.0b","version_comment":"!!!!! Version 2.0 beta release (background colors and 'conceal' patch) !!!!!\r\nCode cleanup (removed unused functions, streamlined color name lookup)\r\n","3":"!!!!! Version 2.0 beta release (background colors and 'conceal' patch) !!!!!\r\nCode cleanup (removed unused functions, streamlined color name lookup)\r\n","package":"txtfmt_v2.0b.tar.gz","4":"txtfmt_v2.0b.tar.gz","src_id":"11387","5":"11387","creation_date":"1253103770","6":"1253103770"},{"0":"2208","vim_version":"6.0","1":"6.0","script_version":"2.0a","2":"2.0a","version_comment":"!!!!! MAJOR RELEASE !!!!!\r\n-Added support for background colors!!!\r\n-Added support for Vince Negri's 'conceal' patch, which can make Txtfmt tokens consume zero screen width\r\n","3":"!!!!! MAJOR RELEASE !!!!!\r\n-Added support for background colors!!!\r\n-Added support for Vince Negri's 'conceal' patch, which can make Txtfmt tokens consume zero screen width\r\n","package":"txtfmt_v2.0a.tar.gz","4":"txtfmt_v2.0a.tar.gz","src_id":"11250","5":"11250","creation_date":"1251202930","6":"1251202930"},{"0":"2208","vim_version":"6.0","1":"6.0","script_version":"1.5","2":"1.5","version_comment":"-Removed (obsolete) multibyte syntax patch from distribution\r\n-Updated help to reflect fact that several issues affecting Txtfmt have been eliminated in Vim 7.2","3":"-Removed (obsolete) multibyte syntax patch from distribution\r\n-Updated help to reflect fact that several issues affecting Txtfmt have been eliminated in Vim 7.2","package":"txtfmt_v1.5.tar.gz","4":"txtfmt_v1.5.tar.gz","src_id":"10118","5":"10118","creation_date":"1236260007","6":"1236260007"},{"0":"2208","vim_version":"6.0","1":"6.0","script_version":"1.4","2":"1.4","version_comment":"-Fixed several of the operator-pending \"jump to token\" maps\r\n-Added more robust mechanism for hiding tokens, eliminating dependence upon \"Ignore\" group whenever possible\r\n-Added help section \"Color terminal pitfalls\" containing...\r\n    -Description of \"Ignore\" group issue and recommended workarounds\r\n    -Description of gnome-terminal issue and recommended workarounds\r\n-Fixed broken link in helpfile\r\n-Minor cosmetic fix on test page\r\n","3":"-Fixed several of the operator-pending \"jump to token\" maps\r\n-Added more robust mechanism for hiding tokens, eliminating dependence upon \"Ignore\" group whenever possible\r\n-Added help section \"Color terminal pitfalls\" containing...\r\n    -Description of \"Ignore\" group issue and recommended workarounds\r\n    -Description of gnome-terminal issue and recommended workarounds\r\n-Fixed broken link in helpfile\r\n-Minor cosmetic fix on test page\r\n","package":"txtfmt_v1.4.tar.gz","4":"txtfmt_v1.4.tar.gz","src_id":"10013","5":"10013","creation_date":"1235412039","6":"1235412039"},{"0":"2208","vim_version":"6.0","1":"6.0","script_version":"1.3","2":"1.3","version_comment":"Fixed \"bold\" attribute display in color terminals. Prior to this fix, the default Txtfmt colors were unaffected by the bold attribute. With this fix, the bold attribute will cause dark colors to appear brighter (lighter) in a color terminal.\r\n","3":"Fixed \"bold\" attribute display in color terminals. Prior to this fix, the default Txtfmt colors were unaffected by the bold attribute. With this fix, the bold attribute will cause dark colors to appear brighter (lighter) in a color terminal.\r\n","package":"txtfmt_v1.3.tar.gz","4":"txtfmt_v1.3.tar.gz","src_id":"9681","5":"9681","creation_date":"1229439822","6":"1229439822"},{"0":"2208","vim_version":"6.0","1":"6.0","script_version":"1.2","2":"1.2","version_comment":"Added missing help tags for a number of options.","3":"Added missing help tags for a number of options.","package":"txtfmt_v1.2.tar.gz","4":"txtfmt_v1.2.tar.gz","src_id":"9139","5":"9139","creation_date":"1218964264","6":"1218964264"},{"0":"2208","vim_version":"6.0","1":"6.0","script_version":"1.1","2":"1.1","version_comment":"NOW WORKS WITH MULTIBYTE ENCODINGS!!! (no patch required)\r\n-Added logic to determine whether the running Vim treats syntax match offsets as byte or character offsets. (This logic renders the multi-byte syntax patch obsolete.)\r\n-Help file additions: added instructions for using Txtfmt with TVO (:help txtfmt-nesting-tvo-example), and outlined a strategy for achieving \"colorscheme independence\" by defining colors according to default highlighting groups (:help txtfmt-colorschemes)\r\n","3":"NOW WORKS WITH MULTIBYTE ENCODINGS!!! (no patch required)\r\n-Added logic to determine whether the running Vim treats syntax match offsets as byte or character offsets. (This logic renders the multi-byte syntax patch obsolete.)\r\n-Help file additions: added instructions for using Txtfmt with TVO (:help txtfmt-nesting-tvo-example), and outlined a strategy for achieving \"colorscheme independence\" by defining colors according to default highlighting groups (:help txtfmt-colorschemes)\r\n","package":"txtfmt_v1.1.tar.gz","4":"txtfmt_v1.1.tar.gz","src_id":"8751","5":"8751","creation_date":"1212558861","6":"1212558861"},{"0":"2208","vim_version":"6.0","1":"6.0","script_version":"1.0e","2":"1.0e","version_comment":"-Fixed bug that prevented buf-local color definitions from being used.\r\n-Added to the help file a description of a possible strategy for making txtfmt\r\n color definitions dependent upon current colorscheme.\r\n-Fixed bug that sometimes prevented txtfmt option changes from taking effect\r\n when a txtfmt buffer was re-edited.\r\n-Fixed bug that prevented insert-token mappings from working in Replace mode.","3":"-Fixed bug that prevented buf-local color definitions from being used.\r\n-Added to the help file a description of a possible strategy for making txtfmt\r\n color definitions dependent upon current colorscheme.\r\n-Fixed bug that sometimes prevented txtfmt option changes from taking effect\r\n when a txtfmt buffer was re-edited.\r\n-Fixed bug that prevented insert-token mappings from working in Replace mode.","package":"txtfmt_v1.0e.tar.gz","4":"txtfmt_v1.0e.tar.gz","src_id":"8670","5":"8670","creation_date":"1210484327","6":"1210484327"},{"0":"2208","vim_version":"6.0","1":"6.0","script_version":"1.0d","2":"1.0d","version_comment":"Applied the <silent> attribute to prevent the jump-to-token\r\nmappings from echoing to the command line","3":"Applied the <silent> attribute to prevent the jump-to-token\r\nmappings from echoing to the command line","package":"txtfmt_v1.0d.tar.gz","4":"txtfmt_v1.0d.tar.gz","src_id":"8611","5":"8611","creation_date":"1209358261","6":"1209358261"},{"0":"2208","vim_version":"6.0","1":"6.0","script_version":"1.0c","2":"1.0c","version_comment":"-Added buffer-local mapping (\\ga) and command (:GetTokInfo) for obtaining\r\ninformation about a specific character\/token in a txtfmt buffer.\r\n(Functionality is analogous to that of Vim's ga normal mode command.)\r\n-Fixed documentation and reporting bug that caused a 0-based color index to be\r\ndisplayed instead of the 1-based index specified in the help file. (Affected\r\n:MakeTestPage, \\ga, :GetTokInfo and documentation)","3":"-Added buffer-local mapping (\\ga) and command (:GetTokInfo) for obtaining\r\ninformation about a specific character\/token in a txtfmt buffer.\r\n(Functionality is analogous to that of Vim's ga normal mode command.)\r\n-Fixed documentation and reporting bug that caused a 0-based color index to be\r\ndisplayed instead of the 1-based index specified in the help file. (Affected\r\n:MakeTestPage, \\ga, :GetTokInfo and documentation)","package":"txtfmt_v1.0c.tar.gz","4":"txtfmt_v1.0c.tar.gz","src_id":"8580","5":"8580","creation_date":"1208585015","6":"1208585015"},{"0":"2208","vim_version":"6.0","1":"6.0","script_version":"1.0b","2":"1.0b","version_comment":"Fixed bug in ftplugin that caused sample \"user-maps\" (defined for testing) to override any user-defined ones.","3":"Fixed bug in ftplugin that caused sample \"user-maps\" (defined for testing) to override any user-defined ones.","package":"txtfmt_v1.0b.tar.gz","4":"txtfmt_v1.0b.tar.gz","src_id":"8544","5":"8544","creation_date":"1207859571","6":"1207859571"},{"0":"2208","vim_version":"6.0","1":"6.0","script_version":"1.0a","2":"1.0a","version_comment":"Initial upload","3":"Initial upload","package":"txtfmt_v1.0a.tar.gz","4":"txtfmt_v1.0a.tar.gz","src_id":"8526","5":"8526","creation_date":"1207478956","6":"1207478956"}]},"2207":{"script_id":"2207","0":"2207","script_name":"Relativize","1":"Relativize","script_type":"utility","2":"utility","summary":"quickly make a full path name relative to an index.html or tags file","3":"quickly make a full path name relative to an index.html or tags file","description":"               Project with a tags file example:\r\n\r\n               Open a long full path name from some error log\r\n\r\n                vi \/some\/full\/path\/to\/project\/current_project\/lib\/module\/file.ext\r\n               ...\r\n\r\n               :Relativize tags<cr>\r\n\r\n               if you type :pwd you should get\r\n\r\n               \/some\/full\/path\/to\/project\/current_project\r\n\r\n               assuming a tags file has been created in the current_project\r\n               file in the past.\r\n\r\n               So hopefully this means tag jumps will work and relative\r\n               include paths can be accessed via gf.\r\n\r\n               This could also be useful for other landmark files on the\r\n               system (eg. index.html, tags, .project,build.xml,README...etc). \r\n               In the above example\r\n               using the actual file.ext as the argument will make the\r\n               working directory the module directory\r\n\r\n               The function will prioritise the deepest tags file.\r\n\r\n                I have this in my vimrc to give you some ideas\r\n                \r\n                nnoremap ,pp :split<cr>:enew<cr>:r! tail -n 1000 \/var\/log\/php_errorlog<cr>:set buftype=nofile<cr>Gf\/\r\n                nnoremap gft gf:Relativize tags<cr>\r\n                nnoremap gfi gf:Relativize index.php<cr>\r\n\r\n\r\n\r\n\r\n         Bugs:\r\n\r\n               - Will probably not work with MS windows paths in current form.\r\n               It will probably cause an infinite loop you will need to\r\n               Ctrl-C out of.\r\n   ","4":"               Project with a tags file example:\r\n\r\n               Open a long full path name from some error log\r\n\r\n                vi \/some\/full\/path\/to\/project\/current_project\/lib\/module\/file.ext\r\n               ...\r\n\r\n               :Relativize tags<cr>\r\n\r\n               if you type :pwd you should get\r\n\r\n               \/some\/full\/path\/to\/project\/current_project\r\n\r\n               assuming a tags file has been created in the current_project\r\n               file in the past.\r\n\r\n               So hopefully this means tag jumps will work and relative\r\n               include paths can be accessed via gf.\r\n\r\n               This could also be useful for other landmark files on the\r\n               system (eg. index.html, tags, .project,build.xml,README...etc). \r\n               In the above example\r\n               using the actual file.ext as the argument will make the\r\n               working directory the module directory\r\n\r\n               The function will prioritise the deepest tags file.\r\n\r\n                I have this in my vimrc to give you some ideas\r\n                \r\n                nnoremap ,pp :split<cr>:enew<cr>:r! tail -n 1000 \/var\/log\/php_errorlog<cr>:set buftype=nofile<cr>Gf\/\r\n                nnoremap gft gf:Relativize tags<cr>\r\n                nnoremap gfi gf:Relativize index.php<cr>\r\n\r\n\r\n\r\n\r\n         Bugs:\r\n\r\n               - Will probably not work with MS windows paths in current form.\r\n               It will probably cause an infinite loop you will need to\r\n               Ctrl-C out of.\r\n   ","install_details":"add the relativize.vim into the plugins directory","5":"add the relativize.vim into the plugins directory","first_name":"Michael","6":"Michael","last_name":"Brown","7":"Brown","releases":[{"0":"2207","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"relativize.vim","4":"relativize.vim","src_id":"8518","5":"8518","creation_date":"1207099903","6":"1207099903"}]},"2206":{"script_id":"2206","0":"2206","script_name":"runzip","1":"runzip","script_type":"utility","2":"utility","summary":"edit zip files recursively (zip files inside zip files)","3":"edit zip files recursively (zip files inside zip files)","description":"this plugin improves vim runtime zip plugin, making it able to recursively read and write zip files : it allows editing zipfiles inside zipfiles inside zipfiles (on an arbitrary number of levels).\r\n\r\nWarning: this plugin needs python interface. it can be used only if vim is compiled with +python feature. To check this, type :version, and look for +python.","4":"this plugin improves vim runtime zip plugin, making it able to recursively read and write zip files : it allows editing zipfiles inside zipfiles inside zipfiles (on an arbitrary number of levels).\r\n\r\nWarning: this plugin needs python interface. it can be used only if vim is compiled with +python feature. To check this, type :version, and look for +python.","install_details":"unzip zip.zip in ~\/.vim directorys.","5":"unzip zip.zip in ~\/.vim directorys.","first_name":"arno.","6":"arno.","last_name":" ","7":" ","releases":[{"0":"2206","vim_version":"6.0","1":"6.0","script_version":"1.1","2":"1.1","version_comment":"fixes fail to write zip files when compress type is not ZIP_STORED ZIP_DEFLATED. patch by tocer","3":"fixes fail to write zip files when compress type is not ZIP_STORED ZIP_DEFLATED. patch by tocer","package":"zip.zip","4":"zip.zip","src_id":"11942","5":"11942","creation_date":"1261558363","6":"1261558363"},{"0":"2206","vim_version":"7.0","1":"7.0","script_version":"1","2":"1","version_comment":"Initial upload","3":"Initial upload","package":"zip.zip","4":"zip.zip","src_id":"8508","5":"8508","creation_date":"1206875834","6":"1206875834"}]},"2205":{"script_id":"2205","0":"2205","script_name":"CoremoSearch","1":"CoremoSearch","script_type":"utility","2":"utility","summary":"A simple simultaneous search script.","3":"A simple simultaneous search script.","description":"  This script provides simultaneous search functionality.\r\n                                                                     \r\n  You can add a string that you want to search and remove a string.\r\n\r\n  (from 0.2) Color highlighting is available setting :set[l] nohlsearch.\r\n                                                                     \r\nUsage:\r\n  A. Adding a word (like asterisk(*) keystroke)\r\n      1. Place the cursor on the word that you want to search.\r\n      2. Press <C-@> or :CoremoSearchAdd\r\n                                                                     \r\n  B. Adding a selected string\r\n      1. In visual mode, select the string that you want to search.\r\n      2. Press <C-@> or :CoremoSearchAddV\r\n                                                                     \r\n  A'. Removing a word\r\n      1. Place the cursor on the word.\r\n      2. Press <Learder><C-@> or :CoremoSearchRemove\r\n          (in most cases, <Leader> equals to backslash(\\) keystroke)\r\n                                                                     \r\n  B'. Removing a selected string\r\n      1. In visual mode, select the string.\r\n      2. Press <Learder><C-@> or :CoremoSearchRemoveV\r\n          (in most cases, <Leader> equals to backslash(\\) keystroke)\r\n","4":"  This script provides simultaneous search functionality.\r\n                                                                     \r\n  You can add a string that you want to search and remove a string.\r\n\r\n  (from 0.2) Color highlighting is available setting :set[l] nohlsearch.\r\n                                                                     \r\nUsage:\r\n  A. Adding a word (like asterisk(*) keystroke)\r\n      1. Place the cursor on the word that you want to search.\r\n      2. Press <C-@> or :CoremoSearchAdd\r\n                                                                     \r\n  B. Adding a selected string\r\n      1. In visual mode, select the string that you want to search.\r\n      2. Press <C-@> or :CoremoSearchAddV\r\n                                                                     \r\n  A'. Removing a word\r\n      1. Place the cursor on the word.\r\n      2. Press <Learder><C-@> or :CoremoSearchRemove\r\n          (in most cases, <Leader> equals to backslash(\\) keystroke)\r\n                                                                     \r\n  B'. Removing a selected string\r\n      1. In visual mode, select the string.\r\n      2. Press <Learder><C-@> or :CoremoSearchRemoveV\r\n          (in most cases, <Leader> equals to backslash(\\) keystroke)\r\n","install_details":"Put this plugin in your plugin directory(e.g. $VIMRUNTIME\/plugin).\r\nThen restart Vim or :source it.","5":"Put this plugin in your plugin directory(e.g. $VIMRUNTIME\/plugin).\r\nThen restart Vim or :source it.","first_name":"Shuhei","6":"Shuhei","last_name":"Kubota","7":"Kubota","releases":[{"0":"2205","vim_version":"7.0","1":"7.0","script_version":"0.5","2":"0.5","version_comment":"add CoremoSearchList to filter out items (works only on recent Vim)\r\n","3":"add CoremoSearchList to filter out items (works only on recent Vim)\r\n","package":"coremo_search.vim","4":"coremo_search.vim","src_id":"26517","5":"26517","creation_date":"1559742096","6":"1559742096"},{"0":"2205","vim_version":"7.0","1":"7.0","script_version":"0.4","2":"0.4","version_comment":"* now it works only in visual-mode. (not works in select-mode)","3":"* now it works only in visual-mode. (not works in select-mode)","package":"coremo_search.vim","4":"coremo_search.vim","src_id":"17188","5":"17188","creation_date":"1326367087","6":"1326367087"},{"0":"2205","vim_version":"7.0","1":"7.0","script_version":"0.3","2":"0.3","version_comment":"* added option hooking of \/ (standard searching keystroke)\r\n* re-hightlights when you changed between windows","3":"* added option hooking of \/ (standard searching keystroke)\r\n* re-hightlights when you changed between windows","package":"coremo_search.vim","4":"coremo_search.vim","src_id":"17068","5":"17068","creation_date":"1323947239","6":"1323947239"},{"0":"2205","vim_version":"7.0","1":"7.0","script_version":"0.2","2":"0.2","version_comment":"supports coloring search words!","3":"supports coloring search words!","package":"coremo_search.vim","4":"coremo_search.vim","src_id":"8512","5":"8512","creation_date":"1206939781","6":"1206939781"},{"0":"2205","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"coremo_search.vim","4":"coremo_search.vim","src_id":"8505","5":"8505","creation_date":"1206752439","6":"1206752439"}]},"2204":{"script_id":"2204","0":"2204","script_name":"TwitVim","1":"TwitVim","script_type":"utility","2":"utility","summary":"Twitter client for Vim","3":"Twitter client for Vim","description":"Introduction\r\n\r\nTwitVim is a Vim plugin that allows you to post to Twitter and view Twitter timelines. It is an enhancement of vimscript #2124 by Travis Jeffery. Credit goes to Travis for the original script concept and implementation.\r\n\r\nTwitVim supports most of the features of a typical Twitter client, including: \r\n\r\n- Friends, User, Direct Message, Mentions, and Favorites timelines \r\n- Twitter Search \r\n- Replying and retweeting\r\n- Hashtags (jump to search timeline) \r\n- In reply to (See which tweet an @-reply is for.) \r\n- Opening links in a browser \r\n- User profile display \r\n- Twitter List viewing and managing \r\n- Trending topics\r\n- Timeline filtering\r\n\r\n*****\r\n\r\nUsage\r\n\r\nPlugin commands:\r\n\r\n- :PosttoTwitter - This command will prompt you for a message to send to Twitter. \r\n- :CPosttoTwitter - This command posts the current line in the current buffer to Twitter. \r\n- :BPosttoTwitter - This command posts the current buffer to Twitter. \r\n- :FriendsTwitter - View friends timeline. \r\n- :UserTwitter - View your timeline. \r\n- :MentionsTwitter - View @-mentions. \r\n- :PublicTwitter - View public timeline. \r\n- :DMTwitter - View direct messages. \r\n- :SearchTwitter - Use Twitter Search. \r\n\r\nGlobal mappings:\r\n\r\n- Alt-T - In Visual select mode, the Alt-T key posts the selected text to Twitter. Use this mapping if you compose your tweets in a separate scratch buffer.\r\n- Ctrl-T - Use this instead if the menu bar is enabled or if Alt-T is not available on your platform.\r\n\r\nTimeline buffer mappings:\r\n\r\n- Alt-R or <Leader>r - Starts a @-reply. (in timeline buffer) \r\n- Alt-D or <Leader>d - Starts a direct message. (in timeline buffer) \r\n\r\nMany more commands and mappings are available. See TwitVim's help documentation for full details. \r\n\r\n*****\r\n\r\nLicense\r\n\r\nTwitVim is distributed under the same terms as Vim itself. See :help license.\r\n\r\n*****\r\n\r\nContact\r\n\r\n- @mortonfox (https:\/\/twitter.com\/mortonfox) - The maintainer\r\n- @twitvim (https:\/\/twitter.com\/twitvim) - TwitVim announcements\r\n","4":"Introduction\r\n\r\nTwitVim is a Vim plugin that allows you to post to Twitter and view Twitter timelines. It is an enhancement of vimscript #2124 by Travis Jeffery. Credit goes to Travis for the original script concept and implementation.\r\n\r\nTwitVim supports most of the features of a typical Twitter client, including: \r\n\r\n- Friends, User, Direct Message, Mentions, and Favorites timelines \r\n- Twitter Search \r\n- Replying and retweeting\r\n- Hashtags (jump to search timeline) \r\n- In reply to (See which tweet an @-reply is for.) \r\n- Opening links in a browser \r\n- User profile display \r\n- Twitter List viewing and managing \r\n- Trending topics\r\n- Timeline filtering\r\n\r\n*****\r\n\r\nUsage\r\n\r\nPlugin commands:\r\n\r\n- :PosttoTwitter - This command will prompt you for a message to send to Twitter. \r\n- :CPosttoTwitter - This command posts the current line in the current buffer to Twitter. \r\n- :BPosttoTwitter - This command posts the current buffer to Twitter. \r\n- :FriendsTwitter - View friends timeline. \r\n- :UserTwitter - View your timeline. \r\n- :MentionsTwitter - View @-mentions. \r\n- :PublicTwitter - View public timeline. \r\n- :DMTwitter - View direct messages. \r\n- :SearchTwitter - Use Twitter Search. \r\n\r\nGlobal mappings:\r\n\r\n- Alt-T - In Visual select mode, the Alt-T key posts the selected text to Twitter. Use this mapping if you compose your tweets in a separate scratch buffer.\r\n- Ctrl-T - Use this instead if the menu bar is enabled or if Alt-T is not available on your platform.\r\n\r\nTimeline buffer mappings:\r\n\r\n- Alt-R or <Leader>r - Starts a @-reply. (in timeline buffer) \r\n- Alt-D or <Leader>d - Starts a direct message. (in timeline buffer) \r\n\r\nMany more commands and mappings are available. See TwitVim's help documentation for full details. \r\n\r\n*****\r\n\r\nLicense\r\n\r\nTwitVim is distributed under the same terms as Vim itself. See :help license.\r\n\r\n*****\r\n\r\nContact\r\n\r\n- @mortonfox (https:\/\/twitter.com\/mortonfox) - The maintainer\r\n- @twitvim (https:\/\/twitter.com\/twitvim) - TwitVim announcements\r\n","install_details":"Prerequisites\r\n\r\nTwitVim uses cURL (http:\/\/curl.haxx.se\/) to communicate with Twitter. Alternatively, you can configure TwitVim to use Vim's Perl, Python, Ruby, or Tcl interfaces for faster network I\/O. \r\n\r\nTwitter OAuth requires either the OpenSSL (http:\/\/www.openssl.org\/) software or a Vim binary compiled with Perl, Python, Ruby, or Tcl.\r\n\r\nSome platforms already have cURL and OpenSSL preinstalled or have installation packages for those, so that is the easier way to satisfy the prerequisites.\r\n\r\n*****\r\n\r\nInstallation\r\n\r\nUse one of the methods below, depending on which plugin manager (or not)\r\nyou have. After installation, see :help TwitVim-install for further\r\ninstructions.\r\n\r\n* Pathogen\r\n\r\nUse the following commands:\r\n\r\n    cd ~\/.vim\/bundle\r\n    git clone https:\/\/github.com\/twitvim\/twitvim.git\r\n\r\n* Vundle\r\n\r\nAdd the following to your vimrc:\r\n\r\n    Plugin 'https:\/\/github.com\/twitvim\/twitvim.git'\r\n\r\nInstall with :PluginInstall\r\n\r\n* Vimball file\r\n\r\nOpen the vmb file and then source it.\r\n\r\n    vim twitvim-0.9.1.vmb\r\n    :so %\r\n","5":"Prerequisites\r\n\r\nTwitVim uses cURL (http:\/\/curl.haxx.se\/) to communicate with Twitter. Alternatively, you can configure TwitVim to use Vim's Perl, Python, Ruby, or Tcl interfaces for faster network I\/O. \r\n\r\nTwitter OAuth requires either the OpenSSL (http:\/\/www.openssl.org\/) software or a Vim binary compiled with Perl, Python, Ruby, or Tcl.\r\n\r\nSome platforms already have cURL and OpenSSL preinstalled or have installation packages for those, so that is the easier way to satisfy the prerequisites.\r\n\r\n*****\r\n\r\nInstallation\r\n\r\nUse one of the methods below, depending on which plugin manager (or not)\r\nyou have. After installation, see :help TwitVim-install for further\r\ninstructions.\r\n\r\n* Pathogen\r\n\r\nUse the following commands:\r\n\r\n    cd ~\/.vim\/bundle\r\n    git clone https:\/\/github.com\/twitvim\/twitvim.git\r\n\r\n* Vundle\r\n\r\nAdd the following to your vimrc:\r\n\r\n    Plugin 'https:\/\/github.com\/twitvim\/twitvim.git'\r\n\r\nInstall with :PluginInstall\r\n\r\n* Vimball file\r\n\r\nOpen the vmb file and then source it.\r\n\r\n    vim twitvim-0.9.1.vmb\r\n    :so %\r\n","first_name":"Po Shan","6":"Po Shan","last_name":"Cheah","7":"Cheah","releases":[{"0":"2204","vim_version":"7.4","1":"7.4","script_version":"0.9.1","2":"0.9.1","version_comment":"Support higher char limit for DMs.\r\n","3":"Support higher char limit for DMs.\r\n","package":"twitvim-0.9.1.vmb","4":"twitvim-0.9.1.vmb","src_id":"23560","5":"23560","creation_date":"1440798673","6":"1440798673"},{"0":"2204","vim_version":"7.4","1":"7.4","script_version":"0.9.0","2":"0.9.0","version_comment":"* Removed identi.ca support and legacy code.\r\n* Removed support for old token file formats.\r\n* Removed old Twitter search code.\r\n* Removed some obscure URL shortening services.\r\n* Updated to bit.ly v3 API.\r\n* Removed old goo.gl URL shortening code.\r\n* Removed services menu because we only have Twitter now.\r\n* Removed public timeline command.\r\n* Moved most of the plugin code to an autoload file.\r\n* Search header fix in UTF-8 encoding. (@mattn_jp)\r\n* Don't use curl -p for HTTP. (@mattn_jp)\r\n* Handle surrogate pairs. (@mattn_jp)\r\n","3":"* Removed identi.ca support and legacy code.\r\n* Removed support for old token file formats.\r\n* Removed old Twitter search code.\r\n* Removed some obscure URL shortening services.\r\n* Updated to bit.ly v3 API.\r\n* Removed old goo.gl URL shortening code.\r\n* Removed services menu because we only have Twitter now.\r\n* Removed public timeline command.\r\n* Moved most of the plugin code to an autoload file.\r\n* Search header fix in UTF-8 encoding. (@mattn_jp)\r\n* Don't use curl -p for HTTP. (@mattn_jp)\r\n* Handle surrogate pairs. (@mattn_jp)\r\n","package":"twitvim-0.9.0.vmb","4":"twitvim-0.9.0.vmb","src_id":"23161","5":"23161","creation_date":"1428698558","6":"1428698558"},{"0":"2204","vim_version":"7.3","1":"7.3","script_version":"0.8.2","2":"0.8.2","version_comment":"Added support for stock symbols.\r\nTwitter URLs are now https-only.\r\nCheck for zero-length messages earlier so that the user can cancel a Twitter post without logging in.\r\n","3":"Added support for stock symbols.\r\nTwitter URLs are now https-only.\r\nCheck for zero-length messages earlier so that the user can cancel a Twitter post without logging in.\r\n","package":"twitvim-0.8.2.vmb","4":"twitvim-0.8.2.vmb","src_id":"21701","5":"21701","creation_date":"1396324843","6":"1396324843"},{"0":"2204","vim_version":"7.3","1":"7.3","script_version":"0.8.1","2":"0.8.1","version_comment":"* Fix for suspended users in followers list.\r\n* Rewrote URL regex for new regex engine in Vim 7.4.\r\n","3":"* Fix for suspended users in followers list.\r\n* Rewrote URL regex for new regex engine in Vim 7.4.\r\n","package":"twitvim-0.8.1.vmb","4":"twitvim-0.8.1.vmb","src_id":"20641","5":"20641","creation_date":"1376458086","6":"1376458086"},{"0":"2204","vim_version":"7.0","1":"7.0","script_version":"0.8.0","2":"0.8.0","version_comment":"* Support for Twitter API 1.1.\r\n* Support for identi.ca OAuth and switching between Twitter OAuth and identi.ca OAuth logins.\r\n* Added twitvim_force_ssl.\r\n* Added :DeleteLoginTwitter.\r\n* Add in-reply-to status to old-style retweets. (@mattn_jp)\r\n* Fix for old-style retweets with '&' characters.\r\n* Some fixes for https proxy support.\r\n","3":"* Support for Twitter API 1.1.\r\n* Support for identi.ca OAuth and switching between Twitter OAuth and identi.ca OAuth logins.\r\n* Added twitvim_force_ssl.\r\n* Added :DeleteLoginTwitter.\r\n* Add in-reply-to status to old-style retweets. (@mattn_jp)\r\n* Fix for old-style retweets with '&' characters.\r\n* Some fixes for https proxy support.\r\n","package":"twitvim-0.8.0.vmb","4":"twitvim-0.8.0.vmb","src_id":"19299","5":"19299","creation_date":"1357162639","6":"1357162639"},{"0":"2204","vim_version":"7.0","1":"7.0","script_version":"0.7.4","2":"0.7.4","version_comment":"* Allow users to customize timestamp format in timeline displays.\r\n* Take Twitter's URL-wrapping into account when counting characters in tweets. You do not have to shorten URLs manually any more. Just post to Twitter with the original URLs and TwitVim will ensure that the tweet fits the 140-character limit after Twitter's t.co link-wrapping.\r\n* Added network timeout option.\r\n* Added Python 3 networking and OAuth code.\r\n* Switched from page-style pagination to max_id-style pagination because page-style pagination has been deprecated. As a result, all timeline commands will cease to accept count parameters and :PreviousTwitter will return to the top page regardless of current page number.\r\n* Switched to new API for :FollowingTwitter and :FollowersTwitter because the old API was deprecated.\r\n* :FollowTwitter now stops you from following a user that you are already following. This is to avoid triggering a Twitter bug where the following flag reverts to 'follow request sent' if the subject's timeline is protected.\r\n","3":"* Allow users to customize timestamp format in timeline displays.\r\n* Take Twitter's URL-wrapping into account when counting characters in tweets. You do not have to shorten URLs manually any more. Just post to Twitter with the original URLs and TwitVim will ensure that the tweet fits the 140-character limit after Twitter's t.co link-wrapping.\r\n* Added network timeout option.\r\n* Added Python 3 networking and OAuth code.\r\n* Switched from page-style pagination to max_id-style pagination because page-style pagination has been deprecated. As a result, all timeline commands will cease to accept count parameters and :PreviousTwitter will return to the top page regardless of current page number.\r\n* Switched to new API for :FollowingTwitter and :FollowersTwitter because the old API was deprecated.\r\n* :FollowTwitter now stops you from following a user that you are already following. This is to avoid triggering a Twitter bug where the following flag reverts to 'follow request sent' if the subject's timeline is protected.\r\n","package":"twitvim-0.7.4.vmb","4":"twitvim-0.7.4.vmb","src_id":"17895","5":"17895","creation_date":"1336404335","6":"1336404335"},{"0":"2204","vim_version":"7.0","1":"7.0","script_version":"0.7.3","2":"0.7.3","version_comment":"* Switched to JSON API for Twitter Search so that TwitVim can support t.co URL expansion and in-reply-to in search results.\r\n* Made the URL-matching pattern more accurate.\r\n","3":"* Switched to JSON API for Twitter Search so that TwitVim can support t.co URL expansion and in-reply-to in search results.\r\n* Made the URL-matching pattern more accurate.\r\n","package":"twitvim-0.7.3.vmb","4":"twitvim-0.7.3.vmb","src_id":"17317","5":"17317","creation_date":"1327520467","6":"1327520467"},{"0":"2204","vim_version":"7.0","1":"7.0","script_version":"0.7.2","2":"0.7.2","version_comment":"* Allow users to use their own consumer key and secret. See twitvim_consumer_key and twitvim_consumer_secret.\r\n* Added t.co URL expansion for media URLs too.\r\n* Added confirmation prompt before new-style retweet.\r\n* Added a fix for :TrendTwitter and :SetTrendLocationTwitter because Twitter removed support for XML format in those APIs.\r\n* Read token file before first invocation of :SwitchLoginTwitter to ensure it has the list of logins ready. (@mattn_jp)\r\n","3":"* Allow users to use their own consumer key and secret. See twitvim_consumer_key and twitvim_consumer_secret.\r\n* Added t.co URL expansion for media URLs too.\r\n* Added confirmation prompt before new-style retweet.\r\n* Added a fix for :TrendTwitter and :SetTrendLocationTwitter because Twitter removed support for XML format in those APIs.\r\n* Read token file before first invocation of :SwitchLoginTwitter to ensure it has the list of logins ready. (@mattn_jp)\r\n","package":"twitvim-0.7.2.vmb","4":"twitvim-0.7.2.vmb","src_id":"16883","5":"16883","creation_date":"1321471933","6":"1321471933"},{"0":"2204","vim_version":"7.0","1":"7.0","script_version":"0.7.1","2":"0.7.1","version_comment":"* Added trending topics. :TrendTwitter and :SetTrendLocationTwitter\r\n* Some fixes for browser-launching issues.\r\n* Fix for quoting issue when doing goo.gl URL shortening with cURL network interface under Windows.\r\n* Support for HTML hex entities.\r\n* Show 'follow request sent' in user profile display if that is the case.\r\n","3":"* Added trending topics. :TrendTwitter and :SetTrendLocationTwitter\r\n* Some fixes for browser-launching issues.\r\n* Fix for quoting issue when doing goo.gl URL shortening with cURL network interface under Windows.\r\n* Support for HTML hex entities.\r\n* Show 'follow request sent' in user profile display if that is the case.\r\n","package":"twitvim-0.7.1.vmb","4":"twitvim-0.7.1.vmb","src_id":"16560","5":"16560","creation_date":"1316630211","6":"1316630211"},{"0":"2204","vim_version":"7.0","1":"7.0","script_version":"0.7.0","2":"0.7.0","version_comment":"* Faster XML parser.\r\n* Replaced deprecated Twitter API calls with updated versions.\r\n* OAuth multi-login feature. Added :SwitchLoginTwitter command.\r\n","3":"* Faster XML parser.\r\n* Replaced deprecated Twitter API calls with updated versions.\r\n* OAuth multi-login feature. Added :SwitchLoginTwitter command.\r\n","package":"twitvim-0.7.0.vba","4":"twitvim-0.7.0.vba","src_id":"16044","5":"16044","creation_date":"1309979495","6":"1309979495"},{"0":"2204","vim_version":"7.0","1":"7.0","script_version":"0.6.3","2":"0.6.3","version_comment":"Auto-expand t.co URLs in timeline displays.\r\nAdded timeline filtering. \r\n","3":"Auto-expand t.co URLs in timeline displays.\r\nAdded timeline filtering. \r\n","package":"twitvim-0.6.3.vba","4":"twitvim-0.6.3.vba","src_id":"15633","5":"15633","creation_date":"1305316439","6":"1305316439"},{"0":"2204","vim_version":"7.0","1":"7.0","script_version":"0.6.2","2":"0.6.2","version_comment":"* Added more user relationship info to :ProfileTwitter.\r\n* Added :EnableRetweetsTwitter and :DisableRetweetsTwitter.\r\n* Switch to new (documented) goo.gl API.\r\n* Added :ListInfoTwitter. \r\n","3":"* Added more user relationship info to :ProfileTwitter.\r\n* Added :EnableRetweetsTwitter and :DisableRetweetsTwitter.\r\n* Switch to new (documented) goo.gl API.\r\n* Added :ListInfoTwitter. \r\n","package":"twitvim-0.6.2.vba","4":"twitvim-0.6.2.vba","src_id":"15353","5":"15353","creation_date":"1301693652","6":"1301693652"},{"0":"2204","vim_version":"7.0","1":"7.0","script_version":"0.6.1","2":"0.6.1","version_comment":"* Fix for buffer stack bug if user closes a window manually.\r\n* Use https OAuth endpoints if user has set up https API root.\r\n* Match a URL even if prefix is in mixed case.\r\n","3":"* Fix for buffer stack bug if user closes a window manually.\r\n* Use https OAuth endpoints if user has set up https API root.\r\n* Match a URL even if prefix is in mixed case.\r\n","package":"twitvim-0.6.1.vba","4":"twitvim-0.6.1.vba","src_id":"14690","5":"14690","creation_date":"1294294127","6":"1294294127"},{"0":"2204","vim_version":"7.0","1":"7.0","script_version":"0.6.0","2":"0.6.0","version_comment":"* Added :FollowingTwitter, :FollowersTwitter.\r\n* Added :MembersOfListTwitter, :SubsOfListTwitter, :OwnedListsTwitter, :MemberListsTwitter, :SubsListsTwitter, :FollowListTwitter, :UnfollowListTwitter.\r\n* Added support for goo.gl :Googl and Rga.la. :Rgala\r\n* Extended TwitVim-Leader-g to support Name: lines in user profile and following\/followers lists.\r\n* Added history stack for info buffer.\r\n* Added :BackInfoTwitter, :ForwardInfoTwitter, :RefreshInfoTwitter, :NextInfoTwitter, :PreviousInfoTwitter for the info buffer. Also added support for TwitVim-C-PageDown and TwitVim-C-PageUp in info buffer.\r\n* Added twitvim filetype for user customization via autocommands.\r\n* Changed display of retweets to show the full version instead of the truncated version when the retweeted status is near the character limit.\r\n* :ProfileTwitter with no argument now shows info on logged-in user.\r\n* Made TwitVim-Leader-@ work on new-style retweets by showing the retweeted status as the parent.\r\n","3":"* Added :FollowingTwitter, :FollowersTwitter.\r\n* Added :MembersOfListTwitter, :SubsOfListTwitter, :OwnedListsTwitter, :MemberListsTwitter, :SubsListsTwitter, :FollowListTwitter, :UnfollowListTwitter.\r\n* Added support for goo.gl :Googl and Rga.la. :Rgala\r\n* Extended TwitVim-Leader-g to support Name: lines in user profile and following\/followers lists.\r\n* Added history stack for info buffer.\r\n* Added :BackInfoTwitter, :ForwardInfoTwitter, :RefreshInfoTwitter, :NextInfoTwitter, :PreviousInfoTwitter for the info buffer. Also added support for TwitVim-C-PageDown and TwitVim-C-PageUp in info buffer.\r\n* Added twitvim filetype for user customization via autocommands.\r\n* Changed display of retweets to show the full version instead of the truncated version when the retweeted status is near the character limit.\r\n* :ProfileTwitter with no argument now shows info on logged-in user.\r\n* Made TwitVim-Leader-@ work on new-style retweets by showing the retweeted status as the parent.\r\n","package":"twitvim-0.6.0.vba","4":"twitvim-0.6.0.vba","src_id":"14136","5":"14136","creation_date":"1288193459","6":"1288193459"},{"0":"2204","vim_version":"7.0","1":"7.0","script_version":"0.5.6","2":"0.5.6","version_comment":"* Exception handling for Python net interface.\r\n* Added converter functions for non-UTF8 encoding by @mattn_jp.\r\n* Convert entities in profile name, bio, and location. (Suggested by code933k)\r\n* Fix for posting foreign chars when encoding is not UTF8 and net method is not Curl.\r\n* Support twitvim_count in :DMTwitter and :DMSentTwitter.\r\n* Added :FavTwitter and mappings to favorite and unfavorite tweets.\r\n","3":"* Exception handling for Python net interface.\r\n* Added converter functions for non-UTF8 encoding by @mattn_jp.\r\n* Convert entities in profile name, bio, and location. (Suggested by code933k)\r\n* Fix for posting foreign chars when encoding is not UTF8 and net method is not Curl.\r\n* Support twitvim_count in :DMTwitter and :DMSentTwitter.\r\n* Added :FavTwitter and mappings to favorite and unfavorite tweets.\r\n","package":"twitvim-0.5.6.vba","4":"twitvim-0.5.6.vba","src_id":"13924","5":"13924","creation_date":"1285524090","6":"1285524090"},{"0":"2204","vim_version":"7.0","1":"7.0","script_version":"0.5.5","2":"0.5.5","version_comment":"Added a way to compute HMAC-SHA1 digests using openssl command line utility.\r\n","3":"Added a way to compute HMAC-SHA1 digests using openssl command line utility.\r\n","package":"twitvim-0.5.5.vba","4":"twitvim-0.5.5.vba","src_id":"13653","5":"13653","creation_date":"1282575946","6":"1282575946"},{"0":"2204","vim_version":"7.0","1":"7.0","script_version":"0.5.4","2":"0.5.4","version_comment":"* Added Ruby and Tcl versions of HMAC-SHA1 digest code.\r\n* Improved error messages for cURL users.\r\n* Code fix to keep 'nomodifiable' setting from leaking out into other buffers.\r\n* Support Twitter SSL via Tcl interface.\r\n","3":"* Added Ruby and Tcl versions of HMAC-SHA1 digest code.\r\n* Improved error messages for cURL users.\r\n* Code fix to keep 'nomodifiable' setting from leaking out into other buffers.\r\n* Support Twitter SSL via Tcl interface.\r\n","package":"twitvim-0.5.4.vba","4":"twitvim-0.5.4.vba","src_id":"13563","5":"13563","creation_date":"1281769902","6":"1281769902"},{"0":"2204","vim_version":"7.0","1":"7.0","script_version":"0.5.3","2":"0.5.3","version_comment":"* Improved error messages for most commands if using Perl, Python, Ruby, or Tcl interfaces.\r\n* Added :FollowTwitter, :UnfollowTwitter, :BlockTwitter, :UnblockTwitter, :ReportSpamTwitter, :AddToListTwitter, :RemoveFromListTwitter.\r\n\r\n","3":"* Improved error messages for most commands if using Perl, Python, Ruby, or Tcl interfaces.\r\n* Added :FollowTwitter, :UnfollowTwitter, :BlockTwitter, :UnblockTwitter, :ReportSpamTwitter, :AddToListTwitter, :RemoveFromListTwitter.\r\n\r\n","package":"twitvim-0.5.3.vba","4":"twitvim-0.5.3.vba","src_id":"13280","5":"13280","creation_date":"1278128856","6":"1278128856"},{"0":"2204","vim_version":"7.0","1":"7.0","script_version":"0.5.2","2":"0.5.2","version_comment":"More fixes for Twitter OAuth.","3":"More fixes for Twitter OAuth.","package":"twitvim-0.5.2.vba","4":"twitvim-0.5.2.vba","src_id":"13232","5":"13232","creation_date":"1277183548","6":"1277183548"},{"0":"2204","vim_version":"7.0","1":"7.0","script_version":"0.5.1","2":"0.5.1","version_comment":"* Shorten auth URL with is.gd\/Bitly if we need to ask the user to visit it manually.\r\n* Fixed the :PublicTwitter invalid request error.\r\n* Include new-style retweets in user timeline.\r\n","3":"* Shorten auth URL with is.gd\/Bitly if we need to ask the user to visit it manually.\r\n* Fixed the :PublicTwitter invalid request error.\r\n* Include new-style retweets in user timeline.\r\n","package":"twitvim-0.5.1.vba","4":"twitvim-0.5.1.vba","src_id":"13218","5":"13218","creation_date":"1276963257","6":"1276963257"},{"0":"2204","vim_version":"7.0","1":"7.0","script_version":"0.5.0","2":"0.5.0","version_comment":"Switched to OAuth for user authentication on Twitter.\r\nAdded more information to :ProfileTwitter output.\r\n","3":"Switched to OAuth for user authentication on Twitter.\r\nAdded more information to :ProfileTwitter output.\r\n","package":"twitvim-0.5.0.vba","4":"twitvim-0.5.0.vba","src_id":"13204","5":"13204","creation_date":"1276754431","6":"1276754431"},{"0":"2204","vim_version":"7.0","1":"7.0","script_version":"0.4.7","2":"0.4.7","version_comment":"* Added :MentionsTwitter as an alias for :RepliesTwitter.\r\n* Support twitvim_count in :MentionsTwitter.\r\n* Fixed twitvim_count bug in :ListTwitter.\r\n* Fixed Ruby interface problem with Vim patch 7.2.374.\r\n* Fixed :BackTwitter behavior when timeline window is hidden by user.\r\n* Handle SocketError exception in Ruby code.\r\n","3":"* Added :MentionsTwitter as an alias for :RepliesTwitter.\r\n* Support twitvim_count in :MentionsTwitter.\r\n* Fixed twitvim_count bug in :ListTwitter.\r\n* Fixed Ruby interface problem with Vim patch 7.2.374.\r\n* Fixed :BackTwitter behavior when timeline window is hidden by user.\r\n* Handle SocketError exception in Ruby code.\r\n","package":"twitvim-0.4.7.vba","4":"twitvim-0.4.7.vba","src_id":"12626","5":"12626","creation_date":"1268507250","6":"1268507250"},{"0":"2204","vim_version":"7.0","1":"7.0","script_version":"0.4.6","2":"0.4.6","version_comment":"Added twitvim_show_header config to allow user to hide the timeline header.\r\nMinor fix to normal commands to avoid inadvertently triggering user mappings.\r\n","3":"Added twitvim_show_header config to allow user to hide the timeline header.\r\nMinor fix to normal commands to avoid inadvertently triggering user mappings.\r\n","package":"twitvim-0.4.6.vba","4":"twitvim-0.4.6.vba","src_id":"12383","5":"12383","creation_date":"1266115231","6":"1266115231"},{"0":"2204","vim_version":"7.0","1":"7.0","script_version":"0.4.5","2":"0.4.5","version_comment":"Prompt user for Twitter login if not configured in vimrc. Reintroduced old-style retweets via user option.","3":"Prompt user for Twitter login if not configured in vimrc. Reintroduced old-style retweets via user option.","package":"twitvim-0.4.5.vba","4":"twitvim-0.4.5.vba","src_id":"11990","5":"11990","creation_date":"1262302926","6":"1262302926"},{"0":"2204","vim_version":"7.0","1":"7.0","script_version":"0.4.4","2":"0.4.4","version_comment":"Added some support for Retweet API.\r\nFixed :BackTwitter behavior with lists.\r\nUpgraded bit.ly API support to version 2.0.1.\r\nAdded support for Zi.ma URL shortener.\r\n","3":"Added some support for Retweet API.\r\nFixed :BackTwitter behavior with lists.\r\nUpgraded bit.ly API support to version 2.0.1.\r\nAdded support for Zi.ma URL shortener.\r\n","package":"twitvim-0.4.4.vba","4":"twitvim-0.4.4.vba","src_id":"11915","5":"11915","creation_date":"1261092865","6":"1261092865"},{"0":"2204","vim_version":"7.0","1":"7.0","script_version":"0.4.3","2":"0.4.3","version_comment":"* Added |:ListTwitter|\r\n* Fixed some minor breakage in LongURL support.\r\n* Omit author's name from the list when doing a reply to all.\r\n","3":"* Added |:ListTwitter|\r\n* Fixed some minor breakage in LongURL support.\r\n* Omit author's name from the list when doing a reply to all.\r\n","package":"twitvim-0.4.3.vba","4":"twitvim-0.4.3.vba","src_id":"11820","5":"11820","creation_date":"1259344258","6":"1259344258"},{"0":"2204","vim_version":"7.0","1":"7.0","script_version":"0.4.2","2":"0.4.2","version_comment":"* Bugfix: Reset syntax items in Twitter window.\r\n* Bugfix: Show progress message before querying for in-reply-to tweet.\r\n* Added reply to all feature.\r\n","3":"* Bugfix: Reset syntax items in Twitter window.\r\n* Bugfix: Show progress message before querying for in-reply-to tweet.\r\n* Added reply to all feature.\r\n","package":"twitvim-0.4.2.vba","4":"twitvim-0.4.2.vba","src_id":"10989","5":"10989","creation_date":"1247249129","6":"1247249129"},{"0":"2204","vim_version":"7.0","1":"7.0","script_version":"0.4.1","2":"0.4.1","version_comment":"Fixed a problem with usernames and search terms that begin with digits.\r\n","3":"Fixed a problem with usernames and search terms that begin with digits.\r\n","package":"twitvim-0.4.1.vba","4":"twitvim-0.4.1.vba","src_id":"10325","5":"10325","creation_date":"1238449274","6":"1238449274"},{"0":"2204","vim_version":"7.0","1":"7.0","script_version":"0.4.0","2":"0.4.0","version_comment":"Many changes. See release notes at http:\/\/mortonfox.livejournal.com\/654033.html\r\n","3":"Many changes. See release notes at http:\/\/mortonfox.livejournal.com\/654033.html\r\n","package":"twitvim-0.4.0.vba","4":"twitvim-0.4.0.vba","src_id":"10154","5":"10154","creation_date":"1236636545","6":"1236636545"},{"0":"2204","vim_version":"7.0","1":"7.0","script_version":"0.3.5","2":"0.3.5","version_comment":"* Added support for pagination and page length to :SearchTwitter.\r\n* Shortened default retweet prefix to \"RT\".\r\n","3":"* Added support for pagination and page length to :SearchTwitter.\r\n* Shortened default retweet prefix to \"RT\".\r\n","package":"twitvim-0.3.5.vba","4":"twitvim-0.3.5.vba","src_id":"9913","5":"9913","creation_date":"1233781936","6":"1233781936"},{"0":"2204","vim_version":"7.0","1":"7.0","script_version":"0.3.4","2":"0.3.4","version_comment":"Added twitvim_count option to allow user to configure the number of tweets returned by :FriendsTwitter and :UserTwitter.\r\n","3":"Added twitvim_count option to allow user to configure the number of tweets returned by :FriendsTwitter and :UserTwitter.\r\n","package":"twitvim-0.3.4.vba","4":"twitvim-0.3.4.vba","src_id":"9501","5":"9501","creation_date":"1226703642","6":"1226703642"},{"0":"2204","vim_version":"7.0","1":"7.0","script_version":"0.3.3","2":"0.3.3","version_comment":"* Added support for Cligs. |:Cligs|\r\n* Fixed a problem with not being able to unset the proxy if using Tcl http.\r\n","3":"* Added support for Cligs. |:Cligs|\r\n* Fixed a problem with not being able to unset the proxy if using Tcl http.\r\n","package":"twitvim-0.3.3.vba","4":"twitvim-0.3.3.vba","src_id":"9325","5":"9325","creation_date":"1223585459","6":"1223585459"},{"0":"2204","vim_version":"7.0","1":"7.0","script_version":"0.3.2","2":"0.3.2","version_comment":"* Added command to display rate limit info.\r\n* Improved error reporting for :UserTwitter.\r\n* Added command and mapping to display user profile information.\r\n* Added command for updating location.\r\n* Added support for tr.im.\r\n* Error reporting fix for Tcl http code.\r\n","3":"* Added command to display rate limit info.\r\n* Improved error reporting for :UserTwitter.\r\n* Added command and mapping to display user profile information.\r\n* Added command for updating location.\r\n* Added support for tr.im.\r\n* Error reporting fix for Tcl http code.\r\n","package":"twitvim-0.3.2.vba","4":"twitvim-0.3.2.vba","src_id":"9298","5":"9298","creation_date":"1222898926","6":"1222898926"},{"0":"2204","vim_version":"7.0","1":"7.0","script_version":"0.3.1","2":"0.3.1","version_comment":"* Added support for http networking through the Vim Perl, Python, Ruby, and Tcl interfaces, as alternatives to cURL. See :help TwitVim-non-cURL for setup details.\r\n* Removed UrlTea support.\r\n* Added support for posting Unicode tweets.\r\n* Added support for LongURL.\r\n* Remove newlines from tweets before retweeting.\r\n\r\n","3":"* Added support for http networking through the Vim Perl, Python, Ruby, and Tcl interfaces, as alternatives to cURL. See :help TwitVim-non-cURL for setup details.\r\n* Removed UrlTea support.\r\n* Added support for posting Unicode tweets.\r\n* Added support for LongURL.\r\n* Remove newlines from tweets before retweeting.\r\n\r\n","package":"twitvim-0.3.1.vba","4":"twitvim-0.3.1.vba","src_id":"9269","5":"9269","creation_date":"1222107556","6":"1222107556"},{"0":"2204","vim_version":"7.0","1":"7.0","script_version":"0.2.24","2":"0.2.24","version_comment":"Added retweet feature.","3":"Added retweet feature.","package":"twitvim-0.2.24.vba","4":"twitvim-0.2.24.vba","src_id":"9195","5":"9195","creation_date":"1220023806","6":"1220023806"},{"0":"2204","vim_version":"7.0","1":"7.0","script_version":"0.2.23","2":"0.2.23","version_comment":"* Support in_reply_to_status_id parameter.\r\n* Added tip on line length in statusline.\r\n* Report browser launch errors.\r\n* Set syntax highlighting on every timeline refresh.\r\n","3":"* Support in_reply_to_status_id parameter.\r\n* Added tip on line length in statusline.\r\n* Report browser launch errors.\r\n* Set syntax highlighting on every timeline refresh.\r\n","package":"twitvim-0.2.23.vba","4":"twitvim-0.2.23.vba","src_id":"9174","5":"9174","creation_date":"1219747449","6":"1219747449"},{"0":"2204","vim_version":"7.0","1":"7.0","script_version":"0.2.22","2":"0.2.22","version_comment":"Rewrote date\/time formatting code in pure Vim script so it should now work on almost any Vim installation without requiring if_perl or if_python.","3":"Rewrote date\/time formatting code in pure Vim script so it should now work on almost any Vim installation without requiring if_perl or if_python.","package":"twitvim-0.2.22.vba","4":"twitvim-0.2.22.vba","src_id":"9122","5":"9122","creation_date":"1218659225","6":"1218659225"},{"0":"2204","vim_version":"7.0","1":"7.0","script_version":"0.2.21","2":"0.2.21","version_comment":"* Added tips section to documentation.\r\n* Use create_or_reuse instead of create in UrlBorg API so that it will always generate the same short URL for the same long URL.\r\n* Added support for highlighting #hashtags and jumping to Twitter Searches for #hashtags.\r\n* Added Python code to convert Twitter timestamps to local time and simplify them.\r\n","3":"* Added tips section to documentation.\r\n* Use create_or_reuse instead of create in UrlBorg API so that it will always generate the same short URL for the same long URL.\r\n* Added support for highlighting #hashtags and jumping to Twitter Searches for #hashtags.\r\n* Added Python code to convert Twitter timestamps to local time and simplify them.\r\n","package":"twitvim-0.2.21.vba","4":"twitvim-0.2.21.vba","src_id":"9117","5":"9117","creation_date":"1218581212","6":"1218581212"},{"0":"2204","vim_version":"7.0","1":"7.0","script_version":"0.2.20","2":"0.2.20","version_comment":"Switched from Summize to Twitter Search.","3":"Switched from Summize to Twitter Search.","package":"twitvim-0.2.20.vba","4":"twitvim-0.2.20.vba","src_id":"9020","5":"9020","creation_date":"1216943540","6":"1216943540"},{"0":"2204","vim_version":"7.0","1":"7.0","script_version":"0.2.19","2":"0.2.19","version_comment":"Added support for non-Twitter servers implementing the Twitter API. This is for identi.ca support.\r\n","3":"Added support for non-Twitter servers implementing the Twitter API. This is for identi.ca support.\r\n","package":"twitvim-0.2.19.vba","4":"twitvim-0.2.19.vba","src_id":"9011","5":"9011","creation_date":"1216854809","6":"1216854809"},{"0":"2204","vim_version":"7.0","1":"7.0","script_version":"0.2.18","2":"0.2.18","version_comment":"Added support for urlBorg API.\r\n","3":"Added support for urlBorg API.\r\n","package":"twitvim-0.2.18.vba","4":"twitvim-0.2.18.vba","src_id":"8953","5":"8953","creation_date":"1216047834","6":"1216047834"},{"0":"2204","vim_version":"7.0","1":"7.0","script_version":"0.2.17","2":"0.2.17","version_comment":"* Added command to show DM Sent Timeline.\r\n* Added support for pagination in Friends, User, Replies, DM, and DM Sent timelines.\r\n* Added support for bit.ly API and is.gd API.\r\n","3":"* Added command to show DM Sent Timeline.\r\n* Added support for pagination in Friends, User, Replies, DM, and DM Sent timelines.\r\n* Added support for bit.ly API and is.gd API.\r\n","package":"twitvim-0.2.17.vba","4":"twitvim-0.2.17.vba","src_id":"8928","5":"8928","creation_date":"1215799221","6":"1215799221"},{"0":"2204","vim_version":"7.0","1":"7.0","script_version":"0.2.16a","2":"0.2.16a","version_comment":"Escape ! character in browser launch URL.","3":"Escape ! character in browser launch URL.","package":"twitvim-0.2.16a.vba","4":"twitvim-0.2.16a.vba","src_id":"8694","5":"8694","creation_date":"1210894069","6":"1210894069"},{"0":"2204","vim_version":"7.0","1":"7.0","script_version":"0.2.16","2":"0.2.16","version_comment":"Removed quotes around browser launch URL. There was a problem with TwitPic.","3":"Removed quotes around browser launch URL. There was a problem with TwitPic.","package":"twitvim-0.2.16.vba","4":"twitvim-0.2.16.vba","src_id":"8693","5":"8693","creation_date":"1210893196","6":"1210893196"},{"0":"2204","vim_version":"7.0","1":"7.0","script_version":"0.2.15","2":"0.2.15","version_comment":"* Extend :UserTwitter and :FriendsTwitter to show another user's timeline if argument supplied.\r\n* Extend Alt-G mapping to jump to another user's timeline if invoked over @user or user:\r\n* Escape special Vim shell characters in URL when launching web browser.\r\n","3":"* Extend :UserTwitter and :FriendsTwitter to show another user's timeline if argument supplied.\r\n* Extend Alt-G mapping to jump to another user's timeline if invoked over @user or user:\r\n* Escape special Vim shell characters in URL when launching web browser.\r\n","package":"twitvim-0.2.15.vba","4":"twitvim-0.2.15.vba","src_id":"8686","5":"8686","creation_date":"1210716308","6":"1210716308"},{"0":"2204","vim_version":"7.0","1":"7.0","script_version":"0.2.14","2":"0.2.14","version_comment":"Added support for Summize search API.","3":"Added support for Summize search API.","package":"twitvim-0.2.14.vba","4":"twitvim-0.2.14.vba","src_id":"8684","5":"8684","creation_date":"1210631881","6":"1210631881"},{"0":"2204","vim_version":"7.0","1":"7.0","script_version":"0.2.13","2":"0.2.13","version_comment":"Added mappings to launch web browser on URLs in timeline.\r\n","3":"Added mappings to launch web browser on URLs in timeline.\r\n","package":"twitvim-0.2.13.vba","4":"twitvim-0.2.13.vba","src_id":"8659","5":"8659","creation_date":"1210200479","6":"1210200479"},{"0":"2204","vim_version":"7.0","1":"7.0","script_version":"0.2.12","2":"0.2.12","version_comment":"Allow user to specify Twitter login info and proxy login info preencoded in base64.","3":"Allow user to specify Twitter login info and proxy login info preencoded in base64.","package":"twitvim-0.2.12.vba","4":"twitvim-0.2.12.vba","src_id":"8648","5":"8648","creation_date":"1210025372","6":"1210025372"},{"0":"2204","vim_version":"7.0","1":"7.0","script_version":"0.2.11","2":"0.2.11","version_comment":"* Scroll to top in timeline window after adding an update line.\r\n* Add <Leader>r and <Leader>d mappings as alternative to Alt-R and Alt-D.\r\n","3":"* Scroll to top in timeline window after adding an update line.\r\n* Add <Leader>r and <Leader>d mappings as alternative to Alt-R and Alt-D.\r\n","package":"twitvim-0.2.11.vba","4":"twitvim-0.2.11.vba","src_id":"8636","5":"8636","creation_date":"1209736336","6":"1209736336"},{"0":"2204","vim_version":"7.0","1":"7.0","script_version":"0.2.10","2":"0.2.10","version_comment":"* Shortened snipurl.com to snipr.com\r\n* Added support for proxy authentication.\r\n* Handle Perl module load failure. Not that I expect those modules to ever be missing.\r\n","3":"* Shortened snipurl.com to snipr.com\r\n* Added support for proxy authentication.\r\n* Handle Perl module load failure. Not that I expect those modules to ever be missing.\r\n","package":"twitvim-0.2.10.vba","4":"twitvim-0.2.10.vba","src_id":"8606","5":"8606","creation_date":"1209120901","6":"1209120901"},{"0":"2204","vim_version":"7.0","1":"7.0","script_version":"0.2.9","2":"0.2.9","version_comment":"* Added some status messages.\r\n* Added menu items under Plugin menu.\r\n* Allow Ctrl-T as an alternative to Alt-T to avoid conflict with the menu bar.\r\n* Added support for UrlTea API.\r\n* Generalize URL encoding to all non-alpha chars.\r\n","3":"* Added some status messages.\r\n* Added menu items under Plugin menu.\r\n* Allow Ctrl-T as an alternative to Alt-T to avoid conflict with the menu bar.\r\n* Added support for UrlTea API.\r\n* Generalize URL encoding to all non-alpha chars.\r\n","package":"twitvim-0.2.9.vba","4":"twitvim-0.2.9.vba","src_id":"8592","5":"8592","creation_date":"1208904984","6":"1208904984"},{"0":"2204","vim_version":"7.0","1":"7.0","script_version":"0.2.8","2":"0.2.8","version_comment":"* Encode URLs sent to URL-shortening services.\r\n","3":"* Encode URLs sent to URL-shortening services.\r\n","package":"twitvim-0.2.8.vba","4":"twitvim-0.2.8.vba","src_id":"8590","5":"8590","creation_date":"1208865208","6":"1208865208"},{"0":"2204","vim_version":"7.0","1":"7.0","script_version":"0.2.7","2":"0.2.7","version_comment":"* Add support for TinyURL API.\r\n* Add quick direct message feature.\r\n","3":"* Add support for TinyURL API.\r\n* Add quick direct message feature.\r\n","package":"twitvim-0.2.7.vba","4":"twitvim-0.2.7.vba","src_id":"8588","5":"8588","creation_date":"1208787567","6":"1208787567"},{"0":"2204","vim_version":"7.0","1":"7.0","script_version":"0.2.6","2":"0.2.6","version_comment":"* Delete Twitter buffer to the blackhole register to avoid stepping on registers unnecessarily.\r\n* Quote login and proxy arguments before sending to cURL.\r\n* Added support for SnipURL API and Metamark API.\r\n","3":"* Delete Twitter buffer to the blackhole register to avoid stepping on registers unnecessarily.\r\n* Quote login and proxy arguments before sending to cURL.\r\n* Added support for SnipURL API and Metamark API.\r\n","package":"twitvim-0.2.6.vba","4":"twitvim-0.2.6.vba","src_id":"8565","5":"8565","creation_date":"1208301454","6":"1208301454"},{"0":"2204","vim_version":"7.0","1":"7.0","script_version":"0.2.5","2":"0.2.5","version_comment":"* Escape the \"+\" character in sent tweets.\r\n* Added Perl code to convert Twitter timestamps to local time and simplify them.\r\n* Fix for timestamp highlight when the \"|\" character appears in a tweet.\r\n","3":"* Escape the \"+\" character in sent tweets.\r\n* Added Perl code to convert Twitter timestamps to local time and simplify them.\r\n* Fix for timestamp highlight when the \"|\" character appears in a tweet.\r\n","package":"twitvim-0.2.5.vba","4":"twitvim-0.2.5.vba","src_id":"8562","5":"8562","creation_date":"1208200123","6":"1208200123"},{"0":"2204","vim_version":"7.0","1":"7.0","script_version":"0.2.4","2":"0.2.4","version_comment":"* Use <q-args> in Tweetburner commands.\r\n* Improve XML parsing so that order of elements does not matter.\r\n* Changed T mapping to Alt-T to avoid overriding the |T| command.\r\n","3":"* Use <q-args> in Tweetburner commands.\r\n* Improve XML parsing so that order of elements does not matter.\r\n* Changed T mapping to Alt-T to avoid overriding the |T| command.\r\n","package":"twitvim-0.2.4.vba","4":"twitvim-0.2.4.vba","src_id":"8553","5":"8553","creation_date":"1208070635","6":"1208070635"},{"0":"2204","vim_version":"7.0","1":"7.0","script_version":"0.2.3","2":"0.2.3","version_comment":"Added more Tweetburner commands.","3":"Added more Tweetburner commands.","package":"twitvim-0.2.3.vba","4":"twitvim-0.2.3.vba","src_id":"8547","5":"8547","creation_date":"1207929103","6":"1207929103"},{"0":"2204","vim_version":"7.0","1":"7.0","script_version":"0.2.2","2":"0.2.2","version_comment":"* Added quick reply feature.\r\n\t\t\t   * Added Tweetburner support.\r\n\t\t\t   * Changed client ident to \"from twitvim\".","3":"* Added quick reply feature.\r\n\t\t\t   * Added Tweetburner support.\r\n\t\t\t   * Changed client ident to \"from twitvim\".","package":"twitvim-0.2.2.vba","4":"twitvim-0.2.2.vba","src_id":"8545","5":"8545","creation_date":"1207861953","6":"1207861953"},{"0":"2204","vim_version":"7.0","1":"7.0","script_version":"0.2.1","2":"0.2.1","version_comment":"Bug fix for Chinese characters in timeline.\r\nScroll up to newest tweet after refreshing timeline.\r\nChanged Twitter window name to avoid unsafe special characters and clashes with file names.","3":"Bug fix for Chinese characters in timeline.\r\nScroll up to newest tweet after refreshing timeline.\r\nChanged Twitter window name to avoid unsafe special characters and clashes with file names.","package":"twitvim-0.2.1.vba","4":"twitvim-0.2.1.vba","src_id":"8540","5":"8540","creation_date":"1207817064","6":"1207817064"},{"0":"2204","vim_version":"7.0","1":"7.0","script_version":"0.2.0","2":"0.2.0","version_comment":"Added views for public, friends, user timelines, replies, and direct messages. Automatically insert user's posts into public, friends, or user timeline, if visible. Added syntax highlighting for timeline view.","3":"Added views for public, friends, user timelines, replies, and direct messages. Automatically insert user's posts into public, friends, or user timeline, if visible. Added syntax highlighting for timeline view.","package":"twitvim-0.2.0.vba","4":"twitvim-0.2.0.vba","src_id":"8539","5":"8539","creation_date":"1207736795","6":"1207736795"},{"0":"2204","vim_version":"7.0","1":"7.0","script_version":"0.1.2","2":"0.1.2","version_comment":"Added help documentation. Made plugin code conform to guidelines in :help write-plugin. Repackaged as Vimball archive.","3":"Added help documentation. Made plugin code conform to guidelines in :help write-plugin. Repackaged as Vimball archive.","package":"twitvim.vba","4":"twitvim.vba","src_id":"8519","5":"8519","creation_date":"1207239609","6":"1207239609"},{"0":"2204","vim_version":"7.0","1":"7.0","script_version":"0.1.1","2":"0.1.1","version_comment":"Report errors from or problems with cURL.","3":"Report errors from or problems with cURL.","package":"twitvim.vim","4":"twitvim.vim","src_id":"8516","5":"8516","creation_date":"1207058779","6":"1207058779"},{"0":"2204","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial version.","3":"Initial version.","package":"twitvim.vim","4":"twitvim.vim","src_id":"8504","5":"8504","creation_date":"1206715343","6":"1206715343"}]},"2203":{"script_id":"2203","0":"2203","script_name":"vimgen","1":"vimgen","script_type":"utility","2":"utility","summary":"vim inline generator \/ template expander","3":"vim inline generator \/ template expander","description":"Vimgen is a simple template system that works inside a VIM buffer. The \r\ninput is a region of text. Everything until the first empty line in this \r\nregion is considered the data section, everything below the first empty line\r\nis the template section. See included help file.\r\n\r\nThe data section of the input (everything until the first empty line) has to \r\nbe a valid VIM dictionary. Newlines (\"\\n\") but no empty lines can be inserted for \r\nbetter readability (they are ignored). The data section is evaluated using VIM's \r\neval function, hence it can include VIM functions, e.g. from the included range_date.vim.\r\n\r\nThe template section of the input (everything below the first empty line) is the\r\ndesired output (including newlines etc.) that has to be enriched\/multiplied by the \r\ndata using vimgen tags.\r\n\r\nThere are only three types of tags:\r\n\r\n\u00c2\u00ab-var\u00c2\u00bb...\u00c2\u00ab-\u00c2\u00bb          \r\nthis tags loop over the variable 'var' which has to be \r\na list. Inside the loop \u00c2\u00abvar\u00c2\u00bb references the element of\r\nthe current iteration\r\n\r\n\u00c2\u00ab!var\u00c2\u00bb...\u00c2\u00ab-\u00c2\u00bb\r\nused inside a loop over 'var'. The test\/tags that are surrounded\r\nby this tag are ignored in the first iteration of the loop. This\r\nis useful for enumerations (see |vimgen-examples|)\r\n\r\n\u00c2\u00abvar\u00c2\u00bb\r\nthis tag is replaced with the variable 'var', where 'var'\r\neither has only one value or the tag is surrounded by \r\na loop iterating over 'var'. In case of nested dictionaries,\r\na dot notation is used, e.g. a.b.c\r\n\r\nExample of a template for a partitioned oracle table:\r\n\r\n{'date':Range_month(\"200712\",\"200803\"), 'code':[['foo','0OF'',''OFF2'],['bar','RAB']]}\r\n\r\nCREATE TABLE test_table\r\n    (date_id  DATE NOT NULL, id1 NUMBER, id2 NUMBER) \r\nPARTITION BY RANGE (date_id) SUBPARTITION BY LIST (id1)\r\n(\r\n  \u00c2\u00ab-date\u00c2\u00bb\u00c2\u00ab!date\u00c2\u00bb, \r\n  \u00c2\u00ab!\u00c2\u00bbPARTITION testpart_\u00c2\u00abdate\u00c2\u00bb VALUES LESS THAN (TO_DATE('\u00c2\u00abdate\u00c2\u00bb01', 'YYYYMMDD'))\r\n  ( \r\n    \u00c2\u00ab-code\u00c2\u00bb\u00c2\u00ab!code\u00c2\u00bb,\r\n    \u00c2\u00ab!\u00c2\u00bbSUBPARTITION testpart_\u00c2\u00abdate\u00c2\u00bb_\u00c2\u00abcode[0]\u00c2\u00bb VALUES ('\u00c2\u00abcode[1]\u00c2\u00bb')\u00c2\u00ab-\u00c2\u00bb\r\n  )\u00c2\u00ab-\u00c2\u00bb\r\n);\r\n\r\nOutput:\r\nCREATE TABLE test_table\r\n    (date_id  DATE NOT NULL, id1 NUMBER, id2 NUMBER) \r\nPARTITION BY RANGE (date_id) SUBPARTITION BY LIST (id1)\r\n(\r\n  PARTITION testpart_200712 VALUES LESS THAN (TO_DATE('20071201', 'YYYYMMDD'))\r\n  ( \r\n    SUBPARTITION testpart_200712_foo VALUES ('0OF','OFF2'),\r\n    SUBPARTITION testpart_200712_bar VALUES ('RAB')\r\n  ), \r\n  PARTITION testpart_200801 VALUES LESS THAN (TO_DATE('20080101', 'YYYYMMDD'))\r\n  ( \r\n    SUBPARTITION testpart_200801_foo VALUES ('0OF','OFF2'),\r\n    SUBPARTITION testpart_200801_bar VALUES ('RAB')\r\n  ), \r\n  PARTITION testpart_200802 VALUES LESS THAN (TO_DATE('20080201', 'YYYYMMDD'))\r\n  ( \r\n    SUBPARTITION testpart_200802_foo VALUES ('0OF','OFF2'),\r\n    SUBPARTITION testpart_200802_bar VALUES ('RAB')\r\n  ), \r\n  PARTITION testpart_200803 VALUES LESS THAN (TO_DATE('20080301', 'YYYYMMDD'))\r\n  ( \r\n    SUBPARTITION testpart_200803_foo VALUES ('0OF','OFF2'),\r\n    SUBPARTITION testpart_200803_bar VALUES ('RAB')\r\n  )\r\n);","4":"Vimgen is a simple template system that works inside a VIM buffer. The \r\ninput is a region of text. Everything until the first empty line in this \r\nregion is considered the data section, everything below the first empty line\r\nis the template section. See included help file.\r\n\r\nThe data section of the input (everything until the first empty line) has to \r\nbe a valid VIM dictionary. Newlines (\"\\n\") but no empty lines can be inserted for \r\nbetter readability (they are ignored). The data section is evaluated using VIM's \r\neval function, hence it can include VIM functions, e.g. from the included range_date.vim.\r\n\r\nThe template section of the input (everything below the first empty line) is the\r\ndesired output (including newlines etc.) that has to be enriched\/multiplied by the \r\ndata using vimgen tags.\r\n\r\nThere are only three types of tags:\r\n\r\n\u00c2\u00ab-var\u00c2\u00bb...\u00c2\u00ab-\u00c2\u00bb          \r\nthis tags loop over the variable 'var' which has to be \r\na list. Inside the loop \u00c2\u00abvar\u00c2\u00bb references the element of\r\nthe current iteration\r\n\r\n\u00c2\u00ab!var\u00c2\u00bb...\u00c2\u00ab-\u00c2\u00bb\r\nused inside a loop over 'var'. The test\/tags that are surrounded\r\nby this tag are ignored in the first iteration of the loop. This\r\nis useful for enumerations (see |vimgen-examples|)\r\n\r\n\u00c2\u00abvar\u00c2\u00bb\r\nthis tag is replaced with the variable 'var', where 'var'\r\neither has only one value or the tag is surrounded by \r\na loop iterating over 'var'. In case of nested dictionaries,\r\na dot notation is used, e.g. a.b.c\r\n\r\nExample of a template for a partitioned oracle table:\r\n\r\n{'date':Range_month(\"200712\",\"200803\"), 'code':[['foo','0OF'',''OFF2'],['bar','RAB']]}\r\n\r\nCREATE TABLE test_table\r\n    (date_id  DATE NOT NULL, id1 NUMBER, id2 NUMBER) \r\nPARTITION BY RANGE (date_id) SUBPARTITION BY LIST (id1)\r\n(\r\n  \u00c2\u00ab-date\u00c2\u00bb\u00c2\u00ab!date\u00c2\u00bb, \r\n  \u00c2\u00ab!\u00c2\u00bbPARTITION testpart_\u00c2\u00abdate\u00c2\u00bb VALUES LESS THAN (TO_DATE('\u00c2\u00abdate\u00c2\u00bb01', 'YYYYMMDD'))\r\n  ( \r\n    \u00c2\u00ab-code\u00c2\u00bb\u00c2\u00ab!code\u00c2\u00bb,\r\n    \u00c2\u00ab!\u00c2\u00bbSUBPARTITION testpart_\u00c2\u00abdate\u00c2\u00bb_\u00c2\u00abcode[0]\u00c2\u00bb VALUES ('\u00c2\u00abcode[1]\u00c2\u00bb')\u00c2\u00ab-\u00c2\u00bb\r\n  )\u00c2\u00ab-\u00c2\u00bb\r\n);\r\n\r\nOutput:\r\nCREATE TABLE test_table\r\n    (date_id  DATE NOT NULL, id1 NUMBER, id2 NUMBER) \r\nPARTITION BY RANGE (date_id) SUBPARTITION BY LIST (id1)\r\n(\r\n  PARTITION testpart_200712 VALUES LESS THAN (TO_DATE('20071201', 'YYYYMMDD'))\r\n  ( \r\n    SUBPARTITION testpart_200712_foo VALUES ('0OF','OFF2'),\r\n    SUBPARTITION testpart_200712_bar VALUES ('RAB')\r\n  ), \r\n  PARTITION testpart_200801 VALUES LESS THAN (TO_DATE('20080101', 'YYYYMMDD'))\r\n  ( \r\n    SUBPARTITION testpart_200801_foo VALUES ('0OF','OFF2'),\r\n    SUBPARTITION testpart_200801_bar VALUES ('RAB')\r\n  ), \r\n  PARTITION testpart_200802 VALUES LESS THAN (TO_DATE('20080201', 'YYYYMMDD'))\r\n  ( \r\n    SUBPARTITION testpart_200802_foo VALUES ('0OF','OFF2'),\r\n    SUBPARTITION testpart_200802_bar VALUES ('RAB')\r\n  ), \r\n  PARTITION testpart_200803 VALUES LESS THAN (TO_DATE('20080301', 'YYYYMMDD'))\r\n  ( \r\n    SUBPARTITION testpart_200803_foo VALUES ('0OF','OFF2'),\r\n    SUBPARTITION testpart_200803_bar VALUES ('RAB')\r\n  )\r\n);","install_details":"This is a vimball, just edit vimgen.vba and source everything\r\n:so %","5":"This is a vimball, just edit vimgen.vba and source everything\r\n:so %","first_name":"Bastian","6":"Bastian","last_name":"Mathes","7":"Mathes","releases":[{"0":"2203","vim_version":"7.0","1":"7.0","script_version":"0.1.1","2":"0.1.1","version_comment":"small error correction","3":"small error correction","package":"vimgen.vba","4":"vimgen.vba","src_id":"8596","5":"8596","creation_date":"1208990093","6":"1208990093"},{"0":"2203","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"vimgen.vba","4":"vimgen.vba","src_id":"8497","5":"8497","creation_date":"1206543875","6":"1206543875"}]},"2202":{"script_id":"2202","0":"2202","script_name":"Boost Build v2 (BBv2) syntax","1":"Boost Build v2 (BBv2) syntax","script_type":"syntax","2":"syntax","summary":"Syntax highlight for BBv2 build scripts (Jamfile, Jamroot)","3":"Syntax highlight for BBv2 build scripts (Jamfile, Jamroot)","description":"There\u00e2\u0080\u0099s another build system that I personally prefer to use: http:\/\/boost.org\/boost-build2\/index.html\r\nThis scripts cover a small amount of the BBv2 syntax, but the work has just been started ;-) Welcome any contributions!","4":"There\u00e2\u0080\u0099s another build system that I personally prefer to use: http:\/\/boost.org\/boost-build2\/index.html\r\nThis scripts cover a small amount of the BBv2 syntax, but the work has just been started ;-) Welcome any contributions!","install_details":"cd ~\/.vim && tar -xvjf bbv2.tar.bz2 && vim","5":"cd ~\/.vim && tar -xvjf bbv2.tar.bz2 && vim","first_name":"Anatoli","6":"Anatoli","last_name":"Sakhnik","7":"Sakhnik","releases":[{"0":"2202","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"bbv2-1.0.tar.bz2","4":"bbv2-1.0.tar.bz2","src_id":"8494","5":"8494","creation_date":"1206496688","6":"1206496688"}]},"2201":{"script_id":"2201","0":"2201","script_name":"SCMDiff","1":"SCMDiff","script_type":"utility","2":"utility","summary":"Highlight changed lines in a file via SCM diff command","3":"Highlight changed lines in a file via SCM diff command","description":"This script is a modification of the script posted here:\r\nhttp:\/\/tekrat.com\/2008\/02\/21\/vim-diff\/\r\n\r\nIt allows you to quickly toggle (through a keybinding, Ctrl-D by default) the highlighting of changed lines in a file through an SCM's diff command.\r\n\r\nIt also binds Ctrl-G to :set nodiff to quickly turn off the highlighting.\r\n\r\nThe original script was written for git, but this version works for (at least) Mercurial and Subversion as well.  CVS and Perforce likely work but have not been tested.\r\n\r\nIt likely only works on Unix systems, or at least systems with 'cat' and 'patch', in addition to the SCM's command.\r\n\r\nConfiguration consists of the variable g:SCMDiffCommand, which if not set will be set to 'svn', assuming Subversion.  If g:SCMDiffCommand is set to 'hg', it works for Mercurial, and likewise 'git' for git.","4":"This script is a modification of the script posted here:\r\nhttp:\/\/tekrat.com\/2008\/02\/21\/vim-diff\/\r\n\r\nIt allows you to quickly toggle (through a keybinding, Ctrl-D by default) the highlighting of changed lines in a file through an SCM's diff command.\r\n\r\nIt also binds Ctrl-G to :set nodiff to quickly turn off the highlighting.\r\n\r\nThe original script was written for git, but this version works for (at least) Mercurial and Subversion as well.  CVS and Perforce likely work but have not been tested.\r\n\r\nIt likely only works on Unix systems, or at least systems with 'cat' and 'patch', in addition to the SCM's command.\r\n\r\nConfiguration consists of the variable g:SCMDiffCommand, which if not set will be set to 'svn', assuming Subversion.  If g:SCMDiffCommand is set to 'hg', it works for Mercurial, and likewise 'git' for git.","install_details":"Just drop in $VIM\/plugin and set g:SCMDiffCommand to the base command of the SCM system of your choice: i.e. 'svn', 'hg', 'git'.","5":"Just drop in $VIM\/plugin and set g:SCMDiffCommand to the base command of the SCM system of your choice: i.e. 'svn', 'hg', 'git'.","first_name":"James","6":"James","last_name":"Longstreet","7":"Longstreet","releases":[{"0":"2201","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"scmdiff.vim","4":"scmdiff.vim","src_id":"8493","5":"8493","creation_date":"1206428630","6":"1206428630"}]},"2200":{"script_id":"2200","0":"2200","script_name":"northland.vim","1":"northland.vim","script_type":"color scheme","2":"color scheme","summary":"Blueish colorscheme with dominant dark blue\/red","3":"Blueish colorscheme with dominant dark blue\/red","description":"Relatively dark colorscheme, with dominant dark blue and red. For gvim only.","4":"Relatively dark colorscheme, with dominant dark blue and red. For gvim only.","install_details":"- copy file to \\colors directory\r\n- start gvim\r\n- type \":colorscheme northland\"","5":"- copy file to \\colors directory\r\n- start gvim\r\n- type \":colorscheme northland\"","first_name":"Luka","6":"Luka","last_name":"Djigas","7":"Djigas","releases":[{"0":"2200","vim_version":"6.0","1":"6.0","script_version":"0.2","2":"0.2","version_comment":"Added syntax highlighting which has been missing, fixed a few colours ...\r\nScreenshot at http:\/\/i34.tinypic.com\/350uk2e.jpg\r\n","3":"Added syntax highlighting which has been missing, fixed a few colours ...\r\nScreenshot at http:\/\/i34.tinypic.com\/350uk2e.jpg\r\n","package":"northland.vim","4":"northland.vim","src_id":"9563","5":"9563","creation_date":"1227574458","6":"1227574458"},{"0":"2200","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"northland.vim","4":"northland.vim","src_id":"8489","5":"8489","creation_date":"1206391169","6":"1206391169"}]},"2199":{"script_id":"2199","0":"2199","script_name":"gauref.vim","1":"gauref.vim","script_type":"utility","2":"utility","summary":"Look up a reference manual of Gauche","3":"Look up a reference manual of Gauche","description":"Screenshot:\r\n  English: http:\/\/photozou.jp\/photo\/photo_only\/175590\/10747826\r\n  Japanese: http:\/\/photozou.jp\/photo\/photo_only\/175590\/10747824\r\n\r\nDescription in Japanese:\r\n  http:\/\/vim.g.hatena.ne.jp\/keyword\/gauref.vim \r\n\r\nDescription: ---------------------------------------------------------- {{{1\r\n  Gauref provides interfaces to look up a keyword in a reference manual of\r\n  Gauche which is an R5RS Scheme implementation.\r\n                                                                             \r\n  You can look up a keyword:\r\n    - command-line with completion.\r\n    - under the cursor in Normal mode.\r\n    - selected in Visual mode.\r\n                                                                             \r\n  In the buffer of reference manual, folds for every section\/entry are\r\n  created and closed by default. You can open a closed fold by looking up\r\n  it.\r\n                                                                             \r\n  gauche-refe.txt and gauche-refj.txt are Gauche reference manuals of\r\n  English and Japanese version which are converted texi files inluded Gauche\r\n  package.\r\n                                                                             \r\nInstallation: --------------------------------------------------------- {{{1\r\n  - Drop this file in your plugin directory.\r\n  - Drop gauche-refe.txt in ~\/.vim\/. You can change location by\r\n    g:gauref_file option. (To see japanese manual, use gauche-refj.txt)\r\n                                                                             \r\nUsage: ---------------------------------------------------------------- {{{1\r\n  You can look up keywords by command\/mapping.\r\n                                                                             \r\n  Command:\r\n    :Gauref {keyword}\r\n      looks up {keyword}. You can use command-line completion.\r\n                                                                             \r\n  Mapping:\r\n    \"K\"\r\n      looks up the keyword under the cursor in Normal mode, or selected\r\n      keyword in Visual mode.\r\n                                                                             \r\n  If there is more than one entry with the same name, you can jump to next\r\n  entry by using \"K\" on the keyword.\r\n                                                                             \r\n                                                                             \r\nOptions: -------------------------------------------------------------- {{{1\r\n  g:gauref_file:\r\n    The file name of Gauche reference manual.\r\n                                                                             \r\n  g:gauref_key_lookup:\r\n    The key which is mapped to look up the keyword under the cursor or\r\n    selected.\r\n","4":"Screenshot:\r\n  English: http:\/\/photozou.jp\/photo\/photo_only\/175590\/10747826\r\n  Japanese: http:\/\/photozou.jp\/photo\/photo_only\/175590\/10747824\r\n\r\nDescription in Japanese:\r\n  http:\/\/vim.g.hatena.ne.jp\/keyword\/gauref.vim \r\n\r\nDescription: ---------------------------------------------------------- {{{1\r\n  Gauref provides interfaces to look up a keyword in a reference manual of\r\n  Gauche which is an R5RS Scheme implementation.\r\n                                                                             \r\n  You can look up a keyword:\r\n    - command-line with completion.\r\n    - under the cursor in Normal mode.\r\n    - selected in Visual mode.\r\n                                                                             \r\n  In the buffer of reference manual, folds for every section\/entry are\r\n  created and closed by default. You can open a closed fold by looking up\r\n  it.\r\n                                                                             \r\n  gauche-refe.txt and gauche-refj.txt are Gauche reference manuals of\r\n  English and Japanese version which are converted texi files inluded Gauche\r\n  package.\r\n                                                                             \r\nInstallation: --------------------------------------------------------- {{{1\r\n  - Drop this file in your plugin directory.\r\n  - Drop gauche-refe.txt in ~\/.vim\/. You can change location by\r\n    g:gauref_file option. (To see japanese manual, use gauche-refj.txt)\r\n                                                                             \r\nUsage: ---------------------------------------------------------------- {{{1\r\n  You can look up keywords by command\/mapping.\r\n                                                                             \r\n  Command:\r\n    :Gauref {keyword}\r\n      looks up {keyword}. You can use command-line completion.\r\n                                                                             \r\n  Mapping:\r\n    \"K\"\r\n      looks up the keyword under the cursor in Normal mode, or selected\r\n      keyword in Visual mode.\r\n                                                                             \r\n  If there is more than one entry with the same name, you can jump to next\r\n  entry by using \"K\" on the keyword.\r\n                                                                             \r\n                                                                             \r\nOptions: -------------------------------------------------------------- {{{1\r\n  g:gauref_file:\r\n    The file name of Gauche reference manual.\r\n                                                                             \r\n  g:gauref_key_lookup:\r\n    The key which is mapped to look up the keyword under the cursor or\r\n    selected.\r\n","install_details":"","5":"","first_name":"Takeshi","6":"Takeshi","last_name":"NISHIDA","7":"NISHIDA","releases":[{"0":"2199","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"gauref.zip","4":"gauref.zip","src_id":"8488","5":"8488","creation_date":"1206258770","6":"1206258770"}]},"2198":{"script_id":"2198","0":"2198","script_name":"rastafari.vim","1":"rastafari.vim","script_type":"color scheme","2":"color scheme","summary":"color scheme for black terminal or GUI","3":"color scheme for black terminal or GUI","description":"This is a dark color scheme (for GUI or black terminal).  I named it rastafari bacause its main colors: black, green, red, gold.\r\n\r\nIt should work equally well for color terminal and GUI.\r\n\r\nScreenshot:\r\n  http:\/\/dominique.pelle.free.fr\/rastafari.vim.png\r\n\r\nSee also my ~\/.vimrc highlighted with the rastafari colorscheme:\r\n  http:\/\/dominique.pelle.free.fr\/.vimrc.html\r\n","4":"This is a dark color scheme (for GUI or black terminal).  I named it rastafari bacause its main colors: black, green, red, gold.\r\n\r\nIt should work equally well for color terminal and GUI.\r\n\r\nScreenshot:\r\n  http:\/\/dominique.pelle.free.fr\/rastafari.vim.png\r\n\r\nSee also my ~\/.vimrc highlighted with the rastafari colorscheme:\r\n  http:\/\/dominique.pelle.free.fr\/.vimrc.html\r\n","install_details":"Copy rastafari.vim either to ~\/.vim\/colors\/ or ($HOME\/vimfiles\/colors\/ on Windows)\r\nCommand to set: colorscheme rastafari","5":"Copy rastafari.vim either to ~\/.vim\/colors\/ or ($HOME\/vimfiles\/colors\/ on Windows)\r\nCommand to set: colorscheme rastafari","first_name":"Dominique","6":"Dominique","last_name":"Pell\u00c3\u00a9","7":"Pell\u00c3\u00a9","releases":[{"0":"2198","vim_version":"6.0","1":"6.0","script_version":"1.7","2":"1.7","version_comment":"- updates for highlighting XML files","3":"- updates for highlighting XML files","package":"rastafari.vim","4":"rastafari.vim","src_id":"13292","5":"13292","creation_date":"1278284748","6":"1278284748"},{"0":"2198","vim_version":"6.0","1":"6.0","script_version":"1.6","2":"1.6","version_comment":"- Improved colors for vim-diff and many other updates.","3":"- Improved colors for vim-diff and many other updates.","package":"rastafari.vim","4":"rastafari.vim","src_id":"10968","5":"10968","creation_date":"1247061402","6":"1247061402"},{"0":"2198","vim_version":"6.0","1":"6.0","script_version":"1.5","2":"1.5","version_comment":"- more consistency between GUI and cterm\r\n- added more highlight groups","3":"- more consistency between GUI and cterm\r\n- added more highlight groups","package":"rastafari.vim","4":"rastafari.vim","src_id":"10164","5":"10164","creation_date":"1236716238","6":"1236716238"},{"0":"2198","vim_version":"6.0","1":"6.0","script_version":"1.4","2":"1.4","version_comment":"- tuned colors for doxygen, netrw, perl, diff\r\n- added color for cursor\r\n- make it more portable (if has('...'))","3":"- tuned colors for doxygen, netrw, perl, diff\r\n- added color for cursor\r\n- make it more portable (if has('...'))","package":"rastafari.vim","4":"rastafari.vim","src_id":"9856","5":"9856","creation_date":"1232844323","6":"1232844323"},{"0":"2198","vim_version":"6.0","1":"6.0","script_version":"1.3","2":"1.3","version_comment":"- check version of vim before setting spelling colors\r\n- improved colors for Perl\r\n- improved colors for Doxygen comments\r\n- improved colors for diff","3":"- check version of vim before setting spelling colors\r\n- improved colors for Perl\r\n- improved colors for Doxygen comments\r\n- improved colors for diff","package":"rastafari.vim","4":"rastafari.vim","src_id":"8582","5":"8582","creation_date":"1208683184","6":"1208683184"},{"0":"2198","vim_version":"6.0","1":"6.0","script_version":"1.2","2":"1.2","version_comment":"- improved consistency of GUI and cterm","3":"- improved consistency of GUI and cterm","package":"rastafari.vim","4":"rastafari.vim","src_id":"8491","5":"8491","creation_date":"1206415429","6":"1206415429"},{"0":"2198","vim_version":"6.0","1":"6.0","script_version":"1.1","2":"1.1","version_comment":"- updated Visual and Pmenu colors. Improved consistency between GUI and cterm","3":"- updated Visual and Pmenu colors. Improved consistency between GUI and cterm","package":"rastafari.vim","4":"rastafari.vim","src_id":"8490","5":"8490","creation_date":"1206414917","6":"1206414917"},{"0":"2198","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"rastafari.vim","4":"rastafari.vim","src_id":"8486","5":"8486","creation_date":"1206233663","6":"1206233663"}]},"2197":{"script_id":"2197","0":"2197","script_name":"beauty256","1":"beauty256","script_type":"color scheme","2":"color scheme","summary":"A beautiful theme specially designed for xterm with 256 color","3":"A beautiful theme specially designed for xterm with 256 color","description":"this is my first theme here. it uses natural and friendly colors. and convert your terminal vim to modern-looking IDE.\r\nscreenshots are here: \r\n\r\nhttp:\/\/b.imagehost.org\/view\/0306\/beauty256.png\r\nhttp:\/\/b.imagehost.org\/view\/0309\/beauty256_2.png\r\n\r\nthis is specially designed for xterm with 256 color like terminal of ubuntu systems.\r\n","4":"this is my first theme here. it uses natural and friendly colors. and convert your terminal vim to modern-looking IDE.\r\nscreenshots are here: \r\n\r\nhttp:\/\/b.imagehost.org\/view\/0306\/beauty256.png\r\nhttp:\/\/b.imagehost.org\/view\/0309\/beauty256_2.png\r\n\r\nthis is specially designed for xterm with 256 color like terminal of ubuntu systems.\r\n","install_details":"copy the beauty256.vim script to $HOME\/.vim\/colors folder.\r\ndont forget to add this line to your .vimrc\r\n\r\nset t_Co=256\r\ncolor beauty256\r\n\r\nfirst line set vim to use 256 color in terminal.","5":"copy the beauty256.vim script to $HOME\/.vim\/colors folder.\r\ndont forget to add this line to your .vimrc\r\n\r\nset t_Co=256\r\ncolor beauty256\r\n\r\nfirst line set vim to use 256 color in terminal.","first_name":"Mahmoud","6":"Mahmoud","last_name":"Sahebi","7":"Sahebi","releases":[{"0":"2197","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"beauty256.vim","4":"beauty256.vim","src_id":"8484","5":"8484","creation_date":"1206171607","6":"1206171607"}]},"2196":{"script_id":"2196","0":"2196","script_name":"antlr3.vim","1":"antlr3.vim","script_type":"syntax","2":"syntax","summary":"ANTLR v3 error parsing for ANT","3":"ANTLR v3 error parsing for ANT","description":"ANTLR v3 has some strangely formatted error messages. With ANT you can use the errorformat of this script.","4":"ANTLR v3 has some strangely formatted error messages. With ANT you can use the errorformat of this script.","install_details":"Source it or replace the appropriate location in your ant.vim file.","5":"Source it or replace the appropriate location in your ant.vim file.","first_name":"Manfred","6":"Manfred","last_name":"W\u00c3\u00b6lfel","7":"W\u00c3\u00b6lfel","releases":[{"0":"2196","vim_version":"7.0","1":"7.0","script_version":"0.0","2":"0.0","version_comment":"Initial upload","3":"Initial upload","package":"antlr3.vim","4":"antlr3.vim","src_id":"8482","5":"8482","creation_date":"1206148433","6":"1206148433"}]},"2195":{"script_id":"2195","0":"2195","script_name":"Unicode Macro Table","1":"Unicode Macro Table","script_type":"utility","2":"utility","summary":"Macros to easily add mathematical symbols and operators to your document","3":"Macros to easily add mathematical symbols and operators to your document","description":"Provided under the GPLv3 (http:\/\/www.gnu.org\/licenses\/gpl.txt).\r\n\r\nThis script provides the needed functionality to easily register insert mode macros for useful Unicode characters as well as initial mapping tables for a mostly math oriented background.\r\n\r\nFor further information refer to: http:\/\/westhoffswelt.de\/blog\/vim_unicode_macros.html","4":"Provided under the GPLv3 (http:\/\/www.gnu.org\/licenses\/gpl.txt).\r\n\r\nThis script provides the needed functionality to easily register insert mode macros for useful Unicode characters as well as initial mapping tables for a mostly math oriented background.\r\n\r\nFor further information refer to: http:\/\/westhoffswelt.de\/blog\/vim_unicode_macros.html","install_details":"Simple source the script inside your .vimrc to register the needed macros. You may then use any macro name listed inside the first part of the script file with a backslash in front of it. Therefore just typing e.g. \"\\alpha \\beta \\gamma\" in insert mode would give you the Greek letters you want.\r\n\r\nYou may customize every mapping table to your linkings or add new ones. If you create new tables or extend the ones already present I would be grateful if you could send me a copy of your work, for everyone to benefit from.","5":"Simple source the script inside your .vimrc to register the needed macros. You may then use any macro name listed inside the first part of the script file with a backslash in front of it. Therefore just typing e.g. \"\\alpha \\beta \\gamma\" in insert mode would give you the Greek letters you want.\r\n\r\nYou may customize every mapping table to your linkings or add new ones. If you create new tables or extend the ones already present I would be grateful if you could send me a copy of your work, for everyone to benefit from.","first_name":"Jakob","6":"Jakob","last_name":"Westhoff","7":"Westhoff","releases":[{"0":"2195","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"unicodemacros_0.1.tar.gz","4":"unicodemacros_0.1.tar.gz","src_id":"8481","5":"8481","creation_date":"1206111998","6":"1206111998"}]},"2194":{"script_id":"2194","0":"2194","script_name":"number marks","1":"number marks","script_type":"utility","2":"utility","summary":"showing marks using number array in color, easy to trace.","3":"showing marks using number array in color, easy to trace.","description":"You can show your marks using number array in color, and you can delete one or all marks(now, you can replace a mark to another place). The color depend on your color scheme setting. You easy to trace the marks using hot key, move to ahead or behind. The mark's number make you easy to understand where you are. And you also can save and reload these marks in a file.\r\n\r\n这个脚本显示用带颜色的数字标明的[标记]，你可以删除你不想用的某个[标记]，或者用F4键全部删掉所有的[标记](现在也可以把一个标记移动位置，而不改变他的数字标号)。带颜色的数字[标记]使你更容易了解当前行在代码中的位置，方便理解代码。[标记]的颜色依赖于你的颜色设定文件。不同的颜色风格可能又不同的[标记]颜色式样。你可以很方便的使用快捷键向前或者向后跟踪你的[标记]。你也可以保存你的[标记]到你指定的文件夹下面，然后以后再次打开所有的[标记]。\r\n\r\n# 两个重要更新，移动标记和在不同的tab页之间跳转, 如果你有两个以上的tab页的话。\r\n\" ##  You can set marks only less 100.  ##\r\n\" ##  If you have more than two tabpage, you can jump from one tabpage to another one.  ##\r\n\r\n这个脚本因为signs的显示的原因，所以只提供最大99个[标记]。\r\n\r\nscreenshot \/ 抓图\r\nhttp:\/\/wiki.ubuntu.org.cn\/images\/b\/b6\/Vim_marks.PNG\r\n\r\n USAGE:\r\n 1:make a mark, or delete it: \r\n  ctrl + F2\r\n  mm\r\n 2:move to ahead mark:          \r\n  shift + F2\r\n  mv\r\n 3:move to next mark:                           \r\n  F2\r\n  mb\r\n 4:delete all marks:\r\n  F4\r\n5:moving a mark:\r\n  m.\r\n  (press m. at the one mark, and move the cursor to another line, press m. again. )\r\n6:save marks\r\n  F6， input a name， press ENTER\r\n7:reload marks\r\n  F5， input a name， press ENTER\r\n\r\n用法：\r\n（下面所有的操作都是在非插入模式下，光标置于你要操作的行）\r\n1：设定一个[标记]，或者取消这个[标记]\r\n    按Ctrl+F2 或者 mm （快速连着按两下m字母键）\r\n2：向前移动\r\n   按 shift + F2 或者 mv （快速按字母m和字母v键）\r\n3：向后移动\r\n   按 F2 或者 mb\r\n4：取消所有的[标记]\r\n    按F4键    （按取消后，再次标记时候重新从01到99开始标数）\r\n5:移动一个[标记]\r\n    把光标移动到一个有标记的行，按m. 这时这个标记改变颜色，\r\n    然后把光标移到一个没有标记的行，再一次按m.  则把刚才的\r\n   标记移动到当前行。\r\n6:保存标记\r\n   按F6，输入一个名称，按回车。\r\n7：读入标记\r\n   按F5，输入一个以保存过的名称，按回车。\r\n","4":"You can show your marks using number array in color, and you can delete one or all marks(now, you can replace a mark to another place). The color depend on your color scheme setting. You easy to trace the marks using hot key, move to ahead or behind. The mark's number make you easy to understand where you are. And you also can save and reload these marks in a file.\r\n\r\n这个脚本显示用带颜色的数字标明的[标记]，你可以删除你不想用的某个[标记]，或者用F4键全部删掉所有的[标记](现在也可以把一个标记移动位置，而不改变他的数字标号)。带颜色的数字[标记]使你更容易了解当前行在代码中的位置，方便理解代码。[标记]的颜色依赖于你的颜色设定文件。不同的颜色风格可能又不同的[标记]颜色式样。你可以很方便的使用快捷键向前或者向后跟踪你的[标记]。你也可以保存你的[标记]到你指定的文件夹下面，然后以后再次打开所有的[标记]。\r\n\r\n# 两个重要更新，移动标记和在不同的tab页之间跳转, 如果你有两个以上的tab页的话。\r\n\" ##  You can set marks only less 100.  ##\r\n\" ##  If you have more than two tabpage, you can jump from one tabpage to another one.  ##\r\n\r\n这个脚本因为signs的显示的原因，所以只提供最大99个[标记]。\r\n\r\nscreenshot \/ 抓图\r\nhttp:\/\/wiki.ubuntu.org.cn\/images\/b\/b6\/Vim_marks.PNG\r\n\r\n USAGE:\r\n 1:make a mark, or delete it: \r\n  ctrl + F2\r\n  mm\r\n 2:move to ahead mark:          \r\n  shift + F2\r\n  mv\r\n 3:move to next mark:                           \r\n  F2\r\n  mb\r\n 4:delete all marks:\r\n  F4\r\n5:moving a mark:\r\n  m.\r\n  (press m. at the one mark, and move the cursor to another line, press m. again. )\r\n6:save marks\r\n  F6， input a name， press ENTER\r\n7:reload marks\r\n  F5， input a name， press ENTER\r\n\r\n用法：\r\n（下面所有的操作都是在非插入模式下，光标置于你要操作的行）\r\n1：设定一个[标记]，或者取消这个[标记]\r\n    按Ctrl+F2 或者 mm （快速连着按两下m字母键）\r\n2：向前移动\r\n   按 shift + F2 或者 mv （快速按字母m和字母v键）\r\n3：向后移动\r\n   按 F2 或者 mb\r\n4：取消所有的[标记]\r\n    按F4键    （按取消后，再次标记时候重新从01到99开始标数）\r\n5:移动一个[标记]\r\n    把光标移动到一个有标记的行，按m. 这时这个标记改变颜色，\r\n    然后把光标移到一个没有标记的行，再一次按m.  则把刚才的\r\n   标记移动到当前行。\r\n6:保存标记\r\n   按F6，输入一个名称，按回车。\r\n7：读入标记\r\n   按F5，输入一个以保存过的名称，按回车。\r\n","install_details":"Unzip marks_corey.zip into your vim's plugin folder.\r\n－－－－－－－－－－－－－－－－－－－－－－\r\n\" If you want to save the marks to a file. Do it like below:\r\n\" Put the one line\r\n\" let g:Signs_file_path_corey='c:\\\\'\r\n\" into your gvimrc or _vimrc, change it to your path.\r\n<F6>   # Save marks.\r\n<F5>   # reload signs.\r\n\r\n简单的解压这个压缩文件到你的vim的plugin文件夹下。\r\n如果要使用[标记]保存功能，最好你要在你的gvimrc，或者_vimrc里面设置\r\nlet g:Signs_file_path_corey='c:\\\\' <<你可以修改成你的有读写权限的文件夹。\r\n<F6>   # 保存所有〔标记〕\r\n<F5>   # 恢复所有〔标记〕\r\n\r\n","5":"Unzip marks_corey.zip into your vim's plugin folder.\r\n－－－－－－－－－－－－－－－－－－－－－－\r\n\" If you want to save the marks to a file. Do it like below:\r\n\" Put the one line\r\n\" let g:Signs_file_path_corey='c:\\\\'\r\n\" into your gvimrc or _vimrc, change it to your path.\r\n<F6>   # Save marks.\r\n<F5>   # reload signs.\r\n\r\n简单的解压这个压缩文件到你的vim的plugin文件夹下。\r\n如果要使用[标记]保存功能，最好你要在你的gvimrc，或者_vimrc里面设置\r\nlet g:Signs_file_path_corey='c:\\\\' <<你可以修改成你的有读写权限的文件夹。\r\n<F6>   # 保存所有〔标记〕\r\n<F5>   # 恢复所有〔标记〕\r\n\r\n","first_name":"Hongli","6":"Hongli","last_name":"Gao","7":"Gao","releases":[{"0":"2194","vim_version":"7.3","1":"7.3","script_version":"1.4","2":"1.4","version_comment":"Afford two hotkeys, \r\n<F5> load marks' file, \r\n<F6> save marks to a file. \r\n\r\n--NOTED  THIS------------------------ \r\nAdd \r\n\r\nlet g:Signs_file_path_corey='c:\\' \r\n\r\nto your gvimrc, change it to your path. \r\n----------------------------- \r\n提供两个新的快捷键， \r\n按F5读入标记文件， \r\n按F6保存标记到文件里。 \r\n----------------------------------- \r\n注意，你的gvimrc文件里面需要加入以下一行。 \r\n\r\nlet g:Signs_file_path_corey='c:\\' \r\n\r\n并且改成你自己喜欢的目录。","3":"Afford two hotkeys, \r\n<F5> load marks' file, \r\n<F6> save marks to a file. \r\n\r\n--NOTED  THIS------------------------ \r\nAdd \r\n\r\nlet g:Signs_file_path_corey='c:\\' \r\n\r\nto your gvimrc, change it to your path. \r\n----------------------------- \r\n提供两个新的快捷键， \r\n按F5读入标记文件， \r\n按F6保存标记到文件里。 \r\n----------------------------------- \r\n注意，你的gvimrc文件里面需要加入以下一行。 \r\n\r\nlet g:Signs_file_path_corey='c:\\' \r\n\r\n并且改成你自己喜欢的目录。","package":"marks_corey.zip","4":"marks_corey.zip","src_id":"13689","5":"13689","creation_date":"1282890165","6":"1282890165"},{"0":"2194","vim_version":"7.0","1":"7.0","script_version":"1.3","2":"1.3","version_comment":"If the buffer is not in the buffer list the sign cannot be added when you reload the marks from a file.\r\n当你重新读取保存在文件里的标记时，如果那个标记所在的buffer没有在当前的buffer list里面的时候，不能正确的显示标记。","3":"If the buffer is not in the buffer list the sign cannot be added when you reload the marks from a file.\r\n当你重新读取保存在文件里的标记时，如果那个标记所在的buffer没有在当前的buffer list里面的时候，不能正确的显示标记。","package":"marks_corey.zip","4":"marks_corey.zip","src_id":"11272","5":"11272","creation_date":"1251356393","6":"1251356393"},{"0":"2194","vim_version":"7.0","1":"7.0","script_version":"1.2","2":"1.2","version_comment":"I'm sorry for updating frequently, this time only for optimizing!\r\n1:reduce screen flash rate when jumping with tabpage.\r\n2:reuse the biggest number for the marks.\r\n\r\n抱歉这么频繁更新，这次是为了优化的目的！\r\n1:当在tabpage之间跳转得时候，降低画面闪烁\r\n2:重新使用被删除的最大号码，也就是在一处不停的使用mm，号码不再无限增长","3":"I'm sorry for updating frequently, this time only for optimizing!\r\n1:reduce screen flash rate when jumping with tabpage.\r\n2:reuse the biggest number for the marks.\r\n\r\n抱歉这么频繁更新，这次是为了优化的目的！\r\n1:当在tabpage之间跳转得时候，降低画面闪烁\r\n2:重新使用被删除的最大号码，也就是在一处不停的使用mm，号码不再无限增长","package":"marks_corey.zip","4":"marks_corey.zip","src_id":"8558","5":"8558","creation_date":"1208153940","6":"1208153940"},{"0":"2194","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"New functions, now you can moving a mark to another place.\r\nand you can jump marks from one tabpage to another one,\r\nthis depends on whether you have more than two tabpages at one time, otherwise jumping will be in one window. So I call this copy 1.0.\r\nBut this not very good at two windows in one tabpage, I will improve it in future.\r\n\r\n添加实用功能， 就是移动一个标记到另一个位置。\r\n同时实现了在不同tabpage页中间跳转标记的功能。\r\n如果你跳转标记的时候使用了两个以上的tab页，那么就在tab页之间\r\n跳转，并且可以在新tab页里面打开当前没有打开的文件。\r\n但是目前没有很好的实现一个tab页里面有多个窗口的问题。\r\n以后解决这个问题。\r\n","3":"New functions, now you can moving a mark to another place.\r\nand you can jump marks from one tabpage to another one,\r\nthis depends on whether you have more than two tabpages at one time, otherwise jumping will be in one window. So I call this copy 1.0.\r\nBut this not very good at two windows in one tabpage, I will improve it in future.\r\n\r\n添加实用功能， 就是移动一个标记到另一个位置。\r\n同时实现了在不同tabpage页中间跳转标记的功能。\r\n如果你跳转标记的时候使用了两个以上的tab页，那么就在tab页之间\r\n跳转，并且可以在新tab页里面打开当前没有打开的文件。\r\n但是目前没有很好的实现一个tab页里面有多个窗口的问题。\r\n以后解决这个问题。\r\n","package":"marks_corey.zip","4":"marks_corey.zip","src_id":"8548","5":"8548","creation_date":"1207983719","6":"1207983719"},{"0":"2194","vim_version":"7.0","1":"7.0","script_version":"0.2","2":"0.2","version_comment":"just unzip this file and cover your old version file.\r\n解压后，覆盖原来的文件就可以。\r\n\r\nfixed a makeing number bug, when you restore the marks from a file. Before this, you restore marks, then the script will makeing number from 01.\r\n\r\n修复一个错误，读取保存在文件里的标记后，再次追加标记时，会重新开始从01编号。如果不使用标记保存功能不会有这个问题。","3":"just unzip this file and cover your old version file.\r\n解压后，覆盖原来的文件就可以。\r\n\r\nfixed a makeing number bug, when you restore the marks from a file. Before this, you restore marks, then the script will makeing number from 01.\r\n\r\n修复一个错误，读取保存在文件里的标记后，再次追加标记时，会重新开始从01编号。如果不使用标记保存功能不会有这个问题。","package":"marks_corey.zip","4":"marks_corey.zip","src_id":"8492","5":"8492","creation_date":"1206428557","6":"1206428557"},{"0":"2194","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"marks_corey.zip","4":"marks_corey.zip","src_id":"8470","5":"8470","creation_date":"1205980851","6":"1205980851"}]},"2193":{"script_id":"2193","0":"2193","script_name":"fpdf.vim","1":"fpdf.vim","script_type":"utility","2":"utility","summary":"PDF writer","3":"PDF writer","description":"fpdf.vim is a port of FPDF.\r\n\r\nAbout FPDF:\r\n  FPDF is a PHP class which allows to generate PDF files with pure PHP.\r\n  See http:\/\/www.fpdf.org\/\r\n\r\n\r\nRequirement:\r\n  :set encoding=utf-8 and iconv() feature for non-ascii text.\r\n  xxd for image\/font embedding.\r\n  xxd and gzip for compression.\r\n\r\n\r\nUsage:\r\n  :set runtimepath+=\/path\/to\/fpdf-vim\r\n  :let FPDF = fpdf#import()\r\n  :let pdf = FPDF.new()\r\n  :call pdf.AddPage()\r\n  :call pdf.SetFont('Arial','B',16)\r\n  :call pdf.Cell(40,10,'Hello World!')\r\n  :let pdfout = pdf.Output()\r\n  :put =pdfout\r\n\r\n\r\nReference:\r\n  See FPDF site.\r\n","4":"fpdf.vim is a port of FPDF.\r\n\r\nAbout FPDF:\r\n  FPDF is a PHP class which allows to generate PDF files with pure PHP.\r\n  See http:\/\/www.fpdf.org\/\r\n\r\n\r\nRequirement:\r\n  :set encoding=utf-8 and iconv() feature for non-ascii text.\r\n  xxd for image\/font embedding.\r\n  xxd and gzip for compression.\r\n\r\n\r\nUsage:\r\n  :set runtimepath+=\/path\/to\/fpdf-vim\r\n  :let FPDF = fpdf#import()\r\n  :let pdf = FPDF.new()\r\n  :call pdf.AddPage()\r\n  :call pdf.SetFont('Arial','B',16)\r\n  :call pdf.Cell(40,10,'Hello World!')\r\n  :let pdfout = pdf.Output()\r\n  :put =pdfout\r\n\r\n\r\nReference:\r\n  See FPDF site.\r\n","install_details":"","5":"","first_name":"Yukihiro","6":"Yukihiro","last_name":"Nakadaira","7":"Nakadaira","releases":[{"0":"2193","vim_version":"7.0","1":"7.0","script_version":"0.4","2":"0.4","version_comment":"Updated codebase to fpdf1.6.","3":"Updated codebase to fpdf1.6.","package":"fpdf-vim.zip","4":"fpdf-vim.zip","src_id":"9129","5":"9129","creation_date":"1218788545","6":"1218788545"},{"0":"2193","vim_version":"7.0","1":"7.0","script_version":"0.3","2":"0.3","version_comment":"Changed to use Vim7.2 floating point feature.\r\nAdded :TOpdf command.","3":"Changed to use Vim7.2 floating point feature.\r\nAdded :TOpdf command.","package":"fpdf-vim.zip","4":"fpdf-vim.zip","src_id":"9116","5":"9116","creation_date":"1218574766","6":"1218574766"},{"0":"2193","vim_version":"7.0","1":"7.0","script_version":"0.2","2":"0.2","version_comment":"Added support embedding font and image (require xxd)","3":"Added support embedding font and image (require xxd)","package":"fpdf-vim.zip","4":"fpdf-vim.zip","src_id":"8480","5":"8480","creation_date":"1206093556","6":"1206093556"},{"0":"2193","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"fpdf-vim.zip","4":"fpdf-vim.zip","src_id":"8469","5":"8469","creation_date":"1205973157","6":"1205973157"}]},"2192":{"script_id":"2192","0":"2192","script_name":"Syntax for Fasta","1":"Syntax for Fasta","script_type":"syntax","2":"syntax","summary":"Highlighting for Fasta (Pearson) format","3":"Highlighting for Fasta (Pearson) format","description":"Syntax highlighting for the Fasta format (Pearson) for biosequences.\r\nAlso available at http:\/\/bioinf.ibun.unal.edu.co\/~miguel\/?id=5","4":"Syntax highlighting for the Fasta format (Pearson) for biosequences.\r\nAlso available at http:\/\/bioinf.ibun.unal.edu.co\/~miguel\/?id=5","install_details":"Just place file into syntax folder.  To tell vim detect fasta files automatically, just put the following line into filetype.vim (into the vim configuration dir):\r\n\r\nau BufNewFile,BufRead *.fasta,*.fa  setf fasta ","5":"Just place file into syntax folder.  To tell vim detect fasta files automatically, just put the following line into filetype.vim (into the vim configuration dir):\r\n\r\nau BufNewFile,BufRead *.fasta,*.fa  setf fasta ","first_name":"Miguel","6":"Miguel","last_name":"Rodriguez","7":"Rodriguez","releases":[{"0":"2192","vim_version":"5.7","1":"5.7","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"fasta.vim","4":"fasta.vim","src_id":"8465","5":"8465","creation_date":"1205856980","6":"1205856980"}]},"2191":{"script_id":"2191","0":"2191","script_name":"MountainDew.vim","1":"MountainDew.vim","script_type":"color scheme","2":"color scheme","summary":"Stay awake through those long hack sessions","3":"Stay awake through those long hack sessions","description":"Do the Dew!  http:\/\/www.servimg.com\/image_preview.php?i=5&u=12096412\r\nCreated with ColorSchemeEditor vimscript #2180","4":"Do the Dew!  http:\/\/www.servimg.com\/image_preview.php?i=5&u=12096412\r\nCreated with ColorSchemeEditor vimscript #2180","install_details":"Copy into $HOME\/.vim\/colors (or %USERPROFILE%\/vimfiles\/colors)","5":"Copy into $HOME\/.vim\/colors (or %USERPROFILE%\/vimfiles\/colors)","first_name":"erik","6":"erik","last_name":"falor","7":"falor","releases":[{"0":"2191","vim_version":"6.0","1":"6.0","script_version":"2.0","2":"2.0","version_comment":"Changed to Unix line endings.","3":"Changed to Unix line endings.","package":"MountainDew.vim","4":"MountainDew.vim","src_id":"8639","5":"8639","creation_date":"1209757004","6":"1209757004"},{"0":"2191","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"MountainDew.vim","4":"MountainDew.vim","src_id":"8463","5":"8463","creation_date":"1205827964","6":"1205827964"}]},"2190":{"script_id":"2190","0":"2190","script_name":"dtrace syntax file","1":"dtrace syntax file","script_type":"syntax","2":"syntax","summary":"This provides excessive highlighting of dtrace script files","3":"This provides excessive highlighting of dtrace script files","description":"This file provides excessive syntax highlighting for files written in the D language that's used with dtrace. A description of the D file format can be found at http:\/\/docs.sun.com\/app\/docs\/doc\/817-6223.\r\n\r\nVersion 1.5 of this script is included in the official vim7.2 distribution.","4":"This file provides excessive syntax highlighting for files written in the D language that's used with dtrace. A description of the D file format can be found at http:\/\/docs.sun.com\/app\/docs\/doc\/817-6223.\r\n\r\nVersion 1.5 of this script is included in the official vim7.2 distribution.","install_details":"Copy dtrace.vim to ~\/.vim\/syntax\/ (on Unix or Mac OS X) or to ...\/vimfiles\/syntax on windows.\r\n\r\nVim usually associates .d files with the D programming language by Digital Mars. To override this, add something like\r\n\r\n      autocmd BufNewFile,BufRead *.d setf dtrace\r\n\r\nto your ~\/.vimrc or to ~\/.vim\/ftdetect\/dtrace.vim (you probably have to create the latter).\r\n\r\n","5":"Copy dtrace.vim to ~\/.vim\/syntax\/ (on Unix or Mac OS X) or to ...\/vimfiles\/syntax on windows.\r\n\r\nVim usually associates .d files with the D programming language by Digital Mars. To override this, add something like\r\n\r\n      autocmd BufNewFile,BufRead *.d setf dtrace\r\n\r\nto your ~\/.vimrc or to ~\/.vim\/ftdetect\/dtrace.vim (you probably have to create the latter).\r\n\r\n","first_name":"Nicolas","6":"Nicolas","last_name":"Weber","7":"Weber","releases":[{"0":"2190","vim_version":"6.0","1":"6.0","script_version":"1.4","2":"1.4","version_comment":"Minor improvements, require at least vim 5.8 (the script upload form only has 5.7 and 6.0 as options, so this does officially require vim 6.0 now).","3":"Minor improvements, require at least vim 5.8 (the script upload form only has 5.7 and 6.0 as options, so this does officially require vim 6.0 now).","package":"dtrace.vim","4":"dtrace.vim","src_id":"8509","5":"8509","creation_date":"1206878661","6":"1206878661"},{"0":"2190","vim_version":"5.7","1":"5.7","script_version":"1.3","2":"1.3","version_comment":"Added highlighting for BEGIN, END, ERROR probe descriptions; improved probe and predicate highlighting; added `rawbytes` to recognized #pragma options.\r\n\r\n","3":"Added highlighting for BEGIN, END, ERROR probe descriptions; improved probe and predicate highlighting; added `rawbytes` to recognized #pragma options.\r\n\r\n","package":"dtrace.vim","4":"dtrace.vim","src_id":"8478","5":"8478","creation_date":"1206092348","6":"1206092348"},{"0":"2190","vim_version":"5.7","1":"5.7","script_version":"1.2","2":"1.2","version_comment":"Highlight `#!\/usr\/sbin\/dtrace -s` if present; improved probe description and predicate highlighting.","3":"Highlight `#!\/usr\/sbin\/dtrace -s` if present; improved probe description and predicate highlighting.","package":"dtrace.vim","4":"dtrace.vim","src_id":"8473","5":"8473","creation_date":"1206005589","6":"1206005589"},{"0":"2190","vim_version":"5.7","1":"5.7","script_version":"1.1","2":"1.1","version_comment":"Added highlighting for valid #pragma D options","3":"Added highlighting for valid #pragma D options","package":"dtrace.vim","4":"dtrace.vim","src_id":"8468","5":"8468","creation_date":"1205936479","6":"1205936479"},{"0":"2190","vim_version":"5.7","1":"5.7","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"dtrace.vim","4":"dtrace.vim","src_id":"8456","5":"8456","creation_date":"1205669398","6":"1205669398"}]},"2189":{"script_id":"2189","0":"2189","script_name":"Luinnar","1":"Luinnar","script_type":"color scheme","2":"color scheme","summary":"Dark color scheme","3":"Dark color scheme","description":"This is a dark color scheme with bright text colors. The background is absolutely black, so the color scheme would suit only the people who aren't afraid of darkness. The text colors are like road lights at night, it's magical from my point of view.\r\n\r\nBelow are some examples:\r\nhttp:\/\/luinnar.narod.ru\/vim\/qsort.png\r\nhttp:\/\/luinnar.narod.ru\/vim\/qsort-term.png (in terminal)\r\n\r\nhttp:\/\/luinnar.narod.ru\/vim\/pick.png\r\nhttp:\/\/luinnar.narod.ru\/vim\/pick-term.png (in terminal)\r\n\r\nhttp:\/\/luinnar.narod.ru\/vim\/dirent.png\r\nhttp:\/\/luinnar.narod.ru\/vim\/dirent-term.png (in terminal)\r\n\r\nDiff mode:\r\nhttp:\/\/luinnar.narod.ru\/vim\/vim-diff.png\r\nhttp:\/\/luinnar.narod.ru\/vim\/vim-diff-term.png (in terminal)\r\n\r\nPS: suggestions are welcome here:\r\nhttps:\/\/github.com\/lxmzhv\/vim\/tree\/master\/colors","4":"This is a dark color scheme with bright text colors. The background is absolutely black, so the color scheme would suit only the people who aren't afraid of darkness. The text colors are like road lights at night, it's magical from my point of view.\r\n\r\nBelow are some examples:\r\nhttp:\/\/luinnar.narod.ru\/vim\/qsort.png\r\nhttp:\/\/luinnar.narod.ru\/vim\/qsort-term.png (in terminal)\r\n\r\nhttp:\/\/luinnar.narod.ru\/vim\/pick.png\r\nhttp:\/\/luinnar.narod.ru\/vim\/pick-term.png (in terminal)\r\n\r\nhttp:\/\/luinnar.narod.ru\/vim\/dirent.png\r\nhttp:\/\/luinnar.narod.ru\/vim\/dirent-term.png (in terminal)\r\n\r\nDiff mode:\r\nhttp:\/\/luinnar.narod.ru\/vim\/vim-diff.png\r\nhttp:\/\/luinnar.narod.ru\/vim\/vim-diff-term.png (in terminal)\r\n\r\nPS: suggestions are welcome here:\r\nhttps:\/\/github.com\/lxmzhv\/vim\/tree\/master\/colors","install_details":"As usual copy the file luinnar.vim into your ~\/.vim\/colors\/ and then perform the command \":colors luinnar\" from within vim.","5":"As usual copy the file luinnar.vim into your ~\/.vim\/colors\/ and then perform the command \":colors luinnar\" from within vim.","first_name":"Luinnar","6":"Luinnar","last_name":".","7":".","releases":[{"0":"2189","vim_version":"7.0","1":"7.0","script_version":"1.3","2":"1.3","version_comment":"Updated terminal colors and some other minor fixes.","3":"Updated terminal colors and some other minor fixes.","package":"luinnar.vim","4":"luinnar.vim","src_id":"14210","5":"14210","creation_date":"1289308594","6":"1289308594"},{"0":"2189","vim_version":"6.0","1":"6.0","script_version":"1.2","2":"1.2","version_comment":"Minor fix","3":"Minor fix","package":"luinnar.vim","4":"luinnar.vim","src_id":"13543","5":"13543","creation_date":"1281428650","6":"1281428650"}]},"2188":{"script_id":"2188","0":"2188","script_name":"earendel","1":"earendel","script_type":"color scheme","2":"color scheme","summary":"Light and cheerful color scheme with friendly colors, highly readable","3":"Light and cheerful color scheme with friendly colors, highly readable","description":"This color scheme is for GUI only, although it contains some tweaks for the console version of Vim, too. It is not too complicated and its highlights are supposed to be cheerful, friendly to your eyes, and easy to read. Though all niceties can only bee seen in Vim 7, this color scheme should work in Vim 6, too.\r\n\r\nSince version 1.1 it contains not only a light color scheme, but also a dark one. The correct scheme is being chosen according to the setting of the option 'background'.\r\n\r\nYou can switch between these styles by using the :Colo command, like \":Colo light\" or \":Colo dark\"","4":"This color scheme is for GUI only, although it contains some tweaks for the console version of Vim, too. It is not too complicated and its highlights are supposed to be cheerful, friendly to your eyes, and easy to read. Though all niceties can only bee seen in Vim 7, this color scheme should work in Vim 6, too.\r\n\r\nSince version 1.1 it contains not only a light color scheme, but also a dark one. The correct scheme is being chosen according to the setting of the option 'background'.\r\n\r\nYou can switch between these styles by using the :Colo command, like \":Colo light\" or \":Colo dark\"","install_details":"Just put it in \"~\/.vim\/colors\" or in \"<your vim directory>\\vimfiles\\colors\" on Windows. Do \":colo earendel\" to apply it. If you want to install it as your default color scheme, just add \"colo earendel\" to your vimrc file.\r\n\r\nIf your background is dark, the dark mode of this scheme will be loaded (and vice versa). If the scheme doesn't load the mode being preferred by you, just add one of the following to your vimrc file:\r\n\r\nset background=dark\r\nset background=light","5":"Just put it in \"~\/.vim\/colors\" or in \"<your vim directory>\\vimfiles\\colors\" on Windows. Do \":colo earendel\" to apply it. If you want to install it as your default color scheme, just add \"colo earendel\" to your vimrc file.\r\n\r\nIf your background is dark, the dark mode of this scheme will be loaded (and vice versa). If the scheme doesn't load the mode being preferred by you, just add one of the following to your vimrc file:\r\n\r\nset background=dark\r\nset background=light","first_name":"Georg","6":"Georg","last_name":"Dahn","7":"Dahn","releases":[{"0":"2188","vim_version":"7.0","1":"7.0","script_version":"2.4.4","2":"2.4.4","version_comment":"Changed CursorColumn from gray to low saturated red.","3":"Changed CursorColumn from gray to low saturated red.","package":"earendel.vim","4":"earendel.vim","src_id":"24222","5":"24222","creation_date":"1462259043","6":"1462259043"},{"0":"2188","vim_version":"7.0","1":"7.0","script_version":"2.4.3","2":"2.4.3","version_comment":"Changed guibg of Normal slightly to increase contrast.","3":"Changed guibg of Normal slightly to increase contrast.","package":"earendel.vim","4":"earendel.vim","src_id":"22767","5":"22767","creation_date":"1420704228","6":"1420704228"},{"0":"2188","vim_version":"7.0","1":"7.0","script_version":"2.4.2","2":"2.4.2","version_comment":"Changed color of LineNr, NonText, CursorLineNr, FoldColumn, and SignColumn to make it more distinguishable from Normal.","3":"Changed color of LineNr, NonText, CursorLineNr, FoldColumn, and SignColumn to make it more distinguishable from Normal.","package":"earendel.vim","4":"earendel.vim","src_id":"20815","5":"20815","creation_date":"1379448881","6":"1379448881"},{"0":"2188","vim_version":"7.0","1":"7.0","script_version":"2.4.1","2":"2.4.1","version_comment":"Light scheme: corrected colors of selections and folds.","3":"Light scheme: corrected colors of selections and folds.","package":"earendel.vim","4":"earendel.vim","src_id":"20727","5":"20727","creation_date":"1377760930","6":"1377760930"},{"0":"2188","vim_version":"7.0","1":"7.0","script_version":"2.4","2":"2.4","version_comment":"Changed many highlight groups concerning UI to monochrome and added CursorLineNr.","3":"Changed many highlight groups concerning UI to monochrome and added CursorLineNr.","package":"earendel.vim","4":"earendel.vim","src_id":"20726","5":"20726","creation_date":"1377703710","6":"1377703710"},{"0":"2188","vim_version":"7.0","1":"7.0","script_version":"2.3.6","2":"2.3.6","version_comment":"Light scheme: made background slightly lighter, changed font color to dark gray.","3":"Light scheme: made background slightly lighter, changed font color to dark gray.","package":"earendel.vim","4":"earendel.vim","src_id":"20722","5":"20722","creation_date":"1377683141","6":"1377683141"},{"0":"2188","vim_version":"7.0","1":"7.0","script_version":"2.3.5","2":"2.3.5","version_comment":"Changed background in order to reduce contrast.","3":"Changed background in order to reduce contrast.","package":"earendel.vim","4":"earendel.vim","src_id":"15040","5":"15040","creation_date":"1298024780","6":"1298024780"}]},"2187":{"script_id":"2187","0":"2187","script_name":"Latex Text Formatter","1":"Latex Text Formatter","script_type":"utility","2":"utility","summary":"This scripts makes it easier to format latex text","3":"This scripts makes it easier to format latex text","description":"The script allows to format a piece of latex text by splitting paragraphs according to latex keywords.\r\n\r\nThe main function, FormatLatexPar, formats the latex text to which the cursor belong, stopping above and below when a keyword is found, or when the vim paragraph ends. Then it moves at the end of the formatted section. If the current line is a comment, does the same thing, but searching for neighboring comments. The function is mapped to CTRL-j.\r\n\r\nNote: have a look also at a similar scrip (http:\/\/www.vim.org\/scripts\/script.php?script_id=2307).\r\n\r\nTodolist: merge multiple empty line into one.\r\n\r\nIf you have better solutions, improvements or suggestions, email me!\r\n\r\nHere is an example of text, and the resulting formatted text obtained by repeated calls of the function:\r\n\r\n<EXAMPLE BEGIN>\r\nThis is an example of the latex formatting script: the paragraphs are\r\nformatted\r\nby taking into account special latex ending keywords, as any\r\n\\begin{something}\r\n    or as,\r\n    for example\r\n\\end{something}\r\n\r\nAlso\r\nformulas\r\n$$\r\n    like this\r\n    one\r\n$$\r\nare kept separated\r\n\r\nOther separators are a line beginning\r\nwith\r\n{\r\n    as this one\r\n}   \r\nbut others can be easily added\r\n\r\nAlso,\r\ncomments\r\n% like this\r\n% or this\r\n% are merged\r\n\r\nbut not % if the comment is not at the beginning of the line\r\n% as in this case.\r\n\r\n\b\\begin{itemize}\r\n    \\item Some commands, as item, are delimiters,\r\n    but one may want\r\n    to format them with the text.\r\n    \\item These are treated differently\r\n    in the script\r\n\\end{itemize}\r\n\r\nYou can easily suit this script to your needs\r\nchanging SingleLineLatexParEndings and\r\nMultiLineLatexParEndings functions.\r\n<EXAMPLE END>\r\n\r\nis formatted, by subsequent calls, into\r\n\r\n<FORMATTED EXAMPLE BEGIN>\r\nThis is an example of the latex formatting script: the paragraphs \r\nare formatted by taking into account special latex ending keywords,\r\nas any\r\n\b\\begin{something}\r\n    or as, for example\r\n\\end{something}\r\n\r\nAlso formulas\r\n$$\r\n    like this one\r\n$$  \r\nare kept separated\r\n\r\nOther separators are a line beginning with\r\n{\r\n    as this one\r\n}   \r\nbut others can be easily added\r\n\r\nAlso, comments\r\n% like this or this are merged\r\n\r\nbut not % if the comment is not at the beginning of the line\r\n% as in this case.\r\n\r\n\\b\begin{itemize}\r\n    \\item Some commands, as item, are delimiters, but one may want\r\n    to format them with the text.\r\n    \\item These are treated differently in the script\r\n\\end{itemize}\r\n\r\nYou can easily suit this script to your needs changing\r\nSingleLineLatexParEndings and MultiLineLatexParEndings functions.\r\n<FORMATTED EXAMPLE END>","4":"The script allows to format a piece of latex text by splitting paragraphs according to latex keywords.\r\n\r\nThe main function, FormatLatexPar, formats the latex text to which the cursor belong, stopping above and below when a keyword is found, or when the vim paragraph ends. Then it moves at the end of the formatted section. If the current line is a comment, does the same thing, but searching for neighboring comments. The function is mapped to CTRL-j.\r\n\r\nNote: have a look also at a similar scrip (http:\/\/www.vim.org\/scripts\/script.php?script_id=2307).\r\n\r\nTodolist: merge multiple empty line into one.\r\n\r\nIf you have better solutions, improvements or suggestions, email me!\r\n\r\nHere is an example of text, and the resulting formatted text obtained by repeated calls of the function:\r\n\r\n<EXAMPLE BEGIN>\r\nThis is an example of the latex formatting script: the paragraphs are\r\nformatted\r\nby taking into account special latex ending keywords, as any\r\n\\begin{something}\r\n    or as,\r\n    for example\r\n\\end{something}\r\n\r\nAlso\r\nformulas\r\n$$\r\n    like this\r\n    one\r\n$$\r\nare kept separated\r\n\r\nOther separators are a line beginning\r\nwith\r\n{\r\n    as this one\r\n}   \r\nbut others can be easily added\r\n\r\nAlso,\r\ncomments\r\n% like this\r\n% or this\r\n% are merged\r\n\r\nbut not % if the comment is not at the beginning of the line\r\n% as in this case.\r\n\r\n\b\\begin{itemize}\r\n    \\item Some commands, as item, are delimiters,\r\n    but one may want\r\n    to format them with the text.\r\n    \\item These are treated differently\r\n    in the script\r\n\\end{itemize}\r\n\r\nYou can easily suit this script to your needs\r\nchanging SingleLineLatexParEndings and\r\nMultiLineLatexParEndings functions.\r\n<EXAMPLE END>\r\n\r\nis formatted, by subsequent calls, into\r\n\r\n<FORMATTED EXAMPLE BEGIN>\r\nThis is an example of the latex formatting script: the paragraphs \r\nare formatted by taking into account special latex ending keywords,\r\nas any\r\n\b\\begin{something}\r\n    or as, for example\r\n\\end{something}\r\n\r\nAlso formulas\r\n$$\r\n    like this one\r\n$$  \r\nare kept separated\r\n\r\nOther separators are a line beginning with\r\n{\r\n    as this one\r\n}   \r\nbut others can be easily added\r\n\r\nAlso, comments\r\n% like this or this are merged\r\n\r\nbut not % if the comment is not at the beginning of the line\r\n% as in this case.\r\n\r\n\\b\begin{itemize}\r\n    \\item Some commands, as item, are delimiters, but one may want\r\n    to format them with the text.\r\n    \\item These are treated differently in the script\r\n\\end{itemize}\r\n\r\nYou can easily suit this script to your needs changing\r\nSingleLineLatexParEndings and MultiLineLatexParEndings functions.\r\n<FORMATTED EXAMPLE END>","install_details":"Copy in your .vim\/plugin directory. If CTRL-j is already mapped, change the mapping for FormatLatexPar.","5":"Copy in your .vim\/plugin directory. If CTRL-j is already mapped, change the mapping for FormatLatexPar.","first_name":"Sandro","6":"Sandro","last_name":"Bosio","7":"Bosio","releases":[{"0":"2187","vim_version":"7.0","1":"7.0","script_version":"2.5","2":"2.5","version_comment":"Corrected a bug closing the open tab when formatting a comment","3":"Corrected a bug closing the open tab when formatting a comment","package":"LatexParFormat.vim","4":"LatexParFormat.vim","src_id":"16894","5":"16894","creation_date":"1321554203","6":"1321554203"},{"0":"2187","vim_version":"7.0","1":"7.0","script_version":"2.4","2":"2.4","version_comment":"Corrected a bug merging comments with standard text","3":"Corrected a bug merging comments with standard text","package":"LatexParFormat.vim","4":"LatexParFormat.vim","src_id":"16893","5":"16893","creation_date":"1321552146","6":"1321552146"},{"0":"2187","vim_version":"7.0","1":"7.0","script_version":"2.3","2":"2.3","version_comment":"In this version the comments are formatted even when the comment character is not at the beginning of a line, that is, indented multi-line comments get properly formatted as well. \r\n\r\nThe comment string is parametrized according to the filetype, so that e.g. formatting works also for c\/c++ comments (very few languages supported). If the filetype is not recognized, the comment is set as the tex comment %.\r\n\r\nThe script also contains a simple but useful Comment command that toggles the comments on a range (again, for few languages only). \r\n\r\nRemove or personalize the maps to FormatLatexPar and ToggleComment as desired.","3":"In this version the comments are formatted even when the comment character is not at the beginning of a line, that is, indented multi-line comments get properly formatted as well. \r\n\r\nThe comment string is parametrized according to the filetype, so that e.g. formatting works also for c\/c++ comments (very few languages supported). If the filetype is not recognized, the comment is set as the tex comment %.\r\n\r\nThe script also contains a simple but useful Comment command that toggles the comments on a range (again, for few languages only). \r\n\r\nRemove or personalize the maps to FormatLatexPar and ToggleComment as desired.","package":"LatexParFormat.vim","4":"LatexParFormat.vim","src_id":"16891","5":"16891","creation_date":"1321541283","6":"1321541283"},{"0":"2187","vim_version":"7.0","1":"7.0","script_version":"2.2","2":"2.2","version_comment":"Corrected a bug possibly splitting a comment at the end of a line, making it normal text.","3":"Corrected a bug possibly splitting a comment at the end of a line, making it normal text.","package":"LatexParFormat.vim","4":"LatexParFormat.vim","src_id":"9487","5":"9487","creation_date":"1226419491","6":"1226419491"},{"0":"2187","vim_version":"7.0","1":"7.0","script_version":"2.1","2":"2.1","version_comment":"Resolved problem with undos jumping at the beginning of the file. Better implementation (i.e., more readable) of some functions.","3":"Resolved problem with undos jumping at the beginning of the file. Better implementation (i.e., more readable) of some functions.","package":"LatexParFormat.vim","4":"LatexParFormat.vim","src_id":"9282","5":"9282","creation_date":"1222347991","6":"1222347991"},{"0":"2187","vim_version":"7.0","1":"7.0","script_version":"2.0","2":"2.0","version_comment":"Basic improvements and bug removals: 1) It distinguish between paragraph separating commands (that do not have to be formatted with the text) and paragraph beginning commands (that will be formatted together with the paragraph they begin). 2) Works also on commented text, for any level of comments. The functions are now much more readable, too.","3":"Basic improvements and bug removals: 1) It distinguish between paragraph separating commands (that do not have to be formatted with the text) and paragraph beginning commands (that will be formatted together with the paragraph they begin). 2) Works also on commented text, for any level of comments. The functions are now much more readable, too.","package":"LatexParFormat.vim","4":"LatexParFormat.vim","src_id":"9266","5":"9266","creation_date":"1222090614","6":"1222090614"},{"0":"2187","vim_version":"6.0","1":"6.0","script_version":"1.3","2":"1.3","version_comment":"Added some paragraph delimiters, learned some vim scripting, improved readability for some functions. Now it works also for \\item, and can be extended to any paragraph begin that one wants to be inlined with the text.","3":"Added some paragraph delimiters, learned some vim scripting, improved readability for some functions. Now it works also for \\item, and can be extended to any paragraph begin that one wants to be inlined with the text.","package":"LatexParFormat.vim","4":"LatexParFormat.vim","src_id":"9237","5":"9237","creation_date":"1220952193","6":"1220952193"},{"0":"2187","vim_version":"6.0","1":"6.0","script_version":"1.2","2":"1.2","version_comment":"Some changes to the definition of paragraph endings (see the comments).","3":"Some changes to the definition of paragraph endings (see the comments).","package":"LatexParFormat.vim","4":"LatexParFormat.vim","src_id":"8538","5":"8538","creation_date":"1207721852","6":"1207721852"},{"0":"2187","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"LatexParFormat.vim","4":"LatexParFormat.vim","src_id":"8438","5":"8438","creation_date":"1205323531","6":"1205323531"}]},"2186":{"script_id":"2186","0":"2186","script_name":"pig.vim","1":"pig.vim","script_type":"syntax","2":"syntax","summary":"Pig language syntax highlighting","3":"Pig language syntax highlighting","description":"\r\nThis plugin is in active development on github: https:\/\/github.com\/motus\/pig.vim\r\n\r\nPlease use github to send pull requests and report issues.\r\n","4":"\r\nThis plugin is in active development on github: https:\/\/github.com\/motus\/pig.vim\r\n\r\nPlease use github to send pull requests and report issues.\r\n","install_details":"1) copy pig.vim file into your ~\/.vim\/syntax\/ directory;\r\n\r\n2) add the following three lines to your ~\/.vimrc file:\r\n\r\naugroup filetypedetect\r\n  au BufNewFile,BufRead *.pig set filetype=pig syntax=pig\r\naugroup END\r\n","5":"1) copy pig.vim file into your ~\/.vim\/syntax\/ directory;\r\n\r\n2) add the following three lines to your ~\/.vimrc file:\r\n\r\naugroup filetypedetect\r\n  au BufNewFile,BufRead *.pig set filetype=pig syntax=pig\r\naugroup END\r\n","first_name":"Sergiy","6":"Sergiy","last_name":"Matusevych","7":"Matusevych","releases":[{"0":"2186","vim_version":"7.0","1":"7.0","script_version":"0.12","2":"0.12","version_comment":"Support for Pig up to 0.12","3":"Support for Pig up to 0.12","package":"pig.vim","4":"pig.vim","src_id":"22064","5":"22064","creation_date":"1403207646","6":"1403207646"}]},"2185":{"script_id":"2185","0":"2185","script_name":"git:file.vim","1":"git:file.vim","script_type":"utility","2":"utility","summary":"open any version of a file in git","3":"open any version of a file in git","description":"Allows for opening <branch>:<file> patters using a git repo.\r\n\r\nYou can open a file from the shell:\r\n\r\n    vim HEAD~10:filename\r\n\r\nor from inside vim:\r\n\r\n    :e branch:filename\r\n    :sp tag:filename\r\n\r\nyou could even check what changed between the current edits and another revision:\r\n\r\n    :diffthis\r\n    :vsp HEAD:%\r\n    :diffthis\r\n\r\nbut that's what gitdiff.vim (vimscript#1846) is for.","4":"Allows for opening <branch>:<file> patters using a git repo.\r\n\r\nYou can open a file from the shell:\r\n\r\n    vim HEAD~10:filename\r\n\r\nor from inside vim:\r\n\r\n    :e branch:filename\r\n    :sp tag:filename\r\n\r\nyou could even check what changed between the current edits and another revision:\r\n\r\n    :diffthis\r\n    :vsp HEAD:%\r\n    :diffthis\r\n\r\nbut that's what gitdiff.vim (vimscript#1846) is for.","install_details":"copy to ~\/.vim\/plugins\/git:file.vim","5":"copy to ~\/.vim\/plugins\/git:file.vim","first_name":"Bart","6":"Bart","last_name":"Trojanowski","7":"Trojanowski","releases":[{"0":"2185","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"git:file.vim","4":"git:file.vim","src_id":"8416","5":"8416","creation_date":"1204884519","6":"1204884519"}]},"2184":{"script_id":"2184","0":"2184","script_name":"file:line","1":"file:line","script_type":"utility","2":"utility","summary":"Allows you to open file:line and it does the right thing :-)","3":"Allows you to open file:line and it does the right thing :-)","description":"When you open a file:line, for instance when coping and pasting from an error from your compiler vim tries to open a file with a colon in its name. With this little script in your plugins folder if the stuff after the colon is a number and a file exists with the name especified before the colon vim will open this file and take you to the line you wished in the first place.\r\n\r\nThis script is licensed with GPLv3 and you can contribute to it on github at https:\/\/github.com\/bogado\/file-line .","4":"When you open a file:line, for instance when coping and pasting from an error from your compiler vim tries to open a file with a colon in its name. With this little script in your plugins folder if the stuff after the colon is a number and a file exists with the name especified before the colon vim will open this file and take you to the line you wished in the first place.\r\n\r\nThis script is licensed with GPLv3 and you can contribute to it on github at https:\/\/github.com\/bogado\/file-line .","install_details":"Just copy the file into your plugins path ($HOME\/.vim\/plugin under unixes).","5":"Just copy the file into your plugins path ($HOME\/.vim\/plugin under unixes).","first_name":"Victor","6":"Victor","last_name":"Bogado da Silva Lins","7":"Bogado da Silva Lins","releases":[{"0":"2184","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"- better support for windows\r\n- allows copy and paste from grep results (making the line parameter optional)\r\n- center the cursor line (thanks Dmitri Louchtchenko)\r\n- better fold management (thanks Dmitri Louchtchenko)","3":"- better support for windows\r\n- allows copy and paste from grep results (making the line parameter optional)\r\n- center the cursor line (thanks Dmitri Louchtchenko)\r\n- better fold management (thanks Dmitri Louchtchenko)","package":"file_line.vim","4":"file_line.vim","src_id":"17417","5":"17417","creation_date":"1328795164","6":"1328795164"},{"0":"2184","vim_version":"7.0","1":"7.0","script_version":"0.6","2":"0.6","version_comment":"Added some changes made by Ingo Karkat that made the whole thing more robust.","3":"Added some changes made by Ingo Karkat that made the whole thing more robust.","package":"file:line.vim","4":"file:line.vim","src_id":"14875","5":"14875","creation_date":"1296056766","6":"1296056766"},{"0":"2184","vim_version":"7.0","1":"7.0","script_version":"0.5","2":"0.5","version_comment":"following Dr. David Alan Gilbert suggestion of allowing file:line:column format.","3":"following Dr. David Alan Gilbert suggestion of allowing file:line:column format.","package":"file:line.vim","4":"file:line.vim","src_id":"14792","5":"14792","creation_date":"1295462110","6":"1295462110"},{"0":"2184","vim_version":"6.0","1":"6.0","script_version":"0.4","2":"0.4","version_comment":"Closes the buffer for the nonexistent file \"file:line\" after it opens the correct file. ","3":"Closes the buffer for the nonexistent file \"file:line\" after it opens the correct file. ","package":"file:line.vim","4":"file:line.vim","src_id":"9148","5":"9148","creation_date":"1219072682","6":"1219072682"},{"0":"2184","vim_version":"6.0","1":"6.0","script_version":"0.3","2":"0.3","version_comment":"Opens eventual folds on the desired lines. Changes made by Rodolfo Borges (user barrett9h)","3":"Opens eventual folds on the desired lines. Changes made by Rodolfo Borges (user barrett9h)","package":"file:line.vim","4":"file:line.vim","src_id":"8433","5":"8433","creation_date":"1205224600","6":"1205224600"},{"0":"2184","vim_version":"6.0","1":"6.0","script_version":"0.2","2":"0.2","version_comment":"This version uses a simpler way to open the desired file and also uses the \"nested\" option so the loaded file can be correctly detected by vim.","3":"This version uses a simpler way to open the desired file and also uses the \"nested\" option so the loaded file can be correctly detected by vim.","package":"file:line.vim","4":"file:line.vim","src_id":"8417","5":"8417","creation_date":"1204885849","6":"1204885849"},{"0":"2184","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"file:line.vim","4":"file:line.vim","src_id":"8413","5":"8413","creation_date":"1204875557","6":"1204875557"}]},"2183":{"script_id":"2183","0":"2183","script_name":"smoothPageScroll.vim","1":"smoothPageScroll.vim","script_type":"utility","2":"utility","summary":"smooth page scroll","3":"smooth page scroll","description":"Yet another smooth page scroll implementation.\r\nI found scrolling the number of winheight() is not always correct, because the file could have wrapped lines. Let's say if your window height is 40, but you only see 35 actual lines because you have 5 wrapped lines. Then by scrolling the number of winheight(), 5 lines would be over-scrolled. This script won't skip the extra lines for having wrapped lines.\r\n\r\nThis script also emualtes one of VIM's normal <PageDown> or <PageUp> behaviors: which is to display first or last 2 lines from the previous screen after scrolling, unless it reaches first or last line, or the current window is showing 3 lines or less. \r\n\r\nSee other implementation - vimscript #1601, :help scroll-smooth","4":"Yet another smooth page scroll implementation.\r\nI found scrolling the number of winheight() is not always correct, because the file could have wrapped lines. Let's say if your window height is 40, but you only see 35 actual lines because you have 5 wrapped lines. Then by scrolling the number of winheight(), 5 lines would be over-scrolled. This script won't skip the extra lines for having wrapped lines.\r\n\r\nThis script also emualtes one of VIM's normal <PageDown> or <PageUp> behaviors: which is to display first or last 2 lines from the previous screen after scrolling, unless it reaches first or last line, or the current window is showing 3 lines or less. \r\n\r\nSee other implementation - vimscript #1601, :help scroll-smooth","install_details":"Install:\r\nCopy this script in your plugin directory\r\n\r\nUsage:\r\n1) call them directly\r\n\t:call SmoothPageScrollDown() to scroll page down \r\n\t:call SmoothPageScrollUp() to scroll page up\r\n\r\n2) or remap <PageDown> and <PageUp>\r\n\tmap <PageDown> :call SmoothPageScrollDown()<CR>\r\n\tmap <PageUp>   :call SmoothPageScrollUp()<CR>\r\n\r\nPersonally, I remapped <Space> and <S-Space> keys, since <Space> in non-insert mode is not that useful (just move the cursor one position right). And many programs such as web browsers or acrobat reader use space key to scroll page. \r\n\tmap <Space>   :call SmoothPageScrollDown()<CR>\r\n\tmap <S-Space> :call SmoothPageScrollUp()<CR>\r\n\r\nBut remapping <S-Space> may not work on certain console or platform. So you might have to find another candidate, such as <M-Space>, <C-Space> or something else.\r\n\r\nIf the scrolling speed is too fast, you can delay scrolling speed more by adding g:smooth_page_scroll_delay in your [._]vimrc. Following line will delay extra 5 milliseconds per each line.\r\n\r\nlet g:smooth_page_scroll_delay = 5","5":"Install:\r\nCopy this script in your plugin directory\r\n\r\nUsage:\r\n1) call them directly\r\n\t:call SmoothPageScrollDown() to scroll page down \r\n\t:call SmoothPageScrollUp() to scroll page up\r\n\r\n2) or remap <PageDown> and <PageUp>\r\n\tmap <PageDown> :call SmoothPageScrollDown()<CR>\r\n\tmap <PageUp>   :call SmoothPageScrollUp()<CR>\r\n\r\nPersonally, I remapped <Space> and <S-Space> keys, since <Space> in non-insert mode is not that useful (just move the cursor one position right). And many programs such as web browsers or acrobat reader use space key to scroll page. \r\n\tmap <Space>   :call SmoothPageScrollDown()<CR>\r\n\tmap <S-Space> :call SmoothPageScrollUp()<CR>\r\n\r\nBut remapping <S-Space> may not work on certain console or platform. So you might have to find another candidate, such as <M-Space>, <C-Space> or something else.\r\n\r\nIf the scrolling speed is too fast, you can delay scrolling speed more by adding g:smooth_page_scroll_delay in your [._]vimrc. Following line will delay extra 5 milliseconds per each line.\r\n\r\nlet g:smooth_page_scroll_delay = 5","first_name":"Hosup","6":"Hosup","last_name":"Chung","7":"Chung","releases":[{"0":"2183","vim_version":"6.0","1":"6.0","script_version":"0.20","2":"0.20","version_comment":"added a function to delay scroll speed","3":"added a function to delay scroll speed","package":"smoothPageScroll.vim","4":"smoothPageScroll.vim","src_id":"8432","5":"8432","creation_date":"1205122468","6":"1205122468"},{"0":"2183","vim_version":"6.0","1":"6.0","script_version":"0.13","2":"0.13","version_comment":"temporary fix for infinite scrolling attempt on folded line","3":"temporary fix for infinite scrolling attempt on folded line","package":"smoothPageScroll.vim","4":"smoothPageScroll.vim","src_id":"8412","5":"8412","creation_date":"1204873549","6":"1204873549"},{"0":"2183","vim_version":"6.0","1":"6.0","script_version":"0.12","2":"0.12","version_comment":"fixed problem of not scrolling at long single line","3":"fixed problem of not scrolling at long single line","package":"smoothPageScroll.vim","4":"smoothPageScroll.vim","src_id":"8410","5":"8410","creation_date":"1204869285","6":"1204869285"},{"0":"2183","vim_version":"6.0","1":"6.0","script_version":"0.11","2":"0.11","version_comment":"Smooth page scroll","3":"Smooth page scroll","package":"smoothPageScroll.vim","4":"smoothPageScroll.vim","src_id":"8405","5":"8405","creation_date":"1204795641","6":"1204795641"}]},"2182":{"script_id":"2182","0":"2182","script_name":"vimlatex","1":"vimlatex","script_type":"utility","2":"utility","summary":"Sanitizes LaTeX error messages for Vim-LaTeX.","3":"Sanitizes LaTeX error messages for Vim-LaTeX.","description":"# vimlatex: Script wrapper for TeX\/LaTeX\/etc. that sanitizes output to\r\n#           be compatible with Vim-LaTeX's errorformat. Prevents Vim\r\n#           from opening the wrong file after some errors.\r\n#\r\n#           This script is inspired by\r\n#\r\n# http:\/\/hermitte.free.fr\/vim\/ressources\/vimfiles\/compiler\/vim-tex_sh.html\r\n#\r\n# and\r\n#\r\n# http:\/\/www.unix.com\/shell-programming-scripting\/20218-pipelining.html\r\n#\r\n# Original author: Ted Pavlic\r\n#                  ted@tedpavlic.com\r\n#                  http:\/\/www.tedpavlic.com\/\r\n#\r\n# Mercurial source code repository for original author's version:\r\n#                  http:\/\/hg.tedpavlic.com\/vimlatex\/\r\n#\r\n# Copyright (c) 2008 Theodore P. Pavlic under MIT license (http:\/\/www.opensource.org\/licenses\/mit-license.php)\r\n#\r\n# Usage: vimlatex %command [%arguments]\r\n#\r\n#        where the command line:\r\n#\r\n#        %command %arguments\r\n#\r\n#        would texify as normal. In other words, the \"vimlatex\" command\r\n#        can simply be added before a given working command line.\r\n#\r\n# For more information (and history), see:\r\n#\r\n# http:\/\/phaseportrait.blogspot.com\/2008\/03\/fixing-vim-latex-compiler-error.html\r\n#","4":"# vimlatex: Script wrapper for TeX\/LaTeX\/etc. that sanitizes output to\r\n#           be compatible with Vim-LaTeX's errorformat. Prevents Vim\r\n#           from opening the wrong file after some errors.\r\n#\r\n#           This script is inspired by\r\n#\r\n# http:\/\/hermitte.free.fr\/vim\/ressources\/vimfiles\/compiler\/vim-tex_sh.html\r\n#\r\n# and\r\n#\r\n# http:\/\/www.unix.com\/shell-programming-scripting\/20218-pipelining.html\r\n#\r\n# Original author: Ted Pavlic\r\n#                  ted@tedpavlic.com\r\n#                  http:\/\/www.tedpavlic.com\/\r\n#\r\n# Mercurial source code repository for original author's version:\r\n#                  http:\/\/hg.tedpavlic.com\/vimlatex\/\r\n#\r\n# Copyright (c) 2008 Theodore P. Pavlic under MIT license (http:\/\/www.opensource.org\/licenses\/mit-license.php)\r\n#\r\n# Usage: vimlatex %command [%arguments]\r\n#\r\n#        where the command line:\r\n#\r\n#        %command %arguments\r\n#\r\n#        would texify as normal. In other words, the \"vimlatex\" command\r\n#        can simply be added before a given working command line.\r\n#\r\n# For more information (and history), see:\r\n#\r\n# http:\/\/phaseportrait.blogspot.com\/2008\/03\/fixing-vim-latex-compiler-error.html\r\n#","install_details":"Place script somewhere in PATH, like:\r\n\r\n\/usr\/local\/bin\/vimlatex\r\n\r\nand make it executable, like:\r\n\r\nchmod 0755 \/usr\/local\/bin\/vimlatex\r\n\r\nThen, add \"vimlatex\" before any tex or latex build command lines. \"vimlatex\" is a wrapper that processes the output while maintaining the same return code. For example:\r\n\r\nlatex myfile.tex\r\n\r\nand\r\n\r\nvimlatex latex myfile.tex\r\n\r\nboth run \"latex\" on \"myfile.tex\", but the output from the second line will have error messages that should all make sense to Vim-LaTeX's error format.","5":"Place script somewhere in PATH, like:\r\n\r\n\/usr\/local\/bin\/vimlatex\r\n\r\nand make it executable, like:\r\n\r\nchmod 0755 \/usr\/local\/bin\/vimlatex\r\n\r\nThen, add \"vimlatex\" before any tex or latex build command lines. \"vimlatex\" is a wrapper that processes the output while maintaining the same return code. For example:\r\n\r\nlatex myfile.tex\r\n\r\nand\r\n\r\nvimlatex latex myfile.tex\r\n\r\nboth run \"latex\" on \"myfile.tex\", but the output from the second line will have error messages that should all make sense to Vim-LaTeX's error format.","first_name":"Ted","6":"Ted","last_name":"Pavlic","7":"Pavlic","releases":[{"0":"2182","vim_version":"6.0","1":"6.0","script_version":"1.06","2":"1.06","version_comment":"Improved handling of log lines with (...)...) sections.","3":"Improved handling of log lines with (...)...) sections.","package":"vimlatex","4":"vimlatex","src_id":"8914","5":"8914","creation_date":"1215592546","6":"1215592546"},{"0":"2182","vim_version":"6.0","1":"6.0","script_version":"1.05","2":"1.05","version_comment":"Added link to Mercurial source code repository (no changes to code).","3":"Added link to Mercurial source code repository (no changes to code).","package":"vimlatex","4":"vimlatex","src_id":"8820","5":"8820","creation_date":"1213722162","6":"1213722162"},{"0":"2182","vim_version":"6.0","1":"6.0","script_version":"1.04","2":"1.04","version_comment":"Made MIT license explicit.","3":"Made MIT license explicit.","package":"vimlatex","4":"vimlatex","src_id":"8737","5":"8737","creation_date":"1211883972","6":"1211883972"},{"0":"2182","vim_version":"6.0","1":"6.0","script_version":"1.03","2":"1.03","version_comment":"First attempt to preventing breaking lines with (..) on them.","3":"First attempt to preventing breaking lines with (..) on them.","package":"vimlatex","4":"vimlatex","src_id":"8736","5":"8736","creation_date":"1211878851","6":"1211878851"},{"0":"2182","vim_version":"6.0","1":"6.0","script_version":"1.02","2":"1.02","version_comment":"Improved portability (particularly with OLD NON-GNU sed provided by OS\/X).","3":"Improved portability (particularly with OLD NON-GNU sed provided by OS\/X).","package":"vimlatex","4":"vimlatex","src_id":"8420","5":"8420","creation_date":"1204898011","6":"1204898011"},{"0":"2182","vim_version":"6.0","1":"6.0","script_version":"1.01","2":"1.01","version_comment":"Improved sed script by combining three sed calls into one (Christian Ebert suggestion).","3":"Improved sed script by combining three sed calls into one (Christian Ebert suggestion).","package":"vimlatex","4":"vimlatex","src_id":"8414","5":"8414","creation_date":"1204883242","6":"1204883242"},{"0":"2182","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial revision.","3":"Initial revision.","package":"vimlatex","4":"vimlatex","src_id":"8401","5":"8401","creation_date":"1204790298","6":"1204790298"}]},"2181":{"script_id":"2181","0":"2181","script_name":"reliable","1":"reliable","script_type":"color scheme","2":"color scheme","summary":"A futuristic colorscheme with a bright, clean look","3":"A futuristic colorscheme with a bright, clean look","description":"Created with ColorSchemeEditor vimscript #2180\r\nSee also ColorSchemeMenuMaker vimscript #2004","4":"Created with ColorSchemeEditor vimscript #2180\r\nSee also ColorSchemeMenuMaker vimscript #2004","install_details":"Copy to $HOME\/.vim\/colors","5":"Copy to $HOME\/.vim\/colors","first_name":"erik","6":"erik","last_name":"falor","7":"falor","releases":[{"0":"2181","vim_version":"6.0","1":"6.0","script_version":"1.0.2","2":"1.0.2","version_comment":"Changed Type highlight group to display bold","3":"Changed Type highlight group to display bold","package":"reliable.vim","4":"reliable.vim","src_id":"8415","5":"8415","creation_date":"1204883546","6":"1204883546"},{"0":"2181","vim_version":"6.0","1":"6.0","script_version":"1.0.1","2":"1.0.1","version_comment":"Fixed an issue generated color schemes have when loaded into Vim versions < 700","3":"Fixed an issue generated color schemes have when loaded into Vim versions < 700","package":"reliable.vim","4":"reliable.vim","src_id":"8393","5":"8393","creation_date":"1204703957","6":"1204703957"}]},"2180":{"script_id":"2180","0":"2180","script_name":"ColorSchemeEditor","1":"ColorSchemeEditor","script_type":"utility","2":"utility","summary":"PyGTK GUI to more easily create colorschemes (keywords: color scheme editor)","3":"PyGTK GUI to more easily create colorschemes (keywords: color scheme editor)","description":"This plugin provides a GUI tool which simplifies creating\/editing Vim\r\ncolorscheme files.  It consists of a Vim plugin as well as a Python program,\r\nand utilizes Vim's command server interface |clientserver| for communications.\r\n\r\nNew in version 1.1:\r\nThe list of highlight groups now displays a swatch of the current foreground\/\r\nbackground colors.  You can see right away which colors are used for each\r\nhighlight group.  \r\nAfter getting some negative feedback over my last few colorscheme contributions,\r\nI have added a readability column to this tool that analyses the color contrast \r\nbetween foreground and background colors.  I hope that this will lead to \r\ncolorschemes that are easy on the eyes for all Vim users.\r\n\r\nSee the screenshots:\r\n\r\nhttp:\/\/i49.servimg.com\/u\/f49\/12\/09\/64\/12\/metada10.jpg\r\nhttp:\/\/i49.servimg.com\/u\/f49\/12\/09\/64\/12\/colors10.png\r\n\r\nThe goals that I hope to achieve through this plugin are to improve the\r\nquality of existing colorschemes by allowing the authors the freedom to create\r\ncolorschemes in a natural WYSIWYG fashion.  Immediate visual feedback lets the\r\nauthor quickly assess the effects of their changes, and allows them to easily\r\nchoose just the right color for a highlight element.  By displaying all of the\r\n\"preferred\" highlight groups in a treeview, colorscheme authors can ensure\r\nthat all of the important highlights have been changed to fit in with the\r\noverall scheme.  Users of colorschemes can use this plugin to tweak their\r\nfavorite colorschemes more to their liking.\r\n\r\nColorschemes generated with this plugin are backwards-compatible with earlier\r\nversions of Gvim that do not use such highlight groups as CursorLine or Pmenu.\r\n\r\nYour palette of custom colors is saved in the colorscheme file, so that your\r\nchoices persist between editing sessions.  This helps you maintain\r\na consistent look-and-feel while you are in the process of creating the\r\ncolorscheme.  Other metadata related to the colorscheme, such as licensing\r\ninformation and your contact information are accessible from within the editor\r\nas well.\r\n\r\nThis plugin makes a nice compliment to my earlier work, ColorSchemeMenuMaker.\r\n    http:\/\/www.vim.org\/scripts\/script.php?script_id=2004\r\n\r\nIf you have already installed ColorSchemeMenuMaker, the menu entry for\r\nColorSchemeEditor will appear at the bottom of the \"ColorSchemes\" menu item.\r\nAdditionally, you may invoke it via the :ColorSchemeEditor command.\r\n\r\nSend bugs, suggestions, flames, etc. to NOSPAMewfalor@NOSPAMgmail.com - NOSPAM.\r\n\r\n","4":"This plugin provides a GUI tool which simplifies creating\/editing Vim\r\ncolorscheme files.  It consists of a Vim plugin as well as a Python program,\r\nand utilizes Vim's command server interface |clientserver| for communications.\r\n\r\nNew in version 1.1:\r\nThe list of highlight groups now displays a swatch of the current foreground\/\r\nbackground colors.  You can see right away which colors are used for each\r\nhighlight group.  \r\nAfter getting some negative feedback over my last few colorscheme contributions,\r\nI have added a readability column to this tool that analyses the color contrast \r\nbetween foreground and background colors.  I hope that this will lead to \r\ncolorschemes that are easy on the eyes for all Vim users.\r\n\r\nSee the screenshots:\r\n\r\nhttp:\/\/i49.servimg.com\/u\/f49\/12\/09\/64\/12\/metada10.jpg\r\nhttp:\/\/i49.servimg.com\/u\/f49\/12\/09\/64\/12\/colors10.png\r\n\r\nThe goals that I hope to achieve through this plugin are to improve the\r\nquality of existing colorschemes by allowing the authors the freedom to create\r\ncolorschemes in a natural WYSIWYG fashion.  Immediate visual feedback lets the\r\nauthor quickly assess the effects of their changes, and allows them to easily\r\nchoose just the right color for a highlight element.  By displaying all of the\r\n\"preferred\" highlight groups in a treeview, colorscheme authors can ensure\r\nthat all of the important highlights have been changed to fit in with the\r\noverall scheme.  Users of colorschemes can use this plugin to tweak their\r\nfavorite colorschemes more to their liking.\r\n\r\nColorschemes generated with this plugin are backwards-compatible with earlier\r\nversions of Gvim that do not use such highlight groups as CursorLine or Pmenu.\r\n\r\nYour palette of custom colors is saved in the colorscheme file, so that your\r\nchoices persist between editing sessions.  This helps you maintain\r\na consistent look-and-feel while you are in the process of creating the\r\ncolorscheme.  Other metadata related to the colorscheme, such as licensing\r\ninformation and your contact information are accessible from within the editor\r\nas well.\r\n\r\nThis plugin makes a nice compliment to my earlier work, ColorSchemeMenuMaker.\r\n    http:\/\/www.vim.org\/scripts\/script.php?script_id=2004\r\n\r\nIf you have already installed ColorSchemeMenuMaker, the menu entry for\r\nColorSchemeEditor will appear at the bottom of the \"ColorSchemes\" menu item.\r\nAdditionally, you may invoke it via the :ColorSchemeEditor command.\r\n\r\nSend bugs, suggestions, flames, etc. to NOSPAMewfalor@NOSPAMgmail.com - NOSPAM.\r\n\r\n","install_details":"ColorSchemeEditor requires that your version of Vim is compiled with the |gui|\r\nand |clientserver| features.\r\n\r\nThe GUI editor is written with Python, with PyGTK and Glade comprising the\r\ngraphical interface.\r\n\r\nIf you want to use this on Un*x systems, make sure you have those three\r\npackages and their dependencies installed.\r\n\r\nMore specifically, Gentoo users will need at least the following packages:\r\ndev-lang\/python x11-libs\/gtk+ gnome-base\/libglade dev-python\/pygtk\r\n\r\nUbuntu users will need at least these packages: libglade2-0, python, python-gtk2, python-glade2\r\n\r\n\r\nWindows users will need at least the following software packages:\r\nPython       http:\/\/www.python.org\/download\/\r\nPyGTK        http:\/\/www.pygtk.org\/downloads.html\r\nPygobject    See above\r\nPycairo      See above\r\ngladewin32   http:\/\/gladewin32.sourceforge.net\/modules\/news\/\r\n\r\nOnce the requisite software packages are installed, simply unzip the plugin\r\npackage into your ~\/.vim (or ~\/vimfiles) directory.  The\r\nColorSchemeEditor.{py,vim,glade} files should all wind up in the plugin\r\ndirectory.\r\n\r\nAny new instances of Gvim will now show the 'ColorSchemes' menu, and are ready\r\nto go.  Within already running instances of Gvim, you may execute\r\n\r\n    :runtime plugin\/ColorSchemeEditor.vim \r\n\r\nto load the plugin.\r\n\r\nAlso, you should run helptags: \r\n\r\n    :helptags $HOME\/.vim\/doc\r\n","5":"ColorSchemeEditor requires that your version of Vim is compiled with the |gui|\r\nand |clientserver| features.\r\n\r\nThe GUI editor is written with Python, with PyGTK and Glade comprising the\r\ngraphical interface.\r\n\r\nIf you want to use this on Un*x systems, make sure you have those three\r\npackages and their dependencies installed.\r\n\r\nMore specifically, Gentoo users will need at least the following packages:\r\ndev-lang\/python x11-libs\/gtk+ gnome-base\/libglade dev-python\/pygtk\r\n\r\nUbuntu users will need at least these packages: libglade2-0, python, python-gtk2, python-glade2\r\n\r\n\r\nWindows users will need at least the following software packages:\r\nPython       http:\/\/www.python.org\/download\/\r\nPyGTK        http:\/\/www.pygtk.org\/downloads.html\r\nPygobject    See above\r\nPycairo      See above\r\ngladewin32   http:\/\/gladewin32.sourceforge.net\/modules\/news\/\r\n\r\nOnce the requisite software packages are installed, simply unzip the plugin\r\npackage into your ~\/.vim (or ~\/vimfiles) directory.  The\r\nColorSchemeEditor.{py,vim,glade} files should all wind up in the plugin\r\ndirectory.\r\n\r\nAny new instances of Gvim will now show the 'ColorSchemes' menu, and are ready\r\nto go.  Within already running instances of Gvim, you may execute\r\n\r\n    :runtime plugin\/ColorSchemeEditor.vim \r\n\r\nto load the plugin.\r\n\r\nAlso, you should run helptags: \r\n\r\n    :helptags $HOME\/.vim\/doc\r\n","first_name":"erik","6":"erik","last_name":"falor","7":"falor","releases":[{"0":"2180","vim_version":"7.0","1":"7.0","script_version":"1.2.3","2":"1.2.3","version_comment":"Parameterize name of the Python executable.\r\nAdjust the rgb.txt search path.","3":"Parameterize name of the Python executable.\r\nAdjust the rgb.txt search path.","package":"ColorSchemeEditor.zip","4":"ColorSchemeEditor.zip","src_id":"17641","5":"17641","creation_date":"1332453600","6":"1332453600"}]},"2179":{"script_id":"2179","0":"2179","script_name":"Source Explorer (SrcExpl)","1":"Source Explorer (SrcExpl)","script_type":"utility","2":"utility","summary":"A Source code Explorer for viewing definition(s) and contextual info","3":"A Source code Explorer for viewing definition(s) and contextual info","description":"[GitHub]\r\n\r\nThe latest dev version of Source Explorer and screenshots can be downloaded from GitHub Homepage:\r\n\r\nhttps:\/\/github.com\/wenlongche\/SrcExpl\r\n\r\n[Introduction]\r\n\r\nSrcExpl (Source Explorer) is a source code explorer that provides context for the currently selected keyword by displaying the function or type definition\r\nor declaration in a separate window. This plugin aims to recreate the context window available in the IDE.\r\n\r\nFor example, you put the cursor on a function name in the Normal mode, its definition will show on the Source Explorer window a moment later. As soon as you do the 'double-click' operation using your mouse onto the Source Explorer window which had appeared on the bottom of (G)Vim, the definition and its context will be shown on the editor window. In srcexpl v1.2 and above, the function key which users mapped will play a important role that you can not only use mouse but also use keyboard in order to exploring source code in both GUI and cterm VIM.\r\n\r\nThe Source Explorer can work with 'Taglist' and 'NERD tree' very well. Both of them make (G)Vim looks like the IDE in Unix\/Windows\/Mac enviroment.\r\n\r\n[Features]\r\n\r\n1\\ Go insight the definitions of functions and various types of C\/C++\/Java language project, including function, marcos, structure, array, method, class, global variable, local variable etc.\r\n2\\ Double click using left mouse and your own map key (such as: <ENTER>) onto the  Source Explorer window can go forward to the preview context.\r\n3\\ Popup menu and Your own map key to go back from the preview context.\r\n4\\ Auto create and update the 'tags' file intelligently.\r\n\r\n[Tips]\r\n\r\n1\\ Ensure that there is only one 'tags' file in your project PATH, or it would make VIM load all of them on the same time. For example: There are two tags file in the 'your_project' directory, so we will delete the excess 'tags' file in the 'sub_directory'.\r\n\r\n... ...\r\n\r\n[chewenlong@localhost ~]$ cd your_project\/\r\n[chewenlong@localhost your_project]$ pwd\r\n\/home\/chewenlong\/your_project\r\n[chewenlong@localhost your_project]$ ls\r\nbar.c  sub_directory  tags\r\n[chewenlong@localhost your_project]$ cd sub_directory\/\r\n[chewenlong@localhost sub_directory]$ ls\r\nfoo.c  tags\r\n[chewenlong@localhost sub_directory]$ rm -rf tags\r\n[chewenlong@localhost sub_directory]$ ls\r\nfoo.c\r\n[chewenlong@localhost sub_directory]$ cd ..\r\n[chewenlong@localhost your_project]$ ls\r\nbar.c  sub_directory  tags\r\n[chewenlong@localhost your_project]$ vim bar.c\r\n\r\n... ...\r\n\r\n2\\ Make sure the files you are exploring is unix-format, that is, there is no '\\r'(displayed as '^M') at the end of each line. Because the plugin would make a jump mistake when executing EX-commands.\r\n\r\n3\\ If you want your VIM works like the IDE, just try a VIM plugin named 'Trinity (trinity.vim)': \r\n\r\nhttps:\/\/www.vim.org\/scripts\/script.php?script_id=2347\r\n\r\nThis simple plugin can manage 'Source Explorer', 'Taglist' and 'NERD Tree' work together very well.\r\n\r\nIf you want to use VIM with Source Explorer in the UNIXs-console, I suggest map the keys below to jump from one window to another.\r\n\r\nnmap <C-H> <C-W>h\r\nnmap <C-J> <C-W>j\r\nnmap <C-K> <C-W>k\r\nnmap <C-L> <C-W>l\r\n\r\nBelow key mappings can replace the Vim feature for jumping to previously visited locations via jump list.\r\n\r\nnmap <C-I> <C-W>j:call g:SrcExpl_Jump()<CR>\r\nnmap <C-O> :call g:SrcExpl_GoBack()<CR>\r\n\r\nThe typical actions using srcexpl.vim are: \r\n\r\na\\ Move the cursor onto a symbol word.\r\nb\\ As soon as the definition of the word is displayed on the preview window, we type <Ctrl-j> to jump into the previw window.\r\nc\\ Type the SrcExpl_jumpKey(<ENTER> as default) to jump to the exact context of its definition.\r\nd\\ Type the SrcExpl_gobackKey(<SPACE> as default) to go back to the previous position of the symbol word.\r\n","4":"[GitHub]\r\n\r\nThe latest dev version of Source Explorer and screenshots can be downloaded from GitHub Homepage:\r\n\r\nhttps:\/\/github.com\/wenlongche\/SrcExpl\r\n\r\n[Introduction]\r\n\r\nSrcExpl (Source Explorer) is a source code explorer that provides context for the currently selected keyword by displaying the function or type definition\r\nor declaration in a separate window. This plugin aims to recreate the context window available in the IDE.\r\n\r\nFor example, you put the cursor on a function name in the Normal mode, its definition will show on the Source Explorer window a moment later. As soon as you do the 'double-click' operation using your mouse onto the Source Explorer window which had appeared on the bottom of (G)Vim, the definition and its context will be shown on the editor window. In srcexpl v1.2 and above, the function key which users mapped will play a important role that you can not only use mouse but also use keyboard in order to exploring source code in both GUI and cterm VIM.\r\n\r\nThe Source Explorer can work with 'Taglist' and 'NERD tree' very well. Both of them make (G)Vim looks like the IDE in Unix\/Windows\/Mac enviroment.\r\n\r\n[Features]\r\n\r\n1\\ Go insight the definitions of functions and various types of C\/C++\/Java language project, including function, marcos, structure, array, method, class, global variable, local variable etc.\r\n2\\ Double click using left mouse and your own map key (such as: <ENTER>) onto the  Source Explorer window can go forward to the preview context.\r\n3\\ Popup menu and Your own map key to go back from the preview context.\r\n4\\ Auto create and update the 'tags' file intelligently.\r\n\r\n[Tips]\r\n\r\n1\\ Ensure that there is only one 'tags' file in your project PATH, or it would make VIM load all of them on the same time. For example: There are two tags file in the 'your_project' directory, so we will delete the excess 'tags' file in the 'sub_directory'.\r\n\r\n... ...\r\n\r\n[chewenlong@localhost ~]$ cd your_project\/\r\n[chewenlong@localhost your_project]$ pwd\r\n\/home\/chewenlong\/your_project\r\n[chewenlong@localhost your_project]$ ls\r\nbar.c  sub_directory  tags\r\n[chewenlong@localhost your_project]$ cd sub_directory\/\r\n[chewenlong@localhost sub_directory]$ ls\r\nfoo.c  tags\r\n[chewenlong@localhost sub_directory]$ rm -rf tags\r\n[chewenlong@localhost sub_directory]$ ls\r\nfoo.c\r\n[chewenlong@localhost sub_directory]$ cd ..\r\n[chewenlong@localhost your_project]$ ls\r\nbar.c  sub_directory  tags\r\n[chewenlong@localhost your_project]$ vim bar.c\r\n\r\n... ...\r\n\r\n2\\ Make sure the files you are exploring is unix-format, that is, there is no '\\r'(displayed as '^M') at the end of each line. Because the plugin would make a jump mistake when executing EX-commands.\r\n\r\n3\\ If you want your VIM works like the IDE, just try a VIM plugin named 'Trinity (trinity.vim)': \r\n\r\nhttps:\/\/www.vim.org\/scripts\/script.php?script_id=2347\r\n\r\nThis simple plugin can manage 'Source Explorer', 'Taglist' and 'NERD Tree' work together very well.\r\n\r\nIf you want to use VIM with Source Explorer in the UNIXs-console, I suggest map the keys below to jump from one window to another.\r\n\r\nnmap <C-H> <C-W>h\r\nnmap <C-J> <C-W>j\r\nnmap <C-K> <C-W>k\r\nnmap <C-L> <C-W>l\r\n\r\nBelow key mappings can replace the Vim feature for jumping to previously visited locations via jump list.\r\n\r\nnmap <C-I> <C-W>j:call g:SrcExpl_Jump()<CR>\r\nnmap <C-O> :call g:SrcExpl_GoBack()<CR>\r\n\r\nThe typical actions using srcexpl.vim are: \r\n\r\na\\ Move the cursor onto a symbol word.\r\nb\\ As soon as the definition of the word is displayed on the preview window, we type <Ctrl-j> to jump into the previw window.\r\nc\\ Type the SrcExpl_jumpKey(<ENTER> as default) to jump to the exact context of its definition.\r\nd\\ Type the SrcExpl_gobackKey(<SPACE> as default) to go back to the previous position of the symbol word.\r\n","install_details":"1\\ Unzip the archive into your ~\/.vim directory. That should put srcexpl.vim in ~\/.vim\/plugin and srcexpl.txt in ~\/.vim\/doc. \r\n\r\n2\\ Add the followings in your .vimrc or _vimrc and change them by yourself\r\n\r\n\" \/\/ The switch of the Source Explorer                                         \"\r\n\" nmap <F8> :SrcExplToggle<CR>\r\n\"                                                                              \"\r\n\" \/\/ Set the height of Source Explorer window                                  \"\r\n\" let g:SrcExpl_winHeight = 8\r\n\"                                                                              \"\r\n\" \/\/ Set 100 ms for refreshing the Source Explorer                             \"\r\n\" let g:SrcExpl_refreshTime = 100\r\n\"                                                                              \"\r\n\" \/\/ Set \"Enter\" key to jump into the exact definition context                 \"\r\n\" let g:SrcExpl_jumpKey = \"<ENTER>\"\r\n\"                                                                              \"\r\n\" \/\/ Set \"Space\" key for back from the definition context                      \"\r\n\" let g:SrcExpl_gobackKey = \"<SPACE>\"\r\n\"                                                                              \"\r\n\" \/\/ In order to avoid conflicts, the Source Explorer should know what plugins \"\r\n\" \/\/ except itself are using buffers. And you need add their buffer names into \"\r\n\" \/\/ below listaccording to the command \":buffers!\"                            \"\r\n\" let g:SrcExpl_pluginList = [\r\n\"         \\ \"__Tag_List__\",\r\n\"         \\ \"_NERD_tree_\",\r\n\"         \\ \"Source_Explorer\"\r\n\"     \\ ]\r\n\"                                                                              \"\r\n\" \/\/ The color schemes used by Source Explorer. There are five color schemes           \"\r\n\" \/\/ supported for now - Red, Cyan, Green, Yellow and Magenta. Source Explorer         \"\r\n\" \/\/ will pick up one of them randomly when initialization.                            \"\r\n\" let g:SrcExpl_colorSchemeList = [\r\n\"         \\ \"Red\",\r\n\"         \\ \"Cyan\",\r\n\"         \\ \"Green\",\r\n\"         \\ \"Yellow\",\r\n\"         \\ \"Magenta\"\r\n\"     \\ ]\r\n\"                                                                              \"\r\n\" \/\/ Enable\/Disable the local definition searching, and note that this is not  \"\r\n\" \/\/ guaranteed to work, the Source Explorer doesn't check the syntax for now. \"\r\n\" \/\/ It only searches for a match with the keyword according to command 'gd'   \"\r\n\" let g:SrcExpl_searchLocalDef = 1\r\n\"                                                                              \"\r\n\" \/\/ Workaround for Vim bug @https:\/\/goo.gl\/TLPK4K as any plugins using autocmd for    \"\r\n\" \/\/ BufReadPre might have conflicts with Source Explorer. e.g. YCM, Syntastic etc.    \"\r\n\" let g:SrcExpl_nestedAutoCmd = 1\r\n\"                                                                              \"\r\n\" \/\/ Do not let the Source Explorer update the tags file when opening          \"\r\n\" let g:SrcExpl_isUpdateTags = 0\r\n\"                                                                              \"\r\n\" \/\/ Use 'Exuberant Ctags' with '--sort=foldcase -R .' or '-L cscope.files' to \"\r\n\" \/\/  create\/update a tags file                                                \"\r\n\" let g:SrcExpl_updateTagsCmd = \"ctags --sort=foldcase -R .\"\r\n\"                                                                              \"\r\n\" \/\/ Set \"<F12>\" key for updating the tags file artificially                   \"\r\n\" let g:SrcExpl_updateTagsKey = \"<F12>\"\r\n\"                                                                              \"\r\n\" \/\/ Set \"<F3>\" key for displaying the previous definition in the jump list    \"\r\nlet g:SrcExpl_prevDefKey = \"<F3>\"\r\n\"                                                                              \"\r\n\" \/\/ Set \"<F4>\" key for displaying the next definition in the jump list        \"\r\nlet g:SrcExpl_nextDefKey = \"<F4>\"\r\n\r\n3\\ Enjoy vimming :-)","5":"1\\ Unzip the archive into your ~\/.vim directory. That should put srcexpl.vim in ~\/.vim\/plugin and srcexpl.txt in ~\/.vim\/doc. \r\n\r\n2\\ Add the followings in your .vimrc or _vimrc and change them by yourself\r\n\r\n\" \/\/ The switch of the Source Explorer                                         \"\r\n\" nmap <F8> :SrcExplToggle<CR>\r\n\"                                                                              \"\r\n\" \/\/ Set the height of Source Explorer window                                  \"\r\n\" let g:SrcExpl_winHeight = 8\r\n\"                                                                              \"\r\n\" \/\/ Set 100 ms for refreshing the Source Explorer                             \"\r\n\" let g:SrcExpl_refreshTime = 100\r\n\"                                                                              \"\r\n\" \/\/ Set \"Enter\" key to jump into the exact definition context                 \"\r\n\" let g:SrcExpl_jumpKey = \"<ENTER>\"\r\n\"                                                                              \"\r\n\" \/\/ Set \"Space\" key for back from the definition context                      \"\r\n\" let g:SrcExpl_gobackKey = \"<SPACE>\"\r\n\"                                                                              \"\r\n\" \/\/ In order to avoid conflicts, the Source Explorer should know what plugins \"\r\n\" \/\/ except itself are using buffers. And you need add their buffer names into \"\r\n\" \/\/ below listaccording to the command \":buffers!\"                            \"\r\n\" let g:SrcExpl_pluginList = [\r\n\"         \\ \"__Tag_List__\",\r\n\"         \\ \"_NERD_tree_\",\r\n\"         \\ \"Source_Explorer\"\r\n\"     \\ ]\r\n\"                                                                              \"\r\n\" \/\/ The color schemes used by Source Explorer. There are five color schemes           \"\r\n\" \/\/ supported for now - Red, Cyan, Green, Yellow and Magenta. Source Explorer         \"\r\n\" \/\/ will pick up one of them randomly when initialization.                            \"\r\n\" let g:SrcExpl_colorSchemeList = [\r\n\"         \\ \"Red\",\r\n\"         \\ \"Cyan\",\r\n\"         \\ \"Green\",\r\n\"         \\ \"Yellow\",\r\n\"         \\ \"Magenta\"\r\n\"     \\ ]\r\n\"                                                                              \"\r\n\" \/\/ Enable\/Disable the local definition searching, and note that this is not  \"\r\n\" \/\/ guaranteed to work, the Source Explorer doesn't check the syntax for now. \"\r\n\" \/\/ It only searches for a match with the keyword according to command 'gd'   \"\r\n\" let g:SrcExpl_searchLocalDef = 1\r\n\"                                                                              \"\r\n\" \/\/ Workaround for Vim bug @https:\/\/goo.gl\/TLPK4K as any plugins using autocmd for    \"\r\n\" \/\/ BufReadPre might have conflicts with Source Explorer. e.g. YCM, Syntastic etc.    \"\r\n\" let g:SrcExpl_nestedAutoCmd = 1\r\n\"                                                                              \"\r\n\" \/\/ Do not let the Source Explorer update the tags file when opening          \"\r\n\" let g:SrcExpl_isUpdateTags = 0\r\n\"                                                                              \"\r\n\" \/\/ Use 'Exuberant Ctags' with '--sort=foldcase -R .' or '-L cscope.files' to \"\r\n\" \/\/  create\/update a tags file                                                \"\r\n\" let g:SrcExpl_updateTagsCmd = \"ctags --sort=foldcase -R .\"\r\n\"                                                                              \"\r\n\" \/\/ Set \"<F12>\" key for updating the tags file artificially                   \"\r\n\" let g:SrcExpl_updateTagsKey = \"<F12>\"\r\n\"                                                                              \"\r\n\" \/\/ Set \"<F3>\" key for displaying the previous definition in the jump list    \"\r\nlet g:SrcExpl_prevDefKey = \"<F3>\"\r\n\"                                                                              \"\r\n\" \/\/ Set \"<F4>\" key for displaying the next definition in the jump list        \"\r\nlet g:SrcExpl_nextDefKey = \"<F4>\"\r\n\r\n3\\ Enjoy vimming :-)","first_name":"Wenlong","6":"Wenlong","last_name":"Che","7":"Che","releases":[{"0":"2179","vim_version":"7.0","1":"7.0","script_version":"6.0","2":"6.0","version_comment":"- Add color scheme feature - The user is able to easily identify the specific\r\n  window by the color used for highlight when there are multi-windows open\r\n  at the same time.\r\n- Add a workaround for Vim bug @https:\/\/goo.gl\/TLPK4K as any plugins using\r\n  autocmd for BufReadPre might have conflicts with Source Explorer. e.g. YCM,\r\n  Syntastic etc. - https:\/\/github.com\/wesleyche\/SrcExpl\/issues\/6\r\n- Bug fix - https:\/\/github.com\/wesleyche\/SrcExpl\/issues\/4","3":"- Add color scheme feature - The user is able to easily identify the specific\r\n  window by the color used for highlight when there are multi-windows open\r\n  at the same time.\r\n- Add a workaround for Vim bug @https:\/\/goo.gl\/TLPK4K as any plugins using\r\n  autocmd for BufReadPre might have conflicts with Source Explorer. e.g. YCM,\r\n  Syntastic etc. - https:\/\/github.com\/wesleyche\/SrcExpl\/issues\/6\r\n- Bug fix - https:\/\/github.com\/wesleyche\/SrcExpl\/issues\/4","package":"SrcExpl-6.0.zip","4":"SrcExpl-6.0.zip","src_id":"26062","5":"26062","creation_date":"1529407754","6":"1529407754"},{"0":"2179","vim_version":"7.0","1":"7.0","script_version":"5.3","2":"5.3","version_comment":"- Fix a bug when operating the Quickfix window after closing the Source Explorer window. \r\n- Handle the case when the cursor is located at the Quickfix window as same as other external plugins.\r\n- Update doc\/srcexpl.txt","3":"- Fix a bug when operating the Quickfix window after closing the Source Explorer window. \r\n- Handle the case when the cursor is located at the Quickfix window as same as other external plugins.\r\n- Update doc\/srcexpl.txt","package":"SrcExpl-5.3.zip","4":"SrcExpl-5.3.zip","src_id":"20807","5":"20807","creation_date":"1379273414","6":"1379273414"},{"0":"2179","vim_version":"7.0","1":"7.0","script_version":"5.2","2":"5.2","version_comment":"- Add the fast way for displaying the previous or next definition in the jump list. The new feature is similar with the commands called cprev and cnext for operating the Quickfix list. You can add below config lines in your .vimrc or just update your Trinity to v2.1. \r\n    1. \" \/\/ Set \"<F3>\" key for displaying the previous definition in the jump list \r\n       let g:SrcExpl_prevDefKey = \"<F3>\" \r\n    2. \" \/\/ Set \"<F4>\" key for displaying the next definition in the jump list \r\n       let g:SrcExpl_nextDefKey = \"<F4>\" \r\n- Fix a bug when clicking the default prompt line in the Source Explorer window.","3":"- Add the fast way for displaying the previous or next definition in the jump list. The new feature is similar with the commands called cprev and cnext for operating the Quickfix list. You can add below config lines in your .vimrc or just update your Trinity to v2.1. \r\n    1. \" \/\/ Set \"<F3>\" key for displaying the previous definition in the jump list \r\n       let g:SrcExpl_prevDefKey = \"<F3>\" \r\n    2. \" \/\/ Set \"<F4>\" key for displaying the next definition in the jump list \r\n       let g:SrcExpl_nextDefKey = \"<F4>\" \r\n- Fix a bug when clicking the default prompt line in the Source Explorer window.","package":"SrcExpl-5.2.zip","4":"SrcExpl-5.2.zip","src_id":"19701","5":"19701","creation_date":"1364213421","6":"1364213421"},{"0":"2179","vim_version":"7.0","1":"7.0","script_version":"5.1","2":"5.1","version_comment":"5.0\r\nReplaced use of preview window with a named buffer.\r\nMoved to github.\r\nAdded documentation.\r\n\r\n5.1\r\nAdded two APIs for serving other plugins:\r\nSrcExpl_GetWin(), getting the Source Explorer window number for those plugins based on multiple windows.\r\nSrcExpl_GetVer(), getting the Source Explorer version for the forward compatibility.\r\nAdded debug\/logging functions for the internal development.","3":"5.0\r\nReplaced use of preview window with a named buffer.\r\nMoved to github.\r\nAdded documentation.\r\n\r\n5.1\r\nAdded two APIs for serving other plugins:\r\nSrcExpl_GetWin(), getting the Source Explorer window number for those plugins based on multiple windows.\r\nSrcExpl_GetVer(), getting the Source Explorer version for the forward compatibility.\r\nAdded debug\/logging functions for the internal development.","package":"SrcExpl-5.1.zip","4":"SrcExpl-5.1.zip","src_id":"18642","5":"18642","creation_date":"1348145237","6":"1348145237"},{"0":"2179","vim_version":"7.0","1":"7.0","script_version":"4.5","2":"4.5","version_comment":"The Source Explorer can support Vim Highlight Searching in this version. Because srcexpl.vim can restore the user's setting named hlsearch after executing the EX command and redraw the screen.","3":"The Source Explorer can support Vim Highlight Searching in this version. Because srcexpl.vim can restore the user's setting named hlsearch after executing the EX command and redraw the screen.","package":"srcexpl.vim","4":"srcexpl.vim","src_id":"18357","5":"18357","creation_date":"1343813466","6":"1343813466"},{"0":"2179","vim_version":"7.0","1":"7.0","script_version":"4.4","2":"4.4","version_comment":"Change the variable named s:SrcExpl_markList to be a global one. So we can recover the context of mark list and continue to use SrcExpl_GoBack function although the plugin had been re-opened.","3":"Change the variable named s:SrcExpl_markList to be a global one. So we can recover the context of mark list and continue to use SrcExpl_GoBack function although the plugin had been re-opened.","package":"srcexpl.vim","4":"srcexpl.vim","src_id":"18351","5":"18351","creation_date":"1343734680","6":"1343734680"},{"0":"2179","vim_version":"7.0","1":"7.0","script_version":"4.3","2":"4.3","version_comment":"Fixed a bug when the working 'tags' file was created with the commands 'ctags -L cscope.files'. In this case, the plugin could not change the relative path to the absolute one. Thank Trevor Brown for reporting this bug.","3":"Fixed a bug when the working 'tags' file was created with the commands 'ctags -L cscope.files'. In this case, the plugin could not change the relative path to the absolute one. Thank Trevor Brown for reporting this bug.","package":"srcexpl.vim","4":"srcexpl.vim","src_id":"14003","5":"14003","creation_date":"1286344881","6":"1286344881"},{"0":"2179","vim_version":"7.0","1":"7.0","script_version":"4.2","2":"4.2","version_comment":"Bug fixed: In Linux or other *UNIX OS, Source Explorer v4.1 would change the 'current work directory' to '~\/' when updating the tags file. Thanks to Ozan Sener for the bug-report.","3":"Bug fixed: In Linux or other *UNIX OS, Source Explorer v4.1 would change the 'current work directory' to '~\/' when updating the tags file. Thanks to Ozan Sener for the bug-report.","package":"srcexpl.vim","4":"srcexpl.vim","src_id":"10221","5":"10221","creation_date":"1237203727","6":"1237203727"},{"0":"2179","vim_version":"7.0","1":"7.0","script_version":"4.1","2":"4.1","version_comment":"Fixed a bug in Version 4.0 which would make you jump into a empty file when listing multi-tags information. ","3":"Fixed a bug in Version 4.0 which would make you jump into a empty file when listing multi-tags information. ","package":"srcexpl.vim","4":"srcexpl.vim","src_id":"10186","5":"10186","creation_date":"1236863260","6":"1236863260"},{"0":"2179","vim_version":"7.0","1":"7.0","script_version":"4.0","2":"4.0","version_comment":"In this version, the taglist() interface do the binary searching in the exact tags file instead of a linear search, so each tagging responses much more quickly than before even though the tags file of the source code project is so large. All we have to do is add an option in your ctags ultility (--sort=foldcase).","3":"In this version, the taglist() interface do the binary searching in the exact tags file instead of a linear search, so each tagging responses much more quickly than before even though the tags file of the source code project is so large. All we have to do is add an option in your ctags ultility (--sort=foldcase).","package":"srcexpl.vim","4":"srcexpl.vim","src_id":"10149","5":"10149","creation_date":"1236604974","6":"1236604974"},{"0":"2179","vim_version":"7.0","1":"7.0","script_version":"3.9","2":"3.9","version_comment":"New features: --- The 1st anniversary \r\n1\\ Manually updating or creating the 'tags' file using a new custom key named g:SrceExpl_updateTagsKey when you browse the source code without closing the Source Explorer window. \r\n2\\ Dynamically loading the tags database from one source code project to another without closing the Source Explorer window. ","3":"New features: --- The 1st anniversary \r\n1\\ Manually updating or creating the 'tags' file using a new custom key named g:SrceExpl_updateTagsKey when you browse the source code without closing the Source Explorer window. \r\n2\\ Dynamically loading the tags database from one source code project to another without closing the Source Explorer window. ","package":"srcexpl.vim","4":"srcexpl.vim","src_id":"10108","5":"10108","creation_date":"1236168681","6":"1236168681"},{"0":"2179","vim_version":"7.0","1":"7.0","script_version":"3.8","2":"3.8","version_comment":"I've implemented a local mark-stack mechanism using variable type of dictionary in this version, so you can trace into the source code more deeply without warring about the limit of 'A-Z' level using Vim's mark before.\r\n","3":"I've implemented a local mark-stack mechanism using variable type of dictionary in this version, so you can trace into the source code more deeply without warring about the limit of 'A-Z' level using Vim's mark before.\r\n","package":"srcexpl.vim","4":"srcexpl.vim","src_id":"10083","5":"10083","creation_date":"1235994108","6":"1235994108"},{"0":"2179","vim_version":"7.0","1":"7.0","script_version":"3.7","2":"3.7","version_comment":"In this version, We do not try to tag something when we got the invalid symbol (only 0-9, a-z, A-Z, and '_' are valid) under the current cursor. So we should not feel unfrequently when we explore the huge source code project using \"HJKL\" to jump from a word to another.","3":"In this version, We do not try to tag something when we got the invalid symbol (only 0-9, a-z, A-Z, and '_' are valid) under the current cursor. So we should not feel unfrequently when we explore the huge source code project using \"HJKL\" to jump from a word to another.","package":"srcexpl.vim","4":"srcexpl.vim","src_id":"10055","5":"10055","creation_date":"1235745403","6":"1235745403"},{"0":"2179","vim_version":"7.0","1":"7.0","script_version":"3.6","2":"3.6","version_comment":"Let all the folds opened in order to avoid opening and closeing each fold every time.","3":"Let all the folds opened in order to avoid opening and closeing each fold every time.","package":"srcexpl.vim","4":"srcexpl.vim","src_id":"9728","5":"9728","creation_date":"1230471213","6":"1230471213"},{"0":"2179","vim_version":"7.0","1":"7.0","script_version":"3.5","2":"3.5","version_comment":"1\\ Add one new feature: Update different 'tags' file dynamically on different project PATH when opening the Source Explorer each time. \r\n2\\ Add one user interface variable named g:SrcExpl_updateTagsCmd, which can be set to execute particular 'ctags' utility program, \"ctags -R *\" as default. ","3":"1\\ Add one new feature: Update different 'tags' file dynamically on different project PATH when opening the Source Explorer each time. \r\n2\\ Add one user interface variable named g:SrcExpl_updateTagsCmd, which can be set to execute particular 'ctags' utility program, \"ctags -R *\" as default. ","package":"srcexpl.vim","4":"srcexpl.vim","src_id":"9461","5":"9461","creation_date":"1226141884","6":"1226141884"},{"0":"2179","vim_version":"7.0","1":"7.0","script_version":"3.4","2":"3.4","version_comment":"Bug fixed: Make \"Source_Explorer\" not display on the buffers list and menu.","3":"Bug fixed: Make \"Source_Explorer\" not display on the buffers list and menu.","package":"srcexpl.vim","4":"srcexpl.vim","src_id":"9424","5":"9424","creation_date":"1225713595","6":"1225713595"},{"0":"2179","vim_version":"7.0","1":"7.0","script_version":"3.3","2":"3.3","version_comment":"Bug fixed: The string of EX command is set to be case sensitive, so it is more accurate when excuting the EX command.","3":"Bug fixed: The string of EX command is set to be case sensitive, so it is more accurate when excuting the EX command.","package":"srcexpl.vim","4":"srcexpl.vim","src_id":"9256","5":"9256","creation_date":"1221541742","6":"1221541742"},{"0":"2179","vim_version":"7.0","1":"7.0","script_version":"3.2","2":"3.2","version_comment":"1\\ Added one user interface variable named g:SrcExpl_jumpKey, which can be mapped to jump into the exact definition context, \"<ENTER>\" as default.\r\n2\\ Delete one user interface variable named g:SrcExpl_refreshKey, because it is almost not be used actually according to feedbacks from users.\r\n3\\ Added the protect mechanism when running multiple tab pages.\r\n4\\ Avoid additional refresh operation when the cursor had jumped into the definition context.\r\n5\\ Fixed a bug that setting a error mark on the [Jump List] line without judgement.\r\n\r\n","3":"1\\ Added one user interface variable named g:SrcExpl_jumpKey, which can be mapped to jump into the exact definition context, \"<ENTER>\" as default.\r\n2\\ Delete one user interface variable named g:SrcExpl_refreshKey, because it is almost not be used actually according to feedbacks from users.\r\n3\\ Added the protect mechanism when running multiple tab pages.\r\n4\\ Avoid additional refresh operation when the cursor had jumped into the definition context.\r\n5\\ Fixed a bug that setting a error mark on the [Jump List] line without judgement.\r\n\r\n","package":"srcexpl.vim","4":"srcexpl.vim","src_id":"9185","5":"9185","creation_date":"1219895052","6":"1219895052"},{"0":"2179","vim_version":"7.0","1":"7.0","script_version":"3.1","2":"3.1","version_comment":"Two bugs fixed:\r\n1\\ Avoid highlight the whole EX command when previewing the definition.\r\n2\\ Not update the Popup menu when the current word under the cursor\r\n   had been tagged already, or it would be changed on the UNIXs platform.","3":"Two bugs fixed:\r\n1\\ Avoid highlight the whole EX command when previewing the definition.\r\n2\\ Not update the Popup menu when the current word under the cursor\r\n   had been tagged already, or it would be changed on the UNIXs platform.","package":"srcexpl.vim","4":"srcexpl.vim","src_id":"9144","5":"9144","creation_date":"1219037742","6":"1219037742"},{"0":"2179","vim_version":"7.0","1":"7.0","script_version":"3.0","2":"3.0","version_comment":"New feature: Local definition searching and preview using the interface of 'gd' command in VIM. Note that this is not guaranteed to work, the Source Explorer does not check the syntax for now, it only searches for a match with the keyword according to the command 'gd' when you enable the new variable named g:SrcExpl_searchLocalDef.\r\nImprovement: Reimplement the jump mechannism when going back from the preview context using the mark stack with 'A-Z' (26 depth actually). It is more accurate than using the 'Ctrl-o' command.","3":"New feature: Local definition searching and preview using the interface of 'gd' command in VIM. Note that this is not guaranteed to work, the Source Explorer does not check the syntax for now, it only searches for a match with the keyword according to the command 'gd' when you enable the new variable named g:SrcExpl_searchLocalDef.\r\nImprovement: Reimplement the jump mechannism when going back from the preview context using the mark stack with 'A-Z' (26 depth actually). It is more accurate than using the 'Ctrl-o' command.","package":"srcexpl.vim","4":"srcexpl.vim","src_id":"9086","5":"9086","creation_date":"1218132306","6":"1218132306"},{"0":"2179","vim_version":"7.0","1":"7.0","script_version":"2.6","2":"2.6","version_comment":"Update the mechanism and process when the Source Explorer work with other plugins, such as Taglist, NERD tree, etc. Of course, you must tell the Source Explorer what plugins are using the split windows according to a new MMI setting: g:SrcExpl_pluginList","3":"Update the mechanism and process when the Source Explorer work with other plugins, such as Taglist, NERD tree, etc. Of course, you must tell the Source Explorer what plugins are using the split windows according to a new MMI setting: g:SrcExpl_pluginList","package":"srcexpl.vim","4":"srcexpl.vim","src_id":"9028","5":"9028","creation_date":"1217047923","6":"1217047923"},{"0":"2179","vim_version":"7.0","1":"7.0","script_version":"2.5","2":"2.5","version_comment":"  In this version, I add a prompt line which contain the tag name and its counts when we do the multi-definition searching. A bug about folding in VIM is fixed. In srcexpl.vim, I desrcibed that how the Source Explorer works with the Taglist and the MiniBufExplorer on my platform.","3":"  In this version, I add a prompt line which contain the tag name and its counts when we do the multi-definition searching. A bug about folding in VIM is fixed. In srcexpl.vim, I desrcibed that how the Source Explorer works with the Taglist and the MiniBufExplorer on my platform.","package":"srcexpl.vim","4":"srcexpl.vim","src_id":"8955","5":"8955","creation_date":"1216101692","6":"1216101692"},{"0":"2179","vim_version":"7.0","1":"7.0","script_version":"2.4","2":"2.4","version_comment":"    In version 2.4, the srcexpl plugin should work more stable and more efficient than before.\r\n    Firstly, I implemented the method of getting tags list without traversaling the 'tags' file. So parsing and showing the tags of whole project is more quickly, espacially in a large project. (e.g. The size of tags file in \"Linux-2.4.0\" is 19 MBytes which including more than 248000 lines data.)\r\n    Secondly, it is more accurate to find the symbol definition because of the regular expression. \r\n    Finally, I handled a potential problem of deleting buffers, and it may become a bug when changing the tags list in WIN32 platform.\r\n\r\n","3":"    In version 2.4, the srcexpl plugin should work more stable and more efficient than before.\r\n    Firstly, I implemented the method of getting tags list without traversaling the 'tags' file. So parsing and showing the tags of whole project is more quickly, espacially in a large project. (e.g. The size of tags file in \"Linux-2.4.0\" is 19 MBytes which including more than 248000 lines data.)\r\n    Secondly, it is more accurate to find the symbol definition because of the regular expression. \r\n    Finally, I handled a potential problem of deleting buffers, and it may become a bug when changing the tags list in WIN32 platform.\r\n\r\n","package":"srcexpl.vim","4":"srcexpl.vim","src_id":"8901","5":"8901","creation_date":"1215498768","6":"1215498768"},{"0":"2179","vim_version":"7.0","1":"7.0","script_version":"2.3","2":"2.3","version_comment":"Bugfixed: When the current file which you are editing is not saved, the Source Explorer would not jump to the definition of the symbol under the cursor. This mechanism can handle the 'one-file-multi-buffers' situation very well.","3":"Bugfixed: When the current file which you are editing is not saved, the Source Explorer would not jump to the definition of the symbol under the cursor. This mechanism can handle the 'one-file-multi-buffers' situation very well.","package":"srcexpl.vim","4":"srcexpl.vim","src_id":"8520","5":"8520","creation_date":"1207361314","6":"1207361314"},{"0":"2179","vim_version":"7.0","1":"7.0","script_version":"2.2","2":"2.2","version_comment":"In this version(V2.2), I added a feature, which supported 'tags' file auto-updateing when you open the Source Explorer every time. And if the tags file  were not found, the Source Explorer would create one in the current directory according your choice. Besides, I fixed a bug of tags file loading on the mac OS X running enviorment. Thank Larry and Maqi for their freebacks and suggestions. :-)","3":"In this version(V2.2), I added a feature, which supported 'tags' file auto-updateing when you open the Source Explorer every time. And if the tags file  were not found, the Source Explorer would create one in the current directory according your choice. Besides, I fixed a bug of tags file loading on the mac OS X running enviorment. Thank Larry and Maqi for their freebacks and suggestions. :-)","package":"srcexpl.vim","4":"srcexpl.vim","src_id":"8495","5":"8495","creation_date":"1206511807","6":"1206511807"},{"0":"2179","vim_version":"7.0","1":"7.0","script_version":"2.1","2":"2.1","version_comment":"In this version, I implemented the method to do the recursion for searching the 'tags' file from the current directory to the root directory. In addition, the mechanism for vim version inspection is added. Finally, I rewrote the function named g:SrcExpl_OtherPluginAdapter() in order to adapt the privious postion of the editor window when using the Taglist and MiniBufExpl Plugins.","3":"In this version, I implemented the method to do the recursion for searching the 'tags' file from the current directory to the root directory. In addition, the mechanism for vim version inspection is added. Finally, I rewrote the function named g:SrcExpl_OtherPluginAdapter() in order to adapt the privious postion of the editor window when using the Taglist and MiniBufExpl Plugins.","package":"srcexpl.vim","4":"srcexpl.vim","src_id":"8487","5":"8487","creation_date":"1206253907","6":"1206253907"},{"0":"2179","vim_version":"7.0","1":"7.0","script_version":"2.0","2":"2.0","version_comment":"Added an important feature, that is, multi-definitions list and explore. \r\nWhen the symbol under the cursor is defined in several places, the Source Explorer window will list them one by one. You can select one of them by a double-click or a <Enter> key onto the exact line, and then we jump to the place that match the definition.\r\nThis feature is so important that you can only use one hand ( the one using the mouse :-) ) to explore the source code conveniently, and avoid the number selection when tagging a mulit-definition by <Left-Mouse> or <Ctrl-]>.","3":"Added an important feature, that is, multi-definitions list and explore. \r\nWhen the symbol under the cursor is defined in several places, the Source Explorer window will list them one by one. You can select one of them by a double-click or a <Enter> key onto the exact line, and then we jump to the place that match the definition.\r\nThis feature is so important that you can only use one hand ( the one using the mouse :-) ) to explore the source code conveniently, and avoid the number selection when tagging a mulit-definition by <Left-Mouse> or <Ctrl-]>.","package":"srcexpl.vim","4":"srcexpl.vim","src_id":"8453","5":"8453","creation_date":"1205475572","6":"1205475572"},{"0":"2179","vim_version":"7.0","1":"7.0","script_version":"1.2","2":"1.2","version_comment":"Add one feature and two user interfaces.\r\nYou can use your own map key to force to complete one refreshing operation. And it will take a less waiting time sometimes.\r\nAdditionally, users can set update time interval by themselves in this version.","3":"Add one feature and two user interfaces.\r\nYou can use your own map key to force to complete one refreshing operation. And it will take a less waiting time sometimes.\r\nAdditionally, users can set update time interval by themselves in this version.","package":"srcexpl.vim","4":"srcexpl.vim","src_id":"8430","5":"8430","creation_date":"1205121274","6":"1205121274"},{"0":"2179","vim_version":"7.0","1":"7.0","script_version":"1.1","2":"1.1","version_comment":"Inthis version(v1.1), I added the following features\r\n1\\ add the 'SrcExplGoBack' item in popup menu when you click right button of your mouse. You will see that when you use srcexpl.vim for exploring the source code.\r\n2\\ add an interface for users who want to map their own key for do the 'SrcExplGoBack' function.\r\n3\\ 'SrcExplGoBack' is such a feature that it make user go back from 'definition contexts' in editor. When you click the 'SrcExplGoBack' item, it jump the privious place which your have explored just now.","3":"Inthis version(v1.1), I added the following features\r\n1\\ add the 'SrcExplGoBack' item in popup menu when you click right button of your mouse. You will see that when you use srcexpl.vim for exploring the source code.\r\n2\\ add an interface for users who want to map their own key for do the 'SrcExplGoBack' function.\r\n3\\ 'SrcExplGoBack' is such a feature that it make user go back from 'definition contexts' in editor. When you click the 'SrcExplGoBack' item, it jump the privious place which your have explored just now.","package":"srcexpl.vim","4":"srcexpl.vim","src_id":"8400","5":"8400","creation_date":"1204781134","6":"1204781134"},{"0":"2179","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"srcexpl.vim","4":"srcexpl.vim","src_id":"8388","5":"8388","creation_date":"1204608480","6":"1204608480"}]},"2178":{"script_id":"2178","0":"2178","script_name":"cqml.vim","1":"cqml.vim","script_type":"syntax","2":"syntax","summary":"Syntax definitions for the Component Quality Modelling Language","3":"Syntax definitions for the Component Quality Modelling Language","description":"Highlights keywords from CQML which is a formal language to define component quality aspects and templates for service level agreements in software engineering.","4":"Highlights keywords from CQML which is a formal language to define component quality aspects and templates for service level agreements in software engineering.","install_details":"","5":"","first_name":"Josef","6":"Josef","last_name":"Spillner","7":"Spillner","releases":[{"0":"2178","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"cqml.vim","4":"cqml.vim","src_id":"8387","5":"8387","creation_date":"1204591357","6":"1204591357"}]},"2177":{"script_id":"2177","0":"2177","script_name":"rdhelp.txt","1":"rdhelp.txt","script_type":"utility","2":"utility","summary":"Help to Rd files (R documentation) in vimhelp format","3":"Help to Rd files (R documentation) in vimhelp format","description":"This is an excerpt from R manual \"Writing R Extensions\" which is limited to section 3. \"Writing R Documentation Files\". It is a specification of the Rd format, available commands etc. For a full document look here: http:\/\/cran.r-project.org\/doc\/manuals\/R-exts.html. The project's website is http:\/\/www.r-project.org\/.","4":"This is an excerpt from R manual \"Writing R Extensions\" which is limited to section 3. \"Writing R Documentation Files\". It is a specification of the Rd format, available commands etc. For a full document look here: http:\/\/cran.r-project.org\/doc\/manuals\/R-exts.html. The project's website is http:\/\/www.r-project.org\/.","install_details":"Put to $vimfiles\/doc and use :helptags command to generate the tags.","5":"Put to $vimfiles\/doc and use :helptags command to generate the tags.","first_name":"Micha\u0142","6":"Michał","last_name":"Bojanowski","7":"Bojanowski","releases":[{"0":"2177","vim_version":"6.0","1":"6.0","script_version":"1.0.1","2":"1.0.1","version_comment":"Minor tag corrections","3":"Minor tag corrections","package":"rdhelp.txt","4":"rdhelp.txt","src_id":"11532","5":"11532","creation_date":"1255684818","6":"1255684818"},{"0":"2177","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"rdhelp.txt","4":"rdhelp.txt","src_id":"8377","5":"8377","creation_date":"1204392284","6":"1204392284"}]},"2176":{"script_id":"2176","0":"2176","script_name":"cwiki","1":"cwiki","script_type":"ftplugin","2":"ftplugin","summary":"single file wiki with unobtrusive syntax","3":"single file wiki with unobtrusive syntax","description":"The plugin enhances syntax\/folding\/mappings of the current buffer, converting it to simple yet useful single-file wiki. Name stands for something like \"compact wiki\".\r\n\r\nScreenshot can be downloaded here: http:\/\/a-hw.narod.ru\/cwiki.png\r\n\r\nFeatures:\r\n=========================\r\n\r\n * single file storage (readable textual format; built-in VIM encryption can be applied)\r\n * unobtrusive wikiwords (no special symbols like brackets)\r\n * synonyms (you can define them, so \"Bill\", \"William\", and \"Mr. W. Smith\" point to the same article)\r\n * folding (separates articles; shows number of meaningful article lines)\r\n * syntax highlighting\r\n * visual wikiword selector\r\n\r\nSyntax:\r\n=========================\r\n\r\nFirst level article title: +++ Wiki word\r\nSecond level article title: ++++ Wiki word\r\nThird level article title: +++++ Wiki word\r\n\r\nLevel affects folding only, no other side effects.\r\n\r\nOptional metadata is expected to be the first non-blank line after the title:\r\n\r\n\tSynonyms: a, b, {C,c}def\r\n\r\nWhitespace before \"Synonyms\" and after comma is mandatory. Curly braces are expanded like shell patterns, i.e. the line above is equivalent to the following:\r\n\r\n\tSynonyms: a, b, Cdef, cdef\r\n\r\nActually \"Synonyms\" is the only metadata currently supported.\r\n\r\nKey mappings:\r\n=========================\r\n\r\nn_Ctrl-]: follow wikiword under cursor\r\nv_Ctrl-]: add new article; currently selected text is used as title\r\nn_F5: refresh the wiki (you need this if you altered synonyms)\r\nn_F3: show wikiword selector (current wikiword will be highlighted; move cursor to the desired wikiword and press <CR> to select it, or press <F3> to close the selector)\r\n\r\nNo other special bindings so far. You can move text around at will. Specifically it is really handy to move whole articles by doing DD and p with folded blocks.\r\n\r\nHighlighting groups:\r\n=========================\r\n\r\n * CWikiTitle1, CWikiTitle2, CWikiTitle3: article titles (linked to Title by default).\r\n * CWikiTitleMark: \"+\" signs in the title (linked to Title by default)\r\n * CWikiWord: any detected wikiword (linked to Underlined by default)\r\n\r\nNotes:\r\n=========================\r\n\r\nAFAIK on Win32 by default Underlined looks like Normal, so you won't be able to see any wikiwords. The following might help:\r\n\r\n\t:highlight Underlined gui=underlined\r\n\r\nI didn't experience any problems with the plugin yet. But maybe it is a good idea to make backups every now and then (if you do something useful, of course):\r\n\r\n\tset backup\r\n\tset writebackup\r\n\tau BufWritePre <buffer> let &bex = '-' . strftime(\"%Y%b%d%X\") . '~'\r\n\r\nSample:\r\n=========================\r\n\r\nHere is minimal yet complete sample of the wikifile. Just paste it into new buffer and type :set ft=cwiki (after installing the plugin, of course).\r\n\r\n--8<------------------------------\r\n+++ First article\r\n\r\n    Synonyms: 1st article, {A,a}rticle #1\r\n\r\nHere we have some text. I'd like to mention Mr. W.\r\nSmith (note that his name is wrapped with <CR>).\r\n\r\n+++ Mr. W. Smith\r\n\r\n    Synonyms: William, Bill, dad\r\n\r\nThis article is about Mr. W. Smith, also known as\r\nWilliam, Bill. He has two doughters: Jane and Kim.\r\n\r\nArticle #1 mentions Bill. Though, that 1st article\r\nis rather short.\r\n\r\n++++ Jane Smith\r\n\r\n    Synonyms: Jane\r\n\r\nMs. Jane's dad is Bill.\r\n\r\n++++ Kim\r\n\r\nKim is too young, so we refer to her without the last\r\nname, e.g. no synonyms yet. She loves her dad.\r\n--8<------------------------------","4":"The plugin enhances syntax\/folding\/mappings of the current buffer, converting it to simple yet useful single-file wiki. Name stands for something like \"compact wiki\".\r\n\r\nScreenshot can be downloaded here: http:\/\/a-hw.narod.ru\/cwiki.png\r\n\r\nFeatures:\r\n=========================\r\n\r\n * single file storage (readable textual format; built-in VIM encryption can be applied)\r\n * unobtrusive wikiwords (no special symbols like brackets)\r\n * synonyms (you can define them, so \"Bill\", \"William\", and \"Mr. W. Smith\" point to the same article)\r\n * folding (separates articles; shows number of meaningful article lines)\r\n * syntax highlighting\r\n * visual wikiword selector\r\n\r\nSyntax:\r\n=========================\r\n\r\nFirst level article title: +++ Wiki word\r\nSecond level article title: ++++ Wiki word\r\nThird level article title: +++++ Wiki word\r\n\r\nLevel affects folding only, no other side effects.\r\n\r\nOptional metadata is expected to be the first non-blank line after the title:\r\n\r\n\tSynonyms: a, b, {C,c}def\r\n\r\nWhitespace before \"Synonyms\" and after comma is mandatory. Curly braces are expanded like shell patterns, i.e. the line above is equivalent to the following:\r\n\r\n\tSynonyms: a, b, Cdef, cdef\r\n\r\nActually \"Synonyms\" is the only metadata currently supported.\r\n\r\nKey mappings:\r\n=========================\r\n\r\nn_Ctrl-]: follow wikiword under cursor\r\nv_Ctrl-]: add new article; currently selected text is used as title\r\nn_F5: refresh the wiki (you need this if you altered synonyms)\r\nn_F3: show wikiword selector (current wikiword will be highlighted; move cursor to the desired wikiword and press <CR> to select it, or press <F3> to close the selector)\r\n\r\nNo other special bindings so far. You can move text around at will. Specifically it is really handy to move whole articles by doing DD and p with folded blocks.\r\n\r\nHighlighting groups:\r\n=========================\r\n\r\n * CWikiTitle1, CWikiTitle2, CWikiTitle3: article titles (linked to Title by default).\r\n * CWikiTitleMark: \"+\" signs in the title (linked to Title by default)\r\n * CWikiWord: any detected wikiword (linked to Underlined by default)\r\n\r\nNotes:\r\n=========================\r\n\r\nAFAIK on Win32 by default Underlined looks like Normal, so you won't be able to see any wikiwords. The following might help:\r\n\r\n\t:highlight Underlined gui=underlined\r\n\r\nI didn't experience any problems with the plugin yet. But maybe it is a good idea to make backups every now and then (if you do something useful, of course):\r\n\r\n\tset backup\r\n\tset writebackup\r\n\tau BufWritePre <buffer> let &bex = '-' . strftime(\"%Y%b%d%X\") . '~'\r\n\r\nSample:\r\n=========================\r\n\r\nHere is minimal yet complete sample of the wikifile. Just paste it into new buffer and type :set ft=cwiki (after installing the plugin, of course).\r\n\r\n--8<------------------------------\r\n+++ First article\r\n\r\n    Synonyms: 1st article, {A,a}rticle #1\r\n\r\nHere we have some text. I'd like to mention Mr. W.\r\nSmith (note that his name is wrapped with <CR>).\r\n\r\n+++ Mr. W. Smith\r\n\r\n    Synonyms: William, Bill, dad\r\n\r\nThis article is about Mr. W. Smith, also known as\r\nWilliam, Bill. He has two doughters: Jane and Kim.\r\n\r\nArticle #1 mentions Bill. Though, that 1st article\r\nis rather short.\r\n\r\n++++ Jane Smith\r\n\r\n    Synonyms: Jane\r\n\r\nMs. Jane's dad is Bill.\r\n\r\n++++ Kim\r\n\r\nKim is too young, so we refer to her without the last\r\nname, e.g. no synonyms yet. She loves her dad.\r\n--8<------------------------------","install_details":"Copy the file into your ~\/.vim\/ftplugin\/ directory. To wikify particular file, load it and then type:\r\n\r\n    :set ft=cwiki\r\n\r\nYou might want to add an autocommand. Alternatively, you can add modeline to your wikifile:\r\n\r\n    vim: ft=cwiki","5":"Copy the file into your ~\/.vim\/ftplugin\/ directory. To wikify particular file, load it and then type:\r\n\r\n    :set ft=cwiki\r\n\r\nYou might want to add an autocommand. Alternatively, you can add modeline to your wikifile:\r\n\r\n    vim: ft=cwiki","first_name":"Alex","6":"Alex","last_name":"Kunin","7":"Kunin","releases":[{"0":"2176","vim_version":"7.0","1":"7.0","script_version":"0.1a","2":"0.1a","version_comment":"Added visual wikiword selector: press <F3>, selector window will appear, current wikiword will be highlighted; move cursor to the desired wikiword and press <CR> to select it, or press <F3> to close the selector.","3":"Added visual wikiword selector: press <F3>, selector window will appear, current wikiword will be highlighted; move cursor to the desired wikiword and press <CR> to select it, or press <F3> to close the selector.","package":"cwiki.vim","4":"cwiki.vim","src_id":"8383","5":"8383","creation_date":"1204513216","6":"1204513216"},{"0":"2176","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"cwiki.vim","4":"cwiki.vim","src_id":"8376","5":"8376","creation_date":"1204384035","6":"1204384035"}]},"2175":{"script_id":"2175","0":"2175","script_name":"Railscasts Theme (GUI&256color)","1":"Railscasts Theme (GUI&256color)","script_type":"color scheme","2":"color scheme","summary":"A railscasts color theme that works in 256color terminals as well as gui","3":"A railscasts color theme that works in 256color terminals as well as gui","description":"This theme is based on Josh O'Rourke's Vim clone of the railscast\r\ntextmate theme ( vimscript #1995 ).  The key thing I have done here is\r\nsupply 256-color terminal equivalents for as many of the colors as\r\npossible, and fixed up a few of the funny tags for editing e-mails and\r\nsuch.\r\n\r\nYou can see a side-by-side comparison at http:\/\/zork.net\/~nick\/screenshots\/colorcomparison.png\r\n","4":"This theme is based on Josh O'Rourke's Vim clone of the railscast\r\ntextmate theme ( vimscript #1995 ).  The key thing I have done here is\r\nsupply 256-color terminal equivalents for as many of the colors as\r\npossible, and fixed up a few of the funny tags for editing e-mails and\r\nsuch.\r\n\r\nYou can see a side-by-side comparison at http:\/\/zork.net\/~nick\/screenshots\/colorcomparison.png\r\n","install_details":"To use for gvim:\r\n1: install this file as ~\/.vim\/colors\/railscasts.vim\r\n2: put \"colorscheme railscasts\" in your .gvimrc\r\n\r\nIf you are using Ubuntu, you can get the benefit of this theme in your\r\ngnome-terminals by taking the following steps:\r\n\r\n1: sudo apt-get install ncurses-term\r\n2: put the following in your .vimrc\r\n    if $COLORTERM == 'gnome-terminal'\r\n        set term=gnome-256color\r\n        colorscheme railscasts\r\n    else\r\n        colorscheme default\r\n    endif\r\n3: if you wish to use this with screen, add the following to your .screenrc:\r\n    attrcolor b \".I\"\r\n    termcapinfo xterm 'Co#256:AB=\\E[48;5;%dm:AF=\\E[38;5;%dm'\r\n    defbce \"on\"\r\n    term screen-256color-bce\r\n","5":"To use for gvim:\r\n1: install this file as ~\/.vim\/colors\/railscasts.vim\r\n2: put \"colorscheme railscasts\" in your .gvimrc\r\n\r\nIf you are using Ubuntu, you can get the benefit of this theme in your\r\ngnome-terminals by taking the following steps:\r\n\r\n1: sudo apt-get install ncurses-term\r\n2: put the following in your .vimrc\r\n    if $COLORTERM == 'gnome-terminal'\r\n        set term=gnome-256color\r\n        colorscheme railscasts\r\n    else\r\n        colorscheme default\r\n    endif\r\n3: if you wish to use this with screen, add the following to your .screenrc:\r\n    attrcolor b \".I\"\r\n    termcapinfo xterm 'Co#256:AB=\\E[48;5;%dm:AF=\\E[38;5;%dm'\r\n    defbce \"on\"\r\n    term screen-256color-bce\r\n","first_name":"Nick","6":"Nick","last_name":"Moffitt","7":"Moffitt","releases":[{"0":"2175","vim_version":"7.0","1":"7.0","script_version":"2.1","2":"2.1","version_comment":"Accidentally commented out the more specific ruby colors, and made the capitalization spelling color less obnoxious.  Also got rid of goofy if\/else block and just made all the definitions inline.  This helps uniformity greatly.","3":"Accidentally commented out the more specific ruby colors, and made the capitalization spelling color less obnoxious.  Also got rid of goofy if\/else block and just made all the definitions inline.  This helps uniformity greatly.","package":"railscasts.vim","4":"railscasts.vim","src_id":"8379","5":"8379","creation_date":"1204439772","6":"1204439772"},{"0":"2175","vim_version":"7.0","1":"7.0","script_version":"2.0","2":"2.0","version_comment":"Initial upload","3":"Initial upload","package":"railscasts.vim","4":"railscasts.vim","src_id":"8374","5":"8374","creation_date":"1204354872","6":"1204354872"}]},"2174":{"script_id":"2174","0":"2174","script_name":"repmo.vim","1":"repmo.vim","script_type":"utility","2":"utility","summary":"repeat motions for which a count was given","3":"repeat motions for which a count was given","description":"2016 Nov 22 started a new script at https:\/\/github.com\/Houl\/vim-repmo\r\n\r\nUsage by example:\r\n\r\n  Type \"5j\" (without quotes) and then \";\" to repeat \"5j\".\r\n  Type \"hjkl\" and then \";\", it still repeats \"5j\".\r\n  Type \",\" to do \"5k\" (go in reverse direction).\r\n  Type \"4k\" and then \";\" to repeat \"4k\".\r\n\r\n  The following motions (and scroll commands) are mapped per default:\r\n      j,k, h,l, Ctrl-E,Ctrl-Y, zh,zl\r\n\r\nCheck out:\r\n\r\n  Visual mode, e.g. \"V5j;;;;\"\r\n  \"f{char}\" followed by \";,\" -- it should still work\r\n  Operator pending mode with \";\" and \",\"\r\n\r\nCommands:\r\n\r\n  :RepmoMap {motion}|{reverse-motion} ...\r\n\r\n      Map {motion} to be repeatable with \";\".  Use {reverse-motion} for \",\".  Key notation is like in mappings.\r\n\r\nOptions, with defaults:\r\n\r\n  \" keys to be used for repeating (notation like in mappings), checked frequently:\r\n  :let repmo_key = \";\"\r\n  :let repmo_revkey = \",\"\r\n\r\n  \" map some default motions (argument string for :RepmoMap):\r\n  :let g:repmo_mapmotions = \"j|k h|l <C-E>|<C-Y> zh|zl\"\r\n\r\nNotes:\r\n\r\n  Your own remapping of a motion is silently discarded.\r\n  Your own remappings for \"f\", \"F\", \"t\" and \"T\" are kept.\r\n\r\n2009 Jun 03","4":"2016 Nov 22 started a new script at https:\/\/github.com\/Houl\/vim-repmo\r\n\r\nUsage by example:\r\n\r\n  Type \"5j\" (without quotes) and then \";\" to repeat \"5j\".\r\n  Type \"hjkl\" and then \";\", it still repeats \"5j\".\r\n  Type \",\" to do \"5k\" (go in reverse direction).\r\n  Type \"4k\" and then \";\" to repeat \"4k\".\r\n\r\n  The following motions (and scroll commands) are mapped per default:\r\n      j,k, h,l, Ctrl-E,Ctrl-Y, zh,zl\r\n\r\nCheck out:\r\n\r\n  Visual mode, e.g. \"V5j;;;;\"\r\n  \"f{char}\" followed by \";,\" -- it should still work\r\n  Operator pending mode with \";\" and \",\"\r\n\r\nCommands:\r\n\r\n  :RepmoMap {motion}|{reverse-motion} ...\r\n\r\n      Map {motion} to be repeatable with \";\".  Use {reverse-motion} for \",\".  Key notation is like in mappings.\r\n\r\nOptions, with defaults:\r\n\r\n  \" keys to be used for repeating (notation like in mappings), checked frequently:\r\n  :let repmo_key = \";\"\r\n  :let repmo_revkey = \",\"\r\n\r\n  \" map some default motions (argument string for :RepmoMap):\r\n  :let g:repmo_mapmotions = \"j|k h|l <C-E>|<C-Y> zh|zl\"\r\n\r\nNotes:\r\n\r\n  Your own remapping of a motion is silently discarded.\r\n  Your own remappings for \"f\", \"F\", \"t\" and \"T\" are kept.\r\n\r\n2009 Jun 03","install_details":"repmo is a plugin, put it into your ~\/.vim\/plugin folder","5":"repmo is a plugin, put it into your ~\/.vim\/plugin folder","first_name":"Andy","6":"Andy","last_name":"Wokula","7":"Wokula","releases":[{"0":"2174","vim_version":"7.0","1":"7.0","script_version":"0.5.3","2":"0.5.3","version_comment":"supposed to make it work with yankstack (1.0.5)","3":"supposed to make it work with yankstack (1.0.5)","package":"repmo.vim","4":"repmo.vim","src_id":"21988","5":"21988","creation_date":"1401999539","6":"1401999539"},{"0":"2174","vim_version":"7.0","1":"7.0","script_version":"0.5.1","2":"0.5.1","version_comment":"- make \"v5j\" work again after vim7.3.100 (:normal resets the count)","3":"- make \"v5j\" work again after vim7.3.100 (:normal resets the count)","package":"repmo.vim","4":"repmo.vim","src_id":"18691","5":"18691","creation_date":"1348609479","6":"1348609479"},{"0":"2174","vim_version":"7.0","1":"7.0","script_version":"0.5","2":"0.5","version_comment":"- :RepmoMap, new argument syntax\r\n- work in Vi-mode with <special>\r\n- added :sil! before  unmap ;  in case user unmapped \";\" by hand\r\n- :normal didn't work with <Space> (i.e. \" \")\r\n- let f\/F\/t\/T accept a count when unmapping","3":"- :RepmoMap, new argument syntax\r\n- work in Vi-mode with <special>\r\n- added :sil! before  unmap ;  in case user unmapped \";\" by hand\r\n- :normal didn't work with <Space> (i.e. \" \")\r\n- let f\/F\/t\/T accept a count when unmapping","package":"repmo.vim","4":"repmo.vim","src_id":"10720","5":"10720","creation_date":"1244057271","6":"1244057271"},{"0":"2174","vim_version":"7.0","1":"7.0","script_version":"0.3","2":"0.3","version_comment":"Initial upload","3":"Initial upload","package":"repmo.vim","4":"repmo.vim","src_id":"8373","5":"8373","creation_date":"1204346889","6":"1204346889"}]},"2173":{"script_id":"2173","0":"2173","script_name":"head.vim","1":"head.vim","script_type":"utility","2":"utility","summary":"easy reading file head or tail, with file prefix 'head:', 'tail:'.","3":"easy reading file head or tail, with file prefix 'head:', 'tail:'.","description":"Overview\r\n--------\r\nOpen file with file prefix 'head:','tail:',\r\nvim editor read file 10 rows from top, or bottom.\r\n(for example, head:sample.pl, tail:somedir\/app.conf)\r\n\r\ncommand example,\r\n  - Windows\r\n  (within vim)  : :e head;TEST.txt\r\n                : :e tail;TEST.txt\r\n\r\n  - Mac OSX, Unix, Liux\r\n  (command line): vim head:TEST.txt\r\n                : vim tail:TEST.txt\r\n\r\n  (within vim)  : :e head:TEST.txt\r\n                : :e tail:TEST.txt\r\n\r\n\r\nInstallation\r\n------------\r\n1. Copy the head.vim script to the $HOME\/.vim\/plugin or\r\n   the $HOME\/vimfiles\/plugin. Refer to the ':help add-plugin',\r\n   ':help add-global-plugin' and ':help runtimepath' topics for\r\n   more details about Vim plugins.\r\n2. Restart Vim.\r\n\r\n\r\nUsage\r\n-----\r\n(Windows)\r\n:e head;TEST.TXT  |  display 'TEST.TXT' head. (default 10 rows read.)\r\n:r head;TEST.TXT  |  read 'TEST.TXT' head, and insert at cursor position. (default 10 rows read.)\r\n:w head;TEST.TXT  |  update 'TEST.TXT' head with current buffer. (default 10 rows replaced.)\r\n\r\n:e tail;TEST.TXT  |  display 'TEST.TXT' tail. (default 10 rows read.)\r\n:r tail;TEST.TXT  |  read 'TEST.TXT' tail, and insert at cursor position. (default 10 rows read.)\r\n:w tail;TEST.TXT  |  update 'TEST.TXT' tail with current buffer. (default 10 rows replaced.)\r\n\r\n(OSX, Unix, Linux)\r\n:e head:TEST.TXT  |  display 'TEST.TXT' head. (default 10 rows read.)\r\n:r head:TEST.TXT  |  read 'TEST.TXT' head, and insert at cursor position. (default 10 rows read.)\r\n:w head:TEST.TXT  |  update 'TEST.TXT' head with current buffer. (default 10 rows replaced.)\r\n\r\n:e tail:TEST.TXT  |  display 'TEST.TXT' tail. (default 10 rows read.)\r\n:r tail:TEST.TXT  |  read 'TEST.TXT' tail, and insert at cursor position. (default 10 rows read.)\r\n:w tail:TEST.TXT  |  update 'TEST.TXT' tail with current buffer. (default 10 rows replaced.)\r\n\r\n\r\nPlugin Options\r\n--------------\r\ng:head_display_lines\r\n  customize number of lines of file reading.\r\n  below is setting example.\r\n\r\n      :let g:head_display_lines = 30\r\n\r\n  you will update this parameter by command 'Head',\r\n  for example,\r\n\r\n      :Head 30\r\n\r\n","4":"Overview\r\n--------\r\nOpen file with file prefix 'head:','tail:',\r\nvim editor read file 10 rows from top, or bottom.\r\n(for example, head:sample.pl, tail:somedir\/app.conf)\r\n\r\ncommand example,\r\n  - Windows\r\n  (within vim)  : :e head;TEST.txt\r\n                : :e tail;TEST.txt\r\n\r\n  - Mac OSX, Unix, Liux\r\n  (command line): vim head:TEST.txt\r\n                : vim tail:TEST.txt\r\n\r\n  (within vim)  : :e head:TEST.txt\r\n                : :e tail:TEST.txt\r\n\r\n\r\nInstallation\r\n------------\r\n1. Copy the head.vim script to the $HOME\/.vim\/plugin or\r\n   the $HOME\/vimfiles\/plugin. Refer to the ':help add-plugin',\r\n   ':help add-global-plugin' and ':help runtimepath' topics for\r\n   more details about Vim plugins.\r\n2. Restart Vim.\r\n\r\n\r\nUsage\r\n-----\r\n(Windows)\r\n:e head;TEST.TXT  |  display 'TEST.TXT' head. (default 10 rows read.)\r\n:r head;TEST.TXT  |  read 'TEST.TXT' head, and insert at cursor position. (default 10 rows read.)\r\n:w head;TEST.TXT  |  update 'TEST.TXT' head with current buffer. (default 10 rows replaced.)\r\n\r\n:e tail;TEST.TXT  |  display 'TEST.TXT' tail. (default 10 rows read.)\r\n:r tail;TEST.TXT  |  read 'TEST.TXT' tail, and insert at cursor position. (default 10 rows read.)\r\n:w tail;TEST.TXT  |  update 'TEST.TXT' tail with current buffer. (default 10 rows replaced.)\r\n\r\n(OSX, Unix, Linux)\r\n:e head:TEST.TXT  |  display 'TEST.TXT' head. (default 10 rows read.)\r\n:r head:TEST.TXT  |  read 'TEST.TXT' head, and insert at cursor position. (default 10 rows read.)\r\n:w head:TEST.TXT  |  update 'TEST.TXT' head with current buffer. (default 10 rows replaced.)\r\n\r\n:e tail:TEST.TXT  |  display 'TEST.TXT' tail. (default 10 rows read.)\r\n:r tail:TEST.TXT  |  read 'TEST.TXT' tail, and insert at cursor position. (default 10 rows read.)\r\n:w tail:TEST.TXT  |  update 'TEST.TXT' tail with current buffer. (default 10 rows replaced.)\r\n\r\n\r\nPlugin Options\r\n--------------\r\ng:head_display_lines\r\n  customize number of lines of file reading.\r\n  below is setting example.\r\n\r\n      :let g:head_display_lines = 30\r\n\r\n  you will update this parameter by command 'Head',\r\n  for example,\r\n\r\n      :Head 30\r\n\r\n","install_details":"1. Copy the head.vim script to the $HOME\/.vim\/plugin or\r\n   the $HOME\/vimfiles\/plugin. Refer to the ':help add-plugin',\r\n   ':help add-global-plugin' and ':help runtimepath' topics for\r\n   more details about Vim plugins.\r\n2. Restart Vim.","5":"1. Copy the head.vim script to the $HOME\/.vim\/plugin or\r\n   the $HOME\/vimfiles\/plugin. Refer to the ':help add-plugin',\r\n   ':help add-global-plugin' and ':help runtimepath' topics for\r\n   more details about Vim plugins.\r\n2. Restart Vim.","first_name":"omi","6":"omi","last_name":"taku","7":"taku","releases":[{"0":"2173","vim_version":"7.0","1":"7.0","script_version":"0.8","2":"0.8","version_comment":"Initial upload","3":"Initial upload","package":"head.vim","4":"head.vim","src_id":"8368","5":"8368","creation_date":"1204267754","6":"1204267754"}]},"2172":{"script_id":"2172","0":"2172","script_name":"abcdefg","1":"abcdefg","script_type":"utility","2":"utility","summary":"nothing is here。","3":"nothing is here。","description":"because i can not delete this uploaded file。","4":"because i can not delete this uploaded file。","install_details":"nothing","5":"nothing","first_name":"Hongli","6":"Hongli","last_name":"Gao","7":"Gao","releases":[{"0":"2172","vim_version":"6.0","1":"6.0","script_version":"0.3","2":"0.3","version_comment":"test2 update","3":"test2 update","package":"test","4":"test","src_id":"8366","5":"8366","creation_date":"1204238663","6":"1204238663"}]},"2171":{"script_id":"2171","0":"2171","script_name":"PERLDOC2","1":"PERLDOC2","script_type":"utility","2":"utility","summary":"Perldoc with sytnax highlighting in vim","3":"Perldoc with sytnax highlighting in vim","description":"This is PERLDOC2 for Vim. This plugin provides colouful experience for viewing perl documentation. The following pod items receive special highlighting treatment: verbatim text, headings and lists. The generated pod documents are kept in a cache directory, which allows browsing back and forth in your pod history.\r\n\r\nFor more information and some screenshots, see http:\/\/mechanicalrevolution.com\/blog\/perldoc_vim.html","4":"This is PERLDOC2 for Vim. This plugin provides colouful experience for viewing perl documentation. The following pod items receive special highlighting treatment: verbatim text, headings and lists. The generated pod documents are kept in a cache directory, which allows browsing back and forth in your pod history.\r\n\r\nFor more information and some screenshots, see http:\/\/mechanicalrevolution.com\/blog\/perldoc_vim.html","install_details":"1. Install the Pod::Simple::Vim module from CPAN.\r\n2. Install syntax\/perldoc.vim and plugin\/perldoc2.vim in the respective folders in your vim runtime path.\r\n3. Set the g:Perldoc_path variable in your vimrc to to point to a directory where the cached pod files will be stored (include trailing slash!).\r\n4. Use the Perldoc command, which requires one argument - the name of a module, e.g. \":Perldoc Test::More\".","5":"1. Install the Pod::Simple::Vim module from CPAN.\r\n2. Install syntax\/perldoc.vim and plugin\/perldoc2.vim in the respective folders in your vim runtime path.\r\n3. Set the g:Perldoc_path variable in your vimrc to to point to a directory where the cached pod files will be stored (include trailing slash!).\r\n4. Use the Perldoc command, which requires one argument - the name of a module, e.g. \":Perldoc Test::More\".","first_name":"Peter","6":"Peter","last_name":"Shangov","7":"Shangov","releases":[{"0":"2171","vim_version":"7.0","1":"7.0","script_version":"0.3","2":"0.3","version_comment":"Changed line-endings to unix style","3":"Changed line-endings to unix style","package":"PERLDOC2.zip","4":"PERLDOC2.zip","src_id":"11276","5":"11276","creation_date":"1251442632","6":"1251442632"},{"0":"2171","vim_version":"7.0","1":"7.0","script_version":"0.2","2":"0.2","version_comment":"Now uses the Pod::Simple::Vim module from CPAN and no longer requires vim with perl bindings","3":"Now uses the Pod::Simple::Vim module from CPAN and no longer requires vim with perl bindings","package":"PERLDOC2.zip","4":"PERLDOC2.zip","src_id":"10322","5":"10322","creation_date":"1238426643","6":"1238426643"}]},"2170":{"script_id":"2170","0":"2170","script_name":"osx_like","1":"osx_like","script_type":"color scheme","2":"color scheme","summary":"Color scheme that uses MacOS X like colors","3":"Color scheme that uses MacOS X like colors","description":"This color scheme is derived from the excellent sienna color scheme with some adjustments: There is only one color set for light background, and it looks best under gvim.\r\nI adjusted almost only the colors for line numbers, folding and status bar. A screen shot can be found at http:\/\/img443.imageshack.us\/my.php?image=osxlikejx7.gif\r\n\r\n(I am using GTK and Metacity themes from the Mac4Lin project. See http:\/\/sourceforge.net\/projects\/mac4lin )\r\n","4":"This color scheme is derived from the excellent sienna color scheme with some adjustments: There is only one color set for light background, and it looks best under gvim.\r\nI adjusted almost only the colors for line numbers, folding and status bar. A screen shot can be found at http:\/\/img443.imageshack.us\/my.php?image=osxlikejx7.gif\r\n\r\n(I am using GTK and Metacity themes from the Mac4Lin project. See http:\/\/sourceforge.net\/projects\/mac4lin )\r\n","install_details":"Put the file osx_like.vim into your ~\/.vim\/colors directory and activate it inside vim with\r\n:colors osx_like\r\n","5":"Put the file osx_like.vim into your ~\/.vim\/colors directory and activate it inside vim with\r\n:colors osx_like\r\n","first_name":"Martin","6":"Martin","last_name":"Winkler","7":"Winkler","releases":[{"0":"2170","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"osx_like.vim","4":"osx_like.vim","src_id":"8362","5":"8362","creation_date":"1204197562","6":"1204197562"}]},"2169":{"script_id":"2169","0":"2169","script_name":"jammy.vim","1":"jammy.vim","script_type":"color scheme","2":"color scheme","summary":"a great color scheme","3":"a great color scheme","description":"Working with it every day,and having fun~~~\r\nsend me email , if you want to say anything","4":"Working with it every day,and having fun~~~\r\nsend me email , if you want to say anything","install_details":"","5":"","first_name":"Jammy","6":"Jammy","last_name":"Lee","7":"Lee","releases":[{"0":"2169","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Small Fix","3":"Small Fix","package":"jammy.vim","4":"jammy.vim","src_id":"8471","5":"8471","creation_date":"1205980958","6":"1205980958"},{"0":"2169","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"jammy.vim","4":"jammy.vim","src_id":"8357","5":"8357","creation_date":"1204154808","6":"1204154808"}]},"2168":{"script_id":"2168","0":"2168","script_name":"Doxygen-via-Doxygen","1":"Doxygen-via-Doxygen","script_type":"utility","2":"utility","summary":"Generate Doxygen documentation","3":"Generate Doxygen documentation","description":"This script allows one to easily generate Doxygen documentation for C and C++ functions. Java could work, I haven\\\\\\'t tested.\r\n\r\nThere are many of these scripts available, but I\\\\\\'ve found most are commonly severely restricted by the fact that they parse the C\/C++ code themselves. Parsing C++ is hard. Very hard even. I wouldn\\\\\\'t consider parsing code myself, and especially not in VimScript.\r\n\r\nSo the trick is this: use Doxygen itself to parse the code, and then parse that output instead. Doxygen can output to XML, which is easily processed further. In this case by applying an XSL transformation. VimScript is used to glue all this together, e.g. move to the correct line number, hightlight\/remove the old tag.\r\n\r\nAs a result this script has the following nice features:\r\n- Parses C++ code correctly, regardless of layout, interspersed comments, etc. If Doxygen cannot parse it there\\\\\\'s little need to add a Doxygen tag. See www.doxygen.org for further details if you think you\\\\\\'ve found a bug.\r\n- Re-uses old Doxygen tags, i.e. generates new tags dropping old items and inserting new ones.\r\n\r\nThe maintenance bottleneck is the XSLT file, which should be kept up-to-date to the XML Doxygen outputs. Also, not all markup is kept intact. It is not my intention to make the XSLT file complete, I\\\\\\'m very pragmatic in that sense and I\\\\\\'ll only add what\\\\\\'s actually needed (at the moment: bold, italics, typewriter, (un)ordered lists).\r\n\r\nAt the moment I\\\\\\'m looking for developers proficient with both Vim and XSLT who want to give this a spin. This is *alpha* software. I\\\\\\'m releasing it purely in the spirit of Bazaar development. I have not thoroughly tested this script yet. Since I\\\\\\'m more than likely to use my own creation I\\\\\\'ll probably fix bugs and update new versions.\r\n\r\nFor all other users: feel free to download and use this. In my humble opinion it\\\\\\'ll serve you at least as good as the scripts already out there. But some hacking may be required.\r\n\r\nSources are licensed under the liberal MIT license.","4":"This script allows one to easily generate Doxygen documentation for C and C++ functions. Java could work, I haven\\\\\\'t tested.\r\n\r\nThere are many of these scripts available, but I\\\\\\'ve found most are commonly severely restricted by the fact that they parse the C\/C++ code themselves. Parsing C++ is hard. Very hard even. I wouldn\\\\\\'t consider parsing code myself, and especially not in VimScript.\r\n\r\nSo the trick is this: use Doxygen itself to parse the code, and then parse that output instead. Doxygen can output to XML, which is easily processed further. In this case by applying an XSL transformation. VimScript is used to glue all this together, e.g. move to the correct line number, hightlight\/remove the old tag.\r\n\r\nAs a result this script has the following nice features:\r\n- Parses C++ code correctly, regardless of layout, interspersed comments, etc. If Doxygen cannot parse it there\\\\\\'s little need to add a Doxygen tag. See www.doxygen.org for further details if you think you\\\\\\'ve found a bug.\r\n- Re-uses old Doxygen tags, i.e. generates new tags dropping old items and inserting new ones.\r\n\r\nThe maintenance bottleneck is the XSLT file, which should be kept up-to-date to the XML Doxygen outputs. Also, not all markup is kept intact. It is not my intention to make the XSLT file complete, I\\\\\\'m very pragmatic in that sense and I\\\\\\'ll only add what\\\\\\'s actually needed (at the moment: bold, italics, typewriter, (un)ordered lists).\r\n\r\nAt the moment I\\\\\\'m looking for developers proficient with both Vim and XSLT who want to give this a spin. This is *alpha* software. I\\\\\\'m releasing it purely in the spirit of Bazaar development. I have not thoroughly tested this script yet. Since I\\\\\\'m more than likely to use my own creation I\\\\\\'ll probably fix bugs and update new versions.\r\n\r\nFor all other users: feel free to download and use this. In my humble opinion it\\\\\\'ll serve you at least as good as the scripts already out there. But some hacking may be required.\r\n\r\nSources are licensed under the liberal MIT license.","install_details":"Extract the tarball somewhere where .vim files will be read at startup. Edit make_doxygen_tag.vim and edit (at least) the location of the XSLT file.\r\n\r\nYou need a XSLT processor and Doxygen!\r\n\r\nAs an XSLT processor I\\\\\\'d recommend libxml2\\\\\\'s xsltproc: www.libxml.org\r\nYou need a recent version of Doxygen (tested with 1.5.5).","5":"Extract the tarball somewhere where .vim files will be read at startup. Edit make_doxygen_tag.vim and edit (at least) the location of the XSLT file.\r\n\r\nYou need a XSLT processor and Doxygen!\r\n\r\nAs an XSLT processor I\\\\\\'d recommend libxml2\\\\\\'s xsltproc: www.libxml.org\r\nYou need a recent version of Doxygen (tested with 1.5.5).","first_name":"Niels","6":"Niels","last_name":"Aan de Brugh","7":"Aan de Brugh","releases":[{"0":"2168","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"make_doxytag.tar.gz","4":"make_doxytag.tar.gz","src_id":"8356","5":"8356","creation_date":"1204117054","6":"1204117054"}]},"2167":{"script_id":"2167","0":"2167","script_name":"dakota.vim","1":"dakota.vim","script_type":"syntax","2":"syntax","summary":"Syntax highlight file for DAKOTA Toolkit","3":"Syntax highlight file for DAKOTA Toolkit","description":"Syntax highlight file for DAKOTA Toolkit","4":"Syntax highlight file for DAKOTA Toolkit","install_details":"Place dakota.vim file in ~\/.vim\/syntax\/ folder.","5":"Place dakota.vim file in ~\/.vim\/syntax\/ folder.","first_name":"Jacobo","6":"Jacobo","last_name":"Diaz","7":"Diaz","releases":[{"0":"2167","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"dakota.vim","4":"dakota.vim","src_id":"8354","5":"8354","creation_date":"1204101547","6":"1204101547"}]},"2166":{"script_id":"2166","0":"2166","script_name":"patran.vim","1":"patran.vim","script_type":"syntax","2":"syntax","summary":"Syntax highlight file for MSC Patran","3":"Syntax highlight file for MSC Patran","description":"Syntax highlight file for MSC Patran","4":"Syntax highlight file for MSC Patran","install_details":"Place patran.vim file in ~\/.vim\/syntax\/ folder.","5":"Place patran.vim file in ~\/.vim\/syntax\/ folder.","first_name":"Jacobo","6":"Jacobo","last_name":"Diaz","7":"Diaz","releases":[{"0":"2166","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"patran.vim","4":"patran.vim","src_id":"8353","5":"8353","creation_date":"1204101398","6":"1204101398"}]},"2165":{"script_id":"2165","0":"2165","script_name":"ukrainian-enhanced.vim","1":"ukrainian-enhanced.vim","script_type":"utility","2":"utility","summary":"Ukrainian enhanced keymap","3":"Ukrainian enhanced keymap","description":"A keymap for Ukrainian (UTF-8).\r\n\r\nThe \"Ukrainian enhanced keymap\" simply allows you typing Ukrainian in Vim using jcuken Windows layout.\r\nThere is another ukrainian layout already in Vim. See keymap\\ukrainian-jcuken.vim script by Anatoli Sakhnik. But this one differs in way it maps numeric keys. It uses values usual for Windows users.\r\n\r\nSee also:\r\n\t:help keymap\r\n\t:help i_Ctrl-^\r\n\r\nI use this in my vimrc file:\r\n\" Ukrainian support\r\n\"set keymap=ukrainian-enhanced\r\n\" Default - latin layout\r\n\"set iminsert=0\r\n\" Default - latin layout in search mode\r\n\"set imsearch=0\r\n\r\nSee more details (in ukrainian) at http:\/\/korneliuk.blogspot.com\/2008\/03\/vim-localization.html","4":"A keymap for Ukrainian (UTF-8).\r\n\r\nThe \"Ukrainian enhanced keymap\" simply allows you typing Ukrainian in Vim using jcuken Windows layout.\r\nThere is another ukrainian layout already in Vim. See keymap\\ukrainian-jcuken.vim script by Anatoli Sakhnik. But this one differs in way it maps numeric keys. It uses values usual for Windows users.\r\n\r\nSee also:\r\n\t:help keymap\r\n\t:help i_Ctrl-^\r\n\r\nI use this in my vimrc file:\r\n\" Ukrainian support\r\n\"set keymap=ukrainian-enhanced\r\n\" Default - latin layout\r\n\"set iminsert=0\r\n\" Default - latin layout in search mode\r\n\"set imsearch=0\r\n\r\nSee more details (in ukrainian) at http:\/\/korneliuk.blogspot.com\/2008\/03\/vim-localization.html","install_details":"Just copy the file to $VIM\/vimfiles\/keymap\r\n\r\nTo start typing in cyrillic use command:\r\n:set keymap=ukrainian-enhanced\r\n\r\nTo toggle between languages use \"Ctrl-^\" in insert mode.","5":"Just copy the file to $VIM\/vimfiles\/keymap\r\n\r\nTo start typing in cyrillic use command:\r\n:set keymap=ukrainian-enhanced\r\n\r\nTo toggle between languages use \"Ctrl-^\" in insert mode.","first_name":"Ivan","6":"Ivan","last_name":"Korneliuk","7":"Korneliuk","releases":[{"0":"2165","vim_version":"6.0","1":"6.0","script_version":"1.3","2":"1.3","version_comment":"Added letter 'ґ' (mapped to '\\\\') and 'Ґ' (mapped to '|'). Thanks to @sergiigu","3":"Added letter 'ґ' (mapped to '\\\\') and 'Ґ' (mapped to '|'). Thanks to @sergiigu","package":"ukrainian-enhanced.vim","4":"ukrainian-enhanced.vim","src_id":"16748","5":"16748","creation_date":"1319660966","6":"1319660966"},{"0":"2165","vim_version":"6.0","1":"6.0","script_version":"1.2","2":"1.2","version_comment":"Script saved with unix line endings - so it can be used on all systems.","3":"Script saved with unix line endings - so it can be used on all systems.","package":"ukrainian-enhanced.vim","4":"ukrainian-enhanced.vim","src_id":"16552","5":"16552","creation_date":"1316419223","6":"1316419223"},{"0":"2165","vim_version":"6.0","1":"6.0","script_version":"1.1","2":"1.1","version_comment":"Fix letter names.","3":"Fix letter names.","package":"ukrainian-enhanced.vim","4":"ukrainian-enhanced.vim","src_id":"8349","5":"8349","creation_date":"1203947203","6":"1203947203"},{"0":"2165","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"ukrainian-enhanced.vim","4":"ukrainian-enhanced.vim","src_id":"8343","5":"8343","creation_date":"1203853942","6":"1203853942"}]},"2164":{"script_id":"2164","0":"2164","script_name":"renamec.vim","1":"renamec.vim","script_type":"utility","2":"utility","summary":"Renaming refactoring for C symbols using cscope","3":"Renaming refactoring for C symbols using cscope","description":"I have not used or modified this script in a long time. Christophe-Marie Duquesne has published a script that is based on this script here, you will probably want to have a look at http:\/\/www.vim.org\/scripts\/script.php?script_id=3028\r\n\r\nOriginal description:\r\nA simple function to rename a C (and possibly C++) symbols (functions\/variables) in multiple files using cscope information. Maybe just a starting point to adapt to your own needs, but at least works for me. \r\n\r\nWith the mapping below, one can start the renaming with \\r, enter the new name and it will be renamed (using a simple substitution on the lines returned by cscope) in all files. Needs an up to date cscope reference file (see below). \r\n\r\n","4":"I have not used or modified this script in a long time. Christophe-Marie Duquesne has published a script that is based on this script here, you will probably want to have a look at http:\/\/www.vim.org\/scripts\/script.php?script_id=3028\r\n\r\nOriginal description:\r\nA simple function to rename a C (and possibly C++) symbols (functions\/variables) in multiple files using cscope information. Maybe just a starting point to adapt to your own needs, but at least works for me. \r\n\r\nWith the mapping below, one can start the renaming with \\r, enter the new name and it will be renamed (using a simple substitution on the lines returned by cscope) in all files. Needs an up to date cscope reference file (see below). \r\n\r\n","install_details":"Put renamec.vim in your plugin directory. I use the following mapping\r\nnoremap <Leader>r :call Renamec()<cr>\r\nto start the renaming with \\r and\r\nmap <F12> :!cscope -R -k -b<CR>:cs reset<CR>\r\nto update the cscope reference file.","5":"Put renamec.vim in your plugin directory. I use the following mapping\r\nnoremap <Leader>r :call Renamec()<cr>\r\nto start the renaming with \\r and\r\nmap <F12> :!cscope -R -k -b<CR>:cs reset<CR>\r\nto update the cscope reference file.","first_name":"Bastian","6":"Bastian","last_name":"Mathes","7":"Mathes","releases":[{"0":"2164","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"renamec.vim","4":"renamec.vim","src_id":"8341","5":"8341","creation_date":"1203833912","6":"1203833912"}]},"2163":{"script_id":"2163","0":"2163","script_name":"GNU R","1":"GNU R","script_type":"utility","2":"utility","summary":"facilitates work with GNU R statistical package","3":"facilitates work with GNU R statistical package","description":"A. What it does:\r\npress F4 to process R files, press F5 to see the results saved in separate file ROutPut)\r\n\r\nB. Install:\r\nsimply copy the files from archive as follows:\r\n\r\n1) .vimrc goes to ~\/\r\n2) RVim.bat goes to ~\/.vim\/ REMEMBER to make it executable (chmod +x FILE)\r\n3) myfiletypes.vim goes to ~\/.vim\r\n4) myfunctions.vim goes to ~\/.vim\r\n5) r.vim goes to \/usr\/share\/vim\/**CURRENT VERSION**\/syntax\/\r\n6) vimSwap (and ROutput inside) goes to ~\/\r\n7) gpl.txt is for you to read.\r\n\r\nC. Licensing\r\nThis is released under GNU, copy attached.\r\n\r\nD. Acknowledgements\r\n\r\nThose files were inspired, and share some code with VimFiles for Ox by Vincent Nijs (originally posted http:\/\/www.jiscmail.ac.uk\/cgi-bin\/webadmin?A2=ind0112&L=ox-users&T=0&F=& S=&P=900). Credit when credit's due. Good job Mr Nijs\r\n","4":"A. What it does:\r\npress F4 to process R files, press F5 to see the results saved in separate file ROutPut)\r\n\r\nB. Install:\r\nsimply copy the files from archive as follows:\r\n\r\n1) .vimrc goes to ~\/\r\n2) RVim.bat goes to ~\/.vim\/ REMEMBER to make it executable (chmod +x FILE)\r\n3) myfiletypes.vim goes to ~\/.vim\r\n4) myfunctions.vim goes to ~\/.vim\r\n5) r.vim goes to \/usr\/share\/vim\/**CURRENT VERSION**\/syntax\/\r\n6) vimSwap (and ROutput inside) goes to ~\/\r\n7) gpl.txt is for you to read.\r\n\r\nC. Licensing\r\nThis is released under GNU, copy attached.\r\n\r\nD. Acknowledgements\r\n\r\nThose files were inspired, and share some code with VimFiles for Ox by Vincent Nijs (originally posted http:\/\/www.jiscmail.ac.uk\/cgi-bin\/webadmin?A2=ind0112&L=ox-users&T=0&F=& S=&P=900). Credit when credit's due. Good job Mr Nijs\r\n","install_details":"1) .vimrc goes to ~\/\r\n2) RVim.bat goes to ~\/.vim\/ REMEMBER to make it executable (chmod +x FILE)\r\n3) myfiletypes.vim goes to ~\/.vim\r\n4) myfunctions.vim goes to ~\/.vim\r\n5) r.vim goes to \/usr\/share\/vim\/**CURRENT VERSION**\/syntax\/\r\n6) vimSwap (and ROutput inside) goes to ~\/\r\n7) gpl.txt is for you to read.","5":"1) .vimrc goes to ~\/\r\n2) RVim.bat goes to ~\/.vim\/ REMEMBER to make it executable (chmod +x FILE)\r\n3) myfiletypes.vim goes to ~\/.vim\r\n4) myfunctions.vim goes to ~\/.vim\r\n5) r.vim goes to \/usr\/share\/vim\/**CURRENT VERSION**\/syntax\/\r\n6) vimSwap (and ROutput inside) goes to ~\/\r\n7) gpl.txt is for you to read.","first_name":"Szymon","6":"Szymon","last_name":"Wlazlowski","7":"Wlazlowski","releases":[{"0":"2163","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"r.myvimfiles.tar.gz","4":"r.myvimfiles.tar.gz","src_id":"8336","5":"8336","creation_date":"1203766004","6":"1203766004"}]},"2162":{"script_id":"2162","0":"2162","script_name":"F# Syntax","1":"F# Syntax","script_type":"syntax","2":"syntax","summary":"initial file based on ocaml and cs syntax files.","3":"initial file based on ocaml and cs syntax files.","description":"Syntax highlighting for the F# programming language. http:\/\/research.microsoft.com\/fsharp\/fsharp.aspx","4":"Syntax highlighting for the F# programming language. http:\/\/research.microsoft.com\/fsharp\/fsharp.aspx","install_details":"put it in your syntax directory. requires xml.vim and dtd.vim to be in the same directory.","5":"put it in your syntax directory. requires xml.vim and dtd.vim to be in the same directory.","first_name":"Choy","6":"Choy","last_name":"Rim","7":"Rim","releases":[{"0":"2162","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"fs.vim","4":"fs.vim","src_id":"8332","5":"8332","creation_date":"1203730187","6":"1203730187"}]},"2161":{"script_id":"2161","0":"2161","script_name":"DataStage (Server & Parallel)","1":"DataStage (Server & Parallel)","script_type":"syntax","2":"syntax","summary":"Syntax file for DataStage. Includes Universe Basic, DSX and Parallel functions.","3":"Syntax file for DataStage. Includes Universe Basic, DSX and Parallel functions.","description":"This script replaces old script vimscript #1310.\r\n\r\nIt includes vimscript #2143 for Universe Basic by Dan Sharp therefore you need that script too.","4":"This script replaces old script vimscript #1310.\r\n\r\nIt includes vimscript #2143 for Universe Basic by Dan Sharp therefore you need that script too.","install_details":"Put datastage.vim and unibasic.vim into syntax directory. You can also do appropriate changes in synmenu.vim and filetype.vim.","5":"Put datastage.vim and unibasic.vim into syntax directory. You can also do appropriate changes in synmenu.vim and filetype.vim.","first_name":"Lubomir","6":"Lubomir","last_name":"Husar","7":"Husar","releases":[{"0":"2161","vim_version":"6.0","1":"6.0","script_version":"1.1","2":"1.1","version_comment":"More PX functions added.","3":"More PX functions added.","package":"datastage.vim","4":"datastage.vim","src_id":"8358","5":"8358","creation_date":"1204172293","6":"1204172293"},{"0":"2161","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"datastage.vim","4":"datastage.vim","src_id":"8318","5":"8318","creation_date":"1203569651","6":"1203569651"}]},"2160":{"script_id":"2160","0":"2160","script_name":"VFT - VIM Form Toolkit","1":"VFT - VIM Form Toolkit","script_type":"utility","2":"utility","summary":"console-based forms with checkboxes, comboboxes, etc. (screenshot included)","3":"console-based forms with checkboxes, comboboxes, etc. (screenshot included)","description":"The package includes:\r\n\r\n    vft.vim - the library\r\n    vft-test.vim - simple plugin the utilizes the library\r\n\r\nScreenshot of vft-test in action can be found here:\r\n\r\n   http:\/\/javascript.cooldev.com\/alx\/vft.png\r\n\r\nLots of work yet to be done, but the library has minimal yet complete set of features that should simplify creation of simple forms.","4":"The package includes:\r\n\r\n    vft.vim - the library\r\n    vft-test.vim - simple plugin the utilizes the library\r\n\r\nScreenshot of vft-test in action can be found here:\r\n\r\n   http:\/\/javascript.cooldev.com\/alx\/vft.png\r\n\r\nLots of work yet to be done, but the library has minimal yet complete set of features that should simplify creation of simple forms.","install_details":"Unzip file into your ~\/.vim\/, or manually extract vft.vim to ~\/.vim\/autoload\/ and vft-test.vim to ~\/.vim\/plugin\/. Restart VIM (or :source ~\/.vim\/plugin\/vft-test.vim), hit <F5>.","5":"Unzip file into your ~\/.vim\/, or manually extract vft.vim to ~\/.vim\/autoload\/ and vft-test.vim to ~\/.vim\/plugin\/. Restart VIM (or :source ~\/.vim\/plugin\/vft-test.vim), hit <F5>.","first_name":"Alex","6":"Alex","last_name":"Kunin","7":"Kunin","releases":[{"0":"2160","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"vft.zip","4":"vft.zip","src_id":"8313","5":"8313","creation_date":"1203494542","6":"1203494542"}]},"2159":{"script_id":"2159","0":"2159","script_name":"timestamp","1":"timestamp","script_type":"utility","2":"utility","summary":"Add a timestamp to your source file","3":"Add a timestamp to your source file","description":"This SCRIPT will add\/update the timestamp when you close the source file.\r\nC++, C, Java, Makefile, rb, py, vim script is supported.","4":"This SCRIPT will add\/update the timestamp when you close the source file.\r\nC++, C, Java, Makefile, rb, py, vim script is supported.","install_details":"copy it to [plugin path].","5":"copy it to [plugin path].","first_name":"Peng","6":"Peng","last_name":"Du","7":"Du","releases":[{"0":"2159","vim_version":"7.0","1":"7.0","script_version":"1.1","2":"1.1","version_comment":"It's a script to insert a \"Last Change\" comment field in your source file.\r\nYou can modify the default behavior of this plug-in.\r\nTo add the support of new file type\r\nput this to your vimrc\r\nau BufWritePre *.cpp        call TimeStamp('\/\/')\r\nif the comment block in that language has both the begin and end symbol,\r\njust enjoy this\r\nau BufWritePre *.php          call TimeStamp('<?php \/\/', '?>')\r\n","3":"It's a script to insert a \"Last Change\" comment field in your source file.\r\nYou can modify the default behavior of this plug-in.\r\nTo add the support of new file type\r\nput this to your vimrc\r\nau BufWritePre *.cpp        call TimeStamp('\/\/')\r\nif the comment block in that language has both the begin and end symbol,\r\njust enjoy this\r\nau BufWritePre *.php          call TimeStamp('<?php \/\/', '?>')\r\n","package":"timestamp.vim","4":"timestamp.vim","src_id":"9480","5":"9480","creation_date":"1226345405","6":"1226345405"},{"0":"2159","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"timestamp.vim","4":"timestamp.vim","src_id":"8311","5":"8311","creation_date":"1203446782","6":"1203446782"}]},"2158":{"script_id":"2158","0":"2158","script_name":"diffchanges.vim","1":"diffchanges.vim","script_type":"utility","2":"utility","summary":"Show changes made to current buffer since the last save","3":"Show changes made to current buffer since the last save","description":"Show changes made to current buffer since the last save. This plugin is based from an example in the Hacking Vim book. The differences are that this functionality is in the form of a plugin, is a bit more robust, and can be toggled.","4":"Show changes made to current buffer since the last save. This plugin is based from an example in the Hacking Vim book. The differences are that this functionality is in the form of a plugin, is a bit more robust, and can be toggled.","install_details":"Extract to ~\/.vim","5":"Extract to ~\/.vim","first_name":"Jeremy","6":"Jeremy","last_name":"Cantrell","7":"Cantrell","releases":[{"0":"2158","vim_version":"7.0","1":"7.0","script_version":"346dae2","2":"346dae2","version_comment":"Make sure filename is properly escaped","3":"Make sure filename is properly escaped","package":"jmcantrell-vim-diffchanges-346dae2.zip","4":"jmcantrell-vim-diffchanges-346dae2.zip","src_id":"17578","5":"17578","creation_date":"1331335716","6":"1331335716"},{"0":"2158","vim_version":"7.0","1":"7.0","script_version":"0.5","2":"0.5","version_comment":"The new command was defined wrong","3":"The new command was defined wrong","package":"jmcantrell-vim-diffchanges-a755db9.zip","4":"jmcantrell-vim-diffchanges-a755db9.zip","src_id":"15299","5":"15299","creation_date":"1301192661","6":"1301192661"},{"0":"2158","vim_version":"7.0","1":"7.0","script_version":"0.4","2":"0.4","version_comment":"Added command for writing patch directly. (Thanks to iceroot for the idea)","3":"Added command for writing patch directly. (Thanks to iceroot for the idea)","package":"jmcantrell-vim-diffchanges-dedd1ba.zip","4":"jmcantrell-vim-diffchanges-dedd1ba.zip","src_id":"15296","5":"15296","creation_date":"1301174562","6":"1301174562"},{"0":"2158","vim_version":"7.0","1":"7.0","script_version":"0.3","2":"0.3","version_comment":"Add docs, repackage","3":"Add docs, repackage","package":"jmcantrell-vim-diffchanges-3b047fc.zip","4":"jmcantrell-vim-diffchanges-3b047fc.zip","src_id":"15175","5":"15175","creation_date":"1299561349","6":"1299561349"},{"0":"2158","vim_version":"7.0","1":"7.0","script_version":"0.2.6","2":"0.2.6","version_comment":"Fixed problem with diff mode where diff was not started on the first line.","3":"Fixed problem with diff mode where diff was not started on the first line.","package":"diffchanges.vim","4":"diffchanges.vim","src_id":"11831","5":"11831","creation_date":"1259544389","6":"1259544389"},{"0":"2158","vim_version":"7.0","1":"7.0","script_version":"0.2.6","2":"0.2.6","version_comment":"Fixed problem with diff mode where diff was not started on the first line.","3":"Fixed problem with diff mode where diff was not started on the first line.","package":"diffchanges.vim","4":"diffchanges.vim","src_id":"11830","5":"11830","creation_date":"1259544388","6":"1259544388"},{"0":"2158","vim_version":"7.0","1":"7.0","script_version":"0.2.5","2":"0.2.5","version_comment":"Improved some of the error checking and fixed a few regressions from the previous upload.","3":"Improved some of the error checking and fixed a few regressions from the previous upload.","package":"diffchanges.vim","4":"diffchanges.vim","src_id":"8429","5":"8429","creation_date":"1205104284","6":"1205104284"},{"0":"2158","vim_version":"7.0","1":"7.0","script_version":"0.2.4","2":"0.2.4","version_comment":"Added a check to make sure the script only loads in Vim 7 (Thanks to Scott Urban).","3":"Added a check to make sure the script only loads in Vim 7 (Thanks to Scott Urban).","package":"diffchanges.vim","4":"diffchanges.vim","src_id":"8426","5":"8426","creation_date":"1204966720","6":"1204966720"},{"0":"2158","vim_version":"7.0","1":"7.0","script_version":"0.2.3","2":"0.2.3","version_comment":"Made it easier to :source the plugin after it has already been loaded.","3":"Made it easier to :source the plugin after it has already been loaded.","package":"diffchanges.vim","4":"diffchanges.vim","src_id":"8371","5":"8371","creation_date":"1204289607","6":"1204289607"},{"0":"2158","vim_version":"7.0","1":"7.0","script_version":"0.2.2","2":"0.2.2","version_comment":"Bug fixes and a few enhancements (Thanks to Ben Armston).","3":"Bug fixes and a few enhancements (Thanks to Ben Armston).","package":"diffchanges.vim","4":"diffchanges.vim","src_id":"8369","5":"8369","creation_date":"1204272981","6":"1204272981"},{"0":"2158","vim_version":"7.0","1":"7.0","script_version":"0.2.1","2":"0.2.1","version_comment":"Added another mode for viewing a patch of the changes made since last save","3":"Added another mode for viewing a patch of the changes made since last save","package":"diffchanges.vim","4":"diffchanges.vim","src_id":"8337","5":"8337","creation_date":"1203808130","6":"1203808130"},{"0":"2158","vim_version":"7.0","1":"7.0","script_version":"0.2","2":"0.2","version_comment":"Made functions, variables, and mappings \"script-friendly\". Thanks #vim!","3":"Made functions, variables, and mappings \"script-friendly\". Thanks #vim!","package":"diffchanges.vim","4":"diffchanges.vim","src_id":"8331","5":"8331","creation_date":"1203730171","6":"1203730171"},{"0":"2158","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"diffchanges.vim","4":"diffchanges.vim","src_id":"8294","5":"8294","creation_date":"1203297177","6":"1203297177"}]},"2157":{"script_id":"2157","0":"2157","script_name":"altfile","1":"altfile","script_type":"utility","2":"utility","summary":"easy switching between related files","3":"easy switching between related files","description":"Screenshot: http:\/\/altfile.googlecode.com\/files\/shot1.png\r\nProject site: http:\/\/code.google.com\/p\/altfile\/\r\n\r\n-----\r\n\r\nSuppose we have a project which resides in a \"proj\" directory. Content of that directory might look like this:\r\n\r\n  proj\/classes\/Class1.php\r\n  proj\/classes\/Class2.php\r\n  proj\/classes\/Namespace\/Class3.php\r\n  proj\/tpl\/Class1.html\r\n  proj\/tpl\/Class2.html\r\n  proj\/tpl\/Namespace\/Class3.html\r\n  proj\/tests\/Class1.phpt\r\n  proj\/tests\/Class2.phpt\r\n  proj\/tests\/Namespace\/Class3.phpt\r\n\r\nCreate \"proj\/.altfile\" and put these lines inside:\r\n\r\n  class: classes\/{MATCH}.php\r\n  template: tpl\/{MATCH}.html\r\n  test: tests\/{MATCH}.phpt\r\n\r\nNow load \"proj\/classes\/Class1.php\" and hit the hot key. Menu will\r\nappear:\r\n\r\n  class  [template]  test\r\n\r\nNow you can use it as any other wild menu: cursor keys, <CR>, <Esc>.\r\n\r\nBy default previously active item is highilighted (works like Alt-Tab for Windows or Cmd-Tab for Mac OS X). So, to quickly switch between two files all you have to do is <M-Tab><CR>.\r\n\r\nNow load \"proj\/tpl\/Class4.html\" - it does not exist, and you'll get empty window. Hit <M-Tab>, select \"class\" and hit <CR> - VIM will create new buffer for (still non-existing) \"proj\/classes\/Class4.php\". Ta-dah! Actually, this is my main reason for creating this plugin.\r\n\r\nNote that it DOES NOT matter what is your current directory: you can cd to whatever place you want. But it DOES matter where \".altfile\" is, becase patterns inside it are relative to its placement.\r\n\r\nTo show visual file selector hit <F3>. Use movement\/cursor keys to highlight a file; <CR> loads file; <Tab> switches between labels.\r\n","4":"Screenshot: http:\/\/altfile.googlecode.com\/files\/shot1.png\r\nProject site: http:\/\/code.google.com\/p\/altfile\/\r\n\r\n-----\r\n\r\nSuppose we have a project which resides in a \"proj\" directory. Content of that directory might look like this:\r\n\r\n  proj\/classes\/Class1.php\r\n  proj\/classes\/Class2.php\r\n  proj\/classes\/Namespace\/Class3.php\r\n  proj\/tpl\/Class1.html\r\n  proj\/tpl\/Class2.html\r\n  proj\/tpl\/Namespace\/Class3.html\r\n  proj\/tests\/Class1.phpt\r\n  proj\/tests\/Class2.phpt\r\n  proj\/tests\/Namespace\/Class3.phpt\r\n\r\nCreate \"proj\/.altfile\" and put these lines inside:\r\n\r\n  class: classes\/{MATCH}.php\r\n  template: tpl\/{MATCH}.html\r\n  test: tests\/{MATCH}.phpt\r\n\r\nNow load \"proj\/classes\/Class1.php\" and hit the hot key. Menu will\r\nappear:\r\n\r\n  class  [template]  test\r\n\r\nNow you can use it as any other wild menu: cursor keys, <CR>, <Esc>.\r\n\r\nBy default previously active item is highilighted (works like Alt-Tab for Windows or Cmd-Tab for Mac OS X). So, to quickly switch between two files all you have to do is <M-Tab><CR>.\r\n\r\nNow load \"proj\/tpl\/Class4.html\" - it does not exist, and you'll get empty window. Hit <M-Tab>, select \"class\" and hit <CR> - VIM will create new buffer for (still non-existing) \"proj\/classes\/Class4.php\". Ta-dah! Actually, this is my main reason for creating this plugin.\r\n\r\nNote that it DOES NOT matter what is your current directory: you can cd to whatever place you want. But it DOES matter where \".altfile\" is, becase patterns inside it are relative to its placement.\r\n\r\nTo show visual file selector hit <F3>. Use movement\/cursor keys to highlight a file; <CR> loads file; <Tab> switches between labels.\r\n","install_details":"Copy this file to your ~\/.vim\/plugin\/ folder. Bind some key to AltFile_ShowMenu() and AltFile_ShowSelector():\r\n\r\n    nmap <expr> <M-Tab> AltFile_ShowMenu()\r\n    nmap <F3> :call AltFile_ShowSelector()<CR>\r\n\r\nMake sure that wildmenu is enabled:\r\n\r\n    set wildmenu","5":"Copy this file to your ~\/.vim\/plugin\/ folder. Bind some key to AltFile_ShowMenu() and AltFile_ShowSelector():\r\n\r\n    nmap <expr> <M-Tab> AltFile_ShowMenu()\r\n    nmap <F3> :call AltFile_ShowSelector()<CR>\r\n\r\nMake sure that wildmenu is enabled:\r\n\r\n    set wildmenu","first_name":"Alex","6":"Alex","last_name":"Kunin","7":"Kunin","releases":[{"0":"2157","vim_version":"7.0","1":"7.0","script_version":"0.2a","2":"0.2a","version_comment":"No more \":drop\" (i.e. no more GUI dependency). File load\/activation code is smarter now. Uncommented forgotten try...catch block. Removed all inline docs, added link to the project site.","3":"No more \":drop\" (i.e. no more GUI dependency). File load\/activation code is smarter now. Uncommented forgotten try...catch block. Removed all inline docs, added link to the project site.","package":"altfile-0.2a.zip","4":"altfile-0.2a.zip","src_id":"8372","5":"8372","creation_date":"1204333370","6":"1204333370"},{"0":"2157","vim_version":"7.0","1":"7.0","script_version":"0.2","2":"0.2","version_comment":"Added visual file selector (resembles BufExplorer; also, some tricks were borrowed from source code of that really nice script).\r\n","3":"Added visual file selector (resembles BufExplorer; also, some tricks were borrowed from source code of that really nice script).\r\n","package":"altfile-0.2.zip","4":"altfile-0.2.zip","src_id":"8352","5":"8352","creation_date":"1204015902","6":"1204015902"},{"0":"2157","vim_version":"7.0","1":"7.0","script_version":"0.1e","2":"0.1e","version_comment":"Autoload support and \"write-plugin\" guidelines (thanks to Thomas Link for advices). Couple of minor bugs fixed.\r\n","3":"Autoload support and \"write-plugin\" guidelines (thanks to Thomas Link for advices). Couple of minor bugs fixed.\r\n","package":"altfile.vim","4":"altfile.vim","src_id":"8329","5":"8329","creation_date":"1203680750","6":"1203680750"},{"0":"2157","vim_version":"7.0","1":"7.0","script_version":"0.1d","2":"0.1d","version_comment":"Now wildmenu is used as \"engine\", so look & feel are much better now. No more numeric shortcats, however. Lots of code cleanup.\r\n","3":"Now wildmenu is used as \"engine\", so look & feel are much better now. No more numeric shortcats, however. Lots of code cleanup.\r\n","package":"altfile.vim","4":"altfile.vim","src_id":"8306","5":"8306","creation_date":"1203386397","6":"1203386397"},{"0":"2157","vim_version":"7.0","1":"7.0","script_version":"0.1c","2":"0.1c","version_comment":"Default choice now mimics Alt-Tab (Cmd-Tab for Mac users), i.e. hitting the hot key and then <CR> will cycle between last two files. Visual adjustments: current file is square brakets, and asterisk indicates default choice.\r\n","3":"Default choice now mimics Alt-Tab (Cmd-Tab for Mac users), i.e. hitting the hot key and then <CR> will cycle between last two files. Visual adjustments: current file is square brakets, and asterisk indicates default choice.\r\n","package":"altfile.vim","4":"altfile.vim","src_id":"8298","5":"8298","creation_date":"1203311165","6":"1203311165"},{"0":"2157","vim_version":"7.0","1":"7.0","script_version":"0.1b","2":"0.1b","version_comment":"If selected file is already visible in some window, the script will activate it.\r\n","3":"If selected file is already visible in some window, the script will activate it.\r\n","package":"altfile.vim","4":"altfile.vim","src_id":"8296","5":"8296","creation_date":"1203308317","6":"1203308317"},{"0":"2157","vim_version":"7.0","1":"7.0","script_version":"0.1a","2":"0.1a","version_comment":"When GUI is available, dialog forced to be console-friendly, i.e. no GUI window is poping up.\r\n","3":"When GUI is available, dialog forced to be console-friendly, i.e. no GUI window is poping up.\r\n","package":"altfile.vim","4":"altfile.vim","src_id":"8288","5":"8288","creation_date":"1203197277","6":"1203197277"},{"0":"2157","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"altfile.vim","4":"altfile.vim","src_id":"8286","5":"8286","creation_date":"1203156886","6":"1203156886"}]},"2156":{"script_id":"2156","0":"2156","script_name":"leo256","1":"leo256","script_type":"color scheme","2":"color scheme","summary":"A beautiful theme for dark\/black background (256 colors, gui + term)","3":"A beautiful theme for dark\/black background (256 colors, gui + term)","description":"This is my multipurpose everyday theme I use for coding (and everything else :-).\r\n\r\nIt focuses on high readability and colors harmony.\r\n\r\nGood results with most programming languages:\r\n  - Ruby\r\n  - Lua\r\n  - Scala\r\n  - Clojure\r\n  - PHP\r\n  - HTML\r\n  - ...\r\n\r\nHave a look:\r\n\r\nhttp:\/\/www.leonini.net\/vim_leo_theme_0.94.png \r\nhttp:\/\/www.leonini.net\/vim_leo_theme_0.93.png\r\nhttp:\/\/www.leonini.net\/vim_leo_theme_0.9.png\r\n\r\nold:\r\n\r\nhttp:\/\/www.leonini.net\/vim_leo_theme.0.2.png\r\nhttp:\/\/www.leonini.net\/vim_leo_theme.0.32.png\r\nhttp:\/\/www.leonini.net\/vim_leo_theme.0.40.png\r\nhttp:\/\/www.leonini.net\/vim_leo_theme2.0.40.png\r\nhttp:\/\/www.leonini.net\/vim_leo_theme_0.8.png\r\nhttp:\/\/www.leonini.net\/vim_leo_theme_0.82.png\r\n","4":"This is my multipurpose everyday theme I use for coding (and everything else :-).\r\n\r\nIt focuses on high readability and colors harmony.\r\n\r\nGood results with most programming languages:\r\n  - Ruby\r\n  - Lua\r\n  - Scala\r\n  - Clojure\r\n  - PHP\r\n  - HTML\r\n  - ...\r\n\r\nHave a look:\r\n\r\nhttp:\/\/www.leonini.net\/vim_leo_theme_0.94.png \r\nhttp:\/\/www.leonini.net\/vim_leo_theme_0.93.png\r\nhttp:\/\/www.leonini.net\/vim_leo_theme_0.9.png\r\n\r\nold:\r\n\r\nhttp:\/\/www.leonini.net\/vim_leo_theme.0.2.png\r\nhttp:\/\/www.leonini.net\/vim_leo_theme.0.32.png\r\nhttp:\/\/www.leonini.net\/vim_leo_theme.0.40.png\r\nhttp:\/\/www.leonini.net\/vim_leo_theme2.0.40.png\r\nhttp:\/\/www.leonini.net\/vim_leo_theme_0.8.png\r\nhttp:\/\/www.leonini.net\/vim_leo_theme_0.82.png\r\n","install_details":"Just copy leo.vim into ~\/.vim\/colors.\r\n\r\nTo use it, issue ':colorscheme leo' in vim and you're done (put 'colorscheme leo' in you .vimrc for a permanent setting).\r\n\r\nIf your term reports only 8 colors ('tput colors') you can try to set in you .vimrc\r\nset t_Co=256\r\n\r\nRecent xterm, Eterm, gnome-terminal and konsole support 256 colors. \r\n\r\nBackground color of your terminal should be deep black. Colors will appear a little dark on Eterm (compare with screenshots if needed).","5":"Just copy leo.vim into ~\/.vim\/colors.\r\n\r\nTo use it, issue ':colorscheme leo' in vim and you're done (put 'colorscheme leo' in you .vimrc for a permanent setting).\r\n\r\nIf your term reports only 8 colors ('tput colors') you can try to set in you .vimrc\r\nset t_Co=256\r\n\r\nRecent xterm, Eterm, gnome-terminal and konsole support 256 colors. \r\n\r\nBackground color of your terminal should be deep black. Colors will appear a little dark on Eterm (compare with screenshots if needed).","first_name":"Lorenzo","6":"Lorenzo","last_name":"Leonini","7":"Leonini","releases":[{"0":"2156","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"The long awaited version 1.0 ;)                                               \r\n\r\n- Tab colors\r\n- Vim 7.3 addition","3":"The long awaited version 1.0 ;)                                               \r\n\r\n- Tab colors\r\n- Vim 7.3 addition","package":"leo.vim","4":"leo.vim","src_id":"14339","5":"14339","creation_date":"1290349446","6":"1290349446"},{"0":"2156","vim_version":"6.0","1":"6.0","script_version":"0.94","2":"0.94","version_comment":"Folding color correction.","3":"Folding color correction.","package":"leo.vim","4":"leo.vim","src_id":"12796","5":"12796","creation_date":"1270688365","6":"1270688365"},{"0":"2156","vim_version":"6.0","1":"6.0","script_version":"0.93","2":"0.93","version_comment":"Console and GUI are deliberately slightly differents (see 0.93 screenshot)\r\nPreference for a dark black in console and a more lighter black in GUI.","3":"Console and GUI are deliberately slightly differents (see 0.93 screenshot)\r\nPreference for a dark black in console and a more lighter black in GUI.","package":"leo.vim","4":"leo.vim","src_id":"12750","5":"12750","creation_date":"1270018116","6":"1270018116"},{"0":"2156","vim_version":"6.0","1":"6.0","script_version":"0.92","2":"0.92","version_comment":"- Fixed visual in GUI mode\r\n- Dark line numbers\r\n","3":"- Fixed visual in GUI mode\r\n- Dark line numbers\r\n","package":"leo.vim","4":"leo.vim","src_id":"12742","5":"12742","creation_date":"1269966955","6":"1269966955"},{"0":"2156","vim_version":"6.0","1":"6.0","script_version":"0.91","2":"0.91","version_comment":"fixed cursor color with MatchParen","3":"fixed cursor color with MatchParen","package":"leo.vim","4":"leo.vim","src_id":"12548","5":"12548","creation_date":"1267597386","6":"1267597386"},{"0":"2156","vim_version":"6.0","1":"6.0","script_version":"0.9","2":"0.9","version_comment":"- more blue (blue <=> green swap)\r\n- lot of changes, some may prefer previous version\r\n","3":"- more blue (blue <=> green swap)\r\n- lot of changes, some may prefer previous version\r\n","package":"leo.vim","4":"leo.vim","src_id":"10845","5":"10845","creation_date":"1245136824","6":"1245136824"},{"0":"2156","vim_version":"6.0","1":"6.0","script_version":"0.82","2":"0.82","version_comment":"- menu backgrounf lighter\r\n- LineNr\r\n- gui comments in italic\r\n- invisible chars\r\n- status bar\r\n- add MatchParen\r\n- add Underlined","3":"- menu backgrounf lighter\r\n- LineNr\r\n- gui comments in italic\r\n- invisible chars\r\n- status bar\r\n- add MatchParen\r\n- add Underlined","package":"leo.vim","4":"leo.vim","src_id":"9963","5":"9963","creation_date":"1234521009","6":"1234521009"},{"0":"2156","vim_version":"6.0","1":"6.0","script_version":"0.8","2":"0.8","version_comment":"GUI fix and full synchronization\r\ncolor < 16 fix (all in 256 code)\r\nlighter comments\r\nboolean and number more visible\r\n","3":"GUI fix and full synchronization\r\ncolor < 16 fix (all in 256 code)\r\nlighter comments\r\nboolean and number more visible\r\n","package":"leo.vim","4":"leo.vim","src_id":"9917","5":"9917","creation_date":"1233792647","6":"1233792647"},{"0":"2156","vim_version":"6.0","1":"6.0","script_version":"0.6","2":"0.6","version_comment":"GUI synchro (almost) done,\r\nMinor changes","3":"GUI synchro (almost) done,\r\nMinor changes","package":"leo.vim","4":"leo.vim","src_id":"9609","5":"9609","creation_date":"1228341397","6":"1228341397"},{"0":"2156","vim_version":"6.0","1":"6.0","script_version":"0.6","2":"0.6","version_comment":"GUI synchro (almost) done\r\nMinor changes","3":"GUI synchro (almost) done\r\nMinor changes","package":"leo.vim","4":"leo.vim","src_id":"9607","5":"9607","creation_date":"1228338096","6":"1228338096"},{"0":"2156","vim_version":"6.0","1":"6.0","script_version":"0.5","2":"0.5","version_comment":"Lot of changes, including:\r\n- search highlight\r\n- Ligther vertical separation\r\n- Folding\r\n- Better diff\r\n- Better pmenu\r\n- Uniformisation between status bar, tabs and pmenu\r\n...","3":"Lot of changes, including:\r\n- search highlight\r\n- Ligther vertical separation\r\n- Folding\r\n- Better diff\r\n- Better pmenu\r\n- Uniformisation between status bar, tabs and pmenu\r\n...","package":"leo.vim","4":"leo.vim","src_id":"9119","5":"9119","creation_date":"1218627120","6":"1218627120"},{"0":"2156","vim_version":"6.0","1":"6.0","script_version":"0.31","2":"0.31","version_comment":"- Added coloration for popup menu (omni-completion, ...) (thanks Ryan)\r\n- Added coloration for tabs\r\n\r\n(all parts of vim should be themed now)","3":"- Added coloration for popup menu (omni-completion, ...) (thanks Ryan)\r\n- Added coloration for tabs\r\n\r\n(all parts of vim should be themed now)","package":"leo.vim","4":"leo.vim","src_id":"8999","5":"8999","creation_date":"1216723938","6":"1216723938"},{"0":"2156","vim_version":"6.0","1":"6.0","script_version":"0.3","2":"0.3","version_comment":"- General improvements\r\n- Correct colors on normal xterm\r\n- Preliminary GUI version","3":"- General improvements\r\n- Correct colors on normal xterm\r\n- Preliminary GUI version","package":"leo.vim","4":"leo.vim","src_id":"8996","5":"8996","creation_date":"1216708859","6":"1216708859"},{"0":"2156","vim_version":"6.0","1":"6.0","script_version":"0.22","2":"0.22","version_comment":"still less bold, little improvements","3":"still less bold, little improvements","package":"leo.vim","4":"leo.vim","src_id":"8882","5":"8882","creation_date":"1215016342","6":"1215016342"},{"0":"2156","vim_version":"6.0","1":"6.0","script_version":"0.21","2":"0.21","version_comment":"less bold, little improvements","3":"less bold, little improvements","package":"leo.vim","4":"leo.vim","src_id":"8340","5":"8340","creation_date":"1203828989","6":"1203828989"},{"0":"2156","vim_version":"6.0","1":"6.0","script_version":"0.2","2":"0.2","version_comment":"Ful theme, details, diff mode, string background","3":"Ful theme, details, diff mode, string background","package":"leo.vim","4":"leo.vim","src_id":"8310","5":"8310","creation_date":"1203433601","6":"1203433601"},{"0":"2156","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"leo.vim","4":"leo.vim","src_id":"8285","5":"8285","creation_date":"1203132248","6":"1203132248"}]},"2155":{"script_id":"2155","0":"2155","script_name":"greenvision","1":"greenvision","script_type":"color scheme","2":"color scheme","summary":"green colorscheme for GUI, 256 and 88 color terminals","3":"green colorscheme for GUI, 256 and 88 color terminals","description":"A ultra low contrast dark colorscheme.\r\n","4":"A ultra low contrast dark colorscheme.\r\n","install_details":"Put it in .vim\/colors\/ directory","5":"Put it in .vim\/colors\/ directory","first_name":"Paul B.","6":"Paul B.","last_name":"Mahol","7":"Mahol","releases":[{"0":"2155","vim_version":"7.0","1":"7.0","script_version":"2.0","2":"2.0","version_comment":"General cleanup and small color improvements","3":"General cleanup and small color improvements","package":"greenvision.vim","4":"greenvision.vim","src_id":"8759","5":"8759","creation_date":"1212691410","6":"1212691410"}]},"2154":{"script_id":"2154","0":"2154","script_name":"marvim","1":"marvim","script_type":"utility","2":"utility","summary":"Macro Persistent Storage and Shareable Repository for VIM","3":"Macro Persistent Storage and Shareable Repository for VIM","description":"MARVIM - MAcro Repository for VIM\r\n\r\n\"Give your most complex macros a name and store it for future recall and use\"\r\n\r\nProblem statement(s): \r\n-------------------------------\r\n   * Can not remember those complex VIM macro sequences you use frequently?\r\n   * Wish you could save those macros beyond your immediate session? \r\n   * Wish you could share your VIM macros with each other?\r\n   * Why not templates as well in the same script?\r\n\r\nFeatures\r\n------------\r\n    * Recording of VIM macros into persistent storage for future use\r\n    * Auto-complete based recursive search and load of stored VIM macros\r\n    * Visually select and save templates into persistent storage\r\n    * Macro namespaces, to permit organization of macros \r\n    * Support for a default namespace based on filetype\r\n    * Supports a shared macro repository for a team on a shared directory\r\n    * Macro menu items in GVIM version for all main actions\r\n\r\nHotkeys \r\n-----------\r\n<F2>            - Find and execute a macro or insert template from repository\r\nVisual <F2> - Replays last macro for each line selected\r\n<F3>             - Save default macro register by name to the macro repository \r\nVisual <F3>  - Save selection as template by name to the macro repository \r\n<Tab>            - On the Macro command line for cycling through autocomplete\r\n<Control>+D - On the Macro command line for listing autocomplete options\r\n\r\nUsage:\r\n----------\r\no Store a new macro to the repository\r\n\r\n1)  record macro as usual into q register \r\n    (i.e. qq..<macro keystrokes>..q)\r\n2)  press save macro key <F3> (default) in normal mode\r\n3)  enter the macro name when prompted after the prefix \r\n    (a prefix will be provided based on the filetype)\r\n4)  macro is now store in the repository\r\n\r\no Save template into repository\r\n\r\n1)  select area you want to save in visual mode\r\n2)  press the macro save button <F3> (default) in visual mode\r\n3)  enter the template name when prompted\r\n    (a prefix will be provided based on the filetype)\r\n4)  template is now saved in repository\r\n\r\no Recall macro\/template through a search\r\n\r\n1)  press the macro find key <F2> (default) in normal mode\r\n2)  enter a search string when prompted \r\n    (a prefix will be put by default, which can be deleted)\r\n3)  press <Tab> or <Control-D> to auto-complete until you find the macro\r\n4)  macro is now run and also loaded for further use into the q register\r\n\r\no Replay last loaded macro on multiple lines for each line\r\n\r\n1)  select the area you want the macro to run on in visual mode\r\n2)  press the macro find key <F3> (default) in visual mode\r\n3)  macro in q register is replayed for every line\r\n\r\nBugs, Patches, Help and Suggestions\r\n-----------------------------------------------------\r\nIf you have some feedback, find any bugs or need some help, please send\r\nand email to chamindra [at] gmail.com and put the word marvim in the\r\nsubject line. \r\n\r\nFurther information\r\n--------------------------\r\nRead the README file or goto http:\/\/chamindra.googlepages.com\/marvim\r\n\r\n","4":"MARVIM - MAcro Repository for VIM\r\n\r\n\"Give your most complex macros a name and store it for future recall and use\"\r\n\r\nProblem statement(s): \r\n-------------------------------\r\n   * Can not remember those complex VIM macro sequences you use frequently?\r\n   * Wish you could save those macros beyond your immediate session? \r\n   * Wish you could share your VIM macros with each other?\r\n   * Why not templates as well in the same script?\r\n\r\nFeatures\r\n------------\r\n    * Recording of VIM macros into persistent storage for future use\r\n    * Auto-complete based recursive search and load of stored VIM macros\r\n    * Visually select and save templates into persistent storage\r\n    * Macro namespaces, to permit organization of macros \r\n    * Support for a default namespace based on filetype\r\n    * Supports a shared macro repository for a team on a shared directory\r\n    * Macro menu items in GVIM version for all main actions\r\n\r\nHotkeys \r\n-----------\r\n<F2>            - Find and execute a macro or insert template from repository\r\nVisual <F2> - Replays last macro for each line selected\r\n<F3>             - Save default macro register by name to the macro repository \r\nVisual <F3>  - Save selection as template by name to the macro repository \r\n<Tab>            - On the Macro command line for cycling through autocomplete\r\n<Control>+D - On the Macro command line for listing autocomplete options\r\n\r\nUsage:\r\n----------\r\no Store a new macro to the repository\r\n\r\n1)  record macro as usual into q register \r\n    (i.e. qq..<macro keystrokes>..q)\r\n2)  press save macro key <F3> (default) in normal mode\r\n3)  enter the macro name when prompted after the prefix \r\n    (a prefix will be provided based on the filetype)\r\n4)  macro is now store in the repository\r\n\r\no Save template into repository\r\n\r\n1)  select area you want to save in visual mode\r\n2)  press the macro save button <F3> (default) in visual mode\r\n3)  enter the template name when prompted\r\n    (a prefix will be provided based on the filetype)\r\n4)  template is now saved in repository\r\n\r\no Recall macro\/template through a search\r\n\r\n1)  press the macro find key <F2> (default) in normal mode\r\n2)  enter a search string when prompted \r\n    (a prefix will be put by default, which can be deleted)\r\n3)  press <Tab> or <Control-D> to auto-complete until you find the macro\r\n4)  macro is now run and also loaded for further use into the q register\r\n\r\no Replay last loaded macro on multiple lines for each line\r\n\r\n1)  select the area you want the macro to run on in visual mode\r\n2)  press the macro find key <F3> (default) in visual mode\r\n3)  macro in q register is replayed for every line\r\n\r\nBugs, Patches, Help and Suggestions\r\n-----------------------------------------------------\r\nIf you have some feedback, find any bugs or need some help, please send\r\nand email to chamindra [at] gmail.com and put the word marvim in the\r\nsubject line. \r\n\r\nFurther information\r\n--------------------------\r\nRead the README file or goto http:\/\/chamindra.googlepages.com\/marvim\r\n\r\n","install_details":"* Download Marvim to your VIM plugin ($VIMRUNTIME\/plugin) directory \r\n  or source it explicitly. Below is an example if you place it in \r\n  the home directory\r\n\r\n  source $HOME\/marvim.vim \r\n\r\n* Start vim and this will automatically create the base marvim macro \r\n  repository in your home directory. Based on the OS it will be \r\n  located as follows:\r\n\r\n  UNIX      ~\/.marvim  \r\n  WINDOWS   C:\\Document and Settings\\Username\\marvim \r\n\r\n* (optional) Copy predefined macro\/template directories into the base \r\n  marvin macro directory. Marvim uses recursive directory search so \r\n  you can nest the directories as you wish.\r\n\r\n* (optional) change the default hotkeys as given above\r\n\r\nChanging the default hotkeys, repository and macro register\r\n-----------------------------------------------------------------------------------\r\nOptionally place the following lines in your vimrc before the location \r\nyou source the marvim.vim script (don't worry about location if \r\nthe script is in the vim plugin directory). \r\n\r\n  \" to change the macro storage location use the following \r\n  let marvim_store = '\/usr\/local\/share\/projectX\/marvim' \r\n  let marvim_find_key = '<Space>' \" change find key from <F2> to 'space'\r\n  let marvim_store_key = 'ms'     \" change store key from <F3> to 'ms'\r\n  let marvim_register = 'c'       \" change used register from 'q' to 'c'\r\n  let marvim_prefix = 0           \" disable default syntax based prefix\r\n\r\n","5":"* Download Marvim to your VIM plugin ($VIMRUNTIME\/plugin) directory \r\n  or source it explicitly. Below is an example if you place it in \r\n  the home directory\r\n\r\n  source $HOME\/marvim.vim \r\n\r\n* Start vim and this will automatically create the base marvim macro \r\n  repository in your home directory. Based on the OS it will be \r\n  located as follows:\r\n\r\n  UNIX      ~\/.marvim  \r\n  WINDOWS   C:\\Document and Settings\\Username\\marvim \r\n\r\n* (optional) Copy predefined macro\/template directories into the base \r\n  marvin macro directory. Marvim uses recursive directory search so \r\n  you can nest the directories as you wish.\r\n\r\n* (optional) change the default hotkeys as given above\r\n\r\nChanging the default hotkeys, repository and macro register\r\n-----------------------------------------------------------------------------------\r\nOptionally place the following lines in your vimrc before the location \r\nyou source the marvim.vim script (don't worry about location if \r\nthe script is in the vim plugin directory). \r\n\r\n  \" to change the macro storage location use the following \r\n  let marvim_store = '\/usr\/local\/share\/projectX\/marvim' \r\n  let marvim_find_key = '<Space>' \" change find key from <F2> to 'space'\r\n  let marvim_store_key = 'ms'     \" change store key from <F3> to 'ms'\r\n  let marvim_register = 'c'       \" change used register from 'q' to 'c'\r\n  let marvim_prefix = 0           \" disable default syntax based prefix\r\n\r\n","first_name":"Chamindra","6":"Chamindra","last_name":"de Silva","7":"de Silva","releases":[{"0":"2154","vim_version":"7.0","1":"7.0","script_version":"0.5 Beta","2":"0.5 Beta","version_comment":"Change Log\r\n----------------\r\n- Refactorted to support latest plugin format of VIM 8\r\n- Added help files and changed the readme to be markdown\r\n- Fixed issues with files with multiple dots in them and other fixes\r\n- You can now pull plugin from github chamindra\/marvim \r\n- Special kudos to @omrisarig13 for VIM 8 plugin refactor \r\n\r\nSend bugs\/feedback to: https:\/\/github.com\/chamindra\/marvim.\r\n","3":"Change Log\r\n----------------\r\n- Refactorted to support latest plugin format of VIM 8\r\n- Added help files and changed the readme to be markdown\r\n- Fixed issues with files with multiple dots in them and other fixes\r\n- You can now pull plugin from github chamindra\/marvim \r\n- Special kudos to @omrisarig13 for VIM 8 plugin refactor \r\n\r\nSend bugs\/feedback to: https:\/\/github.com\/chamindra\/marvim.\r\n","package":"marvim.tar.gz","4":"marvim.tar.gz","src_id":"26749","5":"26749","creation_date":"1568615059","6":"1568615059"},{"0":"2154","vim_version":"7.0","1":"7.0","script_version":"0.4","2":"0.4","version_comment":"Change Log\r\n-----------------\r\n- Now supports auto-completion based recursive search for macros on the command  line\r\n- Use <Tab> and <Ctrl-D> to search for macros in command line as usual in VIM\r\n- The default name space is taken from the file type on the command line ( e.g. php:)\r\n","3":"Change Log\r\n-----------------\r\n- Now supports auto-completion based recursive search for macros on the command  line\r\n- Use <Tab> and <Ctrl-D> to search for macros in command line as usual in VIM\r\n- The default name space is taken from the file type on the command line ( e.g. php:)\r\n","package":"marvim.tar.gz","4":"marvim.tar.gz","src_id":"9289","5":"9289","creation_date":"1222600766","6":"1222600766"},{"0":"2154","vim_version":"6.0","1":"6.0","script_version":"0.3","2":"0.3","version_comment":"Changelog - v0.3 Beta\r\n=================\r\n- New namespace features for macro that map to macro sub-directories\r\n- Supported the creation of macros and templates in a namespace\r\n- Creates namespace directories if they do not exist\r\n- Added the ability to point to a different macro store\r\n- The above permits a shared macro\/template repository within a team\r\n- Refactored code to make macro and template saving a function\r\n- Fixed bug on windows listing of macros without whole path name\r\n\r\n","3":"Changelog - v0.3 Beta\r\n=================\r\n- New namespace features for macro that map to macro sub-directories\r\n- Supported the creation of macros and templates in a namespace\r\n- Creates namespace directories if they do not exist\r\n- Added the ability to point to a different macro store\r\n- The above permits a shared macro\/template repository within a team\r\n- Refactored code to make macro and template saving a function\r\n- Fixed bug on windows listing of macros without whole path name\r\n\r\n","package":"marvim.tar.gz","4":"marvim.tar.gz","src_id":"9258","5":"9258","creation_date":"1222000788","6":"1222000788"},{"0":"2154","vim_version":"7.0","1":"7.0","script_version":"0.2","2":"0.2","version_comment":"Change Log\r\n---------------\r\nv0.2\r\n- Made script windows compatible\r\n- Makes the macro home directory if it does not exist\r\n- Recursively looks up base repository subdirectories for macros\r\n- Creates a macro menu for the GUI versions\r\n- Changed defauly macro input register to q\r\n- Made it easy to define configuration details in vimrc\r\n- Abstracted hotkeys so that they can be defined in the vimrc easily\r\n- Fixed the breaking on spaces in directory paths\r\n- Changed template extension to mvt for ease\r\n- Changed naming conventions to avoid namespace conflict ","3":"Change Log\r\n---------------\r\nv0.2\r\n- Made script windows compatible\r\n- Makes the macro home directory if it does not exist\r\n- Recursively looks up base repository subdirectories for macros\r\n- Creates a macro menu for the GUI versions\r\n- Changed defauly macro input register to q\r\n- Made it easy to define configuration details in vimrc\r\n- Abstracted hotkeys so that they can be defined in the vimrc easily\r\n- Fixed the breaking on spaces in directory paths\r\n- Changed template extension to mvt for ease\r\n- Changed naming conventions to avoid namespace conflict ","package":"marvim.tar.gz","4":"marvim.tar.gz","src_id":"8282","5":"8282","creation_date":"1203073729","6":"1203073729"},{"0":"2154","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"marvim.tar.gz","4":"marvim.tar.gz","src_id":"8269","5":"8269","creation_date":"1202904536","6":"1202904536"}]},"2153":{"script_id":"2153","0":"2153","script_name":"RecentFiles","1":"RecentFiles","script_type":"utility","2":"utility","summary":"Plugin that allows you to easily access recently opened files.","3":"Plugin that allows you to easily access recently opened files.","description":"This script allows you to easily access recently opened files.\r\nFunction RecentFilesList() (with default key binding ',f') displays list of files, and allow you to open one by entering its number.\r\nThe list is empty at the begining, it's updated when you open\/write files.\r\n\r\nScreenshot:\r\nhttp:\/\/s258.photobucket.com\/albums\/hh246\/otokan\/?action=view¤t=vim-RecentFilesList-plugin.png\r\n\r\nScript sets (by default) following key bindings and autocommands:\r\n nmap ,f :call RecentFilesList()<cr>\r\n au BufReadPost,BufWritePost * call RecentFilesAdd()\r\n\r\nEnjoy!\r\n","4":"This script allows you to easily access recently opened files.\r\nFunction RecentFilesList() (with default key binding ',f') displays list of files, and allow you to open one by entering its number.\r\nThe list is empty at the begining, it's updated when you open\/write files.\r\n\r\nScreenshot:\r\nhttp:\/\/s258.photobucket.com\/albums\/hh246\/otokan\/?action=view¤t=vim-RecentFilesList-plugin.png\r\n\r\nScript sets (by default) following key bindings and autocommands:\r\n nmap ,f :call RecentFilesList()<cr>\r\n au BufReadPost,BufWritePost * call RecentFilesAdd()\r\n\r\nEnjoy!\r\n","install_details":"Place script  in your plugin directory (i.e: ~\/.vim\/plugin\/)\r\n\r\nNOTE: you must have ! in &viminfo for this script to work.\r\nAdd line:   set viminfo+=!   to your configuration file if necessary.\r\n\r\nYou can edit some settings in the SETTINGS section of the script file.","5":"Place script  in your plugin directory (i.e: ~\/.vim\/plugin\/)\r\n\r\nNOTE: you must have ! in &viminfo for this script to work.\r\nAdd line:   set viminfo+=!   to your configuration file if necessary.\r\n\r\nYou can edit some settings in the SETTINGS section of the script file.","first_name":"Bartlomiej","6":"Bartlomiej","last_name":"P.","7":"P.","releases":[{"0":"2153","vim_version":"7.0","1":"7.0","script_version":"0.5","2":"0.5","version_comment":"Initial upload","3":"Initial upload","package":"RecentFiles.vim","4":"RecentFiles.vim","src_id":"8268","5":"8268","creation_date":"1202876541","6":"1202876541"}]},"2152":{"script_id":"2152","0":"2152","script_name":"snippets.vim","1":"snippets.vim","script_type":"utility","2":"utility","summary":"Simple snippet storage and retrieval separated by filetype.","3":"Simple snippet storage and retrieval separated by filetype.","description":"Simple utility for managing snippets of text within vim. Users can add, edit, and delete snippets within vim. Command completion is supported in all places that make sense. A menu is also added at \"Plugin\/Snippets\".\r\n\r\nCOMMANDS\r\nAddSnippet -- adds new snippet that contain a range of lines\r\nEditSnippet -- edits a snippet in a new tab\r\nDeleteSnippet -- deletes a snippet (with confirmation)\r\nInsertSnippet -- inserts a snippet before the current line\r\nAppendSnippet -- inserts a snippet after the current line\r\nListSnippets -- lists snippets\r\n\r\nMAPPINGS (<leader> is set to '\\\\', by default)\r\n<leader>ssa -- AddSnippet with current buffer (normal mode)\r\n<leader>ssa -- AddSnippet with range of lines (visual mode)\r\n<leader>sse -- EditSnippet\r\n<leader>ssd -- DeleteSnippet\r\n<leader>ssp -- AppendSnippet\r\n<leader>ssP -- InsertSnippet\r\n<leader>ssl -- ListSnippets","4":"Simple utility for managing snippets of text within vim. Users can add, edit, and delete snippets within vim. Command completion is supported in all places that make sense. A menu is also added at \"Plugin\/Snippets\".\r\n\r\nCOMMANDS\r\nAddSnippet -- adds new snippet that contain a range of lines\r\nEditSnippet -- edits a snippet in a new tab\r\nDeleteSnippet -- deletes a snippet (with confirmation)\r\nInsertSnippet -- inserts a snippet before the current line\r\nAppendSnippet -- inserts a snippet after the current line\r\nListSnippets -- lists snippets\r\n\r\nMAPPINGS (<leader> is set to '\\\\', by default)\r\n<leader>ssa -- AddSnippet with current buffer (normal mode)\r\n<leader>ssa -- AddSnippet with range of lines (visual mode)\r\n<leader>sse -- EditSnippet\r\n<leader>ssd -- DeleteSnippet\r\n<leader>ssp -- AppendSnippet\r\n<leader>ssP -- InsertSnippet\r\n<leader>ssl -- ListSnippets","install_details":"Place script in ~\/.vim\/plugin and start vim.","5":"Place script in ~\/.vim\/plugin and start vim.","first_name":"Jeremy","6":"Jeremy","last_name":"Cantrell","7":"Cantrell","releases":[{"0":"2152","vim_version":"7.0","1":"7.0","script_version":"0.2","2":"0.2","version_comment":"Made functions, variables, and mappings \"script-friendly\". Thanks #vim!","3":"Made functions, variables, and mappings \"script-friendly\". Thanks #vim!","package":"snippets.vim","4":"snippets.vim","src_id":"8333","5":"8333","creation_date":"1203730217","6":"1203730217"},{"0":"2152","vim_version":"7.0","1":"7.0","script_version":"0.1.5","2":"0.1.5","version_comment":"Split the PutSnippet command into InsertSnippet and AppendSnippet","3":"Split the PutSnippet command into InsertSnippet and AppendSnippet","package":"snippets.vim","4":"snippets.vim","src_id":"8328","5":"8328","creation_date":"1203666823","6":"1203666823"},{"0":"2152","vim_version":"7.0","1":"7.0","script_version":"0.1.4","2":"0.1.4","version_comment":"The base snippet directory can now be overridden by setting the variable \"g:snippets_base_directory\" in the vimrc file.","3":"The base snippet directory can now be overridden by setting the variable \"g:snippets_base_directory\" in the vimrc file.","package":"snippets.vim","4":"snippets.vim","src_id":"8278","5":"8278","creation_date":"1202991655","6":"1202991655"},{"0":"2152","vim_version":"7.0","1":"7.0","script_version":"0.1.3","2":"0.1.3","version_comment":"Confirmation dialog now uses the builtin confirm()","3":"Confirmation dialog now uses the builtin confirm()","package":"snippets.vim","4":"snippets.vim","src_id":"8277","5":"8277","creation_date":"1202988759","6":"1202988759"},{"0":"2152","vim_version":"7.0","1":"7.0","script_version":"0.1.2","2":"0.1.2","version_comment":"Fixed a problem where the base snippet directory was not being created on startup.","3":"Fixed a problem where the base snippet directory was not being created on startup.","package":"snippets.vim","4":"snippets.vim","src_id":"8274","5":"8274","creation_date":"1202973391","6":"1202973391"},{"0":"2152","vim_version":"7.0","1":"7.0","script_version":"0.1.1","2":"0.1.1","version_comment":"Forgot to add a description to the script header.","3":"Forgot to add a description to the script header.","package":"snippets.vim","4":"snippets.vim","src_id":"8272","5":"8272","creation_date":"1202928299","6":"1202928299"}]},"2151":{"script_id":"2151","0":"2151","script_name":"sessions.vim","1":"sessions.vim","script_type":"utility","2":"utility","summary":"Easy session management for gvim.","3":"Easy session management for gvim.","description":"This is a very simple script.  It adds a Sessions menu to gvim. Using the menu you can save and restore sessions. Sessions are saved in ~\/.vim\/sessions by default. In case you need further clarification, see the screenshot:\r\n\r\nhttp:\/\/chargedsoftware.com\/~charged2885\/files\/sessions.vim.png\r\n\r\nFor those who don't know, sessions allow you to save the state of your current Vim session to a file. You can then :source the session file to resume state. see :h mks for more information.","4":"This is a very simple script.  It adds a Sessions menu to gvim. Using the menu you can save and restore sessions. Sessions are saved in ~\/.vim\/sessions by default. In case you need further clarification, see the screenshot:\r\n\r\nhttp:\/\/chargedsoftware.com\/~charged2885\/files\/sessions.vim.png\r\n\r\nFor those who don't know, sessions allow you to save the state of your current Vim session to a file. You can then :source the session file to resume state. see :h mks for more information.","install_details":"Put into ~\/.vim\/plugin\/ and reload vim. Manage sessions using new \"Sessions\" menu. You can put your existing session files in ~\/.vim\/sessions\/ and :call DrawSessionMenu().","5":"Put into ~\/.vim\/plugin\/ and reload vim. Manage sessions using new \"Sessions\" menu. You can put your existing session files in ~\/.vim\/sessions\/ and :call DrawSessionMenu().","first_name":"Todd","6":"Todd","last_name":"Boland","7":"Boland","releases":[{"0":"2151","vim_version":"7.0","1":"7.0","script_version":"0.2","2":"0.2","version_comment":"Added win32 support thanks to \"lizard\".","3":"Added win32 support thanks to \"lizard\".","package":"sessions.vim","4":"sessions.vim","src_id":"8266","5":"8266","creation_date":"1202843865","6":"1202843865"},{"0":"2151","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"sessions.vim","4":"sessions.vim","src_id":"8260","5":"8260","creation_date":"1202735485","6":"1202735485"}]},"2150":{"script_id":"2150","0":"2150","script_name":"css_color.vim","1":"css_color.vim","script_type":"syntax","2":"syntax","summary":"CSS color preview","3":"CSS color preview","description":"This Script underlays the hexadecimal CSS colorcodes with their real color. The foreground color is selected appositely. So #FF0000 will look as hot as a fire engine!\r\n\r\nAn image for those who do not get my prose:\r\nhttp:\/\/lanpartei.de\/~niklas\/vim\/after\/syntax\/css-color-vim.png","4":"This Script underlays the hexadecimal CSS colorcodes with their real color. The foreground color is selected appositely. So #FF0000 will look as hot as a fire engine!\r\n\r\nAn image for those who do not get my prose:\r\nhttp:\/\/lanpartei.de\/~niklas\/vim\/after\/syntax\/css-color-vim.png","install_details":"Save it locally under .vim\/after\/syntax\/css.vim ","5":"Save it locally under .vim\/after\/syntax\/css.vim ","first_name":"Niklas","6":"Niklas","last_name":"Hofer","7":"Hofer","releases":[{"0":"2150","vim_version":"6.0","1":"6.0","script_version":"0.7","2":"0.7","version_comment":"Patch (by Yusuke Yanbe): works in 256-color terminals","3":"Patch (by Yusuke Yanbe): works in 256-color terminals","package":"css.vim","4":"css.vim","src_id":"8846","5":"8846","creation_date":"1214304474","6":"1214304474"},{"0":"2150","vim_version":"6.0","1":"6.0","script_version":"0.6","2":"0.6","version_comment":"* do not double-define matchers\r\n* correctly highlight if something like #666 is present before #666666 (thx to jmarshall for finding this)\r\n* colorize named colors (w3c+extra)\r\n* url for svn","3":"* do not double-define matchers\r\n* correctly highlight if something like #666 is present before #666666 (thx to jmarshall for finding this)\r\n* colorize named colors (w3c+extra)\r\n* url for svn","package":"css.vim","4":"css.vim","src_id":"8263","5":"8263","creation_date":"1202810310","6":"1202810310"},{"0":"2150","vim_version":"6.0","1":"6.0","script_version":"0.5","2":"0.5","version_comment":"Initial upload","3":"Initial upload","package":"css.vim","4":"css.vim","src_id":"8256","5":"8256","creation_date":"1202666265","6":"1202666265"}]},"2149":{"script_id":"2149","0":"2149","script_name":"ncss.vim","1":"ncss.vim","script_type":"syntax","2":"syntax","summary":"Syntax File for NCSS","3":"Syntax File for NCSS","description":"This is the syntax file vor NCSS (Nested CSS), also known as CSS DRYer.\r\n\r\nIt is used as an optional plugin for the Ruby on Rails to write CSS without repeating yourself. \r\n\r\nPlease see http:\/\/opensource.airbladesoftware.com\/trunk\/plugins\/css_dryer","4":"This is the syntax file vor NCSS (Nested CSS), also known as CSS DRYer.\r\n\r\nIt is used as an optional plugin for the Ruby on Rails to write CSS without repeating yourself. \r\n\r\nPlease see http:\/\/opensource.airbladesoftware.com\/trunk\/plugins\/css_dryer","install_details":"","5":"","first_name":"Niklas","6":"Niklas","last_name":"Hofer","7":"Hofer","releases":[{"0":"2149","vim_version":"6.0","1":"6.0","script_version":"0.7","2":"0.7","version_comment":"Initial upload","3":"Initial upload","package":"ncss.vim","4":"ncss.vim","src_id":"8255","5":"8255","creation_date":"1202665962","6":"1202665962"}]},"2148":{"script_id":"2148","0":"2148","script_name":"quiltdiff","1":"quiltdiff","script_type":"utility","2":"utility","summary":"Shows changes of the current patch on the left as signs","3":"Shows changes of the current patch on the left as signs","description":"When using quilt, this plugin shows the changes in the current patch on the left. This script is the quilt port of svndiff (http:\/\/www.vim.org\/scripts\/script.php?script_id=1881).","4":"When using quilt, this plugin shows the changes in the current patch on the left. This script is the quilt port of svndiff (http:\/\/www.vim.org\/scripts\/script.php?script_id=1881).","install_details":"Just copy quiltdiff.vim to ~\/.vim\/plugin.","5":"Just copy quiltdiff.vim to ~\/.vim\/plugin.","first_name":"Bernhard","6":"Bernhard","last_name":"Walle","7":"Walle","releases":[{"0":"2148","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"quiltdiff.vim","4":"quiltdiff.vim","src_id":"8254","5":"8254","creation_date":"1202634150","6":"1202634150"}]},"2147":{"script_id":"2147","0":"2147","script_name":"VimTrac","1":"VimTrac","script_type":"utility","2":"utility","summary":"A vim client for the Trac wiki and ticketing system","3":"A vim client for the Trac wiki and ticketing system","description":"[NOTE: The most recent version requires the Align.vim (vimscript #294) plugin if you want to use the summary ticket view. (The default and most readable view)\r\nhttp:\/\/www.ascetinteractive.com.au\/vimtrac\/attachment\/wiki\/Screenshots\/summary.jpg]\r\n\r\n\r\nThis is a client for the open source trac source code manager and ticketing system. (http:\/\/trac.edgewall.org\/) It will enable you to \r\n\r\n- do browsing and editing  of a trac sites wiki pages\r\n- create and edit tickets \r\n- add attachments \r\n- view project timelines changesets as unified diffs.\r\n- perform trac site searches\r\n- browser previews and text dumps of wikis.\r\n\r\n\r\nVimTrac's wiki is here http:\/\/www.ascetinteractive.com.au\/vimtrac \r\nThe Repo is now on github here http:\/\/github.com\/mjbrownie\/Trac.vim\r\n\r\nIf you have any issues\/requests create a ticket there using the login details in the trac.vim script or email me.\r\n\r\n","4":"[NOTE: The most recent version requires the Align.vim (vimscript #294) plugin if you want to use the summary ticket view. (The default and most readable view)\r\nhttp:\/\/www.ascetinteractive.com.au\/vimtrac\/attachment\/wiki\/Screenshots\/summary.jpg]\r\n\r\n\r\nThis is a client for the open source trac source code manager and ticketing system. (http:\/\/trac.edgewall.org\/) It will enable you to \r\n\r\n- do browsing and editing  of a trac sites wiki pages\r\n- create and edit tickets \r\n- add attachments \r\n- view project timelines changesets as unified diffs.\r\n- perform trac site searches\r\n- browser previews and text dumps of wikis.\r\n\r\n\r\nVimTrac's wiki is here http:\/\/www.ascetinteractive.com.au\/vimtrac \r\nThe Repo is now on github here http:\/\/github.com\/mjbrownie\/Trac.vim\r\n\r\nIf you have any issues\/requests create a ticket there using the login details in the trac.vim script or email me.\r\n\r\n","install_details":"                                  Usage Notes\r\n\r\n     * You must have a working Trac repository version 0.10 or later\r\n       complete with the xmlrpc plugin and a user with suitable access\r\n       rights.\r\n\r\n     * Vim must be compiled with python support and your client must have\r\n       python 2.4.4 or later\r\n\r\n       Add the trac.py, trac.vim in either your $VIMRUMTTIME\/plugin directory or your HOME\/.vim\/plugin\/ directory.\r\n\r\n       Add trac.txt to your doc directory and run :helptags (dir) to source it.\r\n\r\n     * Read the trac.vim leading comments on the setup\r\n\r\n      * create links to your trac servers in a vimscript dictionary in your vimrc as follows...\r\n        let g:tracServerList = {}       \r\n        let g:tracServerList['Vim Trac - vimtrac user'] = 'http:\/\/vimtracuser:wibble@www.ascetinteractive.com.au\/vimtrac\/login\/xmlrpc'\r\n        let g:tracServerList['(Server Name)'] = 'http:\/\/(user):(password)@(trac serverpath)\/login\/xmlrpc'\r\n\r\n\r\n   The servers can now be set by typing\r\n        :TTServer <Server Name>\r\n        :TWServer <Server Name>\r\n\r\n   The <tab> key will cycle through available servers.\r\n\r\nDefatult key mappings:\r\n\r\n     * <leader>to - Opens the Trac wiki view\r\n     * <leader>tq - Closes the Trac wiki View\r\n     * <leader>tw - Writes the Current Wiki Page (Uses default update\r\n       Comment)\r\n     * (0.2.3) <leader>tt - Toggles between current window size mode.\r\n       (normal, full horizontal,maximized ....)\r\n     * (0.2.5) <leader>tp - Launches a browser preview of the current\r\n       wiki page\r\n\r\n     or\r\n\r\n     * :TWOpen - Open the wiki View\r\n     * :TClose - Close the wiki View\r\n     * :TWSave \"<Comment>\" - Saves the Active Wiki Page\r\n     * :TTOpen <Ticket ID> - Open Trac Ticket Browser\r\n     * :TWCreate - Create a Wiki Page\r\n     * :TServer <Trac Server> - Set the Current Server (tab\r\n       complete)\r\n     * :TSearch <search term> - Opens Trac Search View\r\n     * :TWPreview - opens current wiki in browser\r\n     *  :TWDump - lynx dump of the current wiki\r\n     *  :TracChangesetView? <id> - Opens a Unified Diff of a\r\n       specific changeset\r\n\r\nBuffer Specific Key Mappings\r\n\r\n     * In the Wiki TOC View Pages can be loaded for editing by hitting\r\n       <enter> or <space> for browser preview\r\n     * In the Ticket can be loaded for editing by hitting <enter> or\r\n       <space> for browser preview on lines containing Ticket:>>\r\n     * In the Wiki View Window a Page will go to the wiki page if you hit\r\n       ctrl+] but will throw an error if you arent on a proper link.\r\n     * Wikis can now be saved with :w and :wq. (As of 0.2.3 it pauses\r\n       :TWSave ? so you can enter a change comment)\r\n     * In all Trac windows :q will return to the normal view\r\n     * Wiki Syntax will work with this wiki syntax file\r\n       http:\/\/www.vim.org\/scripts\/script.php?script_id=725\r\n","5":"                                  Usage Notes\r\n\r\n     * You must have a working Trac repository version 0.10 or later\r\n       complete with the xmlrpc plugin and a user with suitable access\r\n       rights.\r\n\r\n     * Vim must be compiled with python support and your client must have\r\n       python 2.4.4 or later\r\n\r\n       Add the trac.py, trac.vim in either your $VIMRUMTTIME\/plugin directory or your HOME\/.vim\/plugin\/ directory.\r\n\r\n       Add trac.txt to your doc directory and run :helptags (dir) to source it.\r\n\r\n     * Read the trac.vim leading comments on the setup\r\n\r\n      * create links to your trac servers in a vimscript dictionary in your vimrc as follows...\r\n        let g:tracServerList = {}       \r\n        let g:tracServerList['Vim Trac - vimtrac user'] = 'http:\/\/vimtracuser:wibble@www.ascetinteractive.com.au\/vimtrac\/login\/xmlrpc'\r\n        let g:tracServerList['(Server Name)'] = 'http:\/\/(user):(password)@(trac serverpath)\/login\/xmlrpc'\r\n\r\n\r\n   The servers can now be set by typing\r\n        :TTServer <Server Name>\r\n        :TWServer <Server Name>\r\n\r\n   The <tab> key will cycle through available servers.\r\n\r\nDefatult key mappings:\r\n\r\n     * <leader>to - Opens the Trac wiki view\r\n     * <leader>tq - Closes the Trac wiki View\r\n     * <leader>tw - Writes the Current Wiki Page (Uses default update\r\n       Comment)\r\n     * (0.2.3) <leader>tt - Toggles between current window size mode.\r\n       (normal, full horizontal,maximized ....)\r\n     * (0.2.5) <leader>tp - Launches a browser preview of the current\r\n       wiki page\r\n\r\n     or\r\n\r\n     * :TWOpen - Open the wiki View\r\n     * :TClose - Close the wiki View\r\n     * :TWSave \"<Comment>\" - Saves the Active Wiki Page\r\n     * :TTOpen <Ticket ID> - Open Trac Ticket Browser\r\n     * :TWCreate - Create a Wiki Page\r\n     * :TServer <Trac Server> - Set the Current Server (tab\r\n       complete)\r\n     * :TSearch <search term> - Opens Trac Search View\r\n     * :TWPreview - opens current wiki in browser\r\n     *  :TWDump - lynx dump of the current wiki\r\n     *  :TracChangesetView? <id> - Opens a Unified Diff of a\r\n       specific changeset\r\n\r\nBuffer Specific Key Mappings\r\n\r\n     * In the Wiki TOC View Pages can be loaded for editing by hitting\r\n       <enter> or <space> for browser preview\r\n     * In the Ticket can be loaded for editing by hitting <enter> or\r\n       <space> for browser preview on lines containing Ticket:>>\r\n     * In the Wiki View Window a Page will go to the wiki page if you hit\r\n       ctrl+] but will throw an error if you arent on a proper link.\r\n     * Wikis can now be saved with :w and :wq. (As of 0.2.3 it pauses\r\n       :TWSave ? so you can enter a change comment)\r\n     * In all Trac windows :q will return to the normal view\r\n     * Wiki Syntax will work with this wiki syntax file\r\n       http:\/\/www.vim.org\/scripts\/script.php?script_id=725\r\n","first_name":"Michael","6":"Michael","last_name":"Brown","7":"Brown","releases":[{"0":"2147","vim_version":"7.0","1":"7.0","script_version":"0.3.6","2":"0.3.6","version_comment":"Some compatability fixes for trac 0.11. Fixed :w mapping on add_comment buffer.  Thanks to Brad Fritz","3":"Some compatability fixes for trac 0.11. Fixed :w mapping on add_comment buffer.  Thanks to Brad Fritz","package":"trac.vim.0.3.6.tar.gz","4":"trac.vim.0.3.6.tar.gz","src_id":"11431","5":"11431","creation_date":"1253867470","6":"1253867470"},{"0":"2147","vim_version":"7.0","1":"7.0","script_version":"0.3.5","2":"0.3.5","version_comment":"Improved python old version checker and notification. removed .svn files that were accidentally stuck in the last package, Thanks Kai","3":"Improved python old version checker and notification. removed .svn files that were accidentally stuck in the last package, Thanks Kai","package":"trac.vim.0.3.5.tar.gz","4":"trac.vim.0.3.5.tar.gz","src_id":"10047","5":"10047","creation_date":"1235687956","6":"1235687956"},{"0":"2147","vim_version":"7.0","1":"7.0","script_version":"0.3.3","2":"0.3.3","version_comment":"Added improved ticket summary view, Wiki VimDiff view, blacklist filters for tickets and ticket sorting ","3":"Added improved ticket summary view, Wiki VimDiff view, blacklist filters for tickets and ticket sorting ","package":"trac.vim.0.3.3.tar.gz","4":"trac.vim.0.3.3.tar.gz","src_id":"8804","5":"8804","creation_date":"1213490178","6":"1213490178"}]},"2146":{"script_id":"2146","0":"2146","script_name":"prmths","1":"prmths","script_type":"color scheme","2":"color scheme","summary":"Nice dark clean easy to look at color theme","3":"Nice dark clean easy to look at color theme","description":"Dark theme with mostly blues and cyans, a little red and some yellow.... very easy to look at. enough contrast to be useful, not so much that it's an eye-strain. I stare at my screen for hours with this theme and don't get fatigued.","4":"Dark theme with mostly blues and cyans, a little red and some yellow.... very easy to look at. enough contrast to be useful, not so much that it's an eye-strain. I stare at my screen for hours with this theme and don't get fatigued.","install_details":"put it in ~\/.vim\/colors\r\nrun \r\n:colo prmths\r\nin vim","5":"put it in ~\/.vim\/colors\r\nrun \r\n:colo prmths\r\nin vim","first_name":"Gregory","6":"Gregory","last_name":"Maculo","7":"Maculo","releases":[{"0":"2146","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"prmths.vim","4":"prmths.vim","src_id":"8246","5":"8246","creation_date":"1202505472","6":"1202505472"}]},"2145":{"script_id":"2145","0":"2145","script_name":"GOBject Builder (gob2)","1":"GOBject Builder (gob2)","script_type":"syntax","2":"syntax","summary":"Syntax and indent for GObject Builder (gob2)","3":"Syntax and indent for GObject Builder (gob2)","description":"Vim syntax and indent files for GObject Builder (gob2)\r\n\r\nIt works well with gtk-vim-syntax (vimscript #1000) package. \r\n\r\nBasically, it depends on c.vim, so change in c.vim will also affect it.\r\n","4":"Vim syntax and indent files for GObject Builder (gob2)\r\n\r\nIt works well with gtk-vim-syntax (vimscript #1000) package. \r\n\r\nBasically, it depends on c.vim, so change in c.vim will also affect it.\r\n","install_details":"For Unix:\r\n1. Extract the package to ~\/.vim\r\n2a. If ~\/.vim\/filetype.vim exists then insert something like:\r\n   augroup filetypedetect\r\n   ............\r\n     au! BufRead,BufNewFile *.gob setfiletype gob\r\n   ...........\r\n   augroup END\r\n\r\n   in ~\/.vim\/filetype.vim\r\n\r\n2b. If not, then:\r\n   cd ~\/.vim;\r\n   cp filetype.vim.example filetype.vim\r\n\r\n========================================================   \r\nFor Windows:\r\n1. Extract the package to $HOME\/vimfiles\r\n2a. If $HOME\/vimfiles\/filetype.vim exists then insert something like:\r\n   augroup filetypedetect\r\n   ............\r\n     au! BufRead,BufNewFile *.gob setfiletype gob\r\n   ...........\r\n   augroup END\r\n\r\n   in $HOME\/vimfiles\/filetype.vim\r\n\r\n2b. If not, then:\r\n   cd $HOME\/vimfiles\r\n   copy filetype.vim.example filetype.vim\r\n","5":"For Unix:\r\n1. Extract the package to ~\/.vim\r\n2a. If ~\/.vim\/filetype.vim exists then insert something like:\r\n   augroup filetypedetect\r\n   ............\r\n     au! BufRead,BufNewFile *.gob setfiletype gob\r\n   ...........\r\n   augroup END\r\n\r\n   in ~\/.vim\/filetype.vim\r\n\r\n2b. If not, then:\r\n   cd ~\/.vim;\r\n   cp filetype.vim.example filetype.vim\r\n\r\n========================================================   \r\nFor Windows:\r\n1. Extract the package to $HOME\/vimfiles\r\n2a. If $HOME\/vimfiles\/filetype.vim exists then insert something like:\r\n   augroup filetypedetect\r\n   ............\r\n     au! BufRead,BufNewFile *.gob setfiletype gob\r\n   ...........\r\n   augroup END\r\n\r\n   in $HOME\/vimfiles\/filetype.vim\r\n\r\n2b. If not, then:\r\n   cd $HOME\/vimfiles\r\n   copy filetype.vim.example filetype.vim\r\n","first_name":"Ding-Yi","6":"Ding-Yi","last_name":"Chen","7":"Chen","releases":[{"0":"2145","vim_version":"7.0","1":"7.0","script_version":"0.5","2":"0.5","version_comment":"Fix align after override, signal, and virtual\r\nAdd LONG, object_type, export, link as keyword","3":"Fix align after override, signal, and virtual\r\nAdd LONG, object_type, export, link as keyword","package":"GObjectBuilder.0.5.tar.gz","4":"GObjectBuilder.0.5.tar.gz","src_id":"8441","5":"8441","creation_date":"1205340917","6":"1205340917"},{"0":"2145","vim_version":"7.0","1":"7.0","script_version":"0.4","2":"0.4","version_comment":" * Fix align with destroy(with) unref(with)\r\n * Fix indent after %{ tags\r\n * Fix indent of access keyword (public, protected..) after  virtual or override","3":" * Fix align with destroy(with) unref(with)\r\n * Fix indent after %{ tags\r\n * Fix indent of access keyword (public, protected..) after  virtual or override","package":"GObjectBuilder.0.4.tar.gz","4":"GObjectBuilder.0.4.tar.gz","src_id":"8382","5":"8382","creation_date":"1204476114","6":"1204476114"},{"0":"2145","vim_version":"7.0","1":"7.0","script_version":"0.3","2":"0.3","version_comment":"- Better recognition of CBlock (e.g. %headertop{, %alltop{, .... }\r\n- Add ftplugin\/gob.vim\r\n","3":"- Better recognition of CBlock (e.g. %headertop{, %alltop{, .... }\r\n- Add ftplugin\/gob.vim\r\n","package":"GObjectBuilder.0.3.tar.gz","4":"GObjectBuilder.0.3.tar.gz","src_id":"8316","5":"8316","creation_date":"1203536029","6":"1203536029"}]},"2144":{"script_id":"2144","0":"2144","script_name":"nice-vim","1":"nice-vim","script_type":"syntax","2":"syntax","summary":"Syntax highlighting for Nice programming language","3":"Syntax highlighting for Nice programming language","description":"This script provides syntax highlight and file type detection for Nice programming language.\r\n","4":"This script provides syntax highlight and file type detection for Nice programming language.\r\n","install_details":"Just unpack the zip-archive into an appropriate ViM directory (e.g. ~\/vimfiles).","5":"Just unpack the zip-archive into an appropriate ViM directory (e.g. ~\/vimfiles).","first_name":"Yauheni","6":"Yauheni","last_name":"Akhotnikau","7":"Akhotnikau","releases":[{"0":"2144","vim_version":"6.0","1":"6.0","script_version":"0.2","2":"0.2","version_comment":"Support for public-read\/private-write and try-catch-finally added.","3":"Support for public-read\/private-write and try-catch-finally added.","package":"nice-vim-0.2.zip","4":"nice-vim-0.2.zip","src_id":"8280","5":"8280","creation_date":"1203063863","6":"1203063863"},{"0":"2144","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"nice-vim-0.1.zip","4":"nice-vim-0.1.zip","src_id":"8242","5":"8242","creation_date":"1202374566","6":"1202374566"}]},"2143":{"script_id":"2143","0":"2143","script_name":"unibasic.vim","1":"unibasic.vim","script_type":"syntax","2":"syntax","summary":"Programming language for the UniVerse Database","3":"Programming language for the UniVerse Database","description":"The UniVerse BASIC syntax file highlights the programming language used in IBM's UniVerse multivalue database application.  This file is extracted from Lubomir Husar's DataStage syntax file (vimscript #1310) and focuses on only the data related to UniVerse BASIC.  All the DataStage-specific items remain in the previous script.","4":"The UniVerse BASIC syntax file highlights the programming language used in IBM's UniVerse multivalue database application.  This file is extracted from Lubomir Husar's DataStage syntax file (vimscript #1310) and focuses on only the data related to UniVerse BASIC.  All the DataStage-specific items remain in the previous script.","install_details":"Copy the file into the ~\/.vim\/syntax (Unix) or ~\/vimfiles\/syntax (Windows) directory, then activate on the current buffer with the command\r\n\r\n:setfiletype unibasic","5":"Copy the file into the ~\/.vim\/syntax (Unix) or ~\/vimfiles\/syntax (Windows) directory, then activate on the current buffer with the command\r\n\r\n:setfiletype unibasic","first_name":"Dan","6":"Dan","last_name":"Sharp","7":"Sharp","releases":[{"0":"2143","vim_version":"6.0","1":"6.0","script_version":"1.4","2":"1.4","version_comment":"Initial upload","3":"Initial upload","package":"unibasic.vim","4":"unibasic.vim","src_id":"8241","5":"8241","creation_date":"1202335807","6":"1202335807"}]},"2142":{"script_id":"2142","0":"2142","script_name":"showmarks","1":"showmarks","script_type":"utility","2":"utility","summary":"Display marks as signs (needs +sign feat )","3":"Display marks as signs (needs +sign feat )","description":" ShowMarks                                                        \r\n                                                                  \r\n Give a visual aid to navigate marks, by displaying them as signs \r\n (obviously needs the +signs feature).                            \r\n                                                                  \r\n commands                                                         \r\n --------                                                         \r\n                                                                  \r\n :DoShowMarks                                                     \r\n   show marks for current buffer                                  \r\n :DoShowMarks!                                                    \r\n   show marks for all buffers                                     \r\n :NoShowMarks                                                     \r\n   disable it for current buffer                                  \r\n :NoShowMarks!                                                    \r\n   disable it for all buffers                                     \r\n                                                                  \r\n :[count]ShowMarksOnce                                            \r\n   Display marks for [count] Cursorhold                           \r\n   events. Mostly for mapping it like :                           \r\n   nnoremap ` :ShowMarksOnce<cr>`                                 \r\n                                                                  \r\n :[count]PreviewMarks                                             \r\n   Display marks of current buffer in pvw.                        \r\n   Like ':marks', but at the top of the window ;-).               \r\n   [count] is the same as above.                                  \r\n                                                                  \r\n variables                                                        \r\n --------                                                         \r\n                                                                  \r\n let g:showmarks_marks = \"abcdef....\"                             \r\n   the marks you want to have displayed.                          \r\n hlShowMarks                                                      \r\n   the highlight color                                            \r\n                                                                  \r\n I suggest you lower the value of 'updatetime'.                    \r\n","4":" ShowMarks                                                        \r\n                                                                  \r\n Give a visual aid to navigate marks, by displaying them as signs \r\n (obviously needs the +signs feature).                            \r\n                                                                  \r\n commands                                                         \r\n --------                                                         \r\n                                                                  \r\n :DoShowMarks                                                     \r\n   show marks for current buffer                                  \r\n :DoShowMarks!                                                    \r\n   show marks for all buffers                                     \r\n :NoShowMarks                                                     \r\n   disable it for current buffer                                  \r\n :NoShowMarks!                                                    \r\n   disable it for all buffers                                     \r\n                                                                  \r\n :[count]ShowMarksOnce                                            \r\n   Display marks for [count] Cursorhold                           \r\n   events. Mostly for mapping it like :                           \r\n   nnoremap ` :ShowMarksOnce<cr>`                                 \r\n                                                                  \r\n :[count]PreviewMarks                                             \r\n   Display marks of current buffer in pvw.                        \r\n   Like ':marks', but at the top of the window ;-).               \r\n   [count] is the same as above.                                  \r\n                                                                  \r\n variables                                                        \r\n --------                                                         \r\n                                                                  \r\n let g:showmarks_marks = \"abcdef....\"                             \r\n   the marks you want to have displayed.                          \r\n hlShowMarks                                                      \r\n   the highlight color                                            \r\n                                                                  \r\n I suggest you lower the value of 'updatetime'.                    \r\n","install_details":"unzip to your $vim_dir","5":"unzip to your $vim_dir","first_name":"Andreas","6":"Andreas","last_name":"Politz","7":"Politz","releases":[{"0":"2142","vim_version":"7.0","1":"7.0","script_version":"v0.1","2":"v0.1","version_comment":"Initial upload","3":"Initial upload","package":"showmarks.zip","4":"showmarks.zip","src_id":"8240","5":"8240","creation_date":"1202276280","6":"1202276280"}]},"2141":{"script_id":"2141","0":"2141","script_name":"undobranche_viewer.vim","1":"undobranche_viewer.vim","script_type":"utility","2":"utility","summary":"Undo Branches Explorer","3":"Undo Branches Explorer","description":"Overview\r\n--------\r\nVim7 Undo Branches Explorer.\r\nSee ':help undo-branches', also.\r\n\r\nInstallation\r\n------------\r\n1. Copy the undobranch_viewer.vim script to the $HOME\/.vim\/plugin or\r\n   the $HOME\/vimfiles\/plugin. Refer to the ':help add-plugin',\r\n   ':help add-global-plugin' and ':help runtimepath' topics for\r\n   more details about Vim plugins.\r\n\r\n2. Restart Vim.\r\n\r\n3. This script requires tlib (vimscript #1863) to be installed. \r\n\r\nUsage\r\n-----\r\n1. Open Undo Branches Explorer with command ':UndoBranchViewer'.\r\n2.\r\n      <c-p> undo selected branche.\r\n      <c-u> undo selected branche, and close undo branches list.\r\n","4":"Overview\r\n--------\r\nVim7 Undo Branches Explorer.\r\nSee ':help undo-branches', also.\r\n\r\nInstallation\r\n------------\r\n1. Copy the undobranch_viewer.vim script to the $HOME\/.vim\/plugin or\r\n   the $HOME\/vimfiles\/plugin. Refer to the ':help add-plugin',\r\n   ':help add-global-plugin' and ':help runtimepath' topics for\r\n   more details about Vim plugins.\r\n\r\n2. Restart Vim.\r\n\r\n3. This script requires tlib (vimscript #1863) to be installed. \r\n\r\nUsage\r\n-----\r\n1. Open Undo Branches Explorer with command ':UndoBranchViewer'.\r\n2.\r\n      <c-p> undo selected branche.\r\n      <c-u> undo selected branche, and close undo branches list.\r\n","install_details":"1. Copy the undobranch_viewer.vim script to the $HOME\/.vim\/plugin or\r\n   the $HOME\/vimfiles\/plugin. Refer to the ':help add-plugin',\r\n   ':help add-global-plugin' and ':help runtimepath' topics for\r\n   more details about Vim plugins.\r\n\r\n2. Restart Vim.\r\n\r\n3. This script requires tlib (vimscript #1863) to be installed. \r\n","5":"1. Copy the undobranch_viewer.vim script to the $HOME\/.vim\/plugin or\r\n   the $HOME\/vimfiles\/plugin. Refer to the ':help add-plugin',\r\n   ':help add-global-plugin' and ':help runtimepath' topics for\r\n   more details about Vim plugins.\r\n\r\n2. Restart Vim.\r\n\r\n3. This script requires tlib (vimscript #1863) to be installed. \r\n","first_name":"omi","6":"omi","last_name":"taku","7":"taku","releases":[{"0":"2141","vim_version":"7.0","1":"7.0","script_version":"0.4","2":"0.4","version_comment":"Initial upload","3":"Initial upload","package":"undobranche_viewer.vim","4":"undobranche_viewer.vim","src_id":"8235","5":"8235","creation_date":"1202106334","6":"1202106334"}]},"2140":{"script_id":"2140","0":"2140","script_name":"xoria256.vim","1":"xoria256.vim","script_type":"color scheme","2":"color scheme","summary":"Soft pastel gamma on dark background, same appearence in {,g}vim","3":"Soft pastel gamma on dark background, same appearence in {,g}vim","description":"Screenshots:\r\n--- outdated a little ---\r\n * Django template, random HTML page: http:\/\/i052.radikal.ru\/1105\/cd\/033017b68c3c.png\r\n * NEDRTree, crazy vim autocomplete: http:\/\/i017.radikal.ru\/1105\/b8\/113c699f023f.png\r\n * vimdiff (indispensable for the sysadmins out there!): http:\/\/i048.radikal.ru\/1105\/05\/93e85f0eccda.png\r\n--- outdated even more (but still representative) ---\r\n * GUI, C code with a :split and foldings: http:\/\/i.piccy.info\/i3\/2f\/32\/04d9c2b4095038a9ee591e9ef6a3.png\r\n * Console, C code: http:\/\/i.piccy.info\/i3\/e8\/cd\/9d32e1fd38e9c8b54848a3f59794.png\r\n * GUI, Python: http:\/\/i.piccy.info\/i3\/4b\/63\/8815c1fbed0dfdf2a3a6af1bc83c.png\r\n * Console, Bash: http:\/\/i.piccy.info\/i3\/6d\/fc\/f8c24fb713f396dae0127ec2339c.png\r\n\r\nNotes:\r\nThis colorscheme tries to follow the \"traditional\" colour semantics found in some IDEs: cold (blue-ish) hues for control structures, warm colors for data, (green would look for comments, but it's difficult to pick an appropriate value for the dark background with only 256 colors available plus a little hard to read, so they are grey). Colors should look almost similar in vim, running in any modern terminal emulator (like recent versions of xterm or konsole), and in GTK2 GUI.","4":"Screenshots:\r\n--- outdated a little ---\r\n * Django template, random HTML page: http:\/\/i052.radikal.ru\/1105\/cd\/033017b68c3c.png\r\n * NEDRTree, crazy vim autocomplete: http:\/\/i017.radikal.ru\/1105\/b8\/113c699f023f.png\r\n * vimdiff (indispensable for the sysadmins out there!): http:\/\/i048.radikal.ru\/1105\/05\/93e85f0eccda.png\r\n--- outdated even more (but still representative) ---\r\n * GUI, C code with a :split and foldings: http:\/\/i.piccy.info\/i3\/2f\/32\/04d9c2b4095038a9ee591e9ef6a3.png\r\n * Console, C code: http:\/\/i.piccy.info\/i3\/e8\/cd\/9d32e1fd38e9c8b54848a3f59794.png\r\n * GUI, Python: http:\/\/i.piccy.info\/i3\/4b\/63\/8815c1fbed0dfdf2a3a6af1bc83c.png\r\n * Console, Bash: http:\/\/i.piccy.info\/i3\/6d\/fc\/f8c24fb713f396dae0127ec2339c.png\r\n\r\nNotes:\r\nThis colorscheme tries to follow the \"traditional\" colour semantics found in some IDEs: cold (blue-ish) hues for control structures, warm colors for data, (green would look for comments, but it's difficult to pick an appropriate value for the dark background with only 256 colors available plus a little hard to read, so they are grey). Colors should look almost similar in vim, running in any modern terminal emulator (like recent versions of xterm or konsole), and in GTK2 GUI.","install_details":"Your terminal should support 256-color terminfo definitions.  For that, install 'ncurses-term' or similar package (not installed in Ubuntu-8.10 by default, btw). Then check that you have $TERM variable properly defined (`echo $TERM` gives something like \"xterm-256color\"). I use gnome-terminal, and I additionally put the following into ~\/.bashrc:\r\n\r\nif [ \"$COLORTERM\" == \"gnome-terminal\" ]; then\r\n    export TERM=xterm-256color\r\nfi\r\n\r\nIf you plan to use screen multiplexer, you'll also have to assure, that your ~\/.screenrc contains the following stuff:\r\n\r\nterm screen-256color\r\nattrcolor b \".I\"\r\n# Tell screen how to set colors. AB = background, AF=foreground\r\ntermcapinfo xterm 'Co#256:AB=\\E[48;5;%dm:AF=\\E[38;5;%dm'\r\n# Erase background with current bg color.  Not needed if TERM=screen-256color\r\ndefbce \"on\"\r\n\r\nWhen everything is set and done, copy xoria256.vim into ~\/.vim\/colors.  To use it, issue ':colo xoria256' in {,g}vim.","5":"Your terminal should support 256-color terminfo definitions.  For that, install 'ncurses-term' or similar package (not installed in Ubuntu-8.10 by default, btw). Then check that you have $TERM variable properly defined (`echo $TERM` gives something like \"xterm-256color\"). I use gnome-terminal, and I additionally put the following into ~\/.bashrc:\r\n\r\nif [ \"$COLORTERM\" == \"gnome-terminal\" ]; then\r\n    export TERM=xterm-256color\r\nfi\r\n\r\nIf you plan to use screen multiplexer, you'll also have to assure, that your ~\/.screenrc contains the following stuff:\r\n\r\nterm screen-256color\r\nattrcolor b \".I\"\r\n# Tell screen how to set colors. AB = background, AF=foreground\r\ntermcapinfo xterm 'Co#256:AB=\\E[48;5;%dm:AF=\\E[38;5;%dm'\r\n# Erase background with current bg color.  Not needed if TERM=screen-256color\r\ndefbce \"on\"\r\n\r\nWhen everything is set and done, copy xoria256.vim into ~\/.vim\/colors.  To use it, issue ':colo xoria256' in {,g}vim.","first_name":"Dmitriy","6":"Dmitriy","last_name":"Zotikov","7":"Zotikov","releases":[{"0":"2140","vim_version":"8.0","1":"8.0","script_version":"1.8","2":"1.8","version_comment":"Add new colour definitions for StatusLineTerm, StatusLineTermNC (thanks, Hugh)","3":"Add new colour definitions for StatusLineTerm, StatusLineTermNC (thanks, Hugh)","package":"xoria256.vim","4":"xoria256.vim","src_id":"26882","5":"26882","creation_date":"1577857008","6":"1577857008"},{"0":"2140","vim_version":"7.0","1":"7.0","script_version":"1.7","2":"1.7","version_comment":"Add licencing information.","3":"Add licencing information.","package":"xoria256.vim","4":"xoria256.vim","src_id":"26507","5":"26507","creation_date":"1559449922","6":"1559449922"},{"0":"2140","vim_version":"7.0","1":"7.0","script_version":"1.6","2":"1.6","version_comment":"minor changes","3":"minor changes","package":"xoria256.vim","4":"xoria256.vim","src_id":"23975","5":"23975","creation_date":"1454282868","6":"1454282868"},{"0":"2140","vim_version":"7.0","1":"7.0","script_version":"1.5","2":"1.5","version_comment":"Experimental colours for HTML, NERDTree plugin, django templates, something else... Some fixes from the cool folks 'round the globe (big up!)","3":"Experimental colours for HTML, NERDTree plugin, django templates, something else... Some fixes from the cool folks 'round the globe (big up!)","package":"xoria256.vim","4":"xoria256.vim","src_id":"15762","5":"15762","creation_date":"1306735381","6":"1306735381"},{"0":"2140","vim_version":"7.0","1":"7.0","script_version":"1.4","2":"1.4","version_comment":"Spelling errors highlighting colours are taken from railscasts.vim as suggested. Thanks!","3":"Spelling errors highlighting colours are taken from railscasts.vim as suggested. Thanks!","package":"xoria256.vim","4":"xoria256.vim","src_id":"14251","5":"14251","creation_date":"1289659099","6":"1289659099"},{"0":"2140","vim_version":"7.0","1":"7.0","script_version":"1.3","2":"1.3","version_comment":"Few updates here and there.","3":"Few updates here and there.","package":"xoria256.vim","4":"xoria256.vim","src_id":"14249","5":"14249","creation_date":"1289640551","6":"1289640551"},{"0":"2140","vim_version":"7.0","1":"7.0","script_version":"1.2","2":"1.2","version_comment":"WildMenu uses the green as a highlight, NonText and LineNr are darker than normal text.\r\n","3":"WildMenu uses the green as a highlight, NonText and LineNr are darker than normal text.\r\n","package":"xoria256.vim","4":"xoria256.vim","src_id":"12917","5":"12917","creation_date":"1272623327","6":"1272623327"},{"0":"2140","vim_version":"7.0","1":"7.0","script_version":"1.1","2":"1.1","version_comment":"New colors in vimdiff mode (thanks, Scrool); Highlight Errors with background red (thanks, Diwaker); Make Identifier non-bold.","3":"New colors in vimdiff mode (thanks, Scrool); Highlight Errors with background red (thanks, Diwaker); Make Identifier non-bold.","package":"xoria256.vim","4":"xoria256.vim","src_id":"10321","5":"10321","creation_date":"1238402501","6":"1238402501"},{"0":"2140","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Major update. Full code rewrite, many fixes.","3":"Major update. Full code rewrite, many fixes.","package":"xoria256.vim","4":"xoria256.vim","src_id":"9862","5":"9862","creation_date":"1232912991","6":"1232912991"},{"0":"2140","vim_version":"7.0","1":"7.0","script_version":"0.3.2","2":"0.3.2","version_comment":"Small fix for 'Ignore' highlight (some elements were not displayed properly in vim :help files)","3":"Small fix for 'Ignore' highlight (some elements were not displayed properly in vim :help files)","package":"xoria256.vim","4":"xoria256.vim","src_id":"8721","5":"8721","creation_date":"1211630926","6":"1211630926"},{"0":"2140","vim_version":"7.0","1":"7.0","script_version":"0.3.1","2":"0.3.1","version_comment":"Small fixes for 'Number', 'Identifier' and 'Special' highlights. Sorry for that frequent updates, but I feel almost physical pain when I see a smallest color inconsistency. I'm still not completly satisfied with what is done, however, so, please, send me your ideas on how the scheme could be improved in your opinion.","3":"Small fixes for 'Number', 'Identifier' and 'Special' highlights. Sorry for that frequent updates, but I feel almost physical pain when I see a smallest color inconsistency. I'm still not completly satisfied with what is done, however, so, please, send me your ideas on how the scheme could be improved in your opinion.","package":"xoria256.vim","4":"xoria256.vim","src_id":"8692","5":"8692","creation_date":"1210854595","6":"1210854595"},{"0":"2140","vim_version":"7.0","1":"7.0","script_version":"0.3","2":"0.3","version_comment":"Lots of changes, please upgrade!","3":"Lots of changes, please upgrade!","package":"xoria256.vim","4":"xoria256.vim","src_id":"8667","5":"8667","creation_date":"1210328722","6":"1210328722"},{"0":"2140","vim_version":"7.0","1":"7.0","script_version":"0.2","2":"0.2","version_comment":"Small fixes for 'Folded' and 'Number' highlights. Thanks, Diwaker!","3":"Small fixes for 'Folded' and 'Number' highlights. Thanks, Diwaker!","package":"xoria256.vim","4":"xoria256.vim","src_id":"8641","5":"8641","creation_date":"1209778604","6":"1209778604"},{"0":"2140","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"xoria256.vim","4":"xoria256.vim","src_id":"8227","5":"8227","creation_date":"1202034856","6":"1202034856"}]},"2139":{"script_id":"2139","0":"2139","script_name":"sgf.vim","1":"sgf.vim","script_type":"syntax","2":"syntax","summary":"SFG - Smart Game Fomat (Go savegames)","3":"SFG - Smart Game Fomat (Go savegames)","description":"Syntax highlighting for the Smart Game Format, which is the default savegame format for the two-player Go game.\r\nIt is not very complete yet, as I'll work on it as the need arises. But it makes it a lot easier to dig through the SGF information already than just having everything white on black.","4":"Syntax highlighting for the Smart Game Format, which is the default savegame format for the two-player Go game.\r\nIt is not very complete yet, as I'll work on it as the need arises. But it makes it a lot easier to dig through the SGF information already than just having everything white on black.","install_details":"","5":"","first_name":"Josef","6":"Josef","last_name":"Spillner","7":"Spillner","releases":[{"0":"2139","vim_version":"6.0","1":"6.0","script_version":"0.0.1","2":"0.0.1","version_comment":"Initial upload","3":"Initial upload","package":"sgf.vim","4":"sgf.vim","src_id":"8226","5":"8226","creation_date":"1202024109","6":"1202024109"}]},"2138":{"script_id":"2138","0":"2138","script_name":"PBwiki syntax highlighting","1":"PBwiki syntax highlighting","script_type":"syntax","2":"syntax","summary":"Syntax highlighting and an ftplugin for PBwiki","3":"Syntax highlighting and an ftplugin for PBwiki","description":"Syntax highlighting for PBwiki, http:\/\/pbwiki.com\/. Also a filetype detection script which sets appropriate buffer-local options for editing long lines, etc.\r\n\r\nLatest copy can be found at http:\/\/www.georgevreilly.com\/vim\/pbwiki\/","4":"Syntax highlighting for PBwiki, http:\/\/pbwiki.com\/. Also a filetype detection script which sets appropriate buffer-local options for editing long lines, etc.\r\n\r\nLatest copy can be found at http:\/\/www.georgevreilly.com\/vim\/pbwiki\/","install_details":"Create a HOME directory, if you haven't already\r\nCreate a \"vimfiles\" (Windows) or \".vim\" (Unix\/Mac) folder in your HOME directory.\r\nUnzip pbwiki.zip in that vimfiles (.vim) folder.\r\nRestart Vim\r\n\r\nSee \":help add-global-plugin\" for more details","5":"Create a HOME directory, if you haven't already\r\nCreate a \"vimfiles\" (Windows) or \".vim\" (Unix\/Mac) folder in your HOME directory.\r\nUnzip pbwiki.zip in that vimfiles (.vim) folder.\r\nRestart Vim\r\n\r\nSee \":help add-global-plugin\" for more details","first_name":"George V.","6":"George V.","last_name":"Reilly","7":"Reilly","releases":[{"0":"2138","vim_version":"6.0","1":"6.0","script_version":"0.21","2":"0.21","version_comment":"Converted DOS line endings to Unix format.","3":"Converted DOS line endings to Unix format.","package":"pbwiki.zip","4":"pbwiki.zip","src_id":"8258","5":"8258","creation_date":"1202673154","6":"1202673154"},{"0":"2138","vim_version":"6.0","1":"6.0","script_version":"0.2","2":"0.2","version_comment":"Clean-up. Better matching of PBwiki constructs. Removed stale Flexwiki matches that have no PBwiki equivalent.","3":"Clean-up. Better matching of PBwiki constructs. Removed stale Flexwiki matches that have no PBwiki equivalent.","package":"pbwiki.zip","4":"pbwiki.zip","src_id":"8228","5":"8228","creation_date":"1202041993","6":"1202041993"},{"0":"2138","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Re-upload now that I know the script_id. Chicken, meet egg.","3":"Re-upload now that I know the script_id. Chicken, meet egg.","package":"pbwiki.zip","4":"pbwiki.zip","src_id":"8219","5":"8219","creation_date":"1202001378","6":"1202001378"}]},"2137":{"script_id":"2137","0":"2137","script_name":"Css Pretty","1":"Css Pretty","script_type":"utility","2":"utility","summary":"Pretty-print a css file","3":"Pretty-print a css file","description":"Simple script to format text as CSS in readable format","4":"Simple script to format text as CSS in readable format","install_details":"place in plugin directory","5":"place in plugin directory","first_name":"Todd","6":"Todd","last_name":"Freed","7":"Freed","releases":[{"0":"2137","vim_version":"7.0","1":"7.0","script_version":"1.1","2":"1.1","version_comment":"patch provided by hotoo dot cn at gmail dot com \r\n\r\nfixes parsing error with properties enclosed in parentheses (url, for example)","3":"patch provided by hotoo dot cn at gmail dot com \r\n\r\nfixes parsing error with properties enclosed in parentheses (url, for example)","package":"csspretty.vim","4":"csspretty.vim","src_id":"13560","5":"13560","creation_date":"1281709894","6":"1281709894"},{"0":"2137","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"csspretty.vim","4":"csspretty.vim","src_id":"8211","5":"8211","creation_date":"1201894154","6":"1201894154"}]},"2136":{"script_id":"2136","0":"2136","script_name":"repeat.vim","1":"repeat.vim","script_type":"utility","2":"utility","summary":"Use the repeat command (.) with supported plugins","3":"Use the repeat command (.) with supported plugins","description":"If you've ever tried using the \".\" command after a plugin map, you were likely disappointed to discover it only repeated the last native command inside that map, rather than the map as a whole.  That disappointment ends today.  Repeat.vim remaps \".\" in a way that plugins can tap into it.\r\n\r\nSupport is already present in the following plugins:\r\n\r\nsurround.vim (vimscript #1697)\r\nspeeddating.vim (vimscript #2120)\r\nabolish.vim (vimscript #1545)\r\nunimpaired.vim (vimscript #1590)\r\ncommentary.vim (vimscript #3695)\r\n\r\nAdding support to a plugin is generally as simple as the following command at the end of your map functions.\r\n\r\n  silent! call repeat#set(\"\\<Plug>MyWonderfulMap\",v:count)\r\n\r\nDetails are at the top of the file.  Let me know if you add support to a script on vim.org and I will link it here.\r\n\r\nhttp:\/\/github.com\/tpope\/vim-repeat","4":"If you've ever tried using the \".\" command after a plugin map, you were likely disappointed to discover it only repeated the last native command inside that map, rather than the map as a whole.  That disappointment ends today.  Repeat.vim remaps \".\" in a way that plugins can tap into it.\r\n\r\nSupport is already present in the following plugins:\r\n\r\nsurround.vim (vimscript #1697)\r\nspeeddating.vim (vimscript #2120)\r\nabolish.vim (vimscript #1545)\r\nunimpaired.vim (vimscript #1590)\r\ncommentary.vim (vimscript #3695)\r\n\r\nAdding support to a plugin is generally as simple as the following command at the end of your map functions.\r\n\r\n  silent! call repeat#set(\"\\<Plug>MyWonderfulMap\",v:count)\r\n\r\nDetails are at the top of the file.  Let me know if you add support to a script on vim.org and I will link it here.\r\n\r\nhttp:\/\/github.com\/tpope\/vim-repeat","install_details":"Install in ~\/.vim\/autoload\/repeat.vim (~\\vim\\autoload\\repeat.vim on Windows).","5":"Install in ~\/.vim\/autoload\/repeat.vim (~\\vim\\autoload\\repeat.vim on Windows).","first_name":"Tim","6":"Tim","last_name":"Pope","7":"Pope","releases":[{"0":"2136","vim_version":"7.0","1":"7.0","script_version":"1.2","2":"1.2","version_comment":"Provide <Plug> mappings.\r\nEnable repeating operators with custom motions.\r\nAssorted bug fixes.","3":"Provide <Plug> mappings.\r\nEnable repeating operators with custom motions.\r\nAssorted bug fixes.","package":"repeat.zip","4":"repeat.zip","src_id":"25810","5":"25810","creation_date":"1517371747","6":"1517371747"},{"0":"2136","vim_version":"7.0","1":"7.0","script_version":"1.1","2":"1.1","version_comment":"Fix adding trailing spaces when 've' is not empty.\r\nDon't increment b:changedtick, offer invalidate instead.\r\nSupport repetition with original register.\r\nDon't clobber existing U map.\r\nRespect 'foldopen' on undo.\r\nAllow customizing all mappings.","3":"Fix adding trailing spaces when 've' is not empty.\r\nDon't increment b:changedtick, offer invalidate instead.\r\nSupport repetition with original register.\r\nDon't clobber existing U map.\r\nRespect 'foldopen' on undo.\r\nAllow customizing all mappings.","package":"repeat.zip","4":"repeat.zip","src_id":"19285","5":"19285","creation_date":"1357056861","6":"1357056861"},{"0":"2136","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"repeat.vim","4":"repeat.vim","src_id":"8206","5":"8206","creation_date":"1201795708","6":"1201795708"}]},"2135":{"script_id":"2135","0":"2135","script_name":"syntax highlighting for tintin\/tt++","1":"syntax highlighting for tintin\/tt++","script_type":"syntax","2":"syntax","summary":"great little syntax file for all you mudders!","3":"great little syntax file for all you mudders!","description":"cool vim syntax file for tt++ \/ tintin...http:\/\/tintin.sourceforge.net\/\r\nonly the best mud client available to man!\r\n\r\nnote***this file is in a linux format, it probably won't work straightaway on a windows box...you'll have to go reset the cr \/ crlf's i believe.\r\n\r\n-=Todo=-\r\nExpand keyword selection to include caps...right now #alias \/ #action and all other keywords are on highlighted if they are in lowercase.\r\nIf you have any suggestions please feel free to mail me at \r\ncheshire.in.darkness ::at:: gmail ::dot:: com\r\n\r\nthanks!","4":"cool vim syntax file for tt++ \/ tintin...http:\/\/tintin.sourceforge.net\/\r\nonly the best mud client available to man!\r\n\r\nnote***this file is in a linux format, it probably won't work straightaway on a windows box...you'll have to go reset the cr \/ crlf's i believe.\r\n\r\n-=Todo=-\r\nExpand keyword selection to include caps...right now #alias \/ #action and all other keywords are on highlighted if they are in lowercase.\r\nIf you have any suggestions please feel free to mail me at \r\ncheshire.in.darkness ::at:: gmail ::dot:: com\r\n\r\nthanks!","install_details":"simply copy this file to \/usr\/share\/vim\/vim71\/syntax or ~\/.vim\/syntax\r\nand then execute the following command in vim\r\n:set syntax=tt","5":"simply copy this file to \/usr\/share\/vim\/vim71\/syntax or ~\/.vim\/syntax\r\nand then execute the following command in vim\r\n:set syntax=tt","first_name":"Jared","6":"Jared","last_name":"Smith","7":"Smith","releases":[{"0":"2135","vim_version":"7.0","1":"7.0","script_version":"a","2":"a","version_comment":"Initial upload","3":"Initial upload","package":"tt.vim","4":"tt.vim","src_id":"8205","5":"8205","creation_date":"1201779268","6":"1201779268"}]},"2134":{"script_id":"2134","0":"2134","script_name":"tabpage_sort.vim","1":"tabpage_sort.vim","script_type":"utility","2":"utility","summary":"Sort vim7 tab page in 'buffer number' order.","3":"Sort vim7 tab page in 'buffer number' order.","description":"sort vim7 tab page in 'buffer number' order.\r\n\r\nInstallation\r\n------------\r\n1. Copy the tabpage_sort.vim script to the $HOME\/.vim\/plugin or\r\n   the $HOME\/vimfiles\/plugin. Refer to the ':help add-plugin',\r\n   ':help add-global-plugin' and ':help runtimepath' topics for\r\n   more details about Vim plugins.\r\n2. Restart Vim.\r\n\r\nUsage\r\n-----\r\n1. Run command ':TabpageSort', ':TabpageSort asc', ':TabpageSort desc',\r\n   ':TabpageSortAsc' or ':TabpageSortDesc'.\r\n\r\n   :TabpageSort           sort vim7 tab page in buffer number ascending order.\r\n   :TabpageSort asc       sort vim7 tab page in buffer number ascending order.\r\n   :TabpageSort desc      sort vim7 tab page in buffer number descending order.\r\n   :TabpageSortAsc        sort vim7 tab page in buffer number ascending order.\r\n   :TabpageSortDesc       sort vim7 tab page in buffer number descending order.\r\n\r\nNote\r\n----\r\n1. If current buffer size is over current 'tabpagemax' option setting,\r\n   'tabpagemax' option size is automatically expanded.\r\n   see \":help tabpagemax\".\r\n","4":"sort vim7 tab page in 'buffer number' order.\r\n\r\nInstallation\r\n------------\r\n1. Copy the tabpage_sort.vim script to the $HOME\/.vim\/plugin or\r\n   the $HOME\/vimfiles\/plugin. Refer to the ':help add-plugin',\r\n   ':help add-global-plugin' and ':help runtimepath' topics for\r\n   more details about Vim plugins.\r\n2. Restart Vim.\r\n\r\nUsage\r\n-----\r\n1. Run command ':TabpageSort', ':TabpageSort asc', ':TabpageSort desc',\r\n   ':TabpageSortAsc' or ':TabpageSortDesc'.\r\n\r\n   :TabpageSort           sort vim7 tab page in buffer number ascending order.\r\n   :TabpageSort asc       sort vim7 tab page in buffer number ascending order.\r\n   :TabpageSort desc      sort vim7 tab page in buffer number descending order.\r\n   :TabpageSortAsc        sort vim7 tab page in buffer number ascending order.\r\n   :TabpageSortDesc       sort vim7 tab page in buffer number descending order.\r\n\r\nNote\r\n----\r\n1. If current buffer size is over current 'tabpagemax' option setting,\r\n   'tabpagemax' option size is automatically expanded.\r\n   see \":help tabpagemax\".\r\n","install_details":"1. Copy the tabpage_sort.vim script to the $HOME\/.vim\/plugin or\r\n   the $HOME\/vimfiles\/plugin. Refer to the ':help add-plugin',\r\n   ':help add-global-plugin' and ':help runtimepath' topics for\r\n   more details about Vim plugins.\r\n2. Restart Vim.","5":"1. Copy the tabpage_sort.vim script to the $HOME\/.vim\/plugin or\r\n   the $HOME\/vimfiles\/plugin. Refer to the ':help add-plugin',\r\n   ':help add-global-plugin' and ':help runtimepath' topics for\r\n   more details about Vim plugins.\r\n2. Restart Vim.","first_name":"omi","6":"omi","last_name":"taku","7":"taku","releases":[{"0":"2134","vim_version":"7.0","1":"7.0","script_version":"0.8","2":"0.8","version_comment":"Initial upload","3":"Initial upload","package":"tabpage_sort.vim","4":"tabpage_sort.vim","src_id":"8204","5":"8204","creation_date":"1201773847","6":"1201773847"}]},"2133":{"script_id":"2133","0":"2133","script_name":"tintin.vim","1":"tintin.vim","script_type":"syntax","2":"syntax","summary":"Syntax Highlighting for Tintin++","3":"Syntax Highlighting for Tintin++","description":"TinTin++ is a free mud client that runs on the Windows, Linux, and Mac OSX platforms.\r\n\r\nif can be found here: http:\/\/tintin.sourceforge.net\/ \r\n\r\ncontains syntax for commands, color codes, comments, braces, quotes, and variables cmd separators, although this is pretty average, and doesnt do nearly as much as i want it to do. \r\n\r\nfor a better version, check this out http:\/\/www.vim.org\/scripts\/script.php?script_id=2135","4":"TinTin++ is a free mud client that runs on the Windows, Linux, and Mac OSX platforms.\r\n\r\nif can be found here: http:\/\/tintin.sourceforge.net\/ \r\n\r\ncontains syntax for commands, color codes, comments, braces, quotes, and variables cmd separators, although this is pretty average, and doesnt do nearly as much as i want it to do. \r\n\r\nfor a better version, check this out http:\/\/www.vim.org\/scripts\/script.php?script_id=2135","install_details":"","5":"","first_name":"Mark","6":"Mark","last_name":"Vandenbos","7":"Vandenbos","releases":[{"0":"2133","vim_version":"6.0","1":"6.0","script_version":"1.1","2":"1.1","version_comment":"added CmdSep\r\nchanged ttColor & ttVariable to match digits instead of words\r\ntweaked colors","3":"added CmdSep\r\nchanged ttColor & ttVariable to match digits instead of words\r\ntweaked colors","package":"tintin.vim","4":"tintin.vim","src_id":"8200","5":"8200","creation_date":"1201632602","6":"1201632602"},{"0":"2133","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"tintin.vim","4":"tintin.vim","src_id":"8199","5":"8199","creation_date":"1201630264","6":"1201630264"}]},"2132":{"script_id":"2132","0":"2132","script_name":"byter","1":"byter","script_type":"syntax","2":"syntax","summary":"byter syntax support","3":"byter syntax support","description":"Support for byter esoteric programming language.","4":"Support for byter esoteric programming language.","install_details":"","5":"","first_name":"Sergey","6":"Sergey","last_name":"Zasenko","7":"Zasenko","releases":[{"0":"2132","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"byter.vim","4":"byter.vim","src_id":"8193","5":"8193","creation_date":"1201593751","6":"1201593751"}]},"2131":{"script_id":"2131","0":"2131","script_name":"Socialtext wiki syntax highlighting","1":"Socialtext wiki syntax highlighting","script_type":"syntax","2":"syntax","summary":"Syntax highlighting and an ftplugin for Socialtext wiki","3":"Syntax highlighting and an ftplugin for Socialtext wiki","description":"Syntax highlighting for the Socialtext wiki, http:\/\/www.socialtext.net\/. Also a filetype detection script which sets appropriate buffer-local options for editing long lines, etc.\r\n\r\nLatest copy can be found at http:\/\/www.georgevreilly.com\/vim\/stwiki\/","4":"Syntax highlighting for the Socialtext wiki, http:\/\/www.socialtext.net\/. Also a filetype detection script which sets appropriate buffer-local options for editing long lines, etc.\r\n\r\nLatest copy can be found at http:\/\/www.georgevreilly.com\/vim\/stwiki\/","install_details":"Create a HOME directory, if you haven't already\r\nCreate a \"vimfiles\" (Windows) or \".vim\" (Unix\/Mac) folder in your HOME directory.\r\nUnzip stwiki.zip in that vimfiles (.vim) folder.\r\nRestart Vim\r\n\r\nSee \":help add-global-plugin\" for more details\r\n","5":"Create a HOME directory, if you haven't already\r\nCreate a \"vimfiles\" (Windows) or \".vim\" (Unix\/Mac) folder in your HOME directory.\r\nUnzip stwiki.zip in that vimfiles (.vim) folder.\r\nRestart Vim\r\n\r\nSee \":help add-global-plugin\" for more details\r\n","first_name":"George V.","6":"George V.","last_name":"Reilly","7":"Reilly","releases":[{"0":"2131","vim_version":"6.0","1":"6.0","script_version":"0.32","2":"0.32","version_comment":"Changed DOS line endings to Unix format.","3":"Changed DOS line endings to Unix format.","package":"stwiki.zip","4":"stwiki.zip","src_id":"8259","5":"8259","creation_date":"1202673223","6":"1202673223"},{"0":"2131","vim_version":"6.0","1":"6.0","script_version":"0.31","2":"0.31","version_comment":"Use forward slashes in the ftplugin, not backslashes.","3":"Use forward slashes in the ftplugin, not backslashes.","package":"stwiki.zip","4":"stwiki.zip","src_id":"8218","5":"8218","creation_date":"1202001312","6":"1202001312"}]},"2130":{"script_id":"2130","0":"2130","script_name":"XmlPretty","1":"XmlPretty","script_type":"utility","2":"utility","summary":"Pretty-print an xml file","3":"Pretty-print an xml file","description":"Simple script that treats your buffer as an xml file and indents it for easy reading","4":"Simple script that treats your buffer as an xml file and indents it for easy reading","install_details":"place in plugin directory. I have it mapped to <F5>","5":"place in plugin directory. I have it mapped to <F5>","first_name":"Todd","6":"Todd","last_name":"Freed","7":"Freed","releases":[{"0":"2130","vim_version":"7.0","1":"7.0","script_version":"1.5","2":"1.5","version_comment":"Added ability to pass line ranges and\/or return resulting text as List of strings. Also added <a href=\"http:\/\/www.vim.org\/scripts\/script.php?script_id=2137\">CssPretty<\/a> which is invoked from XmlPretty to format the contents of <style> tags.","3":"Added ability to pass line ranges and\/or return resulting text as List of strings. Also added <a href=\"http:\/\/www.vim.org\/scripts\/script.php?script_id=2137\">CssPretty<\/a> which is invoked from XmlPretty to format the contents of <style> tags.","package":"xmlpretty.vim","4":"xmlpretty.vim","src_id":"8212","5":"8212","creation_date":"1201894319","6":"1201894319"},{"0":"2130","vim_version":"7.0","1":"7.0","script_version":"7.1","2":"7.1","version_comment":"Initial upload","3":"Initial upload","package":"xmlpretty.vim","4":"xmlpretty.vim","src_id":"8183","5":"8183","creation_date":"1201351367","6":"1201351367"}]},"2129":{"script_id":"2129","0":"2129","script_name":"Noweb","1":"Noweb","script_type":"syntax","2":"syntax","summary":"A hacked-up noweb syntax file","3":"A hacked-up noweb syntax file","description":"The original nw.vim file isn't working with new environments. I had made a few irrelevant hacks, and changed the name of the script out of no reason.","4":"The original nw.vim file isn't working with new environments. I had made a few irrelevant hacks, and changed the name of the script out of no reason.","install_details":"As usual.","5":"As usual.","first_name":"Xun","6":"Xun","last_name":"GONG","7":"GONG","releases":[{"0":"2129","vim_version":"6.0","1":"6.0","script_version":"1.2","2":"1.2","version_comment":"Initial upload","3":"Initial upload","package":"noweb.vim","4":"noweb.vim","src_id":"8182","5":"8182","creation_date":"1201348345","6":"1201348345"}]},"2128":{"script_id":"2128","0":"2128","script_name":"symfony.vim","1":"symfony.vim","script_type":"utility","2":"utility","summary":"Useful editing tip for Symfony PHP Framework","3":"Useful editing tip for Symfony PHP Framework","description":"DESCRIPTION\r\n\r\nUsefull commands for symfony projects editing\r\n\r\n* Switch between template view \/ module view ( <F8> key )\r\n\r\n  While editing a module method, press <F8>. It will switch to the appropriate template view\r\n  Press <F8> again to go back to the module method .\r\n\r\n  It works with Actions and Components :\r\n\r\n    function executeMyAction() < > myActionSuccess.php\r\n    function executeMyComponent() < > _myComponent.php \r\n\r\nTODO \r\n\r\n* Support for xxxError, handleXXX, validateXXX\r\n* Shortcuts to the layout template of an action\/view\r\n* Support for empty action files and missing templates\r\n\r\nFeedbacks mostly appreciated : email.de.nicolas.martin@gmail.com\r\n","4":"DESCRIPTION\r\n\r\nUsefull commands for symfony projects editing\r\n\r\n* Switch between template view \/ module view ( <F8> key )\r\n\r\n  While editing a module method, press <F8>. It will switch to the appropriate template view\r\n  Press <F8> again to go back to the module method .\r\n\r\n  It works with Actions and Components :\r\n\r\n    function executeMyAction() < > myActionSuccess.php\r\n    function executeMyComponent() < > _myComponent.php \r\n\r\nTODO \r\n\r\n* Support for xxxError, handleXXX, validateXXX\r\n* Shortcuts to the layout template of an action\/view\r\n* Support for empty action files and missing templates\r\n\r\nFeedbacks mostly appreciated : email.de.nicolas.martin@gmail.com\r\n","install_details":"- copy the symfony.vim in your plugin directory and run Vim.\r\n\r\n- optionnaly map <F8> or any key to the switching command by typing : silent map <F8> :SfSwitchView <CR>\r\n\r\nYou can now easily switch between Action view \/ Template view of an action.\r\n\r\nNote : When entering a buffer, the plugin detects the symfony root dir from the current working directory ( getpwd() ) \r\n\r\n","5":"- copy the symfony.vim in your plugin directory and run Vim.\r\n\r\n- optionnaly map <F8> or any key to the switching command by typing : silent map <F8> :SfSwitchView <CR>\r\n\r\nYou can now easily switch between Action view \/ Template view of an action.\r\n\r\nNote : When entering a buffer, the plugin detects the symfony root dir from the current working directory ( getpwd() ) \r\n\r\n","first_name":"Nicolas","6":"Nicolas","last_name":"MARTIN","7":"MARTIN","releases":[{"0":"2128","vim_version":"7.0","1":"7.0","script_version":"0.7","2":"0.7","version_comment":"Major update : Symfony 1.1 compatibilty\r\n\r\nThe method parameters of an action introduced in 1.1 is now handled.\r\n\r\nsymfony 1.0.X : public function executeEdit()\r\nsymfony 1.1.X : public function executeEdit($request) \r\n","3":"Major update : Symfony 1.1 compatibilty\r\n\r\nThe method parameters of an action introduced in 1.1 is now handled.\r\n\r\nsymfony 1.0.X : public function executeEdit()\r\nsymfony 1.1.X : public function executeEdit($request) \r\n","package":"symfony.vim","4":"symfony.vim","src_id":"8739","5":"8739","creation_date":"1211939176","6":"1211939176"},{"0":"2128","vim_version":"6.0","1":"6.0","script_version":"0.6","2":"0.6","version_comment":"Enable use for custom symfony projects tree structure ( disabling directory presence check ) ( reported by Tom Haskins )","3":"Enable use for custom symfony projects tree structure ( disabling directory presence check ) ( reported by Tom Haskins )","package":"symfony.vim","4":"symfony.vim","src_id":"8728","5":"8728","creation_date":"1211769221","6":"1211769221"},{"0":"2128","vim_version":"7.0","1":"7.0","script_version":"0.5","2":"0.5","version_comment":"Added automatic sf_root_dir detection ( suggested by Gr\u00c3\u00a9goire Hubert )","3":"Added automatic sf_root_dir detection ( suggested by Gr\u00c3\u00a9goire Hubert )","package":"symfony.vim","4":"symfony.vim","src_id":"8560","5":"8560","creation_date":"1208159729","6":"1208159729"},{"0":"2128","vim_version":"7.0","1":"7.0","script_version":"0.4","2":"0.4","version_comment":"Added : SfPluginLoad command replacing the manual path configuration\r\nModified : Installation details","3":"Added : SfPluginLoad command replacing the manual path configuration\r\nModified : Installation details","package":"symfony.vim","4":"symfony.vim","src_id":"8399","5":"8399","creation_date":"1204770300","6":"1204770300"},{"0":"2128","vim_version":"6.0","1":"6.0","script_version":"0.3","2":"0.3","version_comment":"Major update : Unix paths are now handled correctly\r\n\r\nThe plugin now works on Linux systems.","3":"Major update : Unix paths are now handled correctly\r\n\r\nThe plugin now works on Linux systems.","package":"symfony.vim","4":"symfony.vim","src_id":"8367","5":"8367","creation_date":"1204250906","6":"1204250906"},{"0":"2128","vim_version":"7.0","1":"7.0","script_version":"0.2","2":"0.2","version_comment":"Added support for Components module\/template switching\r\n","3":"Added support for Components module\/template switching\r\n","package":"symfony.vim","4":"symfony.vim","src_id":"8239","5":"8239","creation_date":"1202213887","6":"1202213887"},{"0":"2128","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Bug fixes","3":"Bug fixes","package":"symfony.vim","4":"symfony.vim","src_id":"8176","5":"8176","creation_date":"1201156614","6":"1201156614"}]},"2127":{"script_id":"2127","0":"2127","script_name":"Wikidoc syntax highlighting","1":"Wikidoc syntax highlighting","script_type":"syntax","2":"syntax","summary":"Wikidoc format syntax highlighting","3":"Wikidoc format syntax highlighting","description":"Syntax highlighting for Wikidoc format in vim.\r\nI don't know if anybody uses the wikidoc format...\r\nI hope it will be useful to you.\r\nIt's pretty stupid now...\r\n","4":"Syntax highlighting for Wikidoc format in vim.\r\nI don't know if anybody uses the wikidoc format...\r\nI hope it will be useful to you.\r\nIt's pretty stupid now...\r\n","install_details":"Usually you should copy this file into your ~\/.vim\/syntax folder","5":"Usually you should copy this file into your ~\/.vim\/syntax folder","first_name":"Cosimo","6":"Cosimo","last_name":"Streppone","7":"Streppone","releases":[{"0":"2127","vim_version":"7.0","1":"7.0","script_version":"0.01","2":"0.01","version_comment":"Initial upload","3":"Initial upload","package":"wikidoc.vim","4":"wikidoc.vim","src_id":"8169","5":"8169","creation_date":"1200879999","6":"1200879999"}]},"2126":{"script_id":"2126","0":"2126","script_name":"accurev","1":"accurev","script_type":"utility","2":"utility","summary":"AccuRev SCM Integration for Vim","3":"AccuRev SCM Integration for Vim","description":"This is the AccuRev SCM Integration for Vim.  \r\n\r\nAccuRev is a leading Software Configuration Management (SCM) application that enables massive, parallel software development across local and distributed geographic boundaries.  If you develop software in large teams with multiple releases or product variants... AccuRev is for you. See more at http:\/\/www.accurev.com.\r\n\r\nThis plugin provides the ability to perform 20+ AccuRev commands (keep, promote, update, merge, etc) directly within Vim.  \r\n\r\nThe plugin requires Vim 7.x and supports AccuRev 4.5\/4.6\/4.7.  Developed on linux (Ubuntu 8.04), it has also been tested on Windows (XPsp2).\r\n\r\nFork me on github: https:\/\/github.com\/davidpthomas\/vim4accurev\r\n\r\nUpdate Aug 2012: The AccuRev CLI should have no backward incompatible changes so the 'core' commands used in this plugin should work even with recent versions of AccuRev.\r\n","4":"This is the AccuRev SCM Integration for Vim.  \r\n\r\nAccuRev is a leading Software Configuration Management (SCM) application that enables massive, parallel software development across local and distributed geographic boundaries.  If you develop software in large teams with multiple releases or product variants... AccuRev is for you. See more at http:\/\/www.accurev.com.\r\n\r\nThis plugin provides the ability to perform 20+ AccuRev commands (keep, promote, update, merge, etc) directly within Vim.  \r\n\r\nThe plugin requires Vim 7.x and supports AccuRev 4.5\/4.6\/4.7.  Developed on linux (Ubuntu 8.04), it has also been tested on Windows (XPsp2).\r\n\r\nFork me on github: https:\/\/github.com\/davidpthomas\/vim4accurev\r\n\r\nUpdate Aug 2012: The AccuRev CLI should have no backward incompatible changes so the 'core' commands used in this plugin should work even with recent versions of AccuRev.\r\n","install_details":"Unpack the zip file directly in your [unix] $HOME\/.vim or [windows] $HOME\/vimfiles directory.  See INSTALL.vim4accurev for installation instructions.","5":"Unpack the zip file directly in your [unix] $HOME\/.vim or [windows] $HOME\/vimfiles directory.  See INSTALL.vim4accurev for installation instructions.","first_name":"David","6":"David","last_name":"Thomas","7":"Thomas","releases":[{"0":"2126","vim_version":"7.0","1":"7.0","script_version":"1.1.1","2":"1.1.1","version_comment":"support for optionally requiring commit comments; ideal for preventing accidental <Enter> or <Esc> at commit time; minor string\/path compare patch for Windows users during workspace detection (thanks Charles Bates)","3":"support for optionally requiring commit comments; ideal for preventing accidental <Enter> or <Esc> at commit time; minor string\/path compare patch for Windows users during workspace detection (thanks Charles Bates)","package":"vim4accurev-1.1.1.zip","4":"vim4accurev-1.1.1.zip","src_id":"11212","5":"11212","creation_date":"1250615643","6":"1250615643"},{"0":"2126","vim_version":"7.0","1":"7.0","script_version":"1.1.0","2":"1.1.0","version_comment":"In-session plugin enable\/disable useful on slow network connections; gvim per-buffer graphical menus; new annotate\/blame feature; removed dependency on cwd allows editing workspace files from anywhere (user reported fix); ability to launch stream browser; ability to launch graphical merge on true conflict.  updated docs + more content.  General script refactoring and housecleaning.  enjoy!","3":"In-session plugin enable\/disable useful on slow network connections; gvim per-buffer graphical menus; new annotate\/blame feature; removed dependency on cwd allows editing workspace files from anywhere (user reported fix); ability to launch stream browser; ability to launch graphical merge on true conflict.  updated docs + more content.  General script refactoring and housecleaning.  enjoy!","package":"vim4accurev-1.1.0.zip","4":"vim4accurev-1.1.0.zip","src_id":"11199","5":"11199","creation_date":"1250451089","6":"1250451089"},{"0":"2126","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial version.","3":"Initial version.","package":"vim4accurev-1.0.1.zip","4":"vim4accurev-1.0.1.zip","src_id":"8178","5":"8178","creation_date":"1201188834","6":"1201188834"}]},"2125":{"script_id":"2125","0":"2125","script_name":"SDL library syntax (for C)","1":"SDL library syntax (for C)","script_type":"syntax","2":"syntax","summary":"SDL library syntax for C","3":"SDL library syntax for C","description":"SDL library syntax for C","4":"SDL library syntax for C","install_details":"Add this to the end of your C syntax file:\r\n\r\nif version < 600\r\n  so <sfile>:p:h\/libsdl.vim\r\nelse\r\n  runtime! syntax\/libsdl.vim\r\nendif","5":"Add this to the end of your C syntax file:\r\n\r\nif version < 600\r\n  so <sfile>:p:h\/libsdl.vim\r\nelse\r\n  runtime! syntax\/libsdl.vim\r\nendif","first_name":"Andr\u00c3\u00a9","6":"Andr\u00c3\u00a9","last_name":"Wagner","7":"Wagner","releases":[{"0":"2125","vim_version":"6.0","1":"6.0","script_version":"1.1","2":"1.1","version_comment":"Fileformat changed to Unix.","3":"Fileformat changed to Unix.","package":"libsdl.vim","4":"libsdl.vim","src_id":"8159","5":"8159","creation_date":"1200554322","6":"1200554322"},{"0":"2125","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"libsdl.vim","4":"libsdl.vim","src_id":"8158","5":"8158","creation_date":"1200547001","6":"1200547001"}]},"2124":{"script_id":"2124","0":"2124","script_name":"Twitter","1":"Twitter","script_type":"utility","2":"utility","summary":"Post to Twitter from Vim","3":"Post to Twitter from Vim","description":"This is a very simple Vim Script that allows you to post to Twitter straight from Vim.\r\n\r\nUsage: Do the command :PosttoTwitter it will ask you for your Twitter in the command-line, type it in and hit enter to send it off. Or in a buffer; type the text you want to Twitter and in normal mode do :BPosttoTwitter to try and send the whole buffer, or :CPosttoTwitter to send the current line, or T to send the visualized text. \r\n\r\nFor anyone who wants to follow me: http:\/\/twitter.com\/travisjeffery\r\n\r\nGet the new and improved version by Po Shan Cheah at http:\/\/www.vim.org\/scripts\/script.php?script_id=2204 in the future.","4":"This is a very simple Vim Script that allows you to post to Twitter straight from Vim.\r\n\r\nUsage: Do the command :PosttoTwitter it will ask you for your Twitter in the command-line, type it in and hit enter to send it off. Or in a buffer; type the text you want to Twitter and in normal mode do :BPosttoTwitter to try and send the whole buffer, or :CPosttoTwitter to send the current line, or T to send the visualized text. \r\n\r\nFor anyone who wants to follow me: http:\/\/twitter.com\/travisjeffery\r\n\r\nGet the new and improved version by Po Shan Cheah at http:\/\/www.vim.org\/scripts\/script.php?script_id=2204 in the future.","install_details":"Install: move to someplace in your Vim Path (most likely: .vim\/plugin\/) and put in your .vimrc file: let vimtwitter_login=\"USER:PASS\"\r\n","5":"Install: move to someplace in your Vim Path (most likely: .vim\/plugin\/) and put in your .vimrc file: let vimtwitter_login=\"USER:PASS\"\r\n","first_name":"Travis","6":"Travis","last_name":"Jeffery","7":"Jeffery","releases":[{"0":"2124","vim_version":"7.0","1":"7.0","script_version":"5.0","2":"5.0","version_comment":"This will probably be my last version, it will be continued by Po Shan Cheah. This version does a lot under the hood: now you just define your login and password in your .vimrc file so that when you update the script you don't have to change it at all. The format in your .vimrc file should be \"let vimtwitter_login=\"USER:PASS\". All the commands are the same, now when you use the T command (tweet visualized text) it doesn't have to open a new tab. Added HTTP proxy support, URL-encoded the tweet so that special characters such as &, \", %, all work much better now. Thanks to Po Shan Cheah for the help, and to everyone who liked my script.","3":"This will probably be my last version, it will be continued by Po Shan Cheah. This version does a lot under the hood: now you just define your login and password in your .vimrc file so that when you update the script you don't have to change it at all. The format in your .vimrc file should be \"let vimtwitter_login=\"USER:PASS\". All the commands are the same, now when you use the T command (tweet visualized text) it doesn't have to open a new tab. Added HTTP proxy support, URL-encoded the tweet so that special characters such as &, \", %, all work much better now. Thanks to Po Shan Cheah for the help, and to everyone who liked my script.","package":"vimtwitter.vim","4":"vimtwitter.vim","src_id":"8502","5":"8502","creation_date":"1206713625","6":"1206713625"},{"0":"2124","vim_version":"7.0","1":"7.0","script_version":"4.1","2":"4.1","version_comment":"Fixed a bug with the T map.","3":"Fixed a bug with the T map.","package":"vimtwitter.vim","4":"vimtwitter.vim","src_id":"8496","5":"8496","creation_date":"1206541063","6":"1206541063"},{"0":"2124","vim_version":"7.0","1":"7.0","script_version":"4.0","2":"4.0","version_comment":"Changed the :PosttoTwitter command so that you now just type your Twitter in the command-line. So when you do :PosttoTwitter it will ask you for your twitter you type it in and send it off; which is better because there\\'s no need to start a new buffer. To Twitter the current buffer now do :BPosttoTwitter, and to Twitter the current line do the :CPosttoTwitter.","3":"Changed the :PosttoTwitter command so that you now just type your Twitter in the command-line. So when you do :PosttoTwitter it will ask you for your twitter you type it in and send it off; which is better because there\\'s no need to start a new buffer. To Twitter the current buffer now do :BPosttoTwitter, and to Twitter the current line do the :CPosttoTwitter.","package":"vimtwitter.vim","4":"vimtwitter.vim","src_id":"8418","5":"8418","creation_date":"1204895632","6":"1204895632"},{"0":"2124","vim_version":"7.0","1":"7.0","script_version":"3.0","2":"3.0","version_comment":"Now when you send a Twitter it nows says \"from Vim\" instead of the default \"from web.\"","3":"Now when you send a Twitter it nows says \"from Vim\" instead of the default \"from web.\"","package":"vimtwitter.vim","4":"vimtwitter.vim","src_id":"8381","5":"8381","creation_date":"1204458295","6":"1204458295"},{"0":"2124","vim_version":"7.0","1":"7.0","script_version":"2.0","2":"2.0","version_comment":"Added a few other things by request; now you can just send the current line with :CPosttoTwitter, and also I hacked together the ability to post visually selected text. To send visualized text; visual select the text and press T, thats a capital t. All the functionality to send visualized text is through a map that will yank the text, open a new tab, paste the text run the normal command :PosttoTwitter and then close the tab.","3":"Added a few other things by request; now you can just send the current line with :CPosttoTwitter, and also I hacked together the ability to post visually selected text. To send visualized text; visual select the text and press T, thats a capital t. All the functionality to send visualized text is through a map that will yank the text, open a new tab, paste the text run the normal command :PosttoTwitter and then close the tab.","package":"vimtwitter.vim","4":"vimtwitter.vim","src_id":"8346","5":"8346","creation_date":"1203890302","6":"1203890302"},{"0":"2124","vim_version":"7.0","1":"7.0","script_version":"1.61","2":"1.61","version_comment":"Fixed a grammar mistake.","3":"Fixed a grammar mistake.","package":"vimtweet.vim","4":"vimtweet.vim","src_id":"8324","5":"8324","creation_date":"1203618866","6":"1203618866"},{"0":"2124","vim_version":"7.0","1":"7.0","script_version":"1.6","2":"1.6","version_comment":"Now supports \"quotes.\"","3":"Now supports \"quotes.\"","package":"vimtwitter.vim","4":"vimtwitter.vim","src_id":"8323","5":"8323","creation_date":"1203615218","6":"1203615218"},{"0":"2124","vim_version":"7.0","1":"7.0","script_version":"1.5","2":"1.5","version_comment":"Fixed an error where the script wouldn't send Tweets that were exactly 140 characters.","3":"Fixed an error where the script wouldn't send Tweets that were exactly 140 characters.","package":"vimtweet.vim","4":"vimtweet.vim","src_id":"8305","5":"8305","creation_date":"1203370481","6":"1203370481"},{"0":"2124","vim_version":"7.0","1":"7.0","script_version":"1.4","2":"1.4","version_comment":"The script will now handle multiple lines.","3":"The script will now handle multiple lines.","package":"vimtwitter.vim","4":"vimtwitter.vim","src_id":"8304","5":"8304","creation_date":"1203366806","6":"1203366806"},{"0":"2124","vim_version":"7.0","1":"7.0","script_version":"1.3","2":"1.3","version_comment":"Now tells you how many characters you used on a successful Tweet.","3":"Now tells you how many characters you used on a successful Tweet.","package":"vimtwitter.vim","4":"vimtwitter.vim","src_id":"8302","5":"8302","creation_date":"1203339824","6":"1203339824"},{"0":"2124","vim_version":"7.0","1":"7.0","script_version":"1.2","2":"1.2","version_comment":"If you're over 140 characters it will tell you by how many and and not send anything.","3":"If you're over 140 characters it will tell you by how many and and not send anything.","package":"vimtwitter.vim","4":"vimtwitter.vim","src_id":"8301","5":"8301","creation_date":"1203331878","6":"1203331878"},{"0":"2124","vim_version":"7.0","1":"7.0","script_version":"1.1","2":"1.1","version_comment":"Simply made it so that \"Tweet successfully sent.\" is echoed.","3":"Simply made it so that \"Tweet successfully sent.\" is echoed.","package":"vimtwitter.vim","4":"vimtwitter.vim","src_id":"8295","5":"8295","creation_date":"1203300520","6":"1203300520"},{"0":"2124","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"vimtwitter.vim","4":"vimtwitter.vim","src_id":"8156","5":"8156","creation_date":"1200425836","6":"1200425836"}]},"2123":{"script_id":"2123","0":"2123","script_name":"basic colors","1":"basic colors","script_type":"color scheme","2":"color scheme","summary":"a simple color scheme that only highlights strings, comments, and errors","3":"a simple color scheme that only highlights strings, comments, and errors","description":"I got sick of color schemes that used every color and highlighted every possible item.\r\n\r\nThis basic color scheme gets rid of syntax highlighting for numbers, variables, and function names.  It keeps the colors for comments, strings, errors, and special information that's not actually in the document like line numbers.\r\n\r\nThis allows you to easily see if you've forgotten to terminate a string or comment, without being overwhelmed by the colors of everything else.","4":"I got sick of color schemes that used every color and highlighted every possible item.\r\n\r\nThis basic color scheme gets rid of syntax highlighting for numbers, variables, and function names.  It keeps the colors for comments, strings, errors, and special information that's not actually in the document like line numbers.\r\n\r\nThis allows you to easily see if you've forgotten to terminate a string or comment, without being overwhelmed by the colors of everything else.","install_details":"Copy to ~\/.vim\/colors or \/usr\/share\/vim\/vim71\/colors then type :color basic.","5":"Copy to ~\/.vim\/colors or \/usr\/share\/vim\/vim71\/colors then type :color basic.","first_name":"Mikel","6":"Mikel","last_name":"Ward","7":"Ward","releases":[{"0":"2123","vim_version":"7.0","1":"7.0","script_version":"2","2":"2","version_comment":"Uses original Vim default colors for dark backgrounds (e.g. comments = cyan, strings = magenta, etc.).\r\n\r\nThe colors for light backgrounds are unchanged (comments = blue, strings = green, etc.).","3":"Uses original Vim default colors for dark backgrounds (e.g. comments = cyan, strings = magenta, etc.).\r\n\r\nThe colors for light backgrounds are unchanged (comments = blue, strings = green, etc.).","package":"basic.vim","4":"basic.vim","src_id":"8155","5":"8155","creation_date":"1200424456","6":"1200424456"}]},"2122":{"script_id":"2122","0":"2122","script_name":"bg.py","1":"bg.py","script_type":"utility","2":"utility","summary":"Post to your blog at blogger.com from gVIM.","3":"Post to your blog at blogger.com from gVIM.","description":"Tested on windows only.\r\nRequirements:  \r\n 1. python \"http:\/\/python.org\" installed.\r\n 2. Google Data APIs -  \"http:\/\/code.google.com\/p\/gdata-python-client\/\"   gdata-python-client\r\n  can be downloaded from here : \"http:\/\/gdata-python-client.googlecode.com\/files\/gdata.py-1.0.10.latest.zip\"\r\n","4":"Tested on windows only.\r\nRequirements:  \r\n 1. python \"http:\/\/python.org\" installed.\r\n 2. Google Data APIs -  \"http:\/\/code.google.com\/p\/gdata-python-client\/\"   gdata-python-client\r\n  can be downloaded from here : \"http:\/\/gdata-python-client.googlecode.com\/files\/gdata.py-1.0.10.latest.zip\"\r\n","install_details":"Installation :\r\n 1.Install python \r\n 2.Download gdata-python-client  unpack and run \"setup.py install\" \r\n 3.download bg01.zip unpack bg.py and place in any folder mentioned in %PATH%  \r\n 4. add this line to your _vmrc file :\r\n\r\nnnoremap <Leader>blog :! bg.py --f %:p --u my@email.com  --p inline<cr>\r\n\r\n where my@email.com is your email registered on blogger.com  \r\n \r\n --p inline - means that password will be asked on every posting to blog , you can specify it in this line if you want.\r\n Than script will not be asking every time.\r\nnnoremap <Leader>blog :! bg.py --f %:p --u my@email.com  --p mypassword<cr>\r\n\r\nUsing:\r\n When you want to post current file to blog : just hit '\\blog' enter password and new blog entry will be created.\r\n I added post \r\nhttp:\/\/sourcefield.blogspot.com\/2008\/01\/how-to-blog-from-source-code-from-vim_09.html\r\n how to create  blog with syntax-highlighted source code. \r\n Please leave a word or question,concern,comment,jockes,bugs  http:\/\/sourcefield.blogspot.com\/2008\/01\/post-to-your-blog-at-bloggercom-from.html\r\n","5":"Installation :\r\n 1.Install python \r\n 2.Download gdata-python-client  unpack and run \"setup.py install\" \r\n 3.download bg01.zip unpack bg.py and place in any folder mentioned in %PATH%  \r\n 4. add this line to your _vmrc file :\r\n\r\nnnoremap <Leader>blog :! bg.py --f %:p --u my@email.com  --p inline<cr>\r\n\r\n where my@email.com is your email registered on blogger.com  \r\n \r\n --p inline - means that password will be asked on every posting to blog , you can specify it in this line if you want.\r\n Than script will not be asking every time.\r\nnnoremap <Leader>blog :! bg.py --f %:p --u my@email.com  --p mypassword<cr>\r\n\r\nUsing:\r\n When you want to post current file to blog : just hit '\\blog' enter password and new blog entry will be created.\r\n I added post \r\nhttp:\/\/sourcefield.blogspot.com\/2008\/01\/how-to-blog-from-source-code-from-vim_09.html\r\n how to create  blog with syntax-highlighted source code. \r\n Please leave a word or question,concern,comment,jockes,bugs  http:\/\/sourcefield.blogspot.com\/2008\/01\/post-to-your-blog-at-bloggercom-from.html\r\n","first_name":"sourcefield.blogspot.com","6":"sourcefield.blogspot.com","last_name":"sourcefield.blogspot.com","7":"sourcefield.blogspot.com","releases":[{"0":"2122","vim_version":"7.0","1":"7.0","script_version":"02","2":"02","version_comment":"Updated reading password by getpass.getpass() python function   \r\nThanks Albie ( http:\/\/epidermis2.blogspot.com\/ ) .","3":"Updated reading password by getpass.getpass() python function   \r\nThanks Albie ( http:\/\/epidermis2.blogspot.com\/ ) .","package":"bg02.zip","4":"bg02.zip","src_id":"8170","5":"8170","creation_date":"1200921459","6":"1200921459"},{"0":"2122","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"bg01.zip","4":"bg01.zip","src_id":"8150","5":"8150","creation_date":"1200221205","6":"1200221205"}]},"2121":{"script_id":"2121","0":"2121","script_name":"HeaderCVS","1":"HeaderCVS","script_type":"utility","2":"utility","summary":"Auto generate CVS Header before current cursor","3":"Auto generate CVS Header before current cursor","description":"\"\r\n\" This plugin adds CVS Header before current cursor.\r\n\"\r\n\" The CVS Header will automatically reflect current file name, current date and\r\n\" your description beside a standard CVS Header.\r\n\"\r\n\" (Note: This plugin is only tested on **Linux**.)\r\n\r\nFor example:\r\nIf you type \":HeaderCVS This is my file description.\" when editing file \"Demo.sh\",\r\nthis plugin will add the following CVS Header before current cursor.\r\n\r\n########################################################################\r\n#  Copyright MyCompany Inc.  All Rights reserved\r\n########################################################################\r\n#\r\n#  File                :  Demo.sh\r\n#  Creator           :  AyuanX ( ayuanx#163.com )\r\n#  Creation Date  :  2008-01-11\r\n#  Description      :  This is my file description.\r\n#\r\n########################################################################\r\n#    $Author$\r\n#    $Source$\r\n#    $Revision$\r\n#    $Date$\r\n#    $Id$\r\n########################################################################\r\n#    $Log$\r\n########################################################################\r\n\r\nTIP:\r\nCompany Name and Creator are customizable, File Name and Date are auto generated.\r\n\r\nWARNING:\r\nThis script is written with shell comment character '#' by default, you may need some workarounds manually to comment out the added header with other corresponding comment character.","4":"\"\r\n\" This plugin adds CVS Header before current cursor.\r\n\"\r\n\" The CVS Header will automatically reflect current file name, current date and\r\n\" your description beside a standard CVS Header.\r\n\"\r\n\" (Note: This plugin is only tested on **Linux**.)\r\n\r\nFor example:\r\nIf you type \":HeaderCVS This is my file description.\" when editing file \"Demo.sh\",\r\nthis plugin will add the following CVS Header before current cursor.\r\n\r\n########################################################################\r\n#  Copyright MyCompany Inc.  All Rights reserved\r\n########################################################################\r\n#\r\n#  File                :  Demo.sh\r\n#  Creator           :  AyuanX ( ayuanx#163.com )\r\n#  Creation Date  :  2008-01-11\r\n#  Description      :  This is my file description.\r\n#\r\n########################################################################\r\n#    $Author$\r\n#    $Source$\r\n#    $Revision$\r\n#    $Date$\r\n#    $Id$\r\n########################################################################\r\n#    $Log$\r\n########################################################################\r\n\r\nTIP:\r\nCompany Name and Creator are customizable, File Name and Date are auto generated.\r\n\r\nWARNING:\r\nThis script is written with shell comment character '#' by default, you may need some workarounds manually to comment out the added header with other corresponding comment character.","install_details":"\"\r\n\" 1. Please edit HeaderCVS.vim, customizing the following variables.\r\n\"          let s:company = \"MyCompany\"\r\n\"          let s:creator = \"AyuanX ( ayuanx#163.com )\"\r\n\"\r\n\" 2. Put HeaderCVS.vim into path \"~\/.vim\/plugin\/\".\r\n\"\r\n\" 3. Type \":HeaderCVS YOUR DESCRIPTION HERE\" to add CVS Header when editting files.\r\n\"    (NOTE: You can insert spaces into your description or omit description.)\r\n","5":"\"\r\n\" 1. Please edit HeaderCVS.vim, customizing the following variables.\r\n\"          let s:company = \"MyCompany\"\r\n\"          let s:creator = \"AyuanX ( ayuanx#163.com )\"\r\n\"\r\n\" 2. Put HeaderCVS.vim into path \"~\/.vim\/plugin\/\".\r\n\"\r\n\" 3. Type \":HeaderCVS YOUR DESCRIPTION HERE\" to add CVS Header when editting files.\r\n\"    (NOTE: You can insert spaces into your description or omit description.)\r\n","first_name":"AyuanX","6":"AyuanX","last_name":" ","7":" ","releases":[{"0":"2121","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial version","3":"Initial version","package":"HeaderCVS.vim","4":"HeaderCVS.vim","src_id":"8168","5":"8168","creation_date":"1200861882","6":"1200861882"}]},"2120":{"script_id":"2120","0":"2120","script_name":"speeddating.vim","1":"speeddating.vim","script_type":"utility","2":"utility","summary":"Use CTRL-A\/X to increment dates, times, and more","3":"Use CTRL-A\/X to increment dates, times, and more","description":"Take the following date:\r\n\r\n1999-12-31\r\n\r\nBecause Vim treats the hyphen as a negative sign, pressing CTRL-A on the 31 would normally increment it to\r\n\r\n1999-12-30\r\n\r\nCompare this with what happens when speeddating.vim is installed:\r\n\r\n2000-01-01\r\n\r\nPressing 5<C-X> on the 03 in the first line below transforms it into the second:\r\n\r\nSat, 01 Jan 2000 00:00:03 +0000\r\nFri, 31 Dec 1999 23:59:58 +0000\r\n\r\nSeveral date, time, and datetime formats are included.  Additional formats can be defined in a strftime-like syntax with the :SpeedDatingFormat command.\r\n\r\nExisting Vim semantics are preserved.  CTRL-A and CTRL-X accept a count, and plain number incrementing is used if no date format is matched.\r\n\r\nUse of CTRL-A\/X in visual mode enables incrementing several lines at once.  Blank spots are filled by incrementing the match from the previous line, allowing for creation of sequences (1, 2, 3; 2000-10-30, 2000-10-31, 2000-11-01).\r\n\r\nCan also increment roman numerals and ordinals (1st, 2nd, 3rd, ...).  In visual mode, letters of the alphabet are supported.\r\n\r\nd<C-A> sets the timestamp under the cursor to the current time.  d<C-X> does the same, but uses UTC rather than the local time.\r\n\r\nThe \".\" command will work as expected if you install repeat.vim, vimscript #2136.\r\n\r\nFeedback wanted: speeddating currently supports locale dependent day\/month names\/abbrevations, but also includes English abbreviation support.  However, most of the built-in formats just use the English version, because it is either mandated by a standard (like RFC 822) or because they are typically used in an international context (like the Last Change: header in Vim scripts).  Is it even worth supporting the locale dependent names at all?  Is anyone actively using them?\r\n\r\nhttp:\/\/github.com\/tpope\/vim-speeddating","4":"Take the following date:\r\n\r\n1999-12-31\r\n\r\nBecause Vim treats the hyphen as a negative sign, pressing CTRL-A on the 31 would normally increment it to\r\n\r\n1999-12-30\r\n\r\nCompare this with what happens when speeddating.vim is installed:\r\n\r\n2000-01-01\r\n\r\nPressing 5<C-X> on the 03 in the first line below transforms it into the second:\r\n\r\nSat, 01 Jan 2000 00:00:03 +0000\r\nFri, 31 Dec 1999 23:59:58 +0000\r\n\r\nSeveral date, time, and datetime formats are included.  Additional formats can be defined in a strftime-like syntax with the :SpeedDatingFormat command.\r\n\r\nExisting Vim semantics are preserved.  CTRL-A and CTRL-X accept a count, and plain number incrementing is used if no date format is matched.\r\n\r\nUse of CTRL-A\/X in visual mode enables incrementing several lines at once.  Blank spots are filled by incrementing the match from the previous line, allowing for creation of sequences (1, 2, 3; 2000-10-30, 2000-10-31, 2000-11-01).\r\n\r\nCan also increment roman numerals and ordinals (1st, 2nd, 3rd, ...).  In visual mode, letters of the alphabet are supported.\r\n\r\nd<C-A> sets the timestamp under the cursor to the current time.  d<C-X> does the same, but uses UTC rather than the local time.\r\n\r\nThe \".\" command will work as expected if you install repeat.vim, vimscript #2136.\r\n\r\nFeedback wanted: speeddating currently supports locale dependent day\/month names\/abbrevations, but also includes English abbreviation support.  However, most of the built-in formats just use the English version, because it is either mandated by a standard (like RFC 822) or because they are typically used in an international context (like the Last Change: header in Vim scripts).  Is it even worth supporting the locale dependent names at all?  Is anyone actively using them?\r\n\r\nhttp:\/\/github.com\/tpope\/vim-speeddating","install_details":"Extract in ~\/.vim (~\\vimfiles on Windows).","5":"Extract in ~\/.vim (~\\vimfiles on Windows).","first_name":"Tim","6":"Tim","last_name":"Pope","7":"Pope","releases":[{"0":"2120","vim_version":"7.0","1":"7.0","script_version":"20150124","2":"20150124","version_comment":"Convert to use autoload file.\r\nSupport milliseconds on %k.\r\nAdd default formats for date -Im.\r\nRespect nrformats without octal in visual mode.\r\nFix for selection=exclusive.\r\nFix current time retrieval on Windows.","3":"Convert to use autoload file.\r\nSupport milliseconds on %k.\r\nAdd default formats for date -Im.\r\nRespect nrformats without octal in visual mode.\r\nFix for selection=exclusive.\r\nFix current time retrieval on Windows.","package":"speeddating.zip","4":"speeddating.zip","src_id":"22824","5":"22824","creation_date":"1422128547","6":"1422128547"},{"0":"2120","vim_version":"7.0","1":"7.0","script_version":"20100301","2":"20100301","version_comment":"Fix hanging when incrementing a month across a year boundary.","3":"Fix hanging when incrementing a month across a year boundary.","package":"speeddating.zip","4":"speeddating.zip","src_id":"12533","5":"12533","creation_date":"1267482534","6":"1267482534"},{"0":"2120","vim_version":"7.0","1":"7.0","script_version":"20100219","2":"20100219","version_comment":"Real documentation file.\r\nCTRL-X on March 31 yields February 28 not March 3.","3":"Real documentation file.\r\nCTRL-X on March 31 yields February 28 not March 3.","package":"speeddating.zip","4":"speeddating.zip","src_id":"12438","5":"12438","creation_date":"1266616713","6":"1266616713"},{"0":"2120","vim_version":"7.0","1":"7.0","script_version":"20081016","2":"20081016","version_comment":"Fix false positives on patterns with periods","3":"Fix false positives on patterns with periods","package":"speeddating.vim","4":"speeddating.vim","src_id":"9356","5":"9356","creation_date":"1224127396","6":"1224127396"},{"0":"2120","vim_version":"7.0","1":"7.0","script_version":"20080314","2":"20080314","version_comment":"Basic timezone support.\r\nFormats like \"Fri Mar 14\" are smartly incremented, rather than assuming the year 2000.\r\nFixed error when wrapping down that would result in things like 23:60:60.","3":"Basic timezone support.\r\nFormats like \"Fri Mar 14\" are smartly incremented, rather than assuming the year 2000.\r\nFixed error when wrapping down that would result in things like 23:60:60.","package":"speeddating.vim","4":"speeddating.vim","src_id":"8454","5":"8454","creation_date":"1205491695","6":"1205491695"},{"0":"2120","vim_version":"7.0","1":"7.0","script_version":"20080129","2":"20080129","version_comment":"Integer treated as unix timestamp with maps for current time.\r\n%* at beginning\/end of pattern suppresses \\<\/\\>.\r\n%0x in a pattern is %x with mandatory leading zeros.\r\nThree new default formats.","3":"Integer treated as unix timestamp with maps for current time.\r\n%* at beginning\/end of pattern suppresses \\<\/\\>.\r\n%0x in a pattern is %x with mandatory leading zeros.\r\nThree new default formats.","package":"speeddating.vim","4":"speeddating.vim","src_id":"8197","5":"8197","creation_date":"1201615067","6":"1201615067"},{"0":"2120","vim_version":"7.0","1":"7.0","script_version":"20080120","2":"20080120","version_comment":"Removed days of week.  They may be added back if desired with :SpeedDatingFormat (%A is full name, %a is abbreviation).\r\nRoman numerals are now just a special year format.  They can be disabled with :SpeedDatingFormat! (%^v for uppercase, %v for lowercase).\r\nChanged default \"now\" mappings to d<C-A> and d<C-X>.\r\nBug fixes, mostly concerning visual mode.","3":"Removed days of week.  They may be added back if desired with :SpeedDatingFormat (%A is full name, %a is abbreviation).\r\nRoman numerals are now just a special year format.  They can be disabled with :SpeedDatingFormat! (%^v for uppercase, %v for lowercase).\r\nChanged default \"now\" mappings to d<C-A> and d<C-X>.\r\nBug fixes, mostly concerning visual mode.","package":"speeddating.vim","4":"speeddating.vim","src_id":"8166","5":"8166","creation_date":"1200844641","6":"1200844641"},{"0":"2120","vim_version":"7.0","1":"7.0","script_version":"20080111","2":"20080111","version_comment":"Initial upload","3":"Initial upload","package":"speeddating.vim","4":"speeddating.vim","src_id":"8146","5":"8146","creation_date":"1200050184","6":"1200050184"}]},"2119":{"script_id":"2119","0":"2119","script_name":"webpreview","1":"webpreview","script_type":"utility","2":"utility","summary":"make previewing pages  in web browsers easily","3":"make previewing pages  in web browsers easily","description":"support preview edit pages in outer web browser, included file types like php,html,jsp and so on.\r\nYou can just give a  browser, web server  in .vimrc like :\r\n\" let g:Default_WebBrowser='c:\\Program Files\\Maxthon2\\Maxthon.exe'\r\n\" let g:Second_WebBrowser=''\r\n\" let g:Default_WebDomain='http:\/\/weiye.cn'\r\n\" let g:Default_WebRoot='D:\/www' \r\n\r\nOr give a server list  and browser list like:\r\n\" let g:WebList = [\r\n\"            \\ {'domain' : 'http:\/\/ * .blog.weiye.cn','rootdir' : 'D:\/www\/blog\/ * '},\r\n\"            \\ {'domain' : 'http:\/\/blog.weiye.cn','rootdir' : 'D:\/www\/blog'},\r\n\"            \\ {'domain' : 'http:\/\/weiye.cn','rootdir' : 'D:\/www'},\r\n\"            \\ {'domain' : 'http:\/\/aa.bb.cn','rootdir' : 'ftp:\/\/user@192.168.202.110\/www\/xx'}\r\n\"            \\ ]\r\n\r\n\" let g:BrowserList = {\r\n\"            \\'default' : 'c:\\Program Files\\Maxthonsecond\\Maxthon.exe' ,\r\n\"            \\'second'  : 'c:\\Program Files\\Mozilla Firefox\\firefox.exe' ,\r\n\"            \\'ie'      : 'c:\\Program Files\\Internet Explorer\\iexplore.exe' ,\r\n\"            \\'ff'      : 'c:\\Program Files\\Mozilla Firefox\\firefox.exe' \r\n\"            \\}\r\n\r\nsupport wildcard * in server list.support remote ftp server.\r\nIn default, use \",bd\" to preview the current edited page in the default web browsers and \",bs\" in the second web \r\nserver.\r\nRead the webpreview.vim document for more details \r\n","4":"support preview edit pages in outer web browser, included file types like php,html,jsp and so on.\r\nYou can just give a  browser, web server  in .vimrc like :\r\n\" let g:Default_WebBrowser='c:\\Program Files\\Maxthon2\\Maxthon.exe'\r\n\" let g:Second_WebBrowser=''\r\n\" let g:Default_WebDomain='http:\/\/weiye.cn'\r\n\" let g:Default_WebRoot='D:\/www' \r\n\r\nOr give a server list  and browser list like:\r\n\" let g:WebList = [\r\n\"            \\ {'domain' : 'http:\/\/ * .blog.weiye.cn','rootdir' : 'D:\/www\/blog\/ * '},\r\n\"            \\ {'domain' : 'http:\/\/blog.weiye.cn','rootdir' : 'D:\/www\/blog'},\r\n\"            \\ {'domain' : 'http:\/\/weiye.cn','rootdir' : 'D:\/www'},\r\n\"            \\ {'domain' : 'http:\/\/aa.bb.cn','rootdir' : 'ftp:\/\/user@192.168.202.110\/www\/xx'}\r\n\"            \\ ]\r\n\r\n\" let g:BrowserList = {\r\n\"            \\'default' : 'c:\\Program Files\\Maxthonsecond\\Maxthon.exe' ,\r\n\"            \\'second'  : 'c:\\Program Files\\Mozilla Firefox\\firefox.exe' ,\r\n\"            \\'ie'      : 'c:\\Program Files\\Internet Explorer\\iexplore.exe' ,\r\n\"            \\'ff'      : 'c:\\Program Files\\Mozilla Firefox\\firefox.exe' \r\n\"            \\}\r\n\r\nsupport wildcard * in server list.support remote ftp server.\r\nIn default, use \",bd\" to preview the current edited page in the default web browsers and \",bs\" in the second web \r\nserver.\r\nRead the webpreview.vim document for more details \r\n","install_details":"put the webpreview.vim into $vim\/vimfiles\/plugin\/ (win32) or $vim\/.vim\/plugin\/(linux)","5":"put the webpreview.vim into $vim\/vimfiles\/plugin\/ (win32) or $vim\/.vim\/plugin\/(linux)","first_name":"weiye","6":"weiye","last_name":"zhou","7":"zhou","releases":[{"0":"2119","vim_version":"7.0","1":"7.0","script_version":"0.2","2":"0.2","version_comment":"Initial upload","3":"Initial upload","package":"webpreview.vim","4":"webpreview.vim","src_id":"8144","5":"8144","creation_date":"1200025816","6":"1200025816"}]},"2118":{"script_id":"2118","0":"2118","script_name":"gcov.vim","1":"gcov.vim","script_type":"syntax","2":"syntax","summary":"Highlighting for gcov files (gcc coverage)","3":"Highlighting for gcov files (gcc coverage)","description":"Syntax highlighting for runtime code coverage output generated by GCC\\'s coverage testing tool.\r\n\r\nSimply compile your code with: \r\n    -fprofile-arcs -ftest-coverage\r\n\r\nAnd run \r\n    gcov *.gcda\r\n\r\nOpen the resulting .gcov files to see which lines of code were executed how many times.","4":"Syntax highlighting for runtime code coverage output generated by GCC\\'s coverage testing tool.\r\n\r\nSimply compile your code with: \r\n    -fprofile-arcs -ftest-coverage\r\n\r\nAnd run \r\n    gcov *.gcda\r\n\r\nOpen the resulting .gcov files to see which lines of code were executed how many times.","install_details":"Put in your syntax directory","5":"Put in your syntax directory","first_name":"Saikat","6":"Saikat","last_name":"Guha","7":"Guha","releases":[{"0":"2118","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"gcov.vim","4":"gcov.vim","src_id":"8141","5":"8141","creation_date":"1199867039","6":"1199867039"}]},"2117":{"script_id":"2117","0":"2117","script_name":"GCov plugin","1":"GCov plugin","script_type":"utility","2":"utility","summary":"Simple plugin for easy access to .gcov files","3":"Simple plugin for easy access to .gcov files","description":"GCov is a profiler that comes with GCC. It is used to combine source code with profiling information and write the result into a gcov file. Switching between gcov and source file can easily become inefficient. This little plugin makes it easy to access current source line in the corresponding .gcov file. Just compile your application with -fprofile-aprc and -ftest-coverage, run it once to create the coverage files and press F11 in any source file to jump to the corresponding line in gcov file. ","4":"GCov is a profiler that comes with GCC. It is used to combine source code with profiling information and write the result into a gcov file. Switching between gcov and source file can easily become inefficient. This little plugin makes it easy to access current source line in the corresponding .gcov file. Just compile your application with -fprofile-aprc and -ftest-coverage, run it once to create the coverage files and press F11 in any source file to jump to the corresponding line in gcov file. ","install_details":"Copy this script into ~\/.vim\/plugins","5":"Copy this script into ~\/.vim\/plugins","first_name":"Martin","6":"Martin","last_name":"K. Schreder","7":"K. Schreder","releases":[{"0":"2117","vim_version":"6.0","1":"6.0","script_version":"0.01","2":"0.01","version_comment":"Initial upload","3":"Initial upload","package":"gcov.vim","4":"gcov.vim","src_id":"8134","5":"8134","creation_date":"1199716464","6":"1199716464"}]},"2116":{"script_id":"2116","0":"2116","script_name":"Io programming language syntax","1":"Io programming language syntax","script_type":"syntax","2":"syntax","summary":"Io language syntax support","3":"Io language syntax support","description":"vim syntax syntax for the Io programming language <http:\/\/www.iolanguage.com\/>\r\n\r\nCreator:  Scott Dunlop <swdunlop@verizon.net>\r\nFixes:-\r\n- Manpreet Singh <junkblocker@yahoo.com>\r\n- Jonathan Wright <quaggy@gmail.com>\r\n- Erik Garrison <erik.garrison@gmail.com>\r\n","4":"vim syntax syntax for the Io programming language <http:\/\/www.iolanguage.com\/>\r\n\r\nCreator:  Scott Dunlop <swdunlop@verizon.net>\r\nFixes:-\r\n- Manpreet Singh <junkblocker@yahoo.com>\r\n- Jonathan Wright <quaggy@gmail.com>\r\n- Erik Garrison <erik.garrison@gmail.com>\r\n","install_details":"","5":"","first_name":"Simon","6":"Simon","last_name":"Rozet","7":"Rozet","releases":[{"0":"2116","vim_version":"6.0","1":"6.0","script_version":"1","2":"1","version_comment":"Initial upload","3":"Initial upload","package":"io.vim","4":"io.vim","src_id":"8129","5":"8129","creation_date":"1199564204","6":"1199564204"}]},"2115":{"script_id":"2115","0":"2115","script_name":"Processing","1":"Processing","script_type":"syntax","2":"syntax","summary":"Syntax highlighting for the Processing language","3":"Syntax highlighting for the Processing language","description":"## Vim Processing\r\n\r\nOriginally authored by Szabolcs Horv\u00c3\u00a1t, and extended by Erich Heine and others (see below for a full list), this plugin exists to allow vim to replace the Processing IDE to develop sketches.\r\n\r\nPrimary development is now done by Erich Heine. The latest development version is found at https:\/\/github.com\/sophacles\/vim-processing\r\n\r\n### Features\r\n\r\n1. Syntax Highlighting for the Processing language: processing.vim will properly highlight sketches, based on the processing keywords.txt file. This includes processing functions and Java types and keywords as well.\r\n\r\n2. Documentation lookup -- pressing K in when over a keyword, type or function defined by processing will open a browser to the relevant documentation.(Currently this requires Python support compiled into Vim)\r\n\r\n3. Integrates with Vim's compiler support. Sketches can be run directly from Vim using the :make command. They are run via the processing-java command. This tool is used to run sketches outside of the Processing editor, and is supplied with Processing itself. Make sure processing-java is in your PATH before trying to run it from vim-processing.\r\n\r\n(MacOSX users will need to install the processing-java command from the Processing IDE before using this functionality)\r\n\r\n4. Folding can be enabled by defining \"processing_fold\"\r\n    let processing_fold = 1\r\n\r\nFor more usage information see :help processing-intro\r\n\r\n\r\n### Contributors\r\n\r\nThe full list of contributors to this project:\r\n\r\n*  Erich Heine (@sophacles on GitHub)\r\n*  Guy John (@rumblesan)\r\n*  Richard Gray (@vortura)\r\n*  Crazy Master (@crazymaster)\r\n*  V\u00c3\u00adtor Galv\u00c3\u00a3o (@vitorgalvao)\r\n*  Szabolcs Horv\u00c3\u00a1t (@szhorvat)\r\n\r\n### License\r\n\r\nCopyright (c) the contributors to the project. Distributed under the same terms as Vim itself.  See :help license\r\n","4":"## Vim Processing\r\n\r\nOriginally authored by Szabolcs Horv\u00c3\u00a1t, and extended by Erich Heine and others (see below for a full list), this plugin exists to allow vim to replace the Processing IDE to develop sketches.\r\n\r\nPrimary development is now done by Erich Heine. The latest development version is found at https:\/\/github.com\/sophacles\/vim-processing\r\n\r\n### Features\r\n\r\n1. Syntax Highlighting for the Processing language: processing.vim will properly highlight sketches, based on the processing keywords.txt file. This includes processing functions and Java types and keywords as well.\r\n\r\n2. Documentation lookup -- pressing K in when over a keyword, type or function defined by processing will open a browser to the relevant documentation.(Currently this requires Python support compiled into Vim)\r\n\r\n3. Integrates with Vim's compiler support. Sketches can be run directly from Vim using the :make command. They are run via the processing-java command. This tool is used to run sketches outside of the Processing editor, and is supplied with Processing itself. Make sure processing-java is in your PATH before trying to run it from vim-processing.\r\n\r\n(MacOSX users will need to install the processing-java command from the Processing IDE before using this functionality)\r\n\r\n4. Folding can be enabled by defining \"processing_fold\"\r\n    let processing_fold = 1\r\n\r\nFor more usage information see :help processing-intro\r\n\r\n\r\n### Contributors\r\n\r\nThe full list of contributors to this project:\r\n\r\n*  Erich Heine (@sophacles on GitHub)\r\n*  Guy John (@rumblesan)\r\n*  Richard Gray (@vortura)\r\n*  Crazy Master (@crazymaster)\r\n*  V\u00c3\u00adtor Galv\u00c3\u00a3o (@vitorgalvao)\r\n*  Szabolcs Horv\u00c3\u00a1t (@szhorvat)\r\n\r\n### License\r\n\r\nCopyright (c) the contributors to the project. Distributed under the same terms as Vim itself.  See :help license\r\n","install_details":"Use your favourite plugin manager, or download processing.zip from vimscripts and unzip it in ~\/.vim\/\r\n","5":"Use your favourite plugin manager, or download processing.zip from vimscripts and unzip it in ~\/.vim\/\r\n","first_name":"Szabolcs","6":"Szabolcs","last_name":"Horv\u00c3\u00a1t","7":"Horv\u00c3\u00a1t","releases":[{"0":"2115","vim_version":"7.0","1":"7.0","script_version":"1.0.0","2":"1.0.0","version_comment":"New, improved version by Erich Heine, for Processing 2.0\r\n\r\n* Updated syntax highlighting for Processing 2.0\r\n* Takes advantage of the processing-java command line tool from processing 2.0 in conjunction with :make in vim\r\n* Added a helpfile\r\n* Added utility scripts to update syntax files simply\r\n* Documentation finder supports python2 and python3","3":"New, improved version by Erich Heine, for Processing 2.0\r\n\r\n* Updated syntax highlighting for Processing 2.0\r\n* Takes advantage of the processing-java command line tool from processing 2.0 in conjunction with :make in vim\r\n* Added a helpfile\r\n* Added utility scripts to update syntax files simply\r\n* Documentation finder supports python2 and python3","package":"processing.zip","4":"processing.zip","src_id":"20901","5":"20901","creation_date":"1381268337","6":"1381268337"},{"0":"2115","vim_version":"6.0","1":"6.0","script_version":"3","2":"3","version_comment":"Fixed unmatched bracket highlighting and other minor fixes.","3":"Fixed unmatched bracket highlighting and other minor fixes.","package":"processing.zip","4":"processing.zip","src_id":"8220","5":"8220","creation_date":"1202005548","6":"1202005548"},{"0":"2115","vim_version":"6.0","1":"6.0","script_version":"2","2":"2","version_comment":"Added highlighting for unmatched brackets and an ftplugin for integration with the documentation.","3":"Added highlighting for unmatched brackets and an ftplugin for integration with the documentation.","package":"processing.zip","4":"processing.zip","src_id":"8184","5":"8184","creation_date":"1201358793","6":"1201358793"},{"0":"2115","vim_version":"6.0","1":"6.0","script_version":"1","2":"1","version_comment":"Initial upload","3":"Initial upload","package":"processing.vim","4":"processing.vim","src_id":"8123","5":"8123","creation_date":"1199456631","6":"1199456631"}]},"2114":{"script_id":"2114","0":"2114","script_name":"Torquescript syntax highlighting","1":"Torquescript syntax highlighting","script_type":"syntax","2":"syntax","summary":"Syntax highlighting for scripting in the Torque game engines","3":"Syntax highlighting for scripting in the Torque game engines","description":"This script allows for full syntax highlighting of TorqueScript, the scripting language for the family of Torque Game Engines.","4":"This script allows for full syntax highlighting of TorqueScript, the scripting language for the family of Torque Game Engines.","install_details":"Place the torque.vim into your vim runtime directory in the syntax subdirectory. The filetype.vim needs to be copied\/merged into the vim runtime directory as well. \r\nfiletype.vim performs automatic loading of Torquescript syntax for files with the correct script extensions. \r\nSee the Readme.txt for any additional details. ","5":"Place the torque.vim into your vim runtime directory in the syntax subdirectory. The filetype.vim needs to be copied\/merged into the vim runtime directory as well. \r\nfiletype.vim performs automatic loading of Torquescript syntax for files with the correct script extensions. \r\nSee the Readme.txt for any additional details. ","first_name":"Eric","6":"Eric","last_name":"Roberts","7":"Roberts","releases":[{"0":"2114","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"VimTorqueSyntax.zip","4":"VimTorqueSyntax.zip","src_id":"8115","5":"8115","creation_date":"1199274872","6":"1199274872"}]},"2113":{"script_id":"2113","0":"2113","script_name":"pspad colors scheme","1":"pspad colors scheme","script_type":"color scheme","2":"color scheme","summary":"soft blue colors, similar to \\'rajat\\' scheme in pspad","3":"soft blue colors, similar to \\'rajat\\' scheme in pspad","description":"Examples:\r\nhttp:\/\/academicproductivity.com\/software\/ISense.ahk.html\r\nhttp:\/\/academicproductivity.com\/softwareactivegoto.ahk.html\r\n\r\n","4":"Examples:\r\nhttp:\/\/academicproductivity.com\/software\/ISense.ahk.html\r\nhttp:\/\/academicproductivity.com\/softwareactivegoto.ahk.html\r\n\r\n","install_details":"drop into \/vimfiles\/colors\/\r\n\r\ndo a :colo pspad to apply it.","5":"drop into \/vimfiles\/colors\/\r\n\r\ndo a :colo pspad to apply it.","first_name":"Jose","6":"Jose","last_name":"Quesada","7":"Quesada","releases":[{"0":"2113","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"pspad.vim","4":"pspad.vim","src_id":"8114","5":"8114","creation_date":"1199266423","6":"1199266423"}]},"2112":{"script_id":"2112","0":"2112","script_name":"autohotkey (ahk)","1":"autohotkey (ahk)","script_type":"syntax","2":"syntax","summary":"autohotkey syntax highlighting","3":"autohotkey syntax highlighting","description":"autohotkey (ahk) syntax file.\r\nBest in combination with color scheme pspad.\r\n\r\nExamples:\r\nIsense script\r\nhttp:\/\/academicproductivity.com\/software\/ISense.ahk.html\r\n\r\nactiveGoto script\r\nhttp:\/\/academicproductivity.com\/software\/activegoto.ahk.html\r\n\r\nIn a Nutshell:\r\nBuilt-in finctions are blue\r\nUser defined functions are green\r\nAutohotkey variables are orange\r\nLabels are red (return too; makes it easy to find subs scopes)\r\nGUI commands, others, are brown\r\n","4":"autohotkey (ahk) syntax file.\r\nBest in combination with color scheme pspad.\r\n\r\nExamples:\r\nIsense script\r\nhttp:\/\/academicproductivity.com\/software\/ISense.ahk.html\r\n\r\nactiveGoto script\r\nhttp:\/\/academicproductivity.com\/software\/activegoto.ahk.html\r\n\r\nIn a Nutshell:\r\nBuilt-in finctions are blue\r\nUser defined functions are green\r\nAutohotkey variables are orange\r\nLabels are red (return too; makes it easy to find subs scopes)\r\nGUI commands, others, are brown\r\n","install_details":"drop into \/vimfiles\/syntax.\r\n\r\nMake sure the extension ahk is mapped to this syntax file. To do that, go to \/vimYourVersionNb\/filetype.vim and add:\r\n\r\n\" Autohotkey\r\nau BufNewFile,BufRead *.ahk\t\t\tsetf autohotkey\r\n","5":"drop into \/vimfiles\/syntax.\r\n\r\nMake sure the extension ahk is mapped to this syntax file. To do that, go to \/vimYourVersionNb\/filetype.vim and add:\r\n\r\n\" Autohotkey\r\nau BufNewFile,BufRead *.ahk\t\t\tsetf autohotkey\r\n","first_name":"Jose","6":"Jose","last_name":"Quesada","7":"Quesada","releases":[{"0":"2112","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"autohotkey.vim","4":"autohotkey.vim","src_id":"8113","5":"8113","creation_date":"1199266057","6":"1199266057"}]},"2111":{"script_id":"2111","0":"2111","script_name":"robocom","1":"robocom","script_type":"syntax","2":"syntax","summary":"Hiliting for Robocom scripts.","3":"Hiliting for Robocom scripts.","description":"See http:\/\/www.cyty.com\/robocom\/ for details on Robocom game.","4":"See http:\/\/www.cyty.com\/robocom\/ for details on Robocom game.","install_details":"Place it under ~\/.vim\/syntax.","5":"Place it under ~\/.vim\/syntax.","first_name":"Roman","6":"Roman","last_name":"Cheplyaka","7":"Cheplyaka","releases":[{"0":"2111","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Added version check.","3":"Added version check.","package":"robocom.vim","4":"robocom.vim","src_id":"8100","5":"8100","creation_date":"1198893493","6":"1198893493"},{"0":"2111","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"robocom.vim","4":"robocom.vim","src_id":"8099","5":"8099","creation_date":"1198892739","6":"1198892739"}]},"2110":{"script_id":"2110","0":"2110","script_name":"chords","1":"chords","script_type":"ftplugin","2":"ftplugin","summary":"(Guitar) chords and tabs","3":"(Guitar) chords and tabs","description":"Allows to hilite chords and tabs stored in text files.\r\nScreenshot: http:\/\/ro-che.info\/docs\/img\/chords.png","4":"Allows to hilite chords and tabs stored in text files.\r\nScreenshot: http:\/\/ro-che.info\/docs\/img\/chords.png","install_details":"Place it under ~\/.vim\/syntax and use :set syntax=chords or some autocommand.","5":"Place it under ~\/.vim\/syntax and use :set syntax=chords or some autocommand.","first_name":"Roman","6":"Roman","last_name":"Cheplyaka","7":"Cheplyaka","releases":[{"0":"2110","vim_version":"6.0","1":"6.0","script_version":"1.1","2":"1.1","version_comment":"Improved tabs hiliting.","3":"Improved tabs hiliting.","package":"chords.vim","4":"chords.vim","src_id":"8104","5":"8104","creation_date":"1198989434","6":"1198989434"},{"0":"2110","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"chords.vim","4":"chords.vim","src_id":"8098","5":"8098","creation_date":"1198891754","6":"1198891754"}]},"2109":{"script_id":"2109","0":"2109","script_name":"BBCode","1":"BBCode","script_type":"syntax","2":"syntax","summary":"Syntax highlighting for BBCode","3":"Syntax highlighting for BBCode","description":"This script adds syntax highlighting for BBCode, which is an abbreviation for Bulletin Board Code, the markup language used to format posts in many message boards. At the moment it highlights all tags and links defined by the URL-tag, but also the text between B-tags, I-tags, and U-tags (nesting is allowed), too.\r\n\r\nTODO: I intended to highlight the text between QUOTE-Tags, too, but found no solution yet which worked for nested quotes.\r\n","4":"This script adds syntax highlighting for BBCode, which is an abbreviation for Bulletin Board Code, the markup language used to format posts in many message boards. At the moment it highlights all tags and links defined by the URL-tag, but also the text between B-tags, I-tags, and U-tags (nesting is allowed), too.\r\n\r\nTODO: I intended to highlight the text between QUOTE-Tags, too, but found no solution yet which worked for nested quotes.\r\n","install_details":"Just put it in \"~\/.vim\/syntax\" or in \"<your vim directory>\\vimfiles\\syntax\" on Windows. If you do \":set filetype=bbcode\", the syntax definition will be loaded automativcally.\r\n","5":"Just put it in \"~\/.vim\/syntax\" or in \"<your vim directory>\\vimfiles\\syntax\" on Windows. If you do \":set filetype=bbcode\", the syntax definition will be loaded automativcally.\r\n","first_name":"Georg","6":"Georg","last_name":"Dahn","7":"Dahn","releases":[{"0":"2109","vim_version":"6.0","1":"6.0","script_version":"0.9.2","2":"0.9.2","version_comment":"Minor update: the enclosing quotes of a string may also be a ' ","3":"Minor update: the enclosing quotes of a string may also be a ' ","package":"bbcode.vim","4":"bbcode.vim","src_id":"8108","5":"8108","creation_date":"1199195217","6":"1199195217"}]},"2108":{"script_id":"2108","0":"2108","script_name":"csv reader","1":"csv reader","script_type":"utility","2":"utility","summary":"Read csv file (comma or tab, choosable), easy to move to every column in color.","3":"Read csv file (comma or tab, choosable), easy to move to every column in color.","description":"When you open a .csv file, you can read it more easy, this script make the current column\r\nhighlighting, and you can jump to the field that you want or select the comma or tab as the split symbol.\r\n[ Some code come from network, and I like to share this with you. Thanks, every body. ]\r\n\r\nF9: move to ahead column\r\nF10: move to next column\r\nF11:jump to field\r\nF12: select the split symbol, you can directly push the enter as input comma, or type comma or tab.","4":"When you open a .csv file, you can read it more easy, this script make the current column\r\nhighlighting, and you can jump to the field that you want or select the comma or tab as the split symbol.\r\n[ Some code come from network, and I like to share this with you. Thanks, every body. ]\r\n\r\nF9: move to ahead column\r\nF10: move to next column\r\nF11:jump to field\r\nF12: select the split symbol, you can directly push the enter as input comma, or type comma or tab.","install_details":"step1;  put the readcsv.vim into your plugin folder.\r\n\r\nstep2;  add below line into your .vimrc\r\n\r\nautocmd BufNewFile,Bufread *.csv call CSVSELECT()\r\nmap <F9> :call CSV_HighlightPrevCol()<CR> \r\nmap <F10> :call CSV_HighlightNextCol()<CR> \r\nmap <F11> :call CSV_goto_field()<CR>\r\nmap <F12> :call CSV_SE()<CR>\r\n\r\nstep3; Now ',' is default. If you use comma as default, you need not do this.\r\n\r\nthere is a way to set it use 'tab' by default. \r\nopen  readcsv.vim\r\nfind almost last line,  change the line \r\n\r\ncall CSVSettings()\r\nto be\r\ncall CSVTabs()  ","5":"step1;  put the readcsv.vim into your plugin folder.\r\n\r\nstep2;  add below line into your .vimrc\r\n\r\nautocmd BufNewFile,Bufread *.csv call CSVSELECT()\r\nmap <F9> :call CSV_HighlightPrevCol()<CR> \r\nmap <F10> :call CSV_HighlightNextCol()<CR> \r\nmap <F11> :call CSV_goto_field()<CR>\r\nmap <F12> :call CSV_SE()<CR>\r\n\r\nstep3; Now ',' is default. If you use comma as default, you need not do this.\r\n\r\nthere is a way to set it use 'tab' by default. \r\nopen  readcsv.vim\r\nfind almost last line,  change the line \r\n\r\ncall CSVSettings()\r\nto be\r\ncall CSVTabs()  ","first_name":"Hongli","6":"Hongli","last_name":"Gao","7":"Gao","releases":[{"0":"2108","vim_version":"7.0","1":"7.0","script_version":"6.0","2":"6.0","version_comment":"Initial upload","3":"Initial upload","package":"readcsv.zip","4":"readcsv.zip","src_id":"8085","5":"8085","creation_date":"1198609355","6":"1198609355"}]},"2107":{"script_id":"2107","0":"2107","script_name":"scratch","1":"scratch","script_type":"utility","2":"utility","summary":"Emacs like scratch buffer","3":"Emacs like scratch buffer","description":"*scratch* is a Vim plugin to provide Emacs-like scratch buffer.  You can write\r\nanything in it, and you can also evaluate a part of the buffer as Vim script.\r\nIt is a temporary buffer and it is not related to a real file, so the content\r\nof the buffer will be discarded when you quit Vim.  This buffer is useful when\r\nyou test a bit of script or other use.\r\n\r\n\r\nRequirements:\r\n- Vim 7.0 or later\r\n\r\nLatest version:\r\nhttp:\/\/github.com\/kana\/vim-scratch\r\n\r\nDocument in HTML format:\r\nhttp:\/\/kana.github.com\/config\/vim\/scratch.html","4":"*scratch* is a Vim plugin to provide Emacs-like scratch buffer.  You can write\r\nanything in it, and you can also evaluate a part of the buffer as Vim script.\r\nIt is a temporary buffer and it is not related to a real file, so the content\r\nof the buffer will be discarded when you quit Vim.  This buffer is useful when\r\nyou test a bit of script or other use.\r\n\r\n\r\nRequirements:\r\n- Vim 7.0 or later\r\n\r\nLatest version:\r\nhttp:\/\/github.com\/kana\/vim-scratch\r\n\r\nDocument in HTML format:\r\nhttp:\/\/kana.github.com\/config\/vim\/scratch.html","install_details":"...","5":"...","first_name":"Kana","6":"Kana","last_name":"Natsuno","7":"Natsuno","releases":[{"0":"2107","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"vim-scratch-0.1.zip","4":"vim-scratch-0.1.zip","src_id":"8084","5":"8084","creation_date":"1198577289","6":"1198577289"}]},"2106":{"script_id":"2106","0":"2106","script_name":"hiveminder.vim","1":"hiveminder.vim","script_type":"syntax","2":"syntax","summary":"Syntax for Hiveminder exported tasks (tasks.txt) files","3":"Syntax for Hiveminder exported tasks (tasks.txt) files","description":"Provides filetype='hiveminder' for use with text file export from Hiveminder (http:\/\/hiveminder.com\/)\r\n\r\ntasks.txt is a formatted todo list which can be edited in place and sent back to Hiveminder to propagate changes.\r\n\r\nThe file can be generated by clicking on the text file export link on your Hiveminder page, or by using their todo.pl script with the download option.  Nothing is provided to detect these files if an alternate filename is selected.\r\n\r\nThe syntax will also work with the 'braindump' format temporary files generated when you run todo.pl with the 'braindump' option.  There's no easy way to detect these, but I've hacked my todo.pl to inform vim.  See doc\/hiveminder.txt for more information.","4":"Provides filetype='hiveminder' for use with text file export from Hiveminder (http:\/\/hiveminder.com\/)\r\n\r\ntasks.txt is a formatted todo list which can be edited in place and sent back to Hiveminder to propagate changes.\r\n\r\nThe file can be generated by clicking on the text file export link on your Hiveminder page, or by using their todo.pl script with the download option.  Nothing is provided to detect these files if an alternate filename is selected.\r\n\r\nThe syntax will also work with the 'braindump' format temporary files generated when you run todo.pl with the 'braindump' option.  There's no easy way to detect these, but I've hacked my todo.pl to inform vim.  See doc\/hiveminder.txt for more information.","install_details":"Unpack the tarball into ~\/.vim\r\n\r\nIf you want braindumps to automatically have filetype=hiveminder, you'll need to hack todo.pl  A suggested patch for this is in the provided doc\/hiveminder.txt","5":"Unpack the tarball into ~\/.vim\r\n\r\nIf you want braindumps to automatically have filetype=hiveminder, you'll need to hack todo.pl  A suggested patch for this is in the provided doc\/hiveminder.txt","first_name":"Marc","6":"Marc","last_name":"Hartstein","7":"Hartstein","releases":[{"0":"2106","vim_version":"5.7","1":"5.7","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"hiveminder.tar.gz","4":"hiveminder.tar.gz","src_id":"8080","5":"8080","creation_date":"1198328193","6":"1198328193"}]},"2105":{"script_id":"2105","0":"2105","script_name":"oberon2","1":"oberon2","script_type":"utility","2":"utility","summary":"Syntax file for Oberon-2.","3":"Syntax file for Oberon-2.","description":"Syntax file for Oberon-2.\r\nIt was derived from syntax file for Modula-2 by Peter Funk.\r\nThe main idea was to let type Oberon-2 keywords in lower case, using abbr to capitalize them.","4":"Syntax file for Oberon-2.\r\nIt was derived from syntax file for Modula-2 by Peter Funk.\r\nThe main idea was to let type Oberon-2 keywords in lower case, using abbr to capitalize them.","install_details":"Simply copy oberon2.vim into syntax directory.\r\nAfter that you may change filetype.vim to associate Oberon-2 syntax file with extension that is used by your compiler.\r\nFor example, I use XDS Oberon-2 compiler, my source files have extension *.ob2","5":"Simply copy oberon2.vim into syntax directory.\r\nAfter that you may change filetype.vim to associate Oberon-2 syntax file with extension that is used by your compiler.\r\nFor example, I use XDS Oberon-2 compiler, my source files have extension *.ob2","first_name":"Alexey","6":"Alexey","last_name":"Cheremkhin","7":"Cheremkhin","releases":[{"0":"2105","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"oberon2.vim","4":"oberon2.vim","src_id":"8074","5":"8074","creation_date":"1198065478","6":"1198065478"}]},"2104":{"script_id":"2104","0":"2104","script_name":"R.vim","1":"R.vim","script_type":"ftplugin","2":"ftplugin","summary":"Execute R-code from vim on Mac OS X","3":"Execute R-code from vim on Mac OS X","description":"This script is a related to vimscript#1048. However, it only works only on Mac OS X and does not require funnel.pl (vimscript#221) or any other code. It uses AppleScript embedded in the R.vim file to send selected lines of code to an R buffer (press <F3>). It is also possible to have all code in a buffer run using R to get the output back as an output buffer in vim (press <F4> or <F5>). In addition you can comment in\/out lines of code with 'mc'.","4":"This script is a related to vimscript#1048. However, it only works only on Mac OS X and does not require funnel.pl (vimscript#221) or any other code. It uses AppleScript embedded in the R.vim file to send selected lines of code to an R buffer (press <F3>). It is also possible to have all code in a buffer run using R to get the output back as an output buffer in vim (press <F4> or <F5>). In addition you can comment in\/out lines of code with 'mc'.","install_details":"I put the R.vim script in my .vim\/after\/syntax directory.","5":"I put the R.vim script in my .vim\/after\/syntax directory.","first_name":"Vincent","6":"Vincent","last_name":"Nijs","7":"Nijs","releases":[{"0":"2104","vim_version":"7.0","1":"7.0","script_version":"0.01","2":"0.01","version_comment":"Initial upload","3":"Initial upload","package":"R.vim","4":"R.vim","src_id":"8069","5":"8069","creation_date":"1197992195","6":"1197992195"}]},"2103":{"script_id":"2103","0":"2103","script_name":"kwbdi.vim","1":"kwbdi.vim","script_type":"utility","2":"utility","summary":"Keep Window on Buffer Delete - Improved","3":"Keep Window on Buffer Delete - Improved","description":"This is an improved version of kwbd.vim. It allows you to delete a buffer without closing the window. It meets the following criteria:\r\n\r\n\r\n    * The window layout must be kept in all circumstances.\r\n    * If there is an alternate buffer must be showing that.\r\n    * If there is not alternate buffer then must be showing the preious buffer.\r\n    * If there is no alternate nor previous buffer (it is the only buffer) must show an empty buffer. \r\n\r\nIf there are two windows with the same buffer open, both windows will remain open, and the buffer will be deleted\r\n\r\nTo delete a buffer while keeping the window open, just type \\bd\r\n\r\nThanks to the authors of kwbd.vim and minibufexpl.vim!","4":"This is an improved version of kwbd.vim. It allows you to delete a buffer without closing the window. It meets the following criteria:\r\n\r\n\r\n    * The window layout must be kept in all circumstances.\r\n    * If there is an alternate buffer must be showing that.\r\n    * If there is not alternate buffer then must be showing the preious buffer.\r\n    * If there is no alternate nor previous buffer (it is the only buffer) must show an empty buffer. \r\n\r\nIf there are two windows with the same buffer open, both windows will remain open, and the buffer will be deleted\r\n\r\nTo delete a buffer while keeping the window open, just type \\bd\r\n\r\nThanks to the authors of kwbd.vim and minibufexpl.vim!","install_details":"Copy the script into ~\/.vim\/plugin","5":"Copy the script into ~\/.vim\/plugin","first_name":"Ben","6":"Ben","last_name":"Booth","7":"Booth","releases":[{"0":"2103","vim_version":"6.0","1":"6.0","script_version":"1.1","2":"1.1","version_comment":"fixed some bugs","3":"fixed some bugs","package":"kwbdi.vim","4":"kwbdi.vim","src_id":"8068","5":"8068","creation_date":"1197988542","6":"1197988542"},{"0":"2103","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"kwbdi.vim","4":"kwbdi.vim","src_id":"8067","5":"8067","creation_date":"1197980123","6":"1197980123"}]},"2102":{"script_id":"2102","0":"2102","script_name":"EnvEdit.vim","1":"EnvEdit.vim","script_type":"utility","2":"utility","summary":"Intelligently edit environment variable values","3":"Intelligently edit environment variable values","description":"Please send comments, suggestions, flames, etc. to NewOfalSor at gPmaAilM dot com, minus NOSPAM\r\n\r\nChanging environment variables in Windows' \"Environment\r\nVariables\" dialog is just WAY too tedious.  This plugin\r\nprovides the following benefits: \r\n    1. Vim's editing keystrokes.\r\n    2. You can resize the window so that the entire value\r\n       fits on the screen.\r\n    3. You can easily use the value of a different variable\r\n       in the definition of another.\r\n    4. Vim shows up in the taskbar, so you don't have to\r\n       minimize all of your other windows to find the\r\n       misplaced \"Environment Variables\" dialog after looking\r\n       up the correct value for a variable in the\r\n       documentation.\r\n    5. Command-line completion is an easier way to locate\r\n       a variable than hunting for it in two different\r\n       five-line high lists.\r\n\r\nAt the command-line type this command: :EnvEdit {VARIABLE}\r\nThis will open a new buffer named $VARIABLE and containing the\r\nvalue of that environment variable.  If there exists no such\r\nenvironment variable, you'll be greeted with an empty buffer.\r\n\r\nWhen the buffer is saved, the new text is stored in the\r\ndefault register \"\", exported to the clipboard via the \"+ and \"*\r\nregisters, and exported to Vim's own environment.  This means\r\nthat any child processes of that instance of Vim inherit the\r\nnew environment variable.\r\n\r\nIf the environment variable contains your system's path\r\nseparator character (':' on UNIX and ';' on Windows), the\r\nvariable's text is split on this character and each component\r\nis presented on its own line.  When you save the buffer, all\r\nlines are joined and delimited by this same character.  Empty\r\nlines are filtered out to prevent consecutive path separators\r\nfrom appearing.\r\n","4":"Please send comments, suggestions, flames, etc. to NewOfalSor at gPmaAilM dot com, minus NOSPAM\r\n\r\nChanging environment variables in Windows' \"Environment\r\nVariables\" dialog is just WAY too tedious.  This plugin\r\nprovides the following benefits: \r\n    1. Vim's editing keystrokes.\r\n    2. You can resize the window so that the entire value\r\n       fits on the screen.\r\n    3. You can easily use the value of a different variable\r\n       in the definition of another.\r\n    4. Vim shows up in the taskbar, so you don't have to\r\n       minimize all of your other windows to find the\r\n       misplaced \"Environment Variables\" dialog after looking\r\n       up the correct value for a variable in the\r\n       documentation.\r\n    5. Command-line completion is an easier way to locate\r\n       a variable than hunting for it in two different\r\n       five-line high lists.\r\n\r\nAt the command-line type this command: :EnvEdit {VARIABLE}\r\nThis will open a new buffer named $VARIABLE and containing the\r\nvalue of that environment variable.  If there exists no such\r\nenvironment variable, you'll be greeted with an empty buffer.\r\n\r\nWhen the buffer is saved, the new text is stored in the\r\ndefault register \"\", exported to the clipboard via the \"+ and \"*\r\nregisters, and exported to Vim's own environment.  This means\r\nthat any child processes of that instance of Vim inherit the\r\nnew environment variable.\r\n\r\nIf the environment variable contains your system's path\r\nseparator character (':' on UNIX and ';' on Windows), the\r\nvariable's text is split on this character and each component\r\nis presented on its own line.  When you save the buffer, all\r\nlines are joined and delimited by this same character.  Empty\r\nlines are filtered out to prevent consecutive path separators\r\nfrom appearing.\r\n","install_details":"Copy into your .vim\/plugins directory","5":"Copy into your .vim\/plugins directory","first_name":"erik","6":"erik","last_name":"falor","7":"falor","releases":[{"0":"2102","vim_version":"7.0","1":"7.0","script_version":"0.3","2":"0.3","version_comment":"Substitute %SystemRoot% in the expansion of %PATH% on Windows","3":"Substitute %SystemRoot% in the expansion of %PATH% on Windows","package":"EnvEdit.vim","4":"EnvEdit.vim","src_id":"22762","5":"22762","creation_date":"1420644688","6":"1420644688"},{"0":"2102","vim_version":"7.0","1":"7.0","script_version":"0.2","2":"0.2","version_comment":"Stores value of variable into the \"* register, aka the selection buffer.  This is the text that is put down when you press the middle mouse button.  Sorry Windows users, this is just another reason why Vista isn't ready for the desktop yet.","3":"Stores value of variable into the \"* register, aka the selection buffer.  This is the text that is put down when you press the middle mouse button.  Sorry Windows users, this is just another reason why Vista isn't ready for the desktop yet.","package":"EnvEdit.vim","4":"EnvEdit.vim","src_id":"8135","5":"8135","creation_date":"1199718512","6":"1199718512"},{"0":"2102","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"EnvEdit.vim","4":"EnvEdit.vim","src_id":"8063","5":"8063","creation_date":"1197902640","6":"1197902640"}]},"2101":{"script_id":"2101","0":"2101","script_name":"textobj-datetime","1":"textobj-datetime","script_type":"utility","2":"utility","summary":"Text objects for date and time","3":"Text objects for date and time","description":"*textobj-datetime* is a Vim plugin to provide text objects for date and time.\r\n\r\n\r\nRequirements:\r\n- Vim 7.0 or later\r\n- |textobj-user| 0.3.3 or later (vimscript#2100)\r\n\r\nLatest version:\r\nhttp:\/\/github.com\/kana\/vim-textobj-datetime\r\n\r\nDocument in HTML format:\r\nhttp:\/\/kana.github.com\/config\/vim\/textobj-datetime.html","4":"*textobj-datetime* is a Vim plugin to provide text objects for date and time.\r\n\r\n\r\nRequirements:\r\n- Vim 7.0 or later\r\n- |textobj-user| 0.3.3 or later (vimscript#2100)\r\n\r\nLatest version:\r\nhttp:\/\/github.com\/kana\/vim-textobj-datetime\r\n\r\nDocument in HTML format:\r\nhttp:\/\/kana.github.com\/config\/vim\/textobj-datetime.html","install_details":"...","5":"...","first_name":"Kana","6":"Kana","last_name":"Natsuno","7":"Natsuno","releases":[{"0":"2101","vim_version":"7.0","1":"7.0","script_version":"0.3.1","2":"0.3.1","version_comment":"Update to use textobj-user 0.3.3 or later.","3":"Update to use textobj-user 0.3.3 or later.","package":"vim-textobj-datetime-0.3.1.zip","4":"vim-textobj-datetime-0.3.1.zip","src_id":"8857","5":"8857","creation_date":"1214459455","6":"1214459455"},{"0":"2101","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"vim-textobj-datetime-0.1.zip","4":"vim-textobj-datetime-0.1.zip","src_id":"8059","5":"8059","creation_date":"1197719559","6":"1197719559"}]},"2100":{"script_id":"2100","0":"2100","script_name":"textobj-user","1":"textobj-user","script_type":"utility","2":"utility","summary":"Support for user-defined text objects","3":"Support for user-defined text objects","description":"*textobj-user* is a Vim plugin to SUPPORT writing user-defined text objects,\nespecially, simple text objects which can be defined by regular expression.\n\nNote that this plugin only provides functions to support writing user-defined\ntext objects, and this plugin does not provide any useful text objects.  That\nis your work.\n\n\nRequirements:\n- Vim 7.0 or later\n\nLatest version:\nhttp:\/\/github.com\/kana\/vim-textobj-user\n\nDocument in HTML format:\nhttp:\/\/kana.github.com\/config\/vim\/textobj-user.html","4":"*textobj-user* is a Vim plugin to SUPPORT writing user-defined text objects,\nespecially, simple text objects which can be defined by regular expression.\n\nNote that this plugin only provides functions to support writing user-defined\ntext objects, and this plugin does not provide any useful text objects.  That\nis your work.\n\n\nRequirements:\n- Vim 7.0 or later\n\nLatest version:\nhttp:\/\/github.com\/kana\/vim-textobj-user\n\nDocument in HTML format:\nhttp:\/\/kana.github.com\/config\/vim\/textobj-user.html","install_details":"...","5":"...","first_name":"Kana","6":"Kana","last_name":"Natsuno","7":"Natsuno","releases":[{"0":"2100","vim_version":"7.0","1":"7.0","script_version":"0.3.12","2":"0.3.12","version_comment":"- |textobj#user#plugin()|: Fix the bug that \"*sfile*\" is not correctly interpreted in a Unix-like environment on Microsoft Windows such as Git for Windows.  (Thank sgur for reporting this problem.  See also: https:\/\/github.com\/kana\/vim-textobj-user\/pull\/5)","3":"- |textobj#user#plugin()|: Fix the bug that \"*sfile*\" is not correctly interpreted in a Unix-like environment on Microsoft Windows such as Git for Windows.  (Thank sgur for reporting this problem.  See also: https:\/\/github.com\/kana\/vim-textobj-user\/pull\/5)","package":"vim-textobj-user-0.3.12.zip","4":"vim-textobj-user-0.3.12.zip","src_id":"17246","5":"17246","creation_date":"1326887321","6":"1326887321"},{"0":"2100","vim_version":"7.0","1":"7.0","script_version":"0.3.11","2":"0.3.11","version_comment":"- |textobj#user#plugin()|: Fix the bug that \"move-n\" and \"move-p\" operations for text objects are not correctly defined if 'ignorecase' is enabled.  (Thank h1mesuke for reporting this problem.  See also: https:\/\/github.com\/kana\/vim-textobj-user\/pull\/4)","3":"- |textobj#user#plugin()|: Fix the bug that \"move-n\" and \"move-p\" operations for text objects are not correctly defined if 'ignorecase' is enabled.  (Thank h1mesuke for reporting this problem.  See also: https:\/\/github.com\/kana\/vim-textobj-user\/pull\/4)","package":"vim-textobj-user-0.3.11.zip","4":"vim-textobj-user-0.3.11.zip","src_id":"17236","5":"17236","creation_date":"1326802164","6":"1326802164"},{"0":"2100","vim_version":"7.0","1":"7.0","script_version":"0.3.10","2":"0.3.10","version_comment":"- Update for Vim 7.3.233 or later.  (Thank cehoffman and thinca for reporting this problem.)","3":"- Update for Vim 7.3.233 or later.  (Thank cehoffman and thinca for reporting this problem.)","package":"vim-textobj-user-0.3.10.zip","4":"vim-textobj-user-0.3.10.zip","src_id":"16107","5":"16107","creation_date":"1311170848","6":"1311170848"},{"0":"2100","vim_version":"7.0","1":"7.0","script_version":"0.3.9","2":"0.3.9","version_comment":"- |textobj#user#plugin()|: Fix not to define key mappings in Select mode if appropriate.  Now it works smoothly with plugins which utilize and depend on the default behavior in Select mode.","3":"- |textobj#user#plugin()|: Fix not to define key mappings in Select mode if appropriate.  Now it works smoothly with plugins which utilize and depend on the default behavior in Select mode.","package":"vim-textobj-user-0.3.9.zip","4":"vim-textobj-user-0.3.9.zip","src_id":"12866","5":"12866","creation_date":"1271682852","6":"1271682852"},{"0":"2100","vim_version":"7.0","1":"7.0","script_version":"0.3.8","2":"0.3.8","version_comment":"- Fix a bug that it was not possible to select any range which starts with the end of a line.\n- |textobj#user#plugin()|: Fix a bug that it did not accept any function which is not script-local as a value for \"*{spec}-function*\".","3":"- Fix a bug that it was not possible to select any range which starts with the end of a line.\n- |textobj#user#plugin()|: Fix a bug that it did not accept any function which is not script-local as a value for \"*{spec}-function*\".","package":"vim-textobj-user-0.3.8.zip","4":"vim-textobj-user-0.3.8.zip","src_id":"11027","5":"11027","creation_date":"1247880325","6":"1247880325"},{"0":"2100","vim_version":"7.0","1":"7.0","script_version":"0.3.7","2":"0.3.7","version_comment":"- |textobj#user#select()|: Fix a bug that it didn't select an object\n  which: (1) matches to multiple lines and (2) contains the cursor.\n- |textobj#user#select()|, |textobj#user#select_pair()|,\n  |textobj#user#plugin()| with \"*{spec}-function*\":\n  Support |o_v| and others.  To use this feature, you have to apply\n  the following patch to Vim:\n  http:\/\/github.com\/kana\/vim\/commits\/hack\/vimvar-motion_force","3":"- |textobj#user#select()|: Fix a bug that it didn't select an object\n  which: (1) matches to multiple lines and (2) contains the cursor.\n- |textobj#user#select()|, |textobj#user#select_pair()|,\n  |textobj#user#plugin()| with \"*{spec}-function*\":\n  Support |o_v| and others.  To use this feature, you have to apply\n  the following patch to Vim:\n  http:\/\/github.com\/kana\/vim\/commits\/hack\/vimvar-motion_force","package":"vim-textobj-user-0.3.7.zip","4":"vim-textobj-user-0.3.7.zip","src_id":"9391","5":"9391","creation_date":"1224794042","6":"1224794042"},{"0":"2100","vim_version":"7.0","1":"7.0","script_version":"0.3.5","2":"0.3.5","version_comment":"Incompatible changes with 0.3.4 or ealier:\r\n- |textobj#user#plugin()|: Change the specification of functions for \"*{spec}-function*\".\r\n\r\nOther changes:\r\n- |textobj#user#plugin()|: Add missing description of functions for \"*{spec}-function*\".\r\n","3":"Incompatible changes with 0.3.4 or ealier:\r\n- |textobj#user#plugin()|: Change the specification of functions for \"*{spec}-function*\".\r\n\r\nOther changes:\r\n- |textobj#user#plugin()|: Add missing description of functions for \"*{spec}-function*\".\r\n","package":"vim-textobj-user-0.3.5.zip","4":"vim-textobj-user-0.3.5.zip","src_id":"9164","5":"9164","creation_date":"1219639005","6":"1219639005"},{"0":"2100","vim_version":"7.0","1":"7.0","script_version":"0.3.4","2":"0.3.4","version_comment":"Fix several bugs.  Add textobj#user#plugin() to define key mappings and a command to support writing a plugin which provides various user-defined text objects.\r\n","3":"Fix several bugs.  Add textobj#user#plugin() to define key mappings and a command to support writing a plugin which provides various user-defined text objects.\r\n","package":"vim-textobj-user-0.3.4.zip","4":"vim-textobj-user-0.3.4.zip","src_id":"8856","5":"8856","creation_date":"1214459302","6":"1214459302"},{"0":"2100","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"vim-textobj-user-0.1.zip","4":"vim-textobj-user-0.1.zip","src_id":"8058","5":"8058","creation_date":"1197719429","6":"1197719429"}]},"2099":{"script_id":"2099","0":"2099","script_name":"xml_autons","1":"xml_autons","script_type":"ftplugin","2":"ftplugin","summary":"auto :XMLns by the current content","3":"auto :XMLns by the current content","description":"*xml_autons* is an additional Vim filetype plugin for XML to execute |:XMLns|\r\naccording to the content of the current buffer.  This supports to use omni\r\ncompletion for XML (|ft-xml-omni|), because it requires to execute |:XMLns|.\r\n\r\n\r\nRequirements:\r\n- Vim 7.0 or later\r\n\r\nLatest version:\r\nhttp:\/\/github.com\/kana\/vim-xml-autons\r\n\r\nDocument in HTML format:\r\nhttp:\/\/kana.github.com\/config\/vim\/xml_autons.html","4":"*xml_autons* is an additional Vim filetype plugin for XML to execute |:XMLns|\r\naccording to the content of the current buffer.  This supports to use omni\r\ncompletion for XML (|ft-xml-omni|), because it requires to execute |:XMLns|.\r\n\r\n\r\nRequirements:\r\n- Vim 7.0 or later\r\n\r\nLatest version:\r\nhttp:\/\/github.com\/kana\/vim-xml-autons\r\n\r\nDocument in HTML format:\r\nhttp:\/\/kana.github.com\/config\/vim\/xml_autons.html","install_details":"...","5":"...","first_name":"Kana","6":"Kana","last_name":"Natsuno","7":"Natsuno","releases":[{"0":"2099","vim_version":"7.0","1":"7.0","script_version":"0.0.1","2":"0.0.1","version_comment":"Initial upload","3":"Initial upload","package":"vim-xml_autons-0.0.1.zip","4":"vim-xml_autons-0.0.1.zip","src_id":"8057","5":"8057","creation_date":"1197719225","6":"1197719225"}]},"2098":{"script_id":"2098","0":"2098","script_name":"fakeclip","1":"fakeclip","script_type":"utility","2":"utility","summary":"pseudo clipboard register for non-GUI version of Vim","3":"pseudo clipboard register for non-GUI version of Vim","description":"*fakeclip* is a Vim plugin to provide a pseudo |clipboard| register for\nseveral versions of Vim without |+clipboard| support, especially for non-GUI\nversion of Vim on the following platforms:\n\n- Cygwin\n- Mac OS X\n- X Window System (by xclip <http:\/\/sourceforge.net\/projects\/xclip\/>)\n\n\nfakeclip also provides a pseudo register to access a \"paste buffer\" if one of\nthe following applications is available:\n\n- GNU screen\n- tmux\n\n\nFAQ: If you can't copy\/paste multibyte characters with the clipboard\n     on Mac OS X, see |fakeclip-multibyte-on-mac|.\n\nNote for Mac OS users: Though Vim supports clipboard for the console version\nsince version 7.3, fakeclip is still useful to access a \"paste buffer\".\n\n\nRequirements:\n- Vim 7.0 or later\n\nLatest version:\nhttp:\/\/github.com\/kana\/vim-fakeclip\n\nDocument in HTML format:\nhttp:\/\/kana.github.com\/config\/vim\/fakeclip.html","4":"*fakeclip* is a Vim plugin to provide a pseudo |clipboard| register for\nseveral versions of Vim without |+clipboard| support, especially for non-GUI\nversion of Vim on the following platforms:\n\n- Cygwin\n- Mac OS X\n- X Window System (by xclip <http:\/\/sourceforge.net\/projects\/xclip\/>)\n\n\nfakeclip also provides a pseudo register to access a \"paste buffer\" if one of\nthe following applications is available:\n\n- GNU screen\n- tmux\n\n\nFAQ: If you can't copy\/paste multibyte characters with the clipboard\n     on Mac OS X, see |fakeclip-multibyte-on-mac|.\n\nNote for Mac OS users: Though Vim supports clipboard for the console version\nsince version 7.3, fakeclip is still useful to access a \"paste buffer\".\n\n\nRequirements:\n- Vim 7.0 or later\n\nLatest version:\nhttp:\/\/github.com\/kana\/vim-fakeclip\n\nDocument in HTML format:\nhttp:\/\/kana.github.com\/config\/vim\/fakeclip.html","install_details":"...","5":"...","first_name":"Kana","6":"Kana","last_name":"Natsuno","7":"Natsuno","releases":[{"0":"2098","vim_version":"7.0","1":"7.0","script_version":"0.2.10","2":"0.2.10","version_comment":"- Improve the detection of terminal multiplexers.  In other words, (a) use a more suitable one according to the current environment; (b) support using the pastebuffer from Vim not in a tmux session.  See also |g:fakeclip_terminal_multiplexer_type| for the details.  (Thanks m4i for reporting the problem via https:\/\/github.com\/kana\/vim-fakeclip\/pull\/5)","3":"- Improve the detection of terminal multiplexers.  In other words, (a) use a more suitable one according to the current environment; (b) support using the pastebuffer from Vim not in a tmux session.  See also |g:fakeclip_terminal_multiplexer_type| for the details.  (Thanks m4i for reporting the problem via https:\/\/github.com\/kana\/vim-fakeclip\/pull\/5)","package":"vim-fakeclip-0.2.10.zip","4":"vim-fakeclip-0.2.10.zip","src_id":"17281","5":"17281","creation_date":"1327165143","6":"1327165143"},{"0":"2098","vim_version":"7.0","1":"7.0","script_version":"0.2.9","2":"0.2.9","version_comment":"- Add support for |d|, |dd| and |D| operation for the clipboard and the pastebuffer.  (Thanks for Suan-Aik Yeo)","3":"- Add support for |d|, |dd| and |D| operation for the clipboard and the pastebuffer.  (Thanks for Suan-Aik Yeo)","package":"vim-fakeclip-0.2.9.zip","4":"vim-fakeclip-0.2.9.zip","src_id":"16630","5":"16630","creation_date":"1317988723","6":"1317988723"},{"0":"2098","vim_version":"7.0","1":"7.0","script_version":"0.2.8","2":"0.2.8","version_comment":"- |:FakeclipDefaultKeyMappings|: Fix to regard a given bang.","3":"- |:FakeclipDefaultKeyMappings|: Fix to regard a given bang.","package":"vim-fakeclip-0.2.8.zip","4":"vim-fakeclip-0.2.8.zip","src_id":"13733","5":"13733","creation_date":"1283255006","6":"1283255006"},{"0":"2098","vim_version":"7.0","1":"7.0","script_version":"0.2.7","2":"0.2.7","version_comment":"- Fix to read\/write the paste buffer of GNU screen outside a session.  Old versions allow to read\/write the paste buffer only if Vim is running in a session of GNU screen.","3":"- Fix to read\/write the paste buffer of GNU screen outside a session.  Old versions allow to read\/write the paste buffer only if Vim is running in a session of GNU screen.","package":"vim-fakeclip-0.2.7.zip","4":"vim-fakeclip-0.2.7.zip","src_id":"12770","5":"12770","creation_date":"1270215059","6":"1270215059"},{"0":"2098","vim_version":"7.0","1":"7.0","script_version":"0.2.6","2":"0.2.6","version_comment":"- Fix improper error message on putting to paste buffer.  (Thanks to @thinca for reporting)\n- Fix a bug that there is a possibility to fail to read the paste buffer of GNU screen if it is emptied by \"register . ''\".  (Thanks to @thinca for reporting)\n- Revise for race condition problem to read the paste buffer of GNU screen, though it's not perfect yet.","3":"- Fix improper error message on putting to paste buffer.  (Thanks to @thinca for reporting)\n- Fix a bug that there is a possibility to fail to read the paste buffer of GNU screen if it is emptied by \"register . ''\".  (Thanks to @thinca for reporting)\n- Revise for race condition problem to read the paste buffer of GNU screen, though it's not perfect yet.","package":"vim-fakeclip-0.2.6.zip","4":"vim-fakeclip-0.2.6.zip","src_id":"11739","5":"11739","creation_date":"1258374960","6":"1258374960"},{"0":"2098","vim_version":"7.0","1":"7.0","script_version":"0.2.5","2":"0.2.5","version_comment":"- Revise the way to detect whether GNU screen is available or not.\n- Fix a bug to yank to string with newline character into paste buffer register.\n- Support X Window System by xclip.  (Thanks for @thinca)\n- Support tmux.  (Thanks for @thinca)","3":"- Revise the way to detect whether GNU screen is available or not.\n- Fix a bug to yank to string with newline character into paste buffer register.\n- Support X Window System by xclip.  (Thanks for @thinca)\n- Support tmux.  (Thanks for @thinca)","package":"vim-fakeclip-0.2.5.zip","4":"vim-fakeclip-0.2.5.zip","src_id":"11709","5":"11709","creation_date":"1257952790","6":"1257952790"},{"0":"2098","vim_version":"7.0","1":"7.0","script_version":"0.2.4","2":"0.2.4","version_comment":"- Revise on platforms where |+clipboard| is available:\n  - Define all stuffs such as |fakeclip-key-mappings| on all platforms.  Without this, the pseudo register for GNU screen's paste buffer is not available if |+clipboard| is available.\n  - |:FakeclipDefaultKeyMappings|: Don't define the default key mappings for clipboard to avoid confusion with the built-in key mappings.  For example, \"*y and \"+y are not mapped to |<Plug>(fakeclip-y)|.","3":"- Revise on platforms where |+clipboard| is available:\n  - Define all stuffs such as |fakeclip-key-mappings| on all platforms.  Without this, the pseudo register for GNU screen's paste buffer is not available if |+clipboard| is available.\n  - |:FakeclipDefaultKeyMappings|: Don't define the default key mappings for clipboard to avoid confusion with the built-in key mappings.  For example, \"*y and \"+y are not mapped to |<Plug>(fakeclip-y)|.","package":"vim-fakeclip-0.2.4.zip","4":"vim-fakeclip-0.2.4.zip","src_id":"10814","5":"10814","creation_date":"1244886207","6":"1244886207"},{"0":"2098","vim_version":"7.0","1":"7.0","script_version":"0.2.3","2":"0.2.3","version_comment":"- Revise the documents on Mac OS X specific problems.  See |fakeclip-multibyte-on-mac| if you can't copy\/paste with the clipboard on Mac OS X.\n- Fix a bug that fakeclip uses wrong function to escape file-like arguments to shells.  Thanks @thinca for reporting this.","3":"- Revise the documents on Mac OS X specific problems.  See |fakeclip-multibyte-on-mac| if you can't copy\/paste with the clipboard on Mac OS X.\n- Fix a bug that fakeclip uses wrong function to escape file-like arguments to shells.  Thanks @thinca for reporting this.","package":"vim-fakeclip-0.2.3.zip","4":"vim-fakeclip-0.2.3.zip","src_id":"10535","5":"10535","creation_date":"1241547119","6":"1241547119"},{"0":"2098","vim_version":"7.0","1":"7.0","script_version":"0.2.2","2":"0.2.2","version_comment":"- Add equivalents for the following commands: |]p|, |]P|, |[p|, |[P|, |i_CTRL-R_CTRL-R|, |i_CTRL-R_CTRL-O|, |i_CTRL-R_CTRL-P|, |c_CTRL-R_CTRL-R|, |c_CTRL-R_CTRL-O|.\n- Fix the way to detect the current platform.  For Mac OS X, it depended on some assumptions.  Thanks for someone who wrote about this bug at the Vim Tips Wiki.","3":"- Add equivalents for the following commands: |]p|, |]P|, |[p|, |[P|, |i_CTRL-R_CTRL-R|, |i_CTRL-R_CTRL-O|, |i_CTRL-R_CTRL-P|, |c_CTRL-R_CTRL-R|, |c_CTRL-R_CTRL-O|.\n- Fix the way to detect the current platform.  For Mac OS X, it depended on some assumptions.  Thanks for someone who wrote about this bug at the Vim Tips Wiki.","package":"vim-fakeclip-0.2.2.zip","4":"vim-fakeclip-0.2.2.zip","src_id":"10276","5":"10276","creation_date":"1237984069","6":"1237984069"},{"0":"2098","vim_version":"7.0","1":"7.0","script_version":"0.2.1","2":"0.2.1","version_comment":"- Refactor.\n- Support the paste buffer of GNU screen as a pseudo register.","3":"- Refactor.\n- Support the paste buffer of GNU screen as a pseudo register.","package":"vim-fakeclip-0.2.1.zip","4":"vim-fakeclip-0.2.1.zip","src_id":"9395","5":"9395","creation_date":"1224839665","6":"1224839665"},{"0":"2098","vim_version":"7.0","1":"7.0","script_version":"0.2.0","2":"0.2.0","version_comment":"- Rename as \"fakeclip\" (the old name is \"cygclip\").\r\n- Support Mac OS X.\r\n- Autoloaded.","3":"- Rename as \"fakeclip\" (the old name is \"cygclip\").\r\n- Support Mac OS X.\r\n- Autoloaded.","package":"vim-fakeclip-0.2.0.zip","4":"vim-fakeclip-0.2.0.zip","src_id":"8965","5":"8965","creation_date":"1216277254","6":"1216277254"},{"0":"2098","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Modified to define the default key mappings as this plugin is loaded.  Add the way to suppress this behavior.","3":"Modified to define the default key mappings as this plugin is loaded.  Add the way to suppress this behavior.","package":"vim-cygclip-0.1.zip","4":"vim-cygclip-0.1.zip","src_id":"8091","5":"8091","creation_date":"1198736867","6":"1198736867"},{"0":"2098","vim_version":"7.0","1":"7.0","script_version":"0.0","2":"0.0","version_comment":"Initial upload","3":"Initial upload","package":"vim-cygclip-0.0.zip","4":"vim-cygclip-0.0.zip","src_id":"8056","5":"8056","creation_date":"1197718951","6":"1197718951"}]},"2097":{"script_id":"2097","0":"2097","script_name":"narrow","1":"narrow","script_type":"utility","2":"utility","summary":"Emulate Emacs' narrowing feature","3":"Emulate Emacs' narrowing feature","description":"*narrow* is a Vim plugin to emulate Emacs' narrowing feature.\r\nFrom GNU Emacs Manual:\r\n\r\n\tNarrowing means focusing in on some portion of the buffer, making the\r\n\trest temporarily inaccessible. The portion which you can still get to\r\n\tis called the accessible portion. Canceling the narrowing, which makes\r\n\tthe entire buffer once again accessible, is called widening. The\r\n\tbounds of narrowing in effect in a buffer are called the buffer's\r\n\trestriction.\r\n\r\n\tNarrowing can make it easier to concentrate on a single subroutine or\r\n\tparagraph by eliminating clutter. It can also be used to limit the\r\n\trange of operation of a replace command or repeating keyboard macro.\r\n\r\nNote that there are some differences from the original behavior.\r\nSee |narrow-bugs| for the detail.\r\n\r\n\r\nRequirements:\r\n- Vim 7.0 or later\r\n\r\nLatest version:\r\nhttp:\/\/github.com\/kana\/vim-narrow\r\n\r\nDocument in HTML format:\r\nhttp:\/\/kana.github.com\/config\/vim\/narrow.html","4":"*narrow* is a Vim plugin to emulate Emacs' narrowing feature.\r\nFrom GNU Emacs Manual:\r\n\r\n\tNarrowing means focusing in on some portion of the buffer, making the\r\n\trest temporarily inaccessible. The portion which you can still get to\r\n\tis called the accessible portion. Canceling the narrowing, which makes\r\n\tthe entire buffer once again accessible, is called widening. The\r\n\tbounds of narrowing in effect in a buffer are called the buffer's\r\n\trestriction.\r\n\r\n\tNarrowing can make it easier to concentrate on a single subroutine or\r\n\tparagraph by eliminating clutter. It can also be used to limit the\r\n\trange of operation of a replace command or repeating keyboard macro.\r\n\r\nNote that there are some differences from the original behavior.\r\nSee |narrow-bugs| for the detail.\r\n\r\n\r\nRequirements:\r\n- Vim 7.0 or later\r\n\r\nLatest version:\r\nhttp:\/\/github.com\/kana\/vim-narrow\r\n\r\nDocument in HTML format:\r\nhttp:\/\/kana.github.com\/config\/vim\/narrow.html","install_details":"...","5":"...","first_name":"Kana","6":"Kana","last_name":"Natsuno","7":"Natsuno","releases":[{"0":"2097","vim_version":"7.0","1":"7.0","script_version":"0.2.1","2":"0.2.1","version_comment":"- Fix minor bugs:\n  - |:Widen| raises an error for buffers without fold.\n  - |:Narrow| doesn't hide lines smaller than 'foldminlines'.","3":"- Fix minor bugs:\n  - |:Widen| raises an error for buffers without fold.\n  - |:Narrow| doesn't hide lines smaller than 'foldminlines'.","package":"vim-narrow-0.2.1.zip","4":"vim-narrow-0.2.1.zip","src_id":"10060","5":"10060","creation_date":"1235810343","6":"1235810343"},{"0":"2097","vim_version":"7.0","1":"7.0","script_version":"0.2","2":"0.2","version_comment":"- Fix |:Narrow| and |:Widen| not to use temporary files.  Now |:Widen| correctly works even if the target buffer is |:Narrow|'ed by two or more Vim processes.\r\n- Modify |:Narrow| to |zz| after narrowing for visibility.\r\n- Modify |:Narrow| to include all lines of closed folds in [range].","3":"- Fix |:Narrow| and |:Widen| not to use temporary files.  Now |:Widen| correctly works even if the target buffer is |:Narrow|'ed by two or more Vim processes.\r\n- Modify |:Narrow| to |zz| after narrowing for visibility.\r\n- Modify |:Narrow| to include all lines of closed folds in [range].","package":"vim-narrow-0.2.zip","4":"vim-narrow-0.2.zip","src_id":"8096","5":"8096","creation_date":"1198855859","6":"1198855859"},{"0":"2097","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"- Fix the bug that 'foldenable' is not set after :Narrow.\r\n- Fix the bug that the cursor is moved to somewhere after :Widen.\r\n- Add g:narrow_allow_overridingp.","3":"- Fix the bug that 'foldenable' is not set after :Narrow.\r\n- Fix the bug that the cursor is moved to somewhere after :Widen.\r\n- Add g:narrow_allow_overridingp.","package":"vim-narrow-0.1.zip","4":"vim-narrow-0.1.zip","src_id":"8092","5":"8092","creation_date":"1198749647","6":"1198749647"},{"0":"2097","vim_version":"7.0","1":"7.0","script_version":"0.0","2":"0.0","version_comment":"Initial upload","3":"Initial upload","package":"vim-narrow-0.0.zip","4":"vim-narrow-0.0.zip","src_id":"8055","5":"8055","creation_date":"1197717239","6":"1197717239"}]},"2096":{"script_id":"2096","0":"2096","script_name":"Tab Menu","1":"Tab Menu","script_type":"utility","2":"utility","summary":"Tab Menu for all the tabs in VIM","3":"Tab Menu for all the tabs in VIM","description":"This plugin adds a menu with the list of all the tabs in GVIM. Clicking on a file name in the menu takes to the corresponding tab. This would be very useful when working with many files in different tabs. This would simulate the tab behaviour in other editors. \r\n\r\n\r\nKnown Problems:\r\nImmediately after opening a new tab, the tab list will not reflect with the actual tab details. Once you move to another tab, the tab list would be refreshed. ","4":"This plugin adds a menu with the list of all the tabs in GVIM. Clicking on a file name in the menu takes to the corresponding tab. This would be very useful when working with many files in different tabs. This would simulate the tab behaviour in other editors. \r\n\r\n\r\nKnown Problems:\r\nImmediately after opening a new tab, the tab list will not reflect with the actual tab details. Once you move to another tab, the tab list would be refreshed. ","install_details":"Copy tabmenu.vim to vim70\/plugins directory. ","5":"Copy tabmenu.vim to vim70\/plugins directory. ","first_name":"Satish","6":"Satish","last_name":"TN","7":"TN","releases":[{"0":"2096","vim_version":"7.0","1":"7.0","script_version":"1.3","2":"1.3","version_comment":"Fixed the problem when opened from the shell. Courtesy: Martin Filser","3":"Fixed the problem when opened from the shell. Courtesy: Martin Filser","package":"tabmenu.vim","4":"tabmenu.vim","src_id":"15921","5":"15921","creation_date":"1308350320","6":"1308350320"},{"0":"2096","vim_version":"7.0","1":"7.0","script_version":"1.2","2":"1.2","version_comment":"I removed ^M characters in the previous version. ","3":"I removed ^M characters in the previous version. ","package":"tabmenu.vim","4":"tabmenu.vim","src_id":"9059","5":"9059","creation_date":"1217499965","6":"1217499965"},{"0":"2096","vim_version":"7.0","1":"7.0","script_version":"1.1","2":"1.1","version_comment":"The tab menu is sorted on the filename","3":"The tab menu is sorted on the filename","package":"tabmenu.vim","4":"tabmenu.vim","src_id":"8143","5":"8143","creation_date":"1200022896","6":"1200022896"},{"0":"2096","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"tabmenu.vim","4":"tabmenu.vim","src_id":"8054","5":"8054","creation_date":"1197713016","6":"1197713016"}]},"2095":{"script_id":"2095","0":"2095","script_name":"Smartput","1":"Smartput","script_type":"utility","2":"utility","summary":"Adjust spaces and commas when putting text.","3":"Adjust spaces and commas when putting text.","description":"Smartput tries to reduce the need of fine-tuning spaces after a put.  Under certain conditions, it also moves a comma to the other side of the register before putting.\r\n\r\nThe following keys are remapped: p, P, gp and gP.\r\n\r\nPress  <Leader>st  to toggle Smartput on and off.\r\n\r\nSee also:\r\n    :help todo| \/Smart cut.paste\r\n\r\nThere is a wealth of customization options -- the help file has the details.\r\n\r\n\r\nExamples:\r\n\r\n    Hello World!\r\nType  dwep  on \"Hello\"\r\n    World Hello!\r\n\r\n    Hello World!\r\nType  dawbP  on \"World\"\r\n    World Hello!\r\n\r\n    Hello\r\n    ()\r\nType  dww3p  on \"Hello\"\r\n    (Hello Hello Hello)\r\n\r\n    (Hello, World)\r\nType  dWep  on \"Hello\"\r\n    (World, Hello)\r\n","4":"Smartput tries to reduce the need of fine-tuning spaces after a put.  Under certain conditions, it also moves a comma to the other side of the register before putting.\r\n\r\nThe following keys are remapped: p, P, gp and gP.\r\n\r\nPress  <Leader>st  to toggle Smartput on and off.\r\n\r\nSee also:\r\n    :help todo| \/Smart cut.paste\r\n\r\nThere is a wealth of customization options -- the help file has the details.\r\n\r\n\r\nExamples:\r\n\r\n    Hello World!\r\nType  dwep  on \"Hello\"\r\n    World Hello!\r\n\r\n    Hello World!\r\nType  dawbP  on \"World\"\r\n    World Hello!\r\n\r\n    Hello\r\n    ()\r\nType  dww3p  on \"Hello\"\r\n    (Hello Hello Hello)\r\n\r\n    (Hello, World)\r\nType  dWep  on \"Hello\"\r\n    (World, Hello)\r\n","install_details":"Note: v0.5 works only with single byte encodings!\r\n\r\nExtract the archive to a folder of your runtimepath.\r\n\r\nFiles:\r\ndoc\\smartput.txt\r\nplugin\\smartput.vim\r\n\r\nInstall the help file:\r\n    :h helptags","5":"Note: v0.5 works only with single byte encodings!\r\n\r\nExtract the archive to a folder of your runtimepath.\r\n\r\nFiles:\r\ndoc\\smartput.txt\r\nplugin\\smartput.vim\r\n\r\nInstall the help file:\r\n    :h helptags","first_name":"Andy","6":"Andy","last_name":"Wokula","7":"Wokula","releases":[{"0":"2095","vim_version":"7.0","1":"7.0","script_version":"0.6","2":"0.6","version_comment":"Added: now supposed to work with UTF-8\r\nChanged: g:smartput_comma string of CharTypes (not a pattern)\r\nFixed: hasmapto() bug, user mapping didn't disable <Leader>st","3":"Added: now supposed to work with UTF-8\r\nChanged: g:smartput_comma string of CharTypes (not a pattern)\r\nFixed: hasmapto() bug, user mapping didn't disable <Leader>st","package":"smartput_0.6.zip","4":"smartput_0.6.zip","src_id":"8062","5":"8062","creation_date":"1197823723","6":"1197823723"},{"0":"2095","vim_version":"7.0","1":"7.0","script_version":"0.5","2":"0.5","version_comment":"Initial upload","3":"Initial upload","package":"smartput.zip","4":"smartput.zip","src_id":"8053","5":"8053","creation_date":"1197701067","6":"1197701067"}]},"2094":{"script_id":"2094","0":"2094","script_name":"Puppet Syntax Highlighting","1":"Puppet Syntax Highlighting","script_type":"syntax","2":"syntax","summary":"Syntax Highlighting for Puppet (Conf Mang.)","3":"Syntax Highlighting for Puppet (Conf Mang.)","description":"Syntax highlighting for Puppet, http:\/\/reductivelabs.com\/trac\/puppet, the distributed configuration management system. Based on the initial work by Luke Kanies.\r\n\r\n","4":"Syntax highlighting for Puppet, http:\/\/reductivelabs.com\/trac\/puppet, the distributed configuration management system. Based on the initial work by Luke Kanies.\r\n\r\n","install_details":"To Install: unzip puppet_syntax.zip into your ~\/.vim or respective config location.","5":"To Install: unzip puppet_syntax.zip into your ~\/.vim or respective config location.","first_name":"Britt","6":"Britt","last_name":"Selvitelle","7":"Selvitelle","releases":[{"0":"2094","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"puppet_syntax.zip","4":"puppet_syntax.zip","src_id":"8052","5":"8052","creation_date":"1197636529","6":"1197636529"}]},"2093":{"script_id":"2093","0":"2093","script_name":"complval.vim","1":"complval.vim","script_type":"utility","2":"utility","summary":"complete a variable's value after :let in the command line","3":"complete a variable's value after :let in the command line","description":"Usage Example:\r\n    :let foo = \"bar\"\r\n    :let foo = <C-G>\r\n\r\nCompletable values are numbers, strings, lists and dicts.\r\n\r\nGood for changing customization variables.","4":"Usage Example:\r\n    :let foo = \"bar\"\r\n    :let foo = <C-G>\r\n\r\nCompletable values are numbers, strings, lists and dicts.\r\n\r\nGood for changing customization variables.","install_details":"copy the file into your autoload folder\r\n\r\ncreate a mapping in your vimrc:\r\n    cno <C-G> <c-r>=complval#VarComplValue()<cr>\r\nThis maps c_Ctrl-G for completion.  Tab should not be used, it already completes other things.\r\n","5":"copy the file into your autoload folder\r\n\r\ncreate a mapping in your vimrc:\r\n    cno <C-G> <c-r>=complval#VarComplValue()<cr>\r\nThis maps c_Ctrl-G for completion.  Tab should not be used, it already completes other things.\r\n","first_name":"Andy","6":"Andy","last_name":"Wokula","7":"Wokula","releases":[{"0":"2093","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"complval.vim","4":"complval.vim","src_id":"8047","5":"8047","creation_date":"1197540238","6":"1197540238"}]},"2092":{"script_id":"2092","0":"2092","script_name":"reloaded.vim","1":"reloaded.vim","script_type":"color scheme","2":"color scheme","summary":"Simplified Matrix theme for console\/gui","3":"Simplified Matrix theme for console\/gui","description":"This is a simplified version of the Matrix theme using colors that work in the console as well as the GUI (Should look about the same in both)","4":"This is a simplified version of the Matrix theme using colors that work in the console as well as the GUI (Should look about the same in both)","install_details":"Put it in one of your colors directories.\r\n  ex. $HOME\/.vim\/colors\/\r\n  ex. $HOME\\vimfiles\\colors\\\r\n  ex. $VIM\\vimfiles\\colors\\\r\nThen, just do :colorscheme reloaded","5":"Put it in one of your colors directories.\r\n  ex. $HOME\/.vim\/colors\/\r\n  ex. $HOME\\vimfiles\\colors\\\r\n  ex. $VIM\\vimfiles\\colors\\\r\nThen, just do :colorscheme reloaded","first_name":"Connor","6":"Connor","last_name":"Berry","7":"Berry","releases":[{"0":"2092","vim_version":"7.0","1":"7.0","script_version":"0.3","2":"0.3","version_comment":":set nu now greenish also","3":":set nu now greenish also","package":"reloaded.vim","4":"reloaded.vim","src_id":"8095","5":"8095","creation_date":"1198834402","6":"1198834402"},{"0":"2092","vim_version":"6.0","1":"6.0","script_version":"0.2","2":"0.2","version_comment":"fixed splash screen colors, changed\/added cursorline\/cursorcolumn \r\n","3":"fixed splash screen colors, changed\/added cursorline\/cursorcolumn \r\n","package":"reloaded.vim","4":"reloaded.vim","src_id":"8048","5":"8048","creation_date":"1197546632","6":"1197546632"},{"0":"2092","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"reloaded.vim","4":"reloaded.vim","src_id":"8041","5":"8041","creation_date":"1197466599","6":"1197466599"}]},"2091":{"script_id":"2091","0":"2091","script_name":"verilog.vim","1":"verilog.vim","script_type":"indent","2":"indent","summary":"Verilog HDL\/SystemVerilog HDVL indent file","3":"Verilog HDL\/SystemVerilog HDVL indent file","description":"\" Title:        Verilog HDL\/SystemVerilog HDVL indent file\r\n\" Maintainer:\tMingzhi Li <limingzhi05@mail.nankai.edu.cn>\r\n\" Last Change:\t2007-12-16 20:10:57 CST\r\n\"\r\n\" Buffer Variables:\r\n\"     b:verilog_indent_width   : indenting width(default value: shiftwidth)\r\n\"\r\n\" Install:\r\n\"     Drop it to ~\/.vim\/indent \r\n\"\r\n\" URL:\r\n\"    http:\/\/www.vim.org\/scripts\/script.php?script_id=2091\r\n\"\r\n\" Revision Comments:\r\n\"     Mingzhi Li  2007-12-16 20:09:39 CST Version 1.2      \r\n\"        Bug fixes\r\n\"     Mingzhi Li  2007-12-13 23:47:54 CST Version 1.1      \r\n\"        Bug fix, improve performance and add introductions\r\n\"     Mingzhi Li  2007-12-7  22:16:41 CST Version 1.0  \r\n\"        Initial version\r\n\"       \r\n\" Known Limited:\r\n\"     This indent file can not work well, when you break the long line into\r\n\"     multi-line manually, such as:\r\n\"      always @(posedge a or posedge b \r\n\"          or posedge c ) begin\r\n\"         \/\/...\r\n\"      end \r\n\"     Recommend to use the coding style(wraped by vim automatically) as following:\r\n\"       always @(posedge a or posedge b or posedge c ) begin\r\n\"         \/\/...\r\n\"       end ","4":"\" Title:        Verilog HDL\/SystemVerilog HDVL indent file\r\n\" Maintainer:\tMingzhi Li <limingzhi05@mail.nankai.edu.cn>\r\n\" Last Change:\t2007-12-16 20:10:57 CST\r\n\"\r\n\" Buffer Variables:\r\n\"     b:verilog_indent_width   : indenting width(default value: shiftwidth)\r\n\"\r\n\" Install:\r\n\"     Drop it to ~\/.vim\/indent \r\n\"\r\n\" URL:\r\n\"    http:\/\/www.vim.org\/scripts\/script.php?script_id=2091\r\n\"\r\n\" Revision Comments:\r\n\"     Mingzhi Li  2007-12-16 20:09:39 CST Version 1.2      \r\n\"        Bug fixes\r\n\"     Mingzhi Li  2007-12-13 23:47:54 CST Version 1.1      \r\n\"        Bug fix, improve performance and add introductions\r\n\"     Mingzhi Li  2007-12-7  22:16:41 CST Version 1.0  \r\n\"        Initial version\r\n\"       \r\n\" Known Limited:\r\n\"     This indent file can not work well, when you break the long line into\r\n\"     multi-line manually, such as:\r\n\"      always @(posedge a or posedge b \r\n\"          or posedge c ) begin\r\n\"         \/\/...\r\n\"      end \r\n\"     Recommend to use the coding style(wraped by vim automatically) as following:\r\n\"       always @(posedge a or posedge b or posedge c ) begin\r\n\"         \/\/...\r\n\"       end ","install_details":"Drop it to ~\/.vim\/indent","5":"Drop it to ~\/.vim\/indent","first_name":"MingZhi","6":"MingZhi","last_name":"Li","7":"Li","releases":[{"0":"2091","vim_version":"7.0","1":"7.0","script_version":"1.3","2":"1.3","version_comment":"Bugfixs","3":"Bugfixs","package":"verilog.vim","4":"verilog.vim","src_id":"17590","5":"17590","creation_date":"1331651791","6":"1331651791"},{"0":"2091","vim_version":"7.0","1":"7.0","script_version":"1.2","2":"1.2","version_comment":"Bug fixes","3":"Bug fixes","package":"verilog.vim","4":"verilog.vim","src_id":"8061","5":"8061","creation_date":"1197778305","6":"1197778305"},{"0":"2091","vim_version":"7.0","1":"7.0","script_version":"1.1","2":"1.1","version_comment":"Bug fix, improve performance and add introductions","3":"Bug fix, improve performance and add introductions","package":"verilog.vim","4":"verilog.vim","src_id":"8046","5":"8046","creation_date":"1197537101","6":"1197537101"},{"0":"2091","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"verilog.vim","4":"verilog.vim","src_id":"8040","5":"8040","creation_date":"1197438980","6":"1197438980"}]},"2090":{"script_id":"2090","0":"2090","script_name":"view_diff","1":"view_diff","script_type":"utility","2":"utility","summary":"view diff file in an eaiser way by vimdiff","3":"view diff file in an eaiser way by vimdiff","description":"Tags: vimdiff svn subversion diff \r\n\r\nWHY I WRITE IT:\r\n  During daily work, I often need to read the result of \"svn diff\" before I commit my work into subversion repository. But only reading the diff result is tedious: sometimes I want to read more context lines; sometimes, when I find some mistake I made in my work, I have to open the file and modify the codes there. On the other hand, vim provide a very good way to view the diff of two versions of file, that is vimdiff, I like it! So f we can use it here that will be very useful. But after some web searching, I did not find anything that can help me here. So the script comes out.\r\n\r\nHOW TO USE IT:\r\n  Normally I use this script in the following way: \r\n    1. piped svn diff result to vim, for example: \"svn diff | vim - \"\r\n    2. use shortcuts to open vimdiff modes on current diff file\r\n    shortcuts: \r\n        <leader>dv   :   open two versions of file in vimdiff mode\r\n        <leader>df    :   open  the old\/new file \r\n        <leader>dn   :   open next two versions of file in vimdiff mode in svn diff result file\r\n        <leader>dp   :   open previous two versions of file in vimdiff mode in svn diff result file\r\n        <leader>dz   :    fold svn diff result file\r\n    This script work both for svn diff result and normal diff result. \r\n\r\n    There is not more docs till now(maybe more in future), but you can learn this script by trying it :)    \r\n\r\n  I need to point out that I am not an experienced vim script programmer and I just want to work out a script that can fulfill my needs. So the codes of script may not be beautiful, but I have used it for several months and it works fine. \r\n\r\n  If you have any comment, bug report, patch, please email it to me(linsong DOT qizi AT gmail DOT com), Thanks. \r\n\r\n  Happy Vimming! \r\n\r\n","4":"Tags: vimdiff svn subversion diff \r\n\r\nWHY I WRITE IT:\r\n  During daily work, I often need to read the result of \"svn diff\" before I commit my work into subversion repository. But only reading the diff result is tedious: sometimes I want to read more context lines; sometimes, when I find some mistake I made in my work, I have to open the file and modify the codes there. On the other hand, vim provide a very good way to view the diff of two versions of file, that is vimdiff, I like it! So f we can use it here that will be very useful. But after some web searching, I did not find anything that can help me here. So the script comes out.\r\n\r\nHOW TO USE IT:\r\n  Normally I use this script in the following way: \r\n    1. piped svn diff result to vim, for example: \"svn diff | vim - \"\r\n    2. use shortcuts to open vimdiff modes on current diff file\r\n    shortcuts: \r\n        <leader>dv   :   open two versions of file in vimdiff mode\r\n        <leader>df    :   open  the old\/new file \r\n        <leader>dn   :   open next two versions of file in vimdiff mode in svn diff result file\r\n        <leader>dp   :   open previous two versions of file in vimdiff mode in svn diff result file\r\n        <leader>dz   :    fold svn diff result file\r\n    This script work both for svn diff result and normal diff result. \r\n\r\n    There is not more docs till now(maybe more in future), but you can learn this script by trying it :)    \r\n\r\n  I need to point out that I am not an experienced vim script programmer and I just want to work out a script that can fulfill my needs. So the codes of script may not be beautiful, but I have used it for several months and it works fine. \r\n\r\n  If you have any comment, bug report, patch, please email it to me(linsong DOT qizi AT gmail DOT com), Thanks. \r\n\r\n  Happy Vimming! \r\n\r\n","install_details":"just put view_diff.vim to $HOME\/.vim\/plugin folder, that is done. \r\n\r\nNOTE: \r\n   * this script need vim7.0+\r\n   * this script only works under linux like system(include Mac OS), but not work under windows(may support in future)","5":"just put view_diff.vim to $HOME\/.vim\/plugin folder, that is done. \r\n\r\nNOTE: \r\n   * this script need vim7.0+\r\n   * this script only works under linux like system(include Mac OS), but not work under windows(may support in future)","first_name":"Vincent","6":"Vincent","last_name":"Wang","7":"Wang","releases":[{"0":"2090","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"view_diff.vim","4":"view_diff.vim","src_id":"8033","5":"8033","creation_date":"1197160236","6":"1197160236"}]},"2089":{"script_id":"2089","0":"2089","script_name":"Acpp","1":"Acpp","script_type":"utility","2":"utility","summary":"Does a better job than A script","3":"Does a better job than A script","description":"If you call \"Acpp\" when editing \"\/path\/to\/file\/src\/Window.cpp\", the script:\r\n* sees if there's \"\/path\/to\/file\/src\/\" directory;\r\n** if so:\r\n*** switch to \"\/path\/to\/file\/include\/Window\" if it exists;\r\n*** switch to \"\/path\/to\/file\/include\/Window.h\" even if it doesn't exist;\r\n** if not:\r\n*** switch to \"\/path\/to\/file\/src\/Window\" if it exists;\r\n*** switch to \"\/path\/to\/file\/src\/Window.h\" even if it doesn't exist.\r\n\r\nIf you call \"Acpp\" when editing \"\/path\/to\/file\/include\/Window\"\r\nor \"\/path\/to\/file\/include\/Window.h\", the script:\r\n* sees if there's \"\/path\/to\/file\/src\/\" directory;\r\n** if so:\r\n*** switch to \"\/path\/to\/file\/src\/Window.cpp\" even if it doesn't exist.\r\n\r\nIt does not strictly depend on Vim 7, it's just the version I have, the script should work fine with previous versions too.","4":"If you call \"Acpp\" when editing \"\/path\/to\/file\/src\/Window.cpp\", the script:\r\n* sees if there's \"\/path\/to\/file\/src\/\" directory;\r\n** if so:\r\n*** switch to \"\/path\/to\/file\/include\/Window\" if it exists;\r\n*** switch to \"\/path\/to\/file\/include\/Window.h\" even if it doesn't exist;\r\n** if not:\r\n*** switch to \"\/path\/to\/file\/src\/Window\" if it exists;\r\n*** switch to \"\/path\/to\/file\/src\/Window.h\" even if it doesn't exist.\r\n\r\nIf you call \"Acpp\" when editing \"\/path\/to\/file\/include\/Window\"\r\nor \"\/path\/to\/file\/include\/Window.h\", the script:\r\n* sees if there's \"\/path\/to\/file\/src\/\" directory;\r\n** if so:\r\n*** switch to \"\/path\/to\/file\/src\/Window.cpp\" even if it doesn't exist.\r\n\r\nIt does not strictly depend on Vim 7, it's just the version I have, the script should work fine with previous versions too.","install_details":"I simply added the following line into my ~\/.vimrc file:\r\nsource ~\/acpp.vim\r\nYou can also place it to \/usr\/share\/vim\/vim71\/plugin directory (substitute vim71 with your vimVERSION)","5":"I simply added the following line into my ~\/.vimrc file:\r\nsource ~\/acpp.vim\r\nYou can also place it to \/usr\/share\/vim\/vim71\/plugin directory (substitute vim71 with your vimVERSION)","first_name":"michael","6":"michael","last_name":"kapelko","7":"kapelko","releases":[{"0":"2089","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Switching between .h\/.h-less header and .cpp source files both with include\/src scheme and simply in the same directory.","3":"Switching between .h\/.h-less header and .cpp source files both with include\/src scheme and simply in the same directory.","package":"acpp.vim","4":"acpp.vim","src_id":"20591","5":"20591","creation_date":"1375432054","6":"1375432054"},{"0":"2089","vim_version":"7.0","1":"7.0","script_version":"0.01","2":"0.01","version_comment":"Initial upload","3":"Initial upload","package":"acpp.vim","4":"acpp.vim","src_id":"8030","5":"8030","creation_date":"1196890004","6":"1196890004"}]},"2088":{"script_id":"2088","0":"2088","script_name":"WuYe","1":"WuYe","script_type":"color scheme","2":"color scheme","summary":"A dark background color scheme","3":"A dark background color scheme","description":"A dark colorscheme which works in the GUI and in 8\/16 colour terminals .\r\n\r\nScreenshot: http:\/\/i30.tinypic.com\/29ghbnd.png\r\n\r\n\"WuYe\"=\"午夜\"","4":"A dark colorscheme which works in the GUI and in 8\/16 colour terminals .\r\n\r\nScreenshot: http:\/\/i30.tinypic.com\/29ghbnd.png\r\n\r\n\"WuYe\"=\"午夜\"","install_details":"","5":"","first_name":"Chunlin","6":"Chunlin","last_name":"Li(\u674e)","7":"Li(李)","releases":[{"0":"2088","vim_version":"7.0","1":"7.0","script_version":"1.2.1","2":"1.2.1","version_comment":"The final version","3":"The final version","package":"wuye.vim","4":"wuye.vim","src_id":"11181","5":"11181","creation_date":"1250089335","6":"1250089335"}]},"2087":{"script_id":"2087","0":"2087","script_name":"refactor","1":"refactor","script_type":"utility","2":"utility","summary":"C\/C++ refactoring tool","3":"C\/C++ refactoring tool","description":"This plugin contains some basic refactoring commands for C\/C++.\r\nFor the complexity of C++, instead of really parse the source code, I used \r\nregular expression matches. But it works well as I tested. \r\n\r\nNOTE: It doesn't work for old style parameter declaratoins! And I admit that it may mess up your code sometime if you occasionally forget the rules. Thanks for the kind man who point out this.\r\n\r\n\r\nThe refactor commands and their default key map currently are:\r\n\t1. <A-r>e \tExtract method\r\n\t2. <A-r>p \tlocal variable to Parameter\r\n\t3. <A-r>r \t Rename local variable\r\n\t4. <A-r>d \tDelete parameter\r\n\t5. <A-r>o \treOrder parameters\r\n\t6. <A-r>c \tintroduce Constant\r\n\r\nBiDongliang \tbidongliang_2000@126.com 2007\/12\/4","4":"This plugin contains some basic refactoring commands for C\/C++.\r\nFor the complexity of C++, instead of really parse the source code, I used \r\nregular expression matches. But it works well as I tested. \r\n\r\nNOTE: It doesn't work for old style parameter declaratoins! And I admit that it may mess up your code sometime if you occasionally forget the rules. Thanks for the kind man who point out this.\r\n\r\n\r\nThe refactor commands and their default key map currently are:\r\n\t1. <A-r>e \tExtract method\r\n\t2. <A-r>p \tlocal variable to Parameter\r\n\t3. <A-r>r \t Rename local variable\r\n\t4. <A-r>d \tDelete parameter\r\n\t5. <A-r>o \treOrder parameters\r\n\t6. <A-r>c \tintroduce Constant\r\n\r\nBiDongliang \tbidongliang_2000@126.com 2007\/12\/4","install_details":"","5":"","first_name":"bi","6":"bi","last_name":"dongliang","7":"dongliang","releases":[{"0":"2087","vim_version":"6.0","1":"6.0","script_version":"1.03","2":"1.03","version_comment":"Updated some messages to help using more easy.","3":"Updated some messages to help using more easy.","package":"refactor.vim","4":"refactor.vim","src_id":"8029","5":"8029","creation_date":"1196874023","6":"1196874023"},{"0":"2087","vim_version":"6.0","1":"6.0","script_version":"1.02","2":"1.02","version_comment":"Parse error of variable defination with initialization.","3":"Parse error of variable defination with initialization.","package":"refactor.vim","4":"refactor.vim","src_id":"8023","5":"8023","creation_date":"1196724691","6":"1196724691"},{"0":"2087","vim_version":"6.0","1":"6.0","script_version":"1.01","2":"1.01","version_comment":"Add word boundary to some patterns. (\\<\\>)","3":"Add word boundary to some patterns. (\\<\\>)","package":"refactor.vim","4":"refactor.vim","src_id":"8021","5":"8021","creation_date":"1196717460","6":"1196717460"}]},"2086":{"script_id":"2086","0":"2086","script_name":"code-snippet","1":"code-snippet","script_type":"utility","2":"utility","summary":"Simple input assistance of code snippets","3":"Simple input assistance of code snippets","description":"FILE COMPOSITION:\r\n\r\nplugin\/code-snippet.vim : a script file.\r\ndoc\/code-snippet.txt : an English help file.\r\ndoc\/code-snippet.jax : a Japanese help file.\r\n\r\nSUMMARY:\r\n\r\nThis plugin provides a simple input assistance of code snippets.  A code snippet is an idiom much used in source codes or markuped texts.  Here are the basic steps to use (and they are almost all).\r\n\r\n        1. Register snippets (generally in filetype plugins).\r\n        2. Type a trigger string in the insert mode.\r\n        3. Press <S-CR> or <C-CR> to expand a snippet, and jump to each next\/previous placeholder.\r\n        4. Press <CR> to fill in a placeholder.\r\n\r\nSnippets are registered as abbreviations.  You can therefore expand them by pressing <Esc> like mere abbreviations.\r\n\r\nPlaceholders can contain default strings.\r\n\r\nThis plugin is well configurable.  You can configure these points.\r\n\r\n        * Map commands to other keys.\r\n        * Use the select mode instead of the visual mode.\r\n        * Change the format of placeholders in general or buffer-local.\r\n\r\nEXAMPLE:\r\n\r\nType like this in the commandline mode.\r\n\r\n        :StringAbbrLocal fputs() \"fputs([~str~], [~fp:stderr~])[~~]\"\r\n\r\nThen type like this in the insert mode.\r\n\r\n        fputs()\r\n\r\nAnd press <S-CR>.\r\n\r\n        fputs([~str~], [~fp:stderr~])[~~]\r\n\r\nThe line is expanded like above and \"[~str~]\" is selected in the visual mode.  \"[~ ... ~]\" is a placeholder.  Each time you press <S-CR>, the cursor jumps to the next placeholder.  Press <C-CR> to jump back to the previous placeholder.\r\n\r\nWhen you press <CR>, the placeholder under the cursor is cut and Vim switches to the insert mode.  So that you can fill in the place.  Pressing <CR> at the second placeholder \"[~fp:stderr~]\", the default string \"stderr\" is inserted.  If you want to insert another word, it can be deleted by pressing <C-U> (see :help i_Ctrl-U).\r\n\r\nThe last empty placeholder \"[~~]\" is not selected by <S-CR>, but simply deleted so that you can insert a semicolon and so on.","4":"FILE COMPOSITION:\r\n\r\nplugin\/code-snippet.vim : a script file.\r\ndoc\/code-snippet.txt : an English help file.\r\ndoc\/code-snippet.jax : a Japanese help file.\r\n\r\nSUMMARY:\r\n\r\nThis plugin provides a simple input assistance of code snippets.  A code snippet is an idiom much used in source codes or markuped texts.  Here are the basic steps to use (and they are almost all).\r\n\r\n        1. Register snippets (generally in filetype plugins).\r\n        2. Type a trigger string in the insert mode.\r\n        3. Press <S-CR> or <C-CR> to expand a snippet, and jump to each next\/previous placeholder.\r\n        4. Press <CR> to fill in a placeholder.\r\n\r\nSnippets are registered as abbreviations.  You can therefore expand them by pressing <Esc> like mere abbreviations.\r\n\r\nPlaceholders can contain default strings.\r\n\r\nThis plugin is well configurable.  You can configure these points.\r\n\r\n        * Map commands to other keys.\r\n        * Use the select mode instead of the visual mode.\r\n        * Change the format of placeholders in general or buffer-local.\r\n\r\nEXAMPLE:\r\n\r\nType like this in the commandline mode.\r\n\r\n        :StringAbbrLocal fputs() \"fputs([~str~], [~fp:stderr~])[~~]\"\r\n\r\nThen type like this in the insert mode.\r\n\r\n        fputs()\r\n\r\nAnd press <S-CR>.\r\n\r\n        fputs([~str~], [~fp:stderr~])[~~]\r\n\r\nThe line is expanded like above and \"[~str~]\" is selected in the visual mode.  \"[~ ... ~]\" is a placeholder.  Each time you press <S-CR>, the cursor jumps to the next placeholder.  Press <C-CR> to jump back to the previous placeholder.\r\n\r\nWhen you press <CR>, the placeholder under the cursor is cut and Vim switches to the insert mode.  So that you can fill in the place.  Pressing <CR> at the second placeholder \"[~fp:stderr~]\", the default string \"stderr\" is inserted.  If you want to insert another word, it can be deleted by pressing <C-U> (see :help i_Ctrl-U).\r\n\r\nThe last empty placeholder \"[~~]\" is not selected by <S-CR>, but simply deleted so that you can insert a semicolon and so on.","install_details":"Extend the zip file to \"%HOME\\vimfiles\\\" (Windows) or \"$HOME\/.vim\/\" (*nix).  Then open \"code-snippet.txt\" with Vim under \"%HOME\\vimfiles\\doc\\\" or \"$HOME\/.vim\/doc\/\", and type \":helptags .\" as an ex command to register help files.\r\n\r\nTo enable loading plugins and indent files for particular file types, it is recomended to add this line to your .vimrc file.\r\n\r\n        filetype plugin indent on\r\n\r\nIt is not required for running this plugin, but necessary for registering snippets for particular file types.  And the setting makes it easy to register multi-line snippets. See \":help filetype\".\r\n\r\nOn most terminal emulators, and some other systems, <S-CR> and <C-CR> of the default key mappings may not work.  In those conditions, You should therefore map the commands to other keys.  See \":help code-snippet-mappings\".\r\n\r\nIt is same as installing other plugins.  See \":help add-plugin\" and \":help add-local-help\" for more information.","5":"Extend the zip file to \"%HOME\\vimfiles\\\" (Windows) or \"$HOME\/.vim\/\" (*nix).  Then open \"code-snippet.txt\" with Vim under \"%HOME\\vimfiles\\doc\\\" or \"$HOME\/.vim\/doc\/\", and type \":helptags .\" as an ex command to register help files.\r\n\r\nTo enable loading plugins and indent files for particular file types, it is recomended to add this line to your .vimrc file.\r\n\r\n        filetype plugin indent on\r\n\r\nIt is not required for running this plugin, but necessary for registering snippets for particular file types.  And the setting makes it easy to register multi-line snippets. See \":help filetype\".\r\n\r\nOn most terminal emulators, and some other systems, <S-CR> and <C-CR> of the default key mappings may not work.  In those conditions, You should therefore map the commands to other keys.  See \":help code-snippet-mappings\".\r\n\r\nIt is same as installing other plugins.  See \":help add-plugin\" and \":help add-local-help\" for more information.","first_name":"Taku","6":"Taku","last_name":"Miyakawa","7":"Miyakawa","releases":[{"0":"2086","vim_version":"7.0","1":"7.0","script_version":"071204a","2":"071204a","version_comment":"* Rewrote the Japanese help file.","3":"* Rewrote the Japanese help file.","package":"code-snippet-2007-12-04a.zip","4":"code-snippet-2007-12-04a.zip","src_id":"8026","5":"8026","creation_date":"1196761221","6":"1196761221"},{"0":"2086","vim_version":"7.0","1":"7.0","script_version":"071204","2":"071204","version_comment":"* Corrected help files.  Placeholders were still written as \"(_ ... _)\".\r\n* Sorry, changed again the default format of placeholders from \"[| ... |]\" to \"[~ ... ~]\".  The format of \"[| ... |]\" causes a trouble in help files.","3":"* Corrected help files.  Placeholders were still written as \"(_ ... _)\".\r\n* Sorry, changed again the default format of placeholders from \"[| ... |]\" to \"[~ ... ~]\".  The format of \"[| ... |]\" causes a trouble in help files.","package":"code-snippet-2007-12-04.zip","4":"code-snippet-2007-12-04.zip","src_id":"8024","5":"8024","creation_date":"1196728211","6":"1196728211"},{"0":"2086","vim_version":"7.0","1":"7.0","script_version":"071203","2":"071203","version_comment":"* Fixed a bug that \"|\" is not escaped to <Bar> in :StringAbbr...\r\n* Changed the default format of placeholders from \"(_ ... _)\" to \"[| ... |]\".","3":"* Fixed a bug that \"|\" is not escaped to <Bar> in :StringAbbr...\r\n* Changed the default format of placeholders from \"(_ ... _)\" to \"[| ... |]\".","package":"code-snippet-2007-12-03.zip","4":"code-snippet-2007-12-03.zip","src_id":"8017","5":"8017","creation_date":"1196632924","6":"1196632924"},{"0":"2086","vim_version":"7.0","1":"7.0","script_version":"071202","2":"071202","version_comment":"Initial upload","3":"Initial upload","package":"code-snippet-2007-12-02.zip","4":"code-snippet-2007-12-02.zip","src_id":"8016","5":"8016","creation_date":"1196575856","6":"1196575856"}]},"2085":{"script_id":"2085","0":"2085","script_name":"TI-Basic Syntax","1":"TI-Basic Syntax","script_type":"syntax","2":"syntax","summary":"Syntax for TI-99\/4+ Basic and Extended Basic","3":"Syntax for TI-99\/4+ Basic and Extended Basic","description":"Syntax file covering TI-BASIC and TI Extended Basic from the TI-99\/4 Extended Basic manual circa 1981.","4":"Syntax file covering TI-BASIC and TI Extended Basic from the TI-99\/4 Extended Basic manual circa 1981.","install_details":"","5":"","first_name":"Tim","6":"Tim","last_name":"Hentenaar","7":"Hentenaar","releases":[{"0":"2085","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"tibasic.vim","4":"tibasic.vim","src_id":"8010","5":"8010","creation_date":"1196459163","6":"1196459163"}]},"2084":{"script_id":"2084","0":"2084","script_name":"gen_vimoptrc.vim","1":"gen_vimoptrc.vim","script_type":"utility","2":"utility","summary":"Generate vim option configuration file from option-window.","3":"Generate vim option configuration file from option-window.","description":"Overview\r\n--------\r\nGenerate \"_vimoptrc\" file that contains your all vim optin settings.\r\nNew command \":GenVimOptrc\", this script added, parse \"option-window\" and\r\ngenerate configuration file to your home directory.\r\nThis script support your easily update configuration file.\r\n\r\nInstallation\r\n------------\r\n1. Copy the autoresize.vim script to the $HOME\/.vim\/plugin or\r\n   the $HOME\/vimfiles\/plugin. Refer to the ':help add-plugin',\r\n   ':help add-global-plugin' and ':help runtimepath' topics for\r\n   more details about Vim plugins.\r\n2. Restart Vim.\r\n\r\nUsage\r\n-----\r\n1. Run \":options\" command.\r\n2. Update your vim options.\r\n3. Run \":GenVimOptrc\" command in \"option-window\",\r\n   this command generate \"_gvimoptrc\" in your $HOME directory.\r\n4. Source \"_gvimoptrc\" in your gvimrc,\r\n   for example\r\n\r\n   :if has(\"gui_running\")\r\n     :source $HOME\/_gvimoptrc\r\n   :endif\r\n\r\nConfiguration\r\n-------------\r\n1. You want use \".gvimoptrc\" instead of \"_gvimoptrc\",\r\n   set your _gvimrc this code.\r\n   \r\n   example.\r\n       :let g:GEN_VIMOPTRC_USE_DOT = 1\r\n\r\nLimitation\r\n----------\r\n1. Currently only GUI version of vim is supported.\r\n\r\nNote\r\n----\r\n1. see also \":help save-settings\".\r\n","4":"Overview\r\n--------\r\nGenerate \"_vimoptrc\" file that contains your all vim optin settings.\r\nNew command \":GenVimOptrc\", this script added, parse \"option-window\" and\r\ngenerate configuration file to your home directory.\r\nThis script support your easily update configuration file.\r\n\r\nInstallation\r\n------------\r\n1. Copy the autoresize.vim script to the $HOME\/.vim\/plugin or\r\n   the $HOME\/vimfiles\/plugin. Refer to the ':help add-plugin',\r\n   ':help add-global-plugin' and ':help runtimepath' topics for\r\n   more details about Vim plugins.\r\n2. Restart Vim.\r\n\r\nUsage\r\n-----\r\n1. Run \":options\" command.\r\n2. Update your vim options.\r\n3. Run \":GenVimOptrc\" command in \"option-window\",\r\n   this command generate \"_gvimoptrc\" in your $HOME directory.\r\n4. Source \"_gvimoptrc\" in your gvimrc,\r\n   for example\r\n\r\n   :if has(\"gui_running\")\r\n     :source $HOME\/_gvimoptrc\r\n   :endif\r\n\r\nConfiguration\r\n-------------\r\n1. You want use \".gvimoptrc\" instead of \"_gvimoptrc\",\r\n   set your _gvimrc this code.\r\n   \r\n   example.\r\n       :let g:GEN_VIMOPTRC_USE_DOT = 1\r\n\r\nLimitation\r\n----------\r\n1. Currently only GUI version of vim is supported.\r\n\r\nNote\r\n----\r\n1. see also \":help save-settings\".\r\n","install_details":"Copy gen_vimoptrc.vim to your plugin directory.","5":"Copy gen_vimoptrc.vim to your plugin directory.","first_name":"omi","6":"omi","last_name":"taku","7":"taku","releases":[{"0":"2084","vim_version":"7.0","1":"7.0","script_version":"0.5","2":"0.5","version_comment":"Initial upload","3":"Initial upload","package":"gen_vimoptrc.vim","4":"gen_vimoptrc.vim","src_id":"8007","5":"8007","creation_date":"1196395717","6":"1196395717"}]},"2083":{"script_id":"2083","0":"2083","script_name":"javascript.vim","1":"javascript.vim","script_type":"syntax","2":"syntax","summary":"powerful javascript syntax","3":"powerful javascript syntax","description":"powerful javascript syntax support color and indent.","4":"powerful javascript syntax support color and indent.","install_details":"","5":"","first_name":"raynm","6":"raynm","last_name":"welshare","7":"welshare","releases":[{"0":"2083","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"javascript.vim","4":"javascript.vim","src_id":"8006","5":"8006","creation_date":"1196382165","6":"1196382165"}]},"2082":{"script_id":"2082","0":"2082","script_name":"comments.vim","1":"comments.vim","script_type":"utility","2":"utility","summary":"Simple, flexible commenting script","3":"Simple, flexible commenting script","description":"This is yet another script to do some code commenting\/uncommenting. It is simple and easy to use, and should work for almost any filetype.\r\n\r\nIt defines a command :CommentStyle which takes one argument, which can be either a comment prefix (\"# \" for shell) or a comment string (\"\/* @ *\/\" for C) with a @ as a placeholder.\r\nIt also defines three mappings: >c to comment, <c to uncomment, and =c to change the CommentStyle.\r\n\r\nNested comments are handled correctly (this means that if you comment the following C code line:\r\nx \/* comment *\/ ++;\r\nthen the inner comment will be protected).","4":"This is yet another script to do some code commenting\/uncommenting. It is simple and easy to use, and should work for almost any filetype.\r\n\r\nIt defines a command :CommentStyle which takes one argument, which can be either a comment prefix (\"# \" for shell) or a comment string (\"\/* @ *\/\" for C) with a @ as a placeholder.\r\nIt also defines three mappings: >c to comment, <c to uncomment, and =c to change the CommentStyle.\r\n\r\nNested comments are handled correctly (this means that if you comment the following C code line:\r\nx \/* comment *\/ ++;\r\nthen the inner comment will be protected).","install_details":"Drop into 'runtimepath' and say :runtime comments.vim .\r\nIncluded are default settings for some filetypes. Add your own if needed.\r\n\r\nThis is an UTF-8 encoded file, but as non-ASCII characters are used only as placeholders, this should cause no problem.","5":"Drop into 'runtimepath' and say :runtime comments.vim .\r\nIncluded are default settings for some filetypes. Add your own if needed.\r\n\r\nThis is an UTF-8 encoded file, but as non-ASCII characters are used only as placeholders, this should cause no problem.","first_name":"J\u00c3\u00a9r\u00c3\u00b4me","6":"J\u00c3\u00a9r\u00c3\u00b4me","last_name":"Pl\u00c3\u00bbt","7":"Pl\u00c3\u00bbt","releases":[{"0":"2082","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"comments.vim","4":"comments.vim","src_id":"8003","5":"8003","creation_date":"1196321018","6":"1196321018"}]},"2081":{"script_id":"2081","0":"2081","script_name":"mysqlquery","1":"mysqlquery","script_type":"utility","2":"utility","summary":"Simple and Easy to use utility for executing MySQL queries","3":"Simple and Easy to use utility for executing MySQL queries","description":"Simple and Easy to use utility for executing MySQL queries.\r\n\r\nWith this script comes only one function ExecMySQL(), so you need to bind a key to this function, for executing queries. For example:\r\n\r\n:vmap <F9> :call ExecMySQL()<CR>\r\n:nmap <F9> V:call ExecMySQL()<CR>\r\n\r\nAfter that you need to write a SQL query, then select it (or if query consist only of one line, point cursor to it) ant press <F9>.\r\n\r\nQuery will be executed and in new buffer you will see result of that query. Results are shown in beautifully aligned table.\r\n\r\nBest way to work with this plug-in is separate file for queries. At the beginning of that file, in one of 10 first lines you need to add connection string:\r\n\r\n -- mysql:\/\/username:password@hostname\/dbname\r\n\r\nYou can add many connection strings, but only first found string will be used. So if you want to change database, just move connection string at the very top of file.\r\n\r\n\r\nAlso I suggesting you to use this mapping for better usage:\r\n\r\nmap <F5> :b#<CR>\r\n\r\nWith this mapping, after executing a query, you can easily switch back to query editing, just by pressing <F5>.","4":"Simple and Easy to use utility for executing MySQL queries.\r\n\r\nWith this script comes only one function ExecMySQL(), so you need to bind a key to this function, for executing queries. For example:\r\n\r\n:vmap <F9> :call ExecMySQL()<CR>\r\n:nmap <F9> V:call ExecMySQL()<CR>\r\n\r\nAfter that you need to write a SQL query, then select it (or if query consist only of one line, point cursor to it) ant press <F9>.\r\n\r\nQuery will be executed and in new buffer you will see result of that query. Results are shown in beautifully aligned table.\r\n\r\nBest way to work with this plug-in is separate file for queries. At the beginning of that file, in one of 10 first lines you need to add connection string:\r\n\r\n -- mysql:\/\/username:password@hostname\/dbname\r\n\r\nYou can add many connection strings, but only first found string will be used. So if you want to change database, just move connection string at the very top of file.\r\n\r\n\r\nAlso I suggesting you to use this mapping for better usage:\r\n\r\nmap <F5> :b#<CR>\r\n\r\nWith this mapping, after executing a query, you can easily switch back to query editing, just by pressing <F5>.","install_details":"Simply copy this script to your vim plugins directory:\r\n\r\nwget http:\/\/www.vim.org\/scripts\/download_script.php?src_id=8122 -O ~\/.vim\/plugin\/mysqlquery.vim\r\n\r\nNote, that this script requires elinks, so before using, apt-get it.","5":"Simply copy this script to your vim plugins directory:\r\n\r\nwget http:\/\/www.vim.org\/scripts\/download_script.php?src_id=8122 -O ~\/.vim\/plugin\/mysqlquery.vim\r\n\r\nNote, that this script requires elinks, so before using, apt-get it.","first_name":"Mantas","6":"Mantas","last_name":"Zimnickas","7":"Zimnickas","releases":[{"0":"2081","vim_version":"7.0","1":"7.0","script_version":"0.2","2":"0.2","version_comment":"- Improved error handling.\r\n- Added possibility to add connection string to beginning of the file, where all query's are executing.","3":"- Improved error handling.\r\n- Added possibility to add connection string to beginning of the file, where all query's are executing.","package":"vimpydb.vim","4":"vimpydb.vim","src_id":"8122","5":"8122","creation_date":"1199449144","6":"1199449144"},{"0":"2081","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"mysqlquery.vim","4":"mysqlquery.vim","src_id":"8002","5":"8002","creation_date":"1196320872","6":"1196320872"}]},"2080":{"script_id":"2080","0":"2080","script_name":"autoresize.vim","1":"autoresize.vim","script_type":"utility","2":"utility","summary":"Automatically Resizing Splitted Current Window Size Larger.","3":"Automatically Resizing Splitted Current Window Size Larger.","description":"Overview\r\n--------\r\nThis plugin updates vim splitted window size automatically large.\r\nCurrent window size will be large, and the other window size will be\r\nsmall.\r\n\r\nInstallation\r\n------------\r\n1. Copy the autoresize.vim script to the $HOME\/.vim\/plugin or\r\n   the $HOME\/vimfiles\/plugin. Refer to the ':help add-plugin',\r\n   ':help add-global-plugin' and ':help runtimepath' topics for\r\n   more details about Vim plugins.\r\n2. Restart Vim.\r\n\r\nUsage\r\n-----\r\n1. Split vim window, and so current window height or width is automatically\r\n   updated with large value. \r\n2. You move cursor to the other window from one, the other window size is\r\n   automatically updated.\r\n3. If you check this script,\r\n   split vim window with \":split\" or \":vsplit\",\r\n   and push <C-W><C-W><C-W><C-W><C-W><C-W>....\r\n\r\nConfiguration\r\n-------------\r\n1. Minimum window size.\r\n   Script use \"g:AUTORESIZE_ANOTHER_WINDOW_HEIGHT\" variables when you split window\r\n   horizontally.  If you split window vertically then, script use\r\n   \"g:AUTORESIZE_ANOTHER_WINDOW_WIDTH\" variables.\r\n   These variables are used as the other window size parameter. (not a current)\r\n\r\n   example.\r\n       :let g:AUTORESIZE_ANOTHER_WINDOW_HEIGHT = 5\r\n       :let g:AUTORESIZE_ANOTHER_WINDOW_WIDTH = 12\r\n\r\n2. Disable script defined autocommands.\r\n   Script add 1 autocommand to your vim environment.\r\n   If you want make this autocommand disable,\r\n   set \"g:AUTORESIZE_AUTOCMD_DISABLE\" variables to \"1\".\r\n\r\n   example.\r\n       :let g:AUTORESIZE_AUTOCMD_DISABLE = 1\r\n\r\n3. Run autocommand in specific filetype.\r\n   If you use this script only in some filetype, add this autocommand to your vimrc.\r\n\r\n   example.\r\n       :let g:AUTORESIZE_AUTOCMD_DISABLE = 1\r\n       :autocmd WinEnter *.txt :AutoWindowResize\r\n\r\n4. Run script on your action\r\n   If you run this script with some your action (for example, push F4),\r\n   add this configuration to your vimrc.\r\n\r\n   example.\r\n       :let g:AUTORESIZE_AUTOCMD_DISABLE = 1\r\n       :nmap <F4> :AutoWindowResize<CR>\r\n\r\nLimitation\r\n----------\r\n1. This script will run only on 2 window. Vim run on 3 splitted window,\r\n   on 4 splitted window, or on 1 window then, this script is not running.\r\n","4":"Overview\r\n--------\r\nThis plugin updates vim splitted window size automatically large.\r\nCurrent window size will be large, and the other window size will be\r\nsmall.\r\n\r\nInstallation\r\n------------\r\n1. Copy the autoresize.vim script to the $HOME\/.vim\/plugin or\r\n   the $HOME\/vimfiles\/plugin. Refer to the ':help add-plugin',\r\n   ':help add-global-plugin' and ':help runtimepath' topics for\r\n   more details about Vim plugins.\r\n2. Restart Vim.\r\n\r\nUsage\r\n-----\r\n1. Split vim window, and so current window height or width is automatically\r\n   updated with large value. \r\n2. You move cursor to the other window from one, the other window size is\r\n   automatically updated.\r\n3. If you check this script,\r\n   split vim window with \":split\" or \":vsplit\",\r\n   and push <C-W><C-W><C-W><C-W><C-W><C-W>....\r\n\r\nConfiguration\r\n-------------\r\n1. Minimum window size.\r\n   Script use \"g:AUTORESIZE_ANOTHER_WINDOW_HEIGHT\" variables when you split window\r\n   horizontally.  If you split window vertically then, script use\r\n   \"g:AUTORESIZE_ANOTHER_WINDOW_WIDTH\" variables.\r\n   These variables are used as the other window size parameter. (not a current)\r\n\r\n   example.\r\n       :let g:AUTORESIZE_ANOTHER_WINDOW_HEIGHT = 5\r\n       :let g:AUTORESIZE_ANOTHER_WINDOW_WIDTH = 12\r\n\r\n2. Disable script defined autocommands.\r\n   Script add 1 autocommand to your vim environment.\r\n   If you want make this autocommand disable,\r\n   set \"g:AUTORESIZE_AUTOCMD_DISABLE\" variables to \"1\".\r\n\r\n   example.\r\n       :let g:AUTORESIZE_AUTOCMD_DISABLE = 1\r\n\r\n3. Run autocommand in specific filetype.\r\n   If you use this script only in some filetype, add this autocommand to your vimrc.\r\n\r\n   example.\r\n       :let g:AUTORESIZE_AUTOCMD_DISABLE = 1\r\n       :autocmd WinEnter *.txt :AutoWindowResize\r\n\r\n4. Run script on your action\r\n   If you run this script with some your action (for example, push F4),\r\n   add this configuration to your vimrc.\r\n\r\n   example.\r\n       :let g:AUTORESIZE_AUTOCMD_DISABLE = 1\r\n       :nmap <F4> :AutoWindowResize<CR>\r\n\r\nLimitation\r\n----------\r\n1. This script will run only on 2 window. Vim run on 3 splitted window,\r\n   on 4 splitted window, or on 1 window then, this script is not running.\r\n","install_details":"Copy autoresize.vim to your plugin directory.","5":"Copy autoresize.vim to your plugin directory.","first_name":"omi","6":"omi","last_name":"taku","7":"taku","releases":[{"0":"2080","vim_version":"7.0","1":"7.0","script_version":"0.7","2":"0.7","version_comment":"Initial upload","3":"Initial upload","package":"autoresize.vim","4":"autoresize.vim","src_id":"8001","5":"8001","creation_date":"1196313551","6":"1196313551"}]},"2079":{"script_id":"2079","0":"2079","script_name":"Coq indent","1":"Coq indent","script_type":"indent","2":"indent","summary":"Indentation for coq files","3":"Indentation for coq files","description":"Pretty clear, no ?","4":"Pretty clear, no ?","install_details":"Put the file in the directory ~\/.vim\/indent\/\r\n\r\nIf not already done, follow step 2 of install at http:\/\/www.vim.org\/scripts\/script.php?script_id=2063.\r\n\r\nAlso, if not already done, add the line:\r\n:filetype indent on\r\nto your .vimrc file\r\n\r\n","5":"Put the file in the directory ~\/.vim\/indent\/\r\n\r\nIf not already done, follow step 2 of install at http:\/\/www.vim.org\/scripts\/script.php?script_id=2063.\r\n\r\nAlso, if not already done, add the line:\r\n:filetype indent on\r\nto your .vimrc file\r\n\r\n","first_name":"Vincent","6":"Vincent","last_name":"Aravantinos","7":"Aravantinos","releases":[{"0":"2079","vim_version":"7.0","1":"7.0","script_version":"0.3","2":"0.3","version_comment":"Bugfix inside proofs.","3":"Bugfix inside proofs.","package":"coq.vim","4":"coq.vim","src_id":"8013","5":"8013","creation_date":"1196529760","6":"1196529760"},{"0":"2079","vim_version":"7.0","1":"7.0","script_version":"0.2","2":"0.2","version_comment":"Handle proofs that do not start with 'Proof' - REQUIRES VERSION 1.3.5 OR MORE OF THE PLUGIN COQ SYNTAX (http:\/\/www.vim.org\/scripts\/script.php?script_id=2063)","3":"Handle proofs that do not start with 'Proof' - REQUIRES VERSION 1.3.5 OR MORE OF THE PLUGIN COQ SYNTAX (http:\/\/www.vim.org\/scripts\/script.php?script_id=2063)","package":"coq.vim","4":"coq.vim","src_id":"7999","5":"7999","creation_date":"1196221801","6":"1196221801"},{"0":"2079","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"coq.vim","4":"coq.vim","src_id":"7997","5":"7997","creation_date":"1196178987","6":"1196178987"}]},"2078":{"script_id":"2078","0":"2078","script_name":"industrial","1":"industrial","script_type":"color scheme","2":"color scheme","summary":"A Darkgrey with blue and green colorscheme.","3":"A Darkgrey with blue and green colorscheme.","description":"I took the colorscheme \"jocafa\" and edited the colors.\r\n\r\nIt has a darkgrey background with blue and green highlights.\r\n\r\nSearch highlights are yellow.\r\n\r\nscreenshot: http:\/\/img182.imageshack.us\/img182\/9925\/gvimindustrial10pn6.png","4":"I took the colorscheme \"jocafa\" and edited the colors.\r\n\r\nIt has a darkgrey background with blue and green highlights.\r\n\r\nSearch highlights are yellow.\r\n\r\nscreenshot: http:\/\/img182.imageshack.us\/img182\/9925\/gvimindustrial10pn6.png","install_details":"drop it in ~\/.vim\/colors\/ or $VIM\/vimfiles\/colors\/ depending on your OS.\r\n\r\n:colorscheme industrial","5":"drop it in ~\/.vim\/colors\/ or $VIM\/vimfiles\/colors\/ depending on your OS.\r\n\r\n:colorscheme industrial","first_name":"Tom","6":"Tom","last_name":"Wieland","7":"Wieland","releases":[{"0":"2078","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"industrial.vim","4":"industrial.vim","src_id":"7993","5":"7993","creation_date":"1196094594","6":"1196094594"}]},"2077":{"script_id":"2077","0":"2077","script_name":"phtml.vim","1":"phtml.vim","script_type":"syntax","2":"syntax","summary":"A syntax file to php templates.","3":"A syntax file to php templates.","description":"Use this script to enable syntax coloring when using a mix of html and php or with template engines like those used by CakePHP, Symfony, SolarPHP and others\r\n\r\nTo use xmledit (vimscript #301) with phtml files change line 105 to:\r\n\r\nif &filetype == 'xml' || (!exists (\"g:did_xhtmlcf_inits\") && exists (\"g:xml_use_xhtml\") && (&filetype == 'html' || &filetype == 'xhtml' || &filetype == 'php' || &filetype == 'phtml' || &filetype == 'rhtml'))\r\n\r\nAnd line 168 to:\r\n\r\nif (&filetype == 'html' || &filetype == 'php' || &filetype == 'phtml') && (!exists (\"g:xml_no_html\"))\r\n\r\nAnd symlink:\r\n\r\ncd $HOME\/.vim\/ftplugin\r\nln -s xml.vim phtml.vim","4":"Use this script to enable syntax coloring when using a mix of html and php or with template engines like those used by CakePHP, Symfony, SolarPHP and others\r\n\r\nTo use xmledit (vimscript #301) with phtml files change line 105 to:\r\n\r\nif &filetype == 'xml' || (!exists (\"g:did_xhtmlcf_inits\") && exists (\"g:xml_use_xhtml\") && (&filetype == 'html' || &filetype == 'xhtml' || &filetype == 'php' || &filetype == 'phtml' || &filetype == 'rhtml'))\r\n\r\nAnd line 168 to:\r\n\r\nif (&filetype == 'html' || &filetype == 'php' || &filetype == 'phtml') && (!exists (\"g:xml_no_html\"))\r\n\r\nAnd symlink:\r\n\r\ncd $HOME\/.vim\/ftplugin\r\nln -s xml.vim phtml.vim","install_details":"Just drop into .vim\/syntax\r\n\r\nTo enable a better identation symlink the default html.vim to phtml.vim:\r\n\r\nln -s $VIMRUNTIME\/indent\/html.vim $HOME\/.vim\/indent\/phtml.vim","5":"Just drop into .vim\/syntax\r\n\r\nTo enable a better identation symlink the default html.vim to phtml.vim:\r\n\r\nln -s $VIMRUNTIME\/indent\/html.vim $HOME\/.vim\/indent\/phtml.vim","first_name":"Giuliani","6":"Giuliani","last_name":"Sanches","7":"Sanches","releases":[{"0":"2077","vim_version":"7.0","1":"7.0","script_version":"0.1.2","2":"0.1.2","version_comment":"Changed name to phtml.\r\nNow the script will override the defaul phtml file (wich has some issues) and can be used with any template using php as script language.","3":"Changed name to phtml.\r\nNow the script will override the defaul phtml file (wich has some issues) and can be used with any template using php as script language.","package":"phtml.vim","4":"phtml.vim","src_id":"7972","5":"7972","creation_date":"1195566153","6":"1195566153"},{"0":"2077","vim_version":"6.0","1":"6.0","script_version":"0.1.1","2":"0.1.1","version_comment":"This script was based on mako.vim by Armin Ronacher. So.. credits added ;)","3":"This script was based on mako.vim by Armin Ronacher. So.. credits added ;)","package":"solar.vim","4":"solar.vim","src_id":"7968","5":"7968","creation_date":"1195482788","6":"1195482788"},{"0":"2077","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"solar.vim","4":"solar.vim","src_id":"7967","5":"7967","creation_date":"1195482518","6":"1195482518"}]},"2076":{"script_id":"2076","0":"2076","script_name":"setsyntax","1":"setsyntax","script_type":"utility","2":"utility","summary":"Set options specific for the syntax group under cursor","3":"Set options specific for the syntax group under cursor","description":"This plugin sets options\/variables according to the syntax under the \r\ncursor. It was originally created in response to \r\nhttp:\/\/groups.google.com\/group\/vim_use\/browse_frm\/thread\/ff624d5a68f0a562 \r\nand to solve a similar problem. While this plugin solves that other \r\nrelated problem it doesn't seem to work properly for tex files.\r\n\r\nConfiguration:\r\n\r\ng:setsyntax_options            (default: {})\r\n    This variable is a dictionary of dictionaries of dictionaries.\r\n    {FILETYPE => {SYNREGEXP => {OPTION\/VARIABLE: VALUE}}}\r\n    \r\n    Example:\r\n      let g:setsyntax_options['tex'] = {'^texMathZone': {'&l:tw': 0}}\r\n\r\n\r\n:SetSyntax SYNTAX,... VAR VALUE ...\r\n:SetSyntax \/REGEXP\/ VAR VALUE ...\r\n    Set syntax-specific options for the current buffer. When using a \r\n    REGEXP, the syntax names have to be already defined, i.e. you can use \r\n    the REGEXP only after the syntax file was loaded.\r\n    \r\n    VAR must be a variable name (see |:let| and |:let-&| for details). \r\n    I.e., if you want to set a option, e.g. spelllang, don't use\r\n\r\n        SetSyntax \/^texMath\/ spelllang \"\"\r\n\r\n    but instead use:\r\n\r\n      SetSyntax \/^texMath\/ &l:spelllang \"\"\r\n    \r\n    VALUE actually is an expression that will be evaluated when setting \r\n    the variable.\r\n    \r\n    NOTE: Blanks in VALUE must be escaped with a backslash. See the help \r\n    page on <f-args> for details.\r\n\r\n","4":"This plugin sets options\/variables according to the syntax under the \r\ncursor. It was originally created in response to \r\nhttp:\/\/groups.google.com\/group\/vim_use\/browse_frm\/thread\/ff624d5a68f0a562 \r\nand to solve a similar problem. While this plugin solves that other \r\nrelated problem it doesn't seem to work properly for tex files.\r\n\r\nConfiguration:\r\n\r\ng:setsyntax_options            (default: {})\r\n    This variable is a dictionary of dictionaries of dictionaries.\r\n    {FILETYPE => {SYNREGEXP => {OPTION\/VARIABLE: VALUE}}}\r\n    \r\n    Example:\r\n      let g:setsyntax_options['tex'] = {'^texMathZone': {'&l:tw': 0}}\r\n\r\n\r\n:SetSyntax SYNTAX,... VAR VALUE ...\r\n:SetSyntax \/REGEXP\/ VAR VALUE ...\r\n    Set syntax-specific options for the current buffer. When using a \r\n    REGEXP, the syntax names have to be already defined, i.e. you can use \r\n    the REGEXP only after the syntax file was loaded.\r\n    \r\n    VAR must be a variable name (see |:let| and |:let-&| for details). \r\n    I.e., if you want to set a option, e.g. spelllang, don't use\r\n\r\n        SetSyntax \/^texMath\/ spelllang \"\"\r\n\r\n    but instead use:\r\n\r\n      SetSyntax \/^texMath\/ &l:spelllang \"\"\r\n    \r\n    VALUE actually is an expression that will be evaluated when setting \r\n    the variable.\r\n    \r\n    NOTE: Blanks in VALUE must be escaped with a backslash. See the help \r\n    page on <f-args> for details.\r\n\r\n","install_details":"Edit the vba file and type: >\r\n\r\n    :so %\r\n\r\nSee :help vimball for details. If you have difficulties or use vim 7.0, \r\nplease make sure, you have the current version of vimball (vimscript \r\n#1502) installed.\r\n\r\nThis script requires hookcursormoved (vimscript #2037) and tlib \r\n(vimscript #1863) to be installed.\r\n\r\n\r\nAlso available via git\r\nhttp:\/\/github.com\/tomtom\/setsyntax_vim","5":"Edit the vba file and type: >\r\n\r\n    :so %\r\n\r\nSee :help vimball for details. If you have difficulties or use vim 7.0, \r\nplease make sure, you have the current version of vimball (vimscript \r\n#1502) installed.\r\n\r\nThis script requires hookcursormoved (vimscript #2037) and tlib \r\n(vimscript #1863) to be installed.\r\n\r\n\r\nAlso available via git\r\nhttp:\/\/github.com\/tomtom\/setsyntax_vim","first_name":"Tom","6":"Tom","last_name":"Link","7":"Link","releases":[{"0":"2076","vim_version":"7.0","1":"7.0","script_version":"0.3","2":"0.3","version_comment":"- SetSyntax command\r\n- Require tlib >= 0.21, hookcursormoved >= 0.7\r\n- Look-up should be slightly faster now\r\n","3":"- SetSyntax command\r\n- Require tlib >= 0.21, hookcursormoved >= 0.7\r\n- Look-up should be slightly faster now\r\n","package":"setsyntax.vba.gz","4":"setsyntax.vba.gz","src_id":"7980","5":"7980","creation_date":"1195642802","6":"1195642802"},{"0":"2076","vim_version":"7.0","1":"7.0","script_version":"0.2","2":"0.2","version_comment":"- Defined viki regions","3":"- Defined viki regions","package":"setsyntax.vba.gz","4":"setsyntax.vba.gz","src_id":"7964","5":"7964","creation_date":"1195374671","6":"1195374671"},{"0":"2076","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"setsyntax.vba.gz","4":"setsyntax.vba.gz","src_id":"7962","5":"7962","creation_date":"1195372385","6":"1195372385"}]},"2075":{"script_id":"2075","0":"2075","script_name":"indent\/html.vim","1":"indent\/html.vim","script_type":"indent","2":"indent","summary":"alternative html indent script","3":"alternative html indent script","description":"This script is based on the distributed indent scripts for HTML (and CSS).  The original script becomes very slow when indenting more than a few lines, thus here is an improvement.\r\n\r\n\r\nCustomization:  Variables you can set in the vimrc.  Given values are examples to change the defaults.\r\n\r\n  Note: This applies to v0.6 (!).  Earlier version used :IndHtmlLocal for customization.  Details can always be found in the script header.\r\n\r\n  You can set the indent for the first line after <script> and <style> \"block tags\" (default \"zero\"):\r\n\r\n      :let g:html_indent_script1 = \"inc\"\r\n      :let g:html_indent_style1 = \"inc\"\r\n\r\n      VALUE\tMEANING\r\n      \"zero\"\tzero indent\r\n      \"auto\"\tauto indent (same indent as the blocktag)\r\n      \"inc\"\tauto indent + one indent step\r\n\r\n  The following <tags> increase the indent (for what follows) per default (taken from the original script, but slightly modified):\r\n      a, abbr, acronym, address, b, bdo, big, blockquote, button, caption, center, cite, code, colgroup, del, dfn, dir, div, dl, em, fieldset, font, form, frameset, h1, h2, h3, h4, h5, h6, i, iframe, ins, kbd, label, legend, map, menu, noframes, noscript, object, ol, optgroup, q, s, samp, select, small, span, strong, sub, sup, table, textarea, title, tt, u, ul, var, th, td, tr, tfoot, thead\r\n      (added with v0.8): area, article, aside, audio, bdi, canvas, command, datalist, details, embed, figure, footer, header, group, keygen, mark, math, meter, nav, output, progress, ruby, section, svg, texture, time, video, wbr, text\r\n\r\n  You can add further tags with\r\n\r\n      :let g:html_indent_inctags = \"html,body,head,tbody\"\r\n\r\n      \" the original script uses the g:html_indent_strict variable to include these tags\r\n\r\n  You can remove tags with\r\n\r\n      :let g:html_indent_autotags = \"th,td,tr,tfoot,thead\"\r\n\r\n      \" the original script uses the g:html_indent_strict_table variable to include these tags\r\n\r\n  Default value is empty for both variables.  The default tags that increase indent are defined once per session only.\r\n\r\n\r\nProblems and Bugs:\r\n\r\n  - still no indent rules for attributes spanning several lines\r\n  - sometimes cindent() thinks it is better to use zero indent for what follows ...\r\n  - some tags increase indent per default, but their closing tag is optional, e.g. <td> -- the script cannot detect missing closing tags\r\n\r\nSuggestions, bug reports welcome (I'm not writing HTML regularly).\r\n\r\n2014 Jul 04: Vim 7.4.356 or later includes a descendant of this script (the official script is now maintained by Bram and includes massive changes)\r\n2013 Jun 13: Vim 7.3.1180 or later includes the latest version of this script.","4":"This script is based on the distributed indent scripts for HTML (and CSS).  The original script becomes very slow when indenting more than a few lines, thus here is an improvement.\r\n\r\n\r\nCustomization:  Variables you can set in the vimrc.  Given values are examples to change the defaults.\r\n\r\n  Note: This applies to v0.6 (!).  Earlier version used :IndHtmlLocal for customization.  Details can always be found in the script header.\r\n\r\n  You can set the indent for the first line after <script> and <style> \"block tags\" (default \"zero\"):\r\n\r\n      :let g:html_indent_script1 = \"inc\"\r\n      :let g:html_indent_style1 = \"inc\"\r\n\r\n      VALUE\tMEANING\r\n      \"zero\"\tzero indent\r\n      \"auto\"\tauto indent (same indent as the blocktag)\r\n      \"inc\"\tauto indent + one indent step\r\n\r\n  The following <tags> increase the indent (for what follows) per default (taken from the original script, but slightly modified):\r\n      a, abbr, acronym, address, b, bdo, big, blockquote, button, caption, center, cite, code, colgroup, del, dfn, dir, div, dl, em, fieldset, font, form, frameset, h1, h2, h3, h4, h5, h6, i, iframe, ins, kbd, label, legend, map, menu, noframes, noscript, object, ol, optgroup, q, s, samp, select, small, span, strong, sub, sup, table, textarea, title, tt, u, ul, var, th, td, tr, tfoot, thead\r\n      (added with v0.8): area, article, aside, audio, bdi, canvas, command, datalist, details, embed, figure, footer, header, group, keygen, mark, math, meter, nav, output, progress, ruby, section, svg, texture, time, video, wbr, text\r\n\r\n  You can add further tags with\r\n\r\n      :let g:html_indent_inctags = \"html,body,head,tbody\"\r\n\r\n      \" the original script uses the g:html_indent_strict variable to include these tags\r\n\r\n  You can remove tags with\r\n\r\n      :let g:html_indent_autotags = \"th,td,tr,tfoot,thead\"\r\n\r\n      \" the original script uses the g:html_indent_strict_table variable to include these tags\r\n\r\n  Default value is empty for both variables.  The default tags that increase indent are defined once per session only.\r\n\r\n\r\nProblems and Bugs:\r\n\r\n  - still no indent rules for attributes spanning several lines\r\n  - sometimes cindent() thinks it is better to use zero indent for what follows ...\r\n  - some tags increase indent per default, but their closing tag is optional, e.g. <td> -- the script cannot detect missing closing tags\r\n\r\nSuggestions, bug reports welcome (I'm not writing HTML regularly).\r\n\r\n2014 Jul 04: Vim 7.4.356 or later includes a descendant of this script (the official script is now maintained by Bram and includes massive changes)\r\n2013 Jun 13: Vim 7.3.1180 or later includes the latest version of this script.","install_details":"Unix: copy script to ~\/.vim\/indent\r\nWin: copy script to ~\\vimfiles\\indent\r\n\r\nEnable filetype detection and use of indent plugins:\r\n    :filetype indent on","5":"Unix: copy script to ~\/.vim\/indent\r\nWin: copy script to ~\\vimfiles\\indent\r\n\r\nEnable filetype detection and use of indent plugins:\r\n    :filetype indent on","first_name":"Andy","6":"Andy","last_name":"Wokula","7":"Wokula","releases":[{"0":"2075","vim_version":"7.0","1":"7.0","script_version":"0.10","2":"0.10","version_comment":"added b:html_indent_usestate; and a bug fix","3":"added b:html_indent_usestate; and a bug fix","package":"html.vim","4":"html.vim","src_id":"21389","5":"21389","creation_date":"1390852132","6":"1390852132"},{"0":"2075","vim_version":"7.0","1":"7.0","script_version":"0.8","2":"0.8","version_comment":"added HTML5 tags (thx to J. Zuckerman)","3":"added HTML5 tags (thx to J. Zuckerman)","package":"html.vim","4":"html.vim","src_id":"16508","5":"16508","creation_date":"1315776241","6":"1315776241"},{"0":"2075","vim_version":"7.0","1":"7.0","script_version":"0.6","2":"0.6","version_comment":"customization revised, no other changes","3":"customization revised, no other changes","package":"html.vim","4":"html.vim","src_id":"8614","5":"8614","creation_date":"1209386390","6":"1209386390"},{"0":"2075","vim_version":"7.0","1":"7.0","script_version":"0.5","2":"0.5","version_comment":"Fixed: 'indk' when breaking a line with Enter (e.g. given the line \"<div><center><\/center>\", inserting Enter after \"<center>\" now adds an indent for the new line)\r\nChange: line must start with a closing tag (old: any tag) to get same indent as the starting tag","3":"Fixed: 'indk' when breaking a line with Enter (e.g. given the line \"<div><center><\/center>\", inserting Enter after \"<center>\" now adds an indent for the new line)\r\nChange: line must start with a closing tag (old: any tag) to get same indent as the starting tag","package":"html.vim","4":"html.vim","src_id":"8428","5":"8428","creation_date":"1205070615","6":"1205070615"},{"0":"2075","vim_version":"7.0","1":"7.0","script_version":"0.4","2":"0.4","version_comment":"Added: configurable indent for the first line after <script> or <style>","3":"Added: configurable indent for the first line after <script> or <style>","package":"html.vim","4":"html.vim","src_id":"7982","5":"7982","creation_date":"1195657134","6":"1195657134"},{"0":"2075","vim_version":"7.0","1":"7.0","script_version":"0.3.2","2":"0.3.2","version_comment":"Another dumb bug fixed: didn't match tag names with digits (h1-h6)\r\ngoody: simple arg-completion for IndHtmlLocal","3":"Another dumb bug fixed: didn't match tag names with digits (h1-h6)\r\ngoody: simple arg-completion for IndHtmlLocal","package":"html.vim","4":"html.vim","src_id":"7977","5":"7977","creation_date":"1195630149","6":"1195630149"},{"0":"2075","vim_version":"7.0","1":"7.0","script_version":"0.3.1","2":"0.3.1","version_comment":"Bugfix: didn't detect \"-->\" as end of region","3":"Bugfix: didn't detect \"-->\" as end of region","package":"html.vim","4":"html.vim","src_id":"7974","5":"7974","creation_date":"1195578432","6":"1195578432"},{"0":"2075","vim_version":"7.0","1":"7.0","script_version":"0.3","2":"0.3","version_comment":"now indents <style> regions","3":"now indents <style> regions","package":"html.vim","4":"html.vim","src_id":"7970","5":"7970","creation_date":"1195494453","6":"1195494453"},{"0":"2075","vim_version":"7.0","1":"7.0","script_version":"0.2","2":"0.2","version_comment":"Initial upload","3":"Initial upload","package":"html.vim","4":"html.vim","src_id":"7961","5":"7961","creation_date":"1195369382","6":"1195369382"}]},"2074":{"script_id":"2074","0":"2074","script_name":"rcg_term","1":"rcg_term","script_type":"color scheme","2":"color scheme","summary":"A dark background color scheme for Terminal","3":"A dark background color scheme for Terminal","description":"A simple dark background color scheme for Vim.","4":"A simple dark background color scheme for Vim.","install_details":"Put this file in your vim color directory (e.g. ~\/.vim\/colors). \r\n\r\nAdd lines below to your .vimrc file: \r\nif !has(\"gui_running\") \r\n  colorscheme rcg_term\r\nendif","5":"Put this file in your vim color directory (e.g. ~\/.vim\/colors). \r\n\r\nAdd lines below to your .vimrc file: \r\nif !has(\"gui_running\") \r\n  colorscheme rcg_term\r\nendif","first_name":"Rui Carlos","6":"Rui Carlos","last_name":"Gon\u00c3\u00a7alves","7":"Gon\u00c3\u00a7alves","releases":[{"0":"2074","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload.","3":"Initial upload.","package":"rcg_term.vim","4":"rcg_term.vim","src_id":"11132","5":"11132","creation_date":"1249484691","6":"1249484691"}]},"2073":{"script_id":"2073","0":"2073","script_name":"rcg_gui","1":"rcg_gui","script_type":"color scheme","2":"color scheme","summary":"A dark background color scheme for GUI","3":"A dark background color scheme for GUI","description":"A simple dark background color scheme for GUI","4":"A simple dark background color scheme for GUI","install_details":"Put this file in your vim color directory (e.g. ~\/.vim\/colors).\r\n\r\nAdd lines below to your .vimrc file:\r\nif has(\"gui_running\")\r\n  colorscheme rcg_gui\r\nendif","5":"Put this file in your vim color directory (e.g. ~\/.vim\/colors).\r\n\r\nAdd lines below to your .vimrc file:\r\nif has(\"gui_running\")\r\n  colorscheme rcg_gui\r\nendif","first_name":"Rui Carlos","6":"Rui Carlos","last_name":"Gon\u00c3\u00a7alves","7":"Gon\u00c3\u00a7alves","releases":[{"0":"2073","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload.","3":"Initial upload.","package":"rcg_gui.vim","4":"rcg_gui.vim","src_id":"11131","5":"11131","creation_date":"1249484623","6":"1249484623"}]},"2072":{"script_id":"2072","0":"2072","script_name":"switch files","1":"switch files","script_type":"utility","2":"utility","summary":"switch between .c and .h files or different path and same filename easily","3":"switch between .c and .h files or different path and same filename easily","description":"Call \r\nfunction! vl#lib#files#switch_files#SwitchFileUI()\r\n  map <m-s><m-b> :call vl#lib#files#switch_files#SwitchFile()<cr>\r\nendfunction\r\nsomewhere to get the default mapping.\r\n\r\nThen use lines like this\r\ncall vl#lib#files#switch_files#SwitchFileRegisterLocalRegexSwap('.h$', ['.cpp', '.cc' ])\r\nautocmd BufRead,BufNewFile \/pr\/*nix,\/pr\/*nix\/*.sh call vl#lib#files#switch_files#SwitchFileRegisterLocalRegexSwap('\/pr\/mynix\/','\/pr\/svnnix\/')\r\n\r\nfor each buffer to tell the script how to find alternates.\r\n\r\nThere is also some support to add custom functions. Drop me an email if you want to know more","4":"Call \r\nfunction! vl#lib#files#switch_files#SwitchFileUI()\r\n  map <m-s><m-b> :call vl#lib#files#switch_files#SwitchFile()<cr>\r\nendfunction\r\nsomewhere to get the default mapping.\r\n\r\nThen use lines like this\r\ncall vl#lib#files#switch_files#SwitchFileRegisterLocalRegexSwap('.h$', ['.cpp', '.cc' ])\r\nautocmd BufRead,BufNewFile \/pr\/*nix,\/pr\/*nix\/*.sh call vl#lib#files#switch_files#SwitchFileRegisterLocalRegexSwap('\/pr\/mynix\/','\/pr\/svnnix\/')\r\n\r\nfor each buffer to tell the script how to find alternates.\r\n\r\nThere is also some support to add custom functions. Drop me an email if you want to know more","install_details":"Just source the file and follow the instructions. \r\nYou'll be asked before any action is taken. \r\n\r\nIf you don't feel comfortable installing to .vim insntall to another arbitrary directory and add it to your runtimepath \r\n(let runtimepath+= ..)","5":"Just source the file and follow the instructions. \r\nYou'll be asked before any action is taken. \r\n\r\nIf you don't feel comfortable installing to .vim insntall to another arbitrary directory and add it to your runtimepath \r\n(let runtimepath+= ..)","first_name":"Marc","6":"Marc","last_name":"Weber","7":"Weber","releases":[{"0":"2072","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"vimlib_switch_File_support_installer_sourceme.zip","4":"vimlib_switch_File_support_installer_sourceme.zip","src_id":"7956","5":"7956","creation_date":"1195225457","6":"1195225457"}]},"2071":{"script_id":"2071","0":"2071","script_name":"yet another svn script","1":"yet another svn script","script_type":"utility","2":"utility","summary":"makes svn add \/commit much easier from vim","3":"makes svn add \/commit much easier from vim","description":"Probably you want to try http:\/\/www.vim.org\/scripts\/script.php?script_id=90 instead. It's much more powerful\r\n\r\nDefault mapping are provided by\r\n\r\nvl#dev#versioncontrolsystem#manager#VCSUI()\r\n(and see the tagging UI function below)\r\n\r\nEg when committing you'll get a new window like this:\r\n=============  =======================================================\r\n\r\nVCCommit\r\n\r\n  press <m-h> for a short help, <m-f> when you have finished\r\n\r\n@#@ \/pr\/svnnix\/trace\/nixpkgs\/trunk\/ :\r\n@#@ \/pr\/svnnix\/trace\/nixpkgs\/trunk\/pkgs\/top-level\/all-packages.nix :\r\n@#@ comment for all (additional comments will be added below this) :\r\n=============  =======================================================\r\n\r\nEither place you comment below the last line (comment for all)\r\nOr add individual comments for each file (a svn commit will then be executed for each of them)\r\nThe comment for all will be added as well in this case\r\n\r\nIf a file hasn't been added it will be added automatically.\r\n\r\nSee the **tagging.vim file (defining b:tagged) which tells the script which\r\nfiles to add \/ commit\r\n\r\nIt does also define the command UntagAll\r\n\r\nYou want to call vl#lib#ui#tagging#TaggingUI() to add the <m-t><m-g> mapping\r\ntoggling the tagged status.\r\n\r\nI've been using this script for quite while now.\r\nIt's not finished but it does all I need most of the time.\r\n\r\nIf you have trouble (errors) then try\r\n:echo g:systemResult\r\nwhich shows the last command output much nicer then the exception\r\n\r\nFeel free to sent me a mail with any questions\/ enhancements etc.\r\n","4":"Probably you want to try http:\/\/www.vim.org\/scripts\/script.php?script_id=90 instead. It's much more powerful\r\n\r\nDefault mapping are provided by\r\n\r\nvl#dev#versioncontrolsystem#manager#VCSUI()\r\n(and see the tagging UI function below)\r\n\r\nEg when committing you'll get a new window like this:\r\n=============  =======================================================\r\n\r\nVCCommit\r\n\r\n  press <m-h> for a short help, <m-f> when you have finished\r\n\r\n@#@ \/pr\/svnnix\/trace\/nixpkgs\/trunk\/ :\r\n@#@ \/pr\/svnnix\/trace\/nixpkgs\/trunk\/pkgs\/top-level\/all-packages.nix :\r\n@#@ comment for all (additional comments will be added below this) :\r\n=============  =======================================================\r\n\r\nEither place you comment below the last line (comment for all)\r\nOr add individual comments for each file (a svn commit will then be executed for each of them)\r\nThe comment for all will be added as well in this case\r\n\r\nIf a file hasn't been added it will be added automatically.\r\n\r\nSee the **tagging.vim file (defining b:tagged) which tells the script which\r\nfiles to add \/ commit\r\n\r\nIt does also define the command UntagAll\r\n\r\nYou want to call vl#lib#ui#tagging#TaggingUI() to add the <m-t><m-g> mapping\r\ntoggling the tagged status.\r\n\r\nI've been using this script for quite while now.\r\nIt's not finished but it does all I need most of the time.\r\n\r\nIf you have trouble (errors) then try\r\n:echo g:systemResult\r\nwhich shows the last command output much nicer then the exception\r\n\r\nFeel free to sent me a mail with any questions\/ enhancements etc.\r\n","install_details":"Just source the file and follow the instructions. \r\nYou'll be asked before any action is taken. \r\n\r\nIf you don't feel comfortable installing to .vim install to another arbitrary directory and add it to your runtimepath \r\n(let runtimepath+= ..)","5":"Just source the file and follow the instructions. \r\nYou'll be asked before any action is taken. \r\n\r\nIf you don't feel comfortable installing to .vim install to another arbitrary directory and add it to your runtimepath \r\n(let runtimepath+= ..)","first_name":"Marc","6":"Marc","last_name":"Weber","7":"Weber","releases":[{"0":"2071","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"vimlib_svn_support_installer_sourceme.zip","4":"vimlib_svn_support_installer_sourceme.zip","src_id":"7955","5":"7955","creation_date":"1195224664","6":"1195224664"}]},"2070":{"script_id":"2070","0":"2070","script_name":"bbcode","1":"bbcode","script_type":"utility","2":"utility","summary":"bbcode syntax and code templates","3":"bbcode syntax and code templates","description":"This plugin includes a syntax highlighting for bbcode and some code \r\nskeletons for use with tSkeleton (vimscript #1160).\r\n\r\nIf viki (vimscript #861) >= 304 is installed, tex regions will be \r\nproperly highlighted too.\r\n\r\nIf you use tSkeleton < 403, you might also want to set these variables:\r\n\r\n    let g:tskelKeyword_bbcode = '\\(\\[\\*\\|[\\[\\\\][*[:alnum:]]\\{-}\\)'\r\n    let g:tskelBitGroup_bbcode = ['bbcode', 'tex']\r\n\r\nThe basic syntax file can also be used without any of these add-ons.\r\n\r\n","4":"This plugin includes a syntax highlighting for bbcode and some code \r\nskeletons for use with tSkeleton (vimscript #1160).\r\n\r\nIf viki (vimscript #861) >= 304 is installed, tex regions will be \r\nproperly highlighted too.\r\n\r\nIf you use tSkeleton < 403, you might also want to set these variables:\r\n\r\n    let g:tskelKeyword_bbcode = '\\(\\[\\*\\|[\\[\\\\][*[:alnum:]]\\{-}\\)'\r\n    let g:tskelBitGroup_bbcode = ['bbcode', 'tex']\r\n\r\nThe basic syntax file can also be used without any of these add-ons.\r\n\r\n","install_details":"Open the vba file and type:\r\n\r\n    :so %\r\n\r\nSee :help vimball for details. If you have difficulties to install this \r\nplugin or if you use vim 7.0, please make sure to use the current \r\nversion of vimball (vimscript #1502). You might need to download the \r\ndevelopment version from the author's website since previous versions of \r\nvimball had difficulties with certain filenames.\r\n\r\nIn the meantime (after I made the first release), there is a second \r\nsyntax file for bbcode, which you might also want to check out: \r\nvimscript #2109.\r\n\r\n\r\nAlso available via git\r\nhttp:\/\/github.com\/tomtom\/vimtlib\/tree\/master\r\n","5":"Open the vba file and type:\r\n\r\n    :so %\r\n\r\nSee :help vimball for details. If you have difficulties to install this \r\nplugin or if you use vim 7.0, please make sure to use the current \r\nversion of vimball (vimscript #1502). You might need to download the \r\ndevelopment version from the author's website since previous versions of \r\nvimball had difficulties with certain filenames.\r\n\r\nIn the meantime (after I made the first release), there is a second \r\nsyntax file for bbcode, which you might also want to check out: \r\nvimscript #2109.\r\n\r\n\r\nAlso available via git\r\nhttp:\/\/github.com\/tomtom\/vimtlib\/tree\/master\r\n","first_name":"Tom","6":"Tom","last_name":"Link","7":"Link","releases":[{"0":"2070","vim_version":"7.0","1":"7.0","script_version":"0.2","2":"0.2","version_comment":"Minor tweaks, more templates, made tags upper case,","3":"Minor tweaks, more templates, made tags upper case,","package":"bbcode.vba.gz","4":"bbcode.vba.gz","src_id":"8119","5":"8119","creation_date":"1199423377","6":"1199423377"},{"0":"2070","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"bbcode.vba.gz","4":"bbcode.vba.gz","src_id":"7945","5":"7945","creation_date":"1195122200","6":"1195122200"}]},"2069":{"script_id":"2069","0":"2069","script_name":"ttagcomplete","1":"ttagcomplete","script_type":"utility","2":"utility","summary":"Context-sensitive tags-based completion and code skeletons","3":"Context-sensitive tags-based completion and code skeletons","description":"In theory, this plugin provides a framework for context-sensitive \r\ntags-based completion and code skeletons (requires tSkeleton vimscript \r\n#1160). I.e. the completion function checks the context and filters the \r\navailable tags accordingly. You should thus get only those tags included \r\nin the list that are actually useful in a given context (eg because the \r\nare valid methods of a certain class).\r\n\r\nIn practice, the context sensitivity is currently only implemented for \r\nJava and requires a tags file for the JDK sources to be created (see the \r\nnotes on |tlib#tag#Retrieve()| for details). It also makes certain \r\nassumption about how variable declarations look like, e.g. the \r\nclass\/type name should be in the same line as the variable name; class \r\nnames start with an upper-case letter etc.\r\n\r\nLimitation: you have to type g:ttagecho_min_chars = 1 chars before\r\ncompletion is allowed.\r\n\r\nIt shouldn't be too difficult to adapt this for other statically typed \r\nlanguages with formal variable declarations. As the source code isn't \r\nactually parsed or anything, there is little chance to use this \r\nefficiently with dynamically typed languages like ruby where the \r\ntype\/class is only known at run-time.\r\n","4":"In theory, this plugin provides a framework for context-sensitive \r\ntags-based completion and code skeletons (requires tSkeleton vimscript \r\n#1160). I.e. the completion function checks the context and filters the \r\navailable tags accordingly. You should thus get only those tags included \r\nin the list that are actually useful in a given context (eg because the \r\nare valid methods of a certain class).\r\n\r\nIn practice, the context sensitivity is currently only implemented for \r\nJava and requires a tags file for the JDK sources to be created (see the \r\nnotes on |tlib#tag#Retrieve()| for details). It also makes certain \r\nassumption about how variable declarations look like, e.g. the \r\nclass\/type name should be in the same line as the variable name; class \r\nnames start with an upper-case letter etc.\r\n\r\nLimitation: you have to type g:ttagecho_min_chars = 1 chars before\r\ncompletion is allowed.\r\n\r\nIt shouldn't be too difficult to adapt this for other statically typed \r\nlanguages with formal variable declarations. As the source code isn't \r\nactually parsed or anything, there is little chance to use this \r\nefficiently with dynamically typed languages like ruby where the \r\ntype\/class is only known at run-time.\r\n","install_details":"Edit the vba file and type: >\r\n\r\n    :so %\r\n\r\nSee :help vimball for details. If you have difficulties or use vim 7.0, \r\nplease make sure, you have the current version of vimball (vimscript \r\n#1502) installed.\r\n\r\nThis script requires tlib (vimscript #1863) to be installed.\r\n\r\nFor code skeletons, you also need tSkeletons (vimscript #1160).\r\n\r\nSuggested setup for java (best set in ~\/vimfiles\/after\/ftplugin\/java.vim): >\r\n\r\n    \" See notes on |tlib#tag#Retrieve()|.\r\n    let b:tlib_tags_extra = $JAVA_HOME .'\/tags0'\r\n\r\n    let b:ttagcomplete_collect='ttagcomplete#Java'\r\n\r\n    \" Call |ttagcomplete#On()| and set 'omnifunc'.\r\n    TTagCompleteOn\r\n\r\n    \" For code skeletons, use this:\r\n    if exists('g:loaded_tskeleton') && g:loaded_tskeleton >= 402\r\n        noremap <buffer> <c-x><c-g> :call ttagcomplete#CompleteSkeletons('m')<cr>\r\n        inoremap <buffer> <c-x><c-g> <c-\\><c-o>:call ttagcomplete#CompleteSkeletons('m')<cr>\r\n    endif\r\n\r\n\r\nAlso available via git\r\nhttp:\/\/github.com\/tomtom\/vimtlib\/tree\/master\r\n","5":"Edit the vba file and type: >\r\n\r\n    :so %\r\n\r\nSee :help vimball for details. If you have difficulties or use vim 7.0, \r\nplease make sure, you have the current version of vimball (vimscript \r\n#1502) installed.\r\n\r\nThis script requires tlib (vimscript #1863) to be installed.\r\n\r\nFor code skeletons, you also need tSkeletons (vimscript #1160).\r\n\r\nSuggested setup for java (best set in ~\/vimfiles\/after\/ftplugin\/java.vim): >\r\n\r\n    \" See notes on |tlib#tag#Retrieve()|.\r\n    let b:tlib_tags_extra = $JAVA_HOME .'\/tags0'\r\n\r\n    let b:ttagcomplete_collect='ttagcomplete#Java'\r\n\r\n    \" Call |ttagcomplete#On()| and set 'omnifunc'.\r\n    TTagCompleteOn\r\n\r\n    \" For code skeletons, use this:\r\n    if exists('g:loaded_tskeleton') && g:loaded_tskeleton >= 402\r\n        noremap <buffer> <c-x><c-g> :call ttagcomplete#CompleteSkeletons('m')<cr>\r\n        inoremap <buffer> <c-x><c-g> <c-\\><c-o>:call ttagcomplete#CompleteSkeletons('m')<cr>\r\n    endif\r\n\r\n\r\nAlso available via git\r\nhttp:\/\/github.com\/tomtom\/vimtlib\/tree\/master\r\n","first_name":"Tom","6":"Tom","last_name":"Link","7":"Link","releases":[{"0":"2069","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"ttagcomplete.vba.gz","4":"ttagcomplete.vba.gz","src_id":"7940","5":"7940","creation_date":"1194863408","6":"1194863408"}]},"2068":{"script_id":"2068","0":"2068","script_name":"yate","1":"yate","script_type":"utility","2":"utility","summary":"This plugin makes search in tags more convenient.","3":"This plugin makes search in tags more convenient.","description":"This plugin makes search in tags more convenient. It holds query and search result in one buffer for faster jump to desired tag.\r\n\r\nSource code is also available on bitbucket: https:\/\/bitbucket.org\/madevgeny\/yate.\r\n\r\nUsage:\r\nCommand :YATE toggles visibility of search buffer which will be closed after tag was selected.\r\nCommand :YATEStationary toggles visibility of search buffer which will not be closed after tag is selected, instead cursor remains in YATE buffer to allow select another tag.\r\nParameter g:YATE_window_height sets height of search buffer. Default = 15.\r\nParameter g:YATE_strip_long_paths enables(1)\/disables(0) cutting of long file paths. Default = 1.\r\nParameter g:YATE_enable_real_time_search enables(1)\/disables(0) as-you-type search. Default = 1.\r\nParameter g:YATE_min_symbols_to_search sets search string length threshold after which as-you-type search will start. Default = 4.\r\nParameter g:YATE_max_matches_to_show sets the maximum number of matches to display. If it's negative than all lines will be shown. Default = -1.\r\nParameter g:YATE_history_size sets the maximum number of stored search queries in history. Default = 10.\r\nParameter g:YATE_clear_search_string controls clearing of search string on next YATE buffer invocation. Default = 1.\r\n\r\nTo get list of matching tags set cursor on string containing expression\r\nto search (in YATE buffer) then press <Tab> or <Enter>, never mind if \r\nyou are in normal or insert mode.\r\n\r\nTo open tag location set cursor on string with desired tag and\r\npress <Enter> or double click left mouse button on this string, \r\nnever mind if you are in normal or insert mode.\r\n\r\nTo open tag in new tab press <Ctrl-Enter>, in new horizontal\r\nsplitted buffer <Shift-Enter>, in new vertical splitted buffer <Ctrl-Shift-Enter>.\r\n\r\nTo get queries history press <Ctrl-H> in insert or normal mode in\r\nsearch string. Autocompletion using history also works by <Ctrl-X><Ctrl-U>.","4":"This plugin makes search in tags more convenient. It holds query and search result in one buffer for faster jump to desired tag.\r\n\r\nSource code is also available on bitbucket: https:\/\/bitbucket.org\/madevgeny\/yate.\r\n\r\nUsage:\r\nCommand :YATE toggles visibility of search buffer which will be closed after tag was selected.\r\nCommand :YATEStationary toggles visibility of search buffer which will not be closed after tag is selected, instead cursor remains in YATE buffer to allow select another tag.\r\nParameter g:YATE_window_height sets height of search buffer. Default = 15.\r\nParameter g:YATE_strip_long_paths enables(1)\/disables(0) cutting of long file paths. Default = 1.\r\nParameter g:YATE_enable_real_time_search enables(1)\/disables(0) as-you-type search. Default = 1.\r\nParameter g:YATE_min_symbols_to_search sets search string length threshold after which as-you-type search will start. Default = 4.\r\nParameter g:YATE_max_matches_to_show sets the maximum number of matches to display. If it's negative than all lines will be shown. Default = -1.\r\nParameter g:YATE_history_size sets the maximum number of stored search queries in history. Default = 10.\r\nParameter g:YATE_clear_search_string controls clearing of search string on next YATE buffer invocation. Default = 1.\r\n\r\nTo get list of matching tags set cursor on string containing expression\r\nto search (in YATE buffer) then press <Tab> or <Enter>, never mind if \r\nyou are in normal or insert mode.\r\n\r\nTo open tag location set cursor on string with desired tag and\r\npress <Enter> or double click left mouse button on this string, \r\nnever mind if you are in normal or insert mode.\r\n\r\nTo open tag in new tab press <Ctrl-Enter>, in new horizontal\r\nsplitted buffer <Shift-Enter>, in new vertical splitted buffer <Ctrl-Shift-Enter>.\r\n\r\nTo get queries history press <Ctrl-H> in insert or normal mode in\r\nsearch string. Autocompletion using history also works by <Ctrl-X><Ctrl-U>.","install_details":"Just drop this file in your plugin directory.\r\nIf you use Vundle (https:\/\/github.com\/gmarik\/vundle\/), you could add \r\n\r\nBundle('https:\/\/bitbucket.org\/madevgeny\/yate.git')\r\n\r\nto your Vundle config to install yate.","5":"Just drop this file in your plugin directory.\r\nIf you use Vundle (https:\/\/github.com\/gmarik\/vundle\/), you could add \r\n\r\nBundle('https:\/\/bitbucket.org\/madevgeny\/yate.git')\r\n\r\nto your Vundle config to install yate.","first_name":"Evgeny","6":"Evgeny","last_name":"Podjachev","7":"Podjachev","releases":[{"0":"2068","vim_version":"7.0","1":"7.0","script_version":"1.4.2","2":"1.4.2","version_comment":"Fixed error when running YATEStationary. Thanks to Eoin Mcloughlin.\r\n","3":"Fixed error when running YATEStationary. Thanks to Eoin Mcloughlin.\r\n","package":"yate.vim","4":"yate.vim","src_id":"21208","5":"21208","creation_date":"1387364139","6":"1387364139"},{"0":"2068","vim_version":"7.0","1":"7.0","script_version":"1.4.1","2":"1.4.1","version_comment":"Fixed issue with TabBar plugin.\r\nRemoved yate buffer from buffers list.\r\nBetter work with history popup menu.","3":"Fixed issue with TabBar plugin.\r\nRemoved yate buffer from buffers list.\r\nBetter work with history popup menu.","package":"yate.vim","4":"yate.vim","src_id":"18933","5":"18933","creation_date":"1351716152","6":"1351716152"},{"0":"2068","vim_version":"7.0","1":"7.0","script_version":"1.4.0","2":"1.4.0","version_comment":"Added command YATEStationary to look into several tags without reopen YATE buffer.\r\nFixed conflict if already there is mapping on Q.","3":"Added command YATEStationary to look into several tags without reopen YATE buffer.\r\nFixed conflict if already there is mapping on Q.","package":"yate.vim","4":"yate.vim","src_id":"18298","5":"18298","creation_date":"1342900358","6":"1342900358"},{"0":"2068","vim_version":"7.0","1":"7.0","script_version":"1.3.1","2":"1.3.1","version_comment":"Disabled AutoComplPop plugin in YATE buffer.","3":"Disabled AutoComplPop plugin in YATE buffer.","package":"yate.vim","4":"yate.vim","src_id":"18295","5":"18295","creation_date":"1342816880","6":"1342816880"},{"0":"2068","vim_version":"7.0","1":"7.0","script_version":"1.3.0","2":"1.3.0","version_comment":"Added parameter g:YATE_clear_search_string to control clearing of search string on next YATE buffer invocation.\r\nPressing <Enter> in search string if length of search string is more or equal g:YATE_min_symbols_to_search lead to open first tag in search results.\r\n","3":"Added parameter g:YATE_clear_search_string to control clearing of search string on next YATE buffer invocation.\r\nPressing <Enter> in search string if length of search string is more or equal g:YATE_min_symbols_to_search lead to open first tag in search results.\r\n","package":"yate.vim","4":"yate.vim","src_id":"18287","5":"18287","creation_date":"1342692698","6":"1342692698"},{"0":"2068","vim_version":"7.0","1":"7.0","script_version":"1.2.5","2":"1.2.5","version_comment":"Force disable line numbering in YATE buffer.","3":"Force disable line numbering in YATE buffer.","package":"yate.vim","4":"yate.vim","src_id":"18283","5":"18283","creation_date":"1342597697","6":"1342597697"},{"0":"2068","vim_version":"7.0","1":"7.0","script_version":"1.2.4","2":"1.2.4","version_comment":"Fixed leaving of insert mode after leaving YATE buffer.","3":"Fixed leaving of insert mode after leaving YATE buffer.","package":"yate.vim","4":"yate.vim","src_id":"18262","5":"18262","creation_date":"1342288436","6":"1342288436"},{"0":"2068","vim_version":"7.0","1":"7.0","script_version":"1.2.3","2":"1.2.3","version_comment":"Insert mode is default in YATE buffer.","3":"Insert mode is default in YATE buffer.","package":"yate.vim","4":"yate.vim","src_id":"18257","5":"18257","creation_date":"1342278190","6":"1342278190"},{"0":"2068","vim_version":"7.0","1":"7.0","script_version":"1.2.2","2":"1.2.2","version_comment":"Fixed cleaning of search string in some cases.","3":"Fixed cleaning of search string in some cases.","package":"yate.vim","4":"yate.vim","src_id":"10698","5":"10698","creation_date":"1243537529","6":"1243537529"},{"0":"2068","vim_version":"7.0","1":"7.0","script_version":"1.2.1","2":"1.2.1","version_comment":"History menu (<C-H>) also works in normal mode.","3":"History menu (<C-H>) also works in normal mode.","package":"yate.vim","4":"yate.vim","src_id":"10502","5":"10502","creation_date":"1241167526","6":"1241167526"},{"0":"2068","vim_version":"7.0","1":"7.0","script_version":"1.2.0","2":"1.2.0","version_comment":"Added history of search queries.","3":"Added history of search queries.","package":"yate.vim","4":"yate.vim","src_id":"10346","5":"10346","creation_date":"1238854388","6":"1238854388"},{"0":"2068","vim_version":"7.0","1":"7.0","script_version":"1.1.1","2":"1.1.1","version_comment":"Slightly optimized search results output.\r\nFixed resizing of YATE window when vim is resized.","3":"Slightly optimized search results output.\r\nFixed resizing of YATE window when vim is resized.","package":"yate.vim","4":"yate.vim","src_id":"9815","5":"9815","creation_date":"1231955658","6":"1231955658"},{"0":"2068","vim_version":"7.0","1":"7.0","script_version":"1.1.0","2":"1.1.0","version_comment":"Fixes in as-you-type search to improve its usability and fix some bugs.\r\nAdded highlight of line with cursor.\r\nAdded parameter g:YATE_max_matches_to_show defining the maximum number of matches to display.\r\nSearch results were protected from editing.","3":"Fixes in as-you-type search to improve its usability and fix some bugs.\r\nAdded highlight of line with cursor.\r\nAdded parameter g:YATE_max_matches_to_show defining the maximum number of matches to display.\r\nSearch results were protected from editing.","package":"yate.vim","4":"yate.vim","src_id":"9248","5":"9248","creation_date":"1221298760","6":"1221298760"},{"0":"2068","vim_version":"7.0","1":"7.0","script_version":"1.0.1","2":"1.0.1","version_comment":"Fixed serious bug which caused the impossibility of inputing characters nowhere but at the and of the search string.\r\nAdd support of GetLatestVimScripts.","3":"Fixed serious bug which caused the impossibility of inputing characters nowhere but at the and of the search string.\r\nAdd support of GetLatestVimScripts.","package":"yate.vim","4":"yate.vim","src_id":"8467","5":"8467","creation_date":"1205929179","6":"1205929179"},{"0":"2068","vim_version":"7.0","1":"7.0","script_version":"1.0.0","2":"1.0.0","version_comment":"Added automatic search after input of any character (so called as-you-type search).\r\nLong file paths may be cut to fit line width.\r\nFixed bug preventing jump by tags containing ~ (e.g. c++ destructors).\r\nFixed bug preventing jump by tags in files with mixed line ends (Win\/Unix).","3":"Added automatic search after input of any character (so called as-you-type search).\r\nLong file paths may be cut to fit line width.\r\nFixed bug preventing jump by tags containing ~ (e.g. c++ destructors).\r\nFixed bug preventing jump by tags in files with mixed line ends (Win\/Unix).","package":"yate.vim","4":"yate.vim","src_id":"8378","5":"8378","creation_date":"1204434058","6":"1204434058"},{"0":"2068","vim_version":"7.0","1":"7.0","script_version":"0.9.2","2":"0.9.2","version_comment":"Attempt to search empty string doesn't produce error.\r\nReplacement of modified buffer works correct.\r\nClose YATE buffer externally (by :q, ZZ etc.) dosn't break its visibility toggle.\r\nFixed bug leading to failure to open to tag containing square brackets.","3":"Attempt to search empty string doesn't produce error.\r\nReplacement of modified buffer works correct.\r\nClose YATE buffer externally (by :q, ZZ etc.) dosn't break its visibility toggle.\r\nFixed bug leading to failure to open to tag containing square brackets.","package":"yate.vim","4":"yate.vim","src_id":"8082","5":"8082","creation_date":"1198398290","6":"1198398290"},{"0":"2068","vim_version":"7.0","1":"7.0","script_version":"0.9.1","2":"0.9.1","version_comment":"Search string isn't cleared if there are no matched tags.\r\nBug fixes.","3":"Search string isn't cleared if there are no matched tags.\r\nBug fixes.","package":"yate.vim","4":"yate.vim","src_id":"8004","5":"8004","creation_date":"1196332849","6":"1196332849"},{"0":"2068","vim_version":"7.0","1":"7.0","script_version":"0.9","2":"0.9","version_comment":"Initial upload","3":"Initial upload","package":"yate.vim","4":"yate.vim","src_id":"7930","5":"7930","creation_date":"1194751138","6":"1194751138"}]},"2067":{"script_id":"2067","0":"2067","script_name":"newlisp","1":"newlisp","script_type":"syntax","2":"syntax","summary":"newLISP syntax file","3":"newLISP syntax file","description":"Syntax file for the newLISP language (http:\/\/www.newlisp.org). Another location is http:\/\/slobin.ru\/vim\/syntax\/newlisp.vim\r\n","4":"Syntax file for the newLISP language (http:\/\/www.newlisp.org). Another location is http:\/\/slobin.ru\/vim\/syntax\/newlisp.vim\r\n","install_details":"","5":"","first_name":"Cyril","6":"Cyril","last_name":"Slobin","7":"Slobin","releases":[{"0":"2067","vim_version":"7.0","1":"7.0","script_version":"1.37","2":"1.37","version_comment":"Based on newLISP v10.5.0 (including bigint arithmetic)","3":"Based on newLISP v10.5.0 (including bigint arithmetic)","package":"newlisp.vim","4":"newlisp.vim","src_id":"20268","5":"20268","creation_date":"1370199876","6":"1370199876"},{"0":"2067","vim_version":"7.0","1":"7.0","script_version":"1.35","2":"1.35","version_comment":"Misc changes, experimental release.","3":"Misc changes, experimental release.","package":"newlisp.vim","4":"newlisp.vim","src_id":"15449","5":"15449","creation_date":"1302847839","6":"1302847839"},{"0":"2067","vim_version":"7.0","1":"7.0","script_version":"1.33","2":"1.33","version_comment":"Got in synch with newLISP v10.2.16","3":"Got in synch with newLISP v10.2.16","package":"newlisp.vim","4":"newlisp.vim","src_id":"14023","5":"14023","creation_date":"1286479293","6":"1286479293"},{"0":"2067","vim_version":"7.0","1":"7.0","script_version":"1.32","2":"1.32","version_comment":"Matching of parentheses in documenting comments was broken, fixed.","3":"Matching of parentheses in documenting comments was broken, fixed.","package":"newlisp.vim","4":"newlisp.vim","src_id":"14014","5":"14014","creation_date":"1286418540","6":"1286418540"},{"0":"2067","vim_version":"6.0","1":"6.0","script_version":"1.31","2":"1.31","version_comment":"Multiple patches by LM adopted, ready for newLISP 10.3 release.","3":"Multiple patches by LM adopted, ready for newLISP 10.3 release.","package":"newlisp.vim","4":"newlisp.vim","src_id":"12981","5":"12981","creation_date":"1273439161","6":"1273439161"},{"0":"2067","vim_version":"6.0","1":"6.0","script_version":"1.27","2":"1.27","version_comment":"new built-in and preloaded functions from newlisp 10.0.8, newlispdoc custom tags, intended to match the upcoming newlisp 10.1 release","3":"new built-in and preloaded functions from newlisp 10.0.8, newlispdoc custom tags, intended to match the upcoming newlisp 10.1 release","package":"newlisp.vim","4":"newlisp.vim","src_id":"10812","5":"10812","creation_date":"1244815358","6":"1244815358"},{"0":"2067","vim_version":"6.0","1":"6.0","script_version":"1.25","2":"1.25","version_comment":"Synchronized with newlisp 10.0.2","3":"Synchronized with newlisp 10.0.2","package":"newlisp.vim","4":"newlisp.vim","src_id":"10257","5":"10257","creation_date":"1237596075","6":"1237596075"},{"0":"2067","vim_version":"6.0","1":"6.0","script_version":"1.24","2":"1.24","version_comment":"Another step toward newlisp v10.0","3":"Another step toward newlisp v10.0","package":"newlisp.vim","4":"newlisp.vim","src_id":"9574","5":"9574","creation_date":"1227734476","6":"1227734476"},{"0":"2067","vim_version":"6.0","1":"6.0","script_version":"1.23","2":"1.23","version_comment":"Meeting the upcoming newlisp v10.0 release","3":"Meeting the upcoming newlisp v10.0 release","package":"newlisp.vim","4":"newlisp.vim","src_id":"9292","5":"9292","creation_date":"1222635865","6":"1222635865"},{"0":"2067","vim_version":"6.0","1":"6.0","script_version":"1.22","2":"1.22","version_comment":"Vim 6.0 compatibility restored","3":"Vim 6.0 compatibility restored","package":"newlisp.vim","4":"newlisp.vim","src_id":"8824","5":"8824","creation_date":"1213878270","6":"1213878270"},{"0":"2067","vim_version":"7.0","1":"7.0","script_version":"1.21","2":"1.21","version_comment":"Functions list updated to meet 9.3.15 version of newlisp (hopefully it will not change in 9.4.0)","3":"Functions list updated to meet 9.3.15 version of newlisp (hopefully it will not change in 9.4.0)","package":"newlisp.vim","4":"newlisp.vim","src_id":"8809","5":"8809","creation_date":"1213603427","6":"1213603427"},{"0":"2067","vim_version":"6.0","1":"6.0","script_version":"1.20","2":"1.20","version_comment":"'read' replaced with 'read-expr', definition of special symbols changed","3":"'read' replaced with 'read-expr', definition of special symbols changed","package":"newlisp.vim","4":"newlisp.vim","src_id":"8507","5":"8507","creation_date":"1206839522","6":"1206839522"},{"0":"2067","vim_version":"6.0","1":"6.0","script_version":"1.19","2":"1.19","version_comment":"@index keyword and <hr> tag added","3":"@index keyword and <hr> tag added","package":"newlisp.vim","4":"newlisp.vim","src_id":"8361","5":"8361","creation_date":"1204195703","6":"1204195703"},{"0":"2067","vim_version":"6.0","1":"6.0","script_version":"1.18","2":"1.18","version_comment":"ostype added to standard variables, ALL_CAPS became special","3":"ostype added to standard variables, ALL_CAPS became special","package":"newlisp.vim","4":"newlisp.vim","src_id":"8339","5":"8339","creation_date":"1203823007","6":"1203823007"},{"0":"2067","vim_version":"6.0","1":"6.0","script_version":"1.17","2":"1.17","version_comment":"Code cleanup","3":"Code cleanup","package":"newlisp.vim","4":"newlisp.vim","src_id":"8338","5":"8338","creation_date":"1203817881","6":"1203817881"},{"0":"2067","vim_version":"6.0","1":"6.0","script_version":"1.16","2":"1.16","version_comment":"fn keyword added, some groups renamed","3":"fn keyword added, some groups renamed","package":"newlisp.vim","4":"newlisp.vim","src_id":"8326","5":"8326","creation_date":"1203657995","6":"1203657995"},{"0":"2067","vim_version":"6.0","1":"6.0","script_version":"1.15","2":"1.15","version_comment":"read and lambda keywords added","3":"read and lambda keywords added","package":"newlisp.vim","4":"newlisp.vim","src_id":"8284","5":"8284","creation_date":"1203111912","6":"1203111912"},{"0":"2067","vim_version":"6.0","1":"6.0","script_version":"1.14","2":"1.14","version_comment":"Fixed bug in @link keyword highlighting","3":"Fixed bug in @link keyword highlighting","package":"newlisp.vim","4":"newlisp.vim","src_id":"8215","5":"8215","creation_date":"1201943442","6":"1201943442"},{"0":"2067","vim_version":"6.0","1":"6.0","script_version":"1.13","2":"1.13","version_comment":"Symbols ending with special characters are treated as special; errors disabling (introduced in 1.10) removed back, it was a bad idea anyway.\r\n","3":"Symbols ending with special characters are treated as special; errors disabling (introduced in 1.10) removed back, it was a bad idea anyway.\r\n","package":"newlisp.vim","4":"newlisp.vim","src_id":"8209","5":"8209","creation_date":"1201858048","6":"1201858048"},{"0":"2067","vim_version":"6.0","1":"6.0","script_version":"1.12","2":"1.12","version_comment":"Keywords list updated; functions and constants placed in separate groups; link to this page in header; minor bugfixes.","3":"Keywords list updated; functions and constants placed in separate groups; link to this page in header; minor bugfixes.","package":"newlisp.vim","4":"newlisp.vim","src_id":"8163","5":"8163","creation_date":"1200735194","6":"1200735194"},{"0":"2067","vim_version":"6.0","1":"6.0","script_version":"1.10","2":"1.10","version_comment":"Highlighting of errors can be disabled on case-by-case basis","3":"Highlighting of errors can be disabled on case-by-case basis","package":"newlisp.vim","4":"newlisp.vim","src_id":"7984","5":"7984","creation_date":"1195815457","6":"1195815457"},{"0":"2067","vim_version":"6.0","1":"6.0","script_version":"1.9","2":"1.9","version_comment":"Start of non top-level expression in the first column is marked as an error -- probably the previous top-level expression has not been closed properly","3":"Start of non top-level expression in the first column is marked as an error -- probably the previous top-level expression has not been closed properly","package":"newlisp.vim","4":"newlisp.vim","src_id":"7935","5":"7935","creation_date":"1194859980","6":"1194859980"},{"0":"2067","vim_version":"6.0","1":"6.0","script_version":"1.8","2":"1.8","version_comment":"Bug in <italic> and 'monospace' highlighting fixed","3":"Bug in <italic> and 'monospace' highlighting fixed","package":"newlisp.vim","4":"newlisp.vim","src_id":"7933","5":"7933","creation_date":"1194822646","6":"1194822646"},{"0":"2067","vim_version":"6.0","1":"6.0","script_version":"1.7","2":"1.7","version_comment":"Fixed bug in @example keyword highlighting","3":"Fixed bug in @example keyword highlighting","package":"newlisp.vim","4":"newlisp.vim","src_id":"7929","5":"7929","creation_date":"1194737047","6":"1194737047"},{"0":"2067","vim_version":"6.0","1":"6.0","script_version":"1.6","2":"1.6","version_comment":"Fixed bug when syntax switched off and back on or colorscheme changed","3":"Fixed bug when syntax switched off and back on or colorscheme changed","package":"newlisp.vim","4":"newlisp.vim","src_id":"7924","5":"7924","creation_date":"1194702293","6":"1194702293"},{"0":"2067","vim_version":"6.0","1":"6.0","script_version":"1.5","2":"1.5","version_comment":"By popular demand, quoted symbols are highlighted now","3":"By popular demand, quoted symbols are highlighted now","package":"newlisp.vim","4":"newlisp.vim","src_id":"7918","5":"7918","creation_date":"1194654724","6":"1194654724"},{"0":"2067","vim_version":"6.0","1":"6.0","script_version":"1.4","2":"1.4","version_comment":"newlispdoc syntax properly supported","3":"newlispdoc syntax properly supported","package":"newlisp.vim","4":"newlisp.vim","src_id":"7914","5":"7914","creation_date":"1194648681","6":"1194648681"},{"0":"2067","vim_version":"6.0","1":"6.0","script_version":"1.3","2":"1.3","version_comment":"Keywords and HTML tags in comments are highlighted now","3":"Keywords and HTML tags in comments are highlighted now","package":"newlisp.vim","4":"newlisp.vim","src_id":"7913","5":"7913","creation_date":"1194638324","6":"1194638324"},{"0":"2067","vim_version":"6.0","1":"6.0","script_version":"1.2","2":"1.2","version_comment":"Parentheses highlighting added","3":"Parentheses highlighting added","package":"newlisp.vim","4":"newlisp.vim","src_id":"7911","5":"7911","creation_date":"1194628373","6":"1194628373"},{"0":"2067","vim_version":"6.0","1":"6.0","script_version":"1.1+1","2":"1.1+1","version_comment":"Initial upload","3":"Initial upload","package":"newlisp.vim","4":"newlisp.vim","src_id":"7909","5":"7909","creation_date":"1194625311","6":"1194625311"}]},"2066":{"script_id":"2066","0":"2066","script_name":"executevimscript","1":"executevimscript","script_type":"utility","2":"utility","summary":"Execute selected vimscript lines","3":"Execute selected vimscript lines","description":"This package allows you to:\r\n- Execute some selected vimscript lines\r\n- Create a vimscript sandbox where you can type & test vimscript fast\r\n\r\nThis is a very rough version, with no checks. It currently works only on lines, but in later versions hopefully it will work with any selection, including rectangular selection.\r\n\r\nThe goal of this package is to provide a Vim equivalent of Smalltalk\\'s \\\"do it\\\" and \\\"print it\\\".\r\n","4":"This package allows you to:\r\n- Execute some selected vimscript lines\r\n- Create a vimscript sandbox where you can type & test vimscript fast\r\n\r\nThis is a very rough version, with no checks. It currently works only on lines, but in later versions hopefully it will work with any selection, including rectangular selection.\r\n\r\nThe goal of this package is to provide a Vim equivalent of Smalltalk\\'s \\\"do it\\\" and \\\"print it\\\".\r\n","install_details":"Source this vimscript file (:source executevimscript.vim) and choose key bindings for the functions.","5":"Source this vimscript file (:source executevimscript.vim) and choose key bindings for the functions.","first_name":"S\u00c3\u00a9bastien","6":"S\u00c3\u00a9bastien","last_name":"Rocca-Serra","7":"Rocca-Serra","releases":[{"0":"2066","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"executevimscript.vim","4":"executevimscript.vim","src_id":"7908","5":"7908","creation_date":"1194596040","6":"1194596040"}]},"2065":{"script_id":"2065","0":"2065","script_name":"checksum.vim","1":"checksum.vim","script_type":"utility","2":"utility","summary":"Compute checksums on files or lines","3":"Compute checksums on files or lines","description":"Compute MD5 or SHA1 checksum of entire file or range of lines.\r\nStore checksum in buffer variable or in user-specified\r\nregister.  Uses external programs to compute checksums;\r\ncurrently supports GNU md5sum, GNU sha1sum, and OpenSSL.\r\nIf you are a Windows user, you should install GNU CoreUtils\r\nfor Windows\r\n(http:\/\/gnuwin32.sourceforge.net\/downlinks\/coreutils.php)\r\nor Win32 OpenSSL\r\n(http:\/\/www.slproweb.com\/products\/Win32OpenSSL.html)\r\n\r\nUsage:\r\n:{range}Md5 [register] - displays MD5 checksum for given range\r\nof lines (default is entire file) and stores in b:md5sum and\r\nthe register named as an argument.\r\n:{range}Sha1 [register] - displays SHA1 checksum for given\r\nrange of lines (default is entire file) and stores in\r\nb:sha1sum and the register named as an argument.\r\n<Leader>md - displays MD5 checksum for entire file or visual\r\nselection and stores in b:md5sum\r\n<Leader>sh - displays SHA1 checksum for entire file or visual\r\nselection and stores in b:sha1sum\r\n\r\n","4":"Compute MD5 or SHA1 checksum of entire file or range of lines.\r\nStore checksum in buffer variable or in user-specified\r\nregister.  Uses external programs to compute checksums;\r\ncurrently supports GNU md5sum, GNU sha1sum, and OpenSSL.\r\nIf you are a Windows user, you should install GNU CoreUtils\r\nfor Windows\r\n(http:\/\/gnuwin32.sourceforge.net\/downlinks\/coreutils.php)\r\nor Win32 OpenSSL\r\n(http:\/\/www.slproweb.com\/products\/Win32OpenSSL.html)\r\n\r\nUsage:\r\n:{range}Md5 [register] - displays MD5 checksum for given range\r\nof lines (default is entire file) and stores in b:md5sum and\r\nthe register named as an argument.\r\n:{range}Sha1 [register] - displays SHA1 checksum for given\r\nrange of lines (default is entire file) and stores in\r\nb:sha1sum and the register named as an argument.\r\n<Leader>md - displays MD5 checksum for entire file or visual\r\nselection and stores in b:md5sum\r\n<Leader>sh - displays SHA1 checksum for entire file or visual\r\nselection and stores in b:sha1sum\r\n\r\n","install_details":"Place checksum.vim in your $HOME\/.vim\/plugin directory.\r\n($HOME\/vimfiles\/plugin if you are a Windows Vimmer).","5":"Place checksum.vim in your $HOME\/.vim\/plugin directory.\r\n($HOME\/vimfiles\/plugin if you are a Windows Vimmer).","first_name":"erik","6":"erik","last_name":"falor","7":"falor","releases":[{"0":"2065","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"checksum.vim","4":"checksum.vim","src_id":"7903","5":"7903","creation_date":"1194526855","6":"1194526855"}]},"2064":{"script_id":"2064","0":"2064","script_name":"(x)emacs mouse drag-copy","1":"(x)emacs mouse drag-copy","script_type":"utility","2":"utility","summary":"(x)emacs style quick copy and paste","3":"(x)emacs style quick copy and paste","description":"In xemacs and emacs if it is enabled, there is a very handy way to copy and paste  without repositioning the cursor.  You press the control key, drag the mouse over some text, and when you release the mouse button the text will be inserted in the original position.  There is no need to move the position of the cursor.  Doing the same while pressing the shift key instead of the control key will move text instead of copying.  This script does these things in vim, for insert mode.","4":"In xemacs and emacs if it is enabled, there is a very handy way to copy and paste  without repositioning the cursor.  You press the control key, drag the mouse over some text, and when you release the mouse button the text will be inserted in the original position.  There is no need to move the position of the cursor.  Doing the same while pressing the shift key instead of the control key will move text instead of copying.  This script does these things in vim, for insert mode.","install_details":"Add to your .vimrc file.","5":"Add to your .vimrc file.","first_name":"Carl","6":"Carl","last_name":"Mueller","7":"Mueller","releases":[{"0":"2064","vim_version":"7.0","1":"7.0","script_version":"1.2","2":"1.2","version_comment":"Fixed a problem caused by tabs.","3":"Fixed a problem caused by tabs.","package":"xemacs-mouse-drag-copy.vim","4":"xemacs-mouse-drag-copy.vim","src_id":"8406","5":"8406","creation_date":"1204804798","6":"1204804798"},{"0":"2064","vim_version":"6.0","1":"6.0","script_version":"1.1","2":"1.1","version_comment":"Included shift-left-mouse-drag to move text.","3":"Included shift-left-mouse-drag to move text.","package":"xemacs-mouse-drag-copy.vim","4":"xemacs-mouse-drag-copy.vim","src_id":"7947","5":"7947","creation_date":"1195128407","6":"1195128407"},{"0":"2064","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"xemacs-mouse-drag-copy.vim","4":"xemacs-mouse-drag-copy.vim","src_id":"7894","5":"7894","creation_date":"1194429994","6":"1194429994"}]},"2063":{"script_id":"2063","0":"2063","script_name":"coq syntax","1":"coq syntax","script_type":"syntax","2":"syntax","summary":"syntax colouring for coq files","3":"syntax colouring for coq files","description":"All is in the title: syntax colouring for the coq proof assistant files (*.v).\r\n\r\nAlso check http:\/\/www.vim.org\/scripts\/script.php?script_id=2079 for indentation.\r\n\r\nSome people asked me if I planned to do something to interact between vim and coq. I answered that yes and that I had started it. The plugin is usable but not \u00e2\u0080\u009cpublishable\" :) However I now have many other things to do and am not using Coq at that time. So if I publish such a thing some day it may be in quite a long time. Apologies.","4":"All is in the title: syntax colouring for the coq proof assistant files (*.v).\r\n\r\nAlso check http:\/\/www.vim.org\/scripts\/script.php?script_id=2079 for indentation.\r\n\r\nSome people asked me if I planned to do something to interact between vim and coq. I answered that yes and that I had started it. The plugin is usable but not \u00e2\u0080\u009cpublishable\" :) However I now have many other things to do and am not using Coq at that time. So if I publish such a thing some day it may be in quite a long time. Apologies.","install_details":"1. Put the file in your ~\/.vim\/syntax directory.\r\n\r\n2. Create the file ~\/.vim\/ftdetect\/coq.vim and put the following line inside:\r\n\r\n  au BufRead,BufNewFile *.v   set filetype=coq\r\n\r\n(Notice that *.v files are also used for verilog sources. This will make vim recognize *.v files as coq ones. VERILOG FILES WON'T BE RECOGNIZED ANYMORE.)\r\n","5":"1. Put the file in your ~\/.vim\/syntax directory.\r\n\r\n2. Create the file ~\/.vim\/ftdetect\/coq.vim and put the following line inside:\r\n\r\n  au BufRead,BufNewFile *.v   set filetype=coq\r\n\r\n(Notice that *.v files are also used for verilog sources. This will make vim recognize *.v files as coq ones. VERILOG FILES WON'T BE RECOGNIZED ANYMORE.)\r\n","first_name":"Vincent","6":"Vincent","last_name":"Aravantinos","7":"Aravantinos","releases":[{"0":"2063","vim_version":"6.0","1":"6.0","script_version":"1.4.3","2":"1.4.3","version_comment":"Added Program and Obligations constructs of Coq v8.2.","3":"Added Program and Obligations constructs of Coq v8.2.","package":"coq.vim","4":"coq.vim","src_id":"9597","5":"9597","creation_date":"1228213308","6":"1228213308"},{"0":"2063","vim_version":"7.0","1":"7.0","script_version":"1.4","2":"1.4","version_comment":"- Changed the colours. It should now be more uniform and more readable. Tell me if you prefer the way it was before. \r\n- Improved the way things are coloured : in previous versions, the plugin often had to wait until you finish the current sentence before colouring it. Quite inconvenient. Now, it will colour things as you type them (for almost all constructions). Colouring is also more robust.","3":"- Changed the colours. It should now be more uniform and more readable. Tell me if you prefer the way it was before. \r\n- Improved the way things are coloured : in previous versions, the plugin often had to wait until you finish the current sentence before colouring it. Quite inconvenient. Now, it will colour things as you type them (for almost all constructions). Colouring is also more robust.","package":"coq.vim","4":"coq.vim","src_id":"8187","5":"8187","creation_date":"1201426506","6":"1201426506"},{"0":"2063","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Complete refactoring. Highlighting is now much more accurate. Oh, and the code is not ugly anymore.","3":"Complete refactoring. Highlighting is now much more accurate. Oh, and the code is not ugly anymore.","package":"coq.vim","4":"coq.vim","src_id":"7892","5":"7892","creation_date":"1194413877","6":"1194413877"},{"0":"2063","vim_version":"7.0","1":"7.0","script_version":"0.01","2":"0.01","version_comment":"Initial upload","3":"Initial upload","package":"coq.vim","4":"coq.vim","src_id":"7885","5":"7885","creation_date":"1194329059","6":"1194329059"}]},"2062":{"script_id":"2062","0":"2062","script_name":"haskell.vim","1":"haskell.vim","script_type":"syntax","2":"syntax","summary":"Syntax file for Haskell","3":"Syntax file for Haskell","description":"This script provides syntax highlight for Haskell.\r\nIt will highlight all standard prelude functions, types and constants.\r\n\r\nDownload at https:\/\/rcgoncalves.pt\/files\/haskell.zip\r\n\r\nPS: This script is an improvement on the vim default haskell script.","4":"This script provides syntax highlight for Haskell.\r\nIt will highlight all standard prelude functions, types and constants.\r\n\r\nDownload at https:\/\/rcgoncalves.pt\/files\/haskell.zip\r\n\r\nPS: This script is an improvement on the vim default haskell script.","install_details":"Put haskell.vim in your syntax diretory (e.g. ~\/.vim\/syntax). ","5":"Put haskell.vim in your syntax diretory (e.g. ~\/.vim\/syntax). ","first_name":"Rui Carlos","6":"Rui Carlos","last_name":"Gon\u00c3\u00a7alves","7":"Gon\u00c3\u00a7alves","releases":[{"0":"2062","vim_version":"7.0","1":"7.0","script_version":"2.0","2":"2.0","version_comment":"Updated to Haskell 2010.","3":"Updated to Haskell 2010.","package":"haskell.vim","4":"haskell.vim","src_id":"16590","5":"16590","creation_date":"1317054473","6":"1317054473"},{"0":"2062","vim_version":"7.0","1":"7.0","script_version":"1.2","2":"1.2","version_comment":"Error fixed (mim -> min)","3":"Error fixed (mim -> min)","package":"haskell.vim","4":"haskell.vim","src_id":"8252","5":"8252","creation_date":"1202561921","6":"1202561921"},{"0":"2062","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"haskell.vim","4":"haskell.vim","src_id":"7875","5":"7875","creation_date":"1194169284","6":"1194169284"}]},"2061":{"script_id":"2061","0":"2061","script_name":"Warm grey","1":"Warm grey","script_type":"color scheme","2":"color scheme","summary":"A monochromish, light slightly warm theme","3":"A monochromish, light slightly warm theme","description":"Tries to look as clear as pyte but a little less saturated with a slight \"warm\" touch.\r\n\r\nEdit: I removed the screenshot as I won't continue to work on this theme anymore. If you really like it and want to see it developed further, contact me (e.g. via http:\/\/leetless.de), if I see theres still a bunch of people wo like to see me working on this theme, I might decide to do so.","4":"Tries to look as clear as pyte but a little less saturated with a slight \"warm\" touch.\r\n\r\nEdit: I removed the screenshot as I won't continue to work on this theme anymore. If you really like it and want to see it developed further, contact me (e.g. via http:\/\/leetless.de), if I see theres still a bunch of people wo like to see me working on this theme, I might decide to do so.","install_details":"Put into ~\/.vim\/colors","5":"Put into ~\/.vim\/colors","first_name":"Henning","6":"Henning","last_name":"Hasemann","7":"Hasemann","releases":[{"0":"2061","vim_version":"6.0","1":"6.0","script_version":"1.1","2":"1.1","version_comment":"More colorful version, the old one was simply too boring.","3":"More colorful version, the old one was simply too boring.","package":"warm_grey.vim","4":"warm_grey.vim","src_id":"7991","5":"7991","creation_date":"1196046956","6":"1196046956"},{"0":"2061","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"warm_grey.vim","4":"warm_grey.vim","src_id":"7874","5":"7874","creation_date":"1194168588","6":"1194168588"}]},"2060":{"script_id":"2060","0":"2060","script_name":"winwkspaceexplorer","1":"winwkspaceexplorer","script_type":"utility","2":"utility","summary":"IDE like Project explorer ( plugin for winmanager )","3":"IDE like Project explorer ( plugin for winmanager )","description":"Many IDEs make it easy to organise source files into projects. Some IDEs then make it easy to organise projects into workspaces which can be explored. This is very useful for related projects where one may be an executable and another a required library. Code::Blocks is a very good examples of such an IDE. This is a feature that this plugin attempts to mimic inside the vim plugin winmanager. winmanager makes it incredibly easy to write such plugins (although the availability of an  example would be much appreciated).\r\n\r\nThere are however major differences between what this plugin attempts to achieve and what the workspace\/solution explorers in other IDEs give you. Classic IDE project explorers also give you access to build options and 'project settings', essentially configurations that would normally be within the scope of a makefile. winworkspaceexlporer does not attempt to do the this. It would not be appropriate. Most people coding with vim would probably be using 'make' or one of its many variants or replacements ( I use Scons ). It is more natural to edit the equivalent of the makefile directly in vim. Adding, deleting files to a project does not need to be supported in a plugin like this as these changes would be carried out directly in the makefile-like file. Whilst I do not require IDE workspace-explorer capabilities to set project options, compiler flags , link flags etc, I did have a need for a workspace-explorer-like plugin for vim that would simply let me explore the project files and organise them conveniently, hence winwkspaceexplorer.\r\n\r\nThe preferred way to generate the winwkspaceexplorer PROJECT files would be as additional targets in the makefile. I use SCons ( replacement for make)  and on Windows the project file for a popular  IDE gets created on the fly during the build process by code in the sconscript file ( Scons version of a makefile)(Scons actualy has this feature builtin). Similarly on Linux and Cygwin a winwkspaceexplorer project file is generated on the fly by the same sconscript file.\r\n\r\nThere are alternatives such as the script found at  http:\/\/www.vim.org\/scripts\/script.php?script_id=69. This is a very good plugin and definitely worth trying out. However I needed something that I could use with the winmanager, which is my first choice for the foundation of a very good IDE.  \r\n\r\nThis plugin is in early stages but, for me very useable. There are many more things that can be added easily. I am however keen to keep the plugin minimalist and most importantly do not want to duplicate any functionality  between winwkspaceexplorer and the makefile. \r\n\r\n\r\n\r\nPlease send any comments, suggestions,  or bugs to narinder_claireATyahoo.co.uk\r\n\r\n[NOTE]:  There are 2 entries for the winmanager plugin on vim.org. The original :\r\n                              http:\/\/www.vim.org\/scripts\/script.php?script_id=95\r\n               and its descendant \r\n                              http:\/\/www.vim.org\/scripts\/script.php?script_id=1440\r\n               I use the latter as its a continuation of the first and contains bugfixes.\r\n               To understand why there are two entries read the notes for the latter.\r\n\r\n \r\n\r\n================================================\r\nCHANGE LOG\r\n================================================\r\n02\/11\/2007 initial upload\r\n------------------------------------------------------------------------------------------------------------------\r\n03\/11\/2007 Feature: Added folding for Workspace explorer window. Syntax highlighting added to make the Workspace Explorer window nicer to use.\r\n------------------------------------------------------------------------------------------------------------------\r\n04\/11\/2007 Bug Fix: While you had a workspace loaded  then a change to any of the project files\r\nwould NOT force an update of the workspace explorer on the next window refresh. This has now been fixed. What hasn't been 'fixed' is that you need to press CTRL-W a few times  to force the workspace window to refresh.\r\n---------------------------------------------------------------------------------------------------------------------\r\n05\/11\/2007 Feature Tweak: Selecting a file in the workspace explorer and pressing <CR>,<TAB> or double-clicking to edit the file only worked in normal mode, now it also works in insert mode too. \r\nI just don't want to keep pressing <Esc> and THEN select a new file to edit , I prefer to just select and edit. \r\n----------------------------------------------------------------------------------------------------------------------\r\n10\/11\/2007 Feature Tweak (v0.32): It was a bit annoying that files displayed in the workspace were displayed in a random order. This has been fixed, now they are displayed in alphabetic order ( almost , uppercase takes precendant over lower case so 'Z' before 'a').            \r\nBug Fix (v0.33):Every time there was a change to any of the modification times of any of the projects in the workspace, everything in the workspace window would get folded up. This was really annoying as my makefile creates a project file on the fly and every time make was run everything would get folded up. This has now been fixed.                                                         \r\n----------------------------------------------------------------------------------------------------------------------- \r\n12\/11\/07 Bug FIx : Files failed to open for edit if they were in the same directory as the workspace file and project file , and the the cwd was not the directory containing the workspace file.\r\n-----------------------------------------------------------------------------------------------------------------------  \r\n24\/04\/08 v0.33.2 Minor Bug fix. Thanks to Wang Danqi for the bug report \r\n         and bug fix. The following is an extract from the report.\r\n         \"..when I installed the script in my vim plugin directory and\r\n         launch winmanager, I got a error report. Finally I found the\r\n         error was occured by line 90 in winwkspaceexplorer.vim, in \r\n             function! WKSpaceExplorer_Start():\r\n               call s:EditWKS(getcwd().\"\/\".fnamemodify(getcwd(),\":t:r\")i.g:wksExtension)\r\n         I changed it to \r\n               call s:EditWKS(getcwd().\"\/\".fnamemodify(getcwd(),\":t:r\").g:wksExtension)\r\n         by delete the character 'i' and it now works smothly.\" - Wang Danqi\r\n\r\n-----------------------------------------------------------------------------------------------------------------------  \r\n\r\n\r\n","4":"Many IDEs make it easy to organise source files into projects. Some IDEs then make it easy to organise projects into workspaces which can be explored. This is very useful for related projects where one may be an executable and another a required library. Code::Blocks is a very good examples of such an IDE. This is a feature that this plugin attempts to mimic inside the vim plugin winmanager. winmanager makes it incredibly easy to write such plugins (although the availability of an  example would be much appreciated).\r\n\r\nThere are however major differences between what this plugin attempts to achieve and what the workspace\/solution explorers in other IDEs give you. Classic IDE project explorers also give you access to build options and 'project settings', essentially configurations that would normally be within the scope of a makefile. winworkspaceexlporer does not attempt to do the this. It would not be appropriate. Most people coding with vim would probably be using 'make' or one of its many variants or replacements ( I use Scons ). It is more natural to edit the equivalent of the makefile directly in vim. Adding, deleting files to a project does not need to be supported in a plugin like this as these changes would be carried out directly in the makefile-like file. Whilst I do not require IDE workspace-explorer capabilities to set project options, compiler flags , link flags etc, I did have a need for a workspace-explorer-like plugin for vim that would simply let me explore the project files and organise them conveniently, hence winwkspaceexplorer.\r\n\r\nThe preferred way to generate the winwkspaceexplorer PROJECT files would be as additional targets in the makefile. I use SCons ( replacement for make)  and on Windows the project file for a popular  IDE gets created on the fly during the build process by code in the sconscript file ( Scons version of a makefile)(Scons actualy has this feature builtin). Similarly on Linux and Cygwin a winwkspaceexplorer project file is generated on the fly by the same sconscript file.\r\n\r\nThere are alternatives such as the script found at  http:\/\/www.vim.org\/scripts\/script.php?script_id=69. This is a very good plugin and definitely worth trying out. However I needed something that I could use with the winmanager, which is my first choice for the foundation of a very good IDE.  \r\n\r\nThis plugin is in early stages but, for me very useable. There are many more things that can be added easily. I am however keen to keep the plugin minimalist and most importantly do not want to duplicate any functionality  between winwkspaceexplorer and the makefile. \r\n\r\n\r\n\r\nPlease send any comments, suggestions,  or bugs to narinder_claireATyahoo.co.uk\r\n\r\n[NOTE]:  There are 2 entries for the winmanager plugin on vim.org. The original :\r\n                              http:\/\/www.vim.org\/scripts\/script.php?script_id=95\r\n               and its descendant \r\n                              http:\/\/www.vim.org\/scripts\/script.php?script_id=1440\r\n               I use the latter as its a continuation of the first and contains bugfixes.\r\n               To understand why there are two entries read the notes for the latter.\r\n\r\n \r\n\r\n================================================\r\nCHANGE LOG\r\n================================================\r\n02\/11\/2007 initial upload\r\n------------------------------------------------------------------------------------------------------------------\r\n03\/11\/2007 Feature: Added folding for Workspace explorer window. Syntax highlighting added to make the Workspace Explorer window nicer to use.\r\n------------------------------------------------------------------------------------------------------------------\r\n04\/11\/2007 Bug Fix: While you had a workspace loaded  then a change to any of the project files\r\nwould NOT force an update of the workspace explorer on the next window refresh. This has now been fixed. What hasn't been 'fixed' is that you need to press CTRL-W a few times  to force the workspace window to refresh.\r\n---------------------------------------------------------------------------------------------------------------------\r\n05\/11\/2007 Feature Tweak: Selecting a file in the workspace explorer and pressing <CR>,<TAB> or double-clicking to edit the file only worked in normal mode, now it also works in insert mode too. \r\nI just don't want to keep pressing <Esc> and THEN select a new file to edit , I prefer to just select and edit. \r\n----------------------------------------------------------------------------------------------------------------------\r\n10\/11\/2007 Feature Tweak (v0.32): It was a bit annoying that files displayed in the workspace were displayed in a random order. This has been fixed, now they are displayed in alphabetic order ( almost , uppercase takes precendant over lower case so 'Z' before 'a').            \r\nBug Fix (v0.33):Every time there was a change to any of the modification times of any of the projects in the workspace, everything in the workspace window would get folded up. This was really annoying as my makefile creates a project file on the fly and every time make was run everything would get folded up. This has now been fixed.                                                         \r\n----------------------------------------------------------------------------------------------------------------------- \r\n12\/11\/07 Bug FIx : Files failed to open for edit if they were in the same directory as the workspace file and project file , and the the cwd was not the directory containing the workspace file.\r\n-----------------------------------------------------------------------------------------------------------------------  \r\n24\/04\/08 v0.33.2 Minor Bug fix. Thanks to Wang Danqi for the bug report \r\n         and bug fix. The following is an extract from the report.\r\n         \"..when I installed the script in my vim plugin directory and\r\n         launch winmanager, I got a error report. Finally I found the\r\n         error was occured by line 90 in winwkspaceexplorer.vim, in \r\n             function! WKSpaceExplorer_Start():\r\n               call s:EditWKS(getcwd().\"\/\".fnamemodify(getcwd(),\":t:r\")i.g:wksExtension)\r\n         I changed it to \r\n               call s:EditWKS(getcwd().\"\/\".fnamemodify(getcwd(),\":t:r\").g:wksExtension)\r\n         by delete the character 'i' and it now works smothly.\" - Wang Danqi\r\n\r\n-----------------------------------------------------------------------------------------------------------------------  \r\n\r\n\r\n","install_details":"The plugin 'winmanager' needs to be installed. The required version is 2.34 and is available for download from  http:\/\/www.vim.org\/scripts\/script.php?script_id=1440 \r\n\r\nThe plugin 'bufexplorer' is recommended and can be downloaded from http:\/\/www.vim.org\/scripts\/script.php?script_id=42\r\n\r\nTo install winworkspaceexplorer just unzip winwksexplorer.zip into ~\/.vim or\r\nwhere ever the plugins are located. This will decompress the files \r\n\r\nplugin\/winwkspaceexplorer.vim\r\ndoc\/winwkspaceexplorer.txt\r\n\r\nIf your download includes the example then it will decompress into \r\n\r\nplugin\/winwkspaceexplorer.vim\r\ndoc\/winwkspaceexplorer.txt\r\nwksExample.zip\r\n\r\nMove wksExample.zip to somewhere else such as your temporary directory, unzip it and change to the unzipped directory wksExample. Then on entering vim you can enter the command \r\n\r\n               WKSpace example.vimwks\r\n\r\nThe example is for the gnu toolset. \r\n............................................................................................\r\n\r\nThis plugin seems to work fine under Windows.","5":"The plugin 'winmanager' needs to be installed. The required version is 2.34 and is available for download from  http:\/\/www.vim.org\/scripts\/script.php?script_id=1440 \r\n\r\nThe plugin 'bufexplorer' is recommended and can be downloaded from http:\/\/www.vim.org\/scripts\/script.php?script_id=42\r\n\r\nTo install winworkspaceexplorer just unzip winwksexplorer.zip into ~\/.vim or\r\nwhere ever the plugins are located. This will decompress the files \r\n\r\nplugin\/winwkspaceexplorer.vim\r\ndoc\/winwkspaceexplorer.txt\r\n\r\nIf your download includes the example then it will decompress into \r\n\r\nplugin\/winwkspaceexplorer.vim\r\ndoc\/winwkspaceexplorer.txt\r\nwksExample.zip\r\n\r\nMove wksExample.zip to somewhere else such as your temporary directory, unzip it and change to the unzipped directory wksExample. Then on entering vim you can enter the command \r\n\r\n               WKSpace example.vimwks\r\n\r\nThe example is for the gnu toolset. \r\n............................................................................................\r\n\r\nThis plugin seems to work fine under Windows.","first_name":"Narinder","6":"Narinder","last_name":"Claire","7":"Claire","releases":[{"0":"2060","vim_version":"7.0","1":"7.0","script_version":"0.33.2+eg","2":"0.33.2+eg","version_comment":"Minor Bug fix. Thanks to Wang Danqi for the bug report and bug fix.","3":"Minor Bug fix. Thanks to Wang Danqi for the bug report and bug fix.","package":"winwksexplorer.zip","4":"winwksexplorer.zip","src_id":"8602","5":"8602","creation_date":"1209029158","6":"1209029158"},{"0":"2060","vim_version":"7.0","1":"7.0","script_version":"0.33.1+e.g","2":"0.33.1+e.g","version_comment":"Minor Bug fix. If the current working directory was not the same as the directory containing the loaded .vimwks file and there was a .vimprj file in that same directory, then files that were also in the current working directory would not open. Now fixed.\r\n","3":"Minor Bug fix. If the current working directory was not the same as the directory containing the loaded .vimwks file and there was a .vimprj file in that same directory, then files that were also in the current working directory would not open. Now fixed.\r\n","package":"winwksexplorer.zip","4":"winwksexplorer.zip","src_id":"7942","5":"7942","creation_date":"1194883107","6":"1194883107"},{"0":"2060","vim_version":"7.0","1":"7.0","script_version":"0.33+exmpl","2":"0.33+exmpl","version_comment":"v0.33 with an example workspace.\r\nOn unzipping the zip file to install there will be an additional zip file 'wksExample.zip'. Move this somewhere else and unzip it. Then  cd to the new unzipped directory 'wksExample'. \r\nEnter vim ( or gvim) then run the command ':WKSpace example.vimwks'\r\n\r\nThe example is only for the gnu toolset, but could easily be modified for other toolsets.\r\n\r\n\r\n","3":"v0.33 with an example workspace.\r\nOn unzipping the zip file to install there will be an additional zip file 'wksExample.zip'. Move this somewhere else and unzip it. Then  cd to the new unzipped directory 'wksExample'. \r\nEnter vim ( or gvim) then run the command ':WKSpace example.vimwks'\r\n\r\nThe example is only for the gnu toolset, but could easily be modified for other toolsets.\r\n\r\n\r\n","package":"winwksexplorer.zip","4":"winwksexplorer.zip","src_id":"7923","5":"7923","creation_date":"1194674231","6":"1194674231"}]},"2059":{"script_id":"2059","0":"2059","script_name":"matchparen++","1":"matchparen++","script_type":"utility","2":"utility","summary":"Improvement over standard matchparen plugin","3":"Improvement over standard matchparen plugin","description":"Improves over standard matchparen.vim plugin by echoing line containing matching bracket in the status line so you can quickly see which block is terminated by this paren.  Also scans for braces\/parens which are off-screen.\r\n\r\nIf you write functions or blocks like this:\r\nif (condition)\r\n{\r\n    ...\r\n}\r\nthe plugin will echo the line \"if (condition)\" and not the lone \"{\".\r\nBy default, the plugin scans the line containing the opening brace and the two lines above that, looking for the statement that begins the block, be it a loop or function definition.  If you want more or less, set it in the variable g:MP_stmt_thresh.\r\n","4":"Improves over standard matchparen.vim plugin by echoing line containing matching bracket in the status line so you can quickly see which block is terminated by this paren.  Also scans for braces\/parens which are off-screen.\r\n\r\nIf you write functions or blocks like this:\r\nif (condition)\r\n{\r\n    ...\r\n}\r\nthe plugin will echo the line \"if (condition)\" and not the lone \"{\".\r\nBy default, the plugin scans the line containing the opening brace and the two lines above that, looking for the statement that begins the block, be it a loop or function definition.  If you want more or less, set it in the variable g:MP_stmt_thresh.\r\n","install_details":"Copy file to $HOME\/.vim\/plugin or $HOME\/vimfiles\/plugin.  Since your local plugins directory is searched before the one in $VIM, it will disable loading of the standard matchparen.vim plugin.  If you install it somewhere else, the standard plugin could be found before this one and be loaded instead.","5":"Copy file to $HOME\/.vim\/plugin or $HOME\/vimfiles\/plugin.  Since your local plugins directory is searched before the one in $VIM, it will disable loading of the standard matchparen.vim plugin.  If you install it somewhere else, the standard plugin could be found before this one and be loaded instead.","first_name":"erik","6":"erik","last_name":"falor","7":"falor","releases":[{"0":"2059","vim_version":"7.0","1":"7.0","script_version":"1.0.3","2":"1.0.3","version_comment":"Ingo Karkat has pointed out a bug brought about by Vim 8.1.0112:                                            \r\n  \"Recent Vim versions have tightened the accepted arguments for searchpair[pos]()\r\n  The fix (also taken from the latest matchparen.vim) is easy: Pass a String-type \"0\" instead of the number 0 in s_skip\"","3":"Ingo Karkat has pointed out a bug brought about by Vim 8.1.0112:                                            \r\n  \"Recent Vim versions have tightened the accepted arguments for searchpair[pos]()\r\n  The fix (also taken from the latest matchparen.vim) is easy: Pass a String-type \"0\" instead of the number 0 in s_skip\"","package":"matchparen++.vim","4":"matchparen++.vim","src_id":"26121","5":"26121","creation_date":"1531138916","6":"1531138916"},{"0":"2059","vim_version":"7.0","1":"7.0","script_version":"1.0.2","2":"1.0.2","version_comment":"DoMatchParen command re-loads this plugin instead of matchparen.vim.\r\nThanks to James Marshall for this idea.\r\n","3":"DoMatchParen command re-loads this plugin instead of matchparen.vim.\r\nThanks to James Marshall for this idea.\r\n","package":"matchparen++.vim","4":"matchparen++.vim","src_id":"8542","5":"8542","creation_date":"1207818930","6":"1207818930"},{"0":"2059","vim_version":"7.0","1":"7.0","script_version":"1.0.1","2":"1.0.1","version_comment":"Using timeout feature of searchpairpos() to avoid a long delay while \r\nfinding a matching paren.  Borrowed from Bram's patch #7.1.269.\r\nAlso accommodates Vim users who don't have the latest patches compiled.","3":"Using timeout feature of searchpairpos() to avoid a long delay while \r\nfinding a matching paren.  Borrowed from Bram's patch #7.1.269.\r\nAlso accommodates Vim users who don't have the latest patches compiled.","package":"matchparen++.vim","4":"matchparen++.vim","src_id":"8466","5":"8466","creation_date":"1205919395","6":"1205919395"},{"0":"2059","vim_version":"7.0","1":"7.0","script_version":"0.1.99","2":"0.1.99","version_comment":"Using Bram's matchparen.vim plugin from standard distribution as starting point for this version.  \r\n                                                                                 \r\nPrint line containing matching brace with echo instead of echomsg so as to not fill message history with non-message items.\r\n                                                                                 \r\nTruncate matching brace line when it's gonna be too long - this avoids the dreaded \"Press ENTER or type command to continue\" message that would be so disruptive to workflow.\r\n                                                                                 \r\nTo do this, the plugin must take the &showcmd, &ruler and &laststatus options into consideration.  If you use a custom &rulerformat, you will want to set the global variable g:MP_rulerwidth to the width of your ruler.\r\n                                                                                 \r\nThe variable g:MP_stmt_thresh lets the user specify how far back the plugin may scan for a statement beginning a code block.\r\n","3":"Using Bram's matchparen.vim plugin from standard distribution as starting point for this version.  \r\n                                                                                 \r\nPrint line containing matching brace with echo instead of echomsg so as to not fill message history with non-message items.\r\n                                                                                 \r\nTruncate matching brace line when it's gonna be too long - this avoids the dreaded \"Press ENTER or type command to continue\" message that would be so disruptive to workflow.\r\n                                                                                 \r\nTo do this, the plugin must take the &showcmd, &ruler and &laststatus options into consideration.  If you use a custom &rulerformat, you will want to set the global variable g:MP_rulerwidth to the width of your ruler.\r\n                                                                                 \r\nThe variable g:MP_stmt_thresh lets the user specify how far back the plugin may scan for a statement beginning a code block.\r\n","package":"matchparen++.vim","4":"matchparen++.vim","src_id":"7881","5":"7881","creation_date":"1194268877","6":"1194268877"},{"0":"2059","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"matchparen++.vim","4":"matchparen++.vim","src_id":"7857","5":"7857","creation_date":"1193928452","6":"1193928452"}]},"2058":{"script_id":"2058","0":"2058","script_name":"PropBank Semantic Role Annotations","1":"PropBank Semantic Role Annotations","script_type":"syntax","2":"syntax","summary":"Syntax highlighting for PropBank Semantic Role Annotations","3":"Syntax highlighting for PropBank Semantic Role Annotations","description":"Syntax highlighting for PropBank Semantic Role Annotations. \r\n[http:\/\/www.cs.rochester.edu\/~gildea\/PropBank\/Sort\/]\r\n\r\nThe highlighting patterns are based on the following css:\r\n[http:\/\/www.cs.rochester.edu\/~gildea\/pb_style.css]\r\n\r\nScreenshot: [http:\/\/wuzhaojun.googlepages.com\/propbank.png]","4":"Syntax highlighting for PropBank Semantic Role Annotations. \r\n[http:\/\/www.cs.rochester.edu\/~gildea\/PropBank\/Sort\/]\r\n\r\nThe highlighting patterns are based on the following css:\r\n[http:\/\/www.cs.rochester.edu\/~gildea\/pb_style.css]\r\n\r\nScreenshot: [http:\/\/wuzhaojun.googlepages.com\/propbank.png]","install_details":"1. download and store it in ~\/.vim\/syntax\/;\r\n2. enter \":setfiletype propbank\" to apply it on current window.","5":"1. download and store it in ~\/.vim\/syntax\/;\r\n2. enter \":setfiletype propbank\" to apply it on current window.","first_name":"Zhaojun","6":"Zhaojun","last_name":"WU","7":"WU","releases":[{"0":"2058","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"propbank.vim","4":"propbank.vim","src_id":"7849","5":"7849","creation_date":"1193815358","6":"1193815358"}]},"2057":{"script_id":"2057","0":"2057","script_name":"soso.vim","1":"soso.vim","script_type":"color scheme","2":"color scheme","summary":"Color scheme with light-gray background that supports Vim7 highlight groups","3":"Color scheme with light-gray background that supports Vim7 highlight groups","description":"This is a color scheme with light-gray background ideal for programming. Highlighted items have dark colors to please the eyes but provide enough contrast to distinguish between them.\r\nVim7 highlight groups are supported, e.g. tab line, completion menu, spelling, and paren matching.\r\nTogether with the ShowPairs plugin (vimscript #626) this color scheme provides highlighting for being inside matching parens (light green background) or exactly on a paren (emphasized light green background).\r\nWorks for GUI and CTerm.","4":"This is a color scheme with light-gray background ideal for programming. Highlighted items have dark colors to please the eyes but provide enough contrast to distinguish between them.\r\nVim7 highlight groups are supported, e.g. tab line, completion menu, spelling, and paren matching.\r\nTogether with the ShowPairs plugin (vimscript #626) this color scheme provides highlighting for being inside matching parens (light green background) or exactly on a paren (emphasized light green background).\r\nWorks for GUI and CTerm.","install_details":"Copy this file to your $VIMRUNTIME\/colors\/ or $HOME\/.vim\/colors\/ directory. Then type :colors soso","5":"Copy this file to your $VIMRUNTIME\/colors\/ or $HOME\/.vim\/colors\/ directory. Then type :colors soso","first_name":"Soeren","6":"Soeren","last_name":"Sonntag","7":"Sonntag","releases":[{"0":"2057","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"soso.vim","4":"soso.vim","src_id":"7848","5":"7848","creation_date":"1193789039","6":"1193789039"}]},"2056":{"script_id":"2056","0":"2056","script_name":"please remove me","1":"please remove me","script_type":"utility","2":"utility","summary":"please remove me","3":"please remove me","description":"please use vimscript #2055 instead. This was posted twice.","4":"please use vimscript #2055 instead. This was posted twice.","install_details":"","5":"","first_name":"Tom","6":"Tom","last_name":"Link","7":"Link","releases":[{"0":"2056","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"ttagecho.vba.gz","4":"ttagecho.vba.gz","src_id":"7845","5":"7845","creation_date":"1193700544","6":"1193700544"}]},"2055":{"script_id":"2055","0":"2055","script_name":"ttagecho","1":"ttagecho","script_type":"utility","2":"utility","summary":"Show current tag information","3":"Show current tag information","description":"This plugin is similar to echofunc (vimscript #1735) to which it owes \r\nmuch inspiration and two lines of code. echofunc is probably also better \r\ntested.\r\n\r\nIt displays some information about the tag under the cursor or mouse \r\npointer either in the echo area or as balloon help (see \r\n|g:ttagecho_balloon_patterns|). If there are more than one tags that \r\nmatch, you can loop through the tags by invoking the respective commands \r\nrepeatedly.\r\n\r\nIf hookcursormoved (vimscript #2037, version >= 0.4) is installed, for \r\ncertain filetypes (see |g:ttagecho_parentheses_patterns|) it will \r\ndisplay the information in the echo area also if the cursor moves over a \r\nround parenthesis.\r\n\r\nIf you don't like the default format for the tags, you can define the \r\nfunction TTagechoFormat_{&filetype}(a:tag) that should return some nicely \r\nformatted information.\r\n","4":"This plugin is similar to echofunc (vimscript #1735) to which it owes \r\nmuch inspiration and two lines of code. echofunc is probably also better \r\ntested.\r\n\r\nIt displays some information about the tag under the cursor or mouse \r\npointer either in the echo area or as balloon help (see \r\n|g:ttagecho_balloon_patterns|). If there are more than one tags that \r\nmatch, you can loop through the tags by invoking the respective commands \r\nrepeatedly.\r\n\r\nIf hookcursormoved (vimscript #2037, version >= 0.4) is installed, for \r\ncertain filetypes (see |g:ttagecho_parentheses_patterns|) it will \r\ndisplay the information in the echo area also if the cursor moves over a \r\nround parenthesis.\r\n\r\nIf you don't like the default format for the tags, you can define the \r\nfunction TTagechoFormat_{&filetype}(a:tag) that should return some nicely \r\nformatted information.\r\n","install_details":"Edit the vba file and type: >\r\n\r\n    :so %\r\n\r\nSee :help vimball for details. If you have difficulties or use vim 7.0, \r\nplease make sure, you have the current version of vimball (vimscript \r\n#1502) installed.\r\n\r\nSuggested maps (to be set in ~\/.vimrc): >\r\n    noremap <Leader>g+ :TTagechoWord<cr>\r\n    noremap <Leader>g* :TTagechoWord!<cr>\r\n    noremap <Leader>g? :TTagechoWords!<cr>\r\n\r\nSuggested enhancement:\r\n    hookcursormoved (vimscript #2037)\r\n\r\n\r\nAlso available via git\r\nhttp:\/\/github.com\/tomtom\/ttagecho_vim","5":"Edit the vba file and type: >\r\n\r\n    :so %\r\n\r\nSee :help vimball for details. If you have difficulties or use vim 7.0, \r\nplease make sure, you have the current version of vimball (vimscript \r\n#1502) installed.\r\n\r\nSuggested maps (to be set in ~\/.vimrc): >\r\n    noremap <Leader>g+ :TTagechoWord<cr>\r\n    noremap <Leader>g* :TTagechoWord!<cr>\r\n    noremap <Leader>g? :TTagechoWords!<cr>\r\n\r\nSuggested enhancement:\r\n    hookcursormoved (vimscript #2037)\r\n\r\n\r\nAlso available via git\r\nhttp:\/\/github.com\/tomtom\/ttagecho_vim","first_name":"Tom","6":"Tom","last_name":"Link","7":"Link","releases":[{"0":"2055","vim_version":"7.0","1":"7.0","script_version":"0.6","2":"0.6","version_comment":"- NEW: g:ttagecho_char_rx: custom keyword char regexp\r\n- Always use compact style when there is only one tag that matches and if many_lines < 0\r\n- Find the right keyword, when the current line contains more than one","3":"- NEW: g:ttagecho_char_rx: custom keyword char regexp\r\n- Always use compact style when there is only one tag that matches and if many_lines < 0\r\n- Find the right keyword, when the current line contains more than one","package":"ttagecho.vba.gz","4":"ttagecho.vba.gz","src_id":"11544","5":"11544","creation_date":"1255877605","6":"1255877605"},{"0":"2055","vim_version":"7.0","1":"7.0","script_version":"0.5","2":"0.5","version_comment":"- Make sure tlib is loaded even if it is installed in a different rtp-directory (thanks to ... sorry, cannot find the e-mail)\r\n- Use tlib#notify#TrimMessage() (thanks to Erik Falor)\r\n","3":"- Make sure tlib is loaded even if it is installed in a different rtp-directory (thanks to ... sorry, cannot find the e-mail)\r\n- Use tlib#notify#TrimMessage() (thanks to Erik Falor)\r\n","package":"ttagecho.vba.gz","4":"ttagecho.vba.gz","src_id":"9311","5":"9311","creation_date":"1223199933","6":"1223199933"},{"0":"2055","vim_version":"7.0","1":"7.0","script_version":"0.4","2":"0.4","version_comment":"- Adapt for hookcursormoved >= 0.7\r\n","3":"- Adapt for hookcursormoved >= 0.7\r\n","package":"ttagecho.vba.gz","4":"ttagecho.vba.gz","src_id":"7981","5":"7981","creation_date":"1195642835","6":"1195642835"},{"0":"2055","vim_version":"7.0","1":"7.0","script_version":"0.3","2":"0.3","version_comment":"- Customize display: g:ttagecho_tagwidth\r\n- g:ttagecho_matchbeginning\r\n- Check for has('balloon_eval')\r\n- Restore showmode only on InsertLeave events (not on CursorHold(I) events).\r\n- Check only opening parentheses (require hookcursormoved 0.5)\r\n- Use [bg]:tlib_tags_extra if defined.\r\n- Require tlib >= 0.20\r\n- g:ttagecho_substitute became g:tlib_tag_substitute\r\n- Removed support for: [bg]:ttagecho_more_tags (use [bg]:tlib_tags_extra \r\ninstead)\r\n","3":"- Customize display: g:ttagecho_tagwidth\r\n- g:ttagecho_matchbeginning\r\n- Check for has('balloon_eval')\r\n- Restore showmode only on InsertLeave events (not on CursorHold(I) events).\r\n- Check only opening parentheses (require hookcursormoved 0.5)\r\n- Use [bg]:tlib_tags_extra if defined.\r\n- Require tlib >= 0.20\r\n- g:ttagecho_substitute became g:tlib_tag_substitute\r\n- Removed support for: [bg]:ttagecho_more_tags (use [bg]:tlib_tags_extra \r\ninstead)\r\n","package":"ttagecho.vba.gz","4":"ttagecho.vba.gz","src_id":"7938","5":"7938","creation_date":"1194863017","6":"1194863017"},{"0":"2055","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"ttagecho.vba.gz","4":"ttagecho.vba.gz","src_id":"7843","5":"7843","creation_date":"1193700342","6":"1193700342"}]},"2054":{"script_id":"2054","0":"2054","script_name":"TranslateIt","1":"TranslateIt","script_type":"utility","2":"utility","summary":"Translate a word under cursor using custom dictionary utility","3":"Translate a word under cursor using custom dictionary utility","description":"This script looks up a word under cursor in a dictionary using custom utility such as sdcv (console version of StarDict program)\r\n","4":"This script looks up a word under cursor in a dictionary using custom utility such as sdcv (console version of StarDict program)\r\n","install_details":"Put this file into your $HOME\/.vim\/plugin directory.\r\n","5":"Put this file into your $HOME\/.vim\/plugin directory.\r\n","first_name":"pento","6":"pento","last_name":"pento","7":"pento","releases":[{"0":"2054","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"translateit.vim","4":"translateit.vim","src_id":"7836","5":"7836","creation_date":"1193398285","6":"1193398285"}]},"2053":{"script_id":"2053","0":"2053","script_name":"asmc54xx","1":"asmc54xx","script_type":"syntax","2":"syntax","summary":"TI DSP Assembler for the C54xx family","3":"TI DSP Assembler for the C54xx family","description":"Basic assembler support for the C54xx DSP chip family from TI.","4":"Basic assembler support for the C54xx DSP chip family from TI.","install_details":"Just unpack the archive in your .vim (unix) or vimfiles (windows) directory.\r\nIf you want the syntax automaticaly loaded for *.s54 files, add the following in your filetype.vim (in .vim): \r\nau BufNewFile,BufRead *.s54\t\t\tsetf asmc54xx","5":"Just unpack the archive in your .vim (unix) or vimfiles (windows) directory.\r\nIf you want the syntax automaticaly loaded for *.s54 files, add the following in your filetype.vim (in .vim): \r\nau BufNewFile,BufRead *.s54\t\t\tsetf asmc54xx","first_name":"Gerd","6":"Gerd","last_name":"Wiegand","7":"Wiegand","releases":[{"0":"2053","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"asmc54xx.zip","4":"asmc54xx.zip","src_id":"7833","5":"7833","creation_date":"1193361113","6":"1193361113"}]},"2052":{"script_id":"2052","0":"2052","script_name":"idlang.vim","1":"idlang.vim","script_type":"syntax","2":"syntax","summary":"Vim syntax file for IDL 7.0","3":"Vim syntax file for IDL 7.0","description":"idlang.vim provides basic syntax support for IDL 7.0, it is based on the syntax file  included in vim-7.1.tar.bz2.","4":"idlang.vim provides basic syntax support for IDL 7.0, it is based on the syntax file  included in vim-7.1.tar.bz2.","install_details":"Like a standard syntax file.","5":"Like a standard syntax file.","first_name":"Hayato","6":"Hayato","last_name":"Mikami","7":"Mikami","releases":[{"0":"2052","vim_version":"7.0","1":"7.0","script_version":"0.2","2":"0.2","version_comment":"Add new IDL Routines, \"GET_LOGIN_INFO\", \"MAKE_RT\", and \"ROUTINE_FILEPATH\".\r\n\r\n","3":"Add new IDL Routines, \"GET_LOGIN_INFO\", \"MAKE_RT\", and \"ROUTINE_FILEPATH\".\r\n\r\n","package":"idlang.vim","4":"idlang.vim","src_id":"9120","5":"9120","creation_date":"1218629124","6":"1218629124"},{"0":"2052","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"idlang.vim","4":"idlang.vim","src_id":"7830","5":"7830","creation_date":"1193354181","6":"1193354181"}]},"2051":{"script_id":"2051","0":"2051","script_name":"enscript-highlight","1":"enscript-highlight","script_type":"syntax","2":"syntax","summary":"EnScript Syntax HighLighting","3":"EnScript Syntax HighLighting","description":"This plugin adds syntax highlighting for Encase Scripts (aka enscript files).\r\n\r\nActually it is a modified version of the cpp.vim module, but I'm planning to add autocompletion and more fixups.\r\n\r\nPlease. Feel free to send me patches and bug reports to: g??cnapnxr@lbhgrez.pbz","4":"This plugin adds syntax highlighting for Encase Scripts (aka enscript files).\r\n\r\nActually it is a modified version of the cpp.vim module, but I'm planning to add autocompletion and more fixups.\r\n\r\nPlease. Feel free to send me patches and bug reports to: g??cnapnxr@lbhgrez.pbz","install_details":"On w32:\r\n - Copy the vimfiles\/ directory into your vim home.\r\n - Copy enscript.vim into your vim's home\r\n - Add this line to your vimrc: (_vimrc on w32):\r\n   source \/path\/to\/vim\/enscript.vim\r\n\r\nThere's a sample vimrc that you can get it if you want to test my vim configuration :)","5":"On w32:\r\n - Copy the vimfiles\/ directory into your vim home.\r\n - Copy enscript.vim into your vim's home\r\n - Add this line to your vimrc: (_vimrc on w32):\r\n   source \/path\/to\/vim\/enscript.vim\r\n\r\nThere's a sample vimrc that you can get it if you want to test my vim configuration :)","first_name":"( pancake","6":"( pancake","last_name":")","7":")","releases":[{"0":"2051","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"VimEnscript.rar","4":"VimEnscript.rar","src_id":"7825","5":"7825","creation_date":"1193199687","6":"1193199687"}]},"2050":{"script_id":"2050","0":"2050","script_name":"LustyJuggler","1":"LustyJuggler","script_type":"utility","2":"utility","summary":"Switch very quickly among your active buffers","3":"Switch very quickly among your active buffers","description":"*** Download the newest version of this plugin on Github: https:\/\/github.com\/sjbach\/lusty ***\r\n\r\nLustyJuggler is a high speed buffer juggler.  Having to consciously think about which buffer you need to switch to sucks, so use this instead.\r\n\r\nSomeone made a screen cast showing it in action (jump to 6:20):\r\n\r\n      http:\/\/lococast.net\/archives\/185\r\n\r\n      Also, a quick video demo:\r\n      http:\/\/www.youtube.com\/watch?v=vQuF0Vm0EG4\r\n\r\n      Older stuff:\r\n      http:\/\/sjbach.com\/lusty-juggler-animated.gif\r\n      http:\/\/sjbach.com\/lusty-juggler-annotated.png\r\n\r\nLaunch the juggler with this key combo:\r\n\r\n      <Leader>lj\r\n\r\nThe command bar at bottom is replaced with a new bar showing the names of your currently opened buffers in most-recently-used order.\r\n\r\nThe buffer names are mapped to these keys:\r\n\r\n      1st --> a or 1\r\n      2nd --> s or 2\r\n      3rd --> d or 3\r\n      4th --> f or 4\r\n      5th --> g or 5\r\n      6th --> h or 6\r\n      7th --> j or 7\r\n      8th --> k or 8\r\n      9th --> l or 9\r\n      10th --> ; or 0\r\n\r\nSo if you type \"f\" or \"4\", the fourth buffer name will be highlighted and the bar will shift to center it as necessary (and show more of the buffer names on the right).\r\n\r\nIf you want to switch to that buffer, press \"f\" or \"4\" again or press \"<ENTER>\".  Alternatively, press one of the other mapped keys to highlight another buffer.\r\n\r\nIf you changed your mind, cancel the juggler with any of \"q\", \"<ESC>\", \"<C-c\", \"<BS>\", \"<Del>\", or \"<C-h>\".\r\n\r\nIf you like LustyJuggler, you may also like LustyExplorer: vimscript #1890\r\n\r\nDevelopment repository: http:\/\/github.com\/sjbach\/lusty","4":"*** Download the newest version of this plugin on Github: https:\/\/github.com\/sjbach\/lusty ***\r\n\r\nLustyJuggler is a high speed buffer juggler.  Having to consciously think about which buffer you need to switch to sucks, so use this instead.\r\n\r\nSomeone made a screen cast showing it in action (jump to 6:20):\r\n\r\n      http:\/\/lococast.net\/archives\/185\r\n\r\n      Also, a quick video demo:\r\n      http:\/\/www.youtube.com\/watch?v=vQuF0Vm0EG4\r\n\r\n      Older stuff:\r\n      http:\/\/sjbach.com\/lusty-juggler-animated.gif\r\n      http:\/\/sjbach.com\/lusty-juggler-annotated.png\r\n\r\nLaunch the juggler with this key combo:\r\n\r\n      <Leader>lj\r\n\r\nThe command bar at bottom is replaced with a new bar showing the names of your currently opened buffers in most-recently-used order.\r\n\r\nThe buffer names are mapped to these keys:\r\n\r\n      1st --> a or 1\r\n      2nd --> s or 2\r\n      3rd --> d or 3\r\n      4th --> f or 4\r\n      5th --> g or 5\r\n      6th --> h or 6\r\n      7th --> j or 7\r\n      8th --> k or 8\r\n      9th --> l or 9\r\n      10th --> ; or 0\r\n\r\nSo if you type \"f\" or \"4\", the fourth buffer name will be highlighted and the bar will shift to center it as necessary (and show more of the buffer names on the right).\r\n\r\nIf you want to switch to that buffer, press \"f\" or \"4\" again or press \"<ENTER>\".  Alternatively, press one of the other mapped keys to highlight another buffer.\r\n\r\nIf you changed your mind, cancel the juggler with any of \"q\", \"<ESC>\", \"<C-c\", \"<BS>\", \"<Del>\", or \"<C-h>\".\r\n\r\nIf you like LustyJuggler, you may also like LustyExplorer: vimscript #1890\r\n\r\nDevelopment repository: http:\/\/github.com\/sjbach\/lusty","install_details":"Copy the plugin\/ and autoload\/ directories into your $HOME\/.vim\/ directory.\r\n\r\nNOTE: This plugin requires Vim be compiled with Ruby interpretation.  If you do not currently have this functionality, see the \"Install Details:\" section of the script for directions on adding it.  It's not too tough.\r\n\r\nAlso: prior to Vim 7.3.32, LustyJuggler can interact poorly with plugins such as YankRing or SuperTab that remap common normal mode keys such as \"d\" (for dd, dw, etc.)","5":"Copy the plugin\/ and autoload\/ directories into your $HOME\/.vim\/ directory.\r\n\r\nNOTE: This plugin requires Vim be compiled with Ruby interpretation.  If you do not currently have this functionality, see the \"Install Details:\" section of the script for directions on adding it.  It's not too tough.\r\n\r\nAlso: prior to Vim 7.3.32, LustyJuggler can interact poorly with plugins such as YankRing or SuperTab that remap common normal mode keys such as \"d\" (for dd, dw, etc.)","first_name":"Stephen","6":"Stephen","last_name":"Bach","7":"Bach","releases":[{"0":"2050","vim_version":"7.0","1":"7.0","script_version":"1.6","2":"1.6","version_comment":"Many minor fixes over the last six years.","3":"Many minor fixes over the last six years.","package":"lusty-juggler-1.6.zip","4":"lusty-juggler-1.6.zip","src_id":"26147","5":"26147","creation_date":"1532494632","6":"1532494632"},{"0":"2050","vim_version":"7.0","1":"7.0","script_version":"1.5.1","2":"1.5.1","version_comment":"Fixed \"Missing quote\" error message introduced in v1.5. (Guy Haskin Fernald)","3":"Fixed \"Missing quote\" error message introduced in v1.5. (Guy Haskin Fernald)","package":"lusty-juggler.vim","4":"lusty-juggler.vim","src_id":"17547","5":"17547","creation_date":"1330542116","6":"1330542116"},{"0":"2050","vim_version":"7.0","1":"7.0","script_version":"1.5","2":"1.5","version_comment":"Added support for Dvorak keyboard layout.  Enable it with 'let g:LustyJugglerKeyboardLayout = \"dvorak\"'. (Chris Lasher)","3":"Added support for Dvorak keyboard layout.  Enable it with 'let g:LustyJugglerKeyboardLayout = \"dvorak\"'. (Chris Lasher)","package":"lusty-juggler.vim","4":"lusty-juggler.vim","src_id":"17528","5":"17528","creation_date":"1330140455","6":"1330140455"},{"0":"2050","vim_version":"7.0","1":"7.0","script_version":"1.4","2":"1.4","version_comment":"- Open buffers in a new window split: \"b\" for horizontal, \"v\" for vertical. (Leonid Shevtsov)\r\n- Added arrow key navigation. (Giuseppe Rota)\r\n- Further fixes to saving\/restoring key bindings. (Giuseppe Rota)\r\n- Added g:LustyJugglerDefaultMappings configuration. (G\u00c3\u00b6ran Gustafsson)","3":"- Open buffers in a new window split: \"b\" for horizontal, \"v\" for vertical. (Leonid Shevtsov)\r\n- Added arrow key navigation. (Giuseppe Rota)\r\n- Further fixes to saving\/restoring key bindings. (Giuseppe Rota)\r\n- Added g:LustyJugglerDefaultMappings configuration. (G\u00c3\u00b6ran Gustafsson)","package":"lusty-juggler.vim","4":"lusty-juggler.vim","src_id":"16965","5":"16965","creation_date":"1322250787","6":"1322250787"},{"0":"2050","vim_version":"7.0","1":"7.0","script_version":"1.3","2":"1.3","version_comment":"- 'i' now cancels the juggler rather than putting Vim in an uncertain state. (Thanks to Adam Rutkowski)\r\n- Improve restoring of keymappings for Vim versions >= 7.3.32.  This allows LustyJuggler to be used effectively with e.g. YankRing and SuperTab. (Thanks to Carlo Teubner)","3":"- 'i' now cancels the juggler rather than putting Vim in an uncertain state. (Thanks to Adam Rutkowski)\r\n- Improve restoring of keymappings for Vim versions >= 7.3.32.  This allows LustyJuggler to be used effectively with e.g. YankRing and SuperTab. (Thanks to Carlo Teubner)","package":"lusty-juggler.vim","4":"lusty-juggler.vim","src_id":"15546","5":"15546","creation_date":"1304105013","6":"1304105013"},{"0":"2050","vim_version":"7.0","1":"7.0","script_version":"1.2","2":"1.2","version_comment":"- Don't show unlisted buffers. (Thanks to Johannes Holzfu\u00c3\u009f)\r\n- New Alt-Tab mode to emulate window manager switching.  See g:LustyJugglerAltTabMode in documentation. (Thanks to Martin Wache)\r\n- Save and restore keymappings. (Thanks to Vincent Driessen)","3":"- Don't show unlisted buffers. (Thanks to Johannes Holzfu\u00c3\u009f)\r\n- New Alt-Tab mode to emulate window manager switching.  See g:LustyJugglerAltTabMode in documentation. (Thanks to Martin Wache)\r\n- Save and restore keymappings. (Thanks to Vincent Driessen)","package":"lusty-juggler.vim","4":"lusty-juggler.vim","src_id":"14536","5":"14536","creation_date":"1292555619","6":"1292555619"},{"0":"2050","vim_version":"7.0","1":"7.0","script_version":"1.1.4","2":"1.1.4","version_comment":"- don't error if ENTER is pressed before selection\r\n- avoid a \"Press ENTER to continue\" message.  (Thanks to Bartosz Leper)\r\n- don't error when the QuickFix buffer is open.  (Thanks to Marco Barberis)","3":"- don't error if ENTER is pressed before selection\r\n- avoid a \"Press ENTER to continue\" message.  (Thanks to Bartosz Leper)\r\n- don't error when the QuickFix buffer is open.  (Thanks to Marco Barberis)","package":"lusty-juggler.vim","4":"lusty-juggler.vim","src_id":"13094","5":"13094","creation_date":"1275526713","6":"1275526713"},{"0":"2050","vim_version":"7.0","1":"7.0","script_version":"1.1.3","2":"1.1.3","version_comment":"- Fix portability with the updated Vim->Ruby data type conversion in devhead Vim.\r\n- Fix portability with Ruby 1.9.","3":"- Fix portability with the updated Vim->Ruby data type conversion in devhead Vim.\r\n- Fix portability with Ruby 1.9.","package":"lusty-juggler.vim","4":"lusty-juggler.vim","src_id":"12558","5":"12558","creation_date":"1267756057","6":"1267756057"},{"0":"2050","vim_version":"7.0","1":"7.0","script_version":"1.1.2","2":"1.1.2","version_comment":"Fix ENTER key to select the active buffer.  Thanks to Bartosz Leper.","3":"Fix ENTER key to select the active buffer.  Thanks to Bartosz Leper.","package":"lusty-juggler.vim","4":"lusty-juggler.vim","src_id":"11020","5":"11020","creation_date":"1247771762","6":"1247771762"},{"0":"2050","vim_version":"7.0","1":"7.0","script_version":"1.1.1","2":"1.1.1","version_comment":"Fix a startup bug in OS X and Windows.  Thanks to Bartosz Leper.","3":"Fix a startup bug in OS X and Windows.  Thanks to Bartosz Leper.","package":"lusty-juggler.vim","4":"lusty-juggler.vim","src_id":"11015","5":"11015","creation_date":"1247708240","6":"1247708240"},{"0":"2050","vim_version":"7.0","1":"7.0","script_version":"1.1.0","2":"1.1.0","version_comment":"- Substantially shorten displayed buffer names; usually only the basename is shown.  Thanks to Matt Tolton for the idea.\r\n- Add GetLatestVimScripts compatibility.","3":"- Substantially shorten displayed buffer names; usually only the basename is shown.  Thanks to Matt Tolton for the idea.\r\n- Add GetLatestVimScripts compatibility.","package":"lusty-juggler.vim","4":"lusty-juggler.vim","src_id":"10686","5":"10686","creation_date":"1243438140","6":"1243438140"},{"0":"2050","vim_version":"7.0","1":"7.0","script_version":"1.0.4","2":"1.0.4","version_comment":"The g:LustyJugglerShowKeys option should not be required to be set.","3":"The g:LustyJugglerShowKeys option should not be required to be set.","package":"lusty-juggler.vim","4":"lusty-juggler.vim","src_id":"9506","5":"9506","creation_date":"1226725309","6":"1226725309"},{"0":"2050","vim_version":"7.0","1":"7.0","script_version":"1.0.3","2":"1.0.3","version_comment":"Added g:LustyJugglerShowKeys for prefixing buffer names.  Thanks to Juan Frias for the original patch.","3":"Added g:LustyJugglerShowKeys for prefixing buffer names.  Thanks to Juan Frias for the original patch.","package":"lusty-juggler.vim","4":"lusty-juggler.vim","src_id":"9288","5":"9288","creation_date":"1222542148","6":"1222542148"},{"0":"2050","vim_version":"7.0","1":"7.0","script_version":"1.0.2","2":"1.0.2","version_comment":"- Colouring for path elements.\r\n- Added :JugglePrevious, a smarter version of the :b# command.\r\n- Refactoring.","3":"- Colouring for path elements.\r\n- Added :JugglePrevious, a smarter version of the :b# command.\r\n- Refactoring.","package":"lusty-juggler.vim","4":"lusty-juggler.vim","src_id":"9171","5":"9171","creation_date":"1219693309","6":"1219693309"},{"0":"2050","vim_version":"7.0","1":"7.0","script_version":"1.0.1","2":"1.0.1","version_comment":"- Fixed the layout algorithm so as not to veer right.\r\n- Disabled showmode when juggler is active.","3":"- Fixed the layout algorithm so as not to veer right.\r\n- Disabled showmode when juggler is active.","package":"lusty-juggler.vim","4":"lusty-juggler.vim","src_id":"7837","5":"7837","creation_date":"1193419971","6":"1193419971"},{"0":"2050","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"lusty-juggler.vim","4":"lusty-juggler.vim","src_id":"7820","5":"7820","creation_date":"1193164663","6":"1193164663"}]},"2049":{"script_id":"2049","0":"2049","script_name":"vim++","1":"vim++","script_type":"utility","2":"utility","summary":"Object-oriented programming for vim scripts in C++ style.","3":"Object-oriented programming for vim scripts in C++ style.","description":"Vim++ is a library to make object-oriented programming with Vim easy and natural. In Vim 7 were added some syntax constructions for object-oriented programming, but some tricky code should be written still, especially for inheritance and object constructors. So Vim++ defines a few commands to enable script writers avoid additional coding and make code more elegant. Vim++ use C++ like syntax for class definition. It defines commands Class, EndClass, Constr, Method, Abstract and Var. Usually class definitions looks as:\r\n\r\nClass MyClass : BaseClass1, BaseClass2, BaseClassN\r\n    Var member1 = 1\r\n    Constr New(arg1, arg2, arg3) : g:BaseClass1.New(a:arg1), g:BaseClass2.New(a:arg2), g:BaseClassN.New(a:arg1, a:arg2)\r\n        let self.member2 = a:arg3\r\n        return self\r\n    endfunction\r\n    Constr New1(arg1, arg2, argn) : {'member3': a:arg1}\r\n    endfunction\r\n    ........................\r\n    Method method1(arg1, arg2)\r\n        ....................\r\n    endf\r\n    Method method2(arg1, arg2)\r\n        ....................\r\n    endf\r\nEndClass\r\n\r\nSo definition begins with Class classname, then optionally comma-separated list of base classes follows after colon. Then a few constructors, methods and members are defined(in any order). And EndClass command finishes class definition. The object is available in methods and constructors as self. Methods are like usual functions, just use another keyword Method. Constructors are like functions too, though there are a few differences. After usual function-like definitions a list of initializers may present after colon. Initializers usually are objects of base class constructed, but really any expression allowed which can be evaluated to dictionary. Constructor obtain variable 'self' which is already an object of proper type with all methods and members including inherited from base classes. Constructor should return variable 'self', though it can return something another if construction was not successful due to some reasons. Both constructors and methods must be finished with endfunction.\r\n\r\nVim++ object is just a dictionary with a few members and few functions defined with 'dict' attribute. Vim++ class is just global variable contains all default to this class methods and members. So methods should be invoked as object.method1(arg1, arg2, argN) and constructors should be invoked as ClassName.New1(arg1, arg2, argN). If you invoke constructor in another function or in initializers list, you should use g: prefix.\r\n\r\ns: prefix is not supported in vim++. Don't use it in methods and constructors. Maybe in future versions it will be fixed.\r\n\r\nAll classes are subclass of Object class. Object has a few methods:\r\n\r\nMethod is(class)                        Is object of class a:class?\r\nMethod HasParent(class)                 Has object a parent of type a:class?\r\nMethod HasAncestor(class)               Has object an ancestor of type a:class?\r\n\r\nAny script using vim++ should be saved in file with extension .vim++ and placed somewhere in &runtimepath as usual Vim plugin. Though usual Vim plugin can use vim++ and libraries written on vim++ too, it should call function vimpp#Load() first.\r\n\r\nHead of vim++ script usually looks like this:\r\n\r\nPackage 1.2\r\nImport vim++ 0.1\r\nImport Library1\r\nImport Library2 1.3\r\nImport Library2 ver > 0.5\r\nImport LibraryN ver > 0.6.1 && ver < 0.7.4\r\n\r\nInstead Package you may use Library. The difference is that a package is loaded always and a library is loaded only if it have been imported.\r\n\r\nCommand Import imports some library. It may accept version of library as dot-separated list of numbers or some expression evaluated to integer. In the first case library loaded if and only if its version coincides with import argument. In the second case library is loaded only if expression evaluated to true(i.e. non-zero). Expression in Import argument may use 'ver' variable which contains actual version of library. Versions can be compared using usual comparison operators.\r\n\r\nVim++ scripts should import 'vim++' library first. This will prevent script to be loaded by improper version of vim++. Current vim++ version is 0.1.0. The last zero can be omited(but it is not allowed to omit zero in expression ver == 0.1.0).\r\n\r\nVim++ contains one built-in library, Reflection. It defines classes Type, FuncType and Method. Constructor g:Type.New(var)\r\nconstructs Type object for any variable var. Class Type has methods:\r\n\r\nMethod IsVimPPObject()                  True, if var is vim++ object, false otherwise.\r\nMethod GetMembers()                     Returns list which contains members names\r\nMethod GetMethods(...)                  Returns a dictionary having method names as keys and objects of type Method as values.\r\nMethod GetConstructors(...)             Returns a dictionary having constructor names as keys and objects of type Method as values.\r\n\r\nClass Method represents methods of some class. It is derived from FuncType class which is Type subclass to represent type of function reference.\r\n\r\nFuncType has methods: \r\n\r\nMethod GetArgList()                     Returns list of names of function arguments.\r\nMethod Definition()                     Returns definition of the function as list of lines.\r\n\r\nVim++ contains syntax and indentation file for .vim++ files.\r\n","4":"Vim++ is a library to make object-oriented programming with Vim easy and natural. In Vim 7 were added some syntax constructions for object-oriented programming, but some tricky code should be written still, especially for inheritance and object constructors. So Vim++ defines a few commands to enable script writers avoid additional coding and make code more elegant. Vim++ use C++ like syntax for class definition. It defines commands Class, EndClass, Constr, Method, Abstract and Var. Usually class definitions looks as:\r\n\r\nClass MyClass : BaseClass1, BaseClass2, BaseClassN\r\n    Var member1 = 1\r\n    Constr New(arg1, arg2, arg3) : g:BaseClass1.New(a:arg1), g:BaseClass2.New(a:arg2), g:BaseClassN.New(a:arg1, a:arg2)\r\n        let self.member2 = a:arg3\r\n        return self\r\n    endfunction\r\n    Constr New1(arg1, arg2, argn) : {'member3': a:arg1}\r\n    endfunction\r\n    ........................\r\n    Method method1(arg1, arg2)\r\n        ....................\r\n    endf\r\n    Method method2(arg1, arg2)\r\n        ....................\r\n    endf\r\nEndClass\r\n\r\nSo definition begins with Class classname, then optionally comma-separated list of base classes follows after colon. Then a few constructors, methods and members are defined(in any order). And EndClass command finishes class definition. The object is available in methods and constructors as self. Methods are like usual functions, just use another keyword Method. Constructors are like functions too, though there are a few differences. After usual function-like definitions a list of initializers may present after colon. Initializers usually are objects of base class constructed, but really any expression allowed which can be evaluated to dictionary. Constructor obtain variable 'self' which is already an object of proper type with all methods and members including inherited from base classes. Constructor should return variable 'self', though it can return something another if construction was not successful due to some reasons. Both constructors and methods must be finished with endfunction.\r\n\r\nVim++ object is just a dictionary with a few members and few functions defined with 'dict' attribute. Vim++ class is just global variable contains all default to this class methods and members. So methods should be invoked as object.method1(arg1, arg2, argN) and constructors should be invoked as ClassName.New1(arg1, arg2, argN). If you invoke constructor in another function or in initializers list, you should use g: prefix.\r\n\r\ns: prefix is not supported in vim++. Don't use it in methods and constructors. Maybe in future versions it will be fixed.\r\n\r\nAll classes are subclass of Object class. Object has a few methods:\r\n\r\nMethod is(class)                        Is object of class a:class?\r\nMethod HasParent(class)                 Has object a parent of type a:class?\r\nMethod HasAncestor(class)               Has object an ancestor of type a:class?\r\n\r\nAny script using vim++ should be saved in file with extension .vim++ and placed somewhere in &runtimepath as usual Vim plugin. Though usual Vim plugin can use vim++ and libraries written on vim++ too, it should call function vimpp#Load() first.\r\n\r\nHead of vim++ script usually looks like this:\r\n\r\nPackage 1.2\r\nImport vim++ 0.1\r\nImport Library1\r\nImport Library2 1.3\r\nImport Library2 ver > 0.5\r\nImport LibraryN ver > 0.6.1 && ver < 0.7.4\r\n\r\nInstead Package you may use Library. The difference is that a package is loaded always and a library is loaded only if it have been imported.\r\n\r\nCommand Import imports some library. It may accept version of library as dot-separated list of numbers or some expression evaluated to integer. In the first case library loaded if and only if its version coincides with import argument. In the second case library is loaded only if expression evaluated to true(i.e. non-zero). Expression in Import argument may use 'ver' variable which contains actual version of library. Versions can be compared using usual comparison operators.\r\n\r\nVim++ scripts should import 'vim++' library first. This will prevent script to be loaded by improper version of vim++. Current vim++ version is 0.1.0. The last zero can be omited(but it is not allowed to omit zero in expression ver == 0.1.0).\r\n\r\nVim++ contains one built-in library, Reflection. It defines classes Type, FuncType and Method. Constructor g:Type.New(var)\r\nconstructs Type object for any variable var. Class Type has methods:\r\n\r\nMethod IsVimPPObject()                  True, if var is vim++ object, false otherwise.\r\nMethod GetMembers()                     Returns list which contains members names\r\nMethod GetMethods(...)                  Returns a dictionary having method names as keys and objects of type Method as values.\r\nMethod GetConstructors(...)             Returns a dictionary having constructor names as keys and objects of type Method as values.\r\n\r\nClass Method represents methods of some class. It is derived from FuncType class which is Type subclass to represent type of function reference.\r\n\r\nFuncType has methods: \r\n\r\nMethod GetArgList()                     Returns list of names of function arguments.\r\nMethod Definition()                     Returns definition of the function as list of lines.\r\n\r\nVim++ contains syntax and indentation file for .vim++ files.\r\n","install_details":"Download tarball and unzip the files to the $HOME\/.vim or the  $HOME\/vimfiles or the $VIM\/vimfiles directory.","5":"Download tarball and unzip the files to the $HOME\/.vim or the  $HOME\/vimfiles or the $VIM\/vimfiles directory.","first_name":"Michael","6":"Michael","last_name":"Schwarz","7":"Schwarz","releases":[{"0":"2049","vim_version":"7.0","1":"7.0","script_version":"0.1.0","2":"0.1.0","version_comment":"Initial upload","3":"Initial upload","package":"vim++-0.1.0.tar.gz","4":"vim++-0.1.0.tar.gz","src_id":"7818","5":"7818","creation_date":"1193127216","6":"1193127216"}]},"2048":{"script_id":"2048","0":"2048","script_name":"BlockDiff","1":"BlockDiff","script_type":"utility","2":"utility","summary":"Difference between two blocks (functions etc...)","3":"Difference between two blocks (functions etc...)","description":"This script provides a simple and fast way to see the difference between two blocks of text.\r\nThis might be similar source code functions, definitions, etc.\r\n\r\nJust select the first portion, goto Menu \"Tools->BlockDiff->This is block 1\".\r\nSelect the second portion, goto Menu \"Tools->BlockDiff->This is block 2, start diff\".\r\nThe script will open a new tab, split it and diff the two portions.\r\n\r\nIf you prefer the mouse context-menu, a key mapping or ex commands, they all are prepared in the file, just remove the comment and\/or change the mappings.\r\n\r\nCurrently only for Vim 7.* with GUI (and tabs). ","4":"This script provides a simple and fast way to see the difference between two blocks of text.\r\nThis might be similar source code functions, definitions, etc.\r\n\r\nJust select the first portion, goto Menu \"Tools->BlockDiff->This is block 1\".\r\nSelect the second portion, goto Menu \"Tools->BlockDiff->This is block 2, start diff\".\r\nThe script will open a new tab, split it and diff the two portions.\r\n\r\nIf you prefer the mouse context-menu, a key mapping or ex commands, they all are prepared in the file, just remove the comment and\/or change the mappings.\r\n\r\nCurrently only for Vim 7.* with GUI (and tabs). ","install_details":"Just drop into your vim\/plugins directory","5":"Just drop into your vim\/plugins directory","first_name":"Timo","6":"Timo","last_name":"Teifel","7":"Teifel","releases":[{"0":"2048","vim_version":"7.0","1":"7.0","script_version":"1.1","2":"1.1","version_comment":"Added:\r\n - Commands :BlockDiff1 and :BlockDiff2\r\n - Inclusion guard\r\n - Moved Menu to Tools, right below \"Diff\"\r\nThanks to Ingo Karkat for these improvements!","3":"Added:\r\n - Commands :BlockDiff1 and :BlockDiff2\r\n - Inclusion guard\r\n - Moved Menu to Tools, right below \"Diff\"\r\nThanks to Ingo Karkat for these improvements!","package":"blockdiff.vim","4":"blockdiff.vim","src_id":"7817","5":"7817","creation_date":"1193111926","6":"1193111926"},{"0":"2048","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"blockdiff.vim","4":"blockdiff.vim","src_id":"7815","5":"7815","creation_date":"1193056008","6":"1193056008"}]},"2047":{"script_id":"2047","0":"2047","script_name":"nosql.vim","1":"nosql.vim","script_type":"syntax","2":"syntax","summary":"Provides syntax highlighting for NoSQL tables, or any tab-separated (TSV) tables","3":"Provides syntax highlighting for NoSQL tables, or any tab-separated (TSV) tables","description":"This is a simple syntax file to color columns in NoSQL tables. It's a rather\r\nheavily modified version of the VimOutliner syntax file. Currently it supports\r\nup to 16 columns. If you need more than that, you can always tweak the file.\r\n\r\nSince NoSQL tables are just TSV (tab-separated) tables, this syntax file will work on any \r\nTSV table you like. \r\n\r\nIf you don't favor NoSQL, you can access TSV tables in perl, e.g., using\r\nthe DBI module and DBI::AnyData. For example, to access a list of photos:\r\n\r\nour $fphotos = \"photos.tsv\";\r\n\r\nour $pdbh = DBI->connect('dbi:AnyData(RaiseError=>1):');\r\n\r\n$pdbh->func( 'photos', 'Tab', \"$fphotos\", 'ad_catalog' );\r\n\r\nNote that you'll need to remove the ^A characters in the header line to access a NoSQL table \r\nwith DBI like this. That's the only difference I've noted.\r\n\r\nFuture versions of nosql.vim might include helpful mappings for navigation, deleting\r\ncolumns, and so on, as well as syntax highlighting for NoSQL lists and templates.\r\n\r\nNoSQL, of course, is a delightful and free collection of scripts that can\r\nturn flat text files into databases. Instead of locking your data in binary\r\nand slogging through phpMyAdmin, you can open your tables in Vim, \r\nedit your data with your usual Vim flair, and then save your queries and\r\nreports as shell scripts. If you don't yet have NoSQL installed, check out the\r\nRESOURCES in the help file.\r\n\r\nNoSQL homepage: http:\/\/www.scriptaworks.com\/cgi-bin\/wiki.cgi\/NoSQL\/HomePage?from=NoSQL.NoSQL\r\n\r\nnosql.vim homepage: Coming soon. :)","4":"This is a simple syntax file to color columns in NoSQL tables. It's a rather\r\nheavily modified version of the VimOutliner syntax file. Currently it supports\r\nup to 16 columns. If you need more than that, you can always tweak the file.\r\n\r\nSince NoSQL tables are just TSV (tab-separated) tables, this syntax file will work on any \r\nTSV table you like. \r\n\r\nIf you don't favor NoSQL, you can access TSV tables in perl, e.g., using\r\nthe DBI module and DBI::AnyData. For example, to access a list of photos:\r\n\r\nour $fphotos = \"photos.tsv\";\r\n\r\nour $pdbh = DBI->connect('dbi:AnyData(RaiseError=>1):');\r\n\r\n$pdbh->func( 'photos', 'Tab', \"$fphotos\", 'ad_catalog' );\r\n\r\nNote that you'll need to remove the ^A characters in the header line to access a NoSQL table \r\nwith DBI like this. That's the only difference I've noted.\r\n\r\nFuture versions of nosql.vim might include helpful mappings for navigation, deleting\r\ncolumns, and so on, as well as syntax highlighting for NoSQL lists and templates.\r\n\r\nNoSQL, of course, is a delightful and free collection of scripts that can\r\nturn flat text files into databases. Instead of locking your data in binary\r\nand slogging through phpMyAdmin, you can open your tables in Vim, \r\nedit your data with your usual Vim flair, and then save your queries and\r\nreports as shell scripts. If you don't yet have NoSQL installed, check out the\r\nRESOURCES in the help file.\r\n\r\nNoSQL homepage: http:\/\/www.scriptaworks.com\/cgi-bin\/wiki.cgi\/NoSQL\/HomePage?from=NoSQL.NoSQL\r\n\r\nnosql.vim homepage: Coming soon. :)","install_details":"There's nothing fancy about nosql.vim; it's just a help file, a syntax\r\nfile, and a small ftdetect file that should fire up the syntax file when you\r\nopen a nosql table with an .nsq extension.\r\n\r\nSimply unzip the tarball and the copy the subdirectories into your $VIM\r\ndirectory. ","5":"There's nothing fancy about nosql.vim; it's just a help file, a syntax\r\nfile, and a small ftdetect file that should fire up the syntax file when you\r\nopen a nosql table with an .nsq extension.\r\n\r\nSimply unzip the tarball and the copy the subdirectories into your $VIM\r\ndirectory. ","first_name":"Bill","6":"Bill","last_name":"Powell","7":"Powell","releases":[{"0":"2047","vim_version":"6.0","1":"6.0","script_version":"0.2","2":"0.2","version_comment":"Added note on using nosql.vim for plain TSV tables, and also perl snippet for accessing TSV tables in perl with DBI and DBI::AnyData.","3":"Added note on using nosql.vim for plain TSV tables, and also perl snippet for accessing TSV tables in perl with DBI and DBI::AnyData.","package":"nosql-0.2.tar.gz","4":"nosql-0.2.tar.gz","src_id":"9242","5":"9242","creation_date":"1221132418","6":"1221132418"},{"0":"2047","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"nosql-0.1.tar.gz","4":"nosql-0.1.tar.gz","src_id":"7813","5":"7813","creation_date":"1192905084","6":"1192905084"}]},"2045":{"script_id":"2045","0":"2045","script_name":"mips.vim","1":"mips.vim","script_type":"syntax","2":"syntax","summary":"Your standard MIPS syntax highlighting","3":"Your standard MIPS syntax highlighting","description":"Frankly, I wasn't happy with the state of MIPS highlighting, so this script attempts to correct this.  It recognizes the entire set of MIPS instructions and directives, as well as all registers (be they aliased ($s0), directly numerical ($16), or an FP register ($f0)), correct MIPS comment style, and label declarations.\r\n\r\nIf you have any problems, I invite you to contact me and report them.  Enjoy!","4":"Frankly, I wasn't happy with the state of MIPS highlighting, so this script attempts to correct this.  It recognizes the entire set of MIPS instructions and directives, as well as all registers (be they aliased ($s0), directly numerical ($16), or an FP register ($f0)), correct MIPS comment style, and label declarations.\r\n\r\nIf you have any problems, I invite you to contact me and report them.  Enjoy!","install_details":"Just copy the script to your syntax directory.  On UNIX, this is ~\/.vim\/syntax\/.  Note that filetype is not autodetected, so to enable the highlighting, you must run the command \":set syntax=mips\".","5":"Just copy the script to your syntax directory.  On UNIX, this is ~\/.vim\/syntax\/.  Note that filetype is not autodetected, so to enable the highlighting, you must run the command \":set syntax=mips\".","first_name":"Alex","6":"Alex","last_name":"Brick","7":"Brick","releases":[{"0":"2045","vim_version":"6.0","1":"6.0","script_version":"1.0.1","2":"1.0.1","version_comment":"A minor fix to enable 6.x compatibility (noticed and patched by Jarmo Jaakkola), and a fix to hexadecimal numbers.","3":"A minor fix to enable 6.x compatibility (noticed and patched by Jarmo Jaakkola), and a fix to hexadecimal numbers.","package":"mips.vim","4":"mips.vim","src_id":"7826","5":"7826","creation_date":"1193223988","6":"1193223988"},{"0":"2045","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"mips.vim","4":"mips.vim","src_id":"7808","5":"7808","creation_date":"1192715885","6":"1192715885"}]},"2044":{"script_id":"2044","0":"2044","script_name":"myvim.vim","1":"myvim.vim","script_type":"utility","2":"utility","summary":"useful functions","3":"useful functions","description":"Following functions\r\nC-C for rectangle copy\r\nF5 F6 for copy likes of code\r\nS-f5 f6 to copy cut","4":"Following functions\r\nC-C for rectangle copy\r\nF5 F6 for copy likes of code\r\nS-f5 f6 to copy cut","install_details":"Drop it in plugin directory","5":"Drop it in plugin directory","first_name":"vijayandra","6":"vijayandra","last_name":"singh","7":"singh","releases":[{"0":"2044","vim_version":"6.0","1":"6.0","script_version":"1.1","2":"1.1","version_comment":"Added email field","3":"Added email field","package":"myvim.vim","4":"myvim.vim","src_id":"7807","5":"7807","creation_date":"1192649128","6":"1192649128"}]},"2043":{"script_id":"2043","0":"2043","script_name":"VimPdb","1":"VimPdb","script_type":"utility","2":"utility","summary":"Integrated Python debugging within Vim","3":"Integrated Python debugging within Vim","description":"    * Tired of debugging Python using print statements? \r\n    * Don't like the cumbersome PDB (Python debugger) console? \r\n    * Prefer using Vim for coding your Python programs? \r\n\r\nVimPdb is the solution - allows debugging Python in an IDE-fashion, right within the Vim editor.\r\n\r\nFeatures:\r\n    * Highlighting of currently debugged line and breakpoint lines.\r\n    * F5 - Run\/continue running.\r\n    * F2 - Toggle breakpoint at current line\r\n    * Ctrl-F2 \/ Shift-F2 - Toggle conditional\/temporary breakpoint.\r\n    * F7 \/ F8 - Step into\/over\r\n    * F12 - Print stack trace\r\n    * F3 \/ Ctrl-F3 - Eval\/Exec a given statement (in the current debugging context)\r\n    * Save\/load breakpoints into session files.\r\n    * Cross-platform\r\n    * And many more... See readme.txt for details \r\n\r\nCheck out http:\/\/code.google.com\/p\/vimpdb\/ for a screenshot.\r\n\r\nImportant Notes\r\n\r\n    * It's still considered Beta, so I'm not too sure about its stability or lack of bugs. However, I do appreciate if you could report bugs, suggest features or help out with the known issues (see \"Known Issues\" section in readme.txt). Email me at vimpdb@gmail.com\r\n    * It's possible to easily implement the debugging capabilities for another editor (e.g. Emacs) - you could write a Python class of your own, which inherits from the PdbIDE class, and implements editor-specific functionalities (such as highlighting). ","4":"    * Tired of debugging Python using print statements? \r\n    * Don't like the cumbersome PDB (Python debugger) console? \r\n    * Prefer using Vim for coding your Python programs? \r\n\r\nVimPdb is the solution - allows debugging Python in an IDE-fashion, right within the Vim editor.\r\n\r\nFeatures:\r\n    * Highlighting of currently debugged line and breakpoint lines.\r\n    * F5 - Run\/continue running.\r\n    * F2 - Toggle breakpoint at current line\r\n    * Ctrl-F2 \/ Shift-F2 - Toggle conditional\/temporary breakpoint.\r\n    * F7 \/ F8 - Step into\/over\r\n    * F12 - Print stack trace\r\n    * F3 \/ Ctrl-F3 - Eval\/Exec a given statement (in the current debugging context)\r\n    * Save\/load breakpoints into session files.\r\n    * Cross-platform\r\n    * And many more... See readme.txt for details \r\n\r\nCheck out http:\/\/code.google.com\/p\/vimpdb\/ for a screenshot.\r\n\r\nImportant Notes\r\n\r\n    * It's still considered Beta, so I'm not too sure about its stability or lack of bugs. However, I do appreciate if you could report bugs, suggest features or help out with the known issues (see \"Known Issues\" section in readme.txt). Email me at vimpdb@gmail.com\r\n    * It's possible to easily implement the debugging capabilities for another editor (e.g. Emacs) - you could write a Python class of your own, which inherits from the PdbIDE class, and implements editor-specific functionalities (such as highlighting). ","install_details":"Just drop vimpdb.py and vimpdb.vim into your Vim plugin directory, and you're all set to go.","5":"Just drop vimpdb.py and vimpdb.vim into your Vim plugin directory, and you're all set to go.","first_name":"Yaron","6":"Yaron","last_name":"Budowski","7":"Budowski","releases":[{"0":"2043","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"VimPdb.tar","4":"VimPdb.tar","src_id":"7805","5":"7805","creation_date":"1192546569","6":"1192546569"}]},"2042":{"script_id":"2042","0":"2042","script_name":"of.vim","1":"of.vim","script_type":"utility","2":"utility","summary":"Switch between open files \/ Find files by parital name (Similar to TM's Cmd-T)","3":"Switch between open files \/ Find files by parital name (Similar to TM's Cmd-T)","description":"This script works under CLI Vim (not gvim) and provides a curses interface for switching between \/ opening files simlar to TextMate's Cmd-T command.  It requires Vim to be compiled with Ruby bindings, and if you want it to keep a history, also for Ruby's sqlite3 bindings to be installed (it makes a db in your home directory, .of.db, where it stores info on recently opened files and preferred shortcuts for certain files).  To open a file called accounts_controller.php, you could simply call OF (I bind it to Alt-T) and type in ac -- a list of files under your working directory come up that have these two letters in any order.  Move up and down with arrows or ^P\/^N, scroll with your mouse, or click\/enter to select.  Escape gets you out.  This is a work in progress.  The code has no comments and needs to be cleaned up, but it does what I want it to for now, and maybe what you want.\r\n\r\nThis may be a little slow if run from a directory with a huge amount of files.  I usually start it from the base of whatever project I'm working on.","4":"This script works under CLI Vim (not gvim) and provides a curses interface for switching between \/ opening files simlar to TextMate's Cmd-T command.  It requires Vim to be compiled with Ruby bindings, and if you want it to keep a history, also for Ruby's sqlite3 bindings to be installed (it makes a db in your home directory, .of.db, where it stores info on recently opened files and preferred shortcuts for certain files).  To open a file called accounts_controller.php, you could simply call OF (I bind it to Alt-T) and type in ac -- a list of files under your working directory come up that have these two letters in any order.  Move up and down with arrows or ^P\/^N, scroll with your mouse, or click\/enter to select.  Escape gets you out.  This is a work in progress.  The code has no comments and needs to be cleaned up, but it does what I want it to for now, and maybe what you want.\r\n\r\nThis may be a little slow if run from a directory with a huge amount of files.  I usually start it from the base of whatever project I'm working on.","install_details":"Make sure you have Ruby bindings compiled into Vim.  They are included in Ubuntu's vim-full package, and can be compiled in with the --enable-rubyinterp option for .\/configure if you are compiling from source.  To check if they're working in Vim, type :ruby puts 'Hello'.  \r\n\r\nIf you want a working file history, and smart reuse of the shortcuts you use, you'll also need to install Ruby, Sqlite3 and Ruby Sqlite3 bindings on your system (highly recommended, but a pain on some systems):\r\n\r\nIn Ubuntu: \r\n\r\n sudo apt-get install vim-full ruby libsqlite3-ruby sqlite3  (easy as pie)\r\n\r\nVia Yum: \r\n\r\n sudo yum install ruby-devel\r\n sudo yum install sqlite3-devel\r\n sudo gem install sqlite3-ruby  (there is probably a yum package for ruby-sqlite3, but there wasn't on the machine I tested on)\r\n\r\nOS X via MacPorts: (with \/opt\/local\/bin in your path before \/usr\/bin):\r\n\r\n sudo port install ruby\r\n sudo port install vim +ruby\r\n sudo port install sqlite3\r\n sudo port install rb-rubygems\r\n sudo gem update\r\n sudo gem install sqlite3-ruby\r\n\r\nPut of.vim in your ~\/.vim\/plugins folder, and bind call OF() to something.  I use Alt-T (in my .vimrc):\r\nnnoremap ^[t :call OF()<CR>\r\n(type ^[t like ctrl-v, alt-t)\r\n\r\nIf you need to do anything special to install it on another type of system, shoot me an email and I will post the details here.","5":"Make sure you have Ruby bindings compiled into Vim.  They are included in Ubuntu's vim-full package, and can be compiled in with the --enable-rubyinterp option for .\/configure if you are compiling from source.  To check if they're working in Vim, type :ruby puts 'Hello'.  \r\n\r\nIf you want a working file history, and smart reuse of the shortcuts you use, you'll also need to install Ruby, Sqlite3 and Ruby Sqlite3 bindings on your system (highly recommended, but a pain on some systems):\r\n\r\nIn Ubuntu: \r\n\r\n sudo apt-get install vim-full ruby libsqlite3-ruby sqlite3  (easy as pie)\r\n\r\nVia Yum: \r\n\r\n sudo yum install ruby-devel\r\n sudo yum install sqlite3-devel\r\n sudo gem install sqlite3-ruby  (there is probably a yum package for ruby-sqlite3, but there wasn't on the machine I tested on)\r\n\r\nOS X via MacPorts: (with \/opt\/local\/bin in your path before \/usr\/bin):\r\n\r\n sudo port install ruby\r\n sudo port install vim +ruby\r\n sudo port install sqlite3\r\n sudo port install rb-rubygems\r\n sudo gem update\r\n sudo gem install sqlite3-ruby\r\n\r\nPut of.vim in your ~\/.vim\/plugins folder, and bind call OF() to something.  I use Alt-T (in my .vimrc):\r\nnnoremap ^[t :call OF()<CR>\r\n(type ^[t like ctrl-v, alt-t)\r\n\r\nIf you need to do anything special to install it on another type of system, shoot me an email and I will post the details here.","first_name":"Ethan","6":"Ethan","last_name":"McCreadie","7":"McCreadie","releases":[{"0":"2042","vim_version":"7.0","1":"7.0","script_version":"0.16","2":"0.16","version_comment":"adjusted scrolling and file-list caching","3":"adjusted scrolling and file-list caching","package":"of.vim","4":"of.vim","src_id":"7798","5":"7798","creation_date":"1192456273","6":"1192456273"},{"0":"2042","vim_version":"7.0","1":"7.0","script_version":"0.15","2":"0.15","version_comment":"fixed scrolling issue and some funky db saves","3":"fixed scrolling issue and some funky db saves","package":"of.vim","4":"of.vim","src_id":"7796","5":"7796","creation_date":"1192429717","6":"1192429717"},{"0":"2042","vim_version":"7.0","1":"7.0","script_version":"0.14","2":"0.14","version_comment":"fixes","3":"fixes","package":"of.vim","4":"of.vim","src_id":"7785","5":"7785","creation_date":"1192202923","6":"1192202923"},{"0":"2042","vim_version":"7.0","1":"7.0","script_version":"0.13","2":"0.13","version_comment":"Allows script to function without sqlite support.  Much more fun if you have it though.","3":"Allows script to function without sqlite support.  Much more fun if you have it though.","package":"of.vim","4":"of.vim","src_id":"7784","5":"7784","creation_date":"1192197467","6":"1192197467"},{"0":"2042","vim_version":"6.0","1":"6.0","script_version":"0.12","2":"0.12","version_comment":"Accomodates for versions of sqlite that don't support CREATE TABLE IF NOT EXISTS syntax","3":"Accomodates for versions of sqlite that don't support CREATE TABLE IF NOT EXISTS syntax","package":"of.vim","4":"of.vim","src_id":"7783","5":"7783","creation_date":"1192194363","6":"1192194363"},{"0":"2042","vim_version":"6.0","1":"6.0","script_version":"0.11","2":"0.11","version_comment":"Allows for sqlite3 to come from ruby-gems, fixed minor bugs.","3":"Allows for sqlite3 to come from ruby-gems, fixed minor bugs.","package":"of.vim","4":"of.vim","src_id":"7782","5":"7782","creation_date":"1192192986","6":"1192192986"},{"0":"2042","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"of.vim","4":"of.vim","src_id":"7781","5":"7781","creation_date":"1192178427","6":"1192178427"}]},"2041":{"script_id":"2041","0":"2041","script_name":"AutoScrollMode","1":"AutoScrollMode","script_type":"utility","2":"utility","summary":"script to let vim auto scroll text for you","3":"script to let vim auto scroll text for you","description":"Sometimes you just read text inside vim. You spend hours in Normal mode, not doing nothing, just scrolling text and pressing hjkl keys all the time. In such situations this script becomes very useful.\r\nTo enter Auto Scroll Mode, install this script first,\r\nand than activate it pressing <F21> key from Normal mode (Pause on keyboard)\r\nTo start scrolling text type 'l', for more info read next section.\r\n\r\nCOMMANDS\r\n\r\n Commands used in Auto Scroll Mode to change how Vim will scroll text\r\n\r\n        0-9        : change type of movement to:\r\n\r\n        \"1\"        : character, default\r\n        \"2\"        : word\r\n        \"3\"        : WORD\r\n        \"4\"        : line\r\n        \"5\"        : half page\r\n        \"6\"        : full page\r\n        \"7\"        : full screen\r\n        \"8\"        : sentence\r\n        \"9\"        : paragraph        see 'paragraphs'\r\n        \"0\"        : section        see 'sections'\r\n\r\n\r\n\r\n Commands used to change how much time will Vim\r\n sleep until the cursor is moved, default: Vim will sleep forever\r\n Note: period can be negative, in that case period is changed to\r\n positive but direction is switched i.e. up becomes down.\r\n\r\n\r\n        \"h\"        : decrease sleep period for 1 millisecond\r\n\r\n        \"l\"        : increase sleep period for 1 millisecond\r\n\r\n\r\n        \"k\"        : divides sleep period for 2\r\n\r\n        \"j\"        : multiplies sleep period for 2\r\n\r\n\r\n        \"`\"        : set sleep period to zero, default\r\n\r\n other useful commands:\r\n\r\n        \"r\"        : clean and redraw screen\r\n\r\n        <Space>    : toggle pause, text stop scrolling\r\n        <Enter>    : toggle backward\/forward movement\r\n\r\n        <Esc>      : exit AutoScrollMode, enters Normal Vim mode\r\n        CTRL-C     : immediately exit in Normal Vim mode\r\n","4":"Sometimes you just read text inside vim. You spend hours in Normal mode, not doing nothing, just scrolling text and pressing hjkl keys all the time. In such situations this script becomes very useful.\r\nTo enter Auto Scroll Mode, install this script first,\r\nand than activate it pressing <F21> key from Normal mode (Pause on keyboard)\r\nTo start scrolling text type 'l', for more info read next section.\r\n\r\nCOMMANDS\r\n\r\n Commands used in Auto Scroll Mode to change how Vim will scroll text\r\n\r\n        0-9        : change type of movement to:\r\n\r\n        \"1\"        : character, default\r\n        \"2\"        : word\r\n        \"3\"        : WORD\r\n        \"4\"        : line\r\n        \"5\"        : half page\r\n        \"6\"        : full page\r\n        \"7\"        : full screen\r\n        \"8\"        : sentence\r\n        \"9\"        : paragraph        see 'paragraphs'\r\n        \"0\"        : section        see 'sections'\r\n\r\n\r\n\r\n Commands used to change how much time will Vim\r\n sleep until the cursor is moved, default: Vim will sleep forever\r\n Note: period can be negative, in that case period is changed to\r\n positive but direction is switched i.e. up becomes down.\r\n\r\n\r\n        \"h\"        : decrease sleep period for 1 millisecond\r\n\r\n        \"l\"        : increase sleep period for 1 millisecond\r\n\r\n\r\n        \"k\"        : divides sleep period for 2\r\n\r\n        \"j\"        : multiplies sleep period for 2\r\n\r\n\r\n        \"`\"        : set sleep period to zero, default\r\n\r\n other useful commands:\r\n\r\n        \"r\"        : clean and redraw screen\r\n\r\n        <Space>    : toggle pause, text stop scrolling\r\n        <Enter>    : toggle backward\/forward movement\r\n\r\n        <Esc>      : exit AutoScrollMode, enters Normal Vim mode\r\n        CTRL-C     : immediately exit in Normal Vim mode\r\n","install_details":"Just source file once you opened it inside vim, or put it in Vim plugins directory.","5":"Just source file once you opened it inside vim, or put it in Vim plugins directory.","first_name":"Paul B.","6":"Paul B.","last_name":"Mahol","7":"Mahol","releases":[{"0":"2041","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"AutoScrollMode.vim","4":"AutoScrollMode.vim","src_id":"7772","5":"7772","creation_date":"1192000211","6":"1192000211"}]},"2040":{"script_id":"2040","0":"2040","script_name":"tcalc","1":"tcalc","script_type":"utility","2":"utility","summary":"A small ruby-based RPN-calculator","3":"A small ruby-based RPN-calculator","description":"It turns out that ruby is pretty good at maths and deals well with \r\ncomplex or rational numbers etc. Anyway, in certain occasions a postfix \r\nsyntax and a stack are better suited for calculations than ruby's infix \r\nsyntax. So, here comes ...\r\n\r\n:TCalc[!]\r\n    A small ruby-based[*] RPN-calculator, a simple ASCII function \r\n    plotter, and stack-based playground :-).\r\n\r\nThe tcalc.rb script can also be used as a stand-alone calculator (with \r\noptional support for curses and readline). Run \"tcalc --help\" for \r\ninformation on the command-line options.\r\n\r\nInput:\r\n    - Numbers (anything that starts with \"-\" or a decimal)\r\n    - Strings (anything that matches \/^\"(.*?)\"$\/)\r\n        - Be aware that the strings and numbers get evaluated by ruby. \r\n          You can thus execute ruby code by input like: -1;p'foo'\r\n    - Methods & constants of the following classes are available:\r\n        Float    :: http:\/\/www.ruby-doc.org\/core\/classes\/Float.html\r\n        Complex  :: http:\/\/www.ruby-doc.org\/core\/classes\/Complex.html\r\n        Rational :: http:\/\/www.ruby-doc.org\/core\/classes\/Rational.html\r\n        Integer  :: http:\/\/www.ruby-doc.org\/core\/classes\/Integer.html\r\n        Matrix   :: http:\/\/www.ruby-doc.org\/core\/classes\/Matrix.html\r\n        Vector   :: http:\/\/www.ruby-doc.org\/core\/classes\/Vector.html\r\n        Math     :: http:\/\/www.ruby-doc.org\/core\/classes\/Math.html\r\n    - #N (pull the item at position N to the top)\r\n    - Commands: COMMAND[COUNT][,ARGUMENT]\r\n        - If COUNT is \"#\", the top element will be used.\r\n    - Enter, escape => exit\r\n\r\nTokens are separated by blanks (\u00c3\u00a0 la forth). The blanks between the \r\nwords thus are significant.\r\n","4":"It turns out that ruby is pretty good at maths and deals well with \r\ncomplex or rational numbers etc. Anyway, in certain occasions a postfix \r\nsyntax and a stack are better suited for calculations than ruby's infix \r\nsyntax. So, here comes ...\r\n\r\n:TCalc[!]\r\n    A small ruby-based[*] RPN-calculator, a simple ASCII function \r\n    plotter, and stack-based playground :-).\r\n\r\nThe tcalc.rb script can also be used as a stand-alone calculator (with \r\noptional support for curses and readline). Run \"tcalc --help\" for \r\ninformation on the command-line options.\r\n\r\nInput:\r\n    - Numbers (anything that starts with \"-\" or a decimal)\r\n    - Strings (anything that matches \/^\"(.*?)\"$\/)\r\n        - Be aware that the strings and numbers get evaluated by ruby. \r\n          You can thus execute ruby code by input like: -1;p'foo'\r\n    - Methods & constants of the following classes are available:\r\n        Float    :: http:\/\/www.ruby-doc.org\/core\/classes\/Float.html\r\n        Complex  :: http:\/\/www.ruby-doc.org\/core\/classes\/Complex.html\r\n        Rational :: http:\/\/www.ruby-doc.org\/core\/classes\/Rational.html\r\n        Integer  :: http:\/\/www.ruby-doc.org\/core\/classes\/Integer.html\r\n        Matrix   :: http:\/\/www.ruby-doc.org\/core\/classes\/Matrix.html\r\n        Vector   :: http:\/\/www.ruby-doc.org\/core\/classes\/Vector.html\r\n        Math     :: http:\/\/www.ruby-doc.org\/core\/classes\/Math.html\r\n    - #N (pull the item at position N to the top)\r\n    - Commands: COMMAND[COUNT][,ARGUMENT]\r\n        - If COUNT is \"#\", the top element will be used.\r\n    - Enter, escape => exit\r\n\r\nTokens are separated by blanks (\u00c3\u00a0 la forth). The blanks between the \r\nwords thus are significant.\r\n","install_details":"As VIM-plugin:\r\nExtract the archive's contents to ~\/vimfiles (or ~\/.vim).\r\n\r\nStand-alone ruby script:\r\nCopy the file ruby\/tcalc.rb to your path (you could also rename it to \r\ntcalc).\r\n\r\n\r\nAlso available via git\r\nhttp:\/\/github.com\/tomtom\/tcalc_vim","5":"As VIM-plugin:\r\nExtract the archive's contents to ~\/vimfiles (or ~\/.vim).\r\n\r\nStand-alone ruby script:\r\nCopy the file ruby\/tcalc.rb to your path (you could also rename it to \r\ntcalc).\r\n\r\n\r\nAlso available via git\r\nhttp:\/\/github.com\/tomtom\/tcalc_vim","first_name":"Tom","6":"Tom","last_name":"Link","7":"Link","releases":[{"0":"2040","vim_version":"7.0","1":"7.0","script_version":"0.13","2":"0.13","version_comment":"- help command (not really useful yet)\n- help (not really useful yet)\n- ruby 1.8 compatibility\n- FIX: help command\n- Interpret .[0-9]+ as float (suggested by John Orr)\n- .gitignore\nMD5 checksum: b2f2bf21e1fe9cb0bdc612a7cb973621","3":"- help command (not really useful yet)\n- help (not really useful yet)\n- ruby 1.8 compatibility\n- FIX: help command\n- Interpret .[0-9]+ as float (suggested by John Orr)\n- .gitignore\nMD5 checksum: b2f2bf21e1fe9cb0bdc612a7cb973621","package":"tcalc.vba","4":"tcalc.vba","src_id":"15730","5":"15730","creation_date":"1306393713","6":"1306393713"},{"0":"2040","vim_version":"7.0","1":"7.0","script_version":"0.11","2":"0.11","version_comment":"- New words: all?, any?, array_*, and, or, !=\r\n- Curses frontend: Show possible completions; map 127 to backspace, F1 \r\nto 'ls'; improved handling of cursor keys etc.\r\n- Debugger (sort of)\r\n- FIX: Nested blocks & more\r\n","3":"- New words: all?, any?, array_*, and, or, !=\r\n- Curses frontend: Show possible completions; map 127 to backspace, F1 \r\nto 'ls'; improved handling of cursor keys etc.\r\n- Debugger (sort of)\r\n- FIX: Nested blocks & more\r\n","package":"tcalc.zip","4":"tcalc.zip","src_id":"8028","5":"8028","creation_date":"1196853873","6":"1196853873"},{"0":"2040","vim_version":"7.0","1":"7.0","script_version":"0.10","2":"0.10","version_comment":"- rm,* ... Remove all words\r\n- If g:tcalc_lines < 0, use fixed window height.\r\n- VIM: use the tcalc window to display plots, lists etc.\r\n- FIX: Nested words and some more\r\n","3":"- rm,* ... Remove all words\r\n- If g:tcalc_lines < 0, use fixed window height.\r\n- VIM: use the tcalc window to display plots, lists etc.\r\n- FIX: Nested words and some more\r\n","package":"tcalc.zip","4":"tcalc.zip","src_id":"8009","5":"8009","creation_date":"1196418449","6":"1196418449"},{"0":"2040","vim_version":"7.0","1":"7.0","script_version":"0.9","2":"0.9","version_comment":"- FIX: Curses frontend: Display error messages properly\r\n- FIX: readline support.\r\n- FIX: sort words on completion\r\n- Distribute as zip\r\n","3":"- FIX: Curses frontend: Display error messages properly\r\n- FIX: readline support.\r\n- FIX: sort words on completion\r\n- Distribute as zip\r\n","package":"tcalc.zip","4":"tcalc.zip","src_id":"8000","5":"8000","creation_date":"1196247527","6":"1196247527"},{"0":"2040","vim_version":"7.0","1":"7.0","script_version":"0.8","2":"0.8","version_comment":"- Named arguments: args is a synonym for assert but provides for named \r\narguments.\r\n- New words: Sequence\/seq, map, mmap, plot (a simple ASCII function \r\nplotter), stack_size, stack_empty?, iqueue_size, iqueue_empty?\r\n- Syntactic sugar for assignments: VALUE -> VAR\r\n- Defined \"Array\" as a synonym for \"group\"\r\n- \"define\" command as alternative to the forth-like syntax for defining \r\nwords\r\n- Dynamic binding of words\/variables (the words \"begin ... end\" \r\nestablish a new scope)\r\n- The stack, the input queue, and the dictionary are accessible like \r\nwords (__STACK__, __IQUEUE__, __WORDS__)\r\n- TCalc and tcalc#Calculator take initial tokens as argument.\r\n- TCalc! with [!] will reset the stack & input queue.\r\n- Completion of partial commands\r\n- Readline-support for CLI mode (--no-curses).\r\n- Simple key handling for the curses-based frontend\r\n- Non-VIM-versons save the history in ~\/.tcalc\/history.txt\r\n- #VAR,METHOD has slightly changed.\r\n- TCalc syntax file.\r\n- FIX: Command line completion\r\n","3":"- Named arguments: args is a synonym for assert but provides for named \r\narguments.\r\n- New words: Sequence\/seq, map, mmap, plot (a simple ASCII function \r\nplotter), stack_size, stack_empty?, iqueue_size, iqueue_empty?\r\n- Syntactic sugar for assignments: VALUE -> VAR\r\n- Defined \"Array\" as a synonym for \"group\"\r\n- \"define\" command as alternative to the forth-like syntax for defining \r\nwords\r\n- Dynamic binding of words\/variables (the words \"begin ... end\" \r\nestablish a new scope)\r\n- The stack, the input queue, and the dictionary are accessible like \r\nwords (__STACK__, __IQUEUE__, __WORDS__)\r\n- TCalc and tcalc#Calculator take initial tokens as argument.\r\n- TCalc! with [!] will reset the stack & input queue.\r\n- Completion of partial commands\r\n- Readline-support for CLI mode (--no-curses).\r\n- Simple key handling for the curses-based frontend\r\n- Non-VIM-versons save the history in ~\/.tcalc\/history.txt\r\n- #VAR,METHOD has slightly changed.\r\n- TCalc syntax file.\r\n- FIX: Command line completion\r\n","package":"tcalc.vba.gz","4":"tcalc.vba.gz","src_id":"7995","5":"7995","creation_date":"1196162894","6":"1196162894"},{"0":"2040","vim_version":"7.0","1":"7.0","script_version":"0.7","2":"0.7","version_comment":"- Comments: \/* ... *\/\r\n- New words:\r\n    - assert: Display an error message if the stack doesn't match the \r\n    assertion.\r\n    - validate: Like assert but push a boolean (the result of the check) \r\n    on the stack.\r\n    - do: synonym for recapture.\r\n    - source: load a file (see also g:tcalc_dir)\r\n    - require: load a ruby library\r\n    - p: print an object (doesn't do much, but prettyprint seems \r\n    to have problems)\r\n    - history (useful when using tcalc as stand-alone calculator)\r\n- tcalc.rb can now be used as stand-alone program (a simple \r\ncurses-based frontend).\r\n","3":"- Comments: \/* ... *\/\r\n- New words:\r\n    - assert: Display an error message if the stack doesn't match the \r\n    assertion.\r\n    - validate: Like assert but push a boolean (the result of the check) \r\n    on the stack.\r\n    - do: synonym for recapture.\r\n    - source: load a file (see also g:tcalc_dir)\r\n    - require: load a ruby library\r\n    - p: print an object (doesn't do much, but prettyprint seems \r\n    to have problems)\r\n    - history (useful when using tcalc as stand-alone calculator)\r\n- tcalc.rb can now be used as stand-alone program (a simple \r\ncurses-based frontend).\r\n","package":"tcalc.vba.gz","4":"tcalc.vba.gz","src_id":"7844","5":"7844","creation_date":"1193700450","6":"1193700450"},{"0":"2040","vim_version":"7.0","1":"7.0","script_version":"0.6","2":"0.6","version_comment":"- Included support for rational and complex numbers\r\n- Included matrix support \r\n- Syntax for pushing arrays [ a b c ... ]\r\n- New \"at\" method to select an item from array-like objects\r\n- Removed shortcut variables.\r\n","3":"- Included support for rational and complex numbers\r\n- Included matrix support \r\n- Syntax for pushing arrays [ a b c ... ]\r\n- New \"at\" method to select an item from array-like objects\r\n- Removed shortcut variables.\r\n","package":"tcalc.vba.gz","4":"tcalc.vba.gz","src_id":"7832","5":"7832","creation_date":"1193357859","6":"1193357859"},{"0":"2040","vim_version":"7.0","1":"7.0","script_version":"0.5","2":"0.5","version_comment":"- Minor fix: command regexp\r\n","3":"- Minor fix: command regexp\r\n","package":"tcalc.vba.gz","4":"tcalc.vba.gz","src_id":"7789","5":"7789","creation_date":"1192229035","6":"1192229035"},{"0":"2040","vim_version":"7.0","1":"7.0","script_version":"0.4","2":"0.4","version_comment":"- COUNT can be \"#\", in which case the top number on the stack will be \r\nused (e.g. \"3 dup3\" is the same as \"3 3 dup#\")\r\n- Disabled vars, (, ) commands\r\n- Variables are words\r\n- New words can be defined in a forth-like manner \":NAME ... ;\"\r\n- Built-in commands get evaluated before any methods.\r\n- Messages can be sent to objects on the stack by \"#N,METHOD\", e.g. \"1 2 \r\ng2 3 #1,<<\" yields \"[1,2,3]\"\r\n- The copyN, cN command now means: push a copy of element N.\r\n- ( ... ) push unprocessed tokens as array\r\n- recapture command (feed an array of unprocessed tokens to the input \r\nqueue)\r\n- if, ifelse commands\r\n- delN, deleteN commands\r\n- Can push strings (\"foo bar\")\r\n- \"Symbols\" \u00c3\u00a0 la 'foo (actually a string)\r\n","3":"- COUNT can be \"#\", in which case the top number on the stack will be \r\nused (e.g. \"3 dup3\" is the same as \"3 3 dup#\")\r\n- Disabled vars, (, ) commands\r\n- Variables are words\r\n- New words can be defined in a forth-like manner \":NAME ... ;\"\r\n- Built-in commands get evaluated before any methods.\r\n- Messages can be sent to objects on the stack by \"#N,METHOD\", e.g. \"1 2 \r\ng2 3 #1,<<\" yields \"[1,2,3]\"\r\n- The copyN, cN command now means: push a copy of element N.\r\n- ( ... ) push unprocessed tokens as array\r\n- recapture command (feed an array of unprocessed tokens to the input \r\nqueue)\r\n- if, ifelse commands\r\n- delN, deleteN commands\r\n- Can push strings (\"foo bar\")\r\n- \"Symbols\" \u00c3\u00a0 la 'foo (actually a string)\r\n","package":"tcalc.vba.gz","4":"tcalc.vba.gz","src_id":"7765","5":"7765","creation_date":"1191838567","6":"1191838567"},{"0":"2040","vim_version":"7.0","1":"7.0","script_version":"0.3","2":"0.3","version_comment":"- The swap count argument is increased by one (for conformance with the \r\nrot command).\r\n- Shortcuts are now RPN expression (elements at the stack can be \r\nreferred to by # (= top element) or #N).\r\n- Removed g:tcalc_reverse_display\r\n- Positions on the stack can be referred to by #N.\r\n- rot works the other way round\r\n- d, dup command\r\n- clear command\r\n- print, hex, HEX, oct, dec, bin, float, format commands\r\n- Removed dependency on tlib\r\n- Variables; ls, vars, let, =, rm commands\r\n- Command line completion for variables and commands\r\n","3":"- The swap count argument is increased by one (for conformance with the \r\nrot command).\r\n- Shortcuts are now RPN expression (elements at the stack can be \r\nreferred to by # (= top element) or #N).\r\n- Removed g:tcalc_reverse_display\r\n- Positions on the stack can be referred to by #N.\r\n- rot works the other way round\r\n- d, dup command\r\n- clear command\r\n- print, hex, HEX, oct, dec, bin, float, format commands\r\n- Removed dependency on tlib\r\n- Variables; ls, vars, let, =, rm commands\r\n- Command line completion for variables and commands\r\n","package":"tcalc.vba.gz","4":"tcalc.vba.gz","src_id":"7764","5":"7764","creation_date":"1191792622","6":"1191792622"},{"0":"2040","vim_version":"7.0","1":"7.0","script_version":"0.2","2":"0.2","version_comment":"- Arguments were (not properly) reverted: 12 4 \/ now yields 3.\r\n- The input will be split into tokens, i.e. you can input \"1 2 + <cr>\" \r\nor \"1<cr>2<cr>+<cr>\". (Command-line completions doesn't work properly \r\nthough.)\r\n- The syntax has slightly changed: \"CmdCount,Arg\", eg, \"y3,a\"\r\n","3":"- Arguments were (not properly) reverted: 12 4 \/ now yields 3.\r\n- The input will be split into tokens, i.e. you can input \"1 2 + <cr>\" \r\nor \"1<cr>2<cr>+<cr>\". (Command-line completions doesn't work properly \r\nthough.)\r\n- The syntax has slightly changed: \"CmdCount,Arg\", eg, \"y3,a\"\r\n","package":"tcalc.vba.gz","4":"tcalc.vba.gz","src_id":"7763","5":"7763","creation_date":"1191744785","6":"1191744785"},{"0":"2040","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"tcalc.vba.gz","4":"tcalc.vba.gz","src_id":"7761","5":"7761","creation_date":"1191739964","6":"1191739964"}]},"2039":{"script_id":"2039","0":"2039","script_name":"QuickComment","1":"QuickComment","script_type":"utility","2":"utility","summary":"comment\/uncomment utility","3":"comment\/uncomment utility","description":"It bases on Chris Russell\\'s BlockComment and i just added some enhancement to it.\r\nSimply type : <range> C to comment and <range> NC to uncomment. The original functions are also supported.","4":"It bases on Chris Russell\\'s BlockComment and i just added some enhancement to it.\r\nSimply type : <range> C to comment and <range> NC to uncomment. The original functions are also supported.","install_details":"drop QuickComment.vim to $VIM_RUNTIME\/plugin\/","5":"drop QuickComment.vim to $VIM_RUNTIME\/plugin\/","first_name":"Simon","6":"Simon","last_name":"Xu","7":"Xu","releases":[{"0":"2039","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"bug fixed","3":"bug fixed","package":"QuickComment.vim","4":"QuickComment.vim","src_id":"7769","5":"7769","creation_date":"1191884961","6":"1191884961"}]},"2038":{"script_id":"2038","0":"2038","script_name":"narrow_region","1":"narrow_region","script_type":"utility","2":"utility","summary":"hide certain lines of a buffer","3":"hide certain lines of a buffer","description":"This plugin provides a command which somewhat limits the buffer to a specified range of lines.\r\n\r\n...\r\n:[range]NarrowRegion\r\n\t\tThis command does the following, with [range] defaulting to\r\n\t\tthe current line :\r\n\t\t- store current folds, foldstates and foldoptions\r\n\t\t- delete all folds\r\n\t\t- setl foldopen=undo\r\n\t\t- setl foldclose=all\r\n\t\t- setl foldminlines=0\r\n\t\t- setl foldmethod=manual\r\n\t\t- fold all lines outside of range\r\n\t\t- setup the nice extras, see below\r\n...","4":"This plugin provides a command which somewhat limits the buffer to a specified range of lines.\r\n\r\n...\r\n:[range]NarrowRegion\r\n\t\tThis command does the following, with [range] defaulting to\r\n\t\tthe current line :\r\n\t\t- store current folds, foldstates and foldoptions\r\n\t\t- delete all folds\r\n\t\t- setl foldopen=undo\r\n\t\t- setl foldclose=all\r\n\t\t- setl foldminlines=0\r\n\t\t- setl foldmethod=manual\r\n\t\t- fold all lines outside of range\r\n\t\t- setup the nice extras, see below\r\n...","install_details":"As usual :\r\n\r\nvim narrow_region.vba\r\n:so %\r\n\r\n","5":"As usual :\r\n\r\nvim narrow_region.vba\r\n:so %\r\n\r\n","first_name":"Andreas","6":"Andreas","last_name":"Politz","7":"Politz","releases":[{"0":"2038","vim_version":"7.0","1":"7.0","script_version":"v1.0","2":"v1.0","version_comment":"Initial upload","3":"Initial upload","package":"narrow_region.vba","4":"narrow_region.vba","src_id":"7757","5":"7757","creation_date":"1191626434","6":"1191626434"}]},"2037":{"script_id":"2037","0":"2037","script_name":"hookcursormoved","1":"hookcursormoved","script_type":"utility","2":"utility","summary":"Facilitate definition of triggers on CursorMoved[I] events","3":"Facilitate definition of triggers on CursorMoved[I] events","description":"This experimental plugin provides some help with the definition of \r\nfunctions that should be called when the cursor position changed.\r\n\r\nWhen the cursor position changes, it first checks if a certain condition \r\nis met and then calls functions registered in \r\n[bg]:hookcursormoved_{CONDITION} (an array).\r\n\r\nPre-defined conditions:\r\n    linechange\r\n        The line-number has changed.\r\n    parenthesis\r\n        Cursor is over (), [], or {}.\r\n    syntaxchange\r\n        The syntax group under the cursor has changed (i.e. the cursor \r\n        has moved in\/out of a syntax group.\r\n    syntaxleave\r\n        b:hookcursormoved_syntax (ARRAY) should contain the syntax names \r\n        which should run the hook code.\r\n    syntaxleave_oneline\r\n        Same as a above but check also for changes of the line number.\r\n\r\nIn order to define a new conditions, you have to define a function \r\n\"HookCursorMoved_{CONDITION}(mode)\", which returns true if the condition \r\nis met.\r\n\r\nFunctions are best registered using |hookcursormoved#Register()|.\r\nExample: >\r\n\r\n    function! WhatsGoingOn(mode) \"{{{3\r\n        if mode == 'i'\r\n            DoThis\r\n        elseif mode == 'n'\r\n            DoThat\r\n        endif\r\n    endf\r\n\r\n    call hookcursormoved#Register('b', 'syntaxchange', function('WhatsGoingOn'))\r\n\r\n","4":"This experimental plugin provides some help with the definition of \r\nfunctions that should be called when the cursor position changed.\r\n\r\nWhen the cursor position changes, it first checks if a certain condition \r\nis met and then calls functions registered in \r\n[bg]:hookcursormoved_{CONDITION} (an array).\r\n\r\nPre-defined conditions:\r\n    linechange\r\n        The line-number has changed.\r\n    parenthesis\r\n        Cursor is over (), [], or {}.\r\n    syntaxchange\r\n        The syntax group under the cursor has changed (i.e. the cursor \r\n        has moved in\/out of a syntax group.\r\n    syntaxleave\r\n        b:hookcursormoved_syntax (ARRAY) should contain the syntax names \r\n        which should run the hook code.\r\n    syntaxleave_oneline\r\n        Same as a above but check also for changes of the line number.\r\n\r\nIn order to define a new conditions, you have to define a function \r\n\"HookCursorMoved_{CONDITION}(mode)\", which returns true if the condition \r\nis met.\r\n\r\nFunctions are best registered using |hookcursormoved#Register()|.\r\nExample: >\r\n\r\n    function! WhatsGoingOn(mode) \"{{{3\r\n        if mode == 'i'\r\n            DoThis\r\n        elseif mode == 'n'\r\n            DoThat\r\n        endif\r\n    endf\r\n\r\n    call hookcursormoved#Register('b', 'syntaxchange', function('WhatsGoingOn'))\r\n\r\n","install_details":"Edit the vba file and type: >\r\n\r\n    :so %\r\n\r\nSee :help vimball for details. If you have difficulties or use vim 7.0,\r\nplease make sure, you have the current version of vimball\r\n(vimscript #1502) installed.\r\n\r\n\r\nAlso available via git\r\nhttp:\/\/github.com\/tomtom\/hookcursormoved_vim","5":"Edit the vba file and type: >\r\n\r\n    :so %\r\n\r\nSee :help vimball for details. If you have difficulties or use vim 7.0,\r\nplease make sure, you have the current version of vimball\r\n(vimscript #1502) installed.\r\n\r\n\r\nAlso available via git\r\nhttp:\/\/github.com\/tomtom\/hookcursormoved_vim","first_name":"Tom","6":"Tom","last_name":"Link","7":"Link","releases":[{"0":"2037","vim_version":"7.0","1":"7.0","script_version":"0.9","2":"0.9","version_comment":"- hookcursormoved#Register: Print a message on unknown hooks (don't throw an error)\r\n- hookcursormoved#Register: If g:hookcursormoved_linechange is undefined, assume the plugin wasn't loaded.","3":"- hookcursormoved#Register: Print a message on unknown hooks (don't throw an error)\r\n- hookcursormoved#Register: If g:hookcursormoved_linechange is undefined, assume the plugin wasn't loaded.","package":"hookcursormoved.vba.gz","4":"hookcursormoved.vba.gz","src_id":"11543","5":"11543","creation_date":"1255877541","6":"1255877541"},{"0":"2037","vim_version":"7.0","1":"7.0","script_version":"0.8","2":"0.8","version_comment":"hookcursormoved#Register: Allow deregister","3":"hookcursormoved#Register: Allow deregister","package":"hookcursormoved.vba.gz","4":"hookcursormoved.vba.gz","src_id":"8926","5":"8926","creation_date":"1215759756","6":"1215759756"},{"0":"2037","vim_version":"7.0","1":"7.0","script_version":"0.7","2":"0.7","version_comment":"- Minor tweaks\r\n- FIX: Check correct column in s:CheckChars()\r\n","3":"- Minor tweaks\r\n- FIX: Check correct column in s:CheckChars()\r\n","package":"hookcursormoved.vba.gz","4":"hookcursormoved.vba.gz","src_id":"7979","5":"7979","creation_date":"1195642708","6":"1195642708"},{"0":"2037","vim_version":"7.0","1":"7.0","script_version":"0.6","2":"0.6","version_comment":"- Check correct column in syntax* tests.","3":"- Check correct column in syntax* tests.","package":"hookcursormoved.vba.gz","4":"hookcursormoved.vba.gz","src_id":"7963","5":"7963","creation_date":"1195374609","6":"1195374609"},{"0":"2037","vim_version":"7.0","1":"7.0","script_version":"0.5","2":"0.5","version_comment":"- hookcursormoved#Register() takes mode as optional 3rd argument which \r\nallows to check a condition only in insert or only in normal mode.\r\n- Defined parenthesis_round_open and parenthesis_round_close.\r\n- Modes are now defined via the g:hookcursormoved_{mode} variable (the \r\nfunction name as string).\r\n","3":"- hookcursormoved#Register() takes mode as optional 3rd argument which \r\nallows to check a condition only in insert or only in normal mode.\r\n- Defined parenthesis_round_open and parenthesis_round_close.\r\n- Modes are now defined via the g:hookcursormoved_{mode} variable (the \r\nfunction name as string).\r\n","package":"hookcursormoved.vba.gz","4":"hookcursormoved.vba.gz","src_id":"7936","5":"7936","creation_date":"1194862906","6":"1194862906"},{"0":"2037","vim_version":"7.0","1":"7.0","script_version":"0.4","2":"0.4","version_comment":"- Defined parenthesis_round\r\n- FIX: parenthesis","3":"- Defined parenthesis_round\r\n- FIX: parenthesis","package":"hookcursormoved.vba.gz","4":"hookcursormoved.vba.gz","src_id":"7842","5":"7842","creation_date":"1193700148","6":"1193700148"},{"0":"2037","vim_version":"7.0","1":"7.0","script_version":"0.3","2":"0.3","version_comment":"- Defined parenthesis, syntaxleave_oneline conditions\r\n- Removed namespace parameter (everything is buffer-local)\r\n- Perform less checks (this should be no problem, if you use #Register).\r\n","3":"- Defined parenthesis, syntaxleave_oneline conditions\r\n- Removed namespace parameter (everything is buffer-local)\r\n- Perform less checks (this should be no problem, if you use #Register).\r\n","package":"hookcursormoved.vba.gz","4":"hookcursormoved.vba.gz","src_id":"7787","5":"7787","creation_date":"1192228842","6":"1192228842"},{"0":"2037","vim_version":"7.0","1":"7.0","script_version":"0.2","2":"0.2","version_comment":"- Renamed s:Enable() to hookcursormoved#Enable()\r\n- Renamed s:enabled to b:hookcursormoved_enabled\r\n","3":"- Renamed s:Enable() to hookcursormoved#Enable()\r\n- Renamed s:enabled to b:hookcursormoved_enabled\r\n","package":"hookcursormoved.vba.gz","4":"hookcursormoved.vba.gz","src_id":"7751","5":"7751","creation_date":"1191495447","6":"1191495447"}]},"2036":{"script_id":"2036","0":"2036","script_name":"F6_Comment","1":"F6_Comment","script_type":"utility","2":"utility","summary":"Auto commenting that accepts Visual range","3":"Auto commenting that accepts Visual range","description":"Description:\r\nI don't know for sure that something like this does not already exist in Vim, but if it does, I can't find it.\r\n\r\nI recall Cream having this kind of functionallity mapped to <F6>,\r\nso to maintain consistency I've kept the convention.\r\n\r\nThis uses the current value of &cms \/ &commentstring to comment and uncomment code.\r\nIt works for ranges selected in Visual mode, or for the current line in all modes.\r\nNB. Comment strings may not include '@' or '+'\r\n(I don't know of any languages that use these characters for comments).\r\n\r\nHelp:\r\nUse <F6> to comment, and <S-F6> to uncomment\r\n","4":"Description:\r\nI don't know for sure that something like this does not already exist in Vim, but if it does, I can't find it.\r\n\r\nI recall Cream having this kind of functionallity mapped to <F6>,\r\nso to maintain consistency I've kept the convention.\r\n\r\nThis uses the current value of &cms \/ &commentstring to comment and uncomment code.\r\nIt works for ranges selected in Visual mode, or for the current line in all modes.\r\nNB. Comment strings may not include '@' or '+'\r\n(I don't know of any languages that use these characters for comments).\r\n\r\nHelp:\r\nUse <F6> to comment, and <S-F6> to uncomment\r\n","install_details":"Just put it in your plugin directory.","5":"Just put it in your plugin directory.","first_name":"David","6":"David","last_name":"Maclay","7":"Maclay","releases":[{"0":"2036","vim_version":"7.0","1":"7.0","script_version":"1.2","2":"1.2","version_comment":"This version puts the first comment on a line after any leading whitespace.","3":"This version puts the first comment on a line after any leading whitespace.","package":"F6_Comment.vim","4":"F6_Comment.vim","src_id":"8018","5":"8018","creation_date":"1196686456","6":"1196686456"},{"0":"2036","vim_version":"7.0","1":"7.0","script_version":"1.1","2":"1.1","version_comment":"Set the vim file format to \"unix\"","3":"Set the vim file format to \"unix\"","package":"F6_Comment.vim","4":"F6_Comment.vim","src_id":"7760","5":"7760","creation_date":"1191727661","6":"1191727661"},{"0":"2036","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"F6_Comment.vim","4":"F6_Comment.vim","src_id":"7742","5":"7742","creation_date":"1191406526","6":"1191406526"}]},"2035":{"script_id":"2035","0":"2035","script_name":"F6_Comment (old)","1":"F6_Comment (old)","script_type":"utility","2":"utility","summary":"Auto commenting that accepts Visual range","3":"Auto commenting that accepts Visual range","description":"******************************************************************\r\nNB.  I accidentally uploaded this script twice, this instance needs to be deleted,\r\n         and the copy listed under Vim 7.0 should be kept.\r\n         I just don't know how to do this ... sorry.\r\n******************************************************************\r\n\r\n\r\nDescription:\r\nI don't know for sure that something like this does not already exist in Vim, but if it does, I can't find it.\r\n\r\nI recall Cream having this kind of functionallity mapped to <F6>,\r\nso to maintain consistency I've kept the convention.\r\n\r\nThis uses the current value of &cms \/ &commentstring to comment and uncomment code.\r\nIt works for ranges selected in Visual mode, or for the current line in all modes.\r\nNB. Comment strings may not include '@' or '+'\r\n(I don't know of any languages that use these characters).\r\n\r\nHelp:\r\nUse <F6> to comment, and <S-F6> to uncomment\r\n","4":"******************************************************************\r\nNB.  I accidentally uploaded this script twice, this instance needs to be deleted,\r\n         and the copy listed under Vim 7.0 should be kept.\r\n         I just don't know how to do this ... sorry.\r\n******************************************************************\r\n\r\n\r\nDescription:\r\nI don't know for sure that something like this does not already exist in Vim, but if it does, I can't find it.\r\n\r\nI recall Cream having this kind of functionallity mapped to <F6>,\r\nso to maintain consistency I've kept the convention.\r\n\r\nThis uses the current value of &cms \/ &commentstring to comment and uncomment code.\r\nIt works for ranges selected in Visual mode, or for the current line in all modes.\r\nNB. Comment strings may not include '@' or '+'\r\n(I don't know of any languages that use these characters).\r\n\r\nHelp:\r\nUse <F6> to comment, and <S-F6> to uncomment\r\n","install_details":"","5":"","first_name":"David","6":"David","last_name":"Maclay","7":"Maclay","releases":[{"0":"2035","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"F6_Comment.vim","4":"F6_Comment.vim","src_id":"7741","5":"7741","creation_date":"1191406523","6":"1191406523"}]},"2034":{"script_id":"2034","0":"2034","script_name":"colorful256.vim","1":"colorful256.vim","script_type":"color scheme","2":"color scheme","summary":"initial upload","3":"initial upload","description":"This is high contrast colorscheme. Not advisable during night.\r\n Dark background and used lot of colors mostly yellow and light blue shades.\r\n Only for console version which supports 256 colors.\r\n Please make sure to set t_Co=256 before calling the colorscheme.\r\n  ","4":"This is high contrast colorscheme. Not advisable during night.\r\n Dark background and used lot of colors mostly yellow and light blue shades.\r\n Only for console version which supports 256 colors.\r\n Please make sure to set t_Co=256 before calling the colorscheme.\r\n  ","install_details":"Copy this file to your private or public colors-directory. ","5":"Copy this file to your private or public colors-directory. ","first_name":"jagpreet","6":"jagpreet","last_name":"chhabra","7":"chhabra","releases":[{"0":"2034","vim_version":"7.0","1":"7.0","script_version":"1.1","2":"1.1","version_comment":"couple of color changes.\r\nadded colors for GUI terminal.","3":"couple of color changes.\r\nadded colors for GUI terminal.","package":"colorful256.vim","4":"colorful256.vim","src_id":"7746","5":"7746","creation_date":"1191465728","6":"1191465728"},{"0":"2034","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"colorful256.vim","4":"colorful256.vim","src_id":"7739","5":"7739","creation_date":"1191371604","6":"1191371604"}]},"2033":{"script_id":"2033","0":"2033","script_name":"trag","1":"trag","script_type":"utility","2":"utility","summary":"A language-aware source code scanner (with support for git grep, ack, ag, sift)","3":"A language-aware source code scanner (with support for git grep, ack, ag, sift)","description":"This plugin uses ad-hoc searches to find strings in files. For certain \r\nlanguages, it can also find variable\/function\/class definitions, \r\nfunction calls etc.\r\n\r\nOther than |tags| or |cscope|, it doesn't build a database to speed up \r\nsearches but always scans all files. It can make use of the following \r\nexternal tools in order to gain acceptable performance for medium-sized \r\nprojects:\r\n\r\n    - `git grep`\r\n    - `ack` http:\/\/beyondgrep.com\/\r\n    - `ag` https:\/\/github.com\/ggreer\/the_silver_searcher\r\n    - `sift` https:\/\/sift-tool.org\/\r\n\r\nThe builtin vimscript-based version file scanner and also \r\n|vimgrep| are suitable for small projects. See |g:trag#grep_type| for \r\navailable options.\r\n\r\n\r\nUsage~\r\n\r\nFirst, define which files belong to your project. See \r\n|g:trag#file_sources| for available sources. If the variable contains \r\n\"vcs\" and the current buffer is under control of a supported VCS, trag \r\nwill scan the files in the VCS. Maybe your project's source files are \r\nalready registered in your tags files, in which case those will be used.\r\n\r\nSecondly, use |:Trag| to scan your project's files. You can restrict searches \r\nto certain \"kinds\" like only variable definitions or only function calls. See \r\n|trag-kinds| for details.\r\n\r\nYou can also type <Leader>r# to search for the word under cursor (see \r\n|g:trag_map_leader| and |TragInstallMap()| for details on maps). In \r\nsupported filetypes, <Leader>rd will search for the definition of the \r\nword under cursor.\r\n\r\nCurrently the following filetypes are supported:\r\n\r\n    - java\r\n    - javascript\r\n    - json\r\n    - make\r\n    - r\r\n    - ruby\r\n    - viki\r\n    - vim\r\n\r\nRun `:echo globpath(&rtp, 'ftplugin\/*\/trag.vim')` to get a full listing \r\nof supported filetypes.\r\n\r\nNOTE: Some kinds are available only for a subset of known filetypes.\r\n\r\nDefault maps:\r\n\r\n    <Leader>r# ... Trag the word under cursor\r\n    <Leader>r. ... :Trag command-line\r\n    <Leader>r+ ... Show quickfixlist via |:Tragcw|\r\n    <Leader>r* ... Edit a file from the files list, i.e. the list that would be \r\n                   used if no \"--file_sources\" argument were passed to \r\n                   |:Trag|\r\n    <Leader>rx ... The same as `:Trag -l -i=x -x=i <cword><cr>`\r\n                   where x is a alphabetical letter that describes a kind in \r\n                   |g:trag_kinds| and <cword> is the word under cursor.\r\n                   \"-x=i\" (exclude commented text) is only added if kind x is \r\n                   in |g:trag_kinds_ignored_comments|.\r\n","4":"This plugin uses ad-hoc searches to find strings in files. For certain \r\nlanguages, it can also find variable\/function\/class definitions, \r\nfunction calls etc.\r\n\r\nOther than |tags| or |cscope|, it doesn't build a database to speed up \r\nsearches but always scans all files. It can make use of the following \r\nexternal tools in order to gain acceptable performance for medium-sized \r\nprojects:\r\n\r\n    - `git grep`\r\n    - `ack` http:\/\/beyondgrep.com\/\r\n    - `ag` https:\/\/github.com\/ggreer\/the_silver_searcher\r\n    - `sift` https:\/\/sift-tool.org\/\r\n\r\nThe builtin vimscript-based version file scanner and also \r\n|vimgrep| are suitable for small projects. See |g:trag#grep_type| for \r\navailable options.\r\n\r\n\r\nUsage~\r\n\r\nFirst, define which files belong to your project. See \r\n|g:trag#file_sources| for available sources. If the variable contains \r\n\"vcs\" and the current buffer is under control of a supported VCS, trag \r\nwill scan the files in the VCS. Maybe your project's source files are \r\nalready registered in your tags files, in which case those will be used.\r\n\r\nSecondly, use |:Trag| to scan your project's files. You can restrict searches \r\nto certain \"kinds\" like only variable definitions or only function calls. See \r\n|trag-kinds| for details.\r\n\r\nYou can also type <Leader>r# to search for the word under cursor (see \r\n|g:trag_map_leader| and |TragInstallMap()| for details on maps). In \r\nsupported filetypes, <Leader>rd will search for the definition of the \r\nword under cursor.\r\n\r\nCurrently the following filetypes are supported:\r\n\r\n    - java\r\n    - javascript\r\n    - json\r\n    - make\r\n    - r\r\n    - ruby\r\n    - viki\r\n    - vim\r\n\r\nRun `:echo globpath(&rtp, 'ftplugin\/*\/trag.vim')` to get a full listing \r\nof supported filetypes.\r\n\r\nNOTE: Some kinds are available only for a subset of known filetypes.\r\n\r\nDefault maps:\r\n\r\n    <Leader>r# ... Trag the word under cursor\r\n    <Leader>r. ... :Trag command-line\r\n    <Leader>r+ ... Show quickfixlist via |:Tragcw|\r\n    <Leader>r* ... Edit a file from the files list, i.e. the list that would be \r\n                   used if no \"--file_sources\" argument were passed to \r\n                   |:Trag|\r\n    <Leader>rx ... The same as `:Trag -l -i=x -x=i <cword><cr>`\r\n                   where x is a alphabetical letter that describes a kind in \r\n                   |g:trag_kinds| and <cword> is the word under cursor.\r\n                   \"-x=i\" (exclude commented text) is only added if kind x is \r\n                   in |g:trag_kinds_ignored_comments|.\r\n","install_details":"To install the vimball, edit the vba file and type: >\r\n\r\n    :so %\r\n\r\nSee :help vimball for details.\r\n\r\nTo install from github, please use\r\n    1. git + a plugin loader like enable_vim, pathogen, vim-unbundle etc.\r\n    2. a plugin manager like VAM, Vundle, NeoBundle, vim-plug etc.\r\n\r\nThe tlib_vim plugin is required:\r\nhttps:\/\/github.com\/tomtom\/tlib_vim\r\n\r\nAlso available via git: http:\/\/github.com\/tomtom\/trag_vim\r\n","5":"To install the vimball, edit the vba file and type: >\r\n\r\n    :so %\r\n\r\nSee :help vimball for details.\r\n\r\nTo install from github, please use\r\n    1. git + a plugin loader like enable_vim, pathogen, vim-unbundle etc.\r\n    2. a plugin manager like VAM, Vundle, NeoBundle, vim-plug etc.\r\n\r\nThe tlib_vim plugin is required:\r\nhttps:\/\/github.com\/tomtom\/tlib_vim\r\n\r\nAlso available via git: http:\/\/github.com\/tomtom\/trag_vim\r\n","first_name":"Tom","6":"Tom","last_name":"Link","7":"Link","releases":[{"0":"2033","vim_version":"7.0","1":"7.0","script_version":"2.00","2":"2.00","version_comment":"- Require tlib 1.14; use tlib#file#Edit()\n- Move ftplugin\/* -> autoload\/trag\/ft\/*\n- trag#ScanWithGrepDefs() etc.\n- a:leader .'+' map -> :Tragcw\n- trag#ScanWithGrepDefs(): Return values(qfl)\n- Misc fixes\n- GrepWith_external(): strip text\n- trag#utils#GrepaddFiles(): Use shellescape()\n- Support for sift (https:\/\/sift-tool.org)\n- Support for markdown\n- Move qfl\/loclist browser to tlib; require tlib 1.15\n- trag#BrowseList: deepcopy g:trag#world\n- trag#BrowseList: Use copy()\n- Breaking change: Use tlib#arg#GetOpts\n- :Tragsearch --file_sources command-line option\n- trag#Grep: Use return\n- s:GrepWith_external: Don't check if executable for grep_type == vcs\n- s:GrepWith_external(): Don't use deepcopy\n- s:GetRx(): don't precalc fnamemodify()\n- Removed :Tragfile, :Traggrep, :Tragsetfiles, :Tragaddfiles, :Tragclearfiles, :TragGitFiles, :TragRepoFiles\n- g:trag#file_sources: support for function sources; various improvements\n- Re-introduce :Tragfiles command\n- Deprecate trag#Grep()\n- FIX maps\n- Remove Tragsearch command; s\/TLibTrace\/Tlibtrace\/g\nMD5 checksum: 099e3abc4020163be874d233f90b59f1","3":"- Require tlib 1.14; use tlib#file#Edit()\n- Move ftplugin\/* -> autoload\/trag\/ft\/*\n- trag#ScanWithGrepDefs() etc.\n- a:leader .'+' map -> :Tragcw\n- trag#ScanWithGrepDefs(): Return values(qfl)\n- Misc fixes\n- GrepWith_external(): strip text\n- trag#utils#GrepaddFiles(): Use shellescape()\n- Support for sift (https:\/\/sift-tool.org)\n- Support for markdown\n- Move qfl\/loclist browser to tlib; require tlib 1.15\n- trag#BrowseList: deepcopy g:trag#world\n- trag#BrowseList: Use copy()\n- Breaking change: Use tlib#arg#GetOpts\n- :Tragsearch --file_sources command-line option\n- trag#Grep: Use return\n- s:GrepWith_external: Don't check if executable for grep_type == vcs\n- s:GrepWith_external(): Don't use deepcopy\n- s:GetRx(): don't precalc fnamemodify()\n- Removed :Tragfile, :Traggrep, :Tragsetfiles, :Tragaddfiles, :Tragclearfiles, :TragGitFiles, :TragRepoFiles\n- g:trag#file_sources: support for function sources; various improvements\n- Re-introduce :Tragfiles command\n- Deprecate trag#Grep()\n- FIX maps\n- Remove Tragsearch command; s\/TLibTrace\/Tlibtrace\/g\nMD5 checksum: 099e3abc4020163be874d233f90b59f1","package":"trag.vba","4":"trag.vba","src_id":"23725","5":"23725","creation_date":"1447087826","6":"1447087826"},{"0":"2033","vim_version":"7.0","1":"7.0","script_version":"1.02","2":"1.02","version_comment":"- trag#Edit(): Don't set initial filter when the source of the files listing was a VCS\n- trag#InitListBuffer: Use set_syntax\n- trag#GetFilename() instead of s:GetFilename()\n- FormatBase(): Allow customization via format_item\nMD5 checksum: 738c7a98299f22507000ab21a53d7b2f","3":"- trag#Edit(): Don't set initial filter when the source of the files listing was a VCS\n- trag#InitListBuffer: Use set_syntax\n- trag#GetFilename() instead of s:GetFilename()\n- FormatBase(): Allow customization via format_item\nMD5 checksum: 738c7a98299f22507000ab21a53d7b2f","package":"trag.vba","4":"trag.vba","src_id":"22593","5":"22593","creation_date":"1414921706","6":"1414921706"},{"0":"2033","vim_version":"7.0","1":"7.0","script_version":"1.01","2":"1.01","version_comment":"- trag#utils#GrepaddFiles(): Use shellescape(..., 1)\n- g:trag#debug: Hide warnings by default\n- Make sure not to run git grep on files outside of the repo (use trag instead; require tlib 0.112)\n- Minor improvements; g:trag#grep_fallback_type\n- GrepWith_external(): bufnr optimization\n- GrepWith_external(): normalize filenames\n- ag: Don't use -Q for \"identity\"\nMD5 checksum: 3c5f2c7653a0345612891fe614655997","3":"- trag#utils#GrepaddFiles(): Use shellescape(..., 1)\n- g:trag#debug: Hide warnings by default\n- Make sure not to run git grep on files outside of the repo (use trag instead; require tlib 0.112)\n- Minor improvements; g:trag#grep_fallback_type\n- GrepWith_external(): bufnr optimization\n- GrepWith_external(): normalize filenames\n- ag: Don't use -Q for \"identity\"\nMD5 checksum: 3c5f2c7653a0345612891fe614655997","package":"trag.vba","4":"trag.vba","src_id":"22160","5":"22160","creation_date":"1404756535","6":"1404756535"},{"0":"2033","vim_version":"7.0","1":"7.0","script_version":"1.00","2":"1.00","version_comment":"- addon-info\n- <c-l> Edit line\n- Help template\n- trag#RunCmdOnSelected(): Optionally use w.GetBufferLines() if provided (see vikitasks #104b45b)\n- trag#RunCmdOnSelected(): Preliminary support for w.AfterRunCmd()\n- trag#Grep(): Takes filetype as second optional argument\n- g:trag#grep_type replaces g:trag_search_mode\n- g:trag_map_leader, TragInstallMap(), TragInstallKindMap(): Make it easier to set up maps\n- trag#GetGitFiles(): Use g:tlib#dir#sep, not the obsolete g:tlib_filename_sep\n- Rename most commands matching TRag* -> Trag*\n- trag#SetRepoFiles(): Use files in current VCS repo\n- trag#Grep(): Refactor to enable use of external grep commands\n- s:GetRx(): Return [posrx, filetype]\n- First draft for use of external grep\n- vim: Use :grepadd\n- Further improvements to allow use of external grep commands\n- Initial support for VCS (e.g. git grep)\n- g:trag#file_sources: Define source for file lists\n- trag#external#vcs#Run(): Use fnameescape()\n- Fixed some regexps\n- Rename s:trag_filenames to g:trag_extension_filetype\n- TRagDefKind: accepts an optional \"!\"\n- g:trag#file_sources can be buffer-local (b:trag_file_sources)\n- Remove references to trag#Process_*\n- trag#GetGitFiles(): Use \\%()\n- trag#external#grep#IsSupported(): Minor simplification\n- trag#external#vcs#Run(): Minor optimization\n- trag#DefFiletype()\n- trag#external#vcs#Run(): Use\n- Move filetype definitions to ftplugin\/*\/trag.vim\n- json support\n- FIX javascript regexp\n- Use viki for *.TXT\n- Draft for \"hg grep\" support (currently disabled due to poor performance)\n- rx.vim: Convert regexps\n- trag#utils#GrepaddFiles(): Process files in batches\n- Adapt vcs to previous changes\n- Improved support for grep\n- Support for ack\n- b:trag_grep_type: Buffer-local g:trag#grep_type\n- GrepWith_grep, GrepWith_ack\n- g:trag#file_sources: tags support\n- Rename g:trag#external#ack#ack_params to g:trag#external#ack#opts\n- Support for ag (the_silver_searcher)\n- FIX javascript l regexp\n- g:trag_kinds_ignored_comments: A list of kinds for which |TragInstallKindMap()| will install maps that ignore comments\n- New kind: \"u\" (uses of word; ignore comments)\n- trag#utils#GrepaddFiles(): Escape \"()\" in filenames\n- trag#rx#ConvertRx_perl(): Handle \\{-}, \\+, \\?\n- trag#utils#GrepaddFiles(): Use shellescape()\n- Support for Makefiles\nMD5 checksum: c87df75189cfb7574a10ba093bf60a0a","3":"- addon-info\n- <c-l> Edit line\n- Help template\n- trag#RunCmdOnSelected(): Optionally use w.GetBufferLines() if provided (see vikitasks #104b45b)\n- trag#RunCmdOnSelected(): Preliminary support for w.AfterRunCmd()\n- trag#Grep(): Takes filetype as second optional argument\n- g:trag#grep_type replaces g:trag_search_mode\n- g:trag_map_leader, TragInstallMap(), TragInstallKindMap(): Make it easier to set up maps\n- trag#GetGitFiles(): Use g:tlib#dir#sep, not the obsolete g:tlib_filename_sep\n- Rename most commands matching TRag* -> Trag*\n- trag#SetRepoFiles(): Use files in current VCS repo\n- trag#Grep(): Refactor to enable use of external grep commands\n- s:GetRx(): Return [posrx, filetype]\n- First draft for use of external grep\n- vim: Use :grepadd\n- Further improvements to allow use of external grep commands\n- Initial support for VCS (e.g. git grep)\n- g:trag#file_sources: Define source for file lists\n- trag#external#vcs#Run(): Use fnameescape()\n- Fixed some regexps\n- Rename s:trag_filenames to g:trag_extension_filetype\n- TRagDefKind: accepts an optional \"!\"\n- g:trag#file_sources can be buffer-local (b:trag_file_sources)\n- Remove references to trag#Process_*\n- trag#GetGitFiles(): Use \\%()\n- trag#external#grep#IsSupported(): Minor simplification\n- trag#external#vcs#Run(): Minor optimization\n- trag#DefFiletype()\n- trag#external#vcs#Run(): Use\n- Move filetype definitions to ftplugin\/*\/trag.vim\n- json support\n- FIX javascript regexp\n- Use viki for *.TXT\n- Draft for \"hg grep\" support (currently disabled due to poor performance)\n- rx.vim: Convert regexps\n- trag#utils#GrepaddFiles(): Process files in batches\n- Adapt vcs to previous changes\n- Improved support for grep\n- Support for ack\n- b:trag_grep_type: Buffer-local g:trag#grep_type\n- GrepWith_grep, GrepWith_ack\n- g:trag#file_sources: tags support\n- Rename g:trag#external#ack#ack_params to g:trag#external#ack#opts\n- Support for ag (the_silver_searcher)\n- FIX javascript l regexp\n- g:trag_kinds_ignored_comments: A list of kinds for which |TragInstallKindMap()| will install maps that ignore comments\n- New kind: \"u\" (uses of word; ignore comments)\n- trag#utils#GrepaddFiles(): Escape \"()\" in filenames\n- trag#rx#ConvertRx_perl(): Handle \\{-}, \\+, \\?\n- trag#utils#GrepaddFiles(): Use shellescape()\n- Support for Makefiles\nMD5 checksum: c87df75189cfb7574a10ba093bf60a0a","package":"trag.vba","4":"trag.vba","src_id":"22134","5":"22134","creation_date":"1404566831","6":"1404566831"},{"0":"2033","vim_version":"7.0","1":"7.0","script_version":"0.11","2":"0.11","version_comment":"- trag#LocList(): Take world & suspended as arguments (like #BrowseList())\n- Be more clever at guessing the filetype (allow filenames as patterns)\n- No direct external access to trag_filenames\n- g:trag#check_vcs: If the file is under a VCS, scan through all files in the VCS (requires tlib 0.44)\n- trag#AgentWithSelected(): cmd as optional argument\n- s:DoAutoCmd(): call event only if one is defined\n- Show item in balloon (if available)\n- trag#RunCmdOnSelected(): Optional argument: Don't close scratch\nMD5 checksum: e4bc34f9c3ef3ce134f2c41918d0922d","3":"- trag#LocList(): Take world & suspended as arguments (like #BrowseList())\n- Be more clever at guessing the filetype (allow filenames as patterns)\n- No direct external access to trag_filenames\n- g:trag#check_vcs: If the file is under a VCS, scan through all files in the VCS (requires tlib 0.44)\n- trag#AgentWithSelected(): cmd as optional argument\n- s:DoAutoCmd(): call event only if one is defined\n- Show item in balloon (if available)\n- trag#RunCmdOnSelected(): Optional argument: Don't close scratch\nMD5 checksum: e4bc34f9c3ef3ce134f2c41918d0922d","package":"trag.vba","4":"trag.vba","src_id":"18705","5":"18705","creation_date":"1348830703","6":"1348830703"},{"0":"2033","vim_version":"7.0","1":"7.0","script_version":"0.09","2":"0.09","version_comment":"- Don't hide the window if all error numbers are -1\n- .gitignore\n- trag#Grep(): trigger QuickFixCmdPre & QuickFixCmdPost events for \"trag\"\n- trag#LocList() used qfl\nMD5 checksum: 255a58b855b4e21462b517826c88fd91","3":"- Don't hide the window if all error numbers are -1\n- .gitignore\n- trag#Grep(): trigger QuickFixCmdPre & QuickFixCmdPost events for \"trag\"\n- trag#LocList() used qfl\nMD5 checksum: 255a58b855b4e21462b517826c88fd91","package":"trag.vba","4":"trag.vba","src_id":"17290","5":"17290","creation_date":"1327167898","6":"1327167898"},{"0":"2033","vim_version":"7.0","1":"7.0","script_version":"0.8","2":"0.8","version_comment":"- Moved the definition of some variables from plugin\/trag.vim to autoload\/trag.vim\r\n- :TRagcw! (show :cw even if there are no recognized errors)\r\n- Require tlib 0.37\r\n","3":"- Moved the definition of some variables from plugin\/trag.vim to autoload\/trag.vim\r\n- :TRagcw! (show :cw even if there are no recognized errors)\r\n- Require tlib 0.37\r\n","package":"trag.vba","4":"trag.vba","src_id":"12752","5":"12752","creation_date":"1270054405","6":"1270054405"},{"0":"2033","vim_version":"7.0","1":"7.0","script_version":"0.7","2":"0.7","version_comment":"- trag#QuickList(): Accept a dict as optional argument.\r\n- trag#Grep(): rx defaults to '\\.{-}'\r\n- trag#Grep(): use :g (instead of search()) for non-vimgrep mode\r\n","3":"- trag#QuickList(): Accept a dict as optional argument.\r\n- trag#Grep(): rx defaults to '\\.{-}'\r\n- trag#Grep(): use :g (instead of search()) for non-vimgrep mode\r\n","package":"trag.vba.gz","4":"trag.vba.gz","src_id":"11932","5":"11932","creation_date":"1261423904","6":"1261423904"},{"0":"2033","vim_version":"7.0","1":"7.0","script_version":"0.6","2":"0.6","version_comment":"- trag#viki#Rename()\r\n- Generalized trag#rename#Rename()\r\n- Enabled \"trace cursor\" functionality (mapped to the <c-insert> key).\r\n- :Traglw\r\n- TRagGitFiles, trag#SetGitFiles(), g:trag_git","3":"- trag#viki#Rename()\r\n- Generalized trag#rename#Rename()\r\n- Enabled \"trace cursor\" functionality (mapped to the <c-insert> key).\r\n- :Traglw\r\n- TRagGitFiles, trag#SetGitFiles(), g:trag_git","package":"trag.vba.gz","4":"trag.vba.gz","src_id":"11546","5":"11546","creation_date":"1255877709","6":"1255877709"},{"0":"2033","vim_version":"7.0","1":"7.0","script_version":"0.5","2":"0.5","version_comment":"- Update the qfl when running a command on selected lines\r\n- Enable certain operations for multiple choices\r\n- Java, Ruby: x ... find subclasses (extends\/implements)\r\n- Experimental rename command for refactoring (general, java)\r\n- NEW: [bg]:trag_get_files_{&filetype}\r\n- Traggrep: If the second argument (glob pattern) is missing, the \r\ndefault file list will be used.\r\n","3":"- Update the qfl when running a command on selected lines\r\n- Enable certain operations for multiple choices\r\n- Java, Ruby: x ... find subclasses (extends\/implements)\r\n- Experimental rename command for refactoring (general, java)\r\n- NEW: [bg]:trag_get_files_{&filetype}\r\n- Traggrep: If the second argument (glob pattern) is missing, the \r\ndefault file list will be used.\r\n","package":"trag.vba.gz","4":"trag.vba.gz","src_id":"10036","5":"10036","creation_date":"1235593653","6":"1235593653"},{"0":"2033","vim_version":"7.0","1":"7.0","script_version":"0.4","2":"0.4","version_comment":"- trag_proj* variables were renamed to trag_project*.\r\n- Traggrep: Arguments have changed for conformity with grep commands (an implicit .-argument is prepended)\r\n- Make sure tlib is loaded even if it is installed in a different rtp-directory.\r\n- Post-process lines (strip whitespace) collected by vimgrep\r\n- tlib#Edit(): for list input, set pick_last_item=0, show_empty=1\r\n- Aliases for some commands: Trag, Traggrep ...\r\n","3":"- trag_proj* variables were renamed to trag_project*.\r\n- Traggrep: Arguments have changed for conformity with grep commands (an implicit .-argument is prepended)\r\n- Make sure tlib is loaded even if it is installed in a different rtp-directory.\r\n- Post-process lines (strip whitespace) collected by vimgrep\r\n- tlib#Edit(): for list input, set pick_last_item=0, show_empty=1\r\n- Aliases for some commands: Trag, Traggrep ...\r\n","package":"trag.vba.gz","4":"trag.vba.gz","src_id":"9545","5":"9545","creation_date":"1227378982","6":"1227378982"},{"0":"2033","vim_version":"7.0","1":"7.0","script_version":"0.3","2":"0.3","version_comment":"- Use vimgrep with set ei=all as default search mode (can be configured via g:trag_search_mode); by default trag now is a wrapper around vimgrep that does the handling of project-related file-sets and regexp builing for you.\r\n- FIX: ruby\/f regexp\r\n","3":"- Use vimgrep with set ei=all as default search mode (can be configured via g:trag_search_mode); by default trag now is a wrapper around vimgrep that does the handling of project-related file-sets and regexp builing for you.\r\n- FIX: ruby\/f regexp\r\n","package":"trag.vba.gz","4":"trag.vba.gz","src_id":"8350","5":"8350","creation_date":"1203987444","6":"1203987444"},{"0":"2033","vim_version":"7.0","1":"7.0","script_version":"0.2","2":"0.2","version_comment":"- Quite a few things have changed and I haven't had the time yet to test \r\nthese changes thorougly. There is a chance that nested patterns thus \r\ndon't work as described (please report).\r\n- Enable search for more than one kinds at once (as comma-separated \r\nlist)\r\n- Enabled <c-e>: Run ex-command on selected lines (e.g. for refactoring \r\npurposes)\r\n- Enabled <c-s>, <c-v>, <c-t>: Open selected lines in (vertically) split \r\nwindows or tabs.\r\n- Renamed vV kinds to lL (~ let)\r\n- New kind: r\/R (right hand side argument of an assignment\/let, i.e. \r\nvalue)\r\n- New kind: fuzzy (typo-tolerant search)\r\n- INCOMPATIBLE CHANGE: Renamed \"mode\" to \"kind\"\r\n- TRag now has some idea of negation. E.g., \"TRag !i,w call\" will search \r\nfor the word \"call\" but ignore matches in comments (if defined for the \r\n    current filetype)\r\n- Alternative methods to define project files: g:trag_files, \r\ng:trag_glob, g:trag_proj.\r\n- Improved support for ruby, vim\r\n- TRagKeyword, trag#CWord(): Customize keyword rx.\r\n- g:trag_get_files\r\n- [bg]:trag_proj_{&filetype}: Name of the filetype-specific project \r\nfiles catalog (overrides [bg]:trag_proj if defined)\r\n- trag#Edit() will now initally select files with the same \"basename \r\nroot\" (^\\w\\+) as the current buffer (the command is thus slightly more \r\nuseful and can be used as an ad-hoc alternative file switcher)\r\n- FIX: Match a line only once\r\n- FIX: Caching of regexps\r\n","3":"- Quite a few things have changed and I haven't had the time yet to test \r\nthese changes thorougly. There is a chance that nested patterns thus \r\ndon't work as described (please report).\r\n- Enable search for more than one kinds at once (as comma-separated \r\nlist)\r\n- Enabled <c-e>: Run ex-command on selected lines (e.g. for refactoring \r\npurposes)\r\n- Enabled <c-s>, <c-v>, <c-t>: Open selected lines in (vertically) split \r\nwindows or tabs.\r\n- Renamed vV kinds to lL (~ let)\r\n- New kind: r\/R (right hand side argument of an assignment\/let, i.e. \r\nvalue)\r\n- New kind: fuzzy (typo-tolerant search)\r\n- INCOMPATIBLE CHANGE: Renamed \"mode\" to \"kind\"\r\n- TRag now has some idea of negation. E.g., \"TRag !i,w call\" will search \r\nfor the word \"call\" but ignore matches in comments (if defined for the \r\n    current filetype)\r\n- Alternative methods to define project files: g:trag_files, \r\ng:trag_glob, g:trag_proj.\r\n- Improved support for ruby, vim\r\n- TRagKeyword, trag#CWord(): Customize keyword rx.\r\n- g:trag_get_files\r\n- [bg]:trag_proj_{&filetype}: Name of the filetype-specific project \r\nfiles catalog (overrides [bg]:trag_proj if defined)\r\n- trag#Edit() will now initally select files with the same \"basename \r\nroot\" (^\\w\\+) as the current buffer (the command is thus slightly more \r\nuseful and can be used as an ad-hoc alternative file switcher)\r\n- FIX: Match a line only once\r\n- FIX: Caching of regexps\r\n","package":"trag.vba.gz","4":"trag.vba.gz","src_id":"8307","5":"8307","creation_date":"1203408790","6":"1203408790"},{"0":"2033","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"trag.vba.gz","4":"trag.vba.gz","src_id":"7734","5":"7734","creation_date":"1191155777","6":"1191155777"}]},"2032":{"script_id":"2032","0":"2032","script_name":"swap parameters","1":"swap parameters","script_type":"utility","2":"utility","summary":"swap parameters of a function (requires python)","3":"swap parameters of a function (requires python)","description":"Requires python and Vim compiled with +python option\r\n\r\nBasic Usecase: Place the cursor inside the parameter you want to swap\r\nwith the next one, and press gs\r\n\r\nIt is a versatile script to swap parameters of a function\r\nor, generally speaking, elements in any coma seperated list.\r\n\r\nkey bindings (normal mode):\r\n[count]gs -- where count defaults to 1 -- swap the argument under\r\n             the cursor with the [count] next one\r\n[count]gS -- swap with the previous one\r\n\r\n\r\nBelow are exaples of what happens after pressing gs (equivalent to 1gs).\r\nPrettier version can be found here: \r\nhttp:\/\/blog.kamil.dworakowski.name\/2007\/09\/swap-parameters-script-for-vim.html.\r\nOn each line the lefthand side shows the line before typing gs, and\r\nthe righthand side shows the effect. The cursor position is depicted\r\nwith || symbols. par|m|1 means that the cursor is on the character m.\r\n\r\nfun(par|m|1, parm2) ==> fun(parm2, parm|1|)\r\nfun(par|m|1(), parm2) ==> fun(parm2, parm1(|)|)\r\nfun(parm1(|)|, parm2) ==> fun(parm2, parm1(|)|)\r\nfun(parm|1|(arg,arg2), parm2) ==> fun(parm2, parm1(arg,arg2|)|)\r\nfun(parm1|(|arg,arg2), parm2) ==> fun(parm2, parm1(arg,arg2|)|)\r\nfun(parm1(arg,arg2|)|, parm2) ==> fun(parm2, parm1(arg,arg2|)|)\r\nfun(parm1(arg, arg2|)|, parm2) ==> fun(parm2, parm1(arg, arg2|)|)\r\nfun(arg1, ar|g|2, arg3) ==> fun(arg1, arg3, arg|2|)\r\narray[a|r|g1, arg2] ==> array[arg2, arg|1|]\r\nfun(par|m|1[], parm2) ==> fun(parm2, parm1[|]|)\r\nfun(parm1[|]|, parm2) ==> fun(parm2, parm1[|]|)\r\nfun(par|m|1, array[]) ==> fun(array[], parm|1|)\r\nfun(|a|,b) ==> fun(b,|a|)\r\n[(p1, p2|)|, p3] ==> [p3, (p1, p2|)|]\r\n\r\n\r\nThe following lines demonstrate using gS (swap with previous).\r\n\r\nfun(parm2, par|m|1) ==> fun(|p|arm1, parm2)\r\nfun(parm2, par|m|1()) ==> fun(|p|arm1(), parm2)\r\nfun(parm2, parm1(|)|) ==> fun(|p|arm1(), parm2)\r\nfun(parm2, parm|1|(arg,arg2)) ==> fun(|p|arm1(arg,arg2), parm2)\r\nfun(parm2, parm1|(|arg,arg2)) ==> fun(|p|arm1(arg,arg2), parm2)\r\nfun(parm2, parm1(arg,arg2|)|) ==> fun(|p|arm1(arg,arg2), parm2)\r\nfun(parm2, parm1(arg, arg2|)|) ==> fun(|p|arm1(arg, arg2), parm2)\r\nfun(arg1, ar|g|2, arg3) ==> fun(|a|rg2, arg1, arg3)\r\nfun(arg1, arg2, ar|g|3) ==> fun(arg1, |a|rg3, arg2)\r\narray[arg2, a|r|g1] ==> array[|a|rg1, arg2]\r\nfun(par|m|1[], parm2) ==> fun(|p|arm1[], parm2)\r\nfun(parm2, parm1[|]|) ==> fun(|p|arm1[], parm2)\r\nfun(array[], par|m|1) ==> fun(|p|arm1, array[])\r\nfun(b,|a|) ==> fun(|a|,b)\r\n\r\nA useful, however unexpected by the author, feature of this script is that\r\non pressing j to move cursor to the line below, the cursor is restored to \r\nthe column position before the swap. This allows for a streamlined\r\nswaping of parameters in the case like this:\r\n\r\nfun(arg2, arg1)\r\nfun(arg2, arg1)\r\nfun(arg2, arg1)\r\n\r\nYou would put cursor on arg2, and type gsjgsjgs","4":"Requires python and Vim compiled with +python option\r\n\r\nBasic Usecase: Place the cursor inside the parameter you want to swap\r\nwith the next one, and press gs\r\n\r\nIt is a versatile script to swap parameters of a function\r\nor, generally speaking, elements in any coma seperated list.\r\n\r\nkey bindings (normal mode):\r\n[count]gs -- where count defaults to 1 -- swap the argument under\r\n             the cursor with the [count] next one\r\n[count]gS -- swap with the previous one\r\n\r\n\r\nBelow are exaples of what happens after pressing gs (equivalent to 1gs).\r\nPrettier version can be found here: \r\nhttp:\/\/blog.kamil.dworakowski.name\/2007\/09\/swap-parameters-script-for-vim.html.\r\nOn each line the lefthand side shows the line before typing gs, and\r\nthe righthand side shows the effect. The cursor position is depicted\r\nwith || symbols. par|m|1 means that the cursor is on the character m.\r\n\r\nfun(par|m|1, parm2) ==> fun(parm2, parm|1|)\r\nfun(par|m|1(), parm2) ==> fun(parm2, parm1(|)|)\r\nfun(parm1(|)|, parm2) ==> fun(parm2, parm1(|)|)\r\nfun(parm|1|(arg,arg2), parm2) ==> fun(parm2, parm1(arg,arg2|)|)\r\nfun(parm1|(|arg,arg2), parm2) ==> fun(parm2, parm1(arg,arg2|)|)\r\nfun(parm1(arg,arg2|)|, parm2) ==> fun(parm2, parm1(arg,arg2|)|)\r\nfun(parm1(arg, arg2|)|, parm2) ==> fun(parm2, parm1(arg, arg2|)|)\r\nfun(arg1, ar|g|2, arg3) ==> fun(arg1, arg3, arg|2|)\r\narray[a|r|g1, arg2] ==> array[arg2, arg|1|]\r\nfun(par|m|1[], parm2) ==> fun(parm2, parm1[|]|)\r\nfun(parm1[|]|, parm2) ==> fun(parm2, parm1[|]|)\r\nfun(par|m|1, array[]) ==> fun(array[], parm|1|)\r\nfun(|a|,b) ==> fun(b,|a|)\r\n[(p1, p2|)|, p3] ==> [p3, (p1, p2|)|]\r\n\r\n\r\nThe following lines demonstrate using gS (swap with previous).\r\n\r\nfun(parm2, par|m|1) ==> fun(|p|arm1, parm2)\r\nfun(parm2, par|m|1()) ==> fun(|p|arm1(), parm2)\r\nfun(parm2, parm1(|)|) ==> fun(|p|arm1(), parm2)\r\nfun(parm2, parm|1|(arg,arg2)) ==> fun(|p|arm1(arg,arg2), parm2)\r\nfun(parm2, parm1|(|arg,arg2)) ==> fun(|p|arm1(arg,arg2), parm2)\r\nfun(parm2, parm1(arg,arg2|)|) ==> fun(|p|arm1(arg,arg2), parm2)\r\nfun(parm2, parm1(arg, arg2|)|) ==> fun(|p|arm1(arg, arg2), parm2)\r\nfun(arg1, ar|g|2, arg3) ==> fun(|a|rg2, arg1, arg3)\r\nfun(arg1, arg2, ar|g|3) ==> fun(arg1, |a|rg3, arg2)\r\narray[arg2, a|r|g1] ==> array[|a|rg1, arg2]\r\nfun(par|m|1[], parm2) ==> fun(|p|arm1[], parm2)\r\nfun(parm2, parm1[|]|) ==> fun(|p|arm1[], parm2)\r\nfun(array[], par|m|1) ==> fun(|p|arm1, array[])\r\nfun(b,|a|) ==> fun(|a|,b)\r\n\r\nA useful, however unexpected by the author, feature of this script is that\r\non pressing j to move cursor to the line below, the cursor is restored to \r\nthe column position before the swap. This allows for a streamlined\r\nswaping of parameters in the case like this:\r\n\r\nfun(arg2, arg1)\r\nfun(arg2, arg1)\r\nfun(arg2, arg1)\r\n\r\nYou would put cursor on arg2, and type gsjgsjgs","install_details":"To install put the script file into plugin directory.","5":"To install put the script file into plugin directory.","first_name":"Kamil","6":"Kamil","last_name":"Dworakowski","7":"Dworakowski","releases":[{"0":"2032","vim_version":"7.0","1":"7.0","script_version":"1.1.3","2":"1.1.3","version_comment":"now it is even more robust","3":"now it is even more robust","package":"swap_parameters.vim","4":"swap_parameters.vim","src_id":"8421","5":"8421","creation_date":"1204905667","6":"1204905667"},{"0":"2032","vim_version":"7.0","1":"7.0","script_version":"1.1.2","2":"1.1.2","version_comment":"A yet another defect fixes release.","3":"A yet another defect fixes release.","package":"swap_parameters.vim","4":"swap_parameters.vim","src_id":"8243","5":"8243","creation_date":"1202392455","6":"1202392455"},{"0":"2032","vim_version":"7.0","1":"7.0","script_version":"1.1.1","2":"1.1.1","version_comment":"Now also swap imports: \r\nfrom os import |p|open, path --> from os import path, pope|n|","3":"Now also swap imports: \r\nfrom os import |p|open, path --> from os import path, pope|n|","package":"swap_parameters.vim","4":"swap_parameters.vim","src_id":"8198","5":"8198","creation_date":"1201620467","6":"1201620467"},{"0":"2032","vim_version":"7.0","1":"7.0","script_version":"1.1","2":"1.1","version_comment":"Now the script will also cope with coma separated list that is not enclosed in brackets, which is common in Python code.\r\n\r\nfor |a|, b in some_dict.items()  -->    for b, |a| in some_dict.items()\r\n\r\nMoreover, I have made the code (with full suite of tests) available on code.google.com. Link is on my blog: http:\/\/blog.kamil.dworakowski.name\/2008\/01\/smarter-swap-parameters-for-vim.html.","3":"Now the script will also cope with coma separated list that is not enclosed in brackets, which is common in Python code.\r\n\r\nfor |a|, b in some_dict.items()  -->    for b, |a| in some_dict.items()\r\n\r\nMoreover, I have made the code (with full suite of tests) available on code.google.com. Link is on my blog: http:\/\/blog.kamil.dworakowski.name\/2008\/01\/smarter-swap-parameters-for-vim.html.","package":"swap_parameters.vim","4":"swap_parameters.vim","src_id":"8164","5":"8164","creation_date":"1200749093","6":"1200749093"},{"0":"2032","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"swap_parameters.vim","4":"swap_parameters.vim","src_id":"7728","5":"7728","creation_date":"1190991157","6":"1190991157"}]},"2031":{"script_id":"2031","0":"2031","script_name":"makeprgs","1":"makeprgs","script_type":"utility","2":"utility","summary":"Set makeprg and compiler type based on globbed files","3":"Set makeprg and compiler type based on globbed files","description":"If you work on several different projects, chances are you will come across Makefile, Ant or SCons based build systems. If you have <F5> mapped to :make with \":nmap <F5> :make<CR>\" then it would be nice if the correct build program were used. That is the purpose of this script. It also maps <F5> as mentioned.\r\n\r\nThe script checks if the file SConstruct or SConscript is in the current directory and if so sets the makeprg to scons, or scons -u for scripts.\r\n\r\nIf GNUmakefile, makefile or Makefile are found in the current directory, then the makeprg value is set to make.\r\n\r\nIf build.xml is found, then \"ant\" is the assumed compiler - i.e. \":compiler ant\" is called.\r\n\r\nA global variable makeprgs_make_types can be set to extend the functionality somewhat. Example included in the doc\/*.txt file.\r\n\r\nThe file detection is pretty crude - it runs a glob in the CWD and if the files are found sets the appropriate value. I hope you find it useful.\r\n\r\nTested on Vim 7.0 and 7.1, but should work on earlier releases (6.0 at least).","4":"If you work on several different projects, chances are you will come across Makefile, Ant or SCons based build systems. If you have <F5> mapped to :make with \":nmap <F5> :make<CR>\" then it would be nice if the correct build program were used. That is the purpose of this script. It also maps <F5> as mentioned.\r\n\r\nThe script checks if the file SConstruct or SConscript is in the current directory and if so sets the makeprg to scons, or scons -u for scripts.\r\n\r\nIf GNUmakefile, makefile or Makefile are found in the current directory, then the makeprg value is set to make.\r\n\r\nIf build.xml is found, then \"ant\" is the assumed compiler - i.e. \":compiler ant\" is called.\r\n\r\nA global variable makeprgs_make_types can be set to extend the functionality somewhat. Example included in the doc\/*.txt file.\r\n\r\nThe file detection is pretty crude - it runs a glob in the CWD and if the files are found sets the appropriate value. I hope you find it useful.\r\n\r\nTested on Vim 7.0 and 7.1, but should work on earlier releases (6.0 at least).","install_details":"The tar contains plugin\/makeprgs.vim and doc\/makeprgs.txt, so one should use these commands to install:\r\n\r\ncd $HOME\/.vim\r\ntar xzvf \/path\/to\/makeprgs.tar.gz\r\n\r\nThen in Vim, run :helptags ~\/.vim\/doc to generate the help. :help makeprgs will show the help file with extra details on customising.","5":"The tar contains plugin\/makeprgs.vim and doc\/makeprgs.txt, so one should use these commands to install:\r\n\r\ncd $HOME\/.vim\r\ntar xzvf \/path\/to\/makeprgs.tar.gz\r\n\r\nThen in Vim, run :helptags ~\/.vim\/doc to generate the help. :help makeprgs will show the help file with extra details on customising.","first_name":"Richard","6":"Richard","last_name":"Quirk","7":"Quirk","releases":[{"0":"2031","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"makeprgs-20070928.tar.gz","4":"makeprgs-20070928.tar.gz","src_id":"7727","5":"7727","creation_date":"1190989871","6":"1190989871"}]},"2030":{"script_id":"2030","0":"2030","script_name":"vimblog.vim","1":"vimblog.vim","script_type":"utility","2":"utility","summary":"blogging from vim ruby script","3":"blogging from vim ruby script","description":"For Vi, Vim, MacVim or GVim users, there is a simple way to manage your blog posts. Under Vim environment, you can create new blog posts, edit, list all categories, list older posts, delete posts, turn Published into Draft posts, and vice-versa.\r\nIt is out-of-the-box working for Wordpress, but very easilly, you can make it manage Blogger, MovableType, TextPattern, etc, platforms. Its the beauty of Open Source software. Study the code, change it, and use it. \r\n\r\nHomepage: https:\/\/github.com\/pedromg\/vimblog.vim\r\nScreenshots on Flickr: http:\/\/www.flickr.com\/search\/?w=all&q=vimblog&m=tags\r\n","4":"For Vi, Vim, MacVim or GVim users, there is a simple way to manage your blog posts. Under Vim environment, you can create new blog posts, edit, list all categories, list older posts, delete posts, turn Published into Draft posts, and vice-versa.\r\nIt is out-of-the-box working for Wordpress, but very easilly, you can make it manage Blogger, MovableType, TextPattern, etc, platforms. Its the beauty of Open Source software. Study the code, change it, and use it. \r\n\r\nHomepage: https:\/\/github.com\/pedromg\/vimblog.vim\r\nScreenshots on Flickr: http:\/\/www.flickr.com\/search\/?w=all&q=vimblog&m=tags\r\n","install_details":"Requirements:\r\n\"   - you'll need VIM compiled with Ruby scripting support\r\n\"     - example: for Debian\/Ubuntu: sudo apt-get install vim-ruby\r\n\"   - please, copy this file to one of your VIM dir\r\n\"     - example: to your .vim home folder: $HOME\/.vim\/vimblog.vim\r\n\"   - please, add this code to your .vimrc file:\r\n\"\r\n\"       if !exists('*Wordpress_vim')\r\n\"         runtime vimblog.vim\r\n\"       endif\r\n\"\r\n\"   - change your blog login\/password info on the get_personal_data\r\n\"     function bellow. \r\n\"   - make sure you have xmlrpc.php file in your \/ blog dir. If not, \r\n\"     change the @xml variable to find it.\r\n\"   - testing: open vim, and do \r\n\"       :Blog rp \r\n\"     to get your recent 10 posts.\r\n\r\nUPDATE: if you have several Vim's, and not all of them compiled with Ruby interpreter support, you will see a message when you open \"not +ruby\" Vim's. To disable that message, change the script, removing the s:ErrMsg( \"Error: Required vim compiled with +ruby\" ) line, or commenting it with \"\r\n","5":"Requirements:\r\n\"   - you'll need VIM compiled with Ruby scripting support\r\n\"     - example: for Debian\/Ubuntu: sudo apt-get install vim-ruby\r\n\"   - please, copy this file to one of your VIM dir\r\n\"     - example: to your .vim home folder: $HOME\/.vim\/vimblog.vim\r\n\"   - please, add this code to your .vimrc file:\r\n\"\r\n\"       if !exists('*Wordpress_vim')\r\n\"         runtime vimblog.vim\r\n\"       endif\r\n\"\r\n\"   - change your blog login\/password info on the get_personal_data\r\n\"     function bellow. \r\n\"   - make sure you have xmlrpc.php file in your \/ blog dir. If not, \r\n\"     change the @xml variable to find it.\r\n\"   - testing: open vim, and do \r\n\"       :Blog rp \r\n\"     to get your recent 10 posts.\r\n\r\nUPDATE: if you have several Vim's, and not all of them compiled with Ruby interpreter support, you will see a message when you open \"not +ruby\" Vim's. To disable that message, change the script, removing the s:ErrMsg( \"Error: Required vim compiled with +ruby\" ) line, or commenting it with \"\r\n","first_name":"pedro","6":"pedro","last_name":"mg","7":"mg","releases":[{"0":"2030","vim_version":"7.0","1":"7.0","script_version":"1.1","2":"1.1","version_comment":"# change on the way Vim delivers a message upon non compile with ruby Vim","3":"# change on the way Vim delivers a message upon non compile with ruby Vim","package":"vimblog.vim","4":"vimblog.vim","src_id":"8543","5":"8543","creation_date":"1207839060","6":"1207839060"},{"0":"2030","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"vimblog.vim","4":"vimblog.vim","src_id":"7720","5":"7720","creation_date":"1190850187","6":"1190850187"}]},"2029":{"script_id":"2029","0":"2029","script_name":"4NT Bundle","1":"4NT Bundle","script_type":"ftplugin","2":"ftplugin","summary":"btm (Batch to Memory - 4NT, TakeCommand Script) filetype bundle","3":"btm (Batch to Memory - 4NT, TakeCommand Script) filetype bundle","description":"Updates both the file type and syntax plug-in for btm (Batch to Memory - 4NT, TakeCommand Script) file type Bundle. Includes simple user and omni completion.\r\n\r\n| Source      || https:\/\/github.com\/krischik\/vim-btm\r\n| Wiki        || https:\/\/github.com\/krischik\/vim-btm\/wiki\r\n| Releases    || https:\/\/github.com\/krischik\/vim-btm\/releases \r\n| Issues      || https:\/\/github.com\/krischik\/vim-btm\/issues \r\n| Discussions || https:\/\/github.com\/krischik\/vim-btm\/discussions \r\n\r\n","4":"Updates both the file type and syntax plug-in for btm (Batch to Memory - 4NT, TakeCommand Script) file type Bundle. Includes simple user and omni completion.\r\n\r\n| Source      || https:\/\/github.com\/krischik\/vim-btm\r\n| Wiki        || https:\/\/github.com\/krischik\/vim-btm\/wiki\r\n| Releases    || https:\/\/github.com\/krischik\/vim-btm\/releases \r\n| Issues      || https:\/\/github.com\/krischik\/vim-btm\/issues \r\n| Discussions || https:\/\/github.com\/krischik\/vim-btm\/discussions \r\n\r\n","install_details":"Install from https:\/\/github.com\/krischik\/vim-btm using dein (https:\/\/github.com\/Shougo\/dein.vim) or similar:\r\n\r\ncall dein#begin('$HOME\/vimfiles\/bundles')\r\ncall dein#add('krischik\/vim-btm')\r\ncall dein#end()\r\ncall dein#install()\r\n","5":"Install from https:\/\/github.com\/krischik\/vim-btm using dein (https:\/\/github.com\/Shougo\/dein.vim) or similar:\r\n\r\ncall dein#begin('$HOME\/vimfiles\/bundles')\r\ncall dein#add('krischik\/vim-btm')\r\ncall dein#end()\r\ncall dein#install()\r\n","first_name":"Martin","6":"Martin","last_name":"Krischik","7":"Krischik","releases":[{"0":"2029","vim_version":"7.0","1":"7.0","script_version":"2.0","2":"2.0","version_comment":"See https:\/\/github.com\/krischik\/4NT-Bundle\/releases\/tag\/v_2.0","3":"See https:\/\/github.com\/krischik\/4NT-Bundle\/releases\/tag\/v_2.0","package":"4NT-Bundle-v_2.0.zip","4":"4NT-Bundle-v_2.0.zip","src_id":"28179","5":"28179","creation_date":"1663002854","6":"1663002854"},{"0":"2029","vim_version":"7.0","1":"7.0","script_version":"1.1","2":"1.1","version_comment":"Fixes and new features:\r\n\r\n1) Bill McCarthy contributed matchit settings.\r\n2) some loop-keywords where missing.\r\n3) additional minor fixes","3":"Fixes and new features:\r\n\r\n1) Bill McCarthy contributed matchit settings.\r\n2) some loop-keywords where missing.\r\n3) additional minor fixes","package":"btm-1.1.vba","4":"btm-1.1.vba","src_id":"7721","5":"7721","creation_date":"1190852766","6":"1190852766"},{"0":"2029","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"btm-1.0.vba","4":"btm-1.0.vba","src_id":"7718","5":"7718","creation_date":"1190777602","6":"1190777602"}]},"2028":{"script_id":"2028","0":"2028","script_name":"MarkLines","1":"MarkLines","script_type":"utility","2":"utility","summary":"Toggle highlighting on important lines","3":"Toggle highlighting on important lines","description":"The MarkLines plugin allows one to visually mark any number of lines, in any\r\nnumber of buffers, with any chosen highlight.  In a sufficiently new version\r\nof VIM, 7.1.040 or greater, you can use more than one highlight color per\r\nwindow simultaneously.\r\n\r\nTHIS PLUGIN REQUIRES VIM 7.0 OR GREATER.\r\n\r\nUseful for things like 'Mark every line that contains the word...'  or\r\n'Brighten every line containing a function declaration' without having it\r\ncleared every time you search for something else.  :)\r\n\r\n(By the way, you could do the first example with :%g\/foo\/MarkLinesOn)\r\n\r\n:MarkLinesOn         turns on highlighting for the current line or range\r\n:MarkLinesOff         turns off highlighting for the current line or range\r\n:MarkLinesToggle  toggles highlighting for the current line or range\r\n\r\nEach can be followed by an optional highlight group name as an argument;\r\nif so they turn on highlighting to that color (On, Toggle) or only clear lines of\r\nthat color (Off).\r\n\r\nA few maps are provided as well.\r\n<leader>mc   Clear:  Call MarkLinesOff for the current line or selection.\r\n<leader>ms   Select: Call MarkLinesOn for the current line or selection.\r\n<leader>mt   Toggle: Call MarkLinesToggle for the current line or selection.\r\n<leader>me   Error:  Like \\mt but using the \"ErrorMsg\" group, rather than the\r\n                     default highlight group.\r\n\r\nFor more details please see the in-vim help.  I spent a long time writing it,\r\nsomeone should read it.  ^_^\r\n\r\nAny questions, please feel free to email me.\r\n","4":"The MarkLines plugin allows one to visually mark any number of lines, in any\r\nnumber of buffers, with any chosen highlight.  In a sufficiently new version\r\nof VIM, 7.1.040 or greater, you can use more than one highlight color per\r\nwindow simultaneously.\r\n\r\nTHIS PLUGIN REQUIRES VIM 7.0 OR GREATER.\r\n\r\nUseful for things like 'Mark every line that contains the word...'  or\r\n'Brighten every line containing a function declaration' without having it\r\ncleared every time you search for something else.  :)\r\n\r\n(By the way, you could do the first example with :%g\/foo\/MarkLinesOn)\r\n\r\n:MarkLinesOn         turns on highlighting for the current line or range\r\n:MarkLinesOff         turns off highlighting for the current line or range\r\n:MarkLinesToggle  toggles highlighting for the current line or range\r\n\r\nEach can be followed by an optional highlight group name as an argument;\r\nif so they turn on highlighting to that color (On, Toggle) or only clear lines of\r\nthat color (Off).\r\n\r\nA few maps are provided as well.\r\n<leader>mc   Clear:  Call MarkLinesOff for the current line or selection.\r\n<leader>ms   Select: Call MarkLinesOn for the current line or selection.\r\n<leader>mt   Toggle: Call MarkLinesToggle for the current line or selection.\r\n<leader>me   Error:  Like \\mt but using the \"ErrorMsg\" group, rather than the\r\n                     default highlight group.\r\n\r\nFor more details please see the in-vim help.  I spent a long time writing it,\r\nsomeone should read it.  ^_^\r\n\r\nAny questions, please feel free to email me.\r\n","install_details":"To install, download the zipfile and unzip it to ~\/.vim, or ~\/vimfiles in windows, then run ':helptags ~\/.vim\/doc'","5":"To install, download the zipfile and unzip it to ~\/.vim, or ~\/vimfiles in windows, then run ':helptags ~\/.vim\/doc'","first_name":"Matt","6":"Matt","last_name":"Wozniski","7":"Wozniski","releases":[{"0":"2028","vim_version":"7.0","1":"7.0","script_version":"1.1","2":"1.1","version_comment":"Fix up a few assorted bugs.","3":"Fix up a few assorted bugs.","package":"MarkLines.zip","4":"MarkLines.zip","src_id":"9647","5":"9647","creation_date":"1228985325","6":"1228985325"},{"0":"2028","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"I forgot that I hate VimBalls.  Just unzip in your ~\/.vim directory , or whatever the windows equivalent is, and then do ':helptags ~\/.vim\/doc' from within vim","3":"I forgot that I hate VimBalls.  Just unzip in your ~\/.vim directory , or whatever the windows equivalent is, and then do ':helptags ~\/.vim\/doc' from within vim","package":"MarkLines.zip","4":"MarkLines.zip","src_id":"7715","5":"7715","creation_date":"1190725031","6":"1190725031"},{"0":"2028","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"MarkLines.vba","4":"MarkLines.vba","src_id":"7713","5":"7713","creation_date":"1190720230","6":"1190720230"}]},"2027":{"script_id":"2027","0":"2027","script_name":"taskpaper.vim","1":"taskpaper.vim","script_type":"ftplugin","2":"ftplugin","summary":"TaskPaper to-do list format support","3":"TaskPaper to-do list format support","description":"The latest version is available from https:\/\/github.com\/davidoc\/taskpaper.vim\r\n\r\nFrom the TaskPaper website (http:\/\/hogbaysoftware.com\/projects\/taskpaper):\r\n\r\n  \"TaskPaper is a simple to-do list application that helps you stay\r\norganized. Unlike competing applications, TaskPaper is based on plain text\r\nfiles which offer you paper-like simplicity and ease of use.\" \r\n\r\nTaskPaper is a to-do list application for Mac OS X based on the \"Getting\r\nThings Done\" approach of David Allen (http:\/\/www.davidco.com\/). It supports\r\nthe GTD notions of projects, tasks and contexts.\r\n\r\nThis package contains a syntax file and a file-type plugin for the simple\r\nformat used by the TaskPaper application. It is intended for Mac users who\r\nwant to edit their TaskPaper lists in Vim from time to time (for example, in\r\na SSH session, or on a non-Mac system) and for anyone who is looking for a\r\nsimple to-do list format.\r\n","4":"The latest version is available from https:\/\/github.com\/davidoc\/taskpaper.vim\r\n\r\nFrom the TaskPaper website (http:\/\/hogbaysoftware.com\/projects\/taskpaper):\r\n\r\n  \"TaskPaper is a simple to-do list application that helps you stay\r\norganized. Unlike competing applications, TaskPaper is based on plain text\r\nfiles which offer you paper-like simplicity and ease of use.\" \r\n\r\nTaskPaper is a to-do list application for Mac OS X based on the \"Getting\r\nThings Done\" approach of David Allen (http:\/\/www.davidco.com\/). It supports\r\nthe GTD notions of projects, tasks and contexts.\r\n\r\nThis package contains a syntax file and a file-type plugin for the simple\r\nformat used by the TaskPaper application. It is intended for Mac users who\r\nwant to edit their TaskPaper lists in Vim from time to time (for example, in\r\na SSH session, or on a non-Mac system) and for anyone who is looking for a\r\nsimple to-do list format.\r\n","install_details":"Unpack the package into your .vim directory.\r\nIt contains the following files:\r\n    autoload\/taskpaper.vim\r\n    doc\/example.taskpaper\r\n    doc\/taskpaper.txt\r\n    doc\/taskpaper_licence.txt\r\n    ftdetect\/taskpaper.vim\r\n    ftplugin\/taskpaper.vim\r\n    syntax\/taskpaper.vim","5":"Unpack the package into your .vim directory.\r\nIt contains the following files:\r\n    autoload\/taskpaper.vim\r\n    doc\/example.taskpaper\r\n    doc\/taskpaper.txt\r\n    doc\/taskpaper_licence.txt\r\n    ftdetect\/taskpaper.vim\r\n    ftplugin\/taskpaper.vim\r\n    syntax\/taskpaper.vim","first_name":"David","6":"David","last_name":"O'Callaghan","7":"O'Callaghan","releases":[{"0":"2027","vim_version":"6.0","1":"6.0","script_version":"0.7","2":"0.7","version_comment":"Major update with many improvements and additional features.","3":"Major update with many improvements and additional features.","package":"taskpaper-0.7.tar.gz","4":"taskpaper-0.7.tar.gz","src_id":"17570","5":"17570","creation_date":"1331074227","6":"1331074227"},{"0":"2027","vim_version":"6.0","1":"6.0","script_version":"0.6","2":"0.6","version_comment":"Updates from contributors:\r\n  - ToggleCancelled\r\n  - Customise the date format\r\n  - Use tabs not spaces (noexpandtab)\r\n  - Use <Leader> rather than <LocalLeader>\r\n  - Start new task after <CR>","3":"Updates from contributors:\r\n  - ToggleCancelled\r\n  - Customise the date format\r\n  - Use tabs not spaces (noexpandtab)\r\n  - Use <Leader> rather than <LocalLeader>\r\n  - Start new task after <CR>","package":"taskpaper-0.6.tar.gz","4":"taskpaper-0.6.tar.gz","src_id":"15014","5":"15014","creation_date":"1297772315","6":"1297772315"},{"0":"2027","vim_version":"6.0","1":"6.0","script_version":"0.5","2":"0.5","version_comment":"Now on http:\/\/github.com\/davidoc\/taskpaper.vim\r\n- Display non-tasks as comments\r\n- Patch to toggle done state ","3":"Now on http:\/\/github.com\/davidoc\/taskpaper.vim\r\n- Display non-tasks as comments\r\n- Patch to toggle done state ","package":"taskpaper-0.5.tar.gz","4":"taskpaper-0.5.tar.gz","src_id":"13646","5":"13646","creation_date":"1282515560","6":"1282515560"},{"0":"2027","vim_version":"6.0","1":"6.0","script_version":"0.4","2":"0.4","version_comment":"Use styles from colour scheme for better control of appearance.","3":"Use styles from colour scheme for better control of appearance.","package":"taskpaper-0.4.tar.gz","4":"taskpaper-0.4.tar.gz","src_id":"8712","5":"8712","creation_date":"1211512911","6":"1211512911"},{"0":"2027","vim_version":"6.0","1":"6.0","script_version":"0.3","2":"0.3","version_comment":"New release including changes suggested and contributed by users.","3":"New release including changes suggested and contributed by users.","package":"taskpaper.tar.gz","4":"taskpaper.tar.gz","src_id":"8384","5":"8384","creation_date":"1204520541","6":"1204520541"},{"0":"2027","vim_version":"6.0","1":"6.0","script_version":"0.2","2":"0.2","version_comment":"New release including patches contributed by users..","3":"New release including patches contributed by users..","package":"taskpaper.tar.gz","4":"taskpaper.tar.gz","src_id":"8036","5":"8036","creation_date":"1197280605","6":"1197280605"},{"0":"2027","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"gzipped the tar file this time!","3":"gzipped the tar file this time!","package":"taskpaper.tar.gz","4":"taskpaper.tar.gz","src_id":"7711","5":"7711","creation_date":"1190699498","6":"1190699498"}]},"2026":{"script_id":"2026","0":"2026","script_name":"motion.vim","1":"motion.vim","script_type":"utility","2":"utility","summary":"motion text in command mode","3":"motion text in command mode","description":"motion text in command mode.\r\nuse:\r\n**line**\r\nCTRL+up      - move line\r\nCTRL+down - move line\r\n\r\n**char**\r\nCTRL+right   - move char\r\nCTRL+left     - move char\r\n\r\n**screen**\r\nSHIFT+up      - move screen\r\nSHIFT+down - move screen\r\nSHIFT+right   - move screen\r\nSHIFT+left     - move screen","4":"motion text in command mode.\r\nuse:\r\n**line**\r\nCTRL+up      - move line\r\nCTRL+down - move line\r\n\r\n**char**\r\nCTRL+right   - move char\r\nCTRL+left     - move char\r\n\r\n**screen**\r\nSHIFT+up      - move screen\r\nSHIFT+down - move screen\r\nSHIFT+right   - move screen\r\nSHIFT+left     - move screen","install_details":"put it into vim plugin folder (\/usr\/share\/vim\/vim71\/plugin) or in your ~\/.vim\/plugin\/ folder","5":"put it into vim plugin folder (\/usr\/share\/vim\/vim71\/plugin) or in your ~\/.vim\/plugin\/ folder","first_name":"ivan","6":"ivan","last_name":"lopes","7":"lopes","releases":[{"0":"2026","vim_version":"7.0","1":"7.0","script_version":"1.1","2":"1.1","version_comment":"bug fixes","3":"bug fixes","package":"motion.vim","4":"motion.vim","src_id":"7756","5":"7756","creation_date":"1191608225","6":"1191608225"},{"0":"2026","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"motion.vim","4":"motion.vim","src_id":"7704","5":"7704","creation_date":"1190577153","6":"1190577153"}]},"2025":{"script_id":"2025","0":"2025","script_name":"camlanot.vim","1":"camlanot.vim","script_type":"ftplugin","2":"ftplugin","summary":"Ocaml support for type annotation files, included support for ocamlbuild","3":"Ocaml support for type annotation files, included support for ocamlbuild","description":"**** This plugin is now part of the official ocaml ftplugin (i.e. the one already distributed with Vim) ****\r\n\r\nOcaml support for annot file is already implemented in the official Ocaml ftplugin and in ocaml.annot.pl (script_id=1197).\r\n\r\nBut this script adds the following:\r\n\r\n   - no need for python support (neither perl or anything else : only vim code inside)\r\n     + plus: more portable\r\n     + minus: no more lazy parsing, it looks very fast however\r\n     \r\n   - ocamlbuild support, ie.\r\n     + the plugin finds the _build directory and looks for the \r\n       corresponding file inside;\r\n     + if the user decides to change the name of the _build directory thanks\r\n       to the '-build-dir' option of ocamlbuild, the plugin will manage to find it out;\r\n     + if ocamlbuild is not used, the usual behaviour holds; ie. the .annot\r\n       file should be in the same directory as the source file;\r\n     + for vim plugin programmers:\r\n       the variable 'b:_build_dir' contains the inferred path to the build \r\n       directory, even if this one is not named '_build'.\r\n\r\n Bonus:\r\n   - latin1 accents are handled\r\n   - lists are handled, even on multiple lines, you don't need the visual mode\r\n     (the cursor must be on the first bracket)\r\n   - parenthesized expressions, arrays, and structures (ie. '(...)', '[|...|]',\r\n     and '{...}') are handled the same way\r\n\r\nUsage:\r\n   - press <LocalLeader>t to display the type of expression under cursor\r\n   - don't forget to compile with -dtypes option (or -cflags -dtypes if you're using ocamlbuild)\r\n\r\n\r\n","4":"**** This plugin is now part of the official ocaml ftplugin (i.e. the one already distributed with Vim) ****\r\n\r\nOcaml support for annot file is already implemented in the official Ocaml ftplugin and in ocaml.annot.pl (script_id=1197).\r\n\r\nBut this script adds the following:\r\n\r\n   - no need for python support (neither perl or anything else : only vim code inside)\r\n     + plus: more portable\r\n     + minus: no more lazy parsing, it looks very fast however\r\n     \r\n   - ocamlbuild support, ie.\r\n     + the plugin finds the _build directory and looks for the \r\n       corresponding file inside;\r\n     + if the user decides to change the name of the _build directory thanks\r\n       to the '-build-dir' option of ocamlbuild, the plugin will manage to find it out;\r\n     + if ocamlbuild is not used, the usual behaviour holds; ie. the .annot\r\n       file should be in the same directory as the source file;\r\n     + for vim plugin programmers:\r\n       the variable 'b:_build_dir' contains the inferred path to the build \r\n       directory, even if this one is not named '_build'.\r\n\r\n Bonus:\r\n   - latin1 accents are handled\r\n   - lists are handled, even on multiple lines, you don't need the visual mode\r\n     (the cursor must be on the first bracket)\r\n   - parenthesized expressions, arrays, and structures (ie. '(...)', '[|...|]',\r\n     and '{...}') are handled the same way\r\n\r\nUsage:\r\n   - press <LocalLeader>t to display the type of expression under cursor\r\n   - don't forget to compile with -dtypes option (or -cflags -dtypes if you're using ocamlbuild)\r\n\r\n\r\n","install_details":"We'll assume your personal vim directory is \"~\/.vim\/\".\r\n\r\n- Copy the plugin in \"~\/.vim\/after\/ftplugin\/\"\r\n- If it does not already exist, add a file \"~\/.vim\/after\/ftplugin\/ocaml.vim\".\r\n- At the end of this file, add the following line :\r\nsource camlanot.vim\r\n- It's done.\r\n\r\nVersion note: should work with Vim 6.0, but not tested.","5":"We'll assume your personal vim directory is \"~\/.vim\/\".\r\n\r\n- Copy the plugin in \"~\/.vim\/after\/ftplugin\/\"\r\n- If it does not already exist, add a file \"~\/.vim\/after\/ftplugin\/ocaml.vim\".\r\n- At the end of this file, add the following line :\r\nsource camlanot.vim\r\n- It's done.\r\n\r\nVersion note: should work with Vim 6.0, but not tested.","first_name":"Vincent","6":"Vincent","last_name":"Aravantinos","7":"Aravantinos","releases":[{"0":"2025","vim_version":"7.0","1":"7.0","script_version":"0.9","2":"0.9","version_comment":"Initial upload","3":"Initial upload","package":"camlanot.vim","4":"camlanot.vim","src_id":"7702","5":"7702","creation_date":"1190442150","6":"1190442150"}]},"2024":{"script_id":"2024","0":"2024","script_name":"brew.vim","1":"brew.vim","script_type":"syntax","2":"syntax","summary":"Syntax highlighting for a templating system in R","3":"Syntax highlighting for a templating system in R","description":"Brew is a templating system for R similar to PHP, Java\/Active server pages, Ruby's erb, or Python's psp.\r\n\r\nBased heavily on eruby.vim of the ruby-vim package by Tim Pope and others.\r\n\r\nhttp:\/\/github.com\/graywh\/vim-brew","4":"Brew is a templating system for R similar to PHP, Java\/Active server pages, Ruby's erb, or Python's psp.\r\n\r\nBased heavily on eruby.vim of the ruby-vim package by Tim Pope and others.\r\n\r\nhttp:\/\/github.com\/graywh\/vim-brew","install_details":"Drop into the 'syntax' directory of your vim config and put the appropriate filetype detection in filetype.vim or ftdetect\/brew.vim.\r\n\r\nautocmd BufNewFile,BufRead *.brew set filetype=brew","5":"Drop into the 'syntax' directory of your vim config and put the appropriate filetype detection in filetype.vim or ftdetect\/brew.vim.\r\n\r\nautocmd BufNewFile,BufRead *.brew set filetype=brew","first_name":"Will","6":"Will","last_name":"Gray","7":"Gray","releases":[{"0":"2024","vim_version":"6.0","1":"6.0","script_version":"1.2","2":"1.2","version_comment":"Remove 5.x compatibility. Fix regions ends.","3":"Remove 5.x compatibility. Fix regions ends.","package":"brew.vim","4":"brew.vim","src_id":"15112","5":"15112","creation_date":"1298582479","6":"1298582479"},{"0":"2024","vim_version":"6.0","1":"6.0","script_version":"1.1","2":"1.1","version_comment":"Add subtype detection from filetype=brew.html","3":"Add subtype detection from filetype=brew.html","package":"brew.vim","4":"brew.vim","src_id":"12649","5":"12649","creation_date":"1268849975","6":"1268849975"},{"0":"2024","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"brew.vim","4":"brew.vim","src_id":"7690","5":"7690","creation_date":"1190119309","6":"1190119309"}]},"2023":{"script_id":"2023","0":"2023","script_name":"erlang indent file","1":"erlang indent file","script_type":"indent","2":"indent","summary":"Erlang indent file","3":"Erlang indent file","description":"This is an indent file for Erlang.\r\n\r\n***THE NEWER VERSIONS OF THIS SCRIPT ARE ON GITHUB:***\r\n\r\nhttps:\/\/github.com\/vim-erlang\/vim-erlang-runtime\r\n","4":"This is an indent file for Erlang.\r\n\r\n***THE NEWER VERSIONS OF THIS SCRIPT ARE ON GITHUB:***\r\n\r\nhttps:\/\/github.com\/vim-erlang\/vim-erlang-runtime\r\n","install_details":"Put the script into your ~\/.vim\/indent directory.","5":"Put the script into your ~\/.vim\/indent directory.","first_name":"Csaba","6":"Csaba","last_name":"Hoch","7":"Hoch","releases":[{"0":"2023","vim_version":"7.0","1":"7.0","script_version":"1.2","2":"1.2","version_comment":"Using =~# operator instead of =~, so if the user has the 'ignorekeys' on, it will still work correctly. (Thanks to Edwin Fine!)","3":"Using =~# operator instead of =~, so if the user has the 'ignorekeys' on, it will still work correctly. (Thanks to Edwin Fine!)","package":"erlang.vim","4":"erlang.vim","src_id":"8442","5":"8442","creation_date":"1205347629","6":"1205347629"},{"0":"2023","vim_version":"7.0","1":"7.0","script_version":"1.1","2":"1.1","version_comment":"- only defines the indent functions once\r\n- more indentkeys\r\n- a full stop in a record won't considered as the end of a function","3":"- only defines the indent functions once\r\n- more indentkeys\r\n- a full stop in a record won't considered as the end of a function","package":"erlang.vim","4":"erlang.vim","src_id":"8011","5":"8011","creation_date":"1196488473","6":"1196488473"},{"0":"2023","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"erlang.vim","4":"erlang.vim","src_id":"7681","5":"7681","creation_date":"1189947062","6":"1189947062"}]},"2022":{"script_id":"2022","0":"2022","script_name":"Tailf","1":"Tailf","script_type":"utility","2":"utility","summary":"Tails a log file continuously, like using 'tail -f'","3":"Tails a log file continuously, like using 'tail -f'","description":"Discontinued script, please don't download.","4":"Discontinued script, please don't download.","install_details":"","5":"","first_name":"Basil","6":"Basil","last_name":"Shkara","7":"Shkara","releases":[{"0":"2022","vim_version":"7.0","1":"7.0","script_version":"1.0.2","2":"1.0.2","version_comment":"Fixed buffer reload problem","3":"Fixed buffer reload problem","package":"tailf.vim","4":"tailf.vim","src_id":"7687","5":"7687","creation_date":"1190042240","6":"1190042240"}]},"2021":{"script_id":"2021","0":"2021","script_name":"headerguard","1":"headerguard","script_type":"utility","2":"utility","summary":"Add header guards to C\/C++ header files","3":"Add header guards to C\/C++ header files","description":"******************************************************\r\nHeaderguard -  Add header guards to C\/C++ header files\r\n******************************************************\r\n\r\nIt is a common practice to insert header guards into C\/C++ header files to\r\nallow a header to be included multiple times.  A header guard for file\r\nHeaderName.h typically looks something like this::\r\n\r\n  #ifndef HEADERNAME_H\r\n  #define HEADERNAME_H\r\n\r\n    ...header content...\r\n\r\n  #endif \/* HEADERNAME_H *\/\r\n\r\nHeaderguard provides methods for inserting and updating header guards, and for\r\ntailoring the header guard style to fit local conventions.  It checks for a\r\npre-existing header guard, and if found, modifies the existing guard in-place.\r\n\r\nSee documentation in doc\/headerguard.txt for installation, customization, and\r\nusage instructions.\r\n\r\nDeveloped by Michael Henry (vim at drmikehenry.com).\r\n\r\nDistributed under Vim's license.\r\n\r\nGit repository:   https:\/\/github.com\/drmikehenry\/vim-headerguard\r\n","4":"******************************************************\r\nHeaderguard -  Add header guards to C\/C++ header files\r\n******************************************************\r\n\r\nIt is a common practice to insert header guards into C\/C++ header files to\r\nallow a header to be included multiple times.  A header guard for file\r\nHeaderName.h typically looks something like this::\r\n\r\n  #ifndef HEADERNAME_H\r\n  #define HEADERNAME_H\r\n\r\n    ...header content...\r\n\r\n  #endif \/* HEADERNAME_H *\/\r\n\r\nHeaderguard provides methods for inserting and updating header guards, and for\r\ntailoring the header guard style to fit local conventions.  It checks for a\r\npre-existing header guard, and if found, modifies the existing guard in-place.\r\n\r\nSee documentation in doc\/headerguard.txt for installation, customization, and\r\nusage instructions.\r\n\r\nDeveloped by Michael Henry (vim at drmikehenry.com).\r\n\r\nDistributed under Vim's license.\r\n\r\nGit repository:   https:\/\/github.com\/drmikehenry\/vim-headerguard\r\n","install_details":"","5":"","first_name":"Michael","6":"Michael","last_name":"Henry","7":"Henry","releases":[{"0":"2021","vim_version":"7.0","1":"7.0","script_version":"0.2.2","2":"0.2.2","version_comment":"Add g:headerguard_use_cpp_comments to use C++ comments in #endif (thanks to P\u00c3\u00a9ter Szabados).","3":"Add g:headerguard_use_cpp_comments to use C++ comments in #endif (thanks to P\u00c3\u00a9ter Szabados).","package":"headerguard-0.2.2.zip","4":"headerguard-0.2.2.zip","src_id":"23249","5":"23249","creation_date":"1430437832","6":"1430437832"},{"0":"2021","vim_version":"7.0","1":"7.0","script_version":"0.2.1","2":"0.2.1","version_comment":"Documentation reorganization.\r\n","3":"Documentation reorganization.\r\n","package":"headerguard-0.2.1.zip","4":"headerguard-0.2.1.zip","src_id":"20875","5":"20875","creation_date":"1380813840","6":"1380813840"},{"0":"2021","vim_version":"7.0","1":"7.0","script_version":"0.2.0","2":"0.2.0","version_comment":"- Convert to bundle-based installation.\r\n- Allow for buffer-local overrides of global guard definitions.\r\n","3":"- Convert to bundle-based installation.\r\n- Allow for buffer-local overrides of global guard definitions.\r\n","package":"headerguard-0.2.0.zip","4":"headerguard-0.2.0.zip","src_id":"20874","5":"20874","creation_date":"1380813433","6":"1380813433"},{"0":"2021","vim_version":"7.0","1":"7.0","script_version":"0.1.1","2":"0.1.1","version_comment":"Properly restore cpoptions.","3":"Properly restore cpoptions.","package":"headerguard-0.1.1.zip","4":"headerguard-0.1.1.zip","src_id":"20837","5":"20837","creation_date":"1380019137","6":"1380019137"},{"0":"2021","vim_version":"7.0","1":"7.0","script_version":"0.1.0","2":"0.1.0","version_comment":"Initial upload","3":"Initial upload","package":"headerguard-0.1.0.zip","4":"headerguard-0.1.0.zip","src_id":"7675","5":"7675","creation_date":"1189804116","6":"1189804116"}]},"2020":{"script_id":"2020","0":"2020","script_name":"Gettext PO file compiler","1":"Gettext PO file compiler","script_type":"utility","2":"utility","summary":"This is a compiler for gettext files (*.po)","3":"This is a compiler for gettext files (*.po)","description":"This compiler plugin compiles the gettext po files to mo files and checks the errors.","4":"This compiler plugin compiles the gettext po files to mo files and checks the errors.","install_details":"Put this into your compiler directory and set this in your vimrc:\r\n\r\naugroup PO\r\n        autocmd FileType po compiler po\r\naugroup END\r\n","5":"Put this into your compiler directory and set this in your vimrc:\r\n\r\naugroup PO\r\n        autocmd FileType po compiler po\r\naugroup END\r\n","first_name":"Istv\u00c3\u00a1n","6":"Istv\u00c3\u00a1n","last_name":"Karaszi","7":"Karaszi","releases":[{"0":"2020","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"po.vim","4":"po.vim","src_id":"7672","5":"7672","creation_date":"1189740859","6":"1189740859"}]},"2019":{"script_id":"2019","0":"2019","script_name":"3DGlasses.vim","1":"3DGlasses.vim","script_type":"color scheme","2":"color scheme","summary":"Dark blue scheme with parallax effect","3":"Dark blue scheme with parallax effect","description":"This was supposed to be a Tron color scheme, but I don't think it quite captured the essence of the Tron universe.\r\nThis scheme uses a dark blue background against which soft blue text is set.  Bright red highlights really stand out (that's due to the chromostereoscopic effect).\r\n\r\nSend feedback to g?? ArjBsnyFbCe@tzNnvZy.pbz - ABFCNZ\r\n ","4":"This was supposed to be a Tron color scheme, but I don't think it quite captured the essence of the Tron universe.\r\nThis scheme uses a dark blue background against which soft blue text is set.  Bright red highlights really stand out (that's due to the chromostereoscopic effect).\r\n\r\nSend feedback to g?? ArjBsnyFbCe@tzNnvZy.pbz - ABFCNZ\r\n ","install_details":"Put 3dglasses.vim inside your colors directory.\r\n:colo 3dglasses\r\nAlso check out vimscript #2004 for a handy way to organize your color schemes.","5":"Put 3dglasses.vim inside your colors directory.\r\n:colo 3dglasses\r\nAlso check out vimscript #2004 for a handy way to organize your color schemes.","first_name":"erik","6":"erik","last_name":"falor","7":"falor","releases":[{"0":"2019","vim_version":"7.0","1":"7.0","script_version":" 1.1.1","2":" 1.1.1","version_comment":"Changed MatchParens group so that matching <> in xml files show up better. \r\nBe sure to append <:> to your matchpairs option.","3":"Changed MatchParens group so that matching <> in xml files show up better. \r\nBe sure to append <:> to your matchpairs option.","package":"3dglasses.vim","4":"3dglasses.vim","src_id":"7724","5":"7724","creation_date":"1190898669","6":"1190898669"},{"0":"2019","vim_version":"7.0","1":"7.0","script_version":"1.1","2":"1.1","version_comment":"Added support for GetLatestVimScripts\r\n","3":"Added support for GetLatestVimScripts\r\n","package":"3dglasses.vim","4":"3dglasses.vim","src_id":"7699","5":"7699","creation_date":"1190278373","6":"1190278373"},{"0":"2019","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"bug fix","3":"bug fix","package":"3dglasses.vim","4":"3dglasses.vim","src_id":"7663","5":"7663","creation_date":"1189603023","6":"1189603023"}]},"2018":{"script_id":"2018","0":"2018","script_name":"ttags","1":"ttags","script_type":"utility","2":"utility","summary":"Tag list browser (List, filter, preview, jump to tags)","3":"Tag list browser (List, filter, preview, jump to tags)","description":":TTags [KIND] [TAGS_RX] [FILE_RX]\r\nIn order to match any kind\/rx, use *.\r\nE.g. TTags * * _foo.vim$\r\n\r\nFeatures:\r\n    - List tags\r\n    - Filter tags matching a pattern\r\n    - Jump\/Preview tags\r\n    - Insert tags (and a template for the argument list if supported by \r\n      tSkeleton (vimscript #1160), which has to be installed for this)\r\n\r\nYou can use :echo keys(ttags#Kinds())<cr> to find out which kinds are defined.\r\n","4":":TTags [KIND] [TAGS_RX] [FILE_RX]\r\nIn order to match any kind\/rx, use *.\r\nE.g. TTags * * _foo.vim$\r\n\r\nFeatures:\r\n    - List tags\r\n    - Filter tags matching a pattern\r\n    - Jump\/Preview tags\r\n    - Insert tags (and a template for the argument list if supported by \r\n      tSkeleton (vimscript #1160), which has to be installed for this)\r\n\r\nYou can use :echo keys(ttags#Kinds())<cr> to find out which kinds are defined.\r\n","install_details":"Edit the vba file and type: >\r\n\r\n    :so %\r\n\r\nSee :help vimball for details. If you have difficulties or use vim 7.0, please make\r\nsure, you have the current version of vimball (vimscript #1502)\r\ninstalled.\r\n\r\nThis script requires tlib (vimscript #1863) to be installed.\r\n\r\nSuggested key maps:\r\n\r\n    noremap <Leader>g. :TTags<cr>\r\n    noremap <Leader>g# :call ttags#List(0, \"*\", tlib#rx#Escape(expand(\"<cword>\")))<cr>\r\n    noremap <Leader>g* :call ttags#List(0, \"*\", tlib#rx#Escape(expand(\"<cword>\")) .\".*\")<cr>\r\n    noremap <Leader>g? :call ttags#List(1, \"*\", tlib#rx#Escape(expand(\"<cword>\")))<cr>\r\n    for c in split('abcdefghijklmnopqrstuvwxyzABCDEFGHIJKLMNOPQRSTUVWXYZ', '\\zs')\r\n        exec 'noremap <Leader>g'. c .' :TTags '. c .'<cr>'\r\n    endfor\r\n\r\n\r\nAlso available via git\r\nhttp:\/\/github.com\/tomtom\/ttags_vim","5":"Edit the vba file and type: >\r\n\r\n    :so %\r\n\r\nSee :help vimball for details. If you have difficulties or use vim 7.0, please make\r\nsure, you have the current version of vimball (vimscript #1502)\r\ninstalled.\r\n\r\nThis script requires tlib (vimscript #1863) to be installed.\r\n\r\nSuggested key maps:\r\n\r\n    noremap <Leader>g. :TTags<cr>\r\n    noremap <Leader>g# :call ttags#List(0, \"*\", tlib#rx#Escape(expand(\"<cword>\")))<cr>\r\n    noremap <Leader>g* :call ttags#List(0, \"*\", tlib#rx#Escape(expand(\"<cword>\")) .\".*\")<cr>\r\n    noremap <Leader>g? :call ttags#List(1, \"*\", tlib#rx#Escape(expand(\"<cword>\")))<cr>\r\n    for c in split('abcdefghijklmnopqrstuvwxyzABCDEFGHIJKLMNOPQRSTUVWXYZ', '\\zs')\r\n        exec 'noremap <Leader>g'. c .' :TTags '. c .'<cr>'\r\n    endfor\r\n\r\n\r\nAlso available via git\r\nhttp:\/\/github.com\/tomtom\/ttags_vim","first_name":"Tom","6":"Tom","last_name":"Link","7":"Link","releases":[{"0":"2018","vim_version":"7.0","1":"7.0","script_version":"0.6","2":"0.6","version_comment":"- Use pathshorten()\r\n- Require tlib >= 0.21\r\n- FIX: Use ListW()\r\n- Make sure tlib is loaded even if it is installed in a different rtp-directory.\r\n- temporarily set nomagic when running the tag command\r\n- Show tags in the current file: TTags * * .\r\n","3":"- Use pathshorten()\r\n- Require tlib >= 0.21\r\n- FIX: Use ListW()\r\n- Make sure tlib is loaded even if it is installed in a different rtp-directory.\r\n- temporarily set nomagic when running the tag command\r\n- Show tags in the current file: TTags * * .\r\n","package":"ttags.vba.gz","4":"ttags.vba.gz","src_id":"11511","5":"11511","creation_date":"1255243002","6":"1255243002"},{"0":"2018","vim_version":"7.0","1":"7.0","script_version":"0.5","2":"0.5","version_comment":"- More compact view of tags (via |g:tlib_tag_substitute|)\r\n- When previewing tags, restore the original position when closing the tags list\r\n- g:ttags_match_front, g:ttags_match_end\r\n- Require tlib >= 0.20\r\n","3":"- More compact view of tags (via |g:tlib_tag_substitute|)\r\n- When previewing tags, restore the original position when closing the tags list\r\n- g:ttags_match_front, g:ttags_match_end\r\n- Require tlib >= 0.20\r\n","package":"ttags.vba.gz","4":"ttags.vba.gz","src_id":"7939","5":"7939","creation_date":"1194863132","6":"1194863132"},{"0":"2018","vim_version":"7.0","1":"7.0","script_version":"0.4","2":"0.4","version_comment":"- New: ttags#Select() that matches any field\r\n- New: TTagselect command that takes a key list as argument to match any \r\nfield.\r\n- New: [wbg]:ttags_constraints configuration variable (a dictionary with \r\nregexps).\r\n- If the commands TTags and TTagselect are called with [!], \r\ng:tlib_tags_extra is used to temporarily scan additional tag files.\r\n- If a variable [bg]:ttags_rewrite is defined, it is used as function \r\nname to rewrite tag filesname (eg to prevent name incompatibilities \r\nbetween cygwin ctag & windows vim).\r\n- \"[wbg]:ttags_tags_rx\" was renamed to \"[wbg]:ttags_name_rx\"\r\n- \"[wbg]:ttags_file_rx\" was renamed to \"[wbg]:ttags_filename_rx\"\r\n- g:ttags_display: Alternatively use \"locations\" or \"quickfix\" lists to \r\ndisplay the tags (default: \"tlib\").\r\n- Require tlib 0.19\r\n- Previously, all tags were retrieved and filtered only later on. The \r\nidea was to save time by caching the tags information. Now the initial \r\nfiltering by name is done by |taglist()| right away, which seems faster.\r\n","3":"- New: ttags#Select() that matches any field\r\n- New: TTagselect command that takes a key list as argument to match any \r\nfield.\r\n- New: [wbg]:ttags_constraints configuration variable (a dictionary with \r\nregexps).\r\n- If the commands TTags and TTagselect are called with [!], \r\ng:tlib_tags_extra is used to temporarily scan additional tag files.\r\n- If a variable [bg]:ttags_rewrite is defined, it is used as function \r\nname to rewrite tag filesname (eg to prevent name incompatibilities \r\nbetween cygwin ctag & windows vim).\r\n- \"[wbg]:ttags_tags_rx\" was renamed to \"[wbg]:ttags_name_rx\"\r\n- \"[wbg]:ttags_file_rx\" was renamed to \"[wbg]:ttags_filename_rx\"\r\n- g:ttags_display: Alternatively use \"locations\" or \"quickfix\" lists to \r\ndisplay the tags (default: \"tlib\").\r\n- Require tlib 0.19\r\n- Previously, all tags were retrieved and filtered only later on. The \r\nidea was to save time by caching the tags information. Now the initial \r\nfiltering by name is done by |taglist()| right away, which seems faster.\r\n","package":"ttags.vba.gz","4":"ttags.vba.gz","src_id":"7884","5":"7884","creation_date":"1194302550","6":"1194302550"},{"0":"2018","vim_version":"7.0","1":"7.0","script_version":"0.3","2":"0.3","version_comment":"- Configuration via [wbg]:ttags_kinds, [wbg]:ttags_tags_rx, \r\n[wbg]:ttags_file_rx variables\r\n- The list includes the kind identifier and the entries are highlighted \r\n(see g:ttags_highlighting)\r\n- If tSkeleton (vimscript #1160) is installed and if g:tskelTypes \r\ncontains \"tags\", <c-t> will insert the tag in the buffer including (if \r\nsupported by tSkeleton for the current filetype) a template for the \r\nargument list.\r\n- g:ttags_world can be a normal dictionary (use tlib#input#ListD instead\r\nof #ListW)\r\n- Require tlib 0.14\r\n","3":"- Configuration via [wbg]:ttags_kinds, [wbg]:ttags_tags_rx, \r\n[wbg]:ttags_file_rx variables\r\n- The list includes the kind identifier and the entries are highlighted \r\n(see g:ttags_highlighting)\r\n- If tSkeleton (vimscript #1160) is installed and if g:tskelTypes \r\ncontains \"tags\", <c-t> will insert the tag in the buffer including (if \r\nsupported by tSkeleton for the current filetype) a template for the \r\nargument list.\r\n- g:ttags_world can be a normal dictionary (use tlib#input#ListD instead\r\nof #ListW)\r\n- Require tlib 0.14\r\n","package":"ttags.vba.gz","4":"ttags.vba.gz","src_id":"7730","5":"7730","creation_date":"1191034916","6":"1191034916"},{"0":"2018","vim_version":"7.0","1":"7.0","script_version":"0.2","2":"0.2","version_comment":"- The kind argument was introduced (i.e. the argument list has changed)\r\n- * was defined as \"match any\".\r\n","3":"- The kind argument was introduced (i.e. the argument list has changed)\r\n- * was defined as \"match any\".\r\n","package":"ttags.vba.gz","4":"ttags.vba.gz","src_id":"7655","5":"7655","creation_date":"1189507424","6":"1189507424"},{"0":"2018","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"ttags.vba.gz","4":"ttags.vba.gz","src_id":"7654","5":"7654","creation_date":"1189505868","6":"1189505868"}]},"2017":{"script_id":"2017","0":"2017","script_name":"tregisters","1":"tregisters","script_type":"utility","2":"utility","summary":"List, edit, and run\/execute registers\/clipboards","3":"List, edit, and run\/execute registers\/clipboards","description":":TRegister\r\n    List the registers as returned by |:reg|.\r\n\r\nKeys~\r\n    <c-e> ... Edit register\/clipboard\r\n    <c-q> ... Execute register (see |@|)\r\n    <cr>  ... Put selected register(s) (see |:put|)\r\n    <esc> ... Cancel\r\n","4":":TRegister\r\n    List the registers as returned by |:reg|.\r\n\r\nKeys~\r\n    <c-e> ... Edit register\/clipboard\r\n    <c-q> ... Execute register (see |@|)\r\n    <cr>  ... Put selected register(s) (see |:put|)\r\n    <esc> ... Cancel\r\n","install_details":"Copy to ~\/vimfiles\/plugin\/ or ~\/.vim\/plugin\r\n\r\nAlso available via git\r\nhttp:\/\/github.com\/tomtom\/tregisters_vim","5":"Copy to ~\/vimfiles\/plugin\/ or ~\/.vim\/plugin\r\n\r\nAlso available via git\r\nhttp:\/\/github.com\/tomtom\/tregisters_vim","first_name":"Tom","6":"Tom","last_name":"Link","7":"Link","releases":[{"0":"2017","vim_version":"7.0","1":"7.0","script_version":"0.2","2":"0.2","version_comment":"Forgot GetLatestVimScripts id","3":"Forgot GetLatestVimScripts id","package":"tregisters.vim","4":"tregisters.vim","src_id":"7653","5":"7653","creation_date":"1189503056","6":"1189503056"}]},"2016":{"script_id":"2016","0":"2016","script_name":"no_quarter","1":"no_quarter","script_type":"color scheme","2":"color scheme","summary":"Colorfully scheme with an nice dark gray background and low contrast","3":"Colorfully scheme with an nice dark gray background and low contrast","description":"Colorfully scheme with an nice dark gray background, low contrast and some special features for Perl developers.\r\n\r\nScreenshot: http:\/\/emresumo.com\/no_quarter\/no_quarter-screenshot_01.png","4":"Colorfully scheme with an nice dark gray background, low contrast and some special features for Perl developers.\r\n\r\nScreenshot: http:\/\/emresumo.com\/no_quarter\/no_quarter-screenshot_01.png","install_details":"$ mv no_quarter.vim ~\/.vim\/colors\/","5":"$ mv no_quarter.vim ~\/.vim\/colors\/","first_name":"Otavio","6":"Otavio","last_name":"Fernandes","7":"Fernandes","releases":[{"0":"2016","vim_version":"7.0","1":"7.0","script_version":"1.0.7","2":"1.0.7","version_comment":"Improved Perl colors and a darker background.","3":"Improved Perl colors and a darker background.","package":"no_quarter.vim","4":"no_quarter.vim","src_id":"12828","5":"12828","creation_date":"1271255576","6":"1271255576"},{"0":"2016","vim_version":"7.0","1":"7.0","script_version":"1.0.6","2":"1.0.6","version_comment":"Better colors for TXT with Taglist.","3":"Better colors for TXT with Taglist.","package":"no_quarter.vim","4":"no_quarter.vim","src_id":"12007","5":"12007","creation_date":"1262566794","6":"1262566794"},{"0":"2016","vim_version":"7.0","1":"7.0","script_version":"1.0.5","2":"1.0.5","version_comment":"Minor color changes.","3":"Minor color changes.","package":"no_quarter.vim","4":"no_quarter.vim","src_id":"11973","5":"11973","creation_date":"1262032497","6":"1262032497"},{"0":"2016","vim_version":"7.0","1":"7.0","script_version":"1.0.4","2":"1.0.4","version_comment":"New colors for TagList plugin and current line highlight. ","3":"New colors for TagList plugin and current line highlight. ","package":"no_quarter.vim","4":"no_quarter.vim","src_id":"9108","5":"9108","creation_date":"1218386306","6":"1218386306"},{"0":"2016","vim_version":"7.0","1":"7.0","script_version":"1.0.3","2":"1.0.3","version_comment":"Omni menus and comments coloring changes","3":"Omni menus and comments coloring changes","package":"no_quarter.vim","4":"no_quarter.vim","src_id":"7669","5":"7669","creation_date":"1189689090","6":"1189689090"},{"0":"2016","vim_version":"7.0","1":"7.0","script_version":"1.0.2","2":"1.0.2","version_comment":"New colors for Perl Scripts","3":"New colors for Perl Scripts","package":"no_quarter.vim","4":"no_quarter.vim","src_id":"7659","5":"7659","creation_date":"1189578696","6":"1189578696"},{"0":"2016","vim_version":"7.0","1":"7.0","script_version":"1.0.0","2":"1.0.0","version_comment":"Initial upload","3":"Initial upload","package":"no_quarter.vim","4":"no_quarter.vim","src_id":"7646","5":"7646","creation_date":"1189488220","6":"1189488220"}]},"2015":{"script_id":"2015","0":"2015","script_name":"cheat.vim","1":"cheat.vim","script_type":"utility","2":"utility","summary":"Vim wrapper for cheat (http:\/\/cheat.errtheblog.com) utility.","3":"Vim wrapper for cheat (http:\/\/cheat.errtheblog.com) utility.","description":"Usage:\r\n\r\n:Cheat <Tab>\r\nwill autocomplete the available cheatsheets.\r\n\r\nalternatively, you can position the cursor over a word matching a cheatsheet (say ambition) and hit <leader>ch\r\nTip: looks nicer when you have wildmenu turned on ;-)","4":"Usage:\r\n\r\n:Cheat <Tab>\r\nwill autocomplete the available cheatsheets.\r\n\r\nalternatively, you can position the cursor over a word matching a cheatsheet (say ambition) and hit <leader>ch\r\nTip: looks nicer when you have wildmenu turned on ;-)","install_details":"Just drop in $VIM\/plugin\/ and you're set.","5":"Just drop in $VIM\/plugin\/ and you're set.","first_name":"Alexandru","6":"Alexandru","last_name":"Ungur","7":"Ungur","releases":[{"0":"2015","vim_version":"6.0","1":"6.0","script_version":"1.2","2":"1.2","version_comment":"* added CheatRecent command to get a list of recent cheatsheets\r\n* thanks to Ferry Boender for the code for dumping output of\r\n   commands into a window (Bexec - script #1788) now Cheat dumps\r\n   its output into a window as well, and no longer to 'stdout'\r\n","3":"* added CheatRecent command to get a list of recent cheatsheets\r\n* thanks to Ferry Boender for the code for dumping output of\r\n   commands into a window (Bexec - script #1788) now Cheat dumps\r\n   its output into a window as well, and no longer to 'stdout'\r\n","package":"cheat.vim","4":"cheat.vim","src_id":"8748","5":"8748","creation_date":"1212534013","6":"1212534013"},{"0":"2015","vim_version":"6.0","1":"6.0","script_version":"1.1","2":"1.1","version_comment":"Added caching to decrease the loading time. By default it caches to \"$HOME\/.cheats\" but that can be overriden from .vimrc with:\r\nlet g:cheats_cache = \"\/path\/to\/your\/file\"\r\n\r\nAlso the plugin does not depend on any *nix commands any longer (cut, grep, cat) so it may be possible to run it on other platforms as well.\r\n","3":"Added caching to decrease the loading time. By default it caches to \"$HOME\/.cheats\" but that can be overriden from .vimrc with:\r\nlet g:cheats_cache = \"\/path\/to\/your\/file\"\r\n\r\nAlso the plugin does not depend on any *nix commands any longer (cut, grep, cat) so it may be possible to run it on other platforms as well.\r\n","package":"cheat.vim","4":"cheat.vim","src_id":"7676","5":"7676","creation_date":"1189862073","6":"1189862073"},{"0":"2015","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"cheat.vim","4":"cheat.vim","src_id":"7635","5":"7635","creation_date":"1189250595","6":"1189250595"}]},"2014":{"script_id":"2014","0":"2014","script_name":"ttoc","1":"ttoc","script_type":"utility","2":"utility","summary":"A regexp-based table of contents of the current buffer","3":"A regexp-based table of contents of the current buffer","description":"This plugin tries to duplicate the functionality of Marc Weber's \r\noutline.vim (vimscript #1947) on the basis of its description and of \r\nvim's own |:g|. Other than outline.vim, it relies on tlib\r\n(vimscript #1863).\r\n\r\nThe TToC[!] command can be used to get a quick table of contents of the \r\nbuffer based on a given regular expression. The regexp can be defined on \r\nthe command line, in window (w:ttoc_rx), buffer-local (b:ttoc_rx) \r\nvariables or in global filetype-specific (g:ttoc_rx_{&filetype}) \r\nvariables. The order actually is: [wbg]:ttoc_rx_{&filetype} > \r\n[wbg]:ttoc_rx.\r\n\r\nIn the list view, you can select a line and either preview it (<c-p>), \r\njump there (<), close the list and jump there (<cr>).\r\n\r\nExample:\r\n\r\n  \" Use the default settings for the current file-type\r\n  :TToC\r\n  \" Show all words beginning at column 1\r\n  :TToC ^\\w\r\n  \" Show 'if' statements (but not the concluding 'then' statement)\r\n  :TToC ^\\s*if\\>.\\{-}\\ze\\s\\+then\r\n  \" Show 'if' statements and 3 extra lines\r\n  :3TToC! \\<if\\>\r\n\r\nTToC only shows the matching string. TToC! works somewhat like |:g| in \r\nshowing the whole line, only that you can browse\/filter the list and \r\nselect an item after reviewing the results. \r\n","4":"This plugin tries to duplicate the functionality of Marc Weber's \r\noutline.vim (vimscript #1947) on the basis of its description and of \r\nvim's own |:g|. Other than outline.vim, it relies on tlib\r\n(vimscript #1863).\r\n\r\nThe TToC[!] command can be used to get a quick table of contents of the \r\nbuffer based on a given regular expression. The regexp can be defined on \r\nthe command line, in window (w:ttoc_rx), buffer-local (b:ttoc_rx) \r\nvariables or in global filetype-specific (g:ttoc_rx_{&filetype}) \r\nvariables. The order actually is: [wbg]:ttoc_rx_{&filetype} > \r\n[wbg]:ttoc_rx.\r\n\r\nIn the list view, you can select a line and either preview it (<c-p>), \r\njump there (<), close the list and jump there (<cr>).\r\n\r\nExample:\r\n\r\n  \" Use the default settings for the current file-type\r\n  :TToC\r\n  \" Show all words beginning at column 1\r\n  :TToC ^\\w\r\n  \" Show 'if' statements (but not the concluding 'then' statement)\r\n  :TToC ^\\s*if\\>.\\{-}\\ze\\s\\+then\r\n  \" Show 'if' statements and 3 extra lines\r\n  :3TToC! \\<if\\>\r\n\r\nTToC only shows the matching string. TToC! works somewhat like |:g| in \r\nshowing the whole line, only that you can browse\/filter the list and \r\nselect an item after reviewing the results. \r\n","install_details":"Edit the vba file and type: >\r\n\r\n    :so %\r\n\r\nSee :help vimball for details. If you have difficulties, please make \r\nsure, you have the current version of vimball (vimscript #1502) \r\ninstalled.\r\n\r\nThis script requires tlib (vimscript #1863) to be installed.\r\n\r\nSuggested maps (to be set in ~\/.vimrc): >\r\n    noremap  <Leader>cc       :TToC<cr>\r\n    inoremap <Leader>cc       <c-o>:TToC<cr>\r\n    noremap  <Leader>c<space> :TToC!\r\n    inoremap <Leader>c<space> <c-o>:TToC!\r\n\r\nThe following gives you a |[I| or |]I| like experience but with a IMHO more \r\nconvenient UI:\r\n\r\n    noremap  <Leader>c#       :TToC! <c-r><c-w><cr>\r\n    inoremap <Leader>c#       <c-o>:TToC! <c-r><c-w><cr>\r\n\r\n\r\nAlso available via git\r\nhttp:\/\/github.com\/tomtom\/ttoc_vim","5":"Edit the vba file and type: >\r\n\r\n    :so %\r\n\r\nSee :help vimball for details. If you have difficulties, please make \r\nsure, you have the current version of vimball (vimscript #1502) \r\ninstalled.\r\n\r\nThis script requires tlib (vimscript #1863) to be installed.\r\n\r\nSuggested maps (to be set in ~\/.vimrc): >\r\n    noremap  <Leader>cc       :TToC<cr>\r\n    inoremap <Leader>cc       <c-o>:TToC<cr>\r\n    noremap  <Leader>c<space> :TToC!\r\n    inoremap <Leader>c<space> <c-o>:TToC!\r\n\r\nThe following gives you a |[I| or |]I| like experience but with a IMHO more \r\nconvenient UI:\r\n\r\n    noremap  <Leader>c#       :TToC! <c-r><c-w><cr>\r\n    inoremap <Leader>c#       <c-o>:TToC! <c-r><c-w><cr>\r\n\r\n\r\nAlso available via git\r\nhttp:\/\/github.com\/tomtom\/ttoc_vim","first_name":"Tom","6":"Tom","last_name":"Link","7":"Link","releases":[{"0":"2014","vim_version":"7.0","1":"7.0","script_version":"0.08","2":"0.08","version_comment":"- Help template\n- g:ttoc#scratch#wipeout defaults to: 'BufDelete,BufWipeout' . (&hidden ? '' : ',BufHidden')\n- ttoc#View(): Use a clean filename\nMD5 checksum: fcdca87eb2d549e516705e781cfaa069","3":"- Help template\n- g:ttoc#scratch#wipeout defaults to: 'BufDelete,BufWipeout' . (&hidden ? '' : ',BufHidden')\n- ttoc#View(): Use a clean filename\nMD5 checksum: fcdca87eb2d549e516705e781cfaa069","package":"ttoc.vba","4":"ttoc.vba","src_id":"21045","5":"21045","creation_date":"1384512764","6":"1384512764"},{"0":"2014","vim_version":"7.0","1":"7.0","script_version":"0.07","2":"0.07","version_comment":"- addon-info\n- g:ttoc_rx_help\n- Allow for g:ttoc_world_{&filetype}\n- When deleting the source buffer, delete the respective ttoc buffer\nMD5 checksum: bb3b38c08da5d2a5a852d4da75508e3f","3":"- addon-info\n- g:ttoc_rx_help\n- Allow for g:ttoc_world_{&filetype}\n- When deleting the source buffer, delete the respective ttoc buffer\nMD5 checksum: bb3b38c08da5d2a5a852d4da75508e3f","package":"ttoc.vba","4":"ttoc.vba","src_id":"20934","5":"20934","creation_date":"1382118003","6":"1382118003"},{"0":"2014","vim_version":"7.0","1":"7.0","script_version":"0.06","2":"0.06","version_comment":"- .gitignore\n- Removed obsolete code\n- \\n triggers multiline mode (fixes https:\/\/github.com\/tomtom\/tlib_vim\/issues\/12)\n- Markdown support\nMD5 checksum: 87b122db88d0af8092f8b284ec64a9e9","3":"- .gitignore\n- Removed obsolete code\n- \\n triggers multiline mode (fixes https:\/\/github.com\/tomtom\/tlib_vim\/issues\/12)\n- Markdown support\nMD5 checksum: 87b122db88d0af8092f8b284ec64a9e9","package":"ttoc.vba","4":"ttoc.vba","src_id":"17283","5":"17283","creation_date":"1327166569","6":"1327166569"},{"0":"2014","vim_version":"7.0","1":"7.0","script_version":"0.5","2":"0.5","version_comment":"- Handle multi-line regexps (thanks to M Weber for pointing this out)\r\n- Changed key for \"trace cursor\" from <c-t> to <c-insert>.\r\n- Require tlib 0.32\r\n- Fill location list\r\n","3":"- Handle multi-line regexps (thanks to M Weber for pointing this out)\r\n- Changed key for \"trace cursor\" from <c-t> to <c-insert>.\r\n- Require tlib 0.32\r\n- Fill location list\r\n","package":"ttoc.vba.gz","4":"ttoc.vba.gz","src_id":"11512","5":"11512","creation_date":"1255243050","6":"1255243050"},{"0":"2014","vim_version":"7.0","1":"7.0","script_version":"0.3","2":"0.3","version_comment":"- Highlight the search term on partial searches\r\n- Defined :Ttoc as synonym for :TToC\r\n- Defined :Ttocbg to open a toc in the \"background\" (leave the focus\/cursor in the main window)\r\n- Require tlib 0.21\r\n- Experimental: ttoc#Autoword(onoff): automatically show lines containing the word under the cursor; must be enabled for each buffer.\r\n- Split plugin into (autoload|plugin)\/ttoc.vim\r\n- Follow\/trace cursor functionality (toggled with <c-t>): instantly preview the line under cursor.\r\n- Restore original position when using preview","3":"- Highlight the search term on partial searches\r\n- Defined :Ttoc as synonym for :TToC\r\n- Defined :Ttocbg to open a toc in the \"background\" (leave the focus\/cursor in the main window)\r\n- Require tlib 0.21\r\n- Experimental: ttoc#Autoword(onoff): automatically show lines containing the word under the cursor; must be enabled for each buffer.\r\n- Split plugin into (autoload|plugin)\/ttoc.vim\r\n- Follow\/trace cursor functionality (toggled with <c-t>): instantly preview the line under cursor.\r\n- Restore original position when using preview","package":"ttoc.vba.gz","4":"ttoc.vba.gz","src_id":"9549","5":"9549","creation_date":"1227427132","6":"1227427132"},{"0":"2014","vim_version":"7.0","1":"7.0","script_version":"0.2","2":"0.2","version_comment":"- <c-e> Run a command on selected lines.\r\n- g:ttoc_world can be a normal dictionary.\r\n- Use tlib#input#ListD() instead of tlib#input#ListW().\r\n- Require tlib >= 0.14\r\n","3":"- <c-e> Run a command on selected lines.\r\n- g:ttoc_world can be a normal dictionary.\r\n- Use tlib#input#ListD() instead of tlib#input#ListW().\r\n- Require tlib >= 0.14\r\n","package":"ttoc.vba.gz","4":"ttoc.vba.gz","src_id":"7883","5":"7883","creation_date":"1194302489","6":"1194302489"},{"0":"2014","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"ttoc.vba.gz","4":"ttoc.vba.gz","src_id":"7634","5":"7634","creation_date":"1189226538","6":"1189226538"}]},"2013":{"script_id":"2013","0":"2013","script_name":"DrillCtg","1":"DrillCtg","script_type":"utility","2":"utility","summary":"Allows fast drill-down search across the pathnames in your ctags file","3":"Allows fast drill-down search across the pathnames in your ctags file","description":"DrillCtg allows drill-down search by character across the pathnames in your current loaded ctags file.  Upon first launching DrillCtg, if a ctags file is currently set, it will parse it and create a Vim list (an array).  This is a sorted array which contains all unique pathnames, able to searched quickly using Vim's match() function.\r\n\r\nIt uses Vim's complete-functions to provide a dynamically populated list of values which are updated on every keypress.  You can then select which pathname to open.\r\n\r\nIf a ctags file is not currently set upon launching DrillCtg, it will prompt you for the location of one.\r\n\r\nIf you set a different ctags file, upon the next call to DrillCtg, it will replace the contents of the old array with the new pathnames.\r\n\r\nCurrently this plugin only supports 1 loaded ctags file at a time.  If you have more than 1 ctags file loaded, it is likely that this plugin will not work.\r\n\r\nI created this plugin because I wanted something similar to Eclipse's Navigate > Go To > Resource dialog box.  I find this implementation a lot faster than Eclipse when dealing with several thousand unique pathnames.\r\n\r\nDrillCtg requires Vim 7.","4":"DrillCtg allows drill-down search by character across the pathnames in your current loaded ctags file.  Upon first launching DrillCtg, if a ctags file is currently set, it will parse it and create a Vim list (an array).  This is a sorted array which contains all unique pathnames, able to searched quickly using Vim's match() function.\r\n\r\nIt uses Vim's complete-functions to provide a dynamically populated list of values which are updated on every keypress.  You can then select which pathname to open.\r\n\r\nIf a ctags file is not currently set upon launching DrillCtg, it will prompt you for the location of one.\r\n\r\nIf you set a different ctags file, upon the next call to DrillCtg, it will replace the contents of the old array with the new pathnames.\r\n\r\nCurrently this plugin only supports 1 loaded ctags file at a time.  If you have more than 1 ctags file loaded, it is likely that this plugin will not work.\r\n\r\nI created this plugin because I wanted something similar to Eclipse's Navigate > Go To > Resource dialog box.  I find this implementation a lot faster than Eclipse when dealing with several thousand unique pathnames.\r\n\r\nDrillCtg requires Vim 7.","install_details":"1. Drop the plugin file (drillctg.vim) into your plugins directory.\r\n2. Restart Vim to load DrillCtg.\r\n3. To open the search box you can use the \":Drill\" command.\r\n4. To close the search box hit <Esc> and then :q or the :Drill command.","5":"1. Drop the plugin file (drillctg.vim) into your plugins directory.\r\n2. Restart Vim to load DrillCtg.\r\n3. To open the search box you can use the \":Drill\" command.\r\n4. To close the search box hit <Esc> and then :q or the :Drill command.","first_name":"Basil","6":"Basil","last_name":"Shkara","7":"Shkara","releases":[{"0":"2013","vim_version":"7.0","1":"7.0","script_version":"1.1.3","2":"1.1.3","version_comment":"Now checks if existing tag file is readable before prompting for new tags file.\r\n","3":"Now checks if existing tag file is readable before prompting for new tags file.\r\n","package":"drillctg.vim","4":"drillctg.vim","src_id":"8287","5":"8287","creation_date":"1203184974","6":"1203184974"},{"0":"2013","vim_version":"7.0","1":"7.0","script_version":"1.1.2","2":"1.1.2","version_comment":"Added autocommand to clean up after unloading buffer.\r\nNow uses new tab rather than new buffer to clean up ctags file resulting in cleaner exit.","3":"Added autocommand to clean up after unloading buffer.\r\nNow uses new tab rather than new buffer to clean up ctags file resulting in cleaner exit.","package":"drillctg.vim","4":"drillctg.vim","src_id":"7703","5":"7703","creation_date":"1190571010","6":"1190571010"},{"0":"2013","vim_version":"7.0","1":"7.0","script_version":"1.1.1","2":"1.1.1","version_comment":"Fixed bug that occurs when quitting.\r\nAdded support for Takeshi Nishida's autocomplpop.vim.\r\nPlugin now cleans up after itself as it should.","3":"Fixed bug that occurs when quitting.\r\nAdded support for Takeshi Nishida's autocomplpop.vim.\r\nPlugin now cleans up after itself as it should.","package":"drillctg.vim","4":"drillctg.vim","src_id":"7657","5":"7657","creation_date":"1189523813","6":"1189523813"},{"0":"2013","vim_version":"7.0","1":"7.0","script_version":"1.1","2":"1.1","version_comment":"New implementation using Vim's complete-functions.  The interface is now a dynamically populated list which is updated on every key press.","3":"New implementation using Vim's complete-functions.  The interface is now a dynamically populated list which is updated on every key press.","package":"drillctg.vim","4":"drillctg.vim","src_id":"7641","5":"7641","creation_date":"1189388712","6":"1189388712"},{"0":"2013","vim_version":"7.0","1":"7.0","script_version":"1.0.1","2":"1.0.1","version_comment":"Added version checking and small bug fixes","3":"Added version checking and small bug fixes","package":"drillctg.vim","4":"drillctg.vim","src_id":"7631","5":"7631","creation_date":"1189215570","6":"1189215570"}]},"2012":{"script_id":"2012","0":"2012","script_name":"openssl.vim","1":"openssl.vim","script_type":"utility","2":"utility","summary":"Turn Vim into a Password Safe and edit openssl encrypted files","3":"Turn Vim into a Password Safe and edit openssl encrypted files","description":"== Edit OpenSSL encrypted files and turn Vim into a Password Safe! ==\r\n\r\nThis plugin enables reading and writing of files encrypted using OpenSSL.\r\nThe file must have the extension of one of the ciphers used by OpenSSL. For\r\nexample:\r\n\r\n   .des3 .aes .bf .bfa .idea .cast .rc2 .rc4 .rc5\r\n\r\nThis will turn off the swap file and .viminfo log. The `openssl` command\r\nline tool must be in the path.\r\n\r\n== Install ==\r\n\r\nPut this in your plugin directory and Vim will automatically load it:\r\n\r\n   ~\/.vim\/plugin\/openssl.vim\r\n\r\nYou can start by editing an empty unencrypted file. Give it one of the\r\nextensions above. When you write the file you will be asked to give it a new\r\npassword.\r\n\r\n== Simple Vim Password Safe ==\r\n\r\nIf you edit any file named '.auth.bfa' (that's the full name, not just the\r\nextension) then this plugin will add folding features and an automatic quit\r\ntimeout.\r\n\r\nVim will quit automatically after 5 minutes of no typing activity (unless\r\nthe file has been changed).\r\n\r\nThis plugin will fold on wiki-style headlines in the following format:\r\n\r\n    == This is a headline ==\r\n\r\nAny notes under the headline will be inside the fold until the next headline\r\nis reached. The SPACE key will toggle a fold open and closed. The q key will\r\nquit Vim. Create the following example file named ~\/.auth.des3:\r\n\r\n    == Colo server ==\r\n\r\n    username: maryjane password: esydpm\r\n\r\n    == Office server ==\r\n\r\n    username: peter password: 4m4z1ng\r\n\r\nThen create this bash alias:\r\n\r\n    alias auth='view ~\/.auth.des3'\r\n\r\nNow you can view your password safe by typing 'auth'. When Vim starts all\r\nthe password information will be hidden under the headlines. To view the\r\npassword information put the cursor on the headline and press SPACE.\r\n\r\nThanks to Tom Purl for the des3 tip.\r\n\r\nI release all copyright claims. This code is in the public domain.\r\nPermission is granted to use, copy modify, distribute, and sell this\r\nsoftware for any purpose. I make no guarantee about the suitability of this\r\nsoftware for any purpose and I am not liable for any damages resulting from\r\nits use. Further, I am under no obligation to maintain or extend this\r\nsoftware. It is provided on an 'as is' basis without any expressed or\r\nimplied warranty.\r\n","4":"== Edit OpenSSL encrypted files and turn Vim into a Password Safe! ==\r\n\r\nThis plugin enables reading and writing of files encrypted using OpenSSL.\r\nThe file must have the extension of one of the ciphers used by OpenSSL. For\r\nexample:\r\n\r\n   .des3 .aes .bf .bfa .idea .cast .rc2 .rc4 .rc5\r\n\r\nThis will turn off the swap file and .viminfo log. The `openssl` command\r\nline tool must be in the path.\r\n\r\n== Install ==\r\n\r\nPut this in your plugin directory and Vim will automatically load it:\r\n\r\n   ~\/.vim\/plugin\/openssl.vim\r\n\r\nYou can start by editing an empty unencrypted file. Give it one of the\r\nextensions above. When you write the file you will be asked to give it a new\r\npassword.\r\n\r\n== Simple Vim Password Safe ==\r\n\r\nIf you edit any file named '.auth.bfa' (that's the full name, not just the\r\nextension) then this plugin will add folding features and an automatic quit\r\ntimeout.\r\n\r\nVim will quit automatically after 5 minutes of no typing activity (unless\r\nthe file has been changed).\r\n\r\nThis plugin will fold on wiki-style headlines in the following format:\r\n\r\n    == This is a headline ==\r\n\r\nAny notes under the headline will be inside the fold until the next headline\r\nis reached. The SPACE key will toggle a fold open and closed. The q key will\r\nquit Vim. Create the following example file named ~\/.auth.des3:\r\n\r\n    == Colo server ==\r\n\r\n    username: maryjane password: esydpm\r\n\r\n    == Office server ==\r\n\r\n    username: peter password: 4m4z1ng\r\n\r\nThen create this bash alias:\r\n\r\n    alias auth='view ~\/.auth.des3'\r\n\r\nNow you can view your password safe by typing 'auth'. When Vim starts all\r\nthe password information will be hidden under the headlines. To view the\r\npassword information put the cursor on the headline and press SPACE.\r\n\r\nThanks to Tom Purl for the des3 tip.\r\n\r\nI release all copyright claims. This code is in the public domain.\r\nPermission is granted to use, copy modify, distribute, and sell this\r\nsoftware for any purpose. I make no guarantee about the suitability of this\r\nsoftware for any purpose and I am not liable for any damages resulting from\r\nits use. Further, I am under no obligation to maintain or extend this\r\nsoftware. It is provided on an 'as is' basis without any expressed or\r\nimplied warranty.\r\n","install_details":"Put this in your plugin directory and Vim will automatically load it:\r\n\r\n   ~\/.vim\/plugin\/openssl.vim\r\n","5":"Put this in your plugin directory and Vim will automatically load it:\r\n\r\n   ~\/.vim\/plugin\/openssl.vim\r\n","first_name":"Noah","6":"Noah","last_name":"Spurrier","7":"Spurrier","releases":[{"0":"2012","vim_version":"7.0","1":"7.0","script_version":"3.2","2":"3.2","version_comment":"I added a feature to make a backup of an encrypted file before writing changes. This helps guard against the situation where you may edit a file and write changes with the wrong password. You can still go back to the previous backup version. The backup file will have the same name as the original file with .bak before the original extension. For example:\r\n\r\n    .auth.bfa  -->  .auth.bak.bfa\r\n\r\nTo turn on backups put the following global definition in your .vimrc file:\r\n\r\n    let g:openssl_backup = 1\r\n","3":"I added a feature to make a backup of an encrypted file before writing changes. This helps guard against the situation where you may edit a file and write changes with the wrong password. You can still go back to the previous backup version. The backup file will have the same name as the original file with .bak before the original extension. For example:\r\n\r\n    .auth.bfa  -->  .auth.bak.bfa\r\n\r\nTo turn on backups put the following global definition in your .vimrc file:\r\n\r\n    let g:openssl_backup = 1\r\n","package":"openssl.vim","4":"openssl.vim","src_id":"8564","5":"8564","creation_date":"1208262403","6":"1208262403"},{"0":"2012","vim_version":"6.0","1":"6.0","script_version":"3.0","2":"3.0","version_comment":"Initial upload","3":"Initial upload","package":"openssl.vim","4":"openssl.vim","src_id":"7628","5":"7628","creation_date":"1189192537","6":"1189192537"}]},"2011":{"script_id":"2011","0":"2011","script_name":"dbext4rdb","1":"dbext4rdb","script_type":"utility","2":"utility","summary":"dbext 506 with added capabilities for Rdb","3":"dbext 506 with added capabilities for Rdb","description":"For vim on Open VMS look at http:\/\/www.polarhome.com\/vim\/\r\nFor Open VMS http:\/\/h71000.www7.hp.com\/openvms\/\r\n\r\nThe \"official\" dbext 5.11 release (and any future ones) has incorporated the\r\nOracle Rdb Open VMS support.  Please refer to the dbext homepage for further\r\nupdates:\r\nhttps:\/\/www.vim.org\/scripts\/script.php?script_id=356\r\n\r\n\r\nIf DBEXT_506_RDB.ZIP was installed, please verify it was not installed into\r\nany of the vim70 or vim71 directories.  All plugins should be installed into\r\nthe .vim (Unix) or vimfiles (Windows) directories.  If you find any of the\r\ndbext files in the vim7x directories, please remove these before installing\r\nthe official version.\r\n","4":"For vim on Open VMS look at http:\/\/www.polarhome.com\/vim\/\r\nFor Open VMS http:\/\/h71000.www7.hp.com\/openvms\/\r\n\r\nThe \"official\" dbext 5.11 release (and any future ones) has incorporated the\r\nOracle Rdb Open VMS support.  Please refer to the dbext homepage for further\r\nupdates:\r\nhttps:\/\/www.vim.org\/scripts\/script.php?script_id=356\r\n\r\n\r\nIf DBEXT_506_RDB.ZIP was installed, please verify it was not installed into\r\nany of the vim70 or vim71 directories.  All plugins should be installed into\r\nthe .vim (Unix) or vimfiles (Windows) directories.  If you find any of the\r\ndbext files in the vim7x directories, please remove these before installing\r\nthe official version.\r\n","install_details":"see dbext installation instructions:\r\nhttp:\/\/www.vim.org\/scripts\/script.php?script_id=356","5":"see dbext installation instructions:\r\nhttp:\/\/www.vim.org\/scripts\/script.php?script_id=356","first_name":"Andi","6":"Andi","last_name":"Stern","7":"Stern","releases":[{"0":"2011","vim_version":"7.0","1":"7.0","script_version":"506","2":"506","version_comment":"Initial upload","3":"Initial upload","package":"DBEXT_506_RDB.ZIP","4":"DBEXT_506_RDB.ZIP","src_id":"7624","5":"7624","creation_date":"1189137783","6":"1189137783"}]},"2010":{"script_id":"2010","0":"2010","script_name":"sessionman.vim","1":"sessionman.vim","script_type":"utility","2":"utility","summary":"Vim session manager","3":"Vim session manager","description":"Vim provides a ':mksession' command to save the current editing session.  This plug-in helps to work with Vim sessions by keeping them in the dedicated location and by providing commands to list all sessions, open session, open last session, close session, save session and show last session.  From a list of sessions you can open session, delete session, edit session and edit extra session script.  Please note that session name can contain spaces and does not have to have a .vim extension.\r\n\r\nOn Windows, DOS and OS2 sessions are saved in:\r\n  \"$HOME\/vimfiles\/sessions\"   if $HOME is defined\r\n  \"$APPDATA\/Vim\/sessions\"     if $APPDATA is defined\r\n  \"$VIM\/sessions\"             otherwise\r\nOn Unix sessions are saved in:\r\n  \"$HOME\/.vim\/sessions\"\r\nIf this directory does not exist, it will be created by the :SessionSave command (requires Vim 7).\r\n\r\nAt the top of the window there is a help that shows normal mode mappings:\r\n  q                        - close session list\r\n  o, <CR>, <2-LeftMouse>   - open session\r\n  d                        - delete session\r\n  e                        - edit session\r\n  x                        - edit extra session script\r\nThe name of an opened session is saved in g:LAST_SESSION variable which is saved in the viminfo file if 'viminfo' option contains '!'.  It is used to open last session by :SessionOpenLast command.  It can be done when Vim starts (gvim +bd -c SessionOpenLast) or any time during a Vim session.  You can edit an extra session script to specify additional settings and actions associated with a given session.  If you change values of 'expandtab', 'tabstop' or 'shiftwidth', they will be restored to their original values when session is closed or before a new session is opened.  When session is opened and 'cscope' is enabled, script calls 'cscope add' for the current directory so make sure it is set correctly for the session.\r\n\r\n:SessionOpen command takes a session name as an argument.  It supports argument completion.\r\n\r\n:SessionOpenLast command opens the g:LAST_SESSION session (see above).\r\n\r\n:SessionClose command wipes out all buffers, kills cscope and clears variables with session name.\r\n\r\n:SessionSave command saves the current editing session.  If v:this_session is empty it asks for a session name.\r\n\r\n:SessionSaveAs command takes a session name as an optional argument.  If there is no argument or it is empty, it asks for a session name (default is the last part of v:this_session).\r\n\r\n:SessionShowLast command shows the content of the g:LAST_SESSION and v:this_session variables.\r\n\r\nIf 'sessionman_save_on_exit != 0' (default) then the current editing session will be automatically saved when you exit Vim.\r\n\r\nPlug-in creates a \"Sessions\" sub-menu under the \"File\" menu.\r\n","4":"Vim provides a ':mksession' command to save the current editing session.  This plug-in helps to work with Vim sessions by keeping them in the dedicated location and by providing commands to list all sessions, open session, open last session, close session, save session and show last session.  From a list of sessions you can open session, delete session, edit session and edit extra session script.  Please note that session name can contain spaces and does not have to have a .vim extension.\r\n\r\nOn Windows, DOS and OS2 sessions are saved in:\r\n  \"$HOME\/vimfiles\/sessions\"   if $HOME is defined\r\n  \"$APPDATA\/Vim\/sessions\"     if $APPDATA is defined\r\n  \"$VIM\/sessions\"             otherwise\r\nOn Unix sessions are saved in:\r\n  \"$HOME\/.vim\/sessions\"\r\nIf this directory does not exist, it will be created by the :SessionSave command (requires Vim 7).\r\n\r\nAt the top of the window there is a help that shows normal mode mappings:\r\n  q                        - close session list\r\n  o, <CR>, <2-LeftMouse>   - open session\r\n  d                        - delete session\r\n  e                        - edit session\r\n  x                        - edit extra session script\r\nThe name of an opened session is saved in g:LAST_SESSION variable which is saved in the viminfo file if 'viminfo' option contains '!'.  It is used to open last session by :SessionOpenLast command.  It can be done when Vim starts (gvim +bd -c SessionOpenLast) or any time during a Vim session.  You can edit an extra session script to specify additional settings and actions associated with a given session.  If you change values of 'expandtab', 'tabstop' or 'shiftwidth', they will be restored to their original values when session is closed or before a new session is opened.  When session is opened and 'cscope' is enabled, script calls 'cscope add' for the current directory so make sure it is set correctly for the session.\r\n\r\n:SessionOpen command takes a session name as an argument.  It supports argument completion.\r\n\r\n:SessionOpenLast command opens the g:LAST_SESSION session (see above).\r\n\r\n:SessionClose command wipes out all buffers, kills cscope and clears variables with session name.\r\n\r\n:SessionSave command saves the current editing session.  If v:this_session is empty it asks for a session name.\r\n\r\n:SessionSaveAs command takes a session name as an optional argument.  If there is no argument or it is empty, it asks for a session name (default is the last part of v:this_session).\r\n\r\n:SessionShowLast command shows the content of the g:LAST_SESSION and v:this_session variables.\r\n\r\nIf 'sessionman_save_on_exit != 0' (default) then the current editing session will be automatically saved when you exit Vim.\r\n\r\nPlug-in creates a \"Sessions\" sub-menu under the \"File\" menu.\r\n","install_details":"Download and copy sessionman.vim to $HOME\/.vim\/plugin (Unix) or $HOME\/vimfiles\/plugin (Windows) or $VIM\/vimfiles\/plugin (both) directory.","5":"Download and copy sessionman.vim to $HOME\/.vim\/plugin (Unix) or $HOME\/vimfiles\/plugin (Windows) or $VIM\/vimfiles\/plugin (both) directory.","first_name":"Yuri","6":"Yuri","last_name":"Klubakov","7":"Klubakov","releases":[{"0":"2010","vim_version":"6.0","1":"6.0","script_version":"1.07","2":"1.07","version_comment":"Wiping out all buffers with '%bwipeout' was reported to be more reliable by demon386","3":"Wiping out all buffers with '%bwipeout' was reported to be more reliable by demon386","package":"sessionman.vim","4":"sessionman.vim","src_id":"23152","5":"23152","creation_date":"1428553306","6":"1428553306"},{"0":"2010","vim_version":"6.0","1":"6.0","script_version":"1.06","2":"1.06","version_comment":"- Added more \"doautoall\" commands when session is opened (thanks to Marcin Szamotulski)\r\n- Turned off spell checking in session list window.","3":"- Added more \"doautoall\" commands when session is opened (thanks to Marcin Szamotulski)\r\n- Turned off spell checking in session list window.","package":"sessionman.vim","4":"sessionman.vim","src_id":"15599","5":"15599","creation_date":"1304725048","6":"1304725048"},{"0":"2010","vim_version":"6.0","1":"6.0","script_version":"1.05","2":"1.05","version_comment":"- Improved compatibility with other scripts.\r\n- Kill all cscope connections before sourcing new session.\r\n  That allows to add additional connections in extra session script.\r\n- Fixed extra session script file name when session name has an extension.\r\n- Removed <ESC> mapping. Only 'q' will close session list.\r\n","3":"- Improved compatibility with other scripts.\r\n- Kill all cscope connections before sourcing new session.\r\n  That allows to add additional connections in extra session script.\r\n- Fixed extra session script file name when session name has an extension.\r\n- Removed <ESC> mapping. Only 'q' will close session list.\r\n","package":"sessionman.vim","4":"sessionman.vim","src_id":"15591","5":"15591","creation_date":"1304655643","6":"1304655643"},{"0":"2010","vim_version":"6.0","1":"6.0","script_version":"1.04","2":"1.04","version_comment":"- Added ability to edit session file (can be useful if you moved files to a different location) and extra session script (see description).\r\n- Added :SessionShowLast command that shows the content of the g:LAST_SESSION and v:this_session variables.\r\n- Added test if session list window is already displayed and switch to it if it is.\r\n- Show help at the top of the session list window instead of the status line (with Erik Falor)","3":"- Added ability to edit session file (can be useful if you moved files to a different location) and extra session script (see description).\r\n- Added :SessionShowLast command that shows the content of the g:LAST_SESSION and v:this_session variables.\r\n- Added test if session list window is already displayed and switch to it if it is.\r\n- Show help at the top of the session list window instead of the status line (with Erik Falor)","package":"sessionman.vim","4":"sessionman.vim","src_id":"8836","5":"8836","creation_date":"1214148120","6":"1214148120"},{"0":"2010","vim_version":"6.0","1":"6.0","script_version":"1.03","2":"1.03","version_comment":"- The command names were changed to start with :Session... to make them completion-friendly (sorry for breaking your settings).\r\n- Added :SessionOpen {session} command that supports argument completion.  It makes it possible to open a session without showing session list (useful when used in a script).\r\n- Added :SessionSaveAs [session] command.  It makes it possible to save a session without a prompt when called with an argument (useful when used in a script).\r\n- :SessionSave command now saves the active session without a prompt if v:this_session is not empty.","3":"- The command names were changed to start with :Session... to make them completion-friendly (sorry for breaking your settings).\r\n- Added :SessionOpen {session} command that supports argument completion.  It makes it possible to open a session without showing session list (useful when used in a script).\r\n- Added :SessionSaveAs [session] command.  It makes it possible to save a session without a prompt when called with an argument (useful when used in a script).\r\n- :SessionSave command now saves the active session without a prompt if v:this_session is not empty.","package":"sessionman.vim","4":"sessionman.vim","src_id":"7670","5":"7670","creation_date":"1189690565","6":"1189690565"},{"0":"2010","vim_version":"6.0","1":"6.0","script_version":"1.02","2":"1.02","version_comment":"Configurable option to automatically save the current editing session on exit (with Viktor Kojouharov)","3":"Configurable option to automatically save the current editing session on exit (with Viktor Kojouharov)","package":"sessionman.vim","4":"sessionman.vim","src_id":"7658","5":"7658","creation_date":"1189554802","6":"1189554802"},{"0":"2010","vim_version":"6.0","1":"6.0","script_version":"1.01","2":"1.01","version_comment":"- \"OS friendly\" sessions location (see description)\r\n- Create new window for the session list\r\n- Create \"Sessions\" sub-menu under the \"File\" menu","3":"- \"OS friendly\" sessions location (see description)\r\n- Create new window for the session list\r\n- Create \"Sessions\" sub-menu under the \"File\" menu","package":"sessionman.vim","4":"sessionman.vim","src_id":"7636","5":"7636","creation_date":"1189279884","6":"1189279884"},{"0":"2010","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"sessionman.vim","4":"sessionman.vim","src_id":"7621","5":"7621","creation_date":"1189024208","6":"1189024208"}]},"2009":{"script_id":"2009","0":"2009","script_name":"AutoClose","1":"AutoClose","script_type":"utility","2":"utility","summary":"Auto close pair of characters","3":"Auto close pair of characters","description":"*NOTE*\r\n======\r\nThe header of the plugin says it is on version 1.1, but this is wrong. The 1.4 version is indeed the 1.4 version only with a wrong header. Next version I'll fix it.\r\n\r\nOverview\r\n=======\r\nThis plugin was  born  as  a  personal  need  to  have some little special features from other editors into my preferred one. The Eclipse IDE editor has an auto-complete for  open-close  pair  of  characters  feature  that I always wanted into Vim.\r\n\r\nAs soon  as you type  a character that  could have a  close pair,  Eclipse automatically puts its  pair in front of your cursor,  and  if you continue to type and type  the close character,  Eclipse is smart enough  to not insert it again (it just move your cursor one character forward).\r\n\r\nBut the Eclipse editor don't stop  there.  If you type an \"open\" character on any part of your code that  should not have a pair completion,  it will not insert the close character for you.\r\n\r\nThe AutoClose plugin is an attempt to reproduce this behavior on Vim. \r\n\r\nConfiguration\r\n==========\r\n1. Definning characters to auto close\r\n--------------------------------------------------\r\nIf you  are not sattisfied  with the default  characters to close  you can define your own by setting the global variable g:AutoClosePairs.\r\n\r\nThe only thing to be careful is that this variable must be a dictionary on the following format:\r\n\r\n    {\"<open_char>\": \"<close_char>\"}\r\n\r\nOtherwise the  plugin will  not recognize  the settings  and will  use the default values.\r\n\r\nFollowing is the default declaration for auto close chars. If this configuration is enought, you don't need to configure nothing:\r\n\r\n    let g:AutoClosePairs = {'(': ')', '{': '}', '[': ']', '\"': '\"', \"'\": \"'\"}\r\n\r\n\r\n2. Definning protected regions\r\n-----------------------------------------\r\nInside some special  regions  the  auto  close  feature  is far from util, actually we  can say  that on those  regions,  this feature  is worst  than no feature at all. This is the case for \"Comments\" and \"Strings\".\r\n\r\nIf you edit files with this characteristic and there is more than comments and strings where you would like  to protect from auto close,  just define the global variable g:AutoCloseProtectedRegions.\r\n\r\nThis variable must be  a list of strings or the  plugin will not recognize it and will  use the defaults parameters.  The format  of this variable should be:\r\n\r\n    [\"<protected_region1>\", \"<protected_region2>\", ...]\r\n\r\nFollowing is the default declaration to the protected regions.  If you are satisfied with this, you don't have to set this setting:\r\n\r\n    let g:AutoCloseProtectedRegions. = [\"Comment\", \"String\", \"Character\"]\r\n\r\n\r\n3. Turning AutoComplete on and off\r\n------------------------------------------------\r\nAs AutoComplete change the buffer you are editing, sometimes you just want to turn this feature off for a while and than turn it on again.\r\n\r\nAutoComplete provide three  commands that can be mapped to  any key as you want to do that task:\r\n\r\n    1. AutoCloseOn\r\n    2. AutoCloseOff\r\n    3. AutoCloseToggle\r\n\r\nAnd if you don't want to map anything, just use them on the command mode.\r\n","4":"*NOTE*\r\n======\r\nThe header of the plugin says it is on version 1.1, but this is wrong. The 1.4 version is indeed the 1.4 version only with a wrong header. Next version I'll fix it.\r\n\r\nOverview\r\n=======\r\nThis plugin was  born  as  a  personal  need  to  have some little special features from other editors into my preferred one. The Eclipse IDE editor has an auto-complete for  open-close  pair  of  characters  feature  that I always wanted into Vim.\r\n\r\nAs soon  as you type  a character that  could have a  close pair,  Eclipse automatically puts its  pair in front of your cursor,  and  if you continue to type and type  the close character,  Eclipse is smart enough  to not insert it again (it just move your cursor one character forward).\r\n\r\nBut the Eclipse editor don't stop  there.  If you type an \"open\" character on any part of your code that  should not have a pair completion,  it will not insert the close character for you.\r\n\r\nThe AutoClose plugin is an attempt to reproduce this behavior on Vim. \r\n\r\nConfiguration\r\n==========\r\n1. Definning characters to auto close\r\n--------------------------------------------------\r\nIf you  are not sattisfied  with the default  characters to close  you can define your own by setting the global variable g:AutoClosePairs.\r\n\r\nThe only thing to be careful is that this variable must be a dictionary on the following format:\r\n\r\n    {\"<open_char>\": \"<close_char>\"}\r\n\r\nOtherwise the  plugin will  not recognize  the settings  and will  use the default values.\r\n\r\nFollowing is the default declaration for auto close chars. If this configuration is enought, you don't need to configure nothing:\r\n\r\n    let g:AutoClosePairs = {'(': ')', '{': '}', '[': ']', '\"': '\"', \"'\": \"'\"}\r\n\r\n\r\n2. Definning protected regions\r\n-----------------------------------------\r\nInside some special  regions  the  auto  close  feature  is far from util, actually we  can say  that on those  regions,  this feature  is worst  than no feature at all. This is the case for \"Comments\" and \"Strings\".\r\n\r\nIf you edit files with this characteristic and there is more than comments and strings where you would like  to protect from auto close,  just define the global variable g:AutoCloseProtectedRegions.\r\n\r\nThis variable must be  a list of strings or the  plugin will not recognize it and will  use the defaults parameters.  The format  of this variable should be:\r\n\r\n    [\"<protected_region1>\", \"<protected_region2>\", ...]\r\n\r\nFollowing is the default declaration to the protected regions.  If you are satisfied with this, you don't have to set this setting:\r\n\r\n    let g:AutoCloseProtectedRegions. = [\"Comment\", \"String\", \"Character\"]\r\n\r\n\r\n3. Turning AutoComplete on and off\r\n------------------------------------------------\r\nAs AutoComplete change the buffer you are editing, sometimes you just want to turn this feature off for a while and than turn it on again.\r\n\r\nAutoComplete provide three  commands that can be mapped to  any key as you want to do that task:\r\n\r\n    1. AutoCloseOn\r\n    2. AutoCloseOff\r\n    3. AutoCloseToggle\r\n\r\nAnd if you don't want to map anything, just use them on the command mode.\r\n","install_details":"Put the script into your $VIM\/plugin directory and the documentation into $VIM\/doc and type on your vim:\r\n\r\n   :helptags $VIM\/doc\r\n\r\nYou can change $VIM to whatever place your vim can automatically read plugins and documentations like in your home vim directory.","5":"Put the script into your $VIM\/plugin directory and the documentation into $VIM\/doc and type on your vim:\r\n\r\n   :helptags $VIM\/doc\r\n\r\nYou can change $VIM to whatever place your vim can automatically read plugins and documentations like in your home vim directory.","first_name":"Thiago","6":"Thiago","last_name":"Alves","7":"Alves","releases":[{"0":"2009","vim_version":"7.0","1":"7.0","script_version":"1.4","2":"1.4","version_comment":"Fix a problem when use AutoClose on Visual Mode Blockwise. Unfortunatelly Backspace will not work as expected on this mode due Vim behavior. E.g.:\r\nSelect a column of text and press <Backspace> than <Delete> keys. You'll see that only the first line will be changed.","3":"Fix a problem when use AutoClose on Visual Mode Blockwise. Unfortunatelly Backspace will not work as expected on this mode due Vim behavior. E.g.:\r\nSelect a column of text and press <Backspace> than <Delete> keys. You'll see that only the first line will be changed.","package":"autoclose.vim","4":"autoclose.vim","src_id":"9223","5":"9223","creation_date":"1220507036","6":"1220507036"},{"0":"2009","vim_version":"7.0","1":"7.0","script_version":"1.3","2":"1.3","version_comment":"Fix a bug that prevent to automatically close pair of equal chars that the first one is entered on the very first column.","3":"Fix a bug that prevent to automatically close pair of equal chars that the first one is entered on the very first column.","package":"autoclose.zip","4":"autoclose.zip","src_id":"9169","5":"9169","creation_date":"1219691913","6":"1219691913"},{"0":"2009","vim_version":"7.0","1":"7.0","script_version":"1.2","2":"1.2","version_comment":"Fixed the not closing bug to string on some languages. Perhaps other strange behaviors also happens because of that!","3":"Fixed the not closing bug to string on some languages. Perhaps other strange behaviors also happens because of that!","package":"autoclose.zip","4":"autoclose.zip","src_id":"9163","5":"9163","creation_date":"1219604869","6":"1219604869"},{"0":"2009","vim_version":"7.0","1":"7.0","script_version":"1.1","2":"1.1","version_comment":"Complete refactor of the plugin.\r\nRemove all autocommands and drastically simplify the whole plugin.\r\nThis version was refactor thanks for the simple_pairs plugin that was launched on 08\/10\/2008 that point me to a much simpler way!","3":"Complete refactor of the plugin.\r\nRemove all autocommands and drastically simplify the whole plugin.\r\nThis version was refactor thanks for the simple_pairs plugin that was launched on 08\/10\/2008 that point me to a much simpler way!","package":"autoclose.zip","4":"autoclose.zip","src_id":"9110","5":"9110","creation_date":"1218478979","6":"1218478979"},{"0":"2009","vim_version":"7.0","1":"7.0","script_version":"0.9","2":"0.9","version_comment":"Initial upload","3":"Initial upload","package":"townkAutoCompleteChar.vim","4":"townkAutoCompleteChar.vim","src_id":"7620","5":"7620","creation_date":"1188931337","6":"1188931337"}]},"2008":{"script_id":"2008","0":"2008","script_name":"buffer-status-menu.vim","1":"buffer-status-menu.vim","script_type":"utility","2":"utility","summary":"Add modified\/current status to Buffers menu","3":"Add modified\/current status to Buffers menu","description":"Replacement for Vim's default buffers menu to add status display.\r\nNow adds a + before modified buffers, * before the current buffer.\r\n\r\nNote that Vim doesn't seem to have an autocmd event for a buffer\r\nbecoming modified, so the menu won't show this change until something\r\nelse causes it to refresh.\r\n\r\nOriginal code stolen from Vim 7.0-164","4":"Replacement for Vim's default buffers menu to add status display.\r\nNow adds a + before modified buffers, * before the current buffer.\r\n\r\nNote that Vim doesn't seem to have an autocmd event for a buffer\r\nbecoming modified, so the menu won't show this change until something\r\nelse causes it to refresh.\r\n\r\nOriginal code stolen from Vim 7.0-164","install_details":"Just drop it in the Vim plugins directory.","5":"Just drop it in the Vim plugins directory.","first_name":"Thomas","6":"Thomas","last_name":"Matysik","7":"Matysik","releases":[{"0":"2008","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"buffer-status-menu.vim","4":"buffer-status-menu.vim","src_id":"7614","5":"7614","creation_date":"1188689980","6":"1188689980"}]},"2007":{"script_id":"2007","0":"2007","script_name":"greplist.vim","1":"greplist.vim","script_type":"utility","2":"utility","summary":"vimgrep location list manager","3":"vimgrep location list manager","description":"This plug-in is for someone who often does multi-file search in multiple locations and these locations often change when for example you work on several different projects.  It helps to maintain a list of frequently used vimgrep locations and defines commands to edit a list and to perform a search in the selected locations.\r\n\r\n:GrepListConfig command loads a list for editing.  A list is kept in\r\n\"$HOME\/_vimgrep\" file or in \"$VIM\/_vimgrep\" file if $HOME is not defined.  If \"_vimgrep\" file does not exist or empty, a sample list is created.  Status line shows useful normal mode mappings:\r\n  'q' - abandon any changes and wipe the buffer\r\n  's' - save the changes and wipe the buffer\r\n  ' ' - select\/deselect current line (selected lines start with '+')\r\n\r\n:GrepListFind(mode) command prompts for the string to find and starts the vimgrep search in the selected locations.  The default value for the search string is either the current visual selection (mode != 0) or the current word (mode == 0).  Plug-in automatically surrounds the search string with '\/' and adds 'j' option.\r\n\r\nAs usual, it is more convenient to create mappings for these commands.  For example:\r\nnoremap <F8> :GrepListFind 0<CR>\r\ninoremap <F8> <C-O>:GrepListFind 0<CR>\r\nvnoremap <F8> <C-C>:GrepListFind 1<CR>\r\n\r\nFor more information please see the source code -- it is small and easy to read.\r\n","4":"This plug-in is for someone who often does multi-file search in multiple locations and these locations often change when for example you work on several different projects.  It helps to maintain a list of frequently used vimgrep locations and defines commands to edit a list and to perform a search in the selected locations.\r\n\r\n:GrepListConfig command loads a list for editing.  A list is kept in\r\n\"$HOME\/_vimgrep\" file or in \"$VIM\/_vimgrep\" file if $HOME is not defined.  If \"_vimgrep\" file does not exist or empty, a sample list is created.  Status line shows useful normal mode mappings:\r\n  'q' - abandon any changes and wipe the buffer\r\n  's' - save the changes and wipe the buffer\r\n  ' ' - select\/deselect current line (selected lines start with '+')\r\n\r\n:GrepListFind(mode) command prompts for the string to find and starts the vimgrep search in the selected locations.  The default value for the search string is either the current visual selection (mode != 0) or the current word (mode == 0).  Plug-in automatically surrounds the search string with '\/' and adds 'j' option.\r\n\r\nAs usual, it is more convenient to create mappings for these commands.  For example:\r\nnoremap <F8> :GrepListFind 0<CR>\r\ninoremap <F8> <C-O>:GrepListFind 0<CR>\r\nvnoremap <F8> <C-C>:GrepListFind 1<CR>\r\n\r\nFor more information please see the source code -- it is small and easy to read.\r\n","install_details":"Download and copy greplist.vim to $HOME\/vimfiles\/plugin or \r\n$VIM\/vimfiles\/plugin directory.","5":"Download and copy greplist.vim to $HOME\/vimfiles\/plugin or \r\n$VIM\/vimfiles\/plugin directory.","first_name":"Yuri","6":"Yuri","last_name":"Klubakov","7":"Klubakov","releases":[{"0":"2007","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"greplist.vim","4":"greplist.vim","src_id":"7613","5":"7613","creation_date":"1188678862","6":"1188678862"}]},"2006":{"script_id":"2006","0":"2006","script_name":"progressbar widget","1":"progressbar widget","script_type":"game","2":"game","summary":"pimp your plugins","3":"pimp your plugins","description":"Pimp your plugins with the latest in widget technology ! This plugin implements a simple progressbar for the statusline. Never again you will have to wonder, how you should tell your user that something is happening.\r\n\r\nThis may be the foundation of big vim widgets library :O)","4":"Pimp your plugins with the latest in widget technology ! This plugin implements a simple progressbar for the statusline. Never again you will have to wonder, how you should tell your user that something is happening.\r\n\r\nThis may be the foundation of big vim widgets library :O)","install_details":"- extract it to your vimdir\r\n- read the example in autoload\/vim\/widgets\/progressbar_example.vim","5":"- extract it to your vimdir\r\n- read the example in autoload\/vim\/widgets\/progressbar_example.vim","first_name":"Andreas","6":"Andreas","last_name":"Politz","7":"Politz","releases":[{"0":"2006","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"progressbar-1.0.tgz","4":"progressbar-1.0.tgz","src_id":"7612","5":"7612","creation_date":"1188649408","6":"1188649408"}]},"2005":{"script_id":"2005","0":"2005","script_name":"karma.vim","1":"karma.vim","script_type":"utility","2":"utility","summary":"For given karma print how users possibly voted","3":"For given karma print how users possibly voted","description":"Usage:\r\n:Karma {score} {votes}\r\n\r\nExamples:\r\n:Karma 4727 1463\r\nKarma: 4727\/1463\r\n   1. Life Changing: 1088   Helpful: 375   Unfulfilling: 0\r\n   2. Life Changing: 1090   Helpful: 370   Unfulfilling: 3\r\n      ...\r\n  76. Life Changing: 1238   Helpful: 0   Unfulfilling: 225\r\n\r\n(the dots are literal output, and btw this is the karma for vimscript #273)\r\n\r\nChecking the results (here for 2.):\r\n    1090*4 + 370*1 + 3*(-1) = 4727\r\n    1090 + 370 + 3 = 1463\r\n\r\n:Karma -3 16\r\nKarma: -3\/16\r\n   1. Life Changing: 1   Helpful: 4   Unfulfilling: 11\r\n\r\nOther vimscripts: vimscript #936\r\n\r\n2007 Dec 08","4":"Usage:\r\n:Karma {score} {votes}\r\n\r\nExamples:\r\n:Karma 4727 1463\r\nKarma: 4727\/1463\r\n   1. Life Changing: 1088   Helpful: 375   Unfulfilling: 0\r\n   2. Life Changing: 1090   Helpful: 370   Unfulfilling: 3\r\n      ...\r\n  76. Life Changing: 1238   Helpful: 0   Unfulfilling: 225\r\n\r\n(the dots are literal output, and btw this is the karma for vimscript #273)\r\n\r\nChecking the results (here for 2.):\r\n    1090*4 + 370*1 + 3*(-1) = 4727\r\n    1090 + 370 + 3 = 1463\r\n\r\n:Karma -3 16\r\nKarma: -3\/16\r\n   1. Life Changing: 1   Helpful: 4   Unfulfilling: 11\r\n\r\nOther vimscripts: vimscript #936\r\n\r\n2007 Dec 08","install_details":"copy script to ~\/.vim\/plugin\r\nor  :source  it when needed\r\n\r\nHint: you can also make the script \"autoloaded\" (Vim 5.7 and above):\r\n- copy script to ~\/.vim\/\r\n- put the following line into your .vimrc\r\n    com -nargs=* Karma so ~\/.vim\/karma.vim| Karma <args>","5":"copy script to ~\/.vim\/plugin\r\nor  :source  it when needed\r\n\r\nHint: you can also make the script \"autoloaded\" (Vim 5.7 and above):\r\n- copy script to ~\/.vim\/\r\n- put the following line into your .vimrc\r\n    com -nargs=* Karma so ~\/.vim\/karma.vim| Karma <args>","first_name":"Andy","6":"Andy","last_name":"Wokula","7":"Wokula","releases":[{"0":"2005","vim_version":"5.7","1":"5.7","script_version":"4","2":"4","version_comment":"NF: now also prints an average voting","3":"NF: now also prints an average voting","package":"karma.vim","4":"karma.vim","src_id":"17330","5":"17330","creation_date":"1327786320","6":"1327786320"},{"0":"2005","vim_version":"5.7","1":"5.7","script_version":"3","2":"3","version_comment":"now compatible to Vim 5.7","3":"now compatible to Vim 5.7","package":"karma.vim","4":"karma.vim","src_id":"7616","5":"7616","creation_date":"1188894525","6":"1188894525"},{"0":"2005","vim_version":"7.0","1":"7.0","script_version":"2","2":"2","version_comment":"rating -1\/1 is a bug report, lol.  but who knows that (-1 % 2) is -1, and not 1.","3":"rating -1\/1 is a bug report, lol.  but who knows that (-1 % 2) is -1, and not 1.","package":"karma.vim","4":"karma.vim","src_id":"7581","5":"7581","creation_date":"1188398990","6":"1188398990"},{"0":"2005","vim_version":"7.0","1":"7.0","script_version":"1","2":"1","version_comment":"Initial upload","3":"Initial upload","package":"karma.vim","4":"karma.vim","src_id":"7579","5":"7579","creation_date":"1188393040","6":"1188393040"}]},"2004":{"script_id":"2004","0":"2004","script_name":"ColorSchemeMenuMaker","1":"ColorSchemeMenuMaker","script_type":"color scheme","2":"color scheme","summary":"Auto-generates menu containing your colorschemes (keywords: color scheme menu)","3":"Auto-generates menu containing your colorschemes (keywords: color scheme menu)","description":"Are you in the mood for a blue desktop, but don't want to take the time to go through all of your installed color scheme files just to find the ones you want?  Or do you like to make each of your Vim windows a different color to easily identify which editor contains which projects?\r\n\r\nIf so, this plugin is for you.\r\n\r\nThis script crawls through the directories in your &runtimepath searching for installed colorscheme files.  When it finds a colorscheme, it adds it to a menu called ColorSchemes where it is sorted by the predominant color used.  Color schemes are also stored alphabetically by name in this menu.  This way, you can have all of your blue themes at your fingertips.  Or if you just remember the name, you can quickly browse to it.\r\n\r\nThis script works by analysing the guibg option of the Normal highlight group to determine which basic color to file the scheme under.  It will place each theme in one of the following categories: black, blue, cyan, darkgrey, green, grey, offwhite, orange, purple, red, white, yellow, or unknown if no background color is specified.  It uses a heuristic that is still a work in progress, so it doesn't always guess the color correctly.  For that matter, people have a hard time deciding what category a color might fall under, so it may always be a work in progress!\r\n\r\nIf you install new color schemes, force a re-scan by clicking 'Rebuild Menu' in the ColorSchemes menu.  'Reload Menu' simply forces Vim to re-source an already generated menu file.\r\n\r\nA menu entry that appears with an asterisk before it indicates a color scheme that contains more than one \"hi Normal\" command.  This script assumes that the first such command encountered is the one that will be executed.  Such entries are not guaranteed to be sorted correctly.\r\n\r\nSince version 0.6, this script includes an autoload plugin that facilitates tweaking the color selection algorithm.\r\nThis autoload plugin contains a Perl script which generates an HTML page that shows the Normal background color for each installed theme, along with the plugin's guess at which category it should be filed under.  The embedded Perl script calls the very same functions the plugin uses, letting you quickly assess the results of your changes.  The plugin keeps track of the three previous guesses, and highlights the colorschemes that have been affected by your changes.  \r\n\r\nMore details are found in plugin\/ColorSchemeMenuMaker.vim.\r\n\r\nIf you can make any improvements, I'd love to see them!\r\n","4":"Are you in the mood for a blue desktop, but don't want to take the time to go through all of your installed color scheme files just to find the ones you want?  Or do you like to make each of your Vim windows a different color to easily identify which editor contains which projects?\r\n\r\nIf so, this plugin is for you.\r\n\r\nThis script crawls through the directories in your &runtimepath searching for installed colorscheme files.  When it finds a colorscheme, it adds it to a menu called ColorSchemes where it is sorted by the predominant color used.  Color schemes are also stored alphabetically by name in this menu.  This way, you can have all of your blue themes at your fingertips.  Or if you just remember the name, you can quickly browse to it.\r\n\r\nThis script works by analysing the guibg option of the Normal highlight group to determine which basic color to file the scheme under.  It will place each theme in one of the following categories: black, blue, cyan, darkgrey, green, grey, offwhite, orange, purple, red, white, yellow, or unknown if no background color is specified.  It uses a heuristic that is still a work in progress, so it doesn't always guess the color correctly.  For that matter, people have a hard time deciding what category a color might fall under, so it may always be a work in progress!\r\n\r\nIf you install new color schemes, force a re-scan by clicking 'Rebuild Menu' in the ColorSchemes menu.  'Reload Menu' simply forces Vim to re-source an already generated menu file.\r\n\r\nA menu entry that appears with an asterisk before it indicates a color scheme that contains more than one \"hi Normal\" command.  This script assumes that the first such command encountered is the one that will be executed.  Such entries are not guaranteed to be sorted correctly.\r\n\r\nSince version 0.6, this script includes an autoload plugin that facilitates tweaking the color selection algorithm.\r\nThis autoload plugin contains a Perl script which generates an HTML page that shows the Normal background color for each installed theme, along with the plugin's guess at which category it should be filed under.  The embedded Perl script calls the very same functions the plugin uses, letting you quickly assess the results of your changes.  The plugin keeps track of the three previous guesses, and highlights the colorschemes that have been affected by your changes.  \r\n\r\nMore details are found in plugin\/ColorSchemeMenuMaker.vim.\r\n\r\nIf you can make any improvements, I'd love to see them!\r\n","install_details":"Unpack the archive in your $HOME\/.vim (or $HOME\/vimfiles, you poor, poor Win32 user) directory. The next time you start an instance of Vim, it will detect that the file ColorSchemes.vim is not present, and will add all of your color schemes to the menu.  ColorSchemes.vim is written in the the same directory the main plugin is located.\r\n\r\nSubsequently, Vim will use the generated file instead of re-scanning all of your color schemes.\r\n\r\nSend feedback to ewfalor -at- gmail -dot- com","5":"Unpack the archive in your $HOME\/.vim (or $HOME\/vimfiles, you poor, poor Win32 user) directory. The next time you start an instance of Vim, it will detect that the file ColorSchemes.vim is not present, and will add all of your color schemes to the menu.  ColorSchemes.vim is written in the the same directory the main plugin is located.\r\n\r\nSubsequently, Vim will use the generated file instead of re-scanning all of your color schemes.\r\n\r\nSend feedback to ewfalor -at- gmail -dot- com","first_name":"erik","6":"erik","last_name":"falor","7":"falor","releases":[{"0":"2004","vim_version":"7.0","1":"7.0","script_version":"1.0.2","2":"1.0.2","version_comment":"Adjust lookup path for rgb.txt","3":"Adjust lookup path for rgb.txt","package":"ColorSchemeMenuMaker.zip","4":"ColorSchemeMenuMaker.zip","src_id":"17640","5":"17640","creation_date":"1332453470","6":"1332453470"}]},"2003":{"script_id":"2003","0":"2003","script_name":"gobgen","1":"gobgen","script_type":"utility","2":"utility","summary":"GObject skeleton generator","3":"GObject skeleton generator","description":"This plugin generate simple c and h templates for new GObject class and interface.\r\nThere a bit of commands for this:\r\n- GOBGenerateC\r\n- GOBGenerateIC\r\n- GOBGenerateCModule\r\n- GOBGenerateH\r\n- GOBGenerateIH\r\nScript by default uses current file name for class name (optionaly you can type class name manually)\r\n\r\nFor nice code formating it is need to enable ai option","4":"This plugin generate simple c and h templates for new GObject class and interface.\r\nThere a bit of commands for this:\r\n- GOBGenerateC\r\n- GOBGenerateIC\r\n- GOBGenerateCModule\r\n- GOBGenerateH\r\n- GOBGenerateIH\r\nScript by default uses current file name for class name (optionaly you can type class name manually)\r\n\r\nFor nice code formating it is need to enable ai option","install_details":"Copy gobgen.vim file to ~\/.vim\/plugins directory","5":"Copy gobgen.vim file to ~\/.vim\/plugins directory","first_name":"Andrey","6":"Andrey","last_name":"Dubravin","7":"Dubravin","releases":[{"0":"2003","vim_version":"6.0","1":"6.0","script_version":"1.3","2":"1.3","version_comment":"Add GOBGenenrateIH GOBGenenrateIC for interface generation\r\nFix: prefix prompt identical for all functions","3":"Add GOBGenenrateIH GOBGenenrateIC for interface generation\r\nFix: prefix prompt identical for all functions","package":"gobgen.vim","4":"gobgen.vim","src_id":"7879","5":"7879","creation_date":"1194241601","6":"1194241601"},{"0":"2003","vim_version":"6.0","1":"6.0","script_version":"1.2","2":"1.2","version_comment":"Fix bug in GOBGenerateH function (parentName not defined)","3":"Fix bug in GOBGenerateH function (parentName not defined)","package":"gobgen.vim","4":"gobgen.vim","src_id":"7771","5":"7771","creation_date":"1191932245","6":"1191932245"},{"0":"2003","vim_version":"6.0","1":"6.0","script_version":"1.1","2":"1.1","version_comment":"Added GOBGenerateCModule function, that generate .c file pattern for plugin class realisation\r\nFix: cast dispose and finalize functions\r\nFix: remove question about prefix name editing","3":"Added GOBGenerateCModule function, that generate .c file pattern for plugin class realisation\r\nFix: cast dispose and finalize functions\r\nFix: remove question about prefix name editing","package":"gobgen.vim","4":"gobgen.vim","src_id":"7667","5":"7667","creation_date":"1189682752","6":"1189682752"},{"0":"2003","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"gobgen.vim","4":"gobgen.vim","src_id":"7558","5":"7558","creation_date":"1188103654","6":"1188103654"}]},"2002":{"script_id":"2002","0":"2002","script_name":"python_ifold","1":"python_ifold","script_type":"utility","2":"utility","summary":"Improved version of python_fold. Uses folding expression for python code.","3":"Improved version of python_fold. Uses folding expression for python code.","description":"Folds are created for:\r\n\r\n- 'class' and 'def' definitions.\r\n- Blocks between {{{, }}} markers (but not yet {{{n, etc.)\r\n\r\n\r\nFlavors:\r\n\r\n- A (python_ifold.a.vim) - ideal for legacy systems.\r\n- B (python_ifold.b.vim) -  with all options set by default.\r\n- C (python_ifold.c.vim) -  same as flavor B, but uses extra Vim settings for user comfort.\r\n\r\n\r\nImprovements over python_fold:\r\n\r\n- Fixes the wild (i.e. bogus) folding bug \r\n- Shows class and function signatures\r\n- Now, as in the original, flavor B will omit any misplaced comment mark\r\n- Flavor A boosts performance on outdated systems, something of great importance when there are lots of nested folds over large code pages\r\n\r\n\r\nCaveats:\r\n\r\n- The fold level for each fold is equal to the indentation divided by the value of the 'shiftwidth' option, so make sure that 'shiftwidth' is set to the right value for your code. For best results set 'shiftwidth' , 'softtabstop'  and 'tabstop' to the same value, and use 'expandtab' and 'autoindent' (all included in flavor C).\r\n\r\nExample:\r\nset tabstop=4\r\nset softtabstop=4\r\nset shiftwidth=4\r\nset expandtab\r\nset autoindent\r\nset foldcolumn=1  \" Optional\r\n\r\n- Class and function folds show a counter of number of lines (and the first line below the signature) that are within the fold when it's closed. Read the change history to learn more about this.\r\n\r\n- Press F key whenever you want to disable temporarily the folding, press F again to re-enable it (won't fold the block of code where the cursor is, though).\r\n\r\n- If g:ifold_mode is set to a value greater than 0, will make extra parsing to your code to avoid including blank lines at the end of each fold and wont unfold your code if any comment marks are misplaced. This behavior is set by default in flavor B. But be warned , though. This option requires more power from your system (hence the two versions: 'A' for lower-end systems and 'B' for powerful-enough systems), so if you lack of requirements you shouldn't use it. \r\n\r\n- The docstring is not shown at all.\r\n\r\n- If you choose flavor A or if you set the global g:ifold_mode to 0, bare in mind that any comment mark between the beginning of a line and the first expression's character (of a sentence) WILL interfere with the whole folding process, that is, only if these marks do not respect the indentation sequence.","4":"Folds are created for:\r\n\r\n- 'class' and 'def' definitions.\r\n- Blocks between {{{, }}} markers (but not yet {{{n, etc.)\r\n\r\n\r\nFlavors:\r\n\r\n- A (python_ifold.a.vim) - ideal for legacy systems.\r\n- B (python_ifold.b.vim) -  with all options set by default.\r\n- C (python_ifold.c.vim) -  same as flavor B, but uses extra Vim settings for user comfort.\r\n\r\n\r\nImprovements over python_fold:\r\n\r\n- Fixes the wild (i.e. bogus) folding bug \r\n- Shows class and function signatures\r\n- Now, as in the original, flavor B will omit any misplaced comment mark\r\n- Flavor A boosts performance on outdated systems, something of great importance when there are lots of nested folds over large code pages\r\n\r\n\r\nCaveats:\r\n\r\n- The fold level for each fold is equal to the indentation divided by the value of the 'shiftwidth' option, so make sure that 'shiftwidth' is set to the right value for your code. For best results set 'shiftwidth' , 'softtabstop'  and 'tabstop' to the same value, and use 'expandtab' and 'autoindent' (all included in flavor C).\r\n\r\nExample:\r\nset tabstop=4\r\nset softtabstop=4\r\nset shiftwidth=4\r\nset expandtab\r\nset autoindent\r\nset foldcolumn=1  \" Optional\r\n\r\n- Class and function folds show a counter of number of lines (and the first line below the signature) that are within the fold when it's closed. Read the change history to learn more about this.\r\n\r\n- Press F key whenever you want to disable temporarily the folding, press F again to re-enable it (won't fold the block of code where the cursor is, though).\r\n\r\n- If g:ifold_mode is set to a value greater than 0, will make extra parsing to your code to avoid including blank lines at the end of each fold and wont unfold your code if any comment marks are misplaced. This behavior is set by default in flavor B. But be warned , though. This option requires more power from your system (hence the two versions: 'A' for lower-end systems and 'B' for powerful-enough systems), so if you lack of requirements you shouldn't use it. \r\n\r\n- The docstring is not shown at all.\r\n\r\n- If you choose flavor A or if you set the global g:ifold_mode to 0, bare in mind that any comment mark between the beginning of a line and the first expression's character (of a sentence) WILL interfere with the whole folding process, that is, only if these marks do not respect the indentation sequence.","install_details":"Download the archive and extract the flavor that suits your needs. Then, either source that file whenever you want to use the folding, or save it in your ftplugin directory (for example, ~\/.vim\/ftplugin) and it should load every time you edit python code.\r\n","5":"Download the archive and extract the flavor that suits your needs. Then, either source that file whenever you want to use the folding, or save it in your ftplugin directory (for example, ~\/.vim\/ftplugin) and it should load every time you edit python code.\r\n","first_name":"Jean-Pierre","6":"Jean-Pierre","last_name":"Chauvel","7":"Chauvel","releases":[{"0":"2002","vim_version":"6.0","1":"6.0","script_version":"2.9","2":"2.9","version_comment":"- Code refactoring and small fixes. \r\n- There's a new experimental engine for testing purposes. I did a regression from version 2.8.4 to 2.8.3.6 to the code, moving the enhancement you usually found in 2.8.4 to the experimental engine. It'll stay in this state until I fix some minor bugs. If you wish to continue using the \"signature\" enhancement, you need to put this in your vimrc:\r\nlet g:ifold_mode=2\r\n- The globals g:ifold_support_markers, g:ifold_show_text, and g:ifold_accuracy were deleted and their respective functionality was replaced with the global g:ifold_mode when its value is 1 ore greater.","3":"- Code refactoring and small fixes. \r\n- There's a new experimental engine for testing purposes. I did a regression from version 2.8.4 to 2.8.3.6 to the code, moving the enhancement you usually found in 2.8.4 to the experimental engine. It'll stay in this state until I fix some minor bugs. If you wish to continue using the \"signature\" enhancement, you need to put this in your vimrc:\r\nlet g:ifold_mode=2\r\n- The globals g:ifold_support_markers, g:ifold_show_text, and g:ifold_accuracy were deleted and their respective functionality was replaced with the global g:ifold_mode when its value is 1 ore greater.","package":"python_ifold-2.9.zip","4":"python_ifold-2.9.zip","src_id":"8583","5":"8583","creation_date":"1208686716","6":"1208686716"},{"0":"2002","vim_version":"6.0","1":"6.0","script_version":"2.8.4","2":"2.8.4","version_comment":"Now it will show the entire signatures of class and function definitions, even if spanned for several lines.","3":"Now it will show the entire signatures of class and function definitions, even if spanned for several lines.","package":"python_ifold-2.8.4.zip","4":"python_ifold-2.8.4.zip","src_id":"8578","5":"8578","creation_date":"1208535467","6":"1208535467"},{"0":"2002","vim_version":"6.0","1":"6.0","script_version":"2.8.3.6","2":"2.8.3.6","version_comment":"minor bugfix: Fixed a small bug introduced in the previous release.","3":"minor bugfix: Fixed a small bug introduced in the previous release.","package":"python_ifold-2.8.3.6.zip","4":"python_ifold-2.8.3.6.zip","src_id":"8576","5":"8576","creation_date":"1208533550","6":"1208533550"},{"0":"2002","vim_version":"6.0","1":"6.0","script_version":"2.8.3.5","2":"2.8.3.5","version_comment":"New python_ifold flavor: After receiving many requests via email, I decided to put all the vimrc recommended settings inside the plugin. In a nutshell, it loads these settings whenever the user opens a python file:\r\n\r\nset tabstop=4\r\nset softtabstop=4\r\nset shiftwidth=4\r\nset expandtab\r\nset autoindent\r\nset foldcolumn=1\r\n","3":"New python_ifold flavor: After receiving many requests via email, I decided to put all the vimrc recommended settings inside the plugin. In a nutshell, it loads these settings whenever the user opens a python file:\r\n\r\nset tabstop=4\r\nset softtabstop=4\r\nset shiftwidth=4\r\nset expandtab\r\nset autoindent\r\nset foldcolumn=1\r\n","package":"python_ifold-2.8.3.5.zip","4":"python_ifold-2.8.3.5.zip","src_id":"8514","5":"8514","creation_date":"1207043598","6":"1207043598"},{"0":"2002","vim_version":"6.0","1":"6.0","script_version":"2.8.3.4","2":"2.8.3.4","version_comment":"Fix (applicable only for the 'b' flavor): small fix for bug introduced in version 2.8.3.3.b","3":"Fix (applicable only for the 'b' flavor): small fix for bug introduced in version 2.8.3.3.b","package":"python_ifold-2.8.3.4.zip","4":"python_ifold-2.8.3.4.zip","src_id":"8427","5":"8427","creation_date":"1204968083","6":"1204968083"},{"0":"2002","vim_version":"6.0","1":"6.0","script_version":"2.8.3.3","2":"2.8.3.3","version_comment":"Only in the b version or if the g:ifold_accuracy global variable is set\r\nFix: Now the script omits any comment mark that lays between the beginning of the line and the first sentence's character, that is, it wont unfold your code even if you put comment marks without proper indentation.","3":"Only in the b version or if the g:ifold_accuracy global variable is set\r\nFix: Now the script omits any comment mark that lays between the beginning of the line and the first sentence's character, that is, it wont unfold your code even if you put comment marks without proper indentation.","package":"python_ifold-2.8.3.3.zip","4":"python_ifold-2.8.3.3.zip","src_id":"8370","5":"8370","creation_date":"1204280965","6":"1204280965"},{"0":"2002","vim_version":"6.0","1":"6.0","script_version":"2.8.3.2.b","2":"2.8.3.2.b","version_comment":"python_ifold with all options selected by default","3":"python_ifold with all options selected by default","package":"python_ifold.vim","4":"python_ifold.vim","src_id":"7988","5":"7988","creation_date":"1196024149","6":"1196024149"},{"0":"2002","vim_version":"6.0","1":"6.0","script_version":"2.8.3.2.a","2":"2.8.3.2.a","version_comment":"python_ifold for legacy systems","3":"python_ifold for legacy systems","package":"python_ifold.vim","4":"python_ifold.vim","src_id":"7986","5":"7986","creation_date":"1196023476","6":"1196023476"},{"0":"2002","vim_version":"6.0","1":"6.0","script_version":"2.8.3.2","2":"2.8.3.2","version_comment":"Enhancement: Now the script prevents \"folding preemption\", that is, when you try to expand the distance between two fold groups--be them class or function definitions--the engine will prevent from blank lines being eaten up at the bottom of the first fold group; nevertheless, I created a new global (g:ifold_accuracy) so that you can compare the former behavior with the new one.  Also, I decided to make the older engine the default method because it's quicker.\r\n\r\nNew global:\r\ng:ifold_accuracy (0 by default, set it to 1 for experimentation with the new, someway better, behavior)\r\n\r\nPut this in your vimrc to try it:\r\nlet g:fold_accuracy = 1","3":"Enhancement: Now the script prevents \"folding preemption\", that is, when you try to expand the distance between two fold groups--be them class or function definitions--the engine will prevent from blank lines being eaten up at the bottom of the first fold group; nevertheless, I created a new global (g:ifold_accuracy) so that you can compare the former behavior with the new one.  Also, I decided to make the older engine the default method because it's quicker.\r\n\r\nNew global:\r\ng:ifold_accuracy (0 by default, set it to 1 for experimentation with the new, someway better, behavior)\r\n\r\nPut this in your vimrc to try it:\r\nlet g:fold_accuracy = 1","package":"python_ifold.vim","4":"python_ifold.vim","src_id":"7809","5":"7809","creation_date":"1192747145","6":"1192747145"},{"0":"2002","vim_version":"6.0","1":"6.0","script_version":"2.8.3.1","2":"2.8.3.1","version_comment":"bugfix: the ugly bug introduced in 2.8.3 is no more :D","3":"bugfix: the ugly bug introduced in 2.8.3 is no more :D","package":"python_ifold.vim","4":"python_ifold.vim","src_id":"7607","5":"7607","creation_date":"1188577603","6":"1188577603"},{"0":"2002","vim_version":"6.0","1":"6.0","script_version":"2.8.3","2":"2.8.3","version_comment":"code refactoring and bugfixing:\r\nbefore this upgrade the script tend to include commented lines within folded block of lines when they where uncommented, pretty annoying.","3":"code refactoring and bugfixing:\r\nbefore this upgrade the script tend to include commented lines within folded block of lines when they where uncommented, pretty annoying.","package":"python_ifold.vim","4":"python_ifold.vim","src_id":"7605","5":"7605","creation_date":"1188571060","6":"1188571060"},{"0":"2002","vim_version":"6.0","1":"6.0","script_version":"2.8.2","2":"2.8.2","version_comment":"bugfix: a stupid bug didn't allow the script to segregate line comments from the class or function definition even if this token was found two lines ahead. I really don't know if this was the expected behavior.\r\n\r\nExample:\r\n\r\nclass A:\r\n    pass\r\n\r\n    #this line was included inside the fold","3":"bugfix: a stupid bug didn't allow the script to segregate line comments from the class or function definition even if this token was found two lines ahead. I really don't know if this was the expected behavior.\r\n\r\nExample:\r\n\r\nclass A:\r\n    pass\r\n\r\n    #this line was included inside the fold","package":"python_ifold.vim","4":"python_ifold.vim","src_id":"7601","5":"7601","creation_date":"1188556624","6":"1188556624"},{"0":"2002","vim_version":"6.0","1":"6.0","script_version":"2.8.1","2":"2.8.1","version_comment":" Bugfixes:\r\n- the script now avoids folding a block of code when there is a class or function definition 2 lines ahead.\r\n- It is now possible to have one line of separation between classes of the same level of indentation without worrying the script eating that line--although happening in extremely rare cases:\r\n\r\nclass A():\r\n    # will start folding here\r\n    ...\r\n    class SubSomething():\r\n        somethinghere = ''\r\n        # the script ate the next \r\n        # blank line before the bugfix\r\n\r\nclass B():\r\n    ...","3":" Bugfixes:\r\n- the script now avoids folding a block of code when there is a class or function definition 2 lines ahead.\r\n- It is now possible to have one line of separation between classes of the same level of indentation without worrying the script eating that line--although happening in extremely rare cases:\r\n\r\nclass A():\r\n    # will start folding here\r\n    ...\r\n    class SubSomething():\r\n        somethinghere = ''\r\n        # the script ate the next \r\n        # blank line before the bugfix\r\n\r\nclass B():\r\n    ...","package":"python_ifold.vim","4":"python_ifold.vim","src_id":"7596","5":"7596","creation_date":"1188527735","6":"1188527735"},{"0":"2002","vim_version":"6.0","1":"6.0","script_version":"2.8","2":"2.8","version_comment":"Bugfix: this time, the script won't fold when the immediate line is a class or function definition, like the example below\r\n\r\nclass MyClass():\r\n    def __init__():\r\n        return something     #no fold will be here\r\n    class MyInnerClass():\r\n        #...","3":"Bugfix: this time, the script won't fold when the immediate line is a class or function definition, like the example below\r\n\r\nclass MyClass():\r\n    def __init__():\r\n        return something     #no fold will be here\r\n    class MyInnerClass():\r\n        #...","package":"python_ifold.vim","4":"python_ifold.vim","src_id":"7568","5":"7568","creation_date":"1188233601","6":"1188233601"},{"0":"2002","vim_version":"6.0","1":"6.0","script_version":"2.7","2":"2.7","version_comment":"Feature: Now you can toggle on\/off the script with 'f' key (it won't fold the block where the cursor is tough, but can be folded with zC later).","3":"Feature: Now you can toggle on\/off the script with 'f' key (it won't fold the block where the cursor is tough, but can be folded with zC later).","package":"python_ifold.vim","4":"python_ifold.vim","src_id":"7565","5":"7565","creation_date":"1188155173","6":"1188155173"},{"0":"2002","vim_version":"6.0","1":"6.0","script_version":"2.6","2":"2.6","version_comment":"Feature: The support markers and the text displayed in the folds are now optional (unset by default), in a desperate attempt to achieve better performance on legacy systems.\r\nIf you want the opposite behavior then you have to set the globals g:ifold_support_markers and g:ifold_show_text to 1.","3":"Feature: The support markers and the text displayed in the folds are now optional (unset by default), in a desperate attempt to achieve better performance on legacy systems.\r\nIf you want the opposite behavior then you have to set the globals g:ifold_support_markers and g:ifold_show_text to 1.","package":"python_ifold.vim","4":"python_ifold.vim","src_id":"7564","5":"7564","creation_date":"1188149942","6":"1188149942"},{"0":"2002","vim_version":"6.0","1":"6.0","script_version":"2.5","2":"2.5","version_comment":"Feature: Added ReFold() function, pretty useful when some or all folds disappear.","3":"Feature: Added ReFold() function, pretty useful when some or all folds disappear.","package":"python_ifold.vim","4":"python_ifold.vim","src_id":"7557","5":"7557","creation_date":"1188085711","6":"1188085711"},{"0":"2002","vim_version":"6.0","1":"6.0","script_version":"2.4","2":"2.4","version_comment":"Initial upload","3":"Initial upload","package":"python_ifold.vim","4":"python_ifold.vim","src_id":"7555","5":"7555","creation_date":"1188069337","6":"1188069337"}]},"2001":{"script_id":"2001","0":"2001","script_name":"lookup.vim","1":"lookup.vim","script_type":"utility","2":"utility","summary":"Lookup dictionary meaning of a word (and thesaurus too)","3":"Lookup dictionary meaning of a word (and thesaurus too)","description":"Place your cursor over a word and run :Lookup. It will then display the list of meanings from a dictionary and the list of similar words from a thesaurus.\r\n\r\nIt talks to a DICT server to look up the meaning, so the script will need an active internet connection to work.","4":"Place your cursor over a word and run :Lookup. It will then display the list of meanings from a dictionary and the list of similar words from a thesaurus.\r\n\r\nIt talks to a DICT server to look up the meaning, so the script will need an active internet connection to work.","install_details":"1. Download http:\/\/gopher.quux.org:70\/devel\/dictclient\/dictclient_1.0.1.tar.gz,  run 'tar -xvzf dictclient_1.0.1.tar.gz' and then run 'cd dictclient; python setup.py install'.\r\n2. Copy lookup.vim to ~\/.vim\/plugin\/ (or ~\/vimfiles\/plugin\/ on Windows)","5":"1. Download http:\/\/gopher.quux.org:70\/devel\/dictclient\/dictclient_1.0.1.tar.gz,  run 'tar -xvzf dictclient_1.0.1.tar.gz' and then run 'cd dictclient; python setup.py install'.\r\n2. Copy lookup.vim to ~\/.vim\/plugin\/ (or ~\/vimfiles\/plugin\/ on Windows)","first_name":"Swaroop","6":"Swaroop","last_name":"C H","7":"C H","releases":[{"0":"2001","vim_version":"6.0","1":"6.0","script_version":"2.1","2":"2.1","version_comment":"Updating to a different working DICT server, thanks to finferflu.","3":"Updating to a different working DICT server, thanks to finferflu.","package":"lookup.vim","4":"lookup.vim","src_id":"7824","5":"7824","creation_date":"1193196303","6":"1193196303"},{"0":"2001","vim_version":"6.0","1":"6.0","script_version":"2","2":"2","version_comment":"Now uses DICT protocol.","3":"Now uses DICT protocol.","package":"lookup.vim","4":"lookup.vim","src_id":"7644","5":"7644","creation_date":"1189445809","6":"1189445809"},{"0":"2001","vim_version":"6.0","1":"6.0","script_version":"1","2":"1","version_comment":"Initial upload","3":"Initial upload","package":"lookup.vim","4":"lookup.vim","src_id":"7553","5":"7553","creation_date":"1188028221","6":"1188028221"}]},"2000":{"script_id":"2000","0":"2000","script_name":"blinking_cursor","1":"blinking_cursor","script_type":"utility","2":"utility","summary":"Makes the cursor blink in x terms when the user is in insert mode","3":"Makes the cursor blink in x terms when the user is in insert mode","description":"A short script ( with two c prgrams ) that makes the cursor blink in x terms when the user switches in insert mode. I think it may run on other vim Version, but i didn't test yet. ","4":"A short script ( with two c prgrams ) that makes the cursor blink in x terms when the user switches in insert mode. I think it may run on other vim Version, but i didn't test yet. ","install_details":"* Supported os:\r\n  - Linux\/UNIX\r\n* Install:\r\n  - copy the archive somewhere in your Vim path (usually \/usr\/share\/vim\/addons\/plugin if you've got root permissions  or ~\/.vim\/plugin). You can also put it anywhere as long as you keep  'vimblinkcursor' and 'vimstopblinking' along with blink_cursor.vim. In this case switch the script on manually into Vim with:\r\n          :so \/path\/to\/the\/script\/blinking_cursor.vim\r\n\r\n  - untar the archive:\r\n          $ tar -zxvf blinking_cursor.tar.gz\r\n\r\n  - Make sure that your terminal isn't set to make the cursor blink (in gnome-terminal : Edit=>Current Profile...). If you want to keep the cursor blinking while not using vim, you can add this line in your ~\/.bashrc file :\r\n            \/full\/path\/to\/the\/script\/vimblinkcursor&\r\nand in your ~\/.vimrc:\r\n            augroup blinking_cursor\r\n            au!    \r\n            au VimLeave * :silent! ! \/full\/path\/to\/the\/scriptvimblinkcursor&\r\n            augroup END\r\n\r\n  - If it doesn't work as expected, or if you are not on a i386-arch computer, compile vimblinkcursor and stopblinking sources again:\r\n           $ gcc vimblinkcursor.c -o vimblinkcursor\r\n           $ gcc vimstopblinking.c -o vimstopblinking\r\n\r\n  - If it still does not work properly, please e-mail me\r\n* TODO:\r\n  - let the user set the blinking delays\r\n  - let the user switch the script on\/off \r\n  - port to windows ( i don't think i can do it myself _I've got only an uninstalled win95 copy_. If someone can, please e-mail me ) \r\n* Thanks\r\n  - blinking_cursor.vim uses blink.c by Bram Moolenaar (provided with vim in \/tools)\r\n","5":"* Supported os:\r\n  - Linux\/UNIX\r\n* Install:\r\n  - copy the archive somewhere in your Vim path (usually \/usr\/share\/vim\/addons\/plugin if you've got root permissions  or ~\/.vim\/plugin). You can also put it anywhere as long as you keep  'vimblinkcursor' and 'vimstopblinking' along with blink_cursor.vim. In this case switch the script on manually into Vim with:\r\n          :so \/path\/to\/the\/script\/blinking_cursor.vim\r\n\r\n  - untar the archive:\r\n          $ tar -zxvf blinking_cursor.tar.gz\r\n\r\n  - Make sure that your terminal isn't set to make the cursor blink (in gnome-terminal : Edit=>Current Profile...). If you want to keep the cursor blinking while not using vim, you can add this line in your ~\/.bashrc file :\r\n            \/full\/path\/to\/the\/script\/vimblinkcursor&\r\nand in your ~\/.vimrc:\r\n            augroup blinking_cursor\r\n            au!    \r\n            au VimLeave * :silent! ! \/full\/path\/to\/the\/scriptvimblinkcursor&\r\n            augroup END\r\n\r\n  - If it doesn't work as expected, or if you are not on a i386-arch computer, compile vimblinkcursor and stopblinking sources again:\r\n           $ gcc vimblinkcursor.c -o vimblinkcursor\r\n           $ gcc vimstopblinking.c -o vimstopblinking\r\n\r\n  - If it still does not work properly, please e-mail me\r\n* TODO:\r\n  - let the user set the blinking delays\r\n  - let the user switch the script on\/off \r\n  - port to windows ( i don't think i can do it myself _I've got only an uninstalled win95 copy_. If someone can, please e-mail me ) \r\n* Thanks\r\n  - blinking_cursor.vim uses blink.c by Bram Moolenaar (provided with vim in \/tools)\r\n","first_name":"Bruno","6":"Bruno","last_name":"Dupuis","7":"Dupuis","releases":[{"0":"2000","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"blinking_cursor.tar.gz","4":"blinking_cursor.tar.gz","src_id":"7550","5":"7550","creation_date":"1187886944","6":"1187886944"}]},"1999":{"script_id":"1999","0":"1999","script_name":"sas.vim","1":"sas.vim","script_type":"syntax","2":"syntax","summary":"SAS syntax file","3":"SAS syntax file","description":"And updated SAS syntax file that uses the suggested group names from {group-name} instead of defining its own color scheme.","4":"And updated SAS syntax file that uses the suggested group names from {group-name} instead of defining its own color scheme.","install_details":"Place in ~\/.vim\/syntax\/ and the appropriate BufRead,BufNew autocmds in ~\/.vim\/filetype.vim or ~\/.vim\/ftdetect\/sas.vim.","5":"Place in ~\/.vim\/syntax\/ and the appropriate BufRead,BufNew autocmds in ~\/.vim\/filetype.vim or ~\/.vim\/ftdetect\/sas.vim.","first_name":"Will","6":"Will","last_name":"Gray","7":"Gray","releases":[{"0":"1999","vim_version":"5.7","1":"5.7","script_version":"1.1.0","2":"1.1.0","version_comment":"Simplified comment regions (let me know if it's incomplete).  Fixed string regions.  Changed macro items to a match pattern.","3":"Simplified comment regions (let me know if it's incomplete).  Fixed string regions.  Changed macro items to a match pattern.","package":"sas.vim","4":"sas.vim","src_id":"7587","5":"7587","creation_date":"1188468377","6":"1188468377"},{"0":"1999","vim_version":"6.0","1":"6.0","script_version":"1.0.1","2":"1.0.1","version_comment":"Edited the comments","3":"Edited the comments","package":"sas.vim","4":"sas.vim","src_id":"7574","5":"7574","creation_date":"1188301811","6":"1188301811"},{"0":"1999","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"sas.vim","4":"sas.vim","src_id":"7545","5":"7545","creation_date":"1187793299","6":"1187793299"}]},"1998":{"script_id":"1998","0":"1998","script_name":"iast.vim","1":"iast.vim","script_type":"utility","2":"utility","summary":"Vim Keymap file for translitteration of pāli and sanskrit with IAST mapping","3":"Vim Keymap file for translitteration of pāli and sanskrit with IAST mapping","description":"Vim Keymap file for translitteration of pāli and sanskrit with IAST mapping","4":"Vim Keymap file for translitteration of pāli and sanskrit with IAST mapping","install_details":"Install to Vim keymap directory and say in Vim:\r\n:set keymap=iast\r\n","5":"Install to Vim keymap directory and say in Vim:\r\n:set keymap=iast\r\n","first_name":"t-","6":"t-","last_name":"om","7":"om","releases":[{"0":"1998","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"iast.vim","4":"iast.vim","src_id":"7539","5":"7539","creation_date":"1187681260","6":"1187681260"}]},"1997":{"script_id":"1997","0":"1997","script_name":"undo_tags","1":"undo_tags","script_type":"utility","2":"utility","summary":"small utility that lets you tag undo branches","3":"small utility that lets you tag undo branches","description":"Undo branches are a very cool feature in vim7, which I recently discovered.\r\nYou can navigate through the change history of the current session as\r\nlong as you do not run out of undolevels.\r\n\r\nThis small plugin lets you:\r\n-  Assign tags \/ names and description to points in the buffers change history\r\n-  List the tags \/ names\r\n-  Choose a tag \/ name to revert back","4":"Undo branches are a very cool feature in vim7, which I recently discovered.\r\nYou can navigate through the change history of the current session as\r\nlong as you do not run out of undolevels.\r\n\r\nThis small plugin lets you:\r\n-  Assign tags \/ names and description to points in the buffers change history\r\n-  List the tags \/ names\r\n-  Choose a tag \/ name to revert back","install_details":"Extract it to your vim dir.\r\nDo :helptags","5":"Extract it to your vim dir.\r\nDo :helptags","first_name":"Andreas","6":"Andreas","last_name":"Politz","7":"Politz","releases":[{"0":"1997","vim_version":"7.0","1":"7.0","script_version":"1.2","2":"1.2","version_comment":"+helpfile more standard alike\r\n+better handling of long tagnames\r\n+allow tagging a virgin buffer ","3":"+helpfile more standard alike\r\n+better handling of long tagnames\r\n+allow tagging a virgin buffer ","package":"undo_tags-1.2.tgz","4":"undo_tags-1.2.tgz","src_id":"7609","5":"7609","creation_date":"1188587048","6":"1188587048"},{"0":"1997","vim_version":"7.0","1":"7.0","script_version":"1.1","2":"1.1","version_comment":"- renamed commands\r\n- replaced autocommand with function\r\n- added command for deleting tags\r\n- use changenr() instead of :undolist\r\n  this way it always returns to the correct textstate\r\n+thanks to A.Wokula\r\n\r\n\t\t\r\n","3":"- renamed commands\r\n- replaced autocommand with function\r\n- added command for deleting tags\r\n- use changenr() instead of :undolist\r\n  this way it always returns to the correct textstate\r\n+thanks to A.Wokula\r\n\r\n\t\t\r\n","package":"undo_tags-1.1.tar.gz","4":"undo_tags-1.1.tar.gz","src_id":"7549","5":"7549","creation_date":"1187874539","6":"1187874539"},{"0":"1997","vim_version":"7.0","1":"7.0","script_version":"1.0.1","2":"1.0.1","version_comment":"bugfix :  changed the strftime  string, which happens to crash on some windows\u00c2\u00a9 versions","3":"bugfix :  changed the strftime  string, which happens to crash on some windows\u00c2\u00a9 versions","package":"undo_tags-1.0.1.tar.gz","4":"undo_tags-1.0.1.tar.gz","src_id":"7546","5":"7546","creation_date":"1187804042","6":"1187804042"},{"0":"1997","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"undo_tags-1-0.tar.gz","4":"undo_tags-1-0.tar.gz","src_id":"7536","5":"7536","creation_date":"1187652279","6":"1187652279"}]},"1996":{"script_id":"1996","0":"1996","script_name":"bruce.vim","1":"bruce.vim","script_type":"utility","2":"utility","summary":"annoy people who spy on your emails","3":"annoy people who spy on your emails","description":"This small Python plugin is a translation of the Emacs 'bruce' utility (formerly known as 'spook'). It adds key words and phrases one might expect in a e-mail spying program to the end of the current buffer in the form of a signature, in order to confuse such programs. I didn't write it so much to make a statement as to relieve boredom for a few minutes, but the issue is important.\r\n\r\nIncludes a terrible Swedish translation of the README.","4":"This small Python plugin is a translation of the Emacs 'bruce' utility (formerly known as 'spook'). It adds key words and phrases one might expect in a e-mail spying program to the end of the current buffer in the form of a signature, in order to confuse such programs. I didn't write it so much to make a statement as to relieve boredom for a few minutes, but the issue is important.\r\n\r\nIncludes a terrible Swedish translation of the README.","install_details":"Installation is relatively simple. Copy bruce.vim to global or local plugin directory. You'll need a data file, ~\/.bruce.lines of course, which consists of special words and phrases, separated by newlines; otherwise Python will raise an error. I included a good example from Emacs with small changes.","5":"Installation is relatively simple. Copy bruce.vim to global or local plugin directory. You'll need a data file, ~\/.bruce.lines of course, which consists of special words and phrases, separated by newlines; otherwise Python will raise an error. I included a good example from Emacs with small changes.","first_name":"chris","6":"chris","last_name":"hever","7":"hever","releases":[{"0":"1996","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"bruce.tgz","4":"bruce.tgz","src_id":"7523","5":"7523","creation_date":"1187389523","6":"1187389523"}]},"1995":{"script_id":"1995","0":"1995","script_name":"railscasts","1":"railscasts","script_type":"color scheme","2":"color scheme","summary":"Railscasts TextMate theme for Vim (GUI Only)","3":"Railscasts TextMate theme for Vim (GUI Only)","description":"A GUI only color scheme based on the Railscasts TextMate theme.  To see the TextMate version check out http:\/\/railscasts.com\r\n\r\nGitHub: http:\/\/github.com\/jpo\/vim-railscasts-theme\/tree\/master\r\nScreenshot: http:\/\/github.com\/jpo\/vim-railscasts-theme\/blob\/43a71c6debe22d74dfabda27b58cca415c8925d5\/screenshot.jpg","4":"A GUI only color scheme based on the Railscasts TextMate theme.  To see the TextMate version check out http:\/\/railscasts.com\r\n\r\nGitHub: http:\/\/github.com\/jpo\/vim-railscasts-theme\/tree\/master\r\nScreenshot: http:\/\/github.com\/jpo\/vim-railscasts-theme\/blob\/43a71c6debe22d74dfabda27b58cca415c8925d5\/screenshot.jpg","install_details":"Just copy it into ~\/.vim\/colors\/ (*nix) or vimfiles\/colors\/ (Windows) as with other color schemes.\r\nType \"colorscheme railscasts\" into your vimrc file.","5":"Just copy it into ~\/.vim\/colors\/ (*nix) or vimfiles\/colors\/ (Windows) as with other color schemes.\r\nType \"colorscheme railscasts\" into your vimrc file.","first_name":"Josh","6":"Josh","last_name":"O'Rourke","7":"O'Rourke","releases":[{"0":"1995","vim_version":"7.0","1":"7.0","script_version":"1.3","2":"1.3","version_comment":"Added colors for Directory, Fold, and Drop Menu, and others. ","3":"Added colors for Directory, Fold, and Drop Menu, and others. ","package":"railscasts.vim","4":"railscasts.vim","src_id":"10645","5":"10645","creation_date":"1242852302","6":"1242852302"},{"0":"1995","vim_version":"7.0","1":"7.0","script_version":"1.2","2":"1.2","version_comment":"Replaced the ruby specific highlight groups with more general ones.","3":"Replaced the ruby specific highlight groups with more general ones.","package":"railscasts.vim","4":"railscasts.vim","src_id":"10558","5":"10558","creation_date":"1241718325","6":"1241718325"},{"0":"1995","vim_version":"7.0","1":"7.0","script_version":"1.1","2":"1.1","version_comment":"Minor color tweaking and fixes.","3":"Minor color tweaking and fixes.","package":"railscasts.vim","4":"railscasts.vim","src_id":"7520","5":"7520","creation_date":"1187366623","6":"1187366623"},{"0":"1995","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"railscasts.vim","4":"railscasts.vim","src_id":"7508","5":"7508","creation_date":"1187267027","6":"1187267027"}]},"1994":{"script_id":"1994","0":"1994","script_name":"confluencewiki.vim","1":"confluencewiki.vim","script_type":"syntax","2":"syntax","summary":"Confluence WIKI syntax","3":"Confluence WIKI syntax","description":"This is the syntax highlighter for Atlassian Confluence WIKI \r\n\r\nhttp:\/\/confluence.atlassian.com\/renderer\/notationhelp.action?section=all","4":"This is the syntax highlighter for Atlassian Confluence WIKI \r\n\r\nhttp:\/\/confluence.atlassian.com\/renderer\/notationhelp.action?section=all","install_details":"copy this script to ~\/.vim\/syntax\/confluencewiki.vim\r\n\r\nset ft=confluencewiki \r\n","5":"copy this script to ~\/.vim\/syntax\/confluencewiki.vim\r\n\r\nset ft=confluencewiki \r\n","first_name":"Daniel","6":"Daniel","last_name":"Gra\u00c3\u00b1a","7":"Gra\u00c3\u00b1a","releases":[{"0":"1994","vim_version":"7.0","1":"7.0","script_version":"1.0.1","2":"1.0.1","version_comment":"Folding improvements sent by Robin Lee Powell <rlpowell@digitalkingdom.org>","3":"Folding improvements sent by Robin Lee Powell <rlpowell@digitalkingdom.org>","package":"confluencewiki.vim","4":"confluencewiki.vim","src_id":"24162","5":"24162","creation_date":"1460083720","6":"1460083720"},{"0":"1994","vim_version":"6.0","1":"6.0","script_version":"1.0.0","2":"1.0.0","version_comment":"More improvements from Ingo Karkat. \r\n\r\nquoting him:\r\n> I recently had made some additional tweaks to the boundary\r\n> conditions of formatting markup; stuff like ({{text}}) wasn't properly\r\n> highlighted.","3":"More improvements from Ingo Karkat. \r\n\r\nquoting him:\r\n> I recently had made some additional tweaks to the boundary\r\n> conditions of formatting markup; stuff like ({{text}}) wasn't properly\r\n> highlighted.","package":"confluencewiki.vim","4":"confluencewiki.vim","src_id":"21715","5":"21715","creation_date":"1396474615","6":"1396474615"},{"0":"1994","vim_version":"6.0","1":"6.0","script_version":"0.1.0","2":"0.1.0","version_comment":"a lot of improvements made by Ingor Karkat <swdev{AT}ingo-karkat{DOT}de>\r\n\r\n- Added confluenceImage.\r\n- confluenceCode, confluenceQuote and confluenceVerbatim tags are now\r\n  highlighted as tags, not the formatting they create.\r\n- confluenceLink now supports optional labels and tips with different\r\n  highlighting.\r\n- Adjusted confluenceHeading, confluenceHeadingMarker, confluenceList,\r\n  confluenceFixed and confluenceLink highlightings to other wiki syntax\r\n  highlightings.\r\n- BF: confluenceLink is unbounded, i.e. need not be surrounded by whitespace\r\n  etc.\r\n- Added spelling support.\r\n- BF: confluenceHeading only supports 1-6.\r\n- BF: confluenceTag parameter names can also contain '-'; parameter values can\r\n  contain any character except '|' or '}'.\r\n- Expanded highlighting of confluenceTag to highlight (optional) parameters\r\n  and their values, similar to HTML tag attributes.\r\n- confluenceComment tags are now highlighted as tags, not the formatting they\r\n  create.\r\n- BF: No spell error on {HTMLcomment}, {code} and {noformat} tags.\r\n- BF: Applying top-level formatting inside confluenceComment and\r\n  confluenceQuote, (but not for confluenceCode and confluenceVerbatim).\r\n- BF: Allowing optional parameters for confluenceCode and confluenceVerbatim.\r\n- BF: Added 'keepend' for confluenceQuote.\r\n- Added highlighting for confluenceEmoticons.\r\n- BF: Added additional allowed characters after confluenceEmphasis and\r\n  confluenceFixed: !()[]{}\r\n- Added matching and highlighting for confluenceCitation, confluenceStrike,\r\n  confluenceUnderlined, confluenceSuperscript, confluenceSubscript.\r\n- ENH: Escaped (via '\\') markup is not highlighted any more.\r\n- Added confluenceEscaping to highlight the escape character '\\'.\r\n- BF: confluenceSeparator: horizontal ruler must be exactly 4 dashes, but can\r\n  be surrounded by whitespace in the line.\r\n- BF: Emphasis must contain at least one non-emphasis character (i.e. an empty\r\n  emphasis is not rendered). Added after-match atom to\r\n  s:ConfluenceCreateEmphasis().\r\n  Added confluenceSymbols for ndash (--) and mdash (---).\r\n- ENH: Added highlighting for confluenceTableHeader (which can include other\r\n  emphases).\r\n- ENH: confluenceImage now supports highlighting of image link (like a\r\n  confluenceLink) and optional parameter names and values.","3":"a lot of improvements made by Ingor Karkat <swdev{AT}ingo-karkat{DOT}de>\r\n\r\n- Added confluenceImage.\r\n- confluenceCode, confluenceQuote and confluenceVerbatim tags are now\r\n  highlighted as tags, not the formatting they create.\r\n- confluenceLink now supports optional labels and tips with different\r\n  highlighting.\r\n- Adjusted confluenceHeading, confluenceHeadingMarker, confluenceList,\r\n  confluenceFixed and confluenceLink highlightings to other wiki syntax\r\n  highlightings.\r\n- BF: confluenceLink is unbounded, i.e. need not be surrounded by whitespace\r\n  etc.\r\n- Added spelling support.\r\n- BF: confluenceHeading only supports 1-6.\r\n- BF: confluenceTag parameter names can also contain '-'; parameter values can\r\n  contain any character except '|' or '}'.\r\n- Expanded highlighting of confluenceTag to highlight (optional) parameters\r\n  and their values, similar to HTML tag attributes.\r\n- confluenceComment tags are now highlighted as tags, not the formatting they\r\n  create.\r\n- BF: No spell error on {HTMLcomment}, {code} and {noformat} tags.\r\n- BF: Applying top-level formatting inside confluenceComment and\r\n  confluenceQuote, (but not for confluenceCode and confluenceVerbatim).\r\n- BF: Allowing optional parameters for confluenceCode and confluenceVerbatim.\r\n- BF: Added 'keepend' for confluenceQuote.\r\n- Added highlighting for confluenceEmoticons.\r\n- BF: Added additional allowed characters after confluenceEmphasis and\r\n  confluenceFixed: !()[]{}\r\n- Added matching and highlighting for confluenceCitation, confluenceStrike,\r\n  confluenceUnderlined, confluenceSuperscript, confluenceSubscript.\r\n- ENH: Escaped (via '\\') markup is not highlighted any more.\r\n- Added confluenceEscaping to highlight the escape character '\\'.\r\n- BF: confluenceSeparator: horizontal ruler must be exactly 4 dashes, but can\r\n  be surrounded by whitespace in the line.\r\n- BF: Emphasis must contain at least one non-emphasis character (i.e. an empty\r\n  emphasis is not rendered). Added after-match atom to\r\n  s:ConfluenceCreateEmphasis().\r\n  Added confluenceSymbols for ndash (--) and mdash (---).\r\n- ENH: Added highlighting for confluenceTableHeader (which can include other\r\n  emphases).\r\n- ENH: confluenceImage now supports highlighting of image link (like a\r\n  confluenceLink) and optional parameter names and values.","package":"confluencewiki.vim","4":"confluencewiki.vim","src_id":"11306","5":"11306","creation_date":"1251983163","6":"1251983163"},{"0":"1994","vim_version":"6.0","1":"6.0","script_version":"0.0.2","2":"0.0.2","version_comment":"{HTMLcomment} support added","3":"{HTMLcomment} support added","package":"confluencewiki.vim","4":"confluencewiki.vim","src_id":"7507","5":"7507","creation_date":"1187257317","6":"1187257317"},{"0":"1994","vim_version":"6.0","1":"6.0","script_version":"0.0.1","2":"0.0.1","version_comment":"Initial upload","3":"Initial upload","package":"confluencewiki.vim","4":"confluencewiki.vim","src_id":"7506","5":"7506","creation_date":"1187257050","6":"1187257050"}]},"1993":{"script_id":"1993","0":"1993","script_name":"NightVision","1":"NightVision","script_type":"color scheme","2":"color scheme","summary":"Color scheme with dark background","3":"Color scheme with dark background","description":"Low contrast color scheme with dark background.","4":"Low contrast color scheme with dark background.","install_details":"* Place file on .vim\/colors\/ directory\r\n* On a gvim window enter \":color nightVision\"","5":"* Place file on .vim\/colors\/ directory\r\n* On a gvim window enter \":color nightVision\"","first_name":"Dinesh","6":"Dinesh","last_name":".","7":".","releases":[{"0":"1993","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"nightVision.vim","4":"nightVision.vim","src_id":"7504","5":"7504","creation_date":"1187177072","6":"1187177072"}]},"1992":{"script_id":"1992","0":"1992","script_name":"triangle.vim","1":"triangle.vim","script_type":"syntax","2":"syntax","summary":"Syntax highlighting for triangle source files","3":"Syntax highlighting for triangle source files","description":"A basic syntax highlighting script for the triangle language from the book \"Programming Language Processors in Java\".","4":"A basic syntax highlighting script for the triangle language from the book \"Programming Language Processors in Java\".","install_details":"Just as with other syntax files: Copy this to .vim\/syntax\/triangle.vim and add something like\r\n\r\nif has(\"autocmd\")\r\n  au BufNewFile,BufRead *.tri set syntax=triangle\r\nendif\r\n\r\nto your .vimrc .","5":"Just as with other syntax files: Copy this to .vim\/syntax\/triangle.vim and add something like\r\n\r\nif has(\"autocmd\")\r\n  au BufNewFile,BufRead *.tri set syntax=triangle\r\nendif\r\n\r\nto your .vimrc .","first_name":"Nicolas","6":"Nicolas","last_name":"Weber","7":"Weber","releases":[{"0":"1992","vim_version":"5.7","1":"5.7","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"triangle.vim","4":"triangle.vim","src_id":"7500","5":"7500","creation_date":"1187156620","6":"1187156620"}]},"1991":{"script_id":"1991","0":"1991","script_name":"Shell History","1":"Shell History","script_type":"utility","2":"utility","summary":"Autocomplete based upon bash_history","3":"Autocomplete based upon bash_history","description":"If you have previously typed a complicated command into your shell and then want to use it within a shell script this will make it easier to grab\r\n\r\njust start typing a fragment of the command and hit control b\r\n\r\nNote: .bash_history will normally only be written to when you exit a shell\r\n\r\nYou may want to tweak your history settings to gain best possible performance\r\npossibly http:\/\/wooledge.org\/mywiki\/BashFAQ#faq77 (realtime updates...although I haven't tried this)\r\n\r\nThis was just a personal  experiment at vim scripting, please send improvements\/suggestions. \r\n\r\n","4":"If you have previously typed a complicated command into your shell and then want to use it within a shell script this will make it easier to grab\r\n\r\njust start typing a fragment of the command and hit control b\r\n\r\nNote: .bash_history will normally only be written to when you exit a shell\r\n\r\nYou may want to tweak your history settings to gain best possible performance\r\npossibly http:\/\/wooledge.org\/mywiki\/BashFAQ#faq77 (realtime updates...although I haven't tried this)\r\n\r\nThis was just a personal  experiment at vim scripting, please send improvements\/suggestions. \r\n\r\n","install_details":"place the vim file in the plugin folder","5":"place the vim file in the plugin folder","first_name":"Michael","6":"Michael","last_name":"Brown","7":"Brown","releases":[{"0":"1991","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"shell_history.vim","4":"shell_history.vim","src_id":"7499","5":"7499","creation_date":"1187071216","6":"1187071216"}]},"1990":{"script_id":"1990","0":"1990","script_name":"kwiki.vim","1":"kwiki.vim","script_type":"syntax","2":"syntax","summary":"Syntax highlighting for kwiki files","3":"Syntax highlighting for kwiki files","description":"The script is based on the wiki.vim developed by Andreas Kneib <aporia@web.de> and Mathias Panzenb\u00c3\u00b6ck <grosser.meister.morti@gmx.at>.  The formatting rules are mainly derived (with modification) from the perl module Kwiki::Formatter. http:\/\/search.cpan.org\/~ingy\/Kwiki-0.39\/lib\/Kwiki\/Formatter.pm\r\n","4":"The script is based on the wiki.vim developed by Andreas Kneib <aporia@web.de> and Mathias Panzenb\u00c3\u00b6ck <grosser.meister.morti@gmx.at>.  The formatting rules are mainly derived (with modification) from the perl module Kwiki::Formatter. http:\/\/search.cpan.org\/~ingy\/Kwiki-0.39\/lib\/Kwiki\/Formatter.pm\r\n","install_details":"Simply drop the file into your syntax directory ($HOME\/.vim\/syntax) and add one line into your filetype.vim:\r\n\r\n    au BufRead,BufNewFile *.kwiki setf kwiki\r\n\r\n","5":"Simply drop the file into your syntax directory ($HOME\/.vim\/syntax) and add one line into your filetype.vim:\r\n\r\n    au BufRead,BufNewFile *.kwiki setf kwiki\r\n\r\n","first_name":"Ruey-Cheng","6":"Ruey-Cheng","last_name":"Chen","7":"Chen","releases":[{"0":"1990","vim_version":"7.0","1":"7.0","script_version":"0.2","2":"0.2","version_comment":"Rewrite a number of patterns (i.e., kwikiParagraph, kwikiUlist, and kwikiOlist) for efficiency.","3":"Rewrite a number of patterns (i.e., kwikiParagraph, kwikiUlist, and kwikiOlist) for efficiency.","package":"kwiki.vim","4":"kwiki.vim","src_id":"17261","5":"17261","creation_date":"1327045360","6":"1327045360"},{"0":"1990","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"kwiki.vim","4":"kwiki.vim","src_id":"7495","5":"7495","creation_date":"1186986670","6":"1186986670"}]},"1989":{"script_id":"1989","0":"1989","script_name":"gitvimdiff","1":"gitvimdiff","script_type":"utility","2":"utility","summary":"Script to show git diffs in vimdiff format","3":"Script to show git diffs in vimdiff format","description":"This script will show a git diff in vimdiff format. -g will use gvimdiff instead of vimdiff.\r\n\r\nIt creates a temporary file based on the diff output of git diff, and then runs vimdiff (or gvimdiff) against that. On completion it should delete the temporary files.","4":"This script will show a git diff in vimdiff format. -g will use gvimdiff instead of vimdiff.\r\n\r\nIt creates a temporary file based on the diff output of git diff, and then runs vimdiff (or gvimdiff) against that. On completion it should delete the temporary files.","install_details":"The file itself is a bash script, so just make it executable on a Unix-like system.","5":"The file itself is a bash script, so just make it executable on a Unix-like system.","first_name":"Geoff","6":"Geoff","last_name":"Buchan","7":"Buchan","releases":[{"0":"1989","vim_version":"7.0","1":"7.0","script_version":"1.8","2":"1.8","version_comment":"Replace tempfile with mktemp to generate temporary file names. tempfile is deprecated and no longer distributed with the current Fedora, whereas mktemp exists both there and the older Debian installs I use.","3":"Replace tempfile with mktemp to generate temporary file names. tempfile is deprecated and no longer distributed with the current Fedora, whereas mktemp exists both there and the older Debian installs I use.","package":"gitvimdiff","4":"gitvimdiff","src_id":"28055","5":"28055","creation_date":"1653523664","6":"1653523664"},{"0":"1989","vim_version":"7.0","1":"7.0","script_version":"1.7","2":"1.7","version_comment":"Use sed instead of cut to strip a filename out of a line of git status output. Cut was blindly removing 15 columns before, but the git status format changed slightly. sed now simply requires that the line start with \\'\\\\tmodified:\\'.","3":"Use sed instead of cut to strip a filename out of a line of git status output. Cut was blindly removing 15 columns before, but the git status format changed slightly. sed now simply requires that the line start with \\'\\\\tmodified:\\'.","package":"gitvimdiff","4":"gitvimdiff","src_id":"22389","5":"22389","creation_date":"1409439159","6":"1409439159"},{"0":"1989","vim_version":"7.0","1":"7.0","script_version":"1.6","2":"1.6","version_comment":"Fix switch arguments to tempfile, and change temporary file name\r\nto use full filename, not just the last token of it.\r\nThanks to Stefan Heinemann for pointing out the change to tempfile!","3":"Fix switch arguments to tempfile, and change temporary file name\r\nto use full filename, not just the last token of it.\r\nThanks to Stefan Heinemann for pointing out the change to tempfile!","package":"gitvimdiff","4":"gitvimdiff","src_id":"19778","5":"19778","creation_date":"1365359484","6":"1365359484"},{"0":"1989","vim_version":"7.0","1":"7.0","script_version":"1.5","2":"1.5","version_comment":"Bug fix: remove temporary file with file suffix on exit","3":"Bug fix: remove temporary file with file suffix on exit","package":"gitvimdiff","4":"gitvimdiff","src_id":"11271","5":"11271","creation_date":"1251333172","6":"1251333172"},{"0":"1989","vim_version":"7.0","1":"7.0","script_version":"1.3","2":"1.3","version_comment":"Add code to put orignal file suffix on patched file.\r\nThis fixes syntax highlighting for the file.\r\nThanks to Stefan Heinemann for the patch!\r\n","3":"Add code to put orignal file suffix on patched file.\r\nThis fixes syntax highlighting for the file.\r\nThanks to Stefan Heinemann for the patch!\r\n","package":"gitvimdiff","4":"gitvimdiff","src_id":"11259","5":"11259","creation_date":"1251251736","6":"1251251736"},{"0":"1989","vim_version":"7.0","1":"7.0","script_version":"1.2","2":"1.2","version_comment":"Initial upload","3":"Initial upload","package":"gitvimdiff","4":"gitvimdiff","src_id":"7492","5":"7492","creation_date":"1186801850","6":"1186801850"}]},"1988":{"script_id":"1988","0":"1988","script_name":"two2tango","1":"two2tango","script_type":"color scheme","2":"color scheme","summary":"Colorscheme based upon Tango palette","3":"Colorscheme based upon Tango palette","description":"This color scheme is based upon Panos Laganakos' original darktango vimscript #1672 color scheme.\r\nI have improved upon the original scheme by increasing the number of colors used to disambiguate different sytactical structures.  With one exception, the scheme is restricted to colors from the Tango Icon palette \r\nhttp:\/\/tango.freedesktop.org\/Tango_Icon_Theme_Guidelines.  \r\n\r\nSend feedback to NefOaloSr@gPAmaMil.com - NOSPAM","4":"This color scheme is based upon Panos Laganakos' original darktango vimscript #1672 color scheme.\r\nI have improved upon the original scheme by increasing the number of colors used to disambiguate different sytactical structures.  With one exception, the scheme is restricted to colors from the Tango Icon palette \r\nhttp:\/\/tango.freedesktop.org\/Tango_Icon_Theme_Guidelines.  \r\n\r\nSend feedback to NefOaloSr@gPAmaMil.com - NOSPAM","install_details":"Put two2tango.vim inside your .vim\/colors directory.","5":"Put two2tango.vim inside your .vim\/colors directory.","first_name":"erik","6":"erik","last_name":"falor","7":"falor","releases":[{"0":"1988","vim_version":"6.0","1":"6.0","script_version":"1.2","2":"1.2","version_comment":"Thanks to Max Battcher for his suggestion for VisualNOS highlighting.\r\nAdded styling for non-GUI tabline elements.","3":"Thanks to Max Battcher for his suggestion for VisualNOS highlighting.\r\nAdded styling for non-GUI tabline elements.","package":"two2tango.vim","4":"two2tango.vim","src_id":"13054","5":"13054","creation_date":"1274799875","6":"1274799875"},{"0":"1988","vim_version":"7.0","1":"7.0","script_version":"1.1","2":"1.1","version_comment":"Changed Ignore highlight group to blend in with background.","3":"Changed Ignore highlight group to blend in with background.","package":"two2tango.vim","4":"two2tango.vim","src_id":"8125","5":"8125","creation_date":"1199461515","6":"1199461515"}]},"1987":{"script_id":"1987","0":"1987","script_name":"khaki.vim","1":"khaki.vim","script_type":"color scheme","2":"color scheme","summary":"A light colorscheme optimized for gui and 256 color terminals.","3":"A light colorscheme optimized for gui and 256 color terminals.","description":"This colour scheme was created primarily because there seems to be few\r\n(if any) that take the trouble to appear the same in gui and cterm environments.\r\n\r\nSecondly, most cterm colour schemes seem to use excessively strong colours\r\nin psychotic combinations compared to the gui schemes. This scheme\r\nstrives to follow the guidelines described in \"Color Theory for Developers\"\r\n       http:\/\/www.devsource.com\/article2\/0,1895,2069736,00.asp\r\nfor a softer appearance like more modern gui schemes.\r\n\r\nFinally, some terminals render bold and italic fonts badly, so those attributes have been avoided.\r\n\r\nFeatures:\r\n    - Optimized for 256 colour palette, then converted to gui.\r\n    - Identical colour rendition in both gui and cterm environments.\r\n    - Low-contrast colours keep it \"REAL\", avoiding psychotic edit sessions.\r\n    - Avoids use of terminal attributes {bold italic etc}, with the\r\n      exception of 'underline' used with the 'Underlined' group-name.\r\n\r\nTesting:\r\n    Tested with the following programs (256 colour versions), which render identically to gvim:-\r\n        gnu-screen (compiled with --enable-colors256 option)\r\n        xterm\r\n        gnome-terminal\r\n\r\n        konsole (version 1.6.5) renders slightly darker colours for some unknown reason.\r\n            See KDE Bug 138237: Color cube incorrect for xterm-256color mode (patch)\r\n","4":"This colour scheme was created primarily because there seems to be few\r\n(if any) that take the trouble to appear the same in gui and cterm environments.\r\n\r\nSecondly, most cterm colour schemes seem to use excessively strong colours\r\nin psychotic combinations compared to the gui schemes. This scheme\r\nstrives to follow the guidelines described in \"Color Theory for Developers\"\r\n       http:\/\/www.devsource.com\/article2\/0,1895,2069736,00.asp\r\nfor a softer appearance like more modern gui schemes.\r\n\r\nFinally, some terminals render bold and italic fonts badly, so those attributes have been avoided.\r\n\r\nFeatures:\r\n    - Optimized for 256 colour palette, then converted to gui.\r\n    - Identical colour rendition in both gui and cterm environments.\r\n    - Low-contrast colours keep it \"REAL\", avoiding psychotic edit sessions.\r\n    - Avoids use of terminal attributes {bold italic etc}, with the\r\n      exception of 'underline' used with the 'Underlined' group-name.\r\n\r\nTesting:\r\n    Tested with the following programs (256 colour versions), which render identically to gvim:-\r\n        gnu-screen (compiled with --enable-colors256 option)\r\n        xterm\r\n        gnome-terminal\r\n\r\n        konsole (version 1.6.5) renders slightly darker colours for some unknown reason.\r\n            See KDE Bug 138237: Color cube incorrect for xterm-256color mode (patch)\r\n","install_details":"  - Copy khaki.vim to ~\/.vim\/colors\/\r\n\r\n  - Add following lines to ~\/.vimrc\r\n        if !has(\"gui_running\")\r\n            set t_Co=256\r\n        endif\r\n        colorscheme khaki\r\n","5":"  - Copy khaki.vim to ~\/.vim\/colors\/\r\n\r\n  - Add following lines to ~\/.vimrc\r\n        if !has(\"gui_running\")\r\n            set t_Co=256\r\n        endif\r\n        colorscheme khaki\r\n","first_name":"frank","6":"frank","last_name":"baruch","7":"baruch","releases":[{"0":"1987","vim_version":"5.7","1":"5.7","script_version":"1.1","2":"1.1","version_comment":"Bugfix: Changed gui palette intensity (0x8f values should be 0x87).","3":"Bugfix: Changed gui palette intensity (0x8f values should be 0x87).","package":"khaki.vim","4":"khaki.vim","src_id":"7569","5":"7569","creation_date":"1188242471","6":"1188242471"},{"0":"1987","vim_version":"5.7","1":"5.7","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"khaki.vim","4":"khaki.vim","src_id":"7482","5":"7482","creation_date":"1186705525","6":"1186705525"}]},"1986":{"script_id":"1986","0":"1986","script_name":"mosalisp.vim","1":"mosalisp.vim","script_type":"game","2":"game","summary":"lisp interpreter","3":"lisp interpreter","description":"This is a lisp interpreter written in vim script.","4":"This is a lisp interpreter written in vim script.","install_details":"","5":"","first_name":"Yukihiro","6":"Yukihiro","last_name":"Nakadaira","7":"Nakadaira","releases":[{"0":"1986","vim_version":"7.0","1":"7.0","script_version":"1.3","2":"1.3","version_comment":"bug fix.\r\nadded exception handling.","3":"bug fix.\r\nadded exception handling.","package":"mosalisp.vim","4":"mosalisp.vim","src_id":"7526","5":"7526","creation_date":"1187563936","6":"1187563936"},{"0":"1986","vim_version":"7.0","1":"7.0","script_version":"1.2.2","2":"1.2.2","version_comment":"bug fix","3":"bug fix","package":"mosalisp.vim","4":"mosalisp.vim","src_id":"7502","5":"7502","creation_date":"1187174468","6":"1187174468"},{"0":"1986","vim_version":"7.0","1":"7.0","script_version":"1.2.1","2":"1.2.1","version_comment":"bug fix","3":"bug fix","package":"mosalisp.vim","4":"mosalisp.vim","src_id":"7498","5":"7498","creation_date":"1187066342","6":"1187066342"},{"0":"1986","vim_version":"7.0","1":"7.0","script_version":"1.2","2":"1.2","version_comment":"bug fix","3":"bug fix","package":"mosalisp.vim","4":"mosalisp.vim","src_id":"7497","5":"7497","creation_date":"1187018197","6":"1187018197"},{"0":"1986","vim_version":"7.0","1":"7.0","script_version":"1.1","2":"1.1","version_comment":"bug fix and improvement","3":"bug fix and improvement","package":"mosalisp.vim","4":"mosalisp.vim","src_id":"7493","5":"7493","creation_date":"1186888707","6":"1186888707"},{"0":"1986","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"mosalisp.vim","4":"mosalisp.vim","src_id":"7478","5":"7478","creation_date":"1186638512","6":"1186638512"}]},"1985":{"script_id":"1985","0":"1985","script_name":"runtests.vim","1":"runtests.vim","script_type":"utility","2":"utility","summary":"Automatically generate, manage, and run test files for perl source.","3":"Automatically generate, manage, and run test files for perl source.","description":"This is a quick and dirty vim script for automatically generating, managing, and running perl t\/*.t files for any perl file you are currently editing.\r\n\r\nThe idea is to give a perl developer a leg up in creating tests for new or legacy code to give some basic unit tests.  Please note that these tests are just stub tests - it is up to the developer to expand the stub tests to fully exercise the code they're testing.\r\n\r\nIn a module (.pm) file, it looks for a new() constructor and adds a special test to create an object of that package, adds an isa_ok() for the created object, and every subroutine that it finds is called as an method on that object.\r\n\r\nIn a normal perl file (.pl), calls all subroutines as functions in ok() calls.\r\n\r\nAlso has a few extra commands for opening a quick view to the test file, creating a Makefile, which helps run your tests as well as a few extra bonuses such as running code coverage reporting, automatically opening the HTML code coverage report in a local web browser.  Please note that the last element is completely untested and not working on windows or linux - patches welcome :)\r\n\r\nHelp is available after installing:  :help runtests\r\n\r\nIdeas for improvements or other suggestions welcome.","4":"This is a quick and dirty vim script for automatically generating, managing, and running perl t\/*.t files for any perl file you are currently editing.\r\n\r\nThe idea is to give a perl developer a leg up in creating tests for new or legacy code to give some basic unit tests.  Please note that these tests are just stub tests - it is up to the developer to expand the stub tests to fully exercise the code they're testing.\r\n\r\nIn a module (.pm) file, it looks for a new() constructor and adds a special test to create an object of that package, adds an isa_ok() for the created object, and every subroutine that it finds is called as an method on that object.\r\n\r\nIn a normal perl file (.pl), calls all subroutines as functions in ok() calls.\r\n\r\nAlso has a few extra commands for opening a quick view to the test file, creating a Makefile, which helps run your tests as well as a few extra bonuses such as running code coverage reporting, automatically opening the HTML code coverage report in a local web browser.  Please note that the last element is completely untested and not working on windows or linux - patches welcome :)\r\n\r\nHelp is available after installing:  :help runtests\r\n\r\nIdeas for improvements or other suggestions welcome.","install_details":"Move runtests.tgz to ~\/.vim.\r\n\r\nUntar: tar xzvf runtests.tgz","5":"Move runtests.tgz to ~\/.vim.\r\n\r\nUntar: tar xzvf runtests.tgz","first_name":"Kent","6":"Kent","last_name":"Cowgill","7":"Cowgill","releases":[{"0":"1985","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"runtests.tgz","4":"runtests.tgz","src_id":"7472","5":"7472","creation_date":"1186588550","6":"1186588550"}]},"1984":{"script_id":"1984","0":"1984","script_name":"FuzzyFinder","1":"FuzzyFinder","script_type":"utility","2":"utility","summary":"buffer\/file\/command\/tag\/etc explorer with fuzzy matching","3":"buffer\/file\/command\/tag\/etc explorer with fuzzy matching","description":"Repository:\r\n  https:\/\/bitbucket.org\/ns9tks\/vim-fuzzyfinder\/\r\n\r\nIssues:\r\n  http:\/\/bitbucket.org\/ns9tks\/vim-fuzzyfinder\/issues\/\r\n\r\nDownload latest(development) version\r\n  https:\/\/bitbucket.org\/ns9tks\/vim-fuzzyfinder\/get\/tip.zip\r\n\r\nSceenshot:\r\n  Buffer mode:\r\n    http:\/\/cdn.bitbucket.org\/ns9tks\/vim-fuzzyfinder\/downloads\/fuzzyfinder-buffer.png\r\n  File mode (searching from all files in vim runtime directories using abbreviation\/multiple-search)\r\n    http:\/\/cdn.bitbucket.org\/ns9tks\/vim-fuzzyfinder\/downloads\/fuzzyfinder-file-abbrev.png\r\n\r\n\r\n==============================================================================\r\nINTRODUCTION                                                *fuf-introduction*\r\n\r\nFuzzyFinder provides convenient ways to quickly reach the\r\nbuffer\/file\/command\/bookmark\/tag you want. FuzzyFinder searches with the\r\nfuzzy\/partial pattern to which it converted an entered pattern.\r\n\r\n        Entered pattern  Fuzzy pattern   Partial pattern ~\r\n>\r\n        abc              *a*b*c*         *abc*\r\n        dir\/file         dir\/*f*i*l*e*   dir\/*file*\r\n        d*r\/file         d*r\/*f*i*l*e*   d*r\/*file*\r\n        ..\/**\/s          ..\/**\/*s*       ..\/**\/*s*\r\n                         (** allows searching a directory tree.)\r\n<\r\nYou will be happy when:\r\n\r\n        \".\/AhLongLongLongLongLongFile.txt\"\r\n        \".\/AhLongLongLongLongLongName.txt\"\r\n        \".\/OhLongLongLongLongLongFile.txt\"\r\n        \".\/OhLongLongLongLongLongName.txt\" <- you want :O\r\n\r\nType \"ON\" and \"OhLongLongLongLongLongName.txt\" will be selected. :D\r\n\r\nFuzzyFinder can search:\r\n\r\n        - buffers\r\n        - files\r\n        - directories\r\n        - most recently used files\r\n        - files around most recently used files\r\n        - most recently used command-lines\r\n        - bookmarked files\r\n        - bookmarked directories\r\n        - tags\r\n        - files which are included in current tagfiles\r\n        - jump list\r\n        - change list\r\n        - buffer lines\r\n        - quickfix\r\n        - help\r\n\r\nFuzzyFinder also provides APIs to use its system of searching files or\r\nselecting items.\r\n\r\nFuzzyFinder supports multibyte characters.\r\n\r\n\r\n==============================================================================\r\nINSTALLATION                                                *fuf-installation*\r\n\r\nPut all files into your runtime directory. If you have the zip file, extract\r\nit to your runtime directory.\r\n\r\nYou should place the files as follows:\r\n>\r\n        <your runtime directory>\/plugin\/fuf.vim\r\n        <your runtime directory>\/doc\/fuf.txt\r\n        ...\r\n<\r\nIf you are disgusted to make your runtime directory confused with a lot of\r\nplugins, put each of the plugins into a directory individually and just add\r\nthe directory path to 'runtimepath'. It's easy to uninstall plugins.\r\n\r\nThen update your help tags files to enable help for this plugin. See\r\n|add-local-help| for details.\r\n\r\nRequirements: ~\r\n\r\n- L9 library (vimscript #3252)\r\n\r\n\r\n==============================================================================\r\nUSAGE                                                              *fuf-usage*\r\n\r\nYou can launch FuzzyFinder by the following commands:\r\n\r\n         Command           Mode ~\r\n        |:FufBuffer|       - Buffer mode (|fuf-buffer-mode|)\r\n        |:FufFile|         - File mode (|fuf-file-mode|)\r\n        |:FufCoverageFile| - Coverage-File mode (|fuf-coveragefile-mode|)\r\n        |:FufDir|          - Directory mode (|fuf-dir-mode|)\r\n        |:FufMruFile|      - MRU-File mode (|fuf-mrufile-mode|)\r\n        |:FufMruCmd|       - MRU-Command mode (|fuf-mrucmd-mode|)\r\n        |:FufBookmarkFile| - Bookmark-File mode (|fuf-bookmarkfile-mode|)\r\n        |:FufBookmarkDir|  - Bookmark-Dir mode (|fuf-bookmarkdir-mode|)\r\n        |:FufTag|          - Tag mode (|fuf-tag-mode|)\r\n        |:FufBufferTag|    - Buffer-Tag mode (|fuf-buffertag-mode|)\r\n        |:FufTaggedFile|   - Tagged-File mode (|fuf-taggedfile-mode|)\r\n        |:FufJumpList|     - Jump-List mode (|fuf-jumplist-mode|)\r\n        |:FufChangeList|   - Change-List mode (|fuf-changelist-mode|)\r\n        |:FufQuickfix|     - Quickfix mode (|fuf-quickfix-mode|)\r\n        |:FufLine|         - Line mode (|fuf-line-mode|)\r\n        |:FufHelp|         - Help mode (|fuf-help-mode|)\r\n\r\nIt is recommended to map these commands.\r\n\r\nThese commands open 1-line buffer to enter search pattern and start insert\r\nmode.\r\n\r\nFuzzyFinder searchs for matching items with an entered pattern and shows them\r\nin a completion menu. For more details on pattern matching, see\r\n|fuf-search-patterns|.\r\n\r\nIf there are a lot of matching items, FuzzyFinder limits the number of\r\nenumerating items (|g:fuf_enumeratingLimit|) to speed up a response time, and\r\nhighlights the pattern with \"Error\" group.\r\n\r\nThe first item in the completion menu will be selected automatically.\r\n\r\nTyping <C-w> deletes one block of an entered pattern before the cursor, like a\r\ndirectory name.\r\n\r\nwith <C-s> (|g:fuf_keyPrevPattern|) and <C-^> (|g:fuf_keyNextPattern|), You\r\ncan recall patterns which have been entered before from history.\r\n\r\nYou can open a selected item in various ways:\r\n\r\n        <CR>  (|g:fuf_keyOpen|)        - opens in a previous window.\r\n        <C-j> (|g:fuf_keyOpenSplit|)   - opens in a split window.\r\n        <C-k> (|g:fuf_keyOpenVsplit|)  - opens in a vertical-split window.\r\n        <C-l> (|g:fuf_keyOpenTabpage|) - opens in a new tab page.\r\n\r\nTo cancel and return to previous window, just leave Insert mode.\r\n\r\nWith <C-\\><C-\\> (|g:fuf_keySwitchMatching|), You can switch search method\r\nbetween fuzzy matching and partial matching.\r\n\r\nWith <C-t> (|g:fuf_keyNextMode|) and <C-y> (|g:fuf_keyPrevMode|), You can\r\nswitch current mode without leaving Insert mode .\r\n\r\nYou can preview selected item with <C-@> (|g:fuf_keyPreview|) in some modes.\r\nRepeating the key on the same item shows another information. The height\r\nof command-line area is changed to |g:fuf_previewHeight| when you launch a\r\nmode supporting preview. This feature is available when |g:fuf_previewHeight|\r\nis not 0.\r\n\r\n\r\n==============================================================================\r\nMODES                                                              *fuf-modes*\r\n\r\n                                                             *fuf-buffer-mode*\r\nBuffer mode ~\r\n\r\nThis mode provides an interface to select a buffer from a list of existing\r\nbuffers and open it.\r\n\r\nPress <C-]> (|g:fuf_buffer_keyDelete|) in this mode and selected buffer will\r\nbe deleted.\r\n\r\n                                                               *fuf-file-mode*\r\nFile mode ~\r\n\r\nThis mode provides an interface to search a file tree for a file and open it.\r\n\r\n                                                       *fuf-coveragefile-mode*\r\nCoverage-File mode ~\r\n\r\nThis mode provides an interface to select a file from all files of a preset\r\ncoverage and open it.\r\n\r\nBy default, This mode lists all files under the current working directory\r\nrecursively. (|g:fuf_coveragefile_globPatterns|)\r\n\r\nIf you want to search other coverage, execute |FufCoverageFileRegister|\r\ncommand to register new search coverage and |FufCoverageFileChange| command to\r\nchoose a search coverage and launch Coverage-File mode.\r\n\r\nIn addition, there is another way to change a search coverage with\r\n|fuf#setOneTimeVariables()| function.\r\n\r\nExample: search only .h and .c files:\r\n>\r\n        call fuf#setOneTimeVariables(['g:fuf_coveragefile_globPatterns', ['**\/*.h', '**\/*.c']])\r\n              \\ | FufCoverageFile\r\n<\r\nExample: search your home directory in addition to the default coverage:\r\n>\r\n        call fuf#setOneTimeVariables(['g:fuf_coveragefile_globPatterns', g:fuf_coveragefile_globPatterns + ['~\/**\/.*', '~\/**\/*']])\r\n              \\ | FufCoverageFile\r\n<\r\n\r\n                                                                *fuf-dir-mode*\r\nDirectory mode ~\r\n\r\nThis mode provides an interface to search a file tree for a directory and\r\nchange the current directory.\r\n\r\n                                                            *fuf-mrufile-mode*\r\nMRU-File mode ~\r\n\r\nThis mode provides an interface to select a file from the most recently used\r\nfiles and open it.\r\n\r\nPress <C-]> (|g:fuf_mrufile_keyExpand|) in this mode and files around the most\r\nrecently used files are listed. Each time the key is pressed, the search range\r\nare expanded one level along the directory tree upwardly\/downwardly.\r\n\r\nThis mode is set to disable by default (|g:fuf_modesDisable|) because\r\nprocesses for this mode in |BufEnter| and |BufWritePost| could cause\r\nPerformance issue.\r\n\r\nSee also: |FufMruFileInCwd|\r\n\r\n                                                             *fuf-mrucmd-mode*\r\nMRU-Command mode ~\r\n\r\nThis mode provides an interface to select a command from the most recently\r\nused commands and execute it.\r\n\r\nThis mode is set to disable by default (|g:fuf_modesDisable|) because mapping\r\n<CR> of Command-line mode required by this mode has side effects.\r\n\r\n                                                       *fuf-bookmarkfile-mode*\r\nBookmark-File mode ~\r\n\r\nThis mode provides an interface to select one of the bookmarks you have added\r\nbeforehand and jump there.\r\n\r\nYou can add a cursor line to bookmarks by |:FufBookmarkFileAdd| command.\r\nExecute that command and you will be prompted to enter a bookmark name.\r\n\r\nFuzzyFinder adjusts a line number for jump. If a line of bookmarked position\r\ndoes not match to a pattern when the bookmark was added, FuzzyFinder searches\r\na matching line around bookmarked position. So you can jump to a bookmarked\r\nline even if the line is out of bookmarked position. If you want to jump to\r\nbookmarked line number without the adjustment, set\r\n|g:fuf_bookmarkfile_searchRange| option to 0.\r\n\r\nPress <C-]> (|g:fuf_bookmarkfile_keyDelete|) in this mode and selected\r\nbookmark will be deleted.\r\n\r\n                                                        *fuf-bookmarkdir-mode*\r\nBookmark-Dir mode ~\r\n\r\nThis mode provides an interface to select one of the bookmarks you have added\r\nbeforehand and change the current directory.\r\n\r\nYou can add a directory to bookmarks by |:FufBookmarkDirAdd| command. Execute\r\nthat command and you will be prompted to enter a directory path and  a\r\nbookmark name.\r\n\r\nPress <C-]> (|g:fuf_bookmarkdir_keyDelete|) in this mode and selected bookmark\r\nwill be deleted.\r\n\r\n                                                                *fuf-tag-mode*\r\nTag mode ~\r\n\r\nThis mode provides an interface to select a tag and jump to the definition of\r\nit.\r\n\r\nFollowing mapping is a replacement for <C-]>:\r\n>\r\n        noremap <silent> <C-]> :FufTagWithCursorWord!<CR>\r\n<\r\n\r\n                                                          *fuf-buffertag-mode*\r\nBuffer-Tag mode ~\r\n\r\nThis mode provides an interface to select a tag of current buffer or all\r\nbuffers and jump to the definition of it.\r\n\r\nTag list is instantly created when FuzzyFinder is launched, so there is no\r\nneed to make tags file in advance.\r\n\r\n|FufBufferTag| covers current buffer and |FufBufferTagAll| covers all buffers.\r\n\r\nFollowing mapping is a replacement for <C-]>:\r\n>\r\n        nnoremap <silent> <C-]> :FufBufferTagWithCursorWord!<CR>\r\n        vnoremap <silent> <C-]> :FufBufferTagAllWithSelectedText!<CR>\r\n<\r\nor\r\n>\r\n        nnoremap <silent> <C-]> :FufBufferTagAllWithCursorWord!<CR>\r\n        vnoremap <silent> <C-]> :FufBufferTagAllWithSelectedText!<CR>\r\n<\r\nThis mode is inspired by taglist.vim (vimscript #273) and refered its codes.\r\n\r\n                                                         *fuf-taggedfile-mode*\r\nTagged-File mode ~\r\n\r\nThis mode provides an interface to select one of the files which are included\r\nin current tagfiles and open it.\r\n\r\n                                                           *fuf-jumplist-mode*\r\nJump-List mode ~\r\n\r\nThis mode provides an interface to select one from the |jumplist| of the\r\ncurrent window and jump there.\r\n\r\n                                                         *fuf-changelist-mode*\r\nChange-List mode ~\r\n\r\nThis mode provides an interface to select one from the |changelist| of the\r\ncurrent buffer and jump there.\r\n\r\n                                                           *fuf-quickfix-mode*\r\nQuickfix mode ~\r\n\r\nThis mode provides an interface to select one from the |quickfix| list and\r\njump there.\r\n\r\n                                                               *fuf-line-mode*\r\nLine mode ~\r\n\r\nThis mode provides an interface to select a line from current buffer and jump\r\nthere.\r\n\r\n                                                               *fuf-help-mode*\r\nHelp mode ~\r\n\r\nThis mode provides an interface to select a help tag and jump to the help\r\npage.\r\n\r\n                                                          *fuf-givenfile-mode*\r\nGiven-File mode ~\r\n\r\nThis mode provides an API to open a selected file from a given list.\r\n\r\nAPI function:\r\n>\r\n        function fuf#givenfile#launch(\r\n              \\ initialPattern, partialMatching, prompt, items)\r\n<\r\n        initialPattern  - String which is inserted after launching\r\n                          FuzzyFinder.\r\n        partialMatching - If non-zero, enable partial matching instead of\r\n                          fuzzy matching.\r\n        prompt          - Prompt string\r\n        items           - List of items.\r\n\r\nExample of use:\r\n>\r\n        \" Open one of your dotfiles.\r\n        call fuf#givenfile#launch('', 0, '>', split(glob('~\/.*'), \"\\n\"))\r\n<\r\n\r\n                                                           *fuf-givendir-mode*\r\nGiven-Directory mode ~\r\n\r\nThis mode provides an API to change current working directory to a selected\r\none from a given list.\r\n\r\nAPI function:\r\n>\r\n        function fuf#givendir#launch(\r\n              \\ initialPattern, partialMatching, prompt, items)\r\n<\r\n        initialPattern  - String which is inserted after launching\r\n                          FuzzyFinder.\r\n        partialMatching - If non-zero, enable partial matching instead of\r\n                          fuzzy matching.\r\n        prompt          - Prompt string\r\n        items           - List of items.\r\n\r\n\r\nExample of use:\r\n>\r\n        \" Change current working directory to one of your runtime directory.\r\n        call fuf#givendir#launch('', 0, '>', split(&runtimepath, ','))\r\n<\r\n\r\n                                                           *fuf-givencmd-mode*\r\nGiven-Command mode ~\r\n\r\nThis mode provides an API to execute a selected command from a given list.\r\n\r\nA selected command is executed by |feedkeys()|, so it is able to emulate a\r\nseries of key input in Normal mode.\r\n\r\nAPI function:\r\n>\r\n        function fuf#givencmd#launch(\r\n              \\ initialPattern, partialMatching, prompt, items)\r\n<\r\n        initialPattern  - String which is inserted after launching\r\n                          FuzzyFinder.\r\n        partialMatching - If non-zero, enable partial matching instead of\r\n                          fuzzy matching.\r\n        prompt          - Prompt string\r\n        items           - List of items.\r\n\r\n\r\nExample of use:\r\n>\r\n        function GetAllCommands()\r\n          redir => commands\r\n          silent command\r\n          redir END\r\n          return map((split(commands, \"\\n\")[3:]),\r\n              \\      '\":\" . matchstr(v:val, ''^....\\zs\\S*'')')\r\n        endfunction\r\n\r\n        \" execute one of the user-defined commands \r\n        call fuf#givencmd#launch('', 0, '>', GetAllCommands())\r\n\r\n<\r\n\r\n                                                       *fuf-callbackfile-mode*\r\nCallback-File mode ~\r\n\r\nThis mode provides an API to find and get a file path which is selected by an\r\nuser.\r\n\r\nAPI function:\r\n>\r\n        function fuf#callbackfile#launch(\r\n              \\ initialPattern, partialMatching, prompt, exclude, listener)\r\n<\r\n        initialPattern  - String which is inserted after launching\r\n                          FuzzyFinder.\r\n        partialMatching - If non-zero, enable partial matching instead of\r\n                          fuzzy matching.\r\n        prompt          - Prompt string.\r\n        exclude         - Regexp pattern for items which you want to exclude\r\n                          from completion list.\r\n        listener        - |Dictionary| which has 'onComplete' and 'onAbort'.\r\n                          They are called at the end of FuzzyFinder.\r\n                          listener.onComplete(item, method) is called with 2\r\n                          arguments which are a name of selected item and a\r\n                          number of open method when completed.\r\n                          listener.onAbort() is called when aborted.\r\n\r\nExample of use:\r\n>\r\n        let listener = {}\r\n\r\n        function listener.onComplete(item, method)\r\n          echo \"Item: \" . a:item . \"\\nMethod: \" . a:method\r\n        endfunction\r\n\r\n        function listener.onAbort()\r\n          echo \"Abort\"\r\n        endfunction\r\n\r\n        \" Find a file from current working directory.\r\n        call fuf#callbackfile#launch('', 0, '>', '', listener)\r\n\r\n        \" Find a file from home directory.\r\n        call fuf#callbackfile#launch('~\/', 0, '>', '', listener)\r\n<\r\n\r\n                                                       *fuf-callbackitem-mode*\r\nCallback-Item mode ~\r\n\r\nThis mode provides an API to get an item which is selected from a given list\r\nby an user.\r\n\r\nAPI function:\r\n>\r\n        function fuf#callbackitem#launch(\r\n              \\ initialPattern, partialMatching, prompt, listener, items, forPath)\r\n<\r\n        initialPattern  - String which is inserted after launching\r\n                          FuzzyFinder.\r\n        partialMatching - If non-zero, enable partial matching instead of\r\n                          fuzzy matching.\r\n        prompt          - Prompt string\r\n        listener        - |Dictionary| which has 'onComplete' and 'onAbort'.\r\n                          They are called at the end of FuzzyFinder.\r\n                          listener.onComplete(item, method) is called with 2\r\n                          arguments which are a name of selected item and a\r\n                          number of open method when completed.\r\n                          listener.onAbort() is called when aborted.\r\n        items           - List of items.\r\n        forPath         - If non-zero, use a matching method for files.\r\n\r\nExample of use:\r\n>\r\n        let listener = {}\r\n\r\n        function listener.onComplete(item, method)\r\n          echo \"Item: \" . a:item . \"\\nMethod: \" . a:method\r\n        endfunction\r\n\r\n        function listener.onAbort()\r\n          echo \"Abort\"\r\n        endfunction\r\n\r\n        \" Select an item from a given list.\r\n        call fuf#callbackitem#launch('', 0, '>', listener, ['ed', 'vi', 'vim'], 0)\r\n\r\n        \" Select a file from a given list.\r\n        call fuf#callbackitem#launch('', 0, '>', listener, ['..\/foo\/bar', 'baz'], 1)\r\n<\r\n\r\n==============================================================================\r\nDETAILED TOPICS                                          *fuf-detailed-topics*\r\n\r\n                     *fuf-setting-one-time-option* *fuf#setOneTimeVariables()*\r\nSetting One-Time Options ~\r\n\r\nIf you want to set one-time options only for the next FuzzyFinder,\r\n|fuf#setOneTimeVariables()| function will be of help. This function is used as\r\nfollows:\r\n>\r\n        call fuf#setOneTimeVariables(['g:fuf_ignoreCase', 0], ['&lines', 50])\r\n<\r\nThis function takes 0 or more arguments and each of them is a pair of a\r\nvariable name and its value. Specified options will be set practically next\r\ntime FuzzyFinder is launched, and restored when FuzzyFinder is closed.\r\n\r\n                                                         *fuf-search-patterns*\r\nSearch Patterns ~\r\n\r\nYou can enter one primary pattern and zero or more refining patterns as search\r\npatterns. An entered pattern is separated by \";\" (|g:fuf_patternSeparator|),\r\nand the first pattern is a primary pattern and the rest of patterns is a\r\nrefining pattern.\r\n>\r\n                   primary    refining  refining\r\n                 |----------| |-------| |----|\r\n        >MruFile>bookmark.vim;autoload\/;\/home\/\r\n<\r\nA refining pattern is used to narrow down the list of matching items by\r\nanother pattern.\r\n\r\nWith a primary pattern, FuzzyFinder does fuzzy matching or partial matching,\r\nwhich you specified. With a refining pattern, FuzzyFinder does partial\r\nmatching by default. (|g:fuf_fuzzyRefining|)\r\n\r\nWhen you enter a number as refining pattern, it also can match the index of\r\neach item.\r\n\r\nIn a mode which targets a static set of file paths (such as Buffer or MRU-File\r\nmode, not File or Directory) and |g:fuf_splitPathMatching| is non-zero,\r\nmatching with a primary pattern is divided into head part and tail part and\r\ndone individually.\r\n>\r\n          head   tail\r\n        |------||-----|\r\n        foo\/bar\/baz.vim\r\n\r\n        fuzzy matching example:\r\n        +----------------+---------+---------+---------+\r\n        | item \\ pattern | foo\/bar | foo\/    | bar     |\r\n        +----------------+---------+---------+---------+\r\n        | foo\/bar        |   match |   match |   match |\r\n        | foo\/abc        | unmatch |   match | unmatch |\r\n        | abc\/bar        | unmatch | unmatch |   match |\r\n        | foobar         | unmatch | unmatch |   match |\r\n        | foooo\/barrrr   |   match |   match |   match |\r\n        | foooo\/fooooo   | unmatch |   match | unmatch |\r\n        +----------------+---------+---------+---------+\r\n<\r\nrefining pattern can match anywhere on each path in the above case.\r\n\r\n                                             *fuf-sorting-of-completion-items*\r\nSorting Of Completion Items ~\r\n\r\nFuzzyFinder sorts completion items with some rules.\r\n\r\nAn item, one part of which is matched with a whole pattern, is placed upper.\r\nE.g., with the pattern \"bc\", the item \"abc\" is placed upper than \"bac\".\r\n\r\nIn the above case, items, each having matching part at the head of itself, are\r\nplaced upper than others. E.g., with the pattern \"foo\", the item \"foobar\" is\r\nplaced upper than \"foobarbaz\".\r\n\r\nAnd the shorter the length of the item after matching position puts it higher.\r\nE.g., with the pattern \"bar\", the item \"foobar\" is placed upper than\r\n\"foobarbaz\".\r\n\r\nIf a pattern matches an item at only word boundaries of it, the item is placed\r\nupper. E.g., with a pattern \"fb\", items such as \"fooBarBaz\" and \"foo_bar_baz\"\r\nis placed upper.\r\n\r\nPlus, FuzzyFinder has a learning system. An item which has been completed in\r\nthe past with current pattern is placed upper.\r\n\r\n                                                          *fuf-reusing-window*\r\nReusing Of A Window Containing Target Buffer\/File ~\r\n\r\nIf a window containing target buffer is found in current tab page when\r\nFuzzyFinder is going to open the buffer in a split new window, move to it. If\r\na window containing target buffer is found in other tab page when FuzzyFinder\r\nis going to open the buffer in a new tab page, move to it.\r\n\r\nYou can disable that feature via 'reuse_window' options if always want to open\r\na buffer in a new window.\r\n\r\n                                                             *fuf-hiding-menu*\r\nTo Hide The Completion Menu Temporarily In FuzzyFinder ~\r\n\r\nYou can close it by <C-e> and reopen it by <C-x><C-o>.\r\n\r\n                                      *fuf-abbreviation* *fuf-multiple-search*\r\nAbbreviations And Multiple Search ~\r\n\r\nYou can use abbreviations and multiple search in all modes by setting\r\n|g:fuf_abbrevMap| option.\r\n\r\nFor example, set as below:\r\n>\r\n        let g:fuf_abbrevMap = {\r\n              \\   \"^doc:\" : [\r\n              \\     \"~\/project\/**\/doc\/\",\r\n              \\     \".vim\/doc\/\",\r\n              \\   ],\r\n              \\ }\r\n<\r\nand enter \"doc:txt\" in File mode, then FuzzyFinder searches by the following\r\npatterns:\r\n\r\n        \"~\/project\/**\/doc\/*t*x*t*\"\r\n        \".vim\/doc\/*t*x*t*\"\r\n\r\nand show concatenated search results.\r\n\r\n                                                               *fuf-data-file*\r\nData File ~\r\n\r\nFuzzyFinder writes completion statistics, MRU data, bookmark, etc to files\r\nunder |g:fuf_dataDir|.\r\n\r\n|:FufEditDataFile| command is helpful in editing your data files. This command\r\nreads the data file in new unnamed buffer. Write the buffer and the data file\r\nwill be updated.\r\n\r\n                                                                   *fuf-cache*\r\nCache ~\r\n\r\nOnce a cache was created, It is not automatically updated to speed up the\r\nresponse time by default. To update it, use |:FufRenewCache| command.\r\n\r\n                                                            *fuf-dot-sequence*\r\nGoing Up Parent Directories With Dot Sequence ~\r\n\r\nYou can go up parent directories with entering dot sequence. Dot sequence\r\nafter a path separator is expanded to \"..\/\" sequence.\r\n\r\n        Dot sequence    Expanded pattern ~\r\n        \/..             \/..\/\r\n        \/...            \/..\/..\/\r\n        \/....           \/..\/..\/..\/\r\n\r\n                                                         *fuf-how-to-add-mode*\r\nHow To Add Mode ~\r\n\r\nTo add \"mymode\" mode, put the source file at autoload\/fuf\/mymode.vim and call\r\nfuf#addMode(\"mymode\") .\r\n\r\n                                                                  *fuf-migemo*\r\nWhat Is Migemo ~\r\n\r\nMigemo is a search method for Japanese language.\r\n\r\n\r\n==============================================================================\r\n","4":"Repository:\r\n  https:\/\/bitbucket.org\/ns9tks\/vim-fuzzyfinder\/\r\n\r\nIssues:\r\n  http:\/\/bitbucket.org\/ns9tks\/vim-fuzzyfinder\/issues\/\r\n\r\nDownload latest(development) version\r\n  https:\/\/bitbucket.org\/ns9tks\/vim-fuzzyfinder\/get\/tip.zip\r\n\r\nSceenshot:\r\n  Buffer mode:\r\n    http:\/\/cdn.bitbucket.org\/ns9tks\/vim-fuzzyfinder\/downloads\/fuzzyfinder-buffer.png\r\n  File mode (searching from all files in vim runtime directories using abbreviation\/multiple-search)\r\n    http:\/\/cdn.bitbucket.org\/ns9tks\/vim-fuzzyfinder\/downloads\/fuzzyfinder-file-abbrev.png\r\n\r\n\r\n==============================================================================\r\nINTRODUCTION                                                *fuf-introduction*\r\n\r\nFuzzyFinder provides convenient ways to quickly reach the\r\nbuffer\/file\/command\/bookmark\/tag you want. FuzzyFinder searches with the\r\nfuzzy\/partial pattern to which it converted an entered pattern.\r\n\r\n        Entered pattern  Fuzzy pattern   Partial pattern ~\r\n>\r\n        abc              *a*b*c*         *abc*\r\n        dir\/file         dir\/*f*i*l*e*   dir\/*file*\r\n        d*r\/file         d*r\/*f*i*l*e*   d*r\/*file*\r\n        ..\/**\/s          ..\/**\/*s*       ..\/**\/*s*\r\n                         (** allows searching a directory tree.)\r\n<\r\nYou will be happy when:\r\n\r\n        \".\/AhLongLongLongLongLongFile.txt\"\r\n        \".\/AhLongLongLongLongLongName.txt\"\r\n        \".\/OhLongLongLongLongLongFile.txt\"\r\n        \".\/OhLongLongLongLongLongName.txt\" <- you want :O\r\n\r\nType \"ON\" and \"OhLongLongLongLongLongName.txt\" will be selected. :D\r\n\r\nFuzzyFinder can search:\r\n\r\n        - buffers\r\n        - files\r\n        - directories\r\n        - most recently used files\r\n        - files around most recently used files\r\n        - most recently used command-lines\r\n        - bookmarked files\r\n        - bookmarked directories\r\n        - tags\r\n        - files which are included in current tagfiles\r\n        - jump list\r\n        - change list\r\n        - buffer lines\r\n        - quickfix\r\n        - help\r\n\r\nFuzzyFinder also provides APIs to use its system of searching files or\r\nselecting items.\r\n\r\nFuzzyFinder supports multibyte characters.\r\n\r\n\r\n==============================================================================\r\nINSTALLATION                                                *fuf-installation*\r\n\r\nPut all files into your runtime directory. If you have the zip file, extract\r\nit to your runtime directory.\r\n\r\nYou should place the files as follows:\r\n>\r\n        <your runtime directory>\/plugin\/fuf.vim\r\n        <your runtime directory>\/doc\/fuf.txt\r\n        ...\r\n<\r\nIf you are disgusted to make your runtime directory confused with a lot of\r\nplugins, put each of the plugins into a directory individually and just add\r\nthe directory path to 'runtimepath'. It's easy to uninstall plugins.\r\n\r\nThen update your help tags files to enable help for this plugin. See\r\n|add-local-help| for details.\r\n\r\nRequirements: ~\r\n\r\n- L9 library (vimscript #3252)\r\n\r\n\r\n==============================================================================\r\nUSAGE                                                              *fuf-usage*\r\n\r\nYou can launch FuzzyFinder by the following commands:\r\n\r\n         Command           Mode ~\r\n        |:FufBuffer|       - Buffer mode (|fuf-buffer-mode|)\r\n        |:FufFile|         - File mode (|fuf-file-mode|)\r\n        |:FufCoverageFile| - Coverage-File mode (|fuf-coveragefile-mode|)\r\n        |:FufDir|          - Directory mode (|fuf-dir-mode|)\r\n        |:FufMruFile|      - MRU-File mode (|fuf-mrufile-mode|)\r\n        |:FufMruCmd|       - MRU-Command mode (|fuf-mrucmd-mode|)\r\n        |:FufBookmarkFile| - Bookmark-File mode (|fuf-bookmarkfile-mode|)\r\n        |:FufBookmarkDir|  - Bookmark-Dir mode (|fuf-bookmarkdir-mode|)\r\n        |:FufTag|          - Tag mode (|fuf-tag-mode|)\r\n        |:FufBufferTag|    - Buffer-Tag mode (|fuf-buffertag-mode|)\r\n        |:FufTaggedFile|   - Tagged-File mode (|fuf-taggedfile-mode|)\r\n        |:FufJumpList|     - Jump-List mode (|fuf-jumplist-mode|)\r\n        |:FufChangeList|   - Change-List mode (|fuf-changelist-mode|)\r\n        |:FufQuickfix|     - Quickfix mode (|fuf-quickfix-mode|)\r\n        |:FufLine|         - Line mode (|fuf-line-mode|)\r\n        |:FufHelp|         - Help mode (|fuf-help-mode|)\r\n\r\nIt is recommended to map these commands.\r\n\r\nThese commands open 1-line buffer to enter search pattern and start insert\r\nmode.\r\n\r\nFuzzyFinder searchs for matching items with an entered pattern and shows them\r\nin a completion menu. For more details on pattern matching, see\r\n|fuf-search-patterns|.\r\n\r\nIf there are a lot of matching items, FuzzyFinder limits the number of\r\nenumerating items (|g:fuf_enumeratingLimit|) to speed up a response time, and\r\nhighlights the pattern with \"Error\" group.\r\n\r\nThe first item in the completion menu will be selected automatically.\r\n\r\nTyping <C-w> deletes one block of an entered pattern before the cursor, like a\r\ndirectory name.\r\n\r\nwith <C-s> (|g:fuf_keyPrevPattern|) and <C-^> (|g:fuf_keyNextPattern|), You\r\ncan recall patterns which have been entered before from history.\r\n\r\nYou can open a selected item in various ways:\r\n\r\n        <CR>  (|g:fuf_keyOpen|)        - opens in a previous window.\r\n        <C-j> (|g:fuf_keyOpenSplit|)   - opens in a split window.\r\n        <C-k> (|g:fuf_keyOpenVsplit|)  - opens in a vertical-split window.\r\n        <C-l> (|g:fuf_keyOpenTabpage|) - opens in a new tab page.\r\n\r\nTo cancel and return to previous window, just leave Insert mode.\r\n\r\nWith <C-\\><C-\\> (|g:fuf_keySwitchMatching|), You can switch search method\r\nbetween fuzzy matching and partial matching.\r\n\r\nWith <C-t> (|g:fuf_keyNextMode|) and <C-y> (|g:fuf_keyPrevMode|), You can\r\nswitch current mode without leaving Insert mode .\r\n\r\nYou can preview selected item with <C-@> (|g:fuf_keyPreview|) in some modes.\r\nRepeating the key on the same item shows another information. The height\r\nof command-line area is changed to |g:fuf_previewHeight| when you launch a\r\nmode supporting preview. This feature is available when |g:fuf_previewHeight|\r\nis not 0.\r\n\r\n\r\n==============================================================================\r\nMODES                                                              *fuf-modes*\r\n\r\n                                                             *fuf-buffer-mode*\r\nBuffer mode ~\r\n\r\nThis mode provides an interface to select a buffer from a list of existing\r\nbuffers and open it.\r\n\r\nPress <C-]> (|g:fuf_buffer_keyDelete|) in this mode and selected buffer will\r\nbe deleted.\r\n\r\n                                                               *fuf-file-mode*\r\nFile mode ~\r\n\r\nThis mode provides an interface to search a file tree for a file and open it.\r\n\r\n                                                       *fuf-coveragefile-mode*\r\nCoverage-File mode ~\r\n\r\nThis mode provides an interface to select a file from all files of a preset\r\ncoverage and open it.\r\n\r\nBy default, This mode lists all files under the current working directory\r\nrecursively. (|g:fuf_coveragefile_globPatterns|)\r\n\r\nIf you want to search other coverage, execute |FufCoverageFileRegister|\r\ncommand to register new search coverage and |FufCoverageFileChange| command to\r\nchoose a search coverage and launch Coverage-File mode.\r\n\r\nIn addition, there is another way to change a search coverage with\r\n|fuf#setOneTimeVariables()| function.\r\n\r\nExample: search only .h and .c files:\r\n>\r\n        call fuf#setOneTimeVariables(['g:fuf_coveragefile_globPatterns', ['**\/*.h', '**\/*.c']])\r\n              \\ | FufCoverageFile\r\n<\r\nExample: search your home directory in addition to the default coverage:\r\n>\r\n        call fuf#setOneTimeVariables(['g:fuf_coveragefile_globPatterns', g:fuf_coveragefile_globPatterns + ['~\/**\/.*', '~\/**\/*']])\r\n              \\ | FufCoverageFile\r\n<\r\n\r\n                                                                *fuf-dir-mode*\r\nDirectory mode ~\r\n\r\nThis mode provides an interface to search a file tree for a directory and\r\nchange the current directory.\r\n\r\n                                                            *fuf-mrufile-mode*\r\nMRU-File mode ~\r\n\r\nThis mode provides an interface to select a file from the most recently used\r\nfiles and open it.\r\n\r\nPress <C-]> (|g:fuf_mrufile_keyExpand|) in this mode and files around the most\r\nrecently used files are listed. Each time the key is pressed, the search range\r\nare expanded one level along the directory tree upwardly\/downwardly.\r\n\r\nThis mode is set to disable by default (|g:fuf_modesDisable|) because\r\nprocesses for this mode in |BufEnter| and |BufWritePost| could cause\r\nPerformance issue.\r\n\r\nSee also: |FufMruFileInCwd|\r\n\r\n                                                             *fuf-mrucmd-mode*\r\nMRU-Command mode ~\r\n\r\nThis mode provides an interface to select a command from the most recently\r\nused commands and execute it.\r\n\r\nThis mode is set to disable by default (|g:fuf_modesDisable|) because mapping\r\n<CR> of Command-line mode required by this mode has side effects.\r\n\r\n                                                       *fuf-bookmarkfile-mode*\r\nBookmark-File mode ~\r\n\r\nThis mode provides an interface to select one of the bookmarks you have added\r\nbeforehand and jump there.\r\n\r\nYou can add a cursor line to bookmarks by |:FufBookmarkFileAdd| command.\r\nExecute that command and you will be prompted to enter a bookmark name.\r\n\r\nFuzzyFinder adjusts a line number for jump. If a line of bookmarked position\r\ndoes not match to a pattern when the bookmark was added, FuzzyFinder searches\r\na matching line around bookmarked position. So you can jump to a bookmarked\r\nline even if the line is out of bookmarked position. If you want to jump to\r\nbookmarked line number without the adjustment, set\r\n|g:fuf_bookmarkfile_searchRange| option to 0.\r\n\r\nPress <C-]> (|g:fuf_bookmarkfile_keyDelete|) in this mode and selected\r\nbookmark will be deleted.\r\n\r\n                                                        *fuf-bookmarkdir-mode*\r\nBookmark-Dir mode ~\r\n\r\nThis mode provides an interface to select one of the bookmarks you have added\r\nbeforehand and change the current directory.\r\n\r\nYou can add a directory to bookmarks by |:FufBookmarkDirAdd| command. Execute\r\nthat command and you will be prompted to enter a directory path and  a\r\nbookmark name.\r\n\r\nPress <C-]> (|g:fuf_bookmarkdir_keyDelete|) in this mode and selected bookmark\r\nwill be deleted.\r\n\r\n                                                                *fuf-tag-mode*\r\nTag mode ~\r\n\r\nThis mode provides an interface to select a tag and jump to the definition of\r\nit.\r\n\r\nFollowing mapping is a replacement for <C-]>:\r\n>\r\n        noremap <silent> <C-]> :FufTagWithCursorWord!<CR>\r\n<\r\n\r\n                                                          *fuf-buffertag-mode*\r\nBuffer-Tag mode ~\r\n\r\nThis mode provides an interface to select a tag of current buffer or all\r\nbuffers and jump to the definition of it.\r\n\r\nTag list is instantly created when FuzzyFinder is launched, so there is no\r\nneed to make tags file in advance.\r\n\r\n|FufBufferTag| covers current buffer and |FufBufferTagAll| covers all buffers.\r\n\r\nFollowing mapping is a replacement for <C-]>:\r\n>\r\n        nnoremap <silent> <C-]> :FufBufferTagWithCursorWord!<CR>\r\n        vnoremap <silent> <C-]> :FufBufferTagAllWithSelectedText!<CR>\r\n<\r\nor\r\n>\r\n        nnoremap <silent> <C-]> :FufBufferTagAllWithCursorWord!<CR>\r\n        vnoremap <silent> <C-]> :FufBufferTagAllWithSelectedText!<CR>\r\n<\r\nThis mode is inspired by taglist.vim (vimscript #273) and refered its codes.\r\n\r\n                                                         *fuf-taggedfile-mode*\r\nTagged-File mode ~\r\n\r\nThis mode provides an interface to select one of the files which are included\r\nin current tagfiles and open it.\r\n\r\n                                                           *fuf-jumplist-mode*\r\nJump-List mode ~\r\n\r\nThis mode provides an interface to select one from the |jumplist| of the\r\ncurrent window and jump there.\r\n\r\n                                                         *fuf-changelist-mode*\r\nChange-List mode ~\r\n\r\nThis mode provides an interface to select one from the |changelist| of the\r\ncurrent buffer and jump there.\r\n\r\n                                                           *fuf-quickfix-mode*\r\nQuickfix mode ~\r\n\r\nThis mode provides an interface to select one from the |quickfix| list and\r\njump there.\r\n\r\n                                                               *fuf-line-mode*\r\nLine mode ~\r\n\r\nThis mode provides an interface to select a line from current buffer and jump\r\nthere.\r\n\r\n                                                               *fuf-help-mode*\r\nHelp mode ~\r\n\r\nThis mode provides an interface to select a help tag and jump to the help\r\npage.\r\n\r\n                                                          *fuf-givenfile-mode*\r\nGiven-File mode ~\r\n\r\nThis mode provides an API to open a selected file from a given list.\r\n\r\nAPI function:\r\n>\r\n        function fuf#givenfile#launch(\r\n              \\ initialPattern, partialMatching, prompt, items)\r\n<\r\n        initialPattern  - String which is inserted after launching\r\n                          FuzzyFinder.\r\n        partialMatching - If non-zero, enable partial matching instead of\r\n                          fuzzy matching.\r\n        prompt          - Prompt string\r\n        items           - List of items.\r\n\r\nExample of use:\r\n>\r\n        \" Open one of your dotfiles.\r\n        call fuf#givenfile#launch('', 0, '>', split(glob('~\/.*'), \"\\n\"))\r\n<\r\n\r\n                                                           *fuf-givendir-mode*\r\nGiven-Directory mode ~\r\n\r\nThis mode provides an API to change current working directory to a selected\r\none from a given list.\r\n\r\nAPI function:\r\n>\r\n        function fuf#givendir#launch(\r\n              \\ initialPattern, partialMatching, prompt, items)\r\n<\r\n        initialPattern  - String which is inserted after launching\r\n                          FuzzyFinder.\r\n        partialMatching - If non-zero, enable partial matching instead of\r\n                          fuzzy matching.\r\n        prompt          - Prompt string\r\n        items           - List of items.\r\n\r\n\r\nExample of use:\r\n>\r\n        \" Change current working directory to one of your runtime directory.\r\n        call fuf#givendir#launch('', 0, '>', split(&runtimepath, ','))\r\n<\r\n\r\n                                                           *fuf-givencmd-mode*\r\nGiven-Command mode ~\r\n\r\nThis mode provides an API to execute a selected command from a given list.\r\n\r\nA selected command is executed by |feedkeys()|, so it is able to emulate a\r\nseries of key input in Normal mode.\r\n\r\nAPI function:\r\n>\r\n        function fuf#givencmd#launch(\r\n              \\ initialPattern, partialMatching, prompt, items)\r\n<\r\n        initialPattern  - String which is inserted after launching\r\n                          FuzzyFinder.\r\n        partialMatching - If non-zero, enable partial matching instead of\r\n                          fuzzy matching.\r\n        prompt          - Prompt string\r\n        items           - List of items.\r\n\r\n\r\nExample of use:\r\n>\r\n        function GetAllCommands()\r\n          redir => commands\r\n          silent command\r\n          redir END\r\n          return map((split(commands, \"\\n\")[3:]),\r\n              \\      '\":\" . matchstr(v:val, ''^....\\zs\\S*'')')\r\n        endfunction\r\n\r\n        \" execute one of the user-defined commands \r\n        call fuf#givencmd#launch('', 0, '>', GetAllCommands())\r\n\r\n<\r\n\r\n                                                       *fuf-callbackfile-mode*\r\nCallback-File mode ~\r\n\r\nThis mode provides an API to find and get a file path which is selected by an\r\nuser.\r\n\r\nAPI function:\r\n>\r\n        function fuf#callbackfile#launch(\r\n              \\ initialPattern, partialMatching, prompt, exclude, listener)\r\n<\r\n        initialPattern  - String which is inserted after launching\r\n                          FuzzyFinder.\r\n        partialMatching - If non-zero, enable partial matching instead of\r\n                          fuzzy matching.\r\n        prompt          - Prompt string.\r\n        exclude         - Regexp pattern for items which you want to exclude\r\n                          from completion list.\r\n        listener        - |Dictionary| which has 'onComplete' and 'onAbort'.\r\n                          They are called at the end of FuzzyFinder.\r\n                          listener.onComplete(item, method) is called with 2\r\n                          arguments which are a name of selected item and a\r\n                          number of open method when completed.\r\n                          listener.onAbort() is called when aborted.\r\n\r\nExample of use:\r\n>\r\n        let listener = {}\r\n\r\n        function listener.onComplete(item, method)\r\n          echo \"Item: \" . a:item . \"\\nMethod: \" . a:method\r\n        endfunction\r\n\r\n        function listener.onAbort()\r\n          echo \"Abort\"\r\n        endfunction\r\n\r\n        \" Find a file from current working directory.\r\n        call fuf#callbackfile#launch('', 0, '>', '', listener)\r\n\r\n        \" Find a file from home directory.\r\n        call fuf#callbackfile#launch('~\/', 0, '>', '', listener)\r\n<\r\n\r\n                                                       *fuf-callbackitem-mode*\r\nCallback-Item mode ~\r\n\r\nThis mode provides an API to get an item which is selected from a given list\r\nby an user.\r\n\r\nAPI function:\r\n>\r\n        function fuf#callbackitem#launch(\r\n              \\ initialPattern, partialMatching, prompt, listener, items, forPath)\r\n<\r\n        initialPattern  - String which is inserted after launching\r\n                          FuzzyFinder.\r\n        partialMatching - If non-zero, enable partial matching instead of\r\n                          fuzzy matching.\r\n        prompt          - Prompt string\r\n        listener        - |Dictionary| which has 'onComplete' and 'onAbort'.\r\n                          They are called at the end of FuzzyFinder.\r\n                          listener.onComplete(item, method) is called with 2\r\n                          arguments which are a name of selected item and a\r\n                          number of open method when completed.\r\n                          listener.onAbort() is called when aborted.\r\n        items           - List of items.\r\n        forPath         - If non-zero, use a matching method for files.\r\n\r\nExample of use:\r\n>\r\n        let listener = {}\r\n\r\n        function listener.onComplete(item, method)\r\n          echo \"Item: \" . a:item . \"\\nMethod: \" . a:method\r\n        endfunction\r\n\r\n        function listener.onAbort()\r\n          echo \"Abort\"\r\n        endfunction\r\n\r\n        \" Select an item from a given list.\r\n        call fuf#callbackitem#launch('', 0, '>', listener, ['ed', 'vi', 'vim'], 0)\r\n\r\n        \" Select a file from a given list.\r\n        call fuf#callbackitem#launch('', 0, '>', listener, ['..\/foo\/bar', 'baz'], 1)\r\n<\r\n\r\n==============================================================================\r\nDETAILED TOPICS                                          *fuf-detailed-topics*\r\n\r\n                     *fuf-setting-one-time-option* *fuf#setOneTimeVariables()*\r\nSetting One-Time Options ~\r\n\r\nIf you want to set one-time options only for the next FuzzyFinder,\r\n|fuf#setOneTimeVariables()| function will be of help. This function is used as\r\nfollows:\r\n>\r\n        call fuf#setOneTimeVariables(['g:fuf_ignoreCase', 0], ['&lines', 50])\r\n<\r\nThis function takes 0 or more arguments and each of them is a pair of a\r\nvariable name and its value. Specified options will be set practically next\r\ntime FuzzyFinder is launched, and restored when FuzzyFinder is closed.\r\n\r\n                                                         *fuf-search-patterns*\r\nSearch Patterns ~\r\n\r\nYou can enter one primary pattern and zero or more refining patterns as search\r\npatterns. An entered pattern is separated by \";\" (|g:fuf_patternSeparator|),\r\nand the first pattern is a primary pattern and the rest of patterns is a\r\nrefining pattern.\r\n>\r\n                   primary    refining  refining\r\n                 |----------| |-------| |----|\r\n        >MruFile>bookmark.vim;autoload\/;\/home\/\r\n<\r\nA refining pattern is used to narrow down the list of matching items by\r\nanother pattern.\r\n\r\nWith a primary pattern, FuzzyFinder does fuzzy matching or partial matching,\r\nwhich you specified. With a refining pattern, FuzzyFinder does partial\r\nmatching by default. (|g:fuf_fuzzyRefining|)\r\n\r\nWhen you enter a number as refining pattern, it also can match the index of\r\neach item.\r\n\r\nIn a mode which targets a static set of file paths (such as Buffer or MRU-File\r\nmode, not File or Directory) and |g:fuf_splitPathMatching| is non-zero,\r\nmatching with a primary pattern is divided into head part and tail part and\r\ndone individually.\r\n>\r\n          head   tail\r\n        |------||-----|\r\n        foo\/bar\/baz.vim\r\n\r\n        fuzzy matching example:\r\n        +----------------+---------+---------+---------+\r\n        | item \\ pattern | foo\/bar | foo\/    | bar     |\r\n        +----------------+---------+---------+---------+\r\n        | foo\/bar        |   match |   match |   match |\r\n        | foo\/abc        | unmatch |   match | unmatch |\r\n        | abc\/bar        | unmatch | unmatch |   match |\r\n        | foobar         | unmatch | unmatch |   match |\r\n        | foooo\/barrrr   |   match |   match |   match |\r\n        | foooo\/fooooo   | unmatch |   match | unmatch |\r\n        +----------------+---------+---------+---------+\r\n<\r\nrefining pattern can match anywhere on each path in the above case.\r\n\r\n                                             *fuf-sorting-of-completion-items*\r\nSorting Of Completion Items ~\r\n\r\nFuzzyFinder sorts completion items with some rules.\r\n\r\nAn item, one part of which is matched with a whole pattern, is placed upper.\r\nE.g., with the pattern \"bc\", the item \"abc\" is placed upper than \"bac\".\r\n\r\nIn the above case, items, each having matching part at the head of itself, are\r\nplaced upper than others. E.g., with the pattern \"foo\", the item \"foobar\" is\r\nplaced upper than \"foobarbaz\".\r\n\r\nAnd the shorter the length of the item after matching position puts it higher.\r\nE.g., with the pattern \"bar\", the item \"foobar\" is placed upper than\r\n\"foobarbaz\".\r\n\r\nIf a pattern matches an item at only word boundaries of it, the item is placed\r\nupper. E.g., with a pattern \"fb\", items such as \"fooBarBaz\" and \"foo_bar_baz\"\r\nis placed upper.\r\n\r\nPlus, FuzzyFinder has a learning system. An item which has been completed in\r\nthe past with current pattern is placed upper.\r\n\r\n                                                          *fuf-reusing-window*\r\nReusing Of A Window Containing Target Buffer\/File ~\r\n\r\nIf a window containing target buffer is found in current tab page when\r\nFuzzyFinder is going to open the buffer in a split new window, move to it. If\r\na window containing target buffer is found in other tab page when FuzzyFinder\r\nis going to open the buffer in a new tab page, move to it.\r\n\r\nYou can disable that feature via 'reuse_window' options if always want to open\r\na buffer in a new window.\r\n\r\n                                                             *fuf-hiding-menu*\r\nTo Hide The Completion Menu Temporarily In FuzzyFinder ~\r\n\r\nYou can close it by <C-e> and reopen it by <C-x><C-o>.\r\n\r\n                                      *fuf-abbreviation* *fuf-multiple-search*\r\nAbbreviations And Multiple Search ~\r\n\r\nYou can use abbreviations and multiple search in all modes by setting\r\n|g:fuf_abbrevMap| option.\r\n\r\nFor example, set as below:\r\n>\r\n        let g:fuf_abbrevMap = {\r\n              \\   \"^doc:\" : [\r\n              \\     \"~\/project\/**\/doc\/\",\r\n              \\     \".vim\/doc\/\",\r\n              \\   ],\r\n              \\ }\r\n<\r\nand enter \"doc:txt\" in File mode, then FuzzyFinder searches by the following\r\npatterns:\r\n\r\n        \"~\/project\/**\/doc\/*t*x*t*\"\r\n        \".vim\/doc\/*t*x*t*\"\r\n\r\nand show concatenated search results.\r\n\r\n                                                               *fuf-data-file*\r\nData File ~\r\n\r\nFuzzyFinder writes completion statistics, MRU data, bookmark, etc to files\r\nunder |g:fuf_dataDir|.\r\n\r\n|:FufEditDataFile| command is helpful in editing your data files. This command\r\nreads the data file in new unnamed buffer. Write the buffer and the data file\r\nwill be updated.\r\n\r\n                                                                   *fuf-cache*\r\nCache ~\r\n\r\nOnce a cache was created, It is not automatically updated to speed up the\r\nresponse time by default. To update it, use |:FufRenewCache| command.\r\n\r\n                                                            *fuf-dot-sequence*\r\nGoing Up Parent Directories With Dot Sequence ~\r\n\r\nYou can go up parent directories with entering dot sequence. Dot sequence\r\nafter a path separator is expanded to \"..\/\" sequence.\r\n\r\n        Dot sequence    Expanded pattern ~\r\n        \/..             \/..\/\r\n        \/...            \/..\/..\/\r\n        \/....           \/..\/..\/..\/\r\n\r\n                                                         *fuf-how-to-add-mode*\r\nHow To Add Mode ~\r\n\r\nTo add \"mymode\" mode, put the source file at autoload\/fuf\/mymode.vim and call\r\nfuf#addMode(\"mymode\") .\r\n\r\n                                                                  *fuf-migemo*\r\nWhat Is Migemo ~\r\n\r\nMigemo is a search method for Japanese language.\r\n\r\n\r\n==============================================================================\r\n","install_details":"","5":"","first_name":"Takeshi","6":"Takeshi","last_name":"NISHIDA","7":"NISHIDA","releases":[{"0":"1984","vim_version":"7.2","1":"7.2","script_version":"4.2.2","2":"4.2.2","version_comment":"- Fixed a bug that unloaded buffers weren't covered by FufBufferTagAll.","3":"- Fixed a bug that unloaded buffers weren't covered by FufBufferTagAll.","package":"vim-fuzzyfinder.zip","4":"vim-fuzzyfinder.zip","src_id":"13961","5":"13961","creation_date":"1285852234","6":"1285852234"},{"0":"1984","vim_version":"7.2","1":"7.2","script_version":"4.2.1","2":"4.2.1","version_comment":"- Improved response of Buffer-Tag mode.\r\n- Fixed a bug that buffers which had been opened weren't listed in\r\n  Coverage-File mode\r\n- Fixed a bug that tag entries including tab characters weren't parsed\r\n  correctly in Coverage-File mode\r\n","3":"- Improved response of Buffer-Tag mode.\r\n- Fixed a bug that buffers which had been opened weren't listed in\r\n  Coverage-File mode\r\n- Fixed a bug that tag entries including tab characters weren't parsed\r\n  correctly in Coverage-File mode\r\n","package":"vim-fuzzyfinder.zip","4":"vim-fuzzyfinder.zip","src_id":"13956","5":"13956","creation_date":"1285772996","6":"1285772996"},{"0":"1984","vim_version":"7.2","1":"7.2","script_version":"4.2","2":"4.2","version_comment":"- L9 library (vimscript #3252) version 1.1 is required.\r\n- Added Buffer-Tag mode, inspired by taglist.vim (vimscript #273).\r\n- Added :FufMruFileInCwd command.\r\n","3":"- L9 library (vimscript #3252) version 1.1 is required.\r\n- Added Buffer-Tag mode, inspired by taglist.vim (vimscript #273).\r\n- Added :FufMruFileInCwd command.\r\n","package":"vim-fuzzyfinder.zip","4":"vim-fuzzyfinder.zip","src_id":"13949","5":"13949","creation_date":"1285686659","6":"1285686659"},{"0":"1984","vim_version":"7.2","1":"7.2","script_version":"4.1.1","2":"4.1.1","version_comment":"- Fixed a bug causing a error in MRU-File mode.","3":"- Fixed a bug causing a error in MRU-File mode.","package":"vim-fuzzyfinder.zip","4":"vim-fuzzyfinder.zip","src_id":"13941","5":"13941","creation_date":"1285604490","6":"1285604490"},{"0":"1984","vim_version":"7.0","1":"7.0","script_version":"4.1","2":"4.1","version_comment":"- Added Bookmark-Dir mode.\r\n- Added Bookmark-File mode and removed Bookmark mode.\r\n- Changed the filename to store data of Coverage-File mode, from\r\n  '~\/.vim-fuf-data\/coveragefile\/items' to\r\n  '~\/.vim-fuf-data\/coveragefile\/coverages' .\r\n- Fixed a bug that floating point numbers weren't evaluated correctly and\r\n  caused errors on some non-English locales.\r\n- Removed Around-MRU-File mode and integrated its feature to MRU-File mode.\r\n","3":"- Added Bookmark-Dir mode.\r\n- Added Bookmark-File mode and removed Bookmark mode.\r\n- Changed the filename to store data of Coverage-File mode, from\r\n  '~\/.vim-fuf-data\/coveragefile\/items' to\r\n  '~\/.vim-fuf-data\/coveragefile\/coverages' .\r\n- Fixed a bug that floating point numbers weren't evaluated correctly and\r\n  caused errors on some non-English locales.\r\n- Removed Around-MRU-File mode and integrated its feature to MRU-File mode.\r\n","package":"vim-fuzzyfinder.zip","4":"vim-fuzzyfinder.zip","src_id":"13938","5":"13938","creation_date":"1285596437","6":"1285596437"},{"0":"1984","vim_version":"7.2","1":"7.2","script_version":"4.0","2":"4.0","version_comment":"- From this version, L9 library (vimscript #3252) is required.\r\n- Added Coverage-File mode for users wanting something like TextMate's\r\n  command-t. (But I've never used it.)\r\n- Added Around-MRU-File mode. (Too slow. There is room for improvement.)\r\n- Added new feature which deletes selected buffer with FuzzyFinder and\r\n  g:fuf_buffer_keyDelete option.\r\n- Added new feature which allows to set one-time options\/variables with\r\n  fuf#setOneTimeVariables() function.\r\n- Added g:fuf_dataDir option and removed g:fuf_infoFile,\r\n  g:g:fuf_tag_cache_dir, g:fuf_taggedfile_cache_dir, and\r\n  g:fuf_help_cache_dir options.\r\n- Added :FufEditDataFile command and removed :FufEditInfo command.\r\n- Added g:fuf_fuzzyRefining option.\r\n- Added new feature which is auto-preview and g:fuf_autoPreview option.\r\n- Changed the default value of g:fuf_previewHeight to 0 in order to disable\r\n  preview feature. There is an unfixable problem which is caused by a Vim's\r\n  bug.\r\n- Changed the default value of g:fuf_modesDisable option.\r\n- Changed the default value of g:fuf_*_switchOrder options.\r\n- Improved speed of changing buffers.\r\n- Improved the way to add user-defined mode.\r\n- Fixed a bug that FuzzyFinder caused reseting window layout.\r\n- Removed g:fuf_smartBs option. Use <C-w> instead.\r\n","3":"- From this version, L9 library (vimscript #3252) is required.\r\n- Added Coverage-File mode for users wanting something like TextMate's\r\n  command-t. (But I've never used it.)\r\n- Added Around-MRU-File mode. (Too slow. There is room for improvement.)\r\n- Added new feature which deletes selected buffer with FuzzyFinder and\r\n  g:fuf_buffer_keyDelete option.\r\n- Added new feature which allows to set one-time options\/variables with\r\n  fuf#setOneTimeVariables() function.\r\n- Added g:fuf_dataDir option and removed g:fuf_infoFile,\r\n  g:g:fuf_tag_cache_dir, g:fuf_taggedfile_cache_dir, and\r\n  g:fuf_help_cache_dir options.\r\n- Added :FufEditDataFile command and removed :FufEditInfo command.\r\n- Added g:fuf_fuzzyRefining option.\r\n- Added new feature which is auto-preview and g:fuf_autoPreview option.\r\n- Changed the default value of g:fuf_previewHeight to 0 in order to disable\r\n  preview feature. There is an unfixable problem which is caused by a Vim's\r\n  bug.\r\n- Changed the default value of g:fuf_modesDisable option.\r\n- Changed the default value of g:fuf_*_switchOrder options.\r\n- Improved speed of changing buffers.\r\n- Improved the way to add user-defined mode.\r\n- Fixed a bug that FuzzyFinder caused reseting window layout.\r\n- Removed g:fuf_smartBs option. Use <C-w> instead.\r\n","package":"vim-fuzzyfinder.zip","4":"vim-fuzzyfinder.zip","src_id":"13908","5":"13908","creation_date":"1285340215","6":"1285340215"},{"0":"1984","vim_version":"7.0","1":"7.0","script_version":"3.5","2":"3.5","version_comment":"  - Added Line mode.\r\n  - Added Help mode.\r\n  - Added key mapping to switch between fuzzy matching and partial matching.\r\n  - Changed the default values of g:fuf_file_exclude for ignoring \"*.dll\".\r\n  - Changed Tag mode and Tagged-File mode to cache parsed data to files in \"~\/.vim-fuf-cache\/\".\r\n  - Fixed a bug that repeating preview key produced no effect.\r\n  - Fixed a bug that File mode and Directory mode didn't list items in a directory whose name includes uppercase characters. (Thanks, ryo7000)\r\n","3":"  - Added Line mode.\r\n  - Added Help mode.\r\n  - Added key mapping to switch between fuzzy matching and partial matching.\r\n  - Changed the default values of g:fuf_file_exclude for ignoring \"*.dll\".\r\n  - Changed Tag mode and Tagged-File mode to cache parsed data to files in \"~\/.vim-fuf-cache\/\".\r\n  - Fixed a bug that repeating preview key produced no effect.\r\n  - Fixed a bug that File mode and Directory mode didn't list items in a directory whose name includes uppercase characters. (Thanks, ryo7000)\r\n","package":"vim-fuzzyfinder.zip","4":"vim-fuzzyfinder.zip","src_id":"11852","5":"11852","creation_date":"1259851720","6":"1259851720"},{"0":"1984","vim_version":"7.0","1":"7.0","script_version":"3.4a","2":"3.4a","version_comment":"- Added new feature which makes it possible to preview selected completion item.\r\n- Changed matching rules and added g:fuf_splitPathMatching.\r\n- Changed sorting rules.\r\n- Changed the default values of g:fuf_file_exclude and g:fuf_dir_exclude in order to ignore \".hg\", \".git\", and \".bzr\" directories.\r\n- Changed the default value of g:fuf_mrufile_exclude in order to ignore network files (\\\\*) on Windows and ignore \/mnt\/* and \/media\/* on Unix like systems.\r\n- Fixed a bug that an exclude pattern of File, Dir, and Callback-File mode can't be changed.\r\n","3":"- Added new feature which makes it possible to preview selected completion item.\r\n- Changed matching rules and added g:fuf_splitPathMatching.\r\n- Changed sorting rules.\r\n- Changed the default values of g:fuf_file_exclude and g:fuf_dir_exclude in order to ignore \".hg\", \".git\", and \".bzr\" directories.\r\n- Changed the default value of g:fuf_mrufile_exclude in order to ignore network files (\\\\*) on Windows and ignore \/mnt\/* and \/media\/* on Unix like systems.\r\n- Fixed a bug that an exclude pattern of File, Dir, and Callback-File mode can't be changed.\r\n","package":"vim-fuzzyfinder.zip","4":"vim-fuzzyfinder.zip","src_id":"11769","5":"11769","creation_date":"1258727076","6":"1258727076"},{"0":"1984","vim_version":"7.0","1":"7.0","script_version":"3.3","2":"3.3","version_comment":"- Added Jump-List mode, Change-List mode, and Quickfix mode which enable\r\n  jumps with jump list, change list, and quickfix list.\r\n- Added new feature which deletes selected bookmark with FuzzyFinder and\r\n  g:fuf_bookmark_keyDelete option.\r\n- Changed default values of g:fuf_keyPrevPattern.\r\n- Changed to show error message when incompatible with a installed vim.\r\n","3":"- Added Jump-List mode, Change-List mode, and Quickfix mode which enable\r\n  jumps with jump list, change list, and quickfix list.\r\n- Added new feature which deletes selected bookmark with FuzzyFinder and\r\n  g:fuf_bookmark_keyDelete option.\r\n- Changed default values of g:fuf_keyPrevPattern.\r\n- Changed to show error message when incompatible with a installed vim.\r\n","package":"vim-fuzzyfinder.zip","4":"vim-fuzzyfinder.zip","src_id":"11537","5":"11537","creation_date":"1255761993","6":"1255761993"},{"0":"1984","vim_version":"7.0","1":"7.0","script_version":"3.2","2":"3.2","version_comment":"- Added g:fuf_promptHighlight option to integrate such options for each\r\n  mode.\r\n- Changed APIs of Given-File, Given-Directory, Given-Command, Callback-File,\r\n  and Callback-Item modes to be able to set a prompt string.\r\n- Changed default values of g:fuf_keyPrevPattern and g:fuf_keyNextPattern.\r\n- Fixed a bug that MRU-File data was not updated When a file was opened with\r\n  FuzzyFinder.\r\n- Fixed a bug with scoring matchings for sorting. Thanks to Vincent.\r\n- Brought back the removed feature which is switching to an other mode in\r\n  FuzzyFinder.\r\n","3":"- Added g:fuf_promptHighlight option to integrate such options for each\r\n  mode.\r\n- Changed APIs of Given-File, Given-Directory, Given-Command, Callback-File,\r\n  and Callback-Item modes to be able to set a prompt string.\r\n- Changed default values of g:fuf_keyPrevPattern and g:fuf_keyNextPattern.\r\n- Fixed a bug that MRU-File data was not updated When a file was opened with\r\n  FuzzyFinder.\r\n- Fixed a bug with scoring matchings for sorting. Thanks to Vincent.\r\n- Brought back the removed feature which is switching to an other mode in\r\n  FuzzyFinder.\r\n","package":"vim-fuzzyfinder.zip","4":"vim-fuzzyfinder.zip","src_id":"11365","5":"11365","creation_date":"1252835714","6":"1252835714"},{"0":"1984","vim_version":"7.0","1":"7.0","script_version":"3.1","2":"3.1","version_comment":"- Added new feature to recall patterns which have been entered before from\r\n  history.\r\n","3":"- Added new feature to recall patterns which have been entered before from\r\n  history.\r\n","package":"vim-fuzzyfinder.zip","4":"vim-fuzzyfinder.zip","src_id":"11336","5":"11336","creation_date":"1252321503","6":"1252321503"},{"0":"1984","vim_version":"7.0","1":"7.0","script_version":"3.0","2":"3.0","version_comment":"- Redesigned the whole plugin for improvements of maintainability and\r\n  performance. \"fuzzyfinder\" is abbreviated to \"fuf\" in the sorce code and\r\n  filenames. All commands and options are renamed.\r\n- Added new feature which is refining pattern.\r\n- Improved the rules for sorting completion items. Thanks to the suggestion\r\n  by Nathan, the rule for boundary matching was implemented.\r\n- Changed to open one line buffer of FuzzyFinder with :topleft command\r\n  instead of :leftabove. The window will alway appear at the top and occupy\r\n  the full with of the vim window. Thanks to Jan Christoph.\r\n- Changed default filename of information file.\r\n- Changed MRU-File mode and MRU-Command mode to be disabled by default\r\n  due to performance and side effect issues.\r\n- Removed the feature which is switching to an other mode in FuzzyFinder.\r\n- Removed the feature which is temporarily switching 'ignorecase' in\r\n  FuzzyFinder.\r\n","3":"- Redesigned the whole plugin for improvements of maintainability and\r\n  performance. \"fuzzyfinder\" is abbreviated to \"fuf\" in the sorce code and\r\n  filenames. All commands and options are renamed.\r\n- Added new feature which is refining pattern.\r\n- Improved the rules for sorting completion items. Thanks to the suggestion\r\n  by Nathan, the rule for boundary matching was implemented.\r\n- Changed to open one line buffer of FuzzyFinder with :topleft command\r\n  instead of :leftabove. The window will alway appear at the top and occupy\r\n  the full with of the vim window. Thanks to Jan Christoph.\r\n- Changed default filename of information file.\r\n- Changed MRU-File mode and MRU-Command mode to be disabled by default\r\n  due to performance and side effect issues.\r\n- Removed the feature which is switching to an other mode in FuzzyFinder.\r\n- Removed the feature which is temporarily switching 'ignorecase' in\r\n  FuzzyFinder.\r\n","package":"vim-fuzzyfinder.zip","4":"vim-fuzzyfinder.zip","src_id":"11319","5":"11319","creation_date":"1252067877","6":"1252067877"},{"0":"1984","vim_version":"7.0","1":"7.0","script_version":"2.22.3","2":"2.22.3","version_comment":"- Fixed a bug that Fuzzyfinder could not open files with '$' in the name on\r\n  Windows.","3":"- Fixed a bug that Fuzzyfinder could not open files with '$' in the name on\r\n  Windows.","package":"vim-fuzzyfinder.zip","4":"vim-fuzzyfinder.zip","src_id":"10718","5":"10718","creation_date":"1244036216","6":"1244036216"},{"0":"1984","vim_version":"7.0","1":"7.0","script_version":"2.22.2","2":"2.22.2","version_comment":"- Changed to consider a length of a date\/time string when abbreviates long\r\n  completion items.\r\n- Fixed a bug that '**\/' pattern did not search for files directly under the\r\n  current working directory in File mode. Thanks to Martin for reporting.\r\n","3":"- Changed to consider a length of a date\/time string when abbreviates long\r\n  completion items.\r\n- Fixed a bug that '**\/' pattern did not search for files directly under the\r\n  current working directory in File mode. Thanks to Martin for reporting.\r\n","package":"vim-fuzzyfinder.zip","4":"vim-fuzzyfinder.zip","src_id":"10714","5":"10714","creation_date":"1243947638","6":"1243947638"},{"0":"1984","vim_version":"7.0","1":"7.0","script_version":"2.22.1","2":"2.22.1","version_comment":"- Fixed a bug that Fuzzyfinder could not expand abbreviations to patterns\r\n  including '\\' correctly.\r\n- Fixed to show item number in Given-File, Given-Directory, and\r\n  Given-Command mode.\r\n","3":"- Fixed a bug that Fuzzyfinder could not expand abbreviations to patterns\r\n  including '\\' correctly.\r\n- Fixed to show item number in Given-File, Given-Directory, and\r\n  Given-Command mode.\r\n","package":"vim-fuzzyfinder.zip","4":"vim-fuzzyfinder.zip","src_id":"10677","5":"10677","creation_date":"1243257205","6":"1243257205"},{"0":"1984","vim_version":"7.0","1":"7.0","script_version":"2.22.0","2":"2.22.0","version_comment":"- More improved the abbreviation method for long completion items.\r\n- Added Given-File mode for third-party script to select a file from a given\r\n  list and open.\r\n- Added Given-Directory mode for third-party script to select a directory\r\n  from a given list and change current working directory to it.\r\n- Added Given-Command mode for third-party script to select a command from a\r\n  given list and execute.\r\n- Changed ways to launch Callback-File mode and Callback-item mode.\r\n","3":"- More improved the abbreviation method for long completion items.\r\n- Added Given-File mode for third-party script to select a file from a given\r\n  list and open.\r\n- Added Given-Directory mode for third-party script to select a directory\r\n  from a given list and change current working directory to it.\r\n- Added Given-Command mode for third-party script to select a command from a\r\n  given list and execute.\r\n- Changed ways to launch Callback-File mode and Callback-item mode.\r\n","package":"vim-fuzzyfinder.zip","4":"vim-fuzzyfinder.zip","src_id":"10639","5":"10639","creation_date":"1242829560","6":"1242829560"},{"0":"1984","vim_version":"7.0","1":"7.0","script_version":"2.21.0","2":"2.21.0","version_comment":"- Improved a method of trimming long completion items. Thanks to Andy,\r\n  pyrhockz, and Nathan.\r\n- Changed not to map command-line <CR> for MRU-Command mode if\r\n  g:FuzzyFinderOptions.MruCmd.mode_available is set 0 before loading\r\n  fuzzyfinder.vim.\r\n- Added Callback-File mode and Callback-Item mode for third-party script to\r\n  find a file\/directory or an item from a given list using Fuzzyfinder.\r\n- Changed not to append \"..\" to a completion menu in File\/Directory mode.\r\n  Use dot sequence feature.\r\n- Changed default value of g:FuzzyFinderOptions.File.excluded_path option.\r\n- Changed default value of g:FuzzyFinderOptions.Dir.excluded_path option.\r\n- Fixed a bug that couldn't jump to a tag. Thanks to Thinca.\r\n","3":"- Improved a method of trimming long completion items. Thanks to Andy,\r\n  pyrhockz, and Nathan.\r\n- Changed not to map command-line <CR> for MRU-Command mode if\r\n  g:FuzzyFinderOptions.MruCmd.mode_available is set 0 before loading\r\n  fuzzyfinder.vim.\r\n- Added Callback-File mode and Callback-Item mode for third-party script to\r\n  find a file\/directory or an item from a given list using Fuzzyfinder.\r\n- Changed not to append \"..\" to a completion menu in File\/Directory mode.\r\n  Use dot sequence feature.\r\n- Changed default value of g:FuzzyFinderOptions.File.excluded_path option.\r\n- Changed default value of g:FuzzyFinderOptions.Dir.excluded_path option.\r\n- Fixed a bug that couldn't jump to a tag. Thanks to Thinca.\r\n","package":"vim-fuzzyfinder.zip","4":"vim-fuzzyfinder.zip","src_id":"10588","5":"10588","creation_date":"1242232481","6":"1242232481"},{"0":"1984","vim_version":"7.0","1":"7.0","script_version":"2.20","2":"2.20","version_comment":"- Added help files which are doc\/fuzzyfinder.txt and doc\/fuzzyfinder.jax.\r\n- Fixed a bug that an error occurs if current directory included spaces.\r\n  Thanks id:cho45 and id:secondlife.\r\n- Implemented a feature to reuse a window containing target buffer.\r\n- Added g:FuzzyFinderOptions.Buffer.reuse_window option.\r\n- Added g:FuzzyFinderOptions.File.reuse_window option.\r\n- Added g:FuzzyFinderOptions.MruFile.reuse_window option.\r\n- Added g:FuzzyFinderOptions.Bookmark.reuse_window option.\r\n- Added g:FuzzyFinderOptions.TaggedFile.reuse_window option.\r\n- Changed to use 'omnifunc' instead of 'completefunc'. Now you can use <C-u>\r\n  to delete all entered characters.\r\n- Changed default value of g:FuzzyFinderOptions.Base.key_open_tab option.\r\n- Changed default value of g:FuzzyFinderOptions.Base.key_next_mode option.\r\n- Changed default value of g:FuzzyFinderOptions.Base.key_prev_mode option.\r\n- Changed default value of g:FuzzyFinderOptions.Base.key_ignore_case option.\r\n- Changed to truncate long completion items from the head instead of tail.\r\n- Added g:FuzzyFinderOptions.Base.max_menu_width option instead of\r\n  g:FuzzyFinderOptions.Base.trim_length option.\r\n- Added :FuzzyFinderFileWithFullCwd command.\r\n- Added :FuzzyFinderFileWithCurrentBufferDir command.\r\n- Added :FuzzyFinderDirWithFullCwd command.\r\n- Added :FuzzyFinderDirWithCurrentBufferDir command.\r\n- Added :FuzzyFinderTagWithCursorWord command.\r\n- Renamed :FuzzyFinderRemoveCache command to :FuzzyFinderRenewCache.\r\n","3":"- Added help files which are doc\/fuzzyfinder.txt and doc\/fuzzyfinder.jax.\r\n- Fixed a bug that an error occurs if current directory included spaces.\r\n  Thanks id:cho45 and id:secondlife.\r\n- Implemented a feature to reuse a window containing target buffer.\r\n- Added g:FuzzyFinderOptions.Buffer.reuse_window option.\r\n- Added g:FuzzyFinderOptions.File.reuse_window option.\r\n- Added g:FuzzyFinderOptions.MruFile.reuse_window option.\r\n- Added g:FuzzyFinderOptions.Bookmark.reuse_window option.\r\n- Added g:FuzzyFinderOptions.TaggedFile.reuse_window option.\r\n- Changed to use 'omnifunc' instead of 'completefunc'. Now you can use <C-u>\r\n  to delete all entered characters.\r\n- Changed default value of g:FuzzyFinderOptions.Base.key_open_tab option.\r\n- Changed default value of g:FuzzyFinderOptions.Base.key_next_mode option.\r\n- Changed default value of g:FuzzyFinderOptions.Base.key_prev_mode option.\r\n- Changed default value of g:FuzzyFinderOptions.Base.key_ignore_case option.\r\n- Changed to truncate long completion items from the head instead of tail.\r\n- Added g:FuzzyFinderOptions.Base.max_menu_width option instead of\r\n  g:FuzzyFinderOptions.Base.trim_length option.\r\n- Added :FuzzyFinderFileWithFullCwd command.\r\n- Added :FuzzyFinderFileWithCurrentBufferDir command.\r\n- Added :FuzzyFinderDirWithFullCwd command.\r\n- Added :FuzzyFinderDirWithCurrentBufferDir command.\r\n- Added :FuzzyFinderTagWithCursorWord command.\r\n- Renamed :FuzzyFinderRemoveCache command to :FuzzyFinderRenewCache.\r\n","package":"vim-fuzzyfinder.zip","4":"vim-fuzzyfinder.zip","src_id":"10480","5":"10480","creation_date":"1240934926","6":"1240934926"},{"0":"1984","vim_version":"7.0","1":"7.0","script_version":"2.19","2":"2.19","version_comment":"- Changed MRU-File mode that always formats completion items to be\r\n  relative to the home directory.\r\n- Fixed a bug that a file was opened in an unintended window with Tag\r\n  List plugin. Thanks Alexey.\r\n- Fixed a bug that garbage characters were entered when switched current\r\n  mode. Thanks id:lugecy.\r\n","3":"- Changed MRU-File mode that always formats completion items to be\r\n  relative to the home directory.\r\n- Fixed a bug that a file was opened in an unintended window with Tag\r\n  List plugin. Thanks Alexey.\r\n- Fixed a bug that garbage characters were entered when switched current\r\n  mode. Thanks id:lugecy.\r\n","package":"fuzzyfinder.vim","4":"fuzzyfinder.vim","src_id":"9814","5":"9814","creation_date":"1231941974","6":"1231941974"},{"0":"1984","vim_version":"7.0","1":"7.0","script_version":"2.18","2":"2.18","version_comment":"- Improved rules for the sorting of completion items.\r\n- Changed not to learn a completion if an entered pattern is empty.\r\n- Fixed a bug that Buffer mode did not work. Thanks ryo7000.\r\n","3":"- Improved rules for the sorting of completion items.\r\n- Changed not to learn a completion if an entered pattern is empty.\r\n- Fixed a bug that Buffer mode did not work. Thanks ryo7000.\r\n","package":"fuzzyfinder.vim","4":"fuzzyfinder.vim","src_id":"9808","5":"9808","creation_date":"1231852929","6":"1231852929"},{"0":"1984","vim_version":"6.0","1":"6.0","script_version":"2.17","2":"2.17","version_comment":"- Introduced a learning system for the sorting of completion items.\r\n- Added g:FuzzyFinderOptions.Base.learning_limit option.\r\n- Changed the specification of the information file. Please remove your\r\n  information file for Fuzzyfinder.\r\n","3":"- Introduced a learning system for the sorting of completion items.\r\n- Added g:FuzzyFinderOptions.Base.learning_limit option.\r\n- Changed the specification of the information file. Please remove your\r\n  information file for Fuzzyfinder.\r\n","package":"fuzzyfinder.vim","4":"fuzzyfinder.vim","src_id":"9798","5":"9798","creation_date":"1231696167","6":"1231696167"},{"0":"1984","vim_version":"7.0","1":"7.0","script_version":"2.16","2":"2.16","version_comment":"- Improved response time by caching in MRU-File mode.\r\n- Fixed a bug in Bookmark mode that Fuzzyfinder did not jump to the\r\n  Bookmarked line number when Bookmarked pattern was not found.\r\n","3":"- Improved response time by caching in MRU-File mode.\r\n- Fixed a bug in Bookmark mode that Fuzzyfinder did not jump to the\r\n  Bookmarked line number when Bookmarked pattern was not found.\r\n","package":"fuzzyfinder.vim","4":"fuzzyfinder.vim","src_id":"9643","5":"9643","creation_date":"1228879819","6":"1228879819"},{"0":"1984","vim_version":"7.0","1":"7.0","script_version":"2.15","2":"2.15","version_comment":"- Added Bookmark mode.\r\n- Removed Favorite-file mode. Use Bookmark mode instead.\r\n- Fixed not to record a entry of input() in MRU-Command mode.\r\n","3":"- Added Bookmark mode.\r\n- Removed Favorite-file mode. Use Bookmark mode instead.\r\n- Fixed not to record a entry of input() in MRU-Command mode.\r\n","package":"fuzzyfinder.vim","4":"fuzzyfinder.vim","src_id":"9623","5":"9623","creation_date":"1228595938","6":"1228595938"},{"0":"1984","vim_version":"7.0","1":"7.0","script_version":"2.14","2":"2.14","version_comment":"- Changed to show buffer status in Buffer mode.\r\n- Fixed a bug that an error occurs when nonexistent buffer-name was\r\n  entered in Buffer mode. Thanks Maxim Kim.\r\n- Added 'enumerating_limit' option. Thanks id:secondlife.\r\n- Removed 'matching_limit' option. Use 'enumerating_limit' instead.\r\n","3":"- Changed to show buffer status in Buffer mode.\r\n- Fixed a bug that an error occurs when nonexistent buffer-name was\r\n  entered in Buffer mode. Thanks Maxim Kim.\r\n- Added 'enumerating_limit' option. Thanks id:secondlife.\r\n- Removed 'matching_limit' option. Use 'enumerating_limit' instead.\r\n","package":"fuzzyfinder.vim","4":"fuzzyfinder.vim","src_id":"9599","5":"9599","creation_date":"1228231089","6":"1228231089"},{"0":"1984","vim_version":"7.0","1":"7.0","script_version":"2.13","2":"2.13","version_comment":"- Fixed a bug that a directory disappeared when a file in that directroy\r\n  was being opened in File\/Mru-File mode.\r\n","3":"- Fixed a bug that a directory disappeared when a file in that directroy\r\n  was being opened in File\/Mru-File mode.\r\n","package":"fuzzyfinder.vim","4":"fuzzyfinder.vim","src_id":"9306","5":"9306","creation_date":"1223111100","6":"1223111100"},{"0":"1984","vim_version":"7.0","1":"7.0","script_version":"2.12","2":"2.12","version_comment":"- Changed to be able to show completion items in the order of recently\r\n  used in Buffer mode.\r\n- Added g:FuzzyFinderOptions.Buffer.mru_order option.\r\n","3":"- Changed to be able to show completion items in the order of recently\r\n  used in Buffer mode.\r\n- Added g:FuzzyFinderOptions.Buffer.mru_order option.\r\n","package":"fuzzyfinder.vim","4":"fuzzyfinder.vim","src_id":"9246","5":"9246","creation_date":"1221272497","6":"1221272497"},{"0":"1984","vim_version":"7.0","1":"7.0","script_version":"2.11","2":"2.11","version_comment":"- Changed that a dot sequence of entered pattern is expanded to parent\r\n  directroies in File\/Dir mode.\r\n  E.g.: \"foo\/...bar\" -> \"foo\/..\/..\/bar\"\r\n- Fixed a bug that a prompt string was excessively inserted.\r\n","3":"- Changed that a dot sequence of entered pattern is expanded to parent\r\n  directroies in File\/Dir mode.\r\n  E.g.: \"foo\/...bar\" -> \"foo\/..\/..\/bar\"\r\n- Fixed a bug that a prompt string was excessively inserted.\r\n","package":"fuzzyfinder.vim","4":"fuzzyfinder.vim","src_id":"9240","5":"9240","creation_date":"1221080950","6":"1221080950"},{"0":"1984","vim_version":"7.0","1":"7.0","script_version":"2.10","2":"2.10","version_comment":"- Changed not to show a current buffer in a completion menu.\r\n- Fixed a bug that a filename to open was not been escaped.\r\n- Added 'prompt' option.\r\n- Added 'prompt_highlight' option.\r\n- Removed g:FuzzyFinderOptions.MruFile.no_special_buffer option.\r\n","3":"- Changed not to show a current buffer in a completion menu.\r\n- Fixed a bug that a filename to open was not been escaped.\r\n- Added 'prompt' option.\r\n- Added 'prompt_highlight' option.\r\n- Removed g:FuzzyFinderOptions.MruFile.no_special_buffer option.\r\n","package":"fuzzyfinder.vim","4":"fuzzyfinder.vim","src_id":"9233","5":"9233","creation_date":"1220949555","6":"1220949555"},{"0":"1984","vim_version":"7.0","1":"7.0","script_version":"2.9","2":"2.9","version_comment":"- Enhanced <BS> behavior in Fuzzyfinder and added 'smart_bs' option.\r\n- Fixed a bug that entered pattern was not been escaped.\r\n- Fixed not to insert \"zv\" with \"c\/pattern<CR>\" command in Normal mode\r\n- Avoid the slow down problem caused by filereadable() check for the MRU\r\n  information in BufEnter\/BufWritePost.\r\n","3":"- Enhanced <BS> behavior in Fuzzyfinder and added 'smart_bs' option.\r\n- Fixed a bug that entered pattern was not been escaped.\r\n- Fixed not to insert \"zv\" with \"c\/pattern<CR>\" command in Normal mode\r\n- Avoid the slow down problem caused by filereadable() check for the MRU\r\n  information in BufEnter\/BufWritePost.\r\n","package":"fuzzyfinder.vim","4":"fuzzyfinder.vim","src_id":"9227","5":"9227","creation_date":"1220659151","6":"1220659151"},{"0":"1984","vim_version":"7.0","1":"7.0","script_version":"2.8.1","2":"2.8.1","version_comment":"- Fixed a bug caused by the non-escaped buffer name \"[Fuzzyfinder]\".\r\n- Fixed a command to open in a new tab page in Buffer mode.\r\n","3":"- Fixed a bug caused by the non-escaped buffer name \"[Fuzzyfinder]\".\r\n- Fixed a command to open in a new tab page in Buffer mode.\r\n","package":"fuzzyfinder.vim","4":"fuzzyfinder.vim","src_id":"9172","5":"9172","creation_date":"1219700843","6":"1219700843"},{"0":"1984","vim_version":"7.0","1":"7.0","script_version":"2.8","2":"2.8","version_comment":"- Added 'trim_length' option.\r\n- Added 'switch_order' option.\r\n- Fixed a bug that entered command did not become the newest in the\r\n  history.\r\n- Fixed a bug that folds could not open with <CR> in a command-line when\r\n  searching.\r\n- Removed 'excluded_indicator' option. Now a completion list in Buffer\r\n  mode is the same as a result of :buffers.\r\n","3":"- Added 'trim_length' option.\r\n- Added 'switch_order' option.\r\n- Fixed a bug that entered command did not become the newest in the\r\n  history.\r\n- Fixed a bug that folds could not open with <CR> in a command-line when\r\n  searching.\r\n- Removed 'excluded_indicator' option. Now a completion list in Buffer\r\n  mode is the same as a result of :buffers.\r\n","package":"fuzzyfinder.vim","4":"fuzzyfinder.vim","src_id":"8964","5":"8964","creation_date":"1216276094","6":"1216276094"},{"0":"1984","vim_version":"7.0","1":"7.0","script_version":"2.7","2":"2.7","version_comment":"- Changed to find an item whose index is matched with the number\r\n  suffixed with entered pattern.\r\n- Fixed the cache bug after changing current directroy in File mode.\r\n","3":"- Changed to find an item whose index is matched with the number\r\n  suffixed with entered pattern.\r\n- Fixed the cache bug after changing current directroy in File mode.\r\n","package":"fuzzyfinder.vim","4":"fuzzyfinder.vim","src_id":"8950","5":"8950","creation_date":"1216012462","6":"1216012462"},{"0":"1984","vim_version":"7.0","1":"7.0","script_version":"2.6.2","2":"2.6.2","version_comment":"- Fixed not to miss changes in options when updates the MRU information.","3":"- Fixed not to miss changes in options when updates the MRU information.","package":"fuzzyfinder.vim","4":"fuzzyfinder.vim","src_id":"8908","5":"8908","creation_date":"1215549592","6":"1215549592"},{"0":"1984","vim_version":"7.0","1":"7.0","script_version":"2.6.1","2":"2.6.1","version_comment":"- Fixed a bug related to floating-point support.\r\n- Added support for GetLatestVimScripts.\r\n","3":"- Fixed a bug related to floating-point support.\r\n- Added support for GetLatestVimScripts.\r\n","package":"fuzzyfinder.vim","4":"fuzzyfinder.vim","src_id":"8895","5":"8895","creation_date":"1215412907","6":"1215412907"},{"0":"1984","vim_version":"7.0","1":"7.0","script_version":"2.6","2":"2.6","version_comment":"- Revived MRU-command mode. The problem with a command-line abbreviation\r\n  was solved.\r\n- Changed the specification of the information file.\r\n- Added :FuzzyFinderEditInfo command.\r\n","3":"- Revived MRU-command mode. The problem with a command-line abbreviation\r\n  was solved.\r\n- Changed the specification of the information file.\r\n- Added :FuzzyFinderEditInfo command.\r\n","package":"fuzzyfinder.vim","4":"fuzzyfinder.vim","src_id":"8500","5":"8500","creation_date":"1206671520","6":"1206671520"},{"0":"1984","vim_version":"7.0","1":"7.0","script_version":"2.5.1","2":"2.5.1","version_comment":"- Fixed to be able to match \"foo\/.\/bar\" by \"foo\/**\/bar\" in File mode.\r\n- Fixed to be able to open a space-containing file in File mode.\r\n- Fixed to honor the current working directory properly in File mode.\r\n","3":"- Fixed to be able to match \"foo\/.\/bar\" by \"foo\/**\/bar\" in File mode.\r\n- Fixed to be able to open a space-containing file in File mode.\r\n- Fixed to honor the current working directory properly in File mode.\r\n","package":"fuzzyfinder.vim","4":"fuzzyfinder.vim","src_id":"8485","5":"8485","creation_date":"1206185937","6":"1206185937"},{"0":"1984","vim_version":"7.0","1":"7.0","script_version":"2.5","2":"2.5","version_comment":"- Fixed the bug that a wrong initial text is entered after switching to a\r\n  next mode.\r\n- Fixed the bug that it does not return to previous window after leaving\r\n  Fuzzyfinder one.\r\n","3":"- Fixed the bug that a wrong initial text is entered after switching to a\r\n  next mode.\r\n- Fixed the bug that it does not return to previous window after leaving\r\n  Fuzzyfinder one.\r\n","package":"fuzzyfinder.vim","4":"fuzzyfinder.vim","src_id":"8327","5":"8327","creation_date":"1203664893","6":"1203664893"},{"0":"1984","vim_version":"7.0","1":"7.0","script_version":"2.4","2":"2.4","version_comment":"- Fixed the bug that Fuzzyfinder fails to open a file caused by auto-cd\r\n  plugin\/script.\r\n","3":"- Fixed the bug that Fuzzyfinder fails to open a file caused by auto-cd\r\n  plugin\/script.\r\n","package":"fuzzyfinder.vim","4":"fuzzyfinder.vim","src_id":"8315","5":"8315","creation_date":"1203498696","6":"1203498696"},{"0":"1984","vim_version":"7.0","1":"7.0","script_version":"2.3","2":"2.3","version_comment":"- Added a key mapping to open items in a new tab page and\r\n  g:FuzzyFinderOptions.Base.key_open_tab opton.\r\n- Changed to show Fuzzyfinder window above last window even if\r\n  'splitbelow' was set.\r\n- Changed to set nocursorline and nocursorcolumn in Fuzzyfinder.\r\n- Fixed not to push up a buffer number unlimitedly.\r\n","3":"- Added a key mapping to open items in a new tab page and\r\n  g:FuzzyFinderOptions.Base.key_open_tab opton.\r\n- Changed to show Fuzzyfinder window above last window even if\r\n  'splitbelow' was set.\r\n- Changed to set nocursorline and nocursorcolumn in Fuzzyfinder.\r\n- Fixed not to push up a buffer number unlimitedly.\r\n","package":"fuzzyfinder.vim","4":"fuzzyfinder.vim","src_id":"8308","5":"8308","creation_date":"1203410869","6":"1203410869"},{"0":"1984","vim_version":"7.0","1":"7.0","script_version":"2.2","2":"2.2","version_comment":"- Added new feature, which is the partial matching.\r\n- Fixed the bug that an error occurs when \"'\" was entered.\r\n","3":"- Added new feature, which is the partial matching.\r\n- Fixed the bug that an error occurs when \"'\" was entered.\r\n","package":"fuzzyfinder.vim","4":"fuzzyfinder.vim","src_id":"8299","5":"8299","creation_date":"1203315360","6":"1203315360"},{"0":"1984","vim_version":"7.0","1":"7.0","script_version":"2.1","2":"2.1","version_comment":"- Restructured the option system AGAIN. Sorry :p\r\n- Changed to inherit a typed text when switching a mode without leaving\r\n  a insert mode.\r\n- Changed commands which launch explorers to be able to take a argument\r\n  for initial text.\r\n- Changed to complete file names by relative path and not full path in\r\n  the buffer\/mru-file\/tagged-file mode.\r\n- Changed to highlight a typed text when the completion item was not\r\n  found or the completion process was aborted.\r\n- Changed to create caches for each tag file and not working directory\r\n  in the tag\/tagged-file mode.\r\n- Fixed the bug that the buffer mode couldn't open a unnamed buffer.\r\n- Added 'matching_limit' option.\r\n- Removed 'max_match' option. Use 'matching_limit' option instead.\r\n- Removed 'initial_text' option. Use command argument instead.\r\n- Removed the MRU-command mode.\r\n","3":"- Restructured the option system AGAIN. Sorry :p\r\n- Changed to inherit a typed text when switching a mode without leaving\r\n  a insert mode.\r\n- Changed commands which launch explorers to be able to take a argument\r\n  for initial text.\r\n- Changed to complete file names by relative path and not full path in\r\n  the buffer\/mru-file\/tagged-file mode.\r\n- Changed to highlight a typed text when the completion item was not\r\n  found or the completion process was aborted.\r\n- Changed to create caches for each tag file and not working directory\r\n  in the tag\/tagged-file mode.\r\n- Fixed the bug that the buffer mode couldn't open a unnamed buffer.\r\n- Added 'matching_limit' option.\r\n- Removed 'max_match' option. Use 'matching_limit' option instead.\r\n- Removed 'initial_text' option. Use command argument instead.\r\n- Removed the MRU-command mode.\r\n","package":"fuzzyfinder.vim","4":"fuzzyfinder.vim","src_id":"8291","5":"8291","creation_date":"1203239116","6":"1203239116"},{"0":"1984","vim_version":"7.0","1":"7.0","script_version":"2.0","2":"2.0","version_comment":"- Added the tag mode.\r\n- Added the tagged-file mode.\r\n- Added :FuzzyFinderRemoveCache command.\r\n- Restructured the option system. many options are changed names or\r\n  default values of some options.\r\n- Changed to hold and reuse caches of completion lists by default.\r\n- Changed to set filetype 'fuzzyfinder'.\r\n- Disabled the MRU-command mode by default because there are problems.\r\n- Removed FuzzyFinderAddMode command.","3":"- Added the tag mode.\r\n- Added the tagged-file mode.\r\n- Added :FuzzyFinderRemoveCache command.\r\n- Restructured the option system. many options are changed names or\r\n  default values of some options.\r\n- Changed to hold and reuse caches of completion lists by default.\r\n- Changed to set filetype 'fuzzyfinder'.\r\n- Disabled the MRU-command mode by default because there are problems.\r\n- Removed FuzzyFinderAddMode command.","package":"fuzzyfinder.vim","4":"fuzzyfinder.vim","src_id":"8118","5":"8118","creation_date":"1199397458","6":"1199397458"},{"0":"1984","vim_version":"7.0","1":"7.0","script_version":"1.5","2":"1.5","version_comment":"- Added the directory mode.\r\n- Fixed the bug that it caused an error when switch a mode in the\r\n  insert mode.\r\n- Changed g:FuzzyFinder_KeySwitchMode type to a list.\r\n","3":"- Added the directory mode.\r\n- Fixed the bug that it caused an error when switch a mode in the\r\n  insert mode.\r\n- Changed g:FuzzyFinder_KeySwitchMode type to a list.\r\n","package":"fuzzyfinder.vim","4":"fuzzyfinder.vim","src_id":"7906","5":"7906","creation_date":"1194569861","6":"1194569861"},{"0":"1984","vim_version":"7.0","1":"7.0","script_version":"1.4.1","2":"1.4.1","version_comment":"- Changed the specification of the information file.\r\n- Added the MRU-commands mode.\r\n- Renamed :FuzzyFinderAddFavorite command to :FuzzyFinderAddFavFile.\r\n- Renamed g:FuzzyFinder_MruModeVars option to\r\n  g:FuzzyFinder_MruFileModeVars.\r\n- Renamed g:FuzzyFinder_FavoriteModeVars option to\r\n  g:FuzzyFinder_FavFileModeVars.\r\n- Changed to show registered time of each item in MRU\/favorite mode.\r\n- Added 'timeFormat' option for MRU\/favorite modes. ","3":"- Changed the specification of the information file.\r\n- Added the MRU-commands mode.\r\n- Renamed :FuzzyFinderAddFavorite command to :FuzzyFinderAddFavFile.\r\n- Renamed g:FuzzyFinder_MruModeVars option to\r\n  g:FuzzyFinder_MruFileModeVars.\r\n- Renamed g:FuzzyFinder_FavoriteModeVars option to\r\n  g:FuzzyFinder_FavFileModeVars.\r\n- Changed to show registered time of each item in MRU\/favorite mode.\r\n- Added 'timeFormat' option for MRU\/favorite modes. ","package":"fuzzyfinder.vim","4":"fuzzyfinder.vim","src_id":"7822","5":"7822","creation_date":"1193191130","6":"1193191130"},{"0":"1984","vim_version":"7.0","1":"7.0","script_version":"1.3","2":"1.3","version_comment":"- Fixed a handling of multi-byte characters.","3":"- Fixed a handling of multi-byte characters.","package":"fuzzyfinder.vim","4":"fuzzyfinder.vim","src_id":"7811","5":"7811","creation_date":"1192757909","6":"1192757909"},{"0":"1984","vim_version":"7.0","1":"7.0","script_version":"1.2","2":"1.2","version_comment":"- Added support for Migemo. (Migemo is Japanese search method.)\r\n","3":"- Added support for Migemo. (Migemo is Japanese search method.)\r\n","package":"fuzzyfinder.vim","4":"fuzzyfinder.vim","src_id":"7800","5":"7800","creation_date":"1192498276","6":"1192498276"},{"0":"1984","vim_version":"7.0","1":"7.0","script_version":"1.1","2":"1.1","version_comment":"- Added the favorite mode.\r\n- Added new features, which are abbreviations and multiple search.\r\n- Added 'abbrevMap' option for each mode.\r\n- Added g:FuzzyFinder_MruModeVars['ignoreSpecialBuffers'] option.\r\n- Fixed the bug that it did not work correctly when a user have mapped\r\n  <C-p> or <Down>.\r\n","3":"- Added the favorite mode.\r\n- Added new features, which are abbreviations and multiple search.\r\n- Added 'abbrevMap' option for each mode.\r\n- Added g:FuzzyFinder_MruModeVars['ignoreSpecialBuffers'] option.\r\n- Fixed the bug that it did not work correctly when a user have mapped\r\n  <C-p> or <Down>.\r\n","package":"fuzzyfinder.vim","4":"fuzzyfinder.vim","src_id":"7794","5":"7794","creation_date":"1192404090","6":"1192404090"},{"0":"1984","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"- Added the MRU mode.\r\n- Added commands to add and use original mode.\r\n- Improved the sorting algorithm for completion items.\r\n- Added 'initialInput' option to automatically insert a text at the\r\n  beginning of a mode.\r\n- Changed that 'excludedPath' option works for the entire path.\r\n- Renamed some options. \r\n- Changed default values of some options. \r\n- Packed the mode-specific options to dictionaries.\r\n- Removed some options.\r\n","3":"- Added the MRU mode.\r\n- Added commands to add and use original mode.\r\n- Improved the sorting algorithm for completion items.\r\n- Added 'initialInput' option to automatically insert a text at the\r\n  beginning of a mode.\r\n- Changed that 'excludedPath' option works for the entire path.\r\n- Renamed some options. \r\n- Changed default values of some options. \r\n- Packed the mode-specific options to dictionaries.\r\n- Removed some options.\r\n","package":"fuzzyfinder.vim","4":"fuzzyfinder.vim","src_id":"7767","5":"7767","creation_date":"1191864582","6":"1191864582"},{"0":"1984","vim_version":"7.0","1":"7.0","script_version":"0.6","2":"0.6","version_comment":"- Fixed some bugs.","3":"- Fixed some bugs.","package":"fuzzyfinder.vim","4":"fuzzyfinder.vim","src_id":"7664","5":"7664","creation_date":"1189623905","6":"1189623905"},{"0":"1984","vim_version":"7.0","1":"7.0","script_version":"0.5","2":"0.5","version_comment":"- Improved response by aborting processing too many items.\r\n- Changed to be able to open a buffer\/file not only in previous\r\n  window but also in new window.\r\n- Fixed a bug that recursive searching with '**' does not work.\r\n- Added g:FuzzyFinder_CompletionItemLimit option.\r\n- Added g:FuzzyFinder_KeyOpen option.\r\n","3":"- Improved response by aborting processing too many items.\r\n- Changed to be able to open a buffer\/file not only in previous\r\n  window but also in new window.\r\n- Fixed a bug that recursive searching with '**' does not work.\r\n- Added g:FuzzyFinder_CompletionItemLimit option.\r\n- Added g:FuzzyFinder_KeyOpen option.\r\n","package":"fuzzyfinder.vim","4":"fuzzyfinder.vim","src_id":"7647","5":"7647","creation_date":"1189499244","6":"1189499244"},{"0":"1984","vim_version":"7.0","1":"7.0","script_version":"0.4","2":"0.4","version_comment":"- Improved response of the input.\r\n- Improved the sorting algorithm for completion items. It is based\r\n  on the matching level. 1st is perfect matching, 2nd is prefix\r\n  matching, and 3rd is fuzzy matching.\r\n- Added g:FuzzyFinder_ExcludePattern option.\r\n- Removed g:FuzzyFinder_WildIgnore option.\r\n- Removed g:FuzzyFinder_EchoPattern option.\r\n- Removed g:FuzzyFinder_PathSeparator option.\r\n- Changed the default value of g:FuzzyFinder_MinLengthFile from 1 to\r\n  0.\r\n","3":"- Improved response of the input.\r\n- Improved the sorting algorithm for completion items. It is based\r\n  on the matching level. 1st is perfect matching, 2nd is prefix\r\n  matching, and 3rd is fuzzy matching.\r\n- Added g:FuzzyFinder_ExcludePattern option.\r\n- Removed g:FuzzyFinder_WildIgnore option.\r\n- Removed g:FuzzyFinder_EchoPattern option.\r\n- Removed g:FuzzyFinder_PathSeparator option.\r\n- Changed the default value of g:FuzzyFinder_MinLengthFile from 1 to\r\n  0.\r\n","package":"fuzzyfinder.vim","4":"fuzzyfinder.vim","src_id":"7626","5":"7626","creation_date":"1189148460","6":"1189148460"},{"0":"1984","vim_version":"7.0","1":"7.0","script_version":"0.3","2":"0.3","version_comment":"- Added g:FuzzyFinder_IgnoreCase option.\r\n- Added g:FuzzyFinder_KeyToggleIgnoreCase option.\r\n- Added g:FuzzyFinder_EchoPattern option.\r\n- Changed the open command in a buffer mode from \":edit\" to\r\n\":buffer\" to avoid being reset cursor position.\r\n- Changed the default value of g:FuzzyFinder_KeyToggleMode from\r\n<C-Space> to <F12> because <C-Space> does not work on some CUI\r\nenvironments.\r\n- Changed to avoid being loaded by Vim before 7.0.\r\n- Fixed a bug with making a fuzzy pattern which has '\\'.\r\n","3":"- Added g:FuzzyFinder_IgnoreCase option.\r\n- Added g:FuzzyFinder_KeyToggleIgnoreCase option.\r\n- Added g:FuzzyFinder_EchoPattern option.\r\n- Changed the open command in a buffer mode from \":edit\" to\r\n\":buffer\" to avoid being reset cursor position.\r\n- Changed the default value of g:FuzzyFinder_KeyToggleMode from\r\n<C-Space> to <F12> because <C-Space> does not work on some CUI\r\nenvironments.\r\n- Changed to avoid being loaded by Vim before 7.0.\r\n- Fixed a bug with making a fuzzy pattern which has '\\'.\r\n","package":"fuzzyfinder.vim","4":"fuzzyfinder.vim","src_id":"7486","5":"7486","creation_date":"1186739167","6":"1186739167"},{"0":"1984","vim_version":"7.0","1":"7.0","script_version":"0.2","2":"0.2","version_comment":"A bug it does not work on Linux is fixed.","3":"A bug it does not work on Linux is fixed.","package":"fuzzyfinder.vim","4":"fuzzyfinder.vim","src_id":"7477","5":"7477","creation_date":"1186620568","6":"1186620568"},{"0":"1984","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"fuzzyfinder.vim","4":"fuzzyfinder.vim","src_id":"7467","5":"7467","creation_date":"1186544369","6":"1186544369"}]},"1983":{"script_id":"1983","0":"1983","script_name":"GtagsClient","1":"GtagsClient","script_type":"utility","2":"utility","summary":"A client for Google Gtags","3":"A client for Google Gtags","description":"Google Gtags is an extension to GNU Emacs and X-Emacs TAGS functionality, with a server-side component that narrows down the view of a potentially large TAGS file and serves the narrowed view over the wire for better performance. Google Gtags could be downloaded from http:\/\/code.google.com\/p\/google-gtags\/ .\r\n\r\nThis plugin is a Vim client to Googe Gtags. With this plugin, you could easily set up many projects in your workstation, and use different Gtags servers in different projects automatically. The only thing you should do is putting a text file named \".gtags\" in the project root directory, write the servers' information in this file, one line per server. The description format is:\r\n\r\nlanguage,type,hostname,port\r\n\r\nFor example:\r\n\r\nc++,definition,my.server.org,8928\r\nc++,callgraph,my.server.org,8929\r\npython,definition,my.server.org,8930\r\npython,callgraph,my.server.org,8931\r\n\r\nThen when you open any files under this directory (including all sub directories), your Vim will use these servers for tags looking up.\r\n\r\nThe server auto-selection doesn't work with \"mixer\" feature.  So if you want to use the server auto-selection feature, you should disable the mixer feature by typing \":let g:google_tags_use_mixer=0\", or put the following lines in your .vimrc.\r\n\r\n\" Gtags\r\nlet g:google_tags_use_mixer=0","4":"Google Gtags is an extension to GNU Emacs and X-Emacs TAGS functionality, with a server-side component that narrows down the view of a potentially large TAGS file and serves the narrowed view over the wire for better performance. Google Gtags could be downloaded from http:\/\/code.google.com\/p\/google-gtags\/ .\r\n\r\nThis plugin is a Vim client to Googe Gtags. With this plugin, you could easily set up many projects in your workstation, and use different Gtags servers in different projects automatically. The only thing you should do is putting a text file named \".gtags\" in the project root directory, write the servers' information in this file, one line per server. The description format is:\r\n\r\nlanguage,type,hostname,port\r\n\r\nFor example:\r\n\r\nc++,definition,my.server.org,8928\r\nc++,callgraph,my.server.org,8929\r\npython,definition,my.server.org,8930\r\npython,callgraph,my.server.org,8931\r\n\r\nThen when you open any files under this directory (including all sub directories), your Vim will use these servers for tags looking up.\r\n\r\nThe server auto-selection doesn't work with \"mixer\" feature.  So if you want to use the server auto-selection feature, you should disable the mixer feature by typing \":let g:google_tags_use_mixer=0\", or put the following lines in your .vimrc.\r\n\r\n\" Gtags\r\nlet g:google_tags_use_mixer=0","install_details":"This plugin is compressed in VimBall format. So you may need to install the latest version of vimscript #1502 first.\r\n\r\nThen the only thing you should do is just downloading the Vimball, opening it in Vim and typing this command followed by an enter in your Vim:\r\n\r\n:so %","5":"This plugin is compressed in VimBall format. So you may need to install the latest version of vimscript #1502 first.\r\n\r\nThen the only thing you should do is just downloading the Vimball, opening it in Vim and typing this command followed by an enter in your Vim:\r\n\r\n:so %","first_name":"Edward","6":"Edward","last_name":"Fox","7":"Fox","releases":[{"0":"1983","vim_version":"7.0","1":"7.0","script_version":"0.12","2":"0.12","version_comment":"Upgraded from the upstream, using google-gtags 2.0.","3":"Upgraded from the upstream, using google-gtags 2.0.","package":"GtagsClient.vba.gz","4":"GtagsClient.vba.gz","src_id":"10368","5":"10368","creation_date":"1239252593","6":"1239252593"},{"0":"1983","vim_version":"7.0","1":"7.0","script_version":"0.11","2":"0.11","version_comment":"Added \"GetLatestVimScripts\" support so that you could obtain the latest updated version of this script automatically with the help of vimscript #642.","3":"Added \"GetLatestVimScripts\" support so that you could obtain the latest updated version of this script automatically with the help of vimscript #642.","package":"GtagsClient.vba.gz","4":"GtagsClient.vba.gz","src_id":"7474","5":"7474","creation_date":"1186603095","6":"1186603095"},{"0":"1983","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"GtagsClient.vba.gz","4":"GtagsClient.vba.gz","src_id":"7463","5":"7463","creation_date":"1186540780","6":"1186540780"}]},"1982":{"script_id":"1982","0":"1982","script_name":"vimff","1":"vimff","script_type":"utility","2":"utility","summary":"Connection between common-lisp and vim.","3":"Connection between common-lisp and vim.","description":"Connection between common-lisp and vim.\r\nby pressing 'e' will send form to common-lisp.\r\nCurrently tested on on sbcl.\r\n\r\nfor more info and latest code: http:\/\/www.valkama.se\/software\/vimff\/\r\n","4":"Connection between common-lisp and vim.\r\nby pressing 'e' will send form to common-lisp.\r\nCurrently tested on on sbcl.\r\n\r\nfor more info and latest code: http:\/\/www.valkama.se\/software\/vimff\/\r\n","install_details":"1) unpack with bzip2\r\n2) read readme.txt","5":"1) unpack with bzip2\r\n2) read readme.txt","first_name":"larry","6":"larry","last_name":"valkama","7":"valkama","releases":[{"0":"1982","vim_version":"7.0","1":"7.0","script_version":"20070810","2":"20070810","version_comment":"* form lisp evaluation\r\n* symbol completion\r\n* symbol help","3":"* form lisp evaluation\r\n* symbol completion\r\n* symbol help","package":"vimff-20070810.tar.bz2","4":"vimff-20070810.tar.bz2","src_id":"7483","5":"7483","creation_date":"1186716417","6":"1186716417"}]},"1981":{"script_id":"1981","0":"1981","script_name":"halfmove","1":"halfmove","script_type":"utility","2":"utility","summary":"Move the cursor half way up or down the screen","3":"Move the cursor half way up or down the screen","description":"Vim script to move the cursor half way down\/up the screen. This can be\r\nthought of as a binary search for a line that is visible in the window by\r\neither moving up or down.\r\n\r\nCreated:\t2007 Aug 05\r\nLast Change:\t2007 Aug 05\r\nAuthor:\tAndy Spencer <andy753421 at gmail dot com>\r\nThanks To:\t#vim@irc.freenode.net\r\n\r\nUsage:\r\n  Press <C-K> to jump half way to the top of the screen\r\n  Press <C-J> to jump half way to the bottom of the screen\r\n  Pressing <C-[KJ]> several times in a row will jump halfway to the\r\n  top\/bottom or half way to a previous jump location.\r\n  Example: To jump 3\/8 of the way to the bottom of the screen press\r\n    <C-J><C-K><C-J>\r\n  \r\nCustomization:\r\n  map <silent> <YOUR-DOWN-KEY> :call HM_Move(\"down\")<CR>\r\n  map <silent> <YOUR-UP-KEY>   :call HM_Move(\"up\")<CR>\r\n\r\nProblems:\r\n  <C-J> and <C-K> will not be mapped over existing mappings. If other\r\n  scripts map <C-J> or <C-K> then you will need to manually override those.","4":"Vim script to move the cursor half way down\/up the screen. This can be\r\nthought of as a binary search for a line that is visible in the window by\r\neither moving up or down.\r\n\r\nCreated:\t2007 Aug 05\r\nLast Change:\t2007 Aug 05\r\nAuthor:\tAndy Spencer <andy753421 at gmail dot com>\r\nThanks To:\t#vim@irc.freenode.net\r\n\r\nUsage:\r\n  Press <C-K> to jump half way to the top of the screen\r\n  Press <C-J> to jump half way to the bottom of the screen\r\n  Pressing <C-[KJ]> several times in a row will jump halfway to the\r\n  top\/bottom or half way to a previous jump location.\r\n  Example: To jump 3\/8 of the way to the bottom of the screen press\r\n    <C-J><C-K><C-J>\r\n  \r\nCustomization:\r\n  map <silent> <YOUR-DOWN-KEY> :call HM_Move(\"down\")<CR>\r\n  map <silent> <YOUR-UP-KEY>   :call HM_Move(\"up\")<CR>\r\n\r\nProblems:\r\n  <C-J> and <C-K> will not be mapped over existing mappings. If other\r\n  scripts map <C-J> or <C-K> then you will need to manually override those.","install_details":"Add this file to $RUNTIME\/plugins","5":"Add this file to $RUNTIME\/plugins","first_name":"Andy","6":"Andy","last_name":"Spencer","7":"Spencer","releases":[{"0":"1981","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"halfmove.vim","4":"halfmove.vim","src_id":"7450","5":"7450","creation_date":"1186256566","6":"1186256566"}]},"1980":{"script_id":"1980","0":"1980","script_name":"vimremote.sh","1":"vimremote.sh","script_type":"utility","2":"utility","summary":"script to use gvim from IDE","3":"script to use gvim from IDE","description":"I wanted to use vim from the Xilinx ide, and I like the following actions to occur from the IDE\r\n\r\n\r\n1) open every file in a split window in one gvim session\r\n2) when opening the same file again from the IDE, don't cause a new split window if there is already one\r\n3) use the line numbers provided by the ide.\r\n\r\nIn Xilinx you would define the external editor call \r\n\r\n\/path\/to\/vimremote.sh XILINX $1 $2\r\n\r\nThe XILINX is just a name so that one particular gvim session is used for it, and not any others you might have hanging around\r\n\r\nYou need a decent shell. Don't know how that works in Windows. This script could be useful in many other ide's that allow calls to external editors","4":"I wanted to use vim from the Xilinx ide, and I like the following actions to occur from the IDE\r\n\r\n\r\n1) open every file in a split window in one gvim session\r\n2) when opening the same file again from the IDE, don't cause a new split window if there is already one\r\n3) use the line numbers provided by the ide.\r\n\r\nIn Xilinx you would define the external editor call \r\n\r\n\/path\/to\/vimremote.sh XILINX $1 $2\r\n\r\nThe XILINX is just a name so that one particular gvim session is used for it, and not any others you might have hanging around\r\n\r\nYou need a decent shell. Don't know how that works in Windows. This script could be useful in many other ide's that allow calls to external editors","install_details":"Just put the file somewhere on your harddisk, and configure your IDE to use it. The call to vimremote.sh has 3 parameters:\r\n1) unique name for the gvim to associate with a certain IDE\r\n2) filename\r\n3) (optional) line number in the file","5":"Just put the file somewhere on your harddisk, and configure your IDE to use it. The call to vimremote.sh has 3 parameters:\r\n1) unique name for the gvim to associate with a certain IDE\r\n2) filename\r\n3) (optional) line number in the file","first_name":"Bart","6":"Bart","last_name":"van Deenen","7":"van Deenen","releases":[{"0":"1980","vim_version":"6.0","1":"6.0","script_version":"1.01","2":"1.01","version_comment":"Does not require file to exist. Everything else the same","3":"Does not require file to exist. Everything else the same","package":"vimremote.sh","4":"vimremote.sh","src_id":"7449","5":"7449","creation_date":"1186224542","6":"1186224542"}]},"1979":{"script_id":"1979","0":"1979","script_name":"Sass","1":"Sass","script_type":"syntax","2":"syntax","summary":"Sass syntax highlight","3":"Sass syntax highlight","description":"This is the syntax highlighting mode for Sass (http:\/\/haml.hamptoncatlin.com\/) -- Syntactically Awesome StyleSheets\r\n\r\nScreenshot: http:\/\/www.flickr.com\/photos\/dmitryilyashevich\/1006425093\/","4":"This is the syntax highlighting mode for Sass (http:\/\/haml.hamptoncatlin.com\/) -- Syntactically Awesome StyleSheets\r\n\r\nScreenshot: http:\/\/www.flickr.com\/photos\/dmitryilyashevich\/1006425093\/","install_details":"put it into syntax directory and add sass filetype\r\n\r\nau! BufRead,BufNewFile *.sass         setfiletype sass\r\n\r\nin your filetype.vim","5":"put it into syntax directory and add sass filetype\r\n\r\nau! BufRead,BufNewFile *.sass         setfiletype sass\r\n\r\nin your filetype.vim","first_name":"Dmitry","6":"Dmitry","last_name":"Ilyashevich","7":"Ilyashevich","releases":[{"0":"1979","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"sass.vim","4":"sass.vim","src_id":"7447","5":"7447","creation_date":"1186206984","6":"1186206984"}]},"1978":{"script_id":"1978","0":"1978","script_name":"Easy alignment to column","1":"Easy alignment to column","script_type":"utility","2":"utility","summary":"Quickly align a word to a predefined column","3":"Quickly align a word to a predefined column","description":"This script was made to ease typing programming code like:\r\n\r\n    int                        someVariable;\r\n    double                     foo;\r\n    std::vector< std::string > andSomeLongerName;\r\n\r\n(If this doesn't look nicely aligned it's because you're not viewing it using a fixed-width font.)\r\n\r\nThe attached script allows you to quickly align the variable names on the same (virtual) column. It defines two mappings for this:\r\n\r\n  ,a : Align the current cursor to the predefined column.\r\n  ,A : Try to find the alignment column automatically on the previous line.\r\n\r\n(Replace , with your g:mapleader.)\r\n\r\nThe first mapping actually does want we want to achieve, but the latter makes it really easy to use. It looks for the separating gap, which is \\s\\s (two consecutive white-space characters), and a single tab (following by anything) as a plan B. This may not always work of course. To specify the column, I hijack one of your mark (c in this case), which you can always set manually. If you don't want mark c to be sacrificed to the script, it's very easy to adapt it and make it use another (by editing the key mappings in the file).\r\n\r\nThe variable g:align_uses_tabs can be reset if you want the script to only insert spaces. Else, it inserts as many tabs as possible, than \"fine-tunes\" using spaces.\r\n","4":"This script was made to ease typing programming code like:\r\n\r\n    int                        someVariable;\r\n    double                     foo;\r\n    std::vector< std::string > andSomeLongerName;\r\n\r\n(If this doesn't look nicely aligned it's because you're not viewing it using a fixed-width font.)\r\n\r\nThe attached script allows you to quickly align the variable names on the same (virtual) column. It defines two mappings for this:\r\n\r\n  ,a : Align the current cursor to the predefined column.\r\n  ,A : Try to find the alignment column automatically on the previous line.\r\n\r\n(Replace , with your g:mapleader.)\r\n\r\nThe first mapping actually does want we want to achieve, but the latter makes it really easy to use. It looks for the separating gap, which is \\s\\s (two consecutive white-space characters), and a single tab (following by anything) as a plan B. This may not always work of course. To specify the column, I hijack one of your mark (c in this case), which you can always set manually. If you don't want mark c to be sacrificed to the script, it's very easy to adapt it and make it use another (by editing the key mappings in the file).\r\n\r\nThe variable g:align_uses_tabs can be reset if you want the script to only insert spaces. Else, it inserts as many tabs as possible, than \"fine-tunes\" using spaces.\r\n","install_details":"","5":"","first_name":"Niels","6":"Niels","last_name":"Aan de Brugh","7":"Aan de Brugh","releases":[{"0":"1978","vim_version":"6.0","1":"6.0","script_version":"0.2.1","2":"0.2.1","version_comment":"Added key mapping for align (,a) and using Unix EOLs now (thanks to Maarten Bressers for noticing).","3":"Added key mapping for align (,a) and using Unix EOLs now (thanks to Maarten Bressers for noticing).","package":"alignment.vim","4":"alignment.vim","src_id":"7665","5":"7665","creation_date":"1189675924","6":"1189675924"},{"0":"1978","vim_version":"6.0","1":"6.0","script_version":"0.2","2":"0.2","version_comment":"Fix for expandtab.\r\nAlign at white-space at the beginning of a line too.","3":"Fix for expandtab.\r\nAlign at white-space at the beginning of a line too.","package":"alignment.vim","4":"alignment.vim","src_id":"7577","5":"7577","creation_date":"1188379062","6":"1188379062"},{"0":"1978","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"alignment.vim","4":"alignment.vim","src_id":"7442","5":"7442","creation_date":"1186136289","6":"1186136289"}]},"1977":{"script_id":"1977","0":"1977","script_name":"rcscript","1":"rcscript","script_type":"indent","2":"indent","summary":"RcScript indent file","3":"RcScript indent file","description":"RcScript is a scripting language developed by RainCode. For more information see http:\/\/www.raincode.com.","4":"RcScript is a scripting language developed by RainCode. For more information see http:\/\/www.raincode.com.","install_details":"","5":"","first_name":"Hans","6":"Hans","last_name":"Winderix","7":"Winderix","releases":[{"0":"1977","vim_version":"6.0","1":"6.0","script_version":"1.0.0","2":"1.0.0","version_comment":"Initial upload","3":"Initial upload","package":"rcscript.vim","4":"rcscript.vim","src_id":"7437","5":"7437","creation_date":"1185961881","6":"1185961881"}]},"1976":{"script_id":"1976","0":"1976","script_name":"rcscript","1":"rcscript","script_type":"syntax","2":"syntax","summary":"RcScript syntax file","3":"RcScript syntax file","description":"RcScript is a scripting language developed by RainCode. For more information see http:\/\/www.raincode.com.","4":"RcScript is a scripting language developed by RainCode. For more information see http:\/\/www.raincode.com.","install_details":"","5":"","first_name":"Hans","6":"Hans","last_name":"Winderix","7":"Winderix","releases":[{"0":"1976","vim_version":"6.0","1":"6.0","script_version":"1.0.0","2":"1.0.0","version_comment":"Initial upload","3":"Initial upload","package":"rcscript.vim","4":"rcscript.vim","src_id":"7436","5":"7436","creation_date":"1185961443","6":"1185961443"}]},"1975":{"script_id":"1975","0":"1975","script_name":"lettuce.vim","1":"lettuce.vim","script_type":"color scheme","2":"color scheme","summary":"highly detalized dark scheme for gui and 256 color terminal","3":"highly detalized dark scheme for gui and 256 color terminal","description":"Detalized and nice-looking color scheme with dark background.\r\nCan be used in gui and 256 color terminal.\r\nHighlights statusline in insert mode.\r\nImproved highlighting for c, cpp, ruby and javascript languages.\r\n\r\nAlso following option is recommended (put it to your .vimrc):\r\nset fillchars=vert:\\ ,fold:\\ \" <- trailing space","4":"Detalized and nice-looking color scheme with dark background.\r\nCan be used in gui and 256 color terminal.\r\nHighlights statusline in insert mode.\r\nImproved highlighting for c, cpp, ruby and javascript languages.\r\n\r\nAlso following option is recommended (put it to your .vimrc):\r\nset fillchars=vert:\\ ,fold:\\ \" <- trailing space","install_details":"put lettuce.vim to ~\/.vim\/colors\/","5":"put lettuce.vim to ~\/.vim\/colors\/","first_name":"Valentin","6":"Valentin","last_name":"Valyaeff","7":"Valyaeff","releases":[{"0":"1975","vim_version":"7.0","1":"7.0","script_version":"1.2","2":"1.2","version_comment":"Improved highlighting for c, cpp, ruby and javascript","3":"Improved highlighting for c, cpp, ruby and javascript","package":"lettuce.vim","4":"lettuce.vim","src_id":"7471","5":"7471","creation_date":"1186586069","6":"1186586069"},{"0":"1975","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"lettuce.vim","4":"lettuce.vim","src_id":"7431","5":"7431","creation_date":"1185838263","6":"1185838263"}]},"1974":{"script_id":"1974","0":"1974","script_name":"pyconsole_vim.vim","1":"pyconsole_vim.vim","script_type":"utility","2":"utility","summary":"PyConsole - embedded console session in windows Vim","3":"PyConsole - embedded console session in windows Vim","description":"This plugin allows for the execution of windows based command line commands such as \"dir\", \"findstr\" or \"ping\" directly within a vim buffer.\r\n\r\nStart up an embedded console from within vim by:\r\n        :call PyConsole()\r\n    or the windows command line by:\r\n        gvim \"+call PyConsole()\"\r\n\r\nSee http:\/\/pyconsole.googlecode.com\/ for a flash demo.\r\n\r\nRequirements:\r\n- Vim 7.0 or above: http:\/\/www.vim.org\/download.php#pc\r\n- Python 2.4 or above: http:\/\/www.python.org\/download\/windows\/\r\n- Python for Windows extensions: http:\/\/sourceforge.net\/projects\/pywin32\/\r\n- Python ctypes module (not necessary for Python 2.5 and above): http:\/\/sourceforge.net\/projects\/ctypes\/\r\n\r\nBased on the Python PyConsole project.\r\n","4":"This plugin allows for the execution of windows based command line commands such as \"dir\", \"findstr\" or \"ping\" directly within a vim buffer.\r\n\r\nStart up an embedded console from within vim by:\r\n        :call PyConsole()\r\n    or the windows command line by:\r\n        gvim \"+call PyConsole()\"\r\n\r\nSee http:\/\/pyconsole.googlecode.com\/ for a flash demo.\r\n\r\nRequirements:\r\n- Vim 7.0 or above: http:\/\/www.vim.org\/download.php#pc\r\n- Python 2.4 or above: http:\/\/www.python.org\/download\/windows\/\r\n- Python for Windows extensions: http:\/\/sourceforge.net\/projects\/pywin32\/\r\n- Python ctypes module (not necessary for Python 2.5 and above): http:\/\/sourceforge.net\/projects\/ctypes\/\r\n\r\nBased on the Python PyConsole project.\r\n","install_details":"Installation instructions:\r\n- Download pyconsole_vim.zip\r\n- Extract the files into your vim plugin directory (typically \"C:\\Program Files\\Vim\\vimfiles\\plugin\")\r\n","5":"Installation instructions:\r\n- Download pyconsole_vim.zip\r\n- Extract the files into your vim plugin directory (typically \"C:\\Program Files\\Vim\\vimfiles\\plugin\")\r\n","first_name":"Michael","6":"Michael","last_name":"Graz","7":"Graz","releases":[{"0":"1974","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"pyconsole_vim.zip","4":"pyconsole_vim.zip","src_id":"7429","5":"7429","creation_date":"1185802338","6":"1185802338"}]},"1973":{"script_id":"1973","0":"1973","script_name":"JET_toggle","1":"JET_toggle","script_type":"utility","2":"utility","summary":"Dynamically add sets of commands to toggle between with a hotkey","3":"Dynamically add sets of commands to toggle between with a hotkey","description":"<!-- === START_DOC\r\n*JET_toggle.txt*           Plugin to dynamically add toggles #version#\r\n\r\n\r\n                         JET_TOGGLE REFERENCE MANUAL~\r\n\r\n\r\n\r\n\r\n\r\n==============================================================================\r\nCONTENTS {{{2                                        *JET_togglelist-contents* \r\n\r\n    1. Intro ................................... |JET_toggle|\r\n    2. How to add a toggle ..................... |JET_toggle-howto|\r\n    3. Feedback ................................ |JET_toggle-feedback|\r\n\r\n==============================================================================\r\n1. Intro {{{2                                                     *JET_toggle*\r\n\r\n    JET_toggle provides a mechanism for adding toggle commands and mapping\r\n  them to a shortcut.\r\n\r\n==============================================================================\r\n2. How to add a toggle {{{2                                 *JET_toggle-howto*\r\n\r\n  Source the script from your .vimrc, and then add whatever toggles you want.\r\n  \r\n\r\n  Syntax:\r\n  \r\n    JET_AddToggle(':someCommandString', ':someOtherCommandString', '<keymap>')\r\n  \r\n  \r\n  Example:\r\n  \r\n    source ~\/.vim\/plugin\/JET_toggle.vim\r\n    JET_AddToggle(':set list', ':set nolist', '<C-l>')\r\n    JET_AddToggle(':set paste', ':set nopaste', '<M-p>')\r\n  \r\n\r\n    Then, when you type control-l it will toggle between ':set list' and\r\n  ':set nolist' and when you type alt-p it will toggle between ':set paste'\r\n  and ':set nopaste'.\r\n  \r\n==============================================================================\r\n3. Feedback {{{2                                         *JET_toggle-feedback*\r\n\r\n  Constructive feedback is welcome, send it to outtatime.at-symbol.gmail.com\r\n  with [JET_toggle] in the subject line.  Enjoy!\r\n-->","4":"<!-- === START_DOC\r\n*JET_toggle.txt*           Plugin to dynamically add toggles #version#\r\n\r\n\r\n                         JET_TOGGLE REFERENCE MANUAL~\r\n\r\n\r\n\r\n\r\n\r\n==============================================================================\r\nCONTENTS {{{2                                        *JET_togglelist-contents* \r\n\r\n    1. Intro ................................... |JET_toggle|\r\n    2. How to add a toggle ..................... |JET_toggle-howto|\r\n    3. Feedback ................................ |JET_toggle-feedback|\r\n\r\n==============================================================================\r\n1. Intro {{{2                                                     *JET_toggle*\r\n\r\n    JET_toggle provides a mechanism for adding toggle commands and mapping\r\n  them to a shortcut.\r\n\r\n==============================================================================\r\n2. How to add a toggle {{{2                                 *JET_toggle-howto*\r\n\r\n  Source the script from your .vimrc, and then add whatever toggles you want.\r\n  \r\n\r\n  Syntax:\r\n  \r\n    JET_AddToggle(':someCommandString', ':someOtherCommandString', '<keymap>')\r\n  \r\n  \r\n  Example:\r\n  \r\n    source ~\/.vim\/plugin\/JET_toggle.vim\r\n    JET_AddToggle(':set list', ':set nolist', '<C-l>')\r\n    JET_AddToggle(':set paste', ':set nopaste', '<M-p>')\r\n  \r\n\r\n    Then, when you type control-l it will toggle between ':set list' and\r\n  ':set nolist' and when you type alt-p it will toggle between ':set paste'\r\n  and ':set nopaste'.\r\n  \r\n==============================================================================\r\n3. Feedback {{{2                                         *JET_toggle-feedback*\r\n\r\n  Constructive feedback is welcome, send it to outtatime.at-symbol.gmail.com\r\n  with [JET_toggle] in the subject line.  Enjoy!\r\n-->","install_details":"Source it from your .vimrc file and it will do the rest.","5":"Source it from your .vimrc file and it will do the rest.","first_name":"Jai","6":"Jai","last_name":"Tkker","7":"Tkker","releases":[{"0":"1973","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"JET_toggle.vim","4":"JET_toggle.vim","src_id":"7425","5":"7425","creation_date":"1185632614","6":"1185632614"}]},"1972":{"script_id":"1972","0":"1972","script_name":"Parameter Helpers","1":"Parameter Helpers","script_type":"utility","2":"utility","summary":"[Programming] Useful functions for handling parameters in function calls","3":"[Programming] Useful functions for handling parameters in function calls","description":"This \"script\" is my initial attempt to ease a typical task that used to frustrate me: changing and moving around parameters in a typical function call.\r\n\r\nThe code is written for C\/C++ programmers (as well as language that inherit that syntax): change aap( \"noot\", &mies ) to aap( &mies, \"noot\" ) in a single keystroke if you want.\r\n\r\nI'm providing this code in the hope it will help some people out. It's not a plug-in. The code works nicely though.\r\n\r\nNote that the current code does NOT handle multi-line parameter lists. This is on the TODO list.\r\n\r\nFunctions:\r\nSavePositions and RestorePosiions: save and restore visual and cursor position respectively. Can be called multiple times. Uses script-global variables.\r\nInsideQuotedString: tries to determine if the cursor is inside a quoted string in a very imprecise way. Only useful to call if something strange is happening (like operator [( not working).\r\nParamRangeList: the brain stem. Constructs a list of virtual column offsets for the current parameter context.\r\nCurrentPosition: determine the offset in the list returned by ParamRangeList based on the current cursor position.\r\nShiftCurrentParam: function to substitute a parameter with another based on a delta in the offset of the list ParamRangeList returned. (e.g. -1 substitutes the CurrentPosition parameter with the one to the left).\r\n\r\nExample usage (assuming g:mapleader set):\r\nexec \"nmap \" .g:mapleader.\"p :call VisualizeParameter(0)<CR>\"\r\n\" if this is false shifting a parameter at offset 0 to left is an error, trivially analogous case for right shift\r\n\" if it's true a shift wraps around list boundaries\r\nlet g:param_shift_round_robin = 1\r\nexec \"nmap \" .g:mapleader.\"< :call ShiftCurrentParam(-1)<CR>\"\r\nexec \"nmap \" .g:mapleader.\"> :call ShiftCurrentParam(1)<CR>\"\r\n\r\nEverything seems to be sort of robust, I've done some tests, but no guarantees. Typical BSD license conditions apply.\r\n\r\nN.","4":"This \"script\" is my initial attempt to ease a typical task that used to frustrate me: changing and moving around parameters in a typical function call.\r\n\r\nThe code is written for C\/C++ programmers (as well as language that inherit that syntax): change aap( \"noot\", &mies ) to aap( &mies, \"noot\" ) in a single keystroke if you want.\r\n\r\nI'm providing this code in the hope it will help some people out. It's not a plug-in. The code works nicely though.\r\n\r\nNote that the current code does NOT handle multi-line parameter lists. This is on the TODO list.\r\n\r\nFunctions:\r\nSavePositions and RestorePosiions: save and restore visual and cursor position respectively. Can be called multiple times. Uses script-global variables.\r\nInsideQuotedString: tries to determine if the cursor is inside a quoted string in a very imprecise way. Only useful to call if something strange is happening (like operator [( not working).\r\nParamRangeList: the brain stem. Constructs a list of virtual column offsets for the current parameter context.\r\nCurrentPosition: determine the offset in the list returned by ParamRangeList based on the current cursor position.\r\nShiftCurrentParam: function to substitute a parameter with another based on a delta in the offset of the list ParamRangeList returned. (e.g. -1 substitutes the CurrentPosition parameter with the one to the left).\r\n\r\nExample usage (assuming g:mapleader set):\r\nexec \"nmap \" .g:mapleader.\"p :call VisualizeParameter(0)<CR>\"\r\n\" if this is false shifting a parameter at offset 0 to left is an error, trivially analogous case for right shift\r\n\" if it's true a shift wraps around list boundaries\r\nlet g:param_shift_round_robin = 1\r\nexec \"nmap \" .g:mapleader.\"< :call ShiftCurrentParam(-1)<CR>\"\r\nexec \"nmap \" .g:mapleader.\"> :call ShiftCurrentParam(1)<CR>\"\r\n\r\nEverything seems to be sort of robust, I've done some tests, but no guarantees. Typical BSD license conditions apply.\r\n\r\nN.","install_details":"","5":"","first_name":"Niels","6":"Niels","last_name":"Aan de Brugh","7":"Aan de Brugh","releases":[{"0":"1972","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"parameter_helpers.vim","4":"parameter_helpers.vim","src_id":"7423","5":"7423","creation_date":"1185555753","6":"1185555753"}]},"1971":{"script_id":"1971","0":"1971","script_name":"trivial256","1":"trivial256","script_type":"color scheme","2":"color scheme","summary":"trivial color scheme for terminals","3":"trivial color scheme for terminals","description":"Trivial color scheme: light background, no-gui terminals.","4":"Trivial color scheme: light background, no-gui terminals.","install_details":"","5":"","first_name":"nobody","6":"nobody","last_name":"isageek","7":"isageek","releases":[{"0":"1971","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"trivial256.vim","4":"trivial256.vim","src_id":"7422","5":"7422","creation_date":"1185536833","6":"1185536833"}]},"1970":{"script_id":"1970","0":"1970","script_name":"deb.vim","1":"deb.vim","script_type":"utility","2":"utility","summary":"browse debian package","3":"browse debian package","description":"Allows you to browse debian package in the same way you can browse .tar and .zip files.\r\nWith this script, after opening a debian package with vim, you get a list of files included in the archive. You can then open those files.","4":"Allows you to browse debian package in the same way you can browse .tar and .zip files.\r\nWith this script, after opening a debian package with vim, you get a list of files included in the archive. You can then open those files.","install_details":"unzip deb.zip in ~\/.vim directorys.","5":"unzip deb.zip in ~\/.vim directorys.","first_name":"arno.","6":"arno.","last_name":" ","7":" ","releases":[{"0":"1970","vim_version":"7.0","1":"7.0","script_version":"v1.4","2":"v1.4","version_comment":"fixes: could not open files with # or % in file name\r\n\r\nadd support for data.tar.bz2, data.tar.lzma and data.tar","3":"fixes: could not open files with # or % in file name\r\n\r\nadd support for data.tar.bz2, data.tar.lzma and data.tar","package":"deb.zip","4":"deb.zip","src_id":"8517","5":"8517","creation_date":"1207098404","6":"1207098404"},{"0":"1970","vim_version":"7.0","1":"7.0","script_version":"1.3","2":"1.3","version_comment":"format man pages","3":"format man pages","package":"deb.zip","4":"deb.zip","src_id":"8078","5":"8078","creation_date":"1198228583","6":"1198228583"},{"0":"1970","vim_version":"7.0","1":"7.0","script_version":"1.2","2":"1.2","version_comment":"License clarification","3":"License clarification","package":"deb.zip","4":"deb.zip","src_id":"8032","5":"8032","creation_date":"1197023430","6":"1197023430"},{"0":"1970","vim_version":"7.0","1":"7.0","script_version":"1.1","2":"1.1","version_comment":"filetype for browsing debian changelog becomes debchangelog (instead of changelog). thanks to James Vega","3":"filetype for browsing debian changelog becomes debchangelog (instead of changelog). thanks to James Vega","package":"deb.zip","4":"deb.zip","src_id":"8031","5":"8031","creation_date":"1196951042","6":"1196951042"},{"0":"1970","vim_version":"7.0","1":"7.0","script_version":"v1","2":"v1","version_comment":"Initial upload","3":"Initial upload","package":"deb.zip","4":"deb.zip","src_id":"7420","5":"7420","creation_date":"1185503032","6":"1185503032"}]},"1969":{"script_id":"1969","0":"1969","script_name":"Highlight and Mark Lines","1":"Highlight and Mark Lines","script_type":"utility","2":"utility","summary":"Highlights and Marks lines (up to 3) and allows moving between them.","3":"Highlights and Marks lines (up to 3) and allows moving between them.","description":"Inspired from other scripters. Thanks.\r\n\r\nThis utility was created because of needs as others. My job requires log\r\nmining. Sometimes I need to highlight specific lines and moving between \r\nthem for comparison. Most of my colleagues use UltraEdit which has this\r\ncapability which made me to find a way to add this capability to Vim.\r\n\r\nWhat does this utility do?\r\nIt highlights and marks the line under cursor. Then you'll be able to move\r\nbetween these marks easily. Unfortunately it is just limited to 3 marks because of my lack of coding knowledge.\r\n\r\nStep 1 - Just highlight and mark the line with CTRL+F2, CTRL+F3 or CTRL+F4. \r\nStep 2 - Then use F2, F3 and F4 to move between these marks. \r\nStep 3 - Use SHIFT+CTRL+F2, SHIFT+CTRL+F3 and SHIFT+CTRL+F4 to reset the related mark and highlight.\r\nStep 4 - use cm in normal mode to reset all highlights and marks\r\n\r\nIt is that simple.","4":"Inspired from other scripters. Thanks.\r\n\r\nThis utility was created because of needs as others. My job requires log\r\nmining. Sometimes I need to highlight specific lines and moving between \r\nthem for comparison. Most of my colleagues use UltraEdit which has this\r\ncapability which made me to find a way to add this capability to Vim.\r\n\r\nWhat does this utility do?\r\nIt highlights and marks the line under cursor. Then you'll be able to move\r\nbetween these marks easily. Unfortunately it is just limited to 3 marks because of my lack of coding knowledge.\r\n\r\nStep 1 - Just highlight and mark the line with CTRL+F2, CTRL+F3 or CTRL+F4. \r\nStep 2 - Then use F2, F3 and F4 to move between these marks. \r\nStep 3 - Use SHIFT+CTRL+F2, SHIFT+CTRL+F3 and SHIFT+CTRL+F4 to reset the related mark and highlight.\r\nStep 4 - use cm in normal mode to reset all highlights and marks\r\n\r\nIt is that simple.","install_details":"Move the file to \"plugins\" directory of your Vim installation.","5":"Move the file to \"plugins\" directory of your Vim installation.","first_name":"Ahmet Gokalp","6":"Ahmet Gokalp","last_name":"ERGEC","7":"ERGEC","releases":[{"0":"1969","vim_version":"7.0","1":"7.0","script_version":"0.2","2":"0.2","version_comment":"Initial upload","3":"Initial upload","package":"hglt_mark.vim","4":"hglt_mark.vim","src_id":"7413","5":"7413","creation_date":"1185353439","6":"1185353439"}]},"1968":{"script_id":"1968","0":"1968","script_name":"indent\/haskell.vim","1":"indent\/haskell.vim","script_type":"indent","2":"indent","summary":"Haskell indent file","3":"Haskell indent file","description":"Indentation script for Haskell.\r\n\r\nModify g:haskell_indent_if and g:haskell_indent_case to\r\nchange indentation for `if'(default 3) and `case'(default 5).\r\nExample (in .vimrc):\r\n> let g:haskell_indent_if = 2\r\n","4":"Indentation script for Haskell.\r\n\r\nModify g:haskell_indent_if and g:haskell_indent_case to\r\nchange indentation for `if'(default 3) and `case'(default 5).\r\nExample (in .vimrc):\r\n> let g:haskell_indent_if = 2\r\n","install_details":"Put the script at ~\/.vim\/indent .","5":"Put the script at ~\/.vim\/indent .","first_name":"motemen","6":"motemen","last_name":".","7":".","releases":[{"0":"1968","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"haskell.vim","4":"haskell.vim","src_id":"7407","5":"7407","creation_date":"1185266472","6":"1185266472"}]},"1967":{"script_id":"1967","0":"1967","script_name":"gvim extensions for TAL\/pTAL","1":"gvim extensions for TAL\/pTAL","script_type":"utility","2":"utility","summary":"Support for TAL\/pTAL source files with syntax highlighting and tags","3":"Support for TAL\/pTAL source files with syntax highlighting and tags","description":"These tools provides support in gvim for TAL\/pTAL source files with syntax highlighting and tags. HP NonStop (NSK) users who need to edit TAL\/pTAL source files can use all features of gvim with the help of these tools. This is intended for use by developers when the source files have been copied to Windows. Reading and writing of files residing on NSK are not supported.\r\n\r\nSyntax highlighting is provided for TAL\/pTAL source files, which helps in simplifying complicated code. A tool is provided for building tags for TAL\/pTAL source files similar to the tags built by ctags for C code. This helps in easy navigation of multiple source files and jumping directly to procedure definitions.\r\n","4":"These tools provides support in gvim for TAL\/pTAL source files with syntax highlighting and tags. HP NonStop (NSK) users who need to edit TAL\/pTAL source files can use all features of gvim with the help of these tools. This is intended for use by developers when the source files have been copied to Windows. Reading and writing of files residing on NSK are not supported.\r\n\r\nSyntax highlighting is provided for TAL\/pTAL source files, which helps in simplifying complicated code. A tool is provided for building tags for TAL\/pTAL source files similar to the tags built by ctags for C code. This helps in easy navigation of multiple source files and jumping directly to procedure definitions.\r\n","install_details":"Install the GVim 7.1 version from ftp:\/\/ftp.vim.org\/pub\/vim\/pc\/gvim71.exe. Then use install.bat to install the extensions. See README.txt in the zip file for details.","5":"Install the GVim 7.1 version from ftp:\/\/ftp.vim.org\/pub\/vim\/pc\/gvim71.exe. Then use install.bat to install the extensions. See README.txt in the zip file for details.","first_name":"Ajay","6":"Ajay","last_name":"Kidave","7":"Kidave","releases":[{"0":"1967","vim_version":"7.0","1":"7.0","script_version":"1.3","2":"1.3","version_comment":"Minor documentation changes.","3":"Minor documentation changes.","package":"GVimTAL.zip","4":"GVimTAL.zip","src_id":"7405","5":"7405","creation_date":"1185256662","6":"1185256662"}]},"1966":{"script_id":"1966","0":"1966","script_name":"Ruby Snippets","1":"Ruby Snippets","script_type":"utility","2":"utility","summary":"Some abbreviations to use with Ruby","3":"Some abbreviations to use with Ruby","description":"This script have some abbreviations to use in insert mode while writing Ruby code. The goal is to speed up (more!) code writing.\r\nThere are \"triggers\" when typing def, for, begin, inject, class, module, collect, detect, each, find, find_all, map, reject, select, attr_reader, attr_writer, attr_accessor. For example, when typing \"class\" you get\r\n\r\nclass ClassName\r\nend\r\n\r\nand the cursor is positioned on \"ClassName\", where you can use cw to replace it to the name you want on the class.\r\n\r\nThere's a little video on http:\/\/eustaquiorangel.com\/blog\/show\/438 about the script. Non-portuguese readers, please just click on play.\r\n","4":"This script have some abbreviations to use in insert mode while writing Ruby code. The goal is to speed up (more!) code writing.\r\nThere are \"triggers\" when typing def, for, begin, inject, class, module, collect, detect, each, find, find_all, map, reject, select, attr_reader, attr_writer, attr_accessor. For example, when typing \"class\" you get\r\n\r\nclass ClassName\r\nend\r\n\r\nand the cursor is positioned on \"ClassName\", where you can use cw to replace it to the name you want on the class.\r\n\r\nThere's a little video on http:\/\/eustaquiorangel.com\/blog\/show\/438 about the script. Non-portuguese readers, please just click on play.\r\n","install_details":"Just unzip the package to your $HOME\/.vim directory and source it when editing Ruby files, like this:\r\n\r\nautocmd BufNewFile,BufRead *.rb source ~\/.vim\/scripts\/rubysnippets.vim\r\n\r\nIf you want to make it works on some Rails files also, just insert the file extensions with a comma after *.rb (ex: *.rhtml).\r\n","5":"Just unzip the package to your $HOME\/.vim directory and source it when editing Ruby files, like this:\r\n\r\nautocmd BufNewFile,BufRead *.rb source ~\/.vim\/scripts\/rubysnippets.vim\r\n\r\nIf you want to make it works on some Rails files also, just insert the file extensions with a comma after *.rb (ex: *.rhtml).\r\n","first_name":"Eustaquio","6":"Eustaquio","last_name":"Rangel de Oliveira Jr.","7":"Rangel de Oliveira Jr.","releases":[{"0":"1966","vim_version":"7.0","1":"7.0","script_version":"0.1.0","2":"0.1.0","version_comment":"Fixed the behaviour of keywords after an equal sign is typed. Added search on the online docs at Rollyo.com.","3":"Fixed the behaviour of keywords after an equal sign is typed. Added search on the online docs at Rollyo.com.","package":"rubysnippets.zip","4":"rubysnippets.zip","src_id":"7457","5":"7457","creation_date":"1186419966","6":"1186419966"},{"0":"1966","vim_version":"7.0","1":"7.0","script_version":"0.0.9","2":"0.0.9","version_comment":"A lot of refactoring to allow methods like like select, map, collect and keywords like class, module and def to create the blocks only when they are on the correct scope. So, if you have a comment like \r\n\/\/ def a module class for each object \r\nthey will not expand to the blocks.","3":"A lot of refactoring to allow methods like like select, map, collect and keywords like class, module and def to create the blocks only when they are on the correct scope. So, if you have a comment like \r\n\/\/ def a module class for each object \r\nthey will not expand to the blocks.","package":"rubysnippets.zip","4":"rubysnippets.zip","src_id":"7440","5":"7440","creation_date":"1186053935","6":"1186053935"},{"0":"1966","vim_version":"7.0","1":"7.0","script_version":"0.0.8","2":"0.0.8","version_comment":"Defined signs. They can be simple text strings (>>) or a little Ruby icon when using GUI, and can be inserted on Normal Mode with \"is\" (insert sign) and removed with \"rs\" (remove sign).\r\n","3":"Defined signs. They can be simple text strings (>>) or a little Ruby icon when using GUI, and can be inserted on Normal Mode with \"is\" (insert sign) and removed with \"rs\" (remove sign).\r\n","package":"rubysnippets.zip","4":"rubysnippets.zip","src_id":"7428","5":"7428","creation_date":"1185774799","6":"1185774799"},{"0":"1966","vim_version":"7.0","1":"7.0","script_version":"0.0.7","2":"0.0.7","version_comment":"Fixed some problems about indentation, spaces and tabs.","3":"Fixed some problems about indentation, spaces and tabs.","package":"rubysnippets.zip","4":"rubysnippets.zip","src_id":"7421","5":"7421","creation_date":"1185524111","6":"1185524111"},{"0":"1966","vim_version":"7.0","1":"7.0","script_version":"0.0.6","2":"0.0.6","version_comment":"Added a configuration variable to skip the insertion of some structures (def, class, module) default names (method_name,ClassName,ModuleName).","3":"Added a configuration variable to skip the insertion of some structures (def, class, module) default names (method_name,ClassName,ModuleName).","package":"rubysnippets.zip","4":"rubysnippets.zip","src_id":"7418","5":"7418","creation_date":"1185471513","6":"1185471513"},{"0":"1966","vim_version":"7.0","1":"7.0","script_version":"0.0.5","2":"0.0.5","version_comment":"Fixed some problems with indentation. Now if you don't use some keywords like class, module and for on the start of the line, they will not expand to its structures. Changed the way to make hashes, they are created checking the nearest cursor position { and } pair.","3":"Fixed some problems with indentation. Now if you don't use some keywords like class, module and for on the start of the line, they will not expand to its structures. Changed the way to make hashes, they are created checking the nearest cursor position { and } pair.","package":"rubysnippets.zip","4":"rubysnippets.zip","src_id":"7417","5":"7417","creation_date":"1185451755","6":"1185451755"},{"0":"1966","vim_version":"7.0","1":"7.0","script_version":"0.0.4","2":"0.0.4","version_comment":"Changed the way to create hashes. Now it works on Insert and Normal modes,  with <C-H> formatting the content of a string like { key value } to the Ruby hash format. Added some documentation.","3":"Changed the way to create hashes. Now it works on Insert and Normal modes,  with <C-H> formatting the content of a string like { key value } to the Ruby hash format. Added some documentation.","package":"rubysnippets.zip","4":"rubysnippets.zip","src_id":"7415","5":"7415","creation_date":"1185372648","6":"1185372648"},{"0":"1966","vim_version":"7.0","1":"7.0","script_version":"0.0.3","2":"0.0.3","version_comment":"Added some features to create for loops and hashes with parameters from the current line.","3":"Added some features to create for loops and hashes with parameters from the current line.","package":"rubysnippets.zip","4":"rubysnippets.zip","src_id":"7414","5":"7414","creation_date":"1185363619","6":"1185363619"},{"0":"1966","vim_version":"7.0","1":"7.0","script_version":"0.0.2","2":"0.0.2","version_comment":"Created some onliners and made some fixes regarding this tip, which I use a lot:\r\nhttp:\/\/www.vim.org\/tips\/tip.php?tip_id=153\r\nIs tested if some chars (like {) are mapped, if so the close pair is not inserted.","3":"Created some onliners and made some fixes regarding this tip, which I use a lot:\r\nhttp:\/\/www.vim.org\/tips\/tip.php?tip_id=153\r\nIs tested if some chars (like {) are mapped, if so the close pair is not inserted.","package":"rubysnippets.vim","4":"rubysnippets.vim","src_id":"7402","5":"7402","creation_date":"1185210189","6":"1185210189"},{"0":"1966","vim_version":"7.0","1":"7.0","script_version":"0.0.1","2":"0.0.1","version_comment":"Initial upload","3":"Initial upload","package":"rubysnippets.vim","4":"rubysnippets.vim","src_id":"7399","5":"7399","creation_date":"1185167394","6":"1185167394"}]},"1965":{"script_id":"1965","0":"1965","script_name":"lodgeit.vim","1":"lodgeit.vim","script_type":"utility","2":"utility","summary":"pastes code to paste.pocoo.org","3":"pastes code to paste.pocoo.org","description":"Just do :Lodgeit to paste the file or selection.","4":"Just do :Lodgeit to paste the file or selection.","install_details":"Copy the file to ~\/.vim\/plugin\r\n\r\nIf you want to paste on ctrl + p just add this to your vimrc:\r\n\tmap ^P :Lodgeit<CR>\r\n(where ^P is entered using ctrl + v, ctrl + p in vim)","5":"Copy the file to ~\/.vim\/plugin\r\n\r\nIf you want to paste on ctrl + p just add this to your vimrc:\r\n\tmap ^P :Lodgeit<CR>\r\n(where ^P is entered using ctrl + v, ctrl + p in vim)","first_name":"Armin","6":"Armin","last_name":"Ronacher","7":"Ronacher","releases":[{"0":"1965","vim_version":"7.0","1":"7.0","script_version":"0.3","2":"0.3","version_comment":"Switched to pound paste and added license.","3":"Switched to pound paste and added license.","package":"lodgeit.vim","4":"lodgeit.vim","src_id":"19925","5":"19925","creation_date":"1366815898","6":"1366815898"},{"0":"1965","vim_version":"7.0","1":"7.0","script_version":"0.2","2":"0.2","version_comment":"Added support for opening private pastes.","3":"Added support for opening private pastes.","package":"lodgeit.vim","4":"lodgeit.vim","src_id":"8848","5":"8848","creation_date":"1214325193","6":"1214325193"},{"0":"1965","vim_version":"7.0","1":"7.0","script_version":"0.1.5","2":"0.1.5","version_comment":"You can now download pastes via :Lodgeit URL or :Lodgeit #pasteid and push a change to the server via :Lodgeit.","3":"You can now download pastes via :Lodgeit URL or :Lodgeit #pasteid and push a change to the server via :Lodgeit.","package":"lodgeit.vim","4":"lodgeit.vim","src_id":"7400","5":"7400","creation_date":"1185171758","6":"1185171758"},{"0":"1965","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"lodgeit.vim","4":"lodgeit.vim","src_id":"7396","5":"7396","creation_date":"1185157929","6":"1185157929"}]},"1964":{"script_id":"1964","0":"1964","script_name":"tie.vim","1":"tie.vim","script_type":"syntax","2":"syntax","summary":"Vim syntax file for Tensilica Xtensa TIE extension language","3":"Vim syntax file for Tensilica Xtensa TIE extension language","description":"This is syntax highlighting file for TIE language that is used by Tensilica for xtensa processor tie extensions. For more information on xtensa and tensilica processors: see http:\/\/www.tensilica.com.\r\n","4":"This is syntax highlighting file for TIE language that is used by Tensilica for xtensa processor tie extensions. For more information on xtensa and tensilica processors: see http:\/\/www.tensilica.com.\r\n","install_details":"**All downloaders, please provide honest rating karmas to improve this script.**\r\n\r\nDo the following steps for installation:\r\n1. Copy the tie.vim file to the $VIMRUNTIME\/syntax folder (the folder where vim is installed in your system).\r\n2. Add the following lines in your ~\/.vimrc file (the vimrc script that will be located in your home folder).\r\n\r\nFile ~\/.vimrc\r\n------ snip ----\r\n\" include tie file syntax\r\nau BufNewFile,BufRead *.tie\t\t\tsetf tie\r\nsyn on\r\n------ snap ----\r\nNote: The \"syn on\" above can be omitted if already present in your vimrc file.\r\n\r\nThats it! You are ready to use your vim editor with the tie syntax enabled for editing.\r\nI am happy to receive any bug reports\/constructive comments\/critisism from the users of tie.vim.\r\nIf there are any requests that you would have - do let me know; I will try my best to see what I can do ;) Happy tie vimming !\r\n\r\n","5":"**All downloaders, please provide honest rating karmas to improve this script.**\r\n\r\nDo the following steps for installation:\r\n1. Copy the tie.vim file to the $VIMRUNTIME\/syntax folder (the folder where vim is installed in your system).\r\n2. Add the following lines in your ~\/.vimrc file (the vimrc script that will be located in your home folder).\r\n\r\nFile ~\/.vimrc\r\n------ snip ----\r\n\" include tie file syntax\r\nau BufNewFile,BufRead *.tie\t\t\tsetf tie\r\nsyn on\r\n------ snap ----\r\nNote: The \"syn on\" above can be omitted if already present in your vimrc file.\r\n\r\nThats it! You are ready to use your vim editor with the tie syntax enabled for editing.\r\nI am happy to receive any bug reports\/constructive comments\/critisism from the users of tie.vim.\r\nIf there are any requests that you would have - do let me know; I will try my best to see what I can do ;) Happy tie vimming !\r\n\r\n","first_name":"Saravanan","6":"Saravanan","last_name":"T S","7":"T S","releases":[{"0":"1964","vim_version":"6.0","1":"6.0","script_version":"0.7","2":"0.7","version_comment":"Initial upload","3":"Initial upload","package":"tie.vim","4":"tie.vim","src_id":"7390","5":"7390","creation_date":"1185060186","6":"1185060186"}]},"1963":{"script_id":"1963","0":"1963","script_name":"vimscript coding aids","1":"vimscript coding aids","script_type":"utility","2":"utility","summary":"some coding aids for writing vim scripts","3":"some coding aids for writing vim scripts","description":"See http:\/\/github.com\/MarcWeber\/theonevimlib.\r\nStart by reading core\/docs\/tovl.vim\r\n\r\nThere is a plugin called\r\nplugins#filetype#vim#vl_repo#PluginVL_RepoStuff\r\n\r\nEnjoy, join and contribute!","4":"See http:\/\/github.com\/MarcWeber\/theonevimlib.\r\nStart by reading core\/docs\/tovl.vim\r\n\r\nThere is a plugin called\r\nplugins#filetype#vim#vl_repo#PluginVL_RepoStuff\r\n\r\nEnjoy, join and contribute!","install_details":"I merged the completion stuff with vim-dev-plugin http:\/\/github.com\/c9s\/vim-dev-plugin\r\nI may merge the fix prefix functions somewhen in the future","5":"I merged the completion stuff with vim-dev-plugin http:\/\/github.com\/c9s\/vim-dev-plugin\r\nI may merge the fix prefix functions somewhen in the future","first_name":"Marc","6":"Marc","last_name":"Weber","7":"Weber","releases":[{"0":"1963","vim_version":"7.0","1":"7.0","script_version":"0.5","2":"0.5","version_comment":"Initial upload","3":"Initial upload","package":"vimlib_vimscript_coding_aids_installer_sourceme.zip","4":"vimlib_vimscript_coding_aids_installer_sourceme.zip","src_id":"7378","5":"7378","creation_date":"1184753107","6":"1184753107"}]},"1962":{"script_id":"1962","0":"1962","script_name":"Simple256","1":"Simple256","script_type":"color scheme","2":"color scheme","summary":"Simple color scheme for using with light background","3":"Simple color scheme for using with light background","description":"This is a simple color scheme for using with light background and 256\/88 colors terminal.\r\nScreenshot: http:\/\/i.imgur.com\/cf7YXFY.png .","4":"This is a simple color scheme for using with light background and 256\/88 colors terminal.\r\nScreenshot: http:\/\/i.imgur.com\/cf7YXFY.png .","install_details":"Copy script to ~\/.vim\/colors and add to your .vimrc following lines:\r\nif $TERM == \"xterm\"\r\n    set t_Co = 256\r\n    colors simple256\r\nendif\r\n","5":"Copy script to ~\/.vim\/colors and add to your .vimrc following lines:\r\nif $TERM == \"xterm\"\r\n    set t_Co = 256\r\n    colors simple256\r\nendif\r\n","first_name":"Alexander","6":"Alexander","last_name":"Rodin","7":"Rodin","releases":[{"0":"1962","vim_version":"6.0","1":"6.0","script_version":"0.01","2":"0.01","version_comment":"Initial upload","3":"Initial upload","package":"simple256.vim","4":"simple256.vim","src_id":"7374","5":"7374","creation_date":"1184737544","6":"1184737544"}]},"1961":{"script_id":"1961","0":"1961","script_name":"Tabmerge","1":"Tabmerge","script_type":"utility","2":"utility","summary":"Merge a tab's windows with the current tab","3":"Merge a tab's windows with the current tab","description":"Usage:\r\n :Tabmerge [tab number] [top|bottom|left|right]\r\n\r\nThe tab number can be \"$\" for the last tab.  If the tab number isn't specified the tab to the right of the current tab is merged.  If there is no right tab, the left tab is merged.\r\n\r\nThe location specifies where in the current tab to merge the windows. Defaults to \"top\".\r\n","4":"Usage:\r\n :Tabmerge [tab number] [top|bottom|left|right]\r\n\r\nThe tab number can be \"$\" for the last tab.  If the tab number isn't specified the tab to the right of the current tab is merged.  If there is no right tab, the left tab is merged.\r\n\r\nThe location specifies where in the current tab to merge the windows. Defaults to \"top\".\r\n","install_details":"Put the script in your plugin directory or source it directly.","5":"Put the script in your plugin directory or source it directly.","first_name":"Christian J.","6":"Christian J.","last_name":"Robinson","7":"Robinson","releases":[{"0":"1961","vim_version":"9.0","1":"9.0","script_version":"0.4","2":"0.4","version_comment":"- Updated for Vim 9 (no functionality changes)","3":"- Updated for Vim 9 (no functionality changes)","package":"Tabmerge.vim","4":"Tabmerge.vim","src_id":"28138","5":"28138","creation_date":"1661149278","6":"1661149278"},{"0":"1961","vim_version":"7.0","1":"7.0","script_version":"0.3","2":"0.3","version_comment":"- Can now merge to the left\/right as well","3":"- Can now merge to the left\/right as well","package":"Tabmerge.vim","4":"Tabmerge.vim","src_id":"8828","5":"8828","creation_date":"1213922939","6":"1213922939"},{"0":"1961","vim_version":"7.0","1":"7.0","script_version":"0.2","2":"0.2","version_comment":"- Made the tab number optional\r\n- Wasn't properly restoring 'switchbuf' when there was an error","3":"- Made the tab number optional\r\n- Wasn't properly restoring 'switchbuf' when there was an error","package":"Tabmerge.vim","4":"Tabmerge.vim","src_id":"7372","5":"7372","creation_date":"1184721824","6":"1184721824"},{"0":"1961","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"Tabmerge.vim","4":"Tabmerge.vim","src_id":"7369","5":"7369","creation_date":"1184719191","6":"1184719191"}]},"1960":{"script_id":"1960","0":"1960","script_name":"cimpl","1":"cimpl","script_type":"utility","2":"utility","summary":"Generates implimentations for C\/C++ function prototypes","3":"Generates implimentations for C\/C++ function prototypes","description":"This script generates empty implementations for C\/C++ functions from specified header file. For following header file\r\n\r\n#ifndef TEST_H\r\n#define TEST_H\r\nclass Test\r\n{\r\n    public:\r\n        explicit Test(int val = 0);\r\n        int getVal() const\r\n        {\r\n            return m_val;\r\n        }\r\n        void setVal(int val);\r\n\r\n        friend const Test operator +(const Test& a, const Test& b);\r\n\r\n    private:\r\n         int m_val;\r\n};\r\n\r\nconst Test operator + ( const Test &a, const Test & b );\r\n#endif\r\n\r\noutput will be\r\n\r\nTest::Test(int val)\r\n{\r\n    \r\n}\r\n\r\nvoid Test::setVal(int val)\r\n{\r\n    \r\n}\r\n\r\nconst Test operator +(const Test& a, const Test& b)\r\n{\r\n    \r\n}\r\n","4":"This script generates empty implementations for C\/C++ functions from specified header file. For following header file\r\n\r\n#ifndef TEST_H\r\n#define TEST_H\r\nclass Test\r\n{\r\n    public:\r\n        explicit Test(int val = 0);\r\n        int getVal() const\r\n        {\r\n            return m_val;\r\n        }\r\n        void setVal(int val);\r\n\r\n        friend const Test operator +(const Test& a, const Test& b);\r\n\r\n    private:\r\n         int m_val;\r\n};\r\n\r\nconst Test operator + ( const Test &a, const Test & b );\r\n#endif\r\n\r\noutput will be\r\n\r\nTest::Test(int val)\r\n{\r\n    \r\n}\r\n\r\nvoid Test::setVal(int val)\r\n{\r\n    \r\n}\r\n\r\nconst Test operator +(const Test& a, const Test& b)\r\n{\r\n    \r\n}\r\n","install_details":"You must have installed exuberant-ctags. Copy this script to ~\/.vim\/plugins. Also you can install tSkeleton (vimscript#1160) to add functions implementations in new source files. \r\nThis skeleton for .cpp files:\r\n\r\n<+call:eval('findfile(expand(\"%:t:r\").\".h\", \".;\") != \"\" ? \"\\n#include \\\"\".findfile(expand(\"%:r:t\").\".h\", \".;\").\"\\\"\\n\" : \"\"')+><+call:eval('findfile(expand(\"%:t:r\").\".h\", \".;\") != \"\" ? \"<+CURSOR+>\".GenImpl(findfile(expand(\"%:r:t\").\".h\", \".;\")) : \"\\n<+CURSOR+>\\n\"')+>\r\n\r\nwill find .h files with same name in current directory and if it exists add implementations for definitions from header.\r\n","5":"You must have installed exuberant-ctags. Copy this script to ~\/.vim\/plugins. Also you can install tSkeleton (vimscript#1160) to add functions implementations in new source files. \r\nThis skeleton for .cpp files:\r\n\r\n<+call:eval('findfile(expand(\"%:t:r\").\".h\", \".;\") != \"\" ? \"\\n#include \\\"\".findfile(expand(\"%:r:t\").\".h\", \".;\").\"\\\"\\n\" : \"\"')+><+call:eval('findfile(expand(\"%:t:r\").\".h\", \".;\") != \"\" ? \"<+CURSOR+>\".GenImpl(findfile(expand(\"%:r:t\").\".h\", \".;\")) : \"\\n<+CURSOR+>\\n\"')+>\r\n\r\nwill find .h files with same name in current directory and if it exists add implementations for definitions from header.\r\n","first_name":"Alexander","6":"Alexander","last_name":"Rodin","7":"Rodin","releases":[{"0":"1960","vim_version":"6.0","1":"6.0","script_version":"0.03","2":"0.03","version_comment":"Add support for pure virtual functions (thanks to Anton)","3":"Add support for pure virtual functions (thanks to Anton)","package":"cimpl.vim","4":"cimpl.vim","src_id":"7916","5":"7916","creation_date":"1194650818","6":"1194650818"},{"0":"1960","vim_version":"6.0","1":"6.0","script_version":"0.02","2":"0.02","version_comment":"Add support for operators and friend functions","3":"Add support for operators and friend functions","package":"cimpl.vim","4":"cimpl.vim","src_id":"7375","5":"7375","creation_date":"1184739960","6":"1184739960"},{"0":"1960","vim_version":"6.0","1":"6.0","script_version":"0.01","2":"0.01","version_comment":"Initial upload","3":"Initial upload","package":"cimpl.vim","4":"cimpl.vim","src_id":"7367","5":"7367","creation_date":"1184666400","6":"1184666400"}]},"1959":{"script_id":"1959","0":"1959","script_name":"CharSort","1":"CharSort","script_type":"utility","2":"utility","summary":"Functions and mappings to sort the characters in a string","3":"Functions and mappings to sort the characters in a string","description":"Mappings:\r\n <lead>so  --  sort, case sensitive\r\n <lead>si  --  sort, case insensitive\r\n\r\nThese mappings work in visual and normal mode--in normal mode they take a motion operator.  See \":help mapleader\"\r\n\r\nFunction:\r\n CharSort#Sort({string} [, {i\/c}]) -- Sort {string}\r\n    {i\/c} == c  -- match case (default)\r\n    {i\/c} == i  -- ignore case","4":"Mappings:\r\n <lead>so  --  sort, case sensitive\r\n <lead>si  --  sort, case insensitive\r\n\r\nThese mappings work in visual and normal mode--in normal mode they take a motion operator.  See \":help mapleader\"\r\n\r\nFunction:\r\n CharSort#Sort({string} [, {i\/c}]) -- Sort {string}\r\n    {i\/c} == c  -- match case (default)\r\n    {i\/c} == i  -- ignore case","install_details":"Either source this file directly or put it in <runtimepath>\/autoload and copy the following maps in the file to your vimrc.\r\n","5":"Either source this file directly or put it in <runtimepath>\/autoload and copy the following maps in the file to your vimrc.\r\n","first_name":"Christian J.","6":"Christian J.","last_name":"Robinson","7":"Robinson","releases":[{"0":"1959","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"CharSort.vim","4":"CharSort.vim","src_id":"7358","5":"7358","creation_date":"1184621819","6":"1184621819"}]},"1958":{"script_id":"1958","0":"1958","script_name":"SmartX","1":"SmartX","script_type":"utility","2":"utility","summary":"Smart deletion of \\X escapes with the x\/X\/Backspace\/Delete keys","3":"Smart deletion of \\X escapes with the x\/X\/Backspace\/Delete keys","description":"This script will autmatically delete \\X escapes when the cursor is on the \\ and you press X in normal mode or after the X and you press backspace in insert mode.  X and the delete key in normal mode and the delete key in insert mode also work.\r\n","4":"This script will autmatically delete \\X escapes when the cursor is on the \\ and you press X in normal mode or after the X and you press backspace in insert mode.  X and the delete key in normal mode and the delete key in insert mode also work.\r\n","install_details":"The mappings are buffer-local so you need to source it from a filetype plugin, for example, put it in ~\/.vim and put \"runtime SmartX.vim\" in ~\/.vim\/ftplugin\/perl.vim.","5":"The mappings are buffer-local so you need to source it from a filetype plugin, for example, put it in ~\/.vim and put \"runtime SmartX.vim\" in ~\/.vim\/ftplugin\/perl.vim.","first_name":"Christian J.","6":"Christian J.","last_name":"Robinson","7":"Robinson","releases":[{"0":"1958","vim_version":"9.0","1":"9.0","script_version":"0.2","2":"0.2","version_comment":"- Update for Vim 9 (no functionality added)","3":"- Update for Vim 9 (no functionality added)","package":"SmartX.vim","4":"SmartX.vim","src_id":"28139","5":"28139","creation_date":"1661150717","6":"1661150717"},{"0":"1958","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"SmartX.vim","4":"SmartX.vim","src_id":"7357","5":"7357","creation_date":"1184621517","6":"1184621517"}]},"1957":{"script_id":"1957","0":"1957","script_name":"yasnippets","1":"yasnippets","script_type":"utility","2":"utility","summary":"Yet another plugin for snippets and file skeletons","3":"Yet another plugin for snippets and file skeletons","description":"With this plugin you may insert text snippets.  These is used for frequently\r\ntyped text, such as statements in programs, copyrights, timestamps and other.\r\nThis plugin supports several types of snippets: keyword snippets,\r\nnewline snippets, file skeletons, To work with this plugin you need support\r\nfor ruby ('+ruby' compile option and ruby language itself), ERb (embedded ruby\r\nlibrary for ruby), and imaps.vim plugin (vimscript#244).\r\n\r\nMain advantages of this plugin are convenience and flexible way to define\r\nsnippets, \"newline\" snippets, and file skeletons with embedded ruby.\r\n","4":"With this plugin you may insert text snippets.  These is used for frequently\r\ntyped text, such as statements in programs, copyrights, timestamps and other.\r\nThis plugin supports several types of snippets: keyword snippets,\r\nnewline snippets, file skeletons, To work with this plugin you need support\r\nfor ruby ('+ruby' compile option and ruby language itself), ERb (embedded ruby\r\nlibrary for ruby), and imaps.vim plugin (vimscript#244).\r\n\r\nMain advantages of this plugin are convenience and flexible way to define\r\nsnippets, \"newline\" snippets, and file skeletons with embedded ruby.\r\n","install_details":"Decompress and untar in your ~\/.vim directory (or \r\nequivalent).  Inside Vim, enter this: \r\n   :helptags ~\/.vim\/doc \r\n(or equivalent directory) \r\n\r\nThen enter \r\n  :help yasnippets\r\nfor information","5":"Decompress and untar in your ~\/.vim directory (or \r\nequivalent).  Inside Vim, enter this: \r\n   :helptags ~\/.vim\/doc \r\n(or equivalent directory) \r\n\r\nThen enter \r\n  :help yasnippets\r\nfor information","first_name":"Valentin","6":"Valentin","last_name":"Valyaeff","7":"Valyaeff","releases":[{"0":"1957","vim_version":"7.0","1":"7.0","script_version":"3.0","2":"3.0","version_comment":"File skeletons \r\nUsing imaps.vim \r\nDocumentation\r\nOther bugfixes and improvements","3":"File skeletons \r\nUsing imaps.vim \r\nDocumentation\r\nOther bugfixes and improvements","package":"yasnippets.tar.gz","4":"yasnippets.tar.gz","src_id":"7444","5":"7444","creation_date":"1186159944","6":"1186159944"},{"0":"1957","vim_version":"7.0","1":"7.0","script_version":"2.1","2":"2.1","version_comment":"Highlighting for marker","3":"Highlighting for marker","package":"yasnippets.vim","4":"yasnippets.vim","src_id":"7383","5":"7383","creation_date":"1184854550","6":"1184854550"},{"0":"1957","vim_version":"7.0","1":"7.0","script_version":"2.0","2":"2.0","version_comment":"Merged with vimscript#1956","3":"Merged with vimscript#1956","package":"yasnippets.vim","4":"yasnippets.vim","src_id":"7377","5":"7377","creation_date":"1184751742","6":"1184751742"},{"0":"1957","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"yasnippets.vim","4":"yasnippets.vim","src_id":"7355","5":"7355","creation_date":"1184501652","6":"1184501652"}]},"1956":{"script_id":"1956","0":"1956","script_name":"smart_cr","1":"smart_cr","script_type":"utility","2":"utility","summary":"Inserting snippets in new line","3":"Inserting snippets in new line","description":"Deprecated, use vimscript#1957\r\n\r\nExample\r\n-------\r\nPerhaps you editing C file:\r\n  #include <stdlib.h*>\r\n(* - cursor position)\r\nIf you hit Enter, new include directive will be inserted:\r\n  #include <stdlib.h>\r\n  #include <*>\r\n\r\nConfiguration\r\n-------------\r\nYou must create new hash g:smart_cr\r\n  let g:smart_cr = {}\r\nHash must contain arrays for different filetypes:\r\n  let g:smart_cr.c = [['^#include <', '^>$', \"#include \\<@@@>\"],\r\n                     \\['^#include \"', '^\"$', \"#include \\\"@@@\\\"\"]]\r\nWhen you hit Enter, line is divided on two parts - before and above\r\nthe cursor. First two strings are regular expressions for left and\r\nright parts of line. If they matched, third string will be inserted in\r\nnew line.\r\n\"@@@\" is marker where to place cursor. You may redefine it by setting\r\nglobal variable:\r\n  let g:smart_cr_marker = '<here>'\r\n\r\nAnother example\r\n---------------\r\nThis for Embedded ruby:\r\n  let g:smart_cr.eruby = [['<%[^=]', '^\\s*%>',  \"<% @@@ %>\"],\r\n                         \\['<%[^=]', '^\\s*-%>', \"<% @@@ -%>\"],\r\n                         \\['<%=',    '^\\s*%>',  \"<%= @@@ %>\"],\r\n                         \\['<%=',    '^\\s*-%>', \"<%= @@@ -%>\"]]","4":"Deprecated, use vimscript#1957\r\n\r\nExample\r\n-------\r\nPerhaps you editing C file:\r\n  #include <stdlib.h*>\r\n(* - cursor position)\r\nIf you hit Enter, new include directive will be inserted:\r\n  #include <stdlib.h>\r\n  #include <*>\r\n\r\nConfiguration\r\n-------------\r\nYou must create new hash g:smart_cr\r\n  let g:smart_cr = {}\r\nHash must contain arrays for different filetypes:\r\n  let g:smart_cr.c = [['^#include <', '^>$', \"#include \\<@@@>\"],\r\n                     \\['^#include \"', '^\"$', \"#include \\\"@@@\\\"\"]]\r\nWhen you hit Enter, line is divided on two parts - before and above\r\nthe cursor. First two strings are regular expressions for left and\r\nright parts of line. If they matched, third string will be inserted in\r\nnew line.\r\n\"@@@\" is marker where to place cursor. You may redefine it by setting\r\nglobal variable:\r\n  let g:smart_cr_marker = '<here>'\r\n\r\nAnother example\r\n---------------\r\nThis for Embedded ruby:\r\n  let g:smart_cr.eruby = [['<%[^=]', '^\\s*%>',  \"<% @@@ %>\"],\r\n                         \\['<%[^=]', '^\\s*-%>', \"<% @@@ -%>\"],\r\n                         \\['<%=',    '^\\s*%>',  \"<%= @@@ %>\"],\r\n                         \\['<%=',    '^\\s*-%>', \"<%= @@@ -%>\"]]","install_details":"Place file into plugin folder","5":"Place file into plugin folder","first_name":"Valentin","6":"Valentin","last_name":"Valyaeff","7":"Valyaeff","releases":[{"0":"1956","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"smart_cr.vim","4":"smart_cr.vim","src_id":"7351","5":"7351","creation_date":"1184402109","6":"1184402109"}]},"1955":{"script_id":"1955","0":"1955","script_name":"doxygen-support","1":"doxygen-support","script_type":"utility","2":"utility","summary":"Generate Doxygen comments from user defined templates","3":"Generate Doxygen comments from user defined templates","description":"***** This plug-in is no longer supported *****\r\n\r\nSupport for Doxygen is integrated in the C-Support plug-in :\r\nhttp:\/\/vim.sourceforge.net\/scripts\/script.php?script_id=213\r\n\r\n\r\n***************\r\n\r\n\r\n\r\nThis plug-in generates Ex commands and a menu (or a menu tree) from a template\r\nfile containing user defined comment templates to be used for source code\r\ndocumentation with Doxygen. The template file can have user defined macros.\r\n\r\n\r\nDOCUMENTATION\r\n--------------------------------------------------------\r\nThis plug-in comes with a help file (doxygensupport.txt). Read it with\r\n\r\n   :help doxygensupport","4":"***** This plug-in is no longer supported *****\r\n\r\nSupport for Doxygen is integrated in the C-Support plug-in :\r\nhttp:\/\/vim.sourceforge.net\/scripts\/script.php?script_id=213\r\n\r\n\r\n***************\r\n\r\n\r\n\r\nThis plug-in generates Ex commands and a menu (or a menu tree) from a template\r\nfile containing user defined comment templates to be used for source code\r\ndocumentation with Doxygen. The template file can have user defined macros.\r\n\r\n\r\nDOCUMENTATION\r\n--------------------------------------------------------\r\nThis plug-in comes with a help file (doxygensupport.txt). Read it with\r\n\r\n   :help doxygensupport","install_details":"(1) Copy the zip archive  doxygen-support.zip to $HOME\/.vim\/ or $VIM\/vimfiles\r\n    (on the Windows platforms) and run\r\n\r\n      unzip doxygen-support.zip\r\n\r\n    If you have already an older version of doxygen-support and you have modified\r\n    the template files you may want to save your templates first or copy the \r\n    files from the archive by hand.\r\n\r\n(2) Loading of plugin files must be enabled. If not use\r\n      :filetype plugin on\r\n    This is the minimal content of the file '$HOME\/.vimrc'. Create one if there\r\n    is none. \r\n\r\n(3) Set at least some personal details in the main file \r\n    'doxygen-support\/templates\/doxygen.templates'. \r\n\r\n(4) Restart gVim\/Vim generate the help tags \r\n\r\n      :helptags ~\/.vim\/doc\r\n\r\n    and look at the doxygensupport help with\r\n\r\n      :h doxygensupport\r\n\r\n  For a system-wide installation please see the help file 'doc\/doxygensupport.txt'.","5":"(1) Copy the zip archive  doxygen-support.zip to $HOME\/.vim\/ or $VIM\/vimfiles\r\n    (on the Windows platforms) and run\r\n\r\n      unzip doxygen-support.zip\r\n\r\n    If you have already an older version of doxygen-support and you have modified\r\n    the template files you may want to save your templates first or copy the \r\n    files from the archive by hand.\r\n\r\n(2) Loading of plugin files must be enabled. If not use\r\n      :filetype plugin on\r\n    This is the minimal content of the file '$HOME\/.vimrc'. Create one if there\r\n    is none. \r\n\r\n(3) Set at least some personal details in the main file \r\n    'doxygen-support\/templates\/doxygen.templates'. \r\n\r\n(4) Restart gVim\/Vim generate the help tags \r\n\r\n      :helptags ~\/.vim\/doc\r\n\r\n    and look at the doxygensupport help with\r\n\r\n      :h doxygensupport\r\n\r\n  For a system-wide installation please see the help file 'doc\/doxygensupport.txt'.","first_name":"Fritz","6":"Fritz","last_name":"Mehner","7":"Mehner","releases":[{"0":"1955","vim_version":"7.0","1":"7.0","script_version":"2.2","2":"2.2","version_comment":"- New main menu iten: \"help (Doxygen-Support)\"\r\n- Bugfix: detection of a systemwide installation can fail.","3":"- New main menu iten: \"help (Doxygen-Support)\"\r\n- Bugfix: detection of a systemwide installation can fail.","package":"doxygen-support.zip","4":"doxygen-support.zip","src_id":"15161","5":"15161","creation_date":"1299321432","6":"1299321432"},{"0":"1955","vim_version":"7.0","1":"7.0","script_version":"2.1","2":"2.1","version_comment":"- Completely new doxygen integration.\r\n- New ex-commands.","3":"- Completely new doxygen integration.\r\n- New ex-commands.","package":"doxygen-support.zip","4":"doxygen-support.zip","src_id":"13297","5":"13297","creation_date":"1278408686","6":"1278408686"},{"0":"1955","vim_version":"7.0","1":"7.0","script_version":"2.0.2","2":"2.0.2","version_comment":"- Windows: Missing variable from 2.0.1 was still wrong.\r\n- Bugfix: variable g:Doxy_LoadMenus had no effect.\r\n- Documentation corrected.","3":"- Windows: Missing variable from 2.0.1 was still wrong.\r\n- Bugfix: variable g:Doxy_LoadMenus had no effect.\r\n- Documentation corrected.","package":"doxygen-support.zip","4":"doxygen-support.zip","src_id":"8483","5":"8483","creation_date":"1206165317","6":"1206165317"},{"0":"1955","vim_version":"7.0","1":"7.0","script_version":"2.0.1","2":"2.0.1","version_comment":"- Windows: Missing variable prevents correct plugin loading (thanks to Martin Banszel)\r\n- Documentation corrected.","3":"- Windows: Missing variable prevents correct plugin loading (thanks to Martin Banszel)\r\n- Documentation corrected.","package":"doxygen-support.zip","4":"doxygen-support.zip","src_id":"8423","5":"8423","creation_date":"1204946286","6":"1204946286"},{"0":"1955","vim_version":"7.0","1":"7.0","script_version":"2.0","2":"2.0","version_comment":"- Systemwide installation now possible.\r\n- Visual mode insert (surround a marked region).\r\n- Dialog to ask for parameters possible.\r\n- Automatic generation of submenu titles.","3":"- Systemwide installation now possible.\r\n- Visual mode insert (surround a marked region).\r\n- Dialog to ask for parameters possible.\r\n- Automatic generation of submenu titles.","package":"doxygen-support.zip","4":"doxygen-support.zip","src_id":"8394","5":"8394","creation_date":"1204704168","6":"1204704168"},{"0":"1955","vim_version":"7.0","1":"7.0","script_version":"1.4","2":"1.4","version_comment":"- Templates now can contain preprocessor statements.","3":"- Templates now can contain preprocessor statements.","package":"doxygen-support.zip","4":"doxygen-support.zip","src_id":"7996","5":"7996","creation_date":"1196163555","6":"1196163555"},{"0":"1955","vim_version":"7.0","1":"7.0","script_version":"1.3","2":"1.3","version_comment":"- Include mechanism for template files.\r\n- Menu items can be sorted\/unsorted.","3":"- Include mechanism for template files.\r\n- Menu items can be sorted\/unsorted.","package":"doxygen-support.zip","4":"doxygen-support.zip","src_id":"7453","5":"7453","creation_date":"1186286918","6":"1186286918"},{"0":"1955","vim_version":"7.0","1":"7.0","script_version":"1.2","2":"1.2","version_comment":"+ New 'insert' attribute for templates.","3":"+ New 'insert' attribute for templates.","package":"doxygen-support.zip","4":"doxygen-support.zip","src_id":"7438","5":"7438","creation_date":"1185968589","6":"1185968589"},{"0":"1955","vim_version":"7.0","1":"7.0","script_version":"1.1","2":"1.1","version_comment":"- New template attributes allow insertion above and below the current line and appending to the current line.","3":"- New template attributes allow insertion above and below the current line and appending to the current line.","package":"doxygen-support.zip","4":"doxygen-support.zip","src_id":"7426","5":"7426","creation_date":"1185754810","6":"1185754810"},{"0":"1955","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"doxygen-support.zip","4":"doxygen-support.zip","src_id":"7350","5":"7350","creation_date":"1184389587","6":"1184389587"}]},"1954":{"script_id":"1954","0":"1954","script_name":"yavdb","1":"yavdb","script_type":"utility","2":"utility","summary":"Yet Another (Generic) Vim Debugger Integration","3":"Yet Another (Generic) Vim Debugger Integration","description":"This is a generic Vim <->Debugger Interface Tool designed to be adaptable to any debugger application.  Currently supported debuggers include jdb and gdb.\r\n\r\nScript Requirements:\r\n-VIM compiled with Signs, Client-Server, and Python support.\r\n-Python 2.5\r\n-An operating system with support for named pipes\r\n\r\nUsing YAVDB:\r\n\r\n  yavdb [-s servername] [-t type] <debugger command line>\r\n\r\n-s specifies the Vim servername.  If no VIM (or GVIM) window exists with this servername, a new GVIM window will be opened.  If not specified, the servername 'VimDebugger' will be used.  If multiple applications are being debugged simultaneously unique servernames must be used.\r\n\r\n-t can be used to override the debugger type.  If this option is omitted the debugger name will be used as the type.  Currently supported debugger types include 'gdb' and 'jdb'.  Note that jdb will only correctly notify VIM of events when classnames are identical to filenames (other than the .java extension).\r\n\r\nVIM will have the following key mappings set:\r\n\r\n<C-F5> Run Application\r\n<F5> Continue Execution\r\n<F7> Step Into a Function\r\n<F8> Next Instruction\r\n<F9> Set Breakpoint\r\n<F10> Print variable value under cursor\r\n","4":"This is a generic Vim <->Debugger Interface Tool designed to be adaptable to any debugger application.  Currently supported debuggers include jdb and gdb.\r\n\r\nScript Requirements:\r\n-VIM compiled with Signs, Client-Server, and Python support.\r\n-Python 2.5\r\n-An operating system with support for named pipes\r\n\r\nUsing YAVDB:\r\n\r\n  yavdb [-s servername] [-t type] <debugger command line>\r\n\r\n-s specifies the Vim servername.  If no VIM (or GVIM) window exists with this servername, a new GVIM window will be opened.  If not specified, the servername 'VimDebugger' will be used.  If multiple applications are being debugged simultaneously unique servernames must be used.\r\n\r\n-t can be used to override the debugger type.  If this option is omitted the debugger name will be used as the type.  Currently supported debugger types include 'gdb' and 'jdb'.  Note that jdb will only correctly notify VIM of events when classnames are identical to filenames (other than the .java extension).\r\n\r\nVIM will have the following key mappings set:\r\n\r\n<C-F5> Run Application\r\n<F5> Continue Execution\r\n<F7> Step Into a Function\r\n<F8> Next Instruction\r\n<F9> Set Breakpoint\r\n<F10> Print variable value under cursor\r\n","install_details":"Place the file yavdb.vim in your plugins directory.\r\nPlace the file yavdb on in a directory on your path.","5":"Place the file yavdb.vim in your plugins directory.\r\nPlace the file yavdb on in a directory on your path.","first_name":"David","6":"David","last_name":"Morris","7":"Morris","releases":[{"0":"1954","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"yavdb.tgz","4":"yavdb.tgz","src_id":"7349","5":"7349","creation_date":"1184346238","6":"1184346238"}]},"1953":{"script_id":"1953","0":"1953","script_name":"Vimpress","1":"Vimpress","script_type":"utility","2":"utility","summary":"Manage wordpress blog posts from Vim","3":"Manage wordpress blog posts from Vim","description":"Vimpress is a nifty plugin for Vim which allows you to publish and edit posts on your wordpress blog.\r\n\r\nFeatures\r\n    * Get a list of all articles\r\n    * Write a new article\r\n    * Edit a current article\r\n    * Save (yeah, no kidding)\r\n    * Supports categories\r\n    * Supports tags1\r\n\r\nCommands\r\n    * \u00e2\u0080\u009c:BlogList\u00e2\u0080\u009d\r\n      Lists all articles in the blog\r\n    * \u00e2\u0080\u009c:BlogNew\u00e2\u0080\u009d\r\n      Opens page to write new article\r\n    * \u00e2\u0080\u009c:BlogOpen id\u00e2\u0080\u009d\r\n      Opens the article for edition\r\n    * \u00e2\u0080\u009c:BlogSend\u00e2\u0080\u009d\r\n      Saves the article to the blog\r\n\r\nProjects page : http:\/\/www.friggeri.net\/projets\/vimpress\/","4":"Vimpress is a nifty plugin for Vim which allows you to publish and edit posts on your wordpress blog.\r\n\r\nFeatures\r\n    * Get a list of all articles\r\n    * Write a new article\r\n    * Edit a current article\r\n    * Save (yeah, no kidding)\r\n    * Supports categories\r\n    * Supports tags1\r\n\r\nCommands\r\n    * \u00e2\u0080\u009c:BlogList\u00e2\u0080\u009d\r\n      Lists all articles in the blog\r\n    * \u00e2\u0080\u009c:BlogNew\u00e2\u0080\u009d\r\n      Opens page to write new article\r\n    * \u00e2\u0080\u009c:BlogOpen id\u00e2\u0080\u009d\r\n      Opens the article for edition\r\n    * \u00e2\u0080\u009c:BlogSend\u00e2\u0080\u009d\r\n      Saves the article to the blog\r\n\r\nProjects page : http:\/\/www.friggeri.net\/projets\/vimpress\/","install_details":"Edit the \u00e2\u0080\u009cSettings\u00e2\u0080\u009d section in blog.vim (starts at line 51). If you wish to use UTW tags, you should install the following plugin http:\/\/blog.circlesixdesign.com\/download\/utw-rpc-autotag\/ : and set \u00e2\u0080\u009cenable_tags\u00e2\u0080\u009d to 1\r\nJust fill in the blanks, do not modify the highlighted parts and everything should be ok.","5":"Edit the \u00e2\u0080\u009cSettings\u00e2\u0080\u009d section in blog.vim (starts at line 51). If you wish to use UTW tags, you should install the following plugin http:\/\/blog.circlesixdesign.com\/download\/utw-rpc-autotag\/ : and set \u00e2\u0080\u009cenable_tags\u00e2\u0080\u009d to 1\r\nJust fill in the blanks, do not modify the highlighted parts and everything should be ok.","first_name":"Adrien","6":"Adrien","last_name":"Friggeri","7":"Friggeri","releases":[{"0":"1953","vim_version":"7.0","1":"7.0","script_version":"0.91","2":"0.91","version_comment":"Minor encoding correction","3":"Minor encoding correction","package":"vimpress.tar.gz","4":"vimpress.tar.gz","src_id":"7348","5":"7348","creation_date":"1184319873","6":"1184319873"},{"0":"1953","vim_version":"7.0","1":"7.0","script_version":"0.9","2":"0.9","version_comment":"Initial upload","3":"Initial upload","package":"vimpress.tar.gz","4":"vimpress.tar.gz","src_id":"7347","5":"7347","creation_date":"1184319603","6":"1184319603"}]},"1952":{"script_id":"1952","0":"1952","script_name":"systemverilog.vim","1":"systemverilog.vim","script_type":"syntax","2":"syntax","summary":"Syntax for SystemVerilog","3":"Syntax for SystemVerilog","description":"IEEE 1800 SystemVerilog is the industry's first unified hardware description and verification language (HDVL) standard. SystemVerilog is a major extension of the established IEEE 1364 Verilog language.\r\ncheers!","4":"IEEE 1800 SystemVerilog is the industry's first unified hardware description and verification language (HDVL) standard. SystemVerilog is a major extension of the established IEEE 1364 Verilog language.\r\ncheers!","install_details":"Step 1: drop the file in ~\/.vim\/syntax (if the directory does not exist then create it)\r\n             Note: If you are using vim 7.0 or better, you can source SV.vba to autoinstall it regardless of which flavor of\r\n             operating system you are using VIM on!!\r\nStep 2: Append following lines in ~\/.vim\/filetype.vim\r\n\r\n if exists(\"did_load_filetypes\")\r\n          finish\r\n        endif\r\n        augroup filetypedetect\r\n          au! BufRead,BufNewFile *.sv    setfiletype SV\r\n          au! BufRead,BufNewFile *.svi   setfiletype SV\r\n        augroup END\r\n","5":"Step 1: drop the file in ~\/.vim\/syntax (if the directory does not exist then create it)\r\n             Note: If you are using vim 7.0 or better, you can source SV.vba to autoinstall it regardless of which flavor of\r\n             operating system you are using VIM on!!\r\nStep 2: Append following lines in ~\/.vim\/filetype.vim\r\n\r\n if exists(\"did_load_filetypes\")\r\n          finish\r\n        endif\r\n        augroup filetypedetect\r\n          au! BufRead,BufNewFile *.sv    setfiletype SV\r\n          au! BufRead,BufNewFile *.svi   setfiletype SV\r\n        augroup END\r\n","first_name":"Aditya","6":"Aditya","last_name":"Kher","7":"Kher","releases":[{"0":"1952","vim_version":"7.0","1":"7.0","script_version":"1.3","2":"1.3","version_comment":"vba for VIM 7.0 or better","3":"vba for VIM 7.0 or better","package":"sv.vba","4":"sv.vba","src_id":"8796","5":"8796","creation_date":"1213252843","6":"1213252843"},{"0":"1952","vim_version":"6.0","1":"6.0","script_version":"1.2","2":"1.2","version_comment":"vim 6 or better compatibility","3":"vim 6 or better compatibility","package":"sv.vim","4":"sv.vim","src_id":"8795","5":"8795","creation_date":"1213252534","6":"1213252534"}]},"1951":{"script_id":"1951","0":"1951","script_name":"gvim-pdfsync","1":"gvim-pdfsync","script_type":"utility","2":"utility","summary":"Open file in OS X Vim at a specific line. Good for PDFSync inverse searches.","3":"Open file in OS X Vim at a specific line. Good for PDFSync inverse searches.","description":"For a summary of the newest developments (e.g., PDFSync support in the new MacVim project), see\r\n\r\nhttp:\/\/phaseportrait.blogspot.com\/2007\/12\/pdfsync-inverse-searches-in-macvim.html\r\n\r\nBelow are the comments at the head of the gvim-pdfsync script. \r\n\r\n# gvim-pdfsync: Script for opening a file in Vim in OS X and positioning\r\n#               the cursor at a particular line. If the file is already\r\n#               open in an existing Vim, the cursor will be repositioned\r\n#               re-opening the file.\r\n#\r\n#               The script is meant to extend the inverse searching\r\n#               (c.f. PDFSync compatible PDF viewers (e.g., Skim or\r\n#               TeXniscope) or DVI viewers that pay attention to \r\n#               source specials (e.g., TeXniscope)) to MacVim.\r\n#\r\n# Author: Ted Pavlic\r\n#         ted@tedpavlic.com\r\n#         http:\/\/www.tedpavlic.com\/\r\n#\r\n# Usage: gvim-pdfsync \"%file\" [%line]\r\n#\r\n#        where %file is a file name and %line is a line number.\r\n#\r\n# History and acknowledgments: \r\n#\r\n#    The genesis of this script is this comment:\r\n#\r\n#    http:\/\/www.macosxhints.com\/comment.php?mode=view&cid=88674\r\n#\r\n#    to this thread:\r\n#\r\n#    http:\/\/www.macosxhints.com\/article.php?story=20070111095701823\r\n#\r\n#    Most of the important AppleScript is by Yonatan Amit, the original\r\n#    author of that thread.\r\n#\r\n# For more information (and history):\r\n#\r\n# http:\/\/phaseportrait.blogspot.com\/2007\/07\/pdfsync-inverse-searches-on-vim-for-os.html\r\n#","4":"For a summary of the newest developments (e.g., PDFSync support in the new MacVim project), see\r\n\r\nhttp:\/\/phaseportrait.blogspot.com\/2007\/12\/pdfsync-inverse-searches-in-macvim.html\r\n\r\nBelow are the comments at the head of the gvim-pdfsync script. \r\n\r\n# gvim-pdfsync: Script for opening a file in Vim in OS X and positioning\r\n#               the cursor at a particular line. If the file is already\r\n#               open in an existing Vim, the cursor will be repositioned\r\n#               re-opening the file.\r\n#\r\n#               The script is meant to extend the inverse searching\r\n#               (c.f. PDFSync compatible PDF viewers (e.g., Skim or\r\n#               TeXniscope) or DVI viewers that pay attention to \r\n#               source specials (e.g., TeXniscope)) to MacVim.\r\n#\r\n# Author: Ted Pavlic\r\n#         ted@tedpavlic.com\r\n#         http:\/\/www.tedpavlic.com\/\r\n#\r\n# Usage: gvim-pdfsync \"%file\" [%line]\r\n#\r\n#        where %file is a file name and %line is a line number.\r\n#\r\n# History and acknowledgments: \r\n#\r\n#    The genesis of this script is this comment:\r\n#\r\n#    http:\/\/www.macosxhints.com\/comment.php?mode=view&cid=88674\r\n#\r\n#    to this thread:\r\n#\r\n#    http:\/\/www.macosxhints.com\/article.php?story=20070111095701823\r\n#\r\n#    Most of the important AppleScript is by Yonatan Amit, the original\r\n#    author of that thread.\r\n#\r\n# For more information (and history):\r\n#\r\n# http:\/\/phaseportrait.blogspot.com\/2007\/07\/pdfsync-inverse-searches-on-vim-for-os.html\r\n#","install_details":"NOTE: THIS IS DESIGNED FOR OS X. It uses AppleScript.\r\n\r\nSave this file in the path somewhere. For example:\r\n\r\n\/usr\/local\/bin\/gvim-pdfsync\r\n\r\nThen chmod it 0755. For example,\r\n\r\nchmod 0755 \/usr\/local\/bin\/gvim-pdfsync\r\n\r\nIt then can be used like this:\r\n\r\ngvim-pdfsync \"%file\" %line\r\n\r\nwhere %file is the name of the file being opened and %line is the desired line number for the cursor. If you run it again with a different line number, the Vim application will reposition the cursor.","5":"NOTE: THIS IS DESIGNED FOR OS X. It uses AppleScript.\r\n\r\nSave this file in the path somewhere. For example:\r\n\r\n\/usr\/local\/bin\/gvim-pdfsync\r\n\r\nThen chmod it 0755. For example,\r\n\r\nchmod 0755 \/usr\/local\/bin\/gvim-pdfsync\r\n\r\nIt then can be used like this:\r\n\r\ngvim-pdfsync \"%file\" %line\r\n\r\nwhere %file is the name of the file being opened and %line is the desired line number for the cursor. If you run it again with a different line number, the Vim application will reposition the cursor.","first_name":"Ted","6":"Ted","last_name":"Pavlic","7":"Pavlic","releases":[{"0":"1951","vim_version":"6.0","1":"6.0","script_version":"1.03","2":"1.03","version_comment":"More conventional usage line. Updated documentation. Trivial changes.","3":"More conventional usage line. Updated documentation. Trivial changes.","package":"gvim-pdfsync","4":"gvim-pdfsync","src_id":"7387","5":"7387","creation_date":"1184924239","6":"1184924239"},{"0":"1951","vim_version":"6.0","1":"6.0","script_version":"1.02","2":"1.02","version_comment":"Added \"usage\" and changed some internal handling of shell variables. Trivial changes.","3":"Added \"usage\" and changed some internal handling of shell variables. Trivial changes.","package":"gvim-pdfsync","4":"gvim-pdfsync","src_id":"7368","5":"7368","creation_date":"1184673921","6":"1184673921"},{"0":"1951","vim_version":"6.0","1":"6.0","script_version":"1.01","2":"1.01","version_comment":"Somehow in a copy and paste while putting the script together, a couple of \\\\'s turned into \\'s. \r\n\r\nFixed that. Now the script should work fine.","3":"Somehow in a copy and paste while putting the script together, a couple of \\\\'s turned into \\'s. \r\n\r\nFixed that. Now the script should work fine.","package":"gvim-pdfsync","4":"gvim-pdfsync","src_id":"7343","5":"7343","creation_date":"1184175258","6":"1184175258"}]},"1950":{"script_id":"1950","0":"1950","script_name":"VimExplorer","1":"VimExplorer","script_type":"utility","2":"utility","summary":"VE - the File Manager within Vim!","3":"VE - the File Manager within Vim!","description":"Get the latest version from Github:\r\nhttps:\/\/github.com\/mbbill\/VimExplorer\r\n\r\n Usage:        :h VimExplorer\r\nScreen shots: \r\nhttp:\/\/mbbill.googlepages.com\/VE1.PNG\r\nhttp:\/\/mbbill.googlepages.com\/VE2.PNG\r\n\r\nCONTENTS                                        *VimExplorer-contents*\r\n\r\n1.  Intro.......................................|VimExplorer-start|\r\n2.  Functionality...............................|VimExplorer-functionality|\r\n    2.1  Tree Panel Hotkeys.....................|VimExplorer-treehotkey|\r\n    2.2  File Panel Hotkeys.....................|VimExplorer-filehotkey|\r\n    2.3  Commands...............................|VimExplorer-commands|\r\n3.  Directory Browsing..........................|VimExplorer-browse|\r\n    3.1  Tree Browsing..........................|VimExplorer-treebrowse|\r\n    3.2  File Browsing..........................|VimExplorer-filebrowse|\r\n    3.3  Forward and Backward...................|VimExplorer-forbackward|\r\n    3.4  Favorites..............................|VimExplorer-favorite|\r\n    3.5  Temp Marks.............................|VimExplorer-tempmark|\r\n4.  Marks.......................................|VimExplorer-mark|\r\n    4.1  Single File Marks......................|VimExplorer-marksingle|\r\n    4.2  Visual Marks...........................|VimExplorer-markvisual|\r\n    4.3  Regexp Marks...........................|VimExplorer-markregexp|\r\n5.  File operations.............................|VimExplorer-fileoperation|\r\n    5.1  Create.................................|VimExplorer-new|\r\n    5.2  Move...................................|VimExplorer-move|\r\n    5.3  Delete.................................|VimExplorer-delete|\r\n    5.4  Diff...................................|VimExplorer-diff|\r\n    5.5  Search.................................|VimExplorer-search|\r\n    5.6  Other Operations.......................|VimExplorer-otherfileopt|\r\n6.  Other Functionalities.......................|VimExplorer-otherfuncs|\r\n7.  Customization...............................|VimExplorer-customize|\r\n    7.1  Normal Options.........................|VimExplorer-custnormal|\r\n    7.2  Hotkey Customization...................|VimExplorer-custhotkey|\r\n    7.3  Command Customization..................|VimExplorer-custcommand|\r\n8.  The Author..................................|VimExplorer-author|\r\n9.  Problems and Fixes..........................|VimExplorer-problems|\r\n\r\n\r\n==============================================================================\r\n1.  Intro                                       *VimExplorer-start*\r\n\r\nWhat is VimExplorer ？\r\nVimExplorer is a file manager, it can do a lot of file operations such as\r\ncopy, delete, move, preview, search and so on. Also it has a variety of other\r\ncapacities and customization abilities.\r\n\r\nYou can start VimExplorer by the following command:\r\n>\r\n        :VE\r\n<\r\nThen it will ask you for the starting directory, default is the current path.\r\n>\r\n        VimExplorer (directory): \/home\/username\/\r\n<\r\nYou can change it to some other directories or just push \"Enter\" to start it.\r\n\r\nThe second approach to start VimExplorer:\r\n>\r\n        :VE [directory]\r\n<\r\nExample:\r\n>\r\n        :VE \/usr\/src\/\r\n<\r\nNow, VimExplorer will start using the path '\/usr\/src\/'. When you are typing\r\nthe path, <tab> and <ctrl-d> will help you to complete the path automatically.\r\nAfter all of these operations, you can see a new tab which has two panels\r\nwithin it, one is the \"Tree Panel\" and the other is \"File Panel\". From now you\r\nwill have a happy journey using the powerful file manager.","4":"Get the latest version from Github:\r\nhttps:\/\/github.com\/mbbill\/VimExplorer\r\n\r\n Usage:        :h VimExplorer\r\nScreen shots: \r\nhttp:\/\/mbbill.googlepages.com\/VE1.PNG\r\nhttp:\/\/mbbill.googlepages.com\/VE2.PNG\r\n\r\nCONTENTS                                        *VimExplorer-contents*\r\n\r\n1.  Intro.......................................|VimExplorer-start|\r\n2.  Functionality...............................|VimExplorer-functionality|\r\n    2.1  Tree Panel Hotkeys.....................|VimExplorer-treehotkey|\r\n    2.2  File Panel Hotkeys.....................|VimExplorer-filehotkey|\r\n    2.3  Commands...............................|VimExplorer-commands|\r\n3.  Directory Browsing..........................|VimExplorer-browse|\r\n    3.1  Tree Browsing..........................|VimExplorer-treebrowse|\r\n    3.2  File Browsing..........................|VimExplorer-filebrowse|\r\n    3.3  Forward and Backward...................|VimExplorer-forbackward|\r\n    3.4  Favorites..............................|VimExplorer-favorite|\r\n    3.5  Temp Marks.............................|VimExplorer-tempmark|\r\n4.  Marks.......................................|VimExplorer-mark|\r\n    4.1  Single File Marks......................|VimExplorer-marksingle|\r\n    4.2  Visual Marks...........................|VimExplorer-markvisual|\r\n    4.3  Regexp Marks...........................|VimExplorer-markregexp|\r\n5.  File operations.............................|VimExplorer-fileoperation|\r\n    5.1  Create.................................|VimExplorer-new|\r\n    5.2  Move...................................|VimExplorer-move|\r\n    5.3  Delete.................................|VimExplorer-delete|\r\n    5.4  Diff...................................|VimExplorer-diff|\r\n    5.5  Search.................................|VimExplorer-search|\r\n    5.6  Other Operations.......................|VimExplorer-otherfileopt|\r\n6.  Other Functionalities.......................|VimExplorer-otherfuncs|\r\n7.  Customization...............................|VimExplorer-customize|\r\n    7.1  Normal Options.........................|VimExplorer-custnormal|\r\n    7.2  Hotkey Customization...................|VimExplorer-custhotkey|\r\n    7.3  Command Customization..................|VimExplorer-custcommand|\r\n8.  The Author..................................|VimExplorer-author|\r\n9.  Problems and Fixes..........................|VimExplorer-problems|\r\n\r\n\r\n==============================================================================\r\n1.  Intro                                       *VimExplorer-start*\r\n\r\nWhat is VimExplorer ？\r\nVimExplorer is a file manager, it can do a lot of file operations such as\r\ncopy, delete, move, preview, search and so on. Also it has a variety of other\r\ncapacities and customization abilities.\r\n\r\nYou can start VimExplorer by the following command:\r\n>\r\n        :VE\r\n<\r\nThen it will ask you for the starting directory, default is the current path.\r\n>\r\n        VimExplorer (directory): \/home\/username\/\r\n<\r\nYou can change it to some other directories or just push \"Enter\" to start it.\r\n\r\nThe second approach to start VimExplorer:\r\n>\r\n        :VE [directory]\r\n<\r\nExample:\r\n>\r\n        :VE \/usr\/src\/\r\n<\r\nNow, VimExplorer will start using the path '\/usr\/src\/'. When you are typing\r\nthe path, <tab> and <ctrl-d> will help you to complete the path automatically.\r\nAfter all of these operations, you can see a new tab which has two panels\r\nwithin it, one is the \"Tree Panel\" and the other is \"File Panel\". From now you\r\nwill have a happy journey using the powerful file manager.","install_details":"Put vimExplorer.vim to plugin\/ directory, that's all.","5":"Put vimExplorer.vim to plugin\/ directory, that's all.","first_name":"Ming","6":"Ming","last_name":"Bai","7":"Bai","releases":[{"0":"1950","vim_version":"7.0","1":"7.0","script_version":"0.99","2":"0.99","version_comment":"Some new features and bug-fixes.","3":"Some new features and bug-fixes.","package":"vimExplorer.vim","4":"vimExplorer.vim","src_id":"16054","5":"16054","creation_date":"1310094445","6":"1310094445"},{"0":"1950","vim_version":"7.0","1":"7.0","script_version":"0.98","2":"0.98","version_comment":"(BE SURE TO UPDATE TO THIS VERSION, THE PREVIOUS VERSION HAS A SERIOUS BUG WHICH WOULD CAUSE FILE LOST!)\r\n0.98\r\n    -   Add option VEConf_filePanelFilter.\r\n    -   Bug fix: Escape <space> in command 'e' 'se' 'u' and '='.\r\n    -   Bug fix: 'Cut' and 'Paste' command causes file lost.\r\n    -   Change the default hotkey 'M' and 'B' to 'm','J'.\r\n    -   Change forward and backward hotkey to |<c-o>| and |<c-i>|(<tab>).\r\n    -   Change hotkey |<tab>| to |<c-tab>|.\r\n    -   Change hotkey |mr| |mv| |md| |me| |mc| to |Mr| |Mv| |Md| |Me| |Mc|.\r\n    -   When GUI is running, use confirm() to pop a dialog instead of input().\r\n","3":"(BE SURE TO UPDATE TO THIS VERSION, THE PREVIOUS VERSION HAS A SERIOUS BUG WHICH WOULD CAUSE FILE LOST!)\r\n0.98\r\n    -   Add option VEConf_filePanelFilter.\r\n    -   Bug fix: Escape <space> in command 'e' 'se' 'u' and '='.\r\n    -   Bug fix: 'Cut' and 'Paste' command causes file lost.\r\n    -   Change the default hotkey 'M' and 'B' to 'm','J'.\r\n    -   Change forward and backward hotkey to |<c-o>| and |<c-i>|(<tab>).\r\n    -   Change hotkey |<tab>| to |<c-tab>|.\r\n    -   Change hotkey |mr| |mv| |md| |me| |mc| to |Mr| |Mv| |Md| |Me| |Mc|.\r\n    -   When GUI is running, use confirm() to pop a dialog instead of input().\r\n","package":"vimExplorer.vim","4":"vimExplorer.vim","src_id":"7461","5":"7461","creation_date":"1186532332","6":"1186532332"},{"0":"1950","vim_version":"7.0","1":"7.0","script_version":"0.97","2":"0.97","version_comment":"0.97\r\n    - Change the behaviour of hotkey 'F', now it adds the path under cursor to\r\n        favorite list. If no path under cursor, use current working path\r\n        instead.(Thanks to Vincent Wang)\r\n    - Bug fix: escape ' %#' for path.\r\n    - Add options |g:VEConf_usingKDE| and |g:VEConf_usingGnome| for starting\r\n        program in *nix environment.\r\n    - Check if the script is already loaded, thanks to Dennis Hostetler.\r\n    - Change default g:VEConf_systemEncoding to '' (empty)\r\n    - Bug fix: favorite selection out of range.\r\n","3":"0.97\r\n    - Change the behaviour of hotkey 'F', now it adds the path under cursor to\r\n        favorite list. If no path under cursor, use current working path\r\n        instead.(Thanks to Vincent Wang)\r\n    - Bug fix: escape ' %#' for path.\r\n    - Add options |g:VEConf_usingKDE| and |g:VEConf_usingGnome| for starting\r\n        program in *nix environment.\r\n    - Check if the script is already loaded, thanks to Dennis Hostetler.\r\n    - Change default g:VEConf_systemEncoding to '' (empty)\r\n    - Bug fix: favorite selection out of range.\r\n","package":"vimExplorer.vim","4":"vimExplorer.vim","src_id":"7408","5":"7408","creation_date":"1185271440","6":"1185271440"},{"0":"1950","vim_version":"7.0","1":"7.0","script_version":"0.96","2":"0.96","version_comment":"bug fix.","3":"bug fix.","package":"vimExplorer.vim","4":"vimExplorer.vim","src_id":"7373","5":"7373","creation_date":"1184733919","6":"1184733919"},{"0":"1950","vim_version":"7.0","1":"7.0","script_version":"0.95","2":"0.95","version_comment":"Initial upload","3":"Initial upload","package":"vimExplorer.vim","4":"vimExplorer.vim","src_id":"7339","5":"7339","creation_date":"1184148292","6":"1184148292"}]},"1948":{"script_id":"1948","0":"1948","script_name":"Dictionary","1":"Dictionary","script_type":"utility","2":"utility","summary":"English Dictionary","3":"English Dictionary","description":"English Dictionary","4":"English Dictionary","install_details":"Just copy Dictionary.vim to .\/.vimrc\/plugin\/\r\nTo use this function, use :Dic<cr>\r\n\r\n","5":"Just copy Dictionary.vim to .\/.vimrc\/plugin\/\r\nTo use this function, use :Dic<cr>\r\n\r\n","first_name":"SungTae","6":"SungTae","last_name":"Moon","7":"Moon","releases":[{"0":"1948","vim_version":"6.0","1":"6.0","script_version":"0.5","2":"0.5","version_comment":"Initial upload","3":"Initial upload","package":"dictionary.vim","4":"dictionary.vim","src_id":"7338","5":"7338","creation_date":"1184131824","6":"1184131824"}]},"1947":{"script_id":"1947","0":"1947","script_name":"outline","1":"outline","script_type":"utility","2":"utility","summary":"Create your own custom view of the file based on regex","3":"Create your own custom view of the file based on regex","description":"Vim has many possibilites to let you find the code you want to have a look at.\r\nThis script shows all matches of a regular expression in another buffer together with line numbers. The cursor will be placed where you have been.\r\nSo you won't loose orientation.\r\n\r\nI think a small example will help you much to illustrate what this script can do for you\r\n\r\nThe script is called autoload\/vl\/ui\/navigation\/jump_to_code_by_regex.vim\r\n\r\nand looks like :\r\n==============================\r\n[...]\r\nfunction! vl#ui#navigation#jump_to_code_by_regex#Outline(regex, ...)\r\n  exec vl#lib#brief#args#GetOptionalArg('try_higlight', string(0))\r\n[...]\r\nendfunction\r\n[...]\r\nfunction ...\r\n==============================\r\n\r\nAfter using the mapping you'll get \r\n==============================\r\n   17  function! vl#ui#navigation#jump_to_code_by_regex#Outline(regex, ...)\r\n   66  function! vl#ui#navigation#jump_to_code_by_regex#JumpToPos()\r\n   75  function! vl#ui#navigation#jump_to_code_by_regex#AddOutlineMappings(regex)\r\n==============================\r\nPressing enter will take you to line 17 \/ 66 etc..\r\n\r\nOf course you can also find definitions this way (use let as regex and you'll get)\r\n====================\r\n   19    let ft = &filetype\r\n   20    let file = expand('%')\r\n   21    let window = winnr()\r\n[...]\r\n=====================\r\nPressing <c-o> will take you back\r\n\r\nI'v put some minor effort into higlighting the regular expression match. Thus you can use \\zs and \\ze to higlight special words.\r\nHow nice this works depends on the already existing syntax definitions. This can be improved much","4":"Vim has many possibilites to let you find the code you want to have a look at.\r\nThis script shows all matches of a regular expression in another buffer together with line numbers. The cursor will be placed where you have been.\r\nSo you won't loose orientation.\r\n\r\nI think a small example will help you much to illustrate what this script can do for you\r\n\r\nThe script is called autoload\/vl\/ui\/navigation\/jump_to_code_by_regex.vim\r\n\r\nand looks like :\r\n==============================\r\n[...]\r\nfunction! vl#ui#navigation#jump_to_code_by_regex#Outline(regex, ...)\r\n  exec vl#lib#brief#args#GetOptionalArg('try_higlight', string(0))\r\n[...]\r\nendfunction\r\n[...]\r\nfunction ...\r\n==============================\r\n\r\nAfter using the mapping you'll get \r\n==============================\r\n   17  function! vl#ui#navigation#jump_to_code_by_regex#Outline(regex, ...)\r\n   66  function! vl#ui#navigation#jump_to_code_by_regex#JumpToPos()\r\n   75  function! vl#ui#navigation#jump_to_code_by_regex#AddOutlineMappings(regex)\r\n==============================\r\nPressing enter will take you to line 17 \/ 66 etc..\r\n\r\nOf course you can also find definitions this way (use let as regex and you'll get)\r\n====================\r\n   19    let ft = &filetype\r\n   20    let file = expand('%')\r\n   21    let window = winnr()\r\n[...]\r\n=====================\r\nPressing <c-o> will take you back\r\n\r\nI'v put some minor effort into higlighting the regular expression match. Thus you can use \\zs and \\ze to higlight special words.\r\nHow nice this works depends on the already existing syntax definitions. This can be improved much","install_details":"Use http:\/\/www.vim.org\/scripts\/script.php?script_id=2014 instead.\r\n\r\nJust source the file and follow the instructions.\r\nYou'll be asked before any action is taken.\r\n\r\nIf you don't feel comfortable installing to .vim insntall to another arbitrary directory and add it to your runtimepath\r\n(let runtimepath+= ..)\r\n\r\nDefault mappings are provided in the \r\nfunction! vl#ui#navigation#jump_to_code_by_regex#AddOutlineMappings(regex)\r\n\r\nftplugin\/vim.vim:\r\ncall vl#ui#navigation#jump_to_code_by_regex#AddOutlineMappings('^\\s*fun.*')\r\n..\/c.vim:\r\n\"outline mappings and regex\r\nlet s:cpp_prefix='\\%(\\w\\+\\s\\+\\)\\='\r\nlet s:ret_type='[a-zA-Z0-9\\&* \\t]\\+\\s\\+'\r\nlet s:name='\\%(\\w\\+\\::\\)\\=\\w\\+\\s*'\r\nlet s:func_args='([ \\t,0-9a-zA-Z\\&*\\n\\[\\]_]*)\\ze\\s*{'\r\nlet s:func_pattern=substitute(s:cpp_prefix.s:ret_type.s:name.s:func_args,'\\\\s','[ \\\\t\\\\n]','g')\r\nlet g:func_pattern=s:func_pattern \r\nlet s:pattern = string('\\%('.s:func_pattern.'\\)\\\\|class')\r\nexec 'noremap <buffer> <m-o><m-s> :call vl#ui#navigation#jump_to_code_by_regex#Outline('.s:pattern.')<cr>\/'\r\nexec 'noremap <buffer> <m-o><m-l> :call vl#ui#navigation#jump_to_code_by_regex#Outline('.s:pattern.')<cr>'\r\netc..\r\n\r\nIf you still have problems drop me a mail.\r\n\r\nPatches welcome.","5":"Use http:\/\/www.vim.org\/scripts\/script.php?script_id=2014 instead.\r\n\r\nJust source the file and follow the instructions.\r\nYou'll be asked before any action is taken.\r\n\r\nIf you don't feel comfortable installing to .vim insntall to another arbitrary directory and add it to your runtimepath\r\n(let runtimepath+= ..)\r\n\r\nDefault mappings are provided in the \r\nfunction! vl#ui#navigation#jump_to_code_by_regex#AddOutlineMappings(regex)\r\n\r\nftplugin\/vim.vim:\r\ncall vl#ui#navigation#jump_to_code_by_regex#AddOutlineMappings('^\\s*fun.*')\r\n..\/c.vim:\r\n\"outline mappings and regex\r\nlet s:cpp_prefix='\\%(\\w\\+\\s\\+\\)\\='\r\nlet s:ret_type='[a-zA-Z0-9\\&* \\t]\\+\\s\\+'\r\nlet s:name='\\%(\\w\\+\\::\\)\\=\\w\\+\\s*'\r\nlet s:func_args='([ \\t,0-9a-zA-Z\\&*\\n\\[\\]_]*)\\ze\\s*{'\r\nlet s:func_pattern=substitute(s:cpp_prefix.s:ret_type.s:name.s:func_args,'\\\\s','[ \\\\t\\\\n]','g')\r\nlet g:func_pattern=s:func_pattern \r\nlet s:pattern = string('\\%('.s:func_pattern.'\\)\\\\|class')\r\nexec 'noremap <buffer> <m-o><m-s> :call vl#ui#navigation#jump_to_code_by_regex#Outline('.s:pattern.')<cr>\/'\r\nexec 'noremap <buffer> <m-o><m-l> :call vl#ui#navigation#jump_to_code_by_regex#Outline('.s:pattern.')<cr>'\r\netc..\r\n\r\nIf you still have problems drop me a mail.\r\n\r\nPatches welcome.","first_name":"Marc","6":"Marc","last_name":"Weber","7":"Weber","releases":[{"0":"1947","vim_version":"7.0","1":"7.0","script_version":"0.0","2":"0.0","version_comment":"Initial upload","3":"Initial upload","package":"vimlib_outline_installer_sourceme.zip","4":"vimlib_outline_installer_sourceme.zip","src_id":"7334","5":"7334","creation_date":"1183911393","6":"1183911393"}]},"1946":{"script_id":"1946","0":"1946","script_name":"QuickFixFilterUtil","1":"QuickFixFilterUtil","script_type":"utility","2":"utility","summary":"filter matched files in the quickfix window manually\/ drop .svn .hg _darcs","3":"filter matched files in the quickfix window manually\/ drop .svn .hg _darcs","description":"When grepping I don\\\\\\'t want to get the files stored by the version control system. That\\\\\\'s why I\\\\\\'ve written this script to remove those matches. \r\nIt can also be used to replace filenames (cygwin problem)..\r\nIf you are unsure which and how many files have been removed just invoke :LogShowAll and rerun. \r\n","4":"When grepping I don\\\\\\'t want to get the files stored by the version control system. That\\\\\\'s why I\\\\\\'ve written this script to remove those matches. \r\nIt can also be used to replace filenames (cygwin problem)..\r\nIf you are unsure which and how many files have been removed just invoke :LogShowAll and rerun. \r\n","install_details":"Just source the files and follow the instructions.\r\nYou\\\\\\'ll be asked before any action is taken.\r\n\r\nIf you don\\\\\\'t feel comfortable installing to .vim insntall to another arbitrary directory and add it to your runtimepath\r\n(let runtimepath+= ..)\r\n\r\nDefault mappings are provided in the file\r\n\/autoload\/vl\/lib\/quickfix\/filtermod.vim\r\nfunction vl#lib#quickfix#filtermod#EnableQuickFixScript()\r\n\r\nIf you still have problems drop me a mail.\r\n\r\nPatches welcome.","5":"Just source the files and follow the instructions.\r\nYou\\\\\\'ll be asked before any action is taken.\r\n\r\nIf you don\\\\\\'t feel comfortable installing to .vim insntall to another arbitrary directory and add it to your runtimepath\r\n(let runtimepath+= ..)\r\n\r\nDefault mappings are provided in the file\r\n\/autoload\/vl\/lib\/quickfix\/filtermod.vim\r\nfunction vl#lib#quickfix#filtermod#EnableQuickFixScript()\r\n\r\nIf you still have problems drop me a mail.\r\n\r\nPatches welcome.","first_name":"Marc","6":"Marc","last_name":"Weber","7":"Weber","releases":[{"0":"1946","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"The autocommands now do work .git are removed automatically as well now","3":"The autocommands now do work .git are removed automatically as well now","package":"vimlib_quickfixfilter_installer_sourceme.zip","4":"vimlib_quickfixfilter_installer_sourceme.zip","src_id":"8151","5":"8151","creation_date":"1200237556","6":"1200237556"}]},"1945":{"script_id":"1945","0":"1945","script_name":"JSON.vim","1":"JSON.vim","script_type":"syntax","2":"syntax","summary":"A syntax highlighting file for JSON","3":"A syntax highlighting file for JSON","description":"NOTE\r\n==============================================================\r\nPlease use https:\/\/github.com\/elzr\/vim-json \u00e2\u0080\u0094 it's an updated version of my this script and is Pathogen compatible.\r\n\r\nThis script will NOT be updated anymore, again, see the version on the URL above.\r\n==============================================================\r\n\r\nA simple highlighting file for JSON constructs.","4":"NOTE\r\n==============================================================\r\nPlease use https:\/\/github.com\/elzr\/vim-json \u00e2\u0080\u0094 it's an updated version of my this script and is Pathogen compatible.\r\n\r\nThis script will NOT be updated anymore, again, see the version on the URL above.\r\n==============================================================\r\n\r\nA simple highlighting file for JSON constructs.","install_details":"To your filetype.vim just add something like:\r\n\r\nau! BufRead,BufNewFile *.json set filetype=json\r\n\r\nand in your generic list of autocommands add something like the following for indentation and folding:\r\n\r\naugroup json_autocmd\r\n  autocmd!\r\n  autocmd FileType json set autoindent\r\n  autocmd FileType json set formatoptions=tcq2l\r\n  autocmd FileType json set textwidth=78 shiftwidth=2\r\n  autocmd FileType json set softtabstop=2 tabstop=8\r\n  autocmd FileType json set expandtab\r\n  autocmd FileType json set foldmethod=syntax\r\naugroup END","5":"To your filetype.vim just add something like:\r\n\r\nau! BufRead,BufNewFile *.json set filetype=json\r\n\r\nand in your generic list of autocommands add something like the following for indentation and folding:\r\n\r\naugroup json_autocmd\r\n  autocmd!\r\n  autocmd FileType json set autoindent\r\n  autocmd FileType json set formatoptions=tcq2l\r\n  autocmd FileType json set textwidth=78 shiftwidth=2\r\n  autocmd FileType json set softtabstop=2 tabstop=8\r\n  autocmd FileType json set expandtab\r\n  autocmd FileType json set foldmethod=syntax\r\naugroup END","first_name":"Jeroen","6":"Jeroen","last_name":"Ruigrok van der Werven","7":"Ruigrok van der Werven","releases":[{"0":"1945","vim_version":"7.0","1":"7.0","script_version":"0.4","2":"0.4","version_comment":"Fixed some syntax highlighting for numbers.\r\nSmall improvements and fixes.","3":"Fixed some syntax highlighting for numbers.\r\nSmall improvements and fixes.","package":"json.vim","4":"json.vim","src_id":"10853","5":"10853","creation_date":"1245180464","6":"1245180464"}]},"1944":{"script_id":"1944","0":"1944","script_name":"stingray","1":"stingray","script_type":"color scheme","2":"color scheme","summary":"blue gray colorscheme","3":"blue gray colorscheme","description":"Color Scheme that tries to make the actual program logic more visible.\r\nComments and type identifiers are displayed in colors that try to put them in the background. \r\nThey are still visible if necessary, but can be ignored if desired.\r\nGenerally the more important something is to algorithmic logic, the brighter it should be.","4":"Color Scheme that tries to make the actual program logic more visible.\r\nComments and type identifiers are displayed in colors that try to put them in the background. \r\nThey are still visible if necessary, but can be ignored if desired.\r\nGenerally the more important something is to algorithmic logic, the brighter it should be.","install_details":"drop in your colors directory either in your vim install directory or in your personal colors directory.","5":"drop in your colors directory either in your vim install directory or in your personal colors directory.","first_name":"Connor","6":"Connor","last_name":"Berry","7":"Berry","releases":[{"0":"1944","vim_version":"6.0","1":"6.0","script_version":".1","2":".1","version_comment":"Initial upload","3":"Initial upload","package":"stingray.vim","4":"stingray.vim","src_id":"7326","5":"7326","creation_date":"1183714686","6":"1183714686"}]},"1943":{"script_id":"1943","0":"1943","script_name":"fx.vim","1":"fx.vim","script_type":"syntax","2":"syntax","summary":"JavaFX Script syntax","3":"JavaFX Script syntax","description":"This is a simple syntax mode for the new JavaFX Script language. This is also my first-ever vim syntax file. I couldn't get some things working, such as types for function arguments. Feedback, contributions, and enhancements are most welcome!","4":"This is a simple syntax mode for the new JavaFX Script language. This is also my first-ever vim syntax file. I couldn't get some things working, such as types for function arguments. Feedback, contributions, and enhancements are most welcome!","install_details":"","5":"","first_name":"Yang","6":"Yang","last_name":"Zhang","7":"Zhang","releases":[{"0":"1943","vim_version":"6.0","1":"6.0","script_version":"0.2","2":"0.2","version_comment":"Updated with more keywords, based on some users' negative feedback :)","3":"Updated with more keywords, based on some users' negative feedback :)","package":"fx.vim","4":"fx.vim","src_id":"9840","5":"9840","creation_date":"1232340360","6":"1232340360"},{"0":"1943","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"fx.vim","4":"fx.vim","src_id":"7321","5":"7321","creation_date":"1183480105","6":"1183480105"}]},"1940":{"script_id":"1940","0":"1940","script_name":"drools.vim","1":"drools.vim","script_type":"syntax","2":"syntax","summary":"Syntax highlighting for DROOLS Rules Sets.","3":"Syntax highlighting for DROOLS Rules Sets.","description":"Syntax highlighting for \"Rules Set\" files for the DROOLS Rules Engine, a.k.a, JBoss Rules: http:\/\/labs.jboss.com\/jbossrules\/. This does a ton of borrowing from the existing Java syntax file, as written by Claudio Fleiner <claudio@fleiner.com>, so I hope he doesn't mind. This is just an initial version that I wrote to make writing DROOLS files a little more bearable, so if you see any desired improvements, just e-mail me and let me know. Thanks!","4":"Syntax highlighting for \"Rules Set\" files for the DROOLS Rules Engine, a.k.a, JBoss Rules: http:\/\/labs.jboss.com\/jbossrules\/. This does a ton of borrowing from the existing Java syntax file, as written by Claudio Fleiner <claudio@fleiner.com>, so I hope he doesn't mind. This is just an initial version that I wrote to make writing DROOLS files a little more bearable, so if you see any desired improvements, just e-mail me and let me know. Thanks!","install_details":"In the \"autocmds\" section of your .vimrc file, just add this line:\r\nau bufreadpost,filereadpost *.drl set ft=drools","5":"In the \"autocmds\" section of your .vimrc file, just add this line:\r\nau bufreadpost,filereadpost *.drl set ft=drools","first_name":"Alan","6":"Alan","last_name":"Daniels","7":"Daniels","releases":[{"0":"1940","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"drools.vim","4":"drools.vim","src_id":"7315","5":"7315","creation_date":"1183361764","6":"1183361764"}]},"1939":{"script_id":"1939","0":"1939","script_name":"autofmt","1":"autofmt","script_type":"utility","2":"utility","summary":"text formatting plugin","3":"text formatting plugin","description":"This is a 'formatexpr' plugin and framework for it.\r\n\r\nFollowing method can be used:\r\n  compat (Vim compatible)\r\n  uax14 (Implementation of UAX #14)\r\n  Japanese\r\n\r\nUAX #14: Line Breaking Properties: http:\/\/unicode.org\/reports\/tr14\/.\r\n","4":"This is a 'formatexpr' plugin and framework for it.\r\n\r\nFollowing method can be used:\r\n  compat (Vim compatible)\r\n  uax14 (Implementation of UAX #14)\r\n  Japanese\r\n\r\nUAX #14: Line Breaking Properties: http:\/\/unicode.org\/reports\/tr14\/.\r\n","install_details":":set runtimepath+=\/path\/to\/autofmt\/\r\n:set formatexpr=autofmt#compat#formatexpr()\r\n\r\nlatest source: https:\/\/github.com\/vim-jp\/autofmt","5":":set runtimepath+=\/path\/to\/autofmt\/\r\n:set formatexpr=autofmt#compat#formatexpr()\r\n\r\nlatest source: https:\/\/github.com\/vim-jp\/autofmt","first_name":"Yukihiro","6":"Yukihiro","last_name":"Nakadaira","7":"Nakadaira","releases":[{"0":"1939","vim_version":"7.3","1":"7.3","script_version":"1.6","2":"1.6","version_comment":"vimball","3":"vimball","package":"autofmt.vmb.gz","4":"autofmt.vmb.gz","src_id":"16792","5":"16792","creation_date":"1320291877","6":"1320291877"},{"0":"1939","vim_version":"7.3","1":"7.3","script_version":"1.6","2":"1.6","version_comment":"bug fix.\r\nAdded documentation to customize uax14 behavior.","3":"bug fix.\r\nAdded documentation to customize uax14 behavior.","package":"autofmt.zip","4":"autofmt.zip","src_id":"16750","5":"16750","creation_date":"1319718960","6":"1319718960"},{"0":"1939","vim_version":"7.3","1":"7.3","script_version":"1.5","2":"1.5","version_comment":"Updated to UAX #14 revision 26.","3":"Updated to UAX #14 revision 26.","package":"autofmt.zip","4":"autofmt.zip","src_id":"14714","5":"14714","creation_date":"1294591430","6":"1294591430"},{"0":"1939","vim_version":"7.0","1":"7.0","script_version":"1.4","2":"1.4","version_comment":"Fixed some incompatibility of comment formatting.","3":"Fixed some incompatibility of comment formatting.","package":"autofmt.zip","4":"autofmt.zip","src_id":"11719","5":"11719","creation_date":"1258103261","6":"1258103261"},{"0":"1939","vim_version":"7.0","1":"7.0","script_version":"1.3","2":"1.3","version_comment":"Fixed a bug that c, q flags of formatoptions didn't work.","3":"Fixed a bug that c, q flags of formatoptions didn't work.","package":"autofmt.zip","4":"autofmt.zip","src_id":"10447","5":"10447","creation_date":"1240634267","6":"1240634267"},{"0":"1939","vim_version":"7.0","1":"7.0","script_version":"1.2","2":"1.2","version_comment":"Removed dependency of unicode table from compat.","3":"Removed dependency of unicode table from compat.","package":"autofmt.zip","4":"autofmt.zip","src_id":"8563","5":"8563","creation_date":"1208239154","6":"1208239154"},{"0":"1939","vim_version":"7.0","1":"7.0","script_version":"1.1","2":"1.1","version_comment":"bug fix","3":"bug fix","package":"autofmt.zip","4":"autofmt.zip","src_id":"7324","5":"7324","creation_date":"1183697317","6":"1183697317"},{"0":"1939","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"autofmt.zip","4":"autofmt.zip","src_id":"7312","5":"7312","creation_date":"1183289496","6":"1183289496"}]},"1938":{"script_id":"1938","0":"1938","script_name":"todo.vim","1":"todo.vim","script_type":"syntax","2":"syntax","summary":"Syntax highlighting for simple to do lists.","3":"Syntax highlighting for simple to do lists.","description":"Adds syntax highlighting for simple to do lists.\r\n\r\nThis is pretty rudimentary right now, but I've been using it for a while. Please send me comments\/suggestions.\r\n\r\nThe file todo.vim lists known limitations\/bugs.","4":"Adds syntax highlighting for simple to do lists.\r\n\r\nThis is pretty rudimentary right now, but I've been using it for a while. Please send me comments\/suggestions.\r\n\r\nThe file todo.vim lists known limitations\/bugs.","install_details":"Quick install:\r\n\r\n    o Extract todo.vim under the syntax directory.\r\n    o Add the following to your .vimrc (or to ftdetect\/filetype.vim; sample filetype.vim is included)\r\n\r\n        au BufRead,BufNewFile *.todo setfiletype todo\r\n\r\nAny file of the form *.todo or any file whose filetype is set as 'todo' will now have syntax highlighting enabled. Read the comments in todo.vim and view the sample file sample.todo for details.\r\n\r\nOptional: Add the following to your .vimrc (or to scripts.vim file under the config directory; sample scripts.vim is included). This allows, in addition, for files starting with '#todo' in the first line to be marked as to do lists:\r\n\r\n        if getline(1) =~? '^#\\?TODO\\>'\r\n            setfiletype todo\r\n        endif","5":"Quick install:\r\n\r\n    o Extract todo.vim under the syntax directory.\r\n    o Add the following to your .vimrc (or to ftdetect\/filetype.vim; sample filetype.vim is included)\r\n\r\n        au BufRead,BufNewFile *.todo setfiletype todo\r\n\r\nAny file of the form *.todo or any file whose filetype is set as 'todo' will now have syntax highlighting enabled. Read the comments in todo.vim and view the sample file sample.todo for details.\r\n\r\nOptional: Add the following to your .vimrc (or to scripts.vim file under the config directory; sample scripts.vim is included). This allows, in addition, for files starting with '#todo' in the first line to be marked as to do lists:\r\n\r\n        if getline(1) =~? '^#\\?TODO\\>'\r\n            setfiletype todo\r\n        endif","first_name":"Suresh","6":"Suresh","last_name":"Srinivasan","7":"Srinivasan","releases":[{"0":"1938","vim_version":"7.0","1":"7.0","script_version":"0.4","2":"0.4","version_comment":"Syntax coloring now works even if colorscheme is changed. Minor enhancements to date formats. See included README.txt for details.","3":"Syntax coloring now works even if colorscheme is changed. Minor enhancements to date formats. See included README.txt for details.","package":"todo_vimfiles.zip","4":"todo_vimfiles.zip","src_id":"19511","5":"19511","creation_date":"1360795590","6":"1360795590"},{"0":"1938","vim_version":"7.0","1":"7.0","script_version":"0.31","2":"0.31","version_comment":"Same as 0.3, but .zip'ed.","3":"Same as 0.3, but .zip'ed.","package":"todo_vimfiles.zip","4":"todo_vimfiles.zip","src_id":"7847","5":"7847","creation_date":"1193757829","6":"1193757829"},{"0":"1938","vim_version":"7.0","1":"7.0","script_version":"0.3","2":"0.3","version_comment":"Minor bug fixes.","3":"Minor bug fixes.","package":"todo_vimfiles.tar.gz","4":"todo_vimfiles.tar.gz","src_id":"7846","5":"7846","creation_date":"1193757787","6":"1193757787"},{"0":"1938","vim_version":"7.0","1":"7.0","script_version":"0.21","2":"0.21","version_comment":"Same as 0.2, but as a .zip instead of .gz","3":"Same as 0.2, but as a .zip instead of .gz","package":"todo_vimfiles.zip","4":"todo_vimfiles.zip","src_id":"7773","5":"7773","creation_date":"1192008852","6":"1192008852"}]},"1937":{"script_id":"1937","0":"1937","script_name":"Syntax for XUL","1":"Syntax for XUL","script_type":"syntax","2":"syntax","summary":"Highlighting for XML User interface Language.","3":"Highlighting for XML User interface Language.","description":"Syntax highlighting for the XML User interface Language (XUL) a.k.a. eXtensible User interface Language.  Based on Nicolai Nespor's xul.vim v0.5.  Follows XUL's reference at http:\/\/developer.mozilla.org\/en\/docs\/XUL_Reference.\r\n\r\nAlso available at http:\/\/bioinf.ibun.unal.edu.co\/~miguel\/?id=5","4":"Syntax highlighting for the XML User interface Language (XUL) a.k.a. eXtensible User interface Language.  Based on Nicolai Nespor's xul.vim v0.5.  Follows XUL's reference at http:\/\/developer.mozilla.org\/en\/docs\/XUL_Reference.\r\n\r\nAlso available at http:\/\/bioinf.ibun.unal.edu.co\/~miguel\/?id=5","install_details":"Just place file into syntax folder.  To tell vim detect *.xul files automatically, just put the following line into filetype.vim (into the vim configuration dir) before the XML line:\r\nau BufNewFile,BufRead *.xul  setf xul\r\nIf you want to disable the attributes syntax, put let nohl_xul_atts = 1 in your .\/[g]vim.\r\n<script\/> is not the better way, it's better <script><\/script>; but, if you want <script\/> form support, just place into your .\/[g]vim file: let xul_noclose_script = 1.  If you do so, it's possible to damage the <script><\/script> performance, in the case you use any \"\/\" char into the <script>, for example: <script type=\"application\/x-javascript\">.  It's up to you.","5":"Just place file into syntax folder.  To tell vim detect *.xul files automatically, just put the following line into filetype.vim (into the vim configuration dir) before the XML line:\r\nau BufNewFile,BufRead *.xul  setf xul\r\nIf you want to disable the attributes syntax, put let nohl_xul_atts = 1 in your .\/[g]vim.\r\n<script\/> is not the better way, it's better <script><\/script>; but, if you want <script\/> form support, just place into your .\/[g]vim file: let xul_noclose_script = 1.  If you do so, it's possible to damage the <script><\/script> performance, in the case you use any \"\/\" char into the <script>, for example: <script type=\"application\/x-javascript\">.  It's up to you.","first_name":"Miguel","6":"Miguel","last_name":"Rodriguez","7":"Rodriguez","releases":[{"0":"1937","vim_version":"7.0","1":"7.0","script_version":"0.35","2":"0.35","version_comment":"<script \/> form supported.  Identified and fixed some bugs.","3":"<script \/> form supported.  Identified and fixed some bugs.","package":"xul.vim","4":"xul.vim","src_id":"7456","5":"7456","creation_date":"1186379796","6":"1186379796"},{"0":"1937","vim_version":"7.0","1":"7.0","script_version":"0.2","2":"0.2","version_comment":"<script> tag completely highlighted","3":"<script> tag completely highlighted","package":"xul.vim","4":"xul.vim","src_id":"7332","5":"7332","creation_date":"1183887815","6":"1183887815"},{"0":"1937","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"xul.vim","4":"xul.vim","src_id":"7306","5":"7306","creation_date":"1183075707","6":"1183075707"}]},"1936":{"script_id":"1936","0":"1936","script_name":"OOP javascript indentation","1":"OOP javascript indentation","script_type":"indent","2":"indent","summary":"This indentation script for OOP javascript (especially for EXTJS)","3":"This indentation script for OOP javascript (especially for EXTJS)","description":"This indentation script for javascript \r\n\r\nexample of public method of class\r\n\r\nvar testing = function(){\r\n  return {\r\n    showDialog:new dialog([\r\n      {\r\n        1:'testing',\r\n        2:'coba',\r\n        3:'jajal'\r\n      }\r\n    ]);\r\n  }\r\n}\r\n\r\nComments are welcome! ryanthe@gmail.com","4":"This indentation script for javascript \r\n\r\nexample of public method of class\r\n\r\nvar testing = function(){\r\n  return {\r\n    showDialog:new dialog([\r\n      {\r\n        1:'testing',\r\n        2:'coba',\r\n        3:'jajal'\r\n      }\r\n    ]);\r\n  }\r\n}\r\n\r\nComments are welcome! ryanthe@gmail.com","install_details":"put at ~\/.vim\/indent","5":"put at ~\/.vim\/indent","first_name":"Ryan","6":"Ryan","last_name":"Fabella","7":"Fabella","releases":[{"0":"1936","vim_version":"6.0","1":"6.0","script_version":"0.1patch2","2":"0.1patch2","version_comment":"Former:\r\n\/**\r\n* This is a test\r\n*\/\r\nfoo();\r\n\r\nProper:\r\n\/**\r\n * This is a test\r\n *\/\r\nfoo();\r\n\r\n\r\npatch from Devin Weaver <suki@tritarget.org>","3":"Former:\r\n\/**\r\n* This is a test\r\n*\/\r\nfoo();\r\n\r\nProper:\r\n\/**\r\n * This is a test\r\n *\/\r\nfoo();\r\n\r\n\r\npatch from Devin Weaver <suki@tritarget.org>","package":"javascript.vim","4":"javascript.vim","src_id":"7708","5":"7708","creation_date":"1190676818","6":"1190676818"},{"0":"1936","vim_version":"6.0","1":"6.0","script_version":"0.1patch1","2":"0.1patch1","version_comment":"thanks to drdr.xp@gmail.com \r\npatch on case \r\nvar o = {}; \r\n","3":"thanks to drdr.xp@gmail.com \r\npatch on case \r\nvar o = {}; \r\n","package":"javascript.vim","4":"javascript.vim","src_id":"7394","5":"7394","creation_date":"1185146775","6":"1185146775"},{"0":"1936","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"javascript.vim","4":"javascript.vim","src_id":"7286","5":"7286","creation_date":"1182478975","6":"1182478975"}]},"1935":{"script_id":"1935","0":"1935","script_name":"rectcut","1":"rectcut","script_type":"utility","2":"utility","summary":"Rectangle Copy","3":"Rectangle Copy","description":"After installation\r\n\r\n Run Command \r\n\r\n:Cut 1 1 3 4    => Copies from Col 1 Row 1 to Col 3 and Row 4 \r\n:Pas 1            => Paste every thing at end of line number 1","4":"After installation\r\n\r\n Run Command \r\n\r\n:Cut 1 1 3 4    => Copies from Col 1 Row 1 to Col 3 and Row 4 \r\n:Pas 1            => Paste every thing at end of line number 1","install_details":"Just drop it in plugin directory","5":"Just drop it in plugin directory","first_name":"vijayandra","6":"vijayandra","last_name":"singh","7":"singh","releases":[{"0":"1935","vim_version":"6.0","1":"6.0","script_version":"1.02","2":"1.02","version_comment":"Added help, \r\n\r\n:Cut <StartLine> <StartCol> <EndLine> <EndCol>","3":"Added help, \r\n\r\n:Cut <StartLine> <StartCol> <EndLine> <EndCol>","package":"rectcut.vim","4":"rectcut.vim","src_id":"7289","5":"7289","creation_date":"1182511159","6":"1182511159"}]},"1934":{"script_id":"1934","0":"1934","script_name":"git-commit","1":"git-commit","script_type":"ftplugin","2":"ftplugin","summary":"see your commit diff with git","3":"see your commit diff with git","description":"this ftplugin (and syntax file) brings you the ability to see the diffs of the commit you are commenting at the same time, a bit like svn-commit does.","4":"this ftplugin (and syntax file) brings you the ability to see the diffs of the commit you are commenting at the same time, a bit like svn-commit does.","install_details":"unpack the tar in your $HOME and add:\r\n\r\n  au BufRead,BufNewFile COMMIT_EDITMSG     setf git \r\n\r\ninto your .vim\/filetype.vim","5":"unpack the tar in your $HOME and add:\r\n\r\n  au BufRead,BufNewFile COMMIT_EDITMSG     setf git \r\n\r\ninto your .vim\/filetype.vim","first_name":"Pierre","6":"Pierre","last_name":"Habouzit","7":"Habouzit","releases":[{"0":"1934","vim_version":"7.0","1":"7.0","script_version":"0.2","2":"0.2","version_comment":"use GIT_INDEX_FILE and git diff --stat -p --cached…\r\n\r\nthanks a lot to Junio and Jan Hudec for the tip…","3":"use GIT_INDEX_FILE and git diff --stat -p --cached…\r\n\r\nthanks a lot to Junio and Jan Hudec for the tip…","package":"git.tar","4":"git.tar","src_id":"7990","5":"7990","creation_date":"1196039968","6":"1196039968"},{"0":"1934","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"git.tar","4":"git.tar","src_id":"7279","5":"7279","creation_date":"1182414918","6":"1182414918"}]},"1933":{"script_id":"1933","0":"1933","script_name":"html_french","1":"html_french","script_type":"ftplugin","2":"ftplugin","summary":"view html entities as accented characters for French","3":"view html entities as accented characters for French","description":"When loading a html file, this plugin replaces all HTML-coded French characters (like & eacute ;) with the normal representation (\u00c3\u00a9), like so many other scripts: html_umlaute(vimscript#907), html_portuguese(vimscript#924), html_danish (vimscript#1163).  I specifically ripped off html_danish, thank you Sune Vuroela.\r\n","4":"When loading a html file, this plugin replaces all HTML-coded French characters (like & eacute ;) with the normal representation (\u00c3\u00a9), like so many other scripts: html_umlaute(vimscript#907), html_portuguese(vimscript#924), html_danish (vimscript#1163).  I specifically ripped off html_danish, thank you Sune Vuroela.\r\n","install_details":"put into your plugin directory.","5":"put into your plugin directory.","first_name":"Roger","6":"Roger","last_name":"Pilkey","7":"Pilkey","releases":[{"0":"1933","vim_version":"6.0","1":"6.0","script_version":"1.3","2":"1.3","version_comment":"adding \u00c3\u00b9","3":"adding \u00c3\u00b9","package":"html_fr.vim","4":"html_fr.vim","src_id":"7983","5":"7983","creation_date":"1195718854","6":"1195718854"},{"0":"1933","vim_version":"6.0","1":"6.0","script_version":"1.2","2":"1.2","version_comment":"add « and »","3":"add « and »","package":"html_fr.vim","4":"html_fr.vim","src_id":"7707","5":"7707","creation_date":"1190610319","6":"1190610319"},{"0":"1933","vim_version":"6.0","1":"6.0","script_version":"1.1","2":"1.1","version_comment":"forgot î (& icirc ;)  doh.","3":"forgot î (& icirc ;)  doh.","package":"html_fr.vim","4":"html_fr.vim","src_id":"7340","5":"7340","creation_date":"1184152141","6":"1184152141"},{"0":"1933","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"html_fr.vim","4":"html_fr.vim","src_id":"7277","5":"7277","creation_date":"1182405411","6":"1182405411"}]},"1932":{"script_id":"1932","0":"1932","script_name":"visSum.vim","1":"visSum.vim","script_type":"utility","2":"utility","summary":"Computes sum of selected numbers","3":"Computes sum of selected numbers","description":"It is something so trivial, I can't believe it hasn't been done before.\r\nAfter looking for an hour I couldn't find a plugin to do this without relying on external programs, so here is my offering, 100% pure vimscript.\r\n\r\nHighlight some lines containing numbers, and use <Leader>su (usually that's \\su) and the sum appears in the message line.  \r\n\r\nIt works by grepping each line of your selection for the first number it sees, and adds that to the running total.\r\n\r\nVisual Block support added in version 0.2.\r\n\r\nFeedback to g?? ArjBsnyFbCe@tzNnvZy.pbz - NOSPAM\r\n","4":"It is something so trivial, I can't believe it hasn't been done before.\r\nAfter looking for an hour I couldn't find a plugin to do this without relying on external programs, so here is my offering, 100% pure vimscript.\r\n\r\nHighlight some lines containing numbers, and use <Leader>su (usually that's \\su) and the sum appears in the message line.  \r\n\r\nIt works by grepping each line of your selection for the first number it sees, and adds that to the running total.\r\n\r\nVisual Block support added in version 0.2.\r\n\r\nFeedback to g?? ArjBsnyFbCe@tzNnvZy.pbz - NOSPAM\r\n","install_details":"Drop visSum.vim into your ~\/.vim\/plugin directory.","5":"Drop visSum.vim into your ~\/.vim\/plugin directory.","first_name":"erik","6":"erik","last_name":"falor","7":"falor","releases":[{"0":"1932","vim_version":"7.0","1":"7.0","script_version":"1.2","2":"1.2","version_comment":"This version (1.2) contains a fix for a bug reported by Fabio Inguaggiato.\r\nThanks, Fabio!","3":"This version (1.2) contains a fix for a bug reported by Fabio Inguaggiato.\r\nThanks, Fabio!","package":"visSum.vim","4":"visSum.vim","src_id":"23522","5":"23522","creation_date":"1439955382","6":"1439955382"},{"0":"1932","vim_version":"7.0","1":"7.0","script_version":"1.1","2":"1.1","version_comment":"Fixes a bug discovered by Markus Weimar.","3":"Fixes a bug discovered by Markus Weimar.","package":"visSum.vim","4":"visSum.vim","src_id":"23399","5":"23399","creation_date":"1434556301","6":"1434556301"},{"0":"1932","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"After nearly five years, I've finally updated this plugin to support floating-point numbers.\r\nI couldn't have done it without the patch submitted by Christian Mauderer.  Thanks, Christian!\r\n\r\nThe plugin will work equally well whether or not your Vim supports the +float feature; if you don't have +float the old behavior is retained.  If you sum a column of numbers and the fractional part is insignificant, an integer is returned.  I went out of may way to make that happen.  If you don't like it, please let me know and I'll change it.  For what I perceive to be the most common use-case, this shouldn't be problematic.\r\n\r\nVim can also represent floats in scientific notation: presently this is unsupported.  If you'd like this feature, I'd recommend following Christian's lead and submitting a patch.","3":"After nearly five years, I've finally updated this plugin to support floating-point numbers.\r\nI couldn't have done it without the patch submitted by Christian Mauderer.  Thanks, Christian!\r\n\r\nThe plugin will work equally well whether or not your Vim supports the +float feature; if you don't have +float the old behavior is retained.  If you sum a column of numbers and the fractional part is insignificant, an integer is returned.  I went out of may way to make that happen.  If you don't like it, please let me know and I'll change it.  For what I perceive to be the most common use-case, this shouldn't be problematic.\r\n\r\nVim can also represent floats in scientific notation: presently this is unsupported.  If you'd like this feature, I'd recommend following Christian's lead and submitting a patch.","package":"visSum.vim","4":"visSum.vim","src_id":"18281","5":"18281","creation_date":"1342588595","6":"1342588595"},{"0":"1932","vim_version":"7.0","1":"7.0","script_version":"0.3","2":"0.3","version_comment":"Stores sum in buffer variable b:sum.\r\n:VisSum command can take a register name as an argument to store the sum.","3":"Stores sum in buffer variable b:sum.\r\n:VisSum command can take a register name as an argument to store the sum.","package":"visSum.vim","4":"visSum.vim","src_id":"7856","5":"7856","creation_date":"1193926539","6":"1193926539"}]},"1931":{"script_id":"1931","0":"1931","script_name":"svndiff.vim","1":"svndiff.vim","script_type":"utility","2":"utility","summary":"vim plugin to for visual display of svn diffs in two vim windows","3":"vim plugin to for visual display of svn diffs in two vim windows","description":"1) used as vim command, format :D [v] [version #]\r\n   :D h    \r\n      -- diff between opened file and lastest svn version, horizontal split\r\n   :D      \r\n      -- diff between opened file and lastest svn version, vertical split\r\n   :D h <version #>  example  :D 1.2\r\n      -- diff between opened file and svn version #, horizontal split\r\n   :D <version #>  example  :D v 1.2\r\n      -- diff between opened file and svn version #, vertical split\r\n2) map to key \r\n   can create key mapping by adding the following lines in ~\/.vimrc, example\r\n   a. map <F8> <Plug>D\r\n        -- press F8 in vim, show diff to svn last version, horizontal split\r\n   b. map <F7> <Plug>Dh\r\n        -- press F7 in vim, show diff to svn last version, vertical split\r\n3) return from diff mode to normal mode\r\n   :set nodiff\r\n\r\nexample:\r\n  a) open a file in vim\r\n  b) use vim command line, :D <enter> to see two windows with diffs\r\n  c) :close to close tmp window\r\n  d) :set nodiff to expand the compressed view, or press a on '+' sign to expand \r\n\r\nversion updates:\r\n0.2 -- merged Tom Ziomek's fix","4":"1) used as vim command, format :D [v] [version #]\r\n   :D h    \r\n      -- diff between opened file and lastest svn version, horizontal split\r\n   :D      \r\n      -- diff between opened file and lastest svn version, vertical split\r\n   :D h <version #>  example  :D 1.2\r\n      -- diff between opened file and svn version #, horizontal split\r\n   :D <version #>  example  :D v 1.2\r\n      -- diff between opened file and svn version #, vertical split\r\n2) map to key \r\n   can create key mapping by adding the following lines in ~\/.vimrc, example\r\n   a. map <F8> <Plug>D\r\n        -- press F8 in vim, show diff to svn last version, horizontal split\r\n   b. map <F7> <Plug>Dh\r\n        -- press F7 in vim, show diff to svn last version, vertical split\r\n3) return from diff mode to normal mode\r\n   :set nodiff\r\n\r\nexample:\r\n  a) open a file in vim\r\n  b) use vim command line, :D <enter> to see two windows with diffs\r\n  c) :close to close tmp window\r\n  d) :set nodiff to expand the compressed view, or press a on '+' sign to expand \r\n\r\nversion updates:\r\n0.2 -- merged Tom Ziomek's fix","install_details":"copy this file to your vim plugin directory, normally ~\/.vim\/plugin\r\nif not, can manally source this file in vim or add into ~\/.vimrc\r\n:source svndiff.vim\r\n","5":"copy this file to your vim plugin directory, normally ~\/.vim\/plugin\r\nif not, can manally source this file in vim or add into ~\/.vimrc\r\n:source svndiff.vim\r\n","first_name":"Eric","6":"Eric","last_name":"Ji","7":"Ji","releases":[{"0":"1931","vim_version":"6.0","1":"6.0","script_version":"0.2","2":"0.2","version_comment":"Merged the patch from T Ziomek (t_ziomek@yahoo.com), to fix a bug when -v is used.","3":"Merged the patch from T Ziomek (t_ziomek@yahoo.com), to fix a bug when -v is used.","package":"svndiff.vim","4":"svndiff.vim","src_id":"9050","5":"9050","creation_date":"1217443722","6":"1217443722"},{"0":"1931","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"svndiff.vim","4":"svndiff.vim","src_id":"7274","5":"7274","creation_date":"1182365633","6":"1182365633"}]},"1930":{"script_id":"1930","0":"1930","script_name":"maxscript.vim","1":"maxscript.vim","script_type":"syntax","2":"syntax","summary":"Syntax highlighting for MAXScript 8.0","3":"Syntax highlighting for MAXScript 8.0","description":"This file will provide basic highlighting for MAXScript release 8.0. Comments, keywords, numbers, and strings are currently highlighted.","4":"This file will provide basic highlighting for MAXScript release 8.0. Comments, keywords, numbers, and strings are currently highlighted.","install_details":"Save in vimfiles\/syntax or in .vim\/syntax, depending on platform.\r\n\r\nWrite the following to ftdetect\/maxscript.vim:\r\n\r\n    augroup filetypedetect\r\n    au! BufRead,BufNewFile *.ms\t\tsetf maxscript\r\n    augroup END\r\n\r\nYou can also add *.mse, *.mcr, *.mzp, *.ds if you use those names.","5":"Save in vimfiles\/syntax or in .vim\/syntax, depending on platform.\r\n\r\nWrite the following to ftdetect\/maxscript.vim:\r\n\r\n    augroup filetypedetect\r\n    au! BufRead,BufNewFile *.ms\t\tsetf maxscript\r\n    augroup END\r\n\r\nYou can also add *.mse, *.mcr, *.mzp, *.ds if you use those names.","first_name":"Josh","6":"Josh","last_name":"Lee","7":"Lee","releases":[{"0":"1930","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"maxscript.vim","4":"maxscript.vim","src_id":"7268","5":"7268","creation_date":"1182324580","6":"1182324580"}]},"1929":{"script_id":"1929","0":"1929","script_name":"DBGp client","1":"DBGp client","script_type":"utility","2":"utility","summary":"a remote debugger interface to the DBGp protocol (tested only with XDebug\/PHP)","3":"a remote debugger interface to the DBGp protocol (tested only with XDebug\/PHP)","description":"PLEASE NOTE: This script has only been tested with XDebug for PHP debugging. But it may work with other debuggers. If you would like to contribute any patches which would add support for other debuggers, please contact me at sam at box dot net.\r\n\r\nALSO PLEASE NOTE: The original script was written by Seung Woo Shin, located at http:\/\/www.vim.org\/scripts\/script.php?script_id=1152. This is a slightly modified version of that script with a few additional capabilities. If anyone would like to contribute any patches to this script, feel free to submit diffs or contact me at sam at box dot net.","4":"PLEASE NOTE: This script has only been tested with XDebug for PHP debugging. But it may work with other debuggers. If you would like to contribute any patches which would add support for other debuggers, please contact me at sam at box dot net.\r\n\r\nALSO PLEASE NOTE: The original script was written by Seung Woo Shin, located at http:\/\/www.vim.org\/scripts\/script.php?script_id=1152. This is a slightly modified version of that script with a few additional capabilities. If anyone would like to contribute any patches to this script, feel free to submit diffs or contact me at sam at box dot net.","install_details":"For a tutorial on how to use this plugin, please visit http:\/\/tech.blog.box.net\/2007\/06\/20\/how-to-debug-php-with-vim-and-xdebug-on-linux\/ .","5":"For a tutorial on how to use this plugin, please visit http:\/\/tech.blog.box.net\/2007\/06\/20\/how-to-debug-php-with-vim-and-xdebug-on-linux\/ .","first_name":"Sam","6":"Sam","last_name":"Ghods","7":"Ghods","releases":[{"0":"1929","vim_version":"6.0","1":"6.0","script_version":"1.1.1","2":"1.1.1","version_comment":"Added a check so the script doesn't load if python is not compiled in. (Contributed by Lars Becker.)","3":"Added a check so the script doesn't load if python is not compiled in. (Contributed by Lars Becker.)","package":"debugger.zip","4":"debugger.zip","src_id":"7285","5":"7285","creation_date":"1182439904","6":"1182439904"},{"0":"1929","vim_version":"6.0","1":"6.0","script_version":"1.1","2":"1.1","version_comment":"Initial upload","3":"Initial upload","package":"debugger.zip","4":"debugger.zip","src_id":"7267","5":"7267","creation_date":"1182277718","6":"1182277718"}]},"1928":{"script_id":"1928","0":"1928","script_name":"Rename","1":"Rename","script_type":"utility","2":"utility","summary":"Rename a buffer within Vim and on disk","3":"Rename a buffer within Vim and on disk","description":"A command and function that basically does a \":saveas <newfile>\" then removes the old filename on the disk.\r\n","4":"A command and function that basically does a \":saveas <newfile>\" then removes the old filename on the disk.\r\n","install_details":"Either :source it or put it in your plugin directory.","5":"Either :source it or put it in your plugin directory.","first_name":"Christian J.","6":"Christian J.","last_name":"Robinson","7":"Robinson","releases":[{"0":"1928","vim_version":"9.0","1":"9.0","script_version":"0.5","2":"0.5","version_comment":"- Update for Vim 9 (no new features)","3":"- Update for Vim 9 (no new features)","package":"Rename.vim","4":"Rename.vim","src_id":"28143","5":"28143","creation_date":"1661156372","6":"1661156372"},{"0":"1928","vim_version":"7.2","1":"7.2","script_version":"0.4","2":"0.4","version_comment":"Minor tweaks","3":"Minor tweaks","package":"Rename.vim","4":"Rename.vim","src_id":"27655","5":"27655","creation_date":"1626432991","6":"1626432991"},{"0":"1928","vim_version":"7.2","1":"7.2","script_version":"0.3","2":"0.3","version_comment":"- Multi-byte characters in the destination filename could cause issues","3":"- Multi-byte characters in the destination filename could cause issues","package":"Rename.vim","4":"Rename.vim","src_id":"16331","5":"16331","creation_date":"1314081957","6":"1314081957"},{"0":"1928","vim_version":"7.0","1":"7.0","script_version":"0.2","2":"0.2","version_comment":"- Minor correction in the :command definition to resolve issues with Windows style paths","3":"- Minor correction in the :command definition to resolve issues with Windows style paths","package":"Rename.vim","4":"Rename.vim","src_id":"16282","5":"16282","creation_date":"1313525492","6":"1313525492"},{"0":"1928","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"Rename.vim","4":"Rename.vim","src_id":"7262","5":"7262","creation_date":"1182209863","6":"1182209863"}]},"1927":{"script_id":"1927","0":"1927","script_name":"syntax\/algol68.vim","1":"syntax\/algol68.vim","script_type":"syntax","2":"syntax","summary":"Syntax for Algol68","3":"Syntax for Algol68","description":"First version... looking for ideas.\r\n\r\nAlternate download location: http:\/\/3ttechnology.com\/vim\/syntax\/algol68.vim\r\n\r\nCurrently does fully handle unicode\/htm4 characters, eg &divide; for \u00c3\u00b7 AND &perp; for ⊥\r\n\r\nTargeted toward the ALGOL-68G version from:\r\nhttp:\/\/www.xs4all.nl\/~jmvdveer\/algol.html#obtaining\r\nAnd includes extensions.\r\n\r\nHas SOME reserved words\/extensions from ALGOL-68R and ALGOL-68C\r\n\r\nCurrently cannot parse code with BOLDED HTML.\r\n\r\nSome pascal syntax remains.","4":"First version... looking for ideas.\r\n\r\nAlternate download location: http:\/\/3ttechnology.com\/vim\/syntax\/algol68.vim\r\n\r\nCurrently does fully handle unicode\/htm4 characters, eg &divide; for \u00c3\u00b7 AND &perp; for ⊥\r\n\r\nTargeted toward the ALGOL-68G version from:\r\nhttp:\/\/www.xs4all.nl\/~jmvdveer\/algol.html#obtaining\r\nAnd includes extensions.\r\n\r\nHas SOME reserved words\/extensions from ALGOL-68R and ALGOL-68C\r\n\r\nCurrently cannot parse code with BOLDED HTML.\r\n\r\nSome pascal syntax remains.","install_details":"copy algol68.vim to \/usr\/share\/vim\/vim64\/syntax\/ directory - ($VIMRUNTIME\/syntax directory)\r\n\r\nUpdate the following files:\r\n\r\n1. \/usr\/share\/vim\/vim64\/filetype.vim:\r\n \" Algol68 (also *.a68)\r\nau BufNewFile,BufRead *.a68                   setf algol68\r\n\r\n2. \/usr\/share\/vim\/vim64\/synmenu.vim:\r\nan 50.80.135 &Syntax.PQ.Algol68 :cal SetSyn(\"algol68\")<CR>\r\n","5":"copy algol68.vim to \/usr\/share\/vim\/vim64\/syntax\/ directory - ($VIMRUNTIME\/syntax directory)\r\n\r\nUpdate the following files:\r\n\r\n1. \/usr\/share\/vim\/vim64\/filetype.vim:\r\n \" Algol68 (also *.a68)\r\nau BufNewFile,BufRead *.a68                   setf algol68\r\n\r\n2. \/usr\/share\/vim\/vim64\/synmenu.vim:\r\nan 50.80.135 &Syntax.PQ.Algol68 :cal SetSyn(\"algol68\")<CR>\r\n","first_name":"Neville","6":"Neville","last_name":"Dempsey","7":"Dempsey","releases":[{"0":"1927","vim_version":"7.0","1":"7.0","script_version":"0.2","2":"0.2","version_comment":"Added missing ''stand in'', ''stand out'' etc. ''proc''edures and support for the unicode decimal exponent symbol '''⏨'''","3":"Added missing ''stand in'', ''stand out'' etc. ''proc''edures and support for the unicode decimal exponent symbol '''⏨'''","package":"algol68.vim","4":"algol68.vim","src_id":"13926","5":"13926","creation_date":"1285539094","6":"1285539094"},{"0":"1927","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"algol68.vim","4":"algol68.vim","src_id":"7260","5":"7260","creation_date":"1182207510","6":"1182207510"}]},"1926":{"script_id":"1926","0":"1926","script_name":"bbs.vim","1":"bbs.vim","script_type":"syntax","2":"syntax","summary":"Syntax highlighting plugin for SMTH BBS","3":"Syntax highlighting plugin for SMTH BBS","description":"This is a simple syntax highlighting plugin for SMTH BBS. If you didn't know what is SMTH, this plugin has no use to you so just ignore it. :-)","4":"This is a simple syntax highlighting plugin for SMTH BBS. If you didn't know what is SMTH, this plugin has no use to you so just ignore it. :-)","install_details":"This plugin is compressed in VimBall format. So you may need to install the latest version of vimscript #1502 first.\r\n\r\nThen the only thing you should do is just downloading the Vimball, opening it in Vim and typing this command followed by an enter in your Vim:\r\n\r\n:so %","5":"This plugin is compressed in VimBall format. So you may need to install the latest version of vimscript #1502 first.\r\n\r\nThen the only thing you should do is just downloading the Vimball, opening it in Vim and typing this command followed by an enter in your Vim:\r\n\r\n:so %","first_name":"Edward","6":"Edward","last_name":"Fox","7":"Fox","releases":[{"0":"1926","vim_version":"7.0","1":"7.0","script_version":"0.92","2":"0.92","version_comment":"* Added foldexpr to make it easier to read and reply messages.","3":"* Added foldexpr to make it easier to read and reply messages.","package":"bbs.vba.gz","4":"bbs.vba.gz","src_id":"9111","5":"9111","creation_date":"1218486889","6":"1218486889"},{"0":"1926","vim_version":"6.0","1":"6.0","script_version":"0.91","2":"0.91","version_comment":"* Removed unused syntax for E-mail.\r\n\r\n* Declared the script encoding as utf-8 explicitly.\r\n","3":"* Removed unused syntax for E-mail.\r\n\r\n* Declared the script encoding as utf-8 explicitly.\r\n","package":"bbs.vba.gz","4":"bbs.vba.gz","src_id":"7266","5":"7266","creation_date":"1182273460","6":"1182273460"},{"0":"1926","vim_version":"6.0","1":"6.0","script_version":"0.9","2":"0.9","version_comment":"Initial upload","3":"Initial upload","package":"bbs.vba.gz","4":"bbs.vba.gz","src_id":"7258","5":"7258","creation_date":"1182159986","6":"1182159986"}]},"1925":{"script_id":"1925","0":"1925","script_name":"context complier plugin","1":"context complier plugin","script_type":"utility","2":"utility","summary":"complier for context","3":"complier for context","description":"This complier plugin sets up texexec with appropriate options as the make program. To use this do\r\n\r\n:compiler texexec\r\n:make <options> <filename>\r\n\r\nwhere <options> are additional options that you want to pass to texexec. If you always want to use this compiler with context files, add \r\n\r\ncompiler texexec\r\n\r\nin your .vim\/ftplugin\/context.vim file.","4":"This complier plugin sets up texexec with appropriate options as the make program. To use this do\r\n\r\n:compiler texexec\r\n:make <options> <filename>\r\n\r\nwhere <options> are additional options that you want to pass to texexec. If you always want to use this compiler with context files, add \r\n\r\ncompiler texexec\r\n\r\nin your .vim\/ftplugin\/context.vim file.","install_details":"Store the texexec.vim file in your .vim\/complier directory (Unix) or vimfiles\/compiler directory (Windows).","5":"Store the texexec.vim file in your .vim\/complier directory (Unix) or vimfiles\/compiler directory (Windows).","first_name":"Aditya","6":"Aditya","last_name":"Mahajan","7":"Mahajan","releases":[{"0":"1925","vim_version":"5.7","1":"5.7","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"texexec.vim","4":"texexec.vim","src_id":"7255","5":"7255","creation_date":"1182101862","6":"1182101862"}]},"1924":{"script_id":"1924","0":"1924","script_name":"omniperl","1":"omniperl","script_type":"ftplugin","2":"ftplugin","summary":"omnicompletion for the perl language","3":"omnicompletion for the perl language","description":"\r\nNote : This script is a bit buggy and wrong in the details.\r\nIt needs a more theoretical sound basis, rework or maybe a different approach.\r\n\r\n","4":"\r\nNote : This script is a bit buggy and wrong in the details.\r\nIt needs a more theoretical sound basis, rework or maybe a different approach.\r\n\r\n","install_details":"1. unzip omniperl.zip\r\n2. vim omniperl.vba\r\n3. :so %\r\n ","5":"1. unzip omniperl.zip\r\n2. vim omniperl.vba\r\n3. :so %\r\n ","first_name":"Andreas","6":"Andreas","last_name":"Politz","7":"Politz","releases":[{"0":"1924","vim_version":"7.0","1":"7.0","script_version":"v1.1","2":"v1.1","version_comment":"- fixed a bug that would lead to the \"Red screen of death\"\r\n  , and some other minor ones\r\n- g:OmniPerl_Modulelist_File is now globed\r\n- fixed the helpfile \r\n    * removed global 'isf' from modeline \r\n    * added uninstall informations\r\n    * fixed tags\r\n- plugin is now zipped, because it is more common \r\n","3":"- fixed a bug that would lead to the \"Red screen of death\"\r\n  , and some other minor ones\r\n- g:OmniPerl_Modulelist_File is now globed\r\n- fixed the helpfile \r\n    * removed global 'isf' from modeline \r\n    * added uninstall informations\r\n    * fixed tags\r\n- plugin is now zipped, because it is more common \r\n","package":"omniperl.zip","4":"omniperl.zip","src_id":"7254","5":"7254","creation_date":"1182052792","6":"1182052792"}]},"1923":{"script_id":"1923","0":"1923","script_name":"vpp.vim","1":"vpp.vim","script_type":"syntax","2":"syntax","summary":"Syntax file for VDM++","3":"Syntax file for VDM++","description":"This script provides syntax highlight for VDM++ specification language. \r\n\r\nDownload at https:\/\/rcgoncalves.pt\/files\/vpp.zip","4":"This script provides syntax highlight for VDM++ specification language. \r\n\r\nDownload at https:\/\/rcgoncalves.pt\/files\/vpp.zip","install_details":"Put vpp.vim in your syntax diretory (e.g. ~\/.vim\/syntax). \r\nAdd line below to your .vimrc file: \r\nau BufNewFile,BufRead *.vpp     setf vpp","5":"Put vpp.vim in your syntax diretory (e.g. ~\/.vim\/syntax). \r\nAdd line below to your .vimrc file: \r\nau BufNewFile,BufRead *.vpp     setf vpp","first_name":"Rui Carlos","6":"Rui Carlos","last_name":"Gon\u00c3\u00a7alves","7":"Gon\u00c3\u00a7alves","releases":[{"0":"1923","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Multiple errors fixed.","3":"Multiple errors fixed.","package":"vpp.vim","4":"vpp.vim","src_id":"16589","5":"16589","creation_date":"1317054340","6":"1317054340"},{"0":"1923","vim_version":"7.0","1":"7.0","script_version":"0.10","2":"0.10","version_comment":"Error correction (exits  -->  exists).","3":"Error correction (exits  -->  exists).","package":"vpp.vim","4":"vpp.vim","src_id":"7318","5":"7318","creation_date":"1183446448","6":"1183446448"},{"0":"1923","vim_version":"7.0","1":"7.0","script_version":"0.9","2":"0.9","version_comment":"Initial upload","3":"Initial upload","package":"vpp.vim","4":"vpp.vim","src_id":"7243","5":"7243","creation_date":"1181753281","6":"1181753281"}]},"1922":{"script_id":"1922","0":"1922","script_name":"ChocolatePapaya","1":"ChocolatePapaya","script_type":"color scheme","2":"color scheme","summary":"low contrast scheme, light or dark","3":"low contrast scheme, light or dark","description":"This is a unified light\/dark version of PapayaWhip (vimscript #591) and ChocolateLiquor (vimscript #592). Both are pretty easy on the eyes, and feature the colors PapayaWhip and one I call ChocolateLiquor (aka #3F1F1F).\r\n\r\nScreenshots:\r\n\r\nLight Version: http:\/\/home.ptd.net\/~gwilliam\/vim\/PapayaWhip.png\r\nDark Version: http:\/\/home.ptd.net\/~gwilliam\/vim\/ChocolateLiquor.png","4":"This is a unified light\/dark version of PapayaWhip (vimscript #591) and ChocolateLiquor (vimscript #592). Both are pretty easy on the eyes, and feature the colors PapayaWhip and one I call ChocolateLiquor (aka #3F1F1F).\r\n\r\nScreenshots:\r\n\r\nLight Version: http:\/\/home.ptd.net\/~gwilliam\/vim\/PapayaWhip.png\r\nDark Version: http:\/\/home.ptd.net\/~gwilliam\/vim\/ChocolateLiquor.png","install_details":"Copy to $HOME\/.vim\/colors or $VIM\/vimfiles\/colors\r\n:colorscheme ChocolatePapaya","5":"Copy to $HOME\/.vim\/colors or $VIM\/vimfiles\/colors\r\n:colorscheme ChocolatePapaya","first_name":"Gerald","6":"Gerald","last_name":"Williams","7":"Williams","releases":[{"0":"1922","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"ChocolatePapaya.vim","4":"ChocolatePapaya.vim","src_id":"7237","5":"7237","creation_date":"1181713845","6":"1181713845"}]},"1921":{"script_id":"1921","0":"1921","script_name":"javalog.vim","1":"javalog.vim","script_type":"syntax","2":"syntax","summary":"syntax highlighting for default java.util.logging output","3":"syntax highlighting for default java.util.logging output","description":"Syntax highlighting appropriate for log files written by java.util.logging default FileHandler settings.","4":"Syntax highlighting appropriate for log files written by java.util.logging default FileHandler settings.","install_details":"Drop in vimfiles\/syntax or other appropriate directory where vim will find syntax files.  \r\n\r\nTo use once, \":set syn=javalog\".  See \":help filetype\" to associate this syntax file with a filename pattern.","5":"Drop in vimfiles\/syntax or other appropriate directory where vim will find syntax files.  \r\n\r\nTo use once, \":set syn=javalog\".  See \":help filetype\" to associate this syntax file with a filename pattern.","first_name":"Rich","6":"Rich","last_name":"Davies","7":"Davies","releases":[{"0":"1921","vim_version":"7.0","1":"7.0","script_version":"7.0","2":"7.0","version_comment":"Initial upload","3":"Initial upload","package":"javalog.vim","4":"javalog.vim","src_id":"7230","5":"7230","creation_date":"1181653170","6":"1181653170"}]},"1920":{"script_id":"1920","0":"1920","script_name":"cvsps syntax","1":"cvsps syntax","script_type":"syntax","2":"syntax","summary":"Syntax highlight for cvsps files","3":"Syntax highlight for cvsps files","description":"It lacks a detector, the user must manually \":set ft=cvsps\", make a ftdetect based on filename or put \"vim: ft=cvsps\" in the file.","4":"It lacks a detector, the user must manually \":set ft=cvsps\", make a ftdetect based on filename or put \"vim: ft=cvsps\" in the file.","install_details":"Just put it in ~\/.vim\/syntax.","5":"Just put it in ~\/.vim\/syntax.","first_name":"Leandro","6":"Leandro","last_name":"Penz","7":"Penz","releases":[{"0":"1920","vim_version":"6.0","1":"6.0","script_version":"1","2":"1","version_comment":"Initial upload","3":"Initial upload","package":"cvsps.vim","4":"cvsps.vim","src_id":"7224","5":"7224","creation_date":"1181389761","6":"1181389761"}]},"1919":{"script_id":"1919","0":"1919","script_name":"clibs.vim","1":"clibs.vim","script_type":"syntax","2":"syntax","summary":"Syntax highlighting for C library functions and constants","3":"Syntax highlighting for C library functions and constants","description":"This is a fork of the default c.vim syntax file that provides highlighting of C library functions and constants.\r\n\r\nThe patch to c.vim is very minor (just add one container class for library functions \/ constants), so your usual syntax highlighting in C will be preserved.\r\n\r\nIt contains options that let you control how much, and which libraries you want highlighted.\r\n\r\nCurrently, the only libraries supported are \"glibc\" and \"xlib\". But it comes with instructions on how to add your own (project specific, or other) libraries. Feel free to add support for other standard libraries and send them to me :).","4":"This is a fork of the default c.vim syntax file that provides highlighting of C library functions and constants.\r\n\r\nThe patch to c.vim is very minor (just add one container class for library functions \/ constants), so your usual syntax highlighting in C will be preserved.\r\n\r\nIt contains options that let you control how much, and which libraries you want highlighted.\r\n\r\nCurrently, the only libraries supported are \"glibc\" and \"xlib\". But it comes with instructions on how to add your own (project specific, or other) libraries. Feel free to add support for other standard libraries and send them to me :).","install_details":"To install script and help files\r\n\r\n    cd ~\/.vim && tar -xjvf \/tmp\/clibs.vim && vim +\":helptags doc\/\" +:q\r\n\r\nand put\r\n\r\n    let c_hi_identifiers\t= 'all'\r\n    let c_hi_libs\t\t= ['*']\r\n\r\nin ~\/.vimrc. For complete help do\r\n\r\n    :help clibs\r\n","5":"To install script and help files\r\n\r\n    cd ~\/.vim && tar -xjvf \/tmp\/clibs.vim && vim +\":helptags doc\/\" +:q\r\n\r\nand put\r\n\r\n    let c_hi_identifiers\t= 'all'\r\n    let c_hi_libs\t\t= ['*']\r\n\r\nin ~\/.vimrc. For complete help do\r\n\r\n    :help clibs\r\n","first_name":"gi1242","6":"gi1242","last_name":"gi1242","7":"gi1242","releases":[{"0":"1919","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"clibs.tbz2","4":"clibs.tbz2","src_id":"7222","5":"7222","creation_date":"1181333052","6":"1181333052"}]},"1918":{"script_id":"1918","0":"1918","script_name":"Scheme Mode","1":"Scheme Mode","script_type":"ftplugin","2":"ftplugin","summary":"As many useful commands and functions for Scheme as possible","3":"As many useful commands and functions for Scheme as possible","description":"\" This is a simple fileplugin supposed to help you write Scheme code fast.\n\" Comes with shortcuts for usual patterns such as `if`, `cond`, `case`, as\n\" well as `let`s (normal, letrec and named let), `syntax-rules`, and eventually\n\" a header generator and shortcuts to inser (print) lilke statements.\n\" Since many of those patterns have placeholders for code, `f and `s tags are\n\" mapped to what can be thought of as 1st place and 2nd place. For example, in\n\" an `if`, first place is the #t branch, and second place is the #f branch\n\"\n\" Little help with motions is given too. Mapped <C-l> and <C-h> to the next and\n\" previous Sexp, in depth parsing order.\n\"\n\" You are more than suggested to define the bindings as you want them.\n\" I chose <Leader>sX so that the \"s\" reminds you scheme, though is slows down\n\" typing quite a bit. Moreover, you might not want a 3 keyed shortcut to start a\n\" quoted list...\n\"\n\" Also comes with a function that closes all open brackets.\n","4":"\" This is a simple fileplugin supposed to help you write Scheme code fast.\n\" Comes with shortcuts for usual patterns such as `if`, `cond`, `case`, as\n\" well as `let`s (normal, letrec and named let), `syntax-rules`, and eventually\n\" a header generator and shortcuts to inser (print) lilke statements.\n\" Since many of those patterns have placeholders for code, `f and `s tags are\n\" mapped to what can be thought of as 1st place and 2nd place. For example, in\n\" an `if`, first place is the #t branch, and second place is the #f branch\n\"\n\" Little help with motions is given too. Mapped <C-l> and <C-h> to the next and\n\" previous Sexp, in depth parsing order.\n\"\n\" You are more than suggested to define the bindings as you want them.\n\" I chose <Leader>sX so that the \"s\" reminds you scheme, though is slows down\n\" typing quite a bit. Moreover, you might not want a 3 keyed shortcut to start a\n\" quoted list...\n\"\n\" Also comes with a function that closes all open brackets.\n","install_details":"\" Simply drop this file into your $HOME\/.vim\/ftplugin\/ directory and add to your\n\" vimrc file the following line :\n\" autocmd Filetype scheme source ~\/.vim\/ftplugin\/SchemeMode.vim\n\"","5":"\" Simply drop this file into your $HOME\/.vim\/ftplugin\/ directory and add to your\n\" vimrc file the following line :\n\" autocmd Filetype scheme source ~\/.vim\/ftplugin\/SchemeMode.vim\n\"","first_name":"Adrien","6":"Adrien","last_name":"(Axioplase::Pied)","7":"(Axioplase::Pied)","releases":[{"0":"1918","vim_version":"7.0","1":"7.0","script_version":"0.577","2":"0.577","version_comment":"Initial upload","3":"Initial upload","package":"SchemeMode.vim","4":"SchemeMode.vim","src_id":"7219","5":"7219","creation_date":"1181243671","6":"1181243671"}]},"1917":{"script_id":"1917","0":"1917","script_name":"mySqlGenQueryMenu.vim","1":"mySqlGenQueryMenu.vim","script_type":"utility","2":"utility","summary":"Generates vim menu from sql queries files (python required)","3":"Generates vim menu from sql queries files (python required)","description":"When you use a database as a tool for your work, you may have queries you\r\noften use and don't want to write each time.\r\nIn this case, as you are a vim user, you may dream of a way to simply create a\r\nmenu in vim containing all your queries with a few parameters...\r\nThis plugin is for you.\r\n\r\nIt aims to let you write your queries in sql files as you would normally do it\r\nand then generate a menu for you to access them.\r\n\r\n\r\nAdvertising :\r\nHave you heard of this other funny script ?\r\n\r\nIf you find this script  too serious, try this other one : \r\nhttp:\/\/www.vim.org\/scripts\/script.php?script_id=800\r\nWith this script you'll be able to MixCase like the best H\u00c3\u00a0\u00c2\u00aed(or\u00c3\u00aa m1\u00c3\u0097C\u00c3\u00a0se ma$+Er and make your coding very new style ;-)","4":"When you use a database as a tool for your work, you may have queries you\r\noften use and don't want to write each time.\r\nIn this case, as you are a vim user, you may dream of a way to simply create a\r\nmenu in vim containing all your queries with a few parameters...\r\nThis plugin is for you.\r\n\r\nIt aims to let you write your queries in sql files as you would normally do it\r\nand then generate a menu for you to access them.\r\n\r\n\r\nAdvertising :\r\nHave you heard of this other funny script ?\r\n\r\nIf you find this script  too serious, try this other one : \r\nhttp:\/\/www.vim.org\/scripts\/script.php?script_id=800\r\nWith this script you'll be able to MixCase like the best H\u00c3\u00a0\u00c2\u00aed(or\u00c3\u00aa m1\u00c3\u0097C\u00c3\u00a0se ma$+Er and make your coding very new style ;-)","install_details":"Just drop this file in your plugin directory.\r\n\r\nNote: this plugin uses python and the DBExt plugin to access the databases\r\n    http:\/\/www.vim.org\/scripts\/script.php?script_id=356\r\n\r\nTo init the help tags, start Vim and do either\r\n:helptags ~\/.vim\/doc (for unix)\r\nor\r\n:helptags ~\\vimfiles\\doc (for MSWindows)\r\nto rebuild the tags file. Do \":help add-local-help\" for more details.\r\n","5":"Just drop this file in your plugin directory.\r\n\r\nNote: this plugin uses python and the DBExt plugin to access the databases\r\n    http:\/\/www.vim.org\/scripts\/script.php?script_id=356\r\n\r\nTo init the help tags, start Vim and do either\r\n:helptags ~\/.vim\/doc (for unix)\r\nor\r\n:helptags ~\\vimfiles\\doc (for MSWindows)\r\nto rebuild the tags file. Do \":help add-local-help\" for more details.\r\n","first_name":"jean-christophe","6":"jean-christophe","last_name":"clavier","7":"clavier","releases":[{"0":"1917","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"mySqlGenQueryMenu.zip","4":"mySqlGenQueryMenu.zip","src_id":"7213","5":"7213","creation_date":"1181175439","6":"1181175439"}]},"1916":{"script_id":"1916","0":"1916","script_name":"vdm.vim","1":"vdm.vim","script_type":"syntax","2":"syntax","summary":"Syntax file for VDM-SL","3":"Syntax file for VDM-SL","description":"This script provides syntax highlight for VDM-SL specification language.\r\n\r\nDownload at https:\/\/rcgoncalves.pt\/files\/vdm.zip","4":"This script provides syntax highlight for VDM-SL specification language.\r\n\r\nDownload at https:\/\/rcgoncalves.pt\/files\/vdm.zip","install_details":"Put vdm.vim in your syntax diretory (e.g. ~\/.vim\/syntax).\r\nAdd line below to your .vimrc file:\r\nau BufNewFile,BufRead *.vdm     setf vdm","5":"Put vdm.vim in your syntax diretory (e.g. ~\/.vim\/syntax).\r\nAdd line below to your .vimrc file:\r\nau BufNewFile,BufRead *.vdm     setf vdm","first_name":"Rui Carlos","6":"Rui Carlos","last_name":"Gon\u00c3\u00a7alves","7":"Gon\u00c3\u00a7alves","releases":[{"0":"1916","vim_version":"7.0","1":"7.0","script_version":"2.6","2":"2.6","version_comment":"Error fixed (multiple spaces in expressions).","3":"Error fixed (multiple spaces in expressions).","package":"vdm.vim","4":"vdm.vim","src_id":"16588","5":"16588","creation_date":"1317054185","6":"1317054185"},{"0":"1916","vim_version":"7.0","1":"7.0","script_version":"2.5","2":"2.5","version_comment":"Error correction (exits  -->  exists).","3":"Error correction (exits  -->  exists).","package":"vdm.vim","4":"vdm.vim","src_id":"7317","5":"7317","creation_date":"1183446365","6":"1183446365"},{"0":"1916","vim_version":"7.0","1":"7.0","script_version":"2.4","2":"2.4","version_comment":"Correction on mk_* functions syntax.","3":"Correction on mk_* functions syntax.","package":"vdm.vim","4":"vdm.vim","src_id":"7249","5":"7249","creation_date":"1181917598","6":"1181917598"}]},"1915":{"script_id":"1915","0":"1915","script_name":"tbibtools","1":"tbibtools","script_type":"utility","2":"utility","summary":"bibtex-related utilities (sort, reformat, list contents ...)","3":"bibtex-related utilities (sort, reformat, list contents ...)","description":"tbibtools provide a simple regexp-based bibtex parser. Please be aware \r\nthat this script makes a few assumptions on how a bib file should look \r\nlike and that it may fail on files formatted in unusual ways. Failure \r\nmay lead to loss of bib entries and malformed or incomplete output.  \r\nComments and other text will be stripped when reformatting entries. Any \r\nfeature of bibtex I don't know and\/or don't use myself is most likely \r\nnot supported by this script\/class.\r\n\r\nPlease take care when using this script. Make backups and check the \r\noutput, especially when using the -f command-line option. Don't blame me \r\nif you lose information or end up with corrupted bib files.\r\n\r\n\r\nFeatures:\r\n    - sort bib files\r\n    - reformat bib files\r\n    - list keys in a bib file\r\n    - show bib entries matching a regular expression\r\n\r\n\r\nFrom the commands line:\r\n\r\nThe ruby directory contains a file tbibtools.rb that can be used as a \r\nstand-alone script from the command line. For command-line use, only the \r\nfile tbibtools.rb and a ruby interpreter is needed.\r\n\r\n    tbibtools [OPTIONS] < IN > OUT\r\n\r\n\r\nFor vim users:\r\n\r\nThe file plugin\/tbibtools.vim provides the commands\r\n\r\n    :'<,'>TBibTools [OPTIONS]\r\n        Filter the selected text or the whole buffer through \r\n        tbibtools.rb. The command line options are the same as for the \r\n        script.\r\n\r\n    :'<,'>TBibList [OPTIONS]\r\n        List keys in a bibtex file (mostly the same as TBibTools --ls \r\n        but lets you select an entry and jump to its position in the \r\n        bibtex file).\r\n\r\n\r\nOptions:\r\n\r\n    -i          ... case insensitive\r\n    -e REGEXP   ... display entries matching the regexp\r\n    -f FORMATS  ... re-format (order matters, comma-separated list): \r\n                    align, bracket, check, downcaseType, gsub, indent, \r\n                    list, nil, nnIsYear, ls, tml, stripEmpty, \r\n                    stripRedundantTitel, unwrap, upcaseType, wrap\r\n    --ls        ... synonym for: -f list,stripPrelude (\"list\" implies \r\n    \"unwrap\")\r\n    -l FORMAT   ... format string for list\r\n    -q FIELD=RX ... show entries for which field matches the regexp\r\n    -P          ... strip the prelude: same as -f stripPrelude but helps \r\n    to maintain the original formatting\r\n    -s FIELD    ... sort (default: sort by key; key = _id, type = _type)\r\n    -S          ... replace\/expand strings\r\n    --strip FIELDS ... ignore\/strip fields\r\n    -u          ... unsorted\r\n\r\n\r\nFormats:\r\n\r\nFormats can be easily plugged in by defining a method (see \r\nTBibTools#format). As the formatters process the entry one after the \r\nother, the order given on the command line matters.\r\n\r\nPlease scrutinize the output carefully. The use of an incomplete or simply \r\nthe wrong set of formatters can easily result in a corrupted bib file \r\nthat bibtex cannot read.\r\n\r\n    align\r\n         Align the = sign.\r\n\r\n    bracket\r\n         Enclose non-numeric values in curly braces.\r\n\r\n    gsub=FROM1:TO2:FROM2:TO2\r\n         Replace text in the value.\r\n\r\n    indent,\r\n         indent=N (default=4) Indent the entry's key-value pairs.\r\n\r\n    nil\r\n         Don't print any output.\r\n\r\n    stripRedundantTitel\r\n         If an entry has a title and a booktitle field with the\r\n         same value, only the booktitle field will be propagated.\r\n\r\n    stripEmpty\r\n         Drop fields with empty values.\r\n\r\n    unwrap\r\n         Put wrapped text into a single line.\r\n\r\n    wrap\r\n         Try to cheaply wrap the value.\r\n\r\n    check\r\n         Print a warning on invalid entries\r\n\r\n    nnIsYear\r\n         Try to correctly sort two-digit numbers in the key, i.e. sort \r\n         example99 before example00.\r\n\r\n    downcaseType\r\n         Downcase the bibtex type.\r\n\r\n    upcaseType\r\n         Put the bibtex type in upper case letters.\r\n\r\n    list\r\n         List keys only.\r\n\r\n    stripPrelude\r\n         Drop any prelude (useful in conjunction with some other \r\n         commands). It is supposed the bibtex file is made up of a \r\n         prelude containing @string definitions and a series of bibtex \r\n         entries.\r\n\r\n    tml\r\n        A shortcut for: \r\n        nnIsYear,downcaseType,stripRedundantTitle,stripEmpty,bracket,align,unwrap,indent \r\n        (see also TBibTools#format_option_tml)\r\n\r\n\r\nExamples:\r\n\r\nReformat the bib file\r\n\r\n  tbibtools -f tml < monos.bib > monos_sorted.bib\r\n\r\n  tbibtools -f gsub=\u00c3\u0083\u00c2\u00a4:\\\"a:\u00c3\u0083\u00c2\u00b6:\\\"o:\u00c3\u0083\u00c2\u00bc:\\\"u < monos.bib > monos_sorted.bib\r\n\r\nList the contents (see also TBibTools#format_option_ls)\r\n\r\n  tbibtools --ls < monos.bib\r\n  tbibtools --ls -l \"#{_lineno}: #{author|editor|institution}: #{title|booktitle}\" < monos.bib\r\n\r\nExtract a few entries \u00c3\u00a0 la grep (kind of):\r\n\r\n  tbibtools -P -e Hugo < monos.bib\r\n  tbibtools -P -q author=Adorno -q keywords=Adorno < monos.bib\r\n  tbibtools -P -q author=\"Husserl|Merleau-Ponty\" < monos.bib\r\n\r\n","4":"tbibtools provide a simple regexp-based bibtex parser. Please be aware \r\nthat this script makes a few assumptions on how a bib file should look \r\nlike and that it may fail on files formatted in unusual ways. Failure \r\nmay lead to loss of bib entries and malformed or incomplete output.  \r\nComments and other text will be stripped when reformatting entries. Any \r\nfeature of bibtex I don't know and\/or don't use myself is most likely \r\nnot supported by this script\/class.\r\n\r\nPlease take care when using this script. Make backups and check the \r\noutput, especially when using the -f command-line option. Don't blame me \r\nif you lose information or end up with corrupted bib files.\r\n\r\n\r\nFeatures:\r\n    - sort bib files\r\n    - reformat bib files\r\n    - list keys in a bib file\r\n    - show bib entries matching a regular expression\r\n\r\n\r\nFrom the commands line:\r\n\r\nThe ruby directory contains a file tbibtools.rb that can be used as a \r\nstand-alone script from the command line. For command-line use, only the \r\nfile tbibtools.rb and a ruby interpreter is needed.\r\n\r\n    tbibtools [OPTIONS] < IN > OUT\r\n\r\n\r\nFor vim users:\r\n\r\nThe file plugin\/tbibtools.vim provides the commands\r\n\r\n    :'<,'>TBibTools [OPTIONS]\r\n        Filter the selected text or the whole buffer through \r\n        tbibtools.rb. The command line options are the same as for the \r\n        script.\r\n\r\n    :'<,'>TBibList [OPTIONS]\r\n        List keys in a bibtex file (mostly the same as TBibTools --ls \r\n        but lets you select an entry and jump to its position in the \r\n        bibtex file).\r\n\r\n\r\nOptions:\r\n\r\n    -i          ... case insensitive\r\n    -e REGEXP   ... display entries matching the regexp\r\n    -f FORMATS  ... re-format (order matters, comma-separated list): \r\n                    align, bracket, check, downcaseType, gsub, indent, \r\n                    list, nil, nnIsYear, ls, tml, stripEmpty, \r\n                    stripRedundantTitel, unwrap, upcaseType, wrap\r\n    --ls        ... synonym for: -f list,stripPrelude (\"list\" implies \r\n    \"unwrap\")\r\n    -l FORMAT   ... format string for list\r\n    -q FIELD=RX ... show entries for which field matches the regexp\r\n    -P          ... strip the prelude: same as -f stripPrelude but helps \r\n    to maintain the original formatting\r\n    -s FIELD    ... sort (default: sort by key; key = _id, type = _type)\r\n    -S          ... replace\/expand strings\r\n    --strip FIELDS ... ignore\/strip fields\r\n    -u          ... unsorted\r\n\r\n\r\nFormats:\r\n\r\nFormats can be easily plugged in by defining a method (see \r\nTBibTools#format). As the formatters process the entry one after the \r\nother, the order given on the command line matters.\r\n\r\nPlease scrutinize the output carefully. The use of an incomplete or simply \r\nthe wrong set of formatters can easily result in a corrupted bib file \r\nthat bibtex cannot read.\r\n\r\n    align\r\n         Align the = sign.\r\n\r\n    bracket\r\n         Enclose non-numeric values in curly braces.\r\n\r\n    gsub=FROM1:TO2:FROM2:TO2\r\n         Replace text in the value.\r\n\r\n    indent,\r\n         indent=N (default=4) Indent the entry's key-value pairs.\r\n\r\n    nil\r\n         Don't print any output.\r\n\r\n    stripRedundantTitel\r\n         If an entry has a title and a booktitle field with the\r\n         same value, only the booktitle field will be propagated.\r\n\r\n    stripEmpty\r\n         Drop fields with empty values.\r\n\r\n    unwrap\r\n         Put wrapped text into a single line.\r\n\r\n    wrap\r\n         Try to cheaply wrap the value.\r\n\r\n    check\r\n         Print a warning on invalid entries\r\n\r\n    nnIsYear\r\n         Try to correctly sort two-digit numbers in the key, i.e. sort \r\n         example99 before example00.\r\n\r\n    downcaseType\r\n         Downcase the bibtex type.\r\n\r\n    upcaseType\r\n         Put the bibtex type in upper case letters.\r\n\r\n    list\r\n         List keys only.\r\n\r\n    stripPrelude\r\n         Drop any prelude (useful in conjunction with some other \r\n         commands). It is supposed the bibtex file is made up of a \r\n         prelude containing @string definitions and a series of bibtex \r\n         entries.\r\n\r\n    tml\r\n        A shortcut for: \r\n        nnIsYear,downcaseType,stripRedundantTitle,stripEmpty,bracket,align,unwrap,indent \r\n        (see also TBibTools#format_option_tml)\r\n\r\n\r\nExamples:\r\n\r\nReformat the bib file\r\n\r\n  tbibtools -f tml < monos.bib > monos_sorted.bib\r\n\r\n  tbibtools -f gsub=\u00c3\u0083\u00c2\u00a4:\\\"a:\u00c3\u0083\u00c2\u00b6:\\\"o:\u00c3\u0083\u00c2\u00bc:\\\"u < monos.bib > monos_sorted.bib\r\n\r\nList the contents (see also TBibTools#format_option_ls)\r\n\r\n  tbibtools --ls < monos.bib\r\n  tbibtools --ls -l \"#{_lineno}: #{author|editor|institution}: #{title|booktitle}\" < monos.bib\r\n\r\nExtract a few entries \u00c3\u00a0 la grep (kind of):\r\n\r\n  tbibtools -P -e Hugo < monos.bib\r\n  tbibtools -P -q author=Adorno -q keywords=Adorno < monos.bib\r\n  tbibtools -P -q author=\"Husserl|Merleau-Ponty\" < monos.bib\r\n\r\n","install_details":"Install as vim plugin:\r\nExtract the archive to ~\/.vim or ~\/vimfiles (Windows).\r\n\r\nA vim with compiled-in ruby support is required.\r\n\r\nThe TBibList command requires tlib (vimscript #1863).\r\n\r\n\r\nInstall as script:\r\nThe ruby directory contains a rudimentary makefile:\r\n    make -f Makefile.tbibtools install\r\n\r\n\r\nAlso available via git\r\nhttp:\/\/github.com\/tomtom\/tbibtools_vim","5":"Install as vim plugin:\r\nExtract the archive to ~\/.vim or ~\/vimfiles (Windows).\r\n\r\nA vim with compiled-in ruby support is required.\r\n\r\nThe TBibList command requires tlib (vimscript #1863).\r\n\r\n\r\nInstall as script:\r\nThe ruby directory contains a rudimentary makefile:\r\n    make -f Makefile.tbibtools install\r\n\r\n\r\nAlso available via git\r\nhttp:\/\/github.com\/tomtom\/tbibtools_vim","first_name":"Tom","6":"Tom","last_name":"Link","7":"Link","releases":[{"0":"1915","vim_version":"7.0","1":"7.0","script_version":"0.5","2":"0.5","version_comment":"- VIM: Require tlib 0.9\r\n","3":"- VIM: Require tlib 0.9\r\n","package":"tbibtools.zip","4":"tbibtools.zip","src_id":"7364","5":"7364","creation_date":"1184663354","6":"1184663354"},{"0":"1915","vim_version":"7.0","1":"7.0","script_version":"0.4","2":"0.4","version_comment":"- sortCrossref: Put cross-referenced entries to the back.\r\n- New format: (un)selectCrossref: View only entries that are (not) cross-referenced\r\n- Improved TBibList (include keywords in list; if g:tbibUseCache is set, the listing will be cached between editing sessions)\r\n","3":"- sortCrossref: Put cross-referenced entries to the back.\r\n- New format: (un)selectCrossref: View only entries that are (not) cross-referenced\r\n- Improved TBibList (include keywords in list; if g:tbibUseCache is set, the listing will be cached between editing sessions)\r\n","package":"tbibtools.zip","4":"tbibtools.zip","src_id":"7259","5":"7259","creation_date":"1182164571","6":"1182164571"},{"0":"1915","vim_version":"7.0","1":"7.0","script_version":"0.3","2":"0.3","version_comment":"- Syntax of the query command has changed: query FIELD1 => RX1, FIELD2 => RX2 ...\r\n- Merge duplicate entries\r\n- Merge certain conflicting fields\r\n- FIX: Problem with --ls\r\n","3":"- Syntax of the query command has changed: query FIELD1 => RX1, FIELD2 => RX2 ...\r\n- Merge duplicate entries\r\n- Merge certain conflicting fields\r\n- FIX: Problem with --ls\r\n","package":"tbibtools.zip","4":"tbibtools.zip","src_id":"7220","5":"7220","creation_date":"1181261842","6":"1181261842"}]},"1913":{"script_id":"1913","0":"1913","script_name":"perlhelp.vim","1":"perlhelp.vim","script_type":"utility","2":"utility","summary":"Interface to perldoc","3":"Interface to perldoc","description":"A plugin that provides quick and easy access to perldoc. The perldoc text is displayed in a new window. This window is reused for resulting lookups if left open. When looking up a module filetype is set to perl so it is correctly highlighted, if syntax highlighting is turned on.\r\n\r\nFunctions:\r\nThe functions can accept an argument for the topic to lookup. If no argument is supplied they will prompt for the topic.\r\nPerlFAQ - Lookup a regular expression using perldoc -q.\r\nPerlHelp - Lookup a topic using perldoc.\r\nPerlFunc - Lookup a function using perldoc -f.\r\nPerlMod - Lookup a module using perldoc -m.\r\nPerlVar - Lookup a Perl builtin variable in the perlvar page.\r\n\r\nKey Mappings:\r\n<Leader>ph - Lookup the selected text in visual mode or the word under the cursor in normal mode using perldoc.\r\n<Leader>PH - Prompt for a topic to lookup using perldoc.\r\n<Leader>pf - Lookup the selected text in visual mode or the word under the cursor in normal mode using perldoc -f.\r\n<Leader>PF - Prompt for a function to lookup using perldoc -f.\r\n<Leader>pm - Lookup the selected text in visual mode or the word under the cursor in normal mode using perldoc -m.\r\n<Leader>PM - Prompt for a module to display using perldoc -m.\r\n<Leader>pq - Lookup the selected text in visual mode or the word under the cursor in normal mode using perldoc -q.\r\n<Leader>PQ - Prompt for a regular expression to lookup using perldoc -q.\r\n<Leader>pv - Lookup the selected text in visual mode or the word under the cursor in normal mode in the perlvar page.\r\n<Leader>PV - Prompt for a Perl builtin variable and look it up in the perlvar page.\r\n\r\nThe <Leader> key is normally '\\\\'. Thus to lookup the word under the cursor type '\\ph'.\r\n\r\nTip:\r\nAdding the following to your vimrc file will make POD documentation in Perl modules easier to read:\r\nlet perl_include_pod=1\r\n\r\nIf you find any problems or have any suggestions please feel free to email me at LoranceStinson+perlhelp AT gmail DOT com.\r\n\r\nAlso available at http:\/\/lorance.freeshell.org\/perlhelp\/","4":"A plugin that provides quick and easy access to perldoc. The perldoc text is displayed in a new window. This window is reused for resulting lookups if left open. When looking up a module filetype is set to perl so it is correctly highlighted, if syntax highlighting is turned on.\r\n\r\nFunctions:\r\nThe functions can accept an argument for the topic to lookup. If no argument is supplied they will prompt for the topic.\r\nPerlFAQ - Lookup a regular expression using perldoc -q.\r\nPerlHelp - Lookup a topic using perldoc.\r\nPerlFunc - Lookup a function using perldoc -f.\r\nPerlMod - Lookup a module using perldoc -m.\r\nPerlVar - Lookup a Perl builtin variable in the perlvar page.\r\n\r\nKey Mappings:\r\n<Leader>ph - Lookup the selected text in visual mode or the word under the cursor in normal mode using perldoc.\r\n<Leader>PH - Prompt for a topic to lookup using perldoc.\r\n<Leader>pf - Lookup the selected text in visual mode or the word under the cursor in normal mode using perldoc -f.\r\n<Leader>PF - Prompt for a function to lookup using perldoc -f.\r\n<Leader>pm - Lookup the selected text in visual mode or the word under the cursor in normal mode using perldoc -m.\r\n<Leader>PM - Prompt for a module to display using perldoc -m.\r\n<Leader>pq - Lookup the selected text in visual mode or the word under the cursor in normal mode using perldoc -q.\r\n<Leader>PQ - Prompt for a regular expression to lookup using perldoc -q.\r\n<Leader>pv - Lookup the selected text in visual mode or the word under the cursor in normal mode in the perlvar page.\r\n<Leader>PV - Prompt for a Perl builtin variable and look it up in the perlvar page.\r\n\r\nThe <Leader> key is normally '\\\\'. Thus to lookup the word under the cursor type '\\ph'.\r\n\r\nTip:\r\nAdding the following to your vimrc file will make POD documentation in Perl modules easier to read:\r\nlet perl_include_pod=1\r\n\r\nIf you find any problems or have any suggestions please feel free to email me at LoranceStinson+perlhelp AT gmail DOT com.\r\n\r\nAlso available at http:\/\/lorance.freeshell.org\/perlhelp\/","install_details":"Unzip the file in your .vim directory.\r\n\r\nUpdate your help tags to install the help text. \":helptags ~\/.vim\/doc\/\" should do it","5":"Unzip the file in your .vim directory.\r\n\r\nUpdate your help tags to install the help text. \":helptags ~\/.vim\/doc\/\" should do it","first_name":"Lorance","6":"Lorance","last_name":"Stinson","7":"Stinson","releases":[{"0":"1913","vim_version":"6.0","1":"6.0","script_version":"1.5","2":"1.5","version_comment":"*Added lookup of Perl builtin variables via \\pv and PerlVar.\r\n*Now loads default topics when no topic is provided.","3":"*Added lookup of Perl builtin variables via \\pv and PerlVar.\r\n*Now loads default topics when no topic is provided.","package":"perlhelp.zip","4":"perlhelp.zip","src_id":"7304","5":"7304","creation_date":"1182783475","6":"1182783475"},{"0":"1913","vim_version":"6.0","1":"6.0","script_version":"1.4","2":"1.4","version_comment":"When lookup up a function strip everything up to, and including, '->'.  This will make methods be looked up instead of the object the method is called from.","3":"When lookup up a function strip everything up to, and including, '->'.  This will make methods be looked up instead of the object the method is called from.","package":"perlhelp.zip","4":"perlhelp.zip","src_id":"7290","5":"7290","creation_date":"1182522241","6":"1182522241"},{"0":"1913","vim_version":"6.0","1":"6.0","script_version":"1.3","2":"1.3","version_comment":"* Enhanced the handling of module and general help topic lookup.\r\n* Set the file type to man when looking up general perl help topics.","3":"* Enhanced the handling of module and general help topic lookup.\r\n* Set the file type to man when looking up general perl help topics.","package":"perlhelp.zip","4":"perlhelp.zip","src_id":"7250","5":"7250","creation_date":"1181931956","6":"1181931956"},{"0":"1913","vim_version":"6.0","1":"6.0","script_version":"1.2","2":"1.2","version_comment":"Removed 'setlocal iskeyword+=:' and used <cWORD> and a substitution as suggested by Erik Falor.","3":"Removed 'setlocal iskeyword+=:' and used <cWORD> and a substitution as suggested by Erik Falor.","package":"perlhelp.zip","4":"perlhelp.zip","src_id":"7245","5":"7245","creation_date":"1181815053","6":"1181815053"},{"0":"1913","vim_version":"6.0","1":"6.0","script_version":"1.1","2":"1.1","version_comment":"Added 'setlocal iskeyword+=:' to account for :'s in module names.","3":"Added 'setlocal iskeyword+=:' to account for :'s in module names.","package":"perlhelp.zip","4":"perlhelp.zip","src_id":"7241","5":"7241","creation_date":"1181730143","6":"1181730143"},{"0":"1913","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"perlhelp.zip","4":"perlhelp.zip","src_id":"7202","5":"7202","creation_date":"1180988594","6":"1180988594"}]},"1912":{"script_id":"1912","0":"1912","script_name":"in.vim","1":"in.vim","script_type":"syntax","2":"syntax","summary":"Syntax file for Silvaco\/Simucad Atlas and Athena input files","3":"Syntax file for Silvaco\/Simucad Atlas and Athena input files","description":"This is a syntax file for input files used by \"Atlas\" or \"Athena\", which are semiconductor device and process modeling tools developed by Silvaco\/Simucad.   The default extension for \"Atlas\" and \"Athena\" input files is .in","4":"This is a syntax file for input files used by \"Atlas\" or \"Athena\", which are semiconductor device and process modeling tools developed by Silvaco\/Simucad.   The default extension for \"Atlas\" and \"Athena\" input files is .in","install_details":"","5":"","first_name":"Derek","6":"Derek","last_name":"Hullinger","7":"Hullinger","releases":[{"0":"1912","vim_version":"6.0","1":"6.0","script_version":"1","2":"1","version_comment":"Initial upload","3":"Initial upload","package":"in.vim","4":"in.vim","src_id":"7200","5":"7200","creation_date":"1180957297","6":"1180957297"}]},"1911":{"script_id":"1911","0":"1911","script_name":"SuperPre","1":"SuperPre","script_type":"syntax","2":"syntax","summary":"syntax for the text that contains several programming language","3":"syntax for the text that contains several programming language","description":"The spre (SuperPre) is a syntax plugin for the text that contains several programing language.  The text can be converted to HTML.  This is useful for writing programming notes or creating web pages.\r\n\r\nspre syntax is like a C macro.  Example to make HTML:\r\n<html>\r\n<head>\r\n<title>example<\/title>\r\n<\/head>\r\n<body>\r\n#macro\r\n\" You can use Vim script as embedded macro.\r\nreturn \"<h1>Example to make HTML<\/h1>\"\r\n#end\r\n\r\n## comment is removed from result.\r\n\r\n#pre c {\"colorscheme\":\"evening\"}\r\n\/* This section will be <pre class=\"c\">...<\/pre> *\/\r\nint func(int n) {\r\n  return func(n);\r\n}\r\n#end\r\n\r\n#macro\r\nlet s:attr = {}\r\nlet s:attr.colorscheme = \"desert\"\r\nlet s:attr.tag = \"div\"\r\nlet s:attr.class = \"c main\"\r\nlet s:attr.modeline = \"list number\"\r\n#end\r\n#pre c s:attr\r\n\/* This section will be <div class=\"c main\">...<\/div> *\/\r\nint main(int argc, char **argv) {\r\n  return 0;\r\n}\r\n#end\r\n\r\n#macro\r\nreturn readfile(expand(\"%:p:h\") . \"\/footer.txt\")\r\n#end\r\n<\/body>\r\n<\/html>\r\n\r\nIf you want to highlight HTML tag outside of spre macro:\r\n  :set ft=html.spre\r\nSpre will work as additional syntax.\r\n\r\ncolored example:\r\nhttp:\/\/yukihiro.nakadaira.googlepages.com\/spre_example.html","4":"The spre (SuperPre) is a syntax plugin for the text that contains several programing language.  The text can be converted to HTML.  This is useful for writing programming notes or creating web pages.\r\n\r\nspre syntax is like a C macro.  Example to make HTML:\r\n<html>\r\n<head>\r\n<title>example<\/title>\r\n<\/head>\r\n<body>\r\n#macro\r\n\" You can use Vim script as embedded macro.\r\nreturn \"<h1>Example to make HTML<\/h1>\"\r\n#end\r\n\r\n## comment is removed from result.\r\n\r\n#pre c {\"colorscheme\":\"evening\"}\r\n\/* This section will be <pre class=\"c\">...<\/pre> *\/\r\nint func(int n) {\r\n  return func(n);\r\n}\r\n#end\r\n\r\n#macro\r\nlet s:attr = {}\r\nlet s:attr.colorscheme = \"desert\"\r\nlet s:attr.tag = \"div\"\r\nlet s:attr.class = \"c main\"\r\nlet s:attr.modeline = \"list number\"\r\n#end\r\n#pre c s:attr\r\n\/* This section will be <div class=\"c main\">...<\/div> *\/\r\nint main(int argc, char **argv) {\r\n  return 0;\r\n}\r\n#end\r\n\r\n#macro\r\nreturn readfile(expand(\"%:p:h\") . \"\/footer.txt\")\r\n#end\r\n<\/body>\r\n<\/html>\r\n\r\nIf you want to highlight HTML tag outside of spre macro:\r\n  :set ft=html.spre\r\nSpre will work as additional syntax.\r\n\r\ncolored example:\r\nhttp:\/\/yukihiro.nakadaira.googlepages.com\/spre_example.html","install_details":"","5":"","first_name":"Yukihiro","6":"Yukihiro","last_name":"Nakadaira","7":"Nakadaira","releases":[{"0":"1911","vim_version":"7.0","1":"7.0","script_version":"1.3","2":"1.3","version_comment":"Added #macro","3":"Added #macro","package":"spre.zip","4":"spre.zip","src_id":"7834","5":"7834","creation_date":"1193384420","6":"1193384420"},{"0":"1911","vim_version":"7.0","1":"7.0","script_version":"1.2","2":"1.2","version_comment":"bug fix","3":"bug fix","package":"spre.zip","4":"spre.zip","src_id":"7323","5":"7323","creation_date":"1183697274","6":"1183697274"},{"0":"1911","vim_version":"7.0","1":"7.0","script_version":"1.1","2":"1.1","version_comment":"bug fix","3":"bug fix","package":"spre.zip","4":"spre.zip","src_id":"7203","5":"7203","creation_date":"1180988661","6":"1180988661"},{"0":"1911","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"spre.zip","4":"spre.zip","src_id":"7196","5":"7196","creation_date":"1180801624","6":"1180801624"}]},"1910":{"script_id":"1910","0":"1910","script_name":"QuickBuf","1":"QuickBuf","script_type":"utility","2":"utility","summary":"Very small, clean but quick and powerful buffer manager!","3":"Very small, clean but quick and powerful buffer manager!","description":"QuickBuf\r\nVim plugin helps navigate and manipulate buffers\r\nMaintainer: palnart <palnart@gmail.com>\r\n\r\nBrief description:\r\nWhile making the task of browsing and manipulating buffers visual and simple, QuickBuf also offers advanced abilities of dealing with buffers (ex: \"unlisted\" mode). It's unique among several other buffer managers for creating no dedicated buffer and defining no auto command, thus minimize its interference.\r\n\r\nGive it a try and you may find it all you need to work with Vim's buffers!\r\nAny bugs or suggestions, please mail to: palnart@gmail.com\r\n\r\nUsage:\r\n+ Press the assigned hotkey to activate QuickBuf (default <F4>). It brings out a list of buffers that you can browse and give commands on! Some indicators in the list:\r\n\t- * : the buffer being opened in the active window\r\n\t- = : a buffer being opened in a window, but not active\r\n\t- [+] : modifed buffer\r\n+ Use k\/j or <Up>\/<Down> keys to select the buffer.\r\n+ Press a key to give a command to the currently selected buffer\r\n\t- d : delete buffer\r\n\t- w : wipe out buffer\r\n\t- s : open buffer in a new horizontally split window\r\n\t- u : open buffer\r\n\t- <enter> : open buffer and leave QuickBuf; if the\tbuffer is already opened in a window, switch to that window.\r\n+ d, w, and <enter> operations may fail (ex: delete a modified buffer), QuickBuf will inform you so that you can force them by preceding the above characters with an exclamation mark ('!'). Ex: !d, !w, !<enter>\r\n+ Instead of moving the selection bar around to select a buffer, you can use a number to specify a buffer. For example: '2d' will delete the second buffer in the list. Try '3<enter>', '1w', '1!w'\r\n+ Use 'l' key to toggle between LISTED and UNLISTED mode. Which mode QuickBuf enter first depends on the active buffer. While in UNLISTED mode, 'unlisted' buffers (the buffers you have deleted) are showed. Also:\r\n\t- [+] indicates a loaded buffer\r\n\t- 'd' command makes the selected buffer 'listed' again\r\n+ Press <esc> key to leave QuickBuf","4":"QuickBuf\r\nVim plugin helps navigate and manipulate buffers\r\nMaintainer: palnart <palnart@gmail.com>\r\n\r\nBrief description:\r\nWhile making the task of browsing and manipulating buffers visual and simple, QuickBuf also offers advanced abilities of dealing with buffers (ex: \"unlisted\" mode). It's unique among several other buffer managers for creating no dedicated buffer and defining no auto command, thus minimize its interference.\r\n\r\nGive it a try and you may find it all you need to work with Vim's buffers!\r\nAny bugs or suggestions, please mail to: palnart@gmail.com\r\n\r\nUsage:\r\n+ Press the assigned hotkey to activate QuickBuf (default <F4>). It brings out a list of buffers that you can browse and give commands on! Some indicators in the list:\r\n\t- * : the buffer being opened in the active window\r\n\t- = : a buffer being opened in a window, but not active\r\n\t- [+] : modifed buffer\r\n+ Use k\/j or <Up>\/<Down> keys to select the buffer.\r\n+ Press a key to give a command to the currently selected buffer\r\n\t- d : delete buffer\r\n\t- w : wipe out buffer\r\n\t- s : open buffer in a new horizontally split window\r\n\t- u : open buffer\r\n\t- <enter> : open buffer and leave QuickBuf; if the\tbuffer is already opened in a window, switch to that window.\r\n+ d, w, and <enter> operations may fail (ex: delete a modified buffer), QuickBuf will inform you so that you can force them by preceding the above characters with an exclamation mark ('!'). Ex: !d, !w, !<enter>\r\n+ Instead of moving the selection bar around to select a buffer, you can use a number to specify a buffer. For example: '2d' will delete the second buffer in the list. Try '3<enter>', '1w', '1!w'\r\n+ Use 'l' key to toggle between LISTED and UNLISTED mode. Which mode QuickBuf enter first depends on the active buffer. While in UNLISTED mode, 'unlisted' buffers (the buffers you have deleted) are showed. Also:\r\n\t- [+] indicates a loaded buffer\r\n\t- 'd' command makes the selected buffer 'listed' again\r\n+ Press <esc> key to leave QuickBuf","install_details":"Install:\r\n+ Source it with ':so qbuf.vim' or simply put it in \/plugin under Vim's folder.\r\n+ To define hotkey for QuickBuf:\r\n\tDefine g:qb_hotkey before source qbuf.vim, ex:\r\n\t\tlet g:qb_hotkey = \"<F3>\"\r\n\tOr put that line in your _vimrc profile. Default, key \"<F4>\" is used.\r\n\tWhenever you change g:qb_hotkey, :so qbuf.vim again to update hotkey.","5":"Install:\r\n+ Source it with ':so qbuf.vim' or simply put it in \/plugin under Vim's folder.\r\n+ To define hotkey for QuickBuf:\r\n\tDefine g:qb_hotkey before source qbuf.vim, ex:\r\n\t\tlet g:qb_hotkey = \"<F3>\"\r\n\tOr put that line in your _vimrc profile. Default, key \"<F4>\" is used.\r\n\tWhenever you change g:qb_hotkey, :so qbuf.vim again to update hotkey.","first_name":"pal","6":"pal","last_name":"nart","7":"nart","releases":[{"0":"1910","vim_version":"7.0","1":"7.0","script_version":"1.12","2":"1.12","version_comment":"ADD: key 'c' to close an already opened window.\r\nADD: checking vim's version to silently skip on older vim (less than 7.0). Thanks to Bernhard Walle.","3":"ADD: key 'c' to close an already opened window.\r\nADD: checking vim's version to silently skip on older vim (less than 7.0). Thanks to Bernhard Walle.","package":"qbuf.vim","4":"qbuf.vim","src_id":"9909","5":"9909","creation_date":"1233674145","6":"1233674145"},{"0":"1910","vim_version":"6.0","1":"6.0","script_version":"1.11","2":"1.11","version_comment":"Changes:\r\n   - Automatically select the active buffer\r\n   - Fix the display problem related to Vim's option \"lazyredraw\"","3":"Changes:\r\n   - Automatically select the active buffer\r\n   - Fix the display problem related to Vim's option \"lazyredraw\"","package":"qbuf.zip","4":"qbuf.zip","src_id":"8128","5":"8128","creation_date":"1199563100","6":"1199563100"},{"0":"1910","vim_version":"6.0","1":"6.0","script_version":"1.1","2":"1.1","version_comment":"Changes:\r\n- More stable, tolerant to malformed commands\r\n- Add <up>\/<down> key to navigate buffer list\r\n- Add 's' command to open buffer in a new split window\r\n- Deal with Vim's multiple window\r\n- Improve: 'u' command automatically move select bar to the next buffer\r\n- Add some decorations","3":"Changes:\r\n- More stable, tolerant to malformed commands\r\n- Add <up>\/<down> key to navigate buffer list\r\n- Add 's' command to open buffer in a new split window\r\n- Deal with Vim's multiple window\r\n- Improve: 'u' command automatically move select bar to the next buffer\r\n- Add some decorations","package":"qbuf.zip","4":"qbuf.zip","src_id":"8083","5":"8083","creation_date":"1198543586","6":"1198543586"},{"0":"1910","vim_version":"7.0","1":"7.0","script_version":"1.01","2":"1.01","version_comment":"Minor fix:\r\nSave and keystroke when user press <Enter> but error switching to another buffer, no need to wait a keystroke, just leave QuickBuf, error message still visible!","3":"Minor fix:\r\nSave and keystroke when user press <Enter> but error switching to another buffer, no need to wait a keystroke, just leave QuickBuf, error message still visible!","package":"qbuf.zip","4":"qbuf.zip","src_id":"7198","5":"7198","creation_date":"1180822575","6":"1180822575"},{"0":"1910","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Redesign, much added, much more feature rich!","3":"Redesign, much added, much more feature rich!","package":"qbuf.zip","4":"qbuf.zip","src_id":"7197","5":"7197","creation_date":"1180821177","6":"1180821177"},{"0":"1910","vim_version":"7.0","1":"7.0","script_version":"0.11","2":"0.11","version_comment":"Add a plus sign (+) to indicate modified buffers\r\nError message when buffer list too long to fit in Vim's shell more readable","3":"Add a plus sign (+) to indicate modified buffers\r\nError message when buffer list too long to fit in Vim's shell more readable","package":"quickbuf.zip","4":"quickbuf.zip","src_id":"7190","5":"7190","creation_date":"1180750996","6":"1180750996"},{"0":"1910","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"qbuf.vim","4":"qbuf.vim","src_id":"7187","5":"7187","creation_date":"1180707307","6":"1180707307"}]},"1909":{"script_id":"1909","0":"1909","script_name":"creole.vim","1":"creole.vim","script_type":"syntax","2":"syntax","summary":"creole.vim is a syntax file for the creole wiki markup standard.","3":"creole.vim is a syntax file for the creole wiki markup standard.","description":"creole.vim is a vim syntax file for the http:\/\/www.wikicreole.org markup standard. \r\n\r\nIt is based on vimscript#725 from Andreas Kneib.\r\n\r\nNew versions can be found at http:\/\/www.peter-hoffmann.com\/code\/vim\/","4":"creole.vim is a vim syntax file for the http:\/\/www.wikicreole.org markup standard. \r\n\r\nIt is based on vimscript#725 from Andreas Kneib.\r\n\r\nNew versions can be found at http:\/\/www.peter-hoffmann.com\/code\/vim\/","install_details":"mkdir ~\/.vim\/syntax\r\nmv ~\/creole.vim ~\/.vim\/syntax\/creole.vim\r\n\r\n:set syntax=creole\r\n","5":"mkdir ~\/.vim\/syntax\r\nmv ~\/creole.vim ~\/.vim\/syntax\/creole.vim\r\n\r\n:set syntax=creole\r\n","first_name":"Peter","6":"Peter","last_name":"Hoffmann","7":"Hoffmann","releases":[{"0":"1909","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"creole.vim","4":"creole.vim","src_id":"7182","5":"7182","creation_date":"1180615701","6":"1180615701"}]},"1908":{"script_id":"1908","0":"1908","script_name":"snipper","1":"snipper","script_type":"syntax","2":"syntax","summary":"snippets script for vim (like textmate or scribes have)","3":"snippets script for vim (like textmate or scribes have)","description":"see https:\/\/launchpad.net\/snipper\/ and http:\/\/tmske.blogspot.com\/\r\nyou need vim with python enabled for this script\r\nfor the most recent package at all times you beter use the code of https:\/\/launchpad.net\/snipper\/\r\nThere are some templates in the package (python, c, xml, ...)\r\n\r\nSee http:\/\/snipper.googlecode.com\/files\/snipper-0.1-example.ogg for a small screencast of how snipper works","4":"see https:\/\/launchpad.net\/snipper\/ and http:\/\/tmske.blogspot.com\/\r\nyou need vim with python enabled for this script\r\nfor the most recent package at all times you beter use the code of https:\/\/launchpad.net\/snipper\/\r\nThere are some templates in the package (python, c, xml, ...)\r\n\r\nSee http:\/\/snipper.googlecode.com\/files\/snipper-0.1-example.ogg for a small screencast of how snipper works","install_details":"unpack the package to a folder and see use.wiki in the package.\r\n\r\nyou need vim with python enabled, if you don't have python 2.5 you'll need cElementTree, that you can find\r\nhere: http:\/\/effbot.org\/downloads\/#cElementTree\r\non ubuntu: apt-get install python-celementtree","5":"unpack the package to a folder and see use.wiki in the package.\r\n\r\nyou need vim with python enabled, if you don't have python 2.5 you'll need cElementTree, that you can find\r\nhere: http:\/\/effbot.org\/downloads\/#cElementTree\r\non ubuntu: apt-get install python-celementtree","first_name":"thomas","6":"thomas","last_name":"coopman","7":"coopman","releases":[{"0":"1908","vim_version":"7.0","1":"7.0","script_version":"0.2","2":"0.2","version_comment":"complete refactor,\r\nnow it should work with python2.4 and it should also work when editing different buffers with different filetypes!","3":"complete refactor,\r\nnow it should work with python2.4 and it should also work when editing different buffers with different filetypes!","package":"snipper-0.2.tar.gz","4":"snipper-0.2.tar.gz","src_id":"7173","5":"7173","creation_date":"1180411997","6":"1180411997"},{"0":"1908","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"snipper-0.1.tar.gz","4":"snipper-0.1.tar.gz","src_id":"7170","5":"7170","creation_date":"1180249838","6":"1180249838"}]},"1906":{"script_id":"1906","0":"1906","script_name":"tmboxbrowser","1":"tmboxbrowser","script_type":"utility","2":"utility","summary":"A mbox browser -- Read your e-mails with vim","3":"A mbox browser -- Read your e-mails with vim","description":"mbox is a widely used format to store e-mails. Thunderbird uses it too.\r\n\r\nFeatures\r\n    - Show an index of e-mails contained in a mbox file\r\n    - Mark e-mails as read and don't show them again in the index\r\n    - View e-mails\r\n        - display single parts of a multipart message\r\n        - decode quoted printables\r\n        - filter html mails through an external program; in the default \r\n          setup, this requires \"w3m\" (g:tmboxbrowser_convert_html)\r\n        - view base64 encoded attachments; this also requires \"base64\" \r\n          (g:tmboxbrowser_convert_base64) to be installed\r\n            - if viki (vimscript #861) is installed, use \r\n              VikiOpenSpecialFile()\r\n            - otherwise the file will be opened with \r\n              g:netrw_browsex_viewer\r\n\r\n:TMBoxBrowser[!] [FILE]\r\n    Open a index list with the e-mails in the currently opened mbox.\r\n    With [!], read items are displayed too. In this mode, no e-mails are \r\n    marked as read.\r\n    If [FILE] is given, the file is (newly) edited.\r\n    I.e. if you open a mbox, mark all items as read and then want to \r\n    browse the file again, you'll have to type>\r\n\r\n        :TMBoxBrowser! %\r\n\r\n    Alternatively, press <c-t> in the list view to show\/hide read mails.\r\n\r\n:TMBoxSelect[!]\r\n    Show a list of mbox files (as defined in g:tmboxbrowser_path). \r\n    Open a mbox & call :TMBoxBrowser.\r\n\r\n\r\nKey maps\r\nThese are effective in the __MBOX_Browser__ window:\r\n\r\n    i        ... Display the index list (in gvim, you can also use <esc>)\r\n    p        ... Select parts or re-view mail\r\n    q        ... Quit the browser\r\n    ?        ... Help\r\n    <space>  ... Page down\r\n    <bs>     ... Page up\r\n","4":"mbox is a widely used format to store e-mails. Thunderbird uses it too.\r\n\r\nFeatures\r\n    - Show an index of e-mails contained in a mbox file\r\n    - Mark e-mails as read and don't show them again in the index\r\n    - View e-mails\r\n        - display single parts of a multipart message\r\n        - decode quoted printables\r\n        - filter html mails through an external program; in the default \r\n          setup, this requires \"w3m\" (g:tmboxbrowser_convert_html)\r\n        - view base64 encoded attachments; this also requires \"base64\" \r\n          (g:tmboxbrowser_convert_base64) to be installed\r\n            - if viki (vimscript #861) is installed, use \r\n              VikiOpenSpecialFile()\r\n            - otherwise the file will be opened with \r\n              g:netrw_browsex_viewer\r\n\r\n:TMBoxBrowser[!] [FILE]\r\n    Open a index list with the e-mails in the currently opened mbox.\r\n    With [!], read items are displayed too. In this mode, no e-mails are \r\n    marked as read.\r\n    If [FILE] is given, the file is (newly) edited.\r\n    I.e. if you open a mbox, mark all items as read and then want to \r\n    browse the file again, you'll have to type>\r\n\r\n        :TMBoxBrowser! %\r\n\r\n    Alternatively, press <c-t> in the list view to show\/hide read mails.\r\n\r\n:TMBoxSelect[!]\r\n    Show a list of mbox files (as defined in g:tmboxbrowser_path). \r\n    Open a mbox & call :TMBoxBrowser.\r\n\r\n\r\nKey maps\r\nThese are effective in the __MBOX_Browser__ window:\r\n\r\n    i        ... Display the index list (in gvim, you can also use <esc>)\r\n    p        ... Select parts or re-view mail\r\n    q        ... Quit the browser\r\n    ?        ... Help\r\n    <space>  ... Page down\r\n    <bs>     ... Page up\r\n","install_details":"After installation:\r\n    0. Check the values of:\r\n        - g:tmboxbrowser_attachments_dir\r\n        - g:tmboxbrowser_datadir\r\n        - g:tmboxbrowser_path\r\n    1. Open an mbox file\r\n    2. Type :TMboxBrowser<cr>\r\n\r\nRequirements\r\n    tlib (vimscript#1863) is required.\r\n\r\n\r\nAlso available via git\r\nhttp:\/\/github.com\/tomtom\/vimtlib\/tree\/master\r\n","5":"After installation:\r\n    0. Check the values of:\r\n        - g:tmboxbrowser_attachments_dir\r\n        - g:tmboxbrowser_datadir\r\n        - g:tmboxbrowser_path\r\n    1. Open an mbox file\r\n    2. Type :TMboxBrowser<cr>\r\n\r\nRequirements\r\n    tlib (vimscript#1863) is required.\r\n\r\n\r\nAlso available via git\r\nhttp:\/\/github.com\/tomtom\/vimtlib\/tree\/master\r\n","first_name":"Tom","6":"Tom","last_name":"Link","7":"Link","releases":[{"0":"1906","vim_version":"7.0","1":"7.0","script_version":"0.3","2":"0.3","version_comment":"- Require tlib 0.10\r\n- FIX: Problem with scratch related functions\r\n","3":"- Require tlib 0.10\r\n- FIX: Problem with scratch related functions\r\n","package":"tmboxbrowser.vba.gz","4":"tmboxbrowser.vba.gz","src_id":"7381","5":"7381","creation_date":"1184761403","6":"1184761403"},{"0":"1906","vim_version":"7.0","1":"7.0","script_version":"0.2","2":"0.2","version_comment":"- Show all mails if there are no unread mails.\r\n- Require tlib 0.9\r\n","3":"- Show all mails if there are no unread mails.\r\n- Require tlib 0.9\r\n","package":"tmboxbrowser.vba.gz","4":"tmboxbrowser.vba.gz","src_id":"7363","5":"7363","creation_date":"1184663239","6":"1184663239"},{"0":"1906","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"tmboxbrowser.vba.gz","4":"tmboxbrowser.vba.gz","src_id":"7158","5":"7158","creation_date":"1179917267","6":"1179917267"}]},"1905":{"script_id":"1905","0":"1905","script_name":"camelcasemotion","1":"camelcasemotion","script_type":"utility","2":"utility","summary":"Motion through CamelCaseWords and underscore_notation.","3":"Motion through CamelCaseWords and underscore_notation.","description":"DESCRIPTION\r\nVim provides many built-in motions, e.g. to move to the next word, or end of\r\nthe current word. Most programming languages use either CamelCase\r\n(\"anIdentifier\") or underscore_notation (\"an_identifier\") naming conventions\r\nfor identifiers. The best way to navigate inside those identifiers using Vim\r\nbuilt-in motions is the [count]f{char} motion, i.e. f{uppercase-char} or f_,\r\nrespectively. But we can make this easier:\r\n\r\nThis plugin defines motions ,w ,b and ,e (similar to w b e), which do\r\nnot move word-wise (forward\/backward), but Camel-wise; i.e. to word boundaries\r\nand uppercase letters. The motions also work on underscore notation, where\r\nwords are delimited by underscore ('_') characters. From here on, both\r\nCamelCase and underscore_notation entities are referred to as \"words\" (in\r\ndouble quotes). Just like with the regular motions, a [count] can be prepended\r\nto move over multiple \"words\" at once. Outside of \"words\" (e.g. in non-keyword\r\ncharacters like \/\/ or ;), the new motions move just like the regular motions.\r\n\r\nVim provides a built-in iw text object called 'inner word', which works in\r\noperator-pending and visual mode. Analog to that, this plugin defines inner\r\n\"word\" text objects i,w i,b and i,e, which select the \"word\" (or\r\nmultiple \"words\" if a [count] is given) where the cursor is located.\r\n\r\nSOURCE\r\nBased on vimtip #1016 by Anthony Van Ham\r\n    http:\/\/vim.wikia.com\/wiki\/Moving_through_camel_case_words\r\n\r\nSEE ALSO\r\n- CamelCaseComplete (vimscript #3915) provides insert mode completion that\r\n  expands CamelCaseWords and underscore_words based on anchor characters for\r\n  each word fragment.\r\n\r\nRELATED WORKS\r\n- mlessnau_case (vimscript #4641) provides sort-of text objects vic, dic, cic,\r\n  but it seems to use a simplistic regexp for selection.\r\n- txtobj-underscore (https:\/\/github.com\/lucapette\/vim-textobj-underscore) uses\r\n  vim-textobj-user to define a_ and i_ text objects.\r\n\r\nUSAGE\r\nUse the new motions ,w ,b and ,e in normal mode, operator-pending mode\r\n(cp. operator), and visual mode. For example, type bc,w to change \"Camel\"\r\nin \"CamelCase\" to something else.\r\n\r\nEXAMPLE\r\nGiven the following CamelCase identifiers in a source code fragment:\r\n    set Script31337PathAndNameWithoutExtension11=%~dpn0\r\n    set Script31337PathANDNameWITHOUTExtension11=%~dpn0\r\nand the corresponding identifiers in underscore_notation:\r\n    set script_31337_path_and_name_without_extension_11=%~dpn0\r\n    set SCRIPT_31337_PATH_AND_NAME_WITHOUT_EXTENSION_11=%~dpn0\r\n\r\n,w moves to ([x] is cursor position): [s]et, [s]cript, [3]1337, [p]ath,\r\n    [a]nd, [n]ame, [w]ithout, [e]xtension, [1]1, [d]pn0, dpn[0], [s]et\r\n,b moves to: [d]pn0, [1]1, [e]xtension, [w]ithout, ...\r\n,e moves to: se[t], scrip[t], 3133[7], pat[h], an[d], nam[e], withou[t],\r\n    extensio[n], 1[1], dpn[0]\r\n\r\nTEXT OBJECTS\r\ni,w                 \"inner \"word\" forward\", select [count] \"words\", including\r\n                    the _ separator in underscore_notation\r\ni,b                 \"inner \"word\" backward\", select [count] \"words\" from the\r\n                    cursor position to the left, excluding the _ separator in\r\n                    underscore_notation\r\ni,e                 \"inner to the end of \"word\"\", select [count] \"words\",\r\n                    excluding the _ separator in underscore_notation\r\n\r\n                    Inside CamelWords, there is no difference between i,w\r\n                    and i,e. Unless [count] is larger than 1, i,b and\r\n                    i,e are identical.\r\nEXAMPLE\r\nGiven the following identifier, with the cursor positioned at [x]:\r\n    script_31337_path_and_na[m]e_without_extension_11\r\n\r\nv3i,w selects script_31337_path_and_[name_without_extension_]11\r\nv3i,b selects script_31337_[path_and_name]_without_extension_11\r\nv3i,e selects script_31337_path_and_[name_without_extension]_11\r\nInstead of visual mode, you can also use c3i,w to change, d3i,w to delete,\r\ngU3i,w to upper-case, and so on.\r\n\r\nBOUNDARIES\r\nAll the normal word boundaries of the w, b, and e motions apply here as\r\nwell: whitespace, sequences of keyword characters and non-keyword-characters.\r\nBoundaries between underscore_notation are defined by the \"_\" character.\r\nA new CamelWord starts with an uppercase letter (\"Camel\", \"ACRONYM\", \"C####\")\r\nor a number (\"123\", \"42foo#bar\").","4":"DESCRIPTION\r\nVim provides many built-in motions, e.g. to move to the next word, or end of\r\nthe current word. Most programming languages use either CamelCase\r\n(\"anIdentifier\") or underscore_notation (\"an_identifier\") naming conventions\r\nfor identifiers. The best way to navigate inside those identifiers using Vim\r\nbuilt-in motions is the [count]f{char} motion, i.e. f{uppercase-char} or f_,\r\nrespectively. But we can make this easier:\r\n\r\nThis plugin defines motions ,w ,b and ,e (similar to w b e), which do\r\nnot move word-wise (forward\/backward), but Camel-wise; i.e. to word boundaries\r\nand uppercase letters. The motions also work on underscore notation, where\r\nwords are delimited by underscore ('_') characters. From here on, both\r\nCamelCase and underscore_notation entities are referred to as \"words\" (in\r\ndouble quotes). Just like with the regular motions, a [count] can be prepended\r\nto move over multiple \"words\" at once. Outside of \"words\" (e.g. in non-keyword\r\ncharacters like \/\/ or ;), the new motions move just like the regular motions.\r\n\r\nVim provides a built-in iw text object called 'inner word', which works in\r\noperator-pending and visual mode. Analog to that, this plugin defines inner\r\n\"word\" text objects i,w i,b and i,e, which select the \"word\" (or\r\nmultiple \"words\" if a [count] is given) where the cursor is located.\r\n\r\nSOURCE\r\nBased on vimtip #1016 by Anthony Van Ham\r\n    http:\/\/vim.wikia.com\/wiki\/Moving_through_camel_case_words\r\n\r\nSEE ALSO\r\n- CamelCaseComplete (vimscript #3915) provides insert mode completion that\r\n  expands CamelCaseWords and underscore_words based on anchor characters for\r\n  each word fragment.\r\n\r\nRELATED WORKS\r\n- mlessnau_case (vimscript #4641) provides sort-of text objects vic, dic, cic,\r\n  but it seems to use a simplistic regexp for selection.\r\n- txtobj-underscore (https:\/\/github.com\/lucapette\/vim-textobj-underscore) uses\r\n  vim-textobj-user to define a_ and i_ text objects.\r\n\r\nUSAGE\r\nUse the new motions ,w ,b and ,e in normal mode, operator-pending mode\r\n(cp. operator), and visual mode. For example, type bc,w to change \"Camel\"\r\nin \"CamelCase\" to something else.\r\n\r\nEXAMPLE\r\nGiven the following CamelCase identifiers in a source code fragment:\r\n    set Script31337PathAndNameWithoutExtension11=%~dpn0\r\n    set Script31337PathANDNameWITHOUTExtension11=%~dpn0\r\nand the corresponding identifiers in underscore_notation:\r\n    set script_31337_path_and_name_without_extension_11=%~dpn0\r\n    set SCRIPT_31337_PATH_AND_NAME_WITHOUT_EXTENSION_11=%~dpn0\r\n\r\n,w moves to ([x] is cursor position): [s]et, [s]cript, [3]1337, [p]ath,\r\n    [a]nd, [n]ame, [w]ithout, [e]xtension, [1]1, [d]pn0, dpn[0], [s]et\r\n,b moves to: [d]pn0, [1]1, [e]xtension, [w]ithout, ...\r\n,e moves to: se[t], scrip[t], 3133[7], pat[h], an[d], nam[e], withou[t],\r\n    extensio[n], 1[1], dpn[0]\r\n\r\nTEXT OBJECTS\r\ni,w                 \"inner \"word\" forward\", select [count] \"words\", including\r\n                    the _ separator in underscore_notation\r\ni,b                 \"inner \"word\" backward\", select [count] \"words\" from the\r\n                    cursor position to the left, excluding the _ separator in\r\n                    underscore_notation\r\ni,e                 \"inner to the end of \"word\"\", select [count] \"words\",\r\n                    excluding the _ separator in underscore_notation\r\n\r\n                    Inside CamelWords, there is no difference between i,w\r\n                    and i,e. Unless [count] is larger than 1, i,b and\r\n                    i,e are identical.\r\nEXAMPLE\r\nGiven the following identifier, with the cursor positioned at [x]:\r\n    script_31337_path_and_na[m]e_without_extension_11\r\n\r\nv3i,w selects script_31337_path_and_[name_without_extension_]11\r\nv3i,b selects script_31337_[path_and_name]_without_extension_11\r\nv3i,e selects script_31337_path_and_[name_without_extension]_11\r\nInstead of visual mode, you can also use c3i,w to change, d3i,w to delete,\r\ngU3i,w to upper-case, and so on.\r\n\r\nBOUNDARIES\r\nAll the normal word boundaries of the w, b, and e motions apply here as\r\nwell: whitespace, sequences of keyword characters and non-keyword-characters.\r\nBoundaries between underscore_notation are defined by the \"_\" character.\r\nA new CamelWord starts with an uppercase letter (\"Camel\", \"ACRONYM\", \"C####\")\r\nor a number (\"123\", \"42foo#bar\").","install_details":"INSTALLATION\r\nThis script is packaged as a vimball. If you have the \"gunzip\" decompressor\r\nin your PATH, simply edit the *.vba.gz package in Vim; otherwise, decompress\r\nthe archive first, e.g. using WinZip. Inside Vim, install by sourcing the\r\nvimball or via the :UseVimball command.\r\n    vim camelcasemotion.vba.gz\r\n    :so %\r\nTo uninstall, use the :RmVimball command.\r\n\r\nDEPENDENCIES\r\n- Requires Vim 7.0 or higher.\r\n\r\nCONFIGURATION\r\nFor a permanent configuration, put the following commands into your vimrc:\r\n\r\nThere's a special case dating back to vi that cw does not include the\r\nwhitespace after a word; it works like ce. If you want the same special case\r\nfor the c,w motion and ciw text object, define the following additional\r\nmapping:\r\n    nmap c,w c,e\r\nLikewise, the iw text object does not include trailing whitespace. If you\r\nwant the camelcasemotion text objects behave the same way, add:\r\n    \" Must define the default mappings first in order to change them.\r\n    runtime plugin\/camelcasemotion.vim\r\n    omap i,w i,e\r\n    xmap i,w i,e\r\nIf you're using different mappings (see below), you need to adapt the\r\narguments, naturally.\r\n\r\nBy default, all mappings start with , (comma) as the map leader instead of\r\nusing <Leader>. I personally find the default <Leader> key too far off the\r\nkeyboard to be useful for custom motions (which also cannot be repeated via\r\nthe . (dot) command, so they should be very fast to type repeatedly), but\r\nquite suitable for general, less frequently used custom mappings.\r\nTo avoid losing the (rarely used) , mapping (which repeats latest f, t, F or\r\nT in opposite direction), you can remap it to ,,:\r\n    nnoremap ,, ,\r\n    xnoremap ,, ,\r\n    onoremap ,, ,\r\n\r\nIf you want to use different mappings, map your keys to the\r\n<Plug>CamelCaseMotion_? mapping targets _before_ sourcing the script (e.g. in\r\nyour vimrc).\r\n\r\nEXAMPLE: Replace the default w, b and e mappings instead of defining\r\nadditional mappings ,w, ,b  and ,e :\r\n    map w <Plug>CamelCaseMotion_w\r\n    map b <Plug>CamelCaseMotion_b\r\n    map e <Plug>CamelCaseMotion_e\r\n    sunmap w\r\n    sunmap b\r\n    sunmap e\r\nIn this case, you probably want to restore the special camelcasemotion-c,w\r\nbehavior, too:\r\n    nmap cw ce\r\nFor consistency, the i_CTRL-W command probably should observe the word\r\nfragments, too. This is a simplistic attempt:\r\n    imap <C-w> <C-o>d<Plug>CamelCaseMotion_ie\r\nBut it fails when inside a word or with trailing whitespace.\r\n\r\nEXAMPLE: Replace default iw text-object and define analog ib and  ie\r\nmotions:\r\n    omap iw <Plug>CamelCaseMotion_iw\r\n    xmap iw <Plug>CamelCaseMotion_iw\r\n    omap ib <Plug>CamelCaseMotion_ib\r\n    xmap ib <Plug>CamelCaseMotion_ib\r\n    omap ie <Plug>CamelCaseMotion_ie\r\n    xmap ie <Plug>CamelCaseMotion_ie\r\nIn this case, you probably want to restore the special camelcasemotion-c,w\r\nbehavior, too:\r\n    \" Must define the default mappings first in order to change them.\r\n    runtime plugin\/camelcasemotion.vim\r\n    omap iw ie\r\n    xmap iw ie","5":"INSTALLATION\r\nThis script is packaged as a vimball. If you have the \"gunzip\" decompressor\r\nin your PATH, simply edit the *.vba.gz package in Vim; otherwise, decompress\r\nthe archive first, e.g. using WinZip. Inside Vim, install by sourcing the\r\nvimball or via the :UseVimball command.\r\n    vim camelcasemotion.vba.gz\r\n    :so %\r\nTo uninstall, use the :RmVimball command.\r\n\r\nDEPENDENCIES\r\n- Requires Vim 7.0 or higher.\r\n\r\nCONFIGURATION\r\nFor a permanent configuration, put the following commands into your vimrc:\r\n\r\nThere's a special case dating back to vi that cw does not include the\r\nwhitespace after a word; it works like ce. If you want the same special case\r\nfor the c,w motion and ciw text object, define the following additional\r\nmapping:\r\n    nmap c,w c,e\r\nLikewise, the iw text object does not include trailing whitespace. If you\r\nwant the camelcasemotion text objects behave the same way, add:\r\n    \" Must define the default mappings first in order to change them.\r\n    runtime plugin\/camelcasemotion.vim\r\n    omap i,w i,e\r\n    xmap i,w i,e\r\nIf you're using different mappings (see below), you need to adapt the\r\narguments, naturally.\r\n\r\nBy default, all mappings start with , (comma) as the map leader instead of\r\nusing <Leader>. I personally find the default <Leader> key too far off the\r\nkeyboard to be useful for custom motions (which also cannot be repeated via\r\nthe . (dot) command, so they should be very fast to type repeatedly), but\r\nquite suitable for general, less frequently used custom mappings.\r\nTo avoid losing the (rarely used) , mapping (which repeats latest f, t, F or\r\nT in opposite direction), you can remap it to ,,:\r\n    nnoremap ,, ,\r\n    xnoremap ,, ,\r\n    onoremap ,, ,\r\n\r\nIf you want to use different mappings, map your keys to the\r\n<Plug>CamelCaseMotion_? mapping targets _before_ sourcing the script (e.g. in\r\nyour vimrc).\r\n\r\nEXAMPLE: Replace the default w, b and e mappings instead of defining\r\nadditional mappings ,w, ,b  and ,e :\r\n    map w <Plug>CamelCaseMotion_w\r\n    map b <Plug>CamelCaseMotion_b\r\n    map e <Plug>CamelCaseMotion_e\r\n    sunmap w\r\n    sunmap b\r\n    sunmap e\r\nIn this case, you probably want to restore the special camelcasemotion-c,w\r\nbehavior, too:\r\n    nmap cw ce\r\nFor consistency, the i_CTRL-W command probably should observe the word\r\nfragments, too. This is a simplistic attempt:\r\n    imap <C-w> <C-o>d<Plug>CamelCaseMotion_ie\r\nBut it fails when inside a word or with trailing whitespace.\r\n\r\nEXAMPLE: Replace default iw text-object and define analog ib and  ie\r\nmotions:\r\n    omap iw <Plug>CamelCaseMotion_iw\r\n    xmap iw <Plug>CamelCaseMotion_iw\r\n    omap ib <Plug>CamelCaseMotion_ib\r\n    xmap ib <Plug>CamelCaseMotion_ib\r\n    omap ie <Plug>CamelCaseMotion_ie\r\n    xmap ie <Plug>CamelCaseMotion_ie\r\nIn this case, you probably want to restore the special camelcasemotion-c,w\r\nbehavior, too:\r\n    \" Must define the default mappings first in order to change them.\r\n    runtime plugin\/camelcasemotion.vim\r\n    omap iw ie\r\n    xmap iw ie","first_name":"Ingo","6":"Ingo","last_name":"Karkat","7":"Karkat","releases":[{"0":"1905","vim_version":"7.0","1":"7.0","script_version":"1.52","2":"1.52","version_comment":"- FIX: Correct forward-to-end motion over lowercase part in \"lowerCamel\". Found this by chance in GitHub fork by Kevin Lee (bkad). \r\n- BUG: Correct wrong stop on second letter of ACRONYM at the beginning of a word \"AXBCText\". \r\n- The motion functionality is automatically tested via a runVimTests (vimscript #2565) test suite. ","3":"- FIX: Correct forward-to-end motion over lowercase part in \"lowerCamel\". Found this by chance in GitHub fork by Kevin Lee (bkad). \r\n- BUG: Correct wrong stop on second letter of ACRONYM at the beginning of a word \"AXBCText\". \r\n- The motion functionality is automatically tested via a runVimTests (vimscript #2565) test suite. ","package":"camelcasemotion.vba.gz","4":"camelcasemotion.vba.gz","src_id":"16854","5":"16854","creation_date":"1321101780","6":"1321101780"},{"0":"1905","vim_version":"7.0","1":"7.0","script_version":"1.50","2":"1.50","version_comment":"- Do not create mappings for select mode; according to|Select-mode|, printable\r\n  character commands should delete the selection and insert the typed\r\n  characters. Now using :xmap to only target visual mode. \r\n- Moved functions from plugin to separate autoload script. \r\n- Split off documentation into separate help file. Now packaging as VimBall. ","3":"- Do not create mappings for select mode; according to|Select-mode|, printable\r\n  character commands should delete the selection and insert the typed\r\n  characters. Now using :xmap to only target visual mode. \r\n- Moved functions from plugin to separate autoload script. \r\n- Split off documentation into separate help file. Now packaging as VimBall. ","package":"camelcasemotion.vba.gz","4":"camelcasemotion.vba.gz","src_id":"10530","5":"10530","creation_date":"1241530345","6":"1241530345"},{"0":"1905","vim_version":"7.0","1":"7.0","script_version":"1.40.017","2":"1.40.017","version_comment":"BF: Now using :normal! to be independent from any user mappings. Thanks to Neil Walker for the patch.","3":"BF: Now using :normal! to be independent from any user mappings. Thanks to Neil Walker for the patch.","package":"camelcasemotion.vim","4":"camelcasemotion.vim","src_id":"8708","5":"8708","creation_date":"1211188861","6":"1211188861"},{"0":"1905","vim_version":"7.0","1":"7.0","script_version":"1.40.016","2":"1.40.016","version_comment":"BF: Wrong forward motion stop at the second digit if a word starts with multiple numbers (e.g. 1234.56789). Thanks to Wasim Ahmed for reporting this. ","3":"BF: Wrong forward motion stop at the second digit if a word starts with multiple numbers (e.g. 1234.56789). Thanks to Wasim Ahmed for reporting this. ","package":"camelcasemotion.vim","4":"camelcasemotion.vim","src_id":"8612","5":"8612","creation_date":"1209372894","6":"1209372894"},{"0":"1905","vim_version":"7.0","1":"7.0","script_version":"1.40.015","2":"1.40.015","version_comment":"ENH: Added inner \"word\" text objects 'i,w' etc. that work analoguous to the built-in 'iw' text object. Thanks to David Kotchan for this suggestion. ","3":"ENH: Added inner \"word\" text objects 'i,w' etc. that work analoguous to the built-in 'iw' text object. Thanks to David Kotchan for this suggestion. ","package":"camelcasemotion.vim","4":"camelcasemotion.vim","src_id":"8599","5":"8599","creation_date":"1209007291","6":"1209007291"},{"0":"1905","vim_version":"7.0","1":"7.0","script_version":"1.30.014","2":"1.30.014","version_comment":"The motions now also stop at non-keyword boundaries, just like the regular motions. This has no effect inside a CamelCaseWord or inside underscore_notation, but it makes the motions behave like the regular motions (which is important if you replace the default motions). Thanks to Mun Johl for reporting this. ","3":"The motions now also stop at non-keyword boundaries, just like the regular motions. This has no effect inside a CamelCaseWord or inside underscore_notation, but it makes the motions behave like the regular motions (which is important if you replace the default motions). Thanks to Mun Johl for reporting this. ","package":"camelcasemotion.vim","4":"camelcasemotion.vim","src_id":"8587","5":"8587","creation_date":"1208733243","6":"1208733243"},{"0":"1905","vim_version":"7.0","1":"7.0","script_version":"1.30.013","2":"1.30.013","version_comment":"Allowing users to use mappings different than ,w ,b ,e by defining <Plug>CamelCaseMotion_? target mappings. This can even be used to replace the default 'w', 'b' and 'e' mappings, as suggested by Mun Johl. \r\nNow requires VIM 7.0 or higher. ","3":"Allowing users to use mappings different than ,w ,b ,e by defining <Plug>CamelCaseMotion_? target mappings. This can even be used to replace the default 'w', 'b' and 'e' mappings, as suggested by Mun Johl. \r\nNow requires VIM 7.0 or higher. ","package":"camelcasemotion.vim","4":"camelcasemotion.vim","src_id":"8536","5":"8536","creation_date":"1207701054","6":"1207701054"},{"0":"1905","vim_version":"6.0","1":"6.0","script_version":"1.20.012","2":"1.20.012","version_comment":"BF: Corrected motions through mixed CamelCase_and_UnderScore words by re-ordering and narrowing the search patterns.  ","3":"BF: Corrected motions through mixed CamelCase_and_UnderScore words by re-ordering and narrowing the search patterns.  ","package":"camelcasemotion.vim","4":"camelcasemotion.vim","src_id":"7210","5":"7210","creation_date":"1181093517","6":"1181093517"},{"0":"1905","vim_version":"6.0","1":"6.0","script_version":"1.20.011","2":"1.20.011","version_comment":"Thanks again to Joseph Barker for discussing the complicated visual mode mapping on the vim-dev mailing list and coming up with a great simplification. ","3":"Thanks again to Joseph Barker for discussing the complicated visual mode mapping on the vim-dev mailing list and coming up with a great simplification. ","package":"camelcasemotion.vim","4":"camelcasemotion.vim","src_id":"7189","5":"7189","creation_date":"1180743381","6":"1180743381"},{"0":"1905","vim_version":"6.0","1":"6.0","script_version":"1.20.010","2":"1.20.010","version_comment":"ENH: The visual mode motions now also (mostly) work with the (default) setting 'set selection=inclusive' \/ 'behave xterm', instead of selecting one character too much. So far, you had to 'set selection=exclusive' \/ 'behave mswin'. ","3":"ENH: The visual mode motions now also (mostly) work with the (default) setting 'set selection=inclusive' \/ 'behave xterm', instead of selecting one character too much. So far, you had to 'set selection=exclusive' \/ 'behave mswin'. ","package":"camelcasemotion.vim","4":"camelcasemotion.vim","src_id":"7177","5":"7177","creation_date":"1180494928","6":"1180494928"},{"0":"1905","vim_version":"6.0","1":"6.0","script_version":"1.10.009","2":"1.10.009","version_comment":"Incorporated major improvements and simplifications done by Joseph Barker:\r\nOperator-pending and visual mode motions now accept [count] of more than 9. \r\nVisual selections can now be extended from either end. \r\nInstead of misusing the :[range], the special variable v:count1 is used. Custom commands are not needed anymore. \r\nOperator-pending and visual mode mappings are now generic: There's only a single mapping for ,w that can be repeated, rather than having a separate mapping for 1,w 2,w 3,w ...\r\nBF: The operator-pending and visual mode ,e mapping doesn't work properly when it reaches the end of line; the final character of the moved-over \"word\" remains. Fixed this problem unless the \"word\" is at the very end of the buffer. \r\nBF: Degenerate CamelCaseWords that consist of only a single uppercase letter (e.g. \"P\" in \"MapPRoblem\") are skipped by all motions. Thanks to Joseph Barker for reporting this. \r\nBF: In CamelCaseWords that consist of uppercase letters followed by decimals (e.g. \"MyUPPER123Problem\", the uppercase \"word\" is skipped by all motions. ","3":"Incorporated major improvements and simplifications done by Joseph Barker:\r\nOperator-pending and visual mode motions now accept [count] of more than 9. \r\nVisual selections can now be extended from either end. \r\nInstead of misusing the :[range], the special variable v:count1 is used. Custom commands are not needed anymore. \r\nOperator-pending and visual mode mappings are now generic: There's only a single mapping for ,w that can be repeated, rather than having a separate mapping for 1,w 2,w 3,w ...\r\nBF: The operator-pending and visual mode ,e mapping doesn't work properly when it reaches the end of line; the final character of the moved-over \"word\" remains. Fixed this problem unless the \"word\" is at the very end of the buffer. \r\nBF: Degenerate CamelCaseWords that consist of only a single uppercase letter (e.g. \"P\" in \"MapPRoblem\") are skipped by all motions. Thanks to Joseph Barker for reporting this. \r\nBF: In CamelCaseWords that consist of uppercase letters followed by decimals (e.g. \"MyUPPER123Problem\", the uppercase \"word\" is skipped by all motions. ","package":"camelcasemotion.vim","4":"camelcasemotion.vim","src_id":"7176","5":"7176","creation_date":"1180494358","6":"1180494358"},{"0":"1905","vim_version":"6.0","1":"6.0","script_version":"1.00.007","2":"1.00.007","version_comment":"Initial upload","3":"Initial upload","package":"camelcasemotion.vim","4":"camelcasemotion.vim","src_id":"7152","5":"7152","creation_date":"1179800298","6":"1179800298"}]},"1904":{"script_id":"1904","0":"1904","script_name":"ReloadScript","1":"ReloadScript","script_type":"utility","2":"utility","summary":"Reload a Vim script during script development.","3":"Reload a Vim script during script development.","description":"DESCRIPTION\r\nRe-sources a Vim script. The script may use a multiple inclusion guard\r\nvariable g:loaded_{scriptname} (with {scriptname} having either the same case\r\nas specified or all lowercase.)\r\nIf you specify the bare scriptname (without .vim extension), the script must\r\nreside in plugin\/{scriptname}.vim somewhere on 'runtimepath'. Otherwise, the\r\npassed filespec is interpreted as the file system location of a Vim script and\r\nsourced as-is. If you execute :ReloadScript without passing a scriptname,\r\nthe current buffer is re-sourced.\r\n\r\nRELATED WORKS\r\n- scriptease.vim (vimscript #4394) has a :Runtime command that unlets any\r\n  include guards first\r\n\r\nUSAGE\r\nReloadScript                            Re-sources the current buffer.\r\nReloadScript {scriptname}               Re-sources the passed plugin script.\r\nReloadScript {path\/to\/script.vim}       Re-sources the passed file.","4":"DESCRIPTION\r\nRe-sources a Vim script. The script may use a multiple inclusion guard\r\nvariable g:loaded_{scriptname} (with {scriptname} having either the same case\r\nas specified or all lowercase.)\r\nIf you specify the bare scriptname (without .vim extension), the script must\r\nreside in plugin\/{scriptname}.vim somewhere on 'runtimepath'. Otherwise, the\r\npassed filespec is interpreted as the file system location of a Vim script and\r\nsourced as-is. If you execute :ReloadScript without passing a scriptname,\r\nthe current buffer is re-sourced.\r\n\r\nRELATED WORKS\r\n- scriptease.vim (vimscript #4394) has a :Runtime command that unlets any\r\n  include guards first\r\n\r\nUSAGE\r\nReloadScript                            Re-sources the current buffer.\r\nReloadScript {scriptname}               Re-sources the passed plugin script.\r\nReloadScript {path\/to\/script.vim}       Re-sources the passed file.","install_details":"INSTALLATION\r\nThis script is packaged as a vimball. If you have the \"gunzip\" decompressor\r\nin your PATH, simply edit the *.vmb.gz package in Vim; otherwise, decompress\r\nthe archive first, e.g. using WinZip. Inside Vim, install by sourcing the\r\nvimball or via the :UseVimball command.\r\n    vim ReloadScript*.vmb.gz\r\n    :so %\r\nTo uninstall, use the :RmVimball command.\r\n\r\nDEPENDENCIES\r\n- Requires Vim 7.0 or higher. ","5":"INSTALLATION\r\nThis script is packaged as a vimball. If you have the \"gunzip\" decompressor\r\nin your PATH, simply edit the *.vmb.gz package in Vim; otherwise, decompress\r\nthe archive first, e.g. using WinZip. Inside Vim, install by sourcing the\r\nvimball or via the :UseVimball command.\r\n    vim ReloadScript*.vmb.gz\r\n    :so %\r\nTo uninstall, use the :RmVimball command.\r\n\r\nDEPENDENCIES\r\n- Requires Vim 7.0 or higher. ","first_name":"Ingo","6":"Ingo","last_name":"Karkat","7":"Karkat","releases":[{"0":"1904","vim_version":"7.0","1":"7.0","script_version":"1.21","2":"1.21","version_comment":"- Avoid <f-args> because of its unescaping behavior.\r\n- Also no global inclusion guard for ftdetect scripts.","3":"- Avoid <f-args> because of its unescaping behavior.\r\n- Also no global inclusion guard for ftdetect scripts.","package":"ReloadScript-1.21.vmb.gz","4":"ReloadScript-1.21.vmb.gz","src_id":"18503","5":"18503","creation_date":"1346154131","6":"1346154131"},{"0":"1904","vim_version":"7.0","1":"7.0","script_version":"1.20","2":"1.20","version_comment":"- BUG: Avoiding \"E471: Argument required\" error on empty buffer name. \r\n- ENH: Explicitly checking for the existence of the file, as we don't want to put the :source command inside try...catch (it would stop showing all resulting errors and show only the first), and because :runtime doesn't complain at all. \r\n- Added separate help file and packaging the plugin as a vimball. ","3":"- BUG: Avoiding \"E471: Argument required\" error on empty buffer name. \r\n- ENH: Explicitly checking for the existence of the file, as we don't want to put the :source command inside try...catch (it would stop showing all resulting errors and show only the first), and because :runtime doesn't complain at all. \r\n- Added separate help file and packaging the plugin as a vimball. ","package":"ReloadScript.vba.gz","4":"ReloadScript.vba.gz","src_id":"14715","5":"14715","creation_date":"1294602678","6":"1294602678"},{"0":"1904","vim_version":"7.0","1":"7.0","script_version":"1.10.005","2":"1.10.005","version_comment":"Combined missing inclusion guard warning with reload message to avoid the \"Hit ENTER\" prompt. \r\nNo missing inclusion guard warning for scripts that do not need one (e.g. after-directory, autoload, ftplugin, indent, syntax, ...)","3":"Combined missing inclusion guard warning with reload message to avoid the \"Hit ENTER\" prompt. \r\nNo missing inclusion guard warning for scripts that do not need one (e.g. after-directory, autoload, ftplugin, indent, syntax, ...)","package":"ReloadScript.vim","4":"ReloadScript.vim","src_id":"9038","5":"9038","creation_date":"1217316016","6":"1217316016"},{"0":"1904","vim_version":"7.0","1":"7.0","script_version":"1.10.004","2":"1.10.004","version_comment":"A scriptname argument with path and\/or extension is sourced as-is. This allows a third usage: :ReloadScript path\/to\/script.vim","3":"A scriptname argument with path and\/or extension is sourced as-is. This allows a third usage: :ReloadScript path\/to\/script.vim","package":"ReloadScript.vim","4":"ReloadScript.vim","src_id":"8360","5":"8360","creation_date":"1204188833","6":"1204188833"},{"0":"1904","vim_version":"7.0","1":"7.0","script_version":"1.00.003","2":"1.00.003","version_comment":"Initial upload","3":"Initial upload","package":"ReloadScript.vim","4":"ReloadScript.vim","src_id":"7150","5":"7150","creation_date":"1179798462","6":"1179798462"}]},"1903":{"script_id":"1903","0":"1903","script_name":":REPL","1":":REPL","script_type":"utility","2":"utility","summary":"Prompt-driven replace(substitute) for console vim, also in multiple files.","3":"Prompt-driven replace(substitute) for console vim, also in multiple files.","description":"\" This script defines command REPL which is prompt-driven. REPL \r\n\" command does not take arguments. It prompts for:\r\n\" 1) string to replace. You can use * here for current word under cursor,\r\n\"    \/ for current search pattern. Simply Enter means current search pattern, too.\r\n\" 2) string to repalce to. Empty string means empty string here.\r\n\" 3) Substitution flags:\r\n\"     (i) ignorecase (m) matchCase\r\n\"     (w) as word    (c) confirm    (f) in files\r\n\"    Default flags are 'mw' - match-case and whole-word substitution.\r\n\"\r\n\" If you include f in flags, you are additionally prompted for\r\n\" file patterns (space-separated). Examples: (1) *.c *.h (2)  **.[ch]\r\n\" '**' in file patterns means recursive file matching.\r\n\"\r\n\" Press Ctrl-C at any prompt to abort the script.\r\n\"\r\n\" That's all.\r\n\" Send bugs and wishes to: iler.ml@gmail.com\r\n\"\r\n\" Todo & wishes:\r\n\" - print \"No substitutions\" when there were no substitutions. Currently,\r\n\"   nothing is printed where nothing was substituted.\r\n\"\r\n\" Example dialog:\r\n\"  :REPL\r\n\"  Replace what > foo\r\n\"  Replace to   > bar\r\n\"   (i) ignorecase (m) matchCase\r\n\"   (w) as word    (c) confirm    (f) in files [mw]\r\n","4":"\" This script defines command REPL which is prompt-driven. REPL \r\n\" command does not take arguments. It prompts for:\r\n\" 1) string to replace. You can use * here for current word under cursor,\r\n\"    \/ for current search pattern. Simply Enter means current search pattern, too.\r\n\" 2) string to repalce to. Empty string means empty string here.\r\n\" 3) Substitution flags:\r\n\"     (i) ignorecase (m) matchCase\r\n\"     (w) as word    (c) confirm    (f) in files\r\n\"    Default flags are 'mw' - match-case and whole-word substitution.\r\n\"\r\n\" If you include f in flags, you are additionally prompted for\r\n\" file patterns (space-separated). Examples: (1) *.c *.h (2)  **.[ch]\r\n\" '**' in file patterns means recursive file matching.\r\n\"\r\n\" Press Ctrl-C at any prompt to abort the script.\r\n\"\r\n\" That's all.\r\n\" Send bugs and wishes to: iler.ml@gmail.com\r\n\"\r\n\" Todo & wishes:\r\n\" - print \"No substitutions\" when there were no substitutions. Currently,\r\n\"   nothing is printed where nothing was substituted.\r\n\"\r\n\" Example dialog:\r\n\"  :REPL\r\n\"  Replace what > foo\r\n\"  Replace to   > bar\r\n\"   (i) ignorecase (m) matchCase\r\n\"   (w) as word    (c) confirm    (f) in files [mw]\r\n","install_details":"Short instructions: drop script into your personal plugin\r\ndirectory (~\/.vim\/plugin)\r\n\r\nDetailed version:\r\n\r\n1. Download script  repl.vim  from the link below.\r\n2. Create directory ~\/.vim\/plugin if it does not exist:\r\n                 mkdir -p ~\/.vim\/plugin\r\n   (your personal plugin directory).\r\n3. Copy script  repl.vim  into ~\/.vim\/plugin directory.\r\n4. Restart vim\r\n","5":"Short instructions: drop script into your personal plugin\r\ndirectory (~\/.vim\/plugin)\r\n\r\nDetailed version:\r\n\r\n1. Download script  repl.vim  from the link below.\r\n2. Create directory ~\/.vim\/plugin if it does not exist:\r\n                 mkdir -p ~\/.vim\/plugin\r\n   (your personal plugin directory).\r\n3. Copy script  repl.vim  into ~\/.vim\/plugin directory.\r\n4. Restart vim\r\n","first_name":"Yakov","6":"Yakov","last_name":"Lerner","7":"Lerner","releases":[{"0":"1903","vim_version":"6.0","1":"6.0","script_version":"070521c","2":"070521c","version_comment":"Added optional autowrite in multi-file-replace. Checksum 1752632450","3":"Added optional autowrite in multi-file-replace. Checksum 1752632450","package":"repl.vim","4":"repl.vim","src_id":"7147","5":"7147","creation_date":"1179727815","6":"1179727815"}]},"1902":{"script_id":"1902","0":"1902","script_name":"skill_comment.vim","1":"skill_comment.vim","script_type":"ftplugin","2":"ftplugin","summary":"After pair of brackets auto-add starting keyword in the comment","3":"After pair of brackets auto-add starting keyword in the comment","description":"Vim filetype plugin enhancement\r\nLanguage: skill (cadence extension language)\r\n\r\nType \");\" in Insert mode to insert the word located before the matching \"(\".\r\nFor selected keywords this also adds the argument (following the keyword).\r\nTo work properly, keyword and argument must be found on the same line.\r\n\r\nExample:\r\n\r\nprocedure( vscCheckpointHier( @key lib cell view message inclibs )\r\n    let(( ddCVs )\r\n        vscPrint0(sprintf( nil \"Hierarchy for %s,%s,%s ...\" lib cell view ))\r\n        when( ddCVs = vscGetHierarchyDDs( ?lib lib ?cell cell ?view view\r\n                                          ?inclibs inclibs )\r\n            vscPrint0(sprintf( nil \"  %d cellviews.\" length(ddCVs) ))\r\n            vscCheckpoint( ddCVs ?message message)\r\n        ); when ddCVs\r\n    ); let\r\n); procedure vscCheckpointHier\r\n","4":"Vim filetype plugin enhancement\r\nLanguage: skill (cadence extension language)\r\n\r\nType \");\" in Insert mode to insert the word located before the matching \"(\".\r\nFor selected keywords this also adds the argument (following the keyword).\r\nTo work properly, keyword and argument must be found on the same line.\r\n\r\nExample:\r\n\r\nprocedure( vscCheckpointHier( @key lib cell view message inclibs )\r\n    let(( ddCVs )\r\n        vscPrint0(sprintf( nil \"Hierarchy for %s,%s,%s ...\" lib cell view ))\r\n        when( ddCVs = vscGetHierarchyDDs( ?lib lib ?cell cell ?view view\r\n                                          ?inclibs inclibs )\r\n            vscPrint0(sprintf( nil \"  %d cellviews.\" length(ddCVs) ))\r\n            vscCheckpoint( ddCVs ?message message)\r\n        ); when ddCVs\r\n    ); let\r\n); procedure vscCheckpointHier\r\n","install_details":"Copy the file to  ~\/.vim\/ftplugin  -- or  vimfiles\\ftplugin (Win)\r\n\r\nHow come ...?\r\nVim will detect that the script belongs to the skill filetype, because the\r\nfilename matches \"skill_*.vim\".\r\n\r\nMake sure your vimrc contains\r\n    filetype plugin on\r\nelse the script won't be loaded automatically.\r\n\r\n2007 Oct 10","5":"Copy the file to  ~\/.vim\/ftplugin  -- or  vimfiles\\ftplugin (Win)\r\n\r\nHow come ...?\r\nVim will detect that the script belongs to the skill filetype, because the\r\nfilename matches \"skill_*.vim\".\r\n\r\nMake sure your vimrc contains\r\n    filetype plugin on\r\nelse the script won't be loaded automatically.\r\n\r\n2007 Oct 10","first_name":"Andy","6":"Andy","last_name":"Wokula","7":"Wokula","releases":[{"0":"1902","vim_version":"7.0","1":"7.0","script_version":"4","2":"4","version_comment":"Initial upload","3":"Initial upload","package":"skill_comment.vim","4":"skill_comment.vim","src_id":"7138","5":"7138","creation_date":"1179417900","6":"1179417900"}]},"1901":{"script_id":"1901","0":"1901","script_name":"freefem.vim","1":"freefem.vim","script_type":"syntax","2":"syntax","summary":"FreeFEM++ Syntax File","3":"FreeFEM++ Syntax File","description":"This is the syntax file for FreeFEM++ opensource finite element oriented PDE solver:\r\n\r\nhttp:\/\/www.freefem.org","4":"This is the syntax file for FreeFEM++ opensource finite element oriented PDE solver:\r\n\r\nhttp:\/\/www.freefem.org","install_details":"Just untar the archive in your $HOME\/.vim directory.","5":"Just untar the archive in your $HOME\/.vim directory.","first_name":"David","6":"David","last_name":"Radice","7":"Radice","releases":[{"0":"1901","vim_version":"6.0","1":"6.0","script_version":"0.1.3","2":"0.1.3","version_comment":"Added the keywords for the FreeFEM++ MPI version.","3":"Added the keywords for the FreeFEM++ MPI version.","package":"edp-0.1.3.tar.gz","4":"edp-0.1.3.tar.gz","src_id":"9458","5":"9458","creation_date":"1226099402","6":"1226099402"},{"0":"1901","vim_version":"6.0","1":"6.0","script_version":"0.1.2","2":"0.1.2","version_comment":"Added the new commands introduced in FreeFEM++ version 2.17.","3":"Added the new commands introduced in FreeFEM++ version 2.17.","package":"edp-0.1.2.tar.gz","4":"edp-0.1.2.tar.gz","src_id":"7246","5":"7246","creation_date":"1181815365","6":"1181815365"},{"0":"1901","vim_version":"6.0","1":"6.0","script_version":"0.1.1","2":"0.1.1","version_comment":"Stripped the leading .vim directory in the tarball.","3":"Stripped the leading .vim directory in the tarball.","package":"edp.tar.gz","4":"edp.tar.gz","src_id":"7137","5":"7137","creation_date":"1179406334","6":"1179406334"}]},"1900":{"script_id":"1900","0":"1900","script_name":"ael.vim","1":"ael.vim","script_type":"syntax","2":"syntax","summary":"Syntax for Asterisk Extension Language (AEL)","3":"Syntax for Asterisk Extension Language (AEL)","description":"Includes highlighting for most of the basic structure of AEL files.","4":"Includes highlighting for most of the basic structure of AEL files.","install_details":"Place ael.vim in ~\/.vim\/syntax, and activate it with \":setf ael\" when editing an AEL file, or add the appropriate code to ~\/.vim\/filetype.vim.","5":"Place ael.vim in ~\/.vim\/syntax, and activate it with \":setf ael\" when editing an AEL file, or add the appropriate code to ~\/.vim\/filetype.vim.","first_name":"Chad","6":"Chad","last_name":"Wallace","7":"Wallace","releases":[{"0":"1900","vim_version":"6.0","1":"6.0","script_version":"0.3","2":"0.3","version_comment":"Tweaked treatment of Set, goto, macros and interpolation.  Added for and while loops.  Made semicolons optional after closing braces.  Added support for callerid on extensions.  Added support for multiline comments (thanks to Andrea Spadaccini).","3":"Tweaked treatment of Set, goto, macros and interpolation.  Added for and while loops.  Made semicolons optional after closing braces.  Added support for callerid on extensions.  Added support for multiline comments (thanks to Andrea Spadaccini).","package":"ael.vim","4":"ael.vim","src_id":"12203","5":"12203","creation_date":"1264642988","6":"1264642988"},{"0":"1900","vim_version":"6.0","1":"6.0","script_version":"0.2","2":"0.2","version_comment":"Added recognition of Set and other application calls, as well as $[] and ${} expressions.","3":"Added recognition of Set and other application calls, as well as $[] and ${} expressions.","package":"ael.vim","4":"ael.vim","src_id":"7188","5":"7188","creation_date":"1180712530","6":"1180712530"},{"0":"1900","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"ael.vim","4":"ael.vim","src_id":"7133","5":"7133","creation_date":"1179395675","6":"1179395675"}]},"1899":{"script_id":"1899","0":"1899","script_name":"FindFile","1":"FindFile","script_type":"utility","2":"utility","summary":"Open file quickly by using autocomplete","3":"Open file quickly by using autocomplete","description":"Somewhat similar to locate on Unix, FindFile allows you open a file quickly by typing in its file name.  You can use :FC to generate the cache of all files in a directory recursively, then using :FF will open a buffer that can autocomplete on the filenames that are cached.  Pressing <Enter> will open the file.  \r\n\r\nThis is a pure vim implementation and the cache is stored in memory using a vim dictionary.  It should work on both Windows and Unix.\r\n\r\nSee http:\/\/wlee.net\/FindFile.swf.html for details.","4":"Somewhat similar to locate on Unix, FindFile allows you open a file quickly by typing in its file name.  You can use :FC to generate the cache of all files in a directory recursively, then using :FF will open a buffer that can autocomplete on the filenames that are cached.  Pressing <Enter> will open the file.  \r\n\r\nThis is a pure vim implementation and the cache is stored in memory using a vim dictionary.  It should work on both Windows and Unix.\r\n\r\nSee http:\/\/wlee.net\/FindFile.swf.html for details.","install_details":"Put this file in your ~\/.vim\/plugin directory.\r\nIf you are working on a project, go to the root directory of the project,\r\nthen execute:\r\n\r\n    :FindFileCache .<CR>\r\n    or\r\n    :FC .<CR>\r\n\r\nThis will recursively parse the directory and create the internal cache.\r\n\r\nYou can also put in multiple arguments in :FC:\r\n\r\n    :FC \/dir1 \/dir2 \/dir3\r\n\r\nYou can add to the cache by calling :FC again.  File with the same path\r\nwill not be added to the cache twice.\r\n\r\nTo find a file:\r\n\r\n    :FindFile<CR>\r\n    or\r\n    :FF<CR>\r\n\r\nThis opens a scratch buffer that you can type in the file name.  Press\r\n<Esc> will quit the buffer, while <Enter> will select and edit the file.\r\n\r\nThis will split the window and open the file in the newly split window:\r\n\r\n    :FindFileSplit<CR>\r\n    or\r\n    :FS<CR>\r\n\r\nTo clear the internal cache, do:\r\n\r\n    :FindFileCacheClear<CR>\r\n    or\r\n    :FCC<CR>\r\n\r\n\r\nYou can put the following lines in your ~\/.vimrc in order to invoke\r\nFindFile quickly by hitting <C-f>:\r\n\r\n    nmap <C-f> :FindFile<CR>\r\n    nmap <C-s> :FindFileSplit<CR>\r\n\r\n\r\nBy default, all the *.o, *.pyc, and *\/tmp\/* files will be ignored, in\r\naddition to the wildignore patterns.  You can customize this by setting in\r\nyour .vimrc:\r\n\r\n    let g:FindFileIgnore = ['*.o', '*.pyc', '*\/tmp\/*']\r\n","5":"Put this file in your ~\/.vim\/plugin directory.\r\nIf you are working on a project, go to the root directory of the project,\r\nthen execute:\r\n\r\n    :FindFileCache .<CR>\r\n    or\r\n    :FC .<CR>\r\n\r\nThis will recursively parse the directory and create the internal cache.\r\n\r\nYou can also put in multiple arguments in :FC:\r\n\r\n    :FC \/dir1 \/dir2 \/dir3\r\n\r\nYou can add to the cache by calling :FC again.  File with the same path\r\nwill not be added to the cache twice.\r\n\r\nTo find a file:\r\n\r\n    :FindFile<CR>\r\n    or\r\n    :FF<CR>\r\n\r\nThis opens a scratch buffer that you can type in the file name.  Press\r\n<Esc> will quit the buffer, while <Enter> will select and edit the file.\r\n\r\nThis will split the window and open the file in the newly split window:\r\n\r\n    :FindFileSplit<CR>\r\n    or\r\n    :FS<CR>\r\n\r\nTo clear the internal cache, do:\r\n\r\n    :FindFileCacheClear<CR>\r\n    or\r\n    :FCC<CR>\r\n\r\n\r\nYou can put the following lines in your ~\/.vimrc in order to invoke\r\nFindFile quickly by hitting <C-f>:\r\n\r\n    nmap <C-f> :FindFile<CR>\r\n    nmap <C-s> :FindFileSplit<CR>\r\n\r\n\r\nBy default, all the *.o, *.pyc, and *\/tmp\/* files will be ignored, in\r\naddition to the wildignore patterns.  You can customize this by setting in\r\nyour .vimrc:\r\n\r\n    let g:FindFileIgnore = ['*.o', '*.pyc', '*\/tmp\/*']\r\n","first_name":"William","6":"William","last_name":"Lee","7":"Lee","releases":[{"0":"1899","vim_version":"7.0","1":"7.0","script_version":"1.0.3","2":"1.0.3","version_comment":"Ignore the directories in the autocomplete file list.","3":"Ignore the directories in the autocomplete file list.","package":"FindFile.vim","4":"FindFile.vim","src_id":"7528","5":"7528","creation_date":"1187594495","6":"1187594495"},{"0":"1899","vim_version":"6.0","1":"6.0","script_version":"1.0.2","2":"1.0.2","version_comment":"Map more characters for autocompletion.","3":"Map more characters for autocompletion.","package":"FindFile.vim","4":"FindFile.vim","src_id":"7469","5":"7469","creation_date":"1186562625","6":"1186562625"},{"0":"1899","vim_version":"7.0","1":"7.0","script_version":"1.0.1","2":"1.0.1","version_comment":"Added the FindFileSplit option.  Improved the autocomplete behavior.","3":"Added the FindFileSplit option.  Improved the autocomplete behavior.","package":"FindFile.vim","4":"FindFile.vim","src_id":"7139","5":"7139","creation_date":"1179432267","6":"1179432267"},{"0":"1899","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"FindFile.vim","4":"FindFile.vim","src_id":"7125","5":"7125","creation_date":"1179350089","6":"1179350089"}]},"1898":{"script_id":"1898","0":"1898","script_name":"vcsnursery","1":"vcsnursery","script_type":"utility","2":"utility","summary":"Additional backends for vcscommand","3":"Additional backends for vcscommand","description":"This is now outdated, if you are interested in sccs plugin to vcscommand, there is git project at https:\/\/github.com\/vlmarek\/VCSCommandVlad\/commits\/Vlad\r\n\r\nIntro:\r\nThis package contains additional backends (Mercurial and sccs currently) for vcscommand vimscript#90 (thanks for the excellent package!). While talking Bob about including them to vcscommand, he suggested to create additional package, which would contain new and possibly buggy backends. After some soak time, they might be moved to vcscommand itself. So here we go.\r\n\r\nCurrent status:\r\nMercurial: Full support + annotate syntax\r\nSCCS: Limited support (full is not possible, see below) and annotate syntax\r\n\r\nSccs backend does not have Add, Delete, Lock, Revert, Unlock and Update. There's enough for VCSVimDiff, VCSAnnotate and VCSLog. The reason is, that sccs can be used on it's own, through TeamWare and through other wrappers like Sun internal wx. It would be possible to write plugin to handle them all, but I'm not convinced that it's worth the hassle (make me do it :)).\r\n\r\nContact:\r\nsee my account info\r\n","4":"This is now outdated, if you are interested in sccs plugin to vcscommand, there is git project at https:\/\/github.com\/vlmarek\/VCSCommandVlad\/commits\/Vlad\r\n\r\nIntro:\r\nThis package contains additional backends (Mercurial and sccs currently) for vcscommand vimscript#90 (thanks for the excellent package!). While talking Bob about including them to vcscommand, he suggested to create additional package, which would contain new and possibly buggy backends. After some soak time, they might be moved to vcscommand itself. So here we go.\r\n\r\nCurrent status:\r\nMercurial: Full support + annotate syntax\r\nSCCS: Limited support (full is not possible, see below) and annotate syntax\r\n\r\nSccs backend does not have Add, Delete, Lock, Revert, Unlock and Update. There's enough for VCSVimDiff, VCSAnnotate and VCSLog. The reason is, that sccs can be used on it's own, through TeamWare and through other wrappers like Sun internal wx. It would be possible to write plugin to handle them all, but I'm not convinced that it's worth the hassle (make me do it :)).\r\n\r\nContact:\r\nsee my account info\r\n","install_details":"Unpack the package and copy plugin and syntax files to your ~\/.vim or equivalent directory.\r\n","5":"Unpack the package and copy plugin and syntax files to your ~\/.vim or equivalent directory.\r\n","first_name":"Vladimir","6":"Vladimir","last_name":"Marek","7":"Marek","releases":[{"0":"1898","vim_version":"7.0","1":"7.0","script_version":"4","2":"4","version_comment":"- Hg & Sccs backends: Better implementation of VCSAnnotate. Thanks to Christian Ebert\r\n- Hg backend: Syntax fix for author names starting at the end of the line\r\n- Sccs backend: Syntax fix for branches","3":"- Hg & Sccs backends: Better implementation of VCSAnnotate. Thanks to Christian Ebert\r\n- Hg backend: Syntax fix for author names starting at the end of the line\r\n- Sccs backend: Syntax fix for branches","package":"vcsnursery.zip","4":"vcsnursery.zip","src_id":"8570","5":"8570","creation_date":"1208421071","6":"1208421071"},{"0":"1898","vim_version":"7.0","1":"7.0","script_version":"3","2":"3","version_comment":"- Hg backend: Fixed VCSAnnotate","3":"- Hg backend: Fixed VCSAnnotate","package":"vcsnursery.zip","4":"vcsnursery.zip","src_id":"8569","5":"8569","creation_date":"1208417032","6":"1208417032"},{"0":"1898","vim_version":"7.0","1":"7.0","script_version":"2","2":"2","version_comment":"- updated to latest vcscommand version\r\n- Sccs backend: added VCSDiff support (VCSVimDiff was already implemented)\r\n","3":"- updated to latest vcscommand version\r\n- Sccs backend: added VCSDiff support (VCSVimDiff was already implemented)\r\n","package":"vcsnursery.zip","4":"vcsnursery.zip","src_id":"8568","5":"8568","creation_date":"1208401924","6":"1208401924"},{"0":"1898","vim_version":"7.0","1":"7.0","script_version":"1","2":"1","version_comment":"Initial upload","3":"Initial upload","package":"vcsnursery.zip","4":"vcsnursery.zip","src_id":"7116","5":"7116","creation_date":"1179232463","6":"1179232463"}]},"1897":{"script_id":"1897","0":"1897","script_name":"synic.vim","1":"synic.vim","script_type":"color scheme","2":"color scheme","summary":"A pastel and high contrast colorscheme","3":"A pastel and high contrast colorscheme","description":"Based from desert, but with a higher contrast of colors.  The background is always black to make the syntax colors stand out better.  I took special effort to make sure that no color is too bright.  Works great if you're working at the office under good light.\r\n\r\nScreenshot at http:\/\/www.exaile.org\/vim.png\r\n\r\nThe latest version is the combined 256 color terminal and gvim colorscheme","4":"Based from desert, but with a higher contrast of colors.  The background is always black to make the syntax colors stand out better.  I took special effort to make sure that no color is too bright.  Works great if you're working at the office under good light.\r\n\r\nScreenshot at http:\/\/www.exaile.org\/vim.png\r\n\r\nThe latest version is the combined 256 color terminal and gvim colorscheme","install_details":"Copy synic.vim into  ~\/.vim\/colors.  Load with :colorscheme synic","5":"Copy synic.vim into  ~\/.vim\/colors.  Load with :colorscheme synic","first_name":"Adam","6":"Adam","last_name":"Olsen","7":"Olsen","releases":[{"0":"1897","vim_version":"6.0","1":"6.0","script_version":"0.5","2":"0.5","version_comment":"Remove duplicate definitions.","3":"Remove duplicate definitions.","package":"synic.vim","4":"synic.vim","src_id":"11157","5":"11157","creation_date":"1249668057","6":"1249668057"},{"0":"1897","vim_version":"6.0","1":"6.0","script_version":"0.4","2":"0.4","version_comment":"No background in 256color terminal mode instead of black, for transparent terminals","3":"No background in 256color terminal mode instead of black, for transparent terminals","package":"synic.vim","4":"synic.vim","src_id":"11144","5":"11144","creation_date":"1249611651","6":"1249611651"},{"0":"1897","vim_version":"6.0","1":"6.0","script_version":"0.3","2":"0.3","version_comment":"Combined 256 color terminal and gvim colorscheme","3":"Combined 256 color terminal and gvim colorscheme","package":"synic.vim","4":"synic.vim","src_id":"11133","5":"11133","creation_date":"1249496497","6":"1249496497"},{"0":"1897","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"synic.vim","4":"synic.vim","src_id":"7110","5":"7110","creation_date":"1179136819","6":"1179136819"}]},"1896":{"script_id":"1896","0":"1896","script_name":"ragtag.vim","1":"ragtag.vim","script_type":"utility","2":"utility","summary":"A set of mappings for HTML, XML, PHP, ASP, eRuby, JSP, and more (formerly allml)","3":"A set of mappings for HTML, XML, PHP, ASP, eRuby, JSP, and more (formerly allml)","description":"This plugin started out as a set of personal mappings, but there was enough enjoyment among those I shared it with for me to clean it up and release it.\r\n\r\nFeatures:\r\n\r\nWhile there are several HTML and XML scripts on vim.org, I have found none that share a significant amount of functionality with allml.vim.\r\n\r\nA huge variety of filetypes are supported:  html, xhtml, wml, xml, xslt, xsd, jsp, php, aspperl, aspvbs, cf, mason, htmldjango, and eruby.  (Let me know if I missed any).  Some features take note of the filetype and adapt to it.\r\n\r\nMaps for editing tags are provided.  This includes a couple of \"make last word into a tag pair\" maps, a doctype map (inserts <?xml ...?> in XML), a \"close last tag\" map, and a few extra goodies.\r\n\r\nFor templating languages (ASP, PHP, etc.), there are maps for inserting template code.  The maps are dependent on the filetype: in ASP, you get <% %> and <%= %>, in PHP, <?php ?> and <?php print ?>, etc.  If said template language has a comment syntax, there is a map for it, otherwise, that map points to <!-- -->.\r\n\r\nMaps for XML\/HTML escaping and URL encoding have been moved to unimpaired.vim, vimscript #1590.\r\n\r\nEnhances surround.vim, vimscript #1697.\r\n\r\nhttp:\/\/github.com\/tpope\/vim-ragtag","4":"This plugin started out as a set of personal mappings, but there was enough enjoyment among those I shared it with for me to clean it up and release it.\r\n\r\nFeatures:\r\n\r\nWhile there are several HTML and XML scripts on vim.org, I have found none that share a significant amount of functionality with allml.vim.\r\n\r\nA huge variety of filetypes are supported:  html, xhtml, wml, xml, xslt, xsd, jsp, php, aspperl, aspvbs, cf, mason, htmldjango, and eruby.  (Let me know if I missed any).  Some features take note of the filetype and adapt to it.\r\n\r\nMaps for editing tags are provided.  This includes a couple of \"make last word into a tag pair\" maps, a doctype map (inserts <?xml ...?> in XML), a \"close last tag\" map, and a few extra goodies.\r\n\r\nFor templating languages (ASP, PHP, etc.), there are maps for inserting template code.  The maps are dependent on the filetype: in ASP, you get <% %> and <%= %>, in PHP, <?php ?> and <?php print ?>, etc.  If said template language has a comment syntax, there is a map for it, otherwise, that map points to <!-- -->.\r\n\r\nMaps for XML\/HTML escaping and URL encoding have been moved to unimpaired.vim, vimscript #1590.\r\n\r\nEnhances surround.vim, vimscript #1697.\r\n\r\nhttp:\/\/github.com\/tpope\/vim-ragtag","install_details":"Extract in ~\/.vim or ~\\vimfiles (Windows).  If you want a few general purpose mappings available globally, add the following to your vimrc:\r\n\r\nlet g:ragtag_global_maps = 1\r\n","5":"Extract in ~\/.vim or ~\\vimfiles (Windows).  If you want a few general purpose mappings available globally, add the following to your vimrc:\r\n\r\nlet g:ragtag_global_maps = 1\r\n","first_name":"Tim","6":"Tim","last_name":"Pope","7":"Pope","releases":[{"0":"1896","vim_version":"6.0","1":"6.0","script_version":"2.0","2":"2.0","version_comment":"Rename from allml.vim to ragtag.vim.\r\nReal documentation file.\r\nRemove HTML\/URL encoding in favor of using unimpaired.vim, vimscript #1590.","3":"Rename from allml.vim to ragtag.vim.\r\nReal documentation file.\r\nRemove HTML\/URL encoding in favor of using unimpaired.vim, vimscript #1590.","package":"ragtag.zip","4":"ragtag.zip","src_id":"12338","5":"12338","creation_date":"1265591097","6":"1265591097"},{"0":"1896","vim_version":"6.0","1":"6.0","script_version":"1.11","2":"1.11","version_comment":"Insert mode HTML\/XML and URL escaping.\r\nClarified documentation and license.","3":"Insert mode HTML\/XML and URL escaping.\r\nClarified documentation and license.","package":"allml.vim","4":"allml.vim","src_id":"7356","5":"7356","creation_date":"1184582957","6":"1184582957"},{"0":"1896","vim_version":"6.0","1":"6.0","script_version":"1.8","2":"1.8","version_comment":"Initial upload","3":"Initial upload","package":"allml.vim","4":"allml.vim","src_id":"7101","5":"7101","creation_date":"1179009203","6":"1179009203"}]},"1895":{"script_id":"1895","0":"1895","script_name":"gmcs.vim","1":"gmcs.vim","script_type":"utility","2":"utility","summary":"Mono C# compiler profile","3":"Mono C# compiler profile","description":"Mono C# compiler profile.  Tells vim to run gmcs when you :make your file.  Plus, when you run the :make command on your .cs file, this will parse the error messages and let you jump right to the problem points.   ","4":"Mono C# compiler profile.  Tells vim to run gmcs when you :make your file.  Plus, when you run the :make command on your .cs file, this will parse the error messages and let you jump right to the problem points.   ","install_details":"Place file in your $VIMRUNTIME\/compiler directory, and issue the ':compiler gmcs' command.\r\n\r\nSee :help compiler for more info.","5":"Place file in your $VIMRUNTIME\/compiler directory, and issue the ':compiler gmcs' command.\r\n\r\nSee :help compiler for more info.","first_name":"erik","6":"erik","last_name":"falor","7":"falor","releases":[{"0":"1895","vim_version":"7.0","1":"7.0","script_version":"1.2.1","2":"1.2.1","version_comment":"Can now be used with GNU Make.  Just set makeprg=make and provide a makefile.  The error output is is correctly parsed and jumps to the correct files. \r\n\r\nEmail comments and improvements to ewfalor@gmail.com","3":"Can now be used with GNU Make.  Just set makeprg=make and provide a makefile.  The error output is is correctly parsed and jumps to the correct files. \r\n\r\nEmail comments and improvements to ewfalor@gmail.com","package":"gmcs.vim","4":"gmcs.vim","src_id":"7165","5":"7165","creation_date":"1179997875","6":"1179997875"},{"0":"1895","vim_version":"7.0","1":"7.0","script_version":"1.2","2":"1.2","version_comment":"Improved error format distinguishes warnings and errors.","3":"Improved error format distinguishes warnings and errors.","package":"gmcs.vim","4":"gmcs.vim","src_id":"7109","5":"7109","creation_date":"1179136199","6":"1179136199"}]},"1894":{"script_id":"1894","0":"1894","script_name":"Vim Setup system","1":"Vim Setup system","script_type":"utility","2":"utility","summary":"Vim Setup system - persistent setup directly in vim","3":"Vim Setup system - persistent setup directly in vim","description":"This script is a modified version of the Setup script created by Jos van RisWick and which can be found here: \r\nhttp:\/\/www.xs4all.nl\/~josvanr\/vim\/setup.vim\r\n\r\nModifications:\r\n- This package includes all the external scripts needed in order to make this script work.\r\n- All scripts are modified such that they expect to find the other scripts in the plugin folder in vimhome instead of in the users home directory. \r\n- fixed an incompatibility with vim 7.0 and newer\r\nPlease see Jos' site for more info about the script. ","4":"This script is a modified version of the Setup script created by Jos van RisWick and which can be found here: \r\nhttp:\/\/www.xs4all.nl\/~josvanr\/vim\/setup.vim\r\n\r\nModifications:\r\n- This package includes all the external scripts needed in order to make this script work.\r\n- All scripts are modified such that they expect to find the other scripts in the plugin folder in vimhome instead of in the users home directory. \r\n- fixed an incompatibility with vim 7.0 and newer\r\nPlease see Jos' site for more info about the script. ","install_details":"go into vim home (typically ~\/.vim\/) and unpack the package. This will place all files in a subfolder named plugin\/\r\nRead further instructions in top of the setup.vim file. \r\n","5":"go into vim home (typically ~\/.vim\/) and unpack the package. This will place all files in a subfolder named plugin\/\r\nRead further instructions in top of the setup.vim file. \r\n","first_name":"Kim","6":"Kim","last_name":"Schulz","7":"Schulz","releases":[{"0":"1894","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"vim-setup-0.1.tgz","4":"vim-setup-0.1.tgz","src_id":"7094","5":"7094","creation_date":"1178808075","6":"1178808075"}]},"1893":{"script_id":"1893","0":"1893","script_name":"vmake","1":"vmake","script_type":"utility","2":"utility","summary":"Use quickfix with external make","3":"Use quickfix with external make","description":"vmake is a small bash script to use quickfix with the external make command.  running 'vmake' on sourcode with errors will let gvim  jump automatically to the first error. Now you can use all quixfix commands.\r\nIf you prefer the external make instead of the build in check it out.\r\n","4":"vmake is a small bash script to use quickfix with the external make command.  running 'vmake' on sourcode with errors will let gvim  jump automatically to the first error. Now you can use all quixfix commands.\r\nIf you prefer the external make instead of the build in check it out.\r\n","install_details":"1. chmod +x vmake\r\n2. copy to '\/usr\/bin' or '\/usr\/local\/bin'.\r\n3. run gvim\r\n4. run vmake inside a sourcecode folder\r\n5. gvim will jump to the first error in list\r\n6. cn jump to the next error\r\n\r\n\r\n\r\n","5":"1. chmod +x vmake\r\n2. copy to '\/usr\/bin' or '\/usr\/local\/bin'.\r\n3. run gvim\r\n4. run vmake inside a sourcecode folder\r\n5. gvim will jump to the first error in list\r\n6. cn jump to the next error\r\n\r\n\r\n\r\n","first_name":"Jochen","6":"Jochen","last_name":"Baier","7":"Baier","releases":[{"0":"1893","vim_version":"7.0","1":"7.0","script_version":"0.2","2":"0.2","version_comment":"Added Shebang, License.","3":"Added Shebang, License.","package":"vmake","4":"vmake","src_id":"7096","5":"7096","creation_date":"1178846701","6":"1178846701"},{"0":"1893","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"vmake","4":"vmake","src_id":"7091","5":"7091","creation_date":"1178799412","6":"1178799412"}]},"1892":{"script_id":"1892","0":"1892","script_name":"CimpTabulate.vim","1":"CimpTabulate.vim","script_type":"utility","2":"utility","summary":"Utility script for case tabulation in C\/C++","3":"Utility script for case tabulation in C\/C++","description":"This utility script is useful where you have a long list of similar, one-line case statements, and you'd like to format these statements in tabular form.\r\n\r\nThe script main function is :[range]call CimpTabulateCase(...) and it takes one optional argument. \r\n\r\nCimpTabulateCase() has three modes of tabulation: \r\n  * tabulation -- each sub-statement following the \"case :\" is aligned to a column\r\n  * compact -- only the statement immediately following the \"case :\" is aligned to a column\r\n  * smart tabulation -- as with tabulation, but tries to reduce the number of columns or apply compact for lines which overflow &textwidth\r\n\r\nCimpTabulateCase() interprets arguments as follows:\r\n  * 1 or \"^s\" -- use smart tabulation\r\n  * 2 or \"^c\" -- use compact tabulation\r\n  * all other non-empty arguments -- use normal tabulation\r\n\r\nIf CimpTabulateCase() it is used without arguments, and on the same range as it was previously used, it will cycle through the three modes of tabulation. Otherwise, it will use normal tabulation.\r\n\r\ncimp.vim defines four mappings for CimpTabulateCase():\r\n\r\n  :map <Leader>cc :call CimpTabulateCase()<CR>\r\n  :map <Leader>c0 :call CimpTabulateCase(0)<CR>\r\n  :map <Leader>c1 :call CimpTabulateCase(1)<CR>\r\n  :map <Leader>c2 :call CimpTabulateCase(2)<CR>\r\n\r\ncimp.vim also defines the following settings:\r\n\r\n  g:CimpPadding -- column padding, default = 1\r\n  g:CimpAlignSpecial -- align statements at the end of each line matching g:CimpAlignSpecialPattern in the last column, default = 1\r\n  g:CimpAlignSpecialPattern -- pattern for special alignment, default = \"\\^return\\\\|\\^break\"\r\n\r\nCimpTabulateCase() is probably best demonstrated using the following example: \r\n\r\n1. Add the following case statements to any buffer:\r\n    case kOneArg:         printf(\"Number: %d\\n\", argc); break;\r\n    case kTwoArgs:        printf(\"Number: %d\\n\", argc); break;\r\n    case kFourArgs:       printf(\"Number: %d\\n\", argc); a = b + c; break;\r\n    case kFifteenArgs:    printf(\"Number of args: %d\\n\"); a = b; break;\r\n    case TwentyThreeArgs: printf(\"Number of args are way too many: %d\\n\"); break;\r\n\r\n2. :se tw=80\r\n\r\n3. At the first case statement, try the following normal commands: \r\n\r\n  5\\c0 -- normal tabulation\r\n  5\\c1 -- smart tabulation\r\n  5\\c2 -- compact tabulation\r\n  5\\cc -- cycle to normal tabulation\r\n\r\nOf course you can also select a range using visual mode, and then\r\n\r\n  \\c0\r\n  gv\\c1\r\n  gv\\c2\r\n  gv\\cc\r\n\r\nImprovement suggestions and bug submissions are welcome.","4":"This utility script is useful where you have a long list of similar, one-line case statements, and you'd like to format these statements in tabular form.\r\n\r\nThe script main function is :[range]call CimpTabulateCase(...) and it takes one optional argument. \r\n\r\nCimpTabulateCase() has three modes of tabulation: \r\n  * tabulation -- each sub-statement following the \"case :\" is aligned to a column\r\n  * compact -- only the statement immediately following the \"case :\" is aligned to a column\r\n  * smart tabulation -- as with tabulation, but tries to reduce the number of columns or apply compact for lines which overflow &textwidth\r\n\r\nCimpTabulateCase() interprets arguments as follows:\r\n  * 1 or \"^s\" -- use smart tabulation\r\n  * 2 or \"^c\" -- use compact tabulation\r\n  * all other non-empty arguments -- use normal tabulation\r\n\r\nIf CimpTabulateCase() it is used without arguments, and on the same range as it was previously used, it will cycle through the three modes of tabulation. Otherwise, it will use normal tabulation.\r\n\r\ncimp.vim defines four mappings for CimpTabulateCase():\r\n\r\n  :map <Leader>cc :call CimpTabulateCase()<CR>\r\n  :map <Leader>c0 :call CimpTabulateCase(0)<CR>\r\n  :map <Leader>c1 :call CimpTabulateCase(1)<CR>\r\n  :map <Leader>c2 :call CimpTabulateCase(2)<CR>\r\n\r\ncimp.vim also defines the following settings:\r\n\r\n  g:CimpPadding -- column padding, default = 1\r\n  g:CimpAlignSpecial -- align statements at the end of each line matching g:CimpAlignSpecialPattern in the last column, default = 1\r\n  g:CimpAlignSpecialPattern -- pattern for special alignment, default = \"\\^return\\\\|\\^break\"\r\n\r\nCimpTabulateCase() is probably best demonstrated using the following example: \r\n\r\n1. Add the following case statements to any buffer:\r\n    case kOneArg:         printf(\"Number: %d\\n\", argc); break;\r\n    case kTwoArgs:        printf(\"Number: %d\\n\", argc); break;\r\n    case kFourArgs:       printf(\"Number: %d\\n\", argc); a = b + c; break;\r\n    case kFifteenArgs:    printf(\"Number of args: %d\\n\"); a = b; break;\r\n    case TwentyThreeArgs: printf(\"Number of args are way too many: %d\\n\"); break;\r\n\r\n2. :se tw=80\r\n\r\n3. At the first case statement, try the following normal commands: \r\n\r\n  5\\c0 -- normal tabulation\r\n  5\\c1 -- smart tabulation\r\n  5\\c2 -- compact tabulation\r\n  5\\cc -- cycle to normal tabulation\r\n\r\nOf course you can also select a range using visual mode, and then\r\n\r\n  \\c0\r\n  gv\\c1\r\n  gv\\c2\r\n  gv\\cc\r\n\r\nImprovement suggestions and bug submissions are welcome.","install_details":":so \/path\/to\/cimp.vim","5":":so \/path\/to\/cimp.vim","first_name":"Henrik","6":"Henrik","last_name":"\u00c3\u0096hman","7":"\u00c3\u0096hman","releases":[{"0":"1892","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"cimp.vim","4":"cimp.vim","src_id":"7086","5":"7086","creation_date":"1178696281","6":"1178696281"}]},"1891":{"script_id":"1891","0":"1891","script_name":"vividchalk.vim","1":"vividchalk.vim","script_type":"color scheme","2":"color scheme","summary":"A colorscheme strangely reminiscent of Vibrant Ink for a certain OS X editor","3":"A colorscheme strangely reminiscent of Vibrant Ink for a certain OS X editor","description":"This colorscheme is based on the Vibrant Ink theme for TextMate.  The original\r\ntheme was biased towards Ruby on Rails and this colorscheme continues that\r\ntradition.  In addition to the GUI, 256, 88, and even 16 color terminals are\r\nall supported.\r\n\r\nhttp:\/\/github.com\/tpope\/vim-vividchalk\r\n","4":"This colorscheme is based on the Vibrant Ink theme for TextMate.  The original\r\ntheme was biased towards Ruby on Rails and this colorscheme continues that\r\ntradition.  In addition to the GUI, 256, 88, and even 16 color terminals are\r\nall supported.\r\n\r\nhttp:\/\/github.com\/tpope\/vim-vividchalk\r\n","install_details":"Install in ~\/.vim\/colors, or ~\\vimfiles\\colors on Windows.\r\n\r\nTry it out with\r\n\r\n:colorscheme vividchalk\r\n\r\nIf you want to make it the default, add that command to your vimrc or gvimrc.\r\n","5":"Install in ~\/.vim\/colors, or ~\\vimfiles\\colors on Windows.\r\n\r\nTry it out with\r\n\r\n:colorscheme vividchalk\r\n\r\nIf you want to make it the default, add that command to your vimrc or gvimrc.\r\n","first_name":"Tim","6":"Tim","last_name":"Pope","7":"Pope","releases":[{"0":"1891","vim_version":"6.0","1":"6.0","script_version":"2.0","2":"2.0","version_comment":"Diff highlighting.\r\nSpell check highlighting.\r\nTone down matchparen highlighting.\r\nFix search highlighting in 16 color terminal.","3":"Diff highlighting.\r\nSpell check highlighting.\r\nTone down matchparen highlighting.\r\nFix search highlighting in 16 color terminal.","package":"vividchalk.vim","4":"vividchalk.vim","src_id":"12437","5":"12437","creation_date":"1266610968","6":"1266610968"},{"0":"1891","vim_version":"6.0","1":"6.0","script_version":"1.8","2":"1.8","version_comment":"Eliminated use of ugly underlining if italics isn't available.\r\nClarified license.","3":"Eliminated use of ugly underlining if italics isn't available.\r\nClarified license.","package":"vividchalk.vim","4":"vividchalk.vim","src_id":"7341","5":"7341","creation_date":"1184154746","6":"1184154746"},{"0":"1891","vim_version":"6.0","1":"6.0","script_version":"1.7","2":"1.7","version_comment":"A couple of Rails specific tweaks","3":"A couple of Rails specific tweaks","package":"vividchalk.vim","4":"vividchalk.vim","src_id":"7179","5":"7179","creation_date":"1180542741","6":"1180542741"},{"0":"1891","vim_version":"6.0","1":"6.0","script_version":"1.6","2":"1.6","version_comment":"Brightened colors up a bit in 256 color terminals.","3":"Brightened colors up a bit in 256 color terminals.","package":"vividchalk.vim","4":"vividchalk.vim","src_id":"7161","5":"7161","creation_date":"1179946806","6":"1179946806"},{"0":"1891","vim_version":"6.0","1":"6.0","script_version":"1.4","2":"1.4","version_comment":"Initial upload","3":"Initial upload","package":"vividchalk.vim","4":"vividchalk.vim","src_id":"7103","5":"7103","creation_date":"1179044906","6":"1179044906"}]},"1890":{"script_id":"1890","0":"1890","script_name":"LustyExplorer","1":"LustyExplorer","script_type":"utility","2":"utility","summary":"Dynamic filesystem and buffer explorer","3":"Dynamic filesystem and buffer explorer","description":"*** Download the newest version of this plugin on Github: https:\/\/github.com\/sjbach\/lusty ***\r\n\r\nLustyExplorer is a fast and responsive way to manage files and buffers in Vim.  It includes a filesystem explorer, a buffer switcher, and a buffer grep for searching through and switching between files and buffers quickly, all through a mostly common interface.\r\n\r\nShort demo videos folks have made:\r\n\r\n      http:\/\/www.youtube.com\/watch?v=dLMKVYqdarY\r\n      http:\/\/www.youtube.com\/watch?v=39A-VoPnsI0\r\n\r\n      Older stuff (pre v2.0 - we now use fuzzy matching instead of tab completion):\r\n      http:\/\/sjbach.com\/lusty-explorer-animated.gif\r\n      http:\/\/sjbach.com\/lusty-explorer-annotated.png\r\n\r\nInstructions:\r\n\r\n      :LustyFilesystemExplorer\r\n      :LustyFilesystemExplorerFromHere\r\n      :LustyBufferExplorer\r\n      :LustyBufferGrep (for searching through all open buffers)\r\n\r\n      <Leader>lf  - Opens filesystem explorer.\r\n      <Leader>lr  - Opens filesystem explorer at the directory of the current file.\r\n      <Leader>lb  - Opens buffer explorer.\r\n      <Leader>lg  - Opens buffer grep.\r\n\r\nWhen one of the explorers is launched, a new window appears at bottom presenting a table of files\/dirs or buffers, and in the status bar is a prompt:\r\n\r\n      >>\r\n\r\nAs you type a name, the table updates using a fuzzy matching algorithm (or regex matching in the case of grep).  Press enter to open the selected match, <C-n>\/<C-p> to select the next\/previous match, or press <ESC> or <Ctrl-c> to cancel.\r\n\r\nSee the \"Usage:\" section of the script for other tricks and features.\r\n\r\nIf you like LustyExplorer, you may also like LustyJuggler: vimscript #2050\r\n\r\nDevelopment repository: http:\/\/github.com\/sjbach\/lusty","4":"*** Download the newest version of this plugin on Github: https:\/\/github.com\/sjbach\/lusty ***\r\n\r\nLustyExplorer is a fast and responsive way to manage files and buffers in Vim.  It includes a filesystem explorer, a buffer switcher, and a buffer grep for searching through and switching between files and buffers quickly, all through a mostly common interface.\r\n\r\nShort demo videos folks have made:\r\n\r\n      http:\/\/www.youtube.com\/watch?v=dLMKVYqdarY\r\n      http:\/\/www.youtube.com\/watch?v=39A-VoPnsI0\r\n\r\n      Older stuff (pre v2.0 - we now use fuzzy matching instead of tab completion):\r\n      http:\/\/sjbach.com\/lusty-explorer-animated.gif\r\n      http:\/\/sjbach.com\/lusty-explorer-annotated.png\r\n\r\nInstructions:\r\n\r\n      :LustyFilesystemExplorer\r\n      :LustyFilesystemExplorerFromHere\r\n      :LustyBufferExplorer\r\n      :LustyBufferGrep (for searching through all open buffers)\r\n\r\n      <Leader>lf  - Opens filesystem explorer.\r\n      <Leader>lr  - Opens filesystem explorer at the directory of the current file.\r\n      <Leader>lb  - Opens buffer explorer.\r\n      <Leader>lg  - Opens buffer grep.\r\n\r\nWhen one of the explorers is launched, a new window appears at bottom presenting a table of files\/dirs or buffers, and in the status bar is a prompt:\r\n\r\n      >>\r\n\r\nAs you type a name, the table updates using a fuzzy matching algorithm (or regex matching in the case of grep).  Press enter to open the selected match, <C-n>\/<C-p> to select the next\/previous match, or press <ESC> or <Ctrl-c> to cancel.\r\n\r\nSee the \"Usage:\" section of the script for other tricks and features.\r\n\r\nIf you like LustyExplorer, you may also like LustyJuggler: vimscript #2050\r\n\r\nDevelopment repository: http:\/\/github.com\/sjbach\/lusty","install_details":"Copy the plugin\/ and autoload\/ directories into your $HOME\/.vim\/ directory.\r\n\r\nNOTE: This plugin requires Vim be compiled with Ruby interpretation.  If you do not currently have this functionality, see the \"Install Details:\" section of the script for directions to add it.\r\n\r\nIf adding Ruby is an issue for you, you may want to try LycosaExplorer, a Python port of this plugin: vimscript #3659","5":"Copy the plugin\/ and autoload\/ directories into your $HOME\/.vim\/ directory.\r\n\r\nNOTE: This plugin requires Vim be compiled with Ruby interpretation.  If you do not currently have this functionality, see the \"Install Details:\" section of the script for directions to add it.\r\n\r\nIf adding Ruby is an issue for you, you may want to try LycosaExplorer, a Python port of this plugin: vimscript #3659","first_name":"Stephen","6":"Stephen","last_name":"Bach","7":"Bach","releases":[{"0":"1890","vim_version":"7.0","1":"7.0","script_version":"5.0","2":"5.0","version_comment":"Many minor fixes over the last six years.","3":"Many minor fixes over the last six years.","package":"lusty-explorer-5.0.zip","4":"lusty-explorer-5.0.zip","src_id":"26146","5":"26146","creation_date":"1532494592","6":"1532494592"},{"0":"1890","vim_version":"7.0","1":"7.0","script_version":"4.3","2":"4.3","version_comment":"- Fixed some quoting bugs when invoking :LustyFilesystemExplorerStart. (Joel D. Elkins)\r\n- Handle directory security restrictions in Windows more gracefully. (Joel D. Elkins)\r\n- Hide \"relativenumber\" display in the explorer. (G\u00c3\u00b6ran Gustafsson)","3":"- Fixed some quoting bugs when invoking :LustyFilesystemExplorerStart. (Joel D. Elkins)\r\n- Handle directory security restrictions in Windows more gracefully. (Joel D. Elkins)\r\n- Hide \"relativenumber\" display in the explorer. (G\u00c3\u00b6ran Gustafsson)","package":"lusty-explorer.vim","4":"lusty-explorer.vim","src_id":"17529","5":"17529","creation_date":"1330140507","6":"1330140507"},{"0":"1890","vim_version":"7.0","1":"7.0","script_version":"4.2","2":"4.2","version_comment":"- Added arrow key navigation. (Giuseppe Rota)\r\n- Fixed an \"incompatible character encodings\" error. (lilydjwg)\r\n- Fixed a divide-by-zero error. (Toby O'Connell)\r\n- Added g:LustyExplorerDefaultMappings configuration. (G\u00c3\u00b6ran Gustafsson)","3":"- Added arrow key navigation. (Giuseppe Rota)\r\n- Fixed an \"incompatible character encodings\" error. (lilydjwg)\r\n- Fixed a divide-by-zero error. (Toby O'Connell)\r\n- Added g:LustyExplorerDefaultMappings configuration. (G\u00c3\u00b6ran Gustafsson)","package":"lusty-explorer.vim","4":"lusty-explorer.vim","src_id":"16964","5":"16964","creation_date":"1322250735","6":"1322250735"},{"0":"1890","vim_version":"7.0","1":"7.0","script_version":"4.1","2":"4.1","version_comment":"- Add Ctrl-B and Ctrl-F mappings to move to the next\/previous column. (Thanks to lilydjwg)\r\n- Allow exploring starting at arbitrary paths - :LustyFilesystemExplorer now accepts a path argument. (Thanks to Donald Curtis)\r\n- Prevent unwanted highlighting in the display buffer. (Thanks to Jan Zwiener)\r\n- Fix opening files with '%' in their names. (Thanks to lilydjwg)","3":"- Add Ctrl-B and Ctrl-F mappings to move to the next\/previous column. (Thanks to lilydjwg)\r\n- Allow exploring starting at arbitrary paths - :LustyFilesystemExplorer now accepts a path argument. (Thanks to Donald Curtis)\r\n- Prevent unwanted highlighting in the display buffer. (Thanks to Jan Zwiener)\r\n- Fix opening files with '%' in their names. (Thanks to lilydjwg)","package":"lusty-explorer.vim","4":"lusty-explorer.vim","src_id":"15545","5":"15545","creation_date":"1304104965","6":"1304104965"},{"0":"1890","vim_version":"7.0","1":"7.0","script_version":"4.0","2":"4.0","version_comment":"- New and improved fuzzy matching algorithm: Mercury. (Matt Tolton)\r\n- Buffer Explorer: don't show unlisted buffers. (Thanks to Johannes Holzfu\u00c3\u009f)\r\n- Align multi-byte CJK characters correctly in filenames. (Thanks to lilydjwg)\r\n- Truncate prompt if longer than window width to avoid \"press any key\" message. (Thanks to Martin Wache)\r\n- Save\/restore window config better. (Thanks to robquant)","3":"- New and improved fuzzy matching algorithm: Mercury. (Matt Tolton)\r\n- Buffer Explorer: don't show unlisted buffers. (Thanks to Johannes Holzfu\u00c3\u009f)\r\n- Align multi-byte CJK characters correctly in filenames. (Thanks to lilydjwg)\r\n- Truncate prompt if longer than window width to avoid \"press any key\" message. (Thanks to Martin Wache)\r\n- Save\/restore window config better. (Thanks to robquant)","package":"lusty-explorer.vim","4":"lusty-explorer.vim","src_id":"14546","5":"14546","creation_date":"1292603665","6":"1292603665"},{"0":"1890","vim_version":"7.0","1":"7.0","script_version":"3.1.1","2":"3.1.1","version_comment":"Don't throw an error when looking up special non-file buffers.  (Thanks to Ben Boeckel)","3":"Don't throw an error when looking up special non-file buffers.  (Thanks to Ben Boeckel)","package":"lusty-explorer.vim","4":"lusty-explorer.vim","src_id":"13373","5":"13373","creation_date":"1279724855","6":"1279724855"},{"0":"1890","vim_version":"7.0","1":"7.0","script_version":"3.1.0","2":"3.1.0","version_comment":"- Buffer grep: performance improvement.\r\n- Buffer explorer: secondary sort by most-recently used.","3":"- Buffer grep: performance improvement.\r\n- Buffer explorer: secondary sort by most-recently used.","package":"lusty-explorer.vim","4":"lusty-explorer.vim","src_id":"13255","5":"13255","creation_date":"1277736721","6":"1277736721"},{"0":"1890","vim_version":"7.0","1":"7.0","script_version":"3.0","2":"3.0","version_comment":"- New :LustyBufferGrep for searching through open buffers.\r\n- Filesystem explorer: fixed a directory recursion highlighting bug.","3":"- New :LustyBufferGrep for searching through open buffers.\r\n- Filesystem explorer: fixed a directory recursion highlighting bug.","package":"lusty-explorer.vim","4":"lusty-explorer.vim","src_id":"13245","5":"13245","creation_date":"1277577525","6":"1277577525"},{"0":"1890","vim_version":"7.0","1":"7.0","script_version":"2.3.0","2":"2.3.0","version_comment":"- Better matches window layout algorithm.\r\n- Put code in its own namespace to play nicer with other Ruby plugins.\r\n- Don't error when run in read-only mode.  (Thanks to Ali Asad Lotia)\r\n- Don't error if a file is treated as a dir.\r\n- Don't error when a single-quote is typed.","3":"- Better matches window layout algorithm.\r\n- Put code in its own namespace to play nicer with other Ruby plugins.\r\n- Don't error when run in read-only mode.  (Thanks to Ali Asad Lotia)\r\n- Don't error if a file is treated as a dir.\r\n- Don't error when a single-quote is typed.","package":"lusty-explorer.vim","4":"lusty-explorer.vim","src_id":"12728","5":"12728","creation_date":"1269801629","6":"1269801629"},{"0":"1890","vim_version":"7.0","1":"7.0","script_version":"2.2.3","2":"2.2.3","version_comment":"Cygwin and Windows compatibility fixes.  (Thanks to Brett DiFrischia)\r\n- Warn if &compatible mode is set.\r\n- Windows: show matches when at root (i.e. C:\/).\r\n- Cygwin: workaround some missing POSIX stuff.\r\n- Cygwin: don't freeze when exploring root (weird Ruby bug).","3":"Cygwin and Windows compatibility fixes.  (Thanks to Brett DiFrischia)\r\n- Warn if &compatible mode is set.\r\n- Windows: show matches when at root (i.e. C:\/).\r\n- Cygwin: workaround some missing POSIX stuff.\r\n- Cygwin: don't freeze when exploring root (weird Ruby bug).","package":"lusty-explorer.vim","4":"lusty-explorer.vim","src_id":"12711","5":"12711","creation_date":"1269657866","6":"1269657866"},{"0":"1890","vim_version":"7.0","1":"7.0","script_version":"2.2.2","2":"2.2.2","version_comment":"Buffer explorer: fixed a spurious error message introduced in the previous release.  (Thanks to sowill)","3":"Buffer explorer: fixed a spurious error message introduced in the previous release.  (Thanks to sowill)","package":"lusty-explorer.vim","4":"lusty-explorer.vim","src_id":"12709","5":"12709","creation_date":"1269577698","6":"1269577698"},{"0":"1890","vim_version":"7.0","1":"7.0","script_version":"2.2.1","2":"2.2.1","version_comment":"Performance improvements.","3":"Performance improvements.","package":"lusty-explorer.vim","4":"lusty-explorer.vim","src_id":"12708","5":"12708","creation_date":"1269563662","6":"1269563662"},{"0":"1890","vim_version":"7.0","1":"7.0","script_version":"2.2.0","2":"2.2.0","version_comment":"- New keys: C-o -> open in horizontal split, C-v -> open in vertical split.  (Thanks to David Brown)\r\n- Fix environment variable expansion.\r\n- Rename launch commands, e.g. BufferExplorer -> LustyBufferExplorer.","3":"- New keys: C-o -> open in horizontal split, C-v -> open in vertical split.  (Thanks to David Brown)\r\n- Fix environment variable expansion.\r\n- Rename launch commands, e.g. BufferExplorer -> LustyBufferExplorer.","package":"lusty-explorer.vim","4":"lusty-explorer.vim","src_id":"12632","5":"12632","creation_date":"1268675279","6":"1268675279"},{"0":"1890","vim_version":"7.0","1":"7.0","script_version":"2.1.3","2":"2.1.3","version_comment":"Fix an error message on some platforms introduced in the previous release.  (Thanks to sowill)","3":"Fix an error message on some platforms introduced in the previous release.  (Thanks to sowill)","package":"lusty-explorer.vim","4":"lusty-explorer.vim","src_id":"12552","5":"12552","creation_date":"1267671078","6":"1267671078"},{"0":"1890","vim_version":"7.0","1":"7.0","script_version":"2.1.2","2":"2.1.2","version_comment":"- Fix performance over NFS.\r\n- Fix portability with the updated Vim->Ruby data type conversion in devhead Vim.  (Thanks to Bj\u00c3\u00b6rn Winckler)\r\n- Fix portability with Ruby 1.9.","3":"- Fix performance over NFS.\r\n- Fix portability with the updated Vim->Ruby data type conversion in devhead Vim.  (Thanks to Bj\u00c3\u00b6rn Winckler)\r\n- Fix portability with Ruby 1.9.","package":"lusty-explorer.vim","4":"lusty-explorer.vim","src_id":"12551","5":"12551","creation_date":"1267639528","6":"1267639528"},{"0":"1890","vim_version":"7.0","1":"7.0","script_version":"2.1.1","2":"2.1.1","version_comment":"- Open files using relative paths for better readability in e.g. :ls. (Thanks to Bernhard Walle)\r\n- Warn when fuzzyfinder_textmate is detected -- this plugin interacts poorly with LustyExplorer. (Thanks to Charl Matthee)\r\n- Fix a minor highlighting bug.","3":"- Open files using relative paths for better readability in e.g. :ls. (Thanks to Bernhard Walle)\r\n- Warn when fuzzyfinder_textmate is detected -- this plugin interacts poorly with LustyExplorer. (Thanks to Charl Matthee)\r\n- Fix a minor highlighting bug.","package":"lusty-explorer.vim","4":"lusty-explorer.vim","src_id":"11526","5":"11526","creation_date":"1255456060","6":"1255456060"},{"0":"1890","vim_version":"7.0","1":"7.0","script_version":"2.1.0","2":"2.1.0","version_comment":"- Significant performance increase for directories with many files.\r\n- Lower memory usage in directory memoization.","3":"- Significant performance increase for directories with many files.\r\n- Lower memory usage in directory memoization.","package":"lusty-explorer.vim","4":"lusty-explorer.vim","src_id":"10797","5":"10797","creation_date":"1244645296","6":"1244645296"},{"0":"1890","vim_version":"7.0","1":"7.0","script_version":"2.0","2":"2.0","version_comment":"The vast majority of these changes were contributed by Matt Tolton:\r\n- Flex\/fuzzy matching using the LiquidMetal algorithm:\r\n  <http:\/\/github.com\/rmm5t\/liquidmetal\/tree\/master>\r\n- Buffer explorer: paths are hidden except to differentiate buffers of\r\n  the same basename.\r\n- New option:\r\n    g:LustyExplorerAlwaysShowDotFiles\r\n- Filesystem explorer: directory contents are memoized\r\n- New keys for the prompt:\r\n    C-t: open selected entry in new tab\r\n    C-n: select the next entry\r\n    C-p: select the previous entry\r\n    C-w: move one directory upward at prompt\r\n    C-u: clear the prompt\r\n- New keys specific to the filesystem explorer:\r\n    C-r: refresh directory contents\r\n    C-a: open all files in the current list\r\n    C-e: create a new file with the given name\r\n- Cursor will \"hide\" correctly when a filename includes a two-column\r\n  character.\r\n- GetLatestVimScripts compatibility.\r\n- Faster implentation of columnize().  Thanks to Sami Samhuri.\r\n- Fixed a declaration typo.  Thanks to Simo Salminen.","3":"The vast majority of these changes were contributed by Matt Tolton:\r\n- Flex\/fuzzy matching using the LiquidMetal algorithm:\r\n  <http:\/\/github.com\/rmm5t\/liquidmetal\/tree\/master>\r\n- Buffer explorer: paths are hidden except to differentiate buffers of\r\n  the same basename.\r\n- New option:\r\n    g:LustyExplorerAlwaysShowDotFiles\r\n- Filesystem explorer: directory contents are memoized\r\n- New keys for the prompt:\r\n    C-t: open selected entry in new tab\r\n    C-n: select the next entry\r\n    C-p: select the previous entry\r\n    C-w: move one directory upward at prompt\r\n    C-u: clear the prompt\r\n- New keys specific to the filesystem explorer:\r\n    C-r: refresh directory contents\r\n    C-a: open all files in the current list\r\n    C-e: create a new file with the given name\r\n- Cursor will \"hide\" correctly when a filename includes a two-column\r\n  character.\r\n- GetLatestVimScripts compatibility.\r\n- Faster implentation of columnize().  Thanks to Sami Samhuri.\r\n- Fixed a declaration typo.  Thanks to Simo Salminen.","package":"lusty-explorer.vim","4":"lusty-explorer.vim","src_id":"10696","5":"10696","creation_date":"1243524760","6":"1243524760"},{"0":"1890","vim_version":"7.0","1":"7.0","script_version":"1.4.3","2":"1.4.3","version_comment":"- Definitively fix the bug of overwritten delete registers.\r\n- Respect the 'wildignore' variable; g:LustyExplorerFileMasks still works, but is deprecated.","3":"- Definitively fix the bug of overwritten delete registers.\r\n- Respect the 'wildignore' variable; g:LustyExplorerFileMasks still works, but is deprecated.","package":"lusty-explorer.vim","4":"lusty-explorer.vim","src_id":"9902","5":"9902","creation_date":"1233533677","6":"1233533677"},{"0":"1890","vim_version":"7.0","1":"7.0","script_version":"1.4.2","2":"1.4.2","version_comment":"Restore the unnamed (default) register after using the explorer.  Thanks to cho45.","3":"Restore the unnamed (default) register after using the explorer.  Thanks to cho45.","package":"lusty-explorer.vim","4":"lusty-explorer.vim","src_id":"9170","5":"9170","creation_date":"1219692466","6":"1219692466"},{"0":"1890","vim_version":"7.0","1":"7.0","script_version":"1.4.1","2":"1.4.1","version_comment":"- When the explorer is cancelled, reset the previous buffer (b#) to the actual previous buffer.\r\n- Fixed error when launching the explorer while editing a remote file through netrw.  Thanks to Bernhard Walle.","3":"- When the explorer is cancelled, reset the previous buffer (b#) to the actual previous buffer.\r\n- Fixed error when launching the explorer while editing a remote file through netrw.  Thanks to Bernhard Walle.","package":"lusty-explorer.vim","4":"lusty-explorer.vim","src_id":"7877","5":"7877","creation_date":"1194208088","6":"1194208088"},{"0":"1890","vim_version":"7.0","1":"7.0","script_version":"1.4.0","2":"1.4.0","version_comment":"- Filesystem explorer: added g:LustyExplorerFileMasks variable to hide certain types of files.\r\n- Filesystem explorer: speed up for directories with many files.\r\n- Added truncation indicator if there are more entries than can be displayed.","3":"- Filesystem explorer: added g:LustyExplorerFileMasks variable to hide certain types of files.\r\n- Filesystem explorer: speed up for directories with many files.\r\n- Added truncation indicator if there are more entries than can be displayed.","package":"lusty-explorer.vim","4":"lusty-explorer.vim","src_id":"7858","5":"7858","creation_date":"1193934399","6":"1193934399"},{"0":"1890","vim_version":"7.0","1":"7.0","script_version":"1.3.1","2":"1.3.1","version_comment":"Fixed memoization bug for recursing into directories with mixed case names.","3":"Fixed memoization bug for recursing into directories with mixed case names.","package":"lusty-explorer.vim","4":"lusty-explorer.vim","src_id":"7838","5":"7838","creation_date":"1193434407","6":"1193434407"},{"0":"1890","vim_version":"7.0","1":"7.0","script_version":"1.3.0","2":"1.3.0","version_comment":"- Filesystem explorer now does variable ($FOO) expansion.\r\n- Added some memoization for noticeable speed up on older hardware.","3":"- Filesystem explorer now does variable ($FOO) expansion.\r\n- Added some memoization for noticeable speed up on older hardware.","package":"lusty-explorer.vim","4":"lusty-explorer.vim","src_id":"7829","5":"7829","creation_date":"1193342332","6":"1193342332"},{"0":"1890","vim_version":"7.0","1":"7.0","script_version":"1.2.6","2":"1.2.6","version_comment":"Added compatibility for Windows, finally.  Please let me know if you have any problems.","3":"Added compatibility for Windows, finally.  Please let me know if you have any problems.","package":"lusty-explorer.vim","4":"lusty-explorer.vim","src_id":"7792","5":"7792","creation_date":"1192304195","6":"1192304195"},{"0":"1890","vim_version":"7.0","1":"7.0","script_version":"1.2.5","2":"1.2.5","version_comment":"- Now deals correctly with unnamed buffers instead of spitting out an error.  Thanks to Rajendra Badapanda.\r\n- Buffer explorer will now launch even if only a single buffer is open.","3":"- Now deals correctly with unnamed buffers instead of spitting out an error.  Thanks to Rajendra Badapanda.\r\n- Buffer explorer will now launch even if only a single buffer is open.","package":"lusty-explorer.vim","4":"lusty-explorer.vim","src_id":"7753","5":"7753","creation_date":"1191561133","6":"1191561133"},{"0":"1890","vim_version":"7.0","1":"7.0","script_version":"1.2.4","2":"1.2.4","version_comment":"- Pressing <TAB> will now open a buffer\/file if it is the only entry.\r\n- If <ENTER> is pressed when there are no matching entries, a new buffer will be created with the given name.\r\n- <C-g> now behaves like <C-c> and <ESC>.","3":"- Pressing <TAB> will now open a buffer\/file if it is the only entry.\r\n- If <ENTER> is pressed when there are no matching entries, a new buffer will be created with the given name.\r\n- <C-g> now behaves like <C-c> and <ESC>.","package":"lusty-explorer.vim","4":"lusty-explorer.vim","src_id":"7691","5":"7691","creation_date":"1190146258","6":"1190146258"},{"0":"1890","vim_version":"7.0","1":"7.0","script_version":"1.2.3","2":"1.2.3","version_comment":"Added g:LustyExplorerSuppressRubyWarning option for situations where the same Vim configuration is used over multiple machines, not all of which have Ruby installed.  Thanks to Bernhard Walle.","3":"Added g:LustyExplorerSuppressRubyWarning option for situations where the same Vim configuration is used over multiple machines, not all of which have Ruby installed.  Thanks to Bernhard Walle.","package":"lusty-explorer.vim","4":"lusty-explorer.vim","src_id":"7281","5":"7281","creation_date":"1182416592","6":"1182416592"},{"0":"1890","vim_version":"7.0","1":"7.0","script_version":"1.2.2","2":"1.2.2","version_comment":"Fixed filename truncation when sidescroll\/sidescrolloff have been set.  Thanks to Bernhard Walle.","3":"Fixed filename truncation when sidescroll\/sidescrolloff have been set.  Thanks to Bernhard Walle.","package":"lusty-explorer.vim","4":"lusty-explorer.vim","src_id":"7257","5":"7257","creation_date":"1182152698","6":"1182152698"},{"0":"1890","vim_version":"7.0","1":"7.0","script_version":"1.2.1","2":"1.2.1","version_comment":"- <C-h> now interpreted as backspace.  Thanks to Yuichi Tateno.\r\n- Much improved handling of files\/directories with special characters in their names.","3":"- <C-h> now interpreted as backspace.  Thanks to Yuichi Tateno.\r\n- Much improved handling of files\/directories with special characters in their names.","package":"lusty-explorer.vim","4":"lusty-explorer.vim","src_id":"7209","5":"7209","creation_date":"1181053376","6":"1181053376"},{"0":"1890","vim_version":"7.0","1":"7.0","script_version":"1.2.0","2":"1.2.0","version_comment":"- Added :FilesystemExplorerFromHere command.  Thanks to Sergey Popov.\r\n- Added highlighting to the prompt and cursor.\r\n- Buffer explorer: added [+] indicator to dirty buffers.\r\n- Many small fixes.","3":"- Added :FilesystemExplorerFromHere command.  Thanks to Sergey Popov.\r\n- Added highlighting to the prompt and cursor.\r\n- Buffer explorer: added [+] indicator to dirty buffers.\r\n- Many small fixes.","package":"lusty-explorer.vim","4":"lusty-explorer.vim","src_id":"7192","5":"7192","creation_date":"1180779619","6":"1180779619"},{"0":"1890","vim_version":"7.0","1":"7.0","script_version":"1.1.2","2":"1.1.2","version_comment":"- Filesystem explorer now does tilde (~) expansion.\r\n- Fixed some Vim error messages for special characters in filenames\/input.\r\n- Internal refactoring.","3":"- Filesystem explorer now does tilde (~) expansion.\r\n- Fixed some Vim error messages for special characters in filenames\/input.\r\n- Internal refactoring.","package":"lusty-explorer.vim","4":"lusty-explorer.vim","src_id":"7181","5":"7181","creation_date":"1180549897","6":"1180549897"},{"0":"1890","vim_version":"7.0","1":"7.0","script_version":"1.1.1","2":"1.1.1","version_comment":"Recursing into directories with capital letters in their names using case-insensitive matching has been fixed.  Thanks to Raimon Grau.","3":"Recursing into directories with capital letters in their names using case-insensitive matching has been fixed.  Thanks to Raimon Grau.","package":"lusty-explorer.vim","4":"lusty-explorer.vim","src_id":"7135","5":"7135","creation_date":"1179401266","6":"1179401266"},{"0":"1890","vim_version":"7.0","1":"7.0","script_version":"1.1.0","2":"1.1.0","version_comment":"- Renamed from DynamicExplorer.\r\n- Buffer explorer now orders by Most Recently Used.\r\n- Buffer explorer now matches anywhere in name.\r\n- Filesystem explorer highlights opened files.","3":"- Renamed from DynamicExplorer.\r\n- Buffer explorer now orders by Most Recently Used.\r\n- Buffer explorer now matches anywhere in name.\r\n- Filesystem explorer highlights opened files.","package":"lusty-explorer.vim","4":"lusty-explorer.vim","src_id":"7120","5":"7120","creation_date":"1179246852","6":"1179246852"},{"0":"1890","vim_version":"7.0","1":"7.0","script_version":"1.0.1","2":"1.0.1","version_comment":"- Allow opening files with spaces in their names.\r\n- Fixed listing bug where the whole window width sometimes wasn't being utilized.\r\n- The cursor is now moved off into a more inconspicuous corner.\r\n- Syntax highlighting improved for listings with spaces or parens.\r\n- Internal refactoring.","3":"- Allow opening files with spaces in their names.\r\n- Fixed listing bug where the whole window width sometimes wasn't being utilized.\r\n- The cursor is now moved off into a more inconspicuous corner.\r\n- Syntax highlighting improved for listings with spaces or parens.\r\n- Internal refactoring.","package":"dynamic-explorer.vim","4":"dynamic-explorer.vim","src_id":"7099","5":"7099","creation_date":"1178967903","6":"1178967903"},{"0":"1890","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"dynamic-explorer.vim","4":"dynamic-explorer.vim","src_id":"7081","5":"7081","creation_date":"1178648449","6":"1178648449"}]},"1889":{"script_id":"1889","0":"1889","script_name":"automated-rafb.net uploader plugin","1":"automated-rafb.net uploader plugin","script_type":"utility","2":"utility","summary":"only works on Windows, uploads current file in rafb.net","3":"only works on Windows, uploads current file in rafb.net","description":"the script is actually a perl script\r\nand you only have to make a minor modification to vimrc\r\nto be able to use it.\r\nwhat it does it is automated to go to rafb.net\r\npaste the current file you're editing there,and\r\nthen as rafb.net gives you a link to the file\r\nthe script will put it in your clipboard so you can reffer\r\nto where you need it.\r\nthis script would be recommended for whoever needs to paste some code.\r\nyou can use F5 to run the script on the current file.\r\nit only works on windows.","4":"the script is actually a perl script\r\nand you only have to make a minor modification to vimrc\r\nto be able to use it.\r\nwhat it does it is automated to go to rafb.net\r\npaste the current file you're editing there,and\r\nthen as rafb.net gives you a link to the file\r\nthe script will put it in your clipboard so you can reffer\r\nto where you need it.\r\nthis script would be recommended for whoever needs to paste some code.\r\nyou can use F5 to run the script on the current file.\r\nit only works on windows.","install_details":"put post_rafb.pl in your Vim folder\r\nadd the following line to your vimrc\r\n:map <F5> :!perl \"D:\\Program Files\\Vim\\post_rafb.pl\" \"%:p\"<Enter><Enter>\r\nclose and open again vim and it will work\r\n(be carefull at D:\\ , it may not be your install path)","5":"put post_rafb.pl in your Vim folder\r\nadd the following line to your vimrc\r\n:map <F5> :!perl \"D:\\Program Files\\Vim\\post_rafb.pl\" \"%:p\"<Enter><Enter>\r\nclose and open again vim and it will work\r\n(be carefull at D:\\ , it may not be your install path)","first_name":"Petrea","6":"Petrea","last_name":"Stefan","7":"Stefan","releases":[{"0":"1889","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"post_rafb.pl","4":"post_rafb.pl","src_id":"7076","5":"7076","creation_date":"1178566764","6":"1178566764"}]},"1888":{"script_id":"1888","0":"1888","script_name":"DiffGoFile","1":"DiffGoFile","script_type":"utility","2":"utility","summary":"Jump to file from diff output","3":"Jump to file from diff output","description":"Script home: https:\/\/github.com\/vlmarek\/DiffGoFile\r\n\r\n\r\nDescription:\r\nIf you are editing diff file and you want to jump quickly to corresponding source files, function DiffGoFile does that. Place cursor on the spot in diff file which interests you, call DiffGoFile and you will be presented with the source file exactly at the place you were looking at. Currently only unified diff is supported, but the script has framework for adding more types.\r\n\r\nInvocation:\r\nPlace cursor on the line you are interested in and\r\n:call DiffGoFile('X')\r\nWhere X is one of: n - open in New window\r\n                   v - open in Vertical split\r\n                   h - open in Horizontal split\r\n                   t - open in new Tab\r\n\r\nConfiguration:\r\nYou may wish to setup a hotkey, I'm using CTRL-] (:tag) for example\r\n\r\nautocmd FileType diff nnoremap <buffer> <C-]> :call DiffGoFile('n')<CR>\r\n","4":"Script home: https:\/\/github.com\/vlmarek\/DiffGoFile\r\n\r\n\r\nDescription:\r\nIf you are editing diff file and you want to jump quickly to corresponding source files, function DiffGoFile does that. Place cursor on the spot in diff file which interests you, call DiffGoFile and you will be presented with the source file exactly at the place you were looking at. Currently only unified diff is supported, but the script has framework for adding more types.\r\n\r\nInvocation:\r\nPlace cursor on the line you are interested in and\r\n:call DiffGoFile('X')\r\nWhere X is one of: n - open in New window\r\n                   v - open in Vertical split\r\n                   h - open in Horizontal split\r\n                   t - open in new Tab\r\n\r\nConfiguration:\r\nYou may wish to setup a hotkey, I'm using CTRL-] (:tag) for example\r\n\r\nautocmd FileType diff nnoremap <buffer> <C-]> :call DiffGoFile('n')<CR>\r\n","install_details":"If you are upgrading from version 1\r\n  - remove ~\/.vim\/plugin\/diffgofile.vim\r\n\r\nCopy the file to the proper location\r\n  - mkdir -p ~\/.vim\/ftplugin\r\n  - cp diff_gofile.vim ~\/.vim\/ftplugin\r\n\r\nMake sure that you are using ftplugins\r\n  - add \"filetype plugin on\" to your ~\/.vimrc\r\n","5":"If you are upgrading from version 1\r\n  - remove ~\/.vim\/plugin\/diffgofile.vim\r\n\r\nCopy the file to the proper location\r\n  - mkdir -p ~\/.vim\/ftplugin\r\n  - cp diff_gofile.vim ~\/.vim\/ftplugin\r\n\r\nMake sure that you are using ftplugins\r\n  - add \"filetype plugin on\" to your ~\/.vimrc\r\n","first_name":"Vladimir","6":"Vladimir","last_name":"Marek","7":"Marek","releases":[{"0":"1888","vim_version":"6.0","1":"6.0","script_version":"4","2":"4","version_comment":"More clever repository root detection\r\nDocumentattion","3":"More clever repository root detection\r\nDocumentattion","package":"diffgofile.zip","4":"diffgofile.zip","src_id":"20662","5":"20662","creation_date":"1376648702","6":"1376648702"},{"0":"1888","vim_version":"7.0","1":"7.0","script_version":"2","2":"2","version_comment":"* Ability to open the source file in new buffer\/vertical split\/horizontal split\/new tab\r\n* Script was reworked to became ftplugin","3":"* Ability to open the source file in new buffer\/vertical split\/horizontal split\/new tab\r\n* Script was reworked to became ftplugin","package":"diff_gofile.vim","4":"diff_gofile.vim","src_id":"7090","5":"7090","creation_date":"1178787670","6":"1178787670"},{"0":"1888","vim_version":"7.0","1":"7.0","script_version":"1","2":"1","version_comment":"Initial upload","3":"Initial upload","package":"diffgofile.vim","4":"diffgofile.vim","src_id":"7075","5":"7075","creation_date":"1178509404","6":"1178509404"}]},"1887":{"script_id":"1887","0":"1887","script_name":"AnyPrinter","1":"AnyPrinter","script_type":"utility","2":"utility","summary":"Lets you insert a print statement quickly in any language","3":"Lets you insert a print statement quickly in any language","description":"\" This is a  simple script to quicky insert a print statement in your code.\r\n\" Currently supported languages are : \r\n\"       C\r\n\"       Scheme, Lisp , OCaml\/Omlet, Haskell\r\n\"       Java\r\n\" It also indents current line and puts the cursor where you expect it to be, in\r\n\" insert mode of course !\r\n\r\nFor example, in C, it would insert a printf(\"X\"); while in Scheme, you'd have a (display X), where X is the cursor position.\r\n\r\nMapped to <Leader>P in normal mode\r\nabbreviated to pap in insert mode (as in \"PrintAPrint\")\r\n\r\nTODO :\r\nMore languages to be added as I'm requested.\r\nSome more idiomatic statements may replace those I chose, and the possibility to choose between several printers ? (print, display, pretty-print, show....)\r\n","4":"\" This is a  simple script to quicky insert a print statement in your code.\r\n\" Currently supported languages are : \r\n\"       C\r\n\"       Scheme, Lisp , OCaml\/Omlet, Haskell\r\n\"       Java\r\n\" It also indents current line and puts the cursor where you expect it to be, in\r\n\" insert mode of course !\r\n\r\nFor example, in C, it would insert a printf(\"X\"); while in Scheme, you'd have a (display X), where X is the cursor position.\r\n\r\nMapped to <Leader>P in normal mode\r\nabbreviated to pap in insert mode (as in \"PrintAPrint\")\r\n\r\nTODO :\r\nMore languages to be added as I'm requested.\r\nSome more idiomatic statements may replace those I chose, and the possibility to choose between several printers ? (print, display, pretty-print, show....)\r\n","install_details":"Simply drop in your plugin directory !","5":"Simply drop in your plugin directory !","first_name":"Adrien","6":"Adrien","last_name":"(Axioplase::Pied)","7":"(Axioplase::Pied)","releases":[{"0":"1887","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"AnyPrinter.vim","4":"AnyPrinter.vim","src_id":"7073","5":"7073","creation_date":"1178379645","6":"1178379645"}]},"1886":{"script_id":"1886","0":"1886","script_name":"nginx.vim","1":"nginx.vim","script_type":"syntax","2":"syntax","summary":"initial version","3":"initial version","description":"nginx.vim highlights configuration files for nginx, the high-performance web server (see http:\/\/nginx.net).","4":"nginx.vim highlights configuration files for nginx, the high-performance web server (see http:\/\/nginx.net).","install_details":"Download nginx.vim to ~\/.vim\/syntax\/, and then add this line to ~\/.vim\/filetype.vim:\r\n\r\nau BufRead,BufNewFile \/etc\/nginx\/*,\/usr\/local\/nginx\/conf\/* if &ft == '' | setfiletype nginx | endif\r\n\r\n(adjust the path to your nginx installation)","5":"Download nginx.vim to ~\/.vim\/syntax\/, and then add this line to ~\/.vim\/filetype.vim:\r\n\r\nau BufRead,BufNewFile \/etc\/nginx\/*,\/usr\/local\/nginx\/conf\/* if &ft == '' | setfiletype nginx | endif\r\n\r\n(adjust the path to your nginx installation)","first_name":"Evan","6":"Evan","last_name":"Miller","7":"Miller","releases":[{"0":"1886","vim_version":"6.0","1":"6.0","script_version":"0.3.3","2":"0.3.3","version_comment":"Fix comment detection when tabs are present.","3":"Fix comment detection when tabs are present.","package":"nginx.vim","4":"nginx.vim","src_id":"19394","5":"19394","creation_date":"1358654440","6":"1358654440"},{"0":"1886","vim_version":"6.0","1":"6.0","script_version":"0.3.2","2":"0.3.2","version_comment":"Highlight comments properly near {'s. Thanks to Eric Herot","3":"Highlight comments properly near {'s. Thanks to Eric Herot","package":"nginx.vim","4":"nginx.vim","src_id":"14376","5":"14376","creation_date":"1290716594","6":"1290716594"},{"0":"1886","vim_version":"6.0","1":"6.0","script_version":"0.3.1","2":"0.3.1","version_comment":"Bugfix: lines with \"{\" did not show in the comment color when prefixed by \"#\".","3":"Bugfix: lines with \"{\" did not show in the comment color when prefixed by \"#\".","package":"nginx.vim","4":"nginx.vim","src_id":"12990","5":"12990","creation_date":"1273598897","6":"1273598897"},{"0":"1886","vim_version":"6.0","1":"6.0","script_version":"0.3","2":"0.3","version_comment":"Update to work with the latest Nginx directives (as of 0.8.32) and 3rd party modules. Thanks to Sergey Bochenkov.","3":"Update to work with the latest Nginx directives (as of 0.8.32) and 3rd party modules. Thanks to Sergey Bochenkov.","package":"nginx.vim","4":"nginx.vim","src_id":"12453","5":"12453","creation_date":"1266716939","6":"1266716939"},{"0":"1886","vim_version":"6.0","1":"6.0","script_version":"0.2","2":"0.2","version_comment":"Support more modules and keywords. Thanks to Bruno Michel.","3":"Support more modules and keywords. Thanks to Bruno Michel.","package":"nginx.vim","4":"nginx.vim","src_id":"11456","5":"11456","creation_date":"1254267728","6":"1254267728"},{"0":"1886","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"nginx.vim","4":"nginx.vim","src_id":"7071","5":"7071","creation_date":"1178373337","6":"1178373337"}]},"1885":{"script_id":"1885","0":"1885","script_name":"scmCloseParens","1":"scmCloseParens","script_type":"utility","2":"utility","summary":"Lets you easily close all open parens up to the cursor line.","3":"Lets you easily close all open parens up to the cursor line.","description":"Lets you easily close all open parens up to the cursor line.\r\n\r\nI tested it quickly with Scheme, but it should also work with Lisp.\r\n\r\n(define foo\r\n  (lambda(x)\r\n    (+ x 1\r\n\r\nPut your cursor on the last line (or below), and type <Leader>p\r\nIt will become\r\n\r\n(define foo\r\n  (lambda(x)\r\n    (+ x 1)))\r\n\r\nI chose \"p\" as in \"parens\", for it is easy to remember. I would have preferred \"c\" as in \"close\", but <leader>c is already taken by the good EnhancedCommentify :D\r\n\r\n\r\nI apologize for this script beeing a dirty quick hack, but writing in vim's script language is a real pain, and this script is enough useful to me to choose to share it.\r\nI should at least clean it by the following weeks.","4":"Lets you easily close all open parens up to the cursor line.\r\n\r\nI tested it quickly with Scheme, but it should also work with Lisp.\r\n\r\n(define foo\r\n  (lambda(x)\r\n    (+ x 1\r\n\r\nPut your cursor on the last line (or below), and type <Leader>p\r\nIt will become\r\n\r\n(define foo\r\n  (lambda(x)\r\n    (+ x 1)))\r\n\r\nI chose \"p\" as in \"parens\", for it is easy to remember. I would have preferred \"c\" as in \"close\", but <leader>c is already taken by the good EnhancedCommentify :D\r\n\r\n\r\nI apologize for this script beeing a dirty quick hack, but writing in vim's script language is a real pain, and this script is enough useful to me to choose to share it.\r\nI should at least clean it by the following weeks.","install_details":"simply drop it into .vim\/plugin\/ that should be enough.","5":"simply drop it into .vim\/plugin\/ that should be enough.","first_name":"Adrien","6":"Adrien","last_name":"(Axioplase::Pied)","7":"(Axioplase::Pied)","releases":[{"0":"1885","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"scmCloseParens.vim","4":"scmCloseParens.vim","src_id":"7070","5":"7070","creation_date":"1178313814","6":"1178313814"}]},"1884":{"script_id":"1884","0":"1884","script_name":"python_import.vim","1":"python_import.vim","script_type":"ftplugin","2":"ftplugin","summary":"automatically remove unused imports and clean up the rest","3":"automatically remove unused imports and clean up the rest","description":"This plugin defines a function for automatically cleaning up the imports\r\nin a python module or program. It does two things:\r\n\r\n - removes unused imports\r\n - sorts and formats the remaining imports\r\n\r\nThis function is mapped to <LocalLeader>i (for \"import\") in two contexts.\r\nIn Normal mode, it operates on the current paragraph.\r\nIn Visual mode, it operates on the selected range.\r\n\r\nThe python 'tokenize' module is used to determine which symbols are used\r\nin the current buffer, so the script is pretty good at identifying unused imports.\r\n\r\nThe import formatting style was chosen to work well with grep - the name of\r\nthe module and the symbols imported from it are guaranteed to always\r\nappear on the same line.","4":"This plugin defines a function for automatically cleaning up the imports\r\nin a python module or program. It does two things:\r\n\r\n - removes unused imports\r\n - sorts and formats the remaining imports\r\n\r\nThis function is mapped to <LocalLeader>i (for \"import\") in two contexts.\r\nIn Normal mode, it operates on the current paragraph.\r\nIn Visual mode, it operates on the selected range.\r\n\r\nThe python 'tokenize' module is used to determine which symbols are used\r\nin the current buffer, so the script is pretty good at identifying unused imports.\r\n\r\nThe import formatting style was chosen to work well with grep - the name of\r\nthe module and the symbols imported from it are guaranteed to always\r\nappear on the same line.","install_details":"Just drop the file in ~\/.vim\/ftplugin.\r\n\r\nvim must be compiled with +python.","5":"Just drop the file in ~\/.vim\/ftplugin.\r\n\r\nvim must be compiled with +python.","first_name":"Jason","6":"Jason","last_name":"Lunz","7":"Lunz","releases":[{"0":"1884","vim_version":"7.0","1":"7.0","script_version":"0.2","2":"0.2","version_comment":"clean up imports ;)","3":"clean up imports ;)","package":"python_import.vim","4":"python_import.vim","src_id":"21292","5":"21292","creation_date":"1389228774","6":"1389228774"},{"0":"1884","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"python_import.vim","4":"python_import.vim","src_id":"7069","5":"7069","creation_date":"1178298288","6":"1178298288"}]},"1883":{"script_id":"1883","0":"1883","script_name":"felix.vim","1":"felix.vim","script_type":"syntax","2":"syntax","summary":"Felix language syntax highlighting","3":"Felix language syntax highlighting","description":"Felix language syntax highlighting","4":"Felix language syntax highlighting","install_details":"","5":"","first_name":"john","6":"john","last_name":"skaller","7":"skaller","releases":[{"0":"1883","vim_version":"6.0","1":"6.0","script_version":"1","2":"1","version_comment":"Initial upload","3":"Initial upload","package":"felix.vim","4":"felix.vim","src_id":"7067","5":"7067","creation_date":"1178279315","6":"1178279315"}]},"1882":{"script_id":"1882","0":"1882","script_name":"Increment and Decrement number","1":"Increment and Decrement number","script_type":"utility","2":"utility","summary":"Increment or decrement the number which is under your cursor","3":"Increment or decrement the number which is under your cursor","description":"In the command mode, move your cursor on the number which you want to change.\r\nThen use SHIFT and + to increment the number \r\nor SHIFT and - to decrement the number.","4":"In the command mode, move your cursor on the number which you want to change.\r\nThen use SHIFT and + to increment the number \r\nor SHIFT and - to decrement the number.","install_details":"Put the file in the plugin folder... that's all","5":"Put the file in the plugin folder... that's all","first_name":"Sudipta","6":"Sudipta","last_name":"Ghorui","7":"Ghorui","releases":[{"0":"1882","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"incrDcrNumber.vim","4":"incrDcrNumber.vim","src_id":"7064","5":"7064","creation_date":"1178252698","6":"1178252698"}]},"1881":{"script_id":"1881","0":"1881","script_name":"svndiff","1":"svndiff","script_type":"utility","2":"utility","summary":"Shows colored signs in buffer indicating diff with original svn\/git file,","3":"Shows colored signs in buffer indicating diff with original svn\/git file,","description":"Screenshot available at http:\/\/zevv.nl\/play\/code\/vimscripts\/\r\n\r\nIntroduction\r\n------------\r\n\r\nNOTE: This plugin is unix-only!\r\n\r\nAn small vim 7.0 plugin for showing RCS diff information in a file while\r\nediting. This plugin runs a diff between the current buffer and the original\r\nfile from the version control system, and shows coloured signs indicating\r\nwhere the buffer differs from the original file from the repository. The\r\noriginal text is not shown, only signs are used to indicate where changes were\r\nmade. With proper key bindings configured, fast navigation between changed\r\nblocks is also provided.\r\n\r\nDespite the name 'svndiff' this plugin supports the following RCS systems:\r\n\r\n- Subversion\r\n- Git\r\n- Mercurial\r\n- Perforce \/ p4\r\n- CVS\r\n- Fossil\r\n\r\nThe type of RCS will be detected when first issuing a svndiff command on\r\nthe file.\r\n\r\nThe following symbols and syntax highlight groups are used for the signs:\r\n\r\n  > DiffAdd:    Newly added lines. (default=blue)\r\n\r\n  ! DiffChange: Lines which are changed from the original. (default=cyan)\r\n\r\n  < DiffDel:    Applied to the lines directly above and below a deleted block\r\n                (default=magenta)\r\n\r\nUsage\r\n-----\r\n\r\nThe plugin defines one function: Svndiff(). This function figures out the\r\ndifference between the current buffer and it's RCS original, and adds the\r\nsigns at the places where the buffer differs from the original file from svn\r\nor git. You'll need to call this function after making changes to update the\r\nhighlighting.\r\n\r\nThe function takes one argument specifying an additional action to perform:\r\n\r\n  \"prev\"  : jump to the previous different block\r\n  \"next\"  : jump to the next different block\r\n  \"clear\" : clean up all signs\r\n\r\nYou might want to map some keys to run the Svndiff function. For\r\nexample, add to your .vimrc:\r\n\r\n  noremap <F3> :call Svndiff(\"prev\")<CR>\r\n  noremap <F4> :call Svndiff(\"next\")<CR>\r\n  noremap <F5> :call Svndiff(\"clear\")<CR>\r\n\r\n\r\nConfiguration\r\n-------------\r\n\r\nThe following configuration variables are availabe:\r\n\r\n* g:svndiff_autoupdate\r\n\r\n  If this variable is defined, svndiff will automatically update the signs\r\n  when the user stops typing for a short while, and when leaving insert\r\n  mode. This might slow things down on large files, so use with caution.\r\n  The vim variable 'updatetime' can be used to set the auto-update interval,\r\n  but note that changing this variable other effects as well. (refer to the\r\n  vim docs for more info)\r\n  To use, add to your .vimrc:\r\n\r\n  let g:svndiff_autoupdate = 1\r\n\r\n* g:svndiff_one_sign_delete\r\n\r\n  Normally, two 'delete' signs are placed around the location where\r\n  text was deleted. When this variable is defined, only one sign is\r\n  placed, above the location of the deleted text.\r\n  To use, add to your .vimrc:\r\n\r\n  let g:svndiff_one_sign_delete = 1\r\n\r\nColors\r\n------\r\n\r\nPersonally, I find the following colours more intuitive for diff colours:\r\nred=deleted, green=added, yellow=changed. If you want to use these colours,\r\ntry adding the following lines to your .vimrc\r\n\r\nhi DiffAdd      ctermfg=0 ctermbg=2 guibg='green'\r\nhi DiffDelete   ctermfg=0 ctermbg=1 guibg='red'\r\nhi DiffChange   ctermfg=0 ctermbg=3 guibg='yellow'\r\n\r\nChangelog\r\n---------\r\n\r\n1.0 2007-04-02  Initial version\r\n\r\n1.1 2007-04-02  Added goto prev\/next diffblock commands\r\n\r\n1.2 2007-06-14  Updated diff arguments from -u0 (obsolete) to -U0\r\n\r\n2.0 2007-08-16  Changed from syntax highlighting to using signs, thanks\r\n                to Noah Spurrier for the idea. NOTE: the name of the\r\n                function changed from Svndiff_show() to Svndiff(), so\r\n                you might need to update your .vimrc mappings!\r\n\r\n3.0 2008-02-02  Redesign with some ideas from Jan Bezdekovsky. The\r\n                diff is only updated when the buffer actually changes,\r\n                cleanup of signs is now done properly and some info\r\n                about each diff block is printed in the status line.\r\n\r\n3.1 2008-02-04  Fixed bug that broke plugin in non-english locales, thanks\r\n                to Bernhard Walle for the patch\r\n\r\n3.2 2008-02-27  The latest rewrite broke vim 6 compatiblity. The plugin\r\n                is now simply disabled for older vim versions to avoid\r\n                a lot of warnings when loading.\r\n\r\n4.0 2008-11-24  Added GIT support. The RCS type is now detected (svn\/git)\r\n\r\n4.1 2008-11-25  Added CVS support.\r\n\r\n4.2 2009-07-31  Added support for proper handling of non-unix file formats\r\n                which use different newline conventions (dos, mac)\r\n\r\n4.3 2010-05-08  Added support for Mercurial, fixed git support (thanks\r\n                Frankovskyi Bogdan)\r\n\r\n4.4 2011-03-30  Added support for perforce\/p4 (thanks, Timandahaf)\r\n\r\n4.5 2011-10-09  Bugfix when trying to use svndiff in a new fileless buffer (Frankovskyi Bogdan)\r\n\r\n4.6 2012-06-02  Added support for the Fossil SCM (Andrea Federico Grisotto)\r\n\r\n","4":"Screenshot available at http:\/\/zevv.nl\/play\/code\/vimscripts\/\r\n\r\nIntroduction\r\n------------\r\n\r\nNOTE: This plugin is unix-only!\r\n\r\nAn small vim 7.0 plugin for showing RCS diff information in a file while\r\nediting. This plugin runs a diff between the current buffer and the original\r\nfile from the version control system, and shows coloured signs indicating\r\nwhere the buffer differs from the original file from the repository. The\r\noriginal text is not shown, only signs are used to indicate where changes were\r\nmade. With proper key bindings configured, fast navigation between changed\r\nblocks is also provided.\r\n\r\nDespite the name 'svndiff' this plugin supports the following RCS systems:\r\n\r\n- Subversion\r\n- Git\r\n- Mercurial\r\n- Perforce \/ p4\r\n- CVS\r\n- Fossil\r\n\r\nThe type of RCS will be detected when first issuing a svndiff command on\r\nthe file.\r\n\r\nThe following symbols and syntax highlight groups are used for the signs:\r\n\r\n  > DiffAdd:    Newly added lines. (default=blue)\r\n\r\n  ! DiffChange: Lines which are changed from the original. (default=cyan)\r\n\r\n  < DiffDel:    Applied to the lines directly above and below a deleted block\r\n                (default=magenta)\r\n\r\nUsage\r\n-----\r\n\r\nThe plugin defines one function: Svndiff(). This function figures out the\r\ndifference between the current buffer and it's RCS original, and adds the\r\nsigns at the places where the buffer differs from the original file from svn\r\nor git. You'll need to call this function after making changes to update the\r\nhighlighting.\r\n\r\nThe function takes one argument specifying an additional action to perform:\r\n\r\n  \"prev\"  : jump to the previous different block\r\n  \"next\"  : jump to the next different block\r\n  \"clear\" : clean up all signs\r\n\r\nYou might want to map some keys to run the Svndiff function. For\r\nexample, add to your .vimrc:\r\n\r\n  noremap <F3> :call Svndiff(\"prev\")<CR>\r\n  noremap <F4> :call Svndiff(\"next\")<CR>\r\n  noremap <F5> :call Svndiff(\"clear\")<CR>\r\n\r\n\r\nConfiguration\r\n-------------\r\n\r\nThe following configuration variables are availabe:\r\n\r\n* g:svndiff_autoupdate\r\n\r\n  If this variable is defined, svndiff will automatically update the signs\r\n  when the user stops typing for a short while, and when leaving insert\r\n  mode. This might slow things down on large files, so use with caution.\r\n  The vim variable 'updatetime' can be used to set the auto-update interval,\r\n  but note that changing this variable other effects as well. (refer to the\r\n  vim docs for more info)\r\n  To use, add to your .vimrc:\r\n\r\n  let g:svndiff_autoupdate = 1\r\n\r\n* g:svndiff_one_sign_delete\r\n\r\n  Normally, two 'delete' signs are placed around the location where\r\n  text was deleted. When this variable is defined, only one sign is\r\n  placed, above the location of the deleted text.\r\n  To use, add to your .vimrc:\r\n\r\n  let g:svndiff_one_sign_delete = 1\r\n\r\nColors\r\n------\r\n\r\nPersonally, I find the following colours more intuitive for diff colours:\r\nred=deleted, green=added, yellow=changed. If you want to use these colours,\r\ntry adding the following lines to your .vimrc\r\n\r\nhi DiffAdd      ctermfg=0 ctermbg=2 guibg='green'\r\nhi DiffDelete   ctermfg=0 ctermbg=1 guibg='red'\r\nhi DiffChange   ctermfg=0 ctermbg=3 guibg='yellow'\r\n\r\nChangelog\r\n---------\r\n\r\n1.0 2007-04-02  Initial version\r\n\r\n1.1 2007-04-02  Added goto prev\/next diffblock commands\r\n\r\n1.2 2007-06-14  Updated diff arguments from -u0 (obsolete) to -U0\r\n\r\n2.0 2007-08-16  Changed from syntax highlighting to using signs, thanks\r\n                to Noah Spurrier for the idea. NOTE: the name of the\r\n                function changed from Svndiff_show() to Svndiff(), so\r\n                you might need to update your .vimrc mappings!\r\n\r\n3.0 2008-02-02  Redesign with some ideas from Jan Bezdekovsky. The\r\n                diff is only updated when the buffer actually changes,\r\n                cleanup of signs is now done properly and some info\r\n                about each diff block is printed in the status line.\r\n\r\n3.1 2008-02-04  Fixed bug that broke plugin in non-english locales, thanks\r\n                to Bernhard Walle for the patch\r\n\r\n3.2 2008-02-27  The latest rewrite broke vim 6 compatiblity. The plugin\r\n                is now simply disabled for older vim versions to avoid\r\n                a lot of warnings when loading.\r\n\r\n4.0 2008-11-24  Added GIT support. The RCS type is now detected (svn\/git)\r\n\r\n4.1 2008-11-25  Added CVS support.\r\n\r\n4.2 2009-07-31  Added support for proper handling of non-unix file formats\r\n                which use different newline conventions (dos, mac)\r\n\r\n4.3 2010-05-08  Added support for Mercurial, fixed git support (thanks\r\n                Frankovskyi Bogdan)\r\n\r\n4.4 2011-03-30  Added support for perforce\/p4 (thanks, Timandahaf)\r\n\r\n4.5 2011-10-09  Bugfix when trying to use svndiff in a new fileless buffer (Frankovskyi Bogdan)\r\n\r\n4.6 2012-06-02  Added support for the Fossil SCM (Andrea Federico Grisotto)\r\n\r\n","install_details":"Copy the file into your ~\/.vim\/plugin directory, and optionally create a keymap as described above.","5":"Copy the file into your ~\/.vim\/plugin directory, and optionally create a keymap as described above.","first_name":"Ico","6":"Ico","last_name":"-","7":"-","releases":[{"0":"1881","vim_version":"7.0","1":"7.0","script_version":"4.7","2":"4.7","version_comment":"Fixed git diffs when cwd is not the top git directory.","3":"Fixed git diffs when cwd is not the top git directory.","package":"svndiff.vim","4":"svndiff.vim","src_id":"19933","5":"19933","creation_date":"1366896050","6":"1366896050"},{"0":"1881","vim_version":"7.0","1":"7.0","script_version":"4.6","2":"4.6","version_comment":"Added support for Fossil ","3":"Added support for Fossil ","package":"svndiff.vim","4":"svndiff.vim","src_id":"18079","5":"18079","creation_date":"1338616525","6":"1338616525"},{"0":"1881","vim_version":"7.0","1":"7.0","script_version":"4.6","2":"4.6","version_comment":"Added support for the Fossil SCM","3":"Added support for the Fossil SCM","package":"svndiff.vim","4":"svndiff.vim","src_id":"18078","5":"18078","creation_date":"1338616420","6":"1338616420"},{"0":"1881","vim_version":"7.0","1":"7.0","script_version":"4.5","2":"4.5","version_comment":"Bugfix when trying to use svndiff on a new buffer without file","3":"Bugfix when trying to use svndiff on a new buffer without file","package":"svndiff.vim","4":"svndiff.vim","src_id":"16644","5":"16644","creation_date":"1318170177","6":"1318170177"},{"0":"1881","vim_version":"7.0","1":"7.0","script_version":"4.4","2":"4.4","version_comment":"Added support for perforce\/p4.\r\n\r\nSupported RCS software is now subversion, git, mercurial, cvs and perforce!\r\n","3":"Added support for perforce\/p4.\r\n\r\nSupported RCS software is now subversion, git, mercurial, cvs and perforce!\r\n","package":"svndiff.vim","4":"svndiff.vim","src_id":"15335","5":"15335","creation_date":"1301466646","6":"1301466646"},{"0":"1881","vim_version":"6.0","1":"6.0","script_version":"4.3","2":"4.3","version_comment":"Added support for Mercurial, fixed Git support","3":"Added support for Mercurial, fixed Git support","package":"svndiff.vim","4":"svndiff.vim","src_id":"12972","5":"12972","creation_date":"1273298358","6":"1273298358"},{"0":"1881","vim_version":"6.0","1":"6.0","script_version":"4.1","2":"4.1","version_comment":"Added CVS support. svndiff now works with subversion, GIT and CVS. ","3":"Added CVS support. svndiff now works with subversion, GIT and CVS. ","package":"svndiff.vim","4":"svndiff.vim","src_id":"9564","5":"9564","creation_date":"1227618008","6":"1227618008"},{"0":"1881","vim_version":"6.0","1":"6.0","script_version":"4.0","2":"4.0","version_comment":"Added support for GIT, repository type is detected at runtime (subversion \/ git)","3":"Added support for GIT, repository type is detected at runtime (subversion \/ git)","package":"svndiff.vim","4":"svndiff.vim","src_id":"9558","5":"9558","creation_date":"1227539327","6":"1227539327"},{"0":"1881","vim_version":"7.0","1":"7.0","script_version":"3.2","2":"3.2","version_comment":"The latest rewrite broke vim 6 compatiblity. The plugin is now simply disabled for older vim versions to avoid a lot of warnings when loading.\r\n","3":"The latest rewrite broke vim 6 compatiblity. The plugin is now simply disabled for older vim versions to avoid a lot of warnings when loading.\r\n","package":"svndiff.vim","4":"svndiff.vim","src_id":"8355","5":"8355","creation_date":"1204112736","6":"1204112736"},{"0":"1881","vim_version":"6.0","1":"6.0","script_version":"3.1","2":"3.1","version_comment":"Fixed script behaviour for non-english locales.","3":"Fixed script behaviour for non-english locales.","package":"svndiff.vim","4":"svndiff.vim","src_id":"8234","5":"8234","creation_date":"1202104609","6":"1202104609"},{"0":"1881","vim_version":"6.0","1":"6.0","script_version":"3.0","2":"3.0","version_comment":"Major redesign of the plugin:\r\n\r\n* auto-update feature highlights svn diff signs while editing\r\n* signs from other sources (debugger, etc) are no longer effected\r\n* better performance, diff is only executed when code is actually modified","3":"Major redesign of the plugin:\r\n\r\n* auto-update feature highlights svn diff signs while editing\r\n* signs from other sources (debugger, etc) are no longer effected\r\n* better performance, diff is only executed when code is actually modified","package":"svndiff.vim","4":"svndiff.vim","src_id":"8231","5":"8231","creation_date":"1202078293","6":"1202078293"},{"0":"1881","vim_version":"7.0","1":"7.0","script_version":"2.0","2":"2.0","version_comment":"svndiff now uses tags to indicated the difference between the buffer and the original file, so it leaves intact the original syntax highlighting.","3":"svndiff now uses tags to indicated the difference between the buffer and the original file, so it leaves intact the original syntax highlighting.","package":"svndiff.vim","4":"svndiff.vim","src_id":"7505","5":"7505","creation_date":"1187227875","6":"1187227875"},{"0":"1881","vim_version":"6.0","1":"6.0","script_version":"1.2","2":"1.2","version_comment":"updated to work with recent version of diff (-u0 option was obsolete, changed to -U0)","3":"updated to work with recent version of diff (-u0 option was obsolete, changed to -U0)","package":"svndiff.vim","4":"svndiff.vim","src_id":"7244","5":"7244","creation_date":"1181790765","6":"1181790765"},{"0":"1881","vim_version":"7.0","1":"7.0","script_version":"1.1","2":"1.1","version_comment":"Added jump-to-prev\/next ","3":"Added jump-to-prev\/next ","package":"svndiff.vim","4":"svndiff.vim","src_id":"7057","5":"7057","creation_date":"1178116947","6":"1178116947"}]},"1880":{"script_id":"1880","0":"1880","script_name":"ck.vim","1":"ck.vim","script_type":"syntax","2":"syntax","summary":"ChucK Audio Programming Language Syntax","3":"ChucK Audio Programming Language Syntax","description":"Syntax file for the ChucK Audio Programming Language http:\/\/chuck.cs.princeton.edu\/","4":"Syntax file for the ChucK Audio Programming Language http:\/\/chuck.cs.princeton.edu\/","install_details":"NOTE: in order to obtain syntax highlighting in Chuck programs just follow the\r\n      steps below or in case you don't have root privileges follow Graham Percival's tip :\r\n      1. copy this file into \/usr\/share\/vim\/vim62\/syntax.\r\n      2. add the following line in \/usr\/share\/vim\/filetype.vim,\r\n\r\n               au BufNewFile,BufRead *.ck          setf ck\r\n","5":"NOTE: in order to obtain syntax highlighting in Chuck programs just follow the\r\n      steps below or in case you don't have root privileges follow Graham Percival's tip :\r\n      1. copy this file into \/usr\/share\/vim\/vim62\/syntax.\r\n      2. add the following line in \/usr\/share\/vim\/filetype.vim,\r\n\r\n               au BufNewFile,BufRead *.ck          setf ck\r\n","first_name":"Adam","6":"Adam","last_name":"Pense","7":"Pense","releases":[{"0":"1880","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial Version","3":"Initial Version","package":"ck.vim","4":"ck.vim","src_id":"7052","5":"7052","creation_date":"1178104548","6":"1178104548"}]},"1879":{"script_id":"1879","0":"1879","script_name":"AutoComplPop","1":"AutoComplPop","script_type":"utility","2":"utility","summary":"Automatically opens popup menu for completions","3":"Automatically opens popup menu for completions","description":"Repository:\r\n  https:\/\/bitbucket.org\/ns9tks\/vim-autocomplpop\/\r\n\r\nIssues:\r\n  http:\/\/bitbucket.org\/ns9tks\/vim-autocomplpop\/issues\/\r\n\r\nDownload latest(development) version\r\n  https:\/\/bitbucket.org\/ns9tks\/vim-autocomplpop\/get\/tip.zip\r\n\r\n==============================================================================\r\nINTRODUCTION                                                *acp-introduction*\r\n\r\nWith this plugin, your vim comes to automatically opens popup menu for\r\ncompletions when you enter characters or move the cursor in Insert mode. It\r\nwon't prevent you continuing entering characters.\r\n\r\n\r\n==============================================================================\r\nINSTALLATION                                                *acp-installation*\r\n\r\nPut all files into your runtime directory. If you have the zip file, extract\r\nit to your runtime directory.\r\n\r\nYou should place the files as follows:\r\n>\r\n        <your runtime directory>\/plugin\/acp.vim\r\n        <your runtime directory>\/doc\/acp.txt\r\n        ...\r\n<\r\nIf you disgust to jumble up this plugin and other plugins in your runtime\r\ndirectory, put the files into new directory and just add the directory path to\r\n'runtimepath'. It's easy to uninstall the plugin.\r\n\r\nAnd then update your help tags files to enable fuzzyfinder help. See\r\n|add-local-help| for details.\r\n\r\n\r\n==============================================================================\r\nUSAGE                                                              *acp-usage*\r\n\r\nOnce this plugin is installed, auto-popup is enabled at startup by default.\r\n\r\nWhich completion method is used depends on the text before the cursor. The\r\ndefault behavior is as follows:\r\n\r\n        kind      filetype    text before the cursor ~\r\n        Keyword   *           two keyword characters\r\n        Filename  *           a filename character + a path separator \r\n                              + 0 or more filename character\r\n        Omni      ruby        \".\", \"::\" or non-word character + \":\"\r\n                              (|+ruby| required.)\r\n        Omni      python      \".\" (|+python| required.)\r\n        Omni      xml         \"<\", \"<\/\" or (\"<\" + non-\">\" characters + \" \")\r\n        Omni      html\/xhtml  \"<\", \"<\/\" or (\"<\" + non-\">\" characters + \" \")\r\n        Omni      css         (\":\", \";\", \"{\", \"^\", \"@\", or \"!\")\r\n                              + 0 or 1 space\r\n\r\nAlso, you can make user-defined completion and snipMate's trigger completion\r\n(|acp-snipMate|) auto-popup if the options are set.\r\n\r\nThese behavior are customizable.\r\n\r\n                                                                *acp-snipMate*\r\nsnipMate's Trigger Completion ~\r\n\r\nsnipMate's trigger completion enables you to complete a snippet trigger\r\nprovided by snipMate plugin\r\n(http:\/\/www.vim.org\/scripts\/script.php?script_id=2540) and expand it.\r\n\r\n\r\nTo enable auto-popup for this completion, add following function to\r\nplugin\/snipMate.vim:\r\n>\r\n  fun! GetSnipsInCurrentScope()\r\n    let snips = {}\r\n    for scope in [bufnr('%')] + split(&ft, '\\.') + ['_']\r\n      call extend(snips, get(s:snippets, scope, {}), 'keep')\r\n      call extend(snips, get(s:multi_snips, scope, {}), 'keep')\r\n    endfor\r\n    return snips\r\n  endf\r\n<\r\nAnd set |g:acp_behaviorSnipmateLength| option to 1.\r\n\r\nThere is the restriction on this auto-popup, that the word before cursor must\r\nconsist only of uppercase characters.\r\n\r\n                                                               *acp-perl-omni*\r\nPerl Omni-Completion ~\r\n\r\nAutoComplPop supports perl-completion.vim\r\n(http:\/\/www.vim.org\/scripts\/script.php?script_id=2852).\r\n\r\nTo enable auto-popup for this completion, set |g:acp_behaviorPerlOmniLength|\r\noption to 0 or more.\r\n\r\n\r\n==============================================================================\r\n","4":"Repository:\r\n  https:\/\/bitbucket.org\/ns9tks\/vim-autocomplpop\/\r\n\r\nIssues:\r\n  http:\/\/bitbucket.org\/ns9tks\/vim-autocomplpop\/issues\/\r\n\r\nDownload latest(development) version\r\n  https:\/\/bitbucket.org\/ns9tks\/vim-autocomplpop\/get\/tip.zip\r\n\r\n==============================================================================\r\nINTRODUCTION                                                *acp-introduction*\r\n\r\nWith this plugin, your vim comes to automatically opens popup menu for\r\ncompletions when you enter characters or move the cursor in Insert mode. It\r\nwon't prevent you continuing entering characters.\r\n\r\n\r\n==============================================================================\r\nINSTALLATION                                                *acp-installation*\r\n\r\nPut all files into your runtime directory. If you have the zip file, extract\r\nit to your runtime directory.\r\n\r\nYou should place the files as follows:\r\n>\r\n        <your runtime directory>\/plugin\/acp.vim\r\n        <your runtime directory>\/doc\/acp.txt\r\n        ...\r\n<\r\nIf you disgust to jumble up this plugin and other plugins in your runtime\r\ndirectory, put the files into new directory and just add the directory path to\r\n'runtimepath'. It's easy to uninstall the plugin.\r\n\r\nAnd then update your help tags files to enable fuzzyfinder help. See\r\n|add-local-help| for details.\r\n\r\n\r\n==============================================================================\r\nUSAGE                                                              *acp-usage*\r\n\r\nOnce this plugin is installed, auto-popup is enabled at startup by default.\r\n\r\nWhich completion method is used depends on the text before the cursor. The\r\ndefault behavior is as follows:\r\n\r\n        kind      filetype    text before the cursor ~\r\n        Keyword   *           two keyword characters\r\n        Filename  *           a filename character + a path separator \r\n                              + 0 or more filename character\r\n        Omni      ruby        \".\", \"::\" or non-word character + \":\"\r\n                              (|+ruby| required.)\r\n        Omni      python      \".\" (|+python| required.)\r\n        Omni      xml         \"<\", \"<\/\" or (\"<\" + non-\">\" characters + \" \")\r\n        Omni      html\/xhtml  \"<\", \"<\/\" or (\"<\" + non-\">\" characters + \" \")\r\n        Omni      css         (\":\", \";\", \"{\", \"^\", \"@\", or \"!\")\r\n                              + 0 or 1 space\r\n\r\nAlso, you can make user-defined completion and snipMate's trigger completion\r\n(|acp-snipMate|) auto-popup if the options are set.\r\n\r\nThese behavior are customizable.\r\n\r\n                                                                *acp-snipMate*\r\nsnipMate's Trigger Completion ~\r\n\r\nsnipMate's trigger completion enables you to complete a snippet trigger\r\nprovided by snipMate plugin\r\n(http:\/\/www.vim.org\/scripts\/script.php?script_id=2540) and expand it.\r\n\r\n\r\nTo enable auto-popup for this completion, add following function to\r\nplugin\/snipMate.vim:\r\n>\r\n  fun! GetSnipsInCurrentScope()\r\n    let snips = {}\r\n    for scope in [bufnr('%')] + split(&ft, '\\.') + ['_']\r\n      call extend(snips, get(s:snippets, scope, {}), 'keep')\r\n      call extend(snips, get(s:multi_snips, scope, {}), 'keep')\r\n    endfor\r\n    return snips\r\n  endf\r\n<\r\nAnd set |g:acp_behaviorSnipmateLength| option to 1.\r\n\r\nThere is the restriction on this auto-popup, that the word before cursor must\r\nconsist only of uppercase characters.\r\n\r\n                                                               *acp-perl-omni*\r\nPerl Omni-Completion ~\r\n\r\nAutoComplPop supports perl-completion.vim\r\n(http:\/\/www.vim.org\/scripts\/script.php?script_id=2852).\r\n\r\nTo enable auto-popup for this completion, set |g:acp_behaviorPerlOmniLength|\r\noption to 0 or more.\r\n\r\n\r\n==============================================================================\r\n","install_details":"","5":"","first_name":"Takeshi","6":"Takeshi","last_name":"NISHIDA","7":"NISHIDA","releases":[{"0":"1879","vim_version":"7.0","1":"7.0","script_version":"2.14.1","2":"2.14.1","version_comment":"- Changed the way of auto-popup for avoiding an issue about filename completion.\r\n- Fixed a bug that popup menu was opened twice when auto-popup was done.\r\n","3":"- Changed the way of auto-popup for avoiding an issue about filename completion.\r\n- Fixed a bug that popup menu was opened twice when auto-popup was done.\r\n","package":"vim-autocomplpop.zip","4":"vim-autocomplpop.zip","src_id":"11894","5":"11894","creation_date":"1260635600","6":"1260635600"},{"0":"1879","vim_version":"7.0","1":"7.0","script_version":"2.14","2":"2.14","version_comment":"- Added the support for perl-completion.vim.","3":"- Added the support for perl-completion.vim.","package":"vim-autocomplpop.zip","4":"vim-autocomplpop.zip","src_id":"11731","5":"11731","creation_date":"1258296742","6":"1258296742"},{"0":"1879","vim_version":"7.0","1":"7.0","script_version":"2.13","2":"2.13","version_comment":"- Changed to sort snipMate's triggers.\r\n- Fixed a bug that a wasted character was inserted after snipMate's trigger\r\n  completion.\r\n","3":"- Changed to sort snipMate's triggers.\r\n- Fixed a bug that a wasted character was inserted after snipMate's trigger\r\n  completion.\r\n","package":"vim-autocomplpop.zip","4":"vim-autocomplpop.zip","src_id":"11725","5":"11725","creation_date":"1258158877","6":"1258158877"},{"0":"1879","vim_version":"7.0","1":"7.0","script_version":"2.12.1","2":"2.12.1","version_comment":"- Changed to avoid a strange behavior with Microsoft IME.","3":"- Changed to avoid a strange behavior with Microsoft IME.","package":"vim-autocomplpop.zip","4":"vim-autocomplpop.zip","src_id":"11714","5":"11714","creation_date":"1258039096","6":"1258039096"},{"0":"1879","vim_version":"7.0","1":"7.0","script_version":"2.12","2":"2.12","version_comment":"- Added g:acp_behaviorKeywordIgnores option.\r\n- Added g:acp_behaviorUserDefinedMeets option and removed\r\n  g:acp_behaviorUserDefinedPattern.\r\n- Changed to do auto-popup only when a buffer is modified.\r\n- Changed the structure of g:acp_behavior option.\r\n- Changed to reflect a change of behavior options (named g:acp_behavior*)\r\n  any time it is done.\r\n- Fixed a bug that completions after omni completions or snipMate's trigger\r\n  completion were never attempted when no candidate for the former\r\n  completions was found.\r\n","3":"- Added g:acp_behaviorKeywordIgnores option.\r\n- Added g:acp_behaviorUserDefinedMeets option and removed\r\n  g:acp_behaviorUserDefinedPattern.\r\n- Changed to do auto-popup only when a buffer is modified.\r\n- Changed the structure of g:acp_behavior option.\r\n- Changed to reflect a change of behavior options (named g:acp_behavior*)\r\n  any time it is done.\r\n- Fixed a bug that completions after omni completions or snipMate's trigger\r\n  completion were never attempted when no candidate for the former\r\n  completions was found.\r\n","package":"vim-autocomplpop.zip","4":"vim-autocomplpop.zip","src_id":"11706","5":"11706","creation_date":"1257911695","6":"1257911695"},{"0":"1879","vim_version":"7.0","1":"7.0","script_version":"2.11.1","2":"2.11.1","version_comment":"- Fixed a bug that a snipMate's trigger could not be expanded when it was\r\n  completed.\r\n","3":"- Fixed a bug that a snipMate's trigger could not be expanded when it was\r\n  completed.\r\n","package":"vim-autocomplpop.zip","4":"vim-autocomplpop.zip","src_id":"11604","5":"11604","creation_date":"1256642501","6":"1256642501"},{"0":"1879","vim_version":"7.0","1":"7.0","script_version":"2.11","2":"2.11","version_comment":"- Implemented experimental feature which is snipMate's trigger completion.","3":"- Implemented experimental feature which is snipMate's trigger completion.","package":"vim-autocomplpop.zip","4":"vim-autocomplpop.zip","src_id":"11570","5":"11570","creation_date":"1256305164","6":"1256305164"},{"0":"1879","vim_version":"7.0","1":"7.0","script_version":"2.10","2":"2.10","version_comment":"- Improved the response by changing not to attempt any completion when\r\n  keyword characters are entered after a word which has been found that it\r\n  has no completion candidate at the last attempt of completions.\r\n- Improved the response by changing to close popup menu when <BS> was\r\n  pressed and the text before the cursor would not match with the pattern of\r\n  current behavior.\r\n","3":"- Improved the response by changing not to attempt any completion when\r\n  keyword characters are entered after a word which has been found that it\r\n  has no completion candidate at the last attempt of completions.\r\n- Improved the response by changing to close popup menu when <BS> was\r\n  pressed and the text before the cursor would not match with the pattern of\r\n  current behavior.\r\n","package":"vim-autocomplpop.zip","4":"vim-autocomplpop.zip","src_id":"11558","5":"11558","creation_date":"1256212337","6":"1256212337"},{"0":"1879","vim_version":"7.0","1":"7.0","script_version":"2.9","2":"2.9","version_comment":"- Changed default behavior to support XML omni completion.\r\n- Changed default value of g:acp_behaviorKeywordCommand option.\r\n  The option with \"\\<C-p>\" cause a problem which inserts a match without\r\n  <CR> when 'dictionary' has been set and keyword completion is done.\r\n- Changed to show error message when incompatible with a installed vim.\r\n","3":"- Changed default behavior to support XML omni completion.\r\n- Changed default value of g:acp_behaviorKeywordCommand option.\r\n  The option with \"\\<C-p>\" cause a problem which inserts a match without\r\n  <CR> when 'dictionary' has been set and keyword completion is done.\r\n- Changed to show error message when incompatible with a installed vim.\r\n","package":"vim-autocomplpop.zip","4":"vim-autocomplpop.zip","src_id":"11538","5":"11538","creation_date":"1255770038","6":"1255770038"},{"0":"1879","vim_version":"7.0","1":"7.0","script_version":"2.8.1","2":"2.8.1","version_comment":"- Fixed a bug which inserted a selected match to the next line when\r\n  auto-wrapping (enabled with 'formatoptions') was performed.\r\n","3":"- Fixed a bug which inserted a selected match to the next line when\r\n  auto-wrapping (enabled with 'formatoptions') was performed.\r\n","package":"vim-autocomplpop.zip","4":"vim-autocomplpop.zip","src_id":"11379","5":"11379","creation_date":"1253023617","6":"1253023617"},{"0":"1879","vim_version":"7.0","1":"7.0","script_version":"2.8","2":"2.8","version_comment":"- Added g:acp_behaviorUserDefinedFunction option and\r\n  g:acp_behaviorUserDefinedPattern option for users who want to make custom\r\n  completion auto-popup.\r\n- Fixed a bug that setting 'spell' on a new buffer made typing go crazy.\r\n","3":"- Added g:acp_behaviorUserDefinedFunction option and\r\n  g:acp_behaviorUserDefinedPattern option for users who want to make custom\r\n  completion auto-popup.\r\n- Fixed a bug that setting 'spell' on a new buffer made typing go crazy.\r\n","package":"vim-autocomplpop.zip","4":"vim-autocomplpop.zip","src_id":"11373","5":"11373","creation_date":"1252928315","6":"1252928315"},{"0":"1879","vim_version":"7.0","1":"7.0","script_version":"2.7","2":"2.7","version_comment":"- Changed naming conventions for filenames, functions, commands, and options \r\n  and thus renamed them.\r\n- Added g:acp_behaviorKeywordCommand option. If you prefer the previous\r\n  behavior for keyword completion, set this option \"\\<C-n>\".\r\n- Changed default value of g:acp_ignorecaseOption option.\r\n                                                                              \r\nThe following were done by Ingo Karkat:\r\n                                                                              \r\n- ENH: Added support for setting a user-provided 'completefunc' during the\r\n  completion, configurable via g:acp_behavior. \r\n- BUG: When the configured completion is <C-p> or <C-x><C-p>, the command to\r\n  restore the original text (in on_popup_post()) must be reverted, too. \r\n- BUG: When using a custom completion function (<C-x><C-u>) that also uses\r\n  an s:...() function name, the s:GetSidPrefix() function dynamically\r\n  determines the wrong SID. Now calling s:DetermineSidPrefix() once during\r\n  sourcing and caching the value in s:SID. \r\n- BUG: Should not use custom defined <C-X><C-...> completion mappings. Now\r\n  consistently using unmapped completion commands everywhere. (Beforehand,\r\n  s:PopupFeeder.feed() used mappings via feedkeys(..., 'm'), but\r\n  s:PopupFeeder.on_popup_post() did not due to its invocation via\r\n  :map-expr.) \r\n","3":"- Changed naming conventions for filenames, functions, commands, and options \r\n  and thus renamed them.\r\n- Added g:acp_behaviorKeywordCommand option. If you prefer the previous\r\n  behavior for keyword completion, set this option \"\\<C-n>\".\r\n- Changed default value of g:acp_ignorecaseOption option.\r\n                                                                              \r\nThe following were done by Ingo Karkat:\r\n                                                                              \r\n- ENH: Added support for setting a user-provided 'completefunc' during the\r\n  completion, configurable via g:acp_behavior. \r\n- BUG: When the configured completion is <C-p> or <C-x><C-p>, the command to\r\n  restore the original text (in on_popup_post()) must be reverted, too. \r\n- BUG: When using a custom completion function (<C-x><C-u>) that also uses\r\n  an s:...() function name, the s:GetSidPrefix() function dynamically\r\n  determines the wrong SID. Now calling s:DetermineSidPrefix() once during\r\n  sourcing and caching the value in s:SID. \r\n- BUG: Should not use custom defined <C-X><C-...> completion mappings. Now\r\n  consistently using unmapped completion commands everywhere. (Beforehand,\r\n  s:PopupFeeder.feed() used mappings via feedkeys(..., 'm'), but\r\n  s:PopupFeeder.on_popup_post() did not due to its invocation via\r\n  :map-expr.) \r\n","package":"vim-autocomplpop.zip","4":"vim-autocomplpop.zip","src_id":"11366","5":"11366","creation_date":"1252835823","6":"1252835823"},{"0":"1879","vim_version":"7.0","1":"7.0","script_version":"2.6","2":"2.6","version_comment":"- Improved the behavior of omni completion for HTML\/XHTML.","3":"- Improved the behavior of omni completion for HTML\/XHTML.","package":"autocomplpop.vim","4":"autocomplpop.vim","src_id":"9335","5":"9335","creation_date":"1223785122","6":"1223785122"},{"0":"1879","vim_version":"7.0","1":"7.0","script_version":"2.5","2":"2.5","version_comment":"- Added some options to customize behavior easily:\r\n    g:AutoComplPop_BehaviorKeywordLength\r\n    g:AutoComplPop_BehaviorFileLength\r\n    g:AutoComplPop_BehaviorRubyOmniMethodLength\r\n    g:AutoComplPop_BehaviorRubyOmniSymbolLength\r\n    g:AutoComplPop_BehaviorPythonOmniLength\r\n    g:AutoComplPop_BehaviorHtmlOmniLength\r\n    g:AutoComplPop_BehaviorCssOmniPropertyLength\r\n    g:AutoComplPop_BehaviorCssOmniValueLength\r\n","3":"- Added some options to customize behavior easily:\r\n    g:AutoComplPop_BehaviorKeywordLength\r\n    g:AutoComplPop_BehaviorFileLength\r\n    g:AutoComplPop_BehaviorRubyOmniMethodLength\r\n    g:AutoComplPop_BehaviorRubyOmniSymbolLength\r\n    g:AutoComplPop_BehaviorPythonOmniLength\r\n    g:AutoComplPop_BehaviorHtmlOmniLength\r\n    g:AutoComplPop_BehaviorCssOmniPropertyLength\r\n    g:AutoComplPop_BehaviorCssOmniValueLength\r\n","package":"autocomplpop.vim","4":"autocomplpop.vim","src_id":"8821","5":"8821","creation_date":"1213727909","6":"1213727909"},{"0":"1879","vim_version":"7.0","1":"7.0","script_version":"2.4","2":"2.4","version_comment":"- Added g:AutoComplPop_MappingDriven option.","3":"- Added g:AutoComplPop_MappingDriven option.","package":"autocomplpop.vim","4":"autocomplpop.vim","src_id":"8656","5":"8656","creation_date":"1210143450","6":"1210143450"},{"0":"1879","vim_version":"7.0","1":"7.0","script_version":"2.3.1","2":"2.3.1","version_comment":"- Changed to set 'lazyredraw' while a popup menu is visible to avoid\r\n  flickering.\r\n- Changed a behavior for CSS.\r\n- Added support for GetLatestVimScripts.\r\n","3":"- Changed to set 'lazyredraw' while a popup menu is visible to avoid\r\n  flickering.\r\n- Changed a behavior for CSS.\r\n- Added support for GetLatestVimScripts.\r\n","package":"autocomplpop.vim","4":"autocomplpop.vim","src_id":"8513","5":"8513","creation_date":"1206948605","6":"1206948605"},{"0":"1879","vim_version":"7.0","1":"7.0","script_version":"2.3","2":"2.3","version_comment":"- Added a behavior for Python to support omni completion.\r\n- Added a behavior for CSS to support omni completion.\r\n","3":"- Added a behavior for Python to support omni completion.\r\n- Added a behavior for CSS to support omni completion.\r\n","package":"autocomplpop.vim","4":"autocomplpop.vim","src_id":"8506","5":"8506","creation_date":"1206832492","6":"1206832492"},{"0":"1879","vim_version":"7.0","1":"7.0","script_version":"2.2","2":"2.2","version_comment":"- Changed not to work when 'paste' option is set.\r\n- Fixed AutoComplPopEnable command and AutoComplPopDisable command to\r\n  map\/unmap \"i\" and \"R\".\r\n","3":"- Changed not to work when 'paste' option is set.\r\n- Fixed AutoComplPopEnable command and AutoComplPopDisable command to\r\n  map\/unmap \"i\" and \"R\".\r\n","package":"autocomplpop.vim","4":"autocomplpop.vim","src_id":"8477","5":"8477","creation_date":"1206081051","6":"1206081051"},{"0":"1879","vim_version":"7.0","1":"7.0","script_version":"2.1","2":"2.1","version_comment":"- Fixed the problem caused by \".\" command in Normal mode.\r\n- Changed to map \"i\" and \"R\" to feed completion command after starting\r\n  Insert mode.\r\n- Avoided the problem caused by Windows IME.\r\n","3":"- Fixed the problem caused by \".\" command in Normal mode.\r\n- Changed to map \"i\" and \"R\" to feed completion command after starting\r\n  Insert mode.\r\n- Avoided the problem caused by Windows IME.\r\n","package":"autocomplpop.vim","4":"autocomplpop.vim","src_id":"8472","5":"8472","creation_date":"1205991959","6":"1205991959"},{"0":"1879","vim_version":"7.0","1":"7.0","script_version":"2.0","2":"2.0","version_comment":"- Changed to use CursorMovedI event to feed a completion command instead\r\n  of key mapping. Now the auto-popup is triggered by moving the cursor.\r\n- Changed to feed completion command after starting Insert mode.\r\n- Removed g:AutoComplPop_MapList option.\r\n","3":"- Changed to use CursorMovedI event to feed a completion command instead\r\n  of key mapping. Now the auto-popup is triggered by moving the cursor.\r\n- Changed to feed completion command after starting Insert mode.\r\n- Removed g:AutoComplPop_MapList option.\r\n","package":"autocomplpop.vim","4":"autocomplpop.vim","src_id":"8460","5":"8460","creation_date":"1205806170","6":"1205806170"},{"0":"1879","vim_version":"7.0","1":"7.0","script_version":"1.7","2":"1.7","version_comment":"- Added behaviors for HTML\/XHTML. Now supports the omni completion for\r\n  HTML\/XHTML.\r\n- Changed not to show expressions for CTRL-R =.\r\n- Changed not to set 'nolazyredraw' while a popup menu is visible.\r\n","3":"- Added behaviors for HTML\/XHTML. Now supports the omni completion for\r\n  HTML\/XHTML.\r\n- Changed not to show expressions for CTRL-R =.\r\n- Changed not to set 'nolazyredraw' while a popup menu is visible.\r\n","package":"autocomplpop.vim","4":"autocomplpop.vim","src_id":"8385","5":"8385","creation_date":"1204529806","6":"1204529806"},{"0":"1879","vim_version":"7.0","1":"7.0","script_version":"1.6.1","2":"1.6.1","version_comment":"- Changed not to trigger the filename competion by a text which has\r\n  multi-byte characters.\r\n","3":"- Changed not to trigger the filename competion by a text which has\r\n  multi-byte characters.\r\n","package":"autocomplpop.vim","4":"autocomplpop.vim","src_id":"8261","5":"8261","creation_date":"1202795509","6":"1202795509"},{"0":"1879","vim_version":"7.0","1":"7.0","script_version":"1.6","2":"1.6","version_comment":"- Redesigned g:AutoComplPop_Behavior option.\r\n- Changed default value of g:AutoComplPop_CompleteOption option.\r\n- Changed default value of g:AutoComplPop_MapList option.\r\n","3":"- Redesigned g:AutoComplPop_Behavior option.\r\n- Changed default value of g:AutoComplPop_CompleteOption option.\r\n- Changed default value of g:AutoComplPop_MapList option.\r\n","package":"autocomplpop.vim","4":"autocomplpop.vim","src_id":"8207","5":"8207","creation_date":"1201845218","6":"1201845218"},{"0":"1879","vim_version":"7.0","1":"7.0","script_version":"1.5","2":"1.5","version_comment":"- Implemented continuous-completion for the filename completion. And\r\n  added new option to g:AutoComplPop_Behavior.\r\n","3":"- Implemented continuous-completion for the filename completion. And\r\n  added new option to g:AutoComplPop_Behavior.\r\n","package":"autocomplpop.vim","4":"autocomplpop.vim","src_id":"8086","5":"8086","creation_date":"1198633523","6":"1198633523"},{"0":"1879","vim_version":"7.0","1":"7.0","script_version":"1.4","2":"1.4","version_comment":"- Fixed the bug that the auto-popup was not suspended in fuzzyfinder.\r\n- Fixed the bug that an error has occurred with Ruby-omni-completion\r\n  unless Ruby interface.\r\n","3":"- Fixed the bug that the auto-popup was not suspended in fuzzyfinder.\r\n- Fixed the bug that an error has occurred with Ruby-omni-completion\r\n  unless Ruby interface.\r\n","package":"autocomplpop.vim","4":"autocomplpop.vim","src_id":"8034","5":"8034","creation_date":"1197188865","6":"1197188865"},{"0":"1879","vim_version":"7.0","1":"7.0","script_version":"1.3","2":"1.3","version_comment":"- Supported Ruby-omni-completion by default.\r\n- Supported filename completion by default.\r\n- Added g:AutoComplPop_Behavior option.\r\n- Added g:AutoComplPop_CompleteoptPreview option.\r\n- Removed g:AutoComplPop_MinLength option.\r\n- Removed g:AutoComplPop_MaxLength option.\r\n- Removed g:AutoComplPop_PopupCmd option.\r\n","3":"- Supported Ruby-omni-completion by default.\r\n- Supported filename completion by default.\r\n- Added g:AutoComplPop_Behavior option.\r\n- Added g:AutoComplPop_CompleteoptPreview option.\r\n- Removed g:AutoComplPop_MinLength option.\r\n- Removed g:AutoComplPop_MaxLength option.\r\n- Removed g:AutoComplPop_PopupCmd option.\r\n","package":"autocomplpop.vim","4":"autocomplpop.vim","src_id":"7960","5":"7960","creation_date":"1195332642","6":"1195332642"},{"0":"1879","vim_version":"7.0","1":"7.0","script_version":"1.2","2":"1.2","version_comment":"- Fixed bugs related to 'completeopt'.","3":"- Fixed bugs related to 'completeopt'.","package":"autocomplpop.vim","4":"autocomplpop.vim","src_id":"7931","5":"7931","creation_date":"1194806842","6":"1194806842"},{"0":"1879","vim_version":"7.0","1":"7.0","script_version":"1.1","2":"1.1","version_comment":"- Added g:AutoComplPop_IgnoreCaseOption option.\r\n- Added g:AutoComplPop_NotEnableAtStartup option.\r\n- Removed g:AutoComplPop_LoadAndEnable option.\r\n","3":"- Added g:AutoComplPop_IgnoreCaseOption option.\r\n- Added g:AutoComplPop_NotEnableAtStartup option.\r\n- Removed g:AutoComplPop_LoadAndEnable option.\r\n","package":"autocomplpop.vim","4":"autocomplpop.vim","src_id":"7907","5":"7907","creation_date":"1194570055","6":"1194570055"},{"0":"1879","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"g:AutoComplPop_LoadAndEnable option for a startup activation is added.\r\nAutoComplPopLock command and AutoComplPopUnlock command are added to suspend and resume.\r\n'completeopt' and 'complete' options are changed temporarily while completing by this script.\r\n","3":"g:AutoComplPop_LoadAndEnable option for a startup activation is added.\r\nAutoComplPopLock command and AutoComplPopUnlock command are added to suspend and resume.\r\n'completeopt' and 'complete' options are changed temporarily while completing by this script.\r\n","package":"autocomplpop.vim","4":"autocomplpop.vim","src_id":"7464","5":"7464","creation_date":"1186544024","6":"1186544024"},{"0":"1879","vim_version":"7.0","1":"7.0","script_version":"0.4","2":"0.4","version_comment":"The first match are selected when the popup menu is Opened. You can insert the first match with CTRL-Y.","3":"The first match are selected when the popup menu is Opened. You can insert the first match with CTRL-Y.","package":"autocomplpop.vim","4":"autocomplpop.vim","src_id":"7107","5":"7107","creation_date":"1179081327","6":"1179081327"},{"0":"1879","vim_version":"7.0","1":"7.0","script_version":"0.3","2":"0.3","version_comment":"Fixed the problem that the original text is not restored if 'longest' is not set in 'completeopt'. Now the plugin works whether or not 'longest' is set in 'completeopt', and also 'menuone'.\r\n","3":"Fixed the problem that the original text is not restored if 'longest' is not set in 'completeopt'. Now the plugin works whether or not 'longest' is set in 'completeopt', and also 'menuone'.\r\n","package":"autocomplpop.vim","4":"autocomplpop.vim","src_id":"7085","5":"7085","creation_date":"1178689775","6":"1178689775"},{"0":"1879","vim_version":"7.0","1":"7.0","script_version":"0.2","2":"0.2","version_comment":"When completion matches are not found, insert CTRL-E to stop completion.\r\nClear the echo area.\r\nFixed the problem in case of dividing words by symbols, popup menu is not opened.\r\n","3":"When completion matches are not found, insert CTRL-E to stop completion.\r\nClear the echo area.\r\nFixed the problem in case of dividing words by symbols, popup menu is not opened.\r\n","package":"autocomplpop.vim","4":"autocomplpop.vim","src_id":"7084","5":"7084","creation_date":"1178678311","6":"1178678311"},{"0":"1879","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"autocomplpop.vim","4":"autocomplpop.vim","src_id":"7048","5":"7048","creation_date":"1178077542","6":"1178077542"}]},"1878":{"script_id":"1878","0":"1878","script_name":"vimoutliner-colorscheme-fix","1":"vimoutliner-colorscheme-fix","script_type":"syntax","2":"syntax","summary":"Allows VimOutliner files to work with *any* colorscheme.","3":"Allows VimOutliner files to work with *any* colorscheme.","description":"If you're familiar with VimOutliner, at http:\/\/vimoutliner.org, you know it's a fantastic outlining tool that can easily become your default way to use Vim. The one major annoyance I've found is that it ships with one or two colorschemes. \r\nUnlike most syntax files, the colors are hard-coded in, so if you try to use a different colorscheme, the syntax highlighting disappears.\r\n\r\nFortunately, there's an easy fix. This tiny package is simply an updated syntax file, in which I have linked the syntax groups to established Vim groups, like Normal, Comment, and so on. You can now open a VimOutliner file in any colorscheme you like. \r\n\r\nYou\u00e2\u0080\u0099ll still get some occasional weirdnesses (certain elements can default to invisible), in which case you can either change colorschemes, tweak the colorscheme itself, or tweak syntax\/vo_base.vim. Anyhow, it usually works.\r\n\r\n(More info at http:\/\/www.billpowellisalive.com\/2007\/01\/vimoutliner-and-a-tweak-to-use-colorschemes\/)","4":"If you're familiar with VimOutliner, at http:\/\/vimoutliner.org, you know it's a fantastic outlining tool that can easily become your default way to use Vim. The one major annoyance I've found is that it ships with one or two colorschemes. \r\nUnlike most syntax files, the colors are hard-coded in, so if you try to use a different colorscheme, the syntax highlighting disappears.\r\n\r\nFortunately, there's an easy fix. This tiny package is simply an updated syntax file, in which I have linked the syntax groups to established Vim groups, like Normal, Comment, and so on. You can now open a VimOutliner file in any colorscheme you like. \r\n\r\nYou\u00e2\u0080\u0099ll still get some occasional weirdnesses (certain elements can default to invisible), in which case you can either change colorschemes, tweak the colorscheme itself, or tweak syntax\/vo_base.vim. Anyhow, it usually works.\r\n\r\n(More info at http:\/\/www.billpowellisalive.com\/2007\/01\/vimoutliner-and-a-tweak-to-use-colorschemes\/)","install_details":"Assuming you\u00e2\u0080\u0099ve already gotten VimOutliner, just copy the package onto your vim tree (on Unix, usually ~\/.vim).  Note that THIS WILL OVERWRITE THE OLD SYNTAX FILE, e.g., ~\/.vim\/syntax\/vo_base.vim, so back it up if you want it around. \r\n\r\nAlso, I've only tested this on a Linux machine. The actual file has a long name which includes its \r\nOf course, the next type you upgrade VimOutliner, this syntax fix will be wiped out. But I\u00e2\u0080\u0099m posting this on the VimOutliner site; maybe this tweak\u00e2\u0080\u0099ll be in the next version. ","5":"Assuming you\u00e2\u0080\u0099ve already gotten VimOutliner, just copy the package onto your vim tree (on Unix, usually ~\/.vim).  Note that THIS WILL OVERWRITE THE OLD SYNTAX FILE, e.g., ~\/.vim\/syntax\/vo_base.vim, so back it up if you want it around. \r\n\r\nAlso, I've only tested this on a Linux machine. The actual file has a long name which includes its \r\nOf course, the next type you upgrade VimOutliner, this syntax fix will be wiped out. But I\u00e2\u0080\u0099m posting this on the VimOutliner site; maybe this tweak\u00e2\u0080\u0099ll be in the next version. ","first_name":"Bill","6":"Bill","last_name":"Powell","7":"Powell","releases":[{"0":"1878","vim_version":"7.0","1":"7.0","script_version":"0.2b","2":"0.2b","version_comment":"Quick fix in package.","3":"Quick fix in package.","package":"vimoutliner-colorscheme-fix-0.2b.tar.gz","4":"vimoutliner-colorscheme-fix-0.2b.tar.gz","src_id":"7043","5":"7043","creation_date":"1177917813","6":"1177917813"},{"0":"1878","vim_version":"7.0","1":"7.0","script_version":"0.2","2":"0.2","version_comment":"Initial upload","3":"Initial upload","package":"vimoutliner-colorscheme-fix-0.2.tar.gz","4":"vimoutliner-colorscheme-fix-0.2.tar.gz","src_id":"7042","5":"7042","creation_date":"1177917265","6":"1177917265"}]},"1877":{"script_id":"1877","0":"1877","script_name":"voodu.vim","1":"voodu.vim","script_type":"utility","2":"utility","summary":"Framework for implementing Object Oriented Programming with Vim Scripts","3":"Framework for implementing Object Oriented Programming with Vim Scripts","description":"This is an implementation of OOP with a decisively Perl flavor utilizing Vim 7.0's dictionary representation of objects.  More extensive documentation will be added at a later date.  I'm also aware of vimscript #1034 but it was pre-7.0 and thus doesn't utilize many of the features involved with Voodu.  For now, you can do the following:\r\n\r\nlet s:AD = tv#series#comedy#New('Arrested Development')\r\nlet s:TO = tv#series#comedy#New('The Office')\r\n\r\necho s:AD.name()\r\necho s:AD.type()\r\necho s:TO.name().\" is a \".s:TO.type()\r\n\r\nlet s:SS = tv#series#comedy#New('The Simpsons')\r\n\r\n\" An example of Class Method accessing Class Data\r\necho tv#series#Names()\r\n\r\nlet s:dailyshow = tv#New('News Parody')\r\necho s:dailyshow.type()\r\n\r\n--------------------------------------- Future Plans ---------------------------------------\r\n\r\nI want to demonstrate the usefulness of this utility plugin by implementing generic tab\/window\/buffer classes that can hide a lot of the work I see plugin authors performing, e.g. wincommander, WinWalker, SideBar.\r\n\r\nAdditionally, I believe I can add functionality similar to Perl's Class::Accessor or Ruby's attr_reader:, namely automatic provision of simple accessor methods.","4":"This is an implementation of OOP with a decisively Perl flavor utilizing Vim 7.0's dictionary representation of objects.  More extensive documentation will be added at a later date.  I'm also aware of vimscript #1034 but it was pre-7.0 and thus doesn't utilize many of the features involved with Voodu.  For now, you can do the following:\r\n\r\nlet s:AD = tv#series#comedy#New('Arrested Development')\r\nlet s:TO = tv#series#comedy#New('The Office')\r\n\r\necho s:AD.name()\r\necho s:AD.type()\r\necho s:TO.name().\" is a \".s:TO.type()\r\n\r\nlet s:SS = tv#series#comedy#New('The Simpsons')\r\n\r\n\" An example of Class Method accessing Class Data\r\necho tv#series#Names()\r\n\r\nlet s:dailyshow = tv#New('News Parody')\r\necho s:dailyshow.type()\r\n\r\n--------------------------------------- Future Plans ---------------------------------------\r\n\r\nI want to demonstrate the usefulness of this utility plugin by implementing generic tab\/window\/buffer classes that can hide a lot of the work I see plugin authors performing, e.g. wincommander, WinWalker, SideBar.\r\n\r\nAdditionally, I believe I can add functionality similar to Perl's Class::Accessor or Ruby's attr_reader:, namely automatic provision of simple accessor methods.","install_details":"$ cd ~\/.vim\r\n$ tar xzvf voodu-0.0.1.tar.gz\r\n\r\nAnd then you can test with:\r\n\r\n$ vim -c ':so %' tv.vim","5":"$ cd ~\/.vim\r\n$ tar xzvf voodu-0.0.1.tar.gz\r\n\r\nAnd then you can test with:\r\n\r\n$ vim -c ':so %' tv.vim","first_name":"Ian","6":"Ian","last_name":"Tegebo","7":"Tegebo","releases":[{"0":"1877","vim_version":"7.0","1":"7.0","script_version":"0.0.1","2":"0.0.1","version_comment":"Initial upload","3":"Initial upload","package":"voodu-0.0.1.tar.gz","4":"voodu-0.0.1.tar.gz","src_id":"7039","5":"7039","creation_date":"1177857476","6":"1177857476"}]},"1876":{"script_id":"1876","0":"1876","script_name":"securemodelines","1":"securemodelines","script_type":"utility","2":"utility","summary":"Secure, user-configurable modeline support","3":"Secure, user-configurable modeline support","description":"Secure, user-configurable modeline support for Vim 7.\r\n\r\nVim's internal modeline support allows all sorts of annoying and potentially insecure options to be set. This script implements a much more heavily restricted modeline parser that permits only user-specified options to be set.\r\n\r\nThe g:secure_modelines_allowed_items array contains allowable options. By default it is set as follows:\r\n\r\n    let g:secure_modelines_allowed_items = [\r\n                \\ \"textwidth\",   \"tw\",\r\n                \\ \"softtabstop\", \"sts\",\r\n                \\ \"tabstop\",     \"ts\",\r\n                \\ \"shiftwidth\",  \"sw\",\r\n                \\ \"expandtab\",   \"et\",   \"noexpandtab\", \"noet\",\r\n                \\ \"filetype\",    \"ft\",\r\n                \\ \"foldmethod\",  \"fdm\",\r\n                \\ \"readonly\",    \"ro\",   \"noreadonly\", \"noro\",\r\n                \\ \"rightleft\",   \"rl\",   \"norightleft\", \"norl\"\r\n                \\ ]\r\n\r\nThe g:secure_modelines_verbose option, if set to something true, will make the script warn when a modeline attempts to set any other option.\r\n\r\nThe g:secure_modelines_modelines option overrides the number of lines to check. By default it is 5.\r\n\r\nIf g:secure_modelines_leave_modeline is defined, the script will not clobber &modeline. Otherwise &modeline will be unset.\r\n\r\nKeeping things up to date on vim.org is a nuisance. For the latest version, visit:\r\n\r\n    http:\/\/github.com\/ciaranm\/securemodelines","4":"Secure, user-configurable modeline support for Vim 7.\r\n\r\nVim's internal modeline support allows all sorts of annoying and potentially insecure options to be set. This script implements a much more heavily restricted modeline parser that permits only user-specified options to be set.\r\n\r\nThe g:secure_modelines_allowed_items array contains allowable options. By default it is set as follows:\r\n\r\n    let g:secure_modelines_allowed_items = [\r\n                \\ \"textwidth\",   \"tw\",\r\n                \\ \"softtabstop\", \"sts\",\r\n                \\ \"tabstop\",     \"ts\",\r\n                \\ \"shiftwidth\",  \"sw\",\r\n                \\ \"expandtab\",   \"et\",   \"noexpandtab\", \"noet\",\r\n                \\ \"filetype\",    \"ft\",\r\n                \\ \"foldmethod\",  \"fdm\",\r\n                \\ \"readonly\",    \"ro\",   \"noreadonly\", \"noro\",\r\n                \\ \"rightleft\",   \"rl\",   \"norightleft\", \"norl\"\r\n                \\ ]\r\n\r\nThe g:secure_modelines_verbose option, if set to something true, will make the script warn when a modeline attempts to set any other option.\r\n\r\nThe g:secure_modelines_modelines option overrides the number of lines to check. By default it is 5.\r\n\r\nIf g:secure_modelines_leave_modeline is defined, the script will not clobber &modeline. Otherwise &modeline will be unset.\r\n\r\nKeeping things up to date on vim.org is a nuisance. For the latest version, visit:\r\n\r\n    http:\/\/github.com\/ciaranm\/securemodelines","install_details":"Install into your plugin directory of choice.","5":"Install into your plugin directory of choice.","first_name":"Ciaran","6":"Ciaran","last_name":"McCreesh","7":"McCreesh","releases":[{"0":"1876","vim_version":"7.0","1":"7.0","script_version":"20080424","2":"20080424","version_comment":"Two tweaks, thanks to Christian J. Robinson: Make the messages it echoes end up in the :messages history. Modelines of the format \"vim: set ...:\" can also be be \"vim:set ...:\".","3":"Two tweaks, thanks to Christian J. Robinson: Make the messages it echoes end up in the :messages history. Modelines of the format \"vim: set ...:\" can also be be \"vim:set ...:\".","package":"securemodelines.vim","4":"securemodelines.vim","src_id":"8598","5":"8598","creation_date":"1209007201","6":"1209007201"},{"0":"1876","vim_version":"7.0","1":"7.0","script_version":"20070518","2":"20070518","version_comment":"The number of lines to search is now controllable via let g:secure_modelines_modelines=5. If g:secure_modelines_leave_modeline is defined, the internal &modeline variable will be left alone. Previously only one line at the end of the document would be searched for modelines. This is now fixed, thanks to Thomas de Grenier de Latour. The <SID>DoModelines function can now be accessed externally via SecureModelines_DoModelines.","3":"The number of lines to search is now controllable via let g:secure_modelines_modelines=5. If g:secure_modelines_leave_modeline is defined, the internal &modeline variable will be left alone. Previously only one line at the end of the document would be searched for modelines. This is now fixed, thanks to Thomas de Grenier de Latour. The <SID>DoModelines function can now be accessed externally via SecureModelines_DoModelines.","package":"securemodelines.vim","4":"securemodelines.vim","src_id":"7142","5":"7142","creation_date":"1179464120","6":"1179464120"},{"0":"1876","vim_version":"7.0","1":"7.0","script_version":"20070513","2":"20070513","version_comment":"Modelines with no set: are now parsed correctly. rightleft is now included in the default allowed options, for help files. Builtin modelines are now forcibly disabled.\r\n","3":"Modelines with no set: are now parsed correctly. rightleft is now included in the default allowed options, for help files. Builtin modelines are now forcibly disabled.\r\n","package":"securemodelines.vim","4":"securemodelines.vim","src_id":"7104","5":"7104","creation_date":"1179072734","6":"1179072734"},{"0":"1876","vim_version":"7.0","1":"7.0","script_version":"20070409","2":"20070409","version_comment":"Initial upload","3":"Initial upload","package":"securemodelines.vim","4":"securemodelines.vim","src_id":"7038","5":"7038","creation_date":"1177832297","6":"1177832297"}]},"1875":{"script_id":"1875","0":"1875","script_name":"verilog_emacsauto.vim","1":"verilog_emacsauto.vim","script_type":"ftplugin","2":"ftplugin","summary":"verilog filetype plugin to enable emacs verilog-mode autos","3":"verilog filetype plugin to enable emacs verilog-mode autos","description":"Two emacs verilog-mode functions are mapped.\r\n\\a expands all the verilog-mode autos (similar to C-c C-a in emacs).\r\n\\d collapses all the verilog-mode autos (similar to C-c C-d in emacs).\r\n\r\nPreviously if I wanted to update verilog-mode autos, I would\r\n   save and quit vim\r\n   fire up emacs\r\n   do the auto commands\r\n   save and close emacs\r\n   fire up vim.\r\nAnd in doing so, I would lose all the edit history in vim.\r\nWith this I can just type \\a and keep all the previous edit history for undos.\r\n\r\nThis is my first attempt at writing a vim plugin. Code should be simple enough for an average Verilog user to take and fix\/enhance according to needs. Doing :he plugin, :he write-plugin, or :he plugin-details should reveal how simple this really is.","4":"Two emacs verilog-mode functions are mapped.\r\n\\a expands all the verilog-mode autos (similar to C-c C-a in emacs).\r\n\\d collapses all the verilog-mode autos (similar to C-c C-d in emacs).\r\n\r\nPreviously if I wanted to update verilog-mode autos, I would\r\n   save and quit vim\r\n   fire up emacs\r\n   do the auto commands\r\n   save and close emacs\r\n   fire up vim.\r\nAnd in doing so, I would lose all the edit history in vim.\r\nWith this I can just type \\a and keep all the previous edit history for undos.\r\n\r\nThis is my first attempt at writing a vim plugin. Code should be simple enough for an average Verilog user to take and fix\/enhance according to needs. Doing :he plugin, :he write-plugin, or :he plugin-details should reveal how simple this really is.","install_details":"Download this script and put it in your ~\/.vim\/ftplugin\/ directory, creating the directories if necessary.\r\n\r\nYou need to get the verilog-mode.el file from the http:\/\/www.verilog.com\/verilog-mode.html site.\r\nYou can follow the installation instruction there, but to use it with this script all you need to do is place the uncompressed file in your ~\/elisp directory. You can also place the file in other locations as long as you change the path to the file in this script.","5":"Download this script and put it in your ~\/.vim\/ftplugin\/ directory, creating the directories if necessary.\r\n\r\nYou need to get the verilog-mode.el file from the http:\/\/www.verilog.com\/verilog-mode.html site.\r\nYou can follow the installation instruction there, but to use it with this script all you need to do is place the uncompressed file in your ~\/elisp directory. You can also place the file in other locations as long as you change the path to the file in this script.","first_name":"Seong","6":"Seong","last_name":"Kang","7":"Kang","releases":[{"0":"1875","vim_version":"6.0","1":"6.0","script_version":"0.4","2":"0.4","version_comment":"moved setlocals outside of loaded check so it works properly when opening multiple files","3":"moved setlocals outside of loaded check so it works properly when opening multiple files","package":"verilog_emacsauto.vim","4":"verilog_emacsauto.vim","src_id":"7578","5":"7578","creation_date":"1188383674","6":"1188383674"},{"0":"1875","vim_version":"6.0","1":"6.0","script_version":"0.3","2":"0.3","version_comment":"Made emacs stderr output to show to help debugging any problems.\r\nMade removal of temporary file standard.","3":"Made emacs stderr output to show to help debugging any problems.\r\nMade removal of temporary file standard.","package":"verilog_emacsauto.vim","4":"verilog_emacsauto.vim","src_id":"7045","5":"7045","creation_date":"1177935506","6":"1177935506"},{"0":"1875","vim_version":"6.0","1":"6.0","script_version":"0.2","2":"0.2","version_comment":"Added folding of emacs autos. I.e. 'zo' and 'zc' can be used to open and close folds.\r\nDo :he fold for more about foldings","3":"Added folding of emacs autos. I.e. 'zo' and 'zc' can be used to open and close folds.\r\nDo :he fold for more about foldings","package":"verilog_emacsauto.vim","4":"verilog_emacsauto.vim","src_id":"7033","5":"7033","creation_date":"1177688584","6":"1177688584"},{"0":"1875","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"verilog_emacsauto.vim","4":"verilog_emacsauto.vim","src_id":"7031","5":"7031","creation_date":"1177602771","6":"1177602771"}]},"1874":{"script_id":"1874","0":"1874","script_name":"psql.vim","1":"psql.vim","script_type":"indent","2":"indent","summary":"initial upload","3":"initial upload","description":"This file is a rewrite for PostgreSQL of the more general SQL intenting vim file made for Oracle and Sybase Adaptive Server Anywhere (ASA). All credits go to David Fishburn.","4":"This file is a rewrite for PostgreSQL of the more general SQL intenting vim file made for Oracle and Sybase Adaptive Server Anywhere (ASA). All credits go to David Fishburn.","install_details":"copy in ~\/.vim\/indent\/","5":"copy in ~\/.vim\/indent\/","first_name":"Pim","6":"Pim","last_name":"Snel","7":"Snel","releases":[{"0":"1874","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"psql.vim","4":"psql.vim","src_id":"7028","5":"7028","creation_date":"1177508848","6":"1177508848"}]},"1873":{"script_id":"1873","0":"1873","script_name":"projtags.vim","1":"projtags.vim","script_type":"utility","2":"utility","summary":"Set tags file for per project","3":"Set tags file for per project","description":"Usage:\r\n\r\nSet your projects path into g:ProjTags as a list, for example:\r\n\r\nlet g:ProjTags = [ \"~\/work\/proj1\" ]\r\n\r\nIn this case for all file match the pattern \"~\/work\/proj1\/*\", the tag file\r\n\"~\/work\/proj1\/tags\" will be used.\r\n\r\nYou can also specify a tags file other than the default one or more tags\r\nfiles for one directory by a list:\r\n\r\nlet g:ProjTags += [[ \"~\/work\/proj2\", \"~\/work\/proj2\/tags\",\r\n\"~\/work\/common.tags\" ]]\r\n\r\nIn this case for all files match the pattern \"~\/work\/proj2\/*\", the tag files\r\n\"~\/work\/proj2\/tags\" and \"~\/work\/common.tags\" will be used.\r\n\r\nIf one of the items in the list begins with \":\", it will be treated as a\r\ncommand (other than tag file):\r\n\r\nlet g:ProjTags += [[ \"~\/work\/proj3\", \"~\/work\/proj3\/tags\",\r\n\":set shiftwidth=4\" ]]\r\n\r\nIn this case for all files match the pattern \"~\/work\/proj3\/*\", the tag file\r\n\"~\/work\/proj3\/tags\" will be used, and \"shiftwidth=4\" will be set.\r\n\r\nPlease note that if you use \"set\" in the command, we will actually use\r\n\"setlocal\" instead, to avoid polluting the whole vim environment.\r\n\r\nYou can add the above codes into your vimrc file.\r\n\r\nGit repository at https:\/\/github.com\/fishy\/projtags-vim\r\n\r\nGoogle+ page at https:\/\/plus.google.com\/100558470596894261435","4":"Usage:\r\n\r\nSet your projects path into g:ProjTags as a list, for example:\r\n\r\nlet g:ProjTags = [ \"~\/work\/proj1\" ]\r\n\r\nIn this case for all file match the pattern \"~\/work\/proj1\/*\", the tag file\r\n\"~\/work\/proj1\/tags\" will be used.\r\n\r\nYou can also specify a tags file other than the default one or more tags\r\nfiles for one directory by a list:\r\n\r\nlet g:ProjTags += [[ \"~\/work\/proj2\", \"~\/work\/proj2\/tags\",\r\n\"~\/work\/common.tags\" ]]\r\n\r\nIn this case for all files match the pattern \"~\/work\/proj2\/*\", the tag files\r\n\"~\/work\/proj2\/tags\" and \"~\/work\/common.tags\" will be used.\r\n\r\nIf one of the items in the list begins with \":\", it will be treated as a\r\ncommand (other than tag file):\r\n\r\nlet g:ProjTags += [[ \"~\/work\/proj3\", \"~\/work\/proj3\/tags\",\r\n\":set shiftwidth=4\" ]]\r\n\r\nIn this case for all files match the pattern \"~\/work\/proj3\/*\", the tag file\r\n\"~\/work\/proj3\/tags\" will be used, and \"shiftwidth=4\" will be set.\r\n\r\nPlease note that if you use \"set\" in the command, we will actually use\r\n\"setlocal\" instead, to avoid polluting the whole vim environment.\r\n\r\nYou can add the above codes into your vimrc file.\r\n\r\nGit repository at https:\/\/github.com\/fishy\/projtags-vim\r\n\r\nGoogle+ page at https:\/\/plus.google.com\/100558470596894261435","install_details":"put this file under your ~\/.vim\/plugin\/","5":"put this file under your ~\/.vim\/plugin\/","first_name":"Yuxuan","6":"Yuxuan","last_name":"Wang","7":"Wang","releases":[{"0":"1873","vim_version":"7.0","1":"7.0","script_version":"0.42","2":"0.42","version_comment":"+ added missing \"let\" thanks to Adam!","3":"+ added missing \"let\" thanks to Adam!","package":"projtags.vim","4":"projtags.vim","src_id":"19343","5":"19343","creation_date":"1357807455","6":"1357807455"},{"0":"1873","vim_version":"7.0","1":"7.0","script_version":"0.41","2":"0.41","version_comment":" * a serious bug regarding the return value of match() fixed thanks to ramp!","3":" * a serious bug regarding the return value of match() fixed thanks to ramp!","package":"projtags.vim","4":"projtags.vim","src_id":"14225","5":"14225","creation_date":"1289391555","6":"1289391555"},{"0":"1873","vim_version":"6.0","1":"6.0","script_version":"0.4","2":"0.4","version_comment":" + can handle directories end with \"\/\" now","3":" + can handle directories end with \"\/\" now","package":"projtags.vim","4":"projtags.vim","src_id":"12536","5":"12536","creation_date":"1267517049","6":"1267517049"},{"0":"1873","vim_version":"6.0","1":"6.0","script_version":"0.3","2":"0.3","version_comment":"+ can add commands now","3":"+ can add commands now","package":"projtags.vim","4":"projtags.vim","src_id":"11112","5":"11112","creation_date":"1249033347","6":"1249033347"},{"0":"1873","vim_version":"6.0","1":"6.0","script_version":"0.2","2":"0.2","version_comment":"+ more tags file for one directory support (contributed by Joseph Barker)\r\n+ check for g:ProjTags before use it ","3":"+ more tags file for one directory support (contributed by Joseph Barker)\r\n+ check for g:ProjTags before use it ","package":"projtags.vim","4":"projtags.vim","src_id":"7027","5":"7027","creation_date":"1177461019","6":"1177461019"},{"0":"1873","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"projtags.vim","4":"projtags.vim","src_id":"7024","5":"7024","creation_date":"1177413163","6":"1177413163"}]},"1872":{"script_id":"1872","0":"1872","script_name":"summerfruit.vim","1":"summerfruit.vim","script_type":"color scheme","2":"color scheme","summary":"Light version of fruity.vim","3":"Light version of fruity.vim","description":"Smaller and brighter version of fruity.vim.","4":"Smaller and brighter version of fruity.vim.","install_details":"Copy into ~\/.vim\/colors","5":"Copy into ~\/.vim\/colors","first_name":"Armin","6":"Armin","last_name":"Ronacher","7":"Ronacher","releases":[{"0":"1872","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"summerfruit.vim","4":"summerfruit.vim","src_id":"7017","5":"7017","creation_date":"1177233548","6":"1177233548"}]},"1871":{"script_id":"1871","0":"1871","script_name":"fruity.vim","1":"fruity.vim","script_type":"color scheme","2":"color scheme","summary":"Dark Colorscheme with advanced color informations for several languages","3":"Dark Colorscheme with advanced color informations for several languages","description":"This colorscheme contains additional color informations for python, ruby, jinja templates and some others I use often.","4":"This colorscheme contains additional color informations for python, ruby, jinja templates and some others I use often.","install_details":"Copy it into ~\/.vim\/colors","5":"Copy it into ~\/.vim\/colors","first_name":"Armin","6":"Armin","last_name":"Ronacher","7":"Ronacher","releases":[{"0":"1871","vim_version":"6.0","1":"6.0","script_version":"0.2","2":"0.2","version_comment":"Initial upload","3":"Initial upload","package":"fruity.vim","4":"fruity.vim","src_id":"7016","5":"7016","creation_date":"1177233447","6":"1177233447"}]},"1870":{"script_id":"1870","0":"1870","script_name":"django.vim","1":"django.vim","script_type":"color scheme","2":"color scheme","summary":"colorscheme in the colors of the django webpage","3":"colorscheme in the colors of the django webpage","description":"Vim colorscheme in the colors of the django webframework webpage.","4":"Vim colorscheme in the colors of the django webframework webpage.","install_details":"Copy it into ~\/.vim\/colors","5":"Copy it into ~\/.vim\/colors","first_name":"Armin","6":"Armin","last_name":"Ronacher","7":"Ronacher","releases":[{"0":"1870","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"django.vim","4":"django.vim","src_id":"7015","5":"7015","creation_date":"1177233307","6":"1177233307"}]},"1869":{"script_id":"1869","0":"1869","script_name":"genshi.vim","1":"genshi.vim","script_type":"syntax","2":"syntax","summary":"Adds support for Genshi HTMl Templates to vim","3":"Adds support for Genshi HTMl Templates to vim","description":"Adds support for Genshi HTML Templates to Vim.\r\n\r\nGenshi Webpage: http:\/\/genshi.edgewall.org\/","4":"Adds support for Genshi HTML Templates to Vim.\r\n\r\nGenshi Webpage: http:\/\/genshi.edgewall.org\/","install_details":"copy genshi.vim into your ~\/.vim\/syntax folder. Requires python.vim and html.vim to work.","5":"copy genshi.vim into your ~\/.vim\/syntax folder. Requires python.vim and html.vim to work.","first_name":"Armin","6":"Armin","last_name":"Ronacher","7":"Ronacher","releases":[{"0":"1869","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"genshi.vim","4":"genshi.vim","src_id":"7014","5":"7014","creation_date":"1177227767","6":"1177227767"}]},"1868":{"script_id":"1868","0":"1868","script_name":"simplefold","1":"simplefold","script_type":"utility","2":"utility","summary":"space-optimized, configurable folds, supports Ruby, Ocaml, Perl, PHP, Java...","3":"space-optimized, configurable folds, supports Ruby, Ocaml, Perl, PHP, Java...","description":"More info at http:\/\/eigenclass.org\/hiki\/simplefold\r\n\r\nsimplefold is a small plugin that improves (for some definition of \"improve\", see the explanation and screenshots at http:\/\/eigenclass.org\/hiki\/simplefold) on other folding methods (syntax, marker, indent, expr). It was originally written for Ruby, but now also supports Objective Caml, PHP, Perl and Java. It features:\r\n* optimized vertical space usage\r\n* sensible foldtext\r\n* top-level folds: one per interesting definition. No need to open a class fold to see which methods it contains. Get a quick overview of the classes\/methods\/functions (whatever applies in the current filetype) with zM.\r\n* optional nested folds for if\/while and so on\r\n* easy to adapt to other filetypes; just by setting 2-3 regexps\r\n\r\nUsage\r\n---------\r\nUse <Leader>f (by default \\f) to fold.\r\n\r\nYou can also use \r\n :Fold UNQUOTED-REGEXP\r\n\r\nto create folds showing the lines matching the given regexp, leaving everything else hidden; e.g.\r\n\r\n :Fold \\vfoo(bar|baz)\r\n\r\nwill create folds starting at each line matching foo(bar|baz), so that these are the only lines you see in your buffer (it's effectively a sort of internal grep).\r\n\r\nSee also vimtip#77 and vimscript #158","4":"More info at http:\/\/eigenclass.org\/hiki\/simplefold\r\n\r\nsimplefold is a small plugin that improves (for some definition of \"improve\", see the explanation and screenshots at http:\/\/eigenclass.org\/hiki\/simplefold) on other folding methods (syntax, marker, indent, expr). It was originally written for Ruby, but now also supports Objective Caml, PHP, Perl and Java. It features:\r\n* optimized vertical space usage\r\n* sensible foldtext\r\n* top-level folds: one per interesting definition. No need to open a class fold to see which methods it contains. Get a quick overview of the classes\/methods\/functions (whatever applies in the current filetype) with zM.\r\n* optional nested folds for if\/while and so on\r\n* easy to adapt to other filetypes; just by setting 2-3 regexps\r\n\r\nUsage\r\n---------\r\nUse <Leader>f (by default \\f) to fold.\r\n\r\nYou can also use \r\n :Fold UNQUOTED-REGEXP\r\n\r\nto create folds showing the lines matching the given regexp, leaving everything else hidden; e.g.\r\n\r\n :Fold \\vfoo(bar|baz)\r\n\r\nwill create folds starting at each line matching foo(bar|baz), so that these are the only lines you see in your buffer (it's effectively a sort of internal grep).\r\n\r\nSee also vimtip#77 and vimscript #158","install_details":"Just place the .vim file in the plugin directory (e.g. ~\/.vim\/plugin).","5":"Just place the .vim file in the plugin directory (e.g. ~\/.vim\/plugin).","first_name":"Mauricio","6":"Mauricio","last_name":"Fernandez","7":"Fernandez","releases":[{"0":"1868","vim_version":"7.0","1":"7.0","script_version":"0.5.0","2":"0.5.0","version_comment":"Initial upload","3":"Initial upload","package":"SimpleFold.vim","4":"SimpleFold.vim","src_id":"7003","5":"7003","creation_date":"1176975571","6":"1176975571"}]},"1867":{"script_id":"1867","0":"1867","script_name":"doctest syntax","1":"doctest syntax","script_type":"syntax","2":"syntax","summary":"Highlighting for Python doctest files","3":"Highlighting for Python doctest files","description":"Syntax file for highlighting Python doctest files. This is usefull for when you have your doctests in a seperate from your source code (in a .txt file). The syntax highlighter will color the ReST headers, code blocks and expected values.","4":"Syntax file for highlighting Python doctest files. This is usefull for when you have your doctests in a seperate from your source code (in a .txt file). The syntax highlighter will color the ReST headers, code blocks and expected values.","install_details":"Place the vim file into a syntax dir and set the filetype to doctest.","5":"Place the vim file into a syntax dir and set the filetype to doctest.","first_name":"Jeroen","6":"Jeroen","last_name":"Vloothuis","7":"Vloothuis","releases":[{"0":"1867","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"doctest.vim","4":"doctest.vim","src_id":"7002","5":"7002","creation_date":"1176973236","6":"1176973236"}]},"1866":{"script_id":"1866","0":"1866","script_name":"tselectbuffer","1":"tselectbuffer","script_type":"utility","2":"utility","summary":"A quick buffer selector\/switcher","3":"A quick buffer selector\/switcher","description":"This plugin provides a simple buffer selector. It doesn't have all the \r\nfeatures other buffer selectors have but can be useful for quickly \r\nswitching to a different buffer or for deleting buffers.\r\n\r\nThe idea is to view the buffer list, to do something, and to close the \r\nbuffer list. If you really want to permanently watch the buffer list to \r\nsee whether it's changed, you might want to use a different plugin.\r\n\r\nFeatures:\r\n    - list buffers, dynamically filter buffers matching a pattern\r\n    - switch to a buffer\r\n    - rename a buffer (you may need to use :saveas! or :w! when writing \r\n    the renamed buffer to disk)\r\n    - delete one or more buffer(s)\r\n\r\n:[N]TSelectBuffer[!]\r\n    List buffers. With a count or a !, show also hidden buffers.\r\n    Keys:\r\n    <cr>  ... Select (close the buffer list)\r\n    <c-s> ... Open in split window\r\n    <c-v> ... Open in vertically split window\r\n    <c-t> ... Open in new tab\r\n    <c-w> ... Show in original window (continue with the buffer list)\r\n    <c-d> ... Delete a buffer\r\n    <c-u> ... Rename a buffer\r\n    <     ... Jump to opened buffer in window\/tab\r\n\r\nSuggested keymaps (put something like this into ~\/.vimrc):\r\n    noremap <m-b> :TSelectBuffer<cr>\r\n    inoremap <m-b> <c-o>:TSelectBuffer<cr>\r\n","4":"This plugin provides a simple buffer selector. It doesn't have all the \r\nfeatures other buffer selectors have but can be useful for quickly \r\nswitching to a different buffer or for deleting buffers.\r\n\r\nThe idea is to view the buffer list, to do something, and to close the \r\nbuffer list. If you really want to permanently watch the buffer list to \r\nsee whether it's changed, you might want to use a different plugin.\r\n\r\nFeatures:\r\n    - list buffers, dynamically filter buffers matching a pattern\r\n    - switch to a buffer\r\n    - rename a buffer (you may need to use :saveas! or :w! when writing \r\n    the renamed buffer to disk)\r\n    - delete one or more buffer(s)\r\n\r\n:[N]TSelectBuffer[!]\r\n    List buffers. With a count or a !, show also hidden buffers.\r\n    Keys:\r\n    <cr>  ... Select (close the buffer list)\r\n    <c-s> ... Open in split window\r\n    <c-v> ... Open in vertically split window\r\n    <c-t> ... Open in new tab\r\n    <c-w> ... Show in original window (continue with the buffer list)\r\n    <c-d> ... Delete a buffer\r\n    <c-u> ... Rename a buffer\r\n    <     ... Jump to opened buffer in window\/tab\r\n\r\nSuggested keymaps (put something like this into ~\/.vimrc):\r\n    noremap <m-b> :TSelectBuffer<cr>\r\n    inoremap <m-b> <c-o>:TSelectBuffer<cr>\r\n","install_details":"vimscript #1863 is required.\r\n\r\nCopy the vim file to ~\/.vim\/plugin\/\r\n\r\n\r\nAlso available via git\r\nhttp:\/\/github.com\/tomtom\/tselectbuffer_vim","5":"vimscript #1863 is required.\r\n\r\nCopy the vim file to ~\/.vim\/plugin\/\r\n\r\n\r\nAlso available via git\r\nhttp:\/\/github.com\/tomtom\/tselectbuffer_vim","first_name":"Tom","6":"Tom","last_name":"Link","7":"Link","releases":[{"0":"1866","vim_version":"7.0","1":"7.0","script_version":"0.7","2":"0.7","version_comment":"- Moved the definition of some variables from plugin\/tselectbuffer.vim to autoload\/tselectbuffer.vim\r\n- Delete buffer: New options: None, all\r\n- Support for g:tselectbuffer#order = \"basename\"\r\n- Require tlib 0.40\r\n","3":"- Moved the definition of some variables from plugin\/tselectbuffer.vim to autoload\/tselectbuffer.vim\r\n- Delete buffer: New options: None, all\r\n- Support for g:tselectbuffer#order = \"basename\"\r\n- Require tlib 0.40\r\n","package":"tselectbuffer.vba","4":"tselectbuffer.vba","src_id":"13974","5":"13974","creation_date":"1286009903","6":"1286009903"},{"0":"1866","vim_version":"7.0","1":"7.0","script_version":"0.6","2":"0.6","version_comment":"- Alternate buffer wasn't initially selected after 0.4\r\n- FIX: <c-s> and similar keys didn't work.\r\n- MRU order (set g:tselectbuffer_order to \"mru\")\r\n","3":"- Alternate buffer wasn't initially selected after 0.4\r\n- FIX: <c-s> and similar keys didn't work.\r\n- MRU order (set g:tselectbuffer_order to \"mru\")\r\n","package":"tselectbuffer.vim","4":"tselectbuffer.vim","src_id":"9596","5":"9596","creation_date":"1228209469","6":"1228209469"},{"0":"1866","vim_version":"7.0","1":"7.0","script_version":"0.4","2":"0.4","version_comment":"- <c-w> ... View file in original window\r\n- < ... Jump to already opened window, preferably on the current tab \r\npage (if any)\r\n- Enabled <c-t> to open buffer in tab\r\n- Require tlib 0.13\r\n- Initially select the alternate buffer\r\n- Make a count act as bang.\r\n- Can be \"suspended\" (i.e. you can switch back to the orignal window)\r\n","3":"- <c-w> ... View file in original window\r\n- < ... Jump to already opened window, preferably on the current tab \r\npage (if any)\r\n- Enabled <c-t> to open buffer in tab\r\n- Require tlib 0.13\r\n- Initially select the alternate buffer\r\n- Make a count act as bang.\r\n- Can be \"suspended\" (i.e. you can switch back to the orignal window)\r\n","package":"tselectbuffer.vim","4":"tselectbuffer.vim","src_id":"7651","5":"7651","creation_date":"1189502797","6":"1189502797"},{"0":"1866","vim_version":"7.0","1":"7.0","script_version":"0.3","2":"0.3","version_comment":"- <c-u>: Rename buffer (and file on disk)\r\n- <c-v>: Show buffers in vertically split windows\r\n- Require tlib 0.9\r\n- \"Delete buffer\" will wipe-out unloaded buffers.\r\n","3":"- <c-u>: Rename buffer (and file on disk)\r\n- <c-v>: Show buffers in vertically split windows\r\n- Require tlib 0.9\r\n- \"Delete buffer\" will wipe-out unloaded buffers.\r\n","package":"tselectbuffer.vim","4":"tselectbuffer.vim","src_id":"7362","5":"7362","creation_date":"1184663178","6":"1184663178"},{"0":"1866","vim_version":"7.0","1":"7.0","script_version":"0.2","2":"0.2","version_comment":"- Minor improvements\r\n","3":"- Minor improvements\r\n","package":"tselectbuffer.vim","4":"tselectbuffer.vim","src_id":"7131","5":"7131","creation_date":"1179383044","6":"1179383044"},{"0":"1866","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"tselectbuffer.vim","4":"tselectbuffer.vim","src_id":"7001","5":"7001","creation_date":"1176892322","6":"1176892322"}]},"1865":{"script_id":"1865","0":"1865","script_name":"tselectfiles","1":"tselectfiles","script_type":"utility","2":"utility","summary":"A quick file selector\/browser\/explorer (sort of)","3":"A quick file selector\/browser\/explorer (sort of)","description":"This plugin provides a simple file browser. It is not a full blown \r\nexplorer but can be nevertheless be useful for quickly selecting a few \r\nfiles or renaming them.\r\n\r\nAs the plugin does some caching in the background, the filelist is only \r\ngenerated once for each path or when called with [!]. In conjuncture \r\nwith the use of the [wbg]:tselectfile_filter_rx variable, this provides \r\nfor use as a simple ad-hoc project manager.\r\n\r\nVIM-CENTRIC EXAMPLE:\r\nWhen I open a file under \"~\/vimfiles\", I set b:tselectfiles_dir \r\nto all the relevant directories under \"~\/vimfiles\" and then set \r\nb:tselectfile_filter_rx = expand('%:t:r'). Thus, when I open \r\n\"~\/vimfiles\/plugin\/foo.vim\", b:tselectfile_filter_rx is \"foo\", and \r\n:TSelectFiles shows all the files under \"~\/vimfiles\" matching \"foo\".\r\n\r\nFeatures:\r\n    - list files (recursively or the in the current directory only), \r\n      dynamically select files matching a pattern\r\n    - open files\r\n    - preview files\r\n    - rename\/move files\r\n    - batch rename\/move files (using a regular expression)\r\n    - copy files\r\n    - delete files\r\n    - show file info\r\n\r\nAdvanced uses:\r\n\r\nRelated files: If you set |g:tselectfiles_filter_rx| to some appropriate \r\nvalue, only files matching that regexp will be shown initially. This can \r\nbe used to restrict the list to \"related\" files. (The initial filter can \r\nbe removed by pressing <c-bs>.) See also |tselectfiles#BaseFilter()| and \r\n|g:tselectfiles_part_subst|.\r\n\r\nRolodex: If a filename matches an entry in \r\n|g:tselectfiles_filedescription_rx| (a dictionnary patter => funcref), \r\nfuncref(filename) will be called to retrieve the file's description. \r\nThis function could be used to extract metadata or selected lines from \r\nthe file etc. By mapping one record onto one file, you would get some \r\nsort of rolodex-like database. See \r\n|tselectfiles#FormatVikiMetaDataOrFirstLine()| for an example for \r\nviki\/deplate (vimscript #861) formatted files.\r\n\r\nDemo: http:\/\/vimsomnia.blogspot.com\/2012\/09\/tselectfiles-demo.html","4":"This plugin provides a simple file browser. It is not a full blown \r\nexplorer but can be nevertheless be useful for quickly selecting a few \r\nfiles or renaming them.\r\n\r\nAs the plugin does some caching in the background, the filelist is only \r\ngenerated once for each path or when called with [!]. In conjuncture \r\nwith the use of the [wbg]:tselectfile_filter_rx variable, this provides \r\nfor use as a simple ad-hoc project manager.\r\n\r\nVIM-CENTRIC EXAMPLE:\r\nWhen I open a file under \"~\/vimfiles\", I set b:tselectfiles_dir \r\nto all the relevant directories under \"~\/vimfiles\" and then set \r\nb:tselectfile_filter_rx = expand('%:t:r'). Thus, when I open \r\n\"~\/vimfiles\/plugin\/foo.vim\", b:tselectfile_filter_rx is \"foo\", and \r\n:TSelectFiles shows all the files under \"~\/vimfiles\" matching \"foo\".\r\n\r\nFeatures:\r\n    - list files (recursively or the in the current directory only), \r\n      dynamically select files matching a pattern\r\n    - open files\r\n    - preview files\r\n    - rename\/move files\r\n    - batch rename\/move files (using a regular expression)\r\n    - copy files\r\n    - delete files\r\n    - show file info\r\n\r\nAdvanced uses:\r\n\r\nRelated files: If you set |g:tselectfiles_filter_rx| to some appropriate \r\nvalue, only files matching that regexp will be shown initially. This can \r\nbe used to restrict the list to \"related\" files. (The initial filter can \r\nbe removed by pressing <c-bs>.) See also |tselectfiles#BaseFilter()| and \r\n|g:tselectfiles_part_subst|.\r\n\r\nRolodex: If a filename matches an entry in \r\n|g:tselectfiles_filedescription_rx| (a dictionnary patter => funcref), \r\nfuncref(filename) will be called to retrieve the file's description. \r\nThis function could be used to extract metadata or selected lines from \r\nthe file etc. By mapping one record onto one file, you would get some \r\nsort of rolodex-like database. See \r\n|tselectfiles#FormatVikiMetaDataOrFirstLine()| for an example for \r\nviki\/deplate (vimscript #861) formatted files.\r\n\r\nDemo: http:\/\/vimsomnia.blogspot.com\/2012\/09\/tselectfiles-demo.html","install_details":"Edit the vba file and type: >\r\n\r\n    :so %\r\n\r\nSee :help vimball for details. If you have difficulties, please make \r\nsure, you have the current version of vimball (vimscript #1502) \r\ninstalled.\r\n\r\nThis script requires tlib (vimscript #1863) to be installed.\r\n\r\n\r\nAlso available via git\r\nhttp:\/\/github.com\/tomtom\/tselectfiles_vim","5":"Edit the vba file and type: >\r\n\r\n    :so %\r\n\r\nSee :help vimball for details. If you have difficulties, please make \r\nsure, you have the current version of vimball (vimscript #1502) \r\ninstalled.\r\n\r\nThis script requires tlib (vimscript #1863) to be installed.\r\n\r\n\r\nAlso available via git\r\nhttp:\/\/github.com\/tomtom\/tselectfiles_vim","first_name":"Tom","6":"Tom","last_name":"Link","7":"Link","releases":[{"0":"1865","vim_version":"7.0","1":"7.0","script_version":"0.11","2":"0.11","version_comment":"- tselectfiles#AgentPreviewFile(): redraw\n- Convert encoding if the assumed &fenc != &enc\n- tselectfiles#FormatVikiMetaDataOrFirstLine: Reversed argument order (world is optional)\n- Renamed variables named g:tselectfiles_* to g:tselectfiles#*\n- .gitignore\n- g:tselectfiles#use_vcs\nMD5 checksum: 41885c7229478d59e37fd7a222767a61","3":"- tselectfiles#AgentPreviewFile(): redraw\n- Convert encoding if the assumed &fenc != &enc\n- tselectfiles#FormatVikiMetaDataOrFirstLine: Reversed argument order (world is optional)\n- Renamed variables named g:tselectfiles_* to g:tselectfiles#*\n- .gitignore\n- g:tselectfiles#use_vcs\nMD5 checksum: 41885c7229478d59e37fd7a222767a61","package":"tselectfiles.vba","4":"tselectfiles.vba","src_id":"18627","5":"18627","creation_date":"1347803736","6":"1347803736"},{"0":"1865","vim_version":"7.0","1":"7.0","script_version":"0.10","2":"0.10","version_comment":"- :TSelectFiles, :TSelectFilesInSubdirs, tselectfiles#SelectFiles: take \r\nan initial pattern as the second optional argument (i.e. if you pass a \r\ndirectory as first optional argument, you'll have to escape blanks with \r\na backslash).\r\n- tselectfiles#SelectFiles: if dir is &, search &path\r\n- tselectfiles_filter_rx is always evaluated unless a pattern is \r\nprovided as extra argument\r\n- tselectfiles_prefix is always evaluated\r\n","3":"- :TSelectFiles, :TSelectFilesInSubdirs, tselectfiles#SelectFiles: take \r\nan initial pattern as the second optional argument (i.e. if you pass a \r\ndirectory as first optional argument, you'll have to escape blanks with \r\na backslash).\r\n- tselectfiles#SelectFiles: if dir is &, search &path\r\n- tselectfiles_filter_rx is always evaluated unless a pattern is \r\nprovided as extra argument\r\n- tselectfiles_prefix is always evaluated\r\n","package":"tselectfiles.vba.gz","4":"tselectfiles.vba.gz","src_id":"11510","5":"11510","creation_date":"1255242874","6":"1255242874"},{"0":"1865","vim_version":"7.0","1":"7.0","script_version":"0.9","2":"0.9","version_comment":"- Don't assume s:select_files_pattern.limit is set\r\n- Include .* in tselectfiles_hidden_rx\r\n- FIX: Include .* files (but hide them by default; thanks to \r\nnaquad\/Daniil F.).\r\n- FIX: If 'splitbelow' is false, opening buffers in split view didn't \r\nproperly work (thanks to naquad\/Daniil F.)\r\n","3":"- Don't assume s:select_files_pattern.limit is set\r\n- Include .* in tselectfiles_hidden_rx\r\n- FIX: Include .* files (but hide them by default; thanks to \r\nnaquad\/Daniil F.).\r\n- FIX: If 'splitbelow' is false, opening buffers in split view didn't \r\nproperly work (thanks to naquad\/Daniil F.)\r\n","package":"tselectfiles.vba.gz","4":"tselectfiles.vba.gz","src_id":"9958","5":"9958","creation_date":"1234457577","6":"1234457577"},{"0":"1865","vim_version":"7.0","1":"7.0","script_version":"0.8","2":"0.8","version_comment":"- Require tlib 0.28\r\n","3":"- Require tlib 0.28\r\n","package":"tselectfiles.vba.gz","4":"tselectfiles.vba.gz","src_id":"9594","5":"9594","creation_date":"1228209364","6":"1228209364"},{"0":"1865","vim_version":"7.0","1":"7.0","script_version":"0.7","2":"0.7","version_comment":"- NEW: g:tselectfiles_part_subst* variables (for use with tselectfiles#BaseFilter())\r\n- NEW: [bg]:tselectfiles_filter_basename variable (if true, match on basename only)\r\n","3":"- NEW: g:tselectfiles_part_subst* variables (for use with tselectfiles#BaseFilter())\r\n- NEW: [bg]:tselectfiles_filter_basename variable (if true, match on basename only)\r\n","package":"tselectfiles.vba.gz","4":"tselectfiles.vba.gz","src_id":"9360","5":"9360","creation_date":"1224173650","6":"1224173650"},{"0":"1865","vim_version":"7.0","1":"7.0","script_version":"0.6","2":"0.6","version_comment":"- [gbw]tselectfiles_prefix: Remove prefix from filenames in list\r\n- [gbw]tselectfiles_limit variable\r\n- [wbg]:tselectfiles_filter_rx is used only when no directory is given on the command line.\r\n- Require tlib >= 0.18\r\n- If the filename matches an entry in g:tselectfiles_filedescription_rx, use the expression there to construct a file description (eg the file's first line)\r\n- Option to run vimgrep on selected files.\r\n- tselectfiles#BaseFilter(): Set b:tselectfiles_filter_rx to something useful.\r\n- tselectfiles#BaseFilter(): takes 2 optional arguments to substitute a rx in the current buffer's filename.\r\n- tselectfiles_filter_rx: Set as array\r\n- Problem when browsing single directories\r\n","3":"- [gbw]tselectfiles_prefix: Remove prefix from filenames in list\r\n- [gbw]tselectfiles_limit variable\r\n- [wbg]:tselectfiles_filter_rx is used only when no directory is given on the command line.\r\n- Require tlib >= 0.18\r\n- If the filename matches an entry in g:tselectfiles_filedescription_rx, use the expression there to construct a file description (eg the file's first line)\r\n- Option to run vimgrep on selected files.\r\n- tselectfiles#BaseFilter(): Set b:tselectfiles_filter_rx to something useful.\r\n- tselectfiles#BaseFilter(): takes 2 optional arguments to substitute a rx in the current buffer's filename.\r\n- tselectfiles_filter_rx: Set as array\r\n- Problem when browsing single directories\r\n","package":"tselectfiles.vba.gz","4":"tselectfiles.vba.gz","src_id":"9310","5":"9310","creation_date":"1223199192","6":"1223199192"},{"0":"1865","vim_version":"7.0","1":"7.0","script_version":"0.4","2":"0.4","version_comment":"- \"Delete file\" will ask whether to delete a corresponding buffer too.\r\n- <c-w> ... View file in original window\r\n- Disabled <c-o> Open dir\r\n- Require tlib >= 0.13\r\n- When renaming a file that's loaded, rename also the buffer.\r\n- You can filter the list of selected files via setting the \r\n[wbg]:tselectfiles_filter_rx variable.\r\n- Renamed g:tselectfiles_no_cache to g:tselectfiles_no_cache_rx\r\n- [bg]:tselectfiles_use_cache and [bg]:tselectfiles_no_cache_rx can now \r\nalso be set per buffer.\r\n- Renamed some variables from tselectfile_* to tselectfiles_*.\r\n- Can be \"suspended\" (i.e. you can switch back to the orignal window)\r\n","3":"- \"Delete file\" will ask whether to delete a corresponding buffer too.\r\n- <c-w> ... View file in original window\r\n- Disabled <c-o> Open dir\r\n- Require tlib >= 0.13\r\n- When renaming a file that's loaded, rename also the buffer.\r\n- You can filter the list of selected files via setting the \r\n[wbg]:tselectfiles_filter_rx variable.\r\n- Renamed g:tselectfiles_no_cache to g:tselectfiles_no_cache_rx\r\n- [bg]:tselectfiles_use_cache and [bg]:tselectfiles_no_cache_rx can now \r\nalso be set per buffer.\r\n- Renamed some variables from tselectfile_* to tselectfiles_*.\r\n- Can be \"suspended\" (i.e. you can switch back to the orignal window)\r\n","package":"tselectfiles.vba.gz","4":"tselectfiles.vba.gz","src_id":"7649","5":"7649","creation_date":"1189502647","6":"1189502647"},{"0":"1865","vim_version":"7.0","1":"7.0","script_version":"0.2","2":"0.2","version_comment":"- Require tlib 0.9\r\n- \"Delete file\" will ask whether to delete a corresponding buffer too.\r\n","3":"- Require tlib 0.9\r\n- \"Delete file\" will ask whether to delete a corresponding buffer too.\r\n","package":"tselectfiles.vim","4":"tselectfiles.vim","src_id":"7361","5":"7361","creation_date":"1184663144","6":"1184663144"},{"0":"1865","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"tselectfiles.vim","4":"tselectfiles.vim","src_id":"7000","5":"7000","creation_date":"1176892221","6":"1176892221"}]},"1864":{"script_id":"1864","0":"1864","script_name":"tmru","1":"tmru","script_type":"utility","2":"utility","summary":"Most Recently Used Files","3":"Most Recently Used Files","description":"This plugin allows users to open recently used files. Users can filter \r\nthe file list by typing a pattern. Users can open multiple files at \r\nonce. The list of recently used files is synchronized across multiple \r\ninstances of (g)vim running simultaneously.\r\n\r\nBy default, tmru will remember 500 files (accessible via the \r\n:TRecentlyUsedFiles command). The list can be easily filtered (users \r\ncan optionally use fuzzy patterns, which is not enabled by default though).\r\n\r\nFiles can be groups in sessions:\r\n\r\n     - Use named sessions to group files that are frequently edited together\r\n     - Use numbered sessions to open files you edited during one of the latest editing sessions\r\n\r\nFiles can be marked as \"sticky\" -- they will never be removed from the list.\r\n\r\nCommands:\r\n\r\n:TRecentlyUsedFiles ... open one or more recently used file(s)\r\n:TRecentlyUsedFilesEdit ... edit the mru list\r\n","4":"This plugin allows users to open recently used files. Users can filter \r\nthe file list by typing a pattern. Users can open multiple files at \r\nonce. The list of recently used files is synchronized across multiple \r\ninstances of (g)vim running simultaneously.\r\n\r\nBy default, tmru will remember 500 files (accessible via the \r\n:TRecentlyUsedFiles command). The list can be easily filtered (users \r\ncan optionally use fuzzy patterns, which is not enabled by default though).\r\n\r\nFiles can be groups in sessions:\r\n\r\n     - Use named sessions to group files that are frequently edited together\r\n     - Use numbered sessions to open files you edited during one of the latest editing sessions\r\n\r\nFiles can be marked as \"sticky\" -- they will never be removed from the list.\r\n\r\nCommands:\r\n\r\n:TRecentlyUsedFiles ... open one or more recently used file(s)\r\n:TRecentlyUsedFilesEdit ... edit the mru list\r\n","install_details":"Edit the vba file and type: >\r\n\r\n    :so %\r\n\r\nSee :help vimball for details. If you have difficulties or use vim 7.0,\r\nplease make sure, you have the current version of vimball\r\n(vimscript #1502) installed or update your runtime.\r\n\r\ntlib (vimscript #1863) is required.\r\n\r\nSuggested keymaps (put something like this into ~\/.vimrc):\r\n\r\n    noremap <m-r> :TRecentlyUsedFiles<cr>\r\n\r\nIn order to disable the sub-menu, set g:tmruMenu to \"\" in your vimrc file.\r\n","5":"Edit the vba file and type: >\r\n\r\n    :so %\r\n\r\nSee :help vimball for details. If you have difficulties or use vim 7.0,\r\nplease make sure, you have the current version of vimball\r\n(vimscript #1502) installed or update your runtime.\r\n\r\ntlib (vimscript #1863) is required.\r\n\r\nSuggested keymaps (put something like this into ~\/.vimrc):\r\n\r\n    noremap <m-r> :TRecentlyUsedFiles<cr>\r\n\r\nIn order to disable the sub-menu, set g:tmruMenu to \"\" in your vimrc file.\r\n","first_name":"Tom","6":"Tom","last_name":"Link","7":"Link","releases":[{"0":"1864","vim_version":"7.0","1":"7.0","script_version":"1.03","2":"1.03","version_comment":"- Set the initial index in the list view to the first non-sticky file\n- FIX #37: Clarfiy doc of g:tmru#display_relative_filename\n- Exclude files on truecrypt volumes (linux)\n- Always enable save on exit\n- FIX #40: Insert files at the right position; sort list only on exit\nMD5 checksum: 89f6d47aa31a9df4022bc3e78f887fec","3":"- Set the initial index in the list view to the first non-sticky file\n- FIX #37: Clarfiy doc of g:tmru#display_relative_filename\n- Exclude files on truecrypt volumes (linux)\n- Always enable save on exit\n- FIX #40: Insert files at the right position; sort list only on exit\nMD5 checksum: 89f6d47aa31a9df4022bc3e78f887fec","package":"tmru.vba","4":"tmru.vba","src_id":"22183","5":"22183","creation_date":"1405012559","6":"1405012559"},{"0":"1864","vim_version":"7.0","1":"7.0","script_version":"1.02","2":"1.02","version_comment":"  - repackaged  \r\n  - addon-info\r\n  - Use cwd as base directory for relative filenames (fixes #30)\r\n  - Enable configuration via g:tmru_world (fixes #31)\r\n  - FIX for previous commit\r\n  - Make automatic removal on non-existing files configurable & consistent: g:tmru#auto_remove_unreadable (fixes #32)\r\n  - Only use `:drop` with GUI enabled\r\n  - Support for b:tmru_world\r\n  - Support for g:tmru_select_filter (and b:tmru_select_filter) (fixes #34)\r\n  - Support for named sessions (requires tlib 1.06)\r\n  - Help template\r\n  - Don't call buflisted() on all files in the tmru list (fixes #36)\r\n  - s:SetSessions(): Use (bufexists(filename) && buflisted(filename)\r\n  - Really call buflisted() only for vim buffers (fixes #36)\r\n  - g:tmru#sessions_len: Trim list of numbered sessions\r\n  - g:tmru#set_filename_indicators\r\n  MD5 checksum: f526a3b4c97827e0c51388a916b2f4aa\r\n","3":"  - repackaged  \r\n  - addon-info\r\n  - Use cwd as base directory for relative filenames (fixes #30)\r\n  - Enable configuration via g:tmru_world (fixes #31)\r\n  - FIX for previous commit\r\n  - Make automatic removal on non-existing files configurable & consistent: g:tmru#auto_remove_unreadable (fixes #32)\r\n  - Only use `:drop` with GUI enabled\r\n  - Support for b:tmru_world\r\n  - Support for g:tmru_select_filter (and b:tmru_select_filter) (fixes #34)\r\n  - Support for named sessions (requires tlib 1.06)\r\n  - Help template\r\n  - Don't call buflisted() on all files in the tmru list (fixes #36)\r\n  - s:SetSessions(): Use (bufexists(filename) && buflisted(filename)\r\n  - Really call buflisted() only for vim buffers (fixes #36)\r\n  - g:tmru#sessions_len: Trim list of numbered sessions\r\n  - g:tmru#set_filename_indicators\r\n  MD5 checksum: f526a3b4c97827e0c51388a916b2f4aa\r\n","package":"tmru.vba","4":"tmru.vba","src_id":"21335","5":"21335","creation_date":"1389963979","6":"1389963979"},{"0":"1864","vim_version":"7.0","1":"7.0","script_version":"1.00","2":"1.00","version_comment":"- Use tlib#persistent\n- Error when the list of recently used files was empty\n- Handle multiple running instances of vim (fixes #23)\n- s:MruRetrieve(...): call tlib#persistent#Get() only once\n- TMRU: Alias for |:TRecentlyUsedFiles|.\n- Removed support for metadata (which was broken anyway)\n- on edit ignore swap file exists error + use v:exception for other errors\n- Set g:tmruSize dependent on whether viminfo is used\n- File properties again (only if viminfo is not used)\n- Mark files as persistent\/sticky (i.e. the won't be removed from the list)\n- Fix problem on windows (val -> v:val)\n- Normalize filenames when registering a buffer; minor improvements\n- Improved synchronization of mru lists across multiple instances of vim (fixes #26)\n- Mark sticky filenames with \"s\"\n- g:tmru_drop\n- Renamed g:tmru_single_child_mode to g:tmru_single_instance_mode\n- Filename indicators (s for sticky files; requires tlib 1.04)\n- Name buffer __TMRU__\n- s:SelectMRU(): Don't use s:FindIndex() and make sure to use the currect mru list (fixes #27)\n- Make sure to save the file list when removing outdated files\n- Make sure to save the mru list when it has been modified upon the user's request\n- Re-introduced :TRecentlyUsedFilesSessions command.\n- Code reorganization\n- Fix use of relative filenames (closes #29)\n- Don't simply record a file's latest session but every session it was in\n- g:tmru_sessions = 9\n- Make sure to register file's that are already opened when tmru is loaded\nMD5 checksum: 82ed5a7b285c6ca1ec7bd0a2d5795039","3":"- Use tlib#persistent\n- Error when the list of recently used files was empty\n- Handle multiple running instances of vim (fixes #23)\n- s:MruRetrieve(...): call tlib#persistent#Get() only once\n- TMRU: Alias for |:TRecentlyUsedFiles|.\n- Removed support for metadata (which was broken anyway)\n- on edit ignore swap file exists error + use v:exception for other errors\n- Set g:tmruSize dependent on whether viminfo is used\n- File properties again (only if viminfo is not used)\n- Mark files as persistent\/sticky (i.e. the won't be removed from the list)\n- Fix problem on windows (val -> v:val)\n- Normalize filenames when registering a buffer; minor improvements\n- Improved synchronization of mru lists across multiple instances of vim (fixes #26)\n- Mark sticky filenames with \"s\"\n- g:tmru_drop\n- Renamed g:tmru_single_child_mode to g:tmru_single_instance_mode\n- Filename indicators (s for sticky files; requires tlib 1.04)\n- Name buffer __TMRU__\n- s:SelectMRU(): Don't use s:FindIndex() and make sure to use the currect mru list (fixes #27)\n- Make sure to save the file list when removing outdated files\n- Make sure to save the mru list when it has been modified upon the user's request\n- Re-introduced :TRecentlyUsedFilesSessions command.\n- Code reorganization\n- Fix use of relative filenames (closes #29)\n- Don't simply record a file's latest session but every session it was in\n- g:tmru_sessions = 9\n- Make sure to register file's that are already opened when tmru is loaded\nMD5 checksum: 82ed5a7b285c6ca1ec7bd0a2d5795039","package":"tmru.vba","4":"tmru.vba","src_id":"19180","5":"19180","creation_date":"1355421988","6":"1355421988"},{"0":"1864","vim_version":"7.0","1":"7.0","script_version":"0.10","2":"0.10","version_comment":"- .gitignore\n- Don't check for has('vim_starting')\n- EditMRU(): Save the new, not the old list\n- Fix g:tmruExclude default for '+shellslash'.\n- Attempt at canonical filenames on Windows.\n- Merge branch 'canonical'\n- tmruExclude, s:PS: use temporary script-local variable\n- Also exclude *.tmp and COMMIT_EDITMSG (suggested by blueyed)\n- Ignore `git-rebase-todo` and `quickfix` by default.\n- Make filename relative to home dir.\n- Fix CheckFilenames.\n- Expand() filename in CanonicalizeFilename for \"~\".\n- Optimize performace with MruRetrieve.\n- Deactivate `:~` modification; performance reasons.\n- Use `substitute` instead of `fnamemodify`.\n- s:MruRetrieve(): Use single quotes\n- Do not split &suffixes on escaped comma.\n- Remove duplicates in CheckFilenames.\n- Use unlet() instead of keys() to remove dupes.\n- Exclude 'fugitive:' files by default.\n- Fix g:tmruExclude default pattern.\n- Normalization of entries in CheckFilenames.\n- g:tmruEvents is a dictionary now (was a string)\n- Some optimizations with respect to when the list should be saved\n- Experimental: Maintain some metadata\n- :TMRUSession command\n- Undo some over-engineering :-), fixes #14\n- s:CheckFilenames(): Also remove metadata when removing a dupe\n- Fix setup of g:TMRU_METADATA; undefined \"mru\".\n- s:MruRegister(): also remove metadata when removing an item\n- disabled sessions\n- Moved function s:MruRegister()\n- Added BufDelete to g:tmruEvents\n- s:AutoMRU() takes event argument\n- g:tmru_debug\n- g:tmru_check_disk (fixes #20)\n- tmru#DisplayUnreadableFiles(mru)\nMD5 checksum: 7c61e5342a1551f30a2d61fd7dd4965e","3":"- .gitignore\n- Don't check for has('vim_starting')\n- EditMRU(): Save the new, not the old list\n- Fix g:tmruExclude default for '+shellslash'.\n- Attempt at canonical filenames on Windows.\n- Merge branch 'canonical'\n- tmruExclude, s:PS: use temporary script-local variable\n- Also exclude *.tmp and COMMIT_EDITMSG (suggested by blueyed)\n- Ignore `git-rebase-todo` and `quickfix` by default.\n- Make filename relative to home dir.\n- Fix CheckFilenames.\n- Expand() filename in CanonicalizeFilename for \"~\".\n- Optimize performace with MruRetrieve.\n- Deactivate `:~` modification; performance reasons.\n- Use `substitute` instead of `fnamemodify`.\n- s:MruRetrieve(): Use single quotes\n- Do not split &suffixes on escaped comma.\n- Remove duplicates in CheckFilenames.\n- Use unlet() instead of keys() to remove dupes.\n- Exclude 'fugitive:' files by default.\n- Fix g:tmruExclude default pattern.\n- Normalization of entries in CheckFilenames.\n- g:tmruEvents is a dictionary now (was a string)\n- Some optimizations with respect to when the list should be saved\n- Experimental: Maintain some metadata\n- :TMRUSession command\n- Undo some over-engineering :-), fixes #14\n- s:CheckFilenames(): Also remove metadata when removing a dupe\n- Fix setup of g:TMRU_METADATA; undefined \"mru\".\n- s:MruRegister(): also remove metadata when removing an item\n- disabled sessions\n- Moved function s:MruRegister()\n- Added BufDelete to g:tmruEvents\n- s:AutoMRU() takes event argument\n- g:tmru_debug\n- g:tmru_check_disk (fixes #20)\n- tmru#DisplayUnreadableFiles(mru)\nMD5 checksum: 7c61e5342a1551f30a2d61fd7dd4965e","package":"tmru.vba","4":"tmru.vba","src_id":"17321","5":"17321","creation_date":"1327652069","6":"1327652069"},{"0":"1864","vim_version":"7.0","1":"7.0","script_version":"0.9","2":"0.9","version_comment":"Please see http:\/\/github.com\/tomtom\/tmru_vim\/commits\/master\/\nMD5 checksum: 0b6a19a9e793340f26616209e058606e","3":"Please see http:\/\/github.com\/tomtom\/tmru_vim\/commits\/master\/\nMD5 checksum: 0b6a19a9e793340f26616209e058606e","package":"tmru.vba","4":"tmru.vba","src_id":"14163","5":"14163","creation_date":"1288627033","6":"1288627033"},{"0":"1864","vim_version":"7.0","1":"7.0","script_version":"0.7","2":"0.7","version_comment":"If viminfo doesn't include '!', then use tlib#cache to save the file list.","3":"If viminfo doesn't include '!', then use tlib#cache to save the file list.","package":"tmru.vba.gz","4":"tmru.vba.gz","src_id":"10171","5":"10171","creation_date":"1236778213","6":"1236778213"},{"0":"1864","vim_version":"7.0","1":"7.0","script_version":"0.6","2":"0.6","version_comment":"- g:tmruEvents can be configured (eg. BufEnter)\r\n- Require tlib 0.28\r\n","3":"- g:tmruEvents can be configured (eg. BufEnter)\r\n- Require tlib 0.28\r\n","package":"tmru.vba.gz","4":"tmru.vba.gz","src_id":"9593","5":"9593","creation_date":"1228209335","6":"1228209335"},{"0":"1864","vim_version":"7.0","1":"7.0","script_version":"0.5","2":"0.5","version_comment":"- Don't escape backslashes for :edit","3":"- Don't escape backslashes for :edit","package":"tmru.vim","4":"tmru.vim","src_id":"7791","5":"7791","creation_date":"1192229242","6":"1192229242"},{"0":"1864","vim_version":"7.0","1":"7.0","script_version":"0.4","2":"0.4","version_comment":"- <c-w> ... View file in original window\r\n- <c-i> ... Show file info\r\n- <c-t> ... Show in tab\r\n- Require tlib >= 0.13\r\n","3":"- <c-w> ... View file in original window\r\n- <c-i> ... Show file info\r\n- <c-t> ... Show in tab\r\n- Require tlib >= 0.13\r\n","package":"tmru.vim","4":"tmru.vim","src_id":"7650","5":"7650","creation_date":"1189502771","6":"1189502771"},{"0":"1864","vim_version":"7.0","1":"7.0","script_version":"0.3","2":"0.3","version_comment":"- Autocmds use expand('%') instead of expand('<afile>')\r\n- Build menu (if the prefix g:tmruMenu isn't empty)\r\n- Key shortcuts to open files in (vertically) split windows or tabs\r\n- Require tlib >= 0.9\r\n","3":"- Autocmds use expand('%') instead of expand('<afile>')\r\n- Build menu (if the prefix g:tmruMenu isn't empty)\r\n- Key shortcuts to open files in (vertically) split windows or tabs\r\n- Require tlib >= 0.9\r\n","package":"tmru.vim","4":"tmru.vim","src_id":"7360","5":"7360","creation_date":"1184663053","6":"1184663053"},{"0":"1864","vim_version":"7.0","1":"7.0","script_version":"0.2","2":"0.2","version_comment":"- :TRecentlyUsedFilesEdit\r\n- Don't register nofile buffers or buffers with no filename.\r\n- <c-c> copy file name(s) (to @*)\r\n- When !has('fname_case'), ignore case when checking if a filename is \r\nalready registered.\r\n","3":"- :TRecentlyUsedFilesEdit\r\n- Don't register nofile buffers or buffers with no filename.\r\n- <c-c> copy file name(s) (to @*)\r\n- When !has('fname_case'), ignore case when checking if a filename is \r\nalready registered.\r\n","package":"tmru.vim","4":"tmru.vim","src_id":"7114","5":"7114","creation_date":"1179224500","6":"1179224500"},{"0":"1864","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"tmru.vim","4":"tmru.vim","src_id":"6999","5":"6999","creation_date":"1176892065","6":"1176892065"}]},"1863":{"script_id":"1863","0":"1863","script_name":"tlib","1":"tlib","script_type":"utility","2":"utility","summary":"Some utility functions","3":"Some utility functions","description":"This library provides some utility functions. There isn't much need to \r\ninstall it unless another plugin requires you to do so.\r\n\r\nThe most useful functions provided by this library probably are:\r\n\r\ntlib#input#List(), tlib#input#ListW()\r\n    - Display a list\r\n    - Dynamically filter items matching a pattern (somethat like google)\r\n        - E.g. you filter for \"foo -bar\": show all entries containing foo but not bar.\r\n    - Select items from a list\r\n    - Do stuff\r\n        - Developers can define keys that trigger some action with the \r\n          selected items\r\n    - Demo: http:\/\/vimsomnia.blogspot.com\/2010\/11\/selecting-items-from-list-with-tlibs.html\r\n\r\ntlib#input#EditList\r\n    + Edit a list (copy, cut, paste, delete, edit ...)\r\n\r\n:TLet VAR = VALUE\r\n    Set a variable only if it doesn't already exist.\r\n\r\n:TScratch\r\n    Open a scratch buffer (a buffer without a file).\r\n\r\n:TVarArg VAR1, [VAR2, DEFAULT2] ...\r\n    Handle \"rest\" (variable) arguments in functions.\r\n    EXAMPLES:\r\n      function! Foo(...)\r\n          TVarArg ['a', 1], 'b'\r\n          echo 'a='. a\r\n          echo 'b='. b\r\n      endf\r\n\r\nTBrowseOutput COMMAND\r\n    Every wondered how to effciently browse the output of a command \r\n    without redirecting it to a file? This command takes a command as \r\n    argument and presents the output via |tlib#input#List()| so that you \r\n    can easily search for a keyword (e.g. the name of a variable or \r\n    function) and the like.\r\n    \r\n    If you press enter, the selected line will be copied to the command \r\n    line. Press ESC to cancel browsing.\r\n    \r\n    EXAMPLES:\r\n      TBrowseOutput 20verb TeaseTheCulprit\r\n      TBrowseOutput let\r\n      TBrowseOutput map\r\n\r\n\r\nRelated (small) plugins that utilize tlib and thus provide some degree of uniform user experience:\r\n    tbibtools (vimscript #1915): bibtex-related utilities (sort, reformat, list contents ...)\r\n    tmarks (vimscript #2594): Browse, place, & delete marks\r\n    tmboxbrowser (vimscript #1906): A mbox browser -- Read your e-mails with vim\r\n    tmru (vimscript #1864): Most Recently Used Files\r\n    trag (vimscript #2033): A slightly language-aware alternative to grep\r\n    tregisters (vimscript #2017): List, edit, and run\/execute registers\/clipboards\r\n    tselectbuffer (vimscript #1866): A quick buffer selector\/switcher\r\n    tselectfiles (vimscript #1865): A quick file selector\/browser\/explorer (sort of)\r\n    ttagecho (vimscript #2055): Show current tag information\r\n    ttagcomplete (vimscript #2069): Context-sensitive tags-based completion and code skeletons\r\n    ttags (vimscript #2018): Tag list browser (List, filter, preview, jump to tags)\r\n    ttoc (vimscript #2014): A regexp-based table of contents of the current buffer\r\n    vikitasks (vimscript #2894): Search viki files for tasks and display them in a list\r\n\r\n\r\nFor full details, please see: \r\nhttp:\/\/github.com\/tomtom\/tlib_vim\/blob\/master\/doc\/tlib.txt\r\n\r\nAlso available via git\r\nhttp:\/\/github.com\/tomtom\/tlib_vim","4":"This library provides some utility functions. There isn't much need to \r\ninstall it unless another plugin requires you to do so.\r\n\r\nThe most useful functions provided by this library probably are:\r\n\r\ntlib#input#List(), tlib#input#ListW()\r\n    - Display a list\r\n    - Dynamically filter items matching a pattern (somethat like google)\r\n        - E.g. you filter for \"foo -bar\": show all entries containing foo but not bar.\r\n    - Select items from a list\r\n    - Do stuff\r\n        - Developers can define keys that trigger some action with the \r\n          selected items\r\n    - Demo: http:\/\/vimsomnia.blogspot.com\/2010\/11\/selecting-items-from-list-with-tlibs.html\r\n\r\ntlib#input#EditList\r\n    + Edit a list (copy, cut, paste, delete, edit ...)\r\n\r\n:TLet VAR = VALUE\r\n    Set a variable only if it doesn't already exist.\r\n\r\n:TScratch\r\n    Open a scratch buffer (a buffer without a file).\r\n\r\n:TVarArg VAR1, [VAR2, DEFAULT2] ...\r\n    Handle \"rest\" (variable) arguments in functions.\r\n    EXAMPLES:\r\n      function! Foo(...)\r\n          TVarArg ['a', 1], 'b'\r\n          echo 'a='. a\r\n          echo 'b='. b\r\n      endf\r\n\r\nTBrowseOutput COMMAND\r\n    Every wondered how to effciently browse the output of a command \r\n    without redirecting it to a file? This command takes a command as \r\n    argument and presents the output via |tlib#input#List()| so that you \r\n    can easily search for a keyword (e.g. the name of a variable or \r\n    function) and the like.\r\n    \r\n    If you press enter, the selected line will be copied to the command \r\n    line. Press ESC to cancel browsing.\r\n    \r\n    EXAMPLES:\r\n      TBrowseOutput 20verb TeaseTheCulprit\r\n      TBrowseOutput let\r\n      TBrowseOutput map\r\n\r\n\r\nRelated (small) plugins that utilize tlib and thus provide some degree of uniform user experience:\r\n    tbibtools (vimscript #1915): bibtex-related utilities (sort, reformat, list contents ...)\r\n    tmarks (vimscript #2594): Browse, place, & delete marks\r\n    tmboxbrowser (vimscript #1906): A mbox browser -- Read your e-mails with vim\r\n    tmru (vimscript #1864): Most Recently Used Files\r\n    trag (vimscript #2033): A slightly language-aware alternative to grep\r\n    tregisters (vimscript #2017): List, edit, and run\/execute registers\/clipboards\r\n    tselectbuffer (vimscript #1866): A quick buffer selector\/switcher\r\n    tselectfiles (vimscript #1865): A quick file selector\/browser\/explorer (sort of)\r\n    ttagecho (vimscript #2055): Show current tag information\r\n    ttagcomplete (vimscript #2069): Context-sensitive tags-based completion and code skeletons\r\n    ttags (vimscript #2018): Tag list browser (List, filter, preview, jump to tags)\r\n    ttoc (vimscript #2014): A regexp-based table of contents of the current buffer\r\n    vikitasks (vimscript #2894): Search viki files for tasks and display them in a list\r\n\r\n\r\nFor full details, please see: \r\nhttp:\/\/github.com\/tomtom\/tlib_vim\/blob\/master\/doc\/tlib.txt\r\n\r\nAlso available via git\r\nhttp:\/\/github.com\/tomtom\/tlib_vim","install_details":"When installing tlib for the first time, it might be necessary that you create the directory ~\/.vim\/autoload\/tlib before sourcing the vimball. If you have difficulties to install this plugin, please make sure to use the current version of vimball (vimscript #1502). The vimball that comes with vim 7.0 is most likely not recent enough.\r\n\r\nOpen the file and type\r\n\r\n    :so %\r\n\r\nsee :help vimball for details.","5":"When installing tlib for the first time, it might be necessary that you create the directory ~\/.vim\/autoload\/tlib before sourcing the vimball. If you have difficulties to install this plugin, please make sure to use the current version of vimball (vimscript #1502). The vimball that comes with vim 7.0 is most likely not recent enough.\r\n\r\nOpen the file and type\r\n\r\n    :so %\r\n\r\nsee :help vimball for details.","first_name":"Tom","6":"Tom","last_name":"Link","7":"Link","releases":[{"0":"1863","vim_version":"7.0","1":"7.0","script_version":"1.2.8","2":"1.2.8","version_comment":"https:\/\/github.com\/tomtom\/tlib_vim\/commits\/master","3":"https:\/\/github.com\/tomtom\/tlib_vim\/commits\/master","package":"tlib.zip","4":"tlib.zip","src_id":"28101","5":"28101","creation_date":"1658446068","6":"1658446068"},{"0":"1863","vim_version":"7.0","1":"7.0","script_version":"1.23","2":"1.23","version_comment":"- bump version 1.23 + misc changes\n- FIX #24: avoid vim8 features\n- tlib#win#GetID(): Alternative implementation sets a window variable to identify the window\n- tlib#arg#GetOpts(): If args is a dict, return it\n- tlib#file#FilterFiles(): FIX typo\n- tlib#trace#Set: Experimental support for log levels\n- tlib#input#ListW: make sure to close scratch when <= 1 items are in the list\n- FIX #25: set win_nr again; fix some lint warnings\n- tlib#progressbar#Init(): returns a statusline definition that can be used for restor\nMD5 checksum: c4d6e018cbbd3b286a9b1648b748c1f3","3":"- bump version 1.23 + misc changes\n- FIX #24: avoid vim8 features\n- tlib#win#GetID(): Alternative implementation sets a window variable to identify the window\n- tlib#arg#GetOpts(): If args is a dict, return it\n- tlib#file#FilterFiles(): FIX typo\n- tlib#trace#Set: Experimental support for log levels\n- tlib#input#ListW: make sure to close scratch when <= 1 items are in the list\n- FIX #25: set win_nr again; fix some lint warnings\n- tlib#progressbar#Init(): returns a statusline definition that can be used for restor\nMD5 checksum: c4d6e018cbbd3b286a9b1648b748c1f3","package":"tlib.zip","4":"tlib.zip","src_id":"26467","5":"26467","creation_date":"1556396655","6":"1556396655"},{"0":"1863","vim_version":"7.0","1":"7.0","script_version":"1.23","2":"1.23","version_comment":"- bump version 1.23 + misc changes\n- FIX #24: avoid vim8 features\n- tlib#win#GetID(): Alternative implementation sets a window variable to identify the window\n- tlib#arg#GetOpts(): If args is a dict, return it\n- tlib#file#FilterFiles(): FIX typo\n- tlib#trace#Set: Experimental support for log levels\n- tlib#input#ListW: make sure to close scratch when <= 1 items are in the list\n- FIX #25: set win_nr again; fix some lint warnings\n- tlib#progressbar#Init(): returns a statusline definition that can be used for restor\nMD5 checksum: c4d6e018cbbd3b286a9b1648b748c1f3","3":"- bump version 1.23 + misc changes\n- FIX #24: avoid vim8 features\n- tlib#win#GetID(): Alternative implementation sets a window variable to identify the window\n- tlib#arg#GetOpts(): If args is a dict, return it\n- tlib#file#FilterFiles(): FIX typo\n- tlib#trace#Set: Experimental support for log levels\n- tlib#input#ListW: make sure to close scratch when <= 1 items are in the list\n- FIX #25: set win_nr again; fix some lint warnings\n- tlib#progressbar#Init(): returns a statusline definition that can be used for restor\nMD5 checksum: c4d6e018cbbd3b286a9b1648b748c1f3","package":"tlib.zip","4":"tlib.zip","src_id":"25035","5":"25035","creation_date":"1489692777","6":"1489692777"},{"0":"1863","vim_version":"7.0","1":"7.0","script_version":"1.22","2":"1.22","version_comment":"- tlib#date#Shift(): Support for business days 'Nb'\n- tlib#list#Uniq: Properly handle empty strings\n- tlib#trace: Use g:tlib#trace#printer and tlib#trace#Printer_{printer}\n- tlib#dictionary#Rev: Optional argument `opts = {}`; properly handle empty values etc.\n- NEW g:tlib#trace#hl\n- NEW spec\/dictionary.vim\n- tlib#agent#CompleteAgentNames: case insensitive\n- tlib#arg#CComplete: --[no-]debug option\n- tlib#date#Format: use localtime() if no arg is provided\n- NEW tlib#file#IsAbsolute\n- NEW tlib#notify#PrintError()\n- tlib#trace#Print: FIX s\/exec\/call\/\n- tlib#type#Is() match full type name\n- NEW tlib#string#MatchAll()\n- Tlibtraceset, tlib#trace#Set(): If no `+` or `-` is prepended, assume `+`.\n- tlib#list#Input: fix highlighting for filenames\n- tlib#input#ListW: use world.CloseScratch(1)\n- tlib#agent#ViewFile: Ignore errors in :exec back\n- NEW tlib#agent#EditFileInWindow()\n- :Tlibtraceset uses tlib#arg#GetOpts(), i.e. you can set the log file more easily\nMD5 checksum: 20a48e225f32b9f58808096a5377af04","3":"- tlib#date#Shift(): Support for business days 'Nb'\n- tlib#list#Uniq: Properly handle empty strings\n- tlib#trace: Use g:tlib#trace#printer and tlib#trace#Printer_{printer}\n- tlib#dictionary#Rev: Optional argument `opts = {}`; properly handle empty values etc.\n- NEW g:tlib#trace#hl\n- NEW spec\/dictionary.vim\n- tlib#agent#CompleteAgentNames: case insensitive\n- tlib#arg#CComplete: --[no-]debug option\n- tlib#date#Format: use localtime() if no arg is provided\n- NEW tlib#file#IsAbsolute\n- NEW tlib#notify#PrintError()\n- tlib#trace#Print: FIX s\/exec\/call\/\n- tlib#type#Is() match full type name\n- NEW tlib#string#MatchAll()\n- Tlibtraceset, tlib#trace#Set(): If no `+` or `-` is prepended, assume `+`.\n- tlib#list#Input: fix highlighting for filenames\n- tlib#input#ListW: use world.CloseScratch(1)\n- tlib#agent#ViewFile: Ignore errors in :exec back\n- NEW tlib#agent#EditFileInWindow()\n- :Tlibtraceset uses tlib#arg#GetOpts(), i.e. you can set the log file more easily\nMD5 checksum: 20a48e225f32b9f58808096a5377af04","package":"tlib.zip","4":"tlib.zip","src_id":"24967","5":"24967","creation_date":"1487066179","6":"1487066179"},{"0":"1863","vim_version":"7.0","1":"7.0","script_version":"1.20","2":"1.20","version_comment":"- tlib#arg: Completion for comma-separated lists\n- Use \"silent cd\"\n- NEW tlib#type#DefSchema(); FIX tlib#type#Has()\n- tlib#cache#Value(): minor change\n- tlib#date#IsDate() also checks whether the date is valid\n- ! tlib#sys#Open(): escape special chars only once\n- tlib#trace#Print: Allow for strings\n- :Tlibtrace, :Tlibtraceset, :Tlibassert remove `-bar`\n- NEW :Tlibtype (type\/schema assertions); tlib#type#Is() also accepts schemas as \"types\"\n- tlib#dir#CD(): Use haslocaldir()\n- tlib#qfl#AgentGotoQFE: Don't use wincmd w\n- NEW tlib#string#Input()\n- FIX g:tlib#sys#system_rx; add OpenOffice exensions to g:tlib#sys#special_suffixes\n- NEW tlib#selection#GetSelection()\n- tlib#date#Shift(): Fix \"Xm\", ++specs\n- tlib#trace#Set: FIX Properly handly \"-label\"\nMD5 checksum: c919e0782931a8c628c6996903f989d3","3":"- tlib#arg: Completion for comma-separated lists\n- Use \"silent cd\"\n- NEW tlib#type#DefSchema(); FIX tlib#type#Has()\n- tlib#cache#Value(): minor change\n- tlib#date#IsDate() also checks whether the date is valid\n- ! tlib#sys#Open(): escape special chars only once\n- tlib#trace#Print: Allow for strings\n- :Tlibtrace, :Tlibtraceset, :Tlibassert remove `-bar`\n- NEW :Tlibtype (type\/schema assertions); tlib#type#Is() also accepts schemas as \"types\"\n- tlib#dir#CD(): Use haslocaldir()\n- tlib#qfl#AgentGotoQFE: Don't use wincmd w\n- NEW tlib#string#Input()\n- FIX g:tlib#sys#system_rx; add OpenOffice exensions to g:tlib#sys#special_suffixes\n- NEW tlib#selection#GetSelection()\n- tlib#date#Shift(): Fix \"Xm\", ++specs\n- tlib#trace#Set: FIX Properly handly \"-label\"\nMD5 checksum: c919e0782931a8c628c6996903f989d3","package":"tlib.vba","4":"tlib.vba","src_id":"23953","5":"23953","creation_date":"1453827860","6":"1453827860"},{"0":"1863","vim_version":"7.0","1":"7.0","script_version":"1.17","2":"1.17","version_comment":"- tlib#input#List: #ReduceFilter: make sure the regexp is valid\n- TTimeCommand -> Ttimecommand\n- tlib#eval#Extend: mode argument for expand() compatibility\n- tlib#input#List: Key handlers can have additional arguments\n- tlib#qfl#AgentWithSelected: Set world\n- prototype.UseInputListScratch: Run tlib_UseInputListScratch hook earlier\n- tlib#qfl#AgentWithSelected: typo\n- tlib#arg#GetOpts: type conversion (comma-separated lists etc.)\n- tlib#arg: validators\n- NEW tlib#date#IsDate()\n- tlib#balloon#Remove: Unset &ballooneval, &balloonexpr\n- NEW tlib#balloon#Expand()\n- NEW tlib#date#Format()\n- FIX tlib#date#Shift(..., \"+Xm\") for months\n- NEW tlib#trace#Backtrace()\n- NEW tlib#type#Is(), tlib#type#Are(), tlib#type#Has(), tlib#type#Have()\n- NEW :Tlibassert\nMD5 checksum: 3c4125a28ff1860accd254846651c251","3":"- tlib#input#List: #ReduceFilter: make sure the regexp is valid\n- TTimeCommand -> Ttimecommand\n- tlib#eval#Extend: mode argument for expand() compatibility\n- tlib#input#List: Key handlers can have additional arguments\n- tlib#qfl#AgentWithSelected: Set world\n- prototype.UseInputListScratch: Run tlib_UseInputListScratch hook earlier\n- tlib#qfl#AgentWithSelected: typo\n- tlib#arg#GetOpts: type conversion (comma-separated lists etc.)\n- tlib#arg: validators\n- NEW tlib#date#IsDate()\n- tlib#balloon#Remove: Unset &ballooneval, &balloonexpr\n- NEW tlib#balloon#Expand()\n- NEW tlib#date#Format()\n- FIX tlib#date#Shift(..., \"+Xm\") for months\n- NEW tlib#trace#Backtrace()\n- NEW tlib#type#Is(), tlib#type#Are(), tlib#type#Has(), tlib#type#Have()\n- NEW :Tlibassert\nMD5 checksum: 3c4125a28ff1860accd254846651c251","package":"tlib.vba","4":"tlib.vba","src_id":"23755","5":"23755","creation_date":"1448349805","6":"1448349805"},{"0":"1863","vim_version":"7.0","1":"7.0","script_version":"1.16","2":"1.16","version_comment":"- tlib#arg#GetOpts: Handle short options\n- tlib#arg: support short flags & facilitate completion\n- NEW :TLibTrace\n- tlib#sys#system_browser: FIX XDG string\n- NEW tlib#sys#SystemInDir() (used by tlib#vcs#Ls)\n- tlib#agent#Complete: improve fltrx\n- Remove tlib#arg#Key(), :TKeyArg\n- Move :TRequire, :TTimeCommand to macros\/tlib.vim\n- NEW tlib#cmd#TBrowseScriptnames()\n- TScratch: use empty('<bang>')\n- NEW :TLibTrace\n- tlib#qfl: FIX TTagedFilesFilename regexp\n- Remove tlib#arg#Key()\n- tlib#buffer#InsertText(): Don't use TKeyArg\n- tlib#eval#Extend: don't assign value\n- NEW :TLibTrace, tlib#trace (was tlib#debug)\n- NEW tlib#string#SplitCommaList()\n- NEW tlib#time#FormatNow()\n- tlib#arg#GetOpts: selectively disable \"long\", \"short\" flags\n- tlib#arg#CComplete(): Support values completion (complete_customlist field)\n- NEW tlib#date#Shift()\n- tlib#qfl#Balloon(): Handle items with no bufnr\n- NEW tlib#file#Glob, tlib#file#Globpath\n- tlib#progressbar#Display(): optional \"always\" argument\n- tlib#vcs#GitLsPostprocess(): Try to handle encoded filenames from git ls-files\n- tlib#vcs#GitLsPostprocess: Eval only \\ddd substrings\n- FIX #22: duplicate tag\n- tlib#buffer: Use 2match instead of 3match (incompatibility with matchparen)\n- FIX #23: duplicate help tag\n- tlib#string#SplitCommaList: optional \"sep\" argument\n- Rename TLibTrace -> Tlibtrace; NEW Tlibtraceset command\n- Rename s:SetSyntax -> tlib#qfl#SetSyntax\n- mv tlib#rx#Convert to incubator\nMD5 checksum: f3656fb35b7b3033084d6c5e504aca61","3":"- tlib#arg#GetOpts: Handle short options\n- tlib#arg: support short flags & facilitate completion\n- NEW :TLibTrace\n- tlib#sys#system_browser: FIX XDG string\n- NEW tlib#sys#SystemInDir() (used by tlib#vcs#Ls)\n- tlib#agent#Complete: improve fltrx\n- Remove tlib#arg#Key(), :TKeyArg\n- Move :TRequire, :TTimeCommand to macros\/tlib.vim\n- NEW tlib#cmd#TBrowseScriptnames()\n- TScratch: use empty('<bang>')\n- NEW :TLibTrace\n- tlib#qfl: FIX TTagedFilesFilename regexp\n- Remove tlib#arg#Key()\n- tlib#buffer#InsertText(): Don't use TKeyArg\n- tlib#eval#Extend: don't assign value\n- NEW :TLibTrace, tlib#trace (was tlib#debug)\n- NEW tlib#string#SplitCommaList()\n- NEW tlib#time#FormatNow()\n- tlib#arg#GetOpts: selectively disable \"long\", \"short\" flags\n- tlib#arg#CComplete(): Support values completion (complete_customlist field)\n- NEW tlib#date#Shift()\n- tlib#qfl#Balloon(): Handle items with no bufnr\n- NEW tlib#file#Glob, tlib#file#Globpath\n- tlib#progressbar#Display(): optional \"always\" argument\n- tlib#vcs#GitLsPostprocess(): Try to handle encoded filenames from git ls-files\n- tlib#vcs#GitLsPostprocess: Eval only \\ddd substrings\n- FIX #22: duplicate tag\n- tlib#buffer: Use 2match instead of 3match (incompatibility with matchparen)\n- FIX #23: duplicate help tag\n- tlib#string#SplitCommaList: optional \"sep\" argument\n- Rename TLibTrace -> Tlibtrace; NEW Tlibtraceset command\n- Rename s:SetSyntax -> tlib#qfl#SetSyntax\n- mv tlib#rx#Convert to incubator\nMD5 checksum: f3656fb35b7b3033084d6c5e504aca61","package":"tlib.vba","4":"tlib.vba","src_id":"23722","5":"23722","creation_date":"1447087410","6":"1447087410"},{"0":"1863","vim_version":"7.0","1":"7.0","script_version":"1.15","2":"1.15","version_comment":"- tlib#file#Join(): New optional argument: maybe_absolute Drop preceding parts if a part looks like an absolute filename\n- tlib#sys#Open(), tlib#sys#IsSpecial() (moved from viki)\n- tlib#list#Uniq(): Handle hetergenous lists\n- FIX #21: duplicate help tag\n- NEW tlib#dictionary#Rev()\n- tlib#input#List(): Use <Tab> to complete current word\n- NEW tlib#arg#GetOpts(); ENH tlib#arg#StringAsKeyArgsEqual()\n- cache: Allow for in memory cache\n- NEW tlib#eval#Extend()\n- Move qfl\/loclist browser from trag to tlib\n- FIX tlib#eval#Extend()\n- Simplify tlib#eval#Extend()\n- World.index_next_syntax may be a dict\n- tlib#qfl#QflList: Use copy()\n- tlib#arg#GetOpts: Handle exit code\nMD5 checksum: 13fd8b0e4ba9cd932c57fc40ac3f641f","3":"- tlib#file#Join(): New optional argument: maybe_absolute Drop preceding parts if a part looks like an absolute filename\n- tlib#sys#Open(), tlib#sys#IsSpecial() (moved from viki)\n- tlib#list#Uniq(): Handle hetergenous lists\n- FIX #21: duplicate help tag\n- NEW tlib#dictionary#Rev()\n- tlib#input#List(): Use <Tab> to complete current word\n- NEW tlib#arg#GetOpts(); ENH tlib#arg#StringAsKeyArgsEqual()\n- cache: Allow for in memory cache\n- NEW tlib#eval#Extend()\n- Move qfl\/loclist browser from trag to tlib\n- FIX tlib#eval#Extend()\n- Simplify tlib#eval#Extend()\n- World.index_next_syntax may be a dict\n- tlib#qfl#QflList: Use copy()\n- tlib#arg#GetOpts: Handle exit code\nMD5 checksum: 13fd8b0e4ba9cd932c57fc40ac3f641f","package":"tlib.vba","4":"tlib.vba","src_id":"23687","5":"23687","creation_date":"1445883752","6":"1445883752"},{"0":"1863","vim_version":"7.0","1":"7.0","script_version":"1.14","2":"1.14","version_comment":"- FIX #18: Make sure the scratch isn't readonly\n- FIX: display filter (properly handle backslashes)\n- Remove loaded_* guard from autoload files\n- tlib#notify#Echo(): minor changes\n- tlib#file#Edit() (used by tlib#agent#ViewFile)\n- tlib#buffer#GetList(): Buffer numbers are converted to numbers\n- tlib#sys: Change order of functions (move tlib#sys#IsCygwinBin to the (possibly FIX #19)\n- g:tlib#sys#check_cygpath: Call tlib#sys#IsExecutable('cygpath', 1)  (possibly FIX #19)\nMD5 checksum: 2cf6386218736a2d09db43c8e751e5a4","3":"- FIX #18: Make sure the scratch isn't readonly\n- FIX: display filter (properly handle backslashes)\n- Remove loaded_* guard from autoload files\n- tlib#notify#Echo(): minor changes\n- tlib#file#Edit() (used by tlib#agent#ViewFile)\n- tlib#buffer#GetList(): Buffer numbers are converted to numbers\n- tlib#sys: Change order of functions (move tlib#sys#IsCygwinBin to the (possibly FIX #19)\n- g:tlib#sys#check_cygpath: Call tlib#sys#IsExecutable('cygpath', 1)  (possibly FIX #19)\nMD5 checksum: 2cf6386218736a2d09db43c8e751e5a4","package":"tlib.vba","4":"tlib.vba","src_id":"23637","5":"23637","creation_date":"1443787639","6":"1443787639"},{"0":"1863","vim_version":"7.0","1":"7.0","script_version":"1.13","2":"1.13","version_comment":"- SetInitialFilter(): Use deepcopy()\n- tlib#var#List(): use keys(namespace) for newer versions of vim\n- g:tlib#input#user_shortcuts (not functional yet)\n- tlib#input#List: state \"picked\"\n- UseInputListScratch(): Allow customization via self.index_next_syntax\n- tlib#cmd#Capture()\n- Facilitate customization of key agents via g:tlib_extend_keyagents_InputList_s, g:tlib_extend_keyagents_InputList_m\nMD5 checksum: 7dd8b17a1a5b555df979381dcbd4c9aa","3":"- SetInitialFilter(): Use deepcopy()\n- tlib#var#List(): use keys(namespace) for newer versions of vim\n- g:tlib#input#user_shortcuts (not functional yet)\n- tlib#input#List: state \"picked\"\n- UseInputListScratch(): Allow customization via self.index_next_syntax\n- tlib#cmd#Capture()\n- Facilitate customization of key agents via g:tlib_extend_keyagents_InputList_s, g:tlib_extend_keyagents_InputList_m\nMD5 checksum: 7dd8b17a1a5b555df979381dcbd4c9aa","package":"tlib.vba","4":"tlib.vba","src_id":"22592","5":"22592","creation_date":"1414921561","6":"1414921561"},{"0":"1863","vim_version":"7.0","1":"7.0","script_version":"1.12","2":"1.12","version_comment":"- tlib#list#ToDictionary()\n- tlib#dir#CanonicName(): Use tlib#file#Canonic()\n- tlib#file#Canonic()\nMD5 checksum: 7995ab58f31eb6673d20deab8761838e","3":"- tlib#list#ToDictionary()\n- tlib#dir#CanonicName(): Use tlib#file#Canonic()\n- tlib#file#Canonic()\nMD5 checksum: 7995ab58f31eb6673d20deab8761838e","package":"tlib.vba","4":"tlib.vba","src_id":"22159","5":"22159","creation_date":"1404756422","6":"1404756422"},{"0":"1863","vim_version":"7.0","1":"7.0","script_version":"1.11","2":"1.11","version_comment":"- tlib#vcs#FindVCS(filename): Wrong parameters to fnamemodifiy if filename is a directory\n- Some system-related functions (e.g. facilitate use of cygwin tools)\n- tlib#arg#StringAsKeyArgsEqual(), tlib#arg#StringAsKeyArgs(): Support \"key=val\" type argument lists\n- tlib#vcs#Executable()\n- scripts\/create_crc_table.rb\n- tlib#var#Get(): For namespaces other than global, replace \"#\" with \"_\"\nMD5 checksum: 4a33f2f23e1fc6600b32e7f8323e001e","3":"- tlib#vcs#FindVCS(filename): Wrong parameters to fnamemodifiy if filename is a directory\n- Some system-related functions (e.g. facilitate use of cygwin tools)\n- tlib#arg#StringAsKeyArgsEqual(), tlib#arg#StringAsKeyArgs(): Support \"key=val\" type argument lists\n- tlib#vcs#Executable()\n- scripts\/create_crc_table.rb\n- tlib#var#Get(): For namespaces other than global, replace \"#\" with \"_\"\nMD5 checksum: 4a33f2f23e1fc6600b32e7f8323e001e","package":"tlib.vba","4":"tlib.vba","src_id":"22135","5":"22135","creation_date":"1404566955","6":"1404566955"},{"0":"1863","vim_version":"7.0","1":"7.0","script_version":"1.10","2":"1.10","version_comment":"- tlib#string#Chomp: Optional argument: max number of chars that should be removed\nMD5 checksum: 8c1b94e25045580874e2f892d509291b","3":"- tlib#string#Chomp: Optional argument: max number of chars that should be removed\nMD5 checksum: 8c1b94e25045580874e2f892d509291b","package":"tlib.vba","4":"tlib.vba","src_id":"22100","5":"22100","creation_date":"1403894427","6":"1403894427"},{"0":"1863","vim_version":"7.0","1":"7.0","script_version":"1.09","2":"1.09","version_comment":"- tlib#cache#Filename(): Use sha256() for VIM >= 7.4\n- tlib#cache#Value(): Undo previous hack\n- tlib#list#Uniq(): option to remove empty values\n- tlib#cache#MTime(); tlib#persistent#Save() calls tlib#cache#Save()\n- tlib#input#ListW: Temporarily set noshowmode\n- tlib#list#Uniq(): Fix handling of empty items\n- lis picker: Remove <C-Space> from help\n- tlib#list#Uniq(): Implementation based on syntastic#util#unique(list) by scrooloose\nMD5 checksum: b5fb4107d63930c2c8b1f0f6b3a7ff07","3":"- tlib#cache#Filename(): Use sha256() for VIM >= 7.4\n- tlib#cache#Value(): Undo previous hack\n- tlib#list#Uniq(): option to remove empty values\n- tlib#cache#MTime(); tlib#persistent#Save() calls tlib#cache#Save()\n- tlib#input#ListW: Temporarily set noshowmode\n- tlib#list#Uniq(): Fix handling of empty items\n- lis picker: Remove <C-Space> from help\n- tlib#list#Uniq(): Implementation based on syntastic#util#unique(list) by scrooloose\nMD5 checksum: b5fb4107d63930c2c8b1f0f6b3a7ff07","package":"tlib.vba","4":"tlib.vba","src_id":"21707","5":"21707","creation_date":"1396378022","6":"1396378022"},{"0":"1863","vim_version":"7.0","1":"7.0","script_version":"1.08","2":"1.08","version_comment":"- list#input: Improved support for file indicators (closes #17)\n- tlib#char#Get(): Optionally, also return mod\n- tlib#input#ListW: Use #DisplayFormat(world.list)\n- Renamed cnfx filter to glob & minor filter-related enhancements\n- list#input: Make help available as command; help cannot be called via ?\n- list#input: Improved help message\n- list#input: Support Home & End keys\n- list#input: Added glob filter\n- tlib#agent#ShowInfo: Show full filename\n- tlib#cmd#BrowseOutputWithCallback: Support calling callback with multiple results\n- tlib#cmd#ParseScriptname: Properly parse results from :scriptnames\n- tlib#tab#Set()\n- Prepare for proper handling of scratch_split == -1\n- tlib#vim#CopyFunction()\n- tlib#cache#Value(): If generator is empty, use the optional argument as start value\n- tlib#persistent#Get() refers to tlib#cache#Get()\nMD5 checksum: 459ec620168d1ae9b18c69eb3f991832","3":"- list#input: Improved support for file indicators (closes #17)\n- tlib#char#Get(): Optionally, also return mod\n- tlib#input#ListW: Use #DisplayFormat(world.list)\n- Renamed cnfx filter to glob & minor filter-related enhancements\n- list#input: Make help available as command; help cannot be called via ?\n- list#input: Improved help message\n- list#input: Support Home & End keys\n- list#input: Added glob filter\n- tlib#agent#ShowInfo: Show full filename\n- tlib#cmd#BrowseOutputWithCallback: Support calling callback with multiple results\n- tlib#cmd#ParseScriptname: Properly parse results from :scriptnames\n- tlib#tab#Set()\n- Prepare for proper handling of scratch_split == -1\n- tlib#vim#CopyFunction()\n- tlib#cache#Value(): If generator is empty, use the optional argument as start value\n- tlib#persistent#Get() refers to tlib#cache#Get()\nMD5 checksum: 459ec620168d1ae9b18c69eb3f991832","package":"tlib.vba","4":"tlib.vba","src_id":"21527","5":"21527","creation_date":"1393264421","6":"1393264421"},{"0":"1863","vim_version":"7.0","1":"7.0","script_version":"1.07","2":"1.07","version_comment":"- Help template\n- prototype.Highlight_filename(): Use matchstr() instead of fnamemodify()\n- Display buffer-related filename indicators only if g:tlib_inputlist_filename_indicators is true\n- tlib#file#Join(): strip_slashes defaults to 1\nMD5 checksum: 6c8fa96fd3747be05df848ee93dd789b","3":"- Help template\n- prototype.Highlight_filename(): Use matchstr() instead of fnamemodify()\n- Display buffer-related filename indicators only if g:tlib_inputlist_filename_indicators is true\n- tlib#file#Join(): strip_slashes defaults to 1\nMD5 checksum: 6c8fa96fd3747be05df848ee93dd789b","package":"tlib.vba","4":"tlib.vba","src_id":"21331","5":"21331","creation_date":"1389946843","6":"1389946843"},{"0":"1863","vim_version":"7.0","1":"7.0","script_version":"1.06","2":"1.06","version_comment":"- Rename g:tlib_debug to g:tlib#debug\n- Renamed g:tlib_sortprefs_threshold to g:tlib#input#sortprefs_threshold\n- Renamed g:tlib#input#livesearch_threshold\n- Renamed g:tlib_inputlist_match to g:tlib#input#filter_mode\n- Renamed g:tlib_inputlist_higroup to g:tlib#input#higroup\n- Renamed g:tlib#debug\n- Moved g:tlib_pick_last_item\n- Renamed g:tlib#input#and, g:tlib#input#or, g:tlib#input#not\n- Moved g:tlib_numeric_chars to autoload\/tlib\/input.vim\n- Renamed g:tlib#input#keyagents_InputList_s, g:tlib#input#keyagents_InputList_m, g:tlib#input#handlers_EditList\n- Moved g:tlib_inputlist_pct, g:tlib_inputlist_width_filename, g:tlib_inputlist_filename_indicators, g:tlib_inputlist_shortmessage to autoload\/tlib\/World.vim\n- Renamed tlib#input#pick_last_item (2)\n- prototype.SelectItemsByNames()\n- filtered_items: Restricted view\n- prototype.PrintLines()\n- Restricted view (2)\n- Moved g:tlib_scroll_lines to autoload\/tlib\/agent.vim\n- prototype.PrintLines() (2)\n- tlib#input: Improved handling of popup menu (allows submenu)\n- tlib#input: Allow mods in keys\n- Moved g:tlib_scratch_pos to autoload\/tlib\/scratch.vim\n- Moved g:tlib_tags_extra, g:tlib_tag_substitute to autoload\/tlib\/tag.vim\n- tlib#agent#CompleteAgentNames(): Respect Arglead\n- Move g:tlib_viewline_position to autoload\/tlib\/buffer.vim\n- Move g:tlib_cache to autoload\/tlib\/cache.vim\n- Renamed g:tlib_filename_sep to g:tlib#dir#sep\n- prototype.UseScratch(): Set b:tlib_world\n- tlib#input: f9 toggles resticted view\n- tlib#input: next_agent, next_eval\n- tlib#input: Revised use of the popup menu\n- tlib#input: Disable popup menu for gui_gtk\n- tlib#input: Re-enabled the popup menu for gtk gui\n- tlib#input: FIX popup menu on Windows\n- Renamed g:tlib_numeric_chars to g:tlib#input#numeric_chars (disabled per-buffer values) (fixes #35)\n- Improve scratch list\n- New: tlib#grep\n- Merge branch 'master' of https:\/\/github.com\/bruno-\/tlib_vim into pull16\n- g:tlib_scratch_hidden: Configure how to \"hide\" the scratch buffer\n- tlib#grep#Do: don't escape \"*\" in patterns\n- Optimize use of visible scratch buffers\n- World.scratch_hidden parameter\n- scratch: Always use keepalt & keepjumps\nMD5 checksum: 2e40449c47dc606ccef57aa0b1e22e8e","3":"- Rename g:tlib_debug to g:tlib#debug\n- Renamed g:tlib_sortprefs_threshold to g:tlib#input#sortprefs_threshold\n- Renamed g:tlib#input#livesearch_threshold\n- Renamed g:tlib_inputlist_match to g:tlib#input#filter_mode\n- Renamed g:tlib_inputlist_higroup to g:tlib#input#higroup\n- Renamed g:tlib#debug\n- Moved g:tlib_pick_last_item\n- Renamed g:tlib#input#and, g:tlib#input#or, g:tlib#input#not\n- Moved g:tlib_numeric_chars to autoload\/tlib\/input.vim\n- Renamed g:tlib#input#keyagents_InputList_s, g:tlib#input#keyagents_InputList_m, g:tlib#input#handlers_EditList\n- Moved g:tlib_inputlist_pct, g:tlib_inputlist_width_filename, g:tlib_inputlist_filename_indicators, g:tlib_inputlist_shortmessage to autoload\/tlib\/World.vim\n- Renamed tlib#input#pick_last_item (2)\n- prototype.SelectItemsByNames()\n- filtered_items: Restricted view\n- prototype.PrintLines()\n- Restricted view (2)\n- Moved g:tlib_scroll_lines to autoload\/tlib\/agent.vim\n- prototype.PrintLines() (2)\n- tlib#input: Improved handling of popup menu (allows submenu)\n- tlib#input: Allow mods in keys\n- Moved g:tlib_scratch_pos to autoload\/tlib\/scratch.vim\n- Moved g:tlib_tags_extra, g:tlib_tag_substitute to autoload\/tlib\/tag.vim\n- tlib#agent#CompleteAgentNames(): Respect Arglead\n- Move g:tlib_viewline_position to autoload\/tlib\/buffer.vim\n- Move g:tlib_cache to autoload\/tlib\/cache.vim\n- Renamed g:tlib_filename_sep to g:tlib#dir#sep\n- prototype.UseScratch(): Set b:tlib_world\n- tlib#input: f9 toggles resticted view\n- tlib#input: next_agent, next_eval\n- tlib#input: Revised use of the popup menu\n- tlib#input: Disable popup menu for gui_gtk\n- tlib#input: Re-enabled the popup menu for gtk gui\n- tlib#input: FIX popup menu on Windows\n- Renamed g:tlib_numeric_chars to g:tlib#input#numeric_chars (disabled per-buffer values) (fixes #35)\n- Improve scratch list\n- New: tlib#grep\n- Merge branch 'master' of https:\/\/github.com\/bruno-\/tlib_vim into pull16\n- g:tlib_scratch_hidden: Configure how to \"hide\" the scratch buffer\n- tlib#grep#Do: don't escape \"*\" in patterns\n- Optimize use of visible scratch buffers\n- World.scratch_hidden parameter\n- scratch: Always use keepalt & keepjumps\nMD5 checksum: 2e40449c47dc606ccef57aa0b1e22e8e","package":"tlib.vba","4":"tlib.vba","src_id":"20931","5":"20931","creation_date":"1382117772","6":"1382117772"},{"0":"1863","vim_version":"7.0","1":"7.0","script_version":"1.05","2":"1.05","version_comment":"- tlib#hash: Adler32 & CRC32 (using zlib via ruby) algorithms\n- tlib#cache#Filename(): If the cache filename is too long, add the Adler32 checksum to the shortened path\n- tlib#cache#Filename(): Use tlib#hash#Adler32() only if the or() function exists\n- tlib#hash#Adler32(): Raise error, if or() doesn't exist\n- tlib#hash#CRC32(): Alternative implementation of crc32 (doesn't work yet, thus currently disabled)\n- tlib#bitwise: Bitwise operations for older versions of vim\n- tlib#number: Base conversion\n- tlib#input#ListW(): Handle mouse clicks more correctly\n- tlib#bitwise#Num2Bits(): Supports returning floats\n- tlib#hash#CRC32(): Alternative implementation of crc32 (doesn't work yet)\n- tlib#hash#CRC32(): Re-enable ruby version\n- tlib#hash#CRC32B(): Implementation of CRC32B checksum in vimscript (used only if +ruby isn't available)\n- tlib#hash#CRC32B(): vim version: cache the crc table\n- tlib#cache#Filename(): Use tlib#hash#CRC32B(file) instead of not Adler32 for filenames too long\n- tlib#hash#CRC32B(): ruby version: return upper case hex value\n- g:tlib#hash#use_crc32: define which crc32b version should be used\n- Moved spec files from vimtlib to tlib_vim\n- tlib#bitwise#Add() and tlib#bitwise#Sub()\n- tlib#file#Relative(): Wrong results for filenames that don't exist\n- Implementation of hash#Adler32 for earlier vim versions; g:tlib#hash#use_adler32\n- tlib#cache#Filename(): Use adler32 again\n- addon-info\n- tlib#file#Absolute(): remove redundant \".\" parts in full filename\n- win32: Fix moving window when using :vertical for tlib#inpu#List()\n- tlib#cache#Filename(): Don't create wrong directory if the cache filename is too long\n- tlib#file#Join(): if strip_slashes, also strip redundant (back)slashes\n- tlib#input#ListW(): Always set post_keys variable\n- tlib#file#With(): escape backslashes\n- tlib#cmd#OutputAsList(): Support for nesting\n- tlib#dir#NativeName(dirname)\nMD5 checksum: 493f9beca44374de386f20d1613155e3","3":"- tlib#hash: Adler32 & CRC32 (using zlib via ruby) algorithms\n- tlib#cache#Filename(): If the cache filename is too long, add the Adler32 checksum to the shortened path\n- tlib#cache#Filename(): Use tlib#hash#Adler32() only if the or() function exists\n- tlib#hash#Adler32(): Raise error, if or() doesn't exist\n- tlib#hash#CRC32(): Alternative implementation of crc32 (doesn't work yet, thus currently disabled)\n- tlib#bitwise: Bitwise operations for older versions of vim\n- tlib#number: Base conversion\n- tlib#input#ListW(): Handle mouse clicks more correctly\n- tlib#bitwise#Num2Bits(): Supports returning floats\n- tlib#hash#CRC32(): Alternative implementation of crc32 (doesn't work yet)\n- tlib#hash#CRC32(): Re-enable ruby version\n- tlib#hash#CRC32B(): Implementation of CRC32B checksum in vimscript (used only if +ruby isn't available)\n- tlib#hash#CRC32B(): vim version: cache the crc table\n- tlib#cache#Filename(): Use tlib#hash#CRC32B(file) instead of not Adler32 for filenames too long\n- tlib#hash#CRC32B(): ruby version: return upper case hex value\n- g:tlib#hash#use_crc32: define which crc32b version should be used\n- Moved spec files from vimtlib to tlib_vim\n- tlib#bitwise#Add() and tlib#bitwise#Sub()\n- tlib#file#Relative(): Wrong results for filenames that don't exist\n- Implementation of hash#Adler32 for earlier vim versions; g:tlib#hash#use_adler32\n- tlib#cache#Filename(): Use adler32 again\n- addon-info\n- tlib#file#Absolute(): remove redundant \".\" parts in full filename\n- win32: Fix moving window when using :vertical for tlib#inpu#List()\n- tlib#cache#Filename(): Don't create wrong directory if the cache filename is too long\n- tlib#file#Join(): if strip_slashes, also strip redundant (back)slashes\n- tlib#input#ListW(): Always set post_keys variable\n- tlib#file#With(): escape backslashes\n- tlib#cmd#OutputAsList(): Support for nesting\n- tlib#dir#NativeName(dirname)\nMD5 checksum: 493f9beca44374de386f20d1613155e3","package":"tlib.vba","4":"tlib.vba","src_id":"20693","5":"20693","creation_date":"1377022330","6":"1377022330"},{"0":"1863","vim_version":"7.0","1":"7.0","script_version":"1.04","2":"1.04","version_comment":"- tlib#cache#Value(cfile, generator, ftime, ...): cache value & check timestamp\n- Replaced g:tlib#cache#silent with g:tlib#cache#verbosity\n- FormatFilenames: improved handling of utf8 characters\n- tlib#persistent#Value()\n- tlib#input#List: Allow filename indiactors defined by the caller\n- Custom filename_indicators are displayed after (and clearly separted from) the standard indicators\n- Check the return value of an unknown_key agent\n- Format filename = \"l\": Allow \"..\" as start of a directory name\n- Format filename = \"l\": If the filename is just a filename's tail, display it on both sides\n- Set g:tlib_filename_sep to \"\\\" on Windows (again)\n- g:tlib#cache#max_filename: If the cache filename is longer than N characters, use |pathshorten()|.\nMD5 checksum: b64ce6764f39f40bfc95f3916bbb0057","3":"- tlib#cache#Value(cfile, generator, ftime, ...): cache value & check timestamp\n- Replaced g:tlib#cache#silent with g:tlib#cache#verbosity\n- FormatFilenames: improved handling of utf8 characters\n- tlib#persistent#Value()\n- tlib#input#List: Allow filename indiactors defined by the caller\n- Custom filename_indicators are displayed after (and clearly separted from) the standard indicators\n- Check the return value of an unknown_key agent\n- Format filename = \"l\": Allow \"..\" as start of a directory name\n- Format filename = \"l\": If the filename is just a filename's tail, display it on both sides\n- Set g:tlib_filename_sep to \"\\\" on Windows (again)\n- g:tlib#cache#max_filename: If the cache filename is longer than N characters, use |pathshorten()|.\nMD5 checksum: b64ce6764f39f40bfc95f3916bbb0057","package":"tlib.vba","4":"tlib.vba","src_id":"19179","5":"19179","creation_date":"1355421973","6":"1355421973"},{"0":"1863","vim_version":"7.0","1":"7.0","script_version":"1.02","2":"1.02","version_comment":"- #UseInputListScratch(): Make sure the TLib autogroup was created (fixes #14)\nMD5 checksum: 5a6da7fc99c7fc7584e8fc2f7bf86fe4","3":"- #UseInputListScratch(): Make sure the TLib autogroup was created (fixes #14)\nMD5 checksum: 5a6da7fc99c7fc7584e8fc2f7bf86fe4","package":"tlib.vba","4":"tlib.vba","src_id":"18844","5":"18844","creation_date":"1350725058","6":"1350725058"},{"0":"1863","vim_version":"7.0","1":"7.0","script_version":"1.01","2":"1.01","version_comment":"- Set g:tlib_inputlist_and to  ' ' again\n- g:tlib#input#filename_max_width: maximum display width of filenames\n- tlib#input#List: <s-esc>, <f10>: run command by name\nMD5 checksum: a42f90275cdbe9f7d92cac61b884a2d1","3":"- Set g:tlib_inputlist_and to  ' ' again\n- g:tlib#input#filename_max_width: maximum display width of filenames\n- tlib#input#List: <s-esc>, <f10>: run command by name\nMD5 checksum: a42f90275cdbe9f7d92cac61b884a2d1","package":"tlib.vba","4":"tlib.vba","src_id":"18744","5":"18744","creation_date":"1349285236","6":"1349285236"},{"0":"1863","vim_version":"7.0","1":"7.0","script_version":"1.00","2":"1.00","version_comment":"- tlib#input#List: optimizations\n- Prepare for multi-mode maps\n- tlib#input#List: cnfx is new default filter\n- Filters: minor changes to how the pattern is displayed\n- g:tlib#input#format_filename: alternative method for formatting filenames\n- tlib#input#List: allow multiple keymaps \/ modes\n- Handle rezise events\n- Don't initialize the same window twice\n- Minor optimizations to how help is displayed\n- Handle VimResize event per buffer\n- Improve display of filenames & highlighting\n- Filename highlighter: set Highlight_filename()\n- RunStateHandlers(): set world variable\n- Optimize help display\nMD5 checksum: e3652927722bdc51935eb1a04238546b","3":"- tlib#input#List: optimizations\n- Prepare for multi-mode maps\n- tlib#input#List: cnfx is new default filter\n- Filters: minor changes to how the pattern is displayed\n- g:tlib#input#format_filename: alternative method for formatting filenames\n- tlib#input#List: allow multiple keymaps \/ modes\n- Handle rezise events\n- Don't initialize the same window twice\n- Minor optimizations to how help is displayed\n- Handle VimResize event per buffer\n- Improve display of filenames & highlighting\n- Filename highlighter: set Highlight_filename()\n- RunStateHandlers(): set world variable\n- Optimize help display\nMD5 checksum: e3652927722bdc51935eb1a04238546b","package":"tlib.vba","4":"tlib.vba","src_id":"18704","5":"18704","creation_date":"1348830550","6":"1348830550"},{"0":"1863","vim_version":"7.0","1":"7.0","script_version":"0.46","2":"0.46","version_comment":"- Support for tinykeymap (move paragraph)\n- Moved para_move to autoload\/tinykeymap\/map\n- tlib#vcs: some \"diff\" commands were defined as \"ls\"; updated hg def; %s is optional\nMD5 checksum: f2f2fe0893e75bb9423c1ddcd01f38f6","3":"- Support for tinykeymap (move paragraph)\n- Moved para_move to autoload\/tinykeymap\/map\n- tlib#vcs: some \"diff\" commands were defined as \"ls\"; updated hg def; %s is optional\nMD5 checksum: f2f2fe0893e75bb9423c1ddcd01f38f6","package":"tlib.vba","4":"tlib.vba","src_id":"18628","5":"18628","creation_date":"1347804378","6":"1347804378"},{"0":"1863","vim_version":"7.0","1":"7.0","script_version":"0.45","2":"0.45","version_comment":"- fuzzy mode: prototype.highlight defaults to g:tlib_inputlist_higroup\n- tlib#scratch: Use noautocmd\n- tlib#input#ListW(): Use world.RestoreOrigin() instead of tlib#win#SetLayout(world.winview)\n- tlib#input#ListW(): Revert to tlib#win#SetLayout(world.winview)\n- tlib#cmd#OutputAsList(): Also save output in g:tlib#cmd#last_output\n- tlib#agent#Suspend(): Resume on BufEnter\n- tlib#input#Resume(): Make sure we are in the right buffer\n- tlib#agent#Suspend(): Use only BufEnter event to trigger a Resume\n- tlib#input#ListW(): When redisplaying a list, make sure prefix > 0\n- tlib#vcs: Access vcs (initially only git is supported)\n- tlib#vcs: improved\n- tlib#persistent: Persistent data file names\n- tlib#file#With(): Trigger BufRead autocommands\n- Duplicate help tags (fixes #13)\n- Make sure scrolloff is 0 while viewing the list (fixes https:\/\/github.com\/tomtom\/vikitasks_vim\/issues\/2)\nMD5 checksum: 0af19ebc0e424727a598a988fdc90f4e","3":"- fuzzy mode: prototype.highlight defaults to g:tlib_inputlist_higroup\n- tlib#scratch: Use noautocmd\n- tlib#input#ListW(): Use world.RestoreOrigin() instead of tlib#win#SetLayout(world.winview)\n- tlib#input#ListW(): Revert to tlib#win#SetLayout(world.winview)\n- tlib#cmd#OutputAsList(): Also save output in g:tlib#cmd#last_output\n- tlib#agent#Suspend(): Resume on BufEnter\n- tlib#input#Resume(): Make sure we are in the right buffer\n- tlib#agent#Suspend(): Use only BufEnter event to trigger a Resume\n- tlib#input#ListW(): When redisplaying a list, make sure prefix > 0\n- tlib#vcs: Access vcs (initially only git is supported)\n- tlib#vcs: improved\n- tlib#persistent: Persistent data file names\n- tlib#file#With(): Trigger BufRead autocommands\n- Duplicate help tags (fixes #13)\n- Make sure scrolloff is 0 while viewing the list (fixes https:\/\/github.com\/tomtom\/vikitasks_vim\/issues\/2)\nMD5 checksum: 0af19ebc0e424727a598a988fdc90f4e","package":"tlib.vba","4":"tlib.vba","src_id":"18488","5":"18488","creation_date":"1345872146","6":"1345872146"},{"0":"1863","vim_version":"7.0","1":"7.0","script_version":"0.42","2":"0.42","version_comment":"- g:tlib#cache#silent: don't display messages when purging the cache (fixes #9)\n- Changed message when deleting directories in the cache.\n- g:tlib#input#use_popup: Don't rely on has('menu') but also check for gtk & win gui (fixes #10)\n- debug\n- tlib#input#ListW(): Didn't return a list when type == \"m\"\n- docs (solves #11)\nMD5 checksum: aa8b5a4602235cc1a5bc9ee45d801b81","3":"- g:tlib#cache#silent: don't display messages when purging the cache (fixes #9)\n- Changed message when deleting directories in the cache.\n- g:tlib#input#use_popup: Don't rely on has('menu') but also check for gtk & win gui (fixes #10)\n- debug\n- tlib#input#ListW(): Didn't return a list when type == \"m\"\n- docs (solves #11)\nMD5 checksum: aa8b5a4602235cc1a5bc9ee45d801b81","package":"tlib.vba","4":"tlib.vba","src_id":"17284","5":"17284","creation_date":"1327166696","6":"1327166696"},{"0":"1863","vim_version":"7.0","1":"7.0","script_version":"0.42","2":"0.42","version_comment":"- tlib#input#List: <s-space> inserts a *-like wildcard (represented as \"__\")\n- Check if a cache file cannot be created because a directory of the same name exists (display a message if so)\n- tlib#cache#Filename: Removed check if a directory of the same name exists (due to inconsistent use)\n- Minor improvements related to buffer handling (scratch_split)\n- .gitignore\n- docs (thanks to blueyed)\n- There is no \"edit\" answer possibility.\n- Fix first purge: do nothing if no timestamp file.\n- g:tlib_pick_single_item\n- Removed pick_single_item. Changed the default behavour when a list has only 1 item. See doc for g:tlib_pick_last_item.\n- Updated help for tlib#input#List(); help_extra attribute\n- EXPERIMENTAL: cache_var, restore_from_cache, on_leave properties; #Initialize(), #Leave()\n- added tlib#cmd#BrowseOutputWithCallback function and :TBrowseScriptnames command\n- tlib#cmd#BrowseOutputWithCallback function and :TBrowseScriptnames command documentation\n- s:prototype.Initialize(): unlet self.cache_var after restoring values\n- tlib#input#List: filter-specific help\n- Removed the seq filter (use cnfd or fuzzy instead)\n- tlib#input#List: temp_prompt (for help message)\nMD5 checksum: aa8b5a4602235cc1a5bc9ee45d801b81","3":"- tlib#input#List: <s-space> inserts a *-like wildcard (represented as \"__\")\n- Check if a cache file cannot be created because a directory of the same name exists (display a message if so)\n- tlib#cache#Filename: Removed check if a directory of the same name exists (due to inconsistent use)\n- Minor improvements related to buffer handling (scratch_split)\n- .gitignore\n- docs (thanks to blueyed)\n- There is no \"edit\" answer possibility.\n- Fix first purge: do nothing if no timestamp file.\n- g:tlib_pick_single_item\n- Removed pick_single_item. Changed the default behavour when a list has only 1 item. See doc for g:tlib_pick_last_item.\n- Updated help for tlib#input#List(); help_extra attribute\n- EXPERIMENTAL: cache_var, restore_from_cache, on_leave properties; #Initialize(), #Leave()\n- added tlib#cmd#BrowseOutputWithCallback function and :TBrowseScriptnames command\n- tlib#cmd#BrowseOutputWithCallback function and :TBrowseScriptnames command documentation\n- s:prototype.Initialize(): unlet self.cache_var after restoring values\n- tlib#input#List: filter-specific help\n- Removed the seq filter (use cnfd or fuzzy instead)\n- tlib#input#List: temp_prompt (for help message)\nMD5 checksum: aa8b5a4602235cc1a5bc9ee45d801b81","package":"tlib.vba","4":"tlib.vba","src_id":"15732","5":"15732","creation_date":"1306394018","6":"1306394018"},{"0":"1863","vim_version":"7.0","1":"7.0","script_version":"0.41","2":"0.41","version_comment":"- World.UseScratch(): keepalt\n- Really include balloon.vim\nMD5 checksum: 3fcbc4f7556f5378d39622e62ab8f379","3":"- World.UseScratch(): keepalt\n- Really include balloon.vim\nMD5 checksum: 3fcbc4f7556f5378d39622e62ab8f379","package":"tlib.vba","4":"tlib.vba","src_id":"14245","5":"14245","creation_date":"1289585981","6":"1289585981"},{"0":"1863","vim_version":"7.0","1":"7.0","script_version":"0.40a","2":"0.40a","version_comment":"Forgot to include autoload\/tlib\/balloon.vim (thanks Maciej)","3":"Forgot to include autoload\/tlib\/balloon.vim (thanks Maciej)","package":"tlib.vba","4":"tlib.vba","src_id":"14078","5":"14078","creation_date":"1287507230","6":"1287507230"},{"0":"1863","vim_version":"7.0","1":"7.0","script_version":"0.40","2":"0.40","version_comment":"- tlib#agent#ViewFile: Use split\/sbuffer if nohidden && modified \r\n- tlib#buffer#GetList(): order by \"basename\"\r\n","3":"- tlib#agent#ViewFile: Use split\/sbuffer if nohidden && modified \r\n- tlib#buffer#GetList(): order by \"basename\"\r\n","package":"tlib.vba","4":"tlib.vba","src_id":"13973","5":"13973","creation_date":"1286009805","6":"1286009805"},{"0":"1863","vim_version":"7.0","1":"7.0","script_version":"0.39","2":"0.39","version_comment":"- tlib#World#Resize: set winfix{height|width}\r\n- g:tlib#cache#dont_purge\r\n- tlib#vim#RestoreWindow()\r\n- tlib#ballon#...()\r\n","3":"- tlib#World#Resize: set winfix{height|width}\r\n- g:tlib#cache#dont_purge\r\n- tlib#vim#RestoreWindow()\r\n- tlib#ballon#...()\r\n","package":"tlib.vba","4":"tlib.vba","src_id":"13832","5":"13832","creation_date":"1284493108","6":"1284493108"},{"0":"1863","vim_version":"7.0","1":"7.0","script_version":"0.37","2":"0.37","version_comment":"- g:tlib_inputlist_livesearch_threshold defaults to 1000\r\n- tlib#World: optional scratch_pos field\r\n- tlib#input#List: By default <m-NUMBER> selects by number but NUMBER is interpreted as string\r\n- tlib#date\r\n- TTimeCommand\r\n","3":"- g:tlib_inputlist_livesearch_threshold defaults to 1000\r\n- tlib#World: optional scratch_pos field\r\n- tlib#input#List: By default <m-NUMBER> selects by number but NUMBER is interpreted as string\r\n- tlib#date\r\n- TTimeCommand\r\n","package":"tlib.vba","4":"tlib.vba","src_id":"12751","5":"12751","creation_date":"1270054372","6":"1270054372"},{"0":"1863","vim_version":"7.0","1":"7.0","script_version":"0.36","2":"0.36","version_comment":"- Display a message when the filter is for whatever reason invalid\r\n- Removed tlib#paragraph#Delete()\r\n- New: tlib#paragraph#Define(), tlib#textobjects#StandardParagraph()\r\n","3":"- Display a message when the filter is for whatever reason invalid\r\n- Removed tlib#paragraph#Delete()\r\n- New: tlib#paragraph#Define(), tlib#textobjects#StandardParagraph()\r\n","package":"tlib.vba.gz","4":"tlib.vba.gz","src_id":"12444","5":"12444","creation_date":"1266653743","6":"1266653743"},{"0":"1863","vim_version":"7.0","1":"7.0","script_version":"0.35","2":"0.35","version_comment":"tlib#input#EditList(): return the list if the user presses esc","3":"tlib#input#EditList(): return the list if the user presses esc","package":"tlib.vba.gz","4":"tlib.vba.gz","src_id":"11931","5":"11931","creation_date":"1261423867","6":"1261423867"},{"0":"1863","vim_version":"7.0","1":"7.0","script_version":"0.34","2":"0.34","version_comment":"- tlib#buffer#HighlightLine(line): call tlib#autocmdgroup#Init()  (reported by Sergey Khorev)","3":"- tlib#buffer#HighlightLine(line): call tlib#autocmdgroup#Init()  (reported by Sergey Khorev)","package":"tlib.vba.gz","4":"tlib.vba.gz","src_id":"11881","5":"11881","creation_date":"1260187845","6":"1260187845"},{"0":"1863","vim_version":"7.0","1":"7.0","script_version":"0.33","2":"0.33","version_comment":"- tlib#agent#Exit: explicitly return empty value (as a consequence, \r\npressing <esc> when browsing an index-list, returns 0 and not \"\")\r\n- tlib#signs\r\n- tlib#input#List: set local statusline\r\n- Don't reset statusline\r\n- Don't use fnamemodify() to split filenames (for performance reasons)\r\n- scratch: Set ft after setting up scratch options\r\n- tlib#map#PumAccept(key)","3":"- tlib#agent#Exit: explicitly return empty value (as a consequence, \r\npressing <esc> when browsing an index-list, returns 0 and not \"\")\r\n- tlib#signs\r\n- tlib#input#List: set local statusline\r\n- Don't reset statusline\r\n- Don't use fnamemodify() to split filenames (for performance reasons)\r\n- scratch: Set ft after setting up scratch options\r\n- tlib#map#PumAccept(key)","package":"tlib.vba.gz","4":"tlib.vba.gz","src_id":"11509","5":"11509","creation_date":"1255242800","6":"1255242800"},{"0":"1863","vim_version":"7.0","1":"7.0","script_version":"0.31","2":"0.31","version_comment":"- :TRequire\r\n-tlib#input#List: For i-type list views, make sure agents are called \r\nwith the base indices.\r\n- World#RestoreOrigin(): Don't assume &splitright\r\n","3":"- :TRequire\r\n-tlib#input#List: For i-type list views, make sure agents are called \r\nwith the base indices.\r\n- World#RestoreOrigin(): Don't assume &splitright\r\n","package":"tlib.vba.gz","4":"tlib.vba.gz","src_id":"10035","5":"10035","creation_date":"1235593436","6":"1235593436"},{"0":"1863","vim_version":"7.0","1":"7.0","script_version":"0.29","2":"0.29","version_comment":"- tlib#string#Strip(): Strip also control characters (newlines etc.)\r\n- tlib#rx#Suffixes(): 'suffixes' as Regexp\r\n- World#RestoreOrigin(): Don't assume &splitbelow\r\n","3":"- tlib#string#Strip(): Strip also control characters (newlines etc.)\r\n- tlib#rx#Suffixes(): 'suffixes' as Regexp\r\n- World#RestoreOrigin(): Don't assume &splitbelow\r\n","package":"tlib.vba.gz","4":"tlib.vba.gz","src_id":"9957","5":"9957","creation_date":"1234457502","6":"1234457502"},{"0":"1863","vim_version":"7.0","1":"7.0","script_version":"0.28","2":"0.28","version_comment":"- tlib#input#List():\r\n-- Improved handling of sticky lists; <cr> and <Leftmouse> resume a suspended list and immediately selects the item under the cursor\r\n-- Experimental \"seq\" matching style: the conjunctions are sequentially ordered, they are combined with \"OR\" (disjunctions), the regexp is 'magic', and \".\" is expanded to '.\\{-}'\r\n-- Experimental \"cnfd\" matching style: Same as cnf but with an \"elastic\" dot \".\" that matches '\\.\\{-}'\r\n-- Filtering acts as if &ic=1 && $sc=1\r\n-- Weighting is done by the filter\r\n- tlib#agent#Input(): Consume <esc> when aborting input()\r\n- INCOMPATIBLE CHANGE: Changed eligible values of g:tlib_inputlist_match to \"cnf\", \"cnfd\", \"seq\" and \"fuzzy\"\r\n- NEW: tlib#buffer#KeepCursorPosition()\r\n- tlib#buffer#InsertText(): Take care of the extra line when appending text to an empty buffer.\r\n","3":"- tlib#input#List():\r\n-- Improved handling of sticky lists; <cr> and <Leftmouse> resume a suspended list and immediately selects the item under the cursor\r\n-- Experimental \"seq\" matching style: the conjunctions are sequentially ordered, they are combined with \"OR\" (disjunctions), the regexp is 'magic', and \".\" is expanded to '.\\{-}'\r\n-- Experimental \"cnfd\" matching style: Same as cnf but with an \"elastic\" dot \".\" that matches '\\.\\{-}'\r\n-- Filtering acts as if &ic=1 && $sc=1\r\n-- Weighting is done by the filter\r\n- tlib#agent#Input(): Consume <esc> when aborting input()\r\n- INCOMPATIBLE CHANGE: Changed eligible values of g:tlib_inputlist_match to \"cnf\", \"cnfd\", \"seq\" and \"fuzzy\"\r\n- NEW: tlib#buffer#KeepCursorPosition()\r\n- tlib#buffer#InsertText(): Take care of the extra line when appending text to an empty buffer.\r\n","package":"tlib.vba.gz","4":"tlib.vba.gz","src_id":"9592","5":"9592","creation_date":"1228209307","6":"1228209307"},{"0":"1863","vim_version":"7.0","1":"7.0","script_version":"0.27","2":"0.27","version_comment":"- NEW: tlib#normal#WithRegister()\r\n- FIX: Try not to change numbered registers\r\n- FIX: Cosmetic bug, wrong packaging (thanks Nathan Neff)\r\n- Meaning of World#filter_format changed; new World#filter_options \r\n- Filtering didn't work as advertised\r\n","3":"- NEW: tlib#normal#WithRegister()\r\n- FIX: Try not to change numbered registers\r\n- FIX: Cosmetic bug, wrong packaging (thanks Nathan Neff)\r\n- Meaning of World#filter_format changed; new World#filter_options \r\n- Filtering didn't work as advertised\r\n","package":"tlib.vba.gz","4":"tlib.vba.gz","src_id":"9359","5":"9359","creation_date":"1224173545","6":"1224173545"},{"0":"1863","vim_version":"7.0","1":"7.0","script_version":"0.25","2":"0.25","version_comment":"- NEW: tlib#notify#TrimMessage(): trim message to prevent \"Press ENTER\" messages (contributed by Erik Falor)\r\n- NEW: tlib#notify#Echo()\r\n- FIX: World.CloseScratch(): Set window\r\n- FIX: tlib#input#ListW(): Set initial_display = 1 on reset\r\n","3":"- NEW: tlib#notify#TrimMessage(): trim message to prevent \"Press ENTER\" messages (contributed by Erik Falor)\r\n- NEW: tlib#notify#Echo()\r\n- FIX: World.CloseScratch(): Set window\r\n- FIX: tlib#input#ListW(): Set initial_display = 1 on reset\r\n","package":"tlib.vba.gz","4":"tlib.vba.gz","src_id":"9309","5":"9309","creation_date":"1223199011","6":"1223199011"},{"0":"1863","vim_version":"7.0","1":"7.0","script_version":"0.24","2":"0.24","version_comment":"- s:prototype.SetInitialFilter: accept list as argument\r\n- Maintain buffer MRU if required\r\n","3":"- s:prototype.SetInitialFilter: accept list as argument\r\n- Maintain buffer MRU if required\r\n","package":"tlib.vba.gz","4":"tlib.vba.gz","src_id":"9200","5":"9200","creation_date":"1220163452","6":"1220163452"},{"0":"1863","vim_version":"7.0","1":"7.0","script_version":"0.23","2":"0.23","version_comment":"- FIX: very magic mode for tlib#rx#Escape()\r\n- FIX: tlib#arg#Ex: escape \"!\"\r\n- Respect the setting of g:tlib_inputlist_filename_indicators\r\n- tlib#input#List(): Reset syntax on resume; option to make list window \"sticky\"\r\n- tlib#agent#ToggleStickyList()\r\n- Simplified tlib#url#Decode()\r\n- tlib#arg#Ex(): use fnameescape() if available","3":"- FIX: very magic mode for tlib#rx#Escape()\r\n- FIX: tlib#arg#Ex: escape \"!\"\r\n- Respect the setting of g:tlib_inputlist_filename_indicators\r\n- tlib#input#List(): Reset syntax on resume; option to make list window \"sticky\"\r\n- tlib#agent#ToggleStickyList()\r\n- Simplified tlib#url#Decode()\r\n- tlib#arg#Ex(): use fnameescape() if available","package":"tlib.vba.gz","4":"tlib.vba.gz","src_id":"8834","5":"8834","creation_date":"1214085164","6":"1214085164"},{"0":"1863","vim_version":"7.0","1":"7.0","script_version":"0.21","2":"0.21","version_comment":"- tlib#buffer#InsertText(): Respect tabs and (experimental) formatoptions+=or\r\n- tlib\/syntax.vim: Syntax-related functions\r\n","3":"- tlib#buffer#InsertText(): Respect tabs and (experimental) formatoptions+=or\r\n- tlib\/syntax.vim: Syntax-related functions\r\n","package":"tlib.vba.gz","4":"tlib.vba.gz","src_id":"7978","5":"7978","creation_date":"1195642540","6":"1195642540"},{"0":"1863","vim_version":"7.0","1":"7.0","script_version":"0.20","2":"0.20","version_comment":"CHANGES:\r\n- The arguments of tlib#tag#Collect() have changed.\r\n- tlib#input#List(): The view can be \"suspended\" on initial display.\r\n- tlib#input#List(): Follow\/trace cursor functionality\r\n","3":"CHANGES:\r\n- The arguments of tlib#tag#Collect() have changed.\r\n- tlib#input#List(): The view can be \"suspended\" on initial display.\r\n- tlib#input#List(): Follow\/trace cursor functionality\r\n","package":"tlib.vba.gz","4":"tlib.vba.gz","src_id":"7937","5":"7937","creation_date":"1194862947","6":"1194862947"},{"0":"1863","vim_version":"7.0","1":"7.0","script_version":"0.19","2":"0.19","version_comment":"NEW:\r\n    - tag.vim\r\nFIX:\r\n    - dir.vim: Use plain dir name in tlib#dir#Ensure()\r\n    - tlib#input#List(): An initial filter argument creates [[filter]] \r\n    and not as before [[''], [filter]].\r\n    - tlib#input#List(): When type was \"si\" and the item was picked by \r\n    filter, the wrong index was returned.\r\n    - tlib#input#List(): Don't check if chars are typed when displaying \r\n    the list for the first time.\r\n","3":"NEW:\r\n    - tag.vim\r\nFIX:\r\n    - dir.vim: Use plain dir name in tlib#dir#Ensure()\r\n    - tlib#input#List(): An initial filter argument creates [[filter]] \r\n    and not as before [[''], [filter]].\r\n    - tlib#input#List(): When type was \"si\" and the item was picked by \r\n    filter, the wrong index was returned.\r\n    - tlib#input#List(): Don't check if chars are typed when displaying \r\n    the list for the first time.\r\n","package":"tlib.vba.gz","4":"tlib.vba.gz","src_id":"7882","5":"7882","creation_date":"1194302435","6":"1194302435"},{"0":"1863","vim_version":"7.0","1":"7.0","script_version":"0.18","2":"0.18","version_comment":"NEW:\r\n    - tlib\/time.vim\r\n    - g:tlib_inputlist_livesearch_threshold (useful on slower systems)\r\nCHANGES:\r\n    - tlib#input#ListD(), World: Don't redisplay the list while typing \r\n    new letters; calculate filter regexps only once before filtering the \r\n    list.\r\n    - World.vim: Minor changes to how filenames are handled.\r\n","3":"NEW:\r\n    - tlib\/time.vim\r\n    - g:tlib_inputlist_livesearch_threshold (useful on slower systems)\r\nCHANGES:\r\n    - tlib#input#ListD(), World: Don't redisplay the list while typing \r\n    new letters; calculate filter regexps only once before filtering the \r\n    list.\r\n    - World.vim: Minor changes to how filenames are handled.\r\n","package":"tlib.vba.gz","4":"tlib.vba.gz","src_id":"7831","5":"7831","creation_date":"1193357738","6":"1193357738"},{"0":"1863","vim_version":"7.0","1":"7.0","script_version":"0.17","2":"0.17","version_comment":"NEW:\r\n    - TBrowseOutput\r\n- Some minor changes\r\n","3":"NEW:\r\n    - TBrowseOutput\r\n- Some minor changes\r\n","package":"tlib.vba.gz","4":"tlib.vba.gz","src_id":"7788","5":"7788","creation_date":"1192228982","6":"1192228982"},{"0":"1863","vim_version":"7.0","1":"7.0","script_version":"0.16","2":"0.16","version_comment":"- tlib#string#Printf1()","3":"- tlib#string#Printf1()","package":"tlib.vba.gz","4":"tlib.vba.gz","src_id":"7762","5":"7762","creation_date":"1191740348","6":"1191740348"},{"0":"1863","vim_version":"7.0","1":"7.0","script_version":"0.15","2":"0.15","version_comment":"NEW:\r\n    - tlib#string#TrimLeft(), tlib#string#TrimRight(), tlib#string#Strip()\r\n    - Progress bar\r\n","3":"NEW:\r\n    - tlib#string#TrimLeft(), tlib#string#TrimRight(), tlib#string#Strip()\r\n    - Progress bar\r\n","package":"tlib.vba.gz","4":"tlib.vba.gz","src_id":"7733","5":"7733","creation_date":"1191155494","6":"1191155494"},{"0":"1863","vim_version":"7.0","1":"7.0","script_version":"0.14","2":"0.14","version_comment":"NEW:\r\n    - tlib#buffer#InsertText()\r\nCHANGES:\r\n    - tlib#win#[SG]etLayout(): Use a dictionnary, set &cmdheight.\r\nFIXES:\r\n    - tlib#input#List(): Wrong order with pre-defined filters.\r\n","3":"NEW:\r\n    - tlib#buffer#InsertText()\r\nCHANGES:\r\n    - tlib#win#[SG]etLayout(): Use a dictionnary, set &cmdheight.\r\nFIXES:\r\n    - tlib#input#List(): Wrong order with pre-defined filters.\r\n","package":"tlib.vba.gz","4":"tlib.vba.gz","src_id":"7695","5":"7695","creation_date":"1190200967","6":"1190200967"},{"0":"1863","vim_version":"7.0","1":"7.0","script_version":"0.13","2":"0.13","version_comment":"CHANGES:\r\n    - Scratch: Set &fdc=0.\r\n    - The cache directory can be configured via g:tlib_cache\r\n    - Renamed tlib#buffer#SetBuffer() to tlib#buffer#Set().\r\nFIXES:\r\n    - tlib#input#List(): Select the active item per mouse.\r\n    - TLet: simplified\r\n","3":"CHANGES:\r\n    - Scratch: Set &fdc=0.\r\n    - The cache directory can be configured via g:tlib_cache\r\n    - Renamed tlib#buffer#SetBuffer() to tlib#buffer#Set().\r\nFIXES:\r\n    - tlib#input#List(): Select the active item per mouse.\r\n    - TLet: simplified\r\n","package":"tlib.vba.gz","4":"tlib.vba.gz","src_id":"7648","5":"7648","creation_date":"1189502573","6":"1189502573"},{"0":"1863","vim_version":"7.0","1":"7.0","script_version":"0.12","2":"0.12","version_comment":"NEW:\r\n    - tlib\/tab.vim\r\nCHANGES:\r\n    - Renamed tlib#win#SetWin() to tlib#win#Set()\r\nIMPROVEMENTS:\r\n    - tlib#input#List(): <left>, <right> keys work in some lists\r\n    - tlib#input#List(): If an index_table is provided this will be used \r\n    instead of the item's list index.\r\nFIXES:\r\n    - tlib#input#List(): Problem with scrolling, when the list was \r\n    shorter than the window (eg when using a vertical window).\r\n    - tlib#cache#Filename(): Don't rewrite name as relative filename if \r\n    explicitly given as argument. Avoid double (back)slashes.\r\n    - TLet: simplified\r\n","3":"NEW:\r\n    - tlib\/tab.vim\r\nCHANGES:\r\n    - Renamed tlib#win#SetWin() to tlib#win#Set()\r\nIMPROVEMENTS:\r\n    - tlib#input#List(): <left>, <right> keys work in some lists\r\n    - tlib#input#List(): If an index_table is provided this will be used \r\n    instead of the item's list index.\r\nFIXES:\r\n    - tlib#input#List(): Problem with scrolling, when the list was \r\n    shorter than the window (eg when using a vertical window).\r\n    - tlib#cache#Filename(): Don't rewrite name as relative filename if \r\n    explicitly given as argument. Avoid double (back)slashes.\r\n    - TLet: simplified\r\n","package":"tlib.vba.gz","4":"tlib.vba.gz","src_id":"7632","5":"7632","creation_date":"1189226237","6":"1189226237"},{"0":"1863","vim_version":"7.0","1":"7.0","script_version":"0.11","2":"0.11","version_comment":"NEW:\r\n    - The :TLet command replaces :TLLet (which was removed)\r\n    - :TScratch[!] command (with ! don't split but use the whole window)\r\n    - tlib#rx#Escape(text, ?magic='m')\r\n    - tlib#buffer#GetList(?show_hidden=0)\r\n    - tlib#dir#CD(), tlib#dir#Push(), tlib#dir#Pop()\r\n    - tlib#input#ListW: A slightly remodeled version of tlib#input#List \r\n    that takes a World as second argument.\r\n    - Added some documentation doc\/tlib.txt (most of it is automatically \r\n    compiled from the source files)\r\nCHANGES:\r\n    - tlib#input#List(): The default keys for AND, NOT have changed to \r\n    be more Google-like (space, minus); the keys can be configured via \r\n    global variables.\r\nIMPROVEMENTS:\r\n    - In file listings, indicate if a file is loaded, listed, modified \r\n    etc.\r\n    - tlib#input#List(): Highlight the filter pattern\r\n    - tlib#input#List(): <c-up\/down> scrolls g:tlib_scroll_lines \r\n    (default=10) lines\r\nFIXES:\r\n    - tlib#input#List(): Centering line, clear match, clear & restore \r\n    the search register\r\n    - tlib#input#List(): Ensure the window layout doesn't change (if the \r\n    number of windows hasn't changed)\r\n    - tlib#arg#Ex(): Don't escape backslashes by default\r\n","3":"NEW:\r\n    - The :TLet command replaces :TLLet (which was removed)\r\n    - :TScratch[!] command (with ! don't split but use the whole window)\r\n    - tlib#rx#Escape(text, ?magic='m')\r\n    - tlib#buffer#GetList(?show_hidden=0)\r\n    - tlib#dir#CD(), tlib#dir#Push(), tlib#dir#Pop()\r\n    - tlib#input#ListW: A slightly remodeled version of tlib#input#List \r\n    that takes a World as second argument.\r\n    - Added some documentation doc\/tlib.txt (most of it is automatically \r\n    compiled from the source files)\r\nCHANGES:\r\n    - tlib#input#List(): The default keys for AND, NOT have changed to \r\n    be more Google-like (space, minus); the keys can be configured via \r\n    global variables.\r\nIMPROVEMENTS:\r\n    - In file listings, indicate if a file is loaded, listed, modified \r\n    etc.\r\n    - tlib#input#List(): Highlight the filter pattern\r\n    - tlib#input#List(): <c-up\/down> scrolls g:tlib_scroll_lines \r\n    (default=10) lines\r\nFIXES:\r\n    - tlib#input#List(): Centering line, clear match, clear & restore \r\n    the search register\r\n    - tlib#input#List(): Ensure the window layout doesn't change (if the \r\n    number of windows hasn't changed)\r\n    - tlib#arg#Ex(): Don't escape backslashes by default\r\n","package":"tlib.vba.gz","4":"tlib.vba.gz","src_id":"7559","5":"7559","creation_date":"1188130156","6":"1188130156"},{"0":"1863","vim_version":"7.0","1":"7.0","script_version":"0.10","2":"0.10","version_comment":"- tlib#input#List(): (v)split type of commands leave the original window \r\nuntouched (you may use <c-w> to replace its contents)\r\n- tlib#file#With(): Check whether an existing buffer is loaded.\r\n- Scratch related functions went to tlib\/scratch.vim so that they are \r\naccessible from other scripts.\r\n- Configure the list window height via g:tlib_inputlist_pct (1..100%)\r\n","3":"- tlib#input#List(): (v)split type of commands leave the original window \r\nuntouched (you may use <c-w> to replace its contents)\r\n- tlib#file#With(): Check whether an existing buffer is loaded.\r\n- Scratch related functions went to tlib\/scratch.vim so that they are \r\naccessible from other scripts.\r\n- Configure the list window height via g:tlib_inputlist_pct (1..100%)\r\n","package":"tlib.vba.gz","4":"tlib.vba.gz","src_id":"7380","5":"7380","creation_date":"1184761382","6":"1184761382"},{"0":"1863","vim_version":"7.0","1":"7.0","script_version":"0.9","2":"0.9","version_comment":"- Re-arrangements & modularization (this means many function names have \r\nchanged, on the other hand only those functions are loaded that are \r\nactually needed)\r\n- tlib#input#List(): Added maps with m-modifiers for <c-q>, <c-z>, <c-a>\r\n- tlib#input#List(): Make sure &fdm is manual\r\n- tlib#input#List(): When exiting the list view, consume the next 5 \r\ncharacters in the queue (if any)\r\n- tlib#input#EditList(): Now has cut, copy, paste functionality.\r\n- Added documentation and examples\r\n","3":"- Re-arrangements & modularization (this means many function names have \r\nchanged, on the other hand only those functions are loaded that are \r\nactually needed)\r\n- tlib#input#List(): Added maps with m-modifiers for <c-q>, <c-z>, <c-a>\r\n- tlib#input#List(): Make sure &fdm is manual\r\n- tlib#input#List(): When exiting the list view, consume the next 5 \r\ncharacters in the queue (if any)\r\n- tlib#input#EditList(): Now has cut, copy, paste functionality.\r\n- Added documentation and examples\r\n","package":"tlib.vba.gz","4":"tlib.vba.gz","src_id":"7359","5":"7359","creation_date":"1184662995","6":"1184662995"},{"0":"1863","vim_version":"7.0","1":"7.0","script_version":"0.8","2":"0.8","version_comment":"- FIX: Return empty cache name for buffers that have no files attached to it\r\n- Some re-arranging\r\n","3":"- FIX: Return empty cache name for buffers that have no files attached to it\r\n- Some re-arranging\r\n","package":"tlib.vba.gz","4":"tlib.vba.gz","src_id":"7299","5":"7299","creation_date":"1182677748","6":"1182677748"},{"0":"1863","vim_version":"7.0","1":"7.0","script_version":"0.7","2":"0.7","version_comment":"- tlib#InputList(): <c-z> ... Suspend\/Resume input loop\r\n- tlib#InputList(): <c-q> ... Input text on the command line (useful on slow systems when working with very large lists)\r\n- tlib#InputList(): AND-pattern starting with '!' will work as 'exclude matches'\r\n- tlib#InputList(): FIX <c-bs> pop OR-patterns properly\r\n- tlib#InputList(): display_format == filename: don't add '\/' to directory names (avoid filesystem access)\r\n","3":"- tlib#InputList(): <c-z> ... Suspend\/Resume input loop\r\n- tlib#InputList(): <c-q> ... Input text on the command line (useful on slow systems when working with very large lists)\r\n- tlib#InputList(): AND-pattern starting with '!' will work as 'exclude matches'\r\n- tlib#InputList(): FIX <c-bs> pop OR-patterns properly\r\n- tlib#InputList(): display_format == filename: don't add '\/' to directory names (avoid filesystem access)\r\n","package":"tlib.vba.gz","4":"tlib.vba.gz","src_id":"7269","5":"7269","creation_date":"1182339100","6":"1182339100"},{"0":"1863","vim_version":"7.0","1":"7.0","script_version":"0.6","2":"0.6","version_comment":"- tlib#InputList(): Disabled <c-space> map\r\n- tlib#InputList(): try to be smart about user itentions only if a \r\nlist's length is < g:tlib_sortprefs_threshold (default: 200)\r\n- tlib#Object: Super() method\r\n- tlib#MyRuntimeDir()\r\n- tlib#GetCacheName(), tlib#CacheSave(), tlib#CacheGet()\r\n- tlib#Args(), tlib#GetArg()\r\n- FIX: tlib#InputList(): Display problem with first item\r\n","3":"- tlib#InputList(): Disabled <c-space> map\r\n- tlib#InputList(): try to be smart about user itentions only if a \r\nlist's length is < g:tlib_sortprefs_threshold (default: 200)\r\n- tlib#Object: Super() method\r\n- tlib#MyRuntimeDir()\r\n- tlib#GetCacheName(), tlib#CacheSave(), tlib#CacheGet()\r\n- tlib#Args(), tlib#GetArg()\r\n- FIX: tlib#InputList(): Display problem with first item\r\n","package":"tlib.vba.gz","4":"tlib.vba.gz","src_id":"7157","5":"7157","creation_date":"1179917038","6":"1179917038"},{"0":"1863","vim_version":"7.0","1":"7.0","script_version":"0.5","2":"0.5","version_comment":"- tlib#InputList(): FIX: Selecting items in filtered view\r\n- tlib#InputList(): <c-bs>: Remove last AND pattern from filter\r\n","3":"- tlib#InputList(): FIX: Selecting items in filtered view\r\n- tlib#InputList(): <c-bs>: Remove last AND pattern from filter\r\n","package":"tlib.vba.gz","4":"tlib.vba.gz","src_id":"7130","5":"7130","creation_date":"1179382769","6":"1179382769"},{"0":"1863","vim_version":"7.0","1":"7.0","script_version":"0.4","2":"0.4","version_comment":"- tlib#InputList(): Up\/Down keys wrap around list\r\n- tlib#InputList(): FIX: Problem when reducing the filter & using AND\r\n- tlib#InputList(): FIX: Problem when using shift-up\/down with filtered lists\r\n- tlib#InputList(): Made <a-numeric> work (can be configured via \r\n- tlib#InputList(): special display_format: \"filename\"\r\n- tlib#Object: experimental support for some kind of OOP\r\n- tlib#World: Extracted some functions from tlib.vim to tlib\/World.vim\r\n- tlib#FileJoin(), tlib#FileSplit(), tlib#RelativeFilename()\r\n- tlib#Let()\r\n- tlib#EnsureDirectoryExists(dir)\r\n- tlib#DirName(dir)\r\n- tlib#DecodeURL(url), tlib#EncodeChar(char), tlib#EncodeURL(url)\r\n","3":"- tlib#InputList(): Up\/Down keys wrap around list\r\n- tlib#InputList(): FIX: Problem when reducing the filter & using AND\r\n- tlib#InputList(): FIX: Problem when using shift-up\/down with filtered lists\r\n- tlib#InputList(): Made <a-numeric> work (can be configured via \r\n- tlib#InputList(): special display_format: \"filename\"\r\n- tlib#Object: experimental support for some kind of OOP\r\n- tlib#World: Extracted some functions from tlib.vim to tlib\/World.vim\r\n- tlib#FileJoin(), tlib#FileSplit(), tlib#RelativeFilename()\r\n- tlib#Let()\r\n- tlib#EnsureDirectoryExists(dir)\r\n- tlib#DirName(dir)\r\n- tlib#DecodeURL(url), tlib#EncodeChar(char), tlib#EncodeURL(url)\r\n","package":"tlib.vba.gz","4":"tlib.vba.gz","src_id":"7113","5":"7113","creation_date":"1179224446","6":"1179224446"},{"0":"1863","vim_version":"7.0","1":"7.0","script_version":"0.3","2":"0.3","version_comment":"- Show feedback in statusline instead of the echo area\r\n- tlib#GetVar(), tlib#GetValue()\r\n","3":"- Show feedback in statusline instead of the echo area\r\n- tlib#GetVar(), tlib#GetValue()\r\n","package":"tlib.vba.gz","4":"tlib.vba.gz","src_id":"7029","5":"7029","creation_date":"1177580583","6":"1177580583"},{"0":"1863","vim_version":"7.0","1":"7.0","script_version":"0.2","2":"0.2","version_comment":"- More list convenience functions\r\n- tlib#EditList()\r\n- tlib#InputList(): properly handle duplicate items; it type contains \r\n'i', the list index + 1 is returned, not the element\r\n","3":"- More list convenience functions\r\n- tlib#EditList()\r\n- tlib#InputList(): properly handle duplicate items; it type contains \r\n'i', the list index + 1 is returned, not the element\r\n","package":"tlib.vba.gz","4":"tlib.vba.gz","src_id":"7021","5":"7021","creation_date":"1177411064","6":"1177411064"},{"0":"1863","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"tlib.vba.gz","4":"tlib.vba.gz","src_id":"6998","5":"6998","creation_date":"1176891740","6":"1176891740"}]},"1862":{"script_id":"1862","0":"1862","script_name":"kpl.vim","1":"kpl.vim","script_type":"syntax","2":"syntax","summary":"KPL (A Kernel Programming Language) syntax file","3":"KPL (A Kernel Programming Language) syntax file","description":"KPL is the C-like language used for programming for BLITZ (see http:\/\/web.cecs.pdx.edu\/~harry\/Blitz\/)","4":"KPL is the C-like language used for programming for BLITZ (see http:\/\/web.cecs.pdx.edu\/~harry\/Blitz\/)","install_details":"Place kpl.vim in your .vim\/syntax directory, and call \":setf kpl\" to load the syntax.  Since the files end in .c and .h, I haven't bothered to try and automatically determine the filetype.","5":"Place kpl.vim in your .vim\/syntax directory, and call \":setf kpl\" to load the syntax.  Since the files end in .c and .h, I haven't bothered to try and automatically determine the filetype.","first_name":"Adam","6":"Adam","last_name":"Blinkinsop","7":"Blinkinsop","releases":[{"0":"1862","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"kpl.vim","4":"kpl.vim","src_id":"6994","5":"6994","creation_date":"1176834680","6":"1176834680"}]},"1861":{"script_id":"1861","0":"1861","script_name":"errormarker.vim","1":"errormarker.vim","script_type":"utility","2":"utility","summary":"Highlights and sets error markers for lines with compile errors","3":"Highlights and sets error markers for lines with compile errors","description":"Hooks the make quickfix command and converts all compiler errors into signs that are placed next to the line with the error. Additionally, lines with errors are highlighted. Hover with your mouse over such a line to get the error message in a tooltip (only gui), or press \\cc. The error markers will be updated on every call to :make.\r\n\r\nA screenshot of doxygen in action with a lot of errors can be found at http:\/\/mh21.github.io\/vim-error-markers-doxygen.png.\r\n\r\nGet the latest version, submit pull requests, and file bug reports on GitHub:\r\n        https:\/\/github.com\/mh21\/errormarker.vim","4":"Hooks the make quickfix command and converts all compiler errors into signs that are placed next to the line with the error. Additionally, lines with errors are highlighted. Hover with your mouse over such a line to get the error message in a tooltip (only gui), or press \\cc. The error markers will be updated on every call to :make.\r\n\r\nA screenshot of doxygen in action with a lot of errors can be found at http:\/\/mh21.github.io\/vim-error-markers-doxygen.png.\r\n\r\nGet the latest version, submit pull requests, and file bug reports on GitHub:\r\n        https:\/\/github.com\/mh21\/errormarker.vim","install_details":"Use pathogen.vim.\r\n    cd ~\/.vim\/bundle\r\n    git clone git:\/\/github.com\/mh21\/errormarker.vim\r\n\r\nTo distinguish between warnings and errors for gcc messages, place sth. like this in your .vimrc:\r\n        let &errorformat=\"%f:%l:%c: %t%*[^:]:%m,%f:%l: %t%*[^:]:%m,\" . &errorformat\r\nIf you use a different locale than English, this may be also needed:\r\n        set makeprg=LANGUAGE=C\\ make","5":"Use pathogen.vim.\r\n    cd ~\/.vim\/bundle\r\n    git clone git:\/\/github.com\/mh21\/errormarker.vim\r\n\r\nTo distinguish between warnings and errors for gcc messages, place sth. like this in your .vimrc:\r\n        let &errorformat=\"%f:%l:%c: %t%*[^:]:%m,%f:%l: %t%*[^:]:%m,\" . &errorformat\r\nIf you use a different locale than English, this may be also needed:\r\n        set makeprg=LANGUAGE=C\\ make","first_name":"Michael","6":"Michael","last_name":"Hofmann","7":"Hofmann","releases":[{"0":"1861","vim_version":"7.0","1":"7.0","script_version":"0.2.1","2":"0.2.1","version_comment":"- only remove own signs (thanks Mike Szymaniak)","3":"- only remove own signs (thanks Mike Szymaniak)","package":"errormarker-0.2.1.zip","4":"errormarker-0.2.1.zip","src_id":"24225","5":"24225","creation_date":"1462352207","6":"1462352207"},{"0":"1861","vim_version":"7.0","1":"7.0","script_version":"0.2","2":"0.2","version_comment":"- redraw (thanks yoppi, kano4)\r\n- ship icons, sign highlight (thanks andersonfreitas)\r\n- ship docs separately, moved to github (thanks mbertheau)\r\n","3":"- redraw (thanks yoppi, kano4)\r\n- ship icons, sign highlight (thanks andersonfreitas)\r\n- ship docs separately, moved to github (thanks mbertheau)\r\n","package":"errormarker-0.2.zip","4":"errormarker-0.2.zip","src_id":"22825","5":"22825","creation_date":"1422200355","6":"1422200355"},{"0":"1861","vim_version":"7.0","1":"7.0","script_version":"0.1.13","2":"0.1.13","version_comment":"- shortcut can be disabled (thanks Michael Jansen)","3":"- shortcut can be disabled (thanks Michael Jansen)","package":"errormarker.vim","4":"errormarker.vim","src_id":"14142","5":"14142","creation_date":"1288291723","6":"1288291723"},{"0":"1861","vim_version":"7.0","1":"7.0","script_version":"0.1.12","2":"0.1.12","version_comment":"shortcut (<Leader>cc) to show error at cursor (thanks Eric Rannaud)","3":"shortcut (<Leader>cc) to show error at cursor (thanks Eric Rannaud)","package":"errormarker.vim","4":"errormarker.vim","src_id":"13041","5":"13041","creation_date":"1274474946","6":"1274474946"},{"0":"1861","vim_version":"7.0","1":"7.0","script_version":"0.1.11","2":"0.1.11","version_comment":"- changelog fix","3":"- changelog fix","package":"errormarker.vim","4":"errormarker.vim","src_id":"8877","5":"8877","creation_date":"1214903187","6":"1214903187"},{"0":"1861","vim_version":"7.0","1":"7.0","script_version":"0.1.10","2":"0.1.10","version_comment":"- removes accidental dependency on NerdEcho","3":"- removes accidental dependency on NerdEcho","package":"errormarker.vim","4":"errormarker.vim","src_id":"8876","5":"8876","creation_date":"1214902762","6":"1214902762"},{"0":"1861","vim_version":"7.0","1":"7.0","script_version":"0.1.9","2":"0.1.9","version_comment":"- fixes Win32 icon display","3":"- fixes Win32 icon display","package":"errormarker.vim","4":"errormarker.vim","src_id":"7264","5":"7264","creation_date":"1182220676","6":"1182220676"},{"0":"1861","vim_version":"7.0","1":"7.0","script_version":"0.1.8","2":"0.1.8","version_comment":"- check for Vim version","3":"- check for Vim version","package":"errormarker.vim","4":"errormarker.vim","src_id":"7225","5":"7225","creation_date":"1181467802","6":"1181467802"},{"0":"1861","vim_version":"7.0","1":"7.0","script_version":"0.1.7","2":"0.1.7","version_comment":"- fixes gcc error message parsing example","3":"- fixes gcc error message parsing example","package":"errormarker.vim","4":"errormarker.vim","src_id":"7214","5":"7214","creation_date":"1181180888","6":"1181180888"},{"0":"1861","vim_version":"7.0","1":"7.0","script_version":"0.1.6","2":"0.1.6","version_comment":"- support for GetLatestVimScripts (vimscript#642)","3":"- support for GetLatestVimScripts (vimscript#642)","package":"errormarker.vim","4":"errormarker.vim","src_id":"7068","5":"7068","creation_date":"1178288978","6":"1178288978"},{"0":"1861","vim_version":"7.0","1":"7.0","script_version":"0.1.5","2":"0.1.5","version_comment":"- clarified documentation about paths","3":"- clarified documentation about paths","package":"errormarker.vim","4":"errormarker.vim","src_id":"7012","5":"7012","creation_date":"1177123850","6":"1177123850"}]},"1860":{"script_id":"1860","0":"1860","script_name":"Directory-specific settings","1":"Directory-specific settings","script_type":"utility","2":"utility","summary":"Easily have settings that apply only to files under a given directory","3":"Easily have settings that apply only to files under a given directory","description":"This is a very simple plugin that allows for directory tree-specific vim settings.\r\n\r\nFor example, I prefer to indent with spaces, but one of the code bases I'm working on uses TABs for indentation.  So, instead of mucking with settings and going back and forth, I just create a file called \".vimdir\" at the top of that tree and put in some code like this:\r\n\r\nsetlocal noexpandtab\r\n\r\nAnd that's it!  Every file I edit under that directory will use that setting!\r\n\r\nFor every file edited, it searches upward from that file's directory for a file named '.vimdir' and sources it.  So, any arbitrary code can be put into the .vimdir file.  But you should take care to ensure that the code applies only to that file and doesn't have any global side-effects.  So, for example, always use 'setlocal'.\r\n\r\nThis plugin is very similar to vimscript #441.\r\n","4":"This is a very simple plugin that allows for directory tree-specific vim settings.\r\n\r\nFor example, I prefer to indent with spaces, but one of the code bases I'm working on uses TABs for indentation.  So, instead of mucking with settings and going back and forth, I just create a file called \".vimdir\" at the top of that tree and put in some code like this:\r\n\r\nsetlocal noexpandtab\r\n\r\nAnd that's it!  Every file I edit under that directory will use that setting!\r\n\r\nFor every file edited, it searches upward from that file's directory for a file named '.vimdir' and sources it.  So, any arbitrary code can be put into the .vimdir file.  But you should take care to ensure that the code applies only to that file and doesn't have any global side-effects.  So, for example, always use 'setlocal'.\r\n\r\nThis plugin is very similar to vimscript #441.\r\n","install_details":"Place in .vim\/plugin.","5":"Place in .vim\/plugin.","first_name":"Tye","6":"Tye","last_name":"Zdrojewski","7":"Zdrojewski","releases":[{"0":"1860","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"dirsettings.vim","4":"dirsettings.vim","src_id":"6980","5":"6980","creation_date":"1176655817","6":"1176655817"}]},"1859":{"script_id":"1859","0":"1859","script_name":"eZVim","1":"eZVim","script_type":"utility","2":"utility","summary":"eZVim adds some features to vim for eZ Publish CMS","3":"eZVim adds some features to vim for eZ Publish CMS","description":"Features\r\n    * Classes View : a sidebar displaying group classes, classes and attributes of content object classes.\r\n    * Syntax highligthing for eZ Publish templates and ini files\r\n    * Some vim abbreviations for the eZ Publish template syntax.\r\n\r\nRequirements\r\n    * vim and python scripting support. Under Debian or Ubuntu, just install the vim-python package.\r\n    * eZ Publish with the eZDevtools extension.\r\n\r\nTested with vim 7.1 under Ubuntu. It should work under any Unix. Not tested with others. \r\n\r\nSee project page http:\/\/projects.ez.no\/ezvim for more.","4":"Features\r\n    * Classes View : a sidebar displaying group classes, classes and attributes of content object classes.\r\n    * Syntax highligthing for eZ Publish templates and ini files\r\n    * Some vim abbreviations for the eZ Publish template syntax.\r\n\r\nRequirements\r\n    * vim and python scripting support. Under Debian or Ubuntu, just install the vim-python package.\r\n    * eZ Publish with the eZDevtools extension.\r\n\r\nTested with vim 7.1 under Ubuntu. It should work under any Unix. Not tested with others. \r\n\r\nSee project page http:\/\/projects.ez.no\/ezvim for more.","install_details":"","5":"","first_name":"Damien","6":"Damien","last_name":"POBEL","7":"POBEL","releases":[{"0":"1859","vim_version":"7.0","1":"7.0","script_version":"0.2","2":"0.2","version_comment":"New version with syntax highlithing for eZ Publish templates and ini files.","3":"New version with syntax highlithing for eZ Publish templates and ini files.","package":"ezvim-0.2.tar.gz","4":"ezvim-0.2.tar.gz","src_id":"9834","5":"9834","creation_date":"1232144770","6":"1232144770"},{"0":"1859","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"ezvim-0.1.tar.gz","4":"ezvim-0.1.tar.gz","src_id":"6964","5":"6964","creation_date":"1176040456","6":"1176040456"}]},"1858":{"script_id":"1858","0":"1858","script_name":"mako.vim","1":"mako.vim","script_type":"syntax","2":"syntax","summary":"Adds mako support to vim","3":"Adds mako support to vim","description":"Adds support for the mako python template engine to vim.\r\n\r\nMako: http:\/\/www.makotemplates.org\/\r\n\r\nLicense: three clause BSD","4":"Adds support for the mako python template engine to vim.\r\n\r\nMako: http:\/\/www.makotemplates.org\/\r\n\r\nLicense: three clause BSD","install_details":"Copy into ~\/.vim\/syntax. Requires html.vim and python.vim to work.","5":"Copy into ~\/.vim\/syntax. Requires html.vim and python.vim to work.","first_name":"Armin","6":"Armin","last_name":"Ronacher","7":"Ronacher","releases":[{"0":"1858","vim_version":"6.0","1":"6.0","script_version":"0.6.1","2":"0.6.1","version_comment":"Fixed a bug in <%namespace> highlighting.","3":"Fixed a bug in <%namespace> highlighting.","package":"mako.vim","4":"mako.vim","src_id":"9244","5":"9244","creation_date":"1221226585","6":"1221226585"},{"0":"1858","vim_version":"6.0","1":"6.0","script_version":"0.6","2":"0.6","version_comment":"attributes are now highlighted as makoAttributeKey and makoAttributeValue instead of using the python lexer. Those default to Type and String.","3":"attributes are now highlighted as makoAttributeKey and makoAttributeValue instead of using the python lexer. Those default to Type and String.","package":"mako.vim","4":"mako.vim","src_id":"7013","5":"7013","creation_date":"1177208504","6":"1177208504"},{"0":"1858","vim_version":"6.0","1":"6.0","script_version":"0.5","2":"0.5","version_comment":"Initial upload","3":"Initial upload","package":"mako.vim","4":"mako.vim","src_id":"6963","5":"6963","creation_date":"1176005901","6":"1176005901"}]},"1857":{"script_id":"1857","0":"1857","script_name":"native.vim","1":"native.vim","script_type":"color scheme","2":"color scheme","summary":"dark greenish theme for vim.","3":"dark greenish theme for vim.","description":"Screenshot: http:\/\/pocoo.org\/~mitsuhiko\/green-human.png","4":"Screenshot: http:\/\/pocoo.org\/~mitsuhiko\/green-human.png","install_details":"Copy it into ~\/.vim\/colors","5":"Copy it into ~\/.vim\/colors","first_name":"Armin","6":"Armin","last_name":"Ronacher","7":"Ronacher","releases":[{"0":"1857","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"native.vim","4":"native.vim","src_id":"6962","5":"6962","creation_date":"1175998869","6":"1175998869"}]},"1856":{"script_id":"1856","0":"1856","script_name":"Jinja","1":"Jinja","script_type":"syntax","2":"syntax","summary":"adds jinja highlighting support to vim","3":"adds jinja highlighting support to vim","description":"Adds Jinja support to vim. The jinja.vim just highlights Jinja, the jinjahtml.vim which you can install additionally also highlights HTML around the Jinja tags.\r\n\r\nJinja is a template engine for python located at http:\/\/jinja.pocoo.org\/\r\n\r\nScreenshot with my personal vim theme: http:\/\/lucumr.pocoo.org\/static\/pictures\/jinja_in_vim.png","4":"Adds Jinja support to vim. The jinja.vim just highlights Jinja, the jinjahtml.vim which you can install additionally also highlights HTML around the Jinja tags.\r\n\r\nJinja is a template engine for python located at http:\/\/jinja.pocoo.org\/\r\n\r\nScreenshot with my personal vim theme: http:\/\/lucumr.pocoo.org\/static\/pictures\/jinja_in_vim.png","install_details":"Copy the jinja.vim into your ~\/.vim\/syntax folder","5":"Copy the jinja.vim into your ~\/.vim\/syntax folder","first_name":"Armin","6":"Armin","last_name":"Ronacher","7":"Ronacher","releases":[{"0":"1856","vim_version":"7.0","1":"7.0","script_version":"1.1","2":"1.1","version_comment":"Added support for Jinja2.","3":"Added support for Jinja2.","package":"jinja.vim","4":"jinja.vim","src_id":"8666","5":"8666","creation_date":"1210301863","6":"1210301863"},{"0":"1856","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"additional file for html+jinja highlighting","3":"additional file for html+jinja highlighting","package":"htmljinja.vim","4":"htmljinja.vim","src_id":"6961","5":"6961","creation_date":"1175998005","6":"1175998005"},{"0":"1856","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"jinja.vim","4":"jinja.vim","src_id":"6960","5":"6960","creation_date":"1175997976","6":"1175997976"}]},"1855":{"script_id":"1855","0":"1855","script_name":"textmate16.vim","1":"textmate16.vim","script_type":"color scheme","2":"color scheme","summary":"Textmate like colors for 16 color xterm.","3":"Textmate like colors for 16 color xterm.","description":"Color scheme to emulate the default color scheme from textmate for ruby scripts. Designed to work with an xterm with 16 colors. The background color is not changed and the intention is that the color scheme be used with a dark back ground, so the user should change the background to a dark gray or black. If you are using the gui then use the vibrantink.vim color scheme instead.","4":"Color scheme to emulate the default color scheme from textmate for ruby scripts. Designed to work with an xterm with 16 colors. The background color is not changed and the intention is that the color scheme be used with a dark back ground, so the user should change the background to a dark gray or black. If you are using the gui then use the vibrantink.vim color scheme instead.","install_details":"Copy the file textmate16.vim to ~\/.vim\/colors and then add a line to your .vimrc file;\r\ncolorscheme textmate16\r\nEnsure that syntax is enabled, which is done by adding the following line to your .vimrc file;\r\nsyntax enable","5":"Copy the file textmate16.vim to ~\/.vim\/colors and then add a line to your .vimrc file;\r\ncolorscheme textmate16\r\nEnsure that syntax is enabled, which is done by adding the following line to your .vimrc file;\r\nsyntax enable","first_name":"Bruce","6":"Bruce","last_name":"Woodward","7":"Woodward","releases":[{"0":"1855","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"textmate16.vim","4":"textmate16.vim","src_id":"6955","5":"6955","creation_date":"1175834346","6":"1175834346"}]},"1854":{"script_id":"1854","0":"1854","script_name":"Xdebugx\\'s dictionary of functions","1":"Xdebugx\\'s dictionary of functions","script_type":"ftplugin","2":"ftplugin","summary":"This is simply  dictionary of Xdebug2 functions","3":"This is simply  dictionary of Xdebug2 functions","description":"This is simply  dictionary of Xdebug2 functions. So after install it you can use auto completion of these functions in your PHP scripts.\r\n\r\nFor more details watch http:\/\/xdebug.org\/","4":"This is simply  dictionary of Xdebug2 functions. So after install it you can use auto completion of these functions in your PHP scripts.\r\n\r\nFor more details watch http:\/\/xdebug.org\/","install_details":"Copy the file to your \\\"dic directory\\\" (usually it is ~\/.vim\/dic) and add to your ~\/.vimrc or PHP\\'s ftplugin config:\r\n\r\nset dictionary+=~\/.vim\/dic\/xdebug2\r\n","5":"Copy the file to your \\\"dic directory\\\" (usually it is ~\/.vim\/dic) and add to your ~\/.vimrc or PHP\\'s ftplugin config:\r\n\r\nset dictionary+=~\/.vim\/dic\/xdebug2\r\n","first_name":"James","6":"James","last_name":"Bond","7":"Bond","releases":[{"0":"1854","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"xdebug2","4":"xdebug2","src_id":"6954","5":"6954","creation_date":"1175809913","6":"1175809913"}]},"1853":{"script_id":"1853","0":"1853","script_name":"Twitter","1":"Twitter","script_type":"utility","2":"utility","summary":"A simple client for Twitter","3":"A simple client for Twitter","description":"It's just a simple client for Twitter, if you want to update your Twitter status, check public timeline or your friends timeline all right from within your Vim, then this script is for you!\r\n\r\nNOTE: It requires your Vim to be compiled with Python bindings (which is, in most distributions by default)","4":"It's just a simple client for Twitter, if you want to update your Twitter status, check public timeline or your friends timeline all right from within your Vim, then this script is for you!\r\n\r\nNOTE: It requires your Vim to be compiled with Python bindings (which is, in most distributions by default)","install_details":"Extract the tarball into your ~\/.vim\/plugin\r\nIn order to update your status or fetch your friends time line you have to set your Twitter accounts username\/password pair, you can set them using:\r\n\r\n:let g:twitterusername='username'\r\n:let g:twitterpassword='password'\r\n\r\nor put 'em in your ~\/.vimrc\r\n\r\n\r\nUSER NOTES (useful tips from a user of this script):\r\n-----------------------------------------------------------------------\r\nHere's what I added to my _vimrc:\r\n\r\n\" helpful mappings for using twitter.vim\r\n\" see http:\/\/vim.sourceforge.net\/scripts\/script.php?script_id=1853\r\n\r\nlet g:twitterusername='username'\r\nlet g:twitterpassword=''\r\n\r\nmap <unique> <eader>tp <Esc>:let g:twitterpassword=inputsecret('password? ')<cr>\r\nmap <unique> <eader>tw <Esc>:execute 'TwitterStatusUpdate ' . inputdialog('Enter a Twitter status message:')<cr>\r\nmap <unique> <eader>tf <Esc>:TwitterFriendsTimeline<cr>\r\n\r\ntp will prompt you for your twitter password so you don't have to hardcode it in a file, tw will prompt you for your status message and tf will list your friend's twitters.","5":"Extract the tarball into your ~\/.vim\/plugin\r\nIn order to update your status or fetch your friends time line you have to set your Twitter accounts username\/password pair, you can set them using:\r\n\r\n:let g:twitterusername='username'\r\n:let g:twitterpassword='password'\r\n\r\nor put 'em in your ~\/.vimrc\r\n\r\n\r\nUSER NOTES (useful tips from a user of this script):\r\n-----------------------------------------------------------------------\r\nHere's what I added to my _vimrc:\r\n\r\n\" helpful mappings for using twitter.vim\r\n\" see http:\/\/vim.sourceforge.net\/scripts\/script.php?script_id=1853\r\n\r\nlet g:twitterusername='username'\r\nlet g:twitterpassword=''\r\n\r\nmap <unique> <eader>tp <Esc>:let g:twitterpassword=inputsecret('password? ')<cr>\r\nmap <unique> <eader>tw <Esc>:execute 'TwitterStatusUpdate ' . inputdialog('Enter a Twitter status message:')<cr>\r\nmap <unique> <eader>tf <Esc>:TwitterFriendsTimeline<cr>\r\n\r\ntp will prompt you for your twitter password so you don't have to hardcode it in a file, tw will prompt you for your status message and tf will list your friend's twitters.","first_name":"Amir Mohammad","6":"Amir Mohammad","last_name":"Saied","7":"Saied","releases":[{"0":"1853","vim_version":"6.0","1":"6.0","script_version":"0.2","2":"0.2","version_comment":"Source fixed, now you would get \"from VimScript#1853\" appended to your status updates.","3":"Source fixed, now you would get \"from VimScript#1853\" appended to your status updates.","package":"twitter.tar.gz","4":"twitter.tar.gz","src_id":"8574","5":"8574","creation_date":"1208474206","6":"1208474206"},{"0":"1853","vim_version":"6.0","1":"6.0","script_version":"0.1.1","2":"0.1.1","version_comment":"BUGFIX: It's now possible to pass statuses containing ' (single-quotation)\r\n(Thanks to Armen Baghumian)","3":"BUGFIX: It's now possible to pass statuses containing ' (single-quotation)\r\n(Thanks to Armen Baghumian)","package":"twitter.tar.gz","4":"twitter.tar.gz","src_id":"6952","5":"6952","creation_date":"1175771545","6":"1175771545"}]},"1852":{"script_id":"1852","0":"1852","script_name":"clarity.vim","1":"clarity.vim","script_type":"color scheme","2":"color scheme","summary":"Yet another color scheme with a dark blue background","3":"Yet another color scheme with a dark blue background","description":"Yet another color scheme with a dark blue background. Has good syntax highlighting. I have found it to be easy on the eyes for long hours of looking at code. Has been written for gvim.","4":"Yet another color scheme with a dark blue background. Has good syntax highlighting. I have found it to be easy on the eyes for long hours of looking at code. Has been written for gvim.","install_details":"copy clarity.vim to $HOME\/.vim\/colors\r\nOpen gvim and type \":color clarity\" ","5":"copy clarity.vim to $HOME\/.vim\/colors\r\nOpen gvim and type \":color clarity\" ","first_name":"Dinesh","6":"Dinesh","last_name":".","7":".","releases":[{"0":"1852","vim_version":"6.0","1":"6.0","script_version":"2.2","2":"2.2","version_comment":"Better highlighting for vimdiffs.\r\nMisc. changes","3":"Better highlighting for vimdiffs.\r\nMisc. changes","package":"clarity.vim","4":"clarity.vim","src_id":"7316","5":"7316","creation_date":"1183397586","6":"1183397586"},{"0":"1852","vim_version":"6.0","1":"6.0","script_version":"2.1","2":"2.1","version_comment":"Minor color changes.","3":"Minor color changes.","package":"clarity.vim","4":"clarity.vim","src_id":"7034","5":"7034","creation_date":"1177692010","6":"1177692010"},{"0":"1852","vim_version":"6.0","1":"6.0","script_version":"2.0","2":"2.0","version_comment":"* Changed to a slightly darker background.\r\n* Other minor color changes.","3":"* Changed to a slightly darker background.\r\n* Other minor color changes.","package":"clarity.vim","4":"clarity.vim","src_id":"6965","5":"6965","creation_date":"1176116564","6":"1176116564"},{"0":"1852","vim_version":"6.0","1":"6.0","script_version":"1.2","2":"1.2","version_comment":"Tweaked background color.","3":"Tweaked background color.","package":"clarity.vim","4":"clarity.vim","src_id":"6953","5":"6953","creation_date":"1175774359","6":"1175774359"},{"0":"1852","vim_version":"6.0","1":"6.0","script_version":"1.1","2":"1.1","version_comment":"Minor changes for syntax highlighting .","3":"Minor changes for syntax highlighting .","package":"clarity.vim","4":"clarity.vim","src_id":"6947","5":"6947","creation_date":"1175709807","6":"1175709807"}]},"1851":{"script_id":"1851","0":"1851","script_name":"SearchSyntaxError","1":"SearchSyntaxError","script_type":"utility","2":"utility","summary":"search for the next syntax error detected by the vim highlighting mechanism","3":"search for the next syntax error detected by the vim highlighting mechanism","description":"\" This scritp searches for the next syntax error detected by the vim highlighting\r\n\" mechanism. To search for the next syntax error, issue command\r\n\"       :ERR\r\n\" That all, folks.\r\n\"\r\n\" You can map this :ERR to your favorite key or key combination as follows:\r\n\"\r\n\"    noremap <silent><C-K><C-E>  :ERR<cr>\r\n\"\r\n\" For feedback, bugs and wishes: write to: iler.ml at gmail.com\r\n\"\r\n\" As a bonus, :ERRP searches backwards for the syntax error.\r\n\" And <Ctrl-K><Ctrl-E> is mapped to :ERR, unless somebody redefined it(\r\n\" (your vimrc or some other plugin).","4":"\" This scritp searches for the next syntax error detected by the vim highlighting\r\n\" mechanism. To search for the next syntax error, issue command\r\n\"       :ERR\r\n\" That all, folks.\r\n\"\r\n\" You can map this :ERR to your favorite key or key combination as follows:\r\n\"\r\n\"    noremap <silent><C-K><C-E>  :ERR<cr>\r\n\"\r\n\" For feedback, bugs and wishes: write to: iler.ml at gmail.com\r\n\"\r\n\" As a bonus, :ERRP searches backwards for the syntax error.\r\n\" And <Ctrl-K><Ctrl-E> is mapped to :ERR, unless somebody redefined it(\r\n\" (your vimrc or some other plugin).","install_details":"Short instructions: drop script into your personal plugin\r\ndirectory (~\/.vim\/plugin). Restart vim. Or source the script directly.\r\n\r\nDetailed version:\r\n\r\n1. Download script SearchSyntaxError.vim from the link below.\r\n2. Create directory ~\/.vim\/plugin if it does not exist:\r\n                 mkdir -p ~\/.vim\/plugin\r\n   (your personal plugin directory).\r\n3. Copy script SearchSyntaxError.vim into ~\/.vim\/plugin directory.\r\n4. Restart vim\r\n\r\n","5":"Short instructions: drop script into your personal plugin\r\ndirectory (~\/.vim\/plugin). Restart vim. Or source the script directly.\r\n\r\nDetailed version:\r\n\r\n1. Download script SearchSyntaxError.vim from the link below.\r\n2. Create directory ~\/.vim\/plugin if it does not exist:\r\n                 mkdir -p ~\/.vim\/plugin\r\n   (your personal plugin directory).\r\n3. Copy script SearchSyntaxError.vim into ~\/.vim\/plugin directory.\r\n4. Restart vim\r\n\r\n","first_name":"Yakov","6":"Yakov","last_name":"Lerner","7":"Lerner","releases":[{"0":"1851","vim_version":"6.0","1":"6.0","script_version":"070404b","2":"070404b","version_comment":"added URL at www.vim.org\/scripts. Checksum 36635136","3":"added URL at www.vim.org\/scripts. Checksum 36635136","package":"SearchSyntaxError.vim","4":"SearchSyntaxError.vim","src_id":"6944","5":"6944","creation_date":"1175666151","6":"1175666151"}]},"1850":{"script_id":"1850","0":"1850","script_name":"carrot.vim","1":"carrot.vim","script_type":"color scheme","2":"color scheme","summary":"My color scheme based on \"PeachPuff\" color scheme","3":"My color scheme based on \"PeachPuff\" color scheme","description":"* My color scheme based on the \"PeachPuff\" color scheme\r\n* Works only for gvim","4":"* My color scheme based on the \"PeachPuff\" color scheme\r\n* Works only for gvim","install_details":"1. Add carrot.vim to $HOME\/.vim\/colors\/\r\n2. Open gvim and type: \":color carrot\"","5":"1. Add carrot.vim to $HOME\/.vim\/colors\/\r\n2. Open gvim and type: \":color carrot\"","first_name":"Dinesh","6":"Dinesh","last_name":".","7":".","releases":[{"0":"1850","vim_version":"6.0","1":"6.0","script_version":"2.0","2":"2.0","version_comment":"Added more shades of carrot color.","3":"Added more shades of carrot color.","package":"carrot.vim","4":"carrot.vim","src_id":"7602","5":"7602","creation_date":"1188556871","6":"1188556871"},{"0":"1850","vim_version":"6.0","1":"6.0","script_version":"1.1","2":"1.1","version_comment":"Minor tweaks","3":"Minor tweaks","package":"carrot.vim","4":"carrot.vim","src_id":"7335","5":"7335","creation_date":"1183981555","6":"1183981555"},{"0":"1850","vim_version":"6.0","1":"6.0","script_version":"1","2":"1","version_comment":"Initial upload","3":"Initial upload","package":"carrot.vim","4":"carrot.vim","src_id":"6941","5":"6941","creation_date":"1175602537","6":"1175602537"}]},"1849":{"script_id":"1849","0":"1849","script_name":"AutoClose","1":"AutoClose","script_type":"utility","2":"utility","summary":"Inserts matching bracket, paren, brace or quote","3":"Inserts matching bracket, paren, brace or quote","description":"There are very simple ways to insert a closing brace by setting up a few mappings. The problem with all these approaches is that they break undo, history or both. This script is my sixth attempt at correcting this problem and the first one that has worked in all scenarios.\r\n\r\nUsing this script, typing ``(`` will result in (|), where | is the cursor position and the double backticks are just marking input. Typing a ``)`` will move the cursor outside the parens. This moving outside works even in nested scenarios. Typing ``if(my_array['key`` results in if(my_array['key|']) and ``)`` gets you if(my_array['key'])|.\r\n\r\nThe paired characters are: [, (, {, \", '\r\n\r\nIf you like this script, you should also check out surround.vim","4":"There are very simple ways to insert a closing brace by setting up a few mappings. The problem with all these approaches is that they break undo, history or both. This script is my sixth attempt at correcting this problem and the first one that has worked in all scenarios.\r\n\r\nUsing this script, typing ``(`` will result in (|), where | is the cursor position and the double backticks are just marking input. Typing a ``)`` will move the cursor outside the parens. This moving outside works even in nested scenarios. Typing ``if(my_array['key`` results in if(my_array['key|']) and ``)`` gets you if(my_array['key'])|.\r\n\r\nThe paired characters are: [, (, {, \", '\r\n\r\nIf you like this script, you should also check out surround.vim","install_details":"","5":"","first_name":"Karl","6":"Karl","last_name":"Guertin","7":"Guertin","releases":[{"0":"1849","vim_version":"6.0","1":"6.0","script_version":"1.2","2":"1.2","version_comment":"Fixed all known bugs (finally). Typing a closing character will now consistently jump out of a match at all times.","3":"Fixed all known bugs (finally). Typing a closing character will now consistently jump out of a match at all times.","package":"autoclose.vim","4":"autoclose.vim","src_id":"10873","5":"10873","creation_date":"1245374047","6":"1245374047"},{"0":"1849","vim_version":"7.0","1":"7.0","script_version":"1.1.2","2":"1.1.2","version_comment":"Fixes a rather nasty bug that sometimes deletes closing chars on the same line. Add double brace auto-indent. 1.1.2 contains fixes for a mapping typo and auto-indent edge case.","3":"Fixes a rather nasty bug that sometimes deletes closing chars on the same line. Add double brace auto-indent. 1.1.2 contains fixes for a mapping typo and auto-indent edge case.","package":"autoclose.vim","4":"autoclose.vim","src_id":"7700","5":"7700","creation_date":"1190302564","6":"1190302564"},{"0":"1849","vim_version":"7.0","1":"7.0","script_version":"1.0.1","2":"1.0.1","version_comment":"Knew I shouldn't have uploaded the first version as 1.0","3":"Knew I shouldn't have uploaded the first version as 1.0","package":"autoclose.vim","4":"autoclose.vim","src_id":"6940","5":"6940","creation_date":"1175572142","6":"1175572142"}]},"1848":{"script_id":"1848","0":"1848","script_name":"arpalert","1":"arpalert","script_type":"syntax","2":"syntax","summary":"arpalert syntax file","3":"arpalert syntax file","description":"Arpalert is a daemon used for monitoring ethernet networks. See http:\/\/www.arpalert.org\/ for more details.","4":"Arpalert is a daemon used for monitoring ethernet networks. See http:\/\/www.arpalert.org\/ for more details.","install_details":"Copy the arpalert.vim file to $HOME\/.vim\/syntax\/ and add the following to your vimrc:\r\nau BufRead,BufNewFile arpalert* set ft=arpalert","5":"Copy the arpalert.vim file to $HOME\/.vim\/syntax\/ and add the following to your vimrc:\r\nau BufRead,BufNewFile arpalert* set ft=arpalert","first_name":"Bruno","6":"Bruno","last_name":"Michel","7":"Michel","releases":[{"0":"1848","vim_version":"7.0","1":"7.0","script_version":"0.2","2":"0.2","version_comment":"Initial upload","3":"Initial upload","package":"arpalert.vim","4":"arpalert.vim","src_id":"6932","5":"6932","creation_date":"1175477607","6":"1175477607"}]},"1847":{"script_id":"1847","0":"1847","script_name":"NesC Syntax Highlighting","1":"NesC Syntax Highlighting","script_type":"syntax","2":"syntax","summary":"The Syntax Highlighting for NesC Files","3":"The Syntax Highlighting for NesC Files","description":"nesC is an extension to the C programming language designed to embody the structuring concepts and execution model of TinyOS. TinyOS is an event-driven operating system designed for sensor network nodes that have very limited resources.\r\nThis script is the Syntax Highlighting for the programming files written in NesC.\r\nDetailed can found from here: http:\/\/www.amingsite.info\/aming\/archives\/?arch=vi_nesc","4":"nesC is an extension to the C programming language designed to embody the structuring concepts and execution model of TinyOS. TinyOS is an event-driven operating system designed for sensor network nodes that have very limited resources.\r\nThis script is the Syntax Highlighting for the programming files written in NesC.\r\nDetailed can found from here: http:\/\/www.amingsite.info\/aming\/archives\/?arch=vi_nesc","install_details":"Version 1.0\r\nMake a folder for the script if not existed\r\nmkdir ~\/.vim\/syntax\r\nput the script in ~\/.vim\/syntax\r\nadd the following into the end of ~\/.vimrc\r\naugroup filetypedetect\r\n  au! BufRead,BufNewFile *nc setfiletype nc\r\naugroup END\r\n\r\nVersion 2.0\r\nuntar the the files to ~\/.vim\/\r\ntar zxvf vim.tar.gz\r\nadd the following into the end of ~\/.vimrc\r\naugroup filetypedetect\r\n  au! BufRead,BufNewFile *nc setfiletype nc\r\naugroup END","5":"Version 1.0\r\nMake a folder for the script if not existed\r\nmkdir ~\/.vim\/syntax\r\nput the script in ~\/.vim\/syntax\r\nadd the following into the end of ~\/.vimrc\r\naugroup filetypedetect\r\n  au! BufRead,BufNewFile *nc setfiletype nc\r\naugroup END\r\n\r\nVersion 2.0\r\nuntar the the files to ~\/.vim\/\r\ntar zxvf vim.tar.gz\r\nadd the following into the end of ~\/.vimrc\r\naugroup filetypedetect\r\n  au! BufRead,BufNewFile *nc setfiletype nc\r\naugroup END","first_name":"Ming Leong","6":"Ming Leong","last_name":"Lau","7":"Lau","releases":[{"0":"1847","vim_version":"6.0","1":"6.0","script_version":"2.0","2":"2.0","version_comment":"Add the file for the function of indentation","3":"Add the file for the function of indentation","package":"vim.tar.gz","4":"vim.tar.gz","src_id":"6935","5":"6935","creation_date":"1175526128","6":"1175526128"},{"0":"1847","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"nc.vim","4":"nc.vim","src_id":"6929","5":"6929","creation_date":"1175419094","6":"1175419094"}]},"1846":{"script_id":"1846","0":"1846","script_name":"gitdiff.vim","1":"gitdiff.vim","script_type":"utility","2":"utility","summary":"show git diff in a split window","3":"show git diff in a split window","description":"This script provides two functions to display git diffs in vim.\r\n\r\n:GITDiff [commitish]\r\n\r\n    Split the vim window vertically, display the HEAD, or some other changeset, version of the file in the split, then diff them.\r\n\r\n:GITChanges [commitish]\r\n\r\n    Highlight lines that were changed since the HEAD or some other changeset.\r\n\r\nSome examples:\r\n\r\n:GITDiff HEAD~10\r\n:diffoff\r\n\r\n:GITChanges origin\/master\r\n:syntax on","4":"This script provides two functions to display git diffs in vim.\r\n\r\n:GITDiff [commitish]\r\n\r\n    Split the vim window vertically, display the HEAD, or some other changeset, version of the file in the split, then diff them.\r\n\r\n:GITChanges [commitish]\r\n\r\n    Highlight lines that were changed since the HEAD or some other changeset.\r\n\r\nSome examples:\r\n\r\n:GITDiff HEAD~10\r\n:diffoff\r\n\r\n:GITChanges origin\/master\r\n:syntax on","install_details":"1. grab vimball (vimscript#1502) then:\r\n2. vim gitdiff.vba\r\n   :so %\r\n   :q","5":"1. grab vimball (vimscript#1502) then:\r\n2. vim gitdiff.vba\r\n   :so %\r\n   :q","first_name":"Bart","6":"Bart","last_name":"Trojanowski","7":"Trojanowski","releases":[{"0":"1846","vim_version":"6.0","1":"6.0","script_version":"2","2":"2","version_comment":"Needs vimball plugin (vimscript#1502)\r\nMerged in vimscript#1881 to show changed lines.","3":"Needs vimball plugin (vimscript#1502)\r\nMerged in vimscript#1881 to show changed lines.","package":"gitdiff.vba","4":"gitdiff.vba","src_id":"7059","5":"7059","creation_date":"1178129834","6":"1178129834"},{"0":"1846","vim_version":"6.0","1":"6.0","script_version":"0.0","2":"0.0","version_comment":"Initial upload","3":"Initial upload","package":"gitdiff.vim","4":"gitdiff.vim","src_id":"6925","5":"6925","creation_date":"1175283704","6":"1175283704"}]},"1845":{"script_id":"1845","0":"1845","script_name":"haproxy","1":"haproxy","script_type":"syntax","2":"syntax","summary":"syntax for haproxy","3":"syntax for haproxy","description":"HAProxy is a free, very fast and reliable solution offering high availability, load balancing, and proxying for TCP and HTTP-based applications. It is particularly suited for web sites crawling under very high loads while needing persistence or Layer7 processing.\r\n\r\nFor more details, see http:\/\/haproxy.1wt.eu\/.","4":"HAProxy is a free, very fast and reliable solution offering high availability, load balancing, and proxying for TCP and HTTP-based applications. It is particularly suited for web sites crawling under very high loads while needing persistence or Layer7 processing.\r\n\r\nFor more details, see http:\/\/haproxy.1wt.eu\/.","install_details":"Copy the haproxy.vim file to $HOME\/.vim\/syntax\/ and add the following to your vimrc:\r\nau BufRead,BufNewFile haproxy* set ft=haproxy\r\n","5":"Copy the haproxy.vim file to $HOME\/.vim\/syntax\/ and add the following to your vimrc:\r\nau BufRead,BufNewFile haproxy* set ft=haproxy\r\n","first_name":"Bruno","6":"Bruno","last_name":"Michel","7":"Michel","releases":[{"0":"1845","vim_version":"7.0","1":"7.0","script_version":"0.3","2":"0.3","version_comment":"Initial upload","3":"Initial upload","package":"haproxy.vim","4":"haproxy.vim","src_id":"6924","5":"6924","creation_date":"1175256141","6":"1175256141"}]},"1844":{"script_id":"1844","0":"1844","script_name":"OceanBlack256","1":"OceanBlack256","script_type":"color scheme","2":"color scheme","summary":"OceanBlack color scheme for a 256 color terminal.","3":"OceanBlack color scheme for a 256 color terminal.","description":"This color scheme based on Chris Vertonghen\u00e2\u0080\u0099s Ocean Black color scheme. It is basically a conversion using dither.pl a Perl script I wrote to convert schemes to 256 xterm. \r\n\r\nSee the link bellow for some screen shots of what it looks like with Vim script, Java and C++ as well as the Perl source code for dither.pl.\r\n\r\nhttp:\/\/juan.boxfi.com\/vim-color-schemes\/#oceanblack256 \r\n\r\nWhen sending questions or comments please keep in mind that this theme will not work on 8\/16 color terminals and I have not tested it in 88 color terminals. Also I am not in any way a unix\/linux expert and had to endure many headaches recompiling Vim and messing with TERMCap settings trying to get the 256 term to work ","4":"This color scheme based on Chris Vertonghen\u00e2\u0080\u0099s Ocean Black color scheme. It is basically a conversion using dither.pl a Perl script I wrote to convert schemes to 256 xterm. \r\n\r\nSee the link bellow for some screen shots of what it looks like with Vim script, Java and C++ as well as the Perl source code for dither.pl.\r\n\r\nhttp:\/\/juan.boxfi.com\/vim-color-schemes\/#oceanblack256 \r\n\r\nWhen sending questions or comments please keep in mind that this theme will not work on 8\/16 color terminals and I have not tested it in 88 color terminals. Also I am not in any way a unix\/linux expert and had to endure many headaches recompiling Vim and messing with TERMCap settings trying to get the 256 term to work ","install_details":"","5":"","first_name":"Juan","6":"Juan","last_name":"Frias","7":"Frias","releases":[{"0":"1844","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"oceanblack256.vim","4":"oceanblack256.vim","src_id":"6922","5":"6922","creation_date":"1175247630","6":"1175247630"}]},"1843":{"script_id":"1843","0":"1843","script_name":"jman.vim","1":"jman.vim","script_type":"ftplugin","2":"ftplugin","summary":"Initial upload","3":"Initial upload","description":"* About\r\n\r\nThs \"jman.vim\" plugin is jman browser plugin for vim and jman user.\r\nJman is \"on-line manual pages for japanese\".\r\nJman is seen so that you may just use man.vim for man.\r\n\r\n* Need \"jman\" command.\r\n\r\nIt need \"jman\" command!\r\nIf you use FreeBSD, you can install jman program as root user,\r\n\r\n   cd \/usr\/ports\/japanese\/man && make install clean\r\n\r\njman.vim use \/usr\/local\/bin\/jman.\r\n\r\n* Usage\r\n\r\nIf you want to know ls(1), you can type following command.\r\n:Jman ls\r\n\r\nWant to know printf(3)\r\n:Jman 3 printf\r\n\r\n\r\n* see also\r\n\r\n- \/usr\/local\/share\/vim\/vim*\/ftplugin\/man.vim\r\n","4":"* About\r\n\r\nThs \"jman.vim\" plugin is jman browser plugin for vim and jman user.\r\nJman is \"on-line manual pages for japanese\".\r\nJman is seen so that you may just use man.vim for man.\r\n\r\n* Need \"jman\" command.\r\n\r\nIt need \"jman\" command!\r\nIf you use FreeBSD, you can install jman program as root user,\r\n\r\n   cd \/usr\/ports\/japanese\/man && make install clean\r\n\r\njman.vim use \/usr\/local\/bin\/jman.\r\n\r\n* Usage\r\n\r\nIf you want to know ls(1), you can type following command.\r\n:Jman ls\r\n\r\nWant to know printf(3)\r\n:Jman 3 printf\r\n\r\n\r\n* see also\r\n\r\n- \/usr\/local\/share\/vim\/vim*\/ftplugin\/man.vim\r\n","install_details":"1. Download the jman.vim script file.\r\n2. And copy to the $HOME\/.vim\/ftplugin directory.\r\n\r\n# version 1.0\r\n mkdir -p $HOME\/.vim\/ftplugin\/\r\n fetch -o $HOME\/.vim\/ftplugin\/jman.vim 'http:\/\/www.vim.org\/scripts\/download_script.php?src_id=6920'\r\n","5":"1. Download the jman.vim script file.\r\n2. And copy to the $HOME\/.vim\/ftplugin directory.\r\n\r\n# version 1.0\r\n mkdir -p $HOME\/.vim\/ftplugin\/\r\n fetch -o $HOME\/.vim\/ftplugin\/jman.vim 'http:\/\/www.vim.org\/scripts\/download_script.php?src_id=6920'\r\n","first_name":"kaoru","6":"kaoru","last_name":"toda","7":"toda","releases":[{"0":"1843","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"jman.vim","4":"jman.vim","src_id":"6920","5":"6920","creation_date":"1175160898","6":"1175160898"}]},"1842":{"script_id":"1842","0":"1842","script_name":"screenplay","1":"screenplay","script_type":"ftplugin","2":"ftplugin","summary":"A filetype plugin to enable easy screenplay writing","3":"A filetype plugin to enable easy screenplay writing","description":"Vim plugin to assist in writing screenplays compatible with \r\nthe trelby plaintext screenplay format.\r\n\r\n\r\nFor plaintext screenplays that actually look like screenplays.\r\n\r\n\r\nFeatures\r\n=======\r\n\r\n * The tab button and the backspace button have been modified to go\r\n   backwards and forwards in helpful chunks \r\n\r\n * Good margins for ACTION and DIALOG\r\n\r\n * Control-p will format a paragraph from under the cursor\r\n    downwards, relative to the (textwidth) margin\r\n\r\n * Tab complete character names\r\n  \r\n * Hitting enter after DIALOG should align for a new character name \r\n","4":"Vim plugin to assist in writing screenplays compatible with \r\nthe trelby plaintext screenplay format.\r\n\r\n\r\nFor plaintext screenplays that actually look like screenplays.\r\n\r\n\r\nFeatures\r\n=======\r\n\r\n * The tab button and the backspace button have been modified to go\r\n   backwards and forwards in helpful chunks \r\n\r\n * Good margins for ACTION and DIALOG\r\n\r\n * Control-p will format a paragraph from under the cursor\r\n    downwards, relative to the (textwidth) margin\r\n\r\n * Tab complete character names\r\n  \r\n * Hitting enter after DIALOG should align for a new character name \r\n","install_details":"* Drop this screenplay.vim file in your ${VIMRUNTIME}\/ftplugin\/ directory\r\n* ensure your instance of vim has these options enabled:\r\n  :filetype on\r\n  :filetype plugin on\r\n  :au BufRead,BufNewFile *.screenplay    set filetype=screenplay\r\n* Ensure the suffix of the file you are editing is .screenplay and away you\r\n  go!\r\n","5":"* Drop this screenplay.vim file in your ${VIMRUNTIME}\/ftplugin\/ directory\r\n* ensure your instance of vim has these options enabled:\r\n  :filetype on\r\n  :filetype plugin on\r\n  :au BufRead,BufNewFile *.screenplay    set filetype=screenplay\r\n* Ensure the suffix of the file you are editing is .screenplay and away you\r\n  go!\r\n","first_name":"Alex","6":"Alex","last_name":"Lance","7":"Lance","releases":[{"0":"1842","vim_version":"7.0","1":"7.0","script_version":"0.9","2":"0.9","version_comment":"Updated it to work more harmoniously with trelby's plaintext format","3":"Updated it to work more harmoniously with trelby's plaintext format","package":"screenplay.vim","4":"screenplay.vim","src_id":"22353","5":"22353","creation_date":"1408513143","6":"1408513143"},{"0":"1842","vim_version":"7.0","1":"7.0","script_version":"0.8","2":"0.8","version_comment":"Initial upload","3":"Initial upload","package":"screenplay.vim","4":"screenplay.vim","src_id":"6919","5":"6919","creation_date":"1175135814","6":"1175135814"}]},"1841":{"script_id":"1841","0":"1841","script_name":"nicotine.vim","1":"nicotine.vim","script_type":"color scheme","2":"color scheme","summary":"Light and simple color scheme for Gvim","3":"Light and simple color scheme for Gvim","description":"This is in fact a slightly customed version of lingodirector colorscheme\r\n(vimscript #1012) by Thomas Schmall.\r\n\r\nThis is a GUI version just for now.\r\n\r\nThanks:\r\nThomas Schmall for a great color scheme (lingodirector.vim) and\r\nBram Moolenaar et al. for the gem that is Vim.","4":"This is in fact a slightly customed version of lingodirector colorscheme\r\n(vimscript #1012) by Thomas Schmall.\r\n\r\nThis is a GUI version just for now.\r\n\r\nThanks:\r\nThomas Schmall for a great color scheme (lingodirector.vim) and\r\nBram Moolenaar et al. for the gem that is Vim.","install_details":"Just drop the file in $VIMRUNTIME\/colors\/\r\nOn the command line, type :colo nicotine\r\n\r\n","5":"Just drop the file in $VIMRUNTIME\/colors\/\r\nOn the command line, type :colo nicotine\r\n\r\n","first_name":"Tuomas","6":"Tuomas","last_name":"Kasmra","7":"Kasmra","releases":[{"0":"1841","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"nicotine.vim","4":"nicotine.vim","src_id":"6915","5":"6915","creation_date":"1175070007","6":"1175070007"}]},"1840":{"script_id":"1840","0":"1840","script_name":"Javascript Indentation","1":"Javascript Indentation","script_type":"indent","2":"indent","summary":"Indentation for Javascript","3":"Indentation for Javascript","description":"Yes, Javascript has similarities to C, but it is a more flexible syntax, with constructs that are not handled by cindent().  And they shouldn't be, since it's not really C.\r\n\r\nThis script requires the IndentAnything plugin.\r\n\r\nFeedback is welcome.","4":"Yes, Javascript has similarities to C, but it is a more flexible syntax, with constructs that are not handled by cindent().  And they shouldn't be, since it's not really C.\r\n\r\nThis script requires the IndentAnything plugin.\r\n\r\nFeedback is welcome.","install_details":"Place in ~\/.vim\/indent.","5":"Place in ~\/.vim\/indent.","first_name":"Tye","6":"Tye","last_name":"Zdrojewski","7":"Zdrojewski","releases":[{"0":"1840","vim_version":"7.0","1":"7.0","script_version":"1.1.3","2":"1.1.3","version_comment":"Fixed silly syntax error.  Shame on me...","3":"Fixed silly syntax error.  Shame on me...","package":"javascript.vim","4":"javascript.vim","src_id":"11838","5":"11838","creation_date":"1259725693","6":"1259725693"},{"0":"1840","vim_version":"7.0","1":"7.0","script_version":"1.1.2","2":"1.1.2","version_comment":"Added support for brackets ('[...]')","3":"Added support for brackets ('[...]')","package":"javascript.vim","4":"javascript.vim","src_id":"11824","5":"11824","creation_date":"1259473850","6":"1259473850"},{"0":"1840","vim_version":"7.0","1":"7.0","script_version":"1.1.1","2":"1.1.1","version_comment":"Added copywrite \/ Apache2 license","3":"Added copywrite \/ Apache2 license","package":"javascript.vim","4":"javascript.vim","src_id":"7860","5":"7860","creation_date":"1193952878","6":"1193952878"},{"0":"1840","vim_version":"7.0","1":"7.0","script_version":"1.1","2":"1.1","version_comment":"Fixed issue with extra indentation in switch statements.","3":"Fixed issue with extra indentation in switch statements.","package":"javascript.vim","4":"javascript.vim","src_id":"6918","5":"6918","creation_date":"1175112084","6":"1175112084"},{"0":"1840","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"javascript.vim","4":"javascript.vim","src_id":"6910","5":"6910","creation_date":"1175000385","6":"1175000385"}]},"1839":{"script_id":"1839","0":"1839","script_name":"IndentAnything","1":"IndentAnything","script_type":"indent","2":"indent","summary":"Write indentations or enhance existing indentations without writing code","3":"Write indentations or enhance existing indentations without writing code","description":"The IndentAnything plugin is intended to make it easier to write new indentation scripts and\/or supplement existing ones.  It makes the assumption that all indentable languages have similar characteristics:\r\n\r\n\t- blocks of code or text over multiple lines\r\n\t- continuation lines\r\n\t- comments\r\n\r\nThe rules of indentation are specified in a series of variables.  Explanation is provided in the included doc\/IndentAnything.txt help file.\r\n\r\nAn example HTML indentation enhancement is also included.","4":"The IndentAnything plugin is intended to make it easier to write new indentation scripts and\/or supplement existing ones.  It makes the assumption that all indentable languages have similar characteristics:\r\n\r\n\t- blocks of code or text over multiple lines\r\n\t- continuation lines\r\n\t- comments\r\n\r\nThe rules of indentation are specified in a series of variables.  Explanation is provided in the included doc\/IndentAnything.txt help file.\r\n\r\nAn example HTML indentation enhancement is also included.","install_details":"cd ~\/.vim\r\ntar zxvf IndentAnything.tar.gz\r\n\r\nIf you want the help to be searchable:\r\n:helptags ~\/.vim\/doc","5":"cd ~\/.vim\r\ntar zxvf IndentAnything.tar.gz\r\n\r\nIf you want the help to be searchable:\r\n:helptags ~\/.vim\/doc","first_name":"Tye","6":"Tye","last_name":"Zdrojewski","7":"Zdrojewski","releases":[{"0":"1839","vim_version":"7.0","1":"7.0","script_version":"1.2.2","2":"1.2.2","version_comment":"Bug fix and backed off version 1.3","3":"Bug fix and backed off version 1.3","package":"IndentAnything.tar.gz","4":"IndentAnything.tar.gz","src_id":"10228","5":"10228","creation_date":"1237239055","6":"1237239055"},{"0":"1839","vim_version":"7.0","1":"7.0","script_version":"1.2.1","2":"1.2.1","version_comment":"Added Apache2 license and test file.","3":"Added Apache2 license and test file.","package":"IndentAnything.tar.gz","4":"IndentAnything.tar.gz","src_id":"7859","5":"7859","creation_date":"1193952467","6":"1193952467"},{"0":"1839","vim_version":"7.0","1":"7.0","script_version":"1.2","2":"1.2","version_comment":"Fixed an issue with block comments being improperly affected by line continuations.","3":"Fixed an issue with block comments being improperly affected by line continuations.","package":"IndentAnything.tar.gz","4":"IndentAnything.tar.gz","src_id":"6979","5":"6979","creation_date":"1176655072","6":"1176655072"},{"0":"1839","vim_version":"7.0","1":"7.0","script_version":"1.1","2":"1.1","version_comment":"Not a functional change.  Changed a bad example in documentation.","3":"Not a functional change.  Changed a bad example in documentation.","package":"IndentAnything.tar.gz","4":"IndentAnything.tar.gz","src_id":"6917","5":"6917","creation_date":"1175111957","6":"1175111957"},{"0":"1839","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"IndentAnything.tar.gz","4":"IndentAnything.tar.gz","src_id":"6909","5":"6909","creation_date":"1174999721","6":"1174999721"}]},"1838":{"script_id":"1838","0":"1838","script_name":"tEchoPair","1":"tEchoPair","script_type":"utility","2":"utility","summary":"Display the matching parenthesis\/pair in the echo area","3":"Display the matching parenthesis\/pair in the echo area","description":"VIM is an excellent editor but in comparison too e.g. emacs it lacks a \r\nminor feature that makes editing lisp code somewhat cumbersome. While \r\nVIM can highlight the matching parenthesis, this doesn't help much with \r\nlong functions when the matching parenthesis is off the screen. \r\nEmacs users are better off in such a situation, since emace displays the \r\nmatching line in the echo area.\r\n\r\nThis plugin tries to mimic Emacs's behaviour. Whenever the cursor is \r\nplaced over a parenthesis or an element of a pair the matching element is \r\ndisplayed in the echo area. If 'cmdheight' is set to a value greater \r\nthan 1, additional context lines are displayed, too.\r\n\r\n\r\nIn order to enable this plugin, you choose between the following  \r\noptions:\r\n    TEchoPairInstallBuffer ... enable for the current buffer\r\n\r\n    call TEchoPairInstall('*') ... enable globally\r\n\r\n    let g:tEchoPairInstall = ['lisp', 'scheme'] ... enable for certain \r\n      filetypes\r\n\r\n\r\nCurrently, there are the following display modes:\r\n    indicate ... Display the whole line and highlight the matching \r\n      parenthesis. If 'cmdheight' is greater than 1, additional lines \r\n      are display.\r\n\r\n    inner ... Display the inner text Emacs-style.\r\n\r\nIn order to see the matching parenthesis when 'showmode' is on, set \r\n'cmdheight' to something greater than 1.\r\n\r\nYou can select the preferred display mode on a filetype basis, by \r\nsetting g:tEchoPairStyle_{STYLE}.\r\n\r\nExample:\r\n    let g:tEchoPairStyle_inner = ['lisp', 'scheme']\r\n    let g:tEchoPairStyle_indicate = ['java']\r\n\r\n\r\nThe pairs are usually deduced from the value of 'matchpairs' unless \r\nthere is an entry for the current buffer's filetype in g:tEchoPairs. For \r\nthe following filetypes custom pairs are pre-defined:\r\n    - ruby\r\n    - vim\r\n\r\nBUT: It actually only works for lisp-like languages.\r\n","4":"VIM is an excellent editor but in comparison too e.g. emacs it lacks a \r\nminor feature that makes editing lisp code somewhat cumbersome. While \r\nVIM can highlight the matching parenthesis, this doesn't help much with \r\nlong functions when the matching parenthesis is off the screen. \r\nEmacs users are better off in such a situation, since emace displays the \r\nmatching line in the echo area.\r\n\r\nThis plugin tries to mimic Emacs's behaviour. Whenever the cursor is \r\nplaced over a parenthesis or an element of a pair the matching element is \r\ndisplayed in the echo area. If 'cmdheight' is set to a value greater \r\nthan 1, additional context lines are displayed, too.\r\n\r\n\r\nIn order to enable this plugin, you choose between the following  \r\noptions:\r\n    TEchoPairInstallBuffer ... enable for the current buffer\r\n\r\n    call TEchoPairInstall('*') ... enable globally\r\n\r\n    let g:tEchoPairInstall = ['lisp', 'scheme'] ... enable for certain \r\n      filetypes\r\n\r\n\r\nCurrently, there are the following display modes:\r\n    indicate ... Display the whole line and highlight the matching \r\n      parenthesis. If 'cmdheight' is greater than 1, additional lines \r\n      are display.\r\n\r\n    inner ... Display the inner text Emacs-style.\r\n\r\nIn order to see the matching parenthesis when 'showmode' is on, set \r\n'cmdheight' to something greater than 1.\r\n\r\nYou can select the preferred display mode on a filetype basis, by \r\nsetting g:tEchoPairStyle_{STYLE}.\r\n\r\nExample:\r\n    let g:tEchoPairStyle_inner = ['lisp', 'scheme']\r\n    let g:tEchoPairStyle_indicate = ['java']\r\n\r\n\r\nThe pairs are usually deduced from the value of 'matchpairs' unless \r\nthere is an entry for the current buffer's filetype in g:tEchoPairs. For \r\nthe following filetypes custom pairs are pre-defined:\r\n    - ruby\r\n    - vim\r\n\r\nBUT: It actually only works for lisp-like languages.\r\n","install_details":"Copy to ~\/.vim\/plugin\/\r\n\r\n\r\nAlso available via git\r\nhttp:\/\/github.com\/tomtom\/vimtlib\/tree\/master\r\n","5":"Copy to ~\/.vim\/plugin\/\r\n\r\n\r\nAlso available via git\r\nhttp:\/\/github.com\/tomtom\/vimtlib\/tree\/master\r\n","first_name":"Tom","6":"Tom","last_name":"Link","7":"Link","releases":[{"0":"1838","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"tEchoPair.vim","4":"tEchoPair.vim","src_id":"6907","5":"6907","creation_date":"1174992472","6":"1174992472"}]},"1837":{"script_id":"1837","0":"1837","script_name":"BlitzBasic syntax and indentation","1":"BlitzBasic syntax and indentation","script_type":"indent","2":"indent","summary":"Syntax highlighting and indentation for BlitzBasic.","3":"Syntax highlighting and indentation for BlitzBasic.","description":"These two scripts provide syntax highlighting and automatic code indentation for BlitzBasic code. Supported are the Blitz2D and Blitz3D commandsets.\r\n\r\nPlease note that there's one little bug: I couldn't determine which regular expression to use for if statements to indent correctly. Therefore you always have to write a 'Then' at the end of an if statement - which looks better anyway, in my opinion. ;-) Whatever, if you know how to change the regex to support both versions (with and without 'Then'), feel free to contact me.","4":"These two scripts provide syntax highlighting and automatic code indentation for BlitzBasic code. Supported are the Blitz2D and Blitz3D commandsets.\r\n\r\nPlease note that there's one little bug: I couldn't determine which regular expression to use for if statements to indent correctly. Therefore you always have to write a 'Then' at the end of an if statement - which looks better anyway, in my opinion. ;-) Whatever, if you know how to change the regex to support both versions (with and without 'Then'), feel free to contact me.","install_details":"Extract the archive to your ~\/.vim directory. Add the following lines to your ~\/.vimrc to enable filetype recognition:\r\n\r\naugroup filetypedetect\r\n\tau BufNewFile,BufRead *.bb\tsetf bb\r\naugroup END","5":"Extract the archive to your ~\/.vim directory. Add the following lines to your ~\/.vimrc to enable filetype recognition:\r\n\r\naugroup filetypedetect\r\n\tau BufNewFile,BufRead *.bb\tsetf bb\r\naugroup END","first_name":"Stefan","6":"Stefan","last_name":"Schindler","7":"Schindler","releases":[{"0":"1837","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"bb.tar.gz","4":"bb.tar.gz","src_id":"6905","5":"6905","creation_date":"1174839188","6":"1174839188"}]},"1836":{"script_id":"1836","0":"1836","script_name":"bufpos","1":"bufpos","script_type":"utility","2":"utility","summary":"switch buffer with Alt-<number>","3":"switch buffer with Alt-<number>","description":"This script provides a function to activate a vim buffer by passing it the position in the buffers list and maps it to <M-number> to easily switch between open buffers.\r\n\r\nThis is best used together with the buftabs plugin: http:\/\/www.vim.org\/scripts\/script.php?script_id=1664\r\nAnd even better with my slightly modified version: http:\/\/blog.micampe.it\/articles\/2007\/03\/28\/enhanced-buftabs-vim-plugin\r\n\r\nExplanation here: http:\/\/blog.micampe.it\/articles\/2007\/03\/25\/tabs-in-vim-and-my-first-plugin","4":"This script provides a function to activate a vim buffer by passing it the position in the buffers list and maps it to <M-number> to easily switch between open buffers.\r\n\r\nThis is best used together with the buftabs plugin: http:\/\/www.vim.org\/scripts\/script.php?script_id=1664\r\nAnd even better with my slightly modified version: http:\/\/blog.micampe.it\/articles\/2007\/03\/28\/enhanced-buftabs-vim-plugin\r\n\r\nExplanation here: http:\/\/blog.micampe.it\/articles\/2007\/03\/25\/tabs-in-vim-and-my-first-plugin","install_details":"Download the script and put it in ~\/.vim\/plugins","5":"Download the script and put it in ~\/.vim\/plugins","first_name":"Michele","6":"Michele","last_name":"Campeotto","7":"Campeotto","releases":[{"0":"1836","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"bufpos.vim","4":"bufpos.vim","src_id":"6901","5":"6901","creation_date":"1174823358","6":"1174823358"}]},"1835":{"script_id":"1835","0":"1835","script_name":"RDF Namespace-complete","1":"RDF Namespace-complete","script_type":"utility","2":"utility","summary":"RDF Vocabulary\/Model Omni-Completion for Vim 7+","3":"RDF Vocabulary\/Model Omni-Completion for Vim 7+","description":"In a file with namespace prefix declarations similar to XML, Turtle\/Notation3 or SPARQL, call\r\n\r\n  :RDF\r\n\r\nto turn on completion on terms within a namespace using the preceding prefix. This will load all RDF\/XML and n3-files found in one of the following dirs:\r\n\r\n  - $RDF_MODEL_FILES (environment variable)\r\n  - ~\/rdfmodels\/\r\n  - ~\/Documents\/rdfmodels\/\r\n  - \/usr\/local\/share\/rdfmodels\/\r\n\r\nCall\r\n\r\n  :RDF reload\r\n\r\nto reload model files, and\r\n\r\n  :RDF quit\r\n\r\nto restore the original omnifunc (if any).\r\n","4":"In a file with namespace prefix declarations similar to XML, Turtle\/Notation3 or SPARQL, call\r\n\r\n  :RDF\r\n\r\nto turn on completion on terms within a namespace using the preceding prefix. This will load all RDF\/XML and n3-files found in one of the following dirs:\r\n\r\n  - $RDF_MODEL_FILES (environment variable)\r\n  - ~\/rdfmodels\/\r\n  - ~\/Documents\/rdfmodels\/\r\n  - \/usr\/local\/share\/rdfmodels\/\r\n\r\nCall\r\n\r\n  :RDF reload\r\n\r\nto reload model files, and\r\n\r\n  :RDF quit\r\n\r\nto restore the original omnifunc (if any).\r\n","install_details":"Copy to $HOME\/.vim\/plugins\/ to have it loaded from startup.\r\n\r\nRequires Vim compiled with Python and RDFLib installed for Python.\r\n","5":"Copy to $HOME\/.vim\/plugins\/ to have it loaded from startup.\r\n\r\nRequires Vim compiled with Python and RDFLib installed for Python.\r\n","first_name":"Niklas","6":"Niklas","last_name":"Lindstr\u00c3\u00b6m","7":"Lindstr\u00c3\u00b6m","releases":[{"0":"1835","vim_version":"7.0","1":"7.0","script_version":"1.0.1","2":"1.0.1","version_comment":"Minor change - improved prefix handling (better prefix completion, refreshes prefix dict).","3":"Minor change - improved prefix handling (better prefix completion, refreshes prefix dict).","package":"rdfnscomplete.vim","4":"rdfnscomplete.vim","src_id":"6904","5":"6904","creation_date":"1174826910","6":"1174826910"},{"0":"1835","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"rdfnscomplete.vim","4":"rdfnscomplete.vim","src_id":"6900","5":"6900","creation_date":"1174823240","6":"1174823240"}]},"1834":{"script_id":"1834","0":"1834","script_name":"st.vim","1":"st.vim","script_type":"syntax","2":"syntax","summary":"Syntax highlighting for Smalltalk","3":"Syntax highlighting for Smalltalk","description":"st.vim is a syntax highlighting script for Smalltalk that I wrote because I wasn't quite happy with the one that was distributed with my copy of Vim.  It's somewhat GNU Smalltalk-oriented, but I'm open to suggestions on improving compatibility with other versions of Smalltalk, as well as suggestions and corrections in general.  Also, I have only tested it in Vim 7.0.  If it works (or can be made to work) in earlier versions, please let me know.\r\n","4":"st.vim is a syntax highlighting script for Smalltalk that I wrote because I wasn't quite happy with the one that was distributed with my copy of Vim.  It's somewhat GNU Smalltalk-oriented, but I'm open to suggestions on improving compatibility with other versions of Smalltalk, as well as suggestions and corrections in general.  Also, I have only tested it in Vim 7.0.  If it works (or can be made to work) in earlier versions, please let me know.\r\n","install_details":"Drop st.vim in the syntax directory of your 'runtimepath'.  Type :help 'runtimepath' to find out where it is on your system and :help syntax for information on syntax highlighting in general.\r\n","5":"Drop st.vim in the syntax directory of your 'runtimepath'.  Type :help 'runtimepath' to find out where it is on your system and :help syntax for information on syntax highlighting in general.\r\n","first_name":"J\u0101nis","6":"Jānis","last_name":"R\u016bcis","7":"Rūcis","releases":[{"0":"1834","vim_version":"7.0","1":"7.0","script_version":"0.2.1","2":"0.2.1","version_comment":"Changed the way temporary variables are matched.  Should be less broken now.\r\n","3":"Changed the way temporary variables are matched.  Should be less broken now.\r\n","package":"st.vim","4":"st.vim","src_id":"6928","5":"6928","creation_date":"1175406623","6":"1175406623"},{"0":"1834","vim_version":"7.0","1":"7.0","script_version":"0.2.0","2":"0.2.0","version_comment":"- Underscore is now recognized in identifiers.\r\n- Added support for Smalltalk\/X-style end-of-line comments (comment starting with \"\/ and ending at a newline).  For these to be recognized you have to set (:let) the st_stx_style_end_of_line_comments internal variable to any value in your .vimrc or wherever it is you usually set them.\r\n- For name spaces in addition to the dot a double-colon is now recognized in the #methodFor: statement.\r\n- Support for three-character binary selectors can be activated by setting the st_three_character_binary_selectors internal variable to any value.\r\n- Made the white-space before an argument identifier optional for keyword and binary selectors in message patterns.  \"doSomethingTo:anObject\" and \"==anObject\" won't be highlighted as errors. \r\n- Added support for Smalltalk\/X-style primitives, sort of.  #primitiveDefinitions and #primitiveFunctions chunks are recognized, as well as %{ and %}-delimited regions.  (Contained C code is also highlighted.  Might be an overkill, though.)  For these to be recognized, set the st_stx_style_primitives variable.\r\n- Re-added support for GNU Smalltalk-style sign-after-radix numbers.  Actived with st_sign_after_radix.\r\n- Sign is now everywhere highlighted as part of the number.\r\n- Assignment operator is only highlighted if preceded by an identifier.\r\n- Some other stuff like, say, a new completely arbitrary script versioning system...","3":"- Underscore is now recognized in identifiers.\r\n- Added support for Smalltalk\/X-style end-of-line comments (comment starting with \"\/ and ending at a newline).  For these to be recognized you have to set (:let) the st_stx_style_end_of_line_comments internal variable to any value in your .vimrc or wherever it is you usually set them.\r\n- For name spaces in addition to the dot a double-colon is now recognized in the #methodFor: statement.\r\n- Support for three-character binary selectors can be activated by setting the st_three_character_binary_selectors internal variable to any value.\r\n- Made the white-space before an argument identifier optional for keyword and binary selectors in message patterns.  \"doSomethingTo:anObject\" and \"==anObject\" won't be highlighted as errors. \r\n- Added support for Smalltalk\/X-style primitives, sort of.  #primitiveDefinitions and #primitiveFunctions chunks are recognized, as well as %{ and %}-delimited regions.  (Contained C code is also highlighted.  Might be an overkill, though.)  For these to be recognized, set the st_stx_style_primitives variable.\r\n- Re-added support for GNU Smalltalk-style sign-after-radix numbers.  Actived with st_sign_after_radix.\r\n- Sign is now everywhere highlighted as part of the number.\r\n- Assignment operator is only highlighted if preceded by an identifier.\r\n- Some other stuff like, say, a new completely arbitrary script versioning system...","package":"st.vim","4":"st.vim","src_id":"6927","5":"6927","creation_date":"1175327089","6":"1175327089"},{"0":"1834","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Added a check to make sure there's white-space separating\r\nmessage pattern from the body of the method.  Makes\r\nerrors somewhat easier to spot.\r\n\r\nAdded a fix to allow use of line continuation.  Script will no\r\nlonger fail when 'compatible' is set.\r\n\r\nAdded support for spell checking.  It's now performed only\r\nin comments and strings.\r\n\r\nNumbers are now handled separately as integers, floats and\r\nscaled decimals.  The patterns now conform to the\r\ndraft ANSI Smalltalk standard which means that some\r\nGNU Smalltalk specific constructs are no longer supported.\r\nIt's planned to reintroduce those in a different fashion\r\nsome time \"in the future\".  Which is soon, hopefully.\r\n\r\nTemporarily removed error highlighting from array literals.  This is a\r\nside effect of the change above.\r\n\r\nSymbol handling was also changed for conformance.  In\r\nparticular, Symbol literals that aren't strings must\r\nbe valid selectors.  This isn't quite true in\r\nGNU Smalltalk, but it's also something that I'll add back\r\nlater.\r\n","3":"Added a check to make sure there's white-space separating\r\nmessage pattern from the body of the method.  Makes\r\nerrors somewhat easier to spot.\r\n\r\nAdded a fix to allow use of line continuation.  Script will no\r\nlonger fail when 'compatible' is set.\r\n\r\nAdded support for spell checking.  It's now performed only\r\nin comments and strings.\r\n\r\nNumbers are now handled separately as integers, floats and\r\nscaled decimals.  The patterns now conform to the\r\ndraft ANSI Smalltalk standard which means that some\r\nGNU Smalltalk specific constructs are no longer supported.\r\nIt's planned to reintroduce those in a different fashion\r\nsome time \"in the future\".  Which is soon, hopefully.\r\n\r\nTemporarily removed error highlighting from array literals.  This is a\r\nside effect of the change above.\r\n\r\nSymbol handling was also changed for conformance.  In\r\nparticular, Symbol literals that aren't strings must\r\nbe valid selectors.  This isn't quite true in\r\nGNU Smalltalk, but it's also something that I'll add back\r\nlater.\r\n","package":"st.vim","4":"st.vim","src_id":"6911","5":"6911","creation_date":"1175010680","6":"1175010680"},{"0":"1834","vim_version":"7.0","1":"7.0","script_version":"0.2","2":"0.2","version_comment":"Don't treat comments in Array and ByteArray literals as error.","3":"Don't treat comments in Array and ByteArray literals as error.","package":"st.vim","4":"st.vim","src_id":"6899","5":"6899","creation_date":"1174752438","6":"1174752438"},{"0":"1834","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"st.vim","4":"st.vim","src_id":"6898","5":"6898","creation_date":"1174735687","6":"1174735687"}]},"1833":{"script_id":"1833","0":"1833","script_name":"des3.vim","1":"des3.vim","script_type":"utility","2":"utility","summary":"Edit DES3 encrypted files and turn Vim into a simple password safe.","3":"Edit DES3 encrypted files and turn Vim into a simple password safe.","description":"\r\nThis is replaced by openssl.vim. See vimscript#2012.","4":"\r\nThis is replaced by openssl.vim. See vimscript#2012.","install_details":"","5":"","first_name":"Noah","6":"Noah","last_name":"Spurrier","7":"Spurrier","releases":[{"0":"1833","vim_version":"6.0","1":"6.0","script_version":"1","2":"1","version_comment":"Initial upload","3":"Initial upload","package":"des3.vim","4":"des3.vim","src_id":"6892","5":"6892","creation_date":"1174434032","6":"1174434032"}]},"1832":{"script_id":"1832","0":"1832","script_name":"asciidoc.vim","1":"asciidoc.vim","script_type":"syntax","2":"syntax","summary":"Syntax file for Asciidoc","3":"Syntax file for Asciidoc","description":"*Update:* A more sophisticated syntax file for Asciidoc is included since release 8.2. Check http:\/\/www.methods.co.nz\/asciidoc\/ f or details.\r\n\r\nThis is a syntax file for Asciidoc markup. You'll get info about Asciidoc on the Asciidoc Homepage: http:\/\/www.methods.co.nz\/asciidoc\/.\r\n\r\ncurrently the following elements are supported:\r\n\r\n * titles\r\n * rules\r\n * bullets\r\n * TODO, FIXME, ToDo, FixMe\r\n * references\r\n * labels\r\n * footnotes\r\n * links\r\n * comments\r\n * meta info\r\n\r\nThanks to Dag for several enhancements!\r\n\r\nFeel free to submit patches, comments, suggestions...to felix at obenhuber dot de and don't forget to cc asciidoc-discuss at metaperl dot com.\r\n\r\n\r\n","4":"*Update:* A more sophisticated syntax file for Asciidoc is included since release 8.2. Check http:\/\/www.methods.co.nz\/asciidoc\/ f or details.\r\n\r\nThis is a syntax file for Asciidoc markup. You'll get info about Asciidoc on the Asciidoc Homepage: http:\/\/www.methods.co.nz\/asciidoc\/.\r\n\r\ncurrently the following elements are supported:\r\n\r\n * titles\r\n * rules\r\n * bullets\r\n * TODO, FIXME, ToDo, FixMe\r\n * references\r\n * labels\r\n * footnotes\r\n * links\r\n * comments\r\n * meta info\r\n\r\nThanks to Dag for several enhancements!\r\n\r\nFeel free to submit patches, comments, suggestions...to felix at obenhuber dot de and don't forget to cc asciidoc-discuss at metaperl dot com.\r\n\r\n\r\n","install_details":"copy the file to $VIMRUNTIME\/syntax\r\n\r\n...and :help syn-files is your friend!","5":"copy the file to $VIMRUNTIME\/syntax\r\n\r\n...and :help syn-files is your friend!","first_name":"Felix","6":"Felix","last_name":"Obenhuber","7":"Obenhuber","releases":[{"0":"1832","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"asciidoc.vim","4":"asciidoc.vim","src_id":"6891","5":"6891","creation_date":"1174396603","6":"1174396603"}]},"1831":{"script_id":"1831","0":"1831","script_name":"VimSpy","1":"VimSpy","script_type":"utility","2":"utility","summary":"VimSpy enables you to browse through all Vim internal entities.","3":"VimSpy enables you to browse through all Vim internal entities.","description":"VimSpy defines a few commands and key mappings which enables you browse through almost all Vim internal entities such as functions, commands, menus and key mappings. \r\n\r\nMain commands: \r\n\r\nFunction [funcName]\r\nCommand [cmdName]\r\nAutocmd [autocmd]\r\nMenu [menuName]\r\nMap [mapping]\r\nSyntax [synItem]\r\nHighlight [synItem]\r\n\r\nThese commands are simply analogues of well-known Vim informational commands as function, command, autocmd and so on.\r\nBut they are modified in such a way that enables you use it much more efficient.\r\n\r\n1. An output of command is displayed in new window rather than ugly console.\r\n2. It is nicely highlighted.\r\n3. All function names and other keywords in output are clickable. When you double-click function name, new window with function definition is opened. In this function definition you may click any other function name and one more definition will be opened.  If you double-click Vim built-in keyword, help window will be opened. You also may to put cursor on keyword you are interested for and press enter. It will have the same effect as double-click.\r\n\r\n So you can in such a way quickly browse Vim internals. \r\n\r\nVimSpy also has such commands:\r\n\r\nChanges -- :change command analogue\r\nMessages -- :message command analogue\r\n\r\nCommandOutput  [cmd [args]] -- display output of any command in new window (It will not be highlighted though, except all command that have uppercase analogues)\r\n\r\nAMap        AMenu         ANoreMap   ANoreMenu\r\nCMap        CMenu         CNoreMap  CNoreMenu\r\nIMap          IMenu          INoreMap    INoreMenu\r\nNMap         NMenu        NNoreMap   NNoreMenu\r\nNoreMap    NoreMenu    OMap          OMenu\r\nONoreMap ONoreMenu  SMap          SMenu\r\nSNoreMap  SNoreMenu  VMap          VMenu\r\nVNoreMap  VNoreMenu  XMap          XMenu\r\nXNoreMap  XNoreMenu  LMap         LNoreMap    --      analogues of lowercase functions\r\n\r\n\r\n","4":"VimSpy defines a few commands and key mappings which enables you browse through almost all Vim internal entities such as functions, commands, menus and key mappings. \r\n\r\nMain commands: \r\n\r\nFunction [funcName]\r\nCommand [cmdName]\r\nAutocmd [autocmd]\r\nMenu [menuName]\r\nMap [mapping]\r\nSyntax [synItem]\r\nHighlight [synItem]\r\n\r\nThese commands are simply analogues of well-known Vim informational commands as function, command, autocmd and so on.\r\nBut they are modified in such a way that enables you use it much more efficient.\r\n\r\n1. An output of command is displayed in new window rather than ugly console.\r\n2. It is nicely highlighted.\r\n3. All function names and other keywords in output are clickable. When you double-click function name, new window with function definition is opened. In this function definition you may click any other function name and one more definition will be opened.  If you double-click Vim built-in keyword, help window will be opened. You also may to put cursor on keyword you are interested for and press enter. It will have the same effect as double-click.\r\n\r\n So you can in such a way quickly browse Vim internals. \r\n\r\nVimSpy also has such commands:\r\n\r\nChanges -- :change command analogue\r\nMessages -- :message command analogue\r\n\r\nCommandOutput  [cmd [args]] -- display output of any command in new window (It will not be highlighted though, except all command that have uppercase analogues)\r\n\r\nAMap        AMenu         ANoreMap   ANoreMenu\r\nCMap        CMenu         CNoreMap  CNoreMenu\r\nIMap          IMenu          INoreMap    INoreMenu\r\nNMap         NMenu        NNoreMap   NNoreMenu\r\nNoreMap    NoreMenu    OMap          OMenu\r\nONoreMap ONoreMenu  SMap          SMenu\r\nSNoreMap  SNoreMenu  VMap          VMenu\r\nVNoreMap  VNoreMenu  XMap          XMenu\r\nXNoreMap  XNoreMenu  LMap         LNoreMap    --      analogues of lowercase functions\r\n\r\n\r\n","install_details":"Just unpack tarball into $VIMRUNTIME or $HOME\/.vim","5":"Just unpack tarball into $VIMRUNTIME or $HOME\/.vim","first_name":"Michael","6":"Michael","last_name":"Schwarz","7":"Schwarz","releases":[{"0":"1831","vim_version":"7.0","1":"7.0","script_version":"0.2","2":"0.2","version_comment":"Was added good syntax highlighting, ability to browse over all function names and a few new commands (Autocmd, Map and Map and Menu derivatives).","3":"Was added good syntax highlighting, ability to browse over all function names and a few new commands (Autocmd, Map and Map and Menu derivatives).","package":"VimSpy.tar.gz","4":"VimSpy.tar.gz","src_id":"7009","5":"7009","creation_date":"1177101923","6":"1177101923"},{"0":"1831","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"CommandOutput.tar.gz","4":"CommandOutput.tar.gz","src_id":"6889","5":"6889","creation_date":"1174235098","6":"1174235098"}]},"1830":{"script_id":"1830","0":"1830","script_name":"html improved indentation","1":"html improved indentation","script_type":"indent","2":"indent","summary":"A better indentation for HTML and embedded javascript","3":"A better indentation for HTML and embedded javascript","description":"This has been indenting HTML and JavaScript more properly that the standard html.vim.\r\n\r\nIt depends on the syntax file for HTML and JavaScript.","4":"This has been indenting HTML and JavaScript more properly that the standard html.vim.\r\n\r\nIt depends on the syntax file for HTML and JavaScript.","install_details":"Just put it in ~\/.vim\/indent.","5":"Just put it in ~\/.vim\/indent.","first_name":"Leandro","6":"Leandro","last_name":"Penz","7":"Penz","releases":[{"0":"1830","vim_version":"7.0","1":"7.0","script_version":"37","2":"37","version_comment":"Initial upload","3":"Initial upload","package":"html.vim","4":"html.vim","src_id":"6885","5":"6885","creation_date":"1174059660","6":"1174059660"}]},"1829":{"script_id":"1829","0":"1829","script_name":"writebackupVersionControl","1":"writebackupVersionControl","script_type":"utility","2":"utility","summary":"Version control functions (diff, restore, history) for writebackup backups.","3":"Version control functions (diff, restore, history) for writebackup backups.","description":"DESCRIPTION\r\nThis plugin enhances the primitive file backup mechanism provided by\r\nwritebackup.vim with some functions of real revision control systems like\r\nCVS, RCS or Subversion - without additional software.\r\nVia Vim commands, you can list and go to all backup versions that exist for\r\nthe current file, check whether you have a current backup, backup the saved\r\nversion of the buffer even after you've made unsaved changes in the buffer\r\n(which is useful for after-the-fact backups).\r\nWithin Vim, you can create a diff with the previous version, restore the\r\ncurrent file from its predecessor or any other backed-up version.\r\n\r\nUSAGE\r\n:WriteBackupListVersions\r\n                        List all backup versions that exist for the current\r\n                        file. If the file isn't the original, it is marked in\r\n                        the version list. If the file is the original, the\r\n                        time that has passed since the last backup is printed,\r\n                        too.\r\n\r\n:[count]WriteBackupGoPrev[!]\r\n:[count]WriteBackupGoNext[!]\r\n                        Open a backup file version relative to the current\r\n                        backup or original file (with 'readonly' set to\r\n                        prevent accidental edits) . You can skip multiple\r\n                        backups via the optional [count]; if the resulting\r\n                        index is out of bounds, the first \/ last available\r\n                        backup version is edited.\r\n                        Thus, :999WriteBackupGoPrev edits the very first\r\n                        existing backup, and :999WriteBackupGoNext edits the\r\n                        latest (i.e. most recent) backup.\r\n                        With [!], any changes to the current version are\r\n                        discarded.\r\n\r\n:WriteBackupGoOriginal[!]\r\n                        Edit the original of the current backup file. If\r\n                        backups are stored in a different directory, it may\r\n                        not be possible to determine the original file. With\r\n                        [!], any changes to the current version are discarded.\r\n\r\n:WriteBackupIsBackedUp\r\n                        Check whether the latest backup is identical to the\r\n                        (saved version of the) current file (which must be the\r\n                        original file).\r\n\r\n:[count]WriteBackupDiffWithPred\r\n                        Perform a diff of the current file (which may be the\r\n                        original file or any backup) with the [count]'th\r\n                        previous version. If the resulting index is out of\r\n                        bounds, the first available backup version is used.\r\n                        The diff is done inside Vim, with a new :diffsplit\r\n                        being opened.\r\n\r\n:[count]WriteBackupViewDiffWithPred [{diff-arguments}]\r\n                        Show the differences of the current file (which may be\r\n                        the original file or any backup) with the [count]'th\r\n                        previous version. If the resulting index is out of\r\n                        bounds, the first available backup version is used.\r\n                        The diff output is opened in a split scratch buffer.\r\n                        Any {diff-arguments} are passed as-is to the diff\r\n                        executable. The \"icase\" and \"iwhite\" settings of\r\n                        'diffopt' are used, too.\r\n                        The current working directory is used as the diff root\r\n                        directory (in which the diff command will be invoked)\r\n                        You can set the diff root via:\r\n                        :lcd {diff-root} | WriteBackupViewDiffWithPred | lcd -\r\n                       Use the :saveas command if you want to persist the\r\n                        diff scratch buffer on disk. Rename the scratch buffer\r\n                        via the :file command if you want to keep it and\r\n                        prevent further updates.\r\n          + [count]du\r\n                        By repeating the command, an existing scratch buffer\r\n                        is updated; no new split is created. One can also\r\n                        update the differences by repeating\r\n                        :WriteBackupViewDiffWithPred in the diff scratch\r\n                        buffer itself, or through the buffer-local [count]du\r\n                        mapping. The mapping will update with the same diff\r\n                        options used previously; the command can be repeated\r\n                        with the same or different {diff-arguments}. For\r\n                        example, you can change a context diff created via\r\n                            :WriteBackupViewDiffWithPred -c\r\n                       into the unified format by repeating via >\r\n                            :WriteBackupViewDiffWithPred -u\r\n                       If you repeat with a [count], a new predecessor is\r\n                        chosen for the updated diff; the newer file is kept.\r\n\r\n:[count]WriteBackupDiffDaysChanges\r\n                        Perform a diff of the current file (which may be the\r\n                        original file or any backup) with today's (or\r\n                        [count] - 1 days ago) first backup.\r\n                        The diff is done inside Vim, with a new :diffsplit\r\n                        being opened.\r\n\r\n:[count]WriteBackupViewDaysChanges [{diff-arguments}]\r\n                        Show the differences of the current file (which may be\r\n                        the original file or any backup) with today's (or\r\n                        [count] - 1 days ago) first backup.\r\n                        The diff output is opened in a split scratch buffer.\r\n\r\n:[count]WriteBackupRestoreFromPred[!]\r\n                        Overwrite the current file (which must be the\r\n                        original) with the [count]'th previous backup. With\r\n                        [!] skips confirmation dialog and allows to restore\r\n                        over readonly original file.\r\n\r\n:WriteBackupRestoreThisBackup[!]\r\n                        Restore the current file as the original file, which\r\n                        will be overwritten. With [!] skips confirmation\r\n                        dialog and allows to restore over readonly original\r\n                        file.\r\n\r\n:WriteBackupOfSavedOriginal[!]\r\n                        Instead of backing up the current buffer, back up the\r\n                        saved version of the buffer. This comes handy when you\r\n                        realize you need a backup only after you've made\r\n                        changes to the buffer.\r\n                        With [!], creation of a new backup file is forced:\r\n                        - even if the last backup is identical\r\n                        - even when no more backup versions (for this day) are\r\n                          available (the last '.YYYYMMDDz' backup gets\r\n                          overwritten, even if it is readonly)\r\n\r\n:WriteBackupDeleteLastBackup[!]\r\n                        Delete the last backup. With [!] skips confirmation\r\n                        dialog and allows to delete readonly backup file.","4":"DESCRIPTION\r\nThis plugin enhances the primitive file backup mechanism provided by\r\nwritebackup.vim with some functions of real revision control systems like\r\nCVS, RCS or Subversion - without additional software.\r\nVia Vim commands, you can list and go to all backup versions that exist for\r\nthe current file, check whether you have a current backup, backup the saved\r\nversion of the buffer even after you've made unsaved changes in the buffer\r\n(which is useful for after-the-fact backups).\r\nWithin Vim, you can create a diff with the previous version, restore the\r\ncurrent file from its predecessor or any other backed-up version.\r\n\r\nUSAGE\r\n:WriteBackupListVersions\r\n                        List all backup versions that exist for the current\r\n                        file. If the file isn't the original, it is marked in\r\n                        the version list. If the file is the original, the\r\n                        time that has passed since the last backup is printed,\r\n                        too.\r\n\r\n:[count]WriteBackupGoPrev[!]\r\n:[count]WriteBackupGoNext[!]\r\n                        Open a backup file version relative to the current\r\n                        backup or original file (with 'readonly' set to\r\n                        prevent accidental edits) . You can skip multiple\r\n                        backups via the optional [count]; if the resulting\r\n                        index is out of bounds, the first \/ last available\r\n                        backup version is edited.\r\n                        Thus, :999WriteBackupGoPrev edits the very first\r\n                        existing backup, and :999WriteBackupGoNext edits the\r\n                        latest (i.e. most recent) backup.\r\n                        With [!], any changes to the current version are\r\n                        discarded.\r\n\r\n:WriteBackupGoOriginal[!]\r\n                        Edit the original of the current backup file. If\r\n                        backups are stored in a different directory, it may\r\n                        not be possible to determine the original file. With\r\n                        [!], any changes to the current version are discarded.\r\n\r\n:WriteBackupIsBackedUp\r\n                        Check whether the latest backup is identical to the\r\n                        (saved version of the) current file (which must be the\r\n                        original file).\r\n\r\n:[count]WriteBackupDiffWithPred\r\n                        Perform a diff of the current file (which may be the\r\n                        original file or any backup) with the [count]'th\r\n                        previous version. If the resulting index is out of\r\n                        bounds, the first available backup version is used.\r\n                        The diff is done inside Vim, with a new :diffsplit\r\n                        being opened.\r\n\r\n:[count]WriteBackupViewDiffWithPred [{diff-arguments}]\r\n                        Show the differences of the current file (which may be\r\n                        the original file or any backup) with the [count]'th\r\n                        previous version. If the resulting index is out of\r\n                        bounds, the first available backup version is used.\r\n                        The diff output is opened in a split scratch buffer.\r\n                        Any {diff-arguments} are passed as-is to the diff\r\n                        executable. The \"icase\" and \"iwhite\" settings of\r\n                        'diffopt' are used, too.\r\n                        The current working directory is used as the diff root\r\n                        directory (in which the diff command will be invoked)\r\n                        You can set the diff root via:\r\n                        :lcd {diff-root} | WriteBackupViewDiffWithPred | lcd -\r\n                       Use the :saveas command if you want to persist the\r\n                        diff scratch buffer on disk. Rename the scratch buffer\r\n                        via the :file command if you want to keep it and\r\n                        prevent further updates.\r\n          + [count]du\r\n                        By repeating the command, an existing scratch buffer\r\n                        is updated; no new split is created. One can also\r\n                        update the differences by repeating\r\n                        :WriteBackupViewDiffWithPred in the diff scratch\r\n                        buffer itself, or through the buffer-local [count]du\r\n                        mapping. The mapping will update with the same diff\r\n                        options used previously; the command can be repeated\r\n                        with the same or different {diff-arguments}. For\r\n                        example, you can change a context diff created via\r\n                            :WriteBackupViewDiffWithPred -c\r\n                       into the unified format by repeating via >\r\n                            :WriteBackupViewDiffWithPred -u\r\n                       If you repeat with a [count], a new predecessor is\r\n                        chosen for the updated diff; the newer file is kept.\r\n\r\n:[count]WriteBackupDiffDaysChanges\r\n                        Perform a diff of the current file (which may be the\r\n                        original file or any backup) with today's (or\r\n                        [count] - 1 days ago) first backup.\r\n                        The diff is done inside Vim, with a new :diffsplit\r\n                        being opened.\r\n\r\n:[count]WriteBackupViewDaysChanges [{diff-arguments}]\r\n                        Show the differences of the current file (which may be\r\n                        the original file or any backup) with today's (or\r\n                        [count] - 1 days ago) first backup.\r\n                        The diff output is opened in a split scratch buffer.\r\n\r\n:[count]WriteBackupRestoreFromPred[!]\r\n                        Overwrite the current file (which must be the\r\n                        original) with the [count]'th previous backup. With\r\n                        [!] skips confirmation dialog and allows to restore\r\n                        over readonly original file.\r\n\r\n:WriteBackupRestoreThisBackup[!]\r\n                        Restore the current file as the original file, which\r\n                        will be overwritten. With [!] skips confirmation\r\n                        dialog and allows to restore over readonly original\r\n                        file.\r\n\r\n:WriteBackupOfSavedOriginal[!]\r\n                        Instead of backing up the current buffer, back up the\r\n                        saved version of the buffer. This comes handy when you\r\n                        realize you need a backup only after you've made\r\n                        changes to the buffer.\r\n                        With [!], creation of a new backup file is forced:\r\n                        - even if the last backup is identical\r\n                        - even when no more backup versions (for this day) are\r\n                          available (the last '.YYYYMMDDz' backup gets\r\n                          overwritten, even if it is readonly)\r\n\r\n:WriteBackupDeleteLastBackup[!]\r\n                        Delete the last backup. With [!] skips confirmation\r\n                        dialog and allows to delete readonly backup file.","install_details":"INSTALLATION\r\nThe code is hosted in a Git repo at\r\n    https:\/\/github.com\/inkarkat\/vim-writebackupVersionControl\r\nYou can use your favorite plugin manager, or \"git clone\" into a directory used\r\nfor Vim packages. Releases are on the \"stable\" branch, the latest unstable\r\ndevelopment snapshot on \"master\".\r\n\r\nThis script is also packaged as a vimball. If you have the \"gunzip\"\r\ndecompressor in your PATH, simply edit the *.vmb.gz package in Vim; otherwise,\r\ndecompress the archive first, e.g. using WinZip. Inside Vim, install by\r\nsourcing the vimball or via the :UseVimball command.\r\n    vim writebackupVersionControl*.vmb.gz\r\n    :so %\r\nTo uninstall, use the :RmVimball command.\r\n\r\nDEPENDENCIES\r\n- Requires Vim 7.0 or higher.\r\n- Requires the writebackup.vim plugin (vimscript #1828), version 2.00 or\r\n  higher.\r\n- Requires the ingo-library.vim plugin (vimscript #4433), version 1.022 or\r\n  higher.\r\n- External command \"cmp\" or \"diff\" (or equivalent) for comparison.\r\n- External command \"diff\" or equivalent for listing of differences.\r\n- External commands \"cp\" (Unix) \/ \"copy\" and \"xcopy\" (Windows) for restore\r\n  and backup original file functionality.\r\n\r\nCONFIGURATION\r\nFor a permanent configuration, put the following commands into your vimrc:\r\n\r\nTo change the default diffsplit from vertical to horizontal, use:\r\n    let g:WriteBackup_DiffVertSplit = 0\r\n\r\nThe :WriteBackupIsBackedUp command uses an external compare command (either\r\n\"cmp -s\" or \"diff -q\") to determine whether the backup is identical with the\r\noriginal file. You can overwrite the auto-detected default via:\r\n    let g:WriteBackup_CompareShellCommand = '\/path\/to\/mycomparecmd --myoption'\r\nThe command must take two filespec arguments, return 0 for identical files, 1\r\nfor different files and anything else for trouble.\r\n\r\nThe :WriteBackupViewDiffWithPred command invokes an external diff command to\r\nlist the differences between two files. Overwrite if \"diff\" cannot be found\r\nthrough $PATH:\r\n    let g:WriteBackup_DiffShellCommand = '\/path\/to\/mydiff'\r\n\r\nCommand-line arguments for the external diff command can be specified\r\nseparately. Configure any arguments that should always be passed here:\r\n    let g:WriteBackup_DiffCreateAlwaysArguments = '-t -F \"^[_a-zA-Z0-9]+ *(\"'\r\n\r\nIf no {diff-arguments} are passed to the :WriteBackupViewDiffWithPred\r\ncommand, the default diff output format is set to the unified format. You can\r\nfor example change this to a context diff by setting:\r\n    let g:WriteBackup_DiffCreateDefaultArguments = '-c'\r\n\r\nThe :WriteBackupViewDiffWithPred command opens the diff scratch buffer via\r\nthe :new command. You can add window command modifiers like :vertical or\r\n:topleft to change the positioning of the window:\r\n    let g:WriteBackup_ScratchBufferCommandModifiers = 'topleft'","5":"INSTALLATION\r\nThe code is hosted in a Git repo at\r\n    https:\/\/github.com\/inkarkat\/vim-writebackupVersionControl\r\nYou can use your favorite plugin manager, or \"git clone\" into a directory used\r\nfor Vim packages. Releases are on the \"stable\" branch, the latest unstable\r\ndevelopment snapshot on \"master\".\r\n\r\nThis script is also packaged as a vimball. If you have the \"gunzip\"\r\ndecompressor in your PATH, simply edit the *.vmb.gz package in Vim; otherwise,\r\ndecompress the archive first, e.g. using WinZip. Inside Vim, install by\r\nsourcing the vimball or via the :UseVimball command.\r\n    vim writebackupVersionControl*.vmb.gz\r\n    :so %\r\nTo uninstall, use the :RmVimball command.\r\n\r\nDEPENDENCIES\r\n- Requires Vim 7.0 or higher.\r\n- Requires the writebackup.vim plugin (vimscript #1828), version 2.00 or\r\n  higher.\r\n- Requires the ingo-library.vim plugin (vimscript #4433), version 1.022 or\r\n  higher.\r\n- External command \"cmp\" or \"diff\" (or equivalent) for comparison.\r\n- External command \"diff\" or equivalent for listing of differences.\r\n- External commands \"cp\" (Unix) \/ \"copy\" and \"xcopy\" (Windows) for restore\r\n  and backup original file functionality.\r\n\r\nCONFIGURATION\r\nFor a permanent configuration, put the following commands into your vimrc:\r\n\r\nTo change the default diffsplit from vertical to horizontal, use:\r\n    let g:WriteBackup_DiffVertSplit = 0\r\n\r\nThe :WriteBackupIsBackedUp command uses an external compare command (either\r\n\"cmp -s\" or \"diff -q\") to determine whether the backup is identical with the\r\noriginal file. You can overwrite the auto-detected default via:\r\n    let g:WriteBackup_CompareShellCommand = '\/path\/to\/mycomparecmd --myoption'\r\nThe command must take two filespec arguments, return 0 for identical files, 1\r\nfor different files and anything else for trouble.\r\n\r\nThe :WriteBackupViewDiffWithPred command invokes an external diff command to\r\nlist the differences between two files. Overwrite if \"diff\" cannot be found\r\nthrough $PATH:\r\n    let g:WriteBackup_DiffShellCommand = '\/path\/to\/mydiff'\r\n\r\nCommand-line arguments for the external diff command can be specified\r\nseparately. Configure any arguments that should always be passed here:\r\n    let g:WriteBackup_DiffCreateAlwaysArguments = '-t -F \"^[_a-zA-Z0-9]+ *(\"'\r\n\r\nIf no {diff-arguments} are passed to the :WriteBackupViewDiffWithPred\r\ncommand, the default diff output format is set to the unified format. You can\r\nfor example change this to a context diff by setting:\r\n    let g:WriteBackup_DiffCreateDefaultArguments = '-c'\r\n\r\nThe :WriteBackupViewDiffWithPred command opens the diff scratch buffer via\r\nthe :new command. You can add window command modifiers like :vertical or\r\n:topleft to change the positioning of the window:\r\n    let g:WriteBackup_ScratchBufferCommandModifiers = 'topleft'","first_name":"Ingo","6":"Ingo","last_name":"Karkat","7":"Karkat","releases":[{"0":"1829","vim_version":"7.0","1":"7.0","script_version":"3.22","2":"3.22","version_comment":"- FIX: Avoid \"E16: Invalid range\" in writebackupVersionControl#GetAllBackupsForFile() with a filename containing \"[[\" by escaping the filespec for wildcard characters.\r\n- Make Unix 'cp' command configurable via g:WriteBackupCopyShellCommand.\r\n- Support non-GNU cp command (e.g. on BSD) that doesn't support the --preserve=timestamp argument by making it configurable (g:WriteBackupCopyPreserveArgument) and implemening a heuristic that falls back to the POSIX -p option if the original cp command failed.\r\n- Use ingo#compat#glob().\r\n- ingo#buffer#scratch#Create() from ingo-library.vim version 1.024 doesn't position the cursor on the first line any more; explicitly do this, as the alternative condition of the potential original cursor position restore depends on this.\r\n- :WriteBackupViewDiffWithPred: Keep the same 'iskeyword' value as the original buffer's. Makes it easier to search across diff and original with |star|.\r\n- Inconsistency: :WriteBackupOfSavedOriginal keeps executable attributes, whereas :WriteBackup normally doesn't. The general discrepancy is that the 'cp' command by default preserves the attributes, whereas a :write from within Vim doesn't. Add --no-preserve=mode to g:WriteBackupCopyPreserveArgument. *** You need to update to ingo-library (vimscript #4433) version 1.022! ***","3":"- FIX: Avoid \"E16: Invalid range\" in writebackupVersionControl#GetAllBackupsForFile() with a filename containing \"[[\" by escaping the filespec for wildcard characters.\r\n- Make Unix 'cp' command configurable via g:WriteBackupCopyShellCommand.\r\n- Support non-GNU cp command (e.g. on BSD) that doesn't support the --preserve=timestamp argument by making it configurable (g:WriteBackupCopyPreserveArgument) and implemening a heuristic that falls back to the POSIX -p option if the original cp command failed.\r\n- Use ingo#compat#glob().\r\n- ingo#buffer#scratch#Create() from ingo-library.vim version 1.024 doesn't position the cursor on the first line any more; explicitly do this, as the alternative condition of the potential original cursor position restore depends on this.\r\n- :WriteBackupViewDiffWithPred: Keep the same 'iskeyword' value as the original buffer's. Makes it easier to search across diff and original with |star|.\r\n- Inconsistency: :WriteBackupOfSavedOriginal keeps executable attributes, whereas :WriteBackup normally doesn't. The general discrepancy is that the 'cp' command by default preserves the attributes, whereas a :write from within Vim doesn't. Add --no-preserve=mode to g:WriteBackupCopyPreserveArgument. *** You need to update to ingo-library (vimscript #4433) version 1.022! ***","package":"writebackupVersionControl-3.22.vmb.gz","4":"writebackupVersionControl-3.22.vmb.gz","src_id":"27096","5":"27096","creation_date":"1585886184","6":"1585886184"},{"0":"1829","vim_version":"7.0","1":"7.0","script_version":"3.21","2":"3.21","version_comment":"- Implement abort on error for all commands.\r\n- CHG: writebackupVersionControl#ListVersions() now indicates no backups exist with 2 instead of 0.\r\n- CHG: writebackupVersionControl#RestoreThisBackup(), writebackupVersionControl#RestoreFromPred(), writebackupVersionControl#DeleteBackupLastBackup() now indicate user decline with 2 instead of 0.\r\n- Keep the same 'fileformat' as the original buffer's on :WriteBackupViewDiffWithPred. This matters when the diff is persisted as a patch.\r\n- Add dependency to ingo-library (vimscript #4433). *** You need to separately install ingo-library (vimscript #4433) version 1.013 (or higher)! ***","3":"- Implement abort on error for all commands.\r\n- CHG: writebackupVersionControl#ListVersions() now indicates no backups exist with 2 instead of 0.\r\n- CHG: writebackupVersionControl#RestoreThisBackup(), writebackupVersionControl#RestoreFromPred(), writebackupVersionControl#DeleteBackupLastBackup() now indicate user decline with 2 instead of 0.\r\n- Keep the same 'fileformat' as the original buffer's on :WriteBackupViewDiffWithPred. This matters when the diff is persisted as a patch.\r\n- Add dependency to ingo-library (vimscript #4433). *** You need to separately install ingo-library (vimscript #4433) version 1.013 (or higher)! ***","package":"writebackupVersionControl-3.21.vmb.gz","4":"writebackupVersionControl-3.21.vmb.gz","src_id":"21401","5":"21401","creation_date":"1391028200","6":"1391028200"},{"0":"1829","vim_version":"7.0","1":"7.0","script_version":"3.20","2":"3.20","version_comment":"- ENH: Allow to override g:WriteBackup_DiffCreateAlwaysArguments and g:WriteBackup_DiffCreateDefaultArguments with buffer-local variables; e.g. to provide a filetype-specific \"--show-function-list\" diff argument.\r\n- ENH: When the current window is in diff mode, \"inherit\" the participation in the diff to the next backup file on :WriteBackupGo* commands, as the user probably wants to continue comparing them.\r\n- BUG: On Windows, when file backups exist in different upper-\/lowercase versions, the ordering of :WriteBackupListVersions and :WriteBackupGoPrev\/Next are broken.","3":"- ENH: Allow to override g:WriteBackup_DiffCreateAlwaysArguments and g:WriteBackup_DiffCreateDefaultArguments with buffer-local variables; e.g. to provide a filetype-specific \"--show-function-list\" diff argument.\r\n- ENH: When the current window is in diff mode, \"inherit\" the participation in the diff to the next backup file on :WriteBackupGo* commands, as the user probably wants to continue comparing them.\r\n- BUG: On Windows, when file backups exist in different upper-\/lowercase versions, the ordering of :WriteBackupListVersions and :WriteBackupGoPrev\/Next are broken.","package":"writebackupVersionControl-3.20.vmb.gz","4":"writebackupVersionControl-3.20.vmb.gz","src_id":"19182","5":"19182","creation_date":"1355477051","6":"1355477051"},{"0":"1829","vim_version":"7.0","1":"7.0","script_version":"3.10","2":"3.10","version_comment":"ENH: Add :WriteBackupDiffDaysChanges and :WriteBackupViewDaysChanges. ","3":"ENH: Add :WriteBackupDiffDaysChanges and :WriteBackupViewDaysChanges. ","package":"writebackupVersionControl.vba.gz","4":"writebackupVersionControl.vba.gz","src_id":"17501","5":"17501","creation_date":"1329758469","6":"1329758469"},{"0":"1829","vim_version":"7.0","1":"7.0","script_version":"3.00","2":"3.00","version_comment":"ENH: New writebackup.vim default \"redate\" for g:WriteBackup_AvoidIdenticalBackups that renames an identical backup from an earlier date to be the first backup of today is also used for :WriteBackupOfSavedOriginal. The changes now require version 3.00 of both plugins. ","3":"ENH: New writebackup.vim default \"redate\" for g:WriteBackup_AvoidIdenticalBackups that renames an identical backup from an earlier date to be the first backup of today is also used for :WriteBackupOfSavedOriginal. The changes now require version 3.00 of both plugins. ","package":"writebackupVersionControl.vba.gz","4":"writebackupVersionControl.vba.gz","src_id":"17475","5":"17475","creation_date":"1329402800","6":"1329402800"},{"0":"1829","vim_version":"7.0","1":"7.0","script_version":"2.30","2":"2.30","version_comment":"- ENH: On Windows, :WriteBackupOfSavedOriginal now updates the modification date (via a \"copy\" trick), and on Unix, :WriteBackupRestoreThisBackup \/ :WriteBackupRestoreFromPred now keep the backup's modification date. \r\n- Expose many internal functions and make all autoload functions behind the various commands now also indicate their success via a boolean \/ numeric return value. \r\n- Use ingodate#HumanReltime() for a more human output of elapsed time since last backup. ","3":"- ENH: On Windows, :WriteBackupOfSavedOriginal now updates the modification date (via a \"copy\" trick), and on Unix, :WriteBackupRestoreThisBackup \/ :WriteBackupRestoreFromPred now keep the backup's modification date. \r\n- Expose many internal functions and make all autoload functions behind the various commands now also indicate their success via a boolean \/ numeric return value. \r\n- Use ingodate#HumanReltime() for a more human output of elapsed time since last backup. ","package":"writebackupVersionControl.vba.gz","4":"writebackupVersionControl.vba.gz","src_id":"17458","5":"17458","creation_date":"1329220494","6":"1329220494"},{"0":"1829","vim_version":"7.0","1":"7.0","script_version":"2.24","2":"2.24","version_comment":"- ENH: Define a local 'du' mapping to quickly update the diff (of the same version and with the same options as this time), unless [count] is given, which sets a different version). \r\n- :WriteBackupViewDiffWithPred not just checks for empty scratch buffer, but also considers the diff command exit code. \r\n- BUG: :WriteBackupViewDiffWithPred can cause E121: Undefined variable: l:predecessor. Similar issue with a:filespec showing scratch buffer name in place of the original file name. Now using l:oldFile and l:newFile instead. \r\n- BUG: WriteBackupViewDiffWithPred didn't always go back to the original window when no differences, but fell back to the next one.","3":"- ENH: Define a local 'du' mapping to quickly update the diff (of the same version and with the same options as this time), unless [count] is given, which sets a different version). \r\n- :WriteBackupViewDiffWithPred not just checks for empty scratch buffer, but also considers the diff command exit code. \r\n- BUG: :WriteBackupViewDiffWithPred can cause E121: Undefined variable: l:predecessor. Similar issue with a:filespec showing scratch buffer name in place of the original file name. Now using l:oldFile and l:newFile instead. \r\n- BUG: WriteBackupViewDiffWithPred didn't always go back to the original window when no differences, but fell back to the next one.","package":"writebackupVersionControl.vba.gz","4":"writebackupVersionControl.vba.gz","src_id":"12368","5":"12368","creation_date":"1266002594","6":"1266002594"},{"0":"1829","vim_version":"7.0","1":"7.0","script_version":"2.23","2":"2.23","version_comment":"ENH: :WriteBackupRestoreFromPred now takes an optional [count] to restore an earlier predecessor. ","3":"ENH: :WriteBackupRestoreFromPred now takes an optional [count] to restore an earlier predecessor. ","package":"writebackupVersionControl.vba.gz","4":"writebackupVersionControl.vba.gz","src_id":"11598","5":"11598","creation_date":"1256573014","6":"1256573014"},{"0":"1829","vim_version":"7.0","1":"7.0","script_version":"2.22","2":"2.22","version_comment":"BF: escapings#shellescape() caused E118 on Vim 7.1. Enhanced wrapper function. ","3":"BF: escapings#shellescape() caused E118 on Vim 7.1. Enhanced wrapper function. ","package":"writebackupVersionControl.vba.gz","4":"writebackupVersionControl.vba.gz","src_id":"11216","5":"11216","creation_date":"1250687243","6":"1250687243"},{"0":"1829","vim_version":"7.0","1":"7.0","script_version":"2.21","2":"2.21","version_comment":"- Replaced simple filespec quoting with built-in shellescape() function (or emulation for Vim 7.0 \/ 7.1) via escapings.vim wrapper. \r\n- Keeping cursor position when only refreshing the diff scratch buffer. \r\n- Window position of the diff scratch buffer can now be configured. \r\n- ENH: Now issuing a warning that there are no differences and closing the useless diff scratch buffer if it is empty. \r\n- BF: Forgot {special} in shellescape() call for writebackupVersionControl#ViewDiffWithPred(); the scratch buffer uses the ! command. ","3":"- Replaced simple filespec quoting with built-in shellescape() function (or emulation for Vim 7.0 \/ 7.1) via escapings.vim wrapper. \r\n- Keeping cursor position when only refreshing the diff scratch buffer. \r\n- Window position of the diff scratch buffer can now be configured. \r\n- ENH: Now issuing a warning that there are no differences and closing the useless diff scratch buffer if it is empty. \r\n- BF: Forgot {special} in shellescape() call for writebackupVersionControl#ViewDiffWithPred(); the scratch buffer uses the ! command. ","package":"writebackupVersionControl.vba.gz","4":"writebackupVersionControl.vba.gz","src_id":"11039","5":"11039","creation_date":"1248033565","6":"1248033565"},{"0":"1829","vim_version":"7.0","1":"7.0","script_version":"2.20","2":"2.20","version_comment":"ENH: Added :WriteBackupViewDiffWithPred command to show the diff output in a scratch buffer. With this, one can get a quick overview of what has changed since the last backup without performing a diffsplit within Vim. ","3":"ENH: Added :WriteBackupViewDiffWithPred command to show the diff output in a scratch buffer. With this, one can get a quick overview of what has changed since the last backup without performing a diffsplit within Vim. ","package":"writebackupVersionControl.vba.gz","4":"writebackupVersionControl.vba.gz","src_id":"10985","5":"10985","creation_date":"1247217967","6":"1247217967"},{"0":"1829","vim_version":"7.0","1":"7.0","script_version":"2.11","2":"2.11","version_comment":"ENH: :WriteBackupDiffWithPred now takes an optional [count] to diff with an\r\nearlier predecessor. ","3":"ENH: :WriteBackupDiffWithPred now takes an optional [count] to diff with an\r\nearlier predecessor. ","package":"writebackupVersionControl.vba.gz","4":"writebackupVersionControl.vba.gz","src_id":"10914","5":"10914","creation_date":"1246364845","6":"1246364845"},{"0":"1829","vim_version":"7.0","1":"7.0","script_version":"2.10","2":"2.10","version_comment":"Replaced simple filespec escaping with built-in fnameescape() function (or\r\nemulation for Vim 7.0 \/ 7.1) via escapings.vim wrapper.","3":"Replaced simple filespec escaping with built-in fnameescape() function (or\r\nemulation for Vim 7.0 \/ 7.1) via escapings.vim wrapper.","package":"writebackupVersionControl.vba.gz","4":"writebackupVersionControl.vba.gz","src_id":"10695","5":"10695","creation_date":"1243519333","6":"1243519333"},{"0":"1829","vim_version":"7.0","1":"7.0","script_version":"2.01","2":"2.01","version_comment":"Backup versions are now opened read-only (through :WriteBackupGoPrev\/Next and\r\n:WriteBackupDiffWithPred commands) to prevent the user from accidentally\r\nediting the backup instead of the original. ","3":"Backup versions are now opened read-only (through :WriteBackupGoPrev\/Next and\r\n:WriteBackupDiffWithPred commands) to prevent the user from accidentally\r\nediting the backup instead of the original. ","package":"writebackupVersionControl.vba.gz","4":"writebackupVersionControl.vba.gz","src_id":"10577","5":"10577","creation_date":"1242050992","6":"1242050992"},{"0":"1829","vim_version":"7.0","1":"7.0","script_version":"2.00","2":"2.00","version_comment":"- Using separate autoload script to help speed up VIM startup. This is an\r\n  incompatible change that also requires the corresponding writebackup plugin\r\n  version. *** PLEASE UPDATE writebackup (vimscript #1828), too ***\r\n- BF: :WriteBackupListVersions now handles (and reports) backup files with a\r\n  future date.\r\n- ENH: Allowing to configure compare shell command via\r\n  g:WriteBackup_CompareShellCommand. \r\n- ENH: Added :WriteBackupDeleteLastBackup command. \r\n- ENH: Added [!] to the following commands to disable confirmation dialog and\r\n  override readonly target files: :WriteBackupRestoreFromPred, \r\n  :WriteBackupRestoreThisBackup, :WriteBackupOfSavedOriginal, \r\n  :WriteBackupDeleteLastBackup","3":"- Using separate autoload script to help speed up VIM startup. This is an\r\n  incompatible change that also requires the corresponding writebackup plugin\r\n  version. *** PLEASE UPDATE writebackup (vimscript #1828), too ***\r\n- BF: :WriteBackupListVersions now handles (and reports) backup files with a\r\n  future date.\r\n- ENH: Allowing to configure compare shell command via\r\n  g:WriteBackup_CompareShellCommand. \r\n- ENH: Added :WriteBackupDeleteLastBackup command. \r\n- ENH: Added [!] to the following commands to disable confirmation dialog and\r\n  override readonly target files: :WriteBackupRestoreFromPred, \r\n  :WriteBackupRestoreThisBackup, :WriteBackupOfSavedOriginal, \r\n  :WriteBackupDeleteLastBackup","package":"writebackupVersionControl.vba.gz","4":"writebackupVersionControl.vba.gz","src_id":"10046","5":"10046","creation_date":"1235671903","6":"1235671903"},{"0":"1829","vim_version":"7.0","1":"7.0","script_version":"1.41.021","2":"1.41.021","version_comment":"Split off documentation into separate help file. Now packaging as VimBall. ","3":"Split off documentation into separate help file. Now packaging as VimBall. ","package":"writebackupVersionControl.vba.gz","4":"writebackupVersionControl.vba.gz","src_id":"9982","5":"9982","creation_date":"1234799873","6":"1234799873"},{"0":"1829","vim_version":"7.0","1":"7.0","script_version":"1.40.020","2":"1.40.020","version_comment":"Renamed configuration variable from g:writebackup_DiffVertSplit to g:WriteBackup_DiffVertSplit. *** PLEASE UPDATE YOUR CONFIGURATION *** \r\nENH: Added :WriteBackupGoPrev, :WriteBackupGoNext and :WriteBackupGoOriginal commands. \r\nENH: :WriteBackupListVersions now includes backup dirspec if backups aren't done in the original file's directory. \r\nBF: :WriteBackupDiffWithPred failed to open the predecessor with the ':set autochdir' setting if the CWD has been (temporarily) changed. Now using absolute path for the :split command. \r\n:WriteBackupDiffWithPred doesn't jump to the predecessor window; it now moves the cursor back to the originating window; this feels more natural. \r\n:WriteBackupDiffWithPred now avoids that a previous (open) fold status at the cursor position is remembered and obscures the actual differences. \r\nAdded Windows detection via has('win64'). ","3":"Renamed configuration variable from g:writebackup_DiffVertSplit to g:WriteBackup_DiffVertSplit. *** PLEASE UPDATE YOUR CONFIGURATION *** \r\nENH: Added :WriteBackupGoPrev, :WriteBackupGoNext and :WriteBackupGoOriginal commands. \r\nENH: :WriteBackupListVersions now includes backup dirspec if backups aren't done in the original file's directory. \r\nBF: :WriteBackupDiffWithPred failed to open the predecessor with the ':set autochdir' setting if the CWD has been (temporarily) changed. Now using absolute path for the :split command. \r\n:WriteBackupDiffWithPred doesn't jump to the predecessor window; it now moves the cursor back to the originating window; this feels more natural. \r\n:WriteBackupDiffWithPred now avoids that a previous (open) fold status at the cursor position is remembered and obscures the actual differences. \r\nAdded Windows detection via has('win64'). ","package":"writebackupVersionControl.vim","4":"writebackupVersionControl.vim","src_id":"9971","5":"9971","creation_date":"1234633447","6":"1234633447"},{"0":"1829","vim_version":"7.0","1":"7.0","script_version":"1.20.010","2":"1.20.010","version_comment":"Minor change: Added -bar to all commands that do not take any arguments, so that these can be chained together.","3":"Minor change: Added -bar to all commands that do not take any arguments, so that these can be chained together.","package":"writebackupVersionControl.vim","4":"writebackupVersionControl.vim","src_id":"8838","5":"8838","creation_date":"1214198223","6":"1214198223"},{"0":"1829","vim_version":"7.0","1":"7.0","script_version":"1.20.009","2":"1.20.009","version_comment":"Small Enhancement: :WriteBackupListVersions and :WriteBackupDiffWithPred claimed \"no backups exist\" if option 'wildignore' hides the backup files. Now temporarily resetting the option before glob().  ","3":"Small Enhancement: :WriteBackupListVersions and :WriteBackupDiffWithPred claimed \"no backups exist\" if option 'wildignore' hides the backup files. Now temporarily resetting the option before glob().  ","package":"writebackupVersionControl.vim","4":"writebackupVersionControl.vim","src_id":"8105","5":"8105","creation_date":"1199068933","6":"1199068933"},{"0":"1829","vim_version":"7.0","1":"7.0","script_version":"1.20.008","2":"1.20.008","version_comment":"ENH: Added support for writing backup files into a different directory (either one static backup dir or relative to the original file). Now requires writebackup.vim version 1.20 or later. \r\nCommand :WriteBackupOfSavedOriginal now checks that the file is an original one. \r\nBF: :WriteBackupIsBackedUp doesn't deal correctly with filenames that contain special ex characters [%#!]. ","3":"ENH: Added support for writing backup files into a different directory (either one static backup dir or relative to the original file). Now requires writebackup.vim version 1.20 or later. \r\nCommand :WriteBackupOfSavedOriginal now checks that the file is an original one. \r\nBF: :WriteBackupIsBackedUp doesn't deal correctly with filenames that contain special ex characters [%#!]. ","package":"writebackupVersionControl.vim","4":"writebackupVersionControl.vim","src_id":"7689","5":"7689","creation_date":"1190099848","6":"1190099848"},{"0":"1829","vim_version":"7.0","1":"7.0","script_version":"1.00.006","2":"1.00.006","version_comment":"Initial upload","3":"Initial upload","package":"writebackupVersionControl.vim","4":"writebackupVersionControl.vim","src_id":"6884","5":"6884","creation_date":"1174026181","6":"1174026181"}]},"1828":{"script_id":"1828","0":"1828","script_name":"writebackup","1":"writebackup","script_type":"utility","2":"utility","summary":"Write backups of current file with date file extension.","3":"Write backups of current file with date file extension.","description":"DESCRIPTION\r\nThis is a poor man's revision control system, a primitive alternative to CVS,\r\nRCS, Subversion, etc., which works with no additional software and almost any\r\nfile system.\r\nThe :WriteBackup command writes subsequent backups of the current file with a\r\n'current date + counter' file extension (format '.YYYYMMDD[a-z]'). The first\r\nbackup of a day has letter 'a' appended, the next 'b', and so on. (So that a\r\nfile can be backed up up to 26 times on any given day.)\r\n\r\nBy default, backups are created in the same directory as the original file,\r\nbut they can also be placed in a directory relative to the original file, or\r\nin one common backup directory for all files (similar to Vim's 'backupdir'\r\noption), or even in a file-specific location that is determined via a\r\nuser-provided callback function.\r\n\r\nSEE ALSO\r\n- The writebackupVersionControl.vim plugin (vimscript #1829) complements\r\n  this script with additional commands and enhances the :WriteBackup command\r\n  with more checks, but is not required.\r\n- The writebackupToAdjacentDir.vim plugin (vimscript #3107) implements a\r\n  WriteBackup-dynamic-backupdir configuration that puts the backup files in\r\n  an adjacent backup directory if one exists. This helps where the backups\r\n  cannot be placed into the same directory.\r\n- The writebackupAutomator.vim plugin (vimscript #3940) automatically writes\r\n  a backup on a day's first write of a file that was backed up in the past,\r\n  but not yet today. It can be your safety net when you forget to make a\r\n  backup.\r\n\r\nUSAGE\r\n:WriteBackup[!]\r\n                        Write the whole current buffer to the next available\r\n                        backup file with a '.YYYYMMDD[a-z]' file extension.\r\n                        If the last backup is identical with the current\r\n                        buffer contents, no (redundant) backup is written.\r\n                        With [!], creation of a new backup file is forced:\r\n                        - even if the last backup is identical\r\n                        - even when no more backup versions (for this day) are\r\n                          available (the last '.YYYYMMDDz' backup gets\r\n                          overwritten, even if it is readonly)\r\n                        - even if writing of backups is disallowed by a\r\n                          configured g:WriteBackup_ExclusionPredicates\r\n\r\nPS: In addition to this Vim plugin, I also provide the basic writebackup\r\nfunctionality outside of Vim as VBScript and Bash Shell script versions at\r\nhttp:\/\/ingo-karkat.de\/downloads\/tools\/writebackup\/index.html","4":"DESCRIPTION\r\nThis is a poor man's revision control system, a primitive alternative to CVS,\r\nRCS, Subversion, etc., which works with no additional software and almost any\r\nfile system.\r\nThe :WriteBackup command writes subsequent backups of the current file with a\r\n'current date + counter' file extension (format '.YYYYMMDD[a-z]'). The first\r\nbackup of a day has letter 'a' appended, the next 'b', and so on. (So that a\r\nfile can be backed up up to 26 times on any given day.)\r\n\r\nBy default, backups are created in the same directory as the original file,\r\nbut they can also be placed in a directory relative to the original file, or\r\nin one common backup directory for all files (similar to Vim's 'backupdir'\r\noption), or even in a file-specific location that is determined via a\r\nuser-provided callback function.\r\n\r\nSEE ALSO\r\n- The writebackupVersionControl.vim plugin (vimscript #1829) complements\r\n  this script with additional commands and enhances the :WriteBackup command\r\n  with more checks, but is not required.\r\n- The writebackupToAdjacentDir.vim plugin (vimscript #3107) implements a\r\n  WriteBackup-dynamic-backupdir configuration that puts the backup files in\r\n  an adjacent backup directory if one exists. This helps where the backups\r\n  cannot be placed into the same directory.\r\n- The writebackupAutomator.vim plugin (vimscript #3940) automatically writes\r\n  a backup on a day's first write of a file that was backed up in the past,\r\n  but not yet today. It can be your safety net when you forget to make a\r\n  backup.\r\n\r\nUSAGE\r\n:WriteBackup[!]\r\n                        Write the whole current buffer to the next available\r\n                        backup file with a '.YYYYMMDD[a-z]' file extension.\r\n                        If the last backup is identical with the current\r\n                        buffer contents, no (redundant) backup is written.\r\n                        With [!], creation of a new backup file is forced:\r\n                        - even if the last backup is identical\r\n                        - even when no more backup versions (for this day) are\r\n                          available (the last '.YYYYMMDDz' backup gets\r\n                          overwritten, even if it is readonly)\r\n                        - even if writing of backups is disallowed by a\r\n                          configured g:WriteBackup_ExclusionPredicates\r\n\r\nPS: In addition to this Vim plugin, I also provide the basic writebackup\r\nfunctionality outside of Vim as VBScript and Bash Shell script versions at\r\nhttp:\/\/ingo-karkat.de\/downloads\/tools\/writebackup\/index.html","install_details":"INSTALLATION\r\nThe code is hosted in a Git repo at\r\n    https:\/\/github.com\/inkarkat\/vim-writebackup\r\nYou can use your favorite plugin manager, or \"git clone\" into a directory used\r\nfor Vim packages. Releases are on the \"stable\" branch, the latest unstable\r\ndevelopment snapshot on \"master\".\r\n\r\nThis script is also packaged as a vimball. If you have the \"gunzip\"\r\ndecompressor in your PATH, simply edit the *.vmb.gz package in Vim; otherwise,\r\ndecompress the archive first, e.g. using WinZip. Inside Vim, install by\r\nsourcing the vimball or via the :UseVimball command.\r\n    vim writebackup*.vmb.gz\r\n    :so %\r\nTo uninstall, use the :RmVimball command.\r\n\r\nDEPENDENCIES\r\n- Requires Vim 7.0 or higher.\r\n- Requires the ingo-library.vim plugin (vimscript #4433), version 1.012 or\r\n  higher.\r\n- The writebackupVersionControl.vim plugin (vimscript #1829) complements\r\n  this script with additional commands and enhances the :WriteBackup command\r\n  with more checks, but is not required.\r\n\r\nCONFIGURATION\r\nFor a permanent configuration, put the following commands into your vimrc:\r\n\r\nTo put backups into another directory, specify a backup directory via\r\n    let g:WriteBackup_BackupDir = 'D:\\backups'\r\nPlease note that this setting may result in name clashes when backing up files\r\nwith the same name from different directories!\r\n\r\nA directory starting with '.\/' or '..\/' (or the backslashed-variants '.\\' for\r\nMS-DOS et al.) puts the backup file relative to where the backed-up file is.\r\nThe leading '.' is replaced with the path name of the current file:\r\n    let g:WriteBackup_BackupDir = '.\/backups'\r\n\r\nBackup creation will fail if the backup directory does not exist, the\r\ndirectory will NOT be created automatically!\r\n\r\nIf you want to automatically create a non-existing backup directory,\r\ndynamically determine the backup directory based on the current filespec or\r\nany other changing circumstances, you can set a custom callback function:\r\n\r\n    function MyResolveBackupDir(originalFilespec, isQueryOnly)\r\n        ...\r\n        return backupDirspec\r\n    endfunction\r\n    let g:WriteBackup_BackupDir = function('MyResolveBackupDir')\r\n\r\nThis function will be invoked each time a backup is about to be written. The\r\nfunction must accept one String argument that represents the filespec of the\r\noriginal file (the filespec can be relative or absolute, like the output of\r\nexpand('%')), and one Number that represents a boolean flag whether this is\r\njust a query (no backup is about to be written, so don't cause any permanent\r\nside effects).\r\nIt must return a String representing the backup dirspec (again either relative\r\nor absolute, '.' for current directory, please no trailing path separator).\r\nThrow an exception if you want to abort the backup. If the exception starts\r\nwith 'WriteBackup:', the rest of the exception text will be nicely printed as\r\nthe error text to the user. To just forbid backup creation for certain files,\r\nuse g:WriteBackup_ExclusionPredicates instead.\r\n\r\nRemember that because of the alphabetic numbering, it doesn't make much sense\r\nif the backup directory changes for subsequent backups of the same file. Use\r\nthis functionality to adapt the backup location based on filespec, file type,\r\navailability of a backup medium, etc., or to inject additional side effects\r\nlike creating backup directories, pruning old backups, etc.\r\n\r\nYou can override this global setting for specific buffers via a buffer-scoped\r\nvariable, which can be set by an autocmd, ftplugin, or manually:\r\n    let b:WriteBackup_BackupDir = 'X:\\special\\backup\\folder'\r\n\r\nIf the writebackupVersionControl plugin is installed, no backup is written if\r\nthere is an identical predecessor, so you don't need to remember whether\r\nyou've already backed up the current file; no redundant backups will be\r\ncreated.\r\nIf you don't like this check, turn it off via:\r\n    let g:WriteBackup_AvoidIdenticalBackups = 0\r\nIt occasionally happens that an identical backup is kept lying around, e.g.\r\nwhen reverting to the backup without removing it. Since that backup would\r\nmisleadingly date the next change much earlier than it actually happened,\r\nwritebackup automatically renames the earlier backup if it would be identical\r\nto the first backup created today.\r\nIf you don't want such an automatic rename and instead get the \"is already\r\nbacked up\" error, turn off redate via:\r\n    let g:WriteBackup_AvoidIdenticalBackups = 1\r\nThis reinstates the old behavior of writebackup versions < 3.00.\r\n\r\nTo disallow a backup for certain files, you can define a List of expressions\r\nor Funcrefs that are evaluated; if one returns 1 (or a non-empty String, in\r\nwhich case this will be the error message), backup of the buffer will be\r\nskipped (unless :WriteBackup! is used).\r\n    let g:writebackup_ExclusionPredicates = [\r\n    \\   'expand(\"%:e\") ==? \"bak\"',\r\n    \\   function('ExcludeScratchFiles')\r\n    \\]\r\n\r\nIn case you already have other custom Vim commands starting with W, you can\r\ndefine a shorter command alias ':W' in your vimrc to save some keystrokes. I\r\nlike the parallelism between ':w' for a normal write and ':W' for a backup\r\nwrite.\r\n    command -bar -bang W :WriteBackup<bang>","5":"INSTALLATION\r\nThe code is hosted in a Git repo at\r\n    https:\/\/github.com\/inkarkat\/vim-writebackup\r\nYou can use your favorite plugin manager, or \"git clone\" into a directory used\r\nfor Vim packages. Releases are on the \"stable\" branch, the latest unstable\r\ndevelopment snapshot on \"master\".\r\n\r\nThis script is also packaged as a vimball. If you have the \"gunzip\"\r\ndecompressor in your PATH, simply edit the *.vmb.gz package in Vim; otherwise,\r\ndecompress the archive first, e.g. using WinZip. Inside Vim, install by\r\nsourcing the vimball or via the :UseVimball command.\r\n    vim writebackup*.vmb.gz\r\n    :so %\r\nTo uninstall, use the :RmVimball command.\r\n\r\nDEPENDENCIES\r\n- Requires Vim 7.0 or higher.\r\n- Requires the ingo-library.vim plugin (vimscript #4433), version 1.012 or\r\n  higher.\r\n- The writebackupVersionControl.vim plugin (vimscript #1829) complements\r\n  this script with additional commands and enhances the :WriteBackup command\r\n  with more checks, but is not required.\r\n\r\nCONFIGURATION\r\nFor a permanent configuration, put the following commands into your vimrc:\r\n\r\nTo put backups into another directory, specify a backup directory via\r\n    let g:WriteBackup_BackupDir = 'D:\\backups'\r\nPlease note that this setting may result in name clashes when backing up files\r\nwith the same name from different directories!\r\n\r\nA directory starting with '.\/' or '..\/' (or the backslashed-variants '.\\' for\r\nMS-DOS et al.) puts the backup file relative to where the backed-up file is.\r\nThe leading '.' is replaced with the path name of the current file:\r\n    let g:WriteBackup_BackupDir = '.\/backups'\r\n\r\nBackup creation will fail if the backup directory does not exist, the\r\ndirectory will NOT be created automatically!\r\n\r\nIf you want to automatically create a non-existing backup directory,\r\ndynamically determine the backup directory based on the current filespec or\r\nany other changing circumstances, you can set a custom callback function:\r\n\r\n    function MyResolveBackupDir(originalFilespec, isQueryOnly)\r\n        ...\r\n        return backupDirspec\r\n    endfunction\r\n    let g:WriteBackup_BackupDir = function('MyResolveBackupDir')\r\n\r\nThis function will be invoked each time a backup is about to be written. The\r\nfunction must accept one String argument that represents the filespec of the\r\noriginal file (the filespec can be relative or absolute, like the output of\r\nexpand('%')), and one Number that represents a boolean flag whether this is\r\njust a query (no backup is about to be written, so don't cause any permanent\r\nside effects).\r\nIt must return a String representing the backup dirspec (again either relative\r\nor absolute, '.' for current directory, please no trailing path separator).\r\nThrow an exception if you want to abort the backup. If the exception starts\r\nwith 'WriteBackup:', the rest of the exception text will be nicely printed as\r\nthe error text to the user. To just forbid backup creation for certain files,\r\nuse g:WriteBackup_ExclusionPredicates instead.\r\n\r\nRemember that because of the alphabetic numbering, it doesn't make much sense\r\nif the backup directory changes for subsequent backups of the same file. Use\r\nthis functionality to adapt the backup location based on filespec, file type,\r\navailability of a backup medium, etc., or to inject additional side effects\r\nlike creating backup directories, pruning old backups, etc.\r\n\r\nYou can override this global setting for specific buffers via a buffer-scoped\r\nvariable, which can be set by an autocmd, ftplugin, or manually:\r\n    let b:WriteBackup_BackupDir = 'X:\\special\\backup\\folder'\r\n\r\nIf the writebackupVersionControl plugin is installed, no backup is written if\r\nthere is an identical predecessor, so you don't need to remember whether\r\nyou've already backed up the current file; no redundant backups will be\r\ncreated.\r\nIf you don't like this check, turn it off via:\r\n    let g:WriteBackup_AvoidIdenticalBackups = 0\r\nIt occasionally happens that an identical backup is kept lying around, e.g.\r\nwhen reverting to the backup without removing it. Since that backup would\r\nmisleadingly date the next change much earlier than it actually happened,\r\nwritebackup automatically renames the earlier backup if it would be identical\r\nto the first backup created today.\r\nIf you don't want such an automatic rename and instead get the \"is already\r\nbacked up\" error, turn off redate via:\r\n    let g:WriteBackup_AvoidIdenticalBackups = 1\r\nThis reinstates the old behavior of writebackup versions < 3.00.\r\n\r\nTo disallow a backup for certain files, you can define a List of expressions\r\nor Funcrefs that are evaluated; if one returns 1 (or a non-empty String, in\r\nwhich case this will be the error message), backup of the buffer will be\r\nskipped (unless :WriteBackup! is used).\r\n    let g:writebackup_ExclusionPredicates = [\r\n    \\   'expand(\"%:e\") ==? \"bak\"',\r\n    \\   function('ExcludeScratchFiles')\r\n    \\]\r\n\r\nIn case you already have other custom Vim commands starting with W, you can\r\ndefine a shorter command alias ':W' in your vimrc to save some keystrokes. I\r\nlike the parallelism between ':w' for a normal write and ':W' for a backup\r\nwrite.\r\n    command -bar -bang W :WriteBackup<bang>","first_name":"Ingo","6":"Ingo","last_name":"Karkat","7":"Karkat","releases":[{"0":"1828","vim_version":"7.0","1":"7.0","script_version":"3.10","2":"3.10","version_comment":"- ENH: Add g:WriteBackup_ExclusionPredicates to disallow writing of backups (unless it is forced via :WriteBackup!), e.g. when another (proper) revision control system (like Git) is used.","3":"- ENH: Add g:WriteBackup_ExclusionPredicates to disallow writing of backups (unless it is forced via :WriteBackup!), e.g. when another (proper) revision control system (like Git) is used.","package":"writebackup-3.10.vmb.gz","4":"writebackup-3.10.vmb.gz","src_id":"27095","5":"27095","creation_date":"1585885579","6":"1585885579"},{"0":"1828","vim_version":"7.0","1":"7.0","script_version":"3.01","2":"3.01","version_comment":"- :WriteBackup now aborts on error.\r\n- Add dependency to ingo-library (vimscript #4433). *** You need to separately install ingo-library (vimscript #4433) version 1.012 (or higher)! ***","3":"- :WriteBackup now aborts on error.\r\n- Add dependency to ingo-library (vimscript #4433). *** You need to separately install ingo-library (vimscript #4433) version 1.012 (or higher)! ***","package":"writebackup-3.01.vmb.gz","4":"writebackup-3.01.vmb.gz","src_id":"21400","5":"21400","creation_date":"1391028063","6":"1391028063"},{"0":"1828","vim_version":"7.0","1":"7.0","script_version":"3.00","2":"3.00","version_comment":"- ENH: New default \"redate\" for g:WriteBackup_AvoidIdenticalBackups that renames an identical backup from an earlier date to be the first backup of today. \r\n- Using :keepalt instead of a temporary :set cpo-=A. ","3":"- ENH: New default \"redate\" for g:WriteBackup_AvoidIdenticalBackups that renames an identical backup from an earlier date to be the first backup of today. \r\n- Using :keepalt instead of a temporary :set cpo-=A. ","package":"writebackup.vba.gz","4":"writebackup.vba.gz","src_id":"17474","5":"17474","creation_date":"1329402689","6":"1329402689"},{"0":"1828","vim_version":"7.0","1":"7.0","script_version":"2.10","2":"2.10","version_comment":"Replaced simple filespec escaping with built-in fnameescape() function (or\r\nemulation for Vim 7.0 \/ 7.1) via escapings.vim wrapper.","3":"Replaced simple filespec escaping with built-in fnameescape() function (or\r\nemulation for Vim 7.0 \/ 7.1) via escapings.vim wrapper.","package":"writebackup.vba.gz","4":"writebackup.vba.gz","src_id":"10694","5":"10694","creation_date":"1243518692","6":"1243518692"},{"0":"1828","vim_version":"7.0","1":"7.0","script_version":"2.00","2":"2.00","version_comment":"- Using separate autoload script to help speed up VIM startup. This is an\r\n  incompatible change that also requires the corresponding\r\n  writebackupVersionControl plugin version. *** PLEASE UPDATE\r\n  writebackupVersionControl (vimscript #1829), too, if you're using it ***\r\n- ENH: Disallowing backup of backup file if the writebackupVersionControl\r\n  plugin is installed. \r\n- ENH: No backup is written if there is an identical previous backup. This\r\n  requires the writebackupVersionControl plugin and can be configured via\r\n  g:WriteBackup_AvoidIdenticalBackups. ","3":"- Using separate autoload script to help speed up VIM startup. This is an\r\n  incompatible change that also requires the corresponding\r\n  writebackupVersionControl plugin version. *** PLEASE UPDATE\r\n  writebackupVersionControl (vimscript #1829), too, if you're using it ***\r\n- ENH: Disallowing backup of backup file if the writebackupVersionControl\r\n  plugin is installed. \r\n- ENH: No backup is written if there is an identical previous backup. This\r\n  requires the writebackupVersionControl plugin and can be configured via\r\n  g:WriteBackup_AvoidIdenticalBackups. ","package":"writebackup.vba.gz","4":"writebackup.vba.gz","src_id":"10045","5":"10045","creation_date":"1235671898","6":"1235671898"},{"0":"1828","vim_version":"7.0","1":"7.0","script_version":"1.31.013","2":"1.31.013","version_comment":"Split off documentation into separate help file. Now packaging as VimBall. ","3":"Split off documentation into separate help file. Now packaging as VimBall. ","package":"writebackup.vba.gz","4":"writebackup.vba.gz","src_id":"9980","5":"9980","creation_date":"1234799283","6":"1234799283"},{"0":"1828","vim_version":"7.0","1":"7.0","script_version":"1.30.011","2":"1.30.011","version_comment":"ENH: The backup directory can now be determined dynamically through a callback function. \r\nRenamed configuration variable from g:writebackup_BackupDir to g:WriteBackup_BackupDir. *** PLEASE UPDATE YOUR CONFIGURATION ***\r\nBF: Now also allowing relative backup dir in an upper directory (i.e. g:WriteBackup_BackupDir starting with '..\/'. \r\nBF: Unnamed buffers were backed up as '.YYYYMMDDa'. \r\nNow setting v:errmsg on errors and using ErrorMsg instead of Error highlight group. ","3":"ENH: The backup directory can now be determined dynamically through a callback function. \r\nRenamed configuration variable from g:writebackup_BackupDir to g:WriteBackup_BackupDir. *** PLEASE UPDATE YOUR CONFIGURATION ***\r\nBF: Now also allowing relative backup dir in an upper directory (i.e. g:WriteBackup_BackupDir starting with '..\/'. \r\nBF: Unnamed buffers were backed up as '.YYYYMMDDa'. \r\nNow setting v:errmsg on errors and using ErrorMsg instead of Error highlight group. ","package":"writebackup.vim","4":"writebackup.vim","src_id":"9950","5":"9950","creation_date":"1234382759","6":"1234382759"},{"0":"1828","vim_version":"7.0","1":"7.0","script_version":"1.20.006","2":"1.20.006","version_comment":"Minor change: Added -bar to :WriteBackup, so that commands can be chained together.  ","3":"Minor change: Added -bar to :WriteBackup, so that commands can be chained together.  ","package":"writebackup.vim","4":"writebackup.vim","src_id":"8839","5":"8839","creation_date":"1214198442","6":"1214198442"},{"0":"1828","vim_version":"7.0","1":"7.0","script_version":"1.20.005","2":"1.20.005","version_comment":"ENH: Added support for writing backup files into a different directory (either one static backup dir or relative to the original file) via g:writebackup_BackupDir configuration, as suggested by Vincent DiCarlo. \r\nNow requiring VIM 7.0 or later, because it's using lists. \r\nBF: Special ex command characters ' \\%#' must be escaped for ':w' command. ","3":"ENH: Added support for writing backup files into a different directory (either one static backup dir or relative to the original file) via g:writebackup_BackupDir configuration, as suggested by Vincent DiCarlo. \r\nNow requiring VIM 7.0 or later, because it's using lists. \r\nBF: Special ex command characters ' \\%#' must be escaped for ':w' command. ","package":"writebackup.vim","4":"writebackup.vim","src_id":"7688","5":"7688","creation_date":"1190099477","6":"1190099477"},{"0":"1828","vim_version":"6.0","1":"6.0","script_version":"1.00.004","2":"1.00.004","version_comment":"Initial upload","3":"Initial upload","package":"writebackup.vim","4":"writebackup.vim","src_id":"6883","5":"6883","creation_date":"1174025811","6":"1174025811"}]},"1827":{"script_id":"1827","0":"1827","script_name":"smp","1":"smp","script_type":"color scheme","2":"color scheme","summary":"You will never bored, bcoz its simple","3":"You will never bored, bcoz its simple","description":"Ultra nice colors may be very good for kids or just for looking, for long time simple color scheme good for both bright and low light situation. Works great for eyes brain and work.","4":"Ultra nice colors may be very good for kids or just for looking, for long time simple color scheme good for both bright and low light situation. Works great for eyes brain and work.","install_details":"Just drop it in color directory and \r\nadd following lines in vimrc\r\n\r\ncolo smp","5":"Just drop it in color directory and \r\nadd following lines in vimrc\r\n\r\ncolo smp","first_name":"vijayandra","6":"vijayandra","last_name":"singh","7":"singh","releases":[{"0":"1827","vim_version":"6.0","1":"6.0","script_version":"1.2","2":"1.2","version_comment":"Initial upload","3":"Initial upload","package":"smp.vim","4":"smp.vim","src_id":"6875","5":"6875","creation_date":"1173781800","6":"1173781800"}]},"1826":{"script_id":"1826","0":"1826","script_name":"Hints for C Library Functions","1":"Hints for C Library Functions","script_type":"ftplugin","2":"ftplugin","summary":"while typing a C function, a prototype is shown (man3 based)","3":"while typing a C function, a prototype is shown (man3 based)","description":"This script may be manually sourced or, if placed in .vim\/ftplugin\/c, will be automatically sourced whenever a C file is edited (which is where vimball will put it).  The prototypes within it are based on gcc's \/usr\/share\/man\/man3 directory.\r\n\r\nThis plugin is truly simple to use: after one has typed a function name, a protype \"hint\" will be shown.\r\n \r\nex.    printf(\r\n\r\n       will result in\r\n\r\n          int printf(const char * format, ...)\r\n\r\n       being echo'd at the bottom of the display.\r\n\r\nYou'll probably want your cmdheight option set to at least two (ie.  set ch=2).\r\n\r\n(see vimscript#1825 for man-2 function hints)\r\n(see http:\/\/www.drchip.org\/astronaut\/vim\/index.html#HINTSMAN3 for the latest version)\r\n\r\n","4":"This script may be manually sourced or, if placed in .vim\/ftplugin\/c, will be automatically sourced whenever a C file is edited (which is where vimball will put it).  The prototypes within it are based on gcc's \/usr\/share\/man\/man3 directory.\r\n\r\nThis plugin is truly simple to use: after one has typed a function name, a protype \"hint\" will be shown.\r\n \r\nex.    printf(\r\n\r\n       will result in\r\n\r\n          int printf(const char * format, ...)\r\n\r\n       being echo'd at the bottom of the display.\r\n\r\nYou'll probably want your cmdheight option set to at least two (ie.  set ch=2).\r\n\r\n(see vimscript#1825 for man-2 function hints)\r\n(see http:\/\/www.drchip.org\/astronaut\/vim\/index.html#HINTSMAN3 for the latest version)\r\n\r\n","install_details":"1. Make sure you have and are using an up-to-date version of vimball (see vimscript#1502)\r\n   (if you have vim 7.1a or later, you probably can skip this step)\r\n2. vim hints_man3.vba.gz\r\n     :so %\r\n     :q\r\n","5":"1. Make sure you have and are using an up-to-date version of vimball (see vimscript#1502)\r\n   (if you have vim 7.1a or later, you probably can skip this step)\r\n2. vim hints_man3.vba.gz\r\n     :so %\r\n     :q\r\n","first_name":"Charles","6":"Charles","last_name":"Campbell","7":"Campbell","releases":[{"0":"1826","vim_version":"7.0","1":"7.0","script_version":"2","2":"2","version_comment":"Improvements to the prototype from manpage extraction scripts yielded some more function prototypes","3":"Improvements to the prototype from manpage extraction scripts yielded some more function prototypes","package":"hints_man3.vba.gz","4":"hints_man3.vba.gz","src_id":"6878","5":"6878","creation_date":"1173852967","6":"1173852967"},{"0":"1826","vim_version":"7.0","1":"7.0","script_version":"1","2":"1","version_comment":"Initial upload","3":"Initial upload","package":"hints_man3.vba.gz","4":"hints_man3.vba.gz","src_id":"6872","5":"6872","creation_date":"1173780101","6":"1173780101"}]},"1825":{"script_id":"1825","0":"1825","script_name":"Hints for C Library Functions","1":"Hints for C Library Functions","script_type":"ftplugin","2":"ftplugin","summary":"while typing a C function, a prototype is shown (man2 based)","3":"while typing a C function, a prototype is shown (man2 based)","description":"This script may be manually sourced or, if placed in .vim\/ftplugin\/c, will be automatically sourced whenever a C file is edited (which is where vimball will put it).  The prototypes within it are based on gcc's \/usr\/share\/man\/man2 directory.\r\n\r\nThis plugin is truly simple to use: after one has typed a function name, a protype \"hint\" will be shown.\r\n \r\nex.    select(\r\n\r\n       will result in\r\n\r\n          int select(int nfds, fd_set * readfds, fd_set * writefds, fd_set * exceptfds, struct timeval * utimeout)\r\n\r\n       being echo'd at the bottom of the display.\r\n\r\nYou'll probably want your cmdheight option set to at least two (ie.  set ch=2). \r\n\r\n(see vimscript#1826 for man-3 based function hints)\r\n(see http:\/\/www.drchip.org\/astronaut\/vim\/index.html#HINTSMAN2 for the latest version)","4":"This script may be manually sourced or, if placed in .vim\/ftplugin\/c, will be automatically sourced whenever a C file is edited (which is where vimball will put it).  The prototypes within it are based on gcc's \/usr\/share\/man\/man2 directory.\r\n\r\nThis plugin is truly simple to use: after one has typed a function name, a protype \"hint\" will be shown.\r\n \r\nex.    select(\r\n\r\n       will result in\r\n\r\n          int select(int nfds, fd_set * readfds, fd_set * writefds, fd_set * exceptfds, struct timeval * utimeout)\r\n\r\n       being echo'd at the bottom of the display.\r\n\r\nYou'll probably want your cmdheight option set to at least two (ie.  set ch=2). \r\n\r\n(see vimscript#1826 for man-3 based function hints)\r\n(see http:\/\/www.drchip.org\/astronaut\/vim\/index.html#HINTSMAN2 for the latest version)","install_details":"1. Make sure you have and are using an up-to-date version of vimball (see vimscript#1502)\r\n    (if you have vim 7.1a or later, you probably can skip this step)\r\n2. vim hints_man3.vba.gz\r\n     :so %\r\n     :q\r\n","5":"1. Make sure you have and are using an up-to-date version of vimball (see vimscript#1502)\r\n    (if you have vim 7.1a or later, you probably can skip this step)\r\n2. vim hints_man3.vba.gz\r\n     :so %\r\n     :q\r\n","first_name":"Charles","6":"Charles","last_name":"Campbell","7":"Campbell","releases":[{"0":"1825","vim_version":"7.0","1":"7.0","script_version":"1","2":"1","version_comment":"See a prototype while entering a function call (man2 based)","3":"See a prototype while entering a function call (man2 based)","package":"hints_man2.vba.gz","4":"hints_man2.vba.gz","src_id":"6877","5":"6877","creation_date":"1173852767","6":"1173852767"}]},"1824":{"script_id":"1824","0":"1824","script_name":"withdrawn","1":"withdrawn","script_type":"ftplugin","2":"ftplugin","summary":"withdrawn","3":"withdrawn","description":"Sigh -- another snafu caused by vim.sf.net not responding to an upload","4":"Sigh -- another snafu caused by vim.sf.net not responding to an upload","install_details":"withdrawn","5":"withdrawn","first_name":"Charles","6":"Charles","last_name":"Campbell","7":"Campbell","releases":[{"0":"1824","vim_version":"6.0","1":"6.0","script_version":"1","2":"1","version_comment":"withdrawn","3":"withdrawn","package":"Withdrawn.vim","4":"Withdrawn.vim","src_id":"6873","5":"6873","creation_date":"1173780430","6":"1173780430"}]},"1823":{"script_id":"1823","0":"1823","script_name":"NetSend.vim","1":"NetSend.vim","script_type":"utility","2":"utility","summary":"NetSend.vim: Plugin for sending messages using MS net send","3":"NetSend.vim: Plugin for sending messages using MS net send","description":"Plugin for sending messages with the 'net send' MS command.\r\nIt keeps the name of the users you send messages in a file and you can access them with the <tab> key.\r\nNavigation through menu (Plugin->NetSend->...) you can send messages, add users and remove them.\r\nYou can also open the file with the user names and edit directly.\r\n\r\nUsage:\r\n----------\r\nYou can use the menu in \"Plugin->NetSend-> or:\r\nInsert ':NetSend user_name message to this user'\r\n    and user_name will reicive a message saying: 'myUser says: message to this user'\r\nInsert :NetSent <tab> to see the list of users you have stored.\r\nInsert :NetSent r<tab> to see all the users beginning by 'r'\r\nInsert: NetSendCC user1 user2 user3<ENTER>\r\n    to send the same message to several users at a time (or :NetSendBCC if you wish)\r\n\r\nTo edit the list of users just open the file used in the g:NetSend_File. You can do it Typing :EditNetSend\r\n\r\nTODO: write the unix\/linux version (smbclient -M MS-Windows-host-name OR talk)","4":"Plugin for sending messages with the 'net send' MS command.\r\nIt keeps the name of the users you send messages in a file and you can access them with the <tab> key.\r\nNavigation through menu (Plugin->NetSend->...) you can send messages, add users and remove them.\r\nYou can also open the file with the user names and edit directly.\r\n\r\nUsage:\r\n----------\r\nYou can use the menu in \"Plugin->NetSend-> or:\r\nInsert ':NetSend user_name message to this user'\r\n    and user_name will reicive a message saying: 'myUser says: message to this user'\r\nInsert :NetSent <tab> to see the list of users you have stored.\r\nInsert :NetSent r<tab> to see all the users beginning by 'r'\r\nInsert: NetSendCC user1 user2 user3<ENTER>\r\n    to send the same message to several users at a time (or :NetSendBCC if you wish)\r\n\r\nTo edit the list of users just open the file used in the g:NetSend_File. You can do it Typing :EditNetSend\r\n\r\nTODO: write the unix\/linux version (smbclient -M MS-Windows-host-name OR talk)","install_details":"1. Copy the NetSend.vim script to the $HOME\/.vim\/plugin or the\r\n    $HOME\/vimfiles\/plugin or the $VIM\/vimfiles directory.  Refer to the\r\n    ':help add-plugin', ':help add-global-plugin' and ':help runtimepath'\r\n    topics for more details about Vim plugins.\r\n2. Set the NetSend_File Vim variable in the .vimrc file to the location of a\r\n    file to store the user names.\r\n    Example: let g:NetSend_File = $HOME .\"\/_netSend_Users\"\r\n3. If you want a different message to be added to the message just add to\r\n    your .vimrc: let g:NetSend_msg = \"My initial message\"\r\n4. Restart Vim.\r\n\r\nFor those guys who use pathogen, the installation should be as simple as a git clone: \r\n\r\n$ cd ~\/.vim\/bundle \r\n$ git clone git:\/\/github.com\/vim-scripts\/NetSed.vim.git\r\n","5":"1. Copy the NetSend.vim script to the $HOME\/.vim\/plugin or the\r\n    $HOME\/vimfiles\/plugin or the $VIM\/vimfiles directory.  Refer to the\r\n    ':help add-plugin', ':help add-global-plugin' and ':help runtimepath'\r\n    topics for more details about Vim plugins.\r\n2. Set the NetSend_File Vim variable in the .vimrc file to the location of a\r\n    file to store the user names.\r\n    Example: let g:NetSend_File = $HOME .\"\/_netSend_Users\"\r\n3. If you want a different message to be added to the message just add to\r\n    your .vimrc: let g:NetSend_msg = \"My initial message\"\r\n4. Restart Vim.\r\n\r\nFor those guys who use pathogen, the installation should be as simple as a git clone: \r\n\r\n$ cd ~\/.vim\/bundle \r\n$ git clone git:\/\/github.com\/vim-scripts\/NetSed.vim.git\r\n","first_name":"J. Manuel","6":"J. Manuel","last_name":"Picaza","7":"Picaza","releases":[{"0":"1823","vim_version":"7.0","1":"7.0","script_version":"1.6","2":"1.6","version_comment":"The console output is analized and informs you if there was an error sending the message.Messages are saved in :messages during the current vim session.","3":"The console output is analized and informs you if there was an error sending the message.Messages are saved in :messages during the current vim session.","package":"NetSend.vim","4":"NetSend.vim","src_id":"7709","5":"7709","creation_date":"1190695226","6":"1190695226"},{"0":"1823","vim_version":"6.0","1":"6.0","script_version":"1.5","2":"1.5","version_comment":"Fixed little bug: Now you can  use ! as part of the message.","3":"Fixed little bug: Now you can  use ! as part of the message.","package":"NetSend.vim","4":"NetSend.vim","src_id":"7077","5":"7077","creation_date":"1178585881","6":"1178585881"},{"0":"1823","vim_version":"7.0","1":"7.0","script_version":"1.4","2":"1.4","version_comment":"Solve a bug related to 'Cancel' button in the message dialog box. ","3":"Solve a bug related to 'Cancel' button in the message dialog box. ","package":"NetSend.vim","4":"NetSend.vim","src_id":"6981","5":"6981","creation_date":"1176693180","6":"1176693180"},{"0":"1823","vim_version":"7.0","1":"7.0","script_version":"1.3","2":"1.3","version_comment":"Send Messages using 'net send'. Now you can send the same message to several users (Cc and Bcc).","3":"Send Messages using 'net send'. Now you can send the same message to several users (Cc and Bcc).","package":"NetSend.vim","4":"NetSend.vim","src_id":"6970","5":"6970","creation_date":"1176271962","6":"1176271962"},{"0":"1823","vim_version":"7.0","1":"7.0","script_version":"1.2","2":"1.2","version_comment":"Added compatibility with GetLatestVimScripts plugin.\r\nSome litle bugs fixed.\r\nNext Version: Send the same message to several users.\r\n","3":"Added compatibility with GetLatestVimScripts plugin.\r\nSome litle bugs fixed.\r\nNext Version: Send the same message to several users.\r\n","package":"NetSend.vim","4":"NetSend.vim","src_id":"6916","5":"6916","creation_date":"1175077789","6":"1175077789"},{"0":"1823","vim_version":"7.0","1":"7.0","script_version":"1.1","2":"1.1","version_comment":"Added a menu (Plugins->NetSend) for managging it with the mouse.\r\n","3":"Added a menu (Plugins->NetSend) for managging it with the mouse.\r\n","package":"NetSend.vim","4":"NetSend.vim","src_id":"6876","5":"6876","creation_date":"1173842302","6":"1173842302"},{"0":"1823","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"NetSend.vim","4":"NetSend.vim","src_id":"6869","5":"6869","creation_date":"1173769100","6":"1173769100"}]},"1822":{"script_id":"1822","0":"1822","script_name":"incfilesearch.vim","1":"incfilesearch.vim","script_type":"utility","2":"utility","summary":"Incremental search for files to edit using glob","3":"Incremental search for files to edit using glob","description":"Based on incbufswitch.vim (http:\/\/www.vim.org\/scripts\/script.php?script_id=685)\r\n\r\nUsage:\r\n(1) Define a normal key mapping to :IncFileSearch or leave the default of <C-O>\r\n(2) When activated, start typing the name of the buffer you want to switch to.\r\n(3) Press <BS> if you make an error\r\n(4) Press <CR> to edit the first buffer in the remaining match list\r\n(5) Press <ESC> to quit and continue editing the current buffer\r\n\r\nStill a little crude. Polish from vim experts appreciated!","4":"Based on incbufswitch.vim (http:\/\/www.vim.org\/scripts\/script.php?script_id=685)\r\n\r\nUsage:\r\n(1) Define a normal key mapping to :IncFileSearch or leave the default of <C-O>\r\n(2) When activated, start typing the name of the buffer you want to switch to.\r\n(3) Press <BS> if you make an error\r\n(4) Press <CR> to edit the first buffer in the remaining match list\r\n(5) Press <ESC> to quit and continue editing the current buffer\r\n\r\nStill a little crude. Polish from vim experts appreciated!","install_details":"(1) Copy to plugin directory\r\n(2) Start vim. Hit <C-O> and start typing a regexp. Or redefine the key mapping. Check out the script header.","5":"(1) Copy to plugin directory\r\n(2) Start vim. Hit <C-O> and start typing a regexp. Or redefine the key mapping. Check out the script header.","first_name":"Greg","6":"Greg","last_name":"McIntyre","7":"McIntyre","releases":[{"0":"1822","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"incfilesearch.vim","4":"incfilesearch.vim","src_id":"6863","5":"6863","creation_date":"1173731450","6":"1173731450"}]},"1821":{"script_id":"1821","0":"1821","script_name":"NAnt syntax","1":"NAnt syntax","script_type":"syntax","2":"syntax","summary":"Highlighting for nant build files","3":"Highlighting for nant build files","description":"A simple syntax script for NAnt build files (http:\/\/nant.sourceforge.net\/). Just highlights elements and attributes as extracted from the version 0.85 schema.","4":"A simple syntax script for NAnt build files (http:\/\/nant.sourceforge.net\/). Just highlights elements and attributes as extracted from the version 0.85 schema.","install_details":"","5":"","first_name":"Juan","6":"Juan","last_name":"Chanco","7":"Chanco","releases":[{"0":"1821","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"nant.vim","4":"nant.vim","src_id":"6862","5":"6862","creation_date":"1173721354","6":"1173721354"}]},"1820":{"script_id":"1820","0":"1820","script_name":"NAnt completion","1":"NAnt completion","script_type":"ftplugin","2":"ftplugin","summary":"XML omni-completion data for NAnt build files","3":"XML omni-completion data for NAnt build files","description":"File to allow Vim's xml autocompletion to work with NAnt build files (http:\/\/nant.sourceforge.net\/). Elements and attributes were taken from the 0.85 version schema.","4":"File to allow Vim's xml autocompletion to work with NAnt build files (http:\/\/nant.sourceforge.net\/). Elements and attributes were taken from the 0.85 version schema.","install_details":"Copy the nant.vim file in to ~\/.vim\/autoload\/xml\/\r\nNAnt files should be recognized as XML files, but you'll need to call \":XMLns nant\" to load this data. I have a one line nant.vim file in ~\/.vim\/ftplugin with the line \"XMLns nant\" in it.","5":"Copy the nant.vim file in to ~\/.vim\/autoload\/xml\/\r\nNAnt files should be recognized as XML files, but you'll need to call \":XMLns nant\" to load this data. I have a one line nant.vim file in ~\/.vim\/ftplugin with the line \"XMLns nant\" in it.","first_name":"Juan","6":"Juan","last_name":"Chanco","7":"Chanco","releases":[{"0":"1820","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"nant.vim","4":"nant.vim","src_id":"6861","5":"6861","creation_date":"1173720959","6":"1173720959"}]},"1819":{"script_id":"1819","0":"1819","script_name":"vimbuddy.vim","1":"vimbuddy.vim","script_type":"utility","2":"utility","summary":"Vimbuddy (update): An absolutely unuseful little thing","3":"Vimbuddy (update): An absolutely unuseful little thing","description":"An update to vimscript #8 for Vim 7 by the Gentoo guys.\r\n\r\nI'm neither the author nor the updator (if you are, drop me a line and I'll relinquish control of this page).\r\n\r\nPuts a smiley on your status line. Nose will rotate on <Left> and <Right>\r\nWill frown on errors and warnings","4":"An update to vimscript #8 for Vim 7 by the Gentoo guys.\r\n\r\nI'm neither the author nor the updator (if you are, drop me a line and I'll relinquish control of this page).\r\n\r\nPuts a smiley on your status line. Nose will rotate on <Left> and <Right>\r\nWill frown on errors and warnings","install_details":"Source vimbuddy.vim from your .vimrc or put into ~\/.vim\/plugin\/ then put the string \"%{VimBuddy()}\" into your 'statusline'","5":"Source vimbuddy.vim from your .vimrc or put into ~\/.vim\/plugin\/ then put the string \"%{VimBuddy()}\" into your 'statusline'","first_name":"Seth","6":"Seth","last_name":"House","7":"House","releases":[{"0":"1819","vim_version":"7.0","1":"7.0","script_version":"0.9.1-a","2":"0.9.1-a","version_comment":"Initial upload","3":"Initial upload","package":"vimbuddy.vim","4":"vimbuddy.vim","src_id":"6860","5":"6860","creation_date":"1173717350","6":"1173717350"}]},"1818":{"script_id":"1818","0":"1818","script_name":"Yankcode","1":"Yankcode","script_type":"utility","2":"utility","summary":"Paste syntax code to webpage quickly","3":"Paste syntax code to webpage quickly","description":"Many times when I using my old blog system, I fell in bad mood when I have to mix my source code with content, or no support for source code like syntax highlighted. And when I use vim\u00e2\u0080\u0099s script TOhtml to deal with these thing, I feel that it\u00e2\u0080\u0099s handy, but still not enough convenient. I have to choose and copy the html code by my hand, then add a something like <quoteblock class=\u00e2\u0080\u009dvimblock\u00e2\u0080\u009d>(\u00e2\u0080\u009dvimblock\u00e2\u0080\u009d is a user-defined CSS element, will be mention later) tag to differentiate these code from common <quoteblock>. It\u00e2\u0080\u0099s too inconvenient, also seems easy to be done with a script. So I wrote this.  \r\n\r\nWith this script, pasting syntax code is only: \"V\"(selection) and \":Yankcode\" and ctrl-v in editor.\r\n\r\nThe script based on TOhtml written by Bram Moolenarr. It convert the current selection to html using 2html, then get the body of html and wrap it with <blockquote class=\u00e2\u0080\u009dvimblock\u00e2\u0080\u009d>. In the end, it send the wrapped section of syntax code to clipboard for the further use.\r\n\r\nWelcome any advice.","4":"Many times when I using my old blog system, I fell in bad mood when I have to mix my source code with content, or no support for source code like syntax highlighted. And when I use vim\u00e2\u0080\u0099s script TOhtml to deal with these thing, I feel that it\u00e2\u0080\u0099s handy, but still not enough convenient. I have to choose and copy the html code by my hand, then add a something like <quoteblock class=\u00e2\u0080\u009dvimblock\u00e2\u0080\u009d>(\u00e2\u0080\u009dvimblock\u00e2\u0080\u009d is a user-defined CSS element, will be mention later) tag to differentiate these code from common <quoteblock>. It\u00e2\u0080\u0099s too inconvenient, also seems easy to be done with a script. So I wrote this.  \r\n\r\nWith this script, pasting syntax code is only: \"V\"(selection) and \":Yankcode\" and ctrl-v in editor.\r\n\r\nThe script based on TOhtml written by Bram Moolenarr. It convert the current selection to html using 2html, then get the body of html and wrap it with <blockquote class=\u00e2\u0080\u009dvimblock\u00e2\u0080\u009d>. In the end, it send the wrapped section of syntax code to clipboard for the further use.\r\n\r\nWelcome any advice.","install_details":"Copy to your plugin directory.\r\nYou also need specify CSS for using the code generate by this script.\r\nThe default CSS of your schema can be generated by TOhtml, though it will only generate the elements that used by current file, you can find a file with most kinds of elements to generate the basis and modify it when you need more elements.\r\nAfter generation, just copy the section between <!\u00e2\u0080\u0093 \u00e2\u0080\u0093> just below the <style type=\u00e2\u0080\u009dtext\/css\u00e2\u0080\u009d>, replace element name \u00e2\u0080\u009cbody\u00e2\u0080\u009d with \u00e2\u0080\u009c.vimblock\u00e2\u0080\u009d and append it to your CSS file( usually style.css).\r\nAfter have well defined your CSS, you can use the \"V\"(optional) and \":Yankcode\" and paste to editor with you syntax code in xhtml.\r\n\r\nMore  information including my css section and the effect of the script can be found at http:\/\/www.yasker.org\/en\/blog\/a-vim-script-for-pasting-syntax-code-to-webpage-33","5":"Copy to your plugin directory.\r\nYou also need specify CSS for using the code generate by this script.\r\nThe default CSS of your schema can be generated by TOhtml, though it will only generate the elements that used by current file, you can find a file with most kinds of elements to generate the basis and modify it when you need more elements.\r\nAfter generation, just copy the section between <!\u00e2\u0080\u0093 \u00e2\u0080\u0093> just below the <style type=\u00e2\u0080\u009dtext\/css\u00e2\u0080\u009d>, replace element name \u00e2\u0080\u009cbody\u00e2\u0080\u009d with \u00e2\u0080\u009c.vimblock\u00e2\u0080\u009d and append it to your CSS file( usually style.css).\r\nAfter have well defined your CSS, you can use the \"V\"(optional) and \":Yankcode\" and paste to editor with you syntax code in xhtml.\r\n\r\nMore  information including my css section and the effect of the script can be found at http:\/\/www.yasker.org\/en\/blog\/a-vim-script-for-pasting-syntax-code-to-webpage-33","first_name":"Sheng","6":"Sheng","last_name":"Yang","7":"Yang","releases":[{"0":"1818","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"yankcode.tar.gz","4":"yankcode.tar.gz","src_id":"6851","5":"6851","creation_date":"1173409435","6":"1173409435"}]},"1817":{"script_id":"1817","0":"1817","script_name":"buffers_search_and_replace","1":"buffers_search_and_replace","script_type":"utility","2":"utility","summary":"Simple but powerful buffer(s) search & replace tool","3":"Simple but powerful buffer(s) search & replace tool","description":"    The \"Buffers Search & Replace\" plugin is a simple but powerful buffer(s)\r\nsearch & replace tool. Search results can be set in the 'delete' category and replacement\r\ncan be performed on the remaining or deleted search results.\r\n\r\nPlease report any bugs or feature requests.\r\n\r\nAvailable commands :\r\n------------------------------\r\n    :Bs <search_regex>\r\n    :<range> Bsc <search_regex>\r\n\r\nThe 'Bs' command is searching in all the buffers and 'Bsc' only in the current buffer.\r\n\r\n    :Bsf <buffer_name_filter_regex> <search_regex>\r\n    :Bse <buffer_name_exclusion_regex> <search_regex>\r\n\r\nThe 'Bsf' command is searching in all the buffers whose name match <buffer_name_filter_regex> and\r\n'Bse' in all buffers whose name doesn't match <buffer_name_exclusion_regex>.\r\n\r\nDefault key mappings in the buffer with the results :\r\n---------------------------------------------------------------------\r\n  \"Space\"  : moves the cursor on the first result of the next buffer\r\n  \"Enter or Control-j\"   : shows or jumps to the result under the cursor\r\n  \"J\"  : enables or disables jumping on the buffer when pressing Enter or Control-j\r\n  \"A\"  : enables or disables auto-showing the context of the results when pressing j or k\r\n  \"d\" : deletes the current range search result (default: current line)\r\n           (the deleted search results are showed at the bottom of the buffer)\r\n  \"D\" : definitely deletes the current range search result (default: current line)\r\n  \"Q\"  : enables or disables auto-quitting the buffer results when jumping\r\n  \"O\"  : toggles between showing options or showing results\r\n  \"r\"  : replace action on the non-deleted searched results\r\n  \"R\"  : replace action on the deleted searched results\r\n  \"u\"  : replaces this search with a newer one (with the same keyword)\r\n  \"i\"  : enables or disables the search match highlighting on the buffer with the results\r\n  \"I\"  : enables or disables the search match highlighting on the other buffers (not the buffer with the results)\r\n  \"x\"  : enables or disables quite-full-screen\r\n  \"q\"  : deletes the buffer with the results\r\n  \"?\"  : toggles between showing help or showing results\r\n\r\nScreenshot : http:\/\/ioalex.net\/buffers_search_and_replace\/screenshot.png\r\nSmall demo video (ogg theora) : http:\/\/ioalex.net\/buffers_search_and_replace\/demo.ogv\r\n\r\nFor more information, contact me or read the more complete documentation at the start of the plugin file.","4":"    The \"Buffers Search & Replace\" plugin is a simple but powerful buffer(s)\r\nsearch & replace tool. Search results can be set in the 'delete' category and replacement\r\ncan be performed on the remaining or deleted search results.\r\n\r\nPlease report any bugs or feature requests.\r\n\r\nAvailable commands :\r\n------------------------------\r\n    :Bs <search_regex>\r\n    :<range> Bsc <search_regex>\r\n\r\nThe 'Bs' command is searching in all the buffers and 'Bsc' only in the current buffer.\r\n\r\n    :Bsf <buffer_name_filter_regex> <search_regex>\r\n    :Bse <buffer_name_exclusion_regex> <search_regex>\r\n\r\nThe 'Bsf' command is searching in all the buffers whose name match <buffer_name_filter_regex> and\r\n'Bse' in all buffers whose name doesn't match <buffer_name_exclusion_regex>.\r\n\r\nDefault key mappings in the buffer with the results :\r\n---------------------------------------------------------------------\r\n  \"Space\"  : moves the cursor on the first result of the next buffer\r\n  \"Enter or Control-j\"   : shows or jumps to the result under the cursor\r\n  \"J\"  : enables or disables jumping on the buffer when pressing Enter or Control-j\r\n  \"A\"  : enables or disables auto-showing the context of the results when pressing j or k\r\n  \"d\" : deletes the current range search result (default: current line)\r\n           (the deleted search results are showed at the bottom of the buffer)\r\n  \"D\" : definitely deletes the current range search result (default: current line)\r\n  \"Q\"  : enables or disables auto-quitting the buffer results when jumping\r\n  \"O\"  : toggles between showing options or showing results\r\n  \"r\"  : replace action on the non-deleted searched results\r\n  \"R\"  : replace action on the deleted searched results\r\n  \"u\"  : replaces this search with a newer one (with the same keyword)\r\n  \"i\"  : enables or disables the search match highlighting on the buffer with the results\r\n  \"I\"  : enables or disables the search match highlighting on the other buffers (not the buffer with the results)\r\n  \"x\"  : enables or disables quite-full-screen\r\n  \"q\"  : deletes the buffer with the results\r\n  \"?\"  : toggles between showing help or showing results\r\n\r\nScreenshot : http:\/\/ioalex.net\/buffers_search_and_replace\/screenshot.png\r\nSmall demo video (ogg theora) : http:\/\/ioalex.net\/buffers_search_and_replace\/demo.ogv\r\n\r\nFor more information, contact me or read the more complete documentation at the start of the plugin file.","install_details":"    Installation :\r\n\r\nDownload the file \"buffers_search.vim\" and put it into the plugins\r\ndirectory; on a unix-like system, the user plugin directory could be\r\n\"~\/.vim\/plugin\".\r\n\r\n    Optional configuration :\r\n\r\nVariables that you can modify :\r\n         *the variables take the possible values 0 or 1 (0 is disabled, 1 is enabled)\r\n   -g:Bs_stay_on_buffer_results_when_entering_result : if to jump on\r\n    the result or not when pressing enter (option \"J\") (default is 1)\r\n   -g:Bs_auto_jump : if to auto-show the result or not when moving\r\n    with j and k (option \"A\") (default is 1)\r\n   -g:Bs_toggle_quit_enter : if you want to quit the buffer with the\r\n    search results when jumping (option \"Q\") (default is 0)\r\n   -g:Bs_results_buffer_match : if you want to have syntax highlight\r\n    on the search string in the buffer with the results (option \"i\")\r\n    (default is 1)\r\n   -g:Bs_buffers_match : if you want to have syntax highlight on the\r\n    search string in other buffers (option \"I\") (default is 1)","5":"    Installation :\r\n\r\nDownload the file \"buffers_search.vim\" and put it into the plugins\r\ndirectory; on a unix-like system, the user plugin directory could be\r\n\"~\/.vim\/plugin\".\r\n\r\n    Optional configuration :\r\n\r\nVariables that you can modify :\r\n         *the variables take the possible values 0 or 1 (0 is disabled, 1 is enabled)\r\n   -g:Bs_stay_on_buffer_results_when_entering_result : if to jump on\r\n    the result or not when pressing enter (option \"J\") (default is 1)\r\n   -g:Bs_auto_jump : if to auto-show the result or not when moving\r\n    with j and k (option \"A\") (default is 1)\r\n   -g:Bs_toggle_quit_enter : if you want to quit the buffer with the\r\n    search results when jumping (option \"Q\") (default is 0)\r\n   -g:Bs_results_buffer_match : if you want to have syntax highlight\r\n    on the search string in the buffer with the results (option \"i\")\r\n    (default is 1)\r\n   -g:Bs_buffers_match : if you want to have syntax highlight on the\r\n    search string in other buffers (option \"I\") (default is 1)","first_name":"Alexandru Ionut","6":"Alexandru Ionut","last_name":"Munteanu","7":"Munteanu","releases":[{"0":"1817","vim_version":"6.0","1":"6.0","script_version":"0.6","2":"0.6","version_comment":"improved buffer looping performance","3":"improved buffer looping performance","package":"buffers_search_and_replace.vim","4":"buffers_search_and_replace.vim","src_id":"18116","5":"18116","creation_date":"1339449657","6":"1339449657"},{"0":"1817","vim_version":"6.0","1":"6.0","script_version":"0.5.2","2":"0.5.2","version_comment":"- added option to set range when searching through current buffer (:<range> Bsc <search_regex>)\r\n- <range> must be \\'<,\\'> for searching in visual selection\r\n- fixed the \\'u\\' event to update with the current search type\r\n- added a top line showing the type of the search\r\n","3":"- added option to set range when searching through current buffer (:<range> Bsc <search_regex>)\r\n- <range> must be \\'<,\\'> for searching in visual selection\r\n- fixed the \\'u\\' event to update with the current search type\r\n- added a top line showing the type of the search\r\n","package":"buffers_search_and_replace.vim","4":"buffers_search_and_replace.vim","src_id":"10356","5":"10356","creation_date":"1239055719","6":"1239055719"},{"0":"1817","vim_version":"6.0","1":"6.0","script_version":"0.5.1","2":"0.5.1","version_comment":"-added command to search and exclude some buffers from the search :\r\n     :Bse <buffer_name_exclusion_regex> <search_regex>\r\n-added searching on custom buffers (buffer name filtering) command :\r\n     :Bsf <buffer_name_filter_regex> <search_regex>\r\n*thank you Vasilii Pascal :)","3":"-added command to search and exclude some buffers from the search :\r\n     :Bse <buffer_name_exclusion_regex> <search_regex>\r\n-added searching on custom buffers (buffer name filtering) command :\r\n     :Bsf <buffer_name_filter_regex> <search_regex>\r\n*thank you Vasilii Pascal :)","package":"buffers_search_and_replace.vim","4":"buffers_search_and_replace.vim","src_id":"10191","5":"10191","creation_date":"1236897357","6":"1236897357"},{"0":"1817","vim_version":"6.0","1":"6.0","script_version":"0.5","2":"0.5","version_comment":"Optimised 'd' action, in order not to refresh the buffer each time.\r\nWarning ! 'r' option for refreshing the screen has been replaced with the 'replace' action !\r\nAction 'D', 'r' and 'R' added :\r\n\"D\"  : definitely deletes the current range search result (default: current line),\r\n\"r\"  : replace action on the non-deleted searched results\r\n\"R\"  : replace action on the deleted searched results\r\nChanged name to buffers_search_and_replace.vim","3":"Optimised 'd' action, in order not to refresh the buffer each time.\r\nWarning ! 'r' option for refreshing the screen has been replaced with the 'replace' action !\r\nAction 'D', 'r' and 'R' added :\r\n\"D\"  : definitely deletes the current range search result (default: current line),\r\n\"r\"  : replace action on the non-deleted searched results\r\n\"R\"  : replace action on the deleted searched results\r\nChanged name to buffers_search_and_replace.vim","package":"buffers_search_and_replace.vim","4":"buffers_search_and_replace.vim","src_id":"10157","5":"10157","creation_date":"1236644402","6":"1236644402"},{"0":"1817","vim_version":"6.0","1":"6.0","script_version":"0.4","2":"0.4","version_comment":"-option 'd' implemented :\r\n            \"d\"  : deletes the current range search result (default: current line)\r\n                   the deleted search results are showed at the bottom of\r\n                   the buffer; deleting a deleted search results will\r\n                   set it again as search result\r\n-added the ':Bsc <search_string>' command for searching only in the current buffer","3":"-option 'd' implemented :\r\n            \"d\"  : deletes the current range search result (default: current line)\r\n                   the deleted search results are showed at the bottom of\r\n                   the buffer; deleting a deleted search results will\r\n                   set it again as search result\r\n-added the ':Bsc <search_string>' command for searching only in the current buffer","package":"buffers_search.vim","4":"buffers_search.vim","src_id":"10136","5":"10136","creation_date":"1236392120","6":"1236392120"},{"0":"1817","vim_version":"7.0","1":"7.0","script_version":"0.3","2":"0.3","version_comment":"-changed some internals to follow Jimmy advices (like using buffer numbers \r\ninstead of buffer names to support unnamed buffers); thanks!\r\n-options J,A,Q,O,r,u,i,I,x,? implemented (see docs)\r\n","3":"-changed some internals to follow Jimmy advices (like using buffer numbers \r\ninstead of buffer names to support unnamed buffers); thanks!\r\n-options J,A,Q,O,r,u,i,I,x,? implemented (see docs)\r\n","package":"buffers_search.vim","4":"buffers_search.vim","src_id":"6856","5":"6856","creation_date":"1173635656","6":"1173635656"},{"0":"1817","vim_version":"7.0","1":"7.0","script_version":"0.2","2":"0.2","version_comment":"Fixed an important bug : the search did not returned all the matches\r\n","3":"Fixed an important bug : the search did not returned all the matches\r\n","package":"buffers_search.vim","4":"buffers_search.vim","src_id":"6849","5":"6849","creation_date":"1173285072","6":"1173285072"},{"0":"1817","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"buffers_search.vim","4":"buffers_search.vim","src_id":"6847","5":"6847","creation_date":"1173269497","6":"1173269497"}]},"1816":{"script_id":"1816","0":"1816","script_name":"Windows PowerShell File Type Plugin","1":"Windows PowerShell File Type Plugin","script_type":"ftplugin","2":"ftplugin","summary":"[Obsolete] Simple ftplugin for use with Windows PowerShell","3":"[Obsolete] Simple ftplugin for use with Windows PowerShell","description":"This file is out of date and is now included in the Windows PowerShell Syntax Plugin package.\r\n\r\nhttp:\/\/www.vim.org\/scripts\/script.php?script_id=1327","4":"This file is out of date and is now included in the Windows PowerShell Syntax Plugin package.\r\n\r\nhttp:\/\/www.vim.org\/scripts\/script.php?script_id=1327","install_details":"","5":"","first_name":"Peter","6":"Peter","last_name":"Provost","7":"Provost","releases":[{"0":"1816","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"ps1.vim","4":"ps1.vim","src_id":"6840","5":"6840","creation_date":"1173132063","6":"1173132063"}]},"1815":{"script_id":"1815","0":"1815","script_name":"Windows PowerShell Indent File","1":"Windows PowerShell Indent File","script_type":"indent","2":"indent","summary":"[Obsolete] Simple indenting rules for Windows PowerShell","3":"[Obsolete] Simple indenting rules for Windows PowerShell","description":"This file is out of date and is now included in the Windows PowerShell Syntax Plugin package.\r\n\r\nhttp:\/\/www.vim.org\/scripts\/script.php?script_id=1327","4":"This file is out of date and is now included in the Windows PowerShell Syntax Plugin package.\r\n\r\nhttp:\/\/www.vim.org\/scripts\/script.php?script_id=1327","install_details":"","5":"","first_name":"Peter","6":"Peter","last_name":"Provost","7":"Provost","releases":[{"0":"1815","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"ps1.vim","4":"ps1.vim","src_id":"6839","5":"6839","creation_date":"1173131863","6":"1173131863"}]},"1814":{"script_id":"1814","0":"1814","script_name":"sqlvim.sh","1":"sqlvim.sh","script_type":"utility","2":"utility","summary":"Run Oracle SQL*Plus commands from vim","3":"Run Oracle SQL*Plus commands from vim","description":"This shell script runs Oracle SQL*Plus commands\/sql statements in a register from within vim and inserts the results at the location marking the end of the register.\r\n\r\nThe simplest way to use the script is to install it per the instructions in install details, type your SQL code in the vim editor. For example,\r\n\r\nMark the line starting with column as ... ma\r\nGo to line starting with select, then ... \\sx\r\n\r\ncolumn tc format a10\r\nset linesize 120\r\nselect 'hello' tc from dual;\r\n\r\nTC\r\n----------\r\nhello\r\n\r\n1 row selected.\r\n\r\nAnything that you can do on the SQL*Plus command line, you can do from within vim using this script. I have tested it on cygwin and hp\/ux.\r\n","4":"This shell script runs Oracle SQL*Plus commands\/sql statements in a register from within vim and inserts the results at the location marking the end of the register.\r\n\r\nThe simplest way to use the script is to install it per the instructions in install details, type your SQL code in the vim editor. For example,\r\n\r\nMark the line starting with column as ... ma\r\nGo to line starting with select, then ... \\sx\r\n\r\ncolumn tc format a10\r\nset linesize 120\r\nselect 'hello' tc from dual;\r\n\r\nTC\r\n----------\r\nhello\r\n\r\n1 row selected.\r\n\r\nAnything that you can do on the SQL*Plus command line, you can do from within vim using this script. I have tested it on cygwin and hp\/ux.\r\n","install_details":"1. Copy script to some directory in your path.\r\n2. chmod 744 to make it executable.\r\n3. Add a shell variable to your .bash_profile \/ .profile called ORA_LOGIN. \r\n    e.g. ORA_LOGIN=scott\/tiger@ora1\r\n4. Add the following macros to your .vimrc:\r\n\" maps for sqlvim.sh execution\r\nmap <Leader>sx  zz:'a,.!sqlvim.sh<CR>\r\nmap <Leader>sc  zz:.!sqlvim.sh<CR>\r\n5. Source your .bash_profile and startup vim","5":"1. Copy script to some directory in your path.\r\n2. chmod 744 to make it executable.\r\n3. Add a shell variable to your .bash_profile \/ .profile called ORA_LOGIN. \r\n    e.g. ORA_LOGIN=scott\/tiger@ora1\r\n4. Add the following macros to your .vimrc:\r\n\" maps for sqlvim.sh execution\r\nmap <Leader>sx  zz:'a,.!sqlvim.sh<CR>\r\nmap <Leader>sc  zz:.!sqlvim.sh<CR>\r\n5. Source your .bash_profile and startup vim","first_name":"dushyant","6":"dushyant","last_name":"jhamb","7":"jhamb","releases":[{"0":"1814","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"sqlvim.sh","4":"sqlvim.sh","src_id":"6837","5":"6837","creation_date":"1173120929","6":"1173120929"}]},"1813":{"script_id":"1813","0":"1813","script_name":"greplace.vim","1":"greplace.vim","script_type":"utility","2":"utility","summary":"Replace a pattern across multiple files interactively","3":"Replace a pattern across multiple files interactively","description":"Overview\r\n\r\nThe Global Replace plugin allows you to search and replace a pattern across\r\nmultiple files and buffers.\r\n\r\nTo search and replace a pattern in multiple files, you invoke a command\r\nsupplied by this plugin with the search pattern. The plugin displays the lines\r\ncontaining the specified pattern in one or more specified files in a Vim\r\nbuffer. You can use the Vim editing commands to make modifications to this\r\nbuffer. To incorporate the changes back to the corresponding files, you now\r\ninvoke a plugin command. This plugin allows you to make multiple modifications\r\nacross several files in a single pass.\r\n\r\nThis plugin will run only on Vim 7.0 and above.\r\n\r\nRefer to the greplace.txt help file for more information (available with the plugin).\r\n\r\nThe github repository for this plugin is at https:\/\/github.com\/yegappan\/greplace\r\n","4":"Overview\r\n\r\nThe Global Replace plugin allows you to search and replace a pattern across\r\nmultiple files and buffers.\r\n\r\nTo search and replace a pattern in multiple files, you invoke a command\r\nsupplied by this plugin with the search pattern. The plugin displays the lines\r\ncontaining the specified pattern in one or more specified files in a Vim\r\nbuffer. You can use the Vim editing commands to make modifications to this\r\nbuffer. To incorporate the changes back to the corresponding files, you now\r\ninvoke a plugin command. This plugin allows you to make multiple modifications\r\nacross several files in a single pass.\r\n\r\nThis plugin will run only on Vim 7.0 and above.\r\n\r\nRefer to the greplace.txt help file for more information (available with the plugin).\r\n\r\nThe github repository for this plugin is at https:\/\/github.com\/yegappan\/greplace\r\n","install_details":"You can use any one of the Vim plugin managers (dein.vim, pathogen, vam,\r\nvim-plug, volt, Vundle, etc.) to install and manage this plugin.\r\n\r\nAlternatively, you can also manually download and install the plugin\r\nusing the following steps.\r\n\r\n1. Download the greplace.zip file from github or from the vim.sourceforge.io\r\n   site.\r\n2. Unzip the files into the $HOME\/.vim or the $HOME\/vimfiles or the\r\n   $VIM\/vimfiles directory.  After this step, you should have the following\r\n   files (the directory structure should be preserved):\r\n\r\n\tplugin\/greplace.vim - global replace command definitions\r\n\tautoload\/greplace.vim - autoloaded global replace plugin file\r\n\tdoc\/greplace.txt    - documentation (help) file\r\n\r\n3. Change to the $HOME\/.vim\/doc or $HOME\/vimfiles\/doc or $VIM\/vimfiles\/doc\r\n   directory, start Vim and run the \":helptags .\" command to process the\r\n   help file. Without this step, you cannot jump to the help topics.\r\n4. Restart Vim.\r\n\r\nTo uninstall the global replace plugin, remove the plugin\/greplace.vim,\r\nautoload\/greplace.vim and doc\/greplace.txt files from the $HOME\/.vim or\r\n$HOME\/vimfiles directory.\r\n","5":"You can use any one of the Vim plugin managers (dein.vim, pathogen, vam,\r\nvim-plug, volt, Vundle, etc.) to install and manage this plugin.\r\n\r\nAlternatively, you can also manually download and install the plugin\r\nusing the following steps.\r\n\r\n1. Download the greplace.zip file from github or from the vim.sourceforge.io\r\n   site.\r\n2. Unzip the files into the $HOME\/.vim or the $HOME\/vimfiles or the\r\n   $VIM\/vimfiles directory.  After this step, you should have the following\r\n   files (the directory structure should be preserved):\r\n\r\n\tplugin\/greplace.vim - global replace command definitions\r\n\tautoload\/greplace.vim - autoloaded global replace plugin file\r\n\tdoc\/greplace.txt    - documentation (help) file\r\n\r\n3. Change to the $HOME\/.vim\/doc or $HOME\/vimfiles\/doc or $VIM\/vimfiles\/doc\r\n   directory, start Vim and run the \":helptags .\" command to process the\r\n   help file. Without this step, you cannot jump to the help topics.\r\n4. Restart Vim.\r\n\r\nTo uninstall the global replace plugin, remove the plugin\/greplace.vim,\r\nautoload\/greplace.vim and doc\/greplace.txt files from the $HOME\/.vim or\r\n$HOME\/vimfiles directory.\r\n","first_name":"Yegappan","6":"Yegappan","last_name":"Lakshmanan","7":"Lakshmanan","releases":[{"0":"1813","vim_version":"7.0","1":"7.0","script_version":"2.0","2":"2.0","version_comment":"1. Fix various reported bugs with escaping the search pattern, highlighting the changes, etc.\r\n2. Refactor the code.\r\n3. Update the help text.","3":"1. Fix various reported bugs with escaping the search pattern, highlighting the changes, etc.\r\n2. Refactor the code.\r\n3. Update the help text.","package":"greplace.zip","4":"greplace.zip","src_id":"25856","5":"25856","creation_date":"1520187335","6":"1520187335"},{"0":"1813","vim_version":"7.0","1":"7.0","script_version":"1.0b1","2":"1.0b1","version_comment":"Initial revision.","3":"Initial revision.","package":"greplace.zip","4":"greplace.zip","src_id":"6828","5":"6828","creation_date":"1172929597","6":"1172929597"}]},"1812":{"script_id":"1812","0":"1812","script_name":"gotofile","1":"gotofile","script_type":"utility","2":"utility","summary":"gf replacement by using the tags file","3":"gf replacement by using the tags file","description":"This script defines a new command 'GotoFile', which resembles the normal\r\n'gf' function, but uses a standard tags file generated by ctags for\r\nlooking up the file name under the cursor. \r\n\r\nYou need to generate a standard tags file (with ctags) for this script to work.\r\nAdd the following ctags option for generating filename tags: --extra=+f\r\n\r\nFor example: ctags -R --extra=+f\r\n\r\nAdd the following mapping to your .vimrc (or _vimrc) to replace the\r\nnormal 'gf' behavior by the GotoFile command:\r\n\r\nnmap <silent> gf :GotoFile<CR>\r\n\r\nI wrote this script mainly for having an alternative for setting the\r\npath and using 'gf'. While using completion all header files within\r\nthe path are also searched, which causes a major performance hit for\r\nlarge projects (at least for me). So this script allows using the\r\n'gf' feature without setting the path. Other suggestions are welcome!\r\n","4":"This script defines a new command 'GotoFile', which resembles the normal\r\n'gf' function, but uses a standard tags file generated by ctags for\r\nlooking up the file name under the cursor. \r\n\r\nYou need to generate a standard tags file (with ctags) for this script to work.\r\nAdd the following ctags option for generating filename tags: --extra=+f\r\n\r\nFor example: ctags -R --extra=+f\r\n\r\nAdd the following mapping to your .vimrc (or _vimrc) to replace the\r\nnormal 'gf' behavior by the GotoFile command:\r\n\r\nnmap <silent> gf :GotoFile<CR>\r\n\r\nI wrote this script mainly for having an alternative for setting the\r\npath and using 'gf'. While using completion all header files within\r\nthe path are also searched, which causes a major performance hit for\r\nlarge projects (at least for me). So this script allows using the\r\n'gf' feature without setting the path. Other suggestions are welcome!\r\n","install_details":"Just place this script in your plugin directory.\r\nGenerate the tags file with ctags.\r\nMake sure that your tags file can be found by vim. See :help 'tags'\r\nInstall the latest version of genutils (vimscript #197).\r\n\r\n","5":"Just place this script in your plugin directory.\r\nGenerate the tags file with ctags.\r\nMake sure that your tags file can be found by vim. See :help 'tags'\r\nInstall the latest version of genutils (vimscript #197).\r\n\r\n","first_name":"Nathan","6":"Nathan","last_name":"Huizinga","7":"Huizinga","releases":[{"0":"1812","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"GotoFile.vim","4":"GotoFile.vim","src_id":"6824","5":"6824","creation_date":"1172845011","6":"1172845011"}]},"1811":{"script_id":"1811","0":"1811","script_name":"Random Tip Displayer","1":"Random Tip Displayer","script_type":"utility","2":"utility","summary":"display random of \"Best Vim tips\"","3":"display random of \"Best Vim tips\"","description":"This Vim script allows: viewing, downloading, and displaying random position of \"Best Vim Tips\" from the page:\r\nhttp:\/\/rayninfo.co.uk\/vimtips.html (see: vimtip #305)\r\n\r\n\r\nUsage:\r\n\r\n<Leader>gt (or :call GetVimTips()) - download and parse \"Best Vim Tips\". File is saved in ~\/.vim\/vimtips.txt (~\/vimfiles\/vimtips.txt under windows)\r\n\r\n<Leader>dt (or :call DisplayVimTips()) - display \"Best Vim Tips\" in separate buffer (download it, if the file is not present)\r\n   \r\n<Leader>rt (or :call DisplayRandomTip()) - display random position in vimtips.txt (download if necessary)\r\n","4":"This Vim script allows: viewing, downloading, and displaying random position of \"Best Vim Tips\" from the page:\r\nhttp:\/\/rayninfo.co.uk\/vimtips.html (see: vimtip #305)\r\n\r\n\r\nUsage:\r\n\r\n<Leader>gt (or :call GetVimTips()) - download and parse \"Best Vim Tips\". File is saved in ~\/.vim\/vimtips.txt (~\/vimfiles\/vimtips.txt under windows)\r\n\r\n<Leader>dt (or :call DisplayVimTips()) - display \"Best Vim Tips\" in separate buffer (download it, if the file is not present)\r\n   \r\n<Leader>rt (or :call DisplayRandomTip()) - display random position in vimtips.txt (download if necessary)\r\n","install_details":"After unpacking archive, copy files vimtips.vim and random.vim into ~\/.vim\/plugins (~\/vimfiles\/plugins)","5":"After unpacking archive, copy files vimtips.vim and random.vim into ~\/.vim\/plugins (~\/vimfiles\/plugins)","first_name":"Mikolaj","6":"Mikolaj","last_name":"Sitarz","7":"Sitarz","releases":[{"0":"1811","vim_version":"6.0","1":"6.0","script_version":"0.2","2":"0.2","version_comment":"- improved parsing\r\n- added possibility of using python to download file instead of netrw","3":"- improved parsing\r\n- added possibility of using python to download file instead of netrw","package":"rndtips-0.2.tar.gz","4":"rndtips-0.2.tar.gz","src_id":"6888","5":"6888","creation_date":"1174126195","6":"1174126195"},{"0":"1811","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"rndtips-0.1.tar.gz","4":"rndtips-0.1.tar.gz","src_id":"6823","5":"6823","creation_date":"1172840264","6":"1172840264"}]},"1810":{"script_id":"1810","0":"1810","script_name":"Infobasic Set (Syntax, FTDetect, FTPlugi","1":"Infobasic Set (Syntax, FTDetect, FTPlugi","script_type":"syntax","2":"syntax","summary":"It allows work with infobasic scripts, for jbase programming and Globus\/T24 App.","3":"It allows work with infobasic scripts, for jbase programming and Globus\/T24 App.","description":"It allows work with infobasic scripts, for jbase programming and Globus\/T24 App.\r\n\r\n* Syntax Highlighting\r\n* FileType Recognition (Because this files doesn't have extension, i convent that all files have the letters SFC from my company)\r\n* Compiler\r\n* Indent","4":"It allows work with infobasic scripts, for jbase programming and Globus\/T24 App.\r\n\r\n* Syntax Highlighting\r\n* FileType Recognition (Because this files doesn't have extension, i convent that all files have the letters SFC from my company)\r\n* Compiler\r\n* Indent","install_details":"* Syntax Highlighting\r\n* FileType Recognition (Because this files doesn't have extension, i convent that all files have the letters SFC from my company)\r\n* Compiler\r\n* Indent","5":"* Syntax Highlighting\r\n* FileType Recognition (Because this files doesn't have extension, i convent that all files have the letters SFC from my company)\r\n* Compiler\r\n* Indent","first_name":"Marcelo","6":"Marcelo","last_name":"Andrade","7":"Andrade","releases":[{"0":"1810","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"vim-infobasic-V1.0.zip","4":"vim-infobasic-V1.0.zip","src_id":"6822","5":"6822","creation_date":"1172835161","6":"1172835161"}]},"1809":{"script_id":"1809","0":"1809","script_name":"guicolorscheme.vim","1":"guicolorscheme.vim","script_type":"utility","2":"utility","summary":"auto convert gui-only colorschemes to 88\/256 color terminal schemes","3":"auto convert gui-only colorschemes to 88\/256 color terminal schemes","description":"I'll admit, I don't use gvim, except on Windows machines.  When I'm at a terminal, I'm in front of a 88 or 256 color terminal 90% of the time.  Because of this, I have lots of fancy color options, but my vim setup doesn't take advantage of them well because most interesting color schemes are made for gvim and not console vim.  Sure, inkpot, desert256, and a handful of others work nicely, but the choices are so limited.\r\n\r\nEnter GuiColorScheme.  This script converts, as best it can muster, the gui-specific parts of a colorscheme into color numbers for 88 and 256 color terminals (it should also still support gvim as well).\r\n\r\nUsage:\r\n   :GuiColorScheme <color scheme name>\r\n\r\nTab completion works exactly like the completion for the :colorscheme command, so you can use it to browse through your colorschemes.\r\n\r\nFor good measure, a screenshot, showing gvim and putty (in 256 color mode):\r\nhttp:\/\/img.phraktured.net\/other\/guicolorscheme.png","4":"I'll admit, I don't use gvim, except on Windows machines.  When I'm at a terminal, I'm in front of a 88 or 256 color terminal 90% of the time.  Because of this, I have lots of fancy color options, but my vim setup doesn't take advantage of them well because most interesting color schemes are made for gvim and not console vim.  Sure, inkpot, desert256, and a handful of others work nicely, but the choices are so limited.\r\n\r\nEnter GuiColorScheme.  This script converts, as best it can muster, the gui-specific parts of a colorscheme into color numbers for 88 and 256 color terminals (it should also still support gvim as well).\r\n\r\nUsage:\r\n   :GuiColorScheme <color scheme name>\r\n\r\nTab completion works exactly like the completion for the :colorscheme command, so you can use it to browse through your colorschemes.\r\n\r\nFor good measure, a screenshot, showing gvim and putty (in 256 color mode):\r\nhttp:\/\/img.phraktured.net\/other\/guicolorscheme.png","install_details":"Drop this file in ~\/.vim\/plugin\/\r\n\r\n:GuiColorScheme <scheme>\r\nTab completion works (or should) exactly as :colorscheme does","5":"Drop this file in ~\/.vim\/plugin\/\r\n\r\n:GuiColorScheme <scheme>\r\nTab completion works (or should) exactly as :colorscheme does","first_name":"aaron","6":"aaron","last_name":"griffin","7":"griffin","releases":[{"0":"1809","vim_version":"7.0","1":"7.0","script_version":"1.2","2":"1.2","version_comment":"Fixes from Dominique Pelle: support indented hilight stanzas, and clear current hilights before resetting","3":"Fixes from Dominique Pelle: support indented hilight stanzas, and clear current hilights before resetting","package":"guicolorscheme.vim","4":"guicolorscheme.vim","src_id":"10162","5":"10162","creation_date":"1236700169","6":"1236700169"},{"0":"1809","vim_version":"7.0","1":"7.0","script_version":"1.1","2":"1.1","version_comment":"Update to handle gvim appropriately, by simply setting the colorsheme if we're in gui mode","3":"Update to handle gvim appropriately, by simply setting the colorsheme if we're in gui mode","package":"guicolorscheme.vim","4":"guicolorscheme.vim","src_id":"7973","5":"7973","creation_date":"1195575150","6":"1195575150"},{"0":"1809","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"guicolorscheme.vim","4":"guicolorscheme.vim","src_id":"6810","5":"6810","creation_date":"1172577469","6":"1172577469"}]},"1808":{"script_id":"1808","0":"1808","script_name":"Vimplate Enhanced","1":"Vimplate Enhanced","script_type":"utility","2":"utility","summary":"Vimplate template system for vim 7.0 (supports C\/C++\/Cpp, Perl, make, LaTeX)","3":"Vimplate template system for vim 7.0 (supports C\/C++\/Cpp, Perl, make, LaTeX)","description":"*** Introduction and Explanation ***\r\n\r\nI have made substantial updates to the package layout and installation procedure of Stotz's most recent version of vimplate (v0.2.3).  I implemented several fixes so that it would actually be compatible with windows.  I have reworked the installation procedure and it should now be much easier to follow.\r\n\r\nThis version of Vimplate should be MUCH easier to install! (on all operating systems, but especially windows).\r\n\r\nIt is a really neat plugin and I am very pleased to have it working on my laptop.  I hope this will be helpful for at least a few of you out there.\r\n\r\n\r\n--------------------------------------------------------------------------------\r\nChangelog\r\n--------------------------------------------------------------------------------\r\n0.2.4, released by JET on 2007-02-25\r\n  Fixed a number of typos and added additional details in the installation instructions to improve the clarity.\r\n\r\n  Added prompts during the -createconfig phase of the setup so that the user will not need to do as much editing of the .vimplaterc file by hand.\r\n\r\n  Added a createconf batch file to simplify things for windows.\r\n\r\n  Changed how error conditions are handled and displayed in the perl script so that an appropriate amount of information about the problem will be shown.\r\n--------------------------------------------------------------------------------\r\n\r\n\r\n\r\n1. Description\r\n2. Usage\r\n3. Subroutines\r\n4. Example\r\n5. Documentation\r\n6. Depends\r\n7. Installation\r\n\r\n\r\n1. Description                                        *vimplate-description*\r\n\r\nVimplate provides an extensible and powerful template processing system.\r\nIt is based on Perl and Template-Toolkit.\r\nYou can create templates for program code, makefiles, letters, html pages,\r\nlatex etc. As example vimplate contains templates for C++, LaTeX, Perl\r\nand Makefile.\r\nWith vimplate you can write templates which interact with the user.\r\nFor themes are the functions choice() and input().\r\nYou can choose different locale for the function date() and locale().\r\nYou can write your own perl code directly in the templates.\r\n\r\nIf you find this useful and want to let the original author of this package know, email him at <stotz@gmx.ch>.\r\n\r\nIf you write a new template and  would like me to add it to the vimplate package please send an email with the text [VIMPLATE] in the subject line to: < outtatime@gmail.com >.\r\n\r\n\r\n2. Usage                                                    *vimplate-usage*\r\n\r\nUsage:\r\n  :Vimplate <template> [options]\r\n    choice <template> whit <TAB> (command line completion is supported).\r\n    With <TAB> all templates are listed.\r\n    [options]\r\n      -user|u=<username>\r\n        Use the information form user <username> while parsing templates.\r\n      -dir|d=<templatedir>\r\n        Search templatefiles in <templatedir>.\r\n\r\n\r\n3. Subroutines                                         *vimplate-subroutines*\r\n\r\n  locale()                  for locale please see: man locale\r\n  [% loc=locale() %]        get the current locale\r\n                              and write it to the variable loc\r\n  [% locale('C') %]         set global the current locale to C\r\n  [% locale('de_DE') %]     set global the current locale to de_DE\r\n  date()                    for date please see: man date\r\n  [% date('%c') %]          print the current date\r\n                              with the current locale setting\r\n  [% date('de_DE', '%c') %] print the current date with the locale de_DE\r\n  input()\r\n  [% var=input() %]         read input from user\r\n                              and write it to the variable var\r\n  choice()\r\n  [% day=choice('day:', 'Su', 'Mo', 'Tu', 'We', 'Th', 'Fr', 'Sa') %]\r\n                            let the user choice between different values\r\n                            and write it to the variable day\r\n\r\n  please try :Vimplate Test\r\n\r\n\r\n4. Example                                                *vimplate-example*\r\n\r\na LaTeX Template:\r\n  http:\/\/www.napali.ch\/vimplate\/example\/LaTeX.tt.html\r\nthe generated LaTeX File:\r\n  http:\/\/www.napali.ch\/vimplate\/example\/Example.tex.html\r\na Makefile Template for LaTeX:\r\n  http:\/\/www.napali.ch\/vimplate\/example\/Makefile-LaTeX.tt.html\r\nthe generated Makefile:\r\n  http:\/\/www.napali.ch\/vimplate\/example\/Makefile.html\r\nc++ Templates:\r\n  http:\/\/www.napali.ch\/vimplate\/example\/hpp-default.tt.html\r\n  http:\/\/www.napali.ch\/vimplate\/example\/cpp-default.tt.html\r\nthe generated class:\r\n  http:\/\/www.napali.ch\/vimplate\/example\/Example.hpp.html\r\n  http:\/\/www.napali.ch\/vimplate\/example\/Example.cpp.html\r\nthe generated class with doxygen:\r\n  http:\/\/www.napali.ch\/vimplate\/example\/ExampleDoxy.hpp.html\r\n  http:\/\/www.napali.ch\/vimplate\/example\/ExampleDoxy.cpp.html\r\na perl Template:\r\n  http:\/\/www.napali.ch\/vimplate\/example\/perl.tt.html\r\nthe genereated program:\r\n  http:\/\/www.napali.ch\/vimplate\/example\/Example.pl.html\r\nthe genereated program with Log4Perl:\r\n  http:\/\/www.napali.ch\/vimplate\/example\/ExampleLog.pl.html\r\n\r\nExample:\r\n  the template letter.tt:\r\n    ________________________________________________________\r\n    [%\r\n       sex=choice('sex: ', 'female', 'male')\r\n       name=input('name: ')\r\n       location=input('your location: ')\r\n    -%]\r\n                       [% ucfirst(location) %], [% date('C', '%b %d, %Y') %]\r\n\r\n    Dear [% IF sex=='female'; 'Ms'; ELSE; 'Mr'; END %] [% ucfirst(name) %]\r\n\r\n    ...\r\n\r\n    Sincerely\r\n\r\n    [% user.firstname %] [% user.lastname %]\r\n    ________________________________________________________\r\n\r\n  run vim:\r\n    :Vimplate letter\r\n    sex:\r\n      0) female\r\n      1) male\r\n    0\r\n    name: Meier\r\n    your location: Olten\r\n\r\n  your input was:\r\n    :Vimplate letter<CR>0<CR>Meier<CR>Olten<CR>\r\n\r\n  this will produce this letter:\r\n    ________________________________________________________\r\n                                      Olten, Jul 11, 2005\r\n\r\n    Dear Ms Meier\r\n\r\n    ...\r\n\r\n    Sincerely\r\n\r\n    Urs Stotz\r\n    ________________________________________________________\r\n\r\nExample:\r\n  the template hpp-default.tt:\r\n    ________________________________________________________\r\n    [% classname=input('Class name: ')\r\n       doxygen=choice('with Doxygen comments: ', 'no', 'yes')\r\n    -%]\r\n    #ifndef [% uc(classname) %]_HPP\r\n    #define [% uc(classname) %]_HPP\r\n\r\n    [% IF doxygen=='yes' -%]\r\n    \/**\r\n     * @brief [% classname %] ... short description ...\r\n     * @author [% user.firstname %] [% user.lastname %] <[% user.mail %]>\r\n     * @date [% date('%Y-%m-%d') %]\r\n     * ... description ...\r\n     *\/\r\n\r\n    [% END -%]\r\n    class [% classname %]\r\n    {\r\n      public:\r\n    [% IF doxygen=='yes' -%]\r\n\r\n        \/**\r\n         * Default constructor\r\n         *\/\r\n    [% END -%]\r\n        [% classname %]();\r\n    [% IF doxygen=='yes' -%]\r\n\r\n        \/**\r\n         * Copy constructor\r\n         * @param other reference on object to copy\r\n         *\/\r\n    [% END -%]\r\n        [% classname %](const [% classname %]& other);\r\n    [% IF doxygen=='yes' -%]\r\n\r\n        \/**\r\n         * Assignment operator\r\n         * @param other reference on object to copy\r\n         * @return reference on initialisated object\r\n         *\/\r\n    [% END -%]\r\n        [% classname %]& operator=(const [% classname %]& other);\r\n    [% IF doxygen=='yes' -%]\r\n\r\n        \/**\r\n         * Destructor\r\n         *\/\r\n    [% END -%]\r\n        virtual ~[% classname %]();\r\n\r\n      private:\r\n    [% IF doxygen=='yes' -%]\r\n\r\n        \/**\r\n         * Base initialisation should be called\r\n         * at beginning of each constructor\r\n         *\/\r\n    [% END -%]\r\n        void init();\r\n    [% IF doxygen=='yes' -%]\r\n\r\n    \/**\r\n     * Method to copy each member (deep copy)\r\n     * @param other reference on object to copy\r\n     *\/\r\n    [% END -%]\r\n        void init(const [% classname %]& other);\r\n    };\r\n\r\n    #endif \/* #ifndef [% uc(classname) %]_HPP *\/\r\n    ________________________________________________________\r\n\r\n  run vim:\r\n    :Vimplate hpp-default\r\n    Class name: Parent\r\n    with Doxygen comments:\r\n      0) no\r\n      1) yes\r\n    1\r\n\r\n  your input was:\r\n    :Vimplate hpp-default<CR>Parent<CR>1<CR>\r\n\r\n  this will produce this c++ include file:\r\n    ________________________________________________________\r\n    #ifndef PARENT_HPP\r\n    #define PARENT_HPP\r\n\r\n    \/**\r\n     * @brief Parent ... short description ...\r\n     * @author Urs Stotz <stotz@gmx.ch>\r\n     * @date 2005-07-18\r\n     * ... description ...\r\n     *\/\r\n\r\n    class Parent\r\n    {\r\n      public:\r\n\r\n        \/**\r\n         * Default constructor\r\n         *\/\r\n        Parent();\r\n\r\n        \/**\r\n         * Copy constructor\r\n         * @param other reference on object to copy\r\n         *\/\r\n        Parent(const Parent& other);\r\n\r\n        \/**\r\n         * Assignment operator\r\n         * @param other reference on object to copy\r\n         * @return reference on initialisated object\r\n         *\/\r\n        Parent& operator=(const Parent& other);\r\n\r\n        \/**\r\n         * Destructor\r\n         *\/\r\n        virtual ~Parent();\r\n\r\n      private:\r\n\r\n        \/**\r\n         * Base initialisation should be called\r\n         * at beginning of each constructor\r\n         *\/\r\n        void init();\r\n\r\n        \/**\r\n         * Method to copy each member (deep copy)\r\n         * @param other reference on object to copy\r\n         *\/\r\n        void init(const Parent& other);\r\n    };\r\n\r\n    #endif \/* #ifndef PARENT_HPP *\/\r\n    ________________________________________________________\r\n\r\n\r\n5. Documentation                                    *vimplate-documentation*\r\n\r\nDocumentation:\r\n  - http:\/\/napali.ch\/vimplate\r\n  - http:\/\/www.template-toolkit.org\/docs.html\r\n  - http:\/\/perldoc.perl.org\/perl.html\r\n\r\nTodo:\r\n  - better exception handling\r\n  - write more templates\r\n\r\nLicense:\r\n  This program is free software; you can redistribute it and\/or modify it\r\n  under the terms of the GNU General Public License, version 2, as published\r\n  by the Free Software Foundation.\r\n\r\n  This program is distributed in the hope that it will be useful, but\r\n  WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY\r\n  or FITNESS FOR A PARTICULAR PURPOSE.  See the GNU General Public License\r\n  for more details.\r\n\r\n  A copy of the GNU GPL is available as \/usr\/share\/common-licenses\/GPL-2\r\n  on Debian systems, or on the World Wide Web at\r\n  http:\/\/www.gnu.org\/copyleft\/gpl.html\r\n  You can also obtain it by writing to the Free Software Foundation, Inc.,\r\n  59 Temple Place - Suite 330, Boston, MA 02111-1307, USA\r\n\r\nCopyright:\r\n  Copyright (c) 2005, Urs Stotz <stotz@gmx.ch>\r\n\r\nVersion:\r\n  vimplate 0.2.4","4":"*** Introduction and Explanation ***\r\n\r\nI have made substantial updates to the package layout and installation procedure of Stotz's most recent version of vimplate (v0.2.3).  I implemented several fixes so that it would actually be compatible with windows.  I have reworked the installation procedure and it should now be much easier to follow.\r\n\r\nThis version of Vimplate should be MUCH easier to install! (on all operating systems, but especially windows).\r\n\r\nIt is a really neat plugin and I am very pleased to have it working on my laptop.  I hope this will be helpful for at least a few of you out there.\r\n\r\n\r\n--------------------------------------------------------------------------------\r\nChangelog\r\n--------------------------------------------------------------------------------\r\n0.2.4, released by JET on 2007-02-25\r\n  Fixed a number of typos and added additional details in the installation instructions to improve the clarity.\r\n\r\n  Added prompts during the -createconfig phase of the setup so that the user will not need to do as much editing of the .vimplaterc file by hand.\r\n\r\n  Added a createconf batch file to simplify things for windows.\r\n\r\n  Changed how error conditions are handled and displayed in the perl script so that an appropriate amount of information about the problem will be shown.\r\n--------------------------------------------------------------------------------\r\n\r\n\r\n\r\n1. Description\r\n2. Usage\r\n3. Subroutines\r\n4. Example\r\n5. Documentation\r\n6. Depends\r\n7. Installation\r\n\r\n\r\n1. Description                                        *vimplate-description*\r\n\r\nVimplate provides an extensible and powerful template processing system.\r\nIt is based on Perl and Template-Toolkit.\r\nYou can create templates for program code, makefiles, letters, html pages,\r\nlatex etc. As example vimplate contains templates for C++, LaTeX, Perl\r\nand Makefile.\r\nWith vimplate you can write templates which interact with the user.\r\nFor themes are the functions choice() and input().\r\nYou can choose different locale for the function date() and locale().\r\nYou can write your own perl code directly in the templates.\r\n\r\nIf you find this useful and want to let the original author of this package know, email him at <stotz@gmx.ch>.\r\n\r\nIf you write a new template and  would like me to add it to the vimplate package please send an email with the text [VIMPLATE] in the subject line to: < outtatime@gmail.com >.\r\n\r\n\r\n2. Usage                                                    *vimplate-usage*\r\n\r\nUsage:\r\n  :Vimplate <template> [options]\r\n    choice <template> whit <TAB> (command line completion is supported).\r\n    With <TAB> all templates are listed.\r\n    [options]\r\n      -user|u=<username>\r\n        Use the information form user <username> while parsing templates.\r\n      -dir|d=<templatedir>\r\n        Search templatefiles in <templatedir>.\r\n\r\n\r\n3. Subroutines                                         *vimplate-subroutines*\r\n\r\n  locale()                  for locale please see: man locale\r\n  [% loc=locale() %]        get the current locale\r\n                              and write it to the variable loc\r\n  [% locale('C') %]         set global the current locale to C\r\n  [% locale('de_DE') %]     set global the current locale to de_DE\r\n  date()                    for date please see: man date\r\n  [% date('%c') %]          print the current date\r\n                              with the current locale setting\r\n  [% date('de_DE', '%c') %] print the current date with the locale de_DE\r\n  input()\r\n  [% var=input() %]         read input from user\r\n                              and write it to the variable var\r\n  choice()\r\n  [% day=choice('day:', 'Su', 'Mo', 'Tu', 'We', 'Th', 'Fr', 'Sa') %]\r\n                            let the user choice between different values\r\n                            and write it to the variable day\r\n\r\n  please try :Vimplate Test\r\n\r\n\r\n4. Example                                                *vimplate-example*\r\n\r\na LaTeX Template:\r\n  http:\/\/www.napali.ch\/vimplate\/example\/LaTeX.tt.html\r\nthe generated LaTeX File:\r\n  http:\/\/www.napali.ch\/vimplate\/example\/Example.tex.html\r\na Makefile Template for LaTeX:\r\n  http:\/\/www.napali.ch\/vimplate\/example\/Makefile-LaTeX.tt.html\r\nthe generated Makefile:\r\n  http:\/\/www.napali.ch\/vimplate\/example\/Makefile.html\r\nc++ Templates:\r\n  http:\/\/www.napali.ch\/vimplate\/example\/hpp-default.tt.html\r\n  http:\/\/www.napali.ch\/vimplate\/example\/cpp-default.tt.html\r\nthe generated class:\r\n  http:\/\/www.napali.ch\/vimplate\/example\/Example.hpp.html\r\n  http:\/\/www.napali.ch\/vimplate\/example\/Example.cpp.html\r\nthe generated class with doxygen:\r\n  http:\/\/www.napali.ch\/vimplate\/example\/ExampleDoxy.hpp.html\r\n  http:\/\/www.napali.ch\/vimplate\/example\/ExampleDoxy.cpp.html\r\na perl Template:\r\n  http:\/\/www.napali.ch\/vimplate\/example\/perl.tt.html\r\nthe genereated program:\r\n  http:\/\/www.napali.ch\/vimplate\/example\/Example.pl.html\r\nthe genereated program with Log4Perl:\r\n  http:\/\/www.napali.ch\/vimplate\/example\/ExampleLog.pl.html\r\n\r\nExample:\r\n  the template letter.tt:\r\n    ________________________________________________________\r\n    [%\r\n       sex=choice('sex: ', 'female', 'male')\r\n       name=input('name: ')\r\n       location=input('your location: ')\r\n    -%]\r\n                       [% ucfirst(location) %], [% date('C', '%b %d, %Y') %]\r\n\r\n    Dear [% IF sex=='female'; 'Ms'; ELSE; 'Mr'; END %] [% ucfirst(name) %]\r\n\r\n    ...\r\n\r\n    Sincerely\r\n\r\n    [% user.firstname %] [% user.lastname %]\r\n    ________________________________________________________\r\n\r\n  run vim:\r\n    :Vimplate letter\r\n    sex:\r\n      0) female\r\n      1) male\r\n    0\r\n    name: Meier\r\n    your location: Olten\r\n\r\n  your input was:\r\n    :Vimplate letter<CR>0<CR>Meier<CR>Olten<CR>\r\n\r\n  this will produce this letter:\r\n    ________________________________________________________\r\n                                      Olten, Jul 11, 2005\r\n\r\n    Dear Ms Meier\r\n\r\n    ...\r\n\r\n    Sincerely\r\n\r\n    Urs Stotz\r\n    ________________________________________________________\r\n\r\nExample:\r\n  the template hpp-default.tt:\r\n    ________________________________________________________\r\n    [% classname=input('Class name: ')\r\n       doxygen=choice('with Doxygen comments: ', 'no', 'yes')\r\n    -%]\r\n    #ifndef [% uc(classname) %]_HPP\r\n    #define [% uc(classname) %]_HPP\r\n\r\n    [% IF doxygen=='yes' -%]\r\n    \/**\r\n     * @brief [% classname %] ... short description ...\r\n     * @author [% user.firstname %] [% user.lastname %] <[% user.mail %]>\r\n     * @date [% date('%Y-%m-%d') %]\r\n     * ... description ...\r\n     *\/\r\n\r\n    [% END -%]\r\n    class [% classname %]\r\n    {\r\n      public:\r\n    [% IF doxygen=='yes' -%]\r\n\r\n        \/**\r\n         * Default constructor\r\n         *\/\r\n    [% END -%]\r\n        [% classname %]();\r\n    [% IF doxygen=='yes' -%]\r\n\r\n        \/**\r\n         * Copy constructor\r\n         * @param other reference on object to copy\r\n         *\/\r\n    [% END -%]\r\n        [% classname %](const [% classname %]& other);\r\n    [% IF doxygen=='yes' -%]\r\n\r\n        \/**\r\n         * Assignment operator\r\n         * @param other reference on object to copy\r\n         * @return reference on initialisated object\r\n         *\/\r\n    [% END -%]\r\n        [% classname %]& operator=(const [% classname %]& other);\r\n    [% IF doxygen=='yes' -%]\r\n\r\n        \/**\r\n         * Destructor\r\n         *\/\r\n    [% END -%]\r\n        virtual ~[% classname %]();\r\n\r\n      private:\r\n    [% IF doxygen=='yes' -%]\r\n\r\n        \/**\r\n         * Base initialisation should be called\r\n         * at beginning of each constructor\r\n         *\/\r\n    [% END -%]\r\n        void init();\r\n    [% IF doxygen=='yes' -%]\r\n\r\n    \/**\r\n     * Method to copy each member (deep copy)\r\n     * @param other reference on object to copy\r\n     *\/\r\n    [% END -%]\r\n        void init(const [% classname %]& other);\r\n    };\r\n\r\n    #endif \/* #ifndef [% uc(classname) %]_HPP *\/\r\n    ________________________________________________________\r\n\r\n  run vim:\r\n    :Vimplate hpp-default\r\n    Class name: Parent\r\n    with Doxygen comments:\r\n      0) no\r\n      1) yes\r\n    1\r\n\r\n  your input was:\r\n    :Vimplate hpp-default<CR>Parent<CR>1<CR>\r\n\r\n  this will produce this c++ include file:\r\n    ________________________________________________________\r\n    #ifndef PARENT_HPP\r\n    #define PARENT_HPP\r\n\r\n    \/**\r\n     * @brief Parent ... short description ...\r\n     * @author Urs Stotz <stotz@gmx.ch>\r\n     * @date 2005-07-18\r\n     * ... description ...\r\n     *\/\r\n\r\n    class Parent\r\n    {\r\n      public:\r\n\r\n        \/**\r\n         * Default constructor\r\n         *\/\r\n        Parent();\r\n\r\n        \/**\r\n         * Copy constructor\r\n         * @param other reference on object to copy\r\n         *\/\r\n        Parent(const Parent& other);\r\n\r\n        \/**\r\n         * Assignment operator\r\n         * @param other reference on object to copy\r\n         * @return reference on initialisated object\r\n         *\/\r\n        Parent& operator=(const Parent& other);\r\n\r\n        \/**\r\n         * Destructor\r\n         *\/\r\n        virtual ~Parent();\r\n\r\n      private:\r\n\r\n        \/**\r\n         * Base initialisation should be called\r\n         * at beginning of each constructor\r\n         *\/\r\n        void init();\r\n\r\n        \/**\r\n         * Method to copy each member (deep copy)\r\n         * @param other reference on object to copy\r\n         *\/\r\n        void init(const Parent& other);\r\n    };\r\n\r\n    #endif \/* #ifndef PARENT_HPP *\/\r\n    ________________________________________________________\r\n\r\n\r\n5. Documentation                                    *vimplate-documentation*\r\n\r\nDocumentation:\r\n  - http:\/\/napali.ch\/vimplate\r\n  - http:\/\/www.template-toolkit.org\/docs.html\r\n  - http:\/\/perldoc.perl.org\/perl.html\r\n\r\nTodo:\r\n  - better exception handling\r\n  - write more templates\r\n\r\nLicense:\r\n  This program is free software; you can redistribute it and\/or modify it\r\n  under the terms of the GNU General Public License, version 2, as published\r\n  by the Free Software Foundation.\r\n\r\n  This program is distributed in the hope that it will be useful, but\r\n  WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY\r\n  or FITNESS FOR A PARTICULAR PURPOSE.  See the GNU General Public License\r\n  for more details.\r\n\r\n  A copy of the GNU GPL is available as \/usr\/share\/common-licenses\/GPL-2\r\n  on Debian systems, or on the World Wide Web at\r\n  http:\/\/www.gnu.org\/copyleft\/gpl.html\r\n  You can also obtain it by writing to the Free Software Foundation, Inc.,\r\n  59 Temple Place - Suite 330, Boston, MA 02111-1307, USA\r\n\r\nCopyright:\r\n  Copyright (c) 2005, Urs Stotz <stotz@gmx.ch>\r\n\r\nVersion:\r\n  vimplate 0.2.4","install_details":"6. Depends:                                               *vimplate-depends*\r\n\r\n  Perl\r\n    http:\/\/www.perl.org\r\n    Windows users:\r\n      http:\/\/www.activestate.com\/Products\/ActivePerl\r\n  Template-Toolkit\r\n    http:\/\/search.cpan.org\/~abw\/Template-Toolkit-2.14\r\n    or apt-get install libtemplate-perl\r\n    or perl -MCPAN -e\"install Template\"\r\n    Windows users:\r\n      ppm install\r\n        http:\/\/openinteract.sourceforge.net\/ppmpackages\/AppConfig.ppd\r\n      ppm install\r\n        http:\/\/openinteract.sourceforge.net\/ppmpackages\/Template-Toolkit.ppd\r\n\r\nSuggests:\r\n  TT2 syntax:\r\n    http:\/\/www.vim.org\/scripts\/script.php?script_id=830\r\n\r\n\r\n7. Installation                                      *vimplate-installation*\r\n\r\nInstallation steps:\r\n------------------------\r\n  1. change to your $HOME\/.vim directory\r\n       (on windows: set the variable HOME to \"C:\\Documents and Settings\\<Insert Your User Here>\").\r\n\r\n  2. Move vimplate.zip into your $HOME\/.vim folder and extract vimplate.zip there (on windows this folder is '%HOME%\\vimfiles').\r\n\r\n  3. edit your $HOME\/.vimrc (or %HOME%\\.vimrc on windows) and set the variable Vimplate to the filepath to vimplate.pl\r\n\r\n        On *nix, this should be the relative path to the vimplate.pl file.  For example:\r\n          let Vimplate = \"~\/.vim\/vimplate.pl\"\r\n\r\n        On windows, you have to use the full path.  If it has spaces in it you need to put escaped quotation marks around the entire value or it will not work.  For example, if my user name in Windows is \"Villanous Victor\", I would add:\r\n          let Vimplate = \"\\\"C:\/Documents and Settings\/Villanous Victor\/vimfiles\/vimplate.cmd\\\"\"\r\n             - or -\r\n          let Vimplate = \"\\\"C:\\\\Documents and Settings\\\\Villanous Victor\\\\vimfiles\\\\vimplate.cmd\\\"\"\r\n          (take note of the double slashing)\r\n\r\n  6. Run the appropriate command for your operating system to create the $HOME\/.vimplaterc (or %HOME%\/.vimplaterc on windows) configuration file.\r\n\r\n        On *nix, run `$HOME\/.vim\/vimplate.pl -createconfig` to create your configuration file.\r\n\r\n        On windows you can simple execute the file '%HOME%\/vimfiles\/vimplate_createconfig.cmd' to initiate the configuration.\r\n\r\n  7. edit your $HOME\/.vimplaterc\r\n       (on windows: %HOMEPATH%\/.vimplaterc)\r\n\r\n  8. Fire up vim and perform the appropriate helptag update command for your OS:\r\n\r\n        *nix: :helptags ~\/.vim\/doc\r\n\r\n        windows: :helptags ~\/vimfiles\/doc\r\n\r\n  9. Happy Vimplating! Please direct your questions and complaints to < outtatime@gmail.com > and I will do my best to respond in a timely manner.\r\n","5":"6. Depends:                                               *vimplate-depends*\r\n\r\n  Perl\r\n    http:\/\/www.perl.org\r\n    Windows users:\r\n      http:\/\/www.activestate.com\/Products\/ActivePerl\r\n  Template-Toolkit\r\n    http:\/\/search.cpan.org\/~abw\/Template-Toolkit-2.14\r\n    or apt-get install libtemplate-perl\r\n    or perl -MCPAN -e\"install Template\"\r\n    Windows users:\r\n      ppm install\r\n        http:\/\/openinteract.sourceforge.net\/ppmpackages\/AppConfig.ppd\r\n      ppm install\r\n        http:\/\/openinteract.sourceforge.net\/ppmpackages\/Template-Toolkit.ppd\r\n\r\nSuggests:\r\n  TT2 syntax:\r\n    http:\/\/www.vim.org\/scripts\/script.php?script_id=830\r\n\r\n\r\n7. Installation                                      *vimplate-installation*\r\n\r\nInstallation steps:\r\n------------------------\r\n  1. change to your $HOME\/.vim directory\r\n       (on windows: set the variable HOME to \"C:\\Documents and Settings\\<Insert Your User Here>\").\r\n\r\n  2. Move vimplate.zip into your $HOME\/.vim folder and extract vimplate.zip there (on windows this folder is '%HOME%\\vimfiles').\r\n\r\n  3. edit your $HOME\/.vimrc (or %HOME%\\.vimrc on windows) and set the variable Vimplate to the filepath to vimplate.pl\r\n\r\n        On *nix, this should be the relative path to the vimplate.pl file.  For example:\r\n          let Vimplate = \"~\/.vim\/vimplate.pl\"\r\n\r\n        On windows, you have to use the full path.  If it has spaces in it you need to put escaped quotation marks around the entire value or it will not work.  For example, if my user name in Windows is \"Villanous Victor\", I would add:\r\n          let Vimplate = \"\\\"C:\/Documents and Settings\/Villanous Victor\/vimfiles\/vimplate.cmd\\\"\"\r\n             - or -\r\n          let Vimplate = \"\\\"C:\\\\Documents and Settings\\\\Villanous Victor\\\\vimfiles\\\\vimplate.cmd\\\"\"\r\n          (take note of the double slashing)\r\n\r\n  6. Run the appropriate command for your operating system to create the $HOME\/.vimplaterc (or %HOME%\/.vimplaterc on windows) configuration file.\r\n\r\n        On *nix, run `$HOME\/.vim\/vimplate.pl -createconfig` to create your configuration file.\r\n\r\n        On windows you can simple execute the file '%HOME%\/vimfiles\/vimplate_createconfig.cmd' to initiate the configuration.\r\n\r\n  7. edit your $HOME\/.vimplaterc\r\n       (on windows: %HOMEPATH%\/.vimplaterc)\r\n\r\n  8. Fire up vim and perform the appropriate helptag update command for your OS:\r\n\r\n        *nix: :helptags ~\/.vim\/doc\r\n\r\n        windows: :helptags ~\/vimfiles\/doc\r\n\r\n  9. Happy Vimplating! Please direct your questions and complaints to < outtatime@gmail.com > and I will do my best to respond in a timely manner.\r\n","first_name":"Jai","6":"Jai","last_name":"Tkker","7":"Tkker","releases":[{"0":"1808","vim_version":"7.0","1":"7.0","script_version":"0.2.4","2":"0.2.4","version_comment":"Initial upload","3":"Initial upload","package":"vimplate-0.2.4.zip","4":"vimplate-0.2.4.zip","src_id":"6791","5":"6791","creation_date":"1172414999","6":"1172414999"}]},"1807":{"script_id":"1807","0":"1807","script_name":"calmar256-{light,dark}.vim","1":"calmar256-{light,dark}.vim","script_type":"color scheme","2":"color scheme","summary":"256 color-scheme for a capable terminal","3":"256 color-scheme for a capable terminal","description":"It should be *easy* to tweak the colors, \r\njust tweak the numbers based on this chart:\r\n\r\nhttp:\/\/www.calmar.ws\/vim\/256-xterm-24bit-rgb-color-chart.html\r\nor: \r\nhttp:\/\/www.calmar.ws\/vim\/terminalcolors.py\r\n\r\nalso see:\r\n:help hl-<highlight-group>  and \r\n:help highlight-groups\r\n\r\ncalmar256{light,dark}.vim generates the same color for you gvim, like in your 256 color terminal.\r\n\r\nScreenshot: \r\nhttp:\/\/www.calmar.ws\/vim\/calmar256-dark.vim.png\r\nhttp:\/\/www.calmar.ws\/vim\/calmar256-light.vim.png\r\n\r\n(Note: you may need a proper $TERM variable set, so that termcap\/terminfo\r\nknows it's a 256 color terminal. E.g. TERM=xterm-256color in xterm's case. but\r\nespecially set t_Co=256 in your .vimrc so vim knows about what you want.)\r\n\r\nMay also have a look at: \r\nhttp:\/\/www.calmar.ws\/vim\/ (paragraph: Vim and Colors)\r\n\r\nThe file themselves (very lastest version):\r\n\r\nhttp:\/\/www.calmar.ws\/dotfiles\/dotfiledir\/calmar256-dark.vim\r\nhttp:\/\/www.calmar.ws\/dotfiles\/dotfiledir\/calmar256-light.vim\r\n\r\n(feel free to upload improved versions etc, colors or code...)","4":"It should be *easy* to tweak the colors, \r\njust tweak the numbers based on this chart:\r\n\r\nhttp:\/\/www.calmar.ws\/vim\/256-xterm-24bit-rgb-color-chart.html\r\nor: \r\nhttp:\/\/www.calmar.ws\/vim\/terminalcolors.py\r\n\r\nalso see:\r\n:help hl-<highlight-group>  and \r\n:help highlight-groups\r\n\r\ncalmar256{light,dark}.vim generates the same color for you gvim, like in your 256 color terminal.\r\n\r\nScreenshot: \r\nhttp:\/\/www.calmar.ws\/vim\/calmar256-dark.vim.png\r\nhttp:\/\/www.calmar.ws\/vim\/calmar256-light.vim.png\r\n\r\n(Note: you may need a proper $TERM variable set, so that termcap\/terminfo\r\nknows it's a 256 color terminal. E.g. TERM=xterm-256color in xterm's case. but\r\nespecially set t_Co=256 in your .vimrc so vim knows about what you want.)\r\n\r\nMay also have a look at: \r\nhttp:\/\/www.calmar.ws\/vim\/ (paragraph: Vim and Colors)\r\n\r\nThe file themselves (very lastest version):\r\n\r\nhttp:\/\/www.calmar.ws\/dotfiles\/dotfiledir\/calmar256-dark.vim\r\nhttp:\/\/www.calmar.ws\/dotfiles\/dotfiledir\/calmar256-light.vim\r\n\r\n(feel free to upload improved versions etc, colors or code...)","install_details":"1. Store the color scheme in your ~\/.vim\/colors\/  or so.\r\n2. In vim itself or you vimrc file:\r\nset t_Co=256\r\ncolorscheme calmar256-light        \" or -dark","5":"1. Store the color scheme in your ~\/.vim\/colors\/  or so.\r\n2. In vim itself or you vimrc file:\r\nset t_Co=256\r\ncolorscheme calmar256-light        \" or -dark","first_name":"calmar","6":"calmar","last_name":"c","7":"c","releases":[{"0":"1807","vim_version":"6.0","1":"6.0","script_version":"0.98","2":"0.98","version_comment":"Added support for 'gui' style and guisp (color for undercurl) for gvim","3":"Added support for 'gui' style and guisp (color for undercurl) for gvim","package":"calmar256-light.vim","4":"calmar256-light.vim","src_id":"7572","5":"7572","creation_date":"1188271808","6":"1188271808"},{"0":"1807","vim_version":"6.0","1":"6.0","script_version":"0.98","2":"0.98","version_comment":"Added support for 'gui' style and guisp (color for undercurl) for gvim","3":"Added support for 'gui' style and guisp (color for undercurl) for gvim","package":"calmar256-dark.vim","4":"calmar256-dark.vim","src_id":"7571","5":"7571","creation_date":"1188271787","6":"1188271787"}]},"1806":{"script_id":"1806","0":"1806","script_name":"MultiEnc.vim","1":"MultiEnc.vim","script_type":"utility","2":"utility","summary":"Autodetect multiple encodings (more than 'fileencodings')","3":"Autodetect multiple encodings (more than 'fileencodings')","description":"------------------------------------------------------------------------\r\nIMPORTANT NOTICE: This script is now merged with Ming Bai's FencView.vim. The content below is now obsolete. Please go check vimscript#1708.\r\n------------------------------------------------------------------------\r\n\r\nThe Vim option 'fileencodings' has some limitations: e.g., it cannot autodetect GBK and Big5 files at the same time. This is my first motivation to write this script (and the support program tellenc).\r\n\r\nThis script does these things to decide the encoding of a file:\r\n\r\n- If a file has a modeline fileencoding=..., it will be used as the encoding to open the file.\r\n- If a file is an HTML file, and it has the encoding specified with a HTTP-EQUIV meta tag, it will be used as the encoding to open the file. The file pattern of HTML files can be customized by the global variable multienc_html_patterns.\r\n- If a file cannot be decided by the steps above, tellenc may be used to decide its encoding. This includes HTML files without a suitable HTTP-EQUIV meta tag, and additional files can be detected with the global variable multienc_auto_patterns.\r\n- A file can be manually autodetected with the command EditAutoEncoding (without a file name for the current buffer, or with a file name to edit a new file).\r\n- The autodetection may be overridden with the command EditManualEncoding (\"e ++enc=\" may not work in some cases now).\r\n\r\nThe program used to tell the encoding of a file is \"tellenc\" by default. It can also be changed with the environment variable MULTIENC_TELLENC. My current tellenc, available at http:\/\/wyw.dcweb.cn\/download.asp?path=&file=tellenc.zip, supports ASCII, UTF8, UTF-16, Latin1, Windows-1252, GB2312, GBK, Big5, and any Unicode encodings with BOM.","4":"------------------------------------------------------------------------\r\nIMPORTANT NOTICE: This script is now merged with Ming Bai's FencView.vim. The content below is now obsolete. Please go check vimscript#1708.\r\n------------------------------------------------------------------------\r\n\r\nThe Vim option 'fileencodings' has some limitations: e.g., it cannot autodetect GBK and Big5 files at the same time. This is my first motivation to write this script (and the support program tellenc).\r\n\r\nThis script does these things to decide the encoding of a file:\r\n\r\n- If a file has a modeline fileencoding=..., it will be used as the encoding to open the file.\r\n- If a file is an HTML file, and it has the encoding specified with a HTTP-EQUIV meta tag, it will be used as the encoding to open the file. The file pattern of HTML files can be customized by the global variable multienc_html_patterns.\r\n- If a file cannot be decided by the steps above, tellenc may be used to decide its encoding. This includes HTML files without a suitable HTTP-EQUIV meta tag, and additional files can be detected with the global variable multienc_auto_patterns.\r\n- A file can be manually autodetected with the command EditAutoEncoding (without a file name for the current buffer, or with a file name to edit a new file).\r\n- The autodetection may be overridden with the command EditManualEncoding (\"e ++enc=\" may not work in some cases now).\r\n\r\nThe program used to tell the encoding of a file is \"tellenc\" by default. It can also be changed with the environment variable MULTIENC_TELLENC. My current tellenc, available at http:\/\/wyw.dcweb.cn\/download.asp?path=&file=tellenc.zip, supports ASCII, UTF8, UTF-16, Latin1, Windows-1252, GB2312, GBK, Big5, and any Unicode encodings with BOM.","install_details":"Put multienc.vim in your Vim plugin directory, and tellenc in your path. Customize the pattern of HTML files and additional files with the global variables multienc_html_patterns and multienc_auto_patterns if needed. Set the global legacy_encoding with the default legacy encoding on your system.\r\n\r\nA simplistic _vimrc (for Windows) may be like:\r\n\r\n\" Legacy encoding is the system default encoding\r\nlet g:legacy_encoding=&encoding\r\n\r\nsource $VIMRUNTIME\/vimrc_example.vim\r\nsource $VIMRUNTIME\/mswin.vim\r\n\r\nif has('gui_running')\r\n  set encoding=utf-8\r\nelse\r\n  if &termencoding != '' && &termencoding != &encoding\r\n    let &encoding=&termencoding\r\n    let &fileencodings='ucs-bom,utf-8,' . &encoding\r\n  endif\r\nendif\r\n\r\n\" Set default file encoding(s) to the legacy encoding\r\nexec 'set fileencoding=' . g:legacy_encoding\r\nlet &fileencodings=substitute\r\n                  \\(&fileencodings, '\\<default\\>', g:legacy_encoding, '')\r\n\r\n\" File patterns of files for automatic encoding detection\r\nlet multienc_auto_patterns='*.txt,*.tex'\r\nlet multienc_html_patterns='*.htm{l\\=},*.asp'","5":"Put multienc.vim in your Vim plugin directory, and tellenc in your path. Customize the pattern of HTML files and additional files with the global variables multienc_html_patterns and multienc_auto_patterns if needed. Set the global legacy_encoding with the default legacy encoding on your system.\r\n\r\nA simplistic _vimrc (for Windows) may be like:\r\n\r\n\" Legacy encoding is the system default encoding\r\nlet g:legacy_encoding=&encoding\r\n\r\nsource $VIMRUNTIME\/vimrc_example.vim\r\nsource $VIMRUNTIME\/mswin.vim\r\n\r\nif has('gui_running')\r\n  set encoding=utf-8\r\nelse\r\n  if &termencoding != '' && &termencoding != &encoding\r\n    let &encoding=&termencoding\r\n    let &fileencodings='ucs-bom,utf-8,' . &encoding\r\n  endif\r\nendif\r\n\r\n\" Set default file encoding(s) to the legacy encoding\r\nexec 'set fileencoding=' . g:legacy_encoding\r\nlet &fileencodings=substitute\r\n                  \\(&fileencodings, '\\<default\\>', g:legacy_encoding, '')\r\n\r\n\" File patterns of files for automatic encoding detection\r\nlet multienc_auto_patterns='*.txt,*.tex'\r\nlet multienc_html_patterns='*.htm{l\\=},*.asp'","first_name":"Yongwei","6":"Yongwei","last_name":"Wu","7":"Wu","releases":[{"0":"1806","vim_version":"7.0","1":"7.0","script_version":"1.4","2":"1.4","version_comment":"Normalize detected encoding names to make it work better with fileencodings.","3":"Normalize detected encoding names to make it work better with fileencodings.","package":"multienc.vim","4":"multienc.vim","src_id":"6807","5":"6807","creation_date":"1172547933","6":"1172547933"},{"0":"1806","vim_version":"7.0","1":"7.0","script_version":"1.3","2":"1.3","version_comment":"Enhance using modeline to set fileencoding.","3":"Enhance using modeline to set fileencoding.","package":"multienc.vim","4":"multienc.vim","src_id":"6786","5":"6786","creation_date":"1172380898","6":"1172380898"}]},"1805":{"script_id":"1805","0":"1805","script_name":"SearchFold","1":"SearchFold","script_type":"utility","2":"utility","summary":"Search a file by folding non-matching lines with optional context.","3":"Search a file by folding non-matching lines with optional context.","description":"SearchFold is a good script to have around. You give it a search string to find and folds everything except for the lines where the string matches. By default is keeps some non-matching lines around so you can get an idea of where you are in the file and gives you the ability to expand \u00e2\u0080\u009cthe view\u00e2\u0080\u009d for a particular match to get more context. After you are done looking around you can \u00e2\u0080\u009cquit\u00e2\u0080\u009d the script and keep the fold or go back to the file as it was (restoring any previous folds).\r\n\r\nCheck  out this page for a screen shot.\r\nhttp:\/\/juan.boxfi.com\/vim-plugins\/#searchfold","4":"SearchFold is a good script to have around. You give it a search string to find and folds everything except for the lines where the string matches. By default is keeps some non-matching lines around so you can get an idea of where you are in the file and gives you the ability to expand \u00e2\u0080\u009cthe view\u00e2\u0080\u009d for a particular match to get more context. After you are done looking around you can \u00e2\u0080\u009cquit\u00e2\u0080\u009d the script and keep the fold or go back to the file as it was (restoring any previous folds).\r\n\r\nCheck  out this page for a screen shot.\r\nhttp:\/\/juan.boxfi.com\/vim-plugins\/#searchfold","install_details":"1. Read the section titled 'Options'\r\n2. Setup any variables need in your vimrc file\r\n3. Copy 'searchfold.vim' to your plugin directory.","5":"1. Read the section titled 'Options'\r\n2. Setup any variables need in your vimrc file\r\n3. Copy 'searchfold.vim' to your plugin directory.","first_name":"Juan","6":"Juan","last_name":"Frias","7":"Frias","releases":[{"0":"1805","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"searchfold.vim","4":"searchfold.vim","src_id":"6776","5":"6776","creation_date":"1172220874","6":"1172220874"}]},"1804":{"script_id":"1804","0":"1804","script_name":"brief2","1":"brief2","script_type":"utility","2":"utility","summary":"Brief emulation","3":"Brief emulation","description":"This is based on \"brief.vim\" authored by Yegappan Lakshmanan.\r\nIt has some minor improvements, but I hope to add more to make the emulation as complete as possible.  I started using this under Vim 6.3, and have tried it on 7.0 with good success.\r\n\r\n","4":"This is based on \"brief.vim\" authored by Yegappan Lakshmanan.\r\nIt has some minor improvements, but I hope to add more to make the emulation as complete as possible.  I started using this under Vim 6.3, and have tried it on 7.0 with good success.\r\n\r\n","install_details":"Copy this file into your plugin directory.\r\n","5":"Copy this file into your plugin directory.\r\n","first_name":"Richard","6":"Richard","last_name":"Jones","7":"Jones","releases":[{"0":"1804","vim_version":"6.0","1":"6.0","script_version":"1.01","2":"1.01","version_comment":"Initial upload","3":"Initial upload","package":"brief2.vim","4":"brief2.vim","src_id":"6775","5":"6775","creation_date":"1172220365","6":"1172220365"}]},"1803":{"script_id":"1803","0":"1803","script_name":"compview","1":"compview","script_type":"utility","2":"utility","summary":"Creates an interactive search window","3":"Creates an interactive search window","description":"CompView.vim is a handy little script that I use all the time. After a search term is entered it generates a list of matches and displays a window with all the matching lines. As you move around this window to different matched lines the original window is automatically updated to show you where in the file the match is found. It is like an interactive \u00e2\u0080\u0098cw\u00e2\u0080\u0099 command.\r\n\r\nCheck out this page for a screen shot of the script in action.\r\nhttp:\/\/juan.boxfi.com\/vim-plugins\/#compview","4":"CompView.vim is a handy little script that I use all the time. After a search term is entered it generates a list of matches and displays a window with all the matching lines. As you move around this window to different matched lines the original window is automatically updated to show you where in the file the match is found. It is like an interactive \u00e2\u0080\u0098cw\u00e2\u0080\u0099 command.\r\n\r\nCheck out this page for a screen shot of the script in action.\r\nhttp:\/\/juan.boxfi.com\/vim-plugins\/#compview","install_details":"1. Read the section titled 'Options'\r\n2. Setup any variables need in your vimrc file\r\n3. Copy 'compview.vim' to your plugin directory.","5":"1. Read the section titled 'Options'\r\n2. Setup any variables need in your vimrc file\r\n3. Copy 'compview.vim' to your plugin directory.","first_name":"Juan","6":"Juan","last_name":"Frias","7":"Frias","releases":[{"0":"1803","vim_version":"6.0","1":"6.0","script_version":"1.05","2":"1.05","version_comment":"Fixed problems with multiple tags and buffers.","3":"Fixed problems with multiple tags and buffers.","package":"compview.vim","4":"compview.vim","src_id":"10385","5":"10385","creation_date":"1239466726","6":"1239466726"}]},"1802":{"script_id":"1802","0":"1802","script_name":"eclipse.vim","1":"eclipse.vim","script_type":"color scheme","2":"color scheme","summary":"Eclipse like color scheme","3":"Eclipse like color scheme","description":"This color scheme is based on the default colors of the eclipse development environment.\r\n\r\nCheck out some screen shots of what it looks like with Vim script, Java and C++\r\nhttp:\/\/juan.boxfi.com\/vim-color-schemes\/#eclipse","4":"This color scheme is based on the default colors of the eclipse development environment.\r\n\r\nCheck out some screen shots of what it looks like with Vim script, Java and C++\r\nhttp:\/\/juan.boxfi.com\/vim-color-schemes\/#eclipse","install_details":"Just drop in your colors directory.","5":"Just drop in your colors directory.","first_name":"Juan","6":"Juan","last_name":"Frias","7":"Frias","releases":[{"0":"1802","vim_version":"6.0","1":"6.0","script_version":"1.0.2","2":"1.0.2","version_comment":"Minor correction to SpecialKey and Title colors","3":"Minor correction to SpecialKey and Title colors","package":"eclipse.vim","4":"eclipse.vim","src_id":"6890","5":"6890","creation_date":"1174294866","6":"1174294866"}]},"1801":{"script_id":"1801","0":"1801","script_name":"c16gui","1":"c16gui","script_type":"color scheme","2":"color scheme","summary":"A default-looking GUI color scheme of the 16 colors","3":"A default-looking GUI color scheme of the 16 colors","description":"c16gui is a GUI color scheme composed of the sixteen colors, which simulates\r\nthe default scheme.\r\n\r\nscreen shots: http:\/\/www.geocities.jp\/e27874\/","4":"c16gui is a GUI color scheme composed of the sixteen colors, which simulates\r\nthe default scheme.\r\n\r\nscreen shots: http:\/\/www.geocities.jp\/e27874\/","install_details":"The zip archive contains two files, colors\/c16gui.vim and syntax\/c16gui.vim.\r\nLocate the \"colors\/c16gui.vim\" in your \"$HOME\/.vim\/colors\" directory.\r\nLocate the \"syntax\/c16gui.vim\" in your \"$HOME\/.vim\/syntax\" directory.\r\nNow, you've got two files in your computer, the \"$HOME\/.vim\/colors\/c16gui.vim\"\r\nand the \"$HOME\/.vim\/syntax\/c16gui.vim\".\r\n\r\n- You might have to set the 'background' option explicitly before loading the\r\n  color scheme.\r\n- When you change highlightings for some groups, the \"syntax\/c16gui.vim\" will\r\n  help you.  It is an auto-highlighting syntax file.  You can see the sixteen\r\n  colors by browsing that file itself.  Type \":set syn=c16gui\" after entering\r\n  the file if the 'modeline' option is off.  The \":syntax enable\" will also be\r\n  needed to make it work.\r\n\r\nExample of the \"$HOME\/.gvimrc\":\r\n  set bg=light\r\n  colorscheme c16gui\r\n  hi DiffText guifg=#ffffff\r\n  hi DiffChange guifg=fg\r\n\r\nFor Win32, the directory \"$HOME\/.vim\" is \"%HOME%\\vimfiles\", and the file\r\n\"$HOME\/.gvimrc\" is \"%HOME%\\_gvimrc\".  See \":help 'runtimepath'\" for details.","5":"The zip archive contains two files, colors\/c16gui.vim and syntax\/c16gui.vim.\r\nLocate the \"colors\/c16gui.vim\" in your \"$HOME\/.vim\/colors\" directory.\r\nLocate the \"syntax\/c16gui.vim\" in your \"$HOME\/.vim\/syntax\" directory.\r\nNow, you've got two files in your computer, the \"$HOME\/.vim\/colors\/c16gui.vim\"\r\nand the \"$HOME\/.vim\/syntax\/c16gui.vim\".\r\n\r\n- You might have to set the 'background' option explicitly before loading the\r\n  color scheme.\r\n- When you change highlightings for some groups, the \"syntax\/c16gui.vim\" will\r\n  help you.  It is an auto-highlighting syntax file.  You can see the sixteen\r\n  colors by browsing that file itself.  Type \":set syn=c16gui\" after entering\r\n  the file if the 'modeline' option is off.  The \":syntax enable\" will also be\r\n  needed to make it work.\r\n\r\nExample of the \"$HOME\/.gvimrc\":\r\n  set bg=light\r\n  colorscheme c16gui\r\n  hi DiffText guifg=#ffffff\r\n  hi DiffChange guifg=fg\r\n\r\nFor Win32, the directory \"$HOME\/.vim\" is \"%HOME%\\vimfiles\", and the file\r\n\"$HOME\/.gvimrc\" is \"%HOME%\\_gvimrc\".  See \":help 'runtimepath'\" for details.","first_name":"Hideyuki","6":"Hideyuki","last_name":"Kobayashi","7":"Kobayashi","releases":[{"0":"1801","vim_version":"7.0","1":"7.0","script_version":"1.0.1","2":"1.0.1","version_comment":"CursorIM removed, DiffAdd and DiffDelete changed.","3":"CursorIM removed, DiffAdd and DiffDelete changed.","package":"c16gui.zip","4":"c16gui.zip","src_id":"7873","5":"7873","creation_date":"1194147655","6":"1194147655"},{"0":"1801","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"c16gui.zip","4":"c16gui.zip","src_id":"6749","5":"6749","creation_date":"1171765056","6":"1171765056"}]},"1800":{"script_id":"1800","0":"1800","script_name":"IndentHL","1":"IndentHL","script_type":"syntax","2":"syntax","summary":"Color each indent level in different colors.","3":"Color each indent level in different colors.","description":"A simple syntax coloring script you can use to augment existing syntaxes with to include highlighting of each indent level with a different color.\r\n\r\nSee http:\/\/viming.blogspot.com\/2007\/02\/indent-level-highlighting.html for screenshots.","4":"A simple syntax coloring script you can use to augment existing syntaxes with to include highlighting of each indent level with a different color.\r\n\r\nSee http:\/\/viming.blogspot.com\/2007\/02\/indent-level-highlighting.html for screenshots.","install_details":"See :help mysyntaxfile-add for installation details.","5":"See :help mysyntaxfile-add for installation details.","first_name":"Dane","6":"Dane","last_name":"Summers","7":"Summers","releases":[{"0":"1800","vim_version":"7.0","1":"7.0","script_version":"1.3","2":"1.3","version_comment":"Adds indent level highlighting for spaces now as well as tabs (respecting expandtab and shiftwidth settings).\r\nError highlighting for bad combinations of tabs\/spaces.\r\nConfigurable settings added.","3":"Adds indent level highlighting for spaces now as well as tabs (respecting expandtab and shiftwidth settings).\r\nError highlighting for bad combinations of tabs\/spaces.\r\nConfigurable settings added.","package":"indenthl.zip","4":"indenthl.zip","src_id":"15279","5":"15279","creation_date":"1300906134","6":"1300906134"},{"0":"1800","vim_version":"7.0","1":"7.0","script_version":"2","2":"2","version_comment":"Problem with some this syntax not working with some types (ruby) corrected.","3":"Problem with some this syntax not working with some types (ruby) corrected.","package":"indenthl.vim.gz","4":"indenthl.vim.gz","src_id":"6753","5":"6753","creation_date":"1171800506","6":"1171800506"},{"0":"1800","vim_version":"7.0","1":"7.0","script_version":"1","2":"1","version_comment":"Initial upload","3":"Initial upload","package":"indenthl.vim.gz","4":"indenthl.vim.gz","src_id":"6748","5":"6748","creation_date":"1171719090","6":"1171719090"}]},"1799":{"script_id":"1799","0":"1799","script_name":"polycfg.vim","1":"polycfg.vim","script_type":"syntax","2":"syntax","summary":"Polyhedra configuration syntax","3":"Polyhedra configuration syntax","description":"This script provides syntax highlighting for the configuration files of the Polyhedra database.\r\nFor more information about Polyhedra, see: http:\/\/www.enea.com\/templates\/Extension____259.aspx\r\n\r\nSee also vimscript#1782: Polyhedra CL syntax","4":"This script provides syntax highlighting for the configuration files of the Polyhedra database.\r\nFor more information about Polyhedra, see: http:\/\/www.enea.com\/templates\/Extension____259.aspx\r\n\r\nSee also vimscript#1782: Polyhedra CL syntax","install_details":"Save into your personnal syntax directory: $HOME\/{.vim|vimfiles}\/syntax ({Unix|Windows}).\r\n\r\nTo manually colorize a file:\r\n  :syntax on\r\n  :filetype on\r\n  :set filetype=polycfg\r\n\r\nTo assign this syntax to a particular configuration file, add this at the beginning or at the end:\r\n  -- vim: set filetype=polycfg :\r\n\r\nSee also the built-in help in Vim:\r\n    :help 'filetype'\r\n    :help 'modeline'\r\n    :help filetype-plugin\r\n    :help mysyntaxfile\r\n","5":"Save into your personnal syntax directory: $HOME\/{.vim|vimfiles}\/syntax ({Unix|Windows}).\r\n\r\nTo manually colorize a file:\r\n  :syntax on\r\n  :filetype on\r\n  :set filetype=polycfg\r\n\r\nTo assign this syntax to a particular configuration file, add this at the beginning or at the end:\r\n  -- vim: set filetype=polycfg :\r\n\r\nSee also the built-in help in Vim:\r\n    :help 'filetype'\r\n    :help 'modeline'\r\n    :help filetype-plugin\r\n    :help mysyntaxfile\r\n","first_name":"Olivier","6":"Olivier","last_name":"Mengu\u00c3\u00a9","7":"Mengu\u00c3\u00a9","releases":[{"0":"1799","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"polycfg.vim","4":"polycfg.vim","src_id":"6745","5":"6745","creation_date":"1171555392","6":"1171555392"}]},"1798":{"script_id":"1798","0":"1798","script_name":"smarty.vim","1":"smarty.vim","script_type":"syntax","2":"syntax","summary":"smarty syntax file","3":"smarty syntax file","description":"A friend and I found that there were no acceptable vim syntax files for smarty, so we took the only one we could find and added everything from the smarty documentation (http:\/\/smarty.php.net\/manual\/en) to it.  If nothing else, this is a very good start on a complete smarty syntax file.  We have even used vimtip #498 to use autocomplete with this syntax and so far it seems to work well.","4":"A friend and I found that there were no acceptable vim syntax files for smarty, so we took the only one we could find and added everything from the smarty documentation (http:\/\/smarty.php.net\/manual\/en) to it.  If nothing else, this is a very good start on a complete smarty syntax file.  We have even used vimtip #498 to use autocomplete with this syntax and so far it seems to work well.","install_details":"just drop it in your ~\/.vim\/syntax directory, then put this somewhere in your vimrc file: \r\n\r\nau BufRead,BufNewFile *.tpl set filetype=smarty\r\n\r\nadditionally, if you would like dictionary completion, feel free to add something like this:\r\n\r\nau Filetype smarty exec('set dictionary=\/home\/user\/.vim\/syntax\/smarty.vim')\r\nau Filetype smarty set complete+=k\r\n\r\nThis will allow <Control-x><Control-k> for dictionary autocomplete. \r\nWe have a mapping that makes it a bit easier:\r\n\r\nimap <S-Space><S-Space> <C-X><C-K>\r\n\r\nYou could use imap <C-Space> <C-X><C-K>, but we have that mapped for normal omni (auto) completion.","5":"just drop it in your ~\/.vim\/syntax directory, then put this somewhere in your vimrc file: \r\n\r\nau BufRead,BufNewFile *.tpl set filetype=smarty\r\n\r\nadditionally, if you would like dictionary completion, feel free to add something like this:\r\n\r\nau Filetype smarty exec('set dictionary=\/home\/user\/.vim\/syntax\/smarty.vim')\r\nau Filetype smarty set complete+=k\r\n\r\nThis will allow <Control-x><Control-k> for dictionary autocomplete. \r\nWe have a mapping that makes it a bit easier:\r\n\r\nimap <S-Space><S-Space> <C-X><C-K>\r\n\r\nYou could use imap <C-Space> <C-X><C-K>, but we have that mapped for normal omni (auto) completion.","first_name":"Ken","6":"Ken","last_name":"Earl","7":"Earl","releases":[{"0":"1798","vim_version":"7.0","1":"7.0","script_version":"2","2":"2","version_comment":"a few small fixes.  Added support for single quotes.","3":"a few small fixes.  Added support for single quotes.","package":"smarty.vim","4":"smarty.vim","src_id":"6741","5":"6741","creation_date":"1171380008","6":"1171380008"},{"0":"1798","vim_version":"7.0","1":"7.0","script_version":"1","2":"1","version_comment":"Initial upload","3":"Initial upload","package":"smarty.vim","4":"smarty.vim","src_id":"6734","5":"6734","creation_date":"1171017811","6":"1171017811"}]},"1797":{"script_id":"1797","0":"1797","script_name":"svnvimdiff","1":"svnvimdiff","script_type":"utility","2":"utility","summary":"svn diff + vimdiff","3":"svn diff + vimdiff","description":"This shell script will display svn diff output by using vimdiff. If you use the -g switch, you use gvimdiff instead of vimdiff. This was cloned from the script cvsvimdiff, written by Stefano Zacchiroli and Enrico Tassi. It launches whatever vim version you have.","4":"This shell script will display svn diff output by using vimdiff. If you use the -g switch, you use gvimdiff instead of vimdiff. This was cloned from the script cvsvimdiff, written by Stefano Zacchiroli and Enrico Tassi. It launches whatever vim version you have.","install_details":"The download itself is a bash shell script, so as long as bash is installed, you don't need to do anything other than make the file executable.","5":"The download itself is a bash shell script, so as long as bash is installed, you don't need to do anything other than make the file executable.","first_name":"Geoff","6":"Geoff","last_name":"Buchan","7":"Buchan","releases":[{"0":"1797","vim_version":"7.0","1":"7.0","script_version":"1.9","2":"1.9","version_comment":"Replace tempfile with mktemp to generate temporary file names. tempfile is deprecated and no longer distributed in Fedora 36, while mktemp exists there and in the older Debian releases I use.","3":"Replace tempfile with mktemp to generate temporary file names. tempfile is deprecated and no longer distributed in Fedora 36, while mktemp exists there and in the older Debian releases I use.","package":"svnvimdiff","4":"svnvimdiff","src_id":"28056","5":"28056","creation_date":"1653523873","6":"1653523873"},{"0":"1797","vim_version":"7.0","1":"7.0","script_version":"1.7","2":"1.7","version_comment":"Bug fix in filename - thanks to Martin Koniczek for finding it!","3":"Bug fix in filename - thanks to Martin Koniczek for finding it!","package":"svnvimdiff","4":"svnvimdiff","src_id":"22287","5":"22287","creation_date":"1407179151","6":"1407179151"},{"0":"1797","vim_version":"7.0","1":"7.0","script_version":"1.6","2":"1.6","version_comment":"Fix switch arguments to tempfile, and change temporary file name\r\nto use full filename, not just the last token of it.\r\nThanks to Stefan Heinemann for pointing out the change to tempfile!","3":"Fix switch arguments to tempfile, and change temporary file name\r\nto use full filename, not just the last token of it.\r\nThanks to Stefan Heinemann for pointing out the change to tempfile!","package":"svnvimdiff","4":"svnvimdiff","src_id":"19777","5":"19777","creation_date":"1365359394","6":"1365359394"},{"0":"1797","vim_version":"7.0","1":"7.0","script_version":"1.5","2":"1.5","version_comment":"Bug fix: remove temporary file with file suffix on exit","3":"Bug fix: remove temporary file with file suffix on exit","package":"svnvimdiff","4":"svnvimdiff","src_id":"11270","5":"11270","creation_date":"1251333107","6":"1251333107"},{"0":"1797","vim_version":"7.0","1":"7.0","script_version":"1.4","2":"1.4","version_comment":"Add code to put orignal file suffix on patched file.\r\nThis fixes syntax highlighting for the file.\r\nThanks to Stefan Heinemann for the patch!","3":"Add code to put orignal file suffix on patched file.\r\nThis fixes syntax highlighting for the file.\r\nThanks to Stefan Heinemann for the patch!","package":"svnvimdiff","4":"svnvimdiff","src_id":"11258","5":"11258","creation_date":"1251251651","6":"1251251651"},{"0":"1797","vim_version":"7.0","1":"7.0","script_version":"1.2","2":"1.2","version_comment":"Fix: don't fail when you pass arguments to svn diff but no filename","3":"Fix: don't fail when you pass arguments to svn diff but no filename","package":"svnvimdiff","4":"svnvimdiff","src_id":"7491","5":"7491","creation_date":"1186801555","6":"1186801555"},{"0":"1797","vim_version":"7.0","1":"7.0","script_version":"1.1","2":"1.1","version_comment":"Add support to pass additional arguments to svndiff, so, for example, you can diff against particular revisions.\r\n","3":"Add support to pass additional arguments to svndiff, so, for example, you can diff against particular revisions.\r\n","package":"svnvimdiff","4":"svnvimdiff","src_id":"7490","5":"7490","creation_date":"1186800378","6":"1186800378"},{"0":"1797","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"svnvimdiff","4":"svnvimdiff","src_id":"6726","5":"6726","creation_date":"1170808581","6":"1170808581"}]},"1796":{"script_id":"1796","0":"1796","script_name":"SETL2","1":"SETL2","script_type":"syntax","2":"syntax","summary":"Syntax file for SETL2 sources","3":"Syntax file for SETL2 sources","description":"First attempt to create a syntax file for SETL2 sources.","4":"First attempt to create a syntax file for SETL2 sources.","install_details":"","5":"","first_name":"Oscar","6":"Oscar","last_name":"Hellstr\u00c3\u00b6m","7":"Hellstr\u00c3\u00b6m","releases":[{"0":"1796","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"setl.vim","4":"setl.vim","src_id":"6724","5":"6724","creation_date":"1170745448","6":"1170745448"}]},"1795":{"script_id":"1795","0":"1795","script_name":"autoloadTemplate.vim","1":"autoloadTemplate.vim","script_type":"utility","2":"utility","summary":"load the template according the filetype while editing a new file","3":"load the template according the filetype while editing a new file","description":" Load template file from a specific directory according their filetype while\r\n starting to edit a new file. if the file does not exist, skip it!","4":" Load template file from a specific directory according their filetype while\r\n starting to edit a new file. if the file does not exist, skip it!","install_details":"   Here is the way to install this script to your site:\r\n     1. extract this file to ~\/.vim\/plugin\r\n     2. create a directory ~\/.vim\/template\r\n     3. create your template files in that directory, where the file name follow\r\n   the rule:\r\n      <filetype>.vim\r\n      where <filetype> is the filetype of this template will apply to, such\r\n      as: verilog.vim, tcl.vim and so on.","5":"   Here is the way to install this script to your site:\r\n     1. extract this file to ~\/.vim\/plugin\r\n     2. create a directory ~\/.vim\/template\r\n     3. create your template files in that directory, where the file name follow\r\n   the rule:\r\n      <filetype>.vim\r\n      where <filetype> is the filetype of this template will apply to, such\r\n      as: verilog.vim, tcl.vim and so on.","first_name":"Alan","6":"Alan","last_name":"Che","7":"Che","releases":[{"0":"1795","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"autoloadTemplate-0.1.zip","4":"autoloadTemplate-0.1.zip","src_id":"6723","5":"6723","creation_date":"1170711107","6":"1170711107"}]},"1794":{"script_id":"1794","0":"1794","script_name":"vibrantink","1":"vibrantink","script_type":"color scheme","2":"color scheme","summary":"A Vim port of Justin Palmer's VibrantInk theme for TextMate","3":"A Vim port of Justin Palmer's VibrantInk theme for TextMate","description":"Based on John Lam's rudimentary Vim version of Justin Palmer's Vibrant Ink color scheme for TextMate. This scheme also works on 256 color terminals.\r\n\r\nScreenshot at http:\/\/jozilla.net\/images\/software\/scripts\/vibrantink.png","4":"Based on John Lam's rudimentary Vim version of Justin Palmer's Vibrant Ink color scheme for TextMate. This scheme also works on 256 color terminals.\r\n\r\nScreenshot at http:\/\/jozilla.net\/images\/software\/scripts\/vibrantink.png","install_details":"Just copy it into ~\/.vim\/colors\/, as with other color schemes.","5":"Just copy it into ~\/.vim\/colors\/, as with other color schemes.","first_name":"Jo","6":"Jo","last_name":"Vermeulen","7":"Vermeulen","releases":[{"0":"1794","vim_version":"6.0","1":"6.0","script_version":"1.3","2":"1.3","version_comment":"No new functionality, just a small change to the description (the original TextMate theme is actually called \"Vibrant Ink\" instead of \"VibrantInk\").","3":"No new functionality, just a small change to the description (the original TextMate theme is actually called \"Vibrant Ink\" instead of \"VibrantInk\").","package":"vibrantink.vim","4":"vibrantink.vim","src_id":"10117","5":"10117","creation_date":"1236257038","6":"1236257038"},{"0":"1794","vim_version":"6.0","1":"6.0","script_version":"1.2","2":"1.2","version_comment":"Added license information.","3":"Added license information.","package":"vibrantink.vim","4":"vibrantink.vim","src_id":"7427","5":"7427","creation_date":"1185758229","6":"1185758229"},{"0":"1794","vim_version":"6.0","1":"6.0","script_version":"1.1","2":"1.1","version_comment":"Updated to support CursorLine highlighting (new in Vim 7.0), using the same colors as the original Textmate theme. Thanks to Eustaquio Rangel De Oliveira Jr. (username TaQ) for mentioning this problem to me.","3":"Updated to support CursorLine highlighting (new in Vim 7.0), using the same colors as the original Textmate theme. Thanks to Eustaquio Rangel De Oliveira Jr. (username TaQ) for mentioning this problem to me.","package":"vibrantink.vim","4":"vibrantink.vim","src_id":"6966","5":"6966","creation_date":"1176188814","6":"1176188814"},{"0":"1794","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"vibrantink.vim","4":"vibrantink.vim","src_id":"6719","5":"6719","creation_date":"1170648741","6":"1170648741"}]},"1793":{"script_id":"1793","0":"1793","script_name":"fcsh tools","1":"fcsh tools","script_type":"utility","2":"utility","summary":"you can compile .as and .mxml files from vim via fcsh : Flex Comipler SHell","3":"you can compile .as and .mxml files from vim via fcsh : Flex Comipler SHell","description":"fcsh can compile actionscript 3 and mxml files.\r\nincluded are fcshserv.sh and fcshcmp.sh.\r\nfcshserv.sh should be launched manually before you edit\r\n.as or .mxml files.\r\nthen, you can execute fcshcmp.sh from vim to compile and optionally run .swf file.\r\n","4":"fcsh can compile actionscript 3 and mxml files.\r\nincluded are fcshserv.sh and fcshcmp.sh.\r\nfcshserv.sh should be launched manually before you edit\r\n.as or .mxml files.\r\nthen, you can execute fcshcmp.sh from vim to compile and optionally run .swf file.\r\n","install_details":"requirements:\r\n- fcsh ( http:\/\/labs.adobe.com\/wiki\/index.php\/Flex_Compiler_Shell )\r\n- bash\r\n\r\nTested only on GNU\/Linux. Might work on *nix or cygwin.\r\n\r\n1) tar xvjf fcshtools.tar.bz2\r\n\r\n2) cd fcshtools\r\n\r\n3) cp *.sh <wherever you want>\r\nit's recommended to put  the files to $HOME\/bin.\r\n\r\n4) set FCSH_VIM_ROOT = $<wherever you want>\r\nif you don't set this environment variable, it'll look at $HOME\/bin.\r\n\r\n5) edit ~\/.vimrc\r\nif you put the files to $HOME\/bin, then add these:\r\n    autocmd BufNewFile,BufRead *.mxml,*.as :nmap <C-B> :!bash ~\/bin\/fcshcmp.sh %:p\r\n    autocmd BufNewFile,BufRead *.mxml,*.as :nmap <C-A> :!bash ~\/bin\/fcshcmp.sh %:p run\r\n\r\n<C-B> will just compile the current file being edited.\r\n<C-A> will compile and run the .swf on flashplayer.\r\n\r\n6) bash $FCSH_VIM_ROOT\/fcshserv.sh\r\nthis runs fcsh and creates a named pipe so fcshcmp.sh can send messages to.\r\nCtrl+C quits the server.\r\n\r\n7) vim hello.as\r\n\r\n8) <C-B> or <C-A>\r\n","5":"requirements:\r\n- fcsh ( http:\/\/labs.adobe.com\/wiki\/index.php\/Flex_Compiler_Shell )\r\n- bash\r\n\r\nTested only on GNU\/Linux. Might work on *nix or cygwin.\r\n\r\n1) tar xvjf fcshtools.tar.bz2\r\n\r\n2) cd fcshtools\r\n\r\n3) cp *.sh <wherever you want>\r\nit's recommended to put  the files to $HOME\/bin.\r\n\r\n4) set FCSH_VIM_ROOT = $<wherever you want>\r\nif you don't set this environment variable, it'll look at $HOME\/bin.\r\n\r\n5) edit ~\/.vimrc\r\nif you put the files to $HOME\/bin, then add these:\r\n    autocmd BufNewFile,BufRead *.mxml,*.as :nmap <C-B> :!bash ~\/bin\/fcshcmp.sh %:p\r\n    autocmd BufNewFile,BufRead *.mxml,*.as :nmap <C-A> :!bash ~\/bin\/fcshcmp.sh %:p run\r\n\r\n<C-B> will just compile the current file being edited.\r\n<C-A> will compile and run the .swf on flashplayer.\r\n\r\n6) bash $FCSH_VIM_ROOT\/fcshserv.sh\r\nthis runs fcsh and creates a named pipe so fcshcmp.sh can send messages to.\r\nCtrl+C quits the server.\r\n\r\n7) vim hello.as\r\n\r\n8) <C-B> or <C-A>\r\n","first_name":"mike","6":"mike","last_name":"rowe","7":"rowe","releases":[{"0":"1793","vim_version":"6.0","1":"6.0","script_version":"0.2","2":"0.2","version_comment":"added more quotes.","3":"added more quotes.","package":"fcshtools.tar.bz2","4":"fcshtools.tar.bz2","src_id":"6744","5":"6744","creation_date":"1171540960","6":"1171540960"},{"0":"1793","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"fcshtools.tar.bz2","4":"fcshtools.tar.bz2","src_id":"6717","5":"6717","creation_date":"1170615150","6":"1170615150"}]},"1792":{"script_id":"1792","0":"1792","script_name":"erm.vim","1":"erm.vim","script_type":"syntax","2":"syntax","summary":"Syntax highlight for ERM","3":"Syntax highlight for ERM","description":"ERM is a script language, the design is similar to most assembler language such as ARM assembler. \r\n\r\nBut the source code is extremely difficult to read without syntax highlight due to it's obfuscated syntax.\r\n\r\nNow you can edit ERM in Vim, bear in mind that ERM script must always be saved in Unix format even in MacOS and Windows. If anything does go wrong, open the script in ERM_S and save it.\r\n\r\nEnjoy!","4":"ERM is a script language, the design is similar to most assembler language such as ARM assembler. \r\n\r\nBut the source code is extremely difficult to read without syntax highlight due to it's obfuscated syntax.\r\n\r\nNow you can edit ERM in Vim, bear in mind that ERM script must always be saved in Unix format even in MacOS and Windows. If anything does go wrong, open the script in ERM_S and save it.\r\n\r\nEnjoy!","install_details":"copy the file into your ~\/vimfiles\/syntax\/erm.vim for windows, or ~\/.vim\/syntax\/erm.vim for other OS.\r\n\r\nthen edit $VIMRUNTIME\/filetype.vim to add the following:\r\n\" Event Related Model\r\nau BufNewFile,BufRead *.erm\t\t\tsetf erm\r\n\r\nif you use modeline then you don't need to edit filetype.vim\r\n\r\nNote: the file was saved in dos format by mistake, if you use it on Linux you must convert the erm.vim into Unix format, though I expect most users will use erm on Windows.\r\n","5":"copy the file into your ~\/vimfiles\/syntax\/erm.vim for windows, or ~\/.vim\/syntax\/erm.vim for other OS.\r\n\r\nthen edit $VIMRUNTIME\/filetype.vim to add the following:\r\n\" Event Related Model\r\nau BufNewFile,BufRead *.erm\t\t\tsetf erm\r\n\r\nif you use modeline then you don't need to edit filetype.vim\r\n\r\nNote: the file was saved in dos format by mistake, if you use it on Linux you must convert the erm.vim into Unix format, though I expect most users will use erm on Windows.\r\n","first_name":"Pan","6":"Pan","last_name":"Shizhu","7":"Shizhu","releases":[{"0":"1792","vim_version":"6.0","1":"6.0","script_version":"0.7","2":"0.7","version_comment":"Initial upload","3":"Initial upload","package":"erm.vim","4":"erm.vim","src_id":"6713","5":"6713","creation_date":"1170487627","6":"1170487627"}]},"1791":{"script_id":"1791","0":"1791","script_name":"tagscan","1":"tagscan","script_type":"utility","2":"utility","summary":"Tag your file for better search requisite place","3":"Tag your file for better search requisite place","description":"[ This script is obsolete. Please use http:\/\/www.vim.org\/scripts\/script.php?script_id=2507 instead ]\r\n\r\nIf you've file with lines\r\n\r\nheader: creation of form with scroll\r\n     tags: create, gui\r\n --- some info\r\n--- some .sco links\r\n --- some info\r\nheader: creation of speed buttons\r\n     tags: gui, create\r\n --- some info\r\n --- some info\r\n\/\/ tags: todo, bug\r\nvoid function_bug( bug_height )\r\n{\r\n}\r\n\r\nYou can type command\r\n:ScanTags\r\n  and do fast find by tags lines you want\r\n\r\n:Select   command do add tag to list ( <CR> key )\r\n:Deselect command remove last tag from list ( <BS> key )\r\n\r\nany letter keys to quick move to tag ( s o r t -  show only tags than consist \"sort\" as their part)\r\n<Tab> key to move to next visible tag\r\n\r\nScript written for easy search information in  files (.sco files for example http:\/\/www.vim.org\/scripts\/script.php?script_id=1638 )\r\n","4":"[ This script is obsolete. Please use http:\/\/www.vim.org\/scripts\/script.php?script_id=2507 instead ]\r\n\r\nIf you've file with lines\r\n\r\nheader: creation of form with scroll\r\n     tags: create, gui\r\n --- some info\r\n--- some .sco links\r\n --- some info\r\nheader: creation of speed buttons\r\n     tags: gui, create\r\n --- some info\r\n --- some info\r\n\/\/ tags: todo, bug\r\nvoid function_bug( bug_height )\r\n{\r\n}\r\n\r\nYou can type command\r\n:ScanTags\r\n  and do fast find by tags lines you want\r\n\r\n:Select   command do add tag to list ( <CR> key )\r\n:Deselect command remove last tag from list ( <BS> key )\r\n\r\nany letter keys to quick move to tag ( s o r t -  show only tags than consist \"sort\" as their part)\r\n<Tab> key to move to next visible tag\r\n\r\nScript written for easy search information in  files (.sco files for example http:\/\/www.vim.org\/scripts\/script.php?script_id=1638 )\r\n","install_details":"put tagscan.vim in plugin folder","5":"put tagscan.vim in plugin folder","first_name":"Mykola","6":"Mykola","last_name":"Golubyev","7":"Golubyev","releases":[{"0":"1791","vim_version":"7.0","1":"7.0","script_version":"2.5","2":"2.5","version_comment":"More friendly tag select mechanism","3":"More friendly tag select mechanism","package":"tagscan.vim","4":"tagscan.vim","src_id":"6728","5":"6728","creation_date":"1170822193","6":"1170822193"},{"0":"1791","vim_version":"7.0","1":"7.0","script_version":"2.0","2":"2.0","version_comment":"Now you haven't to manually select tag. Just type first letters and then <CR>\r\nUse <Esc> to start quick tag search from start.\r\nAdded header support. When you've same tags for different file places, specify header for them header: header_text","3":"Now you haven't to manually select tag. Just type first letters and then <CR>\r\nUse <Esc> to start quick tag search from start.\r\nAdded header support. When you've same tags for different file places, specify header for them header: header_text","package":"tagscan.vim","4":"tagscan.vim","src_id":"6721","5":"6721","creation_date":"1170656683","6":"1170656683"},{"0":"1791","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"tagscan.vim","4":"tagscan.vim","src_id":"6706","5":"6706","creation_date":"1170395263","6":"1170395263"}]},"1790":{"script_id":"1790","0":"1790","script_name":"Audacious Control","1":"Audacious Control","script_type":"utility","2":"utility","summary":"A simple plug-in which let you control your Audacious right within Vim","3":"A simple plug-in which let you control your Audacious right within Vim","description":"You can control your Audacious right within your Vim.\r\n\r\nDisplaying playlist (you can navigate through it and select the song to play),\r\nPlay\/Pause\/Stop Audacious,\r\nJumping forward\/backward in playlist,\r\nTurning on\/off Shuffle play,\r\nTurning on\/off Repeat,\r\nGetting info about the current playing song,\r\nIncreasing\/decreasing volume,\r\nAnd Shutting down Audacious.\r\n\r\nAlso this plugin provides a menu for gVim users.","4":"You can control your Audacious right within your Vim.\r\n\r\nDisplaying playlist (you can navigate through it and select the song to play),\r\nPlay\/Pause\/Stop Audacious,\r\nJumping forward\/backward in playlist,\r\nTurning on\/off Shuffle play,\r\nTurning on\/off Repeat,\r\nGetting info about the current playing song,\r\nIncreasing\/decreasing volume,\r\nAnd Shutting down Audacious.\r\n\r\nAlso this plugin provides a menu for gVim users.","install_details":"Simply put it in ~\/.vim\/plugin","5":"Simply put it in ~\/.vim\/plugin","first_name":"Amir Mohammad","6":"Amir Mohammad","last_name":"Saied","7":"Saied","releases":[{"0":"1790","vim_version":"6.0","1":"6.0","script_version":"0.2.2","2":"0.2.2","version_comment":"BUGFIX: Fixed a typo which caused deletion of the last item in playlist (Thanks to Milad Rastian)","3":"BUGFIX: Fixed a typo which caused deletion of the last item in playlist (Thanks to Milad Rastian)","package":"audaciousctrl.vim","4":"audaciousctrl.vim","src_id":"6702","5":"6702","creation_date":"1170332423","6":"1170332423"}]},"1788":{"script_id":"1788","0":"1788","script_name":"Bexec","1":"Bexec","script_type":"utility","2":"utility","summary":"Execute script in buffer and display output in buffer.","3":"Execute script in buffer and display output in buffer.","description":"The Bexec plugin allows the user to execute the current buffer if it contains a script with a shebang (#!\/path\/to\/interpreter) on the first line or if the default interpreter for the script's type is known by Bexec. The output of the script will be grabbed and displayed in a separate buffer.\r\n\r\nIt can be used to execute, for instance, Shell, PHP, PERL, Python or SQL scripts from within Vim.\r\n\r\nScreenshots can be found at: https:\/\/github.com\/fboender\/bexec\r\n","4":"The Bexec plugin allows the user to execute the current buffer if it contains a script with a shebang (#!\/path\/to\/interpreter) on the first line or if the default interpreter for the script's type is known by Bexec. The output of the script will be grabbed and displayed in a separate buffer.\r\n\r\nIt can be used to execute, for instance, Shell, PHP, PERL, Python or SQL scripts from within Vim.\r\n\r\nScreenshots can be found at: https:\/\/github.com\/fboender\/bexec\r\n","install_details":"Edit bexec-vX.Y.vmb in vim and run:\r\n\r\n:so %","5":"Edit bexec-vX.Y.vmb in vim and run:\r\n\r\n:so %","first_name":"Ferry","6":"Ferry","last_name":"Boender","7":"Boender","releases":[{"0":"1788","vim_version":"7.0","1":"7.0","script_version":"0.10","2":"0.10","version_comment":"Added a 'bexec_splitsize' setting that controls the size of the output buffer.","3":"Added a 'bexec_splitsize' setting that controls the size of the output buffer.","package":"bexec-v0.10.vmb","4":"bexec-v0.10.vmb","src_id":"24888","5":"24888","creation_date":"1483943083","6":"1483943083"},{"0":"1788","vim_version":"7.0","1":"7.0","script_version":"0.9","2":"0.9","version_comment":"Bexec is now auto-loaded on demand; reducing Vim startup times.","3":"Bexec is now auto-loaded on demand; reducing Vim startup times.","package":"bexec-v0.9.vmb","4":"bexec-v0.9.vmb","src_id":"23774","5":"23774","creation_date":"1449304930","6":"1449304930"},{"0":"1788","vim_version":"7.0","1":"7.0","script_version":"0.8","2":"0.8","version_comment":"Honor splitbelow and splitright vim setting.","3":"Honor splitbelow and splitright vim setting.","package":"bexec-v0.8.vmb","4":"bexec-v0.8.vmb","src_id":"22544","5":"22544","creation_date":"1413722943","6":"1413722943"},{"0":"1788","vim_version":"7.0","1":"7.0","script_version":"0.7","2":"0.7","version_comment":"Live auto preview of buffer execution. See http:\/\/f.cl.ly\/items\/331H3h1m1V2e1s2t3R3a\/bexec_live.gif","3":"Live auto preview of buffer execution. See http:\/\/f.cl.ly\/items\/331H3h1m1V2e1s2t3R3a\/bexec_live.gif","package":"bexec-v0.7.vmb","4":"bexec-v0.7.vmb","src_id":"22349","5":"22349","creation_date":"1408454307","6":"1408454307"},{"0":"1788","vim_version":"7.0","1":"7.0","script_version":"0.6","2":"0.6","version_comment":"Support \/ fix for Windows (by mohd-akram).","3":"Support \/ fix for Windows (by mohd-akram).","package":"bexec-v0.6.vmb","4":"bexec-v0.6.vmb","src_id":"21694","5":"21694","creation_date":"1396257779","6":"1396257779"},{"0":"1788","vim_version":"7.0","1":"7.0","script_version":"0.5","2":"0.5","version_comment":"Bugfix in argument handling in Visual mode execution. Range is appended to argument-string, which is wrong. (Mostly affected Zsh users).\r\n\r\nLeader-mappings <leader>bx and <leader>bc are now mapped regardless of previously existing (custom) mappings to Bexec() functions.","3":"Bugfix in argument handling in Visual mode execution. Range is appended to argument-string, which is wrong. (Mostly affected Zsh users).\r\n\r\nLeader-mappings <leader>bx and <leader>bc are now mapped regardless of previously existing (custom) mappings to Bexec() functions.","package":"bexec-0.5.vba","4":"bexec-0.5.vba","src_id":"14953","5":"14953","creation_date":"1296829614","6":"1296829614"},{"0":"1788","vim_version":"7.0","1":"7.0","script_version":"0.3","2":"0.3","version_comment":"A bexec_interpreter setting was added which overrides all other ways of finding an interpreter. A (requested) function BexecCloseOut() was added which closes the output window.\r\n","3":"A bexec_interpreter setting was added which overrides all other ways of finding an interpreter. A (requested) function BexecCloseOut() was added which closes the output window.\r\n","package":"bexec-v0.3.vba","4":"bexec-v0.3.vba","src_id":"6727","5":"6727","creation_date":"1170820387","6":"1170820387"},{"0":"1788","vim_version":"7.0","1":"7.0","script_version":"0.2","2":"0.2","version_comment":"The <F5> mapping has been removed in favour of <leader>bx. Custom filters where added (see :help bexec-customizing) and it is now possible to add your own known interpreters and custom filters from your .vimrc.\r\n","3":"The <F5> mapping has been removed in favour of <leader>bx. Custom filters where added (see :help bexec-customizing) and it is now possible to add your own known interpreters and custom filters from your .vimrc.\r\n","package":"bexec-v0.2.vba","4":"bexec-v0.2.vba","src_id":"6694","5":"6694","creation_date":"1170211124","6":"1170211124"},{"0":"1788","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"bexec-v0.1.vba","4":"bexec-v0.1.vba","src_id":"6691","5":"6691","creation_date":"1170119489","6":"1170119489"}]},"1787":{"script_id":"1787","0":"1787","script_name":"wikipedia.vim","1":"wikipedia.vim","script_type":"syntax","2":"syntax","summary":"Syntax highlighting for MediaWiki articles","3":"Syntax highlighting for MediaWiki articles","description":"This file is for people who use external editors to work on articles on Wikipedia and other MediaWiki sites.  Please note that I didn't write this -- it was downloaded from http:\/\/en.wikipedia.org\/wiki\/Wikipedia%3AText_editor_support#Vim and may well be more up-to-date there.  If the version here is out of date contact me and I'll upload the improved version.\r\n\r\nVersion 1 of this script also contains a few settings to better deal with the fact that MediaWiki articles only contain newlines between paragraphs, you may prefer to remove those and put them in ~\/.vim\/ftplugin\/Wikipedia.vim.  In version 2 these have been moved to a separate file.","4":"This file is for people who use external editors to work on articles on Wikipedia and other MediaWiki sites.  Please note that I didn't write this -- it was downloaded from http:\/\/en.wikipedia.org\/wiki\/Wikipedia%3AText_editor_support#Vim and may well be more up-to-date there.  If the version here is out of date contact me and I'll upload the improved version.\r\n\r\nVersion 1 of this script also contains a few settings to better deal with the fact that MediaWiki articles only contain newlines between paragraphs, you may prefer to remove those and put them in ~\/.vim\/ftplugin\/Wikipedia.vim.  In version 2 these have been moved to a separate file.","install_details":"augroup filetypedetect\r\nau BufNewFile,BufRead *.wiki setf Wikipedia\r\naugroup END","5":"augroup filetypedetect\r\nau BufNewFile,BufRead *.wiki setf Wikipedia\r\naugroup END","first_name":"Matt","6":"Matt","last_name":"C","7":"C","releases":[{"0":"1787","vim_version":"7.0","1":"7.0","script_version":"3","2":"3","version_comment":"Copied directly from http:\/\/en.wikipedia.org\/wiki\/Wikipedia:Text_editor_support#Vim\r\n\r\nSee that page for further options for editing long paragraphs written without line breaks.","3":"Copied directly from http:\/\/en.wikipedia.org\/wiki\/Wikipedia:Text_editor_support#Vim\r\n\r\nSee that page for further options for editing long paragraphs written without line breaks.","package":"Wikipedia.tar.gz","4":"Wikipedia.tar.gz","src_id":"16886","5":"16886","creation_date":"1321499009","6":"1321499009"},{"0":"1787","vim_version":"6.0","1":"6.0","script_version":"2","2":"2","version_comment":"Again, I didn't write this, I'm just uploading a new version from http:\/\/en.wikipedia.org\/wiki\/Wikipedia%3AText_editor_support#Vim so it will be distributed more widely.\r\nFull credit for this upgrade goes to Ian Tegebo, username yontege on this site, who emailed me updated versions of these files and suggested that I upload them here.\r\n\r\nThis package includes the following files:\r\nfiletype.vim\r\nftplugin\/Wikipedia.vim\r\nsyntax\/Wikipedia.vim","3":"Again, I didn't write this, I'm just uploading a new version from http:\/\/en.wikipedia.org\/wiki\/Wikipedia%3AText_editor_support#Vim so it will be distributed more widely.\r\nFull credit for this upgrade goes to Ian Tegebo, username yontege on this site, who emailed me updated versions of these files and suggested that I upload them here.\r\n\r\nThis package includes the following files:\r\nfiletype.vim\r\nftplugin\/Wikipedia.vim\r\nsyntax\/Wikipedia.vim","package":"Wikipedia.tar.gz","4":"Wikipedia.tar.gz","src_id":"7538","5":"7538","creation_date":"1187680599","6":"1187680599"},{"0":"1787","vim_version":"6.0","1":"6.0","script_version":"1","2":"1","version_comment":"Initial upload","3":"Initial upload","package":"wikipedia.vim","4":"wikipedia.vim","src_id":"6688","5":"6688","creation_date":"1170056346","6":"1170056346"}]},"1786":{"script_id":"1786","0":"1786","script_name":"hexsearch.vim","1":"hexsearch.vim","script_type":"utility","2":"utility","summary":"search with a hexadecimal string","3":"search with a hexadecimal string","description":"This is a preprocessor to Vim's search command.\r\nIt converts a sequence of hex numbers into a usual search pattern\r\n(one char per hex-code).  Searching is literal.\r\n\r\nExample:\r\n    :HexSearch 56696d 20 72756c657a21\r\nfinds ... you know.\r\n\r\nIf 'fileformat' is unix or mac, there is (almost) no difference to searching\r\nfor a hex string in a hex-editor.\r\n\r\nHere is the \"almost\" case for 'ff=unix':\r\n    :HexSearch 0A\r\nfinds a linebreak at the end of the file, even if there isn't one.\r\n\r\nSee inside script for more details.","4":"This is a preprocessor to Vim's search command.\r\nIt converts a sequence of hex numbers into a usual search pattern\r\n(one char per hex-code).  Searching is literal.\r\n\r\nExample:\r\n    :HexSearch 56696d 20 72756c657a21\r\nfinds ... you know.\r\n\r\nIf 'fileformat' is unix or mac, there is (almost) no difference to searching\r\nfor a hex string in a hex-editor.\r\n\r\nHere is the \"almost\" case for 'ff=unix':\r\n    :HexSearch 0A\r\nfinds a linebreak at the end of the file, even if there isn't one.\r\n\r\nSee inside script for more details.","install_details":":source hexsearch.vim\r\n\r\nwhen needed or put script in plugin folder","5":":source hexsearch.vim\r\n\r\nwhen needed or put script in plugin folder","first_name":"Andy","6":"Andy","last_name":"Wokula","7":"Wokula","releases":[{"0":"1786","vim_version":"6.0","1":"6.0","script_version":"1","2":"1","version_comment":"Initial upload","3":"Initial upload","package":"hexsearch.vim","4":"hexsearch.vim","src_id":"6686","5":"6686","creation_date":"1170051111","6":"1170051111"}]},"1785":{"script_id":"1785","0":"1785","script_name":"javacomplete","1":"javacomplete","script_type":"ftplugin","2":"ftplugin","summary":"Omni Completion for JAVA","3":"Omni Completion for JAVA","description":"This is javacomplete, an omni-completion script of JAVA language for vim 7.\r\n\r\nIt includes javacomplete.vim, java_parser.vim, Reflection.java, and \r\njavacomplete.txt\r\n\r\nFeatures:\r\n- List members of a class, including (static) fields, (static) methods and ctors.\r\n- List classes or subpackages of a package.\r\n- Provide parameters information of a method, list all overload methods.\r\n- Complete an incomplete word.\r\n- Provide a complete JAVA parser written in Vim script language.\r\n- Use the JVM to obtain most information.\r\n- Use the embedded parser to obtain the class information from source files.\r\n- Tags generated by ctags can also be used.\r\n- JSP is supported, Builtin objects such as request, session can be recognized.\r\n  The classes and jar files in the WEB-INF will be appended automatically to classpath.\r\n\r\n\r\nRequirements:\r\nIt works on all the platforms where\r\n- Vim version 7.0 and above\r\n- JDK version 1.1 and above\r\nexisted \r\n\r\nInput context:\r\nIt recognize nearly all kinds of Primary Expressions (see langspec-3.0)\r\nexcept for \"Primary.new Indentifier\". Casting conversion is also supported.\r\nSamples of input contexts are as following:\t('|' indicates cursor)\r\n    (1). after '.', list members of a class or a package\r\n    - package.|         subpackages and classes of a package\r\n    - Type.|                static members of the 'Type' class and \"class\"\r\n    - var.| or field.|     members of a variable or a field\r\n    - method().|         members of result of method()\r\n    - this.|                   members of the current class\r\n    - ClassName.this.|  members of the qualified class\r\n    - super.|               members of the super class\r\n    - array.|                members of an array object\r\n    - array[i].|             array access, return members of the element of array\r\n    - \"String\".|            String literal, return members of java.lang.String\r\n    - int.| or void.|       primitive type or pseudo-type, return \"class\"\r\n    - int[].|                   array type, return members of a array type and \"class\"\r\n    - java.lang.String[].|\r\n    - new int[].|           members of the new array instance\r\n    - new java.lang.String[i=1][].|\r\n    - new Type().|      members of the new class instance \r\n    - Type.class.|      class literal, return members of java.lang.Class\r\n    - void.class.| or int.class.|\r\n    - ((Type)var).|         cast var as Type, return members of Type.\r\n    - (var.method()).|   same with \"var.|\"\r\n    - (new Class()).|    same with \"new Class().|\"\r\n\r\n   (2). after '(', list matching methods with parameters information.\r\n    - method(|)                 methods matched\r\n    - var.method(|)           methods matched\r\n    - new ClassName(|)  constructors matched\r\n    - this(|)                        constructors of current class matched\r\n    - super(|)                     constructors of super class matched\r\n    Any place between '(' and ')' will be supported soon.\r\n    Help information of javadoc is not supported yet.\r\n\r\n   (3). after an incomplete word, list all the matched beginning with it.\r\n    - var.ab|          subset of members of var beginning with `ab`\r\n    - ab|                list of all maybes\r\n\r\n   (4). import statement\r\n    - \" import         java.util.|\"\r\n    - \" import         java.ut|\"\r\n    - \" import         ja|\"\r\n    - \" import         java.lang.Character.|\"        e.g. \"Subset\"\r\n    - \" import static java.lang.Math.|\"        e.g. \"PI, abs\"\r\n\r\n   (5). package declaration\r\n    - \" package         com.|\"\r\n\r\n   The above are in simple expression.\r\n   (6). after compound expression:\r\n    - PrimaryExpr.var.|\r\n    - PrimaryExpr.method().|\r\n    - PrimaryExpr.method(|)\r\n    - PrimaryExpr.var.ab|\r\n    e.g.\r\n    - \"java.lang        . System.in .|\"\r\n    - \"java.lang.System.getenv().|\"\r\n    - \"int.class.toString().|\"\r\n    - \"list.toArray().|\"\r\n    - \"new ZipFile(path).|\"\r\n    - \"new ZipFile(path).entries().|\"\r\n\r\n   (7). Nested expression:\r\n    - \"System.out.println( str.| )\"\r\n    - \"System.out.println(str.charAt(| )\"\r\n    - \"for (int i = 0; i < str.|; i++)\"\r\n    - \"for ( Object o : a.getCollect| )\"\r\n\r\n\r\nLimitations:\r\nThe embedded parser works a bit slower than expected.\r\n\r\nTODO:\r\n-  Improve performance of the embedded parser. Incremental parser.\r\n-  Add quick information using balloonexpr, ballooneval, balloondelay.\r\n-  Add javadoc\r\n-  Give a hint for class name conflict in different packages.\r\n-  Support parameter information for template\r\n-  Make it faster and more robust.\r\n\r\nScreenshots:\r\nmembers of a package, http:\/\/blog.chinaunix.net\/photo\/44758_070917101010.jpg\r\nmembers of a type, http:\/\/blog.chinaunix.net\/photo\/44758_070917101048.jpg\r\nlocal variable, http:\/\/blog.chinaunix.net\/photo\/44758_070917101134.jpg\r\nspecial reference super, http:\/\/blog.chinaunix.net\/photo\/44758_070917101158.jpg\r\nobject of method result,  http:\/\/blog.chinaunix.net\/photo\/44758_070917101236.jpg\r\n\r\nFeedBack:\r\nAny problem, bug or suggest are welcome to send to fangread@yahoo.com.cn\r\n\r\nBTW, If you want to get more functions on writting java program besides code completion,\r\nyou can try VJDE. http:\/\/www.vim.org\/scripts\/script.php?script_id=1213","4":"This is javacomplete, an omni-completion script of JAVA language for vim 7.\r\n\r\nIt includes javacomplete.vim, java_parser.vim, Reflection.java, and \r\njavacomplete.txt\r\n\r\nFeatures:\r\n- List members of a class, including (static) fields, (static) methods and ctors.\r\n- List classes or subpackages of a package.\r\n- Provide parameters information of a method, list all overload methods.\r\n- Complete an incomplete word.\r\n- Provide a complete JAVA parser written in Vim script language.\r\n- Use the JVM to obtain most information.\r\n- Use the embedded parser to obtain the class information from source files.\r\n- Tags generated by ctags can also be used.\r\n- JSP is supported, Builtin objects such as request, session can be recognized.\r\n  The classes and jar files in the WEB-INF will be appended automatically to classpath.\r\n\r\n\r\nRequirements:\r\nIt works on all the platforms where\r\n- Vim version 7.0 and above\r\n- JDK version 1.1 and above\r\nexisted \r\n\r\nInput context:\r\nIt recognize nearly all kinds of Primary Expressions (see langspec-3.0)\r\nexcept for \"Primary.new Indentifier\". Casting conversion is also supported.\r\nSamples of input contexts are as following:\t('|' indicates cursor)\r\n    (1). after '.', list members of a class or a package\r\n    - package.|         subpackages and classes of a package\r\n    - Type.|                static members of the 'Type' class and \"class\"\r\n    - var.| or field.|     members of a variable or a field\r\n    - method().|         members of result of method()\r\n    - this.|                   members of the current class\r\n    - ClassName.this.|  members of the qualified class\r\n    - super.|               members of the super class\r\n    - array.|                members of an array object\r\n    - array[i].|             array access, return members of the element of array\r\n    - \"String\".|            String literal, return members of java.lang.String\r\n    - int.| or void.|       primitive type or pseudo-type, return \"class\"\r\n    - int[].|                   array type, return members of a array type and \"class\"\r\n    - java.lang.String[].|\r\n    - new int[].|           members of the new array instance\r\n    - new java.lang.String[i=1][].|\r\n    - new Type().|      members of the new class instance \r\n    - Type.class.|      class literal, return members of java.lang.Class\r\n    - void.class.| or int.class.|\r\n    - ((Type)var).|         cast var as Type, return members of Type.\r\n    - (var.method()).|   same with \"var.|\"\r\n    - (new Class()).|    same with \"new Class().|\"\r\n\r\n   (2). after '(', list matching methods with parameters information.\r\n    - method(|)                 methods matched\r\n    - var.method(|)           methods matched\r\n    - new ClassName(|)  constructors matched\r\n    - this(|)                        constructors of current class matched\r\n    - super(|)                     constructors of super class matched\r\n    Any place between '(' and ')' will be supported soon.\r\n    Help information of javadoc is not supported yet.\r\n\r\n   (3). after an incomplete word, list all the matched beginning with it.\r\n    - var.ab|          subset of members of var beginning with `ab`\r\n    - ab|                list of all maybes\r\n\r\n   (4). import statement\r\n    - \" import         java.util.|\"\r\n    - \" import         java.ut|\"\r\n    - \" import         ja|\"\r\n    - \" import         java.lang.Character.|\"        e.g. \"Subset\"\r\n    - \" import static java.lang.Math.|\"        e.g. \"PI, abs\"\r\n\r\n   (5). package declaration\r\n    - \" package         com.|\"\r\n\r\n   The above are in simple expression.\r\n   (6). after compound expression:\r\n    - PrimaryExpr.var.|\r\n    - PrimaryExpr.method().|\r\n    - PrimaryExpr.method(|)\r\n    - PrimaryExpr.var.ab|\r\n    e.g.\r\n    - \"java.lang        . System.in .|\"\r\n    - \"java.lang.System.getenv().|\"\r\n    - \"int.class.toString().|\"\r\n    - \"list.toArray().|\"\r\n    - \"new ZipFile(path).|\"\r\n    - \"new ZipFile(path).entries().|\"\r\n\r\n   (7). Nested expression:\r\n    - \"System.out.println( str.| )\"\r\n    - \"System.out.println(str.charAt(| )\"\r\n    - \"for (int i = 0; i < str.|; i++)\"\r\n    - \"for ( Object o : a.getCollect| )\"\r\n\r\n\r\nLimitations:\r\nThe embedded parser works a bit slower than expected.\r\n\r\nTODO:\r\n-  Improve performance of the embedded parser. Incremental parser.\r\n-  Add quick information using balloonexpr, ballooneval, balloondelay.\r\n-  Add javadoc\r\n-  Give a hint for class name conflict in different packages.\r\n-  Support parameter information for template\r\n-  Make it faster and more robust.\r\n\r\nScreenshots:\r\nmembers of a package, http:\/\/blog.chinaunix.net\/photo\/44758_070917101010.jpg\r\nmembers of a type, http:\/\/blog.chinaunix.net\/photo\/44758_070917101048.jpg\r\nlocal variable, http:\/\/blog.chinaunix.net\/photo\/44758_070917101134.jpg\r\nspecial reference super, http:\/\/blog.chinaunix.net\/photo\/44758_070917101158.jpg\r\nobject of method result,  http:\/\/blog.chinaunix.net\/photo\/44758_070917101236.jpg\r\n\r\nFeedBack:\r\nAny problem, bug or suggest are welcome to send to fangread@yahoo.com.cn\r\n\r\nBTW, If you want to get more functions on writting java program besides code completion,\r\nyou can try VJDE. http:\/\/www.vim.org\/scripts\/script.php?script_id=1213","install_details":"1. Unzip javacomplete.zip to a directory of 'runtimepath', e.g.\r\n$HOME\/.vim (unix\/linux), $VIM\/vimfiles (windows).\r\n\t> unzip javacomplete.zip -d ~\/.vim\r\n\r\n    To update Vim help tags, run vim and run command: \r\n\t:helptags $HOME\/.vim\/doc\r\n    or\r\n\t:helptags $VIM\/vimfiles\/doc\r\n\r\nNOTE: javacomplete.vim, java_parser.vim and Reflection.java should be in one\r\nautoload directory of 'runtimepath'.\r\njavacomplete.txt should be in one doc directory of 'runtimepath'.\r\n\r\n2. Set 'omnifunc' option. e.g.\r\n        :setlocal omnifunc=javacomplete#Complete\r\n  Or, use autocmd: \r\n        :\" Only do this part when compiled with support for autocommands.\r\n        :if has(\"autocmd\")\r\n        :  autocmd Filetype java setlocal omnifunc=javacomplete#Complete\r\n        :endif\r\n  You can add this command to your .vimrc or _vimrc.\r\n\r\n3. Set 'completefunc' option to show parameters information IF YOU LIKE. e.g.\r\n\t:setlocal completefunc=javacomplete#CompleteParamsInfo\r\nYou can map as follows for better display:\r\n\t:inoremap <buffer> <C-X><C-U> <C-X><C-U><C-P>\r\n\t:inoremap <buffer> <C-S-Space> <C-X><C-U><C-P>\r\n\r\n4. Reflection.java will be automatcally compiled and placed to $HOME when you\r\nuse first time. Assure that Reflection.java is in the same directory with\r\njavacomplete.vim to be searched in autoload subdirectory of &rtp. \r\nIf no Reflection.class is generated, check that you have the write permission\r\nin $HOME directory.\r\nIf a previous Reflection.java is not compatible with the new version\r\njavacomplete.vim, please compile Reflection.java manually.\r\n","5":"1. Unzip javacomplete.zip to a directory of 'runtimepath', e.g.\r\n$HOME\/.vim (unix\/linux), $VIM\/vimfiles (windows).\r\n\t> unzip javacomplete.zip -d ~\/.vim\r\n\r\n    To update Vim help tags, run vim and run command: \r\n\t:helptags $HOME\/.vim\/doc\r\n    or\r\n\t:helptags $VIM\/vimfiles\/doc\r\n\r\nNOTE: javacomplete.vim, java_parser.vim and Reflection.java should be in one\r\nautoload directory of 'runtimepath'.\r\njavacomplete.txt should be in one doc directory of 'runtimepath'.\r\n\r\n2. Set 'omnifunc' option. e.g.\r\n        :setlocal omnifunc=javacomplete#Complete\r\n  Or, use autocmd: \r\n        :\" Only do this part when compiled with support for autocommands.\r\n        :if has(\"autocmd\")\r\n        :  autocmd Filetype java setlocal omnifunc=javacomplete#Complete\r\n        :endif\r\n  You can add this command to your .vimrc or _vimrc.\r\n\r\n3. Set 'completefunc' option to show parameters information IF YOU LIKE. e.g.\r\n\t:setlocal completefunc=javacomplete#CompleteParamsInfo\r\nYou can map as follows for better display:\r\n\t:inoremap <buffer> <C-X><C-U> <C-X><C-U><C-P>\r\n\t:inoremap <buffer> <C-S-Space> <C-X><C-U><C-P>\r\n\r\n4. Reflection.java will be automatcally compiled and placed to $HOME when you\r\nuse first time. Assure that Reflection.java is in the same directory with\r\njavacomplete.vim to be searched in autoload subdirectory of &rtp. \r\nIf no Reflection.class is generated, check that you have the write permission\r\nin $HOME directory.\r\nIf a previous Reflection.java is not compatible with the new version\r\njavacomplete.vim, please compile Reflection.java manually.\r\n","first_name":"fang","6":"fang","last_name":"cheng","7":"cheng","releases":[{"0":"1785","vim_version":"7.0","1":"7.0","script_version":"0.77.1.2","2":"0.77.1.2","version_comment":"Fixed the bug caused by that globpath() (vim version < 7.2) does not support the 3rd parameter.\r\nThanks to Sam Lidder's patch.","3":"Fixed the bug caused by that globpath() (vim version < 7.2) does not support the 3rd parameter.\r\nThanks to Sam Lidder's patch.","package":"javacomplete0.77.1.2.zip","4":"javacomplete0.77.1.2.zip","src_id":"14914","5":"14914","creation_date":"1296394489","6":"1296394489"},{"0":"1785","vim_version":"7.0","1":"7.0","script_version":"0.77.1.1","2":"0.77.1.1","version_comment":"Fixed to ignore the 'suffixes' and 'wildignore' options.\r\nReflection.class can not be found if :set wildignore=*.class","3":"Fixed to ignore the 'suffixes' and 'wildignore' options.\r\nReflection.class can not be found if :set wildignore=*.class","package":"javacomplete.zip","4":"javacomplete.zip","src_id":"14244","5":"14244","creation_date":"1289567667","6":"1289567667"},{"0":"1785","vim_version":"7.0","1":"7.0","script_version":"0.77.1","2":"0.77.1","version_comment":"+ Supported showing method parameters information in any place between parenthesises.","3":"+ Supported showing method parameters information in any place between parenthesises.","package":"javacomplete.zip","4":"javacomplete.zip","src_id":"7716","5":"7716","creation_date":"1190753100","6":"1190753100"},{"0":"1785","vim_version":"7.0","1":"7.0","script_version":"0.77","2":"0.77","version_comment":"+ Supported new contexts \"jav|\", \"var|\", just after an incomplete word.\r\n+ Supported accessible static imported members, add new context \"abs(|)\".\r\n+ Supported accessible inherited members.\r\n- [Reflection.java]Improved getting paths of all system jar files for different JDKs in different platforms.\r\n- Rewrote some core functions.","3":"+ Supported new contexts \"jav|\", \"var|\", just after an incomplete word.\r\n+ Supported accessible static imported members, add new context \"abs(|)\".\r\n+ Supported accessible inherited members.\r\n- [Reflection.java]Improved getting paths of all system jar files for different JDKs in different platforms.\r\n- Rewrote some core functions.","package":"javacomplete.zip","4":"javacomplete.zip","src_id":"7692","5":"7692","creation_date":"1190152425","6":"1190152425"},{"0":"1785","vim_version":"6.0","1":"6.0","script_version":"0.76.8","2":"0.76.8","version_comment":"- Improved support of JSP: appending automatically jar or classpath under WEB-INF.\r\n- Supported local and anonymous classes.\r\n- Improved searching type or symbol name.","3":"- Improved support of JSP: appending automatically jar or classpath under WEB-INF.\r\n- Supported local and anonymous classes.\r\n- Improved searching type or symbol name.","package":"javacomplete.zip","4":"javacomplete.zip","src_id":"7584","5":"7584","creation_date":"1188462441","6":"1188462441"},{"0":"1785","vim_version":"7.0","1":"7.0","script_version":"0.76.7","2":"0.76.7","version_comment":"- Improved process of type arguments of generic type and method parameters.\r\n- Reorganize codes in javacomplete#Complete()\r\n- Fixed case of \"new java.util.zip.ZipFile().|\"","3":"- Improved process of type arguments of generic type and method parameters.\r\n- Reorganize codes in javacomplete#Complete()\r\n- Fixed case of \"new java.util.zip.ZipFile().|\"","package":"javacomplete.zip","4":"javacomplete.zip","src_id":"7573","5":"7573","creation_date":"1188282182","6":"1188282182"},{"0":"1785","vim_version":"7.0","1":"7.0","script_version":"0.76.6","2":"0.76.6","version_comment":"- Improved recognizing methods, ctors, and variable declarators declared in most common form.\r\n- Optimized code and fixed bugs.","3":"- Improved recognizing methods, ctors, and variable declarators declared in most common form.\r\n- Optimized code and fixed bugs.","package":"javacomplete.zip","4":"javacomplete.zip","src_id":"7548","5":"7548","creation_date":"1187856124","6":"1187856124"},{"0":"1785","vim_version":"7.0","1":"7.0","script_version":"0.76.5","2":"0.76.5","version_comment":"- Optimized code: s:modeAndEXPR(), formalParameter(), and others.\r\n- Added quick recognizing fields or methods declared in most common form.\r\n- Fixed bug: \"foo().|\", \"getFoo().foo().|\", \"for (Enumeration entries = ; entries.|; )\".\r\n- Supported input contexts: \"((Object)o).|\", \"((Object)o).getClass().|\", \"new ZipFile(path).|\", \"(new String().)|\".","3":"- Optimized code: s:modeAndEXPR(), formalParameter(), and others.\r\n- Added quick recognizing fields or methods declared in most common form.\r\n- Fixed bug: \"foo().|\", \"getFoo().foo().|\", \"for (Enumeration entries = ; entries.|; )\".\r\n- Supported input contexts: \"((Object)o).|\", \"((Object)o).getClass().|\", \"new ZipFile(path).|\", \"(new String().)|\".","package":"javacomplete.zip","4":"javacomplete.zip","src_id":"7540","5":"7540","creation_date":"1187683911","6":"1187683911"},{"0":"1785","vim_version":"7.0","1":"7.0","script_version":"0.76.4.1","2":"0.76.4.1","version_comment":"- Made a major improvement of Reflection. REMEMBER to DELETE the old Reflection.class.\r\n- Support accessible nested classes from reflection.\r\n- Support import static members and import accessible nested classes.\r\n- Improved input contexts: \"int.class.toString().|\", \"list.toArray().|\".\r\n- Fixed recognition of \"this(|)\", \"method1(|)\"\r\n- Added the 'kind' letter to distinguish between classes and packages.\r\n- Fixed a bug when Reflection.java is in the path which contains space.\r\n- Better support for JSP.","3":"- Made a major improvement of Reflection. REMEMBER to DELETE the old Reflection.class.\r\n- Support accessible nested classes from reflection.\r\n- Support import static members and import accessible nested classes.\r\n- Improved input contexts: \"int.class.toString().|\", \"list.toArray().|\".\r\n- Fixed recognition of \"this(|)\", \"method1(|)\"\r\n- Added the 'kind' letter to distinguish between classes and packages.\r\n- Fixed a bug when Reflection.java is in the path which contains space.\r\n- Better support for JSP.","package":"javacomplete.zip","4":"javacomplete.zip","src_id":"7517","5":"7517","creation_date":"1187338318","6":"1187338318"},{"0":"1785","vim_version":"7.0","1":"7.0","script_version":"0.76.3","2":"0.76.3","version_comment":"- Make an improvement for JSP file.\r\n- Add an option 'searchdecl' set by javacomplete#SetSearchdeclMethod().\r\n- Clear cache when set options affecting classpath.\r\n- Improved DoGetPackageList() and s:GenerateImports().\r\n- Replace codes searching list of string with index().\r\n- Removed the unclear s:tokens and s:modifier_keywords in java_parser.\r\n- Add java_parser#GetSnapshot() and java_parser#Restore().\r\n- Fixed a bug when no top level class defined","3":"- Make an improvement for JSP file.\r\n- Add an option 'searchdecl' set by javacomplete#SetSearchdeclMethod().\r\n- Clear cache when set options affecting classpath.\r\n- Improved DoGetPackageList() and s:GenerateImports().\r\n- Replace codes searching list of string with index().\r\n- Removed the unclear s:tokens and s:modifier_keywords in java_parser.\r\n- Add java_parser#GetSnapshot() and java_parser#Restore().\r\n- Fixed a bug when no top level class defined","package":"javacomplete.zip","4":"javacomplete.zip","src_id":"7484","5":"7484","creation_date":"1186732339","6":"1186732339"},{"0":"1785","vim_version":"7.0","1":"7.0","script_version":"0.76.2","2":"0.76.2","version_comment":"- Add inherited fields and methods to local class.\r\n- Combine members of local packages and loadable packages.\r\n- Add quick recognition of package or import. \r\n- Fix failing to list members of nested class.\r\n- Improved java_parser.\r\n- [Reflection] Return a modifier value as a string because it more than 32bit.","3":"- Add inherited fields and methods to local class.\r\n- Combine members of local packages and loadable packages.\r\n- Add quick recognition of package or import. \r\n- Fix failing to list members of nested class.\r\n- Improved java_parser.\r\n- [Reflection] Return a modifier value as a string because it more than 32bit.","package":"javacomplete.zip","4":"javacomplete.zip","src_id":"7468","5":"7468","creation_date":"1186553374","6":"1186553374"},{"0":"1785","vim_version":"6.0","1":"6.0","script_version":"0.76.1","2":"0.76.1","version_comment":"- Support new language features in JAVA 5 and above.\r\n- The embedded JAVA parser is full-featured now, adding supports for parsing statement, block or expression.\r\n- Java_parser.vim is an autoload script now.\r\n- Support JDK1.1.\r\n- Improve for 'this' or 'super'.\r\n- Support searching toplevel class in current directory, same package or in sourcepath.\r\n- Supports input context: \"StringLiteral\".|, \"int.|\", \"void.|\"\r\n- Add java compiler option, default 'javac'\r\n- Add JVM launcher option, default 'java'\r\n- Automatcally compile Reflection.java and place it to $HOME.\r\n- Easier to install and use.","3":"- Support new language features in JAVA 5 and above.\r\n- The embedded JAVA parser is full-featured now, adding supports for parsing statement, block or expression.\r\n- Java_parser.vim is an autoload script now.\r\n- Support JDK1.1.\r\n- Improve for 'this' or 'super'.\r\n- Support searching toplevel class in current directory, same package or in sourcepath.\r\n- Supports input context: \"StringLiteral\".|, \"int.|\", \"void.|\"\r\n- Add java compiler option, default 'javac'\r\n- Add JVM launcher option, default 'java'\r\n- Automatcally compile Reflection.java and place it to $HOME.\r\n- Easier to install and use.","package":"javacomplete.zip","4":"javacomplete.zip","src_id":"7451","5":"7451","creation_date":"1186276276","6":"1186276276"},{"0":"1785","vim_version":"7.0","1":"7.0","script_version":"0.75beta","2":"0.75beta","version_comment":"\" \tAdd java_parser.vim.\r\n\" \tAdd b:sourcepath option.\r\n\" \tImprove recognition of classes defined in current buffer or in source path.\r\n\" \tSupport generating class information from tags instead of returning list directly.","3":"\" \tAdd java_parser.vim.\r\n\" \tAdd b:sourcepath option.\r\n\" \tImprove recognition of classes defined in current buffer or in source path.\r\n\" \tSupport generating class information from tags instead of returning list directly.","package":"javacomplete.zip","4":"javacomplete.zip","src_id":"6738","5":"6738","creation_date":"1171348769","6":"1171348769"},{"0":"1785","vim_version":"7.0","1":"7.0","script_version":"0.74","2":"0.74","version_comment":"Support jre1.2 (and above).\r\nSupport input context like \"boolean.class.|\"\r\nHandle java primitive types such as 'int'.","3":"Support jre1.2 (and above).\r\nSupport input context like \"boolean.class.|\"\r\nHandle java primitive types such as 'int'.","package":"javacomplete.zip","4":"javacomplete.zip","src_id":"6712","5":"6712","creation_date":"1170484972","6":"1170484972"},{"0":"1785","vim_version":"7.0","1":"7.0","script_version":"0.73","2":"0.73","version_comment":"Fix bug that CLASSPATH not used when b:classpath or g:java_classpath not set.\r\nFix bug that call filter() without making a copy for incomplete.\r\nImprove recognition of declaration of this class","3":"Fix bug that CLASSPATH not used when b:classpath or g:java_classpath not set.\r\nFix bug that call filter() without making a copy for incomplete.\r\nImprove recognition of declaration of this class","package":"javacomplete.zip","4":"javacomplete.zip","src_id":"6701","5":"6701","creation_date":"1170315041","6":"1170315041"},{"0":"1785","vim_version":"7.0","1":"7.0","script_version":"0.72","2":"0.72","version_comment":"Fix bugs in nested expression:\r\n\"System.out.println( str.| )\"\r\n\"System.out.println(str.charAt(| )\"\r\n\"for (int i = 0; i < str.|; i++)\"","3":"Fix bugs in nested expression:\r\n\"System.out.println( str.| )\"\r\n\"System.out.println(str.charAt(| )\"\r\n\"for (int i = 0; i < str.|; i++)\"","package":"javacomplete.zip","4":"javacomplete.zip","src_id":"6695","5":"6695","creation_date":"1170216225","6":"1170216225"},{"0":"1785","vim_version":"7.0","1":"7.0","script_version":"0.71","2":"0.71","version_comment":"Initial upload","3":"Initial upload","package":"javacomplete.zip","4":"javacomplete.zip","src_id":"6677","5":"6677","creation_date":"1169963835","6":"1169963835"}]},"1784":{"script_id":"1784","0":"1784","script_name":"apachestyle","1":"apachestyle","script_type":"indent","2":"indent","summary":"Simple indent for apache config files","3":"Simple indent for apache config files","description":"I could not find an indentation file for Apache configuration files, so I wrote this based on someone's xml indentation file. It's very simple and basic.","4":"I could not find an indentation file for Apache configuration files, so I wrote this based on someone's xml indentation file. It's very simple and basic.","install_details":"Drop in with other indent files.","5":"Drop in with other indent files.","first_name":"Satya","6":"Satya","last_name":"P","7":"P","releases":[{"0":"1784","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Changed my name","3":"Changed my name","package":"apachestyle.vim","4":"apachestyle.vim","src_id":"6675","5":"6675","creation_date":"1169905074","6":"1169905074"}]},"1783":{"script_id":"1783","0":"1783","script_name":"cscope wrapper","1":"cscope wrapper","script_type":"utility","2":"utility","summary":"make gvim(WIN32) + cscope(Cygwin) work together","3":"make gvim(WIN32) + cscope(Cygwin) work together","description":"Actually this isn't a script, but a small application. If you are in the same situation as me cswrapper may help.\r\n1. I'm using gvim Win32 version. It works perfectly in my Windows XP.\r\n2. I tried cscope Win32 version, but it always returns 0 lines for any request.\r\n3. I compiled a cscope(ver 15.6) in Cygwin. It works well in its own command window. But gvim freezes when creating a connection to my cscope with 'cs add cscope.out'.\r\nI guess the reason is cscope doesn't flush its output, it causes gvim to hang up when reading from the pipe. Instead of hacking into cscope's source code, I created this wrapper. It acts as a cscope command window, reads requests from gvim, gets the result by executing cscope, then passes the result to gvim. It works well for me till now.\r\nCSWrapper isn't a full function cscope. It only accesses the parameter '-f \/path\/cscope.out' and acts as a wrapper between gvim and cscope. Please use the original cscope.exe to create databases.","4":"Actually this isn't a script, but a small application. If you are in the same situation as me cswrapper may help.\r\n1. I'm using gvim Win32 version. It works perfectly in my Windows XP.\r\n2. I tried cscope Win32 version, but it always returns 0 lines for any request.\r\n3. I compiled a cscope(ver 15.6) in Cygwin. It works well in its own command window. But gvim freezes when creating a connection to my cscope with 'cs add cscope.out'.\r\nI guess the reason is cscope doesn't flush its output, it causes gvim to hang up when reading from the pipe. Instead of hacking into cscope's source code, I created this wrapper. It acts as a cscope command window, reads requests from gvim, gets the result by executing cscope, then passes the result to gvim. It works well for me till now.\r\nCSWrapper isn't a full function cscope. It only accesses the parameter '-f \/path\/cscope.out' and acts as a wrapper between gvim and cscope. Please use the original cscope.exe to create databases.","install_details":"1. Put this program in the same directory as your cscope.exe.\r\n2. Put this line in your _gvimrc, you may need to add the full path:\r\nset csprg=cswrapper.exe\r\n\r\nIt should work now. If it doesn't work, run 'cswrapper -f \/path\/cscope.out' in a command window, then try typing a command, for example '0main', to see what happens.\r\n","5":"1. Put this program in the same directory as your cscope.exe.\r\n2. Put this line in your _gvimrc, you may need to add the full path:\r\nset csprg=cswrapper.exe\r\n\r\nIt should work now. If it doesn't work, run 'cswrapper -f \/path\/cscope.out' in a command window, then try typing a command, for example '0main', to see what happens.\r\n","first_name":"Ausun","6":"Ausun","last_name":"Wang","7":"Wang","releases":[{"0":"1783","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"CSWrapper.zip","4":"CSWrapper.zip","src_id":"6672","5":"6672","creation_date":"1169886524","6":"1169886524"}]},"1782":{"script_id":"1782","0":"1782","script_name":"polycl.vim","1":"polycl.vim","script_type":"syntax","2":"syntax","summary":"Polyhedra CL syntax","3":"Polyhedra CL syntax","description":"CL is the programming language of stored procedures embedded in the Polyhedra database.\r\nFor more information about Polyhedra, see: http:\/\/www.enea.com\/templates\/Extension____259.aspx\r\n\r\nThis script provides syntax highlighting and folding for this language.\r\n\r\nSee also vimscript#1799: Polyhedra configuration syntax","4":"CL is the programming language of stored procedures embedded in the Polyhedra database.\r\nFor more information about Polyhedra, see: http:\/\/www.enea.com\/templates\/Extension____259.aspx\r\n\r\nThis script provides syntax highlighting and folding for this language.\r\n\r\nSee also vimscript#1799: Polyhedra configuration syntax","install_details":"Save into your personnal syntax directory: $HOME\/{.vim|vimfiles}\/syntax ({Unix|Windows}).\r\n\r\nTo manually colorize a file:\r\n  :syntax on\r\n  :filetype on\r\n  :set filetype=polycl\r\n\r\nTo assign CL syntax to a particular file, put this line at the beginning or end of your code:\r\n  -- vim: set filetype=polycl :\r\n\r\nTo assign CL syntax to files *.cl, add this to your ~\/{.vim|vimfiles}\/filetype.vim:\r\n  augroup filetypedetect\r\n    au! BufNewFile,BufRead *.cl setf polycl\r\n  augroup END\r\n\r\nSee also the built-in help in Vim:\r\n    :help 'filetype'\r\n    :help 'modeline'\r\n    :help filetype-plugin\r\n    :help mysyntaxfile\r\n","5":"Save into your personnal syntax directory: $HOME\/{.vim|vimfiles}\/syntax ({Unix|Windows}).\r\n\r\nTo manually colorize a file:\r\n  :syntax on\r\n  :filetype on\r\n  :set filetype=polycl\r\n\r\nTo assign CL syntax to a particular file, put this line at the beginning or end of your code:\r\n  -- vim: set filetype=polycl :\r\n\r\nTo assign CL syntax to files *.cl, add this to your ~\/{.vim|vimfiles}\/filetype.vim:\r\n  augroup filetypedetect\r\n    au! BufNewFile,BufRead *.cl setf polycl\r\n  augroup END\r\n\r\nSee also the built-in help in Vim:\r\n    :help 'filetype'\r\n    :help 'modeline'\r\n    :help filetype-plugin\r\n    :help mysyntaxfile\r\n","first_name":"Olivier","6":"Olivier","last_name":"Mengu\u00c3\u00a9","7":"Mengu\u00c3\u00a9","releases":[{"0":"1782","vim_version":"6.0","1":"6.0","script_version":"0.9.1","2":"0.9.1","version_comment":"Major fixes (typos).\r\nFixed string escapes.\r\nStarted highlighting of operators and split of reserved word in multiple classes.","3":"Major fixes (typos).\r\nFixed string escapes.\r\nStarted highlighting of operators and split of reserved word in multiple classes.","package":"polycl.vim","4":"polycl.vim","src_id":"6746","5":"6746","creation_date":"1171556187","6":"1171556187"},{"0":"1782","vim_version":"6.0","1":"6.0","script_version":"0.9","2":"0.9","version_comment":"Initial upload","3":"Initial upload","package":"polycl.vim","4":"polycl.vim","src_id":"6671","5":"6671","creation_date":"1169881560","6":"1169881560"}]},"1781":{"script_id":"1781","0":"1781","script_name":"mlint.vim","1":"mlint.vim","script_type":"ftplugin","2":"ftplugin","summary":"Matlab code checker (mlint) compiler file","3":"Matlab code checker (mlint) compiler file","description":"This is the compiler file for the Matlab code checker - mlint. I've tested this with Matlab R2006a and vim 7.0, but this should work with other versions too.\r\n\r\nMatlab's editor automatically checks the code you type in it for warnings and errors. To do this in vim, install this script, and type :make whenever you want to check your code. There is a button for this in gvim. Note that you need to have Matlab's bin directory in your system path. \r\n\r\nmlint's messages are of 3 types :\r\nType 1: Suggestions and simple warnings\r\nType 2: Warnings about performance penalties\r\nType 3: Errors\r\nThe type number is displayed next to the column number in the error window. Use :copen to open the error window, and :cn and :cp  (or Alt-n and Alt-p) to go to the next and previous message respectively.","4":"This is the compiler file for the Matlab code checker - mlint. I've tested this with Matlab R2006a and vim 7.0, but this should work with other versions too.\r\n\r\nMatlab's editor automatically checks the code you type in it for warnings and errors. To do this in vim, install this script, and type :make whenever you want to check your code. There is a button for this in gvim. Note that you need to have Matlab's bin directory in your system path. \r\n\r\nmlint's messages are of 3 types :\r\nType 1: Suggestions and simple warnings\r\nType 2: Warnings about performance penalties\r\nType 3: Errors\r\nThe type number is displayed next to the column number in the error window. Use :copen to open the error window, and :cn and :cp  (or Alt-n and Alt-p) to go to the next and previous message respectively.","install_details":"Copy mlint.vim to your $HOME\/vimfiles\/compiler\/ directory.  Add this to your vimrc :\r\n\r\nautocmd BufEnter *.m    compiler mlint\r\nautocmd BufEnter *.m    map <M-n> :cnext<CR>\r\nautocmd BufEnter *.m    map <M-p> :cprevious<CR>\r\n\r\nautocmd BufLeave *.m    unmap <M-n>\r\nautocmd BufLeave *.m    unmap <M-p>\r\n\r\nRestart vim","5":"Copy mlint.vim to your $HOME\/vimfiles\/compiler\/ directory.  Add this to your vimrc :\r\n\r\nautocmd BufEnter *.m    compiler mlint\r\nautocmd BufEnter *.m    map <M-n> :cnext<CR>\r\nautocmd BufEnter *.m    map <M-p> :cprevious<CR>\r\n\r\nautocmd BufLeave *.m    unmap <M-n>\r\nautocmd BufLeave *.m    unmap <M-p>\r\n\r\nRestart vim","first_name":"Sameer","6":"Sameer","last_name":"Sheorey","7":"Sheorey","releases":[{"0":"1781","vim_version":"5.7","1":"5.7","script_version":"20070126","2":"20070126","version_comment":"Initial upload","3":"Initial upload","package":"mlint.vim","4":"mlint.vim","src_id":"6668","5":"6668","creation_date":"1169825745","6":"1169825745"}]},"1780":{"script_id":"1780","0":"1780","script_name":"scala.vim","1":"scala.vim","script_type":"color scheme","2":"color scheme","summary":"syntaxic coloration for Scala code","3":"syntaxic coloration for Scala code","description":"This script enables syntaxic coloration of source code written in the Scala programming language (http:\/\/www.scala-lang.org)\r\n\r\nDisclaimer\r\n\r\n- This is an absolutly basic version\r\n- Only keywords and simple constructs like comments are recognized\r\n- It is by far not finished\r\n\r\nKnown bugs\r\n\r\n- automatic indentation does not work properly when using the syntaxic possibilities of scala (for example when omitting the ; after the return value)\r\n- sign before a number is not colored","4":"This script enables syntaxic coloration of source code written in the Scala programming language (http:\/\/www.scala-lang.org)\r\n\r\nDisclaimer\r\n\r\n- This is an absolutly basic version\r\n- Only keywords and simple constructs like comments are recognized\r\n- It is by far not finished\r\n\r\nKnown bugs\r\n\r\n- automatic indentation does not work properly when using the syntaxic possibilities of scala (for example when omitting the ; after the return value)\r\n- sign before a number is not colored","install_details":"","5":"","first_name":"Rapha\u00c3\u00abl","6":"Rapha\u00c3\u00abl","last_name":"Haberer-Proust","7":"Haberer-Proust","releases":[{"0":"1780","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"scala.vim","4":"scala.vim","src_id":"6665","5":"6665","creation_date":"1169809394","6":"1169809394"}]},"1779":{"script_id":"1779","0":"1779","script_name":"tcmdbar.vim","1":"tcmdbar.vim","script_type":"utility","2":"utility","summary":"Script for use with Total Commander's button bar","3":"Script for use with Total Commander's button bar","description":"This script is only for users of Total Commander and Win32 (maybe Win16).\r\n\r\nAfter proper installation:\r\nStart Total Commander, select one or more files, then click the GVim button.\r\nGVim will create an argument list from the selected files so you can edit them.\r\nSounds trivial, but it is not.\r\n\r\nWorks with Ctrl-B (show flattened file list).\r\n\r\n\r\nCustomization for _vimrc (optional)\r\n\r\nOpen files in windows, tab pages or in diff mode:\r\n    :let Tcmdbar_OpenIn = \"Windows\"\r\n    :let Tcmdbar_OpenIn = \"Tabs\"        \" ignored in Vim6\r\n    :let Tcmdbar_OpenIn = \"Diff Mode\"\r\n\r\nValues may be abbreviated to \"win\", \"tab\" and \"diff\".\r\n\r\n\r\nYou will get an error if you want to open too many files.  In this case\r\nVim will only open windows\/tabs for as many files as possible.\r\n\r\n-- Please report errors if the script does not work for you! --\r\n\r\n2007 Sep 17\r\nIf the first argument is always the file list, the plugin actually isn't needed!\r\nYou can define the button this way:\r\n    Command: <path>\\gvim.exe \"+n `=readfile(argv(0))`\"\r\n    Parameters: %L\r\nIn the help:\r\n    :h `=\r\n    :h next_f","4":"This script is only for users of Total Commander and Win32 (maybe Win16).\r\n\r\nAfter proper installation:\r\nStart Total Commander, select one or more files, then click the GVim button.\r\nGVim will create an argument list from the selected files so you can edit them.\r\nSounds trivial, but it is not.\r\n\r\nWorks with Ctrl-B (show flattened file list).\r\n\r\n\r\nCustomization for _vimrc (optional)\r\n\r\nOpen files in windows, tab pages or in diff mode:\r\n    :let Tcmdbar_OpenIn = \"Windows\"\r\n    :let Tcmdbar_OpenIn = \"Tabs\"        \" ignored in Vim6\r\n    :let Tcmdbar_OpenIn = \"Diff Mode\"\r\n\r\nValues may be abbreviated to \"win\", \"tab\" and \"diff\".\r\n\r\n\r\nYou will get an error if you want to open too many files.  In this case\r\nVim will only open windows\/tabs for as many files as possible.\r\n\r\n-- Please report errors if the script does not work for you! --\r\n\r\n2007 Sep 17\r\nIf the first argument is always the file list, the plugin actually isn't needed!\r\nYou can define the button this way:\r\n    Command: <path>\\gvim.exe \"+n `=readfile(argv(0))`\"\r\n    Parameters: %L\r\nIn the help:\r\n    :h `=\r\n    :h next_f","install_details":"1. Put script in any directory where it is _not_ sourced automatically\r\n    for example, ~\\vimfiles is a good choice\r\n2. Create a button for GVim in TC's button bar (see inside script for details)\r\n    Command: <path>\\gvim.exe -S ~\\vimfiles\\tcmdbar.vim\r\n    Parameters: %L dummy\r\n\r\nNotes:\r\n-   The \"dummy\" argument is a required dummy file name, its name is fixed!\r\n    You should not run into problems if this is an existing file.\r\n-   You can also set a variable in the Command Textbox:\r\n    <path>\\gvim.exe +\"let Tcmdbar_OpenIn='Tabs'\" -S ~\\vimfiles\\tcmdbar.vim","5":"1. Put script in any directory where it is _not_ sourced automatically\r\n    for example, ~\\vimfiles is a good choice\r\n2. Create a button for GVim in TC's button bar (see inside script for details)\r\n    Command: <path>\\gvim.exe -S ~\\vimfiles\\tcmdbar.vim\r\n    Parameters: %L dummy\r\n\r\nNotes:\r\n-   The \"dummy\" argument is a required dummy file name, its name is fixed!\r\n    You should not run into problems if this is an existing file.\r\n-   You can also set a variable in the Command Textbox:\r\n    <path>\\gvim.exe +\"let Tcmdbar_OpenIn='Tabs'\" -S ~\\vimfiles\\tcmdbar.vim","first_name":"Andy","6":"Andy","last_name":"Wokula","7":"Wokula","releases":[{"0":"1779","vim_version":"7.0","1":"7.0","script_version":"9","2":"9","version_comment":"fix: make it work with file list from \"Find Files\" dialog + more than one selected \"Search in\" directories + \"Feed to listbox\"\r\nfix: proper file name escaping with fnameescape()\r\nnew preferred name for config variable: \"tcmdbar_open_in\" (old variable names still work)\r\n","3":"fix: make it work with file list from \"Find Files\" dialog + more than one selected \"Search in\" directories + \"Feed to listbox\"\r\nfix: proper file name escaping with fnameescape()\r\nnew preferred name for config variable: \"tcmdbar_open_in\" (old variable names still work)\r\n","package":"tcmdbar.vim","4":"tcmdbar.vim","src_id":"20773","5":"20773","creation_date":"1378752462","6":"1378752462"},{"0":"1779","vim_version":"6.0","1":"6.0","script_version":"8","2":"8","version_comment":"added  :let Tcmdbar_OpenIn='Ask'  to query the user with a dialog; when selecting two files, the dialog contains a \"diff\" button","3":"added  :let Tcmdbar_OpenIn='Ask'  to query the user with a dialog; when selecting two files, the dialog contains a \"diff\" button","package":"tcmdbar.vim","4":"tcmdbar.vim","src_id":"17331","5":"17331","creation_date":"1327786658","6":"1327786658"},{"0":"1779","vim_version":"6.0","1":"6.0","script_version":"7","2":"7","version_comment":"added option to open two files in diff mode","3":"added option to open two files in diff mode","package":"tcmdbar.vim","4":"tcmdbar.vim","src_id":"7439","5":"7439","creation_date":"1186033918","6":"1186033918"},{"0":"1779","vim_version":"6.0","1":"6.0","script_version":"6","2":"6","version_comment":"Added option to open files in windows or tabpages","3":"Added option to open files in windows or tabpages","package":"tcmdbar.vim","4":"tcmdbar.vim","src_id":"6705","5":"6705","creation_date":"1170393050","6":"1170393050"},{"0":"1779","vim_version":"6.0","1":"6.0","script_version":"5","2":"5","version_comment":"Bugfixes: issues with 'gd', order of buffers","3":"Bugfixes: issues with 'gd', order of buffers","package":"tcmdbar.vim","4":"tcmdbar.vim","src_id":"6676","5":"6676","creation_date":"1169953932","6":"1169953932"}]},"1778":{"script_id":"1778","0":"1778","script_name":"Wombat","1":"Wombat","script_type":"color scheme","2":"color scheme","summary":"Dark gray color scheme sharing some similarities with Desert","3":"Dark gray color scheme sharing some similarities with Desert","description":"Dark gray background with easy-on-the-eyes font colors. It shares some similarities with the Desert color scheme.\r\n\r\nA few screens at: http:\/\/dengmao.wordpress.com\/2007\/01\/22\/vim-color-scheme-wombat\/","4":"Dark gray background with easy-on-the-eyes font colors. It shares some similarities with the Desert color scheme.\r\n\r\nA few screens at: http:\/\/dengmao.wordpress.com\/2007\/01\/22\/vim-color-scheme-wombat\/","install_details":"Place in ~\/.vim\/colors and type :colo wombat","5":"Place in ~\/.vim\/colors and type :colo wombat","first_name":"l","6":"l","last_name":"n","7":"n","releases":[{"0":"1778","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"wombat.vim","4":"wombat.vim","src_id":"6657","5":"6657","creation_date":"1169724359","6":"1169724359"}]},"1777":{"script_id":"1777","0":"1777","script_name":"cvsdiff","1":"cvsdiff","script_type":"utility","2":"utility","summary":"a simple shell script that invoking vimdiff to compare CVS file","3":"a simple shell script that invoking vimdiff to compare CVS file","description":"You can use this script to invoke vimdiff for comparing two files between CVS repository and local copy, or any two difference CVS revision in repository.\r\n\r\nUsage: cvsdiff [-rrevision1] [-rrevision2] file\r\nExamples:\r\n  cvsdiff test.c                           show difference between cvs (in your branch) and local copy.\r\n  cvsdiff -r1.3 test.c                  show difference between revision 1.3 and local copy.\r\n  cvsdiff -rHEAD test.c            show difference between HEAD and local copy.\r\n  cvsdiff -r1.3 -r1.4 test.c         show difference between revision 1.3 and revision 1.4.\r\n  cvsdiff -rHEAD -r1.4 test.c   show difference between HEAD and revision 1.4.\r\n","4":"You can use this script to invoke vimdiff for comparing two files between CVS repository and local copy, or any two difference CVS revision in repository.\r\n\r\nUsage: cvsdiff [-rrevision1] [-rrevision2] file\r\nExamples:\r\n  cvsdiff test.c                           show difference between cvs (in your branch) and local copy.\r\n  cvsdiff -r1.3 test.c                  show difference between revision 1.3 and local copy.\r\n  cvsdiff -rHEAD test.c            show difference between HEAD and local copy.\r\n  cvsdiff -r1.3 -r1.4 test.c         show difference between revision 1.3 and revision 1.4.\r\n  cvsdiff -rHEAD -r1.4 test.c   show difference between HEAD and revision 1.4.\r\n","install_details":"1. Download it and add throw it in a directory which included by PATH.\r\n2. Add execution permission.\r\n    chmod +x cvsdiff\r\n3. Run it.","5":"1. Download it and add throw it in a directory which included by PATH.\r\n2. Add execution permission.\r\n    chmod +x cvsdiff\r\n3. Run it.","first_name":"Mockey","6":"Mockey","last_name":"Chen","7":"Chen","releases":[{"0":"1777","vim_version":"6.0","1":"6.0","script_version":"1.00","2":"1.00","version_comment":"Initial upload","3":"Initial upload","package":"cvsdiff","4":"cvsdiff","src_id":"6655","5":"6655","creation_date":"1169658848","6":"1169658848"}]},"1776":{"script_id":"1776","0":"1776","script_name":"Vimgrep Replace","1":"Vimgrep Replace","script_type":"utility","2":"utility","summary":"Use vimgrep to do search and replace","3":"Use vimgrep to do search and replace","description":"Embryonic hack to allow a user to do search and replaces on a directory using vimgrep and s\/\/\/\r\n\r\nSuggestions and updates are very welcome!","4":"Embryonic hack to allow a user to do search and replaces on a directory using vimgrep and s\/\/\/\r\n\r\nSuggestions and updates are very welcome!","install_details":"","5":"","first_name":"Michael","6":"Michael","last_name":"Geddes","7":"Geddes","releases":[{"0":"1776","vim_version":"6.0","1":"6.0","script_version":"0.3","2":"0.3","version_comment":"Added Bsub - alias to :bufdo %s\/\/\/ - (requested).","3":"Added Bsub - alias to :bufdo %s\/\/\/ - (requested).","package":"vgrepsup.vim","4":"vgrepsup.vim","src_id":"7902","5":"7902","creation_date":"1194521984","6":"1194521984"},{"0":"1776","vim_version":"6.0","1":"6.0","script_version":"0.2","2":"0.2","version_comment":"Added :command\r\n:Gsub  \/srch\/replace\/flags  filespec","3":"Added :command\r\n:Gsub  \/srch\/replace\/flags  filespec","package":"vgrepsup.vim","4":"vgrepsup.vim","src_id":"7810","5":"7810","creation_date":"1192755713","6":"1192755713"},{"0":"1776","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"vgrepsup.vim","4":"vgrepsup.vim","src_id":"6651","5":"6651","creation_date":"1169604721","6":"1169604721"}]},"1775":{"script_id":"1775","0":"1775","script_name":"tcl_critcl.vim","1":"tcl_critcl.vim","script_type":"syntax","2":"syntax","summary":"syntax coloring for critcl. extend tcl.vim","3":"syntax coloring for critcl. extend tcl.vim","description":"    c-syntax for blocks of c-code in tcl definitions.\r\n\r\n    Adds critcl syntax to tcl.vim (vimscript #1603)\r\n\r\n","4":"    c-syntax for blocks of c-code in tcl definitions.\r\n\r\n    Adds critcl syntax to tcl.vim (vimscript #1603)\r\n\r\n","install_details":"    Place in ~\/.vim\/syntax\/\r\n\r\n    Activated by uncommenting the option at the top of the tcl.vim file.\r\n","5":"    Place in ~\/.vim\/syntax\/\r\n\r\n    Activated by uncommenting the option at the top of the tcl.vim file.\r\n","first_name":"sm","6":"sm","last_name":"smithfield","7":"smithfield","releases":[{"0":"1775","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"tcl_critcl.vim","4":"tcl_critcl.vim","src_id":"6649","5":"6649","creation_date":"1169594199","6":"1169594199"}]},"1774":{"script_id":"1774","0":"1774","script_name":"Menu_SQL_Templates.vim","1":"Menu_SQL_Templates.vim","script_type":"utility","2":"utility","summary":"SQL code templates in VIM Menu","3":"SQL code templates in VIM Menu","description":"This is a simple script, which adds a new menu in GVIM. The menu SQL_Templates will have few sub menus. \r\n\r\nThe purpose of the this is to insert SQL code templates in current window\/ file.\r\nSo you don't have to refer manuals for those SQL commands which you don;t use often.","4":"This is a simple script, which adds a new menu in GVIM. The menu SQL_Templates will have few sub menus. \r\n\r\nThe purpose of the this is to insert SQL code templates in current window\/ file.\r\nSo you don't have to refer manuals for those SQL commands which you don;t use often.","install_details":"Just Put the file in you plugin folder.","5":"Just Put the file in you plugin folder.","first_name":"san","6":"san","last_name":"sap","7":"sap","releases":[{"0":"1774","vim_version":"7.0","1":"7.0","script_version":"1.1","2":"1.1","version_comment":"Re-arranged menus, added few new menus ","3":"Re-arranged menus, added few new menus ","package":"Menu_SQL_Templates.vim","4":"Menu_SQL_Templates.vim","src_id":"6772","5":"6772","creation_date":"1172207083","6":"1172207083"},{"0":"1774","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"Menu_SQL_Templates.vim","4":"Menu_SQL_Templates.vim","src_id":"6647","5":"6647","creation_date":"1169534298","6":"1169534298"}]},"1773":{"script_id":"1773","0":"1773","script_name":"Haml","1":"Haml","script_type":"syntax","2":"syntax","summary":"Haml syntax highlight","3":"Haml syntax highlight","description":"This is the syntax highlighting mode for Haml (http:\/\/haml.hamptoncatlin.com\/) -- XHTML Abstraction Markup Language (http:\/\/en.wikipedia.org\/wiki\/Haml)\r\n\r\nScreenshot: http:\/\/www.flickr.com\/photos\/dmitryilyashevich\/1006425091\/","4":"This is the syntax highlighting mode for Haml (http:\/\/haml.hamptoncatlin.com\/) -- XHTML Abstraction Markup Language (http:\/\/en.wikipedia.org\/wiki\/Haml)\r\n\r\nScreenshot: http:\/\/www.flickr.com\/photos\/dmitryilyashevich\/1006425091\/","install_details":"put it into syntax directory and add haml filetype \r\n\r\nau! BufRead,BufNewFile *.haml         setfiletype haml\r\n\r\nin your filetype.vim","5":"put it into syntax directory and add haml filetype \r\n\r\nau! BufRead,BufNewFile *.haml         setfiletype haml\r\n\r\nin your filetype.vim","first_name":"Dmitry","6":"Dmitry","last_name":"Ilyashevich","7":"Ilyashevich","releases":[{"0":"1773","vim_version":"6.0","1":"6.0","script_version":"0.3","2":"0.3","version_comment":"Last synced with Haml 1.8","3":"Last synced with Haml 1.8","package":"haml.vim","4":"haml.vim","src_id":"8461","5":"8461","creation_date":"1205807142","6":"1205807142"},{"0":"1773","vim_version":"7.0","1":"7.0","script_version":"0.2","2":"0.2","version_comment":"Much better quality","3":"Much better quality","package":"haml.vim","4":"haml.vim","src_id":"7353","5":"7353","creation_date":"1184416805","6":"1184416805"},{"0":"1773","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"haml.vim","4":"haml.vim","src_id":"6643","5":"6643","creation_date":"1169474202","6":"1169474202"}]},"1772":{"script_id":"1772","0":"1772","script_name":"DAMOS tools","1":"DAMOS tools","script_type":"utility","2":"utility","summary":"syntax-, indent- and ftplugins for files to use with DAMOS application tool","3":"syntax-, indent- and ftplugins for files to use with DAMOS application tool","description":"DAMOS tools provides support for several filetypes used by DAMOS:\r\n*.dcm, *.dcl, *.kgs\r\n\r\nIt supports syntax highliting, indentation, commentify, tags, ...\r\n\r\nTags:\r\n- if you want to create tags for your kgs- and osp-files you can use the configuration file tools\/ctags.conf. Now you can jump from a kgs-file to the 'codesyntax' or the 'umrechnung'.\r\n\r\n'Umrechnung':\r\n- If you have osp-files for 'umrechnung' and you parsed it with ctags, you can get a set of example values by the command 'GetOspTestValues'\r\n- see :help damos for more information","4":"DAMOS tools provides support for several filetypes used by DAMOS:\r\n*.dcm, *.dcl, *.kgs\r\n\r\nIt supports syntax highliting, indentation, commentify, tags, ...\r\n\r\nTags:\r\n- if you want to create tags for your kgs- and osp-files you can use the configuration file tools\/ctags.conf. Now you can jump from a kgs-file to the 'codesyntax' or the 'umrechnung'.\r\n\r\n'Umrechnung':\r\n- If you have osp-files for 'umrechnung' and you parsed it with ctags, you can get a set of example values by the command 'GetOspTestValues'\r\n- see :help damos for more information","install_details":"extract zip-file in your vimfiles directory","5":"extract zip-file in your vimfiles directory","first_name":"Stefan","6":"Stefan","last_name":"Liebl","7":"Liebl","releases":[{"0":"1772","vim_version":"7.0","1":"7.0","script_version":"1.3","2":"1.3","version_comment":"added some keywords","3":"added some keywords","package":"damos.zip","4":"damos.zip","src_id":"7248","5":"7248","creation_date":"1181866353","6":"1181866353"},{"0":"1772","vim_version":"7.0","1":"7.0","script_version":"1.2","2":"1.2","version_comment":"added keyword 'revision'","3":"added keyword 'revision'","package":"damos.zip","4":"damos.zip","src_id":"6973","5":"6973","creation_date":"1176358742","6":"1176358742"},{"0":"1772","vim_version":"7.0","1":"7.0","script_version":"1.1","2":"1.1","version_comment":"Bugfix in kgs-formatting, new keywords","3":"Bugfix in kgs-formatting, new keywords","package":"damos.zip","4":"damos.zip","src_id":"6793","5":"6793","creation_date":"1172448809","6":"1172448809"},{"0":"1772","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"damos.zip","4":"damos.zip","src_id":"6641","5":"6641","creation_date":"1169441937","6":"1169441937"}]},"1771":{"script_id":"1771","0":"1771","script_name":"woc","1":"woc","script_type":"utility","2":"utility","summary":"A vim WoC browser. It enables hyperlinks for sources and ASCII texts.","3":"A vim WoC browser. It enables hyperlinks for sources and ASCII texts.","description":"This is the WoC client for Vim.\r\nIf you don't know what WoC is, read http:\/\/dev.dyne.org\/wiki\/Woc .\r\n\r\nShort description:\r\nThis plugin permits to use \"hypertags\", i.e. tags pointing to remote files. \r\nIt also supports cscope and ctags, thus you can use hyper-cscope commands which will bring you to remote locations.\r\n\r\nGeneral description:\r\nWocvim is a WoC client for Vim. WoC is a protocol which enables the use of hyperlinks in plain ASCII texts. \r\nThe links can point to local or remote locations. The protocol is specifically designed to support source code, but it can\r\nbe used in any text. For source code, it's also possible to use ad-hoc tag generators like cscope and ctags.\r\n\r\n\r\nwoc-vim: http:\/\/www.freaknet.org\/alpt\/src\/utils\/woc\/readme","4":"This is the WoC client for Vim.\r\nIf you don't know what WoC is, read http:\/\/dev.dyne.org\/wiki\/Woc .\r\n\r\nShort description:\r\nThis plugin permits to use \"hypertags\", i.e. tags pointing to remote files. \r\nIt also supports cscope and ctags, thus you can use hyper-cscope commands which will bring you to remote locations.\r\n\r\nGeneral description:\r\nWocvim is a WoC client for Vim. WoC is a protocol which enables the use of hyperlinks in plain ASCII texts. \r\nThe links can point to local or remote locations. The protocol is specifically designed to support source code, but it can\r\nbe used in any text. For source code, it's also possible to use ad-hoc tag generators like cscope and ctags.\r\n\r\n\r\nwoc-vim: http:\/\/www.freaknet.org\/alpt\/src\/utils\/woc\/readme","install_details":"Download the latest woc-vim tarball from:\r\nhttp:\/\/www.freaknet.org\/alpt\/src\/utils\/woc\/tarball\/\r\n\r\nThen just use .\/install.sh   \r\nor simply execute the following commands:\r\n                            \r\n        cp wocdownloader ~\/.vim\/woc\/\r\n        cp woc.vim ~\/.vim\/plugin\/","5":"Download the latest woc-vim tarball from:\r\nhttp:\/\/www.freaknet.org\/alpt\/src\/utils\/woc\/tarball\/\r\n\r\nThen just use .\/install.sh   \r\nor simply execute the following commands:\r\n                            \r\n        cp wocdownloader ~\/.vim\/woc\/\r\n        cp woc.vim ~\/.vim\/plugin\/","first_name":"AlpT","6":"AlpT","last_name":"Aliptah","7":"Aliptah","releases":[{"0":"1771","vim_version":"7.0","1":"7.0","script_version":"1.2","2":"1.2","version_comment":"Fixed a ``wocdownloader'' bug.\r\n\r\nAdded the g:woc_global_index option. It specifies to always load a global\r\nindex.woc file.\r\n\r\nPython syntax highlighting\r\n\r\nWhen WOCClearCache() is called automatically by WOC, only the last used cache\r\nis cleaned. If, instead, it is called by the :WocClearCache user command, the\r\nwhole cache\/ dir is removed.\r\n\r\nAdded the g:woc_mappings option, to let the user define more easily its own\r\nmappings.","3":"Fixed a ``wocdownloader'' bug.\r\n\r\nAdded the g:woc_global_index option. It specifies to always load a global\r\nindex.woc file.\r\n\r\nPython syntax highlighting\r\n\r\nWhen WOCClearCache() is called automatically by WOC, only the last used cache\r\nis cleaned. If, instead, it is called by the :WocClearCache user command, the\r\nwhole cache\/ dir is removed.\r\n\r\nAdded the g:woc_mappings option, to let the user define more easily its own\r\nmappings.","package":"woc-1.2.tar.bz2","4":"woc-1.2.tar.bz2","src_id":"6680","5":"6680","creation_date":"1169978813","6":"1169978813"},{"0":"1771","vim_version":"7.0","1":"7.0","script_version":"1.1","2":"1.1","version_comment":"A little bit of documentation added.\r\nRead the README ;)","3":"A little bit of documentation added.\r\nRead the README ;)","package":"woc-1.1.tar.bz2","4":"woc-1.1.tar.bz2","src_id":"6662","5":"6662","creation_date":"1169789136","6":"1169789136"},{"0":"1771","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"woc-1.0.tar.bz2","4":"woc-1.0.tar.bz2","src_id":"6637","5":"6637","creation_date":"1169394180","6":"1169394180"}]},"1770":{"script_id":"1770","0":"1770","script_name":"etk-vim-syntax","1":"etk-vim-syntax","script_type":"syntax","2":"syntax","summary":"Syntax highlighting for Etk Enlightenment Toolkit","3":"Syntax highlighting for Etk Enlightenment Toolkit","description":"A C extension syntax file for Etk.\r\n\r\nEtk stand for Enlightenment Toolkit, it's another graphical toolkit written\r\nwith the new EFL. It's under development and there is no stable release for\r\nthe moment, so etk.vim file may not to be up to date.\r\n\r\nEtk version: 0.1.0.002","4":"A C extension syntax file for Etk.\r\n\r\nEtk stand for Enlightenment Toolkit, it's another graphical toolkit written\r\nwith the new EFL. It's under development and there is no stable release for\r\nthe moment, so etk.vim file may not to be up to date.\r\n\r\nEtk version: 0.1.0.002","install_details":"You should run 'vim etk.vba' and ':so %'\r\nor\r\nYou should copy etk.vim in ~\/.vim\/after\/syntax\/c\/\r\nor\r\nYou should copy etk.vim in ~\/.vim\/after\/syntax\/ and add it in ~\/.vim\/after\/syntax\/c.vim\r\nor\r\nYou should ':h runtimepath' ;)\r\n\r\nsee README","5":"You should run 'vim etk.vba' and ':so %'\r\nor\r\nYou should copy etk.vim in ~\/.vim\/after\/syntax\/c\/\r\nor\r\nYou should copy etk.vim in ~\/.vim\/after\/syntax\/ and add it in ~\/.vim\/after\/syntax\/c.vim\r\nor\r\nYou should ':h runtimepath' ;)\r\n\r\nsee README","first_name":"aji","6":"aji","last_name":"prod","7":"prod","releases":[{"0":"1770","vim_version":"5.7","1":"5.7","script_version":"0.1","2":"0.1","version_comment":"++API","3":"++API","package":"etk-vim-syntax.tar.gz","4":"etk-vim-syntax.tar.gz","src_id":"7191","5":"7191","creation_date":"1180770065","6":"1180770065"},{"0":"1770","vim_version":"5.7","1":"5.7","script_version":"0.1","2":"0.1","version_comment":"etk.vba added","3":"etk.vba added","package":"etk-vim-syntax.tar.gz","4":"etk-vim-syntax.tar.gz","src_id":"6636","5":"6636","creation_date":"1169363190","6":"1169363190"}]},"1769":{"script_id":"1769","0":"1769","script_name":"lispcomplete.vim","1":"lispcomplete.vim","script_type":"utility","2":"utility","summary":"SLIME-like compound completion for Lisp","3":"SLIME-like compound completion for Lisp","description":"*** Before using this script, you should check out Limp - http:\/\/mikael.jansson.be\/hacking\/limp\/docs\/\r\nIt gives an experience much closer to SLIME, and is most likely a better solution. ***\r\n\r\nAn omnifunc that provides SLIME style completion of compound keywords.\r\n\r\ne.g.   \\\"m-v-b<C-X><C-O>\\\" expands to \\\"multiple-value-bind\\\"\r\n\r\nThis isn\\'t anything close to a reimplementation of SLIME completion, but provides something closer to the default behavior. Most importantly, since there isn\\'t a connection to swank and a live lisp instance, you can only complete static keywords from the syntax file. (like syntaxcomplete.vim -- in fact this started out as a quick munging of that file, and still has lots of its code in there) Also, currently only \\\"simple\\\" and \\\"compound\\\" modes work, there is no support for \\\"fuzzy\\\" completion.","4":"*** Before using this script, you should check out Limp - http:\/\/mikael.jansson.be\/hacking\/limp\/docs\/\r\nIt gives an experience much closer to SLIME, and is most likely a better solution. ***\r\n\r\nAn omnifunc that provides SLIME style completion of compound keywords.\r\n\r\ne.g.   \\\"m-v-b<C-X><C-O>\\\" expands to \\\"multiple-value-bind\\\"\r\n\r\nThis isn\\'t anything close to a reimplementation of SLIME completion, but provides something closer to the default behavior. Most importantly, since there isn\\'t a connection to swank and a live lisp instance, you can only complete static keywords from the syntax file. (like syntaxcomplete.vim -- in fact this started out as a quick munging of that file, and still has lots of its code in there) Also, currently only \\\"simple\\\" and \\\"compound\\\" modes work, there is no support for \\\"fuzzy\\\" completion.","install_details":"put lispcomplete.vim in runtime\/autoload\r\nthen :setl omnifunc=lispcomplete#Complete","5":"put lispcomplete.vim in runtime\/autoload\r\nthen :setl omnifunc=lispcomplete#Complete","first_name":"Andrew","6":"Andrew","last_name":"Beyer","7":"Beyer","releases":[{"0":"1769","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"lispcomplete.vim","4":"lispcomplete.vim","src_id":"6629","5":"6629","creation_date":"1169176138","6":"1169176138"}]},"1768":{"script_id":"1768","0":"1768","script_name":"SnipSnap","1":"SnipSnap","script_type":"syntax","2":"syntax","summary":"Filetype and Syntax SnipSnap Wiki.","3":"Filetype and Syntax SnipSnap Wiki.","description":"This is a mirror of http:\/\/www.vim.org\/scripts\/script.php?script_id=1768\r\n\r\nSyntax and Filetype plugin for [http:\/\/www.snipsnap.org\/space\/start SnipSnap Wiki].\r\n\r\nUse together with [http:\/\/martin.krischik.com\/index.php\/Main\/EditusExternus.Editus Externus]\r\nand [http:\/\/www.mozilla.com\/firefox FireFox] for easy editing of SnipSnap Wiki pages.\r\n\r\n| Vim-Script  || https:\/\/www.vim.org\/scripts\/script.php?script_id=1768\r\n| Source      || https:\/\/github.com\/krischik\/vim-snipsnap\r\n| Wiki        || https:\/\/github.com\/krischik\/vim-snipsnap\/wiki\r\n| Releases    || https:\/\/github.com\/krischik\/vim-snipsnap\/releases \r\n| Issues      || https:\/\/github.com\/krischik\/vim-snipsnap\/issues \r\n| Discussions || https:\/\/github.com\/krischik\/vim-snipsnap\/discussions \r\n","4":"This is a mirror of http:\/\/www.vim.org\/scripts\/script.php?script_id=1768\r\n\r\nSyntax and Filetype plugin for [http:\/\/www.snipsnap.org\/space\/start SnipSnap Wiki].\r\n\r\nUse together with [http:\/\/martin.krischik.com\/index.php\/Main\/EditusExternus.Editus Externus]\r\nand [http:\/\/www.mozilla.com\/firefox FireFox] for easy editing of SnipSnap Wiki pages.\r\n\r\n| Vim-Script  || https:\/\/www.vim.org\/scripts\/script.php?script_id=1768\r\n| Source      || https:\/\/github.com\/krischik\/vim-snipsnap\r\n| Wiki        || https:\/\/github.com\/krischik\/vim-snipsnap\/wiki\r\n| Releases    || https:\/\/github.com\/krischik\/vim-snipsnap\/releases \r\n| Issues      || https:\/\/github.com\/krischik\/vim-snipsnap\/issues \r\n| Discussions || https:\/\/github.com\/krischik\/vim-snipsnap\/discussions \r\n","install_details":"Install from https:\/\/github.com\/krischik\/vim-snipsnap using dein (https:\/\/github.com\/Shougo\/dein.vim) or similar:\r\n\r\ncall dein#begin('$HOME\/vimfiles\/bundles')\r\ncall dein#add('krischik\/vim-snipsnap')\r\ncall dein#end()\r\ncall dein#install()\r\n","5":"Install from https:\/\/github.com\/krischik\/vim-snipsnap using dein (https:\/\/github.com\/Shougo\/dein.vim) or similar:\r\n\r\ncall dein#begin('$HOME\/vimfiles\/bundles')\r\ncall dein#add('krischik\/vim-snipsnap')\r\ncall dein#end()\r\ncall dein#install()\r\n","first_name":"Martin","6":"Martin","last_name":"Krischik","7":"Krischik","releases":[{"0":"1768","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"snipsnap-0.1.vba","4":"snipsnap-0.1.vba","src_id":"6628","5":"6628","creation_date":"1169174648","6":"1169174648"}]},"1767":{"script_id":"1767","0":"1767","script_name":"recent.vim","1":"recent.vim","script_type":"utility","2":"utility","summary":"Quick access to recently written files","3":"Quick access to recently written files","description":"Former recentern.vim\r\nInspired by vimscript #1228\r\n\r\nRecent.vim keeps track of files you have _written_ recently.  This is useful\r\nto continue work on files that are scattered around the file system.\r\n\r\nThe list of filenames is persistently stored in ~\/.vim\/recent_files\r\n\r\nPer default, the filelist shows up at startup if no other file (or session) is loaded.\r\nAlso a menu with commands gets installed.  You can turn these things off.\r\n\r\nTo open a file of the list, several commands and options are provided to make\r\nuse of windows and tabpages.\r\n\r\nDetails can be found in the help file.\r\n\r\nMisc:\r\n- if there is a window for a file, it is always reused (first one found in\r\n  any tabpage), currently not customizable\r\n- files can be ignored based on autocmd-pattern\r\n- filenames can be highlighted based on extension\r\n- the file list is only updated when necessary","4":"Former recentern.vim\r\nInspired by vimscript #1228\r\n\r\nRecent.vim keeps track of files you have _written_ recently.  This is useful\r\nto continue work on files that are scattered around the file system.\r\n\r\nThe list of filenames is persistently stored in ~\/.vim\/recent_files\r\n\r\nPer default, the filelist shows up at startup if no other file (or session) is loaded.\r\nAlso a menu with commands gets installed.  You can turn these things off.\r\n\r\nTo open a file of the list, several commands and options are provided to make\r\nuse of windows and tabpages.\r\n\r\nDetails can be found in the help file.\r\n\r\nMisc:\r\n- if there is a window for a file, it is always reused (first one found in\r\n  any tabpage), currently not customizable\r\n- files can be ignored based on autocmd-pattern\r\n- filenames can be highlighted based on extension\r\n- the file list is only updated when necessary","install_details":"recent.vim is a plugin, put it into the plugin folder or :source it directly\r\n\t:help add-plugin\r\n\r\nSee the Customization section in the script (recommended)","5":"recent.vim is a plugin, put it into the plugin folder or :source it directly\r\n\t:help add-plugin\r\n\r\nSee the Customization section in the script (recommended)","first_name":"Andy","6":"Andy","last_name":"Wokula","7":"Wokula","releases":[{"0":"1767","vim_version":"7.0","1":"7.0","script_version":"12","2":"12","version_comment":"mostly changes and fixes, added: help file, menu","3":"mostly changes and fixes, added: help file, menu","package":"recent.zip","4":"recent.zip","src_id":"7216","5":"7216","creation_date":"1181217841","6":"1181217841"},{"0":"1767","vim_version":"7.0","1":"7.0","script_version":"9.2","2":"9.2","version_comment":"Initial upload","3":"Initial upload","package":"recentern.vim","4":"recentern.vim","src_id":"6622","5":"6622","creation_date":"1169130540","6":"1169130540"}]},"1766":{"script_id":"1766","0":"1766","script_name":"tcl_togl.vim","1":"tcl_togl.vim","script_type":"syntax","2":"syntax","summary":"syntax coloring for togl. extends tcl.vim","3":"syntax coloring for togl. extends tcl.vim","description":"Adds togl syntax to tcl.vim (vimscript #1603)\r\n","4":"Adds togl syntax to tcl.vim (vimscript #1603)\r\n","install_details":"    Place in ~\/.vim\/syntax\/\r\n\r\n    Activated by uncommenting the option at the top of the tcl.vim file.\r\n","5":"    Place in ~\/.vim\/syntax\/\r\n\r\n    Activated by uncommenting the option at the top of the tcl.vim file.\r\n","first_name":"sm","6":"sm","last_name":"smithfield","7":"smithfield","releases":[{"0":"1766","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"tcl_togl.vim","4":"tcl_togl.vim","src_id":"6611","5":"6611","creation_date":"1168549552","6":"1168549552"}]},"1765":{"script_id":"1765","0":"1765","script_name":"tcl_itcl.vim","1":"tcl_itcl.vim","script_type":"syntax","2":"syntax","summary":"syntax coloring for itcl, extends tcl.vim.","3":"syntax coloring for itcl, extends tcl.vim.","description":" Adds itcl syntax to tcl.vim (vimscript #1603)","4":" Adds itcl syntax to tcl.vim (vimscript #1603)","install_details":"Place in ~\/.vim\/syntax\r\n\r\nActivated by uncommenting the option at the top of the tcl.vim file.\r\n\r\n","5":"Place in ~\/.vim\/syntax\r\n\r\nActivated by uncommenting the option at the top of the tcl.vim file.\r\n\r\n","first_name":"sm","6":"sm","last_name":"smithfield","7":"smithfield","releases":[{"0":"1765","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"tcl_itcl.vim","4":"tcl_itcl.vim","src_id":"6610","5":"6610","creation_date":"1168549303","6":"1168549303"}]},"1764":{"script_id":"1764","0":"1764","script_name":"code_complete","1":"code_complete","script_type":"utility","2":"utility","summary":"function parameter complete, code snippets, and much more.","3":"function parameter complete, code snippets, and much more.","description":"Get the latest version from Github:\r\nhttps:\/\/github.com\/mbbill\/code_complete\r\n\r\n\r\nDemo :http:\/\/files.myopera.com\/mbbill\/files\/code_complete.gif\r\nIt shows what this script can do.\r\nIn insert mode, when you type \"<tab>\"(default value of g:completekey) after function name with a \"(\" , function parameters will be append behind, use \"<tab>\" key again to switch between parameters.\r\nThis key is also used to complete code snippets.\r\nExample:\r\npress <tab> after function name and (     \r\n  foo ( <tab>                             \r\nbecomes:                                  \r\n  foo ( `<first param>`,`<second param>` )\r\npress <tab> after code template           \r\n  if <tab>                                \r\nbecomes:                                  \r\n  if( `<...>` )                           \r\n  {                                       \r\n      `<...>`                             \r\n  }                                       ","4":"Get the latest version from Github:\r\nhttps:\/\/github.com\/mbbill\/code_complete\r\n\r\n\r\nDemo :http:\/\/files.myopera.com\/mbbill\/files\/code_complete.gif\r\nIt shows what this script can do.\r\nIn insert mode, when you type \"<tab>\"(default value of g:completekey) after function name with a \"(\" , function parameters will be append behind, use \"<tab>\" key again to switch between parameters.\r\nThis key is also used to complete code snippets.\r\nExample:\r\npress <tab> after function name and (     \r\n  foo ( <tab>                             \r\nbecomes:                                  \r\n  foo ( `<first param>`,`<second param>` )\r\npress <tab> after code template           \r\n  if <tab>                                \r\nbecomes:                                  \r\n  if( `<...>` )                           \r\n  {                                       \r\n      `<...>`                             \r\n  }                                       ","install_details":"1. Put code_complete.vim to plugin  directory.                          \r\n2. Use the command below to create tags file including signature field.     \r\n   ctags -R --c-kinds=+p --fields=+S .\r\n","5":"1. Put code_complete.vim to plugin  directory.                          \r\n2. Use the command below to create tags file including signature field.     \r\n   ctags -R --c-kinds=+p --fields=+S .\r\n","first_name":"Ming","6":"Ming","last_name":"Bai","7":"Bai","releases":[{"0":"1764","vim_version":"7.0","1":"7.0","script_version":"2.9","2":"2.9","version_comment":"Set file format to unix.","3":"Set file format to unix.","package":"code_complete.vim","4":"code_complete.vim","src_id":"10778","5":"10778","creation_date":"1244477737","6":"1244477737"},{"0":"1764","vim_version":"7.0","1":"7.0","script_version":"2.8","2":"2.8","version_comment":"Add support to function pointer.","3":"Add support to function pointer.","package":"code_complete.vim","4":"code_complete.vim","src_id":"10347","5":"10347","creation_date":"1238856575","6":"1238856575"},{"0":"1764","vim_version":"7.0","1":"7.0","script_version":"2.7","2":"2.7","version_comment":"No longer force set selection to inclusive.","3":"No longer force set selection to inclusive.","package":"code_complete.vim","4":"code_complete.vim","src_id":"7384","5":"7384","creation_date":"1184899215","6":"1184899215"},{"0":"1764","vim_version":"7.0","1":"7.0","script_version":"2.6","2":"2.6","version_comment":"new features:  user defined snippets file support.\r\nchanges:   '('  no longer used , and one \"<tab>\" after '(' instead.","3":"new features:  user defined snippets file support.\r\nchanges:   '('  no longer used , and one \"<tab>\" after '(' instead.","package":"code_complete.zip","4":"code_complete.zip","src_id":"6841","5":"6841","creation_date":"1173161294","6":"1173161294"},{"0":"1764","vim_version":"7.0","1":"7.0","script_version":"2.5","2":"2.5","version_comment":"Speed up the script when the tag file is very big, thanks to Martin Stubenschrott.","3":"Speed up the script when the tag file is very big, thanks to Martin Stubenschrott.","package":"code_complete.vim","4":"code_complete.vim","src_id":"6656","5":"6656","creation_date":"1169667671","6":"1169667671"},{"0":"1764","vim_version":"7.0","1":"7.0","script_version":"2.4","2":"2.4","version_comment":"bugfix","3":"bugfix","package":"code_complete.vim","4":"code_complete.vim","src_id":"6645","5":"6645","creation_date":"1169506236","6":"1169506236"},{"0":"1764","vim_version":"7.0","1":"7.0","script_version":"2.3","2":"2.3","version_comment":"Some improvements, including hot key customization and so on.","3":"Some improvements, including hot key customization and so on.","package":"code_complete.vim","4":"code_complete.vim","src_id":"6638","5":"6638","creation_date":"1169406665","6":"1169406665"},{"0":"1764","vim_version":"7.0","1":"7.0","script_version":"2.2","2":"2.2","version_comment":"Initial upload","3":"Initial upload","package":"code_complete.vim","4":"code_complete.vim","src_id":"6606","5":"6606","creation_date":"1168510969","6":"1168510969"}]},"1763":{"script_id":"1763","0":"1763","script_name":"lua-support","1":"lua-support","script_type":"utility","2":"utility","summary":"Lua-IDE -- Write and run Lua-scripts using menus and hotkeys","3":"Lua-IDE -- Write and run Lua-scripts using menus and hotkeys","description":"***** This plug-in is no longer supported *****\r\n\r\nThe successor for this plugin is Lua Support 2 :\r\nhttp:\/\/vim.sourceforge.net\/scripts\/script.php?script_id=4950 \r\n\r\n\r\n***************\r\n\r\n\r\n\r\n- insert various types of comments\r\n- insert complete statements (e.g. 'if then else end' )\r\n- insert often used code snippets (e.g. empty function, open file)\r\n- read, write, maintain your own code snippets in a separate directory\r\n- run scripts or run syntax check from within the editor\r\n- show compilation erros in a quickfix window; navigate with hotkeys\r\n\r\nDOCUMENTATION\r\n--------------------------------------------------------\r\nThis plug-in comes with a help file (luasupport.txt). Read it with\r\n\r\n    :help luasupport","4":"***** This plug-in is no longer supported *****\r\n\r\nThe successor for this plugin is Lua Support 2 :\r\nhttp:\/\/vim.sourceforge.net\/scripts\/script.php?script_id=4950 \r\n\r\n\r\n***************\r\n\r\n\r\n\r\n- insert various types of comments\r\n- insert complete statements (e.g. 'if then else end' )\r\n- insert often used code snippets (e.g. empty function, open file)\r\n- read, write, maintain your own code snippets in a separate directory\r\n- run scripts or run syntax check from within the editor\r\n- show compilation erros in a quickfix window; navigate with hotkeys\r\n\r\nDOCUMENTATION\r\n--------------------------------------------------------\r\nThis plug-in comes with a help file (luasupport.txt). Read it with\r\n\r\n    :help luasupport","install_details":"Copy the zip archive  lua-support.zip  to $HOME\/.vim\/ or $VIM\/vimfiles (on the Windows platforms) and run\r\n    unzip lua-support.zip\r\nSee also the README file within the zip file.\r\n","5":"Copy the zip archive  lua-support.zip  to $HOME\/.vim\/ or $VIM\/vimfiles (on the Windows platforms) and run\r\n    unzip lua-support.zip\r\nSee also the README file within the zip file.\r\n","first_name":"Fritz","6":"Fritz","last_name":"Mehner","7":"Mehner","releases":[{"0":"1763","vim_version":"6.0","1":"6.0","script_version":"1.1","2":"1.1","version_comment":"+ New menu item and key mapping to adjust end-of-line comments.\r\n+ New insert mode mappings.\r\n+ A few mappings have been renamed (to bring them into line with my C\/C++).\r\n+ New global variable for Lua compiler and interpreter name.\r\n+ Better adaption for console mode.\r\n+ Better adaption for MS Windows.\r\n+ Snippets can now be managed in the console mode.","3":"+ New menu item and key mapping to adjust end-of-line comments.\r\n+ New insert mode mappings.\r\n+ A few mappings have been renamed (to bring them into line with my C\/C++).\r\n+ New global variable for Lua compiler and interpreter name.\r\n+ Better adaption for console mode.\r\n+ Better adaption for MS Windows.\r\n+ Snippets can now be managed in the console mode.","package":"lua-support.zip","4":"lua-support.zip","src_id":"7313","5":"7313","creation_date":"1183345757","6":"1183345757"},{"0":"1763","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"lua-support.zip","4":"lua-support.zip","src_id":"6605","5":"6605","creation_date":"1168485470","6":"1168485470"}]},"1762":{"script_id":"1762","0":"1762","script_name":"aspnetcs","1":"aspnetcs","script_type":"syntax","2":"syntax","summary":"Syntax highlighting for ASP.NET C# files","3":"Syntax highlighting for ASP.NET C# files","description":"This script is just a syntax highlighting file for ASP.NET files (.aspx, .ascx) written with C# as the language.","4":"This script is just a syntax highlighting file for ASP.NET files (.aspx, .ascx) written with C# as the language.","install_details":"Unpack the tarball in ~\/.vim.  That's it.","5":"Unpack the tarball in ~\/.vim.  That's it.","first_name":"Rob","6":"Rob","last_name":"Hoelz","7":"Hoelz","releases":[{"0":"1762","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"aspnetcs.tar.gz","4":"aspnetcs.tar.gz","src_id":"6604","5":"6604","creation_date":"1168473843","6":"1168473843"}]},"1761":{"script_id":"1761","0":"1761","script_name":"surrogat","1":"surrogat","script_type":"utility","2":"utility","summary":"Surrogate alphabets handling plugin","3":"Surrogate alphabets handling plugin","description":"This plugin converts Unicode characters to their ASCII representations (HTML, LaTeX, any) and vice versa. Data driven, highly configurable. Another location is http:\/\/wagner.pp.ru\/~slobin\/vim\/surrogat.zip\r\n ","4":"This plugin converts Unicode characters to their ASCII representations (HTML, LaTeX, any) and vice versa. Data driven, highly configurable. Another location is http:\/\/wagner.pp.ru\/~slobin\/vim\/surrogat.zip\r\n ","install_details":"","5":"","first_name":"Cyril","6":"Cyril","last_name":"Slobin","7":"Slobin","releases":[{"0":"1761","vim_version":"7.0","1":"7.0","script_version":"1.12","2":"1.12","version_comment":"Initial upload","3":"Initial upload","package":"surrogat.zip","4":"surrogat.zip","src_id":"6602","5":"6602","creation_date":"1168419402","6":"1168419402"}]},"1760":{"script_id":"1760","0":"1760","script_name":"lojban","1":"lojban","script_type":"ftplugin","2":"ftplugin","summary":"Lojban language support plugin","3":"Lojban language support plugin","description":"An exhaustive support for the Lojban language (http:\/\/www.lojban.org) - ftdetect, ftplugin and syntax files in one bundle. Another location is http:\/\/wagner.pp.ru\/~slobin\/vim\/lojban.zip\r\n ","4":"An exhaustive support for the Lojban language (http:\/\/www.lojban.org) - ftdetect, ftplugin and syntax files in one bundle. Another location is http:\/\/wagner.pp.ru\/~slobin\/vim\/lojban.zip\r\n ","install_details":"","5":"","first_name":"Cyril","6":"Cyril","last_name":"Slobin","7":"Slobin","releases":[{"0":"1760","vim_version":"7.0","1":"7.0","script_version":"1.9\/3.14","2":"1.9\/3.14","version_comment":"Nasty typo in filetype plugin fixed.","3":"Nasty typo in filetype plugin fixed.","package":"lojban.zip","4":"lojban.zip","src_id":"6805","5":"6805","creation_date":"1172540509","6":"1172540509"},{"0":"1760","vim_version":"7.0","1":"7.0","script_version":"1.8\/3.14","2":"1.8\/3.14","version_comment":"More compatible with common standards.","3":"More compatible with common standards.","package":"lojban.zip","4":"lojban.zip","src_id":"6771","5":"6771","creation_date":"1172201618","6":"1172201618"},{"0":"1760","vim_version":"7.0","1":"7.0","script_version":"1.8\/3.11","2":"1.8\/3.11","version_comment":"Initial upload","3":"Initial upload","package":"lojban.zip","4":"lojban.zip","src_id":"6601","5":"6601","creation_date":"1168418778","6":"1168418778"}]},"1759":{"script_id":"1759","0":"1759","script_name":"conlangs","1":"conlangs","script_type":"utility","2":"utility","summary":"Esperanto text typing plugin","3":"Esperanto text typing plugin","description":"Better alternative to Esperanto keyboard (also Volap\u00c3\u00bck is supported gratis). Another location is http:\/\/wagner.pp.ru\/~slobin\/vim\/conlangs.zip","4":"Better alternative to Esperanto keyboard (also Volap\u00c3\u00bck is supported gratis). Another location is http:\/\/wagner.pp.ru\/~slobin\/vim\/conlangs.zip","install_details":"","5":"","first_name":"Cyril","6":"Cyril","last_name":"Slobin","7":"Slobin","releases":[{"0":"1759","vim_version":"7.0","1":"7.0","script_version":"1.3","2":"1.3","version_comment":"Initial upload","3":"Initial upload","package":"conlangs.zip","4":"conlangs.zip","src_id":"6600","5":"6600","creation_date":"1168417619","6":"1168417619"}]},"1758":{"script_id":"1758","0":"1758","script_name":"kate.vim","1":"kate.vim","script_type":"color scheme","2":"color scheme","summary":"Kate Color Scheme","3":"Kate Color Scheme","description":"Simple light color scheme which is as close to Kate as I could get.  Let me know of any updates that need to be made.","4":"Simple light color scheme which is as close to Kate as I could get.  Let me know of any updates that need to be made.","install_details":"Place kate.vim into your $VIMPATH\/colors","5":"Place kate.vim into your $VIMPATH\/colors","first_name":"Donald Ephraim","6":"Donald Ephraim","last_name":"Curtis","7":"Curtis","releases":[{"0":"1758","vim_version":"7.0","1":"7.0","script_version":"1.1","2":"1.1","version_comment":"added some LaTeX colors to the scheme.","3":"added some LaTeX colors to the scheme.","package":"kate.vim","4":"kate.vim","src_id":"6599","5":"6599","creation_date":"1168386322","6":"1168386322"},{"0":"1758","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"kate.vim","4":"kate.vim","src_id":"6597","5":"6597","creation_date":"1168340671","6":"1168340671"}]},"1757":{"script_id":"1757","0":"1757","script_name":"lbdbq","1":"lbdbq","script_type":"utility","2":"utility","summary":"query lbdb from Vim","3":"query lbdb from Vim","description":"Functions and various mode mappings for querying lbdb (http:\/\/www.spinnaker.de\/lbdb\/) when using Vim to edit mails and mail headers, for example from Mutt (http:\/\/www.mutt.org).\r\n\r\nUsing this utility lines like the following appearing in a Vim buffer:\r\n    To: name surname, name2 surname2\r\ncan be automatically converted to lines like\r\n    To: My Friend <foo@example.com>, My Other Friend <bar@example.com>\r\nby querying lbdb.\r\n\r\nWhen the expansion of a given contact is ambiguous (i.e. it corresponds to more than one contact) the user is interactively asked to choose among them.\r\n\r\nThe utility can be used in various ways:\r\n- in normal mode typing <Leader>lb: the current recipient line will be expanded (i.e. all expandable short names will be expanded to full name\/address pairs)\r\n- in insert mode typing <Leader>lb: same as above but without leaving insert mode\r\n- in line visual mode typing <Leader>lb: same as above but all the visually selected line will be subject to expansion\r\n- in visual mode typing <Leader>lb: only the short names contained in the visually selected text will be subject to expansion\r\n\r\nRELATED SCRIPTS\r\n\r\nI'm (now) aware that vimscript #388 is older than this script of mine and provide similar features. But this script is strictly more powerful (YMMV of course). For example it works in various modes (visual\/insert\/normal\/...), is able to substitute more contacts at once, and takes into account the semantics of recipient lines. E.g.: if you try to expand \"name surname\" (without double quotes) the plugin looks up for both of them, while vimscript #388 will look up only for the part under the courses, leading more likely to ambiguous answers.","4":"Functions and various mode mappings for querying lbdb (http:\/\/www.spinnaker.de\/lbdb\/) when using Vim to edit mails and mail headers, for example from Mutt (http:\/\/www.mutt.org).\r\n\r\nUsing this utility lines like the following appearing in a Vim buffer:\r\n    To: name surname, name2 surname2\r\ncan be automatically converted to lines like\r\n    To: My Friend <foo@example.com>, My Other Friend <bar@example.com>\r\nby querying lbdb.\r\n\r\nWhen the expansion of a given contact is ambiguous (i.e. it corresponds to more than one contact) the user is interactively asked to choose among them.\r\n\r\nThe utility can be used in various ways:\r\n- in normal mode typing <Leader>lb: the current recipient line will be expanded (i.e. all expandable short names will be expanded to full name\/address pairs)\r\n- in insert mode typing <Leader>lb: same as above but without leaving insert mode\r\n- in line visual mode typing <Leader>lb: same as above but all the visually selected line will be subject to expansion\r\n- in visual mode typing <Leader>lb: only the short names contained in the visually selected text will be subject to expansion\r\n\r\nRELATED SCRIPTS\r\n\r\nI'm (now) aware that vimscript #388 is older than this script of mine and provide similar features. But this script is strictly more powerful (YMMV of course). For example it works in various modes (visual\/insert\/normal\/...), is able to substitute more contacts at once, and takes into account the semantics of recipient lines. E.g.: if you try to expand \"name surname\" (without double quotes) the plugin looks up for both of them, while vimscript #388 will look up only for the part under the courses, leading more likely to ambiguous answers.","install_details":"A matter of taste. Personally I drop lbdbq.vim in my ~\/.vim\/ directory and from  ~\/.vim\/after\/ftplugin\/mail.vim I do\r\n    source ~\/.vim\/lbdbq.vim\r\nIf you don't mind having this plugin always loaded just drop it in ~\/.vim\/plugin\/","5":"A matter of taste. Personally I drop lbdbq.vim in my ~\/.vim\/ directory and from  ~\/.vim\/after\/ftplugin\/mail.vim I do\r\n    source ~\/.vim\/lbdbq.vim\r\nIf you don't mind having this plugin always loaded just drop it in ~\/.vim\/plugin\/","first_name":"Stefano","6":"Stefano","last_name":"Zacchiroli","7":"Zacchiroli","releases":[{"0":"1757","vim_version":"7.0","1":"7.0","script_version":"0.3","2":"0.3","version_comment":"- quote the name part of returned addresses, so that names with (e.g.) commas does not break the headers\r\n- change license to GPL v3 or above","3":"- quote the name part of returned addresses, so that names with (e.g.) commas does not break the headers\r\n- change license to GPL v3 or above","package":"lbdbq.vim","4":"lbdbq.vim","src_id":"7393","5":"7393","creation_date":"1185098208","6":"1185098208"},{"0":"1757","vim_version":"7.0","1":"7.0","script_version":"0.2","2":"0.2","version_comment":"- bugfix for lines which are continuation of RFC822 fields\r\n- added URL field in the plugin\r\n- less stupid vmappings (i.e. more efficient)\r\n- normalize spaces when expanding contacts\r\n- silent mappings","3":"- bugfix for lines which are continuation of RFC822 fields\r\n- added URL field in the plugin\r\n- less stupid vmappings (i.e. more efficient)\r\n- normalize spaces when expanding contacts\r\n- silent mappings","package":"lbdbq.vim","4":"lbdbq.vim","src_id":"6594","5":"6594","creation_date":"1168263971","6":"1168263971"}]},"1756":{"script_id":"1756","0":"1756","script_name":"BinarySearchMove","1":"BinarySearchMove","script_type":"game","2":"game","summary":"implements a binary search algorithm to a cursor movement","3":"implements a binary search algorithm to a cursor movement","description":"Move a cursor with binary search principle - each step is twice shorter than previous.\r\nThis requires log2(N) steps in a worth case to position in a line with a length N (7 keypresses for a 120 chars line).\r\n\r\nleft\/right movement are bound to H and L\r\nup\/down to <Leader>u and <Leader>d \r\n","4":"Move a cursor with binary search principle - each step is twice shorter than previous.\r\nThis requires log2(N) steps in a worth case to position in a line with a length N (7 keypresses for a 120 chars line).\r\n\r\nleft\/right movement are bound to H and L\r\nup\/down to <Leader>u and <Leader>d \r\n","install_details":"Place in a plugin directory. Tune key binding if needed.\r\n","5":"Place in a plugin directory. Tune key binding if needed.\r\n","first_name":"Sply","6":"Sply","last_name":"Splyeff","7":"Splyeff","releases":[{"0":"1756","vim_version":"6.0","1":"6.0","script_version":"1","2":"1","version_comment":"Initial upload","3":"Initial upload","package":"bsmove.vim","4":"bsmove.vim","src_id":"6592","5":"6592","creation_date":"1168233580","6":"1168233580"}]},"1755":{"script_id":"1755","0":"1755","script_name":"sparql.vim","1":"sparql.vim","script_type":"syntax","2":"syntax","summary":"Syntax file for SPARQL query language for RDF","3":"Syntax file for SPARQL query language for RDF","description":"This is a first stab at syntax highlighting for SPARQL; Very useful if you write SPARQL in, for example, rq files that you can use with the roqet command line query processor. \r\n\r\nMore information on SPARQL at http:\/\/www.w3.org\/TR\/rdf-sparql-query\/. \r\n\r\nYou might find a more recent version at http:\/\/www.redslider.net\/2007\/2007-01-06-sparql-syntax-vim.html (check the last modified date in the script comment). ","4":"This is a first stab at syntax highlighting for SPARQL; Very useful if you write SPARQL in, for example, rq files that you can use with the roqet command line query processor. \r\n\r\nMore information on SPARQL at http:\/\/www.w3.org\/TR\/rdf-sparql-query\/. \r\n\r\nYou might find a more recent version at http:\/\/www.redslider.net\/2007\/2007-01-06-sparql-syntax-vim.html (check the last modified date in the script comment). ","install_details":"Place in ~\/.vim\/syntax\/sparql.vim. For more info see :help syntax. ","5":"Place in ~\/.vim\/syntax\/sparql.vim. For more info see :help syntax. ","first_name":"Jeroen","6":"Jeroen","last_name":"Pulles","7":"Pulles","releases":[{"0":"1755","vim_version":"6.0","1":"6.0","script_version":"0.0","2":"0.0","version_comment":"Initial upload","3":"Initial upload","package":"sparql.vim","4":"sparql.vim","src_id":"6588","5":"6588","creation_date":"1168143290","6":"1168143290"}]},"1754":{"script_id":"1754","0":"1754","script_name":"TTrCodeAssistor","1":"TTrCodeAssistor","script_type":"utility","2":"utility","summary":"Accelerate your inputing during coding,with auto-complete the function prototype","3":"Accelerate your inputing during coding,with auto-complete the function prototype","description":"I make it as easy as possible and make a lot of action for you to accelerate \r\nyour inputing coding , accoding to the habit of a coder . So i make a lot of \r\nexpand 'key' word to append the content with hot key <c-cr> , and move to the\r\ndifferent area just by <tab> . So ,try and  enjoy it ! I am sure you will love it!\r\n\r\nI add the function that let the ( can  complete the function prototype when you input \r\nyour coding  which make you not have to remeber the sequence of the function arguments.\r\n\r\nAdd the menu item which let you can  control whether this plugin can start or stop.\r\nAnd of course you can let it start automatically by add this to your vimrc:\r\nlet g:TTrCodeAssistor_AutoStart=1\r\n\r\nusage :\r\n<c-cr> to expand the 'key' word ( you can change it to you habit )\r\n<tab> to move forward and <s-tab> to move backward between the 'labels'\r\n(         key to compete the function prototype automantically.\r\n)         automatically move or input itself accoding to the content\r\n<bs>   use as normal but will remove the ) when its front char is (\r\n\r\nRecently ,  i will just add some useful function without map them to some key\r\nJust to expand the function of this plugin , so you can map it according to  your taste. :-)\r\n1. TTrcodeAssistor_ToggleComments\r\n                  nnoremap <F7> :call TTrCodeAssistor_ToggleComments()<CR>\r\n                  vnoremap <F7> :call TTrCodeAssistor_ToggleComments()<CR>\r\n\r\n\r\nNote : \r\n       the function prototype completing must use the exuberant ctags to\r\n       make the tag files which you should add to vim by :set ctags+=\/your\/file\r\n       and You have to add the arguments  --fields=+S after all your arguments\r\n       while making the tag files with 'ctags'\r\n       ex : Make the tags for all the  files of current directory including the subdirectory\r\n             ctags -R --c-types=+p --fields=+S *\r\n\r\n'key' word table can be seen in the file.\r\n\r\nJust have a try.","4":"I make it as easy as possible and make a lot of action for you to accelerate \r\nyour inputing coding , accoding to the habit of a coder . So i make a lot of \r\nexpand 'key' word to append the content with hot key <c-cr> , and move to the\r\ndifferent area just by <tab> . So ,try and  enjoy it ! I am sure you will love it!\r\n\r\nI add the function that let the ( can  complete the function prototype when you input \r\nyour coding  which make you not have to remeber the sequence of the function arguments.\r\n\r\nAdd the menu item which let you can  control whether this plugin can start or stop.\r\nAnd of course you can let it start automatically by add this to your vimrc:\r\nlet g:TTrCodeAssistor_AutoStart=1\r\n\r\nusage :\r\n<c-cr> to expand the 'key' word ( you can change it to you habit )\r\n<tab> to move forward and <s-tab> to move backward between the 'labels'\r\n(         key to compete the function prototype automantically.\r\n)         automatically move or input itself accoding to the content\r\n<bs>   use as normal but will remove the ) when its front char is (\r\n\r\nRecently ,  i will just add some useful function without map them to some key\r\nJust to expand the function of this plugin , so you can map it according to  your taste. :-)\r\n1. TTrcodeAssistor_ToggleComments\r\n                  nnoremap <F7> :call TTrCodeAssistor_ToggleComments()<CR>\r\n                  vnoremap <F7> :call TTrCodeAssistor_ToggleComments()<CR>\r\n\r\n\r\nNote : \r\n       the function prototype completing must use the exuberant ctags to\r\n       make the tag files which you should add to vim by :set ctags+=\/your\/file\r\n       and You have to add the arguments  --fields=+S after all your arguments\r\n       while making the tag files with 'ctags'\r\n       ex : Make the tags for all the  files of current directory including the subdirectory\r\n             ctags -R --c-types=+p --fields=+S *\r\n\r\n'key' word table can be seen in the file.\r\n\r\nJust have a try.","install_details":"put it into .vim\/plugin\/ and then enjoy it ","5":"put it into .vim\/plugin\/ and then enjoy it ","first_name":"winterTTr","6":"winterTTr","last_name":"Wang","7":"Wang","releases":[{"0":"1754","vim_version":"7.0","1":"7.0","script_version":"3.4","2":"3.4","version_comment":"-- Add function TTrCodeAssistor_ToggleComment to add or\r\n   remove comments of the current line or v selected area.\r\nYou can map it to a key like this :\r\n    nnoremap <F7> :call TTrCodeAssistor_ToggleComments()<CR>\r\n    vnoremap <F7> :call TTrCodeAssistor_ToggleComments()<CR>\r\n\r\nI think you can under stand the TTrCodeAssistor_Templates , so , you can expand it when you need.\r\n","3":"-- Add function TTrCodeAssistor_ToggleComment to add or\r\n   remove comments of the current line or v selected area.\r\nYou can map it to a key like this :\r\n    nnoremap <F7> :call TTrCodeAssistor_ToggleComments()<CR>\r\n    vnoremap <F7> :call TTrCodeAssistor_ToggleComments()<CR>\r\n\r\nI think you can under stand the TTrCodeAssistor_Templates , so , you can expand it when you need.\r\n","package":"TTrCodeAssistor.vim","4":"TTrCodeAssistor.vim","src_id":"7265","5":"7265","creation_date":"1182222895","6":"1182222895"},{"0":"1754","vim_version":"7.0","1":"7.0","script_version":"3.3","2":"3.3","version_comment":"-- Modify the code to match the function name exactly\r\n-- Let the menu to display rightly\r\n-- Add the function for <bs> to make it delete the redundant ) while the ) is close to (\r\n-- little bug fixed\r\n\r\n","3":"-- Modify the code to match the function name exactly\r\n-- Let the menu to display rightly\r\n-- Add the function for <bs> to make it delete the redundant ) while the ) is close to (\r\n-- little bug fixed\r\n\r\n","package":"TTrCodeAssistor.vim","4":"TTrCodeAssistor.vim","src_id":"6661","5":"6661","creation_date":"1169769670","6":"1169769670"},{"0":"1754","vim_version":"7.0","1":"7.0","script_version":"3.2.1","2":"3.2.1","version_comment":"remove the confirm info used to debug","3":"remove the confirm info used to debug","package":"TTrCodeAssistor.vim","4":"TTrCodeAssistor.vim","src_id":"6644","5":"6644","creation_date":"1169505571","6":"1169505571"},{"0":"1754","vim_version":"7.0","1":"7.0","script_version":"3.2","2":"3.2","version_comment":"-- Add the Menu for this plugin which let the user can                   \r\n   start or stop all the functions.\r\n-- Add TTrCodeAssistor_AutoStart variable which can let\r\n   this plugin start automaticlly.\r\n-- Fix the problem about the Function name which is followed\r\n   by its owner ,such as , the member function of a class.","3":"-- Add the Menu for this plugin which let the user can                   \r\n   start or stop all the functions.\r\n-- Add TTrCodeAssistor_AutoStart variable which can let\r\n   this plugin start automaticlly.\r\n-- Fix the problem about the Function name which is followed\r\n   by its owner ,such as , the member function of a class.","package":"TTrCodeAssistor.vim","4":"TTrCodeAssistor.vim","src_id":"6627","5":"6627","creation_date":"1169149860","6":"1169149860"},{"0":"1754","vim_version":"7.0","1":"7.0","script_version":"3.1","2":"3.1","version_comment":"-- Add the function for key ')' , make it intelligent on whether to insert himself or just more to the next ')'\r\n-- Remove the <end> label from the function prototype completation , which is replace by the function of key ' )'","3":"-- Add the function for key ')' , make it intelligent on whether to insert himself or just more to the next ')'\r\n-- Remove the <end> label from the function prototype completation , which is replace by the function of key ' )'","package":"TTrCodeAssistor.vim","4":"TTrCodeAssistor.vim","src_id":"6618","5":"6618","creation_date":"1169003720","6":"1169003720"},{"0":"1754","vim_version":"7.0","1":"7.0","script_version":"3.0","2":"3.0","version_comment":"-- Add the expand \"main\"\r\n-- Make the key '(' to have the ability to complete the function prototype according to you tag files\r\n\r\nEnjoy it yourself.!! ;o)","3":"-- Add the expand \"main\"\r\n-- Make the key '(' to have the ability to complete the function prototype according to you tag files\r\n\r\nEnjoy it yourself.!! ;o)","package":"TTrCodeAssistor.vim","4":"TTrCodeAssistor.vim","src_id":"6615","5":"6615","creation_date":"1168913657","6":"1168913657"},{"0":"1754","vim_version":"7.0","1":"7.0","script_version":"2.0","2":"2.0","version_comment":" Modify the main process to make it clear. Add sulotion to the <for> to replace the += 1 or += -1 to += and -- . Add new expand word while modifying some expands to make it more convenient.","3":" Modify the main process to make it clear. Add sulotion to the <for> to replace the += 1 or += -1 to += and -- . Add new expand word while modifying some expands to make it more convenient.","package":"TTrCodeAssistor.vim","4":"TTrCodeAssistor.vim","src_id":"6591","5":"6591","creation_date":"1168215317","6":"1168215317"},{"0":"1754","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"TTrCodeAssistor.vim","4":"TTrCodeAssistor.vim","src_id":"6581","5":"6581","creation_date":"1167877258","6":"1167877258"}]},"1753":{"script_id":"1753","0":"1753","script_name":"surrparen","1":"surrparen","script_type":"syntax","2":"syntax","summary":"Hilights a pair of parens\/braces that surround the cursor","3":"Hilights a pair of parens\/braces that surround the cursor","description":"The surrparen plugin hilights a pair of parens\/braces that surround\r\nthe cursor position automatically. Unlike the matchparen.vim, it works \r\neven when the cursor is not just on a paren\/brace.\r\nIt's useful especially for texts that have many parens like lisp source.","4":"The surrparen plugin hilights a pair of parens\/braces that surround\r\nthe cursor position automatically. Unlike the matchparen.vim, it works \r\neven when the cursor is not just on a paren\/brace.\r\nIt's useful especially for texts that have many parens like lisp source.","install_details":"Just put it in your .vim\/plugin directory.\r\n","5":"Just put it in your .vim\/plugin directory.\r\n","first_name":"Shotaro","6":"Shotaro","last_name":"Aoyama","7":"Aoyama","releases":[{"0":"1753","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"surrparen.vim","4":"surrparen.vim","src_id":"6579","5":"6579","creation_date":"1167819871","6":"1167819871"}]},"1752":{"script_id":"1752","0":"1752","script_name":"kib_plastic","1":"kib_plastic","script_type":"color scheme","2":"color scheme","summary":"My second theme for Python editing.","3":"My second theme for Python editing.","description":"A new theme, relaxing with pale color scheme.\r\n\r\nI was not aware that Dmitry Vasiliev wrote an additional python syntax file for Vim, the next versions of the theme will try to use it.\r\n\r\nOnce again, a the script and a screenshot can be seen here :\r\nhttp:\/\/kib2.free.fr\/documents\/Vim\/\r\n\r\nDon't forget to rate it, please.\r\n\r\n","4":"A new theme, relaxing with pale color scheme.\r\n\r\nI was not aware that Dmitry Vasiliev wrote an additional python syntax file for Vim, the next versions of the theme will try to use it.\r\n\r\nOnce again, a the script and a screenshot can be seen here :\r\nhttp:\/\/kib2.free.fr\/documents\/Vim\/\r\n\r\nDon't forget to rate it, please.\r\n\r\n","install_details":"Put this file into your Vim's \"colors\" directory.","5":"Put this file into your Vim's \"colors\" directory.","first_name":"Kibleur","6":"Kibleur","last_name":"Christophe","7":"Christophe","releases":[{"0":"1752","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"kib_plastic.vim","4":"kib_plastic.vim","src_id":"6576","5":"6576","creation_date":"1167801585","6":"1167801585"}]},"1751":{"script_id":"1751","0":"1751","script_name":"tGpg","1":"tGpg","script_type":"utility","2":"utility","summary":"Yet another plugin for encrypting files with gpg","3":"Yet another plugin for encrypting files with gpg","description":"This plugin currently can do the following:\r\n    - encrypt symmetrically\r\n    - encrypt asymmetrically\r\n    - clearsign buffer contents\r\n\r\nI couldn't get any of the existing gpg plugins to work properly (windows \r\nGvim & cygwin gpg) and do all the things I wanted it to do, so I wrote \r\nthis one. The main purpose is to perform symmetric encryption (the \r\ndefault) but it's flexible enough to do also clearsign and asymmetric \r\nencryption. Depending on your version of gpg, this script could also \r\nbe used as some kind of password safe.\r\n\r\nYou can set g:tgpgMode or b:tgpgMode to 'encrypt' for switching to \r\nasymmetric encryption as default. You can also control the use of \r\nsymmetric and asymmetric encryption by setting set \r\ng:tgpgPattern_symmetric and g:tgpgPattern_encrypt.\r\n\r\nThis plugin passes the passphrase on the command line to the gpg \r\nprogramm. So, it could be possible that somebody makes the passphrase \r\nshow up in some command log. Under some circumstances it could also be \r\npossible that some info (eg the recipients) is logged in your viminfo \r\nfile. If you clearsign a message, the plain text will be written to \r\ndisk. Ie, if you clearsign a gpg encrypted message, the text will \r\ntemporarily be written to disk as plain text -- please keep in mind the \r\nvast range of possible consequences.\r\n\r\nThis plugin uses the (Buf|File)(Read|Write)Cmd autocommand events to \r\nwrite\/read the file. I'm not sure how this works out with other plugins \r\nusing these events.\r\n\r\nAs I don't like typing passphrases, this plugin caches all the \r\npassphrases entered in a script local variable. This means that \r\npassphrases are likely to be written to the swapfile, from where \r\nsomebody somehow could possibly do something ... Set g:tgpgCachePW to 1 \r\n(buffer-wise caching only) or 0 (no caching) to change this.\r\n\r\nThis plugin was tested with Windows GVim & cygwin gpg 1.4.5 (using bash \r\nas shell) as well as linux vim & gpg 1.4.5. It's possible that the use \r\nof a pure Windows version of gpg or cmd.exe as shell doesn't work. \r\n(Please report problems.)\r\n\r\nIf you get a message telling you about gpg command line options instead \r\nof the decrypted file, please check the value of g:tgpgShellQuote.\r\n\r\nIf writing fails, it's possible that you end up with a corrupted or \r\nempty file. That's why we make backups by default. Set g:tgpgBackup \r\nto 0 to change this.\r\n","4":"This plugin currently can do the following:\r\n    - encrypt symmetrically\r\n    - encrypt asymmetrically\r\n    - clearsign buffer contents\r\n\r\nI couldn't get any of the existing gpg plugins to work properly (windows \r\nGvim & cygwin gpg) and do all the things I wanted it to do, so I wrote \r\nthis one. The main purpose is to perform symmetric encryption (the \r\ndefault) but it's flexible enough to do also clearsign and asymmetric \r\nencryption. Depending on your version of gpg, this script could also \r\nbe used as some kind of password safe.\r\n\r\nYou can set g:tgpgMode or b:tgpgMode to 'encrypt' for switching to \r\nasymmetric encryption as default. You can also control the use of \r\nsymmetric and asymmetric encryption by setting set \r\ng:tgpgPattern_symmetric and g:tgpgPattern_encrypt.\r\n\r\nThis plugin passes the passphrase on the command line to the gpg \r\nprogramm. So, it could be possible that somebody makes the passphrase \r\nshow up in some command log. Under some circumstances it could also be \r\npossible that some info (eg the recipients) is logged in your viminfo \r\nfile. If you clearsign a message, the plain text will be written to \r\ndisk. Ie, if you clearsign a gpg encrypted message, the text will \r\ntemporarily be written to disk as plain text -- please keep in mind the \r\nvast range of possible consequences.\r\n\r\nThis plugin uses the (Buf|File)(Read|Write)Cmd autocommand events to \r\nwrite\/read the file. I'm not sure how this works out with other plugins \r\nusing these events.\r\n\r\nAs I don't like typing passphrases, this plugin caches all the \r\npassphrases entered in a script local variable. This means that \r\npassphrases are likely to be written to the swapfile, from where \r\nsomebody somehow could possibly do something ... Set g:tgpgCachePW to 1 \r\n(buffer-wise caching only) or 0 (no caching) to change this.\r\n\r\nThis plugin was tested with Windows GVim & cygwin gpg 1.4.5 (using bash \r\nas shell) as well as linux vim & gpg 1.4.5. It's possible that the use \r\nof a pure Windows version of gpg or cmd.exe as shell doesn't work. \r\n(Please report problems.)\r\n\r\nIf you get a message telling you about gpg command line options instead \r\nof the decrypted file, please check the value of g:tgpgShellQuote.\r\n\r\nIf writing fails, it's possible that you end up with a corrupted or \r\nempty file. That's why we make backups by default. Set g:tgpgBackup \r\nto 0 to change this.\r\n","install_details":"Copy to ~\/.vim\/plugin\/ or similar.\r\n\r\nThis plugin currently is somewhat experimental. Don't blame me if you end up with a file you can't decrypt anymore.\r\n\r\nYou might also want to try vimscript#661 if you don't like this plugin.\r\n\r\n\r\nAlso available via git\r\nhttp:\/\/github.com\/tomtom\/tgpg_vim","5":"Copy to ~\/.vim\/plugin\/ or similar.\r\n\r\nThis plugin currently is somewhat experimental. Don't blame me if you end up with a file you can't decrypt anymore.\r\n\r\nYou might also want to try vimscript#661 if you don't like this plugin.\r\n\r\n\r\nAlso available via git\r\nhttp:\/\/github.com\/tomtom\/tgpg_vim","first_name":"Tom","6":"Tom","last_name":"Link","7":"Link","releases":[{"0":"1751","vim_version":"7.0","1":"7.0","script_version":"0.4","2":"0.4","version_comment":"\/bb- Reset cached passwords after g:tgpg_timeout seconds without access\r\n- If g:tgpg_gpg_md5_sum is set, check gpg's checksum via \r\ng:tgpg_gpg_md5_check before doing anything.\r\n- The gpg program must be configured via g:tgpg_gpg_cmd.\r\n- Make sure certain options (e.g., verbosefile, verbose) are set to \r\npredefined values during read\/write, see g:tgpg_options.\r\n- Reset registers when unloading the buffer (this should prevent \r\ninformation copied to the clipboard to be written to the viminfo file; \r\nas it may have unintended consequences, you can turn it off by setting \r\ng:tgpg_registers to '')\r\n- randomized replacement tables for encryption\r\n","3":"\/bb- Reset cached passwords after g:tgpg_timeout seconds without access\r\n- If g:tgpg_gpg_md5_sum is set, check gpg's checksum via \r\ng:tgpg_gpg_md5_check before doing anything.\r\n- The gpg program must be configured via g:tgpg_gpg_cmd.\r\n- Make sure certain options (e.g., verbosefile, verbose) are set to \r\npredefined values during read\/write, see g:tgpg_options.\r\n- Reset registers when unloading the buffer (this should prevent \r\ninformation copied to the clipboard to be written to the viminfo file; \r\nas it may have unintended consequences, you can turn it off by setting \r\ng:tgpg_registers to '')\r\n- randomized replacement tables for encryption\r\n","package":"tgpg.vba.gz","4":"tgpg.vba.gz","src_id":"8120","5":"8120","creation_date":"1199423392","6":"1199423392"},{"0":"1751","vim_version":"7.0","1":"7.0","script_version":"0.3","2":"0.3","version_comment":"- Changed command template syntax\r\n- The user is now queried for information only as required by the command template\r\n- Changed default value of g:tgpgTempSuffix\r\n- Removed recipients from the clearsign template\r\n- Make sure we're in the right buffer\r\n- Enable buffer local command line options (eg b:tgpgWrite_symmetric_*_options)\r\n","3":"- Changed command template syntax\r\n- The user is now queried for information only as required by the command template\r\n- Changed default value of g:tgpgTempSuffix\r\n- Removed recipients from the clearsign template\r\n- Make sure we're in the right buffer\r\n- Enable buffer local command line options (eg b:tgpgWrite_symmetric_*_options)\r\n","package":"tGpg.vim","4":"tGpg.vim","src_id":"7234","5":"7234","creation_date":"1181680934","6":"1181680934"},{"0":"1751","vim_version":"7.0","1":"7.0","script_version":"0.2","2":"0.2","version_comment":"- Made the cache a script local variable.\r\n- Let user retype passwords when writing a file with a new or changed passphrase.\r\n- Display a warning if the size of the output file is 0 & revert to old file.\r\n- Keep the original when writing.\r\n- Run BufRead autocommands on filename root after reading the buffer.\r\n","3":"- Made the cache a script local variable.\r\n- Let user retype passwords when writing a file with a new or changed passphrase.\r\n- Display a warning if the size of the output file is 0 & revert to old file.\r\n- Keep the original when writing.\r\n- Run BufRead autocommands on filename root after reading the buffer.\r\n","package":"tGpg.vim","4":"tGpg.vim","src_id":"6574","5":"6574","creation_date":"1167789210","6":"1167789210"},{"0":"1751","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"tGpg.vim","4":"tGpg.vim","src_id":"6571","5":"6571","creation_date":"1167733338","6":"1167733338"}]},"1750":{"script_id":"1750","0":"1750","script_name":"kib_darktango.vim","1":"kib_darktango.vim","script_type":"color scheme","2":"color scheme","summary":"A color scheme based on DarkTango specially for Python editing","3":"A color scheme based on DarkTango specially for Python editing","description":"The color scheme I use to edit all my Python files. \r\nIt is more or less based on DarkTango color scheme.\r\n\r\nSome users told me it was nice with PHP files as well, but I haven't tested with other files than Python and Ruby.\r\n\r\nA screenshot is here :\r\nhttp:\/\/kib2.free.fr\/documents\/Vim\/vim_kib_dark_tango.png\r\n\r\nAll comments are welcome.\r\n","4":"The color scheme I use to edit all my Python files. \r\nIt is more or less based on DarkTango color scheme.\r\n\r\nSome users told me it was nice with PHP files as well, but I haven't tested with other files than Python and Ruby.\r\n\r\nA screenshot is here :\r\nhttp:\/\/kib2.free.fr\/documents\/Vim\/vim_kib_dark_tango.png\r\n\r\nAll comments are welcome.\r\n","install_details":"Put it in your \"colors\" directory","5":"Put it in your \"colors\" directory","first_name":"Kibleur","6":"Kibleur","last_name":"Christophe","7":"Christophe","releases":[{"0":"1750","vim_version":"7.0","1":"7.0","script_version":"0.3","2":"0.3","version_comment":"Initial upload","3":"Initial upload","package":"kib_darktango.vim","4":"kib_darktango.vim","src_id":"6568","5":"6568","creation_date":"1167648502","6":"1167648502"}]},"1749":{"script_id":"1749","0":"1749","script_name":"GotoFileArg.vim","1":"GotoFileArg.vim","script_type":"utility","2":"utility","summary":"Jump right to file in arg list by name, substr, regex","3":"Jump right to file in arg list by name, substr, regex","description":"GotoFileArg.vim v0.9b\r\n\r\nMostly for those who load up VIM with a lot of files at once in the arg list.\r\nWhen jumping around in files, this allows you to jump right to a file, by a\r\nsubstring\/regex of the filename.  It repositions VIM in the arg list so\r\nsubsequent :n :N commands work from the actual location of the file.\r\n\r\nAt present it also maps esc-f as the keystroke to type the filename in.\r\n(esc-f is alt-f \/ meta1-f on my system, and many others).\r\n\r\nFeatures:\r\n  * Filename match is done using \"=~\" so a substring \/ regex are fine\r\n  * Last pattern is remembered\r\n  * If the current filename matches, the search, as one would expect, begins\r\nat the next file, and wraps.\r\n","4":"GotoFileArg.vim v0.9b\r\n\r\nMostly for those who load up VIM with a lot of files at once in the arg list.\r\nWhen jumping around in files, this allows you to jump right to a file, by a\r\nsubstring\/regex of the filename.  It repositions VIM in the arg list so\r\nsubsequent :n :N commands work from the actual location of the file.\r\n\r\nAt present it also maps esc-f as the keystroke to type the filename in.\r\n(esc-f is alt-f \/ meta1-f on my system, and many others).\r\n\r\nFeatures:\r\n  * Filename match is done using \"=~\" so a substring \/ regex are fine\r\n  * Last pattern is remembered\r\n  * If the current filename matches, the search, as one would expect, begins\r\nat the next file, and wraps.\r\n","install_details":"Place file in your plugins dir.\r\nI place it at: ~\/.vim\/plugin\/GotoFileArg.vim","5":"Place file in your plugins dir.\r\nI place it at: ~\/.vim\/plugin\/GotoFileArg.vim","first_name":"B","6":"B","last_name":"Hechinger","7":"Hechinger","releases":[{"0":"1749","vim_version":"5.7","1":"5.7","script_version":"0.9b","2":"0.9b","version_comment":"Initial upload","3":"Initial upload","package":"GotoFileArg.vim","4":"GotoFileArg.vim","src_id":"6566","5":"6566","creation_date":"1167646250","6":"1167646250"}]},"1748":{"script_id":"1748","0":"1748","script_name":"toggle_word.vim","1":"toggle_word.vim","script_type":"utility","2":"utility","summary":"toggles words, ie. turn on into off, true into false, etc.","3":"toggles words, ie. turn on into off, true into false, etc.","description":"Toggles words and preserves case. The words will get converted like this:\r\n\r\n  on -> off\r\n  On -> Off\r\n  ON -> OFF\r\n \r\nany other case gets converted to lowercase, e.g.:\r\n\r\n  tRUe -> false\r\n\r\nInspired from vimscript #1676\r\nAll I really wanted besides what that script did, was the ability to\r\npreserve the case of words.\r\n\r\nUsage:\r\nOnce installed it will give you a ToggleWord() command and will map it by\r\ndefault to \"<leader>t\". All you need to do is position the cursor over the word\r\nyou want to toggle and press \\t in normal or visual mode.\r\n","4":"Toggles words and preserves case. The words will get converted like this:\r\n\r\n  on -> off\r\n  On -> Off\r\n  ON -> OFF\r\n \r\nany other case gets converted to lowercase, e.g.:\r\n\r\n  tRUe -> false\r\n\r\nInspired from vimscript #1676\r\nAll I really wanted besides what that script did, was the ability to\r\npreserve the case of words.\r\n\r\nUsage:\r\nOnce installed it will give you a ToggleWord() command and will map it by\r\ndefault to \"<leader>t\". All you need to do is position the cursor over the word\r\nyou want to toggle and press \\t in normal or visual mode.\r\n","install_details":"Please see INSTALL","5":"Please see INSTALL","first_name":"Alexandru","6":"Alexandru","last_name":"Ungur","7":"Ungur","releases":[{"0":"1748","vim_version":"7.0","1":"7.0","script_version":"1.4","2":"1.4","version_comment":" - Loaded a more comprehensive base dictionary trying to make\r\n   the plugin more useful out of the box. Suggestions for\r\n   adding more entries to the default dictionary are welcome;\r\n\r\n - Changed the way that the user defined (g:toggle_words) \r\n   dictionary works: it now gets merged into the default one,\r\n   so you can simply skip the entries already defined in the\r\n   base dictionary unless you need to override them.\r\n\r\n - Retired the 'ruby' version of the plugin. You can fetch it from v1.3\r\n   if you need it, but no further development will be done on it","3":" - Loaded a more comprehensive base dictionary trying to make\r\n   the plugin more useful out of the box. Suggestions for\r\n   adding more entries to the default dictionary are welcome;\r\n\r\n - Changed the way that the user defined (g:toggle_words) \r\n   dictionary works: it now gets merged into the default one,\r\n   so you can simply skip the entries already defined in the\r\n   base dictionary unless you need to override them.\r\n\r\n - Retired the 'ruby' version of the plugin. You can fetch it from v1.3\r\n   if you need it, but no further development will be done on it","package":"toggle_word.zip","4":"toggle_word.zip","src_id":"8749","5":"8749","creation_date":"1212537020","6":"1212537020"},{"0":"1748","vim_version":"7.0","1":"7.0","script_version":"1.3","2":"1.3","version_comment":" - Refactored the code once again, many thanks to Gary Wright for the beautiful solution \r\n   he suggested for the Ruby version of the plugin,\r\n - Initially introduced the \"Vim7\" version of the plugin which does not depend on +ruby at all,\r\n - Added documentation,\r\n - Changed the default binding from ,t to <leader>t\r\n","3":" - Refactored the code once again, many thanks to Gary Wright for the beautiful solution \r\n   he suggested for the Ruby version of the plugin,\r\n - Initially introduced the \"Vim7\" version of the plugin which does not depend on +ruby at all,\r\n - Added documentation,\r\n - Changed the default binding from ,t to <leader>t\r\n","package":"toggle_word.zip","4":"toggle_word.zip","src_id":"6720","5":"6720","creation_date":"1170653587","6":"1170653587"},{"0":"1748","vim_version":"6.0","1":"6.0","script_version":"1.2","2":"1.2","version_comment":"Refactored the code a little bit","3":"Refactored the code a little bit","package":"toggle_word.vim","4":"toggle_word.vim","src_id":"6603","5":"6603","creation_date":"1168423932","6":"1168423932"},{"0":"1748","vim_version":"6.0","1":"6.0","script_version":"1.1","2":"1.1","version_comment":"Simplified the dictionary format. Now you don't have to worry about quotes,\r\ncommas and square brackets anymore, it's all \"just text\".\r\n","3":"Simplified the dictionary format. Now you don't have to worry about quotes,\r\ncommas and square brackets anymore, it's all \"just text\".\r\n","package":"toggle_word.vim","4":"toggle_word.vim","src_id":"6575","5":"6575","creation_date":"1167794933","6":"1167794933"},{"0":"1748","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"toggle_word.vim","4":"toggle_word.vim","src_id":"6564","5":"6564","creation_date":"1167451970","6":"1167451970"}]},"1747":{"script_id":"1747","0":"1747","script_name":"javascript.vim","1":"javascript.vim","script_type":"syntax","2":"syntax","summary":"javascript highlight","3":"javascript highlight","description":"javascript syntax highlight containing DOM keywords","4":"javascript syntax highlight containing DOM keywords","install_details":"","5":"","first_name":"Carl","6":"Carl","last_name":"F\u00c3\u00bcrstenberg","7":"F\u00c3\u00bcrstenberg","releases":[{"0":"1747","vim_version":"7.0","1":"7.0","script_version":"0.0.1","2":"0.0.1","version_comment":"Initial upload","3":"Initial upload","package":"javascript.vim","4":"javascript.vim","src_id":"6562","5":"6562","creation_date":"1167371587","6":"1167371587"}]},"1746":{"script_id":"1746","0":"1746","script_name":"compiler\/flex.vim","1":"compiler\/flex.vim","script_type":"utility","2":"utility","summary":"Compiler plugin for Adobe Flex 2 compiler","3":"Compiler plugin for Adobe Flex 2 compiler","description":"A simple Vim compiler plugin to run ':make' for Adobe Flex 2 MXML files.\r\nCurrently, it works only with 'mxmlc'.","4":"A simple Vim compiler plugin to run ':make' for Adobe Flex 2 MXML files.\r\nCurrently, it works only with 'mxmlc'.","install_details":"1. Download the script and put it in your ~\/.vim\/compiler\/ directory.\r\n\r\n2. Put this in your ~\/.vimrc:\r\nautocmd BufNewFile,BufRead *.mxml compiler flex\r\n\r\n3. Open an MXML file and run ':make'\r\n\r\n4. Run ':clist' to see list of errors (if any)","5":"1. Download the script and put it in your ~\/.vim\/compiler\/ directory.\r\n\r\n2. Put this in your ~\/.vimrc:\r\nautocmd BufNewFile,BufRead *.mxml compiler flex\r\n\r\n3. Open an MXML file and run ':make'\r\n\r\n4. Run ':clist' to see list of errors (if any)","first_name":"Swaroop","6":"Swaroop","last_name":"C H","7":"C H","releases":[{"0":"1746","vim_version":"6.0","1":"6.0","script_version":"1","2":"1","version_comment":"Initial upload","3":"Initial upload","package":"flex.vim","4":"flex.vim","src_id":"6560","5":"6560","creation_date":"1167343939","6":"1167343939"}]},"1745":{"script_id":"1745","0":"1745","script_name":"amifmt.vim","1":"amifmt.vim","script_type":"syntax","2":"syntax","summary":"Syntax for AmiFormat","3":"Syntax for AmiFormat","description":"http:\/\/orangoo.com\/labs\/AmiNation\/AmiFormat\/","4":"http:\/\/orangoo.com\/labs\/AmiNation\/AmiFormat\/","install_details":"Just drop this script into your ~\/.vim\/syntax\/ directory and run :set syntax=amifmt\r\n","5":"Just drop this script into your ~\/.vim\/syntax\/ directory and run :set syntax=amifmt\r\n","first_name":"Swaroop","6":"Swaroop","last_name":"C H","7":"C H","releases":[{"0":"1745","vim_version":"6.0","1":"6.0","script_version":"1","2":"1","version_comment":"Initial upload","3":"Initial upload","package":"amifmt.vim","4":"amifmt.vim","src_id":"6557","5":"6557","creation_date":"1167284850","6":"1167284850"}]},"1744":{"script_id":"1744","0":"1744","script_name":"nightflight.vim","1":"nightflight.vim","script_type":"color scheme","2":"color scheme","summary":"Yet another dark color scheme; dedicated to Antoine de Saint-Exup\u00c3\u00a9ry","3":"Yet another dark color scheme; dedicated to Antoine de Saint-Exup\u00c3\u00a9ry","description":"\"Perfection is achieved, not when there is nothing more to add, but when there is nothing left to take away.\"\r\n-- Antoine de Saint-Exupery \r\n","4":"\"Perfection is achieved, not when there is nothing more to add, but when there is nothing left to take away.\"\r\n-- Antoine de Saint-Exupery \r\n","install_details":"","5":"","first_name":"Ralf","6":"Ralf","last_name":"Holly","7":"Holly","releases":[{"0":"1744","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"nightflight.vim","4":"nightflight.vim","src_id":"6554","5":"6554","creation_date":"1167254514","6":"1167254514"}]},"1743":{"script_id":"1743","0":"1743","script_name":"vst_with_syn","1":"vst_with_syn","script_type":"utility","2":"utility","summary":"combine of Mikolaj Machowski's VST and Estienne Swart's rest.vim","3":"combine of Mikolaj Machowski's VST and Estienne Swart's rest.vim","description":"Fixed non-broken space bug in chinese environment. (just change scriptencoding to utf-8)\r\nFixed '\\\\' escape bug to make VST more python-restructure like, and the code more clear.\r\nTake Estienne Swart's rest.vim in and make it VST compatible,and fix bugs.\r\n\r\nI would like to send this to Mikolaj Machowski, but I can't contact him. So I upload it here, before Mikolaj Machowski got it :))","4":"Fixed non-broken space bug in chinese environment. (just change scriptencoding to utf-8)\r\nFixed '\\\\' escape bug to make VST more python-restructure like, and the code more clear.\r\nTake Estienne Swart's rest.vim in and make it VST compatible,and fix bugs.\r\n\r\nI would like to send this to Mikolaj Machowski, but I can't contact him. So I upload it here, before Mikolaj Machowski got it :))","install_details":"see VST page","5":"see VST page","first_name":"xuesong","6":"xuesong","last_name":"guo","7":"guo","releases":[{"0":"1743","vim_version":"7.0","1":"7.0","script_version":"1.4.1","2":"1.4.1","version_comment":"Initial upload","3":"Initial upload","package":"vst-v1.4[.1]-and-rest[.1]--bugfixed-for-zhcn-by-oxsama.rar","4":"vst-v1.4[.1]-and-rest[.1]--bugfixed-for-zhcn-by-oxsama.rar","src_id":"6548","5":"6548","creation_date":"1166924680","6":"1166924680"}]},"1742":{"script_id":"1742","0":"1742","script_name":"Utility","1":"Utility","script_type":"utility","2":"utility","summary":"Vertical Copy","3":"Vertical Copy","description":"This is the script which duplicates current  text in current file vertically. \r\n\r\nPlay with beautymargin variable to get desired indentation. \r\n\r\ncan be executed using  command  :call ColCopy()\r\nand you will see that it performs vertical copy.","4":"This is the script which duplicates current  text in current file vertically. \r\n\r\nPlay with beautymargin variable to get desired indentation. \r\n\r\ncan be executed using  command  :call ColCopy()\r\nand you will see that it performs vertical copy.","install_details":"Copy the content of file using CRTL-C or mouse and paste it with VIMRC file.","5":"Copy the content of file using CRTL-C or mouse and paste it with VIMRC file.","first_name":"vijayandra","6":"vijayandra","last_name":"singh","7":"singh","releases":[{"0":"1742","vim_version":"6.0","1":"6.0","script_version":"1.02","2":"1.02","version_comment":"margin being calculated based upon length of longest line rather then fixed.","3":"margin being calculated based upon length of longest line rather then fixed.","package":"vert.txt","4":"vert.txt","src_id":"6549","5":"6549","creation_date":"1166953565","6":"1166953565"}]},"1741":{"script_id":"1741","0":"1741","script_name":"R-MacOSX","1":"R-MacOSX","script_type":"ftplugin","2":"ftplugin","summary":"Evaluate R (www.r-project.org) code from Vim in Mac OS X.","3":"Evaluate R (www.r-project.org) code from Vim in Mac OS X.","description":"Enables you to evaluate code in R (http:\/\/www.r-project.org) via the shell command \"osascript\". Tested on Vim 7.0, R 2.4.0 (GUI 1.17) and Mac OS 10.4.8. Probably should also work on earlier versions.\r\n\r\nEvaluate current line or visual selection with <Cmd-E> and source current file with <Shift-Cmd-E>. The key mappings are inspired by the R GUI internal editor.\r\n\r\nTODO (patches accepted!):\r\n- the key mappings should be customizable","4":"Enables you to evaluate code in R (http:\/\/www.r-project.org) via the shell command \"osascript\". Tested on Vim 7.0, R 2.4.0 (GUI 1.17) and Mac OS 10.4.8. Probably should also work on earlier versions.\r\n\r\nEvaluate current line or visual selection with <Cmd-E> and source current file with <Shift-Cmd-E>. The key mappings are inspired by the R GUI internal editor.\r\n\r\nTODO (patches accepted!):\r\n- the key mappings should be customizable","install_details":"Copy the file \"r.vim\" to the ftplugin directory.","5":"Copy the file \"r.vim\" to the ftplugin directory.","first_name":"Jarimatti","6":"Jarimatti","last_name":"Valkonen","7":"Valkonen","releases":[{"0":"1741","vim_version":"7.0","1":"7.0","script_version":"0.2","2":"0.2","version_comment":"File sourcing now works regardless of the working directory. Also added escaping of the R comment character '#'.","3":"File sourcing now works regardless of the working directory. Also added escaping of the R comment character '#'.","package":"r.vim","4":"r.vim","src_id":"6553","5":"6553","creation_date":"1167196453","6":"1167196453"},{"0":"1741","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"r.vim","4":"r.vim","src_id":"6544","5":"6544","creation_date":"1166867282","6":"1166867282"}]},"1740":{"script_id":"1740","0":"1740","script_name":"filetype.vim","1":"filetype.vim","script_type":"ftplugin","2":"ftplugin","summary":"Maps *.applescript, *.as to applescript, *.plt to gnuplot","3":"Maps *.applescript, *.as to applescript, *.plt to gnuplot","description":"Defines two filetypes:\r\n\r\n*.applescript,*as  --> applescript\r\n*.plt,.gnuplot --> gnuplot\r\n","4":"Defines two filetypes:\r\n\r\n*.applescript,*as  --> applescript\r\n*.plt,.gnuplot --> gnuplot\r\n","install_details":"","5":"","first_name":"James","6":"James","last_name":"Eberle","7":"Eberle","releases":[{"0":"1740","vim_version":"6.0","1":"6.0","script_version":"1.1","2":"1.1","version_comment":"Fixed glob char in list","3":"Fixed glob char in list","package":"filetype.vim","4":"filetype.vim","src_id":"12659","5":"12659","creation_date":"1268949343","6":"1268949343"},{"0":"1740","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"filetype.vim","4":"filetype.vim","src_id":"6541","5":"6541","creation_date":"1166783004","6":"1166783004"}]},"1739":{"script_id":"1739","0":"1739","script_name":"Info.plist","1":"Info.plist","script_type":"utility","2":"utility","summary":"Mac OS X Property List for file type bindings to vim","3":"Mac OS X Property List for file type bindings to vim","description":"This is a companion file to the RunVim.applescript file. Finder and LaunchServices use this file to map file types to their corresponding applications.\r\n\r\nFull details on: http:\/\/www.fastnlight.com\/runvim","4":"This is a companion file to the RunVim.applescript file. Finder and LaunchServices use this file to map file types to their corresponding applications.\r\n\r\nFull details on: http:\/\/www.fastnlight.com\/runvim","install_details":"","5":"","first_name":"James","6":"James","last_name":"Eberle","7":"Eberle","releases":[{"0":"1739","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"Info.plist","4":"Info.plist","src_id":"6540","5":"6540","creation_date":"1166782655","6":"1166782655"}]},"1738":{"script_id":"1738","0":"1738","script_name":"RunVim.applescript","1":"RunVim.applescript","script_type":"utility","2":"utility","summary":"AppleScript to launch vim w\/in Terminal (Mac OS X)","3":"AppleScript to launch vim w\/in Terminal (Mac OS X)","description":"Script to launch command-line vim w\/in Terminal.\r\nFor full details & Xcode project, see http:\/\/www.fastnlight.com\/runvim\r\nNote, must be built w\/ Xcode\/AppleScript Studio project. Requires InterfaceBuilder .nib bindings & Info.plist.","4":"Script to launch command-line vim w\/in Terminal.\r\nFor full details & Xcode project, see http:\/\/www.fastnlight.com\/runvim\r\nNote, must be built w\/ Xcode\/AppleScript Studio project. Requires InterfaceBuilder .nib bindings & Info.plist.","install_details":"","5":"","first_name":"James","6":"James","last_name":"Eberle","7":"Eberle","releases":[{"0":"1738","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"RunVim.applescript","4":"RunVim.applescript","src_id":"6539","5":"6539","creation_date":"1166782297","6":"1166782297"}]},"1737":{"script_id":"1737","0":"1737","script_name":"gnuplot.vim","1":"gnuplot.vim","script_type":"syntax","2":"syntax","summary":"Syntax highlighting for Gnuplot","3":"Syntax highlighting for Gnuplot","description":"Syntax file for Gnuplot.\r\nRequires local ~\/.vim\/filetype.vim.\r\nMore details on http:\/\/www.fastnlight.com\/syntax\r\n","4":"Syntax file for Gnuplot.\r\nRequires local ~\/.vim\/filetype.vim.\r\nMore details on http:\/\/www.fastnlight.com\/syntax\r\n","install_details":"See\r\n  :help mysyntaxfile\r\n  :help new-filetype ","5":"See\r\n  :help mysyntaxfile\r\n  :help new-filetype ","first_name":"James","6":"James","last_name":"Eberle","7":"Eberle","releases":[{"0":"1737","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"gnuplot.vim","4":"gnuplot.vim","src_id":"6538","5":"6538","creation_date":"1166781640","6":"1166781640"}]},"1736":{"script_id":"1736","0":"1736","script_name":"applescript.vim","1":"applescript.vim","script_type":"syntax","2":"syntax","summary":"Syntax highlighting for AppleScript","3":"Syntax highlighting for AppleScript","description":"Syntax file for AppleScript. Requires local ~\/.vim\/filetype.vim. More details on http:\/\/www.fastnlight.com\/syntax","4":"Syntax file for AppleScript. Requires local ~\/.vim\/filetype.vim. More details on http:\/\/www.fastnlight.com\/syntax","install_details":"See\r\n  :help mysyntaxfile\r\n  :help new-filetype\r\n","5":"See\r\n  :help mysyntaxfile\r\n  :help new-filetype\r\n","first_name":"James","6":"James","last_name":"Eberle","7":"Eberle","releases":[{"0":"1736","vim_version":"6.0","1":"6.0","script_version":"1.1","2":"1.1","version_comment":"Added \"#\" for new end-of-line comment character","3":"Added \"#\" for new end-of-line comment character","package":"applescript.vim","4":"applescript.vim","src_id":"12658","5":"12658","creation_date":"1268949259","6":"1268949259"},{"0":"1736","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"applescript.vim","4":"applescript.vim","src_id":"6537","5":"6537","creation_date":"1166781275","6":"1166781275"}]},"1735":{"script_id":"1735","0":"1735","script_name":"echofunc.vim","1":"echofunc.vim","script_type":"utility","2":"utility","summary":"Echo the function declaration in the command line for C\/C++.","3":"Echo the function declaration in the command line for C\/C++.","description":"Get the latest version from github: \r\nhttps:\/\/github.com\/mbbill\/echofunc\r\n                   \r\n File:         echofunc.vim                                            \r\n Brief:        Echo the function declaration in                        \r\n               the command line for C\/C++, as well                     \r\n               as other languages that ctags                           \r\n               supports.                                               \r\n Authors:      Ming Bai <mbbill AT gmail DOT com>,                     \r\n               Wu Yongwei <wuyongwei AT gmail DOT com>                                                          \r\n                                                                       \r\n Install:      1. Put echofunc.vim to \/plugin directory.               \r\n               2. Use the command below to create tags                 \r\n                  file including the language and                      \r\n                  signature fields.                                    \r\n                    ctags -R --fields=+lS .                            \r\n                                                                       \r\n Usage:        When you type '(' after a function name                 \r\n               in insert mode, the function declaration                \r\n               will be displayed in the command line                   \r\n               automatically. Then you may use Alt+- and               \r\n               Alt+= (configurable via EchoFuncKeyPrev                 \r\n               and EchoFuncKeyNext) to cycle between                   \r\n               function declarations (if exists).                      \r\n                                                                       \r\n               Another feature is to provide a balloon tip             \r\n               when the mouse cursor hovers a function name,           \r\n               macro name, etc. This works with when                   \r\n               +balloon_eval is compiled in.                           \r\n                                                                       \r\n               Because the message line often cleared by               \r\n               some other plugins (e.g. ominicomplete), an             \r\n               other choice is to show message in status line.         \r\n               First, add  %{EchoFuncGetStatusLine()}  to              \r\n               your 'statusline' option.                               \r\n               Second, add the following line to your vimrc            \r\n               let g:EchoFuncShowOnStatus = 1                          \r\n               to avoid echoing function name in message line.         \r\n                                                                       \r\n Options:      g:EchoFuncLangsDict                                     \r\n                 Dictionary to map the Vim file types to               \r\n                 tags languages that should be used. You do            \r\n                 not need to touch it in most cases.                   \r\n                                                                       \r\n               g:EchoFuncLangsUsed                                     \r\n                 File types to enable echofunc, in case you            \r\n                 do not want to use EchoFunc on all file               \r\n                 types supported. Example:                             \r\n                   let g:EchoFuncLangsUsed = [\"java\",\"cpp\"]            \r\n                                                                       \r\n               g:EchoFuncMaxBalloonDeclarations                        \r\n                 Maximum lines to display in balloon declarations.     \r\n                                                                       \r\n               g:EchoFuncKeyNext                                       \r\n                 Key to echo the next function.                        \r\n                                                                       \r\n               g:EchoFuncKeyPrev                                       \r\n                 Key to echo the previous function.                    \r\n                                                                       \r\n               g:EchoFuncShowOnStatus                                  \r\n                 Show function name on status line. NOTE,              \r\n                 you should manually add %{EchoFuncGetStatusLine()}    \r\n                 to your 'statusline' option.                          \r\n                                                                       \r\n               g:EchoFuncAutoStartBalloonDeclaration                   \r\n                 Automatically start balloon declaration if not 0.     \r\n                                                                       \r\n               g:EchoFuncPathMappingEnabled                            \r\n               g:EchoFuncPathMapping                                   \r\n                 The new feature added by Zhao Cai provides ability    \r\n                 to shorten file path in some specific directory. e.g. \r\n                 \/home\/username\/veryveryvery\/long\/file\/path\/blabla     \r\n                 could be showed as                                    \r\n                 ~\/veryveryvery\/long\/file\/path\/blabla                  \r\n                 If you want to disable this feature, add              \r\n                 let g:EchoFuncPathMappingEnabled = 0                  \r\n                 to your vimrc. It's enabled by default.               \r\n                 To add more mappings in g:EchoFuncPathMapping, search \r\n                 this script and you will know how to do it.           \r\n                                                                       \r\n                                                                       \r\n Thanks:       edyfox                                                  \r\n               minux                                                   \r\n               Zhao Cai                                                \r\n\r\n\r\n\r\nScreenshots:\r\nhttps:\/\/sites.google.com\/site\/mbbill\/echofunc_demo1.png\r\nhttps:\/\/sites.google.com\/site\/mbbill\/echofunc_demo2.png\r\nhttp:\/\/sites.google.com\/site\/mbbill\/echofunc.PNG","4":"Get the latest version from github: \r\nhttps:\/\/github.com\/mbbill\/echofunc\r\n                   \r\n File:         echofunc.vim                                            \r\n Brief:        Echo the function declaration in                        \r\n               the command line for C\/C++, as well                     \r\n               as other languages that ctags                           \r\n               supports.                                               \r\n Authors:      Ming Bai <mbbill AT gmail DOT com>,                     \r\n               Wu Yongwei <wuyongwei AT gmail DOT com>                                                          \r\n                                                                       \r\n Install:      1. Put echofunc.vim to \/plugin directory.               \r\n               2. Use the command below to create tags                 \r\n                  file including the language and                      \r\n                  signature fields.                                    \r\n                    ctags -R --fields=+lS .                            \r\n                                                                       \r\n Usage:        When you type '(' after a function name                 \r\n               in insert mode, the function declaration                \r\n               will be displayed in the command line                   \r\n               automatically. Then you may use Alt+- and               \r\n               Alt+= (configurable via EchoFuncKeyPrev                 \r\n               and EchoFuncKeyNext) to cycle between                   \r\n               function declarations (if exists).                      \r\n                                                                       \r\n               Another feature is to provide a balloon tip             \r\n               when the mouse cursor hovers a function name,           \r\n               macro name, etc. This works with when                   \r\n               +balloon_eval is compiled in.                           \r\n                                                                       \r\n               Because the message line often cleared by               \r\n               some other plugins (e.g. ominicomplete), an             \r\n               other choice is to show message in status line.         \r\n               First, add  %{EchoFuncGetStatusLine()}  to              \r\n               your 'statusline' option.                               \r\n               Second, add the following line to your vimrc            \r\n               let g:EchoFuncShowOnStatus = 1                          \r\n               to avoid echoing function name in message line.         \r\n                                                                       \r\n Options:      g:EchoFuncLangsDict                                     \r\n                 Dictionary to map the Vim file types to               \r\n                 tags languages that should be used. You do            \r\n                 not need to touch it in most cases.                   \r\n                                                                       \r\n               g:EchoFuncLangsUsed                                     \r\n                 File types to enable echofunc, in case you            \r\n                 do not want to use EchoFunc on all file               \r\n                 types supported. Example:                             \r\n                   let g:EchoFuncLangsUsed = [\"java\",\"cpp\"]            \r\n                                                                       \r\n               g:EchoFuncMaxBalloonDeclarations                        \r\n                 Maximum lines to display in balloon declarations.     \r\n                                                                       \r\n               g:EchoFuncKeyNext                                       \r\n                 Key to echo the next function.                        \r\n                                                                       \r\n               g:EchoFuncKeyPrev                                       \r\n                 Key to echo the previous function.                    \r\n                                                                       \r\n               g:EchoFuncShowOnStatus                                  \r\n                 Show function name on status line. NOTE,              \r\n                 you should manually add %{EchoFuncGetStatusLine()}    \r\n                 to your 'statusline' option.                          \r\n                                                                       \r\n               g:EchoFuncAutoStartBalloonDeclaration                   \r\n                 Automatically start balloon declaration if not 0.     \r\n                                                                       \r\n               g:EchoFuncPathMappingEnabled                            \r\n               g:EchoFuncPathMapping                                   \r\n                 The new feature added by Zhao Cai provides ability    \r\n                 to shorten file path in some specific directory. e.g. \r\n                 \/home\/username\/veryveryvery\/long\/file\/path\/blabla     \r\n                 could be showed as                                    \r\n                 ~\/veryveryvery\/long\/file\/path\/blabla                  \r\n                 If you want to disable this feature, add              \r\n                 let g:EchoFuncPathMappingEnabled = 0                  \r\n                 to your vimrc. It's enabled by default.               \r\n                 To add more mappings in g:EchoFuncPathMapping, search \r\n                 this script and you will know how to do it.           \r\n                                                                       \r\n                                                                       \r\n Thanks:       edyfox                                                  \r\n               minux                                                   \r\n               Zhao Cai                                                \r\n\r\n\r\n\r\nScreenshots:\r\nhttps:\/\/sites.google.com\/site\/mbbill\/echofunc_demo1.png\r\nhttps:\/\/sites.google.com\/site\/mbbill\/echofunc_demo2.png\r\nhttp:\/\/sites.google.com\/site\/mbbill\/echofunc.PNG","install_details":"1. Put echofunc.vim to \/plugin directory.\r\n2. Use the command below to create tags\r\n   file including the language and\r\n   signature fields.\r\n     ctags -R --fields=+lS .\r\n","5":"1. Put echofunc.vim to \/plugin directory.\r\n2. Use the command below to create tags\r\n   file including the language and\r\n   signature fields.\r\n     ctags -R --fields=+lS .\r\n","first_name":"Ming","6":"Ming","last_name":"Bai","7":"Bai","releases":[{"0":"1735","vim_version":"7.0","1":"7.0","script_version":"2.0","2":"2.0","version_comment":"Set and restore cpoptions to make sure line continuation works","3":"Set and restore cpoptions to make sure line continuation works","package":"echofunc.vim","4":"echofunc.vim","src_id":"17383","5":"17383","creation_date":"1328359375","6":"1328359375"},{"0":"1735","vim_version":"7.0","1":"7.0","script_version":"1.23","2":"1.23","version_comment":"Accumulated changes:\r\n- Improve support for C++;\r\n- Add new option to show function name on status line;\r\n- Add new option to enable\/disable autostart of balloon declaration.","3":"Accumulated changes:\r\n- Improve support for C++;\r\n- Add new option to show function name on status line;\r\n- Add new option to enable\/disable autostart of balloon declaration.","package":"echofunc.vim","4":"echofunc.vim","src_id":"15953","5":"15953","creation_date":"1308745854","6":"1308745854"},{"0":"1735","vim_version":"7.0","1":"7.0","script_version":"1.19","2":"1.19","version_comment":"Fix compatibility issues with Ctrl-v I and some other plugins.","3":"Fix compatibility issues with Ctrl-v I and some other plugins.","package":"echofunc.vim","4":"echofunc.vim","src_id":"10501","5":"10501","creation_date":"1241141881","6":"1241141881"},{"0":"1735","vim_version":"7.0","1":"7.0","script_version":"1.18","2":"1.18","version_comment":"Work around a problem that matchparen is not in effect.","3":"Work around a problem that matchparen is not in effect.","package":"echofunc.vim","4":"echofunc.vim","src_id":"8087","5":"8087","creation_date":"1198648040","6":"1198648040"},{"0":"1735","vim_version":"7.0","1":"7.0","script_version":"1.17","2":"1.17","version_comment":"Fix a key mapping conflict with omni-completion (thanks to Edward L. Fox and Ben Schmidt).","3":"Fix a key mapping conflict with omni-completion (thanks to Edward L. Fox and Ben Schmidt).","package":"echofunc.vim","4":"echofunc.vim","src_id":"7992","5":"7992","creation_date":"1196062533","6":"1196062533"},{"0":"1735","vim_version":"7.0","1":"7.0","script_version":"1.16","2":"1.16","version_comment":"- Make the keys for Next-Function and Previous-Function configurable.\r\n- Make small enhancements.","3":"- Make the keys for Next-Function and Previous-Function configurable.\r\n- Make small enhancements.","package":"echofunc.vim","4":"echofunc.vim","src_id":"7890","5":"7890","creation_date":"1194412764","6":"1194412764"},{"0":"1735","vim_version":"7.0","1":"7.0","script_version":"1.14","2":"1.14","version_comment":"Use the tags language field, when it is available, to avoid irrelevant matches.","3":"Use the tags language field, when it is available, to avoid irrelevant matches.","package":"echofunc.vim","4":"echofunc.vim","src_id":"7867","5":"7867","creation_date":"1194030563","6":"1194030563"},{"0":"1735","vim_version":"7.0","1":"7.0","script_version":"1.12","2":"1.12","version_comment":"Add some language-specific support;\r\nImprove the support for languages whose tags do not include a `signature'.","3":"Add some language-specific support;\r\nImprove the support for languages whose tags do not include a `signature'.","package":"echofunc.vim","4":"echofunc.vim","src_id":"7854","5":"7854","creation_date":"1193901210","6":"1193901210"},{"0":"1735","vim_version":"7.0","1":"7.0","script_version":"1.11","2":"1.11","version_comment":"- Display more information about variables, macros, classes, structs, etc.;\r\n- Ensure no leading spaces are ever displayed;\r\n- Compress contiguous space characters to a single SPACE;\r\n- Add new control variable for the maximum number of balloon declarations.","3":"- Display more information about variables, macros, classes, structs, etc.;\r\n- Ensure no leading spaces are ever displayed;\r\n- Compress contiguous space characters to a single SPACE;\r\n- Add new control variable for the maximum number of balloon declarations.","package":"echofunc.vim","4":"echofunc.vim","src_id":"7840","5":"7840","creation_date":"1193536434","6":"1193536434"},{"0":"1735","vim_version":"7.0","1":"7.0","script_version":"1.10","2":"1.10","version_comment":"Fix a typo that can prevent member functions from being correctly echoed.","3":"Fix a typo that can prevent member functions from being correctly echoed.","package":"echofunc.vim","4":"echofunc.vim","src_id":"7814","5":"7814","creation_date":"1192927871","6":"1192927871"},{"0":"1735","vim_version":"7.0","1":"7.0","script_version":"1.9","2":"1.9","version_comment":"Make both the function echo and the balloon tip support C++ destructors and operator redefinitions.","3":"Make both the function echo and the balloon tip support C++ destructors and operator redefinitions.","package":"echofunc.vim","4":"echofunc.vim","src_id":"7801","5":"7801","creation_date":"1192522959","6":"1192522959"},{"0":"1735","vim_version":"7.0","1":"7.0","script_version":"1.8","2":"1.8","version_comment":"- Bug fix: not all functions are shown.\r\n- Bug fix: some operations take very long.\r\n- Improvement: \")\" will finish the function echoing.\r\n- Improvement: new global variable EchoFuncTagsLanguages to control in which file types echofunc will be automatically enabled.\r\n- Improvement: Automatic enabling works also on new files.","3":"- Bug fix: not all functions are shown.\r\n- Bug fix: some operations take very long.\r\n- Improvement: \")\" will finish the function echoing.\r\n- Improvement: new global variable EchoFuncTagsLanguages to control in which file types echofunc will be automatically enabled.\r\n- Improvement: Automatic enabling works also on new files.","package":"echofunc.vim","4":"echofunc.vim","src_id":"7758","5":"7758","creation_date":"1191631981","6":"1191631981"},{"0":"1735","vim_version":"7.0","1":"7.0","script_version":"1.6","2":"1.6","version_comment":"Check file type when starting echo function name or pop a balloon.","3":"Check file type when starting echo function name or pop a balloon.","package":"echofunc.vim","4":"echofunc.vim","src_id":"7475","5":"7475","creation_date":"1186603940","6":"1186603940"},{"0":"1735","vim_version":"7.0","1":"7.0","script_version":"1.4","2":"1.4","version_comment":"Bug fix","3":"Bug fix","package":"echofunc.vim","4":"echofunc.vim","src_id":"7433","5":"7433","creation_date":"1185848917","6":"1185848917"},{"0":"1735","vim_version":"7.0","1":"7.0","script_version":"1.3","2":"1.3","version_comment":"Bug fix.","3":"Bug fix.","package":"echofunc.vim","4":"echofunc.vim","src_id":"7395","5":"7395","creation_date":"1185149103","6":"1185149103"},{"0":"1735","vim_version":"7.0","1":"7.0","script_version":"1.2","2":"1.2","version_comment":"It now support popping out a balloon to show the declaration of the functions and class members under GVim","3":"It now support popping out a balloon to show the declaration of the functions and class members under GVim","package":"echofunc.vim","4":"echofunc.vim","src_id":"7223","5":"7223","creation_date":"1181378317","6":"1181378317"},{"0":"1735","vim_version":"7.0","1":"7.0","script_version":"1.1","2":"1.1","version_comment":"Initial upload","3":"Initial upload","package":"echofunc.vim","4":"echofunc.vim","src_id":"6532","5":"6532","creation_date":"1166689196","6":"1166689196"}]},"1734":{"script_id":"1734","0":"1734","script_name":"vbugle","1":"vbugle","script_type":"syntax","2":"syntax","summary":"Highlight possibe security bugs","3":"Highlight possibe security bugs","description":"vBugle will highligh possible security bugs in Java\/C\/PHP\/C++\/ASP source code, using the current Bugle list. To get the most recent bug list go to http:\/\/www.cipher.org.uk\/index.php?p=projects\/bugle.project . Very small at the moment but if you want to give more bug regexp submit them at the link above. \r\n\r\n","4":"vBugle will highligh possible security bugs in Java\/C\/PHP\/C++\/ASP source code, using the current Bugle list. To get the most recent bug list go to http:\/\/www.cipher.org.uk\/index.php?p=projects\/bugle.project . Very small at the moment but if you want to give more bug regexp submit them at the link above. \r\n\r\n","install_details":"Put the file into your syntax directory and do : \r\n:runtime! syntax\/vbugle.vim","5":"Put the file into your syntax directory and do : \r\n:runtime! syntax\/vbugle.vim","first_name":"Manos","6":"Manos","last_name":"","7":"","releases":[{"0":"1734","vim_version":"7.0","1":"7.0","script_version":"0.1b","2":"0.1b","version_comment":"more signatures","3":"more signatures","package":"vbugle.vim","4":"vbugle.vim","src_id":"6534","5":"6534","creation_date":"1166705295","6":"1166705295"}]},"1733":{"script_id":"1733","0":"1733","script_name":"aedit","1":"aedit","script_type":"utility","2":"utility","summary":"Advanced Edit","3":"Advanced Edit","description":"Advanced Edit provides convenience commands, shortcuts and completion for programming.\r\nFull documentation at http:\/\/ld.yi.org\/vim\/aedit\/.","4":"Advanced Edit provides convenience commands, shortcuts and completion for programming.\r\nFull documentation at http:\/\/ld.yi.org\/vim\/aedit\/.","install_details":"Place it in the plugins directory","5":"Place it in the plugins directory","first_name":"Little","6":"Little","last_name":"Dragon","7":"Dragon","releases":[{"0":"1733","vim_version":"7.0","1":"7.0","script_version":"0.91","2":"0.91","version_comment":"Additions and tweaks. Added the visual mode M-' command.","3":"Additions and tweaks. Added the visual mode M-' command.","package":"aedit.vim","4":"aedit.vim","src_id":"7603","5":"7603","creation_date":"1188560450","6":"1188560450"},{"0":"1733","vim_version":"7.0","1":"7.0","script_version":"0.9","2":"0.9","version_comment":"Additions and tweaks. XML and MXML templates, M-! command, M-\/ tweaks.","3":"Additions and tweaks. XML and MXML templates, M-! command, M-\/ tweaks.","package":"aedit.vim","4":"aedit.vim","src_id":"7597","5":"7597","creation_date":"1188550044","6":"1188550044"},{"0":"1733","vim_version":"7.0","1":"7.0","script_version":"0.8","2":"0.8","version_comment":"Additions","3":"Additions","package":"aedit.vim","4":"aedit.vim","src_id":"7580","5":"7580","creation_date":"1188396682","6":"1188396682"},{"0":"1733","vim_version":"7.0","1":"7.0","script_version":"0.6","2":"0.6","version_comment":"Bug fixes","3":"Bug fixes","package":"aedit.vim","4":"aedit.vim","src_id":"6652","5":"6652","creation_date":"1169625894","6":"1169625894"},{"0":"1733","vim_version":"7.0","1":"7.0","script_version":"0.5","2":"0.5","version_comment":"Fixed the tag closing bug","3":"Fixed the tag closing bug","package":"aedit.vim","4":"aedit.vim","src_id":"6639","5":"6639","creation_date":"1169429292","6":"1169429292"},{"0":"1733","vim_version":"7.0","1":"7.0","script_version":"0.4","2":"0.4","version_comment":"Bug fixes, tweaks and additions.","3":"Bug fixes, tweaks and additions.","package":"aedit.vim","4":"aedit.vim","src_id":"6587","5":"6587","creation_date":"1168137418","6":"1168137418"},{"0":"1733","vim_version":"7.0","1":"7.0","script_version":"0.3","2":"0.3","version_comment":"Bug fixes and tweaks","3":"Bug fixes and tweaks","package":"aedit.vim","4":"aedit.vim","src_id":"6569","5":"6569","creation_date":"1167718163","6":"1167718163"},{"0":"1733","vim_version":"7.0","1":"7.0","script_version":"0.2","2":"0.2","version_comment":"Added python support and mapped the <Up> and <Down> keys","3":"Added python support and mapped the <Up> and <Down> keys","package":"aedit.vim","4":"aedit.vim","src_id":"6556","5":"6556","creation_date":"1167268641","6":"1167268641"},{"0":"1733","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"aedit.vim","4":"aedit.vim","src_id":"6528","5":"6528","creation_date":"1166577852","6":"1166577852"}]},"1732":{"script_id":"1732","0":"1732","script_name":"rdark","1":"rdark","script_type":"color scheme","2":"color scheme","summary":"A dark colorscheme for the GUI","3":"A dark colorscheme for the GUI","description":"A dark color scheme for the GUI, inspired by the Tango color scheme.\r\nUse vimscript #1571 to take full advantage of the PHP syntax highlighting features.\r\n\r\nScreenshot: http:\/\/ld.yi.org\/vim\/rdark\/\r\n\r\nFeatures:\r\n  - let rdark_current_line = 1 if you want to highlight the current line","4":"A dark color scheme for the GUI, inspired by the Tango color scheme.\r\nUse vimscript #1571 to take full advantage of the PHP syntax highlighting features.\r\n\r\nScreenshot: http:\/\/ld.yi.org\/vim\/rdark\/\r\n\r\nFeatures:\r\n  - let rdark_current_line = 1 if you want to highlight the current line","install_details":"Place it in the colors directory","5":"Place it in the colors directory","first_name":"Little","6":"Little","last_name":"Dragon","7":"Dragon","releases":[{"0":"1732","vim_version":"6.0","1":"6.0","script_version":"0.6","2":"0.6","version_comment":"Additions","3":"Additions","package":"rdark.vim","4":"rdark.vim","src_id":"7293","5":"7293","creation_date":"1182586866","6":"1182586866"},{"0":"1732","vim_version":"7.0","1":"7.0","script_version":"0.5","2":"0.5","version_comment":"Bug fixes","3":"Bug fixes","package":"rdark.vim","4":"rdark.vim","src_id":"6555","5":"6555","creation_date":"1167268444","6":"1167268444"},{"0":"1732","vim_version":"7.0","1":"7.0","script_version":"0.4","2":"0.4","version_comment":"added current line, tabs and tab columns, changed the visual color","3":"added current line, tabs and tab columns, changed the visual color","package":"rdark.vim","4":"rdark.vim","src_id":"6542","5":"6542","creation_date":"1166803038","6":"1166803038"},{"0":"1732","vim_version":"7.0","1":"7.0","script_version":"0.3","2":"0.3","version_comment":"Bug fixes and additions","3":"Bug fixes and additions","package":"rdark.vim","4":"rdark.vim","src_id":"6536","5":"6536","creation_date":"1166774940","6":"1166774940"},{"0":"1732","vim_version":"7.0","1":"7.0","script_version":"0.2","2":"0.2","version_comment":"Added diff colors","3":"Added diff colors","package":"rdark.vim","4":"rdark.vim","src_id":"6523","5":"6523","creation_date":"1166504336","6":"1166504336"},{"0":"1732","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"rdark.vim","4":"rdark.vim","src_id":"6522","5":"6522","creation_date":"1166503204","6":"1166503204"}]},"1731":{"script_id":"1731","0":"1731","script_name":"perlcritic compiler script","1":"perlcritic compiler script","script_type":"utility","2":"utility","summary":"Compiler file for the perlcritic syntax checker","3":"Compiler file for the perlcritic syntax checker","description":"This is a simple compiler script for perlcritic (http:\/\/search.cpan.org\/~thaljef\/Perl-Critic-0.22\/bin\/perlcritic) a tool to critique Perl source.","4":"This is a simple compiler script for perlcritic (http:\/\/search.cpan.org\/~thaljef\/Perl-Critic-0.22\/bin\/perlcritic) a tool to critique Perl source.","install_details":"Install perlcritic (hint: perl -MCPAN -e install Perl::Critic)\r\n\r\nPut perlchecker.vim in $HOME\/.vim\/compiler\/ \r\n\r\nWhen editing a perl script do:\r\n:compiler perlcritic\r\n:make\r\n:cope","5":"Install perlcritic (hint: perl -MCPAN -e install Perl::Critic)\r\n\r\nPut perlchecker.vim in $HOME\/.vim\/compiler\/ \r\n\r\nWhen editing a perl script do:\r\n:compiler perlcritic\r\n:make\r\n:cope","first_name":"Scott","6":"Scott","last_name":"Peshak","7":"Peshak","releases":[{"0":"1731","vim_version":"6.0","1":"6.0","script_version":"0.2","2":"0.2","version_comment":"Initial upload","3":"Initial upload","package":"perlcritic.vim","4":"perlcritic.vim","src_id":"6521","5":"6521","creation_date":"1166494163","6":"1166494163"}]},"1730":{"script_id":"1730","0":"1730","script_name":"tAssert","1":"tAssert","script_type":"utility","2":"utility","summary":"Simple assertions, poor man's contracts for vim script","3":"Simple assertions, poor man's contracts for vim script","description":"This plugin defines a command |:TAssert| that takes an expression as \r\nargument and throws an exception if this expression evaluates to \r\n|empty()|. You can insert these comments throughout your code whenever \r\nsomething could potentially go wrong. The exception is then thrown right \r\nwhere the problem occurs. You could think of it as a poor man's \r\ndesign-by-contract substitute.\r\n\r\nOne goal of this plugin is to allow users to quickly switch on or off \r\nassertions depending on the context. This can be done either by:\r\n\r\n    1. Turning assertions off so that they are not evaluated. This can \r\n       be achieved by setting g:TASSERT to 0 or by calling the command \r\n       |:TAssertOff|.\r\n\r\n    2. Commenting out assertions in the current buffer by calling the \r\n       commmand |:TAssertComment|.\r\n\r\n\r\nExample:\r\n\r\n    fun! Test(a, b)\r\n        TAssertType a:a, 'string'\r\n        TAssertType a:b, 'number'\r\n        TAssert !empty(a:a)\r\n        return repeat(a:a, a:b)\r\n    endf\r\n\r\n\r\nLogging:\r\n\r\nTAssert also includes a few convenience commands for logging. The \r\nvariable g:TLOG controls where messages are written to:\r\n\r\n    echom ... Print messages in the echo area.\r\n    file  ... Print messages to a file; syntax \"file:FILENAME\"\r\n    Decho ... Print messages via Decho (vimscript#642)\r\n","4":"This plugin defines a command |:TAssert| that takes an expression as \r\nargument and throws an exception if this expression evaluates to \r\n|empty()|. You can insert these comments throughout your code whenever \r\nsomething could potentially go wrong. The exception is then thrown right \r\nwhere the problem occurs. You could think of it as a poor man's \r\ndesign-by-contract substitute.\r\n\r\nOne goal of this plugin is to allow users to quickly switch on or off \r\nassertions depending on the context. This can be done either by:\r\n\r\n    1. Turning assertions off so that they are not evaluated. This can \r\n       be achieved by setting g:TASSERT to 0 or by calling the command \r\n       |:TAssertOff|.\r\n\r\n    2. Commenting out assertions in the current buffer by calling the \r\n       commmand |:TAssertComment|.\r\n\r\n\r\nExample:\r\n\r\n    fun! Test(a, b)\r\n        TAssertType a:a, 'string'\r\n        TAssertType a:b, 'number'\r\n        TAssert !empty(a:a)\r\n        return repeat(a:a, a:b)\r\n    endf\r\n\r\n\r\nLogging:\r\n\r\nTAssert also includes a few convenience commands for logging. The \r\nvariable g:TLOG controls where messages are written to:\r\n\r\n    echom ... Print messages in the echo area.\r\n    file  ... Print messages to a file; syntax \"file:FILENAME\"\r\n    Decho ... Print messages via Decho (vimscript#642)\r\n","install_details":"Extract the archive to ~\/.vim or ~\/vimfiles. If g:TASSERT is 0, the impact of \r\nthis script on startup time should be minimal.\r\n\r\nCompatibility:\r\nInsert the following code in files using assertions. This defines a utility function \r\nand makes sure that end users can still use your files without having this \r\nplugin installed: >\r\n\r\n    if !exists(':TAssert')\r\n        command! -nargs=* -bar -bang TAssert :\r\n        command! -nargs=* -bar -bang TAssertType :\r\n    endif\r\n\r\n\r\nAlso available via git\r\nhttp:\/\/github.com\/tomtom\/tassert_vim","5":"Extract the archive to ~\/.vim or ~\/vimfiles. If g:TASSERT is 0, the impact of \r\nthis script on startup time should be minimal.\r\n\r\nCompatibility:\r\nInsert the following code in files using assertions. This defines a utility function \r\nand makes sure that end users can still use your files without having this \r\nplugin installed: >\r\n\r\n    if !exists(':TAssert')\r\n        command! -nargs=* -bar -bang TAssert :\r\n        command! -nargs=* -bar -bang TAssertType :\r\n    endif\r\n\r\n\r\nAlso available via git\r\nhttp:\/\/github.com\/tomtom\/tassert_vim","first_name":"Tom","6":"Tom","last_name":"Link","7":"Link","releases":[{"0":"1730","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"- Incompatible changes galore\r\n- Removed :TAssertToggle, :TAssertBegin & :TAssertEnd etc. that doesn't really belong here.\r\n- :TAssertType command (requires macros\/tassert.vim)\r\n- Moved Is*() functions to macros\/tassert.vim.\r\n","3":"- Incompatible changes galore\r\n- Removed :TAssertToggle, :TAssertBegin & :TAssertEnd etc. that doesn't really belong here.\r\n- :TAssertType command (requires macros\/tassert.vim)\r\n- Moved Is*() functions to macros\/tassert.vim.\r\n","package":"tAssert.vba.gz","4":"tAssert.vba.gz","src_id":"10172","5":"10172","creation_date":"1236778397","6":"1236778397"},{"0":"1730","vim_version":"7.0","1":"7.0","script_version":"0.3","2":"0.3","version_comment":"- IsA(): Can take a list of types as arguments and it provides a way to \r\ncheck dictionaries againt prototypes or interface definitions.\r\n- IsExistent()\r\n- New log-related commands: TLogOn, TLogOff, TLogBufferOn, TLogBufferOff\r\n- Use TAssertVal(script, expr) to evaluate an expression (as \r\nargument to a command) in the script context.\r\n- TAssertOn implies TLogOn\r\n- *Comment & *Uncomment commands now take a range as argument (default: \r\nwhole file).\r\n- TAssertComment! & TAssertUncomment! (with [!]) also call \r\nTLog(Un)Comment.\r\n","3":"- IsA(): Can take a list of types as arguments and it provides a way to \r\ncheck dictionaries againt prototypes or interface definitions.\r\n- IsExistent()\r\n- New log-related commands: TLogOn, TLogOff, TLogBufferOn, TLogBufferOff\r\n- Use TAssertVal(script, expr) to evaluate an expression (as \r\nargument to a command) in the script context.\r\n- TAssertOn implies TLogOn\r\n- *Comment & *Uncomment commands now take a range as argument (default: \r\nwhole file).\r\n- TAssertComment! & TAssertUncomment! (with [!]) also call \r\nTLog(Un)Comment.\r\n","package":"tAssert.vba.gz","4":"tAssert.vba.gz","src_id":"7036","5":"7036","creation_date":"1177823396","6":"1177823396"},{"0":"1730","vim_version":"7.0","1":"7.0","script_version":"0.2","2":"0.2","version_comment":"- More convenience functions\r\n- The convenience functions now display an explanation for a failure\r\n- Convenience commands weren't loaded when g:TASSERT was off.\r\n- Logging to a file & via Decho()\r\n- TAssert! (the one with the bang) doesn't throw an error but simply \r\ndisplays the failure in the log\r\n- s:ResolveSIDs() didn't return a string if s:assertFile wasn't set.\r\n- s:ResolveSIDs() caches scriptnames\r\n- Moved logging code to 00tLog.vim\r\n","3":"- More convenience functions\r\n- The convenience functions now display an explanation for a failure\r\n- Convenience commands weren't loaded when g:TASSERT was off.\r\n- Logging to a file & via Decho()\r\n- TAssert! (the one with the bang) doesn't throw an error but simply \r\ndisplays the failure in the log\r\n- s:ResolveSIDs() didn't return a string if s:assertFile wasn't set.\r\n- s:ResolveSIDs() caches scriptnames\r\n- Moved logging code to 00tLog.vim\r\n","package":"tAssert.zip","4":"tAssert.zip","src_id":"6526","5":"6526","creation_date":"1166525700","6":"1166525700"},{"0":"1730","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"tAssert.zip","4":"tAssert.zip","src_id":"6514","5":"6514","creation_date":"1166008804","6":"1166008804"}]},"1729":{"script_id":"1729","0":"1729","script_name":"exUtility","1":"exUtility","script_type":"utility","2":"utility","summary":"Global search,symbol search,tag track...(Like IDE\/Source Insight)","3":"Global search,symbol search,tag track...(Like IDE\/Source Insight)","description":"The original idea to develop this plugin is to enhance the vim, as an IDE like editor.\r\nThe plugin has the following features:\r\n\r\n    Global Search \r\n        1: Display global search result.\r\n        2: The search result can be edit and batch select into a quick view window. \r\n        3: Display the search result history.\r\n\r\n    Tag Select\r\n        1: Display tag preview and have good ui for user to select tags\r\n        2: Display tag stack and code-line preview for easy pop stack, re-entry stack, re-select tags.Good ui for user to easy track code.\r\n\r\n    Symbol List\r\n        1: Display the symbols based on the tags-file\r\n        2: Pick up symbol pattern and copy it into quick-view window\r\n        3: Symbol tag jump\r\n\r\n    Environment Setting\r\n        1: Automatically generate project\r\n        2: Variable setting\r\n        3: Multi-projects support\r\n                                                *exUtility-Contact*\r\n","4":"The original idea to develop this plugin is to enhance the vim, as an IDE like editor.\r\nThe plugin has the following features:\r\n\r\n    Global Search \r\n        1: Display global search result.\r\n        2: The search result can be edit and batch select into a quick view window. \r\n        3: Display the search result history.\r\n\r\n    Tag Select\r\n        1: Display tag preview and have good ui for user to select tags\r\n        2: Display tag stack and code-line preview for easy pop stack, re-entry stack, re-select tags.Good ui for user to easy track code.\r\n\r\n    Symbol List\r\n        1: Display the symbols based on the tags-file\r\n        2: Pick up symbol pattern and copy it into quick-view window\r\n        3: Symbol tag jump\r\n\r\n    Environment Setting\r\n        1: Automatically generate project\r\n        2: Variable setting\r\n        3: Multi-projects support\r\n                                                *exUtility-Contact*\r\n","install_details":"1.1. Files~\r\n\r\nThe exUtility have these files:\r\n\r\n\tplugin\\exEnvironmentSetting.vim\r\n\t         exGlobalSearch.vim\r\n\t         exSymbolTable.vim\r\n\t         exTagSelect.vim\r\n\t         exWindow.vim\r\n\r\n\tdoc\\exUtility-exEnvironmentSetting.txt \r\n\t      exUtility-exGlobalSearch.txt       \r\n\t      exUtility-exSymbolTable.txt\r\n\t      exUtility-exTagSelect.txt\r\n\t      exUtility-Install.txt\r\n\r\n1.2. Copy the file into your vim-runtime path~\r\n\tcopy all the file into your vim-runtime path\r\n\r\n1.3. After install you should read~\r\n\texUtility have a lot of docments, but don't worry about this. We wrote\r\n\ta quick-start section for user to easy star up the plugin.\r\n\tRead the quick-start section in each doc file first.\r\n\tWe recommend you read them in this order:\r\n\r\n        exUtility-exTagSelect.txt           \r\n        exUtility-exGlobalSearch.txt        \r\n        exUtility-exSymbolTable.txt         \r\n        exUtility-exEnvironmentSetting.txt  \r\n\r\n\r\n==========================================\r\nABOUT US:\r\n\r\nOur goal is to make a easy GNU-tools support Vim.\r\nwe still have a lot of bugs and things to do in exUtility, and we need your\r\nhelp if you love and concern this project.\r\nIf you have any good idea for the exUtility,\r\n\t    any bug reports,\r\n\t    any advises,\r\n\t    any questions,\r\nFeel free to contact us, we will reply your mail asap. We're vim fans\r\n\r\nContact Method:\r\n\tWu Jie: ayacai (AT) 163 (DOT) com\r\n\tYu Jian Rong: YuJianrong (AT) GMail (DOT) com","5":"1.1. Files~\r\n\r\nThe exUtility have these files:\r\n\r\n\tplugin\\exEnvironmentSetting.vim\r\n\t         exGlobalSearch.vim\r\n\t         exSymbolTable.vim\r\n\t         exTagSelect.vim\r\n\t         exWindow.vim\r\n\r\n\tdoc\\exUtility-exEnvironmentSetting.txt \r\n\t      exUtility-exGlobalSearch.txt       \r\n\t      exUtility-exSymbolTable.txt\r\n\t      exUtility-exTagSelect.txt\r\n\t      exUtility-Install.txt\r\n\r\n1.2. Copy the file into your vim-runtime path~\r\n\tcopy all the file into your vim-runtime path\r\n\r\n1.3. After install you should read~\r\n\texUtility have a lot of docments, but don't worry about this. We wrote\r\n\ta quick-start section for user to easy star up the plugin.\r\n\tRead the quick-start section in each doc file first.\r\n\tWe recommend you read them in this order:\r\n\r\n        exUtility-exTagSelect.txt           \r\n        exUtility-exGlobalSearch.txt        \r\n        exUtility-exSymbolTable.txt         \r\n        exUtility-exEnvironmentSetting.txt  \r\n\r\n\r\n==========================================\r\nABOUT US:\r\n\r\nOur goal is to make a easy GNU-tools support Vim.\r\nwe still have a lot of bugs and things to do in exUtility, and we need your\r\nhelp if you love and concern this project.\r\nIf you have any good idea for the exUtility,\r\n\t    any bug reports,\r\n\t    any advises,\r\n\t    any questions,\r\nFeel free to contact us, we will reply your mail asap. We're vim fans\r\n\r\nContact Method:\r\n\tWu Jie: ayacai (AT) 163 (DOT) com\r\n\tYu Jian Rong: YuJianrong (AT) GMail (DOT) com","first_name":"Wu","6":"Wu","last_name":"Jie","7":"Jie","releases":[{"0":"1729","vim_version":"7.0","1":"7.0","script_version":"4.2.0","2":"4.2.0","version_comment":"exUtility-4.2.0~\r\nBug Fix:~\r\n\texGlobaleSearch: <1> fix jump error when the file have been modified.\r\n\texWindow: <1> prevent edit same file when jumping, to prevent a pop-up error message.\r\nAdditional Features:~\r\n\tnone","3":"exUtility-4.2.0~\r\nBug Fix:~\r\n\texGlobaleSearch: <1> fix jump error when the file have been modified.\r\n\texWindow: <1> prevent edit same file when jumping, to prevent a pop-up error message.\r\nAdditional Features:~\r\n\tnone","package":"exUtility-4.2.0.tar","4":"exUtility-4.2.0.tar","src_id":"6516","5":"6516","creation_date":"1166122901","6":"1166122901"},{"0":"1729","vim_version":"7.0","1":"7.0","script_version":"4.1.0","2":"4.1.0","version_comment":"Initial upload","3":"Initial upload","package":"exUtility-4.1.0.tar","4":"exUtility-4.1.0.tar","src_id":"6512","5":"6512","creation_date":"1165964959","6":"1165964959"}]},"1728":{"script_id":"1728","0":"1728","script_name":"sal syntax","1":"sal syntax","script_type":"syntax","2":"syntax","summary":"syntax file for the SAL modeling language","3":"syntax file for the SAL modeling language","description":"SAL (http:\/\/sal.csl.sri.com\/) is a language to specify automata for model checking.  This is a syntax file that can help read the models.","4":"SAL (http:\/\/sal.csl.sri.com\/) is a language to specify automata for model checking.  This is a syntax file that can help read the models.","install_details":"Just untar into your .vim directory and it automatically detects sal files.","5":"Just untar into your .vim directory and it automatically detects sal files.","first_name":"Brandon","6":"Brandon","last_name":"Borkholder","7":"Borkholder","releases":[{"0":"1728","vim_version":"6.0","1":"6.0","script_version":"0.2","2":"0.2","version_comment":"* Made significant changes to the parsing of the language.  I tried to go through the SAL language manual and identify syntax.\r\n* Colors changed slightly","3":"* Made significant changes to the parsing of the language.  I tried to go through the SAL language manual and identify syntax.\r\n* Colors changed slightly","package":"sal.tar.bz2","4":"sal.tar.bz2","src_id":"7780","5":"7780","creation_date":"1192133352","6":"1192133352"},{"0":"1728","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"sal.tar.bz2","4":"sal.tar.bz2","src_id":"6511","5":"6511","creation_date":"1165957494","6":"1165957494"}]},"1727":{"script_id":"1727","0":"1727","script_name":"Templeet","1":"Templeet","script_type":"syntax","2":"syntax","summary":"Syntax file for templeet","3":"Syntax file for templeet","description":"Templeet is an open-source project initiated by Pascal Courtois and Fabien Penso. It allows you to create photo galeries, news systems, personal sites, blogs, etc. Using Templeet, you can generate HTML, CSS, SVG pictures, SMIL, and any kind of text files.\r\n\r\nFor more details, see http:\/\/templeet.org\/index.en.html","4":"Templeet is an open-source project initiated by Pascal Courtois and Fabien Penso. It allows you to create photo galeries, news systems, personal sites, blogs, etc. Using Templeet, you can generate HTML, CSS, SVG pictures, SMIL, and any kind of text files.\r\n\r\nFor more details, see http:\/\/templeet.org\/index.en.html","install_details":"Untar the tarball in your $HOME directory :\r\ncd && tar xvzf Templeet_*.tgz\r\n","5":"Untar the tarball in your $HOME directory :\r\ncd && tar xvzf Templeet_*.tgz\r\n","first_name":"Bruno","6":"Bruno","last_name":"Michel","7":"Michel","releases":[{"0":"1727","vim_version":"7.0","1":"7.0","script_version":"0.1.3","2":"0.1.3","version_comment":"Initial upload","3":"Initial upload","package":"Templeet_0.1.3.tgz","4":"Templeet_0.1.3.tgz","src_id":"6509","5":"6509","creation_date":"1165920135","6":"1165920135"}]},"1726":{"script_id":"1726","0":"1726","script_name":"ruby_imaps","1":"ruby_imaps","script_type":"ftplugin","2":"ftplugin","summary":"Textmate like Ruby snippets for Vim","3":"Textmate like Ruby snippets for Vim","description":"This is (another) snippets script that tries to emulate what I've seen of Textmates snippets feature (I haven't used Textmate, so this assumption is based on rails screencasts I've watched).\r\n\r\nThis uses imaps.vim. A *great* script originally written by Srinath Avadhanula and modified by Benji Fisher. It is part of the latex suite of scripts but I've included it here with Srinaths and Benjis permission. (If you use latexsuite then there is no need to install  the file again).\r\n\r\nI've set maplocalleader to \";\" in ruby_imaps.vim. If you have set it elsewhere then comment out or remove the first line in that script. You can change it to your preferred key if required. All mappings begin with <localleader>.\r\n\r\nHow it works.\r\nSince this is a ruby ftplugin, the mappings will only work if you are editing a .rb file\r\nThe script is nothing more than a collection of imaps that contain '<+  +>' regions. The description of which is probably best illustrated with an example.\r\n\r\nin a .rb file type ' ;tc ' (<localleader>tc) while in insert mode (without the quotes).\r\nthis will expand to:\r\n\r\n---\r\nrequire \"test\/unit\"\r\nrequire \"<+ lib file name +>\"\r\n\r\nclass Test<+ NameOfTestCases +> < Test::Unit:TestCase\r\n  def test_<+ test case name +>\r\n    <++>\r\n  end\r\nend\r\n---\r\n\r\nand <+ lib file name +> should be selected.\r\nIf you start typing the path to the required file it will overwrite <+ lib file name +>.\r\nOnce you've finished, hold the control key and hit 'j' (CTL-j).\r\n\r\nThis is were the magic of imaps.vim happens!\r\n\r\nYou should jump to the next <+ +> section (<+ NameOfTestCases +>)\r\nAgain, replace by simply typing a viable name.\r\nCTL-j again will jump to and select <+ test case name +>\r\nContinue typing replacements and jumping to the next <+ +> region using CTL-j until you've completed the snippet.\r\n\r\nNote: I've specifically written this for ruby (NOT rails). I've intentionally called it ruby_imaps to not only indicate it uses imaps.vim, but hoping that if others liked it and would like to create other ftplugins they might follow the naming convention (python_imaps, perl_imaps etc). Only a suggestion though ;-)\r\n\r\nBrowse through ruby_imaps.vim to see all mappings.\r\nSome others to test are:    ;ama  ;inj0  ;eawi\r\n\r\nI've tried to make the text between the <+ and +> describe what needs to be typed at any particular point.\r\n\r\nAny suggestions or feedback would be greatly appreciated (markonlinux At internode Dot on Dot net)\r\n(For eg I really need to include more do\/ end blocks!)\r\n\r\n\r\n-- \r\nMark","4":"This is (another) snippets script that tries to emulate what I've seen of Textmates snippets feature (I haven't used Textmate, so this assumption is based on rails screencasts I've watched).\r\n\r\nThis uses imaps.vim. A *great* script originally written by Srinath Avadhanula and modified by Benji Fisher. It is part of the latex suite of scripts but I've included it here with Srinaths and Benjis permission. (If you use latexsuite then there is no need to install  the file again).\r\n\r\nI've set maplocalleader to \";\" in ruby_imaps.vim. If you have set it elsewhere then comment out or remove the first line in that script. You can change it to your preferred key if required. All mappings begin with <localleader>.\r\n\r\nHow it works.\r\nSince this is a ruby ftplugin, the mappings will only work if you are editing a .rb file\r\nThe script is nothing more than a collection of imaps that contain '<+  +>' regions. The description of which is probably best illustrated with an example.\r\n\r\nin a .rb file type ' ;tc ' (<localleader>tc) while in insert mode (without the quotes).\r\nthis will expand to:\r\n\r\n---\r\nrequire \"test\/unit\"\r\nrequire \"<+ lib file name +>\"\r\n\r\nclass Test<+ NameOfTestCases +> < Test::Unit:TestCase\r\n  def test_<+ test case name +>\r\n    <++>\r\n  end\r\nend\r\n---\r\n\r\nand <+ lib file name +> should be selected.\r\nIf you start typing the path to the required file it will overwrite <+ lib file name +>.\r\nOnce you've finished, hold the control key and hit 'j' (CTL-j).\r\n\r\nThis is were the magic of imaps.vim happens!\r\n\r\nYou should jump to the next <+ +> section (<+ NameOfTestCases +>)\r\nAgain, replace by simply typing a viable name.\r\nCTL-j again will jump to and select <+ test case name +>\r\nContinue typing replacements and jumping to the next <+ +> region using CTL-j until you've completed the snippet.\r\n\r\nNote: I've specifically written this for ruby (NOT rails). I've intentionally called it ruby_imaps to not only indicate it uses imaps.vim, but hoping that if others liked it and would like to create other ftplugins they might follow the naming convention (python_imaps, perl_imaps etc). Only a suggestion though ;-)\r\n\r\nBrowse through ruby_imaps.vim to see all mappings.\r\nSome others to test are:    ;ama  ;inj0  ;eawi\r\n\r\nI've tried to make the text between the <+ and +> describe what needs to be typed at any particular point.\r\n\r\nAny suggestions or feedback would be greatly appreciated (markonlinux At internode Dot on Dot net)\r\n(For eg I really need to include more do\/ end blocks!)\r\n\r\n\r\n-- \r\nMark","install_details":"Extract the zip archive into your .vim directory on Linux (vimfiles? directory on windows).\r\nimaps.vim should end up in the 'plugin' folder and ruby_imaps.vim in the 'ftplugin' folder\r\n\r\n","5":"Extract the zip archive into your .vim directory on Linux (vimfiles? directory on windows).\r\nimaps.vim should end up in the 'plugin' folder and ruby_imaps.vim in the 'ftplugin' folder\r\n\r\n","first_name":"Mark","6":"Mark","last_name":"Woodward","7":"Woodward","releases":[{"0":"1726","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"ruby_imaps.zip","4":"ruby_imaps.zip","src_id":"6508","5":"6508","creation_date":"1165892958","6":"1165892958"}]},"1725":{"script_id":"1725","0":"1725","script_name":"capslock.vim","1":"capslock.vim","script_type":"utility","2":"utility","summary":"Software Caps Lock","3":"Software Caps Lock","description":"This plugin enables a software caps lock.  This is advantageous over a regular caps lock in that normal mode commands, other buffers, and other applications are unaffected.\r\n\r\nThe default mapping is <C-G>c but if you use this feature regularly, you will probably want a shorter one.  Simply map something to <Plug>CapsLockToggle and you are good to go.  The default behavior is to disable caps lock when leaving insert mode, but this is customizable too.\r\n\r\nA couple of functions are provided for adding a caps lock indicator to the statusline.\r\n\r\nhttps:\/\/github.com\/tpope\/vim-capslock\r\n","4":"This plugin enables a software caps lock.  This is advantageous over a regular caps lock in that normal mode commands, other buffers, and other applications are unaffected.\r\n\r\nThe default mapping is <C-G>c but if you use this feature regularly, you will probably want a shorter one.  Simply map something to <Plug>CapsLockToggle and you are good to go.  The default behavior is to disable caps lock when leaving insert mode, but this is customizable too.\r\n\r\nA couple of functions are provided for adding a caps lock indicator to the statusline.\r\n\r\nhttps:\/\/github.com\/tpope\/vim-capslock\r\n","install_details":"Install capslock.vim in ~\/.vim\/plugin (~\\vimfiles\\plugin on Windows).  For help with configuring the statusline or changing the mappings, read the top of the file.","5":"Install capslock.vim in ~\/.vim\/plugin (~\\vimfiles\\plugin on Windows).  For help with configuring the statusline or changing the mappings, read the top of the file.","first_name":"Tim","6":"Tim","last_name":"Pope","7":"Pope","releases":[{"0":"1725","vim_version":"6.0","1":"6.0","script_version":"1.1","2":"1.1","version_comment":"Initial upload","3":"Initial upload","package":"capslock.vim","4":"capslock.vim","src_id":"6505","5":"6505","creation_date":"1165398788","6":"1165398788"}]},"1724":{"script_id":"1724","0":"1724","script_name":"pyljvim","1":"pyljvim","script_type":"utility","2":"utility","summary":"pyljvim - LiveJournal Plugin for VIM.","3":"pyljvim - LiveJournal Plugin for VIM.","description":"pyljvim is a a Livejournal Plugin for Vim. One can post to the Livejournal  directly from vim! :)\r\n\r\nHow to use pyljvim:\r\n1) Provide Configfile.txt required details and Install it on your platform\r\n2) Two Templates for posting are provided\r\n\r\n:LJTemplate standart\r\n\r\nOR\r\n\r\n:LJTemplate extended\r\n\r\nFill in the details. Subject is a must.\r\n3) Give a Space after those details and type your text to the world at LJ.\r\n4) When you have finished typing it, do a:\r\n\r\n:LJPost\r\n\r\n5) Your post is online.\r\n\r\n-- \r\nSenthil\r\nhttp:\/\/phoe6.livejournal.com","4":"pyljvim is a a Livejournal Plugin for Vim. One can post to the Livejournal  directly from vim! :)\r\n\r\nHow to use pyljvim:\r\n1) Provide Configfile.txt required details and Install it on your platform\r\n2) Two Templates for posting are provided\r\n\r\n:LJTemplate standart\r\n\r\nOR\r\n\r\n:LJTemplate extended\r\n\r\nFill in the details. Subject is a must.\r\n3) Give a Space after those details and type your text to the world at LJ.\r\n4) When you have finished typing it, do a:\r\n\r\n:LJPost\r\n\r\n5) Your post is online.\r\n\r\n-- \r\nSenthil\r\nhttp:\/\/phoe6.livejournal.com","install_details":"Installation Instructions.\r\n1) Edit Configfile.txt with all the required details.\r\n* Provide the Location of your VIM and PYTHON. ( Keep the Example as the Reference and Provide appropriate Directories)\r\n* If you need PROXY SUPPORT ( Yeah, I need it! :) Give value USE_PROXY as True and provide the details. Otherwise, change the value of USE_PROXY to False\r\n* Provide your LJ Username and Password. ( If Password is not provided, it will be prompt at the time of posting)\r\n\r\n2) python install_pyljvim.py \r\n\r\n3) Thats all. Now can start using it.\r\n\r\nFor a try, do from your vim:\r\n:LJTemplate startart\r\n\r\nFill Subject and type some giberrish and do\r\n\r\n:LJPost\r\n\r\n\r\n","5":"Installation Instructions.\r\n1) Edit Configfile.txt with all the required details.\r\n* Provide the Location of your VIM and PYTHON. ( Keep the Example as the Reference and Provide appropriate Directories)\r\n* If you need PROXY SUPPORT ( Yeah, I need it! :) Give value USE_PROXY as True and provide the details. Otherwise, change the value of USE_PROXY to False\r\n* Provide your LJ Username and Password. ( If Password is not provided, it will be prompt at the time of posting)\r\n\r\n2) python install_pyljvim.py \r\n\r\n3) Thats all. Now can start using it.\r\n\r\nFor a try, do from your vim:\r\n:LJTemplate startart\r\n\r\nFill Subject and type some giberrish and do\r\n\r\n:LJPost\r\n\r\n\r\n","first_name":"Senthil","6":"Senthil","last_name":"Kumaran","7":"Kumaran","releases":[{"0":"1724","vim_version":"7.0","1":"7.0","script_version":"0.4","2":"0.4","version_comment":"Updates to python installation script. Uses distutils.","3":"Updates to python installation script. Uses distutils.","package":"pyljvim-0.4.zip","4":"pyljvim-0.4.zip","src_id":"14312","5":"14312","creation_date":"1290227234","6":"1290227234"}]},"1723":{"script_id":"1723","0":"1723","script_name":"vimpager","1":"vimpager","script_type":"utility","2":"utility","summary":"Use ViM as PAGER","3":"Use ViM as PAGER","description":"A PAGER using less.vim with support for highlighting of man pages and many other features. Works on most UNIX-like systems as well as Cygwin and MSYS.\r\n\r\nOn github:\r\nhttp:\/\/github.com\/rkitover\/vimpager","4":"A PAGER using less.vim with support for highlighting of man pages and many other features. Works on most UNIX-like systems as well as Cygwin and MSYS.\r\n\r\nOn github:\r\nhttp:\/\/github.com\/rkitover\/vimpager","install_details":"% VIMPAGER(1) vimpager user manual\r\n% Rafael Kitover <rkitover@gmail.com>\r\n% April 29, 2015\r\n\r\n# NAME\r\n\r\nvimpager - less.sh replacement\r\n\r\n# SYNOPSIS\r\n\r\nvimpager 'some file'\r\n\r\n# or (this won't always syntax highlight as well)\r\n\r\ncat 'some file' | vimpager\r\n\r\n# RUN-TIME DEPENDENCIES\r\n\r\n* vim\r\n* sharutils or some uudecode (optional)\r\n\r\n# BUILD DEPENDENCIES\r\n\r\n* sharutils or some uuencode\r\n* pandoc\r\n\r\n# INSTALL\r\n\r\n```bash\r\ngit clone git:\/\/github.com\/rkitover\/vimpager\r\ncd vimpager\r\nsudo make install\r\n```\r\n\r\nIf you got vimpager from the vim.org scripts section, just put it\r\nsomewhere in your PATH, e.g.:\r\n\r\n```bash\r\ncp vimpager ~\/bin\r\nchmod +x ~\/bin\/vimpager\r\n```\r\n\r\nIn your ~\/.bashrc add the following:\r\n\r\n```bash\r\nexport PAGER=\/usr\/local\/bin\/vimpager\r\nalias less=$PAGER\r\nalias zless=$PAGER\r\n```\r\n\r\n# DESCRIPTION\r\nA PAGER using less.vim with support for highlighting of man pages and\r\nmany other features. Works on most UNIX-like systems as well as Cygwin\r\nand MSYS.\r\n\r\nOn GitHub: <http:\/\/github.com\/rkitover\/vimpager>\r\n\r\nTo use a different vimrc with vimpager, put your settings into a ~\/.vimpagerrc\r\nor ~\/.vim\/vimpagerrc or a file pointed to by the VIMPAGER_RC environment\r\nvariable.\r\n\r\nYou can also have a global config file for all users in \/etc\/vimpagerrc, users\r\ncan override it by creating a ~\/.vimpagerrc or a ~\/.vim\/vimpagerrc.\r\n\r\nThese are the keys for paging while in vimpager, they are the same as in\r\nless for the most part:\r\n\r\n| _Key_   | _Action_            | _Key_   | _Action_                  |  \r\n|---------|---------------------|---------|---------------------------|  \r\n|<Space>  |One page forward     |b        |One page backward          |  \r\n|d        |Half a page forward  |u        |Half a page backward       |  \r\n|<Enter>  |One line forward     |k        |One line backward          |  \r\n|G        |End of file          |g        |Start of file              |  \r\n|N%       |percentage in file   |,h       |Display this help          |  \r\n|\/pattern |Search for pattern   |?pattern |Search backward for pattern|  \r\n|n        |next pattern match   |N        |Previous pattern match     |  \r\n|:n<Enter>|Next file            |:p<Enter>|Previous file              |  \r\n|q        |Quit                 |,v       |Toggle Less Mode           |  \r\n\r\nTo disable loading plugins, put \"set noloadplugins\" into a vimpagerrc\r\nfile.\r\n\r\nYou can also switch on the \"vimpager\" variable in your vimrc to set alternate\r\nsettings for vimpager.\r\n\r\nPut the following into your .vimrc\/vimpagerrc if you want to use gvim\/MacVim\r\nfor your pager window:\r\n\r\n```vim\r\nlet vimpager_use_gvim = 1\r\n```\r\n\r\nTo turn off the feature of passing through text that is smaller than the\r\nterminal height use this:\r\n\r\n```vim\r\nlet vimpager_passthrough = 0\r\n```\r\n\r\nSee \"PASSTHROUGH MODE\" further down.\r\n\r\nTo start vim with -X (no x11 connection, a bit faster startup) put the following\r\ninto your .vimrc\/vimpagerrc:\r\n\r\n```vim\r\nlet vimpager_disable_x11 = 1\r\n```\r\n\r\nThe scroll offset (:help scrolloff), may be specified by placing the \r\nfollowing into your .vimrc\/vimpagerrc (default = 5, disable = 0):\r\n\r\n```vim\r\nlet vimpager_scrolloff = 5\r\n```\r\n\r\nThe process tree of vimpager is available in the \"vimpager_ptree\" variable, an\r\nexample usage is as follows:\r\n\r\n```vim\r\nif exists(\"vimpager\")\r\n  if exists(\"vimpager_ptree\") && vimpager_ptree[-2] == 'wman'\r\n    set ft=man\r\n  endif\r\nendif\r\n```\r\n\r\nTo disable the use of AnsiEsc.vim to display ANSI colors in the source,\r\nset:\r\n\r\n```vim\r\nlet vimpager_disable_ansiesc = 1\r\n```\r\n\r\nsee the section \"ANSI ESCAPE SEQUENCES AND OVERSTRIKES\" for more\r\ndetails.\r\n\r\n# COMMAND LINE OPTIONS\r\n\r\n## + | +G\r\n\r\nStart at the end of the file, just like less.\r\n\r\n## -c cmd\r\n\r\nRun a vim command after opening the file. Multiple -c arguments are\r\nsupported.\r\n\r\n## --cmd cmd\r\n\r\nRun a vim command when entering vim before anything else. Multiple --cmd\r\narguments are supported.\r\n\r\n## -u vimrc\r\n\r\nUse alternate .vimrc or .vimpagerrc.\r\n\r\n# ANSI ESCAPE SEQUENCES AND OVERSTRIKES\r\n\r\nIf your source is using ANSI escape codes, the AnsiEsc plugin will be\r\nused to show them, rather than the normal vim highlighting, however read\r\nthe caveats below. If this is not possible, they will be stripped out\r\nand normal vim highlighting will be used instead.\r\n\r\nOverstrikes such as in man pages will always be removed.\r\n\r\nvimpager bundles the\r\n[AnsiEsc](http:\/\/www.vim.org\/scripts\/script.php?script_id=4979)\r\nplugin (it is expanded at runtime,\r\nthere is nothing you have to do to enable it.)\r\n\r\nHowever, your vim must have been compiled with the 'conceal' feature\r\nenabled. To check, try\r\n\r\n```vim\r\n:echo has(\"conceal\")\r\n```\r\n\r\nif the result is '1' you have conceal, if it's '0' you do not, and the\r\nAnsiEsc plugin will not be enabled.\r\n\r\nIf you're on a Mac, the system vim does not enable this feature, install\r\nvim from Homebrew.\r\n\r\nTo disable the use of AnsiEsc.vim, set:\r\n\r\n```vim\r\nlet vimpager_disable_ansiesc = 1\r\n```\r\n\r\nin your .vimrc.\r\n\r\n# PASSTHROUGH MODE\r\n\r\nIf the text sent to the pager is smaller than the terminal window, then\r\nit will be displayed without vim as text. If it has ansi codes, they\r\nwill be preserved, otherwise the text will be highlighted with vimcat.\r\n\r\nYou can turn this off by putting\r\n\r\n```vim\r\nlet vimpager_passthrough = 0\r\n```\r\n\r\nPassthrough mode requires a POSIX shell with arithmetic expansion, if\r\nthere is one on your system and it is not detected please submit an\r\nissue with the path and your OS version.\r\n\r\n# CYGWIN\/MSYS\/MSYS2 NOTES\r\n\r\nvimpager works correctly with the native Windows gvim, just put it in\r\nyour PATH and set the vimpager_use_gvim option as described above.\r\n","5":"% VIMPAGER(1) vimpager user manual\r\n% Rafael Kitover <rkitover@gmail.com>\r\n% April 29, 2015\r\n\r\n# NAME\r\n\r\nvimpager - less.sh replacement\r\n\r\n# SYNOPSIS\r\n\r\nvimpager 'some file'\r\n\r\n# or (this won't always syntax highlight as well)\r\n\r\ncat 'some file' | vimpager\r\n\r\n# RUN-TIME DEPENDENCIES\r\n\r\n* vim\r\n* sharutils or some uudecode (optional)\r\n\r\n# BUILD DEPENDENCIES\r\n\r\n* sharutils or some uuencode\r\n* pandoc\r\n\r\n# INSTALL\r\n\r\n```bash\r\ngit clone git:\/\/github.com\/rkitover\/vimpager\r\ncd vimpager\r\nsudo make install\r\n```\r\n\r\nIf you got vimpager from the vim.org scripts section, just put it\r\nsomewhere in your PATH, e.g.:\r\n\r\n```bash\r\ncp vimpager ~\/bin\r\nchmod +x ~\/bin\/vimpager\r\n```\r\n\r\nIn your ~\/.bashrc add the following:\r\n\r\n```bash\r\nexport PAGER=\/usr\/local\/bin\/vimpager\r\nalias less=$PAGER\r\nalias zless=$PAGER\r\n```\r\n\r\n# DESCRIPTION\r\nA PAGER using less.vim with support for highlighting of man pages and\r\nmany other features. Works on most UNIX-like systems as well as Cygwin\r\nand MSYS.\r\n\r\nOn GitHub: <http:\/\/github.com\/rkitover\/vimpager>\r\n\r\nTo use a different vimrc with vimpager, put your settings into a ~\/.vimpagerrc\r\nor ~\/.vim\/vimpagerrc or a file pointed to by the VIMPAGER_RC environment\r\nvariable.\r\n\r\nYou can also have a global config file for all users in \/etc\/vimpagerrc, users\r\ncan override it by creating a ~\/.vimpagerrc or a ~\/.vim\/vimpagerrc.\r\n\r\nThese are the keys for paging while in vimpager, they are the same as in\r\nless for the most part:\r\n\r\n| _Key_   | _Action_            | _Key_   | _Action_                  |  \r\n|---------|---------------------|---------|---------------------------|  \r\n|<Space>  |One page forward     |b        |One page backward          |  \r\n|d        |Half a page forward  |u        |Half a page backward       |  \r\n|<Enter>  |One line forward     |k        |One line backward          |  \r\n|G        |End of file          |g        |Start of file              |  \r\n|N%       |percentage in file   |,h       |Display this help          |  \r\n|\/pattern |Search for pattern   |?pattern |Search backward for pattern|  \r\n|n        |next pattern match   |N        |Previous pattern match     |  \r\n|:n<Enter>|Next file            |:p<Enter>|Previous file              |  \r\n|q        |Quit                 |,v       |Toggle Less Mode           |  \r\n\r\nTo disable loading plugins, put \"set noloadplugins\" into a vimpagerrc\r\nfile.\r\n\r\nYou can also switch on the \"vimpager\" variable in your vimrc to set alternate\r\nsettings for vimpager.\r\n\r\nPut the following into your .vimrc\/vimpagerrc if you want to use gvim\/MacVim\r\nfor your pager window:\r\n\r\n```vim\r\nlet vimpager_use_gvim = 1\r\n```\r\n\r\nTo turn off the feature of passing through text that is smaller than the\r\nterminal height use this:\r\n\r\n```vim\r\nlet vimpager_passthrough = 0\r\n```\r\n\r\nSee \"PASSTHROUGH MODE\" further down.\r\n\r\nTo start vim with -X (no x11 connection, a bit faster startup) put the following\r\ninto your .vimrc\/vimpagerrc:\r\n\r\n```vim\r\nlet vimpager_disable_x11 = 1\r\n```\r\n\r\nThe scroll offset (:help scrolloff), may be specified by placing the \r\nfollowing into your .vimrc\/vimpagerrc (default = 5, disable = 0):\r\n\r\n```vim\r\nlet vimpager_scrolloff = 5\r\n```\r\n\r\nThe process tree of vimpager is available in the \"vimpager_ptree\" variable, an\r\nexample usage is as follows:\r\n\r\n```vim\r\nif exists(\"vimpager\")\r\n  if exists(\"vimpager_ptree\") && vimpager_ptree[-2] == 'wman'\r\n    set ft=man\r\n  endif\r\nendif\r\n```\r\n\r\nTo disable the use of AnsiEsc.vim to display ANSI colors in the source,\r\nset:\r\n\r\n```vim\r\nlet vimpager_disable_ansiesc = 1\r\n```\r\n\r\nsee the section \"ANSI ESCAPE SEQUENCES AND OVERSTRIKES\" for more\r\ndetails.\r\n\r\n# COMMAND LINE OPTIONS\r\n\r\n## + | +G\r\n\r\nStart at the end of the file, just like less.\r\n\r\n## -c cmd\r\n\r\nRun a vim command after opening the file. Multiple -c arguments are\r\nsupported.\r\n\r\n## --cmd cmd\r\n\r\nRun a vim command when entering vim before anything else. Multiple --cmd\r\narguments are supported.\r\n\r\n## -u vimrc\r\n\r\nUse alternate .vimrc or .vimpagerrc.\r\n\r\n# ANSI ESCAPE SEQUENCES AND OVERSTRIKES\r\n\r\nIf your source is using ANSI escape codes, the AnsiEsc plugin will be\r\nused to show them, rather than the normal vim highlighting, however read\r\nthe caveats below. If this is not possible, they will be stripped out\r\nand normal vim highlighting will be used instead.\r\n\r\nOverstrikes such as in man pages will always be removed.\r\n\r\nvimpager bundles the\r\n[AnsiEsc](http:\/\/www.vim.org\/scripts\/script.php?script_id=4979)\r\nplugin (it is expanded at runtime,\r\nthere is nothing you have to do to enable it.)\r\n\r\nHowever, your vim must have been compiled with the 'conceal' feature\r\nenabled. To check, try\r\n\r\n```vim\r\n:echo has(\"conceal\")\r\n```\r\n\r\nif the result is '1' you have conceal, if it's '0' you do not, and the\r\nAnsiEsc plugin will not be enabled.\r\n\r\nIf you're on a Mac, the system vim does not enable this feature, install\r\nvim from Homebrew.\r\n\r\nTo disable the use of AnsiEsc.vim, set:\r\n\r\n```vim\r\nlet vimpager_disable_ansiesc = 1\r\n```\r\n\r\nin your .vimrc.\r\n\r\n# PASSTHROUGH MODE\r\n\r\nIf the text sent to the pager is smaller than the terminal window, then\r\nit will be displayed without vim as text. If it has ansi codes, they\r\nwill be preserved, otherwise the text will be highlighted with vimcat.\r\n\r\nYou can turn this off by putting\r\n\r\n```vim\r\nlet vimpager_passthrough = 0\r\n```\r\n\r\nPassthrough mode requires a POSIX shell with arithmetic expansion, if\r\nthere is one on your system and it is not detected please submit an\r\nissue with the path and your OS version.\r\n\r\n# CYGWIN\/MSYS\/MSYS2 NOTES\r\n\r\nvimpager works correctly with the native Windows gvim, just put it in\r\nyour PATH and set the vimpager_use_gvim option as described above.\r\n","first_name":"Rafael","6":"Rafael","last_name":"Kitover","7":"Kitover","releases":[{"0":"1723","vim_version":"7.0","1":"7.0","script_version":"2.06","2":"2.06","version_comment":"* more Solaris fixes\r\n* remove array syntax from vimcat #118","3":"* more Solaris fixes\r\n* remove array syntax from vimcat #118","package":"vimpager","4":"vimpager","src_id":"23421","5":"23421","creation_date":"1435522342","6":"1435522342"},{"0":"1723","vim_version":"7.0","1":"7.0","script_version":"2.05","2":"2.05","version_comment":"* minor AnsiEsc fixes","3":"* minor AnsiEsc fixes","package":"vimpager","4":"vimpager","src_id":"23358","5":"23358","creation_date":"1433605187","6":"1433605187"},{"0":"1723","vim_version":"7.0","1":"7.0","script_version":"2.04","2":"2.04","version_comment":"* fix Solaris regression","3":"* fix Solaris regression","package":"vimpager","4":"vimpager","src_id":"23308","5":"23308","creation_date":"1432581695","6":"1432581695"},{"0":"1723","vim_version":"7.0","1":"7.0","script_version":"2.03","2":"2.03","version_comment":"* use getpos('.') instead of getcurpos() in ansi retab script, some vims do not have getcurpos() #114\r\n* add ,v mapping to switch back and forth between less mode and editing mode #101\r\n* add ,h mapping for help #107","3":"* use getpos('.') instead of getcurpos() in ansi retab script, some vims do not have getcurpos() #114\r\n* add ,v mapping to switch back and forth between less mode and editing mode #101\r\n* add ,h mapping for help #107","package":"vimpager","4":"vimpager","src_id":"23276","5":"23276","creation_date":"1431728355","6":"1431728355"},{"0":"1723","vim_version":"7.0","1":"7.0","script_version":"2.02","2":"2.02","version_comment":"* fix gvim\/mvim support broken in 2.0","3":"* fix gvim\/mvim support broken in 2.0","package":"vimpager","4":"vimpager","src_id":"23240","5":"23240","creation_date":"1430408105","6":"1430408105"},{"0":"1723","vim_version":"7.0","1":"7.0","script_version":"2.0","2":"2.0","version_comment":"* full support for ANSI highlighted text\r\n  using bundled AnsiEsc \r\n* support MSYS2 \r\n* experimental highlighting support for perl\r\n  in perldocs by Magnus Woldrich \r\n* better detection of C man pages with\r\n  highlighting\r\n* suppress errors about things that look like\r\n  modelines \r\n* support for -- and safer opening of any\r\n  file names \r\n* passthrough mode where text that is shorter\r\n  than the terminal window is just printed is\r\n  now the default and supports all\r\n  highlighting \r\n* clean up mappings like 'h' that caused some\r\n  people problems, we bundle our own less.vim\r\n  now so this is easier \r\n* default to bg=dark when using terminal vim,\r\n  this is helpful for people without vim\r\n  configs since most people use a dark\r\n  background but vim defaults to light \r\n* multiple -c and --cmd options are now\r\n  supported, as well as the -u option\r\n","3":"* full support for ANSI highlighted text\r\n  using bundled AnsiEsc \r\n* support MSYS2 \r\n* experimental highlighting support for perl\r\n  in perldocs by Magnus Woldrich \r\n* better detection of C man pages with\r\n  highlighting\r\n* suppress errors about things that look like\r\n  modelines \r\n* support for -- and safer opening of any\r\n  file names \r\n* passthrough mode where text that is shorter\r\n  than the terminal window is just printed is\r\n  now the default and supports all\r\n  highlighting \r\n* clean up mappings like 'h' that caused some\r\n  people problems, we bundle our own less.vim\r\n  now so this is easier \r\n* default to bg=dark when using terminal vim,\r\n  this is helpful for people without vim\r\n  configs since most people use a dark\r\n  background but vim defaults to light \r\n* multiple -c and --cmd options are now\r\n  supported, as well as the -u option\r\n","package":"vimpager","4":"vimpager","src_id":"23236","5":"23236","creation_date":"1430326340","6":"1430326340"},{"0":"1723","vim_version":"7.0","1":"7.0","script_version":"1.8.9","2":"1.8.9","version_comment":"* security enhancements (snordhausen: Stefan Nordhausen) #78","3":"* security enhancements (snordhausen: Stefan Nordhausen) #78","package":"vimpager","4":"vimpager","src_id":"21936","5":"21936","creation_date":"1401020147","6":"1401020147"},{"0":"1723","vim_version":"7.0","1":"7.0","script_version":"1.8.8","2":"1.8.8","version_comment":"* don't clobber user's PATH (mayersj1: Steve Mayer)  #77","3":"* don't clobber user's PATH (mayersj1: Steve Mayer)  #77","package":"vimpager","4":"vimpager","src_id":"21744","5":"21744","creation_date":"1396894378","6":"1396894378"},{"0":"1723","vim_version":"7.0","1":"7.0","script_version":"1.8.7","2":"1.8.7","version_comment":"* use more lines for fallback man page detection, misc. code cleanups (eworm-de: Christian Hesse)","3":"* use more lines for fallback man page detection, misc. code cleanups (eworm-de: Christian Hesse)","package":"vimpager","4":"vimpager","src_id":"21595","5":"21595","creation_date":"1394489980","6":"1394489980"},{"0":"1723","vim_version":"7.0","1":"7.0","script_version":"1.8.6","2":"1.8.6","version_comment":"* allow _vimrc on non-windows (mortonfox: Morton Fox)","3":"* allow _vimrc on non-windows (mortonfox: Morton Fox)","package":"vimpager","4":"vimpager","src_id":"21522","5":"21522","creation_date":"1393081876","6":"1393081876"},{"0":"1723","vim_version":"7.0","1":"7.0","script_version":"1.8.5","2":"1.8.5","version_comment":"* fix up arrow binding again, broken in 1.8.4","3":"* fix up arrow binding again, broken in 1.8.4","package":"vimpager","4":"vimpager","src_id":"21474","5":"21474","creation_date":"1392226100","6":"1392226100"},{"0":"1723","vim_version":"7.0","1":"7.0","script_version":"1.8.4","2":"1.8.4","version_comment":"* disable help screen 'h' binding, cursor moves left instead (Github issue #71)","3":"* disable help screen 'h' binding, cursor moves left instead (Github issue #71)","package":"vimpager","4":"vimpager","src_id":"21450","5":"21450","creation_date":"1391940315","6":"1391940315"},{"0":"1723","vim_version":"7.0","1":"7.0","script_version":"1.8.3","2":"1.8.3","version_comment":"* reexec self under bash or ksh when available, especially on Solaris (Github issue #63)\r\n* add vim command -c option (aroig: Abdo Roig-Maranges)\r\n* allow ~\/.vim\/vimpagerrc as conf file (lucc: Lucas Hoffmann)","3":"* reexec self under bash or ksh when available, especially on Solaris (Github issue #63)\r\n* add vim command -c option (aroig: Abdo Roig-Maranges)\r\n* allow ~\/.vim\/vimpagerrc as conf file (lucc: Lucas Hoffmann)","package":"vimpager","4":"vimpager","src_id":"21228","5":"21228","creation_date":"1387791910","6":"1387791910"},{"0":"1723","vim_version":"7.0","1":"7.0","script_version":"1.8.2","2":"1.8.2","version_comment":"* better man page detection heuristics, when detection by process tree fails","3":"* better man page detection heuristics, when detection by process tree fails","package":"vimpager","4":"vimpager","src_id":"19937","5":"19937","creation_date":"1366964293","6":"1366964293"},{"0":"1723","vim_version":"7.0","1":"7.0","script_version":"1.8.1","2":"1.8.1","version_comment":"* License under 2-clause BSD (GitHub Issue #59)","3":"* License under 2-clause BSD (GitHub Issue #59)","package":"vimpager","4":"vimpager","src_id":"19820","5":"19820","creation_date":"1366058711","6":"1366058711"},{"0":"1723","vim_version":"7.0","1":"7.0","script_version":"1.8.0","2":"1.8.0","version_comment":"* fix man detection on NetBSD (nonakap: NONAKA Kimihiro)","3":"* fix man detection on NetBSD (nonakap: NONAKA Kimihiro)","package":"vimpager","4":"vimpager","src_id":"19669","5":"19669","creation_date":"1363803077","6":"1363803077"},{"0":"1723","vim_version":"7.0","1":"7.0","script_version":"1.7.8","2":"1.7.8","version_comment":"* set filetype for man pages correctly on FreeBSD (justinkb: Paul Mulders)","3":"* set filetype for man pages correctly on FreeBSD (justinkb: Paul Mulders)","package":"vimpager","4":"vimpager","src_id":"19271","5":"19271","creation_date":"1356971309","6":"1356971309"},{"0":"1723","vim_version":"7.0","1":"7.0","script_version":"1.7.7","2":"1.7.7","version_comment":"* fix screen flashing (GitHub Issue #46)\r\n* fix q with visual selection (GitHub Issue #45)\r\n* support for +G or + command line option to start at the end of the file (vincer: Vince Rosso)","3":"* fix screen flashing (GitHub Issue #46)\r\n* fix q with visual selection (GitHub Issue #45)\r\n* support for +G or + command line option to start at the end of the file (vincer: Vince Rosso)","package":"vimpager","4":"vimpager","src_id":"19030","5":"19030","creation_date":"1353895827","6":"1353895827"},{"0":"1723","vim_version":"7.0","1":"7.0","script_version":"1.7.6","2":"1.7.6","version_comment":"* support \/usr\/local\/etc\/vimpagerrc and \/etc\/vimpagerrc, read after user's .vimrc\r\n* fix for .vimrc paths with spaces (Github Issue #49)\r\n* support compressed file extensions case-insensitively","3":"* support \/usr\/local\/etc\/vimpagerrc and \/etc\/vimpagerrc, read after user's .vimrc\r\n* fix for .vimrc paths with spaces (Github Issue #49)\r\n* support compressed file extensions case-insensitively","package":"vimpager","4":"vimpager","src_id":"18971","5":"18971","creation_date":"1352785458","6":"1352785458"},{"0":"1723","vim_version":"7.0","1":"7.0","script_version":"1.7.5","2":"1.7.5","version_comment":"* set nocp with -u, fixes Pathogen compatibility (Github Issue #40)\r\n* delete temp directory if file is zero length\r\n* remove .gz\/.Z suffixes on temp files for compressed files\r\n* support global config file \/etc\/vimpagerrc (eworm-de: Christian Hesse)","3":"* set nocp with -u, fixes Pathogen compatibility (Github Issue #40)\r\n* delete temp directory if file is zero length\r\n* remove .gz\/.Z suffixes on temp files for compressed files\r\n* support global config file \/etc\/vimpagerrc (eworm-de: Christian Hesse)","package":"vimpager","4":"vimpager","src_id":"18718","5":"18718","creation_date":"1348939908","6":"1348939908"},{"0":"1723","vim_version":"7.0","1":"7.0","script_version":"1.7.4","2":"1.7.4","version_comment":"* improve $VIM detection for Win32 (cygwin\/msys)","3":"* improve $VIM detection for Win32 (cygwin\/msys)","package":"vimpager","4":"vimpager","src_id":"18640","5":"18640","creation_date":"1348079330","6":"1348079330"},{"0":"1723","vim_version":"7.0","1":"7.0","script_version":"1.7.3","2":"1.7.3","version_comment":"* fix usage without a vimrc (Github Issue #38) broken in 1.7.2","3":"* fix usage without a vimrc (Github Issue #38) broken in 1.7.2","package":"vimpager","4":"vimpager","src_id":"18601","5":"18601","creation_date":"1347671378","6":"1347671378"},{"0":"1723","vim_version":"7.0","1":"7.0","script_version":"1.7.2","2":"1.7.2","version_comment":"* passthrough option for small text (Wei Dai)\r\n* major code refactor and cleanup","3":"* passthrough option for small text (Wei Dai)\r\n* major code refactor and cleanup","package":"vimpager","4":"vimpager","src_id":"18593","5":"18593","creation_date":"1347569561","6":"1347569561"},{"0":"1723","vim_version":"7.0","1":"7.0","script_version":"1.7.1","2":"1.7.1","version_comment":"* fix arrow keys (Adam Lickel)","3":"* fix arrow keys (Adam Lickel)","package":"vimpager","4":"vimpager","src_id":"18306","5":"18306","creation_date":"1343030673","6":"1343030673"},{"0":"1723","vim_version":"7.0","1":"7.0","script_version":"1.7.0","2":"1.7.0","version_comment":"* make sure plugins don't override q (GitHub Issue #34)\r\n* attempt fix for OpenBSD ps (GitHub Issue #33)","3":"* make sure plugins don't override q (GitHub Issue #34)\r\n* attempt fix for OpenBSD ps (GitHub Issue #33)","package":"vimpager","4":"vimpager","src_id":"18187","5":"18187","creation_date":"1340607927","6":"1340607927"},{"0":"1723","vim_version":"7.0","1":"7.0","script_version":"1.6.9","2":"1.6.9","version_comment":"* stop sourcing vimrc\/gvimrc twice (Dave Goodell)","3":"* stop sourcing vimrc\/gvimrc twice (Dave Goodell)","package":"vimpager","4":"vimpager","src_id":"18161","5":"18161","creation_date":"1340099420","6":"1340099420"},{"0":"1723","vim_version":"7.0","1":"7.0","script_version":"1.6.8","2":"1.6.8","version_comment":"* fix scrolloff and custom scrolloff setting (GitHub Issue #30)\r\n* safe mode for temp directory (Anselm Strauss)\r\n* turn off relative line numbers (Simon Olofsson and Anisse Astier)","3":"* fix scrolloff and custom scrolloff setting (GitHub Issue #30)\r\n* safe mode for temp directory (Anselm Strauss)\r\n* turn off relative line numbers (Simon Olofsson and Anisse Astier)","package":"vimpager","4":"vimpager","src_id":"17756","5":"17756","creation_date":"1334166923","6":"1334166923"},{"0":"1723","vim_version":"7.0","1":"7.0","script_version":"1.6.7","2":"1.6.7","version_comment":"* more intuitive arrow key behavior (patch by Iftekharul Haque)\r\n* add vimpager_ptree variable to hold the process tree (patch by Wei Dai)","3":"* more intuitive arrow key behavior (patch by Iftekharul Haque)\r\n* add vimpager_ptree variable to hold the process tree (patch by Wei Dai)","package":"vimpager","4":"vimpager","src_id":"17332","5":"17332","creation_date":"1327816027","6":"1327816027"},{"0":"1723","vim_version":"7.0","1":"7.0","script_version":"1.6.6","2":"1.6.6","version_comment":"* fix malformed utf8 warnings","3":"* fix malformed utf8 warnings","package":"vimpager","4":"vimpager","src_id":"17184","5":"17184","creation_date":"1326197199","6":"1326197199"},{"0":"1723","vim_version":"7.0","1":"7.0","script_version":"1.6.5","2":"1.6.5","version_comment":"* fix \"col: illegal byte sequence\" errors","3":"* fix \"col: illegal byte sequence\" errors","package":"vimpager","4":"vimpager","src_id":"17183","5":"17183","creation_date":"1326185522","6":"1326185522"},{"0":"1723","vim_version":"7.0","1":"7.0","script_version":"1.6.4","2":"1.6.4","version_comment":"* configurable scrolloff by Peter Fern","3":"* configurable scrolloff by Peter Fern","package":"vimpager","4":"vimpager","src_id":"17135","5":"17135","creation_date":"1325337217","6":"1325337217"},{"0":"1723","vim_version":"7.0","1":"7.0","script_version":"1.6.3","2":"1.6.3","version_comment":"* fix zero length check on cygwin","3":"* fix zero length check on cygwin","package":"vimpager","4":"vimpager","src_id":"17043","5":"17043","creation_date":"1323423145","6":"1323423145"},{"0":"1723","vim_version":"7.0","1":"7.0","script_version":"1.6.2","2":"1.6.2","version_comment":"* Pathogen compatibility\r\n* slightly faster startup","3":"* Pathogen compatibility\r\n* slightly faster startup","package":"vimpager","4":"vimpager","src_id":"16990","5":"16990","creation_date":"1322513901","6":"1322513901"},{"0":"1723","vim_version":"7.0","1":"7.0","script_version":"1.6.1","2":"1.6.1","version_comment":"* only source .vimrc if it exists","3":"* only source .vimrc if it exists","package":"vimpager","4":"vimpager","src_id":"16940","5":"16940","creation_date":"1321970799","6":"1321970799"},{"0":"1723","vim_version":"7.0","1":"7.0","script_version":"1.6.0","2":"1.6.0","version_comment":"* work around broken sed on OSX by using col -b if available","3":"* work around broken sed on OSX by using col -b if available","package":"vimpager","4":"vimpager","src_id":"16902","5":"16902","creation_date":"1321647651","6":"1321647651"},{"0":"1723","vim_version":"7.0","1":"7.0","script_version":"1.5.9","2":"1.5.9","version_comment":"* remove -X by default (GitHub issue #19)","3":"* remove -X by default (GitHub issue #19)","package":"vimpager","4":"vimpager","src_id":"16889","5":"16889","creation_date":"1321539794","6":"1321539794"},{"0":"1723","vim_version":"7.0","1":"7.0","script_version":"1.5.8","2":"1.5.8","version_comment":"* re-source vimrc\/gvimrc after less.vim to preserve user highlights and mappings","3":"* re-source vimrc\/gvimrc after less.vim to preserve user highlights and mappings","package":"vimpager","4":"vimpager","src_id":"16859","5":"16859","creation_date":"1321190934","6":"1321190934"},{"0":"1723","vim_version":"7.0","1":"7.0","script_version":"1.5.7","2":"1.5.7","version_comment":"* remove mouse=h to allow mouse scrolling","3":"* remove mouse=h to allow mouse scrolling","package":"vimpager","4":"vimpager","src_id":"16134","5":"16134","creation_date":"1311593167","6":"1311593167"},{"0":"1723","vim_version":"7.0","1":"7.0","script_version":"1.5.6","2":"1.5.6","version_comment":"* fix for filenames with spaces by Damien Pollet","3":"* fix for filenames with spaces by Damien Pollet","package":"vimpager","4":"vimpager","src_id":"16086","5":"16086","creation_date":"1310898665","6":"1310898665"},{"0":"1723","vim_version":"7.0","1":"7.0","script_version":"1.5.5","2":"1.5.5","version_comment":"* remove --noplugin\r\n* better gvimrc detection on cygwin","3":"* remove --noplugin\r\n* better gvimrc detection on cygwin","package":"vimpager","4":"vimpager","src_id":"16012","5":"16012","creation_date":"1309471368","6":"1309471368"},{"0":"1723","vim_version":"7.0","1":"7.0","script_version":"1.5.4","2":"1.5.4","version_comment":"* support ~\/.vimpagerrc and VIMPAGER_RC","3":"* support ~\/.vimpagerrc and VIMPAGER_RC","package":"vimpager","4":"vimpager","src_id":"15967","5":"15967","creation_date":"1308884816","6":"1308884816"},{"0":"1723","vim_version":"7.0","1":"7.0","script_version":"1.5.3","2":"1.5.3","version_comment":"* exit immediately for zero length files","3":"* exit immediately for zero length files","package":"vimpager","4":"vimpager","src_id":"15961","5":"15961","creation_date":"1308832495","6":"1308832495"},{"0":"1723","vim_version":"7.0","1":"7.0","script_version":"1.5.2","2":"1.5.2","version_comment":"* turn off terminal reset on OSX","3":"* turn off terminal reset on OSX","package":"vimpager","4":"vimpager","src_id":"15811","5":"15811","creation_date":"1307269277","6":"1307269277"},{"0":"1723","vim_version":"7.0","1":"7.0","script_version":"1.5.1","2":"1.5.1","version_comment":"* better msys support","3":"* better msys support","package":"vimpager","4":"vimpager","src_id":"15696","5":"15696","creation_date":"1306070361","6":"1306070361"},{"0":"1723","vim_version":"7.0","1":"7.0","script_version":"1.5.0","2":"1.5.0","version_comment":"* set scrolloff-5","3":"* set scrolloff-5","package":"vimpager","4":"vimpager","src_id":"15602","5":"15602","creation_date":"1304748942","6":"1304748942"},{"0":"1723","vim_version":"7.0","1":"7.0","script_version":"1.4.9","2":"1.4.9","version_comment":"* trap more signals for temp file removal\r\n* clear terminal on OSX only for terminal vim","3":"* trap more signals for temp file removal\r\n* clear terminal on OSX only for terminal vim","package":"vimpager","4":"vimpager","src_id":"15564","5":"15564","creation_date":"1304268371","6":"1304268371"},{"0":"1723","vim_version":"7.0","1":"7.0","script_version":"1.4.8","2":"1.4.8","version_comment":"* fix compatibility with Cygwin\r\n* fix compatibility with Windows gvim in Cygwin and msys\r\n* detect ssh session on OSX and Cygwin\r\n* remove \"Input not from a terminal\" warning entirely\r\n","3":"* fix compatibility with Cygwin\r\n* fix compatibility with Windows gvim in Cygwin and msys\r\n* detect ssh session on OSX and Cygwin\r\n* remove \"Input not from a terminal\" warning entirely\r\n","package":"vimpager","4":"vimpager","src_id":"15504","5":"15504","creation_date":"1303482618","6":"1303482618"},{"0":"1723","vim_version":"6.0","1":"6.0","script_version":"1.4.7","2":"1.4.7","version_comment":"* fix some \"input not from terminal\" warnings\r\n* fix for invocations on files not in current directory","3":"* fix some \"input not from terminal\" warnings\r\n* fix for invocations on files not in current directory","package":"vimpager","4":"vimpager","src_id":"15453","5":"15453","creation_date":"1302879429","6":"1302879429"},{"0":"1723","vim_version":"6.0","1":"6.0","script_version":"1.4.6","2":"1.4.6","version_comment":"* MacVim support\r\n* override GUI colors from .gvimrc\r\n* fix syntax highlighting for files opened directly\r\n* reset terminal on completion","3":"* MacVim support\r\n* override GUI colors from .gvimrc\r\n* fix syntax highlighting for files opened directly\r\n* reset terminal on completion","package":"vimpager","4":"vimpager","src_id":"15429","5":"15429","creation_date":"1302561041","6":"1302561041"},{"0":"1723","vim_version":"6.0","1":"6.0","script_version":"1.4.5","2":"1.4.5","version_comment":"* fixes for Mac OSX\r\n* -X option to speed up startup (jdevera)","3":"* fixes for Mac OSX\r\n* -X option to speed up startup (jdevera)","package":"vimpager","4":"vimpager","src_id":"15413","5":"15413","creation_date":"1302256265","6":"1302256265"},{"0":"1723","vim_version":"6.0","1":"6.0","script_version":"1.4.4","2":"1.4.4","version_comment":"* .vimrc option let vimpager_use_gvim = 1 to use gvim as the pager window","3":"* .vimrc option let vimpager_use_gvim = 1 to use gvim as the pager window","package":"vimpager","4":"vimpager","src_id":"15268","5":"15268","creation_date":"1300693389","6":"1300693389"},{"0":"1723","vim_version":"6.0","1":"6.0","script_version":"1.4.3","2":"1.4.3","version_comment":"* Support for .Z and .gz files","3":"* Support for .Z and .gz files","package":"vimpager","4":"vimpager","src_id":"15255","5":"15255","creation_date":"1300626703","6":"1300626703"},{"0":"1723","vim_version":"6.0","1":"6.0","script_version":"1.4.2","2":"1.4.2","version_comment":"* Extensive rewrite using awk for real Solaris compatibility by Wout Mertens.\r\n* Filter ANSI color codes and backspaces for all pager invocations (github issue #2)","3":"* Extensive rewrite using awk for real Solaris compatibility by Wout Mertens.\r\n* Filter ANSI color codes and backspaces for all pager invocations (github issue #2)","package":"vimpager","4":"vimpager","src_id":"15253","5":"15253","creation_date":"1300618036","6":"1300618036"},{"0":"1723","vim_version":"6.0","1":"6.0","script_version":"1.4","2":"1.4","version_comment":"* fix for python2 docs on archlinux from Ivan S. Freitas","3":"* fix for python2 docs on archlinux from Ivan S. Freitas","package":"vimpager","4":"vimpager","src_id":"14694","5":"14694","creation_date":"1294360956","6":"1294360956"},{"0":"1723","vim_version":"6.0","1":"6.0","script_version":"1.3","2":"1.3","version_comment":"* added 'set nonu'","3":"* added 'set nonu'","package":"vimpager","4":"vimpager","src_id":"13024","5":"13024","creation_date":"1274132279","6":"1274132279"},{"0":"1723","vim_version":"6.0","1":"6.0","script_version":"1.2","2":"1.2","version_comment":"* fix for FreeBSD\r\n* add esc-u mapping to turn off hlsearch","3":"* fix for FreeBSD\r\n* add esc-u mapping to turn off hlsearch","package":"vimpager","4":"vimpager","src_id":"12918","5":"12918","creation_date":"1272634781","6":"1272634781"},{"0":"1723","vim_version":"6.0","1":"6.0","script_version":"1.1","2":"1.1","version_comment":"Fix bug where it wouldn't move on searches at launch without moving the cursor first","3":"Fix bug where it wouldn't move on searches at launch without moving the cursor first","package":"vimpager","4":"vimpager","src_id":"10663","5":"10663","creation_date":"1243032255","6":"1243032255"},{"0":"1723","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Fix for perldoc on Cygwin","3":"Fix for perldoc on Cygwin","package":"vimpager","4":"vimpager","src_id":"10646","5":"10646","creation_date":"1242868689","6":"1242868689"},{"0":"1723","vim_version":"6.0","1":"6.0","script_version":"0.9","2":"0.9","version_comment":"Fix for filenames with spaces.","3":"Fix for filenames with spaces.","package":"vimpager","4":"vimpager","src_id":"10634","5":"10634","creation_date":"1242753356","6":"1242753356"},{"0":"1723","vim_version":"6.0","1":"6.0","script_version":"0.8","2":"0.8","version_comment":"Turn off folds (correctly this time.)","3":"Turn off folds (correctly this time.)","package":"vimpager","4":"vimpager","src_id":"10294","5":"10294","creation_date":"1238115334","6":"1238115334"}]},"1722":{"script_id":"1722","0":"1722","script_name":"cf.vim","1":"cf.vim","script_type":"syntax","2":"syntax","summary":"Syntax file for ColdFusion","3":"Syntax file for ColdFusion","description":"This is a reasonably complete syntax file for ColdFusion, up to at least version 7.0. I have pored over the LiveDocs fairly thoroughly to make sure that every valid tag, attribute, and function is included; nonetheless, if you find a problem, please let me know! The only current shortcoming that I'm aware of is that deprecated items are not highlighted properly, though they are tagged with the \"Error\" class.\r\n\r\nTwo screenshots are available, one of plain CFML and one of a ColdFusion component:\r\nhttp:\/\/severinghaus.org\/projects\/cfml.png\r\nhttp:\/\/severinghaus.org\/projects\/cfc.png","4":"This is a reasonably complete syntax file for ColdFusion, up to at least version 7.0. I have pored over the LiveDocs fairly thoroughly to make sure that every valid tag, attribute, and function is included; nonetheless, if you find a problem, please let me know! The only current shortcoming that I'm aware of is that deprecated items are not highlighted properly, though they are tagged with the \"Error\" class.\r\n\r\nTwo screenshots are available, one of plain CFML and one of a ColdFusion component:\r\nhttp:\/\/severinghaus.org\/projects\/cfml.png\r\nhttp:\/\/severinghaus.org\/projects\/cfc.png","install_details":"","5":"","first_name":"Steven","6":"Steven","last_name":"Severinghaus","7":"Severinghaus","releases":[{"0":"1722","vim_version":"6.0","1":"6.0","script_version":"0.1.3","2":"0.1.3","version_comment":"Updated to include all valid attributes in CF7; marked even more deprecated tags.","3":"Updated to include all valid attributes in CF7; marked even more deprecated tags.","package":"cf.vim","4":"cf.vim","src_id":"6780","5":"6780","creation_date":"1172241351","6":"1172241351"},{"0":"1722","vim_version":"6.0","1":"6.0","script_version":"0.1.2","2":"0.1.2","version_comment":"Noted a few more deprecated functions as of CF6.1, though they're still not highlighting as I'd like (the \"Error\" class seems to be ignored).","3":"Noted a few more deprecated functions as of CF6.1, though they're still not highlighting as I'd like (the \"Error\" class seems to be ignored).","package":"cf.vim","4":"cf.vim","src_id":"6777","5":"6777","creation_date":"1172224844","6":"1172224844"},{"0":"1722","vim_version":"6.0","1":"6.0","script_version":"0.1.1","2":"0.1.1","version_comment":"Credit to Jeff Lanzarotta for original version; more complete lists of tags, attributes, and functions; a couple of deprecated tags.","3":"Credit to Jeff Lanzarotta for original version; more complete lists of tags, attributes, and functions; a couple of deprecated tags.","package":"cf.vim","4":"cf.vim","src_id":"6485","5":"6485","creation_date":"1164884649","6":"1164884649"},{"0":"1722","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"cf.vim","4":"cf.vim","src_id":"6482","5":"6482","creation_date":"1164803420","6":"1164803420"}]},"1721":{"script_id":"1721","0":"1721","script_name":"renamer.vim","1":"renamer.vim","script_type":"utility","2":"utility","summary":"Use the power of vim to rename groups of files","3":"Use the power of vim to rename groups of files","description":"NOTE! This location is no longer the latest code - it's moved to github, and set up as a pathogen-style bundle, here: \r\n\r\nhttps:\/\/github.com\/qpkorr\/vim-renamer\r\n\r\n\r\nBasic Usage:\r\nShow a list of file names in a directory, rename then in the vim \r\nbuffer using vim editing commands, then have vim rename them on disk\r\nStart the plugin with the command :Renamer\r\n\r\nDetails:\r\nRenaming a single file is easily done via an operating system file explorer,\r\nthe vim file explorer (netrw.vim), or the command line.  When you want to\r\nrename a bunch of files, especially when you want to do a common text\r\nmanipulation to those file names, this plugin may help.  It shows you all\r\nthe files in the current directory, and lets you edit their names in the vim\r\nbuffer.  When you're ready, issue the command \":Ren\" to perform the mass\r\nrename.  The intention is to rename files in the same directory, but\r\nrelative paths can be specified to move files around - provided the \r\ndestination directories exist","4":"NOTE! This location is no longer the latest code - it's moved to github, and set up as a pathogen-style bundle, here: \r\n\r\nhttps:\/\/github.com\/qpkorr\/vim-renamer\r\n\r\n\r\nBasic Usage:\r\nShow a list of file names in a directory, rename then in the vim \r\nbuffer using vim editing commands, then have vim rename them on disk\r\nStart the plugin with the command :Renamer\r\n\r\nDetails:\r\nRenaming a single file is easily done via an operating system file explorer,\r\nthe vim file explorer (netrw.vim), or the command line.  When you want to\r\nrename a bunch of files, especially when you want to do a common text\r\nmanipulation to those file names, this plugin may help.  It shows you all\r\nthe files in the current directory, and lets you edit their names in the vim\r\nbuffer.  When you're ready, issue the command \":Ren\" to perform the mass\r\nrename.  The intention is to rename files in the same directory, but\r\nrelative paths can be specified to move files around - provided the \r\ndestination directories exist","install_details":"The usual - drop this file into your $HOME\/.vim\/plugin directory (unix)\r\nor $HOME\/vimfiles\/plugin directory (Windows), etc.\r\nUse the commands defined below to invoke the functionality (or redefine them\r\nelsewhere to what you want), and set the User Configurable Variables as\r\ndesired.\r\n\r\nInstalling As Windows Right Click Menu Option:\r\nTo add running this script on a directory as a right click menu option,\r\nif you are confident working with the registry, do as\r\nfollows (NOTE - THESE INSTRUCTIONS CAME FROM THE WEB AND WORKED FOR\r\nME for both Windows 7 and XP, BUT I CAN'T GUARANTEE THEY ARE 100% SAFE):\r\n- Run the Registry Editor (REGEDIT.EXE) - make sure you have administrator privileges.\r\n- Open My Computer\\HKEY_CLASSES_ROOT\\Directory and click on the \r\n  sub-item 'shell'. \r\n- Select New from the Edit menu, and then select Key. \r\n- Here, type VimRenamer and press Enter. \r\n- Double-click on the (Default) value in the right pane, and type the name\r\n  to see in the menu, eg Rename Files with Vim Renamer - and then press Enter.\r\n- Click on the new key in the left pane, select New from the Edit menu, \r\n  and then select Key again. \r\n- Type the word 'command' (without quotes) for the name of this new key, and press Enter. \r\n- Double-click on the (Default) value in the right pane, and type the full \r\n  path and filename to vim, along with the vim command as per the following \r\n  example line:\r\n  \"C:\\Program Files\\vim\\vim70\\gvim.exe\" -c \"cd %1|Renamer\"\r\n  Change the path according to the location of gvim on your system. Press Enter when done.\r\n- Close the Registry Editor.","5":"The usual - drop this file into your $HOME\/.vim\/plugin directory (unix)\r\nor $HOME\/vimfiles\/plugin directory (Windows), etc.\r\nUse the commands defined below to invoke the functionality (or redefine them\r\nelsewhere to what you want), and set the User Configurable Variables as\r\ndesired.\r\n\r\nInstalling As Windows Right Click Menu Option:\r\nTo add running this script on a directory as a right click menu option,\r\nif you are confident working with the registry, do as\r\nfollows (NOTE - THESE INSTRUCTIONS CAME FROM THE WEB AND WORKED FOR\r\nME for both Windows 7 and XP, BUT I CAN'T GUARANTEE THEY ARE 100% SAFE):\r\n- Run the Registry Editor (REGEDIT.EXE) - make sure you have administrator privileges.\r\n- Open My Computer\\HKEY_CLASSES_ROOT\\Directory and click on the \r\n  sub-item 'shell'. \r\n- Select New from the Edit menu, and then select Key. \r\n- Here, type VimRenamer and press Enter. \r\n- Double-click on the (Default) value in the right pane, and type the name\r\n  to see in the menu, eg Rename Files with Vim Renamer - and then press Enter.\r\n- Click on the new key in the left pane, select New from the Edit menu, \r\n  and then select Key again. \r\n- Type the word 'command' (without quotes) for the name of this new key, and press Enter. \r\n- Double-click on the (Default) value in the right pane, and type the full \r\n  path and filename to vim, along with the vim command as per the following \r\n  example line:\r\n  \"C:\\Program Files\\vim\\vim70\\gvim.exe\" -c \"cd %1|Renamer\"\r\n  Change the path according to the location of gvim on your system. Press Enter when done.\r\n- Close the Registry Editor.","first_name":"John","6":"John","last_name":"Orr","7":"Orr","releases":[{"0":"1721","vim_version":"7.0","1":"7.0","script_version":"1.4","2":"1.4","version_comment":"- fix permitted filenames problem on Mac OS - thanks Adam Courtemanche.\r\n- fix bug when launching from within an existing buffer.\r\n","3":"- fix permitted filenames problem on Mac OS - thanks Adam Courtemanche.\r\n- fix bug when launching from within an existing buffer.\r\n","package":"renamer.vim","4":"renamer.vim","src_id":"16876","5":"16876","creation_date":"1321407116","6":"1321407116"},{"0":"1721","vim_version":"7.0","1":"7.0","script_version":"1.3","2":"1.3","version_comment":"1.3 - check that proposed filenames are valid before applying them\r\n    - add support for creating required directories - thanks to Glen Miner\r\n      for the request that made it finally happen.\r\n    - fix location of intermediate files to be the same as the source file.\r\n      (Particularly important for large files on slow-access media, as\r\n      they were being copied to and from local media.)\r\n      Thanks to Adam Courtemanche for finding and fixing the bug!","3":"1.3 - check that proposed filenames are valid before applying them\r\n    - add support for creating required directories - thanks to Glen Miner\r\n      for the request that made it finally happen.\r\n    - fix location of intermediate files to be the same as the source file.\r\n      (Particularly important for large files on slow-access media, as\r\n      they were being copied to and from local media.)\r\n      Thanks to Adam Courtemanche for finding and fixing the bug!","package":"renamer.vim","4":"renamer.vim","src_id":"16861","5":"16861","creation_date":"1321200513","6":"1321200513"},{"0":"1721","vim_version":"7.0","1":"7.0","script_version":"1.2","2":"1.2","version_comment":"Fix filename handling for linux - thanks Antonio Monizio\r\nImprove :w support to avoid delay showing command line - thanks Sergey Bochenkov\r\nOther minor improvements","3":"Fix filename handling for linux - thanks Antonio Monizio\r\nImprove :w support to avoid delay showing command line - thanks Sergey Bochenkov\r\nOther minor improvements","package":"renamer.vim","4":"renamer.vim","src_id":"13165","5":"13165","creation_date":"1276232647","6":"1276232647"},{"0":"1721","vim_version":"7.0","1":"7.0","script_version":"1.1","2":"1.1","version_comment":"Added options to\r\n      a) support :w as substitute for :Ren, and\r\n      b) ignore wildignore settings when reading in files.\r\nFixed a bug with highlighting after file deletion.\r\nVarious other minor changes, eg naming the buffer.\r\n","3":"Added options to\r\n      a) support :w as substitute for :Ren, and\r\n      b) ignore wildignore settings when reading in files.\r\nFixed a bug with highlighting after file deletion.\r\nVarious other minor changes, eg naming the buffer.\r\n","package":"renamer.vim","4":"renamer.vim","src_id":"12345","5":"12345","creation_date":"1265718670","6":"1265718670"},{"0":"1721","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"renamer.vim","4":"renamer.vim","src_id":"6479","5":"6479","creation_date":"1164781251","6":"1164781251"}]},"1720":{"script_id":"1720","0":"1720","script_name":"gvimext.dll: support tabs under VIM 7","1":"gvimext.dll: support tabs under VIM 7","script_type":"utility","2":"utility","summary":"Support loading files into a VIM tab","3":"Support loading files into a VIM tab","description":"Update: if you want to always open files in a tab, there is a simple solution with no need for a custom gvimext.dll.  Add the below entry to .vimrc file:\r\nautocmd BufReadPost * tab ball\r\nThis is a tip by \"jackal\" from the below link:\r\nhttp:\/\/stackoverflow.com\/questions\/1891513\/can-i-force-gvim-to-open-dragged-in-files-in-a-new-tab\r\n\r\n--- The below instructions are needed if you want to switch between tab and no tab. ---\r\nImportant: this update only applies to VIM 7.\r\n\r\nThis update to gvimext.dll supports the loading of files under a new tab in VIM 7.  Both the gvimext.dll and its updated source codes are provided in the attached zip file.\r\n\r\nI believe this code change will be included in the upcoming VIM release.  So this upload is for the brave and the impatient.\r\n\r\nBelow is the usage:\r\n0.  The new dll will display \"Edit with ... using tabs\" options upon right-click on files in Windows Explorer based on a registry key and the Shift key combination.\r\n1.  If you don't import UseTab.reg file into registry, gvimext.dll will behave just like before the change.  You can still get the \"using tabs\" options by holding down the Shift key before right-clicking the files.\r\n2.  Shift key effect\r\nShift key serves as a toggle key for the \"Edit with ... using tabs\" context menu.  If you hold down the Shift key and then right-click the selected files in Windows Explorer, the opposite of the default Vim context menu will display.\r\nOnce the Vim content menu displays, you don't need to hold down the Shift key anymore.  Its effect will hold until the next Right-Click.\r\n","4":"Update: if you want to always open files in a tab, there is a simple solution with no need for a custom gvimext.dll.  Add the below entry to .vimrc file:\r\nautocmd BufReadPost * tab ball\r\nThis is a tip by \"jackal\" from the below link:\r\nhttp:\/\/stackoverflow.com\/questions\/1891513\/can-i-force-gvim-to-open-dragged-in-files-in-a-new-tab\r\n\r\n--- The below instructions are needed if you want to switch between tab and no tab. ---\r\nImportant: this update only applies to VIM 7.\r\n\r\nThis update to gvimext.dll supports the loading of files under a new tab in VIM 7.  Both the gvimext.dll and its updated source codes are provided in the attached zip file.\r\n\r\nI believe this code change will be included in the upcoming VIM release.  So this upload is for the brave and the impatient.\r\n\r\nBelow is the usage:\r\n0.  The new dll will display \"Edit with ... using tabs\" options upon right-click on files in Windows Explorer based on a registry key and the Shift key combination.\r\n1.  If you don't import UseTab.reg file into registry, gvimext.dll will behave just like before the change.  You can still get the \"using tabs\" options by holding down the Shift key before right-clicking the files.\r\n2.  Shift key effect\r\nShift key serves as a toggle key for the \"Edit with ... using tabs\" context menu.  If you hold down the Shift key and then right-click the selected files in Windows Explorer, the opposite of the default Vim context menu will display.\r\nOnce the Vim content menu displays, you don't need to hold down the Shift key anymore.  Its effect will hold until the next Right-Click.\r\n","install_details":"1.  Replace existing gvimext.dll with the updated version.\r\nMake a backup of your existing gvimext.dll.  You need to make sure that the existing gvimext.dll is not locked before you copy over the new file.  One way to do it is to open an DOS window, go to the directory where gvimext.dll resides, rename the existing file using the below command:\r\nren gvimext.dll gvimext.old.dll\r\nand then copy over the new dll (assuming the new dll is at c:\\temp)\r\ncopy c:\\temp\\gvimext.dll .\r\nYou need to reboot your machine after this.\r\nAnother way is to use a tool to kill the process (Windows Explorer) that locks gvimext.dll.  One tool is the \"Process Explorer\" from sysinternals (http:\/\/www.microsoft.com\/technet\/sysinternals\/ProcessesAndThreads\/ProcessExplorer.mspx)\r\n2.  UseTab.reg\r\nThis file will add the following registry value:\r\n[HKEY_LOCAL_MACHINE\\SOFTWARE\\Vim\\Gvim]\r\n\"UseTab\"=\"1\"\r\nThe above value will make the \"Edit with ... using tabs\" context menu as the default menu.\r\nTo import this registry file, right-click it and choose Merge in Windows Explorer.\r\n","5":"1.  Replace existing gvimext.dll with the updated version.\r\nMake a backup of your existing gvimext.dll.  You need to make sure that the existing gvimext.dll is not locked before you copy over the new file.  One way to do it is to open an DOS window, go to the directory where gvimext.dll resides, rename the existing file using the below command:\r\nren gvimext.dll gvimext.old.dll\r\nand then copy over the new dll (assuming the new dll is at c:\\temp)\r\ncopy c:\\temp\\gvimext.dll .\r\nYou need to reboot your machine after this.\r\nAnother way is to use a tool to kill the process (Windows Explorer) that locks gvimext.dll.  One tool is the \"Process Explorer\" from sysinternals (http:\/\/www.microsoft.com\/technet\/sysinternals\/ProcessesAndThreads\/ProcessExplorer.mspx)\r\n2.  UseTab.reg\r\nThis file will add the following registry value:\r\n[HKEY_LOCAL_MACHINE\\SOFTWARE\\Vim\\Gvim]\r\n\"UseTab\"=\"1\"\r\nThe above value will make the \"Edit with ... using tabs\" context menu as the default menu.\r\nTo import this registry file, right-click it and choose Merge in Windows Explorer.\r\n","first_name":"Tianmiao","6":"Tianmiao","last_name":"Hu","7":"Hu","releases":[{"0":"1720","vim_version":"7.0","1":"7.0","script_version":"2.0","2":"2.0","version_comment":"Updated to avoid bell sound when VIM already in command mode.","3":"Updated to avoid bell sound when VIM already in command mode.","package":"GvimExt_tab_V2.zip","4":"GvimExt_tab_V2.zip","src_id":"7239","5":"7239","creation_date":"1181723768","6":"1181723768"}]},"1719":{"script_id":"1719","0":"1719","script_name":"WLS Mode","1":"WLS Mode","script_type":"ftplugin","2":"ftplugin","summary":"Complete Bea-Weblogic-Mode as tar.bz2","3":"Complete Bea-Weblogic-Mode as tar.bz2","description":"This is a mirror of http:\/\/www.vim.org\/scripts\/script.php?script_id=1719\r\n\r\nDon't expect to much as it is only Version 0.1 but if you need to edit\/create weblogic.Admin [1] scripts then this plugin will be helpfull.\r\n\r\nAs time passes I plan to add other goodies for Weblogic users. Other contributors are welcome as well.\r\n\r\nReports errors to: http:\/\/code.google.com\/p\/vim-scripts\/issues\/list\r\nDiscuss improvements on: http:\/\/groups.google.com\/group\/vim_scripts\r\n\r\n[1] http:\/\/e-docs.bea.com\/wls\/docs81\/admin_ref\/cli.html\r\n\r\n| Vim-Script  || https:\/\/www.vim.org\/scripts\/script.php?script_id=1719\r\n| Source      || https:\/\/github.com\/krischik\/vim-wls\r\n| Wiki        || https:\/\/github.com\/krischik\/vim-wls\/wiki\r\n| Releases    || https:\/\/github.com\/krischik\/vim-wls\/releases \r\n| Issues      || https:\/\/github.com\/krischik\/vim-wls\/issues \r\n| Discussions || https:\/\/github.com\/krischik\/vim-wls\/discussions \r\n","4":"This is a mirror of http:\/\/www.vim.org\/scripts\/script.php?script_id=1719\r\n\r\nDon't expect to much as it is only Version 0.1 but if you need to edit\/create weblogic.Admin [1] scripts then this plugin will be helpfull.\r\n\r\nAs time passes I plan to add other goodies for Weblogic users. Other contributors are welcome as well.\r\n\r\nReports errors to: http:\/\/code.google.com\/p\/vim-scripts\/issues\/list\r\nDiscuss improvements on: http:\/\/groups.google.com\/group\/vim_scripts\r\n\r\n[1] http:\/\/e-docs.bea.com\/wls\/docs81\/admin_ref\/cli.html\r\n\r\n| Vim-Script  || https:\/\/www.vim.org\/scripts\/script.php?script_id=1719\r\n| Source      || https:\/\/github.com\/krischik\/vim-wls\r\n| Wiki        || https:\/\/github.com\/krischik\/vim-wls\/wiki\r\n| Releases    || https:\/\/github.com\/krischik\/vim-wls\/releases \r\n| Issues      || https:\/\/github.com\/krischik\/vim-wls\/issues \r\n| Discussions || https:\/\/github.com\/krischik\/vim-wls\/discussions \r\n","install_details":"\r\nInstall from https:\/\/github.com\/krischik\/vim-wls using dein (https:\/\/github.com\/Shougo\/dein.vim) or similar:\r\n\r\n{{code|lang=vim|\r\ncall dein#begin('$HOME\/vimfiles\/bundles')\r\ncall dein#add('krischik\/vim-wls')\r\ncall dein#end()\r\ncall dein#install()","5":"\r\nInstall from https:\/\/github.com\/krischik\/vim-wls using dein (https:\/\/github.com\/Shougo\/dein.vim) or similar:\r\n\r\n{{code|lang=vim|\r\ncall dein#begin('$HOME\/vimfiles\/bundles')\r\ncall dein#add('krischik\/vim-wls')\r\ncall dein#end()\r\ncall dein#install()","first_name":"Martin","6":"Martin","last_name":"Krischik","7":"Krischik","releases":[{"0":"1719","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"wls-0.1.0.tar.bz2","4":"wls-0.1.0.tar.bz2","src_id":"6464","5":"6464","creation_date":"1164351356","6":"1164351356"}]},"1718":{"script_id":"1718","0":"1718","script_name":"tabula.vim","1":"tabula.vim","script_type":"color scheme","2":"color scheme","summary":"ergonomic green chalkboard colorscheme for GUI and 256 colors xterms","3":"ergonomic green chalkboard colorscheme for GUI and 256 colors xterms","description":"This is a \"chalkboard\" green background Vim colorscheme featuring soft, yet highly readable contrasts. Main goal was to minimize eye strain when working in a mixed environment where during long edit sessions you have to switch to high contrast white background screens every now and then.\r\nAdditionally there have cterm colors been defined so they will look mostly identical on a 256 color (Linux) xterm. \r\n\r\nView a color sample: http:\/\/www.directupload.net\/file\/d\/4200\/4qiqr6fh_png.htm\r\n(Tabula settings dialog is shown at bottom.)\r\n\r\nStarting with v. 0.2 the colorscheme is adjustable either on setup or on the fly. To permanently redefine the defaults put these settings in your .vimrc file before the\r\n        :colorscheme tabula\r\nline, e.g.:\r\n        :let Tabula_ColorPre = \"red\"\r\n\r\nTo redefine them on the fly call the built-in options dialog:\r\n        :call Tabula()\r\nfrom the Vim command line.\r\nThe new settings will be immediately effective as soon as control is back in the main dialog.\r\nTo get the defaults back issue\r\n        :colorscheme tabula\r\nagain.\r\n(This has changed from earlier tabula versions where this call was necessary to make the settings changes effective.)\r\n\r\nDisplay Statements In Bold:\r\n        Tabula_BoldStatement = 0    -- statements display not bold\r\n        Tabula_BoldStatement = 1    -- statements display bold\r\nDefaults to non-bold display.\r\n\r\nSet GUI Cursor Color:\r\n        Tabula_CurColor = 'blue'\r\n        Tabula_CurColor = 'red'\r\n        Tabula_CurColor = 'yellow'\r\n        Tabula_CurColor = 'white'\r\nDefaults to 'blue'.\r\nNOTE: This works in gvim only. In a terminal (like xterm) the cursor cannot be changed.\r\n\r\nSet Color For Preprocessor Statements:\r\n        Tabula_ColorPre = 'blue'     -- purple-blue\r\n        Tabula_ColorPre = 'red'\t      -- orange-red\r\n        Tabula_ColorPre = 'yellow'  -- lightgreen-yellow\r\nDefaults to 'blue'.\r\n\r\nUse Dark Error Background:\r\nSometimes desirable for less distracting error highlighting.\r\n        Tabula_DarkError = 0        -- light error background\r\n        Tabula_DarkError = 1        -- dark error background\r\nDefaults to light error background.\r\n\r\nUse multiple colors for constant values:\r\n        Tabula_FlatConstants = 1    -- use one common color for all constants\r\n        Tabula_FlatConstants = 0    -- use a different color for each constant type\r\nDefaults to using one common color.\r\n\r\nHow To Display Ignore And NonText Characters:\r\n        Tabula_InvisibleIgnore = 0    -- slightly visible\r\n        Tabula_InvisibleIgnore = 1    -- invisible on standard background\r\nDefaults to invisible display.\r\n\r\nShow Line Numbers Underlined:\r\nSometimes useful to spot a line more easily.\r\n        Tabula_LNumUnderline = 0    -- not underlined\r\n        Tabula_LNumUnderline = 1    -- line numbers are underlined\r\nDefaults to not underlined.\r\n\r\nLet Search Occurrences Stand Out More Prominently:\r\n        Tabula_SearchStandOut = 0    --- normal dark background display\r\n        Tabula_SearchStandOut = 1    --- prominent underlined display\r\n        Tabula_SearchStandOut = 2    --- very prominent display\r\nDefaults to normal display.\r\n\r\nHow To Display TODOs And Similar:\r\n        Tabula_TodoUnderline = 0    -- display on a blue background\r\n        Tabula_TodoUnderline = 1    -- display them underlined white\r\n        Tabula_TodoUnderline = 2\t   -- display them bold\r\n        Tabula_TodoUnderline = 3\t   -- do not enhance them at all\r\nDefaults to underlined display.\r\n\r\nHow to display typographic character values (bold, italic, underlined):\r\n      Tabula_CharValuesColored = 0\tcolored in addition to typographics\r\n      Tabula_CharValuesColored = 1\tnot colored, italics in terminal-based vim reversed\r\n      Tabula_CharValuesColored = 2\tnot colored, underlined in terminal-based vim reversed\r\nDefaults to a colored typographics character values display.\r\nNOTE: \"Colored\" is to be preferred in terminal-based vim because there is no easy way to distinguish italic from underline. In this mode italics and underlined characters are distinguished by different color shades, both displaying not reversed (usually black on a white background field) which is easier to read.\r\nOtherwise there are two non-colored modes:\r\n- italics are shown reversed, underlines are shown underlined\r\nor\r\n- italics are shown underlined, underlines are shown reversed.\r\nThese sub-modes do not affect the GUI display, however, where italics and underlined always display as usual, only color coded or in the common text color.\r\n\r\n","4":"This is a \"chalkboard\" green background Vim colorscheme featuring soft, yet highly readable contrasts. Main goal was to minimize eye strain when working in a mixed environment where during long edit sessions you have to switch to high contrast white background screens every now and then.\r\nAdditionally there have cterm colors been defined so they will look mostly identical on a 256 color (Linux) xterm. \r\n\r\nView a color sample: http:\/\/www.directupload.net\/file\/d\/4200\/4qiqr6fh_png.htm\r\n(Tabula settings dialog is shown at bottom.)\r\n\r\nStarting with v. 0.2 the colorscheme is adjustable either on setup or on the fly. To permanently redefine the defaults put these settings in your .vimrc file before the\r\n        :colorscheme tabula\r\nline, e.g.:\r\n        :let Tabula_ColorPre = \"red\"\r\n\r\nTo redefine them on the fly call the built-in options dialog:\r\n        :call Tabula()\r\nfrom the Vim command line.\r\nThe new settings will be immediately effective as soon as control is back in the main dialog.\r\nTo get the defaults back issue\r\n        :colorscheme tabula\r\nagain.\r\n(This has changed from earlier tabula versions where this call was necessary to make the settings changes effective.)\r\n\r\nDisplay Statements In Bold:\r\n        Tabula_BoldStatement = 0    -- statements display not bold\r\n        Tabula_BoldStatement = 1    -- statements display bold\r\nDefaults to non-bold display.\r\n\r\nSet GUI Cursor Color:\r\n        Tabula_CurColor = 'blue'\r\n        Tabula_CurColor = 'red'\r\n        Tabula_CurColor = 'yellow'\r\n        Tabula_CurColor = 'white'\r\nDefaults to 'blue'.\r\nNOTE: This works in gvim only. In a terminal (like xterm) the cursor cannot be changed.\r\n\r\nSet Color For Preprocessor Statements:\r\n        Tabula_ColorPre = 'blue'     -- purple-blue\r\n        Tabula_ColorPre = 'red'\t      -- orange-red\r\n        Tabula_ColorPre = 'yellow'  -- lightgreen-yellow\r\nDefaults to 'blue'.\r\n\r\nUse Dark Error Background:\r\nSometimes desirable for less distracting error highlighting.\r\n        Tabula_DarkError = 0        -- light error background\r\n        Tabula_DarkError = 1        -- dark error background\r\nDefaults to light error background.\r\n\r\nUse multiple colors for constant values:\r\n        Tabula_FlatConstants = 1    -- use one common color for all constants\r\n        Tabula_FlatConstants = 0    -- use a different color for each constant type\r\nDefaults to using one common color.\r\n\r\nHow To Display Ignore And NonText Characters:\r\n        Tabula_InvisibleIgnore = 0    -- slightly visible\r\n        Tabula_InvisibleIgnore = 1    -- invisible on standard background\r\nDefaults to invisible display.\r\n\r\nShow Line Numbers Underlined:\r\nSometimes useful to spot a line more easily.\r\n        Tabula_LNumUnderline = 0    -- not underlined\r\n        Tabula_LNumUnderline = 1    -- line numbers are underlined\r\nDefaults to not underlined.\r\n\r\nLet Search Occurrences Stand Out More Prominently:\r\n        Tabula_SearchStandOut = 0    --- normal dark background display\r\n        Tabula_SearchStandOut = 1    --- prominent underlined display\r\n        Tabula_SearchStandOut = 2    --- very prominent display\r\nDefaults to normal display.\r\n\r\nHow To Display TODOs And Similar:\r\n        Tabula_TodoUnderline = 0    -- display on a blue background\r\n        Tabula_TodoUnderline = 1    -- display them underlined white\r\n        Tabula_TodoUnderline = 2\t   -- display them bold\r\n        Tabula_TodoUnderline = 3\t   -- do not enhance them at all\r\nDefaults to underlined display.\r\n\r\nHow to display typographic character values (bold, italic, underlined):\r\n      Tabula_CharValuesColored = 0\tcolored in addition to typographics\r\n      Tabula_CharValuesColored = 1\tnot colored, italics in terminal-based vim reversed\r\n      Tabula_CharValuesColored = 2\tnot colored, underlined in terminal-based vim reversed\r\nDefaults to a colored typographics character values display.\r\nNOTE: \"Colored\" is to be preferred in terminal-based vim because there is no easy way to distinguish italic from underline. In this mode italics and underlined characters are distinguished by different color shades, both displaying not reversed (usually black on a white background field) which is easier to read.\r\nOtherwise there are two non-colored modes:\r\n- italics are shown reversed, underlines are shown underlined\r\nor\r\n- italics are shown underlined, underlines are shown reversed.\r\nThese sub-modes do not affect the GUI display, however, where italics and underlined always display as usual, only color coded or in the common text color.\r\n\r\n","install_details":"Unpack the \"tabula.zip\" file in your $HOME\/.vim directory or equivalent.\r\n\r\nThis will put a \"tabula.vim\" color definitions file into the \"colors\" subdirectory\r\nand a short \"tabula.txt\" help file into the \"doc\" subdirectory.\r\n\r\nTo make the documentation known to Vim, issue\r\n        :helptags $HOME\/.vim\/doc\r\n(or equivalent document directory).\r\nAccess the documentation with:\r\n        :help tabula\r\n\r\nDon't forget to update the help tags after upgrading the tabula package.\r\n\r\nLoad the tabula colors with\r\n        :colorscheme tabula\r\n\r\nOptionally define an alternate setup in your .vimrc file and load the colorscheme from there.","5":"Unpack the \"tabula.zip\" file in your $HOME\/.vim directory or equivalent.\r\n\r\nThis will put a \"tabula.vim\" color definitions file into the \"colors\" subdirectory\r\nand a short \"tabula.txt\" help file into the \"doc\" subdirectory.\r\n\r\nTo make the documentation known to Vim, issue\r\n        :helptags $HOME\/.vim\/doc\r\n(or equivalent document directory).\r\nAccess the documentation with:\r\n        :help tabula\r\n\r\nDon't forget to update the help tags after upgrading the tabula package.\r\n\r\nLoad the tabula colors with\r\n        :colorscheme tabula\r\n\r\nOptionally define an alternate setup in your .vimrc file and load the colorscheme from there.","first_name":"Bernd","6":"Bernd","last_name":"Pol","7":"Pol","releases":[{"0":"1718","vim_version":"7.0","1":"7.0","script_version":"1.4.2","2":"1.4.2","version_comment":"- Tabula() dialog fixed: Settings now change immediately.\r\n- Two more display options (bold, not enhanced) for Todos.","3":"- Tabula() dialog fixed: Settings now change immediately.\r\n- Two more display options (bold, not enhanced) for Todos.","package":"tabula.zip","4":"tabula.zip","src_id":"12787","5":"12787","creation_date":"1270499148","6":"1270499148"},{"0":"1718","vim_version":"7.0","1":"7.0","script_version":"1.4.1","2":"1.4.1","version_comment":"- Multiple constant colors reworked\r\n- Unified titles colors\r\n- New option for typographic character values (bold, italic, underline) display.\r\n- Automatic effecting of color changes after Tabula() call does not work, removed.","3":"- Multiple constant colors reworked\r\n- Unified titles colors\r\n- New option for typographic character values (bold, italic, underline) display.\r\n- Automatic effecting of color changes after Tabula() call does not work, removed.","package":"tabula.zip","4":"tabula.zip","src_id":"12771","5":"12771","creation_date":"1270216256","6":"1270216256"},{"0":"1718","vim_version":"7.0","1":"7.0","script_version":"1.4","2":"1.4","version_comment":"Tabula () options dialog changes options automatically when leaving.\r\nColors optimized. VimWiki colors added.","3":"Tabula () options dialog changes options automatically when leaving.\r\nColors optimized. VimWiki colors added.","package":"tabula.zip","4":"tabula.zip","src_id":"12638","5":"12638","creation_date":"1268765206","6":"1268765206"},{"0":"1718","vim_version":"7.0","1":"7.0","script_version":"1.3.2","2":"1.3.2","version_comment":"VimOutliner colors optimized","3":"VimOutliner colors optimized","package":"tabula.zip","4":"tabula.zip","src_id":"8425","5":"8425","creation_date":"1204964412","6":"1204964412"},{"0":"1718","vim_version":"7.0","1":"7.0","script_version":"1.3.1","2":"1.3.1","version_comment":"some small color adjustments\r\nforeground\/background contrast optimized\r\nVimOutliner definitions added","3":"some small color adjustments\r\nforeground\/background contrast optimized\r\nVimOutliner definitions added","package":"tabula.zip","4":"tabula.zip","src_id":"8409","5":"8409","creation_date":"1204866307","6":"1204866307"},{"0":"1718","vim_version":"7.0","1":"7.0","script_version":"1.3","2":"1.3","version_comment":"Option for an even more prominent search display.\r\nHint on forcing 256 xterm colors in help text.","3":"Option for an even more prominent search display.\r\nHint on forcing 256 xterm colors in help text.","package":"tabula.zip","4":"tabula.zip","src_id":"6698","5":"6698","creation_date":"1170294539","6":"1170294539"},{"0":"1718","vim_version":"7.0","1":"7.0","script_version":"1.2","2":"1.2","version_comment":"more color adjustments;\r\noption to switch search highlight added","3":"more color adjustments;\r\noption to switch search highlight added","package":"tabula.zip","4":"tabula.zip","src_id":"6596","5":"6596","creation_date":"1168290975","6":"1168290975"},{"0":"1718","vim_version":"7.0","1":"7.0","script_version":"1.101","2":"1.101","version_comment":"(Sorry, previous upload went wrong! This is the right package.)\r\nSome small color adjustments;\r\ndark error background option added.","3":"(Sorry, previous upload went wrong! This is the right package.)\r\nSome small color adjustments;\r\ndark error background option added.","package":"tabula.zip","4":"tabula.zip","src_id":"6552","5":"6552","creation_date":"1167127384","6":"1167127384"},{"0":"1718","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Colors are quite stable now.\r\nConstant colors option added.\r\nProvided a dialog to change the option settings on the fly.","3":"Colors are quite stable now.\r\nConstant colors option added.\r\nProvided a dialog to change the option settings on the fly.","package":"tabula.zip","4":"tabula.zip","src_id":"6494","5":"6494","creation_date":"1165124183","6":"1165124183"},{"0":"1718","vim_version":"7.0","1":"7.0","script_version":"0.4","2":"0.4","version_comment":"Faulty group link definitions removed;\r\nError group is now yellow on red background except if red cursor is used","3":"Faulty group link definitions removed;\r\nError group is now yellow on red background except if red cursor is used","package":"tabula.vim","4":"tabula.vim","src_id":"6471","5":"6471","creation_date":"1164486616","6":"1164486616"},{"0":"1718","vim_version":"7.0","1":"7.0","script_version":"0.3","2":"0.3","version_comment":"HTML colors added;\r\nCursor color made configurable","3":"HTML colors added;\r\nCursor color made configurable","package":"tabula.vim","4":"tabula.vim","src_id":"6466","5":"6466","creation_date":"1164415839","6":"1164415839"},{"0":"1718","vim_version":"7.0","1":"7.0","script_version":"0.2","2":"0.2","version_comment":"colors slightly adjusted for a harmonic, yet easily distinguishable display on both GUI and xterm;\r\nintroduced some display options","3":"colors slightly adjusted for a harmonic, yet easily distinguishable display on both GUI and xterm;\r\nintroduced some display options","package":"tabula.vim","4":"tabula.vim","src_id":"6462","5":"6462","creation_date":"1164233466","6":"1164233466"},{"0":"1718","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"tabula.vim","4":"tabula.vim","src_id":"6459","5":"6459","creation_date":"1164129806","6":"1164129806"}]},"1717":{"script_id":"1717","0":"1717","script_name":"tcl.vim","1":"tcl.vim","script_type":"indent","2":"indent","summary":"indentation file for tcl","3":"indentation file for tcl","description":"This is a replacement for the tcl indent file that ships with vim. \r\n\r\nHandles line continuations, nested braces and combination of the two. Skips over braces in comments. This should produce indented code that looks \"as you'd expect\".\r\n\r\nIf you have any suggestions or bugs, please send them along. \r\n\r\nRequires vimscript #1603.","4":"This is a replacement for the tcl indent file that ships with vim. \r\n\r\nHandles line continuations, nested braces and combination of the two. Skips over braces in comments. This should produce indented code that looks \"as you'd expect\".\r\n\r\nIf you have any suggestions or bugs, please send them along. \r\n\r\nRequires vimscript #1603.","install_details":"place in ~\/.vim\/indent","5":"place in ~\/.vim\/indent","first_name":"sm","6":"sm","last_name":"smithfield","7":"smithfield","releases":[{"0":"1717","vim_version":"6.0","1":"6.0","script_version":"0.3.6","2":"0.3.6","version_comment":"Another tweek to the indent\/comment interaction.","3":"Another tweek to the indent\/comment interaction.","package":"tcl.vim","4":"tcl.vim","src_id":"6740","5":"6740","creation_date":"1171362852","6":"1171362852"},{"0":"1717","vim_version":"6.0","1":"6.0","script_version":"0.3.5","2":"0.3.5","version_comment":"Change the way indentation interacts with comments and line-continues. Now it basically ignores comments when reformatting indentation.","3":"Change the way indentation interacts with comments and line-continues. Now it basically ignores comments when reformatting indentation.","package":"tcl.vim","4":"tcl.vim","src_id":"6733","5":"6733","creation_date":"1171012763","6":"1171012763"},{"0":"1717","vim_version":"6.0","1":"6.0","script_version":"0.3.3","2":"0.3.3","version_comment":"Thanks to some feedback, found a bug w\/rt the indentation of commented text.","3":"Thanks to some feedback, found a bug w\/rt the indentation of commented text.","package":"tcl.vim","4":"tcl.vim","src_id":"6708","5":"6708","creation_date":"1170423200","6":"1170423200"},{"0":"1717","vim_version":"6.0","1":"6.0","script_version":"0.3.1","2":"0.3.1","version_comment":"fixed a bug for vim<7.0 that would cause a dead hang. This version is properly tested on vim 6.4.","3":"fixed a bug for vim<7.0 that would cause a dead hang. This version is properly tested on vim 6.4.","package":"tcl.vim","4":"tcl.vim","src_id":"6703","5":"6703","creation_date":"1170345221","6":"1170345221"},{"0":"1717","vim_version":"6.0","1":"6.0","script_version":"0.3","2":"0.3","version_comment":"This is a big improvement over the previous version. Too many things to list. Just try it.","3":"This is a big improvement over the previous version. Too many things to list. Just try it.","package":"tcl.vim","4":"tcl.vim","src_id":"6699","5":"6699","creation_date":"1170301487","6":"1170301487"},{"0":"1717","vim_version":"6.0","1":"6.0","script_version":"0.2","2":"0.2","version_comment":"Much improved. Handles hanging indents for things like data runs in [array set]. Handles escaped braces and other edge cases.","3":"Much improved. Handles hanging indents for things like data runs in [array set]. Handles escaped braces and other edge cases.","package":"tcl.vim","4":"tcl.vim","src_id":"6660","5":"6660","creation_date":"1169760472","6":"1169760472"},{"0":"1717","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"tcl.vim","4":"tcl.vim","src_id":"6444","5":"6444","creation_date":"1163941153","6":"1163941153"}]},"1716":{"script_id":"1716","0":"1716","script_name":"tcl_sqlite.vim","1":"tcl_sqlite.vim","script_type":"syntax","2":"syntax","summary":"syntax coloring for sqlite inside tcl, extends tcl.vim","3":"syntax coloring for sqlite inside tcl, extends tcl.vim","description":"Adds sqlite syntax to tcl.vim (vimscript #1603)\r\n\r\nWords that (can) conflict with Tcl\r\n        eval -  overrides eval as a secondary command for interp. \r\n                   This should really not be a problem.\r\n","4":"Adds sqlite syntax to tcl.vim (vimscript #1603)\r\n\r\nWords that (can) conflict with Tcl\r\n        eval -  overrides eval as a secondary command for interp. \r\n                   This should really not be a problem.\r\n","install_details":"     Place in ~\/.vim\/syntax\/\r\n\r\n    Activated by uncommenting the option at the top of the tcl.vim file.","5":"     Place in ~\/.vim\/syntax\/\r\n\r\n    Activated by uncommenting the option at the top of the tcl.vim file.","first_name":"sm","6":"sm","last_name":"smithfield","7":"smithfield","releases":[{"0":"1716","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"tcl_sqlite.vim","4":"tcl_sqlite.vim","src_id":"6442","5":"6442","creation_date":"1163939796","6":"1163939796"}]},"1715":{"script_id":"1715","0":"1715","script_name":"tcl_snit.vim","1":"tcl_snit.vim","script_type":"syntax","2":"syntax","summary":"syntax coloring for snit, extends tcl.vim","3":"syntax coloring for snit, extends tcl.vim","description":"Adds snit syntax to tcl.vim (vimscript #1603)\r\n\r\nWords that (can) conflict with Tcl\r\n      option - same word, different usage\r\n      variable - has additional options\r\n      configure - can step on tk configure !watch out! \r\n\r\n","4":"Adds snit syntax to tcl.vim (vimscript #1603)\r\n\r\nWords that (can) conflict with Tcl\r\n      option - same word, different usage\r\n      variable - has additional options\r\n      configure - can step on tk configure !watch out! \r\n\r\n","install_details":"INSTALATION:\r\n\r\n    Place in ~\/.vim\/syntax\/\r\n   Activated by uncommenting the option at the top of the tcl.vim file.\r\n\r\n","5":"INSTALATION:\r\n\r\n    Place in ~\/.vim\/syntax\/\r\n   Activated by uncommenting the option at the top of the tcl.vim file.\r\n\r\n","first_name":"sm","6":"sm","last_name":"smithfield","7":"smithfield","releases":[{"0":"1715","vim_version":"6.0","1":"6.0","script_version":"0.2","2":"0.2","version_comment":"Minor corrections.","3":"Minor corrections.","package":"tcl_snit.vim","4":"tcl_snit.vim","src_id":"6650","5":"6650","creation_date":"1169594307","6":"1169594307"},{"0":"1715","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"tcl_snit.vim","4":"tcl_snit.vim","src_id":"6441","5":"6441","creation_date":"1163939655","6":"1163939655"}]},"1714":{"script_id":"1714","0":"1714","script_name":"Tail Bundle","1":"Tail Bundle","script_type":"utility","2":"utility","summary":"Yet another tail -f plugin","3":"Yet another tail -f plugin","description":"This Tail plug-in combines the ideas from vimscript#1374 and vimscript#1692 into one plugin offering both preview and tabbed tail functionality. I also added shortcut mapping to \"set wrap\" and \"set number\" - which both can be useful when observing log files.\r\n\r\n| Vim-Script  || https:\/\/www.vim.org\/scripts\/script.php?script_id=1714\r\n| Source      || https:\/\/github.com\/krischik\/vim-tail\r\n| Wiki        || https:\/\/github.com\/krischik\/vim-tail\/wiki\r\n| Releases    || https:\/\/github.com\/krischik\/vim-tail\/releases \r\n| Issues      || https:\/\/github.com\/krischik\/vim-tail\/issues \r\n| Discussions || https:\/\/github.com\/krischik\/vim-tail\/discussions ","4":"This Tail plug-in combines the ideas from vimscript#1374 and vimscript#1692 into one plugin offering both preview and tabbed tail functionality. I also added shortcut mapping to \"set wrap\" and \"set number\" - which both can be useful when observing log files.\r\n\r\n| Vim-Script  || https:\/\/www.vim.org\/scripts\/script.php?script_id=1714\r\n| Source      || https:\/\/github.com\/krischik\/vim-tail\r\n| Wiki        || https:\/\/github.com\/krischik\/vim-tail\/wiki\r\n| Releases    || https:\/\/github.com\/krischik\/vim-tail\/releases \r\n| Issues      || https:\/\/github.com\/krischik\/vim-tail\/issues \r\n| Discussions || https:\/\/github.com\/krischik\/vim-tail\/discussions ","install_details":"Install from https:\/\/github.com\/krischik\/vim-tail using dein (https:\/\/github.com\/Shougo\/dein.vim) or similar:\r\n\r\n{{code|lang=vim|\r\ncall dein#begin('$HOME\/vimfiles\/bundles')\r\ncall dein#add('krischik\/vim-tail')\r\ncall dein#end()\r\ncall dein#install()\r\n","5":"Install from https:\/\/github.com\/krischik\/vim-tail using dein (https:\/\/github.com\/Shougo\/dein.vim) or similar:\r\n\r\n{{code|lang=vim|\r\ncall dein#begin('$HOME\/vimfiles\/bundles')\r\ncall dein#add('krischik\/vim-tail')\r\ncall dein#end()\r\ncall dein#install()\r\n","first_name":"Martin","6":"Martin","last_name":"Krischik","7":"Krischik","releases":[{"0":"1714","vim_version":"7.0","1":"7.0","script_version":"3.1","2":"3.1","version_comment":"See: https:\/\/github.com\/krischik\/Tail-Bundle\/releases\/tag\/v_3.1","3":"See: https:\/\/github.com\/krischik\/Tail-Bundle\/releases\/tag\/v_3.1","package":"Tail-Bundle-v_3.1.zip","4":"Tail-Bundle-v_3.1.zip","src_id":"28183","5":"28183","creation_date":"1663471350","6":"1663471350"},{"0":"1714","vim_version":"7.0","1":"7.0","script_version":"3.0","2":"3.0","version_comment":"Aww https:\/\/github.com\/krischik\/Tail-Bundle\/releases\/tag\/v_3.0","3":"Aww https:\/\/github.com\/krischik\/Tail-Bundle\/releases\/tag\/v_3.0","package":"Tail-Bundle-v_3.0.zip","4":"Tail-Bundle-v_3.0.zip","src_id":"28176","5":"28176","creation_date":"1662994054","6":"1662994054"},{"0":"1714","vim_version":"6.0","1":"6.0","script_version":"3.0","2":"3.0","version_comment":"New features: Startup script:\r\n\r\nYou can now open one or more files for (tabbed) tailing using vim-tail.zsh\r\nwhich is provided in the macros directory. vim-tail.zsh will use a single\r\ngvim server and :TabTail to open the files.\r\n","3":"New features: Startup script:\r\n\r\nYou can now open one or more files for (tabbed) tailing using vim-tail.zsh\r\nwhich is provided in the macros directory. vim-tail.zsh will use a single\r\ngvim server and :TabTail to open the files.\r\n","package":"tail-3.0.vba","4":"tail-3.0.vba","src_id":"7685","5":"7685","creation_date":"1189996382","6":"1189996382"},{"0":"1714","vim_version":"7.0","1":"7.0","script_version":"2.2","2":"2.2","version_comment":"Another bug slipped in and needed fixing.\r\n\r\nOf course the \"checktime\" problem under windows is not yet fixed.","3":"Another bug slipped in and needed fixing.\r\n\r\nOf course the \"checktime\" problem under windows is not yet fixed.","package":"tail-2.2.vba","4":"tail-2.2.vba","src_id":"6567","5":"6567","creation_date":"1167647906","6":"1167647906"},{"0":"1714","vim_version":"7.0","1":"7.0","script_version":"2.1","2":"2.1","version_comment":"Some bug fixes. Vimball has been checked and should work Ok now.\r\n\r\nHowever, in windows \"checktime\" does not work and the \"pedit!\" workaround is problematic when used with tabs and therefore has been commented out. As it is Windows users need to manually reload - or uncomment the \"pedit!\" workaround and not use tabs.","3":"Some bug fixes. Vimball has been checked and should work Ok now.\r\n\r\nHowever, in windows \"checktime\" does not work and the \"pedit!\" workaround is problematic when used with tabs and therefore has been commented out. As it is Windows users need to manually reload - or uncomment the \"pedit!\" workaround and not use tabs.","package":"tail-2.1.vba","4":"tail-2.1.vba","src_id":"6565","5":"6565","creation_date":"1167549174","6":"1167549174"},{"0":"1714","vim_version":"7.0","1":"7.0","script_version":"2.0","2":"2.0","version_comment":"Upload a tar.bz2 version for those who have problems with VimBall.","3":"Upload a tar.bz2 version for those who have problems with VimBall.","package":"tail-2.0.0.tar.bz2","4":"tail-2.0.0.tar.bz2","src_id":"6519","5":"6519","creation_date":"1166334352","6":"1166334352"},{"0":"1714","vim_version":"7.0","1":"7.0","script_version":"2.0","2":"2.0","version_comment":"Initial upload","3":"Initial upload","package":"tail-2.0.vba","4":"tail-2.0.vba","src_id":"6438","5":"6438","creation_date":"1163815589","6":"1163815589"}]},"1713":{"script_id":"1713","0":"1713","script_name":"darker-robin","1":"darker-robin","script_type":"color scheme","2":"color scheme","summary":"Dark color scheme, based on robinhood","3":"Dark color scheme, based on robinhood","description":"Dark color scheme, based on robinhood, but less contast, tested on GVim 7.0\r\n\r\nIt's looks fine on my TFT in night, evening.\r\n\r\nHope, you find it useful :)\r\n\r\nBest regards","4":"Dark color scheme, based on robinhood, but less contast, tested on GVim 7.0\r\n\r\nIt's looks fine on my TFT in night, evening.\r\n\r\nHope, you find it useful :)\r\n\r\nBest regards","install_details":"copy it into ~\/.vim\/colors and type :colo darker-robin","5":"copy it into ~\/.vim\/colors and type :colo darker-robin","first_name":"Alexander","6":"Alexander","last_name":"Chaika","7":"Chaika","releases":[{"0":"1713","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"darker-robin.vim","4":"darker-robin.vim","src_id":"6431","5":"6431","creation_date":"1163741829","6":"1163741829"}]},"1712":{"script_id":"1712","0":"1712","script_name":"Test::Base syntax","1":"Test::Base syntax","script_type":"syntax","2":"syntax","summary":"Test::Base spec syntax hilighting","3":"Test::Base spec syntax hilighting","description":"testbase.vim is Test::Base spec syntax hilighting.\r\n\r\nScreenShot: http:\/\/f.hatena.ne.jp\/images\/fotolife\/s\/secondlife\/20061117\/20061117163415.png\r\n  \r\n: installation\r\n   This script cp ~\/.vim\/syntax\/testbase.vim\r\n   and write file detect file ~\/.vim\/ftdetect\/testbase.vim\r\n      au BufNewFile,BufRead *_test.rb set filetype=ruby | unlet b:current_syntax | syn include @rubyTestBase syntax\/testbase.vim | syn region rubyTestBase matchgroup=rubyData start=\"^__END__$\" keepend end=\"\\%$\" contains=@rubyTestBase\r\n      au BufNewFile,BufRead *.t set filetype=perl | unlet b:current_syntax | syn include @perlTestBase syntax\/testbase.vim | syn region perlTestBase matchgroup=perlData start=\"^__\\(DATA\\|END\\)__$\" keepend end=\"\\%$\" contains=@perlTestBase\r\n","4":"testbase.vim is Test::Base spec syntax hilighting.\r\n\r\nScreenShot: http:\/\/f.hatena.ne.jp\/images\/fotolife\/s\/secondlife\/20061117\/20061117163415.png\r\n  \r\n: installation\r\n   This script cp ~\/.vim\/syntax\/testbase.vim\r\n   and write file detect file ~\/.vim\/ftdetect\/testbase.vim\r\n      au BufNewFile,BufRead *_test.rb set filetype=ruby | unlet b:current_syntax | syn include @rubyTestBase syntax\/testbase.vim | syn region rubyTestBase matchgroup=rubyData start=\"^__END__$\" keepend end=\"\\%$\" contains=@rubyTestBase\r\n      au BufNewFile,BufRead *.t set filetype=perl | unlet b:current_syntax | syn include @perlTestBase syntax\/testbase.vim | syn region perlTestBase matchgroup=perlData start=\"^__\\(DATA\\|END\\)__$\" keepend end=\"\\%$\" contains=@perlTestBase\r\n","install_details":"","5":"","first_name":"yuichi","6":"yuichi","last_name":"tateno","7":"tateno","releases":[{"0":"1712","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"testbase.vim","4":"testbase.vim","src_id":"6428","5":"6428","creation_date":"1163720344","6":"1163720344"}]},"1711":{"script_id":"1711","0":"1711","script_name":"Business Objects Syntax","1":"Business Objects Syntax","script_type":"syntax","2":"syntax","summary":"Highlighting for Business Objects formulas","3":"Highlighting for Business Objects formulas","description":"Highlighting for Business Objects formulas (english)","4":"Highlighting for Business Objects formulas (english)","install_details":"1. copy downloaded file to your syntax directory\r\n2. add the following lines to your filetype.vim file :\r\n\t\" Business Objects formulas\r\n\tau BufNewFile,BufRead *.bof\t\t\tsetf bof","5":"1. copy downloaded file to your syntax directory\r\n2. add the following lines to your filetype.vim file :\r\n\t\" Business Objects formulas\r\n\tau BufNewFile,BufRead *.bof\t\t\tsetf bof","first_name":"Mike","6":"Mike","last_name":"Meirsman","7":"Meirsman","releases":[{"0":"1711","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"bof.vim","4":"bof.vim","src_id":"6424","5":"6424","creation_date":"1163646720","6":"1163646720"}]},"1710":{"script_id":"1710","0":"1710","script_name":"SWIFT-ATE Syntax","1":"SWIFT-ATE Syntax","script_type":"syntax","2":"syntax","summary":"SWIFT ATE files highlighting","3":"SWIFT ATE files highlighting","description":"Proper SWIFT (http:\/\/www.swift.com) ATE files highlighting.\r\n\r\nThis syntax complies to FIN release 2006.","4":"Proper SWIFT (http:\/\/www.swift.com) ATE files highlighting.\r\n\r\nThis syntax complies to FIN release 2006.","install_details":"1. copy downloaded file to your syntax directory\r\n2. add the following lines to your filetype.vim file :\r\n\t\" ATE SWIFT Message\r\n\tau BufNewFile,BufRead *.ate\t\t\tsetf ate","5":"1. copy downloaded file to your syntax directory\r\n2. add the following lines to your filetype.vim file :\r\n\t\" ATE SWIFT Message\r\n\tau BufNewFile,BufRead *.ate\t\t\tsetf ate","first_name":"Mike","6":"Mike","last_name":"Meirsman","7":"Meirsman","releases":[{"0":"1710","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"ate.vim","4":"ate.vim","src_id":"6423","5":"6423","creation_date":"1163646584","6":"1163646584"}]},"1709":{"script_id":"1709","0":"1709","script_name":"scons.vim","1":"scons.vim","script_type":"syntax","2":"syntax","summary":"Syntax file for SConscript\/SConstruct","3":"Syntax file for SConscript\/SConstruct","description":"Syntax file for SConscript or SConstruct, configuration files of the build tool SCons.\r\n\r\nhttp:\/\/www.scons.org\/","4":"Syntax file for SConscript or SConstruct, configuration files of the build tool SCons.\r\n\r\nhttp:\/\/www.scons.org\/","install_details":"1. Copy scons.vim into the directory ~\/.vim\/syntax\/ \r\n2. Add the following line to ~\/.vimrc \r\nau BufNewFile,BufRead SCons* set filetype=scons\r\n\r\nYou may also add syntax support for Scons* or scons* files.","5":"1. Copy scons.vim into the directory ~\/.vim\/syntax\/ \r\n2. Add the following line to ~\/.vimrc \r\nau BufNewFile,BufRead SCons* set filetype=scons\r\n\r\nYou may also add syntax support for Scons* or scons* files.","first_name":"Xi","6":"Xi","last_name":"Wang","7":"Wang","releases":[{"0":"1709","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"scons.vim","4":"scons.vim","src_id":"6421","5":"6421","creation_date":"1163578185","6":"1163578185"}]},"1708":{"script_id":"1708","0":"1708","script_name":"fencview.vim","1":"fencview.vim","script_type":"utility","2":"utility","summary":"Auto detect CJK and Unicode file encodings.","3":"Auto detect CJK and Unicode file encodings.","description":"Have you ever met that after opening a text file with some kind of encoding you got a bunch of unreadable mess? If so, you need fencview.vim.\r\n\r\nNormally, vim detects file encoding based on 'fileencodings' option. For example, if we set this option like this: set fileencodings=ucs-bom,GB2312,big5 Firstly vim try to read file bom. If there is no bom, vim will try to decode the file with GB2312. Unfortunately, the GB2312 and big5 have a lot of overlapped code-points which could lead to a big5-encoded file be decoded with GB2312 by mistake. Then you got mess.\r\n\r\nThe 'vencview' uses another approach, let me show you how. As we know, take Chinese for example, the occurrence frequency of every character in a normal article is different. For example, '的' is a high frequency character which is encoded to 0xb5c4 in GB2312. However, in Big5 0xb5c4 is the code point for '腔' which is much less frequently used. So we can \"guess\" the encoding of a file by count up the frequently used characters. It is not 100% accurate but works in most cases.\r\n\r\nThe user manual is embeded in fencview.vim, refer to it if you'd like to custmize this script.\r\n\r\nIf you encounter a file that fencview can not handle, you're more than welcome to send it to me in order to improve the algrithm, but take care of the sensitive data before you do that.\r\n\r\nHow to use\r\nBasically, you need this plugin only when you ran into some messy code. In this case you need fencview to auto detect the file encoding. Either click the menu entry: \"Tools->Encoding->Auto Detect\" or use this command: :FencAutoDetect and probably that's all.\r\n\r\nIf it doesn't work, you may try to 'guess' the file encoding by yourself. The menu entry \"Tools->Encoding\" or the :FencView command will help you do that.\r\n\r\nIf you need fencview to detect encoding of every file, set g:fencview_autodetect option to 1 in your vimrc. This will slightly impact loading time, so it is disabled by default.\r\n\r\nNow FencView allows the use of an external program to determine the file encoding. It may give you better performance, or better accuracy, in some cases. https:\/\/github.com\/adah1972\/tellenc","4":"Have you ever met that after opening a text file with some kind of encoding you got a bunch of unreadable mess? If so, you need fencview.vim.\r\n\r\nNormally, vim detects file encoding based on 'fileencodings' option. For example, if we set this option like this: set fileencodings=ucs-bom,GB2312,big5 Firstly vim try to read file bom. If there is no bom, vim will try to decode the file with GB2312. Unfortunately, the GB2312 and big5 have a lot of overlapped code-points which could lead to a big5-encoded file be decoded with GB2312 by mistake. Then you got mess.\r\n\r\nThe 'vencview' uses another approach, let me show you how. As we know, take Chinese for example, the occurrence frequency of every character in a normal article is different. For example, '的' is a high frequency character which is encoded to 0xb5c4 in GB2312. However, in Big5 0xb5c4 is the code point for '腔' which is much less frequently used. So we can \"guess\" the encoding of a file by count up the frequently used characters. It is not 100% accurate but works in most cases.\r\n\r\nThe user manual is embeded in fencview.vim, refer to it if you'd like to custmize this script.\r\n\r\nIf you encounter a file that fencview can not handle, you're more than welcome to send it to me in order to improve the algrithm, but take care of the sensitive data before you do that.\r\n\r\nHow to use\r\nBasically, you need this plugin only when you ran into some messy code. In this case you need fencview to auto detect the file encoding. Either click the menu entry: \"Tools->Encoding->Auto Detect\" or use this command: :FencAutoDetect and probably that's all.\r\n\r\nIf it doesn't work, you may try to 'guess' the file encoding by yourself. The menu entry \"Tools->Encoding\" or the :FencView command will help you do that.\r\n\r\nIf you need fencview to detect encoding of every file, set g:fencview_autodetect option to 1 in your vimrc. This will slightly impact loading time, so it is disabled by default.\r\n\r\nNow FencView allows the use of an external program to determine the file encoding. It may give you better performance, or better accuracy, in some cases. https:\/\/github.com\/adah1972\/tellenc","install_details":"Simply put fencview.vim into 'plugin' directory and that's all.","5":"Simply put fencview.vim into 'plugin' directory and that's all.","first_name":"Ming","6":"Ming","last_name":"Bai","7":"Bai","releases":[{"0":"1708","vim_version":"7.0","1":"7.0","script_version":"4.9","2":"4.9","version_comment":"Fix three issues:\r\n- Non-ASCII file names cause failures after 7.4.122.\r\n- Command \":FencManualEncoding\" and menu Tools > Encoding behave differently.\r\n- Modeline does not change the file encoding when a document is reloaded.","3":"Fix three issues:\r\n- Non-ASCII file names cause failures after 7.4.122.\r\n- Command \":FencManualEncoding\" and menu Tools > Encoding behave differently.\r\n- Modeline does not change the file encoding when a document is reloaded.","package":"fencview.vim","4":"fencview.vim","src_id":"21657","5":"21657","creation_date":"1395662023","6":"1395662023"},{"0":"1708","vim_version":"7.0","1":"7.0","script_version":"4.8","2":"4.8","version_comment":"Set and restore cpoptions to make sure line continuation works","3":"Set and restore cpoptions to make sure line continuation works","package":"fencview.vim","4":"fencview.vim","src_id":"17381","5":"17381","creation_date":"1328354539","6":"1328354539"},{"0":"1708","vim_version":"7.0","1":"7.0","script_version":"4.7","2":"4.7","version_comment":"Fix the bug that a modified buffer may be reloaded (:e!) unintentionally.","3":"Fix the bug that a modified buffer may be reloaded (:e!) unintentionally.","package":"fencview.vim","4":"fencview.vim","src_id":"15376","5":"15376","creation_date":"1301902242","6":"1301902242"},{"0":"1708","vim_version":"7.0","1":"7.0","script_version":"4.6","2":"4.6","version_comment":"Progress bar no longer used for better compatibility; one may use  g:fencview_checklines=0 to check all lines; do not change the current file encoding if no valid multi-byte encoding is detected.","3":"Progress bar no longer used for better compatibility; one may use  g:fencview_checklines=0 to check all lines; do not change the current file encoding if no valid multi-byte encoding is detected.","package":"fencview.vim","4":"fencview.vim","src_id":"9649","5":"9649","creation_date":"1229004883","6":"1229004883"},{"0":"1708","vim_version":"7.0","1":"7.0","script_version":"4.5","2":"4.5","version_comment":"Add a workaround (UNIX only) for earlier Vim versions where shellescape() is not defined; avoid using `y$' to prevent issues when folding is used (contributed by Ingo Karkat).","3":"Add a workaround (UNIX only) for earlier Vim versions where shellescape() is not defined; avoid using `y$' to prevent issues when folding is used (contributed by Ingo Karkat).","package":"fencview.vim","4":"fencview.vim","src_id":"9225","5":"9225","creation_date":"1220600354","6":"1220600354"},{"0":"1708","vim_version":"7.0","1":"7.0","script_version":"4.4","2":"4.4","version_comment":"Fix two problems found under Unix:\r\n1) Big5 can be loosely used for CP950;\r\n2) g:legacy_encoding can be wrongly guessed (it should not be used).","3":"Fix two problems found under Unix:\r\n1) Big5 can be loosely used for CP950;\r\n2) g:legacy_encoding can be wrongly guessed (it should not be used).","package":"fencview.vim","4":"fencview.vim","src_id":"8745","5":"8745","creation_date":"1212389841","6":"1212389841"},{"0":"1708","vim_version":"7.0","1":"7.0","script_version":"4.3","2":"4.3","version_comment":"Make it run more smoothly under Windows with my gVim build (http:\/\/wyw.dcweb.cn\/#download).","3":"Make it run more smoothly under Windows with my gVim build (http:\/\/wyw.dcweb.cn\/#download).","package":"fencview.vim","4":"fencview.vim","src_id":"7994","5":"7994","creation_date":"1196144204","6":"1196144204"},{"0":"1708","vim_version":"7.0","1":"7.0","script_version":"4.2","2":"4.2","version_comment":"update","3":"update","package":"fencview.vim","4":"fencview.vim","src_id":"7166","5":"7166","creation_date":"1180055492","6":"1180055492"},{"0":"1708","vim_version":"7.0","1":"7.0","script_version":"4.1","2":"4.1","version_comment":"some improvements","3":"some improvements","package":"fencview.vim","4":"fencview.vim","src_id":"7149","5":"7149","creation_date":"1179798132","6":"1179798132"},{"0":"1708","vim_version":"7.0","1":"7.0","script_version":"4.0","2":"4.0","version_comment":"It merges functionality in multienc.vim: allows the use of an external program to determine the file encoding; use the http-equiv meta tag to help decide the file encoding; use the fileencoding modeline to help decide the file encoding; autodetect the encoding of .txt, .htm, and .html files; add a new command FencManualEncoding to override the encoding where autodetection affects the normal ++enc. Also some minor fixes are made.","3":"It merges functionality in multienc.vim: allows the use of an external program to determine the file encoding; use the http-equiv meta tag to help decide the file encoding; use the fileencoding modeline to help decide the file encoding; autodetect the encoding of .txt, .htm, and .html files; add a new command FencManualEncoding to override the encoding where autodetection affects the normal ++enc. Also some minor fixes are made.","package":"fencview.vim","4":"fencview.vim","src_id":"7061","5":"7061","creation_date":"1178161758","6":"1178161758"},{"0":"1708","vim_version":"7.0","1":"7.0","script_version":"3.2","2":"3.2","version_comment":"bug fix: set syntax on after auto detect","3":"bug fix: set syntax on after auto detect","package":"fencview.vim","4":"fencview.vim","src_id":"6833","5":"6833","creation_date":"1172991159","6":"1172991159"},{"0":"1708","vim_version":"7.0","1":"7.0","script_version":"3.1","2":"3.1","version_comment":"A lot of improvements.","3":"A lot of improvements.","package":"fencview.vim","4":"fencview.vim","src_id":"6507","5":"6507","creation_date":"1165872972","6":"1165872972"},{"0":"1708","vim_version":"7.0","1":"7.0","script_version":"2.3","2":"2.3","version_comment":"Now it can auto detect the file encodings. You just need to select \"Auto detect\" from the menu or use :FencAutoDetect command to let it detect the fileencoding automatically.\r\nSupported encodings:\r\nutf-8\r\ncp936(GBK)\r\ncp950(big5)\r\ncp932(sjis)\r\n","3":"Now it can auto detect the file encodings. You just need to select \"Auto detect\" from the menu or use :FencAutoDetect command to let it detect the fileencoding automatically.\r\nSupported encodings:\r\nutf-8\r\ncp936(GBK)\r\ncp950(big5)\r\ncp932(sjis)\r\n","package":"fencview.vim","4":"fencview.vim","src_id":"6476","5":"6476","creation_date":"1164686107","6":"1164686107"},{"0":"1708","vim_version":"7.0","1":"7.0","script_version":"1.2","2":"1.2","version_comment":"Some bug fix.","3":"Some bug fix.","package":"fencview.vim","4":"fencview.vim","src_id":"6425","5":"6425","creation_date":"1163661329","6":"1163661329"},{"0":"1708","vim_version":"6.0","1":"6.0","script_version":"1.1","2":"1.1","version_comment":"Now, you can select a file encoding from the menu, just like what you did in Firefox\/IE.\r\nScreenshot:\r\nhttp:\/\/mbbill.googlepages.com\/fenc.png\r\n","3":"Now, you can select a file encoding from the menu, just like what you did in Firefox\/IE.\r\nScreenshot:\r\nhttp:\/\/mbbill.googlepages.com\/fenc.png\r\n","package":"fencview.vim","4":"fencview.vim","src_id":"6422","5":"6422","creation_date":"1163578924","6":"1163578924"},{"0":"1708","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"fencview.vim","4":"fencview.vim","src_id":"6417","5":"6417","creation_date":"1163540353","6":"1163540353"}]},"1707":{"script_id":"1707","0":"1707","script_name":"php_getset.vim","1":"php_getset.vim","script_type":"ftplugin","2":"ftplugin","summary":"Automatically add getter\/setters for PHP4 properties","3":"Automatically add getter\/setters for PHP4 properties","description":"This script is modification of: \r\n\"Automatically add getter\/setters for Java properties (including array-based)\"\r\nby Pete Kazmier.\r\n\r\nThis filetype plugin enables a user to automatically add getter\/setter\r\nmethods for PHP properties.  The script will insert a getter, setter,\r\nor both depending on the command\/mapping invoked.  Users can select\r\nproperties one at a time, or in bulk (via a visual block or specifying a\r\nrange).  In either case, the selected block may include comments as they\r\nwill be ignored during the parsing.  For example, you could select all\r\nof these properties with a single visual block.\r\n\r\nclass Test \r\n{ \r\n   var $count;\r\n\r\n   var $name;\r\n\r\n   var $address;\r\n}\r\n\r\n\r\nThe getters\/setters that are inserted can be configured by the user.\r\nFirst, the insertion point can be selected.  It can be one of the\r\nfollowing: before the current line \/ block, after the current line \/\r\nblock, or at the end of the class (default).  Finally, the text that is\r\ninserted can be configured by defining your own templates.  This allows\r\nthe user to format for his\/her coding style.  For example, the default\r\nvalue for s:phpgetset_getterTemplate is:\r\n\r\n    \/**\r\n     * Get %varname%.\r\n     *\r\n     * @return %varname%\r\n     *\/\r\n    function %funcname%()\r\n    {\r\n        return %varname%;\r\n    }\r\n\r\nWhere the items surrounded by % are parameters that are substituted when\r\nthe script is invoked on a particular property.  For more information on\r\nconfiguration, please see the section below on the INTERFACE.\r\n\r\nINTERFACE (commands, mappings, and variables)\r\nThe following section documents the commands, mappings, and variables\r\nused to customize the behavior of this script.  \r\n\r\nCommands:\r\n  :InsertGetterSetter\r\n      Inserts a getter\/setter for the property on the current line, or\r\n      the range of properties specified via a visual block or x,y range\r\n      notation.  The user is prompted to determine what type of method\r\n      to insert.\r\n\r\n  :InsertGetterOnly\r\n      Inserts a getter for the property on the current line, or the\r\n      range of properties specified via a visual block or x,y range\r\n      notation.  The user is not prompted.\r\n\r\n  :InsertSetterOnly\r\n      Inserts a setter for the property on the current line, or the\r\n      range of properties specified via a visual block or x,y range\r\n      notation.  The user is not prompted.\r\n\r\n  :InsertBothGetterSetter\r\n      Inserts a getter and setter for the property on the current line,\r\n      or the range of properties specified via a visual block or x,y\r\n      range notation.  The user is not prompted.\r\n\r\n\r\nMappings:\r\n  The following mappings are pre-defined.  You can disable the mappings\r\n  by setting a variable (see the Variables section below).  The default\r\n  key mappings use the <LocalLeader> which is the backslash key by\r\n  default '\\'.  This can also be configured via a variable (see below).\r\n\r\n  <LocalLeader>p   (or <Plug>JavagetsetInsertGetterSetter)\r\n      Inserts a getter\/setter for the property on the current line, or\r\n      the range of properties specified via a visual block.  User is\r\n      prompted for choice.\r\n\r\n  <LocalLeader>g   (or <Plug>JavagetsetInsertGetterOnly)\r\n      Inserts a getter for the property on the current line, or the\r\n      range of properties specified via a visual block.  User is not\r\n      prompted.\r\n\r\n  <LocalLeader>s   (or <Plug>JavagetsetInsertSetterOnly)\r\n      Inserts a getter for the property on the current line, or the\r\n      range of properties specified via a visual block.  User is not\r\n      prompted.\r\n\r\n  <LocalLeader>b   (or <Plug>JavagetsetInsertBothGetterSetter)\r\n      Inserts both a getter and setter for the property on the current\r\n      line, or the range of properties specified via a visual block.\r\n      User is not prompted.\r\n\r\n  If you want to define your own mapping, you can map whatever you want\r\n  to <Plug>JavagetsetInsertGetterSetter (or any of the other <Plug>s\r\n  defined above).  For example,\r\n\r\n      map <buffer> <C-p> <Plug>JavagetsetInsertGetterSetter\r\n\r\n  When you define your own mapping, the default mapping does not get\r\n  set, only the mapping you specify.  \r\n\r\nVariables:\r\n  The following variables allow you to customize the behavior of this\r\n  script so that you do not need to make changes directly to the script.\r\n  These variables can be set in your vimrc.\r\n\r\n  no_plugin_maps\r\n    Setting this variable will disable all key mappings defined by any\r\n    of your plugins (if the plugin writer adhered to the standard\r\n    convention documented in the scripting section of the VIM manual)\r\n    including this one.\r\n\r\n  no_php_maps\r\n    Setting this variable will disable all key mappings defined by any\r\n    php specific plugin including this one.\r\n\r\n  maplocalleader\r\n    By default, the key mappings defined by this script use\r\n    <LocalLeader> which is the backslash character by default.  You can\r\n    change this by setting this variable to a different key.  For\r\n    example, if you want to use the comma-key, you can add this line to\r\n    your vimrc:\r\n      \r\n        let maplocalleader = ','\r\n\r\n  b:phpgetset_insertPosition\r\n    This variable determines the location where the getter and\/or setter\r\n    will be inserted.  Currently, three positions have been defined:\r\n\r\n        0 - insert at the end of the class (default)\r\n        1 - insert before the current line \/ block\r\n        2 - insert after the current line \/ block\r\n\r\n  b:phpgetset_getterTemplate\r\n  b:phpgetset_setterTemplate\r\n    These variables determine the text that will be inserted for a\r\n    getter, setter, array-based getter, and array-based setter\r\n    respectively.  The templates may contain the following placeholders\r\n    which will be substituted by their appropriate values at insertion\r\n    time:\r\n\r\n        %varname%       The name of the property\r\n        %funcname%      The method name (\"getXzy\" or \"setXzy\")\r\n\r\n    For example, if you wanted to set the default getter template so\r\n    that it would produce the following block of code for a property\r\n    defined as \"var $name\":\r\n\r\n        \/**\r\n         * Get name.\r\n         * @return name\r\n         *\/\r\n       function getName() { return $this->name; }\r\n    \r\n    This block of code can be produced by adding the following variable\r\n    definition to your vimrc file.\r\n\r\n        let b:phpgetset_getterTemplate = \r\n          \\ \"\\n\" .\r\n          \\ \"\/**\\n\" .\r\n          \\ \" * Get %varname%.\\n\" .\r\n          \\ \" * @return %varname%\\n\" .\r\n          \\ \" *\/\\n\" .\r\n          \\ \"%function %funcname%() { return $this->%varname%; }\"\r\n\r\n    The defaults for these variables are defined in the script.  For\r\n    both the getterTemplate and setterTemplate, there is a corresponding\r\n    array-baded template that is invoked if a property is array-based.\r\n    This allows you to set indexed-based getters\/setters if you desire.\r\n    This is the default behavior.\r\n","4":"This script is modification of: \r\n\"Automatically add getter\/setters for Java properties (including array-based)\"\r\nby Pete Kazmier.\r\n\r\nThis filetype plugin enables a user to automatically add getter\/setter\r\nmethods for PHP properties.  The script will insert a getter, setter,\r\nor both depending on the command\/mapping invoked.  Users can select\r\nproperties one at a time, or in bulk (via a visual block or specifying a\r\nrange).  In either case, the selected block may include comments as they\r\nwill be ignored during the parsing.  For example, you could select all\r\nof these properties with a single visual block.\r\n\r\nclass Test \r\n{ \r\n   var $count;\r\n\r\n   var $name;\r\n\r\n   var $address;\r\n}\r\n\r\n\r\nThe getters\/setters that are inserted can be configured by the user.\r\nFirst, the insertion point can be selected.  It can be one of the\r\nfollowing: before the current line \/ block, after the current line \/\r\nblock, or at the end of the class (default).  Finally, the text that is\r\ninserted can be configured by defining your own templates.  This allows\r\nthe user to format for his\/her coding style.  For example, the default\r\nvalue for s:phpgetset_getterTemplate is:\r\n\r\n    \/**\r\n     * Get %varname%.\r\n     *\r\n     * @return %varname%\r\n     *\/\r\n    function %funcname%()\r\n    {\r\n        return %varname%;\r\n    }\r\n\r\nWhere the items surrounded by % are parameters that are substituted when\r\nthe script is invoked on a particular property.  For more information on\r\nconfiguration, please see the section below on the INTERFACE.\r\n\r\nINTERFACE (commands, mappings, and variables)\r\nThe following section documents the commands, mappings, and variables\r\nused to customize the behavior of this script.  \r\n\r\nCommands:\r\n  :InsertGetterSetter\r\n      Inserts a getter\/setter for the property on the current line, or\r\n      the range of properties specified via a visual block or x,y range\r\n      notation.  The user is prompted to determine what type of method\r\n      to insert.\r\n\r\n  :InsertGetterOnly\r\n      Inserts a getter for the property on the current line, or the\r\n      range of properties specified via a visual block or x,y range\r\n      notation.  The user is not prompted.\r\n\r\n  :InsertSetterOnly\r\n      Inserts a setter for the property on the current line, or the\r\n      range of properties specified via a visual block or x,y range\r\n      notation.  The user is not prompted.\r\n\r\n  :InsertBothGetterSetter\r\n      Inserts a getter and setter for the property on the current line,\r\n      or the range of properties specified via a visual block or x,y\r\n      range notation.  The user is not prompted.\r\n\r\n\r\nMappings:\r\n  The following mappings are pre-defined.  You can disable the mappings\r\n  by setting a variable (see the Variables section below).  The default\r\n  key mappings use the <LocalLeader> which is the backslash key by\r\n  default '\\'.  This can also be configured via a variable (see below).\r\n\r\n  <LocalLeader>p   (or <Plug>JavagetsetInsertGetterSetter)\r\n      Inserts a getter\/setter for the property on the current line, or\r\n      the range of properties specified via a visual block.  User is\r\n      prompted for choice.\r\n\r\n  <LocalLeader>g   (or <Plug>JavagetsetInsertGetterOnly)\r\n      Inserts a getter for the property on the current line, or the\r\n      range of properties specified via a visual block.  User is not\r\n      prompted.\r\n\r\n  <LocalLeader>s   (or <Plug>JavagetsetInsertSetterOnly)\r\n      Inserts a getter for the property on the current line, or the\r\n      range of properties specified via a visual block.  User is not\r\n      prompted.\r\n\r\n  <LocalLeader>b   (or <Plug>JavagetsetInsertBothGetterSetter)\r\n      Inserts both a getter and setter for the property on the current\r\n      line, or the range of properties specified via a visual block.\r\n      User is not prompted.\r\n\r\n  If you want to define your own mapping, you can map whatever you want\r\n  to <Plug>JavagetsetInsertGetterSetter (or any of the other <Plug>s\r\n  defined above).  For example,\r\n\r\n      map <buffer> <C-p> <Plug>JavagetsetInsertGetterSetter\r\n\r\n  When you define your own mapping, the default mapping does not get\r\n  set, only the mapping you specify.  \r\n\r\nVariables:\r\n  The following variables allow you to customize the behavior of this\r\n  script so that you do not need to make changes directly to the script.\r\n  These variables can be set in your vimrc.\r\n\r\n  no_plugin_maps\r\n    Setting this variable will disable all key mappings defined by any\r\n    of your plugins (if the plugin writer adhered to the standard\r\n    convention documented in the scripting section of the VIM manual)\r\n    including this one.\r\n\r\n  no_php_maps\r\n    Setting this variable will disable all key mappings defined by any\r\n    php specific plugin including this one.\r\n\r\n  maplocalleader\r\n    By default, the key mappings defined by this script use\r\n    <LocalLeader> which is the backslash character by default.  You can\r\n    change this by setting this variable to a different key.  For\r\n    example, if you want to use the comma-key, you can add this line to\r\n    your vimrc:\r\n      \r\n        let maplocalleader = ','\r\n\r\n  b:phpgetset_insertPosition\r\n    This variable determines the location where the getter and\/or setter\r\n    will be inserted.  Currently, three positions have been defined:\r\n\r\n        0 - insert at the end of the class (default)\r\n        1 - insert before the current line \/ block\r\n        2 - insert after the current line \/ block\r\n\r\n  b:phpgetset_getterTemplate\r\n  b:phpgetset_setterTemplate\r\n    These variables determine the text that will be inserted for a\r\n    getter, setter, array-based getter, and array-based setter\r\n    respectively.  The templates may contain the following placeholders\r\n    which will be substituted by their appropriate values at insertion\r\n    time:\r\n\r\n        %varname%       The name of the property\r\n        %funcname%      The method name (\"getXzy\" or \"setXzy\")\r\n\r\n    For example, if you wanted to set the default getter template so\r\n    that it would produce the following block of code for a property\r\n    defined as \"var $name\":\r\n\r\n        \/**\r\n         * Get name.\r\n         * @return name\r\n         *\/\r\n       function getName() { return $this->name; }\r\n    \r\n    This block of code can be produced by adding the following variable\r\n    definition to your vimrc file.\r\n\r\n        let b:phpgetset_getterTemplate = \r\n          \\ \"\\n\" .\r\n          \\ \"\/**\\n\" .\r\n          \\ \" * Get %varname%.\\n\" .\r\n          \\ \" * @return %varname%\\n\" .\r\n          \\ \" *\/\\n\" .\r\n          \\ \"%function %funcname%() { return $this->%varname%; }\"\r\n\r\n    The defaults for these variables are defined in the script.  For\r\n    both the getterTemplate and setterTemplate, there is a corresponding\r\n    array-baded template that is invoked if a property is array-based.\r\n    This allows you to set indexed-based getters\/setters if you desire.\r\n    This is the default behavior.\r\n","install_details":"1. Copy the script to your ${HOME}\/.vim\/ftplugins directory and make\r\n   sure its named \"php_getset.vim\" or \"php_something.vim\" where\r\n   \"something\" can be anything you want.  \r\n\r\n2. (Optional) Customize the mapping and\/or templates.  You can create\r\n   your own filetype plugin (just make sure its loaded before this one)\r\n   and set the variables in there (i.e. ${HOME}\/.vim\/ftplugin\/php.vim)","5":"1. Copy the script to your ${HOME}\/.vim\/ftplugins directory and make\r\n   sure its named \"php_getset.vim\" or \"php_something.vim\" where\r\n   \"something\" can be anything you want.  \r\n\r\n2. (Optional) Customize the mapping and\/or templates.  You can create\r\n   your own filetype plugin (just make sure its loaded before this one)\r\n   and set the variables in there (i.e. ${HOME}\/.vim\/ftplugin\/php.vim)","first_name":"Antoni","6":"Antoni","last_name":"Jakubiak","7":"Jakubiak","releases":[{"0":"1707","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"php_getset.vim","4":"php_getset.vim","src_id":"6413","5":"6413","creation_date":"1163481739","6":"1163481739"}]},"1706":{"script_id":"1706","0":"1706","script_name":"Marks Browser","1":"Marks Browser","script_type":"utility","2":"utility","summary":"A graphical marks browser","3":"A graphical marks browser","description":"Description:\r\nThis script provides a graphical browsers of the user marks for the local\r\nfile [a-z]\r\n\r\nHelp:\r\nTo open the browser, use the :MarksBrowser command\r\nThe select the a mark to jump to, use <CR> or <2-LeftMouse>\r\nTo delete a mark, press d\r\n\r\nTo have the browser window not close itself after you jump to a mark, set the\r\nmarksCloseWhenSelected in your ~\/.vimrc file\r\n\tExample: let marksCloseWhenSelected = 0\r\n","4":"Description:\r\nThis script provides a graphical browsers of the user marks for the local\r\nfile [a-z]\r\n\r\nHelp:\r\nTo open the browser, use the :MarksBrowser command\r\nThe select the a mark to jump to, use <CR> or <2-LeftMouse>\r\nTo delete a mark, press d\r\n\r\nTo have the browser window not close itself after you jump to a mark, set the\r\nmarksCloseWhenSelected in your ~\/.vimrc file\r\n\tExample: let marksCloseWhenSelected = 0\r\n","install_details":"Put this file into your $HOME\/.vim\/plugin directory.\r\n","5":"Put this file into your $HOME\/.vim\/plugin directory.\r\n","first_name":"Viktor","6":"Viktor","last_name":"Kojouharov","7":"Kojouharov","releases":[{"0":"1706","vim_version":"7.0","1":"7.0","script_version":"0.9","2":"0.9","version_comment":"Initial upload","3":"Initial upload","package":"marksbrowser.vim","4":"marksbrowser.vim","src_id":"6408","5":"6408","creation_date":"1163411670","6":"1163411670"}]},"1705":{"script_id":"1705","0":"1705","script_name":"redcode.vim","1":"redcode.vim","script_type":"syntax","2":"syntax","summary":"Redcode '88 '94 and Pspace syntax for Corewars","3":"Redcode '88 '94 and Pspace syntax for Corewars","description":"This syntax file supports the REDCODE '88 or '94 (with or without Pspace extensions) languages as defined in the ICWS'94 Draft (extended).\r\n\r\n     http:\/\/www.koth.org\/info\/pmars-redcode-94.txt\r\n\r\nThe language was first popularized in a March 1984 Scientific American article, Core War Guidelines, by A. K. Dewdney and D. G. Jones.\r\n\r\nThis implementation can be configured to flag elements of Redcode '94 when used in coding Redcode '88 warriors. It also highlights line-continuations (responsible for a well-known problem with the program Marcia Trionfale 1.3).\r\n\r\n","4":"This syntax file supports the REDCODE '88 or '94 (with or without Pspace extensions) languages as defined in the ICWS'94 Draft (extended).\r\n\r\n     http:\/\/www.koth.org\/info\/pmars-redcode-94.txt\r\n\r\nThe language was first popularized in a March 1984 Scientific American article, Core War Guidelines, by A. K. Dewdney and D. G. Jones.\r\n\r\nThis implementation can be configured to flag elements of Redcode '94 when used in coding Redcode '88 warriors. It also highlights line-continuations (responsible for a well-known problem with the program Marcia Trionfale 1.3).\r\n\r\n","install_details":"These instructions assume a linux|unix type system. Similar steps apply for MS Windows users.\r\n\r\nTo use the syntax file copy it into the directory ~\/.vim\/syntax (create the direcory path if not already present).\r\n\r\nCreate a file named red.vim in ~\/.vim\/ftdetect (again creating the directory if not already present).\r\nThis file defines .red as the filetype of REDCODE source files. It should contain:\r\n\r\n                augroup filetypedetect\r\n                au BufRead,BufNewFile *.red setf redcode\r\n                augroup END\r\n            \r\n\r\nThe following options can be used in your .vimrc initialization file to control the degree of syntax checking:\r\nThey are all commented out by default.\r\n\r\n                \"Remove quote characters on subsequent lines to enable options\r\n\r\n                \"let redcode_88_only = 1\r\n                \"let redcode_94_only = 1\r\n                \"let redcode_highlight_numbers=1\r\n            \r\n\r\nThe default behaviour is to accept '88 '94 and Pspace syntax and to not highlight numbers. ","5":"These instructions assume a linux|unix type system. Similar steps apply for MS Windows users.\r\n\r\nTo use the syntax file copy it into the directory ~\/.vim\/syntax (create the direcory path if not already present).\r\n\r\nCreate a file named red.vim in ~\/.vim\/ftdetect (again creating the directory if not already present).\r\nThis file defines .red as the filetype of REDCODE source files. It should contain:\r\n\r\n                augroup filetypedetect\r\n                au BufRead,BufNewFile *.red setf redcode\r\n                augroup END\r\n            \r\n\r\nThe following options can be used in your .vimrc initialization file to control the degree of syntax checking:\r\nThey are all commented out by default.\r\n\r\n                \"Remove quote characters on subsequent lines to enable options\r\n\r\n                \"let redcode_88_only = 1\r\n                \"let redcode_94_only = 1\r\n                \"let redcode_highlight_numbers=1\r\n            \r\n\r\nThe default behaviour is to accept '88 '94 and Pspace syntax and to not highlight numbers. ","first_name":"Philip","6":"Philip","last_name":"Thorne","7":"Thorne","releases":[{"0":"1705","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"redcode.vim","4":"redcode.vim","src_id":"6385","5":"6385","creation_date":"1162847064","6":"1162847064"}]},"1704":{"script_id":"1704","0":"1704","script_name":"vdb-duplicated","1":"vdb-duplicated","script_type":"utility","2":"utility","summary":"Interrupted upload duplication, do not download","3":"Interrupted upload duplication, do not download","description":"Please see vdb.vim instead which is vimscript #1703","4":"Please see vdb.vim instead which is vimscript #1703","install_details":"Don't install","5":"Don't install","first_name":"James","6":"James","last_name":"Dominy","7":"Dominy","releases":[{"0":"1704","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"vdb.tar.gz","4":"vdb.tar.gz","src_id":"6375","5":"6375","creation_date":"1162570328","6":"1162570328"}]},"1703":{"script_id":"1703","0":"1703","script_name":"vdb.vim","1":"vdb.vim","script_type":"utility","2":"utility","summary":"Vim becomes an integrated debugger for any language with a text based debugger","3":"Vim becomes an integrated debugger for any language with a text based debugger","description":"VDB will eventually provide a generic interface to any text based, line oriented, debugger, such as gdb, or pdb. Right now it only works with gdb, but eventually, it is intended to be made extensible by use of \"interface configuration files\" [potentially in XML, but that's probably overkill] specifying what the debugger of choice considers the commands for various actions to be. It only works on operating systems that support pty's, i.e. not windows. Currently users are able to step over\/into a particular line of code, execute until the current cursor line is reached, set watches on expressions, view the output of their programs in a vim buffer, and interactively enter data into the same buffer when their program requires input. More powerful actions can be performed by using the debug console, which gives you direct access to the back-end debugger process. Type commands in here, and see their results both in text, and reflected in the various status displays within vim. You will need vim version 7.0 or higher. Actually it might work on lower versions, I haven't tested yet. For more info check out the README file that's bundled in the package.\r\n\r\nYou might want to check out pygdb (vimscript #2270) if you prefer GUI debuggers, it looks very promising.\r\n\r\nIf you want to contact me, simply fire off a message to vimdebugger@gmail.com.","4":"VDB will eventually provide a generic interface to any text based, line oriented, debugger, such as gdb, or pdb. Right now it only works with gdb, but eventually, it is intended to be made extensible by use of \"interface configuration files\" [potentially in XML, but that's probably overkill] specifying what the debugger of choice considers the commands for various actions to be. It only works on operating systems that support pty's, i.e. not windows. Currently users are able to step over\/into a particular line of code, execute until the current cursor line is reached, set watches on expressions, view the output of their programs in a vim buffer, and interactively enter data into the same buffer when their program requires input. More powerful actions can be performed by using the debug console, which gives you direct access to the back-end debugger process. Type commands in here, and see their results both in text, and reflected in the various status displays within vim. You will need vim version 7.0 or higher. Actually it might work on lower versions, I haven't tested yet. For more info check out the README file that's bundled in the package.\r\n\r\nYou might want to check out pygdb (vimscript #2270) if you prefer GUI debuggers, it looks very promising.\r\n\r\nIf you want to contact me, simply fire off a message to vimdebugger@gmail.com.","install_details":"Complete and comprehensive installation instructions are provided in the file quick-start.txt","5":"Complete and comprehensive installation instructions are provided in the file quick-start.txt","first_name":"James","6":"James","last_name":"Dominy","7":"Dominy","releases":[{"0":"1703","vim_version":"7.0","1":"7.0","script_version":"0.4.4","2":"0.4.4","version_comment":"vdb-0.4.4.tar.gz\t2010-02-08\r\n * Aoyama Shotaro: add a ruby interface\r\n * Aoyama Shotaro: fixed a typo in cpdb.py and made pdbout global\r\n * Aoyama Shotaro: using subprocess module instead of os,popen\r\n * hacked debuggers to be included in the main package hence forth\r\n * lots more, see change log in the README","3":"vdb-0.4.4.tar.gz\t2010-02-08\r\n * Aoyama Shotaro: add a ruby interface\r\n * Aoyama Shotaro: fixed a typo in cpdb.py and made pdbout global\r\n * Aoyama Shotaro: using subprocess module instead of os,popen\r\n * hacked debuggers to be included in the main package hence forth\r\n * lots more, see change log in the README","package":"vdb-0.4.4.tar.gz","4":"vdb-0.4.4.tar.gz","src_id":"12337","5":"12337","creation_date":"1265584140","6":"1265584140"}]},"1702":{"script_id":"1702","0":"1702","script_name":"edc support","1":"edc support","script_type":"ftplugin","2":"ftplugin","summary":"Syntax\/indent for edc files","3":"Syntax\/indent for edc files","description":"This vimball provides syntax highlighting and indentation for edc files, as well as embryo scripts embedded withing the edc files.\r\n\r\nIt also provides an omni completion script, which will complete all the usual keywords\/statements\/labels appropriately, as well as complete part names and program names when applicable","4":"This vimball provides syntax highlighting and indentation for edc files, as well as embryo scripts embedded withing the edc files.\r\n\r\nIt also provides an omni completion script, which will complete all the usual keywords\/statements\/labels appropriately, as well as complete part names and program names when applicable","install_details":"Open in vim, then :so %","5":"Open in vim, then :so %","first_name":"Viktor","6":"Viktor","last_name":"Kojouharov","7":"Kojouharov","releases":[{"0":"1702","vim_version":"7.0","1":"7.0","script_version":"2.0","2":"2.0","version_comment":"Updated the vimball to support lua syntax highlighting in edje, new keywords and completions","3":"Updated the vimball to support lua syntax highlighting in edje, new keywords and completions","package":"edc.vba","4":"edc.vba","src_id":"12700","5":"12700","creation_date":"1269464236","6":"1269464236"},{"0":"1702","vim_version":"7.0","1":"7.0","script_version":"1.5","2":"1.5","version_comment":"Updated syntax and completion for edc","3":"Updated syntax and completion for edc","package":"edc.vba","4":"edc.vba","src_id":"9695","5":"9695","creation_date":"1229596721","6":"1229596721"},{"0":"1702","vim_version":"7.0","1":"7.0","script_version":"1.4","2":"1.4","version_comment":"Update syntax and omni-completion for new edje types.","3":"Update syntax and omni-completion for new edje types.","package":"edc.vba","4":"edc.vba","src_id":"9433","5":"9433","creation_date":"1225881344","6":"1225881344"},{"0":"1702","vim_version":"7.0","1":"7.0","script_version":"1.3","2":"1.3","version_comment":"Fixed the indentation for the closing curly braces. Added support for the statement.substatement edc style for the syntax and omni-completion files (currently for only 1 depth)","3":"Fixed the indentation for the closing curly braces. Added support for the statement.substatement edc style for the syntax and omni-completion files (currently for only 1 depth)","package":"edc.vba","4":"edc.vba","src_id":"6781","5":"6781","creation_date":"1172242723","6":"1172242723"},{"0":"1702","vim_version":"7.0","1":"7.0","script_version":"1.2","2":"1.2","version_comment":"Completed the syntax file for edc. The completion file has been improved. It now contains all the blocks and labels, and can also complete names for the \"to*:\" label.","3":"Completed the syntax file for edc. The completion file has been improved. It now contains all the blocks and labels, and can also complete names for the \"to*:\" label.","package":"edc.vba","4":"edc.vba","src_id":"6391","5":"6391","creation_date":"1162995173","6":"1162995173"},{"0":"1702","vim_version":"7.0","1":"7.0","script_version":"1.1","2":"1.1","version_comment":"Minor changes to the syntax file.\r\nAdded an omni completion script","3":"Minor changes to the syntax file.\r\nAdded an omni completion script","package":"edc.vba","4":"edc.vba","src_id":"6380","5":"6380","creation_date":"1162766324","6":"1162766324"},{"0":"1702","vim_version":"7.0","1":"7.0","script_version":"1","2":"1","version_comment":"Initial upload","3":"Initial upload","package":"edc.vba","4":"edc.vba","src_id":"6373","5":"6373","creation_date":"1162558954","6":"1162558954"}]},"1701":{"script_id":"1701","0":"1701","script_name":"Remove Trailing Spaces","1":"Remove Trailing Spaces","script_type":"utility","2":"utility","summary":"removes the trailing space from the file","3":"removes the trailing space from the file","description":"removes the trailing space from the file when user will save   any changes\r\n\r\nTo force the time stamp to be not updated, use the command:\r\n             \t\t:NOMODSP\r\nTo change it back, use\r\n             \t\t:MODSP\r\n","4":"removes the trailing space from the file when user will save   any changes\r\n\r\nTo force the time stamp to be not updated, use the command:\r\n             \t\t:NOMODSP\r\nTo change it back, use\r\n             \t\t:MODSP\r\n","install_details":"","5":"","first_name":"Sudipta","6":"Sudipta","last_name":"Ghorui","7":"Ghorui","releases":[{"0":"1701","vim_version":"6.0","1":"6.0","script_version":"1.1","2":"1.1","version_comment":"Tested in FC 2","3":"Tested in FC 2","package":"RemoveTrailingSpace.vim","4":"RemoveTrailingSpace.vim","src_id":"7065","5":"7065","creation_date":"1178252751","6":"1178252751"},{"0":"1701","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"RemoveTrailingSpace.vim","4":"RemoveTrailingSpace.vim","src_id":"6371","5":"6371","creation_date":"1162520593","6":"1162520593"}]},"1700":{"script_id":"1700","0":"1700","script_name":"vimksh","1":"vimksh","script_type":"utility","2":"utility","summary":"Using MSWin Vim with MSWin SFU 3.5","3":"Using MSWin Vim with MSWin SFU 3.5","description":"For MS Windows XP users with Windows Services for Unix (SFU) 3.5 installed, the vimksh script enables the MS Windows version of Vim to use SFU commands and utilities for its shell commands (e.g., \":shell\" and \":!...\") as well as for its filter commands (e.g., \"1G!Gwc -cl\" followed by a quick \"u\"). No more dealing with \"cmd.exe\" -- you get to deal with ksh instead. The script has been tested with Vim 7.0, but should work with earlier Vim versions and with other versions of MS Windows that run SFU 3.5.","4":"For MS Windows XP users with Windows Services for Unix (SFU) 3.5 installed, the vimksh script enables the MS Windows version of Vim to use SFU commands and utilities for its shell commands (e.g., \":shell\" and \":!...\") as well as for its filter commands (e.g., \"1G!Gwc -cl\" followed by a quick \"u\"). No more dealing with \"cmd.exe\" -- you get to deal with ksh instead. The script has been tested with Vim 7.0, but should work with earlier Vim versions and with other versions of MS Windows that run SFU 3.5.","install_details":"The installation instructions are (1) put the script in a directory, (2) use SFU's chmod to make the script executable (\"chmod +x vimksh\"), and (3) add a \"set shell=...\" command to \"_vimrc\". That's basically it. It will be easier if the path to the script does not include embedded spaces, but that's just an escaping issue in the \"set shell\". As an example, if vimksh resides in \"c:\\home\", the \"_vimrc\" command (note the escaped spaces) would be:\r\n\r\n     set shell=c:\\windows\\system32\\posix.exe\\ \/u\\ \/c\\ \/dev\/fs\/C\/home\/vimksh\r\n\r\nThe installation instructions are also in the header comments of the script. Ordinarily, vimksh logs the requests (not the results) that it performs to \"vimksh.log\", so the directory containing vimksh must to be writable. Comments in the script describe how logging can be turned off.\r\n\r\nIf you encounter slow performance on your first few shell and filter commands, keep at it. I was seeing slow performance at first on Windows XP, but as soon as prefetch (or something) kicked in, performance became really good.","5":"The installation instructions are (1) put the script in a directory, (2) use SFU's chmod to make the script executable (\"chmod +x vimksh\"), and (3) add a \"set shell=...\" command to \"_vimrc\". That's basically it. It will be easier if the path to the script does not include embedded spaces, but that's just an escaping issue in the \"set shell\". As an example, if vimksh resides in \"c:\\home\", the \"_vimrc\" command (note the escaped spaces) would be:\r\n\r\n     set shell=c:\\windows\\system32\\posix.exe\\ \/u\\ \/c\\ \/dev\/fs\/C\/home\/vimksh\r\n\r\nThe installation instructions are also in the header comments of the script. Ordinarily, vimksh logs the requests (not the results) that it performs to \"vimksh.log\", so the directory containing vimksh must to be writable. Comments in the script describe how logging can be turned off.\r\n\r\nIf you encounter slow performance on your first few shell and filter commands, keep at it. I was seeing slow performance at first on Windows XP, but as soon as prefetch (or something) kicked in, performance became really good.","first_name":"Mark","6":"Mark","last_name":"Mathieu","7":"Mathieu","releases":[{"0":"1700","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"vimksh","4":"vimksh","src_id":"6367","5":"6367","creation_date":"1162477303","6":"1162477303"}]},"1699":{"script_id":"1699","0":"1699","script_name":"vimGTD","1":"vimGTD","script_type":"ftplugin","2":"ftplugin","summary":"frontend to PyGTD todo list manager","3":"frontend to PyGTD todo list manager","description":"vimGTD - Using 'Getting Things Done' in Vim\r\n--------------------------------------------------------------\r\nall plugin files under the Vim Copyright License\r\n\r\nOverview\r\n--------------\r\n\r\nPyGTD is  a simple  Getting Things  Done (GTD) system  based on  David Allen's\r\npersonal-productivity  book  and  Stephen  Covey's  'Seven  Habits  of  Highly\r\nEffective People'. It is implemented as Python script written by Keith Martin\r\n(http:\/\/96db.com\/pyGTD\/). The goal is to easily organize and prioritize your\r\ntodo lists.\r\n\r\nvimGTD is the Vim frontend to the Python program and includes such features as\r\nsyntax highlighting, file navigation support, and a quick help reference.","4":"vimGTD - Using 'Getting Things Done' in Vim\r\n--------------------------------------------------------------\r\nall plugin files under the Vim Copyright License\r\n\r\nOverview\r\n--------------\r\n\r\nPyGTD is  a simple  Getting Things  Done (GTD) system  based on  David Allen's\r\npersonal-productivity  book  and  Stephen  Covey's  'Seven  Habits  of  Highly\r\nEffective People'. It is implemented as Python script written by Keith Martin\r\n(http:\/\/96db.com\/pyGTD\/). The goal is to easily organize and prioritize your\r\ntodo lists.\r\n\r\nvimGTD is the Vim frontend to the Python program and includes such features as\r\nsyntax highlighting, file navigation support, and a quick help reference.","install_details":"Installation is fairly easy. Follow these steps:\r\n\r\n(i)   Copy the contents of the directory 'vim' (with all subdirectories as is)\r\n      to your local runtimepath (see ':help runtimepath' for various platforms).\r\n\r\n(ii)  After all the vim plugin files are copied, execute ':helptags ~\/.vim\/doc'\r\n      or your OS's equivalent to generate the new help tags.\r\n\r\n(iii) Rename the 'gtd.py' Python script (in directory PyGTD) to 'gtd' and copy\r\n      it to your system's execution path (on UNIX e.g. \/usr\/bin\/gtd or\r\n      \/usr\/local\/bin\/gtd).\r\n\r\n(iv)  You might want to define a shorthand for running GTD from within vim\r\n      (typically when you edit the todo.gtd file). The following mapping will\r\n      do:\r\n\r\n      map ,gtd :!gtd %<C-M>:e<C-M><C-M>\r\n\r\n      so that ',gtd' launches PyGTD.\r\n\r\n(v)   If you use vim in combination with the Mutt email client, try out\r\n      the following macro in your muttrc configuration:\r\n\r\n      macro index \\ch \"!vim ~\/GTD\/todo.gtd\\n\" \"start GTD\"\r\n      macro pager \\ch \"!vim ~\/GTD\/todo.gtd\\n\" \"start GTD\"\r\n\r\n      which binds <CTRL>h to vim opening todo.gtd in your $HOME\/GTD directory\r\n      using PyGTD (you might want to change the directory name).\r\n\r\n(vi)  Note that double-clicking on the context filenames (filenames surrounded\r\n      by brackets in the todo.gtd file) will automatically open them in a new\r\n      vim buffer for editing.\r\n\r\n(vii) Have fun using PyGTD with vim!","5":"Installation is fairly easy. Follow these steps:\r\n\r\n(i)   Copy the contents of the directory 'vim' (with all subdirectories as is)\r\n      to your local runtimepath (see ':help runtimepath' for various platforms).\r\n\r\n(ii)  After all the vim plugin files are copied, execute ':helptags ~\/.vim\/doc'\r\n      or your OS's equivalent to generate the new help tags.\r\n\r\n(iii) Rename the 'gtd.py' Python script (in directory PyGTD) to 'gtd' and copy\r\n      it to your system's execution path (on UNIX e.g. \/usr\/bin\/gtd or\r\n      \/usr\/local\/bin\/gtd).\r\n\r\n(iv)  You might want to define a shorthand for running GTD from within vim\r\n      (typically when you edit the todo.gtd file). The following mapping will\r\n      do:\r\n\r\n      map ,gtd :!gtd %<C-M>:e<C-M><C-M>\r\n\r\n      so that ',gtd' launches PyGTD.\r\n\r\n(v)   If you use vim in combination with the Mutt email client, try out\r\n      the following macro in your muttrc configuration:\r\n\r\n      macro index \\ch \"!vim ~\/GTD\/todo.gtd\\n\" \"start GTD\"\r\n      macro pager \\ch \"!vim ~\/GTD\/todo.gtd\\n\" \"start GTD\"\r\n\r\n      which binds <CTRL>h to vim opening todo.gtd in your $HOME\/GTD directory\r\n      using PyGTD (you might want to change the directory name).\r\n\r\n(vi)  Note that double-clicking on the context filenames (filenames surrounded\r\n      by brackets in the todo.gtd file) will automatically open them in a new\r\n      vim buffer for editing.\r\n\r\n(vii) Have fun using PyGTD with vim!","first_name":"Michael M.","6":"Michael M.","last_name":"Tung","7":"Tung","releases":[{"0":"1699","vim_version":"6.0","1":"6.0","script_version":"1.1","2":"1.1","version_comment":"fixed double-click mapping to be local","3":"fixed double-click mapping to be local","package":"vimGTD.tgz","4":"vimGTD.tgz","src_id":"6366","5":"6366","creation_date":"1162438401","6":"1162438401"},{"0":"1699","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"vimGTD.tgz","4":"vimGTD.tgz","src_id":"6354","5":"6354","creation_date":"1162259866","6":"1162259866"}]},"1698":{"script_id":"1698","0":"1698","script_name":"C_Epita","1":"C_Epita","script_type":"syntax","2":"syntax","summary":"Usefull for EPITA students","3":"Usefull for EPITA students","description":"This script will help you,  with the EPITA norme.\r\n * Headers are automaticaly generated on writing FILE\r\n * cindent is config\r\n * (norme checker) not yet implemented","4":"This script will help you,  with the EPITA norme.\r\n * Headers are automaticaly generated on writing FILE\r\n * cindent is config\r\n * (norme checker) not yet implemented","install_details":"copy the file in your plugin dir (ex : ~\/.vim\/plugin)","5":"copy the file in your plugin dir (ex : ~\/.vim\/plugin)","first_name":"Arnaud","6":"Arnaud","last_name":"GODET","7":"GODET","releases":[{"0":"1698","vim_version":"6.0","1":"6.0","script_version":"0.0.2","2":"0.0.2","version_comment":"Fix a bug in the generted HEADERS, who are more thn 80 columns.\r\nOn saving:\r\n* Generate Headers\r\n* Generate #ifndef for the .h files\r\n* Delete tailing white spaces\r\n* warn you if your function contains more than 25 lines\r\n* add a function <Esc>count_line_func who count the number of lines inside a C function","3":"Fix a bug in the generted HEADERS, who are more thn 80 columns.\r\nOn saving:\r\n* Generate Headers\r\n* Generate #ifndef for the .h files\r\n* Delete tailing white spaces\r\n* warn you if your function contains more than 25 lines\r\n* add a function <Esc>count_line_func who count the number of lines inside a C function","package":"c_epita.vim","4":"c_epita.vim","src_id":"6362","5":"6362","creation_date":"1162381233","6":"1162381233"},{"0":"1698","vim_version":"6.0","1":"6.0","script_version":"0.0.1","2":"0.0.1","version_comment":"Initial upload","3":"Initial upload","package":"c_epita.vim","4":"c_epita.vim","src_id":"6350","5":"6350","creation_date":"1162202007","6":"1162202007"}]},"1697":{"script_id":"1697","0":"1697","script_name":"surround.vim","1":"surround.vim","script_type":"utility","2":"utility","summary":"Delete\/change\/add parentheses\/quotes\/XML-tags\/much more with ease","3":"Delete\/change\/add parentheses\/quotes\/XML-tags\/much more with ease","description":"Surround.vim is all about \"surroundings\": parentheses, brackets, quotes, XML tags, and more.  The plugin provides mappings to easily delete, change and add such surroundings in pairs.  While it works under Vim 6, much of the functionality requires Vim 7.\r\n\r\nExamples follow.  It is difficult to provide good examples in the variable width font of this site; check the documentation for more.\r\n\r\nPress cs\"' (that's c, s, double quote, single quote) inside\r\n\r\n\"Hello world!\"\r\n\r\nto change it to\r\n\r\n'Hello world!'\r\n\r\nNow press cs'<q> to change it to\r\n\r\n<q>Hello world!<\/q>\r\n\r\nTo go full circle, press cst\" to get\r\n\r\n\"Hello world!\"\r\n\r\nTo remove the delimiters entirely, press ds\" .\r\n\r\nHello world!\r\n\r\nNow with the cursor on \"Hello\", press ysiw] (iw is a text object).\r\n\r\n[Hello] world!\r\n\r\nLet's make that braces and add some space (use \"}\" instead of \"{\" for no space): cs]{\r\n\r\n{ Hello } world!\r\n\r\nNow wrap the entire line in parentheses with yssb or yss) .\r\n\r\n({ Hello } world!)\r\n\r\nRevert to the original text: ds{ds)\r\n\r\nHello world!\r\n\r\nEmphasize hello: ysiw<em>\r\n\r\n<em>Hello<\/em> world!\r\n\r\nFinally, let's try out visual mode. Press a capital V (for linewise visual mode)\r\nfollowed by S<p>.\r\n\r\n<p>\r\n  Hello world!\r\n<\/p>\r\n\r\nThis plugin is very powerful for HTML and XML editing, a niche which currently seems underfilled in Vim land.  (As opposed to HTML\/XML *inserting*, for which many plugins are available).  Adding, changing, and removing pairs of tags simultaneously is a breeze.\r\n\r\nThe \".\" command will work with ds, cs, and yss if you install repeat.vim, vimscript #2136.\r\n\r\nAll feedback appreciated.\r\n\r\nhttp:\/\/github.com\/tpope\/vim-surround","4":"Surround.vim is all about \"surroundings\": parentheses, brackets, quotes, XML tags, and more.  The plugin provides mappings to easily delete, change and add such surroundings in pairs.  While it works under Vim 6, much of the functionality requires Vim 7.\r\n\r\nExamples follow.  It is difficult to provide good examples in the variable width font of this site; check the documentation for more.\r\n\r\nPress cs\"' (that's c, s, double quote, single quote) inside\r\n\r\n\"Hello world!\"\r\n\r\nto change it to\r\n\r\n'Hello world!'\r\n\r\nNow press cs'<q> to change it to\r\n\r\n<q>Hello world!<\/q>\r\n\r\nTo go full circle, press cst\" to get\r\n\r\n\"Hello world!\"\r\n\r\nTo remove the delimiters entirely, press ds\" .\r\n\r\nHello world!\r\n\r\nNow with the cursor on \"Hello\", press ysiw] (iw is a text object).\r\n\r\n[Hello] world!\r\n\r\nLet's make that braces and add some space (use \"}\" instead of \"{\" for no space): cs]{\r\n\r\n{ Hello } world!\r\n\r\nNow wrap the entire line in parentheses with yssb or yss) .\r\n\r\n({ Hello } world!)\r\n\r\nRevert to the original text: ds{ds)\r\n\r\nHello world!\r\n\r\nEmphasize hello: ysiw<em>\r\n\r\n<em>Hello<\/em> world!\r\n\r\nFinally, let's try out visual mode. Press a capital V (for linewise visual mode)\r\nfollowed by S<p>.\r\n\r\n<p>\r\n  Hello world!\r\n<\/p>\r\n\r\nThis plugin is very powerful for HTML and XML editing, a niche which currently seems underfilled in Vim land.  (As opposed to HTML\/XML *inserting*, for which many plugins are available).  Adding, changing, and removing pairs of tags simultaneously is a breeze.\r\n\r\nThe \".\" command will work with ds, cs, and yss if you install repeat.vim, vimscript #2136.\r\n\r\nAll feedback appreciated.\r\n\r\nhttp:\/\/github.com\/tpope\/vim-surround","install_details":"Extract to ~\/.vim, or ~\\vimfiles (Windows).  You'll need to regenerate helptags (fill in the install path below)\r\n\r\n:helptags ~\/.vim\/doc","5":"Extract to ~\/.vim, or ~\\vimfiles (Windows).  You'll need to regenerate helptags (fill in the install path below)\r\n\r\n:helptags ~\/.vim\/doc","first_name":"Tim","6":"Tim","last_name":"Pope","7":"Pope","releases":[{"0":"1697","vim_version":"7.0","1":"7.0","script_version":"2.2","2":"2.2","version_comment":"Keep HTML attributes when changing tags.\r\nSupport <Space><Space> as space replacement.\r\nBug fixes.","3":"Keep HTML attributes when changing tags.\r\nSupport <Space><Space> as space replacement.\r\nBug fixes.","package":"surround.zip","4":"surround.zip","src_id":"27781","5":"27781","creation_date":"1634088168","6":"1634088168"},{"0":"1697","vim_version":"7.0","1":"7.0","script_version":"2.1","2":"2.1","version_comment":"Handle arbitrary punctuation delimiters with cs and ds.\r\nDefault to automatic indenting.\r\nProvide cS to force surroundings on separate lines.\r\nSupport for disabling mappings only for insert mode.\r\nAdd repeat.vim support to surround with function.\r\nWork around 'nomagic'.","3":"Handle arbitrary punctuation delimiters with cs and ds.\r\nDefault to automatic indenting.\r\nProvide cS to force surroundings on separate lines.\r\nSupport for disabling mappings only for insert mode.\r\nAdd repeat.vim support to surround with function.\r\nWork around 'nomagic'.","package":"surround.zip","4":"surround.zip","src_id":"22892","5":"22892","creation_date":"1423422456","6":"1423422456"},{"0":"1697","vim_version":"7.0","1":"7.0","script_version":"2.0","2":"2.0","version_comment":"Fix vs with selection=exclusive.\r\nRemove `unnamedplus' from clipboard in addition to `unnamed'.\r\nKill vs.\r\nBump to Vim 7.\r\nAdd support for repeating ys commands.\r\nAdd support for repeating tags.\r\nDon't save deleted surrounding in unnamed register.\r\nFix deletion of delimiters on their own lines.","3":"Fix vs with selection=exclusive.\r\nRemove `unnamedplus' from clipboard in addition to `unnamed'.\r\nKill vs.\r\nBump to Vim 7.\r\nAdd support for repeating ys commands.\r\nAdd support for repeating tags.\r\nDon't save deleted surrounding in unnamed register.\r\nFix deletion of delimiters on their own lines.","package":"surround.zip","4":"surround.zip","src_id":"19287","5":"19287","creation_date":"1357058857","6":"1357058857"},{"0":"1697","vim_version":"6.0","1":"6.0","script_version":"1.90","2":"1.90","version_comment":"Completely eliminate wonky % mapping in prompts. \r\nWorkaround for user remapped d. [Christian Oudard] \r\nIntroduce vgS and begin phasing out vs.","3":"Completely eliminate wonky % mapping in prompts. \r\nWorkaround for user remapped d. [Christian Oudard] \r\nIntroduce vgS and begin phasing out vs.","package":"surround.zip","4":"surround.zip","src_id":"12566","5":"12566","creation_date":"1267837131","6":"1267837131"},{"0":"1697","vim_version":"6.0","1":"6.0","script_version":"1.34","2":"1.34","version_comment":"One more regression fix.\r\nThis is really really planned as the last release with partial Vim 6.0 compatibility  (third time's the charm).","3":"One more regression fix.\r\nThis is really really planned as the last release with partial Vim 6.0 compatibility  (third time's the charm).","package":"surround.zip","4":"surround.zip","src_id":"8283","5":"8283","creation_date":"1203086172","6":"1203086172"},{"0":"1697","vim_version":"7.0","1":"7.0","script_version":"1.33","2":"1.33","version_comment":"Fixed regressions from previous release.\r\nThis is really planned as the last release with partial Vim 6.0 compatibility.","3":"Fixed regressions from previous release.\r\nThis is really planned as the last release with partial Vim 6.0 compatibility.","package":"surround.zip","4":"surround.zip","src_id":"8229","5":"8229","creation_date":"1202068369","6":"1202068369"},{"0":"1697","vim_version":"7.0","1":"7.0","script_version":"1.30","2":"1.30","version_comment":"Fixed edge case where ds could move a multiline inner text down one line.\r\nThis is planned as the last release with partial Vim 6.0 compatibility.","3":"Fixed edge case where ds could move a multiline inner text down one line.\r\nThis is planned as the last release with partial Vim 6.0 compatibility.","package":"surround.zip","4":"surround.zip","src_id":"8185","5":"8185","creation_date":"1201422576","6":"1201422576"},{"0":"1697","vim_version":"7.0","1":"7.0","script_version":"1.27","2":"1.27","version_comment":"Fixed multiline surrounds in insert mode \r\n","3":"Fixed multiline surrounds in insert mode \r\n","package":"surround.zip","4":"surround.zip","src_id":"7744","5":"7744","creation_date":"1191432669","6":"1191432669"},{"0":"1697","vim_version":"7.0","1":"7.0","script_version":"1.26","2":"1.26","version_comment":"Added a \/* C style comment *\/ target.\r\nInsert mode indenting limited to multiline insertions.","3":"Added a \/* C style comment *\/ target.\r\nInsert mode indenting limited to multiline insertions.","package":"surround.vim","4":"surround.vim","src_id":"7434","5":"7434","creation_date":"1185866728","6":"1185866728"},{"0":"1697","vim_version":"7.0","1":"7.0","script_version":"1.24","2":"1.24","version_comment":"surround_indent now works in insert mode.\r\nAdded <C-]> to add braces on separate lines.","3":"surround_indent now works in insert mode.\r\nAdded <C-]> to add braces on separate lines.","package":"surround.zip","4":"surround.zip","src_id":"7093","5":"7093","creation_date":"1178805045","6":"1178805045"},{"0":"1697","vim_version":"7.0","1":"7.0","script_version":"1.23","2":"1.23","version_comment":"xmap rather than vmap, to avoid interfering with select mode.\r\nsurround_insert_tail to specify a universal suffix for use in insert mode.","3":"xmap rather than vmap, to avoid interfering with select mode.\r\nsurround_insert_tail to specify a universal suffix for use in insert mode.","package":"surround.zip","4":"surround.zip","src_id":"6747","5":"6747","creation_date":"1171618386","6":"1171618386"},{"0":"1697","vim_version":"7.0","1":"7.0","script_version":"1.22","2":"1.22","version_comment":"Function properly when clipboard=unnamed\r\nVery experimental custom prompting for substitution text","3":"Function properly when clipboard=unnamed\r\nVery experimental custom prompting for substitution text","package":"surround.zip","4":"surround.zip","src_id":"6737","5":"6737","creation_date":"1171213646","6":"1171213646"},{"0":"1697","vim_version":"7.0","1":"7.0","script_version":"1.18","2":"1.18","version_comment":"Zip file instead of documentation extraction hack","3":"Zip file instead of documentation extraction hack","package":"surround.zip","4":"surround.zip","src_id":"6411","5":"6411","creation_date":"1163460357","6":"1163460357"},{"0":"1697","vim_version":"6.0","1":"6.0","script_version":"1.17","2":"1.17","version_comment":"Insert mode mapping that doesn't conflict with flow control.\r\nFixed edge case with ys where one too many characters would be grabbed.","3":"Insert mode mapping that doesn't conflict with flow control.\r\nFixed edge case with ys where one too many characters would be grabbed.","package":"surround.vim","4":"surround.vim","src_id":"6399","5":"6399","creation_date":"1163111331","6":"1163111331"},{"0":"1697","vim_version":"7.0","1":"7.0","script_version":"1.16","2":"1.16","version_comment":"S in blockwise visual mode strips trailing whitespace.","3":"S in blockwise visual mode strips trailing whitespace.","package":"surround.vim","4":"surround.vim","src_id":"6379","5":"6379","creation_date":"1162763756","6":"1162763756"},{"0":"1697","vim_version":"7.0","1":"7.0","script_version":"1.12","2":"1.12","version_comment":"Lots of tiny bug fixes and cleanup.\r\n\"S\" mappings to force surroundings onto a separate line.\r\nSupport for blockwise visual mode.","3":"Lots of tiny bug fixes and cleanup.\r\n\"S\" mappings to force surroundings onto a separate line.\r\nSupport for blockwise visual mode.","package":"surround.vim","4":"surround.vim","src_id":"6357","5":"6357","creation_date":"1162332173","6":"1162332173"},{"0":"1697","vim_version":"7.0","1":"7.0","script_version":"1.6","2":"1.6","version_comment":"Initial upload","3":"Initial upload","package":"surround.vim","4":"surround.vim","src_id":"6348","5":"6348","creation_date":"1162143591","6":"1162143591"}]},"1696":{"script_id":"1696","0":"1696","script_name":"VPars","1":"VPars","script_type":"utility","2":"utility","summary":"Parameter substitution functions to be used in text fragments","3":"Parameter substitution functions to be used in text fragments","description":"PURPOSE\r\n\r\nParameter substitution functions to be used in text fragments.\r\n\r\nDesigned as kernel to yet another template processing script, but may as well be used stand-alone or from another Vim script.\r\n\r\nMay be used interactively or in batch processing mode, both called from another Vim script (e.g. a templates manager) or directly by the user on a visually selected text block or by calling functions from the command line.\r\n\r\n\r\nCONCEPTUAL OVERVIEW\r\n\r\nThese are basic capabilities only. But VPars is extensively documented in the accompanying Vim help text. Look there for more detail and for the programming interface.\r\n\r\nVPars basically works on a specially selected text block. It finds variables in there, waits for the user to enter replacement text and substitutes this upon a simple keypress (<F3> by default, but may be redefined at any time). Then the next variable in sequence is found, etc.\r\n\r\nThere are built-in mechanisms which allow to skip or alter variables in the course of processing, so VPars will finally wrap around to the beginning of the text block and reprocess it until all variables have been handled.\r\n\r\n\r\nVARIABLES\r\n\r\nEach variable is assumed to have one of the following formats.\r\n\r\nCURSOR\r\n<|>\r\nis a cursor mark which will simply be removed and the cursor be positioned there.\r\n\r\nSIMPLE VARIABLES\r\n<|value|>\r\nwhere 'value' denotes both the variable label and the default value.\r\n\r\n<|value|:label:|>\r\nwhere 'value' denotes the (possible empty) default value, and 'label' the explicit label of this variable.\r\n\r\nRESTRICTIONS\r\nThere are almost no restrictions on the default value and the label as well, except that they must fit in the same line, and cannot contain another VPars variable. The user can even enter multiple lines as substitution text.\r\n\r\nHOW VARIABLES GET SUBSTITUTED\r\nPressing <F3> with the cursor inside the 'value' field of a simple variable will cause this and all equally named variables be replaced by the following text.\r\n    * The current variable will be replaced by the text extending from the left '<|' delimiter up to the current cursor position.\r\n    * If the cursor is positioned immediately after the left delimiter, the variable will be replaced by the given 'default' value.\r\n    * Any text to the right of the cursor does not count.\r\n      (Exception: If the variable bears an explicit ':label:' and was initially empty (of the form <||:label:|>), any text between the bars will be taken as replacement, independent of where the cursor was positioned.)\r\n\r\nIMPLICIT AUTOMATIC SUBSTITUTION\r\nAny equally labeled variable within the currently marked text block will automatically receive the same replacement text, except delayed ones (see below). \r\n\r\nALTERNATIVES\r\n<|alt_1|alt_2|..|alt_n|>\r\nwhere 'alt_1'..'alt_n' denote given alternative substitution values of which the one bearing the cursor will replace this one variable.\r\n\r\n<|alt_1|alt_2|..|alt_n|:label:|>\r\nsame, but explicitely labeled. The selected substitution will replace any variable with this name.\r\n\r\nDELAYED VARIABLES\r\nThere is a primitive means of defining another order to visit the variables and\/or cursor marks within the selected text block. This is based on the VPars method of repeatedly processing the given text block until no variables are left over.\r\n\r\nIf the variable mark found is surrounded by another level of '< .. >' delimiters, this extra level will be removed and the variable skipped in this turn.\r\n\r\nThis allows delaying the variable substitution until others are available, or to position a cursor to a mark located near the beginning of the most recently inserted text after all variable substitutions were done.\r\n\r\n\r\nEXPLICITELY LABELED VARIABLE SUBSTITUTION\r\nIf there is an explicit ':label:' given, all variables bearing this label will be replaced with the substitution of the first occurrence found. This occurs independent of the form the other variables. Especially will the replacement text of simple variables replace alternative variables bearing this name and vice versa.\r\n\r\n\r\nTEXT BOUNDARIES\r\nText replacement will occur upon pressing <F3>. As long as there are variables in this block, <F3> will wrap around from the its end to the marked beginning line. This mechanism allows the handling of delayed variables.\r\n    * The text boundaries are marked linewise.\r\n    * Usually, the text bundaries will be marked by some calling function.\r\n    * The user can expressely select a visual block, which will then repeatedly be parsed for variables upon pressing <F3>.\r\n    * When there is no text block marked or there are no more variables found, the script switches to 'global mode', where the next variable from cursor to the end of the buffer will be found, if any. This global mode is strictly linear, no wrapping around will happen. \r\n\r\n\r\nBATCH PROCESSING\r\nThere is a VPars function implemented which allows batch replacement of any variable in the selected text block before interactive mode is entered.\r\n\r\n\r\nPRE- AND POSTPROCESSING VARIABLES\r\nCalling scripts may provide so-called hook functions which provide ways to process a VPars variable before and after substitution. See the vpars.txt help for more.","4":"PURPOSE\r\n\r\nParameter substitution functions to be used in text fragments.\r\n\r\nDesigned as kernel to yet another template processing script, but may as well be used stand-alone or from another Vim script.\r\n\r\nMay be used interactively or in batch processing mode, both called from another Vim script (e.g. a templates manager) or directly by the user on a visually selected text block or by calling functions from the command line.\r\n\r\n\r\nCONCEPTUAL OVERVIEW\r\n\r\nThese are basic capabilities only. But VPars is extensively documented in the accompanying Vim help text. Look there for more detail and for the programming interface.\r\n\r\nVPars basically works on a specially selected text block. It finds variables in there, waits for the user to enter replacement text and substitutes this upon a simple keypress (<F3> by default, but may be redefined at any time). Then the next variable in sequence is found, etc.\r\n\r\nThere are built-in mechanisms which allow to skip or alter variables in the course of processing, so VPars will finally wrap around to the beginning of the text block and reprocess it until all variables have been handled.\r\n\r\n\r\nVARIABLES\r\n\r\nEach variable is assumed to have one of the following formats.\r\n\r\nCURSOR\r\n<|>\r\nis a cursor mark which will simply be removed and the cursor be positioned there.\r\n\r\nSIMPLE VARIABLES\r\n<|value|>\r\nwhere 'value' denotes both the variable label and the default value.\r\n\r\n<|value|:label:|>\r\nwhere 'value' denotes the (possible empty) default value, and 'label' the explicit label of this variable.\r\n\r\nRESTRICTIONS\r\nThere are almost no restrictions on the default value and the label as well, except that they must fit in the same line, and cannot contain another VPars variable. The user can even enter multiple lines as substitution text.\r\n\r\nHOW VARIABLES GET SUBSTITUTED\r\nPressing <F3> with the cursor inside the 'value' field of a simple variable will cause this and all equally named variables be replaced by the following text.\r\n    * The current variable will be replaced by the text extending from the left '<|' delimiter up to the current cursor position.\r\n    * If the cursor is positioned immediately after the left delimiter, the variable will be replaced by the given 'default' value.\r\n    * Any text to the right of the cursor does not count.\r\n      (Exception: If the variable bears an explicit ':label:' and was initially empty (of the form <||:label:|>), any text between the bars will be taken as replacement, independent of where the cursor was positioned.)\r\n\r\nIMPLICIT AUTOMATIC SUBSTITUTION\r\nAny equally labeled variable within the currently marked text block will automatically receive the same replacement text, except delayed ones (see below). \r\n\r\nALTERNATIVES\r\n<|alt_1|alt_2|..|alt_n|>\r\nwhere 'alt_1'..'alt_n' denote given alternative substitution values of which the one bearing the cursor will replace this one variable.\r\n\r\n<|alt_1|alt_2|..|alt_n|:label:|>\r\nsame, but explicitely labeled. The selected substitution will replace any variable with this name.\r\n\r\nDELAYED VARIABLES\r\nThere is a primitive means of defining another order to visit the variables and\/or cursor marks within the selected text block. This is based on the VPars method of repeatedly processing the given text block until no variables are left over.\r\n\r\nIf the variable mark found is surrounded by another level of '< .. >' delimiters, this extra level will be removed and the variable skipped in this turn.\r\n\r\nThis allows delaying the variable substitution until others are available, or to position a cursor to a mark located near the beginning of the most recently inserted text after all variable substitutions were done.\r\n\r\n\r\nEXPLICITELY LABELED VARIABLE SUBSTITUTION\r\nIf there is an explicit ':label:' given, all variables bearing this label will be replaced with the substitution of the first occurrence found. This occurs independent of the form the other variables. Especially will the replacement text of simple variables replace alternative variables bearing this name and vice versa.\r\n\r\n\r\nTEXT BOUNDARIES\r\nText replacement will occur upon pressing <F3>. As long as there are variables in this block, <F3> will wrap around from the its end to the marked beginning line. This mechanism allows the handling of delayed variables.\r\n    * The text boundaries are marked linewise.\r\n    * Usually, the text bundaries will be marked by some calling function.\r\n    * The user can expressely select a visual block, which will then repeatedly be parsed for variables upon pressing <F3>.\r\n    * When there is no text block marked or there are no more variables found, the script switches to 'global mode', where the next variable from cursor to the end of the buffer will be found, if any. This global mode is strictly linear, no wrapping around will happen. \r\n\r\n\r\nBATCH PROCESSING\r\nThere is a VPars function implemented which allows batch replacement of any variable in the selected text block before interactive mode is entered.\r\n\r\n\r\nPRE- AND POSTPROCESSING VARIABLES\r\nCalling scripts may provide so-called hook functions which provide ways to process a VPars variable before and after substitution. See the vpars.txt help for more.","install_details":"To install VPars, copy the vpars.zip file into the ~\/.vim directory or equivalent and unzip it there. This will install vpars.vim into the plugins subdirectory and vpars.txt into the doc subdirectory.\r\n\r\nTo enable access to this vpars.txt documentation start Vim and issue:\r\n    :helptags ~\/.vim\/doc\r\nvpars.txt should then be listed in the LOCAL ADDITIONS section of the Vim main help (issue :help, and the scroll down to the end).\r\n\r\nTo access VPars help:\r\n    :help vpars\r\nwill display the CONTENTS section of this help, and\r\n    :help vpars-index\r\nwill get you to the INDEX section (which collects all VPars help targets). \r\n\r\nDo not forget to re-initialize the help tags every time you upgrade to another VPars version.","5":"To install VPars, copy the vpars.zip file into the ~\/.vim directory or equivalent and unzip it there. This will install vpars.vim into the plugins subdirectory and vpars.txt into the doc subdirectory.\r\n\r\nTo enable access to this vpars.txt documentation start Vim and issue:\r\n    :helptags ~\/.vim\/doc\r\nvpars.txt should then be listed in the LOCAL ADDITIONS section of the Vim main help (issue :help, and the scroll down to the end).\r\n\r\nTo access VPars help:\r\n    :help vpars\r\nwill display the CONTENTS section of this help, and\r\n    :help vpars-index\r\nwill get you to the INDEX section (which collects all VPars help targets). \r\n\r\nDo not forget to re-initialize the help tags every time you upgrade to another VPars version.","first_name":"Bernd","6":"Bernd","last_name":"Pol","7":"Pol","releases":[{"0":"1696","vim_version":"7.0","1":"7.0","script_version":"2.1","2":"2.1","version_comment":"more bugfixes;\r\nbetter behavior of pause\/resume block processing","3":"more bugfixes;\r\nbetter behavior of pause\/resume block processing","package":"vpars.zip","4":"vpars.zip","src_id":"6612","5":"6612","creation_date":"1168601244","6":"1168601244"},{"0":"1696","vim_version":"7.0","1":"7.0","script_version":"2.0","2":"2.0","version_comment":"A lot of bugs fixed (thanks to Igor Prischepoff for his thorough testing efforts).\r\nCalling VPars simplified by adding a new VPars_Run() function (see documentation).\r\nGUI menu user interface and shortcuts overworked; there is now the possibility to pause (,jp) and resume (,jr) processing the substition loop.","3":"A lot of bugs fixed (thanks to Igor Prischepoff for his thorough testing efforts).\r\nCalling VPars simplified by adding a new VPars_Run() function (see documentation).\r\nGUI menu user interface and shortcuts overworked; there is now the possibility to pause (,jp) and resume (,jr) processing the substition loop.","package":"vpars.zip","4":"vpars.zip","src_id":"6492","5":"6492","creation_date":"1165086827","6":"1165086827"},{"0":"1696","vim_version":"7.0","1":"7.0","script_version":"1.2","2":"1.2","version_comment":"It is possible to escape the delay meaning of <...> brackets by putting dots around the variable: \"<.<|label|>.>\" will result in \"<value>\" after replacement;\r\ncursor end line positioning will behave better in virtualedit modes;\r\ntwo new shortcuts provided:\r\n,jo will visually select the currently valid dedicated text block;\r\n,ji will invalid such a text block;\r\na calling script can now ask VPars to put a menu in the GUI.","3":"It is possible to escape the delay meaning of <...> brackets by putting dots around the variable: \"<.<|label|>.>\" will result in \"<value>\" after replacement;\r\ncursor end line positioning will behave better in virtualedit modes;\r\ntwo new shortcuts provided:\r\n,jo will visually select the currently valid dedicated text block;\r\n,ji will invalid such a text block;\r\na calling script can now ask VPars to put a menu in the GUI.","package":"vpars.zip","4":"vpars.zip","src_id":"6463","5":"6463","creation_date":"1164297059","6":"1164297059"},{"0":"1696","vim_version":"7.0","1":"7.0","script_version":"1.1","2":"1.1","version_comment":"Jump to block beginning\/end added. Alternate set of shortcuts added ( ,jj = next variable | ,jb = jump block begin | ,je = jump block end )","3":"Jump to block beginning\/end added. Alternate set of shortcuts added ( ,jj = next variable | ,jb = jump block begin | ,je = jump block end )","package":"vpars.zip","4":"vpars.zip","src_id":"6401","5":"6401","creation_date":"1163168823","6":"1163168823"},{"0":"1696","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"vpars.zip","4":"vpars.zip","src_id":"6344","5":"6344","creation_date":"1161951651","6":"1161951651"}]},"1695":{"script_id":"1695","0":"1695","script_name":"StateExp","1":"StateExp","script_type":"utility","2":"utility","summary":"Ease writing code by expanding statements.","3":"Ease writing code by expanding statements.","description":"The main point this script targets to is to ease writing code. Just type sw<ctrl-s> and you get a complete switch(){case;break;}  statement. \r\nBut it can also be used to add a header to a letter, etc. What to expand and how to expand can easily be configured.          \r\n                                                                    \r\nTo invoke the statement expansion, type a short form of a statement and press <ctrl-s> in insert mode.                        \r\n  Memory aid: s (s)tatement expansion                               \r\nThe statement will be expanded. By default the most important C statements are defined. \r\n                                                                    \r\nPress <leader>sh to get a list of defined statements.               \r\n  Memory aid: sh (s)tatement expansion (h)elp                       \r\n ","4":"The main point this script targets to is to ease writing code. Just type sw<ctrl-s> and you get a complete switch(){case;break;}  statement. \r\nBut it can also be used to add a header to a letter, etc. What to expand and how to expand can easily be configured.          \r\n                                                                    \r\nTo invoke the statement expansion, type a short form of a statement and press <ctrl-s> in insert mode.                        \r\n  Memory aid: s (s)tatement expansion                               \r\nThe statement will be expanded. By default the most important C statements are defined. \r\n                                                                    \r\nPress <leader>sh to get a list of defined statements.               \r\n  Memory aid: sh (s)tatement expansion (h)elp                       \r\n ","install_details":"Just copy this script into Vim's plugin directory, for details see Vim help ':help plugin'.","5":"Just copy this script into Vim's plugin directory, for details see Vim help ':help plugin'.","first_name":"Christian","6":"Christian","last_name":"Habermann","7":"Habermann","releases":[{"0":"1695","vim_version":"7.0","1":"7.0","script_version":"1.01.00","2":"1.01.00","version_comment":"- better alignment of help page if statements are not all of the same length\r\n- new statement: 'else { }'","3":"- better alignment of help page if statements are not all of the same length\r\n- new statement: 'else { }'","package":"StateExp.vim","4":"StateExp.vim","src_id":"6681","5":"6681","creation_date":"1169980456","6":"1169980456"},{"0":"1695","vim_version":"7.0","1":"7.0","script_version":"1.00.00","2":"1.00.00","version_comment":"Initial upload","3":"Initial upload","package":"stateexp.vim","4":"stateexp.vim","src_id":"6339","5":"6339","creation_date":"1161864876","6":"1161864876"}]},"1694":{"script_id":"1694","0":"1694","script_name":"SnippetsMgr","1":"SnippetsMgr","script_type":"utility","2":"utility","summary":"This script helps to work with code snippets.","3":"This script helps to work with code snippets.","description":"This script helps to work with code snippets. It provides functions to insert, edit, create, delete and rename code snippets.          \r\nSnippets are files that can be loaded into the active buffer (e.g. programmers can easily add a template function header when writing a new function or add often used codes).                   \r\n                                                                   \r\nTo invoke the snippets manager, press <leader>sm                   \r\n  Memory aid: sm (s)nippets(m)anager                               \r\nIn the current window a list of code snippets will be shown. To copy a snippet into the buffer in which SnippetsMgr was invoked,  move cursor over a snippet and press <enter>. That's it.           \r\n                                                                   \r\nSimple and not very useful code snippets are provided with this script. See them as examples and as starting point to write own ones. Code snippets are very personal. To use them in an efficient way you will have to write your owns.                                         \r\n","4":"This script helps to work with code snippets. It provides functions to insert, edit, create, delete and rename code snippets.          \r\nSnippets are files that can be loaded into the active buffer (e.g. programmers can easily add a template function header when writing a new function or add often used codes).                   \r\n                                                                   \r\nTo invoke the snippets manager, press <leader>sm                   \r\n  Memory aid: sm (s)nippets(m)anager                               \r\nIn the current window a list of code snippets will be shown. To copy a snippet into the buffer in which SnippetsMgr was invoked,  move cursor over a snippet and press <enter>. That's it.           \r\n                                                                   \r\nSimple and not very useful code snippets are provided with this script. See them as examples and as starting point to write own ones. Code snippets are very personal. To use them in an efficient way you will have to write your owns.                                         \r\n","install_details":"Just copy this script into Vim's plugin directory, for details see Vim help ':help plugin'.                                          \r\nCopy the directory 'snippets' to your vimfiles directory and set the path to it. How to configure see header of script.                         ","5":"Just copy this script into Vim's plugin directory, for details see Vim help ':help plugin'.                                          \r\nCopy the directory 'snippets' to your vimfiles directory and set the path to it. How to configure see header of script.                         ","first_name":"Christian","6":"Christian","last_name":"Habermann","7":"Habermann","releases":[{"0":"1694","vim_version":"7.0","1":"7.0","script_version":"1.01.00","2":"1.01.00","version_comment":"Snippets can now be loaded with indentation.","3":"Snippets can now be loaded with indentation.","package":"SnippetsMgr.zip","4":"SnippetsMgr.zip","src_id":"6682","5":"6682","creation_date":"1169980631","6":"1169980631"},{"0":"1694","vim_version":"7.0","1":"7.0","script_version":"1.00.00","2":"1.00.00","version_comment":"Initial upload","3":"Initial upload","package":"snippetsmgr.zip","4":"snippetsmgr.zip","src_id":"6338","5":"6338","creation_date":"1161864575","6":"1161864575"}]},"1693":{"script_id":"1693","0":"1693","script_name":"desertEx","1":"desertEx","script_type":"color scheme","2":"color scheme","summary":"A desert based scheme with enhanced colors. ","3":"A desert based scheme with enhanced colors. ","description":"Get the latest version from github:\r\nhttps:\/\/github.com\/mbbill\/desertEx\r\n\r\nThe 'desert' color scheme is a good model of low contrast colors with dark gray background which is good to our eyes. This 'desertEx' color scheme enhanced its colors in order to make it much more beautiful, it also provides nearly the same color for the 256-color terminal.\r\n\r\nScreenShot:\r\nhttps:\/\/sites.google.com\/site\/mbbill\/desertEx1.png\r\nhttps:\/\/sites.google.com\/site\/mbbill\/desertEx2.png","4":"Get the latest version from github:\r\nhttps:\/\/github.com\/mbbill\/desertEx\r\n\r\nThe 'desert' color scheme is a good model of low contrast colors with dark gray background which is good to our eyes. This 'desertEx' color scheme enhanced its colors in order to make it much more beautiful, it also provides nearly the same color for the 256-color terminal.\r\n\r\nScreenShot:\r\nhttps:\/\/sites.google.com\/site\/mbbill\/desertEx1.png\r\nhttps:\/\/sites.google.com\/site\/mbbill\/desertEx2.png","install_details":"","5":"","first_name":"Ming","6":"Ming","last_name":"Bai","7":"Bai","releases":[{"0":"1693","vim_version":"6.0","1":"6.0","script_version":"3.0","2":"3.0","version_comment":"Apply GUI color scheme to console with 256 colors.","3":"Apply GUI color scheme to console with 256 colors.","package":"desertEx.vim","4":"desertEx.vim","src_id":"16802","5":"16802","creation_date":"1320393706","6":"1320393706"},{"0":"1693","vim_version":"7.0","1":"7.0","script_version":"2.0","2":"2.0","version_comment":"Improved diff colors.\r\nSreen shot:\r\nhttp:\/\/mbbill.googlepages.com\/desertEx1.png\r\nhttp:\/\/mbbill.googlepages.com\/desertEx2.png","3":"Improved diff colors.\r\nSreen shot:\r\nhttp:\/\/mbbill.googlepages.com\/desertEx1.png\r\nhttp:\/\/mbbill.googlepages.com\/desertEx2.png","package":"desertEx.vim","4":"desertEx.vim","src_id":"6550","5":"6550","creation_date":"1167010924","6":"1167010924"},{"0":"1693","vim_version":"7.0","1":"7.0","script_version":"1.0.0","2":"1.0.0","version_comment":"Initial upload","3":"Initial upload","package":"desertEx.vim","4":"desertEx.vim","src_id":"6337","5":"6337","creation_date":"1161846873","6":"1161846873"}]},"1692":{"script_id":"1692","0":"1692","script_name":"tailtab.vim","1":"tailtab.vim","script_type":"utility","2":"utility","summary":"View log files getting updated automagically","3":"View log files getting updated automagically","description":"This is a plugin that lets you view multiple log files or any files of interest that are modified externally. The files are opened in read \r\nonly mode.\r\n\r\n:TailView \/tmp\/foo \/var\/log\/bar ...\r\n\r\nwill open as many new tabs as files and you can update the file from disk using the \r\n<Ctrl-K> keypress in normal mode. Also when you swich tabs using the gt command the file gets updated from disk automatically.\r\n\r\nOf course you can use the TAB key to complete file names.\r\n\r\nNormal vim usage is not affected in any way. Only files opened with the TailView command are in read only mode and updated from disk\r\nautomatically when you enter that tab","4":"This is a plugin that lets you view multiple log files or any files of interest that are modified externally. The files are opened in read \r\nonly mode.\r\n\r\n:TailView \/tmp\/foo \/var\/log\/bar ...\r\n\r\nwill open as many new tabs as files and you can update the file from disk using the \r\n<Ctrl-K> keypress in normal mode. Also when you swich tabs using the gt command the file gets updated from disk automatically.\r\n\r\nOf course you can use the TAB key to complete file names.\r\n\r\nNormal vim usage is not affected in any way. Only files opened with the TailView command are in read only mode and updated from disk\r\nautomatically when you enter that tab","install_details":"Normal instructions. Just drop the script into ~\/.vim\/plugin directory\r\nand restart vim!","5":"Normal instructions. Just drop the script into ~\/.vim\/plugin directory\r\nand restart vim!","first_name":"Girish","6":"Girish","last_name":"Venkatachalam","7":"Venkatachalam","releases":[{"0":"1692","vim_version":"7.0","1":"7.0","script_version":"0.2","2":"0.2","version_comment":"Thanks to Bill McCarthy for comments.\r\n\r\nNow, the Ctrl-K update hotkey works only for TailView buffers.","3":"Thanks to Bill McCarthy for comments.\r\n\r\nNow, the Ctrl-K update hotkey works only for TailView buffers.","package":"tailtab.vim","4":"tailtab.vim","src_id":"6333","5":"6333","creation_date":"1161735173","6":"1161735173"},{"0":"1692","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"tailtab.vim","4":"tailtab.vim","src_id":"6331","5":"6331","creation_date":"1161664798","6":"1161664798"}]},"1691":{"script_id":"1691","0":"1691","script_name":"IndentConsistencyCopAutoCmds","1":"IndentConsistencyCopAutoCmds","script_type":"utility","2":"utility","summary":"autocmds for IndentConsistencyCop.vim","3":"autocmds for IndentConsistencyCop.vim","description":"DESCRIPTION\r\nThe autocmds in this script automatically trigger the IndentConsistencyCop for\r\ncertain, configurable filetypes (such as c, cpp, html, xml, ... which\r\ntypically contain lots of indented lines) once when you load the file in Vim,\r\nand\/or on every write of the buffer.\r\nThe entire buffer will be checked for inconsistent indentation, and you will\r\nreceive a report on its findings. With this automatic background check, you'll\r\nbecome aware of indentation problems before you start editing and\/or when\r\nwriting. This prevents you from accidentally introducing an inconsistency with\r\nyour edits.\r\n\r\nUSAGE\r\nTriggering happens automatically; by default, when a buffer is opened for the\r\nfirst time, both the compatibility of the file's indent with the buffer\r\nsettings and its internal consistency are checked; on each subsequent save,\r\nthe latter check is repeated.\r\nOf course, you can still manually execute the :IndentConsistencyCop command\r\nto re-check the buffer at any time.\r\n\r\nFor very large files, the check may take a couple of seconds. You can abort\r\nthe script run with CTRL-C, like any other Vim command.\r\n\r\nIf you chose to \"Ignore\" any inconsistent indents in the IndentConsistencyCop\r\nreport, further automatic invocations on buffer writes are suspended. It is\r\nassumed that you don't bother for this particular file. You can re-enable\r\nautomatic invocations by manually invoking :IndentConsistencyCop once and then\r\nchoosing an option other than \"Ignore\".\r\n\r\n:IndentConsistencyCopAutoCmdsOff\r\n:IndentConsistencyCopAutoCmdsOn\r\n                        Disable \/ re-enable the autocommands. This affects all\r\n                        existing buffers as well as any newly opened files.","4":"DESCRIPTION\r\nThe autocmds in this script automatically trigger the IndentConsistencyCop for\r\ncertain, configurable filetypes (such as c, cpp, html, xml, ... which\r\ntypically contain lots of indented lines) once when you load the file in Vim,\r\nand\/or on every write of the buffer.\r\nThe entire buffer will be checked for inconsistent indentation, and you will\r\nreceive a report on its findings. With this automatic background check, you'll\r\nbecome aware of indentation problems before you start editing and\/or when\r\nwriting. This prevents you from accidentally introducing an inconsistency with\r\nyour edits.\r\n\r\nUSAGE\r\nTriggering happens automatically; by default, when a buffer is opened for the\r\nfirst time, both the compatibility of the file's indent with the buffer\r\nsettings and its internal consistency are checked; on each subsequent save,\r\nthe latter check is repeated.\r\nOf course, you can still manually execute the :IndentConsistencyCop command\r\nto re-check the buffer at any time.\r\n\r\nFor very large files, the check may take a couple of seconds. You can abort\r\nthe script run with CTRL-C, like any other Vim command.\r\n\r\nIf you chose to \"Ignore\" any inconsistent indents in the IndentConsistencyCop\r\nreport, further automatic invocations on buffer writes are suspended. It is\r\nassumed that you don't bother for this particular file. You can re-enable\r\nautomatic invocations by manually invoking :IndentConsistencyCop once and then\r\nchoosing an option other than \"Ignore\".\r\n\r\n:IndentConsistencyCopAutoCmdsOff\r\n:IndentConsistencyCopAutoCmdsOn\r\n                        Disable \/ re-enable the autocommands. This affects all\r\n                        existing buffers as well as any newly opened files.","install_details":"INSTALLATION\r\nThe code is hosted in a Git repo at\r\n    https:\/\/github.com\/inkarkat\/vim-IndentConsistencyCopAutoCmds\r\nYou can use your favorite plugin manager, or \"git clone\" into a directory used\r\nfor Vim packages. Releases are on the \"stable\" branch, the latest unstable\r\ndevelopment snapshot on \"master\".\r\n\r\nThis script is also packaged as a vimball. If you have the \"gunzip\"\r\ndecompressor in your PATH, simply edit the *.vmb.gz package in Vim; otherwise,\r\ndecompress the archive first, e.g. using WinZip. Inside Vim, install by\r\nsourcing the vimball or via the :UseVimball command.\r\n    vim IndentConsistencyCopAutoCmds*.vmb.gz\r\n    :so %\r\nTo uninstall, use the :RmVimball command.\r\n\r\nDEPENDENCIES\r\n- Requires Vim 7.0 or higher.\r\n- Requires the IndentConsistencyCop.vim plugin (vimscript #1690).\r\n- Requires the ingo-library.vim plugin (vimscript #4433), version 1.036 or\r\n  higher.\r\n\r\nCONFIGURATION\r\nFor a permanent configuration, put the following commands into your vimrc:\r\n\r\nIf you don't like the default filetypes that are inspected, define your own\r\ncomma-separated list of filetypes or add to the existing ones:\r\n    let g:indentconsistencycop_filetypes = 'c,cpp,java,javascript,perl,php,python,ruby,sh,tcsh,vim'\r\n    let g:indentconsistencycop_filetypes .= ',perl6'\r\n\r\nTo exclude some files even though they have one of the filetypes in\r\ng:indentconsistencycop_filetypes, you can define a List of expressions or\r\nFuncrefs that are evaluated; if one returns 1, the buffer will be skipped. The\r\ncurrent filename can be obtained from <afile>.\r\n    let g:IndentConsistencyCopAutoCmds_ExclusionPredicates =\r\n    ['expand(\"<afile>:p\" =~# \"\/tmp\"', function('ExcludeScratchFiles')]\r\nBy default, scratch buffers from the fugitive.vim plugin (that show immutable\r\nchanges) are excluded.\r\n\r\nTurn off the IndentConsistencyCop run when a buffer is loaded via\r\n    let g:indentconsistencycop_CheckOnLoad = 0\r\nThis avoids alerts when just viewing files (especially the multiple\r\nconfirmations when opening many files or restoring a saved session; though one\r\ncould also temporarily disable the autocmds in that case via\r\n:IndentConsistencyCopAutoCmdsOff). On the other hand, it comes with the risk\r\nof introducing indent inconsistencies until the first write (when the buffer's\r\nindent settings do not match the file's).\r\n\r\nTurn off the IndentConsistencyCop run after each write via\r\n    let g:indentconsistencycop_CheckAfterWrite = 0\r\nThe IndentConsistencyCop will only run once after loading a file.\r\n\r\nTo avoid blocking the user whenever a large buffer is written, the\r\nIndentConsistencyCop is only scheduled to run on the next 'CursorHold' event\r\nin case the buffer contains many lines. The threshold can be adjusted (to the\r\nsystem's performance and personal level of patience):\r\n    let g:indentconsistencycop_CheckAfterWriteMaxLinesForImmediateCheck = 1000\r\n\r\nBy default, both indent consistency and consistency with the buffer settings\r\nwill be checked when a file is loaded.\r\nOnly indent consistency is checked after a write of the buffer. The user\r\nalready was alerted to inconsistent buffer settings when the file was loaded\r\nand editing the file did't change anything in that regard.\r\nIf you don't want the check for consistency with the buffer settings, set\r\n    let g:indentconsistencycop_AutoRunCmd = 'IndentRangeConsistencyCop'\r\n\r\nINTEGRATION\r\nIf you want to disable the automatic checks for certain buffers only, without\r\nturning off the IndentConsistencyCop completely through\r\n:IndentConsistencyCopAutoCmdsOff or for certain filetypes by adapting\r\ng:indentconsistencycop_filetypes, set a buffer variable, e.g. via one of the\r\nlocal vimrc plugins:\r\n    :let b:indentconsistencycop_SkipChecks = 1","5":"INSTALLATION\r\nThe code is hosted in a Git repo at\r\n    https:\/\/github.com\/inkarkat\/vim-IndentConsistencyCopAutoCmds\r\nYou can use your favorite plugin manager, or \"git clone\" into a directory used\r\nfor Vim packages. Releases are on the \"stable\" branch, the latest unstable\r\ndevelopment snapshot on \"master\".\r\n\r\nThis script is also packaged as a vimball. If you have the \"gunzip\"\r\ndecompressor in your PATH, simply edit the *.vmb.gz package in Vim; otherwise,\r\ndecompress the archive first, e.g. using WinZip. Inside Vim, install by\r\nsourcing the vimball or via the :UseVimball command.\r\n    vim IndentConsistencyCopAutoCmds*.vmb.gz\r\n    :so %\r\nTo uninstall, use the :RmVimball command.\r\n\r\nDEPENDENCIES\r\n- Requires Vim 7.0 or higher.\r\n- Requires the IndentConsistencyCop.vim plugin (vimscript #1690).\r\n- Requires the ingo-library.vim plugin (vimscript #4433), version 1.036 or\r\n  higher.\r\n\r\nCONFIGURATION\r\nFor a permanent configuration, put the following commands into your vimrc:\r\n\r\nIf you don't like the default filetypes that are inspected, define your own\r\ncomma-separated list of filetypes or add to the existing ones:\r\n    let g:indentconsistencycop_filetypes = 'c,cpp,java,javascript,perl,php,python,ruby,sh,tcsh,vim'\r\n    let g:indentconsistencycop_filetypes .= ',perl6'\r\n\r\nTo exclude some files even though they have one of the filetypes in\r\ng:indentconsistencycop_filetypes, you can define a List of expressions or\r\nFuncrefs that are evaluated; if one returns 1, the buffer will be skipped. The\r\ncurrent filename can be obtained from <afile>.\r\n    let g:IndentConsistencyCopAutoCmds_ExclusionPredicates =\r\n    ['expand(\"<afile>:p\" =~# \"\/tmp\"', function('ExcludeScratchFiles')]\r\nBy default, scratch buffers from the fugitive.vim plugin (that show immutable\r\nchanges) are excluded.\r\n\r\nTurn off the IndentConsistencyCop run when a buffer is loaded via\r\n    let g:indentconsistencycop_CheckOnLoad = 0\r\nThis avoids alerts when just viewing files (especially the multiple\r\nconfirmations when opening many files or restoring a saved session; though one\r\ncould also temporarily disable the autocmds in that case via\r\n:IndentConsistencyCopAutoCmdsOff). On the other hand, it comes with the risk\r\nof introducing indent inconsistencies until the first write (when the buffer's\r\nindent settings do not match the file's).\r\n\r\nTurn off the IndentConsistencyCop run after each write via\r\n    let g:indentconsistencycop_CheckAfterWrite = 0\r\nThe IndentConsistencyCop will only run once after loading a file.\r\n\r\nTo avoid blocking the user whenever a large buffer is written, the\r\nIndentConsistencyCop is only scheduled to run on the next 'CursorHold' event\r\nin case the buffer contains many lines. The threshold can be adjusted (to the\r\nsystem's performance and personal level of patience):\r\n    let g:indentconsistencycop_CheckAfterWriteMaxLinesForImmediateCheck = 1000\r\n\r\nBy default, both indent consistency and consistency with the buffer settings\r\nwill be checked when a file is loaded.\r\nOnly indent consistency is checked after a write of the buffer. The user\r\nalready was alerted to inconsistent buffer settings when the file was loaded\r\nand editing the file did't change anything in that regard.\r\nIf you don't want the check for consistency with the buffer settings, set\r\n    let g:indentconsistencycop_AutoRunCmd = 'IndentRangeConsistencyCop'\r\n\r\nINTEGRATION\r\nIf you want to disable the automatic checks for certain buffers only, without\r\nturning off the IndentConsistencyCop completely through\r\n:IndentConsistencyCopAutoCmdsOff or for certain filetypes by adapting\r\ng:indentconsistencycop_filetypes, set a buffer variable, e.g. via one of the\r\nlocal vimrc plugins:\r\n    :let b:indentconsistencycop_SkipChecks = 1","first_name":"Ingo","6":"Ingo","last_name":"Karkat","7":"Karkat","releases":[{"0":"1691","vim_version":"7.0","1":"7.0","script_version":"1.50","2":"1.50","version_comment":"- Make the plugin dependency to IndentConsistencyCop.vim more robust by attempting to load the plugin if it's not yet available during plugin load.\r\n- Check for existence of g:indentconsistencycop_AutoRunCmd and issue error if the command does not exist on :IndentConsistencyCopAutoCmdsOn.\r\n- ENH: Allow to excluded certain files within supported filetypes via new g:IndentConsistencyCopAutoCmds_ExclusionPredicates configuration. By default, exclude scratch buffers from fugitive.vim\r\n- ENH: Offer a \"Ignore forever\" choice that turns off triggering for the current file persistently across Vim sessions. *** You need to update to ingo-library (vimscript #4433) version 1.036! ***","3":"- Make the plugin dependency to IndentConsistencyCop.vim more robust by attempting to load the plugin if it's not yet available during plugin load.\r\n- Check for existence of g:indentconsistencycop_AutoRunCmd and issue error if the command does not exist on :IndentConsistencyCopAutoCmdsOn.\r\n- ENH: Allow to excluded certain files within supported filetypes via new g:IndentConsistencyCopAutoCmds_ExclusionPredicates configuration. By default, exclude scratch buffers from fugitive.vim\r\n- ENH: Offer a \"Ignore forever\" choice that turns off triggering for the current file persistently across Vim sessions. *** You need to update to ingo-library (vimscript #4433) version 1.036! ***","package":"IndentConsistencyCopAutoCmds-1.50.vmb.gz","4":"IndentConsistencyCopAutoCmds-1.50.vmb.gz","src_id":"27020","5":"27020","creation_date":"1582260399","6":"1582260399"},{"0":"1691","vim_version":"7.0","1":"7.0","script_version":"1.46","2":"1.46","version_comment":"- Add yaml filetype to g:indentconsistencycop_filetypes.","3":"- Add yaml filetype to g:indentconsistencycop_filetypes.","package":"IndentConsistencyCopAutoCmds-1.46.vmb.gz","4":"IndentConsistencyCopAutoCmds-1.46.vmb.gz","src_id":"25735","5":"25735","creation_date":"1514063709","6":"1514063709"},{"0":"1691","vim_version":"7.0","1":"7.0","script_version":"1.45","2":"1.45","version_comment":"- Add several more filetypes to g:indentconsistencycop_filetypes.\r\n- FIX: Install of continuous buffer autocmd never worked because of missing <buffer> target.\r\n- Allow buffer-local config for indentconsistencycop_CheckOnLoad, indentconsistencycop_CheckAfterWrite, indentconsistencycop_CheckAfterWriteMaxLinesForImmediateCheck.\r\n- Add dependency to ingo-library (vimscript #4433). *** You need to separately install ingo-library (vimscript #4433) version 1.010 (or higher)! ***","3":"- Add several more filetypes to g:indentconsistencycop_filetypes.\r\n- FIX: Install of continuous buffer autocmd never worked because of missing <buffer> target.\r\n- Allow buffer-local config for indentconsistencycop_CheckOnLoad, indentconsistencycop_CheckAfterWrite, indentconsistencycop_CheckAfterWriteMaxLinesForImmediateCheck.\r\n- Add dependency to ingo-library (vimscript #4433). *** You need to separately install ingo-library (vimscript #4433) version 1.010 (or higher)! ***","package":"IndentConsistencyCopAutoCmds-1.45.vmb.gz","4":"IndentConsistencyCopAutoCmds-1.45.vmb.gz","src_id":"22898","5":"22898","creation_date":"1423481521","6":"1423481521"},{"0":"1691","vim_version":"7.0","1":"7.0","script_version":"1.42","2":"1.42","version_comment":"- When the persistence of the buffer fails (e.g. with \"E212: Cannot open for writing\"), don't run the cop; its messages may obscure the write error.\r\n- ENH: Allow skipping automatic checks for certain buffers (i.e. not globally disabling the checks via :IndentConsistencyCopAutoCmdsOff), configured for example by a directory-local vimrc, via new b:indentconsistencycop_SkipChecks setting.","3":"- When the persistence of the buffer fails (e.g. with \"E212: Cannot open for writing\"), don't run the cop; its messages may obscure the write error.\r\n- ENH: Allow skipping automatic checks for certain buffers (i.e. not globally disabling the checks via :IndentConsistencyCopAutoCmdsOff), configured for example by a directory-local vimrc, via new b:indentconsistencycop_SkipChecks setting.","package":"IndentConsistencyCopAutoCmds-1.42.vmb.gz","4":"IndentConsistencyCopAutoCmds-1.42.vmb.gz","src_id":"19575","5":"19575","creation_date":"1361983828","6":"1361983828"},{"0":"1691","vim_version":"7.0","1":"7.0","script_version":"1.40","2":"1.40","version_comment":"ENH: Allow check only on buffer writes by clearing new config flag g:indentconsistencycop_CheckOnLoad. This comes with the risk of introducing indent inconsistencies until the first write, but on the other hand avoids alerts when just viewing file(s) (especially when restoring a saved session with multiple files; though one could also temporarily disable the autocmds in that case). Suggested by Marcelo Mont\u00c3\u00ba.","3":"ENH: Allow check only on buffer writes by clearing new config flag g:indentconsistencycop_CheckOnLoad. This comes with the risk of introducing indent inconsistencies until the first write, but on the other hand avoids alerts when just viewing file(s) (especially when restoring a saved session with multiple files; though one could also temporarily disable the autocmds in that case). Suggested by Marcelo Mont\u00c3\u00ba.","package":"IndentConsistencyCopAutoCmds-1.40.vmb.gz","4":"IndentConsistencyCopAutoCmds-1.40.vmb.gz","src_id":"18695","5":"18695","creation_date":"1348693766","6":"1348693766"},{"0":"1691","vim_version":"7.0","1":"7.0","script_version":"1.32","2":"1.32","version_comment":"Avoid \"E464: Ambiguous use of user-defined command: IndentConsistencyCop\" when loading of the IndentConsistencyCop has been suppressed via --cmd \"let g:loaded_indentconsistencycop = 1\" by checking for the existence of the command in the definition of the autocmds. Do not define the commands when the IndentConsistencyCop command has not been defined. ","3":"Avoid \"E464: Ambiguous use of user-defined command: IndentConsistencyCop\" when loading of the IndentConsistencyCop has been suppressed via --cmd \"let g:loaded_indentconsistencycop = 1\" by checking for the existence of the command in the definition of the autocmds. Do not define the commands when the IndentConsistencyCop command has not been defined. ","package":"IndentConsistencyCopAutoCmds.vba.gz","4":"IndentConsistencyCopAutoCmds.vba.gz","src_id":"17574","5":"17574","creation_date":"1331226736","6":"1331226736"},{"0":"1691","vim_version":"7.0","1":"7.0","script_version":"1.31","2":"1.31","version_comment":"BUG: \"E216: No such group or event: IndentConsistencyCopBufferCmds\" on :IndentConsistencyCopAutoCmdsOff. ","3":"BUG: \"E216: No such group or event: IndentConsistencyCopBufferCmds\" on :IndentConsistencyCopAutoCmdsOff. ","package":"IndentConsistencyCopAutoCmds.vba.gz","4":"IndentConsistencyCopAutoCmds.vba.gz","src_id":"14712","5":"14712","creation_date":"1294563709","6":"1294563709"},{"0":"1691","vim_version":"7.0","1":"7.0","script_version":"1.30","2":"1.30","version_comment":"- ENH: Do not invoke the IndentConsistencyCop if the user chose to ignore the cop's report of an inconsistency. Requires b:indentconsistencycop_result.isIgnore flag introduced in IndentConsistencyCop 1.21. \r\n- ENH: Only check indent consistency after a write of the buffer, not consistency with buffer settings. \r\n- BUG: :IndentConsistencyCopAutoCmdsOff only works for future buffers, but does not turn off the cop in existing buffers. Must remove all buffer-local autocmds, too. \r\n- Allowing to just run indent consistency check, not buffer settings at all times via g:indentconsistencycop_AutoRunCmd. \r\n- Added separate help file and packaging the plugin as a vimball. \r\n- ENH: Added \"check after write\" feature, which triggers the IndentConsistencyCop whenever the buffer is written. To avoid blocking the user, in large buffers the check is only scheduled to run on the next 'CursorHold' event. \r\n- BUG: The same buffer-local autocmd could be created multiple times when the filetype is set repeatedly. \r\n- BUG: By clearing the entire IndentConsistencyCopBufferCmds augroup, pending autocmds for other buffers were deleted by an autocmd run in the current buffer. Now deleting only the buffer-local autocmds for the events that fired. ","3":"- ENH: Do not invoke the IndentConsistencyCop if the user chose to ignore the cop's report of an inconsistency. Requires b:indentconsistencycop_result.isIgnore flag introduced in IndentConsistencyCop 1.21. \r\n- ENH: Only check indent consistency after a write of the buffer, not consistency with buffer settings. \r\n- BUG: :IndentConsistencyCopAutoCmdsOff only works for future buffers, but does not turn off the cop in existing buffers. Must remove all buffer-local autocmds, too. \r\n- Allowing to just run indent consistency check, not buffer settings at all times via g:indentconsistencycop_AutoRunCmd. \r\n- Added separate help file and packaging the plugin as a vimball. \r\n- ENH: Added \"check after write\" feature, which triggers the IndentConsistencyCop whenever the buffer is written. To avoid blocking the user, in large buffers the check is only scheduled to run on the next 'CursorHold' event. \r\n- BUG: The same buffer-local autocmd could be created multiple times when the filetype is set repeatedly. \r\n- BUG: By clearing the entire IndentConsistencyCopBufferCmds augroup, pending autocmds for other buffers were deleted by an autocmd run in the current buffer. Now deleting only the buffer-local autocmds for the events that fired. ","package":"IndentConsistencyCopAutoCmds.vba.gz","4":"IndentConsistencyCopAutoCmds.vba.gz","src_id":"14666","5":"14666","creation_date":"1293809083","6":"1293809083"},{"0":"1691","vim_version":"7.0","1":"7.0","script_version":"1.10.004","2":"1.10.004","version_comment":"Minor change: Added -bar to all commands that do not take any arguments, so that these can be chained together. ","3":"Minor change: Added -bar to all commands that do not take any arguments, so that these can be chained together. ","package":"IndentConsistencyCopAutoCmds.vim","4":"IndentConsistencyCopAutoCmds.vim","src_id":"8840","5":"8840","creation_date":"1214199873","6":"1214199873"},{"0":"1691","vim_version":"7.0","1":"7.0","script_version":"1.10.003","2":"1.10.003","version_comment":"Avoiding multiple invocations of the IndentConsistencyCop when reloading or switching buffers. Now there's only one check per file and VIM session. \r\nAdded commands :IndentConsistencyCopAutoCmdsOn and :IndentConsistencyCopAutoCmdsOff to re-enable\/disable autocommands.  ","3":"Avoiding multiple invocations of the IndentConsistencyCop when reloading or switching buffers. Now there's only one check per file and VIM session. \r\nAdded commands :IndentConsistencyCopAutoCmdsOn and :IndentConsistencyCopAutoCmdsOff to re-enable\/disable autocommands.  ","package":"IndentConsistencyCopAutoCmds.vim","4":"IndentConsistencyCopAutoCmds.vim","src_id":"8330","5":"8330","creation_date":"1203684131","6":"1203684131"},{"0":"1691","vim_version":"7.0","1":"7.0","script_version":"0.01","2":"0.01","version_comment":"Initial upload","3":"Initial upload","package":"IndentConsistencyCopAutoCmds.vim","4":"IndentConsistencyCopAutoCmds.vim","src_id":"6330","5":"6330","creation_date":"1161660089","6":"1161660089"}]},"1690":{"script_id":"1690","0":"1690","script_name":"IndentConsistencyCop","1":"IndentConsistencyCop","script_type":"utility","2":"utility","summary":"Is the buffer's indentation consistent and does it conform to tab settings?","3":"Is the buffer's indentation consistent and does it conform to tab settings?","description":"DESCRIPTION\r\nIn order to achieve consistent indentation, you need to agree on the\r\nindentation width (e.g. 2, 4 or 8 spaces), and the indentation method (only\r\ntabs, only spaces, or a mix of tabs and spaces that minimizes the number of\r\nspaces and is called 'softtabstop' in Vim). Unfortunately, different people\r\nuse different editors and cannot agree on \"the right\" width and method.\r\nConsistency is important, though, to make the text look the same in different\r\neditors and on printouts. If any editor inadvertently converts tabs and\r\nspaces, version control and diff'ing will be much harder to do.\r\n\r\nThe IndentConsistencyCop examines the indent of the buffer and analyzes the\r\nused indent widths and methods. If there are conflicting ones or if bad\r\ncombinations of tabs and spaces are found, it alerts you and offers help in\r\nlocating the offenders - just like a friendly policeman:\r\n\r\n    :IndentConsistencyCop\r\n   Found inconsistent indentation in this buffer; generated from these\r\n    conflicting settings:\r\n    - tabstop (1838 of 3711 lines) <- buffer setting\r\n    - 4 spaces (33 of 3711 lines)\r\n    - bad mix of spaces and tabs (4 of 3711 lines)\r\n        [I]gnore, (J)ust change buffer settings..., (H)ighlight wrong\r\n        indents...:  h\r\n    What kind of inconsistent indents do you want to highlight?\r\n        Not [b]uffer settings (sts4), Not best (g)uess (tab), Not (c)hosen\r\n        setting..., (I)llegal indents only: g\r\n    Marked 180 incorrect lines.\r\n\r\nIf the buffer contents are okay, the IndentConsistencyCop can evaluate whether\r\nVim's buffer settings are compatible with the indent used in the buffer. The\r\nfriendly cop offers to correct your buffer settings if you run the risk of\r\nscrewing up the indent consistency with your wrong buffer settings:\r\n\r\n    :IndentConsistencyCop\r\n   The buffer's indent settings are inconsistent with the used indent '8\r\n    spaces'; these settings must be changed:\r\n    - expandtab from 0 to 1\r\n    How do you want to deal with the inconsistency?\r\n        [I]gnore, (C)hange: c\r\n    The buffer settings have been changed: tabstop=8 softtabstop=0 shiftwidth=8\r\n    expandtab\r\n\r\nThe IndentConsistencyCop is only concerned with the amount of whitespace from\r\ncolumn 1 to the first visible character; it does not check the alignment of\r\ntables, equals signs in variable assignments, etc. Neither does it know any\r\nspecifics about programming languages, or your personal preferred indentation\r\nstyle.\r\n\r\nSEE ALSO\r\n- IndentConsistencyCopAutoCmds (vimscript #1691) complements this plugin. It\r\n  automatically triggers the IndentConsistencyCop for certain filetypes when\r\n  loading the buffer and optionally also on each write\r\n\r\nRELATED WORKS\r\n- Indent Finder (vimscript #513) is a Python script and Vim plugin that scans\r\n  any loaded buffer and configures the appropriate indent settings\r\n- yaifa.vim (vimscript #3096) is a port to vimscript of the above\r\n- detectindent.vim (https:\/\/github.com\/ciaranm\/detectindent) by Ciaran\r\n  McCreesh tries to auto-detect the indentation settings\r\n- GuessIndent (vimscript #4251) is based on detectindent.vim\r\n- indentdetect.vim\r\n  (https:\/\/github.com\/ervandew\/vimfiles\/blob\/master\/vim\/plugin\/indentdetect.vim)\r\n  by Eric Van Dewoestine performs a simple detection and can set defaults\r\n  based on the filespec\r\n- matchindent.vim (vimscript #4066) detects tabs, 2 and 4-space indents and\r\n  adapts the indent settings accordingly\r\n- sleuth.vim (vimscript #4375) by Tim Pope automatically adjusts 'shiftwidth'\r\n  and 'tabstop' heuristically (via a simplistic sampling that does not check\r\n  for bad or inconsistent indents) or by looking at other files of the same\r\n  type\r\n- filestyle (vimscript #5065) highlights tabs when 'expandtab' is set,\r\n  trailing spaces, and lines longer than 'textwidth', but doesn't actually\r\n  check conformance to indent\r\n- ShowSpaces (vimscript #5148) highlights spaces inside indentation, per\r\n  buffer \/ filetype.\r\n- Indent Detector (vimscript #5195) run when a file is opened or written, has\r\n  warnings about mixed tab \/ space indent, and can adapt Vim's corresponding\r\n  options automatically.\r\n\r\nUSAGE\r\nStart the examination of the current buffer or range via:\r\n    :[range]IndentConsistencyCop [{setting}]\r\nThe optional {setting} specifies the assumed correct indent setting for the\r\nbuffer \/ range (if omitted the cop can later be told), as combination of\r\neither tab, spc, or sts with a number between 1-8, e.g. \"sts4\" for a\r\n4-character soft tabstop indent.\r\nThe triggering can be done automatically for configurable filetypes with the\r\nautocmds defined in IndentConsistencyCopAutoCmds.vim (vimscript #1691).\r\n\r\nIf you chose to highlight incorrect indents, either re-execute the\r\nIndentConsistencyCop to update the highlighting, or execute\r\n    :IndentConsistencyCopOff\r\nto remove the highlightings. Entries in the quickfix and location lists will\r\nbe kept.\r\n\r\nIf you just want to check a read-only file, or do not intend to modify the\r\nfile, you don't care if Vim's buffer settings are compatible with the used\r\nindent. In this case, you can use\r\n    :[range]IndentRangeConsistencyCop [{setting}]\r\ninstead of :IndentConsistencyCop.","4":"DESCRIPTION\r\nIn order to achieve consistent indentation, you need to agree on the\r\nindentation width (e.g. 2, 4 or 8 spaces), and the indentation method (only\r\ntabs, only spaces, or a mix of tabs and spaces that minimizes the number of\r\nspaces and is called 'softtabstop' in Vim). Unfortunately, different people\r\nuse different editors and cannot agree on \"the right\" width and method.\r\nConsistency is important, though, to make the text look the same in different\r\neditors and on printouts. If any editor inadvertently converts tabs and\r\nspaces, version control and diff'ing will be much harder to do.\r\n\r\nThe IndentConsistencyCop examines the indent of the buffer and analyzes the\r\nused indent widths and methods. If there are conflicting ones or if bad\r\ncombinations of tabs and spaces are found, it alerts you and offers help in\r\nlocating the offenders - just like a friendly policeman:\r\n\r\n    :IndentConsistencyCop\r\n   Found inconsistent indentation in this buffer; generated from these\r\n    conflicting settings:\r\n    - tabstop (1838 of 3711 lines) <- buffer setting\r\n    - 4 spaces (33 of 3711 lines)\r\n    - bad mix of spaces and tabs (4 of 3711 lines)\r\n        [I]gnore, (J)ust change buffer settings..., (H)ighlight wrong\r\n        indents...:  h\r\n    What kind of inconsistent indents do you want to highlight?\r\n        Not [b]uffer settings (sts4), Not best (g)uess (tab), Not (c)hosen\r\n        setting..., (I)llegal indents only: g\r\n    Marked 180 incorrect lines.\r\n\r\nIf the buffer contents are okay, the IndentConsistencyCop can evaluate whether\r\nVim's buffer settings are compatible with the indent used in the buffer. The\r\nfriendly cop offers to correct your buffer settings if you run the risk of\r\nscrewing up the indent consistency with your wrong buffer settings:\r\n\r\n    :IndentConsistencyCop\r\n   The buffer's indent settings are inconsistent with the used indent '8\r\n    spaces'; these settings must be changed:\r\n    - expandtab from 0 to 1\r\n    How do you want to deal with the inconsistency?\r\n        [I]gnore, (C)hange: c\r\n    The buffer settings have been changed: tabstop=8 softtabstop=0 shiftwidth=8\r\n    expandtab\r\n\r\nThe IndentConsistencyCop is only concerned with the amount of whitespace from\r\ncolumn 1 to the first visible character; it does not check the alignment of\r\ntables, equals signs in variable assignments, etc. Neither does it know any\r\nspecifics about programming languages, or your personal preferred indentation\r\nstyle.\r\n\r\nSEE ALSO\r\n- IndentConsistencyCopAutoCmds (vimscript #1691) complements this plugin. It\r\n  automatically triggers the IndentConsistencyCop for certain filetypes when\r\n  loading the buffer and optionally also on each write\r\n\r\nRELATED WORKS\r\n- Indent Finder (vimscript #513) is a Python script and Vim plugin that scans\r\n  any loaded buffer and configures the appropriate indent settings\r\n- yaifa.vim (vimscript #3096) is a port to vimscript of the above\r\n- detectindent.vim (https:\/\/github.com\/ciaranm\/detectindent) by Ciaran\r\n  McCreesh tries to auto-detect the indentation settings\r\n- GuessIndent (vimscript #4251) is based on detectindent.vim\r\n- indentdetect.vim\r\n  (https:\/\/github.com\/ervandew\/vimfiles\/blob\/master\/vim\/plugin\/indentdetect.vim)\r\n  by Eric Van Dewoestine performs a simple detection and can set defaults\r\n  based on the filespec\r\n- matchindent.vim (vimscript #4066) detects tabs, 2 and 4-space indents and\r\n  adapts the indent settings accordingly\r\n- sleuth.vim (vimscript #4375) by Tim Pope automatically adjusts 'shiftwidth'\r\n  and 'tabstop' heuristically (via a simplistic sampling that does not check\r\n  for bad or inconsistent indents) or by looking at other files of the same\r\n  type\r\n- filestyle (vimscript #5065) highlights tabs when 'expandtab' is set,\r\n  trailing spaces, and lines longer than 'textwidth', but doesn't actually\r\n  check conformance to indent\r\n- ShowSpaces (vimscript #5148) highlights spaces inside indentation, per\r\n  buffer \/ filetype.\r\n- Indent Detector (vimscript #5195) run when a file is opened or written, has\r\n  warnings about mixed tab \/ space indent, and can adapt Vim's corresponding\r\n  options automatically.\r\n\r\nUSAGE\r\nStart the examination of the current buffer or range via:\r\n    :[range]IndentConsistencyCop [{setting}]\r\nThe optional {setting} specifies the assumed correct indent setting for the\r\nbuffer \/ range (if omitted the cop can later be told), as combination of\r\neither tab, spc, or sts with a number between 1-8, e.g. \"sts4\" for a\r\n4-character soft tabstop indent.\r\nThe triggering can be done automatically for configurable filetypes with the\r\nautocmds defined in IndentConsistencyCopAutoCmds.vim (vimscript #1691).\r\n\r\nIf you chose to highlight incorrect indents, either re-execute the\r\nIndentConsistencyCop to update the highlighting, or execute\r\n    :IndentConsistencyCopOff\r\nto remove the highlightings. Entries in the quickfix and location lists will\r\nbe kept.\r\n\r\nIf you just want to check a read-only file, or do not intend to modify the\r\nfile, you don't care if Vim's buffer settings are compatible with the used\r\nindent. In this case, you can use\r\n    :[range]IndentRangeConsistencyCop [{setting}]\r\ninstead of :IndentConsistencyCop.","install_details":"INSTALLATION\r\nThe code is hosted in a Git repo at\r\n    https:\/\/github.com\/inkarkat\/vim-IndentConsistencyCop\r\nYou can use your favorite plugin manager, or \"git clone\" into a directory used\r\nfor Vim packages. Releases are on the \"stable\" branch, the latest unstable\r\ndevelopment snapshot on \"master\".\r\n\r\nThis script is also packaged as a vimball. If you have the \"gunzip\"\r\ndecompressor in your PATH, simply edit the *.vmb.gz package in Vim; otherwise,\r\ndecompress the archive first, e.g. using WinZip. Inside Vim, install by\r\nsourcing the vimball or via the :UseVimball command.\r\n    vim IndentConsistencyCop*.vmb.gz\r\n    :so %\r\nTo uninstall, use the :RmVimball command.\r\n\r\nDEPENDENCIES\r\n- Requires Vim 7.0 or higher.\r\n- Requires the ingo-library.vim plugin (vimscript #4433), version 1.039 or\r\n  higher.\r\n\r\nCONFIGURATION\r\nFor a permanent configuration, put the following commands into your vimrc:\r\n\r\nYou can select method(s) of highlighting incorrect lines via\r\ng:indentconsistencycop_highlighting; the default fills the search pattern,\r\njumps to the first error, sets 'list', uses the 'Error' highlighting and folds\r\naway the correct lines.\r\nThe variable defines the highlighting methods of incorrect lines, when this is\r\nrequested by the user. Multiple methods can be combined by concatenating the\r\nvalues. The changes done for highlighting are undone when highlighting is\r\nremoved via :IndentConsistencyCopOff.\r\n    s - Fill search pattern with all incorrect lines, so that you navigate\r\n        through all incorrect lines with n\/N.\r\n    g - Jump to the first error.\r\n    l - As a visualization aid, execute ':setlocal list' to see difference\r\n        between tabs and spaces.\r\n    m - Use error highlighting to highlight the wrong indent via the\r\n        'IndentConsistencyCop' highlight group. This is especially useful if\r\n        you don't use the search pattern in combination with 'set hlsearch'\r\n        to locate the incorrect lines.\r\n        You can customize this by defining \/ linking the\r\n        'IndentConsistencyCop' highlight group before this script is\r\n        sourced:\r\n            highlight link IndentConsistencyCop Error\r\n   f:{n} (n = 0..9)\r\n      - Fold correct lines with a context of {n} lines (like\r\n        in Vim diff mode).\r\n    q - Populate quickfix list with all incorrect lines. With uppercase Q\r\n        appends to an existing list.\r\n    w - Populate location list with all incorrect lines. With uppercase W\r\n        appends to an existing list.\r\n\r\n    let g:indentconsistencycop_highlighting = 'sglmf:3'\r\n\r\nYou can offer alternative method(s) of highlighting incorrect lines; the\r\ndefault adds lines to the quickfix list:\r\n    let g:IndentConsistencyCop_AltHighlighting =\r\n    \\   {'methods': 'Q', 'menu': 'Add wrong indents to &quickfix...'}\r\nThe configuration is a Dict with a \"methods\" entry (cp.\r\ng:indentconsistencycop_highlighting) and a \"menu\" entry. If empty, no\r\nalternative method will be presented.\r\n\r\nSome comment styles use additional whitespace characters inside the comment\r\nblock to neatly left-align the comment block, e.g. this is often used in Java\r\nand C\/C++ programs:\r\n    \/* This is a comment that spans multiple\r\n     * lines; neatly left-aligned with asterisks.\r\n     *\/\r\nThe IndentConsistencyCop would be confused by these special indents, so the\r\nnon-indent pattern defined in g:indentconsistencycop_non_indent_pattern\r\nremoves these additional whitespaces from the indent when evaluating lines.\r\n    let g:indentconsistencycop_non_indent_pattern = ' \\*\\%([*\/ \\t]\\|$\\)'\r\n(You can also override \/ set this for certain files with a buffer-local var.)\r\nThe pattern could also match in non-comment lines; to avoid that, the cop can\r\nadditionally check for a syntax match at the comment position, by supplying a\r\nregular expression for the syntax item name, and optionally another one for a\r\nsyntax item name that stops looking further down the syntax stack:\r\n    let g:indentconsistencycop_non_indent_pattern = [' \\*\\%([*\/ \\t]\\|$\\)',\r\n    \\ '^Comment$', 'FoldMarker$']\r\nThese are only considered when :syntax on.\r\n\r\nYou may never want certain indent settings in your files. As an indent\r\nmultiplier of 1 more often is the result of a mess of different indents than\r\nan explicit choice, the default forbids 'spc1' and 'sts1' from being accepted\r\nas consistent indentation:\r\n    let g:IndentConsistencyCop_UnacceptableIndentSettings = ['spc1', 'sts1']\r\nAssign an empty List or String to accept any indent setting. As an alternative\r\nto the List of unacceptable indent settings, this configuration can also take\r\na regular expression pattern:\r\n    let g:IndentConsistencyCop_UnacceptableIndentSettings = '^sts'\r\n\r\nSome comment styles use irregularly indented blocks, for example aligment to a\r\nstart of a keyword or construct in the previous line, without regard to\r\nwhether that aligns with the indent width. To avoid annoying false positives\r\non those lines, you can implement custom function(s) that detect these, so\r\nthat they will be excluded from the cop's checking. Define a List of Funcrefs:\r\n    let g:IndentConsistencyCop_line_filters =\r\n    \\   [function('MyBlockFilter'), function('MyBoilerplateFilter')]\r\nThe function must take two startLnum, endLnum arguments and return a\r\nDictionary whose keys represent the filtered out line numbers. The cop ignores\r\nthe union of all returned Sets.\r\n\r\nIn case of really irregular lines where the removal of some whitespace per\r\ng:indentconsistencycop_non_indent_pattern isn't possible, the lines can be\r\nignored altogether. Lines can be selected by a List of patterns, optionally\r\nlimited to certain syntax item names (tested after the matched text),\r\noptionally with another one for a syntax item name that stops looking further\r\ndown the syntax stack:\r\n    let g:IndentConsistencyCop_IgnorePatterns = [\r\n    \\   '^\\s\\+####D',\r\n    \\   ['^\\s\\+', 'podVerbatimLine']\r\n    \\]\r\n(This is implemented as a default g:IndentConsistencyCop_line_filters.)\r\n\r\nBy default, the cop sets 'copyindent' and 'preserveindent' if the buffer's\r\nindent is inconsistent and this is ignored by the user, as these options\r\ntypically make Vim respect the original indent. This is undone automatically\r\nif the buffer becomes consistent or the cop is turned off via\r\n:IndentConsistencyCopOff. To disable this feature, set\r\n    let g:IndentConsistencyCop_IsCopyAndPreserveIndent = 0\r\n(This is implemented as a default IndentConsistencyCop-event.)\r\n\r\nBy default, the cop also checks for bad whitespace combinations (i.e. space\r\ncharacter(s) followed by one or more tabs) everywhere inside the buffer, not\r\njust in indent. To turn this off and just alert to these bad mixes when they\r\noccur at the beginning of the line:\r\n    let g:IndentConsistencyCop_IsFindBadMixEverywhere = 0\r\n\r\nThe default block alignment g:IndentConsistencyCop_line_filters, can be\r\ntuned with regards to what it considers a block via:\r\n    let g:IndentConsistencyCop_BlockAlignmentPattern = '\\<'\r\nThe default handles alignment to previous keywords, brackets, quotes, and\r\n@Annotation, $var.\r\n\r\nINTEGRATION\r\nThe :IndentConsistencyCop and :IndentRangeConsistencyCop commands fill a\r\nbuffer-scoped dictionary with the results of the check. These results can be\r\nconsumed by other Vim integrations (e.g. for a custom 'statusline').\r\n\r\n    b:indentconsistencycop_result.maxIndent\r\nMaximum indent (in columns) found in the entire buffer. (Not reduced by range\r\nchecks.)\r\n\r\n    b:indentconsistencycop_result.minIndent\r\nMinimum indent (in columns, not counting lines that do not start with\r\nwhitespace at all) found in the entire buffer. (Not increased by range\r\nchecks.)\r\n\r\n    b:indentconsistencycop_result.indentSetting\r\nString representing the actual indent settings. Consistent indent settings are\r\nrepresented by 'tabN', 'spcN', 'stsN' (where N is the indent multiplier) or\r\n'none' (meaning no indent found in buffer). Completely inconsistent indent\r\nsettings are shown as 'XXX'; a setting which is almost consistent, with only\r\nsome bad mix of spaces and tabs, is represented by 'BADtabN', 'BADspcN' or\r\n'BADstsN'.\r\n\r\n    b:indentconsistencycop_result.isConsistent\r\nFlag whether the indent in the entire buffer is consistent. (Not set by range\r\nchecks.)\r\n\r\n    b:indentconsistencycop_result.isDefinite\r\nFlag whether there has been enough indent to make a definite judgement about\r\nthe buffer indent settings. (Not set by range checks.)\r\n\r\n    b:indentconsistencycop_result.acknowledgedByUserSetting\r\nIndent setting that the user has explicitly acknowledged in its interaction\r\nwith the cop (by answering \"Wrong\" or \"Change\" in one of the dialogs).\r\n\r\n    b:indentconsistencycop_result.isDefiniteOrAcknowledgedByUser\r\nCombination of the above two: Flag whether there either has been enough indent\r\nto make a definite judgement about the buffer indent settings, or whether the\r\nuser has explicitly acknowledged the current indent settings in its\r\ninteraction with the cop (by answering \"Wrong\" or \"Change\" in one of the\r\ndialogs).\r\n\r\n    b:indentconsistencycop_result.bufferSettings\r\nString representing the buffer settings. One of 'tabN', 'spcN', 'stsN' (where\r\nN is the indent multiplier), or '???' (meaning inconsistent buffer indent\r\nsettings).\r\n\r\n    b:indentconsistencycop_result.isBufferSettingsConsistent\r\nFlag whether the buffer indent settings (tabstop, softtabstop, shiftwidth,\r\nexpandtab) are consistent with each other.\r\n\r\n    b:indentconsistencycop_result.isConsistentWithBufferSettings\r\nFlag whether the indent in the entire buffer is consistent with the buffer\r\nindent settings. (Not set by range checks; :IndentRangeConsistencyCop leaves\r\nthis flag unchanged.)\r\n\r\n    b:indentconsistencycop_result.isIgnore\r\nFlag whether the user chose to ignore the inconsistent results. This can be\r\nused by integrations (like IndentConsistencyCopAutoCmds) to cease scheduling\r\nof further cop runs in this buffer.\r\n\r\n    b:indentconsistencycop_result.isOff\r\nFlag whether the cop has been (at least temporarily) disabled via\r\n:IndentConsistencyCopOff.\r\n\r\nThe user queries can be extended with additional menu entries, defined in a\r\nDictionary:\r\n    let g:IndentConsistencyCop_MenuExtensions = {\r\n    \\   'Dummy': {\r\n    \\       'priority': 100,\r\n    \\       'choice':   'Dumm&y',\r\n    \\       'Action':   function('DummyAction')\r\n    \\   },\r\n    \\   [...]\r\n    \\}\r\nWith the optional \"choice\" attribute, you can define an accelerator key via &;\r\nthe rest of the text must be identical to the key!\r\nThe optional \"priority\" attribute determines the order of the extension\r\nentries; they will always come after the plugin's core entries, though.\r\nThe mandatory \"Action\" attribute is a Funcref to a function that is invoked\r\nwithout arguments if the menu entry is chosen.\r\n\r\nThe plugin emits a User event \"IndentConsistencyCop\" after each run.\r\nIntegrations can check the b:indentconsistencycop_result dictionary to react\r\ndifferently to various conditions. For example:\r\n    augroup IndentConsistencyCopCustomization\r\n        autocmd!\r\n        autocmd User IndentConsistencyCop unsilent echomsg 'The cop is'\r\n        \\   b:indentconsistencycop_result.isOff ? 'off' : 'on'\r\n    augroup END\r\nThe following turns the buffer read-only if it is inconsistent:\r\n        autocmd User IndentConsistencyCop let &l:readonly =\r\n        \\   ! b:indentconsistencycop_result.isConsistent &&\r\n        \\   ! b:indentconsistencycop_result.isOff","5":"INSTALLATION\r\nThe code is hosted in a Git repo at\r\n    https:\/\/github.com\/inkarkat\/vim-IndentConsistencyCop\r\nYou can use your favorite plugin manager, or \"git clone\" into a directory used\r\nfor Vim packages. Releases are on the \"stable\" branch, the latest unstable\r\ndevelopment snapshot on \"master\".\r\n\r\nThis script is also packaged as a vimball. If you have the \"gunzip\"\r\ndecompressor in your PATH, simply edit the *.vmb.gz package in Vim; otherwise,\r\ndecompress the archive first, e.g. using WinZip. Inside Vim, install by\r\nsourcing the vimball or via the :UseVimball command.\r\n    vim IndentConsistencyCop*.vmb.gz\r\n    :so %\r\nTo uninstall, use the :RmVimball command.\r\n\r\nDEPENDENCIES\r\n- Requires Vim 7.0 or higher.\r\n- Requires the ingo-library.vim plugin (vimscript #4433), version 1.039 or\r\n  higher.\r\n\r\nCONFIGURATION\r\nFor a permanent configuration, put the following commands into your vimrc:\r\n\r\nYou can select method(s) of highlighting incorrect lines via\r\ng:indentconsistencycop_highlighting; the default fills the search pattern,\r\njumps to the first error, sets 'list', uses the 'Error' highlighting and folds\r\naway the correct lines.\r\nThe variable defines the highlighting methods of incorrect lines, when this is\r\nrequested by the user. Multiple methods can be combined by concatenating the\r\nvalues. The changes done for highlighting are undone when highlighting is\r\nremoved via :IndentConsistencyCopOff.\r\n    s - Fill search pattern with all incorrect lines, so that you navigate\r\n        through all incorrect lines with n\/N.\r\n    g - Jump to the first error.\r\n    l - As a visualization aid, execute ':setlocal list' to see difference\r\n        between tabs and spaces.\r\n    m - Use error highlighting to highlight the wrong indent via the\r\n        'IndentConsistencyCop' highlight group. This is especially useful if\r\n        you don't use the search pattern in combination with 'set hlsearch'\r\n        to locate the incorrect lines.\r\n        You can customize this by defining \/ linking the\r\n        'IndentConsistencyCop' highlight group before this script is\r\n        sourced:\r\n            highlight link IndentConsistencyCop Error\r\n   f:{n} (n = 0..9)\r\n      - Fold correct lines with a context of {n} lines (like\r\n        in Vim diff mode).\r\n    q - Populate quickfix list with all incorrect lines. With uppercase Q\r\n        appends to an existing list.\r\n    w - Populate location list with all incorrect lines. With uppercase W\r\n        appends to an existing list.\r\n\r\n    let g:indentconsistencycop_highlighting = 'sglmf:3'\r\n\r\nYou can offer alternative method(s) of highlighting incorrect lines; the\r\ndefault adds lines to the quickfix list:\r\n    let g:IndentConsistencyCop_AltHighlighting =\r\n    \\   {'methods': 'Q', 'menu': 'Add wrong indents to &quickfix...'}\r\nThe configuration is a Dict with a \"methods\" entry (cp.\r\ng:indentconsistencycop_highlighting) and a \"menu\" entry. If empty, no\r\nalternative method will be presented.\r\n\r\nSome comment styles use additional whitespace characters inside the comment\r\nblock to neatly left-align the comment block, e.g. this is often used in Java\r\nand C\/C++ programs:\r\n    \/* This is a comment that spans multiple\r\n     * lines; neatly left-aligned with asterisks.\r\n     *\/\r\nThe IndentConsistencyCop would be confused by these special indents, so the\r\nnon-indent pattern defined in g:indentconsistencycop_non_indent_pattern\r\nremoves these additional whitespaces from the indent when evaluating lines.\r\n    let g:indentconsistencycop_non_indent_pattern = ' \\*\\%([*\/ \\t]\\|$\\)'\r\n(You can also override \/ set this for certain files with a buffer-local var.)\r\nThe pattern could also match in non-comment lines; to avoid that, the cop can\r\nadditionally check for a syntax match at the comment position, by supplying a\r\nregular expression for the syntax item name, and optionally another one for a\r\nsyntax item name that stops looking further down the syntax stack:\r\n    let g:indentconsistencycop_non_indent_pattern = [' \\*\\%([*\/ \\t]\\|$\\)',\r\n    \\ '^Comment$', 'FoldMarker$']\r\nThese are only considered when :syntax on.\r\n\r\nYou may never want certain indent settings in your files. As an indent\r\nmultiplier of 1 more often is the result of a mess of different indents than\r\nan explicit choice, the default forbids 'spc1' and 'sts1' from being accepted\r\nas consistent indentation:\r\n    let g:IndentConsistencyCop_UnacceptableIndentSettings = ['spc1', 'sts1']\r\nAssign an empty List or String to accept any indent setting. As an alternative\r\nto the List of unacceptable indent settings, this configuration can also take\r\na regular expression pattern:\r\n    let g:IndentConsistencyCop_UnacceptableIndentSettings = '^sts'\r\n\r\nSome comment styles use irregularly indented blocks, for example aligment to a\r\nstart of a keyword or construct in the previous line, without regard to\r\nwhether that aligns with the indent width. To avoid annoying false positives\r\non those lines, you can implement custom function(s) that detect these, so\r\nthat they will be excluded from the cop's checking. Define a List of Funcrefs:\r\n    let g:IndentConsistencyCop_line_filters =\r\n    \\   [function('MyBlockFilter'), function('MyBoilerplateFilter')]\r\nThe function must take two startLnum, endLnum arguments and return a\r\nDictionary whose keys represent the filtered out line numbers. The cop ignores\r\nthe union of all returned Sets.\r\n\r\nIn case of really irregular lines where the removal of some whitespace per\r\ng:indentconsistencycop_non_indent_pattern isn't possible, the lines can be\r\nignored altogether. Lines can be selected by a List of patterns, optionally\r\nlimited to certain syntax item names (tested after the matched text),\r\noptionally with another one for a syntax item name that stops looking further\r\ndown the syntax stack:\r\n    let g:IndentConsistencyCop_IgnorePatterns = [\r\n    \\   '^\\s\\+####D',\r\n    \\   ['^\\s\\+', 'podVerbatimLine']\r\n    \\]\r\n(This is implemented as a default g:IndentConsistencyCop_line_filters.)\r\n\r\nBy default, the cop sets 'copyindent' and 'preserveindent' if the buffer's\r\nindent is inconsistent and this is ignored by the user, as these options\r\ntypically make Vim respect the original indent. This is undone automatically\r\nif the buffer becomes consistent or the cop is turned off via\r\n:IndentConsistencyCopOff. To disable this feature, set\r\n    let g:IndentConsistencyCop_IsCopyAndPreserveIndent = 0\r\n(This is implemented as a default IndentConsistencyCop-event.)\r\n\r\nBy default, the cop also checks for bad whitespace combinations (i.e. space\r\ncharacter(s) followed by one or more tabs) everywhere inside the buffer, not\r\njust in indent. To turn this off and just alert to these bad mixes when they\r\noccur at the beginning of the line:\r\n    let g:IndentConsistencyCop_IsFindBadMixEverywhere = 0\r\n\r\nThe default block alignment g:IndentConsistencyCop_line_filters, can be\r\ntuned with regards to what it considers a block via:\r\n    let g:IndentConsistencyCop_BlockAlignmentPattern = '\\<'\r\nThe default handles alignment to previous keywords, brackets, quotes, and\r\n@Annotation, $var.\r\n\r\nINTEGRATION\r\nThe :IndentConsistencyCop and :IndentRangeConsistencyCop commands fill a\r\nbuffer-scoped dictionary with the results of the check. These results can be\r\nconsumed by other Vim integrations (e.g. for a custom 'statusline').\r\n\r\n    b:indentconsistencycop_result.maxIndent\r\nMaximum indent (in columns) found in the entire buffer. (Not reduced by range\r\nchecks.)\r\n\r\n    b:indentconsistencycop_result.minIndent\r\nMinimum indent (in columns, not counting lines that do not start with\r\nwhitespace at all) found in the entire buffer. (Not increased by range\r\nchecks.)\r\n\r\n    b:indentconsistencycop_result.indentSetting\r\nString representing the actual indent settings. Consistent indent settings are\r\nrepresented by 'tabN', 'spcN', 'stsN' (where N is the indent multiplier) or\r\n'none' (meaning no indent found in buffer). Completely inconsistent indent\r\nsettings are shown as 'XXX'; a setting which is almost consistent, with only\r\nsome bad mix of spaces and tabs, is represented by 'BADtabN', 'BADspcN' or\r\n'BADstsN'.\r\n\r\n    b:indentconsistencycop_result.isConsistent\r\nFlag whether the indent in the entire buffer is consistent. (Not set by range\r\nchecks.)\r\n\r\n    b:indentconsistencycop_result.isDefinite\r\nFlag whether there has been enough indent to make a definite judgement about\r\nthe buffer indent settings. (Not set by range checks.)\r\n\r\n    b:indentconsistencycop_result.acknowledgedByUserSetting\r\nIndent setting that the user has explicitly acknowledged in its interaction\r\nwith the cop (by answering \"Wrong\" or \"Change\" in one of the dialogs).\r\n\r\n    b:indentconsistencycop_result.isDefiniteOrAcknowledgedByUser\r\nCombination of the above two: Flag whether there either has been enough indent\r\nto make a definite judgement about the buffer indent settings, or whether the\r\nuser has explicitly acknowledged the current indent settings in its\r\ninteraction with the cop (by answering \"Wrong\" or \"Change\" in one of the\r\ndialogs).\r\n\r\n    b:indentconsistencycop_result.bufferSettings\r\nString representing the buffer settings. One of 'tabN', 'spcN', 'stsN' (where\r\nN is the indent multiplier), or '???' (meaning inconsistent buffer indent\r\nsettings).\r\n\r\n    b:indentconsistencycop_result.isBufferSettingsConsistent\r\nFlag whether the buffer indent settings (tabstop, softtabstop, shiftwidth,\r\nexpandtab) are consistent with each other.\r\n\r\n    b:indentconsistencycop_result.isConsistentWithBufferSettings\r\nFlag whether the indent in the entire buffer is consistent with the buffer\r\nindent settings. (Not set by range checks; :IndentRangeConsistencyCop leaves\r\nthis flag unchanged.)\r\n\r\n    b:indentconsistencycop_result.isIgnore\r\nFlag whether the user chose to ignore the inconsistent results. This can be\r\nused by integrations (like IndentConsistencyCopAutoCmds) to cease scheduling\r\nof further cop runs in this buffer.\r\n\r\n    b:indentconsistencycop_result.isOff\r\nFlag whether the cop has been (at least temporarily) disabled via\r\n:IndentConsistencyCopOff.\r\n\r\nThe user queries can be extended with additional menu entries, defined in a\r\nDictionary:\r\n    let g:IndentConsistencyCop_MenuExtensions = {\r\n    \\   'Dummy': {\r\n    \\       'priority': 100,\r\n    \\       'choice':   'Dumm&y',\r\n    \\       'Action':   function('DummyAction')\r\n    \\   },\r\n    \\   [...]\r\n    \\}\r\nWith the optional \"choice\" attribute, you can define an accelerator key via &;\r\nthe rest of the text must be identical to the key!\r\nThe optional \"priority\" attribute determines the order of the extension\r\nentries; they will always come after the plugin's core entries, though.\r\nThe mandatory \"Action\" attribute is a Funcref to a function that is invoked\r\nwithout arguments if the menu entry is chosen.\r\n\r\nThe plugin emits a User event \"IndentConsistencyCop\" after each run.\r\nIntegrations can check the b:indentconsistencycop_result dictionary to react\r\ndifferently to various conditions. For example:\r\n    augroup IndentConsistencyCopCustomization\r\n        autocmd!\r\n        autocmd User IndentConsistencyCop unsilent echomsg 'The cop is'\r\n        \\   b:indentconsistencycop_result.isOff ? 'off' : 'on'\r\n    augroup END\r\nThe following turns the buffer read-only if it is inconsistent:\r\n        autocmd User IndentConsistencyCop let &l:readonly =\r\n        \\   ! b:indentconsistencycop_result.isConsistent &&\r\n        \\   ! b:indentconsistencycop_result.isOff","first_name":"Ingo","6":"Ingo","last_name":"Karkat","7":"Karkat","releases":[{"0":"1690","vim_version":"7.0","1":"7.0","script_version":"3.00","2":"3.00","version_comment":"- Add b:indentconsistencycop_result.acknowledgedByUserSetting\r\n- ENH: Allow extension of the plugin's user queries with additional menu entries. This is used by IndentConsistencyCopAutoCmds.vim to implement blacklisting of certain files so that they are never checked again.\r\n- Add g:IndentConsistencyCop_UnacceptableIndentSettings and by default forbid indents with multiplier 1 (i.e. 'spc1' and 'sts1') from being accepted as consistent indentation.\r\n- ENH: g:indentconsistencycop_non_indent_pattern now also enforces a comment syntax item (if :syntax on) for applying the special indent pattern, to avoid false positives in non-comment lines that just look like they're starting with a comment prefix.\r\n- Add g:IndentConsistencyCop_IgnorePatterns to completely ignore certain lines that match a pattern (and optionally have a certain syntax item name), implemented as a default g:IndentConsistencyCop_line_filters.\r\n- Emit \"IndentConsistencyCop\" User event after each cop command, so that customizations can react to the results.\r\n- Set 'copyindent' and 'preserveindent' when the buffer is inconsistent and this is ignored (configurable via |g:IndentConsistencyCop_IsCopyAndPreserveIndent|).\r\n- ENH: Allow passing correct indent setting as an :Indent[Range]ConsistencyCop argument. (Overriding of a wrongly found indent setting is already offered in the cop's dialog.)\r\n- Alert to bad \"tab after space\" whitespace combinations everywhere, not just in indent. Can be configured (turned off) via g:IndentConsistencyCop_IsFindBadMixEverywhere.\r\n- ENH: Allow population of quickfix \/ location list via g:indentconsistencycop_highlighting values q\/Q\/w\/W.\r\n- Offer alternative highlighting methods in menu via g:IndentConsistencyCop_AltHighlighting, by default adding to the quickfix list.\r\n- Allow to tweak IndentConsistencyCop#BlockAlignment#Filter() via g:IndentConsistencyCop_BlockAlignmentPattern.\r\n- Also support @Annotation, $var as starts of blocks. *** You need to update to ingo-library (vimscript #4433) version 1.039! ***","3":"- Add b:indentconsistencycop_result.acknowledgedByUserSetting\r\n- ENH: Allow extension of the plugin's user queries with additional menu entries. This is used by IndentConsistencyCopAutoCmds.vim to implement blacklisting of certain files so that they are never checked again.\r\n- Add g:IndentConsistencyCop_UnacceptableIndentSettings and by default forbid indents with multiplier 1 (i.e. 'spc1' and 'sts1') from being accepted as consistent indentation.\r\n- ENH: g:indentconsistencycop_non_indent_pattern now also enforces a comment syntax item (if :syntax on) for applying the special indent pattern, to avoid false positives in non-comment lines that just look like they're starting with a comment prefix.\r\n- Add g:IndentConsistencyCop_IgnorePatterns to completely ignore certain lines that match a pattern (and optionally have a certain syntax item name), implemented as a default g:IndentConsistencyCop_line_filters.\r\n- Emit \"IndentConsistencyCop\" User event after each cop command, so that customizations can react to the results.\r\n- Set 'copyindent' and 'preserveindent' when the buffer is inconsistent and this is ignored (configurable via |g:IndentConsistencyCop_IsCopyAndPreserveIndent|).\r\n- ENH: Allow passing correct indent setting as an :Indent[Range]ConsistencyCop argument. (Overriding of a wrongly found indent setting is already offered in the cop's dialog.)\r\n- Alert to bad \"tab after space\" whitespace combinations everywhere, not just in indent. Can be configured (turned off) via g:IndentConsistencyCop_IsFindBadMixEverywhere.\r\n- ENH: Allow population of quickfix \/ location list via g:indentconsistencycop_highlighting values q\/Q\/w\/W.\r\n- Offer alternative highlighting methods in menu via g:IndentConsistencyCop_AltHighlighting, by default adding to the quickfix list.\r\n- Allow to tweak IndentConsistencyCop#BlockAlignment#Filter() via g:IndentConsistencyCop_BlockAlignmentPattern.\r\n- Also support @Annotation, $var as starts of blocks. *** You need to update to ingo-library (vimscript #4433) version 1.039! ***","package":"IndentConsistencyCop-3.00.vmb.gz","4":"IndentConsistencyCop-3.00.vmb.gz","src_id":"27019","5":"27019","creation_date":"1582260171","6":"1582260171"},{"0":"1690","vim_version":"7.0","1":"7.0","script_version":"2.00","2":"2.00","version_comment":"- Minor: Replace explicit regexp engine workaround with ingo\/compat\/regexp.vim.\r\n- When choosing \"Highlight wrong indents...\" followed by \"Not best guess\" or \"Not chosen setting\", also adapt the buffer settings to that indent setting, as the user has indicated that this is the right one.\r\n- ENH: Add \"Just change buffer settings\" alternative for \"Highlight wrong indents...\" search that only adapts the buffer settings, but does not (in fact clears any) highlight. Often, I must not fix existing wrong indentation, but still would like to adapt my buffer settings to cause no addition harm to the file's indent.\r\n- ENH: Also query the value (multiplier) of 'tabstop' when querying for the indent setting. Though this doesn't affect the consistent \/ inconsistent verdict, it's often an important aspect of a correct visualization.\r\n- Support buffer-local b:indentconsistencycop_non_indent_pattern configuration, too.\r\n- Introduce additional b:indentconsistencycop_result.isDefiniteOrAcknowledgedByUser reporting flag.\r\n- Offer \"Wrong, use buffer settings\" in addition to the existing \"Wrong, choose correct setting\" if the buffer settings are consistent.\r\n- When choosing |Ignore| on reported inconsistencies in the indent, turn off any previous highlighting by the cop (like :IndentConsistencyCopOff).\r\n- Restore last search pattern from history when turning off the cop.\r\n- When there are bad mixes of spaces and tabstop, the individual character widths can't be simply accumulated; need to use strdisplaywidth() to arrive at the correct indent width.\r\n- FIX: :.IndentConsistencyCop on a closed fold only considers the current line, not all lines inside the fold. Need to use ingo#range#NetStart\/End().\r\n- ENH: Add g:IndentConsistencyCop_line_filters configuration to exclude certain, irregular lines from checking. This is a more powerful variant of g:indentconsistencycop_non_indent_pattern. Use IndentConsistencyCop#Filter#BlockAlignment() by default, which handles alignment to previous keywords, brackets, and quotes.\r\n- When the best guess is equal to the buffer indent, already indicate that in the |Ignore| action choice. This wasn't made clear enough by the full description, and users are tempted to choose |Just change buffer settings|, where then the buffer setting isn't available, and the setting would have to be tediously re-chosen.\r\n- CHG: Default to |Change| instead of |Ignore| when just the buffer settings are wrong, and the assessment is solid. This is the most common (and sensible) choice. If there's not enough indent for that, don't default to anything. *** You need to update to ingo-library (vimscript #4433) version 1.024! ***","3":"- Minor: Replace explicit regexp engine workaround with ingo\/compat\/regexp.vim.\r\n- When choosing \"Highlight wrong indents...\" followed by \"Not best guess\" or \"Not chosen setting\", also adapt the buffer settings to that indent setting, as the user has indicated that this is the right one.\r\n- ENH: Add \"Just change buffer settings\" alternative for \"Highlight wrong indents...\" search that only adapts the buffer settings, but does not (in fact clears any) highlight. Often, I must not fix existing wrong indentation, but still would like to adapt my buffer settings to cause no addition harm to the file's indent.\r\n- ENH: Also query the value (multiplier) of 'tabstop' when querying for the indent setting. Though this doesn't affect the consistent \/ inconsistent verdict, it's often an important aspect of a correct visualization.\r\n- Support buffer-local b:indentconsistencycop_non_indent_pattern configuration, too.\r\n- Introduce additional b:indentconsistencycop_result.isDefiniteOrAcknowledgedByUser reporting flag.\r\n- Offer \"Wrong, use buffer settings\" in addition to the existing \"Wrong, choose correct setting\" if the buffer settings are consistent.\r\n- When choosing |Ignore| on reported inconsistencies in the indent, turn off any previous highlighting by the cop (like :IndentConsistencyCopOff).\r\n- Restore last search pattern from history when turning off the cop.\r\n- When there are bad mixes of spaces and tabstop, the individual character widths can't be simply accumulated; need to use strdisplaywidth() to arrive at the correct indent width.\r\n- FIX: :.IndentConsistencyCop on a closed fold only considers the current line, not all lines inside the fold. Need to use ingo#range#NetStart\/End().\r\n- ENH: Add g:IndentConsistencyCop_line_filters configuration to exclude certain, irregular lines from checking. This is a more powerful variant of g:indentconsistencycop_non_indent_pattern. Use IndentConsistencyCop#Filter#BlockAlignment() by default, which handles alignment to previous keywords, brackets, and quotes.\r\n- When the best guess is equal to the buffer indent, already indicate that in the |Ignore| action choice. This wasn't made clear enough by the full description, and users are tempted to choose |Just change buffer settings|, where then the buffer setting isn't available, and the setting would have to be tediously re-chosen.\r\n- CHG: Default to |Change| instead of |Ignore| when just the buffer settings are wrong, and the assessment is solid. This is the most common (and sensible) choice. If there's not enough indent for that, don't default to anything. *** You need to update to ingo-library (vimscript #4433) version 1.024! ***","package":"IndentConsistencyCop-2.00.vmb.gz","4":"IndentConsistencyCop-2.00.vmb.gz","src_id":"25734","5":"25734","creation_date":"1514063235","6":"1514063235"},{"0":"1690","vim_version":"7.0","1":"7.0","script_version":"1.45","2":"1.45","version_comment":"- Minor: Highlight action checks are dependent on 'iskeyword' setting, and could cause script errors.\r\n- Add dependency to ingo-library (vimscript #4433). *** You need to separately install ingo-library (vimscript #4433) version 1.019 (or higher)! ***","3":"- Minor: Highlight action checks are dependent on 'iskeyword' setting, and could cause script errors.\r\n- Add dependency to ingo-library (vimscript #4433). *** You need to separately install ingo-library (vimscript #4433) version 1.019 (or higher)! ***","package":"IndentConsistencyCop-1.45.vmb.gz","4":"IndentConsistencyCop-1.45.vmb.gz","src_id":"22695","5":"22695","creation_date":"1418415914","6":"1418415914"},{"0":"1690","vim_version":"7.0","1":"7.0","script_version":"1.44","2":"1.44","version_comment":"- BUG: The version 1.43 workaround for the Vim 7.4 new regexp engine was ineffective, because the \\%#=1 atom needs to be prepended to the entire regular expression, but that's not possible with the configuration value alone. (Also, the workaround mistakenly specified auto-select (0) instead of old engine (1).) Move the workaround to s:GetBeginningWhitespace() instead.\r\n- ENH: Close all consistent parts of the buffer when highlighting the inconsistencies via folding, and restore the original 'foldlevel' setting (and therefore the global fold state set by zM \/ zR) on :IndentConsistencyCopOff. Thanks to Marcelo Mont\u00c3\u00ba for the idea.\r\n- ENH: Enable folding to highlight the inconsistencies when it was previously :set nofoldenable'd.","3":"- BUG: The version 1.43 workaround for the Vim 7.4 new regexp engine was ineffective, because the \\%#=1 atom needs to be prepended to the entire regular expression, but that's not possible with the configuration value alone. (Also, the workaround mistakenly specified auto-select (0) instead of old engine (1).) Move the workaround to s:GetBeginningWhitespace() instead.\r\n- ENH: Close all consistent parts of the buffer when highlighting the inconsistencies via folding, and restore the original 'foldlevel' setting (and therefore the global fold state set by zM \/ zR) on :IndentConsistencyCopOff. Thanks to Marcelo Mont\u00c3\u00ba for the idea.\r\n- ENH: Enable folding to highlight the inconsistencies when it was previously :set nofoldenable'd.","package":"IndentConsistencyCop-1.44.vmb.gz","4":"IndentConsistencyCop-1.44.vmb.gz","src_id":"21309","5":"21309","creation_date":"1389475115","6":"1389475115"},{"0":"1690","vim_version":"7.0","1":"7.0","script_version":"1.43","2":"1.43","version_comment":"- Minor: Make matchstr() robust against 'ignorecase'.\r\n- Improve g:indentconsistencycop_non_indent_pattern to also handle empty comment lines with a sole ' *' prefix. Thanks to Marcelo Montu for reporting this.","3":"- Minor: Make matchstr() robust against 'ignorecase'.\r\n- Improve g:indentconsistencycop_non_indent_pattern to also handle empty comment lines with a sole ' *' prefix. Thanks to Marcelo Montu for reporting this.","package":"IndentConsistencyCop-1.43.vmb.gz","4":"IndentConsistencyCop-1.43.vmb.gz","src_id":"21215","5":"21215","creation_date":"1387439785","6":"1387439785"},{"0":"1690","vim_version":"7.0","1":"7.0","script_version":"1.42","2":"1.42","version_comment":"When a perfect or authoritative rating didn't pass the majority rule, try to turn around the verdict by checking consistency with buffer settings, as is done for small indents only. For example, this avoids a wrong verdict of inconsistent spc8 when there are more spc8 than spc4. Thanks to Marcelo Mont\u00c3\u00ba for reporting this issue.","3":"When a perfect or authoritative rating didn't pass the majority rule, try to turn around the verdict by checking consistency with buffer settings, as is done for small indents only. For example, this avoids a wrong verdict of inconsistent spc8 when there are more spc8 than spc4. Thanks to Marcelo Mont\u00c3\u00ba for reporting this issue.","package":"IndentConsistencyCop-1.42.vmb.gz","4":"IndentConsistencyCop-1.42.vmb.gz","src_id":"19162","5":"19162","creation_date":"1355220311","6":"1355220311"},{"0":"1690","vim_version":"7.0","1":"7.0","script_version":"1.41","2":"1.41","version_comment":"Change the behavior of :IndentRangeConsistencyCop to consider the buffer settings to turn around the verdict of \"inconsistent indent\" (but still not report inconsistent buffer settings alone). Otherwise, together with the IndentConsistencyCopAutoCmds triggers, it can happen that on opening (i.e. :IndentConsistencyCop), the file is judged okay (considering the buffer settings), but on writing the buffer (:IndentRangeConsistencyCop), a potential inconsistency due to too small indent is reported. Thanks to Marcelo Mont\u00c3\u00ba for reporting this issue.","3":"Change the behavior of :IndentRangeConsistencyCop to consider the buffer settings to turn around the verdict of \"inconsistent indent\" (but still not report inconsistent buffer settings alone). Otherwise, together with the IndentConsistencyCopAutoCmds triggers, it can happen that on opening (i.e. :IndentConsistencyCop), the file is judged okay (considering the buffer settings), but on writing the buffer (:IndentRangeConsistencyCop), a potential inconsistency due to too small indent is reported. Thanks to Marcelo Mont\u00c3\u00ba for reporting this issue.","package":"IndentConsistencyCop-1.41.vmb.gz","4":"IndentConsistencyCop-1.41.vmb.gz","src_id":"19133","5":"19133","creation_date":"1354908235","6":"1354908235"},{"0":"1690","vim_version":"7.0","1":"7.0","script_version":"1.40","2":"1.40","version_comment":"- The cop can often do a solid assessment when the maximum indent is 8. Only when there are no smaller indents, a higher indent is needed to unequivocally recognize soft tabstops.\r\n- ENH: Better handle integer overflow when rating and normalizing: Limit to MAX_INT instead of carrying on with negative ratings, or just use Float values when Vim has support for it.\r\n- When we have only a few, widely indented lines, there may be more than one way to interpret them as a perfect setting. Choose one over the other via some simple heuristics instead of the previous assertion error.\r\n- FIX: Fall back to the old :2match when matchadd() is not available.","3":"- The cop can often do a solid assessment when the maximum indent is 8. Only when there are no smaller indents, a higher indent is needed to unequivocally recognize soft tabstops.\r\n- ENH: Better handle integer overflow when rating and normalizing: Limit to MAX_INT instead of carrying on with negative ratings, or just use Float values when Vim has support for it.\r\n- When we have only a few, widely indented lines, there may be more than one way to interpret them as a perfect setting. Choose one over the other via some simple heuristics instead of the previous assertion error.\r\n- FIX: Fall back to the old :2match when matchadd() is not available.","package":"IndentConsistencyCop-1.40.vmb.gz","4":"IndentConsistencyCop-1.40.vmb.gz","src_id":"18775","5":"18775","creation_date":"1349943345","6":"1349943345"},{"0":"1690","vim_version":"7.0","1":"7.0","script_version":"1.31","2":"1.31","version_comment":"- Use matchadd() instead of :2match to avoid clashes with user highlightings (or other plugins like html_matchtag.vim).\r\n- ENH: Clear highlighting when another buffer is loaded into the window to avoid that the highlightings persist in a now wrong context.","3":"- Use matchadd() instead of :2match to avoid clashes with user highlightings (or other plugins like html_matchtag.vim).\r\n- ENH: Clear highlighting when another buffer is loaded into the window to avoid that the highlightings persist in a now wrong context.","package":"IndentConsistencyCop.vba.gz","4":"IndentConsistencyCop.vba.gz","src_id":"17707","5":"17707","creation_date":"1333446288","6":"1333446288"},{"0":"1690","vim_version":"7.0","1":"7.0","script_version":"1.30","2":"1.30","version_comment":"ENH: Avoid the spurious \"potential inconsistency with buffer settings\" warning when there are only small consistent indents detected as space-indents, but the equivalent softtabstop-indent is consistent with the buffer settings. As many files only have small indents, this warning popped up regularly and has been the most annoying for me, also because to rectify it, one has to answer three questions: \"[W]rong\", \"[s]ofttabstop\", [N]). ","3":"ENH: Avoid the spurious \"potential inconsistency with buffer settings\" warning when there are only small consistent indents detected as space-indents, but the equivalent softtabstop-indent is consistent with the buffer settings. As many files only have small indents, this warning popped up regularly and has been the most annoying for me, also because to rectify it, one has to answer three questions: \"[W]rong\", \"[s]ofttabstop\", [N]). ","package":"IndentConsistencyCop.vba.gz","4":"IndentConsistencyCop.vba.gz","src_id":"16949","5":"16949","creation_date":"1322034182","6":"1322034182"},{"0":"1690","vim_version":"7.0","1":"7.0","script_version":"1.21","2":"1.21","version_comment":"- Added b:indentconsistencycop_result.isIgnore to allow the IndentConsistencyCopAutoCmds integration to suspend further invocations of the cop in the buffer. \r\n- BUG: :IndentRangeConsistencyCop didn't report inconsistencies at all because of a bad conditional statement introduced in 1.20.014. \r\n- Using separate autoload script to help speed up Vim startup. \r\n- Added separate help file and packaging the plugin as a vimball. ","3":"- Added b:indentconsistencycop_result.isIgnore to allow the IndentConsistencyCopAutoCmds integration to suspend further invocations of the cop in the buffer. \r\n- BUG: :IndentRangeConsistencyCop didn't report inconsistencies at all because of a bad conditional statement introduced in 1.20.014. \r\n- Using separate autoload script to help speed up Vim startup. \r\n- Added separate help file and packaging the plugin as a vimball. ","package":"IndentConsistencyCop.vba.gz","4":"IndentConsistencyCop.vba.gz","src_id":"14665","5":"14665","creation_date":"1293808822","6":"1293808822"},{"0":"1690","vim_version":"7.0","1":"7.0","script_version":"1.20.017","2":"1.20.017","version_comment":"BF: Undefined variable l:isEntireBuffer in IndentBufferConsistencyCop().  ","3":"BF: Undefined variable l:isEntireBuffer in IndentBufferConsistencyCop().  ","package":"IndentConsistencyCop.vim","4":"IndentConsistencyCop.vim","src_id":"8995","5":"8995","creation_date":"1216703061","6":"1216703061"},{"0":"1690","vim_version":"7.0","1":"7.0","script_version":"1.20.016","2":"1.20.016","version_comment":"ENH: Added b:indentconsistencycop_result buffer-scoped dictionary containing the results of the check, which can be used by other integrations. \r\nAlso check consistency of buffer settings if the buffer\/range does not contain indented text. Inconsistent indent settings can then be corrected with a queried setting. \r\nBF: Clear previous highlighting if buffer\/range now does not contain indented text. ","3":"ENH: Added b:indentconsistencycop_result buffer-scoped dictionary containing the results of the check, which can be used by other integrations. \r\nAlso check consistency of buffer settings if the buffer\/range does not contain indented text. Inconsistent indent settings can then be corrected with a queried setting. \r\nBF: Clear previous highlighting if buffer\/range now does not contain indented text. ","package":"IndentConsistencyCop.vim","4":"IndentConsistencyCop.vim","src_id":"8982","5":"8982","creation_date":"1216609488","6":"1216609488"},{"0":"1690","vim_version":"7.0","1":"7.0","script_version":"1.10.012","2":"1.10.012","version_comment":"Minor change: Added -bar to all commands that do not take any arguments, so that these can be chained together. ","3":"Minor change: Added -bar to all commands that do not take any arguments, so that these can be chained together. ","package":"IndentConsistencyCop.vim","4":"IndentConsistencyCop.vim","src_id":"8841","5":"8841","creation_date":"1214199937","6":"1214199937"},{"0":"1690","vim_version":"7.0","1":"7.0","script_version":"1.10.011","2":"1.10.011","version_comment":"Improved the algorithm so that 'softtabstop' is recognized even when a file only has small indents with either (up to 7) spaces or tabs, but no tab + space combination. ","3":"Improved the algorithm so that 'softtabstop' is recognized even when a file only has small indents with either (up to 7) spaces or tabs, but no tab + space combination. ","package":"IndentConsistencyCop.vim","4":"IndentConsistencyCop.vim","src_id":"8359","5":"8359","creation_date":"1204188709","6":"1204188709"},{"0":"1690","vim_version":"7.0","1":"7.0","script_version":"1.00.010","2":"1.00.010","version_comment":"BF: In an inconsistent and large buffer\/range that has only one or a few small inconsistencies and one dominant (i.e. 99%) setting, the text \"Some minor \/ inconclusive potential settings have been omitted.\" is not printed. \r\nENH: Print \"noexpandtab\/expandtab\" instead of \" expandtab to 0\/1\", as the user would :setlocal the setting. ","3":"BF: In an inconsistent and large buffer\/range that has only one or a few small inconsistencies and one dominant (i.e. 99%) setting, the text \"Some minor \/ inconclusive potential settings have been omitted.\" is not printed. \r\nENH: Print \"noexpandtab\/expandtab\" instead of \" expandtab to 0\/1\", as the user would :setlocal the setting. ","package":"IndentConsistencyCop.vim","4":"IndentConsistencyCop.vim","src_id":"7898","5":"7898","creation_date":"1194491424","6":"1194491424"},{"0":"1690","vim_version":"7.0","1":"7.0","script_version":"1.00.009","2":"1.00.009","version_comment":"ENH: Improved detection accuracy for soft tabstops when the maximum indent is too small for a solid assessment. When the maximum indent of the buffer is not enough to be sure of the indent settings (i.e. differentiating between soft tabstops and spaces), an inconsistent indent was reported, even though it is much more likely that the indent is consistent with \"soft tabstop n\", but that wasn't recognized because of the small indents used in the file. If allowed, the cop now examines the buffer settings to possibly turn around the verdict of \"inconsistent indent\". ","3":"ENH: Improved detection accuracy for soft tabstops when the maximum indent is too small for a solid assessment. When the maximum indent of the buffer is not enough to be sure of the indent settings (i.e. differentiating between soft tabstops and spaces), an inconsistent indent was reported, even though it is much more likely that the indent is consistent with \"soft tabstop n\", but that wasn't recognized because of the small indents used in the file. If allowed, the cop now examines the buffer settings to possibly turn around the verdict of \"inconsistent indent\". ","package":"IndentConsistencyCop.vim","4":"IndentConsistencyCop.vim","src_id":"7199","5":"7199","creation_date":"1180941892","6":"1180941892"},{"0":"1690","vim_version":"7.0","1":"7.0","script_version":"1.00.008","2":"1.00.008","version_comment":"Allowing user to override wrongly found consistent setting (e.g. 'sts1' instead of 'tab') by choosing 'Wrong, choose correct setting...' in the IndentBufferConsistencyCop. ","3":"Allowing user to override wrongly found consistent setting (e.g. 'sts1' instead of 'tab') by choosing 'Wrong, choose correct setting...' in the IndentBufferConsistencyCop. ","package":"IndentConsistencyCop.vim","4":"IndentConsistencyCop.vim","src_id":"6933","5":"6933","creation_date":"1175478977","6":"1175478977"},{"0":"1690","vim_version":"7.0","1":"7.0","script_version":"0.07","2":"0.07","version_comment":"Corrected unreasonable assumption of a consistent small indent setting (of 1 or 2 spaces) when actually only some wrong spaces spoil the consistency. Now, a perfect consistent rating is only accepted if its absolute rating number is also the maximum rating. \r\nBF: Avoiding runtime error in IndentBufferInconsistencyCop() if s:ratings is empty. \r\nBF: Suppressing 'Not buffer setting' option if the buffer setting is inconsistent ('badset'), which threw an exception when selected. ","3":"Corrected unreasonable assumption of a consistent small indent setting (of 1 or 2 spaces) when actually only some wrong spaces spoil the consistency. Now, a perfect consistent rating is only accepted if its absolute rating number is also the maximum rating. \r\nBF: Avoiding runtime error in IndentBufferInconsistencyCop() if s:ratings is empty. \r\nBF: Suppressing 'Not buffer setting' option if the buffer setting is inconsistent ('badset'), which threw an exception when selected. ","package":"IndentConsistencyCop.vim","4":"IndentConsistencyCop.vim","src_id":"6370","5":"6370","creation_date":"1162509266","6":"1162509266"},{"0":"1690","vim_version":"7.0","1":"7.0","script_version":"0.05","2":"0.05","version_comment":"Improved g:indentconsistencycop_non_indent_pattern to also allow ' *\\t' and ' *****' comments. ","3":"Improved g:indentconsistencycop_non_indent_pattern to also allow ' *\\t' and ' *****' comments. ","package":"IndentConsistencyCop.vim","4":"IndentConsistencyCop.vim","src_id":"6353","5":"6353","creation_date":"1162252569","6":"1162252569"},{"0":"1690","vim_version":"7.0","1":"7.0","script_version":"0.04","2":"0.04","version_comment":"Initial upload","3":"Initial upload","package":"IndentConsistencyCop.vim","4":"IndentConsistencyCop.vim","src_id":"6329","5":"6329","creation_date":"1161659917","6":"1161659917"}]},"1689":{"script_id":"1689","0":"1689","script_name":"mail_indenter","1":"mail_indenter","script_type":"utility","2":"utility","summary":"pretty indentation for e-mail replying","3":"pretty indentation for e-mail replying","description":"This tiny script (my first one) can convert this:\r\n\r\nOn 2006\/10\/23@16:47, <Mauro, Sauco> wrote:\r\n  > This is a post with a very long text without wrapping of text that can go on and on forever and its very annoying because it will make the reply almost impossible to understand.\r\n  > This is another very long line that looks very ugly because some e-mail clients will wrap it automatically but will not consider the indentation mark.\r\n  > I love inline replaying because:   \r\n  > 1. Inline posting creates a natural, chronological ordering to each segment of the discussion stored within a message.\r\n  > 2. Inline posting promotes the practice of trimming quoted text to prevent signature blocks, free-mail-service ads, and corporate disclaimers piling up in a growing useless \"tail\" at the end.\r\n  > 3. nline posting doesn't require the poster to recap each issue being addressed, as comments can be made point-for-point against the original message, making for a more structured, disciplined and unambiguous reply.\r\n\r\nInto this:\r\n\r\nOn 2006\/10\/23@16:47, <Mauro, Sauco> wrote:\r\n  Mauro> This is a post with a very long text without wrapping of text   \r\n  Mauro> that can go on and on forever and its very annoying because it\r\n  Mauro> will make the replay almost impossible to understand.  This is\r\n\r\nThen you can replay inline like this.\r\n   \r\n  Mauro> another very long line that looks very ugly because some e-mail   \r\n  Mauro> clients will wrap it automatically but will not consider the\r\n  Mauro> indentation mark.  I love inline replaying because: 1. Inline\r\n\r\nOr like this.\r\n\r\n  Mauro> posting creates a natural, chronological ordering to each   \r\n  Mauro> segment of the discussion stored within a message.  2. Inline\r\n  Mauro> posting promotes the practice of trimming quoted text to   \r\n  Mauro> prevent signature blocks, free-mail-service ads, and corporate\r\n  Mauro> disclaimers piling up in a growing useless \"tail\" at the end.\r\n\r\nI agree !\r\n\r\n  Mauro> 3. nline posting doesn't require the poster to recap each issue\r\n  Mauro> being addressed, as comments can be made point-for-point\r\n  Mauro> against the original message, making for a more structured,\r\n  Mauro> disciplined and unambiguous reply.\r\n\r\nIn case you didn't notice, the text is now wrapped at 72 and indented with the recipients name.\r\nHow you like it ?\r\n\r\nPlese feel free to drop me an e-mail with questions, suggestions, etc.\r\n\r\nRead the header of the script for keybidings.","4":"This tiny script (my first one) can convert this:\r\n\r\nOn 2006\/10\/23@16:47, <Mauro, Sauco> wrote:\r\n  > This is a post with a very long text without wrapping of text that can go on and on forever and its very annoying because it will make the reply almost impossible to understand.\r\n  > This is another very long line that looks very ugly because some e-mail clients will wrap it automatically but will not consider the indentation mark.\r\n  > I love inline replaying because:   \r\n  > 1. Inline posting creates a natural, chronological ordering to each segment of the discussion stored within a message.\r\n  > 2. Inline posting promotes the practice of trimming quoted text to prevent signature blocks, free-mail-service ads, and corporate disclaimers piling up in a growing useless \"tail\" at the end.\r\n  > 3. nline posting doesn't require the poster to recap each issue being addressed, as comments can be made point-for-point against the original message, making for a more structured, disciplined and unambiguous reply.\r\n\r\nInto this:\r\n\r\nOn 2006\/10\/23@16:47, <Mauro, Sauco> wrote:\r\n  Mauro> This is a post with a very long text without wrapping of text   \r\n  Mauro> that can go on and on forever and its very annoying because it\r\n  Mauro> will make the replay almost impossible to understand.  This is\r\n\r\nThen you can replay inline like this.\r\n   \r\n  Mauro> another very long line that looks very ugly because some e-mail   \r\n  Mauro> clients will wrap it automatically but will not consider the\r\n  Mauro> indentation mark.  I love inline replaying because: 1. Inline\r\n\r\nOr like this.\r\n\r\n  Mauro> posting creates a natural, chronological ordering to each   \r\n  Mauro> segment of the discussion stored within a message.  2. Inline\r\n  Mauro> posting promotes the practice of trimming quoted text to   \r\n  Mauro> prevent signature blocks, free-mail-service ads, and corporate\r\n  Mauro> disclaimers piling up in a growing useless \"tail\" at the end.\r\n\r\nI agree !\r\n\r\n  Mauro> 3. nline posting doesn't require the poster to recap each issue\r\n  Mauro> being addressed, as comments can be made point-for-point\r\n  Mauro> against the original message, making for a more structured,\r\n  Mauro> disciplined and unambiguous reply.\r\n\r\nIn case you didn't notice, the text is now wrapped at 72 and indented with the recipients name.\r\nHow you like it ?\r\n\r\nPlese feel free to drop me an e-mail with questions, suggestions, etc.\r\n\r\nRead the header of the script for keybidings.","install_details":"You can source it  like this:\r\n      vim -c 'source mail_indenter.vim'\r\nOr within Vim like this:\r\n     :source mail_indenter.vim\r\nIn .muttrc like this:\r\n    set editor=\"vim -f +8 -c 'source  mail_indenter.vim' \"\r\nOr copy it to ~\/.vim\/plugin\/\r\n\r\n     ","5":"You can source it  like this:\r\n      vim -c 'source mail_indenter.vim'\r\nOr within Vim like this:\r\n     :source mail_indenter.vim\r\nIn .muttrc like this:\r\n    set editor=\"vim -f +8 -c 'source  mail_indenter.vim' \"\r\nOr copy it to ~\/.vim\/plugin\/\r\n\r\n     ","first_name":"Mauro","6":"Mauro","last_name":"Sauco","7":"Sauco","releases":[{"0":"1689","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"mail_indenter.vim","4":"mail_indenter.vim","src_id":"6327","5":"6327","creation_date":"1161632062","6":"1161632062"}]},"1688":{"script_id":"1688","0":"1688","script_name":"MakeInBuilddir","1":"MakeInBuilddir","script_type":"utility","2":"utility","summary":"runs :make for projects where build and source directories are separated","3":"runs :make for projects where build and source directories are separated","description":"Let's consider a libtool\/autoconf project where source and build directories are separeted:\r\n  source_dir\r\n  source_dir\/build\r\n\r\nIf you're editing a file in source_dir\/src and type Make then\r\n  1\/ the name of the build directory will be asked (here 'build') (it is asked only once)\r\n  2\/ :make will be run in source_dir\/build\/src\r\n\r\nsource_dir is found by searching for configure.ac, configure.in or configure\r\n\r\nThe following additional commands are defined:\r\n   Compile - compiles the current file by calling the libtool-specific\r\n           :make basename.lo\r\n   MakeAll - runs :make in source_dir regardless of the directory of the current file\r\n   Reconfigure - runs \"config.status --recheck\" in source_dir\/build\r\n   RegenAll - runs \"config.status\" in source_dir\/build\r\n   Run execname - starts execname instead of :make\r\n   Debug execname - start a libtool-wrapped gdb (for libtool generated executables)\r\n","4":"Let's consider a libtool\/autoconf project where source and build directories are separeted:\r\n  source_dir\r\n  source_dir\/build\r\n\r\nIf you're editing a file in source_dir\/src and type Make then\r\n  1\/ the name of the build directory will be asked (here 'build') (it is asked only once)\r\n  2\/ :make will be run in source_dir\/build\/src\r\n\r\nsource_dir is found by searching for configure.ac, configure.in or configure\r\n\r\nThe following additional commands are defined:\r\n   Compile - compiles the current file by calling the libtool-specific\r\n           :make basename.lo\r\n   MakeAll - runs :make in source_dir regardless of the directory of the current file\r\n   Reconfigure - runs \"config.status --recheck\" in source_dir\/build\r\n   RegenAll - runs \"config.status\" in source_dir\/build\r\n   Run execname - starts execname instead of :make\r\n   Debug execname - start a libtool-wrapped gdb (for libtool generated executables)\r\n","install_details":"copy makeinbuilddir.vim in .vim\/plugin","5":"copy makeinbuilddir.vim in .vim\/plugin","first_name":"Sylvain","6":"Sylvain","last_name":"Joyeux","7":"Joyeux","releases":[{"0":"1688","vim_version":"7.0","1":"7.0","script_version":"0.3","2":"0.3","version_comment":"Added completion for -C in :Make","3":"Added completion for -C in :Make","package":"makeinbuilddir.vim","4":"makeinbuilddir.vim","src_id":"6335","5":"6335","creation_date":"1161826378","6":"1161826378"},{"0":"1688","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"makeinbuilddir.vim","4":"makeinbuilddir.vim","src_id":"6325","5":"6325","creation_date":"1161609147","6":"1161609147"}]},"1687":{"script_id":"1687","0":"1687","script_name":"jdox","1":"jdox","script_type":"utility","2":"utility","summary":"generates javadoc compatibile comments for c++ function definitions","3":"generates javadoc compatibile comments for c++ function definitions","description":"JDOX is a vim plugin that generates javadoc compatibile comment for c++ function definitions. The main point that differs jdox from similar commenting plugins is that jdox supports comments between arguments, function name and return types.\r\nExample:\r\n\/**\r\n * Function: a_function\r\n * @author Pawel Prokop\r\n * @param str \r\n * @param number \r\n * @return unsigned  int\r\n * @version 1.0\r\n *\/\r\nunsigned \r\nint  a_function  ( char * str, \/* int not_used_anymore, *\/ unsigned int number) {\r\n\r\n","4":"JDOX is a vim plugin that generates javadoc compatibile comment for c++ function definitions. The main point that differs jdox from similar commenting plugins is that jdox supports comments between arguments, function name and return types.\r\nExample:\r\n\/**\r\n * Function: a_function\r\n * @author Pawel Prokop\r\n * @param str \r\n * @param number \r\n * @return unsigned  int\r\n * @version 1.0\r\n *\/\r\nunsigned \r\nint  a_function  ( char * str, \/* int not_used_anymore, *\/ unsigned int number) {\r\n\r\n","install_details":"copy jdox_cpp.vim into .vim\/plugin directory.\r\nUsage: when cursor is on function name press \\d (backslash d)","5":"copy jdox_cpp.vim into .vim\/plugin directory.\r\nUsage: when cursor is on function name press \\d (backslash d)","first_name":"Pawel","6":"Pawel","last_name":"Prokop","7":"Prokop","releases":[{"0":"1687","vim_version":"7.0","1":"7.0","script_version":"1.00pre1","2":"1.00pre1","version_comment":"Initial upload","3":"Initial upload","package":"jdox_cpp.vim","4":"jdox_cpp.vim","src_id":"6315","5":"6315","creation_date":"1161478731","6":"1161478731"}]},"1686":{"script_id":"1686","0":"1686","script_name":"Tango colour scheme","1":"Tango colour scheme","script_type":"color scheme","2":"color scheme","summary":"Colour scheme using the Tango Desktop project palette","3":"Colour scheme using the Tango Desktop project palette","description":"Colour scheme using the Tango Desktop project palette. Works both in GUI and terminal.\r\n\r\nScreenshot and comments: http:\/\/blog.micampe.it\/articles\/2006\/10\/20\/vim-tango-color-scheme\r\nInspired by the Tango palette for the GNOME terminal: http:\/\/uwstopia.nl\/blog\/2006\/07\/tango-terminal\r\nWhat is Tango: http:\/\/tango.freedesktop.org","4":"Colour scheme using the Tango Desktop project palette. Works both in GUI and terminal.\r\n\r\nScreenshot and comments: http:\/\/blog.micampe.it\/articles\/2006\/10\/20\/vim-tango-color-scheme\r\nInspired by the Tango palette for the GNOME terminal: http:\/\/uwstopia.nl\/blog\/2006\/07\/tango-terminal\r\nWhat is Tango: http:\/\/tango.freedesktop.org","install_details":"","5":"","first_name":"Michele","6":"Michele","last_name":"Campeotto","7":"Campeotto","releases":[{"0":"1686","vim_version":"6.0","1":"6.0","script_version":"1.1","2":"1.1","version_comment":"fixes to diff mode","3":"fixes to diff mode","package":"tango.vim","4":"tango.vim","src_id":"6361","5":"6361","creation_date":"1162377297","6":"1162377297"},{"0":"1686","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"tango.vim","4":"tango.vim","src_id":"6310","5":"6310","creation_date":"1161362463","6":"1161362463"}]},"1685":{"script_id":"1685","0":"1685","script_name":"plaintex.vim","1":"plaintex.vim","script_type":"ftplugin","2":"ftplugin","summary":"Support files for editing plain TeX documents","3":"Support files for editing plain TeX documents","description":"ftplugin\/plaintex.vim\r\ncompiler\/plaintex.vim\r\ndoc\/ft-plaintex.txt\r\n\r\nThis package provides a compiler plugin and a filetype plugin for editing plain TeX documents ('ft' = plaintex).  It is intended to be used in addition to the default ftplugin for plaintex, which I also maintain.\r\n\r\nThe compiler plugin enables you to run tex (or pdftex) on your file with\r\n  :make\r\nand then correct errors using quickfix mode.\r\n\r\nThe filetype plugin maps \" (double quote mark) to insert `` (open quotes) at the start of a quotation, then '' (close quotes) at the end.  It also maps <C-B> to insert \"{\\bf }\" and <C-T> to insert \"{\\it \\\/}\".  Both of these keys work in Normal, Insert, and Visual modes.","4":"ftplugin\/plaintex.vim\r\ncompiler\/plaintex.vim\r\ndoc\/ft-plaintex.txt\r\n\r\nThis package provides a compiler plugin and a filetype plugin for editing plain TeX documents ('ft' = plaintex).  It is intended to be used in addition to the default ftplugin for plaintex, which I also maintain.\r\n\r\nThe compiler plugin enables you to run tex (or pdftex) on your file with\r\n  :make\r\nand then correct errors using quickfix mode.\r\n\r\nThe filetype plugin maps \" (double quote mark) to insert `` (open quotes) at the start of a quotation, then '' (close quotes) at the end.  It also maps <C-B> to insert \"{\\bf }\" and <C-T> to insert \"{\\it \\\/}\".  Both of these keys work in Normal, Insert, and Visual modes.","install_details":"Copy the zip archive to your vim directory (e.g., ~\/.vim on *NIX) and\r\n  $unzip plaintex.zip\r\nto unpack the three files.  From within vim, use\r\n  :helptags ~\/.vim\/doc\r\n(or whatever other directory you use) to install the help file.\r\n\r\nConfiguration:  There is a section of the ftplugin file that you can edit to change the key mappings and the menu location.  If you have already edited this section, then write it out to a separate file, plaintex.vimrc, in the ftplugin directory before you install a new version.","5":"Copy the zip archive to your vim directory (e.g., ~\/.vim on *NIX) and\r\n  $unzip plaintex.zip\r\nto unpack the three files.  From within vim, use\r\n  :helptags ~\/.vim\/doc\r\n(or whatever other directory you use) to install the help file.\r\n\r\nConfiguration:  There is a section of the ftplugin file that you can edit to change the key mappings and the menu location.  If you have already edited this section, then write it out to a separate file, plaintex.vimrc, in the ftplugin directory before you install a new version.","first_name":"Benji","6":"Benji","last_name":"Fisher","7":"Fisher","releases":[{"0":"1685","vim_version":"7.0","1":"7.0","script_version":"0.2","2":"0.2","version_comment":"I added a menu.  This way, you can see what keys have been mapped without having to RTFM.","3":"I added a menu.  This way, you can see what keys have been mapped without having to RTFM.","package":"plaintex.zip","4":"plaintex.zip","src_id":"6382","5":"6382","creation_date":"1162804343","6":"1162804343"},{"0":"1685","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"plaintex.zip","4":"plaintex.zip","src_id":"6308","5":"6308","creation_date":"1161343085","6":"1161343085"}]},"1684":{"script_id":"1684","0":"1684","script_name":"DNA sequence highlighter","1":"DNA sequence highlighter","script_type":"syntax","2":"syntax","summary":"Highlight DNA and RNA sequences","3":"Highlight DNA and RNA sequences","description":"Highlight DNA and RNA sequences in a manner similar to most sequence-editing software, e.g., Sequencher, TreeView, MEGA etc.","4":"Highlight DNA and RNA sequences in a manner similar to most sequence-editing software, e.g., Sequencher, TreeView, MEGA etc.","install_details":"","5":"","first_name":"Alexey","6":"Alexey","last_name":"Shipunov","7":"Shipunov","releases":[{"0":"1684","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"dna.vim","4":"dna.vim","src_id":"6307","5":"6307","creation_date":"1161342818","6":"1161342818"}]},"1683":{"script_id":"1683","0":"1683","script_name":"Darcs","1":"Darcs","script_type":"utility","2":"utility","summary":"basic Darcs support for vim","3":"basic Darcs support for vim","description":"Defines the following commands:\r\n  DarcsDiff shows the diff between the file in the current buffer and the Darcs version of that file\r\n  DarcsOff closes the diff view opened by DarcsDiff\r\n  DarcsChanges shows the changes to the file in the current buffer. ","4":"Defines the following commands:\r\n  DarcsDiff shows the diff between the file in the current buffer and the Darcs version of that file\r\n  DarcsOff closes the diff view opened by DarcsDiff\r\n  DarcsChanges shows the changes to the file in the current buffer. ","install_details":"copy darcs.vim into your .vim\/plugin directory","5":"copy darcs.vim into your .vim\/plugin directory","first_name":"Sylvain","6":"Sylvain","last_name":"Joyeux","7":"Joyeux","releases":[{"0":"1683","vim_version":"7.0","1":"7.0","script_version":"0.2.1","2":"0.2.1","version_comment":"added credits\/description\/... comments in top of file","3":"added credits\/description\/... comments in top of file","package":"darcs.vim","4":"darcs.vim","src_id":"6324","5":"6324","creation_date":"1161608295","6":"1161608295"},{"0":"1683","vim_version":"7.0","1":"7.0","script_version":"0.2","2":"0.2","version_comment":"add the s:FindDir function that was missing in 0.1","3":"add the s:FindDir function that was missing in 0.1","package":"darcs.vim","4":"darcs.vim","src_id":"6323","5":"6323","creation_date":"1161608091","6":"1161608091"}]},"1682":{"script_id":"1682","0":"1682","script_name":"IndexedSearch","1":"IndexedSearch","script_type":"utility","2":"utility","summary":"shows  'Nth match out of M'  at every search (index of match+total # matches)","3":"shows  'Nth match out of M'  at every search (index of match+total # matches)","description":"\" This plugin redefines 6 search commands (\/,?,n,N,*,#). At every\r\n\" search command, it automatically prints\r\n\"        \"At match #N out of M matches\".\r\n\" -- the total number of matches (M) and the number(index) of current\r\n\" match (N). This helps to get oriented when searching forward and\r\n\" backward.\r\n\"\r\n\" To try out the plugin, source it and play with N,n,*,#,\/,? commands.\r\n\" There are no new commands and no new behavior to learn. \r\n\" Just watch the bottom line when you do \/,?,n,N,*,#.\r\n\"\r\n\" Works on vim6 and vim7.  Won't cause slowdown\r\n\" on very large files (but then counters are not displayed).\r\n\"\r\n\" -----------------------------------------------------\r\n\" Checking At which Match Number You Are\r\n\" .....................................................\r\n\" You can press g\/ or \\\\ or \\\/ (that's backslach then slash),to show \r\n\" at which match index you are, without moving the cursor.\r\n\" Messages are:\r\n\"     At Nth match of M (if cursor is exactly on the match)\r\n\"     Betwen matches N1-N2 of M (if cursor is between matches)\r\n\"     At single match\r\n\"     Before first match, of N\r\n\"     After last match, of N\r\n\" Command  ':ShowSearchIndex'  shows same information.\r\n\" ------------------------------------------------------\r\n\" To disable colors for messages, set 'let g:indexed_search_colors=0'.\r\n\" ------------------------------------------------------\r\n\" Performance.     Plugin bypasses the calculation of match index when \r\n\" it would take too much time (too many matches, too large file). You can\r\n\" tune performance limits, look into script sources after comment \r\n\" \"Performance tuning limits\".\r\n\" ------------------------------------------------------\r\n\" In case of bugs and wishes, please email to:  \r\n\" iler.ml at gmail.com\r\n\" ------------------------------------------------------\r\n\" To show slightly shorter messages, define 'let g:indexed_search_shortmess=1'\r\n","4":"\" This plugin redefines 6 search commands (\/,?,n,N,*,#). At every\r\n\" search command, it automatically prints\r\n\"        \"At match #N out of M matches\".\r\n\" -- the total number of matches (M) and the number(index) of current\r\n\" match (N). This helps to get oriented when searching forward and\r\n\" backward.\r\n\"\r\n\" To try out the plugin, source it and play with N,n,*,#,\/,? commands.\r\n\" There are no new commands and no new behavior to learn. \r\n\" Just watch the bottom line when you do \/,?,n,N,*,#.\r\n\"\r\n\" Works on vim6 and vim7.  Won't cause slowdown\r\n\" on very large files (but then counters are not displayed).\r\n\"\r\n\" -----------------------------------------------------\r\n\" Checking At which Match Number You Are\r\n\" .....................................................\r\n\" You can press g\/ or \\\\ or \\\/ (that's backslach then slash),to show \r\n\" at which match index you are, without moving the cursor.\r\n\" Messages are:\r\n\"     At Nth match of M (if cursor is exactly on the match)\r\n\"     Betwen matches N1-N2 of M (if cursor is between matches)\r\n\"     At single match\r\n\"     Before first match, of N\r\n\"     After last match, of N\r\n\" Command  ':ShowSearchIndex'  shows same information.\r\n\" ------------------------------------------------------\r\n\" To disable colors for messages, set 'let g:indexed_search_colors=0'.\r\n\" ------------------------------------------------------\r\n\" Performance.     Plugin bypasses the calculation of match index when \r\n\" it would take too much time (too many matches, too large file). You can\r\n\" tune performance limits, look into script sources after comment \r\n\" \"Performance tuning limits\".\r\n\" ------------------------------------------------------\r\n\" In case of bugs and wishes, please email to:  \r\n\" iler.ml at gmail.com\r\n\" ------------------------------------------------------\r\n\" To show slightly shorter messages, define 'let g:indexed_search_shortmess=1'\r\n","install_details":"Short instructions: drop script into your personal plugin directory (~\/.vim\/plugin).\r\n\r\nDetailed instructions:\r\n1. Download script IndexedSearch.vim from the link below.\r\n2. Create directory ~\/.vim\/plugin if it does not exist:\r\n                 mkdir -p ~\/.vim\/plugin\r\n   (your personal plugin directory).\r\n3. Copy script IndexedSearch.vim into ~\/.vim\/plugin directory.\r\n4. Restart vim\r\n","5":"Short instructions: drop script into your personal plugin directory (~\/.vim\/plugin).\r\n\r\nDetailed instructions:\r\n1. Download script IndexedSearch.vim from the link below.\r\n2. Create directory ~\/.vim\/plugin if it does not exist:\r\n                 mkdir -p ~\/.vim\/plugin\r\n   (your personal plugin directory).\r\n3. Copy script IndexedSearch.vim into ~\/.vim\/plugin directory.\r\n4. Restart vim\r\n","first_name":"Yakov","6":"Yakov","last_name":"Lerner","7":"Lerner","releases":[{"0":"1682","vim_version":"6.0","1":"6.0","script_version":"070503","2":"070503","version_comment":"Fixed problem with 'smartcase'. Checksum 726910263","3":"Fixed problem with 'smartcase'. Checksum 726910263","package":"IndexedSearch.vim","4":"IndexedSearch.vim","src_id":"7062","5":"7062","creation_date":"1178185145","6":"1178185145"}]},"1681":{"script_id":"1681","0":"1681","script_name":"ekvoli","1":"ekvoli","script_type":"color scheme","2":"color scheme","summary":"Different shades of blue (colour scheme)","3":"Different shades of blue (colour scheme)","description":"A colour scheme with different shades of blue.\r\n\r\nScreenshots can be seen here: http:\/\/www.pvv.org\/~randhol\/Vim\/ekvoli\/\r\n\r\nHope you like it. ","4":"A colour scheme with different shades of blue.\r\n\r\nScreenshots can be seen here: http:\/\/www.pvv.org\/~randhol\/Vim\/ekvoli\/\r\n\r\nHope you like it. ","install_details":"Just copy the ekvoli.vim file into your \"$HOME\/.vim\/colors\/\" or \"$VIMRUNTIME\/colors\/\" (Windows)  then use \r\n:colorscheme ekvoli","5":"Just copy the ekvoli.vim file into your \"$HOME\/.vim\/colors\/\" or \"$VIMRUNTIME\/colors\/\" (Windows)  then use \r\n:colorscheme ekvoli","first_name":"Preben","6":"Preben","last_name":"Randhol","7":"Randhol","releases":[{"0":"1681","vim_version":"6.0","1":"6.0","script_version":"1.6","2":"1.6","version_comment":"Added colours for TVO: The Vim Outliner  (script_id=517)\r\nChange the folding colours and slightly the statusbar.","3":"Added colours for TVO: The Vim Outliner  (script_id=517)\r\nChange the folding colours and slightly the statusbar.","package":"ekvoli.vim","4":"ekvoli.vim","src_id":"8342","5":"8342","creation_date":"1203851692","6":"1203851692"},{"0":"1681","vim_version":"6.0","1":"6.0","script_version":"1.5","2":"1.5","version_comment":"Fixed background colour and purified the colour scheme some.","3":"Fixed background colour and purified the colour scheme some.","package":"ekvoli.vim","4":"ekvoli.vim","src_id":"7693","5":"7693","creation_date":"1190181998","6":"1190181998"},{"0":"1681","vim_version":"6.0","1":"6.0","script_version":"1.1","2":"1.1","version_comment":"Fixed the colorscheme so that it works with Vim 6.0 and up. Thanks to Niels Heirbaut for help with this.","3":"Fixed the colorscheme so that it works with Vim 6.0 and up. Thanks to Niels Heirbaut for help with this.","package":"ekvoli.vim","4":"ekvoli.vim","src_id":"6313","5":"6313","creation_date":"1161392977","6":"1161392977"},{"0":"1681","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"ekvoli.vim","4":"ekvoli.vim","src_id":"6291","5":"6291","creation_date":"1161076584","6":"1161076584"}]},"1680":{"script_id":"1680","0":"1680","script_name":"Vexorian color scheme","1":"Vexorian color scheme","script_type":"color scheme","2":"color scheme","summary":"initial release","3":"initial release","description":"It uses the highlight setup I personally prefer for programming, white background, green for comments, a different color for constants, italic for strings, gray for preprocessors and bold black for keywords.","4":"It uses the highlight setup I personally prefer for programming, white background, green for comments, a different color for constants, italic for strings, gray for preprocessors and bold black for keywords.","install_details":"Like any other color scheme file","5":"Like any other color scheme file","first_name":"Victor Hugo","6":"Victor Hugo","last_name":"Soliz Kuncar","7":"Soliz Kuncar","releases":[{"0":"1680","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"vexorian.vim","4":"vexorian.vim","src_id":"6290","5":"6290","creation_date":"1161029518","6":"1161029518"}]},"1679":{"script_id":"1679","0":"1679","script_name":"tidy compiler script","1":"tidy compiler script","script_type":"utility","2":"utility","summary":"compiler script for tidy","3":"compiler script for tidy","description":"Tydi is a useful tool for fixing and indenting html files, see http:\/\/tidy.sourceforge.net\/, and this zip contains a compiler script.\r\n","4":"Tydi is a useful tool for fixing and indenting html files, see http:\/\/tidy.sourceforge.net\/, and this zip contains a compiler script.\r\n","install_details":"The \\'tidy.zip\\' contains the compiler script file (\\'tydi.vim\\'), which should placed into the compiler directory in the vimfiles dir. The content of the \\'include_into_vimrc\\' should be copied into the startup file (_vimrc). F12 button starts the tidy application from vim.","5":"The \\'tidy.zip\\' contains the compiler script file (\\'tydi.vim\\'), which should placed into the compiler directory in the vimfiles dir. The content of the \\'include_into_vimrc\\' should be copied into the startup file (_vimrc). F12 button starts the tidy application from vim.","first_name":"Gergely","6":"Gergely","last_name":"Szentesi","7":"Szentesi","releases":[{"0":"1679","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"tidy.zip","4":"tidy.zip","src_id":"6287","5":"6287","creation_date":"1160991767","6":"1160991767"}]},"1678":{"script_id":"1678","0":"1678","script_name":"Tab Name","1":"Tab Name","script_type":"utility","2":"utility","summary":"Set name for your tab-pages.","3":"Set name for your tab-pages.","description":"Suppose you have tab pages with same buffer for edit but with different line positions. How are you going to find correct tab page? \r\nWhat about tabpages with splitted windows?\r\n\r\n:TName 'tab_page_name' - set name of tab-page\r\n:TNoName - remove tab page name","4":"Suppose you have tab pages with same buffer for edit but with different line positions. How are you going to find correct tab page? \r\nWhat about tabpages with splitted windows?\r\n\r\n:TName 'tab_page_name' - set name of tab-page\r\n:TNoName - remove tab page name","install_details":"put tabname.vim to your plugin folder","5":"put tabname.vim to your plugin folder","first_name":"Mykola","6":"Mykola","last_name":"Golubyev","7":"Golubyev","releases":[{"0":"1678","vim_version":"7.0","1":"7.0","script_version":"1","2":"1","version_comment":"Initial upload","3":"Initial upload","package":"tabname.vim","4":"tabname.vim","src_id":"6284","5":"6284","creation_date":"1160968165","6":"1160968165"}]},"1677":{"script_id":"1677","0":"1677","script_name":"twilight","1":"twilight","script_type":"color scheme","2":"color scheme","summary":"A clone of Textmates twilight scheme","3":"A clone of Textmates twilight scheme","description":"A dark scheme, with golden and blueish script.\r\nThis is just a first try, there may be lots of things missing or wrong.\r\n\r\nSee  http:\/\/leetless.de\/vim.html for a screenshot.","4":"A dark scheme, with golden and blueish script.\r\nThis is just a first try, there may be lots of things missing or wrong.\r\n\r\nSee  http:\/\/leetless.de\/vim.html for a screenshot.","install_details":"Put it into ~\/.vim\/colors, then :color twilight","5":"Put it into ~\/.vim\/colors, then :color twilight","first_name":"Henning","6":"Henning","last_name":"Hasemann","7":"Hasemann","releases":[{"0":"1677","vim_version":"6.0","1":"6.0","script_version":"0.3","2":"0.3","version_comment":"Rewrite, changed the whole color feeling according to some screenshots of the original I found.","3":"Rewrite, changed the whole color feeling according to some screenshots of the original I found.","package":"twilight.vim","4":"twilight.vim","src_id":"10496","5":"10496","creation_date":"1241083578","6":"1241083578"},{"0":"1677","vim_version":"6.0","1":"6.0","script_version":"0.2","2":"0.2","version_comment":"Some color adjustments, support some more highlighting groups","3":"Some color adjustments, support some more highlighting groups","package":"twilight.vim","4":"twilight.vim","src_id":"9773","5":"9773","creation_date":"1231430551","6":"1231430551"},{"0":"1677","vim_version":"7.0","1":"7.0","script_version":"0.1alpha","2":"0.1alpha","version_comment":"Initial upload","3":"Initial upload","package":"twilight.vim","4":"twilight.vim","src_id":"6281","5":"6281","creation_date":"1160784111","6":"1160784111"}]},"1676":{"script_id":"1676","0":"1676","script_name":"toggle_words.vim","1":"toggle_words.vim","script_type":"utility","2":"utility","summary":"toggle words like:'true'=>'false', 'True'=>'False' etc","3":"toggle words like:'true'=>'false', 'True'=>'False' etc","description":"\" Documentation: \r\n\"   The purpose of this plugin is very simple, it can toggle words among\r\n\"   'true'=>'false', 'True'=>'False', 'if'=>'elseif'=>'else'=>'endif' etc . \r\n\"\r\n\"   To use it, move the cursor on some words like 'true', 'False', 'YES', etc, \r\n\"   call command \r\n\"     :ToggleWord\r\n\"\r\n\"   It will toggle 'true'=>'false', 'False'=>'True', 'YES'=>'NO' etc. Yes,\r\n\"   this script will try to take the case into account when toggling words, so\r\n\"   'True' will be toggled to 'False' instead of 'false'. Currently the way to\r\n\"   check the case is very simple, but it works well for me.\r\n\"\r\n\"   You can define a map for 'ToggleWord' comand to make it easier: \r\n\"     nmap ,t :ToggleWord<CR>\r\n\"\r\n\"   This script can search the candicate words to toggle based on\r\n\"   current filetype, for example, you can put the following configuration\r\n\"   into your .vimrc to define some words for python:\r\n\"      let g:toggle_words_dict = {'python': [['if', 'elif', 'else']]}\r\n\"   \r\n\"   There are some default words for toggling predefined in the\r\n\"   script(g:_toogle_words_dict) that will work for all filetypes.\r\n\"   Any comment, suggestion, bug report are welcomed. \r\n","4":"\" Documentation: \r\n\"   The purpose of this plugin is very simple, it can toggle words among\r\n\"   'true'=>'false', 'True'=>'False', 'if'=>'elseif'=>'else'=>'endif' etc . \r\n\"\r\n\"   To use it, move the cursor on some words like 'true', 'False', 'YES', etc, \r\n\"   call command \r\n\"     :ToggleWord\r\n\"\r\n\"   It will toggle 'true'=>'false', 'False'=>'True', 'YES'=>'NO' etc. Yes,\r\n\"   this script will try to take the case into account when toggling words, so\r\n\"   'True' will be toggled to 'False' instead of 'false'. Currently the way to\r\n\"   check the case is very simple, but it works well for me.\r\n\"\r\n\"   You can define a map for 'ToggleWord' comand to make it easier: \r\n\"     nmap ,t :ToggleWord<CR>\r\n\"\r\n\"   This script can search the candicate words to toggle based on\r\n\"   current filetype, for example, you can put the following configuration\r\n\"   into your .vimrc to define some words for python:\r\n\"      let g:toggle_words_dict = {'python': [['if', 'elif', 'else']]}\r\n\"   \r\n\"   There are some default words for toggling predefined in the\r\n\"   script(g:_toogle_words_dict) that will work for all filetypes.\r\n\"   Any comment, suggestion, bug report are welcomed. \r\n","install_details":"just put this script into YOUR_HOME_DIR\/[._]vim\/plugin folder.","5":"just put this script into YOUR_HOME_DIR\/[._]vim\/plugin folder.","first_name":"Vincent","6":"Vincent","last_name":"Wang","7":"Wang","releases":[{"0":"1676","vim_version":"7.0","1":"7.0","script_version":"1.5","2":"1.5","version_comment":"add support to extend default toggle words ('*'), based on patch provided by Jeremy Cantrell, thanks","3":"add support to extend default toggle words ('*'), based on patch provided by Jeremy Cantrell, thanks","package":"toggle_words.vim","4":"toggle_words.vim","src_id":"10038","5":"10038","creation_date":"1235621975","6":"1235621975"},{"0":"1676","vim_version":"7.0","1":"7.0","script_version":"1.3","2":"1.3","version_comment":"* fix error of 'E488: Trailing characters', patch provided by Jeremy Cantrell\r\n","3":"* fix error of 'E488: Trailing characters', patch provided by Jeremy Cantrell\r\n","package":"toggle_words.vim","4":"toggle_words.vim","src_id":"8981","5":"8981","creation_date":"1216589218","6":"1216589218"},{"0":"1676","vim_version":"7.0","1":"7.0","script_version":"1.2","2":"1.2","version_comment":"* fixed typo(november => novermber)\r\n* sorted and stacked the definitions to make them more readable\/editable\r\n* added a few new definitions (allow\/deny, min\/max, before\/after, block\/inline\/none, left\/right)\r\n* add revision history \r\n(most of above changes come from Fergus Bremner, thanks Fergus!)\r\n","3":"* fixed typo(november => novermber)\r\n* sorted and stacked the definitions to make them more readable\/editable\r\n* added a few new definitions (allow\/deny, min\/max, before\/after, block\/inline\/none, left\/right)\r\n* add revision history \r\n(most of above changes come from Fergus Bremner, thanks Fergus!)\r\n","package":"toggle_words.vim","4":"toggle_words.vim","src_id":"8977","5":"8977","creation_date":"1216536534","6":"1216536534"},{"0":"1676","vim_version":"7.0","1":"7.0","script_version":"1.01","2":"1.01","version_comment":"Yes, this script will try to take the case into account when toggling words, so 'True' will be toggled to 'False' instead of 'false'. Currently the way to check the case is very simple, but it works well for me.","3":"Yes, this script will try to take the case into account when toggling words, so 'True' will be toggled to 'False' instead of 'false'. Currently the way to check the case is very simple, but it works well for me.","package":"toggle_words.vim","4":"toggle_words.vim","src_id":"7308","5":"7308","creation_date":"1183088058","6":"1183088058"},{"0":"1676","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"toggle_words.vim","4":"toggle_words.vim","src_id":"6271","5":"6271","creation_date":"1160674980","6":"1160674980"}]},"1675":{"script_id":"1675","0":"1675","script_name":"Drupal 5.0 function dictionary","1":"Drupal 5.0 function dictionary","script_type":"syntax","2":"syntax","summary":"Drupal 5.0 function name dictionary for Ctrl-X Ctrl-K completition","3":"Drupal 5.0 function name dictionary for Ctrl-X Ctrl-K completition","description":"This is just a dictionary for Drupal developers, to make their life a bit easier. If you add it to the dictionary list in vim, you can use the Ctrl-X Ctrl-K completition in INSERT mode.","4":"This is just a dictionary for Drupal developers, to make their life a bit easier. If you add it to the dictionary list in vim, you can use the Ctrl-X Ctrl-K completition in INSERT mode.","install_details":"1. Download the dict and place in ~\/.vim\/dictionaries\/\r\n2. Put this line into your .vimrc:\r\n    set dict+=~\/.vim\/dictionaries\/drupal50-functions.dict","5":"1. Download the dict and place in ~\/.vim\/dictionaries\/\r\n2. Put this line into your .vimrc:\r\n    set dict+=~\/.vim\/dictionaries\/drupal50-functions.dict","first_name":"P\u00c3\u00a9ntek","6":"P\u00c3\u00a9ntek","last_name":"G\u00c3\u00a1bor","7":"G\u00c3\u00a1bor","releases":[{"0":"1675","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Drupal 5.0 Core functions.","3":"Drupal 5.0 Core functions.","package":"Drupal5.0-core_functions.dict","4":"Drupal5.0-core_functions.dict","src_id":"6275","5":"6275","creation_date":"1160726519","6":"1160726519"}]},"1674":{"script_id":"1674","0":"1674","script_name":"pdf.vim","1":"pdf.vim","script_type":"syntax","2":"syntax","summary":"PDF Syntax Highlighting","3":"PDF Syntax Highlighting","description":"Syntax hightlighting for PDF files.  ","4":"Syntax hightlighting for PDF files.  ","install_details":"","5":"","first_name":"Mohit","6":"Mohit","last_name":"Kalra","7":"Kalra","releases":[{"0":"1674","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"pdf.vim","4":"pdf.vim","src_id":"6269","5":"6269","creation_date":"1160607197","6":"1160607197"}]},"1673":{"script_id":"1673","0":"1673","script_name":"blueprint.vim","1":"blueprint.vim","script_type":"color scheme","2":"color scheme","summary":"A color theme inspired by blueprint","3":"A color theme inspired by blueprint","description":"This is a color theme inspired by blueprint. It use not-so-dark blue background and not-so-bright white characters, trying to give user a clean, simple and easy to read interface, yet easy to identify different part of your masterpiece codes :)","4":"This is a color theme inspired by blueprint. It use not-so-dark blue background and not-so-bright white characters, trying to give user a clean, simple and easy to read interface, yet easy to identify different part of your masterpiece codes :)","install_details":"tested for GVIM only\r\n\r\ncp it to .vim\/colors\r\nand use \"colorscheme blueprint\" to switch to it, if you want to use it permanently, add \"colorscheme blueprint\" to your .vimrc file","5":"tested for GVIM only\r\n\r\ncp it to .vim\/colors\r\nand use \"colorscheme blueprint\" to switch to it, if you want to use it permanently, add \"colorscheme blueprint\" to your .vimrc file","first_name":"adam","6":"adam","last_name":"si","7":"si","releases":[{"0":"1673","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Fix comments.","3":"Fix comments.","package":"blueprint.vim","4":"blueprint.vim","src_id":"12749","5":"12749","creation_date":"1270003063","6":"1270003063"},{"0":"1673","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"blueprint.vim","4":"blueprint.vim","src_id":"6268","5":"6268","creation_date":"1160606158","6":"1160606158"}]},"1672":{"script_id":"1672","0":"1672","script_name":"darktango.vim","1":"darktango.vim","script_type":"color scheme","2":"color scheme","summary":"Tango based color scheme","3":"Tango based color scheme","description":"Based on the color specifications of www.tango-project.org.\r\n\r\nI've been using this color scheme, for a couple of weeks now. It's not complete but I really like it. For suggestions etc feel free to email me.\r\n\r\nDarkTango, fits great with Tango desktop themes and all that is Tango-ish!\r\n\r\nEnjoy!\r\n\r\nCouple of screenshots (0.3):\r\nhttp:\/\/flickr.com\/photos\/panosl\/2321828928\/in\/photostream\/","4":"Based on the color specifications of www.tango-project.org.\r\n\r\nI've been using this color scheme, for a couple of weeks now. It's not complete but I really like it. For suggestions etc feel free to email me.\r\n\r\nDarkTango, fits great with Tango desktop themes and all that is Tango-ish!\r\n\r\nEnjoy!\r\n\r\nCouple of screenshots (0.3):\r\nhttp:\/\/flickr.com\/photos\/panosl\/2321828928\/in\/photostream\/","install_details":"Drop it in  ~\/vim\/colors\/ directory or the windows equivalent and activate through :colorscheme darktango","5":"Drop it in  ~\/vim\/colors\/ directory or the windows equivalent and activate through :colorscheme darktango","first_name":"panos","6":"panos","last_name":"laganakos","7":"laganakos","releases":[{"0":"1672","vim_version":"7.0","1":"7.0","script_version":"0.3","2":"0.3","version_comment":"Various small fixes and cleanup,\r\nto bring up full tango support to the remaining objects.","3":"Various small fixes and cleanup,\r\nto bring up full tango support to the remaining objects.","package":"darktango.vim","4":"darktango.vim","src_id":"6293","5":"6293","creation_date":"1161146192","6":"1161146192"},{"0":"1672","vim_version":"7.0","1":"7.0","script_version":"0.2","2":"0.2","version_comment":"Got rid of all the unfitting pure black (#000000) objects and some other minor fixes.","3":"Got rid of all the unfitting pure black (#000000) objects and some other minor fixes.","package":"darktango.vim","4":"darktango.vim","src_id":"6266","5":"6266","creation_date":"1160481006","6":"1160481006"}]},"1671":{"script_id":"1671","0":"1671","script_name":"doorhinge.vim","1":"doorhinge.vim","script_type":"color scheme","2":"color scheme","summary":"light blue theme with orange highlights","3":"light blue theme with orange highlights","description":"doorhinge color theme\r\n\r\nUpdated: cleaned up a bit, added cursorline, diff, pmenu, tabline, minibuf, modified statusline, visual modes, folds, color tweak, half decent console colors.","4":"doorhinge color theme\r\n\r\nUpdated: cleaned up a bit, added cursorline, diff, pmenu, tabline, minibuf, modified statusline, visual modes, folds, color tweak, half decent console colors.","install_details":"","5":"","first_name":"talso","6":"talso","last_name":".","7":".","releases":[{"0":"1671","vim_version":"7.0","1":"7.0","script_version":"0.6","2":"0.6","version_comment":"cleaned up a bit, added cursorline, diff, pmenu, tabline, minibuf, modified statusline, visual modes, folds, color tweaks, half decent console looks\r\n\r\nhttp:\/\/members.shaw.ca\/dimset\/vim\/guishot.png\r\nhttp:\/\/members.shaw.ca\/dimset\/vim\/xtermshot.png","3":"cleaned up a bit, added cursorline, diff, pmenu, tabline, minibuf, modified statusline, visual modes, folds, color tweaks, half decent console looks\r\n\r\nhttp:\/\/members.shaw.ca\/dimset\/vim\/guishot.png\r\nhttp:\/\/members.shaw.ca\/dimset\/vim\/xtermshot.png","package":"doorhinge.vim","4":"doorhinge.vim","src_id":"7852","5":"7852","creation_date":"1193831916","6":"1193831916"}]},"1669":{"script_id":"1669","0":"1669","script_name":"Deleted","1":"Deleted","script_type":"utility","2":"utility","summary":"Deleted","3":"Deleted","description":"Deleted","4":"Deleted","install_details":"Deleted","5":"Deleted","first_name":"Mykola","6":"Mykola","last_name":"Golubyev","7":"Golubyev","releases":[{"0":"1669","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"win_full_screen.vim","4":"win_full_screen.vim","src_id":"6251","5":"6251","creation_date":"1159952742","6":"1159952742"}]},"1668":{"script_id":"1668","0":"1668","script_name":"blink","1":"blink","script_type":"color scheme","2":"color scheme","summary":"Minimal colorscheme.","3":"Minimal colorscheme.","description":"A minimal (but complete) colorscheme for dark backgrounds.  Written to simplify customization.","4":"A minimal (but complete) colorscheme for dark backgrounds.  Written to simplify customization.","install_details":"Place this script in your ~\/.vim\/colors directory, and activate with \":colorscheme blink\" from Vim.","5":"Place this script in your ~\/.vim\/colors directory, and activate with \":colorscheme blink\" from Vim.","first_name":"Adam","6":"Adam","last_name":"Blinkinsop","7":"Blinkinsop","releases":[{"0":"1668","vim_version":"7.0","1":"7.0","script_version":"1.2","2":"1.2","version_comment":"Fixed visual selection colors for the gui.","3":"Fixed visual selection colors for the gui.","package":"blink.vim","4":"blink.vim","src_id":"6259","5":"6259","creation_date":"1160130503","6":"1160130503"},{"0":"1668","vim_version":"7.0","1":"7.0","script_version":"1.1","2":"1.1","version_comment":"Fixed gui colors to match terminal colors (whoa, brown is really different), fixed cursor.","3":"Fixed gui colors to match terminal colors (whoa, brown is really different), fixed cursor.","package":"blink.vim","4":"blink.vim","src_id":"6256","5":"6256","creation_date":"1160042590","6":"1160042590"},{"0":"1668","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"blink.vim","4":"blink.vim","src_id":"6240","5":"6240","creation_date":"1159542366","6":"1159542366"}]},"1667":{"script_id":"1667","0":"1667","script_name":"campfire","1":"campfire","script_type":"color scheme","2":"color scheme","summary":"A feel good colorscheme","3":"A feel good colorscheme","description":"Remember those nights, sitting around the campfire.\r\nThe darkblue sky, the green matches, the colors of the campfire, the red coals, the grey ashes.","4":"Remember those nights, sitting around the campfire.\r\nThe darkblue sky, the green matches, the colors of the campfire, the red coals, the grey ashes.","install_details":"Put it in \"~\/.vim\/colors\" or in \"<your vim directory>\\vimfiles\\colors\" on Windows. Do \":colo campfire\" to apply it. To install it as your default color scheme, add \"colo campfire\" to your vimrc file. ","5":"Put it in \"~\/.vim\/colors\" or in \"<your vim directory>\\vimfiles\\colors\" on Windows. Do \":colo campfire\" to apply it. To install it as your default color scheme, add \"colo campfire\" to your vimrc file. ","first_name":"no","6":"no","last_name":"reply","7":"reply","releases":[{"0":"1667","vim_version":"6.0","1":"6.0","script_version":"1.01","2":"1.01","version_comment":"Fixed cursor color.","3":"Fixed cursor color.","package":"campfire.vim","4":"campfire.vim","src_id":"6238","5":"6238","creation_date":"1159410532","6":"1159410532"}]},"1666":{"script_id":"1666","0":"1666","script_name":"Alternate workspace","1":"Alternate workspace","script_type":"utility","2":"utility","summary":"Switch or watch diff between alternate files from child and parent workspaces","3":"Switch or watch diff between alternate files from child and parent workspaces","description":" This script provide a way to quickly switch between files from different workspaces (Child and Parent). And to see difference between them.\r\n\r\nSet variable g:aw_child_path and g:aw_parent_path to work with this script.\r\n\r\nExample of vimrc:\r\n\r\n   let g:aw_child_path = '\/home\/ni\/branch'\r\n   let g:aw_parent_path = '\/project\/' \r\n   let g:aw_stop_word = 'src'\r\n\r\n   nnoremap \\wd :AWDiffMirror<CR>\r\n   nnoremap \\we :AWEditMirror<CR>\r\n\r\nEDIT MIRROR\r\n\r\nSuppose you have two files in different workspaces.\r\nYou edit now file from child workspace.\r\n\r\nyou are at line 100\r\nin that line is text 'int main()'\r\n\r\nin alternate file there is line 'int main()' too but in line 200\r\n\r\nafter command :AWEditMirrorFile you will be at line 200 in alternate file\r\nIt is very useful.\r\n\r\nif there is now such line in alternate file you'll be at line 100.\r\n\r\nSET WORKSPACES \r\n\r\nUse AWSetChild and AWSetParent commands to set workspaces directories (thanks to Sergey Popov).\r\n\r\nUse AWAutoSetChild and AWAutoSetParent commands - this commands will create child and parent path form current file name\r\nexample: \r\n    let g:aw_stop_word = 'src'\r\n    current file name = '\/home\/me\/project\/src\/....\/...\/1.cpp'\r\n    after execution of AWAutoSetChild aw_child_path will be '\/home\/me\/project\/'\r\n\r\n:AWEditMirrorFile - edit alternate file\r\n:AWDiffMirrorFile - diff current and alternate file\r\n","4":" This script provide a way to quickly switch between files from different workspaces (Child and Parent). And to see difference between them.\r\n\r\nSet variable g:aw_child_path and g:aw_parent_path to work with this script.\r\n\r\nExample of vimrc:\r\n\r\n   let g:aw_child_path = '\/home\/ni\/branch'\r\n   let g:aw_parent_path = '\/project\/' \r\n   let g:aw_stop_word = 'src'\r\n\r\n   nnoremap \\wd :AWDiffMirror<CR>\r\n   nnoremap \\we :AWEditMirror<CR>\r\n\r\nEDIT MIRROR\r\n\r\nSuppose you have two files in different workspaces.\r\nYou edit now file from child workspace.\r\n\r\nyou are at line 100\r\nin that line is text 'int main()'\r\n\r\nin alternate file there is line 'int main()' too but in line 200\r\n\r\nafter command :AWEditMirrorFile you will be at line 200 in alternate file\r\nIt is very useful.\r\n\r\nif there is now such line in alternate file you'll be at line 100.\r\n\r\nSET WORKSPACES \r\n\r\nUse AWSetChild and AWSetParent commands to set workspaces directories (thanks to Sergey Popov).\r\n\r\nUse AWAutoSetChild and AWAutoSetParent commands - this commands will create child and parent path form current file name\r\nexample: \r\n    let g:aw_stop_word = 'src'\r\n    current file name = '\/home\/me\/project\/src\/....\/...\/1.cpp'\r\n    after execution of AWAutoSetChild aw_child_path will be '\/home\/me\/project\/'\r\n\r\n:AWEditMirrorFile - edit alternate file\r\n:AWDiffMirrorFile - diff current and alternate file\r\n","install_details":"Put alternate_workspace.vim in plugin directory","5":"Put alternate_workspace.vim in plugin directory","first_name":"Mykola","6":"Mykola","last_name":"Golubyev","7":"Golubyev","releases":[{"0":"1666","vim_version":"6.0","1":"6.0","script_version":"2.0","2":"2.0","version_comment":"AWEditMirrorFile command not only open alternate file but moves to position where is same line (current line) is present. \r\nYou can easily change workspaces by new commands:\r\n:AWAutoSetChild\r\n:AWAutoSetParent\r\nExample:\r\nif you have current file name \"\/home\/me\/project\/src\/.....\/.cpp\"\r\nyou can set variable g:aw_stop_word = \"src\" and after execution of command :AWAutoSetChild\r\nchild path will be \"\/home\/me\/project\"\r\n\r\nRemoved mappings for EditMirrorFile and DiffMirrorFile (\r\nAdd \r\nnnoremap key1 :AWEditMirrorFile<CR>\r\nnnoremap key2 :AWDiffMirrorFile<CR>\r\n...","3":"AWEditMirrorFile command not only open alternate file but moves to position where is same line (current line) is present. \r\nYou can easily change workspaces by new commands:\r\n:AWAutoSetChild\r\n:AWAutoSetParent\r\nExample:\r\nif you have current file name \"\/home\/me\/project\/src\/.....\/.cpp\"\r\nyou can set variable g:aw_stop_word = \"src\" and after execution of command :AWAutoSetChild\r\nchild path will be \"\/home\/me\/project\"\r\n\r\nRemoved mappings for EditMirrorFile and DiffMirrorFile (\r\nAdd \r\nnnoremap key1 :AWEditMirrorFile<CR>\r\nnnoremap key2 :AWDiffMirrorFile<CR>\r\n...","package":"alternate_workspace.vim","4":"alternate_workspace.vim","src_id":"6525","5":"6525","creation_date":"1166513571","6":"1166513571"},{"0":"1666","vim_version":"6.0","1":"6.0","script_version":"1.1","2":"1.1","version_comment":"Added AWSetChild and AWSetParent commands.","3":"Added AWSetChild and AWSetParent commands.","package":"alternate_workspace.vim","4":"alternate_workspace.vim","src_id":"6229","5":"6229","creation_date":"1159232679","6":"1159232679"},{"0":"1666","vim_version":"6.0","1":"6.0","script_version":"1","2":"1","version_comment":"Initial upload","3":"Initial upload","package":"alternate_workspace.vim","4":"alternate_workspace.vim","src_id":"6223","5":"6223","creation_date":"1159152312","6":"1159152312"}]},"1665":{"script_id":"1665","0":"1665","script_name":"tavi.vim","1":"tavi.vim","script_type":"syntax","2":"syntax","summary":"Syntax highlighting for the WikkiTikkiTavi ('Tavi) wiki engine","3":"Syntax highlighting for the WikkiTikkiTavi ('Tavi) wiki engine","description":"Syntax highlighting for the WikkiTikkiTavi ('Tavi) wiki engine.\r\n\r\nHomepage: http:\/\/tavi.sourceforge.net\/","4":"Syntax highlighting for the WikkiTikkiTavi ('Tavi) wiki engine.\r\n\r\nHomepage: http:\/\/tavi.sourceforge.net\/","install_details":"Copy tavi.vim to $VIMRUNTIME\/syntax. 'set filetype=tavi' to turn the highlighting on. See 'help 43.2' if you want to detect tavi pages automatically.","5":"Copy tavi.vim to $VIMRUNTIME\/syntax. 'set filetype=tavi' to turn the highlighting on. See 'help 43.2' if you want to detect tavi pages automatically.","first_name":"Hermann","6":"Hermann","last_name":"Schwarting","7":"Schwarting","releases":[{"0":"1665","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"tavi.vim","4":"tavi.vim","src_id":"6222","5":"6222","creation_date":"1159088829","6":"1159088829"}]},"1664":{"script_id":"1664","0":"1664","script_name":"buftabs","1":"buftabs","script_type":"utility","2":"utility","summary":"Minimalistic buffer tabs saving screen space","3":"Minimalistic buffer tabs saving screen space","description":"[Screeshot available at  http:\/\/zevv.nl\/play\/code\/vimscripts\/]\r\n\r\n\r\nIntroduction\r\n------------\r\nThis is a simple script that shows a tabs-like list of buffers in the bottom\r\nof the window. The biggest advantage of this script over various others is\r\nthat it does not take any lines away from your terminal, leaving more space\r\nfor the document you're editing. The tabs are only visible when you need\r\nthem - when you are switching between buffers.\r\n\r\nUsage\r\n-----\r\nThis script draws buffer tabs on vim startup, when a new buffer is created\r\nand when switching between buffers.\r\n\r\nIt might be handy to create a few maps for easy switching of buffers in your\r\n.vimrc file. For example, using F1 and F2 keys:\r\n\r\n  noremap <f1> :bprev<CR> \r\n  noremap <f2> :bnext<CR>\r\n\r\nor using control-left and control-right keys:\r\n\r\n  :noremap <C-left> :bprev<CR>\r\n  :noremap <C-right> :bnext<CR>\r\n\r\n\r\nSome configuration options are available for styling and layout, check the top of the plugin file for instructions.\r\n","4":"[Screeshot available at  http:\/\/zevv.nl\/play\/code\/vimscripts\/]\r\n\r\n\r\nIntroduction\r\n------------\r\nThis is a simple script that shows a tabs-like list of buffers in the bottom\r\nof the window. The biggest advantage of this script over various others is\r\nthat it does not take any lines away from your terminal, leaving more space\r\nfor the document you're editing. The tabs are only visible when you need\r\nthem - when you are switching between buffers.\r\n\r\nUsage\r\n-----\r\nThis script draws buffer tabs on vim startup, when a new buffer is created\r\nand when switching between buffers.\r\n\r\nIt might be handy to create a few maps for easy switching of buffers in your\r\n.vimrc file. For example, using F1 and F2 keys:\r\n\r\n  noremap <f1> :bprev<CR> \r\n  noremap <f2> :bnext<CR>\r\n\r\nor using control-left and control-right keys:\r\n\r\n  :noremap <C-left> :bprev<CR>\r\n  :noremap <C-right> :bnext<CR>\r\n\r\n\r\nSome configuration options are available for styling and layout, check the top of the plugin file for instructions.\r\n","install_details":"Copy the script into your plugin directory, and optionally define configuration items for styling the buftabs layout.","5":"Copy the script into your plugin directory, and optionally define configuration items for styling the buftabs layout.","first_name":"Ico","6":"Ico","last_name":"-","7":"-","releases":[{"0":"1664","vim_version":"7.0","1":"7.0","script_version":"0.18","2":"0.18","version_comment":"Added marker for denoting modified buffers, provide function for including buftabs into status line descriptor instead of buftabs having to edit the status line directly.\r\n","3":"Added marker for denoting modified buffers, provide function for including buftabs into status line descriptor instead of buftabs having to edit the status line directly.\r\n","package":"buftabs.vim","4":"buftabs.vim","src_id":"15439","5":"15439","creation_date":"1302606580","6":"1302606580"},{"0":"1664","vim_version":"7.0","1":"7.0","script_version":"0.17","2":"0.17","version_comment":"Changed persistent echo function to restore 'updatetime', leading to better behaviour when showing buftabs in the status line.","3":"Changed persistent echo function to restore 'updatetime', leading to better behaviour when showing buftabs in the status line.","package":"buftabs.vim","4":"buftabs.vim","src_id":"15426","5":"15426","creation_date":"1302501137","6":"1302501137"},{"0":"1664","vim_version":"6.0","1":"6.0","script_version":"0.16","2":"0.16","version_comment":"Fixed bug causing errors when using buftabs in vimdiff mode.","3":"Fixed bug causing errors when using buftabs in vimdiff mode.","package":"buftabs.vim","4":"buftabs.vim","src_id":"12520","5":"12520","creation_date":"1267356626","6":"1267356626"},{"0":"1664","vim_version":"6.0","1":"6.0","script_version":"0.15","2":"0.15","version_comment":"* Fixed window width handling bug which caused strange behaviour in combination with the bufferlist plugin.\r\n* Fixed wrong buffer display when deleting last window.\r\n* Added extra options for tabs style and highlighting.\r\n\r\nThaks to all contributors!","3":"* Fixed window width handling bug which caused strange behaviour in combination with the bufferlist plugin.\r\n* Fixed wrong buffer display when deleting last window.\r\n* Added extra options for tabs style and highlighting.\r\n\r\nThaks to all contributors!","package":"buftabs.vim","4":"buftabs.vim","src_id":"12392","5":"12392","creation_date":"1266351965","6":"1266351965"},{"0":"1664","vim_version":"6.0","1":"6.0","script_version":"0.14","2":"0.14","version_comment":"Fixed bug that caused buftabs in command line being overwritten when 'hidden' mode is enabled.\r\n","3":"Fixed bug that caused buftabs in command line being overwritten when 'hidden' mode is enabled.\r\n","package":"buftabs.vim","4":"buftabs.vim","src_id":"12205","5":"12205","creation_date":"1264673210","6":"1264673210"},{"0":"1664","vim_version":"6.0","1":"6.0","script_version":"0.13","2":"0.13","version_comment":"Reusing right-aligned part of original statusline instead of using fixed '%l,%c'","3":"Reusing right-aligned part of original statusline instead of using fixed '%l,%c'","package":"buftabs.vim","4":"buftabs.vim","src_id":"10557","5":"10557","creation_date":"1241700394","6":"1241700394"},{"0":"1664","vim_version":"6.0","1":"6.0","script_version":"0.12","2":"0.12","version_comment":"Fixed support for split windows","3":"Fixed support for split windows","package":"buftabs.vim","4":"buftabs.vim","src_id":"10237","5":"10237","creation_date":"1237359754","6":"1237359754"},{"0":"1664","vim_version":"6.0","1":"6.0","script_version":"0.10","2":"0.10","version_comment":"Added GPL license","3":"Added GPL license","package":"buftabs.vim","4":"buftabs.vim","src_id":"8181","5":"8181","creation_date":"1201315032","6":"1201315032"},{"0":"1664","vim_version":"6.0","1":"6.0","script_version":"0.9","2":"0.9","version_comment":"Now compatible with older Vim versions < 7.0 as well","3":"Now compatible with older Vim versions < 7.0 as well","package":"buftabs.vim","4":"buftabs.vim","src_id":"7544","5":"7544","creation_date":"1187782228","6":"1187782228"},{"0":"1664","vim_version":"7.0","1":"7.0","script_version":"0.8","2":"0.8","version_comment":"Update buftabs when leaving insert to properly show modified-status.","3":"Update buftabs when leaving insert to properly show modified-status.","package":"buftabs.vim","4":"buftabs.vim","src_id":"7056","5":"7056","creation_date":"1178113140","6":"1178113140"},{"0":"1664","vim_version":"6.0","1":"6.0","script_version":"0.7","2":"0.7","version_comment":"Added configuration option to show tabs in statusline instead of cmdline","3":"Added configuration option to show tabs in statusline instead of cmdline","package":"buftabs.vim","4":"buftabs.vim","src_id":"6846","5":"6846","creation_date":"1173235309","6":"1173235309"},{"0":"1664","vim_version":"6.0","1":"6.0","script_version":"0.6","2":"0.6","version_comment":"'only_basename' changed to a global variable.  Removed functions and add event handlers instead.  'hidden' mode broke some things, so is disabled now. Fixed documentation.","3":"'only_basename' changed to a global variable.  Removed functions and add event handlers instead.  'hidden' mode broke some things, so is disabled now. Fixed documentation.","package":"buftabs.vim","4":"buftabs.vim","src_id":"6832","5":"6832","creation_date":"1172983161","6":"1172983161"},{"0":"1664","vim_version":"6.0","1":"6.0","script_version":"0.5","2":"0.5","version_comment":"Added option for showing only filenames without directories in tabs","3":"Added option for showing only filenames without directories in tabs","package":"buftabs.vim","4":"buftabs.vim","src_id":"6799","5":"6799","creation_date":"1172481998","6":"1172481998"}]},"1663":{"script_id":"1663","0":"1663","script_name":"asm8051.vim","1":"asm8051.vim","script_type":"syntax","2":"syntax","summary":"Syntax for 8051 Assembly (some IAR specifics)","3":"Syntax for 8051 Assembly (some IAR specifics)","description":"To my surprise I could not find a syntax file for 8051 assembly.  So I started with vimscript#966 (which was apparently derived from the asm68k syntax) and derived this syntax file.\r\n\r\nThe assembler directives and such are IAR specific b\/c that is the toolset that I am currently using.  Feel free to expand with support for Keil and\/or SDCC.\r\n","4":"To my surprise I could not find a syntax file for 8051 assembly.  So I started with vimscript#966 (which was apparently derived from the asm68k syntax) and derived this syntax file.\r\n\r\nThe assembler directives and such are IAR specific b\/c that is the toolset that I am currently using.  Feel free to expand with support for Keil and\/or SDCC.\r\n","install_details":"Place in the $VIMRUNTIME\/syntax directory and set up the appropriate filetype commands (filetype.vim or other methods) to tell vim to use asm8051 syntax for your 8051 assembly files.\r\n","5":"Place in the $VIMRUNTIME\/syntax directory and set up the appropriate filetype commands (filetype.vim or other methods) to tell vim to use asm8051 syntax for your 8051 assembly files.\r\n","first_name":"Keith","6":"Keith","last_name":"Richeson","7":"Richeson","releases":[{"0":"1663","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"asm8051.vim","4":"asm8051.vim","src_id":"6216","5":"6216","creation_date":"1158924282","6":"1158924282"}]},"1662":{"script_id":"1662","0":"1662","script_name":"rubycomplete.vim","1":"rubycomplete.vim","script_type":"utility","2":"utility","summary":"ruby omni-completion","3":"ruby omni-completion","description":"rubycomplete is an omni-completion script for ruby. \r\nIt supports the following:\r\n  * dynamic completion of in-buffer entities (classes, methods, objects, modules).\r\n  * rails \r\n          - inclusion of column-names\/fields\r\n          - helpers included in completions\r\n  * automatic inclusion of required modules\r\n  * automatic handling of syntax errors\r\n\r\nRubycomplete requires ruby support to work. It uses ruby to process the buffer and introspection to create a list of completions. \r\nIt is distributed with vim, and as part of the vim-ruby project (http:\/\/vim-ruby.rubyforge.org\/).\r\nCVS versions are availible from vim-ruby, major releases will be published here and on my site.\r\n\r\nFor more info go to: http:\/\/blog.hasno.info\/blog\/segfault\/dev\/2006\/04\/10\/vim-7-ruby-omni-completion.html\r\n","4":"rubycomplete is an omni-completion script for ruby. \r\nIt supports the following:\r\n  * dynamic completion of in-buffer entities (classes, methods, objects, modules).\r\n  * rails \r\n          - inclusion of column-names\/fields\r\n          - helpers included in completions\r\n  * automatic inclusion of required modules\r\n  * automatic handling of syntax errors\r\n\r\nRubycomplete requires ruby support to work. It uses ruby to process the buffer and introspection to create a list of completions. \r\nIt is distributed with vim, and as part of the vim-ruby project (http:\/\/vim-ruby.rubyforge.org\/).\r\nCVS versions are availible from vim-ruby, major releases will be published here and on my site.\r\n\r\nFor more info go to: http:\/\/blog.hasno.info\/blog\/segfault\/dev\/2006\/04\/10\/vim-7-ruby-omni-completion.html\r\n","install_details":"copy to .vim\/autoload or your global runtime autoload directory. ","5":"copy to .vim\/autoload or your global runtime autoload directory. ","first_name":"Mark","6":"Mark","last_name":"Guzman","7":"Guzman","releases":[{"0":"1662","vim_version":"7.0","1":"7.0","script_version":"0.7","2":"0.7","version_comment":"Initial upload","3":"Initial upload","package":"rubycomplete.vim","4":"rubycomplete.vim","src_id":"6203","5":"6203","creation_date":"1158660371","6":"1158660371"}]},"1661":{"script_id":"1661","0":"1661","script_name":"redocommand","1":"redocommand","script_type":"utility","2":"utility","summary":"Execute commands from the command history.","3":"Execute commands from the command history.","description":"DESCRIPTION\r\nRe-executes the last \/ Nth ex command previously entered in command mode. An\r\noptional pattern is used to locate the most recent matching command. This is\r\nsimilar to the command-line window (q:), or navigating the command history via\r\n<Up> and <Down>, but provides an even faster way to re-execute a command if\r\nyou remember some characters or a pattern that identifies the command line.\r\nThe redocommand itself will not be included in the command history. Global\r\nliteral replacement can be done via 'old=new' arguments.\r\n\r\nThis is modeled after the 'fc -s' command from the Posix shell (which is often\r\naliased to 'r').\r\n\r\nUSAGE\r\n:[N]Redocommand (or abbreviated :R)\r\n                        Execute the last \/ Nth ex command.\r\n\r\n:[N]Redocommand {pattern}\r\n                        Execute the last \/ Nth ex command that matches\r\n                        {pattern}.\r\n                        Settings such as 'magic' and 'ignorecase' apply.\r\n\r\n                        With N=0, only the very last command from the history\r\n                        is executed if it matches {pattern}; the entire\r\n                        history isn't searched.\r\n\r\n                        Note: If the {pattern} starts with : (and there is no\r\n                        history command matching the literal \":cmd\"), the\r\n                        history is searched for \"cmd\", anchored at the\r\n                        beginning. This is convenient because \":R :echo\" is\r\n                        more intuitive to type than \":R ^echo\".\r\n\r\n:[N]Redocommand {old}={new} [{old2}={new2} ...] [{pattern}]\r\n                        Execute the last \/ Nth ex command (that matches\r\n                        {pattern}), replacing all literal occurrences of {old}\r\n                        with {new}.\r\n\r\n:[N]RedoRepeat [{old}={new} ...] (or abbreviated :RR)\r\n                        Execute the last \/ Nth ex command that was repeated\r\n                        via :Redocommand. Any replacements done the last time\r\n                        are still in effect; new replacements of {old} to\r\n                        {new} can be added.\r\n\r\nThe following variants are useful when you repeatedly use command A in one\r\nbuffer and command B in another. Instead of passing different [N] values to\r\n:RedoRepeat, just recall from the local redo history.\r\n\r\n:[N]RedoBufferRepeat [{old}={new} ...] (or abbreviated :RB)\r\n                        Like :RedoRepeat, but repeat the last \/ Nth ex\r\n                        command repeated in the current buffer.\r\n\r\n:[N]RedoWindowRepeat [{old}={new} ...] (or abbreviated :RW)\r\n                        Like :RedoRepeat, but repeat the last \/ Nth ex\r\n                        command repeated in the current window.\r\n\r\nEXAMPLE\r\nGiven the following history:\r\n    :history\r\n    1 e foo.txt\r\n    2 %s\/foo\/\\0bar\/g\r\n    3 w bar.txt\r\n:Redocommand            will execute :w bar.txt\r\n:Redocommand %          will execute :%s\/foo\\0\/bar\/g\r\n:Redocommand foo        will execute :%s\/foo\\0\/bar\/g\r\n:2Redocommand foo       will execute :e foo.txt\r\n:Redocommand b=B .txt=  will execute ':w bar.txt' as :w Bar\r\n\r\n:echo \"another command\"\r\n:RedoRepeat             will again execute :w Bar\r\n:2RedoRepeat            will execute :%s\/foo\\0\/bar\/g\r\n:RedoRepeat B=F         will execute :w Far\r\n:Redocommand            will execute :echo \"another command\"\r\n:RedoRepeat             will execute :w Far","4":"DESCRIPTION\r\nRe-executes the last \/ Nth ex command previously entered in command mode. An\r\noptional pattern is used to locate the most recent matching command. This is\r\nsimilar to the command-line window (q:), or navigating the command history via\r\n<Up> and <Down>, but provides an even faster way to re-execute a command if\r\nyou remember some characters or a pattern that identifies the command line.\r\nThe redocommand itself will not be included in the command history. Global\r\nliteral replacement can be done via 'old=new' arguments.\r\n\r\nThis is modeled after the 'fc -s' command from the Posix shell (which is often\r\naliased to 'r').\r\n\r\nUSAGE\r\n:[N]Redocommand (or abbreviated :R)\r\n                        Execute the last \/ Nth ex command.\r\n\r\n:[N]Redocommand {pattern}\r\n                        Execute the last \/ Nth ex command that matches\r\n                        {pattern}.\r\n                        Settings such as 'magic' and 'ignorecase' apply.\r\n\r\n                        With N=0, only the very last command from the history\r\n                        is executed if it matches {pattern}; the entire\r\n                        history isn't searched.\r\n\r\n                        Note: If the {pattern} starts with : (and there is no\r\n                        history command matching the literal \":cmd\"), the\r\n                        history is searched for \"cmd\", anchored at the\r\n                        beginning. This is convenient because \":R :echo\" is\r\n                        more intuitive to type than \":R ^echo\".\r\n\r\n:[N]Redocommand {old}={new} [{old2}={new2} ...] [{pattern}]\r\n                        Execute the last \/ Nth ex command (that matches\r\n                        {pattern}), replacing all literal occurrences of {old}\r\n                        with {new}.\r\n\r\n:[N]RedoRepeat [{old}={new} ...] (or abbreviated :RR)\r\n                        Execute the last \/ Nth ex command that was repeated\r\n                        via :Redocommand. Any replacements done the last time\r\n                        are still in effect; new replacements of {old} to\r\n                        {new} can be added.\r\n\r\nThe following variants are useful when you repeatedly use command A in one\r\nbuffer and command B in another. Instead of passing different [N] values to\r\n:RedoRepeat, just recall from the local redo history.\r\n\r\n:[N]RedoBufferRepeat [{old}={new} ...] (or abbreviated :RB)\r\n                        Like :RedoRepeat, but repeat the last \/ Nth ex\r\n                        command repeated in the current buffer.\r\n\r\n:[N]RedoWindowRepeat [{old}={new} ...] (or abbreviated :RW)\r\n                        Like :RedoRepeat, but repeat the last \/ Nth ex\r\n                        command repeated in the current window.\r\n\r\nEXAMPLE\r\nGiven the following history:\r\n    :history\r\n    1 e foo.txt\r\n    2 %s\/foo\/\\0bar\/g\r\n    3 w bar.txt\r\n:Redocommand            will execute :w bar.txt\r\n:Redocommand %          will execute :%s\/foo\\0\/bar\/g\r\n:Redocommand foo        will execute :%s\/foo\\0\/bar\/g\r\n:2Redocommand foo       will execute :e foo.txt\r\n:Redocommand b=B .txt=  will execute ':w bar.txt' as :w Bar\r\n\r\n:echo \"another command\"\r\n:RedoRepeat             will again execute :w Bar\r\n:2RedoRepeat            will execute :%s\/foo\\0\/bar\/g\r\n:RedoRepeat B=F         will execute :w Far\r\n:Redocommand            will execute :echo \"another command\"\r\n:RedoRepeat             will execute :w Far","install_details":"INSTALLATION\r\nThis script is packaged as a vimball. If you have the \"gunzip\" decompressor\r\nin your PATH, simply edit the *.vba.gz package in Vim; otherwise, decompress\r\nthe archive first, e.g. using WinZip. Inside Vim, install by sourcing the\r\nvimball or via the :UseVimball command.\r\n    vim redocommand.vba.gz\r\n    :so %\r\nTo uninstall, use the :RmVimball command.\r\n\r\nDEPENDENCIES\r\n- Requires Vim 7.0 or higher.\r\n\r\nCONFIGURATION\r\nIf you do not want the shorthand :R, :RR, :R... commands, define (e.g. in your\r\nvimrc):\r\n    let g:redocommand_no_short_command = 1","5":"INSTALLATION\r\nThis script is packaged as a vimball. If you have the \"gunzip\" decompressor\r\nin your PATH, simply edit the *.vba.gz package in Vim; otherwise, decompress\r\nthe archive first, e.g. using WinZip. Inside Vim, install by sourcing the\r\nvimball or via the :UseVimball command.\r\n    vim redocommand.vba.gz\r\n    :so %\r\nTo uninstall, use the :RmVimball command.\r\n\r\nDEPENDENCIES\r\n- Requires Vim 7.0 or higher.\r\n\r\nCONFIGURATION\r\nIf you do not want the shorthand :R, :RR, :R... commands, define (e.g. in your\r\nvimrc):\r\n    let g:redocommand_no_short_command = 1","first_name":"Ingo","6":"Ingo","last_name":"Karkat","7":"Karkat","releases":[{"0":"1661","vim_version":"7.0","1":"7.0","script_version":"1.40","2":"1.40","version_comment":"ENH: Add :RedoBufferRepeat \/ :RB and :RedoWindowRepeat \/ :RW commands. These are useful when you repeatedly use command A in one buffer and command B in another. Instead of passing different [N] values to :RedoRepeat, just recall from the local redo history.","3":"ENH: Add :RedoBufferRepeat \/ :RB and :RedoWindowRepeat \/ :RW commands. These are useful when you repeatedly use command A in one buffer and command B in another. Instead of passing different [N] values to :RedoRepeat, just recall from the local redo history.","package":"redocommand.vba.gz","4":"redocommand.vba.gz","src_id":"18293","5":"18293","creation_date":"1342792720","6":"1342792720"},{"0":"1661","vim_version":"7.0","1":"7.0","script_version":"1.30","2":"1.30","version_comment":"- ENH: Add :RedoRepeat command to repeat the last \/ Nth :Redocommand when other Ex commands (e.g. :wnext) were issued in between. \r\n- ENH: If the {pattern} starts with : (and there is no history command matching the literal \":cmd\"), the history is searched for \"cmd\", anchored at the beginning. This is convenient because \":R :echo\" is more intuitive to type than \":R ^echo\". ","3":"- ENH: Add :RedoRepeat command to repeat the last \/ Nth :Redocommand when other Ex commands (e.g. :wnext) were issued in between. \r\n- ENH: If the {pattern} starts with : (and there is no history command matching the literal \":cmd\"), the history is searched for \"cmd\", anchored at the beginning. This is convenient because \":R :echo\" is more intuitive to type than \":R ^echo\". ","package":"redocommand.vba.gz","4":"redocommand.vba.gz","src_id":"16948","5":"16948","creation_date":"1322034027","6":"1322034027"},{"0":"1661","vim_version":"7.0","1":"7.0","script_version":"1.20","2":"1.20","version_comment":"- Added optional [count] to repeat the Nth, not the last found match. \r\n- Split off documentation into separate help file. Now packaging as VimBall.\r\n- Using separate autoload script to help speed up VIM startup. ","3":"- Added optional [count] to repeat the Nth, not the last found match. \r\n- Split off documentation into separate help file. Now packaging as VimBall.\r\n- Using separate autoload script to help speed up VIM startup. ","package":"redocommand.vba.gz","4":"redocommand.vba.gz","src_id":"10342","5":"10342","creation_date":"1238754794","6":"1238754794"},{"0":"1661","vim_version":"7.0","1":"7.0","script_version":"1.10.005","2":"1.10.005","version_comment":"Implemented ':Redocommand old=new <pattern>'. Now requiring VIM 7. ","3":"Implemented ':Redocommand old=new <pattern>'. Now requiring VIM 7. ","package":"redocommand.vim","4":"redocommand.vim","src_id":"9951","5":"9951","creation_date":"1234383489","6":"1234383489"},{"0":"1661","vim_version":"6.0","1":"6.0","script_version":"1.00.003","2":"1.00.003","version_comment":"Better handling of errors during execution of the command. \r\nThe redone command is added to the history.  \r\nLast version with support for VIM 6.2 - 6.4; dropped support for VIM 6.0 and 6.1. ","3":"Better handling of errors during execution of the command. \r\nThe redone command is added to the history.  \r\nLast version with support for VIM 6.2 - 6.4; dropped support for VIM 6.0 and 6.1. ","package":"redocommand.vim","4":"redocommand.vim","src_id":"9071","5":"9071","creation_date":"1217820307","6":"1217820307"},{"0":"1661","vim_version":"6.0","1":"6.0","script_version":"0.02","2":"0.02","version_comment":"Initial upload","3":"Initial upload","package":"redocommand.vim","4":"redocommand.vim","src_id":"6197","5":"6197","creation_date":"1158557390","6":"1158557390"}]},"1660":{"script_id":"1660","0":"1660","script_name":"mint","1":"mint","script_type":"color scheme","2":"color scheme","summary":"dark background (gui only)","3":"dark background (gui only)","description":"Colorscheme I currently use, just want to share it.\r\n\r\nI don't know if there is anything minty about the colors, but I like the name ...\r\n\r\nPreview http:\/\/img45.imageshack.us\/img45\/4215\/mintht7.png (Bitstream Vera Sans Mono 9pt Bold, set linespace=2)\r\n(Thanks to ImageShack for [URL=http:\/\/imageshack.us]Free Image Hosting[\/URL])\r\n\r\nThanks.","4":"Colorscheme I currently use, just want to share it.\r\n\r\nI don't know if there is anything minty about the colors, but I like the name ...\r\n\r\nPreview http:\/\/img45.imageshack.us\/img45\/4215\/mintht7.png (Bitstream Vera Sans Mono 9pt Bold, set linespace=2)\r\n(Thanks to ImageShack for [URL=http:\/\/imageshack.us]Free Image Hosting[\/URL])\r\n\r\nThanks.","install_details":"put in .vim\/colors and type :colo mint","5":"put in .vim\/colors and type :colo mint","first_name":"Char","6":"Char","last_name":"Only","7":"Only","releases":[{"0":"1660","vim_version":"6.0","1":"6.0","script_version":"1.1","2":"1.1","version_comment":"Set darker background","3":"Set darker background","package":"mint.vim","4":"mint.vim","src_id":"6188","5":"6188","creation_date":"1158476189","6":"1158476189"}]},"1659":{"script_id":"1659","0":"1659","script_name":"dw_colors","1":"dw_colors","script_type":"color scheme","2":"color scheme","summary":"Set of black color schemes with some highlight variations","3":"Set of black color schemes with some highlight variations","description":"Like the summary says.  Screenshots for all variants can be found here: http:\/\/sites.google.com\/site\/dwcolors\/\r\n\r\nA contact e-mail is in the header of the colorschemes.  Please feel free to contact me with comments.","4":"Like the summary says.  Screenshots for all variants can be found here: http:\/\/sites.google.com\/site\/dwcolors\/\r\n\r\nA contact e-mail is in the header of the colorschemes.  Please feel free to contact me with comments.","install_details":"Unzip the package in your color schemes directory.\r\n\r\nUse \":colors dw_green\" or similar to switch between different variants or save in your vimrc.","5":"Unzip the package in your color schemes directory.\r\n\r\nUse \":colors dw_green\" or similar to switch between different variants or save in your vimrc.","first_name":"Steve","6":"Steve","last_name":"Cadwallader","7":"Cadwallader","releases":[{"0":"1659","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"dw_colors.zip","4":"dw_colors.zip","src_id":"6186","5":"6186","creation_date":"1158445210","6":"1158445210"}]},"1658":{"script_id":"1658","0":"1658","script_name":"The NERD tree","1":"The NERD tree","script_type":"utility","2":"utility","summary":"A tree explorer plugin for navigating the filesystem","3":"A tree explorer plugin for navigating the filesystem","description":"Grab the latest dev version from github: https:\/\/github.com\/scrooloose\/nerdtree. \r\n\r\nWhat is this \"NERD tree\"??\r\n\r\nCheck out this demo http:\/\/www.flickr.com\/photos\/30496122@N07\/2862367534\/sizes\/o\/\r\n\r\nThe NERD tree allows you to explore your filesystem and to open files and\r\ndirectories. It presents the filesystem to you in the form of a tree which you\r\nmanipulate with the keyboard and\/or mouse. It also allows you to perform\r\nsimple filesystem operations.\r\n\r\nThe following features and functionality are provided by the NERD tree:\r\n    * Files and directories are displayed in a hierarchical tree structure\r\n    * Different highlighting is provided for the following types of nodes:\r\n        * files\r\n        * directories\r\n        * sym-links\r\n        * windows .lnk files\r\n        * read-only files\r\n        * executable files\r\n    * Many (customisable) mappings are provided to manipulate the tree:\r\n        * Mappings to open\/close\/explore directory nodes\r\n        * Mappings to open files in new\/existing windows\/tabs\r\n        * Mappings to change the current root of the tree\r\n        * Mappings to navigate around the tree\r\n        * ...\r\n    * Directories and files can be bookmarked.\r\n    * Most NERD tree navigation can also be done with the mouse\r\n    * Filtering of tree content (can be toggled at runtime)\r\n        * custom file filters to prevent e.g. vim backup files being displayed\r\n        * optional displaying of hidden files (. files)\r\n        * files can be \"turned off\" so that only directories are displayed\r\n    * A textual filesystem menu is provided which allows you to\r\n      create\/delete\/move file and directory nodes as well as copy (for\r\n      supported OSs)\r\n    * The position and size of the NERD tree window can be customised\r\n    * The order in which the nodes in the tree are listed can be customised.\r\n    * A model of your filesystem is created\/maintained as you explore it. This\r\n      has several advantages:\r\n        * All filesystem information is cached and is only re-read on demand\r\n        * If you revisit a part of the tree that you left earlier in your\r\n          session, the directory nodes will be opened\/closed as you left them\r\n    * The script remembers the cursor position and window position in the NERD\r\n      tree so you can toggle it off (or just close the tree window) and then\r\n      reopen it (with NERDTreeToggle) the NERD tree window will appear exactly\r\n      as you left it\r\n    * You can have a separate NERD tree for each tab, share trees across tabs,\r\n      or a mix of both.\r\n    * By default the script overrides the default file browser (netw), so if\r\n      you :edit a directory a (slighly modified) NERD tree will appear in the\r\n      current window\r\n","4":"Grab the latest dev version from github: https:\/\/github.com\/scrooloose\/nerdtree. \r\n\r\nWhat is this \"NERD tree\"??\r\n\r\nCheck out this demo http:\/\/www.flickr.com\/photos\/30496122@N07\/2862367534\/sizes\/o\/\r\n\r\nThe NERD tree allows you to explore your filesystem and to open files and\r\ndirectories. It presents the filesystem to you in the form of a tree which you\r\nmanipulate with the keyboard and\/or mouse. It also allows you to perform\r\nsimple filesystem operations.\r\n\r\nThe following features and functionality are provided by the NERD tree:\r\n    * Files and directories are displayed in a hierarchical tree structure\r\n    * Different highlighting is provided for the following types of nodes:\r\n        * files\r\n        * directories\r\n        * sym-links\r\n        * windows .lnk files\r\n        * read-only files\r\n        * executable files\r\n    * Many (customisable) mappings are provided to manipulate the tree:\r\n        * Mappings to open\/close\/explore directory nodes\r\n        * Mappings to open files in new\/existing windows\/tabs\r\n        * Mappings to change the current root of the tree\r\n        * Mappings to navigate around the tree\r\n        * ...\r\n    * Directories and files can be bookmarked.\r\n    * Most NERD tree navigation can also be done with the mouse\r\n    * Filtering of tree content (can be toggled at runtime)\r\n        * custom file filters to prevent e.g. vim backup files being displayed\r\n        * optional displaying of hidden files (. files)\r\n        * files can be \"turned off\" so that only directories are displayed\r\n    * A textual filesystem menu is provided which allows you to\r\n      create\/delete\/move file and directory nodes as well as copy (for\r\n      supported OSs)\r\n    * The position and size of the NERD tree window can be customised\r\n    * The order in which the nodes in the tree are listed can be customised.\r\n    * A model of your filesystem is created\/maintained as you explore it. This\r\n      has several advantages:\r\n        * All filesystem information is cached and is only re-read on demand\r\n        * If you revisit a part of the tree that you left earlier in your\r\n          session, the directory nodes will be opened\/closed as you left them\r\n    * The script remembers the cursor position and window position in the NERD\r\n      tree so you can toggle it off (or just close the tree window) and then\r\n      reopen it (with NERDTreeToggle) the NERD tree window will appear exactly\r\n      as you left it\r\n    * You can have a separate NERD tree for each tab, share trees across tabs,\r\n      or a mix of both.\r\n    * By default the script overrides the default file browser (netw), so if\r\n      you :edit a directory a (slighly modified) NERD tree will appear in the\r\n      current window\r\n","install_details":"Unzip the archive into your ~\/.vim directory.\r\nThat should put NERD_tree.vim in ~\/.vim\/plugin and NERD_tree.txt in ~\/.vim\/doc.\r\n\r\n\r\n\r\nRun :helptags.\r\n\r\nGo :help NERD_tree.txt for the help page.\r\n\r\n","5":"Unzip the archive into your ~\/.vim directory.\r\nThat should put NERD_tree.vim in ~\/.vim\/plugin and NERD_tree.txt in ~\/.vim\/doc.\r\n\r\n\r\n\r\nRun :helptags.\r\n\r\nGo :help NERD_tree.txt for the help page.\r\n\r\n","first_name":"Marty","6":"Marty","last_name":"Grenfell","7":"Grenfell","releases":[{"0":"1658","vim_version":"7.3","1":"7.3","script_version":"5.0.0","2":"5.0.0","version_comment":"- Refactor the code significantly:\r\n    * Break the classes out into their own files.\r\n    * Make the majority of the code OO - previously large parts were\r\n      effectively a tangle of \"global\" methods.\r\n- Add an API to assign flags to nodes. This allows VCS plugins like\r\n  https:\/\/github.com\/Xuyuanp\/nerdtree-git-plugin to exist. Thanks to\r\n  Xuyuanp for helping design\/test\/build said API.\r\n- add 'scope' argument to the key map API see :help NERDTreeAddKeyMap()\r\n- add magic [[dir]] and [[file]] flags to NERDTreeIgnore\r\n- add support for custom path filters. See :help NERDTreeAddPathFilter()\r\n- add path listener API. See :help NERDTreePathListenerAPI.\r\n- expand the fs menu functionality to list file properties (PhilRunninger,\r\n  apbarrero, JESii)\r\n- make bookmarks work with `~` home shortcuts (hiberabyss)\r\n- show OSX specific fsmenu options in regular vim on mac (evindor)\r\n- make dir arrow icons configurable (PickRelated)\r\n- optimise node sorting performance when opening large dirs (vtsang)\r\n- make the root note render prettier by truncating it at a path slash (gcmt)\r\n- remove NERDChristmasTree option - its always christmas now\r\n- add \"cascade\" open and closing for dirs containing only another single\r\n  dir. See :help NERDTreeCascadeOpenSingleChildDir (pendulm)\r\n\r\nMany other fixes, doc updates and contributions from:\r\nactionshrimp\r\nSchDen\r\negalpin\r\ncperl82 - many small fixes\r\ntoiffel\r\nWoLpH\r\nhandcraftedbits\r\ndevmanhinton\r\nxiaodili\r\nzhangoose\r\ngastropoda\r\nmixvin\r\nalvan\r\nlucascaton\r\nkelaban\r\nshanesmith\r\nstaeff\r\npendulm\r\nstephenprater\r\nfranksort\r\nagrussellknives\r\nAndrewRadev\r\nTwinside\r\n","3":"- Refactor the code significantly:\r\n    * Break the classes out into their own files.\r\n    * Make the majority of the code OO - previously large parts were\r\n      effectively a tangle of \"global\" methods.\r\n- Add an API to assign flags to nodes. This allows VCS plugins like\r\n  https:\/\/github.com\/Xuyuanp\/nerdtree-git-plugin to exist. Thanks to\r\n  Xuyuanp for helping design\/test\/build said API.\r\n- add 'scope' argument to the key map API see :help NERDTreeAddKeyMap()\r\n- add magic [[dir]] and [[file]] flags to NERDTreeIgnore\r\n- add support for custom path filters. See :help NERDTreeAddPathFilter()\r\n- add path listener API. See :help NERDTreePathListenerAPI.\r\n- expand the fs menu functionality to list file properties (PhilRunninger,\r\n  apbarrero, JESii)\r\n- make bookmarks work with `~` home shortcuts (hiberabyss)\r\n- show OSX specific fsmenu options in regular vim on mac (evindor)\r\n- make dir arrow icons configurable (PickRelated)\r\n- optimise node sorting performance when opening large dirs (vtsang)\r\n- make the root note render prettier by truncating it at a path slash (gcmt)\r\n- remove NERDChristmasTree option - its always christmas now\r\n- add \"cascade\" open and closing for dirs containing only another single\r\n  dir. See :help NERDTreeCascadeOpenSingleChildDir (pendulm)\r\n\r\nMany other fixes, doc updates and contributions from:\r\nactionshrimp\r\nSchDen\r\negalpin\r\ncperl82 - many small fixes\r\ntoiffel\r\nWoLpH\r\nhandcraftedbits\r\ndevmanhinton\r\nxiaodili\r\nzhangoose\r\ngastropoda\r\nmixvin\r\nalvan\r\nlucascaton\r\nkelaban\r\nshanesmith\r\nstaeff\r\npendulm\r\nstephenprater\r\nfranksort\r\nagrussellknives\r\nAndrewRadev\r\nTwinside\r\n","package":"NERD_tree.zip","4":"NERD_tree.zip","src_id":"23731","5":"23731","creation_date":"1447434140","6":"1447434140"},{"0":"1658","vim_version":"7.0","1":"7.0","script_version":"4.2.0","2":"4.2.0","version_comment":"* Add NERDTreeDirArrows option to make the UI use pretty arrow chars instead of the old +~| chars to define the tree structure (sickill)\r\n* shift the syntax highlighting out into its own syntax file (gnap) * add some mac specific options to the filesystem menu - for macvim only (andersonfreitas)\r\n* Add NERDTreeMinimalUI option to remove some non functional parts of the nerdtree ui (camthompson)\r\n* tweak the behaviour of :NERDTreeFind - see :help :NERDTreeFind for the new behaviour (benjamingeiger)\r\n* if no name is given to :Bookmark, make it default to the name of the target file\/dir (minyoung)\r\n* use 'file' completion when doing copying, create, and move operations (EvanDotPro)\r\n* lots of misc bug fixes (paddyoloughlin, sdewald, camthompson, Vitaly Bogdanov, AndrewRadev, mathias, scottstvnsn, kml, wycats, me RAWR!)\r\n","3":"* Add NERDTreeDirArrows option to make the UI use pretty arrow chars instead of the old +~| chars to define the tree structure (sickill)\r\n* shift the syntax highlighting out into its own syntax file (gnap) * add some mac specific options to the filesystem menu - for macvim only (andersonfreitas)\r\n* Add NERDTreeMinimalUI option to remove some non functional parts of the nerdtree ui (camthompson)\r\n* tweak the behaviour of :NERDTreeFind - see :help :NERDTreeFind for the new behaviour (benjamingeiger)\r\n* if no name is given to :Bookmark, make it default to the name of the target file\/dir (minyoung)\r\n* use 'file' completion when doing copying, create, and move operations (EvanDotPro)\r\n* lots of misc bug fixes (paddyoloughlin, sdewald, camthompson, Vitaly Bogdanov, AndrewRadev, mathias, scottstvnsn, kml, wycats, me RAWR!)\r\n","package":"nerdtree.zip","4":"nerdtree.zip","src_id":"17123","5":"17123","creation_date":"1325078449","6":"1325078449"},{"0":"1658","vim_version":"7.0","1":"7.0","script_version":"4.1.0","2":"4.1.0","version_comment":"features:\r\n- add NERDTreeFind to reveal the node for the current buffer in\r\n  the tree, see |NERDTreeFind|. This effectively merges the\r\n  FindInNERDTree plugin (by Doug McInnes) into the script.\r\n- make NERDTreeQuitOnOpen apply to the t\/T keymaps too.\r\n  Thanks to Stefan Ritter and R\u00c3\u00a9mi Pr\u00c3\u00a9vost.\r\n- truncate the root node if wider than the tree window.\r\n  Thanks to Victor Gonzalez.\r\n\r\nbugfixes:\r\n- really fix window state restoring\r\n- fix some win32 path escaping issues. Thanks to Stephan\r\n  Baumeister, Ricky, jfilip1024, and Chris Chambers\r\n","3":"features:\r\n- add NERDTreeFind to reveal the node for the current buffer in\r\n  the tree, see |NERDTreeFind|. This effectively merges the\r\n  FindInNERDTree plugin (by Doug McInnes) into the script.\r\n- make NERDTreeQuitOnOpen apply to the t\/T keymaps too.\r\n  Thanks to Stefan Ritter and R\u00c3\u00a9mi Pr\u00c3\u00a9vost.\r\n- truncate the root node if wider than the tree window.\r\n  Thanks to Victor Gonzalez.\r\n\r\nbugfixes:\r\n- really fix window state restoring\r\n- fix some win32 path escaping issues. Thanks to Stephan\r\n  Baumeister, Ricky, jfilip1024, and Chris Chambers\r\n","package":"NERD_tree.zip","4":"NERD_tree.zip","src_id":"11834","5":"11834","creation_date":"1259659518","6":"1259659518"},{"0":"1658","vim_version":"7.0","1":"7.0","script_version":"4.0.0","2":"4.0.0","version_comment":"- add a new programmable menu system (see :help\r\n  NERDTreeMenu).\r\n- add new APIs to add menus\/menu-items to the menu system as\r\n  well as custom key mappings to the NERD tree buffer (see\r\n  :help NERDTreeAPI).\r\n- removed the old API functions\r\n- added a mapping to maximize\/restore the size of nerd tree\r\n  window, thanks to Guillaume Duranceau for the patch. See\r\n  :help NERDTree-A for details.\r\n\r\n- fix a bug where secondary nerd trees (netrw hijacked\r\n  trees) and NERDTreeQuitOnOpen didnt play nicely, thanks to\r\n  Curtis Harvey.\r\n- fix a bug where the script ignored directories whose name\r\n  ended in a dot, thanks to Aggelos Orfanakos for the patch.\r\n- fix a bug when using the x mapping on the tree root,\r\n  thanks to Bryan Venteicher for the patch.\r\n- fix a bug where the cursor position\/window size of the\r\n  nerd tree buffer wasnt being stored on closing the window,\r\n  thanks to Richard Hart.\r\n- fix a bug where NERDTreeMirror would mirror the wrong tree\r\n","3":"- add a new programmable menu system (see :help\r\n  NERDTreeMenu).\r\n- add new APIs to add menus\/menu-items to the menu system as\r\n  well as custom key mappings to the NERD tree buffer (see\r\n  :help NERDTreeAPI).\r\n- removed the old API functions\r\n- added a mapping to maximize\/restore the size of nerd tree\r\n  window, thanks to Guillaume Duranceau for the patch. See\r\n  :help NERDTree-A for details.\r\n\r\n- fix a bug where secondary nerd trees (netrw hijacked\r\n  trees) and NERDTreeQuitOnOpen didnt play nicely, thanks to\r\n  Curtis Harvey.\r\n- fix a bug where the script ignored directories whose name\r\n  ended in a dot, thanks to Aggelos Orfanakos for the patch.\r\n- fix a bug when using the x mapping on the tree root,\r\n  thanks to Bryan Venteicher for the patch.\r\n- fix a bug where the cursor position\/window size of the\r\n  nerd tree buffer wasnt being stored on closing the window,\r\n  thanks to Richard Hart.\r\n- fix a bug where NERDTreeMirror would mirror the wrong tree\r\n","package":"NERD_tree.zip","4":"NERD_tree.zip","src_id":"11500","5":"11500","creation_date":"1255067803","6":"1255067803"},{"0":"1658","vim_version":"7.0","1":"7.0","script_version":"3.1.1","2":"3.1.1","version_comment":"- fix a bug where a non-listed no-name buffer was getting created every\r\n  time the tree window was created, thanks to Derek Wyatt and owen1\r\n- make <CR> behave the same as the 'o' mapping\r\n- some helptag fixes in the doc, thanks strull\r\n- fix an error when using :set nohidden and opening a file where the previous\r\n  buf was modified. Thanks iElectric\r\n- other minor fixes\r\n","3":"- fix a bug where a non-listed no-name buffer was getting created every\r\n  time the tree window was created, thanks to Derek Wyatt and owen1\r\n- make <CR> behave the same as the 'o' mapping\r\n- some helptag fixes in the doc, thanks strull\r\n- fix an error when using :set nohidden and opening a file where the previous\r\n  buf was modified. Thanks iElectric\r\n- other minor fixes\r\n","package":"NERD_tree.zip","4":"NERD_tree.zip","src_id":"10767","5":"10767","creation_date":"1244367575","6":"1244367575"},{"0":"1658","vim_version":"7.0","1":"7.0","script_version":"3.1.0","2":"3.1.0","version_comment":"New features:\r\n- add mappings to open files in a vsplit, see :help\r\n  NERDTree-s and :help NERDTree-gs\r\n- make the statusline for the nerd tree window default to\r\n  something hopefully more useful. See :help\r\n  'NERDTreeStatusline'\r\nBugfixes:\r\n- make the hijack netrw functionality work when vim is\r\n  started with \"vim <some dir>\" (thanks to Alf Mikula for\r\n  the patch).\r\n- fix a bug where the CWD wasnt being changed for some\r\n  operations even when NERDTreeChDirMode==2 (thanks to \r\n  Lucas S. Buchala)\r\n- add -bar to all the nerd tree :commands so they can chain\r\n  with other :commands (thanks to tpope)\r\n- fix bugs when ignorecase was set (thanks to nach)\r\n- fix a bug with the relative path code (thanks to nach)\r\n- fix a bug where doing a :cd would cause :NERDTreeToggle to\r\n  fail (thanks nach)\r\n","3":"New features:\r\n- add mappings to open files in a vsplit, see :help\r\n  NERDTree-s and :help NERDTree-gs\r\n- make the statusline for the nerd tree window default to\r\n  something hopefully more useful. See :help\r\n  'NERDTreeStatusline'\r\nBugfixes:\r\n- make the hijack netrw functionality work when vim is\r\n  started with \"vim <some dir>\" (thanks to Alf Mikula for\r\n  the patch).\r\n- fix a bug where the CWD wasnt being changed for some\r\n  operations even when NERDTreeChDirMode==2 (thanks to \r\n  Lucas S. Buchala)\r\n- add -bar to all the nerd tree :commands so they can chain\r\n  with other :commands (thanks to tpope)\r\n- fix bugs when ignorecase was set (thanks to nach)\r\n- fix a bug with the relative path code (thanks to nach)\r\n- fix a bug where doing a :cd would cause :NERDTreeToggle to\r\n  fail (thanks nach)\r\n","package":"NERD_tree.zip","4":"NERD_tree.zip","src_id":"9870","5":"9870","creation_date":"1233036413","6":"1233036413"},{"0":"1658","vim_version":"7.0","1":"7.0","script_version":"3.0.1","2":"3.0.1","version_comment":"Bugfixes:\r\n- fix bugs with :NERDTreeToggle and :NERDTreeMirror when\r\n  'hidden was not set\r\n- fix a bug where :NERDTree <path> would fail if <path> was\r\n  relative and didnt start with a .\/ or ..\/  Thanks to \r\n  James Kanze.\r\n- make the q mapping work with secondary (:e <dir>  style)\r\n  trees, thanks to jamessan\r\n- fix a bunch of small bugs with secondary trees\r\n\r\nMore insane refactoring.\r\n","3":"Bugfixes:\r\n- fix bugs with :NERDTreeToggle and :NERDTreeMirror when\r\n  'hidden was not set\r\n- fix a bug where :NERDTree <path> would fail if <path> was\r\n  relative and didnt start with a .\/ or ..\/  Thanks to \r\n  James Kanze.\r\n- make the q mapping work with secondary (:e <dir>  style)\r\n  trees, thanks to jamessan\r\n- fix a bunch of small bugs with secondary trees\r\n\r\nMore insane refactoring.\r\n","package":"NERD_tree.zip","4":"NERD_tree.zip","src_id":"9804","5":"9804","creation_date":"1231757100","6":"1231757100"},{"0":"1658","vim_version":"7.0","1":"7.0","script_version":"3.0.0","2":"3.0.0","version_comment":"- hijack netrw so that doing an :edit <directory>  will put\r\n  a NERD tree in the window rather than a netrw browser. See\r\n  :help 'NERDTreeHijackNetrw'\r\n- allow sharing of trees across tabs, see :help :NERDTreeMirror\r\n- remove \"top\" and \"bottom\" as valid settings for NERDTreeWinPos\r\n- change the '<tab>' mapping to 'i'\r\n- change the 'H' mapping to 'I' (capital i)\r\n- lots of refactoring\r\n","3":"- hijack netrw so that doing an :edit <directory>  will put\r\n  a NERD tree in the window rather than a netrw browser. See\r\n  :help 'NERDTreeHijackNetrw'\r\n- allow sharing of trees across tabs, see :help :NERDTreeMirror\r\n- remove \"top\" and \"bottom\" as valid settings for NERDTreeWinPos\r\n- change the '<tab>' mapping to 'i'\r\n- change the 'H' mapping to 'I' (capital i)\r\n- lots of refactoring\r\n","package":"NERD_tree.zip","4":"NERD_tree.zip","src_id":"9744","5":"9744","creation_date":"1230857173","6":"1230857173"},{"0":"1658","vim_version":"7.0","1":"7.0","script_version":"2.14.3","2":"2.14.3","version_comment":"Thanks to tpope for the following:\r\n- use relative paths when doing edit commands if possible\r\n  (useful if you have %f on your statusline for example)\r\n- allow relative paths for :NERDTree commands, eg \r\n  \":NERDTree ..\/foo\"\r\n- fix a bug where the script used the directory of the\r\n  current buffer instead of vims cwd for the :NERDTree\r\n  command\r\n- bugfix for read only node highlighting","3":"Thanks to tpope for the following:\r\n- use relative paths when doing edit commands if possible\r\n  (useful if you have %f on your statusline for example)\r\n- allow relative paths for :NERDTree commands, eg \r\n  \":NERDTree ..\/foo\"\r\n- fix a bug where the script used the directory of the\r\n  current buffer instead of vims cwd for the :NERDTree\r\n  command\r\n- bugfix for read only node highlighting","package":"NERD_tree.zip","4":"NERD_tree.zip","src_id":"9657","5":"9657","creation_date":"1229121013","6":"1229121013"},{"0":"1658","vim_version":"7.0","1":"7.0","script_version":"2.14.2","2":"2.14.2","version_comment":"- compatibility bugfix for older versions of vim, thanks to\r\n  knekk for helping me track it down and to Sean Chou.\r\n- when opening a file (with 'o' or double click) dont split\r\n  the window unless we absolutely have to. This should make\r\n  the script work better with other explorer plugins. Thanks\r\n  to Ryan Penn, Simon Peter Nicholls and Michael\r\n- fix a bug where directories starting with a '+' char could\r\n  not be opened.  Thanks to Tomasz Chomiuk.\r\n- fix a bug where closing vim with :qa with a tree open in\r\n  another tab would break, thanks to Denis Pokataev.\r\n","3":"- compatibility bugfix for older versions of vim, thanks to\r\n  knekk for helping me track it down and to Sean Chou.\r\n- when opening a file (with 'o' or double click) dont split\r\n  the window unless we absolutely have to. This should make\r\n  the script work better with other explorer plugins. Thanks\r\n  to Ryan Penn, Simon Peter Nicholls and Michael\r\n- fix a bug where directories starting with a '+' char could\r\n  not be opened.  Thanks to Tomasz Chomiuk.\r\n- fix a bug where closing vim with :qa with a tree open in\r\n  another tab would break, thanks to Denis Pokataev.\r\n","package":"NERD_tree.zip","4":"NERD_tree.zip","src_id":"9413","5":"9413","creation_date":"1225265073","6":"1225265073"},{"0":"1658","vim_version":"7.0","1":"7.0","script_version":"2.14.1","2":"2.14.1","version_comment":"- dont clobber &cpo. Thanks to godlygeek for the bug report\r\n- a bunch of other minor fixes and refactoring\r\n","3":"- dont clobber &cpo. Thanks to godlygeek for the bug report\r\n- a bunch of other minor fixes and refactoring\r\n","package":"NERD_tree.zip","4":"NERD_tree.zip","src_id":"9331","5":"9331","creation_date":"1223689380","6":"1223689380"},{"0":"1658","vim_version":"7.0","1":"7.0","script_version":"2.14.0","2":"2.14.0","version_comment":"- fix a bug where the <c-w>o mapping  would cause the tree window to be\r\n  incorrectly sized when reopened.\r\n- add keymapping to delete bookmarks from the bookmarks table, see :help\r\n  NERDTree-D\r\n- lots of refactoring\r\n","3":"- fix a bug where the <c-w>o mapping  would cause the tree window to be\r\n  incorrectly sized when reopened.\r\n- add keymapping to delete bookmarks from the bookmarks table, see :help\r\n  NERDTree-D\r\n- lots of refactoring\r\n","package":"NERD_tree.zip","4":"NERD_tree.zip","src_id":"9228","5":"9228","creation_date":"1220723183","6":"1220723183"},{"0":"1658","vim_version":"7.0","1":"7.0","script_version":"2.13.0","2":"2.13.0","version_comment":"- make NERDTreeChDir option default to 0 (i.e. never change\r\n  vims current working dir by default)\r\n- when moving\/deleting nodes with the filesystem menu,\r\n  move\/delete any associated bookmarks\r\n- make the t\/T on directory nodes open a fresh NERD tree for\r\n  the selected dir in a new tab, rather than a netrw.\r\n- place the cursor at the top of the bookmarks table when\r\n  opening it with B\r\n- make NERDTreeQuitOnOpen option work with the g<tab> and go\r\n  mappings, thanks to Maxim Kim for the bug report\r\n- change how invalid bookmarks are handled. Now they are not\r\n  deleted. If a bookmark is malformed (in the bookmarks\r\n  file) or points to an invalid\/nonexisting location then\r\n  print an error and place the offending bookmarks at the\r\n  bottom of the bookmarks file. See :help\r\n  |NERDTreeInvalidBookmarks| for info. Thanks to Zhang\r\n  Shuhan for the suggestion and the testing.\r\n- fix a bug with the 'o' mapping that occurred when opening\r\n  a new buffer for a file whose name was a substring of an\r\n  already open file. Thanks to Charlton Wang for the report.\r\n- stop the script from going into an infinite loop when it\r\n  tries to cache a named pipe. Thanks to Charlton Wang for\r\n  the report.\r\n","3":"- make NERDTreeChDir option default to 0 (i.e. never change\r\n  vims current working dir by default)\r\n- when moving\/deleting nodes with the filesystem menu,\r\n  move\/delete any associated bookmarks\r\n- make the t\/T on directory nodes open a fresh NERD tree for\r\n  the selected dir in a new tab, rather than a netrw.\r\n- place the cursor at the top of the bookmarks table when\r\n  opening it with B\r\n- make NERDTreeQuitOnOpen option work with the g<tab> and go\r\n  mappings, thanks to Maxim Kim for the bug report\r\n- change how invalid bookmarks are handled. Now they are not\r\n  deleted. If a bookmark is malformed (in the bookmarks\r\n  file) or points to an invalid\/nonexisting location then\r\n  print an error and place the offending bookmarks at the\r\n  bottom of the bookmarks file. See :help\r\n  |NERDTreeInvalidBookmarks| for info. Thanks to Zhang\r\n  Shuhan for the suggestion and the testing.\r\n- fix a bug with the 'o' mapping that occurred when opening\r\n  a new buffer for a file whose name was a substring of an\r\n  already open file. Thanks to Charlton Wang for the report.\r\n- stop the script from going into an infinite loop when it\r\n  tries to cache a named pipe. Thanks to Charlton Wang for\r\n  the report.\r\n","package":"NERD_tree.zip","4":"NERD_tree.zip","src_id":"8976","5":"8976","creation_date":"1216524999","6":"1216524999"},{"0":"1658","vim_version":"6.0","1":"6.0","script_version":"2.12.0","2":"2.12.0","version_comment":"- added a UI for bookmarks. See :help NERDTreeBookmarkTable for details.\r\n  Thanks to Zhang Shuhan for testing and bug reports.\r\n- relaxed the restrictions on bookmark names, now the only restriction is\r\n  that they cant contain spaces. This allows for e.g. Chinese bookmark\r\n  names. Thanks to Zhang Shuhan for the suggestion.\r\n- combined the NERDTreeWinPos and NERDTreeSplitVertical options. See :help\r\n  NERDTreeWinPos.\r\n- applied a patch from Matan Nassau to add the NERDTreeQuitOnOpen option\r\n  which closes the tree window after opening a file. See :help\r\n  NERDTreeQuitOnOpen.\r\n- optimised the nerd tree rendering. Now it takes just over 1\/3 of the time\r\n  it previously took to render.\r\n- now the tree filter mappings toggle the filters \"per tree\" rather than\r\n  globally. The global filter variables are used to set the initial filter\r\n  settings for each new NERD tree.\r\n- fix to window resizing when opening a file when NERD tree is the only\r\n  window open\r\n- other fixes\r\n","3":"- added a UI for bookmarks. See :help NERDTreeBookmarkTable for details.\r\n  Thanks to Zhang Shuhan for testing and bug reports.\r\n- relaxed the restrictions on bookmark names, now the only restriction is\r\n  that they cant contain spaces. This allows for e.g. Chinese bookmark\r\n  names. Thanks to Zhang Shuhan for the suggestion.\r\n- combined the NERDTreeWinPos and NERDTreeSplitVertical options. See :help\r\n  NERDTreeWinPos.\r\n- applied a patch from Matan Nassau to add the NERDTreeQuitOnOpen option\r\n  which closes the tree window after opening a file. See :help\r\n  NERDTreeQuitOnOpen.\r\n- optimised the nerd tree rendering. Now it takes just over 1\/3 of the time\r\n  it previously took to render.\r\n- now the tree filter mappings toggle the filters \"per tree\" rather than\r\n  globally. The global filter variables are used to set the initial filter\r\n  settings for each new NERD tree.\r\n- fix to window resizing when opening a file when NERD tree is the only\r\n  window open\r\n- other fixes\r\n","package":"NERD_tree.zip","4":"NERD_tree.zip","src_id":"8886","5":"8886","creation_date":"1215192299","6":"1215192299"},{"0":"1658","vim_version":"7.0","1":"7.0","script_version":"2.11.0","2":"2.11.0","version_comment":"- changes to the 'o' mapping when opening files:\r\n  - dont clobber \"special\" windows (eg taglist\/quickfix\/etc). This should\r\n    make the NERD tree play nicer with other explorer plugins. Thanks to\r\n    Yuan Jiang for the suggestion.\r\n  - if the file is already open in the current tab, just move the cursor\r\n    to that window\r\n- highlight executable files, made some slight changes to other\r\n  highlighting\r\n- if the user resizes the tree window, keep that new size. Dont reset to\r\n  the default during the <tab> mapping, or :NERDTreeToggle command. Only\r\n  reset the size if a fresh tree is started with :NERDTree.\r\n- remove the \"magic\" functionality from the <c-j>\/<c-k> mappings (it was\r\n  more confusing than helpful)\r\n- other minor fixes\r\n","3":"- changes to the 'o' mapping when opening files:\r\n  - dont clobber \"special\" windows (eg taglist\/quickfix\/etc). This should\r\n    make the NERD tree play nicer with other explorer plugins. Thanks to\r\n    Yuan Jiang for the suggestion.\r\n  - if the file is already open in the current tab, just move the cursor\r\n    to that window\r\n- highlight executable files, made some slight changes to other\r\n  highlighting\r\n- if the user resizes the tree window, keep that new size. Dont reset to\r\n  the default during the <tab> mapping, or :NERDTreeToggle command. Only\r\n  reset the size if a fresh tree is started with :NERDTree.\r\n- remove the \"magic\" functionality from the <c-j>\/<c-k> mappings (it was\r\n  more confusing than helpful)\r\n- other minor fixes\r\n","package":"NERD_tree.zip","4":"NERD_tree.zip","src_id":"8837","5":"8837","creation_date":"1214185615","6":"1214185615"},{"0":"1658","vim_version":"7.0","1":"7.0","script_version":"2.10.0","2":"2.10.0","version_comment":"- added bookmarks, see :help NERDTreeBookmarkCommands for details. Thanks to\r\n  Piotr Czachur for all his testing and suggestions.\r\n- fixed screen jumping bug with when &scrolloff != 0\r\n- fixed some bugs with copying nodes\r\n- other random fixes\r\n- changed license to wtfpl\r\n","3":"- added bookmarks, see :help NERDTreeBookmarkCommands for details. Thanks to\r\n  Piotr Czachur for all his testing and suggestions.\r\n- fixed screen jumping bug with when &scrolloff != 0\r\n- fixed some bugs with copying nodes\r\n- other random fixes\r\n- changed license to wtfpl\r\n","package":"NERD_tree.zip","4":"NERD_tree.zip","src_id":"8815","5":"8815","creation_date":"1213675245","6":"1213675245"},{"0":"1658","vim_version":"7.0","1":"7.0","script_version":"2.9.0","2":"2.9.0","version_comment":"- path handling improvements, thanks to Zhang Shuhan for heaps of\r\n  testing\/bug reports\r\n    * improved how paths are stored, now the script will no longer get\r\n      confused about drives on MF Windows\r\n    * made the script way better at handling paths with strange characters\r\n      in them (eg '$@; etc)\r\n- applied a patch from Cory Echols\r\n    * add the command :NERDTreeClose to close the tree for the current tab\r\n    * set the filetype for the NERD tree buffer to \"nerdtree\"","3":"- path handling improvements, thanks to Zhang Shuhan for heaps of\r\n  testing\/bug reports\r\n    * improved how paths are stored, now the script will no longer get\r\n      confused about drives on MF Windows\r\n    * made the script way better at handling paths with strange characters\r\n      in them (eg '$@; etc)\r\n- applied a patch from Cory Echols\r\n    * add the command :NERDTreeClose to close the tree for the current tab\r\n    * set the filetype for the NERD tree buffer to \"nerdtree\"","package":"NERD_tree.zip","4":"NERD_tree.zip","src_id":"8701","5":"8701","creation_date":"1210973415","6":"1210973415"},{"0":"1658","vim_version":"7.0","1":"7.0","script_version":"2.8.0","2":"2.8.0","version_comment":"added an option to enable\/disable line numbers in the NERD tree window. See :help NERDTreeShowLineNumbers for details. Thanks to Olivier Yiptong for the email.","3":"added an option to enable\/disable line numbers in the NERD tree window. See :help NERDTreeShowLineNumbers for details. Thanks to Olivier Yiptong for the email.","package":"NERD_tree.zip","4":"NERD_tree.zip","src_id":"8511","5":"8511","creation_date":"1206916217","6":"1206916217"},{"0":"1658","vim_version":"7.0","1":"7.0","script_version":"2.7.1","2":"2.7.1","version_comment":"- Changed the keys for the filesystem menu to be mnemonic rather than arbitrary integers\r\n- Documented the copying functionality in the filesystem menu\r\n","3":"- Changed the keys for the filesystem menu to be mnemonic rather than arbitrary integers\r\n- Documented the copying functionality in the filesystem menu\r\n","package":"NERD_tree.zip","4":"NERD_tree.zip","src_id":"8160","5":"8160","creation_date":"1200620661","6":"1200620661"},{"0":"1658","vim_version":"7.0","1":"7.0","script_version":"2.7.0","2":"2.7.0","version_comment":"- Bug fix: Now when you have the tree on the right and you open it with multiple windows stacked, it will take up the full height of the vim window. \r\n- Now line numbers always turned off in the tree by default\r\n- Implemented copying of nodes (via the filesystem menu) for *nix\/macosx\r\n- took the help doc out of the script and repackaged the whole thing as a zip\r\n","3":"- Bug fix: Now when you have the tree on the right and you open it with multiple windows stacked, it will take up the full height of the vim window. \r\n- Now line numbers always turned off in the tree by default\r\n- Implemented copying of nodes (via the filesystem menu) for *nix\/macosx\r\n- took the help doc out of the script and repackaged the whole thing as a zip\r\n","package":"NERD_tree.zip","4":"NERD_tree.zip","src_id":"7863","5":"7863","creation_date":"1194023107","6":"1194023107"},{"0":"1658","vim_version":"7.0","1":"7.0","script_version":"2.6.2","2":"2.6.2","version_comment":"Now when you try to open a file node into a window that is modified, the window is not split if the &hidden option is set. Thanks to  Niels Aan de Brugh for this suggestion.\r\n","3":"Now when you try to open a file node into a window that is modified, the window is not split if the &hidden option is set. Thanks to  Niels Aan de Brugh for this suggestion.\r\n","package":"NERD_tree.vim","4":"NERD_tree.vim","src_id":"7554","5":"7554","creation_date":"1188060671","6":"1188060671"},{"0":"1658","vim_version":"7.0","1":"7.0","script_version":"2.6.1","2":"2.6.1","version_comment":"- Fixed a stupid (but major) bug with the <tab> mapping. Thanks to Zhang Weiwu for\r\n  emailing me.\r\n","3":"- Fixed a stupid (but major) bug with the <tab> mapping. Thanks to Zhang Weiwu for\r\n  emailing me.\r\n","package":"NERD_tree.vim","4":"NERD_tree.vim","src_id":"7330","5":"7330","creation_date":"1183851449","6":"1183851449"},{"0":"1658","vim_version":"7.0","1":"7.0","script_version":"2.6.0","2":"2.6.0","version_comment":"- Extended the behaviour of <c-j\/k>. Now if the cursor is on a file node\r\n  and you use <c-j\/k> the cursor will jump to its PARENTS next\/previous\r\n  sibling. Go :help NERDTree-c-j and :help NERDTree-c-k for info.\r\n- Extended the behaviour of the J\/K mappings. Now if the cursor is on the\r\n  last child of a node and you push J\/K it will jump down to the last child\r\n  of the next\/prev of its parents siblings that is open and has children.\r\n  Go :help NERDTree-J and :help NERDTree-K for info.\r\n- The goal of these changes is to make tree navigation faster.\r\n- Reorganised the help page a bit.\r\n- Removed the E mapping.\r\n- bugfixes\r\n","3":"- Extended the behaviour of <c-j\/k>. Now if the cursor is on a file node\r\n  and you use <c-j\/k> the cursor will jump to its PARENTS next\/previous\r\n  sibling. Go :help NERDTree-c-j and :help NERDTree-c-k for info.\r\n- Extended the behaviour of the J\/K mappings. Now if the cursor is on the\r\n  last child of a node and you push J\/K it will jump down to the last child\r\n  of the next\/prev of its parents siblings that is open and has children.\r\n  Go :help NERDTree-J and :help NERDTree-K for info.\r\n- The goal of these changes is to make tree navigation faster.\r\n- Reorganised the help page a bit.\r\n- Removed the E mapping.\r\n- bugfixes\r\n","package":"NERD_tree.vim","4":"NERD_tree.vim","src_id":"7329","5":"7329","creation_date":"1183745944","6":"1183745944"},{"0":"1658","vim_version":"7.0","1":"7.0","script_version":"2.5.0","2":"2.5.0","version_comment":"- Added an option to enforce case sensitivity when sorting tree nodes.  Read :help NERDTreeCaseSensitiveSort for details.  (thanks to Michael Madsen for emailing me about this). Case sensitivity defaults to off.\r\n- Made the script echo a \"please wait\" style message when opening large directories. Thanks to AOYAMA Shotaro for this suggestion.\r\n- Added 2 public functions that can be used to retrieve the treenode and path that the cursor is on. Read :help NERDTreePublicFunctions for details (thanks again to AOYAMA Shotaro for the idea :).\r\n- added 2 new mappings for file nodes: \"g<tab>\" and \"go\". These are the same as the \"<tab>\" and \"o\" maps except that the cursor stays in the NERDTree. Note: these maps are slaved to the o and <tab> mappings, so if eg you remap \"<tab>\" to \"i\" then the \"g<tab>\" map will also be changed to \"gi\".\r\n- Renamed many of the help tags to be simpler.\r\n- Simplified the ascii \"graphics\" for the filesystem menu\r\n- Fixed bugs.\r\n- Probably created bugs.\r\n- Refactoring.\r\n","3":"- Added an option to enforce case sensitivity when sorting tree nodes.  Read :help NERDTreeCaseSensitiveSort for details.  (thanks to Michael Madsen for emailing me about this). Case sensitivity defaults to off.\r\n- Made the script echo a \"please wait\" style message when opening large directories. Thanks to AOYAMA Shotaro for this suggestion.\r\n- Added 2 public functions that can be used to retrieve the treenode and path that the cursor is on. Read :help NERDTreePublicFunctions for details (thanks again to AOYAMA Shotaro for the idea :).\r\n- added 2 new mappings for file nodes: \"g<tab>\" and \"go\". These are the same as the \"<tab>\" and \"o\" maps except that the cursor stays in the NERDTree. Note: these maps are slaved to the o and <tab> mappings, so if eg you remap \"<tab>\" to \"i\" then the \"g<tab>\" map will also be changed to \"gi\".\r\n- Renamed many of the help tags to be simpler.\r\n- Simplified the ascii \"graphics\" for the filesystem menu\r\n- Fixed bugs.\r\n- Probably created bugs.\r\n- Refactoring.\r\n","package":"NERD_tree.vim","4":"NERD_tree.vim","src_id":"7303","5":"7303","creation_date":"1182742808","6":"1182742808"},{"0":"1658","vim_version":"7.0","1":"7.0","script_version":"2.4.0","2":"2.4.0","version_comment":"- Added the P mapping to jump to the tree root.\r\n- Added window centering functionality that can be triggered when doing\r\n  using any of the tree nav mappings. Essentially, if the cursor comes\r\n  within a certain distance of the top\/bottom of the window then a zz is\r\n  done in the window. Two related options were added: NERDTreeAutoCenter\r\n  to turn this functionality on\/off, and NERDTreeAutoCenterThreshold to\r\n  control how close the cursor has to be to the window edge to trigger the\r\n  centering. See |NERDTreeAutoCenter| for info.\r\n","3":"- Added the P mapping to jump to the tree root.\r\n- Added window centering functionality that can be triggered when doing\r\n  using any of the tree nav mappings. Essentially, if the cursor comes\r\n  within a certain distance of the top\/bottom of the window then a zz is\r\n  done in the window. Two related options were added: NERDTreeAutoCenter\r\n  to turn this functionality on\/off, and NERDTreeAutoCenterThreshold to\r\n  control how close the cursor has to be to the window edge to trigger the\r\n  centering. See |NERDTreeAutoCenter| for info.\r\n","package":"NERD_tree.vim","4":"NERD_tree.vim","src_id":"7252","5":"7252","creation_date":"1181954473","6":"1181954473"},{"0":"1658","vim_version":"7.0","1":"7.0","script_version":"2.3.0","2":"2.3.0","version_comment":"- Tree navigation changes:\r\n  - Added J and K mappings to jump to last\/first child of the current dir.\r\n    Options to customise these mappings have also been added.\r\n  - Remapped the jump to next\/prev sibling commands to be <C-j> and <C-k> by\r\n    default.\r\n  These changes should hopefully make tree navigation mappings easier to\r\n  remember and use as the j and k keys are simply reused 3 times (twice\r\n  with modifier keys).\r\n\r\n- Made it so that, when any of the tree filters are toggled, the cursor\r\n  stays with the selected node (or goes to its parent\/grandparent\/... if\r\n  that node is no longer visible)\r\n- Fixed an error in the doc for the mouse mode option.\r\n- Made the quickhelp correctly display the current single\/double click\r\n  mappings for opening nodes as specified by the NERDTreeMouseMode option.\r\n- Fixed a bug where the script was spazzing after prompting you to delete\r\n  a modified buffer when using the filesystem menu.  - Refactoring\r\n","3":"- Tree navigation changes:\r\n  - Added J and K mappings to jump to last\/first child of the current dir.\r\n    Options to customise these mappings have also been added.\r\n  - Remapped the jump to next\/prev sibling commands to be <C-j> and <C-k> by\r\n    default.\r\n  These changes should hopefully make tree navigation mappings easier to\r\n  remember and use as the j and k keys are simply reused 3 times (twice\r\n  with modifier keys).\r\n\r\n- Made it so that, when any of the tree filters are toggled, the cursor\r\n  stays with the selected node (or goes to its parent\/grandparent\/... if\r\n  that node is no longer visible)\r\n- Fixed an error in the doc for the mouse mode option.\r\n- Made the quickhelp correctly display the current single\/double click\r\n  mappings for opening nodes as specified by the NERDTreeMouseMode option.\r\n- Fixed a bug where the script was spazzing after prompting you to delete\r\n  a modified buffer when using the filesystem menu.  - Refactoring\r\n","package":"NERD_tree.vim","4":"NERD_tree.vim","src_id":"7155","5":"7155","creation_date":"1179889837","6":"1179889837"},{"0":"1658","vim_version":"7.0","1":"7.0","script_version":"2.2.3","2":"2.2.3","version_comment":"- Fixed some minor typos in the doc.\r\n- Made some minor changes to the output of the 'Tree filtering mappings'\r\n  part of the quickhelp \r\n- Some internal refactoring\r\n","3":"- Fixed some minor typos in the doc.\r\n- Made some minor changes to the output of the 'Tree filtering mappings'\r\n  part of the quickhelp \r\n- Some internal refactoring\r\n","package":"NERD_tree.vim","4":"NERD_tree.vim","src_id":"7100","5":"7100","creation_date":"1179003055","6":"1179003055"},{"0":"1658","vim_version":"7.0","1":"7.0","script_version":"2.2.2","2":"2.2.2","version_comment":"Yet more bugfixes... doh","3":"Yet more bugfixes... doh","package":"NERD_tree.vim","4":"NERD_tree.vim","src_id":"7041","5":"7041","creation_date":"1177896365","6":"1177896365"},{"0":"1658","vim_version":"7.0","1":"7.0","script_version":"2.2.1","2":"2.2.1","version_comment":"- fixed a bug that was causing an exception when closing the nerd tree. Thanks\r\n  to Tim carey-smith and Yu Jun for pointing this out.\r\n","3":"- fixed a bug that was causing an exception when closing the nerd tree. Thanks\r\n  to Tim carey-smith and Yu Jun for pointing this out.\r\n","package":"NERD_tree.vim","4":"NERD_tree.vim","src_id":"7040","5":"7040","creation_date":"1177880212","6":"1177880212"},{"0":"1658","vim_version":"7.0","1":"7.0","script_version":"2.2.0","2":"2.2.0","version_comment":"- Now 'cursorline' is set in the NERD tree buffer by default. See :help\r\n  NERDTreeHighlightCursorline for how to disable it.\r\n","3":"- Now 'cursorline' is set in the NERD tree buffer by default. See :help\r\n  NERDTreeHighlightCursorline for how to disable it.\r\n","package":"NERD_tree.vim","4":"NERD_tree.vim","src_id":"7035","5":"7035","creation_date":"1177730204","6":"1177730204"},{"0":"1658","vim_version":"7.0","1":"7.0","script_version":"2.1.2","2":"2.1.2","version_comment":"- Stopped the script from clobbering the 1,2,3 .. 9 registers.\r\n- Made it \"silent!\"ly delete buffers when renaming\/deleting file nodes.\r\n- Minor correction to the doc\r\n- Fixed a bug when refreshing that was occurring when the node you\r\n  refreshed had been deleted externally.\r\n- Fixed a bug that was occurring when you open a file that is already open\r\n  and modified.\r\n","3":"- Stopped the script from clobbering the 1,2,3 .. 9 registers.\r\n- Made it \"silent!\"ly delete buffers when renaming\/deleting file nodes.\r\n- Minor correction to the doc\r\n- Fixed a bug when refreshing that was occurring when the node you\r\n  refreshed had been deleted externally.\r\n- Fixed a bug that was occurring when you open a file that is already open\r\n  and modified.\r\n","package":"NERD_tree.vim","4":"NERD_tree.vim","src_id":"7008","5":"7008","creation_date":"1177088512","6":"1177088512"},{"0":"1658","vim_version":"7.0","1":"7.0","script_version":"2.1.1","2":"2.1.1","version_comment":"- Added a bit more info about the buffers you are prompted to delete when\r\n  renaming\/deleting nodes from the filesystem menu that are already loaded\r\n  into buffers.\r\n- Refactoring and bugfixes\r\n","3":"- Added a bit more info about the buffers you are prompted to delete when\r\n  renaming\/deleting nodes from the filesystem menu that are already loaded\r\n  into buffers.\r\n- Refactoring and bugfixes\r\n","package":"NERD_tree.vim","4":"NERD_tree.vim","src_id":"6958","5":"6958","creation_date":"1175896200","6":"1175896200"},{"0":"1658","vim_version":"7.0","1":"7.0","script_version":"2.1.0","2":"2.1.0","version_comment":"- Added NERDTreeMouseMode option. If set to 1, then a double click is\r\n  required to activate all nodes, if set to 2 then a single click will\r\n  activate directory nodes, if set to 3 then a single click will activate\r\n  all nodes.\r\n- Now if you delete a file node and have it open in a buffer you are given\r\n  the option to delete that buffer as well. Similarly if you rename a file\r\n  you are given the option to delete any buffers containing the old file\r\n  (if any exist)\r\n- When you rename or create a node, the cursor is now put on the new node,\r\n  this makes it easy immediately edit  the new file.\r\n- Fixed a bug with the ! mapping that was occurring on windows with paths\r\n  containing spaces.\r\n- Made all the mappings customisable. See |NERD_tree-mappings| for\r\n  details. A side effect is that a lot of the \"double mappings\" have\r\n  disappeared. E.g 'o' is now the key that is used to activate a node,\r\n  <CR> is no longer mapped to the same.\r\n- Made the script echo warnings in some places rather than standard echos\r\n- Insane amounts of refactoring all over the place.\r\n- Finally removed the blank line that always appears at the top of the\r\n  NERDTree buffer","3":"- Added NERDTreeMouseMode option. If set to 1, then a double click is\r\n  required to activate all nodes, if set to 2 then a single click will\r\n  activate directory nodes, if set to 3 then a single click will activate\r\n  all nodes.\r\n- Now if you delete a file node and have it open in a buffer you are given\r\n  the option to delete that buffer as well. Similarly if you rename a file\r\n  you are given the option to delete any buffers containing the old file\r\n  (if any exist)\r\n- When you rename or create a node, the cursor is now put on the new node,\r\n  this makes it easy immediately edit  the new file.\r\n- Fixed a bug with the ! mapping that was occurring on windows with paths\r\n  containing spaces.\r\n- Made all the mappings customisable. See |NERD_tree-mappings| for\r\n  details. A side effect is that a lot of the \"double mappings\" have\r\n  disappeared. E.g 'o' is now the key that is used to activate a node,\r\n  <CR> is no longer mapped to the same.\r\n- Made the script echo warnings in some places rather than standard echos\r\n- Insane amounts of refactoring all over the place.\r\n- Finally removed the blank line that always appears at the top of the\r\n  NERDTree buffer","package":"NERD_tree.vim","4":"NERD_tree.vim","src_id":"6913","5":"6913","creation_date":"1175050427","6":"1175050427"},{"0":"1658","vim_version":"7.0","1":"7.0","script_version":"2.0.0","2":"2.0.0","version_comment":"- Added two new NERDChristmasTree decorations. First person to spot them\r\n  and email me gets a free copy of the NERDTree.\r\n- Made it so that when you jump around the tree (with the p, s and S\r\n  mappings) it is counted as a jump by vim. This means if you, eg, push\r\n  'p' one too many times then you can go `` or ctrl-o.\r\n- Added a new option called NERDTreeSortOrder which takes an array of\r\n  regexs and is used to determine the order that the treenodes are listed\r\n  in. Go :help NERDTreeSortOrder for details.\r\n- Removed the NERDTreeSortDirs option because it is consumed by\r\n  NERDTreeSortOrder\r\n- Added the 'i' mapping which the same as <tab> but requires less effort to\r\n  reach.\r\n- Added the ! mapping which is  used to execute file in the tree (after it\r\n  prompts you for arguments etc)\r\n","3":"- Added two new NERDChristmasTree decorations. First person to spot them\r\n  and email me gets a free copy of the NERDTree.\r\n- Made it so that when you jump around the tree (with the p, s and S\r\n  mappings) it is counted as a jump by vim. This means if you, eg, push\r\n  'p' one too many times then you can go `` or ctrl-o.\r\n- Added a new option called NERDTreeSortOrder which takes an array of\r\n  regexs and is used to determine the order that the treenodes are listed\r\n  in. Go :help NERDTreeSortOrder for details.\r\n- Removed the NERDTreeSortDirs option because it is consumed by\r\n  NERDTreeSortOrder\r\n- Added the 'i' mapping which the same as <tab> but requires less effort to\r\n  reach.\r\n- Added the ! mapping which is  used to execute file in the tree (after it\r\n  prompts you for arguments etc)\r\n","package":"NERD_tree.vim","4":"NERD_tree.vim","src_id":"6894","5":"6894","creation_date":"1174449566","6":"1174449566"},{"0":"1658","vim_version":"7.0","1":"7.0","script_version":"1.4.1","2":"1.4.1","version_comment":"Fixed a bug that was preventing the script from opening files that contained a space in linux.\r\nFixed a syntax highlighting bug in the quickhelp.\r\nSome refactoring. ","3":"Fixed a bug that was preventing the script from opening files that contained a space in linux.\r\nFixed a syntax highlighting bug in the quickhelp.\r\nSome refactoring. ","package":"NERD_tree.vim","4":"NERD_tree.vim","src_id":"6855","5":"6855","creation_date":"1173620589","6":"1173620589"},{"0":"1658","vim_version":"7.0","1":"7.0","script_version":"1.4.0","2":"1.4.0","version_comment":"*directories can now be renamed via the filesystem menu\r\n\r\n*some refactoring and bugfixes\r\n\r\n*rewrote the quickhelp that is toggled from the nerd tree window\r\n\r\n*added syntax highlighting to the quickhelp - thanks to Michael Geddes (aka frogonwheels) for his syntax highlighting tips on #vim\r\n\r\n*added some pretty syntax highlighting to the tree parts and added a new option called NERDChristmasTree to turn the highlighting off if  it is driving you insane (go :help NERDChristmasTree for details)\r\n","3":"*directories can now be renamed via the filesystem menu\r\n\r\n*some refactoring and bugfixes\r\n\r\n*rewrote the quickhelp that is toggled from the nerd tree window\r\n\r\n*added syntax highlighting to the quickhelp - thanks to Michael Geddes (aka frogonwheels) for his syntax highlighting tips on #vim\r\n\r\n*added some pretty syntax highlighting to the tree parts and added a new option called NERDChristmasTree to turn the highlighting off if  it is driving you insane (go :help NERDChristmasTree for details)\r\n","package":"NERD_tree.vim","4":"NERD_tree.vim","src_id":"6804","5":"6804","creation_date":"1172535002","6":"1172535002"},{"0":"1658","vim_version":"6.0","1":"6.0","script_version":"1.3.1","2":"1.3.1","version_comment":"*numerous fixes relating to the filesystem menu\r\n*incorporated a fix that allows the NERD tree to handle windows paths separated by either forward slashes OR backslashes... thanks to Jason Mills for emailing me this fix! :D","3":"*numerous fixes relating to the filesystem menu\r\n*incorporated a fix that allows the NERD tree to handle windows paths separated by either forward slashes OR backslashes... thanks to Jason Mills for emailing me this fix! :D","package":"NERD_tree.vim","4":"NERD_tree.vim","src_id":"6640","5":"6640","creation_date":"1169430842","6":"1169430842"},{"0":"1658","vim_version":"6.0","1":"6.0","script_version":"1.3","2":"1.3","version_comment":"*Now you can delete directories as well as files from the tree\r\n\r\n*The NERDTreeChDirMode option now defaults to 1... setting it to 0 causes a small bug for windows users (see :help NERDTreeChDirMode for details)\r\n\r\n*Opening a NERDTree on a different drive will now work for windows users\r\n\r\n*now the X mapping recursively closes all the children of the selected node. Previously it didnt recurse into the child nodes.","3":"*Now you can delete directories as well as files from the tree\r\n\r\n*The NERDTreeChDirMode option now defaults to 1... setting it to 0 causes a small bug for windows users (see :help NERDTreeChDirMode for details)\r\n\r\n*Opening a NERDTree on a different drive will now work for windows users\r\n\r\n*now the X mapping recursively closes all the children of the selected node. Previously it didnt recurse into the child nodes.","package":"NERD_tree.vim","4":"NERD_tree.vim","src_id":"6623","5":"6623","creation_date":"1169133809","6":"1169133809"},{"0":"1658","vim_version":"7.0","1":"7.0","script_version":"1.2","2":"1.2","version_comment":"*added X mapping which closes all the child directory nodes of the current node\r\n\r\n*when you create a new node you can backspace etc to type in the full path - before you had to create it in the directory of the current node\r\n*the script now tells you when it has finished a refresh operation (via r and R mappings)\r\n*the script also tells you when it has finished a recursive open operation (via O mapping)\r\n*the filesystem menu now works with single keystrokes where possible (i.e. you dont have to push enter all the time)\r\n\r\n*the script doesnt spaz out when you try to edit a ~ in windows anymore","3":"*added X mapping which closes all the child directory nodes of the current node\r\n\r\n*when you create a new node you can backspace etc to type in the full path - before you had to create it in the directory of the current node\r\n*the script now tells you when it has finished a refresh operation (via r and R mappings)\r\n*the script also tells you when it has finished a recursive open operation (via O mapping)\r\n*the filesystem menu now works with single keystrokes where possible (i.e. you dont have to push enter all the time)\r\n\r\n*the script doesnt spaz out when you try to edit a ~ in windows anymore","package":"NERD_tree.vim","4":"NERD_tree.vim","src_id":"6410","5":"6410","creation_date":"1163457141","6":"1163457141"},{"0":"1658","vim_version":"7.0","1":"7.0","script_version":"1.1.1","2":"1.1.1","version_comment":"Bug fixes:\r\n*now when you open a node by double clicking it, vim doesnt go into visual mode. Thanks to Yegappan  Lakshmanan for telling me how to fix this bug :D\r\n*added some \"be patient\" messages when you doing time consuming operations like recursively opening a directory or refreshing the tree\r\n*fixed a minor bug when moving the tree root up","3":"Bug fixes:\r\n*now when you open a node by double clicking it, vim doesnt go into visual mode. Thanks to Yegappan  Lakshmanan for telling me how to fix this bug :D\r\n*added some \"be patient\" messages when you doing time consuming operations like recursively opening a directory or refreshing the tree\r\n*fixed a minor bug when moving the tree root up","package":"NERD_tree.vim","4":"NERD_tree.vim","src_id":"6336","5":"6336","creation_date":"1161827239","6":"1161827239"},{"0":"1658","vim_version":"6.0","1":"6.0","script_version":"1.1.0","2":"1.1.0","version_comment":"New mappings:\r\n* 'cd' changes vim's current working dir to that of the selected node\r\n* 'q' calls :NERDTreeToggle to close the NERD tree window\r\n\r\n*opening a dir node recursively now doesnt open dir nodes if the script is instructed to ignore then via file-filters or the hidden-file filter. This increases performance insanely! Esp. if you have .svn dirs.\r\n\r\n*added the NERDTreeChDirMode option which tells the script if\/when to change vims current working dir. Go :help NERDTreeChDirMode for details.\r\n\r\n*fixed a feature where vim's current working directory was getting changed all over the show. Now it is never changed unless instructed to do so. Via mappings or the NERDTreeChDirMode option. Thanks to Terrance Cohen for emailing me about this :)\r\n\r\n*random bug fixes","3":"New mappings:\r\n* 'cd' changes vim's current working dir to that of the selected node\r\n* 'q' calls :NERDTreeToggle to close the NERD tree window\r\n\r\n*opening a dir node recursively now doesnt open dir nodes if the script is instructed to ignore then via file-filters or the hidden-file filter. This increases performance insanely! Esp. if you have .svn dirs.\r\n\r\n*added the NERDTreeChDirMode option which tells the script if\/when to change vims current working dir. Go :help NERDTreeChDirMode for details.\r\n\r\n*fixed a feature where vim's current working directory was getting changed all over the show. Now it is never changed unless instructed to do so. Via mappings or the NERDTreeChDirMode option. Thanks to Terrance Cohen for emailing me about this :)\r\n\r\n*random bug fixes","package":"NERD_tree.vim","4":"NERD_tree.vim","src_id":"6263","5":"6263","creation_date":"1160443224","6":"1160443224"},{"0":"1658","vim_version":"7.0","1":"7.0","script_version":"1.0.0","2":"1.0.0","version_comment":"*refreshing a directory now  works without closing all the children dir nodes for the refreshed node \r\n*we now have a  '.. (up a dir)' line at the top of the tree which moves the root up a dir when you open it.\r\n*added a 'recursively open directory' mapping\r\n*readonly files are now highlighted\r\n*fixed bugs\r\n","3":"*refreshing a directory now  works without closing all the children dir nodes for the refreshed node \r\n*we now have a  '.. (up a dir)' line at the top of the tree which moves the root up a dir when you open it.\r\n*added a 'recursively open directory' mapping\r\n*readonly files are now highlighted\r\n*fixed bugs\r\n","package":"NERD_tree.vim","4":"NERD_tree.vim","src_id":"6246","5":"6246","creation_date":"1159929118","6":"1159929118"},{"0":"1658","vim_version":"7.0","1":"7.0","script_version":"1.0beta3","2":"1.0beta3","version_comment":"New mappings:\r\n*'e' and 'middlemouse' open an explorer window of the current dir in the previous window.\r\n*'E' is like 'e' except the explorer is opened in a new split window.\r\n*'F' toggles whether files are displayed in the tree or not (this is handy when moving to a different part of the tree).\r\n*'D' (toggle hidden files) has been changed to 'H'\r\n*'m' brings up the 'filesystem menu' which allows you to do simple filesystem operations: create files\/dirs and rename\/delete files.\r\n\r\n*The position on the NERD tree window is customisable with the new NERDTreeSplitVertical and NERDTreeWinPos options.\r\n*The new NERDTreeShowFiles option allows you to specify whether files are shown on startup. This option, in conjunction with the e\/E\/middle-mouse mappings allows you to use the NERDTree like windows explorer.\r\n\r\n*Now the H and f mappings work without causing the tree root to be refreshed (so all your nodes dont get closed).\r\n\r\n*Fixed bugs.","3":"New mappings:\r\n*'e' and 'middlemouse' open an explorer window of the current dir in the previous window.\r\n*'E' is like 'e' except the explorer is opened in a new split window.\r\n*'F' toggles whether files are displayed in the tree or not (this is handy when moving to a different part of the tree).\r\n*'D' (toggle hidden files) has been changed to 'H'\r\n*'m' brings up the 'filesystem menu' which allows you to do simple filesystem operations: create files\/dirs and rename\/delete files.\r\n\r\n*The position on the NERD tree window is customisable with the new NERDTreeSplitVertical and NERDTreeWinPos options.\r\n*The new NERDTreeShowFiles option allows you to specify whether files are shown on startup. This option, in conjunction with the e\/E\/middle-mouse mappings allows you to use the NERDTree like windows explorer.\r\n\r\n*Now the H and f mappings work without causing the tree root to be refreshed (so all your nodes dont get closed).\r\n\r\n*Fixed bugs.","package":"NERD_tree.vim","4":"NERD_tree.vim","src_id":"6234","5":"6234","creation_date":"1159318309","6":"1159318309"},{"0":"1658","vim_version":"7.0","1":"7.0","script_version":"1.0beta2","2":"1.0beta2","version_comment":"*Paramaterised the :NERDTree and :NERDTreeToggle commands so you can give them a directory to start in.\r\n*Added t\/T mappings which open file nodes in a new tab (T does this silently) -- thanks to vigil for this idea.\r\n*Added a mapping to toggle whether the file filter is used.\r\n*Added g:NERDTreeSortDirs option which tells the NERD_tree where to put directories relative to files (i.e. top\/bottom\/alphabetical order with the files)\r\n*Symlinks are now highlighted\r\n*When you toggle the nerd tree off (with :NERDTreeToggle) (or close the nerd tree window) the cursor position is saved as well as the window position in the nerd tree so when you turn it back on it appears exactly as  you left it.\r\n*did some hardcore refactoring","3":"*Paramaterised the :NERDTree and :NERDTreeToggle commands so you can give them a directory to start in.\r\n*Added t\/T mappings which open file nodes in a new tab (T does this silently) -- thanks to vigil for this idea.\r\n*Added a mapping to toggle whether the file filter is used.\r\n*Added g:NERDTreeSortDirs option which tells the NERD_tree where to put directories relative to files (i.e. top\/bottom\/alphabetical order with the files)\r\n*Symlinks are now highlighted\r\n*When you toggle the nerd tree off (with :NERDTreeToggle) (or close the nerd tree window) the cursor position is saved as well as the window position in the nerd tree so when you turn it back on it appears exactly as  you left it.\r\n*did some hardcore refactoring","package":"NERD_tree.vim","4":"NERD_tree.vim","src_id":"6212","5":"6212","creation_date":"1158800653","6":"1158800653"},{"0":"1658","vim_version":"7.0","1":"7.0","script_version":"1.0beta1","2":"1.0beta1","version_comment":"Initial upload","3":"Initial upload","package":"NERD_tree.vim","4":"NERD_tree.vim","src_id":"6185","5":"6185","creation_date":"1158344533","6":"1158344533"}]},"1657":{"script_id":"1657","0":"1657","script_name":"doxygenerator","1":"doxygenerator","script_type":"utility","2":"utility","summary":"Aotomatically generates Doxygen style documentation template for C functions","3":"Aotomatically generates Doxygen style documentation template for C functions","description":"Just type '\\f' putting the cursor on a C function definition\/definition, and it will generate the corresponding Doxygen format documentation template for that function. So far, it doesn't handle functions with variable number of arguments, using '...'. Also, using it for 'void' functions will give incorrect result :)","4":"Just type '\\f' putting the cursor on a C function definition\/definition, and it will generate the corresponding Doxygen format documentation template for that function. So far, it doesn't handle functions with variable number of arguments, using '...'. Also, using it for 'void' functions will give incorrect result :)","install_details":"paste in the plugins directory.","5":"paste in the plugins directory.","first_name":"kaustubh","6":"kaustubh","last_name":"p","7":"p","releases":[{"0":"1657","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"c_function_plugin.vim","4":"c_function_plugin.vim","src_id":"6181","5":"6181","creation_date":"1158290682","6":"1158290682"}]},"1656":{"script_id":"1656","0":"1656","script_name":"quilt","1":"quilt","script_type":"utility","2":"utility","summary":"Enable quilt usage in vim","3":"Enable quilt usage in vim","description":"(from the help of the plugin: :help quilt-intro ) :\r\n\r\n\r\nQuilt is a project initiated by Andrew Morton to work with patches sent on the\r\nLKML. It is quite stable now, and really usefull to deal with stacked patches.\r\n\r\nFirst of all, before using this plugin, you must install quilt on your\r\nstation, for, under debian distribution, type in a command shell:\r\n\r\n\taptitude install quilt\r\n\r\nNow that you have your station setuped, let's speak a little about Quilt\r\nitself, more information can be found in man quilt shell command.\r\n\r\nThe idea behind quilt is that you work on patches, not on sources directly, so\r\nall your productions are patches. You create a patch to track your\r\nmodifications and send this patch to a work group so they can valiadate\/accept\r\nor integrate your modifications.\r\n\r\nNow you need a tool to help you maintain your patches, and that's exacltly\r\nwhat quilt does. Quilt let you apply a patch, modify your files (and thus the\r\npatch), unapply the patch. But it also allows you to do that on several\r\npatches at a time (one patch applied after the other ...) that's what we call\r\nthe stacked patches. (or the patch stack). \r\n\r\nYou can go to a level on the patch stack, modify the patch, and come back to\r\nanother patch stack level.\r\n\r\nThis plugin helps you handle all those boring operations with simple vim\r\ncommands ;)\r\n\r\nTo sum up the workflow :\r\n\r\n|:QuiltSetup| <patchdir>\r\n\r\n then:\r\n\r\n|:QuiltNew|   <patchname>\r\n\r\n ... open a file ...\r\n\r\n|:QuiltAdd|\r\n\r\n ... work on the file ...\r\n ... save your modifiations ...\r\n\r\n |:QuiltRefresh|\r\n\r\n and so on ... \r\n\r\n:help quilt-usage","4":"(from the help of the plugin: :help quilt-intro ) :\r\n\r\n\r\nQuilt is a project initiated by Andrew Morton to work with patches sent on the\r\nLKML. It is quite stable now, and really usefull to deal with stacked patches.\r\n\r\nFirst of all, before using this plugin, you must install quilt on your\r\nstation, for, under debian distribution, type in a command shell:\r\n\r\n\taptitude install quilt\r\n\r\nNow that you have your station setuped, let's speak a little about Quilt\r\nitself, more information can be found in man quilt shell command.\r\n\r\nThe idea behind quilt is that you work on patches, not on sources directly, so\r\nall your productions are patches. You create a patch to track your\r\nmodifications and send this patch to a work group so they can valiadate\/accept\r\nor integrate your modifications.\r\n\r\nNow you need a tool to help you maintain your patches, and that's exacltly\r\nwhat quilt does. Quilt let you apply a patch, modify your files (and thus the\r\npatch), unapply the patch. But it also allows you to do that on several\r\npatches at a time (one patch applied after the other ...) that's what we call\r\nthe stacked patches. (or the patch stack). \r\n\r\nYou can go to a level on the patch stack, modify the patch, and come back to\r\nanother patch stack level.\r\n\r\nThis plugin helps you handle all those boring operations with simple vim\r\ncommands ;)\r\n\r\nTo sum up the workflow :\r\n\r\n|:QuiltSetup| <patchdir>\r\n\r\n then:\r\n\r\n|:QuiltNew|   <patchname>\r\n\r\n ... open a file ...\r\n\r\n|:QuiltAdd|\r\n\r\n ... work on the file ...\r\n ... save your modifiations ...\r\n\r\n |:QuiltRefresh|\r\n\r\n and so on ... \r\n\r\n:help quilt-usage","install_details":"uncompress the archive in your .vim directory (or in the system directory), then restart vim (or :source ~\/.vim\/plugin\/quilt.vim then :helptag ~\/.vim\/doc\/ )\r\n\r\nthe archive contains :\r\n\r\nplugin\/quilt.vim (the plugin itself)\r\ndoc\/quilt.txt      (the vim documentation about the plugin)\r\n","5":"uncompress the archive in your .vim directory (or in the system directory), then restart vim (or :source ~\/.vim\/plugin\/quilt.vim then :helptag ~\/.vim\/doc\/ )\r\n\r\nthe archive contains :\r\n\r\nplugin\/quilt.vim (the plugin itself)\r\ndoc\/quilt.txt      (the vim documentation about the plugin)\r\n","first_name":"Florian","6":"Florian","last_name":"Delizy","7":"Delizy","releases":[{"0":"1656","vim_version":"7.0","1":"7.0","script_version":"0.9.7","2":"0.9.7","version_comment":"Fixed viminfo '\" filemark issue (thanks to Petr Uzel)","3":"Fixed viminfo '\" filemark issue (thanks to Petr Uzel)","package":"quilt-0.9.7.tar.gz","4":"quilt-0.9.7.tar.gz","src_id":"18952","5":"18952","creation_date":"1352208833","6":"1352208833"},{"0":"1656","vim_version":"7.0","1":"7.0","script_version":"0.9.6","2":"0.9.6","version_comment":"Fixed files handling in patches\/ directory (thanks to Jordan Crouse)","3":"Fixed files handling in patches\/ directory (thanks to Jordan Crouse)","package":"quilt-0.9.6.tar.gz","4":"quilt-0.9.6.tar.gz","src_id":"7705","5":"7705","creation_date":"1190581225","6":"1190581225"},{"0":"1656","vim_version":"7.0","1":"7.0","script_version":"0.9.5","2":"0.9.5","version_comment":"bugfix handling absolute filenames\r\nadded readonly mode for files not in current patch","3":"bugfix handling absolute filenames\r\nadded readonly mode for files not in current patch","package":"quilt-0.9.5.tar.gz","4":"quilt-0.9.5.tar.gz","src_id":"7072","5":"7072","creation_date":"1178375908","6":"1178375908"},{"0":"1656","vim_version":"7.0","1":"7.0","script_version":"0.9.4","2":"0.9.4","version_comment":"* Fixed g:Quilt* variables that were reseted every :source quilt.vim \r\n* Added ta customization command for calling thunderbird (debian... \r\n QuiltThunderbirdCmd should be set to \"icedove\" not \"thunderbird\" \r\n","3":"* Fixed g:Quilt* variables that were reseted every :source quilt.vim \r\n* Added ta customization command for calling thunderbird (debian... \r\n QuiltThunderbirdCmd should be set to \"icedove\" not \"thunderbird\" \r\n","package":"quilt-0.9.4.tar.gz","4":"quilt-0.9.4.tar.gz","src_id":"6418","5":"6418","creation_date":"1163560165","6":"1163560165"},{"0":"1656","vim_version":"7.0","1":"7.0","script_version":"0.9.3","2":"0.9.3","version_comment":"* Fixed QuiltAnnotate interface for files not completely from a patch","3":"* Fixed QuiltAnnotate interface for files not completely from a patch","package":"quilt-0.9.3.tar.gz","4":"quilt-0.9.3.tar.gz","src_id":"6406","5":"6406","creation_date":"1163400564","6":"1163400564"},{"0":"1656","vim_version":"7.0","1":"7.0","script_version":"0.9.2","2":"0.9.2","version_comment":"* Fixed QuiltAnnotate Interface when anotating a file not from the 0 line (the Followcursor was not working)","3":"* Fixed QuiltAnnotate Interface when anotating a file not from the 0 line (the Followcursor was not working)","package":"quilt-0.9.2.tar.gz","4":"quilt-0.9.2.tar.gz","src_id":"6389","5":"6389","creation_date":"1162974986","6":"1162974986"},{"0":"1656","vim_version":"7.0","1":"7.0","script_version":"0.9.1","2":"0.9.1","version_comment":"* Added a function to keep the current line in QuiltAnnotate\r\n* Added auto close interface when one is closed","3":"* Added a function to keep the current line in QuiltAnnotate\r\n* Added auto close interface when one is closed","package":"quilt-0.9.1.tar.gz","4":"quilt-0.9.1.tar.gz","src_id":"6384","5":"6384","creation_date":"1162812369","6":"1162812369"},{"0":"1656","vim_version":"7.0","1":"7.0","script_version":"0.9","2":"0.9","version_comment":"* Added auto .rej opening when opening a file\r\n* Added QuiltPatchEdit command\r\n* Added .rej auto recognition in QuiltFiles\r\n* Added automatic .rej recognition for FAILED hunk to QuiltPop\r\n* Added automatic .rej recognition for FAILED hunk to QuiltPush\r\n* Added color on QuiltPop\/Push success\/failure ...\r\n* Added QuiltAnnotate command\r\n* Fixed autocmd usage, so that commands are deleted on :source\r\n* Added the license (GPL of course)\r\n","3":"* Added auto .rej opening when opening a file\r\n* Added QuiltPatchEdit command\r\n* Added .rej auto recognition in QuiltFiles\r\n* Added automatic .rej recognition for FAILED hunk to QuiltPop\r\n* Added automatic .rej recognition for FAILED hunk to QuiltPush\r\n* Added color on QuiltPop\/Push success\/failure ...\r\n* Added QuiltAnnotate command\r\n* Fixed autocmd usage, so that commands are deleted on :source\r\n* Added the license (GPL of course)\r\n","package":"quilt-0.9.tar.gz","4":"quilt-0.9.tar.gz","src_id":"6381","5":"6381","creation_date":"1162803878","6":"1162803878"},{"0":"1656","vim_version":"7.0","1":"7.0","script_version":"0.8.1","2":"0.8.1","version_comment":"* Fixed the nocompatible option that caused problem in 'compatible'","3":"* Fixed the nocompatible option that caused problem in 'compatible'","package":"quilt-0.8.1.tar.gz","4":"quilt-0.8.1.tar.gz","src_id":"6343","5":"6343","creation_date":"1161951645","6":"1161951645"},{"0":"1656","vim_version":"7.0","1":"7.0","script_version":"0.8","2":"0.8","version_comment":"* Added completion of patches directory for QuiltNew\r\n* Beautified the help file :)\r\n* Added patch argument for QuiltAdd\r\n* Changed the completion of QuiltAdd (first arg file, second patch )\r\n* Added QuiltRemoveFrom command\r\n* Added QuiltRemoveFrom completion (patch, then files in <patch>)\r\n* Beautified the code (comments and such ...)\r\n* Added QuiltMail email address completion\r\n* Fixed QuiltHeader to add the correct 'Subject:' template\r\n* Added a status line in QuiltHeader to show the current patch name\r\n* Fixed a little bug in QuiltHeader preventing to Push\/Pop whille\r\n  editing a header                                                     \r\n","3":"* Added completion of patches directory for QuiltNew\r\n* Beautified the help file :)\r\n* Added patch argument for QuiltAdd\r\n* Changed the completion of QuiltAdd (first arg file, second patch )\r\n* Added QuiltRemoveFrom command\r\n* Added QuiltRemoveFrom completion (patch, then files in <patch>)\r\n* Beautified the code (comments and such ...)\r\n* Added QuiltMail email address completion\r\n* Fixed QuiltHeader to add the correct 'Subject:' template\r\n* Added a status line in QuiltHeader to show the current patch name\r\n* Fixed a little bug in QuiltHeader preventing to Push\/Pop whille\r\n  editing a header                                                     \r\n","package":"quilt-0.8.tar.gz","4":"quilt-0.8.tar.gz","src_id":"6340","5":"6340","creation_date":"1161874047","6":"1161874047"},{"0":"1656","vim_version":"6.0","1":"6.0","script_version":"0.7","2":"0.7","version_comment":"* Added QuiltRename command                                            \r\n* Factorized code (adding DoSystem function)                           \r\n* Added QuiltPushAll command                                           \r\n* Added QuiltPopAll command                                            \r\n* Added internal <SID>CurrentArgNumber                                 \r\n* Added QuiltHeader command                                            \r\n* Added QuiltWriteHeader command                                       \r\n","3":"* Added QuiltRename command                                            \r\n* Factorized code (adding DoSystem function)                           \r\n* Added QuiltPushAll command                                           \r\n* Added QuiltPopAll command                                            \r\n* Added internal <SID>CurrentArgNumber                                 \r\n* Added QuiltHeader command                                            \r\n* Added QuiltWriteHeader command                                       \r\n","package":"quilt-0.7.tar.bz2","4":"quilt-0.7.tar.bz2","src_id":"6322","5":"6322","creation_date":"1161588919","6":"1161588919"},{"0":"1656","vim_version":"7.0","1":"7.0","script_version":"0.6.1","2":"0.6.1","version_comment":"* Fixed the mail feature, special characters are now parsed and and rendered properly in thunderbird                                 \r\n","3":"* Fixed the mail feature, special characters are now parsed and and rendered properly in thunderbird                                 \r\n","package":"quilt.tar.gz","4":"quilt.tar.gz","src_id":"6224","5":"6224","creation_date":"1159168434","6":"1159168434"},{"0":"1656","vim_version":"7.0","1":"7.0","script_version":"0.6","2":"0.6","version_comment":"* Added QuiltPatches command                                          \r\n* Fixed bug in commands taking a file a argument when no file was given\r\n  (and no file was opened)                                            \r\n* Added QuiltMail bind with thunderbird                                \r\n* Fixed some bugs ...                                                  \r\n* Spellchecked the help ;)          ","3":"* Added QuiltPatches command                                          \r\n* Fixed bug in commands taking a file a argument when no file was given\r\n  (and no file was opened)                                            \r\n* Added QuiltMail bind with thunderbird                                \r\n* Fixed some bugs ...                                                  \r\n* Spellchecked the help ;)          ","package":"quilt.tar.gz","4":"quilt.tar.gz","src_id":"6215","5":"6215","creation_date":"1158918979","6":"1158918979"},{"0":"1656","vim_version":"7.0","1":"7.0","script_version":"0.5","2":"0.5","version_comment":"Added a help file for all command (and describing a workflow using quilt)\r\nFixed a bug in QuiltStatus, raising error on vim startup","3":"Added a help file for all command (and describing a workflow using quilt)\r\nFixed a bug in QuiltStatus, raising error on vim startup","package":"quilt.tar.gz","4":"quilt.tar.gz","src_id":"6202","5":"6202","creation_date":"1158655314","6":"1158655314"},{"0":"1656","vim_version":"6.0","1":"6.0","script_version":"0.4","2":"0.4","version_comment":"\"       * Changed :exe into system() with return value check                   \r\n\"       * Added QuiltStatus as an autocommand for file reading                 \r\n\"       * Added QuiltRefresh warning parsing, create a quickfix using cexpr    \r\n\"       * Added QuiltFiles command                                             \r\n\"       * Fixed some bugs                                                      \r\n\"       * Suppressed verbose output for QuiltAdd                               \r\n\"       * Suppressed verbose output for QuiltRefresh                           \r\n\"       * Suppressed verbose output for QuiltRemove                            \r\n","3":"\"       * Changed :exe into system() with return value check                   \r\n\"       * Added QuiltStatus as an autocommand for file reading                 \r\n\"       * Added QuiltRefresh warning parsing, create a quickfix using cexpr    \r\n\"       * Added QuiltFiles command                                             \r\n\"       * Fixed some bugs                                                      \r\n\"       * Suppressed verbose output for QuiltAdd                               \r\n\"       * Suppressed verbose output for QuiltRefresh                           \r\n\"       * Suppressed verbose output for QuiltRemove                            \r\n","package":"quilt.vim","4":"quilt.vim","src_id":"6198","5":"6198","creation_date":"1158563017","6":"1158563017"},{"0":"1656","vim_version":"7.0","1":"7.0","script_version":"0.3","2":"0.3","version_comment":"* Added the ! argument for Pop,Push,Refresh\r\n* Added the QuiltMoveTo\/QuiltFinishMove command\r\n* Spellchecked the Changelog ;)\r\n* Fixed the QuiltRefresh bug\r\n* Fixed QuiltAdd definition bug\r\n* Added QuiltGoTo[!] (Push\/Pop)\r\n* Added QuiltSetup[!]\r\n* Make this file 80 characters terminal friendly\r\n* Added QuiltNew command\r\n* Added QuiltDelete[!]\r\n* Fixed a whole bunch of bugs ... (thanks to #vim IRC channel )\r\n","3":"* Added the ! argument for Pop,Push,Refresh\r\n* Added the QuiltMoveTo\/QuiltFinishMove command\r\n* Spellchecked the Changelog ;)\r\n* Fixed the QuiltRefresh bug\r\n* Fixed QuiltAdd definition bug\r\n* Added QuiltGoTo[!] (Push\/Pop)\r\n* Added QuiltSetup[!]\r\n* Make this file 80 characters terminal friendly\r\n* Added QuiltNew command\r\n* Added QuiltDelete[!]\r\n* Fixed a whole bunch of bugs ... (thanks to #vim IRC channel )\r\n","package":"quilt.vim","4":"quilt.vim","src_id":"6190","5":"6190","creation_date":"1158504421","6":"1158504421"},{"0":"1656","vim_version":"7.0","1":"7.0","script_version":"0.2b","2":"0.2b","version_comment":" \t* add QuiltRefresh, QuiltPush, QuiltPop commands\r\n \t* add QuiltAdd, QuiltRemove\r\n \t* check if the current directory is a quilt directory\r\n \t* add parameters for Refresh, Add, Pop, Add ... \r\n \t* add patch completion\r\n \t* add in patch files completion\r\n","3":" \t* add QuiltRefresh, QuiltPush, QuiltPop commands\r\n \t* add QuiltAdd, QuiltRemove\r\n \t* check if the current directory is a quilt directory\r\n \t* add parameters for Refresh, Add, Pop, Add ... \r\n \t* add patch completion\r\n \t* add in patch files completion\r\n","package":"quilt.vim","4":"quilt.vim","src_id":"6182","5":"6182","creation_date":"1158310162","6":"1158310162"},{"0":"1656","vim_version":"7.0","1":"7.0","script_version":"0.1a","2":"0.1a","version_comment":"Initial upload","3":"Initial upload","package":"quilt.vim","4":"quilt.vim","src_id":"6179","5":"6179","creation_date":"1158223912","6":"1158223912"}]},"1655":{"script_id":"1655","0":"1655","script_name":"cobol.zip","1":"cobol.zip","script_type":"indent","2":"indent","summary":"COBOL indent plugin:  Understands COBOL's awkward use of columns","3":"COBOL indent plugin:  Understands COBOL's awkward use of columns","description":"Shipped with Vim as of 7.1\r\n\r\nThe indent plugin understands the column requirements of COBOL (Area A vs. Area B, comment indicator indented 6 spaces, etc.) and also neatly formats nested blocks and fields.  It works quite well for the code I have used it with; further feedback is appreciated.\r\n\r\nThe ftplugin is designed to help comply with COBOL's insane column requirements.  <C-T>, <C-D>, and <Tab> are remapped in insert mode to stop in columns 1, 7, 8 (Area A), and 12 (Area B) before switching to the use of shiftwidth\/softtabstop.  In normal mode, << and >> are remapped to ignore the first 7 columns, and with Vim 7, < and > serve as more general operator maps (>ap to indent a paragraph).  These two behaviors (insert vs. normal mode) are a bit different but generally what one would expect.\r\n\r\nThis script works well coupled with vimscript #1654 .","4":"Shipped with Vim as of 7.1\r\n\r\nThe indent plugin understands the column requirements of COBOL (Area A vs. Area B, comment indicator indented 6 spaces, etc.) and also neatly formats nested blocks and fields.  It works quite well for the code I have used it with; further feedback is appreciated.\r\n\r\nThe ftplugin is designed to help comply with COBOL's insane column requirements.  <C-T>, <C-D>, and <Tab> are remapped in insert mode to stop in columns 1, 7, 8 (Area A), and 12 (Area B) before switching to the use of shiftwidth\/softtabstop.  In normal mode, << and >> are remapped to ignore the first 7 columns, and with Vim 7, < and > serve as more general operator maps (>ap to indent a paragraph).  These two behaviors (insert vs. normal mode) are a bit different but generally what one would expect.\r\n\r\nThis script works well coupled with vimscript #1654 .","install_details":"Unzip in ~\/.vim or ~\\vimfiles (Windows).  The filetype is already detected by Vim.\r\n\r\nAn autocmd similar to the following is recommended for optimal use (place in your vimrc):\r\n\r\nautocmd FileType cobol set sw=4 sts=4 et sta tw=72","5":"Unzip in ~\/.vim or ~\\vimfiles (Windows).  The filetype is already detected by Vim.\r\n\r\nAn autocmd similar to the following is recommended for optimal use (place in your vimrc):\r\n\r\nautocmd FileType cobol set sw=4 sts=4 et sta tw=72","first_name":"Tim","6":"Tim","last_name":"Pope","7":"Pope","releases":[{"0":"1655","vim_version":"6.0","1":"6.0","script_version":"2.0","2":"2.0","version_comment":"Distribute indent and ftplugin together","3":"Distribute indent and ftplugin together","package":"cobol.zip","4":"cobol.zip","src_id":"11936","5":"11936","creation_date":"1261451007","6":"1261451007"},{"0":"1655","vim_version":"6.0","1":"6.0","script_version":"1.2","2":"1.2","version_comment":"Indent after ELSE","3":"Indent after ELSE","package":"cobol.vim","4":"cobol.vim","src_id":"6393","5":"6393","creation_date":"1162996684","6":"1162996684"},{"0":"1655","vim_version":"6.0","1":"6.0","script_version":"1.1","2":"1.1","version_comment":"Initial upload","3":"Initial upload","package":"cobol.vim","4":"cobol.vim","src_id":"6176","5":"6176","creation_date":"1158163452","6":"1158163452"}]},"1654":{"script_id":"1654","0":"1654","script_name":"git.zip","1":"git.zip","script_type":"ftplugin","2":"ftplugin","summary":"Git runtime files","3":"Git runtime files","description":"Included are syntax, indent, and filetype plugin files for git, gitcommit, gitconfig, gitrebase, and gitsendemail.\r\n\r\nEarlier versions of these files are shipped with Vim as of 7.2. The latest versions of these files can be retrieved from http:\/\/github.com\/tpope\/vim-git, which is the official distribution.\r\n\r\nIf you're looking for a Vim interface to Git, be sure to try fugitive.vim: vimscript #2975 http:\/\/github.com\/tpope\/vim-fugitive","4":"Included are syntax, indent, and filetype plugin files for git, gitcommit, gitconfig, gitrebase, and gitsendemail.\r\n\r\nEarlier versions of these files are shipped with Vim as of 7.2. The latest versions of these files can be retrieved from http:\/\/github.com\/tpope\/vim-git, which is the official distribution.\r\n\r\nIf you're looking for a Vim interface to Git, be sure to try fugitive.vim: vimscript #2975 http:\/\/github.com\/tpope\/vim-fugitive","install_details":"Install in ~\/.vim or ~\\vimfiles (Windows).","5":"Install in ~\/.vim or ~\\vimfiles (Windows).","first_name":"Tim","6":"Tim","last_name":"Pope","7":"Pope","releases":[{"0":"1654","vim_version":"6.0","1":"6.0","script_version":"5.0","2":"5.0","version_comment":"Initial upload","3":"Initial upload","package":"git.zip","4":"git.zip","src_id":"11937","5":"11937","creation_date":"1261451489","6":"1261451489"}]},"1653":{"script_id":"1653","0":"1653","script_name":"proe.vim","1":"proe.vim","script_type":"syntax","2":"syntax","summary":"Pro\/Engineer *.pro syntax","3":"Pro\/Engineer *.pro syntax","description":"This is for Wildfire 2.  I doubt there are big changes in 3, but let me know.\r\n\r\nI prefixed syntax items with \"mk_\" because Pro\/E files are largely used for 'Mapkeys'.\r\nHowever, some of the syntax items here apply to general Pro\/E syntax.\r\n\r\nThere is no vocabulary built in.  I was unable to download a good list of commands.  This documentation for Wildfire 2 is in PDF form, and translating to text and HTML both fail miserably for me.\r\n http:\/\/www.cad-resources.com\/WF2_configuration_options.pdf\r\n\r\nI'm confused as to why the tildes ~ and the 'mapkey(continued) ' markings were necessary to the syntax... thoughts, anyone?\r\n","4":"This is for Wildfire 2.  I doubt there are big changes in 3, but let me know.\r\n\r\nI prefixed syntax items with \"mk_\" because Pro\/E files are largely used for 'Mapkeys'.\r\nHowever, some of the syntax items here apply to general Pro\/E syntax.\r\n\r\nThere is no vocabulary built in.  I was unable to download a good list of commands.  This documentation for Wildfire 2 is in PDF form, and translating to text and HTML both fail miserably for me.\r\n http:\/\/www.cad-resources.com\/WF2_configuration_options.pdf\r\n\r\nI'm confused as to why the tildes ~ and the 'mapkey(continued) ' markings were necessary to the syntax... thoughts, anyone?\r\n","install_details":"Place proe.vim in your syntax folder with all the rest of the syntax files.\r\n\r\nAuto detection conflicts with IDL because of the file extension.  Find this line in your filetype.vim and comment it out (with a quote \"):\r\n\r\nau BufNewFile,BufRead *.pro\t\t\tsetf idlang\r\n\r\nIf you need to use that type of file, I hope you can think of your own solution.","5":"Place proe.vim in your syntax folder with all the rest of the syntax files.\r\n\r\nAuto detection conflicts with IDL because of the file extension.  Find this line in your filetype.vim and comment it out (with a quote \"):\r\n\r\nau BufNewFile,BufRead *.pro\t\t\tsetf idlang\r\n\r\nIf you need to use that type of file, I hope you can think of your own solution.","first_name":"Allan","6":"Allan","last_name":"Tokuda","7":"Tokuda","releases":[{"0":"1653","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"proe.vim","4":"proe.vim","src_id":"6171","5":"6171","creation_date":"1158048667","6":"1158048667"}]},"1652":{"script_id":"1652","0":"1652","script_name":"highlight_current_line.vim","1":"highlight_current_line.vim","script_type":"utility","2":"utility","summary":"Highlights CurrentLine","3":"Highlights CurrentLine","description":"Highlights the current line.","4":"Highlights the current line.","install_details":"Put it in your plugin directory or source it. ","5":"Put it in your plugin directory or source it. ","first_name":"Ansuman","6":"Ansuman","last_name":"Mohanty","7":"Mohanty","releases":[{"0":"1652","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"highlight_current_line.vim","4":"highlight_current_line.vim","src_id":"6169","5":"6169","creation_date":"1158039915","6":"1158039915"}]},"1651":{"script_id":"1651","0":"1651","script_name":"freya","1":"freya","script_type":"color scheme","2":"color scheme","summary":"A dark color scheme with warm colors","3":"A dark color scheme with warm colors","description":"This color scheme has a dark blackground. Most colors are very warm (mainly brown and beige shades). The brightness of all highlights is rather similar.\r\n\r\nThis color scheme is for GUI only, but makes some minor tweaks to cterm, too.","4":"This color scheme has a dark blackground. Most colors are very warm (mainly brown and beige shades). The brightness of all highlights is rather similar.\r\n\r\nThis color scheme is for GUI only, but makes some minor tweaks to cterm, too.","install_details":"Just put it in \"~\/.vim\/colors\" or in \"<your vim directory>\\vimfiles\\colors\" on Windows. Do \":colo freya\" to apply it. If you want to install it as your default color scheme, just add \"colo freya\" to your vimrc file. ","5":"Just put it in \"~\/.vim\/colors\" or in \"<your vim directory>\\vimfiles\\colors\" on Windows. Do \":colo freya\" to apply it. If you want to install it as your default color scheme, just add \"colo freya\" to your vimrc file. ","first_name":"Georg","6":"Georg","last_name":"Dahn","7":"Dahn","releases":[{"0":"1651","vim_version":"7.0","1":"7.0","script_version":"1.2.3","2":"1.2.3","version_comment":"changed color of MatchParen, made CursorLineNr lighter.","3":"changed color of MatchParen, made CursorLineNr lighter.","package":"freya.vim","4":"freya.vim","src_id":"20788","5":"20788","creation_date":"1378904069","6":"1378904069"},{"0":"1651","vim_version":"7.0","1":"7.0","script_version":"1.2.3","2":"1.2.3","version_comment":"Added CursorLineNr.","3":"Added CursorLineNr.","package":"freya.vim","4":"freya.vim","src_id":"20785","5":"20785","creation_date":"1378892437","6":"1378892437"},{"0":"1651","vim_version":"6.0","1":"6.0","script_version":"1.2.2","2":"1.2.2","version_comment":"Changed colors of Constant and PreProc, such that they can be distinguished more easily from other highlight groups.","3":"Changed colors of Constant and PreProc, such that they can be distinguished more easily from other highlight groups.","package":"freya.vim","4":"freya.vim","src_id":"6959","5":"6959","creation_date":"1175921629","6":"1175921629"}]},"1650":{"script_id":"1650","0":"1650","script_name":"asmx86_64","1":"asmx86_64","script_type":"syntax","2":"syntax","summary":"Syntax highlighting for x86_64 asm including gcc preprocessor","3":"Syntax highlighting for x86_64 asm including gcc preprocessor","description":"This syntax is especially adapted to working in the Linux kernel (x86_64)\r\n\r\nI am still working on it ... so this is a first version enjoy","4":"This syntax is especially adapted to working in the Linux kernel (x86_64)\r\n\r\nI am still working on it ... so this is a first version enjoy","install_details":"copy into your ~\/.vim\/syntax\/ directory\r\n\r\nto use it, just type :\r\n\r\nset syntax=asmx86_64","5":"copy into your ~\/.vim\/syntax\/ directory\r\n\r\nto use it, just type :\r\n\r\nset syntax=asmx86_64","first_name":"Florian","6":"Florian","last_name":"Delizy","7":"Delizy","releases":[{"0":"1650","vim_version":"7.0","1":"7.0","script_version":"0.5","2":"0.5","version_comment":"Added mm registers and made the syntax usable for objdump output as well","3":"Added mm registers and made the syntax usable for objdump output as well","package":"asmx86_64.vim","4":"asmx86_64.vim","src_id":"6535","5":"6535","creation_date":"1166755338","6":"1166755338"},{"0":"1650","vim_version":"7.0","1":"7.0","script_version":"0.4","2":"0.4","version_comment":"Included all mnemonics (with their size suffix)\r\nFixed the .macro colouring...","3":"Included all mnemonics (with their size suffix)\r\nFixed the .macro colouring...","package":"asmx86_64.vim","4":"asmx86_64.vim","src_id":"6242","5":"6242","creation_date":"1159788127","6":"1159788127"},{"0":"1650","vim_version":"6.0","1":"6.0","script_version":"0.3b","2":"0.3b","version_comment":"Close to completion, just needs now to add xmm and mmx registers, some instructions, and to deal with the #ifdef \/ '#' comment problem","3":"Close to completion, just needs now to add xmm and mmx registers, some instructions, and to deal with the #ifdef \/ '#' comment problem","package":"asmx86_64.vim","4":"asmx86_64.vim","src_id":"6170","5":"6170","creation_date":"1158048296","6":"1158048296"},{"0":"1650","vim_version":"6.0","1":"6.0","script_version":"0.2b","2":"0.2b","version_comment":"Fixed comments syntax: added a 'hack' so that # comment are correctly highted (they are highlighted as long as # is folowed by a space\r\nAdded %regs and regs (still needs mmx and xmm regs\r\n\r\nThis version should work with vim 5.7+ (if some of you try it on old version, please let me know).\r\n\r\nknwon bugs:\r\n\r\n'#' comments only works if followed by a space e.g.:\r\n# my comment (will be highlighted correctly)\r\n#my comment will not ...\r\n\r\ngcc preproc directives works if not followed by a space e.g.:\r\n#ifdef will be highlighted correctly\r\n# ifdef will not ...\r\n\r\nStill working on this problem","3":"Fixed comments syntax: added a 'hack' so that # comment are correctly highted (they are highlighted as long as # is folowed by a space\r\nAdded %regs and regs (still needs mmx and xmm regs\r\n\r\nThis version should work with vim 5.7+ (if some of you try it on old version, please let me know).\r\n\r\nknwon bugs:\r\n\r\n'#' comments only works if followed by a space e.g.:\r\n# my comment (will be highlighted correctly)\r\n#my comment will not ...\r\n\r\ngcc preproc directives works if not followed by a space e.g.:\r\n#ifdef will be highlighted correctly\r\n# ifdef will not ...\r\n\r\nStill working on this problem","package":"asmx86_64.vim","4":"asmx86_64.vim","src_id":"6168","5":"6168","creation_date":"1158039607","6":"1158039607"},{"0":"1650","vim_version":"7.0","1":"7.0","script_version":"0.1a","2":"0.1a","version_comment":"Initial upload","3":"Initial upload","package":"asmx86_64.vim","4":"asmx86_64.vim","src_id":"6164","5":"6164","creation_date":"1157996386","6":"1157996386"}]},"1649":{"script_id":"1649","0":"1649","script_name":"scrollfix","1":"scrollfix","script_type":"utility","2":"utility","summary":"keep cursor at fixed visual line of window","3":"keep cursor at fixed visual line of window","description":"\" This plugin, scrollfix, maintains cursor at fixed visual line of window\r\n\" (except near beginning of file and near end of file. The\r\n\" latter is configurable. You can choose whether to fix cursor\r\n\" near end of file or not, see g:fixeof below). This is enhancement\r\n\" to the 'set scrolloff=999', but scrollfix allows any visual line of\r\n\" window to keep cursor at, not only middle line of window.\r\n\"\r\n\" MAIN CONTROL VARIABLE, THE g:scrollfix:\r\n\"\r\n\" You choose the visual line of screen in percentages from top of screen:\r\n\"     let g:scrollfix=100 \" means lock cursor at bottom of window\r\n\"     let g:scrollfix=0   \" means keep cursor at top line of window\r\n\"     let g:scrollfix=50  \" means middle line of screen\r\n\"     let g:scrollfix=66  \" means two-third from top of screen\r\n\" As shipped, cursor is at 60% (let g:scrollfix=60)\r\n\"\r\n\" CONTROL VARIABLES:\r\n\" To change plugin settings, assign to following variables in your .vimrc.\r\n\" g:scrollfix - percentage from top of screen where to lock cursor\r\n\"               -1 - disables. Default: 60\r\n\" g:fixeof    - 1=>fix cursor also near end-of-file; 0=>no. Default:0\r\n\" g:scrollinfo - 1=>inform when scrollfix is turned on, 0=>no. Default: 1\r\n\" :FIX NNN         comand :FIX is alternate way to change g:scrollfix variable\r\n\"\r\n\" NB:\r\n\" - You need vim version at least 7.0.91 or later (vim6 won't work).\r\n\"   If you have vim7 before 7.0.91, you can use script#1473 to build\r\n\"   & install the latest vim7 executable.\r\n\" - this is beta version of the scrollfix plugin.\r\n\"   Your feedback is welcome. Please send your feedback to iler at gmail dot com.\r\n\"................................................................\r\n","4":"\" This plugin, scrollfix, maintains cursor at fixed visual line of window\r\n\" (except near beginning of file and near end of file. The\r\n\" latter is configurable. You can choose whether to fix cursor\r\n\" near end of file or not, see g:fixeof below). This is enhancement\r\n\" to the 'set scrolloff=999', but scrollfix allows any visual line of\r\n\" window to keep cursor at, not only middle line of window.\r\n\"\r\n\" MAIN CONTROL VARIABLE, THE g:scrollfix:\r\n\"\r\n\" You choose the visual line of screen in percentages from top of screen:\r\n\"     let g:scrollfix=100 \" means lock cursor at bottom of window\r\n\"     let g:scrollfix=0   \" means keep cursor at top line of window\r\n\"     let g:scrollfix=50  \" means middle line of screen\r\n\"     let g:scrollfix=66  \" means two-third from top of screen\r\n\" As shipped, cursor is at 60% (let g:scrollfix=60)\r\n\"\r\n\" CONTROL VARIABLES:\r\n\" To change plugin settings, assign to following variables in your .vimrc.\r\n\" g:scrollfix - percentage from top of screen where to lock cursor\r\n\"               -1 - disables. Default: 60\r\n\" g:fixeof    - 1=>fix cursor also near end-of-file; 0=>no. Default:0\r\n\" g:scrollinfo - 1=>inform when scrollfix is turned on, 0=>no. Default: 1\r\n\" :FIX NNN         comand :FIX is alternate way to change g:scrollfix variable\r\n\"\r\n\" NB:\r\n\" - You need vim version at least 7.0.91 or later (vim6 won't work).\r\n\"   If you have vim7 before 7.0.91, you can use script#1473 to build\r\n\"   & install the latest vim7 executable.\r\n\" - this is beta version of the scrollfix plugin.\r\n\"   Your feedback is welcome. Please send your feedback to iler at gmail dot com.\r\n\"................................................................\r\n","install_details":"Download script scrollfix.vim from the link below and copy it into your\r\npersonal plugin directory, the ~\/.vim\/plugin. Create this directory if\r\nit does not exist. Restart vim. Make sure your vim is version 7.0.91\r\nor later.\r\n\r\nTo customize the plugin, edit this file:\r\n    vim ~\/.vim\/plugin\/scrollfix.vim\r\nand edit following lines:\r\n\"------------------- Parameterization Variables -----------------------\r\nlet g:scrollfix=60  \" percentable of screen height to keep visual cursor on\r\nlet g:fixeof=0  \" 1=>fix cursor also near end-of-file; 0=>no.\r\nlet g:scrollinfo=1 \" 1=>inform when scrollfix is turned on, 0=>no\r\n\"---------------- End of Parameterization Variables -------------------\r\n","5":"Download script scrollfix.vim from the link below and copy it into your\r\npersonal plugin directory, the ~\/.vim\/plugin. Create this directory if\r\nit does not exist. Restart vim. Make sure your vim is version 7.0.91\r\nor later.\r\n\r\nTo customize the plugin, edit this file:\r\n    vim ~\/.vim\/plugin\/scrollfix.vim\r\nand edit following lines:\r\n\"------------------- Parameterization Variables -----------------------\r\nlet g:scrollfix=60  \" percentable of screen height to keep visual cursor on\r\nlet g:fixeof=0  \" 1=>fix cursor also near end-of-file; 0=>no.\r\nlet g:scrollinfo=1 \" 1=>inform when scrollfix is turned on, 0=>no\r\n\"---------------- End of Parameterization Variables -------------------\r\n","first_name":"Yakov","6":"Yakov","last_name":"Lerner","7":"Lerner","releases":[{"0":"1649","vim_version":"7.0","1":"7.0","script_version":"b060910","2":"b060910","version_comment":"Initial upload","3":"Initial upload","package":"scrollfix.vim","4":"scrollfix.vim","src_id":"6157","5":"6157","creation_date":"1157876666","6":"1157876666"}]},"1648":{"script_id":"1648","0":"1648","script_name":"ASL","1":"ASL","script_type":"syntax","2":"syntax","summary":"ACPI syntax language","3":"ACPI syntax language","description":"Syntax file for the ACPI Syntax Language. Uses the c.vim syntax file as base. Added important keywords for highlighting.","4":"Syntax file for the ACPI Syntax Language. Uses the c.vim syntax file as base. Added important keywords for highlighting.","install_details":"Copy asl.vim to your $HOME\/.vim\/syntax directory and add\r\n\r\n  autocmd BufNew,BufRead *.asl setf asl\r\n\r\nto your .vimrc.\r\n\r\n\r\n","5":"Copy asl.vim to your $HOME\/.vim\/syntax directory and add\r\n\r\n  autocmd BufNew,BufRead *.asl setf asl\r\n\r\nto your .vimrc.\r\n\r\n\r\n","first_name":"Sebastian","6":"Sebastian","last_name":"Witt","7":"Witt","releases":[{"0":"1648","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"asl.vim","4":"asl.vim","src_id":"6136","5":"6136","creation_date":"1157206011","6":"1157206011"}]},"1647":{"script_id":"1647","0":"1647","script_name":"addexecmod.vim","1":"addexecmod.vim","script_type":"utility","2":"utility","summary":"add execute permission automatically at saving file","3":"add execute permission automatically at saving file","description":"If you use this plugin, you don't need to type the command \"chmod +x your_script\".","4":"If you use this plugin, you don't need to type the command \"chmod +x your_script\".","install_details":"Just drop into ~\/.vim\/plugin","5":"Just drop into ~\/.vim\/plugin","first_name":"Jiro","6":"Jiro","last_name":"Nishiguchi","7":"Nishiguchi","releases":[{"0":"1647","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"addexecmod.vim","4":"addexecmod.vim","src_id":"6130","5":"6130","creation_date":"1157116717","6":"1157116717"}]},"1646":{"script_id":"1646","0":"1646","script_name":"str2numchar.vim","1":"str2numchar.vim","script_type":"utility","2":"utility","summary":"String convert to Numeric Character Reference","3":"String convert to Numeric Character Reference","description":"Author:       secondlife <hotchpotch@NOSPAM@gmail.com>\r\nLast Change:  2006 Sep 02\r\nVersion: 0.1, for Vim 7.0\r\n\r\nDESCRIPTION:\r\n This plugin is String convert to Numeric Character Reference\r\n and String convert to Hex Literal\r\n\r\nfor example:\r\n:echo Str2HexLiteral('abcd')\r\n\\x61\\x62\\x63\\x64\r\n:echo Str2NumChar('abcd')\r\n&#97;&#98;&#99;&#100;\r\n\r\n==================== file str2numchar.vimrc ====================\r\nvmap <silent> sn :Str2NumChar<CR>\r\nvmap <silent> sh :Str2HexLiteral<CR>\r\n==================== end: str2numchar.vimrc ====================\r\n","4":"Author:       secondlife <hotchpotch@NOSPAM@gmail.com>\r\nLast Change:  2006 Sep 02\r\nVersion: 0.1, for Vim 7.0\r\n\r\nDESCRIPTION:\r\n This plugin is String convert to Numeric Character Reference\r\n and String convert to Hex Literal\r\n\r\nfor example:\r\n:echo Str2HexLiteral('abcd')\r\n\\x61\\x62\\x63\\x64\r\n:echo Str2NumChar('abcd')\r\n&#97;&#98;&#99;&#100;\r\n\r\n==================== file str2numchar.vimrc ====================\r\nvmap <silent> sn :Str2NumChar<CR>\r\nvmap <silent> sh :Str2HexLiteral<CR>\r\n==================== end: str2numchar.vimrc ====================\r\n","install_details":"","5":"","first_name":"yuichi","6":"yuichi","last_name":"tateno","7":"tateno","releases":[{"0":"1646","vim_version":"7.0","1":"7.0","script_version":"0.2","2":"0.2","version_comment":"backslash delete bug fix.\r\nthx mk.","3":"backslash delete bug fix.\r\nthx mk.","package":"str2numchar.vim","4":"str2numchar.vim","src_id":"6156","5":"6156","creation_date":"1157854024","6":"1157854024"},{"0":"1646","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"str2numchar.vim","4":"str2numchar.vim","src_id":"6128","5":"6128","creation_date":"1157110829","6":"1157110829"}]},"1645":{"script_id":"1645","0":"1645","script_name":"tikiwiki.vim","1":"tikiwiki.vim","script_type":"syntax","2":"syntax","summary":"TikiWiki syntax highlighting","3":"TikiWiki syntax highlighting","description":"Syntax file for the tikiwiki language.\r\nThis is mainly useful if your browser allows you to edit text areas in an external editor (like the Mozex entension of Firefox). See also vimtip #805 if you are on Windows.\r\n","4":"Syntax file for the tikiwiki language.\r\nThis is mainly useful if your browser allows you to edit text areas in an external editor (like the Mozex entension of Firefox). See also vimtip #805 if you are on Windows.\r\n","install_details":"Put the script in ~\/.vim\/syntax or C:\\program files\\vim\\vimfiles\\syntax\r\nYou can then type ':set syntax=tikiwiki' (without the quotes) to have tikiwiki syntax highlighting.","5":"Put the script in ~\/.vim\/syntax or C:\\program files\\vim\\vimfiles\\syntax\r\nYou can then type ':set syntax=tikiwiki' (without the quotes) to have tikiwiki syntax highlighting.","first_name":"Olivier","6":"Olivier","last_name":"Teuliere","7":"Teuliere","releases":[{"0":"1645","vim_version":"6.0","1":"6.0","script_version":"1.2","2":"1.2","version_comment":"- Added support for plugins syntax: {PLUGINNAME(param=>value)\/}\r\n- Allowed = instead of => in the parameters list of a plugin, since tikiwiki also seems to allow them\r\n- Unknown plugin names are highlighted like errors\r\n- Plugins inside headings and title bars are now allowed\r\n","3":"- Added support for plugins syntax: {PLUGINNAME(param=>value)\/}\r\n- Allowed = instead of => in the parameters list of a plugin, since tikiwiki also seems to allow them\r\n- Unknown plugin names are highlighted like errors\r\n- Plugins inside headings and title bars are now allowed\r\n","package":"tikiwiki.vim","4":"tikiwiki.vim","src_id":"6971","5":"6971","creation_date":"1176282156","6":"1176282156"},{"0":"1645","vim_version":"6.0","1":"6.0","script_version":"1.1","2":"1.1","version_comment":"Added dedicated support for the FANCYTABLE plugin\r\nUsed @NoSpell in a few syntax groups to avoid spell checking\r\nThe plugin attributes are now more tolerant to additional white spaces","3":"Added dedicated support for the FANCYTABLE plugin\r\nUsed @NoSpell in a few syntax groups to avoid spell checking\r\nThe plugin attributes are now more tolerant to additional white spaces","package":"tikiwiki.vim","4":"tikiwiki.vim","src_id":"6969","5":"6969","creation_date":"1176268664","6":"1176268664"},{"0":"1645","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"tikiwiki.vim","4":"tikiwiki.vim","src_id":"6126","5":"6126","creation_date":"1157103236","6":"1157103236"}]},"1644":{"script_id":"1644","0":"1644","script_name":"switch_headers.vim","1":"switch_headers.vim","script_type":"utility","2":"utility","summary":"Simple switching between corresponding .h\/.hpp and .c\/.cpp files","3":"Simple switching between corresponding .h\/.hpp and .c\/.cpp files","description":"Simply switches between .c\/.cpp and .h\/.hpp files, suitable for one-keystroke switching.\r\nOrder of priority when looking for corresponding files:\r\n1) if .h file, seeks for .c first, then .cpp\r\n2) otherwise, seeks for .h first, then .hpp\r\nInspired by vimtip #384. Not as complex as vimscript #31, but if you need only small amount of code ...","4":"Simply switches between .c\/.cpp and .h\/.hpp files, suitable for one-keystroke switching.\r\nOrder of priority when looking for corresponding files:\r\n1) if .h file, seeks for .c first, then .cpp\r\n2) otherwise, seeks for .h first, then .hpp\r\nInspired by vimtip #384. Not as complex as vimscript #31, but if you need only small amount of code ...","install_details":"Drop into ~\/vimfiles\/plugin\r\nAdd source ~\/vimfiles\/plugin\/switch_headers.vim to your c.vim\/cpp.vim after\/syntax files\r\nUse mapping such as:\r\nnmap <F9> :call SwitchHeader()<cr>","5":"Drop into ~\/vimfiles\/plugin\r\nAdd source ~\/vimfiles\/plugin\/switch_headers.vim to your c.vim\/cpp.vim after\/syntax files\r\nUse mapping such as:\r\nnmap <F9> :call SwitchHeader()<cr>","first_name":"Slavomir","6":"Slavomir","last_name":"Smutny","7":"Smutny","releases":[{"0":"1644","vim_version":"6.0","1":"6.0","script_version":"1.2","2":"1.2","version_comment":"fixed when possibly switching from non-C\/C++ file + if source is missing for header","3":"fixed when possibly switching from non-C\/C++ file + if source is missing for header","package":"switch_headers.vim","4":"switch_headers.vim","src_id":"6125","5":"6125","creation_date":"1157073844","6":"1157073844"},{"0":"1644","vim_version":"6.0","1":"6.0","script_version":"1.1","2":"1.1","version_comment":"Added check for .hpp","3":"Added check for .hpp","package":"switch_headers.vim","4":"switch_headers.vim","src_id":"6118","5":"6118","creation_date":"1156993144","6":"1156993144"},{"0":"1644","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"switch_headers.vim","4":"switch_headers.vim","src_id":"6117","5":"6117","creation_date":"1156992857","6":"1156992857"}]},"1643":{"script_id":"1643","0":"1643","script_name":"SuperTab","1":"SuperTab","script_type":"utility","2":"utility","summary":"Do all your insert-mode completion with Tab.","3":"Do all your insert-mode completion with Tab.","description":"Overview\r\n\r\nSupertab allows you to use <Tab> for all your insert completion needs\r\n(:help ins-completion).\r\n\r\nFeatures\r\n\r\n- Configurable to suit you needs:\r\n  - Default completion type to use.\r\n  - Prevent <Tab> from completing after\/before defined patterns.\r\n  - Close vim's completion preview window when code completion is finished.\r\n  - When using other completion types, you can configure how long to 'remember'\r\n    the current completion type before returning to the default.\r\n  - Don't like using <Tab>? You can also configure a different pair of keys to\r\n    scroll forwards and backwards through completion results.\r\n- Optional improved 'longest' completion support (after typing some characters,\r\n  hitting <Tab> will highlight the next longest match).\r\n- Built in 'context' completion option which chooses the appropriate completion\r\n  type based on the text preceding the cursor.\r\n  - You can also plug in your own functions to determine which completion type\r\n    to use.\r\n- Support for simple completion chaining (falling back to a different\r\n  completion type, keyword completion for example, if omni or user completion\r\n  returns no results).\r\n\r\nYou can also find supertab on github repository:\r\nhttp:\/\/github.com\/ervandew\/supertab\r\n","4":"Overview\r\n\r\nSupertab allows you to use <Tab> for all your insert completion needs\r\n(:help ins-completion).\r\n\r\nFeatures\r\n\r\n- Configurable to suit you needs:\r\n  - Default completion type to use.\r\n  - Prevent <Tab> from completing after\/before defined patterns.\r\n  - Close vim's completion preview window when code completion is finished.\r\n  - When using other completion types, you can configure how long to 'remember'\r\n    the current completion type before returning to the default.\r\n  - Don't like using <Tab>? You can also configure a different pair of keys to\r\n    scroll forwards and backwards through completion results.\r\n- Optional improved 'longest' completion support (after typing some characters,\r\n  hitting <Tab> will highlight the next longest match).\r\n- Built in 'context' completion option which chooses the appropriate completion\r\n  type based on the text preceding the cursor.\r\n  - You can also plug in your own functions to determine which completion type\r\n    to use.\r\n- Support for simple completion chaining (falling back to a different\r\n  completion type, keyword completion for example, if omni or user completion\r\n  returns no results).\r\n\r\nYou can also find supertab on github repository:\r\nhttp:\/\/github.com\/ervandew\/supertab\r\n","install_details":"1. Download supertab.vmb to any directory.\r\n2. Open the file in vim ($ vim supertab.vmb).\r\n3. Source the file (:so %).","5":"1. Download supertab.vmb to any directory.\r\n2. Open the file in vim ($ vim supertab.vmb).\r\n3. Source the file (:so %).","first_name":"Eric","6":"Eric","last_name":"Van Dewoestine","7":"Van Dewoestine","releases":[{"0":"1643","vim_version":"7.0","1":"7.0","script_version":"2.1","2":"2.1","version_comment":"Full list of changes: https:\/\/github.com\/ervandew\/supertab\/compare\/2.0...2.1","3":"Full list of changes: https:\/\/github.com\/ervandew\/supertab\/compare\/2.0...2.1","package":"supertab.vmb","4":"supertab.vmb","src_id":"21752","5":"21752","creation_date":"1397011694","6":"1397011694"},{"0":"1643","vim_version":"7.0","1":"7.0","script_version":"2.0","2":"2.0","version_comment":"- added support for chaining two completion types (falls back to the second if not results from the first).\r\n- added setting to close completion preview window when the completion popup closes.\r\n- improved compatibility with other plugins.\r\n- other minor bug fixes.","3":"- added support for chaining two completion types (falls back to the second if not results from the first).\r\n- added setting to close completion preview window when the completion popup closes.\r\n- improved compatibility with other plugins.\r\n- other minor bug fixes.","package":"supertab.vmb","4":"supertab.vmb","src_id":"18075","5":"18075","creation_date":"1338563102","6":"1338563102"},{"0":"1643","vim_version":"7.0","1":"7.0","script_version":"1.6","2":"1.6","version_comment":"- couple longest enhancement fixes\r\n- added ability to disable supertab via a buffer local variable\r\n- few other miscellaneous fixes.","3":"- couple longest enhancement fixes\r\n- added ability to disable supertab via a buffer local variable\r\n- few other miscellaneous fixes.","package":"supertab.vba","4":"supertab.vba","src_id":"16104","5":"16104","creation_date":"1311138100","6":"1311138100"},{"0":"1643","vim_version":"7.0","1":"7.0","script_version":"1.5","2":"1.5","version_comment":"- updated to support user mapped <c-n>\/<c-p>\r\n- fix logic to decide whether to scroll up or down based on current completion context\r\n- fix <c-x><c-*> w\/ longest enhancement enabled","3":"- updated to support user mapped <c-n>\/<c-p>\r\n- fix logic to decide whether to scroll up or down based on current completion context\r\n- fix <c-x><c-*> w\/ longest enhancement enabled","package":"supertab.vba","4":"supertab.vba","src_id":"15029","5":"15029","creation_date":"1297870263","6":"1297870263"},{"0":"1643","vim_version":"7.0","1":"7.0","script_version":"1.4","2":"1.4","version_comment":"Fix error that occurs attempting to complete after optional alternate completion mapping or :SuperTabHelp have set the completion type.","3":"Fix error that occurs attempting to complete after optional alternate completion mapping or :SuperTabHelp have set the completion type.","package":"supertab.vba","4":"supertab.vba","src_id":"14882","5":"14882","creation_date":"1296142331","6":"1296142331"},{"0":"1643","vim_version":"7.0","1":"7.0","script_version":"1.3","2":"1.3","version_comment":"- fix error attempting tab completion if buffer was loaded with no autocmds fired\r\n- fix tabbing through completion results with longest enabled when the longest text expanded is the empty string.","3":"- fix error attempting tab completion if buffer was loaded with no autocmds fired\r\n- fix tabbing through completion results with longest enabled when the longest text expanded is the empty string.","package":"supertab.vba","4":"supertab.vba","src_id":"14782","5":"14782","creation_date":"1295364851","6":"1295364851"},{"0":"1643","vim_version":"7.0","1":"7.0","script_version":"1.2","2":"1.2","version_comment":"- fix to not break abbreviation expansion on <cr>\r\n- when using longest enhancement, save\/restore any previous mappings for <bs>\/<c-h>\r\n- fix <cr> mapping to cooperate better with <cr> mappings of other plugins (ex. endwise)\r\n- created variables to set user defined list of before or after patterns for which completion should not be attempted (:h supertab-preventcomplete)","3":"- fix to not break abbreviation expansion on <cr>\r\n- when using longest enhancement, save\/restore any previous mappings for <bs>\/<c-h>\r\n- fix <cr> mapping to cooperate better with <cr> mappings of other plugins (ex. endwise)\r\n- created variables to set user defined list of before or after patterns for which completion should not be attempted (:h supertab-preventcomplete)","package":"supertab.vba","4":"supertab.vba","src_id":"14717","5":"14717","creation_date":"1294606487","6":"1294606487"},{"0":"1643","vim_version":"7.0","1":"7.0","script_version":"1.1","2":"1.1","version_comment":"- added optional default <cr> mapping to end completion mode (enabled by default)\r\n- added support for an enhanced longest match completion (disabled by default)\r\n- other minor enhancements + bug fixes","3":"- added optional default <cr> mapping to end completion mode (enabled by default)\r\n- added support for an enhanced longest match completion (disabled by default)\r\n- other minor enhancements + bug fixes","package":"supertab.vba","4":"supertab.vba","src_id":"13928","5":"13928","creation_date":"1285555413","6":"1285555413"},{"0":"1643","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"- fixed reverse cycling through result when using <c-n> completion\r\n- now distributed as a vimball with a help file (:h supertab).  Thanks to Christophe-Marie Duquesne.","3":"- fixed reverse cycling through result when using <c-n> completion\r\n- now distributed as a vimball with a help file (:h supertab).  Thanks to Christophe-Marie Duquesne.","package":"supertab.vba","4":"supertab.vba","src_id":"11853","5":"11853","creation_date":"1259856298","6":"1259856298"},{"0":"1643","vim_version":"7.0","1":"7.0","script_version":"0.61","2":"0.61","version_comment":"Fixed a possible error that may occur in some rare conditions.","3":"Fixed a possible error that may occur in some rare conditions.","package":"supertab.vim","4":"supertab.vim","src_id":"11533","5":"11533","creation_date":"1255703171","6":"1255703171"},{"0":"1643","vim_version":"7.0","1":"7.0","script_version":"0.60","2":"0.60","version_comment":"- Refactored the contextual completion and default discovery support.\r\n  - Context completion now supports plugable functions to determine which\r\n    completion type to use.\r\n  - Default discovery is now a part of context completion.\r\n- NOTE: Several non-backwards compatible configuration changes where made.\r\n  - g:SuperTabRetainCompletionType is now g:SuperTabRetainCompletionDuration\r\n    and accepts one of 'none', 'insert', or 'session'.\r\n  - new setting g:SuperTabCompletionContexts defines which context completion\r\n    functions are consulted.\r\n  - g:SuperTabDefaultCompletionTypeDiscovery is now\r\n    g:SuperTabContextDiscoverDiscovery and requires that\r\n    g:SuperTabContextDefaultCompletionType is set to 'context' and that\r\n    's:ContextDiscover' is in your g:SuperTabCompletionContexts list.\r\nPlease see the updated \"Global Variables\" fold in supertab.vim for additional\r\ndetails and examples.","3":"- Refactored the contextual completion and default discovery support.\r\n  - Context completion now supports plugable functions to determine which\r\n    completion type to use.\r\n  - Default discovery is now a part of context completion.\r\n- NOTE: Several non-backwards compatible configuration changes where made.\r\n  - g:SuperTabRetainCompletionType is now g:SuperTabRetainCompletionDuration\r\n    and accepts one of 'none', 'insert', or 'session'.\r\n  - new setting g:SuperTabCompletionContexts defines which context completion\r\n    functions are consulted.\r\n  - g:SuperTabDefaultCompletionTypeDiscovery is now\r\n    g:SuperTabContextDiscoverDiscovery and requires that\r\n    g:SuperTabContextDefaultCompletionType is set to 'context' and that\r\n    's:ContextDiscover' is in your g:SuperTabCompletionContexts list.\r\nPlease see the updated \"Global Variables\" fold in supertab.vim for additional\r\ndetails and examples.","package":"supertab.vim","4":"supertab.vim","src_id":"11386","5":"11386","creation_date":"1253069140","6":"1253069140"},{"0":"1643","vim_version":"7.0","1":"7.0","script_version":"0.51","2":"0.51","version_comment":"Replaced internal function s:IsWordChar with vim's keyword character class (Thanks to Ingo Karkat for the patch).","3":"Replaced internal function s:IsWordChar with vim's keyword character class (Thanks to Ingo Karkat for the patch).","package":"supertab.vim","4":"supertab.vim","src_id":"10998","5":"10998","creation_date":"1247340276","6":"1247340276"},{"0":"1643","vim_version":"7.0","1":"7.0","script_version":"0.50","2":"0.50","version_comment":"Added check for vim 7 or greater, otherwise disable supertab support (suggested by Vincent Lee).  Also, removed any remaining pre vim 7 logic that is no longer applicable.","3":"Added check for vim 7 or greater, otherwise disable supertab support (suggested by Vincent Lee).  Also, removed any remaining pre vim 7 logic that is no longer applicable.","package":"supertab.vim","4":"supertab.vim","src_id":"10900","5":"10900","creation_date":"1246026236","6":"1246026236"},{"0":"1643","vim_version":"7.0","1":"7.0","script_version":"0.49","2":"0.49","version_comment":"fixed case where new buffer may not be initialized by super tab (thanks to Tammer Saleh for reporting the issue).","3":"fixed case where new buffer may not be initialized by super tab (thanks to Tammer Saleh for reporting the issue).","package":"supertab.vim","4":"supertab.vim","src_id":"9918","5":"9918","creation_date":"1233811925","6":"1233811925"},{"0":"1643","vim_version":"7.0","1":"7.0","script_version":"0.48","2":"0.48","version_comment":"Fixed command line completion (ctrl-x ctrl-v) when invoked from supertab.  Thanks to Frank Chang for the patch.","3":"Fixed command line completion (ctrl-x ctrl-v) when invoked from supertab.  Thanks to Frank Chang for the patch.","package":"supertab.vim","4":"supertab.vim","src_id":"9837","5":"9837","creation_date":"1232245735","6":"1232245735"},{"0":"1643","vim_version":"7.0","1":"7.0","script_version":"0.47","2":"0.47","version_comment":"fixed issue with default completion discovery option if desired type is dependent on file type plugins.  Thanks to Andreas Schneider for reporting the issue.","3":"fixed issue with default completion discovery option if desired type is dependent on file type plugins.  Thanks to Andreas Schneider for reporting the issue.","package":"supertab.vim","4":"supertab.vim","src_id":"9795","5":"9795","creation_date":"1231651883","6":"1231651883"},{"0":"1643","vim_version":"7.0","1":"7.0","script_version":"0.46","2":"0.46","version_comment":"Added support for default completion type 'context', which will result in super tab attempting to determine which completion type to use (file, user\/omni, keyword) based on the text preceding the cursor (Based on suggestion by Fran\u00c3\u00a7ois Beaubert).\r\n","3":"Added support for default completion type 'context', which will result in super tab attempting to determine which completion type to use (file, user\/omni, keyword) based on the text preceding the cursor (Based on suggestion by Fran\u00c3\u00a7ois Beaubert).\r\n","package":"supertab.vim","4":"supertab.vim","src_id":"9510","5":"9510","creation_date":"1226777897","6":"1226777897"},{"0":"1643","vim_version":"6.0","1":"6.0","script_version":"0.45","2":"0.45","version_comment":"- fixed possible completion error on first buffer as supertab may not have been properly initialized (thanks to bill emmons for discovering the error).","3":"- fixed possible completion error on first buffer as supertab may not have been properly initialized (thanks to bill emmons for discovering the error).","package":"supertab.vim","4":"supertab.vim","src_id":"8070","5":"8070","creation_date":"1198012942","6":"1198012942"},{"0":"1643","vim_version":"6.0","1":"6.0","script_version":"0.44","2":"0.44","version_comment":"- added config variable to specify discovery list used to determine the default completion type to use for the current buffer. (based on request by Den Yao)\r\n- added config variables to changed the default mappings for forward backwards completion. (based on request by Li Chaoqun)\r\n- added config variable to preselect the first entry when completeopt has 'menu' and 'longest'. (based on suggestion and patch by Mike Lundy)","3":"- added config variable to specify discovery list used to determine the default completion type to use for the current buffer. (based on request by Den Yao)\r\n- added config variables to changed the default mappings for forward backwards completion. (based on request by Li Chaoqun)\r\n- added config variable to preselect the first entry when completeopt has 'menu' and 'longest'. (based on suggestion and patch by Mike Lundy)","package":"supertab.vim","4":"supertab.vim","src_id":"7904","5":"7904","creation_date":"1194556580","6":"1194556580"},{"0":"1643","vim_version":"6.0","1":"6.0","script_version":"0.43","2":"0.43","version_comment":"With the permission of the original author, this script is now released under the BSD license.","3":"With the permission of the original author, this script is now released under the BSD license.","package":"supertab.vim","4":"supertab.vim","src_id":"7344","5":"7344","creation_date":"1184225788","6":"1184225788"},{"0":"1643","vim_version":"6.0","1":"6.0","script_version":"0.42","2":"0.42","version_comment":"- Added g:SuperTabMidWordCompletion variable to determine if completion should be done within a word (enabled by default).  (based on request by Charles Gruenwald)\r\n- Applied patch to fix <s-tab> cycling through completion results. (submitted by Lukasz Krotowski)\r\n","3":"- Added g:SuperTabMidWordCompletion variable to determine if completion should be done within a word (enabled by default).  (based on request by Charles Gruenwald)\r\n- Applied patch to fix <s-tab> cycling through completion results. (submitted by Lukasz Krotowski)\r\n","package":"supertab.vim","4":"supertab.vim","src_id":"7228","5":"7228","creation_date":"1181546215","6":"1181546215"},{"0":"1643","vim_version":"6.0","1":"6.0","script_version":"0.41","2":"0.41","version_comment":"Initial upload","3":"Initial upload","package":"supertab.vim","4":"supertab.vim","src_id":"6114","5":"6114","creation_date":"1156959079","6":"1156959079"}]},"1642":{"script_id":"1642","0":"1642","script_name":"zzsplash","1":"zzsplash","script_type":"utility","2":"utility","summary":"Show Vim splash screen even when started with a filename argument","3":"Show Vim splash screen even when started with a filename argument","description":"By default, (g)vim displays a splash screen when starting with no editfile, or in response to the \":intro\" command. This plugin makes the splash screen appear at startup in all cases, even when started with one or more \"filename\" arguments.","4":"By default, (g)vim displays a splash screen when starting with no editfile, or in response to the \":intro\" command. This plugin makes the splash screen appear at startup in all cases, even when started with one or more \"filename\" arguments.","install_details":"Just drop this file in the after\/plugin subdirectory of the directory named *last* in the 'runtimepath' option. For instance, its full path will typically become (as seen by the shell)\r\n\r\n- on Linux: ~\/.vim\/after\/plugin\/zzsplash.vim\r\n\r\n- on Windows: %HOME%\\vimfiles\\after\\plugin\\zzsplash.vim\r\n\r\netc.\r\n\r\n\r\n-------\r\nNote: If you want it to work even on versions of Vim with no expression evaluation, add the following at the very end of your vimrc:\r\n\r\nif 1\r\n  finish\r\nendif\r\n\" come here only if expression evaluation is not compiled-in\r\nruntime! plugin\/zzsplash.vim","5":"Just drop this file in the after\/plugin subdirectory of the directory named *last* in the 'runtimepath' option. For instance, its full path will typically become (as seen by the shell)\r\n\r\n- on Linux: ~\/.vim\/after\/plugin\/zzsplash.vim\r\n\r\n- on Windows: %HOME%\\vimfiles\\after\\plugin\\zzsplash.vim\r\n\r\netc.\r\n\r\n\r\n-------\r\nNote: If you want it to work even on versions of Vim with no expression evaluation, add the following at the very end of your vimrc:\r\n\r\nif 1\r\n  finish\r\nendif\r\n\" come here only if expression evaluation is not compiled-in\r\nruntime! plugin\/zzsplash.vim","first_name":"Antoine","6":"Antoine","last_name":"Mechelynck","7":"Mechelynck","releases":[{"0":"1642","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"- bugfix: don\\'t display an extra splash screen if we can detect that Vim will do it\r\n- improvement: support even Tiny versions (after a fashion)\r\n- now we actually support all Vim versions starting at 5.0","3":"- bugfix: don\\'t display an extra splash screen if we can detect that Vim will do it\r\n- improvement: support even Tiny versions (after a fashion)\r\n- now we actually support all Vim versions starting at 5.0","package":"zzsplash.vim","4":"zzsplash.vim","src_id":"6111","5":"6111","creation_date":"1156885666","6":"1156885666"},{"0":"1642","vim_version":"5.7","1":"5.7","script_version":"0.0","2":"0.0","version_comment":"Initial upload","3":"Initial upload","package":"zzsplash.vim","4":"zzsplash.vim","src_id":"6109","5":"6109","creation_date":"1156882302","6":"1156882302"}]},"1641":{"script_id":"1641","0":"1641","script_name":"AfterColors.vim","1":"AfterColors.vim","script_type":"utility","2":"utility","summary":"Provides support for after\/colors\/ scripts","3":"Provides support for after\/colors\/ scripts","description":"Allows you to create an after\/colors\/ script for customizing any colorscheme.\r\n\r\n-- EXAMPLE --\r\nIf you like the 'desert' colorscheme, but you really want comments to be red and functions to be blue, previously you would copy the entire colorscheme into your home directory and customize it.  With this plugin installed, you can create a small script to change just the parts you want for that colorscheme, exactly how you would for an ftplugin or syntax script:\r\n\r\nFor unix systems you would create:\r\n  ~\/.vim\/after\/colors\/desert.vim:\r\n    highlight Comment guifg=Red ctermfg=Red\r\n    highlight Function guifg=Blue ctermfg=Blue\r\n\r\nOn windows you would create:\r\n C:\\Documents and Settings\\Peter\\vimfiles\\after\\colors\\desert.vim:\r\n    highlight Comment guifg=Red ctermfg=Red\r\n    highlight Function guifg=Blue ctermfg=Blue\r\n\r\n\r\n-- VERSION 6 WARNING --\r\nIf your Vim is older than version 7, then the after\/colors scripts will only be loaded once when Vim starts.  This will not be a problem if you choose your colorscheme in your .vimrc file, but if you change your colorscheme after vim has loaded then your after\/colors scripts will be ignored.  This is not an issue in Vim 7.\r\n\r\n\r\nIn case of problems, you can email me: <toomuchphp-vim at yahoo.com>\r\n","4":"Allows you to create an after\/colors\/ script for customizing any colorscheme.\r\n\r\n-- EXAMPLE --\r\nIf you like the 'desert' colorscheme, but you really want comments to be red and functions to be blue, previously you would copy the entire colorscheme into your home directory and customize it.  With this plugin installed, you can create a small script to change just the parts you want for that colorscheme, exactly how you would for an ftplugin or syntax script:\r\n\r\nFor unix systems you would create:\r\n  ~\/.vim\/after\/colors\/desert.vim:\r\n    highlight Comment guifg=Red ctermfg=Red\r\n    highlight Function guifg=Blue ctermfg=Blue\r\n\r\nOn windows you would create:\r\n C:\\Documents and Settings\\Peter\\vimfiles\\after\\colors\\desert.vim:\r\n    highlight Comment guifg=Red ctermfg=Red\r\n    highlight Function guifg=Blue ctermfg=Blue\r\n\r\n\r\n-- VERSION 6 WARNING --\r\nIf your Vim is older than version 7, then the after\/colors scripts will only be loaded once when Vim starts.  This will not be a problem if you choose your colorscheme in your .vimrc file, but if you change your colorscheme after vim has loaded then your after\/colors scripts will be ignored.  This is not an issue in Vim 7.\r\n\r\n\r\nIn case of problems, you can email me: <toomuchphp-vim at yahoo.com>\r\n","install_details":"1) Put AfterColors.vim in ~\/.vim\/plugin\/ or $HOME\\vimfiles\\plugin\\\r\n2) Create your colorscheme customizations in after\/colors\/<colors_name>.vim\r\n3) Create global customizations (for all colorschemes) in after\/colors\/common.vim","5":"1) Put AfterColors.vim in ~\/.vim\/plugin\/ or $HOME\\vimfiles\\plugin\\\r\n2) Create your colorscheme customizations in after\/colors\/<colors_name>.vim\r\n3) Create global customizations (for all colorschemes) in after\/colors\/common.vim","first_name":"Peter","6":"Peter","last_name":"Hodge","7":"Hodge","releases":[{"0":"1641","vim_version":"6.0","1":"6.0","script_version":"1.3","2":"1.3","version_comment":"Added checks for required vim version and features","3":"Added checks for required vim version and features","package":"AfterColors.tar.gz","4":"AfterColors.tar.gz","src_id":"8679","5":"8679","creation_date":"1210607488","6":"1210607488"},{"0":"1641","vim_version":"6.0","1":"6.0","script_version":"1.2B","2":"1.2B","version_comment":"Can now load after\/colors scripts in Vim 6, but only on startup, provided you choose the colorscheme inside your .vimrc script.  (Sorry, version 1.2 had a bug in it which broke in Vim 7, 1.2B is fixed.)","3":"Can now load after\/colors scripts in Vim 6, but only on startup, provided you choose the colorscheme inside your .vimrc script.  (Sorry, version 1.2 had a bug in it which broke in Vim 7, 1.2B is fixed.)","package":"AfterColors.tar.gz","4":"AfterColors.tar.gz","src_id":"6473","5":"6473","creation_date":"1164565695","6":"1164565695"},{"0":"1641","vim_version":"6.0","1":"6.0","script_version":"1.2","2":"1.2","version_comment":"Can now load after\/colors scripts in Vim 6 (but only on startup, provided you choose the colorscheme inside your .vimrc script).","3":"Can now load after\/colors scripts in Vim 6 (but only on startup, provided you choose the colorscheme inside your .vimrc script).","package":"AfterColors.tar.gz","4":"AfterColors.tar.gz","src_id":"6472","5":"6472","creation_date":"1164558567","6":"1164558567"},{"0":"1641","vim_version":"7.0","1":"7.0","script_version":"1.1","2":"1.1","version_comment":"Now looks for customizations in 'after\/colors\/common.vim' for all colorschemes. Thanks to Vincent Wang for this suggestion.","3":"Now looks for customizations in 'after\/colors\/common.vim' for all colorschemes. Thanks to Vincent Wang for this suggestion.","package":"AfterColors.tar.gz","4":"AfterColors.tar.gz","src_id":"6095","5":"6095","creation_date":"1156439614","6":"1156439614"},{"0":"1641","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"AfterColors.tar.gz","4":"AfterColors.tar.gz","src_id":"6094","5":"6094","creation_date":"1156355768","6":"1156355768"}]},"1640":{"script_id":"1640","0":"1640","script_name":"cpp.vim","1":"cpp.vim","script_type":"syntax","2":"syntax","summary":"Extends C++ syntax highlighting to STL classes and method names","3":"Extends C++ syntax highlighting to STL classes and method names","description":"My cpp.vim is intended to replace the cpp.vim that comes with the Vim package (the author of the original is Ken Shan <ccshan@post.harvard.edu>).  It extends the original cpp.vim's C++ syntax highlighting to SGI STL classes and method names (including, e.g., hash_map and hash_set, which do not appear in the official STL).  The color of STL identifiers is distinct from all other colors used by the cpp.vim syntax scheme.\r\n\r\nAs C++ evolves, future versions of this syntax file will reflect any official additions to the standard library, i.e. Boost.  (May happen earlier, depending on user requests.)\r\n\r\nThe STL highlighting scheme is applied to the following words:\r\n\r\nabort abs accumulate acos adjacent_difference adjacent_find any append asctime asin assert assign at atan atan2 atexit atof atoi atol auto_ptr back back_inserter bad bad_alloc bad_cast bad_exception bad_typeid badbit begin binary_compose binary_negate binary_search binder1st binder2nd bitset bsearch c_str calloc capacity ceil cerr cin clear clearerr clock clog close compare const_iterator construct copy copy_backward copy_n cos cosh count count_if cout ctime data deque destroy difftime div domain_error empty end endl eof eofbit equal equal_range erase exception exit exp fabs fail failbit failure fclose feof ferror fflush fgetc fgetpos fgets fill fill_n find find_end find_first_not_of find_first_of find_if find_last_not_of find_last_of flags flip floor flush fmod fopen for_each fprintf fputc fputs fread free freopen frexp front fscanf fseek fsetpos fstream ftell fwrite gcount generate generate_n get_temporary_buffer getc getchar getenv getline gets gmtime good goodbit hash_map hash_multimap hash_multiset hash_set i2s ifstream ignore includes inner_product inplace_merge insert invalid_argument ios ios_base iostate iota is_heap is_open is_sorted isalnum isalpha iscntrl isdigit isgraph islower isprint ispunct isspace istream istream_iterator isupper isxdigit iter_swap iterator key_comp ldiv length length_error lexicographical_compare lexicographical_compare_3way list localtime log log10 logic_error longjmp lower_bound make_heap malloc map max max_element max_size mem_fun mem_fun1 mem_fun1_ref mem_fun_ref memchr memcpy memmove memset merge min min_element mismatch mktime modf multimap multiset next_permutation npos nth_element ofstream open ostream ostream_iterator out_of_range overflow_error pair partial_sort partial_sort_copy partial_sum partition peek perror pointer_to_binary_function pointer_to_unary_function pop pop_back pop_front pop_heap pow power precision prev_permutation printf ptr_fun push push_back push_front push_heap put putback putc putchar puts qsort raise rand random_sample random_sample_n random_shuffle range_error rbegin rdbuf rdstate read realloc remove remove_copy remove_copy_if remove_if rename rend replace replace_copy replace_copy_if replace_if reserve reset resize return_temporary_buffer reverse reverse_copy rewind rfind rotate rotate_copy runtime_error scanf search search_n seekg seekp set set_difference set_intersection set_symmetric_difference set_union setbuf setf setjmp setlocale setvbuf signal sin sinh size size_t sort sort_heap splice sprintf sqrt srand sscanf stable_partition stable_sort std str strcat strchr strcmp strcoll strcpy strcspn strerror strftime string strlen strncat strncmp strncpy strpbrk strrchr strspn strstr strtod strtok strtol strtoul strxfrm substr swap swap_ranges sync_with_stdio system tan tanh tellg tellp temporary_buffer test time time_t tmpfile tmpnam to_string to_ulong tolower top toupper transform unary_compose unary_negate underflow_error unget ungetc uninitialized_copy uninitialized_copy_n uninitialized_fill uninitialized_fill_n unique unique_copy unsetf upper_bound va_arg value_comp vector vfprintf vprintf vsprintf width write\r\n","4":"My cpp.vim is intended to replace the cpp.vim that comes with the Vim package (the author of the original is Ken Shan <ccshan@post.harvard.edu>).  It extends the original cpp.vim's C++ syntax highlighting to SGI STL classes and method names (including, e.g., hash_map and hash_set, which do not appear in the official STL).  The color of STL identifiers is distinct from all other colors used by the cpp.vim syntax scheme.\r\n\r\nAs C++ evolves, future versions of this syntax file will reflect any official additions to the standard library, i.e. Boost.  (May happen earlier, depending on user requests.)\r\n\r\nThe STL highlighting scheme is applied to the following words:\r\n\r\nabort abs accumulate acos adjacent_difference adjacent_find any append asctime asin assert assign at atan atan2 atexit atof atoi atol auto_ptr back back_inserter bad bad_alloc bad_cast bad_exception bad_typeid badbit begin binary_compose binary_negate binary_search binder1st binder2nd bitset bsearch c_str calloc capacity ceil cerr cin clear clearerr clock clog close compare const_iterator construct copy copy_backward copy_n cos cosh count count_if cout ctime data deque destroy difftime div domain_error empty end endl eof eofbit equal equal_range erase exception exit exp fabs fail failbit failure fclose feof ferror fflush fgetc fgetpos fgets fill fill_n find find_end find_first_not_of find_first_of find_if find_last_not_of find_last_of flags flip floor flush fmod fopen for_each fprintf fputc fputs fread free freopen frexp front fscanf fseek fsetpos fstream ftell fwrite gcount generate generate_n get_temporary_buffer getc getchar getenv getline gets gmtime good goodbit hash_map hash_multimap hash_multiset hash_set i2s ifstream ignore includes inner_product inplace_merge insert invalid_argument ios ios_base iostate iota is_heap is_open is_sorted isalnum isalpha iscntrl isdigit isgraph islower isprint ispunct isspace istream istream_iterator isupper isxdigit iter_swap iterator key_comp ldiv length length_error lexicographical_compare lexicographical_compare_3way list localtime log log10 logic_error longjmp lower_bound make_heap malloc map max max_element max_size mem_fun mem_fun1 mem_fun1_ref mem_fun_ref memchr memcpy memmove memset merge min min_element mismatch mktime modf multimap multiset next_permutation npos nth_element ofstream open ostream ostream_iterator out_of_range overflow_error pair partial_sort partial_sort_copy partial_sum partition peek perror pointer_to_binary_function pointer_to_unary_function pop pop_back pop_front pop_heap pow power precision prev_permutation printf ptr_fun push push_back push_front push_heap put putback putc putchar puts qsort raise rand random_sample random_sample_n random_shuffle range_error rbegin rdbuf rdstate read realloc remove remove_copy remove_copy_if remove_if rename rend replace replace_copy replace_copy_if replace_if reserve reset resize return_temporary_buffer reverse reverse_copy rewind rfind rotate rotate_copy runtime_error scanf search search_n seekg seekp set set_difference set_intersection set_symmetric_difference set_union setbuf setf setjmp setlocale setvbuf signal sin sinh size size_t sort sort_heap splice sprintf sqrt srand sscanf stable_partition stable_sort std str strcat strchr strcmp strcoll strcpy strcspn strerror strftime string strlen strncat strncmp strncpy strpbrk strrchr strspn strstr strtod strtok strtol strtoul strxfrm substr swap swap_ranges sync_with_stdio system tan tanh tellg tellp temporary_buffer test time time_t tmpfile tmpnam to_string to_ulong tolower top toupper transform unary_compose unary_negate underflow_error unget ungetc uninitialized_copy uninitialized_copy_n uninitialized_fill uninitialized_fill_n unique unique_copy unsetf upper_bound va_arg value_comp vector vfprintf vprintf vsprintf width write\r\n","install_details":"Make a backup copy of syntax\/vim.cpp and overwrite syntax\/vim.cpp with this file.","5":"Make a backup copy of syntax\/vim.cpp and overwrite syntax\/vim.cpp with this file.","first_name":"Nathan","6":"Nathan","last_name":"Skvirsky","7":"Skvirsky","releases":[{"0":"1640","vim_version":"5.7","1":"5.7","script_version":"1.12","2":"1.12","version_comment":"Added more STL reserved words","3":"Added more STL reserved words","package":"cpp.vim","4":"cpp.vim","src_id":"6320","5":"6320","creation_date":"1161541634","6":"1161541634"},{"0":"1640","vim_version":"5.7","1":"5.7","script_version":"1.1","2":"1.1","version_comment":"Initial upload","3":"Initial upload","package":"cpp.vim","4":"cpp.vim","src_id":"6093","5":"6093","creation_date":"1156335300","6":"1156335300"}]},"1639":{"script_id":"1639","0":"1639","script_name":"MultiTabs","1":"MultiTabs","script_type":"utility","2":"utility","summary":"Open N files, each one in his own tab, like this:  :NTAB file1 file2 ... fileN","3":"Open N files, each one in his own tab, like this:  :NTAB file1 file2 ... fileN","description":"Open N files, each one in his own tab, like this: \r\n    :NTAB file1 file2 ... fileN\r\n\r\nSynonyms:    :NTABS, :ETABS, TABS, OPENTABS\r\n\r\nEnjoy.\r\n\r\nYakov Lerner","4":"Open N files, each one in his own tab, like this: \r\n    :NTAB file1 file2 ... fileN\r\n\r\nSynonyms:    :NTABS, :ETABS, TABS, OPENTABS\r\n\r\nEnjoy.\r\n\r\nYakov Lerner","install_details":"1. Download the script and copy it into your ~\/.vim\/plugin directory.\r\n2. If ~\/.vim\/plugin directory does not exist, create it using command:\r\n                          mkdir -p ~\/.vim\/plugin directory.\r\n3. Restart vim.\r\n\r\n","5":"1. Download the script and copy it into your ~\/.vim\/plugin directory.\r\n2. If ~\/.vim\/plugin directory does not exist, create it using command:\r\n                          mkdir -p ~\/.vim\/plugin directory.\r\n3. Restart vim.\r\n\r\n","first_name":"Yakov","6":"Yakov","last_name":"Lerner","7":"Lerner","releases":[{"0":"1639","vim_version":"7.0","1":"7.0","script_version":"060823","2":"060823","version_comment":"Initial upload","3":"Initial upload","package":"newtabs.vim","4":"newtabs.vim","src_id":"6092","5":"6092","creation_date":"1156326376","6":"1156326376"}]},"1638":{"script_id":"1638","0":"1638","script_name":"SourceCodeObedience","1":"SourceCodeObedience","script_type":"ftplugin","2":"ftplugin","summary":"Browse source code easily with cscope, ctags and marks system","3":"Browse source code easily with cscope, ctags and marks system","description":"PURPOSE\r\n\r\nResearch source code.\r\nSupport source code.\r\n\r\nREQUIREMENT\r\n\r\nCscope: http:\/\/cscope.sourceforge.net\/\r\nCtags: http:\/\/ctags.sourceforge.net\/\r\n\r\nwithout cscope and ctags you can use only marks.\r\n\r\nUSAGE\r\n\r\n--NEW--:  mark commands ability added. read sco_command_feature.sco with vim about new feature\r\n\r\nFirst step:\r\n   Create new file with \"sco\" extension: [g]vim my_name.sco\r\n   Read help.\r\n   Change settings at the beginig of sco file\r\n\r\n   Execute one of the commands\r\n       :SCOSymbol 'class' (for example)\r\n       :SCOGlobal 'main'\r\n       :SCOWhoCall 'setValue'\r\n       :SCOFile 'main'\r\n       :SCOInclude 'stdafx.h'\r\n       :SCOText 'Enter password'\r\n       :SCOGrep ' \".*\" '\r\n       :SCOTag 'gui'\r\n       :SCOClassInfo 'class[struct]name' (cant take some time)\r\n\r\nSecond step:\r\n   Unfold result.\r\n   Filter result (:Delete :Leave :Filter commands)\r\n   Preview result (:Preview command or c<Space>p)\r\n   Preview result using :SCOUp :SCODown commands ( map them on keys <C-Up> <C-Down> for example )\r\n   Select appropriate row and press <Enter> to open file for edit.\r\n\r\nThird step:\r\n   Move inside file.\r\n   Select interesting line.\r\n   Execute :SCOMark command (c<Space>m) or :SCOMarkSmart (c<Space>n)\r\n\r\n   Use :SCOMarkSmart for store results for future\r\n   Change caption of the marks with  :Caption ['sometext'] command or :FileNameCaption\r\n\r\n   Use vim search and then :SCOSaveSearch(c<Space>s) to quick overview of find result and to select appropriate one ( To avoid multi n pressing )\r\n\r\n   Execute :AppendPlace to select place where new marks will be appear ( example http:\/\/groups.google.com\/group\/SourceCodeObedience\/web\/content-example )\r\n\r\n   Use :SCOReMark for change marks point\r\n\r\nFourth step:\r\n   Add tags and header information to your marks and text description to quick find later with http:\/\/www.vim.org\/scripts\/script.php?script_id=1791\r\n\r\nheader: creation of database connection\r\n   tags: connection, create, database\r\nsome text\r\n    SCOMark\r\n\r\nDebug step:\r\n\r\n  when you are going to understand source code with debugger (gdb) you should to use \r\n    :TransferToMarks command.\r\nCopy backtrace lines to sco file. Select them and :TransferToMarks.\r\n\r\nDiscuss step:\r\n\r\nhttp:\/\/groups.google.com\/group\/SourceCodeObedience\/topics\r\n\r\nCSCOPE\r\n\r\nYou don't need to create cscope connection.\r\nWhat cscope data base to use you can set by adding (added automatically when sco file first created)\r\n\r\n% cscope_db: cscope.out\r\n\r\nin the begining of sco file.\r\nAs a result you can have many sco buffers with different cscope connections.\r\nIf your cscope executable installed not in standart place - you can change path to cscope by adding\r\n\r\n% cscope_exe: \/my_path\/cscope\r\n\r\nin the begining of sco file.\r\n\r\nCTAGS\r\n\r\nIf you want to use :SCOClassInfo you must have tag file generated with ctags --fields=fks (default settings)\r\n\r\nChange % tags_db: path_to_tag_file at the begining of sco file to path for your tag file\r\n\r\nVIMRC\r\n\r\nset \r\ng:sco_default_db\r\ng:sco_default_exe \r\ng:sco_default_tags in your .vimrc to avoid continual change first lines of newly created .sco files\r\n\r\nExample \r\nlet g:sco_default_db = \/home\/ni\/cscope.out\r\nlet g:sco_default_exe = \/home\/ni\/bin\/cscope\r\nlet g:sco_default_tags = \/home\/ni\/tags","4":"PURPOSE\r\n\r\nResearch source code.\r\nSupport source code.\r\n\r\nREQUIREMENT\r\n\r\nCscope: http:\/\/cscope.sourceforge.net\/\r\nCtags: http:\/\/ctags.sourceforge.net\/\r\n\r\nwithout cscope and ctags you can use only marks.\r\n\r\nUSAGE\r\n\r\n--NEW--:  mark commands ability added. read sco_command_feature.sco with vim about new feature\r\n\r\nFirst step:\r\n   Create new file with \"sco\" extension: [g]vim my_name.sco\r\n   Read help.\r\n   Change settings at the beginig of sco file\r\n\r\n   Execute one of the commands\r\n       :SCOSymbol 'class' (for example)\r\n       :SCOGlobal 'main'\r\n       :SCOWhoCall 'setValue'\r\n       :SCOFile 'main'\r\n       :SCOInclude 'stdafx.h'\r\n       :SCOText 'Enter password'\r\n       :SCOGrep ' \".*\" '\r\n       :SCOTag 'gui'\r\n       :SCOClassInfo 'class[struct]name' (cant take some time)\r\n\r\nSecond step:\r\n   Unfold result.\r\n   Filter result (:Delete :Leave :Filter commands)\r\n   Preview result (:Preview command or c<Space>p)\r\n   Preview result using :SCOUp :SCODown commands ( map them on keys <C-Up> <C-Down> for example )\r\n   Select appropriate row and press <Enter> to open file for edit.\r\n\r\nThird step:\r\n   Move inside file.\r\n   Select interesting line.\r\n   Execute :SCOMark command (c<Space>m) or :SCOMarkSmart (c<Space>n)\r\n\r\n   Use :SCOMarkSmart for store results for future\r\n   Change caption of the marks with  :Caption ['sometext'] command or :FileNameCaption\r\n\r\n   Use vim search and then :SCOSaveSearch(c<Space>s) to quick overview of find result and to select appropriate one ( To avoid multi n pressing )\r\n\r\n   Execute :AppendPlace to select place where new marks will be appear ( example http:\/\/groups.google.com\/group\/SourceCodeObedience\/web\/content-example )\r\n\r\n   Use :SCOReMark for change marks point\r\n\r\nFourth step:\r\n   Add tags and header information to your marks and text description to quick find later with http:\/\/www.vim.org\/scripts\/script.php?script_id=1791\r\n\r\nheader: creation of database connection\r\n   tags: connection, create, database\r\nsome text\r\n    SCOMark\r\n\r\nDebug step:\r\n\r\n  when you are going to understand source code with debugger (gdb) you should to use \r\n    :TransferToMarks command.\r\nCopy backtrace lines to sco file. Select them and :TransferToMarks.\r\n\r\nDiscuss step:\r\n\r\nhttp:\/\/groups.google.com\/group\/SourceCodeObedience\/topics\r\n\r\nCSCOPE\r\n\r\nYou don't need to create cscope connection.\r\nWhat cscope data base to use you can set by adding (added automatically when sco file first created)\r\n\r\n% cscope_db: cscope.out\r\n\r\nin the begining of sco file.\r\nAs a result you can have many sco buffers with different cscope connections.\r\nIf your cscope executable installed not in standart place - you can change path to cscope by adding\r\n\r\n% cscope_exe: \/my_path\/cscope\r\n\r\nin the begining of sco file.\r\n\r\nCTAGS\r\n\r\nIf you want to use :SCOClassInfo you must have tag file generated with ctags --fields=fks (default settings)\r\n\r\nChange % tags_db: path_to_tag_file at the begining of sco file to path for your tag file\r\n\r\nVIMRC\r\n\r\nset \r\ng:sco_default_db\r\ng:sco_default_exe \r\ng:sco_default_tags in your .vimrc to avoid continual change first lines of newly created .sco files\r\n\r\nExample \r\nlet g:sco_default_db = \/home\/ni\/cscope.out\r\nlet g:sco_default_exe = \/home\/ni\/bin\/cscope\r\nlet g:sco_default_tags = \/home\/ni\/tags","install_details":"unzip sco.zip into your plugin folder","5":"unzip sco.zip into your plugin folder","first_name":"Mykola","6":"Mykola","last_name":"Golubyev","7":"Golubyev","releases":[{"0":"1638","vim_version":"7.0","1":"7.0","script_version":"4.02","2":"4.02","version_comment":"Mark with command ability added.\r\nopen  sco_command_feature.sco from sco.zip arhcive with vim to read about new feature.\r\nBug fix with sco options parse.","3":"Mark with command ability added.\r\nopen  sco_command_feature.sco from sco.zip arhcive with vim to read about new feature.\r\nBug fix with sco options parse.","package":"sco.zip","4":"sco.zip","src_id":"7476","5":"7476","creation_date":"1186616909","6":"1186616909"},{"0":"1638","vim_version":"7.0","1":"7.0","script_version":"4.01","2":"4.01","version_comment":"small bug fix. remove error messages that wasn't at previous versions.","3":"small bug fix. remove error messages that wasn't at previous versions.","package":"sco.zip","4":"sco.zip","src_id":"7470","5":"7470","creation_date":"1186568699","6":"1186568699"},{"0":"1638","vim_version":"7.0","1":"7.0","script_version":"4.0","2":"4.0","version_comment":"Mark with command ability added.\r\nopen  sco_command_feature.sco from sco.zip arhcive with vim to read about new feature.","3":"Mark with command ability added.\r\nopen  sco_command_feature.sco from sco.zip arhcive with vim to read about new feature.","package":"sco.zip","4":"sco.zip","src_id":"7462","5":"7462","creation_date":"1186539687","6":"1186539687"},{"0":"1638","vim_version":"7.0","1":"7.0","script_version":"3.3","2":"3.3","version_comment":"result output headers changed to be with tags: information. SCOSaveSearch rewrited to work faster and  without bugs. changed colors for tag list in tags: line","3":"result output headers changed to be with tags: information. SCOSaveSearch rewrited to work faster and  without bugs. changed colors for tag list in tags: line","package":"sco.zip","4":"sco.zip","src_id":"7382","5":"7382","creation_date":"1184832600","6":"1184832600"},{"0":"1638","vim_version":"7.0","1":"7.0","script_version":"3.241","2":"3.241","version_comment":":SCOSaveSearch bugged on linux. Fixed. Please check.","3":":SCOSaveSearch bugged on linux. Fixed. Please check.","package":"sco.zip","4":"sco.zip","src_id":"7128","5":"7128","creation_date":"1179375120","6":"1179375120"},{"0":"1638","vim_version":"7.0","1":"7.0","script_version":"3.24","2":"3.24","version_comment":":SCOMarkSmart changed to work with :g\/pattern\/SCOMarkSmart. :SCOSaveSearch (c<space>s by default) command added to store all lines with last pattern to sco buffer as marks. create new .sco file and read help.","3":":SCOMarkSmart changed to work with :g\/pattern\/SCOMarkSmart. :SCOSaveSearch (c<space>s by default) command added to store all lines with last pattern to sco buffer as marks. create new .sco file and read help.","package":"sco.zip","4":"sco.zip","src_id":"7127","5":"7127","creation_date":"1179367740","6":"1179367740"},{"0":"1638","vim_version":"7.0","1":"7.0","script_version":"3.2","2":"3.2","version_comment":":AppendPlace added. Select place where you want to add marks in sco file. Execute :AppendPlace on any line in sco buffer. Every :AddMark[Smart]  will add marks staring from that line and exactly in that sco buffer.\r\nsco_keys.vim added to change hot keys.","3":":AppendPlace added. Select place where you want to add marks in sco file. Execute :AppendPlace on any line in sco buffer. Every :AddMark[Smart]  will add marks staring from that line and exactly in that sco buffer.\r\nsco_keys.vim added to change hot keys.","package":"sco.zip","4":"sco.zip","src_id":"6934","5":"6934","creation_date":"1175502817","6":"1175502817"},{"0":"1638","vim_version":"7.0","1":"7.0","script_version":"3","2":"3","version_comment":":TransferToMarks command to convert back trace ( tested on gdb ) to smart marks. Create new sco file and read help","3":":TransferToMarks command to convert back trace ( tested on gdb ) to smart marks. Create new sco file and read help","package":"sco.vim","4":"sco.vim","src_id":"6921","5":"6921","creation_date":"1175245305","6":"1175245305"},{"0":"1638","vim_version":"7.0","1":"7.0","script_version":"2.92","2":"2.92","version_comment":":SCOReMark added ( c<Space>r ) to point current mark to another place: for repair broken marks","3":":SCOReMark added ( c<Space>r ) to point current mark to another place: for repair broken marks","package":"sco.vim","4":"sco.vim","src_id":"6914","5":"6914","creation_date":"1175061214","6":"1175061214"},{"0":"1638","vim_version":"7.0","1":"7.0","script_version":"2.9","2":"2.9","version_comment":":FileNameCaption added ( create new .sco file ( [g]vim newfile.sco ) and read help )","3":":FileNameCaption added ( create new .sco file ( [g]vim newfile.sco ) and read help )","package":"sco.vim","4":"sco.vim","src_id":"6896","5":"6896","creation_date":"1174465279","6":"1174465279"},{"0":"1638","vim_version":"7.0","1":"7.0","script_version":"2.81","2":"2.81","version_comment":"remove bug with :SCONext in cases when there is only one .sco file in buffer list and it is first","3":"remove bug with :SCONext in cases when there is only one .sco file in buffer list and it is first","package":"sco.vim","4":"sco.vim","src_id":"6762","5":"6762","creation_date":"1172030833","6":"1172030833"},{"0":"1638","vim_version":"7.0","1":"7.0","script_version":"2.8","2":"2.8","version_comment":"added :header highlight for use with tagscan.vim","3":"added :header highlight for use with tagscan.vim","package":"sco.vim","4":"sco.vim","src_id":"6722","5":"6722","creation_date":"1170656942","6":"1170656942"},{"0":"1638","vim_version":"7.0","1":"7.0","script_version":"2.7","2":"2.7","version_comment":"Added highlight for records like\r\ntags: tag1, tag2, tag3 \r\ntags: create, gui, file\r\nto use with tagscan.vim","3":"Added highlight for records like\r\ntags: tag1, tag2, tag3 \r\ntags: create, gui, file\r\nto use with tagscan.vim","package":"sco.vim","4":"sco.vim","src_id":"6707","5":"6707","creation_date":"1170395872","6":"1170395872"},{"0":"1638","vim_version":"7.0","1":"7.0","script_version":"2.6","2":"2.6","version_comment":":SCOPrevious :SCONext commands added to switch between different sco buffers ( interfaces.sco; bugs.sco; breakpoints.sco; etc.. ) Map them on <C-Left> <C-Right> for example.\r\nCreate new sco file and read help.","3":":SCOPrevious :SCONext commands added to switch between different sco buffers ( interfaces.sco; bugs.sco; breakpoints.sco; etc.. ) Map them on <C-Left> <C-Right> for example.\r\nCreate new sco file and read help.","package":"sco.vim","4":"sco.vim","src_id":"6684","5":"6684","creation_date":"1170048593","6":"1170048593"},{"0":"1638","vim_version":"7.0","1":"7.0","script_version":"2.5","2":"2.5","version_comment":"Select several lines in sco buffer (visual mode) and press 'o'.\r\nTry it. \r\n ( Create new .sco file and read help )","3":"Select several lines in sco buffer (visual mode) and press 'o'.\r\nTry it. \r\n ( Create new .sco file and read help )","package":"sco.vim","4":"sco.vim","src_id":"6642","5":"6642","creation_date":"1169459537","6":"1169459537"},{"0":"1638","vim_version":"7.0","1":"7.0","script_version":"2.41","2":"2.41","version_comment":"Removed bug with smart mark lines with '||' symbol","3":"Removed bug with smart mark lines with '||' symbol","package":"sco.vim","4":"sco.vim","src_id":"6614","5":"6614","creation_date":"1168847624","6":"1168847624"},{"0":"1638","vim_version":"7.0","1":"7.0","script_version":"2.4","2":"2.4","version_comment":"added useful commands\r\n:SCOUp \r\n:SCODown\r\n( create new .sco file and read help )\r\nMap them for example to <C-Up> and <C-Down> for fast browsing","3":"added useful commands\r\n:SCOUp \r\n:SCODown\r\n( create new .sco file and read help )\r\nMap them for example to <C-Up> and <C-Down> for fast browsing","package":"sco.vim","4":"sco.vim","src_id":"6513","5":"6513","creation_date":"1165998494","6":"1165998494"},{"0":"1638","vim_version":"7.0","1":"7.0","script_version":"2.3","2":"2.3","version_comment":":SCOTag 'tag_regexp' - add tags information to sco buffer.\r\n:SCOTag '' - add information about tag under cursor (c<Space>t)","3":":SCOTag 'tag_regexp' - add tags information to sco buffer.\r\n:SCOTag '' - add information about tag under cursor (c<Space>t)","package":"sco.vim","4":"sco.vim","src_id":"6306","5":"6306","creation_date":"1161332559","6":"1161332559"},{"0":"1638","vim_version":"7.0","1":"7.0","script_version":"2.2","2":"2.2","version_comment":"Command :SCOClassInfo '' generate information about all classes.\r\nFix Bug with \"can't find pattern\" (unescape '\/' symbol when jump to tag)","3":"Command :SCOClassInfo '' generate information about all classes.\r\nFix Bug with \"can't find pattern\" (unescape '\/' symbol when jump to tag)","package":"sco.vim","4":"sco.vim","src_id":"6294","5":"6294","creation_date":"1161165227","6":"1161165227"},{"0":"1638","vim_version":"7.0","1":"7.0","script_version":"2.1","2":"2.1","version_comment":"Added command :SCOClassInfo 'class[stuct]name' which build tree info (members, methods, inner classes with methods and members) about class. Command used tag file builded with ctags. Tested for c++. Execution of this command can take some time. Create new .sco file and set parametr tags_db equal to path for your tag file. \r\n","3":"Added command :SCOClassInfo 'class[stuct]name' which build tree info (members, methods, inner classes with methods and members) about class. Command used tag file builded with ctags. Tested for c++. Execution of this command can take some time. Create new .sco file and set parametr tags_db equal to path for your tag file. \r\n","package":"sco.vim","4":"sco.vim","src_id":"6289","5":"6289","creation_date":"1161005508","6":"1161005508"},{"0":"1638","vim_version":"7.0","1":"7.0","script_version":"2.0","2":"2.0","version_comment":"New appearance of smart marks. New appearance of folds at all.\r\nAdded captions to smart marks. Added hot keys to work in visual mode. Create new file with sco extension and read help","3":"New appearance of smart marks. New appearance of folds at all.\r\nAdded captions to smart marks. Added hot keys to work in visual mode. Create new file with sco extension and read help","package":"sco.vim","4":"sco.vim","src_id":"6258","5":"6258","creation_date":"1160125222","6":"1160125222"},{"0":"1638","vim_version":"7.0","1":"7.0","script_version":"1.1.1","2":"1.1.1","version_comment":"Fix bug. Smart marks didn't worked at lines with \" * [ ] \" symbols","3":"Fix bug. Smart marks didn't worked at lines with \" * [ ] \" symbols","package":"sco.vim","4":"sco.vim","src_id":"6255","5":"6255","creation_date":"1160039856","6":"1160039856"},{"0":"1638","vim_version":"7.0","1":"7.0","script_version":"1.1","2":"1.1","version_comment":"New kind of marks added (smart marks).\r\n:Allign command added. (create new sco file and read help for details)","3":"New kind of marks added (smart marks).\r\n:Allign command added. (create new sco file and read help for details)","package":"sco.vim","4":"sco.vim","src_id":"6243","5":"6243","creation_date":"1159845722","6":"1159845722"},{"0":"1638","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Rewrited in pure vim language. Not need vim's perl support. Not need vim's cscope support.\r\nAdded auto align of marks.","3":"Rewrited in pure vim language. Not need vim's perl support. Not need vim's cscope support.\r\nAdded auto align of marks.","package":"sco.vim","4":"sco.vim","src_id":"6232","5":"6232","creation_date":"1159255881","6":"1159255881"}]},"1637":{"script_id":"1637","0":"1637","script_name":"myfold.vim","1":"myfold.vim","script_type":"utility","2":"utility","summary":"make it easy to open\/close fold and foldcolumn","3":"make it easy to open\/close fold and foldcolumn","description":"NOT MAINTAINED , I don't recommend you to use this script, this was script I created when I was vim newbee. \r\n\r\n\r\n\r\n\r\nThis plugin provide functionality to enable or disalbe\r\nfold more easier.\r\ntwo command wil added.\r\n\r\n:MyFoldEnable\r\n:MyFoldDisable\r\n\r\nParameters are based on my favorite setting( syntax base ), so please modify\r\nthese values directly in function if you need.\r\n\r\n\r\n","4":"NOT MAINTAINED , I don't recommend you to use this script, this was script I created when I was vim newbee. \r\n\r\n\r\n\r\n\r\nThis plugin provide functionality to enable or disalbe\r\nfold more easier.\r\ntwo command wil added.\r\n\r\n:MyFoldEnable\r\n:MyFoldDisable\r\n\r\nParameters are based on my favorite setting( syntax base ), so please modify\r\nthese values directly in function if you need.\r\n\r\n\r\n","install_details":"-----------------------------\r\n** Install\r\n-----------------------------\r\n1. put this file to $HOME\/.vim\/plugin folder or other.\r\n2. start vim and edit an source code.\r\n3. now, you can type two commands, from vim command mode.\r\n\r\n:MyFoldEnable\r\n:MyFoldDisable\r\n\r\n-----------------------------\r\n** My private hilight and keymap in ~\/.vimrc\r\n-----------------------------\r\n# I don't like default fold hilight( I always use vim via SSH cterm ).\r\nhighlight Folded ctermfg=6 ctermbg=0\r\nhighlight FoldColumn ctermfg=6 ctermbg=0\r\n\r\n# set keyboard shortcut.\r\nnnoremap <silent> <F4> :MyFoldEnable<CR>\r\nnnoremap <silent> <F5> :MyFoldDisable<CR>\r\n\r\n-----------------------------\r\n** Short Tutorial\r\n-----------------------------\r\n1. edit program file( I like ruby ).\r\n  vim proglam.rb\r\n\r\n2. type <F4> key in normal mode.\r\n  you can see folded lines( by syntax )and foldcolumn.\r\n\r\n3. type <F4> key in normal mode.\r\n  hide foldcolumn. not change open\/close state each fold.\r\n\r\n4. type <F5> key in normal mode.\r\n  open all fold and hide foldcolumn.","5":"-----------------------------\r\n** Install\r\n-----------------------------\r\n1. put this file to $HOME\/.vim\/plugin folder or other.\r\n2. start vim and edit an source code.\r\n3. now, you can type two commands, from vim command mode.\r\n\r\n:MyFoldEnable\r\n:MyFoldDisable\r\n\r\n-----------------------------\r\n** My private hilight and keymap in ~\/.vimrc\r\n-----------------------------\r\n# I don't like default fold hilight( I always use vim via SSH cterm ).\r\nhighlight Folded ctermfg=6 ctermbg=0\r\nhighlight FoldColumn ctermfg=6 ctermbg=0\r\n\r\n# set keyboard shortcut.\r\nnnoremap <silent> <F4> :MyFoldEnable<CR>\r\nnnoremap <silent> <F5> :MyFoldDisable<CR>\r\n\r\n-----------------------------\r\n** Short Tutorial\r\n-----------------------------\r\n1. edit program file( I like ruby ).\r\n  vim proglam.rb\r\n\r\n2. type <F4> key in normal mode.\r\n  you can see folded lines( by syntax )and foldcolumn.\r\n\r\n3. type <F4> key in normal mode.\r\n  hide foldcolumn. not change open\/close state each fold.\r\n\r\n4. type <F5> key in normal mode.\r\n  open all fold and hide foldcolumn.","first_name":"t9md","6":"t9md","last_name":"jp","7":"jp","releases":[{"0":"1637","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"myfold.vim","4":"myfold.vim","src_id":"6078","5":"6078","creation_date":"1155846841","6":"1155846841"}]},"1636":{"script_id":"1636","0":"1636","script_name":"JDL syntax file","1":"JDL syntax file","script_type":"syntax","2":"syntax","summary":"Syntax highlighting for .jdl files (Job Description Language)","3":"Syntax highlighting for .jdl files (Job Description Language)","description":"Simple highlighting plugin.  It highlights most common attributes, operators, a lot of literals and wrong whitespace at the end of the line.\r\n\r\nReference: http:\/\/www.infn.it\/workload-grid\/docs\/DataGrid-01-TEN-0102-0_2-Document.pdf\r\n","4":"Simple highlighting plugin.  It highlights most common attributes, operators, a lot of literals and wrong whitespace at the end of the line.\r\n\r\nReference: http:\/\/www.infn.it\/workload-grid\/docs\/DataGrid-01-TEN-0102-0_2-Document.pdf\r\n","install_details":"","5":"","first_name":"Roberto","6":"Roberto","last_name":"Bonvallet","7":"Bonvallet","releases":[{"0":"1636","vim_version":"6.0","1":"6.0","script_version":"1","2":"1","version_comment":"Initial upload","3":"Initial upload","package":"jdl.vim","4":"jdl.vim","src_id":"6071","5":"6071","creation_date":"1155620631","6":"1155620631"}]},"1635":{"script_id":"1635","0":"1635","script_name":"candycode.vim","1":"candycode.vim","script_type":"color scheme","2":"color scheme","summary":"A colorful dark scheme with bright pastel colors","3":"A colorful dark scheme with bright pastel colors","description":"This is my personal colorscheme, which I've been carefully tweaking over the past couple years.  It uses a (nearly) black background contrasted with bright pastel colors, which I think are easy to read and rather purty, too.  I don't know of any colorschemes that are too similar, but then again I've only seen a fraction of the huge number that are out there.\r\n\r\nHTML \"screenshot\": http:\/\/goflyapig.googlepages.com\/candycodesample.html\r\nPNG screenshot: http:\/\/img98.imageshack.us\/img98\/9297\/screenshotcandycodevimvimcolorsgvim1ki2.png\r\n\r\nOptimized for the GUI version, but color terminal settings are included, too.","4":"This is my personal colorscheme, which I've been carefully tweaking over the past couple years.  It uses a (nearly) black background contrasted with bright pastel colors, which I think are easy to read and rather purty, too.  I don't know of any colorschemes that are too similar, but then again I've only seen a fraction of the huge number that are out there.\r\n\r\nHTML \"screenshot\": http:\/\/goflyapig.googlepages.com\/candycodesample.html\r\nPNG screenshot: http:\/\/img98.imageshack.us\/img98\/9297\/screenshotcandycodevimvimcolorsgvim1ki2.png\r\n\r\nOptimized for the GUI version, but color terminal settings are included, too.","install_details":"Just drop it in your .vim\/colors or vimfiles\/colors directory and then \":colorscheme candycode\".","5":"Just drop it in your .vim\/colors or vimfiles\/colors directory and then \":colorscheme candycode\".","first_name":"Justin","6":"Justin","last_name":"Constantino","7":"Constantino","releases":[{"0":"1635","vim_version":"7.0","1":"7.0","script_version":"1.0.1","2":"1.0.1","version_comment":"Saved and restored 'cpo' to avoid errors due to line-continuation when 'compatible' is set.","3":"Saved and restored 'cpo' to avoid errors due to line-continuation when 'compatible' is set.","package":"candycode.vim","4":"candycode.vim","src_id":"6066","5":"6066","creation_date":"1155423742","6":"1155423742"},{"0":"1635","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"candycode.vim","4":"candycode.vim","src_id":"6065","5":"6065","creation_date":"1155406360","6":"1155406360"}]},"1634":{"script_id":"1634","0":"1634","script_name":"matlab_run.vim","1":"matlab_run.vim","script_type":"ftplugin","2":"ftplugin","summary":"Run matlab script using Python for Windows users","3":"Run matlab script using Python for Windows users","description":"I no longer use Matlab nor Windows so I won't be able to improve this script any more.  Feel free to take over it and improve it.  \r\n\r\nRequired Python and its module win32com.  \r\nOnly in win32 platform.\r\n\r\nKnown successful versions\r\nWinXP, Python 2.4, Vim 7, Matlab 6.5\r\n\r\nPlease refer to tip#1298: http:\/\/www.vim.org\/tips\/tip.php?tip_id=1298\r\n(Thanks for the improvement from the comments.)\r\n\r\nHow to use:\r\nType ,r then it will save your file and run the file in Matlab.  The output from Matlab will be displayed in the current window.\r\n\r\nRemarks: \r\n1. Work for function file as well as script file, as long as the function does not require inputs.\r\n\r\n2. It will automatically add the path of your file using addpath in Matlab.  If you want to remove it you need to use rmpath in Matlab to do so manually. (Ignore this for version 1.1)\r\n\r\n3. It may take longer time than usual when you open an m file because it also starts Matlab.\r\n\r\n4. DO NOT close the Matlab Command Window.  It will close itself when you close your m files.\r\n\r\n5. For those of you who don't have Python but consider to install it, I recommand the enthought edition (http:\/\/code.enthought.com\/enthon\/) which includes pywin32.  As a Matlab user, you may also find scipy and numpy very useful in the future.","4":"I no longer use Matlab nor Windows so I won't be able to improve this script any more.  Feel free to take over it and improve it.  \r\n\r\nRequired Python and its module win32com.  \r\nOnly in win32 platform.\r\n\r\nKnown successful versions\r\nWinXP, Python 2.4, Vim 7, Matlab 6.5\r\n\r\nPlease refer to tip#1298: http:\/\/www.vim.org\/tips\/tip.php?tip_id=1298\r\n(Thanks for the improvement from the comments.)\r\n\r\nHow to use:\r\nType ,r then it will save your file and run the file in Matlab.  The output from Matlab will be displayed in the current window.\r\n\r\nRemarks: \r\n1. Work for function file as well as script file, as long as the function does not require inputs.\r\n\r\n2. It will automatically add the path of your file using addpath in Matlab.  If you want to remove it you need to use rmpath in Matlab to do so manually. (Ignore this for version 1.1)\r\n\r\n3. It may take longer time than usual when you open an m file because it also starts Matlab.\r\n\r\n4. DO NOT close the Matlab Command Window.  It will close itself when you close your m files.\r\n\r\n5. For those of you who don't have Python but consider to install it, I recommand the enthought edition (http:\/\/code.enthought.com\/enthon\/) which includes pywin32.  As a Matlab user, you may also find scipy and numpy very useful in the future.","install_details":"Download the file and put in $vim\/vimfiles\/ftplugin.","5":"Download the file and put in $vim\/vimfiles\/ftplugin.","first_name":"Manu","6":"Manu","last_name":"Hack","7":"Hack","releases":[{"0":"1634","vim_version":"7.0","1":"7.0","script_version":"1.2","2":"1.2","version_comment":"Polish the script a little bit.  \r\n\r\nIn this version it won't open Matlab when you open an m file.  But need to open Matlab before running scripts.  \r\n\r\ntype ,o to open Matlab.\r\ntype ,r to run.  \r\n\r\nCertainly you could map to your favorite keys.","3":"Polish the script a little bit.  \r\n\r\nIn this version it won't open Matlab when you open an m file.  But need to open Matlab before running scripts.  \r\n\r\ntype ,o to open Matlab.\r\ntype ,r to run.  \r\n\r\nCertainly you could map to your favorite keys.","package":"matlab_run.vim","4":"matlab_run.vim","src_id":"6116","5":"6116","creation_date":"1156983166","6":"1156983166"},{"0":"1634","vim_version":"7.0","1":"7.0","script_version":"1.1","2":"1.1","version_comment":"This version does not add path.  You can also run m files in different directory now.","3":"This version does not add path.  You can also run m files in different directory now.","package":"matlab_run.vim","4":"matlab_run.vim","src_id":"6063","5":"6063","creation_date":"1155294183","6":"1155294183"}]},"1633":{"script_id":"1633","0":"1633","script_name":"svncommand-tng","1":"svncommand-tng","script_type":"utility","2":"utility","summary":"Subversion (svn) Integration Plugin, the next generation (tng)","3":"Subversion (svn) Integration Plugin, the next generation (tng)","description":"This is an update to Adam Lazur's svncommand script, vimscript #922, which was itself based on the cvscommand script (now vcscommand), vimscript #90.\r\n\r\nKeywords: svn SVN svncommand subversion Subversion\r\n\r\nBasically I pulled a newer version of cvscommand (1.76) that had a lot of nice updates that I wanted to use with Subversion and did what Adam did, which is lots of 's\/CVS\/SVN\/'.  Then hacked on it till it worked like it was supposed to.  I also pulled in Adams SVNCommitDiff function for displaying a diff for a svn-commit.* file.  \r\n\r\nFinally, I added a few features of my very own:\r\n - Option to enable automatic execution of SVNCommitDiff when a svn-commit.* file is loaded.\r\n - A simple property editor.  SVNPropedit with no options runs \"svn proplist\" to give you a listing of all the set properties.  If given an argument, it grabs the property of that name and gives you a window to update the value in.\r\n \r\nThe vcscommand script has just been updated to support Subversion (8-10-06), but so far there is not a property editor or CommitDiff function.\r\n\r\nShoot me an email if you find my additions useful! ","4":"This is an update to Adam Lazur's svncommand script, vimscript #922, which was itself based on the cvscommand script (now vcscommand), vimscript #90.\r\n\r\nKeywords: svn SVN svncommand subversion Subversion\r\n\r\nBasically I pulled a newer version of cvscommand (1.76) that had a lot of nice updates that I wanted to use with Subversion and did what Adam did, which is lots of 's\/CVS\/SVN\/'.  Then hacked on it till it worked like it was supposed to.  I also pulled in Adams SVNCommitDiff function for displaying a diff for a svn-commit.* file.  \r\n\r\nFinally, I added a few features of my very own:\r\n - Option to enable automatic execution of SVNCommitDiff when a svn-commit.* file is loaded.\r\n - A simple property editor.  SVNPropedit with no options runs \"svn proplist\" to give you a listing of all the set properties.  If given an argument, it grabs the property of that name and gives you a window to update the value in.\r\n \r\nThe vcscommand script has just been updated to support Subversion (8-10-06), but so far there is not a property editor or CommitDiff function.\r\n\r\nShoot me an email if you find my additions useful! ","install_details":"Untar the file into a temporary directory (Assuming Linux):\r\n   # cd \/tmp\r\n   # tar -zxvf \/downloads\/svncommand-{REL}.tar.gz\r\n\r\nThen you can install the files in one of two ways:\r\n\r\n  - Allow my Makefile to install everything in the right subdirectory under ~\/.vim\r\n    # cd svncommand-{REL}\r\n    #  make install             \r\n - Manually copy each file in the subdirectories of the release to the same named directory under ~\/.vim\r\n\r\nThis might well work with VIM 6.0 (cvscommand 1.76 does and it was based on that) but I have only tested it on 7.0 under Linux.  ","5":"Untar the file into a temporary directory (Assuming Linux):\r\n   # cd \/tmp\r\n   # tar -zxvf \/downloads\/svncommand-{REL}.tar.gz\r\n\r\nThen you can install the files in one of two ways:\r\n\r\n  - Allow my Makefile to install everything in the right subdirectory under ~\/.vim\r\n    # cd svncommand-{REL}\r\n    #  make install             \r\n - Manually copy each file in the subdirectories of the release to the same named directory under ~\/.vim\r\n\r\nThis might well work with VIM 6.0 (cvscommand 1.76 does and it was based on that) but I have only tested it on 7.0 under Linux.  ","first_name":"Troy","6":"Troy","last_name":"Curtis","7":"Curtis","releases":[{"0":"1633","vim_version":"7.0","1":"7.0","script_version":"1.76.2","2":"1.76.2","version_comment":"Initial upload","3":"Initial upload","package":"svncommand-1.76.2.tar.gz","4":"svncommand-1.76.2.tar.gz","src_id":"6058","5":"6058","creation_date":"1155246920","6":"1155246920"}]},"1632":{"script_id":"1632","0":"1632","script_name":"sh.vim","1":"sh.vim","script_type":"indent","2":"indent","summary":"Indent script for sh\/bash","3":"Indent script for sh\/bash","description":"This is a minor bug-fix version of the official sh indent script, in order to support the \"case\" statement.\r\n\r\nThe default indent style is to put the case labels in the same indent level of the case statement. If you want to increase the indent level of the case labels, just add this line in your .vimrc:\r\n\r\nlet g:sh_indent_case_labels=1\r\n","4":"This is a minor bug-fix version of the official sh indent script, in order to support the \"case\" statement.\r\n\r\nThe default indent style is to put the case labels in the same indent level of the case statement. If you want to increase the indent level of the case labels, just add this line in your .vimrc:\r\n\r\nlet g:sh_indent_case_labels=1\r\n","install_details":"Download the file and put it into your indent plugin path.","5":"Download the file and put it into your indent plugin path.","first_name":"Edward","6":"Edward","last_name":"Fox","7":"Fox","releases":[{"0":"1632","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"sh.vim","4":"sh.vim","src_id":"6056","5":"6056","creation_date":"1155177612","6":"1155177612"}]},"1631":{"script_id":"1631","0":"1631","script_name":"gnuchangelog","1":"gnuchangelog","script_type":"utility","2":"utility","summary":"Changelog support like Emacs\/GNU","3":"Changelog support like Emacs\/GNU","description":"Enhances the default changelog support with a global mapping that opens and adds an entry in the appropriate ChangeLog file.  The entry now includes the edited filename and if configured, the class\/method\/function name.  The function that finds the class\/method\/function name can be configured with filetype plugins so that one can use different tag searchers for different languages.\r\n\r\nThe ChangeLog file is only edited if it already exists, which  is searched upwards starting in the directory where the  edited file is located.  If the corresponding ChangeLog file is already opened, the script either splits the window to edit the buffer or switches to the window where the buffer is already opened.\r\n\r\nThis behavior is identical to how emacs handles ChangeLog  files with the change-log-mode provided by C-x 4 a.\r\n\r\nSee also:\r\n\r\nhttp:\/\/gnudist.gnu.org\/software\/emacs\/manual\/html_node\/Change-Log.html\r\nhttp:\/\/www.gnu.org\/prep\/standards\/html_node\/Change-Log-Concepts.html\r\n","4":"Enhances the default changelog support with a global mapping that opens and adds an entry in the appropriate ChangeLog file.  The entry now includes the edited filename and if configured, the class\/method\/function name.  The function that finds the class\/method\/function name can be configured with filetype plugins so that one can use different tag searchers for different languages.\r\n\r\nThe ChangeLog file is only edited if it already exists, which  is searched upwards starting in the directory where the  edited file is located.  If the corresponding ChangeLog file is already opened, the script either splits the window to edit the buffer or switches to the window where the buffer is already opened.\r\n\r\nThis behavior is identical to how emacs handles ChangeLog  files with the change-log-mode provided by C-x 4 a.\r\n\r\nSee also:\r\n\r\nhttp:\/\/gnudist.gnu.org\/software\/emacs\/manual\/html_node\/Change-Log.html\r\nhttp:\/\/www.gnu.org\/prep\/standards\/html_node\/Change-Log-Concepts.html\r\n","install_details":"To install and use this plugin:\r\n\r\n - Set the EMAIL environment to your email address, e.g.,  export EMAIL=\"John Doe <jdoe@foo.com>\".  This is the user name  that will be included in the changelog entry.\r\n\r\n - Copy plugin\/gnuchlog.vim to your ~\/.vim\/plugin dir.\r\n\r\n - Copy ftplugin\/changelog.vim to your ~\/.vim\/ftplugin dir.  This overrides the changelog.vim included by default in vim.\r\n\r\n - Make sure you have \"filetype plugin on\" in your .vimrc\r\n\r\nIf you want to auto-include class\/method\/function name in the ChangeLog entry using the pythonhelper.py plugin:\r\n\r\n - If you don't have it already, copy plugin\/pythonhelper.vim to your ~\/.vim\/plugin dir, which will give you this info in the status line all by itself.\r\n\r\n - Copy the ftplugin\/python_gnuchlog.vim script to your ~\/.vim\/ftplugin dir to make the gnuchlog.vim plugin use the pythonhelper.vim info to get the class\/method\/name when invoked from a python source.  This is an additional python filetype plugin (i.e., loaded and run in addition to the standard python.vim filetype plugin) that configures a global variable that allows the gnuchlog.vim plugin to use information provided by the pythonhelper.vim plugin.\r\n\r\n - You can override the statusline setting to your liking by adding a 'set stl' command to ~\/.vim\/after\/plugin\/pythonhelper.vim.  See ':help statusline' for info on how to configure the status line.\r\n   For example:\r\n\r\n   set stl=%-f%r\\ %2*%m%*%h%w\\ %1*%{TagInStatusLine()}%*%=%l,%c%V\r\n","5":"To install and use this plugin:\r\n\r\n - Set the EMAIL environment to your email address, e.g.,  export EMAIL=\"John Doe <jdoe@foo.com>\".  This is the user name  that will be included in the changelog entry.\r\n\r\n - Copy plugin\/gnuchlog.vim to your ~\/.vim\/plugin dir.\r\n\r\n - Copy ftplugin\/changelog.vim to your ~\/.vim\/ftplugin dir.  This overrides the changelog.vim included by default in vim.\r\n\r\n - Make sure you have \"filetype plugin on\" in your .vimrc\r\n\r\nIf you want to auto-include class\/method\/function name in the ChangeLog entry using the pythonhelper.py plugin:\r\n\r\n - If you don't have it already, copy plugin\/pythonhelper.vim to your ~\/.vim\/plugin dir, which will give you this info in the status line all by itself.\r\n\r\n - Copy the ftplugin\/python_gnuchlog.vim script to your ~\/.vim\/ftplugin dir to make the gnuchlog.vim plugin use the pythonhelper.vim info to get the class\/method\/name when invoked from a python source.  This is an additional python filetype plugin (i.e., loaded and run in addition to the standard python.vim filetype plugin) that configures a global variable that allows the gnuchlog.vim plugin to use information provided by the pythonhelper.vim plugin.\r\n\r\n - You can override the statusline setting to your liking by adding a 'set stl' command to ~\/.vim\/after\/plugin\/pythonhelper.vim.  See ':help statusline' for info on how to configure the status line.\r\n   For example:\r\n\r\n   set stl=%-f%r\\ %2*%m%*%h%w\\ %1*%{TagInStatusLine()}%*%=%l,%c%V\r\n","first_name":"Luis","6":"Luis","last_name":"Caamano","7":"Caamano","releases":[{"0":"1631","vim_version":"7.0","1":"7.0","script_version":"1.3","2":"1.3","version_comment":"Build the path name of the edited file in the entry title relative to the directory where the ChangeLog file is, an emacs ChangeLog behavior I missed.  Thanks to Donald Curtis <donald-curtis@uiowa.edu> for catching that and providing a patch.","3":"Build the path name of the edited file in the entry title relative to the directory where the ChangeLog file is, an emacs ChangeLog behavior I missed.  Thanks to Donald Curtis <donald-curtis@uiowa.edu> for catching that and providing a patch.","package":"gnuchlog_1.3.tgz","4":"gnuchlog_1.3.tgz","src_id":"6089","5":"6089","creation_date":"1156250642","6":"1156250642"},{"0":"1631","vim_version":"7.0","1":"7.0","script_version":"1.2","2":"1.2","version_comment":"Added ';' to findfile() call to make sure we always search upwards.  There are some cases where findfile() doesn't find the ChangeLog file if the semicolon is not added to the path to search.\r\n","3":"Added ';' to findfile() call to make sure we always search upwards.  There are some cases where findfile() doesn't find the ChangeLog file if the semicolon is not added to the path to search.\r\n","package":"gnuchlog_1.2.tgz","4":"gnuchlog_1.2.tgz","src_id":"6064","5":"6064","creation_date":"1155294531","6":"1155294531"}]},"1630":{"script_id":"1630","0":"1630","script_name":"netdict","1":"netdict","script_type":"utility","2":"utility","summary":"A frontend to the Unix dict protocol command-line client.","3":"A frontend to the Unix dict protocol command-line client.","description":"Netdict is a plugin to lookup definitions via the Unix dict protocol command-line client. It has the following features:\r\n\r\n    - specifying an alternate database and search strategy\r\n    - term matching\r\n    - syntax highlighting\r\n    - GUI input dialog\r\n    - customizable settings","4":"Netdict is a plugin to lookup definitions via the Unix dict protocol command-line client. It has the following features:\r\n\r\n    - specifying an alternate database and search strategy\r\n    - term matching\r\n    - syntax highlighting\r\n    - GUI input dialog\r\n    - customizable settings","install_details":"Extract the archive and then `make install'. Then run \":helptags ~\/.vim\/doc\" then \":h netdict\" for more info. You will need to have the bash shell installed.","5":"Extract the archive and then `make install'. Then run \":helptags ~\/.vim\/doc\" then \":h netdict\" for more info. You will need to have the bash shell installed.","first_name":"","6":"","last_name":"","7":"","releases":[{"0":"1630","vim_version":"6.0","1":"6.0","script_version":"20060805","2":"20060805","version_comment":"Initial upload","3":"Initial upload","package":"netdict.tgz","4":"netdict.tgz","src_id":"6042","5":"6042","creation_date":"1154773527","6":"1154773527"}]},"1629":{"script_id":"1629","0":"1629","script_name":"XChat IRC Log","1":"XChat IRC Log","script_type":"syntax","2":"syntax","summary":"Syntax highlighting for X-Chat IRC log files","3":"Syntax highlighting for X-Chat IRC log files","description":"This syntax script provides highlighting for X-Chat's log files, as well as for any text copied and pasted from X-Chat.","4":"This syntax script provides highlighting for X-Chat's log files, as well as for any text copied and pasted from X-Chat.","install_details":"","5":"","first_name":"David","6":"David","last_name":"Bronke","7":"Bronke","releases":[{"0":"1629","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"irclog.vim","4":"irclog.vim","src_id":"6037","5":"6037","creation_date":"1154628931","6":"1154628931"}]},"1628":{"script_id":"1628","0":"1628","script_name":"findfuncname.vim","1":"findfuncname.vim","script_type":"utility","2":"utility","summary":"Find the name of the function you are editing","3":"Find the name of the function you are editing","description":"This is similar to the tip I posted previously, except I made a few fixes and made it self-contained as a plugin.\r\n\r\nThe script contains a function called 'FunctionName()' that returns the name of the function you are currently working in.  This is handy if you got there through a search, or are in a large function or small screen\/window and can't see the function's name.  \r\n\r\nThis on-command (I've seen some that constantly display in the status line) function uses a search pattern to search for a pattern that matches every function declaration I've tried in C, Objective-C, C++, Perl, and Python with the caveat that the function declaration must start on the first character of the line.  I'll fix this one of these days, since Java files will break on that particular point.\r\n\r\n","4":"This is similar to the tip I posted previously, except I made a few fixes and made it self-contained as a plugin.\r\n\r\nThe script contains a function called 'FunctionName()' that returns the name of the function you are currently working in.  This is handy if you got there through a search, or are in a large function or small screen\/window and can't see the function's name.  \r\n\r\nThis on-command (I've seen some that constantly display in the status line) function uses a search pattern to search for a pattern that matches every function declaration I've tried in C, Objective-C, C++, Perl, and Python with the caveat that the function declaration must start on the first character of the line.  I'll fix this one of these days, since Java files will break on that particular point.\r\n\r\n","install_details":"download the script and place it in your plugin directory, or make sure that your .vimrc sources the script wherever you have saved it.\r\n\r\nAdd the following to your .gvim or .vimrc:\r\nmap \\func :echo FunctionName()<CR>\r\n\r\nNow, typing \\func displays the line number and declaration of the name of the function I am editing in.  ","5":"download the script and place it in your plugin directory, or make sure that your .vimrc sources the script wherever you have saved it.\r\n\r\nAdd the following to your .gvim or .vimrc:\r\nmap \\func :echo FunctionName()<CR>\r\n\r\nNow, typing \\func displays the line number and declaration of the name of the function I am editing in.  ","first_name":"Alex","6":"Alex","last_name":"Esplin","7":"Esplin","releases":[{"0":"1628","vim_version":"7.0","1":"7.0","script_version":"3.6","2":"3.6","version_comment":"Silently replace if a function with the same name is already loaded.","3":"Silently replace if a function with the same name is already loaded.","package":"findfuncname.vim","4":"findfuncname.vim","src_id":"14089","5":"14089","creation_date":"1287613015","6":"1287613015"},{"0":"1628","vim_version":"7.0","1":"7.0","script_version":"3.5","2":"3.5","version_comment":"Updated the regex to catch commas (if argument list is split from the declaration line onto succeeding lines) or closing parens (if argument list is all on the declaration line).","3":"Updated the regex to catch commas (if argument list is split from the declaration line onto succeeding lines) or closing parens (if argument list is all on the declaration line).","package":"findfuncname.vim","4":"findfuncname.vim","src_id":"11428","5":"11428","creation_date":"1253820519","6":"1253820519"},{"0":"1628","vim_version":"7.0","1":"7.0","script_version":"3.4","2":"3.4","version_comment":"Fixed a bug with the filename matching when checking for Python files. Made the regex for C-like function declarations a little more specific.","3":"Fixed a bug with the filename matching when checking for Python files. Made the regex for C-like function declarations a little more specific.","package":"findfuncname.vim","4":"findfuncname.vim","src_id":"11427","5":"11427","creation_date":"1253814723","6":"1253814723"},{"0":"1628","vim_version":"7.0","1":"7.0","script_version":"3.3","2":"3.3","version_comment":"Fixed to detect if the current file ends with .py and makes it look for the most recent 'class name:' or def 'func():' statement.","3":"Fixed to detect if the current file ends with .py and makes it look for the most recent 'class name:' or def 'func():' statement.","package":"findfuncname.vim","4":"findfuncname.vim","src_id":"11425","5":"11425","creation_date":"1253769692","6":"1253769692"},{"0":"1628","vim_version":"6.0","1":"6.0","script_version":"3.2","2":"3.2","version_comment":"minor change to allow for empty space at the end of the declaration line","3":"minor change to allow for empty space at the end of the declaration line","package":"findfuncname.vim","4":"findfuncname.vim","src_id":"10315","5":"10315","creation_date":"1238355451","6":"1238355451"},{"0":"1628","vim_version":"7.0","1":"7.0","script_version":"3.1","2":"3.1","version_comment":"Small change to allow for code with the curly brace on the line below the function declaration.","3":"Small change to allow for code with the curly brace on the line below the function declaration.","package":"findfuncname.vim","4":"findfuncname.vim","src_id":"10029","5":"10029","creation_date":"1235528349","6":"1235528349"},{"0":"1628","vim_version":"7.0","1":"7.0","script_version":"3.0","2":"3.0","version_comment":"Major change to search pattern.\r\n\r\nActually works for most C, C++, Python, and Perl programs with functions.\r\n\r\nRelies on function starting in the first column, so Java files will have issues, I'll fix this soon...","3":"Major change to search pattern.\r\n\r\nActually works for most C, C++, Python, and Perl programs with functions.\r\n\r\nRelies on function starting in the first column, so Java files will have issues, I'll fix this soon...","package":"findfuncname.vim","4":"findfuncname.vim","src_id":"10022","5":"10022","creation_date":"1235499202","6":"1235499202"},{"0":"1628","vim_version":"7.0","1":"7.0","script_version":"2.0.1","2":"2.0.1","version_comment":"minor comment\/documentation change","3":"minor comment\/documentation change","package":"findfuncname.vim","4":"findfuncname.vim","src_id":"9845","5":"9845","creation_date":"1232412200","6":"1232412200"},{"0":"1628","vim_version":"7.0","1":"7.0","script_version":"2.0","2":"2.0","version_comment":"Major overhaul using a backwards-searching regular expression that seems to dodge control statements (if,else,else if,for,while, etc...) and catch most function declarations.","3":"Major overhaul using a backwards-searching regular expression that seems to dodge control statements (if,else,else if,for,while, etc...) and catch most function declarations.","package":"findfuncname.vim","4":"findfuncname.vim","src_id":"9844","5":"9844","creation_date":"1232411745","6":"1232411745"},{"0":"1628","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"findfuncname.vim","4":"findfuncname.vim","src_id":"6036","5":"6036","creation_date":"1154622824","6":"1154622824"}]},"1627":{"script_id":"1627","0":"1627","script_name":"doriath.vim","1":"doriath.vim","script_type":"color scheme","2":"color scheme","summary":"a nice mellow dark green scheme","3":"a nice mellow dark green scheme","description":"This theme is _loosely_ based on my old friend the desert colorscheme, but is geared more toward a forest-green\/sea-green appearance.\r\nThis colorscheme was tested only in GVIM so I have no clue what it does in terminal vim.","4":"This theme is _loosely_ based on my old friend the desert colorscheme, but is geared more toward a forest-green\/sea-green appearance.\r\nThis colorscheme was tested only in GVIM so I have no clue what it does in terminal vim.","install_details":"place the \"doriath.vim\" file in your $VIM\/colors\/ directory and select it with \"color doriath\" in your gvimrc file","5":"place the \"doriath.vim\" file in your $VIM\/colors\/ directory and select it with \"color doriath\" in your gvimrc file","first_name":"Alex","6":"Alex","last_name":"Esplin","7":"Esplin","releases":[{"0":"1627","vim_version":"6.0","1":"6.0","script_version":"1.2","2":"1.2","version_comment":"Made some changes to make it less like 'desert' and more like what I wanted, but didn't have time to implement the other day.","3":"Made some changes to make it less like 'desert' and more like what I wanted, but didn't have time to implement the other day.","package":"doriath.vim","4":"doriath.vim","src_id":"6047","5":"6047","creation_date":"1154944037","6":"1154944037"},{"0":"1627","vim_version":"7.0","1":"7.0","script_version":"1.1","2":"1.1","version_comment":"cleaned up some syntax and superfluous comments, tested with Gvim 7.0.","3":"cleaned up some syntax and superfluous comments, tested with Gvim 7.0.","package":"doriath.vim","4":"doriath.vim","src_id":"6033","5":"6033","creation_date":"1154589918","6":"1154589918"},{"0":"1627","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"doriath.vim","4":"doriath.vim","src_id":"6025","5":"6025","creation_date":"1154528016","6":"1154528016"}]},"1626":{"script_id":"1626","0":"1626","script_name":"liquid.vim","1":"liquid.vim","script_type":"syntax","2":"syntax","summary":"Vim syntax file for Liquid Templates","3":"Vim syntax file for Liquid Templates","description":"This highlights Liquid Template Files ( http:\/\/home.leetsoft.com\/liquid )\r\nIt recognizes tags, outputs and comments as well as highlighting \r\nRuby instance variables.\r\n\r\nIt sets the file type to html so that it highlights html as well. If this shouldn't be automatic for some reason, let me know how it should be and I'll change it.\r\n\r\nEnjoy ;)","4":"This highlights Liquid Template Files ( http:\/\/home.leetsoft.com\/liquid )\r\nIt recognizes tags, outputs and comments as well as highlighting \r\nRuby instance variables.\r\n\r\nIt sets the file type to html so that it highlights html as well. If this shouldn't be automatic for some reason, let me know how it should be and I'll change it.\r\n\r\nEnjoy ;)","install_details":"Copy this script to ~\/.vim\/syntax under *NIX systems (If someone could tell me what the directory is for Windows users, I'd appreciate it and add it here as well).\r\n\r\nAdd this line to your ~\/.vim\/filetype.vim:\r\n\r\nau BufNewFile,BufRead *.liquid\t\t\tsetf liquid","5":"Copy this script to ~\/.vim\/syntax under *NIX systems (If someone could tell me what the directory is for Windows users, I'd appreciate it and add it here as well).\r\n\r\nAdd this line to your ~\/.vim\/filetype.vim:\r\n\r\nau BufNewFile,BufRead *.liquid\t\t\tsetf liquid","first_name":"Eugen","6":"Eugen","last_name":"Minciu","7":"Minciu","releases":[{"0":"1626","vim_version":"6.0","1":"6.0","script_version":"2","2":"2","version_comment":"This version doesn't set the filetype to HTML anymore.\r\nIt now works correctly with Tim Pope's SVN version of rails.vim which will support highlighting Liquid through this file.\r\nThe identifier names where changed to start with a lowercase letter (so omnicompletion should now work)","3":"This version doesn't set the filetype to HTML anymore.\r\nIt now works correctly with Tim Pope's SVN version of rails.vim which will support highlighting Liquid through this file.\r\nThe identifier names where changed to start with a lowercase letter (so omnicompletion should now work)","package":"liquid.vim","4":"liquid.vim","src_id":"6028","5":"6028","creation_date":"1154565851","6":"1154565851"},{"0":"1626","vim_version":"6.0","1":"6.0","script_version":"1","2":"1","version_comment":"Initial upload","3":"Initial upload","package":"liquid.vim","4":"liquid.vim","src_id":"6024","5":"6024","creation_date":"1154486904","6":"1154486904"}]},"1625":{"script_id":"1625","0":"1625","script_name":"x12 syntax","1":"x12 syntax","script_type":"syntax","2":"syntax","summary":"Highlighter for X12 EDI(electronic data interchange) files","3":"Highlighter for X12 EDI(electronic data interchange) files","description":"A simple syntax highlighter for EDI X12 files -\r\nIt does not validate the correctness of X12s. Just highlights the file. \r\nCurrently only Healthcare 270\/271s are tested.","4":"A simple syntax highlighter for EDI X12 files -\r\nIt does not validate the correctness of X12s. Just highlights the file. \r\nCurrently only Healthcare 270\/271s are tested.","install_details":"Copy the file to\r\n$VIMRUNTIME\/syntax\/  (Windows)\r\nor \r\n~\/.vim\/syntax\/                      (*nix)\r\n\r\nPut an entry to $VIMRUNTIME\/filetype.vim like:\r\n\r\n\" X12\r\nau BufNewFile,BufRead *.x12\t\tsetf x12\r\n\r\nTo auto load the syntax.\r\n\r\n","5":"Copy the file to\r\n$VIMRUNTIME\/syntax\/  (Windows)\r\nor \r\n~\/.vim\/syntax\/                      (*nix)\r\n\r\nPut an entry to $VIMRUNTIME\/filetype.vim like:\r\n\r\n\" X12\r\nau BufNewFile,BufRead *.x12\t\tsetf x12\r\n\r\nTo auto load the syntax.\r\n\r\n","first_name":"ranjith","6":"ranjith","last_name":"chandran","7":"chandran","releases":[{"0":"1625","vim_version":"7.0","1":"7.0","script_version":"0.2","2":"0.2","version_comment":"Added few more segments left out in 0.1\r\nAdded highlighting for \":\"  as Special.","3":"Added few more segments left out in 0.1\r\nAdded highlighting for \":\"  as Special.","package":"x12.vim","4":"x12.vim","src_id":"7778","5":"7778","creation_date":"1192085507","6":"1192085507"},{"0":"1625","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"x12.vim","4":"x12.vim","src_id":"6016","5":"6016","creation_date":"1154351516","6":"1154351516"}]},"1624":{"script_id":"1624","0":"1624","script_name":"pastie.vim","1":"pastie.vim","script_type":"utility","2":"utility","summary":"Interface with pastie.org; read and create pastes","3":"Interface with pastie.org; read and create pastes","description":"This script lets you read and create pastes at http:\/\/pastie.org\/ .  Pastes can be created from a range, a register (including the clipboard), any number of files, all open windows, or an existing paste.  It automatically maps between Vim filetypes and pastie's parsers.  Details for how to use the :Pastie command are included in the comments at the top of the plugin.\r\n\r\nPastie is the preferred method of sharing code in the Ruby IRC community.\r\n\r\nhttp:\/\/github.com\/tpope\/vim-pastie","4":"This script lets you read and create pastes at http:\/\/pastie.org\/ .  Pastes can be created from a range, a register (including the clipboard), any number of files, all open windows, or an existing paste.  It automatically maps between Vim filetypes and pastie's parsers.  Details for how to use the :Pastie command are included in the comments at the top of the plugin.\r\n\r\nPastie is the preferred method of sharing code in the Ruby IRC community.\r\n\r\nhttp:\/\/github.com\/tpope\/vim-pastie","install_details":"Place in ~\/.vim\/plugin (or vimfiles\/plugin).\r\nRuby is required, but the Vim Ruby interface is not.","5":"Place in ~\/.vim\/plugin (or vimfiles\/plugin).\r\nRuby is required, but the Vim Ruby interface is not.","first_name":"Tim","6":"Tim","last_name":"Pope","7":"Pope","releases":[{"0":"1624","vim_version":"6.0","1":"6.0","script_version":"2.0","2":"2.0","version_comment":"Switch from pastie.caboo.se domain to pastie.org","3":"Switch from pastie.caboo.se domain to pastie.org","package":"pastie.vim","4":"pastie.vim","src_id":"10260","5":"10260","creation_date":"1237663622","6":"1237663622"},{"0":"1624","vim_version":"6.0","1":"6.0","script_version":"1.15","2":"1.15","version_comment":"Update for new server-side parser names.","3":"Update for new server-side parser names.","package":"pastie.vim","4":"pastie.vim","src_id":"8043","5":"8043","creation_date":"1197535750","6":"1197535750"},{"0":"1624","vim_version":"6.0","1":"6.0","script_version":"1.14","2":"1.14","version_comment":"More updates for server changes","3":"More updates for server changes","package":"pastie.vim","4":"pastie.vim","src_id":"7797","5":"7797","creation_date":"1192439470","6":"1192439470"},{"0":"1624","vim_version":"6.0","1":"6.0","script_version":"1.13","2":"1.13","version_comment":"Updates for latest server side changes.\r\nFixed issue with Vim 6.2.","3":"Updates for latest server side changes.\r\nFixed issue with Vim 6.2.","package":"pastie.vim","4":"pastie.vim","src_id":"7736","5":"7736","creation_date":"1191229281","6":"1191229281"},{"0":"1624","vim_version":"6.0","1":"6.0","script_version":"1.9","2":"1.9","version_comment":"Fixed bug in using clipboard as a source","3":"Fixed bug in using clipboard as a source","package":"pastie.vim","4":"pastie.vim","src_id":"7314","5":"7314","creation_date":"1183360934","6":"1183360934"},{"0":"1624","vim_version":"6.0","1":"6.0","script_version":"1.8","2":"1.8","version_comment":"Don't close current tab with \":Pastie!\"","3":"Don't close current tab with \":Pastie!\"","package":"pastie.vim","4":"pastie.vim","src_id":"6617","5":"6617","creation_date":"1168948086","6":"1168948086"},{"0":"1624","vim_version":"6.0","1":"6.0","script_version":"1.7","2":"1.7","version_comment":"Fixed bug in Firefox cookie extraction","3":"Fixed bug in Firefox cookie extraction","package":"pastie.vim","4":"pastie.vim","src_id":"6543","5":"6543","creation_date":"1166803222","6":"1166803222"},{"0":"1624","vim_version":"6.0","1":"6.0","script_version":"1.6","2":"1.6","version_comment":"Support shell=csh","3":"Support shell=csh","package":"pastie.vim","4":"pastie.vim","src_id":"6517","5":"6517","creation_date":"1166139703","6":"1166139703"},{"0":"1624","vim_version":"6.0","1":"6.0","script_version":"1.5","2":"1.5","version_comment":"Properly handle new anti-bot measures","3":"Properly handle new anti-bot measures","package":"pastie.vim","4":"pastie.vim","src_id":"6296","5":"6296","creation_date":"1161248772","6":"1161248772"},{"0":"1624","vim_version":"6.0","1":"6.0","script_version":"1.4","2":"1.4","version_comment":"Extracts login account token from Firefox cookies.","3":"Extracts login account token from Firefox cookies.","package":"pastie.vim","4":"pastie.vim","src_id":"6018","5":"6018","creation_date":"1154383931","6":"1154383931"},{"0":"1624","vim_version":"6.0","1":"6.0","script_version":"1.2","2":"1.2","version_comment":"Initial upload","3":"Initial upload","package":"pastie.vim","4":"pastie.vim","src_id":"6007","5":"6007","creation_date":"1154177372","6":"1154177372"}]},"1623":{"script_id":"1623","0":"1623","script_name":"phpfolding.vim","1":"phpfolding.vim","script_type":"utility","2":"utility","summary":"Automatic folding of PHP functions, classes,.. (also folds related PhpDoc)","3":"Automatic folding of PHP functions, classes,.. (also folds related PhpDoc)","description":"This script can fold PHP functions and\/or classes, properties with their phpdoc\r\nwithout manually adding marker style folds ({{{ and }}}). \r\nIt will generate the following folds when executed:\r\n\r\n<?php\r\n\/**\r\n * This is Foo...\r\n * @author Foo\r\n *\/\r\nclass Foo \r\n{\r\n+-- 11 lines: function foo($bar) ** -------------------------------------------------\r\n+--  8 lines: function bar($bar) ** -------------------------------------------------\r\n+-- 24 lines: function baz($bar) ----------------------------------------------------\r\n}\r\n?>\r\n\r\nBased on e.g. functions declared like this:\r\n\r\n<?php\r\n\/**\r\n* This is fooFunction...\r\n*\r\n* @param mixed $bar\r\n* @access public\r\n* @return void\r\n*\/\r\nfunction fooFunction($bar) \r\n{\r\n    ...\r\n}\r\n?>\r\n\r\nSCREENSHOT\r\nYou can view a screenshot here: http:\/\/blog.cppse.nl\/phpfolding-vim\r\n\r\nFEATURES\r\n- It remembers fold settings. If you add functions and execute the script again,\r\n  your opened folds will not be closed.\r\n- It will not be confused by brackets in comment blocks or string literals.\r\n- The folding of class properties with their PhpDoc comments.\r\n- The folding of all class properties into one fold.\r\n- Folding the original marker style folds too.\r\n- An \"**\" postfixing the fold indicates PhpDoc is inside (configurable).\r\n- An \"**#@+\" postfixing the fold indicates PhpDocBlock is inside (configurable).\r\n- Empty lines postfixing the folds can be configured to be included in the fold.\r\n- Nested folds are supported (functions inside functions, etc.)\r\n- Folding private, public, protected class variables + multi-line param.\r\n- Foloding the class is now an option disabled by default.\r\n- Now works properly as ftplugin\r\n\r\nFUTURE\r\n- Better 'configurability' as opposed to editting the PHPCustomFolds() function\r\n  and some \"Script configuration\" global variables.\r\n\r\nCONTRIBUTE \/ GITHUB\r\nThis project is hosted on github as a mirror through\r\n    https:\/\/github.com\/vim-scripts\/phpfolding.vim\r\nI do not own vim-scripts, so please fork mine instead:\r\n    https:\/\/github.com\/rayburgemeestre\/phpfolding.vim\r\nIt's then easier for me to accept pull requests and upload new version(s) here,\r\nalso I cannot put phpfolding.vim in the ftplugin\/php directory through the\r\nvim.org interface.\r\n\r\n\r\nCOMPATIBILITY\r\nThis script is tested successfully with Vim version >= 6.3 on windows and linux\r\n(With 6.0 it works *sometimes*, I don't recommend using it in that version)","4":"This script can fold PHP functions and\/or classes, properties with their phpdoc\r\nwithout manually adding marker style folds ({{{ and }}}). \r\nIt will generate the following folds when executed:\r\n\r\n<?php\r\n\/**\r\n * This is Foo...\r\n * @author Foo\r\n *\/\r\nclass Foo \r\n{\r\n+-- 11 lines: function foo($bar) ** -------------------------------------------------\r\n+--  8 lines: function bar($bar) ** -------------------------------------------------\r\n+-- 24 lines: function baz($bar) ----------------------------------------------------\r\n}\r\n?>\r\n\r\nBased on e.g. functions declared like this:\r\n\r\n<?php\r\n\/**\r\n* This is fooFunction...\r\n*\r\n* @param mixed $bar\r\n* @access public\r\n* @return void\r\n*\/\r\nfunction fooFunction($bar) \r\n{\r\n    ...\r\n}\r\n?>\r\n\r\nSCREENSHOT\r\nYou can view a screenshot here: http:\/\/blog.cppse.nl\/phpfolding-vim\r\n\r\nFEATURES\r\n- It remembers fold settings. If you add functions and execute the script again,\r\n  your opened folds will not be closed.\r\n- It will not be confused by brackets in comment blocks or string literals.\r\n- The folding of class properties with their PhpDoc comments.\r\n- The folding of all class properties into one fold.\r\n- Folding the original marker style folds too.\r\n- An \"**\" postfixing the fold indicates PhpDoc is inside (configurable).\r\n- An \"**#@+\" postfixing the fold indicates PhpDocBlock is inside (configurable).\r\n- Empty lines postfixing the folds can be configured to be included in the fold.\r\n- Nested folds are supported (functions inside functions, etc.)\r\n- Folding private, public, protected class variables + multi-line param.\r\n- Foloding the class is now an option disabled by default.\r\n- Now works properly as ftplugin\r\n\r\nFUTURE\r\n- Better 'configurability' as opposed to editting the PHPCustomFolds() function\r\n  and some \"Script configuration\" global variables.\r\n\r\nCONTRIBUTE \/ GITHUB\r\nThis project is hosted on github as a mirror through\r\n    https:\/\/github.com\/vim-scripts\/phpfolding.vim\r\nI do not own vim-scripts, so please fork mine instead:\r\n    https:\/\/github.com\/rayburgemeestre\/phpfolding.vim\r\nIt's then easier for me to accept pull requests and upload new version(s) here,\r\nalso I cannot put phpfolding.vim in the ftplugin\/php directory through the\r\nvim.org interface.\r\n\r\n\r\nCOMPATIBILITY\r\nThis script is tested successfully with Vim version >= 6.3 on windows and linux\r\n(With 6.0 it works *sometimes*, I don't recommend using it in that version)","install_details":"INSTALL\r\n1. Put phpfolding.vim in your plugin directory (~\/.vim\/ftplugin\/php\/)\r\n\r\n      Make sure you have \"filetype plugin on\" in your .vimrc!\r\n\r\n      (folds will then be created after opening a file is recognized as php.)\r\n\r\n2. Alternatively, if you want to control loading manually, you might want to\r\n   add the following keyboard mappings to your .vimrc:\r\n\r\n      map <F5> <Esc>:EnableFastPHPFolds<Cr>\r\n      map <F6> <Esc>:EnablePHPFolds<Cr>\r\n      map <F7> <Esc>:DisablePHPFolds<Cr>\r\n\r\nIt might be necessary that you load the plugin from your .vimrc, i.e.:\r\n   let php_folding=0\r\n     (if you can't use the after directory in step 3)\r\n   source ~\/path\/to\/phpfolding.vim\r\n     (if you're not using the default plugin directory)\r\n\r\nKNOWN ISSUES\r\n1. C++ style commented brackets can still interfere with the bracket matching.\r\nFor example comments like are not recognized as comments:  \/\/ old: for (...) {\r\nWhereas C-style comments are, e.g.:  \/* old: for (...) { *\/\r\n(Edit: not sure if this is an issue anymore..)","5":"INSTALL\r\n1. Put phpfolding.vim in your plugin directory (~\/.vim\/ftplugin\/php\/)\r\n\r\n      Make sure you have \"filetype plugin on\" in your .vimrc!\r\n\r\n      (folds will then be created after opening a file is recognized as php.)\r\n\r\n2. Alternatively, if you want to control loading manually, you might want to\r\n   add the following keyboard mappings to your .vimrc:\r\n\r\n      map <F5> <Esc>:EnableFastPHPFolds<Cr>\r\n      map <F6> <Esc>:EnablePHPFolds<Cr>\r\n      map <F7> <Esc>:DisablePHPFolds<Cr>\r\n\r\nIt might be necessary that you load the plugin from your .vimrc, i.e.:\r\n   let php_folding=0\r\n     (if you can't use the after directory in step 3)\r\n   source ~\/path\/to\/phpfolding.vim\r\n     (if you're not using the default plugin directory)\r\n\r\nKNOWN ISSUES\r\n1. C++ style commented brackets can still interfere with the bracket matching.\r\nFor example comments like are not recognized as comments:  \/\/ old: for (...) {\r\nWhereas C-style comments are, e.g.:  \/* old: for (...) { *\/\r\n(Edit: not sure if this is an issue anymore..)","first_name":"Ray","6":"Ray","last_name":"Burgemeestre","7":"Burgemeestre","releases":[{"0":"1623","vim_version":"6.0","1":"6.0","script_version":"2.3","2":"2.3","version_comment":"Thanks to Michael H\u00c3\u00a4rtl (mikehaertl):\r\n- Fix detection of static and visibility keywords (can now appear in any order)\r\n- Fix detection of functions and abstract functions properly\r\n(https:\/\/github.com\/rayburgemeestre\/phpfolding.vim\/pull\/8)","3":"Thanks to Michael H\u00c3\u00a4rtl (mikehaertl):\r\n- Fix detection of static and visibility keywords (can now appear in any order)\r\n- Fix detection of functions and abstract functions properly\r\n(https:\/\/github.com\/rayburgemeestre\/phpfolding.vim\/pull\/8)","package":"phpfolding.vim","4":"phpfolding.vim","src_id":"27709","5":"27709","creation_date":"1628958737","6":"1628958737"},{"0":"1623","vim_version":"6.0","1":"6.0","script_version":"2.2","2":"2.2","version_comment":"1. No longer :redraw after folds are being created by default.\r\n\r\nThere is a setting that can be modified to enable it back, however, on my machine with vim 8.1.2269, whenever I exited vim I would notice tildes (~) all over the place, likely caused by the script executing :redraw during initialization.\r\n\r\nIf vim version 6 or 7 has drawing issues let me know and I'll make it conditional based on the vim version being used.","3":"1. No longer :redraw after folds are being created by default.\r\n\r\nThere is a setting that can be modified to enable it back, however, on my machine with vim 8.1.2269, whenever I exited vim I would notice tildes (~) all over the place, likely caused by the script executing :redraw during initialization.\r\n\r\nIf vim version 6 or 7 has drawing issues let me know and I'll make it conditional based on the vim version being used.","package":"phpfolding.vim","4":"phpfolding.vim","src_id":"27536","5":"27536","creation_date":"1616188010","6":"1616188010"},{"0":"1623","vim_version":"6.0","1":"6.0","script_version":"2.1","2":"2.1","version_comment":"Thanks to a bunch people:\r\n- Fix camelCase names and abstract functions (PR#7) (sutem)\r\n- Fix: Fixed function folding (PR#5) C\u00c3\u00a9sar D. Rodas (crodas)\r\n- Remove echo for fold(s) created (Glendon Solsberry (gms8994))\r\n- The 'function' pattern will match function calls like 'register_shutdown_function' (Fix by blu3gui7ar)\r\n- Changed line-endings from CRLF -> LF (Sudaraka Wijesinghe (sudaraka))\r\n- Move phpfolding.vim to ftplugin\/php\/phpfolding.vim (github only change) (Tak Nishigori (nishigori))\r\n- PHP5-aware(ish) class member & multi-line parameter folding (Jess Telford)","3":"Thanks to a bunch people:\r\n- Fix camelCase names and abstract functions (PR#7) (sutem)\r\n- Fix: Fixed function folding (PR#5) C\u00c3\u00a9sar D. Rodas (crodas)\r\n- Remove echo for fold(s) created (Glendon Solsberry (gms8994))\r\n- The 'function' pattern will match function calls like 'register_shutdown_function' (Fix by blu3gui7ar)\r\n- Changed line-endings from CRLF -> LF (Sudaraka Wijesinghe (sudaraka))\r\n- Move phpfolding.vim to ftplugin\/php\/phpfolding.vim (github only change) (Tak Nishigori (nishigori))\r\n- PHP5-aware(ish) class member & multi-line parameter folding (Jess Telford)","package":"phpfolding.vim","4":"phpfolding.vim","src_id":"26122","5":"26122","creation_date":"1531187618","6":"1531187618"},{"0":"1623","vim_version":"6.0","1":"6.0","script_version":"2.0","2":"2.0","version_comment":"Thanks to 吕海涛 (lvht):\r\n- Support for folding use statements\r\nThanks to Mikkel Paulson:\r\n- Support for folding consts into their docblocks","3":"Thanks to 吕海涛 (lvht):\r\n- Support for folding use statements\r\nThanks to Mikkel Paulson:\r\n- Support for folding consts into their docblocks","package":"phpfolding.vim","4":"phpfolding.vim","src_id":"24257","5":"24257","creation_date":"1463670213","6":"1463670213"},{"0":"1623","vim_version":"6.0","1":"6.0","script_version":"1.9","2":"1.9","version_comment":"Thanks to Yuki Matsukura (matsubo):\r\n1. Line ending fixed\r\n2. README now in Markdown\r\nThanks to Jan Mollowitz (phux):\r\n- Expanded regex to match optional static declared class properties.","3":"Thanks to Yuki Matsukura (matsubo):\r\n1. Line ending fixed\r\n2. README now in Markdown\r\nThanks to Jan Mollowitz (phux):\r\n- Expanded regex to match optional static declared class properties.","package":"phpfolding.vim","4":"phpfolding.vim","src_id":"21976","5":"21976","creation_date":"1401646944","6":"1401646944"},{"0":"1623","vim_version":"6.0","1":"6.0","script_version":"1.8","2":"1.8","version_comment":"Thanks to Dmitri Perunov for informing me of the fixes pending on github!\r\n1. Fix for folding private, public, protected class variables + multi-line param by Jess Telford\r\n2. Fix to make it work well as ftplugin (default now), added option for folding classes (disabled by default) and fix for fatal behavior, all by pekepeke","3":"Thanks to Dmitri Perunov for informing me of the fixes pending on github!\r\n1. Fix for folding private, public, protected class variables + multi-line param by Jess Telford\r\n2. Fix to make it work well as ftplugin (default now), added option for folding classes (disabled by default) and fix for fatal behavior, all by pekepeke","package":"phpfolding.vim","4":"phpfolding.vim","src_id":"20713","5":"20713","creation_date":"1377470675","6":"1377470675"},{"0":"1623","vim_version":"6.0","1":"6.0","script_version":"1.7","2":"1.7","version_comment":"The following much appreciated contributions are from LiTWoL (Oleg Terenchuk):\r\n1. Check if filetype is PHP before automatically creating folds \r\n2. Call EnableFastPHPFolds after reading file into the buffer \r\n3. Avoid reload check \r\n4. Added configuration variable to disable autofolding.","3":"The following much appreciated contributions are from LiTWoL (Oleg Terenchuk):\r\n1. Check if filetype is PHP before automatically creating folds \r\n2. Call EnableFastPHPFolds after reading file into the buffer \r\n3. Avoid reload check \r\n4. Added configuration variable to disable autofolding.","package":"phpfolding.vim","4":"phpfolding.vim","src_id":"12114","5":"12114","creation_date":"1263642174","6":"1263642174"},{"0":"1623","vim_version":"6.0","1":"6.0","script_version":"1.6","2":"1.6","version_comment":"1. Added nested fold support (recursion).\r\n2. Improved install instructions. Thanks to Peter Hodge for some useful information.\r\n3. Added phpdoc \"docblock\" support (\/**#@+ and #@- templates).\r\n4. Minor adjustments in FindPureBlockStart and FindPatternStart.","3":"1. Added nested fold support (recursion).\r\n2. Improved install instructions. Thanks to Peter Hodge for some useful information.\r\n3. Added phpdoc \"docblock\" support (\/**#@+ and #@- templates).\r\n4. Minor adjustments in FindPureBlockStart and FindPatternStart.","package":"phpfolding.vim","4":"phpfolding.vim","src_id":"6102","5":"6102","creation_date":"1156582970","6":"1156582970"},{"0":"1623","vim_version":"6.0","1":"6.0","script_version":"1.5","2":"1.5","version_comment":"1. Previously opened folds are now remembered again. I accidentally broke this in another version.\r\n2. The script now can fold abstract classes too. Thanks to Stefan Walk for adjusting the regex.\r\n3. Changed behaviour and fixed a bug in searching for trailing empty lines.\r\n4. Correct folding of nested folds will be supported in the *next* version.\r\n5. Changed some default settings.","3":"1. Previously opened folds are now remembered again. I accidentally broke this in another version.\r\n2. The script now can fold abstract classes too. Thanks to Stefan Walk for adjusting the regex.\r\n3. Changed behaviour and fixed a bug in searching for trailing empty lines.\r\n4. Correct folding of nested folds will be supported in the *next* version.\r\n5. Changed some default settings.","package":"phpfolding.vim","4":"phpfolding.vim","src_id":"6075","5":"6075","creation_date":"1155741100","6":"1155741100"},{"0":"1623","vim_version":"6.0","1":"6.0","script_version":"1.4.1","2":"1.4.1","version_comment":"1. Removed windows carriage returns (^M) throughout the file.","3":"1. Removed windows carriage returns (^M) throughout the file.","package":"phpfolding.vim","4":"phpfolding.vim","src_id":"6049","5":"6049","creation_date":"1155007069","6":"1155007069"},{"0":"1623","vim_version":"6.0","1":"6.0","script_version":"1.4","2":"1.4","version_comment":"1. The sequence of creating the custom folds no longer matters.\r\n2. Added some more custom folds (includes, defines, .. with phpdoc can now be folded too).\r\n3. It can search farther for PhpDoc comments.\r\n4. It can be configured to fold more empty 'trailing' lines.\r\n5. Adjusted PHPFoldText a bit. \r\n6. Fixed a minor bug in the class fold regex (PEAR's QuickForm.php works now too).","3":"1. The sequence of creating the custom folds no longer matters.\r\n2. Added some more custom folds (includes, defines, .. with phpdoc can now be folded too).\r\n3. It can search farther for PhpDoc comments.\r\n4. It can be configured to fold more empty 'trailing' lines.\r\n5. Adjusted PHPFoldText a bit. \r\n6. Fixed a minor bug in the class fold regex (PEAR's QuickForm.php works now too).","package":"phpfolding.vim","4":"phpfolding.vim","src_id":"6045","5":"6045","creation_date":"1154881879","6":"1154881879"},{"0":"1623","vim_version":"6.0","1":"6.0","script_version":"1.3","2":"1.3","version_comment":"1. Extensive\/slow parsing of brackets is now optional.\r\n2. Class variables \"var $foo = '';\" can be folded with their PhpDoc.\r\n3. Marker style folds ({{{, }}}) can be folded now too.","3":"1. Extensive\/slow parsing of brackets is now optional.\r\n2. Class variables \"var $foo = '';\" can be folded with their PhpDoc.\r\n3. Marker style folds ({{{, }}}) can be folded now too.","package":"phpfolding.vim","4":"phpfolding.vim","src_id":"6011","5":"6011","creation_date":"1154279921","6":"1154279921"},{"0":"1623","vim_version":"6.0","1":"6.0","script_version":"1.2","2":"1.2","version_comment":"1. Previously opened folds are restored when executing the script multiple times (thanks to Marijn Koesen for that idea)\r\n2. The cursor position is now remembered and restored in Linux\r\n3. Cleaned up foldtext a bit","3":"1. Previously opened folds are restored when executing the script multiple times (thanks to Marijn Koesen for that idea)\r\n2. The cursor position is now remembered and restored in Linux\r\n3. Cleaned up foldtext a bit","package":"phpfolding.vim","4":"phpfolding.vim","src_id":"6009","5":"6009","creation_date":"1154240041","6":"1154240041"},{"0":"1623","vim_version":"6.0","1":"6.0","script_version":"1.1","2":"1.1","version_comment":"1. PHP API comments no longer appear in the fold names.\r\n2. The following function header is now recognized:\r\n\r\nfunction (...,\r\n    ....)\r\n{","3":"1. PHP API comments no longer appear in the fold names.\r\n2. The following function header is now recognized:\r\n\r\nfunction (...,\r\n    ....)\r\n{","package":"phpfolding.vim","4":"phpfolding.vim","src_id":"6006","5":"6006","creation_date":"1154167555","6":"1154167555"},{"0":"1623","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"phpfolding.vim","4":"phpfolding.vim","src_id":"6005","5":"6005","creation_date":"1154163506","6":"1154163506"}]},"1622":{"script_id":"1622","0":"1622","script_name":"TIMEIT","1":"TIMEIT","script_type":"utility","2":"utility","summary":"Time execution of vim command(s) with subsecond resolution","3":"Time execution of vim command(s) with subsecond resolution","description":"\" Time execution of vim command(s) with subsecond resolution,\r\n\" For example:\r\n\"      :TIM sleep 100m\r\n\" prnits\r\n\"      Execution took   0.100301 sec.\r\n\" With counter, TIMEIT times that many repetitions of the command:\r\n\"      :10TIM sleep 100m\r\n\" prints:\r\n\"      10 repetitions took   1.039352 sec.\r\n\" You can use sequence of |-separated commands under TIM:\r\n\"      :10TIM syntax off | syntax on\r\n\" This will time ten repetitions of (syntax off | syntax on)\r\n\" sequence, not 10 repetitions of \"syntax off\" followed by\r\n\" one untimes \"syntax on\".\r\n","4":"\" Time execution of vim command(s) with subsecond resolution,\r\n\" For example:\r\n\"      :TIM sleep 100m\r\n\" prnits\r\n\"      Execution took   0.100301 sec.\r\n\" With counter, TIMEIT times that many repetitions of the command:\r\n\"      :10TIM sleep 100m\r\n\" prints:\r\n\"      10 repetitions took   1.039352 sec.\r\n\" You can use sequence of |-separated commands under TIM:\r\n\"      :10TIM syntax off | syntax on\r\n\" This will time ten repetitions of (syntax off | syntax on)\r\n\" sequence, not 10 repetitions of \"syntax off\" followed by\r\n\" one untimes \"syntax on\".\r\n","install_details":"Download the script from the link below and \r\ncopy it into your ~\/.vim\/plugin directory.\r\nCreate this directory if it does not yet exist.\r\nRestart vim. That's it. \r\n","5":"Download the script from the link below and \r\ncopy it into your ~\/.vim\/plugin directory.\r\nCreate this directory if it does not yet exist.\r\nRestart vim. That's it. \r\n","first_name":"Yakov","6":"Yakov","last_name":"Lerner","7":"Lerner","releases":[{"0":"1622","vim_version":"7.0","1":"7.0","script_version":"071014","2":"071014","version_comment":"With contributions from Andy Wokula. Checksum 105516337","3":"With contributions from Andy Wokula. Checksum 105516337","package":"TimeIt.vim","4":"TimeIt.vim","src_id":"7793","5":"7793","creation_date":"1192339861","6":"1192339861"},{"0":"1622","vim_version":"7.0","1":"7.0","script_version":"20060729","2":"20060729","version_comment":"Initial upload","3":"Initial upload","package":"TimeIt.vim","4":"TimeIt.vim","src_id":"6004","5":"6004","creation_date":"1154104301","6":"1154104301"}]},"1621":{"script_id":"1621","0":"1621","script_name":"phpx","1":"phpx","script_type":"color scheme","2":"color scheme","summary":"Like phps colorscheme, similar to php net. Light background. Xterm capability.","3":"Like phps colorscheme, similar to php net. Light background. Xterm capability.","description":"Like phps colorscheme, looks similar to php net. \r\nLight background colorscheme.\r\nxterm support.","4":"Like phps colorscheme, looks similar to php net. \r\nLight background colorscheme.\r\nxterm support.","install_details":"copy to ~\/.vim\/colors","5":"copy to ~\/.vim\/colors","first_name":"Walter","6":"Walter","last_name":"Hutchins","7":"Hutchins","releases":[{"0":"1621","vim_version":"6.0","1":"6.0","script_version":"1.1","2":"1.1","version_comment":"Modified to work with reloaded.vim a.k.a. ps_color.vim","3":"Modified to work with reloaded.vim a.k.a. ps_color.vim","package":"phpx.vim","4":"phpx.vim","src_id":"6019","5":"6019","creation_date":"1154429709","6":"1154429709"},{"0":"1621","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"phpx.vim","4":"phpx.vim","src_id":"6003","5":"6003","creation_date":"1154099640","6":"1154099640"}]},"1620":{"script_id":"1620","0":"1620","script_name":"scvim","1":"scvim","script_type":"utility","2":"utility","summary":"syntax highlighing, interaction and help\/class def lookup for Supercollider","3":"syntax highlighing, interaction and help\/class def lookup for Supercollider","description":"See http:\/\/x37v.info\/scvim\/ for more details. [and the most up to date version].\r\n\r\nHi, these are my supercollider interaction scripts and syntax highlighting for vim.\r\n\r\nIt works on both linux and osx.\r\n\r\nSo far I have:\r\n\r\n    * Syntax Highlighting\r\n    * The ability to single lines, visual blocks or supercollider blocks (ie surrounded by parens) to sclang\r\n    * key bindings for s.freeAll, thisProcess.stop() [cmd-. in the SC editor], TempoClock.clear()\r\n    * In-line Help\r\n    * In-line Class Look-up","4":"See http:\/\/x37v.info\/scvim\/ for more details. [and the most up to date version].\r\n\r\nHi, these are my supercollider interaction scripts and syntax highlighting for vim.\r\n\r\nIt works on both linux and osx.\r\n\r\nSo far I have:\r\n\r\n    * Syntax Highlighting\r\n    * The ability to single lines, visual blocks or supercollider blocks (ie surrounded by parens) to sclang\r\n    * key bindings for s.freeAll, thisProcess.stop() [cmd-. in the SC editor], TempoClock.clear()\r\n    * In-line Help\r\n    * In-line Class Look-up","install_details":"see the tar file for install details.","5":"see the tar file for install details.","first_name":"Alex","6":"Alex","last_name":"Norman","7":"Norman","releases":[{"0":"1620","vim_version":"7.0","1":"7.0","script_version":"beta12","2":"beta12","version_comment":"Added a Scons installer, changed things up quite a bit.","3":"Added a Scons installer, changed things up quite a bit.","package":"scvim-beta12.tar.gz","4":"scvim-beta12.tar.gz","src_id":"9118","5":"9118","creation_date":"1218620810","6":"1218620810"},{"0":"1620","vim_version":"7.0","1":"7.0","script_version":"beta11","2":"beta11","version_comment":"updated to include html help processing","3":"updated to include html help processing","package":"scvim-beta11.tar.gz","4":"scvim-beta11.tar.gz","src_id":"7985","5":"7985","creation_date":"1195832004","6":"1195832004"},{"0":"1620","vim_version":"7.0","1":"7.0","script_version":"beta8","2":"beta8","version_comment":"Initial upload","3":"Initial upload","package":"scvim-beta8.tar.gz","4":"scvim-beta8.tar.gz","src_id":"6000","5":"6000","creation_date":"1154079528","6":"1154079528"}]},"1619":{"script_id":"1619","0":"1619","script_name":"vimtips_with_comments","1":"vimtips_with_comments","script_type":"utility","2":"utility","summary":"a package of all tips from vim's homesite with all comments","3":"a package of all tips from vim's homesite with all comments","description":"   Yes, we can get a tarball of vimtips from http:\/\/vim.sf.net\/tip_download.php, but there are several things missing, for example, there is no comments and no rate record. But they are really very helpful especially when there are many tips in the tip's comments inspired by the current tip. And the rate is also very useful when we need to review tons of tips. Sometime I want to sort all the tips based on the quotient of rating, usally I can find some very useful but not popular tips by this way :)\r\n   In fact, I think there are many other ways to make full use of vim tips, I think post tips about how to make full use of vim tips as a new vim tip will be interesting ;) \r\n   I make this tarball to make my life easier and hope it will be helpful to you. \r\n\r\n   In practice, I use the following script to grab all the scripts. It is not perfect but it works well. Feel free to modify it to make it more powerful and don't forget to tell about your progress :)\r\n\r\n==================================>8=========================================\r\n\r\n#! \/usr\/bin\/env bash\r\n\r\nw3m -dump http:\/\/vim.sourceforge.net\/tips\/tip.php?tip_id=$1 |cut -c 28- | sed -ne '1i\\\r\n======================================================================\\\r\n\r\n1,4d\r\n\/^\\s*\\[Add Note\\]\/Q\r\np'\r\n\r\n===================================>8===========================================\r\n\r\n   TODO: \r\n        * add a colorscheme for tips with comments\r\n   \r\n\r\n","4":"   Yes, we can get a tarball of vimtips from http:\/\/vim.sf.net\/tip_download.php, but there are several things missing, for example, there is no comments and no rate record. But they are really very helpful especially when there are many tips in the tip's comments inspired by the current tip. And the rate is also very useful when we need to review tons of tips. Sometime I want to sort all the tips based on the quotient of rating, usally I can find some very useful but not popular tips by this way :)\r\n   In fact, I think there are many other ways to make full use of vim tips, I think post tips about how to make full use of vim tips as a new vim tip will be interesting ;) \r\n   I make this tarball to make my life easier and hope it will be helpful to you. \r\n\r\n   In practice, I use the following script to grab all the scripts. It is not perfect but it works well. Feel free to modify it to make it more powerful and don't forget to tell about your progress :)\r\n\r\n==================================>8=========================================\r\n\r\n#! \/usr\/bin\/env bash\r\n\r\nw3m -dump http:\/\/vim.sourceforge.net\/tips\/tip.php?tip_id=$1 |cut -c 28- | sed -ne '1i\\\r\n======================================================================\\\r\n\r\n1,4d\r\n\/^\\s*\\[Add Note\\]\/Q\r\np'\r\n\r\n===================================>8===========================================\r\n\r\n   TODO: \r\n        * add a colorscheme for tips with comments\r\n   \r\n\r\n","install_details":"1. download the package\r\n2. untar the package by command: tar -xjvf vimtips_with_comments.tar.bz2\r\n3. open the vimtips_with_comments.txt by vim \r\nThat's all, enjoy! ","5":"1. download the package\r\n2. untar the package by command: tar -xjvf vimtips_with_comments.tar.bz2\r\n3. open the vimtips_with_comments.txt by vim \r\nThat's all, enjoy! ","first_name":"Vincent","6":"Vincent","last_name":"Wang","7":"Wang","releases":[{"0":"1619","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"vimtips_with_comments.tar.bz2","4":"vimtips_with_comments.tar.bz2","src_id":"5998","5":"5998","creation_date":"1154056228","6":"1154056228"}]},"1618":{"script_id":"1618","0":"1618","script_name":"cshelper","1":"cshelper","script_type":"utility","2":"utility","summary":"Highlights the highlighting groups of the colorscheme you are editing.","3":"Highlights the highlighting groups of the colorscheme you are editing.","description":"Color Scheme helper\r\n\r\nThis just highlights the highlighting groups of the color scheme you are\r\nediting in the current buffer -- so that you can see what you are doing.\r\n\r\n:CShelper   - Do 'color g:colors_name' of the file in the buffer, then do CShelperHL\r\n\r\n:CShelperHL - update highlight from current buffer\r\n","4":"Color Scheme helper\r\n\r\nThis just highlights the highlighting groups of the color scheme you are\r\nediting in the current buffer -- so that you can see what you are doing.\r\n\r\n:CShelper   - Do 'color g:colors_name' of the file in the buffer, then do CShelperHL\r\n\r\n:CShelperHL - update highlight from current buffer\r\n","install_details":"copy to ~\/.vim\/plugin","5":"copy to ~\/.vim\/plugin","first_name":"Walter","6":"Walter","last_name":"Hutchins","7":"Hutchins","releases":[{"0":"1618","vim_version":"6.0","1":"6.0","script_version":"1.4","2":"1.4","version_comment":"Changed handling of any leading whitespace preceeding highlight command.","3":"Changed handling of any leading whitespace preceeding highlight command.","package":"cshelper.vim","4":"cshelper.vim","src_id":"6010","5":"6010","creation_date":"1154243958","6":"1154243958"},{"0":"1618","vim_version":"6.0","1":"6.0","script_version":"1.3","2":"1.3","version_comment":"Fixed - links were blocking highlight.","3":"Fixed - links were blocking highlight.","package":"cshelper.vim","4":"cshelper.vim","src_id":"5999","5":"5999","creation_date":"1154064102","6":"1154064102"},{"0":"1618","vim_version":"6.0","1":"6.0","script_version":"1.2","2":"1.2","version_comment":"Initial upload","3":"Initial upload","package":"cshelper.vim","4":"cshelper.vim","src_id":"5996","5":"5996","creation_date":"1154030387","6":"1154030387"}]},"1617":{"script_id":"1617","0":"1617","script_name":"afterimage.vim","1":"afterimage.vim","script_type":"utility","2":"utility","summary":"Edit PNG and GIF icons by converting them to XPM","3":"Edit PNG and GIF icons by converting them to XPM","description":"This plugin converts PNG and GIF icons to XPM with ImageMagick when edited in vim. XPM is an easy to edit plain text image format (it looks great in gvim, too).  The plugin is handy for quick changes to small icons; bigger files are of course more managable in a traditional image editor.\r\n\r\nSee a screenshot at http:\/\/yfrog.com\/37afterimagep .\r\n\r\nAs a bonus, support is also provided for PDFs, Word documents, and Mac OS X plist files.\r\n\r\nhttp:\/\/github.com\/tpope\/vim-afterimage","4":"This plugin converts PNG and GIF icons to XPM with ImageMagick when edited in vim. XPM is an easy to edit plain text image format (it looks great in gvim, too).  The plugin is handy for quick changes to small icons; bigger files are of course more managable in a traditional image editor.\r\n\r\nSee a screenshot at http:\/\/yfrog.com\/37afterimagep .\r\n\r\nAs a bonus, support is also provided for PDFs, Word documents, and Mac OS X plist files.\r\n\r\nhttp:\/\/github.com\/tpope\/vim-afterimage","install_details":"Install in ~\/.vim\/plugin, or vimfiles\/plugin.  ImageMagick needs to be installed, and \"convert\" in your path.","5":"Install in ~\/.vim\/plugin, or vimfiles\/plugin.  ImageMagick needs to be installed, and \"convert\" in your path.","first_name":"Tim","6":"Tim","last_name":"Pope","7":"Pope","releases":[{"0":"1617","vim_version":"7.0","1":"7.0","script_version":"2.2","2":"2.2","version_comment":"Fix write of new plists.","3":"Fix write of new plists.","package":"afterimage.zip","4":"afterimage.zip","src_id":"19284","5":"19284","creation_date":"1357056648","6":"1357056648"},{"0":"1617","vim_version":"6.0","1":"6.0","script_version":"2.1","2":"2.1","version_comment":"Be a little more aggressive in setting filetype to XPM","3":"Be a little more aggressive in setting filetype to XPM","package":"afterimage.zip","4":"afterimage.zip","src_id":"12375","5":"12375","creation_date":"1266032173","6":"1266032173"},{"0":"1617","vim_version":"6.0","1":"6.0","script_version":"2.0","2":"2.0","version_comment":"Rename imagemagick.vim to afterimage.vim.\r\nAdd support for pdf, doc, and plist.\r\nExtract documentation comments to help file.","3":"Rename imagemagick.vim to afterimage.vim.\r\nAdd support for pdf, doc, and plist.\r\nExtract documentation comments to help file.","package":"afterimage.zip","4":"afterimage.zip","src_id":"12117","5":"12117","creation_date":"1263749065","6":"1263749065"},{"0":"1617","vim_version":"6.0","1":"6.0","script_version":"1.1","2":"1.1","version_comment":"Initial upload","3":"Initial upload","package":"imagemagick.vim","4":"imagemagick.vim","src_id":"5994","5":"5994","creation_date":"1153936303","6":"1153936303"}]},"1616":{"script_id":"1616","0":"1616","script_name":"tdl.vim","1":"tdl.vim","script_type":"syntax","2":"syntax","summary":"Vim syntax file for the TreeDL 2.3 language","3":"Vim syntax file for the TreeDL 2.3 language","description":"TreeDL stands for Tree Description Language. See http:\/\/treedl.sourceforge.net for details.","4":"TreeDL stands for Tree Description Language. See http:\/\/treedl.sourceforge.net for details.","install_details":"Copy tdl.vim to the `runtimepath\/syntax' directory. Add the following line to the `runtimepath\/filetype.vim' file:\r\n\tau BufNewFile,BufRead *.tdl             setf tdl","5":"Copy tdl.vim to the `runtimepath\/syntax' directory. Add the following line to the `runtimepath\/filetype.vim' file:\r\n\tau BufNewFile,BufRead *.tdl             setf tdl","first_name":"Mikhail","6":"Mikhail","last_name":"Skvortsov","7":"Skvortsov","releases":[{"0":"1616","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"tdl-syntax.tgz","4":"tdl-syntax.tgz","src_id":"5993","5":"5993","creation_date":"1153881304","6":"1153881304"}]},"1615":{"script_id":"1615","0":"1615","script_name":"SWIG syntax","1":"SWIG syntax","script_type":"syntax","2":"syntax","summary":"Syntax file for SWIG","3":"Syntax file for SWIG","description":"This is a syntax file for SWIG (Simplified Wrapper Interface Generator) description files.  The default syntax for .i files highlights comments in a reverse color scheme which is really horrible.  This syntax builds on vim's c++ syntax by adding highlighting for common swig directives and user defined directives.  For an alternative syntax, see  vimscript #1247 (which I found after writing this).  ","4":"This is a syntax file for SWIG (Simplified Wrapper Interface Generator) description files.  The default syntax for .i files highlights comments in a reverse color scheme which is really horrible.  This syntax builds on vim's c++ syntax by adding highlighting for common swig directives and user defined directives.  For an alternative syntax, see  vimscript #1247 (which I found after writing this).  ","install_details":"copy the script to ~\/.vim\/syntax\/ and add the following to your vimrc:\r\nau BufNewFile,BufRead *.i set filetype=swig\r\nau BufNewFile,BufRead *.swg set filetype=swig\r\n","5":"copy the script to ~\/.vim\/syntax\/ and add the following to your vimrc:\r\nau BufNewFile,BufRead *.i set filetype=swig\r\nau BufNewFile,BufRead *.swg set filetype=swig\r\n","first_name":"Roman","6":"Roman","last_name":"Stanchak","7":"Stanchak","releases":[{"0":"1615","vim_version":"6.0","1":"6.0","script_version":"0.0.1","2":"0.0.1","version_comment":"Initial upload","3":"Initial upload","package":"swig.vim","4":"swig.vim","src_id":"5991","5":"5991","creation_date":"1153830745","6":"1153830745"}]},"1614":{"script_id":"1614","0":"1614","script_name":"Satori Color Scheme","1":"Satori Color Scheme","script_type":"color scheme","2":"color scheme","summary":"Satori is an elegant and clean color scheme for Vim","3":"Satori is an elegant and clean color scheme for Vim","description":"Satori is an elegant and clean color scheme for Vim.\r\nIt looks great on black or white backgrounds.","4":"Satori is an elegant and clean color scheme for Vim.\r\nIt looks great on black or white backgrounds.","install_details":"Download satori.vim from this page and copy satori.vim to ~\/.vim\/colors\/ \r\n\r\nEdit your ~\/.vimrc and insert or update:\r\n\r\nsyntax on\r\ncolorscheme satori","5":"Download satori.vim from this page and copy satori.vim to ~\/.vim\/colors\/ \r\n\r\nEdit your ~\/.vimrc and insert or update:\r\n\r\nsyntax on\r\ncolorscheme satori","first_name":"Rud\u00c3\u00a1","6":"Rud\u00c3\u00a1","last_name":"Moura","7":"Moura","releases":[{"0":"1614","vim_version":"7.3","1":"7.3","script_version":"2017","2":"2017","version_comment":"Satori 2017.\r\n- Menu colors.","3":"Satori 2017.\r\n- Menu colors.","package":"satori.vim","4":"satori.vim","src_id":"25458","5":"25458","creation_date":"1501294209","6":"1501294209"},{"0":"1614","vim_version":"7.3","1":"7.3","script_version":"2014","2":"2014","version_comment":"Satori 2014.","3":"Satori 2014.","package":"satori.vim","4":"satori.vim","src_id":"21667","5":"21667","creation_date":"1395798840","6":"1395798840"},{"0":"1614","vim_version":"7.3","1":"7.3","script_version":"2013","2":"2013","version_comment":"Satori version 2013.\r\n- Using DarkCyan for Comments.\r\n- Verified on OS X Mavericks and Fedora 19.","3":"Satori version 2013.\r\n- Using DarkCyan for Comments.\r\n- Verified on OS X Mavericks and Fedora 19.","package":"satori.vim","4":"satori.vim","src_id":"21011","5":"21011","creation_date":"1383788575","6":"1383788575"},{"0":"1614","vim_version":"7.2","1":"7.2","script_version":"2010","2":"2010","version_comment":"Using color green for searches\r\nFine tuned Error and Todo\r\nUpdated my email","3":"Using color green for searches\r\nFine tuned Error and Todo\r\nUpdated my email","package":"satori.vim","4":"satori.vim","src_id":"14073","5":"14073","creation_date":"1287451646","6":"1287451646"},{"0":"1614","vim_version":"7.0","1":"7.0","script_version":"2008","2":"2008","version_comment":"- No longer coloring Functions group.\r\n- Updated author's email.\r\n- Other Cosmetics.","3":"- No longer coloring Functions group.\r\n- Updated author's email.\r\n- Other Cosmetics.","package":"satori.vim","4":"satori.vim","src_id":"8345","5":"8345","creation_date":"1203864396","6":"1203864396"},{"0":"1614","vim_version":"6.0","1":"6.0","script_version":"2006update","2":"2006update","version_comment":"- Numbers are now colored like strings (red)\r\n- Special symbols like \\n is now colored magenta for a better contrast to strings\r\n- Preprocessor macros is now colored  blue","3":"- Numbers are now colored like strings (red)\r\n- Special symbols like \\n is now colored magenta for a better contrast to strings\r\n- Preprocessor macros is now colored  blue","package":"satori.vim","4":"satori.vim","src_id":"6465","5":"6465","creation_date":"1164390515","6":"1164390515"},{"0":"1614","vim_version":"6.0","1":"6.0","script_version":"2006","2":"2006","version_comment":"Initial upload","3":"Initial upload","package":"satori.vim","4":"satori.vim","src_id":"5979","5":"5979","creation_date":"1153586354","6":"1153586354"}]},"1613":{"script_id":"1613","0":"1613","script_name":"phps","1":"phps","script_type":"syntax","2":"syntax","summary":"colors like .phps","3":"colors like .phps","description":"It for people who like PHP (http:\/\/www.php.net\/).\r\nI try to find script for vim, that have same colors like .phps file, i can't found it. And then i write my color scheme...\r\nit's color scheme only for GUI version.\r\n\r\n\r\nAny suggestions, patchs and new versions mail me to MishaStrij@Mail.Ru - i write your name here)))","4":"It for people who like PHP (http:\/\/www.php.net\/).\r\nI try to find script for vim, that have same colors like .phps file, i can't found it. And then i write my color scheme...\r\nit's color scheme only for GUI version.\r\n\r\n\r\nAny suggestions, patchs and new versions mail me to MishaStrij@Mail.Ru - i write your name here)))","install_details":"UNIX\r\nJust put file to directory ~\/.vim\/colors\/\r\nWINDOWS (for vim 7.0)\r\nJust put file in directory [VIM_INSTALL_DIR]\\vim70\\colors\r\nfor example i put script to \"C:\\Program Files\\Vim\\vim70\\colors\"\r\n","5":"UNIX\r\nJust put file to directory ~\/.vim\/colors\/\r\nWINDOWS (for vim 7.0)\r\nJust put file in directory [VIM_INSTALL_DIR]\\vim70\\colors\r\nfor example i put script to \"C:\\Program Files\\Vim\\vim70\\colors\"\r\n","first_name":"Misha","6":"Misha","last_name":"Strijov","7":"Strijov","releases":[{"0":"1613","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"phps.vim","4":"phps.vim","src_id":"5977","5":"5977","creation_date":"1153459998","6":"1153459998"}]},"1612":{"script_id":"1612","0":"1612","script_name":"vj","1":"vj","script_type":"color scheme","2":"color scheme","summary":"color scheme","3":"color scheme","description":"This scheme is well suited for low and high light condition.","4":"This scheme is well suited for low and high light condition.","install_details":"Just drop it in color folder.","5":"Just drop it in color folder.","first_name":"vijayandra","6":"vijayandra","last_name":"singh","7":"singh","releases":[{"0":"1612","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"vj.vim","4":"vj.vim","src_id":"5975","5":"5975","creation_date":"1153413359","6":"1153413359"}]},"1611":{"script_id":"1611","0":"1611","script_name":"Access SQL Syntax file","1":"Access SQL Syntax file","script_type":"syntax","2":"syntax","summary":"full access syntax highlighting","3":"full access syntax highlighting","description":"Including:\r\n asql.vim - syntax definition file\r\n filetype.vim - with automatical access sql recognition\r\n synmenu.vim - modified menu file\r\n\r\nfor lower versions than 7:\r\nWARNING: I tried to replace filetypes.vim with that from this package, but in version 6.4\r\nIt won't run and it completely disable all filetype autodetections... So if you have lower version\r\nthan 7 please excuse me, you must extend your autodetection In filetypes yourself,\r\nIf someone have done it, please send it to me, i will include, if not, I will do that as soon as possible","4":"Including:\r\n asql.vim - syntax definition file\r\n filetype.vim - with automatical access sql recognition\r\n synmenu.vim - modified menu file\r\n\r\nfor lower versions than 7:\r\nWARNING: I tried to replace filetypes.vim with that from this package, but in version 6.4\r\nIt won't run and it completely disable all filetype autodetections... So if you have lower version\r\nthan 7 please excuse me, you must extend your autodetection In filetypes yourself,\r\nIf someone have done it, please send it to me, i will include, if not, I will do that as soon as possible","install_details":"In package as plain or rtf","5":"In package as plain or rtf","first_name":"Matej","6":"Matej","last_name":"Kasper","7":"Kasper","releases":[{"0":"1611","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"AccessSQL.zip","4":"AccessSQL.zip","src_id":"5970","5":"5970","creation_date":"1153303477","6":"1153303477"}]},"1610":{"script_id":"1610","0":"1610","script_name":"IncRoman.vim","1":"IncRoman.vim","script_type":"utility","2":"utility","summary":"Cope with Roman numbers","3":"Cope with Roman numbers","description":"Increase or decrease a Roman number found under the cursor, with [count].\r\nIf a decimal number is found it is converted into its corresponding Roman\r\nnumber, ignoring the [count].  Any other word is converted to the Roman\r\nnumber that [count] corresponds to.\r\n\r\nRange: I .. MMMCMXCIX (1..3999)\r\nHigher numbers result in more than three \"M\"s.\r\n\r\nThere are interface mappings: <plug>IncRoman and <plug>DecRoman .\r\nThey can be mapped globally or local to buffer, the latter is the default.\r\nFrom the script:\r\n    nmap <unique><buffer> <C-A> <plug>IncRoman\r\n    nmap <unique><buffer> <C-X> <plug>DecRoman\r\n\r\nTherefore if you want to use the script as a plugin, you should define\r\nglobal keys in your .vimrc:\r\n    nmap <C-A> <plug>IncRoman\r\n    nmap <C-X> <plug>DecRoman\r\n\r\nOther scripts with support for Roman numbers:\r\nvimscript #197 genutils : General utility functions\r\n    genutils#Roman2Decimal(str)\r\nvimscript #431 VimFootnotes : Insert various types of footnotes\r\nvimscript #670 VisIncr : Produce increasing\/decreasing columns of numbers, dates, or daynames\r\nvimscript #2120 speeddating.vim : Use CTRL-A\/X to increment dates, times, and more\r\n\r\nLast Change: 2007 Jan 11","4":"Increase or decrease a Roman number found under the cursor, with [count].\r\nIf a decimal number is found it is converted into its corresponding Roman\r\nnumber, ignoring the [count].  Any other word is converted to the Roman\r\nnumber that [count] corresponds to.\r\n\r\nRange: I .. MMMCMXCIX (1..3999)\r\nHigher numbers result in more than three \"M\"s.\r\n\r\nThere are interface mappings: <plug>IncRoman and <plug>DecRoman .\r\nThey can be mapped globally or local to buffer, the latter is the default.\r\nFrom the script:\r\n    nmap <unique><buffer> <C-A> <plug>IncRoman\r\n    nmap <unique><buffer> <C-X> <plug>DecRoman\r\n\r\nTherefore if you want to use the script as a plugin, you should define\r\nglobal keys in your .vimrc:\r\n    nmap <C-A> <plug>IncRoman\r\n    nmap <C-X> <plug>DecRoman\r\n\r\nOther scripts with support for Roman numbers:\r\nvimscript #197 genutils : General utility functions\r\n    genutils#Roman2Decimal(str)\r\nvimscript #431 VimFootnotes : Insert various types of footnotes\r\nvimscript #670 VisIncr : Produce increasing\/decreasing columns of numbers, dates, or daynames\r\nvimscript #2120 speeddating.vim : Use CTRL-A\/X to increment dates, times, and more\r\n\r\nLast Change: 2007 Jan 11","install_details":"Three options: (v2 of the script)\r\n(1) Activate for current buffer:\r\n:source incroman.vim\r\n\r\n(2) Use as a plugin.  Then you need global mappings (see description).\r\n\r\n(3) Source from an ftplugin.\r\n","5":"Three options: (v2 of the script)\r\n(1) Activate for current buffer:\r\n:source incroman.vim\r\n\r\n(2) Use as a plugin.  Then you need global mappings (see description).\r\n\r\n(3) Source from an ftplugin.\r\n","first_name":"Andy","6":"Andy","last_name":"Wokula","7":"Wokula","releases":[{"0":"1610","vim_version":"6.0","1":"6.0","script_version":"2","2":"2","version_comment":"now can be used globally and locally, avoids global var for the count","3":"now can be used globally and locally, avoids global var for the count","package":"incroman.vim","4":"incroman.vim","src_id":"6663","5":"6663","creation_date":"1169797609","6":"1169797609"},{"0":"1610","vim_version":"6.0","1":"6.0","script_version":"1","2":"1","version_comment":"Initial upload","3":"Initial upload","package":"incroman.vim","4":"incroman.vim","src_id":"5961","5":"5961","creation_date":"1153116242","6":"1153116242"}]},"1609":{"script_id":"1609","0":"1609","script_name":"Ada Bundle","1":"Ada Bundle","script_type":"ftplugin","2":"ftplugin","summary":"Complete Ada-Mode (https:\/\/github.com\/krischik\/Ada-Bundle)","3":"Complete Ada-Mode (https:\/\/github.com\/krischik\/Ada-Bundle)","description":"This is a maintained mirror of http:\/\/www.vim.org\/scripts\/script.php?script_id=1609\r\n\r\nContains all files for the new Ada mode. It also has a vim help file which you can call with\r\n\r\n:help ada.txt.\r\n\r\nIncluded is:\r\n\r\n* Syntax highlight\r\n* Auto indenting\r\n* Tag searching\r\n* Classic code completion\r\n* Omni code completion\r\n* Online help\r\n\r\nFor some functionality you need a ctags program.\r\n\r\nDon't forget to actually activate filetype and syntax support:\r\n\r\n:filetype plugin indent on\r\n:syntax enable\r\n\r\nThe Ada mode can be be further extend with the following Scripts:\r\n\r\n; Rainbow Parenthesis:  vimscript#1561, https:\/\/github.com\/krischik\/vim-rainbow-parenthesis.git\r\n; Numbered Backups:  vimscript#1537, https:\/\/github.com\/krischik\/vim-backup.git\r\n; nerd_comments.vim:  vimscript#1218\r\n; matchit.vim:  vimscript#39\r\n; taglist.vim:  vimscript#273\r\n\r\nThe GNU Ada project [3] offers ready patched binary rpm's including the Ada-Mode, all the\r\nscripts mentioned above and Ada aware exuberant Ctags for easy installation.\r\n\r\nChanges with official version, included in Vim\/Neovim:\r\n\r\n* Add support for both Rainbow Parenthesis and Rainbow Parentheses Improved plugin.\r\n* Removed all tags commands which are now in base Vim (like jump to tag).\r\n* Added support for Ale plugin.\r\n* Updated help file.\r\n* Removed support for Dec Ada compiler.\r\n* Fixed and extended support for Vim sessions on loading GNAT project files (it is possible to enable or disable it).\r\n* Added support for Ada 2012.\r\n* Updated omni completion function: now it should be a bit faster and show items definitions too.\r\n* Removed support for GNAT xref.\r\n* Some other fixes for bugs.\r\n\r\nIf you want fully extend your experience with Vim\/NeoVim as Ada IDE, I\r\nrecommend to use Vim-Ada bundle: https:\/\/github.com\/thindil\/vim-ada\r\n\r\nAll propositions and problems about this version of vim-ada, please\r\nreport here, not to the maintainers of Vim or NeoVim.\r\n\r\n| Vim-Script  || https:\/\/www.vim.org\/scripts\/script.php?script_id=1609\r\n| Source      || https:\/\/github.com\/krischik\/vim-ada\r\n| Wiki        || https:\/\/github.com\/krischik\/vim-ada\/wiki\r\n| Releases    || https:\/\/github.com\/krischik\/vim-ada\/releases \r\n| Issues      || https:\/\/github.com\/krischik\/vim-ada\/issues \r\n| Discussions || https:\/\/github.com\/krischik\/vim-ada\/discussions \r\n","4":"This is a maintained mirror of http:\/\/www.vim.org\/scripts\/script.php?script_id=1609\r\n\r\nContains all files for the new Ada mode. It also has a vim help file which you can call with\r\n\r\n:help ada.txt.\r\n\r\nIncluded is:\r\n\r\n* Syntax highlight\r\n* Auto indenting\r\n* Tag searching\r\n* Classic code completion\r\n* Omni code completion\r\n* Online help\r\n\r\nFor some functionality you need a ctags program.\r\n\r\nDon't forget to actually activate filetype and syntax support:\r\n\r\n:filetype plugin indent on\r\n:syntax enable\r\n\r\nThe Ada mode can be be further extend with the following Scripts:\r\n\r\n; Rainbow Parenthesis:  vimscript#1561, https:\/\/github.com\/krischik\/vim-rainbow-parenthesis.git\r\n; Numbered Backups:  vimscript#1537, https:\/\/github.com\/krischik\/vim-backup.git\r\n; nerd_comments.vim:  vimscript#1218\r\n; matchit.vim:  vimscript#39\r\n; taglist.vim:  vimscript#273\r\n\r\nThe GNU Ada project [3] offers ready patched binary rpm's including the Ada-Mode, all the\r\nscripts mentioned above and Ada aware exuberant Ctags for easy installation.\r\n\r\nChanges with official version, included in Vim\/Neovim:\r\n\r\n* Add support for both Rainbow Parenthesis and Rainbow Parentheses Improved plugin.\r\n* Removed all tags commands which are now in base Vim (like jump to tag).\r\n* Added support for Ale plugin.\r\n* Updated help file.\r\n* Removed support for Dec Ada compiler.\r\n* Fixed and extended support for Vim sessions on loading GNAT project files (it is possible to enable or disable it).\r\n* Added support for Ada 2012.\r\n* Updated omni completion function: now it should be a bit faster and show items definitions too.\r\n* Removed support for GNAT xref.\r\n* Some other fixes for bugs.\r\n\r\nIf you want fully extend your experience with Vim\/NeoVim as Ada IDE, I\r\nrecommend to use Vim-Ada bundle: https:\/\/github.com\/thindil\/vim-ada\r\n\r\nAll propositions and problems about this version of vim-ada, please\r\nreport here, not to the maintainers of Vim or NeoVim.\r\n\r\n| Vim-Script  || https:\/\/www.vim.org\/scripts\/script.php?script_id=1609\r\n| Source      || https:\/\/github.com\/krischik\/vim-ada\r\n| Wiki        || https:\/\/github.com\/krischik\/vim-ada\/wiki\r\n| Releases    || https:\/\/github.com\/krischik\/vim-ada\/releases \r\n| Issues      || https:\/\/github.com\/krischik\/vim-ada\/issues \r\n| Discussions || https:\/\/github.com\/krischik\/vim-ada\/discussions \r\n","install_details":"\r\nInstall from https:\/\/github.com\/krischik\/vim-ada using dein (https:\/\/github.com\/Shougo\/dein.vim) or similar:\r\n\r\ncall dein#begin('$HOME\/vimfiles\/bundles')\r\ncall dein#add('krischik\/vim-ada')\r\ncall dein#end()\r\ncall dein#install()\r\n","5":"\r\nInstall from https:\/\/github.com\/krischik\/vim-ada using dein (https:\/\/github.com\/Shougo\/dein.vim) or similar:\r\n\r\ncall dein#begin('$HOME\/vimfiles\/bundles')\r\ncall dein#add('krischik\/vim-ada')\r\ncall dein#end()\r\ncall dein#install()\r\n","first_name":"Martin","6":"Martin","last_name":"Krischik","7":"Krischik","releases":[{"0":"1609","vim_version":"7.0","1":"7.0","script_version":"5.4.0","2":"5.4.0","version_comment":"See https:\/\/github.com\/krischik\/vim-ada\/releases\/tag\/v_5.4.0","3":"See https:\/\/github.com\/krischik\/vim-ada\/releases\/tag\/v_5.4.0","package":"vim-ada-v_5.4.0.zip","4":"vim-ada-v_5.4.0.zip","src_id":"28292","5":"28292","creation_date":"1669953825","6":"1669953825"},{"0":"1609","vim_version":"7.0","1":"7.0","script_version":"5.3.1","2":"5.3.1","version_comment":"https:\/\/github.com\/krischik\/vim-ada\/releases\/tag\/v_5.3.1","3":"https:\/\/github.com\/krischik\/vim-ada\/releases\/tag\/v_5.3.1","package":"vim-ada-v_5.3.1.zip","4":"vim-ada-v_5.3.1.zip","src_id":"28239","5":"28239","creation_date":"1666987250","6":"1666987250"},{"0":"1609","vim_version":"7.0","1":"7.0","script_version":"5.3.0","2":"5.3.0","version_comment":"https:\/\/github.com\/krischik\/vim-ada\/releases\/tag\/v_5.3.0","3":"https:\/\/github.com\/krischik\/vim-ada\/releases\/tag\/v_5.3.0","package":"vim-ada-v_5.3.0.zip","4":"vim-ada-v_5.3.0.zip","src_id":"28238","5":"28238","creation_date":"1666987225","6":"1666987225"},{"0":"1609","vim_version":"7.0","1":"7.0","script_version":"5.2.1","2":"5.2.1","version_comment":"See https:\/\/github.com\/krischik\/vim-ada\/releases\/tag\/v_5.2.1","3":"See https:\/\/github.com\/krischik\/vim-ada\/releases\/tag\/v_5.2.1","package":"vim-ada-v_5.2.1.zip","4":"vim-ada-v_5.2.1.zip","src_id":"28234","5":"28234","creation_date":"1666800762","6":"1666800762"},{"0":"1609","vim_version":"7.0","1":"7.0","script_version":"5.2.0","2":"5.2.0","version_comment":"See: https:\/\/github.com\/krischik\/vim-ada\/releases\/tag\/v_5.2.0","3":"See: https:\/\/github.com\/krischik\/vim-ada\/releases\/tag\/v_5.2.0","package":"vim-ada-v_5.2.0.zip","4":"vim-ada-v_5.2.0.zip","src_id":"28233","5":"28233","creation_date":"1666747660","6":"1666747660"},{"0":"1609","vim_version":"7.0","1":"7.0","script_version":"5.1.0","2":"5.1.0","version_comment":"See: https:\/\/github.com\/krischik\/vim-ada\/releases\/tag\/v_5.1.0","3":"See: https:\/\/github.com\/krischik\/vim-ada\/releases\/tag\/v_5.1.0","package":"vim-ada-v_5.1.0.zip","4":"vim-ada-v_5.1.0.zip","src_id":"28232","5":"28232","creation_date":"1666747634","6":"1666747634"},{"0":"1609","vim_version":"7.0","1":"7.0","script_version":"5.0.0","2":"5.0.0","version_comment":"See https:\/\/github.com\/krischik\/Ada-Bundle\/releases\/tag\/v_5.0.0","3":"See https:\/\/github.com\/krischik\/Ada-Bundle\/releases\/tag\/v_5.0.0","package":"Ada-Bundle-v_5.0.0.zip","4":"Ada-Bundle-v_5.0.0.zip","src_id":"28178","5":"28178","creation_date":"1663002722","6":"1663002722"},{"0":"1609","vim_version":"7.0","1":"7.0","script_version":"4.6.2","2":"4.6.2","version_comment":"See https:\/\/github.com\/krischik\/Ada-Bundle\/releases\/tag\/v_4.6.2","3":"See https:\/\/github.com\/krischik\/Ada-Bundle\/releases\/tag\/v_4.6.2","package":"Ada-Bundle-v_4.6.2.zip","4":"Ada-Bundle-v_4.6.2.zip","src_id":"28177","5":"28177","creation_date":"1663002630","6":"1663002630"},{"0":"1609","vim_version":"7.0","1":"7.0","script_version":"4.6.1-vba","2":"4.6.1-vba","version_comment":"Bram did some nitpicking - this is the improved version for Vim 7.2.","3":"Bram did some nitpicking - this is the improved version for Vim 7.2.","package":"ada-4.6.1.vba","4":"ada-4.6.1.vba","src_id":"8904","5":"8904","creation_date":"1215502881","6":"1215502881"},{"0":"1609","vim_version":"7.0","1":"7.0","script_version":"4.6.1-tar","2":"4.6.1-tar","version_comment":"Bram did some nitpicking - this is the improved version for Vim 7.2.","3":"Bram did some nitpicking - this is the improved version for Vim 7.2.","package":"ada-4.6.1.tar.bz2","4":"ada-4.6.1.tar.bz2","src_id":"8902","5":"8902","creation_date":"1215502817","6":"1215502817"},{"0":"1609","vim_version":"7.0","1":"7.0","script_version":"4.6.0-vba","2":"4.6.0-vba","version_comment":"Mostly bug fixes. Also the version submitted for Vim 7.2.","3":"Mostly bug fixes. Also the version submitted for Vim 7.2.","package":"ada-4.6.0.vba","4":"ada-4.6.0.vba","src_id":"8900","5":"8900","creation_date":"1215494293","6":"1215494293"},{"0":"1609","vim_version":"7.0","1":"7.0","script_version":"4.6.0-tar","2":"4.6.0-tar","version_comment":"Mostly bug fixes. Also the version submitted for Vim 7.2.","3":"Mostly bug fixes. Also the version submitted for Vim 7.2.","package":"ada-4.6.0.tar.bz2","4":"ada-4.6.0.tar.bz2","src_id":"8899","5":"8899","creation_date":"1215494227","6":"1215494227"},{"0":"1609","vim_version":"7.0","1":"7.0","script_version":"4.5","2":"4.5","version_comment":"Bug fixes in the areas of key mappings, indenting, ","3":"Bug fixes in the areas of key mappings, indenting, ","package":"ada-4.5.0.vba","4":"ada-4.5.0.vba","src_id":"7686","5":"7686","creation_date":"1189996556","6":"1189996556"},{"0":"1609","vim_version":"7.0","1":"7.0","script_version":"4.4.0","2":"4.4.0","version_comment":"If you did not set g:ada_default_compiler and g:ada_default_compiler the scripts would fail miserable. Thank's to Taylor Venable for providing a patch to this problem.","3":"If you did not set g:ada_default_compiler and g:ada_default_compiler the scripts would fail miserable. Thank's to Taylor Venable for providing a patch to this problem.","package":"ada-4.4.0.vba","4":"ada-4.4.0.vba","src_id":"7385","5":"7385","creation_date":"1184914535","6":"1184914535"},{"0":"1609","vim_version":"7.0","1":"7.0","script_version":"4.3.0","2":"4.3.0","version_comment":"The VimBall is broken again. I like the VimBall idea if it only worked better. Anyway have a tar file in the meantime.","3":"The VimBall is broken again. I like the VimBall idea if it only worked better. Anyway have a tar file in the meantime.","package":"ada-4.3.0.tar.bz2","4":"ada-4.3.0.tar.bz2","src_id":"6461","5":"6461","creation_date":"1164192570","6":"1164192570"},{"0":"1609","vim_version":"7.0","1":"7.0","script_version":"4.3.0","2":"4.3.0","version_comment":"Integrate Brams fixes. The Vim Ada Mode is not part of the standart runtime.","3":"Integrate Brams fixes. The Vim Ada Mode is not part of the standart runtime.","package":"ada-4.3.vba","4":"ada-4.3.vba","src_id":"6435","5":"6435","creation_date":"1163814790","6":"1163814790"},{"0":"1609","vim_version":"7.0","1":"7.0","script_version":"4.2.0","2":"4.2.0","version_comment":"More bug Fixes.","3":"More bug Fixes.","package":"ada-4.2.vba","4":"ada-4.2.vba","src_id":"6388","5":"6388","creation_date":"1162956691","6":"1162956691"},{"0":"1609","vim_version":"7.0","1":"7.0","script_version":"4.1.0","2":"4.1.0","version_comment":"This version contains the latest fixed after suggestions from Bram. It does not provide new functionality but fixes quite a few hidden bugs.\r\n\r\nAda users should also get yourself a new Ctags as the Ctags Ada Mode has been updated as well. We used a snapshot from the Ctags Subversion archive which means the lates Vim-Script fixes are included as well.\r\n\r\nAs allways binary releases are available from the GNU Ada Project: http:\/\/gnuada.sf.net.","3":"This version contains the latest fixed after suggestions from Bram. It does not provide new functionality but fixes quite a few hidden bugs.\r\n\r\nAda users should also get yourself a new Ctags as the Ctags Ada Mode has been updated as well. We used a snapshot from the Ctags Subversion archive which means the lates Vim-Script fixes are included as well.\r\n\r\nAs allways binary releases are available from the GNU Ada Project: http:\/\/gnuada.sf.net.","package":"ada.vba","4":"ada.vba","src_id":"6387","5":"6387","creation_date":"1162897949","6":"1162897949"},{"0":"1609","vim_version":"6.0","1":"6.0","script_version":"3.9","2":"3.9","version_comment":"Fixed Bugs reported by Roman Marchenko. Changes Licence to Vim for runtime integration.","3":"Fixed Bugs reported by Roman Marchenko. Changes Licence to Vim for runtime integration.","package":"ada.vba","4":"ada.vba","src_id":"6272","5":"6272","creation_date":"1160710733","6":"1160710733"},{"0":"1609","vim_version":"7.0","1":"7.0","script_version":"3.8.1","2":"3.8.1","version_comment":"Identical to the last release - only the 3.8 Vimball is dammaged. You should also use the newest Vimball release as older version have problems with the fold markers which Vimball now uses.","3":"Identical to the last release - only the 3.8 Vimball is dammaged. You should also use the newest Vimball release as older version have problems with the fold markers which Vimball now uses.","package":"ada.vba","4":"ada.vba","src_id":"6261","5":"6261","creation_date":"1160218089","6":"1160218089"},{"0":"1609","vim_version":"7.0","1":"7.0","script_version":"3.8","2":"3.8","version_comment":"This version improves folding support for files which have been pretty printed by the GNAT pretty printer.\r\n\r\nNote: This Vimball comes in Unix text format. It will not work if your Vim is not set up to correctly detect unix text files.","3":"This version improves folding support for files which have been pretty printed by the GNAT pretty printer.\r\n\r\nNote: This Vimball comes in Unix text format. It will not work if your Vim is not set up to correctly detect unix text files.","package":"ada.vba","4":"ada.vba","src_id":"6257","5":"6257","creation_date":"1160114112","6":"1160114112"},{"0":"1609","vim_version":"7.0","1":"7.0","script_version":"3.7","2":"3.7","version_comment":"Fixes for the compiler plugin and the session manager.\r\n\r\nAlso available as tar ball from the GNU Ada Project:\r\n\r\nhttp:\/\/sourceforge.net\/project\/showfiles.php?group_id=12974&package_id=191849","3":"Fixes for the compiler plugin and the session manager.\r\n\r\nAlso available as tar ball from the GNU Ada Project:\r\n\r\nhttp:\/\/sourceforge.net\/project\/showfiles.php?group_id=12974&package_id=191849","package":"ada.vba","4":"ada.vba","src_id":"6155","5":"6155","creation_date":"1157851895","6":"1157851895"},{"0":"1609","vim_version":"7.0","1":"7.0","script_version":"3.5","2":"3.5","version_comment":"Significant improvement for GNAT project manager files:\r\n\r\n- Now a vim-session is attached to each project manager file - vim rembers now all files opened for the project.\r\n- If you open only a *.gpr file it automaticly becomes the active project - you can hit <F7> right away.\r\n- support for the gnat pretty printer added.\r\n\r\nIt's almost an IDE now ;-)","3":"Significant improvement for GNAT project manager files:\r\n\r\n- Now a vim-session is attached to each project manager file - vim rembers now all files opened for the project.\r\n- If you open only a *.gpr file it automaticly becomes the active project - you can hit <F7> right away.\r\n- support for the gnat pretty printer added.\r\n\r\nIt's almost an IDE now ;-)","package":"ada.vba","4":"ada.vba","src_id":"6044","5":"6044","creation_date":"1154848085","6":"1154848085"},{"0":"1609","vim_version":"7.0","1":"7.0","script_version":"3.4","2":"3.4","version_comment":"Maintanance Release: Bugfixes, Cleanup, remove dead code and add fold markers to all files. This release should be easier to maintain and extend now.","3":"Maintanance Release: Bugfixes, Cleanup, remove dead code and add fold markers to all files. This release should be easier to maintain and extend now.","package":"ada.vba","4":"ada.vba","src_id":"6039","5":"6039","creation_date":"1154673293","6":"1154673293"},{"0":"1609","vim_version":"6.0","1":"6.0","script_version":"3.3","2":"3.3","version_comment":"This version of the Ada mode improves key-mappings, user defined commands and pull down menus.","3":"This version of the Ada mode improves key-mappings, user defined commands and pull down menus.","package":"ada.vba","4":"ada.vba","src_id":"5990","5":"5990","creation_date":"1153826824","6":"1153826824"},{"0":"1609","vim_version":"7.0","1":"7.0","script_version":"3.2","2":"3.2","version_comment":"This release fixes quite a few bugs. Especially the GNAT compiler support and the help file where redone. This release also adds support for Dec Ada.","3":"This release fixes quite a few bugs. Especially the GNAT compiler support and the help file where redone. This release also adds support for Dec Ada.","package":"ada.vba","4":"ada.vba","src_id":"5978","5":"5978","creation_date":"1153463296","6":"1153463296"},{"0":"1609","vim_version":"7.0","1":"7.0","script_version":"3.0","2":"3.0","version_comment":"Initial upload","3":"Initial upload","package":"ada.vba","4":"ada.vba","src_id":"5959","5":"5959","creation_date":"1153039223","6":"1153039223"}]},"1608":{"script_id":"1608","0":"1608","script_name":"Chrome syntax script","1":"Chrome syntax script","script_type":"syntax","2":"syntax","summary":"Syntax script for RemObjects Software's Chrome compiler","3":"Syntax script for RemObjects Software's Chrome compiler","description":"This is a syntax script for RemObjects Software's Chrome compiler. That is, for those, who don't know, a compiler for the .NET-Framework or Mono-Framework (which should be almost the same, except for the OS). I just wrote it from the chm help file shipped with the compiler. I just used attributes for color terminals because I got the Windows version without gui so I can't use any other attributes. Maybe the script is not compatible to your shell (though an 8 color terminal is a rather rare sight in these days). And I don't know anything about the least vim version (I asumed 6.0 because it is one major version before the today's, I got 6.4 and it works fine.)\r\nI'm not opposed to feedback from users, so don't be afraid to make my POP3 server work. The address is nullplanwichmann@web.de, and the preferred language is german (my mother tongue) because all the spam I get is english, so I can filter easily. Don't worry: A handwritten mail won't see the dephts of my spam directory. At least I think so.","4":"This is a syntax script for RemObjects Software's Chrome compiler. That is, for those, who don't know, a compiler for the .NET-Framework or Mono-Framework (which should be almost the same, except for the OS). I just wrote it from the chm help file shipped with the compiler. I just used attributes for color terminals because I got the Windows version without gui so I can't use any other attributes. Maybe the script is not compatible to your shell (though an 8 color terminal is a rather rare sight in these days). And I don't know anything about the least vim version (I asumed 6.0 because it is one major version before the today's, I got 6.4 and it works fine.)\r\nI'm not opposed to feedback from users, so don't be afraid to make my POP3 server work. The address is nullplanwichmann@web.de, and the preferred language is german (my mother tongue) because all the spam I get is english, so I can filter easily. Don't worry: A handwritten mail won't see the dephts of my spam directory. At least I think so.","install_details":"Just copy (or move, if you don't want to waste that 1 KB of diskspace) the script (chrome.vim) to your $VIMRUNTIME\/syntax directory (replace the foreslash with whatever your OS uses as directory separator). When you want to use it, open a chrome source file (or a new file that intends to be a chrome source file) and execute in your vim box the following command:\r\n  :set syntax=chrome\r\nIf no error occured anything was done right. If one occured you most likely moved the file to the wrong directory, or you have a pre-6 version of vim. In the first case copy again, this time with the right destination. In the second case update your vim. You need to do. really. (Although I heard there were problems with the year 2000 in programs from the sixties (!) I do not think software should last more than ten years on a hard disk without update if there is one available.)","5":"Just copy (or move, if you don't want to waste that 1 KB of diskspace) the script (chrome.vim) to your $VIMRUNTIME\/syntax directory (replace the foreslash with whatever your OS uses as directory separator). When you want to use it, open a chrome source file (or a new file that intends to be a chrome source file) and execute in your vim box the following command:\r\n  :set syntax=chrome\r\nIf no error occured anything was done right. If one occured you most likely moved the file to the wrong directory, or you have a pre-6 version of vim. In the first case copy again, this time with the right destination. In the second case update your vim. You need to do. really. (Although I heard there were problems with the year 2000 in programs from the sixties (!) I do not think software should last more than ten years on a hard disk without update if there is one available.)","first_name":"Markus","6":"Markus","last_name":"Wichmann","7":"Wichmann","releases":[{"0":"1608","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"chrome.tar.gz","4":"chrome.tar.gz","src_id":"5957","5":"5957","creation_date":"1152968495","6":"1152968495"}]},"1607":{"script_id":"1607","0":"1607","script_name":"color_peruse","1":"color_peruse","script_type":"utility","2":"utility","summary":"Peruse, compare, choose color schemes","3":"Peruse, compare, choose color schemes","description":"Peruse, compare, choose color schemes\r\n\r\nWhen the cursor is in the ColorPeruse window:   \r\n<kPlus>      :ColorPeruse 1             (next color)\r\n<kMinus>    :ColorPeruse -1            (prev color)\r\n<kMultiply> :ColorPeruse                 (original color)\r\n<kDivide>   :ColorPeruse 0              (color under cursor)\r\n     =             :call ColorPeruseDel() (remove duplicate lines)\r\n     +             :call ColorPeruseMerge() (append all :set rtp colors to list)\r\n     ?      Help\r\n     :q     quit\r\n \r\n\r\nYou are in vim when in the ColorPeruse window, so you can edit items you \r\ndon't like from the list, or place markers to return to re-view particular colorschemes.\r\nYou can cut\/paste to put favorites or color\/lightness groups together \r\nto compare more closely.\r\nAlso, since it is in vim, you can save the ColorPeruse list to a file, or \r\nload it from a previous perusal list.\r\n\r\n\r\n","4":"Peruse, compare, choose color schemes\r\n\r\nWhen the cursor is in the ColorPeruse window:   \r\n<kPlus>      :ColorPeruse 1             (next color)\r\n<kMinus>    :ColorPeruse -1            (prev color)\r\n<kMultiply> :ColorPeruse                 (original color)\r\n<kDivide>   :ColorPeruse 0              (color under cursor)\r\n     =             :call ColorPeruseDel() (remove duplicate lines)\r\n     +             :call ColorPeruseMerge() (append all :set rtp colors to list)\r\n     ?      Help\r\n     :q     quit\r\n \r\n\r\nYou are in vim when in the ColorPeruse window, so you can edit items you \r\ndon't like from the list, or place markers to return to re-view particular colorschemes.\r\nYou can cut\/paste to put favorites or color\/lightness groups together \r\nto compare more closely.\r\nAlso, since it is in vim, you can save the ColorPeruse list to a file, or \r\nload it from a previous perusal list.\r\n\r\n\r\n","install_details":"copy to ~\/.vim\/plugin\r\n\r\nPut this mapping in .vimrc:\r\n    map <Leader>cp :ColorPeruse<Space>Mylist<CR>:echo g:colors_name<CR>\r\nThen \\cp will start it up.\r\nIf you once create this 'Mylist' file, it is suggested that you move it\r\ninto a directory in vim's runtimepath. Type :set rtp to see this path.\r\nThis 'Mylist' file does not have to exist.\r\nIn such a list, you may have comments beginning with \" which will be ignored,\r\nand you can sort the list in any order you choose.\r\n\r\n\r\n","5":"copy to ~\/.vim\/plugin\r\n\r\nPut this mapping in .vimrc:\r\n    map <Leader>cp :ColorPeruse<Space>Mylist<CR>:echo g:colors_name<CR>\r\nThen \\cp will start it up.\r\nIf you once create this 'Mylist' file, it is suggested that you move it\r\ninto a directory in vim's runtimepath. Type :set rtp to see this path.\r\nThis 'Mylist' file does not have to exist.\r\nIn such a list, you may have comments beginning with \" which will be ignored,\r\nand you can sort the list in any order you choose.\r\n\r\n\r\n","first_name":"Walter","6":"Walter","last_name":"Hutchins","7":"Hutchins","releases":[{"0":"1607","vim_version":"6.0","1":"6.0","script_version":"1.9","2":"1.9","version_comment":"Minor change to handling file path detection of favorite colors list.","3":"Minor change to handling file path detection of favorite colors list.","package":"color_peruse.vim","4":"color_peruse.vim","src_id":"6014","5":"6014","creation_date":"1154323804","6":"1154323804"},{"0":"1607","vim_version":"6.0","1":"6.0","script_version":"1.8","2":"1.8","version_comment":"Improved options for your favorite colors list.","3":"Improved options for your favorite colors list.","package":"color_peruse.vim","4":"color_peruse.vim","src_id":"5992","5":"5992","creation_date":"1153835070","6":"1153835070"},{"0":"1607","vim_version":"6.0","1":"6.0","script_version":"1.6","2":"1.6","version_comment":"Cursor positions to current colorscheme at startup.","3":"Cursor positions to current colorscheme at startup.","package":"color_peruse.vim","4":"color_peruse.vim","src_id":"5981","5":"5981","creation_date":"1153691312","6":"1153691312"},{"0":"1607","vim_version":"6.0","1":"6.0","script_version":"1.5","2":"1.5","version_comment":"Maps keys only in buffer for <kMinus> - Previous color, <kPlus> - Next color, <kMultiply> - Original color, <kDivide> - Color under cursor. Friendlier \"missing g:colors_name\" message.","3":"Maps keys only in buffer for <kMinus> - Previous color, <kPlus> - Next color, <kMultiply> - Original color, <kDivide> - Color under cursor. Friendlier \"missing g:colors_name\" message.","package":"color_peruse.vim","4":"color_peruse.vim","src_id":"5971","5":"5971","creation_date":"1153320274","6":"1153320274"},{"0":"1607","vim_version":"6.0","1":"6.0","script_version":"1.4","2":"1.4","version_comment":"Maps keys only in buffer for <kMinus> - Previous color, <kPlus> - Next color, <kMultiply> - Original color, <kDivide> - Color under cursor.","3":"Maps keys only in buffer for <kMinus> - Previous color, <kPlus> - Next color, <kMultiply> - Original color, <kDivide> - Color under cursor.","package":"color_peruse.vim","4":"color_peruse.vim","src_id":"5968","5":"5968","creation_date":"1153260069","6":"1153260069"},{"0":"1607","vim_version":"6.0","1":"6.0","script_version":"1.1","2":"1.1","version_comment":"You can narrow down the the list to your preferred items. You can also reset to the original colorscheme any time.","3":"You can narrow down the the list to your preferred items. You can also reset to the original colorscheme any time.","package":"color_peruse.vim","4":"color_peruse.vim","src_id":"5955","5":"5955","creation_date":"1152866323","6":"1152866323"},{"0":"1607","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"color_peruse.vim","4":"color_peruse.vim","src_id":"5953","5":"5953","creation_date":"1152807901","6":"1152807901"}]},"1606":{"script_id":"1606","0":"1606","script_name":"HelpWords","1":"HelpWords","script_type":"utility","2":"utility","summary":"search vimhelp for paragraphs containing given words(substrings) in any order","3":"search vimhelp for paragraphs containing given words(substrings) in any order","description":"\" This script searches vimhelp for paragraphs containing\r\n\" given words (substrings), in any order, and non-adjacent.\r\n\" Scripts defines commandHELPWORDS and it's synonym, HW.\r\n\"              Usage: HW word1 word2 ...\r\n\" This command will search vimhelp for paragraphs\r\n\" containing all given words, in any order (and non-adjacent).\r\n\" To proceed to the next match, us :cn command.\r\n\"\r\n\" Example: HW normal count\r\n\" will find all paragraphs that talk about normal-mode counters.\r\n\"\r\n","4":"\" This script searches vimhelp for paragraphs containing\r\n\" given words (substrings), in any order, and non-adjacent.\r\n\" Scripts defines commandHELPWORDS and it's synonym, HW.\r\n\"              Usage: HW word1 word2 ...\r\n\" This command will search vimhelp for paragraphs\r\n\" containing all given words, in any order (and non-adjacent).\r\n\" To proceed to the next match, us :cn command.\r\n\"\r\n\" Example: HW normal count\r\n\" will find all paragraphs that talk about normal-mode counters.\r\n\"\r\n","install_details":"Installation:\r\nDrop the script into your personal plugin directory, the ~\/.vim\/plugin.\r\nIf you don't yet have directory ~\/.vim\/plugin, just create it\r\nwith command\r\n       mkdir -p ~\/.vim\/plugin\r\nRestart vim. That's it.","5":"Installation:\r\nDrop the script into your personal plugin directory, the ~\/.vim\/plugin.\r\nIf you don't yet have directory ~\/.vim\/plugin, just create it\r\nwith command\r\n       mkdir -p ~\/.vim\/plugin\r\nRestart vim. That's it.","first_name":"Yakov","6":"Yakov","last_name":"Lerner","7":"Lerner","releases":[{"0":"1606","vim_version":"6.0","1":"6.0","script_version":"070219","2":"070219","version_comment":"cosmetic changes. Cheksum 1033211557","3":"cosmetic changes. Cheksum 1033211557","package":"HelpWords.vim","4":"HelpWords.vim","src_id":"6760","5":"6760","creation_date":"1171956342","6":"1171956342"},{"0":"1606","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"HelpWords.vim","4":"HelpWords.vim","src_id":"5950","5":"5950","creation_date":"1152778169","6":"1152778169"}]},"1605":{"script_id":"1605","0":"1605","script_name":"gsl.vim","1":"gsl.vim","script_type":"syntax","2":"syntax","summary":"Syntax file for gsl templates","3":"Syntax file for gsl templates","description":"gsl.vim provides syntax highlighting for GSL templates; more information about GSL can be found on iMatix's site, http:\/\/www.imatix.com\/products .","4":"gsl.vim provides syntax highlighting for GSL templates; more information about GSL can be found on iMatix's site, http:\/\/www.imatix.com\/products .","install_details":"Copy the gsl.vim file into your ~\/.vim\/syntax\/ directory, and add the following to your ~\/.vimrc file (usually inside the \"augroup filedetect\" block):\r\n\r\nau! BufRead,BufNewFile *.gsl  setfiletype gsl\r\n\r\nFor details about adding syntax highlighting support for new file types, read the help at  |:h mysyntaxfile<CR>| and |:h new-filetype<CR>| .\r\n","5":"Copy the gsl.vim file into your ~\/.vim\/syntax\/ directory, and add the following to your ~\/.vimrc file (usually inside the \"augroup filedetect\" block):\r\n\r\nau! BufRead,BufNewFile *.gsl  setfiletype gsl\r\n\r\nFor details about adding syntax highlighting support for new file types, read the help at  |:h mysyntaxfile<CR>| and |:h new-filetype<CR>| .\r\n","first_name":"Ronald","6":"Ronald","last_name":"Tschal\u00c3\u00a4r","7":"Tschal\u00c3\u00a4r","releases":[{"0":"1605","vim_version":"6.0","1":"6.0","script_version":"0.2","2":"0.2","version_comment":"Added support for script mode; fixed function highlighting; added other .for keywords.","3":"Added support for script mode; fixed function highlighting; added other .for keywords.","package":"gsl.vim","4":"gsl.vim","src_id":"6241","5":"6241","creation_date":"1159568277","6":"1159568277"},{"0":"1605","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"gsl.vim","4":"gsl.vim","src_id":"5945","5":"5945","creation_date":"1152749580","6":"1152749580"}]},"1604":{"script_id":"1604","0":"1604","script_name":"colornames","1":"colornames","script_type":"utility","2":"utility","summary":"Show named colors \/ cterm colors with hex code and name colorized in a window","3":"Show named colors \/ cterm colors with hex code and name colorized in a window","description":"Show named colors \/ cterm colors with hex code, name, colorized in a window\r\n\r\n Named colors work in gui only - no color in xterm\r\n\r\n cterm\/gui colors work in gui and 256 xterms\r\n\r\ncall Showhexcolornames() - show all, do not clear syntax\r\n\r\ncall Showhexcolornames(b) - show all (background), do not clear syntax\r\n\r\ncall Showhexcolornames(9) - show all after clearing syntax\r\n\r\ncall Showcolornames(n) - show nth 182 named colors or nth cterm colors\r\n                                             do not clear syntax.\r\n                    [n: 1-3, named]\r\n                    [n: 4-5, cterm]\r\n                    [n: 10,11, cterm (hsv sorted)]\r\n                    [n: 12-14 named (hsv sorted)]\r\n                    [n: 20-24 mixed (hsv sorted)]\r\n                    [hsv sorted: black->red->green->blue->purple]\r\n\r\n\r\ncall Showcolornames(9,n) - show nth 182 named colors or nth cterm colors\r\n                                                after clearing syntax.\r\n                    [n: 1-3, named]\r\n                    [n: 4-5, cterm]\r\n                    [n: 10,11, cterm (hsv sorted)]\r\n                    [n: 12-14 named (hsv sorted)]\r\n                    [n: 20-24 mixed (hsv sorted)]\r\n                    [hsv sorted: black->red->green->blue->purple]\r\n\r\n\r\n    n, b, 9 may be combined as in\r\n                            Showhexcolors(9,4,5) - clear\/ show all cterm\r\n                            Showhexcolors(9,1,2,3) - clear\/ show all named\r\n                            Showhexcolors(9,r,4) - clear\/ show 1st cterm\r\n                                                                    group in background blocks\r\n\r\n\r\n    n=0 - all named colors\r\n    n=6 - all cterm colors\r\n    n=7 - all mixed colors (hsv sorted)\r\n    n=15 - all named colors (hsv sorted)\r\n    n=16 - all cterm colors (hsv sorted)\r\n\r\n    n=20 - mixed, hsv sorted, \"blacks to whites\r\n    n=21 - mixed, hsv sorted, \"reds to yellows\r\n    n=22 - mixed, hsv sorted, \"yellows to greens\r\n    n=23 - mixed, hsv sorted, \"blues\r\n    n=24 - mixed, hsv sorted, \"purples\r\n\r\n    r   - same as b (or background, or reverse) \r\n\r\ncall Showhexcolornames(8) - cleanup highlighting added by Showhexcolornames\r\n\r\nvim < 7 only can show 223 simultaneous highlight groups.\r\n        Once that limit is exceeded, the colors will be random until exit.\r\n        Therefore use 1, 2, 3, 4, or 5 (group of) colors in call.\r\n        Also use 9 - clear syntax, since it needs to clear syntax \r\n        to avoid the 223 limit which makes random colors.\r\n\r\nvim 7 does not have max 223 colors problem\r\n\r\nThis script is also used by color_toon.vim for selecting colorscheme colors.\r\n","4":"Show named colors \/ cterm colors with hex code, name, colorized in a window\r\n\r\n Named colors work in gui only - no color in xterm\r\n\r\n cterm\/gui colors work in gui and 256 xterms\r\n\r\ncall Showhexcolornames() - show all, do not clear syntax\r\n\r\ncall Showhexcolornames(b) - show all (background), do not clear syntax\r\n\r\ncall Showhexcolornames(9) - show all after clearing syntax\r\n\r\ncall Showcolornames(n) - show nth 182 named colors or nth cterm colors\r\n                                             do not clear syntax.\r\n                    [n: 1-3, named]\r\n                    [n: 4-5, cterm]\r\n                    [n: 10,11, cterm (hsv sorted)]\r\n                    [n: 12-14 named (hsv sorted)]\r\n                    [n: 20-24 mixed (hsv sorted)]\r\n                    [hsv sorted: black->red->green->blue->purple]\r\n\r\n\r\ncall Showcolornames(9,n) - show nth 182 named colors or nth cterm colors\r\n                                                after clearing syntax.\r\n                    [n: 1-3, named]\r\n                    [n: 4-5, cterm]\r\n                    [n: 10,11, cterm (hsv sorted)]\r\n                    [n: 12-14 named (hsv sorted)]\r\n                    [n: 20-24 mixed (hsv sorted)]\r\n                    [hsv sorted: black->red->green->blue->purple]\r\n\r\n\r\n    n, b, 9 may be combined as in\r\n                            Showhexcolors(9,4,5) - clear\/ show all cterm\r\n                            Showhexcolors(9,1,2,3) - clear\/ show all named\r\n                            Showhexcolors(9,r,4) - clear\/ show 1st cterm\r\n                                                                    group in background blocks\r\n\r\n\r\n    n=0 - all named colors\r\n    n=6 - all cterm colors\r\n    n=7 - all mixed colors (hsv sorted)\r\n    n=15 - all named colors (hsv sorted)\r\n    n=16 - all cterm colors (hsv sorted)\r\n\r\n    n=20 - mixed, hsv sorted, \"blacks to whites\r\n    n=21 - mixed, hsv sorted, \"reds to yellows\r\n    n=22 - mixed, hsv sorted, \"yellows to greens\r\n    n=23 - mixed, hsv sorted, \"blues\r\n    n=24 - mixed, hsv sorted, \"purples\r\n\r\n    r   - same as b (or background, or reverse) \r\n\r\ncall Showhexcolornames(8) - cleanup highlighting added by Showhexcolornames\r\n\r\nvim < 7 only can show 223 simultaneous highlight groups.\r\n        Once that limit is exceeded, the colors will be random until exit.\r\n        Therefore use 1, 2, 3, 4, or 5 (group of) colors in call.\r\n        Also use 9 - clear syntax, since it needs to clear syntax \r\n        to avoid the 223 limit which makes random colors.\r\n\r\nvim 7 does not have max 223 colors problem\r\n\r\nThis script is also used by color_toon.vim for selecting colorscheme colors.\r\n","install_details":"copy to ~\/.vim\/plugin   or $VIMRUNTIME\/plugin\r\n\r\noptionally set up vimrc command:\r\ncommand! -nargs=* Cna call Showhexcolornames(<f-args>)\r\n","5":"copy to ~\/.vim\/plugin   or $VIMRUNTIME\/plugin\r\n\r\noptionally set up vimrc command:\r\ncommand! -nargs=* Cna call Showhexcolornames(<f-args>)\r\n","first_name":"Walter","6":"Walter","last_name":"Hutchins","7":"Hutchins","releases":[{"0":"1604","vim_version":"6.0","1":"6.0","script_version":"1.5","2":"1.5","version_comment":"For vim versions prior to 7, limits color highlighting types added to 184 to avoid excessive messages. ","3":"For vim versions prior to 7, limits color highlighting types added to 184 to avoid excessive messages. ","package":"colornames.vim","4":"colornames.vim","src_id":"5973","5":"5973","creation_date":"1153379480","6":"1153379480"},{"0":"1604","vim_version":"6.0","1":"6.0","script_version":"1.4","2":"1.4","version_comment":"New options for HSV sorted colors: neutral->red->green->blue->purple","3":"New options for HSV sorted colors: neutral->red->green->blue->purple","package":"colornames.vim","4":"colornames.vim","src_id":"5962","5":"5962","creation_date":"1153133453","6":"1153133453"},{"0":"1604","vim_version":"6.0","1":"6.0","script_version":"1.3","2":"1.3","version_comment":"Open horizontal or vertical split window and show selected group(s) of cterm_gui numbered colors, and\/or gui named colors.","3":"Open horizontal or vertical split window and show selected group(s) of cterm_gui numbered colors, and\/or gui named colors.","package":"colornames.vim","4":"colornames.vim","src_id":"5948","5":"5948","creation_date":"1152775172","6":"1152775172"},{"0":"1604","vim_version":"6.0","1":"6.0","script_version":"1.2","2":"1.2","version_comment":"Shows named or cterm colors in foreground lettering or in a background block.","3":"Shows named or cterm colors in foreground lettering or in a background block.","package":"colornames.vim","4":"colornames.vim","src_id":"5940","5":"5940","creation_date":"1152606617","6":"1152606617"},{"0":"1604","vim_version":"6.0","1":"6.0","script_version":"1.1.01","2":"1.1.01","version_comment":"Removed type check of arguments which allows you to set up a command for viewing subsets of named and cterm colors.","3":"Removed type check of arguments which allows you to set up a command for viewing subsets of named and cterm colors.","package":"colornames.vim","4":"colornames.vim","src_id":"5939","5":"5939","creation_date":"1152595727","6":"1152595727"},{"0":"1604","vim_version":"6.0","1":"6.0","script_version":"1.1","2":"1.1","version_comment":"Added cterm colors. Options to view subsets of named colors and\/or cterm colors.","3":"Added cterm colors. Options to view subsets of named colors and\/or cterm colors.","package":"colornames.vim","4":"colornames.vim","src_id":"5937","5":"5937","creation_date":"1152567721","6":"1152567721"},{"0":"1604","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"colornames.vim","4":"colornames.vim","src_id":"5936","5":"5936","creation_date":"1152530528","6":"1152530528"}]},"1603":{"script_id":"1603","0":"1603","script_name":"tcl.vim","1":"tcl.vim","script_type":"syntax","2":"syntax","summary":"tcl syntax file","3":"tcl syntax file","description":"tcl.vim (syntax)\r\n\r\n    An updated and complete syntax coloring scheme for tcl. Uses the 12 syntax rules of tcl as a starting point.\r\n\r\nADDITIONS\/CORRECTIONS:\r\n    \r\n    Line Continues can be optionally highlighted as Warnings.\r\n\r\n    [set set set] does the right thing.\r\n\r\n    [set ^canvas [canvas create ...]] does the right thing.\r\n\r\n    For [list ...], the subsequent expression is lit like a normal command. Also for [uplevel xx ...].\r\n\r\n    The improved interaction of comments with line continuation and braces based on user feedback.\r\n\r\n\r\nFEATURES:\r\n\r\n    Handles a wide variety of escaped expressions correctly.\r\n\r\n    Multi-line comments following a semi-colon.\r\n\r\n    Spell checking (when spell is enabled) for strings and comments.\r\n\r\n    8.5 syntax: apply, chan, dict, lassign, lrepeat, unload, {expand} and {*} and the new math expressions, all the new words.\r\n\r\n    Added error state to line continues that have trailing spaces, these are errors in a tcl script and now they are immediately visible. (thank you Ilya).\r\n\r\n    \"if {0} {}\" multi-line commenting idiom.\r\n\r\n    Smart syntax folding for procs, namespaces, and several itcl constructs - only folds the outer braces\r\n\r\n    Nested parens brackets braces and quotes.\r\n\r\n    Primary commands, secondary commands, and options.\r\n\r\n    Highlights implicit expressions, such as the first group after an 'if' statement, or the second group after a 'for' statement.\r\n\r\n    Colors expressions and math keyworks; but only inside expressions.\r\n\r\n    Easily extended to include other packages. \r\n\r\n    Current Extensions:\r\n        snit (vimscript #1715)\r\n        sqlite (vimscript #1716)\r\n        itcl (vimscript #1765)\r\n        togl (vimscript #1766)\r\n        critcl (vimscript #1775) \r\n\r\n    Highlight options to adjust the level of coloring. (default is most 'colorful').\r\n ","4":"tcl.vim (syntax)\r\n\r\n    An updated and complete syntax coloring scheme for tcl. Uses the 12 syntax rules of tcl as a starting point.\r\n\r\nADDITIONS\/CORRECTIONS:\r\n    \r\n    Line Continues can be optionally highlighted as Warnings.\r\n\r\n    [set set set] does the right thing.\r\n\r\n    [set ^canvas [canvas create ...]] does the right thing.\r\n\r\n    For [list ...], the subsequent expression is lit like a normal command. Also for [uplevel xx ...].\r\n\r\n    The improved interaction of comments with line continuation and braces based on user feedback.\r\n\r\n\r\nFEATURES:\r\n\r\n    Handles a wide variety of escaped expressions correctly.\r\n\r\n    Multi-line comments following a semi-colon.\r\n\r\n    Spell checking (when spell is enabled) for strings and comments.\r\n\r\n    8.5 syntax: apply, chan, dict, lassign, lrepeat, unload, {expand} and {*} and the new math expressions, all the new words.\r\n\r\n    Added error state to line continues that have trailing spaces, these are errors in a tcl script and now they are immediately visible. (thank you Ilya).\r\n\r\n    \"if {0} {}\" multi-line commenting idiom.\r\n\r\n    Smart syntax folding for procs, namespaces, and several itcl constructs - only folds the outer braces\r\n\r\n    Nested parens brackets braces and quotes.\r\n\r\n    Primary commands, secondary commands, and options.\r\n\r\n    Highlights implicit expressions, such as the first group after an 'if' statement, or the second group after a 'for' statement.\r\n\r\n    Colors expressions and math keyworks; but only inside expressions.\r\n\r\n    Easily extended to include other packages. \r\n\r\n    Current Extensions:\r\n        snit (vimscript #1715)\r\n        sqlite (vimscript #1716)\r\n        itcl (vimscript #1765)\r\n        togl (vimscript #1766)\r\n        critcl (vimscript #1775) \r\n\r\n    Highlight options to adjust the level of coloring. (default is most 'colorful').\r\n ","install_details":"place in ~\/.vim\/syntax\/\r\n\r\nNote: This will override the tcl syntax file that is installed with vim. If you require the old file, remove or rename this one.\r\n\r\n","5":"place in ~\/.vim\/syntax\/\r\n\r\nNote: This will override the tcl syntax file that is installed with vim. If you require the old file, remove or rename this one.\r\n\r\n","first_name":"sm","6":"sm","last_name":"smithfield","7":"smithfield","releases":[{"0":"1603","vim_version":"7.0","1":"7.0","script_version":"0.6","2":"0.6","version_comment":"Fixed a long standing issue w\/ quotation. Single quotes inside regular expressions and other similar irregular quoting patterns involving quote or brackets or braces will not disrupt syntax highlighting. ","3":"Fixed a long standing issue w\/ quotation. Single quotes inside regular expressions and other similar irregular quoting patterns involving quote or brackets or braces will not disrupt syntax highlighting. ","package":"tcl.vim","4":"tcl.vim","src_id":"24212","5":"24212","creation_date":"1461891649","6":"1461891649"},{"0":"1603","vim_version":"6.0","1":"6.0","script_version":"0.5.1","2":"0.5.1","version_comment":"additional syntax for tcl 8.5a6","3":"additional syntax for tcl 8.5a6","package":"tcl.vim","4":"tcl.vim","src_id":"7049","5":"7049","creation_date":"1178085907","6":"1178085907"},{"0":"1603","vim_version":"6.0","1":"6.0","script_version":"0.5","2":"0.5","version_comment":"The result of great feedback from M.Lemburg, J.Seal and R.Terry. See Read Me for full list of additions and corrections.","3":"The result of great feedback from M.Lemburg, J.Seal and R.Terry. See Read Me for full list of additions and corrections.","package":"tcl.vim","4":"tcl.vim","src_id":"6732","5":"6732","creation_date":"1171012568","6":"1171012568"},{"0":"1603","vim_version":"6.0","1":"6.0","script_version":"0.4.5","2":"0.4.5","version_comment":"minor changes to fconfigure and canvas keywords","3":"minor changes to fconfigure and canvas keywords","package":"tcl.vim","4":"tcl.vim","src_id":"6715","5":"6715","creation_date":"1170564358","6":"1170564358"},{"0":"1603","vim_version":"6.0","1":"6.0","script_version":"0.4.3","2":"0.4.3","version_comment":"minor corrections. In extensions like snit, namespace qualifiers color the same as their keywords. Also corrected an issue with the ';# comment' pattern.","3":"minor corrections. In extensions like snit, namespace qualifiers color the same as their keywords. Also corrected an issue with the ';# comment' pattern.","package":"tcl.vim","4":"tcl.vim","src_id":"6648","5":"6648","creation_date":"1169594060","6":"1169594060"},{"0":"1603","vim_version":"6.0","1":"6.0","script_version":"0.4","2":"0.4","version_comment":"Improved parsing of the sort of escaped expressions that are common in regexp (and used to kill the syntax coloring). Fixed a script error for vim6 users. See description for all the goodies.","3":"Improved parsing of the sort of escaped expressions that are common in regexp (and used to kill the syntax coloring). Fixed a script error for vim6 users. See description for all the goodies.","package":"tcl.vim","4":"tcl.vim","src_id":"6609","5":"6609","creation_date":"1168549076","6":"1168549076"},{"0":"1603","vim_version":"6.0","1":"6.0","script_version":"0.3","2":"0.3","version_comment":"full 8.5 support. lots of corrections. lots of additions.","3":"full 8.5 support. lots of corrections. lots of additions.","package":"tcl.vim","4":"tcl.vim","src_id":"6443","5":"6443","creation_date":"1163939972","6":"1163939972"},{"0":"1603","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"tcl.vim","4":"tcl.vim","src_id":"5929","5":"5929","creation_date":"1152198516","6":"1152198516"}]},"1602":{"script_id":"1602","0":"1602","script_name":"developer","1":"developer","script_type":"color scheme","2":"color scheme","summary":"clean colorscheme like MSVS 8.0","3":"clean colorscheme like MSVS 8.0","description":"A clean developer colorscheme like MSVS 8.0","4":"A clean developer colorscheme like MSVS 8.0","install_details":"copy latest developer.vim to ~\/.vim\/colors","5":"copy latest developer.vim to ~\/.vim\/colors","first_name":"Jens","6":"Jens","last_name":"Frederich","7":"Frederich","releases":[{"0":"1602","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"developer.vim","4":"developer.vim","src_id":"5924","5":"5924","creation_date":"1152155628","6":"1152155628"}]},"1601":{"script_id":"1601","0":"1601","script_name":"Smooth Scroll","1":"Smooth Scroll","script_type":"utility","2":"utility","summary":"Smooths scrolls the window for various key mappings","3":"Smooths scrolls the window for various key mappings","description":"\" Smooth Scroll\r\n\"\r\n\" Remamps \r\n\"  <C-U>\r\n\"  <C-D>\r\n\"  <C-F>\r\n\"  <C-B>\r\n\"\r\n\" to allow smooth scrolling of the window. I find that quick changes of\r\n\" context don't allow my eyes to follow the action properly.\r\n\"\r\n\" The global variable g:scroll_factor changes the scroll speed.\r\n\"\r\n\"\r\n\" Written by Brad Phelan 2006\r\n\" http:\/\/xtargets.com\r\n","4":"\" Smooth Scroll\r\n\"\r\n\" Remamps \r\n\"  <C-U>\r\n\"  <C-D>\r\n\"  <C-F>\r\n\"  <C-B>\r\n\"\r\n\" to allow smooth scrolling of the window. I find that quick changes of\r\n\" context don't allow my eyes to follow the action properly.\r\n\"\r\n\" The global variable g:scroll_factor changes the scroll speed.\r\n\"\r\n\"\r\n\" Written by Brad Phelan 2006\r\n\" http:\/\/xtargets.com\r\n","install_details":"Drop the script in the plugins directory.","5":"Drop the script in the plugins directory.","first_name":"brad","6":"brad","last_name":"phelan","7":"phelan","releases":[{"0":"1601","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"smooth_scroll.vim","4":"smooth_scroll.vim","src_id":"5923","5":"5923","creation_date":"1152147984","6":"1152147984"}]},"1600":{"script_id":"1600","0":"1600","script_name":"pop11.vim","1":"pop11.vim","script_type":"syntax","2":"syntax","summary":"Syntax highlighting for Pop-11","3":"Syntax highlighting for Pop-11","description":"Basic syntax highlighting for the Pop-11 programming language (http:\/\/www.poplog.org\/) and some common extensions (objectclass and poprulebase).","4":"Basic syntax highlighting for the Pop-11 programming language (http:\/\/www.poplog.org\/) and some common extensions (objectclass and poprulebase).","install_details":"","5":"","first_name":"Neil","6":"Neil","last_name":"Madden","7":"Madden","releases":[{"0":"1600","vim_version":"6.0","1":"6.0","script_version":"1","2":"1","version_comment":"Initial upload","3":"Initial upload","package":"pop11.vim","4":"pop11.vim","src_id":"5919","5":"5919","creation_date":"1152092189","6":"1152092189"}]},"1599":{"script_id":"1599","0":"1599","script_name":"highlight.vim","1":"highlight.vim","script_type":"utility","2":"utility","summary":"Highlight lines or patterns of interest in different colors","3":"Highlight lines or patterns of interest in different colors","description":"   Line mode\r\n     <C-h><C-h>   Highlight current line \r\n     <C-h><C-a>   Advance color for next line highlight\r\n     <C-h><C-r>   Clear last line highlight\r\n\r\n   Pattern mode\r\n     <C-h><C-w>   Highlight word under cursor (whole word match)\r\n     <C-h><C-l>    Highlight all lines having word under cursor (whole word match)\r\n     <C-h><C-f>    Highlight word under cursor (partial word match)\r\n     <C-h><C-k>   Highlight all lines having word under cursor (partial word match)\r\n     <C-h><C-s>   Highlight last search pattern\r\n     <C-h><C-j>    Highlight all lines having last search pattern\r\n     <C-h><C-d>   Clear last pattern highlight \r\n\r\n     <C-h><C-n>   Clear all highlights\r\n\r\n   All above commands work in both normal & insert modes.\r\n   <C-h><C-h> also works in visual mode. (Select desired lines & hit <C-h><C-h>)\r\n\r\n","4":"   Line mode\r\n     <C-h><C-h>   Highlight current line \r\n     <C-h><C-a>   Advance color for next line highlight\r\n     <C-h><C-r>   Clear last line highlight\r\n\r\n   Pattern mode\r\n     <C-h><C-w>   Highlight word under cursor (whole word match)\r\n     <C-h><C-l>    Highlight all lines having word under cursor (whole word match)\r\n     <C-h><C-f>    Highlight word under cursor (partial word match)\r\n     <C-h><C-k>   Highlight all lines having word under cursor (partial word match)\r\n     <C-h><C-s>   Highlight last search pattern\r\n     <C-h><C-j>    Highlight all lines having last search pattern\r\n     <C-h><C-d>   Clear last pattern highlight \r\n\r\n     <C-h><C-n>   Clear all highlights\r\n\r\n   All above commands work in both normal & insert modes.\r\n   <C-h><C-h> also works in visual mode. (Select desired lines & hit <C-h><C-h>)\r\n\r\n","install_details":"Copy highlight.vim to your .vim\/plugin directory\r\n","5":"Copy highlight.vim to your .vim\/plugin directory\r\n","first_name":"Amit","6":"Amit","last_name":"Sethi","7":"Sethi","releases":[{"0":"1599","vim_version":"6.0","1":"6.0","script_version":"1.6","2":"1.6","version_comment":"Changes to make it work with Console Vim (contributed by Min Kyu Jeong (mkjeong@gmail.com))","3":"Changes to make it work with Console Vim (contributed by Min Kyu Jeong (mkjeong@gmail.com))","package":"highlight.vim","4":"highlight.vim","src_id":"15438","5":"15438","creation_date":"1302602797","6":"1302602797"},{"0":"1599","vim_version":"6.0","1":"6.0","script_version":"1.5","2":"1.5","version_comment":"Added new hightlight mode: \r\n\r\n\"     <C-h><C-j>   Highlight all lines having last search pattern ","3":"Added new hightlight mode: \r\n\r\n\"     <C-h><C-j>   Highlight all lines having last search pattern ","package":"highlight.vim","4":"highlight.vim","src_id":"13794","5":"13794","creation_date":"1284019847","6":"1284019847"},{"0":"1599","vim_version":"6.0","1":"6.0","script_version":"1.4","2":"1.4","version_comment":"Changed Pattern modes. These are now as follows - \r\n\r\n\"   Pattern mode\r\n\"     <C-h><C-w>   Highlight word under cursor (whole word match)\r\n\"     <C-h><C-l>   Highlight all lines having word under cursor (whole word match)\r\n\"     <C-h><C-f>   Highlight word under cursor (partial word match)\r\n\"     <C-h><C-k>   Highlight all lines having word under cursor (partial word match)\r\n\"     <C-h><C-s>   Highlight last search pattern\r\n\"     <C-h><C-d>   Clear last pattern highlight\r\n\"\r\n","3":"Changed Pattern modes. These are now as follows - \r\n\r\n\"   Pattern mode\r\n\"     <C-h><C-w>   Highlight word under cursor (whole word match)\r\n\"     <C-h><C-l>   Highlight all lines having word under cursor (whole word match)\r\n\"     <C-h><C-f>   Highlight word under cursor (partial word match)\r\n\"     <C-h><C-k>   Highlight all lines having word under cursor (partial word match)\r\n\"     <C-h><C-s>   Highlight last search pattern\r\n\"     <C-h><C-d>   Clear last pattern highlight\r\n\"\r\n","package":"highlight.vim","4":"highlight.vim","src_id":"11761","5":"11761","creation_date":"1258614777","6":"1258614777"},{"0":"1599","vim_version":"6.0","1":"6.0","script_version":"1.1","2":"1.1","version_comment":"Modified implementation of word highlight to override comments, etc.","3":"Modified implementation of word highlight to override comments, etc.","package":"highlight.vim","4":"highlight.vim","src_id":"5997","5":"5997","creation_date":"1154053473","6":"1154053473"},{"0":"1599","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"highlight.vim","4":"highlight.vim","src_id":"5918","5":"5918","creation_date":"1152071827","6":"1152071827"}]},"1598":{"script_id":"1598","0":"1598","script_name":"yanktmp.vim","1":"yanktmp.vim","script_type":"utility","2":"utility","summary":"enables vim to yank and paste through the multi processes","3":"enables vim to yank and paste through the multi processes","description":" This plugin enables vim to yank and paste through the multi processes.\r\n\r\n If :call YanktmpYank(), yank string write to tmpfile.\r\n And :call YanktmpPaste_p() or YanktmpPaste_P(), paste string from tmpfile.\r\n\r\n Default tmp file is '\/tmp\/vimyanktmp'\r\n If you want to change tmp file.\r\n let g:yanktmp_file = '\/tmp\/example_tmp_file'\r\n\r\n==================== file yanktmp.vimrc ====================\r\nmap <silent> sy :call YanktmpYank()<CR>\r\nmap <silent> sp :call YanktmpPaste_p()<CR>\r\nmap <silent> sP :call YanktmpPaste_P()<CR>\r\n==================== end: yanktmp.vimrc ====================\r\n","4":" This plugin enables vim to yank and paste through the multi processes.\r\n\r\n If :call YanktmpYank(), yank string write to tmpfile.\r\n And :call YanktmpPaste_p() or YanktmpPaste_P(), paste string from tmpfile.\r\n\r\n Default tmp file is '\/tmp\/vimyanktmp'\r\n If you want to change tmp file.\r\n let g:yanktmp_file = '\/tmp\/example_tmp_file'\r\n\r\n==================== file yanktmp.vimrc ====================\r\nmap <silent> sy :call YanktmpYank()<CR>\r\nmap <silent> sp :call YanktmpPaste_p()<CR>\r\nmap <silent> sP :call YanktmpPaste_P()<CR>\r\n==================== end: yanktmp.vimrc ====================\r\n","install_details":"","5":"","first_name":"yuichi","6":"yuichi","last_name":"tateno","7":"tateno","releases":[{"0":"1598","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"yanktmp.vim","4":"yanktmp.vim","src_id":"5917","5":"5917","creation_date":"1152063268","6":"1152063268"}]},"1597":{"script_id":"1597","0":"1597","script_name":"color_toon","1":"color_toon","script_type":"utility","2":"utility","summary":"Colorscheme utility.","3":"Colorscheme utility.","description":"Shows the colors and the cterm\/gui numbers of the colors. Shows the current syntax highlighting of the color scheme.\r\nYou can change the highlighting colors and save a copy\r\nin a 'myjunk.vim' colorscheme.\r\n\r\nUsage: Colortoon\r\n       Colortoon d  - shows 2nd group of 127 cterm_gui colors\r\n       Colortoon j  - sets colors from last myjunk.vim file\r\n       \r\n        (1) First, run Colortoon.\r\n        (2) Get the desired range of colors into the NamedColors window:\r\n              If cc is mapped to Colorchange as in the suggested setup,\r\n              typing cc will type for you the command line:\r\n              Colorchange h 9\r\n              Following 9<Space>, type a number between 0 and 6.\r\n                0 or blank - All the colors (too many for vim < 7)\r\n                1 - 1st group of 182 named colors (only for guifg and guibg)\r\n                2 - 2nd group of 182 named colors (only for guifg and guibg)\r\n                3 - 3rd group of 182 named colors (only for guifg and guibg)\r\n                4 - 1st group of 128 cterm_gui colors\r\n                5 - 2nd group of 127 cterm_gui colors\r\n                6 - All 255 cterm_gui colors (too many for vim < 7)\r\n\r\n                4 or 5 is recommended.\r\n                You may follow the number with a space and the letter r if you\r\n                want to see color blocks instead of colored lettering.\r\n\r\n              Step (2) may be repeated whenever desired.\r\n                \r\n        (3) Position to desired hi group in myjunk window and type :y b\r\n        (4) Position to desired color in NamedColors window and type :y a\r\n        (5) Colormake                 - Set foreground color per registers a,b\r\n            Colormake b               - Set background color per registers a,b\r\n            If you mapped cm to Colormake as in the suggested setup,\r\n            type cm instead.\r\n\r\n         In steps 3 & 4, ':y a' means :y<SPACEBAR>a<RETURN>\r\n                                   or :yank<SPACEBAR>a<RETURN>\r\n                                   or \"ayy\r\n \r\n                               ':y b' means :y<SPACEBAR>b<RETURN>\r\n                                   or :yank<SPACEBAR>b<RETURN>\r\n                                   or \"byy\r\n                         \r\n                        If you consistently(!) reverse a and b, it still works.\r\n\r\n\r\nYou can also try editing the line in the myjunk window, then copy and \r\npaste that line to the command line which will also update highlighting.\r\nYou can copy the line with  yy\r\n                 and paste it with  :@\"\r\n","4":"Shows the colors and the cterm\/gui numbers of the colors. Shows the current syntax highlighting of the color scheme.\r\nYou can change the highlighting colors and save a copy\r\nin a 'myjunk.vim' colorscheme.\r\n\r\nUsage: Colortoon\r\n       Colortoon d  - shows 2nd group of 127 cterm_gui colors\r\n       Colortoon j  - sets colors from last myjunk.vim file\r\n       \r\n        (1) First, run Colortoon.\r\n        (2) Get the desired range of colors into the NamedColors window:\r\n              If cc is mapped to Colorchange as in the suggested setup,\r\n              typing cc will type for you the command line:\r\n              Colorchange h 9\r\n              Following 9<Space>, type a number between 0 and 6.\r\n                0 or blank - All the colors (too many for vim < 7)\r\n                1 - 1st group of 182 named colors (only for guifg and guibg)\r\n                2 - 2nd group of 182 named colors (only for guifg and guibg)\r\n                3 - 3rd group of 182 named colors (only for guifg and guibg)\r\n                4 - 1st group of 128 cterm_gui colors\r\n                5 - 2nd group of 127 cterm_gui colors\r\n                6 - All 255 cterm_gui colors (too many for vim < 7)\r\n\r\n                4 or 5 is recommended.\r\n                You may follow the number with a space and the letter r if you\r\n                want to see color blocks instead of colored lettering.\r\n\r\n              Step (2) may be repeated whenever desired.\r\n                \r\n        (3) Position to desired hi group in myjunk window and type :y b\r\n        (4) Position to desired color in NamedColors window and type :y a\r\n        (5) Colormake                 - Set foreground color per registers a,b\r\n            Colormake b               - Set background color per registers a,b\r\n            If you mapped cm to Colormake as in the suggested setup,\r\n            type cm instead.\r\n\r\n         In steps 3 & 4, ':y a' means :y<SPACEBAR>a<RETURN>\r\n                                   or :yank<SPACEBAR>a<RETURN>\r\n                                   or \"ayy\r\n \r\n                               ':y b' means :y<SPACEBAR>b<RETURN>\r\n                                   or :yank<SPACEBAR>b<RETURN>\r\n                                   or \"byy\r\n                         \r\n                        If you consistently(!) reverse a and b, it still works.\r\n\r\n\r\nYou can also try editing the line in the myjunk window, then copy and \r\npaste that line to the command line which will also update highlighting.\r\nYou can copy the line with  yy\r\n                 and paste it with  :@\"\r\n","install_details":" Requires:     colornames.vim (v1.3) plugin (included in version 1.4.02 zip)\r\n                    \r\n Note: A new version of colornames.vim (v1.5) is available with\r\n          new options for HSV sorted colors: neutral->red->green->blue->purple\r\n\r\n Setup:   Copy color_toon.vim to ~\/.vim\/plugin\/\r\n               Copy colornames.vim to ~\/.vim\/plugin\/\r\n               Recommend adding to vimrc the mappings:\r\n                  map cn  :Colortoon<Space>\r\n                  map cm  :Colormake<Space>\r\n                  map cc  :Colorchange h 9<Space>\r\n\r\n               Windows - copy to $VIMRUNTIME\/plugin\r\n                       - adjust myjunk | adjust plugin location if necessary.","5":" Requires:     colornames.vim (v1.3) plugin (included in version 1.4.02 zip)\r\n                    \r\n Note: A new version of colornames.vim (v1.5) is available with\r\n          new options for HSV sorted colors: neutral->red->green->blue->purple\r\n\r\n Setup:   Copy color_toon.vim to ~\/.vim\/plugin\/\r\n               Copy colornames.vim to ~\/.vim\/plugin\/\r\n               Recommend adding to vimrc the mappings:\r\n                  map cn  :Colortoon<Space>\r\n                  map cm  :Colormake<Space>\r\n                  map cc  :Colorchange h 9<Space>\r\n\r\n               Windows - copy to $VIMRUNTIME\/plugin\r\n                       - adjust myjunk | adjust plugin location if necessary.","first_name":"Walter","6":"Walter","last_name":"Hutchins","7":"Hutchins","releases":[{"0":"1597","vim_version":"6.0","1":"6.0","script_version":"1.4.02","2":"1.4.02","version_comment":"More colors (cterm_gui numbered and gui named). Better performance and more flexibility. Requires colornames.vim which is included in the zip. Fixed windows problems in version 1.4 and 1.4.01.","3":"More colors (cterm_gui numbered and gui named). Better performance and more flexibility. Requires colornames.vim which is included in the zip. Fixed windows problems in version 1.4 and 1.4.01.","package":"color_toon.zip","4":"color_toon.zip","src_id":"5952","5":"5952","creation_date":"1152784594","6":"1152784594"},{"0":"1597","vim_version":"6.0","1":"6.0","script_version":"1.4.01","2":"1.4.01","version_comment":"More colors (cterm_gui numbered and gui named). Better performance and more flexibility. Requires colornames.vim which is included in the zip. Fixed Windows problem in version 1.4.","3":"More colors (cterm_gui numbered and gui named). Better performance and more flexibility. Requires colornames.vim which is included in the zip. Fixed Windows problem in version 1.4.","package":"color_toon.zip","4":"color_toon.zip","src_id":"5951","5":"5951","creation_date":"1152779554","6":"1152779554"},{"0":"1597","vim_version":"6.0","1":"6.0","script_version":"1.4","2":"1.4","version_comment":"More colors (cterm_gui numbered and gui named). Better performance and more flexibility. Requires colornames.vim which is included in the zip.","3":"More colors (cterm_gui numbered and gui named). Better performance and more flexibility. Requires colornames.vim which is included in the zip.","package":"color_toon.zip","4":"color_toon.zip","src_id":"5949","5":"5949","creation_date":"1152775590","6":"1152775590"},{"0":"1597","vim_version":"6.0","1":"6.0","script_version":"1.3.01","2":"1.3.01","version_comment":"Correction to capture the color scheme intro for Windows.","3":"Correction to capture the color scheme intro for Windows.","package":"color_toon.vim","4":"color_toon.vim","src_id":"5935","5":"5935","creation_date":"1152391610","6":"1152391610"},{"0":"1597","vim_version":"6.0","1":"6.0","script_version":"1.3","2":"1.3","version_comment":"Improved the Colormake function. Reversed default to not input myjunk. Strips \"font=\" out of highlighting to be friendlier to xterms.","3":"Improved the Colormake function. Reversed default to not input myjunk. Strips \"font=\" out of highlighting to be friendlier to xterms.","package":"color_toon.vim","4":"color_toon.vim","src_id":"5933","5":"5933","creation_date":"1152280755","6":"1152280755"},{"0":"1597","vim_version":"6.0","1":"6.0","script_version":"1.2","2":"1.2","version_comment":"New command Colormake makes changing colors easy.","3":"New command Colormake makes changing colors easy.","package":"color_toon.vim","4":"color_toon.vim","src_id":"5925","5":"5925","creation_date":"1152184194","6":"1152184194"},{"0":"1597","vim_version":"6.0","1":"6.0","script_version":"1.1","2":"1.1","version_comment":"More fun. Works better for vim7. Syntax highlighting shows up in a more logical place. New options.","3":"More fun. Works better for vim7. Syntax highlighting shows up in a more logical place. New options.","package":"color_toon.vim","4":"color_toon.vim","src_id":"5922","5":"5922","creation_date":"1152118165","6":"1152118165"},{"0":"1597","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"color_toon.zip","4":"color_toon.zip","src_id":"5915","5":"5915","creation_date":"1152015662","6":"1152015662"}]},"1596":{"script_id":"1596","0":"1596","script_name":"blacklight","1":"blacklight","script_type":"color scheme","2":"color scheme","summary":"Dark colorscheme. Looks like a black light.","3":"Dark colorscheme. Looks like a black light.","description":"Works in gui and 256 color xterm.","4":"Works in gui and 256 color xterm.","install_details":"copy to ~\/.vim\/colors\/","5":"copy to ~\/.vim\/colors\/","first_name":"Walter","6":"Walter","last_name":"Hutchins","7":"Hutchins","releases":[{"0":"1596","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"blacklight.vim","4":"blacklight.vim","src_id":"5914","5":"5914","creation_date":"1152014924","6":"1152014924"}]},"1595":{"script_id":"1595","0":"1595","script_name":"warsow.vim","1":"warsow.vim","script_type":"syntax","2":"syntax","summary":"Syntax script for WarSoW player config and HUD files","3":"Syntax script for WarSoW player config and HUD files","description":"This is a syntax script for WarSoW game config and hud script files. It features all commands, variables and keywords for player config files and variables, constants and operators for HUD scripting files.\r\n\r\nChangelog:\r\n1.0.21 Release (2.01.2007)\r\n- update for War\u00c2\u00a7oW 0.21 version changes\r\n- added dynvars\r\n\r\nVisit project page on:\r\nhttp:\/\/www.haze.ehost.pl\/spoonman\/index.php5?p=8\r\n\r\nExamples (using dusk.vim colorscheme):\r\nhttp:\/\/www.haze.ehost.pl\/spoonman\/images\/warsow-vim1.png\r\nhttp:\/\/www.haze.ehost.pl\/spoonman\/images\/warsow-vim2.png\r\n\r\nYour suggestions are very welcome. I plan to maintain and update this file as WarSoW development continues.","4":"This is a syntax script for WarSoW game config and hud script files. It features all commands, variables and keywords for player config files and variables, constants and operators for HUD scripting files.\r\n\r\nChangelog:\r\n1.0.21 Release (2.01.2007)\r\n- update for War\u00c2\u00a7oW 0.21 version changes\r\n- added dynvars\r\n\r\nVisit project page on:\r\nhttp:\/\/www.haze.ehost.pl\/spoonman\/index.php5?p=8\r\n\r\nExamples (using dusk.vim colorscheme):\r\nhttp:\/\/www.haze.ehost.pl\/spoonman\/images\/warsow-vim1.png\r\nhttp:\/\/www.haze.ehost.pl\/spoonman\/images\/warsow-vim2.png\r\n\r\nYour suggestions are very welcome. I plan to maintain and update this file as WarSoW development continues.","install_details":"Download and unzip into your $HOME\/syntax\/ directory.\r\n:set syntax=warsow","5":"Download and unzip into your $HOME\/syntax\/ directory.\r\n:set syntax=warsow","first_name":"Tomasz","6":"Tomasz","last_name":"Kalkosinski","7":"Kalkosinski","releases":[{"0":"1595","vim_version":"6.0","1":"6.0","script_version":"1.0.21","2":"1.0.21","version_comment":"1.0.21 Release (2.01.2007)\r\n- update for War\u00c2\u00a7oW 0.21 version changes\r\n- added dynvars\r\n","3":"1.0.21 Release (2.01.2007)\r\n- update for War\u00c2\u00a7oW 0.21 version changes\r\n- added dynvars\r\n","package":"warsow-vim-syntax-1.0.21.zip","4":"warsow-vim-syntax-1.0.21.zip","src_id":"6573","5":"6573","creation_date":"1167743623","6":"1167743623"},{"0":"1595","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"warsow.vim","4":"warsow.vim","src_id":"5903","5":"5903","creation_date":"1151680623","6":"1151680623"}]},"1594":{"script_id":"1594","0":"1594","script_name":"showhide.vim","1":"showhide.vim","script_type":"utility","2":"utility","summary":"Show or Hide lines by folding based on pattern","3":"Show or Hide lines by folding based on pattern","description":"A simple script to quickly show\/hide lines of interest. Useful for viewing log files or other huge files in general.\r\n\r\n Uasge:\r\n     zs    Show all lines containing word under cursor\r\n     zh    Hide all lines containing word under cursor\r\n\r\n     :SHOW word pattern ...\r\n           Show lines containing either word or pattern\r\n     \r\n     :HIDE word pattern ...\r\n           Hide lines containing either word or pattern\r\n\r\n           -- pattern can be any regular expression --\r\n\r\n  See \":h fold\" for commands related to folds, e.g.,\r\n     zn\t   Open all folds\r\n","4":"A simple script to quickly show\/hide lines of interest. Useful for viewing log files or other huge files in general.\r\n\r\n Uasge:\r\n     zs    Show all lines containing word under cursor\r\n     zh    Hide all lines containing word under cursor\r\n\r\n     :SHOW word pattern ...\r\n           Show lines containing either word or pattern\r\n     \r\n     :HIDE word pattern ...\r\n           Hide lines containing either word or pattern\r\n\r\n           -- pattern can be any regular expression --\r\n\r\n  See \":h fold\" for commands related to folds, e.g.,\r\n     zn\t   Open all folds\r\n","install_details":"Copy showhide.vim to your .vim\/plugin directory","5":"Copy showhide.vim to your .vim\/plugin directory","first_name":"Amit","6":"Amit","last_name":"Sethi","7":"Sethi","releases":[{"0":"1594","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"showhide.vim","4":"showhide.vim","src_id":"5899","5":"5899","creation_date":"1151622793","6":"1151622793"}]},"1593":{"script_id":"1593","0":"1593","script_name":"comment.vim","1":"comment.vim","script_type":"utility","2":"utility","summary":"Comment-Uncomment Single\/Multiple Files -added Tex file format","3":"Comment-Uncomment Single\/Multiple Files -added Tex file format","description":"Global Plugin to comment and un-comment different\r\nsource files in both normal and visual <Shift-V> mode\r\n\r\nRefer to Jasmeet Singh Anand\\'s Original \\\"comment.vim\\\"\r\nEntire script is copied and I, Keyur Joshi have just added support for two more file formats \\\".tex\\\" and \\\".bib\\\"","4":"Global Plugin to comment and un-comment different\r\nsource files in both normal and visual <Shift-V> mode\r\n\r\nRefer to Jasmeet Singh Anand\\'s Original \\\"comment.vim\\\"\r\nEntire script is copied and I, Keyur Joshi have just added support for two more file formats \\\".tex\\\" and \\\".bib\\\"","install_details":"For VIM 6 -\r\n               Stick this file in your ~\/.vim\/plugin directory or\r\n               in some other \\'plugin\\' directory that is in your runtime path\r\n               For VIM 5 -\r\n               Stick this file somewhere and \\'source <path>\/comments.vim\\' it from\r\n              your ~\/.vimrc file\r\n","5":"For VIM 6 -\r\n               Stick this file in your ~\/.vim\/plugin directory or\r\n               in some other \\'plugin\\' directory that is in your runtime path\r\n               For VIM 5 -\r\n               Stick this file somewhere and \\'source <path>\/comments.vim\\' it from\r\n              your ~\/.vimrc file\r\n","first_name":"Keyur","6":"Keyur","last_name":"Joshi","7":"Joshi","releases":[{"0":"1593","vim_version":"6.0","1":"6.0","script_version":"2.2","2":"2.2","version_comment":"Initial upload","3":"Initial upload","package":"comments.vim","4":"comments.vim","src_id":"5898","5":"5898","creation_date":"1151599836","6":"1151599836"}]},"1592":{"script_id":"1592","0":"1592","script_name":"crestore.vim","1":"crestore.vim","script_type":"utility","2":"utility","summary":"Save (restore afterwards) the current file before using a quickfix command.","3":"Save (restore afterwards) the current file before using a quickfix command.","description":"The script \"crestore.vim\" provide the command \"Crestore\". Before using a quickfix command the script\r\nwill save the current file and cursor position. Using \"Crestore\" will restore the file (and cursor position) used before.\r\n \r\nUsage:\r\n\r\n1. Run a quickfix command: vimgrep, make etc.\r\n2. Jump around in the list, fix errors....\r\n3. Type \"Crestore\" to go back to the file you used before. Quickfix window will be closed. ","4":"The script \"crestore.vim\" provide the command \"Crestore\". Before using a quickfix command the script\r\nwill save the current file and cursor position. Using \"Crestore\" will restore the file (and cursor position) used before.\r\n \r\nUsage:\r\n\r\n1. Run a quickfix command: vimgrep, make etc.\r\n2. Jump around in the list, fix errors....\r\n3. Type \"Crestore\" to go back to the file you used before. Quickfix window will be closed. ","install_details":"Drop crestore.vim into your plugin directory","5":"Drop crestore.vim into your plugin directory","first_name":"Jochen","6":"Jochen","last_name":"Baier","7":"Baier","releases":[{"0":"1592","vim_version":"7.0","1":"7.0","script_version":"0.01","2":"0.01","version_comment":"Initial upload","3":"Initial upload","package":"crestore.vim","4":"crestore.vim","src_id":"5896","5":"5896","creation_date":"1151590040","6":"1151590040"}]},"1591":{"script_id":"1591","0":"1591","script_name":"octave.vim","1":"octave.vim","script_type":"syntax","2":"syntax","summary":"Another syntax highlighting file for octave","3":"Another syntax highlighting file for octave","description":"This script is based in the matlab syntax file, however it adds a few significant features:\r\n\r\n* Supports the octave syntax, including things like endwhile, the # comment, the strings delimited by ' and \", etc.\r\n\r\n* Highlights the predefined functions like normal_cdf, sqrt, etc...\r\n\r\n* Highlights any functions defined in the file being editted, for example if you are editting a file containing something like this:\r\n\r\nfunction my_function()\r\n  ...\r\nendfunction\r\n\r\nit will highlight appearances of my_function in the current file.","4":"This script is based in the matlab syntax file, however it adds a few significant features:\r\n\r\n* Supports the octave syntax, including things like endwhile, the # comment, the strings delimited by ' and \", etc.\r\n\r\n* Highlights the predefined functions like normal_cdf, sqrt, etc...\r\n\r\n* Highlights any functions defined in the file being editted, for example if you are editting a file containing something like this:\r\n\r\nfunction my_function()\r\n  ...\r\nendfunction\r\n\r\nit will highlight appearances of my_function in the current file.","install_details":"The installation procedure is:\r\n\r\n1) mkdir -p ~\/.vim\/syntax\r\n2) Copy octave.vim to ~\/.vim\/syntax\/\r\n3) Then add the following lines to your ~\/.vimrc\r\n\r\n\" Copy from here\r\n\r\n\" Octave Syntax\r\naugroup filetypedetect\r\n  au! BufRead,BufNewFile *.m,*.oct setfiletype octave\r\naugroup END\r\n\r\n\" to here.\r\n","5":"The installation procedure is:\r\n\r\n1) mkdir -p ~\/.vim\/syntax\r\n2) Copy octave.vim to ~\/.vim\/syntax\/\r\n3) Then add the following lines to your ~\/.vimrc\r\n\r\n\" Copy from here\r\n\r\n\" Octave Syntax\r\naugroup filetypedetect\r\n  au! BufRead,BufNewFile *.m,*.oct setfiletype octave\r\naugroup END\r\n\r\n\" to here.\r\n","first_name":"Francisco","6":"Francisco","last_name":"Castro","7":"Castro","releases":[{"0":"1591","vim_version":"7.0","1":"7.0","script_version":"1.2","2":"1.2","version_comment":"The version 1.1 couldn't handle a trailing backslash when defing a function. Now it's fixed.","3":"The version 1.1 couldn't handle a trailing backslash when defing a function. Now it's fixed.","package":"octave.vim","4":"octave.vim","src_id":"7322","5":"7322","creation_date":"1183597747","6":"1183597747"},{"0":"1591","vim_version":"7.0","1":"7.0","script_version":"1.1","2":"1.1","version_comment":"It fixes a typo and minor changes. Also it's tested with vim7 and works.","3":"It fixes a typo and minor changes. Also it's tested with vim7 and works.","package":"octave.vim","4":"octave.vim","src_id":"6369","5":"6369","creation_date":"1162500081","6":"1162500081"}]},"1590":{"script_id":"1590","0":"1590","script_name":"unimpaired.vim","1":"unimpaired.vim","script_type":"utility","2":"utility","summary":"Pairs of handy bracket mappings","3":"Pairs of handy bracket mappings","description":"Much of unimpaired.vim was extracted from my vimrc when I noticed a pattern: complementary pairs of mappings.  They fall into three categories.\r\n\r\nThere are mappings which are simply short normal mode aliases for commonly used ex commands. ]q is :cnext. [q is :cprevious. ]a is :next. [b is :bprevious.  See the documentation for the full set of 16 mappings and mnemonics.  All of them take a count.\r\n\r\nThere are linewise mappings. [<Space> and ]<Space> add newlines before and after the cursor line. [e and ]e exchange the current line with the one above or below it.\r\n\r\nThere are mappings for toggling options. [os, ]os, and =os perform :set spell, :set nospell, and :set invspell, respectively.  There's also l (list), n (number), w (wrap), x (cursorline cursorcolumn), and several others, plus mappings to help alleviate the set paste dance.  Consult the documentation.\r\n\r\nThere are mappings for encoding and decoding. [x and ]x encode and decode XML (and HTML). [u and ]u encode and decode URLs. [y and ]y do C String style escaping.\r\n\r\nOh, and there's also [f and ]f to go to the previous\/next file in the directory, and [n and ]n to go between SCM conflict markers.\r\n\r\nhttp:\/\/github.com\/tpope\/vim-unimpaired","4":"Much of unimpaired.vim was extracted from my vimrc when I noticed a pattern: complementary pairs of mappings.  They fall into three categories.\r\n\r\nThere are mappings which are simply short normal mode aliases for commonly used ex commands. ]q is :cnext. [q is :cprevious. ]a is :next. [b is :bprevious.  See the documentation for the full set of 16 mappings and mnemonics.  All of them take a count.\r\n\r\nThere are linewise mappings. [<Space> and ]<Space> add newlines before and after the cursor line. [e and ]e exchange the current line with the one above or below it.\r\n\r\nThere are mappings for toggling options. [os, ]os, and =os perform :set spell, :set nospell, and :set invspell, respectively.  There's also l (list), n (number), w (wrap), x (cursorline cursorcolumn), and several others, plus mappings to help alleviate the set paste dance.  Consult the documentation.\r\n\r\nThere are mappings for encoding and decoding. [x and ]x encode and decode XML (and HTML). [u and ]u encode and decode URLs. [y and ]y do C String style escaping.\r\n\r\nOh, and there's also [f and ]f to go to the previous\/next file in the directory, and [n and ]n to go between SCM conflict markers.\r\n\r\nhttp:\/\/github.com\/tpope\/vim-unimpaired","install_details":"Unzip in ~\/.vim (~\\vimfiles on Windows). Use :helptags ~\/.vim\/doc to enable :help.","5":"Unzip in ~\/.vim (~\\vimfiles on Windows). Use :helptags ~\/.vim\/doc to enable :help.","first_name":"Tim","6":"Tim","last_name":"Pope","7":"Pope","releases":[{"0":"1590","vim_version":"7.0","1":"7.0","script_version":"2.1","2":"2.1","version_comment":"Provide <Plug> maps for all built-ins.\r\nNever override user maps with Unimpaired maps.\r\nCall :colder\/:cnewer when invoking [f\/]f in quickfix window.\r\nProvide 'colorcolumn' option maps on [ot\/]ot\/yot.\r\nSupport [n\/]n in visual mode.\r\nHandle count on [A\/]A\/[B\/]B.\r\nMake URL encoding Unicode safe.\r\nXML encode ' (apostrophe) as '.","3":"Provide <Plug> maps for all built-ins.\r\nNever override user maps with Unimpaired maps.\r\nCall :colder\/:cnewer when invoking [f\/]f in quickfix window.\r\nProvide 'colorcolumn' option maps on [ot\/]ot\/yot.\r\nSupport [n\/]n in visual mode.\r\nHandle count on [A\/]A\/[B\/]B.\r\nMake URL encoding Unicode safe.\r\nXML encode ' (apostrophe) as '.","package":"unimpaired.zip","4":"unimpaired.zip","src_id":"28062","5":"28062","creation_date":"1653623580","6":"1653623580"},{"0":"1590","vim_version":"7.0","1":"7.0","script_version":"2.0","2":"2.0","version_comment":"Drop deprecated [o and ]o aliases for [f and ]f.\r\nMap [o, ]o, and yo to enable, disable, and toggle options.\r\nMap [op, ]op, and yop to enable paste mode for one insert.\r\nMap [p, ]p, [P, and ]P to force line-wise paste.\r\nMap <p, <P, >p, >P, =p, and =P as re-indenting paste maps.\r\nMap [<C-T> and ]<C-T> as :ptprevious and :ptnext.\r\nBug fixes.","3":"Drop deprecated [o and ]o aliases for [f and ]f.\r\nMap [o, ]o, and yo to enable, disable, and toggle options.\r\nMap [op, ]op, and yop to enable paste mode for one insert.\r\nMap [p, ]p, [P, and ]P to force line-wise paste.\r\nMap <p, <P, >p, >P, =p, and =P as re-indenting paste maps.\r\nMap [<C-T> and ]<C-T> as :ptprevious and :ptnext.\r\nBug fixes.","package":"unimpaired.zip","4":"unimpaired.zip","src_id":"26151","5":"26151","creation_date":"1532668569","6":"1532668569"},{"0":"1590","vim_version":"7.0","1":"7.0","script_version":"1.2","2":"1.2","version_comment":"Add repeat.vim support.\r\nAdd [t and ]t for :tprev and :tnext.\r\nAdd [n and ]n for jumping between conflict markers.\r\nAdd [<C-Q> and ]<C-Q> for :cpfile and :cnfile.\r\nAdd [<C-L> and ]<C-L> for :lpfile and :lnfile.\r\nDeprecate [o and ]o in favor of new maps [f and ]f.\r\nImprove robustness of [f and ]f.\r\nImprove robustness of [e and ]e.\r\nFix unescaping of \"\\a\" and \"\\$\".\r\nWork around `unnamedplus' in clipboard.\r\nExpose API for custom encoding algorithms.","3":"Add repeat.vim support.\r\nAdd [t and ]t for :tprev and :tnext.\r\nAdd [n and ]n for jumping between conflict markers.\r\nAdd [<C-Q> and ]<C-Q> for :cpfile and :cnfile.\r\nAdd [<C-L> and ]<C-L> for :lpfile and :lnfile.\r\nDeprecate [o and ]o in favor of new maps [f and ]f.\r\nImprove robustness of [f and ]f.\r\nImprove robustness of [e and ]e.\r\nFix unescaping of \"\\a\" and \"\\$\".\r\nWork around `unnamedplus' in clipboard.\r\nExpose API for custom encoding algorithms.","package":"unimpaired.zip","4":"unimpaired.zip","src_id":"19374","5":"19374","creation_date":"1358184881","6":"1358184881"},{"0":"1590","vim_version":"7.0","1":"7.0","script_version":"1.1","2":"1.1","version_comment":"Add <Plug> aliases for all mappings.\r\nSkip swap files with ]o and [o.\r\nAccept a count with [e and ]e.","3":"Add <Plug> aliases for all mappings.\r\nSkip swap files with ]o and [o.\r\nAccept a count with [e and ]e.","package":"unimpaired.zip","4":"unimpaired.zip","src_id":"12570","5":"12570","creation_date":"1267924068","6":"1267924068"},{"0":"1590","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"unimpaired.zip","4":"unimpaired.zip","src_id":"12237","5":"12237","creation_date":"1264800564","6":"1264800564"}]},"1589":{"script_id":"1589","0":"1589","script_name":"skk.vim","1":"skk.vim","script_type":"utility","2":"utility","summary":"Japanese SKK","3":"Japanese SKK","description":"This script is an implementation of the Japanese SKK (Simple Kana to Kanji\r\nconversion program).\r\n\r\nThis script is no longer maintained here.\r\nYou can get newer versions of skk.vim from vimscript #3118.","4":"This script is an implementation of the Japanese SKK (Simple Kana to Kanji\r\nconversion program).\r\n\r\nThis script is no longer maintained here.\r\nYou can get newer versions of skk.vim from vimscript #3118.","install_details":"REQUIREMENT: SKK-JISYO.[SML]\r\nSet two global variables if necessary.\r\n  let skk_jisyo = \"path to private dictionary\"\r\n  let skk_large_jisyo = \"path to SKK-JISYO.[SML]\"\r\n:so skk.vim or put this script into your plugin directory.\r\nTo start SKK-mode, press <C-j> in Insert-mode or Commandline-mode.\r\n","5":"REQUIREMENT: SKK-JISYO.[SML]\r\nSet two global variables if necessary.\r\n  let skk_jisyo = \"path to private dictionary\"\r\n  let skk_large_jisyo = \"path to SKK-JISYO.[SML]\"\r\n:so skk.vim or put this script into your plugin directory.\r\nTo start SKK-mode, press <C-j> in Insert-mode or Commandline-mode.\r\n","first_name":"Noriaki","6":"Noriaki","last_name":"Yagi","7":"Yagi","releases":[{"0":"1589","vim_version":"6.0","1":"6.0","script_version":"0.22","2":"0.22","version_comment":"Fixed the flicker of the commandline when editing in Insert-mode.","3":"Fixed the flicker of the commandline when editing in Insert-mode.","package":"skk.zip","4":"skk.zip","src_id":"6283","5":"6283","creation_date":"1160950152","6":"1160950152"},{"0":"1589","vim_version":"6.0","1":"6.0","script_version":"0.21","2":"0.21","version_comment":"Initial upload","3":"Initial upload","package":"skk.zip","4":"skk.zip","src_id":"5891","5":"5891","creation_date":"1151521436","6":"1151521436"}]},"1588":{"script_id":"1588","0":"1588","script_name":"ShowFunc","1":"ShowFunc","script_type":"utility","2":"utility","summary":"Show\/Jump to Function\/Class name","3":"Show\/Jump to Function\/Class name","description":"This small utility define commands to display the type\/function name the cursor in. You can also jump to the closest function\/type name in scope.\r\n\r\nCommand:\r\n    SFunc -- Show type\/function name\r\n    JFunc  -- Jump to closest type\/function name in scope\r\n\r\nshortcut:\r\n     ,f    -- call SFunc\r\n     \\f    -- call JFunc\r\n\r\nIt doesn't relies on ctags file, but it use the syntax file in vim 7.0. It should work for C#\/Java\/C++, but it has best support for C#. In addition to function, it can also recognize property\/event in C#.\r\n\r\n","4":"This small utility define commands to display the type\/function name the cursor in. You can also jump to the closest function\/type name in scope.\r\n\r\nCommand:\r\n    SFunc -- Show type\/function name\r\n    JFunc  -- Jump to closest type\/function name in scope\r\n\r\nshortcut:\r\n     ,f    -- call SFunc\r\n     \\f    -- call JFunc\r\n\r\nIt doesn't relies on ctags file, but it use the syntax file in vim 7.0. It should work for C#\/Java\/C++, but it has best support for C#. In addition to function, it can also recognize property\/event in C#.\r\n\r\n","install_details":"put the script into plugin direcotry","5":"put the script into plugin direcotry","first_name":"Yanbiao","6":"Yanbiao","last_name":"Zhao","7":"Zhao","releases":[{"0":"1588","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"ShowFunc.vim","4":"ShowFunc.vim","src_id":"5884","5":"5884","creation_date":"1151420432","6":"1151420432"}]},"1587":{"script_id":"1587","0":"1587","script_name":"myghty.vim","1":"myghty.vim","script_type":"syntax","2":"syntax","summary":"Syntax script for Myghty","3":"Syntax script for Myghty","description":"This is a syntax script for Myghty (Python embedded in HTML). It was created from mason.vim just by replacing all \"perl\" occurences by \"python\".\r\nThen slight modifications in regular expressions were introduced to match differences between Mason and Myghty syntax.\r\nSeems to work well.","4":"This is a syntax script for Myghty (Python embedded in HTML). It was created from mason.vim just by replacing all \"perl\" occurences by \"python\".\r\nThen slight modifications in regular expressions were introduced to match differences between Mason and Myghty syntax.\r\nSeems to work well.","install_details":"1. Put the script in ~\/.vim\/syntax\/ directory.\r\n\r\n2. To use it manually, just type a command:\r\n:setf myghty\r\n\r\n3. To have it loaded automatically when editing *.myt files, add the following lines to your ~\/.vimrc file:\r\nau BufNewFile,BufRead *.myt         setf myghty\r\nfiletype plugin on","5":"1. Put the script in ~\/.vim\/syntax\/ directory.\r\n\r\n2. To use it manually, just type a command:\r\n:setf myghty\r\n\r\n3. To have it loaded automatically when editing *.myt files, add the following lines to your ~\/.vimrc file:\r\nau BufNewFile,BufRead *.myt         setf myghty\r\nfiletype plugin on","first_name":"Michal","6":"Michal","last_name":"Salaban","7":"Salaban","releases":[{"0":"1587","vim_version":"6.0","1":"6.0","script_version":"1.1","2":"1.1","version_comment":"I've made few modifications in regular expressions to match the differences between Myghty and Mason syntax (this file is based on mason.vim).","3":"I've made few modifications in regular expressions to match the differences between Myghty and Mason syntax (this file is based on mason.vim).","package":"myghty.vim","4":"myghty.vim","src_id":"5932","5":"5932","creation_date":"1152264850","6":"1152264850"},{"0":"1587","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"myghty.vim","4":"myghty.vim","src_id":"5879","5":"5879","creation_date":"1151381983","6":"1151381983"}]},"1586":{"script_id":"1586","0":"1586","script_name":"verilog_systemverilog.vim","1":"verilog_systemverilog.vim","script_type":"syntax","2":"syntax","summary":"Extending Verilog syntax highlighting for SystemVerilog","3":"Extending Verilog syntax highlighting for SystemVerilog","description":"This script extends Verilog syntax highlighting, which comes along with Vim 6.3, and adds SystemVerilog stuff to it. It will recognize Verilog and SystemVerilog syntax in *.v, *.vh and *.sv files. The new syntax is named as \"verilog_systemverilog\". If your scripts are loaded correctly, you should see this syntax name when you execute the Vim command \":set syntax?\" in your Verilog\/SystemVerilog files.","4":"This script extends Verilog syntax highlighting, which comes along with Vim 6.3, and adds SystemVerilog stuff to it. It will recognize Verilog and SystemVerilog syntax in *.v, *.vh and *.sv files. The new syntax is named as \"verilog_systemverilog\". If your scripts are loaded correctly, you should see this syntax name when you execute the Vim command \":set syntax?\" in your Verilog\/SystemVerilog files.","install_details":"Untar the package verilog_systemverilog.tar.gz\r\nCopy  verilog_systemverilog\/ftdetect\/verilog_systemverilog.vim to your $HOME\/.vim\/ftdetect directory.\r\nCopy verilog_systemverilog\/syntax\/verilog_systemverilog.vim to your $HOME\/.vim\/syntax directory.\r\nCopy verilog_systemverilog\/indent\/* to your $HOME\/.vim\/indent directory.","5":"Untar the package verilog_systemverilog.tar.gz\r\nCopy  verilog_systemverilog\/ftdetect\/verilog_systemverilog.vim to your $HOME\/.vim\/ftdetect directory.\r\nCopy verilog_systemverilog\/syntax\/verilog_systemverilog.vim to your $HOME\/.vim\/syntax directory.\r\nCopy verilog_systemverilog\/indent\/* to your $HOME\/.vim\/indent directory.","first_name":"Amit","6":"Amit","last_name":"Sethi","7":"Sethi","releases":[{"0":"1586","vim_version":"6.0","1":"6.0","script_version":"1.2","2":"1.2","version_comment":"syntax\/verilog_systemverilog.vim -\r\n      * Added new highlight group for SVA Assertions\r\n\r\nindent\/verilog_systemverilog.vim -\r\n      * Fixed conflicting function names","3":"syntax\/verilog_systemverilog.vim -\r\n      * Added new highlight group for SVA Assertions\r\n\r\nindent\/verilog_systemverilog.vim -\r\n      * Fixed conflicting function names","package":"verilog_systemverilog.tar.gz","4":"verilog_systemverilog.tar.gz","src_id":"5995","5":"5995","creation_date":"1153960510","6":"1153960510"},{"0":"1586","vim_version":"6.0","1":"6.0","script_version":"1.1","2":"1.1","version_comment":"Added indentation script for SystemVerilog.\r\n\r\nThis script is based on verilog.vim indentation script developed by Chih-Tsun Huang <cthuang@larc.ee.nthu.edu.tw> http:\/\/larc.ee.nthu.edu.tw\/~cthuang\/vim\/indent\/verilog.vim and packaged in Vim6.3\r\n\r\nInstallation\r\nCopy the verilog_systemverilog\/indent\/*.vim to your $HOME\/.vim\/indent directory","3":"Added indentation script for SystemVerilog.\r\n\r\nThis script is based on verilog.vim indentation script developed by Chih-Tsun Huang <cthuang@larc.ee.nthu.edu.tw> http:\/\/larc.ee.nthu.edu.tw\/~cthuang\/vim\/indent\/verilog.vim and packaged in Vim6.3\r\n\r\nInstallation\r\nCopy the verilog_systemverilog\/indent\/*.vim to your $HOME\/.vim\/indent directory","package":"verilog_systemverilog.tar.gz","4":"verilog_systemverilog.tar.gz","src_id":"5886","5":"5886","creation_date":"1151478795","6":"1151478795"},{"0":"1586","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"verilog_systemverilog.tar.gz","4":"verilog_systemverilog.tar.gz","src_id":"5878","5":"5878","creation_date":"1151364205","6":"1151364205"}]},"1585":{"script_id":"1585","0":"1585","script_name":"actionscript.vim","1":"actionscript.vim","script_type":"syntax","2":"syntax","summary":"Syntax file for ActionScript","3":"Syntax file for ActionScript","description":"This is a simple syntax highlighting script for ActionScript 3.0.","4":"This is a simple syntax highlighting script for ActionScript 3.0.","install_details":"","5":"","first_name":"Manish","6":"Manish","last_name":"Jethani","7":"Jethani","releases":[{"0":"1585","vim_version":"6.0","1":"6.0","script_version":"0.3","2":"0.3","version_comment":"Fixed \"for each\" matching. Thanks, Luke Palmer.","3":"Fixed \"for each\" matching. Thanks, Luke Palmer.","package":"actionscript.vim","4":"actionscript.vim","src_id":"16015","5":"16015","creation_date":"1309555545","6":"1309555545"},{"0":"1585","vim_version":"6.0","1":"6.0","script_version":"0.2.1","2":"0.2.1","version_comment":"Same as version 0.2 but with UNIX line breaks. Thanks to Adam Bair for the nudge.","3":"Same as version 0.2 but with UNIX line breaks. Thanks to Adam Bair for the nudge.","package":"actionscript.vim","4":"actionscript.vim","src_id":"7272","5":"7272","creation_date":"1182350516","6":"1182350516"},{"0":"1585","vim_version":"6.0","1":"6.0","script_version":"0.2","2":"0.2","version_comment":"Support for Flex metadata (Event, Style, etc.)","3":"Support for Flex metadata (Event, Style, etc.)","package":"actionscript.vim","4":"actionscript.vim","src_id":"5877","5":"5877","creation_date":"1151350995","6":"1151350995"},{"0":"1585","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial","3":"Initial","package":"actionscript.vim","4":"actionscript.vim","src_id":"5872","5":"5872","creation_date":"1151346114","6":"1151346114"}]},"1584":{"script_id":"1584","0":"1584","script_name":"Erlang plugin package","1":"Erlang plugin package","script_type":"utility","2":"utility","summary":"A pre-release of a plugin package for Erlang.","3":"A pre-release of a plugin package for Erlang.","description":"Erlang plugin package.\r\n\r\nIncludes indenting, syntax highlighting, folding, partial omni completion.\r\n\r\nThere is a repository at:\r\nhttp:\/\/github.com\/oscarh\/vimerl","4":"Erlang plugin package.\r\n\r\nIncludes indenting, syntax highlighting, folding, partial omni completion.\r\n\r\nThere is a repository at:\r\nhttp:\/\/github.com\/oscarh\/vimerl","install_details":"Either unpack the tarball to your local or global vim directory.\r\nsee :help plugin in vim for more info.","5":"Either unpack the tarball to your local or global vim directory.\r\nsee :help plugin in vim for more info.","first_name":"Oscar","6":"Oscar","last_name":"Hellstr\u00c3\u00b6m","7":"Hellstr\u00c3\u00b6m","releases":[{"0":"1584","vim_version":"7.0","1":"7.0","script_version":"0.2","2":"0.2","version_comment":"Cleaned up release and included indentation plugin from Csaba Hoch.","3":"Cleaned up release and included indentation plugin from Csaba Hoch.","package":"vim_erlang-0.2.tar.bz2","4":"vim_erlang-0.2.tar.bz2","src_id":"9305","5":"9305","creation_date":"1223104986","6":"1223104986"},{"0":"1584","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"vim-erlang.tar.bz2","4":"vim-erlang.tar.bz2","src_id":"5858","5":"5858","creation_date":"1151232116","6":"1151232116"}]},"1583":{"script_id":"1583","0":"1583","script_name":"tobase","1":"tobase","script_type":"utility","2":"utility","summary":"Convert from base(2,8,10,16) to base(2-32). Also character to html entity.","3":"Convert from base(2,8,10,16) to base(2-32). Also character to html entity.","description":"Number base converter and character to html entity converter.\r\nPlugin script for vim on any OS. \r\n\r\n(1) Number\/character base converter:\r\nGet a quick answer about a number or character without having\r\nto refer to an external chart or calculator.\r\n\r\nSyntaxes are \r\n :Tobase obase inum\r\n :Tobase obase [0oxy&]inum -- Optional modifier is '0,o,x,y,or &'\r\n\r\nConvert inum to obase and and return it.\r\nThe result will be placed in the unnamed register @@ \r\nwhere a subsequent 'p' command would put the result \r\n|P| before, |p| after the cursor. \r\nOptional modifier preceeding inum indicates input base\r\nof octal, hexadecimal, binary, or html character entity (e.g., &Auml;).\r\nVersion 1.2 has been extended to allow input number to be a character. \r\n(note: vy captures 1 character under the cursor.)\r\n(note: inum may be pasted from the mouse copied from any screen.)\r\nInput base defaults to decimal if not preceeded by a modifier.\r\nOutput base may be 2-32, c, or h (c-character, h-html).\r\nMultiple numbers can be input at once.\r\n\r\nYou could define a command to reduce typing Tobase e.g.,\r\ncommand -nargs=* C Tobase <args>\r\nThen you could execute it like the following examples:\r\n:C 16 101              -- prints 65\r\n:C c 192 193 xc2  -- prints 3 accented capital A's: grave, acute, circ\r\n\r\n(2) Convert characters to\/from html entities:\r\nFunction call Syntaxes\r\ncall Char2HtmlExec() -- Characters to entities (everything on all lines)\r\n[range] call Char2HtmlExec( [min, max, [string] ] ) -- Characters to entities\r\n[range] call Html2CharExec( [min, max, [string] ] ) -- Entities to characters\r\n[range] call Char2AsciiExec( [min, max, [string] ] ) -- Characters to ascii simulation\r\n\r\nThe optional [range] may be line numbers such as 1,15 \r\nor it may be relative such as .-5,.+5 or markers such as 'a,'b.\r\nRange may also be searches such as \/line with this\/,\/line with that\/\r\nIf range is omitted, or if range equates to just 1 line, it does all lines.\r\n\r\nThe optional [min, max, [string] ] goes like this:\r\nmin and max are numbers or characters which evaluate via Tobase\r\nto the range of 128 to 255.\r\nIf both min and max are equal to 0, it means 'do not convert any entities'.\r\nIn order to specify the optional [string], both min and max must be present.\r\nThe optional [string] is useful to specify whether to convert \r\nthe & < > \" to or from &amp;  &lt;  &gt; &quot;\r\nIf [string] contains & it should be the first one.\r\n[string] can contain any combination of & < > \"\r\n\r\nThus, [range] call Char2HtmlExec(0, 0, '& < > \"') \r\nwould cause html in [range] to display literally in the browser.\r\n\r\nIt is easier for me to put these commands in my ~\/.vimrc file:\r\ncommand! -range -nargs=* Foo <line1>,<line2>call Char2HtmlExec(<f-args>)\r\ncommand! -range -nargs=* Foof <line1>,<line2>call Html2CharExec(<f-args>)\r\ncommand! -range -nargs=* Fooa <line1>,<line2>call Char2AsciiExec(<f-args>)\r\nThose commands should be entered exactly as seen.\r\nYou may use other names besides Foo, Foof, and Fooa.\r\n\r\nCommand syntaxes\r\n[range] Foo [ min max [string] ]\r\nIn the command, note that there are not commas between the arguments\r\nand there are not any parentheses, i.e., Foo(128, 255, '&<>\"') is wrong!\r\n\r\nWith the commands in place the syntax is easier:\r\nFoo        - convert all accented characters to entities and convert & < > \"\r\nFoo j      - (j)ust convert & < > \"\r\nFoo n      - (n)ot convert & < > \"\r\n\r\n:Tobase -h    (Help)\r\n:Tobase -hc  (Character conversion help)\r\n\r\nTo run from the command line, a script like this could do the job:\r\n\"::::::::::::::\r\n\"foo.vim\r\n\"::::::::::::::\r\n\"vim -e input_file_name < foo.vim\r\n\"c:\\vim\\vim62\\gvim.exe -e input_file_name +\"source foo.vim\"\r\n\"                                                                         :help gui-w32-cmdargs\r\n:if argc() == 1 && exists(\"*Char2HtmlExec\")\r\n    :let ofile=argv(0) . '.tmp'\r\n    :call Char2HtmlExec()\r\n    :execute ':w!' . ofile . \"\\n\"\r\n:endif\r\n:q\r\n","4":"Number base converter and character to html entity converter.\r\nPlugin script for vim on any OS. \r\n\r\n(1) Number\/character base converter:\r\nGet a quick answer about a number or character without having\r\nto refer to an external chart or calculator.\r\n\r\nSyntaxes are \r\n :Tobase obase inum\r\n :Tobase obase [0oxy&]inum -- Optional modifier is '0,o,x,y,or &'\r\n\r\nConvert inum to obase and and return it.\r\nThe result will be placed in the unnamed register @@ \r\nwhere a subsequent 'p' command would put the result \r\n|P| before, |p| after the cursor. \r\nOptional modifier preceeding inum indicates input base\r\nof octal, hexadecimal, binary, or html character entity (e.g., &Auml;).\r\nVersion 1.2 has been extended to allow input number to be a character. \r\n(note: vy captures 1 character under the cursor.)\r\n(note: inum may be pasted from the mouse copied from any screen.)\r\nInput base defaults to decimal if not preceeded by a modifier.\r\nOutput base may be 2-32, c, or h (c-character, h-html).\r\nMultiple numbers can be input at once.\r\n\r\nYou could define a command to reduce typing Tobase e.g.,\r\ncommand -nargs=* C Tobase <args>\r\nThen you could execute it like the following examples:\r\n:C 16 101              -- prints 65\r\n:C c 192 193 xc2  -- prints 3 accented capital A's: grave, acute, circ\r\n\r\n(2) Convert characters to\/from html entities:\r\nFunction call Syntaxes\r\ncall Char2HtmlExec() -- Characters to entities (everything on all lines)\r\n[range] call Char2HtmlExec( [min, max, [string] ] ) -- Characters to entities\r\n[range] call Html2CharExec( [min, max, [string] ] ) -- Entities to characters\r\n[range] call Char2AsciiExec( [min, max, [string] ] ) -- Characters to ascii simulation\r\n\r\nThe optional [range] may be line numbers such as 1,15 \r\nor it may be relative such as .-5,.+5 or markers such as 'a,'b.\r\nRange may also be searches such as \/line with this\/,\/line with that\/\r\nIf range is omitted, or if range equates to just 1 line, it does all lines.\r\n\r\nThe optional [min, max, [string] ] goes like this:\r\nmin and max are numbers or characters which evaluate via Tobase\r\nto the range of 128 to 255.\r\nIf both min and max are equal to 0, it means 'do not convert any entities'.\r\nIn order to specify the optional [string], both min and max must be present.\r\nThe optional [string] is useful to specify whether to convert \r\nthe & < > \" to or from &amp;  &lt;  &gt; &quot;\r\nIf [string] contains & it should be the first one.\r\n[string] can contain any combination of & < > \"\r\n\r\nThus, [range] call Char2HtmlExec(0, 0, '& < > \"') \r\nwould cause html in [range] to display literally in the browser.\r\n\r\nIt is easier for me to put these commands in my ~\/.vimrc file:\r\ncommand! -range -nargs=* Foo <line1>,<line2>call Char2HtmlExec(<f-args>)\r\ncommand! -range -nargs=* Foof <line1>,<line2>call Html2CharExec(<f-args>)\r\ncommand! -range -nargs=* Fooa <line1>,<line2>call Char2AsciiExec(<f-args>)\r\nThose commands should be entered exactly as seen.\r\nYou may use other names besides Foo, Foof, and Fooa.\r\n\r\nCommand syntaxes\r\n[range] Foo [ min max [string] ]\r\nIn the command, note that there are not commas between the arguments\r\nand there are not any parentheses, i.e., Foo(128, 255, '&<>\"') is wrong!\r\n\r\nWith the commands in place the syntax is easier:\r\nFoo        - convert all accented characters to entities and convert & < > \"\r\nFoo j      - (j)ust convert & < > \"\r\nFoo n      - (n)ot convert & < > \"\r\n\r\n:Tobase -h    (Help)\r\n:Tobase -hc  (Character conversion help)\r\n\r\nTo run from the command line, a script like this could do the job:\r\n\"::::::::::::::\r\n\"foo.vim\r\n\"::::::::::::::\r\n\"vim -e input_file_name < foo.vim\r\n\"c:\\vim\\vim62\\gvim.exe -e input_file_name +\"source foo.vim\"\r\n\"                                                                         :help gui-w32-cmdargs\r\n:if argc() == 1 && exists(\"*Char2HtmlExec\")\r\n    :let ofile=argv(0) . '.tmp'\r\n    :call Char2HtmlExec()\r\n    :execute ':w!' . ofile . \"\\n\"\r\n:endif\r\n:q\r\n","install_details":"Copy to ~\/.vim\/plugin.\r\nOptionally set up commands to do html character conversion.\r\n","5":"Copy to ~\/.vim\/plugin.\r\nOptionally set up commands to do html character conversion.\r\n","first_name":"Walter","6":"Walter","last_name":"Hutchins","7":"Hutchins","releases":[{"0":"1583","vim_version":"6.0","1":"6.0","script_version":"1.2","2":"1.2","version_comment":"Allow input number to be a character.","3":"Allow input number to be a character.","package":"tobase.vim","4":"tobase.vim","src_id":"5897","5":"5897","creation_date":"1151594263","6":"1151594263"},{"0":"1583","vim_version":"6.0","1":"6.0","script_version":"1.1","2":"1.1","version_comment":"Added line range for character to html entity conversion.\r\nAdded ascii simulation for conversion to nearest look-alike \r\ncharacter.","3":"Added line range for character to html entity conversion.\r\nAdded ascii simulation for conversion to nearest look-alike \r\ncharacter.","package":"tobase.vim","4":"tobase.vim","src_id":"5885","5":"5885","creation_date":"1151444426","6":"1151444426"},{"0":"1583","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"tobase.vim","4":"tobase.vim","src_id":"5857","5":"5857","creation_date":"1151149542","6":"1151149542"}]},"1582":{"script_id":"1582","0":"1582","script_name":"vim-addon-background-cmd","1":"vim-addon-background-cmd","script_type":"utility","2":"utility","summary":"keep on working while compiling your project","3":"keep on working while compiling your project","description":"see Example in doc\r\n\r\nusing KISS implementation now\r\n\r\nUse vim-addon-manager to install this plugin:\r\nhttp:\/\/www.vim.org\/scripts\/script.php?script_id=2905\r\n\r\ngit repo: http:\/\/github.com\/MarcWeber\/vim-addon-background-cmd\r\n\r\nrenamed from runtaskinbackground -> vim-addon-background-cmd","4":"see Example in doc\r\n\r\nusing KISS implementation now\r\n\r\nUse vim-addon-manager to install this plugin:\r\nhttp:\/\/www.vim.org\/scripts\/script.php?script_id=2905\r\n\r\ngit repo: http:\/\/github.com\/MarcWeber\/vim-addon-background-cmd\r\n\r\nrenamed from runtaskinbackground -> vim-addon-background-cmd","install_details":"","5":"","first_name":"Marc","6":"Marc","last_name":"Weber","7":"Weber","releases":[{"0":"1582","vim_version":"6.0","1":"6.0","script_version":"0.3.1","2":"0.3.1","version_comment":"fixes + QuickFix shortcut","3":"fixes + QuickFix shortcut","package":"MarcWeber-vim-addon-background-cmd-be4a5a9.zip","4":"MarcWeber-vim-addon-background-cmd-be4a5a9.zip","src_id":"12129","5":"12129","creation_date":"1263942028","6":"1263942028"},{"0":"1582","vim_version":"7.0","1":"7.0","script_version":"0.2.1","2":"0.2.1","version_comment":"not sure how much I've changed. Should work out of the box now","3":"not sure how much I've changed. Should work out of the box now","package":"vimlib_runtaskinbackground_installer_sourceme.zip","4":"vimlib_runtaskinbackground_installer_sourceme.zip","src_id":"9535","5":"9535","creation_date":"1227270118","6":"1227270118"}]},"1581":{"script_id":"1581","0":"1581","script_name":"lookupfile","1":"lookupfile","script_type":"utility","2":"utility","summary":"Lookup files using Vim7 ins-completion","3":"Lookup files using Vim7 ins-completion","description":"Now requires Vim 7.1 version.\r\n\r\nLookupfile is a very simple approach to opening files by typing a pattern to\r\nrepresent the file you are looking for, and selecting a file from the completion\r\ndropdown to open in the current Vim session. It provides a consistent interface\r\nto lookup files by various means (tags, path, buffers, external tools etc.). It\r\nuses the new Vim7 insert-mode completion mechanism to show matching files.\r\n\r\nThe most part of the plugin is autoloaded so it doesn't increase the startup time and doesn't take up Vim resources until it is used for the first time.\r\n\r\nHere are the list of commands that the plugin defines:\r\n        LookupFile      Lookup files from tag files. This is a like a fast GNU\r\n                        find on name. It can lookup files from any Vim\r\n                        compatible tag file (which includes those from ctags),\r\n                        but at the moment it is advisable to generate\r\n                        specialized tag files using :find command (see\r\n                        |lookupfile-tags|).\r\n        LUPath          Lookup files from 'path' using |globpath()|. The :find\r\n                        command while being able to lookup files from 'path', it\r\n                        doesn't provide any completion mechanism, and it is\r\n                        clumsy when there are multiple files with the same name.\r\n                        The :find command doesn't even accept a pattern.\r\n        LUBufs          Lookup loaded files (buffers) using |bufname()|. This is\r\n                        a great addition to whatever buffer-explorer you are\r\n                        using. When there are too many buffers open, this\r\n                        sometimes makes it easy to find the right buffer, by\r\n                        typing part of its name.\r\n        LUWalk          Lookup files using |glob()|. This works like the Emacs\r\n                        ido.el, allowing you to walk up and down a path looking\r\n                        for files. If you use the filename completion with :edit\r\n                        command, then you will find this a lot more convenient\r\n                        and faster to use.\r\n        LUArgs          Lookup files from |:args| list.\r\n\r\nIt is also very easy to add new commands to or customize the plugin at various\r\nlevels. At the simplest, you can create custom command on top of the above that\r\neither pass dynamic arguments or tmporarily change the settings (e.g., you could\r\nhave a command that will start LUPath with the 'path' temporarily changed to\r\nfind only the include header files). You can also take advantage of the the\r\n|lookupfile-extend| features to add new commands that lookup files from a\r\ncompletely new source. You can even add commands that lookup something\r\ncompletely different than a file (like e.g., a spelling using spellsuggest()).\r\n\r\nFor more information install the plugin and type :h lookupfile after running :heptags command.\r\n\r\nHere is what users have to say about the plugin:\r\n    - I am thoroughly enjoying your lookupfile script -- it's just awesome! -- Reva Revadigar (regarding :LookupFile and :LUWalk commands)\r\n    - I use Lookupfile a couple of hundred times a day -- Max Dyckhoff (regarding :LookupFile command)\r\n    - I tried the new plugin. Excellent! Exactly what I want. -- Eddy Zhao (regarding :LUWalk command)\r\n\r\n\r\n\r\nSearch_Key_Words: lookupfile util utils lookup complete completion filename open edit file tags path ctags glob globpath Hari Krishna Dara","4":"Now requires Vim 7.1 version.\r\n\r\nLookupfile is a very simple approach to opening files by typing a pattern to\r\nrepresent the file you are looking for, and selecting a file from the completion\r\ndropdown to open in the current Vim session. It provides a consistent interface\r\nto lookup files by various means (tags, path, buffers, external tools etc.). It\r\nuses the new Vim7 insert-mode completion mechanism to show matching files.\r\n\r\nThe most part of the plugin is autoloaded so it doesn't increase the startup time and doesn't take up Vim resources until it is used for the first time.\r\n\r\nHere are the list of commands that the plugin defines:\r\n        LookupFile      Lookup files from tag files. This is a like a fast GNU\r\n                        find on name. It can lookup files from any Vim\r\n                        compatible tag file (which includes those from ctags),\r\n                        but at the moment it is advisable to generate\r\n                        specialized tag files using :find command (see\r\n                        |lookupfile-tags|).\r\n        LUPath          Lookup files from 'path' using |globpath()|. The :find\r\n                        command while being able to lookup files from 'path', it\r\n                        doesn't provide any completion mechanism, and it is\r\n                        clumsy when there are multiple files with the same name.\r\n                        The :find command doesn't even accept a pattern.\r\n        LUBufs          Lookup loaded files (buffers) using |bufname()|. This is\r\n                        a great addition to whatever buffer-explorer you are\r\n                        using. When there are too many buffers open, this\r\n                        sometimes makes it easy to find the right buffer, by\r\n                        typing part of its name.\r\n        LUWalk          Lookup files using |glob()|. This works like the Emacs\r\n                        ido.el, allowing you to walk up and down a path looking\r\n                        for files. If you use the filename completion with :edit\r\n                        command, then you will find this a lot more convenient\r\n                        and faster to use.\r\n        LUArgs          Lookup files from |:args| list.\r\n\r\nIt is also very easy to add new commands to or customize the plugin at various\r\nlevels. At the simplest, you can create custom command on top of the above that\r\neither pass dynamic arguments or tmporarily change the settings (e.g., you could\r\nhave a command that will start LUPath with the 'path' temporarily changed to\r\nfind only the include header files). You can also take advantage of the the\r\n|lookupfile-extend| features to add new commands that lookup files from a\r\ncompletely new source. You can even add commands that lookup something\r\ncompletely different than a file (like e.g., a spelling using spellsuggest()).\r\n\r\nFor more information install the plugin and type :h lookupfile after running :heptags command.\r\n\r\nHere is what users have to say about the plugin:\r\n    - I am thoroughly enjoying your lookupfile script -- it's just awesome! -- Reva Revadigar (regarding :LookupFile and :LUWalk commands)\r\n    - I use Lookupfile a couple of hundred times a day -- Max Dyckhoff (regarding :LookupFile command)\r\n    - I tried the new plugin. Excellent! Exactly what I want. -- Eddy Zhao (regarding :LUWalk command)\r\n\r\n\r\n\r\nSearch_Key_Words: lookupfile util utils lookup complete completion filename open edit file tags path ctags glob globpath Hari Krishna Dara","install_details":"Expand the zip in your runtime directory.\r\nGenerate help tags using :helptags command.\r\nInstall the latest version of genutils (vimscript #197).\r\nRead help on |lookupfile-installation|.\r\n","5":"Expand the zip in your runtime directory.\r\nGenerate help tags using :helptags command.\r\nInstall the latest version of genutils (vimscript #197).\r\nRead help on |lookupfile-installation|.\r\n","first_name":"Hari Krishna","6":"Hari Krishna","last_name":"Dara","7":"Dara","releases":[{"0":"1581","vim_version":"7.0","1":"7.0","script_version":"1.8","2":"1.8","version_comment":"- Even more control on the mappings with the new setting\r\n  |LookupFile_EnableRemapCmd|.\r\n- New feature to specify names that follow CamelCasing pattern by abbreviating\r\n  them. This works more or less like for the \"Open Type\" dialog in Eclipse.\r\n  For more information see, |LookupFile_TagsExpandCamelCase|.\r\n- New feature to remember the recent files, see\r\n  |Lookupfile_RecentFileListSize|.\r\n- Changed the message line such that the message is shown on the left side and\r\n  the pattern is shown on the right side. This prevents the more important\r\n  message from getting lost when the filenames are too long.\r\n- New settings |LookupFile_EnableRemapCmd|, |LookupFile_SearchForBufsInTabs|,\r\n  |LookupFile_TagsExpandCamelCase|, |Lookupfile_RecentFileListSize|.\r\n","3":"- Even more control on the mappings with the new setting\r\n  |LookupFile_EnableRemapCmd|.\r\n- New feature to specify names that follow CamelCasing pattern by abbreviating\r\n  them. This works more or less like for the \"Open Type\" dialog in Eclipse.\r\n  For more information see, |LookupFile_TagsExpandCamelCase|.\r\n- New feature to remember the recent files, see\r\n  |Lookupfile_RecentFileListSize|.\r\n- Changed the message line such that the message is shown on the left side and\r\n  the pattern is shown on the right side. This prevents the more important\r\n  message from getting lost when the filenames are too long.\r\n- New settings |LookupFile_EnableRemapCmd|, |LookupFile_SearchForBufsInTabs|,\r\n  |LookupFile_TagsExpandCamelCase|, |Lookupfile_RecentFileListSize|.\r\n","package":"lookupfile-1.8.zip","4":"lookupfile-1.8.zip","src_id":"7671","5":"7671","creation_date":"1189708783","6":"1189708783"},{"0":"1581","vim_version":"7.0","1":"7.0","script_version":"1.7","2":"1.7","version_comment":"- Bug fix: LUPath and LUArgs were broken (stoning at gmail dot com).\r\n- Removed debugging code. ","3":"- Bug fix: LUPath and LUArgs were broken (stoning at gmail dot com).\r\n- Removed debugging code. ","package":"lookupfile-1.7.zip","4":"lookupfile-1.7.zip","src_id":"7175","5":"7175","creation_date":"1180432030","6":"1180432030"},{"0":"1581","vim_version":"7.0","1":"7.0","script_version":"1.6","2":"1.6","version_comment":"Requires Vim 7.1.\r\n\r\nThis is a combined 1.5(previously unreleased)\/1.6 release of lookupfile and includes the following improvements and bugfixes.\r\n- LookupFile now uses CursorHoldI instead of CursorMovedI to show matches. This\r\n  means, the matches are not computed until you stop typing, which should give a\r\n  better experience. See |LookupFile_UpdateTime| for more information.\r\n- The plugin now sets 'completefunc' such that you can now hit <C-X><C-U> to\r\n  trigger completions explicitly (instead of waiting for\r\n  g:LookupFile_UpdateTime). This is useful if you are a slow typer and so prefer\r\n  a large value for g:LookupFile_UpdateTime.\r\n- The plugin now recognizes 'ignorecase' and 'smartcase' settings to match files\r\n  even on systems that are case-sensitive. This is mainly significant for the\r\n  commands that use |globpath()| or |glob()| which are, |:LUPath| and |:LUWalk|,\r\n  as the others already respect these settings.\r\n- There is now a separate command called :LUTags that always does what\r\n  :LookupFile used to do, while the :LookupFile command itself now gets\r\n  dynamically assigned to the last command used. This also means, the map that\r\n  is choosen in |lookupfile-map| now invokes the last command that is used, use\r\n  |LookupFile_DefaultCmd| and |LookupFile_DisableDefaultMap| settings to control\r\n  this behavior.\r\n- LUWalk now supports showing only directory names in the results. Just type\r\n  an extra \/ to filter those that are not directories (the suffix will then be\r\n  two slashes).\r\n- The default behavior of |:LUBufs| is now to match the entire |bufname()|,\r\n  just like the |:buffer| command would do. To see the old behavior, reset\r\n  |LookupFile_Bufs_LikeBufCmd| setting.\r\n- If you have the new version of SelectBuf also installed, you can have\r\n  |:LUBufs| sort buffers in MRU order. See, |LookupFile_Bufs_BufListExpr|.\r\n- When tags file is not generated as per the requirements of |lookupfile-tags|,\r\n  the format of the matches doesn't look good, so by default the matches just\r\n  show full filenames. See |LookupFile_UsingSpecializedTags| to get better\r\n  formatted results.\r\n- New settings |LookupFile_UsingSpecializedTags|, |LookupFile_SortMethod|,\r\n  |LookupFile_DefaultCmd|, |LookupFile_DisableDefaultMap|,\r\n  |LookupFile_Bufs_LikeBufCmd|, |LookupFile_Bufs_BufListExpr|,\r\n  |LookupFile_EscCancelsPopup|.\r\n- Bug fix: exact matches were getting dropped from results  (Max Dyckhoff).\r\n- Bug fix: <BS> in |:LUWalk| right after selecting a directory match caused it\r\n  to misbehave.\r\n- Bug fix: if tags file is not in the current directory, the opening fails. Now\r\n  :LookupFile expands the filenames explicitly so that the paths are always\r\n  valid.\r\n- Bug fix: Unsetting |LookupFile_AllowNewFiles| didn't disable the feature.\r\n- Bug fix: <C-E> was not hiding the popup.\r\n- Bug fix: <S-BS> triggers the default insert-mode completion (Max Dyckhoff).\r\n- Fixed misc. bugs in opening files.\r\n- Workaround for <Esc> not working on some systems, allow disabling the\r\n  mapping.\r\n- Bug fix: When there is an exising swapfile, opening the files result in an\r\n  error message (David Fishburn).\r\n- When LookupFile_UsingSpecializedTags is set, sorting should be done on the\r\n  filename (patch by Timothy, Guo). ","3":"Requires Vim 7.1.\r\n\r\nThis is a combined 1.5(previously unreleased)\/1.6 release of lookupfile and includes the following improvements and bugfixes.\r\n- LookupFile now uses CursorHoldI instead of CursorMovedI to show matches. This\r\n  means, the matches are not computed until you stop typing, which should give a\r\n  better experience. See |LookupFile_UpdateTime| for more information.\r\n- The plugin now sets 'completefunc' such that you can now hit <C-X><C-U> to\r\n  trigger completions explicitly (instead of waiting for\r\n  g:LookupFile_UpdateTime). This is useful if you are a slow typer and so prefer\r\n  a large value for g:LookupFile_UpdateTime.\r\n- The plugin now recognizes 'ignorecase' and 'smartcase' settings to match files\r\n  even on systems that are case-sensitive. This is mainly significant for the\r\n  commands that use |globpath()| or |glob()| which are, |:LUPath| and |:LUWalk|,\r\n  as the others already respect these settings.\r\n- There is now a separate command called :LUTags that always does what\r\n  :LookupFile used to do, while the :LookupFile command itself now gets\r\n  dynamically assigned to the last command used. This also means, the map that\r\n  is choosen in |lookupfile-map| now invokes the last command that is used, use\r\n  |LookupFile_DefaultCmd| and |LookupFile_DisableDefaultMap| settings to control\r\n  this behavior.\r\n- LUWalk now supports showing only directory names in the results. Just type\r\n  an extra \/ to filter those that are not directories (the suffix will then be\r\n  two slashes).\r\n- The default behavior of |:LUBufs| is now to match the entire |bufname()|,\r\n  just like the |:buffer| command would do. To see the old behavior, reset\r\n  |LookupFile_Bufs_LikeBufCmd| setting.\r\n- If you have the new version of SelectBuf also installed, you can have\r\n  |:LUBufs| sort buffers in MRU order. See, |LookupFile_Bufs_BufListExpr|.\r\n- When tags file is not generated as per the requirements of |lookupfile-tags|,\r\n  the format of the matches doesn't look good, so by default the matches just\r\n  show full filenames. See |LookupFile_UsingSpecializedTags| to get better\r\n  formatted results.\r\n- New settings |LookupFile_UsingSpecializedTags|, |LookupFile_SortMethod|,\r\n  |LookupFile_DefaultCmd|, |LookupFile_DisableDefaultMap|,\r\n  |LookupFile_Bufs_LikeBufCmd|, |LookupFile_Bufs_BufListExpr|,\r\n  |LookupFile_EscCancelsPopup|.\r\n- Bug fix: exact matches were getting dropped from results  (Max Dyckhoff).\r\n- Bug fix: <BS> in |:LUWalk| right after selecting a directory match caused it\r\n  to misbehave.\r\n- Bug fix: if tags file is not in the current directory, the opening fails. Now\r\n  :LookupFile expands the filenames explicitly so that the paths are always\r\n  valid.\r\n- Bug fix: Unsetting |LookupFile_AllowNewFiles| didn't disable the feature.\r\n- Bug fix: <C-E> was not hiding the popup.\r\n- Bug fix: <S-BS> triggers the default insert-mode completion (Max Dyckhoff).\r\n- Fixed misc. bugs in opening files.\r\n- Workaround for <Esc> not working on some systems, allow disabling the\r\n  mapping.\r\n- Bug fix: When there is an exising swapfile, opening the files result in an\r\n  error message (David Fishburn).\r\n- When LookupFile_UsingSpecializedTags is set, sorting should be done on the\r\n  filename (patch by Timothy, Guo). ","package":"lookupfile-1.6.zip","4":"lookupfile-1.6.zip","src_id":"7172","5":"7172","creation_date":"1180382117","6":"1180382117"},{"0":"1581","vim_version":"7.0","1":"7.0","script_version":"1.4","2":"1.4","version_comment":"- Fixed a bug in the initial pattern getting ignored.\r\n- LUBufs now completes the full pathname of the buffers, so that it is\r\n  less dependent on the current directory of Vim.\r\n- LUBufs and LUPath commands now present the matches in a better format.\r\n- Pressing <F5> while popup is visible didn't close the lookupfile\r\n  window.\r\n","3":"- Fixed a bug in the initial pattern getting ignored.\r\n- LUBufs now completes the full pathname of the buffers, so that it is\r\n  less dependent on the current directory of Vim.\r\n- LUBufs and LUPath commands now present the matches in a better format.\r\n- Pressing <F5> while popup is visible didn't close the lookupfile\r\n  window.\r\n","package":"lookupfile-1.4.zip","4":"lookupfile-1.4.zip","src_id":"6124","5":"6124","creation_date":"1157042589","6":"1157042589"},{"0":"1581","vim_version":"7.0","1":"7.0","script_version":"1.3","2":"1.3","version_comment":"- New feature to create a file, if the file doesn't already exist (Ido).\r\n  Can be disabled using g:LookupFile_AllowNewFiles setting.\r\n- Bug fix: while using LUWalk, if the first match is a directory, then\r\n  selecting files was offset by one.\r\n","3":"- New feature to create a file, if the file doesn't already exist (Ido).\r\n  Can be disabled using g:LookupFile_AllowNewFiles setting.\r\n- Bug fix: while using LUWalk, if the first match is a directory, then\r\n  selecting files was offset by one.\r\n","package":"lookupfile-1.3.zip","4":"lookupfile-1.3.zip","src_id":"6083","5":"6083","creation_date":"1156105056","6":"1156105056"},{"0":"1581","vim_version":"7.0","1":"7.0","script_version":"1.2","2":"1.2","version_comment":"- New LUWalk command that works very similar to Emacs ido.el to quickly navigate\r\n  paths.\r\n- g:LookupFile_AlwaysAcceptFirst setting to always accept the first\r\n  entry (the default is 0).\r\n- g:LookupFile_FileFilter to specify a filter.\r\n- All commands now accepts the initial pattern as argument. This provides\r\n  unlimited number of possibilities to create your own custom commands (see\r\n  |lookupfile-tips| for some examples).\r\n- The g:LookupFile_MinPatLength is automatically set to 0 except for tag and\r\n  'path' lookup.\r\n- When Lookup window is opened, the filetype is set to \"lookupfile\". This allows\r\n  you to create ftplugins to fine tune the behavior.\r\n- Renamed :LUBuf command to :LUBufs.\r\nThe plugin has been in extensive use by myself and a couple of other users, and there are no major issues.","3":"- New LUWalk command that works very similar to Emacs ido.el to quickly navigate\r\n  paths.\r\n- g:LookupFile_AlwaysAcceptFirst setting to always accept the first\r\n  entry (the default is 0).\r\n- g:LookupFile_FileFilter to specify a filter.\r\n- All commands now accepts the initial pattern as argument. This provides\r\n  unlimited number of possibilities to create your own custom commands (see\r\n  |lookupfile-tips| for some examples).\r\n- The g:LookupFile_MinPatLength is automatically set to 0 except for tag and\r\n  'path' lookup.\r\n- When Lookup window is opened, the filetype is set to \"lookupfile\". This allows\r\n  you to create ftplugins to fine tune the behavior.\r\n- Renamed :LUBuf command to :LUBufs.\r\nThe plugin has been in extensive use by myself and a couple of other users, and there are no major issues.","package":"lookupfile-1.2.zip","4":"lookupfile-1.2.zip","src_id":"6073","5":"6073","creation_date":"1155732035","6":"1155732035"},{"0":"1581","vim_version":"6.0","1":"6.0","script_version":"1.1","2":"1.1","version_comment":"- Added LUBuf, LUPath and LUArgs commands.\r\n- Renamed the prefix for all the settings from g:lookupfile_ to\r\n  g:LookupFile_. This is required to support Funcref settings.\r\n- Now the cursor position is preserved, while opening a file that is\r\n  already loaded.\r\n- Using genutils 2.1.\r\n","3":"- Added LUBuf, LUPath and LUArgs commands.\r\n- Renamed the prefix for all the settings from g:lookupfile_ to\r\n  g:LookupFile_. This is required to support Funcref settings.\r\n- Now the cursor position is preserved, while opening a file that is\r\n  already loaded.\r\n- Using genutils 2.1.\r\n","package":"lookupfile-1.1.zip","4":"lookupfile-1.1.zip","src_id":"5921","5":"5921","creation_date":"1152101456","6":"1152101456"},{"0":"1581","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"lookupfile-1.0.zip","4":"lookupfile-1.0.zip","src_id":"5854","5":"5854","creation_date":"1151073695","6":"1151073695"}]},"1580":{"script_id":"1580","0":"1580","script_name":"FlagIt","1":"FlagIt","script_type":"utility","2":"utility","summary":"Add some flags to your code","3":"Add some flags to your code","description":"FlagIt privides a simple way to flag lines with a set of signs.\r\n\r\nScreenshot: http:\/\/sexylizard.org\/images\/flagit.png\r\n(Icons from http:\/\/tango.freedesktop.org\/Tango_Desktop_Project)\r\n\r\nA configuration example is provided in the script header.\r\n\r\nUsage:\r\ng:Fi_Flags\r\n\ta dictionnary which describes the flags\r\n\tSynopsis:\r\n\tan item: '\"flagName\" : [\"aUrlToTheImagePath\", \"aText, One or two character\", uniq, \"additionnal options\"]'\r\n\r\n\t\"flagName\" : an uniq identifier\r\n\t\"aUrlToTheImagePath\" : The path to a pixmap. The flag will be drawn as a pixmap (if GUI avaible and g:Fi_OnlyText is 0).\r\n\t\"aText\" : One or two character. The flag will be drawn as a text (if GUI not avaible or g:Fi_OnlyText is 1)\r\n\tuniq : If 1, only one instance of this flag will be drawn, else multiple instance will be allowed\r\n\t\"additionnal options\" : options added to signs definition (cf. \"sign define\")\r\n\r\n\texample:\r\n\t\tlet g:Fi_Flags = {\"fixme\" : [\"\/home\/login\/.vim\/signs\/fixme.png\", \"!!\", 0, \"\"],\r\n\t\t\\ \"error\" : [\"\/home\/login\/.vim\/signs\/error.png\", \"XX\", 1, \"texthl=ErrorMsg linehl=ErrorMsg\"] }\r\n\r\ng:Fi_ShowMenu\r\n\tIf 1 and Gui avaible and g:Fi_OnlyText is 0, a menu will be added to the ToolBar.\r\n\r\ng:Fi_OnlyText\r\n\tIf 1, pixmap will not be used\r\n\r\nFlagList\r\n\tList all avaible flags\r\n\r\nFlagIt flagName [line number]\r\n\tAdd a flag. If line number is not provided, current line is uses\r\n\tIl a flag is already presents, it will be removed\r\n\r\nUnFlag [flagName]\r\n\tRemove all flags of type flagName\r\n\tIf flagName is not provided,  remove all flags\r\n\r\nFlagDemo\r\n\tJust a way to draw all kind of flags (for test)\r\n\r\nTODO:\r\nsave flags (Modelines ? session ? dedicated file ?)\r\n","4":"FlagIt privides a simple way to flag lines with a set of signs.\r\n\r\nScreenshot: http:\/\/sexylizard.org\/images\/flagit.png\r\n(Icons from http:\/\/tango.freedesktop.org\/Tango_Desktop_Project)\r\n\r\nA configuration example is provided in the script header.\r\n\r\nUsage:\r\ng:Fi_Flags\r\n\ta dictionnary which describes the flags\r\n\tSynopsis:\r\n\tan item: '\"flagName\" : [\"aUrlToTheImagePath\", \"aText, One or two character\", uniq, \"additionnal options\"]'\r\n\r\n\t\"flagName\" : an uniq identifier\r\n\t\"aUrlToTheImagePath\" : The path to a pixmap. The flag will be drawn as a pixmap (if GUI avaible and g:Fi_OnlyText is 0).\r\n\t\"aText\" : One or two character. The flag will be drawn as a text (if GUI not avaible or g:Fi_OnlyText is 1)\r\n\tuniq : If 1, only one instance of this flag will be drawn, else multiple instance will be allowed\r\n\t\"additionnal options\" : options added to signs definition (cf. \"sign define\")\r\n\r\n\texample:\r\n\t\tlet g:Fi_Flags = {\"fixme\" : [\"\/home\/login\/.vim\/signs\/fixme.png\", \"!!\", 0, \"\"],\r\n\t\t\\ \"error\" : [\"\/home\/login\/.vim\/signs\/error.png\", \"XX\", 1, \"texthl=ErrorMsg linehl=ErrorMsg\"] }\r\n\r\ng:Fi_ShowMenu\r\n\tIf 1 and Gui avaible and g:Fi_OnlyText is 0, a menu will be added to the ToolBar.\r\n\r\ng:Fi_OnlyText\r\n\tIf 1, pixmap will not be used\r\n\r\nFlagList\r\n\tList all avaible flags\r\n\r\nFlagIt flagName [line number]\r\n\tAdd a flag. If line number is not provided, current line is uses\r\n\tIl a flag is already presents, it will be removed\r\n\r\nUnFlag [flagName]\r\n\tRemove all flags of type flagName\r\n\tIf flagName is not provided,  remove all flags\r\n\r\nFlagDemo\r\n\tJust a way to draw all kind of flags (for test)\r\n\r\nTODO:\r\nsave flags (Modelines ? session ? dedicated file ?)\r\n","install_details":"Drop it into your plugin directory","5":"Drop it into your plugin directory","first_name":"Paul","6":"Paul","last_name":"Rouget","7":"Rouget","releases":[{"0":"1580","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"flagit.vim","4":"flagit.vim","src_id":"5851","5":"5851","creation_date":"1150946310","6":"1150946310"}]},"1579":{"script_id":"1579","0":"1579","script_name":"cr-bs-del-space-tab.vim","1":"cr-bs-del-space-tab.vim","script_type":"utility","2":"utility","summary":"Use CR-TAB-DEL-SPACE-TAB in Normal Mode like in Insert Mode","3":"Use CR-TAB-DEL-SPACE-TAB in Normal Mode like in Insert Mode","description":"Use the keys: \"Return, Backspace, Delete, Space, Tab\" in Normal-Mode like you are used from Insert-Mode.\r\nVery usefull to do some code cleanup in Normal-Mode, or to make some place for copy\/paste action. Or just to delete a line fast and easy.\r\n(or insert a new line.....). ","4":"Use the keys: \"Return, Backspace, Delete, Space, Tab\" in Normal-Mode like you are used from Insert-Mode.\r\nVery usefull to do some code cleanup in Normal-Mode, or to make some place for copy\/paste action. Or just to delete a line fast and easy.\r\n(or insert a new line.....). ","install_details":"Drop into plugin directory.","5":"Drop into plugin directory.","first_name":"Jochen","6":"Jochen","last_name":"Baier","7":"Baier","releases":[{"0":"1579","vim_version":"7.0","1":"7.0","script_version":"0.02","2":"0.02","version_comment":"*Fixed problems with Return-key in Preview and Tlist window. (And other non normal Windows)","3":"*Fixed problems with Return-key in Preview and Tlist window. (And other non normal Windows)","package":"cr-bs-del-space-tab.vim","4":"cr-bs-del-space-tab.vim","src_id":"5889","5":"5889","creation_date":"1151494191","6":"1151494191"},{"0":"1579","vim_version":"7.0","1":"7.0","script_version":"0.01","2":"0.01","version_comment":"Initial upload","3":"Initial upload","package":"cr-bs-del-space-tab.vim","4":"cr-bs-del-space-tab.vim","src_id":"5850","5":"5850","creation_date":"1150886556","6":"1150886556"}]},"1578":{"script_id":"1578","0":"1578","script_name":"tcl.vim","1":"tcl.vim","script_type":"syntax","2":"syntax","summary":"Tcl syntax TEST version","3":"Tcl syntax TEST version","description":"I am experimenting with updating the syntax file for Tcl. I have added more \"keywords\" and I have enable the syntax highlighting of an option flags starting with \"-\" (i.e. -padx, -text).\r\n\r\nSince Tcl doesn't officially have keywords they may need to be pared down since I added all of the Tcl and Tk commands from the Tcl wiki page.\r\n\r\nNote: This is basically just something I am working on and not for consumption. However, if you have suggestions or requests please email me.\r\n\r\nNote: You need to put \"let tcl_extended_syntax=1\" in your vimrc to get the extra OO syntax coloring. Otherwise you get the \"standard\" syntax coloring.","4":"I am experimenting with updating the syntax file for Tcl. I have added more \"keywords\" and I have enable the syntax highlighting of an option flags starting with \"-\" (i.e. -padx, -text).\r\n\r\nSince Tcl doesn't officially have keywords they may need to be pared down since I added all of the Tcl and Tk commands from the Tcl wiki page.\r\n\r\nNote: This is basically just something I am working on and not for consumption. However, if you have suggestions or requests please email me.\r\n\r\nNote: You need to put \"let tcl_extended_syntax=1\" in your vimrc to get the extra OO syntax coloring. Otherwise you get the \"standard\" syntax coloring.","install_details":"","5":"","first_name":"Robert","6":"Robert","last_name":"Hicks","7":"Hicks","releases":[{"0":"1578","vim_version":"7.0","1":"7.0","script_version":".92","2":".92","version_comment":"* If you want extended syntax put g:tcl_extended_syntax=1 in your .vimrc\r\n* I guess I will start using small rev numbers since I am getting close to 1.0  : )","3":"* If you want extended syntax put g:tcl_extended_syntax=1 in your .vimrc\r\n* I guess I will start using small rev numbers since I am getting close to 1.0  : )","package":"tcl.vim","4":"tcl.vim","src_id":"6133","5":"6133","creation_date":"1157121704","6":"1157121704"},{"0":"1578","vim_version":"7.0","1":"7.0","script_version":".91","2":".91","version_comment":"* Some patches by IIlya to fix some highlighting errors\r\n* renamed script vim.tcl since it *is* supposed to replace the current script in the Vim distro.","3":"* Some patches by IIlya to fix some highlighting errors\r\n* renamed script vim.tcl since it *is* supposed to replace the current script in the Vim distro.","package":"tcl.vim","4":"tcl.vim","src_id":"6132","5":"6132","creation_date":"1157121217","6":"1157121217"},{"0":"1578","vim_version":"7.0","1":"7.0","script_version":"0.9","2":"0.9","version_comment":"* some small bug fixes","3":"* some small bug fixes","package":"tcldev.vim","4":"tcldev.vim","src_id":"6077","5":"6077","creation_date":"1155817867","6":"1155817867"},{"0":"1578","vim_version":"7.0","1":"7.0","script_version":"0.8","2":"0.8","version_comment":"* Cleaned up some\r\n* Namespaces work *I hope*","3":"* Cleaned up some\r\n* Namespaces work *I hope*","package":"tcldev.vim","4":"tcldev.vim","src_id":"5931","5":"5931","creation_date":"1152264564","6":"1152264564"},{"0":"1578","vim_version":"7.0","1":"7.0","script_version":".007","2":".007","version_comment":"* Maintainership of tcl.vim has passed to me. yikes!\r\n* Adding a check. If a user puts \"let tcl_oo=1\" in their rc file then the OO stuff is turned off.\r\n** That is currently turned off for dev purposes but does work","3":"* Maintainership of tcl.vim has passed to me. yikes!\r\n* Adding a check. If a user puts \"let tcl_oo=1\" in their rc file then the OO stuff is turned off.\r\n** That is currently turned off for dev purposes but does work","package":"tcldev.vim","4":"tcldev.vim","src_id":"5902","5":"5902","creation_date":"1151672630","6":"1151672630"},{"0":"1578","vim_version":"7.0","1":"7.0","script_version":".006","2":".006","version_comment":"* Anchored the namespaces so \"oo::whatever\" will color but \"foo::whatever\" will not.\r\n* I have some other things to match like \"ttk::\" can be embedded in other stuff and ::one is also a namespace  *sheesh*! ","3":"* Anchored the namespaces so \"oo::whatever\" will color but \"foo::whatever\" will not.\r\n* I have some other things to match like \"ttk::\" can be embedded in other stuff and ::one is also a namespace  *sheesh*! ","package":"tcldev.vim","4":"tcldev.vim","src_id":"5894","5":"5894","creation_date":"1151566549","6":"1151566549"},{"0":"1578","vim_version":"7.0","1":"7.0","script_version":".005","2":".005","version_comment":"* Added namespace highlighting for ttk::, snit::, itcl:: and oo::\r\n* Added keywords to support OO frameworks","3":"* Added namespace highlighting for ttk::, snit::, itcl:: and oo::\r\n* Added keywords to support OO frameworks","package":"tcldev.vim","4":"tcldev.vim","src_id":"5880","5":"5880","creation_date":"1151389509","6":"1151389509"},{"0":"1578","vim_version":"7.0","1":"7.0","script_version":".004","2":".004","version_comment":"Some cleanup...\r\n\r\n* Added Snit (snit::) and Tile (ttk::) namespace coloring\r\n","3":"Some cleanup...\r\n\r\n* Added Snit (snit::) and Tile (ttk::) namespace coloring\r\n","package":"tcldev.vim","4":"tcldev.vim","src_id":"5863","5":"5863","creation_date":"1151313595","6":"1151313595"},{"0":"1578","vim_version":"7.0","1":"7.0","script_version":".003","2":".003","version_comment":"This *should* source correctly now.","3":"This *should* source correctly now.","package":"tcldev.vim","4":"tcldev.vim","src_id":"5862","5":"5862","creation_date":"1151302644","6":"1151302644"},{"0":"1578","vim_version":"7.0","1":"7.0","script_version":".002","2":".002","version_comment":"Changed the name to \"tcldev.vim\" to better reflect its intent!\r\n\r\nAdded folding\r\n\r\nAdded some widget stuff back in (not tested!)\r\n\r\nChanged the \"-\" option to make sure it only colors alphas and not numerics\r\n\r\nLots of this was done by Tomasz Kalkosiński!!\r\n\r\nThe intent is to get this up to speed and then submit it to the current maintainer of \"tcl.vim\".\r\n\r\nTODO: Tomasz implemented a tclOperator section that isn't in working condition yet.\r\n\r\nTODO: Color the following like \/* *\/\r\n\r\nif {0} {\r\n\r\n}\r\n\r\nTODO: Whatever else floats our boat?  : )","3":"Changed the name to \"tcldev.vim\" to better reflect its intent!\r\n\r\nAdded folding\r\n\r\nAdded some widget stuff back in (not tested!)\r\n\r\nChanged the \"-\" option to make sure it only colors alphas and not numerics\r\n\r\nLots of this was done by Tomasz Kalkosiński!!\r\n\r\nThe intent is to get this up to speed and then submit it to the current maintainer of \"tcl.vim\".\r\n\r\nTODO: Tomasz implemented a tclOperator section that isn't in working condition yet.\r\n\r\nTODO: Color the following like \/* *\/\r\n\r\nif {0} {\r\n\r\n}\r\n\r\nTODO: Whatever else floats our boat?  : )","package":"tcldev.vim","4":"tcldev.vim","src_id":"5852","5":"5852","creation_date":"1151044687","6":"1151044687"},{"0":"1578","vim_version":"7.0","1":"7.0","script_version":".001","2":".001","version_comment":"Initial upload","3":"Initial upload","package":"tcl.vim","4":"tcl.vim","src_id":"5844","5":"5844","creation_date":"1150790652","6":"1150790652"}]},"1577":{"script_id":"1577","0":"1577","script_name":"css.vim","1":"css.vim","script_type":"syntax","2":"syntax","summary":"CSS compiler file","3":"CSS compiler file","description":"This compiler script allows to validate CSS files within vim, through W3C's CSS validation web-service. The compiler file invokes a helper perl script that connects to jigsaw.w3.org and reports all css errors and warnings, showing them up directly in the vim buffer (with :copen command, BTW).\r\n\r\nSurely the script can be made better in many ways.\r\nSuggestions welcome!\r\n\r\nREQUIREMENTS:\r\n- a [dr]ecent perl interpreter installed\r\n- WebService::Validator::CSS::W3C module installed from CPAN.\r\n","4":"This compiler script allows to validate CSS files within vim, through W3C's CSS validation web-service. The compiler file invokes a helper perl script that connects to jigsaw.w3.org and reports all css errors and warnings, showing them up directly in the vim buffer (with :copen command, BTW).\r\n\r\nSurely the script can be made better in many ways.\r\nSuggestions welcome!\r\n\r\nREQUIREMENTS:\r\n- a [dr]ecent perl interpreter installed\r\n- WebService::Validator::CSS::W3C module installed from CPAN.\r\n","install_details":"Installation is done in two simple steps:\r\n\r\n1) Copy the css.vim compiler file to your vim's compiler folder (usually \/usr\/share\/vim\/vimxx\/compiler)\r\n\r\n2) Copy the `validate_css' perl script to your favourite binary folder (usually \/usr\/local\/bin will do). This folder should be in your $PATH.\r\n\r\nFor the perl script to work, you should have WebService::Validator::CSS:W3C\r\nperl module installed. If you don't have this module installed, the script will prompt you and try to install it automatically from CPAN.\r\nIf this doesn't succeed, try the following command on your shell:\r\n  perl -MCPAN -e 'install WebService::Validator::CSS::W3C'\r\n\r\nIf even this does not work, point your browser to:\r\n  http:\/\/cpan.perl.org\/misc\/cpan-faq.html#How_install_Perl_modules\r\n\r\nand follow the instructions.","5":"Installation is done in two simple steps:\r\n\r\n1) Copy the css.vim compiler file to your vim's compiler folder (usually \/usr\/share\/vim\/vimxx\/compiler)\r\n\r\n2) Copy the `validate_css' perl script to your favourite binary folder (usually \/usr\/local\/bin will do). This folder should be in your $PATH.\r\n\r\nFor the perl script to work, you should have WebService::Validator::CSS:W3C\r\nperl module installed. If you don't have this module installed, the script will prompt you and try to install it automatically from CPAN.\r\nIf this doesn't succeed, try the following command on your shell:\r\n  perl -MCPAN -e 'install WebService::Validator::CSS::W3C'\r\n\r\nIf even this does not work, point your browser to:\r\n  http:\/\/cpan.perl.org\/misc\/cpan-faq.html#How_install_Perl_modules\r\n\r\nand follow the instructions.","first_name":"Cosimo","6":"Cosimo","last_name":"Streppone","7":"Streppone","releases":[{"0":"1577","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"CssValidator-0.1.tar.gz","4":"CssValidator-0.1.tar.gz","src_id":"5842","5":"5842","creation_date":"1150710378","6":"1150710378"}]},"1576":{"script_id":"1576","0":"1576","script_name":"crt.vim","1":"crt.vim","script_type":"color scheme","2":"color scheme","summary":"A colorscheme in the spirit of old crts. Changeable selection of 20 schemes.","3":"A colorscheme in the spirit of old crts. Changeable selection of 20 schemes.","description":"This is a colorscheme with a dark grey background and foreground colors reminiscent of old crts -- yellows, bright greens, ambers, and whites. I find that the colors are easy on the eyes and non-distracting. There are 20 variations that can be changed on the fly. Works with gui, 8, 16+, and 256 color terms (see 256 color xterm). Any preferred variation can be made the default by setting a user-defined variable \"T_CO\" in the vimrc file with a statement like \"let T_CO = 259\". The colors can be changed within vim with \":set t_Co=259\". (259 - looks like a green blackboard.)","4":"This is a colorscheme with a dark grey background and foreground colors reminiscent of old crts -- yellows, bright greens, ambers, and whites. I find that the colors are easy on the eyes and non-distracting. There are 20 variations that can be changed on the fly. Works with gui, 8, 16+, and 256 color terms (see 256 color xterm). Any preferred variation can be made the default by setting a user-defined variable \"T_CO\" in the vimrc file with a statement like \"let T_CO = 259\". The colors can be changed within vim with \":set t_Co=259\". (259 - looks like a green blackboard.)","install_details":"Unzip and put in crt.vim into ~\/.vim\/colors. Add \"colorscheme crt\" to your .vimrc file. My vimrc is included as an example. If you want to use it, rename it to .vimrc and put it into ~\/.","5":"Unzip and put in crt.vim into ~\/.vim\/colors. Add \"colorscheme crt\" to your .vimrc file. My vimrc is included as an example. If you want to use it, rename it to .vimrc and put it into ~\/.","first_name":"Walter","6":"Walter","last_name":"Hutchins","7":"Hutchins","releases":[{"0":"1576","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"crt.zip","4":"crt.zip","src_id":"5841","5":"5841","creation_date":"1150618060","6":"1150618060"}]},"1575":{"script_id":"1575","0":"1575","script_name":"findstr.vim","1":"findstr.vim","script_type":"utility","2":"utility","summary":"Using MS-Windows findstr utility to search for text with Vim","3":"Using MS-Windows findstr utility to search for text with Vim","description":"Overview\r\nThe findstr plugin integrates the MS-Windows findstr search utility with\r\nVim. You can use this plugin to search for a pattern or text in multiple\r\nfiles in the current directory or in a directory tree and easily jump to the\r\nmatches. This plugin is useful only on MS-Windows based systems where the\r\nfindstr utility is available.\r\n\r\nUsage\r\nThe findstr plugin introduces the \":Findstring\", \":Findpattern\",\r\n\":Rfindstr\" and \":Rfindpattern\" Vim commands to search for text and patterns\r\nin files.\r\n\r\nThe \":Findstring\" command is used to search for literal strings in files in\r\nthe current directory. The \":Rfindstring\" command is used to search for a\r\nliteral string in the files in a directory tree.\r\n\r\nThe \":Findpattern\" command is used to search for a regular expression\r\npattern in files in the current directory. The \":Rfindpattern\" command is\r\nused to search for a regular expression pattern in the files in a directory\r\ntree.\r\n\r\nThe syntax of these commands is\r\n\r\n   :Findstring [ <options> ] [ <search_string> [ <file_name(s)> ] ]\r\n   :Findpattern [ <options> ] [ <search_pattern> [ <file_name(s)> ] ]\r\n   :Rfindstring [ <options> ] [ <search_string> [ <file_name(s)> ] ]\r\n   :Rfindpattern [ <options> ] [ <search_pattern> [ <file_name(s)> ] ]\r\n\r\nIn the above commands, all the arguments are optional.\r\n\r\nYou can specify findstr options like \/i (ignore case) to the above command.\r\nIf the <options> are not specified, then the default findstr options\r\nspecified by the variable Findstr_Default_Options is used. Refer to the\r\nfindstr MS-Windows documentation for the command-line options supported by\r\nthe findstr command.\r\n\r\nYou can specify the search text\/pattern as an argument to the above\r\ncommands.  If the <search_pattern> is not specified, then you will be\r\nprompted to enter a search pattern. By default, the keyword under the cursor\r\nis displayed for the search pattern prompt. You can accept the default or\r\nmodify it. The regular expression patterns supported by the findstr command\r\ncan be used in the pattern argument. Refer to the findstr MS-Windows\r\ndocumentation for more information.\r\n\r\nIf you want to specify a search pattern with space characters or a\r\nmulti-word pattern, then you should use the \":Findstring\" command text input\r\nprompt to supply the pattern.\r\n\r\nYou can specify one or more file names (or file patterns) to the above\r\ncommands.  If the <file_names> are not specified, then you will be prompted\r\nto enter file names.  By default, the pattern specified by the\r\nFindstr_Default_Filelist variable is used. To specify the file name(s) as an\r\nargument to the above commands, you have to specify the search pattern also.\r\n\r\nWhen you enter only the command name, you will be prompted to enter the\r\nsearch pattern and the files in which to search for the pattern. By default,\r\nthe keyword under the cursor is displayed for the search pattern prompt.\r\nDepending on the command, you may prompted for additional parameters like\r\nthe directories to search for the pattern.\r\n\r\nYou can retrieve previously entered values for the \":Findstring\" prompts\r\nusing the up and down arrow keys. You can cancel the command by pressing the\r\nescape key.  You can use CTRL-U to erase the default shown for the prompt\r\nand CTRL-W to erase the previous word in the prompt. For more information\r\nabout editing the prompt, read ':help cmdline-editing' Vim help topic.\r\n\r\nYou can cancel the \":Findstring\" command when you are prompted for a search\r\npattern or file names by pressing the <Esc> key. You cannot cancel (or kill)\r\nthe findstr command after the external command is invoked.\r\n\r\nYou can map a key to invoke \":Findstring\". For example, the following map\r\ninvokes the \":Findstring\" command to search for the keyword under the\r\ncursor:\r\n\r\n      nnoremap <silent> <F3> :Findstring<CR>\r\n\r\nThe output of the findstr command will be listed in the Vim quickfix window.\r\n1. You can select a line in the quickfix window and press <Enter> or double\r\n   click on a match to jump to that line.\r\n2. You can use the \":cnext\" and \":cprev\" commands to the jump to the next or\r\n   previous output line.\r\n3. You can use the \":colder\" and \":cnewer\" commands to go between multiple\r\n   findstr quickfix output.\r\n4. The quickfix window need not be opened always to use the findstr output.\r\n   You can close the quickfix window and use the quickfix commands to jump\r\n   to the findstr matches.  Use the \":copen\" command to open the quickfix\r\n   window again.\r\n\r\nFor more information about other quickfix commands read \":help quickfix\"\r\n\r\nConfiguration\r\nBy changing the following variables you can configure the behavior of this\r\nplugin. Set the following variables in your .vimrc file using the 'let'\r\ncommand.\r\n\r\nThe \":Findstring\" command will prompt you for the files in which to search\r\nfor the pattern. The 'Findstr_Default_Filelist' variable is used to specify\r\nto default value for this prompt. By default, this variable is set to '*'.\r\nYou can specify multiple matching patterns separated by spaces. You can\r\nchange this settings using the let command:\r\n\r\n      :let Findstr_Default_Filelist = '*.[chS]'\r\n      :let Findstr_Default_Filelist = '*.c *.cpp *.asm'\r\n\r\nThe 'Findstr_Default_Options' is used to pass default command line options\r\nto the findstr command. By default, this is set to an empty string. You can\r\nchange this using the let command:\r\n\r\n      :let Findstr_Default_Options = '\/i'\r\n\r\nBy default, when you invoke the \":Findstring\" command the quickfix window\r\nwill be opened with the search output.  You can disable opening the quickfix\r\nwindow, by setting the 'Findstr_OpenQuickfixWindow' variable  to zero:\r\n\r\n      :let Findstr_OpenQuickfixWindow = 0\r\n\r\nYou can manually open the quickfix window using the :cwindow command.\r\n","4":"Overview\r\nThe findstr plugin integrates the MS-Windows findstr search utility with\r\nVim. You can use this plugin to search for a pattern or text in multiple\r\nfiles in the current directory or in a directory tree and easily jump to the\r\nmatches. This plugin is useful only on MS-Windows based systems where the\r\nfindstr utility is available.\r\n\r\nUsage\r\nThe findstr plugin introduces the \":Findstring\", \":Findpattern\",\r\n\":Rfindstr\" and \":Rfindpattern\" Vim commands to search for text and patterns\r\nin files.\r\n\r\nThe \":Findstring\" command is used to search for literal strings in files in\r\nthe current directory. The \":Rfindstring\" command is used to search for a\r\nliteral string in the files in a directory tree.\r\n\r\nThe \":Findpattern\" command is used to search for a regular expression\r\npattern in files in the current directory. The \":Rfindpattern\" command is\r\nused to search for a regular expression pattern in the files in a directory\r\ntree.\r\n\r\nThe syntax of these commands is\r\n\r\n   :Findstring [ <options> ] [ <search_string> [ <file_name(s)> ] ]\r\n   :Findpattern [ <options> ] [ <search_pattern> [ <file_name(s)> ] ]\r\n   :Rfindstring [ <options> ] [ <search_string> [ <file_name(s)> ] ]\r\n   :Rfindpattern [ <options> ] [ <search_pattern> [ <file_name(s)> ] ]\r\n\r\nIn the above commands, all the arguments are optional.\r\n\r\nYou can specify findstr options like \/i (ignore case) to the above command.\r\nIf the <options> are not specified, then the default findstr options\r\nspecified by the variable Findstr_Default_Options is used. Refer to the\r\nfindstr MS-Windows documentation for the command-line options supported by\r\nthe findstr command.\r\n\r\nYou can specify the search text\/pattern as an argument to the above\r\ncommands.  If the <search_pattern> is not specified, then you will be\r\nprompted to enter a search pattern. By default, the keyword under the cursor\r\nis displayed for the search pattern prompt. You can accept the default or\r\nmodify it. The regular expression patterns supported by the findstr command\r\ncan be used in the pattern argument. Refer to the findstr MS-Windows\r\ndocumentation for more information.\r\n\r\nIf you want to specify a search pattern with space characters or a\r\nmulti-word pattern, then you should use the \":Findstring\" command text input\r\nprompt to supply the pattern.\r\n\r\nYou can specify one or more file names (or file patterns) to the above\r\ncommands.  If the <file_names> are not specified, then you will be prompted\r\nto enter file names.  By default, the pattern specified by the\r\nFindstr_Default_Filelist variable is used. To specify the file name(s) as an\r\nargument to the above commands, you have to specify the search pattern also.\r\n\r\nWhen you enter only the command name, you will be prompted to enter the\r\nsearch pattern and the files in which to search for the pattern. By default,\r\nthe keyword under the cursor is displayed for the search pattern prompt.\r\nDepending on the command, you may prompted for additional parameters like\r\nthe directories to search for the pattern.\r\n\r\nYou can retrieve previously entered values for the \":Findstring\" prompts\r\nusing the up and down arrow keys. You can cancel the command by pressing the\r\nescape key.  You can use CTRL-U to erase the default shown for the prompt\r\nand CTRL-W to erase the previous word in the prompt. For more information\r\nabout editing the prompt, read ':help cmdline-editing' Vim help topic.\r\n\r\nYou can cancel the \":Findstring\" command when you are prompted for a search\r\npattern or file names by pressing the <Esc> key. You cannot cancel (or kill)\r\nthe findstr command after the external command is invoked.\r\n\r\nYou can map a key to invoke \":Findstring\". For example, the following map\r\ninvokes the \":Findstring\" command to search for the keyword under the\r\ncursor:\r\n\r\n      nnoremap <silent> <F3> :Findstring<CR>\r\n\r\nThe output of the findstr command will be listed in the Vim quickfix window.\r\n1. You can select a line in the quickfix window and press <Enter> or double\r\n   click on a match to jump to that line.\r\n2. You can use the \":cnext\" and \":cprev\" commands to the jump to the next or\r\n   previous output line.\r\n3. You can use the \":colder\" and \":cnewer\" commands to go between multiple\r\n   findstr quickfix output.\r\n4. The quickfix window need not be opened always to use the findstr output.\r\n   You can close the quickfix window and use the quickfix commands to jump\r\n   to the findstr matches.  Use the \":copen\" command to open the quickfix\r\n   window again.\r\n\r\nFor more information about other quickfix commands read \":help quickfix\"\r\n\r\nConfiguration\r\nBy changing the following variables you can configure the behavior of this\r\nplugin. Set the following variables in your .vimrc file using the 'let'\r\ncommand.\r\n\r\nThe \":Findstring\" command will prompt you for the files in which to search\r\nfor the pattern. The 'Findstr_Default_Filelist' variable is used to specify\r\nto default value for this prompt. By default, this variable is set to '*'.\r\nYou can specify multiple matching patterns separated by spaces. You can\r\nchange this settings using the let command:\r\n\r\n      :let Findstr_Default_Filelist = '*.[chS]'\r\n      :let Findstr_Default_Filelist = '*.c *.cpp *.asm'\r\n\r\nThe 'Findstr_Default_Options' is used to pass default command line options\r\nto the findstr command. By default, this is set to an empty string. You can\r\nchange this using the let command:\r\n\r\n      :let Findstr_Default_Options = '\/i'\r\n\r\nBy default, when you invoke the \":Findstring\" command the quickfix window\r\nwill be opened with the search output.  You can disable opening the quickfix\r\nwindow, by setting the 'Findstr_OpenQuickfixWindow' variable  to zero:\r\n\r\n      :let Findstr_OpenQuickfixWindow = 0\r\n\r\nYou can manually open the quickfix window using the :cwindow command.\r\n","install_details":"1. Copy the findstr.vim file to the $HOME\/vimfiles\/plugin or\r\n   $VIM\/vimfiles\/plugin directory. \r\n   Refer to the following Vim help topics for more information about Vim\r\n   plugins:\r\n      :help add-plugin\r\n      :help add-global-plugin\r\n      :help runtimepath\r\n2. Restart Vim.\r\n3. You can now use the \":Findstring\" or \":Findpattern\" command to search for\r\n   text\/patterns in files.\r\n","5":"1. Copy the findstr.vim file to the $HOME\/vimfiles\/plugin or\r\n   $VIM\/vimfiles\/plugin directory. \r\n   Refer to the following Vim help topics for more information about Vim\r\n   plugins:\r\n      :help add-plugin\r\n      :help add-global-plugin\r\n      :help runtimepath\r\n2. Restart Vim.\r\n3. You can now use the \":Findstring\" or \":Findpattern\" command to search for\r\n   text\/patterns in files.\r\n","first_name":"Yegappan","6":"Yegappan","last_name":"Lakshmanan","7":"Lakshmanan","releases":[{"0":"1575","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"findstr.vim","4":"findstr.vim","src_id":"5839","5":"5839","creation_date":"1150484090","6":"1150484090"}]},"1574":{"script_id":"1574","0":"1574","script_name":"settlemyer.vim","1":"settlemyer.vim","script_type":"color scheme","2":"color scheme","summary":"A skyblue\/darkgrey\/spring green color scheme with a dark background.(screenshot)","3":"A skyblue\/darkgrey\/spring green color scheme with a dark background.(screenshot)","description":"This is my first gvim color scheme and it has been adapted from a wonderful .emacs file I found online by someone named Brad Settlemyer (http:\/\/deepcopy.org\/emacs\/dotemacs).  Since I moved to vim I had been looking for a theme like this and I couldn't find one so I tried my best to re-create it.\r\n\r\nYou can find a screenshot on the color scheme list here:\r\nhttp:\/\/www.cs.cmu.edu\/~maverick\/VimColorSchemeTest\/index-c.html\r\n","4":"This is my first gvim color scheme and it has been adapted from a wonderful .emacs file I found online by someone named Brad Settlemyer (http:\/\/deepcopy.org\/emacs\/dotemacs).  Since I moved to vim I had been looking for a theme like this and I couldn't find one so I tried my best to re-create it.\r\n\r\nYou can find a screenshot on the color scheme list here:\r\nhttp:\/\/www.cs.cmu.edu\/~maverick\/VimColorSchemeTest\/index-c.html\r\n","install_details":"Place in your vim colors directory.","5":"Place in your vim colors directory.","first_name":"Frank","6":"Frank","last_name":"Rizzo","7":"Rizzo","releases":[{"0":"1574","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"settlemyer.vim","4":"settlemyer.vim","src_id":"5835","5":"5835","creation_date":"1150381653","6":"1150381653"}]},"1573":{"script_id":"1573","0":"1573","script_name":"systemverilog.vim","1":"systemverilog.vim","script_type":"syntax","2":"syntax","summary":"SystemVerilog syntax highlighting","3":"SystemVerilog syntax highlighting","description":"Since there didn't seem to be a SystemVerilog syntax file yet for Vim, I wrote this.\r\nIt's based on the existing Verilog mode from Vim 6.3.\r\nAll language keywords are defined, as are most builtin method\/task\/function names.","4":"Since there didn't seem to be a SystemVerilog syntax file yet for Vim, I wrote this.\r\nIt's based on the existing Verilog mode from Vim 6.3.\r\nAll language keywords are defined, as are most builtin method\/task\/function names.","install_details":"Put it in your runtime directory as per normal syntax files.\r\nI use the following ~\/.vim\/filetype.vim to make it recognise any *.sv file as systemVerilog.\r\n\r\naugroup filetypedetect\r\nau BufNewFile,BufRead *.sv      setf systemverilog\r\naugroup END\r\n","5":"Put it in your runtime directory as per normal syntax files.\r\nI use the following ~\/.vim\/filetype.vim to make it recognise any *.sv file as systemVerilog.\r\n\r\naugroup filetypedetect\r\nau BufNewFile,BufRead *.sv      setf systemverilog\r\naugroup END\r\n","first_name":"Stephen","6":"Stephen","last_name":"Hobbs","7":"Hobbs","releases":[{"0":"1573","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"systemverilog.vim","4":"systemverilog.vim","src_id":"5834","5":"5834","creation_date":"1150352011","6":"1150352011"}]},"1572":{"script_id":"1572","0":"1572","script_name":"SQLComplete.vim","1":"SQLComplete.vim","script_type":"utility","2":"utility","summary":"SQLComplete is a SQL code completion system using the omnifunc framework","3":"SQLComplete is a SQL code completion system using the omnifunc framework","description":"SQLComplete.vim is a plugin which uses the new Vim7 OMNI completion features (intellisense code completion).\r\n\r\nSQLComplete.vim version  4.0 is included in the Vim 7.0 release.\r\nSQLComplete.vim version  5.0 is included in the Vim 7.1 release.\r\nSQLComplete.vim version  6.0 is included in the Vim 7.2 release.\r\nSQLComplete.vim version  9.0 is included in the Vim 7.3 release.\r\nSQLComplete.vim version 10.0 is included in the Vim 7.3 release.\r\nSQLComplete.vim version 11.0 is included in the Vim 7.3 release.\r\nSQLComplete.vim version 12.0 is included in the Vim 7.3 release.\r\nSQLComplete.vim version 13.0 is included in the Vim 7.3 release.\r\nSQLComplete.vim version 14.0 is included in the Vim 7.3 release.\r\nSQLComplete.vim version 15.0 is included in the Vim 7.3 release.\r\n\r\nWhat does it do:\r\n-----------------------\r\nCompletion for the SQL language includes statements, functions, keywords, operators and database options which it draws from the current SQL syntax file in use.  Vim ships with 9 different SQL syntax files (Oracle, Informix, MySQL, SQL Anywhere, ...).  You can choose different SQL dialects using the command  (see :h sql-dialects):\r\n:SQLSetType sqlanywhere\r\n:SQLSetType <Tab> will cycle through the installed dialects.\r\n\r\nIt will also dynamically complete tables, procedures, views and column lists with data pulled directly from a database.  It does this in conjunction with the dbext.vim \"vimscript #356\".  For detailed instructions and a tutorial see :h omni-sql-completion.\r\n\r\nExisting instructions can be found within Vim7 using \r\n:h sql.txt\r\n:h sql-completion\r\n\r\nThis plugin is new to Vim7.  Improvements to the script will be uploaded here, and supplied to Bram for inclusion into future versions of Vim7.\r\n","4":"SQLComplete.vim is a plugin which uses the new Vim7 OMNI completion features (intellisense code completion).\r\n\r\nSQLComplete.vim version  4.0 is included in the Vim 7.0 release.\r\nSQLComplete.vim version  5.0 is included in the Vim 7.1 release.\r\nSQLComplete.vim version  6.0 is included in the Vim 7.2 release.\r\nSQLComplete.vim version  9.0 is included in the Vim 7.3 release.\r\nSQLComplete.vim version 10.0 is included in the Vim 7.3 release.\r\nSQLComplete.vim version 11.0 is included in the Vim 7.3 release.\r\nSQLComplete.vim version 12.0 is included in the Vim 7.3 release.\r\nSQLComplete.vim version 13.0 is included in the Vim 7.3 release.\r\nSQLComplete.vim version 14.0 is included in the Vim 7.3 release.\r\nSQLComplete.vim version 15.0 is included in the Vim 7.3 release.\r\n\r\nWhat does it do:\r\n-----------------------\r\nCompletion for the SQL language includes statements, functions, keywords, operators and database options which it draws from the current SQL syntax file in use.  Vim ships with 9 different SQL syntax files (Oracle, Informix, MySQL, SQL Anywhere, ...).  You can choose different SQL dialects using the command  (see :h sql-dialects):\r\n:SQLSetType sqlanywhere\r\n:SQLSetType <Tab> will cycle through the installed dialects.\r\n\r\nIt will also dynamically complete tables, procedures, views and column lists with data pulled directly from a database.  It does this in conjunction with the dbext.vim \"vimscript #356\".  For detailed instructions and a tutorial see :h omni-sql-completion.\r\n\r\nExisting instructions can be found within Vim7 using \r\n:h sql.txt\r\n:h sql-completion\r\n\r\nThis plugin is new to Vim7.  Improvements to the script will be uploaded here, and supplied to Bram for inclusion into future versions of Vim7.\r\n","install_details":"Copy sqlcomplete.vim to:\r\n.vim\/autoload\/sqlcomplete.vim (Unix)\r\nvimfiles\\autoload\\sqlcomplete.vim (Windows)\r\n\r\nFor documentation:\r\n:h sql.txt ","5":"Copy sqlcomplete.vim to:\r\n.vim\/autoload\/sqlcomplete.vim (Unix)\r\nvimfiles\\autoload\\sqlcomplete.vim (Windows)\r\n\r\nFor documentation:\r\n:h sql.txt ","first_name":"David","6":"David","last_name":"Fishburn","7":"Fishburn","releases":[{"0":"1572","vim_version":"7.0","1":"7.0","script_version":"15.0","2":"15.0","version_comment":"New Features\r\n-------------------\r\nChanged the SQL precached syntax items, omni_sql_precache_syntax_groups, to use regular expressions to pick up extended syntax group names.  This requires an updated SyntaxComplete plugin version 13.0 (uploaded separately).\r\n\r\nIf the required versions have not been installed, previous behaviour will not be impacted.\r\n                                                                               \r\nBug Fixes\r\n--------------\r\n- Added check for cpoptions (cpo).\r\n","3":"New Features\r\n-------------------\r\nChanged the SQL precached syntax items, omni_sql_precache_syntax_groups, to use regular expressions to pick up extended syntax group names.  This requires an updated SyntaxComplete plugin version 13.0 (uploaded separately).\r\n\r\nIf the required versions have not been installed, previous behaviour will not be impacted.\r\n                                                                               \r\nBug Fixes\r\n--------------\r\n- Added check for cpoptions (cpo).\r\n","package":"sqlcomplete.vim","4":"sqlcomplete.vim","src_id":"20271","5":"20271","creation_date":"1370209820","6":"1370209820"},{"0":"1572","vim_version":"7.0","1":"7.0","script_version":"13.0","2":"13.0","version_comment":"New Features\r\n-------------------\r\n- When completing column lists or drilling into a table and g:omni_sql_include_owner is enabled, the only the table name would be replaced with the column list instead of the table name and owner (if specified).\r\n\r\n- When completing column lists using table aliases and g:omni_sql_include_owner is enabled, account for the owner name when looking up the table list instead of the table name and owner (if specified).\r\n\r\nBug Fixes\r\n-------------\r\n- When completing column lists or drilling into a table and g:omni_sql_include_owner is enabled, the column list could often not be found for the table.\r\n\r\n- When OMNI popped up, possibly the wrong word would be replaced for column and column list options.\r\n\r\n","3":"New Features\r\n-------------------\r\n- When completing column lists or drilling into a table and g:omni_sql_include_owner is enabled, the only the table name would be replaced with the column list instead of the table name and owner (if specified).\r\n\r\n- When completing column lists using table aliases and g:omni_sql_include_owner is enabled, account for the owner name when looking up the table list instead of the table name and owner (if specified).\r\n\r\nBug Fixes\r\n-------------\r\n- When completing column lists or drilling into a table and g:omni_sql_include_owner is enabled, the column list could often not be found for the table.\r\n\r\n- When OMNI popped up, possibly the wrong word would be replaced for column and column list options.\r\n\r\n","package":"sqlcomplete.vim","4":"sqlcomplete.vim","src_id":"18832","5":"18832","creation_date":"1350520360","6":"1350520360"},{"0":"1572","vim_version":"7.0","1":"7.0","script_version":"12.0","2":"12.0","version_comment":"New Features\r\n-------------------\r\n- Improved the handling of column completion.  First we match any columns from a previous completion.  If not matches are found, we consider the partial name to be a table or table alias for the query and attempt to match on it.\r\n\r\nBug Fixes\r\n--------------\r\n- Partial column name completion did not work when a table name or table alias was provided (Jonas Enberg).\r\n","3":"New Features\r\n-------------------\r\n- Improved the handling of column completion.  First we match any columns from a previous completion.  If not matches are found, we consider the partial name to be a table or table alias for the query and attempt to match on it.\r\n\r\nBug Fixes\r\n--------------\r\n- Partial column name completion did not work when a table name or table alias was provided (Jonas Enberg).\r\n","package":"sqlcomplete.vim","4":"sqlcomplete.vim","src_id":"17506","5":"17506","creation_date":"1329789548","6":"1329789548"},{"0":"1572","vim_version":"7.0","1":"7.0","script_version":"11.0","2":"11.0","version_comment":"Version 11.0\r\n    Added g:omni_sql_default_compl_type variable\r\n        - You can specify which type of completion to default to \r\n          when pressing <C-X><C-O>.  The entire list of available\r\n          choices can be found in the calls to sqlcomplete#Map in:\r\n              ftplugin\/sql.vim\r\n                                                                             \r\nVersion 10.0\r\n    Updated PreCacheSyntax() \r\n        - Now returns a List of the syntax items it finds.\r\n          This allows other plugins \/ scripts to use this list for their own\r\n          purposes.  In this case XPTemplate can use them for a Choose list.\r\n        - Verifies the parameters are the correct type and displays a\r\n          warning if not.\r\n        - Verifies the parameters are the correct type and displays a\r\n          warning if not.\r\n    Updated SQLCWarningMsg() \r\n        - Prepends warning message with SQLComplete so you know who issued\r\n          the warning.\r\n    Updated SQLCErrorMsg() \r\n        - Prepends error message with SQLComplete so you know who issued\r\n          the error.\r\n","3":"Version 11.0\r\n    Added g:omni_sql_default_compl_type variable\r\n        - You can specify which type of completion to default to \r\n          when pressing <C-X><C-O>.  The entire list of available\r\n          choices can be found in the calls to sqlcomplete#Map in:\r\n              ftplugin\/sql.vim\r\n                                                                             \r\nVersion 10.0\r\n    Updated PreCacheSyntax() \r\n        - Now returns a List of the syntax items it finds.\r\n          This allows other plugins \/ scripts to use this list for their own\r\n          purposes.  In this case XPTemplate can use them for a Choose list.\r\n        - Verifies the parameters are the correct type and displays a\r\n          warning if not.\r\n        - Verifies the parameters are the correct type and displays a\r\n          warning if not.\r\n    Updated SQLCWarningMsg() \r\n        - Prepends warning message with SQLComplete so you know who issued\r\n          the warning.\r\n    Updated SQLCErrorMsg() \r\n        - Prepends error message with SQLComplete so you know who issued\r\n          the error.\r\n","package":"sqlcomplete.vim","4":"sqlcomplete.vim","src_id":"17323","5":"17323","creation_date":"1327728005","6":"1327728005"},{"0":"1572","vim_version":"7.0","1":"7.0","script_version":"9.0","2":"9.0","version_comment":"Version 9.0\r\n- This change removes some of the support for tables with spaces in their names in order to simplify the regexes used to pull out query table aliases for more robust table name and column name code completion.\r\n- Full support for \"table names with spaces\" can be added in again after 7.3.\r\n\r\nVersion 8.0\r\n- Incorrectly re-executed the g:ftplugin_sql_omni_key_right and :ftplugin_sql_omni_key_left  when drilling in and out of a column list for a table.\r\n","3":"Version 9.0\r\n- This change removes some of the support for tables with spaces in their names in order to simplify the regexes used to pull out query table aliases for more robust table name and column name code completion.\r\n- Full support for \"table names with spaces\" can be added in again after 7.3.\r\n\r\nVersion 8.0\r\n- Incorrectly re-executed the g:ftplugin_sql_omni_key_right and :ftplugin_sql_omni_key_left  when drilling in and out of a column list for a table.\r\n","package":"sqlcomplete.vim","4":"sqlcomplete.vim","src_id":"13001","5":"13001","creation_date":"1273773907","6":"1273773907"},{"0":"1572","vim_version":"7.0","1":"7.0","script_version":"7.0","2":"7.0","version_comment":"Version 6.0 added support for table names which had \"spaces in them\".  Unforunately, this broke a few things in the parsing of statements to determine which table to retrieve column names.  This version corrects those mistakes and makes the object names a bit more robust.\r\n","3":"Version 6.0 added support for table names which had \"spaces in them\".  Unforunately, this broke a few things in the parsing of statements to determine which table to retrieve column names.  This version corrects those mistakes and makes the object names a bit more robust.\r\n","package":"sqlcomplete.vim","4":"sqlcomplete.vim","src_id":"12182","5":"12182","creation_date":"1264445936","6":"1264445936"},{"0":"1572","vim_version":"6.0","1":"6.0","script_version":"6.0","2":"6.0","version_comment":"This release is in conjunction with the dbext.vim 6.0 release.  It adds SQL completion support of objects which contain spaces \"my table\".","3":"This release is in conjunction with the dbext.vim 6.0 release.  It adds SQL completion support of objects which contain spaces \"my table\".","package":"sqlcomplete.vim","4":"sqlcomplete.vim","src_id":"8616","5":"8616","creation_date":"1209400926","6":"1209400926"},{"0":"1572","vim_version":"7.0","1":"7.0","script_version":"5.0","2":"5.0","version_comment":"Initial upload","3":"Initial upload","package":"sqlcomplete.vim","4":"sqlcomplete.vim","src_id":"5821","5":"5821","creation_date":"1149843382","6":"1149843382"}]},"1571":{"script_id":"1571","0":"1571","script_name":"php.vim","1":"php.vim","script_type":"syntax","2":"syntax","summary":"PHP Syntax","3":"PHP Syntax","description":"PHP syntax file, with several bug fixes, improvements and additions.  Should be up-to-date with all features of PHP 5.1.4.  If anything is missing, broken, not working well on your setup, or an inconvenience for you, please let me know, all feedback is welcome: <toomuchphp-vim at yahoo.com>.\r\n\r\n\r\nNew and improved highlighting features include:\r\n===============================================\r\n\r\n- User-defined special functions (__autoload(), __construct(), etc)\r\n- Built-in constants (STDIN, STR_PAD_LEFT, etc)\r\n- Built-in classes (stdClass, Exception, Reflection, etc)\r\n- Built-in interfaces (Iterator, Serializable, etc)\r\n- Complex expressions inside double-quoted strings using { }\r\n- Support for PCRE patterns\r\n  (Patterns are only recognized if the pattern is inside the\r\n  function call.)\r\n- Braces are colored to help you see when they are mismatched.\r\n\r\n\r\n* You can find a complete list of available options near the top of the syntax file.\r\n\r\n* Release 0.9 is the official 'stable' release, however I do encourage you to use the latest version as it shouldn't have any bugs either.","4":"PHP syntax file, with several bug fixes, improvements and additions.  Should be up-to-date with all features of PHP 5.1.4.  If anything is missing, broken, not working well on your setup, or an inconvenience for you, please let me know, all feedback is welcome: <toomuchphp-vim at yahoo.com>.\r\n\r\n\r\nNew and improved highlighting features include:\r\n===============================================\r\n\r\n- User-defined special functions (__autoload(), __construct(), etc)\r\n- Built-in constants (STDIN, STR_PAD_LEFT, etc)\r\n- Built-in classes (stdClass, Exception, Reflection, etc)\r\n- Built-in interfaces (Iterator, Serializable, etc)\r\n- Complex expressions inside double-quoted strings using { }\r\n- Support for PCRE patterns\r\n  (Patterns are only recognized if the pattern is inside the\r\n  function call.)\r\n- Braces are colored to help you see when they are mismatched.\r\n\r\n\r\n* You can find a complete list of available options near the top of the syntax file.\r\n\r\n* Release 0.9 is the official 'stable' release, however I do encourage you to use the latest version as it shouldn't have any bugs either.","install_details":"Copy php.vim to:\r\n  ~\/.vim\/syntax\/php.vim\r\n    or\r\n  c:\\program files\\vim\\vimfiles\\syntax\\php.vim","5":"Copy php.vim to:\r\n  ~\/.vim\/syntax\/php.vim\r\n    or\r\n  c:\\program files\\vim\\vimfiles\\syntax\\php.vim","first_name":"Peter","6":"Peter","last_name":"Hodge","7":"Hodge","releases":[{"0":"1571","vim_version":"6.0","1":"6.0","script_version":"0.9.7","2":"0.9.7","version_comment":"Many small bug fixes and improvements","3":"Many small bug fixes and improvements","package":"php.tar.gz","4":"php.tar.gz","src_id":"8651","5":"8651","creation_date":"1210085452","6":"1210085452"},{"0":"1571","vim_version":"6.0","1":"6.0","script_version":"0.9.6","2":"0.9.6","version_comment":"Highlights ';' errors in many more places, can now fold array() structures as well.","3":"Highlights ';' errors in many more places, can now fold array() structures as well.","package":"php.tar.gz","4":"php.tar.gz","src_id":"6341","5":"6341","creation_date":"1161917218","6":"1161917218"},{"0":"1571","vim_version":"6.0","1":"6.0","script_version":"0.9.5","2":"0.9.5","version_comment":"New colors for { } around class\/function\/try\/catch code blocks.  Better errors when a brace or semicolon is out of place.  Options can be configured globally or separately for each buffer.","3":"New colors for { } around class\/function\/try\/catch code blocks.  Better errors when a brace or semicolon is out of place.  Options can be configured globally or separately for each buffer.","package":"php.tar.gz","4":"php.tar.gz","src_id":"6326","5":"6326","creation_date":"1161627384","6":"1161627384"},{"0":"1571","vim_version":"6.0","1":"6.0","script_version":"0.9.4","2":"0.9.4","version_comment":"Now supports multi-line patterns and double-quoted patterns (but no variable substitution yet)","3":"Now supports multi-line patterns and double-quoted patterns (but no variable substitution yet)","package":"php.tar.gz","4":"php.tar.gz","src_id":"6046","5":"6046","creation_date":"1154909402","6":"1154909402"},{"0":"1571","vim_version":"6.0","1":"6.0","script_version":"0.9.3","2":"0.9.3","version_comment":"Improved support for PCRE patterns, fixed variable substituion in strings, added option to highlight '->' in an alternate color when used for object properties.","3":"Improved support for PCRE patterns, fixed variable substituion in strings, added option to highlight '->' in an alternate color when used for object properties.","package":"php.tar.gz","4":"php.tar.gz","src_id":"5976","5":"5976","creation_date":"1153431591","6":"1153431591"},{"0":"1571","vim_version":"6.0","1":"6.0","script_version":"0.9.2","2":"0.9.2","version_comment":"Improved support for preg* functions, added support for most built-in constants","3":"Improved support for preg* functions, added support for most built-in constants","package":"syntax.tar.gz","4":"syntax.tar.gz","src_id":"5861","5":"5861","creation_date":"1151254458","6":"1151254458"},{"0":"1571","vim_version":"6.0","1":"6.0","script_version":"0.9.1","2":"0.9.1","version_comment":"Alpha support for regular expressions inside preg_*() functions, plus some very minor additions.","3":"Alpha support for regular expressions inside preg_*() functions, plus some very minor additions.","package":"syntax.tar.gz","4":"syntax.tar.gz","src_id":"5836","5":"5836","creation_date":"1150392134","6":"1150392134"},{"0":"1571","vim_version":"6.0","1":"6.0","script_version":"0.9","2":"0.9","version_comment":"Initial upload","3":"Initial upload","package":"php.vim","4":"php.vim","src_id":"5816","5":"5816","creation_date":"1149786937","6":"1149786937"}]},"1570":{"script_id":"1570","0":"1570","script_name":"redstring.vim","1":"redstring.vim","script_type":"color scheme","2":"color scheme","summary":"Dark background colorscheme designed for console and Gui.","3":"Dark background colorscheme designed for console and Gui.","description":"This colorscheme combines some of the ideas from the colorschemes darkzen vimscript #1402 and understated vimscript #1405.  It colors comments in a dark grey so that they don't distract you from seeing the code, but they are there if you need them. It should look similar in both console and Gui.  It looks really good for Python and Javascript, and hopefully will look good for other languages.","4":"This colorscheme combines some of the ideas from the colorschemes darkzen vimscript #1402 and understated vimscript #1405.  It colors comments in a dark grey so that they don't distract you from seeing the code, but they are there if you need them. It should look similar in both console and Gui.  It looks really good for Python and Javascript, and hopefully will look good for other languages.","install_details":"copy file to your colors directory or into your .vim\/colors directory if you have one.","5":"copy file to your colors directory or into your .vim\/colors directory if you have one.","first_name":"Connor","6":"Connor","last_name":"Berry","7":"Berry","releases":[{"0":"1570","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"redstring.vim","4":"redstring.vim","src_id":"5807","5":"5807","creation_date":"1149615122","6":"1149615122"}]},"1569":{"script_id":"1569","0":"1569","script_name":"montz.vim","1":"montz.vim","script_type":"color scheme","2":"color scheme","summary":"Port of montz color-theme from Emacs.","3":"Port of montz color-theme from Emacs.","description":"This is a close approximation of the Montz color theme from Emacs.\r\nBackground is grey\/white.  Colors should be similar in console and Gui.\r\n\r\n","4":"This is a close approximation of the Montz color theme from Emacs.\r\nBackground is grey\/white.  Colors should be similar in console and Gui.\r\n\r\n","install_details":"Just drop it into your colors directory or into your .vim\/colors directory if you have one.","5":"Just drop it into your colors directory or into your .vim\/colors directory if you have one.","first_name":"Connor","6":"Connor","last_name":"Berry","7":"Berry","releases":[{"0":"1569","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"montz.vim","4":"montz.vim","src_id":"5806","5":"5806","creation_date":"1149613209","6":"1149613209"}]},"1568":{"script_id":"1568","0":"1568","script_name":"abnf","1":"abnf","script_type":"syntax","2":"syntax","summary":"Initial Augmented BNF syntax script","3":"Initial Augmented BNF syntax script","description":"Provides basic ABNF syntax highlighting, modeled closely after the excellent BNF syntax script by Michael Brailsford. All errors are my responsibility, however.\r\n\r\nI welcome feedback, comments or a new owner for this script. :-)","4":"Provides basic ABNF syntax highlighting, modeled closely after the excellent BNF syntax script by Michael Brailsford. All errors are my responsibility, however.\r\n\r\nI welcome feedback, comments or a new owner for this script. :-)","install_details":"","5":"","first_name":"Matthew","6":"Matthew","last_name":"Daniel","7":"Daniel","releases":[{"0":"1568","vim_version":"6.0","1":"6.0","script_version":"1.0.1","2":"1.0.1","version_comment":"Added support for marking extraneous whitespace not followed by an element. Since (sigh) ABNF seems to be whitespace sensitive, that could be a problem.\r\n\r\nAdded support for marking comments which are not part of a rule (i.e. at the beginning of a file).\r\n\r\nBoth of these new features may be enabled or disabled according to your preference.\r\n\r\nThe whitespace matching is enabled by default, but may be disabled via {{{let abnf_ignore_whitespace=1}}}.\r\n\r\nThe comments thing is disabled by default and may be enabled via {{{let abnf_strict=1}}}","3":"Added support for marking extraneous whitespace not followed by an element. Since (sigh) ABNF seems to be whitespace sensitive, that could be a problem.\r\n\r\nAdded support for marking comments which are not part of a rule (i.e. at the beginning of a file).\r\n\r\nBoth of these new features may be enabled or disabled according to your preference.\r\n\r\nThe whitespace matching is enabled by default, but may be disabled via {{{let abnf_ignore_whitespace=1}}}.\r\n\r\nThe comments thing is disabled by default and may be enabled via {{{let abnf_strict=1}}}","package":"abnf.vim","4":"abnf.vim","src_id":"5805","5":"5805","creation_date":"1149581782","6":"1149581782"},{"0":"1568","vim_version":"6.0","1":"6.0","script_version":"1.0.0","2":"1.0.0","version_comment":"Initial upload","3":"Initial upload","package":"abnf.vim","4":"abnf.vim","src_id":"5799","5":"5799","creation_date":"1149434514","6":"1149434514"}]},"1567":{"script_id":"1567","0":"1567","script_name":"rails.vim","1":"rails.vim","script_type":"utility","2":"utility","summary":"Ruby on Rails: easy file navigation, enhanced syntax highlighting, and more","3":"Ruby on Rails: easy file navigation, enhanced syntax highlighting, and more","description":"This is a massive (in a good way) Vim plugin for editing Ruby on Rails applications.\r\n\r\n* Easy navigation of the Rails directory structure.  gf considers context and knows about partials, fixtures, and much more.  There are two commands, :A (alternate) and :R (related) for easy jumping between files, including favorites like model to schema, template to helper, and controller to functional test.  Commands like :Emodel, :Eview, :Econtroller, are provided to :edit files by type, along with S, V, and T variants for :split, :vsplit, and :tabedit.  Throw a bang on the end (:Emodel foo!) to automatically create the file with the standard boilerplate if it doesn't exist.  :help rails-navigation\r\n\r\n* Enhanced syntax highlighting.  From has_and_belongs_to_many to distance_of_time_in_words, it's here.\r\n\r\n* Interface to the rails command.  Generally, use :Rails console to call rails console.  Many commands have wrappers with additional features: :Generate controller Blog generates a blog controller and loads the generated files into the quickfix list, and :Runner wraps rails runner and doubles as a direct test runner.  :help rails-exec\r\n\r\n* Default task runner.  Use :Rails (with no arguments) to run the current test, spec, or feature.  Use :.Rails to do a focused run of just the method, example, or scenario on the current line.  :Rails can also run arbitrary migrations, load individual fixtures, and more.  :help rails-default-task\r\n\r\n* Partial and concern extraction.  In a view, :Rextract {file} replaces the desired range (typically selected in visual line mode) with render '{file}', which is automatically created with your content.  In a model or controller, a concern is created, with the appropriate include declaration left behind.  :help rails-:Rextract\r\n\r\n* Fully customizable. Define \"projections\" at the global, app, or gem level to define navigation commands and override the alternate file, default rake task, syntax highlighting, abbreviations, and more.  :help rails-projections.\r\n\r\n* Integration with other plugins.  If dbext.vim is installed, it will be transparently configured to reflect database.yml.  Users of abolish.vim get pluralize and tableize coercions, and users of bundler.vim get a smattering of features.  :help rails-integration\r\n\r\nIf you like rails.vim and use Git, please Watch the repository on Github at http:\/\/github.com\/tpope\/vim-rails, and try my Git wrapper fugitive.vim: vimscript #2975 http:\/\/github.com\/tpope\/vim-fugitive","4":"This is a massive (in a good way) Vim plugin for editing Ruby on Rails applications.\r\n\r\n* Easy navigation of the Rails directory structure.  gf considers context and knows about partials, fixtures, and much more.  There are two commands, :A (alternate) and :R (related) for easy jumping between files, including favorites like model to schema, template to helper, and controller to functional test.  Commands like :Emodel, :Eview, :Econtroller, are provided to :edit files by type, along with S, V, and T variants for :split, :vsplit, and :tabedit.  Throw a bang on the end (:Emodel foo!) to automatically create the file with the standard boilerplate if it doesn't exist.  :help rails-navigation\r\n\r\n* Enhanced syntax highlighting.  From has_and_belongs_to_many to distance_of_time_in_words, it's here.\r\n\r\n* Interface to the rails command.  Generally, use :Rails console to call rails console.  Many commands have wrappers with additional features: :Generate controller Blog generates a blog controller and loads the generated files into the quickfix list, and :Runner wraps rails runner and doubles as a direct test runner.  :help rails-exec\r\n\r\n* Default task runner.  Use :Rails (with no arguments) to run the current test, spec, or feature.  Use :.Rails to do a focused run of just the method, example, or scenario on the current line.  :Rails can also run arbitrary migrations, load individual fixtures, and more.  :help rails-default-task\r\n\r\n* Partial and concern extraction.  In a view, :Rextract {file} replaces the desired range (typically selected in visual line mode) with render '{file}', which is automatically created with your content.  In a model or controller, a concern is created, with the appropriate include declaration left behind.  :help rails-:Rextract\r\n\r\n* Fully customizable. Define \"projections\" at the global, app, or gem level to define navigation commands and override the alternate file, default rake task, syntax highlighting, abbreviations, and more.  :help rails-projections.\r\n\r\n* Integration with other plugins.  If dbext.vim is installed, it will be transparently configured to reflect database.yml.  Users of abolish.vim get pluralize and tableize coercions, and users of bundler.vim get a smattering of features.  :help rails-integration\r\n\r\nIf you like rails.vim and use Git, please Watch the repository on Github at http:\/\/github.com\/tpope\/vim-rails, and try my Git wrapper fugitive.vim: vimscript #2975 http:\/\/github.com\/tpope\/vim-fugitive","install_details":"Extract the zip file to ~\/.vim (or vimfiles on Windows).  To use the help, see :help add-local-help.  In a nutshell, :helptags ~\/.vim\/doc.\r\n\r\nFor details, see :help rails","5":"Extract the zip file to ~\/.vim (or vimfiles on Windows).  To use the help, see :help add-local-help.  In a nutshell, :helptags ~\/.vim\/doc.\r\n\r\nFor details, see :help rails","first_name":"Tim","6":"Tim","last_name":"Pope","7":"Pope","releases":[{"0":"1567","vim_version":"7.0","1":"7.0","script_version":"5.4","2":"5.4","version_comment":"Fix issues with :Eview.\r\nFix :Clog.\r\nFix file creation on :confirm A.\r\nFix working directory in :Generate.\r\nFix :Rails g and other abbreviated commands on pre-5 Rails.","3":"Fix issues with :Eview.\r\nFix :Clog.\r\nFix file creation on :confirm A.\r\nFix working directory in :Generate.\r\nFix :Rails g and other abbreviated commands on pre-5 Rails.","package":"rails.zip","4":"rails.zip","src_id":"25852","5":"25852","creation_date":"1520131947","6":"1520131947"},{"0":"1567","vim_version":"7.0","1":"7.0","script_version":"5.3","2":"5.3","version_comment":"Massive gf rewrite for better extensibility.\r\nGreatly improved asset support.\r\nProvide command line <C-R><C-F> with same logic as gf.\r\nSupport Rails 5 rails\/rake unification.\r\nSelectively delegate :Rails to rake on older Rails versions.\r\n:Rails supersedes :Rake as default task dispatcher.\r\nAdd channel and serializer support.\r\nSupport tab\/vert style mods on Vim 8.\r\nProvide :Clog to load logs into quickfix list.\r\nUpdate syntax highlighting for Rails 5.1.\r\nUse filetype=eruby.yaml for yaml files.\r\nRefactor to use projections for much of internal implementation.\r\nEnable :Econtroller to edit controller concerns.\r\nRearrange and clean up help.\r\nDrop legacy (non asset pipeline) Less CSS and CoffeeScript support.\r\nFormally deprecate R commands.","3":"Massive gf rewrite for better extensibility.\r\nGreatly improved asset support.\r\nProvide command line <C-R><C-F> with same logic as gf.\r\nSupport Rails 5 rails\/rake unification.\r\nSelectively delegate :Rails to rake on older Rails versions.\r\n:Rails supersedes :Rake as default task dispatcher.\r\nAdd channel and serializer support.\r\nSupport tab\/vert style mods on Vim 8.\r\nProvide :Clog to load logs into quickfix list.\r\nUpdate syntax highlighting for Rails 5.1.\r\nUse filetype=eruby.yaml for yaml files.\r\nRefactor to use projections for much of internal implementation.\r\nEnable :Econtroller to edit controller concerns.\r\nRearrange and clean up help.\r\nDrop legacy (non asset pipeline) Less CSS and CoffeeScript support.\r\nFormally deprecate R commands.","package":"rails.zip","4":"rails.zip","src_id":"25295","5":"25295","creation_date":"1496961965","6":"1496961965"},{"0":"1567","vim_version":"7.0","1":"7.0","script_version":"5.2","2":"5.2","version_comment":"Add rails compiler plugin and use it for :Rails, :Rake, and :make.\r\nProvide dispatch.vim configuration.\r\nSupport projectionist.vim compatible projections. Old % style is deprecated.\r\nImprove support for view variants.\r\nSupport asset pipeline with gf.\r\nDrop first extension from .css.scss, per Rails 5.\r\nProvide :Ejob.\r\nSupport rails_helper.rb from rspec 3 on :Eintegrationtest.\r\nAdd alternate file support for CoffeeScript.\r\nAdd test\/controllers file to view tests.\r\nRequire app\/ for app detection (fixes false positive on Lotus).\r\nSupport detecting unicorn pid and binding.\r\nUse routes to determine default :Rpreview location.\r\nFix failure to define :OpenURL.\r\nProvide more :Rake defaults.\r\nChange :Rake migration default to db:migrate:redo.\r\nChange :Rake fallback from default to --tasks.\r\nSupport Bundler 2.\r\nSyntax highlighting updates.\r\nSwitch ctags --language from -javascript to ruby.\r\nPrefer .ctags over g:rails_ctags_arguments.\r\nWarn about deprecated :R commands.","3":"Add rails compiler plugin and use it for :Rails, :Rake, and :make.\r\nProvide dispatch.vim configuration.\r\nSupport projectionist.vim compatible projections. Old % style is deprecated.\r\nImprove support for view variants.\r\nSupport asset pipeline with gf.\r\nDrop first extension from .css.scss, per Rails 5.\r\nProvide :Ejob.\r\nSupport rails_helper.rb from rspec 3 on :Eintegrationtest.\r\nAdd alternate file support for CoffeeScript.\r\nAdd test\/controllers file to view tests.\r\nRequire app\/ for app detection (fixes false positive on Lotus).\r\nSupport detecting unicorn pid and binding.\r\nUse routes to determine default :Rpreview location.\r\nFix failure to define :OpenURL.\r\nProvide more :Rake defaults.\r\nChange :Rake migration default to db:migrate:redo.\r\nChange :Rake fallback from default to --tasks.\r\nSupport Bundler 2.\r\nSyntax highlighting updates.\r\nSwitch ctags --language from -javascript to ruby.\r\nPrefer .ctags over g:rails_ctags_arguments.\r\nWarn about deprecated :R commands.","package":"rails.zip","4":"rails.zip","src_id":"23266","5":"23266","creation_date":"1431024298","6":"1431024298"},{"0":"1567","vim_version":"7.0","1":"7.0","script_version":"5.1","2":"5.1","version_comment":"Modernize choice of rake task for running individual tests.\r\nSupport gf for jbuilder partials.\r\nSupport db\/structure.sql.\r\nSupport app\/assets\/ file creation (as opposed to public\/).\r\nHighlight custom keywords in eruby and haml.\r\nMiscellaneous syntax highlighting additions.\r\nEliminate assorted low value syntax highlighting tricks.\r\nDrop automatic set completefunc=syntaxcomplete#Complete.\r\nImprove log file syntax highlighting.\r\nEliminate log file syntax folding for massive speed boost.\r\nAdd g:rails_no_dbext to disable automatic dbext config.\r\nPartial forward compatibility with projectile.vim style projections.\r\nFix :Rlocale with no argument.\r\nFix :.Rake in a .task file.\r\nFix relative directories in 'path'.\r\nFix unintentional jumps into required files.\r\nAssorted alternate file fixes and enhancements.\r\nAssorted fixes to Rails app detection.\r\nAssorted buffer load performance improvements.","3":"Modernize choice of rake task for running individual tests.\r\nSupport gf for jbuilder partials.\r\nSupport db\/structure.sql.\r\nSupport app\/assets\/ file creation (as opposed to public\/).\r\nHighlight custom keywords in eruby and haml.\r\nMiscellaneous syntax highlighting additions.\r\nEliminate assorted low value syntax highlighting tricks.\r\nDrop automatic set completefunc=syntaxcomplete#Complete.\r\nImprove log file syntax highlighting.\r\nEliminate log file syntax folding for massive speed boost.\r\nAdd g:rails_no_dbext to disable automatic dbext config.\r\nPartial forward compatibility with projectile.vim style projections.\r\nFix :Rlocale with no argument.\r\nFix :.Rake in a .task file.\r\nFix relative directories in 'path'.\r\nFix unintentional jumps into required files.\r\nAssorted alternate file fixes and enhancements.\r\nAssorted fixes to Rails app detection.\r\nAssorted buffer load performance improvements.","package":"rails.zip","4":"rails.zip","src_id":"21702","5":"21702","creation_date":"1396325626","6":"1396325626"},{"0":"1567","vim_version":"7.0","1":"7.0","script_version":"5.0","2":"5.0","version_comment":"\"Projections\" greatly enhance the configurability of rails.vim.  See the help.\r\nDrop R from navigation commands (:Emodel, :Smodel, etc).  Old commands are still supported.\r\nNavigation commands provide boilerplate on file creation.\r\nRun tests with :Rrunner.\r\nLoad :Rails new\/:Rgenerate\/:Rdestroy results into quickfix.\r\nAssorted Rails 4 updates.\r\n:Rails replaces deprecated :Rscript.\r\nExtract concerns and helpers with :Rextract.\r\nSwitch :Elib default to Gemfile.\r\nSwitch :Emigration 0 to db\/seeds.rb.\r\nAdd :Eschema navigation command.\r\nRemove support for plugins, including navigation command.\r\nDetect and support engines with bundler.vim.\r\nBetter :Rpreview support for finding the currently running server.\r\nIndent settings are no longer automatically adjusted.  Try sleuth.vim.\r\nRemove configuration provisions superseded by projections.\r\nRemove assorted seldom used features.","3":"\"Projections\" greatly enhance the configurability of rails.vim.  See the help.\r\nDrop R from navigation commands (:Emodel, :Smodel, etc).  Old commands are still supported.\r\nNavigation commands provide boilerplate on file creation.\r\nRun tests with :Rrunner.\r\nLoad :Rails new\/:Rgenerate\/:Rdestroy results into quickfix.\r\nAssorted Rails 4 updates.\r\n:Rails replaces deprecated :Rscript.\r\nExtract concerns and helpers with :Rextract.\r\nSwitch :Elib default to Gemfile.\r\nSwitch :Emigration 0 to db\/seeds.rb.\r\nAdd :Eschema navigation command.\r\nRemove support for plugins, including navigation command.\r\nDetect and support engines with bundler.vim.\r\nBetter :Rpreview support for finding the currently running server.\r\nIndent settings are no longer automatically adjusted.  Try sleuth.vim.\r\nRemove configuration provisions superseded by projections.\r\nRemove assorted seldom used features.","package":"rails.zip","4":"rails.zip","src_id":"19738","5":"19738","creation_date":"1364792695","6":"1364792695"},{"0":"1567","vim_version":"7.0","1":"7.0","script_version":"4.4","2":"4.4","version_comment":"Support Rails 3.1 assets (smarter :Rjavascript and :Rstylesheet).\nSupport RSpec 2 backtrace format in :Rake.\nSupport rename_index in :Rinvert.\nSupport slim template type.\nBetter support for Rails 3 style `:Rails new foo`.\nLink Gemfile and Gemfile.lock with :A.\nAdd bundler.vim support.\nSyntax highlight `execute` in migrations.\nSyntax highlight `attr_readonly` [Adam Vaughan].\nSyntax highlight `around` in specs [Ca\u00c3\u008c\u00c2\u0081ssio Marques].\nFix Oracle dbext support [Mark Roghelia].\nFix singularization of \"movies\".\nFix gf on render :partial => 'foo\/bar.html'.\nFix gf with Ruby 1.9 hashes.\nRemove AWS abbreviation.\nRemove statusline indicator.\nRemove project.vim support.","3":"Support Rails 3.1 assets (smarter :Rjavascript and :Rstylesheet).\nSupport RSpec 2 backtrace format in :Rake.\nSupport rename_index in :Rinvert.\nSupport slim template type.\nBetter support for Rails 3 style `:Rails new foo`.\nLink Gemfile and Gemfile.lock with :A.\nAdd bundler.vim support.\nSyntax highlight `execute` in migrations.\nSyntax highlight `attr_readonly` [Adam Vaughan].\nSyntax highlight `around` in specs [Ca\u00c3\u008c\u00c2\u0081ssio Marques].\nFix Oracle dbext support [Mark Roghelia].\nFix singularization of \"movies\".\nFix gf on render :partial => 'foo\/bar.html'.\nFix gf with Ruby 1.9 hashes.\nRemove AWS abbreviation.\nRemove statusline indicator.\nRemove project.vim support.","package":"rails.zip","4":"rails.zip","src_id":"16429","5":"16429","creation_date":"1314919203","6":"1314919203"},{"0":"1567","vim_version":"7.0","1":"7.0","script_version":"4.3","2":"4.3","version_comment":"Support :Rails new app for Rails 3.\r\nAdd support for CoffeeScript, LESS CSS, and SCSS.\r\nSyntax highlighting updates for Rails 3 and RSpec 2.\r\nSupport for RSpec 2's spec\/requests.\r\nSupport :.Rake in test 'foo' do ... end.\r\n:Rake in quickfix window reruns last rake task.\r\n:Rake - reruns last rake task.\r\n:Rake in views runs view specs.\r\nSupport test\/unit\/helpers.\r\n:A from app\/weird\/foo.rb to spec\/weird\/foo_spec.rb.\r\nEnable omnicomplete in Haml views.\r\nAlso create :RD commands with :Rnavcommand.\r\nFix gf on \"include Namespaced::Module\".\r\nFix Windows \"C:\" versus \"c:\" issue.\r\nChange cookies abbreviation from co to coo (so one can type co.uk).","3":"Support :Rails new app for Rails 3.\r\nAdd support for CoffeeScript, LESS CSS, and SCSS.\r\nSyntax highlighting updates for Rails 3 and RSpec 2.\r\nSupport for RSpec 2's spec\/requests.\r\nSupport :.Rake in test 'foo' do ... end.\r\n:Rake in quickfix window reruns last rake task.\r\n:Rake - reruns last rake task.\r\n:Rake in views runs view specs.\r\nSupport test\/unit\/helpers.\r\n:A from app\/weird\/foo.rb to spec\/weird\/foo_spec.rb.\r\nEnable omnicomplete in Haml views.\r\nAlso create :RD commands with :Rnavcommand.\r\nFix gf on \"include Namespaced::Module\".\r\nFix Windows \"C:\" versus \"c:\" issue.\r\nChange cookies abbreviation from co to coo (so one can type co.uk).","package":"rails.zip","4":"rails.zip","src_id":"13800","5":"13800","creation_date":"1284143849","6":"1284143849"},{"0":"1567","vim_version":"7.0","1":"7.0","script_version":"4.2","2":"4.2","version_comment":"Default :Rlib to db\/seeds.rb.\r\nDefault :Rplugin to Gemfile.\r\n:Renvironment prefers Rails 3's config\/application.rb.\r\nSupport script\/rails from Rails 3.\r\nUpdate generator completion for Rails 3.\r\nSyntax highlighting and gf support in Rails 3 routes.\r\nUpdate syntax highlighting for assorted Rails 3 changes.\r\nAdd support for Rails 3 mailers.\r\nAdd :Rmailer navigation command.\r\nAdd abbreviations for ActiveModel\/ActionDispatch.\r\nExpose pluralization as abolish.vim (vimscript #1545) coercions t and l.\r\nAdd support for allml.vim replacement ragtag.vim (vimscript #1896).\r\nHighlight its, expect, and double from RSpec.\r\nFix parsing of Test::Unit failures.\r\nAdd support for tmux (like GNU screen) [Will Gray].\r\nDisable menu in MacVim by default to eliminate weird terminal output.\r\nEliminate g:rails_expensive, g:rails_dbext, and g:rails_default_database.\r\n","3":"Default :Rlib to db\/seeds.rb.\r\nDefault :Rplugin to Gemfile.\r\n:Renvironment prefers Rails 3's config\/application.rb.\r\nSupport script\/rails from Rails 3.\r\nUpdate generator completion for Rails 3.\r\nSyntax highlighting and gf support in Rails 3 routes.\r\nUpdate syntax highlighting for assorted Rails 3 changes.\r\nAdd support for Rails 3 mailers.\r\nAdd :Rmailer navigation command.\r\nAdd abbreviations for ActiveModel\/ActionDispatch.\r\nExpose pluralization as abolish.vim (vimscript #1545) coercions t and l.\r\nAdd support for allml.vim replacement ragtag.vim (vimscript #1896).\r\nHighlight its, expect, and double from RSpec.\r\nFix parsing of Test::Unit failures.\r\nAdd support for tmux (like GNU screen) [Will Gray].\r\nDisable menu in MacVim by default to eliminate weird terminal output.\r\nEliminate g:rails_expensive, g:rails_dbext, and g:rails_default_database.\r\n","package":"rails.zip","4":"rails.zip","src_id":"12622","5":"12622","creation_date":"1268496598","6":"1268496598"},{"0":"1567","vim_version":"7.0","1":"7.0","script_version":"4.1","2":"4.1","version_comment":"Completely eliminate usage of if_ruby.\r\nHighlight *_via_redirect in tests and raw in views.\r\nSupport gf on stylesheets\/javascripts when extension is given.\r\nLicense clarification to enable distribution in Debian.\r\nExplain that donations on Github through Pledgie are matched and given to ICCF.","3":"Completely eliminate usage of if_ruby.\r\nHighlight *_via_redirect in tests and raw in views.\r\nSupport gf on stylesheets\/javascripts when extension is given.\r\nLicense clarification to enable distribution in Debian.\r\nExplain that donations on Github through Pledgie are matched and given to ICCF.","package":"rails.zip","4":"rails.zip","src_id":"11920","5":"11920","creation_date":"1261169498","6":"1261169498"},{"0":"1567","vim_version":"7.0","1":"7.0","script_version":"4.0","2":"4.0","version_comment":"Remove all deprecated commands.\r\nUpdate syntax highlighting for Rails 2.3.4.\r\nFix bug when path to application contains whitespace.\r\n:Rtree spawns NERDTree. :Rproject is deprecated.\r\nIgnore all Javascript with :Rtags.\r\nAssorted changes to dbext support.\r\nClean up verbosity in statusline.\r\nFix bugs in :Rfixtures.\r\n:Rlocale navigation command.\r\n:Rintegrationtest knows about integration specs.\r\n:RD family of commands for reading in a file.\r\n:R in model is now schema definition (die, annotated_models).\r\n:A in view now always tries for a spec or test, not a helper.\r\n:R\/:A jump to next\/previous timestamped migration.\r\n:1R filename calls :Rfind filename.\r\n:0R is the same as :A and :.A is the same as :R.\r\nCease setting makeprg.\r\n:Rake opens error window (:cwindow).\r\n:Rake in db\/seeds.rb runs rake db:seed.\r\n:.Rake in controller runs rake routes CONTROLLER=.\r\nDocument :Rake default tasks.","3":"Remove all deprecated commands.\r\nUpdate syntax highlighting for Rails 2.3.4.\r\nFix bug when path to application contains whitespace.\r\n:Rtree spawns NERDTree. :Rproject is deprecated.\r\nIgnore all Javascript with :Rtags.\r\nAssorted changes to dbext support.\r\nClean up verbosity in statusline.\r\nFix bugs in :Rfixtures.\r\n:Rlocale navigation command.\r\n:Rintegrationtest knows about integration specs.\r\n:RD family of commands for reading in a file.\r\n:R in model is now schema definition (die, annotated_models).\r\n:A in view now always tries for a spec or test, not a helper.\r\n:R\/:A jump to next\/previous timestamped migration.\r\n:1R filename calls :Rfind filename.\r\n:0R is the same as :A and :.A is the same as :R.\r\nCease setting makeprg.\r\n:Rake opens error window (:cwindow).\r\n:Rake in db\/seeds.rb runs rake db:seed.\r\n:.Rake in controller runs rake routes CONTROLLER=.\r\nDocument :Rake default tasks.","package":"rails.zip","4":"rails.zip","src_id":"11481","5":"11481","creation_date":"1254687040","6":"1254687040"},{"0":"1567","vim_version":"7.0","1":"7.0","script_version":"3.4","2":"3.4","version_comment":"Load rake stats, routes, notes, etc into quickfix window.\r\n:Rake! doesn't jump to first error.\r\n:Rmetal navigation command.\r\n:Rintegrationtest edits cucumber features.\r\n:Rstylesheet edits sass if present.\r\nPreserve case with :Rjavascript and :Rstylesheet.\r\nOption for :Rtags to override ctags arguments.\r\nRails 2.3 gf support: render 'foo', ApplicationController.\r\nRails 2.3 and additional rspec syntax highlighting.","3":"Load rake stats, routes, notes, etc into quickfix window.\r\n:Rake! doesn't jump to first error.\r\n:Rmetal navigation command.\r\n:Rintegrationtest edits cucumber features.\r\n:Rstylesheet edits sass if present.\r\nPreserve case with :Rjavascript and :Rstylesheet.\r\nOption for :Rtags to override ctags arguments.\r\nRails 2.3 gf support: render 'foo', ApplicationController.\r\nRails 2.3 and additional rspec syntax highlighting.","package":"rails.zip","4":"rails.zip","src_id":"10297","5":"10297","creation_date":"1238127420","6":"1238127420"},{"0":"1567","vim_version":"7.0","1":"7.0","script_version":"3.3","2":"3.3","version_comment":":Rtags ignores jquery plugins (can trip up ctags).\r\n:Rtags indexes .rake, .rjs, and .builder files [Mark Wilden].\r\n:Rproject is more robust against missing directories [Mark Wilden].\r\n:Rproject uses NERDTree if project.vim not present.\r\nHighlight #default_scope in models; setup\/teardown\/test in tests [Daniel Schierbeck].\r\n:.Rake in a migration method runs db:migrate:up or db:migrate:down.\r\nGracefully ignore leading underscore in :Rextract _foo.\r\nNavigation commands accept a line number (:Redit Rakefile:5).\r\n:Rmigration with no argument always jumps to latest migration.\r\n:Renvironment and :Rinitializer navigation commands.","3":":Rtags ignores jquery plugins (can trip up ctags).\r\n:Rtags indexes .rake, .rjs, and .builder files [Mark Wilden].\r\n:Rproject is more robust against missing directories [Mark Wilden].\r\n:Rproject uses NERDTree if project.vim not present.\r\nHighlight #default_scope in models; setup\/teardown\/test in tests [Daniel Schierbeck].\r\n:.Rake in a migration method runs db:migrate:up or db:migrate:down.\r\nGracefully ignore leading underscore in :Rextract _foo.\r\nNavigation commands accept a line number (:Redit Rakefile:5).\r\n:Rmigration with no argument always jumps to latest migration.\r\n:Renvironment and :Rinitializer navigation commands.","package":"rails.zip","4":"rails.zip","src_id":"9854","5":"9854","creation_date":"1232750675","6":"1232750675"},{"0":"1567","vim_version":"7.0","1":"7.0","script_version":"3.2","2":"3.2","version_comment":"Fix :Rview when the cwd isn't the rails root.\r\nFix edge case with :Rscript family on Windows.\r\nUse new autocmd interface of dbext 8.00.\r\nFix :Rp, :Rpp, :Ry.\r\nMiscellaneous tab complete fiddling.\r\n:Rake in a cucumber feature runs that feature.\r\nPluralization for alias, status, index, and vertex.","3":"Fix :Rview when the cwd isn't the rails root.\r\nFix edge case with :Rscript family on Windows.\r\nUse new autocmd interface of dbext 8.00.\r\nFix :Rp, :Rpp, :Ry.\r\nMiscellaneous tab complete fiddling.\r\n:Rake in a cucumber feature runs that feature.\r\nPluralization for alias, status, index, and vertex.","package":"rails.zip","4":"rails.zip","src_id":"9499","5":"9499","creation_date":"1226588044","6":"1226588044"},{"0":"1567","vim_version":"7.0","1":"7.0","script_version":"3.1","2":"3.1","version_comment":"Update helpers to Edge Rails.\r\n:Rmigration 0 edits db\/schema.rb.\r\n:Rake now defaults to full test\/spec (:.Rake for a focused run).\r\nRemove Vim 7 clauses from documentation.\r\n:Redit . edits Rails root.\r\nFix tab completion bugs.\r\nFix :Rails command.\r\n","3":"Update helpers to Edge Rails.\r\n:Rmigration 0 edits db\/schema.rb.\r\n:Rake now defaults to full test\/spec (:.Rake for a focused run).\r\nRemove Vim 7 clauses from documentation.\r\n:Redit . edits Rails root.\r\nFix tab completion bugs.\r\nFix :Rails command.\r\n","package":"rails.zip","4":"rails.zip","src_id":"9397","5":"9397","creation_date":"1224881024","6":"1224881024"},{"0":"1567","vim_version":"7.0","1":"7.0","script_version":"3.0","2":"3.0","version_comment":"Major refactoring to take advantage of Vim 7 features (please report any regressions).\r\nSmart, app dependent menus for generators and rake tasks.\r\nSmart, app dependent tab completion for generators, rake tasks, and environments.\r\nCrude fuzzy tab complete: :Rmodel um<Tab> could expand to user_mailer.\r\n:Rlib with no argument is now a shortcut to config\/routes.rb.\r\n:Rintegrationtest with no argument now a shortcut to test\/test_helper.rb.\r\n:Rspec navigation command.\r\n:Runittest also navigates to model specs.\r\n:Rfunctionaltest also navigates to controller specs.\r\n:Rfixtures finds extensionless rspec fixtures.\r\n:Rake line number argument. :8Rake to run the test on line 8.\r\n:0Rake forces all tests to run.\r\n:Rake in a spec scopes by line number.\r\n:Rake in an app\/ file runs the corresponding spec (if no test exists).\r\n:Rake in config\/routes.rb runs rake routes.\r\n:Rake in a fixtures file runs db:fixtures:identify LABEL=identifier.\r\n:0Rake in a fixtures file runs db:fixtures:load FIXTURES=name.\r\n:Rtags now creates tags file in tmp (for easier SCM ignoring).\r\nFix :Rgenerate migration to properly jump to timestamped migrations.","3":"Major refactoring to take advantage of Vim 7 features (please report any regressions).\r\nSmart, app dependent menus for generators and rake tasks.\r\nSmart, app dependent tab completion for generators, rake tasks, and environments.\r\nCrude fuzzy tab complete: :Rmodel um<Tab> could expand to user_mailer.\r\n:Rlib with no argument is now a shortcut to config\/routes.rb.\r\n:Rintegrationtest with no argument now a shortcut to test\/test_helper.rb.\r\n:Rspec navigation command.\r\n:Runittest also navigates to model specs.\r\n:Rfunctionaltest also navigates to controller specs.\r\n:Rfixtures finds extensionless rspec fixtures.\r\n:Rake line number argument. :8Rake to run the test on line 8.\r\n:0Rake forces all tests to run.\r\n:Rake in a spec scopes by line number.\r\n:Rake in an app\/ file runs the corresponding spec (if no test exists).\r\n:Rake in config\/routes.rb runs rake routes.\r\n:Rake in a fixtures file runs db:fixtures:identify LABEL=identifier.\r\n:0Rake in a fixtures file runs db:fixtures:load FIXTURES=name.\r\n:Rtags now creates tags file in tmp (for easier SCM ignoring).\r\nFix :Rgenerate migration to properly jump to timestamped migrations.","package":"rails.zip","4":"rails.zip","src_id":"9367","5":"9367","creation_date":"1224287955","6":"1224287955"},{"0":"1567","vim_version":"6.0","1":"6.0","script_version":"2.1","2":"2.1","version_comment":"Syntax highlighting updates.\r\nTweaks to gf algorithm to find views and add include\/extend support.\r\n:Rcd and :Rlcd tab completion.\r\n:Rake in a spec scopes by line number.\r\nFix :A for lib\/view\/nested-controller specs.\r\nDetect model name in object daddy exemplars (for use with :Rmodel, etc)\r\nPoint docs at github repository.","3":"Syntax highlighting updates.\r\nTweaks to gf algorithm to find views and add include\/extend support.\r\n:Rcd and :Rlcd tab completion.\r\n:Rake in a spec scopes by line number.\r\nFix :A for lib\/view\/nested-controller specs.\r\nDetect model name in object daddy exemplars (for use with :Rmodel, etc)\r\nPoint docs at github repository.","package":"rails.zip","4":"rails.zip","src_id":"9321","5":"9321","creation_date":"1223522095","6":"1223522095"},{"0":"1567","vim_version":"6.0","1":"6.0","script_version":"2.0","2":"2.0","version_comment":"New git friendly versioning scheme.\r\nExtract rails_tabstop feature to vimscript #2253.\r\nTab completion of timestamped migrations.\r\nWork around nonzero exit status on Leopard.\r\nMinor bug fixes.","3":"New git friendly versioning scheme.\r\nExtract rails_tabstop feature to vimscript #2253.\r\nTab completion of timestamped migrations.\r\nWork around nonzero exit status on Leopard.\r\nMinor bug fixes.","package":"rails.zip","4":"rails.zip","src_id":"8735","5":"8735","creation_date":"1211831285","6":"1211831285"},{"0":"1567","vim_version":"6.0","1":"6.0","script_version":"256","2":"256","version_comment":"Added an autoload file, greatly reducing the code loaded at startup.\r\nHighlight omitted assert_tag and assert_no_tag methods in tests.\r\nOS X now more liberally detected when choosing a browser.\r\nHandle plain files with gf.","3":"Added an autoload file, greatly reducing the code loaded at startup.\r\nHighlight omitted assert_tag and assert_no_tag methods in tests.\r\nOS X now more liberally detected when choosing a browser.\r\nHandle plain files with gf.","package":"rails.zip","4":"rails.zip","src_id":"8293","5":"8293","creation_date":"1203274145","6":"1203274145"},{"0":"1567","vim_version":"6.0","1":"6.0","script_version":"239","2":"239","version_comment":"Miscellaneous Rails 2.0 related tweaks.\r\nCommands like :Rconsole now work with Cygwin Ruby.\r\nRudimentary HAML support.","3":"Miscellaneous Rails 2.0 related tweaks.\r\nCommands like :Rconsole now work with Cygwin Ruby.\r\nRudimentary HAML support.","package":"rails.zip","4":"rails.zip","src_id":"8117","5":"8117","creation_date":"1199346984","6":"1199346984"},{"0":"1567","vim_version":"6.0","1":"6.0","script_version":"222","2":"222","version_comment":":Rake runs rake spec inside a spec.\r\nRails 2.0 cleanups and tweaks","3":":Rake runs rake spec inside a spec.\r\nRails 2.0 cleanups and tweaks","package":"rails.zip","4":"rails.zip","src_id":"7862","5":"7862","creation_date":"1193987150","6":"1193987150"},{"0":"1567","vim_version":"6.0","1":"6.0","script_version":"216","2":"216","version_comment":"Refactoring.  Please report any regressions.\r\n:Rpreview utilizes \"# GET \/foos\/1\" style comments.\r\n:Rake in a migration defaults to migrating to the currently edited version.","3":"Refactoring.  Please report any regressions.\r\n:Rpreview utilizes \"# GET \/foos\/1\" style comments.\r\n:Rake in a migration defaults to migrating to the currently edited version.","package":"rails.zip","4":"rails.zip","src_id":"7622","5":"7622","creation_date":"1189084475","6":"1189084475"},{"0":"1567","vim_version":"6.0","1":"6.0","script_version":"200","2":"200","version_comment":"Anniversary edition:\r\nGreatly enhanced documentation.\r\nProper gf support for named route helpers (edit_post_url).\r\nSyntax highlighting for custom assertions from test_helper.rb.","3":"Anniversary edition:\r\nGreatly enhanced documentation.\r\nProper gf support for named route helpers (edit_post_url).\r\nSyntax highlighting for custom assertions from test_helper.rb.","package":"rails.zip","4":"rails.zip","src_id":"7183","5":"7183","creation_date":"1180627602","6":"1180627602"},{"0":"1567","vim_version":"6.0","1":"6.0","script_version":"192","2":"192","version_comment":":Rails works again.\r\n:R jumps between config\/database.yml and config\/environments\/*.rb","3":":Rails works again.\r\n:R jumps between config\/database.yml and config\/environments\/*.rb","package":"rails.zip","4":"rails.zip","src_id":"7134","5":"7134","creation_date":"1179397819","6":"1179397819"},{"0":"1567","vim_version":"6.0","1":"6.0","script_version":"190","2":"190","version_comment":"Partial support for nested extensions from edge (index.html.erb)\r\n:Rpp and Ry evaluate ruby and pretty print\/YAML dump the result.\r\n:Rplugin navigation command.\r\nFixed multiple bugs peculiar to Vim 6.2.\r\nOther small bug fixes and enhancements.","3":"Partial support for nested extensions from edge (index.html.erb)\r\n:Rpp and Ry evaluate ruby and pretty print\/YAML dump the result.\r\n:Rplugin navigation command.\r\nFixed multiple bugs peculiar to Vim 6.2.\r\nOther small bug fixes and enhancements.","package":"rails.zip","4":"rails.zip","src_id":"7117","5":"7117","creation_date":"1179238274","6":"1179238274"},{"0":"1567","vim_version":"6.0","1":"6.0","script_version":"180","2":"180","version_comment":":Rtask now additionally looks in the currently edited plugin's task directory.\r\n:Rlib navigation command looks for files in the lib directory and the current plugin's lib directory.\r\n:Rcommand creates custom navigation commands.\r\n:Rrefresh clears certain cached data. :Rrefresh! reloads rails.vim.\r\nAdded a browsefilter (for win32 file dialogs).","3":":Rtask now additionally looks in the currently edited plugin's task directory.\r\n:Rlib navigation command looks for files in the lib directory and the current plugin's lib directory.\r\n:Rcommand creates custom navigation commands.\r\n:Rrefresh clears certain cached data. :Rrefresh! reloads rails.vim.\r\nAdded a browsefilter (for win32 file dialogs).","package":"rails.zip","4":"rails.zip","src_id":"6991","5":"6991","creation_date":"1176816840","6":"1176816840"},{"0":"1567","vim_version":"6.0","1":"6.0","script_version":"175","2":"175","version_comment":"Highlight user classes (models, etc.) with the railsUserClass group.\r\nStatic list of highlighted helper methods (speeds up initialization).\r\nHTML highlighting occurs inside string literals like %Q<Hello <b>world<\/b>>.\r\nRecognize .erb and .builder extensions from edge Rails.\r\n:Rtask navigation command.","3":"Highlight user classes (models, etc.) with the railsUserClass group.\r\nStatic list of highlighted helper methods (speeds up initialization).\r\nHTML highlighting occurs inside string literals like %Q<Hello <b>world<\/b>>.\r\nRecognize .erb and .builder extensions from edge Rails.\r\n:Rtask navigation command.","package":"rails.zip","4":"rails.zip","src_id":"6923","5":"6923","creation_date":"1175248482","6":"1175248482"},{"0":"1567","vim_version":"6.0","1":"6.0","script_version":"166","2":"166","version_comment":"Prototype syntax highlighting.\r\nImproved errorformat, and an alternate format on :Rake! for backtraces.\r\nMore robust database.yml loading for dbext.","3":"Prototype syntax highlighting.\r\nImproved errorformat, and an alternate format on :Rake! for backtraces.\r\nMore robust database.yml loading for dbext.","package":"rails.zip","4":"rails.zip","src_id":"6813","5":"6813","creation_date":"1172602741","6":"1172602741"},{"0":"1567","vim_version":"6.0","1":"6.0","script_version":"150","2":"150","version_comment":"Fixed stack overflow when used in conjunction with rubycomplete.vim.\r\nImproved speed in certain setups on network file systems.\r\nMore Rails 1.2 goodies, including limited gf on url helpers.","3":"Fixed stack overflow when used in conjunction with rubycomplete.vim.\r\nImproved speed in certain setups on network file systems.\r\nMore Rails 1.2 goodies, including limited gf on url helpers.","package":"rails.zip","4":"rails.zip","src_id":"6683","5":"6683","creation_date":"1170025244","6":"1170025244"},{"0":"1567","vim_version":"6.0","1":"6.0","script_version":"144","2":"144","version_comment":"Syntax highlighting for routes.\r\nUpdates for Ruby on Rails 1.2 (primarily syntax highlighting, and a few abbreviations).\r\nTiny little bug fixes.","3":"Syntax highlighting for routes.\r\nUpdates for Ruby on Rails 1.2 (primarily syntax highlighting, and a few abbreviations).\r\nTiny little bug fixes.","package":"rails.zip","4":"rails.zip","src_id":"6620","5":"6620","creation_date":"1169071611","6":"1169071611"},{"0":"1567","vim_version":"6.0","1":"6.0","script_version":"140","2":"140","version_comment":":Rstylesheet and :Rjavascript commands.\r\nBetter tab completion for some file editing commands.\r\nGUI menu for recently edited projects.\r\nCertain expensive operations now enabled by default.  See :help rails-slow if you have any noticable delays.","3":":Rstylesheet and :Rjavascript commands.\r\nBetter tab completion for some file editing commands.\r\nGUI menu for recently edited projects.\r\nCertain expensive operations now enabled by default.  See :help rails-slow if you have any noticable delays.","package":"rails.zip","4":"rails.zip","src_id":"6582","5":"6582","creation_date":"1167988837","6":"1167988837"},{"0":"1567","vim_version":"6.0","1":"6.0","script_version":"132","2":"132","version_comment":"\":Rmodel .\" will open app\/models.  Other commands follow suit.\r\nSupport for surround.vim, vimscript#1697.\r\nMiscellaneous bug fixes and cleanups.","3":"\":Rmodel .\" will open app\/models.  Other commands follow suit.\r\nSupport for surround.vim, vimscript#1697.\r\nMiscellaneous bug fixes and cleanups.","package":"rails.zip","4":"rails.zip","src_id":"6365","5":"6365","creation_date":"1162407162","6":"1162407162"},{"0":"1567","vim_version":"6.0","1":"6.0","script_version":"128","2":"128","version_comment":"Improved documentation.\r\nMinor bug fixes.\r\nDeprecated :Rpartial in favor of :Rextract.","3":"Improved documentation.\r\nMinor bug fixes.\r\nDeprecated :Rpartial in favor of :Rextract.","package":"rails.zip","4":"rails.zip","src_id":"6076","5":"6076","creation_date":"1155760062","6":"1155760062"},{"0":"1567","vim_version":"6.0","1":"6.0","script_version":"123","2":"123","version_comment":"Quieter error messages (less \"Press ENTER\").\r\nFully functional modelines, including method local modelines.\r\n:Rmodel, :Rview, :Rcontroller, plus 9 other similar commands.","3":"Quieter error messages (less \"Press ENTER\").\r\nFully functional modelines, including method local modelines.\r\n:Rmodel, :Rview, :Rcontroller, plus 9 other similar commands.","package":"rails.zip","4":"rails.zip","src_id":"6041","5":"6041","creation_date":"1154710495","6":"1154710495"},{"0":"1567","vim_version":"6.0","1":"6.0","script_version":"113","2":"113","version_comment":"Bugfix for error messages in 6.x (apparently string() was added in 7.0)","3":"Bugfix for error messages in 6.x (apparently string() was added in 7.0)","package":"rails.zip","4":"rails.zip","src_id":"5972","5":"5972","creation_date":"1153343083","6":"1153343083"},{"0":"1567","vim_version":"6.0","1":"6.0","script_version":"111","2":"111","version_comment":"Abbreviations.\r\n:Rinvert to write a self.down migration.\r\n:Rset for per-app\/buffer\/method configuration.\r\nPreliminary modelines (disabled by default).","3":"Abbreviations.\r\n:Rinvert to write a self.down migration.\r\n:Rset for per-app\/buffer\/method configuration.\r\nPreliminary modelines (disabled by default).","package":"rails.zip","4":"rails.zip","src_id":"5963","5":"5963","creation_date":"1153175474","6":"1153175474"},{"0":"1567","vim_version":"6.0","1":"6.0","script_version":"100","2":"100","version_comment":":Rserver to start a new server, :Rserver! to kill old server first.\r\nOther new commands.\r\nImproved 'errorformat'.\r\nIntegration with dbext.vim.\r\nGUI menu.\r\nRobustness, robustness, robustness.\r\nMiscellaneous bug fixes and tweaks.\r\nAnd as always, more...","3":":Rserver to start a new server, :Rserver! to kill old server first.\r\nOther new commands.\r\nImproved 'errorformat'.\r\nIntegration with dbext.vim.\r\nGUI menu.\r\nRobustness, robustness, robustness.\r\nMiscellaneous bug fixes and tweaks.\r\nAnd as always, more...","package":"rails.zip","4":"rails.zip","src_id":"5911","5":"5911","creation_date":"1151877234","6":"1151877234"},{"0":"1567","vim_version":"6.0","1":"6.0","script_version":"69","2":"69","version_comment":"rails_level now defaults to 3.\r\na.vim compatible commands (:A et al).\r\nautocmds for specific file types (e.g. models)\r\nminimal syntax based user completion function (^X^U).\r\n:Rlog and log syntax highlighting.\r\n:Rproject - create\/find a project.vim project.\r\nand more...","3":"rails_level now defaults to 3.\r\na.vim compatible commands (:A et al).\r\nautocmds for specific file types (e.g. models)\r\nminimal syntax based user completion function (^X^U).\r\n:Rlog and log syntax highlighting.\r\n:Rproject - create\/find a project.vim project.\r\nand more...","package":"rails.zip","4":"rails.zip","src_id":"5840","5":"5840","creation_date":"1150490223","6":"1150490223"},{"0":"1567","vim_version":"6.0","1":"6.0","script_version":"37","2":"37","version_comment":"Lots of new features:\r\nEasy configuration with g:rails_level.\r\n:Rgenerate controller Foo generates and edits foo_controller.rb.\r\n<LocalLeader>rm and <LocalLeader>ra for good clean fun.\r\nSmarter partial extraction with :Rpartial.\r\nAnd more...","3":"Lots of new features:\r\nEasy configuration with g:rails_level.\r\n:Rgenerate controller Foo generates and edits foo_controller.rb.\r\n<LocalLeader>rm and <LocalLeader>ra for good clean fun.\r\nSmarter partial extraction with :Rpartial.\r\nAnd more...","package":"rails.zip","4":"rails.zip","src_id":"5808","5":"5808","creation_date":"1149632547","6":"1149632547"},{"0":"1567","vim_version":"6.0","1":"6.0","script_version":"18","2":"18","version_comment":"Initial upload","3":"Initial upload","package":"rails.zip","4":"rails.zip","src_id":"5789","5":"5789","creation_date":"1149082478","6":"1149082478"}]},"1566":{"script_id":"1566","0":"1566","script_name":"gtd","1":"gtd","script_type":"ftplugin","2":"ftplugin","summary":"TODO List Plugin and Syntax based-on \"Getting Things Done\"","3":"TODO List Plugin and Syntax based-on \"Getting Things Done\"","description":"A file-type plug-in and syntax file for the Vim editor that provides readers of David Allen's book, \"Getting Things Done\", a way to manage their task lists from within Vim.\r\n\r\nScreenshots, installation instructions and a user's guide is available at:\r\nhttp:\/\/www.bartholomew.id.au\/projects\/gtdwithvim\/\r\n\r\n\r\nThis is my first Vim script, so if anyone has any recommendations (especially to improve portability and compatibility with other Vim versions) please contact me.","4":"A file-type plug-in and syntax file for the Vim editor that provides readers of David Allen's book, \"Getting Things Done\", a way to manage their task lists from within Vim.\r\n\r\nScreenshots, installation instructions and a user's guide is available at:\r\nhttp:\/\/www.bartholomew.id.au\/projects\/gtdwithvim\/\r\n\r\n\r\nThis is my first Vim script, so if anyone has any recommendations (especially to improve portability and compatibility with other Vim versions) please contact me.","install_details":"","5":"","first_name":"William","6":"William","last_name":"Bartholomew","7":"Bartholomew","releases":[{"0":"1566","vim_version":"7.0","1":"7.0","script_version":"1.0.36","2":"1.0.36","version_comment":"ADDED Now the creation date of the task is appended to the task description.","3":"ADDED Now the creation date of the task is appended to the task description.","package":"GtdWithVim-1.0.36.7284.zip","4":"GtdWithVim-1.0.36.7284.zip","src_id":"5947","5":"5947","creation_date":"1152761183","6":"1152761183"},{"0":"1566","vim_version":"7.0","1":"7.0","script_version":"1.0.30","2":"1.0.30","version_comment":"FIXED Now supports Vim 6.4 (and possibly earlier)\r\nADDED Ex-mode commands (:GtdNewTask, :GtdAddContext, :GtdAssignProject, :GtdMarkDone)","3":"FIXED Now supports Vim 6.4 (and possibly earlier)\r\nADDED Ex-mode commands (:GtdNewTask, :GtdAddContext, :GtdAssignProject, :GtdMarkDone)","package":"GtdWithVim-1.0.30.6272.zip","4":"GtdWithVim-1.0.30.6272.zip","src_id":"5787","5":"5787","creation_date":"1148949962","6":"1148949962"},{"0":"1566","vim_version":"7.0","1":"7.0","script_version":"1.0.29","2":"1.0.29","version_comment":"Changed to Unix line-endings to improve compatibility (thanks to Mikolaj Machowski)","3":"Changed to Unix line-endings to improve compatibility (thanks to Mikolaj Machowski)","package":"GtdWithVim-1.0.29.2910.zip","4":"GtdWithVim-1.0.29.2910.zip","src_id":"5786","5":"5786","creation_date":"1148831354","6":"1148831354"},{"0":"1566","vim_version":"7.0","1":"7.0","script_version":"1.0.28","2":"1.0.28","version_comment":"Initial upload","3":"Initial upload","package":"GtdWithVim-1.0.28.3674.zip","4":"GtdWithVim-1.0.28.3674.zip","src_id":"5783","5":"5783","creation_date":"1148783566","6":"1148783566"}]},"1565":{"script_id":"1565","0":"1565","script_name":"ftdetect\/ada.vim","1":"ftdetect\/ada.vim","script_type":"ftplugin","2":"ftplugin","summary":"Filetype detection for Ada (inactive, replaced by vimscript#1609)","3":"Filetype detection for Ada (inactive, replaced by vimscript#1609)","description":"This plugin is superseded by vimscript#1609 and https:\/\/github.com\/krischik\/Ad-Bundle.","4":"This plugin is superseded by vimscript#1609 and https:\/\/github.com\/krischik\/Ad-Bundle.","install_details":"Install from https:\/\/github.com\/krischik\/Ad-Bundle using dein (https:\/\/github.com\/Shougo\/dein.vim) or similar:\r\n\r\ncall dein#begin('\/Users\/martin\/vimfiles\/bundles')\r\ncall dein#add('krischik\/Ada-Bundle')\r\ncall dein#end()\r\ncall dein#install()","5":"Install from https:\/\/github.com\/krischik\/Ad-Bundle using dein (https:\/\/github.com\/Shougo\/dein.vim) or similar:\r\n\r\ncall dein#begin('\/Users\/martin\/vimfiles\/bundles')\r\ncall dein#add('krischik\/Ada-Bundle')\r\ncall dein#end()\r\ncall dein#install()","first_name":"Martin","6":"Martin","last_name":"Krischik","7":"Krischik","releases":[{"0":"1565","vim_version":"7.0","1":"7.0","script_version":"2.1","2":"2.1","version_comment":"Initial upload","3":"Initial upload","package":"ada.vim","4":"ada.vim","src_id":"5781","5":"5781","creation_date":"1148715302","6":"1148715302"}]},"1564":{"script_id":"1564","0":"1564","script_name":"forth.vim","1":"forth.vim","script_type":"syntax","2":"syntax","summary":"Syntax highlighting for the Forth programming language","3":"Syntax highlighting for the Forth programming language","description":"I no longer maintain this file. So please use the newest one included in Vim.\r\n\r\n\r\nThis version is an update of the version shipped with Vim 6.X and 7.X. I have only tested it with Vim 7.X.\r\n\r\nNew version allows highlighting of \"space errors\" in comments (e.g. trailing spaces and\/or tabs). Thanks to Benjamin Krill for this nice feature. To turn it on, add the following line to your vimrc:\r\n\r\nlet forth_space_errors=1\r\n\r\nIf you have switched it on, you can turn off highlighting of trailing spaces in comments by setting forth_no_trail_space_error in your vimrc. If you do not want the highlighting of a tabulator following a space in comments, you can turn this off by setting forth_no_tab_space_error.\r\n\r\n\r\nComment for the Initial upload:\r\n\r\nThomas E. Vaughan send me a patch, to allow words end with a parenthesis. Such a trailing parenthesis will now no longer start the highlighting for stack comments.\r\n\r\nI have also added a fix for a bug in the script, that led to an annoying W18 warning while parsing the script. Bill McCarthy and Ilya Sher found that bug in 2004!\r\nShame on me, I thought I had applied that fix *two* years ago to the offical version.\r\nWelcome to embarrassment city :-\\","4":"I no longer maintain this file. So please use the newest one included in Vim.\r\n\r\n\r\nThis version is an update of the version shipped with Vim 6.X and 7.X. I have only tested it with Vim 7.X.\r\n\r\nNew version allows highlighting of \"space errors\" in comments (e.g. trailing spaces and\/or tabs). Thanks to Benjamin Krill for this nice feature. To turn it on, add the following line to your vimrc:\r\n\r\nlet forth_space_errors=1\r\n\r\nIf you have switched it on, you can turn off highlighting of trailing spaces in comments by setting forth_no_trail_space_error in your vimrc. If you do not want the highlighting of a tabulator following a space in comments, you can turn this off by setting forth_no_tab_space_error.\r\n\r\n\r\nComment for the Initial upload:\r\n\r\nThomas E. Vaughan send me a patch, to allow words end with a parenthesis. Such a trailing parenthesis will now no longer start the highlighting for stack comments.\r\n\r\nI have also added a fix for a bug in the script, that led to an annoying W18 warning while parsing the script. Bill McCarthy and Ilya Sher found that bug in 2004!\r\nShame on me, I thought I had applied that fix *two* years ago to the offical version.\r\nWelcome to embarrassment city :-\\","install_details":"","5":"","first_name":"Christian","6":"Christian","last_name":"Br\u00c3\u00bcssow","7":"Br\u00c3\u00bcssow","releases":[{"0":"1564","vim_version":"7.0","1":"7.0","script_version":"1.14","2":"1.14","version_comment":"Dominique Pell\u00c3\u00a9 <dominique dot pelle at gmail dot com> made a patch to allow spellchecking of strings, comments, ...","3":"Dominique Pell\u00c3\u00a9 <dominique dot pelle at gmail dot com> made a patch to allow spellchecking of strings, comments, ...","package":"forth.vim","4":"forth.vim","src_id":"18049","5":"18049","creation_date":"1338127502","6":"1338127502"},{"0":"1564","vim_version":"6.0","1":"6.0","script_version":"1.13","2":"1.13","version_comment":"Thilo Six <T dot Six at gmx dot de> sent a patch for cpoptions.\r\nSee the discussion at http:\/\/thread.gmane.org\/gmane.editors.vim.devel\/32151\r\n","3":"Thilo Six <T dot Six at gmx dot de> sent a patch for cpoptions.\r\nSee the discussion at http:\/\/thread.gmane.org\/gmane.editors.vim.devel\/32151\r\n","package":"forth.vim","4":"forth.vim","src_id":"17172","5":"17172","creation_date":"1325968675","6":"1325968675"},{"0":"1564","vim_version":"7.0","1":"7.0","script_version":"1.12","2":"1.12","version_comment":"Josh Grams send a patch to allow the parenthesis comments at the beginning of a line. That patch also fixed a typo in one of the comments. Thank you :-)\r\n\r\nI have only tested the file with Vim 7.2, but I think it will also work with Vim 6.X.\r\n","3":"Josh Grams send a patch to allow the parenthesis comments at the beginning of a line. That patch also fixed a typo in one of the comments. Thank you :-)\r\n\r\nI have only tested the file with Vim 7.2, but I think it will also work with Vim 6.X.\r\n","package":"forth.vim","4":"forth.vim","src_id":"10961","5":"10961","creation_date":"1246995791","6":"1246995791"},{"0":"1564","vim_version":"7.0","1":"7.0","script_version":"1.11","2":"1.11","version_comment":"Shawn K. Quinn <sjquinn at speakeasy dot net> send a big patch with\r\nnew words commonly used in Forth programs or defined by GNU Forth.\r\nI also fixed a typo in closing words for class and object definition.","3":"Shawn K. Quinn <sjquinn at speakeasy dot net> send a big patch with\r\nnew words commonly used in Forth programs or defined by GNU Forth.\r\nI also fixed a typo in closing words for class and object definition.","package":"forth.vim","4":"forth.vim","src_id":"8247","5":"8247","creation_date":"1202531936","6":"1202531936"},{"0":"1564","vim_version":"7.0","1":"7.0","script_version":"1.10","2":"1.10","version_comment":"Benjamin Krill send me a nice patch to highlight \"space errors\" in comments (e.g. trailing spaces and\/or tabs). Thanks :-)","3":"Benjamin Krill send me a nice patch to highlight \"space errors\" in comments (e.g. trailing spaces and\/or tabs). Thanks :-)","package":"forth.vim","4":"forth.vim","src_id":"7354","5":"7354","creation_date":"1184417925","6":"1184417925"}]},"1563":{"script_id":"1563","0":"1563","script_name":"patchreview.vim","1":"patchreview.vim","script_type":"utility","2":"utility","summary":"Plugin for single or multipatch code reviews and workspace change\/diff reviews","3":"Plugin for single or multipatch code reviews and workspace change\/diff reviews","description":"The Patch Review plugin allows easy single or multipatch code or diff reviews.\r\n\r\nIt opens each affected (modified\/added\/deleted) file in the patch or in a version controlled workspace diff in a diff view in a separate tab.\r\n\r\nVIM provides the :diffpatch command to do single file reviews but can not handle patch files containing multiple patches as is common with software development projects.  This plugin provides that missing functionality.\r\n\r\nIt also does not pollute the workspace like :diffpatch does by writing files in the workspace.\r\n\r\nIt does automatic diff generation for various version control systems by running their respective diff commands.\r\n\r\n(Keywords: codereview, codereviews, code review, patch, patchutils, diff, diffpatch, patchreview, patchreviews, patch review, vcs, scm, mercurial, bazaar, hg, bzr, cvs, monotone, mtn, git, perforce, fossil)","4":"The Patch Review plugin allows easy single or multipatch code or diff reviews.\r\n\r\nIt opens each affected (modified\/added\/deleted) file in the patch or in a version controlled workspace diff in a diff view in a separate tab.\r\n\r\nVIM provides the :diffpatch command to do single file reviews but can not handle patch files containing multiple patches as is common with software development projects.  This plugin provides that missing functionality.\r\n\r\nIt also does not pollute the workspace like :diffpatch does by writing files in the workspace.\r\n\r\nIt does automatic diff generation for various version control systems by running their respective diff commands.\r\n\r\n(Keywords: codereview, codereviews, code review, patch, patchutils, diff, diffpatch, patchreview, patchreviews, patch review, vcs, scm, mercurial, bazaar, hg, bzr, cvs, monotone, mtn, git, perforce, fossil)","install_details":"QUICK INSTALL\r\n\r\nMethod 1\r\n\r\n  1. Unzip the files in your ~\/.vim directory.\r\n\r\n   2. Open Vim and do::\r\n\r\n      :helptags ~\/.vim\/doc\r\n\r\nMethod 2\r\n\r\nUse a vim plugin manager like NeoBundle\r\n\r\n   NeoBundle 'junkblocker\/patchreview-vim'\r\n\r\n\r\nQUICK USAGE\r\n\r\nReviewing current changes in your workspace::\r\n\r\n      :DiffReview\r\n\r\nReviewing staged git changes::\r\n\r\n      :DiffReview git staged --no-color -U5\r\n\r\nReviewing a patch::\r\n\r\n      :PatchReview some.patch\r\n\r\nReviewing a previously applied patch (AKA reverse patch review)::\r\n\r\n      :ReversePatchReview some.patch\r\n\r\nSee::\r\n\r\n      :h patchreview\r\n\r\nfor usage details.\r\n\r\n\r\nThe latest in-development version of the plugin lives at https:\/\/github.com\/junkblocker\/patchreview-vim which may be slightly newer and slightly unstable.","5":"QUICK INSTALL\r\n\r\nMethod 1\r\n\r\n  1. Unzip the files in your ~\/.vim directory.\r\n\r\n   2. Open Vim and do::\r\n\r\n      :helptags ~\/.vim\/doc\r\n\r\nMethod 2\r\n\r\nUse a vim plugin manager like NeoBundle\r\n\r\n   NeoBundle 'junkblocker\/patchreview-vim'\r\n\r\n\r\nQUICK USAGE\r\n\r\nReviewing current changes in your workspace::\r\n\r\n      :DiffReview\r\n\r\nReviewing staged git changes::\r\n\r\n      :DiffReview git staged --no-color -U5\r\n\r\nReviewing a patch::\r\n\r\n      :PatchReview some.patch\r\n\r\nReviewing a previously applied patch (AKA reverse patch review)::\r\n\r\n      :ReversePatchReview some.patch\r\n\r\nSee::\r\n\r\n      :h patchreview\r\n\r\nfor usage details.\r\n\r\n\r\nThe latest in-development version of the plugin lives at https:\/\/github.com\/junkblocker\/patchreview-vim which may be slightly newer and slightly unstable.","first_name":"Manpreet","6":"Manpreet","last_name":"Singh","7":"Singh","releases":[{"0":"1563","vim_version":"7.0","1":"7.0","script_version":"2.1.1","2":"2.1.1","version_comment":"1. Handle project like plugins which change the buffer directory underneath us\r\n\r\n2. Further fixes for handling added and deleted files","3":"1. Handle project like plugins which change the buffer directory underneath us\r\n\r\n2. Further fixes for handling added and deleted files","package":"patchreview-2.1.1.zip","4":"patchreview-2.1.1.zip","src_id":"28622","5":"28622","creation_date":"1709047214","6":"1709047214"},{"0":"1563","vim_version":"7.0","1":"7.0","script_version":"2.0.0","2":"2.0.0","version_comment":"Massive speedup by ignoreing events\r\nStill allow keeping events enabled during processing with the g:patchreview_ignore_events flag\r\nBetter strip level guessing\r\nMiscellaneous accumulated fixes\r\n","3":"Massive speedup by ignoreing events\r\nStill allow keeping events enabled during processing with the g:patchreview_ignore_events flag\r\nBetter strip level guessing\r\nMiscellaneous accumulated fixes\r\n","package":"patchreview-2.0.0.zip","4":"patchreview-2.0.0.zip","src_id":"27220","5":"27220","creation_date":"1593677933","6":"1593677933"},{"0":"1563","vim_version":"7.2","1":"7.2","script_version":"1.3.0","2":"1.3.0","version_comment":"Added g:patchreview_foldlevel setting\r\nAdded g:patchreview_disable_syntax control syntax highlighting \r\nPrevent most autocmds from executing during plugin execution \r\nAdd dein.vim & consolidate install instructions \r\nLinting, README and help fixes and improvements \r\nFix and enhance the notification example \r\nFix DiffReview count style invocation \r\nIgnore shell error for bzr diff as it returns 1 on differences (lutostag) ","3":"Added g:patchreview_foldlevel setting\r\nAdded g:patchreview_disable_syntax control syntax highlighting \r\nPrevent most autocmds from executing during plugin execution \r\nAdd dein.vim & consolidate install instructions \r\nLinting, README and help fixes and improvements \r\nFix and enhance the notification example \r\nFix DiffReview count style invocation \r\nIgnore shell error for bzr diff as it returns 1 on differences (lutostag) ","package":"patchreview-1.3.0.zip","4":"patchreview-1.3.0.zip","src_id":"25101","5":"25101","creation_date":"1493524150","6":"1493524150"},{"0":"1563","vim_version":"7.2","1":"7.2","script_version":"1.2.1","2":"1.2.1","version_comment":"1) Added pathogen instructions (Daniel Lobato Garc\u00c3\u00ada)\r\n2) Fixed subversion support (wilywampa, Michael Leuchtenburg)\r\n","3":"1) Added pathogen instructions (Daniel Lobato Garc\u00c3\u00ada)\r\n2) Fixed subversion support (wilywampa, Michael Leuchtenburg)\r\n","package":"patchreview-1.2.1.zip","4":"patchreview-1.2.1.zip","src_id":"23469","5":"23469","creation_date":"1436759904","6":"1436759904"},{"0":"1563","vim_version":"7.2","1":"7.2","script_version":"1.2.0","2":"1.2.0","version_comment":"1) Support # prefixed comment lines in patches. 2) Better FreeBSD detection.","3":"1) Support # prefixed comment lines in patches. 2) Better FreeBSD detection.","package":"patchreview-1.2.0.zip","4":"patchreview-1.2.0.zip","src_id":"22131","5":"22131","creation_date":"1404446347","6":"1404446347"},{"0":"1563","vim_version":"7.2","1":"7.2","script_version":"1.1.1","2":"1.1.1","version_comment":"Better filepath and strip level calculations and some cleanup. ","3":"Better filepath and strip level calculations and some cleanup. ","package":"patchreview-1.1.1.zip","4":"patchreview-1.1.1.zip","src_id":"21719","5":"21719","creation_date":"1396500617","6":"1396500617"},{"0":"1563","vim_version":"7.2","1":"7.2","script_version":"1.1.0","2":"1.1.0","version_comment":"Added ability to open diffs on the right side (g:patchreview_split_right)","3":"Added ability to open diffs on the right side (g:patchreview_split_right)","package":"patchreview-1.1.0.zip","4":"patchreview-1.1.0.zip","src_id":"21050","5":"21050","creation_date":"1384630717","6":"1384630717"},{"0":"1563","vim_version":"7.2","1":"7.2","script_version":"1.0.9","2":"1.0.9","version_comment":"Fixed breakage caused by a last minute change.","3":"Fixed breakage caused by a last minute change.","package":"patchreview-1.0.9.zip","4":"patchreview-1.0.9.zip","src_id":"21003","5":"21003","creation_date":"1383525484","6":"1383525484"},{"0":"1563","vim_version":"7.2","1":"7.2","script_version":"1.0.8","2":"1.0.8","version_comment":"1.0.7 was half broken \/ Ensure folds are closed at diff creation \/ Make string truncation wide character aware for vim older than 7.3 \/ Minor code style change \/ Show parse result in case of inapplicable patch \/ Prevent empty blank line 1 in log buffer","3":"1.0.7 was half broken \/ Ensure folds are closed at diff creation \/ Make string truncation wide character aware for vim older than 7.3 \/ Minor code style change \/ Show parse result in case of inapplicable patch \/ Prevent empty blank line 1 in log buffer","package":"patchreview-1.0.8.zip","4":"patchreview-1.0.8.zip","src_id":"20997","5":"20997","creation_date":"1383448673","6":"1383448673"},{"0":"1563","vim_version":"7.2","1":"7.2","script_version":"1.0.7","2":"1.0.7","version_comment":"Added support for fossil","3":"Added support for fossil","package":"patchreview-1.0.7.zip","4":"patchreview-1.0.7.zip","src_id":"20763","5":"20763","creation_date":"1378515201","6":"1378515201"},{"0":"1563","vim_version":"7.2","1":"7.2","script_version":"1.0.6","2":"1.0.6","version_comment":"Convert .rej files to unified format if possible for better readability. Disable via g:patchreview_unified_rejects flag.","3":"Convert .rej files to unified format if possible for better readability. Disable via g:patchreview_unified_rejects flag.","package":"patchreview-1.0.6.zip","4":"patchreview-1.0.6.zip","src_id":"19501","5":"19501","creation_date":"1360698363","6":"1360698363"},{"0":"1563","vim_version":"7.2","1":"7.2","script_version":"1.0.5","2":"1.0.5","version_comment":"1) Fixed context format patch handling \r\n2) minor *BSD detection improvement","3":"1) Fixed context format patch handling \r\n2) minor *BSD detection improvement","package":"patchreview-1.0.5.zip","4":"patchreview-1.0.5.zip","src_id":"18855","5":"18855","creation_date":"1350861670","6":"1350861670"},{"0":"1563","vim_version":"7.2","1":"7.2","script_version":"1.0.4","2":"1.0.4","version_comment":"Fix breakage on vim 7.2. List 7.2 as the minimum vim version required.","3":"Fix breakage on vim 7.2. List 7.2 as the minimum vim version required.","package":"patchreview-1.0.4.zip","4":"patchreview-1.0.4.zip","src_id":"18309","5":"18309","creation_date":"1343100355","6":"1343100355"},{"0":"1563","vim_version":"7.0","1":"7.0","script_version":"1.0.3","2":"1.0.3","version_comment":"Perforce diff was skipping files added via branching","3":"Perforce diff was skipping files added via branching","package":"patchreview-1.0.3.zip","4":"patchreview-1.0.3.zip","src_id":"18284","5":"18284","creation_date":"1342634590","6":"1342634590"},{"0":"1563","vim_version":"7.0","1":"7.0","script_version":"1.0.2","2":"1.0.2","version_comment":"Fix for default patch command on BSD (it's not GNU compatible but perfectly usable)","3":"Fix for default patch command on BSD (it's not GNU compatible but perfectly usable)","package":"patchreview-1.0.2.zip","4":"patchreview-1.0.2.zip","src_id":"18248","5":"18248","creation_date":"1342109065","6":"1342109065"},{"0":"1563","vim_version":"7.0","1":"7.0","script_version":"1.0.1","2":"1.0.1","version_comment":"Set foldmethod to diff for patched buffers. This removes the annoying need to open folds by hand in 1.0.","3":"Set foldmethod to diff for patched buffers. This removes the annoying need to open folds by hand in 1.0.","package":"patchreview-1.0.1.zip","4":"patchreview-1.0.1.zip","src_id":"17731","5":"17731","creation_date":"1333724752","6":"1333724752"},{"0":"1563","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"- Added Perforce support\r\n- Add support for arbitrary diff generation commands\r\n- Added ability to plug in new version control systems by others\r\n- Added ability to create diffs in a way which lets session save\/restore work better\r\n- Windows fixes by Sergey Khorev","3":"- Added Perforce support\r\n- Add support for arbitrary diff generation commands\r\n- Added ability to plug in new version control systems by others\r\n- Added ability to create diffs in a way which lets session save\/restore work better\r\n- Windows fixes by Sergey Khorev","package":"patchreview-1.0.zip","4":"patchreview-1.0.zip","src_id":"17604","5":"17604","creation_date":"1332021078","6":"1332021078"},{"0":"1563","vim_version":"7.0","1":"7.0","script_version":"0.3.2","2":"0.3.2","version_comment":"Some diff extraction fixes and general error handling improvement","3":"Some diff extraction fixes and general error handling improvement","package":"patchreview-0.3.2.zip","4":"patchreview-0.3.2.zip","src_id":"16301","5":"16301","creation_date":"1313808381","6":"1313808381"},{"0":"1563","vim_version":"7.0","1":"7.0","script_version":"0.3.1","2":"0.3.1","version_comment":"Open the status buffer only in the current tab","3":"Open the status buffer only in the current tab","package":"patchreview-0.3.1.zip","4":"patchreview-0.3.1.zip","src_id":"15693","5":"15693","creation_date":"1306005442","6":"1306005442"},{"0":"1563","vim_version":"7.0","1":"7.0","script_version":"0.3","2":"0.3","version_comment":"1) Added Git support\r\n2) Some error handling for files which may be open in VIM elsewhere","3":"1) Added Git support\r\n2) Some error handling for files which may be open in VIM elsewhere","package":"patchreview-0.3.zip","4":"patchreview-0.3.zip","src_id":"13762","5":"13762","creation_date":"1283714496","6":"1283714496"},{"0":"1563","vim_version":"7.0","1":"7.0","script_version":"0.2.2","2":"0.2.2","version_comment":"1) Security fixes by removing custom tempfile creation\r\n2) Removed need for DiffReviewCleanup\/PatchReviewCleanup\r\n3) Better command execution error detection and display\r\n4) Improved diff view and folding by ignoring modelines\r\n5) Improved tab labels display ","3":"1) Security fixes by removing custom tempfile creation\r\n2) Removed need for DiffReviewCleanup\/PatchReviewCleanup\r\n3) Better command execution error detection and display\r\n4) Improved diff view and folding by ignoring modelines\r\n5) Improved tab labels display ","package":"patchreview.zip","4":"patchreview.zip","src_id":"12489","5":"12489","creation_date":"1267077972","6":"1267077972"},{"0":"1563","vim_version":"7.0","1":"7.0","script_version":"0.2","2":"0.2","version_comment":"1) Added DiffReview command for reviewing local changes in the workspace\r\n\r\n2) Removed the need for filterdiff by implemeting it in pure vim script\r\n","3":"1) Added DiffReview command for reviewing local changes in the workspace\r\n\r\n2) Removed the need for filterdiff by implemeting it in pure vim script\r\n","package":"patchreview.zip","4":"patchreview.zip","src_id":"12457","5":"12457","creation_date":"1266784081","6":"1266784081"},{"0":"1563","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"patchreview.zip","4":"patchreview.zip","src_id":"5769","5":"5769","creation_date":"1148595475","6":"1148595475"}]},"1562":{"script_id":"1562","0":"1562","script_name":"withdrawn","1":"withdrawn","script_type":"utility","2":"utility","summary":"-","3":"-","description":"Withdrawn","4":"Withdrawn","install_details":"Don't","5":"Don't","first_name":"Charles","6":"Charles","last_name":"Campbell","7":"Campbell","releases":[{"0":"1562","vim_version":"7.0","1":"7.0","script_version":"W","2":"W","version_comment":"Withdrawn","3":"Withdrawn","package":"Withdrawn.vim","4":"Withdrawn.vim","src_id":"5791","5":"5791","creation_date":"1149230394","6":"1149230394"}]},"1561":{"script_id":"1561","0":"1561","script_name":"Rainbow Parenthesis Bundle","1":"Rainbow Parenthesis Bundle","script_type":"utility","2":"utility","summary":"Coloured Parenthesis","3":"Coloured Parenthesis","description":"This is a simple rainbow colour plug-in for those who want an simple light\r\nweight rainbow colour syntax plug-in that supports `(\u00e2\u0080\u00a6)`, `[\u00e2\u0080\u00a6]`, `{\u00e2\u0080\u00a6}`\r\nand `<\u00e2\u0080\u00a6>`. \r\n\r\nIf you need something more powerful and configurable try\r\n[Rainbow Parentheses Improved](https:\/\/github.com\/luochen1990).\r\n\r\nThis is the original for http:\/\/www.vim.org\/scripts\/script.php?script_id=1561\r\n\r\nBased on the original rainbow_parenthesis from john gilmore but enhanced for\r\ngui mode.\r\n\r\n| Vim-Script  || https:\/\/www.vim.org\/scripts\/script.php?script_id=1561\r\n| Source      || https:\/\/github.com\/krischik\/vim-rainbow\r\n| Wiki        || https:\/\/github.com\/krischik\/vim-rainbow\/wiki\r\n| Releases    || https:\/\/github.com\/krischik\/vim-rainbow\/releases \r\n| Issues      || https:\/\/github.com\/krischik\/vim-rainbow\/issues \r\n| Discussions || https:\/\/github.com\/krischik\/vim-rainbow\/discussions \r\n\r\n","4":"This is a simple rainbow colour plug-in for those who want an simple light\r\nweight rainbow colour syntax plug-in that supports `(\u00e2\u0080\u00a6)`, `[\u00e2\u0080\u00a6]`, `{\u00e2\u0080\u00a6}`\r\nand `<\u00e2\u0080\u00a6>`. \r\n\r\nIf you need something more powerful and configurable try\r\n[Rainbow Parentheses Improved](https:\/\/github.com\/luochen1990).\r\n\r\nThis is the original for http:\/\/www.vim.org\/scripts\/script.php?script_id=1561\r\n\r\nBased on the original rainbow_parenthesis from john gilmore but enhanced for\r\ngui mode.\r\n\r\n| Vim-Script  || https:\/\/www.vim.org\/scripts\/script.php?script_id=1561\r\n| Source      || https:\/\/github.com\/krischik\/vim-rainbow\r\n| Wiki        || https:\/\/github.com\/krischik\/vim-rainbow\/wiki\r\n| Releases    || https:\/\/github.com\/krischik\/vim-rainbow\/releases \r\n| Issues      || https:\/\/github.com\/krischik\/vim-rainbow\/issues \r\n| Discussions || https:\/\/github.com\/krischik\/vim-rainbow\/discussions \r\n\r\n","install_details":"Install from https:\/\/github.com\/krischik\/vim-rainbow using dein (https:\/\/github.com\/Shougo\/dein.vim) or similar:\r\n\r\ncall dein#begin('$HOME\/vimfiles\/bundles')\r\ncall dein#add('krischik\/vim-rainbow')\r\ncall dein#end()\r\ncall dein#install()","5":"Install from https:\/\/github.com\/krischik\/vim-rainbow using dein (https:\/\/github.com\/Shougo\/dein.vim) or similar:\r\n\r\ncall dein#begin('$HOME\/vimfiles\/bundles')\r\ncall dein#add('krischik\/vim-rainbow')\r\ncall dein#end()\r\ncall dein#install()","first_name":"Martin","6":"Martin","last_name":"Krischik","7":"Krischik","releases":[{"0":"1561","vim_version":"7.0","1":"7.0","script_version":"5.4","2":"5.4","version_comment":"See https:\/\/github.com\/krischik\/Rainbow-Parenthesis-Bundle\/releases\/tag\/v_5.4","3":"See https:\/\/github.com\/krischik\/Rainbow-Parenthesis-Bundle\/releases\/tag\/v_5.4","package":"Rainbow-Parenthesis-Bundle-v_5.4.zip","4":"Rainbow-Parenthesis-Bundle-v_5.4.zip","src_id":"28185","5":"28185","creation_date":"1663551647","6":"1663551647"},{"0":"1561","vim_version":"7.0","1":"7.0","script_version":"5.3","2":"5.3","version_comment":"See https:\/\/github.com\/krischik\/Rainbow-Parenthesis-Bundle\/releases\/tag\/v_5.3","3":"See https:\/\/github.com\/krischik\/Rainbow-Parenthesis-Bundle\/releases\/tag\/v_5.3","package":"Rainbow-Parenthesis-Bundle-v_5.3.zip","4":"Rainbow-Parenthesis-Bundle-v_5.3.zip","src_id":"28181","5":"28181","creation_date":"1663433831","6":"1663433831"},{"0":"1561","vim_version":"7.0","1":"7.0","script_version":"5.2","2":"5.2","version_comment":"See https:\/\/github.com\/krischik\/Rainbow-Parenthesis-Bundle\/releases\/tag\/v_5.2","3":"See https:\/\/github.com\/krischik\/Rainbow-Parenthesis-Bundle\/releases\/tag\/v_5.2","package":"Rainbow-Parenthesis-Bundle-v_5.2.zip","4":"Rainbow-Parenthesis-Bundle-v_5.2.zip","src_id":"28180","5":"28180","creation_date":"1663297459","6":"1663297459"},{"0":"1561","vim_version":"7.0","1":"7.0","script_version":"5.1","2":"5.1","version_comment":"See https:\/\/github.com\/krischik\/Rainbow-Parenthesis-Bundle\/releases\/tag\/v_5.1","3":"See https:\/\/github.com\/krischik\/Rainbow-Parenthesis-Bundle\/releases\/tag\/v_5.1","package":"Rainbow-Parenthesis-Bundle-v_5.1.zip","4":"Rainbow-Parenthesis-Bundle-v_5.1.zip","src_id":"28173","5":"28173","creation_date":"1662867364","6":"1662867364"},{"0":"1561","vim_version":"7.0","1":"7.0","script_version":"5.0","2":"5.0","version_comment":"See https:\/\/github.com\/krischik\/Rainbow-Parenthesis-Bundle\/releases\/tag\/v_5.0","3":"See https:\/\/github.com\/krischik\/Rainbow-Parenthesis-Bundle\/releases\/tag\/v_5.0","package":"Rainbow-Parenthesis-Bundle-v_5.0.zip","4":"Rainbow-Parenthesis-Bundle-v_5.0.zip","src_id":"28172","5":"28172","creation_date":"1662867273","6":"1662867273"},{"0":"1561","vim_version":"7.0","1":"7.0","script_version":"4.0","2":"4.0","version_comment":"The new version now supports round, square brackets, curly and angle brackets.\r\n\r\nAlso, online help has been added. The online help also contains a section on how to add Rainbow Parenthesis to any syntax file.\r\n\r\nWith all the new features you might want to give it a good test.\r\nReports errors to http:\/\/code.google.com\/p\/vim-scripts\/issues\/list\r\nDiscuss improvements on: http:\/\/groups.google.com\/group\/vim_scripts","3":"The new version now supports round, square brackets, curly and angle brackets.\r\n\r\nAlso, online help has been added. The online help also contains a section on how to add Rainbow Parenthesis to any syntax file.\r\n\r\nWith all the new features you might want to give it a good test.\r\nReports errors to http:\/\/code.google.com\/p\/vim-scripts\/issues\/list\r\nDiscuss improvements on: http:\/\/groups.google.com\/group\/vim_scripts","package":"rainbow_parenthsis-4.0.vba","4":"rainbow_parenthsis-4.0.vba","src_id":"7770","5":"7770","creation_date":"1191901393","6":"1191901393"},{"0":"1561","vim_version":"7.0","1":"7.0","script_version":"3.0","2":"3.0","version_comment":"Now as a bundle. The new version will use autoload to conserve memory and start-up time.\r\n\r\nNew features: Uses functions for easy integration into existing syntax plug ins.","3":"Now as a bundle. The new version will use autoload to conserve memory and start-up time.\r\n\r\nNew features: Uses functions for easy integration into existing syntax plug ins.","package":"rainbow_parenthsis-3.0.vba","4":"rainbow_parenthsis-3.0.vba","src_id":"7684","5":"7684","creation_date":"1189996130","6":"1189996130"},{"0":"1561","vim_version":"7.0","1":"7.0","script_version":"2.1","2":"2.1","version_comment":"bug fixes","3":"bug fixes","package":"rainbow_parenthsis.vim","4":"rainbow_parenthsis.vim","src_id":"6432","5":"6432","creation_date":"1163814639","6":"1163814639"},{"0":"1561","vim_version":"7.0","1":"7.0","script_version":"2.0","2":"2.0","version_comment":"Initial upload","3":"Initial upload","package":"rainbow_parenthsis.vim","4":"rainbow_parenthsis.vim","src_id":"5765","5":"5765","creation_date":"1148548503","6":"1148548503"}]},"1560":{"script_id":"1560","0":"1560","script_name":"Neverness colour scheme","1":"Neverness colour scheme","script_type":"color scheme","2":"color scheme","summary":"A dark colour scheme","3":"A dark colour scheme","description":"Since I did not like any of the colour themes for one reason or another, I did my own.\r\n\r\nScreen shot with C, Python, LaTeX and Email files: http:\/\/www.kierun.org\/screen_shot_vim.png\r\n\r\nCriticism and comments are welcome. ","4":"Since I did not like any of the colour themes for one reason or another, I did my own.\r\n\r\nScreen shot with C, Python, LaTeX and Email files: http:\/\/www.kierun.org\/screen_shot_vim.png\r\n\r\nCriticism and comments are welcome. ","install_details":"Just copy to your ~\/.vim\/colors directory and it should work fine. ","5":"Just copy to your ~\/.vim\/colors directory and it should work fine. ","first_name":"Yann","6":"Yann","last_name":"Golanski","7":"Golanski","releases":[{"0":"1560","vim_version":"7.0","1":"7.0","script_version":"1.4","2":"1.4","version_comment":"SignColor update, thanks to Hannes Saffric.","3":"SignColor update, thanks to Hannes Saffric.","package":"neverness.vim","4":"neverness.vim","src_id":"18197","5":"18197","creation_date":"1340785941","6":"1340785941"},{"0":"1560","vim_version":"7.3","1":"7.3","script_version":"1.3","2":"1.3","version_comment":"Added CursorLineNr colour. ","3":"Added CursorLineNr colour. ","package":"neverness.vim","4":"neverness.vim","src_id":"17665","5":"17665","creation_date":"1332842676","6":"1332842676"},{"0":"1560","vim_version":"7.0","1":"7.0","script_version":"1.2","2":"1.2","version_comment":"Added pmenu colours thanks to  Sam Gr\u00c3\u00b6nblom.","3":"Added pmenu colours thanks to  Sam Gr\u00c3\u00b6nblom.","package":"neverness.vim","4":"neverness.vim","src_id":"12086","5":"12086","creation_date":"1263393347","6":"1263393347"},{"0":"1560","vim_version":"7.0","1":"7.0","script_version":"1.1","2":"1.1","version_comment":"Small bug fix. ","3":"Small bug fix. ","package":"neverness.vim","4":"neverness.vim","src_id":"7066","5":"7066","creation_date":"1178259126","6":"1178259126"},{"0":"1560","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"neverness.vim","4":"neverness.vim","src_id":"5757","5":"5757","creation_date":"1148522688","6":"1148522688"}]},"1559":{"script_id":"1559","0":"1559","script_name":"KDE GVIM vimopen","1":"KDE GVIM vimopen","script_type":"utility","2":"utility","summary":"Opens a file in a currently running GVIM instance","3":"Opens a file in a currently running GVIM instance","description":"This approximates the Open In... functionality of the Windows GVIM implementation.  If there is currently one or more instances of GVIM open, a dialog box is presented which lists them and allows one to be selected.  If the \"new\" option is picked then a new instance is created.  The last-selected instance is the default.","4":"This approximates the Open In... functionality of the Windows GVIM implementation.  If there is currently one or more instances of GVIM open, a dialog box is presented which lists them and allows one to be selected.  If the \"new\" option is picked then a new instance is created.  The last-selected instance is the default.","install_details":"Just put the script in your PATH somewhere and call it instead of gvim.  I've also added it to my kmenu and associated files to it from File Associations so it is called when a file is opened from the file manager.\r\n","5":"Just put the script in your PATH somewhere and call it instead of gvim.  I've also added it to my kmenu and associated files to it from File Associations so it is called when a file is opened from the file manager.\r\n","first_name":"john","6":"john","last_name":"kendall","7":"kendall","releases":[{"0":"1559","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"vimopen","4":"vimopen","src_id":"5756","5":"5756","creation_date":"1148498485","6":"1148498485"}]},"1558":{"script_id":"1558","0":"1558","script_name":"icansee.vim","1":"icansee.vim","script_type":"color scheme","2":"color scheme","summary":"Custom color scheme for maximum legibility on dark background.","3":"Custom color scheme for maximum legibility on dark background.","description":"Black (dark) background, with no obnoxious bold colors.  My attempt at a clean, legible color scheme, tested for half a year with various solaris\/linux\/windows file types (scripts\/configs\/etc.).\r\nTested on vim 6.x - 7.0.\r\n","4":"Black (dark) background, with no obnoxious bold colors.  My attempt at a clean, legible color scheme, tested for half a year with various solaris\/linux\/windows file types (scripts\/configs\/etc.).\r\nTested on vim 6.x - 7.0.\r\n","install_details":"Place in your vim installation's colors directory:\r\n   ~\/vimfiles\/colors\/   (or $VIM\/vimfiles\/colors\/)\r\n\r\nTo auto-load this color scheme every time vim is launched, add below \"source\" line into your vimrc file.  \r\n   source $HOME\/vimfiles\/colors\/icansee.vim    \"(or $VIM\/vimfiles\/colors\/icansee.vim)\r\n   set t_Co=256   \"Set terminals to use 256, instead of 16, colors for proper DarkGray use.\r\n\r\nTo find where your vimrc (settings file) is, run vim, then do :scriptnames.  If it lists nothing, then you probably have the \"tiny\" version (vim --version).  Recompile to use \"normal\" or \"big\" for color support.\r\n\r\nEnjoy!","5":"Place in your vim installation's colors directory:\r\n   ~\/vimfiles\/colors\/   (or $VIM\/vimfiles\/colors\/)\r\n\r\nTo auto-load this color scheme every time vim is launched, add below \"source\" line into your vimrc file.  \r\n   source $HOME\/vimfiles\/colors\/icansee.vim    \"(or $VIM\/vimfiles\/colors\/icansee.vim)\r\n   set t_Co=256   \"Set terminals to use 256, instead of 16, colors for proper DarkGray use.\r\n\r\nTo find where your vimrc (settings file) is, run vim, then do :scriptnames.  If it lists nothing, then you probably have the \"tiny\" version (vim --version).  Recompile to use \"normal\" or \"big\" for color support.\r\n\r\nEnjoy!","first_name":"John","6":"John","last_name":"Rhee","7":"Rhee","releases":[{"0":"1558","vim_version":"7.0","1":"7.0","script_version":"0.3","2":"0.3","version_comment":"Prevent same fore\/background for diff.","3":"Prevent same fore\/background for diff.","package":"icansee.vim","4":"icansee.vim","src_id":"26864","5":"26864","creation_date":"1575851979","6":"1575851979"},{"0":"1558","vim_version":"7.0","1":"7.0","script_version":"0.2","2":"0.2","version_comment":"Set PreProc (set variables) to white.\r\n","3":"Set PreProc (set variables) to white.\r\n","package":"icansee.vim","4":"icansee.vim","src_id":"7656","5":"7656","creation_date":"1189523682","6":"1189523682"},{"0":"1558","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"icansee.vim","4":"icansee.vim","src_id":"5755","5":"5755","creation_date":"1148490297","6":"1148490297"}]},"1557":{"script_id":"1557","0":"1557","script_name":"Toggle Window Size","1":"Toggle Window Size","script_type":"utility","2":"utility","summary":"Toggle the OS Window size(s) of GVIM","3":"Toggle the OS Window size(s) of GVIM","description":"This will maximize\/restore the height and width of the OS Window containing GVIM.  It allows you to specify what the maximum sizes are and will restore the original size and position.","4":"This will maximize\/restore the height and width of the OS Window containing GVIM.  It allows you to specify what the maximum sizes are and will restore the original size and position.","install_details":"just source it in your .vimrc or .gvimrc as:\r\nsource tws.vim\r\n","5":"just source it in your .vimrc or .gvimrc as:\r\nsource tws.vim\r\n","first_name":"john","6":"john","last_name":"kendall","7":"kendall","releases":[{"0":"1557","vim_version":"6.0","1":"6.0","script_version":"0.2","2":"0.2","version_comment":"5\/25\/06 -- \r\nfixed to use variables instead of hard-coded values for columns and lines\r\n            Thanks to Ilya at po4ta.com for the tip!\r\nEnhanced to (attempt to) keep track of window position for restore","3":"5\/25\/06 -- \r\nfixed to use variables instead of hard-coded values for columns and lines\r\n            Thanks to Ilya at po4ta.com for the tip!\r\nEnhanced to (attempt to) keep track of window position for restore","package":"tws.vim","4":"tws.vim","src_id":"5758","5":"5758","creation_date":"1148543616","6":"1148543616"},{"0":"1557","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"tws.vim","4":"tws.vim","src_id":"5754","5":"5754","creation_date":"1148475731","6":"1148475731"}]},"1556":{"script_id":"1556","0":"1556","script_name":"xul.vim","1":"xul.vim","script_type":"syntax","2":"syntax","summary":"Support autocompletion (CTRL-XCTRL-U): balises and attributes with XUL files.","3":"Support autocompletion (CTRL-XCTRL-U): balises and attributes with XUL files.","description":"Support autocompletion (CTRL-XCTRL-U): balises and attributes with XUL files.\r\nIt's easy to extend to others XML files.\r\n","4":"Support autocompletion (CTRL-XCTRL-U): balises and attributes with XUL files.\r\nIt's easy to extend to others XML files.\r\n","install_details":"copy this file into the syntax directory\r\nIf you want to auto set the filetype when you open a XUL file (extension .xul) you must add a file in ftdetect : xul.vim with the line :\r\nau BufRead,BufNewFile *.xul\tset filetype=xul","5":"copy this file into the syntax directory\r\nIf you want to auto set the filetype when you open a XUL file (extension .xul) you must add a file in ftdetect : xul.vim with the line :\r\nau BufRead,BufNewFile *.xul\tset filetype=xul","first_name":"jean-jacques","6":"jean-jacques","last_name":"peyronel","7":"peyronel","releases":[{"0":"1556","vim_version":"7.0","1":"7.0","script_version":"1.1","2":"1.1","version_comment":"Probleme dans la selection des attributs avec un decalage d'un espace.","3":"Probleme dans la selection des attributs avec un decalage d'un espace.","package":"xul.vim","4":"xul.vim","src_id":"5750","5":"5750","creation_date":"1148406045","6":"1148406045"},{"0":"1556","vim_version":"7.0","1":"7.0","script_version":"1","2":"1","version_comment":"Initial upload","3":"Initial upload","package":"xul.vim","4":"xul.vim","src_id":"5749","5":"5749","creation_date":"1148399034","6":"1148399034"}]},"1555":{"script_id":"1555","0":"1555","script_name":"CD_Plus","1":"CD_Plus","script_type":"utility","2":"utility","summary":"cd completion accelerator & file browser","3":"cd completion accelerator & file browser","description":"\r\n\r\n Features:\r\n\r\n    Gets you where you're going with the minimum possible keystrokes:\r\n\r\n        Each key stroke is completed as it is typed.  Since I used <Tab>\r\n        and ^D constantly, I figured, why not make it the default?\r\n\r\n        A directory listing is maintained in a separate window.  The clean,\r\n        scrollable\/editable directory\/file completion list is in a regular\r\n        Vim window.\r\n\r\n        A history is maintained individually for directories and files\r\n        accessed.\r\n\r\n        The completion is optimized for fast directory browsing, and file\r\n        opening.\r\n\r\n        You can create aliases for any directory\/file.  So, if you've set an\r\n        alias for '1', then ':cd 1<cr>' moves to that directory.\r\n\r\n\r\n\r\n    Key Commands:\r\n\r\n    ^H <BS>     The backspace keys are a combination of single char backspace\r\n                and immediate history \"rollback\".  They attempt to go back to\r\n                the first valid directory completion point.\r\n\r\n    ^W          Erase backwards a word\/directory.\r\n\r\n    ^U          Clear the line.\r\n\r\n    <TAB>       Rotate through the current list.\r\n    <S-TAB>     \r\n\r\n    <CR>        Execute a \"cd\" command to the currently shown directory.\r\n\r\n                If <CR> is typed in the display window, the name under the\r\n                cursor will be copied to the command line.\r\n\r\n    <ESC>       Jump into the __CD__ display window.   <ESC> jumps back.\r\n                <CR> selects and jumps back.  Changes made to history lists\r\n                in the buffer are saved to the global history vars.\r\n\r\n    <C-F>       ^F opens the command edit window.\r\n\r\n    <C-C>       ^C quits without changing directories.\r\n\r\n    <C-N>       Forward\/backward in the directory\/file history.\r\n    <C-P>       \r\n\r\n    \/           Can have special actions, see 'Navigating'\r\n\r\n    <C-L>       Refresh\r\n\r\n    <C-E>       Scroll one line\r\n    <C-Y>\r\n    <C-D>       Scroll page\r\n    <C-B>\r\n                Note : it is almost as easy to do your scrolling using\r\n                <ESC> to bounce to\/from the display window.\r\n\r\n\r\n    Other Commands:\r\n\r\n        The built-in commands are implemented as aliases (as are pc-drive\r\n        names).  You can override them, but then it's up to you to create\r\n        new ones.  Enter commands after a trailing  \/ .\r\n\r\n    'set '      Set an alias to the current directory displayed.\r\n\r\n    'delete '   Delete an alias.\r\n\r\n    'o pt '     Sets options.  (o<SPACE>pt is to force it to match sooner.)\r\n        \r\n            -   Set display column wrap width.  Set to 0 for auto-sizing to\r\n                longest path name.\r\n\r\n            -   Auto-change directory.  (default is 'local', as in 'lcd')\r\n\r\n            -   Recan for pc drives, and create 'C:\/' style aliases.\r\n\r\n            -   Match collapses (shortens) listings (default on; off means\r\n                always show full directory listing).\r\n\r\n            -   Toggle highlighting on\/off\r\n\r\n\r\n    'sort '     Sets sorting type. (default==alpha, time, size)\r\n\r\n    'long'      Long listing toggle (sets wrap, fsize, etc.)\r\n\r\n    'help '     This listing.\r\n\r\n    'history '  Browse the history.  A separate history is accessed\r\n                depending on whether the current command is 'cd' or 'lcd',\r\n                or some other file oriented command like 'e' or 'new'.\r\n\r\n    'edit '     Switch to 'open\/edit' file mode.\r\n    'new '      \r\n\r\n    ': '        Input other ex command.  I.e.  :vimgrep aug<CR>\r\n                will prepend as ':vimgrep aug \/someroot\/somefiles*'\r\n\r\n\r\n            Most of these can be abbreviated as first-char<space>  .\r\n\r\n\r\n        Note:   Spaces might not be displayed at the end of a line due to\r\n                some problem with 'echo' and 'input()'.\r\n\r\n\r\n    Navigating:\r\n\r\n        Every character typed will be treated as part of a directory or alias,\r\n        and the display will change accordingly.  Unmatched characters will\r\n        generally be discarded.  This takes a little getting used to, since\r\n        you might tend to type ahead more than will match (see also \/\/ below ).\r\n\r\n        The  \/  character is somewhat special.  If you add a slash after a\r\n        directory name, it moves the display to that directory, and sets the\r\n        current 'input' value to null.  Therefore, typing aliases is best done\r\n        after a trailing  \/  char.\r\n\r\n        Literal input:\r\n\r\n            '\/\/' must be used to enter non-existing names.\r\n\r\n            Adding a \/ to the end of a line which already ends in \/ will\r\n            toggle the  'g:CD_any_input'  option (default off).\r\n            Normally, keys which don't match anything are thrown away unless\r\n            this option == 1.  It also affects what names can be taken\r\n            from the ^N\/^P history.  Aliases are not completed, and must be\r\n            entered as ...\/full_alias<space>\/\r\n\r\n\r\n\r\n    Aliases:\r\n\r\n    -   Aliases automatically have a space added after them to help\r\n        distinguish from directories of the same name.\r\n\r\n    -   Best way to see all aliases is to clear the line with ^U\r\n\r\n\r\n\r\n\r\n    Customizing:\r\n\r\n        The default key mapping is:\r\n\r\n            cnoremap <silent> <expr> e<space> ( getcmdpos() == 1 && getcmdtype() == ':' ? CD_Plus_start('e') : 'e' )\r\n            cnoremap <expr> cd ( getcmdpos() == 1 && getcmdtype() == ':' ? CD_Plus_start('cd') : 'cd' )\r\n            cnoremap <expr> lcd ( getcmdpos() == 1 && getcmdtype() == ':' ? CD_Plus_start('lcd') : 'lcd' )\r\n        \r\n        a simpler keymap might be:\r\n            nnoremap <leader>cd :call CD_Plus('cd')<CR>\r\n\r\n        There is a list of globals,  following the script header, which you\r\n        can change.  There are a few more, but these are the simple ones,\r\n        which can also be set via option aliases.\r\n\r\n            g:CD_rc_file                default: $HOME . '\/.vim_cd_plus'\r\n                                    Most globals and history are saved\r\n                                    here.\r\n\r\n            g:CD_autochdir          'off', 'local', or 'global'\r\n\r\n            g:CD_dsp_wrap_len       default 19, specifies display column\r\n                                    wrapping.\r\n\r\n            g:CD_any_input          0 or 1, the starting value for literal\r\n                                    input (also set by trailing \/\/ toggle).\r\n\r\n            g:CD_scan_pc_drives     0 or 1, whether to attempt to discover\r\n                                    pc drive names (like C:, D:, etc.) and\r\n                                    create aliases for them.\r\n\r\n        If you want to customize the highlighting or sorting, it's a little\r\n        more complicated.  For highlighting, there is an 'init' function\r\n        that needs to be changed.  For sorting, an entry must be added to\r\n        the g:CD_aliases dict var (see top of script), and a new function\r\n        must be defined to do the sorting.  See the Sort_by_ftime() or\r\n        Sort_by_extension() functions for examples.\r\n\r\n\r\n\r\n    Caveats:\r\n\r\n    -   Works only with 'shellslash' on.\r\n    -   Restoring the command line height is a true pain in the ass.  It\r\n        works most of the time, though that is little consolation.\r\n    -   Tabbing is a little slow on large directory lists because of the\r\n        redraw requirement.  It isn't much a problem, though since it's only\r\n        noticable when you hold the tab key down.\r\n","4":"\r\n\r\n Features:\r\n\r\n    Gets you where you're going with the minimum possible keystrokes:\r\n\r\n        Each key stroke is completed as it is typed.  Since I used <Tab>\r\n        and ^D constantly, I figured, why not make it the default?\r\n\r\n        A directory listing is maintained in a separate window.  The clean,\r\n        scrollable\/editable directory\/file completion list is in a regular\r\n        Vim window.\r\n\r\n        A history is maintained individually for directories and files\r\n        accessed.\r\n\r\n        The completion is optimized for fast directory browsing, and file\r\n        opening.\r\n\r\n        You can create aliases for any directory\/file.  So, if you've set an\r\n        alias for '1', then ':cd 1<cr>' moves to that directory.\r\n\r\n\r\n\r\n    Key Commands:\r\n\r\n    ^H <BS>     The backspace keys are a combination of single char backspace\r\n                and immediate history \"rollback\".  They attempt to go back to\r\n                the first valid directory completion point.\r\n\r\n    ^W          Erase backwards a word\/directory.\r\n\r\n    ^U          Clear the line.\r\n\r\n    <TAB>       Rotate through the current list.\r\n    <S-TAB>     \r\n\r\n    <CR>        Execute a \"cd\" command to the currently shown directory.\r\n\r\n                If <CR> is typed in the display window, the name under the\r\n                cursor will be copied to the command line.\r\n\r\n    <ESC>       Jump into the __CD__ display window.   <ESC> jumps back.\r\n                <CR> selects and jumps back.  Changes made to history lists\r\n                in the buffer are saved to the global history vars.\r\n\r\n    <C-F>       ^F opens the command edit window.\r\n\r\n    <C-C>       ^C quits without changing directories.\r\n\r\n    <C-N>       Forward\/backward in the directory\/file history.\r\n    <C-P>       \r\n\r\n    \/           Can have special actions, see 'Navigating'\r\n\r\n    <C-L>       Refresh\r\n\r\n    <C-E>       Scroll one line\r\n    <C-Y>\r\n    <C-D>       Scroll page\r\n    <C-B>\r\n                Note : it is almost as easy to do your scrolling using\r\n                <ESC> to bounce to\/from the display window.\r\n\r\n\r\n    Other Commands:\r\n\r\n        The built-in commands are implemented as aliases (as are pc-drive\r\n        names).  You can override them, but then it's up to you to create\r\n        new ones.  Enter commands after a trailing  \/ .\r\n\r\n    'set '      Set an alias to the current directory displayed.\r\n\r\n    'delete '   Delete an alias.\r\n\r\n    'o pt '     Sets options.  (o<SPACE>pt is to force it to match sooner.)\r\n        \r\n            -   Set display column wrap width.  Set to 0 for auto-sizing to\r\n                longest path name.\r\n\r\n            -   Auto-change directory.  (default is 'local', as in 'lcd')\r\n\r\n            -   Recan for pc drives, and create 'C:\/' style aliases.\r\n\r\n            -   Match collapses (shortens) listings (default on; off means\r\n                always show full directory listing).\r\n\r\n            -   Toggle highlighting on\/off\r\n\r\n\r\n    'sort '     Sets sorting type. (default==alpha, time, size)\r\n\r\n    'long'      Long listing toggle (sets wrap, fsize, etc.)\r\n\r\n    'help '     This listing.\r\n\r\n    'history '  Browse the history.  A separate history is accessed\r\n                depending on whether the current command is 'cd' or 'lcd',\r\n                or some other file oriented command like 'e' or 'new'.\r\n\r\n    'edit '     Switch to 'open\/edit' file mode.\r\n    'new '      \r\n\r\n    ': '        Input other ex command.  I.e.  :vimgrep aug<CR>\r\n                will prepend as ':vimgrep aug \/someroot\/somefiles*'\r\n\r\n\r\n            Most of these can be abbreviated as first-char<space>  .\r\n\r\n\r\n        Note:   Spaces might not be displayed at the end of a line due to\r\n                some problem with 'echo' and 'input()'.\r\n\r\n\r\n    Navigating:\r\n\r\n        Every character typed will be treated as part of a directory or alias,\r\n        and the display will change accordingly.  Unmatched characters will\r\n        generally be discarded.  This takes a little getting used to, since\r\n        you might tend to type ahead more than will match (see also \/\/ below ).\r\n\r\n        The  \/  character is somewhat special.  If you add a slash after a\r\n        directory name, it moves the display to that directory, and sets the\r\n        current 'input' value to null.  Therefore, typing aliases is best done\r\n        after a trailing  \/  char.\r\n\r\n        Literal input:\r\n\r\n            '\/\/' must be used to enter non-existing names.\r\n\r\n            Adding a \/ to the end of a line which already ends in \/ will\r\n            toggle the  'g:CD_any_input'  option (default off).\r\n            Normally, keys which don't match anything are thrown away unless\r\n            this option == 1.  It also affects what names can be taken\r\n            from the ^N\/^P history.  Aliases are not completed, and must be\r\n            entered as ...\/full_alias<space>\/\r\n\r\n\r\n\r\n    Aliases:\r\n\r\n    -   Aliases automatically have a space added after them to help\r\n        distinguish from directories of the same name.\r\n\r\n    -   Best way to see all aliases is to clear the line with ^U\r\n\r\n\r\n\r\n\r\n    Customizing:\r\n\r\n        The default key mapping is:\r\n\r\n            cnoremap <silent> <expr> e<space> ( getcmdpos() == 1 && getcmdtype() == ':' ? CD_Plus_start('e') : 'e' )\r\n            cnoremap <expr> cd ( getcmdpos() == 1 && getcmdtype() == ':' ? CD_Plus_start('cd') : 'cd' )\r\n            cnoremap <expr> lcd ( getcmdpos() == 1 && getcmdtype() == ':' ? CD_Plus_start('lcd') : 'lcd' )\r\n        \r\n        a simpler keymap might be:\r\n            nnoremap <leader>cd :call CD_Plus('cd')<CR>\r\n\r\n        There is a list of globals,  following the script header, which you\r\n        can change.  There are a few more, but these are the simple ones,\r\n        which can also be set via option aliases.\r\n\r\n            g:CD_rc_file                default: $HOME . '\/.vim_cd_plus'\r\n                                    Most globals and history are saved\r\n                                    here.\r\n\r\n            g:CD_autochdir          'off', 'local', or 'global'\r\n\r\n            g:CD_dsp_wrap_len       default 19, specifies display column\r\n                                    wrapping.\r\n\r\n            g:CD_any_input          0 or 1, the starting value for literal\r\n                                    input (also set by trailing \/\/ toggle).\r\n\r\n            g:CD_scan_pc_drives     0 or 1, whether to attempt to discover\r\n                                    pc drive names (like C:, D:, etc.) and\r\n                                    create aliases for them.\r\n\r\n        If you want to customize the highlighting or sorting, it's a little\r\n        more complicated.  For highlighting, there is an 'init' function\r\n        that needs to be changed.  For sorting, an entry must be added to\r\n        the g:CD_aliases dict var (see top of script), and a new function\r\n        must be defined to do the sorting.  See the Sort_by_ftime() or\r\n        Sort_by_extension() functions for examples.\r\n\r\n\r\n\r\n    Caveats:\r\n\r\n    -   Works only with 'shellslash' on.\r\n    -   Restoring the command line height is a true pain in the ass.  It\r\n        works most of the time, though that is little consolation.\r\n    -   Tabbing is a little slow on large directory lists because of the\r\n        redraw requirement.  It isn't much a problem, though since it's only\r\n        noticable when you hold the tab key down.\r\n","install_details":"Put into your plugin directory","5":"Put into your plugin directory","first_name":"Eric","6":"Eric","last_name":"Arnold","7":"Arnold","releases":[{"0":"1555","vim_version":"7.0","1":"7.0","script_version":"2.3","2":"2.3","version_comment":"-\tadded window size restore\r\n-\tchanged \/\/ to 'literal' command\r\n-\tbug with fname and dirname sharing same prefix\r\n","3":"-\tadded window size restore\r\n-\tchanged \/\/ to 'literal' command\r\n-\tbug with fname and dirname sharing same prefix\r\n","package":"CD_Plus.vim","4":"CD_Plus.vim","src_id":"5849","5":"5849","creation_date":"1150858625","6":"1150858625"},{"0":"1555","vim_version":"7.0","1":"7.0","script_version":"2.2","2":"2.2","version_comment":"-\tFixed accumulating syntax entries (gradual slow down)\r\n-\tHighlighting shortcuts to speed up tabbing\r\n","3":"-\tFixed accumulating syntax entries (gradual slow down)\r\n-\tHighlighting shortcuts to speed up tabbing\r\n","package":"CD_Plus.vim","4":"CD_Plus.vim","src_id":"5815","5":"5815","creation_date":"1149759033","6":"1149759033"},{"0":"1555","vim_version":"7.0","1":"7.0","script_version":"2.1","2":"2.1","version_comment":"-\tMisc fixes (stray error messages)\r\n-\tOption to recan for pc drives\r\n-\tMisc fixes for pc drive pathnames\r\n\t(Still some problems).\r\n-\tAdded sorting options\r\n-\tFaster scrolling and tabbing\r\n-\tChanged :excmd enter method\r\n-\tAdded file size and time options.\r\n-\tAdded match collapse listing option.\r\n-\tAdded highlighting toggle\r\n-\tAdded long listing toggle\r\n","3":"-\tMisc fixes (stray error messages)\r\n-\tOption to recan for pc drives\r\n-\tMisc fixes for pc drive pathnames\r\n\t(Still some problems).\r\n-\tAdded sorting options\r\n-\tFaster scrolling and tabbing\r\n-\tChanged :excmd enter method\r\n-\tAdded file size and time options.\r\n-\tAdded match collapse listing option.\r\n-\tAdded highlighting toggle\r\n-\tAdded long listing toggle\r\n","package":"CD_Plus.vim","4":"CD_Plus.vim","src_id":"5810","5":"5810","creation_date":"1149702151","6":"1149702151"},{"0":"1555","vim_version":"7.0","1":"7.0","script_version":"2.0","2":"2.0","version_comment":"\r\n -\tAdded literal input mode (allow non-existent\r\n   names).\r\n -\tAdded ^F command window access.\r\n -\tDisplay and highlighting cleaned and improved.\r\n -\tAdded options aliases for col wrap and\r\n   autochdir.\r\n -\tAdded ^E ^Y passthrough for scrolling.\r\n -\tMisc fixes.\r\n","3":"\r\n -\tAdded literal input mode (allow non-existent\r\n   names).\r\n -\tAdded ^F command window access.\r\n -\tDisplay and highlighting cleaned and improved.\r\n -\tAdded options aliases for col wrap and\r\n   autochdir.\r\n -\tAdded ^E ^Y passthrough for scrolling.\r\n -\tMisc fixes.\r\n","package":"CD_Plus.vim","4":"CD_Plus.vim","src_id":"5800","5":"5800","creation_date":"1149453363","6":"1149453363"},{"0":"1555","vim_version":"7.0","1":"7.0","script_version":"1.5","2":"1.5","version_comment":"-   many minor fixes\r\n-   added filename completion, and quick switch to\r\n    edit, etc., and cmap e<space> .....\r\n-   added separate directory and filename\r\n    histories.\r\n-   will try to create intermediate directories.\r\n","3":"-   many minor fixes\r\n-   added filename completion, and quick switch to\r\n    edit, etc., and cmap e<space> .....\r\n-   added separate directory and filename\r\n    histories.\r\n-   will try to create intermediate directories.\r\n","package":"CD_Plus.vim","4":"CD_Plus.vim","src_id":"5793","5":"5793","creation_date":"1149245746","6":"1149245746"},{"0":"1555","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"CD_Plus.vim","4":"CD_Plus.vim","src_id":"5743","5":"5743","creation_date":"1148292416","6":"1148292416"}]},"1554":{"script_id":"1554","0":"1554","script_name":"autoload\/adacomplete.vim","1":"autoload\/adacomplete.vim","script_type":"ftplugin","2":"ftplugin","summary":"Omni-Competion for Ada (inactive, replaced by vimscript#1609)","3":"Omni-Competion for Ada (inactive, replaced by vimscript#1609)","description":"This plugin is superseded by vimscript#1609 and https:\/\/github.com\/krischik\/Ad-Bundle.","4":"This plugin is superseded by vimscript#1609 and https:\/\/github.com\/krischik\/Ad-Bundle.","install_details":"Install from https:\/\/github.com\/krischik\/Ad-Bundle using dein (https:\/\/github.com\/Shougo\/dein.vim) or similar:\r\n\r\ncall dein#begin('\/Users\/martin\/vimfiles\/bundles')\r\ncall dein#add('krischik\/Ada-Bundle')\r\ncall dein#end()\r\ncall dein#install()","5":"Install from https:\/\/github.com\/krischik\/Ad-Bundle using dein (https:\/\/github.com\/Shougo\/dein.vim) or similar:\r\n\r\ncall dein#begin('\/Users\/martin\/vimfiles\/bundles')\r\ncall dein#add('krischik\/Ada-Bundle')\r\ncall dein#end()\r\ncall dein#install()","first_name":"Martin","6":"Martin","last_name":"Krischik","7":"Krischik","releases":[{"0":"1554","vim_version":"7.0","1":"7.0","script_version":"2.1","2":"2.1","version_comment":"Some correction regarding the use of attributes. Correct use of the ' is a bit tricky. Also improved the search for begin of word which was quite buggy.\r\n\r\nI have created a complete description on how the omni completion works on wikibooks [1] if you like to know how it all works or prehaps like to create omni completion for another lanugage.\r\n\r\n[1] http:\/\/en.wikibooks.org\/wiki\/Learning_vi:Vim#Onmi_Completion","3":"Some correction regarding the use of attributes. Correct use of the ' is a bit tricky. Also improved the search for begin of word which was quite buggy.\r\n\r\nI have created a complete description on how the omni completion works on wikibooks [1] if you like to know how it all works or prehaps like to create omni completion for another lanugage.\r\n\r\n[1] http:\/\/en.wikibooks.org\/wiki\/Learning_vi:Vim#Onmi_Completion","package":"adacomplete.vim","4":"adacomplete.vim","src_id":"5778","5":"5778","creation_date":"1148715106","6":"1148715106"},{"0":"1554","vim_version":"7.0","1":"7.0","script_version":"2.0","2":"2.0","version_comment":"New coordinated release for all Ada plugins. Binary releases which are patched with all Ada plugins is available from the GNU Ada project [1]\r\n\r\n[1] http:\/\/gnuada.sourceforge.net","3":"New coordinated release for all Ada plugins. Binary releases which are patched with all Ada plugins is available from the GNU Ada project [1]\r\n\r\n[1] http:\/\/gnuada.sourceforge.net","package":"adacomplete.vim","4":"adacomplete.vim","src_id":"5764","5":"5764","creation_date":"1148548429","6":"1148548429"},{"0":"1554","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"adacomplete.vim","4":"adacomplete.vim","src_id":"5741","5":"5741","creation_date":"1148282594","6":"1148282594"}]},"1553":{"script_id":"1553","0":"1553","script_name":"autoproto.vim","1":"autoproto.vim","script_type":"utility","2":"utility","summary":"Auto display function parameter in preview","3":"Auto display function parameter in preview","description":"The \"autoproto\" plugin displays the function parameter\/prototypes\r\nin the preview window if you type a left parenthesis behind a function name.\r\nWith this plugin it is not necessary to memorize large parameter lists.\r\nYou do not need to leave insert mode. Typing is almost not affected. ","4":"The \"autoproto\" plugin displays the function parameter\/prototypes\r\nin the preview window if you type a left parenthesis behind a function name.\r\nWith this plugin it is not necessary to memorize large parameter lists.\r\nYou do not need to leave insert mode. Typing is almost not affected. ","install_details":"* Drop autoproto.vim into your plugin directory. \r\n\r\n* The script need a tag file to work:\r\n   - for your project: \":!ctags -R .\" (or use the gvim button)\r\n   - for library functions: \r\n     run: \"ctags -R -f ~\/.vim\/systags --c-kinds=+p \/usr\/include \/usr\/local\/include\"\r\n     put  \"set tags+=~\/.vim\/systags\" in your .vimrc file.\r\n\r\n* Open some *.c file and write for example: \"XCreateWindow (\"\r\n   (or \"XCreateWindow(\").\r\n   If the tag exist it will be shown in the preview window.\r\n   Note: only *.c files are supported ! The file must exist.   ","5":"* Drop autoproto.vim into your plugin directory. \r\n\r\n* The script need a tag file to work:\r\n   - for your project: \":!ctags -R .\" (or use the gvim button)\r\n   - for library functions: \r\n     run: \"ctags -R -f ~\/.vim\/systags --c-kinds=+p \/usr\/include \/usr\/local\/include\"\r\n     put  \"set tags+=~\/.vim\/systags\" in your .vimrc file.\r\n\r\n* Open some *.c file and write for example: \"XCreateWindow (\"\r\n   (or \"XCreateWindow(\").\r\n   If the tag exist it will be shown in the preview window.\r\n   Note: only *.c files are supported ! The file must exist.   ","first_name":"Jochen","6":"Jochen","last_name":"Baier","7":"Baier","releases":[{"0":"1553","vim_version":"7.0","1":"7.0","script_version":"0.06","2":"0.06","version_comment":"* Support for functions not ending with new line (-> between of text)","3":"* Support for functions not ending with new line (-> between of text)","package":"autoproto.vim","4":"autoproto.vim","src_id":"5846","5":"5846","creation_date":"1150798838","6":"1150798838"},{"0":"1553","vim_version":"7.0","1":"7.0","script_version":"0.05","2":"0.05","version_comment":"*set noignorecase during tag search: big performance boost if tag do not exist","3":"*set noignorecase during tag search: big performance boost if tag do not exist","package":"autoproto.vim","4":"autoproto.vim","src_id":"5809","5":"5809","creation_date":"1149682252","6":"1149682252"},{"0":"1553","vim_version":"7.0","1":"7.0","script_version":"0.04","2":"0.04","version_comment":"* Support for nested functions: Redisplay parent prototype if a function was used as a parameter.\r\n* skip numbers\r\n","3":"* Support for nested functions: Redisplay parent prototype if a function was used as a parameter.\r\n* skip numbers\r\n","package":"autoproto.vim","4":"autoproto.vim","src_id":"5790","5":"5790","creation_date":"1149166026","6":"1149166026"},{"0":"1553","vim_version":"6.0","1":"6.0","script_version":"0.03","2":"0.03","version_comment":"- Display found tag in the first line of the preview window.\r\n- some fixes","3":"- Display found tag in the first line of the preview window.\r\n- some fixes","package":"autoproto.vim","4":"autoproto.vim","src_id":"5748","5":"5748","creation_date":"1148391488","6":"1148391488"},{"0":"1553","vim_version":"6.0","1":"6.0","script_version":"0.02","2":"0.02","version_comment":"upps... small bug","3":"upps... small bug","package":"autoproto.vim","4":"autoproto.vim","src_id":"5739","5":"5739","creation_date":"1148219882","6":"1148219882"},{"0":"1553","vim_version":"6.0","1":"6.0","script_version":"0.01","2":"0.01","version_comment":"Initial upload","3":"Initial upload","package":"autoproto.vim","4":"autoproto.vim","src_id":"5738","5":"5738","creation_date":"1148218975","6":"1148218975"}]},"1552":{"script_id":"1552","0":"1552","script_name":"ScreenShot","1":"ScreenShot","script_type":"utility","2":"utility","summary":"ScreenShot.vim enables you make screenshot of your VIM session as HTML code.","3":"ScreenShot.vim enables you make screenshot of your VIM session as HTML code.","description":"ScreenShot.vim enables you generate HTML code for screenshot of all open windows at once.\r\nWindows layout will be preserved, and status line for every window will be displayed.\r\nIn other words, the resulted HTML will look the same as you VIM looks, with exception of menu, toolbar and other GUI items. \r\nHere(http:\/\/community.livejournal.com\/screenshot_vim\/4086.html) you can see a few examples.\r\n\r\nScreenShot.vim defines three commands:\r\n1) ScreenShot  -- to make screenshot itself\r\n2) Text2Html -- to generate HTML code for syntax highlighting of  peace of selected text  or of all current buffer if nothing selected. This command resemles standard command TOhtml, though has a few differences:\r\n   a) Generation of HTML code is designed in assumption that this code will occupy just a region of HTML page rather than all page, so it wrapped in <table> tag and has no <body> tag. Background color and default text color for this region of page will be setted properly.\r\n   b) Width of resulted HTML will be always equal to the width of current window. When 'wrap' setting is on, lines longer than the width of the window will wrap and  displaying continues on the next line.  When off lines will not wrap and only part of long lines will be displayed. So, you do not need to take in account long lines which may broke you page.\r\n   c) Foldcolumn will be displayed\r\n3) Diff2Html -- to display two files comparing with differencies highlighted. You may select any part of the first file, and obtain HTML code for this part and corresponding part of the second file separated with vertical split line.\r\n\r\nScreenShot.vim has a few global options which are stored in global dictionary g:ScreenShot:\r\n\r\ng:ScreenShot.Title -- is title bar enabled\r\ng:ScreenShot.Icon -- is VIM icon displayed in title bar (disabling of icon can significantly decrease size of document)\r\ng:ScreenShot.Credits -- are credits displayed\r\ng:ScreenShot.force_background -- force background color to some specific values \r\ng:ScreenShot.fill_screen -- force space from end of line to end of window to be filled with whitespaces(especially useful with command Text2Html to force highlighted text to occupy a region of HTML page with fixed width)\r\n\r\nColor should be specified as a string in HTML color format #RRGGBB. This option may be useful as there is no reliable method to find out background color for console versions of VIM.\r\n\r\nFor instance, if you want to disable icon and credits you should insert in your vimrc : \r\n\r\nlet ScreenShot = {'Icon':0, 'Credits':0, 'force_background':'#FFFFFF'}\r\n\r\nBy default all these options enabled.\r\n\r\n\r\n","4":"ScreenShot.vim enables you generate HTML code for screenshot of all open windows at once.\r\nWindows layout will be preserved, and status line for every window will be displayed.\r\nIn other words, the resulted HTML will look the same as you VIM looks, with exception of menu, toolbar and other GUI items. \r\nHere(http:\/\/community.livejournal.com\/screenshot_vim\/4086.html) you can see a few examples.\r\n\r\nScreenShot.vim defines three commands:\r\n1) ScreenShot  -- to make screenshot itself\r\n2) Text2Html -- to generate HTML code for syntax highlighting of  peace of selected text  or of all current buffer if nothing selected. This command resemles standard command TOhtml, though has a few differences:\r\n   a) Generation of HTML code is designed in assumption that this code will occupy just a region of HTML page rather than all page, so it wrapped in <table> tag and has no <body> tag. Background color and default text color for this region of page will be setted properly.\r\n   b) Width of resulted HTML will be always equal to the width of current window. When 'wrap' setting is on, lines longer than the width of the window will wrap and  displaying continues on the next line.  When off lines will not wrap and only part of long lines will be displayed. So, you do not need to take in account long lines which may broke you page.\r\n   c) Foldcolumn will be displayed\r\n3) Diff2Html -- to display two files comparing with differencies highlighted. You may select any part of the first file, and obtain HTML code for this part and corresponding part of the second file separated with vertical split line.\r\n\r\nScreenShot.vim has a few global options which are stored in global dictionary g:ScreenShot:\r\n\r\ng:ScreenShot.Title -- is title bar enabled\r\ng:ScreenShot.Icon -- is VIM icon displayed in title bar (disabling of icon can significantly decrease size of document)\r\ng:ScreenShot.Credits -- are credits displayed\r\ng:ScreenShot.force_background -- force background color to some specific values \r\ng:ScreenShot.fill_screen -- force space from end of line to end of window to be filled with whitespaces(especially useful with command Text2Html to force highlighted text to occupy a region of HTML page with fixed width)\r\n\r\nColor should be specified as a string in HTML color format #RRGGBB. This option may be useful as there is no reliable method to find out background color for console versions of VIM.\r\n\r\nFor instance, if you want to disable icon and credits you should insert in your vimrc : \r\n\r\nlet ScreenShot = {'Icon':0, 'Credits':0, 'force_background':'#FFFFFF'}\r\n\r\nBy default all these options enabled.\r\n\r\n\r\n","install_details":"Just copy to $VIMRUNTIME\/plugin directory","5":"Just copy to $VIMRUNTIME\/plugin directory","first_name":"Michael","6":"Michael","last_name":"Schwarz","7":"Schwarz","releases":[{"0":"1552","vim_version":"7.0","1":"7.0","script_version":"1.07","2":"1.07","version_comment":"    1.07:\r\n        Html size optimized\r\n    Fixed:\r\n        1. Status line %V item\r\n        2. Proper embedding in HTML page with defined default color","3":"    1.07:\r\n        Html size optimized\r\n    Fixed:\r\n        1. Status line %V item\r\n        2. Proper embedding in HTML page with defined default color","package":"ScreenShot.vim","4":"ScreenShot.vim","src_id":"6931","5":"6931","creation_date":"1175468774","6":"1175468774"},{"0":"1552","vim_version":"7.0","1":"7.0","script_version":"1.06","2":"1.06","version_comment":"1.06:\r\n      Fixed:\r\n        1. Folds are displayed correctly now(was broken in 1.05)\r\n        2. Unprintable unicode chracters are displayed correctly now\r\n1.05:\r\n      Added:\r\n        Good multibyte support(thanks Cyril Slobin <slobin@ice.ru> for suggestion)\r\n ","3":"1.06:\r\n      Fixed:\r\n        1. Folds are displayed correctly now(was broken in 1.05)\r\n        2. Unprintable unicode chracters are displayed correctly now\r\n1.05:\r\n      Added:\r\n        Good multibyte support(thanks Cyril Slobin <slobin@ice.ru> for suggestion)\r\n ","package":"ScreenShot.vim","4":"ScreenShot.vim","src_id":"6850","5":"6850","creation_date":"1173287403","6":"1173287403"},{"0":"1552","vim_version":"7.0","1":"7.0","script_version":"1.04","2":"1.04","version_comment":"|1.04:\r\n|Fixed:\r\n|    1. Proper colors for DOS and win32 console versions(suggestion by Cyril Slobin <slobin@ice.ru>)\r\n|    2. Black color is now default for background in console, even if no\r\n|       \"reverse\" attribute set, because it is typical behaviour of terminals.\r\n|Added:\r\n|    3. 'force_background' option \r\n|\r\n|1.03: A few bugfixes by Cyril Slobin <slobin@ice.ru>\r\n|Added:\r\n|    7. Support for 256-color xterm\r\n|\r\n|1.0:\r\n|Added:\r\n|    1. Diff mode support\r\n|    2. New command Diff2Html\r\n\r\n","3":"|1.04:\r\n|Fixed:\r\n|    1. Proper colors for DOS and win32 console versions(suggestion by Cyril Slobin <slobin@ice.ru>)\r\n|    2. Black color is now default for background in console, even if no\r\n|       \"reverse\" attribute set, because it is typical behaviour of terminals.\r\n|Added:\r\n|    3. 'force_background' option \r\n|\r\n|1.03: A few bugfixes by Cyril Slobin <slobin@ice.ru>\r\n|Added:\r\n|    7. Support for 256-color xterm\r\n|\r\n|1.0:\r\n|Added:\r\n|    1. Diff mode support\r\n|    2. New command Diff2Html\r\n\r\n","package":"ScreenShot.vim","4":"ScreenShot.vim","src_id":"6843","5":"6843","creation_date":"1173191233","6":"1173191233"},{"0":"1552","vim_version":"7.0","1":"7.0","script_version":"0.9","2":"0.9","version_comment":"Added:\r\n1)Custom statusline (i.e. 'stl' option support)\r\n2)Tabline bar(only for console or if 'guioptions' does not contain 'e'). Custom tabline also supported .\r\n3)Title bar with VIM logo (can be disabled). Custom title(i.e. option 'titlestring') also supported\r\n4)Credits in right bottom corner(can be disabled)\r\n5)A few global settings in dictionary g:ScreenShot\r\nRemoved:\r\nAn extra VertSplit line in the very right","3":"Added:\r\n1)Custom statusline (i.e. 'stl' option support)\r\n2)Tabline bar(only for console or if 'guioptions' does not contain 'e'). Custom tabline also supported .\r\n3)Title bar with VIM logo (can be disabled). Custom title(i.e. option 'titlestring') also supported\r\n4)Credits in right bottom corner(can be disabled)\r\n5)A few global settings in dictionary g:ScreenShot\r\nRemoved:\r\nAn extra VertSplit line in the very right","package":"ScreenShot.vim","4":"ScreenShot.vim","src_id":"5833","5":"5833","creation_date":"1150274600","6":"1150274600"}]},"1551":{"script_id":"1551","0":"1551","script_name":"Simple Color Scheme","1":"Simple Color Scheme","script_type":"color scheme","2":"color scheme","summary":"Light blue background and simple","3":"Light blue background and simple","description":"This scheme is derived from print_bw and,While maintaining the simplicity of print_bw it has low contrast.","4":"This scheme is derived from print_bw and,While maintaining the simplicity of print_bw it has low contrast.","install_details":"Drop it in color folder.","5":"Drop it in color folder.","first_name":"vijayandra","6":"vijayandra","last_name":"singh","7":"singh","releases":[{"0":"1551","vim_version":"7.0","1":"7.0","script_version":"1.00","2":"1.00","version_comment":"Initial upload","3":"Initial upload","package":"simple_b.vim","4":"simple_b.vim","src_id":"5726","5":"5726","creation_date":"1148023688","6":"1148023688"}]},"1550":{"script_id":"1550","0":"1550","script_name":"jVim","1":"jVim","script_type":"utility","2":"utility","summary":"A vim plugin which tries to make vim's keys compatible with other editors.","3":"A vim plugin which tries to make vim's keys compatible with other editors.","description":"I tried to make vim a bit compatible with my old editors, so I maped CTRL+C, CTRL+V, CTRL+Y to copy, paste, del and so on, made Shift+Arrows work in insert mode as \"v\" does in normal mode, popup auto complete menu as you type, map CTRL+Right, CTRL+Left to next\/prev buffer in normal mode, CTRL+N, CTRL+x to new\/del buffer, and some custom settings.\r\n\r\nSee here for more:\r\nhttp:\/\/pijulius.blogspot.com\/2006\/05\/jvimvim.html\r\n\r\nDon't misunderstand me, I really like vim keys, but for now I needed some compatibility with my old editor, so I thought it may be useful for someone too.\r\n\r\nAny feedback\/addition\/note\/idea is more than welcome.","4":"I tried to make vim a bit compatible with my old editors, so I maped CTRL+C, CTRL+V, CTRL+Y to copy, paste, del and so on, made Shift+Arrows work in insert mode as \"v\" does in normal mode, popup auto complete menu as you type, map CTRL+Right, CTRL+Left to next\/prev buffer in normal mode, CTRL+N, CTRL+x to new\/del buffer, and some custom settings.\r\n\r\nSee here for more:\r\nhttp:\/\/pijulius.blogspot.com\/2006\/05\/jvimvim.html\r\n\r\nDon't misunderstand me, I really like vim keys, but for now I needed some compatibility with my old editor, so I thought it may be useful for someone too.\r\n\r\nAny feedback\/addition\/note\/idea is more than welcome.","install_details":"Just copy jvim.vim to your plugin directory (usually ~\/.vim\/plugin\/)","5":"Just copy jvim.vim to your plugin directory (usually ~\/.vim\/plugin\/)","first_name":"P.I.","6":"P.I.","last_name":"Julius","7":"Julius","releases":[{"0":"1550","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"jvim.vim","4":"jvim.vim","src_id":"5723","5":"5723","creation_date":"1148005152","6":"1148005152"}]},"1549":{"script_id":"1549","0":"1549","script_name":"bluez","1":"bluez","script_type":"color scheme","2":"color scheme","summary":"Dark blueish coloscheme for urxvt  (keywords: urxvt cterm 88 color)","3":"Dark blueish coloscheme for urxvt  (keywords: urxvt cterm 88 color)","description":"Dark eye resting coloscheme designed for use in urxvt or urxvt\/screen terminals.\r\nIt makes heavy use of the 88 colors available in this environment and it will not work in any other environment e.g. xterm or gui.\r\n\r\nYou can set a transparent background by adding\r\n\r\n'let g:bluez_transbg=1' \r\n\r\nto your vimrc.","4":"Dark eye resting coloscheme designed for use in urxvt or urxvt\/screen terminals.\r\nIt makes heavy use of the 88 colors available in this environment and it will not work in any other environment e.g. xterm or gui.\r\n\r\nYou can set a transparent background by adding\r\n\r\n'let g:bluez_transbg=1' \r\n\r\nto your vimrc.","install_details":"","5":"","first_name":"Ren\u00c3\u00a9","6":"Ren\u00c3\u00a9","last_name":"K\u00c3\u00b6cher","7":"K\u00c3\u00b6cher","releases":[{"0":"1549","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"bluez.vim","4":"bluez.vim","src_id":"5718","5":"5718","creation_date":"1147927016","6":"1147927016"}]},"1548":{"script_id":"1548","0":"1548","script_name":"ftplugin\/ada.vim","1":"ftplugin\/ada.vim","script_type":"syntax","2":"syntax","summary":"Filetype plugin for Ada (inactive, replaced by vimscript#1609)","3":"Filetype plugin for Ada (inactive, replaced by vimscript#1609)","description":"This plugin is superseded by vimscript#1609 and https:\/\/github.com\/krischik\/Ad-Bundle.","4":"This plugin is superseded by vimscript#1609 and https:\/\/github.com\/krischik\/Ad-Bundle.","install_details":"Install from https:\/\/github.com\/krischik\/Ad-Bundle using dein (https:\/\/github.com\/Shougo\/dein.vim) or similar:\r\n\r\ncall dein#begin('\/Users\/martin\/vimfiles\/bundles')\r\ncall dein#add('krischik\/Ada-Bundle')\r\ncall dein#end()\r\ncall dein#install()","5":"Install from https:\/\/github.com\/krischik\/Ad-Bundle using dein (https:\/\/github.com\/Shougo\/dein.vim) or similar:\r\n\r\ncall dein#begin('\/Users\/martin\/vimfiles\/bundles')\r\ncall dein#add('krischik\/Ada-Bundle')\r\ncall dein#end()\r\ncall dein#install()","first_name":"Martin","6":"Martin","last_name":"Krischik","7":"Krischik","releases":[{"0":"1548","vim_version":"7.0","1":"7.0","script_version":"2.1","2":"2.1","version_comment":"Some correction regarding the use of attributes. Correct use of the ' is a bit tricky.","3":"Some correction regarding the use of attributes. Correct use of the ' is a bit tricky.","package":"ada.vim","4":"ada.vim","src_id":"5780","5":"5780","creation_date":"1148715112","6":"1148715112"},{"0":"1548","vim_version":"7.0","1":"7.0","script_version":"2.0","2":"2.0","version_comment":"New coordinated release for all Ada plugins. Binary releases which are patched with all Ada plugins is available from the GNU Ada project [1]\r\n\r\n[1] http:\/\/gnuada.sourceforge.net","3":"New coordinated release for all Ada plugins. Binary releases which are patched with all Ada plugins is available from the GNU Ada project [1]\r\n\r\n[1] http:\/\/gnuada.sourceforge.net","package":"ada.vim","4":"ada.vim","src_id":"5763","5":"5763","creation_date":"1148548423","6":"1148548423"},{"0":"1548","vim_version":"7.0","1":"7.0","script_version":"1.1","2":"1.1","version_comment":"Exteneded for the omnicompletions plugin.\r\n\r\n","3":"Exteneded for the omnicompletions plugin.\r\n\r\n","package":"ada.vim","4":"ada.vim","src_id":"5742","5":"5742","creation_date":"1148282880","6":"1148282880"},{"0":"1548","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"ada.vim","4":"ada.vim","src_id":"5713","5":"5713","creation_date":"1147852986","6":"1147852986"}]},"1547":{"script_id":"1547","0":"1547","script_name":"compiler\/gnat.vim","1":"compiler\/gnat.vim","script_type":"utility","2":"utility","summary":"Compiler setup for GNAT (inactive, replaced by vimscript#1609)","3":"Compiler setup for GNAT (inactive, replaced by vimscript#1609)","description":"This plugin is superseded by vimscript#1609 and https:\/\/github.com\/krischik\/Ad-Bundle.","4":"This plugin is superseded by vimscript#1609 and https:\/\/github.com\/krischik\/Ad-Bundle.","install_details":"Install from https:\/\/github.com\/krischik\/Ad-Bundle using dein (https:\/\/github.com\/Shougo\/dein.vim) or similar:\r\n\r\ncall dein#begin('\/Users\/martin\/vimfiles\/bundles')\r\ncall dein#add('krischik\/Ada-Bundle')\r\ncall dein#end()\r\ncall dein#install()","5":"Install from https:\/\/github.com\/krischik\/Ad-Bundle using dein (https:\/\/github.com\/Shougo\/dein.vim) or similar:\r\n\r\ncall dein#begin('\/Users\/martin\/vimfiles\/bundles')\r\ncall dein#add('krischik\/Ada-Bundle')\r\ncall dein#end()\r\ncall dein#install()","first_name":"Martin","6":"Martin","last_name":"Krischik","7":"Krischik","releases":[{"0":"1547","vim_version":"7.0","1":"7.0","script_version":"2.0","2":"2.0","version_comment":"New coordinated release for all Ada plugins. Binary releases which are patched with all Ada plugins is available from the GNU Ada project [1]\r\n\r\n[1] http:\/\/gnuada.sourceforge.net","3":"New coordinated release for all Ada plugins. Binary releases which are patched with all Ada plugins is available from the GNU Ada project [1]\r\n\r\n[1] http:\/\/gnuada.sourceforge.net","package":"gnat.vim","4":"gnat.vim","src_id":"5761","5":"5761","creation_date":"1148548418","6":"1148548418"},{"0":"1547","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"gnat.vim","4":"gnat.vim","src_id":"5712","5":"5712","creation_date":"1147852394","6":"1147852394"}]},"1546":{"script_id":"1546","0":"1546","script_name":"perl_search_lib","1":"perl_search_lib","script_type":"ftplugin","2":"ftplugin","summary":"update &l:path by tokens from perl \"use lib\" sentence","3":"update &l:path by tokens from perl \"use lib\" sentence","description":"this is after plugin.","4":"this is after plugin.","install_details":"put archive content to your vim after-directory","5":"put archive content to your vim after-directory","first_name":"Afanasov","6":"Afanasov","last_name":"Dmitry","7":"Dmitry","releases":[{"0":"1546","vim_version":"6.0","1":"6.0","script_version":"0.3","2":"0.3","version_comment":"fixed bug with switching buffers: ftplugin\/perl.vim is executed every time user switching buf and reset l:path.\r\n\r\nadded global variable perl_local_path","3":"fixed bug with switching buffers: ftplugin\/perl.vim is executed every time user switching buf and reset l:path.\r\n\r\nadded global variable perl_local_path","package":"perl_search_lib.tar.bz2","4":"perl_search_lib.tar.bz2","src_id":"5717","5":"5717","creation_date":"1147919683","6":"1147919683"},{"0":"1546","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"perl_search_lib.tar.bz2","4":"perl_search_lib.tar.bz2","src_id":"5709","5":"5709","creation_date":"1147842698","6":"1147842698"}]},"1545":{"script_id":"1545","0":"1545","script_name":"abolish.vim","1":"abolish.vim","script_type":"utility","2":"utility","summary":"Work with several variants of a word at once","3":"Work with several variants of a word at once","description":"This is a plugin over 3 years in the making that I've deferred releasing, primarily because it's so gosh darn hard to explain.  It's three superficially unrelated plugins in one that share a common theme: working with variants of a word.\r\n\r\nABBREVIATION\r\n\r\nI know how to spell separate.  I know how to spell desperate.  My fingers, however, have trouble distinguishing between the two, and I invariably have a 50 percent chance of typing seperate or desparate each time one of these comes up.  At first, I tried abbreviations:\r\n\r\niabbrev  seperate  separate\r\niabbrev desparate desperate \r\n\r\nBut this falls short at the beginning of a sentence.\r\n\r\niabbrev  Seperate  Separate\r\niabbrev Desparate Desperate \r\n\r\nTo be really thorough, we need uppercase too!\r\n\r\niabbrev  SEPERATE  SEPARATE\r\niabbrev DESPARATE DESPERATE \r\n\r\nOh, but consider the noun form, and the adverb form!\r\n\r\niabbrev  seperation  separation\r\niabbrev desparation desperation \r\niabbrev  seperately  separately\r\niabbrev desparately desperately \r\niabbrev  Seperation  separation\r\niabbrev Desparation Desperation \r\niabbrev  Seperately  Separately\r\niabbrev Desparately Desperately \r\niabbrev  SEPERATION  SEPARATION\r\niabbrev DESPARATION DESPERATION \r\niabbrev  SEPERATELY  SEPARATELY\r\niabbrev DESPARATELY DESPERATELY \r\n\r\nWait, there's also separates, separated, separating, separations, separator...\r\n\r\nAbolish.vim provides a simpler way.  The following one command produces 48 abbreviations including all of the above.\r\n\r\nAbolish {despa,sepe}rat{e,es,ed,ing,ely,ion,ions,or}  {despe,sepa}rat{}\r\n\r\nMy current configuration has 25 Abolish commands that create hundreds of corrections my fingers refuse to learn.\r\n\r\nSUBSTITUTION\r\n\r\nOne time I had an application that with a domain model called \"facilities\" that needed to be renamed to \"buildings\". So, a simple search and replace, right?\r\n\r\n:%s\/facility\/building\/g\r\n\r\nOh, but the case variants!\r\n\r\n:%s\/Facility\/Building\/g\r\n:%s\/FACILITY\/BUILDING\/g\r\n\r\nWait, the plural is more than \"s\" so we need to get that too!\r\n\r\n:%s\/facilities\/buildings\/g\r\n:%s\/Facilities\/Buildings\/g\r\n:%s\/FACILITIES\/BUILDINGS\/g\r\n\r\nAbolish.vim has your back.  One command to do all six, and you can repeat it with & too!\r\n\r\n:%Subvert\/facilit{y,ies}\/building{,s}\/g\r\n\r\nYou can abbreviate it as :S, and it accepts the full range of flags including\r\nthings like c (confirm).\r\n\r\nThere's also a variant for searching and a variant for grepping.\r\n\r\nCOERCION\r\n\r\nWant to turn fooBar into foo_bar?  Press crs (coerce to snake_case).\r\nMixedCase, camelCase, snake_case, and UPPER_CASE are all just 3 keystrokes\r\naway.\r\n","4":"This is a plugin over 3 years in the making that I've deferred releasing, primarily because it's so gosh darn hard to explain.  It's three superficially unrelated plugins in one that share a common theme: working with variants of a word.\r\n\r\nABBREVIATION\r\n\r\nI know how to spell separate.  I know how to spell desperate.  My fingers, however, have trouble distinguishing between the two, and I invariably have a 50 percent chance of typing seperate or desparate each time one of these comes up.  At first, I tried abbreviations:\r\n\r\niabbrev  seperate  separate\r\niabbrev desparate desperate \r\n\r\nBut this falls short at the beginning of a sentence.\r\n\r\niabbrev  Seperate  Separate\r\niabbrev Desparate Desperate \r\n\r\nTo be really thorough, we need uppercase too!\r\n\r\niabbrev  SEPERATE  SEPARATE\r\niabbrev DESPARATE DESPERATE \r\n\r\nOh, but consider the noun form, and the adverb form!\r\n\r\niabbrev  seperation  separation\r\niabbrev desparation desperation \r\niabbrev  seperately  separately\r\niabbrev desparately desperately \r\niabbrev  Seperation  separation\r\niabbrev Desparation Desperation \r\niabbrev  Seperately  Separately\r\niabbrev Desparately Desperately \r\niabbrev  SEPERATION  SEPARATION\r\niabbrev DESPARATION DESPERATION \r\niabbrev  SEPERATELY  SEPARATELY\r\niabbrev DESPARATELY DESPERATELY \r\n\r\nWait, there's also separates, separated, separating, separations, separator...\r\n\r\nAbolish.vim provides a simpler way.  The following one command produces 48 abbreviations including all of the above.\r\n\r\nAbolish {despa,sepe}rat{e,es,ed,ing,ely,ion,ions,or}  {despe,sepa}rat{}\r\n\r\nMy current configuration has 25 Abolish commands that create hundreds of corrections my fingers refuse to learn.\r\n\r\nSUBSTITUTION\r\n\r\nOne time I had an application that with a domain model called \"facilities\" that needed to be renamed to \"buildings\". So, a simple search and replace, right?\r\n\r\n:%s\/facility\/building\/g\r\n\r\nOh, but the case variants!\r\n\r\n:%s\/Facility\/Building\/g\r\n:%s\/FACILITY\/BUILDING\/g\r\n\r\nWait, the plural is more than \"s\" so we need to get that too!\r\n\r\n:%s\/facilities\/buildings\/g\r\n:%s\/Facilities\/Buildings\/g\r\n:%s\/FACILITIES\/BUILDINGS\/g\r\n\r\nAbolish.vim has your back.  One command to do all six, and you can repeat it with & too!\r\n\r\n:%Subvert\/facilit{y,ies}\/building{,s}\/g\r\n\r\nYou can abbreviate it as :S, and it accepts the full range of flags including\r\nthings like c (confirm).\r\n\r\nThere's also a variant for searching and a variant for grepping.\r\n\r\nCOERCION\r\n\r\nWant to turn fooBar into foo_bar?  Press crs (coerce to snake_case).\r\nMixedCase, camelCase, snake_case, and UPPER_CASE are all just 3 keystrokes\r\naway.\r\n","install_details":"Extract in ~\/.vim or ~\\vimfiles.\r\n\r\nGrab the very latest from http:\/\/github.com\/tpope\/vim-abolish","5":"Extract in ~\/.vim or ~\\vimfiles.\r\n\r\nGrab the very latest from http:\/\/github.com\/tpope\/vim-abolish","first_name":"Tim","6":"Tim","last_name":"Pope","7":"Pope","releases":[{"0":"1545","vim_version":"7.0","1":"7.0","script_version":"1.2","2":"1.2","version_comment":"Add coercions for \"space case\" (cr<Space>) and \"Title Case\" (crt).\r\nAdd \"PascalCase\" (crp) coercion alias for \"MixedCase\" (crm).\r\nDrop dependence on repeat.vim.","3":"Add coercions for \"space case\" (cr<Space>) and \"Title Case\" (crt).\r\nAdd \"PascalCase\" (crp) coercion alias for \"MixedCase\" (crm).\r\nDrop dependence on repeat.vim.","package":"abolish.zip","4":"abolish.zip","src_id":"28371","5":"28371","creation_date":"1677384891","6":"1677384891"},{"0":"1545","vim_version":"7.0","1":"7.0","script_version":"1.1","2":"1.1","version_comment":"Add . dot case coercion.\r\nAdd U alias for uppercase coercion.\r\nAdd k \"kebab\" alias for dash case coercion.\r\nFix issues with coercion to dash case.\r\nFix issues with 'clipboard' option.\r\nFix abbreviation persistence.\r\nEscape magic characters in substitution.","3":"Add . dot case coercion.\r\nAdd U alias for uppercase coercion.\r\nAdd k \"kebab\" alias for dash case coercion.\r\nFix issues with coercion to dash case.\r\nFix issues with 'clipboard' option.\r\nFix abbreviation persistence.\r\nEscape magic characters in substitution.","package":"abolish.zip","4":"abolish.zip","src_id":"23347","5":"23347","creation_date":"1433290068","6":"1433290068"},{"0":"1545","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"abolish.zip","4":"abolish.zip","src_id":"11499","5":"11499","creation_date":"1255046736","6":"1255046736"}]},"1544":{"script_id":"1544","0":"1544","script_name":"foxpro.vim","1":"foxpro.vim","script_type":"syntax","2":"syntax","summary":"syntax file for MS Foxpro v2.6 for DOS & UNIX","3":"syntax file for MS Foxpro v2.6 for DOS & UNIX","description":"Starting from the original foxpro.vim maintained by Powing Tse <powing@mcmug.org>, this version has been updated to include highlighting for proper Codebook variable naming. An issue with comments has also been corrected.","4":"Starting from the original foxpro.vim maintained by Powing Tse <powing@mcmug.org>, this version has been updated to include highlighting for proper Codebook variable naming. An issue with comments has also been corrected.","install_details":"place this file in the syntax directory","5":"place this file in the syntax directory","first_name":"Bill W.","6":"Bill W.","last_name":"Smith, Jr.","7":"Smith, Jr.","releases":[{"0":"1544","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"foxpro.vim","4":"foxpro.vim","src_id":"5701","5":"5701","creation_date":"1147694249","6":"1147694249"}]},"1543":{"script_id":"1543","0":"1543","script_name":"Tabline wrapping patch","1":"Tabline wrapping patch","script_type":"utility","2":"utility","summary":"Allows tabline strings to wrap onto new lines","3":"Allows tabline strings to wrap onto new lines","description":"When compiled with this patch, Vim will allow the strings delivered via the 'tabline' option to wrap onto new lines.  It is up to the 'tabline' string or function to limit itself.   See TabLineSet.vim for an example of  a script which does this.","4":"When compiled with this patch, Vim will allow the strings delivered via the 'tabline' option to wrap onto new lines.  It is up to the 'tabline' string or function to limit itself.   See TabLineSet.vim for an example of  a script which does this.","install_details":"It's a zip file with .patch files in it :-)","5":"It's a zip file with .patch files in it :-)","first_name":"Eric","6":"Eric","last_name":"Arnold","7":"Arnold","releases":[{"0":"1543","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"tabline_wrap.zip","4":"tabline_wrap.zip","src_id":"5692","5":"5692","creation_date":"1147600445","6":"1147600445"}]},"1542":{"script_id":"1542","0":"1542","script_name":"pythoncomplete","1":"pythoncomplete","script_type":"ftplugin","2":"ftplugin","summary":"Python Omni Completion","3":"Python Omni Completion","description":"This is the pythoncomplete omni-completion script shipped with vim 7.  Updated versions will appear here, as the vim tarballs do not ship with updated runtime files.\r\n\r\nTo use this plugin, make sure ftplugins are enabled, via \"filetype plugin on\".\r\nFiletype detection will set the omnifunction appropriately.\r\n\r\nFeatures:\r\n   Dynamic type deduction (without actually evaluating statements)\r\n   Local visibility handling (will complete from all parent scopes).\r\n   completeopt=preview support, displaying python docstrings\r\n   Function argument completion (whenever possible)\r\n\r\nRequires Vim7 compiled with +python support.","4":"This is the pythoncomplete omni-completion script shipped with vim 7.  Updated versions will appear here, as the vim tarballs do not ship with updated runtime files.\r\n\r\nTo use this plugin, make sure ftplugins are enabled, via \"filetype plugin on\".\r\nFiletype detection will set the omnifunction appropriately.\r\n\r\nFeatures:\r\n   Dynamic type deduction (without actually evaluating statements)\r\n   Local visibility handling (will complete from all parent scopes).\r\n   completeopt=preview support, displaying python docstrings\r\n   Function argument completion (whenever possible)\r\n\r\nRequires Vim7 compiled with +python support.","install_details":"Place this file in ~\/.vim\/autoload\/ or $VIMRUNTIME\/autoload\/","5":"Place this file in ~\/.vim\/autoload\/ or $VIMRUNTIME\/autoload\/","first_name":"aaron","6":"aaron","last_name":"griffin","7":"griffin","releases":[{"0":"1542","vim_version":"7.0","1":"7.0","script_version":"0.9","2":"0.9","version_comment":"NOTE: This is a re-upload. Previous version had old version\/updated headers still\r\n\r\n* Fixed docstring parsing for classes and functions\r\n* Fixed parsing of *args and **kwargs type arguments\r\n* Better function param parsing to handle things like tuples and lambda defaults args\r\n","3":"NOTE: This is a re-upload. Previous version had old version\/updated headers still\r\n\r\n* Fixed docstring parsing for classes and functions\r\n* Fixed parsing of *args and **kwargs type arguments\r\n* Better function param parsing to handle things like tuples and lambda defaults args\r\n","package":"pythoncomplete.vim","4":"pythoncomplete.vim","src_id":"10872","5":"10872","creation_date":"1245356897","6":"1245356897"},{"0":"1542","vim_version":"7.0","1":"7.0","script_version":"0.8","2":"0.8","version_comment":"* Fixed an issue where the FIRST assignment was always used instead of using a subsequent assignment for a variable\r\n* Fixed a scoping issue when working inside a parameterless function","3":"* Fixed an issue where the FIRST assignment was always used instead of using a subsequent assignment for a variable\r\n* Fixed a scoping issue when working inside a parameterless function","package":"pythoncomplete.vim","4":"pythoncomplete.vim","src_id":"7766","5":"7766","creation_date":"1191862812","6":"1191862812"},{"0":"1542","vim_version":"7.0","1":"7.0","script_version":"0.7","2":"0.7","version_comment":"* Fixed function list sorting (_ and __ at the bottom)\r\n* Removed newline removal from docs.  It appears vim handles\r\n  these better in recent patches","3":"* Fixed function list sorting (_ and __ at the bottom)\r\n* Removed newline removal from docs.  It appears vim handles\r\n  these better in recent patches","package":"pythoncomplete.vim","4":"pythoncomplete.vim","src_id":"6300","5":"6300","creation_date":"1161265647","6":"1161265647"},{"0":"1542","vim_version":"7.0","1":"7.0","script_version":"0.6","2":"0.6","version_comment":"Bug fix version:\r\n* Fixed argument completion\r\n* Removed the 'kind' completions, as they are better indicated with real syntax\r\n* Added tuple assignment parsing (whoops, that was forgotten)\r\n* Fixed import handling when flattening scope (visiblity)\r\n","3":"Bug fix version:\r\n* Fixed argument completion\r\n* Removed the 'kind' completions, as they are better indicated with real syntax\r\n* Added tuple assignment parsing (whoops, that was forgotten)\r\n* Fixed import handling when flattening scope (visiblity)\r\n","package":"pythoncomplete.vim","4":"pythoncomplete.vim","src_id":"5690","5":"5690","creation_date":"1147569038","6":"1147569038"},{"0":"1542","vim_version":"7.0","1":"7.0","script_version":"0.5","2":"0.5","version_comment":"Initial upload","3":"Initial upload","package":"pythoncomplete.vim","4":"pythoncomplete.vim","src_id":"5689","5":"5689","creation_date":"1147568924","6":"1147568924"}]},"1541":{"script_id":"1541","0":"1541","script_name":"GetChar event patch","1":"GetChar event patch","script_type":"utility","2":"utility","summary":"Adds a new event intercepting char reads","3":"Adds a new event intercepting char reads","description":"When compiled with this patch, Vim will have a new event, \"GetChar\".\r\n\r\nThe doc page patch:\r\n\r\n\r\n                            *GetChar*\r\nGetChar             Called immediately after a character is\r\n                received from the user or typeahead buffer,\r\n                and before it is processed.  The character is\r\n                available in the |v:getchar| variable as a\r\n                string (not a number).  Changing |v:getchar|\r\n                changes the value returned by the\r\n                |getchar()|function.  The |v:getchartype|\r\n                variable can be blank, 'KeyTyped', or\r\n                'KeyStuffed', depending on how the character\r\n                was obtained.  Setting |v:getchar| to ''\r\n                essentially skips the current character.\r\n","4":"When compiled with this patch, Vim will have a new event, \"GetChar\".\r\n\r\nThe doc page patch:\r\n\r\n\r\n                            *GetChar*\r\nGetChar             Called immediately after a character is\r\n                received from the user or typeahead buffer,\r\n                and before it is processed.  The character is\r\n                available in the |v:getchar| variable as a\r\n                string (not a number).  Changing |v:getchar|\r\n                changes the value returned by the\r\n                |getchar()|function.  The |v:getchartype|\r\n                variable can be blank, 'KeyTyped', or\r\n                'KeyStuffed', depending on how the character\r\n                was obtained.  Setting |v:getchar| to ''\r\n                essentially skips the current character.\r\n","install_details":"Apply the patches to the source files, and check out the test script.\r\n","5":"Apply the patches to the source files, and check out the test script.\r\n","first_name":"Eric","6":"Eric","last_name":"Arnold","7":"Arnold","releases":[{"0":"1541","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"getchar_event.zip","4":"getchar_event.zip","src_id":"5688","5":"5688","creation_date":"1147500765","6":"1147500765"}]},"1540":{"script_id":"1540","0":"1540","script_name":"mousefunc option patch","1":"mousefunc option patch","script_type":"utility","2":"utility","summary":"Patch set to create a mousefunc option","3":"Patch set to create a mousefunc option","description":"When compiled with this patch set, gvim will have a new option, \"mousefunc\" which will call a user script function for every mouse event.\r\n\r\nThe zip file contains a test script which demonstrates how to do things like:\r\n\r\n\r\n\" This script tests various aspects of the \"mousefunc\" option:\r\n\"\r\n\" - demonstrate having the mouse move tabs in the tabline.\r\n\"\r\n\" - text hotspots:\tHere is mouseover |tag1| and here is |tag2|\r\n\"\r\n\" - verbose option which shows all mouse info.\r\n\"\r\n\" - mouse-follow highlighting (set s:show_bullseye)\r\n\"\r\n\" - associate actions with clicking on statusline words\r\n\r\n\r\n\r\n\r\n\r\nFrom the options.txt doc file:\r\n\r\n\r\n'mousefunc' 'mfn'\tstring\t(default empty)\r\n\t\t\tglobal\r\n\t\t\t{not in Vi}\r\n\tWhen nonempty, this option calls the given function when mouse events\r\n\t(click, drag, move, etc.) are detected.  The function should accept\r\n\tthese arguments:\r\n>\r\n\t\tMouseFunc(\tmouse_key, \r\n\t\t\t\t\\ buf_row, buf_col, buf_vcol, \r\n\t\t\t\t\\ mouse_row, mouse_col, \r\n\t\t\t\t\\ x, y,\r\n\t\t\t\t\\ area, screen_line )\r\n<\r\n\t\"mouse_key\" is a string containing up to 6 chars.  It will match\r\n\tagainst a string like:   a:mouse_key == \"\\<LeftMouse>\".\r\n\t\"mouse_key\" can be empty, particularly when cursor-move-only events\r\n\tare delivered.  \r\n\r\n\t\"buf_row\/col\/vcol\" should match line(\".\") and col(\".\") if you were\r\n\tto click in a buffer at that point.\r\n\r\n\t\"mouse_row\/col\" are independent of windows and buffers.\r\n\t\r\n\tThe \"x\" and \"y\" are in pixels, and can be negative, when that\r\n\tinformation isn't available (see also |mousefocus| to have \"x\" and\r\n\t\"y\" track the mouse cursor).  \r\n\r\n\t\"area\" is Vim's idea of where the mouse is.  Values can be:\r\n\t\"IN_BUFFER\", \"IN_UNKNOWN\", \"IN_SEP_LINE\", \"IN_STATUS_LINE\".\r\n\r\n\t\"screen_line\" contains the literal characters in \"mouse_row\" which\r\n\thave been written to the screen, rather than any buffer.  Useful to\r\n\tread what's on the statusline, tabline, and command line areas.\r\n\t\r\n\tThe function should return 0 to consume the mouse click, or 1 to\r\n\tpass it on transparently.\r\n\r\n\tThe |mousefunc| option is set empty for the duration of the call to\r\n\tprevent recursion.  Setting it again during the call could have\r\n\tunexpected problems.\r\n\r\n\tIt intercepts the mouse events at a low level, which has its good\r\n\tand bad points.  The good is that you get the mouse events before\r\n\tother restrictions like statusline, tabline, empty regions, etc.,\r\n\tand receive mouse events while in any mode.  The bad is that you\r\n\thave to watch out for things like recursion errors (i.e.  calling\r\n\tgetchar() from a script function while |mousefunc| is set).\r\n\r\n\tThis function is called often when the mouse is moving, so attention\r\n\tshould be given to returning early out of as many cycles as\r\n\tpossible.\r\n\r\n\tAt the moment, drag and release events are approximated based on the\r\n\tlast primary event (i.e. <leftmouse> or <rightmouse> ).\r\n\r\n","4":"When compiled with this patch set, gvim will have a new option, \"mousefunc\" which will call a user script function for every mouse event.\r\n\r\nThe zip file contains a test script which demonstrates how to do things like:\r\n\r\n\r\n\" This script tests various aspects of the \"mousefunc\" option:\r\n\"\r\n\" - demonstrate having the mouse move tabs in the tabline.\r\n\"\r\n\" - text hotspots:\tHere is mouseover |tag1| and here is |tag2|\r\n\"\r\n\" - verbose option which shows all mouse info.\r\n\"\r\n\" - mouse-follow highlighting (set s:show_bullseye)\r\n\"\r\n\" - associate actions with clicking on statusline words\r\n\r\n\r\n\r\n\r\n\r\nFrom the options.txt doc file:\r\n\r\n\r\n'mousefunc' 'mfn'\tstring\t(default empty)\r\n\t\t\tglobal\r\n\t\t\t{not in Vi}\r\n\tWhen nonempty, this option calls the given function when mouse events\r\n\t(click, drag, move, etc.) are detected.  The function should accept\r\n\tthese arguments:\r\n>\r\n\t\tMouseFunc(\tmouse_key, \r\n\t\t\t\t\\ buf_row, buf_col, buf_vcol, \r\n\t\t\t\t\\ mouse_row, mouse_col, \r\n\t\t\t\t\\ x, y,\r\n\t\t\t\t\\ area, screen_line )\r\n<\r\n\t\"mouse_key\" is a string containing up to 6 chars.  It will match\r\n\tagainst a string like:   a:mouse_key == \"\\<LeftMouse>\".\r\n\t\"mouse_key\" can be empty, particularly when cursor-move-only events\r\n\tare delivered.  \r\n\r\n\t\"buf_row\/col\/vcol\" should match line(\".\") and col(\".\") if you were\r\n\tto click in a buffer at that point.\r\n\r\n\t\"mouse_row\/col\" are independent of windows and buffers.\r\n\t\r\n\tThe \"x\" and \"y\" are in pixels, and can be negative, when that\r\n\tinformation isn't available (see also |mousefocus| to have \"x\" and\r\n\t\"y\" track the mouse cursor).  \r\n\r\n\t\"area\" is Vim's idea of where the mouse is.  Values can be:\r\n\t\"IN_BUFFER\", \"IN_UNKNOWN\", \"IN_SEP_LINE\", \"IN_STATUS_LINE\".\r\n\r\n\t\"screen_line\" contains the literal characters in \"mouse_row\" which\r\n\thave been written to the screen, rather than any buffer.  Useful to\r\n\tread what's on the statusline, tabline, and command line areas.\r\n\t\r\n\tThe function should return 0 to consume the mouse click, or 1 to\r\n\tpass it on transparently.\r\n\r\n\tThe |mousefunc| option is set empty for the duration of the call to\r\n\tprevent recursion.  Setting it again during the call could have\r\n\tunexpected problems.\r\n\r\n\tIt intercepts the mouse events at a low level, which has its good\r\n\tand bad points.  The good is that you get the mouse events before\r\n\tother restrictions like statusline, tabline, empty regions, etc.,\r\n\tand receive mouse events while in any mode.  The bad is that you\r\n\thave to watch out for things like recursion errors (i.e.  calling\r\n\tgetchar() from a script function while |mousefunc| is set).\r\n\r\n\tThis function is called often when the mouse is moving, so attention\r\n\tshould be given to returning early out of as many cycles as\r\n\tpossible.\r\n\r\n\tAt the moment, drag and release events are approximated based on the\r\n\tlast primary event (i.e. <leftmouse> or <rightmouse> ).\r\n\r\n","install_details":"The zip contains the patch files to be applied to the corresponding Vim7 source files.","5":"The zip contains the patch files to be applied to the corresponding Vim7 source files.","first_name":"Eric","6":"Eric","last_name":"Arnold","7":"Arnold","releases":[{"0":"1540","vim_version":"7.0","1":"7.0","script_version":"1.2","2":"1.2","version_comment":"Now tst script fully uses tabline indexes and resize wrapping spots for TabLineSet.vim","3":"Now tst script fully uses tabline indexes and resize wrapping spots for TabLineSet.vim","package":"mousefunc.zip","4":"mousefunc.zip","src_id":"5695","5":"5695","creation_date":"1147627733","6":"1147627733"},{"0":"1540","vim_version":"7.0","1":"7.0","script_version":"1.1","2":"1.1","version_comment":"Smoother tab move code in test script.","3":"Smoother tab move code in test script.","package":"mousefunc.zip","4":"mousefunc.zip","src_id":"5693","5":"5693","creation_date":"1147622079","6":"1147622079"},{"0":"1540","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"mousefunc.zip","4":"mousefunc.zip","src_id":"5684","5":"5684","creation_date":"1147450144","6":"1147450144"}]},"1539":{"script_id":"1539","0":"1539","script_name":"Highlighter.vim","1":"Highlighter.vim","script_type":"utility","2":"utility","summary":"Want to mark up your files with a highlighter?","3":"Want to mark up your files with a highlighter?","description":"This plugin gives you the capability to mark up your files as if you had a highlighter.\r\n\r\nIt's a really useful aid for inspecting log files and marking important sections in source code and documents (even vim help files).\r\n\r\nThe highlights are remembered, even after you close the file. You can also distribute the marks so others can see the highlights you've made.\r\n\r\nThere are a number of different highlighters available for use. (NOTE: you will probably want to create mappings for these commands)\r\n:WordHighlighter\r\nHighlight the word under the cursor\r\n\r\n:SelectionHighlighter\r\nHighlight the current selection. A visual mapping for this command is recommended.\r\n\r\n:SearchPatternHighlighter\r\nHighlight the current search pattern.\r\n\r\n:ClearAllHighlighters\r\nClear all highlights made in this file.\r\n\r\n:ClearCurrentHighligher\r\nClear the Highlighter under the cursor\r\n\r\n:ConfigureHighlighter\r\nOpen the configure window. From here you can configure how the highlighter colors are determined - randomized, use a favorite color, etc.\r\n\r\nLook under Plugin->Highlighter for more options.\r\n\r\nThe highlighter only works with gvim and 'syntax' must be on.  Also, the terminal must support vim colors in the format #rrggbb.\r\n\r\nComments\/suggestions\/complaints are gladly taken.","4":"This plugin gives you the capability to mark up your files as if you had a highlighter.\r\n\r\nIt's a really useful aid for inspecting log files and marking important sections in source code and documents (even vim help files).\r\n\r\nThe highlights are remembered, even after you close the file. You can also distribute the marks so others can see the highlights you've made.\r\n\r\nThere are a number of different highlighters available for use. (NOTE: you will probably want to create mappings for these commands)\r\n:WordHighlighter\r\nHighlight the word under the cursor\r\n\r\n:SelectionHighlighter\r\nHighlight the current selection. A visual mapping for this command is recommended.\r\n\r\n:SearchPatternHighlighter\r\nHighlight the current search pattern.\r\n\r\n:ClearAllHighlighters\r\nClear all highlights made in this file.\r\n\r\n:ClearCurrentHighligher\r\nClear the Highlighter under the cursor\r\n\r\n:ConfigureHighlighter\r\nOpen the configure window. From here you can configure how the highlighter colors are determined - randomized, use a favorite color, etc.\r\n\r\nLook under Plugin->Highlighter for more options.\r\n\r\nThe highlighter only works with gvim and 'syntax' must be on.  Also, the terminal must support vim colors in the format #rrggbb.\r\n\r\nComments\/suggestions\/complaints are gladly taken.","install_details":"Drop into ~\/.vim\/plugin, then read the opening comments in ~\/.vim\/plugin\/highlighter.vim.","5":"Drop into ~\/.vim\/plugin, then read the opening comments in ~\/.vim\/plugin\/highlighter.vim.","first_name":"David","6":"David","last_name":"Larson","7":"Larson","releases":[{"0":"1539","vim_version":"6.0","1":"6.0","script_version":"1.5","2":"1.5","version_comment":"This version no longer adds \"a\" to guioptions, it can have bad effects on windows machines. Thanks to Cristian Ioneci and Stefano Piccardi for pointing it out. Changed how the selected text is determined.","3":"This version no longer adds \"a\" to guioptions, it can have bad effects on windows machines. Thanks to Cristian Ioneci and Stefano Piccardi for pointing it out. Changed how the selected text is determined.","package":"highlighter.vim","4":"highlighter.vim","src_id":"7496","5":"7496","creation_date":"1187015378","6":"1187015378"},{"0":"1539","vim_version":"7.0","1":"7.0","script_version":"1.4","2":"1.4","version_comment":"Highlighter settings were not restored properly on windows systems. Thanks to James Marshall for discovering the problem.","3":"Highlighter settings were not restored properly on windows systems. Thanks to James Marshall for discovering the problem.","package":"highlighter.vim","4":"highlighter.vim","src_id":"7487","5":"7487","creation_date":"1186746535","6":"1186746535"},{"0":"1539","vim_version":"7.0","1":"7.0","script_version":"1.3","2":"1.3","version_comment":"The Selection Highlighter pen didn't work in some environments.\r\nThanks to James Marshall for finding this problem. Fixed it by adding 'a' to 'guioptions'.","3":"The Selection Highlighter pen didn't work in some environments.\r\nThanks to James Marshall for finding this problem. Fixed it by adding 'a' to 'guioptions'.","package":"highlighter.vim","4":"highlighter.vim","src_id":"7480","5":"7480","creation_date":"1186670591","6":"1186670591"}]},"1538":{"script_id":"1538","0":"1538","script_name":"colors\/martin_krischik.vim","1":"colors\/martin_krischik.vim","script_type":"color scheme","2":"color scheme","summary":"My own color scheme for all OS I uses.","3":"My own color scheme for all OS I uses.","description":"This is a maintained mirror of http:\/\/www.vim.org\/scripts\/script.php?script_id=1538\r\n\r\nI don't expect anybody but me to like the colours. But I do think you will like the clean layout of the script file and the symbolic colour names used when you plan to create your own colour scheme.\r\n\r\nTested with Linux (gui, terminal, console), MS-Windows (gui, terminal) and OpenVMS (gui, terminal).\r\n\r\nOptimised for GUI use and readable with terminal and console.\r\n\r\n| Vim-Script  || https:\/\/www.vim.org\/scripts\/script.php?script_id=1538\r\n| Source      || https:\/\/github.com\/krischik\/vim-colors\r\n| Wiki        || https:\/\/github.com\/krischik\/vim-colors\/wiki\r\n| Releases    || https:\/\/github.com\/krischik\/vim-colors\/releases \r\n| Issues      || https:\/\/github.com\/krischik\/vim-colors\/issues \r\n| Discussions || https:\/\/github.com\/krischik\/vim-colors\/discussions \r\n","4":"This is a maintained mirror of http:\/\/www.vim.org\/scripts\/script.php?script_id=1538\r\n\r\nI don't expect anybody but me to like the colours. But I do think you will like the clean layout of the script file and the symbolic colour names used when you plan to create your own colour scheme.\r\n\r\nTested with Linux (gui, terminal, console), MS-Windows (gui, terminal) and OpenVMS (gui, terminal).\r\n\r\nOptimised for GUI use and readable with terminal and console.\r\n\r\n| Vim-Script  || https:\/\/www.vim.org\/scripts\/script.php?script_id=1538\r\n| Source      || https:\/\/github.com\/krischik\/vim-colors\r\n| Wiki        || https:\/\/github.com\/krischik\/vim-colors\/wiki\r\n| Releases    || https:\/\/github.com\/krischik\/vim-colors\/releases \r\n| Issues      || https:\/\/github.com\/krischik\/vim-colors\/issues \r\n| Discussions || https:\/\/github.com\/krischik\/vim-colors\/discussions \r\n","install_details":"Install from https:\/\/github.com\/krischik\/vim-colors using dein (https:\/\/github.com\/Shougo\/dein.vim) or similar:\r\n\r\ncall dein#begin('$HOME\/vimfiles\/bundles')\r\ncall dein#add('krischik\/vim-colors')\r\ncall dein#end()\r\ncall dein#install()","5":"Install from https:\/\/github.com\/krischik\/vim-colors using dein (https:\/\/github.com\/Shougo\/dein.vim) or similar:\r\n\r\ncall dein#begin('$HOME\/vimfiles\/bundles')\r\ncall dein#add('krischik\/vim-colors')\r\ncall dein#end()\r\ncall dein#install()","first_name":"Martin","6":"Martin","last_name":"Krischik","7":"Krischik","releases":[{"0":"1538","vim_version":"7.0","1":"7.0","script_version":"4.0","2":"4.0","version_comment":"See https:\/\/github.com\/krischik\/vim-colors-martin_krischik\/releases\/tag\/v_4.0","3":"See https:\/\/github.com\/krischik\/vim-colors-martin_krischik\/releases\/tag\/v_4.0","package":"vim-colors-martin_krischik-v_4.0.zip","4":"vim-colors-martin_krischik-v_4.0.zip","src_id":"28186","5":"28186","creation_date":"1663815048","6":"1663815048"},{"0":"1538","vim_version":"7.0","1":"7.0","script_version":"3.2","2":"3.2","version_comment":"More terminals supported and bug fixes.","3":"More terminals supported and bug fixes.","package":"martin_krischik.vim","4":"martin_krischik.vim","src_id":"6433","5":"6433","creation_date":"1163814648","6":"1163814648"},{"0":"1538","vim_version":"7.0","1":"7.0","script_version":"3.0","2":"3.0","version_comment":"Finish transitions to Vim 7 - there is probably not a single color unchanged. This version in particular changes that blindingly-bright pink for insert and omni completion to be more in line with the rest of the colorscheme.\r\n\r\nFalls back to \"default\" for older vims (if you accidently start one) so no error messages for non existing features are shown. Perfect starting point for you own vim 7 colorscheme.","3":"Finish transitions to Vim 7 - there is probably not a single color unchanged. This version in particular changes that blindingly-bright pink for insert and omni completion to be more in line with the rest of the colorscheme.\r\n\r\nFalls back to \"default\" for older vims (if you accidently start one) so no error messages for non existing features are shown. Perfect starting point for you own vim 7 colorscheme.","package":"martin_krischik.vim","4":"martin_krischik.vim","src_id":"5984","5":"5984","creation_date":"1153785521","6":"1153785521"},{"0":"1538","vim_version":"7.0","1":"7.0","script_version":"2.0","2":"2.0","version_comment":"New coordinated release for all Ada plugins. Binary releases which are patched with all Ada plugins is available from the GNU Ada project [1]\r\n\r\n[1] http:\/\/gnuada.sourceforge.net","3":"New coordinated release for all Ada plugins. Binary releases which are patched with all Ada plugins is available from the GNU Ada project [1]\r\n\r\n[1] http:\/\/gnuada.sourceforge.net","package":"martin_krischik.vim","4":"martin_krischik.vim","src_id":"5762","5":"5762","creation_date":"1148548419","6":"1148548419"},{"0":"1538","vim_version":"7.0","1":"7.0","script_version":"1.1","2":"1.1","version_comment":"This version now sets all standart vim 7.0 colors. Also the entries have been sorted into groups. So this realy great for creating your own color files.","3":"This version now sets all standart vim 7.0 colors. Also the entries have been sorted into groups. So this realy great for creating your own color files.","package":"martin_krischik.vim","4":"martin_krischik.vim","src_id":"5710","5":"5710","creation_date":"1147852005","6":"1147852005"},{"0":"1538","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"martin_krischik.vim","4":"martin_krischik.vim","src_id":"5672","5":"5672","creation_date":"1147243950","6":"1147243950"}]},"1537":{"script_id":"1537","0":"1537","script_name":"plugin\/backup.vim","1":"plugin\/backup.vim","script_type":"utility","2":"utility","summary":"Numbered Backups.","3":"Numbered Backups.","description":"This is a mirror of http:\/\/www.vim.org\/scripts\/script.php?script_id=1537\r\n\r\nHolds numbered backups inside a separate directory.\r\n\r\nAutomatically purges old backups. Standard is to hold the last 10 versions.\r\n\r\nTested with Linux, MS-Windows and OpenVMS.\r\n\r\nIMPORTANT: Creating this plugin was only possible because vim 7 offers new file management functions - namely :mkdir, finddir() delete() and the new List datatype. This plugin won'g work with vim 6.x.\r\n\r\n| Vim-Script  || https:\/\/www.vim.org\/scripts\/script.php?script_id=1537\r\n| Source      || https:\/\/github.com\/krischik\/vim-backup\r\n| Wiki        || https:\/\/github.com\/krischik\/vim-backup\/wiki\r\n| Releases    || https:\/\/github.com\/krischik\/vim-backup\/releases \r\n| Issues      || https:\/\/github.com\/krischik\/vim-backup\/issues \r\n| Discussions || https:\/\/github.com\/krischik\/vim-backup\/discussions ","4":"This is a mirror of http:\/\/www.vim.org\/scripts\/script.php?script_id=1537\r\n\r\nHolds numbered backups inside a separate directory.\r\n\r\nAutomatically purges old backups. Standard is to hold the last 10 versions.\r\n\r\nTested with Linux, MS-Windows and OpenVMS.\r\n\r\nIMPORTANT: Creating this plugin was only possible because vim 7 offers new file management functions - namely :mkdir, finddir() delete() and the new List datatype. This plugin won'g work with vim 6.x.\r\n\r\n| Vim-Script  || https:\/\/www.vim.org\/scripts\/script.php?script_id=1537\r\n| Source      || https:\/\/github.com\/krischik\/vim-backup\r\n| Wiki        || https:\/\/github.com\/krischik\/vim-backup\/wiki\r\n| Releases    || https:\/\/github.com\/krischik\/vim-backup\/releases \r\n| Issues      || https:\/\/github.com\/krischik\/vim-backup\/issues \r\n| Discussions || https:\/\/github.com\/krischik\/vim-backup\/discussions ","install_details":"Install from https:\/\/github.com\/krischik\/vim-backup using dein (https:\/\/github.com\/Shougo\/dein.vim) or similar:\r\n\r\n{{code|lang=vim|\r\ncall dein#begin('$HOME\/vimfiles\/bundles')\r\ncall dein#add('krischik\/vim-backup')\r\ncall dein#end()\r\ncall dein#install()\r\n}}\r\n\r\nset the following global variables:\r\n\r\ng:backup_directory name of backup directory local to edited file\r\nused for non VMS only. Since non VMS operating-\r\nsystems don't know about version we would get\r\nugly directory listings. So all backups are\r\nmoved into a hidden directory.\r\n\r\ng:backup_purge count of backups to hold - purge older once.\r\nOn VMS PURGE is used to delete older version\r\n0 switched the feature off","5":"Install from https:\/\/github.com\/krischik\/vim-backup using dein (https:\/\/github.com\/Shougo\/dein.vim) or similar:\r\n\r\n{{code|lang=vim|\r\ncall dein#begin('$HOME\/vimfiles\/bundles')\r\ncall dein#add('krischik\/vim-backup')\r\ncall dein#end()\r\ncall dein#install()\r\n}}\r\n\r\nset the following global variables:\r\n\r\ng:backup_directory name of backup directory local to edited file\r\nused for non VMS only. Since non VMS operating-\r\nsystems don't know about version we would get\r\nugly directory listings. So all backups are\r\nmoved into a hidden directory.\r\n\r\ng:backup_purge count of backups to hold - purge older once.\r\nOn VMS PURGE is used to delete older version\r\n0 switched the feature off","first_name":"Martin","6":"Martin","last_name":"Krischik","7":"Krischik","releases":[{"0":"1537","vim_version":"7.0","1":"7.0","script_version":"3.0","2":"3.0","version_comment":"See: https:\/\/github.com\/krischik\/vim-plugin-backup\/releases\/tag\/v_3.0","3":"See: https:\/\/github.com\/krischik\/vim-plugin-backup\/releases\/tag\/v_3.0","package":"vim-plugin-backup-v_3.0.zip","4":"vim-plugin-backup-v_3.0.zip","src_id":"28187","5":"28187","creation_date":"1663815922","6":"1663815922"},{"0":"1537","vim_version":"7.0","1":"7.0","script_version":"2.2","2":"2.2","version_comment":"There was a bug for windows in conjunction with spaces in file names. It did not affect Unix like OS. And it's fixed now.","3":"There was a bug for windows in conjunction with spaces in file names. It did not affect Unix like OS. And it's fixed now.","package":"backup.vim","4":"backup.vim","src_id":"7386","5":"7386","creation_date":"1184915125","6":"1184915125"},{"0":"1537","vim_version":"7.0","1":"7.0","script_version":"2.1","2":"2.1","version_comment":"bug fixes.","3":"bug fixes.","package":"backup.vim","4":"backup.vim","src_id":"6434","5":"6434","creation_date":"1163814653","6":"1163814653"},{"0":"1537","vim_version":"7.0","1":"7.0","script_version":"2.0","2":"2.0","version_comment":"New coordinated release for all Ada plugins. Binary releases which are patched with all Ada plugins is available from the GNU Ada project [1]\r\n\r\n[1] http:\/\/gnuada.sourceforge.net","3":"New coordinated release for all Ada plugins. Binary releases which are patched with all Ada plugins is available from the GNU Ada project [1]\r\n\r\n[1] http:\/\/gnuada.sourceforge.net","package":"backup.vim","4":"backup.vim","src_id":"5760","5":"5760","creation_date":"1148548411","6":"1148548411"},{"0":"1537","vim_version":"7.0","1":"7.0","script_version":"1.1","2":"1.1","version_comment":"Fixed two bugs:\r\n\r\nVMS: \"press key to continue\" is gone.\r\nnon VMS: set of backup directory to user defined variable fixed.","3":"Fixed two bugs:\r\n\r\nVMS: \"press key to continue\" is gone.\r\nnon VMS: set of backup directory to user defined variable fixed.","package":"backup.vim","4":"backup.vim","src_id":"5711","5":"5711","creation_date":"1147852161","6":"1147852161"},{"0":"1537","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"backup.vim","4":"backup.vim","src_id":"5670","5":"5670","creation_date":"1147240219","6":"1147240219"}]},"1536":{"script_id":"1536","0":"1536","script_name":"remind","1":"remind","script_type":"syntax","2":"syntax","summary":"remind syntax","3":"remind syntax","description":"remind is a sophisticated reminder service; you can download remind from: https:\/\/www.roaringpenguin.com\/products\/remind","4":"remind is a sophisticated reminder service; you can download remind from: https:\/\/www.roaringpenguin.com\/products\/remind","install_details":"","5":"","first_name":"Davide","6":"Davide","last_name":"Alberani","7":"Alberani","releases":[{"0":"1536","vim_version":"6.0","1":"6.0","script_version":"0.7","2":"0.7","version_comment":"updated email and link","3":"updated email and link","package":"remind.vim","4":"remind.vim","src_id":"23709","5":"23709","creation_date":"1446501053","6":"1446501053"},{"0":"1536","vim_version":"5.7","1":"5.7","script_version":"0.6","2":"0.6","version_comment":"Added the THROUGH keyword (courtesy of Ben Orchard)","3":"Added the THROUGH keyword (courtesy of Ben Orchard)","package":"remind.vim","4":"remind.vim","src_id":"23661","5":"23661","creation_date":"1444425370","6":"1444425370"},{"0":"1536","vim_version":"6.0","1":"6.0","script_version":"0.5","2":"0.5","version_comment":"updated to hightlight new keywords.","3":"updated to hightlight new keywords.","package":"remind.vim","4":"remind.vim","src_id":"12076","5":"12076","creation_date":"1263302573","6":"1263302573"},{"0":"1536","vim_version":"6.0","1":"6.0","script_version":"0.4","2":"0.4","version_comment":"Minor changes to support some new keywords.","3":"Minor changes to support some new keywords.","package":"remind.vim","4":"remind.vim","src_id":"7424","5":"7424","creation_date":"1185595931","6":"1185595931"},{"0":"1536","vim_version":"6.0","1":"6.0","script_version":"0.3","2":"0.3","version_comment":"Initial upload","3":"Initial upload","package":"remind.vim","4":"remind.vim","src_id":"5667","5":"5667","creation_date":"1147221752","6":"1147221752"}]},"1535":{"script_id":"1535","0":"1535","script_name":"TagsParser","1":"TagsParser","script_type":"utility","2":"utility","summary":"Automatic tagfile updating and tag viewer","3":"Automatic tagfile updating and tag viewer","description":"\r\nThe TagsParser plugin does two things.\r\n\r\nFirst it automatically updates the tag files when you write a file out (Dynamic Tags).  This is controlled by a path so that this does not happen for every file that you ever edit.  This way as soon as you save a file, you will be able to access tags via the usual vim methods ^], :tag, :ts, ^T, etc.  There are various options in the plugin that control which files to tag.  \r\n\r\nThis is nice if you have a bunch of source that you are working on, and like to use ctags to navigate through your source, but get annoyed at manually re-tagging your source to pick up any new variables\/functions\/etc.\r\n\r\nSecondly, there is a tag viewer (the Tag Window) which uses the tag files created by the Dynamic Tag functionality of the script to display the tags that belong to the file you have open.  For C\/C++ and Ada files, it will display the tags hierarchically, so for example, struct members get displayed below the struct they belong to.  This part of the script can be turned off if you prefer to only use the Dynamic Tags functionality.  There are many options which control what is displayed and how, and of course, these are all detailed in the included help file.\r\n\r\nConfiguring the \"TagsParserTagsPath\" or \"TagsParserProjectConfig\" options can be difficult sometimes.  The \":TagsParserPrintPath\" command can help you debug the normal tags path variable, but has not been updated to support debugging the project configurations yet.  See the \"tagsparser-config\" help file entry for more details, but this is the short version:\r\n\r\nThe first important thing to keep in mind, is to use either unix-style slashes (\/), or to 'escape' your windows-style slashes when using a double quoted path (\"stuff\\\\foo\").  Alternatively single quotes can be used instead ('stuff\\foo').\r\n\r\nThe second important thing to keep in mind is that the directories used in defining the project configuration root directories must be defined using the correct slash style for your platform.  So for example, MS windows users _must_ use \"\\\" instead of \"\/\".  Following is an project configuration setup:\r\n\r\n  let g:TagsParserProjectConfig = {}\r\n  let g:TagsParserProjectConfig['C:\\Working\\PRJ1\\Software\\Source Code'] = {}\r\n  let g:TagsParserProjectConfig['C:\\Working\\PRJ1\\Software\\Source Code'] = { 'tagsPath' : 'C:\/Working\/PRJ1\/Software\/Source Code\/OBJ1,C:\/Working\/PRJ1\/Software\/Source Code\/OBJ1\/**,C:\/Working\/PRJ1\/Software\/Source Code\/BSP,C:\/Working\/PRJ1\/Software\/Source Code\/BSP\/**' }\r\n  let g:TagsParserProjectConfig['C:\\Working\\PRJ2\\Software\\OBJ1'] = {}\r\n  let g:TagsParserProjectConfig['C:\\Working\\PRJ2\\Software\\OBJ1'] = { 'tagsPath' : 'C:\/Working\/PRJ2\/Software\/OBJ1,C:\/Working\/PRJ2\/Software\/OBJ1\/**' }\r\n\r\nThis plugin supports all filetypes that Exuberant Ctags supports, along with Ada.  For Ada support I have created an Ada Mode parser for Ctags.  You can find the latest version of that parser here: http:\/\/gnuada.svn.sourceforge.net\/viewvc\/gnuada\/tags\/ At the time that I am writing this version 4.1.0 was the latest and is in this directory: http:\/\/gnuada.svn.sourceforge.net\/viewvc\/gnuada\/tags\/ctags-ada-mode-4.1.0 Directions to install the ada.c file are in the file itself, or you can use the add_ada.vim file to do the necessary updates to the ctags source for you.\r\n\r\nThere are many options that govern how the Tag Window appears, I have tried to setup the default options so that it will display nicely with out any customization, but if you so desire there should be many ways to adjust the way the window appears.\r\n\r\nPlease email me with any questions you have or bugs you find.  I am also happy to take suggestions for features or options that would make this plugin more useful for you.\r\n\r\n-------- Notable Additions -------\r\n- Example configuration options in help file.\r\n\r\n- Tabpage support that actually works!  (I hope)...\r\n\r\n- Debugging functionality.\r\n\r\n- TagsParserCurrentFileCWD feature (added in an earlier release, but was missing from documentation.\r\n\r\n--- Previous Notable Additions ---\r\n- The big addition to version 0.9 is project configurations, these are only supported in Vim 7.0.  The full details can be gathered if you check the help page for \"TagsParserProjectConfig\", but a short version is here:\r\nInstead of one path variable (\"TagsParserTagsPath\"), now you can configure separate paths for different 'projects'.  A project is configured using a Vim hash (dictionary), where the root directory of a project is used as the hash key.  Then a TagsPath, TagsLib, and various other variables can be configured uniquely for every project.  This should reduce the time required to find tags in each project.\r\n\r\n- Tabpages are now supported when using the Tag Window functionality.  Also added some mappings to make it easier to navigate between tabs and buffers.  See \"TagsParserCtrlTabUsage\" for detailed information.\r\n\r\n- All commands have default key mappings (such as <leader>t<space> to toggle the Tag Window On and Off - :TagsParserToggle), and these can all be overridden by a user mapping.\r\n\r\n- The TagsParserSaveInterval variable now prevents tagging a file too frequently (default of 30 second wait period).\r\n\r\n- The TagsParserTagsDir variable can now be used to change the name of the directory that is created to store tag files in (default of \".tags\").\r\n\r\n- The TagsParser functions are now autoloaded, hopefully this speeds up vim startup and reduces overhead when the TagsParser is not being used.\r\n\r\n- See \"tagsparser-changelog\" for more detailed information. ","4":"\r\nThe TagsParser plugin does two things.\r\n\r\nFirst it automatically updates the tag files when you write a file out (Dynamic Tags).  This is controlled by a path so that this does not happen for every file that you ever edit.  This way as soon as you save a file, you will be able to access tags via the usual vim methods ^], :tag, :ts, ^T, etc.  There are various options in the plugin that control which files to tag.  \r\n\r\nThis is nice if you have a bunch of source that you are working on, and like to use ctags to navigate through your source, but get annoyed at manually re-tagging your source to pick up any new variables\/functions\/etc.\r\n\r\nSecondly, there is a tag viewer (the Tag Window) which uses the tag files created by the Dynamic Tag functionality of the script to display the tags that belong to the file you have open.  For C\/C++ and Ada files, it will display the tags hierarchically, so for example, struct members get displayed below the struct they belong to.  This part of the script can be turned off if you prefer to only use the Dynamic Tags functionality.  There are many options which control what is displayed and how, and of course, these are all detailed in the included help file.\r\n\r\nConfiguring the \"TagsParserTagsPath\" or \"TagsParserProjectConfig\" options can be difficult sometimes.  The \":TagsParserPrintPath\" command can help you debug the normal tags path variable, but has not been updated to support debugging the project configurations yet.  See the \"tagsparser-config\" help file entry for more details, but this is the short version:\r\n\r\nThe first important thing to keep in mind, is to use either unix-style slashes (\/), or to 'escape' your windows-style slashes when using a double quoted path (\"stuff\\\\foo\").  Alternatively single quotes can be used instead ('stuff\\foo').\r\n\r\nThe second important thing to keep in mind is that the directories used in defining the project configuration root directories must be defined using the correct slash style for your platform.  So for example, MS windows users _must_ use \"\\\" instead of \"\/\".  Following is an project configuration setup:\r\n\r\n  let g:TagsParserProjectConfig = {}\r\n  let g:TagsParserProjectConfig['C:\\Working\\PRJ1\\Software\\Source Code'] = {}\r\n  let g:TagsParserProjectConfig['C:\\Working\\PRJ1\\Software\\Source Code'] = { 'tagsPath' : 'C:\/Working\/PRJ1\/Software\/Source Code\/OBJ1,C:\/Working\/PRJ1\/Software\/Source Code\/OBJ1\/**,C:\/Working\/PRJ1\/Software\/Source Code\/BSP,C:\/Working\/PRJ1\/Software\/Source Code\/BSP\/**' }\r\n  let g:TagsParserProjectConfig['C:\\Working\\PRJ2\\Software\\OBJ1'] = {}\r\n  let g:TagsParserProjectConfig['C:\\Working\\PRJ2\\Software\\OBJ1'] = { 'tagsPath' : 'C:\/Working\/PRJ2\/Software\/OBJ1,C:\/Working\/PRJ2\/Software\/OBJ1\/**' }\r\n\r\nThis plugin supports all filetypes that Exuberant Ctags supports, along with Ada.  For Ada support I have created an Ada Mode parser for Ctags.  You can find the latest version of that parser here: http:\/\/gnuada.svn.sourceforge.net\/viewvc\/gnuada\/tags\/ At the time that I am writing this version 4.1.0 was the latest and is in this directory: http:\/\/gnuada.svn.sourceforge.net\/viewvc\/gnuada\/tags\/ctags-ada-mode-4.1.0 Directions to install the ada.c file are in the file itself, or you can use the add_ada.vim file to do the necessary updates to the ctags source for you.\r\n\r\nThere are many options that govern how the Tag Window appears, I have tried to setup the default options so that it will display nicely with out any customization, but if you so desire there should be many ways to adjust the way the window appears.\r\n\r\nPlease email me with any questions you have or bugs you find.  I am also happy to take suggestions for features or options that would make this plugin more useful for you.\r\n\r\n-------- Notable Additions -------\r\n- Example configuration options in help file.\r\n\r\n- Tabpage support that actually works!  (I hope)...\r\n\r\n- Debugging functionality.\r\n\r\n- TagsParserCurrentFileCWD feature (added in an earlier release, but was missing from documentation.\r\n\r\n--- Previous Notable Additions ---\r\n- The big addition to version 0.9 is project configurations, these are only supported in Vim 7.0.  The full details can be gathered if you check the help page for \"TagsParserProjectConfig\", but a short version is here:\r\nInstead of one path variable (\"TagsParserTagsPath\"), now you can configure separate paths for different 'projects'.  A project is configured using a Vim hash (dictionary), where the root directory of a project is used as the hash key.  Then a TagsPath, TagsLib, and various other variables can be configured uniquely for every project.  This should reduce the time required to find tags in each project.\r\n\r\n- Tabpages are now supported when using the Tag Window functionality.  Also added some mappings to make it easier to navigate between tabs and buffers.  See \"TagsParserCtrlTabUsage\" for detailed information.\r\n\r\n- All commands have default key mappings (such as <leader>t<space> to toggle the Tag Window On and Off - :TagsParserToggle), and these can all be overridden by a user mapping.\r\n\r\n- The TagsParserSaveInterval variable now prevents tagging a file too frequently (default of 30 second wait period).\r\n\r\n- The TagsParserTagsDir variable can now be used to change the name of the directory that is created to store tag files in (default of \".tags\").\r\n\r\n- The TagsParser functions are now autoloaded, hopefully this speeds up vim startup and reduces overhead when the TagsParser is not being used.\r\n\r\n- See \"tagsparser-changelog\" for more detailed information. ","install_details":"This script requires a few supporting things to be installed.  Exuberant Ctags (http:\/\/ctags.sourceforge.net\/) and if you are not using Vim 7.0, or just like it better, Perl (http:\/\/www.perl.com\/).\r\n\r\nFor most linux\/unix people these won't be a problem.  If you are running windows and need Perl, you will need to install perl (http:\/\/www.activestate.com\/Products\/ActivePerl\/ is a decent version), and ctags.  And for those running MacOS X you will likely only need to install ctags, because the ctags that comes with MacOS X by default is not Exubernat Ctags.\r\n\r\nUntar the tarball in a directory in your vim runtimepath.  Usually ~\/.vim, $VIM\/vimfiles, something along those lines.  There are 3 files: autoload\/TagsPaser.vim, plugin\/TagsPaser.vim and doc\/TagsParser.txt.  After these files have been extracted, run the following command in Vim \":helptags <path>\/doc\" to index the new TagsParser help file.\r\n\r\nTagsParser is no longer packaged in a vimball because the TagsParser plugin does not require Vim 7.0, but the vimball plugin does.  I like the concept of a vimball because it makes installation easier, but I need to make sure that the plugin distribution method supports the same number of users that the plugin supports.","5":"This script requires a few supporting things to be installed.  Exuberant Ctags (http:\/\/ctags.sourceforge.net\/) and if you are not using Vim 7.0, or just like it better, Perl (http:\/\/www.perl.com\/).\r\n\r\nFor most linux\/unix people these won't be a problem.  If you are running windows and need Perl, you will need to install perl (http:\/\/www.activestate.com\/Products\/ActivePerl\/ is a decent version), and ctags.  And for those running MacOS X you will likely only need to install ctags, because the ctags that comes with MacOS X by default is not Exubernat Ctags.\r\n\r\nUntar the tarball in a directory in your vim runtimepath.  Usually ~\/.vim, $VIM\/vimfiles, something along those lines.  There are 3 files: autoload\/TagsPaser.vim, plugin\/TagsPaser.vim and doc\/TagsParser.txt.  After these files have been extracted, run the following command in Vim \":helptags <path>\/doc\" to index the new TagsParser help file.\r\n\r\nTagsParser is no longer packaged in a vimball because the TagsParser plugin does not require Vim 7.0, but the vimball plugin does.  I like the concept of a vimball because it makes installation easier, but I need to make sure that the plugin distribution method supports the same number of users that the plugin supports.","first_name":"Aaron","6":"Aaron","last_name":"Cornelius","7":"Cornelius","releases":[{"0":"1535","vim_version":"6.0","1":"6.0","script_version":"0.9.1","2":"0.9.1","version_comment":"Addition of configuration examples.\r\nBig fixes for tabpage\/multiple file editing (sorry it was so busted in 0.9).\r\nAddition of debugging functionality.","3":"Addition of configuration examples.\r\nBig fixes for tabpage\/multiple file editing (sorry it was so busted in 0.9).\r\nAddition of debugging functionality.","package":"TagsParser-0.9.1.tar.gz","4":"TagsParser-0.9.1.tar.gz","src_id":"6835","5":"6835","creation_date":"1173028993","6":"1173028993"},{"0":"1535","vim_version":"6.0","1":"6.0","script_version":"0.9","2":"0.9","version_comment":"Addition of some new features, most notably project configurations and tabpage support (these require Vim 7.0 to use though).  Many bugfixes also implemented.\r\n","3":"Addition of some new features, most notably project configurations and tabpage support (these require Vim 7.0 to use though).  Many bugfixes also implemented.\r\n","package":"TagsParser-0.9.tar.gz","4":"TagsParser-0.9.tar.gz","src_id":"6739","5":"6739","creation_date":"1171354460","6":"1171354460"},{"0":"1535","vim_version":"6.0","1":"6.0","script_version":"0.7","2":"0.7","version_comment":"Many updates and bugfixes... Addition of fully Vim native functions, Perl is no longer required for users of Vim 7.0 and greater.","3":"Many updates and bugfixes... Addition of fully Vim native functions, Perl is no longer required for users of Vim 7.0 and greater.","package":"TagsParser-0.7.tar.gz","4":"TagsParser-0.7.tar.gz","src_id":"6394","5":"6394","creation_date":"1163020436","6":"1163020436"},{"0":"1535","vim_version":"7.0","1":"7.0","script_version":"0.5","2":"0.5","version_comment":"Vimball of version 0.5","3":"Vimball of version 0.5","package":"TagsParser-0.5.vba.gz","4":"TagsParser-0.5.vba.gz","src_id":"6228","5":"6228","creation_date":"1159207723","6":"1159207723"},{"0":"1535","vim_version":"6.0","1":"6.0","script_version":"0.5","2":"0.5","version_comment":"Another bugfix release.  The complete changes are in the change log.  It has been a while since I uploaded some fixes so I thought it was time.","3":"Another bugfix release.  The complete changes are in the change log.  It has been a while since I uploaded some fixes so I thought it was time.","package":"TagsParser-0.5.tar.gz","4":"TagsParser-0.5.tar.gz","src_id":"6227","5":"6227","creation_date":"1159206551","6":"1159206551"},{"0":"1535","vim_version":"7.0","1":"7.0","script_version":"0.4","2":"0.4","version_comment":"Some bugfixes and modifications.\r\nThis is the vimball of version 0.4 (instead of a tarball).  You must have the vimball script installed (http:\/\/www.vim.org\/scripts\/script.php?script_id=1502), which it is by default on vim 7.","3":"Some bugfixes and modifications.\r\nThis is the vimball of version 0.4 (instead of a tarball).  You must have the vimball script installed (http:\/\/www.vim.org\/scripts\/script.php?script_id=1502), which it is by default on vim 7.","package":"TagsParser-0.4.vba","4":"TagsParser-0.4.vba","src_id":"5824","5":"5824","creation_date":"1150054135","6":"1150054135"},{"0":"1535","vim_version":"6.0","1":"6.0","script_version":"0.4","2":"0.4","version_comment":"Some bugfixes and modifications.","3":"Some bugfixes and modifications.","package":"TagsParser-0.4.tar.gz","4":"TagsParser-0.4.tar.gz","src_id":"5823","5":"5823","creation_date":"1150053987","6":"1150053987"},{"0":"1535","vim_version":"6.0","1":"6.0","script_version":"0.3","2":"0.3","version_comment":"Initial upload","3":"Initial upload","package":"TagsParser-0.3.tar.gz","4":"TagsParser-0.3.tar.gz","src_id":"5652","5":"5652","creation_date":"1147009555","6":"1147009555"}]},"1534":{"script_id":"1534","0":"1534","script_name":"vimproject","1":"vimproject","script_type":"utility","2":"utility","summary":"A Python script to create nested menus in gvim to open files in a project","3":"A Python script to create nested menus in gvim to open files in a project","description":"A crude but useful way to quickly open files in a project, particularly those several directories deep -- saves a lot of typing. See http:\/\/whisperingwind.co.uk\/index.php\/free\/vimproject\/ for screen shots and example XML project file.\r\n\r\nThis could probably be done in vim's native scripting language, but I don't know it and can't be bothered to learn it. Perhaps one day...","4":"A crude but useful way to quickly open files in a project, particularly those several directories deep -- saves a lot of typing. See http:\/\/whisperingwind.co.uk\/index.php\/free\/vimproject\/ for screen shots and example XML project file.\r\n\r\nThis could probably be done in vim's native scripting language, but I don't know it and can't be bothered to learn it. Perhaps one day...","install_details":"Requires vim compiled for Python and GUI (for example, install vim-pythom on Ubuntu Linux). Works Unix\/Linux versions of vim, I haven't tried it on Windows.\r\n\r\nFull install instructions at http:\/\/whisperingwind.co.uk\/index.php\/free\/vimproject\/installation\/","5":"Requires vim compiled for Python and GUI (for example, install vim-pythom on Ubuntu Linux). Works Unix\/Linux versions of vim, I haven't tried it on Windows.\r\n\r\nFull install instructions at http:\/\/whisperingwind.co.uk\/index.php\/free\/vimproject\/installation\/","first_name":"Mike","6":"Mike","last_name":"Wilson","7":"Wilson","releases":[{"0":"1534","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"vimproject.py","4":"vimproject.py","src_id":"5646","5":"5646","creation_date":"1146969851","6":"1146969851"}]},"1533":{"script_id":"1533","0":"1533","script_name":"amarok.vim","1":"amarok.vim","script_type":"utility","2":"utility","summary":"amaroK integration for vim","3":"amaroK integration for vim","description":"amarok.vim - amaroK integration for vim                                         \r\n                                                                                \r\nThis plugin let's you control amaroK (http:\/\/amarok.kde.org) from vim. It adds  \r\na menu to your gvim, and defines a new command called 'AmaroK', which let's     \r\nyou control amarok via Ex-commands. Since it uses the dcop-functionality of     \r\namaroK, you can type in any dcop command the dcop-player-interface of amarok    \r\nsupports. For a complete list type: dcop amarok player functions in a terminal  \r\n                                                                                \r\n                                                                                \r\nIf you don't like the menu, you can set the g:AmaroK_show_menu-variable to 0    \r\nin your vimrc and the menu will not be displayed                                \r\n","4":"amarok.vim - amaroK integration for vim                                         \r\n                                                                                \r\nThis plugin let's you control amaroK (http:\/\/amarok.kde.org) from vim. It adds  \r\na menu to your gvim, and defines a new command called 'AmaroK', which let's     \r\nyou control amarok via Ex-commands. Since it uses the dcop-functionality of     \r\namaroK, you can type in any dcop command the dcop-player-interface of amarok    \r\nsupports. For a complete list type: dcop amarok player functions in a terminal  \r\n                                                                                \r\n                                                                                \r\nIf you don't like the menu, you can set the g:AmaroK_show_menu-variable to 0    \r\nin your vimrc and the menu will not be displayed                                \r\n","install_details":"Put it in your .vim\/plugin directory and the menu will be available in gvim","5":"Put it in your .vim\/plugin directory and the menu will be available in gvim","first_name":"Andr\u00c3\u00a9","6":"Andr\u00c3\u00a9","last_name":"Kelpe","7":"Kelpe","releases":[{"0":"1533","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"amarok.vim","4":"amarok.vim","src_id":"5644","5":"5644","creation_date":"1146838117","6":"1146838117"}]},"1532":{"script_id":"1532","0":"1532","script_name":"txt.vim","1":"txt.vim","script_type":"syntax","2":"syntax","summary":"Universal syntax script for all txt docs, logs and other types","3":"Universal syntax script for all txt docs, logs and other types","description":"This is an universal syntax script for all text documents, logs, changelogs, readmes and all other strange and undetected filetypes. The goal is to keep it very simple.It colors numbers, operators, signs, cites, brackets, delimiters, comments, TODOs, errors, debug, changelog tags and basic smileys ;]\r\n\r\nVisit project site for details and comparision screenshots:\r\nhttp:\/\/spoonman.eu\/wiki\/index.php?page=txt+syntax+file\r\n\r\nI'd also suggest to add a file into your $HOME\/ftdetect called txt.vim that contains a line:\r\n au BufRead,BufNewFile *  setfiletype txt\r\nThis way if Vim cannot detect a filetype of a file you've just opened - it sets this universal syntax.\r\n\r\nYour suggestions are very welcome.","4":"This is an universal syntax script for all text documents, logs, changelogs, readmes and all other strange and undetected filetypes. The goal is to keep it very simple.It colors numbers, operators, signs, cites, brackets, delimiters, comments, TODOs, errors, debug, changelog tags and basic smileys ;]\r\n\r\nVisit project site for details and comparision screenshots:\r\nhttp:\/\/spoonman.eu\/wiki\/index.php?page=txt+syntax+file\r\n\r\nI'd also suggest to add a file into your $HOME\/ftdetect called txt.vim that contains a line:\r\n au BufRead,BufNewFile *  setfiletype txt\r\nThis way if Vim cannot detect a filetype of a file you've just opened - it sets this universal syntax.\r\n\r\nYour suggestions are very welcome.","install_details":"Download package and unzip to your $HOME\/syntax directory.","5":"Download package and unzip to your $HOME\/syntax directory.","first_name":"Tomasz","6":"Tomasz","last_name":"Kalkosinski","7":"Kalkosinski","releases":[{"0":"1532","vim_version":"6.0","1":"6.0","script_version":"1.2","2":"1.2","version_comment":"1.2 Release (03.01.2007)\r\n- add: Changelog tags: add, chg, fix, rem, del linked with Keyword\r\n- add: note to txtTodo group","3":"1.2 Release (03.01.2007)\r\n- add: Changelog tags: add, chg, fix, rem, del linked with Keyword\r\n- add: note to txtTodo group","package":"txt-vim-syntax-1.2.zip","4":"txt-vim-syntax-1.2.zip","src_id":"6580","5":"6580","creation_date":"1167836523","6":"1167836523"},{"0":"1532","vim_version":"6.0","1":"6.0","script_version":"1.1","2":"1.1","version_comment":"Add: International cites\r\nChg: txtString color to Normal\r\nChg: Simplified number coloring working better now","3":"Add: International cites\r\nChg: txtString color to Normal\r\nChg: Simplified number coloring working better now","package":"txt.vim","4":"txt.vim","src_id":"5904","5":"5904","creation_date":"1151681637","6":"1151681637"},{"0":"1532","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"txt.vim","4":"txt.vim","src_id":"5625","5":"5625","creation_date":"1146226817","6":"1146226817"}]},"1531":{"script_id":"1531","0":"1531","script_name":"[backburner]Edit_Visual_Block.vim","1":"[backburner]Edit_Visual_Block.vim","script_type":"utility","2":"utility","summary":"Edit text from Visual Block as if a virtual window.","3":"Edit text from Visual Block as if a virtual window.","description":" ---------------------------------------------------------------------------\r\n\r\n Edit_Visual_Block.vim :   Edit the text in a Visual Block as \r\n                           if it were in a virtual window.\r\n\r\n   Description:\r\n   \r\n       Creates a virtual 'edit window' inside the visual selection area.\r\n       Once the boundary box is drawn, you can insert\/replace\/cut\/paste as\r\n       normal, and it will try to maintain the boundary box in some\r\n       reasonable fashion.\r\n\r\n   Usage:\r\n\r\n       i   Select a Visual Block (with ^V or ^Q), and type 'i' (default\r\n           mapping).  It will draw a box around the visual area, and return\r\n           you to Vim Normal mode.  Begin editing.  See Notes for things\r\n           not to do.\r\n\r\n       <ESC>\r\n           Hitting escape while in Vim Normal mode will terminate the\r\n           Edit Visual Block mode, and return to the visual block\r\n           selection.\r\n\r\n   Notes:\r\n\r\n   -   While this mode is in effect, for the lines that are part of\r\n       the seletion, characters outside of the visual block selection\r\n       cannot be changed,.  It needs these strings as markers for the\r\n       boundaries of the virtual edit window.\r\n\r\n       If changes are made, the boundary strings will be restored, with\r\n       other text moved inwards, if possible.\r\n       \r\n   -   Deleting or adding lines in the selected area is not handled or\r\n       recommended.\r\n\r\n   -   Pasting simple block-wise(\"^V\"), or line-wise (\"V\") text will\r\n       generally do something useful, but pasting multi-line char-wise\r\n       (\"v\"), will generally do something messy.\r\n           \r\n   -   Until I can decypher 'undojoin', you will have use more than one\r\n       'undo' at a time, i.e.  '2u' or '3u' or whatever, to undo the last\r\n       change while the mode is in effect.\r\n\r\n","4":" ---------------------------------------------------------------------------\r\n\r\n Edit_Visual_Block.vim :   Edit the text in a Visual Block as \r\n                           if it were in a virtual window.\r\n\r\n   Description:\r\n   \r\n       Creates a virtual 'edit window' inside the visual selection area.\r\n       Once the boundary box is drawn, you can insert\/replace\/cut\/paste as\r\n       normal, and it will try to maintain the boundary box in some\r\n       reasonable fashion.\r\n\r\n   Usage:\r\n\r\n       i   Select a Visual Block (with ^V or ^Q), and type 'i' (default\r\n           mapping).  It will draw a box around the visual area, and return\r\n           you to Vim Normal mode.  Begin editing.  See Notes for things\r\n           not to do.\r\n\r\n       <ESC>\r\n           Hitting escape while in Vim Normal mode will terminate the\r\n           Edit Visual Block mode, and return to the visual block\r\n           selection.\r\n\r\n   Notes:\r\n\r\n   -   While this mode is in effect, for the lines that are part of\r\n       the seletion, characters outside of the visual block selection\r\n       cannot be changed,.  It needs these strings as markers for the\r\n       boundaries of the virtual edit window.\r\n\r\n       If changes are made, the boundary strings will be restored, with\r\n       other text moved inwards, if possible.\r\n       \r\n   -   Deleting or adding lines in the selected area is not handled or\r\n       recommended.\r\n\r\n   -   Pasting simple block-wise(\"^V\"), or line-wise (\"V\") text will\r\n       generally do something useful, but pasting multi-line char-wise\r\n       (\"v\"), will generally do something messy.\r\n           \r\n   -   Until I can decypher 'undojoin', you will have use more than one\r\n       'undo' at a time, i.e.  '2u' or '3u' or whatever, to undo the last\r\n       change while the mode is in effect.\r\n\r\n","install_details":"   Setup:\r\n\r\n       -   Put into your plugin directory, or source as desired.\r\n\r\n       -   Decide what key to map.\r\n","5":"   Setup:\r\n\r\n       -   Put into your plugin directory, or source as desired.\r\n\r\n       -   Decide what key to map.\r\n","first_name":"Eric","6":"Eric","last_name":"Arnold","7":"Arnold","releases":[{"0":"1531","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"Edit_Visual_Block.vim","4":"Edit_Visual_Block.vim","src_id":"5624","5":"5624","creation_date":"1146225688","6":"1146225688"}]},"1530":{"script_id":"1530","0":"1530","script_name":"timing.vim","1":"timing.vim","script_type":"utility","2":"utility","summary":"stopwatch timing of execution time of vim commands and command sequences","3":"stopwatch timing of execution time of vim commands and command sequences","description":"This script provides the TIM command which measures execution time vim takes to execute given commands up to microsecond resolution (actual resolution depends on OS).\r\n\r\nExample:\r\n\r\n   TIM 2000 let x=0  \" How much time is takes to do 'x=0' 20000 times ?\r\n\r\nIf first argument after TIM is a number, it is treated as repetiion count. \r\nIf first argument is not a number, the command is executed once.\r\n\r\nMultiple commands, separated by bars(|) can be used under TIM command:\r\n\r\n     TIM 100 e xxx | bd  \"How much time it takes \r\n                                  \" to open and close the buffer 100 times\r\n\r\n","4":"This script provides the TIM command which measures execution time vim takes to execute given commands up to microsecond resolution (actual resolution depends on OS).\r\n\r\nExample:\r\n\r\n   TIM 2000 let x=0  \" How much time is takes to do 'x=0' 20000 times ?\r\n\r\nIf first argument after TIM is a number, it is treated as repetiion count. \r\nIf first argument is not a number, the command is executed once.\r\n\r\nMultiple commands, separated by bars(|) can be used under TIM command:\r\n\r\n     TIM 100 e xxx | bd  \"How much time it takes \r\n                                  \" to open and close the buffer 100 times\r\n\r\n","install_details":"Copy file timing.vim into your .vim\/plugin directory. \r\nOr simply source timing.vim: :so timing.vim\r\n","5":"Copy file timing.vim into your .vim\/plugin directory. \r\nOr simply source timing.vim: :so timing.vim\r\n","first_name":"Yakov","6":"Yakov","last_name":"Lerner","7":"Lerner","releases":[{"0":"1530","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"timing.vim","4":"timing.vim","src_id":"5623","5":"5623","creation_date":"1146222893","6":"1146222893"}]},"1529":{"script_id":"1529","0":"1529","script_name":"FlexWiki syntax highlighting","1":"FlexWiki syntax highlighting","script_type":"syntax","2":"syntax","summary":"syntax highlighting for FlexWiki wiki","3":"syntax highlighting for FlexWiki wiki","description":"Syntax highlighting for FlexWiki, http:\/\/www.flexwiki.com\/ Also a filetype detection script which sets appropriate buffer-local options for editing long lines, etc.\r\n\r\nLatest copy can be found at http:\/\/www.georgevreilly.com\/vim\/flexwiki\/\r\n\r\nMore details can be found at http:\/\/www.flexwiki.com\/default.aspx\/FlexWiki\/VimPluginForFlexWiki.html\r\n\r\nThis is included in Vim 7.0\r\n","4":"Syntax highlighting for FlexWiki, http:\/\/www.flexwiki.com\/ Also a filetype detection script which sets appropriate buffer-local options for editing long lines, etc.\r\n\r\nLatest copy can be found at http:\/\/www.georgevreilly.com\/vim\/flexwiki\/\r\n\r\nMore details can be found at http:\/\/www.flexwiki.com\/default.aspx\/FlexWiki\/VimPluginForFlexWiki.html\r\n\r\nThis is included in Vim 7.0\r\n","install_details":"Create a HOME directory, if you haven't already\r\nCreate a \"vimfiles\" (Windows) or \".vim\" (Unix\/Mac) folder in your HOME directory.\r\nUnzip stwiki.zip in that vimfiles (.vim) folder.\r\nRestart Vim\r\n\r\nSee \":help add-global-plugin\" for more details","5":"Create a HOME directory, if you haven't already\r\nCreate a \"vimfiles\" (Windows) or \".vim\" (Unix\/Mac) folder in your HOME directory.\r\nUnzip stwiki.zip in that vimfiles (.vim) folder.\r\nRestart Vim\r\n\r\nSee \":help add-global-plugin\" for more details","first_name":"George V.","6":"George V.","last_name":"Reilly","7":"Reilly","releases":[{"0":"1529","vim_version":"6.0","1":"6.0","script_version":"0.3","2":"0.3","version_comment":"Upload the version that's included with Vim 7.0","3":"Upload the version that's included with Vim 7.0","package":"flexwiki.zip","4":"flexwiki.zip","src_id":"8189","5":"8189","creation_date":"1201556958","6":"1201556958"},{"0":"1529","vim_version":"6.0","1":"6.0","script_version":"0.2","2":"0.2","version_comment":"Initial upload","3":"Initial upload","package":"flexwiki.zip","4":"flexwiki.zip","src_id":"5614","5":"5614","creation_date":"1146005815","6":"1146005815"}]},"1528":{"script_id":"1528","0":"1528","script_name":"comments.vim","1":"comments.vim","script_type":"utility","2":"utility","summary":"To Comment\/Un-Comment single\/multiple lines of code for different source files","3":"To Comment\/Un-Comment single\/multiple lines of code for different source files","description":"Global Plugin to comment and un-comment lines in different source files in both normal and visual <Shift-V> mode\r\nusage:\r\nctrl-c to comment a single line\r\nctrl-x to un-comment a single line\r\nshift-v and select multiple lines, then ctrl-c to comment the selected multiple lines\r\nshift-v and select multiple lines, then ctrl-x to un-comment the selected multiple lines\r\nsupports: c, c++, java, php[2345], proc, css, html, htm, xml, xhtml, vim, vimrc, sql, sh, ksh, csh, perl, tex, fortran, ml, caml, ocaml, vhdl, haskel and normal files","4":"Global Plugin to comment and un-comment lines in different source files in both normal and visual <Shift-V> mode\r\nusage:\r\nctrl-c to comment a single line\r\nctrl-x to un-comment a single line\r\nshift-v and select multiple lines, then ctrl-c to comment the selected multiple lines\r\nshift-v and select multiple lines, then ctrl-x to un-comment the selected multiple lines\r\nsupports: c, c++, java, php[2345], proc, css, html, htm, xml, xhtml, vim, vimrc, sql, sh, ksh, csh, perl, tex, fortran, ml, caml, ocaml, vhdl, haskel and normal files","install_details":"For VIM 6 and higher -                                                                                  \r\nStick this file in your ~\/.vim\/plugin directory or in some other \\'plugin\\' directory that is in your runtime path                                \r\nFor VIM 5 -                                                                                  \r\nStick this file somewhere and \\'source <path>\/comments.vim\\' it from your ~\/.vimrc file","5":"For VIM 6 and higher -                                                                                  \r\nStick this file in your ~\/.vim\/plugin directory or in some other \\'plugin\\' directory that is in your runtime path                                \r\nFor VIM 5 -                                                                                  \r\nStick this file somewhere and \\'source <path>\/comments.vim\\' it from your ~\/.vimrc file","first_name":"Jasmeet Singh","6":"Jasmeet Singh","last_name":"Anand","7":"Anand","releases":[{"0":"1528","vim_version":"7.0","1":"7.0","script_version":"2.12","2":"2.12","version_comment":"fix for haskel files as provided by Jean-Marie","3":"fix for haskel files as provided by Jean-Marie","package":"comments.vim","4":"comments.vim","src_id":"9801","5":"9801","creation_date":"1231703148","6":"1231703148"}]},"1527":{"script_id":"1527","0":"1527","script_name":"habiLight","1":"habiLight","script_type":"color scheme","2":"color scheme","summary":"A light color scheme with support of Vim 7 features","3":"A light color scheme with support of Vim 7 features","description":"This is a color scheme for light background. It can be used with Vim 6 and 7. It is based on nuvola from Johann Pfefferl (vimscript #719). I changed some colors and added support of punctuators, operators, vim 7 features like omni completion, spell checking...\r\n\r\nScreenshot: http:\/\/vim.habermann-net.de\/wp-content\/uploads\/sites\/2\/2013\/12\/habiLight.png\r\n","4":"This is a color scheme for light background. It can be used with Vim 6 and 7. It is based on nuvola from Johann Pfefferl (vimscript #719). I changed some colors and added support of punctuators, operators, vim 7 features like omni completion, spell checking...\r\n\r\nScreenshot: http:\/\/vim.habermann-net.de\/wp-content\/uploads\/sites\/2\/2013\/12\/habiLight.png\r\n","install_details":"Copy this script into your local colors directory (~\/.vim\/colors\/).\r\n\r\nTo support highlighting of C\/C++ operators and punctuators as shown in the screenshot above download c.vim from http:\/\/vim.habermann-net.de\/files\/vim\/after\/syntax\/c.vim\r\nand copy it into your local after\/syntax directory (~\/.vim\/after\/syntax).\r\n","5":"Copy this script into your local colors directory (~\/.vim\/colors\/).\r\n\r\nTo support highlighting of C\/C++ operators and punctuators as shown in the screenshot above download c.vim from http:\/\/vim.habermann-net.de\/files\/vim\/after\/syntax\/c.vim\r\nand copy it into your local after\/syntax directory (~\/.vim\/after\/syntax).\r\n","first_name":"Christian","6":"Christian","last_name":"Habermann","7":"Habermann","releases":[{"0":"1527","vim_version":"7.0","1":"7.0","script_version":"1.2","2":"1.2","version_comment":"Initial upload","3":"Initial upload","package":"habiLight.vim","4":"habiLight.vim","src_id":"5611","5":"5611","creation_date":"1145962818","6":"1145962818"}]},"1526":{"script_id":"1526","0":"1526","script_name":"javaimports.vim","1":"javaimports.vim","script_type":"utility","2":"utility","summary":"Inserts all import clauses to your java source file","3":"Inserts all import clauses to your java source file","description":"This plugin let you write your java application in vim, \r\nwithout taking care about import clauses. Just press `ii (` == backticks)\r\nto insert all neccessary imports.\r\n\r\nOnly for GNU Linux OS.\r\n\r\n","4":"This plugin let you write your java application in vim, \r\nwithout taking care about import clauses. Just press `ii (` == backticks)\r\nto insert all neccessary imports.\r\n\r\nOnly for GNU Linux OS.\r\n\r\n","install_details":"See README in the tarball","5":"See README in the tarball","first_name":"Steve","6":"Steve","last_name":"Kreyer","7":"Kreyer","releases":[{"0":"1526","vim_version":"8.0","1":"8.0","script_version":"1.0.0","2":"1.0.0","version_comment":"better usability when choosing between choices \r\nrework of JRE class extraction: \r\n* Classes are generated during \"make install\"=> independent from JDK version now => if you install new jdk you should rerun make clean; make install \r\n\r\nknown limitations: \r\n* Class names in the java code written inside strings (encapsulated in quotes) are recognized as false positives.","3":"better usability when choosing between choices \r\nrework of JRE class extraction: \r\n* Classes are generated during \"make install\"=> independent from JDK version now => if you install new jdk you should rerun make clean; make install \r\n\r\nknown limitations: \r\n* Class names in the java code written inside strings (encapsulated in quotes) are recognized as false positives.","package":"vim_javaimports.tar.gz","4":"vim_javaimports.tar.gz","src_id":"25983","5":"25983","creation_date":"1526764059","6":"1526764059"},{"0":"1526","vim_version":"6.0","1":"6.0","script_version":"0.0.6","2":"0.0.6","version_comment":"- Added Filetype auto command","3":"- Added Filetype auto command","package":"vim_javaimports.tar.gz","4":"vim_javaimports.tar.gz","src_id":"5610","5":"5610","creation_date":"1145959376","6":"1145959376"},{"0":"1526","vim_version":"6.0","1":"6.0","script_version":"0.0.5","2":"0.0.5","version_comment":"- Fixed bug  in vim script file\r\n- Added org.* classes to lib\r\n- Changed installation directory to ~\/.vim directory, \r\n  so an installation as root is no longer required","3":"- Fixed bug  in vim script file\r\n- Added org.* classes to lib\r\n- Changed installation directory to ~\/.vim directory, \r\n  so an installation as root is no longer required","package":"vim_javaimports.tar.gz","4":"vim_javaimports.tar.gz","src_id":"5605","5":"5605","creation_date":"1145940146","6":"1145940146"},{"0":"1526","vim_version":"6.0","1":"6.0","script_version":"0.0.3","2":"0.0.3","version_comment":"Make the plugin a little bit more user friendly.\r\nIf ambiguous imports occure, the user can choose\r\nwhich import clause to insert.","3":"Make the plugin a little bit more user friendly.\r\nIf ambiguous imports occure, the user can choose\r\nwhich import clause to insert.","package":"vim_javaimports.tar.gz","4":"vim_javaimports.tar.gz","src_id":"5602","5":"5602","creation_date":"1145885480","6":"1145885480"},{"0":"1526","vim_version":"6.0","1":"6.0","script_version":"0.0.2","2":"0.0.2","version_comment":"Changed key mapping from Ctrl-i to `ii","3":"Changed key mapping from Ctrl-i to `ii","package":"vim_javaimports.tar.gz","4":"vim_javaimports.tar.gz","src_id":"5599","5":"5599","creation_date":"1145872428","6":"1145872428"},{"0":"1526","vim_version":"6.0","1":"6.0","script_version":"0.0.1","2":"0.0.1","version_comment":"Initial upload","3":"Initial upload","package":"vim_javaimports.tar.gz","4":"vim_javaimports.tar.gz","src_id":"5595","5":"5595","creation_date":"1145865567","6":"1145865567"}]},"1525":{"script_id":"1525","0":"1525","script_name":"vbnet.vim","1":"vbnet.vim","script_type":"syntax","2":"syntax","summary":"Syntax highlighting for VB.NET","3":"Syntax highlighting for VB.NET","description":"Although VB.NET is really just a new version of VB, the differences seemed large enough to warrant new syntax highlighting.  Nonetheless, this file aims to be backwards compatible with classic VB, although some deprecated VB syntax may be flagged as an error.\r\n\r\nFolding is supported. Try \":set foldmethod=syntax\".\r\n\r\nI haven't done any VB since that one semester in college. I'd appreciate someone taking over this file and submitting it to be included in Vim. I believe it to be a rename and :%s\/vbnet\/vb\/g away from being a far superior replacement for the vb.vim included with Vim, but it is terrible at VBScript, which vb.vim also handles.\r\n","4":"Although VB.NET is really just a new version of VB, the differences seemed large enough to warrant new syntax highlighting.  Nonetheless, this file aims to be backwards compatible with classic VB, although some deprecated VB syntax may be flagged as an error.\r\n\r\nFolding is supported. Try \":set foldmethod=syntax\".\r\n\r\nI haven't done any VB since that one semester in college. I'd appreciate someone taking over this file and submitting it to be included in Vim. I believe it to be a rename and :%s\/vbnet\/vb\/g away from being a far superior replacement for the vb.vim included with Vim, but it is terrible at VBScript, which vb.vim also handles.\r\n","install_details":"Copy vbnet.vim to your syntax directory (.vim\/syntax or vimfiles\/syntax in your home directory).  To activate it, use the command \":set ft=vbnet\".\r\n\r\nThe following autocmd can be added to your vimrc to automatically set the filetype (and activate syntax highlighting) for all VB.NET files.\r\n\r\nautocmd BufNewFile,BufRead *.vb set ft=vbnet","5":"Copy vbnet.vim to your syntax directory (.vim\/syntax or vimfiles\/syntax in your home directory).  To activate it, use the command \":set ft=vbnet\".\r\n\r\nThe following autocmd can be added to your vimrc to automatically set the filetype (and activate syntax highlighting) for all VB.NET files.\r\n\r\nautocmd BufNewFile,BufRead *.vb set ft=vbnet","first_name":"Tim","6":"Tim","last_name":"Pope","7":"Pope","releases":[{"0":"1525","vim_version":"6.0","1":"6.0","script_version":"1.7","2":"1.7","version_comment":"Fixed bugs reported by John Lenz","3":"Fixed bugs reported by John Lenz","package":"vbnet.vim","4":"vbnet.vim","src_id":"5622","5":"5622","creation_date":"1146216181","6":"1146216181"},{"0":"1525","vim_version":"6.0","1":"6.0","script_version":"1.4","2":"1.4","version_comment":"Initial upload","3":"Initial upload","package":"vbnet.vim","4":"vbnet.vim","src_id":"5591","5":"5591","creation_date":"1145800366","6":"1145800366"}]},"1524":{"script_id":"1524","0":"1524","script_name":"magic.vim","1":"magic.vim","script_type":"syntax","2":"syntax","summary":"Syntax highlighting for file's magic","3":"Syntax highlighting for file's magic","description":"This script provides syntax highlighting for magic definitions of the file utility.  The highlighting is strict, everything non-matching is marked as an error (please report problems).","4":"This script provides syntax highlighting for magic definitions of the file utility.  The highlighting is strict, everything non-matching is marked as an error (please report problems).","install_details":"The recommended file type autocommand is\r\n\r\nau BufRead,BufNewFile magic,**\/Magdir\/* setf magic","5":"The recommended file type autocommand is\r\n\r\nau BufRead,BufNewFile magic,**\/Magdir\/* setf magic","first_name":"David","6":"David","last_name":"Necas","7":"Necas","releases":[{"0":"1524","vim_version":"5.7","1":"5.7","script_version":"20060423","2":"20060423","version_comment":"Initial upload","3":"Initial upload","package":"magic.vim","4":"magic.vim","src_id":"5590","5":"5590","creation_date":"1145799768","6":"1145799768"}]},"1523":{"script_id":"1523","0":"1523","script_name":"cmaxx","1":"cmaxx","script_type":"utility","2":"utility","summary":"Expands user defined templates for any filetype.","3":"Expands user defined templates for any filetype.","description":"This script was inspired by Borland Delphis code template function.\r\n\r\nTemplates can be defined in text files. The filename (wihtout extension) is the template name. By entering the template name in the document and pressing the expasion key (predefined to <F6>) the template is expanded.\r\n\r\nTemplates can also use macros which will be replaced bei either a user defined or a predefined text during template expansion.","4":"This script was inspired by Borland Delphis code template function.\r\n\r\nTemplates can be defined in text files. The filename (wihtout extension) is the template name. By entering the template name in the document and pressing the expasion key (predefined to <F6>) the template is expanded.\r\n\r\nTemplates can also use macros which will be replaced bei either a user defined or a predefined text during template expansion.","install_details":"The fastest way to install the script is to unpack the tarball to you local script folder, start vim and follow the instructions.\r\n\r\nThe best way to add this script to vim is to put it in the plugin directory in the user's vim folder (for Unix\/Linux: ~\/.vim\/plugin; for Windows: ~\/vimfiles\/plugin, for more inforation see |.vimrc|).  Then the script will be sourced automatically at the startup.\r\n\r\nThe script relies on a folder where the defined templates reside.  The location of this folder is defined in the variable 'g:CMAxx_TemplateDir'.  The script does not define a default path so it does not work if the variable is not set.  A possible location would be ~\/.vim\/templates.\r\n\r\nThe script comes with a number of templates in the \"templates\" folder.  Move this folder to your preferred location and set 'g:CMAxx_TemplateDir' to this path.  The folder \"templates\" should be part of this path.  A good choice would be local scripts folder.\r\n\r\nThe script will create some mappings.  These mappings can be turned off by two variables.  If the variable 'g:CMAxx_NoExpansionKey' is defined, the mappings for |F6|, |i_F6| and |n_F6| will not be created.  If 'g:CMAxx_NoMappings' is set, all the leader-mappings will not be set.\r\n\r\nDon't forget to run \":helptags\" at the location where you have installed cmaxx.\r\n\r\n\r\nBug reports and feature requests are welcome!","5":"The fastest way to install the script is to unpack the tarball to you local script folder, start vim and follow the instructions.\r\n\r\nThe best way to add this script to vim is to put it in the plugin directory in the user's vim folder (for Unix\/Linux: ~\/.vim\/plugin; for Windows: ~\/vimfiles\/plugin, for more inforation see |.vimrc|).  Then the script will be sourced automatically at the startup.\r\n\r\nThe script relies on a folder where the defined templates reside.  The location of this folder is defined in the variable 'g:CMAxx_TemplateDir'.  The script does not define a default path so it does not work if the variable is not set.  A possible location would be ~\/.vim\/templates.\r\n\r\nThe script comes with a number of templates in the \"templates\" folder.  Move this folder to your preferred location and set 'g:CMAxx_TemplateDir' to this path.  The folder \"templates\" should be part of this path.  A good choice would be local scripts folder.\r\n\r\nThe script will create some mappings.  These mappings can be turned off by two variables.  If the variable 'g:CMAxx_NoExpansionKey' is defined, the mappings for |F6|, |i_F6| and |n_F6| will not be created.  If 'g:CMAxx_NoMappings' is set, all the leader-mappings will not be set.\r\n\r\nDon't forget to run \":helptags\" at the location where you have installed cmaxx.\r\n\r\n\r\nBug reports and feature requests are welcome!","first_name":"Markus","6":"Markus","last_name":"Trenkwalder","7":"Trenkwalder","releases":[{"0":"1523","vim_version":"6.0","1":"6.0","script_version":"1.1.0","2":"1.1.0","version_comment":"Added the possibility to select the value for a macro from a list (see \":help  macro-list-variables\").","3":"Added the possibility to select the value for a macro from a list (see \":help  macro-list-variables\").","package":"cmaxx-1.1.0.tar.gz","4":"cmaxx-1.1.0.tar.gz","src_id":"5703","5":"5703","creation_date":"1147701572","6":"1147701572"},{"0":"1523","vim_version":"6.0","1":"6.0","script_version":"1.0.3","2":"1.0.3","version_comment":"Fixed another bug with buffer local variables found by Andreas Karpfen.","3":"Fixed another bug with buffer local variables found by Andreas Karpfen.","package":"cmaxx-1.0.3.tar.gz","4":"cmaxx-1.0.3.tar.gz","src_id":"5620","5":"5620","creation_date":"1146105448","6":"1146105448"},{"0":"1523","vim_version":"6.0","1":"6.0","script_version":"1.0.2","2":"1.0.2","version_comment":"- Fixed some bugs regarding buffer local variables (thanx to Igor Prischepoff)\r\n- New feature: mappings can be tured off by two variables.","3":"- Fixed some bugs regarding buffer local variables (thanx to Igor Prischepoff)\r\n- New feature: mappings can be tured off by two variables.","package":"cmaxx-1.0.2.tar.gz","4":"cmaxx-1.0.2.tar.gz","src_id":"5618","5":"5618","creation_date":"1146027513","6":"1146027513"},{"0":"1523","vim_version":"6.0","1":"6.0","script_version":"1.0.1","2":"1.0.1","version_comment":"Works with vim 6.x again.","3":"Works with vim 6.x again.","package":"cmaxx-1.0.1.tar.gz","4":"cmaxx-1.0.1.tar.gz","src_id":"5604","5":"5604","creation_date":"1145938957","6":"1145938957"},{"0":"1523","vim_version":"7.0","1":"7.0","script_version":"1.0.0","2":"1.0.0","version_comment":"Initial upload","3":"Initial upload","package":"cmaxx-1.0.0.tar.gz","4":"cmaxx-1.0.0.tar.gz","src_id":"5587","5":"5587","creation_date":"1145596093","6":"1145596093"}]},"1522":{"script_id":"1522","0":"1522","script_name":"WinWalker.vim","1":"WinWalker.vim","script_type":"utility","2":"utility","summary":"Vim 7 windows navigator\/manager","3":"Vim 7 windows navigator\/manager","description":"  Features:                                            *WW_Features* {{{~\r\n\r\n   -   Navigate and manage windows and layouts with blinding speed!\r\n\r\n   -   Multiple window operations are faster and easier because it creates\r\n       a window navigation and management mode where all window commands\r\n       are familiar single chars,  i.e.  h,H,^H  and j,J,^J  etc.  If you\r\n       weren't using Vim in full-screen mode, you'll start considering it.\r\n\r\n   -   More added functionality:\r\n\r\n       -   Better [im]movability:\r\n\r\n           -   Enhanced push\/drag for windows and buffers.\r\n\r\n           -   Push\/drag\/exchange buffers between windows, and windows\r\n               between tabs.  Use adjacent tabs as if they were extensions\r\n               of the current visible screen.\r\n           \r\n           -   Constrained size and placement.  Windows can be 'attached'\r\n               to walls or other windows.\r\n\r\n       -   Quick search\/jump to any window in any tab by giving the first\r\n           unique char(s).  It jumps to a buffer's window, instead of the\r\n           default action of editing buffers in the current window.\r\n\r\n       -   More intuitive for many operations:\r\n           \r\n           -   Incremental resizing is easier, using the [HJKL] and\r\n               [^h^j^k^l].\r\n\r\n           -   Resize in the direction specified, unlike  wincmd + - < > \r\n\r\n           -   Windows move\/push past each other more like you'd expect.\r\n               They can push 'between', instead of just 'maximize at far\r\n               side'.\r\n\r\n       -   Other usability stuff:\r\n\r\n           -   A window-level jump list for ^I\/^O  movement.\r\n\r\n           -   O\/^O  as a tab-capable alternative to ^Wo .\r\n\r\n           -   Various shortcuts to help keep you from breaking your\r\n               stride, i.e. to  :edit,  :ex  mode, sessions, macros, remapping\r\n\r\n   -   All the commands are presented as a prompt menu in the command line\r\n       so forgetting stuff isn't a problem.\r\n\r\n   -   Many of the commands are the same as the default Vim window  ^W  and\r\n       'wincmd' for easy transition, others are shifted around to be more\r\n       consistent.\r\n\r\n   -   Different invocation modes:  |WW_timeoutlen| for menu, key pass-through.\r\n       The goal is to have the menu mode there when you want it, and keep\r\n       quiet otherwise.  Experiment with the different methods to find\r\n       what works best for you.\r\n\r\n\r\n\r\n  Useful Examples:                                            *WW_Useful_Examples* {{{~\r\n\r\n    ... Or, 'How is this going to help me?'\r\n\r\n\r\n    Ergonomics:\r\n\r\n        Overall speed dealing with multiple windows.  Try it out:\r\n\r\n        -   Start the WinWalker menu, ^W\r\n        -   Open a new tab with  'N'\r\n        -   Open a few windows with  'n' and 'v'\r\n        -   Jump around a little with  '[hljk]'\r\n        -   Put some files in them with 'e'\r\n        -   Push some around with '[HLJK]'\r\n        -   Smack them all down with 'q'\r\n\r\n        By now you should have a feel for the difference it makes to have\r\n        single keys to deal with the window system.\r\n\r\n\r\n    AutoResizing:\r\n\r\n        -   Your screen\/terminal\/GUI size will no longer cramp your style.\r\n            Create windows that are always big enough.\r\n\r\n            Example:  You have several windows open, vertical and\r\n            horizontal, which you set to 80 columns, but you only have\r\n            120 or whatever.\r\n\r\n            -   Quickly visit each window, set the dimensions with 'c'.\r\n                See |WW_Misc_Menu| => |WW_presets| if you want to change\r\n                the values.\r\n            \r\n            -   For more individualized sizing,  'grow' the window to\r\n                whatever size makes sense, and use the\r\n                |WW_Attach_Constrain_Menu| -> lc 'lock columns' (and\/or\r\n                'll') command to cause the window to resize itself to the\r\n                current size each time it is entered.\r\n\r\n            Now all those windows will resize themselves each time they are\r\n            entered.\r\n\r\n    Templates:\r\n\r\n    -   Store a tab to a session with the windows arranged how you\r\n        want.\r\n\r\n    -   Create a macro key to retrieve the template like:\r\n\r\n        <F2>    srsessname^M\r\n\r\n                s               save menu\r\n                 r              restore\r\n                  sessname      name of the session (without Session. or .vim )\r\n                          ^M    literal carriage return, with ^V^M or ^Q^M\r\n                    \r\n\r\n    Keeping Track Of Buffers:\r\n\r\n        If you're using TabLineSet.vim with the verbose option, you'll be\r\n        able to see all open buffers in the tabline (especially if you have\r\n        the 'Tabline wrapping patch' installed).\r\n\r\n        The find, '\/', command will show you all loaded buffers, or '?' for\r\n        all buffers.\r\n\r\n","4":"  Features:                                            *WW_Features* {{{~\r\n\r\n   -   Navigate and manage windows and layouts with blinding speed!\r\n\r\n   -   Multiple window operations are faster and easier because it creates\r\n       a window navigation and management mode where all window commands\r\n       are familiar single chars,  i.e.  h,H,^H  and j,J,^J  etc.  If you\r\n       weren't using Vim in full-screen mode, you'll start considering it.\r\n\r\n   -   More added functionality:\r\n\r\n       -   Better [im]movability:\r\n\r\n           -   Enhanced push\/drag for windows and buffers.\r\n\r\n           -   Push\/drag\/exchange buffers between windows, and windows\r\n               between tabs.  Use adjacent tabs as if they were extensions\r\n               of the current visible screen.\r\n           \r\n           -   Constrained size and placement.  Windows can be 'attached'\r\n               to walls or other windows.\r\n\r\n       -   Quick search\/jump to any window in any tab by giving the first\r\n           unique char(s).  It jumps to a buffer's window, instead of the\r\n           default action of editing buffers in the current window.\r\n\r\n       -   More intuitive for many operations:\r\n           \r\n           -   Incremental resizing is easier, using the [HJKL] and\r\n               [^h^j^k^l].\r\n\r\n           -   Resize in the direction specified, unlike  wincmd + - < > \r\n\r\n           -   Windows move\/push past each other more like you'd expect.\r\n               They can push 'between', instead of just 'maximize at far\r\n               side'.\r\n\r\n       -   Other usability stuff:\r\n\r\n           -   A window-level jump list for ^I\/^O  movement.\r\n\r\n           -   O\/^O  as a tab-capable alternative to ^Wo .\r\n\r\n           -   Various shortcuts to help keep you from breaking your\r\n               stride, i.e. to  :edit,  :ex  mode, sessions, macros, remapping\r\n\r\n   -   All the commands are presented as a prompt menu in the command line\r\n       so forgetting stuff isn't a problem.\r\n\r\n   -   Many of the commands are the same as the default Vim window  ^W  and\r\n       'wincmd' for easy transition, others are shifted around to be more\r\n       consistent.\r\n\r\n   -   Different invocation modes:  |WW_timeoutlen| for menu, key pass-through.\r\n       The goal is to have the menu mode there when you want it, and keep\r\n       quiet otherwise.  Experiment with the different methods to find\r\n       what works best for you.\r\n\r\n\r\n\r\n  Useful Examples:                                            *WW_Useful_Examples* {{{~\r\n\r\n    ... Or, 'How is this going to help me?'\r\n\r\n\r\n    Ergonomics:\r\n\r\n        Overall speed dealing with multiple windows.  Try it out:\r\n\r\n        -   Start the WinWalker menu, ^W\r\n        -   Open a new tab with  'N'\r\n        -   Open a few windows with  'n' and 'v'\r\n        -   Jump around a little with  '[hljk]'\r\n        -   Put some files in them with 'e'\r\n        -   Push some around with '[HLJK]'\r\n        -   Smack them all down with 'q'\r\n\r\n        By now you should have a feel for the difference it makes to have\r\n        single keys to deal with the window system.\r\n\r\n\r\n    AutoResizing:\r\n\r\n        -   Your screen\/terminal\/GUI size will no longer cramp your style.\r\n            Create windows that are always big enough.\r\n\r\n            Example:  You have several windows open, vertical and\r\n            horizontal, which you set to 80 columns, but you only have\r\n            120 or whatever.\r\n\r\n            -   Quickly visit each window, set the dimensions with 'c'.\r\n                See |WW_Misc_Menu| => |WW_presets| if you want to change\r\n                the values.\r\n            \r\n            -   For more individualized sizing,  'grow' the window to\r\n                whatever size makes sense, and use the\r\n                |WW_Attach_Constrain_Menu| -> lc 'lock columns' (and\/or\r\n                'll') command to cause the window to resize itself to the\r\n                current size each time it is entered.\r\n\r\n            Now all those windows will resize themselves each time they are\r\n            entered.\r\n\r\n    Templates:\r\n\r\n    -   Store a tab to a session with the windows arranged how you\r\n        want.\r\n\r\n    -   Create a macro key to retrieve the template like:\r\n\r\n        <F2>    srsessname^M\r\n\r\n                s               save menu\r\n                 r              restore\r\n                  sessname      name of the session (without Session. or .vim )\r\n                          ^M    literal carriage return, with ^V^M or ^Q^M\r\n                    \r\n\r\n    Keeping Track Of Buffers:\r\n\r\n        If you're using TabLineSet.vim with the verbose option, you'll be\r\n        able to see all open buffers in the tabline (especially if you have\r\n        the 'Tabline wrapping patch' installed).\r\n\r\n        The find, '\/', command will show you all loaded buffers, or '?' for\r\n        all buffers.\r\n\r\n","install_details":"        -   Unzip the distribution file above your plugin to extract:\r\n\r\n                plugin\/WinWalker.vim\r\n                plugin\/Char_menu.vim\r\n                doc\/WinWalker.txt\r\n\r\n\r\n        -   Set up a key map.  I.e.\r\n\r\n                nmap <silent> <Leader>w :call WinWalkerMenu()<CR>\r\n\r\n                    Default.  I like it mapped to ^W, since I'm used to\r\n                    hitting ^W for windows stuff, and WinWalker is mostly a\r\n                    superset of the standard ^W\/wincmd commands.\r\n\r\n        -   Look through the |WW_Misc_Menu| and |WW_Customizing| for other\r\n            options to change.\r\n\r\n","5":"        -   Unzip the distribution file above your plugin to extract:\r\n\r\n                plugin\/WinWalker.vim\r\n                plugin\/Char_menu.vim\r\n                doc\/WinWalker.txt\r\n\r\n\r\n        -   Set up a key map.  I.e.\r\n\r\n                nmap <silent> <Leader>w :call WinWalkerMenu()<CR>\r\n\r\n                    Default.  I like it mapped to ^W, since I'm used to\r\n                    hitting ^W for windows stuff, and WinWalker is mostly a\r\n                    superset of the standard ^W\/wincmd commands.\r\n\r\n        -   Look through the |WW_Misc_Menu| and |WW_Customizing| for other\r\n            options to change.\r\n\r\n","first_name":"Eric","6":"Eric","last_name":"Arnold","7":"Arnold","releases":[{"0":"1522","vim_version":"7.0","1":"7.0","script_version":"2.2","2":"2.2","version_comment":"-\tRevamped window jump list ( ^I and ^O ); better\r\ntracking, cleanup, and display.\r\n-\tFixed a few problems with the find command and\r\nmenu handler returning early\r\n-\tSeparated startup and menu timeoutlen[s].\r\n-\tUpdated help file.\r\n","3":"-\tRevamped window jump list ( ^I and ^O ); better\r\ntracking, cleanup, and display.\r\n-\tFixed a few problems with the find command and\r\nmenu handler returning early\r\n-\tSeparated startup and menu timeoutlen[s].\r\n-\tUpdated help file.\r\n","package":"WinWalker.2.2.zip","4":"WinWalker.2.2.zip","src_id":"5784","5":"5784","creation_date":"1148792783","6":"1148792783"},{"0":"1522","vim_version":"7.0","1":"7.0","script_version":"2.1","2":"2.1","version_comment":"-\tadded 'follow' option, \r\n-\t'c' preset now sets the sticky auto-resize, \r\n\tline\/column values, \r\n-\twindows and buffers auto-resize separately, \r\n-\tsmall cmdheight bug, \r\n-\tsmarter hondling of 'previous' window, \r\n-\tvarious sizing fixes, \r\n","3":"-\tadded 'follow' option, \r\n-\t'c' preset now sets the sticky auto-resize, \r\n\tline\/column values, \r\n-\twindows and buffers auto-resize separately, \r\n-\tsmall cmdheight bug, \r\n-\tsmarter hondling of 'previous' window, \r\n-\tvarious sizing fixes, \r\n","package":"WinWalker.2.1.zip","4":"WinWalker.2.1.zip","src_id":"5707","5":"5707","creation_date":"1147769648","6":"1147769648"},{"0":"1522","vim_version":"7.0","1":"7.0","script_version":"2.0","2":"2.0","version_comment":"-\tConstrained size and placement.  Windows can be\r\n'attached' to walls or other windows.\r\n-\tAdded key feedkeys() macros\r\n-\tSessions remember WinWalker constraints\r\n","3":"-\tConstrained size and placement.  Windows can be\r\n'attached' to walls or other windows.\r\n-\tAdded key feedkeys() macros\r\n-\tSessions remember WinWalker constraints\r\n","package":"WinWalker.2.0.zip","4":"WinWalker.2.0.zip","src_id":"5621","5":"5621","creation_date":"1146125932","6":"1146125932"},{"0":"1522","vim_version":"7.0","1":"7.0","script_version":"1.2.1","2":"1.2.1","version_comment":"Restored accidentally deleted function, kill spurious debug msg","3":"Restored accidentally deleted function, kill spurious debug msg","package":"WinWalker.1.2.1.zip","4":"WinWalker.1.2.1.zip","src_id":"5596","5":"5596","creation_date":"1145866772","6":"1145866772"},{"0":"1522","vim_version":"7.0","1":"7.0","script_version":"1.2","2":"1.2","version_comment":"-\thandle copen and exchange\/push\r\n-\tfixed searching by bufnr bug\r\n-\tswitch to Unix file format\r\n-\tadded session quick-save\r\n-\trevamped help and help folding\r\n","3":"-\thandle copen and exchange\/push\r\n-\tfixed searching by bufnr bug\r\n-\tswitch to Unix file format\r\n-\tadded session quick-save\r\n-\trevamped help and help folding\r\n","package":"WinWalker.1.2.zip","4":"WinWalker.1.2.zip","src_id":"5592","5":"5592","creation_date":"1145847240","6":"1145847240"},{"0":"1522","vim_version":"7.0","1":"7.0","script_version":"1.1","2":"1.1","version_comment":" -   Added help extraction to standard help\r\n -   Tweaked to handle Taglist.vim\r\n","3":" -   Added help extraction to standard help\r\n -   Tweaked to handle Taglist.vim\r\n","package":"WinWalker.zip","4":"WinWalker.zip","src_id":"5588","5":"5588","creation_date":"1145634234","6":"1145634234"},{"0":"1522","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"WinWalker.zip","4":"WinWalker.zip","src_id":"5581","5":"5581","creation_date":"1145423792","6":"1145423792"}]},"1521":{"script_id":"1521","0":"1521","script_name":"maven2.vim","1":"maven2.vim","script_type":"utility","2":"utility","summary":"Compiler plugin for maven2","3":"Compiler plugin for maven2","description":"This is a simple compiler plugin to use quickfix with maven2. It sets\r\nmakeprg to \"mvn\", and sets the errorformat appropriately. Activate\r\nwith \"compiler maven2\".\r\n\r\nSince this expects the pom.xml to be in the current working directory,\r\ntry adding something like the following to your .vimrc:\r\n\r\naugroup my-project-X\r\n  au!\r\n  autocmd BufNewFile,BufRead    *\/project\/x\/*       lcd <directory-containing-pom>\r\n  autocmd BufNewFile,BufRead    *\/project\/x\/*       compiler maven2\r\naugroup END\r\n\r\nKnown problems: the compiler output uses a 0-based column number, but vim\r\nexpects a 1-based column, so the cursor is off by one.\r\n","4":"This is a simple compiler plugin to use quickfix with maven2. It sets\r\nmakeprg to \"mvn\", and sets the errorformat appropriately. Activate\r\nwith \"compiler maven2\".\r\n\r\nSince this expects the pom.xml to be in the current working directory,\r\ntry adding something like the following to your .vimrc:\r\n\r\naugroup my-project-X\r\n  au!\r\n  autocmd BufNewFile,BufRead    *\/project\/x\/*       lcd <directory-containing-pom>\r\n  autocmd BufNewFile,BufRead    *\/project\/x\/*       compiler maven2\r\naugroup END\r\n\r\nKnown problems: the compiler output uses a 0-based column number, but vim\r\nexpects a 1-based column, so the cursor is off by one.\r\n","install_details":"Put the script in your ~\/.vim\/compiler\/ directory.","5":"Put the script in your ~\/.vim\/compiler\/ directory.","first_name":"Ronald","6":"Ronald","last_name":"Tschal\u00c3\u00a4r","7":"Tschal\u00c3\u00a4r","releases":[{"0":"1521","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"maven2.vim","4":"maven2.vim","src_id":"5577","5":"5577","creation_date":"1145331492","6":"1145331492"}]},"1520":{"script_id":"1520","0":"1520","script_name":"OmniCppComplete","1":"OmniCppComplete","script_type":"ftplugin","2":"ftplugin","summary":"C\/C++ omni-completion with ctags database","3":"C\/C++ omni-completion with ctags database","description":"This script is for vim 7.0 or higher, it provides C\/C++ completion thanks to a ctags database.\r\n\r\nIf you don't want a completion based on ctags there are solutions using compiler front ends (real C++ parsing)\r\n    - \"clang\" with the following script : http:\/\/www.vim.org\/scripts\/script.php?script_id=3302\r\n    - \"gccsense\" : http:\/\/cx4a.org\/software\/gccsense\r\n\r\nFeatures :\r\n\r\n    -   Complete namespaces, classes, structs and union members.\r\n    -   Complete inherited members for classes and structs (single and multiple inheritance).\r\n    -   Complete attribute members eg: myObject->_child->_child etc...\r\n    -   Complete type returned by a function eg: myObject->get()->_child.\r\n    -   Complete the \"this\" pointer.\r\n    -   Complete a typedef.\r\n    -   Complete the current scope (global and class scope).\r\n    -   Complete an object after a cast (C and C++ cast).\r\n    -   Complete anonymous types (eg: struct {int a; int b;}g_Var; g_Var.???). It also works for a typedef of an anonymous type.\r\n\r\n\r\nNotes :\r\n    -   The script manage cached datas for optimization.\r\n    -   Ambiguous namespaces are detected and are not included in the context stack.\r\n    -   The parsed code is tokenized so you can run a completion even if the current \r\n        instruction has bad indentation, spaces, comments or carriage returns between words\r\n        (even if it is not realistic).\r\n\r\nScreenShots :\r\n\r\n    http:\/\/vissale.neang.free.fr\/Vim\/OmniCppComplete\/ScreenShots\/screenshots.htm\r\n","4":"This script is for vim 7.0 or higher, it provides C\/C++ completion thanks to a ctags database.\r\n\r\nIf you don't want a completion based on ctags there are solutions using compiler front ends (real C++ parsing)\r\n    - \"clang\" with the following script : http:\/\/www.vim.org\/scripts\/script.php?script_id=3302\r\n    - \"gccsense\" : http:\/\/cx4a.org\/software\/gccsense\r\n\r\nFeatures :\r\n\r\n    -   Complete namespaces, classes, structs and union members.\r\n    -   Complete inherited members for classes and structs (single and multiple inheritance).\r\n    -   Complete attribute members eg: myObject->_child->_child etc...\r\n    -   Complete type returned by a function eg: myObject->get()->_child.\r\n    -   Complete the \"this\" pointer.\r\n    -   Complete a typedef.\r\n    -   Complete the current scope (global and class scope).\r\n    -   Complete an object after a cast (C and C++ cast).\r\n    -   Complete anonymous types (eg: struct {int a; int b;}g_Var; g_Var.???). It also works for a typedef of an anonymous type.\r\n\r\n\r\nNotes :\r\n    -   The script manage cached datas for optimization.\r\n    -   Ambiguous namespaces are detected and are not included in the context stack.\r\n    -   The parsed code is tokenized so you can run a completion even if the current \r\n        instruction has bad indentation, spaces, comments or carriage returns between words\r\n        (even if it is not realistic).\r\n\r\nScreenShots :\r\n\r\n    http:\/\/vissale.neang.free.fr\/Vim\/OmniCppComplete\/ScreenShots\/screenshots.htm\r\n","install_details":"1) Unzip the plugin to ~\/.vim (unix) or %HOMEPATH%\\vimfiles (windows)\r\n2) Run Vim and type the following command :\r\n\r\n:helptags $HOME\/.vim\/doc\r\n\r\nor\r\n\r\n:helptags $HOME\/vimfiles\/doc\r\n\r\n3) Type :h omnicppcomplete and please read the installation paragraph.","5":"1) Unzip the plugin to ~\/.vim (unix) or %HOMEPATH%\\vimfiles (windows)\r\n2) Run Vim and type the following command :\r\n\r\n:helptags $HOME\/.vim\/doc\r\n\r\nor\r\n\r\n:helptags $HOME\/vimfiles\/doc\r\n\r\n3) Type :h omnicppcomplete and please read the installation paragraph.","first_name":"Vissale","6":"Vissale","last_name":"NEANG","7":"NEANG","releases":[{"0":"1520","vim_version":"7.0","1":"7.0","script_version":"0.41","2":"0.41","version_comment":"-   It's recommended to update ctags to version 5.7 or higher\r\n-   The plugin is now activated for C files\r\n-   New value for OmniCpp_SelectFirstItem when the option is equal to\r\n    2 the first item is selected without inserting it to \r\n    the text (patch from Marek Olszewski)\r\n-   Bug when completing union members fixed with ctags 5.7 \r\n    (reported by Willem-Jan de Hoog) \r\n-   New option OmniCpp_LocalSearchDecl (patch from Roland Kuck)\r\n-   Bug when tags=something,,somethingelse (reported by Tobias Pflug)\r\n-   Bug with nested structure (reported by Mikhail Daen)\r\n-   Bug where the script fails to detect the type of a variable when \r\n    the ignorecase option is on (reported by Alexey Vakhov)\r\n-   Error message when trying to use completion on a not yet saved \r\n    Vim buffer (reported by Neil Bird)\r\n-   Error message when trying to use completion on an file opened from \r\n    a tselect command (reported by Henrique Andrade)\r\n\r\n","3":"-   It's recommended to update ctags to version 5.7 or higher\r\n-   The plugin is now activated for C files\r\n-   New value for OmniCpp_SelectFirstItem when the option is equal to\r\n    2 the first item is selected without inserting it to \r\n    the text (patch from Marek Olszewski)\r\n-   Bug when completing union members fixed with ctags 5.7 \r\n    (reported by Willem-Jan de Hoog) \r\n-   New option OmniCpp_LocalSearchDecl (patch from Roland Kuck)\r\n-   Bug when tags=something,,somethingelse (reported by Tobias Pflug)\r\n-   Bug with nested structure (reported by Mikhail Daen)\r\n-   Bug where the script fails to detect the type of a variable when \r\n    the ignorecase option is on (reported by Alexey Vakhov)\r\n-   Error message when trying to use completion on a not yet saved \r\n    Vim buffer (reported by Neil Bird)\r\n-   Error message when trying to use completion on an file opened from \r\n    a tselect command (reported by Henrique Andrade)\r\n\r\n","package":"omnicppcomplete-0.41.zip","4":"omnicppcomplete-0.41.zip","src_id":"7722","5":"7722","creation_date":"1190883343","6":"1190883343"},{"0":"1520","vim_version":"7.0","1":"7.0","script_version":"0.4","2":"0.4","version_comment":"WARNING1: Please uninstall the previous version (remove at least autoload\/cppomnicomplete.vim)\r\nWARNING2: Option names have changed, don't forget to update your .vimrc\r\nWARNING3: It's recommended to update ctags to the latest version (5.6)\r\nWARNING4: Default value for OmniCpp_NamespaceSearch option is now 1\r\n\r\n-   The script is renamed to OmniCppComplete according to the library\r\n    script directory structure.        \r\n-   OmniCpp_ClassScopeCompletionMethod renamed to OmniCpp_DisplayMode\r\n-   Fixed a bug where the quickfix list is modified after a completion.\r\n-   OmniCpp_ShowPrototypeInAbbr option added. It allows to show the\r\n    function signature in the abbreviation.\r\n-   OmniCpp_ShowAccess option added. It allows to hide the access\r\n    information in the popup menu.\r\n-   The tags database format must be a ctags 5.6 database if you want to \r\n    complete anonymous types.\r\n-   Fixed current scope detection not working properly in destructors.\r\n-   Don't show protected and private members according to the current scope. \r\n-   Overloaded functions are now filtered properly.\r\n-   New cache system using less memory.\r\n-   The class scope of a method is now resolved properly with \"using\r\n    namespace\" declarations.\r\n-   OmniCpp_SelectFirstItem option added. It allows to not select the first\r\n    item in the popup menu when 'completeopt' does not contain \"longest\".\r\n-   Fixed the bug where a \"random\" item in the popup menu is selected\r\n    by default when 'completeopt' does not contain \"longest\" option.\r\n-   The script is now split in library scripts.\r\n-   Cache added for 'using namespace' search in included files\r\n-   Default value for OmniCpp_NamespaceSearch is now 1 (search only in the\r\n    current buffer).\r\n-   Namespace search automatically disabled for C files even if \r\n    OmniCpp_NamespaceSearch != 0.\r\n-   To avoid linear search in tags files, the ignorecase option is now \r\n    disabled when getting tags datas (the user setting is restored after).\r\n-   Fixed a bug where friend functions may crash the script and also crash vim.","3":"WARNING1: Please uninstall the previous version (remove at least autoload\/cppomnicomplete.vim)\r\nWARNING2: Option names have changed, don't forget to update your .vimrc\r\nWARNING3: It's recommended to update ctags to the latest version (5.6)\r\nWARNING4: Default value for OmniCpp_NamespaceSearch option is now 1\r\n\r\n-   The script is renamed to OmniCppComplete according to the library\r\n    script directory structure.        \r\n-   OmniCpp_ClassScopeCompletionMethod renamed to OmniCpp_DisplayMode\r\n-   Fixed a bug where the quickfix list is modified after a completion.\r\n-   OmniCpp_ShowPrototypeInAbbr option added. It allows to show the\r\n    function signature in the abbreviation.\r\n-   OmniCpp_ShowAccess option added. It allows to hide the access\r\n    information in the popup menu.\r\n-   The tags database format must be a ctags 5.6 database if you want to \r\n    complete anonymous types.\r\n-   Fixed current scope detection not working properly in destructors.\r\n-   Don't show protected and private members according to the current scope. \r\n-   Overloaded functions are now filtered properly.\r\n-   New cache system using less memory.\r\n-   The class scope of a method is now resolved properly with \"using\r\n    namespace\" declarations.\r\n-   OmniCpp_SelectFirstItem option added. It allows to not select the first\r\n    item in the popup menu when 'completeopt' does not contain \"longest\".\r\n-   Fixed the bug where a \"random\" item in the popup menu is selected\r\n    by default when 'completeopt' does not contain \"longest\" option.\r\n-   The script is now split in library scripts.\r\n-   Cache added for 'using namespace' search in included files\r\n-   Default value for OmniCpp_NamespaceSearch is now 1 (search only in the\r\n    current buffer).\r\n-   Namespace search automatically disabled for C files even if \r\n    OmniCpp_NamespaceSearch != 0.\r\n-   To avoid linear search in tags files, the ignorecase option is now \r\n    disabled when getting tags datas (the user setting is restored after).\r\n-   Fixed a bug where friend functions may crash the script and also crash vim.","package":"omnicppcomplete.zip","4":"omnicppcomplete.zip","src_id":"5859","5":"5859","creation_date":"1151244927","6":"1151244927"}]},"1519":{"script_id":"1519","0":"1519","script_name":"icalendar.vim","1":"icalendar.vim","script_type":"syntax","2":"syntax","summary":"Syntax file for icalendar files","3":"Syntax file for icalendar files","description":"This is a very rudimentary syntax file for icalendar files (.ics), used by Apple's iCal, Mozilla's Sunbird, Google Calendar, and other software. A screenshot of the syntax highlighting using the \"koehler\" colorscheme is available here: http:\/\/severinghaus.org\/projects\/icalendar_syntax.png","4":"This is a very rudimentary syntax file for icalendar files (.ics), used by Apple's iCal, Mozilla's Sunbird, Google Calendar, and other software. A screenshot of the syntax highlighting using the \"koehler\" colorscheme is available here: http:\/\/severinghaus.org\/projects\/icalendar_syntax.png","install_details":"You may want to add something like this to your vimrc:\r\n\r\nautocmd! BufRead,BufNewFile *.ics setfiletype icalendar","5":"You may want to add something like this to your vimrc:\r\n\r\nautocmd! BufRead,BufNewFile *.ics setfiletype icalendar","first_name":"Steven","6":"Steven","last_name":"Severinghaus","7":"Severinghaus","releases":[{"0":"1519","vim_version":"6.0","1":"6.0","script_version":"0.3","2":"0.3","version_comment":"Various keywords are more precisely matched; more complete set of keywords; minor highlighting improvements; tested in 7.0b","3":"Various keywords are more precisely matched; more complete set of keywords; minor highlighting improvements; tested in 7.0b","package":"icalendar.vim","4":"icalendar.vim","src_id":"5573","5":"5573","creation_date":"1145281330","6":"1145281330"},{"0":"1519","vim_version":"6.0","1":"6.0","script_version":"0.2","2":"0.2","version_comment":"A bit prettier; various standard icalendar properties are recognized, dates highlighted, custom properties, etc.","3":"A bit prettier; various standard icalendar properties are recognized, dates highlighted, custom properties, etc.","package":"icalendar.vim","4":"icalendar.vim","src_id":"5569","5":"5569","creation_date":"1145208109","6":"1145208109"},{"0":"1519","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"icalendar.vim","4":"icalendar.vim","src_id":"5568","5":"5568","creation_date":"1145205162","6":"1145205162"}]},"1518":{"script_id":"1518","0":"1518","script_name":"ClassTree","1":"ClassTree","script_type":"utility","2":"utility","summary":"Display class\/interface hierarchy","3":"Display class\/interface hierarchy","description":"Define command \"CTree\" to display hierarchy of classes\/interfaces defined\r\n\r\nYou must build tag file using Exuberant Ctags with option \"--fields=+i\"\r\n\r\nWorks for C#. Should work for Java and any other single-inheritance OO language.","4":"Define command \"CTree\" to display hierarchy of classes\/interfaces defined\r\n\r\nYou must build tag file using Exuberant Ctags with option \"--fields=+i\"\r\n\r\nWorks for C#. Should work for Java and any other single-inheritance OO language.","install_details":"Drop CTree.vim into your favorite plugin directory or source the script from your .vimrc file","5":"Drop CTree.vim into your favorite plugin directory or source the script from your .vimrc file","first_name":"Yanbiao","6":"Yanbiao","last_name":"Zhao","7":"Zhao","releases":[{"0":"1518","vim_version":"7.0","1":"7.0","script_version":"1.1.2","2":"1.1.2","version_comment":"1. Clear the code to use taglist() instead of using command \"tselect\"\r\n\r\n2. Fix bug in detecting tag file changes","3":"1. Clear the code to use taglist() instead of using command \"tselect\"\r\n\r\n2. Fix bug in detecting tag file changes","package":"CTree.vim","4":"CTree.vim","src_id":"5657","5":"5657","creation_date":"1147096139","6":"1147096139"},{"0":"1518","vim_version":"7.0","1":"7.0","script_version":"1.1.1","2":"1.1.1","version_comment":"1. Add command \"CTag\". It will jump to class\/interface definition matching the tag\r\n\r\n2. Detect the changes to tag setting and tag files. If they are changed, type information will be reloaed automatically. Command \"CTreeReset\" is not necessary any more and removed.\r\n\r\n3. Add short cuts to command \"CTree\" and \"CTag\". They are commented out in the script. Uncomment them if you want.","3":"1. Add command \"CTag\". It will jump to class\/interface definition matching the tag\r\n\r\n2. Detect the changes to tag setting and tag files. If they are changed, type information will be reloaed automatically. Command \"CTreeReset\" is not necessary any more and removed.\r\n\r\n3. Add short cuts to command \"CTree\" and \"CTag\". They are commented out in the script. Uncomment them if you want.","package":"CTree.vim","4":"CTree.vim","src_id":"5639","5":"5639","creation_date":"1146668648","6":"1146668648"},{"0":"1518","vim_version":"7.0","1":"7.0","script_version":"1.1","2":"1.1","version_comment":"Add command \"CTreeReset\" to clear the cached tag information\r\n\r\nWill get parent of interface if it has only one parent.\r\n\r\nAdd prompt information when load tag information and display total number of entries in cache","3":"Add command \"CTreeReset\" to clear the cached tag information\r\n\r\nWill get parent of interface if it has only one parent.\r\n\r\nAdd prompt information when load tag information and display total number of entries in cache","package":"CTree.vim","4":"CTree.vim","src_id":"5567","5":"5567","creation_date":"1145192529","6":"1145192529"},{"0":"1518","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"CTree.vim","4":"CTree.vim","src_id":"5557","5":"5557","creation_date":"1145036832","6":"1145036832"}]},"1517":{"script_id":"1517","0":"1517","script_name":"changelog","1":"changelog","script_type":"utility","2":"utility","summary":"Create ChangeLog entry fast","3":"Create ChangeLog entry fast","description":"The python script creates automatically a ChangeLog entry (GNU style).\r\n\r\n","4":"The python script creates automatically a ChangeLog entry (GNU style).\r\n\r\n","install_details":"1. Create a directory python_plugins in your vim home and add the script.\r\n2. Configure the script by setting the following python trickery up in\r\nyour $Home\/.vimrc (thought thats an example!):\r\n\r\n  py << PY\r\n\r\n  import vim\r\n  import sys\r\n\r\n  # set the system path to the new directory\r\n  sys.path.append(\\'\/home\/roman\/.vim\/python-plugins\\')\r\n\r\n  # now we can import the python module\r\n  from utils import *\r\n\r\n  # set the variables (you may want to leave alone the cvs_command and\r\n  # svn_command\r\n  name = \\\"Roman Joost\\\"\r\n  email = \\\"<romanofski@gimp.org>\\\"\r\n  cvs_command = \\'cvs update -dP 2>&1 | grep -v \\\"Updating\\\"\\'\r\n  svn_command = \\'svn st\\'\r\n\r\n  PY\r\n\r\n3. You may want to bind the script to a key like:\r\n\r\n  map <F2> :py make_cl_entry(name, email, cvs_command, svn_command)<CR>","5":"1. Create a directory python_plugins in your vim home and add the script.\r\n2. Configure the script by setting the following python trickery up in\r\nyour $Home\/.vimrc (thought thats an example!):\r\n\r\n  py << PY\r\n\r\n  import vim\r\n  import sys\r\n\r\n  # set the system path to the new directory\r\n  sys.path.append(\\'\/home\/roman\/.vim\/python-plugins\\')\r\n\r\n  # now we can import the python module\r\n  from utils import *\r\n\r\n  # set the variables (you may want to leave alone the cvs_command and\r\n  # svn_command\r\n  name = \\\"Roman Joost\\\"\r\n  email = \\\"<romanofski@gimp.org>\\\"\r\n  cvs_command = \\'cvs update -dP 2>&1 | grep -v \\\"Updating\\\"\\'\r\n  svn_command = \\'svn st\\'\r\n\r\n  PY\r\n\r\n3. You may want to bind the script to a key like:\r\n\r\n  map <F2> :py make_cl_entry(name, email, cvs_command, svn_command)<CR>","first_name":"Roman","6":"Roman","last_name":"Joost","7":"Joost","releases":[{"0":"1517","vim_version":"7.0","1":"7.0","script_version":"0.2","2":"0.2","version_comment":"Initial upload","3":"Initial upload","package":"changelog_02.tar.gz","4":"changelog_02.tar.gz","src_id":"5554","5":"5554","creation_date":"1144984165","6":"1144984165"}]},"1516":{"script_id":"1516","0":"1516","script_name":"smcl.vim","1":"smcl.vim","script_type":"syntax","2":"syntax","summary":"vim syntax file for SMCL files","3":"vim syntax file for SMCL files","description":"smcl.vim is a syntax file for Stata's smcl- and hlp-files\r\n\r\nThis syntax file will help identify: \r\n\r\n* most smcl codes\r\n* errors in parens, brackets, ...\r\n","4":"smcl.vim is a syntax file for Stata's smcl- and hlp-files\r\n\r\nThis syntax file will help identify: \r\n\r\n* most smcl codes\r\n* errors in parens, brackets, ...\r\n","install_details":"I keep smcl.vim in $HOME\/.vim\/syntax\/ and associate smcl- and hlp-files in$HOME\/.vim\/filetypes.vim using the following:\r\n\r\naugroup filetypedetect\r\n        autocmd! BufRead,BufNewFile *.hlp       set filetype=smcl\r\n        autocmd! BufRead,BufNewFile *.ihlp      set filetype=smcl\r\n        autocmd! BufRead,BufNewFile *.smcl    set filetype=smcl\r\naugrougp END ","5":"I keep smcl.vim in $HOME\/.vim\/syntax\/ and associate smcl- and hlp-files in$HOME\/.vim\/filetypes.vim using the following:\r\n\r\naugroup filetypedetect\r\n        autocmd! BufRead,BufNewFile *.hlp       set filetype=smcl\r\n        autocmd! BufRead,BufNewFile *.ihlp      set filetype=smcl\r\n        autocmd! BufRead,BufNewFile *.smcl    set filetype=smcl\r\naugrougp END ","first_name":"Jeffrey","6":"Jeffrey","last_name":"Pitblado","7":"Pitblado","releases":[{"0":"1516","vim_version":"6.0","1":"6.0","script_version":"1.1.1","2":"1.1.1","version_comment":"'syntax clear' only under version control\r\ncheck for 'b:current_syntax', removed 'did_smcl_syntax_inits'","3":"'syntax clear' only under version control\r\ncheck for 'b:current_syntax', removed 'did_smcl_syntax_inits'","package":"smcl.vim","4":"smcl.vim","src_id":"5561","5":"5561","creation_date":"1145108683","6":"1145108683"},{"0":"1516","vim_version":"6.0","1":"6.0","script_version":"1.0.0","2":"1.0.0","version_comment":"Initial upload","3":"Initial upload","package":"smcl.vim","4":"smcl.vim","src_id":"5553","5":"5553","creation_date":"1144969387","6":"1144969387"}]},"1515":{"script_id":"1515","0":"1515","script_name":"VhdlNav","1":"VhdlNav","script_type":"utility","2":"utility","summary":"Keeps track of your position in a VHDL file","3":"Keeps track of your position in a VHDL file","description":"VHDL is very repetitive in nature.  Often, when looking at only a small section of code that's visibile in the window, it's difficult to glean exactly where you are.  \r\n\r\nFor example, if you have four instances of a component, each 100 lines long.  It can be difficult to know which instance your in without navigating away from your current spot, which I find annoying.\r\n\r\nTo address this, I wrote a script which shows a window displaying snippits of code representing what I consider the major entry points of the source.  The script then determines where you are relative to the snippits, and highlights the snippit above your current location.\r\n\r\nSnippits currently include:\r\nentity declaration\r\ncomponent declaration\r\nfirst line of an instatiation \r\nfirst line of a process\r\nhorizontal lines created from comments (displays the next line as the snippit)\r\n\r\nAs an added bonus, you can also double-click (or hit enter) in the Vhdl_Nav window to jump to the section of code represented by the snippit.\r\n\r\nThis isn't the first script I've ever written, but it's the first I've attempted to write for others to use.  So, while it's been working great for me, you've been warned.  I welcome any feedback and suggestions.","4":"VHDL is very repetitive in nature.  Often, when looking at only a small section of code that's visibile in the window, it's difficult to glean exactly where you are.  \r\n\r\nFor example, if you have four instances of a component, each 100 lines long.  It can be difficult to know which instance your in without navigating away from your current spot, which I find annoying.\r\n\r\nTo address this, I wrote a script which shows a window displaying snippits of code representing what I consider the major entry points of the source.  The script then determines where you are relative to the snippits, and highlights the snippit above your current location.\r\n\r\nSnippits currently include:\r\nentity declaration\r\ncomponent declaration\r\nfirst line of an instatiation \r\nfirst line of a process\r\nhorizontal lines created from comments (displays the next line as the snippit)\r\n\r\nAs an added bonus, you can also double-click (or hit enter) in the Vhdl_Nav window to jump to the section of code represented by the snippit.\r\n\r\nThis isn't the first script I've ever written, but it's the first I've attempted to write for others to use.  So, while it's been working great for me, you've been warned.  I welcome any feedback and suggestions.","install_details":"place VhdlNav.vim in your plugins directory","5":"place VhdlNav.vim in your plugins directory","first_name":"Steven","6":"Steven","last_name":"Milburn","7":"Milburn","releases":[{"0":"1515","vim_version":"6.0","1":"6.0","script_version":"1","2":"1","version_comment":"Initial upload","3":"Initial upload","package":"VhdlNav.vim","4":"VhdlNav.vim","src_id":"5545","5":"5545","creation_date":"1144850666","6":"1144850666"}]},"1514":{"script_id":"1514","0":"1514","script_name":"SwitchExt","1":"SwitchExt","script_type":"utility","2":"utility","summary":"Switch between source and header files","3":"Switch between source and header files","description":"It can switch between your source file (.c\/.cpp files) and the related header file (.h files), to save your time :)","4":"It can switch between your source file (.c\/.cpp files) and the related header file (.h files), to save your time :)","install_details":"put it under your vim plugin directory\r\nset g:switchext_srcext to your source extension, if ommited, it will be \"cpp\"\r\nyou can also map a key to :call SwitchExt() to switch faster.\r\n\r\nhere's a vimrc example:\r\n\r\nlet g:switchext_srcext = \"cpp\"\r\nmap <F3> <ESC>:call SwitchExt()<CR>","5":"put it under your vim plugin directory\r\nset g:switchext_srcext to your source extension, if ommited, it will be \"cpp\"\r\nyou can also map a key to :call SwitchExt() to switch faster.\r\n\r\nhere's a vimrc example:\r\n\r\nlet g:switchext_srcext = \"cpp\"\r\nmap <F3> <ESC>:call SwitchExt()<CR>","first_name":"Yuxuan","6":"Yuxuan","last_name":"Wang","7":"Wang","releases":[{"0":"1514","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"switchext.vim","4":"switchext.vim","src_id":"5543","5":"5543","creation_date":"1144805843","6":"1144805843"}]},"1513":{"script_id":"1513","0":"1513","script_name":"VimVS6","1":"VimVS6","script_type":"utility","2":"utility","summary":"Compile Visual Studio 6 projects and search in MSDN help files using VIM","3":"Compile Visual Studio 6 projects and search in MSDN help files using VIM","description":"This script provides a way to compile and link MS Visual Studio 6 C++       \r\nprojects, jump to compiler errors, start .exe file and look up in MSDN   \r\nhelp files from within VIM.                                              \r\nThere are other projects that try to integrate VIM in Visual Studio.     \r\nVimVS6 does it the other way around and tries to integrate Visual Studio \r\nin VIM ;-)   (don't take this too seriously)                             \r\n                                                                         \r\nVisual Studio can export a make file for nmake (see menu                 \r\nProject -> Export Makefile... in Visual Studio). Nmake is included in    \r\nVisual Studio 6. VimVS6 compiles a Visual Studio 6 project using nmake   \r\nand the exported makefile.                                               \r\n                                                                         \r\nUsage:                                                                   \r\n  <F5>:    make project                                                  \r\n  <S-F5>:  make all                                                      \r\n  <C-F5>:  start .exe file                                               \r\n  <F2>:    search for help in MSDN files for word under cursor           \r\n                                                                         \r\n  Once per VIM session the function VVS_SetEnvironment() must be called  \r\n  to specify paths VimVS6 looks for the project files.                   \r\n  Do   :call VVS_SetEnvironment( 'projectpath', 'projectname' )          \r\n                                                                         \r\n  E.g. :call VVS_SetEnvironment( 'f:\\prog\\GALer', 'GALer' )              \r\n                                                                         \r\n  This call is not needed if only MSDN help search is used.\r\n\r\nFor details on configuration see script header.","4":"This script provides a way to compile and link MS Visual Studio 6 C++       \r\nprojects, jump to compiler errors, start .exe file and look up in MSDN   \r\nhelp files from within VIM.                                              \r\nThere are other projects that try to integrate VIM in Visual Studio.     \r\nVimVS6 does it the other way around and tries to integrate Visual Studio \r\nin VIM ;-)   (don't take this too seriously)                             \r\n                                                                         \r\nVisual Studio can export a make file for nmake (see menu                 \r\nProject -> Export Makefile... in Visual Studio). Nmake is included in    \r\nVisual Studio 6. VimVS6 compiles a Visual Studio 6 project using nmake   \r\nand the exported makefile.                                               \r\n                                                                         \r\nUsage:                                                                   \r\n  <F5>:    make project                                                  \r\n  <S-F5>:  make all                                                      \r\n  <C-F5>:  start .exe file                                               \r\n  <F2>:    search for help in MSDN files for word under cursor           \r\n                                                                         \r\n  Once per VIM session the function VVS_SetEnvironment() must be called  \r\n  to specify paths VimVS6 looks for the project files.                   \r\n  Do   :call VVS_SetEnvironment( 'projectpath', 'projectname' )          \r\n                                                                         \r\n  E.g. :call VVS_SetEnvironment( 'f:\\prog\\GALer', 'GALer' )              \r\n                                                                         \r\n  This call is not needed if only MSDN help search is used.\r\n\r\nFor details on configuration see script header.","install_details":"Copy this script into the plugin directory. To search in MSDN help\r\nfiles the free program keyHH.exe from http:\/\/www.keyworks.net is needed.\r\n","5":"Copy this script into the plugin directory. To search in MSDN help\r\nfiles the free program keyHH.exe from http:\/\/www.keyworks.net is needed.\r\n","first_name":"Christian","6":"Christian","last_name":"Habermann","7":"Habermann","releases":[{"0":"1513","vim_version":"6.0","1":"6.0","script_version":"1.0.1","2":"1.0.1","version_comment":"fixed some typos in the description of the script","3":"fixed some typos in the description of the script","package":"VimVS6.vim","4":"VimVS6.vim","src_id":"7835","5":"7835","creation_date":"1193389528","6":"1193389528"},{"0":"1513","vim_version":"6.0","1":"6.0","script_version":"1.0.0","2":"1.0.0","version_comment":"Initial upload","3":"Initial upload","package":"VimVS6.vim","4":"VimVS6.vim","src_id":"5540","5":"5540","creation_date":"1144754449","6":"1144754449"}]},"1512":{"script_id":"1512","0":"1512","script_name":"screenpaste.vim","1":"screenpaste.vim","script_type":"utility","2":"utility","summary":"pastes current GNU screen buffer in (almost) any mode","3":"pastes current GNU screen buffer in (almost) any mode","description":"Rationale:\r\nThe terminal window manager Screen http:\/\/www.gnu.org\/software\/screen\r\noffers the capability to copy and paste between windows.\r\nIn principle you can just do \"C-a ]\" (default) to paste the current Screen buffer into a vim buffer.\r\nHowever this gives unexpected results when 'paste' is not set or in Vim's command-line.\r\nThis script provides convenience mappings and functions to get correct results.\r\nAs an additional feature the current Screen buffer is available\r\nin any Vim instance, even those \/outside\/ the current screen session.\r\nMany commands are autodetected and the behaviour adapts automatically [:help getcmdtype()].\r\n\r\nMaps:\r\nAssuming the default mapleader \"\\\" and screenpaste's default mappings you can type:\r\n\\p   in Normal mode to put Screen buffer after cursor\r\n\\P   in Normal mode to put Screen buffer before cursor\r\n\\gp in Normal mode to put Screen buffer after cursor and leave cursor after new text\r\n\\gP in Normal mode to put Screen buffer before cursor and leave cursor after new text\r\n\\p   in Visual mode to replace selection with Screen buffer\r\n\\gp in Visual mode to replace selection with Screen buffer and leave cursor after new text\r\n\\p   in Insert and Replace mode to insert Screen buffer\r\n\\p   in Command-line-mode to insert Screen buffer\r\n\r\nCommands:\r\n\r\n:ScreenYank [x]\r\nyanks Screen buffer [into register x]\r\n\r\n:[line]ScreenPut [x]\r\nputs Screen buffer after [line] (default: current line) using register [x]\r\n\r\n:[line]ScreenPut! [x]\r\nputs Screen buffer before [line] (default: current line) using register [x]\r\n\r\n:ScreenCmdlineConf  search | sub | noesc\r\ntells script how to convert Screen buffer in Command-line mode\r\nExamples as typed with default keybindings:\r\n:ScreenCmdlineConf search\r\n:s\/\\p\/repl\/\r\n:ScreenCmdlineConf sub\r\n:s\/pattern\/\\p\/\r\n\r\n:ScreenCmdlineInfo\r\nechoes info on current Command-line mode behaviour\r\n\r\n:ScreenSearch\r\nsets conversion of Screen buffer inserted in cmdline for search use\r\n\r\n:ScreenSub\r\nsets conversion of Screen buffer inserted in cmdline for substitution use\r\n\r\n:ScreenNoEsc\r\nsets end-of-line only conversion for Screen buffer insertion in cmdline\r\n\r\nVimrc Examples:\r\nChange mappings:\r\nNormal and Visual mode:\r\nmap  <Leader>P <Plug>ScreenpastePut\r\nNormal mode (put before cursor):\r\nnmap <Leader>I <Plug>ScreenpastePutBefore\r\nInsert and Command-line mode:\r\nmap! <F7> <Plug>ScreenpastePut\r\nChange cmdline behaviour setting at startup:\r\nlet g:screen_clmode = \"sub\"\r\nSpecify Screen executable (default: 'screen'):\r\nlet g:screen_executable = \"\/usr\/local\/bin\/screen\"\r\nSwitch register used for Screen buffer (default: '\"' for unnamed register):\r\nlet g:screen_register = \"s\"\r\nAutomatically select pasted text in Visual mode:\r\nlet g:screen_visualselect = 1\r\nWait longer for Screen to finish writing its exchange file:\r\nlet g:screen_wait = '500m'\r\n\r\nMercurial repository: https:\/\/bitbucket.org\/blacktrash\/screenpaste","4":"Rationale:\r\nThe terminal window manager Screen http:\/\/www.gnu.org\/software\/screen\r\noffers the capability to copy and paste between windows.\r\nIn principle you can just do \"C-a ]\" (default) to paste the current Screen buffer into a vim buffer.\r\nHowever this gives unexpected results when 'paste' is not set or in Vim's command-line.\r\nThis script provides convenience mappings and functions to get correct results.\r\nAs an additional feature the current Screen buffer is available\r\nin any Vim instance, even those \/outside\/ the current screen session.\r\nMany commands are autodetected and the behaviour adapts automatically [:help getcmdtype()].\r\n\r\nMaps:\r\nAssuming the default mapleader \"\\\" and screenpaste's default mappings you can type:\r\n\\p   in Normal mode to put Screen buffer after cursor\r\n\\P   in Normal mode to put Screen buffer before cursor\r\n\\gp in Normal mode to put Screen buffer after cursor and leave cursor after new text\r\n\\gP in Normal mode to put Screen buffer before cursor and leave cursor after new text\r\n\\p   in Visual mode to replace selection with Screen buffer\r\n\\gp in Visual mode to replace selection with Screen buffer and leave cursor after new text\r\n\\p   in Insert and Replace mode to insert Screen buffer\r\n\\p   in Command-line-mode to insert Screen buffer\r\n\r\nCommands:\r\n\r\n:ScreenYank [x]\r\nyanks Screen buffer [into register x]\r\n\r\n:[line]ScreenPut [x]\r\nputs Screen buffer after [line] (default: current line) using register [x]\r\n\r\n:[line]ScreenPut! [x]\r\nputs Screen buffer before [line] (default: current line) using register [x]\r\n\r\n:ScreenCmdlineConf  search | sub | noesc\r\ntells script how to convert Screen buffer in Command-line mode\r\nExamples as typed with default keybindings:\r\n:ScreenCmdlineConf search\r\n:s\/\\p\/repl\/\r\n:ScreenCmdlineConf sub\r\n:s\/pattern\/\\p\/\r\n\r\n:ScreenCmdlineInfo\r\nechoes info on current Command-line mode behaviour\r\n\r\n:ScreenSearch\r\nsets conversion of Screen buffer inserted in cmdline for search use\r\n\r\n:ScreenSub\r\nsets conversion of Screen buffer inserted in cmdline for substitution use\r\n\r\n:ScreenNoEsc\r\nsets end-of-line only conversion for Screen buffer insertion in cmdline\r\n\r\nVimrc Examples:\r\nChange mappings:\r\nNormal and Visual mode:\r\nmap  <Leader>P <Plug>ScreenpastePut\r\nNormal mode (put before cursor):\r\nnmap <Leader>I <Plug>ScreenpastePutBefore\r\nInsert and Command-line mode:\r\nmap! <F7> <Plug>ScreenpastePut\r\nChange cmdline behaviour setting at startup:\r\nlet g:screen_clmode = \"sub\"\r\nSpecify Screen executable (default: 'screen'):\r\nlet g:screen_executable = \"\/usr\/local\/bin\/screen\"\r\nSwitch register used for Screen buffer (default: '\"' for unnamed register):\r\nlet g:screen_register = \"s\"\r\nAutomatically select pasted text in Visual mode:\r\nlet g:screen_visualselect = 1\r\nWait longer for Screen to finish writing its exchange file:\r\nlet g:screen_wait = '500m'\r\n\r\nMercurial repository: https:\/\/bitbucket.org\/blacktrash\/screenpaste","install_details":"Unzip screenpaste.zip into a $VIMRUNTIME directory.","5":"Unzip screenpaste.zip into a $VIMRUNTIME directory.","first_name":"Christian","6":"Christian","last_name":"Ebert","7":"Ebert","releases":[{"0":"1512","vim_version":"7.0","1":"7.0","script_version":"7.0","2":"7.0","version_comment":"Vim7 only version using autoload. New variable screen_wait: how long to wait for Screen to write its exchange file.","3":"Vim7 only version using autoload. New variable screen_wait: how long to wait for Screen to write its exchange file.","package":"screenpaste.zip","4":"screenpaste.zip","src_id":"9502","5":"9502","creation_date":"1226704972","6":"1226704972"},{"0":"1512","vim_version":"6.0","1":"6.0","script_version":"5.92","2":"5.92","version_comment":"temporarily set 'paste' in insert mode","3":"temporarily set 'paste' in insert mode","package":"screenpaste.vim","4":"screenpaste.vim","src_id":"8130","5":"8130","creation_date":"1199608273","6":"1199608273"}]},"1511":{"script_id":"1511","0":"1511","script_name":"manuscript.vim","1":"manuscript.vim","script_type":"indent","2":"indent","summary":"Sets text width and formatting options for manuscript editing","3":"Sets text width and formatting options for manuscript editing","description":"Manuscript format is the page layout in which most editors prefer to receive writers' submittals of text (novels, short stories, etc.) for publication.  This small script sets text to 60 columns\/five character tabs, reasonable defaults for editing a manuscript as plain text.  Printing is set to 12-point Courier.\r\n\r\nIt doesn't do much more than this; page headers and line spacing is _not_ automatically set correctly in printed output.  Nonetheless I have provided it in the hope that someone will find it useful.\r\n\r\nType \":setfiletype manuscript\" from within Vim to run the script.\r\n\r\nUse the following line in your .vimrc file to associate manuscript.vim with the \".manuscript.txt\" file extension:\r\n\r\nau BufNewFile,BufRead *.manuscript.txt setf manuscript\r\n\r\nUse the following six lines in your .vimrc file to add some useful key mappings (_mf, _mF and _MF):\r\n\r\n\" Use _mf to reformat whole document, paragraphs wrapped to 60 columns.\r\nmap _mf :setlocal tw=60 ts=5 sts=5 et sw=5 noai fo+=aw2tq nonu<CR>ggVGgq\r\n\" Use _mF to remove excess linefeeds\/spaces, useful before issuing _MF.\r\nmap _mF :%s\/^[\\n \\t]\\+\/\\r\/<CR>\r\n\" Use _MF to reformat with newlines only at the end of each paragraph.\r\nmap _MF :setlocal tw=99999999 nu<CR>ggVGgq","4":"Manuscript format is the page layout in which most editors prefer to receive writers' submittals of text (novels, short stories, etc.) for publication.  This small script sets text to 60 columns\/five character tabs, reasonable defaults for editing a manuscript as plain text.  Printing is set to 12-point Courier.\r\n\r\nIt doesn't do much more than this; page headers and line spacing is _not_ automatically set correctly in printed output.  Nonetheless I have provided it in the hope that someone will find it useful.\r\n\r\nType \":setfiletype manuscript\" from within Vim to run the script.\r\n\r\nUse the following line in your .vimrc file to associate manuscript.vim with the \".manuscript.txt\" file extension:\r\n\r\nau BufNewFile,BufRead *.manuscript.txt setf manuscript\r\n\r\nUse the following six lines in your .vimrc file to add some useful key mappings (_mf, _mF and _MF):\r\n\r\n\" Use _mf to reformat whole document, paragraphs wrapped to 60 columns.\r\nmap _mf :setlocal tw=60 ts=5 sts=5 et sw=5 noai fo+=aw2tq nonu<CR>ggVGgq\r\n\" Use _mF to remove excess linefeeds\/spaces, useful before issuing _MF.\r\nmap _mF :%s\/^[\\n \\t]\\+\/\\r\/<CR>\r\n\" Use _MF to reformat with newlines only at the end of each paragraph.\r\nmap _MF :setlocal tw=99999999 nu<CR>ggVGgq","install_details":"Save the file manuscript.vim to your ~\/.vim\/indent directory.","5":"Save the file manuscript.vim to your ~\/.vim\/indent directory.","first_name":"Dave","6":"Dave","last_name":"Hodder","7":"Hodder","releases":[{"0":"1511","vim_version":"6.0","1":"6.0","script_version":"0.1.1","2":"0.1.1","version_comment":"Now ensures autoindent is turned off.","3":"Now ensures autoindent is turned off.","package":"manuscript.vim","4":"manuscript.vim","src_id":"6469","5":"6469","creation_date":"1164462412","6":"1164462412"}]},"1510":{"script_id":"1510","0":"1510","script_name":"autohi","1":"autohi","script_type":"utility","2":"utility","summary":"highlights words like eclipse","3":"highlights words like eclipse","description":"This plugin highlights words that do not belong to the language (i.e. have no hilighting themselves).  This way you can instantly see if you have typed the right variable\/package\/class name right.\r\n\r\nI just did this to say: \"Hey look, my vim is as good as your eclipse!\" :)\r\n\r\nThis is my first plugin and also my first submission, so please, bear with me.","4":"This plugin highlights words that do not belong to the language (i.e. have no hilighting themselves).  This way you can instantly see if you have typed the right variable\/package\/class name right.\r\n\r\nI just did this to say: \"Hey look, my vim is as good as your eclipse!\" :)\r\n\r\nThis is my first plugin and also my first submission, so please, bear with me.","install_details":"Put it into your plugin-directory.","5":"Put it into your plugin-directory.","first_name":"Adam","6":"Adam","last_name":"Duck","7":"Duck","releases":[{"0":"1510","vim_version":"6.0","1":"6.0","script_version":"0.2","2":"0.2","version_comment":"New version by Thiago Alves.\r\n\r\n+ new command :AHToggle, :AutoHighlightToggle\r\n- no list in which to turn on AutoHighLight() anymore.\r\n\r\nBugfixes, beautifications.","3":"New version by Thiago Alves.\r\n\r\n+ new command :AHToggle, :AutoHighlightToggle\r\n- no list in which to turn on AutoHighLight() anymore.\r\n\r\nBugfixes, beautifications.","package":"autohi.vim","4":"autohi.vim","src_id":"7619","5":"7619","creation_date":"1188925187","6":"1188925187"},{"0":"1510","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"autohi.vim","4":"autohi.vim","src_id":"5527","5":"5527","creation_date":"1144377208","6":"1144377208"}]},"1509":{"script_id":"1509","0":"1509","script_name":"withdrawn","1":"withdrawn","script_type":"game","2":"game","summary":"-","3":"-","description":"withdrawn","4":"withdrawn","install_details":"don't","5":"don't","first_name":"Charles","6":"Charles","last_name":"Campbell","7":"Campbell","releases":[{"0":"1509","vim_version":"6.0","1":"6.0","script_version":"W","2":"W","version_comment":"withdrawn","3":"withdrawn","package":"Withdrawn.vim","4":"Withdrawn.vim","src_id":"5539","5":"5539","creation_date":"1144737600","6":"1144737600"}]},"1508":{"script_id":"1508","0":"1508","script_name":"XHTML 1.0 Strict vim7 xml data file","1":"XHTML 1.0 Strict vim7 xml data file","script_type":"utility","2":"utility","summary":"vim7 xml data file","3":"vim7 xml data file","description":"This is xml data file for vim7. Not required for regular (X)HTML completion but necessary for mixing (X)HTML with other XML dialects.","4":"This is xml data file for vim7. Not required for regular (X)HTML completion but necessary for mixing (X)HTML with other XML dialects.","install_details":"Put it in: ~\/.vim\/autoload\/xml directory.\r\nHow to load read :help :XMLns","5":"Put it in: ~\/.vim\/autoload\/xml directory.\r\nHow to load read :help :XMLns","first_name":"Mikolaj","6":"Mikolaj","last_name":"Machowski","7":"Machowski","releases":[{"0":"1508","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"xhtml10s.vim","4":"xhtml10s.vim","src_id":"5507","5":"5507","creation_date":"1143858928","6":"1143858928"}]},"1507":{"script_id":"1507","0":"1507","script_name":"TabLineSet.vim","1":"TabLineSet.vim","script_type":"utility","2":"utility","summary":"A Vim7 tabline customization","3":"A Vim7 tabline customization","description":"Screenshot link:  http:\/\/www.geocities.com\/eric_p_arnold\/TabLineSet_eg.html\r\n\r\nSee feedback tip#1239   http:\/\/vim.sourceforge.net\/tips\/tip.php?tip_id=1239\r\n \r\nSynopsis:\r\n\r\n    -   Configurable, intelligent\/dynamic tab field sizing.\r\n\r\n    -   See all buffers loaded in windows in all tabs.\r\n\r\n    -   New colorscheme and general presentation.  The highlighting groups are\r\n        defined at the end of the script.  Tweak as desired.\r\n\r\n    -   The indicator sets are customizable.\r\n        (It will also turn verbose mode off automatically, as needed.)\r\n\r\n        You can add the   g:TabLineSet_.*   vars to your .vimrc, where you can\r\n        customize tab min\/max, etc., and these these indicators:\r\n            modified        : whether any window in the tab needs saving\r\n            windows         : window count in the tab\r\n            buffers_list    : tab label contains comma list of buffers contained\r\n            closers         : add hot spots (\"!\") to the tab for click-to-close\r\n\r\n            These are mostly for development, but might be useful otherwise:\r\n            tabnr           : include the tab number for the selected tab\/window\r\n            winnr           : ... window number\r\n            bufnr           : ... buffer number\r\n            filler_func     : tell it to use   g:TabLineSetFillerFunc   to\r\n                              contain the name of a function to be evaluated\r\n                              at runtime.  It's proof of concept, mostly.\r\n\r\n\r\n    -   You can add these mappings to your .vimrc to control the verbose\r\n        settings on the fly:\r\n\r\n        The first one toggles all indicators off:\r\n\r\n            nmap <Leader>tv :call TabLineSet_verbose_toggle()<CR>\r\n\r\n        The second rotates through a list of option settings which\r\n        configurable\/extensible via g:TabLineSet_verbose_sets.  See below.\r\n\r\n            nmap <Leader>tr :call TabLineSet_verbose_rotate()<CR>\r\n\r\n    -   Additional customization can be done via the filter lists.  These are\r\n        more complex, requiring use of regex's and such, but they allow you to\r\n        make arbitrary changes to the TabLine string at runtime.\r\n\r\n    -   You have the choice of editing stuff in place here, but it might be\r\n        better to copy the vars and highlights of interest into your .vimrc .\r\n        I think I've isolated it all to be easy to cut and paste, maybe.\r\n\r\n    -   Finally, the ultimate customization:  dink around with the script\r\n        yourself :-)\r\n\r\n\r\n","4":"Screenshot link:  http:\/\/www.geocities.com\/eric_p_arnold\/TabLineSet_eg.html\r\n\r\nSee feedback tip#1239   http:\/\/vim.sourceforge.net\/tips\/tip.php?tip_id=1239\r\n \r\nSynopsis:\r\n\r\n    -   Configurable, intelligent\/dynamic tab field sizing.\r\n\r\n    -   See all buffers loaded in windows in all tabs.\r\n\r\n    -   New colorscheme and general presentation.  The highlighting groups are\r\n        defined at the end of the script.  Tweak as desired.\r\n\r\n    -   The indicator sets are customizable.\r\n        (It will also turn verbose mode off automatically, as needed.)\r\n\r\n        You can add the   g:TabLineSet_.*   vars to your .vimrc, where you can\r\n        customize tab min\/max, etc., and these these indicators:\r\n            modified        : whether any window in the tab needs saving\r\n            windows         : window count in the tab\r\n            buffers_list    : tab label contains comma list of buffers contained\r\n            closers         : add hot spots (\"!\") to the tab for click-to-close\r\n\r\n            These are mostly for development, but might be useful otherwise:\r\n            tabnr           : include the tab number for the selected tab\/window\r\n            winnr           : ... window number\r\n            bufnr           : ... buffer number\r\n            filler_func     : tell it to use   g:TabLineSetFillerFunc   to\r\n                              contain the name of a function to be evaluated\r\n                              at runtime.  It's proof of concept, mostly.\r\n\r\n\r\n    -   You can add these mappings to your .vimrc to control the verbose\r\n        settings on the fly:\r\n\r\n        The first one toggles all indicators off:\r\n\r\n            nmap <Leader>tv :call TabLineSet_verbose_toggle()<CR>\r\n\r\n        The second rotates through a list of option settings which\r\n        configurable\/extensible via g:TabLineSet_verbose_sets.  See below.\r\n\r\n            nmap <Leader>tr :call TabLineSet_verbose_rotate()<CR>\r\n\r\n    -   Additional customization can be done via the filter lists.  These are\r\n        more complex, requiring use of regex's and such, but they allow you to\r\n        make arbitrary changes to the TabLine string at runtime.\r\n\r\n    -   You have the choice of editing stuff in place here, but it might be\r\n        better to copy the vars and highlights of interest into your .vimrc .\r\n        I think I've isolated it all to be easy to cut and paste, maybe.\r\n\r\n    -   Finally, the ultimate customization:  dink around with the script\r\n        yourself :-)\r\n\r\n\r\n","install_details":"Put it in the plugin directory.  Tweak it as desired.\r\n\r\n\r\n","5":"Put it in the plugin directory.  Tweak it as desired.\r\n\r\n\r\n","first_name":"Eric","6":"Eric","last_name":"Arnold","7":"Arnold","releases":[{"0":"1507","vim_version":"7.0","1":"7.0","script_version":"2.0.1","2":"2.0.1","version_comment":"- startup bug with Tab.._min undefined\r\n[blah, sorry]","3":"- startup bug with Tab.._min undefined\r\n[blah, sorry]","package":"TabLineSet.vim","4":"TabLineSet.vim","src_id":"5746","5":"5746","creation_date":"1148373626","6":"1148373626"},{"0":"1507","vim_version":"7.0","1":"7.0","script_version":"2.0","2":"2.0","version_comment":"- Heavily restructured for support for gui tabs;\r\nprobably installed some bugs too :-P\r\n- Some speed tweaks\r\n- Added g:TabLineSet_max_cols to enable GUI tab\r\nscrolling\r\n","3":"- Heavily restructured for support for gui tabs;\r\nprobably installed some bugs too :-P\r\n- Some speed tweaks\r\n- Added g:TabLineSet_max_cols to enable GUI tab\r\nscrolling\r\n","package":"TabLineSet.vim","4":"TabLineSet.vim","src_id":"5745","5":"5745","creation_date":"1148367398","6":"1148367398"},{"0":"1507","vim_version":"7.0","1":"7.0","script_version":"1.8.3","2":"1.8.3","version_comment":"- Checks for need to recalc, now ~instant return for page redraws","3":"- Checks for need to recalc, now ~instant return for page redraws","package":"TabLineSet.vim","4":"TabLineSet.vim","src_id":"5714","5":"5714","creation_date":"1147857688","6":"1147857688"},{"0":"1507","vim_version":"7.0","1":"7.0","script_version":"1.8.1.1","2":"1.8.1.1","version_comment":"Added wrap-max-lines increase\/decrease \"buttons\" on tabline.","3":"Added wrap-max-lines increase\/decrease \"buttons\" on tabline.","package":"TabLineSet.vim","4":"TabLineSet.vim","src_id":"5696","5":"5696","creation_date":"1147627938","6":"1147627938"},{"0":"1507","vim_version":"7.0","1":"7.0","script_version":"1.8.1","2":"1.8.1","version_comment":"- Corrected indexing for mousefunc patch","3":"- Corrected indexing for mousefunc patch","package":"TabLineSet.vim","4":"TabLineSet.vim","src_id":"5694","5":"5694","creation_date":"1147622420","6":"1147622420"},{"0":"1507","vim_version":"7.0","1":"7.0","script_version":"1.8","2":"1.8","version_comment":"- Use the tabline wrapping patch if available.\r\n","3":"- Use the tabline wrapping patch if available.\r\n","package":"TabLineSet.vim","4":"TabLineSet.vim","src_id":"5691","5":"5691","creation_date":"1147600283","6":"1147600283"},{"0":"1507","vim_version":"7.0","1":"7.0","script_version":"1.7.1","2":"1.7.1","version_comment":"- Reset highlighting based on synIDattr() and whether some external operation has cleared attributes.","3":"- Reset highlighting based on synIDattr() and whether some external operation has cleared attributes.","package":"TabLineSet.vim","4":"TabLineSet.vim","src_id":"5645","5":"5645","creation_date":"1146906408","6":"1146906408"},{"0":"1507","vim_version":"7.0","1":"7.0","script_version":"1.7","2":"1.7","version_comment":"- Added pre- and post-proc function hooks\r\n","3":"- Added pre- and post-proc function hooks\r\n","package":"TabLineSet.vim","4":"TabLineSet.vim","src_id":"5640","5":"5640","creation_date":"1146701172","6":"1146701172"},{"0":"1507","vim_version":"7.0","1":"7.0","script_version":"1.61","2":"1.61","version_comment":"- [Really, this time]Fixed problem where slow-down occurs when the\r\ntabline function is called for every keystroke.  Use\r\nthe toggle or rotate mappings\/functions to reset the\r\nhighlighting, if something clobbers it.","3":"- [Really, this time]Fixed problem where slow-down occurs when the\r\ntabline function is called for every keystroke.  Use\r\nthe toggle or rotate mappings\/functions to reset the\r\nhighlighting, if something clobbers it.","package":"TabLineSet.vim","4":"TabLineSet.vim","src_id":"5635","5":"5635","creation_date":"1146555377","6":"1146555377"},{"0":"1507","vim_version":"7.0","1":"7.0","script_version":"1.55","2":"1.55","version_comment":"- disable the g:TabLineSetFillerFunc per the performance problem with VIm70d.","3":"- disable the g:TabLineSetFillerFunc per the performance problem with VIm70d.","package":"TabLineSet.vim","4":"TabLineSet.vim","src_id":"5564","5":"5564","creation_date":"1145171259","6":"1145171259"},{"0":"1507","vim_version":"7.0","1":"7.0","script_version":"1.5","2":"1.5","version_comment":"- added filter lists so users can apply multiple regex's to the tabline string from the config vars.\r\n- re-arranged the close button, the window counter,\r\n  and the (tab,win,buf) list","3":"- added filter lists so users can apply multiple regex's to the tabline string from the config vars.\r\n- re-arranged the close button, the window counter,\r\n  and the (tab,win,buf) list","package":"TabLineSet.vim","4":"TabLineSet.vim","src_id":"5531","5":"5531","creation_date":"1144544107","6":"1144544107"},{"0":"1507","vim_version":"7.0","1":"7.0","script_version":"1.4","2":"1.4","version_comment":"- added comma list of buffers contained in tab\r\n- changed toggle and rotate mapping functions to\r\n  handle multiple option sets to switch through\r\n","3":"- added comma list of buffers contained in tab\r\n- changed toggle and rotate mapping functions to\r\n  handle multiple option sets to switch through\r\n","package":"TabLineSet.vim","4":"TabLineSet.vim","src_id":"5511","5":"5511","creation_date":"1144045889","6":"1144045889"},{"0":"1507","vim_version":"7.0","1":"7.0","script_version":"1.3.5","2":"1.3.5","version_comment":"Added an autocommand to address problems of start up highlighting conflicts.","3":"Added an autocommand to address problems of start up highlighting conflicts.","package":"TabLineSet.vim","4":"TabLineSet.vim","src_id":"5510","5":"5510","creation_date":"1143957760","6":"1143957760"},{"0":"1507","vim_version":"7.0","1":"7.0","script_version":"1.3","2":"1.3","version_comment":"\r\n- Added more indicators, and toggle mapping funcs\r\nfor verbose control.\r\n- Changed the name of the script from tabset.vim\r\n- Solidified the non-GUI color scheme.\r\n- Started some hooks to customize slack area. ","3":"\r\n- Added more indicators, and toggle mapping funcs\r\nfor verbose control.\r\n- Changed the name of the script from tabset.vim\r\n- Solidified the non-GUI color scheme.\r\n- Started some hooks to customize slack area. ","package":"TabLineSet.vim","4":"TabLineSet.vim","src_id":"5509","5":"5509","creation_date":"1143939679","6":"1143939679"},{"0":"1507","vim_version":"7.0","1":"7.0","script_version":"1.2","2":"1.2","version_comment":"Fixed some bugs, better width calc., more presentation and highlighting thingies.","3":"Fixed some bugs, better width calc., more presentation and highlighting thingies.","package":"tabset.vim","4":"tabset.vim","src_id":"5506","5":"5506","creation_date":"1143857945","6":"1143857945"},{"0":"1507","vim_version":"7.0","1":"7.0","script_version":"1.1","2":"1.1","version_comment":"Initial upload","3":"Initial upload","package":"tabset.vim","4":"tabset.vim","src_id":"5505","5":"5505","creation_date":"1143838002","6":"1143838002"}]},"1506":{"script_id":"1506","0":"1506","script_name":"LargeFile","1":"LargeFile","script_type":"utility","2":"utility","summary":"Edit large files quickly (keywords: large huge speed)","3":"Edit large files quickly (keywords: large huge speed)","description":"Editing large files can be a time consuming process as Vim is working on a number of things behind the scenes, such as maintaining an undo database, searching for a syntax highlighting synchronization point, etc.  LargeFile.vim is a very small \"plugin\"; mostly, its just an autocmd that disables certain features of vim in the interests of speed.\r\n\r\nThere's an option:  g:LargeFile (by default, its 100).  It describes the minimum size of a file needed for it to be considered as a \"LargeFile\", in megabytes.  You may set that option in your <.vimrc>.\r\n\r\nThe plugin is based on vimtip#611.\r\n\r\n(alpha\/beta version available at http:\/\/www.drchip.org\/astronaut\/vim\/index.html#LARGEFILE)","4":"Editing large files can be a time consuming process as Vim is working on a number of things behind the scenes, such as maintaining an undo database, searching for a syntax highlighting synchronization point, etc.  LargeFile.vim is a very small \"plugin\"; mostly, its just an autocmd that disables certain features of vim in the interests of speed.\r\n\r\nThere's an option:  g:LargeFile (by default, its 100).  It describes the minimum size of a file needed for it to be considered as a \"LargeFile\", in megabytes.  You may set that option in your <.vimrc>.\r\n\r\nThe plugin is based on vimtip#611.\r\n\r\n(alpha\/beta version available at http:\/\/www.drchip.org\/astronaut\/vim\/index.html#LARGEFILE)","install_details":"Edit LargeFile.vba.gz:\r\n\r\n  vim LargeFile.vba.gz\r\n  :so %\r\n\r\n(this presumes that you have gunzip on your command path)","5":"Edit LargeFile.vba.gz:\r\n\r\n  vim LargeFile.vba.gz\r\n  :so %\r\n\r\n(this presumes that you have gunzip on your command path)","first_name":"Charles","6":"Charles","last_name":"Campbell","7":"Campbell","releases":[{"0":"1506","vim_version":"7.3","1":"7.3","script_version":"5","2":"5","version_comment":"Undo for non-large windows retained if possible (ie. using 7.4 with patch 73 or if your vim has(\"persistent_undo\") )","3":"Undo for non-large windows retained if possible (ie. using 7.4 with patch 73 or if your vim has(\"persistent_undo\") )","package":"LargeFile.vba.gz","4":"LargeFile.vba.gz","src_id":"21106","5":"21106","creation_date":"1385414602","6":"1385414602"},{"0":"1506","vim_version":"6.0","1":"6.0","script_version":"4","2":"4","version_comment":":Large[!] turns :LargeFile mode back on (reverses :Unlarge)\r\n","3":":Large[!] turns :LargeFile mode back on (reverses :Unlarge)\r\n","package":"LargeFile.vba.gz","4":"LargeFile.vba.gz","src_id":"9277","5":"9277","creation_date":"1222200513","6":"1222200513"},{"0":"1506","vim_version":"6.0","1":"6.0","script_version":"4","2":"4","version_comment":":Large[!] implemented (:Large! forces large-file mode)","3":":Large[!] implemented (:Large! forces large-file mode)","package":"LargeFile.vba.gz","4":"LargeFile.vba.gz","src_id":"9275","5":"9275","creation_date":"1222174412","6":"1222174412"},{"0":"1506","vim_version":"6.0","1":"6.0","script_version":"3","2":"3","version_comment":":Unlarge command now undoes what LargeFile does\r\nLargeFile uses getfsize() to decide if a file is large; however, that function may return numbers less than -1 for files between 2GB - 4GB.  LargeFile will treat any such file to be a \"large file\".","3":":Unlarge command now undoes what LargeFile does\r\nLargeFile uses getfsize() to decide if a file is large; however, that function may return numbers less than -1 for files between 2GB - 4GB.  LargeFile will treat any such file to be a \"large file\".","package":"LargeFile.vba.gz","4":"LargeFile.vba.gz","src_id":"7163","5":"7163","creation_date":"1179987955","6":"1179987955"},{"0":"1506","vim_version":"6.0","1":"6.0","script_version":"2","2":"2","version_comment":"Now has GetLatestVimScripts support.\r\nBugfix -- the g:LargeFile option now usefully settable from <.vimrc>.\r\n","3":"Now has GetLatestVimScripts support.\r\nBugfix -- the g:LargeFile option now usefully settable from <.vimrc>.\r\n","package":"LargeFile.vim.gz","4":"LargeFile.vim.gz","src_id":"5500","5":"5500","creation_date":"1143718798","6":"1143718798"}]},"1505":{"script_id":"1505","0":"1505","script_name":"jbase.vim","1":"jbase.vim","script_type":"indent","2":"indent","summary":"Indent script for jBASE (Pick) Basic","3":"Indent script for jBASE (Pick) Basic","description":"This is an indenting script for jBC -- the jBASE flavor of Pick Basic.","4":"This is an indenting script for jBC -- the jBASE flavor of Pick Basic.","install_details":"Copy the script file to ~\/.vim\/indent\/jbase.vim or <vimdir>\/indent\/jbase.vim and add these lines to filetype.vim or .vimrc:\r\n\r\n\" jBASE (Pick) Basic\r\nau BufNewFile,BufRead *.b,*\/*BP*\/*              setf jbase","5":"Copy the script file to ~\/.vim\/indent\/jbase.vim or <vimdir>\/indent\/jbase.vim and add these lines to filetype.vim or .vimrc:\r\n\r\n\" jBASE (Pick) Basic\r\nau BufNewFile,BufRead *.b,*\/*BP*\/*              setf jbase","first_name":"Gary","6":"Gary","last_name":"Calvin","7":"Calvin","releases":[{"0":"1505","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"jbase.vim","4":"jbase.vim","src_id":"5490","5":"5490","creation_date":"1143545528","6":"1143545528"}]},"1504":{"script_id":"1504","0":"1504","script_name":"jbase.vim","1":"jbase.vim","script_type":"syntax","2":"syntax","summary":"Syntax highlighting for jBASE (Pick) Basic","3":"Syntax highlighting for jBASE (Pick) Basic","description":"This is a syntax highlighting script for jBC -- the jBASE flavor of Pick Basic. \r\n","4":"This is a syntax highlighting script for jBC -- the jBASE flavor of Pick Basic. \r\n","install_details":"Copy the script file to ~\/.vim\/syntax\/jbase.vim or <vimdir>\/syntax\/jbase.vim and add these lines to filetype.vim or .vimrc:\r\n\r\n\" jBASE (Pick) Basic\r\nau BufNewFile,BufRead *.b,*\/*BP*\/*              setf jbase\r\n","5":"Copy the script file to ~\/.vim\/syntax\/jbase.vim or <vimdir>\/syntax\/jbase.vim and add these lines to filetype.vim or .vimrc:\r\n\r\n\" jBASE (Pick) Basic\r\nau BufNewFile,BufRead *.b,*\/*BP*\/*              setf jbase\r\n","first_name":"Gary","6":"Gary","last_name":"Calvin","7":"Calvin","releases":[{"0":"1504","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"jbase.vim","4":"jbase.vim","src_id":"5489","5":"5489","creation_date":"1143545310","6":"1143545310"}]},"1503":{"script_id":"1503","0":"1503","script_name":"Search unFold","1":"Search unFold","script_type":"utility","2":"utility","summary":"Fold everything except search results","3":"Fold everything except search results","description":"This is mainly used to display log files. The program will unfold all lines except the previous search. Additional search terms can be added and unfolded.\r\n:SFS --- search fold start\r\n:SF   ---- additional fold\r\n:SR   ---- reset\r\n:SC   ---- count number found","4":"This is mainly used to display log files. The program will unfold all lines except the previous search. Additional search terms can be added and unfolded.\r\n:SFS --- search fold start\r\n:SF   ---- additional fold\r\n:SR   ---- reset\r\n:SC   ---- count number found","install_details":"place in plugin directory","5":"place in plugin directory","first_name":"Paul","6":"Paul","last_name":"Wei","7":"Wei","releases":[{"0":"1503","vim_version":"6.0","1":"6.0","script_version":"1.1","2":"1.1","version_comment":"Initial upload","3":"Initial upload","package":"sf.vim","4":"sf.vim","src_id":"5483","5":"5483","creation_date":"1143107815","6":"1143107815"}]},"1502":{"script_id":"1502","0":"1502","script_name":"Vimball","1":"Vimball","script_type":"utility","2":"utility","summary":"vim-based archiver: builds, extracts, and previews","3":"vim-based archiver: builds, extracts, and previews","description":"                                            [VIM VERSION 7.1 or 7.2 REQUIRED]\r\n\r\nThe vimball plugin facilitates creating, extracting , and listing the contents of \"vimball\" archives (*.vba).  Vimball also records the files extracted with it and can remove them.\r\n\r\nCREATING A VIMBALL\r\n\r\nVimball can create a \"vimball\" archive (*.vba) with the following command:\r\n\r\n   :[range]MkVimball[!] filename\r\n\r\nAs an example:\r\n\r\n    plugin\/something.vim\r\n    doc\/something.txt\r\n    :%MkVimball something\r\n\r\nwill create a \"vimball.vba\" archive.  Each line in the range processed by the MkVimball command simply describes where in the usual vim directory tree various files are.  I am now also providing a C source program that creates vimballs; see http:\/\/www.drchip.org\/astronaut\/src\/index.html#MKVIMBALL .\r\n \r\nEXTRACTING FROM A VIMBALL\r\n\r\nUsers of a vimball archive simply need to\r\n\r\n    $vim something.vba\r\n    :so %\r\n\r\nand the contents of the vimball will be extracted and placed into the proper directories, no matter where the user opened up the vimball.  Furthermore, the helptags command will be automatically and transparently used to make any doc\/*.txt files' contents available by the Vim help system.\r\n\r\nPREVIEWING A VIMBALL\r\n\r\nInstead of immediately sourcing a vimball to extract its contents, one may use\r\n\r\n    :VimballList\r\n\r\nto preview the contents of the vimball archive.\r\n\r\n(alpha\/beta version available at http:\/\/www.drchip.org\/astronaut\/vim\/index.html#VIMBALL)\r\n","4":"                                            [VIM VERSION 7.1 or 7.2 REQUIRED]\r\n\r\nThe vimball plugin facilitates creating, extracting , and listing the contents of \"vimball\" archives (*.vba).  Vimball also records the files extracted with it and can remove them.\r\n\r\nCREATING A VIMBALL\r\n\r\nVimball can create a \"vimball\" archive (*.vba) with the following command:\r\n\r\n   :[range]MkVimball[!] filename\r\n\r\nAs an example:\r\n\r\n    plugin\/something.vim\r\n    doc\/something.txt\r\n    :%MkVimball something\r\n\r\nwill create a \"vimball.vba\" archive.  Each line in the range processed by the MkVimball command simply describes where in the usual vim directory tree various files are.  I am now also providing a C source program that creates vimballs; see http:\/\/www.drchip.org\/astronaut\/src\/index.html#MKVIMBALL .\r\n \r\nEXTRACTING FROM A VIMBALL\r\n\r\nUsers of a vimball archive simply need to\r\n\r\n    $vim something.vba\r\n    :so %\r\n\r\nand the contents of the vimball will be extracted and placed into the proper directories, no matter where the user opened up the vimball.  Furthermore, the helptags command will be automatically and transparently used to make any doc\/*.txt files' contents available by the Vim help system.\r\n\r\nPREVIEWING A VIMBALL\r\n\r\nInstead of immediately sourcing a vimball to extract its contents, one may use\r\n\r\n    :VimballList\r\n\r\nto preview the contents of the vimball archive.\r\n\r\n(alpha\/beta version available at http:\/\/www.drchip.org\/astronaut\/vim\/index.html#VIMBALL)\r\n","install_details":"For vim 7.0, otherwise skip to step 2:\r\n1. Remove all vestiges of any older version of vimball.  Typically, that means:\r\n    cd \/usr\/local\/share\/vim\/vim70\r\n    rm plugin\/vimball*.vim\r\n    rm autoload\/vimball*.vim\r\n\r\n   Under Windows, the vim70 install point may vary.\r\n\r\n2. I've decided that the vimball plugin itself should not expect that vimball is available to extract it.\r\n    Hence, it is now being distributed as vimball.tar.gz.  To unravel that:\r\n   * change directory to the directory holding the plugin\/ and autoload\/ directories where you want to install vimball.\r\n      It is probably best to install the new vimball in the distribution directory.\r\n   * gunzip vimball.tar.gz\r\n   * tar -oxvf vimball.tar\r\n   * (unix) chmod a+r autoload\/vimball.vim doc\/pi_vimball.txt plugin\/vimballPlugin.vim\r\n\r\nVersion 26 and later use fnameescape() for security reasons -- which in turn requires vim 7.1 with patch 299.","5":"For vim 7.0, otherwise skip to step 2:\r\n1. Remove all vestiges of any older version of vimball.  Typically, that means:\r\n    cd \/usr\/local\/share\/vim\/vim70\r\n    rm plugin\/vimball*.vim\r\n    rm autoload\/vimball*.vim\r\n\r\n   Under Windows, the vim70 install point may vary.\r\n\r\n2. I've decided that the vimball plugin itself should not expect that vimball is available to extract it.\r\n    Hence, it is now being distributed as vimball.tar.gz.  To unravel that:\r\n   * change directory to the directory holding the plugin\/ and autoload\/ directories where you want to install vimball.\r\n      It is probably best to install the new vimball in the distribution directory.\r\n   * gunzip vimball.tar.gz\r\n   * tar -oxvf vimball.tar\r\n   * (unix) chmod a+r autoload\/vimball.vim doc\/pi_vimball.txt plugin\/vimballPlugin.vim\r\n\r\nVersion 26 and later use fnameescape() for security reasons -- which in turn requires vim 7.1 with patch 299.","first_name":"Charles","6":"Charles","last_name":"Campbell","7":"Campbell","releases":[{"0":"1502","vim_version":"7.3","1":"7.3","script_version":"33","2":"33","version_comment":"Added support for xz compression.  Supports *.vmb as well as *.vba for extraction; creates *.vmb files.  Bugfixes: zero-length file handling, a problem with fenc.\r\n","3":"Added support for xz compression.  Supports *.vmb as well as *.vba for extraction; creates *.vmb files.  Bugfixes: zero-length file handling, a problem with fenc.\r\n","package":"vimball.tar.gz","4":"vimball.tar.gz","src_id":"15362","5":"15362","creation_date":"1301781076","6":"1301781076"},{"0":"1502","vim_version":"7.0","1":"7.0","script_version":"30","2":"30","version_comment":"RmVimball supports filenames that would otherwise be considered to have \"magic\" characters (ie. Abc[1].vba)\r\nMkVimball allows slashes in the filename\r\n","3":"RmVimball supports filenames that would otherwise be considered to have \"magic\" characters (ie. Abc[1].vba)\r\nMkVimball allows slashes in the filename\r\n","package":"vimball.tar.gz","4":"vimball.tar.gz","src_id":"11981","5":"11981","creation_date":"1262102631","6":"1262102631"},{"0":"1502","vim_version":"7.0","1":"7.0","script_version":"26","2":"26","version_comment":"For those users who don't yet have any plugins, vimball will now create a .vim (vimfiles) directory as necessary.\r\nBugfix: (tnx Bill McCarthy) vimball wasn't updating files plugin\/ to AsNeeded\/ properly\r\n","3":"For those users who don't yet have any plugins, vimball will now create a .vim (vimfiles) directory as necessary.\r\nBugfix: (tnx Bill McCarthy) vimball wasn't updating files plugin\/ to AsNeeded\/ properly\r\n","package":"vimball.tar.gz","4":"vimball.tar.gz","src_id":"8743","5":"8743","creation_date":"1212137429","6":"1212137429"},{"0":"1502","vim_version":"7.0","1":"7.0","script_version":"25","2":"25","version_comment":"* changed vimball#Vimball() to recognize doc\/*.??x as help files, too.\r\n* g:vimball_path_escape used by s:Path() to prevent certain characters from causing trouble\r\n","3":"* changed vimball#Vimball() to recognize doc\/*.??x as help files, too.\r\n* g:vimball_path_escape used by s:Path() to prevent certain characters from causing trouble\r\n","package":"vimball.tar.gz","4":"vimball.tar.gz","src_id":"8515","5":"8515","creation_date":"1207048495","6":"1207048495"},{"0":"1502","vim_version":"7.0","1":"7.0","script_version":"22","2":"22","version_comment":"uses setlocal instead of set during BufEnter","3":"uses setlocal instead of set during BufEnter","package":"vimball.tar.gz","4":"vimball.tar.gz","src_id":"7078","5":"7078","creation_date":"1178622020","6":"1178622020"},{"0":"1502","vim_version":"7.0","1":"7.0","script_version":"21","2":"21","version_comment":"bugfix release","3":"bugfix release","package":"vimball.tar.gz","4":"vimball.tar.gz","src_id":"6578","5":"6578","creation_date":"1167806544","6":"1167806544"},{"0":"1502","vim_version":"7.0","1":"7.0","script_version":"18","2":"18","version_comment":"Vimballs now use folding to more easily display their contents when opened.\r\nWindows: \\s are changed to \/s (bugfix)","3":"Vimballs now use folding to more easily display their contents when opened.\r\nWindows: \\s are changed to \/s (bugfix)","package":"vimball.tar.gz","4":"vimball.tar.gz","src_id":"6120","5":"6120","creation_date":"1157015359","6":"1157015359"},{"0":"1502","vim_version":"7.0","1":"7.0","script_version":"16","2":"16","version_comment":"* RmVimball implemented - allows one to remove files installed via a vimball\r\n* A. Mechylynk's idea to allow users to specify installation root paths implemented for UseVimball, MkVimball, and RmVimball (optional path argument)\r\n* (sssh -- bugfixes, too)\r\n","3":"* RmVimball implemented - allows one to remove files installed via a vimball\r\n* A. Mechylynk's idea to allow users to specify installation root paths implemented for UseVimball, MkVimball, and RmVimball (optional path argument)\r\n* (sssh -- bugfixes, too)\r\n","package":"vimball.vba.gz","4":"vimball.vba.gz","src_id":"5883","5":"5883","creation_date":"1151392198","6":"1151392198"},{"0":"1502","vim_version":"7.0","1":"7.0","script_version":"15","2":"15","version_comment":"bugfixes!","3":"bugfixes!","package":"vimball.tar.gz","4":"vimball.tar.gz","src_id":"5828","5":"5828","creation_date":"1150189674","6":"1150189674"},{"0":"1502","vim_version":"7.0","1":"7.0","script_version":"14","2":"14","version_comment":"Bugfix release:\r\n* exists(\"&acd\") used to determine if the acd option exists\r\n* the |'acd'| option is not always defined\r\n* VimballList would create missing subdirectories that the vimball specified were needed.  Fixed.\r\n* moved all setting saving\/restoration to a pair of functions.  Included some more settings in them which frequently cause trouble.\r\n* various changes to support the Windows prediliction for backslashes and spaces in file and directory names.\r\n","3":"Bugfix release:\r\n* exists(\"&acd\") used to determine if the acd option exists\r\n* the |'acd'| option is not always defined\r\n* VimballList would create missing subdirectories that the vimball specified were needed.  Fixed.\r\n* moved all setting saving\/restoration to a pair of functions.  Included some more settings in them which frequently cause trouble.\r\n* various changes to support the Windows prediliction for backslashes and spaces in file and directory names.\r\n","package":"vimball.vba.gz","4":"vimball.vba.gz","src_id":"5771","5":"5771","creation_date":"1148628391","6":"1148628391"}]},"1501":{"script_id":"1501","0":"1501","script_name":"slr.vim","1":"slr.vim","script_type":"utility","2":"utility","summary":"Statusline\/Ruler rotation","3":"Statusline\/Ruler rotation","description":"This script simply rotates around a preconfigured set of statusline\/ruler formats. Some times depending on the type of editing being done it is useful to have different status lines.\r\n\r\nSee the comments in the file to see how to setup the status lines. Two status lines are already provided. Can configure in the script or in the .vimrc file.\r\n\r\n<Leader>r is the default mapping to effect a single rotation. To cycle through all statuslines\/rulers keep using <Leader>r.","4":"This script simply rotates around a preconfigured set of statusline\/ruler formats. Some times depending on the type of editing being done it is useful to have different status lines.\r\n\r\nSee the comments in the file to see how to setup the status lines. Two status lines are already provided. Can configure in the script or in the .vimrc file.\r\n\r\n<Leader>r is the default mapping to effect a single rotation. To cycle through all statuslines\/rulers keep using <Leader>r.","install_details":"Drop it in to the plug in directory or source the file.","5":"Drop it in to the plug in directory or source the file.","first_name":"Mike","6":"Mike","last_name":"Sharpe","7":"Sharpe","releases":[{"0":"1501","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"slr.vim","4":"slr.vim","src_id":"5458","5":"5458","creation_date":"1142772013","6":"1142772013"}]},"1500":{"script_id":"1500","0":"1500","script_name":"delins.vim","1":"delins.vim","script_type":"utility","2":"utility","summary":"easy marking of corrections in a document","3":"easy marking of corrections in a document","description":"This script I use for marking changes in text files with the html ins and del tags.\r\n\r\nTo mark something something to insert past the current char press <F5> in normal mode.  \"<ins><\/ins>\" appears. The caret is where you would expect it in insert mode.\r\n\r\nTo mark something to be deleted mark it in visual mode and press\r\nD.  \"<del>...<\/del>\" appears around it.\r\n\r\nFor convenience R (replace) in visual mode is bound to D<F5>.","4":"This script I use for marking changes in text files with the html ins and del tags.\r\n\r\nTo mark something something to insert past the current char press <F5> in normal mode.  \"<ins><\/ins>\" appears. The caret is where you would expect it in insert mode.\r\n\r\nTo mark something to be deleted mark it in visual mode and press\r\nD.  \"<del>...<\/del>\" appears around it.\r\n\r\nFor convenience R (replace) in visual mode is bound to D<F5>.","install_details":"simply source it, when you need it. \r\nor do an :au binding","5":"simply source it, when you need it. \r\nor do an :au binding","first_name":"Mirko","6":"Mirko","last_name":"Scholz","7":"Scholz","releases":[{"0":"1500","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"delins.vim","4":"delins.vim","src_id":"5456","5":"5456","creation_date":"1142645981","6":"1142645981"}]},"1499":{"script_id":"1499","0":"1499","script_name":"rfc2html","1":"rfc2html","script_type":"utility","2":"utility","summary":"Convert a RFC into HTML easy to browse","3":"Convert a RFC into HTML easy to browse","description":"This little script makes a HTML file from a RFC (request for comment)\r\ntext file from IETF.org.\r\n\r\nThe TOC is converted into a navigation-frame and anchors inserted everywhere in the document.\r\n\r\nSome visual improvement are done : bold title, rulers between pages, etc.","4":"This little script makes a HTML file from a RFC (request for comment)\r\ntext file from IETF.org.\r\n\r\nThe TOC is converted into a navigation-frame and anchors inserted everywhere in the document.\r\n\r\nSome visual improvement are done : bold title, rulers between pages, etc.","install_details":"1. Open the RFC .txt file you want to convert\r\n\r\n2. Type:\r\n:source rfc2html.vim    (with the right path where you put the script)\r\n\r\n3. Three files have been generated: index.html and its two frames: toc.html and content.html.\r\n","5":"1. Open the RFC .txt file you want to convert\r\n\r\n2. Type:\r\n:source rfc2html.vim    (with the right path where you put the script)\r\n\r\n3. Three files have been generated: index.html and its two frames: toc.html and content.html.\r\n","first_name":"Samuel","6":"Samuel","last_name":"Hangou\u00c3\u00abt","7":"Hangou\u00c3\u00abt","releases":[{"0":"1499","vim_version":"6.0","1":"6.0","script_version":"1.4","2":"1.4","version_comment":"Make TOC acceptable format less strict (now works on rfc2068)\r\nUnix LF only.","3":"Make TOC acceptable format less strict (now works on rfc2068)\r\nUnix LF only.","package":"rfc2html.vim","4":"rfc2html.vim","src_id":"5831","5":"5831","creation_date":"1150246395","6":"1150246395"},{"0":"1499","vim_version":"6.0","1":"6.0","script_version":"1.3","2":"1.3","version_comment":"This new version uses a navigation frame for the table of content.","3":"This new version uses a navigation frame for the table of content.","package":"rfc2html.vim","4":"rfc2html.vim","src_id":"5471","5":"5471","creation_date":"1142904959","6":"1142904959"},{"0":"1499","vim_version":"6.0","1":"6.0","script_version":"1.1","2":"1.1","version_comment":"Script more powerfull and more selective: accept differents kinds of TOC, manage multi-line TOC items, do not put false links inside the text.\r\nAnchors for pages are also generated (not use for the moment).","3":"Script more powerfull and more selective: accept differents kinds of TOC, manage multi-line TOC items, do not put false links inside the text.\r\nAnchors for pages are also generated (not use for the moment).","package":"rfc2html.vim","4":"rfc2html.vim","src_id":"5453","5":"5453","creation_date":"1142573052","6":"1142573052"},{"0":"1499","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"rfc2html.vim","4":"rfc2html.vim","src_id":"5448","5":"5448","creation_date":"1142562829","6":"1142562829"}]},"1498":{"script_id":"1498","0":"1498","script_name":"all colors pack","1":"all colors pack","script_type":"color scheme","2":"color scheme","summary":"all colors pack 1.0 There are 223 of them included","3":"all colors pack 1.0 There are 223 of them included","description":"This package is simply to help people who want to look at alot of color schemes.  It is all the color schemes on vim.sf.net as of March 13th, 2006 -- zipped up in a single package.  There are 223 of them included.  Every single theme was updated to its newest revision. \r\n","4":"This package is simply to help people who want to look at alot of color schemes.  It is all the color schemes on vim.sf.net as of March 13th, 2006 -- zipped up in a single package.  There are 223 of them included.  Every single theme was updated to its newest revision. \r\n","install_details":"Simply unzip, and place the files in ~\/.vim\/plugin and ~\/.vim\/colors --- it will unzip with correct dir structure, so you can just unzip to ~\/.vim \r\n<F12> is change next color.","5":"Simply unzip, and place the files in ~\/.vim\/plugin and ~\/.vim\/colors --- it will unzip with correct dir structure, so you can just unzip to ~\/.vim \r\n<F12> is change next color.","first_name":"li","6":"li","last_name":"li","7":"li","releases":[{"0":"1498","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"There are 223 of them included","3":"There are 223 of them included","package":"all_colors.rar","4":"all_colors.rar","src_id":"5447","5":"5447","creation_date":"1142558672","6":"1142558672"}]},"1497":{"script_id":"1497","0":"1497","script_name":"Align.vim","1":"Align.vim","script_type":"utility","2":"utility","summary":"Map keys ')' and ']' to perform automatic formatting of parentheses content","3":"Map keys ')' and ']' to perform automatic formatting of parentheses content","description":"  Map keys ')' and ']' to perform automatic formatting of parentheses content, i. e., insert spaces in all proper positions.\r\n   Currently spaces are inserted:\r\n   a)After and before '(', ')', '[', ']', '+', '-', '*', '\/', '%', '=', '&', '|', '^'\r\n   b)After and before '==', '+=', '-=', '*=', '%=', '\/=', '|=', '&=', '!=','^=', '<<', '>>', '>=', '<=', '&&', '||' (and never in the middle!)\r\n   c)Only after (and not before) ',', '++', '--'\r\n\r\n   If syntax highlighting is enabled, script correctly handles string literals, i.e, do not change their content.\r\n\r\n   If you have nested parentheses, their content will not be formatted. It is implied that the source is edited continuously, so content of each pair of pare\r\n   ntheses is formatted after closing parenthesis is printed.\r\n\r\n   Bugs:\r\n   a) Unary '*', '&' and '-' are not handled correctly(i. e., spaces are inserted before and after no matter of context)\r\n   b) Final position of cursor is not always proper\r\n","4":"  Map keys ')' and ']' to perform automatic formatting of parentheses content, i. e., insert spaces in all proper positions.\r\n   Currently spaces are inserted:\r\n   a)After and before '(', ')', '[', ']', '+', '-', '*', '\/', '%', '=', '&', '|', '^'\r\n   b)After and before '==', '+=', '-=', '*=', '%=', '\/=', '|=', '&=', '!=','^=', '<<', '>>', '>=', '<=', '&&', '||' (and never in the middle!)\r\n   c)Only after (and not before) ',', '++', '--'\r\n\r\n   If syntax highlighting is enabled, script correctly handles string literals, i.e, do not change their content.\r\n\r\n   If you have nested parentheses, their content will not be formatted. It is implied that the source is edited continuously, so content of each pair of pare\r\n   ntheses is formatted after closing parenthesis is printed.\r\n\r\n   Bugs:\r\n   a) Unary '*', '&' and '-' are not handled correctly(i. e., spaces are inserted before and after no matter of context)\r\n   b) Final position of cursor is not always proper\r\n","install_details":"Copy file into $VIMRUNTIME\/plugin directory","5":"Copy file into $VIMRUNTIME\/plugin directory","first_name":"Michael","6":"Michael","last_name":"Schwarz","7":"Schwarz","releases":[{"0":"1497","vim_version":"6.0","1":"6.0","script_version":"0.15","2":"0.15","version_comment":"Fixed a bug caused script do not work in 6.4 version of Vim.\r\n\r\nNow works on versions 6.4 -- 7.0a (others have not been tested yet)","3":"Fixed a bug caused script do not work in 6.4 version of Vim.\r\n\r\nNow works on versions 6.4 -- 7.0a (others have not been tested yet)","package":"Align.vim","4":"Align.vim","src_id":"5451","5":"5451","creation_date":"1142567584","6":"1142567584"}]},"1496":{"script_id":"1496","0":"1496","script_name":"initng","1":"initng","script_type":"syntax","2":"syntax","summary":"syntax for initng","3":"syntax for initng","description":"syntax hiliting of *.i and *.ii files of initng init scripts. Inherits from sh.vim and adds\r\nin the hiliting to start\/stop {} blocks. Requires Vim 6.3 or later.\r\n\r\nhttp:\/\/www.initng.org\/\r\n\r\nthis script is also available at http:\/\/glen.alkohol.ee\/pld\/initng\/vim\/","4":"syntax hiliting of *.i and *.ii files of initng init scripts. Inherits from sh.vim and adds\r\nin the hiliting to start\/stop {} blocks. Requires Vim 6.3 or later.\r\n\r\nhttp:\/\/www.initng.org\/\r\n\r\nthis script is also available at http:\/\/glen.alkohol.ee\/pld\/initng\/vim\/","install_details":"http:\/\/glen.alkohol.ee\/pld\/initng\/vim\/README","5":"http:\/\/glen.alkohol.ee\/pld\/initng\/vim\/README","first_name":"Elan","6":"Elan","last_name":"Ruusam\u00c3\u00a4e","7":"Ruusam\u00c3\u00a4e","releases":[{"0":"1496","vim_version":"6.0","1":"6.0","script_version":"0.14","2":"0.14","version_comment":"latest version, includes my and initng svn changes","3":"latest version, includes my and initng svn changes","package":"syntax.vim","4":"syntax.vim","src_id":"8769","5":"8769","creation_date":"1212895685","6":"1212895685"},{"0":"1496","vim_version":"6.0","1":"6.0","script_version":"0.12","2":"0.12","version_comment":"Initial upload","3":"Initial upload","package":"syntax.vim","4":"syntax.vim","src_id":"5437","5":"5437","creation_date":"1142349025","6":"1142349025"}]},"1495":{"script_id":"1495","0":"1495","script_name":"derefined","1":"derefined","script_type":"color scheme","2":"color scheme","summary":"A simplistic blue Color Scheme tailored for the 16-color Terminal","3":"A simplistic blue Color Scheme tailored for the 16-color Terminal","description":"A color scheme. Derefined.\r\nKind of like Torte or Astronaut. But different.\r\nThe colors are the same for the gui and the terminal.\r\n\r\nScreenshot: http:\/\/www.upimages.net\/upload\/49c1ea3b.gif\r\n\r\nSend me what's on the top of your mind:  axs221@gmail.com","4":"A color scheme. Derefined.\r\nKind of like Torte or Astronaut. But different.\r\nThe colors are the same for the gui and the terminal.\r\n\r\nScreenshot: http:\/\/www.upimages.net\/upload\/49c1ea3b.gif\r\n\r\nSend me what's on the top of your mind:  axs221@gmail.com","install_details":"","5":"","first_name":"Shawn","6":"Shawn","last_name":"Axsom","7":"Axsom","releases":[{"0":"1495","vim_version":"6.0","1":"6.0","script_version":"1.1b","2":"1.1b","version_comment":"Changed the StatusLine and Folded colors to black.","3":"Changed the StatusLine and Folded colors to black.","package":"derefined.vim","4":"derefined.vim","src_id":"5460","5":"5460","creation_date":"1142782244","6":"1142782244"},{"0":"1495","vim_version":"6.0","1":"6.0","script_version":"1.1","2":"1.1","version_comment":"Major change of background to darkcyan and made a few color changes to support it.","3":"Major change of background to darkcyan and made a few color changes to support it.","package":"derefined.vim","4":"derefined.vim","src_id":"5445","5":"5445","creation_date":"1142517500","6":"1142517500"},{"0":"1495","vim_version":"6.0","1":"6.0","script_version":"1.0b","2":"1.0b","version_comment":"Removed background from Conditionals & Repeats and changed Comment background to Blue. Changed LineNr FG to Cyan to be more readable.","3":"Removed background from Conditionals & Repeats and changed Comment background to Blue. Changed LineNr FG to Cyan to be more readable.","package":"derefined.vim","4":"derefined.vim","src_id":"5434","5":"5434","creation_date":"1142338241","6":"1142338241"},{"0":"1495","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"derefined.vim","4":"derefined.vim","src_id":"5431","5":"5431","creation_date":"1142333594","6":"1142333594"}]},"1494":{"script_id":"1494","0":"1494","script_name":"Efficient python folding","1":"Efficient python folding","script_type":"ftplugin","2":"ftplugin","summary":"Fold python code nicely and toggle with one keystroke","3":"Fold python code nicely and toggle with one keystroke","description":"Folding goes like this:\r\n\r\n1. Only top level class or function definitions are folded (no nesting)\r\n2. Folding is done one line after the class or function definition, so\r\n    for example the line 'class foo( bar )' is right above the fold\r\n3. Fold text is the first line of the corresponding docstring (if any)\r\n    together with the number of folded lines\r\n4. Toggle all folds on\/off with the key F\r\n5. Toggle the fold under the cursor on\/off with the key f\r\n6. In some rare cases folding can break down which can be fixed by :call ReFold()\r\n    The reason for this break down is not known sometimes it happens when jumping\r\n    between different files using tags.\r\n\r\nIn addition the script binds the key <Shift-e> (hint: _e_xecute) to saving the file and executing it in the interpreter assuming that \/usr\/bin\/env exists otherwise you need to change this key mapping slightly. The keys 'gd' (hint: _g_o _d_efinition) are also bound to look for the definition of a function under the cursor similarly to the same key binding for C.\r\n\r\nInspired by vimscript #515, actually the way the number of lines are displayed is stolen from there :). A related script is vimscript #781 and a tip on toggling a fold is vimtip #108.\r\n\r\nThe content of the script is this, in case you find it more convenient to copy\/paste it than downloading:\r\n\r\n\" Only do this when not done yet for this buffer\r\nif exists(\"b:did_ftplugin\")\r\nfinish\r\nendif\r\nlet b:did_ftplugin = 1\r\n\r\nmap <buffer> <S-e> :w<CR>:!\/usr\/bin\/env python % <CR>\r\nmap <buffer> gd \/def <C-R><C-W><CR> \r\n\r\nset foldmethod=expr\r\nset foldexpr=PythonFoldExpr(v:lnum)\r\nset foldtext=PythonFoldText()\r\n\r\nmap <buffer> f za\r\nmap <buffer> F :call ToggleFold()<CR>\r\nlet b:folded = 1\r\n\r\nfunction! ToggleFold()\r\n    if( b:folded == 0 )\r\n        exec \"normal! zM\"\r\n        let b:folded = 1\r\n    else\r\n        exec \"normal! zR\"\r\n        let b:folded = 0\r\n    endif\r\nendfunction\r\n\r\nfunction! PythonFoldText()\r\n    let size = 1 + v:foldend - v:foldstart\r\n    if size < 10\r\n        let size = \" \" . size\r\n    endif\r\n    if size < 100\r\n        let size = \" \" . size\r\n    endif\r\n    if size < 1000\r\n        let size = \" \" . size\r\n    endif\r\n    \r\n    if match(getline(v:foldstart), '\"\"\"') >= 0\r\n        let text = substitute(getline(v:foldstart), '\"\"\"', '', 'g' ) . ' '\r\n    elseif match(getline(v:foldstart), \"'''\") >= 0\r\n        let text = substitute(getline(v:foldstart), \"'''\", '', 'g' ) . ' '\r\n    else\r\n        let text = getline(v:foldstart)\r\n    endif\r\n    \r\n    return size . ' lines:'. text . ' '\r\nendfunction\r\n\r\nfunction! PythonFoldExpr(lnum)\r\n    if indent( nextnonblank(a:lnum) ) == 0\r\n        return 0\r\n    endif\r\n    \r\n    if getline(a:lnum-1) =~ '^\\(class\\|def\\)\\s'\r\n        return 1\r\n    endif\r\n        \r\n    if getline(a:lnum) =~ '^\\s*$'\r\n        return \"=\"\r\n    endif\r\n    \r\n    if indent(a:lnum) == 0\r\n        return 0\r\n    endif\r\n\r\n    return '='\r\nendfunction\r\n\r\n\" In case folding breaks down\r\nfunction! ReFold()\r\n    set foldmethod=expr\r\n    set foldexpr=0\r\n    set foldnestmax=1\r\n    set foldmethod=expr\r\n    set foldexpr=PythonFoldExpr(v:lnum)\r\n    set foldtext=PythonFoldText()\r\n    echo \r\nendfunction\r\n\r\n","4":"Folding goes like this:\r\n\r\n1. Only top level class or function definitions are folded (no nesting)\r\n2. Folding is done one line after the class or function definition, so\r\n    for example the line 'class foo( bar )' is right above the fold\r\n3. Fold text is the first line of the corresponding docstring (if any)\r\n    together with the number of folded lines\r\n4. Toggle all folds on\/off with the key F\r\n5. Toggle the fold under the cursor on\/off with the key f\r\n6. In some rare cases folding can break down which can be fixed by :call ReFold()\r\n    The reason for this break down is not known sometimes it happens when jumping\r\n    between different files using tags.\r\n\r\nIn addition the script binds the key <Shift-e> (hint: _e_xecute) to saving the file and executing it in the interpreter assuming that \/usr\/bin\/env exists otherwise you need to change this key mapping slightly. The keys 'gd' (hint: _g_o _d_efinition) are also bound to look for the definition of a function under the cursor similarly to the same key binding for C.\r\n\r\nInspired by vimscript #515, actually the way the number of lines are displayed is stolen from there :). A related script is vimscript #781 and a tip on toggling a fold is vimtip #108.\r\n\r\nThe content of the script is this, in case you find it more convenient to copy\/paste it than downloading:\r\n\r\n\" Only do this when not done yet for this buffer\r\nif exists(\"b:did_ftplugin\")\r\nfinish\r\nendif\r\nlet b:did_ftplugin = 1\r\n\r\nmap <buffer> <S-e> :w<CR>:!\/usr\/bin\/env python % <CR>\r\nmap <buffer> gd \/def <C-R><C-W><CR> \r\n\r\nset foldmethod=expr\r\nset foldexpr=PythonFoldExpr(v:lnum)\r\nset foldtext=PythonFoldText()\r\n\r\nmap <buffer> f za\r\nmap <buffer> F :call ToggleFold()<CR>\r\nlet b:folded = 1\r\n\r\nfunction! ToggleFold()\r\n    if( b:folded == 0 )\r\n        exec \"normal! zM\"\r\n        let b:folded = 1\r\n    else\r\n        exec \"normal! zR\"\r\n        let b:folded = 0\r\n    endif\r\nendfunction\r\n\r\nfunction! PythonFoldText()\r\n    let size = 1 + v:foldend - v:foldstart\r\n    if size < 10\r\n        let size = \" \" . size\r\n    endif\r\n    if size < 100\r\n        let size = \" \" . size\r\n    endif\r\n    if size < 1000\r\n        let size = \" \" . size\r\n    endif\r\n    \r\n    if match(getline(v:foldstart), '\"\"\"') >= 0\r\n        let text = substitute(getline(v:foldstart), '\"\"\"', '', 'g' ) . ' '\r\n    elseif match(getline(v:foldstart), \"'''\") >= 0\r\n        let text = substitute(getline(v:foldstart), \"'''\", '', 'g' ) . ' '\r\n    else\r\n        let text = getline(v:foldstart)\r\n    endif\r\n    \r\n    return size . ' lines:'. text . ' '\r\nendfunction\r\n\r\nfunction! PythonFoldExpr(lnum)\r\n    if indent( nextnonblank(a:lnum) ) == 0\r\n        return 0\r\n    endif\r\n    \r\n    if getline(a:lnum-1) =~ '^\\(class\\|def\\)\\s'\r\n        return 1\r\n    endif\r\n        \r\n    if getline(a:lnum) =~ '^\\s*$'\r\n        return \"=\"\r\n    endif\r\n    \r\n    if indent(a:lnum) == 0\r\n        return 0\r\n    endif\r\n\r\n    return '='\r\nendfunction\r\n\r\n\" In case folding breaks down\r\nfunction! ReFold()\r\n    set foldmethod=expr\r\n    set foldexpr=0\r\n    set foldnestmax=1\r\n    set foldmethod=expr\r\n    set foldexpr=PythonFoldExpr(v:lnum)\r\n    set foldtext=PythonFoldText()\r\n    echo \r\nendfunction\r\n\r\n","install_details":"Drop the file in your .vim\/ftplugin\/ directory (in case you already have a file there called python_editing.vim, don't forget to change the name).","5":"Drop the file in your .vim\/ftplugin\/ directory (in case you already have a file there called python_editing.vim, don't forget to change the name).","first_name":"Daniel","6":"Daniel","last_name":"Nogradi","7":"Nogradi","releases":[{"0":"1494","vim_version":"6.0","1":"6.0","script_version":"1.1","2":"1.1","version_comment":"Recognizes both double quoted (\"\"\") and single quoted (''') docstrings.\r\nAdded a function to fix folding if it breaks down for some reason.","3":"Recognizes both double quoted (\"\"\") and single quoted (''') docstrings.\r\nAdded a function to fix folding if it breaks down for some reason.","package":"python_editing.vim","4":"python_editing.vim","src_id":"5492","5":"5492","creation_date":"1143559906","6":"1143559906"},{"0":"1494","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"python_editing.vim","4":"python_editing.vim","src_id":"5424","5":"5424","creation_date":"1142274199","6":"1142274199"}]},"1493":{"script_id":"1493","0":"1493","script_name":"Sudoku Solver","1":"Sudoku Solver","script_type":"game","2":"game","summary":"Plugin for solving Sudoku puzzles","3":"Plugin for solving Sudoku puzzles","description":"Sudoku solver plugin\r\n\r\nImportant: Vim 7.0 or later required.\r\n\r\nSudoku is a puzzle where you have to fill all the blank spaces with digits from 1 to 9 such that no row, column, or 3x3 block of cells have any digits repeated. This plugin holds a Vim script that solves Sudoku puzzles by exhaustive search.\r\n\r\nEnter the puzzle into a buffer like this:\r\n\r\n    8xx 69x xx2\r\n    91x xxx xxx\r\n    5xx xx8 xx7\r\n\r\n    xxx 2x9 xx6\r\n    xxx 8xx xx3\r\n    2xx 3x4 xxx\r\n\r\n    3xx 78x xx9\r\n    xxx xxx xx5\r\n    4xx x5x x28\r\n\r\nThe numbers represent supplied digits 1 to 9 in the puzzle. Use any other character to represent blank spaces.\r\n\r\nThen visually select the puzzle and invoke the macro binding ,s\r\n","4":"Sudoku solver plugin\r\n\r\nImportant: Vim 7.0 or later required.\r\n\r\nSudoku is a puzzle where you have to fill all the blank spaces with digits from 1 to 9 such that no row, column, or 3x3 block of cells have any digits repeated. This plugin holds a Vim script that solves Sudoku puzzles by exhaustive search.\r\n\r\nEnter the puzzle into a buffer like this:\r\n\r\n    8xx 69x xx2\r\n    91x xxx xxx\r\n    5xx xx8 xx7\r\n\r\n    xxx 2x9 xx6\r\n    xxx 8xx xx3\r\n    2xx 3x4 xxx\r\n\r\n    3xx 78x xx9\r\n    xxx xxx xx5\r\n    4xx x5x x28\r\n\r\nThe numbers represent supplied digits 1 to 9 in the puzzle. Use any other character to represent blank spaces.\r\n\r\nThen visually select the puzzle and invoke the macro binding ,s\r\n","install_details":"Drop it into the plugin directory.\r\nNote: Vim 7.0 or later required.","5":"Drop it into the plugin directory.\r\nNote: Vim 7.0 or later required.","first_name":"Po Shan","6":"Po Shan","last_name":"Cheah","7":"Cheah","releases":[{"0":"1493","vim_version":"7.0","1":"7.0","script_version":"1.1","2":"1.1","version_comment":"Modified script to display results in a new window split. Improved the status and error messages. Added some checking for obvious problems in the puzzle.","3":"Modified script to display results in a new window split. Improved the status and error messages. Added some checking for obvious problems in the puzzle.","package":"sudoku.vim","4":"sudoku.vim","src_id":"8699","5":"8699","creation_date":"1210935316","6":"1210935316"},{"0":"1493","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"sudoku.vim","4":"sudoku.vim","src_id":"5422","5":"5422","creation_date":"1142259200","6":"1142259200"}]},"1492":{"script_id":"1492","0":"1492","script_name":"pyte","1":"pyte","script_type":"color scheme","2":"color scheme","summary":"A clean, light (nearly white) theme","3":"A clean, light (nearly white) theme","description":"This is a light theme I use for coding.\r\nBackground is very light grey, special things are green or blue, this is for gui only and uses italic for some things (which I find very nice as its makes gvim look less console-like).\r\n\r\nScreenshot: http:\/\/leetless.de\/vim.html","4":"This is a light theme I use for coding.\r\nBackground is very light grey, special things are green or blue, this is for gui only and uses italic for some things (which I find very nice as its makes gvim look less console-like).\r\n\r\nScreenshot: http:\/\/leetless.de\/vim.html","install_details":"Copy this file to your private or public colors-directory.\r\nUnder Linux the following should work: mkdir -p ~\/.vim\/colors; cp pyte.vim ~\/.vim\/colors\r\nIf in doubt use instructions of any other colors-package they should work too, or read\r\nthe vim help about colorscheme-files.\r\n\r\nAs this theme only defined highlight-groups for the vim-gui, you might want to use a different one for textmode.\r\nTo do this, simply put \"colors my_console_scheme\" into your .vimrc-File and \"colors pyte\" ingot your .gvimrc file.","5":"Copy this file to your private or public colors-directory.\r\nUnder Linux the following should work: mkdir -p ~\/.vim\/colors; cp pyte.vim ~\/.vim\/colors\r\nIf in doubt use instructions of any other colors-package they should work too, or read\r\nthe vim help about colorscheme-files.\r\n\r\nAs this theme only defined highlight-groups for the vim-gui, you might want to use a different one for textmode.\r\nTo do this, simply put \"colors my_console_scheme\" into your .vimrc-File and \"colors pyte\" ingot your .gvimrc file.","first_name":"Henning","6":"Henning","last_name":"Hasemann","7":"Hasemann","releases":[{"0":"1492","vim_version":"7.0","1":"7.0","script_version":"1.2.2","2":"1.2.2","version_comment":"Little color fixes","3":"Little color fixes","package":"pyte.vim","4":"pyte.vim","src_id":"13283","5":"13283","creation_date":"1278168306","6":"1278168306"},{"0":"1492","vim_version":"6.0","1":"6.0","script_version":"1.2.1","2":"1.2.1","version_comment":"- Fixed issue with Error-color, if you used cursorline before, errors got white-on white, now foreground color for errors is red which schould cause your attention on every of my defined background colors.","3":"- Fixed issue with Error-color, if you used cursorline before, errors got white-on white, now foreground color for errors is red which schould cause your attention on every of my defined background colors.","package":"pyte.vim","4":"pyte.vim","src_id":"5826","5":"5826","creation_date":"1150164769","6":"1150164769"},{"0":"1492","vim_version":"6.0","1":"6.0","script_version":"1.2","2":"1.2","version_comment":"Added support for some new features in vim:\r\n- CursorLines\r\n- TabLine\r\n- Pmenu (auto-completion)\r\n\r\nNote that this colorscheme does not (and will propably never) *require* VIM v7, as vims-scripting language provides conditionals to query the version.\r\nSo it should look (at your opinion) nice with VIM6 and VIM7 now.","3":"Added support for some new features in vim:\r\n- CursorLines\r\n- TabLine\r\n- Pmenu (auto-completion)\r\n\r\nNote that this colorscheme does not (and will propably never) *require* VIM v7, as vims-scripting language provides conditionals to query the version.\r\nSo it should look (at your opinion) nice with VIM6 and VIM7 now.","package":"pyte.vim","4":"pyte.vim","src_id":"5813","5":"5813","creation_date":"1149744851","6":"1149744851"},{"0":"1492","vim_version":"6.0","1":"6.0","script_version":"1.1","2":"1.1","version_comment":"Defined colors for diff-view (vim -d)","3":"Defined colors for diff-view (vim -d)","package":"pyte.vim","4":"pyte.vim","src_id":"5812","5":"5812","creation_date":"1149741652","6":"1149741652"},{"0":"1492","vim_version":"6.0","1":"6.0","script_version":"1.01","2":"1.01","version_comment":"Made NonText Foreground grey so the \"~\" signs on an empty document dont look that ugly anymore","3":"Made NonText Foreground grey so the \"~\" signs on an empty document dont look that ugly anymore","package":"pyte.vim","4":"pyte.vim","src_id":"5803","5":"5803","creation_date":"1149561309","6":"1149561309"},{"0":"1492","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"pyte.vim","4":"pyte.vim","src_id":"5420","5":"5420","creation_date":"1142155787","6":"1142155787"}]},"1491":{"script_id":"1491","0":"1491","script_name":"JavaScript syntax","1":"JavaScript syntax","script_type":"syntax","2":"syntax","summary":"Better JavaScrirpt syntax support","3":"Better JavaScrirpt syntax support","description":"Hi JavaScript and VIM funs, \r\n\r\nIf you want to use VIM to edit\/view the JavaScript files, you should have this one. \r\nReplace it with the javascript syntax file included with the VIMRUNTIME.\r\n\r\nWhy it is here:\r\nBecause I found that the originaly one which packed with the VIMRUNTIME didn't work very well for the JS files in Mozilla Browser\/SeaMonkey\/Firefox and Dojo. So I decided to some refine on it. \r\n\r\nHope it is also useful for you~~~\r\n\r\nGood Luck,\r\n\r\nYi Zhao (ZHAOYI)\r\nBlog: http:\/\/linuxyz.blogspot.com\/","4":"Hi JavaScript and VIM funs, \r\n\r\nIf you want to use VIM to edit\/view the JavaScript files, you should have this one. \r\nReplace it with the javascript syntax file included with the VIMRUNTIME.\r\n\r\nWhy it is here:\r\nBecause I found that the originaly one which packed with the VIMRUNTIME didn't work very well for the JS files in Mozilla Browser\/SeaMonkey\/Firefox and Dojo. So I decided to some refine on it. \r\n\r\nHope it is also useful for you~~~\r\n\r\nGood Luck,\r\n\r\nYi Zhao (ZHAOYI)\r\nBlog: http:\/\/linuxyz.blogspot.com\/","install_details":"M$ Windows: put at $VIMRUNTIME\/syntax\/javascript.vim\r\nor \r\nUnix: put it at ~\/.vim\/syntax\/javascript.vim ","5":"M$ Windows: put at $VIMRUNTIME\/syntax\/javascript.vim\r\nor \r\nUnix: put it at ~\/.vim\/syntax\/javascript.vim ","first_name":"Yi","6":"Yi","last_name":"Zhao","7":"Zhao","releases":[{"0":"1491","vim_version":"6.0","1":"6.0","script_version":"0.7.7","2":"0.7.7","version_comment":"Add \"undefined\" as a type keyword","3":"Add \"undefined\" as a type keyword","package":"javascript.vim","4":"javascript.vim","src_id":"10728","5":"10728","creation_date":"1244082179","6":"1244082179"},{"0":"1491","vim_version":"6.0","1":"6.0","script_version":"0.7.6","2":"0.7.6","version_comment":"Change the 'syntax sync' method to improve the performance with large JavaScript files.\r\nThe old way 'syntax sync fromstart' is too slow to handle the files greater than 2000 lines. ","3":"Change the 'syntax sync' method to improve the performance with large JavaScript files.\r\nThe old way 'syntax sync fromstart' is too slow to handle the files greater than 2000 lines. ","package":"javascript.vim","4":"javascript.vim","src_id":"9238","5":"9238","creation_date":"1220977906","6":"1220977906"},{"0":"1491","vim_version":"6.0","1":"6.0","script_version":"0.7.5","2":"0.7.5","version_comment":"1, Get the vimdiff problem fixed finally.\r\n  Matthew Gallant reported the problem and test the fix. ;)\r\n\r\n2, Follow the suggestioin from Ingo Karkat.\r\n  The 'foldtext' and 'foldlevel' settings should only be changed if the file being edited is pure JavaScript, not if JavaScript syntax is embedded inside other syntaxes.\r\n\r\n3, Remove function FT_JavaScriptDoc(). Since VIM do the better than me.","3":"1, Get the vimdiff problem fixed finally.\r\n  Matthew Gallant reported the problem and test the fix. ;)\r\n\r\n2, Follow the suggestioin from Ingo Karkat.\r\n  The 'foldtext' and 'foldlevel' settings should only be changed if the file being edited is pure JavaScript, not if JavaScript syntax is embedded inside other syntaxes.\r\n\r\n3, Remove function FT_JavaScriptDoc(). Since VIM do the better than me.","package":"javascript.vim","4":"javascript.vim","src_id":"7129","5":"7129","creation_date":"1179382214","6":"1179382214"},{"0":"1491","vim_version":"6.0","1":"6.0","script_version":"0.7.4","2":"0.7.4","version_comment":"1, Fix a bug reported by Matthew Gallant. \r\n   It will cause the vimdiff (6.x) freezes (chokes, with a 100% cpu usage) and never finally displays the diff between the files. The script need to be finished by press CTRL+C. \r\n\r\n2, Add some more JSDoc tags which used by Yahoo! UI\r\n\r\n","3":"1, Fix a bug reported by Matthew Gallant. \r\n   It will cause the vimdiff (6.x) freezes (chokes, with a 100% cpu usage) and never finally displays the diff between the files. The script need to be finished by press CTRL+C. \r\n\r\n2, Add some more JSDoc tags which used by Yahoo! UI\r\n\r\n","package":"javascript.vim","4":"javascript.vim","src_id":"7108","5":"7108","creation_date":"1179122181","6":"1179122181"},{"0":"1491","vim_version":"6.0","1":"6.0","script_version":"0.7.3","2":"0.7.3","version_comment":"Add the keywords for JavaScript 1.7: let, yield,","3":"Add the keywords for JavaScript 1.7: let, yield,","package":"javascript.vim","4":"javascript.vim","src_id":"6867","5":"6867","creation_date":"1173767056","6":"1173767056"},{"0":"1491","vim_version":"6.0","1":"6.0","script_version":"0.7.2","2":"0.7.2","version_comment":"Turn off the DOM2, HTML, and CSS speicified attributes and methods by default.\r\n\r\nif you like it please add follow code into your .vimrc file.\r\nlet javascript_enable_domhtmlcss=1\r\n\r\nI really hate the inaccuracy syntax highlight.\r\n\r\nThanks,\r\n\r\nZHAOYI  \r\n\r\n\r\n","3":"Turn off the DOM2, HTML, and CSS speicified attributes and methods by default.\r\n\r\nif you like it please add follow code into your .vimrc file.\r\nlet javascript_enable_domhtmlcss=1\r\n\r\nI really hate the inaccuracy syntax highlight.\r\n\r\nThanks,\r\n\r\nZHAOYI  \r\n\r\n\r\n","package":"javascript.vim","4":"javascript.vim","src_id":"6692","5":"6692","creation_date":"1170129489","6":"1170129489"},{"0":"1491","vim_version":"6.0","1":"6.0","script_version":"0.7.1","2":"0.7.1","version_comment":"1, Add DOM2, HTML, and CSS speicified attributes and methods, based on  \r\nhttp:\/\/www.w3.org\/TR\/2000\/REC-DOM-Level-2-Core-20001113\/ecma-script-binding.html\r\n    http:\/\/www.dannyg.com\/ref\/jsquickref.html\r\n    Thanks Claudio Fleiner <claudio@fleiner.com> for the great idea.\r\n2, Minor bug fix for JSDoc.\r\n3, Minor bug fix for comment highlight.\r\n\r\nNOTE:\r\n  The syntax detection for DOM\/HTML\/CSS options are tricky, it can't be handled 100%  \r\n accuracy by using the regex  based highlight system. \r\n  If the DOM\/HTML\/CSS highlight make you unhappy, you can simply add these:\r\n\r\nlet javascript_ignore_domhtmlcss=1\r\n\r\n  into your .vimrc file to prevent the highlight on DOM\/HTML\/CSS functions and attributes. \r\n\r\nThanks,\r\n\r\nYi","3":"1, Add DOM2, HTML, and CSS speicified attributes and methods, based on  \r\nhttp:\/\/www.w3.org\/TR\/2000\/REC-DOM-Level-2-Core-20001113\/ecma-script-binding.html\r\n    http:\/\/www.dannyg.com\/ref\/jsquickref.html\r\n    Thanks Claudio Fleiner <claudio@fleiner.com> for the great idea.\r\n2, Minor bug fix for JSDoc.\r\n3, Minor bug fix for comment highlight.\r\n\r\nNOTE:\r\n  The syntax detection for DOM\/HTML\/CSS options are tricky, it can't be handled 100%  \r\n accuracy by using the regex  based highlight system. \r\n  If the DOM\/HTML\/CSS highlight make you unhappy, you can simply add these:\r\n\r\nlet javascript_ignore_domhtmlcss=1\r\n\r\n  into your .vimrc file to prevent the highlight on DOM\/HTML\/CSS functions and attributes. \r\n\r\nThanks,\r\n\r\nYi","package":"javascript.vim","4":"javascript.vim","src_id":"6583","5":"6583","creation_date":"1168041419","6":"1168041419"},{"0":"1491","vim_version":"6.0","1":"6.0","script_version":"0.7.0","2":"0.7.0","version_comment":"Add all keywords\/exceptions defined in ECMAScript Language Specification Edition 3. ","3":"Add all keywords\/exceptions defined in ECMAScript Language Specification Edition 3. ","package":"javascript.vim","4":"javascript.vim","src_id":"6429","5":"6429","creation_date":"1163724837","6":"1163724837"},{"0":"1491","vim_version":"6.0","1":"6.0","script_version":"0.6.9","2":"0.6.9","version_comment":"1, Fix a bug of javaScriptLineComment which mark the code line which follows the indent empty \/\/ as comment.\r\n2, Modify the javaScriptLinecomment folding mode, line comments only fold start the full line comment.\r\n","3":"1, Fix a bug of javaScriptLineComment which mark the code line which follows the indent empty \/\/ as comment.\r\n2, Modify the javaScriptLinecomment folding mode, line comments only fold start the full line comment.\r\n","package":"javascript.vim","4":"javascript.vim","src_id":"6360","5":"6360","creation_date":"1162358481","6":"1162358481"},{"0":"1491","vim_version":"6.0","1":"6.0","script_version":"0.6.8","2":"0.6.8","version_comment":"Fix the function FT_JavaScriptDoc() redefine warning when switch the buffer in multi-buffer mode.","3":"Fix the function FT_JavaScriptDoc() redefine warning when switch the buffer in multi-buffer mode.","package":"javascript.vim","4":"javascript.vim","src_id":"6349","5":"6349","creation_date":"1162156186","6":"1162156186"},{"0":"1491","vim_version":"6.0","1":"6.0","script_version":"0.6.7","2":"0.6.7","version_comment":"1. JSDoc parameter do recogonize \"#.:\/\" at any position.\r\n2. The \"$\" can appear at any position of the function name.\r\n3. The continous line comments will be folding in fold mode.","3":"1. JSDoc parameter do recogonize \"#.:\/\" at any position.\r\n2. The \"$\" can appear at any position of the function name.\r\n3. The continous line comments will be folding in fold mode.","package":"javascript.vim","4":"javascript.vim","src_id":"6334","5":"6334","creation_date":"1161761848","6":"1161761848"},{"0":"1491","vim_version":"6.0","1":"6.0","script_version":"0.6.6","2":"0.6.6","version_comment":"1. Rename the syntax group name to javaScript* to follow the syntax file recommendation.\r\n2, The unmached \"[]\", \"()\", and \"{}\" can be detected.\r\n3, A minor bug fix for the javaScriptNumber highlight.","3":"1. Rename the syntax group name to javaScript* to follow the syntax file recommendation.\r\n2, The unmached \"[]\", \"()\", and \"{}\" can be detected.\r\n3, A minor bug fix for the javaScriptNumber highlight.","package":"javascript.vim","4":"javascript.vim","src_id":"6317","5":"6317","creation_date":"1161490628","6":"1161490628"},{"0":"1491","vim_version":"6.0","1":"6.0","script_version":"0.6.5","2":"0.6.5","version_comment":"1, Add the highlight for Float number\r\n2, Refine the highlight of Number  \r\n\r\n3, Define the highlight for the JSDoc tags' value. \r\n    e.g. \"@see #see_what\" the #see_what will be highlighted.\r\n\r\n4, Fold support for JavaScript comment and Function's body\r\n    Folding is  intesting. @see http:\/\/vimdoc.sourceforge.net\/htmldoc\/usr_28.html\r\n    By default, the fold is off.\r\n\r\n    In the Normal mode, zM to fold all.\r\n\r\n\r\n","3":"1, Add the highlight for Float number\r\n2, Refine the highlight of Number  \r\n\r\n3, Define the highlight for the JSDoc tags' value. \r\n    e.g. \"@see #see_what\" the #see_what will be highlighted.\r\n\r\n4, Fold support for JavaScript comment and Function's body\r\n    Folding is  intesting. @see http:\/\/vimdoc.sourceforge.net\/htmldoc\/usr_28.html\r\n    By default, the fold is off.\r\n\r\n    In the Normal mode, zM to fold all.\r\n\r\n\r\n","package":"javascript.vim","4":"javascript.vim","src_id":"6312","5":"6312","creation_date":"1161389183","6":"1161389183"},{"0":"1491","vim_version":"6.0","1":"6.0","script_version":"0.6","2":"0.6","version_comment":"Add JSDoc support to the syntax file. The \"@zzzz\" and {@zzz xxxx} will be highlight. \r\n\r\nFor more information about the JSDoc, refer to http:\/\/jsdoc.sf.net ","3":"Add JSDoc support to the syntax file. The \"@zzzz\" and {@zzz xxxx} will be highlight. \r\n\r\nFor more information about the JSDoc, refer to http:\/\/jsdoc.sf.net ","package":"javascript.vim","4":"javascript.vim","src_id":"6292","5":"6292","creation_date":"1161129506","6":"1161129506"},{"0":"1491","vim_version":"6.0","1":"6.0","script_version":"0.5.2","2":"0.5.2","version_comment":"In ECMA-262v3, The dollar sign ($) is permitted anywhere in an identifier. The dollar sign is intended for use only in mechanically generated code.  \r\n\r\nAdd dollar sigh as keyword to avoid irregular highlight against the $break or $continue \r\n\r\nThanks \"Nai chao Wu\" <superwunc AT hotmail.com> for his help.","3":"In ECMA-262v3, The dollar sign ($) is permitted anywhere in an identifier. The dollar sign is intended for use only in mechanically generated code.  \r\n\r\nAdd dollar sigh as keyword to avoid irregular highlight against the $break or $continue \r\n\r\nThanks \"Nai chao Wu\" <superwunc AT hotmail.com> for his help.","package":"javascript.vim","4":"javascript.vim","src_id":"6282","5":"6282","creation_date":"1160797499","6":"1160797499"},{"0":"1491","vim_version":"6.0","1":"6.0","script_version":"0.5.1","2":"0.5.1","version_comment":"Minor upate on the jsRegexpString. ","3":"Minor upate on the jsRegexpString. ","package":"javascript.vim","4":"javascript.vim","src_id":"5908","5":"5908","creation_date":"1151815084","6":"1151815084"},{"0":"1491","vim_version":"6.0","1":"6.0","script_version":"0.5","2":"0.5","version_comment":"1, Provided the htmlJavaScript cluster to HTML syntax (syntax\/html.vim).\r\n2, Try the fold on JavaScript, I found it is really abnormal, and useless for JavaScript. So I just remove the fold from the TODO list.\r\n\r\nAnd there is a syntax highlight problem in html.vim \r\nIf you want to make the JavaScript inside HTML highlight properly, please commented out the follows lines in html.vim.\r\n<pre>\r\n\" HtmlHiLink javaScript\t\t    Special\r\n\" HtmlHiLink javaScriptExpression   javaScript\r\n<\/pre>","3":"1, Provided the htmlJavaScript cluster to HTML syntax (syntax\/html.vim).\r\n2, Try the fold on JavaScript, I found it is really abnormal, and useless for JavaScript. So I just remove the fold from the TODO list.\r\n\r\nAnd there is a syntax highlight problem in html.vim \r\nIf you want to make the JavaScript inside HTML highlight properly, please commented out the follows lines in html.vim.\r\n<pre>\r\n\" HtmlHiLink javaScript\t\t    Special\r\n\" HtmlHiLink javaScriptExpression   javaScript\r\n<\/pre>","package":"javascript.vim","4":"javascript.vim","src_id":"5464","5":"5464","creation_date":"1142834545","6":"1142834545"},{"0":"1491","vim_version":"6.0","1":"6.0","script_version":"0.4.1","2":"0.4.1","version_comment":"Minor fix with jsLabel and jsRegexpString. \r\n\r\nThe dojo.js and dojo.js.uncompressed.js can be highlight properly. ","3":"Minor fix with jsLabel and jsRegexpString. \r\n\r\nThe dojo.js and dojo.js.uncompressed.js can be highlight properly. ","package":"javascript.vim","4":"javascript.vim","src_id":"5457","5":"5457","creation_date":"1142660854","6":"1142660854"},{"0":"1491","vim_version":"6.0","1":"6.0","script_version":"0.4","2":"0.4","version_comment":"1, Update the jsRegexpString, make it work with Dojo JavaScript source. \r\n2, Update the jsSpecial, make it match the oct\/hex\/unicode characters. \r\n\r\nIf you are playing with the regexp string, try this version. :) ","3":"1, Update the jsRegexpString, make it work with Dojo JavaScript source. \r\n2, Update the jsSpecial, make it match the oct\/hex\/unicode characters. \r\n\r\nIf you are playing with the regexp string, try this version. :) ","package":"javascript.vim","4":"javascript.vim","src_id":"5455","5":"5455","creation_date":"1142631492","6":"1142631492"},{"0":"1491","vim_version":"6.0","1":"6.0","script_version":"0.3","2":"0.3","version_comment":"1, Add jsLabel support;\r\n2, Add all JavaScript keywords and Global Objects based on the JavaScript 1.5 reference at http:\/\/developer.mozilla.org\/en\/docs\/Core_JavaScript_1.5_Reference\r\n3, Add jsBlock can be put in jsBracket .","3":"1, Add jsLabel support;\r\n2, Add all JavaScript keywords and Global Objects based on the JavaScript 1.5 reference at http:\/\/developer.mozilla.org\/en\/docs\/Core_JavaScript_1.5_Reference\r\n3, Add jsBlock can be put in jsBracket .","package":"javascript.vim","4":"javascript.vim","src_id":"5418","5":"5418","creation_date":"1142136093","6":"1142136093"},{"0":"1491","vim_version":"6.0","1":"6.0","script_version":"0.2","2":"0.2","version_comment":"Changed the file format to Unix. \r\n\r\nI found that the DOS format file has problems to work under the Unix. \r\nYestorday I didn't test it under the UNIX. \r\n\r\nI am sorry, if it caused some problem. \r\n\r\nThanks,\r\n\r\nYi Zhao\r\n","3":"Changed the file format to Unix. \r\n\r\nI found that the DOS format file has problems to work under the Unix. \r\nYestorday I didn't test it under the UNIX. \r\n\r\nI am sorry, if it caused some problem. \r\n\r\nThanks,\r\n\r\nYi Zhao\r\n","package":"javascript.vim","4":"javascript.vim","src_id":"5396","5":"5396","creation_date":"1141933600","6":"1141933600"}]},"1490":{"script_id":"1490","0":"1490","script_name":"jr.vim","1":"jr.vim","script_type":"syntax","2":"syntax","summary":"jr language syntax script","3":"jr language syntax script","description":"This script provides syntax highlighting for the JR programming language, available at http:\/\/www.cs.ucdavis.edu\/~olsson\/research\/jr\/","4":"This script provides syntax highlighting for the JR programming language, available at http:\/\/www.cs.ucdavis.edu\/~olsson\/research\/jr\/","install_details":"install in the syntax directory, et voila !  You will also need to edit the synmenu.vim and filetype.vim files, and add jr to the list of languages.\r\n\r\nThe line to add in symmenu.vim should look like this (you'll need to adjust the numbers):\r\n    an 50.40.410 &Syntax.HIJK.Jr :cal SetSyn(\"jr\")<CR>\r\n\r\nThe lines to add in filetype.vim:\r\n\r\n\" JR\r\nau BufNewFile,BufRead *.jr                      setf jr\r\n\r\n\r\n\r\n\r\n","5":"install in the syntax directory, et voila !  You will also need to edit the synmenu.vim and filetype.vim files, and add jr to the list of languages.\r\n\r\nThe line to add in symmenu.vim should look like this (you'll need to adjust the numbers):\r\n    an 50.40.410 &Syntax.HIJK.Jr :cal SetSyn(\"jr\")<CR>\r\n\r\nThe lines to add in filetype.vim:\r\n\r\n\" JR\r\nau BufNewFile,BufRead *.jr                      setf jr\r\n\r\n\r\n\r\n\r\n","first_name":"francois","6":"francois","last_name":"kilchoer","7":"kilchoer","releases":[{"0":"1490","vim_version":"6.0","1":"6.0","script_version":"1.2","2":"1.2","version_comment":"This version adds support for two extra keywords, co and elseafter.\r\n","3":"This version adds support for two extra keywords, co and elseafter.\r\n","package":"jr.vim","4":"jr.vim","src_id":"5502","5":"5502","creation_date":"1143721972","6":"1143721972"},{"0":"1490","vim_version":"6.0","1":"6.0","script_version":"1.1","2":"1.1","version_comment":"Initial upload","3":"Initial upload","package":"jr.vim","4":"jr.vim","src_id":"5392","5":"5392","creation_date":"1141866392","6":"1141866392"}]},"1489":{"script_id":"1489","0":"1489","script_name":"PluginKiller","1":"PluginKiller","script_type":"utility","2":"utility","summary":"Helps plugin writers find trouble-causing options before their users do","3":"Helps plugin writers find trouble-causing options before their users do","description":"The PluginKiller helps Vim plugin writers to determine which options that users might set that will cause problems with their plugin before their users do!\r\n\r\nTo do this, the PluginKiller utilizes two instantiations of vim.  The first one is the pluginkiller server; it keeps a copy of the current potential trouble-making options.  The second vim is your working vim; in it you exercise your plugin.  Whenever your plugin works with the currently active trouble-makers, type :PKg (for PluginKiller-good).  This tells the PluginKiller server about the nice set of options it selected, and it responds with a new set.\r\n\r\nOn the other hand, whenever your plugin isn't performing up to your exacting specifications, type :PKb (for PluginKiller-bad).  This command tells the PluginKiller server about the trouble it caused, and the PluginKiller responds with a smaller set of potential troublemakers.\r\n\r\nYou'll need to repeat trying out your plugin and typing :PKg or :PKb until the PluginKiller has found the culprit option.  Its OK to quit the second vim and to use :PK to resume working with the PluginKiller server -- whether you need to quit and resume depends on how your plugin operates -- :PK just reloads the current settings that the PluginKiller wants to have tried out.\r\n\r\n(alpha\/beta version available at http:\/\/www.drchip.org\/astronaut\/vim\/index.html#PLUGINKILLER)\r\n","4":"The PluginKiller helps Vim plugin writers to determine which options that users might set that will cause problems with their plugin before their users do!\r\n\r\nTo do this, the PluginKiller utilizes two instantiations of vim.  The first one is the pluginkiller server; it keeps a copy of the current potential trouble-making options.  The second vim is your working vim; in it you exercise your plugin.  Whenever your plugin works with the currently active trouble-makers, type :PKg (for PluginKiller-good).  This tells the PluginKiller server about the nice set of options it selected, and it responds with a new set.\r\n\r\nOn the other hand, whenever your plugin isn't performing up to your exacting specifications, type :PKb (for PluginKiller-bad).  This command tells the PluginKiller server about the trouble it caused, and the PluginKiller responds with a smaller set of potential troublemakers.\r\n\r\nYou'll need to repeat trying out your plugin and typing :PKg or :PKb until the PluginKiller has found the culprit option.  Its OK to quit the second vim and to use :PK to resume working with the PluginKiller server -- whether you need to quit and resume depends on how your plugin operates -- :PK just reloads the current settings that the PluginKiller wants to have tried out.\r\n\r\n(alpha\/beta version available at http:\/\/www.drchip.org\/astronaut\/vim\/index.html#PLUGINKILLER)\r\n","install_details":"(NOTE: you need vimball v18 or later; see vimscript#1502; vim 7.1a or later should already be ok)\r\n\r\n    vim pluginkiller.vba.gz\r\n     :so %\r\n     :q\r\n\r\n The directions under |pluginkiller-steps| give detailed information on how to use the pluginkiller.\r\n\r\n\r\n\t","5":"(NOTE: you need vimball v18 or later; see vimscript#1502; vim 7.1a or later should already be ok)\r\n\r\n    vim pluginkiller.vba.gz\r\n     :so %\r\n     :q\r\n\r\n The directions under |pluginkiller-steps| give detailed information on how to use the pluginkiller.\r\n\r\n\r\n\t","first_name":"Charles","6":"Charles","last_name":"Campbell","7":"Campbell","releases":[{"0":"1489","vim_version":"7.0","1":"7.0","script_version":"3","2":"3","version_comment":"added more options for pluginkiller's checkout: acd, insertmode, num, spell\r\n","3":"added more options for pluginkiller's checkout: acd, insertmode, num, spell\r\n","package":"pluginkiller.vba.gz","4":"pluginkiller.vba.gz","src_id":"9931","5":"9931","creation_date":"1234057784","6":"1234057784"},{"0":"1489","vim_version":"7.0","1":"7.0","script_version":"2","2":"2","version_comment":"The acd option even causes the pluginkiller itself problems; hence, it doesn't define it for testing (although a commented out version is available).\r\n\r\nPluginkiller is now easier to use: type :PK in a test file with vim and the pluginkiller will initialize itself using a server.  Pluginkiller needs +clientserver enabled vim.","3":"The acd option even causes the pluginkiller itself problems; hence, it doesn't define it for testing (although a commented out version is available).\r\n\r\nPluginkiller is now easier to use: type :PK in a test file with vim and the pluginkiller will initialize itself using a server.  Pluginkiller needs +clientserver enabled vim.","package":"pluginkiller.vba.gz","4":"pluginkiller.vba.gz","src_id":"6299","5":"6299","creation_date":"1161260588","6":"1161260588"},{"0":"1489","vim_version":"6.0","1":"6.0","script_version":"1","2":"1","version_comment":"Initial upload.","3":"Initial upload.","package":"pluginkiller.tar.gz","4":"pluginkiller.tar.gz","src_id":"5390","5":"5390","creation_date":"1141802344","6":"1141802344"}]},"1488":{"script_id":"1488","0":"1488","script_name":"ScrollColors","1":"ScrollColors","script_type":"utility","2":"utility","summary":"Colorsheme Scroller, Chooser, and Browser","3":"Colorsheme Scroller, Chooser, and Browser","description":"SYNOPSIS:\r\n   This is colorscheme Scroller\/Chooser\/Browser.\r\n   With this plugin, you walk through installed colorschemes using arrow keys.\r\n\r\nSHORT USAGE DESCRIPTION:\r\n   Drop ScrollColors.vim into your plugin directory.\r\n   Type :SCROLL\r\n   Use arrow keys to walk through colorschemes, ? for help, Esc to exit.\r\n\r\n DETAILED DESCRIPTION:\r\n   1. source ScrollColors.vim  \" or drop ScrollColors.vim into\r\n                          \" your ~\/.vim\/plugins directory\r\n   2. Type :SCROLL\r\n        Another synonym is :COLOR\r\n   3. Use arrows to scroll thgough colorschemes.\r\n   4. When done, press Esc to exit. You will be prompted\r\n      wether to\r\n\r\n   You can download 140 colorschemes pack from:\r\n        http:\/\/www.vim.org\/scripts\/script.php?script_id=625\r\n   Having 140 installed colorschemes is in no way prerequisite for ScrollColors. But with ScrollColors you can preview 140 colorschemes  in couple of minutes. Have fun.\r\n\r\nCUSTOM KEY MAPPINGS:\r\n   You can map two keys of your choice to NextColor and PrevColor actions.\r\n   Choose pair of shortcut keys (for example <F2> and <f3>, or \\n and \\p)\r\n   and map them as follows:\r\n      map <silent><F3> :NEXTCOLOR<cr>\r\n      map <silent><F2> :PREVCOLOR<cr>\r\n\r\nWorks both in vim6 and vim7.","4":"SYNOPSIS:\r\n   This is colorscheme Scroller\/Chooser\/Browser.\r\n   With this plugin, you walk through installed colorschemes using arrow keys.\r\n\r\nSHORT USAGE DESCRIPTION:\r\n   Drop ScrollColors.vim into your plugin directory.\r\n   Type :SCROLL\r\n   Use arrow keys to walk through colorschemes, ? for help, Esc to exit.\r\n\r\n DETAILED DESCRIPTION:\r\n   1. source ScrollColors.vim  \" or drop ScrollColors.vim into\r\n                          \" your ~\/.vim\/plugins directory\r\n   2. Type :SCROLL\r\n        Another synonym is :COLOR\r\n   3. Use arrows to scroll thgough colorschemes.\r\n   4. When done, press Esc to exit. You will be prompted\r\n      wether to\r\n\r\n   You can download 140 colorschemes pack from:\r\n        http:\/\/www.vim.org\/scripts\/script.php?script_id=625\r\n   Having 140 installed colorschemes is in no way prerequisite for ScrollColors. But with ScrollColors you can preview 140 colorschemes  in couple of minutes. Have fun.\r\n\r\nCUSTOM KEY MAPPINGS:\r\n   You can map two keys of your choice to NextColor and PrevColor actions.\r\n   Choose pair of shortcut keys (for example <F2> and <f3>, or \\n and \\p)\r\n   and map them as follows:\r\n      map <silent><F3> :NEXTCOLOR<cr>\r\n      map <silent><F2> :PREVCOLOR<cr>\r\n\r\nWorks both in vim6 and vim7.","install_details":"Download file ScrollColors.vim and put it into your $HOME\/.vim\/plugin\r\ndirectory. Create this directory if it does not exists, like:\r\n   mkdir -p $HOME\/.vim\/plugin\r\nRestart vim.","5":"Download file ScrollColors.vim and put it into your $HOME\/.vim\/plugin\r\ndirectory. Create this directory if it does not exists, like:\r\n   mkdir -p $HOME\/.vim\/plugin\r\nRestart vim.","first_name":"Yakov","6":"Yakov","last_name":"Lerner","7":"Lerner","releases":[{"0":"1488","vim_version":"6.0","1":"6.0","script_version":"20060719","2":"20060719","version_comment":"Script cksum is 2186132668.\r\nLast change: sort speedup on vim7 using builtin sort()","3":"Script cksum is 2186132668.\r\nLast change: sort speedup on vim7 using builtin sort()","package":"ScrollColor.vim","4":"ScrollColor.vim","src_id":"5966","5":"5966","creation_date":"1153233373","6":"1153233373"},{"0":"1488","vim_version":"6.0","1":"6.0","script_version":"20060718","2":"20060718","version_comment":"2006-07-18 version. FIle cksum is 362040352","3":"2006-07-18 version. FIle cksum is 362040352","package":"ScrollColor.vim","4":"ScrollColor.vim","src_id":"5964","5":"5964","creation_date":"1153222756","6":"1153222756"},{"0":"1488","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"ScrollColor.vim","4":"ScrollColor.vim","src_id":"5387","5":"5387","creation_date":"1141801097","6":"1141801097"}]},"1487":{"script_id":"1487","0":"1487","script_name":"django.vim","1":"django.vim","script_type":"syntax","2":"syntax","summary":"Syntax highlighting for Django templates","3":"Syntax highlighting for Django templates","description":"Type \":setfiletype htmldjango\" from within Vim to select highlighting for Django HTML templates.  If you desire Django template highlighting but not HTML highlighting, type \":setfiletype django\" instead.  Items highlighted include template tags, built-in filters, arguments and comments.\r\n\r\n(N.B. For Vim 7.1 and later you shouldn't need the additional htmldjango.vim file.)","4":"Type \":setfiletype htmldjango\" from within Vim to select highlighting for Django HTML templates.  If you desire Django template highlighting but not HTML highlighting, type \":setfiletype django\" instead.  Items highlighted include template tags, built-in filters, arguments and comments.\r\n\r\n(N.B. For Vim 7.1 and later you shouldn't need the additional htmldjango.vim file.)","install_details":"Save the files django.vim and htmldjango.vim to your ~\/.vim\/syntax directory.","5":"Save the files django.vim and htmldjango.vim to your ~\/.vim\/syntax directory.","first_name":"Dave","6":"Dave","last_name":"Hodder","7":"Hodder","releases":[{"0":"1487","vim_version":"6.0","1":"6.0","script_version":"1.08","2":"1.08","version_comment":"Highlights the elif tag and truncatechars filter, both from Django 1.4.  Thanks to iynaix (Lin Xianyi).","3":"Highlights the elif tag and truncatechars filter, both from Django 1.4.  Thanks to iynaix (Lin Xianyi).","package":"django.vim","4":"django.vim","src_id":"17736","5":"17736","creation_date":"1333834689","6":"1333834689"},{"0":"1487","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"matchit plug-in (extended \"%\" matching) for common Django template tags.  Copy to your ~\/.vim\/ftplugin directory.  Thanks to Michael Brown.","3":"matchit plug-in (extended \"%\" matching) for common Django template tags.  Copy to your ~\/.vim\/ftplugin directory.  Thanks to Michael Brown.","package":"django.vim","4":"django.vim","src_id":"9805","5":"9805","creation_date":"1231802666","6":"1231802666"},{"0":"1487","vim_version":"6.0","1":"6.0","script_version":"1.05","2":"1.05","version_comment":"Improved error highlighting.","3":"Improved error highlighting.","package":"htmldjango.vim","4":"htmldjango.vim","src_id":"6678","5":"6678","creation_date":"1169966062","6":"1169966062"}]},"1486":{"script_id":"1486","0":"1486","script_name":"fasm.vim","1":"fasm.vim","script_type":"indent","2":"indent","summary":"an indent script for fasm assembler","3":"an indent script for fasm assembler","description":"an indent script for fasm assembler","4":"an indent script for fasm assembler","install_details":"drop it into your local indent directory:\r\n~\/.vim\/indent (*nix)\r\n$vim\/vimfiles\/indent(win32)\r\n \r\n","5":"drop it into your local indent directory:\r\n~\/.vim\/indent (*nix)\r\n$vim\/vimfiles\/indent(win32)\r\n \r\n","first_name":"6","6":"6","last_name":"+","7":"+","releases":[{"0":"1486","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"fasm.vim","4":"fasm.vim","src_id":"5381","5":"5381","creation_date":"1141697156","6":"1141697156"}]},"1485":{"script_id":"1485","0":"1485","script_name":"StickyCursor","1":"StickyCursor","script_type":"utility","2":"utility","summary":"remembers the cursor position relative to the window","3":"remembers the cursor position relative to the window","description":"The default vim behavour when switching to an open buffer is to scroll the window so the cursor will be positioned at the window's center.\r\n\r\nThis script remembers the cursor position relative to the window for every visited buffer and restores it (makes proper scrolling) when switched back to the buffer.\r\n\r\nFor more pleasure you can \":set nostartofline\" option.\r\n","4":"The default vim behavour when switching to an open buffer is to scroll the window so the cursor will be positioned at the window's center.\r\n\r\nThis script remembers the cursor position relative to the window for every visited buffer and restores it (makes proper scrolling) when switched back to the buffer.\r\n\r\nFor more pleasure you can \":set nostartofline\" option.\r\n","install_details":"just place to the plugin directory","5":"just place to the plugin directory","first_name":"Sply","6":"Sply","last_name":"Splyeff","7":"Splyeff","releases":[{"0":"1485","vim_version":"6.0","1":"6.0","script_version":"1.1","2":"1.1","version_comment":"If the cursor moved after we leaved a buffer, don't try to restore in-window position.","3":"If the cursor moved after we leaved a buffer, don't try to restore in-window position.","package":"stickycursor.vim","4":"stickycursor.vim","src_id":"6613","5":"6613","creation_date":"1168767829","6":"1168767829"},{"0":"1485","vim_version":"6.0","1":"6.0","script_version":"1","2":"1","version_comment":"Initial upload","3":"Initial upload","package":"stickycursor.vim","4":"stickycursor.vim","src_id":"5362","5":"5362","creation_date":"1141461242","6":"1141461242"}]},"1484":{"script_id":"1484","0":"1484","script_name":"spectro.vim","1":"spectro.vim","script_type":"color scheme","2":"color scheme","summary":"Colorful scheme using HSL colorspace, S and L can be defined globally.","3":"Colorful scheme using HSL colorspace, S and L can be defined globally.","description":"Spectro is a colorful scheme with a dark background. The colors are defined in the HSL (Hue, Saturation, Lightness) colorspace.\r\nThe main interest over the RGB colorspace, is that it's easy to change the overall brightness of the scheme in order to adapt to different screens. \r\nThe Saturation and Lightness are defined globally with g:spectro_saturation and g:spectro_lightness, which shall be set between 0 and 255.\r\n\r\nYou can see what it looks like here : \"http:\/\/pierreantoine.lacaze.free.fr\/linux\/config\/\r\n\r\nNote that there is no support for terms yet.","4":"Spectro is a colorful scheme with a dark background. The colors are defined in the HSL (Hue, Saturation, Lightness) colorspace.\r\nThe main interest over the RGB colorspace, is that it's easy to change the overall brightness of the scheme in order to adapt to different screens. \r\nThe Saturation and Lightness are defined globally with g:spectro_saturation and g:spectro_lightness, which shall be set between 0 and 255.\r\n\r\nYou can see what it looks like here : \"http:\/\/pierreantoine.lacaze.free.fr\/linux\/config\/\r\n\r\nNote that there is no support for terms yet.","install_details":"Just drop it in your .vim\/colors\/ directory and perform :colorscheme spectro","5":"Just drop it in your .vim\/colors\/ directory and perform :colorscheme spectro","first_name":"Pierre-Antoine","6":"Pierre-Antoine","last_name":"Lacaze","7":"Lacaze","releases":[{"0":"1484","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"spectro.vim","4":"spectro.vim","src_id":"5356","5":"5356","creation_date":"1141397100","6":"1141397100"}]},"1483":{"script_id":"1483","0":"1483","script_name":"marklar.vim","1":"marklar.vim","script_type":"color scheme","2":"color scheme","summary":"Dark colorscheme based on green chalkboard colors","3":"Dark colorscheme based on green chalkboard colors","description":":Marklar            - change certain setting dynamically.\r\n:Marklar (no args)  - displays current settings \r\n:Marklar bold?      - diplays current value of bold. works similarly for all options.\r\n:Marklar bold!      - toggles bold value for 'categorical' colors\r\n:Marklar underline! - toggles the appearance of Underlined. \r\n                      marklar.vim uses Underlined as an additional color\r\n                      without the underline as default.\r\n                      If you want the Underline back, turn it back on.\r\n:Marklar ignore!    - toggles the appearance of Ignore'd text \r\n                      from nearly invisible to invisible, ie. same color as background.\r\n:Marklar conceal!   - toggles the appearance of Conceal'd text \r\n                      from Comment to Ignore.\r\n\r\nThis means ... you can dynamically make Conceal'd text invisible, nearly\r\ninvisible or appear as a Comment in both gui and xterm-256 environments.\r\n\r\nThis colorscheme is designed to reduce eyestrain by using a much lower contrast\r\nthan black on white. It is appropriate for all lighting conditions.\r\n\r\nIncludes a palette of colors, support for RainbowLevels and Vimwiki headers.\r\nUncomment as desired.\r\n\r\nGui color support is complete and includes the latest highlight commands from\r\n801.  \r\n\r\nPresumes that you are able to set the foreground and background color to match\r\nthese gui colors. \r\n    fg = #71c293 or rgb(113, 194, 147)\r\n    bg = #06544a or rgb(6, 84, 74)\r\nPretty normal stuff for many terminals at this time.\r\n\r\nxterm-256 color support is 'pretty good atm, though still improving'. The\r\nintent is that xterm-256 conform to the gui colors as closely as possible,\r\ngiving the same essential experience when moving from one environment to the\r\nanother with reduced color capabilities. Next release will complete this\r\neffort.\r\n\r\nxterm-color support for the Terminal.app on macos<=10.6. Similarly, the intent\r\nhere is also to give a similar experience with a much reduced set of colors.\r\n\r\nin your vimrc file put (for example),\r\n    Marklar bold 0\r\n    Marklar underline 1\r\nor, if you are using version<700,\r\n    let g:marklar_bold_opt = 0\r\n    let g:marklar_underline_opt = 1\r\nto establish your own preferences.\r\n\r\nThe 'categorical' colors are the colors which are used by syntax files to match\r\nlinguistic elements.  'Categorical' colors are treated as an ad hoc linguistic\r\nheat map. In order of 'heat' they are..\r\n\r\n    PreProc - includes Delimiter as a remap\r\n    Statement\r\n    Type\r\n    Special\r\n    Identifier\r\n    Constant\r\n    Underlined\r\n\r\nThe emphasis - yellow - is placed upon 'Type'.\r\nThe rest of the colors are 'interface' colors.\r\n","4":":Marklar            - change certain setting dynamically.\r\n:Marklar (no args)  - displays current settings \r\n:Marklar bold?      - diplays current value of bold. works similarly for all options.\r\n:Marklar bold!      - toggles bold value for 'categorical' colors\r\n:Marklar underline! - toggles the appearance of Underlined. \r\n                      marklar.vim uses Underlined as an additional color\r\n                      without the underline as default.\r\n                      If you want the Underline back, turn it back on.\r\n:Marklar ignore!    - toggles the appearance of Ignore'd text \r\n                      from nearly invisible to invisible, ie. same color as background.\r\n:Marklar conceal!   - toggles the appearance of Conceal'd text \r\n                      from Comment to Ignore.\r\n\r\nThis means ... you can dynamically make Conceal'd text invisible, nearly\r\ninvisible or appear as a Comment in both gui and xterm-256 environments.\r\n\r\nThis colorscheme is designed to reduce eyestrain by using a much lower contrast\r\nthan black on white. It is appropriate for all lighting conditions.\r\n\r\nIncludes a palette of colors, support for RainbowLevels and Vimwiki headers.\r\nUncomment as desired.\r\n\r\nGui color support is complete and includes the latest highlight commands from\r\n801.  \r\n\r\nPresumes that you are able to set the foreground and background color to match\r\nthese gui colors. \r\n    fg = #71c293 or rgb(113, 194, 147)\r\n    bg = #06544a or rgb(6, 84, 74)\r\nPretty normal stuff for many terminals at this time.\r\n\r\nxterm-256 color support is 'pretty good atm, though still improving'. The\r\nintent is that xterm-256 conform to the gui colors as closely as possible,\r\ngiving the same essential experience when moving from one environment to the\r\nanother with reduced color capabilities. Next release will complete this\r\neffort.\r\n\r\nxterm-color support for the Terminal.app on macos<=10.6. Similarly, the intent\r\nhere is also to give a similar experience with a much reduced set of colors.\r\n\r\nin your vimrc file put (for example),\r\n    Marklar bold 0\r\n    Marklar underline 1\r\nor, if you are using version<700,\r\n    let g:marklar_bold_opt = 0\r\n    let g:marklar_underline_opt = 1\r\nto establish your own preferences.\r\n\r\nThe 'categorical' colors are the colors which are used by syntax files to match\r\nlinguistic elements.  'Categorical' colors are treated as an ad hoc linguistic\r\nheat map. In order of 'heat' they are..\r\n\r\n    PreProc - includes Delimiter as a remap\r\n    Statement\r\n    Type\r\n    Special\r\n    Identifier\r\n    Constant\r\n    Underlined\r\n\r\nThe emphasis - yellow - is placed upon 'Type'.\r\nThe rest of the colors are 'interface' colors.\r\n","install_details":"Install:\r\n    place marklar.vim in \r\n    ~\/.vim\/colors\/ \r\n    (~\/vimfiles\/colors on PC)\r\n","5":"Install:\r\n    place marklar.vim in \r\n    ~\/.vim\/colors\/ \r\n    (~\/vimfiles\/colors on PC)\r\n","first_name":"sm","6":"sm","last_name":"smithfield","7":"smithfield","releases":[{"0":"1483","vim_version":"7.0","1":"7.0","script_version":"0.8","2":"0.8","version_comment":"more...","3":"more...","package":"marklar.vim","4":"marklar.vim","src_id":"27114","5":"27114","creation_date":"1586613866","6":"1586613866"},{"0":"1483","vim_version":"5.7","1":"5.7","script_version":"0.7","2":"0.7","version_comment":"Nearly completely rethought. Looks similar to earlier versions, but that's about it.","3":"Nearly completely rethought. Looks similar to earlier versions, but that's about it.","package":"marklar.vim","4":"marklar.vim","src_id":"26017","5":"26017","creation_date":"1527864379","6":"1527864379"},{"0":"1483","vim_version":"6.0","1":"6.0","script_version":"0.5","2":"0.5","version_comment":"Added optional settings, 'bold' and 'ignore'. Added a normal command to manipulate the settings. Useful color tweaks.","3":"Added optional settings, 'bold' and 'ignore'. Added a normal command to manipulate the settings. Useful color tweaks.","package":"marklar.vim","4":"marklar.vim","src_id":"6487","5":"6487","creation_date":"1164983279","6":"1164983279"},{"0":"1483","vim_version":"7.0","1":"7.0","script_version":"0.4","2":"0.4","version_comment":"Improvements in colors and contrasts based on vim7 and certain features that were previously obscure to the author.","3":"Improvements in colors and contrasts based on vim7 and certain features that were previously obscure to the author.","package":"marklar.vim","4":"marklar.vim","src_id":"6407","5":"6407","creation_date":"1163404959","6":"1163404959"},{"0":"1483","vim_version":"6.0","1":"6.0","script_version":"0.3","2":"0.3","version_comment":"better colors for tabs, popups, matching parens, error msgs.","3":"better colors for tabs, popups, matching parens, error msgs.","package":"marklar.vim","4":"marklar.vim","src_id":"6359","5":"6359","creation_date":"1162348501","6":"1162348501"},{"0":"1483","vim_version":"7.0","1":"7.0","script_version":"0.2","2":"0.2","version_comment":"Added support for (some of) the coloring additions to 7.0 (the ones that I use :) )","3":"Added support for (some of) the coloring additions to 7.0 (the ones that I use :) )","package":"marklar.vim","4":"marklar.vim","src_id":"5930","5":"5930","creation_date":"1152198655","6":"1152198655"},{"0":"1483","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"marklar.vim","4":"marklar.vim","src_id":"5355","5":"5355","creation_date":"1141320670","6":"1141320670"}]},"1482":{"script_id":"1482","0":"1482","script_name":"kid.vim","1":"kid.vim","script_type":"syntax","2":"syntax","summary":"Syntax file for the Kid templating language","3":"Syntax file for the Kid templating language","description":"Kid (http:\/\/kid.lesscode.org\/) is a attribute-based xml templating language written in Python. This syntax file covers the language as documented in the language specification. The gzipped tarball also contains a kid ftplugin, for gvim integration and a kid ftdetect plugin so that vim highlights the file as kid rather than xml\/xhtml.","4":"Kid (http:\/\/kid.lesscode.org\/) is a attribute-based xml templating language written in Python. This syntax file covers the language as documented in the language specification. The gzipped tarball also contains a kid ftplugin, for gvim integration and a kid ftdetect plugin so that vim highlights the file as kid rather than xml\/xhtml.","install_details":"Extract the file in your home directory. The three scripts are extracted to:\r\n.\/.vim\/ftdetect\/kid.vim\r\n..\/vim\/ftplugin\/kid.vim\r\n.\/.vim\/syntax\/kid.vim","5":"Extract the file in your home directory. The three scripts are extracted to:\r\n.\/.vim\/ftdetect\/kid.vim\r\n..\/vim\/ftplugin\/kid.vim\r\n.\/.vim\/syntax\/kid.vim","first_name":"Karl","6":"Karl","last_name":"Guertin","7":"Guertin","releases":[{"0":"1482","vim_version":"6.0","1":"6.0","script_version":"0.5","2":"0.5","version_comment":"Kid bundle","3":"Kid bundle","package":"kid.tgz","4":"kid.tgz","src_id":"5350","5":"5350","creation_date":"1141289012","6":"1141289012"}]},"1481":{"script_id":"1481","0":"1481","script_name":"cvops-aut.vim","1":"cvops-aut.vim","script_type":"syntax","2":"syntax","summary":"Syntax for CVOPS automation language","3":"Syntax for CVOPS automation language","description":"Syntax file for the CVOPS (C Virtual OPerating System, http:\/\/www.celtius.com\/s.asp?id=418) automation language.","4":"Syntax file for the CVOPS (C Virtual OPerating System, http:\/\/www.celtius.com\/s.asp?id=418) automation language.","install_details":"","5":"","first_name":"Konstantin","6":"Konstantin","last_name":"Shemyak","7":"Shemyak","releases":[{"0":"1481","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"cvops-aut.vim","4":"cvops-aut.vim","src_id":"5347","5":"5347","creation_date":"1141274950","6":"1141274950"}]},"1480":{"script_id":"1480","0":"1480","script_name":"CmdlineCompl.vim","1":"CmdlineCompl.vim","script_type":"utility","2":"utility","summary":"Word completion on the command line","3":"Word completion on the command line","description":"See also:\r\n\r\nvimscript#474\r\nvimscript#147\r\n\r\nDescription:\r\n\r\nBased on ideas from the above two plugins, but also adds the following features:\r\n * Word completion in a regular command line. (in addition to word completion in a search command line)\r\n * Word completion in the middle of the command line. (not just the end of the command line)\r\n\r\nTo use, hit F12 while in the command line. Hit F12 again to get a different completion. Repeated invocations will cycle through all possible completions. Word completion will be done in the context of the current buffer.\r\n\r\nCustomization:\r\n\r\nTo inhibit loading of this plugin, define the loaded_cmdline_compl variable.\r\n\r\nTo change the key mapping, cmap the desired key to <Plug>CmdlinecomplComplete. For example:\r\n\r\n    cmap <F11> <Plug>CmdlinecomplComplete\r\n","4":"See also:\r\n\r\nvimscript#474\r\nvimscript#147\r\n\r\nDescription:\r\n\r\nBased on ideas from the above two plugins, but also adds the following features:\r\n * Word completion in a regular command line. (in addition to word completion in a search command line)\r\n * Word completion in the middle of the command line. (not just the end of the command line)\r\n\r\nTo use, hit F12 while in the command line. Hit F12 again to get a different completion. Repeated invocations will cycle through all possible completions. Word completion will be done in the context of the current buffer.\r\n\r\nCustomization:\r\n\r\nTo inhibit loading of this plugin, define the loaded_cmdline_compl variable.\r\n\r\nTo change the key mapping, cmap the desired key to <Plug>CmdlinecomplComplete. For example:\r\n\r\n    cmap <F11> <Plug>CmdlinecomplComplete\r\n","install_details":"Drop this file into your plugin directory.","5":"Drop this file into your plugin directory.","first_name":"Po Shan","6":"Po Shan","last_name":"Cheah","7":"Cheah","releases":[{"0":"1480","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"cmdlinecompl.vim","4":"cmdlinecompl.vim","src_id":"5346","5":"5346","creation_date":"1141225214","6":"1141225214"}]},"1479":{"script_id":"1479","0":"1479","script_name":"muttrc.vim","1":"muttrc.vim","script_type":"syntax","2":"syntax","summary":"A syntax file to support the syntax of devel versions of mutt","3":"A syntax file to support the syntax of devel versions of mutt","description":"A modified script to support the syntax of devel versions of mutt, as well as a few of the more common patches. This syntax file is for muttrc files. This is the same script that comes with the official vim, but I'm using this page to store versions of the file that are more recent than the one included in the stable vim release.","4":"A modified script to support the syntax of devel versions of mutt, as well as a few of the more common patches. This syntax file is for muttrc files. This is the same script that comes with the official vim, but I'm using this page to store versions of the file that are more recent than the one included in the stable vim release.","install_details":"Put it with the rest of your syntax files, for example, in ~\/.vim\/syntax\/","5":"Put it with the rest of your syntax files, for example, in ~\/.vim\/syntax\/","first_name":"Kyle","6":"Kyle","last_name":"Wheeler","7":"Wheeler","releases":[{"0":"1479","vim_version":"6.0","1":"6.0","script_version":"1.9","2":"1.9","version_comment":"Updated for Mutt 1.10.0","3":"Updated for Mutt 1.10.0","package":"muttrc.vim","4":"muttrc.vim","src_id":"25989","5":"25989","creation_date":"1526958349","6":"1526958349"},{"0":"1479","vim_version":"5.7","1":"5.7","script_version":"1.8.8","2":"1.8.8","version_comment":"Updated for mutt 1.7.0 (thanks Greg Novack!)","3":"Updated for mutt 1.7.0 (thanks Greg Novack!)","package":"muttrc.vim","4":"muttrc.vim","src_id":"24458","5":"24458","creation_date":"1471557895","6":"1471557895"},{"0":"1479","vim_version":"5.7","1":"5.7","script_version":"1.8.7","2":"1.8.7","version_comment":"Add a bunch of variables that have been added in the last few years (thanks to Greg Novak!), and fixed some bugs where a couple boolean variables didn't have all of their no- and inv- variants included.","3":"Add a bunch of variables that have been added in the last few years (thanks to Greg Novak!), and fixed some bugs where a couple boolean variables didn't have all of their no- and inv- variants included.","package":"muttrc.vim","4":"muttrc.vim","src_id":"24413","5":"24413","creation_date":"1469812841","6":"1469812841"},{"0":"1479","vim_version":"5.7","1":"5.7","script_version":"1.8.6","2":"1.8.6","version_comment":"Fix for cpoptions, add BackTab to the list of keys, and add support for a few sidebar keywords.","3":"Fix for cpoptions, add BackTab to the list of keys, and add support for a few sidebar keywords.","package":"muttrc.vim","4":"muttrc.vim","src_id":"17370","5":"17370","creation_date":"1328215455","6":"1328215455"},{"0":"1479","vim_version":"5.7","1":"5.7","script_version":"1.8.5","2":"1.8.5","version_comment":"Support terminals with 100+ colors, all variations on =-based string matching, and partial-string prefixes on variables (so that bright$my_color isn't flagged as an error, for example).","3":"Support terminals with 100+ colors, all variations on =-based string matching, and partial-string prefixes on variables (so that bright$my_color isn't flagged as an error, for example).","package":"muttrc.vim","4":"muttrc.vim","src_id":"14653","5":"14653","creation_date":"1293640385","6":"1293640385"},{"0":"1479","vim_version":"5.7","1":"5.7","script_version":"1.8.4","2":"1.8.4","version_comment":"Handle a few new things; break-thread, link-threads, and asterisks in unlists and unsubscribe commands, as well as the new %D in folder_format.","3":"Handle a few new things; break-thread, link-threads, and asterisks in unlists and unsubscribe commands, as well as the new %D in folder_format.","package":"muttrc.vim","4":"muttrc.vim","src_id":"13528","5":"13528","creation_date":"1281372147","6":"1281372147"},{"0":"1479","vim_version":"5.7","1":"5.7","script_version":"1.8.3","2":"1.8.3","version_comment":"New release for mutt 1.5.20. Handles new fcc_attach behavior, and supports new variables honor_disposition and search_context.","3":"New release for mutt 1.5.20. Handles new fcc_attach behavior, and supports new variables honor_disposition and search_context.","package":"muttrc.vim","4":"muttrc.vim","src_id":"10837","5":"10837","creation_date":"1245083352","6":"1245083352"},{"0":"1479","vim_version":"5.7","1":"5.7","script_version":"1.8.2","2":"1.8.2","version_comment":"fixing the behavior of a few hook commands, added end-cond, and a few other minor nits.","3":"fixing the behavior of a few hook commands, added end-cond, and a few other minor nits.","package":"muttrc.vim","4":"muttrc.vim","src_id":"9983","5":"9983","creation_date":"1234812007","6":"1234812007"},{"0":"1479","vim_version":"5.7","1":"5.7","script_version":"1.8.1","2":"1.8.1","version_comment":"ssl_verify_dates, ssl_verify_host, attempt to handle blocks of text with escaped whitespace (not 100% accurate, but \r\n... better than nothing). also handle \"color header\" lines with regexes on the end","3":"ssl_verify_dates, ssl_verify_host, attempt to handle blocks of text with escaped whitespace (not 100% accurate, but \r\n... better than nothing). also handle \"color header\" lines with regexes on the end","package":"muttrc.vim","4":"muttrc.vim","src_id":"9879","5":"9879","creation_date":"1233156156","6":"1233156156"},{"0":"1479","vim_version":"5.7","1":"5.7","script_version":"1.8","2":"1.8","version_comment":"fixing several things, including header_cache_compress, unnecessarily required whitespace, some matching efficiency, matching pattern undocumented features, setting multiple variables at once, using & and ? variable prefixes, as well as handling escaped variables in macros better.","3":"fixing several things, including header_cache_compress, unnecessarily required whitespace, some matching efficiency, matching pattern undocumented features, setting multiple variables at once, using & and ? variable prefixes, as well as handling escaped variables in macros better.","package":"muttrc.vim","4":"muttrc.vim","src_id":"9738","5":"9738","creation_date":"1230760091","6":"1230760091"},{"0":"1479","vim_version":"5.7","1":"5.7","script_version":"1.7.1","2":"1.7.1","version_comment":"Added support for query_format, f-keys, and next-unread-mailbox. Fixed multi-line macro highlighting, and a typo in \"resend-message\".","3":"Added support for query_format, f-keys, and next-unread-mailbox. Fixed multi-line macro highlighting, and a typo in \"resend-message\".","package":"muttrc.vim","4":"muttrc.vim","src_id":"8797","5":"8797","creation_date":"1213260401","6":"1213260401"},{"0":"1479","vim_version":"5.7","1":"5.7","script_version":"1.7","2":"1.7","version_comment":"Highlights % patterns, and simple patterns can contain variables. Updated for time_inc and threading patterns. Also, if I hadn't mentioned it before, includes support for the printf-style format sequence patterns in the strings that use them.","3":"Highlights % patterns, and simple patterns can contain variables. Updated for time_inc and threading patterns. Also, if I hadn't mentioned it before, includes support for the printf-style format sequence patterns in the strings that use them.","package":"muttrc.vim","4":"muttrc.vim","src_id":"8138","5":"8138","creation_date":"1199795463","6":"1199795463"},{"0":"1479","vim_version":"5.7","1":"5.7","script_version":"1.6","2":"1.6","version_comment":"Added highlighting for the escapes in strings that support them. The support is somewhat primitive, but effective for most common setups.","3":"Added highlighting for the escapes in strings that support them. The support is somewhat primitive, but effective for most common setups.","package":"muttrc.vim","4":"muttrc.vim","src_id":"7458","5":"7458","creation_date":"1186421806","6":"1186421806"},{"0":"1479","vim_version":"5.7","1":"5.7","script_version":"1.5.2","2":"1.5.2","version_comment":"Improved date highlighting in patterns, spell-check, updated for mutt 1.5.14 keywords","3":"Improved date highlighting in patterns, spell-check, updated for mutt 1.5.14 keywords","package":"muttrc.vim","4":"muttrc.vim","src_id":"6866","5":"6866","creation_date":"1173741063","6":"1173741063"},{"0":"1479","vim_version":"5.7","1":"5.7","script_version":"1.5.1","2":"1.5.1","version_comment":"Vastly improved macro highlighting. Also handles aliases with multiple targets, and = search patterns.","3":"Vastly improved macro highlighting. Also handles aliases with multiple targets, and = search patterns.","package":"muttrc.vim","4":"muttrc.vim","src_id":"6488","5":"6488","creation_date":"1165051835","6":"1165051835"},{"0":"1479","vim_version":"5.7","1":"5.7","script_version":"1.5","2":"1.5","version_comment":"Eliminates imap_cachedir in favor of message_cachedir, fixed some errors in highlighting color lines, added support for my_* variables, what-key, and noop","3":"Eliminates imap_cachedir in favor of message_cachedir, fixed some errors in highlighting color lines, added support for my_* variables, what-key, and noop","package":"muttrc.vim","4":"muttrc.vim","src_id":"6032","5":"6032","creation_date":"1154584291","6":"1154584291"},{"0":"1479","vim_version":"5.7","1":"5.7","script_version":"1.4.0.1","2":"1.4.0.1","version_comment":"tag-prefix-cond was missing","3":"tag-prefix-cond was missing","package":"muttrc.vim","4":"muttrc.vim","src_id":"5818","5":"5818","creation_date":"1149835717","6":"1149835717"},{"0":"1479","vim_version":"5.7","1":"5.7","script_version":"1.4","2":"1.4","version_comment":"Better support for unhook commands, and support for Brendan Cully's smtp patch.","3":"Better support for unhook commands, and support for Brendan Cully's smtp patch.","package":"muttrc.vim","4":"muttrc.vim","src_id":"5811","5":"5811","creation_date":"1149718298","6":"1149718298"},{"0":"1479","vim_version":"5.7","1":"5.7","script_version":"1.3","2":"1.3","version_comment":"Support for new CVS options, and the patches currently used in Debian.","3":"Support for new CVS options, and the patches currently used in Debian.","package":"muttrc.vim","4":"muttrc.vim","src_id":"5744","5":"5744","creation_date":"1148302369","6":"1148302369"},{"0":"1479","vim_version":"5.7","1":"5.7","script_version":"1.2","2":"1.2","version_comment":"More support for line-breaks (in alias, unalias, bind, macro, color, uncolor). Support for color lines now much improved. Fixed some regular expression highlighting, and created pattern highlighting - applies to both color lines and hooks.","3":"More support for line-breaks (in alias, unalias, bind, macro, color, uncolor). Support for color lines now much improved. Fixed some regular expression highlighting, and created pattern highlighting - applies to both color lines and hooks.","package":"muttrc.vim","4":"muttrc.vim","src_id":"5512","5":"5512","creation_date":"1144047308","6":"1144047308"},{"0":"1479","vim_version":"5.7","1":"5.7","script_version":"1.1.1","2":"1.1.1","version_comment":"Changed the syntax ordering so that (un)lists and (un)subscribe lines get their -group flags highlighted correctly now.","3":"Changed the syntax ordering so that (un)lists and (un)subscribe lines get their -group flags highlighted correctly now.","package":"muttrc.vim","4":"muttrc.vim","src_id":"5493","5":"5493","creation_date":"1143618900","6":"1143618900"},{"0":"1479","vim_version":"5.7","1":"5.7","script_version":"1.1","2":"1.1","version_comment":"Improved support of un* constructs, allowed for escaped line-breaks in more places, allowed for un-quoted regular expressions in some places.","3":"Improved support of un* constructs, allowed for escaped line-breaks in more places, allowed for un-quoted regular expressions in some places.","package":"muttrc.vim","4":"muttrc.vim","src_id":"5391","5":"5391","creation_date":"1141818806","6":"1141818806"},{"0":"1479","vim_version":"6.0","1":"6.0","script_version":"1","2":"1","version_comment":"Initial upload","3":"Initial upload","package":"muttrc.vim","4":"muttrc.vim","src_id":"5344","5":"5344","creation_date":"1141214317","6":"1141214317"}]},"1478":{"script_id":"1478","0":"1478","script_name":"Surveyor","1":"Surveyor","script_type":"color scheme","2":"color scheme","summary":"High contrast colorscheme with dark background","3":"High contrast colorscheme with dark background","description":"My first attempt at a color scheme for vim. It uses high contrast colors with a dark background.\r\nSeems to work pretty well under situations with high light levels.\r\n\r\nScreenshot:\r\nhttp:\/\/www.vulcanusgames.net\/mars\/vimcolors1.gif","4":"My first attempt at a color scheme for vim. It uses high contrast colors with a dark background.\r\nSeems to work pretty well under situations with high light levels.\r\n\r\nScreenshot:\r\nhttp:\/\/www.vulcanusgames.net\/mars\/vimcolors1.gif","install_details":"Like any other colorscheme.","5":"Like any other colorscheme.","first_name":"Marcel","6":"Marcel","last_name":"Strik","7":"Strik","releases":[{"0":"1478","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"surveyor.vim","4":"surveyor.vim","src_id":"5311","5":"5311","creation_date":"1140700650","6":"1140700650"}]},"1477":{"script_id":"1477","0":"1477","script_name":"Modeliner","1":"Modeliner","script_type":"utility","2":"utility","summary":"Generates modeline according to the current settings.","3":"Generates modeline according to the current settings.","description":"[How to use it?]\r\n\r\nexecute ':Modeliner'.\r\n\r\n\r\n[And, what will happen?]\r\n\r\nIf your current settings are like below:\r\n  - setl fenc=utf-8\r\n  - setl et\r\n  - setl sts=4\r\n\r\nthen you will get a modeline like:\r\n  - for 'c' filetype:\r\n      \/* vim: set fenc=utf-8 et sts=4 : *\/\r\n  - for 'xml' filetype:\r\n      <!-- vim: set fenc=utf-8 et sts=4 : -->\r\n\r\n\r\n[How to include my favorite options?]\r\n\r\nModify  g:Modeliner_format.  It is a simple format.\r\n\r\nAn example:\r\n    let g:Modeliner_format = 'fenc=  tw=  et  ts=  sts=  sw=  backup wrap'","4":"[How to use it?]\r\n\r\nexecute ':Modeliner'.\r\n\r\n\r\n[And, what will happen?]\r\n\r\nIf your current settings are like below:\r\n  - setl fenc=utf-8\r\n  - setl et\r\n  - setl sts=4\r\n\r\nthen you will get a modeline like:\r\n  - for 'c' filetype:\r\n      \/* vim: set fenc=utf-8 et sts=4 : *\/\r\n  - for 'xml' filetype:\r\n      <!-- vim: set fenc=utf-8 et sts=4 : -->\r\n\r\n\r\n[How to include my favorite options?]\r\n\r\nModify  g:Modeliner_format.  It is a simple format.\r\n\r\nAn example:\r\n    let g:Modeliner_format = 'fenc=  tw=  et  ts=  sts=  sw=  backup wrap'","install_details":"Put this plugin in your plugin directory(e.g. $VIMRUNTIME\/plugin).\r\nThen restart Vim or :source it. ","5":"Put this plugin in your plugin directory(e.g. $VIMRUNTIME\/plugin).\r\nThen restart Vim or :source it. ","first_name":"Shuhei","6":"Shuhei","last_name":"Kubota","7":"Kubota","releases":[{"0":"1477","vim_version":"8.2","1":"8.2","script_version":"0.5.1v9","2":"0.5.1v9","version_comment":"remove s:","3":"remove s:","package":"modeliner9.vim","4":"modeliner9.vim","src_id":"27946","5":"27946","creation_date":"1644833623","6":"1644833623"},{"0":"1477","vim_version":"7.0","1":"7.0","script_version":"0.5.0v9","2":"0.5.0v9","version_comment":"vim9script: work under empty &commentstring","3":"vim9script: work under empty &commentstring","package":"modeliner9.vim","4":"modeliner9.vim","src_id":"27846","5":"27846","creation_date":"1639750971","6":"1639750971"},{"0":"1477","vim_version":"7.0","1":"7.0","script_version":"0.5.0","2":"0.5.0","version_comment":"work under empty &commentstring","3":"work under empty &commentstring","package":"modeliner.vim","4":"modeliner.vim","src_id":"27845","5":"27845","creation_date":"1639750943","6":"1639750943"},{"0":"1477","vim_version":"7.0","1":"7.0","script_version":"0.4.0","2":"0.4.0","version_comment":"vim9script","3":"vim9script","package":"modeliner9.vim","4":"modeliner9.vim","src_id":"27834","5":"27834","creation_date":"1639056477","6":"1639056477"},{"0":"1477","vim_version":"7.0","1":"7.0","script_version":"0.3.0","2":"0.3.0","version_comment":"If you use The NERD Commenter, this script uses it to generate a modeline as a comment.","3":"If you use The NERD Commenter, this script uses it to generate a modeline as a comment.","package":"modeliner.vim","4":"modeliner.vim","src_id":"8861","5":"8861","creation_date":"1214504607","6":"1214504607"},{"0":"1477","vim_version":"6.0","1":"6.0","script_version":"0.2.0","2":"0.2.0","version_comment":"finds the existing modeline and overwrite it","3":"finds the existing modeline and overwrite it","package":"modeliner.vim","4":"modeliner.vim","src_id":"7743","5":"7743","creation_date":"1191428987","6":"1191428987"},{"0":"1477","vim_version":"6.0","1":"6.0","script_version":"0.1.0","2":"0.1.0","version_comment":"Initial upload","3":"Initial upload","package":"modeliner.vim","4":"modeliner.vim","src_id":"5305","5":"5305","creation_date":"1140627821","6":"1140627821"}]},"1475":{"script_id":"1475","0":"1475","script_name":"maude.vim","1":"maude.vim","script_type":"syntax","2":"syntax","summary":"Syntax file for the Maude language","3":"Syntax file for the Maude language","description":"This is a very rudimentary but functional and hopefully useful syntax file for the Maude language (http:\/\/maude.cs.uiuc.edu\/). A screenshot with the \"koehler\" colorscheme is available here: http:\/\/severinghaus.org\/projects\/mandelbrot\/maudelbrot_vim.png","4":"This is a very rudimentary but functional and hopefully useful syntax file for the Maude language (http:\/\/maude.cs.uiuc.edu\/). A screenshot with the \"koehler\" colorscheme is available here: http:\/\/severinghaus.org\/projects\/mandelbrot\/maudelbrot_vim.png","install_details":"","5":"","first_name":"Steven","6":"Steven","last_name":"Severinghaus","7":"Severinghaus","releases":[{"0":"1475","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"maude.vim","4":"maude.vim","src_id":"5277","5":"5277","creation_date":"1140432003","6":"1140432003"}]},"1474":{"script_id":"1474","0":"1474","script_name":"yellow","1":"yellow","script_type":"color scheme","2":"color scheme","summary":"A yellow-green color scheme","3":"A yellow-green color scheme","description":"I read from a readability study that yellow on green was pretty readable, and decided to try making a scheme out of it. Basic colors are yellow, green, and orange on dark green.","4":"I read from a readability study that yellow on green was pretty readable, and decided to try making a scheme out of it. Basic colors are yellow, green, and orange on dark green.","install_details":"","5":"","first_name":"Shawn","6":"Shawn","last_name":"Axsom","7":"Axsom","releases":[{"0":"1474","vim_version":"6.0","1":"6.0","script_version":"1.0b","2":"1.0b","version_comment":"Some adjustments.","3":"Some adjustments.","package":"yeller.vim","4":"yeller.vim","src_id":"5279","5":"5279","creation_date":"1140439973","6":"1140439973"},{"0":"1474","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"yeller.vim","4":"yeller.vim","src_id":"5276","5":"5276","creation_date":"1140430298","6":"1140430298"}]},"1473":{"script_id":"1473","0":"1473","script_name":"vim7-install.sh","1":"vim7-install.sh","script_type":"utility","2":"utility","summary":"{download + build + install} latest vim7.1 from svn sources in 1 command.","3":"{download + build + install} latest vim7.1 from svn sources in 1 command.","description":"(This shell script works on Linux, Solaris, Unix, OSX, Cygwin. Not for VisualStudio.)\r\nDownload this script, vim7-install.sh, into any directory and invoke:\r\n        sh .\/vim7-install.sh\r\n\r\nThis will download vim7 sources, then build and install vim7. \r\n- You do not need root privileges. If you do not have root privileges, it will install under your $HOME ($HOME\/bin). If you do have root privileges, it will install system-wide (\/usr\/local\/bin. You can change this with --prefix option).\r\n- No arguments are needed (but you can add any configure-style arguments, see below). \r\n- The latest vim7 sources are downloaded either from svn repository, or from cvs repository, up to the latest today's patch. The freshest runtime files are downloaded from rsync repository.\r\n\r\nPrerequisites: requires either svn client or cvs client installed. Requires C compiler (gcc). On debian or ubuntu, install build prerequisite packages with this command: apt-get build-dep vim-gtk vim-full\r\n\r\nBy default, Vim will be built with '--with-features=huge'. But you can override this with commandline arguments, see below. \r\n\r\nIn case of  $HOME\/bin install, script will prompt you to add $HOME\/bin to your PATH.\r\n\r\nNon-root installation vs Root installation\r\n-------------------------------------------------------\r\nIf you are invoking the script as root, vim will be installed into \/usr\/local (that is , for everybody). If you are non-root, then you will be prompted for one of two choices: (1) to install vim under your $HOME (for which you do not need root password), or (2) to install vim under \/usr\/local, for which you need to know root password.\r\n\r\nIn case of $HOME\/bin install, script will prompt you to add $HOME\/bin to your PATH.\r\n\r\nCustom build options\r\n------------------------------\r\nAll arguments beginning with '--' will be passed to 'configure'. Options beginning with single minus are for vim7-install.sh itself:\r\n   sh vim7-install.sh  -h           prints options of vim7-install.sh itself\r\n   sh vim7-install.sh  --help     prints options of vim's 'configure', and options of vim7-install.sh\r\n\r\nWithout arguments, vim will be built with '--with-features=huge', unless you pass some other '--with-features='  argument. The '--with-features=huge' enables \"almost all features\" (including GUI ), but does not include \"interpreters\" (perl, python, ruby, etc).\r\n\r\nTo include interpreters, add following options:\r\n      .\/vim7-install.sh --enable-perlinterp --enable-pythoninterp --enable-rubyinterp\r\n\r\nChoice of download methods: Svn-export, Svn-checkout, CVS\r\n----------------------------------------------------------------------\r\nDefault download method is Svn-export (thus you need svn client software). Other\r\ndownload methods are CVS (option -cvs), and Svn-checkout (-cvscheckout).\r\nAs of 2006, CVS server is less reliable than SVN server; but CVS server gets patches first. SVN server lags behind CVS by several hours. Overall, SVN server is better choice since it is more reliable.\r\nSvn is noticeably faster than svn-checkout in one run, but svn-checkout is faster\r\nif you do multiple builds.\r\n\r\nSource cache, automatic cleanup, manual cleanup\r\n-------------------------------------------------------------------------\r\n- vim7-install.sh downloads only \"delta\";  that is, changed files that changed since last build. Thus the non-first build is *much* faster than the first build. Your fist build must download the whole source tree, of course.\r\n\r\n- each build is automatically preceded by 'make distclean'. This is non-optional.\r\n\r\n- script will checks for locally modified source files. If script finds locally modified source files, you will be prompted (whether to (1) drop local changes, or (2) to preserve local changes).\r\n\r\n-  if local source tree becomes corrupted and unusable, you need to clean it:\r\n         .\/vim7_install.sh clean\r\n\r\nQ: Do I need to uninstall vim6 before using vim7-install.sh ?\r\n------------------------------------------------------------------------------------\r\nA: No. I recommend that you do not uninstall vim6 before \r\nusing vim7-install.sh. But I do recommend that you rename \r\nvim6 before using vim7-install.sh, as follows:\r\n      become root\r\n      mv \/usr\/bin\/vim \/usr\/bin\/vim6\r\n\r\nPossible future enhancements: \r\n  - easy inclusion of external patches \r\n  - rsync download method.\r\n\r\nBug reports and feedback\r\n-------------------------------------\r\nSend to:   iler.ml at gmail.com\r\nPlease let me know if it works on other Unix flavor other than mentioned in the first line. Or doesn't work.","4":"(This shell script works on Linux, Solaris, Unix, OSX, Cygwin. Not for VisualStudio.)\r\nDownload this script, vim7-install.sh, into any directory and invoke:\r\n        sh .\/vim7-install.sh\r\n\r\nThis will download vim7 sources, then build and install vim7. \r\n- You do not need root privileges. If you do not have root privileges, it will install under your $HOME ($HOME\/bin). If you do have root privileges, it will install system-wide (\/usr\/local\/bin. You can change this with --prefix option).\r\n- No arguments are needed (but you can add any configure-style arguments, see below). \r\n- The latest vim7 sources are downloaded either from svn repository, or from cvs repository, up to the latest today's patch. The freshest runtime files are downloaded from rsync repository.\r\n\r\nPrerequisites: requires either svn client or cvs client installed. Requires C compiler (gcc). On debian or ubuntu, install build prerequisite packages with this command: apt-get build-dep vim-gtk vim-full\r\n\r\nBy default, Vim will be built with '--with-features=huge'. But you can override this with commandline arguments, see below. \r\n\r\nIn case of  $HOME\/bin install, script will prompt you to add $HOME\/bin to your PATH.\r\n\r\nNon-root installation vs Root installation\r\n-------------------------------------------------------\r\nIf you are invoking the script as root, vim will be installed into \/usr\/local (that is , for everybody). If you are non-root, then you will be prompted for one of two choices: (1) to install vim under your $HOME (for which you do not need root password), or (2) to install vim under \/usr\/local, for which you need to know root password.\r\n\r\nIn case of $HOME\/bin install, script will prompt you to add $HOME\/bin to your PATH.\r\n\r\nCustom build options\r\n------------------------------\r\nAll arguments beginning with '--' will be passed to 'configure'. Options beginning with single minus are for vim7-install.sh itself:\r\n   sh vim7-install.sh  -h           prints options of vim7-install.sh itself\r\n   sh vim7-install.sh  --help     prints options of vim's 'configure', and options of vim7-install.sh\r\n\r\nWithout arguments, vim will be built with '--with-features=huge', unless you pass some other '--with-features='  argument. The '--with-features=huge' enables \"almost all features\" (including GUI ), but does not include \"interpreters\" (perl, python, ruby, etc).\r\n\r\nTo include interpreters, add following options:\r\n      .\/vim7-install.sh --enable-perlinterp --enable-pythoninterp --enable-rubyinterp\r\n\r\nChoice of download methods: Svn-export, Svn-checkout, CVS\r\n----------------------------------------------------------------------\r\nDefault download method is Svn-export (thus you need svn client software). Other\r\ndownload methods are CVS (option -cvs), and Svn-checkout (-cvscheckout).\r\nAs of 2006, CVS server is less reliable than SVN server; but CVS server gets patches first. SVN server lags behind CVS by several hours. Overall, SVN server is better choice since it is more reliable.\r\nSvn is noticeably faster than svn-checkout in one run, but svn-checkout is faster\r\nif you do multiple builds.\r\n\r\nSource cache, automatic cleanup, manual cleanup\r\n-------------------------------------------------------------------------\r\n- vim7-install.sh downloads only \"delta\";  that is, changed files that changed since last build. Thus the non-first build is *much* faster than the first build. Your fist build must download the whole source tree, of course.\r\n\r\n- each build is automatically preceded by 'make distclean'. This is non-optional.\r\n\r\n- script will checks for locally modified source files. If script finds locally modified source files, you will be prompted (whether to (1) drop local changes, or (2) to preserve local changes).\r\n\r\n-  if local source tree becomes corrupted and unusable, you need to clean it:\r\n         .\/vim7_install.sh clean\r\n\r\nQ: Do I need to uninstall vim6 before using vim7-install.sh ?\r\n------------------------------------------------------------------------------------\r\nA: No. I recommend that you do not uninstall vim6 before \r\nusing vim7-install.sh. But I do recommend that you rename \r\nvim6 before using vim7-install.sh, as follows:\r\n      become root\r\n      mv \/usr\/bin\/vim \/usr\/bin\/vim6\r\n\r\nPossible future enhancements: \r\n  - easy inclusion of external patches \r\n  - rsync download method.\r\n\r\nBug reports and feedback\r\n-------------------------------------\r\nSend to:   iler.ml at gmail.com\r\nPlease let me know if it works on other Unix flavor other than mentioned in the first line. Or doesn't work.","install_details":"No installation is necessary for this script. Just download it and invoke using shell:\r\n    sh .\/vim7-install.sh\r\n\r\nLatest version can be downloaded from:\r\n    http:\/\/ilerner.3b1.org\/vim\/vim7-install.sh\r\n \r\nIf you install VIM into $HOME\/bin, make sure you have $HOME\/bin in your PATH. You do this by editing your shell startup script, which depends on your shell  (~\/.bashrc, ~\/.profile, ~\/.cshrc, ~\/.tcshrc ). \r\n#------------------------------------------------------------------\r\n#Recent changes\r\n#------------------------------------------------------------------\r\n# 2007-05-10 updated for vim7.1\r\n# 2008-02-20 we download freshest runtime files (with rsync)\r\n# 2008-06-30 URL updated for 7.2. 'svn export' is default method, not 'svn co'.\r\n","5":"No installation is necessary for this script. Just download it and invoke using shell:\r\n    sh .\/vim7-install.sh\r\n\r\nLatest version can be downloaded from:\r\n    http:\/\/ilerner.3b1.org\/vim\/vim7-install.sh\r\n \r\nIf you install VIM into $HOME\/bin, make sure you have $HOME\/bin in your PATH. You do this by editing your shell startup script, which depends on your shell  (~\/.bashrc, ~\/.profile, ~\/.cshrc, ~\/.tcshrc ). \r\n#------------------------------------------------------------------\r\n#Recent changes\r\n#------------------------------------------------------------------\r\n# 2007-05-10 updated for vim7.1\r\n# 2008-02-20 we download freshest runtime files (with rsync)\r\n# 2008-06-30 URL updated for 7.2. 'svn export' is default method, not 'svn co'.\r\n","first_name":"Yakov","6":"Yakov","last_name":"Lerner","7":"Lerner","releases":[{"0":"1473","vim_version":"7.0","1":"7.0","script_version":"080630","2":"080630","version_comment":"URL updated for 7.2. Script checksum 359326547","3":"URL updated for 7.2. Script checksum 359326547","package":"vim7-install.sh","4":"vim7-install.sh","src_id":"8871","5":"8871","creation_date":"1214830342","6":"1214830342"},{"0":"1473","vim_version":"7.0","1":"7.0","script_version":"20080220","2":"20080220","version_comment":"We now download most recent runtime files (with rsync). Script checksum 2430187707","3":"We now download most recent runtime files (with rsync). Script checksum 2430187707","package":"vim7-install.sh","4":"vim7-install.sh","src_id":"8312","5":"8312","creation_date":"1203479359","6":"1203479359"},{"0":"1473","vim_version":"7.0","1":"7.0","script_version":"070510","2":"070510","version_comment":"Updated for vim7.1[a]. Checksum 1420119929.","3":"Updated for vim7.1[a]. Checksum 1420119929.","package":"vim7-install.sh","4":"vim7-install.sh","src_id":"7089","5":"7089","creation_date":"1178721455","6":"1178721455"}]},"1472":{"script_id":"1472","0":"1472","script_name":"Sift","1":"Sift","script_type":"color scheme","2":"color scheme","summary":"a stark Color Scheme for maximum reading speed\/identifiability","3":"a stark Color Scheme for maximum reading speed\/identifiability","description":"My goal for this theme is to be brighter and more contrasted than my previous scheme (baycomb), and I focused on making the scheme cohesive as well as having different color schemes for different sections of code. \r\n\r\nMy basic vision for this scheme, along with others to various degree, would be, even if you were to squint, you could easily identify one type of code from another. Colors are laid out on a spectrum from yellow to blue, with the strongest yellow colors being control structures, green being variables, and blue being values. I usually lay it out this way so that, for example, if functions are performed on a variable, it will fit in well with a yellow\/green scheme, but if you throw one into a long string it won't look like the string is cut in two.\r\n\r\nThat's the basic idea. Let me know if there's anything I could be doing better in that sense.\r\n                                                                \r\nComments and suggestions:  axs221@gmail.com\r\n\r\n","4":"My goal for this theme is to be brighter and more contrasted than my previous scheme (baycomb), and I focused on making the scheme cohesive as well as having different color schemes for different sections of code. \r\n\r\nMy basic vision for this scheme, along with others to various degree, would be, even if you were to squint, you could easily identify one type of code from another. Colors are laid out on a spectrum from yellow to blue, with the strongest yellow colors being control structures, green being variables, and blue being values. I usually lay it out this way so that, for example, if functions are performed on a variable, it will fit in well with a yellow\/green scheme, but if you throw one into a long string it won't look like the string is cut in two.\r\n\r\nThat's the basic idea. Let me know if there's anything I could be doing better in that sense.\r\n                                                                \r\nComments and suggestions:  axs221@gmail.com\r\n\r\n","install_details":"","5":"","first_name":"Shawn","6":"Shawn","last_name":"Axsom","7":"Axsom","releases":[{"0":"1472","vim_version":"7.0","1":"7.0","script_version":"2.1","2":"2.1","version_comment":"Updated terminal colors for JavaScript support","3":"Updated terminal colors for JavaScript support","package":"sift.vim","4":"sift.vim","src_id":"24192","5":"24192","creation_date":"1461378137","6":"1461378137"},{"0":"1472","vim_version":"7.0","1":"7.0","script_version":"2.0","2":"2.0","version_comment":"Updated Color Terminal colors to closely match that found in GVim :)\r\n\r\nAlso added highlighting for GitGutter, Matchmaker, VimDiff.","3":"Updated Color Terminal colors to closely match that found in GVim :)\r\n\r\nAlso added highlighting for GitGutter, Matchmaker, VimDiff.","package":"sift.vim","4":"sift.vim","src_id":"22971","5":"22971","creation_date":"1425250594","6":"1425250594"},{"0":"1472","vim_version":"6.0","1":"6.0","script_version":"1.3c","2":"1.3c","version_comment":"Toned down the text color for normal text, still yellowish but an offwhite.","3":"Toned down the text color for normal text, still yellowish but an offwhite.","package":"sift.vim","4":"sift.vim","src_id":"5673","5":"5673","creation_date":"1147243970","6":"1147243970"},{"0":"1472","vim_version":"7.0","1":"7.0","script_version":"1.3b","2":"1.3b","version_comment":"Added MatchParen colors and made a few other changes","3":"Added MatchParen colors and made a few other changes","package":"sift.vim","4":"sift.vim","src_id":"5664","5":"5664","creation_date":"1147190460","6":"1147190460"},{"0":"1472","vim_version":"6.0","1":"6.0","script_version":"1.3","2":"1.3","version_comment":"Numerous changes in the same direction as the last version.","3":"Numerous changes in the same direction as the last version.","package":"sift.vim","4":"sift.vim","src_id":"5524","5":"5524","creation_date":"1144233349","6":"1144233349"},{"0":"1472","vim_version":"6.0","1":"6.0","script_version":"1.2","2":"1.2","version_comment":"Redesigned, changed \"Type\" to a green and tweaked other colors.","3":"Redesigned, changed \"Type\" to a green and tweaked other colors.","package":"sift.vim","4":"sift.vim","src_id":"5521","5":"5521","creation_date":"1144179524","6":"1144179524"},{"0":"1472","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"sift.vim","4":"sift.vim","src_id":"5517","5":"5517","creation_date":"1144150846","6":"1144150846"}]},"1471":{"script_id":"1471","0":"1471","script_name":"watermark","1":"watermark","script_type":"color scheme","2":"color scheme","summary":"a low contrast Color Scheme","3":"a low contrast Color Scheme","description":"Watermark is a low contrast scheme, with a similar color set as baycomb (vimscript #1454) but the contrast of ps_color (vimscript #760).\r\n                                                                                       _______________\r\n           Comments and suggestions:                    ***| axs221@gmail.com | ***\r\n                                                                                       --------------------------- ","4":"Watermark is a low contrast scheme, with a similar color set as baycomb (vimscript #1454) but the contrast of ps_color (vimscript #760).\r\n                                                                                       _______________\r\n           Comments and suggestions:                    ***| axs221@gmail.com | ***\r\n                                                                                       --------------------------- ","install_details":"","5":"","first_name":"Shawn","6":"Shawn","last_name":"Axsom","7":"Axsom","releases":[{"0":"1471","vim_version":"6.0","1":"6.0","script_version":"1.0b","2":"1.0b","version_comment":"Minor changes.","3":"Minor changes.","package":"watermark.vim","4":"watermark.vim","src_id":"5319","5":"5319","creation_date":"1140776433","6":"1140776433"},{"0":"1471","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload.","3":"Initial upload.","package":"watermark.vim","4":"watermark.vim","src_id":"5318","5":"5318","creation_date":"1140766070","6":"1140766070"}]},"1470":{"script_id":"1470","0":"1470","script_name":"lbnf.vim","1":"lbnf.vim","script_type":"syntax","2":"syntax","summary":"LBNF (Labeled Backus Naur Form) syntax file","3":"LBNF (Labeled Backus Naur Form) syntax file","description":"Syntax highlighting for Labeled BNF.","4":"Syntax highlighting for Labeled BNF.","install_details":"Copy to $VIMRUNTIME\/syntax\/  or $HOME\/.vim\/syntax\/\r\nAdd \"au bufreadpre,bufnewfile *.cf set ft=lbnf\" to your $HOME\/.vimrc file. \r\nNow all *.cf-files should be highlighted using lbnf.vim","5":"Copy to $VIMRUNTIME\/syntax\/  or $HOME\/.vim\/syntax\/\r\nAdd \"au bufreadpre,bufnewfile *.cf set ft=lbnf\" to your $HOME\/.vimrc file. \r\nNow all *.cf-files should be highlighted using lbnf.vim","first_name":"Jim","6":"Jim","last_name":"Persson","7":"Persson","releases":[{"0":"1470","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"lbnf.vim","4":"lbnf.vim","src_id":"5234","5":"5234","creation_date":"1140081672","6":"1140081672"}]},"1469":{"script_id":"1469","0":"1469","script_name":"promela","1":"promela","script_type":"indent","2":"indent","summary":"Promela indent file","3":"Promela indent file","description":"This is my first attempt at writing an indent file for VIM.\r\nIt seems to work OK for at least basic stuff.","4":"This is my first attempt at writing an indent file for VIM.\r\nIt seems to work OK for at least basic stuff.","install_details":"Just put it in $HOME\/.vim\/indent and make sure that the PROMELA file type is recognized by VIM.\r\nIf VIM does not recognize PROMELA either add this to your existing $HOME\/.vim\/filetype.vim:\r\n\" Promela\r\nau BufNewFile,BufRead *.prom,*.prm,*.promela,*.pml              setf promela\r\n\r\nor create a filetype.vim looking like this:\r\naugroup filetypedetect\r\nau BufNewFile,BufRead *.prom,*.prm,*.promela,*.pml              setf promela\r\naugroup END","5":"Just put it in $HOME\/.vim\/indent and make sure that the PROMELA file type is recognized by VIM.\r\nIf VIM does not recognize PROMELA either add this to your existing $HOME\/.vim\/filetype.vim:\r\n\" Promela\r\nau BufNewFile,BufRead *.prom,*.prm,*.promela,*.pml              setf promela\r\n\r\nor create a filetype.vim looking like this:\r\naugroup filetypedetect\r\nau BufNewFile,BufRead *.prom,*.prm,*.promela,*.pml              setf promela\r\naugroup END","first_name":"Oscar","6":"Oscar","last_name":"Hellstr\u00c3\u00b6m","7":"Hellstr\u00c3\u00b6m","releases":[{"0":"1469","vim_version":"6.0","1":"6.0","script_version":"0.2","2":"0.2","version_comment":"Initial upload","3":"Initial upload","package":"promela.vim","4":"promela.vim","src_id":"5231","5":"5231","creation_date":"1140021278","6":"1140021278"}]},"1468":{"script_id":"1468","0":"1468","script_name":"bayQua","1":"bayQua","script_type":"color scheme","2":"color scheme","summary":"An offwhite version of the baycomb colorscheme, influenced by TaQua","3":"An offwhite version of the baycomb colorscheme, influenced by TaQua","description":"An offwhite version of baycomb.vim, with subtle background shading on syntax.\r\nThis is basically a mix between my latest colorscheme, baycomb, and TaQua, by Eustaquio Rangel de Oliveira Jr. \r\n\r\nWhite backgrounds make it harder for me to identify normal text, and it seems harder to identify colors than on a dark background, so I added the soft glowing colors to syntax background. They may or may not be visible on your computer (they are too light to see on my computer at work; i adjusted them to be darker but then they were too dark and overpowering on my home computer).\r\n\r\nThe scheme has highlighting for both the GUI and Terminal. For tips and more information, go to baycomb's site:\r\n\r\nbaycomb: http:\/\/www.vim.org\/scripts\/script.php?script_id=1454\r\nTaQua: http:\/\/www.vim.org\/scripts\/script.php?script_id=594\r\n\r\n                                                                                 _______________\r\n     Comments and suggestions:                    ***| axs221@gmail.com | ***\r\n                                                                                 ---------------------------","4":"An offwhite version of baycomb.vim, with subtle background shading on syntax.\r\nThis is basically a mix between my latest colorscheme, baycomb, and TaQua, by Eustaquio Rangel de Oliveira Jr. \r\n\r\nWhite backgrounds make it harder for me to identify normal text, and it seems harder to identify colors than on a dark background, so I added the soft glowing colors to syntax background. They may or may not be visible on your computer (they are too light to see on my computer at work; i adjusted them to be darker but then they were too dark and overpowering on my home computer).\r\n\r\nThe scheme has highlighting for both the GUI and Terminal. For tips and more information, go to baycomb's site:\r\n\r\nbaycomb: http:\/\/www.vim.org\/scripts\/script.php?script_id=1454\r\nTaQua: http:\/\/www.vim.org\/scripts\/script.php?script_id=594\r\n\r\n                                                                                 _______________\r\n     Comments and suggestions:                    ***| axs221@gmail.com | ***\r\n                                                                                 ---------------------------","install_details":"If the grey terminal background is too dark, try white (add to vimrc or baqua.vim):\r\n   hi Normal ctermbg=white\r\n\r\nTry bolding Identifiers if, for example, you'd like to easily spot where tags close in HTML\r\n   hi Identifier gui=bold","5":"If the grey terminal background is too dark, try white (add to vimrc or baqua.vim):\r\n   hi Normal ctermbg=white\r\n\r\nTry bolding Identifiers if, for example, you'd like to easily spot where tags close in HTML\r\n   hi Identifier gui=bold","first_name":"Shawn","6":"Shawn","last_name":"Axsom","7":"Axsom","releases":[{"0":"1468","vim_version":"7.0","1":"7.0","script_version":"2.0","2":"2.0","version_comment":"Updated a few color terminal colors to better match the GVim GUI colors","3":"Updated a few color terminal colors to better match the GVim GUI colors","package":"bayQua.vim","4":"bayQua.vim","src_id":"22969","5":"22969","creation_date":"1425225876","6":"1425225876"},{"0":"1468","vim_version":"6.0","1":"6.0","script_version":"1.2b","2":"1.2b","version_comment":"Removed background colors.","3":"Removed background colors.","package":"bayQua.vim","4":"bayQua.vim","src_id":"5317","5":"5317","creation_date":"1140762994","6":"1140762994"},{"0":"1468","vim_version":"6.0","1":"6.0","script_version":"1.2","2":"1.2","version_comment":"Updated Terminal colors to better match the GUI. Colors now look almost exactly like the GUI (on my Windows Console atleast).","3":"Updated Terminal colors to better match the GUI. Colors now look almost exactly like the GUI (on my Windows Console atleast).","package":"bayQua.vim","4":"bayQua.vim","src_id":"5240","5":"5240","creation_date":"1140125999","6":"1140125999"},{"0":"1468","vim_version":"6.0","1":"6.0","script_version":"1.1c","2":"1.1c","version_comment":"Minor changes.","3":"Minor changes.","package":"bayQua.vim","4":"bayQua.vim","src_id":"5237","5":"5237","creation_date":"1140090097","6":"1140090097"},{"0":"1468","vim_version":"6.0","1":"6.0","script_version":"1.1b","2":"1.1b","version_comment":"Fixed Underlined to be readable, and made a few adjustments.","3":"Fixed Underlined to be readable, and made a few adjustments.","package":"bayQua.vim","4":"bayQua.vim","src_id":"5233","5":"5233","creation_date":"1140072281","6":"1140072281"},{"0":"1468","vim_version":"6.0","1":"6.0","script_version":"1.1","2":"1.1","version_comment":"Updated terminal colors, now featuring a dark grey background and adjusted values for terminal colors to be visible on new light bg.","3":"Updated terminal colors, now featuring a dark grey background and adjusted values for terminal colors to be visible on new light bg.","package":"bayQua.vim","4":"bayQua.vim","src_id":"5232","5":"5232","creation_date":"1140022055","6":"1140022055"},{"0":"1468","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload.","3":"Initial upload.","package":"bayQua.vim","4":"bayQua.vim","src_id":"5229","5":"5229","creation_date":"1140018957","6":"1140018957"}]},"1467":{"script_id":"1467","0":"1467","script_name":"far","1":"far","script_type":"color scheme","2":"color scheme","summary":"FAR internal editor color scheme","3":"FAR internal editor color scheme","description":"This color scheme is very similar to FAR(http:\/\/www.rarsoft.com) internal editor one.\r\nI use Vim on Unix environment (vim) as replacement of Midnight Commander's internal editor and on Win32 env (gvim) as replacement of FAR internal editor.","4":"This color scheme is very similar to FAR(http:\/\/www.rarsoft.com) internal editor one.\r\nI use Vim on Unix environment (vim) as replacement of Midnight Commander's internal editor and on Win32 env (gvim) as replacement of FAR internal editor.","install_details":"Just put it in $VIMRUNTIME\/colors directory (:help colorscheme) and say inside editor\r\n:colorscheme far","5":"Just put it in $VIMRUNTIME\/colors directory (:help colorscheme) and say inside editor\r\n:colorscheme far","first_name":"Dmitri","6":"Dmitri","last_name":"Shevchenko","7":"Shevchenko","releases":[{"0":"1467","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"far.vim","4":"far.vim","src_id":"5218","5":"5218","creation_date":"1139961404","6":"1139961404"}]},"1466":{"script_id":"1466","0":"1466","script_name":"netrw.vim : support to ftp explorer","1":"netrw.vim : support to ftp explorer","script_type":"ftplugin","2":"ftplugin","summary":"support to view ftp file list","3":"support to view ftp file list","description":" I am not that  fluent in English.\r\n\r\nnetrw.vim plugin not support to view ftp file list..\r\n\r\nthis script to change from netrw.vim to that support to view ftp file list.\r\n\r\nshift + O is \"Open file\" like of explorer!!\r\n\r\nI don't change pattern so don't execute \"vim ftp:\/\/localhost\"..\r\n\r\nbut execute \"vim ftp:\/\/localhost\/\" is success!!\r\n\r\n\r\n\r\n","4":" I am not that  fluent in English.\r\n\r\nnetrw.vim plugin not support to view ftp file list..\r\n\r\nthis script to change from netrw.vim to that support to view ftp file list.\r\n\r\nshift + O is \"Open file\" like of explorer!!\r\n\r\nI don't change pattern so don't execute \"vim ftp:\/\/localhost\"..\r\n\r\nbut execute \"vim ftp:\/\/localhost\/\" is success!!\r\n\r\n\r\n\r\n","install_details":"change from pulgin\/netrw.vim to this file!!","5":"change from pulgin\/netrw.vim to this file!!","first_name":"Seongwook","6":"Seongwook","last_name":"Hwang","7":"Hwang","releases":[{"0":"1466","vim_version":"6.0","1":"6.0","script_version":"1.01","2":"1.01","version_comment":"Adding to New file Creation","3":"Adding to New file Creation","package":"netrw.vim","4":"netrw.vim","src_id":"5180","5":"5180","creation_date":"1139787642","6":"1139787642"},{"0":"1466","vim_version":"6.0","1":"6.0","script_version":"1","2":"1","version_comment":"Initial upload","3":"Initial upload","package":"netrw.vim","4":"netrw.vim","src_id":"5174","5":"5174","creation_date":"1139765845","6":"1139765845"}]},"1465":{"script_id":"1465","0":"1465","script_name":"Ant","1":"Ant","script_type":"utility","2":"utility","summary":"Ant  vim7 xml data file","3":"Ant  vim7 xml data file","description":"Ant vim7 xml data file\r\n\r\nPut in \r\n\r\n~\/.vim\/autoload\/xml\r\n\r\nLoad data with\r\n\r\n:XMLns ant\r\n\r\nfile.\r\n","4":"Ant vim7 xml data file\r\n\r\nPut in \r\n\r\n~\/.vim\/autoload\/xml\r\n\r\nLoad data with\r\n\r\n:XMLns ant\r\n\r\nfile.\r\n","install_details":"","5":"","first_name":"Mikolaj","6":"Mikolaj","last_name":"Machowski","7":"Machowski","releases":[{"0":"1465","vim_version":"6.0","1":"6.0","script_version":"1.1","2":"1.1","version_comment":"- add 'info' about EMPTY tags and REQUIRED attributes","3":"- add 'info' about EMPTY tags and REQUIRED attributes","package":"ant.vim","4":"ant.vim","src_id":"5255","5":"5255","creation_date":"1140252946","6":"1140252946"},{"0":"1465","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"ant.vim","4":"ant.vim","src_id":"5172","5":"5172","creation_date":"1139761803","6":"1139761803"}]},"1464":{"script_id":"1464","0":"1464","script_name":"moria","1":"moria","script_type":"color scheme","2":"color scheme","summary":"A color scheme for GUI supposed to be highly readable","3":"A color scheme for GUI supposed to be highly readable","description":"This color scheme contains four color schemes: two dark and two light color schemes. All highlighting groups have similar brightness. In the dark schemes bold highlighting is avoided, but used where it is reasonable. Different highlighting groups can be distinguished easily without a cluttered appearance. The highlights of all four color schemes have similar colors, but differ in contrast. \r\n\r\nThis color scheme is for the GUI version of Vim and makes only some minor tweaks for the console version.\r\n\r\nThis color scheme is optimized for Vim 7.0, but works for Vim 6.0, too.","4":"This color scheme contains four color schemes: two dark and two light color schemes. All highlighting groups have similar brightness. In the dark schemes bold highlighting is avoided, but used where it is reasonable. Different highlighting groups can be distinguished easily without a cluttered appearance. The highlights of all four color schemes have similar colors, but differ in contrast. \r\n\r\nThis color scheme is for the GUI version of Vim and makes only some minor tweaks for the console version.\r\n\r\nThis color scheme is optimized for Vim 7.0, but works for Vim 6.0, too.","install_details":"Just put it in \"~\/.vim\/colors\" or in \"<your vim directory>\\vimfiles\\colors\" on Windows. Do \":colo moria\" to apply it. If you want to install it as your default color scheme, just add \"colo moria\" to your vimrc file.\r\n\r\nThe color scheme choses the color scheme 'dark' if 'background' is set to dark and 'light' if 'background' is set to light. One can override this by setting the variable 'moria_style'. Its possible values are 'black', 'dark', 'light', and 'white'. The 'dark' scheme has #202020 as its background, the 'light' scheme #f0f0f0, the 'black' ('white') scheme has a black (white) background. If you want to use the 'white' scheme, just do\r\n\r\nlet moria_style = 'white'\r\ncolo moria\r\n\r\nin your vimrc file. Alternatively, you can set the option 'background' instead of 'moria_style' to 'dark' or 'light' and the color scheme applies either the 'dark' scheme or the 'light' one.\r\n\r\nIn gVim you can do 'Colo black', 'Colo dark', 'Colo light', and 'Colo white' to swith to the color scheme you want. In Vim (console version) these commands just swith between a dark and a light scheme.\r\n\r\nThe default colors of StatusLine, Pmenu, LineNr, ... is blue. If you like monochrome colors for these highlighting groups, there is the option 'moria_monochrome'. If the default colors do not fit to the color scheme of your desktop environment, monochrome colors will probably match better. Someone may find monochrome colors of these highlighting groups more pleasant to the eyes, too. To aktivate this option just add\r\n\r\nlet moria_monochrome = 1\r\n\r\nto your vimrc file (before 'colo moria', of course).\r\n\r\nIn the dark schemes ('black' and 'dark') bold highlights are avoided. However, some people like the highlights 'Statement', 'Type' and some other highlights to be bold. If you belong to these people, just add\r\n\r\nlet moria_fontface = 'mixed'\r\n\r\nto your vimrc file.","5":"Just put it in \"~\/.vim\/colors\" or in \"<your vim directory>\\vimfiles\\colors\" on Windows. Do \":colo moria\" to apply it. If you want to install it as your default color scheme, just add \"colo moria\" to your vimrc file.\r\n\r\nThe color scheme choses the color scheme 'dark' if 'background' is set to dark and 'light' if 'background' is set to light. One can override this by setting the variable 'moria_style'. Its possible values are 'black', 'dark', 'light', and 'white'. The 'dark' scheme has #202020 as its background, the 'light' scheme #f0f0f0, the 'black' ('white') scheme has a black (white) background. If you want to use the 'white' scheme, just do\r\n\r\nlet moria_style = 'white'\r\ncolo moria\r\n\r\nin your vimrc file. Alternatively, you can set the option 'background' instead of 'moria_style' to 'dark' or 'light' and the color scheme applies either the 'dark' scheme or the 'light' one.\r\n\r\nIn gVim you can do 'Colo black', 'Colo dark', 'Colo light', and 'Colo white' to swith to the color scheme you want. In Vim (console version) these commands just swith between a dark and a light scheme.\r\n\r\nThe default colors of StatusLine, Pmenu, LineNr, ... is blue. If you like monochrome colors for these highlighting groups, there is the option 'moria_monochrome'. If the default colors do not fit to the color scheme of your desktop environment, monochrome colors will probably match better. Someone may find monochrome colors of these highlighting groups more pleasant to the eyes, too. To aktivate this option just add\r\n\r\nlet moria_monochrome = 1\r\n\r\nto your vimrc file (before 'colo moria', of course).\r\n\r\nIn the dark schemes ('black' and 'dark') bold highlights are avoided. However, some people like the highlights 'Statement', 'Type' and some other highlights to be bold. If you belong to these people, just add\r\n\r\nlet moria_fontface = 'mixed'\r\n\r\nto your vimrc file.","first_name":"Georg","6":"Georg","last_name":"Dahn","7":"Dahn","releases":[{"0":"1464","vim_version":"7.0","1":"7.0","script_version":"2.6.5","2":"2.6.5","version_comment":"added CursorLineNr.","3":"added CursorLineNr.","package":"moria.vim","4":"moria.vim","src_id":"20786","5":"20786","creation_date":"1378892871","6":"1378892871"},{"0":"1464","vim_version":"7.0","1":"7.0","script_version":"2.6.4","2":"2.6.4","version_comment":"Changed names of colors to numbers for ctermbg and ctermfg, because names did not work on my Mac. Highlight information for ColorColumn.","3":"Changed names of colors to numbers for ctermbg and ctermfg, because names did not work on my Mac. Highlight information for ColorColumn.","package":"moria.vim","4":"moria.vim","src_id":"13617","5":"13617","creation_date":"1282133203","6":"1282133203"}]},"1463":{"script_id":"1463","0":"1463","script_name":"docbook44","1":"docbook44","script_type":"utility","2":"utility","summary":"DocBook 4.4 vim7 xml data file\n","3":"DocBook 4.4 vim7 xml data file\n","description":"Data file for Vim7 omnicompletion. Unzip and place in \r\n~\/.vim\/autoload\/xml directory. Completion will be available after \r\n\r\n:XMLns docbook44\r\n\r\ncommand.\r\n","4":"Data file for Vim7 omnicompletion. Unzip and place in \r\n~\/.vim\/autoload\/xml directory. Completion will be available after \r\n\r\n:XMLns docbook44\r\n\r\ncommand.\r\n","install_details":"Unzip and copy into ~\/.vim\/autoload\/xml directory.","5":"Unzip and copy into ~\/.vim\/autoload\/xml directory.","first_name":"Mikolaj","6":"Mikolaj","last_name":"Machowski","7":"Machowski","releases":[{"0":"1463","vim_version":"6.0","1":"6.0","script_version":"1.1","2":"1.1","version_comment":"- add 'info' about EMPTY tags and REQUIRED attributes","3":"- add 'info' about EMPTY tags and REQUIRED attributes","package":"docbook44.zip","4":"docbook44.zip","src_id":"5254","5":"5254","creation_date":"1140252174","6":"1140252174"},{"0":"1463","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"docbook44.zip","4":"docbook44.zip","src_id":"5160","5":"5160","creation_date":"1139745544","6":"1139745544"}]},"1462":{"script_id":"1462","0":"1462","script_name":"dtd2vim","1":"dtd2vim","script_type":"utility","2":"utility","summary":"Script for creation XML data file for Vim7 XML omni-completion from DTDs","3":"Script for creation XML data file for Vim7 XML omni-completion from DTDs","description":"Script for creation XML data file for Vim7 XML omni-completion from DTDs\r\nRequires: perl and perlSGML (tested against 1997Sep18 version)\r\n\r\nINSTALLATION:\r\n\r\n   Copy into your $PATH\r\n\r\nUSAGE:\r\n\r\n   dtd2vim <file.dtd> [<dialectname>]\r\n\r\nThis command will create file <file.vim> (remove .dtd extension and add .vim;\r\nother extensions will remain intact).\r\n\r\n<dialectname> (not obligatory) will be part of dictionary name and will be\r\nused as argument for :XMLns command (file name - sans extensions) have to be\r\nthe same.\r\n\r\nperlSGML and this script doesn't work with multiple files. User has to\r\nprepare single DTD file to parse all data.\r\n\r\nIn created file global variable is named g:xmldata_<dialectname>. When second\r\nargument wasn't provided 'xxxx' will be used.\r\nAfter that place file in:\r\n\r\n   ~\/.vim\/autoload\/xml\r\n\r\ndirectory. Of course it can be also global directory or other Vim data\r\nhierarchy of files. Example for  DocBook 4.4:\r\nDTD is in file docbook.dtd, call command with\r\n\r\n   dtd2vim.pl docbook.dtd docbook44\r\n\r\nPut file as:\r\n  \r\n   ~\/.vim\/autoload\/xml\/docbook44.vim\r\n\r\n Omni-completion for DocBook 4.4 files will be started with:\r\n\r\n   :XMLns docbook44\r\n\r\n command.\r\n\r\n","4":"Script for creation XML data file for Vim7 XML omni-completion from DTDs\r\nRequires: perl and perlSGML (tested against 1997Sep18 version)\r\n\r\nINSTALLATION:\r\n\r\n   Copy into your $PATH\r\n\r\nUSAGE:\r\n\r\n   dtd2vim <file.dtd> [<dialectname>]\r\n\r\nThis command will create file <file.vim> (remove .dtd extension and add .vim;\r\nother extensions will remain intact).\r\n\r\n<dialectname> (not obligatory) will be part of dictionary name and will be\r\nused as argument for :XMLns command (file name - sans extensions) have to be\r\nthe same.\r\n\r\nperlSGML and this script doesn't work with multiple files. User has to\r\nprepare single DTD file to parse all data.\r\n\r\nIn created file global variable is named g:xmldata_<dialectname>. When second\r\nargument wasn't provided 'xxxx' will be used.\r\nAfter that place file in:\r\n\r\n   ~\/.vim\/autoload\/xml\r\n\r\ndirectory. Of course it can be also global directory or other Vim data\r\nhierarchy of files. Example for  DocBook 4.4:\r\nDTD is in file docbook.dtd, call command with\r\n\r\n   dtd2vim.pl docbook.dtd docbook44\r\n\r\nPut file as:\r\n  \r\n   ~\/.vim\/autoload\/xml\/docbook44.vim\r\n\r\n Omni-completion for DocBook 4.4 files will be started with:\r\n\r\n   :XMLns docbook44\r\n\r\n command.\r\n\r\n","install_details":"Copy in your $PATH","5":"Copy in your $PATH","first_name":"Mikolaj","6":"Mikolaj","last_name":"Machowski","7":"Machowski","releases":[{"0":"1462","vim_version":"7.0","1":"7.0","script_version":"2.0","2":"2.0","version_comment":"- not all element children were properly recognized\r\n- comment out lines responsible for detection of obligatory attributes, too many false positives; uncomment on your own responsibility","3":"- not all element children were properly recognized\r\n- comment out lines responsible for detection of obligatory attributes, too many false positives; uncomment on your own responsibility","package":"dtd2vim","4":"dtd2vim","src_id":"5612","5":"5612","creation_date":"1145969696","6":"1145969696"},{"0":"1462","vim_version":"6.0","1":"6.0","script_version":"1.1","2":"1.1","version_comment":"- generate 'info' field for attributes and tags (\/> - EMPTY tag, * - required attribute)\r\n- no extension","3":"- generate 'info' field for attributes and tags (\/> - EMPTY tag, * - required attribute)\r\n- no extension","package":"dtd2vim","4":"dtd2vim","src_id":"5253","5":"5253","creation_date":"1140251973","6":"1140251973"},{"0":"1462","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"dtd2vim.pl","4":"dtd2vim.pl","src_id":"5159","5":"5159","creation_date":"1139745441","6":"1139745441"}]},"1461":{"script_id":"1461","0":"1461","script_name":"syntax\/m4.vim","1":"syntax\/m4.vim","script_type":"syntax","2":"syntax","summary":"Improved m4.vim","3":"Improved m4.vim","description":"This is an improved version of m4.vim.\r\n\r\nIf you are using the changequote() and changecom(), you can specify\r\nthe quote and comment delimiters just like vim modelines in the\r\nfollowing way:\r\n\r\n<BLANK>vim-m4-syntax: quote=[,] comment=<!--,-->:\r\n\r\nYou can specify your default delimiters at your vimrc:\r\n\r\n:let g:m4_default_quote=\"`,'\"\r\n:let g:m4_default_comment='#'\r\n\r\nAfter the file read, you can change them in the following way:\r\n\r\n:let b:m4_quote='<<,>>'\r\n:let b:m4_comment=''\r\n:call M4UpdateSyntax()\r\n","4":"This is an improved version of m4.vim.\r\n\r\nIf you are using the changequote() and changecom(), you can specify\r\nthe quote and comment delimiters just like vim modelines in the\r\nfollowing way:\r\n\r\n<BLANK>vim-m4-syntax: quote=[,] comment=<!--,-->:\r\n\r\nYou can specify your default delimiters at your vimrc:\r\n\r\n:let g:m4_default_quote=\"`,'\"\r\n:let g:m4_default_comment='#'\r\n\r\nAfter the file read, you can change them in the following way:\r\n\r\n:let b:m4_quote='<<,>>'\r\n:let b:m4_comment=''\r\n:call M4UpdateSyntax()\r\n","install_details":"","5":"","first_name":"Shinra","6":"Shinra","last_name":"AIDA","7":"AIDA","releases":[{"0":"1461","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"m4.vim","4":"m4.vim","src_id":"5158","5":"5158","creation_date":"1139711817","6":"1139711817"}]},"1460":{"script_id":"1460","0":"1460","script_name":"glark.vim","1":"glark.vim","script_type":"utility","2":"utility","summary":"a wrapper for the glark command (a grep-like utility)","3":"a wrapper for the glark command (a grep-like utility)","description":"This plugin provides one wrapper command for the glark command:\r\n\r\n    :Glark <args>\r\n\r\nExample: Find occurrences of \"foo\" and \"bar\" within 3 lines and \r\ndisplay 2 lines context:\r\n\r\n    :Glark -r -C 2 --and=3 foo bar *\r\n\r\nThe arguments are passed to the glark command.\r\n\r\nIt displays the output of the glark command (see below) in a window, \r\ndoes some highlighting and provides some handy key maps.\r\n\r\nIf you don't want to display context information, you're probably better\r\noff by setting 'grepprg' to \"glark --grep\".\r\n\r\nBe also aware that this plugin doesn't use vim's quickfix functionality\r\nas most grep plugins do.","4":"This plugin provides one wrapper command for the glark command:\r\n\r\n    :Glark <args>\r\n\r\nExample: Find occurrences of \"foo\" and \"bar\" within 3 lines and \r\ndisplay 2 lines context:\r\n\r\n    :Glark -r -C 2 --and=3 foo bar *\r\n\r\nThe arguments are passed to the glark command.\r\n\r\nIt displays the output of the glark command (see below) in a window, \r\ndoes some highlighting and provides some handy key maps.\r\n\r\nIf you don't want to display context information, you're probably better\r\noff by setting 'grepprg' to \"glark --grep\".\r\n\r\nBe also aware that this plugin doesn't use vim's quickfix functionality\r\nas most grep plugins do.","install_details":"Unzip the archive to ~\/.vim or %HOME%\/vimfiles.\r\n\r\nYou also need the glark command of course. glark (a ruby-based, \r\ngrep-like utility) was made by Jeff Pace and can be downloaded from:\r\n\r\n    http:\/\/glark.sourceforge.net\r\n\r\nMake sure your version is >= 1.7.5.\r\n\r\n\r\nAlso available via git\r\nhttp:\/\/github.com\/tomtom\/vimtlib\/tree\/master\r\n","5":"Unzip the archive to ~\/.vim or %HOME%\/vimfiles.\r\n\r\nYou also need the glark command of course. glark (a ruby-based, \r\ngrep-like utility) was made by Jeff Pace and can be downloaded from:\r\n\r\n    http:\/\/glark.sourceforge.net\r\n\r\nMake sure your version is >= 1.7.5.\r\n\r\n\r\nAlso available via git\r\nhttp:\/\/github.com\/tomtom\/vimtlib\/tree\/master\r\n","first_name":"Tom","6":"Tom","last_name":"Link","7":"Link","releases":[{"0":"1460","vim_version":"6.0","1":"6.0","script_version":"0.2a","2":"0.2a","version_comment":"Forgot to add the ftplugin","3":"Forgot to add the ftplugin","package":"glark.zip","4":"glark.zip","src_id":"5503","5":"5503","creation_date":"1143793535","6":"1143793535"},{"0":"1460","vim_version":"6.0","1":"6.0","script_version":"0.2","2":"0.2","version_comment":"- File completion for the :Glark command\r\n- Support folds\r\n- Use --explain option to construct @\/ pattern\r\n- Bind double click to open file\r\n- GlarkUpdate() (bound to 'u')\r\n- GlarkKeys() is called from ftplugin -> glark is a proper filetype now\r\n- If g:glarkHeight is 0, the window is set to &lines\/2 at runtime.\r\n- Unset wrap before jumping to a line in the document\r\n","3":"- File completion for the :Glark command\r\n- Support folds\r\n- Use --explain option to construct @\/ pattern\r\n- Bind double click to open file\r\n- GlarkUpdate() (bound to 'u')\r\n- GlarkKeys() is called from ftplugin -> glark is a proper filetype now\r\n- If g:glarkHeight is 0, the window is set to &lines\/2 at runtime.\r\n- Unset wrap before jumping to a line in the document\r\n","package":"glark.zip","4":"glark.zip","src_id":"5494","5":"5494","creation_date":"1143620588","6":"1143620588"},{"0":"1460","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"glark.zip","4":"glark.zip","src_id":"5068","5":"5068","creation_date":"1139222104","6":"1139222104"}]},"1459":{"script_id":"1459","0":"1459","script_name":"moin.vim","1":"moin.vim","script_type":"syntax","2":"syntax","summary":"Syntax file for MoinMoin wiki text","3":"Syntax file for MoinMoin wiki text","description":"This provides syntax highlighting for MoinMoin wiki text (http:\/\/moinmoin.wikiwikiweb.de\/).\r\n\r\nThe homepage for moin.vim is http:\/\/moinmoin.wikiwikiweb.de\/VimHighlighting\r\n\r\nmoin.vim is maintained by Michael Lamertz <mike@perl-ronin.de>","4":"This provides syntax highlighting for MoinMoin wiki text (http:\/\/moinmoin.wikiwikiweb.de\/).\r\n\r\nThe homepage for moin.vim is http:\/\/moinmoin.wikiwikiweb.de\/VimHighlighting\r\n\r\nmoin.vim is maintained by Michael Lamertz <mike@perl-ronin.de>","install_details":"","5":"","first_name":"David","6":"David","last_name":"O'Callaghan","7":"O'Callaghan","releases":[{"0":"1459","vim_version":"6.0","1":"6.0","script_version":"1.4.1","2":"1.4.1","version_comment":"Improved WikiWord highlighting thanks to Tony Garland. Reclassified Moin pragma as Define rather than Comment.","3":"Improved WikiWord highlighting thanks to Tony Garland. Reclassified Moin pragma as Define rather than Comment.","package":"moin.vim","4":"moin.vim","src_id":"5804","5":"5804","creation_date":"1149563785","6":"1149563785"},{"0":"1459","vim_version":"6.0","1":"6.0","script_version":"1.4","2":"1.4","version_comment":"Initial upload","3":"Initial upload","package":"moin.vim","4":"moin.vim","src_id":"5062","5":"5062","creation_date":"1139191005","6":"1139191005"}]},"1458":{"script_id":"1458","0":"1458","script_name":"Grape Color","1":"Grape Color","script_type":"color scheme","2":"color scheme","summary":"Light colorscheme","3":"Light colorscheme","description":"Grape red on light background. GUI only. Made in monitor with low brightness (10%), so it will be pale if you use brightness > 50%","4":"Grape red on light background. GUI only. Made in monitor with low brightness (10%), so it will be pale if you use brightness > 50%","install_details":"","5":"","first_name":"Char","6":"Char","last_name":"Only","7":"Only","releases":[{"0":"1458","vim_version":"5.7","1":"5.7","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"grape.vim","4":"grape.vim","src_id":"5061","5":"5061","creation_date":"1139112625","6":"1139112625"}]},"1457":{"script_id":"1457","0":"1457","script_name":"CycleColor","1":"CycleColor","script_type":"utility","2":"utility","summary":"Cycles through available colorschemes","3":"Cycles through available colorschemes","description":"This script provides a function, CycleColor (which is mapped to F4), to cycle through (almost) all available colorschemes.  It includes colorschemes from all \\\"colors\\\" subdirectories in the runtimepath.\r\n\r\nBecause the script uses \\\":colorscheme\\\" rather than \\\":source\\\" to set the colorscheme, if there are two files with the same name in different directories in rtp, only the first one will be used (thus \\\"almost\\\" above).\r\n\r\nThe script was inspired by a one-liner by Tim Chase.","4":"This script provides a function, CycleColor (which is mapped to F4), to cycle through (almost) all available colorschemes.  It includes colorschemes from all \\\"colors\\\" subdirectories in the runtimepath.\r\n\r\nBecause the script uses \\\":colorscheme\\\" rather than \\\":source\\\" to set the colorscheme, if there are two files with the same name in different directories in rtp, only the first one will be used (thus \\\"almost\\\" above).\r\n\r\nThe script was inspired by a one-liner by Tim Chase.","install_details":"Place this script in your $HOME\/.vim\/plugin directory (or Windows equivalent).","5":"Place this script in your $HOME\/.vim\/plugin directory (or Windows equivalent).","first_name":"Marvin","6":"Marvin","last_name":"Renich","7":"Renich","releases":[{"0":"1457","vim_version":"6.0","1":"6.0","script_version":"1.1","2":"1.1","version_comment":"Allows cycling backward (F3) and forward (F4) through the list of colorschemes.","3":"Allows cycling backward (F3) and forward (F4) through the list of colorschemes.","package":"cyclecolor.vim","4":"cyclecolor.vim","src_id":"5965","5":"5965","creation_date":"1153231248","6":"1153231248"},{"0":"1457","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"cyclecolor.vim","4":"cyclecolor.vim","src_id":"5048","5":"5048","creation_date":"1138956192","6":"1138956192"}]},"1456":{"script_id":"1456","0":"1456","script_name":"copypath.vim","1":"copypath.vim","script_type":"utility","2":"utility","summary":"Copy current editing file path to clipboard.","3":"Copy current editing file path to clipboard.","description":"Usage:\r\n   This script adds two new command \":CopyPath\" and \":CopyFileName\".\r\n   You can use the \":CopyPath\" command to copy file path to clipboard,\r\n   and you can use the \":CopyFileName\" command to copy file name to clipboard.\r\n\r\n   :CopyPath\r\n       copy current editing file full path to clipboard.\r\n       And, if you set g:copypath_copy_to_unnamed_register option to 1 then,\r\n       copy file full path to unnamed register too.\r\n       Default, not copy to unnamed register.\r\n\r\n   :CopyFileName\r\n       copy current editing file name to clipboard.\r\n       And, if you set g:copypath_copy_to_unnamed_register option to 1 then,\r\n       copy file name to unnamed register too.\r\n       Default, not copy to unnamed register.\r\n\r\nConfiguration:\r\n   g:copypath_copy_to_unnamed_register\r\n      set this option value to 1 then, copy file path and name to unnamed register too.\r\n  >\r\n      let g:copypath_copy_to_unnamed_register = 1\r\n  <\r\n\r\nNote:\r\n   o  To run this script, Vim needs to be compiled with \"+clipboard\" option.\r\n","4":"Usage:\r\n   This script adds two new command \":CopyPath\" and \":CopyFileName\".\r\n   You can use the \":CopyPath\" command to copy file path to clipboard,\r\n   and you can use the \":CopyFileName\" command to copy file name to clipboard.\r\n\r\n   :CopyPath\r\n       copy current editing file full path to clipboard.\r\n       And, if you set g:copypath_copy_to_unnamed_register option to 1 then,\r\n       copy file full path to unnamed register too.\r\n       Default, not copy to unnamed register.\r\n\r\n   :CopyFileName\r\n       copy current editing file name to clipboard.\r\n       And, if you set g:copypath_copy_to_unnamed_register option to 1 then,\r\n       copy file name to unnamed register too.\r\n       Default, not copy to unnamed register.\r\n\r\nConfiguration:\r\n   g:copypath_copy_to_unnamed_register\r\n      set this option value to 1 then, copy file path and name to unnamed register too.\r\n  >\r\n      let g:copypath_copy_to_unnamed_register = 1\r\n  <\r\n\r\nNote:\r\n   o  To run this script, Vim needs to be compiled with \"+clipboard\" option.\r\n","install_details":"1. Unzip copypath.zip ,\r\n   and extract there to your vim runtimepath directory ,\r\n   $HOME\/vimfiles\/plugin or $HOME\/.vim\/plugin directory directory.\r\n\r\n   Refer to ':help add-plugin', ':help add-global-plugin' and ':help runtimepath'\r\n   for more details about Vim plugins.\r\n\r\n2. Restart Vim.\r\n3. To run this script, Vim needs to be compiled with \"+clipboard\" option.\r\n","5":"1. Unzip copypath.zip ,\r\n   and extract there to your vim runtimepath directory ,\r\n   $HOME\/vimfiles\/plugin or $HOME\/.vim\/plugin directory directory.\r\n\r\n   Refer to ':help add-plugin', ':help add-global-plugin' and ':help runtimepath'\r\n   for more details about Vim plugins.\r\n\r\n2. Restart Vim.\r\n3. To run this script, Vim needs to be compiled with \"+clipboard\" option.\r\n","first_name":"omi","6":"omi","last_name":"taku","7":"taku","releases":[{"0":"1456","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"o  change script package file format to zip format.\r\no  unnamed register copy option is added.","3":"o  change script package file format to zip format.\r\no  unnamed register copy option is added.","package":"copypath.zip","4":"copypath.zip","src_id":"11907","5":"11907","creation_date":"1260953181","6":"1260953181"},{"0":"1456","vim_version":"6.0","1":"6.0","script_version":"0.1.2","2":"0.1.2","version_comment":"document is updated.","3":"document is updated.","package":"copypath.vim","4":"copypath.vim","src_id":"5060","5":"5060","creation_date":"1139011140","6":"1139011140"},{"0":"1456","vim_version":"6.0","1":"6.0","script_version":"0.1.1","2":"0.1.1","version_comment":"fix bug.","3":"fix bug.","package":"copypath.vim","4":"copypath.vim","src_id":"5035","5":"5035","creation_date":"1138917400","6":"1138917400"},{"0":"1456","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"copypath.vim","4":"copypath.vim","src_id":"5034","5":"5034","creation_date":"1138913752","6":"1138913752"}]},"1455":{"script_id":"1455","0":"1455","script_name":"VCard syntax","1":"VCard syntax","script_type":"syntax","2":"syntax","summary":"Vcard syntax for vcf file.","3":"Vcard syntax for vcf file.","description":"I've developed simple syntax file so I'm able to see vcard from Plaxo in colour. It improves the readability of such file.","4":"I've developed simple syntax file so I'm able to see vcard from Plaxo in colour. It improves the readability of such file.","install_details":"Upload to syntax folder. Possibly add item to menu that calls this syntax.\r\n:cal SetSyn(\"vcard\")","5":"Upload to syntax folder. Possibly add item to menu that calls this syntax.\r\n:cal SetSyn(\"vcard\")","first_name":"Lubomir","6":"Lubomir","last_name":"Husar","7":"Husar","releases":[{"0":"1455","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"vcard.vim","4":"vcard.vim","src_id":"5025","5":"5025","creation_date":"1138861350","6":"1138861350"}]},"1454":{"script_id":"1454","0":"1454","script_name":"baycomb","1":"baycomb","script_type":"color scheme","2":"color scheme","summary":"An intuitive Color Scheme (w\/ dark & light colors)","3":"An intuitive Color Scheme (w\/ dark & light colors)","description":"This is a dark scheme consisting primarily of red\/orange & green\/blue\/purple, with support for Terminal and 7.0 users. \r\nBoth the original dark and a light version is included, be sure to specify the version:\r\n  :set background=dark   or   :set background=light\r\n\r\nColors are laid out intuitively, such that:\r\n         action\/structure syntax is tan (Control Structure: red; Commands: orange; Operators: tannish yellow)\r\n         variables\/values are blue (Identifier: greenish blue; Type: greyish blue; Constants: blue)                                   \r\n         text\/special text is white\/yellow (Normal: white; Title: golden; Underline: yellow; Special: brown)\r\nIt works very well for me coding in Html, ASP, and Perl.\r\n\r\nScreenshots (v2.1): [removed from image host, I'll need to resubmit some]\r\n\r\nRecommended programming fonts:\r\n  ProFont, Proggy Fonts, Dina, or Envy Code A (downloadable), as well as Lucida Console or Terminal\r\nSet :set linespace=0  to your preferred line spread (default is 1). \r\n\r\nComments and suggestions:               axs221@gmail.com ","4":"This is a dark scheme consisting primarily of red\/orange & green\/blue\/purple, with support for Terminal and 7.0 users. \r\nBoth the original dark and a light version is included, be sure to specify the version:\r\n  :set background=dark   or   :set background=light\r\n\r\nColors are laid out intuitively, such that:\r\n         action\/structure syntax is tan (Control Structure: red; Commands: orange; Operators: tannish yellow)\r\n         variables\/values are blue (Identifier: greenish blue; Type: greyish blue; Constants: blue)                                   \r\n         text\/special text is white\/yellow (Normal: white; Title: golden; Underline: yellow; Special: brown)\r\nIt works very well for me coding in Html, ASP, and Perl.\r\n\r\nScreenshots (v2.1): [removed from image host, I'll need to resubmit some]\r\n\r\nRecommended programming fonts:\r\n  ProFont, Proggy Fonts, Dina, or Envy Code A (downloadable), as well as Lucida Console or Terminal\r\nSet :set linespace=0  to your preferred line spread (default is 1). \r\n\r\nComments and suggestions:               axs221@gmail.com ","install_details":"Add :colo baycomb to your Gvimrc\/Vimrc, after moving baycomb to $vimruntime\/colors\/\r\n\r\nBE SURE to set background to dark to get the original dark colors.\r\n:set background=dark    or    :set background=light  in your Vimrc","5":"Add :colo baycomb to your Gvimrc\/Vimrc, after moving baycomb to $vimruntime\/colors\/\r\n\r\nBE SURE to set background to dark to get the original dark colors.\r\n:set background=dark    or    :set background=light  in your Vimrc","first_name":"Shawn","6":"Shawn","last_name":"Axsom","7":"Axsom","releases":[{"0":"1454","vim_version":"7.0","1":"7.0","script_version":"3.0","2":"3.0","version_comment":"Updated Color Terminal colors to more closely match the GUI colors in GVim","3":"Updated Color Terminal colors to more closely match the GUI colors in GVim","package":"baycomb.vim","4":"baycomb.vim","src_id":"22968","5":"22968","creation_date":"1425225145","6":"1425225145"},{"0":"1454","vim_version":"7.0","1":"7.0","script_version":"2.4","2":"2.4","version_comment":"New colors for Diff mode","3":"New colors for Diff mode","package":"baycomb.vim","4":"baycomb.vim","src_id":"5795","5":"5795","creation_date":"1149322364","6":"1149322364"},{"0":"1454","vim_version":"7.0","1":"7.0","script_version":"2.3","2":"2.3","version_comment":"Changed Comments to green, several changed to the Terminal. Thanks to Bob Lied for the suggestions.","3":"Changed Comments to green, several changed to the Terminal. Thanks to Bob Lied for the suggestions.","package":"baycomb.vim","4":"baycomb.vim","src_id":"5680","5":"5680","creation_date":"1147356971","6":"1147356971"},{"0":"1454","vim_version":"7.0","1":"7.0","script_version":"2.2","2":"2.2","version_comment":"Some adjustments mixing the old with the new.","3":"Some adjustments mixing the old with the new.","package":"baycomb.vim","4":"baycomb.vim","src_id":"5519","5":"5519","creation_date":"1144154459","6":"1144154459"},{"0":"1454","vim_version":"6.0","1":"6.0","script_version":"VimRC","2":"VimRC","version_comment":"My current VimRC, hopefully someone will find it useful.","3":"My current VimRC, hopefully someone will find it useful.","package":"_vimrc","4":"_vimrc","src_id":"5441","5":"5441","creation_date":"1142457814","6":"1142457814"},{"0":"1454","vim_version":"6.0","1":"6.0","script_version":"2.1g","2":"2.1g","version_comment":"Fixed a Terminal bug from a background not being set.","3":"Fixed a Terminal bug from a background not being set.","package":"baycomb.vim","4":"baycomb.vim","src_id":"5430","5":"5430","creation_date":"1142331936","6":"1142331936"},{"0":"1454","vim_version":"6.0","1":"6.0","script_version":"2.1f","2":"2.1f","version_comment":"Minor changes.","3":"Minor changes.","package":"baycomb.vim","4":"baycomb.vim","src_id":"5428","5":"5428","creation_date":"1142290031","6":"1142290031"},{"0":"1454","vim_version":"6.0","1":"6.0","script_version":"2.1e","2":"2.1e","version_comment":"Added Terminal and GUI colors from the bayQua color scheme for when background is set to \"light\".","3":"Added Terminal and GUI colors from the bayQua color scheme for when background is set to \"light\".","package":"baycomb.vim","4":"baycomb.vim","src_id":"5423","5":"5423","creation_date":"1142273418","6":"1142273418"},{"0":"1454","vim_version":"6.0","1":"6.0","script_version":"2.1d","2":"2.1d","version_comment":"More changes to various Terminal colors to lower overall brightness & fatigue. Added Terminal colors for MatchParen and TabLine.","3":"More changes to various Terminal colors to lower overall brightness & fatigue. Added Terminal colors for MatchParen and TabLine.","package":"baycomb.vim","4":"baycomb.vim","src_id":"5416","5":"5416","creation_date":"1142127173","6":"1142127173"},{"0":"1454","vim_version":"6.0","1":"6.0","script_version":"2.1c","2":"2.1c","version_comment":"Minor adjustments to the new Terminal.","3":"Minor adjustments to the new Terminal.","package":"baycomb.vim","4":"baycomb.vim","src_id":"5410","5":"5410","creation_date":"1141999146","6":"1141999146"},{"0":"1454","vim_version":"6.0","1":"6.0","script_version":"2.1","2":"2.1","version_comment":"Updated Terminal colors to flow better together and match the latest changes in GUI. Now uses more yellow\/cyan than red\/blue, since it appears more readable in a Windows terminal. Also changed comments to black on darkgreen. See new Terminal Screenshot.","3":"Updated Terminal colors to flow better together and match the latest changes in GUI. Now uses more yellow\/cyan than red\/blue, since it appears more readable in a Windows terminal. Also changed comments to black on darkgreen. See new Terminal Screenshot.","package":"baycomb.vim","4":"baycomb.vim","src_id":"5405","5":"5405","creation_date":"1141991517","6":"1141991517"},{"0":"1454","vim_version":"6.0","1":"6.0","script_version":"2.0","2":"2.0","version_comment":"Many changes (see new screenshot)","3":"Many changes (see new screenshot)","package":"baycomb.vim","4":"baycomb.vim","src_id":"5370","5":"5370","creation_date":"1141567808","6":"1141567808"},{"0":"1454","vim_version":"6.0","1":"6.0","script_version":"1.9","2":"1.9","version_comment":"Changed Identifier and Operator to better blend in.","3":"Changed Identifier and Operator to better blend in.","package":"baycomb.vim","4":"baycomb.vim","src_id":"5366","5":"5366","creation_date":"1141557795","6":"1141557795"},{"0":"1454","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"baycomb.vim","4":"baycomb.vim","src_id":"5024","5":"5024","creation_date":"1138840604","6":"1138840604"}]},"1453":{"script_id":"1453","0":"1453","script_name":"cecscope","1":"cecscope","script_type":"utility","2":"utility","summary":"command and menu driven cscope interface","3":"command and menu driven cscope interface","description":"    (requires vim7.0aa snapshot #188 or later)\r\nDrChip's cscope interface supports commands:\r\n\r\n    CS     [cdefgist]   : cscope\r\n    CSl[!] [cdefgist]   : locallist style (! restores efm)\r\n    CSs[!] [cdefgist]   : split window and use cscope\r\n\r\n    !            split vertically\r\n    c (calls)    find functions calling function under cursor\r\n    d (called)   find functions called by function under cursor\r\n    e (egrep)    egrep search for the word under cursor\r\n    f (file)     open the file named under cursor\r\n    g (global)   find global definition(s) of word under cursor\r\n    i (includes) find files that #include file named under cursor\r\n    s (symbol)   find all references to the word under cursor\r\n    t (text)     find all instances of the word under cursor\r\n\r\nand menus which allow you to do all the above.  Includes help\r\nand a tutorial.\r\n\r\n(alpha\/beta version available at http:\/\/www.drchip.org\/astronaut\/vim\/index.html#CECSCOPE)\r\n","4":"    (requires vim7.0aa snapshot #188 or later)\r\nDrChip's cscope interface supports commands:\r\n\r\n    CS     [cdefgist]   : cscope\r\n    CSl[!] [cdefgist]   : locallist style (! restores efm)\r\n    CSs[!] [cdefgist]   : split window and use cscope\r\n\r\n    !            split vertically\r\n    c (calls)    find functions calling function under cursor\r\n    d (called)   find functions called by function under cursor\r\n    e (egrep)    egrep search for the word under cursor\r\n    f (file)     open the file named under cursor\r\n    g (global)   find global definition(s) of word under cursor\r\n    i (includes) find files that #include file named under cursor\r\n    s (symbol)   find all references to the word under cursor\r\n    t (text)     find all instances of the word under cursor\r\n\r\nand menus which allow you to do all the above.  Includes help\r\nand a tutorial.\r\n\r\n(alpha\/beta version available at http:\/\/www.drchip.org\/astronaut\/vim\/index.html#CECSCOPE)\r\n","install_details":"vim cecscope.vba.gz\r\n:so %\r\n:q\r\n\r\n(your system needs to have gunzip on it to decompress the vimball)\r\n(for Windows, see  :help vimball-windows  on where one might obtain gunzip for Windows)\r\n","5":"vim cecscope.vba.gz\r\n:so %\r\n:q\r\n\r\n(your system needs to have gunzip on it to decompress the vimball)\r\n(for Windows, see  :help vimball-windows  on where one might obtain gunzip for Windows)\r\n","first_name":"Charles","6":"Charles","last_name":"Campbell","7":"Campbell","releases":[{"0":"1453","vim_version":"7.0","1":"7.0","script_version":"4","2":"4","version_comment":"Security enhanced with fnameescape(), so cecscope now needs vim 7.2.\r\nHelp menu fixed.\r\n","3":"Security enhanced with fnameescape(), so cecscope now needs vim 7.2.\r\nHelp menu fixed.\r\n","package":"cecscope.vba.gz","4":"cecscope.vba.gz","src_id":"9492","5":"9492","creation_date":"1226509218","6":"1226509218"},{"0":"1453","vim_version":"7.0","1":"7.0","script_version":"3","2":"3","version_comment":":CS now supports cscope.out database searching; if the current directory or a parent directory up to but not including the $HOME directory has a cscope.out database, it'll be used.  This provides better support to projects with their multiple subdirectories.","3":":CS now supports cscope.out database searching; if the current directory or a parent directory up to but not including the $HOME directory has a cscope.out database, it'll be used.  This provides better support to projects with their multiple subdirectories.","package":"cecscope.vba.gz","4":"cecscope.vba.gz","src_id":"8140","5":"8140","creation_date":"1199799249","6":"1199799249"},{"0":"1453","vim_version":"6.0","1":"6.0","script_version":"2","2":"2","version_comment":":CSR included (cscope reset)\r\nChanged commands to :CSH, :CSS, :CSS!, :CSL to make it easier to type","3":":CSR included (cscope reset)\r\nChanged commands to :CSH, :CSS, :CSS!, :CSL to make it easier to type","package":"cecscope.vim.gz","4":"cecscope.vim.gz","src_id":"5189","5":"5189","creation_date":"1139812687","6":"1139812687"},{"0":"1453","vim_version":"6.0","1":"6.0","script_version":"1","2":"1","version_comment":"Initial upload","3":"Initial upload","package":"cecscope.vim.gz","4":"cecscope.vim.gz","src_id":"5012","5":"5012","creation_date":"1138611878","6":"1138611878"}]},"1452":{"script_id":"1452","0":"1452","script_name":"testing","1":"testing","script_type":"syntax","2":"syntax","summary":"testing uploads","3":"testing uploads","description":"testing description","4":"testing description","install_details":"","5":"","first_name":"juan","6":"juan","last_name":"perez","7":"perez","releases":[{"0":"1452","vim_version":"6.0","1":"6.0","script_version":"1.2","2":"1.2","version_comment":"asasasa","3":"asasasa","package":"testaaaing.txt","4":"testaaaing.txt","src_id":"5010","5":"5010","creation_date":"1138558601","6":"1138558601"}]},"1451":{"script_id":"1451","0":"1451","script_name":"svn_commit","1":"svn_commit","script_type":"ftplugin","2":"ftplugin","summary":"read in aborted subversion commit log messages","3":"read in aborted subversion commit log messages","description":"This plugin will look in the current directory for aborted subversion commit log messages, and then read in the newest one to your current commit log.\r\n\r\nThis saves you having to remember what the log files are called, or importing it yourself and tidying up the log message manually.\r\n\r\nhttp:\/\/atlee.ca\/blog\/software\/svn-commit\/","4":"This plugin will look in the current directory for aborted subversion commit log messages, and then read in the newest one to your current commit log.\r\n\r\nThis saves you having to remember what the log files are called, or importing it yourself and tidying up the log message manually.\r\n\r\nhttp:\/\/atlee.ca\/blog\/software\/svn-commit\/","install_details":"Download and put into your ~\/.vim\/ftplugin directory","5":"Download and put into your ~\/.vim\/ftplugin directory","first_name":"Chris","6":"Chris","last_name":"AtLee","7":"AtLee","releases":[{"0":"1451","vim_version":"6.0","1":"6.0","script_version":"0.2","2":"0.2","version_comment":"Applied a patch sent in by a user to 'set modified' if reading a previous svn-commit.tmp file.\r\n\r\nThis allows you to use ':x' to commit if the log message is what you want.","3":"Applied a patch sent in by a user to 'set modified' if reading a previous svn-commit.tmp file.\r\n\r\nThis allows you to use ':x' to commit if the log message is what you want.","package":"svn_commit.vim","4":"svn_commit.vim","src_id":"5700","5":"5700","creation_date":"1147678734","6":"1147678734"},{"0":"1451","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"svn_commit.vim","4":"svn_commit.vim","src_id":"5007","5":"5007","creation_date":"1138373403","6":"1138373403"}]},"1450":{"script_id":"1450","0":"1450","script_name":"VHDL indent ('93 syntax)","1":"VHDL indent ('93 syntax)","script_type":"indent","2":"indent","summary":"Revised VHDL indent file","3":"Revised VHDL indent file","description":"This VHDL indent file will help indent a VHDL file in Vim with the operator '='.\r\nTo indent the whole file, do 'gg=G'. See \":help =\"\r\n\r\nPrevious good work has been done by N. J. Heo & Janez Strangelj (see vimscript#766). However, Heo & Strangelj's script was lacking in terms of alignment for assignment statements that continued on for more than one line, among other things.\r\n\r\nThis script covers a broad set of VHDL keywords, and performs proper alignment on port\/generic mappings & on the RHS of assignment operators.\r\n\r\nTo disable alignment of generic\/port mappings:\r\n  :let g:vhdl_indent_genportmap = 0\r\n\r\nTo disable alignment of right-hand side assignment \"<=\" statements:\r\n  :let g:vhdl_indent_rhsassign = 0\r\n\r\nThe two options above are enabled by default. To change them, place either of the above in \".vimrc\".\r\n\r\nIn later versions of Vim 7.1 and above, access help documentation with:\r\n  :help ft-vhdl-indent\r\n\r\nPlease send feedback and bug reports via e-mail. Much appreciated :)","4":"This VHDL indent file will help indent a VHDL file in Vim with the operator '='.\r\nTo indent the whole file, do 'gg=G'. See \":help =\"\r\n\r\nPrevious good work has been done by N. J. Heo & Janez Strangelj (see vimscript#766). However, Heo & Strangelj's script was lacking in terms of alignment for assignment statements that continued on for more than one line, among other things.\r\n\r\nThis script covers a broad set of VHDL keywords, and performs proper alignment on port\/generic mappings & on the RHS of assignment operators.\r\n\r\nTo disable alignment of generic\/port mappings:\r\n  :let g:vhdl_indent_genportmap = 0\r\n\r\nTo disable alignment of right-hand side assignment \"<=\" statements:\r\n  :let g:vhdl_indent_rhsassign = 0\r\n\r\nThe two options above are enabled by default. To change them, place either of the above in \".vimrc\".\r\n\r\nIn later versions of Vim 7.1 and above, access help documentation with:\r\n  :help ft-vhdl-indent\r\n\r\nPlease send feedback and bug reports via e-mail. Much appreciated :)","install_details":"Copy \"vhdl.vim\" to either one of these indent directories:\r\n  $HOME\/.vim\/indent\/\r\n  $VIMRUNTIME\/indent\/\r\n\r\nPlace this line in \".vimrc\":\r\n  :filetype indent on\r\n\r\n","5":"Copy \"vhdl.vim\" to either one of these indent directories:\r\n  $HOME\/.vim\/indent\/\r\n  $VIMRUNTIME\/indent\/\r\n\r\nPlace this line in \".vimrc\":\r\n  :filetype indent on\r\n\r\n","first_name":"Gerald","6":"Gerald","last_name":"Lai","7":"Lai","releases":[{"0":"1450","vim_version":"7.0","1":"7.0","script_version":"1.62","2":"1.62","version_comment":"Fix regression indenting type records\r\n\r\nIncorporate shiftwidth() patch. Thanks Takuya Fujiwara!","3":"Fix regression indenting type records\r\n\r\nIncorporate shiftwidth() patch. Thanks Takuya Fujiwara!","package":"vhdl.vim","4":"vhdl.vim","src_id":"25611","5":"25611","creation_date":"1508309966","6":"1508309966"},{"0":"1450","vim_version":"7.0","1":"7.0","script_version":"1.60","2":"1.60","version_comment":"Fix indentation of set of generic declarations.\r\nPatch provided by Jacko Dirks.\r\n\r\nFix for port maps with bit-select in first port\r\nCurrent version does not indent the following code\r\ncomp_inst : comp\r\nport map (\r\na_in(0) => a, -- or a_in(1 downto 0) => a,\r\n...\r\nPatch provided by robin.\r\n\r\nThanks to both Jacko, and robin!","3":"Fix indentation of set of generic declarations.\r\nPatch provided by Jacko Dirks.\r\n\r\nFix for port maps with bit-select in first port\r\nCurrent version does not indent the following code\r\ncomp_inst : comp\r\nport map (\r\na_in(0) => a, -- or a_in(1 downto 0) => a,\r\n...\r\nPatch provided by robin.\r\n\r\nThanks to both Jacko, and robin!","package":"vhdl.vim","4":"vhdl.vim","src_id":"24292","5":"24292","creation_date":"1464563432","6":"1464563432"},{"0":"1450","vim_version":"7.0","1":"7.0","script_version":"1.58","2":"1.58","version_comment":"PORT-like indentation of PROCEDURE arguments\r\nBetter indenting for BEGIN and ELSIF\/ELSE\/END IF, etc.\r\n\r\nThanks to Tjaart Opperman!","3":"PORT-like indentation of PROCEDURE arguments\r\nBetter indenting for BEGIN and ELSIF\/ELSE\/END IF, etc.\r\n\r\nThanks to Tjaart Opperman!","package":"vhdl.vim","4":"vhdl.vim","src_id":"16596","5":"16596","creation_date":"1317179880","6":"1317179880"},{"0":"1450","vim_version":"7.0","1":"7.0","script_version":"1.56","2":"1.56","version_comment":"Minor fix to correctly indent type record \/ units.\r\nBetter indenting for END;\r\n\r\nThanks to Angel Ezquerra.","3":"Minor fix to correctly indent type record \/ units.\r\nBetter indenting for END;\r\n\r\nThanks to Angel Ezquerra.","package":"vhdl.vim","4":"vhdl.vim","src_id":"13320","5":"13320","creation_date":"1278839106","6":"1278839106"},{"0":"1450","vim_version":"7.0","1":"7.0","script_version":"1.54","2":"1.54","version_comment":"Minor bug fix over v1.53","3":"Minor bug fix over v1.53","package":"vhdl.vim","4":"vhdl.vim","src_id":"7518","5":"7518","creation_date":"1187340770","6":"1187340770"},{"0":"1450","vim_version":"7.0","1":"7.0","script_version":"1.53","2":"1.53","version_comment":"Full-line comments (lines that begin with \"--\") are aligned with the very previous line only if a whitespace follows after \"--\". In other words, the character that comes after \"--\" determines alignment.\r\n\r\nThis allows commented code to be distinguished from real comments.\r\n\r\nThanks to Christian Brehm again for the idea!","3":"Full-line comments (lines that begin with \"--\") are aligned with the very previous line only if a whitespace follows after \"--\". In other words, the character that comes after \"--\" determines alignment.\r\n\r\nThis allows commented code to be distinguished from real comments.\r\n\r\nThanks to Christian Brehm again for the idea!","package":"vhdl.vim","4":"vhdl.vim","src_id":"7509","5":"7509","creation_date":"1187269604","6":"1187269604"},{"0":"1450","vim_version":"7.0","1":"7.0","script_version":"1.52","2":"1.52","version_comment":"Critical bug FIXED: Alignment of code failed on indents with tabs. Realized that stridx() and matchend() read a tab as 1 space, instead of the correct &tabstop number of spaces. Thanks to Christian Brehm!\r\n\r\nRenamed options to g:vhdl_indent_genportmap & g:vhdl_indent_rhsassign, to be consistent with naming convention.","3":"Critical bug FIXED: Alignment of code failed on indents with tabs. Realized that stridx() and matchend() read a tab as 1 space, instead of the correct &tabstop number of spaces. Thanks to Christian Brehm!\r\n\r\nRenamed options to g:vhdl_indent_genportmap & g:vhdl_indent_rhsassign, to be consistent with naming convention.","package":"vhdl.vim","4":"vhdl.vim","src_id":"7460","5":"7460","creation_date":"1186478151","6":"1186478151"},{"0":"1450","vim_version":"7.0","1":"7.0","script_version":"1.50","2":"1.50","version_comment":"Now, alignment of generic\/port mappings and RHS assignment \"<=\" statements can be disabled in \".vimrc\".\r\nMinor improvements to keywords \"end\" + \"component\".","3":"Now, alignment of generic\/port mappings and RHS assignment \"<=\" statements can be disabled in \".vimrc\".\r\nMinor improvements to keywords \"end\" + \"component\".","package":"vhdl.vim","4":"vhdl.vim","src_id":"6690","5":"6690","creation_date":"1170096795","6":"1170096795"},{"0":"1450","vim_version":"7.0","1":"7.0","script_version":"1.40","2":"1.40","version_comment":"Improved indenting for keyword \"end\".","3":"Improved indenting for keyword \"end\".","package":"vhdl.vim","4":"vhdl.vim","src_id":"5830","5":"5830","creation_date":"1150242058","6":"1150242058"},{"0":"1450","vim_version":"7.0","1":"7.0","script_version":"1.36","2":"1.36","version_comment":"No change to main code. Just commented out code for \"[[\", \"]]\", etc. motion & matchit configuration, because they rightfully belong to the VHDL ftplugin. Also removed auto-indenting when typing \"--\" comment - it was more annoying than helpful.","3":"No change to main code. Just commented out code for \"[[\", \"]]\", etc. motion & matchit configuration, because they rightfully belong to the VHDL ftplugin. Also removed auto-indenting when typing \"--\" comment - it was more annoying than helpful.","package":"vhdl.vim","4":"vhdl.vim","src_id":"5546","5":"5546","creation_date":"1144860396","6":"1144860396"},{"0":"1450","vim_version":"6.0","1":"6.0","script_version":"1.34","2":"1.34","version_comment":"Small change: Improved '[[', ']]', '[]', '][' motions. Motions now accept a count (e.g. indent 3 blocks '=3]['). Motions also ignore comments now, and work for visual-type modes.","3":"Small change: Improved '[[', ']]', '[]', '][' motions. Motions now accept a count (e.g. indent 3 blocks '=3]['). Motions also ignore comments now, and work for visual-type modes.","package":"vhdl.vim","4":"vhdl.vim","src_id":"5157","5":"5157","creation_date":"1139670144","6":"1139670144"},{"0":"1450","vim_version":"6.0","1":"6.0","script_version":"1.3","2":"1.3","version_comment":"Made more robust for various code layout.\r\nFixed \"else\" keyword in conditional statement bug.\r\nMany other tweaks applied.","3":"Made more robust for various code layout.\r\nFixed \"else\" keyword in conditional statement bug.\r\nMany other tweaks applied.","package":"vhdl.vim","4":"vhdl.vim","src_id":"5017","5":"5017","creation_date":"1138721335","6":"1138721335"},{"0":"1450","vim_version":"6.0","1":"6.0","script_version":"1.2","2":"1.2","version_comment":"Minor fixes:\r\nKeyword \"report\" handling added.\r\nBetter handling of keyword \"for\".\r\nResolved \"<=\" confusion between signal assignment & less-than operator.\r\nMade some matches more robust.\r\n","3":"Minor fixes:\r\nKeyword \"report\" handling added.\r\nBetter handling of keyword \"for\".\r\nResolved \"<=\" confusion between signal assignment & less-than operator.\r\nMade some matches more robust.\r\n","package":"vhdl.vim","4":"vhdl.vim","src_id":"5005","5":"5005","creation_date":"1138306529","6":"1138306529"},{"0":"1450","vim_version":"6.0","1":"6.0","script_version":"1.1","2":"1.1","version_comment":"Many major fixes:\r\nGeneric\/Port\/Map statements alignment\r\nGeneric Map no semicolon oddity accounted for\r\nCase-When alignment when one-line When statements are present\r\nComments are smart-aligned now (be sure to do indenting at least twice)\r\nAccommodated more coding styles (VHDL people are a diverse bunch ;))\r\nand many more.","3":"Many major fixes:\r\nGeneric\/Port\/Map statements alignment\r\nGeneric Map no semicolon oddity accounted for\r\nCase-When alignment when one-line When statements are present\r\nComments are smart-aligned now (be sure to do indenting at least twice)\r\nAccommodated more coding styles (VHDL people are a diverse bunch ;))\r\nand many more.","package":"vhdl.vim","4":"vhdl.vim","src_id":"5002","5":"5002","creation_date":"1138231022","6":"1138231022"},{"0":"1450","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"vhdl.vim","4":"vhdl.vim","src_id":"5000","5":"5000","creation_date":"1138066712","6":"1138066712"}]},"1449":{"script_id":"1449","0":"1449","script_name":"vera.vim","1":"vera.vim","script_type":"syntax","2":"syntax","summary":"Syntax highlighting for Vera","3":"Syntax highlighting for Vera","description":"Updated syntax file for Vera 2005.06. Many new features are added from previous vera syntax versions.","4":"Updated syntax file for Vera 2005.06. Many new features are added from previous vera syntax versions.","install_details":"drop it in ~\/.vim\/syntax\/vera.vim.\r\n\r\nNOTE: extra white space at the end of the line will be highlighted if you add this line to your colorscheme:\r\n\r\nhighlight SpaceError    guibg=#204050\r\n\r\n(change the value for guibg to any color you like)","5":"drop it in ~\/.vim\/syntax\/vera.vim.\r\n\r\nNOTE: extra white space at the end of the line will be highlighted if you add this line to your colorscheme:\r\n\r\nhighlight SpaceError    guibg=#204050\r\n\r\n(change the value for guibg to any color you like)","first_name":"David","6":"David","last_name":"Larson","7":"Larson","releases":[{"0":"1449","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"vera.vim","4":"vera.vim","src_id":"4994","5":"4994","creation_date":"1137751338","6":"1137751338"}]},"1448":{"script_id":"1448","0":"1448","script_name":"Low-Contrast Color Schemes","1":"Low-Contrast Color Schemes","script_type":"color scheme","2":"color scheme","summary":"Collection of low-contrast color schemes","3":"Collection of low-contrast color schemes","description":"Many color schemes have colors that have a medium to high contrast.  A higher contrast makes the text stand out more against the background.\r\n\r\nI personally don't like high contrast in my text.  I find it distracting, and it bothers my eyes after looking at it for a long time.  It's especially distracting when the colors have a varying degree of contrast-ness.\r\n\r\nSo, I worked to find the best low-contrast colors that are still distinguishable from each other.  High contrast is still there if it's something important, like an error, or if I never changed the default because it never shows up in the things I do.\r\n\r\nHope you like them!","4":"Many color schemes have colors that have a medium to high contrast.  A higher contrast makes the text stand out more against the background.\r\n\r\nI personally don't like high contrast in my text.  I find it distracting, and it bothers my eyes after looking at it for a long time.  It's especially distracting when the colors have a varying degree of contrast-ness.\r\n\r\nSo, I worked to find the best low-contrast colors that are still distinguishable from each other.  High contrast is still there if it's something important, like an error, or if I never changed the default because it never shows up in the things I do.\r\n\r\nHope you like them!","install_details":"cd ~\/.vim\r\ntar zxf LoContrastColors.tar.gz\r\n","5":"cd ~\/.vim\r\ntar zxf LoContrastColors.tar.gz\r\n","first_name":"Tye","6":"Tye","last_name":"Zdrojewski","7":"Zdrojewski","releases":[{"0":"1448","vim_version":"6.0","1":"6.0","script_version":"1.1","2":"1.1","version_comment":"Slight updates.  Added support for CursorLine and CursorColumn in Vim 7 (but should still work fine in previous versions).","3":"Slight updates.  Added support for CursorLine and CursorColumn in Vim 7 (but should still work fine in previous versions).","package":"LoContrastColors.tar.gz","4":"LoContrastColors.tar.gz","src_id":"6908","5":"6908","creation_date":"1174996704","6":"1174996704"},{"0":"1448","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"LoContrastColors.tar.gz","4":"LoContrastColors.tar.gz","src_id":"4989","5":"4989","creation_date":"1137503067","6":"1137503067"}]},"1447":{"script_id":"1447","0":"1447","script_name":"Altair OptiStruct Syntax","1":"Altair OptiStruct Syntax","script_type":"syntax","2":"syntax","summary":"Fixed field formatting (8 field) for Altair OptiStruct","3":"Fixed field formatting (8 field) for Altair OptiStruct","description":"8 Field formatting for editing Altair OptiStruct decks - you'll never again need to add another \"$......><......><......><......><......><......>\" line when editing an OptiStruct deck . The syntax shows the 8 field spacing with coloured fields.\r\nIt is also recommended that this syntax be used for editing nastran files - its much more useful than the nastran syntax!!","4":"8 Field formatting for editing Altair OptiStruct decks - you'll never again need to add another \"$......><......><......><......><......><......>\" line when editing an OptiStruct deck . The syntax shows the 8 field spacing with coloured fields.\r\nIt is also recommended that this syntax be used for editing nastran files - its much more useful than the nastran syntax!!","install_details":"Add filetype.vim to C:\\Program Files\\Vim\\vim63  = allows vim to autoselect profile for .fem & .bdf files\r\nAdd optistruct.vim to C:\\Program Files\\Vim\\vim63\\syntax = profile\r\nAdd synmenu.vim to C:\\Program Files\\Vim\\vim63  = adds optistruct profile to the syntax menu\r\n","5":"Add filetype.vim to C:\\Program Files\\Vim\\vim63  = allows vim to autoselect profile for .fem & .bdf files\r\nAdd optistruct.vim to C:\\Program Files\\Vim\\vim63\\syntax = profile\r\nAdd synmenu.vim to C:\\Program Files\\Vim\\vim63  = adds optistruct profile to the syntax menu\r\n","first_name":"Sam","6":"Sam","last_name":"Patten","7":"Patten","releases":[{"0":"1447","vim_version":"6.0","1":"6.0","script_version":"110306","2":"110306","version_comment":"As previous but in unix\/linux format.","3":"As previous but in unix\/linux format.","package":"optistruct_linux.tar.gz","4":"optistruct_linux.tar.gz","src_id":"5412","5":"5412","creation_date":"1142043570","6":"1142043570"},{"0":"1447","vim_version":"6.0","1":"6.0","script_version":"210206","2":"210206","version_comment":"As before with more cards supported.","3":"As before with more cards supported.","package":"optistruct.zip","4":"optistruct.zip","src_id":"5288","5":"5288","creation_date":"1140480897","6":"1140480897"},{"0":"1447","vim_version":"6.0","1":"6.0","script_version":"310106","2":"310106","version_comment":"Added 8 & 16 field format support & some more cards","3":"Added 8 & 16 field format support & some more cards","package":"optistruct.zip","4":"optistruct.zip","src_id":"5016","5":"5016","creation_date":"1138704284","6":"1138704284"},{"0":"1447","vim_version":"6.0","1":"6.0","script_version":"300106","2":"300106","version_comment":"Improved 8 field colouring & added colours for some useful cards.","3":"Improved 8 field colouring & added colours for some useful cards.","package":"optistruct.zip","4":"optistruct.zip","src_id":"5011","5":"5011","creation_date":"1138608894","6":"1138608894"},{"0":"1447","vim_version":"6.0","1":"6.0","script_version":"160106","2":"160106","version_comment":"Initial upload","3":"Initial upload","package":"optistruct.zip","4":"optistruct.zip","src_id":"4986","5":"4986","creation_date":"1137477452","6":"1137477452"}]},"1446":{"script_id":"1446","0":"1446","script_name":"MoveLine","1":"MoveLine","script_type":"syntax","2":"syntax","summary":"Moves Lines up or down","3":"Moves Lines up or down","description":"Uses the 'e' and 'f' keys to move a line up or down.  Extremely useful when coding.","4":"Uses the 'e' and 'f' keys to move a line up or down.  Extremely useful when coding.","install_details":"put in the vim plugin folder\r\non linux its usually \/usr\/share\/vim\/vimxx\/plugin\r\non windows I think its\r\nC:\\program files\\vim\\vimxx\\plugin","5":"put in the vim plugin folder\r\non linux its usually \/usr\/share\/vim\/vimxx\/plugin\r\non windows I think its\r\nC:\\program files\\vim\\vimxx\\plugin","first_name":"Joe","6":"Joe","last_name":"Chrzanowski","7":"Chrzanowski","releases":[{"0":"1446","vim_version":"6.0","1":"6.0","script_version":"2","2":"2","version_comment":"Finally fixed it so the lines don't go off the screen anymore -- this one shouldn't have any problems in it.","3":"Finally fixed it so the lines don't go off the screen anymore -- this one shouldn't have any problems in it.","package":"moveline.vim","4":"moveline.vim","src_id":"5566","5":"5566","creation_date":"1145187883","6":"1145187883"},{"0":"1446","vim_version":"6.0","1":"6.0","script_version":"1.1","2":"1.1","version_comment":"Maps 'e' and 'f' instead of 'r' and 'f'\r\n(e is the same as ctrl+<right>)","3":"Maps 'e' and 'f' instead of 'r' and 'f'\r\n(e is the same as ctrl+<right>)","package":"moveline.vim","4":"moveline.vim","src_id":"5487","5":"5487","creation_date":"1143454133","6":"1143454133"},{"0":"1446","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"I added a warning in the comments: if you attempt to move a line past the last line of a file -- it will disappear.  tell me if you know how to fix that.","3":"I added a warning in the comments: if you attempt to move a line past the last line of a file -- it will disappear.  tell me if you know how to fix that.","package":"moveline.vim","4":"moveline.vim","src_id":"4982","5":"4982","creation_date":"1137441635","6":"1137441635"},{"0":"1446","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"moveline.vim","4":"moveline.vim","src_id":"4980","5":"4980","creation_date":"1137438625","6":"1137438625"}]},"1445":{"script_id":"1445","0":"1445","script_name":"AllBuffersToOneWindow.vim","1":"AllBuffersToOneWindow.vim","script_type":"utility","2":"utility","summary":"Bring all remote Vim window buffers together in one Vim window.","3":"Bring all remote Vim window buffers together in one Vim window.","description":"Usage:\r\n   This script adds one new command \":AllBuffersToOneWindow\".\r\n   You can use the \":AllBuffersToOneWindow\" command to load buffers that are\r\n   loaded in remote Vim window in main Vim window.\r\n\r\n   1. Run Vim application (process A), and edit File1, File2, FIle3.\r\n   2. Run Vim application (process B), and edit File4, File5\r\n   3. Run Vim application (process C), and input \":AllBuffersToOneWindow\"\r\n      command.\r\n   4. Input \":buffers\" command. (Vim application process C)\r\n      File1, File2, File3, File4 and File5 are added to buffer list.\r\n\r\nNote:\r\n   o  To run this script, Vim needs to be compiled with \"+clientserver\" option.\r\n   o  If buffer is file and can be read, buffer will be loaded in main Vim window.\r\n   o  If buffer is already loaded in main window, buffer will not be loaded.","4":"Usage:\r\n   This script adds one new command \":AllBuffersToOneWindow\".\r\n   You can use the \":AllBuffersToOneWindow\" command to load buffers that are\r\n   loaded in remote Vim window in main Vim window.\r\n\r\n   1. Run Vim application (process A), and edit File1, File2, FIle3.\r\n   2. Run Vim application (process B), and edit File4, File5\r\n   3. Run Vim application (process C), and input \":AllBuffersToOneWindow\"\r\n      command.\r\n   4. Input \":buffers\" command. (Vim application process C)\r\n      File1, File2, File3, File4 and File5 are added to buffer list.\r\n\r\nNote:\r\n   o  To run this script, Vim needs to be compiled with \"+clientserver\" option.\r\n   o  If buffer is file and can be read, buffer will be loaded in main Vim window.\r\n   o  If buffer is already loaded in main window, buffer will not be loaded.","install_details":"   1. Copy the AllBuffersToOneWindow.vim script to\r\n      $HOME\/vimfiles\/plugin or $HOME\/.vim\/plugin directory directory.\r\n      Refer to ':help add-plugin', ':help add-global-plugin' and ':help runtimepath'\r\n      for more details about Vim plugins.\r\n   2. Restart Vim.\r\n   3. To run this script, Vim needs to be compiled with \"+clientserver\" option.","5":"   1. Copy the AllBuffersToOneWindow.vim script to\r\n      $HOME\/vimfiles\/plugin or $HOME\/.vim\/plugin directory directory.\r\n      Refer to ':help add-plugin', ':help add-global-plugin' and ':help runtimepath'\r\n      for more details about Vim plugins.\r\n   2. Restart Vim.\r\n   3. To run this script, Vim needs to be compiled with \"+clientserver\" option.","first_name":"omi","6":"omi","last_name":"taku","7":"taku","releases":[{"0":"1445","vim_version":"6.0","1":"6.0","script_version":"0.1.1","2":"0.1.1","version_comment":"Some Changes are added to file loading logic.","3":"Some Changes are added to file loading logic.","package":"AllBuffersToOneWindow.vim","4":"AllBuffersToOneWindow.vim","src_id":"4981","5":"4981","creation_date":"1137440771","6":"1137440771"},{"0":"1445","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"AllBuffersToOneWindow.vim","4":"AllBuffersToOneWindow.vim","src_id":"4971","5":"4971","creation_date":"1137257297","6":"1137257297"}]},"1444":{"script_id":"1444","0":"1444","script_name":"colors","1":"colors","script_type":"utility","2":"utility","summary":"Functions to manipulate color values (vim7).","3":"Functions to manipulate color values (vim7).","description":"Rgb2Hsv - change RGB into HSV colorspace\r\nHsv2Rgb - change HSV into RGB colorspace\r\n\r\nr, g, b [0..255]\r\nh [0..359]\r\ns, v [0..255] sic!\r\n\r\nHex2Rgb - change Hex notation (#ffffff) into rgb [255,255,255]\r\nRgb2Hex - change RGB notation into Hex notation\r\nTxt2Rgb - change text names of functions into RGB notation (names according to rgb.txt of X consortium)\r\n\r\nIn addition there is function ColorFormula which will tell if brightness and\r\ncolor differences are good enough (according to W3C) to became background and text colors.\r\nGood for testing colorschemes on HTML sites and Vim.\r\n","4":"Rgb2Hsv - change RGB into HSV colorspace\r\nHsv2Rgb - change HSV into RGB colorspace\r\n\r\nr, g, b [0..255]\r\nh [0..359]\r\ns, v [0..255] sic!\r\n\r\nHex2Rgb - change Hex notation (#ffffff) into rgb [255,255,255]\r\nRgb2Hex - change RGB notation into Hex notation\r\nTxt2Rgb - change text names of functions into RGB notation (names according to rgb.txt of X consortium)\r\n\r\nIn addition there is function ColorFormula which will tell if brightness and\r\ncolor differences are good enough (according to W3C) to became background and text colors.\r\nGood for testing colorschemes on HTML sites and Vim.\r\n","install_details":":so colors.vim\r\n\r\nMay be placed in plugin directory","5":":so colors.vim\r\n\r\nMay be placed in plugin directory","first_name":"Mikolaj","6":"Mikolaj","last_name":"Machowski","7":"Machowski","releases":[{"0":"1444","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"colors.vim","4":"colors.vim","src_id":"4968","5":"4968","creation_date":"1137228692","6":"1137228692"}]},"1443":{"script_id":"1443","0":"1443","script_name":"telstar.vim","1":"telstar.vim","script_type":"color scheme","2":"color scheme","summary":"outer space color scheme for gvim","3":"outer space color scheme for gvim","description":"A dark, blue\/lavender\/gray\/magenta space-y theme for gvim only, sorry. Also has a few extra highlights for Java. Screenshot at http:\/\/excelsi.org\/telstar.jpg (the background there is not part of the colorscheme, but it does match nicely...)\r\n\r\nIf you want to use the Java highlighting you'll need Claudio Fleiner's java.vim syntax highlighting from\r\nhttp:\/\/www.fleiner.com\/vim\/download.html.","4":"A dark, blue\/lavender\/gray\/magenta space-y theme for gvim only, sorry. Also has a few extra highlights for Java. Screenshot at http:\/\/excelsi.org\/telstar.jpg (the background there is not part of the colorscheme, but it does match nicely...)\r\n\r\nIf you want to use the Java highlighting you'll need Claudio Fleiner's java.vim syntax highlighting from\r\nhttp:\/\/www.fleiner.com\/vim\/download.html.","install_details":"drop telstar.vim in your ~\/.vim\/colors directory and say \":colors telstar\". to make it permanent, put \"colors telstar\" in your ~\/.gvimrc.","5":"drop telstar.vim in your ~\/.vim\/colors directory and say \":colors telstar\". to make it permanent, put \"colors telstar\" in your ~\/.gvimrc.","first_name":"john","6":"john","last_name":"white","7":"white","releases":[{"0":"1443","vim_version":"6.0","1":"6.0","script_version":"2","2":"2","version_comment":"added colors for pop-up menu and paren matching","3":"added colors for pop-up menu and paren matching","package":"telstar.vim","4":"telstar.vim","src_id":"7816","5":"7816","creation_date":"1193066147","6":"1193066147"},{"0":"1443","vim_version":"6.0","1":"6.0","script_version":"1","2":"1","version_comment":"Initial upload","3":"Initial upload","package":"telstar.vim","4":"telstar.vim","src_id":"4966","5":"4966","creation_date":"1137207905","6":"1137207905"}]},"1442":{"script_id":"1442","0":"1442","script_name":"XML Completion","1":"XML Completion","script_type":"ftplugin","2":"ftplugin","summary":"Completion for XML files","3":"Completion for XML files","description":"Context sensitive completion for XML.\r\nCompletes:\r\n * element names\r\n * attribute names (rejects already presented attributes)\r\n * attribute values (if defined as enumeration)\r\n * closing tag names\r\n * keywords in XML declaration\r\n\r\n1. Invoking\r\n\r\nThe completion function is XmlComplete() and is imapped on \\C-J.\r\n\r\n2. Completion in elements\r\n\r\nDistribution contains definition files (recipes) for DocBook 4.[234], XSL FO 1.0, XSLT 1.0, Relax NG 1.0, XML Schemas 1.0, SVG 1.1, XHTML 1.1, XInclude 1.0 and OpenOffice 1.0 XML format.\r\n\r\nIf g:xmlSubelements == \"yes\" (default \"no\"), completion of element names is restricted on subelements of parent element. This feature is new and momentarily works only for DocBook, XSLT and XML Schemas (the recipes must be modified).\r\n\r\nCompletion algorithm:\r\n1. If name of currently opened tag is prefixed, looks for respective xmlns mapping for its URN. If mapping exists, selects recipe associated with this URN.\r\n2. If name isn't prefixed, looks for implicit NS. If exists, ... (see above).\r\n3. Looks for Doctype decl. If found, tries first PUBLIC, then SYSTEM ident.\r\n4. If all fails, fires \\C-N for normal completion.","4":"Context sensitive completion for XML.\r\nCompletes:\r\n * element names\r\n * attribute names (rejects already presented attributes)\r\n * attribute values (if defined as enumeration)\r\n * closing tag names\r\n * keywords in XML declaration\r\n\r\n1. Invoking\r\n\r\nThe completion function is XmlComplete() and is imapped on \\C-J.\r\n\r\n2. Completion in elements\r\n\r\nDistribution contains definition files (recipes) for DocBook 4.[234], XSL FO 1.0, XSLT 1.0, Relax NG 1.0, XML Schemas 1.0, SVG 1.1, XHTML 1.1, XInclude 1.0 and OpenOffice 1.0 XML format.\r\n\r\nIf g:xmlSubelements == \"yes\" (default \"no\"), completion of element names is restricted on subelements of parent element. This feature is new and momentarily works only for DocBook, XSLT and XML Schemas (the recipes must be modified).\r\n\r\nCompletion algorithm:\r\n1. If name of currently opened tag is prefixed, looks for respective xmlns mapping for its URN. If mapping exists, selects recipe associated with this URN.\r\n2. If name isn't prefixed, looks for implicit NS. If exists, ... (see above).\r\n3. Looks for Doctype decl. If found, tries first PUBLIC, then SYSTEM ident.\r\n4. If all fails, fires \\C-N for normal completion.","install_details":"","5":"","first_name":"David","6":"David","last_name":"Tardon","7":"Tardon","releases":[{"0":"1442","vim_version":"6.0","1":"6.0","script_version":"1.18","2":"1.18","version_comment":"Initial upload","3":"Initial upload","package":"xml_completion-1.18.tar.gz","4":"xml_completion-1.18.tar.gz","src_id":"4965","5":"4965","creation_date":"1137137914","6":"1137137914"}]},"1441":{"script_id":"1441","0":"1441","script_name":"xsl-fo","1":"xsl-fo","script_type":"syntax","2":"syntax","summary":"xsl-fo Syntax","3":"xsl-fo Syntax","description":"syntax file for xsl-fo\r\n\r\nIt colors all \"valid\" xsl-fo elements and attributes with a set of colors making it easy to spot invalid xsl-fo constructs.\r\n\r\nThis syntax works well with other related syntaxs like xsl or xml.\r\n\r\n","4":"syntax file for xsl-fo\r\n\r\nIt colors all \"valid\" xsl-fo elements and attributes with a set of colors making it easy to spot invalid xsl-fo constructs.\r\n\r\nThis syntax works well with other related syntaxs like xsl or xml.\r\n\r\n","install_details":"Copy the file to $VIMRUNTIME\/Syntax or $VIM\/vimfiles\/syntax\r\n\r\nto enable xsl-fo syntax highlighting on any xsl, xslt or xslfo file go\r\n:set filetype=xslfo\r\n\r\nor add following to your vimrc \r\nautocmd FileType xsl,xslt      set filetype=xslfo\r\n","5":"Copy the file to $VIMRUNTIME\/Syntax or $VIM\/vimfiles\/syntax\r\n\r\nto enable xsl-fo syntax highlighting on any xsl, xslt or xslfo file go\r\n:set filetype=xslfo\r\n\r\nor add following to your vimrc \r\nautocmd FileType xsl,xslt      set filetype=xslfo\r\n","first_name":"anand","6":"anand","last_name":"unawane","7":"unawane","releases":[{"0":"1441","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"xslfo.vim","4":"xslfo.vim","src_id":"4955","5":"4955","creation_date":"1136799026","6":"1136799026"}]},"1440":{"script_id":"1440","0":"1440","script_name":"winmanager","1":"winmanager","script_type":"utility","2":"utility","summary":"A windows style IDE for Vim","3":"A windows style IDE for Vim","description":"This plugin is a minor bug-fix version of vimscript #95.\r\n\r\nI sent the patches to the author of winmanager last September but I've received no reply till now.  I assume that he doesn't maintain this script any more.  So I decide to upload my patched version as a new entry.\r\n\r\nOne new feature of this plugin is called \"start\".  When you are browsing files with winfileexplorer, just place your cursor onto a file and press \"S\" (shift-s), Vim will open the file with the application associated with the file type. So you are able to launch a media player to enjoy the music without opening an extra konqueror or nautilus.\r\n\r\nAnother new feature of this plugin is \"toggle show hidden files\/directories\".  By default, this plugin doesn't show files\/directories prefixed with dot \".\".  You can toggle show\/hide hidden files\/directories by pressing \"x\" in the file explorer window.  You can override this default setting by putting \"let g:explShowHiddenFiles = 1\" in your \"~\/.vimrc\" to make it show hidden files\/directories by default.","4":"This plugin is a minor bug-fix version of vimscript #95.\r\n\r\nI sent the patches to the author of winmanager last September but I've received no reply till now.  I assume that he doesn't maintain this script any more.  So I decide to upload my patched version as a new entry.\r\n\r\nOne new feature of this plugin is called \"start\".  When you are browsing files with winfileexplorer, just place your cursor onto a file and press \"S\" (shift-s), Vim will open the file with the application associated with the file type. So you are able to launch a media player to enjoy the music without opening an extra konqueror or nautilus.\r\n\r\nAnother new feature of this plugin is \"toggle show hidden files\/directories\".  By default, this plugin doesn't show files\/directories prefixed with dot \".\".  You can toggle show\/hide hidden files\/directories by pressing \"x\" in the file explorer window.  You can override this default setting by putting \"let g:explShowHiddenFiles = 1\" in your \"~\/.vimrc\" to make it show hidden files\/directories by default.","install_details":"1. This plugin is compressed in VimBall format. So you may need to install the latest version of vimscript #1502 first.\r\n\r\n2. Then the just download this Vimball, opening it in Vim and typing this command followed by an enter in your Vim:\r\n\r\n:so %\r\n\r\n3. For Windows users, \"start\" is already installed in your system so just skip this step; for Linux users, create a symbolic link named \"start\" in one of your $PATH directory, pointing to \"~\/.vim\/plugin\/start.kde\" or \"~\/.vim\/plugin\/start.gnome\", depending to your desktop environment (other desktop environments are not supported yet); for Mac users, \"start\" feature is unavailable yet.\r\n\r\n4. Install vimscript #42. If you don't want to use that plugin, just add this line in your .vimrc to disable the integration of bufexplorer.vim:\r\n\r\nlet g:winManagerWindowLayout = \"FileExplorer\"\r\n\r\n5. Enjoy and happy Vimming!","5":"1. This plugin is compressed in VimBall format. So you may need to install the latest version of vimscript #1502 first.\r\n\r\n2. Then the just download this Vimball, opening it in Vim and typing this command followed by an enter in your Vim:\r\n\r\n:so %\r\n\r\n3. For Windows users, \"start\" is already installed in your system so just skip this step; for Linux users, create a symbolic link named \"start\" in one of your $PATH directory, pointing to \"~\/.vim\/plugin\/start.kde\" or \"~\/.vim\/plugin\/start.gnome\", depending to your desktop environment (other desktop environments are not supported yet); for Mac users, \"start\" feature is unavailable yet.\r\n\r\n4. Install vimscript #42. If you don't want to use that plugin, just add this line in your .vimrc to disable the integration of bufexplorer.vim:\r\n\r\nlet g:winManagerWindowLayout = \"FileExplorer\"\r\n\r\n5. Enjoy and happy Vimming!","first_name":"Edward","6":"Edward","last_name":"Fox","7":"Fox","releases":[{"0":"1440","vim_version":"7.0","1":"7.0","script_version":"2.41","2":"2.41","version_comment":"Fixed the problem that editing window loses showcmd value when winManager window gains focus. Thanks very much to kend at myvnet dot com for providing this patch!","3":"Fixed the problem that editing window loses showcmd value when winManager window gains focus. Thanks very much to kend at myvnet dot com for providing this patch!","package":"winmanager.vmb.bz2","4":"winmanager.vmb.bz2","src_id":"18243","5":"18243","creation_date":"1341966890","6":"1341966890"},{"0":"1440","vim_version":"7.0","1":"7.0","script_version":"2.40","2":"2.40","version_comment":"Added two configuration variables: \r\n\r\n  g:winManagerOnRightSide - Put the winmanager window on the right side of VIM. Default: 0. \r\n\r\n  g:winManagerAutoOpen - Open winmanager window automatically when launching VIM. Default 0. \r\n\r\nThanks very much to kend at myvnet dot com for providing this patch!","3":"Added two configuration variables: \r\n\r\n  g:winManagerOnRightSide - Put the winmanager window on the right side of VIM. Default: 0. \r\n\r\n  g:winManagerAutoOpen - Open winmanager window automatically when launching VIM. Default 0. \r\n\r\nThanks very much to kend at myvnet dot com for providing this patch!","package":"winmanager.vmb.bz2","4":"winmanager.vmb.bz2","src_id":"18196","5":"18196","creation_date":"1340753875","6":"1340753875"},{"0":"1440","vim_version":"7.0","1":"7.0","script_version":"2.35","2":"2.35","version_comment":"Implemented the \"toggle show hidden files\/directories\" feature.","3":"Implemented the \"toggle show hidden files\/directories\" feature.","package":"winmanager.vba.bz2","4":"winmanager.vba.bz2","src_id":"11032","5":"11032","creation_date":"1247920384","6":"1247920384"},{"0":"1440","vim_version":"7.0","1":"7.0","script_version":"2.34","2":"2.34","version_comment":"1. If \"g:netrw_browsex_viewer\" is set, when press \"S\" in the file explorer the plugin will open the file with the specified browser instead of \"start\" command. So it's not possible to symbolically link \"start.kde\" or \"start.gnome\" into one of your PATH directories.\r\n\r\n2. Try to pack the plugin into a vba ball. So the user can install the plugin by simply open it in Vim and run \":so %\".","3":"1. If \"g:netrw_browsex_viewer\" is set, when press \"S\" in the file explorer the plugin will open the file with the specified browser instead of \"start\" command. So it's not possible to symbolically link \"start.kde\" or \"start.gnome\" into one of your PATH directories.\r\n\r\n2. Try to pack the plugin into a vba ball. So the user can install the plugin by simply open it in Vim and run \":so %\".","package":"winmanager.vba.gz","4":"winmanager.vba.gz","src_id":"7151","5":"7151","creation_date":"1179799475","6":"1179799475"},{"0":"1440","vim_version":"6.0","1":"6.0","script_version":"2.33-p","2":"2.33-p","version_comment":"Minor bug fix: when 'foldmethod' is set as 'indent', refreshing wintagexplorer will throws out many error messages.","3":"Minor bug fix: when 'foldmethod' is set as 'indent', refreshing wintagexplorer will throws out many error messages.","package":"winmanager.tar.bz2","4":"winmanager.tar.bz2","src_id":"6022","5":"6022","creation_date":"1154472413","6":"1154472413"},{"0":"1440","vim_version":"6.0","1":"6.0","script_version":"2.33","2":"2.33","version_comment":"Fixed the bug that the plugin can't open the files which contain spaces in their filenames.","3":"Fixed the bug that the plugin can't open the files which contain spaces in their filenames.","package":"winmanager.tar.bz2","4":"winmanager.tar.bz2","src_id":"5329","5":"5329","creation_date":"1140927415","6":"1140927415"},{"0":"1440","vim_version":"6.0","1":"6.0","script_version":"2.32","2":"2.32","version_comment":"Merge the changes from Hari Krishna Dara and re-release a new pack.","3":"Merge the changes from Hari Krishna Dara and re-release a new pack.","package":"winmanager.tar.bz2","4":"winmanager.tar.bz2","src_id":"4954","5":"4954","creation_date":"1136749422","6":"1136749422"},{"0":"1440","vim_version":"6.0","1":"6.0","script_version":"2.31","2":"2.31","version_comment":"Initial upload","3":"Initial upload","package":"winmanager.tar.bz2","4":"winmanager.tar.bz2","src_id":"4945","5":"4945","creation_date":"1136414706","6":"1136414706"}]},"1439":{"script_id":"1439","0":"1439","script_name":"compiler\/python.vim","1":"compiler\/python.vim","script_type":"ftplugin","2":"ftplugin","summary":"compiler plugin for python","3":"compiler plugin for python","description":"Based on the script and notation from vimscript #477\r\n\r\nThis compiler script does not run the source through the python interpreter, but instead uses the py_compile package to check for syntax errors.  This allows for a development cycle similar to a compiled language - edit, compile, run.","4":"Based on the script and notation from vimscript #477\r\n\r\nThis compiler script does not run the source through the python interpreter, but instead uses the py_compile package to check for syntax errors.  This allows for a development cycle similar to a compiled language - edit, compile, run.","install_details":"Copy the file to $VIMRUNTIME\/compiler\/ or ~\/.vim\/compiler\/","5":"Copy the file to $VIMRUNTIME\/compiler\/ or ~\/.vim\/compiler\/","first_name":"aaron","6":"aaron","last_name":"griffin","7":"griffin","releases":[{"0":"1439","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"python.vim","4":"python.vim","src_id":"4942","5":"4942","creation_date":"1136373119","6":"1136373119"}]},"1438":{"script_id":"1438","0":"1438","script_name":"XML Folding","1":"XML Folding","script_type":"utility","2":"utility","summary":"Folds XML \/ HTML Tags, CDATA and comments","3":"Folds XML \/ HTML Tags, CDATA and comments","description":"It pretend to be the fold solution for all XML\/HTML\/SVG and other xml derivated...\r\n\r\nThis script supports:\r\n\r\nTag folds between two different lines: <tag> <\/tag>\r\nComments folds: <!-- comment -->\r\nCDATA folds content between \"<!<CDATA[\" and \"]]>\"","4":"It pretend to be the fold solution for all XML\/HTML\/SVG and other xml derivated...\r\n\r\nThis script supports:\r\n\r\nTag folds between two different lines: <tag> <\/tag>\r\nComments folds: <!-- comment -->\r\nCDATA folds content between \"<!<CDATA[\" and \"]]>\"","install_details":"You only need to download it and run under your XML\/HTML file with the\r\n\r\n:so XMLFolding.vim\r\n\r\nor, if you want to, add this line into your ~\/.vimrc:\r\n\r\nau BufNewFile,BufRead *.xml,*.htm,*.html so XMLFolding\r\n\r\nDoing this, always the script will be loaded on open these files.\r\nDont forget to put the correct path to access the file!!! ","5":"You only need to download it and run under your XML\/HTML file with the\r\n\r\n:so XMLFolding.vim\r\n\r\nor, if you want to, add this line into your ~\/.vimrc:\r\n\r\nau BufNewFile,BufRead *.xml,*.htm,*.html so XMLFolding\r\n\r\nDoing this, always the script will be loaded on open these files.\r\nDont forget to put the correct path to access the file!!! ","first_name":"Thadeu","6":"Thadeu","last_name":"de Paula","7":"de Paula","releases":[{"0":"1438","vim_version":"6.0","1":"6.0","script_version":"1.1","2":"1.1","version_comment":"In this version... only lines started and ended by a tag ,without spaces before, are used to make an folding... with this rule, the folding errors will be less!!!","3":"In this version... only lines started and ended by a tag ,without spaces before, are used to make an folding... with this rule, the folding errors will be less!!!","package":"XMLFolding.vim","4":"XMLFolding.vim","src_id":"5685","5":"5685","creation_date":"1147479443","6":"1147479443"},{"0":"1438","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"XMLFolding.vim","4":"XMLFolding.vim","src_id":"4936","5":"4936","creation_date":"1136257544","6":"1136257544"}]},"1437":{"script_id":"1437","0":"1437","script_name":"Compiler Plugin for msbuild csc","1":"Compiler Plugin for msbuild csc","script_type":"utility","2":"utility","summary":"Build your msbuild file and visual studio .net 2005 csharp projects in vim.","3":"Build your msbuild file and visual studio .net 2005 csharp projects in vim.","description":"Msbuild is an easy way to building visusal studio's solution without the IDE. It's very cool using vim to work with your \"IDE team members\". So this is msbuild plugin.\r\n\r\nMsbuild use csc internally to build .csproj project file. Normally we build .sln file, which is in the parent directory of .csproj file. So the csc's output is relative to .csproj directory, not the .sln directory. Vim can't find the error source file. To solve this, you must enable \"GenerateFullPaths\" option in your .csproj project file.","4":"Msbuild is an easy way to building visusal studio's solution without the IDE. It's very cool using vim to work with your \"IDE team members\". So this is msbuild plugin.\r\n\r\nMsbuild use csc internally to build .csproj project file. Normally we build .sln file, which is in the parent directory of .csproj file. So the csc's output is relative to .csproj directory, not the .sln directory. Vim can't find the error source file. To solve this, you must enable \"GenerateFullPaths\" option in your .csproj project file.","install_details":"1. copy the msbuild.vim to your vimfiles\/compilers directory. \r\n2. After vim started, select the msbuild as your compiler, or in your _vimrc file.\r\n3. Add Follow line to your .csproj file's common PropertyGroup\r\n    <GenerateFullPaths>True<\/GenerateFullPaths>\r\n\r\n<Project DefaultTargets=\"Build\" xmlns=\"http:\/\/schemas.microsoft.com\/developer\/msbuild\/2003\">\r\n  <PropertyGroup>\r\n    <ProjectType>Local<\/ProjectType>\r\n    <ProductVersion>8.0.50727<\/ProductVersion>\r\n    <SchemaVersion>2.0<\/SchemaVersion>\r\n    <ProjectGuid>{F684BBEC-2818-48B8-B84E-5D736979ECEE}<\/ProjectGuid>\r\n    <Configuration Condition=\" '$(Configuration)' == '' \">Debug<\/Configuration>\r\n    <Platform Condition=\" '$(Platform)' == '' \">AnyCPU<\/Platform>\r\n    <OutputType>Library<\/OutputType>\r\n    <GenerateFullPaths>True<\/GenerateFullPaths>\r\n    ...\r\n","5":"1. copy the msbuild.vim to your vimfiles\/compilers directory. \r\n2. After vim started, select the msbuild as your compiler, or in your _vimrc file.\r\n3. Add Follow line to your .csproj file's common PropertyGroup\r\n    <GenerateFullPaths>True<\/GenerateFullPaths>\r\n\r\n<Project DefaultTargets=\"Build\" xmlns=\"http:\/\/schemas.microsoft.com\/developer\/msbuild\/2003\">\r\n  <PropertyGroup>\r\n    <ProjectType>Local<\/ProjectType>\r\n    <ProductVersion>8.0.50727<\/ProductVersion>\r\n    <SchemaVersion>2.0<\/SchemaVersion>\r\n    <ProjectGuid>{F684BBEC-2818-48B8-B84E-5D736979ECEE}<\/ProjectGuid>\r\n    <Configuration Condition=\" '$(Configuration)' == '' \">Debug<\/Configuration>\r\n    <Platform Condition=\" '$(Platform)' == '' \">AnyCPU<\/Platform>\r\n    <OutputType>Library<\/OutputType>\r\n    <GenerateFullPaths>True<\/GenerateFullPaths>\r\n    ...\r\n","first_name":"Red","6":"Red","last_name":"Forks","7":"Forks","releases":[{"0":"1437","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"msbuild.vim","4":"msbuild.vim","src_id":"4920","5":"4920","creation_date":"1135449894","6":"1135449894"}]},"1436":{"script_id":"1436","0":"1436","script_name":"withdrawn","1":"withdrawn","script_type":"utility","2":"utility","summary":"withdrawn","3":"withdrawn","description":"withdrawn","4":"withdrawn","install_details":"Don't","5":"Don't","first_name":"Charles","6":"Charles","last_name":"Campbell","7":"Campbell","releases":[{"0":"1436","vim_version":"6.0","1":"6.0","script_version":"ignore thi","2":"ignore thi","version_comment":"I wish one could actually delete these mistakes...","3":"I wish one could actually delete these mistakes...","package":"ignorethis.vim","4":"ignorethis.vim","src_id":"4918","5":"4918","creation_date":"1135236560","6":"1135236560"}]},"1435":{"script_id":"1435","0":"1435","script_name":"HiMtchBrkt","1":"HiMtchBrkt","script_type":"utility","2":"utility","summary":"withdrawn","3":"withdrawn","description":"withdrawn -- the search engine bots got ahold of the \"unsatisfactory\" address and in one day -106 was dumped onto HiMtchBrkt's karma.  With the rating being so negative, few bother to look at HiMtchBrkt here anymore (and its largely for v6 of vim, anyway) You can still go to my website, http:\/\/www.drchip.org\/astronaut\/vim\/index.html#HIMTCHBRKT and get a copy.\r\n","4":"withdrawn -- the search engine bots got ahold of the \"unsatisfactory\" address and in one day -106 was dumped onto HiMtchBrkt's karma.  With the rating being so negative, few bother to look at HiMtchBrkt here anymore (and its largely for v6 of vim, anyway) You can still go to my website, http:\/\/www.drchip.org\/astronaut\/vim\/index.html#HIMTCHBRKT and get a copy.\r\n","install_details":"withdrawn","5":"withdrawn","first_name":"Charles","6":"Charles","last_name":"Campbell","7":"Campbell","releases":[{"0":"1435","vim_version":"7.0","1":"7.0","script_version":"W","2":"W","version_comment":"withdrawn","3":"withdrawn","package":"withdrawn.vim","4":"withdrawn.vim","src_id":"16763","5":"16763","creation_date":"1319813084","6":"1319813084"}]},"1434":{"script_id":"1434","0":"1434","script_name":"Dev C++ Scheme","1":"Dev C++ Scheme","script_type":"color scheme","2":"color scheme","summary":"Nice, clear, gentle, professional colorscheme from Dev-C++","3":"Nice, clear, gentle, professional colorscheme from Dev-C++","description":"Nice, clear, gentle, professional colorscheme from Dev-C++.\r\n\r\nBy Xi Chen, HyperNewbie, \r\nbased on the nice structure of the Visual C++ theme :)\r\n\r\nIts te default Dev-C++ theme with little fix-ups from Kate editor. Nice white-background theme that uses gentle colors and strong colors where appropriate, so you grab the right attention while not killing your eyes.\r\n\r\nShould work on most versions of vim...\r\n\r\n\r\n","4":"Nice, clear, gentle, professional colorscheme from Dev-C++.\r\n\r\nBy Xi Chen, HyperNewbie, \r\nbased on the nice structure of the Visual C++ theme :)\r\n\r\nIts te default Dev-C++ theme with little fix-ups from Kate editor. Nice white-background theme that uses gentle colors and strong colors where appropriate, so you grab the right attention while not killing your eyes.\r\n\r\nShould work on most versions of vim...\r\n\r\n\r\n","install_details":"","5":"","first_name":"Xi","6":"Xi","last_name":"Chen","7":"Chen","releases":[{"0":"1434","vim_version":"6.0","1":"6.0","script_version":"6.3","2":"6.3","version_comment":"Initial upload","3":"Initial upload","package":"DevC++.vim","4":"DevC++.vim","src_id":"4912","5":"4912","creation_date":"1135183868","6":"1135183868"}]},"1433":{"script_id":"1433","0":"1433","script_name":"haml.zip","1":"haml.zip","script_type":"syntax","2":"syntax","summary":"Haml and Sass syntax, indenting, and ftplugin","3":"Haml and Sass syntax, indenting, and ftplugin","description":"Runtime files for Haml and Sass. An older version is included with Vim 7.2. Newest version is on Github:\r\n\r\nhttp:\/\/github.com\/tpope\/vim-haml","4":"Runtime files for Haml and Sass. An older version is included with Vim 7.2. Newest version is on Github:\r\n\r\nhttp:\/\/github.com\/tpope\/vim-haml","install_details":"Extract in ~\/.vim or ~\\vimfiles.","5":"Extract in ~\/.vim or ~\\vimfiles.","first_name":"Tim","6":"Tim","last_name":"Pope","7":"Pope","releases":[{"0":"1433","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"haml.zip","4":"haml.zip","src_id":"11498","5":"11498","creation_date":"1255046606","6":"1255046606"}]},"1432":{"script_id":"1432","0":"1432","script_name":"textutil.vim","1":"textutil.vim","script_type":"utility","2":"utility","summary":"Vim plugin for editing rtf,rtfd,doc,wordml files.","3":"Vim plugin for editing rtf,rtfd,doc,wordml files.","description":"\r\n Usage:\r\n    When you open rtf, rtfd, doc or wordml file with Vim,\r\n    editing file format is automatically converted to plain text.\r\n    And when you write file, file format is automatically converted to\r\n    rtf, rtfd, doc or wordml file format.\r\n\r\n Configuration:\r\n    When this script convert rtf, rtfd, doc or wordml file to plain text with textutil command,\r\n    this script use \"g:textutil_txt_encoding\" encoding.\r\n    Default value of \"g:textutil_txt_encoding\" is 'utf-8'.\r\n    You want to change text encoding, set \"g:textutil_txt_encoding\" in your $HOME\/.vimrc file.\r\n    for example,\r\n\r\n        :let g:textutil_txt_encoding='Shift_JIS'\r\n\r\n Note:\r\n    This script is based on 'textutil' command.\r\n    So this script will only run on MacOS 10.4 or later.\r\n\r\n","4":"\r\n Usage:\r\n    When you open rtf, rtfd, doc or wordml file with Vim,\r\n    editing file format is automatically converted to plain text.\r\n    And when you write file, file format is automatically converted to\r\n    rtf, rtfd, doc or wordml file format.\r\n\r\n Configuration:\r\n    When this script convert rtf, rtfd, doc or wordml file to plain text with textutil command,\r\n    this script use \"g:textutil_txt_encoding\" encoding.\r\n    Default value of \"g:textutil_txt_encoding\" is 'utf-8'.\r\n    You want to change text encoding, set \"g:textutil_txt_encoding\" in your $HOME\/.vimrc file.\r\n    for example,\r\n\r\n        :let g:textutil_txt_encoding='Shift_JIS'\r\n\r\n Note:\r\n    This script is based on 'textutil' command.\r\n    So this script will only run on MacOS 10.4 or later.\r\n\r\n","install_details":"    1. Copy the textutil.vim script to the $HOME\/.vim\/plugin directory.\r\n       Refer to ':help add-plugin', ':help add-global-plugin' and ':help runtimepath'\r\n       for more details about Vim plugins.\r\n    2. Restart Vim.\r\n\r\n","5":"    1. Copy the textutil.vim script to the $HOME\/.vim\/plugin directory.\r\n       Refer to ':help add-plugin', ':help add-global-plugin' and ':help runtimepath'\r\n       for more details about Vim plugins.\r\n    2. Restart Vim.\r\n\r\n","first_name":"omi","6":"omi","last_name":"taku","7":"taku","releases":[{"0":"1432","vim_version":"6.0","1":"6.0","script_version":"0.1.1","2":"0.1.1","version_comment":"Add \"inputencoding\" textutil command option.","3":"Add \"inputencoding\" textutil command option.","package":"textutil.vim","4":"textutil.vim","src_id":"4898","5":"4898","creation_date":"1134719575","6":"1134719575"},{"0":"1432","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"textutil.vim","4":"textutil.vim","src_id":"4892","5":"4892","creation_date":"1134432594","6":"1134432594"}]},"1431":{"script_id":"1431","0":"1431","script_name":"checksyntax","1":"checksyntax","script_type":"utility","2":"utility","summary":"Check for syntax errors (r, javascript, php, ruby, tex ...)","3":"Check for syntax errors (r, javascript, php, ruby, tex ...)","description":"The checksyntax plugin runs an external syntax checker for the current buffer \r\nwhenever the buffer is saved (by calling the |:CheckSyntax| command). Syntax \r\nerrors are managed as location or quickfix lists. If any syntax error occurs, \r\nthe |location-list| is opened (users can redefine |CheckSyntaxFail()| to change \r\nthis behaviour). You can use any |location-list| related command to navigate \r\nthe list of syntax errors.\r\n\r\nMost syntax checks can be run asynchronously (from Vim 8 onwards or, for \r\nVim 7, if the AsyncCommand plugin is installed).\r\n\r\n\r\nInvocation~\r\n\r\nManual invocation:\r\nBy default, |:CheckSyntax| is mapped to <F5> (if not mapped already), and \r\nautomatically executed when saving the buffer. If multiple syntax checkers are \r\ndefined for the given filetype, this will by default invoke the preferred (see \r\n|g:checksyntax#preferred|) or first good (i.e. installed) syntax checker for a \r\ngiven filetype.\r\n\r\n:CheckSyntax! (with the optional <bang>) or <C-F5> will run all supported \r\nsyntax checkers for a given filetype if multiple syntax checkers are defined \r\nfor a given filetype and if the software is installed on your computer.\r\n\r\nAutomatic invocation:\r\nIn order to automatically run a syntax check when saving a file, please set \r\n|g:checksyntax#auto_filetypes| or |g:checksyntax#auto_enable_rx| to an \r\nappropriate value. If |g:checksyntax#auto_enable_rx| is set to '.', which \r\nmatches all filetypes, automatic syntax checks are enabled for all supported \r\nfiletypes. Automatic checks are equivalent to running |:CheckSyntax| with no \r\n<bang>.\r\n\r\n\r\nSupported filetypes~\r\n\r\nThe syntax checks are performed by external syntax checker. This software has \r\nto be installed on your computer. Pre-defined syntax checkers are:\r\n\r\n  bash         ... shellcheck, bash -n\r\n  c, cpp       ... splint\r\n  haskell      ... hlint, ghc-mod-check\r\n  html         ... tidy\r\n  java         ... jlint, checkstyle, pmd\r\n  javascript   ... jshint, esprima, gjslint, jslint, jsl, pmd\r\n  lua          ... luac (run luac -p)\r\n  perl         ... perl (run perl -Wc)\r\n  php          ... php (run php -l)\r\n  python       ... pyflakes or pylint\r\n  r            ... lintr\r\n  ruby         ... ruby (run ruby -c)\r\n  tex, latex   ... chktex (run chktex -q -v0)\r\n  typescript   ... tsc\r\n  viki         ... deplate\r\n  vim          ... vint\r\n  xhtml        ... tidy\r\n  xml, docbk   ... xmllint, pmd\r\n\r\nSyntax checker definitions are kept in:\r\nautoload\/checksyntax\/defs\/{&filetype}.vim\r\n\r\nRun this command to find out, which filetypes are supported: >\r\n\r\n  :echo globpath(&rtp, 'autoload\/checksyntax\/defs\/*.vim')\r\n","4":"The checksyntax plugin runs an external syntax checker for the current buffer \r\nwhenever the buffer is saved (by calling the |:CheckSyntax| command). Syntax \r\nerrors are managed as location or quickfix lists. If any syntax error occurs, \r\nthe |location-list| is opened (users can redefine |CheckSyntaxFail()| to change \r\nthis behaviour). You can use any |location-list| related command to navigate \r\nthe list of syntax errors.\r\n\r\nMost syntax checks can be run asynchronously (from Vim 8 onwards or, for \r\nVim 7, if the AsyncCommand plugin is installed).\r\n\r\n\r\nInvocation~\r\n\r\nManual invocation:\r\nBy default, |:CheckSyntax| is mapped to <F5> (if not mapped already), and \r\nautomatically executed when saving the buffer. If multiple syntax checkers are \r\ndefined for the given filetype, this will by default invoke the preferred (see \r\n|g:checksyntax#preferred|) or first good (i.e. installed) syntax checker for a \r\ngiven filetype.\r\n\r\n:CheckSyntax! (with the optional <bang>) or <C-F5> will run all supported \r\nsyntax checkers for a given filetype if multiple syntax checkers are defined \r\nfor a given filetype and if the software is installed on your computer.\r\n\r\nAutomatic invocation:\r\nIn order to automatically run a syntax check when saving a file, please set \r\n|g:checksyntax#auto_filetypes| or |g:checksyntax#auto_enable_rx| to an \r\nappropriate value. If |g:checksyntax#auto_enable_rx| is set to '.', which \r\nmatches all filetypes, automatic syntax checks are enabled for all supported \r\nfiletypes. Automatic checks are equivalent to running |:CheckSyntax| with no \r\n<bang>.\r\n\r\n\r\nSupported filetypes~\r\n\r\nThe syntax checks are performed by external syntax checker. This software has \r\nto be installed on your computer. Pre-defined syntax checkers are:\r\n\r\n  bash         ... shellcheck, bash -n\r\n  c, cpp       ... splint\r\n  haskell      ... hlint, ghc-mod-check\r\n  html         ... tidy\r\n  java         ... jlint, checkstyle, pmd\r\n  javascript   ... jshint, esprima, gjslint, jslint, jsl, pmd\r\n  lua          ... luac (run luac -p)\r\n  perl         ... perl (run perl -Wc)\r\n  php          ... php (run php -l)\r\n  python       ... pyflakes or pylint\r\n  r            ... lintr\r\n  ruby         ... ruby (run ruby -c)\r\n  tex, latex   ... chktex (run chktex -q -v0)\r\n  typescript   ... tsc\r\n  viki         ... deplate\r\n  vim          ... vint\r\n  xhtml        ... tidy\r\n  xml, docbk   ... xmllint, pmd\r\n\r\nSyntax checker definitions are kept in:\r\nautoload\/checksyntax\/defs\/{&filetype}.vim\r\n\r\nRun this command to find out, which filetypes are supported: >\r\n\r\n  :echo globpath(&rtp, 'autoload\/checksyntax\/defs\/*.vim')\r\n","install_details":"Edit the vba file and type: >\r\n\r\n    :so %\r\n\r\nSee :help vimball for details. If you have difficulties or use vim 7.0, \r\nplease make sure, you have the current version of vimball (vimscript \r\n#1502) installed or update your runtime.\r\n\r\nAlso available via git: http:\/\/github.com\/tomtom\/checksyntax_vim\/\r\n\r\n\r\nOptional enhancements~\r\n\r\nIf the quickfixsigns plugin (vimscript #2584) is installed, lines containing \r\nsyntax errors will be marked with signs.\r\n\r\nThe tinykeymap plugin (vimscript #4199) can be used to quickly move from one \r\nissue to the next by using it's quickfix or location-list maps (see \r\n|g:tinykeymap#map#qfl#map| and |g:tinykeymap#map#loc#map|).\r\n\r\nFor vim8+: Checks will be run asynchronously by default.\r\n\r\nFor vim7: If AsyncCommand (vimscript #3431) is installed, syntax checks can \r\nbe peformed asynchronously -- see also |g:checksyntax#run_alternatives|, \r\n|g:checksyntax#run_all_alternatives| and |g:checksyntax#async_runner|. This \r\nrequires a version of vim with |clientserver| support and |v:servername| to be \r\nset (for vim see also |--servername|).\r\n","5":"Edit the vba file and type: >\r\n\r\n    :so %\r\n\r\nSee :help vimball for details. If you have difficulties or use vim 7.0, \r\nplease make sure, you have the current version of vimball (vimscript \r\n#1502) installed or update your runtime.\r\n\r\nAlso available via git: http:\/\/github.com\/tomtom\/checksyntax_vim\/\r\n\r\n\r\nOptional enhancements~\r\n\r\nIf the quickfixsigns plugin (vimscript #2584) is installed, lines containing \r\nsyntax errors will be marked with signs.\r\n\r\nThe tinykeymap plugin (vimscript #4199) can be used to quickly move from one \r\nissue to the next by using it's quickfix or location-list maps (see \r\n|g:tinykeymap#map#qfl#map| and |g:tinykeymap#map#loc#map|).\r\n\r\nFor vim8+: Checks will be run asynchronously by default.\r\n\r\nFor vim7: If AsyncCommand (vimscript #3431) is installed, syntax checks can \r\nbe peformed asynchronously -- see also |g:checksyntax#run_alternatives|, \r\n|g:checksyntax#run_all_alternatives| and |g:checksyntax#async_runner|. This \r\nrequires a version of vim with |clientserver| support and |v:servername| to be \r\nset (for vim see also |--servername|).\r\n","first_name":"Tom","6":"Tom","last_name":"Link","7":"Link","releases":[{"0":"1431","vim_version":"7.0","1":"7.0","script_version":"5.00","2":"5.00","version_comment":"- Renamed g:checksyntax_enable_syntax to g:checksyntax#enable_syntax (allow g:checksyntax#enable_syntax_{&ft}; g:checksyntax#enable_syntax_\n- Trailing whitespace: Ignore before cursor position\n- tabs: highlight tabs\n- checkergen: JIT generation of checker definitions (e.g. multiple targets for haxe)\n- FIX #20: missing comma in defs\/lua.vim\n- FIX #21: s:Open(): lines was undefined\n- VimCheckSyntaxError: if =: ignore text after a \"|\" char\n- s:Open(): redraw! after resize\n- checksyntax#defs#haxe#Gen(): chxml is undefined if :HaxeCtags does not exist\n- FIX #22: mention perl support in docs\n- checksyntax#GetList(): Return only unique items\n- async_handler.get: Set bg & manually\n- Haskell: Support for hlint\n- vim syntax: Highlight \"else if\"\n- haskell: Support for ghc-mod check\n- checksyntax#Check(): check if key \"make_defs\" exists\n- Support for shellcheck\n- Initial support for rust\n- Scala: use fsc for basic checks\n- Scala: use -Xlint\n- FIX #24: Default value for g:checksyntax#async_runner\n- Add flake8 for checking python syntax and fix a bug\n- Simple definition for checking sourcode written in Google Go\n- Merge pull request #26 from thorn1976\/master\n- s:GetDefsByFiletype(): Return {} if buffer was modified\n- Duplicate helptags\n- Merge pull request #25 from yan12125\/master\n- FIX #25: s:GetValidAlternatives(): correct handling of \"first\" option\n- FIX #27: perl: Don't include -W flag\n- checksyntax#Check(): preferred_rx as 3th optional argument\n- checksyntax#RemoveJob(): Call TStatusForceUpdate() if necessary\n- haxe: Support for checksyntax\n- Add PHP_CodeSniffer checker for php.\n- phpcs: Use correct autoload variable names\n- php: Support for phpcs\n- tstatus integration\n- javascript: Updated gjslint definition\n- Merge pull request #31 from machinshin\/patch-1\n- FIX javascript\/gjslint efm\n- Support for vim8 async jobs\n- Updated r checker\n- Misc improvments to async checks\n- vim8: Revert callbacks\n- Implemented some checkers as compilers for easier testing\n- Run vint on autoload\/checksyntax.vim, chktex.vim\n- Support for vint (vim source files)\n- Support for csslint\n- Done(): How to handle loclists, when the buffer has changed?\n- Re-implemented scala checkers to compilers\n- checksyntax#GetChecker(): Optional is a regexp matching the names of eligible checkers\n- php: scriptencoding\n- r: Use ignore_rx\n- scalastyle: Define CheckSyntaxScalaStyleCmd() only once\n- Support for rmd (use r)\n- Misc refactoring, edits\n- Retrieve compiler parameters only once\n- Re-Implemented more checkers as compilers; removed some if_executable and convert_filename entries (those should be automatically detected)\n- :CheckSyntax, checksyntax#Check(): optional arguments have changed; background is set via g:checksyntax#background\n- checksyntax#Check(): FIX optional arguments in autocommand\nMD5 checksum: b346b86f808dc7ca3bc312103dd0d0be","3":"- Renamed g:checksyntax_enable_syntax to g:checksyntax#enable_syntax (allow g:checksyntax#enable_syntax_{&ft}; g:checksyntax#enable_syntax_\n- Trailing whitespace: Ignore before cursor position\n- tabs: highlight tabs\n- checkergen: JIT generation of checker definitions (e.g. multiple targets for haxe)\n- FIX #20: missing comma in defs\/lua.vim\n- FIX #21: s:Open(): lines was undefined\n- VimCheckSyntaxError: if =: ignore text after a \"|\" char\n- s:Open(): redraw! after resize\n- checksyntax#defs#haxe#Gen(): chxml is undefined if :HaxeCtags does not exist\n- FIX #22: mention perl support in docs\n- checksyntax#GetList(): Return only unique items\n- async_handler.get: Set bg & manually\n- Haskell: Support for hlint\n- vim syntax: Highlight \"else if\"\n- haskell: Support for ghc-mod check\n- checksyntax#Check(): check if key \"make_defs\" exists\n- Support for shellcheck\n- Initial support for rust\n- Scala: use fsc for basic checks\n- Scala: use -Xlint\n- FIX #24: Default value for g:checksyntax#async_runner\n- Add flake8 for checking python syntax and fix a bug\n- Simple definition for checking sourcode written in Google Go\n- Merge pull request #26 from thorn1976\/master\n- s:GetDefsByFiletype(): Return {} if buffer was modified\n- Duplicate helptags\n- Merge pull request #25 from yan12125\/master\n- FIX #25: s:GetValidAlternatives(): correct handling of \"first\" option\n- FIX #27: perl: Don't include -W flag\n- checksyntax#Check(): preferred_rx as 3th optional argument\n- checksyntax#RemoveJob(): Call TStatusForceUpdate() if necessary\n- haxe: Support for checksyntax\n- Add PHP_CodeSniffer checker for php.\n- phpcs: Use correct autoload variable names\n- php: Support for phpcs\n- tstatus integration\n- javascript: Updated gjslint definition\n- Merge pull request #31 from machinshin\/patch-1\n- FIX javascript\/gjslint efm\n- Support for vim8 async jobs\n- Updated r checker\n- Misc improvments to async checks\n- vim8: Revert callbacks\n- Implemented some checkers as compilers for easier testing\n- Run vint on autoload\/checksyntax.vim, chktex.vim\n- Support for vint (vim source files)\n- Support for csslint\n- Done(): How to handle loclists, when the buffer has changed?\n- Re-implemented scala checkers to compilers\n- checksyntax#GetChecker(): Optional is a regexp matching the names of eligible checkers\n- php: scriptencoding\n- r: Use ignore_rx\n- scalastyle: Define CheckSyntaxScalaStyleCmd() only once\n- Support for rmd (use r)\n- Misc refactoring, edits\n- Retrieve compiler parameters only once\n- Re-Implemented more checkers as compilers; removed some if_executable and convert_filename entries (those should be automatically detected)\n- :CheckSyntax, checksyntax#Check(): optional arguments have changed; background is set via g:checksyntax#background\n- checksyntax#Check(): FIX optional arguments in autocommand\nMD5 checksum: b346b86f808dc7ca3bc312103dd0d0be","package":"checksyntax.zip","4":"checksyntax.zip","src_id":"25028","5":"25028","creation_date":"1489271813","6":"1489271813"},{"0":"1431","vim_version":"7.0","1":"7.0","script_version":"4.03","2":"4.03","version_comment":"- g:checksyntax#null: upper-case NUL\n- Don't perform auto-checks when dying\n- g:checksyntax_enable_syntax: Highlight frequent beginner errors by means of regexps; set s:vimleave on VimLeave\n- g:checksyntax_enable_syntax: Improved handling; option to mark trailing whitespace\n- checksyntax_enable_syntax: Use own highlight group\n- vim syntax: Minor improvments\n- javascript: FIX no scope for global variables\n- Support for haxe\n- haxe: use -D no-compilation\n- FIX #19: Don't emulate autochdir if it isn't enabled\n- g:checksyntax_enable_syntax: disable by default\nMD5 checksum: 2870d7ccd62e1d7990665b07123c9da0","3":"- g:checksyntax#null: upper-case NUL\n- Don't perform auto-checks when dying\n- g:checksyntax_enable_syntax: Highlight frequent beginner errors by means of regexps; set s:vimleave on VimLeave\n- g:checksyntax_enable_syntax: Improved handling; option to mark trailing whitespace\n- checksyntax_enable_syntax: Use own highlight group\n- vim syntax: Minor improvments\n- javascript: FIX no scope for global variables\n- Support for haxe\n- haxe: use -D no-compilation\n- FIX #19: Don't emulate autochdir if it isn't enabled\n- g:checksyntax_enable_syntax: disable by default\nMD5 checksum: 2870d7ccd62e1d7990665b07123c9da0","package":"checksyntax.vba","4":"checksyntax.vba","src_id":"21672","5":"21672","creation_date":"1395839459","6":"1395839459"},{"0":"1431","vim_version":"7.0","1":"7.0","script_version":"4.02","2":"4.02","version_comment":"- checksyntax#Check(): Use fnameescape() for :lcd\n- php: Facilitate changing cmd & args\n- s:Executable(): Fix windows vs cygwin executables\n- r: Disable svTools::lint (it's only a shortcut to codetools)\nMD5 checksum: 59a1082c5e936b66f38b4a9e873516eb","3":"- checksyntax#Check(): Use fnameescape() for :lcd\n- php: Facilitate changing cmd & args\n- s:Executable(): Fix windows vs cygwin executables\n- r: Disable svTools::lint (it's only a shortcut to codetools)\nMD5 checksum: 59a1082c5e936b66f38b4a9e873516eb","package":"checksyntax.vba","4":"checksyntax.vba","src_id":"21577","5":"21577","creation_date":"1394127867","6":"1394127867"},{"0":"1431","vim_version":"7.0","1":"7.0","script_version":"4.01","2":"4.01","version_comment":"- Fix #17: error when running with noautochdir\n- Remove debug info\nMD5 checksum: 59458811257639ba95f13068aa0d289f","3":"- Fix #17: error when running with noautochdir\n- Remove debug info\nMD5 checksum: 59458811257639ba95f13068aa0d289f","package":"checksyntax.vba","4":"checksyntax.vba","src_id":"21538","5":"21538","creation_date":"1393445957","6":"1393445957"},{"0":"1431","vim_version":"7.0","1":"7.0","script_version":"4.00","2":"4.00","version_comment":"- Move AsyncCommand related code to autoload\/checksyntax\/async\/asynccommand.vim\n- Check validity of g:checksyntax#async_runner only when running an async check\n- Compile to \/dev\/null; properly handle tasks for async tasks\n- g:checksyntax#auto_enable_rx and g:checksyntax#auto_disable_rx replace g:checksyntax#auto_mode\n- javascript: Initial support for checkTypes by closure compiler\n- javascript: closure: g:checksyntax#defs#javascript#closure_warnings\n- Misc changes (use checksyntax#AddChecker() to define checkers) & cleanup\n- Don't use async if v:servername is empty (vim with clientserver)\n- Re-enable support for \"top-level field\"; some support for cygwin; misc improvements\n- Don't check for cygwin on non-windows OS\n- FIX pass filename when running synchronously\n- Minor improvement to acync commands\n- Support for scalastyle\n- Improved use of scalastyle\n- Support for pmd (java, javascript, xml); new options: cmd_args, buffers\n- Disable support for jlint\n- pmd: Use cmdexpr to provide for buffer-local options\n- Don't run make_def, if cmd is set but empty\n- scala: Use sbt scalastyle if there is a scalastyle-config.xml in the same dir as build.sbt\n- Make the qfl\/loc window adapt to the length of the issues list\n- Facilitate configuration of showing the error list\n- Use :resize to set qfl window height\nMD5 checksum: 1838eb8aeb4748b55d50511fc9fc6380","3":"- Move AsyncCommand related code to autoload\/checksyntax\/async\/asynccommand.vim\n- Check validity of g:checksyntax#async_runner only when running an async check\n- Compile to \/dev\/null; properly handle tasks for async tasks\n- g:checksyntax#auto_enable_rx and g:checksyntax#auto_disable_rx replace g:checksyntax#auto_mode\n- javascript: Initial support for checkTypes by closure compiler\n- javascript: closure: g:checksyntax#defs#javascript#closure_warnings\n- Misc changes (use checksyntax#AddChecker() to define checkers) & cleanup\n- Don't use async if v:servername is empty (vim with clientserver)\n- Re-enable support for \"top-level field\"; some support for cygwin; misc improvements\n- Don't check for cygwin on non-windows OS\n- FIX pass filename when running synchronously\n- Minor improvement to acync commands\n- Support for scalastyle\n- Improved use of scalastyle\n- Support for pmd (java, javascript, xml); new options: cmd_args, buffers\n- Disable support for jlint\n- pmd: Use cmdexpr to provide for buffer-local options\n- Don't run make_def, if cmd is set but empty\n- scala: Use sbt scalastyle if there is a scalastyle-config.xml in the same dir as build.sbt\n- Make the qfl\/loc window adapt to the length of the issues list\n- Facilitate configuration of showing the error list\n- Use :resize to set qfl window height\nMD5 checksum: 1838eb8aeb4748b55d50511fc9fc6380","package":"checksyntax.vba","4":"checksyntax.vba","src_id":"21528","5":"21528","creation_date":"1393264538","6":"1393264538"},{"0":"1431","vim_version":"7.0","1":"7.0","script_version":"3.00","2":"3.00","version_comment":"- addon-info\n- Help template\n- g:checksyntax#preferred defaults to {'xml': '.'}\n- g:checksyntax['xml'] use auto: 0 for xmllint\n- javascript: Support for esvalidate (esprima)\n- javascript: default to jshint\n- Support for running checkers asynchronously (requires the AsyncCommand vim plugin)\n- Updated errorformat for jslint 0.2.7\n- Support for typescript compiler (requires https:\/\/github.com\/leafgarland\/typescript-vim)\n- Experimental: Enable async processing when performing a full check (:CheckSyntax!) if AsyncCommand is installed\n- checksyntax#Check(): When mixing async & sync processing, don't show issue list if a check is still pending\n- When mixing sync & async & no pending checks: Include async results in sync results\n- Removed support for syntastic\n- async_handler.get(): Properly handle issues list when the last check yielded no new issues\n- Use job_ids to check for pending tasks\n- g:checksyntax#async_runner and related vars is set based on exists(':AsyncMake')\n- Show info about pending jobs (also support toptions_vim)\n- Correctly handle makeprgs with full filename\n- GetList(): Correctly handle \"process_list\" property\n- r options: Add --ess\n- Reset pending tasks, when calling CheckSyntax before all async tasks were completed\n- Improved integration with toptions_vim\n- R checker defaults to codetools::checkUsage\n- Tentative integration with airline\n- Support for tstatus (replaces toptions)\nMD5 checksum: c9a7ae5304038568ea2309ed13c8ed96","3":"- addon-info\n- Help template\n- g:checksyntax#preferred defaults to {'xml': '.'}\n- g:checksyntax['xml'] use auto: 0 for xmllint\n- javascript: Support for esvalidate (esprima)\n- javascript: default to jshint\n- Support for running checkers asynchronously (requires the AsyncCommand vim plugin)\n- Updated errorformat for jslint 0.2.7\n- Support for typescript compiler (requires https:\/\/github.com\/leafgarland\/typescript-vim)\n- Experimental: Enable async processing when performing a full check (:CheckSyntax!) if AsyncCommand is installed\n- checksyntax#Check(): When mixing async & sync processing, don't show issue list if a check is still pending\n- When mixing sync & async & no pending checks: Include async results in sync results\n- Removed support for syntastic\n- async_handler.get(): Properly handle issues list when the last check yielded no new issues\n- Use job_ids to check for pending tasks\n- g:checksyntax#async_runner and related vars is set based on exists(':AsyncMake')\n- Show info about pending jobs (also support toptions_vim)\n- Correctly handle makeprgs with full filename\n- GetList(): Correctly handle \"process_list\" property\n- r options: Add --ess\n- Reset pending tasks, when calling CheckSyntax before all async tasks were completed\n- Improved integration with toptions_vim\n- R checker defaults to codetools::checkUsage\n- Tentative integration with airline\n- Support for tstatus (replaces toptions)\nMD5 checksum: c9a7ae5304038568ea2309ed13c8ed96","package":"checksyntax.vba","4":"checksyntax.vba","src_id":"21436","5":"21436","creation_date":"1391758431","6":"1391758431"},{"0":"1431","vim_version":"7.0","1":"7.0","script_version":"2.03","2":"2.03","version_comment":"- Included missing files in vba (fixes #16)\nMD5 checksum: 40c9ea31d916db1ff5f22ec1c4af14c3","3":"- Included missing files in vba (fixes #16)\nMD5 checksum: 40c9ea31d916db1ff5f22ec1c4af14c3","package":"checksyntax.vba","4":"checksyntax.vba","src_id":"19321","5":"19321","creation_date":"1357500445","6":"1357500445"},{"0":"1431","vim_version":"7.0","1":"7.0","script_version":"2.02","2":"2.02","version_comment":"- Support for perl (by TheAthlete)\n- s:Make(): Echo v:exception & v:throwpoint\n- checksyntax#Alternative(): Copy top-level properties\n- Don't change the checker definition when dealing with alternatives (reported by techlivezheng)\nMD5 checksum: d2d95bcff1d039497bc9c95cdb7a0ea1","3":"- Support for perl (by TheAthlete)\n- s:Make(): Echo v:exception & v:throwpoint\n- checksyntax#Alternative(): Copy top-level properties\n- Don't change the checker definition when dealing with alternatives (reported by techlivezheng)\nMD5 checksum: d2d95bcff1d039497bc9c95cdb7a0ea1","package":"checksyntax.vba","4":"checksyntax.vba","src_id":"19018","5":"19018","creation_date":"1353655052","6":"1353655052"},{"0":"1431","vim_version":"7.0","1":"7.0","script_version":"2.01","2":"2.01","version_comment":"- Extra syntax checker definitions was prematurely removed after running a single syntax checker\n- Facilitate customization of maps (g:checksyntax_key_single, g:checksyntax_key_all)\n- process_list attribute for syntax checker definitions\n- Support for R (lint::lint, svTools::lint)\n- s:Executable(): Run executable() only once\n- SyntasticLoadChecker(): Accept filetype as optional argument\n- Support for jshint\nMD5 checksum: 617a9cc8fd1fac7533e75b721106f2ad","3":"- Extra syntax checker definitions was prematurely removed after running a single syntax checker\n- Facilitate customization of maps (g:checksyntax_key_single, g:checksyntax_key_all)\n- process_list attribute for syntax checker definitions\n- Support for R (lint::lint, svTools::lint)\n- s:Executable(): Run executable() only once\n- SyntasticLoadChecker(): Accept filetype as optional argument\n- Support for jshint\nMD5 checksum: 617a9cc8fd1fac7533e75b721106f2ad","package":"checksyntax.vba","4":"checksyntax.vba","src_id":"18506","5":"18506","creation_date":"1346175268","6":"1346175268"},{"0":"1431","vim_version":"7.0","1":"7.0","script_version":"2.00","2":"2.00","version_comment":"- Enable syntax checks when loading a file (disabled by default)\n- g:checksyntax#auto_mode: Default auto mode (fixes #10)\n- g:checksyntax#debug\n- s:GetDef(ft): Remove syntax checker definition if the command is not executable\n- Fix duplicate errors (closes bug #7)\n- checksyntax#auto_mode: 0 disable, 1 enable, 2 force (fixes #12)\n- checksyntax: \"if\" and \"alternatives\" fields; removed g:checksyntax_javascript\n- define g:checksyntax in plugin\/checksyntax.vim in order to facilitate customisation\n- s:GetDef(ft): If empty(rv), check if the rest of alternatives is empty\n- Move syntax checker definitions to autoload\/checksyntax\/&filetype.vim\n- php: run with php -l -d error_log= -d error_reporting=E_PARSE\n- Remove outdated references to failrx and okrx\n- Move syntax checker definitions to autoload\/checksyntax\/defs\/\n- Experimental support for syntastic syntax checkers.\n- debug message\n- Support for SyntasticLoadChecker()\n- checksyntax#Require(): Return 0 if filetype is empty\n- efm for jruby (see https:\/\/github.com\/tomtom\/checksyntax_vim\/pull\/13)\n- Run php with \"-d display_errors=0\" (fixes #7)\n- php: Use -d display_errors=0\n- checksyntax#syntastic#Require(): Make sure not to replace existing defintions\n- Experimental: Prepare for running all valid alternatives\n- Prepare for run_alternatives == \"all\"\n- Javascript: Support for jslint (fixes #14)\n- Run multiple syntax checkers (fixes #15)\n- javascript: Remove run_alternatives = all\n- Improved running all alternatives\n- Improved support for syntastic syntax checkers (in conjunction with run_alternatives == all)\n- :CheckSyntax! runs all alternatives (not the alternative syntax checker); use g:checksyntax#preferred for selecting the preferred checker\n- checksyntax#Name(): Also consider the value of compiler\n- s:CompleteItem(): Improved display of error message\n- checksyntax#Alternative(): Define an alternative\n- Updated syntax checker definitions for java, php, python\n- checksyntax#syntastic#Require(): Use checksyntax#Alternative()\n- checksyntax#syntastic#Require(): handle yet undefined filetypes\n- Syntastic: Improved display of the checker name\n- Support for bash -n\n- Call bash -n only if shell =~ bash\n- Facilitate configuration of g:checksyntax#prototypes.\n- Map <c-f5> to CheckSyntax!\nMD5 checksum: dfe8b09008f5106fdf7886d4c4cd5fb6","3":"- Enable syntax checks when loading a file (disabled by default)\n- g:checksyntax#auto_mode: Default auto mode (fixes #10)\n- g:checksyntax#debug\n- s:GetDef(ft): Remove syntax checker definition if the command is not executable\n- Fix duplicate errors (closes bug #7)\n- checksyntax#auto_mode: 0 disable, 1 enable, 2 force (fixes #12)\n- checksyntax: \"if\" and \"alternatives\" fields; removed g:checksyntax_javascript\n- define g:checksyntax in plugin\/checksyntax.vim in order to facilitate customisation\n- s:GetDef(ft): If empty(rv), check if the rest of alternatives is empty\n- Move syntax checker definitions to autoload\/checksyntax\/&filetype.vim\n- php: run with php -l -d error_log= -d error_reporting=E_PARSE\n- Remove outdated references to failrx and okrx\n- Move syntax checker definitions to autoload\/checksyntax\/defs\/\n- Experimental support for syntastic syntax checkers.\n- debug message\n- Support for SyntasticLoadChecker()\n- checksyntax#Require(): Return 0 if filetype is empty\n- efm for jruby (see https:\/\/github.com\/tomtom\/checksyntax_vim\/pull\/13)\n- Run php with \"-d display_errors=0\" (fixes #7)\n- php: Use -d display_errors=0\n- checksyntax#syntastic#Require(): Make sure not to replace existing defintions\n- Experimental: Prepare for running all valid alternatives\n- Prepare for run_alternatives == \"all\"\n- Javascript: Support for jslint (fixes #14)\n- Run multiple syntax checkers (fixes #15)\n- javascript: Remove run_alternatives = all\n- Improved running all alternatives\n- Improved support for syntastic syntax checkers (in conjunction with run_alternatives == all)\n- :CheckSyntax! runs all alternatives (not the alternative syntax checker); use g:checksyntax#preferred for selecting the preferred checker\n- checksyntax#Name(): Also consider the value of compiler\n- s:CompleteItem(): Improved display of error message\n- checksyntax#Alternative(): Define an alternative\n- Updated syntax checker definitions for java, php, python\n- checksyntax#syntastic#Require(): Use checksyntax#Alternative()\n- checksyntax#syntastic#Require(): handle yet undefined filetypes\n- Syntastic: Improved display of the checker name\n- Support for bash -n\n- Call bash -n only if shell =~ bash\n- Facilitate configuration of g:checksyntax#prototypes.\n- Map <c-f5> to CheckSyntax!\nMD5 checksum: dfe8b09008f5106fdf7886d4c4cd5fb6","package":"checksyntax.vba","4":"checksyntax.vba","src_id":"18501","5":"18501","creation_date":"1346088155","6":"1346088155"},{"0":"1431","vim_version":"7.0","1":"7.0","script_version":"1.03","2":"1.03","version_comment":"- checksyntax#Check: Check &modified before anything else\n- .gitignore\n- Support for \"modified\" property\n- Check executable() when setting the *.auto property.\n- When eclim is installed: Set g:checksyntax.php.auto, not b:checksyntax.php.auto\n- Do not map `<F5>` if it is used already.\n- Use either location list (default) or optionally the quickfix list\n- CheckSyntaxFail(): call .Open(); fixes #6\n- Tackle issue #7 ... maybe\n- php is now forced to display parse errors even when in production mode\n- Rename s:prototypes to g:checksyntax#prototypes\nMD5 checksum: dfe8b09008f5106fdf7886d4c4cd5fb6","3":"- checksyntax#Check: Check &modified before anything else\n- .gitignore\n- Support for \"modified\" property\n- Check executable() when setting the *.auto property.\n- When eclim is installed: Set g:checksyntax.php.auto, not b:checksyntax.php.auto\n- Do not map `<F5>` if it is used already.\n- Use either location list (default) or optionally the quickfix list\n- CheckSyntaxFail(): call .Open(); fixes #6\n- Tackle issue #7 ... maybe\n- php is now forced to display parse errors even when in production mode\n- Rename s:prototypes to g:checksyntax#prototypes\nMD5 checksum: dfe8b09008f5106fdf7886d4c4cd5fb6","package":"checksyntax.vba","4":"checksyntax.vba","src_id":"17287","5":"17287","creation_date":"1327167604","6":"1327167604"},{"0":"1431","vim_version":"7.0","1":"7.0","script_version":"1.01","2":"1.01","version_comment":"- checksyntax#Check: Check &modified before anything else\n- .gitignore\n- Support for \"modified\" property\n- Check executable() when setting the *.auto property.\n- When eclim is installed: Set g:checksyntax.php.auto, not b:checksyntax.php.auto\n- Do not map `<F5>` if it is used already.\n- Use either location list (default) or optionally the quickfix list\n- CheckSyntaxFail(): call .Open(); fixes #6\nMD5 checksum: 4425f1434baa8795fbccec38721eef67","3":"- checksyntax#Check: Check &modified before anything else\n- .gitignore\n- Support for \"modified\" property\n- Check executable() when setting the *.auto property.\n- When eclim is installed: Set g:checksyntax.php.auto, not b:checksyntax.php.auto\n- Do not map `<F5>` if it is used already.\n- Use either location list (default) or optionally the quickfix list\n- CheckSyntaxFail(): call .Open(); fixes #6\nMD5 checksum: 4425f1434baa8795fbccec38721eef67","package":"checksyntax.vba","4":"checksyntax.vba","src_id":"15729","5":"15729","creation_date":"1306393511","6":"1306393511"},{"0":"1431","vim_version":"7.0","1":"7.0","script_version":"1.01","2":"1.01","version_comment":"- Experimental support for python: pyflakes, pylint\n- redraw before calling CheckSyntaxSucceed\/CheckSyntaxFail\n- Make sure we're in the right buffer\nMD5 checksum: f94781c5748200e809a28562a692ed6b","3":"- Experimental support for python: pyflakes, pylint\n- redraw before calling CheckSyntaxSucceed\/CheckSyntaxFail\n- Make sure we're in the right buffer\nMD5 checksum: f94781c5748200e809a28562a692ed6b","package":"checksyntax.vba","4":"checksyntax.vba","src_id":"14237","5":"14237","creation_date":"1289499390","6":"1289499390"},{"0":"1431","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"- checksyntax_compiler_{&ft} & checksyntax_cmd_{&ft} variables can be buffer local\r\n- The info maintained as g:checksyntax_* variables is now kept in a dictionary named g:checksyntax\r\n- Support for gjslint\r\n- Some bug fixes (e.g. tidy)\r\n","3":"- checksyntax_compiler_{&ft} & checksyntax_cmd_{&ft} variables can be buffer local\r\n- The info maintained as g:checksyntax_* variables is now kept in a dictionary named g:checksyntax\r\n- Support for gjslint\r\n- Some bug fixes (e.g. tidy)\r\n","package":"checksyntax.vba","4":"checksyntax.vba","src_id":"14146","5":"14146","creation_date":"1288372506","6":"1288372506"},{"0":"1431","vim_version":"7.0","1":"7.0","script_version":"0.5","2":"0.5","version_comment":"- use vim compilers if available (e.g., tidy, xmllint ...)\r\n- Support for jsl (javascript lint).\r\n- Support for jlint.\r\n- Support for lua (thanks to norman)\r\n- Don't automatically check php files if eclim is installed.\r\n- Allow auto_* parameters to be buffer local.\r\n- FIX: Unlet current_compiler, use g:current_compiler\r\n- FIX: garbled screen: use redraw! (thanks to Vincent de Lau)\r\n- FIX: makeprg was restored in the wrong window\r\n","3":"- use vim compilers if available (e.g., tidy, xmllint ...)\r\n- Support for jsl (javascript lint).\r\n- Support for jlint.\r\n- Support for lua (thanks to norman)\r\n- Don't automatically check php files if eclim is installed.\r\n- Allow auto_* parameters to be buffer local.\r\n- FIX: Unlet current_compiler, use g:current_compiler\r\n- FIX: garbled screen: use redraw! (thanks to Vincent de Lau)\r\n- FIX: makeprg was restored in the wrong window\r\n","package":"checksyntax.vba.gz","4":"checksyntax.vba.gz","src_id":"11435","5":"11435","creation_date":"1253941453","6":"1253941453"},{"0":"1431","vim_version":"6.0","1":"6.0","script_version":"0.3","2":"0.3","version_comment":"Initial upload","3":"Initial upload","package":"checksyntax.zip","4":"checksyntax.zip","src_id":"4889","5":"4889","creation_date":"1134385078","6":"1134385078"}]},"1430":{"script_id":"1430","0":"1430","script_name":"please_remove_me","1":"please_remove_me","script_type":"utility","2":"utility","summary":"[removed]","3":"[removed]","description":"Sorry folks, this was one click too much. Please use vimscript #1431.","4":"Sorry folks, this was one click too much. Please use vimscript #1431.","install_details":"","5":"","first_name":"Tom","6":"Tom","last_name":"Link","7":"Link","releases":[{"0":"1430","vim_version":"6.0","1":"6.0","script_version":"0.3","2":"0.3","version_comment":"Initial upload","3":"Initial upload","package":"checksyntax.zip","4":"checksyntax.zip","src_id":"4888","5":"4888","creation_date":"1134385075","6":"1134385075"}]},"1429":{"script_id":"1429","0":"1429","script_name":"cfname","1":"cfname","script_type":"utility","2":"utility","summary":"Shows (or jumps to) the C\/C++ prototype of the function the cursor is in","3":"Shows (or jumps to) the C\/C++ prototype of the function the cursor is in","description":"This is a simple (limited) script for C\/C++ programmers.\r\nWhen editing source files with very long functions, it may happen the \r\nprogrammer does not know which function the current line is in (e.g. \r\nwhen using tags and jumping with Ctrl-] or jumping after a search). \r\nHere are some shortcuts to be typed in normal mode: \r\n   ff: shows the function prototype on the command line \r\n   fb: jumps to the function beginning \r\n   fe: jumps to the function end \r\n   ft: jumps back where the cursor was before typing 'fb' or 'fe'\r\n       (the first 'fb' or 'fe' if a sequence of them is typed)\r\n   fz: folds the function \r\n   fo: unfolds the function      \r\nAlso, the function name is visible between square brackets on the status \r\nline, with automatic update. To disable\/enable this feature on-the-go use 'fd'\/'fs'.\r\nTo disable it steadily, comment the statements \r\n'au BufRead,BufNewFile * CFunSetStatusByFileName' and\r\n'au BufEnter * CFunSetStatusByFileName' by putting a \" in front of them.\r\n\r\nNote that, by default, the status line is not visible when only one window is open.\r\nIf you like to have it always visible, add the statement 'set laststatus=2' in the script.\r\n\r\n\r\n***KNOWN ISSUES***: \r\n- The automatic update of the status bar may slow down or even block the cursor movements. \r\n  This has been experienced with VIM running on an UNIX machine; also experienced with\r\n  very large files and functions. Refer to the instructions above to disable the status line update. \r\n\r\n- In files with comments like \"\/\/ ... }\" (with unmatched '{' or '}' brackets), the script does not\r\n  work well (however, from version 2.2 on, the cursor should behave properly). \r\n  I think it will not be easy to fix this problem. \r\n\r\n\r\n***SPECIAL VERSION***\r\nThere is a special version 3.0a by Yakov Lerner. This version has two differences with respect\r\nto version 3.0:\r\n1) if the user has a non-standard status line, that is preserved and the function name information\r\n   is added to it (the status line is not changed to default);\r\n2) the status line is updated with the function name information only after a while if the\r\n   cursor position is held (it shows [...] before). That is useful if you feel window scrolling\r\n   is slowed down too much.\r\nWith version 3.0a, use a capital F as the first letter for shortcuts.\r\n\r\n\r\nNote that taglist.vim (vimscript #273), the most downloaded script, already does the job of showing \r\nthe function prototype, together with a lot more! However, try this little thing too!\r\n\r\n","4":"This is a simple (limited) script for C\/C++ programmers.\r\nWhen editing source files with very long functions, it may happen the \r\nprogrammer does not know which function the current line is in (e.g. \r\nwhen using tags and jumping with Ctrl-] or jumping after a search). \r\nHere are some shortcuts to be typed in normal mode: \r\n   ff: shows the function prototype on the command line \r\n   fb: jumps to the function beginning \r\n   fe: jumps to the function end \r\n   ft: jumps back where the cursor was before typing 'fb' or 'fe'\r\n       (the first 'fb' or 'fe' if a sequence of them is typed)\r\n   fz: folds the function \r\n   fo: unfolds the function      \r\nAlso, the function name is visible between square brackets on the status \r\nline, with automatic update. To disable\/enable this feature on-the-go use 'fd'\/'fs'.\r\nTo disable it steadily, comment the statements \r\n'au BufRead,BufNewFile * CFunSetStatusByFileName' and\r\n'au BufEnter * CFunSetStatusByFileName' by putting a \" in front of them.\r\n\r\nNote that, by default, the status line is not visible when only one window is open.\r\nIf you like to have it always visible, add the statement 'set laststatus=2' in the script.\r\n\r\n\r\n***KNOWN ISSUES***: \r\n- The automatic update of the status bar may slow down or even block the cursor movements. \r\n  This has been experienced with VIM running on an UNIX machine; also experienced with\r\n  very large files and functions. Refer to the instructions above to disable the status line update. \r\n\r\n- In files with comments like \"\/\/ ... }\" (with unmatched '{' or '}' brackets), the script does not\r\n  work well (however, from version 2.2 on, the cursor should behave properly). \r\n  I think it will not be easy to fix this problem. \r\n\r\n\r\n***SPECIAL VERSION***\r\nThere is a special version 3.0a by Yakov Lerner. This version has two differences with respect\r\nto version 3.0:\r\n1) if the user has a non-standard status line, that is preserved and the function name information\r\n   is added to it (the status line is not changed to default);\r\n2) the status line is updated with the function name information only after a while if the\r\n   cursor position is held (it shows [...] before). That is useful if you feel window scrolling\r\n   is slowed down too much.\r\nWith version 3.0a, use a capital F as the first letter for shortcuts.\r\n\r\n\r\nNote that taglist.vim (vimscript #273), the most downloaded script, already does the job of showing \r\nthe function prototype, together with a lot more! However, try this little thing too!\r\n\r\n","install_details":"Just drop the script into your plugin directory and restart VIM","5":"Just drop the script into your plugin directory and restart VIM","first_name":"Fabio","6":"Fabio","last_name":"Visona'","7":"Visona'","releases":[{"0":"1429","vim_version":"6.0","1":"6.0","script_version":"3.0","2":"3.0","version_comment":"The function name is now automatically displayed on the status bar only for *.c, *.cpp or *.cc files, because the status bar update caused the scrolling of non-c files to slow down unnecessarily. These changes have been contributed by Yakov Lerner.\r\n","3":"The function name is now automatically displayed on the status bar only for *.c, *.cpp or *.cc files, because the status bar update caused the scrolling of non-c files to slow down unnecessarily. These changes have been contributed by Yakov Lerner.\r\n","package":"Cfname.vim","4":"Cfname.vim","src_id":"5485","5":"5485","creation_date":"1143195937","6":"1143195937"},{"0":"1429","vim_version":"6.0","1":"6.0","script_version":"3.0a","2":"3.0a","version_comment":"Special version by Yakov Lerner (see description above)","3":"Special version by Yakov Lerner (see description above)","package":"Cfname.vim","4":"Cfname.vim","src_id":"5484","5":"5484","creation_date":"1143195820","6":"1143195820"},{"0":"1429","vim_version":"6.0","1":"6.0","script_version":"2.2","2":"2.2","version_comment":"- Added 'ft' to jump back where the cursor was before typing 'fb' or 'fe'\r\n- Added missing restoring of the cursor position in 'CF_GetPrototype' when \r\n  'searchpair' calls fail\r\n","3":"- Added 'ft' to jump back where the cursor was before typing 'fb' or 'fe'\r\n- Added missing restoring of the cursor position in 'CF_GetPrototype' when \r\n  'searchpair' calls fail\r\n","package":"Cfname.vim","4":"Cfname.vim","src_id":"4897","5":"4897","creation_date":"1134616399","6":"1134616399"},{"0":"1429","vim_version":"6.0","1":"6.0","script_version":"2.1","2":"2.1","version_comment":"Fixed bug: some ^M characters in the script lead to warning messages under UNIX\r\n","3":"Fixed bug: some ^M characters in the script lead to warning messages under UNIX\r\n","package":"Cfname.vim","4":"Cfname.vim","src_id":"4893","5":"4893","creation_date":"1134439019","6":"1134439019"},{"0":"1429","vim_version":"6.0","1":"6.0","script_version":"2.0","2":"2.0","version_comment":"Added automatic visualization of the function name in the status line;\r\nAdded \"fz\" and \"fo\" commands to fold\/unfold the function.\r\n","3":"Added automatic visualization of the function name in the status line;\r\nAdded \"fz\" and \"fo\" commands to fold\/unfold the function.\r\n","package":"Cfname.vim","4":"Cfname.vim","src_id":"4890","5":"4890","creation_date":"1134395899","6":"1134395899"},{"0":"1429","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"Cfname.vim","4":"Cfname.vim","src_id":"4887","5":"4887","creation_date":"1134382211","6":"1134382211"}]},"1428":{"script_id":"1428","0":"1428","script_name":"selection_eval.vim","1":"selection_eval.vim","script_type":"utility","2":"utility","summary":"Evaluate the statements which you select with visual mode.","3":"Evaluate the statements which you select with visual mode.","description":"Evaluate the statements which you select with visual mode.\r\n\r\nCommands:\r\nvmap <c-e><c-r> evaluate with using ruby.\r\nvmap <c-e><c-l> evaluate with using perl.\r\nvmap <c-e><c-p> evaluate with using python.\r\nvmap <c-e><c-s> evaluate with using shell(bash)\r\nvmap <c-e><c-v> evaluate with using vim.\r\n\r\nyou need to install the interpreter which you want to use.\r\n\r\nUsage: \r\n1. press <ctrl> + v\r\n2. select the snippets with visual mode.  cf) echo \"hello world\"\r\n3. press <c-e><c-v> or :EV (evaluate by vim.)\r\n4. you get the result in the another buffer.\r\n5. when you press the <e-c>c or :ECL, the result buffer is closed.\r\n\r\nReference: dbext.vim\r\n\r\nI use this scripts on FreeBSD5.4 and cygwin. (vim6.3)","4":"Evaluate the statements which you select with visual mode.\r\n\r\nCommands:\r\nvmap <c-e><c-r> evaluate with using ruby.\r\nvmap <c-e><c-l> evaluate with using perl.\r\nvmap <c-e><c-p> evaluate with using python.\r\nvmap <c-e><c-s> evaluate with using shell(bash)\r\nvmap <c-e><c-v> evaluate with using vim.\r\n\r\nyou need to install the interpreter which you want to use.\r\n\r\nUsage: \r\n1. press <ctrl> + v\r\n2. select the snippets with visual mode.  cf) echo \"hello world\"\r\n3. press <c-e><c-v> or :EV (evaluate by vim.)\r\n4. you get the result in the another buffer.\r\n5. when you press the <e-c>c or :ECL, the result buffer is closed.\r\n\r\nReference: dbext.vim\r\n\r\nI use this scripts on FreeBSD5.4 and cygwin. (vim6.3)","install_details":"cp selection_eval.vim $HOME\/.vim\/plugin \r\n","5":"cp selection_eval.vim $HOME\/.vim\/plugin \r\n","first_name":"shunsuke","6":"shunsuke","last_name":"tsutsui","7":"tsutsui","releases":[{"0":"1428","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"selection_eval.vim","4":"selection_eval.vim","src_id":"4885","5":"4885","creation_date":"1134370559","6":"1134370559"}]},"1427":{"script_id":"1427","0":"1427","script_name":"darkerdesert","1":"darkerdesert","script_type":"color scheme","2":"color scheme","summary":"A darker version of desert scheme, less radiation","3":"A darker version of desert scheme, less radiation","description":"Turn the original desert scheme (http:\/\/vim.sourceforge.net\/scripts\/script.php?script_id=105) into a darker one. The distinction between different  hightlight groups remains.","4":"Turn the original desert scheme (http:\/\/vim.sourceforge.net\/scripts\/script.php?script_id=105) into a darker one. The distinction between different  hightlight groups remains.","install_details":"1. drop it to $HOME\/.vim\/colors\r\n2. :colorscheme darkerdesert","5":"1. drop it to $HOME\/.vim\/colors\r\n2. :colorscheme darkerdesert","first_name":"Jing","6":"Jing","last_name":"Zhang","7":"Zhang","releases":[{"0":"1427","vim_version":"6.0","1":"6.0","script_version":"1.02","2":"1.02","version_comment":"Minor changes","3":"Minor changes","package":"darkerdesert.vim","4":"darkerdesert.vim","src_id":"4896","5":"4896","creation_date":"1134603985","6":"1134603985"},{"0":"1427","vim_version":"6.0","1":"6.0","script_version":"1.01","2":"1.01","version_comment":"Initial upload","3":"Initial upload","package":"darkerdesert.vim","4":"darkerdesert.vim","src_id":"4882","5":"4882","creation_date":"1134325598","6":"1134325598"}]},"1426":{"script_id":"1426","0":"1426","script_name":"CarvedWoodCool","1":"CarvedWoodCool","script_type":"color scheme","2":"color scheme","summary":"A variation of CarvedWood with a softer blue background","3":"A variation of CarvedWood with a softer blue background","description":"For those who prefer a blue background, this uses the same basic text scheme as CarvedWood, but with a softer blue background and side bars.\r\n\r\nCarvedWood can be found at:\r\nhttp:\/\/www.vim.org\/scripts\/script.php?script_id=1417\r\n\r\nSend comments and suggestions to:\r\naxs221@gmail.com","4":"For those who prefer a blue background, this uses the same basic text scheme as CarvedWood, but with a softer blue background and side bars.\r\n\r\nCarvedWood can be found at:\r\nhttp:\/\/www.vim.org\/scripts\/script.php?script_id=1417\r\n\r\nSend comments and suggestions to:\r\naxs221@gmail.com","install_details":"","5":"","first_name":"Shawn","6":"Shawn","last_name":"Axsom","7":"Axsom","releases":[{"0":"1426","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"carvedwoodcool.vim","4":"carvedwoodcool.vim","src_id":"4881","5":"4881","creation_date":"1134319117","6":"1134319117"}]},"1425":{"script_id":"1425","0":"1425","script_name":"iptables","1":"iptables","script_type":"syntax","2":"syntax","summary":"iptables-save\/restore syntax highlighter","3":"iptables-save\/restore syntax highlighter","description":"This vim syntax script highlights files used by Harald Welte's iptables-save\r\nand iptables-restore utilities.  Both utilities are part of the iptables\r\napplication (http:\/\/www.netfilter.org\/projects\/iptables).\r\n\r\nFeatures:\r\n\r\n  * Distinguishes commands, options, modules, targets and chains.\r\n  * Distinguishes numeric IP addresses from net masks.\r\n  * Highlights tokens that occur only in hand-edited files; for example,\r\n    \"--append\" and \"destination-unreachable\".\r\n  * Special handling for module names; for example, the tcp module is\r\n    colored differently from the tcp protocol.\r\n\r\nOptions:\r\n\r\n  Customize the behavior of this script by setting values for the following\r\n  options in your .vimrc file.  (Type \":h vimrc\" in vim for more information\r\n  on the .vimrc file.)\r\n\r\n  g:Iptables_SpecialDelimiters\r\n    This variable, if set to a non-zero value, distinguishes numeric\r\n    delimiters, including the dots in IP addresses, the slash that separates\r\n    an IP address from a netmask, and the colon that separates the ends of a\r\n    port range.  If not set, this option defaults to off.\r\n\r\nKnown Issues:\r\n\r\n  * Some special argument tokens are highlighted whether or not they are\r\n    used with the correct option.  For example, \"destination-unreachable\"\r\n    gets special highlighting whether or not is used as an argument to the\r\n    --icmp-type option.  In practice, this is rarely a problem.\r\n\r\nReporting Issues:\r\n\r\n  If you discover an iptables file that this script highlights incorrectly,\r\n  please email the author (address at the top of the script) with the\r\n  following information:\r\n\r\n    * Problem iptables file WITH ANY SENSITIVE INFORMATION REMOVED\r\n    * The release version of this script (see top of the script)\r\n    * If possible, a patch to fix the problem\r\n\r\nDesign Notes:\r\n\r\n  Part of this script is autogenerated from the output of the iptables man\r\n  page.  The source code for generating the script is available from the\r\n  author on request (see email address at the top of the script).  The\r\n  script should build from source on most Linux systems with iptables\r\n  installed.\r\n\r\n  The build system that generates this script strips special CVS tokens\r\n  (like \"Id:\") so that CVS no longer recognizes them.  This allows users to\r\n  place the script in their own version control system without losing\r\n  information.  The author encourages other vim script developers to adopt a\r\n  similar approach in their own scripts.\r\n","4":"This vim syntax script highlights files used by Harald Welte's iptables-save\r\nand iptables-restore utilities.  Both utilities are part of the iptables\r\napplication (http:\/\/www.netfilter.org\/projects\/iptables).\r\n\r\nFeatures:\r\n\r\n  * Distinguishes commands, options, modules, targets and chains.\r\n  * Distinguishes numeric IP addresses from net masks.\r\n  * Highlights tokens that occur only in hand-edited files; for example,\r\n    \"--append\" and \"destination-unreachable\".\r\n  * Special handling for module names; for example, the tcp module is\r\n    colored differently from the tcp protocol.\r\n\r\nOptions:\r\n\r\n  Customize the behavior of this script by setting values for the following\r\n  options in your .vimrc file.  (Type \":h vimrc\" in vim for more information\r\n  on the .vimrc file.)\r\n\r\n  g:Iptables_SpecialDelimiters\r\n    This variable, if set to a non-zero value, distinguishes numeric\r\n    delimiters, including the dots in IP addresses, the slash that separates\r\n    an IP address from a netmask, and the colon that separates the ends of a\r\n    port range.  If not set, this option defaults to off.\r\n\r\nKnown Issues:\r\n\r\n  * Some special argument tokens are highlighted whether or not they are\r\n    used with the correct option.  For example, \"destination-unreachable\"\r\n    gets special highlighting whether or not is used as an argument to the\r\n    --icmp-type option.  In practice, this is rarely a problem.\r\n\r\nReporting Issues:\r\n\r\n  If you discover an iptables file that this script highlights incorrectly,\r\n  please email the author (address at the top of the script) with the\r\n  following information:\r\n\r\n    * Problem iptables file WITH ANY SENSITIVE INFORMATION REMOVED\r\n    * The release version of this script (see top of the script)\r\n    * If possible, a patch to fix the problem\r\n\r\nDesign Notes:\r\n\r\n  Part of this script is autogenerated from the output of the iptables man\r\n  page.  The source code for generating the script is available from the\r\n  author on request (see email address at the top of the script).  The\r\n  script should build from source on most Linux systems with iptables\r\n  installed.\r\n\r\n  The build system that generates this script strips special CVS tokens\r\n  (like \"Id:\") so that CVS no longer recognizes them.  This allows users to\r\n  place the script in their own version control system without losing\r\n  information.  The author encourages other vim script developers to adopt a\r\n  similar approach in their own scripts.\r\n","install_details":"  Put this file in your user runtime syntax directory, usually ~\/.vim\/syntax\r\n  in *NIX or C:\\Program Files\\vim\\vimfiles\\syntax in Windows.  Type \":h\r\n  syn-files\" from within vim for more information.\r\n\r\n  The iptables-save and iptables-restore applications do not specify a\r\n  naming standard for the files they use.  However, iptables-save places a\r\n  comment in the first line of its output.  Other applications, such as\r\n  Fedora Core's system-config-securitylevel use the iptables-save\/restore\r\n  format, but with a different leading comment.  We can use these leading\r\n  comments to identify the filetype by placing the following code in the\r\n  scripts.vim file in your user runtime directory:\r\n  \r\n     if getline(1) =~ \"^# Generated by iptables-save\" ||\r\n      \\ getline(1) =~ \"^# Firewall configuration written by\"\r\n         setfiletype iptables\r\n         set commentstring=#%s\r\n         finish\r\n     endif\r\n\r\n  Setting the commentstring on line 4 allows Meikel Brandmeyer's\r\n  EnhancedCommentify script (vimscript #23) to work with iptables files.\r\n  (Advanced users may want to set the commentstring option in an ftplugin\r\n  file or in autocommands defined in .vimrc.)\r\n","5":"  Put this file in your user runtime syntax directory, usually ~\/.vim\/syntax\r\n  in *NIX or C:\\Program Files\\vim\\vimfiles\\syntax in Windows.  Type \":h\r\n  syn-files\" from within vim for more information.\r\n\r\n  The iptables-save and iptables-restore applications do not specify a\r\n  naming standard for the files they use.  However, iptables-save places a\r\n  comment in the first line of its output.  Other applications, such as\r\n  Fedora Core's system-config-securitylevel use the iptables-save\/restore\r\n  format, but with a different leading comment.  We can use these leading\r\n  comments to identify the filetype by placing the following code in the\r\n  scripts.vim file in your user runtime directory:\r\n  \r\n     if getline(1) =~ \"^# Generated by iptables-save\" ||\r\n      \\ getline(1) =~ \"^# Firewall configuration written by\"\r\n         setfiletype iptables\r\n         set commentstring=#%s\r\n         finish\r\n     endif\r\n\r\n  Setting the commentstring on line 4 allows Meikel Brandmeyer's\r\n  EnhancedCommentify script (vimscript #23) to work with iptables files.\r\n  (Advanced users may want to set the commentstring option in an ftplugin\r\n  file or in autocommands defined in .vimrc.)\r\n","first_name":"Eric","6":"Eric","last_name":"Haarbauer","7":"Haarbauer","releases":[{"0":"1425","vim_version":"7.0","1":"7.0","script_version":"1.09","2":"1.09","version_comment":"Updated for iptables 1.4.19.1.","3":"Updated for iptables 1.4.19.1.","package":"iptables.tar.bz2","4":"iptables.tar.bz2","src_id":"21999","5":"21999","creation_date":"1402197764","6":"1402197764"},{"0":"1425","vim_version":"7.0","1":"7.0","script_version":"1.08","2":"1.08","version_comment":"Updated for iptables 1.4.9.","3":"Updated for iptables 1.4.9.","package":"iptables.tar.bz2","4":"iptables.tar.bz2","src_id":"15041","5":"15041","creation_date":"1298080459","6":"1298080459"}]},"1424":{"script_id":"1424","0":"1424","script_name":"dtdmenu","1":"dtdmenu","script_type":"utility","2":"utility","summary":"DTD menu with skeletons","3":"DTD menu with skeletons","description":"Adds a Dtd menu. Dtd as in docbook and xhtml. e.g\r\n          <!DOCTYPE book PUBLIC \"-\/\/OASIS\/\/DTD DocBook XML V4.3\/\/EN\"\r\n\t      \"http:\/\/www.oasis-open.org\/docbook\/xml\/4.3\/docbookx.dtd\">\r\n\r\nit currently features 6 dtd's (xml docbook (2). HTML (3), XHTM(1))\r\nThe provided skeletons depends  on xml.vim for its expansion. \r\nIf you want to add your own DTD entries look in the file for instructions how to do that","4":"Adds a Dtd menu. Dtd as in docbook and xhtml. e.g\r\n          <!DOCTYPE book PUBLIC \"-\/\/OASIS\/\/DTD DocBook XML V4.3\/\/EN\"\r\n\t      \"http:\/\/www.oasis-open.org\/docbook\/xml\/4.3\/docbookx.dtd\">\r\n\r\nit currently features 6 dtd's (xml docbook (2). HTML (3), XHTM(1))\r\nThe provided skeletons depends  on xml.vim for its expansion. \r\nIf you want to add your own DTD entries look in the file for instructions how to do that","install_details":"cp dtdmenu.vim to your plugin directory","5":"cp dtdmenu.vim to your plugin directory","first_name":"Rene","6":"Rene","last_name":"de Zwart","7":"de Zwart","releases":[{"0":"1424","vim_version":"6.0","1":"6.0","script_version":"1.1","2":"1.1","version_comment":"Initial upload","3":"Initial upload","package":"dtdmenu.vim","4":"dtdmenu.vim","src_id":"4873","5":"4873","creation_date":"1134050400","6":"1134050400"}]},"1423":{"script_id":"1423","0":"1423","script_name":"corn","1":"corn","script_type":"color scheme","2":"color scheme","summary":"green + blue + wheat colorscheme","3":"green + blue + wheat colorscheme","description":"Simple colorscheme, only three to five different colors. The colors try to differentiate between reserved words and user created elements.","4":"Simple colorscheme, only three to five different colors. The colors try to differentiate between reserved words and user created elements.","install_details":"put into your .vim\/colors or vimfiles\\colors then type :colo corn","5":"put into your .vim\/colors or vimfiles\\colors then type :colo corn","first_name":"Char","6":"Char","last_name":"Only","7":"Only","releases":[{"0":"1423","vim_version":"6.0","1":"6.0","script_version":"0.01","2":"0.01","version_comment":"Initial upload","3":"Initial upload","package":"corn.vim","4":"corn.vim","src_id":"4871","5":"4871","creation_date":"1134027503","6":"1134027503"}]},"1422":{"script_id":"1422","0":"1422","script_name":"bufmap.vim","1":"bufmap.vim","script_type":"utility","2":"utility","summary":"automatically maps buffers to function keys","3":"automatically maps buffers to function keys","description":"A script that automatically maps buffers to function keys.\r\n\r\nKeys:\r\nF<n>\r\n        Switch to window 1 through 12.\r\nSHIFT-F<n>\r\n        Switch to window 13 through 24.\r\nALT-1 through ALT-0\r\n        Switch to window 1 through 10.\r\nCTRL-W, F<n>\r\n        Swap the buffer in the current window with the one\r\n        in window n, and activate window n.\r\nCTRL-W, SHIFT-F<n>\r\n        Swap the buffer in the current window with the one\r\n        in buffer n+12, and activate window n+12.\r\nCTRL-W, ALT-<n>\r\n        Swap the buffer in the current window with the one\r\n        in window n, and activate window n.\r\nCTRL-W, c\r\n        Close the current buffer. This does \":bdelete\",\r\n        so it will not work when there are unsaved changes.\r\n        Use \":bd!\" in this case if you want to discard them.\r\nCTRL-W, .\r\n        Move buffers along to lower numbered windows\r\n        (useful after closing a buffer)\r\nCTRL-W, \/\r\n        List all Windows.\r\n","4":"A script that automatically maps buffers to function keys.\r\n\r\nKeys:\r\nF<n>\r\n        Switch to window 1 through 12.\r\nSHIFT-F<n>\r\n        Switch to window 13 through 24.\r\nALT-1 through ALT-0\r\n        Switch to window 1 through 10.\r\nCTRL-W, F<n>\r\n        Swap the buffer in the current window with the one\r\n        in window n, and activate window n.\r\nCTRL-W, SHIFT-F<n>\r\n        Swap the buffer in the current window with the one\r\n        in buffer n+12, and activate window n+12.\r\nCTRL-W, ALT-<n>\r\n        Swap the buffer in the current window with the one\r\n        in window n, and activate window n.\r\nCTRL-W, c\r\n        Close the current buffer. This does \":bdelete\",\r\n        so it will not work when there are unsaved changes.\r\n        Use \":bd!\" in this case if you want to discard them.\r\nCTRL-W, .\r\n        Move buffers along to lower numbered windows\r\n        (useful after closing a buffer)\r\nCTRL-W, \/\r\n        List all Windows.\r\n","install_details":"Put in your plugin dir.\r\n","5":"Put in your plugin dir.\r\n","first_name":"Serge","6":"Serge","last_name":"van den Boom","7":"van den Boom","releases":[{"0":"1422","vim_version":"6.0","1":"6.0","script_version":"1.1","2":"1.1","version_comment":"Initial upload","3":"Initial upload","package":"bufmap.vim","4":"bufmap.vim","src_id":"4867","5":"4867","creation_date":"1133836280","6":"1133836280"}]},"1421":{"script_id":"1421","0":"1421","script_name":"softblue","1":"softblue","script_type":"color scheme","2":"color scheme","summary":"A blue color scheme, low contrast","3":"A blue color scheme, low contrast","description":"Only support gui version of vim.","4":"Only support gui version of vim.","install_details":"1. drop it to ~\/.vim\/colors\r\n2. :colorscheme softblue","5":"1. drop it to ~\/.vim\/colors\r\n2. :colorscheme softblue","first_name":"Jing","6":"Jing","last_name":"Zhang","7":"Zhang","releases":[{"0":"1421","vim_version":"6.0","1":"6.0","script_version":"1.07","2":"1.07","version_comment":"Change hi Special","3":"Change hi Special","package":"softblue.vim","4":"softblue.vim","src_id":"4922","5":"4922","creation_date":"1135623900","6":"1135623900"},{"0":"1421","vim_version":"6.0","1":"6.0","script_version":"1.06","2":"1.06","version_comment":"Change hi Special","3":"Change hi Special","package":"softblue.vim","4":"softblue.vim","src_id":"4909","5":"4909","creation_date":"1135129142","6":"1135129142"},{"0":"1421","vim_version":"6.0","1":"6.0","script_version":"1.05","2":"1.05","version_comment":"Minor changes","3":"Minor changes","package":"softblue.vim","4":"softblue.vim","src_id":"4899","5":"4899","creation_date":"1134790426","6":"1134790426"},{"0":"1421","vim_version":"6.0","1":"6.0","script_version":"1.04","2":"1.04","version_comment":"Make the background a little bit darker","3":"Make the background a little bit darker","package":"softblue.vim","4":"softblue.vim","src_id":"4870","5":"4870","creation_date":"1133999929","6":"1133999929"},{"0":"1421","vim_version":"6.0","1":"6.0","script_version":"1.03","2":"1.03","version_comment":"Add ErrorMsg, adjust Error & Visual","3":"Add ErrorMsg, adjust Error & Visual","package":"softblue.vim","4":"softblue.vim","src_id":"4868","5":"4868","creation_date":"1133895227","6":"1133895227"},{"0":"1421","vim_version":"6.0","1":"6.0","script_version":"1.02","2":"1.02","version_comment":"1. Change hl-Visual\r\n2. Adjust Statement, PreProc, et al.","3":"1. Change hl-Visual\r\n2. Adjust Statement, PreProc, et al.","package":"softblue.vim","4":"softblue.vim","src_id":"4866","5":"4866","creation_date":"1133830840","6":"1133830840"},{"0":"1421","vim_version":"6.0","1":"6.0","script_version":"1.01","2":"1.01","version_comment":"1. Add hl-VertSplit\r\n2. Adjust hl-Folded & hl-FoldColumn","3":"1. Add hl-VertSplit\r\n2. Adjust hl-Folded & hl-FoldColumn","package":"softblue.vim","4":"softblue.vim","src_id":"4864","5":"4864","creation_date":"1133807344","6":"1133807344"},{"0":"1421","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"softblue.vim","4":"softblue.vim","src_id":"4862","5":"4862","creation_date":"1133744646","6":"1133744646"}]},"1420":{"script_id":"1420","0":"1420","script_name":"openvpn","1":"openvpn","script_type":"syntax","2":"syntax","summary":"OpenVPN configuration syntax highlighter","3":"OpenVPN configuration syntax highlighter","description":"This vim syntax script highlights configuration files used with James\r\nYonan's OpenVPN application (http:\/\/openvpn.net).\r\n\r\nFeatures:\r\n\r\n  * Highlights options, comment lines, and arguments\r\n  * Recognizes quoted strings and escaped characters (e.g. \\\\, \\\")\r\n  * Flags arguments given for options that take no arguments\r\n  * Special highlighting for route and server command arguments\r\n\r\nReporting Issues:\r\n\r\n  If you discover an OpenVPN file that this script highlights incorrectly,\r\n  please email the author (address at the top of the file) with the\r\n  following information:\r\n\r\n    * Problem OpenVPN file WITH ANY SENSITIVE INFORMATION REMOVED\r\n    * The release version of this script (see top of the file)\r\n    * If possible, a patch to fix the problem\r\n\r\nDesign Notes:\r\n\r\n  Part of this script is autogenerated from the output of openvpn --help.\r\n  The source code for generating the script is available from the author on\r\n  request (see email address at the top of the script).  The script should\r\n  build from source on most Linux systems with openvpn installed.\r\n\r\n  The build system that generates this script strips special CVS tokens\r\n  (like \"Id:\") so that CVS no longer recognizes them.  This allows users to\r\n  place this script in their own version control system without losing\r\n  information.  The author encourages other vim script developers to adopt a\r\n  similar approach in their own scripts.\r\n","4":"This vim syntax script highlights configuration files used with James\r\nYonan's OpenVPN application (http:\/\/openvpn.net).\r\n\r\nFeatures:\r\n\r\n  * Highlights options, comment lines, and arguments\r\n  * Recognizes quoted strings and escaped characters (e.g. \\\\, \\\")\r\n  * Flags arguments given for options that take no arguments\r\n  * Special highlighting for route and server command arguments\r\n\r\nReporting Issues:\r\n\r\n  If you discover an OpenVPN file that this script highlights incorrectly,\r\n  please email the author (address at the top of the file) with the\r\n  following information:\r\n\r\n    * Problem OpenVPN file WITH ANY SENSITIVE INFORMATION REMOVED\r\n    * The release version of this script (see top of the file)\r\n    * If possible, a patch to fix the problem\r\n\r\nDesign Notes:\r\n\r\n  Part of this script is autogenerated from the output of openvpn --help.\r\n  The source code for generating the script is available from the author on\r\n  request (see email address at the top of the script).  The script should\r\n  build from source on most Linux systems with openvpn installed.\r\n\r\n  The build system that generates this script strips special CVS tokens\r\n  (like \"Id:\") so that CVS no longer recognizes them.  This allows users to\r\n  place this script in their own version control system without losing\r\n  information.  The author encourages other vim script developers to adopt a\r\n  similar approach in their own scripts.\r\n","install_details":"  Put this file in your user runtime syntax directory, usually ~\/.vim\/syntax\r\n  in *NIX or C:\\Program Files\\vim\\vimfiles\\syntax in Windows.  (Type \"h\r\n  syn-files\" from within vim for more information.)\r\n\r\n  Setting up automatic filetype definition requires some knowledge about\r\n  your system.  The OpenVPN application itself does not require a naming\r\n  standard for configuration files, although most distribution packages use\r\n  a .conf suffix.  However, the .conf suffix is also used by many other\r\n  applications with different syntaxes, so one cannot determine filetype by\r\n  filename alone.\r\n\r\n  One way to overcome this ambiguity is to incorporate the directory name\r\n  into the recognition process.  For example, adding the following lines to\r\n  the filetype.vim file in the user runtime directory should work for many\r\n  *NIX systems:\r\n     \r\n      au BufNewFile,BufRead *openvpn*\/*.conf setfiletype openvpn |\r\n                                          \\  set commentstring=#%s\r\n\r\n  On the Fedora Core Linux distribution, this technique recognizes\r\n  configuration files in \/etc\/openvpn and\r\n  \/usr\/share\/doc\/openvpn-X.X.X\/sample-config-files.  Setting the\r\n  commentstring option in the second line allows Meikel Brandmeyer's\r\n  EnhancedCommentify script (vimscript #23) to work with openvpn files.\r\n  (Advanced users may want to set the commentstring option in an ftplugin\r\n  file or in autocommands defined in .vimrc.)\r\n     \r\n  If filename- and directory-based recognition is impractical, the easiest\r\n  alternative is to embed the following modeline in your OpenVPN\r\n  configuration files:\r\n\r\n      # vim:ft=openvpn:\r\n","5":"  Put this file in your user runtime syntax directory, usually ~\/.vim\/syntax\r\n  in *NIX or C:\\Program Files\\vim\\vimfiles\\syntax in Windows.  (Type \"h\r\n  syn-files\" from within vim for more information.)\r\n\r\n  Setting up automatic filetype definition requires some knowledge about\r\n  your system.  The OpenVPN application itself does not require a naming\r\n  standard for configuration files, although most distribution packages use\r\n  a .conf suffix.  However, the .conf suffix is also used by many other\r\n  applications with different syntaxes, so one cannot determine filetype by\r\n  filename alone.\r\n\r\n  One way to overcome this ambiguity is to incorporate the directory name\r\n  into the recognition process.  For example, adding the following lines to\r\n  the filetype.vim file in the user runtime directory should work for many\r\n  *NIX systems:\r\n     \r\n      au BufNewFile,BufRead *openvpn*\/*.conf setfiletype openvpn |\r\n                                          \\  set commentstring=#%s\r\n\r\n  On the Fedora Core Linux distribution, this technique recognizes\r\n  configuration files in \/etc\/openvpn and\r\n  \/usr\/share\/doc\/openvpn-X.X.X\/sample-config-files.  Setting the\r\n  commentstring option in the second line allows Meikel Brandmeyer's\r\n  EnhancedCommentify script (vimscript #23) to work with openvpn files.\r\n  (Advanced users may want to set the commentstring option in an ftplugin\r\n  file or in autocommands defined in .vimrc.)\r\n     \r\n  If filename- and directory-based recognition is impractical, the easiest\r\n  alternative is to embed the following modeline in your OpenVPN\r\n  configuration files:\r\n\r\n      # vim:ft=openvpn:\r\n","first_name":"Eric","6":"Eric","last_name":"Haarbauer","7":"Haarbauer","releases":[{"0":"1420","vim_version":"7.0","1":"7.0","script_version":"1.11","2":"1.11","version_comment":"Upgraded to OpenVPN 2.3.2.","3":"Upgraded to OpenVPN 2.3.2.","package":"openvpn.tar.bz2","4":"openvpn.tar.bz2","src_id":"21998","5":"21998","creation_date":"1402196158","6":"1402196158"},{"0":"1420","vim_version":"7.0","1":"7.0","script_version":"1.10","2":"1.10","version_comment":"Upgraded to openvpn 2.1.1.","3":"Upgraded to openvpn 2.1.1.","package":"openvpn.tar.bz2","4":"openvpn.tar.bz2","src_id":"12713","5":"12713","creation_date":"1269664641","6":"1269664641"}]},"1419":{"script_id":"1419","0":"1419","script_name":"jadl.vim","1":"jadl.vim","script_type":"syntax","2":"syntax","summary":"Syntax highlighting for the JIAC Agent Description Language","3":"Syntax highlighting for the JIAC Agent Description Language","description":"The JIAC framework is the Java-based Intelligent Agent Componentware [http:\/\/www.jiac.de\/] developed at the DAI-Labor [http:\/\/www.dai-labor.de\/] at the Technical University of Berlin [http:\/\/www.tu-berlin.de\/].\r\n\r\nThis script provides syntax highlighting for the *.jadl and *.onto files which are used to program agents in the framework.\r\n\r\nThe official homepage of the script can be found at\r\nhttp:\/\/user.cs.tu-berlin.de\/~makunze\/vim-jiac.html","4":"The JIAC framework is the Java-based Intelligent Agent Componentware [http:\/\/www.jiac.de\/] developed at the DAI-Labor [http:\/\/www.dai-labor.de\/] at the Technical University of Berlin [http:\/\/www.tu-berlin.de\/].\r\n\r\nThis script provides syntax highlighting for the *.jadl and *.onto files which are used to program agents in the framework.\r\n\r\nThe official homepage of the script can be found at\r\nhttp:\/\/user.cs.tu-berlin.de\/~makunze\/vim-jiac.html","install_details":"Download the script file (jadl.vim)\r\n\r\nYou have to edit your ~\/.vimrc file and add the following lines:\r\n\r\nau BufRead,BufNewFile *.jadl set filetype=Jadl\r\nau BufRead,BufNewFile *.onto set filetype=Jadl\r\nau! Syntax Jadl source PATH_TO_JADL.VIM\/jadl.vim\r\n\r\nReplace the PATH_TO_JADL.VIM with the path to your jadl.vim. That's it, now you should have syntax highlighting if you edit *.jadl or *.onto files.","5":"Download the script file (jadl.vim)\r\n\r\nYou have to edit your ~\/.vimrc file and add the following lines:\r\n\r\nau BufRead,BufNewFile *.jadl set filetype=Jadl\r\nau BufRead,BufNewFile *.onto set filetype=Jadl\r\nau! Syntax Jadl source PATH_TO_JADL.VIM\/jadl.vim\r\n\r\nReplace the PATH_TO_JADL.VIM with the path to your jadl.vim. That's it, now you should have syntax highlighting if you edit *.jadl or *.onto files.","first_name":"Marco","6":"Marco","last_name":"Kunze","7":"Kunze","releases":[{"0":"1419","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"jadl.vim","4":"jadl.vim","src_id":"4854","5":"4854","creation_date":"1133523048","6":"1133523048"}]},"1418":{"script_id":"1418","0":"1418","script_name":"avs.vim","1":"avs.vim","script_type":"syntax","2":"syntax","summary":"syntax for avisynth script files (.avs)","3":"syntax for avisynth script files (.avs)","description":"This is a syntax file for avisynth http:\/\/www.avisynth.org a powerful tool for video post-production. It provides almost unlimited ways of editing and processing videos. AviSynth works as a frameserver, providing instant editing without the need for temporary files.\r\n\r\nThis syntax file attempts to add all of the avisynth filters to the syntax list, as well as comments, strings, and nubmers.  This helps make long avs scripts easier to read. \r\n\r\nI tried to include all of the third-party filters in this release, but there are A LOT of them!  Shoot me an email with a list of filters that you would like added to the syntax file and I will release a new version with an update. There are always new filters coming out.  ","4":"This is a syntax file for avisynth http:\/\/www.avisynth.org a powerful tool for video post-production. It provides almost unlimited ways of editing and processing videos. AviSynth works as a frameserver, providing instant editing without the need for temporary files.\r\n\r\nThis syntax file attempts to add all of the avisynth filters to the syntax list, as well as comments, strings, and nubmers.  This helps make long avs scripts easier to read. \r\n\r\nI tried to include all of the third-party filters in this release, but there are A LOT of them!  Shoot me an email with a list of filters that you would like added to the syntax file and I will release a new version with an update. There are always new filters coming out.  ","install_details":"Windows:  drop into C:\\Program Files\\Vim\\vimfiles\\syntax\r\nUNIX:         drop into ~\/.vim\/syntax\r\nadd this line to your ~\/.vimrc:\r\n   au BufNewFile,BufRead *.avs set syntax=avs","5":"Windows:  drop into C:\\Program Files\\Vim\\vimfiles\\syntax\r\nUNIX:         drop into ~\/.vim\/syntax\r\nadd this line to your ~\/.vimrc:\r\n   au BufNewFile,BufRead *.avs set syntax=avs","first_name":"Justin","6":"Justin","last_name":"Randall","7":"Randall","releases":[{"0":"1418","vim_version":"6.0","1":"6.0","script_version":"0.7.2","2":"0.7.2","version_comment":"Added syntax support for the BlendBob() function","3":"Added syntax support for the BlendBob() function","package":"avs.vim","4":"avs.vim","src_id":"4863","5":"4863","creation_date":"1133775673","6":"1133775673"}]},"1417":{"script_id":"1417","0":"1417","script_name":"carvedwood","1":"carvedwood","script_type":"color scheme","2":"color scheme","summary":"A dark (tan\/grey) color scheme for scanning Html","3":"A dark (tan\/grey) color scheme for scanning Html","description":"A typical tan on dark grey color scheme, with more important elements in HTML brightened. \r\n\r\nComments and suggestions are greatly appreciated:\r\n  axs221@gmail.com","4":"A typical tan on dark grey color scheme, with more important elements in HTML brightened. \r\n\r\nComments and suggestions are greatly appreciated:\r\n  axs221@gmail.com","install_details":"Add to _vimrc\/.vimrc:\r\ncolorscheme carvedwood","5":"Add to _vimrc\/.vimrc:\r\ncolorscheme carvedwood","first_name":"Shawn","6":"Shawn","last_name":"Axsom","7":"Axsom","releases":[{"0":"1417","vim_version":"6.0","1":"6.0","script_version":"0.7c","2":"0.7c","version_comment":"Changes to the Terminal; I mostly reduced the amount of red colors to try to reduce the stress without losing resemblance to the GUI.","3":"Changes to the Terminal; I mostly reduced the amount of red colors to try to reduce the stress without losing resemblance to the GUI.","package":"carvedwood.vim","4":"carvedwood.vim","src_id":"5436","5":"5436","creation_date":"1142345434","6":"1142345434"},{"0":"1417","vim_version":"6.0","1":"6.0","script_version":"0.7b","2":"0.7b","version_comment":"Reverted to v0.5c colors and added new Terminal colors to closer resemble the GUI.","3":"Reverted to v0.5c colors and added new Terminal colors to closer resemble the GUI.","package":"carvedwood.vim","4":"carvedwood.vim","src_id":"5415","5":"5415","creation_date":"1142120175","6":"1142120175"},{"0":"1417","vim_version":"6.0","1":"6.0","script_version":"0.5c","2":"0.5c","version_comment":"Minor changes","3":"Minor changes","package":"carvedwood.vim","4":"carvedwood.vim","src_id":"4852","5":"4852","creation_date":"1133475501","6":"1133475501"},{"0":"1417","vim_version":"6.0","1":"6.0","script_version":"0.4","2":"0.4","version_comment":"A few more changes to the side bars and background, changed Nontext to match the new background.","3":"A few more changes to the side bars and background, changed Nontext to match the new background.","package":"carvedwood.vim","4":"carvedwood.vim","src_id":"4841","5":"4841","creation_date":"1133424303","6":"1133424303"},{"0":"1417","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"carvedwood.vim","4":"carvedwood.vim","src_id":"4836","5":"4836","creation_date":"1133374480","6":"1133374480"}]},"1416":{"script_id":"1416","0":"1416","script_name":"shorewall.vim","1":"shorewall.vim","script_type":"syntax","2":"syntax","summary":"Shorewall syntax highlighting","3":"Shorewall syntax highlighting","description":"This is a first approach to make a syntax check and highlighting script for shorewall (http:\/\/www.shorewall.net). \r\n\r\nIt's not heavily tested yet, but it works. It renders you a nice colored rules file and it also check for basic typing errors such as invalid characters, mistyped protocol names or incorrect white spaces that may prevent  the firewall to start.","4":"This is a first approach to make a syntax check and highlighting script for shorewall (http:\/\/www.shorewall.net). \r\n\r\nIt's not heavily tested yet, but it works. It renders you a nice colored rules file and it also check for basic typing errors such as invalid characters, mistyped protocol names or incorrect white spaces that may prevent  the firewall to start.","install_details":"","5":"","first_name":"Pablo","6":"Pablo","last_name":"Hoffman","7":"Hoffman","releases":[{"0":"1416","vim_version":"6.0","1":"6.0","script_version":"0.2","2":"0.2","version_comment":"Fixed some valid syntax with comments at the end of line. Thanks Daniel Gra\u00c3\u00b1a.\r\n","3":"Fixed some valid syntax with comments at the end of line. Thanks Daniel Gra\u00c3\u00b1a.\r\n","package":"shorewall.vim","4":"shorewall.vim","src_id":"6689","5":"6689","creation_date":"1170088790","6":"1170088790"},{"0":"1416","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"shorewall.vim","4":"shorewall.vim","src_id":"4834","5":"4834","creation_date":"1133326507","6":"1133326507"}]},"1415":{"script_id":"1415","0":"1415","script_name":"Auto-debug your vim","1":"Auto-debug your vim","script_type":"utility","2":"utility","summary":"Debug your vim automatically","3":"Debug your vim automatically","description":"Read this bash script  through and modify to your needs.\r\nRun it instead of vim directly.\r\n\r\nHope this helps to make vim more stable.\r\nAny comments, suggestions are welcome.\r\n","4":"Read this bash script  through and modify to your needs.\r\nRun it instead of vim directly.\r\n\r\nHope this helps to make vim more stable.\r\nAny comments, suggestions are welcome.\r\n","install_details":"Modify this bash script as you wish.","5":"Modify this bash script as you wish.","first_name":"Bela","6":"Bela","last_name":"Nagy","7":"Nagy","releases":[{"0":"1415","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"vimd","4":"vimd","src_id":"4833","5":"4833","creation_date":"1133317461","6":"1133317461"}]},"1414":{"script_id":"1414","0":"1414","script_name":"bibFindIndex","1":"bibFindIndex","script_type":"ftplugin","2":"ftplugin","summary":"Jump to an index in an alphabetically ordered file","3":"Jump to an index in an alphabetically ordered file","description":"This is a small ftplugin that helps jumping to a key in a bibtex file. \r\nIt assumes a bibtex file that is alphabethically ordered by the bibitem \r\nkey. Maybe some people will find this useful.\r\n\r\nType <LocalLeader>g and a bibtex-key you want to find.\r\nType <LocalLeader>n to jump to the next key in line.\r\n\r\nExample use:\r\n\r\nIf the keys in the file were: \r\n    \r\n    @article{aa,\r\n    ...}\r\n    @article{ab\r\n    ...}\r\n    @article{aba\r\n    ...}\r\n    @article{ac\r\n    ...}\r\n\r\nthen '<LL>gab<cr>' would take you to \"ab\" but '<LL>nab<cr>' to \"ac\". \r\nActually BibGotoNextIndex is the main reason for why I wrote this one.\r\n\r\nIf g:bibFindIndexAllowSpaces is true, the \"entry head\" may include whitespace. \r\n(I'm not sure if this is legal bibtex, though.)\r\n","4":"This is a small ftplugin that helps jumping to a key in a bibtex file. \r\nIt assumes a bibtex file that is alphabethically ordered by the bibitem \r\nkey. Maybe some people will find this useful.\r\n\r\nType <LocalLeader>g and a bibtex-key you want to find.\r\nType <LocalLeader>n to jump to the next key in line.\r\n\r\nExample use:\r\n\r\nIf the keys in the file were: \r\n    \r\n    @article{aa,\r\n    ...}\r\n    @article{ab\r\n    ...}\r\n    @article{aba\r\n    ...}\r\n    @article{ac\r\n    ...}\r\n\r\nthen '<LL>gab<cr>' would take you to \"ab\" but '<LL>nab<cr>' to \"ac\". \r\nActually BibGotoNextIndex is the main reason for why I wrote this one.\r\n\r\nIf g:bibFindIndexAllowSpaces is true, the \"entry head\" may include whitespace. \r\n(I'm not sure if this is legal bibtex, though.)\r\n","install_details":"Copy the file to ~\/.vim\/ftplugin\/bib\/\r\n\r\nAlso available via git\r\nhttp:\/\/github.com\/tomtom\/vimtlib\/tree\/master\r\n","5":"Copy the file to ~\/.vim\/ftplugin\/bib\/\r\n\r\nAlso available via git\r\nhttp:\/\/github.com\/tomtom\/vimtlib\/tree\/master\r\n","first_name":"Tom","6":"Tom","last_name":"Link","7":"Link","releases":[{"0":"1414","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"bibFindIndex.vim","4":"bibFindIndex.vim","src_id":"4829","5":"4829","creation_date":"1133260732","6":"1133260732"}]},"1413":{"script_id":"1413","0":"1413","script_name":"brsccs.vim","1":"brsccs.vim","script_type":"utility","2":"utility","summary":"an SCCS browser","3":"an SCCS browser","description":"        It allows you to scroll the history back and forth  looking at how the code has changed in a convenient way.\r\n\r\n       Very helpful if you work with Sun Studio + Vim + TeamWare.\r\n\r\n        To start browsing an sccs file press ,v\r\n\r\n        Two windows will pop up: sccs versions and sccs browser.\r\n        In the sccs browser you see the text annotated by the version numbers.\r\n        Each line has the version number when it has changed the last time.\r\n        Press enter in any such line and you jump right to that version.\r\n        Press ,< and you jump right \"under\" that version. I.e. right before\r\n        that line was changed.\r\n       The plugin tries to track your position in the file so that you stay on the same line when move through the history\r\n\r\n        enter           go to the version that annotation specifies\r\n        ,v              start the SCCS browser\r\n        ,-              go back one version\r\n        ,+ or ,=        go forward one version\r\n        ,<              go one version earlier than the annotation specifies\r\n\r\n","4":"        It allows you to scroll the history back and forth  looking at how the code has changed in a convenient way.\r\n\r\n       Very helpful if you work with Sun Studio + Vim + TeamWare.\r\n\r\n        To start browsing an sccs file press ,v\r\n\r\n        Two windows will pop up: sccs versions and sccs browser.\r\n        In the sccs browser you see the text annotated by the version numbers.\r\n        Each line has the version number when it has changed the last time.\r\n        Press enter in any such line and you jump right to that version.\r\n        Press ,< and you jump right \"under\" that version. I.e. right before\r\n        that line was changed.\r\n       The plugin tries to track your position in the file so that you stay on the same line when move through the history\r\n\r\n        enter           go to the version that annotation specifies\r\n        ,v              start the SCCS browser\r\n        ,-              go back one version\r\n        ,+ or ,=        go forward one version\r\n        ,<              go one version earlier than the annotation specifies\r\n\r\n","install_details":"Drop the brsccs.vim into ~\/.vim\/plugin\/","5":"Drop the brsccs.vim into ~\/.vim\/plugin\/","first_name":"horsh","6":"horsh","last_name":"horsh","7":"horsh","releases":[{"0":"1413","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"brsccs.tar.gz","4":"brsccs.tar.gz","src_id":"4828","5":"4828","creation_date":"1133247520","6":"1133247520"}]},"1412":{"script_id":"1412","0":"1412","script_name":"vim_colors","1":"vim_colors","script_type":"color scheme","2":"color scheme","summary":"4 Vim Themes I use for programming (GUI only)","3":"4 Vim Themes I use for programming (GUI only)","description":"These are 4 themes I made which I prefer for programming, pyte.vim for example is a light and clear one which uses italic mode for pronouncing something, quite fun when programming python (or any other language).\r\nThe color-themes will be readably in the console I suppose (since I stole parts from other themes), but are intended to use with a gui such as gvim.","4":"These are 4 themes I made which I prefer for programming, pyte.vim for example is a light and clear one which uses italic mode for pronouncing something, quite fun when programming python (or any other language).\r\nThe color-themes will be readably in the console I suppose (since I stole parts from other themes), but are intended to use with a gui such as gvim.","install_details":"just put the contents of this .tar.gz-file to .vim\/colors in yout Home directory (windows users may have a different directory such as _vim\\colors)","5":"just put the contents of this .tar.gz-file to .vim\/colors in yout Home directory (windows users may have a different directory such as _vim\\colors)","first_name":"Henning","6":"Henning","last_name":"Hasemann","7":"Hasemann","releases":[{"0":"1412","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"vim_colors.tar.gz","4":"vim_colors.tar.gz","src_id":"4827","5":"4827","creation_date":"1133234495","6":"1133234495"}]},"1411":{"script_id":"1411","0":"1411","script_name":"bwTemplate","1":"bwTemplate","script_type":"utility","2":"utility","summary":"This script is used to load templates to buffers with different filetypes","3":"This script is used to load templates to buffers with different filetypes","description":"This script can be used to load template files just to save time. It shows templates for current buffer's filetype, you can choose one and load it. Some templates are distributed with this script, and I will\r\nadd more if I have time. Of course, you can post your templates to me if you like, and I will add them to this package and your name to this script, :-)\r\n","4":"This script can be used to load template files just to save time. It shows templates for current buffer's filetype, you can choose one and load it. Some templates are distributed with this script, and I will\r\nadd more if I have time. Of course, you can post your templates to me if you like, and I will add them to this package and your name to this script, :-)\r\n","install_details":"Drop the script(including bwLibUI.vim and libList.vim distributed with it) to your plugin directory. And you can place the 'templates' directory where you prefer. But DONNOT forget to set the 'g:bwTemplateDir' variable to it.","5":"Drop the script(including bwLibUI.vim and libList.vim distributed with it) to your plugin directory. And you can place the 'templates' directory where you prefer. But DONNOT forget to set the 'g:bwTemplateDir' variable to it.","first_name":"Bruce","6":"Bruce","last_name":"Who","7":"Who","releases":[{"0":"1411","vim_version":"6.0","1":"6.0","script_version":"1.7","2":"1.7","version_comment":"Initial upload","3":"Initial upload","package":"bwTemplate1.7.zip","4":"bwTemplate1.7.zip","src_id":"4825","5":"4825","creation_date":"1133205985","6":"1133205985"}]},"1410":{"script_id":"1410","0":"1410","script_name":"Workspace Manager","1":"Workspace Manager","script_type":"utility","2":"utility","summary":"Plugin for managing groups of files","3":"Plugin for managing groups of files","description":"The workspace plugin allows you to easily access groups of frequently used\r\nfiles and run any command on a selected set of files from the workspace.\r\n\r\nYou can create one or more groups in a workspace. Each group can contain\r\nadditional sub-groups. The workspace and the groups can contain one or more\r\nfilenames.\r\n\r\nThe contents of a workspace are saved in a user specified file. This allows\r\nyou to create multiple workspaces and to load the desired workspace when\r\nneeded.\r\n\r\nYou can run any Vim ex command or an external shell command on a selected\r\ngroup of files from the workspace.\r\n\r\nFor more information about using this plugin, after installing the\r\nworkspace plugin, use the \":help workspace\" command.\r\n\r\nThe workspace plugin manual is also available online at:\r\n     http:\/\/www.geocities.com\/yegappan\/workspace\/workspace.html\r\n","4":"The workspace plugin allows you to easily access groups of frequently used\r\nfiles and run any command on a selected set of files from the workspace.\r\n\r\nYou can create one or more groups in a workspace. Each group can contain\r\nadditional sub-groups. The workspace and the groups can contain one or more\r\nfilenames.\r\n\r\nThe contents of a workspace are saved in a user specified file. This allows\r\nyou to create multiple workspaces and to load the desired workspace when\r\nneeded.\r\n\r\nYou can run any Vim ex command or an external shell command on a selected\r\ngroup of files from the workspace.\r\n\r\nFor more information about using this plugin, after installing the\r\nworkspace plugin, use the \":help workspace\" command.\r\n\r\nThe workspace plugin manual is also available online at:\r\n     http:\/\/www.geocities.com\/yegappan\/workspace\/workspace.html\r\n","install_details":"1. Download the workspace.zip file and unzip the files to the $HOME\/.vim\r\n   or the $HOME\/vimfiles or the $VIM\/vimfiles directory. This should\r\n   unzip the following two files (the directory structure should be\r\n   preserved):\r\n\r\n      plugin\/workspace.vim - main workspace plugin file\r\n      doc\/workspace.txt    - documentation (help) file\r\n\r\n   Refer to the 'add-plugin', 'add-global-plugin' and 'runtimepath'\r\n   Vim help pages for more details about installing Vim plugins.\r\n2. Change to the $HOME\/.vim\/doc or $HOME\/vimfiles\/doc or\r\n   $VIM\/vimfiles\/doc directory, start Vim and run the \":helptags .\"\r\n   command to process the workspace help file.\r\n3. If you are running a terminal\/console version of Vim and the terminal\r\n    doesn't support changing the window width then set the \r\n    'Ws_Inc_Winwidth' variable to 0 in the .vimrc file.\r\n5. Restart Vim.\r\n6. You can now use the \":WsOpen <filename>\" command to open a\r\n     workspace. You can use the \":help workspace\" command to get \r\n     more information about using the workspace plugin.\r\n","5":"1. Download the workspace.zip file and unzip the files to the $HOME\/.vim\r\n   or the $HOME\/vimfiles or the $VIM\/vimfiles directory. This should\r\n   unzip the following two files (the directory structure should be\r\n   preserved):\r\n\r\n      plugin\/workspace.vim - main workspace plugin file\r\n      doc\/workspace.txt    - documentation (help) file\r\n\r\n   Refer to the 'add-plugin', 'add-global-plugin' and 'runtimepath'\r\n   Vim help pages for more details about installing Vim plugins.\r\n2. Change to the $HOME\/.vim\/doc or $HOME\/vimfiles\/doc or\r\n   $VIM\/vimfiles\/doc directory, start Vim and run the \":helptags .\"\r\n   command to process the workspace help file.\r\n3. If you are running a terminal\/console version of Vim and the terminal\r\n    doesn't support changing the window width then set the \r\n    'Ws_Inc_Winwidth' variable to 0 in the .vimrc file.\r\n5. Restart Vim.\r\n6. You can now use the \":WsOpen <filename>\" command to open a\r\n     workspace. You can use the \":help workspace\" command to get \r\n     more information about using the workspace plugin.\r\n","first_name":"Yegappan","6":"Yegappan","last_name":"Lakshmanan","7":"Lakshmanan","releases":[{"0":"1410","vim_version":"6.0","1":"6.0","script_version":"1.0 Beta 1","2":"1.0 Beta 1","version_comment":"Initial upload.","3":"Initial upload.","package":"workspace_1b1.zip","4":"workspace_1b1.zip","src_id":"4812","5":"4812","creation_date":"1133131169","6":"1133131169"}]},"1409":{"script_id":"1409","0":"1409","script_name":"OMNeT++ NED syntax file","1":"OMNeT++ NED syntax file","script_type":"syntax","2":"syntax","summary":"Syntax file for OMNeT++ NED files","3":"Syntax file for OMNeT++ NED files","description":"I didn't find a syntax file for the network description language of the OMNeT++ network simulator. Its files are called *.ned.\r\n\r\nThis syntax file just does basic highlighting and doesn't know any regions or areas. I will maybe change this when I learned how to do it ;)\r\n\r\nIf somebody has a better syntax file for this filetype, please tell me!","4":"I didn't find a syntax file for the network description language of the OMNeT++ network simulator. Its files are called *.ned.\r\n\r\nThis syntax file just does basic highlighting and doesn't know any regions or areas. I will maybe change this when I learned how to do it ;)\r\n\r\nIf somebody has a better syntax file for this filetype, please tell me!","install_details":"copy to ~\/.vim\/syntax\r\nadd to your ~\/.vimrc:\r\n   au BufNewFile,BufRead *.ned set syntax=ned\r\nthat should be all.\r\nPreviously, I had the line \r\n   au Filetype ned set syntax=ned\r\nBut I found out that this doesn't work with every installation, so use the one above...","5":"copy to ~\/.vim\/syntax\r\nadd to your ~\/.vimrc:\r\n   au BufNewFile,BufRead *.ned set syntax=ned\r\nthat should be all.\r\nPreviously, I had the line \r\n   au Filetype ned set syntax=ned\r\nBut I found out that this doesn't work with every installation, so use the one above...","first_name":"Timo","6":"Timo","last_name":"Teifel","7":"Teifel","releases":[{"0":"1409","vim_version":"6.0","1":"6.0","script_version":"0.2","2":"0.2","version_comment":"new keywords added\r\nrecognises numbers\r\nmade it more portable (I read the right chapter in the help ;-) )","3":"new keywords added\r\nrecognises numbers\r\nmade it more portable (I read the right chapter in the help ;-) )","package":"ned.vim","4":"ned.vim","src_id":"4813","5":"4813","creation_date":"1133161266","6":"1133161266"},{"0":"1409","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"ned.vim","4":"ned.vim","src_id":"4809","5":"4809","creation_date":"1132897707","6":"1132897707"}]},"1408":{"script_id":"1408","0":"1408","script_name":"Local configuration","1":"Local configuration","script_type":"utility","2":"utility","summary":"Use different settings for different directories.","3":"Use different settings for different directories.","description":"I work in a project which involves contribution from many other people each with their own coding style. This script helps to load files from different places but with the right settings. I use \"ts=4, sw=4, ...\" in directories i use, and set it to \"ts=8, sw=8, ...\" in the root of the linux kernel directory. These configurations are stored in a file called .lvimrc, subdirectories inherit the settings from their parent unless the subdirectory itself doesnot have a .lvimrc file.\r\n","4":"I work in a project which involves contribution from many other people each with their own coding style. This script helps to load files from different places but with the right settings. I use \"ts=4, sw=4, ...\" in directories i use, and set it to \"ts=8, sw=8, ...\" in the root of the linux kernel directory. These configurations are stored in a file called .lvimrc, subdirectories inherit the settings from their parent unless the subdirectory itself doesnot have a .lvimrc file.\r\n","install_details":"Either copy the content to your vimrc file \r\n (or)\r\nSource this file in your vimrc.\r\n\r\nCreate .lvimrc file with the necessary settings in folder you want to customize.","5":"Either copy the content to your vimrc file \r\n (or)\r\nSource this file in your vimrc.\r\n\r\nCreate .lvimrc file with the necessary settings in folder you want to customize.","first_name":"Vijairaj","6":"Vijairaj","last_name":"R","7":"R","releases":[{"0":"1408","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"localrc.vim","4":"localrc.vim","src_id":"4805","5":"4805","creation_date":"1132807798","6":"1132807798"}]},"1407":{"script_id":"1407","0":"1407","script_name":"DesertedOceanBurnt","1":"DesertedOceanBurnt","script_type":"color scheme","2":"color scheme","summary":"A dull, low saturation version of desertedocean","3":"A dull, low saturation version of desertedocean","description":"This is a low saturation\/dull version of my desertedocean color scheme. I wanted a separate version in the same style as Zenburn, better for low light situations or extended periods of use.\r\n\r\ndesertedocean (high saturation version): http:\/\/www.vim.org\/scripts\/script.php?script_id=1404\r\n---------------------------------------------------------------------------------------------------------------------\r\nThis color scheme has a dark greyish blue background and a blue number line and folding column, and has shades of tan (from orange to wheat) for highlighting syntax. This scheme is made for a GUI; terminal colors are still set to the defaults set by the Desert color scheme. I made this scheme using Desert as a starting point and looked to make it have similar qualities with OceanDeep and Zenburn as well. The final result uses mostly a sandy foreground with a fairly high contrast with the greyish blue background.\r\n\r\nFeedback is appreciated!\r\nEmail comments or suggestions to axs221@gmail.com.\r\nVisit my homepage at http:\/\/axs221.1l.com. ","4":"This is a low saturation\/dull version of my desertedocean color scheme. I wanted a separate version in the same style as Zenburn, better for low light situations or extended periods of use.\r\n\r\ndesertedocean (high saturation version): http:\/\/www.vim.org\/scripts\/script.php?script_id=1404\r\n---------------------------------------------------------------------------------------------------------------------\r\nThis color scheme has a dark greyish blue background and a blue number line and folding column, and has shades of tan (from orange to wheat) for highlighting syntax. This scheme is made for a GUI; terminal colors are still set to the defaults set by the Desert color scheme. I made this scheme using Desert as a starting point and looked to make it have similar qualities with OceanDeep and Zenburn as well. The final result uses mostly a sandy foreground with a fairly high contrast with the greyish blue background.\r\n\r\nFeedback is appreciated!\r\nEmail comments or suggestions to axs221@gmail.com.\r\nVisit my homepage at http:\/\/axs221.1l.com. ","install_details":"","5":"","first_name":"Shawn","6":"Shawn","last_name":"Axsom","7":"Axsom","releases":[{"0":"1407","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"desertedoceanburnt.vim","4":"desertedoceanburnt.vim","src_id":"4777","5":"4777","creation_date":"1132435916","6":"1132435916"}]},"1406":{"script_id":"1406","0":"1406","script_name":"impactG","1":"impactG","script_type":"color scheme","2":"color scheme","summary":"Modification of the original impact colorscheme","3":"Modification of the original impact colorscheme","description":"This was done by Adam Blinkinsop and is a modification of my impact colorscheme.\r\nThis version now contains support for GVim.\r\n\r\nThank's Adam!","4":"This was done by Adam Blinkinsop and is a modification of my impact colorscheme.\r\nThis version now contains support for GVim.\r\n\r\nThank's Adam!","install_details":"","5":"","first_name":"Ren\u00c3\u00a9","6":"Ren\u00c3\u00a9","last_name":"K\u00c3\u00b6cher","7":"K\u00c3\u00b6cher","releases":[{"0":"1406","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"impactG.vim","4":"impactG.vim","src_id":"4766","5":"4766","creation_date":"1132096463","6":"1132096463"}]},"1405":{"script_id":"1405","0":"1405","script_name":"understated","1":"understated","script_type":"color scheme","2":"color scheme","summary":"cterm and gui defs, for sensitive eyes","3":"cterm and gui defs, for sensitive eyes","description":"This is a dark-background colorscheme with enough definition to easily make out all text, but without any colors that are super-bright.  Need a graphical terminal (cterm) or gui.","4":"This is a dark-background colorscheme with enough definition to easily make out all text, but without any colors that are super-bright.  Need a graphical terminal (cterm) or gui.","install_details":"Copy this file to your ~\/.vim\/colors directory, enable with \":colorscheme understated\"","5":"Copy this file to your ~\/.vim\/colors directory, enable with \":colorscheme understated\"","first_name":"Adam","6":"Adam","last_name":"Blinkinsop","7":"Blinkinsop","releases":[{"0":"1405","vim_version":"6.0","1":"6.0","script_version":"1.3","2":"1.3","version_comment":"Switched to Unix EOLs.","3":"Switched to Unix EOLs.","package":"understated.vim","4":"understated.vim","src_id":"5023","5":"5023","creation_date":"1138787666","6":"1138787666"},{"0":"1405","vim_version":"6.0","1":"6.0","script_version":"1.2","2":"1.2","version_comment":"Added diff colors","3":"Added diff colors","package":"understated.vim","4":"understated.vim","src_id":"4761","5":"4761","creation_date":"1131988635","6":"1131988635"},{"0":"1405","vim_version":"6.0","1":"6.0","script_version":"1.1","2":"1.1","version_comment":"Changed Special from Blue to DarkYellow.","3":"Changed Special from Blue to DarkYellow.","package":"understated.vim","4":"understated.vim","src_id":"4760","5":"4760","creation_date":"1131987956","6":"1131987956"},{"0":"1405","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"understated.vim","4":"understated.vim","src_id":"4758","5":"4758","creation_date":"1131979754","6":"1131979754"}]},"1404":{"script_id":"1404","0":"1404","script_name":"desertedocean.vim","1":"desertedocean.vim","script_type":"color scheme","2":"color scheme","summary":"Tan\/blue GUI color scheme modified from Desert, akin to OceanDeep, & Zenburn","3":"Tan\/blue GUI color scheme modified from Desert, akin to OceanDeep, & Zenburn","description":"------------------------Screenshot--------------------------\r\nhttp:\/\/axs221.1l.com\/desertedocean.gif (Updated)\r\n------------------------------------------------------------------\r\n\r\nAlso try out the dull, low contrast version: http:\/\/www.vim.org\/scripts\/script.php?script_id=1407\r\n\r\nThis color scheme has a dark greyish blue background and a blue number line and folding column, and has shades of tan (from orange to wheat) for highlighting syntax. This scheme is made for a GUI; terminal colors are still set to the defaults set by the Desert color scheme. I made this scheme using Desert as a starting point and looked to make it have similar qualities with OceanDeep and Zenburn as well. The final result uses mostly a sandy foreground with a fairly high contrast with the greyish blue background.\r\n\r\nFeedback is appreciated! I will respond to any questions.\r\nEmail comments or suggestions to axs221@gmail.com.\r\nVisit my homepage at http:\/\/axs221.1l.com.\r\n","4":"------------------------Screenshot--------------------------\r\nhttp:\/\/axs221.1l.com\/desertedocean.gif (Updated)\r\n------------------------------------------------------------------\r\n\r\nAlso try out the dull, low contrast version: http:\/\/www.vim.org\/scripts\/script.php?script_id=1407\r\n\r\nThis color scheme has a dark greyish blue background and a blue number line and folding column, and has shades of tan (from orange to wheat) for highlighting syntax. This scheme is made for a GUI; terminal colors are still set to the defaults set by the Desert color scheme. I made this scheme using Desert as a starting point and looked to make it have similar qualities with OceanDeep and Zenburn as well. The final result uses mostly a sandy foreground with a fairly high contrast with the greyish blue background.\r\n\r\nFeedback is appreciated! I will respond to any questions.\r\nEmail comments or suggestions to axs221@gmail.com.\r\nVisit my homepage at http:\/\/axs221.1l.com.\r\n","install_details":"","5":"","first_name":"Shawn","6":"Shawn","last_name":"Axsom","7":"Axsom","releases":[{"0":"1404","vim_version":"7.0","1":"7.0","script_version":"0.5","2":"0.5","version_comment":"Added Pmenu values, thanks goes to Panos Laganakos","3":"Added Pmenu values, thanks goes to Panos Laganakos","package":"desertedocean.vim","4":"desertedocean.vim","src_id":"5802","5":"5802","creation_date":"1149519800","6":"1149519800"},{"0":"1404","vim_version":"6.0","1":"6.0","script_version":"0.4","2":"0.4","version_comment":"Changed Preproc and Constant to a shade of purple (more readible than dark red against the dark blue\/green background)","3":"Changed Preproc and Constant to a shade of purple (more readible than dark red against the dark blue\/green background)","package":"desertedocean.vim","4":"desertedocean.vim","src_id":"4762","5":"4762","creation_date":"1132034590","6":"1132034590"},{"0":"1404","vim_version":"6.0","1":"6.0","script_version":"0.3","2":"0.3","version_comment":"Increased the contrast in the background and removed some of the red hue. Changed the file status bar to shades of blue (from the Desert wheat color). Let me know if you like the new Normal background, or if it needs more adjusting.","3":"Increased the contrast in the background and removed some of the red hue. Changed the file status bar to shades of blue (from the Desert wheat color). Let me know if you like the new Normal background, or if it needs more adjusting.","package":"desertedocean.vim","4":"desertedocean.vim","src_id":"4752","5":"4752","creation_date":"1131820917","6":"1131820917"},{"0":"1404","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"desertedoceaninit.vim","4":"desertedoceaninit.vim","src_id":"4749","5":"4749","creation_date":"1131817727","6":"1131817727"}]},"1403":{"script_id":"1403","0":"1403","script_name":"gnupg-symmetric.vim","1":"gnupg-symmetric.vim","script_type":"utility","2":"utility","summary":"Plugin to transparently work with GPG-symmetric-encrypted (using AES) files.","3":"Plugin to transparently work with GPG-symmetric-encrypted (using AES) files.","description":"This plugin is designed to automatically decrypt\/encrypt GPG files which were encrypted with a passphrase (a.k.a. symmetric encryption using the AES cipher).  It is designed to be secure and robust.  You can replace AES with AES128, AES256 or any other ciphers supported by your gpg.","4":"This plugin is designed to automatically decrypt\/encrypt GPG files which were encrypted with a passphrase (a.k.a. symmetric encryption using the AES cipher).  It is designed to be secure and robust.  You can replace AES with AES128, AES256 or any other ciphers supported by your gpg.","install_details":"To use this script, add the following line to your ~\/.vimrc file:\r\n\r\n:source \/path\/to\/gnupg-symmetric.vim\r\n","5":"To use this script, add the following line to your ~\/.vimrc file:\r\n\r\n:source \/path\/to\/gnupg-symmetric.vim\r\n","first_name":"Konstantin","6":"Konstantin","last_name":"Rozinov","7":"Rozinov","releases":[{"0":"1403","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"deleted.","3":"deleted.","package":"empty.txt","4":"empty.txt","src_id":"4765","5":"4765","creation_date":"1132075548","6":"1132075548"}]},"1402":{"script_id":"1402","0":"1402","script_name":"DarkZen Color Scheme","1":"DarkZen Color Scheme","script_type":"color scheme","2":"color scheme","summary":"DarkZen color scheme for Vim","3":"DarkZen color scheme for Vim","description":"DarkZen is a color scheme for black background terminals with elegant and clean look and feel. This color scheme was developed on Mac OS X but it also looks great on Ubuntu Linux. \r\n\r\nNOTE: this color scheme is deprecated, I recommend to install Satori color scheme http:\/\/www.vim.org\/scripts\/script.php?script_id=1614 ","4":"DarkZen is a color scheme for black background terminals with elegant and clean look and feel. This color scheme was developed on Mac OS X but it also looks great on Ubuntu Linux. \r\n\r\nNOTE: this color scheme is deprecated, I recommend to install Satori color scheme http:\/\/www.vim.org\/scripts\/script.php?script_id=1614 ","install_details":"Download darkzen.vim \r\nmkdir -p .vim\/colors\/ \r\nmv darkzen.vim .vim\/colors\/ \r\nEdit your .vimrc and insert \"colorscheme darkzen\"","5":"Download darkzen.vim \r\nmkdir -p .vim\/colors\/ \r\nmv darkzen.vim .vim\/colors\/ \r\nEdit your .vimrc and insert \"colorscheme darkzen\"","first_name":"Rud\u00c3\u00a1","6":"Rud\u00c3\u00a1","last_name":"Moura","7":"Moura","releases":[{"0":"1402","vim_version":"7.2","1":"7.2","script_version":"2010","2":"2010","version_comment":"Updated my email","3":"Updated my email","package":"darkzen.vim","4":"darkzen.vim","src_id":"14075","5":"14075","creation_date":"1287452861","6":"1287452861"},{"0":"1402","vim_version":"6.0","1":"6.0","script_version":"2005rev1","2":"2005rev1","version_comment":"Fixed bug \"color scheme name seems to be reset while loading it\" reported by Hosup Chung.","3":"Fixed bug \"color scheme name seems to be reset while loading it\" reported by Hosup Chung.","package":"darkzen.vim","4":"darkzen.vim","src_id":"4745","5":"4745","creation_date":"1131781371","6":"1131781371"},{"0":"1402","vim_version":"6.0","1":"6.0","script_version":"2005","2":"2005","version_comment":"Initial upload","3":"Initial upload","package":"darkzen.vim","4":"darkzen.vim","src_id":"4739","5":"4739","creation_date":"1131722733","6":"1131722733"}]},"1401":{"script_id":"1401","0":"1401","script_name":"Zen Color Scheme","1":"Zen Color Scheme","script_type":"color scheme","2":"color scheme","summary":"Zen color scheme for Vim","3":"Zen color scheme for Vim","description":"Zen is a color scheme for white background terminals with elegant and clean look and feel. This color scheme was developed on Mac OS X but it also looks great on Ubuntu Linux.\r\n\r\nNOTE: this color scheme is deprecated, I recommend to install Satori color scheme http:\/\/www.vim.org\/scripts\/script.php?script_id=1614\r\n","4":"Zen is a color scheme for white background terminals with elegant and clean look and feel. This color scheme was developed on Mac OS X but it also looks great on Ubuntu Linux.\r\n\r\nNOTE: this color scheme is deprecated, I recommend to install Satori color scheme http:\/\/www.vim.org\/scripts\/script.php?script_id=1614\r\n","install_details":"Download zen.vim \r\nmkdir -p .vim\/colors\/ \r\nmv zen.vim .vim\/colors\/ \r\nEdit your .vimrc and insert \"colorscheme zen\"","5":"Download zen.vim \r\nmkdir -p .vim\/colors\/ \r\nmv zen.vim .vim\/colors\/ \r\nEdit your .vimrc and insert \"colorscheme zen\"","first_name":"Rud\u00c3\u00a1","6":"Rud\u00c3\u00a1","last_name":"Moura","7":"Moura","releases":[{"0":"1401","vim_version":"7.2","1":"7.2","script_version":"2010","2":"2010","version_comment":"Updated my email","3":"Updated my email","package":"zen.vim","4":"zen.vim","src_id":"14074","5":"14074","creation_date":"1287452822","6":"1287452822"},{"0":"1401","vim_version":"6.0","1":"6.0","script_version":"2005rev1","2":"2005rev1","version_comment":"Fixed bug \"color scheme name seems to be reset while loading it\" reported by Hosup Chung.","3":"Fixed bug \"color scheme name seems to be reset while loading it\" reported by Hosup Chung.","package":"zen.vim","4":"zen.vim","src_id":"4744","5":"4744","creation_date":"1131781291","6":"1131781291"},{"0":"1401","vim_version":"6.0","1":"6.0","script_version":"2005","2":"2005","version_comment":"Initial upload","3":"Initial upload","package":"zen.vim","4":"zen.vim","src_id":"4738","5":"4738","creation_date":"1131722519","6":"1131722519"}]},"1400":{"script_id":"1400","0":"1400","script_name":"desertedocean.vim","1":"desertedocean.vim","script_type":"color scheme","2":"color scheme","summary":"Tan\/blue GUI color scheme modified from Desert, akin to OceanDeep, & Zenburn","3":"Tan\/blue GUI color scheme modified from Desert, akin to OceanDeep, & Zenburn","description":"I changed my username, and uploaded to a new location for this color scheme.\r\n\r\nNEW SCRIPT LOCATION:\r\nhttp:\/\/www.vim.org\/scripts\/script.php?script_id=1404\r\n\r\nTry out the new versions there, these are OUTDATED.","4":"I changed my username, and uploaded to a new location for this color scheme.\r\n\r\nNEW SCRIPT LOCATION:\r\nhttp:\/\/www.vim.org\/scripts\/script.php?script_id=1404\r\n\r\nTry out the new versions there, these are OUTDATED.","install_details":"","5":"","first_name":"Shawn","6":"Shawn","last_name":"Axsom","7":"Axsom","releases":[{"0":"1400","vim_version":"6.0","1":"6.0","script_version":"0.3","2":"0.3","version_comment":"Increased the background contrast, added colors to the file status bar.\r\n\r\nSee the link above for newer versions.","3":"Increased the background contrast, added colors to the file status bar.\r\n\r\nSee the link above for newer versions.","package":"desertedocean.vim","4":"desertedocean.vim","src_id":"4753","5":"4753","creation_date":"1131821679","6":"1131821679"},{"0":"1400","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"desertedocean.vim","4":"desertedocean.vim","src_id":"4731","5":"4731","creation_date":"1131643911","6":"1131643911"}]},"1399":{"script_id":"1399","0":"1399","script_name":"javap.vim","1":"javap.vim","script_type":"utility","2":"utility","summary":"Runs the javap command and displays results in a new buffer","3":"Runs the javap command and displays results in a new buffer","description":"This command allows you to run the JDK utility javap to show the methods in a class found in your classpath.  This function assumes that you have your classpath set up and that you have javap in your path.\r\n\r\nIt's useful when I want to know a method or constructor signature and don't want to look up the javadocs for it.\r\n\r\nTo use it just go to the ex prompt and ...\r\n\r\n:Javap fully_qualified_classname\r\n\r\nFor example,\r\n\r\n:Javap java.lang.String;","4":"This command allows you to run the JDK utility javap to show the methods in a class found in your classpath.  This function assumes that you have your classpath set up and that you have javap in your path.\r\n\r\nIt's useful when I want to know a method or constructor signature and don't want to look up the javadocs for it.\r\n\r\nTo use it just go to the ex prompt and ...\r\n\r\n:Javap fully_qualified_classname\r\n\r\nFor example,\r\n\r\n:Javap java.lang.String;","install_details":"Either source this file or put it in your vimfiles\/plugins directory.  To test it out, run\r\n\r\n:source javap.vim","5":"Either source this file or put it in your vimfiles\/plugins directory.  To test it out, run\r\n\r\n:source javap.vim","first_name":"Don","6":"Don","last_name":"Mitchell","7":"Mitchell","releases":[{"0":"1399","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"javap.vim","4":"javap.vim","src_id":"4730","5":"4730","creation_date":"1131632394","6":"1131632394"}]},"1398":{"script_id":"1398","0":"1398","script_name":"tagSetting.vim","1":"tagSetting.vim","script_type":"utility","2":"utility","summary":"Dynamically set tags option by scanning directory structure","3":"Dynamically set tags option by scanning directory structure","description":"There's two functions provided here.  The first is SetTags() which will scan all of the directories from your current working directory to the root directory for a file called \"jtags\" (who can rename it to just tags if you want).  If it finds a jtags file, it adds it to the tags option. \r\n\r\nI use SetTags() when switching back and forth between different projects that have different tags files at their root level.  \r\n\r\nThe second function is GenerateTags() which works similar to the above script.  It starts at your current working directory and scans all of the directories above it looking for a file called \"build.xml\" (you can use any file you want).  When it finds this file, it assumes that it is at the top of your directory structure and will run the ctags command to generate a new tags file.  By default it creates a tags file called \"jtags\" at that top level.  I use build.xml to indicate the top level because I generally use Ant and the ant build file is a good way to recognize the top of the project in the directory structure.\r\n\r\nThe two functions have been mapped to commands to save typing.  Those commands are:\r\n\r\nmap <unique> <Leader>tj <ESC>:call SetTags()<CR>\r\nmap <unique> <Leader>tg <ESC>:call GenerateTags()<CR>","4":"There's two functions provided here.  The first is SetTags() which will scan all of the directories from your current working directory to the root directory for a file called \"jtags\" (who can rename it to just tags if you want).  If it finds a jtags file, it adds it to the tags option. \r\n\r\nI use SetTags() when switching back and forth between different projects that have different tags files at their root level.  \r\n\r\nThe second function is GenerateTags() which works similar to the above script.  It starts at your current working directory and scans all of the directories above it looking for a file called \"build.xml\" (you can use any file you want).  When it finds this file, it assumes that it is at the top of your directory structure and will run the ctags command to generate a new tags file.  By default it creates a tags file called \"jtags\" at that top level.  I use build.xml to indicate the top level because I generally use Ant and the ant build file is a good way to recognize the top of the project in the directory structure.\r\n\r\nThe two functions have been mapped to commands to save typing.  Those commands are:\r\n\r\nmap <unique> <Leader>tj <ESC>:call SetTags()<CR>\r\nmap <unique> <Leader>tg <ESC>:call GenerateTags()<CR>","install_details":"Either source this script or put it into your vimfiles\/plugins directory.  To try it out just run\r\n\r\n:source tagSetting.vim","5":"Either source this script or put it into your vimfiles\/plugins directory.  To try it out just run\r\n\r\n:source tagSetting.vim","first_name":"Don","6":"Don","last_name":"Mitchell","7":"Mitchell","releases":[{"0":"1398","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"tagSetting.vim","4":"tagSetting.vim","src_id":"4729","5":"4729","creation_date":"1131632102","6":"1131632102"}]},"1397":{"script_id":"1397","0":"1397","script_name":"xml.vim","1":"xml.vim","script_type":"ftplugin","2":"ftplugin","summary":"helps editing xml (and [x]html, sgml, xslt) files","3":"helps editing xml (and [x]html, sgml, xslt) files","description":"A plugin for editing xml. I used xml.vim (http:\/\/www.vim.org\/scripts\/script.php?script_id=301)\r\nThe script does retain most of the functionality of the original xml.vim \r\n - closing tags while you type\r\n - optional adding attributes\r\n - and more\r\n - % matches end or begin tag\r\nit adds:\r\n - fold tags, comments and Cdata \r\n - add start tag\r\n - add end tags\r\n - add  tag around a visual blok or a tag,\r\n - join 2 adjacent same tags\r\n - delete tag\r\n - delete tag section\r\n - change a tag \r\n - visual mode  (blocks, listitems\r\nThe documentation will be created once the script is loaded e.g edit a xml file.\r\nRead the help documentation by typing from within vim  :help xml-plugin\r\n\r\nThe latest version is now available from https:\/\/github.com\/othree\/xml.vim.","4":"A plugin for editing xml. I used xml.vim (http:\/\/www.vim.org\/scripts\/script.php?script_id=301)\r\nThe script does retain most of the functionality of the original xml.vim \r\n - closing tags while you type\r\n - optional adding attributes\r\n - and more\r\n - % matches end or begin tag\r\nit adds:\r\n - fold tags, comments and Cdata \r\n - add start tag\r\n - add end tags\r\n - add  tag around a visual blok or a tag,\r\n - join 2 adjacent same tags\r\n - delete tag\r\n - delete tag section\r\n - change a tag \r\n - visual mode  (blocks, listitems\r\nThe documentation will be created once the script is loaded e.g edit a xml file.\r\nRead the help documentation by typing from within vim  :help xml-plugin\r\n\r\nThe latest version is now available from https:\/\/github.com\/othree\/xml.vim.","install_details":"copy xml.vim to  ~\/.vim\/ftplugin\/xml.vim)\r\noptionally link (or copy on windows) xml.vim in ~\/.vim\/ftplugin directory to docbk.vim, xsl.vim, html.vim, xhtml.vim\r\nwhen you have filetype indent on. Then create a ~\/.vim\/indent directory and for every link (copy) you made do\r\n      echo \"let b:did_indent = 1\" > ~\/.vim\/indent\/xml.vim\r\nBecause standard vimXX\/indent\/xml.vim interferes with xml.vim","5":"copy xml.vim to  ~\/.vim\/ftplugin\/xml.vim)\r\noptionally link (or copy on windows) xml.vim in ~\/.vim\/ftplugin directory to docbk.vim, xsl.vim, html.vim, xhtml.vim\r\nwhen you have filetype indent on. Then create a ~\/.vim\/indent directory and for every link (copy) you made do\r\n      echo \"let b:did_indent = 1\" > ~\/.vim\/indent\/xml.vim\r\nBecause standard vimXX\/indent\/xml.vim interferes with xml.vim","first_name":"Rene","6":"Rene","last_name":"de Zwart","7":"de Zwart","releases":[{"0":"1397","vim_version":"6.0","1":"6.0","script_version":"1.40","2":"1.40","version_comment":"Same version but this patch is from bootleg. Thanks","3":"Same version but this patch is from bootleg. Thanks","package":"xml.vim","4":"xml.vim","src_id":"16076","5":"16076","creation_date":"1310629040","6":"1310629040"},{"0":"1397","vim_version":"7.0","1":"7.0","script_version":"1.40","2":"1.40","version_comment":"O3 supplied this patch (again) thanks","3":"O3 supplied this patch (again) thanks","package":"xml.vim","4":"xml.vim","src_id":"16073","5":"16073","creation_date":"1310585049","6":"1310585049"},{"0":"1397","vim_version":"6.0","1":"6.0","script_version":"1.39","2":"1.39","version_comment":"An other patch from O3. Make sure that buffer variable did_indent exists","3":"An other patch from O3. Make sure that buffer variable did_indent exists","package":"xml.vim","4":"xml.vim","src_id":"14039","5":"14039","creation_date":"1286826200","6":"1286826200"},{"0":"1397","vim_version":"6.0","1":"6.0","script_version":"1.38","2":"1.38","version_comment":"Othree send me the patch for:\r\nupdate the empty tag list and fix a bug\r\nwhile using other indent plugin will make double indent.","3":"Othree send me the patch for:\r\nupdate the empty tag list and fix a bug\r\nwhile using other indent plugin will make double indent.","package":"xml.vim","4":"xml.vim","src_id":"14029","5":"14029","creation_date":"1286569588","6":"1286569588"},{"0":"1397","vim_version":"7.0","1":"7.0","script_version":"1.37","2":"1.37","version_comment":"1) document directory create a wrong directory under windows when the path contained a space. thanks to Guande Wang.\r\n2) filetype indent interferes with xml.vim thanks to Brandon Waskiewicz\r\n3) exe normal changed to exe normal! to avoid key remappings thanks to Roald de Vries ","3":"1) document directory create a wrong directory under windows when the path contained a space. thanks to Guande Wang.\r\n2) filetype indent interferes with xml.vim thanks to Brandon Waskiewicz\r\n3) exe normal changed to exe normal! to avoid key remappings thanks to Roald de Vries ","package":"xml.vim","4":"xml.vim","src_id":"11713","5":"11713","creation_date":"1258038207","6":"1258038207"},{"0":"1397","vim_version":"6.0","1":"6.0","script_version":"1.36","2":"1.36","version_comment":"xml-plugin-callbacks is defined twice by \"Samuel Ferencik\"\r\nCloseTag definiton had optional attribute","3":"xml-plugin-callbacks is defined twice by \"Samuel Ferencik\"\r\nCloseTag definiton had optional attribute","package":"xml.vim","4":"xml.vim","src_id":"11416","5":"11416","creation_date":"1253555872","6":"1253555872"},{"0":"1397","vim_version":"6.0","1":"6.0","script_version":"1.35","2":"1.35","version_comment":"1.35 Neil walker send a patch to change to cursor positioning to use (suprise) cursor function\r\n        Thanks Neil\r\n1.34 Had a variable CloseTag and a function CloseTag","3":"1.35 Neil walker send a patch to change to cursor positioning to use (suprise) cursor function\r\n        Thanks Neil\r\n1.34 Had a variable CloseTag and a function CloseTag","package":"xml.vim","4":"xml.vim","src_id":"6887","5":"6887","creation_date":"1174110483","6":"1174110483"},{"0":"1397","vim_version":"6.0","1":"6.0","script_version":"1.33","2":"1.33","version_comment":"Ian A. Tegebo noticed that match and fold didn't when a tag has an attribute like \r\n<tag att=\"dc=rescomp,dc=berkeley,dc=edu\">. The regular expresssion s:Attrib\r\ndidn't work in that situation","3":"Ian A. Tegebo noticed that match and fold didn't when a tag has an attribute like \r\n<tag att=\"dc=rescomp,dc=berkeley,dc=edu\">. The regular expresssion s:Attrib\r\ndidn't work in that situation","package":"xml.vim","4":"xml.vim","src_id":"5909","5":"5909","creation_date":"1151845650","6":"1151845650"},{"0":"1397","vim_version":"6.0","1":"6.0","script_version":"1.32","2":"1.32","version_comment":"improvements from Guangde Wang (g2wang at yahoo com)\r\ncheck for jsp tags, php tags and 0 length tagnames\r\nThanks Guangde\r\n(and please do send  improvements if anyone stumbles over them)\r\n","3":"improvements from Guangde Wang (g2wang at yahoo com)\r\ncheck for jsp tags, php tags and 0 length tagnames\r\nThanks Guangde\r\n(and please do send  improvements if anyone stumbles over them)\r\n","package":"xml.vim","4":"xml.vim","src_id":"5683","5":"5683","creation_date":"1147446147","6":"1147446147"},{"0":"1397","vim_version":"6.0","1":"6.0","script_version":"1.30","2":"1.30","version_comment":"added function\r\n    DelCData ( \\[ )     deletes Cdata tag\r\n    DelCDataSection (\\{) deletes cdata section\r\n    DelComment (\\])    deletes comment tag\r\n    DelCommentSection (\\})  delete comment section\r\n    commenttag (\\=)       puts a comment around the tag\r\nchanged All suffix to Section as a better understaning\r\nupdated the documentation (volunteers for a better effort are welcome ;-)\r\nadded menu entries\r\nCorrect  typo in menu (Your welcome to point out more)\r\nCheck  more strict to not match comments as closing tag","3":"added function\r\n    DelCData ( \\[ )     deletes Cdata tag\r\n    DelCDataSection (\\{) deletes cdata section\r\n    DelComment (\\])    deletes comment tag\r\n    DelCommentSection (\\})  delete comment section\r\n    commenttag (\\=)       puts a comment around the tag\r\nchanged All suffix to Section as a better understaning\r\nupdated the documentation (volunteers for a better effort are welcome ;-)\r\nadded menu entries\r\nCorrect  typo in menu (Your welcome to point out more)\r\nCheck  more strict to not match comments as closing tag","package":"xml.vim","4":"xml.vim","src_id":"5544","5":"5544","creation_date":"1144819587","6":"1144819587"},{"0":"1397","vim_version":"6.0","1":"6.0","script_version":"1.28","2":"1.28","version_comment":"- Code Changes\r\n    - regular expressions moved to script variables which document them a bit\r\n    - rename b:endtag to b:firstWasEndTag as a better description.\r\n    -while loops level check into while\r\n    - level in\/de-crease using ? operator\r\n- Moved a bit of the global xml script into xml\r\n- added [ and ] mappings for next\/previous open\/close tag\/comment\r\n- distribute dtdmenu seperatly since it is only a bit related to xml.vim\r\n- add \\5 \\% visual mode which extends the visual selection to the matching tag\r\n- made \\l cursor position end up after the closing <\/listitem> easier marking up by hand\r\n-updated the documentation","3":"- Code Changes\r\n    - regular expressions moved to script variables which document them a bit\r\n    - rename b:endtag to b:firstWasEndTag as a better description.\r\n    -while loops level check into while\r\n    - level in\/de-crease using ? operator\r\n- Moved a bit of the global xml script into xml\r\n- added [ and ] mappings for next\/previous open\/close tag\/comment\r\n- distribute dtdmenu seperatly since it is only a bit related to xml.vim\r\n- add \\5 \\% visual mode which extends the visual selection to the matching tag\r\n- made \\l cursor position end up after the closing <\/listitem> easier marking up by hand\r\n-updated the documentation","package":"xml.vim","4":"xml.vim","src_id":"4872","5":"4872","creation_date":"1134049528","6":"1134049528"},{"0":"1397","vim_version":"6.0","1":"6.0","script_version":"1.27","2":"1.27","version_comment":"- Added listitem \\l for marking up (itemized|ordered)list in docbook\r\n- added \\I (capital i) indent all function  (does maybe more then one expect)\r\n- added \\<  to comment out a block  \r\n- added \\c to comment out a block with CDATA Section\r\n- convinience menu entry gvim fold cdata section  (just a simple :?<![CDATA[,\/]]>\/fold)\r\n- convinience menu entry gvim fold comment section (just a simple :?<!--?,\/-->\/fold)\r\n- documentation updated ","3":"- Added listitem \\l for marking up (itemized|ordered)list in docbook\r\n- added \\I (capital i) indent all function  (does maybe more then one expect)\r\n- added \\<  to comment out a block  \r\n- added \\c to comment out a block with CDATA Section\r\n- convinience menu entry gvim fold cdata section  (just a simple :?<![CDATA[,\/]]>\/fold)\r\n- convinience menu entry gvim fold comment section (just a simple :?<!--?,\/-->\/fold)\r\n- documentation updated ","package":"xml-dtd.zip","4":"xml-dtd.zip","src_id":"4835","5":"4835","creation_date":"1133328879","6":"1133328879"},{"0":"1397","vim_version":"6.0","1":"6.0","script_version":"1.16","2":"1.16","version_comment":"- Error in MakeElement in (x)html mode the cursor postion after emptytags was wrong\r\n- foldTag added the case when started from closetag (backward range)\r\n- foldTagAll do everything in the function not calling FoldTag.\r\n- Added the <silent> option to the remaps\r\n- FormatTagAll  do everything in the function not call FormatTag\r\n- Function ShiftRight and ShiftLeft\r\n- Updated the docs","3":"- Error in MakeElement in (x)html mode the cursor postion after emptytags was wrong\r\n- foldTag added the case when started from closetag (backward range)\r\n- foldTagAll do everything in the function not calling FoldTag.\r\n- Added the <silent> option to the remaps\r\n- FormatTagAll  do everything in the function not call FormatTag\r\n- Function ShiftRight and ShiftLeft\r\n- Updated the docs","package":"xml.vim","4":"xml.vim","src_id":"4767","5":"4767","creation_date":"1132103568","6":"1132103568"},{"0":"1397","vim_version":"6.0","1":"6.0","script_version":"1.11","2":"1.11","version_comment":"added function makeElement thanks to Bart van Deenen script make-element.vim (632)\r\ntyping word;; expands into <word><\/word>. ;; is customisable see doc\r\ndocumentation update\r\nhtml_mode mode detection error\r\nmade xml_use_xhtml a buffer variable set by g:xml_use_xhtml\r\nin it's absence by the fact that we are editing a xhtml filetype","3":"added function makeElement thanks to Bart van Deenen script make-element.vim (632)\r\ntyping word;; expands into <word><\/word>. ;; is customisable see doc\r\ndocumentation update\r\nhtml_mode mode detection error\r\nmade xml_use_xhtml a buffer variable set by g:xml_use_xhtml\r\nin it's absence by the fact that we are editing a xhtml filetype","package":"xml.vim","4":"xml.vim","src_id":"4759","5":"4759","creation_date":"1131987308","6":"1131987308"},{"0":"1397","vim_version":"6.0","1":"6.0","script_version":"1.9","2":"1.9","version_comment":"documentation update\r\nnew function FormatTagAll will format all tagnames like the one the cursor is on\r\nerror in BlockTag when visual selection is one line only\r\nafter FoldTagAll, AfterTag, BeforeTag,FormatTagAll return to where the command was given from","3":"documentation update\r\nnew function FormatTagAll will format all tagnames like the one the cursor is on\r\nerror in BlockTag when visual selection is one line only\r\nafter FoldTagAll, AfterTag, BeforeTag,FormatTagAll return to where the command was given from","package":"xml.vim","4":"xml.vim","src_id":"4757","5":"4757","creation_date":"1131963764","6":"1131963764"},{"0":"1397","vim_version":"6.0","1":"6.0","script_version":"1.6","2":"1.6","version_comment":"More compatability with devins xml.  (HtmlAttribCallback && XmlAttribCallback. xml_use_xhtml\r\nsupport for open html tags in html mode and xml mode makes them empty tags)\r\nDocumentation updated\r\nask for attributes\r\nreuse the last given tag and attributes when prompting\r\nvisual block now uses append for top and bottom\r\nremoved the use unmapgt & mapgt in favor of normal!","3":"More compatability with devins xml.  (HtmlAttribCallback && XmlAttribCallback. xml_use_xhtml\r\nsupport for open html tags in html mode and xml mode makes them empty tags)\r\nDocumentation updated\r\nask for attributes\r\nreuse the last given tag and attributes when prompting\r\nvisual block now uses append for top and bottom\r\nremoved the use unmapgt & mapgt in favor of normal!","package":"xml.vim","4":"xml.vim","src_id":"4754","5":"4754","creation_date":"1131929344","6":"1131929344"},{"0":"1397","vim_version":"6.0","1":"6.0","script_version":"1.2","2":"1.2","version_comment":"Initial upload","3":"Initial upload","package":"xml.vim","4":"xml.vim","src_id":"4727","5":"4727","creation_date":"1131621455","6":"1131621455"}]},"1396":{"script_id":"1396","0":"1396","script_name":"range-search.vim","1":"range-search.vim","script_type":"utility","2":"utility","summary":"Allows one to perform a search only inside a range","3":"Allows one to perform a search only inside a range","description":"The default vim search searches the entire file. This script allows a command called :'a,'eRs mypat (where 'a,'e is any range), that searches in only a specified range of lines within a file.","4":"The default vim search searches the entire file. This script allows a command called :'a,'eRs mypat (where 'a,'e is any range), that searches in only a specified range of lines within a file.","install_details":"To use: unzip the package inside ~\/.vim (or equivalent). Afterwards do from within vim:\r\n\r\n:helptags ~\/.vim\/doc\/\r\n\r\nAnd then read the help.","5":"To use: unzip the package inside ~\/.vim (or equivalent). Afterwards do from within vim:\r\n\r\n:helptags ~\/.vim\/doc\/\r\n\r\nAnd then read the help.","first_name":"Shlomi","6":"Shlomi","last_name":"Fish","7":"Fish","releases":[{"0":"1396","vim_version":"6.0","1":"6.0","script_version":"0.4.0","2":"0.4.0","version_comment":"Added documentation, a more informative comment and converted into a .zip file.","3":"Added documentation, a more informative comment and converted into a .zip file.","package":"range-search.zip","4":"range-search.zip","src_id":"10927","5":"10927","creation_date":"1246528800","6":"1246528800"},{"0":"1396","vim_version":"6.0","1":"6.0","script_version":"0.2.0","2":"0.2.0","version_comment":"Initial upload","3":"Initial upload","package":"range-search.vim","4":"range-search.vim","src_id":"4726","5":"4726","creation_date":"1131592162","6":"1131592162"}]},"1395":{"script_id":"1395","0":"1395","script_name":"Processing Syntax","1":"Processing Syntax","script_type":"syntax","2":"syntax","summary":"Syntax description for Processing .pde files","3":"Syntax description for Processing .pde files","description":"This is a simple syntax description for Processing .pde files. You can find more information about Processing at http:\/\/processing.org.","4":"This is a simple syntax description for Processing .pde files. You can find more information about Processing at http:\/\/processing.org.","install_details":"","5":"","first_name":"Chris","6":"Chris","last_name":"Hoge","7":"Hoge","releases":[{"0":"1395","vim_version":"6.0","1":"6.0","script_version":"0.8","2":"0.8","version_comment":"Initial upload","3":"Initial upload","package":"pde.vim","4":"pde.vim","src_id":"4724","5":"4724","creation_date":"1131449075","6":"1131449075"}]},"1394":{"script_id":"1394","0":"1394","script_name":"fish.vim","1":"fish.vim","script_type":"syntax","2":"syntax","summary":"color syntax for fish","3":"color syntax for fish","description":"This is a first attempt to offer a color syntax for fish. It is heavily based on the zsh.vim file. I hope it will become as good :)\r\n\r\nplease feel free to report any problems at the email indicated inside the file.","4":"This is a first attempt to offer a color syntax for fish. It is heavily based on the zsh.vim file. I hope it will become as good :)\r\n\r\nplease feel free to report any problems at the email indicated inside the file.","install_details":"like any syntax file","5":"like any syntax file","first_name":"Yann","6":"Yann","last_name":"Monclair","7":"Monclair","releases":[{"0":"1394","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"fish.vim","4":"fish.vim","src_id":"4723","5":"4723","creation_date":"1131442462","6":"1131442462"}]},"1393":{"script_id":"1393","0":"1393","script_name":"motus.vim","1":"motus.vim","script_type":"color scheme","2":"color scheme","summary":"Dark color scheme based on the popular torte setup. Good for LCD and consoles","3":"Dark color scheme based on the popular torte setup. Good for LCD and consoles","description":"This is a modification of the popular grey-on-black color scheme vimscript #111 (torte).\r\nIt looks great on LCDs and full-screen consoles; I also like it in grey-on-black xterm and KDE Konsole with Linux Colors scheme.\r\nScreenshot is here:\r\nhttp:\/\/motus.kiev.ua\/motus2\/Files\/motus_vim.png\r\nEnjoy!","4":"This is a modification of the popular grey-on-black color scheme vimscript #111 (torte).\r\nIt looks great on LCDs and full-screen consoles; I also like it in grey-on-black xterm and KDE Konsole with Linux Colors scheme.\r\nScreenshot is here:\r\nhttp:\/\/motus.kiev.ua\/motus2\/Files\/motus_vim.png\r\nEnjoy!","install_details":"Copy this file into your ~\/.vim\/colors\/ directory and run\r\n    colorscheme motus\r\nin the vim command line. If you like the scheme, add 'colorscheme motus' line to your ~\/.vimrc","5":"Copy this file into your ~\/.vim\/colors\/ directory and run\r\n    colorscheme motus\r\nin the vim command line. If you like the scheme, add 'colorscheme motus' line to your ~\/.vimrc","first_name":"Sergiy","6":"Sergiy","last_name":"Matusevych","7":"Matusevych","releases":[{"0":"1393","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"motus.vim","4":"motus.vim","src_id":"4717","5":"4717","creation_date":"1131008563","6":"1131008563"}]},"1392":{"script_id":"1392","0":"1392","script_name":"py_jump.vim","1":"py_jump.vim","script_type":"ftplugin","2":"ftplugin","summary":"Ultimate % command for python!","3":"Ultimate % command for python!","description":"The title says it all - this script enhances a % command in python to make it jump not only between ([{}]) brackets, but also between start and end of the indented block - just like it does for {} in C++ and perl.\r\n\r\nThe script also uses some tricks to guess the _beginning_ of the indented block when jumping backwards. Try to use % several times for a deeply nested block to check it out.\r\n\r\nEnjoy!","4":"The title says it all - this script enhances a % command in python to make it jump not only between ([{}]) brackets, but also between start and end of the indented block - just like it does for {} in C++ and perl.\r\n\r\nThe script also uses some tricks to guess the _beginning_ of the indented block when jumping backwards. Try to use % several times for a deeply nested block to check it out.\r\n\r\nEnjoy!","install_details":"Simply rename the file to python.vim and put it into your local ~\/.vim\/ftplugin\/ directory.","5":"Simply rename the file to python.vim and put it into your local ~\/.vim\/ftplugin\/ directory.","first_name":"Sergiy","6":"Sergiy","last_name":"Matusevych","7":"Matusevych","releases":[{"0":"1392","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"py_jump.vim","4":"py_jump.vim","src_id":"4716","5":"4716","creation_date":"1130963755","6":"1130963755"}]},"1391":{"script_id":"1391","0":"1391","script_name":"BuildWin","1":"BuildWin","script_type":"utility","2":"utility","summary":"View the output of a build in progress.","3":"View the output of a build in progress.","description":"BuildWin allows you to view the progress of a build within the Vim instance.  When a build is finished, it will automatically load the results into the error list.\r\n\r\nsee ':help buildwin'","4":"BuildWin allows you to view the progress of a build within the Vim instance.  When a build is finished, it will automatically load the results into the error list.\r\n\r\nsee ':help buildwin'","install_details":"- Unzip the files into your Vim runtime path (vimfiles on Windows, .vim on Unix)\r\n- In Vim, run ':helptags' to rebuild your help file\r\n- Restart Vim","5":"- Unzip the files into your Vim runtime path (vimfiles on Windows, .vim on Unix)\r\n- In Vim, run ':helptags' to rebuild your help file\r\n- Restart Vim","first_name":"Jason","6":"Jason","last_name":"Heddings","7":"Heddings","releases":[{"0":"1391","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"buildwin.zip","4":"buildwin.zip","src_id":"4715","5":"4715","creation_date":"1130947839","6":"1130947839"}]},"1390":{"script_id":"1390","0":"1390","script_name":"GreedyBackspace.vim","1":"GreedyBackspace.vim","script_type":"utility","2":"utility","summary":"Make backspace eat multiple whitespace characters","3":"Make backspace eat multiple whitespace characters","description":"This script will cause your backspace key to delete all the whitespace characters before the cursor when the cursor is on a whitespace character.\r\n\r\nFor example, if you typed \"x       x\" and then hit backspace twice, you'd only have \"x\".  This can be especially useful when auto\/smart\/c\/expression indenting is on.\r\n\r\nThis script isn't very useful if you don't put \"set backspace=indent,eol,start\" or at least \"set backsapce=indent,start\" in your vimrc.\r\n\r\n\r\n(Thanks to Tomi Mickelsson for testing and bug reports.)","4":"This script will cause your backspace key to delete all the whitespace characters before the cursor when the cursor is on a whitespace character.\r\n\r\nFor example, if you typed \"x       x\" and then hit backspace twice, you'd only have \"x\".  This can be especially useful when auto\/smart\/c\/expression indenting is on.\r\n\r\nThis script isn't very useful if you don't put \"set backspace=indent,eol,start\" or at least \"set backsapce=indent,start\" in your vimrc.\r\n\r\n\r\n(Thanks to Tomi Mickelsson for testing and bug reports.)","install_details":"Source the script from your vimrc or just place it in your plugin directory.","5":"Source the script from your vimrc or just place it in your plugin directory.","first_name":"Christian J.","6":"Christian J.","last_name":"Robinson","7":"Robinson","releases":[{"0":"1390","vim_version":"9.0","1":"9.0","script_version":"0.6","2":"0.6","version_comment":"- Update to Vim 9 (no functionality added)","3":"- Update to Vim 9 (no functionality added)","package":"GreedyBackspace.vim","4":"GreedyBackspace.vim","src_id":"28136","5":"28136","creation_date":"1661149127","6":"1661149127"},{"0":"1390","vim_version":"6.0","1":"6.0","script_version":"0.5","2":"0.5","version_comment":"- When 'fileformat' was \"dos\" and g:greedybackspacenl was set too many characters could be deleted.","3":"- When 'fileformat' was \"dos\" and g:greedybackspacenl was set too many characters could be deleted.","package":"GreedyBackspace.vim","4":"GreedyBackspace.vim","src_id":"4802","5":"4802","creation_date":"1132726775","6":"1132726775"},{"0":"1390","vim_version":"6.0","1":"6.0","script_version":"0.4","2":"0.4","version_comment":"- g:greedybackspacenl = 1 wasn't working properly when the cursor was on the first character of a line.","3":"- g:greedybackspacenl = 1 wasn't working properly when the cursor was on the first character of a line.","package":"GreedyBackspace.vim","4":"GreedyBackspace.vim","src_id":"4771","5":"4771","creation_date":"1132174748","6":"1132174748"},{"0":"1390","vim_version":"6.0","1":"6.0","script_version":"0.3","2":"0.3","version_comment":"- The 'smarttab' option was confusing the logic.\r\n- You can now do \":let g:greedybackspacenl = 1\" to cause the script to eat newlines as well.","3":"- The 'smarttab' option was confusing the logic.\r\n- You can now do \":let g:greedybackspacenl = 1\" to cause the script to eat newlines as well.","package":"GreedyBackspace.vim","4":"GreedyBackspace.vim","src_id":"4743","5":"4743","creation_date":"1131730133","6":"1131730133"},{"0":"1390","vim_version":"6.0","1":"6.0","script_version":"0.2","2":"0.2","version_comment":"- Commentary added.\r\n- Syntax tweaks, no functional changes.","3":"- Commentary added.\r\n- Syntax tweaks, no functional changes.","package":"GreedyBackspace.vim","4":"GreedyBackspace.vim","src_id":"4719","5":"4719","creation_date":"1131026798","6":"1131026798"},{"0":"1390","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"GreedyBackspace.vim","4":"GreedyBackspace.vim","src_id":"4711","5":"4711","creation_date":"1130738393","6":"1130738393"}]},"1389":{"script_id":"1389","0":"1389","script_name":"d.vim","1":"d.vim","script_type":"indent","2":"indent","summary":"Indent script for the D programming language.","3":"Indent script for the D programming language.","description":"Indent script for the D programming language.","4":"Indent script for the D programming language.","install_details":"Place the downloaded d.vim in your indent directory. On windows, copy to $VIM\/vimfiles\/indent or $HOME\/vimfiles\/indent . On Linux copy to $HOME\/.vim\/indent or $VIM\/vimfiles\/indent.","5":"Place the downloaded d.vim in your indent directory. On windows, copy to $VIM\/vimfiles\/indent or $HOME\/vimfiles\/indent . On Linux copy to $HOME\/.vim\/indent or $VIM\/vimfiles\/indent.","first_name":"Jason","6":"Jason","last_name":"Mills","7":"Mills","releases":[{"0":"1389","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"d.vim","4":"d.vim","src_id":"4708","5":"4708","creation_date":"1130607215","6":"1130607215"}]},"1388":{"script_id":"1388","0":"1388","script_name":"jay-syntax","1":"jay-syntax","script_type":"syntax","2":"syntax","summary":"Syntax highlighting for jay","3":"Syntax highlighting for jay","description":"Syntax highlighting for jay, a parser generator for C# (part of Mono)","4":"Syntax highlighting for jay, a parser generator for C# (part of Mono)","install_details":"Place the script in ~\/.vim\/syntax\/. Optionally add \r\n\r\nau BufNewFile,BufRead *.jay set ft=jay\r\n\r\nto ~\/.vim\/ftdetect\/jay.vim","5":"Place the script in ~\/.vim\/syntax\/. Optionally add \r\n\r\nau BufNewFile,BufRead *.jay set ft=jay\r\n\r\nto ~\/.vim\/ftdetect\/jay.vim","first_name":"Jelmer","6":"Jelmer","last_name":"Vernooij","7":"Vernooij","releases":[{"0":"1388","vim_version":"6.0","1":"6.0","script_version":"3","2":"3","version_comment":"Initial upload","3":"Initial upload","package":"jay.vim","4":"jay.vim","src_id":"4703","5":"4703","creation_date":"1130436357","6":"1130436357"}]},"1387":{"script_id":"1387","0":"1387","script_name":"build.vim","1":"build.vim","script_type":"utility","2":"utility","summary":"A compiler plugin for the Windows CE build command.","3":"A compiler plugin for the Windows CE build command.","description":"A compiler plugin for the Windows CE build command.","4":"A compiler plugin for the Windows CE build command.","install_details":"Add to your compiler directory.\r\n\r\n\r\n ","5":"Add to your compiler directory.\r\n\r\n\r\n ","first_name":"igor","6":"igor","last_name":"dvorkin","7":"dvorkin","releases":[{"0":"1387","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"build.vim","4":"build.vim","src_id":"4699","5":"4699","creation_date":"1130356053","6":"1130356053"}]},"1386":{"script_id":"1386","0":"1386","script_name":"gdbvim","1":"gdbvim","script_type":"utility","2":"utility","summary":"Watch in gvim what you debug in gdb. And more.","3":"Watch in gvim what you debug in gdb. And more.","description":"NOTICE: MICROSOFT WINDOWS IS NOT CURRENTLY SUPPORTED BY THIS SCRIPT YET!\r\n\r\nI found a very nice plugin called gdbvim. Now I can debug my C \/ C++ code in VIM with its help. The original copy of the plugin can be found at: vimscript #84. See this link for more information about this plugin.\r\n\r\nUnfortunately, I can only set breakpoints with this plugin, but I can't clear the breakpoints set before. So I modified the plugin and made \"toggle breakpoints\" feature possible. Here is my newly patched code. The new gdbvim.vim requires multvars.vim, which can be found at: vimscript #171.\r\n\r\nAny comments or suggestions are welcome.","4":"NOTICE: MICROSOFT WINDOWS IS NOT CURRENTLY SUPPORTED BY THIS SCRIPT YET!\r\n\r\nI found a very nice plugin called gdbvim. Now I can debug my C \/ C++ code in VIM with its help. The original copy of the plugin can be found at: vimscript #84. See this link for more information about this plugin.\r\n\r\nUnfortunately, I can only set breakpoints with this plugin, but I can't clear the breakpoints set before. So I modified the plugin and made \"toggle breakpoints\" feature possible. Here is my newly patched code. The new gdbvim.vim requires multvars.vim, which can be found at: vimscript #171.\r\n\r\nAny comments or suggestions are welcome.","install_details":"Extract files from archive and move the files into your runtime path, for example, \"~\/.vim\". Then run \":helptags ~\/.vim\/doc\". \"plugin\/gdbvim\" is an executable written in Perl. You can create a symbolic link to it in one of your $PATH directories.","5":"Extract files from archive and move the files into your runtime path, for example, \"~\/.vim\". Then run \":helptags ~\/.vim\/doc\". \"plugin\/gdbvim\" is an executable written in Perl. You can create a symbolic link to it in one of your $PATH directories.","first_name":"Edward","6":"Edward","last_name":"Fox","7":"Fox","releases":[{"0":"1386","vim_version":"6.0","1":"6.0","script_version":"0.3a","2":"0.3a","version_comment":"This is an Alpha (UNSTABLE) version with some new features added and a few bugs fixed.\r\n\r\n\r\nNew features:\r\n\r\n  * (Major) Dumps the breakpoints out to \".gdbvim_breakpoints\" when you quit gdbvim, and re-read all the breakpoints when you launch gdbvim the next time.\r\n\r\n  * Add \"Clear all breakpoints\" feature.\r\n\r\n  * (Minor) Changed the menu layout. Added \"Call stacks\" and some other useful menu items.\r\n\r\n\r\nBugs fixed:\r\n\r\n  * The previous version may fail to clear some breakpoints under some new version of gdb. Because  such gdb may breaks at two or more different addresses in the binary code when you set breakpoint at only one position of the source code.","3":"This is an Alpha (UNSTABLE) version with some new features added and a few bugs fixed.\r\n\r\n\r\nNew features:\r\n\r\n  * (Major) Dumps the breakpoints out to \".gdbvim_breakpoints\" when you quit gdbvim, and re-read all the breakpoints when you launch gdbvim the next time.\r\n\r\n  * Add \"Clear all breakpoints\" feature.\r\n\r\n  * (Minor) Changed the menu layout. Added \"Call stacks\" and some other useful menu items.\r\n\r\n\r\nBugs fixed:\r\n\r\n  * The previous version may fail to clear some breakpoints under some new version of gdb. Because  such gdb may breaks at two or more different addresses in the binary code when you set breakpoint at only one position of the source code.","package":"gdbvim.tar.bz2","4":"gdbvim.tar.bz2","src_id":"4701","5":"4701","creation_date":"1130391722","6":"1130391722"},{"0":"1386","vim_version":"6.0","1":"6.0","script_version":"0.2","2":"0.2","version_comment":"Initial upload","3":"Initial upload","package":"gdbvim.tar.bz2","4":"gdbvim.tar.bz2","src_id":"4698","5":"4698","creation_date":"1130289309","6":"1130289309"}]},"1385":{"script_id":"1385","0":"1385","script_name":"interfaces","1":"interfaces","script_type":"syntax","2":"syntax","summary":"A syntax file for \/etc\/network\/interfaces","3":"A syntax file for \/etc\/network\/interfaces","description":"This syntax file adds syntax hilighting for your \/etc\/network\/interfaces.","4":"This syntax file adds syntax hilighting for your \/etc\/network\/interfaces.","install_details":"- Copy the script in ~\/.vim\/syntax\/\r\n- Add to your ~\/.vimrc :\r\n  au BufRead \/etc\/network\/interfaces :set syntax=interfaces\r\n\r\n\r\n","5":"- Copy the script in ~\/.vim\/syntax\/\r\n- Add to your ~\/.vimrc :\r\n  au BufRead \/etc\/network\/interfaces :set syntax=interfaces\r\n\r\n\r\n","first_name":"Fran\u00c3\u00a7ois","6":"Fran\u00c3\u00a7ois","last_name":"Wendling","7":"Wendling","releases":[{"0":"1385","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"interfaces.vim","4":"interfaces.vim","src_id":"4693","5":"4693","creation_date":"1129900630","6":"1129900630"}]},"1384":{"script_id":"1384","0":"1384","script_name":"UniCycle","1":"UniCycle","script_type":"utility","2":"utility","summary":"Unicode character cycler","3":"Unicode character cycler","description":"This script cycles through certain Unicode characters while typing. It only\r\nworks if set encoding=utf-8.\r\n\r\nWhen on, the hyphen (-), period (.), apostrophe ('), and quote (\")\r\ncharacters are mapped to the appropriate functions within this file.\r\n\r\nWhen you enter two hyphen characters in a row, the first hyphen character\r\nwill cycle to an EN DASH character. A third hyphen will turn the EN DASH\r\ninto an EM DASH. A fourth hyphen will turn your EM DASH back into a\r\nHYPHEN-MINUS.\r\n\r\nEntering three periods in a row will replace all three periods with a\r\nHORIZONTAL ELLIPSIS character.\r\n\r\nEntering an apostrophe will try to determine if the apostrophe should be a\r\nLEFT SINGLE QUOTATION MARK or RIGHT SINGLE QUOTATION MARK. It does this by\r\nlooking at the character to the left of the new character. You can cycle\r\nbetween LEFT SINGLE QUOTATION MARK, APOSTROPHE, and RIGHT SINGLE QUOTATION\r\nMARK by repeatedly hitting your apostrophe key.\r\n\r\nQuote characters are treated in the same manner as apostrophe characters.\r\nYou get either a LEFT DOUBLE QUOTATION MARK, normal QUOTATION MARK, or RIGHT\r\nDOUBLE QUOTATION MARK based on the previous character and how many times you\r\nhit your quote key in a row.","4":"This script cycles through certain Unicode characters while typing. It only\r\nworks if set encoding=utf-8.\r\n\r\nWhen on, the hyphen (-), period (.), apostrophe ('), and quote (\")\r\ncharacters are mapped to the appropriate functions within this file.\r\n\r\nWhen you enter two hyphen characters in a row, the first hyphen character\r\nwill cycle to an EN DASH character. A third hyphen will turn the EN DASH\r\ninto an EM DASH. A fourth hyphen will turn your EM DASH back into a\r\nHYPHEN-MINUS.\r\n\r\nEntering three periods in a row will replace all three periods with a\r\nHORIZONTAL ELLIPSIS character.\r\n\r\nEntering an apostrophe will try to determine if the apostrophe should be a\r\nLEFT SINGLE QUOTATION MARK or RIGHT SINGLE QUOTATION MARK. It does this by\r\nlooking at the character to the left of the new character. You can cycle\r\nbetween LEFT SINGLE QUOTATION MARK, APOSTROPHE, and RIGHT SINGLE QUOTATION\r\nMARK by repeatedly hitting your apostrophe key.\r\n\r\nQuote characters are treated in the same manner as apostrophe characters.\r\nYou get either a LEFT DOUBLE QUOTATION MARK, normal QUOTATION MARK, or RIGHT\r\nDOUBLE QUOTATION MARK based on the previous character and how many times you\r\nhit your quote key in a row.","install_details":"To install, drop it in your plugins directory. To use, execute the\r\n:UniCycleOn command. Turn turn it off, execute :UniCycleOff.","5":"To install, drop it in your plugins directory. To use, execute the\r\n:UniCycleOn command. Turn turn it off, execute :UniCycleOff.","first_name":"Jason","6":"Jason","last_name":"Diamond","7":"Diamond","releases":[{"0":"1384","vim_version":"6.0","1":"6.0","script_version":"1","2":"1","version_comment":"Initial upload","3":"Initial upload","package":"unicycle.vim","4":"unicycle.vim","src_id":"4689","5":"4689","creation_date":"1129846915","6":"1129846915"}]},"1383":{"script_id":"1383","0":"1383","script_name":"SessionMgr","1":"SessionMgr","script_type":"utility","2":"utility","summary":"Simplified session management.","3":"Simplified session management.","description":"SessionMgr allows you to easilly and quickly save and restore multiple sessions within Vim.\r\n\r\nBased loosely on the plugin by Andrew Rodionoff:\r\n        http:\/\/www.vim.org\/scripts\/script.php?script_id=780","4":"SessionMgr allows you to easilly and quickly save and restore multiple sessions within Vim.\r\n\r\nBased loosely on the plugin by Andrew Rodionoff:\r\n        http:\/\/www.vim.org\/scripts\/script.php?script_id=780","install_details":"- Unzip the files into your Vim runtime path (vimfiles on Windows, .vim on Unix)\r\n- In Vim, run \\':helptags\\' to rebuild your help file\r\n- Restart Vim","5":"- Unzip the files into your Vim runtime path (vimfiles on Windows, .vim on Unix)\r\n- In Vim, run \\':helptags\\' to rebuild your help file\r\n- Restart Vim","first_name":"Jason","6":"Jason","last_name":"Heddings","7":"Heddings","releases":[{"0":"1383","vim_version":"6.0","1":"6.0","script_version":"1.1","2":"1.1","version_comment":"Initial upload","3":"Initial upload","package":"sessionmgr.zip","4":"sessionmgr.zip","src_id":"4687","5":"4687","creation_date":"1129807027","6":"1129807027"}]},"1382":{"script_id":"1382","0":"1382","script_name":"charon","1":"charon","script_type":"color scheme","2":"color scheme","summary":"Dark colorscheme based on peppers !","3":"Dark colorscheme based on peppers !","description":"Dark colorscheme based on peppers colrscheme by Iyer !","4":"Dark colorscheme based on peppers colrscheme by Iyer !","install_details":"Copy charon.vim to your colors\/ directory and then :colo charon","5":"Copy charon.vim to your colors\/ directory and then :colo charon","first_name":"Narayanan","6":"Narayanan","last_name":"Iyer","7":"Iyer","releases":[{"0":"1382","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"charon.vim","4":"charon.vim","src_id":"4678","5":"4678","creation_date":"1129533002","6":"1129533002"}]},"1381":{"script_id":"1381","0":"1381","script_name":"syntax\/udev.vim","1":"syntax\/udev.vim","script_type":"syntax","2":"syntax","summary":"Syntax highlighting for udev.rules","3":"Syntax highlighting for udev.rules","description":"Syntax highlighting for the udev.rules file.","4":"Syntax highlighting for the udev.rules file.","install_details":"Place the script in ~\/.vim\/syntax\/ . You may wish to create ~\/.vim\/ftdetect\/udev.vim containing something like au BufNewFile,BufRead *udev.rules* set filetype=udev","5":"Place the script in ~\/.vim\/syntax\/ . You may wish to create ~\/.vim\/ftdetect\/udev.vim containing something like au BufNewFile,BufRead *udev.rules* set filetype=udev","first_name":"Ciaran","6":"Ciaran","last_name":"McCreesh","7":"McCreesh","releases":[{"0":"1381","vim_version":"6.0","1":"6.0","script_version":"20051016","2":"20051016","version_comment":"Initial upload","3":"Initial upload","package":"udev.vim","4":"udev.vim","src_id":"4676","5":"4676","creation_date":"1129402091","6":"1129402091"}]},"1380":{"script_id":"1380","0":"1380","script_name":"cHeaderFinder","1":"cHeaderFinder","script_type":"utility","2":"utility","summary":"Finds header required by C functions.","3":"Finds header required by C functions.","description":"This script can find the header or list of headers requires by a particular C function. It uses man pages, chapters 2 and 3. If not found there, it uses the tags file in combination with the a.vim plugin.\r\nAll that without spoiling the jumplist!!!\r\n\r\nUnder suggested settings:\r\n\\f: gets all the headers required by the function under the cursor and puts them in the default register, so you can go to the top of the C source and 'p' them.\r\n\\a: goes to the header of the function under the cursor. It's usually where it *should* be documented.\r\n","4":"This script can find the header or list of headers requires by a particular C function. It uses man pages, chapters 2 and 3. If not found there, it uses the tags file in combination with the a.vim plugin.\r\nAll that without spoiling the jumplist!!!\r\n\r\nUnder suggested settings:\r\n\\f: gets all the headers required by the function under the cursor and puts them in the default register, so you can go to the top of the C source and 'p' them.\r\n\\a: goes to the header of the function under the cursor. It's usually where it *should* be documented.\r\n","install_details":"This script requires a.vim (http:\/\/www.vim.org\/scripts\/script.php?script_id=31).\r\n\r\nJust put the cHeaderFinder.vim in the plugin directory. Help is autoinstalled at the first run.\r\n\r\nIt does not bind any key by default. The recommended binds should be pasted in ~\/.vimrc:\r\nnnoremap <leader>f :call CHeaderFinder_HeadersFromFuncUnderCursor()<CR>\r\nnnoremap <leader>a :call CHeaderFinder_GotoHeaderFromFuncUnderCursor()<CR>\r\n\r\n","5":"This script requires a.vim (http:\/\/www.vim.org\/scripts\/script.php?script_id=31).\r\n\r\nJust put the cHeaderFinder.vim in the plugin directory. Help is autoinstalled at the first run.\r\n\r\nIt does not bind any key by default. The recommended binds should be pasted in ~\/.vimrc:\r\nnnoremap <leader>f :call CHeaderFinder_HeadersFromFuncUnderCursor()<CR>\r\nnnoremap <leader>a :call CHeaderFinder_GotoHeaderFromFuncUnderCursor()<CR>\r\n\r\n","first_name":"Leandro","6":"Leandro","last_name":"Penz","7":"Penz","releases":[{"0":"1380","vim_version":"6.0","1":"6.0","script_version":"1.3","2":"1.3","version_comment":"New function that uses tags to perform '[i' much faster.\r\nnnoremap <leader>[i :call CHeaderUtils_PrototypeFromFuncUnderCursor()<CR>\r\n","3":"New function that uses tags to perform '[i' much faster.\r\nnnoremap <leader>[i :call CHeaderUtils_PrototypeFromFuncUnderCursor()<CR>\r\n","package":"cHeaderUtils.vim","4":"cHeaderUtils.vim","src_id":"7242","5":"7242","creation_date":"1181735780","6":"1181735780"},{"0":"1380","vim_version":"6.0","1":"6.0","script_version":"1.2","2":"1.2","version_comment":"Initial upload","3":"Initial upload","package":"cHeaderFinder.vim","4":"cHeaderFinder.vim","src_id":"4675","5":"4675","creation_date":"1129365323","6":"1129365323"}]},"1379":{"script_id":"1379","0":"1379","script_name":"syntax\/uil.vim","1":"syntax\/uil.vim","script_type":"syntax","2":"syntax","summary":"Motif\/UIL Syntax","3":"Motif\/UIL Syntax","description":"This is a mirror of http:\/\/www.vim.org\/scripts\/script.php?script_id=1379\r\n\r\nThe original Motif\/UIL Syntax file is missing some keywords and hasn't got folding support. This version does!\r\n\r\n| Vim-Script\t|| https:\/\/www.vim.org\/scripts\/script.php?script_id=1379\r\n| Source\t|| https:\/\/github.com\/krischik\/vim-uil\r\n| Wiki\t\t|| https:\/\/github.com\/krischik\/vim-uil\/wiki\r\n| Releases\t|| https:\/\/github.com\/krischik\/vim-uil\/releases \r\n| Issues\t|| https:\/\/github.com\/krischik\/vim-uil\/issues \r\n| Discussions\t|| https:\/\/github.com\/krischik\/vim-uil\/discussions \r\n","4":"This is a mirror of http:\/\/www.vim.org\/scripts\/script.php?script_id=1379\r\n\r\nThe original Motif\/UIL Syntax file is missing some keywords and hasn't got folding support. This version does!\r\n\r\n| Vim-Script\t|| https:\/\/www.vim.org\/scripts\/script.php?script_id=1379\r\n| Source\t|| https:\/\/github.com\/krischik\/vim-uil\r\n| Wiki\t\t|| https:\/\/github.com\/krischik\/vim-uil\/wiki\r\n| Releases\t|| https:\/\/github.com\/krischik\/vim-uil\/releases \r\n| Issues\t|| https:\/\/github.com\/krischik\/vim-uil\/issues \r\n| Discussions\t|| https:\/\/github.com\/krischik\/vim-uil\/discussions \r\n","install_details":"Install from https:\/\/github.com\/krischik\/vim-uil using dein (https:\/\/github.com\/Shougo\/dein.vim) or similar:\r\n\r\ncall dein#begin('$HOME\/vimfiles\/bundles')\r\ncall dein#add('krischik\/vim-uil')\r\ncall dein#end()\r\ncall dein#install()","5":"Install from https:\/\/github.com\/krischik\/vim-uil using dein (https:\/\/github.com\/Shougo\/dein.vim) or similar:\r\n\r\ncall dein#begin('$HOME\/vimfiles\/bundles')\r\ncall dein#add('krischik\/vim-uil')\r\ncall dein#end()\r\ncall dein#install()","first_name":"Martin","6":"Martin","last_name":"Krischik","7":"Krischik","releases":[{"0":"1379","vim_version":"6.0","1":"6.0","script_version":"1.1","2":"1.1","version_comment":"Added operators.","3":"Added operators.","package":"uil.vim","4":"uil.vim","src_id":"5309","5":"5309","creation_date":"1140676889","6":"1140676889"},{"0":"1379","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"uil.vim","4":"uil.vim","src_id":"4672","5":"4672","creation_date":"1129188967","6":"1129188967"}]},"1378":{"script_id":"1378","0":"1378","script_name":"cfengine log file highlighting","1":"cfengine log file highlighting","script_type":"syntax","2":"syntax","summary":"Syntax highlighting for cfagent\/cfengine log files","3":"Syntax highlighting for cfagent\/cfengine log files","description":"Very early release and very buggy and incomplete, but it does work suitably enough that reading logfiles is no longer so difficult.  Currently highlights schedule changes, editfiles blocks, and when things \"change\" on the system (like when files get copied).  As I learn more about how to write syntax files, this should improve somewhat.","4":"Very early release and very buggy and incomplete, but it does work suitably enough that reading logfiles is no longer so difficult.  Currently highlights schedule changes, editfiles blocks, and when things \"change\" on the system (like when files get copied).  As I learn more about how to write syntax files, this should improve somewhat.","install_details":"Standard syntax script -- just stick in ~\/.vim\/syntax, and do :set syntax=cfengine-log to highlight stuff.","5":"Standard syntax script -- just stick in ~\/.vim\/syntax, and do :set syntax=cfengine-log to highlight stuff.","first_name":"Paul","6":"Paul","last_name":"Krizak","7":"Krizak","releases":[{"0":"1378","vim_version":"6.0","1":"6.0","script_version":"0.2","2":"0.2","version_comment":"Better color-coding for editfiles stuff, better consistency on color codes","3":"Better color-coding for editfiles stuff, better consistency on color codes","package":"cfengine-log.vim","4":"cfengine-log.vim","src_id":"4669","5":"4669","creation_date":"1129127145","6":"1129127145"},{"0":"1378","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"cfengine-log.vim","4":"cfengine-log.vim","src_id":"4668","5":"4668","creation_date":"1129111295","6":"1129111295"}]},"1377":{"script_id":"1377","0":"1377","script_name":"Chars2HTML","1":"Chars2HTML","script_type":"utility","2":"utility","summary":"Converting special characters to HTML","3":"Converting special characters to HTML","description":"This plugin will convert between characters(ISO-8859-1) and their HTML \\\\\\\"&xxxxxx;\\\\\\\" entity in the current file. Its a rewrite of html_da vim vimscript #1163, this plugin can be used on all filetypes and contains more special characters and their HTML encoding. Nice plugin if you often copy text to use as HTML, with special european characters(ISO-8859-1), embedded in various programming languages.","4":"This plugin will convert between characters(ISO-8859-1) and their HTML \\\\\\\"&xxxxxx;\\\\\\\" entity in the current file. Its a rewrite of html_da vim vimscript #1163, this plugin can be used on all filetypes and contains more special characters and their HTML encoding. Nice plugin if you often copy text to use as HTML, with special european characters(ISO-8859-1), embedded in various programming languages.","install_details":"Put this file in your plugin directory ~\/.vim\/plugin.\r\nPut a mapping in your .vimrc to call the commands ConvertChars2Html and ConvertHtml2Chars like this:\r\nmap ,ch :ConvertChars2Html<CR>\r\nmap ,hc :ConvertHtml2Chars<CR>\r\n\r\n\r\n","5":"Put this file in your plugin directory ~\/.vim\/plugin.\r\nPut a mapping in your .vimrc to call the commands ConvertChars2Html and ConvertHtml2Chars like this:\r\nmap ,ch :ConvertChars2Html<CR>\r\nmap ,hc :ConvertHtml2Chars<CR>\r\n\r\n\r\n","first_name":"Jens Juul","6":"Jens Juul","last_name":"Christensen","7":"Christensen","releases":[{"0":"1377","vim_version":"6.0","1":"6.0","script_version":"1.1","2":"1.1","version_comment":"Fixed a misspelling and added the option to also convert html back to chars again. Thanks to  Fran\u00c3\u00a7ois Wendling","3":"Fixed a misspelling and added the option to also convert html back to chars again. Thanks to  Fran\u00c3\u00a7ois Wendling","package":"Chars2HTML.vim","4":"Chars2HTML.vim","src_id":"4718","5":"4718","creation_date":"1131018651","6":"1131018651"},{"0":"1377","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"Chars2HTML.vim","4":"Chars2HTML.vim","src_id":"4659","5":"4659","creation_date":"1128859522","6":"1128859522"}]},"1376":{"script_id":"1376","0":"1376","script_name":"fpc.vim","1":"fpc.vim","script_type":"utility","2":"utility","summary":"\"Free Pascal Compiler\" compiler plugin.","3":"\"Free Pascal Compiler\" compiler plugin.","description":"FPC compiler plugin.","4":"FPC compiler plugin.","install_details":"","5":"","first_name":"Jaroslaw","6":"Jaroslaw","last_name":"Blasiok","7":"Blasiok","releases":[{"0":"1376","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"fpc.vim","4":"fpc.vim","src_id":"4654","5":"4654","creation_date":"1128664671","6":"1128664671"}]},"1375":{"script_id":"1375","0":"1375","script_name":"QFixToggle","1":"QFixToggle","script_type":"utility","2":"utility","summary":"Toggle the visibility of the quickfix window","3":"Toggle the visibility of the quickfix window","description":"QFixToggle allows you to toggle the visibility of the |quickfix| window\r\neasilly.  The goal is to provide easy access to the error list when\r\nprogramming or searching for text.\r\n\r\nThanks to Hari for the help on the auto-commands.","4":"QFixToggle allows you to toggle the visibility of the |quickfix| window\r\neasilly.  The goal is to provide easy access to the error list when\r\nprogramming or searching for text.\r\n\r\nThanks to Hari for the help on the auto-commands.","install_details":"- Unzip the files into your Vim runtime path (vimfiles on Windows, .vim on Unix)\r\n- In Vim, run ':helptags' to rebuild your help file\r\n- Restart Vim","5":"- Unzip the files into your Vim runtime path (vimfiles on Windows, .vim on Unix)\r\n- In Vim, run ':helptags' to rebuild your help file\r\n- Restart Vim","first_name":"Jason","6":"Jason","last_name":"Heddings","7":"Heddings","releases":[{"0":"1375","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"qfixtoggle.zip","4":"qfixtoggle.zip","src_id":"4651","5":"4651","creation_date":"1128499213","6":"1128499213"}]},"1374":{"script_id":"1374","0":"1374","script_name":"TailMinusF","1":"TailMinusF","script_type":"utility","2":"utility","summary":"Provides near real-time update of a file in the preview window.","3":"Provides near real-time update of a file in the preview window.","description":"TailMinusF allows you to view the contents of a file in real time.  When a\r\nchange in the file is detected, the window displaying the file is updated and\r\nrepositioned to the last line.\r\n\r\nThe update is not exactly real time, but usually updates within a few seconds\r\nof the file change.  The update interval of the output is determined by the\r\n|updatetime| parameter, along with continued usage of Vim.  This means that if\r\nyou are not doing any editing or motion commands, the preview window will not\r\nbe updated.  See |CursorHold| for more information.\r\n\r\nBecause this window becomes the preview window, it will accept all related\r\ncommands.  For more information, see |preview-window|.\r\n\r\nOnce installed, simply use \\':Tail <filename>\\' to see the file.\r\n Use ':pclose' to close this window.","4":"TailMinusF allows you to view the contents of a file in real time.  When a\r\nchange in the file is detected, the window displaying the file is updated and\r\nrepositioned to the last line.\r\n\r\nThe update is not exactly real time, but usually updates within a few seconds\r\nof the file change.  The update interval of the output is determined by the\r\n|updatetime| parameter, along with continued usage of Vim.  This means that if\r\nyou are not doing any editing or motion commands, the preview window will not\r\nbe updated.  See |CursorHold| for more information.\r\n\r\nBecause this window becomes the preview window, it will accept all related\r\ncommands.  For more information, see |preview-window|.\r\n\r\nOnce installed, simply use \\':Tail <filename>\\' to see the file.\r\n Use ':pclose' to close this window.","install_details":"- Unzip the files into your Vim runtime path (vimfiles on Windows, .vim on Unix)\r\n- In Vim, run \\':helptags\\' to rebuild your help file\r\n- Restart Vim","5":"- Unzip the files into your Vim runtime path (vimfiles on Windows, .vim on Unix)\r\n- In Vim, run \\':helptags\\' to rebuild your help file\r\n- Restart Vim","first_name":"Jason","6":"Jason","last_name":"Heddings","7":"Heddings","releases":[{"0":"1374","vim_version":"6.0","1":"6.0","script_version":"1.1","2":"1.1","version_comment":"Corrected file format for greater compatibility.","3":"Corrected file format for greater compatibility.","package":"tailminusf.zip","4":"tailminusf.zip","src_id":"4688","5":"4688","creation_date":"1129807184","6":"1129807184"},{"0":"1374","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"tailminusf.zip","4":"tailminusf.zip","src_id":"4650","5":"4650","creation_date":"1128440480","6":"1128440480"}]},"1373":{"script_id":"1373","0":"1373","script_name":"asmh8300","1":"asmh8300","script_type":"syntax","2":"syntax","summary":"Hitachi H8S, H8\/300 assemble language syntax","3":"Hitachi H8S, H8\/300 assemble language syntax","description":"My work is writing firmware of H8 mpu now. So I need a better syntax file than old one. I try to improve the official syntax file. My improved one will highlight the keywords more correctly, and highlight the branch command , like \"bhi, blo, ...\" with different color. ","4":"My work is writing firmware of H8 mpu now. So I need a better syntax file than old one. I try to improve the official syntax file. My improved one will highlight the keywords more correctly, and highlight the branch command , like \"bhi, blo, ...\" with different color. ","install_details":"just replace asmh8300.vim in \"syntax\" dir with my file.","5":"just replace asmh8300.vim in \"syntax\" dir with my file.","first_name":"ChonBin","6":"ChonBin","last_name":"Liao","7":"Liao","releases":[{"0":"1373","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"asmh8300.vim","4":"asmh8300.vim","src_id":"4647","5":"4647","creation_date":"1128365769","6":"1128365769"}]},"1372":{"script_id":"1372","0":"1372","script_name":"ldap.vim","1":"ldap.vim","script_type":"utility","2":"utility","summary":"Active Directory Email Lookup using Python and LDAP","3":"Active Directory Email Lookup using Python and LDAP","description":"This script is designed to give LDAP access from within VIM using a Python script.  I developed this script to retrieve email addresses from a Microsoft Exchange server using an Active Directory for usernames, but the script should be easily used with any LDAP server.  In my never-ending quest to never again use MS Windows, I use mutt to read mail and vim to write new messages.  This led to the inevitable problem of looking up people's email addresses without opening Outlook, which led me to writing this script.\r\n\r\nThe script maps the key ^F for insert mode only.  Typing in a person's username followed by ^F will retrieve their email address from the LDAP server and place the first result found in place of the username searched for.\r\n\r\nThe script must be setup with the appropriate server, search base, and (if needed) username\/password before use.  See comments within the script for setup details.\r\n\r\nNote that this script is not generic, I wrote it to fulfill my need and am providing it here simply so that anyone else who needs a similar capability has an example of how to start.","4":"This script is designed to give LDAP access from within VIM using a Python script.  I developed this script to retrieve email addresses from a Microsoft Exchange server using an Active Directory for usernames, but the script should be easily used with any LDAP server.  In my never-ending quest to never again use MS Windows, I use mutt to read mail and vim to write new messages.  This led to the inevitable problem of looking up people's email addresses without opening Outlook, which led me to writing this script.\r\n\r\nThe script maps the key ^F for insert mode only.  Typing in a person's username followed by ^F will retrieve their email address from the LDAP server and place the first result found in place of the username searched for.\r\n\r\nThe script must be setup with the appropriate server, search base, and (if needed) username\/password before use.  See comments within the script for setup details.\r\n\r\nNote that this script is not generic, I wrote it to fulfill my need and am providing it here simply so that anyone else who needs a similar capability has an example of how to start.","install_details":"This script requires the following applications:\r\n\r\nVIM (version 6.0 or newer)\r\nPython\r\nPython-ldap\r\n\r\nInstall the script to your plugins directory.","5":"This script requires the following applications:\r\n\r\nVIM (version 6.0 or newer)\r\nPython\r\nPython-ldap\r\n\r\nInstall the script to your plugins directory.","first_name":"David","6":"David","last_name":"Morris","7":"Morris","releases":[{"0":"1372","vim_version":"6.0","1":"6.0","script_version":"0.91","2":"0.91","version_comment":"Initial upload was wrong version of file.","3":"Initial upload was wrong version of file.","package":"ldap.vim","4":"ldap.vim","src_id":"4649","5":"4649","creation_date":"1128430339","6":"1128430339"}]},"1371":{"script_id":"1371","0":"1371","script_name":"TextMarker","1":"TextMarker","script_type":"utility","2":"utility","summary":"GUI to mark same words in a file using mouse and toolbar buttons, fast and easy","3":"GUI to mark same words in a file using mouse and toolbar buttons, fast and easy","description":"Place the cursor over the word you want to mark and press the TextMarker button in the toolbar or place the mouse cursor over the word you want to mark and use the right mouse button menue or place the mouse cursor over the word you want to mark and press the middle (wheel) mouse button. Using the middle mouse button will colorize the words in different colors for each mouse click.\r\n\r\nIt is also possible to remove the color markers using the same methode.\r\n\r\nHere you can see a screenshot:\r\nhttp:\/\/andreasthoelke.bplaced.net\/Vim\/screenshot.png","4":"Place the cursor over the word you want to mark and press the TextMarker button in the toolbar or place the mouse cursor over the word you want to mark and use the right mouse button menue or place the mouse cursor over the word you want to mark and press the middle (wheel) mouse button. Using the middle mouse button will colorize the words in different colors for each mouse click.\r\n\r\nIt is also possible to remove the color markers using the same methode.\r\n\r\nHere you can see a screenshot:\r\nhttp:\/\/andreasthoelke.bplaced.net\/Vim\/screenshot.png","install_details":"You have to do two things:\r\n1. Copy the textmarker.vim file into the plugin directory so it will be automatically sourced.\r\n2. The Buttons of the toolbar are small bitmap files. The BMP's must be stored into the bitmaps directory.\r\n\r\nYou can find the zipped bitmap files here:\r\nhttp:\/\/andreasthoelke.bplaced.net\/Vim\/index.html\r\nCopy the files: \r\n    lightBlue.bmp\r\n    lightCyan.bmp\r\n    lightGreen.bmp\r\n    lightMagenta.bmp\r\n    lightRed.bmp\r\n    lightYellow.bmp\r\n    white.bmp\r\ninto the directory bitmaps so they will be placed into the toolbar automaticaly.","5":"You have to do two things:\r\n1. Copy the textmarker.vim file into the plugin directory so it will be automatically sourced.\r\n2. The Buttons of the toolbar are small bitmap files. The BMP's must be stored into the bitmaps directory.\r\n\r\nYou can find the zipped bitmap files here:\r\nhttp:\/\/andreasthoelke.bplaced.net\/Vim\/index.html\r\nCopy the files: \r\n    lightBlue.bmp\r\n    lightCyan.bmp\r\n    lightGreen.bmp\r\n    lightMagenta.bmp\r\n    lightRed.bmp\r\n    lightYellow.bmp\r\n    white.bmp\r\ninto the directory bitmaps so they will be placed into the toolbar automaticaly.","first_name":"Andreas","6":"Andreas","last_name":"Thoelke","7":"Thoelke","releases":[{"0":"1371","vim_version":"6.0","1":"6.0","script_version":"1.0.0","2":"1.0.0","version_comment":"Initial upload","3":"Initial upload","package":"textmarker.vim","4":"textmarker.vim","src_id":"4639","5":"4639","creation_date":"1128093773","6":"1128093773"}]},"1370":{"script_id":"1370","0":"1370","script_name":"CVSconflict","1":"CVSconflict","script_type":"utility","2":"utility","summary":"CVS conflict resolution using vimdiff","3":"CVS conflict resolution using vimdiff","description":"CVS conflict resolution using vimdiff\r\n\r\nWhen one does \"cvs update\", one may get files marked with \"C\" for conflict.  Cvs was unable to automatically merge one's local version of such files with the repository's version, and so merging requires human intervention.  The :CVSconflict command takes the current conflict file, splits it into two separate files, and enables vimdiff-style editing and viewing.\r\n\r\nA command,\r\n\r\n  :CVSconflict\r\n\r\nis provided which transforms the current file containing cvs conflict sections such as\r\n\r\n  <<<<<<<\r\n  ...local version...\r\n  =======\r\n  ...repository version...\r\n  >>>>>>>\r\n\r\ninto two side by side versions.  Vim\\'s diff mode is enabled with these two windows, greatly facilitating the production of a merged file.\r\n\r\n(alpha\/beta version available at http:\/\/www.drchip.org\/astronaut\/vim\/index.html#CVSCONFLICT)\r\n","4":"CVS conflict resolution using vimdiff\r\n\r\nWhen one does \"cvs update\", one may get files marked with \"C\" for conflict.  Cvs was unable to automatically merge one's local version of such files with the repository's version, and so merging requires human intervention.  The :CVSconflict command takes the current conflict file, splits it into two separate files, and enables vimdiff-style editing and viewing.\r\n\r\nA command,\r\n\r\n  :CVSconflict\r\n\r\nis provided which transforms the current file containing cvs conflict sections such as\r\n\r\n  <<<<<<<\r\n  ...local version...\r\n  =======\r\n  ...repository version...\r\n  >>>>>>>\r\n\r\ninto two side by side versions.  Vim\\'s diff mode is enabled with these two windows, greatly facilitating the production of a merged file.\r\n\r\n(alpha\/beta version available at http:\/\/www.drchip.org\/astronaut\/vim\/index.html#CVSCONFLICT)\r\n","install_details":"1. Place copy in your .vim\/plugin (vimfiles\\plugin) directory\r\n2. gunzip CVSconflict.vim.gz\r\n\r\nThe file should automatically set up help the next time you fire up vim.","5":"1. Place copy in your .vim\/plugin (vimfiles\\plugin) directory\r\n2. gunzip CVSconflict.vim.gz\r\n\r\nThe file should automatically set up help the next time you fire up vim.","first_name":"Charles","6":"Charles","last_name":"Campbell","7":"Campbell","releases":[{"0":"1370","vim_version":"6.0","1":"6.0","script_version":"1","2":"1","version_comment":"When one does \"cvs update\", one may get files marked with \"C\" for conflict.  Cvs was unable to automatically merge one's local version with the repository, and merging requires human intervention.  The :CVSconflict command takes the current conflict file, splits it into two separate files, and enables vimdiff-style editing and viewing.\r\n","3":"When one does \"cvs update\", one may get files marked with \"C\" for conflict.  Cvs was unable to automatically merge one's local version with the repository, and merging requires human intervention.  The :CVSconflict command takes the current conflict file, splits it into two separate files, and enables vimdiff-style editing and viewing.\r\n","package":"CVSconflict.vim.gz","4":"CVSconflict.vim.gz","src_id":"4631","5":"4631","creation_date":"1127995170","6":"1127995170"}]},"1369":{"script_id":"1369","0":"1369","script_name":"Zopedav","1":"Zopedav","script_type":"ftplugin","2":"ftplugin","summary":"Handles remote editing with WebDAV, including zope","3":"Handles remote editing with WebDAV, including zope","description":"This script allows editing of WebDAV resources and is zope-aware. \r\nThis plugin does not conflict with netrw and catches the \r\nwebdav:\/\/ and zope:\/\/ url schemes.\r\n\r\n- Zope scheme\r\nzope:\/\/[username:password@]host[:port]\/path\/to\/document urls are \r\nGET using a \"\/document_src\" suffix and\r\nPUT using no suffix\r\n\r\n- WebDAV scheme\r\nwebdav:\/\/[username:password@]host[:port]\/path\/to\/document urls are \r\nGET using no suffix and\r\nPUT using no suffix\r\n\r\n- Using SSL\r\nShall you need to use ssl, add an \"s\" prefix to the protocol, for instance\r\nszope:\/\/securedhost\/some\/private\/document.dtml\r\nswebdav:\/\/securedhost\/some\/private\/document\r\n\r\n- Options\r\nIf you intent on editing every WebDAV resource under the \"\/source\"\r\nurl suffix or\/and upload them back under the \"\/upload\" suffix, use the\r\nfollowing options in your .vimrc :\r\nlet g:webdav_get_suffix = \"\/source\"\r\nlet g:webdav_put_suffix = \"\/upload\"\r\n\r\nNB: No error handling is performed\r\nNB: See also vimscript #1075 \r\n","4":"This script allows editing of WebDAV resources and is zope-aware. \r\nThis plugin does not conflict with netrw and catches the \r\nwebdav:\/\/ and zope:\/\/ url schemes.\r\n\r\n- Zope scheme\r\nzope:\/\/[username:password@]host[:port]\/path\/to\/document urls are \r\nGET using a \"\/document_src\" suffix and\r\nPUT using no suffix\r\n\r\n- WebDAV scheme\r\nwebdav:\/\/[username:password@]host[:port]\/path\/to\/document urls are \r\nGET using no suffix and\r\nPUT using no suffix\r\n\r\n- Using SSL\r\nShall you need to use ssl, add an \"s\" prefix to the protocol, for instance\r\nszope:\/\/securedhost\/some\/private\/document.dtml\r\nswebdav:\/\/securedhost\/some\/private\/document\r\n\r\n- Options\r\nIf you intent on editing every WebDAV resource under the \"\/source\"\r\nurl suffix or\/and upload them back under the \"\/upload\" suffix, use the\r\nfollowing options in your .vimrc :\r\nlet g:webdav_get_suffix = \"\/source\"\r\nlet g:webdav_put_suffix = \"\/upload\"\r\n\r\nNB: No error handling is performed\r\nNB: See also vimscript #1075 \r\n","install_details":"- Download cURL from http:\/\/curl.haxx.se\/download.html and put curl executable in your path\r\n- Put zopedav.vim in your $VIMRUNTIME\/plugin directory\r\n- Edit any zope:\/\/localhost:8080\/some\/document.dtml or webdav:\/\/localhost:8080\/document\r\n","5":"- Download cURL from http:\/\/curl.haxx.se\/download.html and put curl executable in your path\r\n- Put zopedav.vim in your $VIMRUNTIME\/plugin directory\r\n- Edit any zope:\/\/localhost:8080\/some\/document.dtml or webdav:\/\/localhost:8080\/document\r\n","first_name":"S\u00c3\u00a9bastien","6":"S\u00c3\u00a9bastien","last_name":"Migniot","7":"Migniot","releases":[{"0":"1369","vim_version":"6.0","1":"6.0","script_version":"2.0","2":"2.0","version_comment":"Version 1.0 was a script kiddie thing. Version 2.0 is robust, uses cURL for WebDAV communication and is ready for Zope out-of-the-box. Version 2.0 can also edit standard WebDAV resources as well.","3":"Version 1.0 was a script kiddie thing. Version 2.0 is robust, uses cURL for WebDAV communication and is ready for Zope out-of-the-box. Version 2.0 can also edit standard WebDAV resources as well.","package":"zopedav.vim","4":"zopedav.vim","src_id":"9189","5":"9189","creation_date":"1219918302","6":"1219918302"},{"0":"1369","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"zopedav.vim","4":"zopedav.vim","src_id":"4624","5":"4624","creation_date":"1127612053","6":"1127612053"}]},"1368":{"script_id":"1368","0":"1368","script_name":"bookmarks.vim","1":"bookmarks.vim","script_type":"utility","2":"utility","summary":"Menu driven bookmarks for gvim","3":"Menu driven bookmarks for gvim","description":" BOOKMARKS OVERVIEW\r\n ------------------\r\n Bookmarks.vim provides an intuitive menu driven interface to facilitate \r\n bookmarking files and directories in gvim.  \r\n \r\n    Bookmark Features:\r\n       -Configurable \\\"popup\\\" bookmark menu\r\n       -Bookmarks contain file name and part of text from bookmarked file, making it easier to remember.\r\n       -The whitespace in bookmarks is compressed, increasing readability.\r\n       -Can have unlimited number of bookmarks.\r\n       -Can bookmark place in help files.\r\n       -Can bookmark local files, remote files, and directories.\r\n       -Can bookmark blank lines - Line number used.\r\n       -Can bookmark gvim on-line help docs.\r\n       -Includes full function bookmark editor -- It\\'s called gvim!\r\n","4":" BOOKMARKS OVERVIEW\r\n ------------------\r\n Bookmarks.vim provides an intuitive menu driven interface to facilitate \r\n bookmarking files and directories in gvim.  \r\n \r\n    Bookmark Features:\r\n       -Configurable \\\"popup\\\" bookmark menu\r\n       -Bookmarks contain file name and part of text from bookmarked file, making it easier to remember.\r\n       -The whitespace in bookmarks is compressed, increasing readability.\r\n       -Can have unlimited number of bookmarks.\r\n       -Can bookmark place in help files.\r\n       -Can bookmark local files, remote files, and directories.\r\n       -Can bookmark blank lines - Line number used.\r\n       -Can bookmark gvim on-line help docs.\r\n       -Includes full function bookmark editor -- It\\'s called gvim!\r\n","install_details":" INSTALLATION\r\n ------------\r\n 1. Copy the bookmarks.vim script to the $HOME\/.vim\/plugin or the $HOME\/vimfiles\/plugin or the $VIM\/vimfiles directory.  Refer to the \\':help add-plugin\\', \\':help add-global-plugin\\' and \\':help runtimepath\\' topics for more details about gvim plugins.\r\n\r\n 2. If you do not want the popup menu enabled (<C-RightMouse>) then add this line to your $HOME\/.vimrc (not .gvimrc):\r\n\r\n       let bm_popup = \\\"off\\\"\r\n\r\n 2. Restart gvim.\r\n","5":" INSTALLATION\r\n ------------\r\n 1. Copy the bookmarks.vim script to the $HOME\/.vim\/plugin or the $HOME\/vimfiles\/plugin or the $VIM\/vimfiles directory.  Refer to the \\':help add-plugin\\', \\':help add-global-plugin\\' and \\':help runtimepath\\' topics for more details about gvim plugins.\r\n\r\n 2. If you do not want the popup menu enabled (<C-RightMouse>) then add this line to your $HOME\/.vimrc (not .gvimrc):\r\n\r\n       let bm_popup = \\\"off\\\"\r\n\r\n 2. Restart gvim.\r\n","first_name":"Bernie","6":"Bernie","last_name":"Barton","7":"Barton","releases":[{"0":"1368","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"bookmarks.vim","4":"bookmarks.vim","src_id":"4622","5":"4622","creation_date":"1127491341","6":"1127491341"}]},"1367":{"script_id":"1367","0":"1367","script_name":"syntax\/conkyrc.vim","1":"syntax\/conkyrc.vim","script_type":"syntax","2":"syntax","summary":"Conky conkyrc syntax highlighting","3":"Conky conkyrc syntax highlighting","description":"Syntax highlighting for conkyrc files used by the the Conky system monitor (http:\/\/conky.sourceforge.net\/).","4":"Syntax highlighting for conkyrc files used by the the Conky system monitor (http:\/\/conky.sourceforge.net\/).","install_details":"Place it into ~\/.vim\/syntax\/. You may wish to create a ~\/.vim\/ftdetect\/conkyrc.vim file containing something like:\r\n    au BufNewFile,BufRead *conkyrc set filetype=conkyrc","5":"Place it into ~\/.vim\/syntax\/. You may wish to create a ~\/.vim\/ftdetect\/conkyrc.vim file containing something like:\r\n    au BufNewFile,BufRead *conkyrc set filetype=conkyrc","first_name":"Ciaran","6":"Ciaran","last_name":"McCreesh","7":"McCreesh","releases":[{"0":"1367","vim_version":"6.0","1":"6.0","script_version":"20050923","2":"20050923","version_comment":"Initial upload","3":"Initial upload","package":"conkyrc.vim","4":"conkyrc.vim","src_id":"4621","5":"4621","creation_date":"1127487543","6":"1127487543"}]},"1366":{"script_id":"1366","0":"1366","script_name":"Peppers","1":"Peppers","script_type":"color scheme","2":"color scheme","summary":"The ultimate dark color scheme...","3":"The ultimate dark color scheme...","description":"The ultimate dark color scheme...well, atleast a pretty good one.\r\nEasy on the eyes and suited for most programming languages.","4":"The ultimate dark color scheme...well, atleast a pretty good one.\r\nEasy on the eyes and suited for most programming languages.","install_details":"Copy peppers.vim to your colors directory\r\nAnd from Vim, :colo peppers to launch the new colorscheme","5":"Copy peppers.vim to your colors directory\r\nAnd from Vim, :colo peppers to launch the new colorscheme","first_name":"Narayanan","6":"Narayanan","last_name":"Iyer","7":"Iyer","releases":[{"0":"1366","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"peppers.vim","4":"peppers.vim","src_id":"4613","5":"4613","creation_date":"1127439658","6":"1127439658"}]},"1365":{"script_id":"1365","0":"1365","script_name":"adobe.vim","1":"adobe.vim","script_type":"color scheme","2":"color scheme","summary":"Adobe theme, easy on eyes. Coloring philosophy inside.","3":"Adobe theme, easy on eyes. Coloring philosophy inside.","description":"I'm now maintaining this in git as a gist. Visit this to download\/clone\/improve the up-to-date version, and view screenshots: https:\/\/gist.github.com\/720355\r\n\r\nGreat for many programming languages, especially Python.  Also cursory testing of bash, perl, html, vim, java, c++, moin, and mutt. Includes console coloring to match GUI colors (for tested cases, please let me know of ones I missed).\r\n\r\nMore details in my blog article: http:\/\/micahelliott.com\/2008\/12\/editor-color-scheme-philosophy","4":"I'm now maintaining this in git as a gist. Visit this to download\/clone\/improve the up-to-date version, and view screenshots: https:\/\/gist.github.com\/720355\r\n\r\nGreat for many programming languages, especially Python.  Also cursory testing of bash, perl, html, vim, java, c++, moin, and mutt. Includes console coloring to match GUI colors (for tested cases, please let me know of ones I missed).\r\n\r\nMore details in my blog article: http:\/\/micahelliott.com\/2008\/12\/editor-color-scheme-philosophy","install_details":"Put this in your ~\/.vim\/colors dir and within vim type \":colo adobe\" from the ex command line.","5":"Put this in your ~\/.vim\/colors dir and within vim type \":colo adobe\" from the ex command line.","first_name":"Micah","6":"Micah","last_name":"Elliott","7":"Elliott","releases":[{"0":"1365","vim_version":"7.0","1":"7.0","script_version":"0.3","2":"0.3","version_comment":"Major overhaul.  Now supports extended comment format.  Full 256 color support, matching the GUI scheme.  More accommodations for Python.  Also now working better with Perl, Moin, mutt. ","3":"Major overhaul.  Now supports extended comment format.  Full 256 color support, matching the GUI scheme.  More accommodations for Python.  Also now working better with Perl, Moin, mutt. ","package":"adobe.vim","4":"adobe.vim","src_id":"9718","5":"9718","creation_date":"1230021141","6":"1230021141"},{"0":"1365","vim_version":"6.0","1":"6.0","script_version":"0.2","2":"0.2","version_comment":"Made colors more usable across languages (python, bash, rst).\r\nFixed duplication of some colors in bash.\r\nMade cterm more consistent with gui.","3":"Made colors more usable across languages (python, bash, rst).\r\nFixed duplication of some colors in bash.\r\nMade cterm more consistent with gui.","package":"adobe.vim","4":"adobe.vim","src_id":"4617","5":"4617","creation_date":"1127464147","6":"1127464147"},{"0":"1365","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Fixed colors_name to reflect \"adobe\".","3":"Fixed colors_name to reflect \"adobe\".","package":"adobe.vim","4":"adobe.vim","src_id":"4615","5":"4615","creation_date":"1127459765","6":"1127459765"}]},"1364":{"script_id":"1364","0":"1364","script_name":"xslhelper.vim","1":"xslhelper.vim","script_type":"ftplugin","2":"ftplugin","summary":"Help for writing XSLT stylesheets","3":"Help for writing XSLT stylesheets","description":"Very basic helper abbreviations for writing xslt stylesheets. Like vivek Venugopalan's dbhelper.vim, uses the format \",<abbrev>\", as in:\r\n,tm ==> <xsl:template match=\"\"><\/xsl:template>\r\n,at ==> <xsl:apply-templates\/>\r\n\r\nIt helps me a ton, hope it helps you too. Please send feedback to andrews AT oreilly.com.\r\n\r\nCheers.","4":"Very basic helper abbreviations for writing xslt stylesheets. Like vivek Venugopalan's dbhelper.vim, uses the format \",<abbrev>\", as in:\r\n,tm ==> <xsl:template match=\"\"><\/xsl:template>\r\n,at ==> <xsl:apply-templates\/>\r\n\r\nIt helps me a ton, hope it helps you too. Please send feedback to andrews AT oreilly.com.\r\n\r\nCheers.","install_details":"I added it to my ftplugin directory, and put the following in my vimrc file:\r\naugroup BEGIN\r\n   au! BufRead,BufNewFile *.xsl source $VIM\\vim63\\ftplugin\\xslhelper.vim\r\naugroup END\r\n","5":"I added it to my ftplugin directory, and put the following in my vimrc file:\r\naugroup BEGIN\r\n   au! BufRead,BufNewFile *.xsl source $VIM\\vim63\\ftplugin\\xslhelper.vim\r\naugroup END\r\n","first_name":"Andrew","6":"Andrew","last_name":"Savikas","7":"Savikas","releases":[{"0":"1364","vim_version":"6.0","1":"6.0","script_version":"1.3","2":"1.3","version_comment":"Fixed a minor glitch in the <xsl:call-template> abbreviation.","3":"Fixed a minor glitch in the <xsl:call-template> abbreviation.","package":"xslhelper.tar.gz","4":"xslhelper.tar.gz","src_id":"4620","5":"4620","creation_date":"1127480620","6":"1127480620"},{"0":"1364","vim_version":"6.0","1":"6.0","script_version":"1.2","2":"1.2","version_comment":"Fixed bug in ,co (<xsl:copy-of>) abbreviation. Now correctly closes with <\/xsl:copy-of> instead of <\/xsl:copy>.","3":"Fixed bug in ,co (<xsl:copy-of>) abbreviation. Now correctly closes with <\/xsl:copy-of> instead of <\/xsl:copy>.","package":"xslhelper.tar.gz","4":"xslhelper.tar.gz","src_id":"4619","5":"4619","creation_date":"1127472616","6":"1127472616"},{"0":"1364","vim_version":"6.0","1":"6.0","script_version":"1.1","2":"1.1","version_comment":"Added documentation (courtesy of Keith Fahlgren) explicitly showing the result of each abbreviation.","3":"Added documentation (courtesy of Keith Fahlgren) explicitly showing the result of each abbreviation.","package":"xslhelper.tar.gz","4":"xslhelper.tar.gz","src_id":"4616","5":"4616","creation_date":"1127463868","6":"1127463868"},{"0":"1364","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"xslhelper.tar.gz","4":"xslhelper.tar.gz","src_id":"4610","5":"4610","creation_date":"1127394724","6":"1127394724"}]},"1363":{"script_id":"1363","0":"1363","script_name":"cloudy","1":"cloudy","script_type":"color scheme","2":"color scheme","summary":"A deep blue cloudy color scheme","3":"A deep blue cloudy color scheme","description":"Perfect for a rainy day !","4":"Perfect for a rainy day !","install_details":"Just copy cloudy.vim to your colors directory and then from vim, type :colo cloudy.vim","5":"Just copy cloudy.vim to your colors directory and then from vim, type :colo cloudy.vim","first_name":"Narayanan","6":"Narayanan","last_name":"Iyer","7":"Iyer","releases":[{"0":"1363","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"cloudy.vim","4":"cloudy.vim","src_id":"4605","5":"4605","creation_date":"1127271647","6":"1127271647"}]},"1362":{"script_id":"1362","0":"1362","script_name":"Last Modified","1":"Last Modified","script_type":"utility","2":"utility","summary":"Changes the Last modified date of a file","3":"Changes the Last modified date of a file","description":"It changes the Last modified date automatically without changing the format of the time you use\r\nHere i added some extra features ----\r\n   1> It checks the time format in the file you are working on and the format given in the plugin. If both are same, it changes the time, other wise it shows you a warning.\r\n   2> It does not change any other thing in the file.\r\n\r\n","4":"It changes the Last modified date automatically without changing the format of the time you use\r\nHere i added some extra features ----\r\n   1> It checks the time format in the file you are working on and the format given in the plugin. If both are same, it changes the time, other wise it shows you a warning.\r\n   2> It does not change any other thing in the file.\r\n\r\n","install_details":"simply copy the file lastModifed.vim in the ....\/Vim\/vimfiles\/plugin and Please change the following things if necessary\r\n    a> Change the variable 's:timeStampLeader' to the string which you use in your code (by default which is \"Last Modified\")\r\n    b> Change the variable 'timeStampFormat'. Put an example of the time format you want.\r\n    c> Change the variable 'timeStampString'. Change it to get the proper time stamp. Read the comments in the file to change the variable.","5":"simply copy the file lastModifed.vim in the ....\/Vim\/vimfiles\/plugin and Please change the following things if necessary\r\n    a> Change the variable 's:timeStampLeader' to the string which you use in your code (by default which is \"Last Modified\")\r\n    b> Change the variable 'timeStampFormat'. Put an example of the time format you want.\r\n    c> Change the variable 'timeStampString'. Change it to get the proper time stamp. Read the comments in the file to change the variable.","first_name":"Sudipta","6":"Sudipta","last_name":"Ghorui","7":"Ghorui","releases":[{"0":"1362","vim_version":"7.0","1":"7.0","script_version":"1.2","2":"1.2","version_comment":"Tested in FC 2 and in C and CPP files","3":"Tested in FC 2 and in C and CPP files","package":"lastModified.vim","4":"lastModified.vim","src_id":"7063","5":"7063","creation_date":"1178251290","6":"1178251290"},{"0":"1362","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"nothing extra","3":"nothing extra","package":"last_modified.vim","4":"last_modified.vim","src_id":"4865","5":"4865","creation_date":"1133824722","6":"1133824722"}]},"1361":{"script_id":"1361","0":"1361","script_name":"HP-41 file type plugin","1":"HP-41 file type plugin","script_type":"ftplugin","2":"ftplugin","summary":"Makes it easier to write HP-41 calculator programs in VIM","3":"Makes it easier to write HP-41 calculator programs in VIM","description":"This ftplugin has the following features:\r\n\r\nAuto-line-numbering: Upon pressing <CR> after a line, the next line has the correct line number. It even renumbers the whole file automatically. So, if you add new lines in the middle of a program, it renumbers the whole file. If you delete a line, just hit Enter to renumber the file (either in Normal or Insert mode)\r\n\r\nAlso, abbreviations of usual commands:\r\niab av AVIEW\r\niab ar ARCL\r\niab as ASTO\r\niab en ENTER\r\niab gt GTO\r\niab ge GETREC\r\niab lb LBL\r\niab pr PROMPT\r\niab sa SAVEREC\r\niab st STO\r\niab rc RCL\r\niab vi VIEW\r\niab xe XEQ\r\niab <> X<>Y\r\niab . STOP\r\n\r\nThere is a matching syntax file here:\r\nhttp:\/\/vim.sourceforge.net\/scripts\/script.php?script_id=1360\r\n","4":"This ftplugin has the following features:\r\n\r\nAuto-line-numbering: Upon pressing <CR> after a line, the next line has the correct line number. It even renumbers the whole file automatically. So, if you add new lines in the middle of a program, it renumbers the whole file. If you delete a line, just hit Enter to renumber the file (either in Normal or Insert mode)\r\n\r\nAlso, abbreviations of usual commands:\r\niab av AVIEW\r\niab ar ARCL\r\niab as ASTO\r\niab en ENTER\r\niab gt GTO\r\niab ge GETREC\r\niab lb LBL\r\niab pr PROMPT\r\niab sa SAVEREC\r\niab st STO\r\niab rc RCL\r\niab vi VIEW\r\niab xe XEQ\r\niab <> X<>Y\r\niab . STOP\r\n\r\nThere is a matching syntax file here:\r\nhttp:\/\/vim.sourceforge.net\/scripts\/script.php?script_id=1360\r\n","install_details":"Drop the hp41.vim syntax file into your .vim\/ftplugin\/ directory and register the file globally or add to your .vimrc file:\r\n\r\nautocmd BufRead,BufNewFile *.41 :source ~\/.vim\/ftplugin\/hp41.vim\r\n\r\nand you are ready for easy HP-41 program writing.","5":"Drop the hp41.vim syntax file into your .vim\/ftplugin\/ directory and register the file globally or add to your .vimrc file:\r\n\r\nautocmd BufRead,BufNewFile *.41 :source ~\/.vim\/ftplugin\/hp41.vim\r\n\r\nand you are ready for easy HP-41 program writing.","first_name":"Geir","6":"Geir","last_name":"Isene","7":"Isene","releases":[{"0":"1361","vim_version":"7.0","1":"7.0","script_version":"0.9","2":"0.9","version_comment":"Various improvements :-)","3":"Various improvements :-)","package":"hp41.vim","4":"hp41.vim","src_id":"25847","5":"25847","creation_date":"1519728042","6":"1519728042"},{"0":"1361","vim_version":"7.0","1":"7.0","script_version":"0.8.3","2":"0.8.3","version_comment":"Minor fixes.","3":"Minor fixes.","package":"hp41.vim","4":"hp41.vim","src_id":"17397","5":"17397","creation_date":"1328481589","6":"1328481589"},{"0":"1361","vim_version":"5.7","1":"5.7","script_version":"0.8.1","2":"0.8.1","version_comment":"Minor but important bug fix","3":"Minor but important bug fix","package":"hp41.vim","4":"hp41.vim","src_id":"14298","5":"14298","creation_date":"1290087508","6":"1290087508"},{"0":"1361","vim_version":"5.7","1":"5.7","script_version":"0.8","2":"0.8","version_comment":"Changed short form of commands to abbreviations (quicker and more sensible). Changed format to conform with Raw file format.","3":"Changed short form of commands to abbreviations (quicker and more sensible). Changed format to conform with Raw file format.","package":"hp41.vim","4":"hp41.vim","src_id":"14295","5":"14295","creation_date":"1290073126","6":"1290073126"},{"0":"1361","vim_version":"6.0","1":"6.0","script_version":"0.6","2":"0.6","version_comment":"Finally fixed the renumbering bug that rendered the plugin useless with large FOCAL programs. It's now very fast. Thanks to Dasn for the fix.","3":"Finally fixed the renumbering bug that rendered the plugin useless with large FOCAL programs. It's now very fast. Thanks to Dasn for the fix.","package":"hp41.vim","4":"hp41.vim","src_id":"10884","5":"10884","creation_date":"1245576403","6":"1245576403"},{"0":"1361","vim_version":"6.0","1":"6.0","script_version":"0.4","2":"0.4","version_comment":"New command <M-W> for generating .RAW files. Made the ftplugin file conform to the syntax file where Alpha is enclosed in double quotes (\"). Other minor changes.","3":"New command <M-W> for generating .RAW files. Made the ftplugin file conform to the syntax file where Alpha is enclosed in double quotes (\"). Other minor changes.","package":"hp41.vim","4":"hp41.vim","src_id":"4877","5":"4877","creation_date":"1134198019","6":"1134198019"},{"0":"1361","vim_version":"6.0","1":"6.0","script_version":"0.2","2":"0.2","version_comment":"Added <M-l> (lower case L) for alpha label.","3":"Added <M-l> (lower case L) for alpha label.","package":"hp41.vim","4":"hp41.vim","src_id":"4626","5":"4626","creation_date":"1127651202","6":"1127651202"},{"0":"1361","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"hp41.vim","4":"hp41.vim","src_id":"4602","5":"4602","creation_date":"1127217255","6":"1127217255"}]},"1360":{"script_id":"1360","0":"1360","script_name":"HP-41 syntax file","1":"HP-41 syntax file","script_type":"syntax","2":"syntax","summary":"Syntax highlighting for HP-41 calculator programs","3":"Syntax highlighting for HP-41 calculator programs","description":"The HP-41 syntax highlighting goes well with the HP-41 file type plugin to facilitate easy writing of HP-41 programs in VIM.\r\n\r\nThere is a matching file type plugin here:\r\nhttp:\/\/vim.sourceforge.net\/scripts\/edit_script.php?script_id=1361","4":"The HP-41 syntax highlighting goes well with the HP-41 file type plugin to facilitate easy writing of HP-41 programs in VIM.\r\n\r\nThere is a matching file type plugin here:\r\nhttp:\/\/vim.sourceforge.net\/scripts\/edit_script.php?script_id=1361","install_details":"Drop the hp41.vim syntax file into your .vim\/syntax\/ directory and register the file globally or add to your .vimrc file:\r\n\r\nautocmd BufRead,BufNewFile *.41 :source ~\/.vim\/syntax\/hp41.vim\r\n\r\nThen all files with the .41 extesion will be highlighted appropriately.","5":"Drop the hp41.vim syntax file into your .vim\/syntax\/ directory and register the file globally or add to your .vimrc file:\r\n\r\nautocmd BufRead,BufNewFile *.41 :source ~\/.vim\/syntax\/hp41.vim\r\n\r\nThen all files with the .41 extesion will be highlighted appropriately.","first_name":"Geir","6":"Geir","last_name":"Isene","7":"Isene","releases":[{"0":"1360","vim_version":"7.0","1":"7.0","script_version":"0.9","2":"0.9","version_comment":"Various improvements :-)","3":"Various improvements :-)","package":"hp41.vim","4":"hp41.vim","src_id":"25846","5":"25846","creation_date":"1519727910","6":"1519727910"},{"0":"1360","vim_version":"7.0","1":"7.0","script_version":"0.8","2":"0.8","version_comment":"Cleanup glitches in highlighting Alpha entries. Conditionals are better highlighted (as Comment)","3":"Cleanup glitches in highlighting Alpha entries. Conditionals are better highlighted (as Comment)","package":"hp41.vim","4":"hp41.vim","src_id":"17398","5":"17398","creation_date":"1328481687","6":"1328481687"},{"0":"1360","vim_version":"5.7","1":"5.7","script_version":"0.7","2":"0.7","version_comment":"Conditionals are now highlighted (as \"Function\")","3":"Conditionals are now highlighted (as \"Function\")","package":"hp41.vim","4":"hp41.vim","src_id":"14301","5":"14301","creation_date":"1290099344","6":"1290099344"},{"0":"1360","vim_version":"5.7","1":"5.7","script_version":"0.6","2":"0.6","version_comment":"Changed coloring. Added highlighting of END. Changed highlighting of LBL to fit with Raw format.","3":"Changed coloring. Added highlighting of END. Changed highlighting of LBL to fit with Raw format.","package":"hp41.vim","4":"hp41.vim","src_id":"14294","5":"14294","creation_date":"1290072560","6":"1290072560"},{"0":"1360","vim_version":"6.0","1":"6.0","script_version":"0.4","2":"0.4","version_comment":"Changed syntax for alpha from a single quote (') to alpha being enclosed in double quotes (\") to conform to the new ftplugin file that makes it easier to genereate .RAW files.","3":"Changed syntax for alpha from a single quote (') to alpha being enclosed in double quotes (\") to conform to the new ftplugin file that makes it easier to genereate .RAW files.","package":"hp41.vim","4":"hp41.vim","src_id":"4876","5":"4876","creation_date":"1134197712","6":"1134197712"},{"0":"1360","vim_version":"6.0","1":"6.0","script_version":"0.2","2":"0.2","version_comment":"Added correct syntax highlighting for alpha labels.","3":"Added correct syntax highlighting for alpha labels.","package":"hp41.vim","4":"hp41.vim","src_id":"4625","5":"4625","creation_date":"1127650935","6":"1127650935"},{"0":"1360","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"hp41.vim","4":"hp41.vim","src_id":"4601","5":"4601","creation_date":"1127216329","6":"1127216329"}]},"1359":{"script_id":"1359","0":"1359","script_name":"SmartCase","1":"SmartCase","script_type":"utility","2":"utility","summary":"replacing words while keeping original lower\/uppercase style","3":"replacing words while keeping original lower\/uppercase style","description":"An example, you may want to replace any FileSize appears in your program into LastModifiedTime. Since it appears everywhere as both uppercases and lowercases, you have to write it several times:\r\n\r\n  :%s\/FileSize\/LastModifiedTime\/g      \" function names\r\n  :%s\/file_size\/last_modified_time\/g   \" variable names\r\n  :%s\/FILE_SIZE\/LAST_MODIFIED_TIME\/g   \" macros\r\n  :%s\/File size\/Last modified time\/g   \" document\/comments\r\n  ......\r\n\r\nThis script copes with the case style for you so that you need write just one command:\r\n\r\n  :%s\/file\\A\\?size\/\\=SmartCase(\"LastModifiedTime\")\/ig\r\n\r\nAn alternative way:\r\n  first search for the string:  \/\\cfile\\A\\?size\r\n  then run a command:  :%SmartCase \"LastModifiedTime\"\r\n\r\nBy the way, SmartCase can also cope with the circumstance where you want to replace the string's case style while keeping its words. For example:\r\n  FileSize => file_size\r\n  LastModifiedTime => last_modified_time\r\n  ......\r\nThis can be done with the following command:\r\n\r\n  :%s\/\\(\\u\\l\\+\\)\\{2,}\/\\=SmartCase(0,\"reference_style\")\/g\r\n\r\nTo sum up: the first argument to SmartCase is the reference words, the secend argument is the reference styles, if the second argument omitted, it's submatch(0).","4":"An example, you may want to replace any FileSize appears in your program into LastModifiedTime. Since it appears everywhere as both uppercases and lowercases, you have to write it several times:\r\n\r\n  :%s\/FileSize\/LastModifiedTime\/g      \" function names\r\n  :%s\/file_size\/last_modified_time\/g   \" variable names\r\n  :%s\/FILE_SIZE\/LAST_MODIFIED_TIME\/g   \" macros\r\n  :%s\/File size\/Last modified time\/g   \" document\/comments\r\n  ......\r\n\r\nThis script copes with the case style for you so that you need write just one command:\r\n\r\n  :%s\/file\\A\\?size\/\\=SmartCase(\"LastModifiedTime\")\/ig\r\n\r\nAn alternative way:\r\n  first search for the string:  \/\\cfile\\A\\?size\r\n  then run a command:  :%SmartCase \"LastModifiedTime\"\r\n\r\nBy the way, SmartCase can also cope with the circumstance where you want to replace the string's case style while keeping its words. For example:\r\n  FileSize => file_size\r\n  LastModifiedTime => last_modified_time\r\n  ......\r\nThis can be done with the following command:\r\n\r\n  :%s\/\\(\\u\\l\\+\\)\\{2,}\/\\=SmartCase(0,\"reference_style\")\/g\r\n\r\nTo sum up: the first argument to SmartCase is the reference words, the secend argument is the reference styles, if the second argument omitted, it's submatch(0).","install_details":"","5":"","first_name":"Yuheng","6":"Yuheng","last_name":"Xie","7":"Xie","releases":[{"0":"1359","vim_version":"6.0","1":"6.0","script_version":"1.0.3","2":"1.0.3","version_comment":"Trivial improvement: Treat numbers using last style, and will not lose numbers when replacing.","3":"Trivial improvement: Treat numbers using last style, and will not lose numbers when replacing.","package":"smartcase.vim","4":"smartcase.vim","src_id":"25211","5":"25211","creation_date":"1494921788","6":"1494921788"},{"0":"1359","vim_version":"6.0","1":"6.0","script_version":"1.0.2","2":"1.0.2","version_comment":"changed <q-args> to <args> for multiple arguments capability.\r\nchanged some usage help.","3":"changed <q-args> to <args> for multiple arguments capability.\r\nchanged some usage help.","package":"smartcase.vim","4":"smartcase.vim","src_id":"4960","5":"4960","creation_date":"1137010549","6":"1137010549"},{"0":"1359","vim_version":"6.0","1":"6.0","script_version":"1.0.1","2":"1.0.1","version_comment":"1) Added a command interface :SmartCase\r\n2) a bug fixed\r\nThank Salman Halim for the bug report and advices.","3":"1) Added a command interface :SmartCase\r\n2) a bug fixed\r\nThank Salman Halim for the bug report and advices.","package":"smartcase.vim","4":"smartcase.vim","src_id":"4603","5":"4603","creation_date":"1127248408","6":"1127248408"}]},"1358":{"script_id":"1358","0":"1358","script_name":"Cthulhian","1":"Cthulhian","script_type":"color scheme","2":"color scheme","summary":"dark color scheme based on oceandeep","3":"dark color scheme based on oceandeep","description":"This is a dark color scheme based on the OceanDeep by Tom Regner (so it is required to have OceanDeep too ;), you can get it from here: vimscript #368).\r\nI slightly modified some colors to my liking.\r\nI agree with Tom that \"console colors \/do\/ suck\", so this scheme will look nice (I hope ;)) only in gvim.","4":"This is a dark color scheme based on the OceanDeep by Tom Regner (so it is required to have OceanDeep too ;), you can get it from here: vimscript #368).\r\nI slightly modified some colors to my liking.\r\nI agree with Tom that \"console colors \/do\/ suck\", so this scheme will look nice (I hope ;)) only in gvim.","install_details":"Just download both this scheme and OceanDeep one, and drop them both to $VIMRUNTIME\/colors\/ or $HOME\/.vim\/colors\/, then use :colorscheme cthulhian (if you like the scheme, you can add it to your .vimrc file ;))","5":"Just download both this scheme and OceanDeep one, and drop them both to $VIMRUNTIME\/colors\/ or $HOME\/.vim\/colors\/, then use :colorscheme cthulhian (if you like the scheme, you can add it to your .vimrc file ;))","first_name":"Eugene","6":"Eugene","last_name":"Mindrov","7":"Mindrov","releases":[{"0":"1358","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"cthulhian.vim","4":"cthulhian.vim","src_id":"4599","5":"4599","creation_date":"1127179042","6":"1127179042"}]},"1357":{"script_id":"1357","0":"1357","script_name":"larlet.vim","1":"larlet.vim","script_type":"game","2":"game","summary":"Type large letters in Insert mode","3":"Type large letters in Insert mode","description":"Larlet.vim provides an enhanced Insert mode: It allows you to type larger symbols, i.e. symbols composed of several characters.  This is rather fun than a utility.\r\n\r\nIf you're looking for a real utility, you might better use Unix' banner or surf to http:\/\/www.figlet.org\/\r\n\r\nTo toggle Larlet mode press F8 in Insert mode or Normal mode.  This maps one key per symbol.  Currently, the following keys are mapped:\r\n\r\n    abcdefghijklmnopqrstuvwxyz.,;!?=+-*:'`#()[]{}^~%$&0123456789\/\\\"_@<>|EL\r\n\r\nCase is not distinguished, only lower letter keys get mapped.  The upper keys are free to map special symbols (e.g. E - euro symbol, L - lambda).  The mappings are per buffer, thus there should be no inference with the rest of the session (except the globally set 'listchars' option reminds you to not use hard tabs).\r\n\r\nv0.04: An alternative key for toggling can be mapped this way:\r\n    :nmap <buffer> <F8> <plug>Larlet_ToggleKeymap\r\n    :imap <buffer> <F8> <c-o><plug>Larlet_ToggleKeymap\r\n\r\nEditing possibilities are - of course - limited. Symbols will always be appended at the end of a d-line [1].  i_Space adds d-spaces, i_Enter creates d-newlines.  i_Backspace deletes symbols from the end of a d-line, by looking for a d-space backwards.\r\n\r\nSymbol size is fixed to 2 lines x 5 columns.  Symbols are arranged tightly in the text, thus \"type-setting\" is not monospace.\r\n\r\n(v0.10 only) A menu \"Larlet\" will be installed for setting some options. [2]\r\n(v0.04) Letter and word spacing can be changed with :SpaceSet\r\n\r\n(v0.10 only)\r\n'fileformat' of the script is dos, if you're on unix you have to convert it.  Ok, this script is not written in a very clean manner, make sure to use it in an extra vim session.\r\n\r\nExample:\r\n.  \/  \/|  \/\u00c2\u00af) \/  \/\u00c2\u00af\u00c2\u00af -\/-  | \/ \/ \/|\/)\r\n. \/_ \/\u00c2\u00af| \/\u00c2\u00af\\ \/_ \/_\u00c2\u00af  \/  o |\/ \/ \/  \/\r\n(this looks like crap, you'll need a monospace font for viewing)\r\n\r\n----------\r\n[1] As symbols need two buffer lines of text, some above terms get a \"d\" prepended for \"double\"\r\n[2] Note: v0.10 is a typo, it should be v0.01\r\n","4":"Larlet.vim provides an enhanced Insert mode: It allows you to type larger symbols, i.e. symbols composed of several characters.  This is rather fun than a utility.\r\n\r\nIf you're looking for a real utility, you might better use Unix' banner or surf to http:\/\/www.figlet.org\/\r\n\r\nTo toggle Larlet mode press F8 in Insert mode or Normal mode.  This maps one key per symbol.  Currently, the following keys are mapped:\r\n\r\n    abcdefghijklmnopqrstuvwxyz.,;!?=+-*:'`#()[]{}^~%$&0123456789\/\\\"_@<>|EL\r\n\r\nCase is not distinguished, only lower letter keys get mapped.  The upper keys are free to map special symbols (e.g. E - euro symbol, L - lambda).  The mappings are per buffer, thus there should be no inference with the rest of the session (except the globally set 'listchars' option reminds you to not use hard tabs).\r\n\r\nv0.04: An alternative key for toggling can be mapped this way:\r\n    :nmap <buffer> <F8> <plug>Larlet_ToggleKeymap\r\n    :imap <buffer> <F8> <c-o><plug>Larlet_ToggleKeymap\r\n\r\nEditing possibilities are - of course - limited. Symbols will always be appended at the end of a d-line [1].  i_Space adds d-spaces, i_Enter creates d-newlines.  i_Backspace deletes symbols from the end of a d-line, by looking for a d-space backwards.\r\n\r\nSymbol size is fixed to 2 lines x 5 columns.  Symbols are arranged tightly in the text, thus \"type-setting\" is not monospace.\r\n\r\n(v0.10 only) A menu \"Larlet\" will be installed for setting some options. [2]\r\n(v0.04) Letter and word spacing can be changed with :SpaceSet\r\n\r\n(v0.10 only)\r\n'fileformat' of the script is dos, if you're on unix you have to convert it.  Ok, this script is not written in a very clean manner, make sure to use it in an extra vim session.\r\n\r\nExample:\r\n.  \/  \/|  \/\u00c2\u00af) \/  \/\u00c2\u00af\u00c2\u00af -\/-  | \/ \/ \/|\/)\r\n. \/_ \/\u00c2\u00af| \/\u00c2\u00af\\ \/_ \/_\u00c2\u00af  \/  o |\/ \/ \/  \/\r\n(this looks like crap, you'll need a monospace font for viewing)\r\n\r\n----------\r\n[1] As symbols need two buffer lines of text, some above terms get a \"d\" prepended for \"double\"\r\n[2] Note: v0.10 is a typo, it should be v0.01\r\n","install_details":"Set encoding to latin1 (already the default for many people):\r\n    :set enc=latin1\r\nOther encodings may also work, but they cannot be multi-byte and probably require the +iconv feature for conversion (because larlet uses some chars above 127).\r\n\r\n    :source larlet.vim\r\nfor current buffer\r\n\r\n2007 Nov 26","5":"Set encoding to latin1 (already the default for many people):\r\n    :set enc=latin1\r\nOther encodings may also work, but they cannot be multi-byte and probably require the +iconv feature for conversion (because larlet uses some chars above 127).\r\n\r\n    :source larlet.vim\r\nfor current buffer\r\n\r\n2007 Nov 26","first_name":"Andy","6":"Andy","last_name":"Wokula","7":"Wokula","releases":[{"0":"1357","vim_version":"6.0","1":"6.0","script_version":"0.04","2":"0.04","version_comment":"made script less intrusive, minor new features, dropped menu, ff=unix, nicer symbols (and umlauts removed)","3":"made script less intrusive, minor new features, dropped menu, ff=unix, nicer symbols (and umlauts removed)","package":"larlet.vim","4":"larlet.vim","src_id":"7537","5":"7537","creation_date":"1187675744","6":"1187675744"},{"0":"1357","vim_version":"6.0","1":"6.0","script_version":"0.10","2":"0.10","version_comment":"Initial upload","3":"Initial upload","package":"larlet.vim","4":"larlet.vim","src_id":"4593","5":"4593","creation_date":"1127031369","6":"1127031369"}]},"1356":{"script_id":"1356","0":"1356","script_name":"eraseSubword","1":"eraseSubword","script_type":"utility","2":"utility","summary":"Erase one subword from a camel case word or from a _ delimited word","3":"Erase one subword from a camel case word or from a _ delimited word","description":"Makes <C-H> in insert mode delete one subword from a camel case word or one _ delimited subword before the cursor.\r\n\r\nFor example, the following word is typed in an editor:\r\n\r\none_twoThree\r\n\r\nFirst <C-H> will delete \"Three\", second - \"two\" and the third will completely erase the word.\r\n\r\nDefault mapping could be changed by setting g:EraseSubword_insertMap to the desired key.  Setting s:EraseSubword_insertMap to an empty string would remove default mapping at all.  Mapping could be changed later (for example in file type plugin or in some auto commands) using EraseSubword_setInsertMap function that takes one argument - new value for the g:EraseSubword_insertMap.  Empty value would disable plugin and any other value would add new mapping (old mapping would be removed).\r\n\r\nThere is also a possibility to use buffer local mapping.  Than you probably want to set g:EraseSubword_insertMap to an empty string (so that there would be no global mapping) and then use EraseSubword_setlocalInsertMap in FileType auto command or BufNew, BufCreate and a like to set buffer local mapping.  EraseSubword_setlocalInsertMap uses same syntax as EraseSubword_insertMap - one argument that is a desired mapping or empty string to remove existing mapping.","4":"Makes <C-H> in insert mode delete one subword from a camel case word or one _ delimited subword before the cursor.\r\n\r\nFor example, the following word is typed in an editor:\r\n\r\none_twoThree\r\n\r\nFirst <C-H> will delete \"Three\", second - \"two\" and the third will completely erase the word.\r\n\r\nDefault mapping could be changed by setting g:EraseSubword_insertMap to the desired key.  Setting s:EraseSubword_insertMap to an empty string would remove default mapping at all.  Mapping could be changed later (for example in file type plugin or in some auto commands) using EraseSubword_setInsertMap function that takes one argument - new value for the g:EraseSubword_insertMap.  Empty value would disable plugin and any other value would add new mapping (old mapping would be removed).\r\n\r\nThere is also a possibility to use buffer local mapping.  Than you probably want to set g:EraseSubword_insertMap to an empty string (so that there would be no global mapping) and then use EraseSubword_setlocalInsertMap in FileType auto command or BufNew, BufCreate and a like to set buffer local mapping.  EraseSubword_setlocalInsertMap uses same syntax as EraseSubword_insertMap - one argument that is a desired mapping or empty string to remove existing mapping.","install_details":"Copy eraseSubword.vim to your ~\/vimfiles\/plugin directory.","5":"Copy eraseSubword.vim to your ~\/vimfiles\/plugin directory.","first_name":"Ilya","6":"Ilya","last_name":"Bobir","7":"Bobir","releases":[{"0":"1356","vim_version":"6.0","1":"6.0","script_version":"4","2":"4","version_comment":"+ Mapping can be changes and buffer local mapping can be set\r\n* 'ignorecase' was not properly handled\r\n* Sometimes deleted to mutch","3":"+ Mapping can be changes and buffer local mapping can be set\r\n* 'ignorecase' was not properly handled\r\n* Sometimes deleted to mutch","package":"eraseSubword.vim","4":"eraseSubword.vim","src_id":"4606","5":"4606","creation_date":"1127323198","6":"1127323198"}]},"1355":{"script_id":"1355","0":"1355","script_name":"PDV - phpDocumentor for Vim","1":"PDV - phpDocumentor for Vim","script_type":"utility","2":"utility","summary":"Provides really comfortable generation of phpDocumentor doc blocks for PHP4 & 5.","3":"Provides really comfortable generation of phpDocumentor doc blocks for PHP4 & 5.","description":"PDV (phpDocumentor for Vim)\r\n========================\r\n\r\nVersion: 1.0.0\r\n\r\nCopyright 2005 by Tobias Schlitt <toby@php.net>\r\nInspired by phpDoc script for Vim by Vidyut Luther (http:\/\/www.phpcult.com\/).\r\n\r\nProvided under the GPL (http:\/\/www.gnu.org\/copyleft\/gpl.html).\r\n\r\nThis script provides functions to generate phpDocumentor conform\r\ndocumentation blocks for your PHP code. The script currently\r\ndocuments:\r\n\r\n- Classes\r\n- Methods\/Functions\r\n- Attributes\r\n\r\nAll of those supporting all PHP 4 and 5 syntax elements.\r\n\r\nBeside that it allows you to define default values for phpDocumentor tags\r\nlike @version (I use $id$ here), @author, @license and so on.\r\n\r\nFor function\/method parameters and attributes, the script tries to guess the\r\ntype as good as possible from PHP5 type hints or default values (array, bool,\r\nint, string...).\r\n\r\nYou can use this script by mapping the function PhpDoc() to any\r\nkey combination. Hit this on the line where the element to document\r\nresides and the doc block will be created directly above that line.\r\n\r\nChangelog\r\n=========\r\n\r\nVersion 1.0.0\r\n-------------------\r\n\r\n* Created the initial version of this script while playing around with VIM\r\n   scripting the first time and trying to fix Vidyut's solution, which\r\n   resulted in a complete rewrite.","4":"PDV (phpDocumentor for Vim)\r\n========================\r\n\r\nVersion: 1.0.0\r\n\r\nCopyright 2005 by Tobias Schlitt <toby@php.net>\r\nInspired by phpDoc script for Vim by Vidyut Luther (http:\/\/www.phpcult.com\/).\r\n\r\nProvided under the GPL (http:\/\/www.gnu.org\/copyleft\/gpl.html).\r\n\r\nThis script provides functions to generate phpDocumentor conform\r\ndocumentation blocks for your PHP code. The script currently\r\ndocuments:\r\n\r\n- Classes\r\n- Methods\/Functions\r\n- Attributes\r\n\r\nAll of those supporting all PHP 4 and 5 syntax elements.\r\n\r\nBeside that it allows you to define default values for phpDocumentor tags\r\nlike @version (I use $id$ here), @author, @license and so on.\r\n\r\nFor function\/method parameters and attributes, the script tries to guess the\r\ntype as good as possible from PHP5 type hints or default values (array, bool,\r\nint, string...).\r\n\r\nYou can use this script by mapping the function PhpDoc() to any\r\nkey combination. Hit this on the line where the element to document\r\nresides and the doc block will be created directly above that line.\r\n\r\nChangelog\r\n=========\r\n\r\nVersion 1.0.0\r\n-------------------\r\n\r\n* Created the initial version of this script while playing around with VIM\r\n   scripting the first time and trying to fix Vidyut's solution, which\r\n   resulted in a complete rewrite.","install_details":"Installation\r\n=========\r\n\r\nFor example include into your .vimrc:\r\n\r\nsource ~\/.vim\/php-doc.vim\r\ninoremap <C-P> <ESC>:call PhpDocSingle()<CR>i\r\nnnoremap <C-P> :call PhpDocSingle()<CR>\r\nvnoremap <C-P> :call PhpDocRange()<CR>\r\n\r\nThis includes the script and maps the combination <ctrl>+p\r\nto the doc functions.","5":"Installation\r\n=========\r\n\r\nFor example include into your .vimrc:\r\n\r\nsource ~\/.vim\/php-doc.vim\r\ninoremap <C-P> <ESC>:call PhpDocSingle()<CR>i\r\nnnoremap <C-P> :call PhpDocSingle()<CR>\r\nvnoremap <C-P> :call PhpDocRange()<CR>\r\n\r\nThis includes the script and maps the combination <ctrl>+p\r\nto the doc functions.","first_name":"Tobias","6":"Tobias","last_name":"Schlitt","7":"Schlitt","releases":[{"0":"1355","vim_version":"6.0","1":"6.0","script_version":"1.0.1","2":"1.0.1","version_comment":"- Fixed commenting of tab indented code.\r\n- Fixed some smaller parsing bugs.\r\n- Fixed bug with call-by-reference parameters.\r\n- ATTENTION: This version contains already some code for version 1.1.0, which does not work by now!","3":"- Fixed commenting of tab indented code.\r\n- Fixed some smaller parsing bugs.\r\n- Fixed bug with call-by-reference parameters.\r\n- ATTENTION: This version contains already some code for version 1.1.0, which does not work by now!","package":"php-doc.vim","4":"php-doc.vim","src_id":"4666","5":"4666","creation_date":"1129033887","6":"1129033887"},{"0":"1355","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"php-doc.vim","4":"php-doc.vim","src_id":"4584","5":"4584","creation_date":"1126717959","6":"1126717959"}]},"1354":{"script_id":"1354","0":"1354","script_name":"Night Vision Colorscheme","1":"Night Vision Colorscheme","script_type":"color scheme","2":"color scheme","summary":"Programming through night vision googles :)","3":"Programming through night vision googles :)","description":"A night vision color scheme - dark green background (GUI only)\r\n\r\n\r\n","4":"A night vision color scheme - dark green background (GUI only)\r\n\r\n\r\n","install_details":"Copy the night_vision.vim file to your \/colors directory\r\nFrom vim type :colo night_vision","5":"Copy the night_vision.vim file to your \/colors directory\r\nFrom vim type :colo night_vision","first_name":"Narayanan","6":"Narayanan","last_name":"Iyer","7":"Iyer","releases":[{"0":"1354","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"night_vision.vim","4":"night_vision.vim","src_id":"4579","5":"4579","creation_date":"1126663951","6":"1126663951"}]},"1353":{"script_id":"1353","0":"1353","script_name":"syntax\/ada.vim","1":"syntax\/ada.vim","script_type":"syntax","2":"syntax","summary":"Syntax Plugin for Ada (inactive, replaced by vimscript#1609)","3":"Syntax Plugin for Ada (inactive, replaced by vimscript#1609)","description":"This plugin is superseded by vimscript#1609 and https:\/\/github.com\/krischik\/Ad-Bundle.","4":"This plugin is superseded by vimscript#1609 and https:\/\/github.com\/krischik\/Ad-Bundle.","install_details":"Install from https:\/\/github.com\/krischik\/Ad-Bundle using dein (https:\/\/github.com\/Shougo\/dein.vim) or similar:\r\n\r\ncall dein#begin('\/Users\/martin\/vimfiles\/bundles')\r\ncall dein#add('krischik\/Ada-Bundle')\r\ncall dein#end()\r\ncall dein#install()","5":"Install from https:\/\/github.com\/krischik\/Ad-Bundle using dein (https:\/\/github.com\/Shougo\/dein.vim) or similar:\r\n\r\ncall dein#begin('\/Users\/martin\/vimfiles\/bundles')\r\ncall dein#add('krischik\/Ada-Bundle')\r\ncall dein#end()\r\ncall dein#install()","first_name":"Martin","6":"Martin","last_name":"Krischik","7":"Krischik","releases":[{"0":"1353","vim_version":"7.0","1":"7.0","script_version":"2.1","2":"2.1","version_comment":"Some correction regarding the use of attributes. Correct use of the ' is a bit tricky.","3":"Some correction regarding the use of attributes. Correct use of the ' is a bit tricky.","package":"ada.vim","4":"ada.vim","src_id":"5779","5":"5779","creation_date":"1148715111","6":"1148715111"},{"0":"1353","vim_version":"7.0","1":"7.0","script_version":"2.0","2":"2.0","version_comment":"New coordinated release for all Ada plugins. Binary releases which are patched with all Ada plugins is available from the GNU Ada project [1]\r\n\r\n[1] http:\/\/gnuada.sourceforge.net","3":"New coordinated release for all Ada plugins. Binary releases which are patched with all Ada plugins is available from the GNU Ada project [1]\r\n\r\n[1] http:\/\/gnuada.sourceforge.net","package":"ada.vim","4":"ada.vim","src_id":"5759","5":"5759","creation_date":"1148548405","6":"1148548405"},{"0":"1353","vim_version":"6.0","1":"6.0","script_version":"1.1","2":"1.1","version_comment":"More features and now with Ada 2005 support.","3":"More features and now with Ada 2005 support.","package":"ada.vim","4":"ada.vim","src_id":"4671","5":"4671","creation_date":"1129188711","6":"1129188711"},{"0":"1353","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"ada.vim","4":"ada.vim","src_id":"4575","5":"4575","creation_date":"1126598229","6":"1126598229"}]},"1352":{"script_id":"1352","0":"1352","script_name":"Modelines Bundle","1":"Modelines Bundle","script_type":"utility","2":"utility","summary":"Insert Modelines from current settings","3":"Insert Modelines from current settings","description":"Inserts three modelines with the currently active filetype, tabulator and spelling settings.\r\n\r\nCan be used for:\r\n\r\n- a quick overview of the file settings (like is the file dos or unix format).\r\n- to set the file setting (just change the settings which are wrong).\r\n- to make sure the file settings stay put when the file is saved and loaded.\r\n\r\nCan be easily extended for more settings - just as you want it.\r\n\r\n| Vim-Script  || https:\/\/www.vim.org\/scripts\/script.php?script_id=1352\r\n| Source      || https:\/\/github.com\/krischik\/vim-modelines\r\n| Wiki\t      || https:\/\/github.com\/krischik\/vim-modelines\/wiki\r\n| Releases    || https:\/\/github.com\/krischik\/vim-modelines\/releases \r\n| Issues      || https:\/\/github.com\/krischik\/vim-modelines\/issues \r\n| Discussions || https:\/\/github.com\/krischik\/vim-modelines\/discussions \r\n","4":"Inserts three modelines with the currently active filetype, tabulator and spelling settings.\r\n\r\nCan be used for:\r\n\r\n- a quick overview of the file settings (like is the file dos or unix format).\r\n- to set the file setting (just change the settings which are wrong).\r\n- to make sure the file settings stay put when the file is saved and loaded.\r\n\r\nCan be easily extended for more settings - just as you want it.\r\n\r\n| Vim-Script  || https:\/\/www.vim.org\/scripts\/script.php?script_id=1352\r\n| Source      || https:\/\/github.com\/krischik\/vim-modelines\r\n| Wiki\t      || https:\/\/github.com\/krischik\/vim-modelines\/wiki\r\n| Releases    || https:\/\/github.com\/krischik\/vim-modelines\/releases \r\n| Issues      || https:\/\/github.com\/krischik\/vim-modelines\/issues \r\n| Discussions || https:\/\/github.com\/krischik\/vim-modelines\/discussions \r\n","install_details":"Install from https:\/\/github.com\/krischik\/vim-modelines using dein (https:\/\/github.com\/Shougo\/dein.vim) or similar:\r\n\r\n{{code|lang=vim|\r\ncall dein#begin('$HOME\/vimfiles\/bundles')\r\ncall dein#add('krischik\/vim-modelines')\r\ncall dein#end()\r\ncall dein#install()\r\n}}","5":"Install from https:\/\/github.com\/krischik\/vim-modelines using dein (https:\/\/github.com\/Shougo\/dein.vim) or similar:\r\n\r\n{{code|lang=vim|\r\ncall dein#begin('$HOME\/vimfiles\/bundles')\r\ncall dein#add('krischik\/vim-modelines')\r\ncall dein#end()\r\ncall dein#install()\r\n}}","first_name":"Martin","6":"Martin","last_name":"Krischik","7":"Krischik","releases":[{"0":"1352","vim_version":"7.0","1":"7.0","script_version":"3.0.0","2":"3.0.0","version_comment":"See https:\/\/github.com\/krischik\/Modelines-Bundle\/releases\/tag\/v_3.0.0","3":"See https:\/\/github.com\/krischik\/Modelines-Bundle\/releases\/tag\/v_3.0.0","package":"Modelines-Bundle-v_3.0.0.zip","4":"Modelines-Bundle-v_3.0.0.zip","src_id":"28182","5":"28182","creation_date":"1663466291","6":"1663466291"},{"0":"1352","vim_version":"7.0","1":"7.0","script_version":"2.0","2":"2.0","version_comment":"Now as a bundle. The new version will use autoload to conserve memory and start-up time.\r\n\r\nNew features: Uses NERD_Commenter when available, fallback to &commentstring when not.","3":"Now as a bundle. The new version will use autoload to conserve memory and start-up time.\r\n\r\nNew features: Uses NERD_Commenter when available, fallback to &commentstring when not.","package":"modelines-2.0.vba","4":"modelines-2.0.vba","src_id":"7683","5":"7683","creation_date":"1189996010","6":"1189996010"},{"0":"1352","vim_version":"7.0","1":"7.0","script_version":"1.4","2":"1.4","version_comment":"When integrating the Ada Mode into the standart runtime Bram enlightent me on which modeline settings are usefull and which are not. The result is this fixed version.\r\n\r\nIt also uses not the \"vim: set ... :\" syntax so it will work fine with languages using something like \"\/* *\/\".","3":"When integrating the Ada Mode into the standart runtime Bram enlightent me on which modeline settings are usefull and which are not. The result is this fixed version.\r\n\r\nIt also uses not the \"vim: set ... :\" syntax so it will work fine with languages using something like \"\/* *\/\".","package":"modelines.vim","4":"modelines.vim","src_id":"6437","5":"6437","creation_date":"1163815245","6":"1163815245"},{"0":"1352","vim_version":"6.0","1":"6.0","script_version":"1.1","2":"1.1","version_comment":"This version does not need the NERD Commenter any more. It used the &commentstring instead.","3":"This version does not need the NERD Commenter any more. It used the &commentstring instead.","package":"modelines.vim","4":"modelines.vim","src_id":"5307","5":"5307","creation_date":"1140675458","6":"1140675458"},{"0":"1352","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"modelines.vim","4":"modelines.vim","src_id":"4574","5":"4574","creation_date":"1126591394","6":"1126591394"}]},"1351":{"script_id":"1351","0":"1351","script_name":"Mud","1":"Mud","script_type":"color scheme","2":"color scheme","summary":"Dark brown colorscheme with beutiful highlighing","3":"Dark brown colorscheme with beutiful highlighing","description":"This is a night mode colorscheme for GUI version.\r\nDark brown colorscheme with beutiful highlighing and easy to distinguish colors for different highlight groups. Very easy on the eyes and especially suited if you are the sort who burn midnight oil. suited for low light conditions !","4":"This is a night mode colorscheme for GUI version.\r\nDark brown colorscheme with beutiful highlighing and easy to distinguish colors for different highlight groups. Very easy on the eyes and especially suited if you are the sort who burn midnight oil. suited for low light conditions !","install_details":"Just copy mud.vim  to your  colors\/directory","5":"Just copy mud.vim  to your  colors\/directory","first_name":"Narayanan","6":"Narayanan","last_name":"Iyer","7":"Iyer","releases":[{"0":"1351","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"mud.vim","4":"mud.vim","src_id":"4570","5":"4570","creation_date":"1126574268","6":"1126574268"}]},"1350":{"script_id":"1350","0":"1350","script_name":"Mud","1":"Mud","script_type":"color scheme","2":"color scheme","summary":"Dark brown colorscheme with beutiful highlighing","3":"Dark brown colorscheme with beutiful highlighing","description":"This is a night mode colorscheme for GUI version.\r\nDark brown colorscheme with beutiful highlighing and easy to distinguish colors for different highlight groups. Very easy on the eyes and especially suited if you are the sort who burn midnight oil. suited for low light conditions !","4":"This is a night mode colorscheme for GUI version.\r\nDark brown colorscheme with beutiful highlighing and easy to distinguish colors for different highlight groups. Very easy on the eyes and especially suited if you are the sort who burn midnight oil. suited for low light conditions !","install_details":"Just copy mud.vim  to your  colors\/directory","5":"Just copy mud.vim  to your  colors\/directory","first_name":"Narayanan","6":"Narayanan","last_name":"Iyer","7":"Iyer","releases":[{"0":"1350","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"mud.vim","4":"mud.vim","src_id":"4569","5":"4569","creation_date":"1126574170","6":"1126574170"}]},"1349":{"script_id":"1349","0":"1349","script_name":"Colortest","1":"Colortest","script_type":"utility","2":"utility","summary":"xterm 256 color test and visual colors list","3":"xterm 256 color test and visual colors list","description":"spits out a list of all the colors IN COLOR, \r\n\r\nalso therefor functions as a test to find out whether your xterm was compiled with 256 color support to use the nice colorschemes. i have no idea what will happen to your terminal if you don't have 256 color support, but I'd imagine you'll just get a bunch of funny chars and that's about it...\r\n\r\nvery handy for writing terminal colorschemes for vim - gives you the cterm color number and the rgb values... makes it very easy and fast to port \"gui only\" colorschemes to the 256 color terminal\r\n\r\ndoesn't work with rxvt and I don't know about other terms because it uses xterm color escapes... it doesn't have the color names... it just displays each one with the color that it actually is, so you just look at it to know what color it is. if you've changed your xresources in your xdefaults file to modify the xterm colors then the RGB values won't hold true, but the actual colors and their corresponding cterm numbers will still produce whatever your xterm is set to...\r\n\r\nsupports a couple of display options... if you've got a fairly normally large\/decent size screen you'll probably want to run it with the switches:\r\n\r\ncolortest -w -s\r\n\r\nNO WARRANTY! or ANYTHING is implied... if this breaks your computer it's not my fault... you might wanna read the code first, it's not doing anything complicated though and it works for me\r\n\r\nI probably will never update or support this in the future so whoever wants it can have it... i hereby grant a full \"anything goes at any time in any way with this file\" 100% free liscense to anyone who wants to mess around with the file","4":"spits out a list of all the colors IN COLOR, \r\n\r\nalso therefor functions as a test to find out whether your xterm was compiled with 256 color support to use the nice colorschemes. i have no idea what will happen to your terminal if you don't have 256 color support, but I'd imagine you'll just get a bunch of funny chars and that's about it...\r\n\r\nvery handy for writing terminal colorschemes for vim - gives you the cterm color number and the rgb values... makes it very easy and fast to port \"gui only\" colorschemes to the 256 color terminal\r\n\r\ndoesn't work with rxvt and I don't know about other terms because it uses xterm color escapes... it doesn't have the color names... it just displays each one with the color that it actually is, so you just look at it to know what color it is. if you've changed your xresources in your xdefaults file to modify the xterm colors then the RGB values won't hold true, but the actual colors and their corresponding cterm numbers will still produce whatever your xterm is set to...\r\n\r\nsupports a couple of display options... if you've got a fairly normally large\/decent size screen you'll probably want to run it with the switches:\r\n\r\ncolortest -w -s\r\n\r\nNO WARRANTY! or ANYTHING is implied... if this breaks your computer it's not my fault... you might wanna read the code first, it's not doing anything complicated though and it works for me\r\n\r\nI probably will never update or support this in the future so whoever wants it can have it... i hereby grant a full \"anything goes at any time in any way with this file\" 100% free liscense to anyone who wants to mess around with the file","install_details":"just download it and chmod it to executable then run it like a normal script\r\n\r\n.\/colortest\r\n\r\nthat's it... put it into \/usr\/local\/bin or somewhere in your path if you really want","5":"just download it and chmod it to executable then run it like a normal script\r\n\r\n.\/colortest\r\n\r\nthat's it... put it into \/usr\/local\/bin or somewhere in your path if you really want","first_name":"Maestro","6":"Maestro","last_name":"Entheon","7":"Entheon","releases":[{"0":"1349","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"colortest","4":"colortest","src_id":"4568","5":"4568","creation_date":"1126556724","6":"1126556724"}]},"1348":{"script_id":"1348","0":"1348","script_name":"The Vim Gardener","1":"The Vim Gardener","script_type":"color scheme","2":"color scheme","summary":"Dark and colorful forrest khaki theme works with 256 color xterms","3":"Dark and colorful forrest khaki theme works with 256 color xterms","description":"  'For code surgeons and web gardeners everywhere'\r\n\r\nA nice earthy  color scheme which is easy on  the eyes. It\r\nhas  as it's  base a  dark background  monocrhomatic khaki\r\nscheme with dabs of color thrown  in here and there on the\r\nkeywords. It's gives you the feeling of looking at the sun through \r\nthe afternoon spring leaves, but all at night time :)\r\n\r\nPlus  lots of  extra config  options so  you can\r\ntweak  it to  your liking  and or  make it  more like  the\r\noriginal Guardian scheme. All the defaults are what I like\r\nbut if you want to change stuff just set the right var and\r\nit will change pretty much  immediately, you might have to\r\nmove out of and back into your buffer for it to refresh.\r\n\r\n\r\nNew Features:\r\n  256 Color XTerm Compatibility\r\n  Richer Syntax\r\n  Black Background\r\n  Functions\r\n  No Italics\r\n  Purple Booleans\r\n  Swapped Status Line Colors\r\n  Green like a garden\r\n  Other minor tweaks\r\n\r\nScreenshot:\r\n  http:\/\/entheon.com\/vim-gardener.gif\r\n","4":"  'For code surgeons and web gardeners everywhere'\r\n\r\nA nice earthy  color scheme which is easy on  the eyes. It\r\nhas  as it's  base a  dark background  monocrhomatic khaki\r\nscheme with dabs of color thrown  in here and there on the\r\nkeywords. It's gives you the feeling of looking at the sun through \r\nthe afternoon spring leaves, but all at night time :)\r\n\r\nPlus  lots of  extra config  options so  you can\r\ntweak  it to  your liking  and or  make it  more like  the\r\noriginal Guardian scheme. All the defaults are what I like\r\nbut if you want to change stuff just set the right var and\r\nit will change pretty much  immediately, you might have to\r\nmove out of and back into your buffer for it to refresh.\r\n\r\n\r\nNew Features:\r\n  256 Color XTerm Compatibility\r\n  Richer Syntax\r\n  Black Background\r\n  Functions\r\n  No Italics\r\n  Purple Booleans\r\n  Swapped Status Line Colors\r\n  Green like a garden\r\n  Other minor tweaks\r\n\r\nScreenshot:\r\n  http:\/\/entheon.com\/vim-gardener.gif\r\n","install_details":"put the gardener.vim file into your ~\/.vim\/colors\/ dir then from within vim do\r\n:colorscheme gardener\r\n\r\nif you're in the terminal and the colorscheme command doesn't work or it turns your file into black and white, then from within vim you'll need to do\r\n:set t_Co=256\r\n\r\nyou'll probably want to put that in your ~\/.vimrc\r\n\r\nyou also need 256 color support compiled into your terminal, I've tested this with both xterm and rxvt, they both work fine with default settings as long as you do :set t_Co=256 and as long as the terminal was compiled with the --enable-256-color option","5":"put the gardener.vim file into your ~\/.vim\/colors\/ dir then from within vim do\r\n:colorscheme gardener\r\n\r\nif you're in the terminal and the colorscheme command doesn't work or it turns your file into black and white, then from within vim you'll need to do\r\n:set t_Co=256\r\n\r\nyou'll probably want to put that in your ~\/.vimrc\r\n\r\nyou also need 256 color support compiled into your terminal, I've tested this with both xterm and rxvt, they both work fine with default settings as long as you do :set t_Co=256 and as long as the terminal was compiled with the --enable-256-color option","first_name":"Maestro","6":"Maestro","last_name":"Entheon","7":"Entheon","releases":[{"0":"1348","vim_version":"6.0","1":"6.0","script_version":"1.1","2":"1.1","version_comment":"this is what i've been using for the past few months and I've probably put some tweaks on it though i can't remember all of what exactly - eventually i'm going to make the gui colors identical to the terminal colors because i think the terminal actually looks better than the gui atm - that'll be version 1.2 when i do that","3":"this is what i've been using for the past few months and I've probably put some tweaks on it though i can't remember all of what exactly - eventually i'm going to make the gui colors identical to the terminal colors because i think the terminal actually looks better than the gui atm - that'll be version 1.2 when i do that","package":"gardener.vim","4":"gardener.vim","src_id":"4682","5":"4682","creation_date":"1129671935","6":"1129671935"}]},"1347":{"script_id":"1347","0":"1347","script_name":"cxxcomplete","1":"cxxcomplete","script_type":"utility","2":"utility","summary":"Tries to implement code completion.","3":"Tries to implement code completion.","description":"First, you'll need ruby support compiled in vim, and ruby bindings for gtk( ruby-gnome).\r\n\r\nWhat it can do?\r\nScans your tags file, and pops up a list of possible completions.\r\nThe completions refers to your variables, and member functions\/variables.\r\nhttp:\/\/photos1.blogger.com\/blogger\/4648\/1229\/1600\/screen11.jpg\r\n\r\nThe script that scans the tags file is based on cppcomplete.\r\n","4":"First, you'll need ruby support compiled in vim, and ruby bindings for gtk( ruby-gnome).\r\n\r\nWhat it can do?\r\nScans your tags file, and pops up a list of possible completions.\r\nThe completions refers to your variables, and member functions\/variables.\r\nhttp:\/\/photos1.blogger.com\/blogger\/4648\/1229\/1600\/screen11.jpg\r\n\r\nThe script that scans the tags file is based on cppcomplete.\r\n","install_details":"copy it into your .vim\/plugin directory.\r\n :w","5":"copy it into your .vim\/plugin directory.\r\n :w","first_name":"Marius","6":"Marius","last_name":"Groleo","7":"Groleo","releases":[{"0":"1347","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"cxxcomplete.vim","4":"cxxcomplete.vim","src_id":"4565","5":"4565","creation_date":"1126488370","6":"1126488370"}]},"1346":{"script_id":"1346","0":"1346","script_name":"VIM Email Client","1":"VIM Email Client","script_type":"utility","2":"utility","summary":"Independent Email Client for Vim","3":"Independent Email Client for Vim","description":"This email client contains two python scripts: fetch.py and send.py that handle the send&receive process, and a vim script called \"email.vim\" that handles the vim binding.\r\n\r\nsee http:\/\/www.ee.bgu.ac.il\/~elentok\/os\/vim-mail\/ for a tutorial and installation instructions.\r\n\r\n","4":"This email client contains two python scripts: fetch.py and send.py that handle the send&receive process, and a vim script called \"email.vim\" that handles the vim binding.\r\n\r\nsee http:\/\/www.ee.bgu.ac.il\/~elentok\/os\/vim-mail\/ for a tutorial and installation instructions.\r\n\r\n","install_details":"see http:\/\/www.ee.bgu.ac.il\/~elentok\/os\/vim-mail\/ ","5":"see http:\/\/www.ee.bgu.ac.il\/~elentok\/os\/vim-mail\/ ","first_name":"David","6":"David","last_name":"E","7":"E","releases":[{"0":"1346","vim_version":"6.0","1":"6.0","script_version":"0.2","2":"0.2","version_comment":"Initial upload","3":"Initial upload","package":"vim-email.zip","4":"vim-email.zip","src_id":"4563","5":"4563","creation_date":"1126325333","6":"1126325333"}]},"1345":{"script_id":"1345","0":"1345","script_name":"dmd","1":"dmd","script_type":"ftplugin","2":"ftplugin","summary":"DigitalMars D language file type plugin(syntax, fold, compiler,include search)","3":"DigitalMars D language file type plugin(syntax, fold, compiler,include search)","description":"It's a quite poor ftplugin,but it work.\r\n\r\nI permiss I will make a d language ftplugin as good as C\/C++ have.\r\nHowever, This is first step.\r\n\r\nfeathers:\r\n   syntax highlight, it's official version.\r\n   syntax fold, quick and dirty way.\r\n   include search, set environment veriable DMD to dmd home, vim can search\r\nall module under $DMD\/import for symbol under cursor.(normal [i, [I ). gf key-sequeue open the module under cursor, too\r\n   ctags support, there is a modified ctags support C\/C++\/D language.\r\n\r\ntodo:\r\n   make comment works well.\r\n   redesign syntax fold.\r\n   ","4":"It's a quite poor ftplugin,but it work.\r\n\r\nI permiss I will make a d language ftplugin as good as C\/C++ have.\r\nHowever, This is first step.\r\n\r\nfeathers:\r\n   syntax highlight, it's official version.\r\n   syntax fold, quick and dirty way.\r\n   include search, set environment veriable DMD to dmd home, vim can search\r\nall module under $DMD\/import for symbol under cursor.(normal [i, [I ). gf key-sequeue open the module under cursor, too\r\n   ctags support, there is a modified ctags support C\/C++\/D language.\r\n\r\ntodo:\r\n   make comment works well.\r\n   redesign syntax fold.\r\n   ","install_details":"put it in vimfiles or .vim\r\n\r\nfor windows(Ok, for M$ windows), ctags.exe can put in $VIMRUNTIME directory.\r\nsorry for linux binary absence. ","5":"put it in vimfiles or .vim\r\n\r\nfor windows(Ok, for M$ windows), ctags.exe can put in $VIMRUNTIME directory.\r\nsorry for linux binary absence. ","first_name":"liang","6":"liang","last_name":"huang","7":"huang","releases":[{"0":"1345","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"d-vim.zip","4":"d-vim.zip","src_id":"4562","5":"4562","creation_date":"1126248247","6":"1126248247"}]},"1344":{"script_id":"1344","0":"1344","script_name":"switchtags.vim","1":"switchtags.vim","script_type":"utility","2":"utility","summary":"Switch tags option automatically between different projects","3":"Switch tags option automatically between different projects","description":"When edit files that belong to different projects with different tags option \r\nsettings at the same time, it's annoying to switch tags option manually.\r\nThis plugin can switch tags option automatically according to the buffer's\r\nfile full name.","4":"When edit files that belong to different projects with different tags option \r\nsettings at the same time, it's annoying to switch tags option manually.\r\nThis plugin can switch tags option automatically according to the buffer's\r\nfile full name.","install_details":"copy it to $VIM\/vimfiles\/plugin or ~\/.vim\/plugin, change the %__tags\r\n variable in switchtags.vim to fit your requirement. See\r\nswitchtags.vim to get detailed information.","5":"copy it to $VIM\/vimfiles\/plugin or ~\/.vim\/plugin, change the %__tags\r\n variable in switchtags.vim to fit your requirement. See\r\nswitchtags.vim to get detailed information.","first_name":"Yubao","6":"Yubao","last_name":"Liu","7":"Liu","releases":[{"0":"1344","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"switchtags.vim","4":"switchtags.vim","src_id":"4552","5":"4552","creation_date":"1125902032","6":"1125902032"}]},"1343":{"script_id":"1343","0":"1343","script_name":"AutoTag","1":"AutoTag","script_type":"utility","2":"utility","summary":"Updates entries in a tags file automatically when saving","3":"Updates entries in a tags file automatically when saving","description":"If you use ctags to make tags files of your source, it's nice to be able to re-run ctags on a source file when you save it.\r\n\r\nHowever, using ctags -a will only change existing entries in a tags file or add new ones. It doesn't delete entries that no longer exist. Should you delete an entity from your source file that's represented by an entry in a tags file, that entry will remain after calling ctags -a.\r\n\r\nThis python function will do two things:\r\n\r\n1) It will search for a tags file starting in the directory where your source file resides and moving up a directory at a time until it either finds one or runs out of directories to try.\r\n\r\n2) Should it find a tags file, it will then delete all entries in said tags file referencing the source file you've just saved and then execute ctags -a on that source file using the relative path to the source file from the tags file.\r\n\r\nThis way, every time you save a file, your tags file will be seamlessly updated.\r\n\r\nThe master copy of this is in my github files:\r\nhttps:\/\/github.com\/craigemery\/vim-autotag","4":"If you use ctags to make tags files of your source, it's nice to be able to re-run ctags on a source file when you save it.\r\n\r\nHowever, using ctags -a will only change existing entries in a tags file or add new ones. It doesn't delete entries that no longer exist. Should you delete an entity from your source file that's represented by an entry in a tags file, that entry will remain after calling ctags -a.\r\n\r\nThis python function will do two things:\r\n\r\n1) It will search for a tags file starting in the directory where your source file resides and moving up a directory at a time until it either finds one or runs out of directories to try.\r\n\r\n2) Should it find a tags file, it will then delete all entries in said tags file referencing the source file you've just saved and then execute ctags -a on that source file using the relative path to the source file from the tags file.\r\n\r\nThis way, every time you save a file, your tags file will be seamlessly updated.\r\n\r\nThe master copy of this is in my github files:\r\nhttps:\/\/github.com\/craigemery\/vim-autotag","install_details":"Simply source the file autoTag.vim from your .vimrc file.\r\nThis utility will (obviously) only work when using vim that's been compiled with python support.","5":"Simply source the file autoTag.vim from your .vimrc file.\r\nThis utility will (obviously) only work when using vim that's been compiled with python support.","first_name":"Craig","6":"Craig","last_name":"Emery","7":"Emery","releases":[{"0":"1343","vim_version":"7.0","1":"7.0","script_version":"1.13","2":"1.13","version_comment":"Use a defaultdict for easier appending.\r\nPass around dir for found tags file for better integration with fugitive (thanks to Markus Bertheau).","3":"Use a defaultdict for easier appending.\r\nPass around dir for found tags file for better integration with fugitive (thanks to Markus Bertheau).","package":"autotag.vim","4":"autotag.vim","src_id":"17415","5":"17415","creation_date":"1328792361","6":"1328792361"},{"0":"1343","vim_version":"7.0","1":"7.0","script_version":"1.12.2","2":"1.12.2","version_comment":"Fixed vim_global(), you can now change the verbosity of the debugging on the fly.\r\ndo\r\n\r\n:call AutoTagDebug()\r\n\r\nto get the debug window and if you lower the verbosity threshold below 30 (logging.WARNING) you'll start to see debug lines about progress. At logging.WARNING the code only emits warnings about failures.","3":"Fixed vim_global(), you can now change the verbosity of the debugging on the fly.\r\ndo\r\n\r\n:call AutoTagDebug()\r\n\r\nto get the debug window and if you lower the verbosity threshold below 30 (logging.WARNING) you'll start to see debug lines about progress. At logging.WARNING the code only emits warnings about failures.","package":"autotag.vim","4":"autotag.vim","src_id":"17400","5":"17400","creation_date":"1328521080","6":"1328521080"},{"0":"1343","vim_version":"7.0","1":"7.0","script_version":"1.12.1","2":"1.12.1","version_comment":"Fixed the Disabled flag handling","3":"Fixed the Disabled flag handling","package":"autotag.vim","4":"autotag.vim","src_id":"17360","5":"17360","creation_date":"1328094844","6":"1328094844"},{"0":"1343","vim_version":"7.0","1":"7.0","script_version":"1.12","2":"1.12","version_comment":"Pythonic debugging (do :call AutoTagDebug() to see debugging)\r\nBetter management of default settings\r\nAbility to stop autotag searching for a tags file if is climbs the tree and reaches a certain directory (likely $HOME, say)\r\nConfigurable max tag file size","3":"Pythonic debugging (do :call AutoTagDebug() to see debugging)\r\nBetter management of default settings\r\nAbility to stop autotag searching for a tags file if is climbs the tree and reaches a certain directory (likely $HOME, say)\r\nConfigurable max tag file size","package":"autotag.vim","4":"autotag.vim","src_id":"17347","5":"17347","creation_date":"1328000746","6":"1328000746"},{"0":"1343","vim_version":"7.0","1":"7.0","script_version":"1.11","2":"1.11","version_comment":"Avoid using fileinput.input() as per Tim Cuthbertson's patch. Thanks!","3":"Avoid using fileinput.input() as per Tim Cuthbertson's patch. Thanks!","package":"autotag.vim","4":"autotag.vim","src_id":"15099","5":"15099","creation_date":"1298471126","6":"1298471126"},{"0":"1343","vim_version":"6.0","1":"6.0","script_version":"1.10","2":"1.10","version_comment":"Minor bug-fix from Manpreet.","3":"Minor bug-fix from Manpreet.","package":"autotag.vim","4":"autotag.vim","src_id":"12473","5":"12473","creation_date":"1266931301","6":"1266931301"},{"0":"1343","vim_version":"6.0","1":"6.0","script_version":"1.9","2":"1.9","version_comment":"Minor change to support updating the taglist menu (for script #273)\r\nThanks Nick.","3":"Minor change to support updating the taglist menu (for script #273)\r\nThanks Nick.","package":"autotag.vim","4":"autotag.vim","src_id":"11095","5":"11095","creation_date":"1248943990","6":"1248943990"},{"0":"1343","vim_version":"6.0","1":"6.0","script_version":"1.8","2":"1.8","version_comment":"Tidied up the diag stuff, using *much* more meaningful variables.\r\nFixed the empty default tags file name.\r\nConfirmed working in MacVim, other platforms not verified. :-$","3":"Tidied up the diag stuff, using *much* more meaningful variables.\r\nFixed the empty default tags file name.\r\nConfirmed working in MacVim, other platforms not verified. :-$","package":"autotag.vim","4":"autotag.vim","src_id":"10912","5":"10912","creation_date":"1246359377","6":"1246359377"},{"0":"1343","vim_version":"7.0","1":"7.0","script_version":"1.7","2":"1.7","version_comment":"More backwards compatibility aimed at Python 2.3.","3":"More backwards compatibility aimed at Python 2.3.","package":"autotag.vim","4":"autotag.vim","src_id":"9886","5":"9886","creation_date":"1233270561","6":"1233270561"},{"0":"1343","vim_version":"6.0","1":"6.0","script_version":"1.6","2":"1.6","version_comment":"Support Python older than 2.4.","3":"Support Python older than 2.4.","package":"autotag.vim","4":"autotag.vim","src_id":"9883","5":"9883","creation_date":"1233227047","6":"1233227047"},{"0":"1343","vim_version":"6.0","1":"6.0","script_version":"1.5","2":"1.5","version_comment":"Improved support for Python 2.6 (with some help from Andreas Schneider: cheers!) by moving to Python 2.4 subprocess API.","3":"Improved support for Python 2.6 (with some help from Andreas Schneider: cheers!) by moving to Python 2.4 subprocess API.","package":"autotag.vim","4":"autotag.vim","src_id":"9640","5":"9640","creation_date":"1228810407","6":"1228810407"},{"0":"1343","vim_version":"6.0","1":"6.0","script_version":"1.4","2":"1.4","version_comment":"Changed the way the script prints messages.\r\nNow there's a run-time configurable verbosity level in the script.\r\nBy default it's 0 (zero) so no messages are printed.\r\nI use level 1 (one) and get a nice quick message telling me which ctags file is being updated.","3":"Changed the way the script prints messages.\r\nNow there's a run-time configurable verbosity level in the script.\r\nBy default it's 0 (zero) so no messages are printed.\r\nI use level 1 (one) and get a nice quick message telling me which ctags file is being updated.","package":"autotag.vim","4":"autotag.vim","src_id":"7256","5":"7256","creation_date":"1182148576","6":"1182148576"},{"0":"1343","vim_version":"6.0","1":"6.0","script_version":"1.3","2":"1.3","version_comment":"Submission from Johan Segolsson added configuration of the ctags command name.\r\nThanks Johan.","3":"Submission from Johan Segolsson added configuration of the ctags command name.\r\nThanks Johan.","package":"autotag.vim","4":"autotag.vim","src_id":"7240","5":"7240","creation_date":"1181725561","6":"1181725561"},{"0":"1343","vim_version":"6.0","1":"6.0","script_version":"1.2","2":"1.2","version_comment":"1.1 would re-declare the Python class on every write.\r\nI've also made the information messages better.\r\nIf you experience a pause during the update, the messages should now let you know where it's happening. :-)","3":"1.1 would re-declare the Python class on every write.\r\nI've also made the information messages better.\r\nIf you experience a pause during the update, the messages should now let you know where it's happening. :-)","package":"autotag.vim","4":"autotag.vim","src_id":"7227","5":"7227","creation_date":"1181533033","6":"1181533033"},{"0":"1343","vim_version":"6.0","1":"6.0","script_version":"1.1","2":"1.1","version_comment":"Fixed a couple of small issues:\r\nFiles with spaces in their names \/ paths are now quoted before being given as arguments to ctags\r\n(though I plan to change this code from using os.popen to using os.execl so as to completely avoid these kinds of issues)\r\nIf the tags file is found in \\ (e.g. c:\\) then I was making the relative path incorrectly. This is fixed.\r\nI've cleaned up the handling of '\/' and '\\\\' in paths (since tags files specify files with '\/' but your OS may not)","3":"Fixed a couple of small issues:\r\nFiles with spaces in their names \/ paths are now quoted before being given as arguments to ctags\r\n(though I plan to change this code from using os.popen to using os.execl so as to completely avoid these kinds of issues)\r\nIf the tags file is found in \\ (e.g. c:\\) then I was making the relative path incorrectly. This is fixed.\r\nI've cleaned up the handling of '\/' and '\\\\' in paths (since tags files specify files with '\/' but your OS may not)","package":"autotag.vim","4":"autotag.vim","src_id":"4663","5":"4663","creation_date":"1128999916","6":"1128999916"},{"0":"1343","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"autotag.vim","4":"autotag.vim","src_id":"4548","5":"4548","creation_date":"1125644599","6":"1125644599"}]},"1341":{"script_id":"1341","0":"1341","script_name":"last_change","1":"last_change","script_type":"utility","2":"utility","summary":"automatically set time-stamp on modification","3":"automatically set time-stamp on modification","description":"this (very) lightweight script automatically updates the time-stamp on a file when you :write it out.\r\nthe time-stamp is of the form:\r\n     Last Change:  Wed Aug 31 10:00 AM 2005 EDT\r\n\r\nThe script is similar to the example given in :help autocmd, the difference being that the time-stamp already there is checked. If it is identical to the one being added, then nothing is done. Since the time-stamp is truncated to the last hour, this ensures that the undo buffer is changed only for :write's every hour.\r\n\r\nSet g:timeStampLeader in your ~\/.vimrc to change 'Last Change: '\r\n(to 'Last modified: ' for instance)\r\n\r\nUse :NOMOD to force the time-stamp to be not updated.\r\nUse :MOD to change it back.\r\n\r\nPS: The update only works if the string 'Last Change: ' is found somewhere\r\nin the first 20 lines of the file. Only the first found occurence is processed. \r\n\r\nThis is a modified version of lastchange.vim script by Srinath Avadhanula.  This version fixes a bug where if the system was not win32, the time-zone would get truncated from PST to P, or EDT to E, etc.","4":"this (very) lightweight script automatically updates the time-stamp on a file when you :write it out.\r\nthe time-stamp is of the form:\r\n     Last Change:  Wed Aug 31 10:00 AM 2005 EDT\r\n\r\nThe script is similar to the example given in :help autocmd, the difference being that the time-stamp already there is checked. If it is identical to the one being added, then nothing is done. Since the time-stamp is truncated to the last hour, this ensures that the undo buffer is changed only for :write's every hour.\r\n\r\nSet g:timeStampLeader in your ~\/.vimrc to change 'Last Change: '\r\n(to 'Last modified: ' for instance)\r\n\r\nUse :NOMOD to force the time-stamp to be not updated.\r\nUse :MOD to change it back.\r\n\r\nPS: The update only works if the string 'Last Change: ' is found somewhere\r\nin the first 20 lines of the file. Only the first found occurence is processed. \r\n\r\nThis is a modified version of lastchange.vim script by Srinath Avadhanula.  This version fixes a bug where if the system was not win32, the time-zone would get truncated from PST to P, or EDT to E, etc.","install_details":"(Windows)    drop in C:\\Program Files\\Vim\\vimfiles\\plugin\r\n(UNIX)           drop in ~\/.vim\/plugin ","5":"(Windows)    drop in C:\\Program Files\\Vim\\vimfiles\\plugin\r\n(UNIX)           drop in ~\/.vim\/plugin ","first_name":"Justin","6":"Justin","last_name":"Randall","7":"Randall","releases":[{"0":"1341","vim_version":"6.0","1":"6.0","script_version":"1.1","2":"1.1","version_comment":"Initial upload","3":"Initial upload","package":"last_change.vim","4":"last_change.vim","src_id":"4540","5":"4540","creation_date":"1125475229","6":"1125475229"}]},"1340":{"script_id":"1340","0":"1340","script_name":"last_change","1":"last_change","script_type":"utility","2":"utility","summary":"automatically set time-stamp on modification","3":"automatically set time-stamp on modification","description":"this (very) lightweight script automatically updates the time-stamp on a file when you :write it out.\r\nthe time-stamp is of the form:\r\n     Last Change:  Wed Aug 31 10:00 AM 2005 EDT\r\n\r\nThe script is similar to the example given in :help autocmd, the difference being that the time-stamp already there is checked. If it is identical to the one being added, then nothing is done. Since the time-stamp is truncated to the last hour, this ensures that the undo buffer is changed only for :write's every hour.\r\n\r\nSet g:timeStampLeader in your ~\/.vimrc to change 'Last Change: '\r\n(to 'Last modified: ' for instance)\r\n\r\nUse :NOMOD to force the time-stamp to be not updated.\r\nUse :MOD to change it back.\r\n\r\nPS: The update only works if the string 'Last Change: ' is found somewhere\r\nin the first 20 lines of the file. Only the first found occurence is processed. \r\n\r\nThis is a modified version of lastchange.vim script by Srinath Avadhanula.  This version fixes a bug where if the system was not win32, the time-zone would get truncated from PST to P, or EDT to E, etc.","4":"this (very) lightweight script automatically updates the time-stamp on a file when you :write it out.\r\nthe time-stamp is of the form:\r\n     Last Change:  Wed Aug 31 10:00 AM 2005 EDT\r\n\r\nThe script is similar to the example given in :help autocmd, the difference being that the time-stamp already there is checked. If it is identical to the one being added, then nothing is done. Since the time-stamp is truncated to the last hour, this ensures that the undo buffer is changed only for :write's every hour.\r\n\r\nSet g:timeStampLeader in your ~\/.vimrc to change 'Last Change: '\r\n(to 'Last modified: ' for instance)\r\n\r\nUse :NOMOD to force the time-stamp to be not updated.\r\nUse :MOD to change it back.\r\n\r\nPS: The update only works if the string 'Last Change: ' is found somewhere\r\nin the first 20 lines of the file. Only the first found occurence is processed. \r\n\r\nThis is a modified version of lastchange.vim script by Srinath Avadhanula.  This version fixes a bug where if the system was not win32, the time-zone would get truncated from PST to P, or EDT to E, etc.","install_details":"(Windows) drop in C:\\Program Files\\Vim\\vimfiles\\plugin\r\n(UNIX)drop in ~\/.vim\/plugin ","5":"(Windows) drop in C:\\Program Files\\Vim\\vimfiles\\plugin\r\n(UNIX)drop in ~\/.vim\/plugin ","first_name":"Justin","6":"Justin","last_name":"Randall","7":"Randall","releases":[{"0":"1340","vim_version":"6.0","1":"6.0","script_version":"1.1","2":"1.1","version_comment":"Initial upload","3":"Initial upload","package":"last_change.vim","4":"last_change.vim","src_id":"4539","5":"4539","creation_date":"1125475219","6":"1125475219"}]},"1339":{"script_id":"1339","0":"1339","script_name":"Autoproject","1":"Autoproject","script_type":"utility","2":"utility","summary":"Use Makefile.am for project management","3":"Use Makefile.am for project management","description":"This is another project management for vim. \r\nIt scans all Makefile.am files recursively for SUBDIRS, _HEADERS and _SOURCES entries and displays all found files and directories in a window left of the codewindow. \r\nIf you select a file, it is opened. ","4":"This is another project management for vim. \r\nIt scans all Makefile.am files recursively for SUBDIRS, _HEADERS and _SOURCES entries and displays all found files and directories in a window left of the codewindow. \r\nIf you select a file, it is opened. ","install_details":"Copy autoproject.vim to ~\/.vim\/plugin\r\nOpen project window with F9 in a automake-based project directory","5":"Copy autoproject.vim to ~\/.vim\/plugin\r\nOpen project window with F9 in a automake-based project directory","first_name":"Lorenz","6":"Lorenz","last_name":"M\u00c3\u00b6senlechner","7":"M\u00c3\u00b6senlechner","releases":[{"0":"1339","vim_version":"6.0","1":"6.0","script_version":"1.1","2":"1.1","version_comment":"Changes: \r\n- color support added (copy syn-autoproject.vim to ~\/.vim\/syntax)\r\n- processing of variables in Makefile.am and makefile\r\n- Makefile.am and configure.in are displayed","3":"Changes: \r\n- color support added (copy syn-autoproject.vim to ~\/.vim\/syntax)\r\n- processing of variables in Makefile.am and makefile\r\n- Makefile.am and configure.in are displayed","package":"autoproject.tar.bz2","4":"autoproject.tar.bz2","src_id":"4550","5":"4550","creation_date":"1125819260","6":"1125819260"},{"0":"1339","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"autoproject.vim","4":"autoproject.vim","src_id":"4537","5":"4537","creation_date":"1125387827","6":"1125387827"}]},"1338":{"script_id":"1338","0":"1338","script_name":"TabBar","1":"TabBar","script_type":"utility","2":"utility","summary":"Plugin to add tab bar ( derived from miniBufExplorer).","3":"Plugin to add tab bar ( derived from miniBufExplorer).","description":"The plugin is derived from miniBufExplorer.\r\nOnly the modifiable buffer are displayed, and counted.\r\nKey-bindings for buffer switching: <Alt-bufNumber>\r\nColored the tabs with the same color as StatusLineNC to create the impression\r\nof tabs.\r\n\r\nTabBar in winxp cmd:\r\nhttp:\/\/photos1.blogger.com\/blogger\/4648\/1229\/1600\/winxp_cmd.jpg\r\n\r\nand gvim on winxp\r\nhttp:\/\/photos1.blogger.com\/blogger\/4648\/1229\/1600\/winxp.jpg\r\n\r\n\r\nand gvim on linux+ion3\r\nhttp:\/\/photos1.blogger.com\/blogger\/4648\/1229\/1600\/screen.1.jpg","4":"The plugin is derived from miniBufExplorer.\r\nOnly the modifiable buffer are displayed, and counted.\r\nKey-bindings for buffer switching: <Alt-bufNumber>\r\nColored the tabs with the same color as StatusLineNC to create the impression\r\nof tabs.\r\n\r\nTabBar in winxp cmd:\r\nhttp:\/\/photos1.blogger.com\/blogger\/4648\/1229\/1600\/winxp_cmd.jpg\r\n\r\nand gvim on winxp\r\nhttp:\/\/photos1.blogger.com\/blogger\/4648\/1229\/1600\/winxp.jpg\r\n\r\n\r\nand gvim on linux+ion3\r\nhttp:\/\/photos1.blogger.com\/blogger\/4648\/1229\/1600\/screen.1.jpg","install_details":"download tabbar.vim\r\nFor *nix:\r\ncp tabbar.vim $HOME\/.vim\/plugin\r\n\r\nFor windows\r\ncp tabbar.vim c:\\vim_location\\vimfiles\\plugin","5":"download tabbar.vim\r\nFor *nix:\r\ncp tabbar.vim $HOME\/.vim\/plugin\r\n\r\nFor windows\r\ncp tabbar.vim c:\\vim_location\\vimfiles\\plugin","first_name":"Marius","6":"Marius","last_name":"Groleo","7":"Groleo","releases":[{"0":"1338","vim_version":"6.0","1":"6.0","script_version":"0.7","2":"0.7","version_comment":"Fixed Bruce Who \"<<\" issue.\r\n","3":"Fixed Bruce Who \"<<\" issue.\r\n","package":"tabbar.vim","4":"tabbar.vim","src_id":"4976","5":"4976","creation_date":"1137372588","6":"1137372588"},{"0":"1338","vim_version":"6.0","1":"6.0","script_version":"0.6","2":"0.6","version_comment":"vim 6 compatible","3":"vim 6 compatible","package":"tabbar.vim","4":"tabbar.vim","src_id":"4886","5":"4886","creation_date":"1134375206","6":"1134375206"},{"0":"1338","vim_version":"6.0","1":"6.0","script_version":"0.5","2":"0.5","version_comment":"Fixed the \"delete buffer with d\" bug.\r\nNow it should work ok.","3":"Fixed the \"delete buffer with d\" bug.\r\nNow it should work ok.","package":"tabbar.vim","4":"tabbar.vim","src_id":"4883","5":"4883","creation_date":"1134342881","6":"1134342881"},{"0":"1338","vim_version":"6.0","1":"6.0","script_version":"0.4","2":"0.4","version_comment":"Copyright issues are worked out: I spelled wrong Bindu Wavell, as Bindu Well","3":"Copyright issues are worked out: I spelled wrong Bindu Wavell, as Bindu Well","package":"tabbar.vim","4":"tabbar.vim","src_id":"4832","5":"4832","creation_date":"1133305985","6":"1133305985"},{"0":"1338","vim_version":"6.0","1":"6.0","script_version":"0.3","2":"0.3","version_comment":"Aaron Griffin added g:Tb_SplitToEdge.\r\n","3":"Aaron Griffin added g:Tb_SplitToEdge.\r\n","package":"tabbar.vim","4":"tabbar.vim","src_id":"4804","5":"4804","creation_date":"1132787571","6":"1132787571"},{"0":"1338","vim_version":"6.0","1":"6.0","script_version":"0.2","2":"0.2","version_comment":"Added bindings for INSERT mode too( 0.1 has bindings only for NORMAL mode).\r\nCleaned the code and removed some redundant variables.","3":"Added bindings for INSERT mode too( 0.1 has bindings only for NORMAL mode).\r\nCleaned the code and removed some redundant variables.","package":"tabbar.vim","4":"tabbar.vim","src_id":"4536","5":"4536","creation_date":"1125362391","6":"1125362391"},{"0":"1338","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"tabbar.vim","4":"tabbar.vim","src_id":"4534","5":"4534","creation_date":"1125276470","6":"1125276470"}]},"1337":{"script_id":"1337","0":"1337","script_name":"plugin\/fonts.vim","1":"plugin\/fonts.vim","script_type":"utility","2":"utility","summary":"Multi OS Font Plugin","3":"Multi OS Font Plugin","description":"= Multi OS Font Plugin =\r\n\r\n== Description ==\r\n\r\nThis is a mirror of http:\/\/www.vim.org\/scripts\/script.php?script_id=1337\r\n\r\nThis plug-in set's the font used depending on the operating system \/ windowing system used. It also contains a smaller and larger font to zoom in and out. It is very helpful if you use GVim with more then one OS, display resolutions etc. pp.\r\n\r\nYou can easily expand the plugin for more OS's or fonts.\r\n\r\n\u00e2\u0080\u00a2 Vim-Script: https:\/\/www.vim.org\/scripts\/script.php?script_id=1337\r\n\u00e2\u0080\u00a2 Source:       https:\/\/github.com\/krischik\/vim-fonts\r\n\u00e2\u0080\u00a2 Wiki:             https:\/\/github.com\/krischik\/vim-fonts\/wiki\r\n\u00e2\u0080\u00a2 Releases:     https:\/\/github.com\/krischik\/vim-fonts\/releases \r\n\u00e2\u0080\u00a2 Issues:       https:\/\/github.com\/krischik\/vim-fonts\/issues \r\n\u00e2\u0080\u00a2 Discussions:  https:\/\/github.com\/krischik\/vim-fonts\/discussions \r\n\r\n\r\n==Comments==\r\n\r\n","4":"= Multi OS Font Plugin =\r\n\r\n== Description ==\r\n\r\nThis is a mirror of http:\/\/www.vim.org\/scripts\/script.php?script_id=1337\r\n\r\nThis plug-in set's the font used depending on the operating system \/ windowing system used. It also contains a smaller and larger font to zoom in and out. It is very helpful if you use GVim with more then one OS, display resolutions etc. pp.\r\n\r\nYou can easily expand the plugin for more OS's or fonts.\r\n\r\n\u00e2\u0080\u00a2 Vim-Script: https:\/\/www.vim.org\/scripts\/script.php?script_id=1337\r\n\u00e2\u0080\u00a2 Source:       https:\/\/github.com\/krischik\/vim-fonts\r\n\u00e2\u0080\u00a2 Wiki:             https:\/\/github.com\/krischik\/vim-fonts\/wiki\r\n\u00e2\u0080\u00a2 Releases:     https:\/\/github.com\/krischik\/vim-fonts\/releases \r\n\u00e2\u0080\u00a2 Issues:       https:\/\/github.com\/krischik\/vim-fonts\/issues \r\n\u00e2\u0080\u00a2 Discussions:  https:\/\/github.com\/krischik\/vim-fonts\/discussions \r\n\r\n\r\n==Comments==\r\n\r\n","install_details":"Install from https:\/\/github.com\/krischik\/vim-fonts using dein (https:\/\/github.com\/Shougo\/dein.vim) or similar:\r\n\r\n\r\ncall dein#begin('$HOME\/vimfiles\/bundles')\r\ncall dein#add('krischik\/vim-fonts')\r\ncall dein#end()\r\ncall dein#install()\r\n\r\n","5":"Install from https:\/\/github.com\/krischik\/vim-fonts using dein (https:\/\/github.com\/Shougo\/dein.vim) or similar:\r\n\r\n\r\ncall dein#begin('$HOME\/vimfiles\/bundles')\r\ncall dein#add('krischik\/vim-fonts')\r\ncall dein#end()\r\ncall dein#install()\r\n\r\n","first_name":"Martin","6":"Martin","last_name":"Krischik","7":"Krischik","releases":[{"0":"1337","vim_version":"7.0","1":"7.0","script_version":"1.5","2":"1.5","version_comment":"https:\/\/github.com\/krischik\/vim-plugin-fonts\/releases\/tag\/v_1.5","3":"https:\/\/github.com\/krischik\/vim-plugin-fonts\/releases\/tag\/v_1.5","package":"vim-plugin-fonts-v_1.5.zip","4":"vim-plugin-fonts-v_1.5.zip","src_id":"28184","5":"28184","creation_date":"1663471443","6":"1663471443"},{"0":"1337","vim_version":"7.0","1":"7.0","script_version":"1.4","2":"1.4","version_comment":"Now with Sun Solaris support. But mind you: All font settings for XServer platforms depend on the Client and Server used - you might hat to fine tune the script for your environment.","3":"Now with Sun Solaris support. But mind you: All font settings for XServer platforms depend on the Client and Server used - you might hat to fine tune the script for your environment.","package":"fonts.vim","4":"fonts.vim","src_id":"6436","5":"6436","creation_date":"1163815049","6":"1163815049"},{"0":"1337","vim_version":"7.0","1":"7.0","script_version":"1.3","2":"1.3","version_comment":"Minor improvements","3":"Minor improvements","package":"fonts.vim","4":"fonts.vim","src_id":"5671","5":"5671","creation_date":"1147242368","6":"1147242368"},{"0":"1337","vim_version":"6.0","1":"6.0","script_version":"1.2","2":"1.2","version_comment":"This version will resize the window as well when changing fonts. Mapping and menus have been improved to support a function key as g:mapleader.","3":"This version will resize the window as well when changing fonts. Mapping and menus have been improved to support a function key as g:mapleader.","package":"fonts.vim","4":"fonts.vim","src_id":"5308","5":"5308","creation_date":"1140675652","6":"1140675652"},{"0":"1337","vim_version":"6.0","1":"6.0","script_version":"1.1","2":"1.1","version_comment":"This version has more features - like using smaller fonts for vimdiff or an alternative fontset for utf8 encoded files.","3":"This version has more features - like using smaller fonts for vimdiff or an alternative fontset for utf8 encoded files.","package":"fonts.vim","4":"fonts.vim","src_id":"4670","5":"4670","creation_date":"1129188655","6":"1129188655"},{"0":"1337","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"fonts.vim","4":"fonts.vim","src_id":"4527","5":"4527","creation_date":"1125054321","6":"1125054321"}]},"1336":{"script_id":"1336","0":"1336","script_name":"Professional colorscheme for Vim","1":"Professional colorscheme for Vim","script_type":"color scheme","2":"color scheme","summary":"At last, a professional colorscheme for Vim...","3":"At last, a professional colorscheme for Vim...","description":"At last, a professional colorscheme for Vim...released by popular demand !\r\n\r\n*Highlights*\r\n\r\n* Uses light background for easy editing on bright light conditions\r\n* Status bar and line numbers uses dark background\r\n* No two highlighting terms have same colors making it easy to distinguish what you are looking at\r\n\r\nSpecially suited if you spend most of your day editing and writing code\r\n\r\nCurrently supports only GUI version. If there is enough demand, I will release a cterm version.","4":"At last, a professional colorscheme for Vim...released by popular demand !\r\n\r\n*Highlights*\r\n\r\n* Uses light background for easy editing on bright light conditions\r\n* Status bar and line numbers uses dark background\r\n* No two highlighting terms have same colors making it easy to distinguish what you are looking at\r\n\r\nSpecially suited if you spend most of your day editing and writing code\r\n\r\nCurrently supports only GUI version. If there is enough demand, I will release a cterm version.","install_details":"Just copy professional.vim to your colors directory.\r\nFrom vim, type Esc :colo professional","5":"Just copy professional.vim to your colors directory.\r\nFrom vim, type Esc :colo professional","first_name":"Narayanan","6":"Narayanan","last_name":"Iyer","7":"Iyer","releases":[{"0":"1336","vim_version":"6.0","1":"6.0","script_version":"1.4","2":"1.4","version_comment":"Background color changed ! Now blends well with the other colors !","3":"Background color changed ! Now blends well with the other colors !","package":"professional.vim","4":"professional.vim","src_id":"4571","5":"4571","creation_date":"1126574536","6":"1126574536"},{"0":"1336","vim_version":"6.0","1":"6.0","script_version":"1.3","2":"1.3","version_comment":"Still more colorful !","3":"Still more colorful !","package":"professional.vim","4":"professional.vim","src_id":"4542","5":"4542","creation_date":"1125539423","6":"1125539423"},{"0":"1336","vim_version":"6.0","1":"6.0","script_version":"1.2","2":"1.2","version_comment":"\"Professional\" colors for file browsing (with e .)","3":"\"Professional\" colors for file browsing (with e .)","package":"professional.vim","4":"professional.vim","src_id":"4526","5":"4526","creation_date":"1125042681","6":"1125042681"},{"0":"1336","vim_version":"6.0","1":"6.0","script_version":"1.1","2":"1.1","version_comment":"Seamless integration of vertical split !","3":"Seamless integration of vertical split !","package":"professional.vim","4":"professional.vim","src_id":"4524","5":"4524","creation_date":"1125041463","6":"1125041463"},{"0":"1336","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"professional.vim","4":"professional.vim","src_id":"4522","5":"4522","creation_date":"1125032507","6":"1125032507"}]},"1335":{"script_id":"1335","0":"1335","script_name":"A soft mellow color scheme","1":"A soft mellow color scheme","script_type":"color scheme","2":"color scheme","summary":"A soft mellow colorscheme","3":"A soft mellow colorscheme","description":"A soft mellow colorscheme especially suited for bright light condition.","4":"A soft mellow colorscheme especially suited for bright light condition.","install_details":"Justcopy the file to your colors directory and type Esc :colo mellow from vim","5":"Justcopy the file to your colors directory and type Esc :colo mellow from vim","first_name":"Narayanan","6":"Narayanan","last_name":"Iyer","7":"Iyer","releases":[{"0":"1335","vim_version":"6.0","1":"6.0","script_version":"1.1","2":"1.1","version_comment":"Improved visibility for cursor !","3":"Improved visibility for cursor !","package":"mellow.vim","4":"mellow.vim","src_id":"4535","5":"4535","creation_date":"1125277638","6":"1125277638"},{"0":"1335","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"mellow.vim","4":"mellow.vim","src_id":"4521","5":"4521","creation_date":"1125025394","6":"1125025394"}]},"1334":{"script_id":"1334","0":"1334","script_name":"VST","1":"VST","script_type":"utility","2":"utility","summary":"Vim reStructured Text","3":"Vim reStructured Text","description":"Requires Vim7.\r\n\r\nVST is script which makes possible to export text files with simple markup to HTML or LaTeX format or S5 HTML presentation. Script doesn't require any external dependency and will work on any platform Vim7 is available. VST is implementation of reStructuredText.\r\n\r\nSupported elements of inline markup:\r\n\r\n- emphasised text (italic)\r\n- strongly emphasised text (bold)\r\n- hyperlinks (in various syntax forms)\r\n- custom decorations (among them: sub, sup, big, small)\r\n\r\nElements of documents structure:\r\n\r\n- paragraphs\r\n- block quotes\r\n- ordered lists\r\n- unordered lists\r\n- option lists\r\n- footnotes\r\n- citations\r\n- images\r\n- preformatted text\r\n- colorized preformatted text (HTML export only)\r\n- tables\r\n- admonitions\r\n- table of contents\r\n\r\nAlso bunch of auxiliary commands which should ease writing of document and navigating (folding, text table of contents, lists or declared links, replacements)\r\n\r\nLatest version of script:\r\nhttp:\/\/skawina.eu.org\/mikolaj\/vst.zip\r\n\r\nHelp file in text form:\r\nhttp:\/\/skawina.eu.org\/mikolaj\/vst.txt\r\n\r\nFollowing versions of help file was produced without any modifications to HTML or LaTeX source:\r\n\r\nHTML:\r\nhttp:\/\/skawina.eu.org\/mikolaj\/vst.html\r\n\r\nLaTeX file exported from vst.txt:\r\nhttp:\/\/skawina.eu.org\/mikolaj\/vst.tex\r\n\r\nPDF file produced from vst.tex:\r\nhttp:\/\/skawina.eu.org\/mikolaj\/vst.pdf\r\n","4":"Requires Vim7.\r\n\r\nVST is script which makes possible to export text files with simple markup to HTML or LaTeX format or S5 HTML presentation. Script doesn't require any external dependency and will work on any platform Vim7 is available. VST is implementation of reStructuredText.\r\n\r\nSupported elements of inline markup:\r\n\r\n- emphasised text (italic)\r\n- strongly emphasised text (bold)\r\n- hyperlinks (in various syntax forms)\r\n- custom decorations (among them: sub, sup, big, small)\r\n\r\nElements of documents structure:\r\n\r\n- paragraphs\r\n- block quotes\r\n- ordered lists\r\n- unordered lists\r\n- option lists\r\n- footnotes\r\n- citations\r\n- images\r\n- preformatted text\r\n- colorized preformatted text (HTML export only)\r\n- tables\r\n- admonitions\r\n- table of contents\r\n\r\nAlso bunch of auxiliary commands which should ease writing of document and navigating (folding, text table of contents, lists or declared links, replacements)\r\n\r\nLatest version of script:\r\nhttp:\/\/skawina.eu.org\/mikolaj\/vst.zip\r\n\r\nHelp file in text form:\r\nhttp:\/\/skawina.eu.org\/mikolaj\/vst.txt\r\n\r\nFollowing versions of help file was produced without any modifications to HTML or LaTeX source:\r\n\r\nHTML:\r\nhttp:\/\/skawina.eu.org\/mikolaj\/vst.html\r\n\r\nLaTeX file exported from vst.txt:\r\nhttp:\/\/skawina.eu.org\/mikolaj\/vst.tex\r\n\r\nPDF file produced from vst.tex:\r\nhttp:\/\/skawina.eu.org\/mikolaj\/vst.pdf\r\n","install_details":"Unzip vst.zip from level of ~\/.vim. It contains data files and documentation in doc2 directory.\r\nTo use just do :source vst.vim and for default HTML export do\r\n:Vst\r\nShort help about script\r\n:Vst help","5":"Unzip vst.zip from level of ~\/.vim. It contains data files and documentation in doc2 directory.\r\nTo use just do :source vst.vim and for default HTML export do\r\n:Vst\r\nShort help about script\r\n:Vst help","first_name":"Mikolaj","6":"Mikolaj","last_name":"Machowski","7":"Machowski","releases":[{"0":"1334","vim_version":"7.0","1":"7.0","script_version":"1.4","2":"1.4","version_comment":"- FIX: Vst link broken\r\n- FIX: & in URLs double encoded\r\n- FIX: broken chained links with uppercase letters\r\n","3":"- FIX: Vst link broken\r\n- FIX: & in URLs double encoded\r\n- FIX: broken chained links with uppercase letters\r\n","package":"vst.zip","4":"vst.zip","src_id":"6377","5":"6377","creation_date":"1162613630","6":"1162613630"},{"0":"1334","vim_version":"7.0","1":"7.0","script_version":"1.3","2":"1.3","version_comment":"  - ADD: show number of directive line and percentage position in file for\r\n    easier navigation when folding by directive\r\n  - ADD: proper encryption of URIs (amp, percentage)\r\n  - ADD: make preproc auxiliary command recursive\r\n  - ADD: fold according to level of headers: fold1, fold2, etc.\r\n  - ADD: recursive folding: foldr\r\n  - ADD: [LaTeX] containers as ghost commands\r\n  - ADD: [LaTeX] Generator line (debug purposes)\r\n  - CHG: make folding by directive more flexible\r\n  - CHG: improve layout of fold texts with centered titles\r\n  - CHG: improve layout of text table of contents with centered titles\r\n  - CHG: level of recursiveness is now &maxfuncdepth\/2 (50 should be enough\r\n    for everybody!)\r\n  - CHG: [HTML] when source are lists starting from no-one use transitional\r\n    doctype, otherwise strict\r\n  - CHG: [HTML] \"Downgrade\" to HTML 4.01 (no sense to use XHTML doctype when\r\n    using content text\/html)\r\n  - FIX: length of ornaments inserted with <C-B>o\r\n  - FIX: show output of auxiliary commands depending on table\r\n  - FIX: presence of apostrophes in section titles could cause problems in folding\r\n  - FIX: internal links in fancy formatted text could be broken\r\n  - FIX: unnecessary creation of targets from links broken in several lines\r\n  - FIX: minor fixes in docs\r\n  - FIX: optimizations, 10-15% speed gains\r\n  - FIX: [LaTeX] too much whitespace at the end of footnotes\r\n  - FIX: [LaTeX] internal links work again\r\n  - FIX: [S5] uploaded CSS files for web page to make presentation work (sorry\r\n    George!)\r\n","3":"  - ADD: show number of directive line and percentage position in file for\r\n    easier navigation when folding by directive\r\n  - ADD: proper encryption of URIs (amp, percentage)\r\n  - ADD: make preproc auxiliary command recursive\r\n  - ADD: fold according to level of headers: fold1, fold2, etc.\r\n  - ADD: recursive folding: foldr\r\n  - ADD: [LaTeX] containers as ghost commands\r\n  - ADD: [LaTeX] Generator line (debug purposes)\r\n  - CHG: make folding by directive more flexible\r\n  - CHG: improve layout of fold texts with centered titles\r\n  - CHG: improve layout of text table of contents with centered titles\r\n  - CHG: level of recursiveness is now &maxfuncdepth\/2 (50 should be enough\r\n    for everybody!)\r\n  - CHG: [HTML] when source are lists starting from no-one use transitional\r\n    doctype, otherwise strict\r\n  - CHG: [HTML] \"Downgrade\" to HTML 4.01 (no sense to use XHTML doctype when\r\n    using content text\/html)\r\n  - FIX: length of ornaments inserted with <C-B>o\r\n  - FIX: show output of auxiliary commands depending on table\r\n  - FIX: presence of apostrophes in section titles could cause problems in folding\r\n  - FIX: internal links in fancy formatted text could be broken\r\n  - FIX: unnecessary creation of targets from links broken in several lines\r\n  - FIX: minor fixes in docs\r\n  - FIX: optimizations, 10-15% speed gains\r\n  - FIX: [LaTeX] too much whitespace at the end of footnotes\r\n  - FIX: [LaTeX] internal links work again\r\n  - FIX: [S5] uploaded CSS files for web page to make presentation work (sorry\r\n    George!)\r\n","package":"vst.zip","4":"vst.zip","src_id":"6356","5":"6356","creation_date":"1162306816","6":"1162306816"},{"0":"1334","vim_version":"7.0","1":"7.0","script_version":"1.2","2":"1.2","version_comment":"  - ADD: <C-B>o auxiliary mapping for ornaments\r\n  - ADD: section numbers in fold auxiliary command\r\n  - ADD: section numbers in toc auxiliary command\r\n  - ADD: [LaTeX] raw directive accepts tex, not only latex argument\r\n  - CHG: don't look for including commands in auxiliary commands - massive\r\n    speed gains\r\n  - CHG: [LaTeX] change default font size for 12pt\r\n  - FIX: [HTML] all styles from multiple 2html directives are in <head>\r\n  - FIX: [HTML] @ in 2html directive was breaking syntax highlighting\r\n  - FIX: [HTML] restore validity of generated documents\r\n  - FIX: [LaTeX] bug with _ in filenames in raw latex file option\r\n  - FIX: many minor bugs\r\n","3":"  - ADD: <C-B>o auxiliary mapping for ornaments\r\n  - ADD: section numbers in fold auxiliary command\r\n  - ADD: section numbers in toc auxiliary command\r\n  - ADD: [LaTeX] raw directive accepts tex, not only latex argument\r\n  - CHG: don't look for including commands in auxiliary commands - massive\r\n    speed gains\r\n  - CHG: [LaTeX] change default font size for 12pt\r\n  - FIX: [HTML] all styles from multiple 2html directives are in <head>\r\n  - FIX: [HTML] @ in 2html directive was breaking syntax highlighting\r\n  - FIX: [HTML] restore validity of generated documents\r\n  - FIX: [LaTeX] bug with _ in filenames in raw latex file option\r\n  - FIX: many minor bugs\r\n","package":"vst.zip","4":"vst.zip","src_id":"6278","5":"6278","creation_date":"1160746045","6":"1160746045"},{"0":"1334","vim_version":"7.0","1":"7.0","script_version":"1.1","2":"1.1","version_comment":"  - ADD: support for ltrim, rtrim, trim for regular replacement\r\n  - CHG: `including commands`_ are working recursively now\r\n  - FIX: wrong indentation of included files\r\n  - FIX: problems with backslash as last character in line\r\n  - FIX: minor fixes in docs\r\n  - FIX: [pdf] incorrect call of cursor function\r\n","3":"  - ADD: support for ltrim, rtrim, trim for regular replacement\r\n  - CHG: `including commands`_ are working recursively now\r\n  - FIX: wrong indentation of included files\r\n  - FIX: problems with backslash as last character in line\r\n  - FIX: minor fixes in docs\r\n  - FIX: [pdf] incorrect call of cursor function\r\n","package":"vst.zip","4":"vst.zip","src_id":"5980","5":"5980","creation_date":"1153670187","6":"1153670187"},{"0":"1334","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Tons of imrovements and bugfixes from last vim-online release. Finally stable 1.0 because of final Vim7. Enjoy!","3":"Tons of imrovements and bugfixes from last vim-online release. Finally stable 1.0 because of final Vim7. Enjoy!","package":"vst.zip","4":"vst.zip","src_id":"5905","5":"5905","creation_date":"1151737534","6":"1151737534"}]},"1333":{"script_id":"1333","0":"1333","script_name":"Pleasant colorscheme","1":"Pleasant colorscheme","script_type":"color scheme","2":"color scheme","summary":"A bright and pleasant colorscheme for heavy programming","3":"A bright and pleasant colorscheme for heavy programming","description":"This is a bright and pleasant colorscheme for heavy programming for the gui version.\r\nI use it all the time for PERL !","4":"This is a bright and pleasant colorscheme for heavy programming for the gui version.\r\nI use it all the time for PERL !","install_details":"Just copy the file to your colors directory and then from vim type Esc :colo pleasant :)","5":"Just copy the file to your colors directory and then from vim type Esc :colo pleasant :)","first_name":"Narayanan","6":"Narayanan","last_name":"Iyer","7":"Iyer","releases":[{"0":"1333","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"pleasant.vim","4":"pleasant.vim","src_id":"4519","5":"4519","creation_date":"1125023312","6":"1125023312"}]},"1332":{"script_id":"1332","0":"1332","script_name":"tidy","1":"tidy","script_type":"color scheme","2":"color scheme","summary":"Color scheme 'tidy' based on PerlTidy's colors.","3":"Color scheme 'tidy' based on PerlTidy's colors.","description":"\" Vim color file tidy.vim based on PerlTidy syntax, http:\/\/perltidy.sourceforge.net\/ written by Steve Hancock <perltidy@users.sourceforge.net>. It's on light background and very pleasant look.\r\n\r\nTwo jpegs with a sources from http:\/\/www.cs.cmu.edu\/~maverick\/VimColorSchemeTest\/ :\r\nhttp:\/\/haze.ehost.pl\/pub\/perl-test.jpg\r\nhttp:\/\/haze.ehost.pl\/pub\/c-test.jpg\r\n","4":"\" Vim color file tidy.vim based on PerlTidy syntax, http:\/\/perltidy.sourceforge.net\/ written by Steve Hancock <perltidy@users.sourceforge.net>. It's on light background and very pleasant look.\r\n\r\nTwo jpegs with a sources from http:\/\/www.cs.cmu.edu\/~maverick\/VimColorSchemeTest\/ :\r\nhttp:\/\/haze.ehost.pl\/pub\/perl-test.jpg\r\nhttp:\/\/haze.ehost.pl\/pub\/c-test.jpg\r\n","install_details":"First upload.","5":"First upload.","first_name":"Tomasz","6":"Tomasz","last_name":"Kalkosinski","7":"Kalkosinski","releases":[{"0":"1332","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"tidy.vim","4":"tidy.vim","src_id":"4509","5":"4509","creation_date":"1124689370","6":"1124689370"}]},"1331":{"script_id":"1331","0":"1331","script_name":"sudoku","1":"sudoku","script_type":"game","2":"game","summary":"Sudoku solving helper","3":"Sudoku solving helper","description":"Easy key bindings for entering Sudoku riddles.\r\nCreation of fileds, filling in digits and a basic check\r\nfor correctness.","4":"Easy key bindings for entering Sudoku riddles.\r\nCreation of fileds, filling in digits and a basic check\r\nfor correctness.","install_details":"Put in into the plugin directory or just :source it.","5":"Put in into the plugin directory or just :source it.","first_name":"Bertram","6":"Bertram","last_name":"Scharpf","7":"Scharpf","releases":[{"0":"1331","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"sudoku.vim","4":"sudoku.vim","src_id":"4502","5":"4502","creation_date":"1124449864","6":"1124449864"}]},"1330":{"script_id":"1330","0":"1330","script_name":"XHTML 1.0-strict help file","1":"XHTML 1.0-strict help file","script_type":"utility","2":"utility","summary":"Help file for XHTML 1.0 Strict","3":"Help file for XHTML 1.0 Strict","description":"Help file for XHTML 1.0 Strict\r\n\r\nYou will find there \r\n- description of tag, \r\n- tags allowed inside of given tag, \r\n- list of attributes,\r\n- description of attributes,\r\n- WAI guidelines for each tag","4":"Help file for XHTML 1.0 Strict\r\n\r\nYou will find there \r\n- description of tag, \r\n- tags allowed inside of given tag, \r\n- list of attributes,\r\n- description of attributes,\r\n- WAI guidelines for each tag","install_details":"Put in ~\/.vim\/doc directory and run\r\n:helptags ~\/.vim\/doc\r\ncommand","5":"Put in ~\/.vim\/doc directory and run\r\n:helptags ~\/.vim\/doc\r\ncommand","first_name":"Mikolaj","6":"Mikolaj","last_name":"Machowski","7":"Machowski","releases":[{"0":"1330","vim_version":"6.0","1":"6.0","script_version":"2.1","2":"2.1","version_comment":"- removed doubled definitions\r\n- add info about IE not supporting abbr\r\n- added onmouseover description\r\n","3":"- removed doubled definitions\r\n- add info about IE not supporting abbr\r\n- added onmouseover description\r\n","package":"xhtml1-strict.zip","4":"xhtml1-strict.zip","src_id":"4658","5":"4658","creation_date":"1128858201","6":"1128858201"},{"0":"1330","vim_version":"6.0","1":"6.0","script_version":"2.0","2":"2.0","version_comment":"Add detailed attributes description * Add WAI guidelines * Add info about CSS 2.1 specification on vim-online","3":"Add detailed attributes description * Add WAI guidelines * Add info about CSS 2.1 specification on vim-online","package":"xhtml1-strict.zip","4":"xhtml1-strict.zip","src_id":"4510","5":"4510","creation_date":"1124705150","6":"1124705150"},{"0":"1330","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"xhtml1-strict.zip","4":"xhtml1-strict.zip","src_id":"4499","5":"4499","creation_date":"1124365093","6":"1124365093"}]},"1329":{"script_id":"1329","0":"1329","script_name":"verilogams.vim","1":"verilogams.vim","script_type":"syntax","2":"syntax","summary":"Highlighting scheme for Verilog-AMS","3":"Highlighting scheme for Verilog-AMS","description":"We're in 6.4 now, but unfortunately, Bram used the 1.0 version I sent him initially. I'll let him know that he can grab the latest version here for the 7.0 release.\r\n\r\nSo for the best highlighting experience, you should keep your own copy of 1.2 installed.","4":"We're in 6.4 now, but unfortunately, Bram used the 1.0 version I sent him initially. I'll let him know that he can grab the latest version here for the 7.0 release.\r\n\r\nSo for the best highlighting experience, you should keep your own copy of 1.2 installed.","install_details":"Put verilogams.vim in ~\/.vim\/syntax\/.\r\n\r\nCreate ~\/.vim\/filetype.vim (or edit it if you already have one) and add these lines:\r\n\r\naugroup filetypedetect\r\nau BufNewFile,BufRead *.va setf verilogams\r\nau BufNewFile,BufRead *.vams setf verilogams\r\naugroup END","5":"Put verilogams.vim in ~\/.vim\/syntax\/.\r\n\r\nCreate ~\/.vim\/filetype.vim (or edit it if you already have one) and add these lines:\r\n\r\naugroup filetypedetect\r\nau BufNewFile,BufRead *.va setf verilogams\r\nau BufNewFile,BufRead *.vams setf verilogams\r\naugroup END","first_name":"Stephen","6":"Stephen","last_name":"Prather","7":"Prather","releases":[{"0":"1329","vim_version":"6.0","1":"6.0","script_version":"1.2","2":"1.2","version_comment":"Some missing keywords fixed by Prasanna Tam. Thanks Prasanna!","3":"Some missing keywords fixed by Prasanna Tam. Thanks Prasanna!","package":"verilogams.vim","4":"verilogams.vim","src_id":"4588","5":"4588","creation_date":"1126811299","6":"1126811299"},{"0":"1329","vim_version":"6.0","1":"6.0","script_version":"1.1","2":"1.1","version_comment":"* Added the metric scale factors to the number matcher. I still need to improve the number matcher a bit, but I don't have time now.\r\n* I initially missed some of the type keywords like genvar. I think I got em all now.","3":"* Added the metric scale factors to the number matcher. I still need to improve the number matcher a bit, but I don't have time now.\r\n* I initially missed some of the type keywords like genvar. I think I got em all now.","package":"verilogams.vim","4":"verilogams.vim","src_id":"4514","5":"4514","creation_date":"1124808174","6":"1124808174"},{"0":"1329","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"verilogams.vim","4":"verilogams.vim","src_id":"4493","5":"4493","creation_date":"1124028744","6":"1124028744"}]},"1328":{"script_id":"1328","0":"1328","script_name":"xslt","1":"xslt","script_type":"ftplugin","2":"ftplugin","summary":"XSLT ftplugin","3":"XSLT ftplugin","description":"The Xslt plugin is the best vim plugin available to edit xsl files. I say its  \r\nthe best because I could not find any other script and had to make one!\r\n\r\nOnce the Xslt plugin is installed, simply press the <F2> key in Insert\r\nmode after the proper keywords and xsl text will be generated.\r\n\r\nYou also need to have xmledit plugin installed.","4":"The Xslt plugin is the best vim plugin available to edit xsl files. I say its  \r\nthe best because I could not find any other script and had to make one!\r\n\r\nOnce the Xslt plugin is installed, simply press the <F2> key in Insert\r\nmode after the proper keywords and xsl text will be generated.\r\n\r\nYou also need to have xmledit plugin installed.","install_details":"Extract to main vim runtime directory (eg: ~\/.vimrc)","5":"Extract to main vim runtime directory (eg: ~\/.vimrc)","first_name":"Pedro","6":"Pedro","last_name":"Alves","7":"Alves","releases":[{"0":"1328","vim_version":"6.0","1":"6.0","script_version":"1.0.1","2":"1.0.1","version_comment":"Removed a typo in namespace definition","3":"Removed a typo in namespace definition","package":"xslt-1.0.1.tgz","4":"xslt-1.0.1.tgz","src_id":"4496","5":"4496","creation_date":"1124258759","6":"1124258759"},{"0":"1328","vim_version":"6.0","1":"6.0","script_version":"1.0.0","2":"1.0.0","version_comment":"Initial upload","3":"Initial upload","package":"xslt-1.0.0.tgz","4":"xslt-1.0.0.tgz","src_id":"4492","5":"4492","creation_date":"1124028719","6":"1124028719"}]},"1327":{"script_id":"1327","0":"1327","script_name":"Windows PowerShell Syntax Plugin","1":"Windows PowerShell Syntax Plugin","script_type":"syntax","2":"syntax","summary":"Syntax coloring, indenting and filetype detection for Windows PowerShell","3":"Syntax coloring, indenting and filetype detection for Windows PowerShell","description":"This plugin provides Vim syntax, indent and filetype detection for WindowsPowerShell.\r\n\r\nFor bugs, suggestions or changes, please use the GitHub site:\r\n\r\nhttp:\/\/github.com\/PProvost\/vim-ps1","4":"This plugin provides Vim syntax, indent and filetype detection for WindowsPowerShell.\r\n\r\nFor bugs, suggestions or changes, please use the GitHub site:\r\n\r\nhttp:\/\/github.com\/PProvost\/vim-ps1","install_details":"Extract the contents of the zip file into your ~\/.vim (or ~\/vimfiles on Windows) folder. If using pathogen, extract into your bundle folder.","5":"Extract the contents of the zip file into your ~\/.vim (or ~\/vimfiles on Windows) folder. If using pathogen, extract into your bundle folder.","first_name":"Peter","6":"Peter","last_name":"Provost","7":"Provost","releases":[{"0":"1327","vim_version":"7.0","1":"7.0","script_version":"2.9","2":"2.9","version_comment":"Added Tomas Restrepo's changed for better booleans, constants, quoted expressions, help tags","3":"Added Tomas Restrepo's changed for better booleans, constants, quoted expressions, help tags","package":"vim-ps1.zip","4":"vim-ps1.zip","src_id":"17575","5":"17575","creation_date":"1331248080","6":"1331248080"},{"0":"1327","vim_version":"7.0","1":"7.0","script_version":"2.81","2":"2.81","version_comment":"Fixed minor type that prevented loading.","3":"Fixed minor type that prevented loading.","package":"vim-ps1.zip","4":"vim-ps1.zip","src_id":"17567","5":"17567","creation_date":"1330996600","6":"1330996600"},{"0":"1327","vim_version":"7.0","1":"7.0","script_version":"2.8","2":"2.8","version_comment":"Better number scanning, multiline comments, missing keywords and constants","3":"Better number scanning, multiline comments, missing keywords and constants","package":"vim-ps1.zip","4":"vim-ps1.zip","src_id":"17566","5":"17566","creation_date":"1330972853","6":"1330972853"},{"0":"1327","vim_version":"6.0","1":"6.0","script_version":"2.7","2":"2.7","version_comment":"Added Heath Stewart's changes:\r\n1.\tAdded begin, process, and end keywords for script blocks\r\n2.\tMake foreach and where highlight when used as foreach-object and where-object\r\n","3":"Added Heath Stewart's changes:\r\n1.\tAdded begin, process, and end keywords for script blocks\r\n2.\tMake foreach and where highlight when used as foreach-object and where-object\r\n","package":"ps1.vim","4":"ps1.vim","src_id":"9270","5":"9270","creation_date":"1222108949","6":"1222108949"},{"0":"1327","vim_version":"6.0","1":"6.0","script_version":"2.6","2":"2.6","version_comment":"Added missing unary -not operator","3":"Added missing unary -not operator","package":"ps1.vim","4":"ps1.vim","src_id":"6838","5":"6838","creation_date":"1173129693","6":"1173129693"},{"0":"1327","vim_version":"6.0","1":"6.0","script_version":"2.5","2":"2.5","version_comment":"Updates for Here-Strings, comment todos and other small cleanups.","3":"Updates for Here-Strings, comment todos and other small cleanups.","package":"ps1.vim","4":"ps1.vim","src_id":"6829","5":"6829","creation_date":"1172942127","6":"1172942127"},{"0":"1327","vim_version":"6.0","1":"6.0","script_version":"2.4","2":"2.4","version_comment":"Added missing keyword: elseif","3":"Added missing keyword: elseif","package":"ps1.vim","4":"ps1.vim","src_id":"6825","5":"6825","creation_date":"1172873113","6":"1172873113"},{"0":"1327","vim_version":"6.0","1":"6.0","script_version":"2.3","2":"2.3","version_comment":"Added missing 'param' keyword.","3":"Added missing 'param' keyword.","package":"ps1.vim","4":"ps1.vim","src_id":"6811","5":"6811","creation_date":"1172588791","6":"1172588791"},{"0":"1327","vim_version":"6.0","1":"6.0","script_version":"2.2","2":"2.2","version_comment":"Minor updates for missing keywords.","3":"Minor updates for missing keywords.","package":"ps1.vim","4":"ps1.vim","src_id":"6759","5":"6759","creation_date":"1171874814","6":"1171874814"},{"0":"1327","vim_version":"7.0","1":"7.0","script_version":"2.1","2":"2.1","version_comment":"Updated to support PowerShell renaming.","3":"Updated to support PowerShell renaming.","package":"ps1.vim","4":"ps1.vim","src_id":"6017","5":"6017","creation_date":"1154353622","6":"1154353622"},{"0":"1327","vim_version":"6.0","1":"6.0","script_version":"2.0","2":"2.0","version_comment":"Many great updates provided by Jared Parsons. Thanks Jared!","3":"Many great updates provided by Jared Parsons. Thanks Jared!","package":"msh.vim","4":"msh.vim","src_id":"4911","5":"4911","creation_date":"1135157802","6":"1135157802"},{"0":"1327","vim_version":"6.0","1":"6.0","script_version":"1.3","2":"1.3","version_comment":"Minor updates to some syntactic elements.","3":"Minor updates to some syntactic elements.","package":"msh.vim","4":"msh.vim","src_id":"4905","5":"4905","creation_date":"1135065143","6":"1135065143"},{"0":"1327","vim_version":"6.0","1":"6.0","script_version":"1.2","2":"1.2","version_comment":"Updated to fix a problem with foreach and while","3":"Updated to fix a problem with foreach and while","package":"msh.vim","4":"msh.vim","src_id":"4490","5":"4490","creation_date":"1123927762","6":"1123927762"},{"0":"1327","vim_version":"6.0","1":"6.0","script_version":"1.1","2":"1.1","version_comment":"Initial upload","3":"Initial upload","package":"msh.vim","4":"msh.vim","src_id":"4489","5":"4489","creation_date":"1123844184","6":"1123844184"}]},"1326":{"script_id":"1326","0":"1326","script_name":"Impact","1":"Impact","script_type":"color scheme","2":"color scheme","summary":"Nice dark colorscheme for term\/cterm only","3":"Nice dark colorscheme for term\/cterm only","description":"This is my personal colorscheme designed for long nights with a fullscreen terminal (e.g the one from xfce-extras).\r\nIt is designed for in-term vim usage only and has no gui definitions in it.\r\n\r\nHappy viming!!","4":"This is my personal colorscheme designed for long nights with a fullscreen terminal (e.g the one from xfce-extras).\r\nIt is designed for in-term vim usage only and has no gui definitions in it.\r\n\r\nHappy viming!!","install_details":"","5":"","first_name":"Ren\u00c3\u00a9","6":"Ren\u00c3\u00a9","last_name":"K\u00c3\u00b6cher","7":"K\u00c3\u00b6cher","releases":[{"0":"1326","vim_version":"6.0","1":"6.0","script_version":"0.2","2":"0.2","version_comment":"Removed the ugly brown constants, everything is now in blue and green tones.\r\nThere is also support for transparent background: simply add 'let g:impact_transbg=1' to your vimrc.","3":"Removed the ugly brown constants, everything is now in blue and green tones.\r\nThere is also support for transparent background: simply add 'let g:impact_transbg=1' to your vimrc.","package":"impact.vim","4":"impact.vim","src_id":"4597","5":"4597","creation_date":"1127110210","6":"1127110210"},{"0":"1326","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"impact.vim","4":"impact.vim","src_id":"4481","5":"4481","creation_date":"1123635438","6":"1123635438"}]},"1325":{"script_id":"1325","0":"1325","script_name":"bufferlist.vim","1":"bufferlist.vim","script_type":"utility","2":"utility","summary":"simple, fast, and slick non-disturbing buffer list","3":"simple, fast, and slick non-disturbing buffer list","description":"This script offers a nice buffer list that does not get in your way. Just hit a key to open it, it will \"slide\" in from the left, select the buffer you want to go to, and *swoosh* the list is gone again.\r\n\r\nSee http:\/\/devel.burningsoda.com\/vim\/bufferlist_ani.gif for a short demo.","4":"This script offers a nice buffer list that does not get in your way. Just hit a key to open it, it will \"slide\" in from the left, select the buffer you want to go to, and *swoosh* the list is gone again.\r\n\r\nSee http:\/\/devel.burningsoda.com\/vim\/bufferlist_ani.gif for a short demo.","install_details":"Just copy the file into your ~\/.vim\/plugin folder. And be sure to check out it's contents for some settings. It uses a nice trick to get a \"full colored\" background.","5":"Just copy the file into your ~\/.vim\/plugin folder. And be sure to check out it's contents for some settings. It uses a nice trick to get a \"full colored\" background.","first_name":"Robert","6":"Robert","last_name":"Lillack","7":"Lillack","releases":[{"0":"1325","vim_version":"6.0","1":"6.0","script_version":"1.3","2":"1.3","version_comment":"Add ability to delete buffers using the buffer list by pressing \u00e2\u0080\u0098d\u00e2\u0080\u0099. A feature requested by Stephen Kennedy.","3":"Add ability to delete buffers using the buffer list by pressing \u00e2\u0080\u0098d\u00e2\u0080\u0099. A feature requested by Stephen Kennedy.","package":"bufferlist.vim","4":"bufferlist.vim","src_id":"4544","5":"4544","creation_date":"1125547124","6":"1125547124"},{"0":"1325","vim_version":"6.0","1":"6.0","script_version":"1.2","2":"1.2","version_comment":"two small fixes:\r\n- bufferlist does not mess up your registers anymore (reported by Kingsley Gordon)\r\n- display fix if there are NO file buffers open","3":"two small fixes:\r\n- bufferlist does not mess up your registers anymore (reported by Kingsley Gordon)\r\n- display fix if there are NO file buffers open","package":"bufferlist.vim","4":"bufferlist.vim","src_id":"4530","5":"4530","creation_date":"1125084492","6":"1125084492"},{"0":"1325","vim_version":"6.0","1":"6.0","script_version":"1.1","2":"1.1","version_comment":"added \u00e2\u0080\u009cintelligent\u00e2\u0080\u009d resizing of the buffer list window and cutting of filenames, if still too long. (set g:BufferListMaxWidth to the maximum window width you can tolerate) -- thanks to Kingsley Gordon for the original request.","3":"added \u00e2\u0080\u009cintelligent\u00e2\u0080\u009d resizing of the buffer list window and cutting of filenames, if still too long. (set g:BufferListMaxWidth to the maximum window width you can tolerate) -- thanks to Kingsley Gordon for the original request.","package":"bufferlist.vim","4":"bufferlist.vim","src_id":"4470","5":"4470","creation_date":"1123453095","6":"1123453095"},{"0":"1325","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"bufferlist.vim","4":"bufferlist.vim","src_id":"4458","5":"4458","creation_date":"1123021680","6":"1123021680"}]},"1324":{"script_id":"1324","0":"1324","script_name":"The Stars Color Scheme","1":"The Stars Color Scheme","script_type":"color scheme","2":"color scheme","summary":"A dark scheme","3":"A dark scheme","description":"A dark, but colorful, color scheme.","4":"A dark, but colorful, color scheme.","install_details":"","5":"","first_name":"Michael","6":"Michael","last_name":"Wiseman","7":"Wiseman","releases":[{"0":"1324","vim_version":"7.0","1":"7.0","script_version":"1.0.1","2":"1.0.1","version_comment":"Updated to support CursorLine option and changed Cursor to work with it.  Color scheme still works with Vim 6.","3":"Updated to support CursorLine option and changed Cursor to work with it.  Color scheme still works with Vim 6.","package":"thestars.vim","4":"thestars.vim","src_id":"5513","5":"5513","creation_date":"1144068063","6":"1144068063"},{"0":"1324","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Updated for Vim 7's tab bar and matching parentheses features and modified to look better with most programming languages.  Still works with Vim 6. ","3":"Updated for Vim 7's tab bar and matching parentheses features and modified to look better with most programming languages.  Still works with Vim 6. ","package":"thestars.vim","4":"thestars.vim","src_id":"5488","5":"5488","creation_date":"1143462095","6":"1143462095"},{"0":"1324","vim_version":"6.0","1":"6.0","script_version":"0.51","2":"0.51","version_comment":"Added support for Vim 7 Omni Completion menu and fixed some other details.  Though the omni menu coloring won't work in Vim 6, the rest of it will.","3":"Added support for Vim 7 Omni Completion menu and fixed some other details.  Though the omni menu coloring won't work in Vim 6, the rest of it will.","package":"thestars.vim","4":"thestars.vim","src_id":"4690","5":"4690","creation_date":"1129851591","6":"1129851591"},{"0":"1324","vim_version":"6.0","1":"6.0","script_version":"0.4","2":"0.4","version_comment":"Color tweak.","3":"Color tweak.","package":"thestars.vim","4":"thestars.vim","src_id":"4582","5":"4582","creation_date":"1126686370","6":"1126686370"},{"0":"1324","vim_version":"6.0","1":"6.0","script_version":"0.3","2":"0.3","version_comment":"Another color tweak.","3":"Another color tweak.","package":"thestars.vim","4":"thestars.vim","src_id":"4491","5":"4491","creation_date":"1123932188","6":"1123932188"},{"0":"1324","vim_version":"6.0","1":"6.0","script_version":"0.2","2":"0.2","version_comment":"Minor color tweak.","3":"Minor color tweak.","package":"thestars.vim","4":"thestars.vim","src_id":"4487","5":"4487","creation_date":"1123796590","6":"1123796590"},{"0":"1324","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"thestars.vim","4":"thestars.vim","src_id":"4457","5":"4457","creation_date":"1122987412","6":"1122987412"}]},"1323":{"script_id":"1323","0":"1323","script_name":"advantage","1":"advantage","script_type":"color scheme","2":"color scheme","summary":"Dark theme for us sensitive coders","3":"Dark theme for us sensitive coders","description":"This theme is a modified version of the bluesky color scheme. I liked most of the colors in this theme, however they were a little too bright so I toned it down a little and came up with this darkened version of it.","4":"This theme is a modified version of the bluesky color scheme. I liked most of the colors in this theme, however they were a little too bright so I toned it down a little and came up with this darkened version of it.","install_details":"Same as with any other color scheme","5":"Same as with any other color scheme","first_name":"Joe","6":"Joe","last_name":"Estock","7":"Estock","releases":[{"0":"1323","vim_version":"6.0","1":"6.0","script_version":"0.01","2":"0.01","version_comment":"Initial upload","3":"Initial upload","package":"advantage.vim","4":"advantage.vim","src_id":"4454","5":"4454","creation_date":"1122895935","6":"1122895935"}]},"1322":{"script_id":"1322","0":"1322","script_name":"ps2vsm","1":"ps2vsm","script_type":"syntax","2":"syntax","summary":"PlayStation2 Vector Unit Assembly syntax","3":"PlayStation2 Vector Unit Assembly syntax","description":"This is just a simple PlayStation2 Vector Unit Assembly highlight file for (g)VIM. Unfortuantly it only supports gvim at the moment, since it defines some of its own colours. You are, of course, welcome to modify the file to support normal vim!\r\nIt uses different colours for High and Low instructions, seperates Integer, Floating Point and Special registers by colour, and also highlights destination, broadcast and bit setting extenstions.\r\n\r\nI'm sure it has many bugs, but it works pretty well here, and helps out alot.\r\n\r\nCouple of screenshots for those who don't have a vsm file handy:\r\nhttp:\/\/www.jbit.net\/~jbit\/ps2vsm-dark.png\r\nhttp:\/\/www.jbit.net\/~jbit\/ps2vsm-light.png\r\n\r\nHope this helps somebody!","4":"This is just a simple PlayStation2 Vector Unit Assembly highlight file for (g)VIM. Unfortuantly it only supports gvim at the moment, since it defines some of its own colours. You are, of course, welcome to modify the file to support normal vim!\r\nIt uses different colours for High and Low instructions, seperates Integer, Floating Point and Special registers by colour, and also highlights destination, broadcast and bit setting extenstions.\r\n\r\nI'm sure it has many bugs, but it works pretty well here, and helps out alot.\r\n\r\nCouple of screenshots for those who don't have a vsm file handy:\r\nhttp:\/\/www.jbit.net\/~jbit\/ps2vsm-dark.png\r\nhttp:\/\/www.jbit.net\/~jbit\/ps2vsm-light.png\r\n\r\nHope this helps somebody!","install_details":"Install just like a normal syntax file.","5":"Install just like a normal syntax file.","first_name":"James","6":"James","last_name":"Lee","7":"Lee","releases":[{"0":"1322","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"ps2vsm.vim","4":"ps2vsm.vim","src_id":"4452","5":"4452","creation_date":"1122813620","6":"1122813620"}]},"1321":{"script_id":"1321","0":"1321","script_name":"CSVTK","1":"CSVTK","script_type":"utility","2":"utility","summary":"Tool kit to work with Comma Separated Values files","3":"Tool kit to work with Comma Separated Values files","description":"CSVTK Provides functions and mappings to help working with CSV files or\r\nany files where a separator (e.g. a comma) is used between values and\r\nwhere values can be enclosed between delimiters (e.g. double quotes).\r\nSeparators characters inside delimiters are not considered as separators.\r\n\r\nField numberting starts at 1.\r\n\r\nMappings allow user to:\r\n  * Jump to a specific field,\r\n  * Display the field number of the field under the cursor,\r\n  * Return the value of field (given the field number) on current line or\r\n  specified line,\r\n  * Toggle highlighting for each field (in one or several colors).\r\n\r\nThe highlight will show in the current line and be updated when user \r\nchanges line (the highlight is updated thanks to an autocomand on the \r\nCursorHold event, therefore it is not updated when in insert mode). The \r\nseparator following the field is highlighted as part of the field.\r\n\r\nAlso, a few examples are provided to show how to display the current field\r\nnumber in the status line (so you always know what field you're in) and\r\nhow to fold lines depending on field content.","4":"CSVTK Provides functions and mappings to help working with CSV files or\r\nany files where a separator (e.g. a comma) is used between values and\r\nwhere values can be enclosed between delimiters (e.g. double quotes).\r\nSeparators characters inside delimiters are not considered as separators.\r\n\r\nField numberting starts at 1.\r\n\r\nMappings allow user to:\r\n  * Jump to a specific field,\r\n  * Display the field number of the field under the cursor,\r\n  * Return the value of field (given the field number) on current line or\r\n  specified line,\r\n  * Toggle highlighting for each field (in one or several colors).\r\n\r\nThe highlight will show in the current line and be updated when user \r\nchanges line (the highlight is updated thanks to an autocomand on the \r\nCursorHold event, therefore it is not updated when in insert mode). The \r\nseparator following the field is highlighted as part of the field.\r\n\r\nAlso, a few examples are provided to show how to display the current field\r\nnumber in the status line (so you always know what field you're in) and\r\nhow to fold lines depending on field content.","install_details":"Place in your plugin directory.\r\nLook at the begining of the script for more info.\r\nLook at the mappings near the end of the script, and change as you wish.\r\nLook at the example at the end of the script.\r\n\r\nRequires vimscript#171\r\nOptional but recommended: vimscript#479","5":"Place in your plugin directory.\r\nLook at the begining of the script for more info.\r\nLook at the mappings near the end of the script, and change as you wish.\r\nLook at the example at the end of the script.\r\n\r\nRequires vimscript#171\r\nOptional but recommended: vimscript#479","first_name":"Christophe","6":"Christophe","last_name":"R","7":"R","releases":[{"0":"1321","vim_version":"6.0","1":"6.0","script_version":"1.1","2":"1.1","version_comment":"Added one function and two mappings to jump to the next\/previous highlighted field.\r\nThe script now requires the genUtils.vim script (for the 'CmpByNumber' sort function)","3":"Added one function and two mappings to jump to the next\/previous highlighted field.\r\nThe script now requires the genUtils.vim script (for the 'CmpByNumber' sort function)","package":"csvtk.vim","4":"csvtk.vim","src_id":"4997","5":"4997","creation_date":"1137863333","6":"1137863333"},{"0":"1321","vim_version":"6.0","1":"6.0","script_version":"1.00","2":"1.00","version_comment":"Initial upload","3":"Initial upload","package":"csvtk.vim","4":"csvtk.vim","src_id":"4451","5":"4451","creation_date":"1122763218","6":"1122763218"}]},"1320":{"script_id":"1320","0":"1320","script_name":"Dynamic Keyword Highlighting","1":"Dynamic Keyword Highlighting","script_type":"utility","2":"utility","summary":"Color-highlighted multi-search trail","3":"Color-highlighted multi-search trail","description":"When inspecting text, often highlighting the current search keyword isn't enough. \r\nThis script allows you to highlight keywords and search patterns in different colors.\r\nThere are a few ways to use this functionality.\r\n\r\n1) visual mode keyword selection\r\nUse visual mode to select text and press <CTRL>h\r\nThe next available color will be used to highlight the keyword.\r\n<CTRL>h without a visual mode highlight releases the last highlight.\r\n\r\n2) search pattern selection\r\nPerform a regular \"\/\" search, and the press <CTRL>j\r\nThe next available color will be used to highlight matches.\r\n<CTRL>h without a visual mode highlight releases the last highlight.\r\n\r\n3) search pattern backtracking\r\nThe last highlighted word is set as the current search pattern.\r\nThis allows you to backtrack searches easily. For example,\r\n- search \"keyword\" \r\n\/keyword\r\n- remember search \r\n<CTRL>j\r\n- search \"pattern\"\r\n\/pattern\r\n- remember search\r\n<CTRL>j\r\n- At this point, repeating search with just \"\/\" will search \"pattern\".\r\n   Use <CTRL>h without any visual highlight to backtrack.\r\n  Repeating search with just \"\/\" will now search \"keyword\".\r\n","4":"When inspecting text, often highlighting the current search keyword isn't enough. \r\nThis script allows you to highlight keywords and search patterns in different colors.\r\nThere are a few ways to use this functionality.\r\n\r\n1) visual mode keyword selection\r\nUse visual mode to select text and press <CTRL>h\r\nThe next available color will be used to highlight the keyword.\r\n<CTRL>h without a visual mode highlight releases the last highlight.\r\n\r\n2) search pattern selection\r\nPerform a regular \"\/\" search, and the press <CTRL>j\r\nThe next available color will be used to highlight matches.\r\n<CTRL>h without a visual mode highlight releases the last highlight.\r\n\r\n3) search pattern backtracking\r\nThe last highlighted word is set as the current search pattern.\r\nThis allows you to backtrack searches easily. For example,\r\n- search \"keyword\" \r\n\/keyword\r\n- remember search \r\n<CTRL>j\r\n- search \"pattern\"\r\n\/pattern\r\n- remember search\r\n<CTRL>j\r\n- At this point, repeating search with just \"\/\" will search \"pattern\".\r\n   Use <CTRL>h without any visual highlight to backtrack.\r\n  Repeating search with just \"\/\" will now search \"keyword\".\r\n","install_details":"Copy code into your .vimrc","5":"Copy code into your .vimrc","first_name":"eiji","6":"eiji","last_name":"kumiai","7":"kumiai","releases":[{"0":"1320","vim_version":"7.0","1":"7.0","script_version":"1.9","2":"1.9","version_comment":"- revised color scheme so that text can be seen clearly\r\n- increased number of highlights from 26 to 35","3":"- revised color scheme so that text can be seen clearly\r\n- increased number of highlights from 26 to 35","package":"dysyn_vimrc.txt","4":"dysyn_vimrc.txt","src_id":"24772","5":"24772","creation_date":"1480437102","6":"1480437102"},{"0":"1320","vim_version":"7.0","1":"7.0","script_version":"1.8","2":"1.8","version_comment":"New feature : search backtracking ","3":"New feature : search backtracking ","package":"dysyn_vimrc.txt","4":"dysyn_vimrc.txt","src_id":"12158","5":"12158","creation_date":"1264124925","6":"1264124925"},{"0":"1320","vim_version":"7.0","1":"7.0","script_version":"1.5","2":"1.5","version_comment":"- <ctrl-j> highlights current search pattern. \r\n  perform normal search and use <ctrl> to do multiple regex patterns.\r\n- cterm colors now supported\r\n- up to 25 search items now supported\r\n- highlight across buffers\r\n- <ctrl-h> on regex characters escaped\r\n","3":"- <ctrl-j> highlights current search pattern. \r\n  perform normal search and use <ctrl> to do multiple regex patterns.\r\n- cterm colors now supported\r\n- up to 25 search items now supported\r\n- highlight across buffers\r\n- <ctrl-h> on regex characters escaped\r\n","package":"_vimrc","4":"_vimrc","src_id":"11602","5":"11602","creation_date":"1256607649","6":"1256607649"},{"0":"1320","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"dynamicsyntax.vim","4":"dynamicsyntax.vim","src_id":"4448","5":"4448","creation_date":"1122597978","6":"1122597978"}]},"1319":{"script_id":"1319","0":"1319","script_name":"perlprove.vim","1":"perlprove.vim","script_type":"utility","2":"utility","summary":"Perl unittest compiler. Parses Test::Harness' `prove` output.","3":"Perl unittest compiler. Parses Test::Harness' `prove` output.","description":"Runs the Test::Harness 'prove' utility and formats the errors. It is implemented as a compiler, so it's invoked with :make and the usual error navigation commands work.\r\n\r\nUsage:\r\n:make  - runs prove for the testfile you are in. Failed tests and perl errors are recognized by vim and it jumps to the first error (failed test or perl syntax error). Use :cn and :cp to go to the next resp. previous error. :cl gives a list of all the errors and :cc <number> jumps to a specific error message. See the 'quickfix' part in the vim manual.\r\n:make <arguments>  - runs prove with the argument you give. It does not add the filename of the current test. Useful to run all your test, eq: ':make *t', or ':make t'\r\n","4":"Runs the Test::Harness 'prove' utility and formats the errors. It is implemented as a compiler, so it's invoked with :make and the usual error navigation commands work.\r\n\r\nUsage:\r\n:make  - runs prove for the testfile you are in. Failed tests and perl errors are recognized by vim and it jumps to the first error (failed test or perl syntax error). Use :cn and :cp to go to the next resp. previous error. :cl gives a list of all the errors and :cc <number> jumps to a specific error message. See the 'quickfix' part in the vim manual.\r\n:make <arguments>  - runs prove with the argument you give. It does not add the filename of the current test. Useful to run all your test, eq: ':make *t', or ':make t'\r\n","install_details":"Copy perlprove.vim to ~\/.vim\/compiler\r\nAdd to your .vimrc:\r\nau BufRead,BufNewFile *.t set filetype=perl | compiler perlprove","5":"Copy perlprove.vim to ~\/.vim\/compiler\r\nAdd to your .vimrc:\r\nau BufRead,BufNewFile *.t set filetype=perl | compiler perlprove","first_name":"Harmen","6":"Harmen","last_name":"Bus","7":"Bus","releases":[{"0":"1319","vim_version":"6.0","1":"6.0","script_version":"2","2":"2","version_comment":"'-l' argument to prove added.\r\nFixed some comments.","3":"'-l' argument to prove added.\r\nFixed some comments.","package":"perlprove.vim","4":"perlprove.vim","src_id":"4450","5":"4450","creation_date":"1122725328","6":"1122725328"},{"0":"1319","vim_version":"6.0","1":"6.0","script_version":"1","2":"1","version_comment":"Initial upload","3":"Initial upload","package":"perlprove.vim","4":"perlprove.vim","src_id":"4446","5":"4446","creation_date":"1122535766","6":"1122535766"}]},"1318":{"script_id":"1318","0":"1318","script_name":"snippetsEmu","1":"snippetsEmu","script_type":"utility","2":"utility","summary":"An attempt to emulate TextMate's snippet expansion","3":"An attempt to emulate TextMate's snippet expansion","description":"***** IMPORTANT *****\r\nThe plugin has now been split into two separate vimballs. The plugin itself and the bundles. This was done because bundles were updated a lot more often than the plugin itself.\r\n\r\nPrevious users of the plugin should delete the old file when upgrading to 1.0. The name of the file changed in 0.6 and so you'll end up with two versions when unpacking the file. Remove the old version \"snippetEmu.vim\" from the plugin directory. The new version is called \"snippetsEmu.vim\". Note the extra 's'\r\n\r\n\r\nHomepage: http:\/\/slipperysnippets.blogspot.com\/\r\nIssue tracker: http:\/\/code.google.com\/p\/snippetsemu\/issues\/list\r\n\r\nPlease email me bugs or create them in the issue tracker.\r\n\r\nThis file contains some simple functions that attempt to emulate some of the behaviour of 'Snippets' from the OS X editor TextMate, in particular the variable bouncing and replacement behaviour.\r\n\r\nDIVING IN:\r\n\r\nInstall the plugin, start a new perl file (as an example) and type the following in insert mode:\r\n\r\nfor<tab><tab><tab><tab>\r\n\r\nYou'll see the text expand and the jumping in action. Try the same again but this time type a new value for 'var' once it is selected. I.e.\r\n\r\nfor<tab>test<tab><tab><tab>\r\n\r\nNotice how all the 'var's are replaced with 'test'.\r\n\r\nCheck out the bundles and the docs for more examples of what can be done.\r\n\r\n*IMPORTANT*\r\n\r\nIf you have any questions, suggestions, problems or criticisms about the plugin then please, please email me and I will do the best to help.","4":"***** IMPORTANT *****\r\nThe plugin has now been split into two separate vimballs. The plugin itself and the bundles. This was done because bundles were updated a lot more often than the plugin itself.\r\n\r\nPrevious users of the plugin should delete the old file when upgrading to 1.0. The name of the file changed in 0.6 and so you'll end up with two versions when unpacking the file. Remove the old version \"snippetEmu.vim\" from the plugin directory. The new version is called \"snippetsEmu.vim\". Note the extra 's'\r\n\r\n\r\nHomepage: http:\/\/slipperysnippets.blogspot.com\/\r\nIssue tracker: http:\/\/code.google.com\/p\/snippetsemu\/issues\/list\r\n\r\nPlease email me bugs or create them in the issue tracker.\r\n\r\nThis file contains some simple functions that attempt to emulate some of the behaviour of 'Snippets' from the OS X editor TextMate, in particular the variable bouncing and replacement behaviour.\r\n\r\nDIVING IN:\r\n\r\nInstall the plugin, start a new perl file (as an example) and type the following in insert mode:\r\n\r\nfor<tab><tab><tab><tab>\r\n\r\nYou'll see the text expand and the jumping in action. Try the same again but this time type a new value for 'var' once it is selected. I.e.\r\n\r\nfor<tab>test<tab><tab><tab>\r\n\r\nNotice how all the 'var's are replaced with 'test'.\r\n\r\nCheck out the bundles and the docs for more examples of what can be done.\r\n\r\n*IMPORTANT*\r\n\r\nIf you have any questions, suggestions, problems or criticisms about the plugin then please, please email me and I will do the best to help.","install_details":"Firstly create an 'after\/ftplugin' directory in your vim home (e.g. ~\/.vim\/after\/ftplugin under unix or vimfiles\/after\/ftplugin under Windows). This is required as Vimball sometimes does not create it for some reason.\r\n\r\nDownload the plugin vimball (and the bundle vimball if you would like the default snippets).\r\n\r\nNow open the Vimball(s) with Vim and follow the instructions (source the vimball to install everything). Vimball should create the help tags. Do a :helptags on your doc directory if it hasn't.\r\n\r\nEnjoy","5":"Firstly create an 'after\/ftplugin' directory in your vim home (e.g. ~\/.vim\/after\/ftplugin under unix or vimfiles\/after\/ftplugin under Windows). This is required as Vimball sometimes does not create it for some reason.\r\n\r\nDownload the plugin vimball (and the bundle vimball if you would like the default snippets).\r\n\r\nNow open the Vimball(s) with Vim and follow the instructions (source the vimball to install everything). Vimball should create the help tags. Do a :helptags on your doc directory if it hasn't.\r\n\r\nEnjoy","first_name":"Felix","6":"Felix","last_name":"Ingram","7":"Ingram","releases":[{"0":"1318","vim_version":"7.0","1":"7.0","script_version":"1.2.3","2":"1.2.3","version_comment":"Fixed jumping bug which caused problems with tags between two named tags being missed out. (really, really uploaded new version)","3":"Fixed jumping bug which caused problems with tags between two named tags being missed out. (really, really uploaded new version)","package":"snippy_plugin.vba","4":"snippy_plugin.vba","src_id":"8450","5":"8450","creation_date":"1205393615","6":"1205393615"},{"0":"1318","vim_version":"7.0","1":"7.0","script_version":"1.2","2":"1.2","version_comment":"Small fix to php bundle. 'php' trigger is now 'phpp'. Previous version could too easily cause conflicts when using the 'incl' snippet.","3":"Small fix to php bundle. 'php' trigger is now 'phpp'. Previous version could too easily cause conflicts when using the 'incl' snippet.","package":"snippy_bundles.vba","4":"snippy_bundles.vba","src_id":"8443","5":"8443","creation_date":"1205376896","6":"1205376896"},{"0":"1318","vim_version":"7.0","1":"7.0","script_version":"1.1","2":"1.1","version_comment":"Updates to the C and HTML bundles","3":"Updates to the C and HTML bundles","package":"snippy_bundles.vba","4":"snippy_bundles.vba","src_id":"8386","5":"8386","creation_date":"1204537363","6":"1204537363"},{"0":"1318","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Filetype plugins for snippetsEmu","3":"Filetype plugins for snippetsEmu","package":"snippy_bundles.vba","4":"snippy_bundles.vba","src_id":"8348","5":"8348","creation_date":"1203933302","6":"1203933302"},{"0":"1318","vim_version":"7.0","1":"7.0","script_version":"1.2.2","2":"1.2.2","version_comment":"Bug fix to plugin. Annoying window jumping sorted out. Bundles are now in a separate vimball.","3":"Bug fix to plugin. Annoying window jumping sorted out. Bundles are now in a separate vimball.","package":"snippy_plugin.vba","4":"snippy_plugin.vba","src_id":"8347","5":"8347","creation_date":"1203933259","6":"1203933259"},{"0":"1318","vim_version":"7.0","1":"7.0","script_version":"1.2.1","2":"1.2.1","version_comment":"VBA file now has unix fileformat, so things should be working better. Vimball has also added fold markers, which aren't backwards compatible, so I've removed them as well.","3":"VBA file now has unix fileformat, so things should be working better. Vimball has also added fold markers, which aren't backwards compatible, so I've removed them as well.","package":"snippetsemu1.2.1.vba","4":"snippetsemu1.2.1.vba","src_id":"7735","5":"7735","creation_date":"1191159511","6":"1191159511"},{"0":"1318","vim_version":"7.0","1":"7.0","script_version":"1.2","2":"1.2","version_comment":"Finally released new version. Big change: No more messing with iskeyword. Other stuff - Commands with autocomplete, new commands for creating snippets, updated bundles. Be sure to read the docs to see what's available.","3":"Finally released new version. Big change: No more messing with iskeyword. Other stuff - Commands with autocomplete, new commands for creating snippets, updated bundles. Be sure to read the docs to see what's available.","package":"snippetsemu1.2.vba","4":"snippetsemu1.2.vba","src_id":"7732","5":"7732","creation_date":"1191151422","6":"1191151422"},{"0":"1318","vim_version":"7.0","1":"7.0","script_version":"1.1","2":"1.1","version_comment":"New version contains several bug fixes, reverts start and end tags to more 'friendly' settings and tries to address indenting issues. Snippets must now define their own 'local' indenting. Make sure you create the after\/ftplugin directories as described in the installation instructions.","3":"New version contains several bug fixes, reverts start and end tags to more 'friendly' settings and tries to address indenting issues. Snippets must now define their own 'local' indenting. Make sure you create the after\/ftplugin directories as described in the installation instructions.","package":"snippetsemu1_1.vba","4":"snippetsemu1_1.vba","src_id":"6951","5":"6951","creation_date":"1175767356","6":"1175767356"},{"0":"1318","vim_version":"7.0","1":"7.0","script_version":"1.0.1","2":"1.0.1","version_comment":"Even more super 1.0.1 version with Unix line endings on the Vimball so things install properly on *nix.","3":"Even more super 1.0.1 version with Unix line endings on the Vimball so things install properly on *nix.","package":"SnippetsEmu_1.0.1.vba","4":"SnippetsEmu_1.0.1.vba","src_id":"6561","5":"6561","creation_date":"1167359655","6":"1167359655"},{"0":"1318","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Super new 1.0 version with many new features and improvements. New bundles also included.","3":"Super new 1.0 version with many new features and improvements. New bundles also included.","package":"SnippetsEmu_1.0.vba","4":"SnippetsEmu_1.0.vba","src_id":"6558","5":"6558","creation_date":"1167299214","6":"1167299214"},{"0":"1318","vim_version":"7.0","1":"7.0","script_version":"0.6.1","2":"0.6.1","version_comment":"Quick fix changes the line endings for the VBA to UNIX which should hopefully stop some problems people are having","3":"Quick fix changes the line endings for the VBA to UNIX which should hopefully stop some problems people are having","package":"snippetsEmu0.6.1.vba","4":"snippetsEmu0.6.1.vba","src_id":"6477","5":"6477","creation_date":"1164707762","6":"1164707762"},{"0":"1318","vim_version":"7.0","1":"7.0","script_version":"0.6","2":"0.6","version_comment":"Bugs fixes as per usual but this new version includes a set of snippets bundles for use with various filetypes. Plugin is now a VimBall so everything is in one file.","3":"Bugs fixes as per usual but this new version includes a set of snippets bundles for use with various filetypes. Plugin is now a VimBall so everything is in one file.","package":"snippetsEmu0.6.vba","4":"snippetsEmu0.6.vba","src_id":"6468","5":"6468","creation_date":"1164451152","6":"1164451152"},{"0":"1318","vim_version":"7.0","1":"7.0","script_version":"0.5.6","2":"0.5.6","version_comment":"Fixed several bugs from the last version including random bug which prevented snippets from starting with 's'.","3":"Fixed several bugs from the last version including random bug which prevented snippets from starting with 's'.","package":"snippetEmu0.5.6.vim","4":"snippetEmu0.5.6.vim","src_id":"6108","5":"6108","creation_date":"1156841389","6":"1156841389"},{"0":"1318","vim_version":"7.0","1":"7.0","script_version":"0.5.5","2":"0.5.5","version_comment":"Fixed various bugs: s:search_str not being defined or being buffer specific and command tag execution not working with two tags on the same line.","3":"Fixed various bugs: s:search_str not being defined or being buffer specific and command tag execution not working with two tags on the same line.","package":"snippetEmu0.5.5.vim","4":"snippetEmu0.5.5.vim","src_id":"6068","5":"6068","creation_date":"1155519260","6":"1155519260"},{"0":"1318","vim_version":"7.0","1":"7.0","script_version":"0.5.4","2":"0.5.4","version_comment":"TextMate compatibile mode now works under linux.","3":"TextMate compatibile mode now works under linux.","package":"snippetEmu0.5.4.vim","4":"snippetEmu0.5.4.vim","src_id":"5987","5":"5987","creation_date":"1153797167","6":"1153797167"},{"0":"1318","vim_version":"7.0","1":"7.0","script_version":"0.5.3","2":"0.5.3","version_comment":"Bug fixes. Things are a lot better behaved. Edge cases should (should) work a lot better now. Highly recommended upgrade.","3":"Bug fixes. Things are a lot better behaved. Edge cases should (should) work a lot better now. Highly recommended upgrade.","package":"snippetEmu0.5.3.vim","4":"snippetEmu0.5.3.vim","src_id":"5944","5":"5944","creation_date":"1152719059","6":"1152719059"},{"0":"1318","vim_version":"7.0","1":"7.0","script_version":"0.5.2","2":"0.5.2","version_comment":"Minor bug fix. Textmate compatible mode did not allow quotes in expansions. Fixed","3":"Minor bug fix. Textmate compatible mode did not allow quotes in expansions. Fixed","package":"snippetEmu0.5.2.vim","4":"snippetEmu0.5.2.vim","src_id":"5916","5":"5916","creation_date":"1152016939","6":"1152016939"},{"0":"1318","vim_version":"7.0","1":"7.0","script_version":"0.5.1","2":"0.5.1","version_comment":"This new version adds some bug fixes to the last release and adds the new functionality of being able to define multicharacter start and end tags. It is now easier to define tags which work across multiple languages.","3":"This new version adds some bug fixes to the last release and adds the new functionality of being able to define multicharacter start and end tags. It is now easier to define tags which work across multiple languages.","package":"snippetEmu0.5.1.vim","4":"snippetEmu0.5.1.vim","src_id":"5912","5":"5912","creation_date":"1151937639","6":"1151937639"},{"0":"1318","vim_version":"7.0","1":"7.0","script_version":"0.5.0","2":"0.5.0","version_comment":"This new version adds TextMate style expansions: snippets are not expanded automatically. The user must press Tab for a snippet to be expanded. Tabbing will jump between tags or insert a <Tab> if no tags are active. \r\n\r\nThe tag syntax has changed. Default values are not supported anymore: use the tag's name instead. Commands can now be added in the first tag and unnamed tags can include commands. \r\n\r\nThis is a test release: please send bug reports.","3":"This new version adds TextMate style expansions: snippets are not expanded automatically. The user must press Tab for a snippet to be expanded. Tabbing will jump between tags or insert a <Tab> if no tags are active. \r\n\r\nThe tag syntax has changed. Default values are not supported anymore: use the tag's name instead. Commands can now be added in the first tag and unnamed tags can include commands. \r\n\r\nThis is a test release: please send bug reports.","package":"snippetEmu0.5.0.vim","4":"snippetEmu0.5.0.vim","src_id":"5907","5":"5907","creation_date":"1151772780","6":"1151772780"},{"0":"1318","vim_version":"6.0","1":"6.0","script_version":"0.3.6","2":"0.3.6","version_comment":"Minor bug fix.  Replacement values modified by commands would be passed to future commands in their modified form, rather than with the original replacement value.","3":"Minor bug fix.  Replacement values modified by commands would be passed to future commands in their modified form, rather than with the original replacement value.","package":"snippetEmu.vim","4":"snippetEmu.vim","src_id":"4977","5":"4977","creation_date":"1137373332","6":"1137373332"},{"0":"1318","vim_version":"6.0","1":"6.0","script_version":"0.3.5","2":"0.3.5","version_comment":"Fundamental change to the way the new commands feature works.  The command is now 'executed' and the result placed in the variable @z.  The intention is for the command to be a function call rather than a standard command.  I.e. using substitute() rather than :s\/\/\/.  The value to be replaced is available to the function in @z (previous values of the variable are kept and restored once the command has been executed).  See the updated docs for examples.","3":"Fundamental change to the way the new commands feature works.  The command is now 'executed' and the result placed in the variable @z.  The intention is for the command to be a function call rather than a standard command.  I.e. using substitute() rather than :s\/\/\/.  The value to be replaced is available to the function in @z (previous values of the variable are kept and restored once the command has been executed).  See the updated docs for examples.","package":"snippetEmu.vim","4":"snippetEmu.vim","src_id":"4969","5":"4969","creation_date":"1137230271","6":"1137230271"},{"0":"1318","vim_version":"6.0","1":"6.0","script_version":"0.3.1","2":"0.3.1","version_comment":"Bug fix - Non-greedy matching is now done on the command searching.","3":"Bug fix - Non-greedy matching is now done on the command searching.","package":"snippetEmu.vim","4":"snippetEmu.vim","src_id":"4962","5":"4962","creation_date":"1137051496","6":"1137051496"},{"0":"1318","vim_version":"6.0","1":"6.0","script_version":"0.3","2":"0.3","version_comment":"New version allows commands to be included in named tags.  Experimental version - does not appear to break older functionality, however.","3":"New version allows commands to be included in named tags.  Experimental version - does not appear to break older functionality, however.","package":"snippetEmu.vim","4":"snippetEmu.vim","src_id":"4959","5":"4959","creation_date":"1136954126","6":"1136954126"},{"0":"1318","vim_version":"6.0","1":"6.0","script_version":"0.2.5","2":"0.2.5","version_comment":"Tag delimiters can now be set with autocommands to allow for different filetypes.  I.e. '<' and '>' for programming and '@' for HTML.","3":"Tag delimiters can now be set with autocommands to allow for different filetypes.  I.e. '<' and '>' for programming and '@' for HTML.","package":"snippetEmu.vim","4":"snippetEmu.vim","src_id":"4947","5":"4947","creation_date":"1136439519","6":"1136439519"},{"0":"1318","vim_version":"6.0","1":"6.0","script_version":"0.2.4","2":"0.2.4","version_comment":"Fixed a bug where certain tags were not recognised","3":"Fixed a bug where certain tags were not recognised","package":"snippetEmu.vim","4":"snippetEmu.vim","src_id":"4946","5":"4946","creation_date":"1136427805","6":"1136427805"},{"0":"1318","vim_version":"6.0","1":"6.0","script_version":"0.2.3","2":"0.2.3","version_comment":"Now works with autoindenting","3":"Now works with autoindenting","package":"snippetEmu.vim","4":"snippetEmu.vim","src_id":"4940","5":"4940","creation_date":"1136367738","6":"1136367738"},{"0":"1318","vim_version":"6.0","1":"6.0","script_version":"0.2.2","2":"0.2.2","version_comment":"Better behaved.  Couple of bug fixes.","3":"Better behaved.  Couple of bug fixes.","package":"snippetEmu.vim","4":"snippetEmu.vim","src_id":"4480","5":"4480","creation_date":"1123579943","6":"1123579943"},{"0":"1318","vim_version":"6.0","1":"6.0","script_version":"0.2.1","2":"0.2.1","version_comment":"Added check for the default key combo so that the user's settings aren't clobbered.","3":"Added check for the default key combo so that the user's settings aren't clobbered.","package":"snippetEmu.vim","4":"snippetEmu.vim","src_id":"4479","5":"4479","creation_date":"1123554071","6":"1123554071"},{"0":"1318","vim_version":"6.0","1":"6.0","script_version":"0.2","2":"0.2","version_comment":"I've given this a full point release as it's a major rewrite.  Start and end tags can now be defined and default values can also be used.","3":"I've given this a full point release as it's a major rewrite.  Start and end tags can now be defined and default values can also be used.","package":"snippetEmu.vim","4":"snippetEmu.vim","src_id":"4471","5":"4471","creation_date":"1123473192","6":"1123473192"},{"0":"1318","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"snippetEmu.vim","4":"snippetEmu.vim","src_id":"4444","5":"4444","creation_date":"1122349844","6":"1122349844"}]},"1317":{"script_id":"1317","0":"1317","script_name":"bwUtility.vim","1":"bwUtility.vim","script_type":"utility","2":"utility","summary":"This script provides some trivial functionalities","3":"This script provides some trivial functionalities","description":"  This script provides following trivial functionalities you can used\r\nin your own scripts:\r\n  - open a console in the current working directory.\r\n  - remove trailing spaces.\r\n  - insert date. This is only available via menu entry.\r\n\r\n  Once the script is installed, it automatically add a menu named\r\n'bwUtility' via which you can access all functins of this script.","4":"  This script provides following trivial functionalities you can used\r\nin your own scripts:\r\n  - open a console in the current working directory.\r\n  - remove trailing spaces.\r\n  - insert date. This is only available via menu entry.\r\n\r\n  Once the script is installed, it automatically add a menu named\r\n'bwUtility' via which you can access all functins of this script.","install_details":"Drop the script to your plugin directory.","5":"Drop the script to your plugin directory.","first_name":"Bruce","6":"Bruce","last_name":"Who","7":"Who","releases":[{"0":"1317","vim_version":"6.0","1":"6.0","script_version":"1.3","2":"1.3","version_comment":"add new menu items: a)break long lines for current buffer according to 'textwidth'; b)break long lines for all buffers.","3":"add new menu items: a)break long lines for current buffer according to 'textwidth'; b)break long lines for all buffers.","package":"bwUtility.vim","4":"bwUtility.vim","src_id":"4507","5":"4507","creation_date":"1124650277","6":"1124650277"},{"0":"1317","vim_version":"6.0","1":"6.0","script_version":"1.1","2":"1.1","version_comment":"Initial upload","3":"Initial upload","package":"bwUtility.vim","4":"bwUtility.vim","src_id":"4443","5":"4443","creation_date":"1122314646","6":"1122314646"}]},"1316":{"script_id":"1316","0":"1316","script_name":"bwHomeEndAdv.vim","1":"bwHomeEndAdv.vim","script_type":"utility","2":"utility","summary":"This script enhances the <Home> and <End> in both normal mode and insert mode","3":"This script enhances the <Home> and <End> in both normal mode and insert mode","description":"Description:\r\n  This script enhances the <Home> and <End> key in both normal mode and\r\n  insert mode. \r\n\r\n  <Home> is enhanced to behave like in Visual C++, you can use <Home> to\r\n  jump between the first column and the first non-space character of a\r\n  line.\r\n\r\n  Besides, <End> is also enhanced and can be used to jump between the last\r\n  column and the last non-space character of a line.","4":"Description:\r\n  This script enhances the <Home> and <End> key in both normal mode and\r\n  insert mode. \r\n\r\n  <Home> is enhanced to behave like in Visual C++, you can use <Home> to\r\n  jump between the first column and the first non-space character of a\r\n  line.\r\n\r\n  Besides, <End> is also enhanced and can be used to jump between the last\r\n  column and the last non-space character of a line.","install_details":"Drop the script to your plugin directory.","5":"Drop the script to your plugin directory.","first_name":"Bruce","6":"Bruce","last_name":"Who","7":"Who","releases":[{"0":"1316","vim_version":"6.0","1":"6.0","script_version":"1.3","2":"1.3","version_comment":"- Bug fix: After Entering VIM, and press <End> for the first time while the cursor is already at the end of the line, an error occurs.\r\n- add <silent> to each mapping to make it behave like normal <Home> & <End>.\r\nThanks to Andrzej Zaborowski who reported the bug and gave me a patch, and also gave me the suggestion.","3":"- Bug fix: After Entering VIM, and press <End> for the first time while the cursor is already at the end of the line, an error occurs.\r\n- add <silent> to each mapping to make it behave like normal <Home> & <End>.\r\nThanks to Andrzej Zaborowski who reported the bug and gave me a patch, and also gave me the suggestion.","package":"bwHomeEndAdv.vim","4":"bwHomeEndAdv.vim","src_id":"4517","5":"4517","creation_date":"1124996022","6":"1124996022"},{"0":"1316","vim_version":"6.0","1":"6.0","script_version":"1.2","2":"1.2","version_comment":"Initial upload","3":"Initial upload","package":"bwHomeEndAdv.vim","4":"bwHomeEndAdv.vim","src_id":"4442","5":"4442","creation_date":"1122229725","6":"1122229725"}]},"1315":{"script_id":"1315","0":"1315","script_name":"udvm.vim","1":"udvm.vim","script_type":"syntax","2":"syntax","summary":"highlights files containing assembly for UDVM","3":"highlights files containing assembly for UDVM","description":"Universal Decompresor Virtual Machine is defined in RFC3320 (SigComp). \r\nIt has an assembly language whose definition can be found in the draft draft-ietf-rohc-sigcomp-user-guide-01.\r\n\r\n","4":"Universal Decompresor Virtual Machine is defined in RFC3320 (SigComp). \r\nIt has an assembly language whose definition can be found in the draft draft-ietf-rohc-sigcomp-user-guide-01.\r\n\r\n","install_details":"Edit your .vimrc, myfiletypefile and mysyntaxfile accordingly.\r\nFor examples on how to do it please see the vim helpfiles.","5":"Edit your .vimrc, myfiletypefile and mysyntaxfile accordingly.\r\nFor examples on how to do it please see the vim helpfiles.","first_name":"Cristian","6":"Cristian","last_name":"Constantin","7":"Constantin","releases":[{"0":"1315","vim_version":"5.7","1":"5.7","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"udvm.vim","4":"udvm.vim","src_id":"4439","5":"4439","creation_date":"1121746676","6":"1121746676"}]},"1314":{"script_id":"1314","0":"1314","script_name":"asmM6502.vim","1":"asmM6502.vim","script_type":"syntax","2":"syntax","summary":"MOS 6502 Assembly syntax","3":"MOS 6502 Assembly syntax","description":"Syntax for the 6502, included \\'Sally\\' (Atari8) ops","4":"Syntax for the 6502, included \\'Sally\\' (Atari8) ops","install_details":"put in syntax dir, :so, or use any other method from your asm.vim","5":"put in syntax dir, :so, or use any other method from your asm.vim","first_name":"Oyd E","6":"Oyd E","last_name":"Leven","7":"Leven","releases":[{"0":"1314","vim_version":"6.0","1":"6.0","script_version":"0.01","2":"0.01","version_comment":"Initial upload","3":"Initial upload","package":"asmM6502.vim","4":"asmM6502.vim","src_id":"4435","5":"4435","creation_date":"1121369147","6":"1121369147"}]},"1313":{"script_id":"1313","0":"1313","script_name":"bwftmenu.vim","1":"bwftmenu.vim","script_type":"utility","2":"utility","summary":"help you make a menu only for buffers with a certain filetype","3":"help you make a menu only for buffers with a certain filetype","description":"Description:\r\n  You can use This script to help you make a menu which only appears when  you are editing buffers with a certain filetype. You can use this script  to make menus in your ftplugin scripts.\r\n\r\n  The menu is automatically made once you enter a buffer whose  filetype is specified. And if you switch to another buffer with a  different filetype, the revious menu is automatically deleted.\r\n\r\nUsage:\r\n  In your ftplugin scripts, follow these steps:\r\n  1. write a function which creates a menu. The function should not\r\n     start with s: or <SID>.\r\n  2. call BW_RegisterFTMenu function which is the only function provided by this script\r\n  That's all.\r\n\r\n  Here is an example. I want to create a menu only for python files,  so I create a function in my ftplugin\/python.vim:\r\n\r\n  function MakeFTMenu_python\r\n    amenu 8000.11 Python.check :echo 'check python script'\r\n    amenu 8000.12 Python.run :echo 'run python script'\r\n  endfunction\r\n\r\n  and then, add this statement to the same .vim file:\r\n\r\n  call BW_RegisterFTMenu('python','Python','MakeFTMenu_python')\r\n\r\n  Note: the second parameter MUST be the same with the name of the menu\r\n        which you created in MakeFTMenu_python function.\r\n","4":"Description:\r\n  You can use This script to help you make a menu which only appears when  you are editing buffers with a certain filetype. You can use this script  to make menus in your ftplugin scripts.\r\n\r\n  The menu is automatically made once you enter a buffer whose  filetype is specified. And if you switch to another buffer with a  different filetype, the revious menu is automatically deleted.\r\n\r\nUsage:\r\n  In your ftplugin scripts, follow these steps:\r\n  1. write a function which creates a menu. The function should not\r\n     start with s: or <SID>.\r\n  2. call BW_RegisterFTMenu function which is the only function provided by this script\r\n  That's all.\r\n\r\n  Here is an example. I want to create a menu only for python files,  so I create a function in my ftplugin\/python.vim:\r\n\r\n  function MakeFTMenu_python\r\n    amenu 8000.11 Python.check :echo 'check python script'\r\n    amenu 8000.12 Python.run :echo 'run python script'\r\n  endfunction\r\n\r\n  and then, add this statement to the same .vim file:\r\n\r\n  call BW_RegisterFTMenu('python','Python','MakeFTMenu_python')\r\n\r\n  Note: the second parameter MUST be the same with the name of the menu\r\n        which you created in MakeFTMenu_python function.\r\n","install_details":"Installation:\r\n  Just drop the script to your plugin directory.\r\n\r\nPrerequisite:\r\n  This script is written in pure vim script and does not depend on other  vim scripts.\r\n","5":"Installation:\r\n  Just drop the script to your plugin directory.\r\n\r\nPrerequisite:\r\n  This script is written in pure vim script and does not depend on other  vim scripts.\r\n","first_name":"Bruce","6":"Bruce","last_name":"Who","7":"Who","releases":[{"0":"1313","vim_version":"6.0","1":"6.0","script_version":"1.3","2":"1.3","version_comment":"bug fix","3":"bug fix","package":"bwftmenu.vim","4":"bwftmenu.vim","src_id":"4441","5":"4441","creation_date":"1122228754","6":"1122228754"}]},"1312":{"script_id":"1312","0":"1312","script_name":"vimplate","1":"vimplate","script_type":"utility","2":"utility","summary":"Template-Toolkit support for Vim","3":"Template-Toolkit support for Vim","description":"Please use this page: http:\/\/www.vim.org\/scripts\/script.php?script_id=1311","4":"Please use this page: http:\/\/www.vim.org\/scripts\/script.php?script_id=1311","install_details":"","5":"","first_name":"Urs","6":"Urs","last_name":"Stotz","7":"Stotz","releases":[{"0":"1312","vim_version":"6.0","1":"6.0","script_version":"0.2.1","2":"0.2.1","version_comment":"Initial upload","3":"Initial upload","package":"vimplate-0.2.1.tar.gz","4":"vimplate-0.2.1.tar.gz","src_id":"4418","5":"4418","creation_date":"1120900226","6":"1120900226"}]},"1311":{"script_id":"1311","0":"1311","script_name":"vimplate","1":"vimplate","script_type":"utility","2":"utility","summary":"template system for vim  (example for C++, Perl, LaTeX and make)","3":"template system for vim  (example for C++, Perl, LaTeX and make)","description":" 1. Description\r\n 2. Usage\r\n 3. Subroutines\r\n 4. Example\r\n 5. Documentation\r\n 6. Depends\r\n 7. Installation\r\n\r\n\r\n1. Description                                        *vimplate-description*\r\n \r\nVimplate provides an extensible and powerful template processing system.\r\nIt is based on Perl and Template-Toolkit.\r\nYou can create templates for program code, makefiles, letters, html pages,\r\nlatex etc. As example vimplate contains templates for C++, LaTeX, Perl\r\nand Makefile.\r\nWith vimplate you can write templates which interact with the user.\r\nFor themes are the functions choice() and input().\r\nYou can choose different locale for the function date() and locale().\r\nYou can write your own perl code directly in the templates.\r\n\r\nIn case you find my template useful,\r\nor have suggestions for improvements, please let me know.\r\n\r\nIf you write a new template,\r\nand  would like me to add it to the vimplate package\r\nplease send it to: stotz@gmx.ch\r\n\r\n\r\n2. Usage                                                    *vimplate-usage*\r\n\r\nUsage:\r\n  :Vimplate <template> [options]\r\n    choice <template> whit <TAB> (command line completion is supported).\r\n    With <TAB> all templates are listed.\r\n    [options]\r\n      -user|u=<username>\r\n        Use the information form user <username> while parsing templates.\r\n      -dir|d=<templatedir>\r\n        Search templatefiles in <templatedir>.\r\n\r\n\r\n3. Subroutines                                         *vimplate-subroutines*\r\n\r\n  locale()                  for locale please see: man locale\r\n  [% loc=locale() %]        get the current locale\r\n                              and write it to the variable loc\r\n  [% locale('C') %]         set global the current locale to C\r\n  [% locale('de_DE') %]     set global the current locale to de_DE\r\n  date()                    for date please see: man date\r\n  [% date('%c') %]          print the current date\r\n                              with the current locale setting\r\n  [% date('de_DE', '%c') %] print the current date with the locale de_DE\r\n  input()\r\n  [% var=input() %]         read input from user\r\n                              and write it to the variable var\r\n  choice()\r\n  [% day=choice('day:', 'Su', 'Mo', 'Tu', 'We', 'Th', 'Fr', 'Sa') %]\r\n                            let the user choice between different values\r\n                            and write it to the variable day\r\n\r\n  please try :Vimplate Test\r\n\r\n\r\n4. Example                                                *vimplate-example*\r\n\r\na LaTeX Template:\r\n  http:\/\/typedef.ch\/vimplate\/example\/LaTeX.tt.html\r\nthe generated LaTeX File:\r\n  http:\/\/typedef.ch\/vimplate\/example\/Example.tex.html\r\na Makefile Template for LaTeX:\r\n  http:\/\/typedef.ch\/vimplate\/example\/Makefile-LaTeX.tt.html\r\nthe generated Makefile:\r\n  http:\/\/typedef.ch\/vimplate\/example\/Makefile.html\r\nc++ Templates:\r\n  http:\/\/typedef.ch\/vimplate\/example\/hpp-default.tt.html\r\n  http:\/\/typedef.ch\/vimplate\/example\/cpp-default.tt.html\r\nthe generated class:\r\n  http:\/\/typedef.ch\/vimplate\/example\/Example.hpp.html\r\n  http:\/\/typedef.ch\/vimplate\/example\/Example.cpp.html\r\nthe generated class with doxygen:\r\n  http:\/\/typedef.ch\/vimplate\/example\/ExampleDoxy.hpp.html\r\n  http:\/\/typedef.ch\/vimplate\/example\/ExampleDoxy.cpp.html\r\na perl Template:\r\n  http:\/\/typedef.ch\/vimplate\/example\/perl.tt.html\r\nthe genereated program:\r\n  http:\/\/typedef.ch\/vimplate\/example\/Example.pl.html\r\nthe genereated program with Log4Perl:\r\n  http:\/\/typedef.ch\/vimplate\/example\/ExampleLog.pl.html\r\n\r\nExample:\r\n  the template letter.tt:\r\n    ________________________________________________________\r\n    [%\r\n       sex=choice('sex: ', 'female', 'male')\r\n       name=input('name: ')\r\n       location=input('your location: ')\r\n    -%]\r\n                       [% ucfirst(location) %], [% date('C', '%b %d, %Y') %]\r\n\r\n    Dear [% IF sex=='female'; 'Ms'; ELSE; 'Mr'; END %] [% ucfirst(name) %]\r\n\r\n    ...\r\n\r\n    Sincerely\r\n\r\n    [% user.firstname %] [% user.lastname %]\r\n    ________________________________________________________\r\n\r\n  run vim:\r\n    :Vimplate letter\r\n    sex:\r\n      0) female\r\n      1) male\r\n    0\r\n    name: Meier\r\n    your location: Olten\r\n\r\n  your input was:\r\n    :Vimplate letter<CR>0<CR>Meier<CR>Olten<CR>\r\n\r\n  this will produce this letter:\r\n    ________________________________________________________\r\n                                      Olten, Jul 11, 2005\r\n\r\n    Dear Ms Meier\r\n\r\n    ...\r\n\r\n    Sincerely\r\n\r\n    Urs Stotz\r\n    ________________________________________________________\r\n\r\nExample:\r\n  the template hpp-default.tt:\r\n    ________________________________________________________\r\n    [% classname=input('Class name: ')\r\n       doxygen=choice('with Doxygen comments: ', 'no', 'yes')\r\n    -%]\r\n    #ifndef [% uc(classname) %]_HPP\r\n    #define [% uc(classname) %]_HPP\r\n\r\n    [% IF doxygen=='yes' -%]\r\n    \/**\r\n     * @brief [% classname %] ... short description ...\r\n     * @author [% user.firstname %] [% user.lastname %] <[% user.mail %]>\r\n     * @date [% date('%Y-%m-%d') %]\r\n     * ... description ...\r\n     *\/\r\n\r\n    [% END -%]\r\n    class [% classname %]\r\n    {\r\n      public:\r\n    [% IF doxygen=='yes' -%]\r\n\r\n        \/**\r\n         * Default constructor\r\n         *\/\r\n    [% END -%]\r\n        [% classname %]();\r\n    [% IF doxygen=='yes' -%]\r\n\r\n        \/**\r\n         * Copy constructor\r\n         * @param other reference on object to copy\r\n         *\/\r\n    [% END -%]\r\n        [% classname %](const [% classname %]& other);\r\n    [% IF doxygen=='yes' -%]\r\n\r\n        \/**\r\n         * Assignment operator\r\n         * @param other reference on object to copy\r\n         * @return reference on initialisated object\r\n         *\/\r\n    [% END -%]\r\n        [% classname %]& operator=(const [% classname %]& other);\r\n    [% IF doxygen=='yes' -%]\r\n\r\n        \/**\r\n         * Destructor\r\n         *\/\r\n    [% END -%]\r\n        virtual ~[% classname %]();\r\n\r\n      private:\r\n    [% IF doxygen=='yes' -%]\r\n\r\n        \/**\r\n         * Base initialisation should be called\r\n         * at beginning of each constructor\r\n         *\/\r\n    [% END -%]\r\n        void init();\r\n    [% IF doxygen=='yes' -%]\r\n\r\n    \/**\r\n     * Method to copy each member (deep copy)\r\n     * @param other reference on object to copy\r\n     *\/\r\n    [% END -%]\r\n        void init(const [% classname %]& other);\r\n    };\r\n\r\n    #endif \/* #ifndef [% uc(classname) %]_HPP *\/\r\n    ________________________________________________________\r\n\r\n  run vim:\r\n    :Vimplate hpp-default\r\n    Class name: Parent\r\n    with Doxygen comments:\r\n      0) no\r\n      1) yes\r\n    1\r\n\r\n  your input was:\r\n    :Vimplate hpp-default<CR>Parent<CR>1<CR>\r\n\r\n  this will produce this c++ include file:\r\n    ________________________________________________________\r\n    #ifndef PARENT_HPP\r\n    #define PARENT_HPP\r\n\r\n    \/**\r\n     * @brief Parent ... short description ...\r\n     * @author Urs Stotz <stotz@gmx.ch>\r\n     * @date 2005-07-18\r\n     * ... description ...\r\n     *\/\r\n\r\n    class Parent\r\n    {\r\n      public:\r\n\r\n        \/**\r\n         * Default constructor\r\n         *\/\r\n        Parent();\r\n\r\n        \/**\r\n         * Copy constructor\r\n         * @param other reference on object to copy\r\n         *\/\r\n        Parent(const Parent& other);\r\n\r\n        \/**\r\n         * Assignment operator\r\n         * @param other reference on object to copy\r\n         * @return reference on initialisated object\r\n         *\/\r\n        Parent& operator=(const Parent& other);\r\n\r\n        \/**\r\n         * Destructor\r\n         *\/\r\n        virtual ~Parent();\r\n\r\n      private:\r\n\r\n        \/**\r\n         * Base initialisation should be called\r\n         * at beginning of each constructor\r\n         *\/\r\n        void init();\r\n\r\n        \/**\r\n         * Method to copy each member (deep copy)\r\n         * @param other reference on object to copy\r\n         *\/\r\n        void init(const Parent& other);\r\n    };\r\n\r\n    #endif \/* #ifndef PARENT_HPP *\/\r\n    ________________________________________________________\r\n\r\n\r\n5. Documentation                                    *vimplate-documentation*\r\n\r\nDocumentation:\r\n  - http:\/\/typedef.ch\/vimplate\r\n  - http:\/\/www.template-toolkit.org\/docs.html\r\n  - http:\/\/perldoc.perl.org\/perl.html\r\n\r\nTodo:\r\n  - better exception handling\r\n  - write more templates\r\n\r\nLicense:\r\n  This program is free software; you can redistribute it and\/or modify it\r\n  under the terms of the GNU General Public License, version 2, as published\r\n  by the Free Software Foundation.\r\n\r\n  This program is distributed in the hope that it will be useful, but\r\n  WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY\r\n  or FITNESS FOR A PARTICULAR PURPOSE.  See the GNU General Public License\r\n  for more details.\r\n\r\n  A copy of the GNU GPL is available as \/usr\/share\/common-licenses\/GPL-2\r\n  on Debian systems, or on the World Wide Web at\r\n  http:\/\/www.gnu.org\/copyleft\/gpl.html\r\n  You can also obtain it by writing to the Free Software Foundation, Inc.,\r\n  59 Temple Place - Suite 330, Boston, MA 02111-1307, USA\r\n\r\nCopyright:\r\n  Copyright (c) 2005, Urs Stotz <stotz@gmx.ch>\r\n\r\nVersion:\r\n  vimplate 0.2.3","4":" 1. Description\r\n 2. Usage\r\n 3. Subroutines\r\n 4. Example\r\n 5. Documentation\r\n 6. Depends\r\n 7. Installation\r\n\r\n\r\n1. Description                                        *vimplate-description*\r\n \r\nVimplate provides an extensible and powerful template processing system.\r\nIt is based on Perl and Template-Toolkit.\r\nYou can create templates for program code, makefiles, letters, html pages,\r\nlatex etc. As example vimplate contains templates for C++, LaTeX, Perl\r\nand Makefile.\r\nWith vimplate you can write templates which interact with the user.\r\nFor themes are the functions choice() and input().\r\nYou can choose different locale for the function date() and locale().\r\nYou can write your own perl code directly in the templates.\r\n\r\nIn case you find my template useful,\r\nor have suggestions for improvements, please let me know.\r\n\r\nIf you write a new template,\r\nand  would like me to add it to the vimplate package\r\nplease send it to: stotz@gmx.ch\r\n\r\n\r\n2. Usage                                                    *vimplate-usage*\r\n\r\nUsage:\r\n  :Vimplate <template> [options]\r\n    choice <template> whit <TAB> (command line completion is supported).\r\n    With <TAB> all templates are listed.\r\n    [options]\r\n      -user|u=<username>\r\n        Use the information form user <username> while parsing templates.\r\n      -dir|d=<templatedir>\r\n        Search templatefiles in <templatedir>.\r\n\r\n\r\n3. Subroutines                                         *vimplate-subroutines*\r\n\r\n  locale()                  for locale please see: man locale\r\n  [% loc=locale() %]        get the current locale\r\n                              and write it to the variable loc\r\n  [% locale('C') %]         set global the current locale to C\r\n  [% locale('de_DE') %]     set global the current locale to de_DE\r\n  date()                    for date please see: man date\r\n  [% date('%c') %]          print the current date\r\n                              with the current locale setting\r\n  [% date('de_DE', '%c') %] print the current date with the locale de_DE\r\n  input()\r\n  [% var=input() %]         read input from user\r\n                              and write it to the variable var\r\n  choice()\r\n  [% day=choice('day:', 'Su', 'Mo', 'Tu', 'We', 'Th', 'Fr', 'Sa') %]\r\n                            let the user choice between different values\r\n                            and write it to the variable day\r\n\r\n  please try :Vimplate Test\r\n\r\n\r\n4. Example                                                *vimplate-example*\r\n\r\na LaTeX Template:\r\n  http:\/\/typedef.ch\/vimplate\/example\/LaTeX.tt.html\r\nthe generated LaTeX File:\r\n  http:\/\/typedef.ch\/vimplate\/example\/Example.tex.html\r\na Makefile Template for LaTeX:\r\n  http:\/\/typedef.ch\/vimplate\/example\/Makefile-LaTeX.tt.html\r\nthe generated Makefile:\r\n  http:\/\/typedef.ch\/vimplate\/example\/Makefile.html\r\nc++ Templates:\r\n  http:\/\/typedef.ch\/vimplate\/example\/hpp-default.tt.html\r\n  http:\/\/typedef.ch\/vimplate\/example\/cpp-default.tt.html\r\nthe generated class:\r\n  http:\/\/typedef.ch\/vimplate\/example\/Example.hpp.html\r\n  http:\/\/typedef.ch\/vimplate\/example\/Example.cpp.html\r\nthe generated class with doxygen:\r\n  http:\/\/typedef.ch\/vimplate\/example\/ExampleDoxy.hpp.html\r\n  http:\/\/typedef.ch\/vimplate\/example\/ExampleDoxy.cpp.html\r\na perl Template:\r\n  http:\/\/typedef.ch\/vimplate\/example\/perl.tt.html\r\nthe genereated program:\r\n  http:\/\/typedef.ch\/vimplate\/example\/Example.pl.html\r\nthe genereated program with Log4Perl:\r\n  http:\/\/typedef.ch\/vimplate\/example\/ExampleLog.pl.html\r\n\r\nExample:\r\n  the template letter.tt:\r\n    ________________________________________________________\r\n    [%\r\n       sex=choice('sex: ', 'female', 'male')\r\n       name=input('name: ')\r\n       location=input('your location: ')\r\n    -%]\r\n                       [% ucfirst(location) %], [% date('C', '%b %d, %Y') %]\r\n\r\n    Dear [% IF sex=='female'; 'Ms'; ELSE; 'Mr'; END %] [% ucfirst(name) %]\r\n\r\n    ...\r\n\r\n    Sincerely\r\n\r\n    [% user.firstname %] [% user.lastname %]\r\n    ________________________________________________________\r\n\r\n  run vim:\r\n    :Vimplate letter\r\n    sex:\r\n      0) female\r\n      1) male\r\n    0\r\n    name: Meier\r\n    your location: Olten\r\n\r\n  your input was:\r\n    :Vimplate letter<CR>0<CR>Meier<CR>Olten<CR>\r\n\r\n  this will produce this letter:\r\n    ________________________________________________________\r\n                                      Olten, Jul 11, 2005\r\n\r\n    Dear Ms Meier\r\n\r\n    ...\r\n\r\n    Sincerely\r\n\r\n    Urs Stotz\r\n    ________________________________________________________\r\n\r\nExample:\r\n  the template hpp-default.tt:\r\n    ________________________________________________________\r\n    [% classname=input('Class name: ')\r\n       doxygen=choice('with Doxygen comments: ', 'no', 'yes')\r\n    -%]\r\n    #ifndef [% uc(classname) %]_HPP\r\n    #define [% uc(classname) %]_HPP\r\n\r\n    [% IF doxygen=='yes' -%]\r\n    \/**\r\n     * @brief [% classname %] ... short description ...\r\n     * @author [% user.firstname %] [% user.lastname %] <[% user.mail %]>\r\n     * @date [% date('%Y-%m-%d') %]\r\n     * ... description ...\r\n     *\/\r\n\r\n    [% END -%]\r\n    class [% classname %]\r\n    {\r\n      public:\r\n    [% IF doxygen=='yes' -%]\r\n\r\n        \/**\r\n         * Default constructor\r\n         *\/\r\n    [% END -%]\r\n        [% classname %]();\r\n    [% IF doxygen=='yes' -%]\r\n\r\n        \/**\r\n         * Copy constructor\r\n         * @param other reference on object to copy\r\n         *\/\r\n    [% END -%]\r\n        [% classname %](const [% classname %]& other);\r\n    [% IF doxygen=='yes' -%]\r\n\r\n        \/**\r\n         * Assignment operator\r\n         * @param other reference on object to copy\r\n         * @return reference on initialisated object\r\n         *\/\r\n    [% END -%]\r\n        [% classname %]& operator=(const [% classname %]& other);\r\n    [% IF doxygen=='yes' -%]\r\n\r\n        \/**\r\n         * Destructor\r\n         *\/\r\n    [% END -%]\r\n        virtual ~[% classname %]();\r\n\r\n      private:\r\n    [% IF doxygen=='yes' -%]\r\n\r\n        \/**\r\n         * Base initialisation should be called\r\n         * at beginning of each constructor\r\n         *\/\r\n    [% END -%]\r\n        void init();\r\n    [% IF doxygen=='yes' -%]\r\n\r\n    \/**\r\n     * Method to copy each member (deep copy)\r\n     * @param other reference on object to copy\r\n     *\/\r\n    [% END -%]\r\n        void init(const [% classname %]& other);\r\n    };\r\n\r\n    #endif \/* #ifndef [% uc(classname) %]_HPP *\/\r\n    ________________________________________________________\r\n\r\n  run vim:\r\n    :Vimplate hpp-default\r\n    Class name: Parent\r\n    with Doxygen comments:\r\n      0) no\r\n      1) yes\r\n    1\r\n\r\n  your input was:\r\n    :Vimplate hpp-default<CR>Parent<CR>1<CR>\r\n\r\n  this will produce this c++ include file:\r\n    ________________________________________________________\r\n    #ifndef PARENT_HPP\r\n    #define PARENT_HPP\r\n\r\n    \/**\r\n     * @brief Parent ... short description ...\r\n     * @author Urs Stotz <stotz@gmx.ch>\r\n     * @date 2005-07-18\r\n     * ... description ...\r\n     *\/\r\n\r\n    class Parent\r\n    {\r\n      public:\r\n\r\n        \/**\r\n         * Default constructor\r\n         *\/\r\n        Parent();\r\n\r\n        \/**\r\n         * Copy constructor\r\n         * @param other reference on object to copy\r\n         *\/\r\n        Parent(const Parent& other);\r\n\r\n        \/**\r\n         * Assignment operator\r\n         * @param other reference on object to copy\r\n         * @return reference on initialisated object\r\n         *\/\r\n        Parent& operator=(const Parent& other);\r\n\r\n        \/**\r\n         * Destructor\r\n         *\/\r\n        virtual ~Parent();\r\n\r\n      private:\r\n\r\n        \/**\r\n         * Base initialisation should be called\r\n         * at beginning of each constructor\r\n         *\/\r\n        void init();\r\n\r\n        \/**\r\n         * Method to copy each member (deep copy)\r\n         * @param other reference on object to copy\r\n         *\/\r\n        void init(const Parent& other);\r\n    };\r\n\r\n    #endif \/* #ifndef PARENT_HPP *\/\r\n    ________________________________________________________\r\n\r\n\r\n5. Documentation                                    *vimplate-documentation*\r\n\r\nDocumentation:\r\n  - http:\/\/typedef.ch\/vimplate\r\n  - http:\/\/www.template-toolkit.org\/docs.html\r\n  - http:\/\/perldoc.perl.org\/perl.html\r\n\r\nTodo:\r\n  - better exception handling\r\n  - write more templates\r\n\r\nLicense:\r\n  This program is free software; you can redistribute it and\/or modify it\r\n  under the terms of the GNU General Public License, version 2, as published\r\n  by the Free Software Foundation.\r\n\r\n  This program is distributed in the hope that it will be useful, but\r\n  WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY\r\n  or FITNESS FOR A PARTICULAR PURPOSE.  See the GNU General Public License\r\n  for more details.\r\n\r\n  A copy of the GNU GPL is available as \/usr\/share\/common-licenses\/GPL-2\r\n  on Debian systems, or on the World Wide Web at\r\n  http:\/\/www.gnu.org\/copyleft\/gpl.html\r\n  You can also obtain it by writing to the Free Software Foundation, Inc.,\r\n  59 Temple Place - Suite 330, Boston, MA 02111-1307, USA\r\n\r\nCopyright:\r\n  Copyright (c) 2005, Urs Stotz <stotz@gmx.ch>\r\n\r\nVersion:\r\n  vimplate 0.2.3","install_details":"6. Depends:                                               *vimplate-depends*\r\n\r\nDebian Users:\r\nVimplate is part of vim-scripts >= 7.0.5  thanks: Stefano Zacchiroli and Michael Piefel\r\n  apt-get install vim-scripts\r\n\r\n  Perl\r\n    http:\/\/www.perl.org\r\n    Windows users:\r\n      http:\/\/www.activestate.com\/Products\/ActivePerl\r\n  Template-Toolkit\r\n    http:\/\/search.cpan.org\/~abw\/Template-Toolkit-2.14\r\n    or apt-get install libtemplate-perl\r\n    or perl -MCPAN -e\"install Template\"\r\n    Windows users:\r\n      ppm install\r\n        http:\/\/openinteract.sourceforge.net\/ppmpackages\/AppConfig.ppd\r\n      ppm install\r\n        http:\/\/openinteract.sourceforge.net\/ppmpackages\/Template-Toolkit.ppd\r\n\r\nSuggests:\r\n  TT2 syntax:\r\n    http:\/\/www.vim.org\/scripts\/script.php?script_id=830\r\n\r\n\r\n7. Installation                                      *vimplate-installation*\r\n\r\nInstallation steps:\r\n  1. change to your $HOME\/.vim directory\r\n       (on windows: set the variable HOME\r\n         set HOME=c:\\vim)\r\n  2. untar vimplate.tar.gz: gzip -dc vimplate.tar.gz |tar xpvf -\r\n  3. move the vimplate into your preferred directory\r\n      for example in $HOME\/bin or \/usr\/local\/bin\r\n  4. move the directory Template with the example templates\r\n      to the place that you prefer\r\n  5. edit your $HOME\/.vimrc and set the variable Vimplate to\r\n      to the place where vimplate is located\r\n      for example let Vimplate = \"$HOME\/bin\/vimplate\"\r\n        (on windows: let Vimplate = \"%HOME%\/bin\/vimplate.cmd\" )\r\n  6. run vimplate to create your configuration file $HOME\/.vimplaterc\r\n      for example $HOME\/bin\/vimplate -createconfig\r\n        (on windows: %HOME%\/bin\/vimplate.cmd -createconfig\" )\r\n  7. edit your $HOME\/.vimplaterc\r\n       (on windows: %HOME%\/_vimplaterc)\r\n  8. change to the $HOME\/.vim\/doc directory,\r\n      start Vim and run the \":helptags .\" command to process the\r\n      taglist help file. (see: |helptags| )\r\n  9. happy vimplating","5":"6. Depends:                                               *vimplate-depends*\r\n\r\nDebian Users:\r\nVimplate is part of vim-scripts >= 7.0.5  thanks: Stefano Zacchiroli and Michael Piefel\r\n  apt-get install vim-scripts\r\n\r\n  Perl\r\n    http:\/\/www.perl.org\r\n    Windows users:\r\n      http:\/\/www.activestate.com\/Products\/ActivePerl\r\n  Template-Toolkit\r\n    http:\/\/search.cpan.org\/~abw\/Template-Toolkit-2.14\r\n    or apt-get install libtemplate-perl\r\n    or perl -MCPAN -e\"install Template\"\r\n    Windows users:\r\n      ppm install\r\n        http:\/\/openinteract.sourceforge.net\/ppmpackages\/AppConfig.ppd\r\n      ppm install\r\n        http:\/\/openinteract.sourceforge.net\/ppmpackages\/Template-Toolkit.ppd\r\n\r\nSuggests:\r\n  TT2 syntax:\r\n    http:\/\/www.vim.org\/scripts\/script.php?script_id=830\r\n\r\n\r\n7. Installation                                      *vimplate-installation*\r\n\r\nInstallation steps:\r\n  1. change to your $HOME\/.vim directory\r\n       (on windows: set the variable HOME\r\n         set HOME=c:\\vim)\r\n  2. untar vimplate.tar.gz: gzip -dc vimplate.tar.gz |tar xpvf -\r\n  3. move the vimplate into your preferred directory\r\n      for example in $HOME\/bin or \/usr\/local\/bin\r\n  4. move the directory Template with the example templates\r\n      to the place that you prefer\r\n  5. edit your $HOME\/.vimrc and set the variable Vimplate to\r\n      to the place where vimplate is located\r\n      for example let Vimplate = \"$HOME\/bin\/vimplate\"\r\n        (on windows: let Vimplate = \"%HOME%\/bin\/vimplate.cmd\" )\r\n  6. run vimplate to create your configuration file $HOME\/.vimplaterc\r\n      for example $HOME\/bin\/vimplate -createconfig\r\n        (on windows: %HOME%\/bin\/vimplate.cmd -createconfig\" )\r\n  7. edit your $HOME\/.vimplaterc\r\n       (on windows: %HOME%\/_vimplaterc)\r\n  8. change to the $HOME\/.vim\/doc directory,\r\n      start Vim and run the \":helptags .\" command to process the\r\n      taglist help file. (see: |helptags| )\r\n  9. happy vimplating","first_name":"Urs","6":"Urs","last_name":"Stotz","7":"Stotz","releases":[{"0":"1311","vim_version":"6.0","1":"6.0","script_version":"0.2.3","2":"0.2.3","version_comment":"The perl vimplate script is running now also on Windows.\r\nA vim help added.\r\nDokumentation written for Windows ActiveState Perl User.\r\nTemplates for C++, Perl, LaTeX and make revised.","3":"The perl vimplate script is running now also on Windows.\r\nA vim help added.\r\nDokumentation written for Windows ActiveState Perl User.\r\nTemplates for C++, Perl, LaTeX and make revised.","package":"vimplate-0.2.3.tar.gz","4":"vimplate-0.2.3.tar.gz","src_id":"4504","5":"4504","creation_date":"1124526836","6":"1124526836"},{"0":"1311","vim_version":"6.0","1":"6.0","script_version":"0.2.2","2":"0.2.2","version_comment":"Better templates for C++. Now with choose between Doxygen comments or non comments.\r\nVimplate should be running on Windows when there Template-Toolkit is installed.","3":"Better templates for C++. Now with choose between Doxygen comments or non comments.\r\nVimplate should be running on Windows when there Template-Toolkit is installed.","package":"vimplate-0.2.2.tar.gz","4":"vimplate-0.2.2.tar.gz","src_id":"4438","5":"4438","creation_date":"1121696066","6":"1121696066"}]},"1310":{"script_id":"1310","0":"1310","script_name":"DataStage (Universe) Basic","1":"DataStage (Universe) Basic","script_type":"syntax","2":"syntax","summary":"Programming language used in Universe DB and DataStage","3":"Programming language used in Universe DB and DataStage","description":"Note: This script is obsolete.\r\n\r\nIf you need syntax file for DataStage go at vimscript #2161. The file includes DataStage Basic and Parallel functions plus DSX syntax.\r\n\r\nIf you need just syntax for Universe Basic go at vimscript #2143.\r\n\r\n","4":"Note: This script is obsolete.\r\n\r\nIf you need syntax file for DataStage go at vimscript #2161. The file includes DataStage Basic and Parallel functions plus DSX syntax.\r\n\r\nIf you need just syntax for Universe Basic go at vimscript #2143.\r\n\r\n","install_details":"Put into VIM's syntax directory. Can also do appropriate changes in synmenu.vim and filetype.vim.","5":"Put into VIM's syntax directory. Can also do appropriate changes in synmenu.vim and filetype.vim.","first_name":"Lubomir","6":"Lubomir","last_name":"Husar","7":"Husar","releases":[{"0":"1310","vim_version":"6.0","1":"6.0","script_version":"1.3","2":"1.3","version_comment":"Dan is simply unbeatable! He came up with another update that fix the problem with displaying of comments.","3":"Dan is simply unbeatable! He came up with another update that fix the problem with displaying of comments.","package":"unibasic.vim","4":"unibasic.vim","src_id":"5477","5":"5477","creation_date":"1143079132","6":"1143079132"},{"0":"1310","vim_version":"6.0","1":"6.0","script_version":"1.2","2":"1.2","version_comment":"Another great tip from Dan. Script is now able recognize strings between backslash - \\.","3":"Another great tip from Dan. Script is now able recognize strings between backslash - \\.","package":"unibasic.vim","4":"unibasic.vim","src_id":"4634","5":"4634","creation_date":"1128063285","6":"1128063285"},{"0":"1310","vim_version":"6.0","1":"6.0","script_version":"1.1","2":"1.1","version_comment":"Minor issue with RPC.* functions highlighting. Added set iskeyword+=. Based on the kindly suggestion of Dan Sharp. Thanks.","3":"Minor issue with RPC.* functions highlighting. Added set iskeyword+=. Based on the kindly suggestion of Dan Sharp. Thanks.","package":"unibasic.vim","4":"unibasic.vim","src_id":"4608","5":"4608","creation_date":"1127351156","6":"1127351156"},{"0":"1310","vim_version":"6.0","1":"6.0","script_version":"1","2":"1","version_comment":"Initial upload","3":"Initial upload","package":"unibasic.vim","4":"unibasic.vim","src_id":"4416","5":"4416","creation_date":"1120806888","6":"1120806888"}]},"1309":{"script_id":"1309","0":"1309","script_name":"java_fold","1":"java_fold","script_type":"utility","2":"utility","summary":"Folding expression for Java","3":"Folding expression for Java","description":"This script uses the expr fold-method to create folds for java source code.  Folds are created for methods, variables and nested classes with a javadoc comment (that is, at any line inside a class that starts with \/**).  The fold will show a count of the number of lines contained in it and the first line of the variable or method declaration.\r\n\r\nThe fold level for each fold is equal to the indentation divided by the value of the 'shiftwidth' option, so make sure that 'shiftwidth' is set to the right value for your code.\r\n\r\nCaveats:\r\n- this doesn't work if you don't indent your code (properly) or if you don't use javadoc comments\r\n- the folds are \"greedy\": they start at a javadoc comment and run upto the next javadoc comment (they don't pay attention to syntax)\r\n- you can't see the javadoc comments in the folds","4":"This script uses the expr fold-method to create folds for java source code.  Folds are created for methods, variables and nested classes with a javadoc comment (that is, at any line inside a class that starts with \/**).  The fold will show a count of the number of lines contained in it and the first line of the variable or method declaration.\r\n\r\nThe fold level for each fold is equal to the indentation divided by the value of the 'shiftwidth' option, so make sure that 'shiftwidth' is set to the right value for your code.\r\n\r\nCaveats:\r\n- this doesn't work if you don't indent your code (properly) or if you don't use javadoc comments\r\n- the folds are \"greedy\": they start at a javadoc comment and run upto the next javadoc comment (they don't pay attention to syntax)\r\n- you can't see the javadoc comments in the folds","install_details":"Either save the script in a file and source that file whenever you want to use the folding, or save it in your ftplugin directory (for example, ~\/.vim\/ftplugin) and it should load every time you edit java code.","5":"Either save the script in a file and source that file whenever you want to use the folding, or save it in your ftplugin directory (for example, ~\/.vim\/ftplugin) and it should load every time you edit java code.","first_name":"Jorrit","6":"Jorrit","last_name":"Wiersma","7":"Wiersma","releases":[{"0":"1309","vim_version":"6.0","1":"6.0","script_version":"1.1","2":"1.1","version_comment":"Added line counts to the fold text (contributed by Robert Ames)","3":"Added line counts to the fold text (contributed by Robert Ames)","package":"java_fold.vim","4":"java_fold.vim","src_id":"4426","5":"4426","creation_date":"1121230640","6":"1121230640"},{"0":"1309","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"java_fold.vim","4":"java_fold.vim","src_id":"4380","5":"4380","creation_date":"1119343769","6":"1119343769"}]},"1308":{"script_id":"1308","0":"1308","script_name":"another dark scheme","1":"another dark scheme","script_type":"color scheme","2":"color scheme","summary":"a pep-up of desert","3":"a pep-up of desert","description":"a color scheme for dark and fuzzy backgrounds, i made it because i thought \"desert\" was too boring.\r\nopen-source\r\nhave fun.","4":"a color scheme for dark and fuzzy backgrounds, i made it because i thought \"desert\" was too boring.\r\nopen-source\r\nhave fun.","install_details":"move to \/usr\/share\/vim\/vim6*\/colors\/anotherdark.vim\r\nget it by typing:\r\n:colorscheme anotherdark\r\n(you can use the tab-key for fast-replacement)\r\nif you want to use it permanently, add the line \"colorscheme anotherdark\" at the bottom of your vimrc file (normally ~\/.vimrc)\r\nhave fun","5":"move to \/usr\/share\/vim\/vim6*\/colors\/anotherdark.vim\r\nget it by typing:\r\n:colorscheme anotherdark\r\n(you can use the tab-key for fast-replacement)\r\nif you want to use it permanently, add the line \"colorscheme anotherdark\" at the bottom of your vimrc file (normally ~\/.vimrc)\r\nhave fun","first_name":"tom","6":"tom","last_name":"reichhart","7":"reichhart","releases":[{"0":"1308","vim_version":"6.0","1":"6.0","script_version":"1.1","2":"1.1","version_comment":"corrected the error in line 22 (it was not a fatal error)","3":"corrected the error in line 22 (it was not a fatal error)","package":"anotherdark.vim","4":"anotherdark.vim","src_id":"4449","5":"4449","creation_date":"1122602291","6":"1122602291"},{"0":"1308","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"anotherdark.vim","4":"anotherdark.vim","src_id":"4377","5":"4377","creation_date":"1119270067","6":"1119270067"}]},"1307":{"script_id":"1307","0":"1307","script_name":"php_template","1":"php_template","script_type":"ftplugin","2":"ftplugin","summary":"PHP5 Code templates for common snippets","3":"PHP5 Code templates for common snippets","description":" This filetype plugin provides a couple of code templates for PHP5\r\n development. The code is formatted according to PEAR Coding Standards.\r\n\r\n The three provided templates are:\r\n  - Class file template\r\n  - Method docblock template\r\n  - Field getter and setter template\r\n\r\n","4":" This filetype plugin provides a couple of code templates for PHP5\r\n development. The code is formatted according to PEAR Coding Standards.\r\n\r\n The three provided templates are:\r\n  - Class file template\r\n  - Method docblock template\r\n  - Field getter and setter template\r\n\r\n","install_details":" Install by placing the file in the ~\/.vim\/ftplugin directory. Make sure you have \r\nfiletype plugins enabled (type :filetype<CR> and look at the result). If not, \r\nplace \"filetype plugin on\" in your ~\/.vimrc\r\n\r\nTo use:\r\n For the method docblock and getter\/setter templates, just write the code as\r\n usual. A mapping is triggered when you type ( after the method name, and\r\n when you type the ; after the field definition.\r\n\r\n For the class file template, type 'class' in normal mode. You'll be prompted\r\n for relevant information, and the class skeleton will be generated.","5":" Install by placing the file in the ~\/.vim\/ftplugin directory. Make sure you have \r\nfiletype plugins enabled (type :filetype<CR> and look at the result). If not, \r\nplace \"filetype plugin on\" in your ~\/.vimrc\r\n\r\nTo use:\r\n For the method docblock and getter\/setter templates, just write the code as\r\n usual. A mapping is triggered when you type ( after the method name, and\r\n when you type the ; after the field definition.\r\n\r\n For the class file template, type 'class' in normal mode. You'll be prompted\r\n for relevant information, and the class skeleton will be generated.","first_name":"S\u00c3\u00a9rgio","6":"S\u00c3\u00a9rgio","last_name":"Carvalho","7":"Carvalho","releases":[{"0":"1307","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"php_template.vim","4":"php_template.vim","src_id":"4376","5":"4376","creation_date":"1119265138","6":"1119265138"}]},"1306":{"script_id":"1306","0":"1306","script_name":"cguess","1":"cguess","script_type":"utility","2":"utility","summary":"C and C++ identifier completion","3":"C and C++ identifier completion","description":"Cguess is a (Yet another?) C\/C++\/Java\u00e2\u0084\u00a2 syntax auto-completer meant to be used as a plugin for VIM text editor or others. See its homepage: http:\/\/www.zabor.org\/cguess and the README file for details.\r\n\r\nThis is an early version and is quite limited. It works the \"intellisense\"-style way but the interface is quite primitive in this version. It maps several key combinations in insert mode and will show a list of members in a splitted window, function prototypes or the list of enumerators in comparisons (after typing == or !=) whenever possible.\r\n\r\nCguess is based on a true C++ language parser (like the compilers) and understands even the most complex syntactic constructs (but it will refuse to parse programs that contain errors). The parser supports several GNU extensions to C and C++ and some ISO and ANSI specific ideas.\r\n\r\nJava\u00e2\u0084\u00a2 is not supported.\r\n\r\nIf you use cguess, help Uganda.","4":"Cguess is a (Yet another?) C\/C++\/Java\u00e2\u0084\u00a2 syntax auto-completer meant to be used as a plugin for VIM text editor or others. See its homepage: http:\/\/www.zabor.org\/cguess and the README file for details.\r\n\r\nThis is an early version and is quite limited. It works the \"intellisense\"-style way but the interface is quite primitive in this version. It maps several key combinations in insert mode and will show a list of members in a splitted window, function prototypes or the list of enumerators in comparisons (after typing == or !=) whenever possible.\r\n\r\nCguess is based on a true C++ language parser (like the compilers) and understands even the most complex syntactic constructs (but it will refuse to parse programs that contain errors). The parser supports several GNU extensions to C and C++ and some ISO and ANSI specific ideas.\r\n\r\nJava\u00e2\u0084\u00a2 is not supported.\r\n\r\nIf you use cguess, help Uganda.","install_details":"Cguess now works on GNU\/Linux, GNU\/Hurd, FreeBSD and OpenBSD with GCC installed, but will be made more portable in future.\r\n\r\nTo install simply untar and do the following:\r\n.\/configure       # type .\/configure --help to see options\r\nmake\r\nmake install     # requires permissions\r\n\r\nAfter you start editing a C or C++ file for the first time please check if the value of g:cguessCFLAGS (type \":echo g:cguessCFLAGS\") is correct for your system. If you type \":let g:cguessVertical=0\", the identifiers will be displayed together with their types in a window above the buffer you're editing. There are some more variables you may want to customize. Set the values from inside your .vimrc to make them permanent.\r\n\r\nAfter you get tired of it, just go to the same directory and type:\r\nmake uninstall\r\nIf you had removed the directory, untar it again and rerun configure with the same parameters first.","5":"Cguess now works on GNU\/Linux, GNU\/Hurd, FreeBSD and OpenBSD with GCC installed, but will be made more portable in future.\r\n\r\nTo install simply untar and do the following:\r\n.\/configure       # type .\/configure --help to see options\r\nmake\r\nmake install     # requires permissions\r\n\r\nAfter you start editing a C or C++ file for the first time please check if the value of g:cguessCFLAGS (type \":echo g:cguessCFLAGS\") is correct for your system. If you type \":let g:cguessVertical=0\", the identifiers will be displayed together with their types in a window above the buffer you're editing. There are some more variables you may want to customize. Set the values from inside your .vimrc to make them permanent.\r\n\r\nAfter you get tired of it, just go to the same directory and type:\r\nmake uninstall\r\nIf you had removed the directory, untar it again and rerun configure with the same parameters first.","first_name":"Andrzej","6":"Andrzej","last_name":"Zaborowski","7":"Zaborowski","releases":[{"0":"1306","vim_version":"6.0","1":"6.0","script_version":"0.2.1","2":"0.2.1","version_comment":"Many bugfixes, some speed improvements and security checks,\r\nImproved interface (searching, sorting) and makefiles,\r\nSupport for the GNU C anonymous unions (union { blah; };) extension,\r\nImproved C++ linkage specifications (extern \"C\" { int operator; }),\r\nUsing hash tables instead of trees,","3":"Many bugfixes, some speed improvements and security checks,\r\nImproved interface (searching, sorting) and makefiles,\r\nSupport for the GNU C anonymous unions (union { blah; };) extension,\r\nImproved C++ linkage specifications (extern \"C\" { int operator; }),\r\nUsing hash tables instead of trees,","package":"cguess-0.2snapshot1.tar.bz2","4":"cguess-0.2snapshot1.tar.bz2","src_id":"4392","5":"4392","creation_date":"1119611280","6":"1119611280"},{"0":"1306","vim_version":"6.0","1":"6.0","script_version":"0.2","2":"0.2","version_comment":"Initial upload","3":"Initial upload","package":"cguess-0.2.tar.bz2","4":"cguess-0.2.tar.bz2","src_id":"4375","5":"4375","creation_date":"1119262763","6":"1119262763"}]},"1305":{"script_id":"1305","0":"1305","script_name":"T7ko","1":"T7ko","script_type":"utility","2":"utility","summary":"Plugins set I use in my everyday vimming (especially when programing)","3":"Plugins set I use in my everyday vimming (especially when programing)","description":"These plugins were written by me during quite a long time.  I just wrote functions and commands for all those operations, that was often necessary for me to do and modified them when my necessities changed.  I'm not sure, that these will be helpful to anybody else except me, but I hope so.\r\n\r\nThis plugins-set is multi-purpose one.  Among others tasks it can handle, there are:\r\n - alignment text in a table-like columns;\r\n - enabling diff on directories from inside Vim;\r\n - some floating-point operations;\r\n - improved vimsessions management;\r\n - sorting lines and makes them unique (useful for those working under Windows).\r\n\r\nIt also has one feature, which I think it is a quite good idea.  You can switch on and off the functionality of each component of this plugin-set at run-time, without restarting Vim.  This allows you not to pollute global Vim namespace with unnecessary functions and commands.","4":"These plugins were written by me during quite a long time.  I just wrote functions and commands for all those operations, that was often necessary for me to do and modified them when my necessities changed.  I'm not sure, that these will be helpful to anybody else except me, but I hope so.\r\n\r\nThis plugins-set is multi-purpose one.  Among others tasks it can handle, there are:\r\n - alignment text in a table-like columns;\r\n - enabling diff on directories from inside Vim;\r\n - some floating-point operations;\r\n - improved vimsessions management;\r\n - sorting lines and makes them unique (useful for those working under Windows).\r\n\r\nIt also has one feature, which I think it is a quite good idea.  You can switch on and off the functionality of each component of this plugin-set at run-time, without restarting Vim.  This allows you not to pollute global Vim namespace with unnecessary functions and commands.","install_details":"Unzip files in your vimfiles\/ dir (i.e. dir, where you have subfolders plugin\/ and doc\/).  After that, start Vim in subfolder vimfiles\/doc\/ and type\r\n  :helptags .\r\nNow plugins and documentation is ready to use.  Type\r\n  :help t7ko\r\nto start from.\r\n\r\nHappy Vimming!","5":"Unzip files in your vimfiles\/ dir (i.e. dir, where you have subfolders plugin\/ and doc\/).  After that, start Vim in subfolder vimfiles\/doc\/ and type\r\n  :helptags .\r\nNow plugins and documentation is ready to use.  Type\r\n  :help t7ko\r\nto start from.\r\n\r\nHappy Vimming!","first_name":"Ivan","6":"Ivan","last_name":"Tishchenko","7":"Tishchenko","releases":[{"0":"1305","vim_version":"6.0","1":"6.0","script_version":"1.1","2":"1.1","version_comment":"Initial upload","3":"Initial upload","package":"t7ko.zip","4":"t7ko.zip","src_id":"4374","5":"4374","creation_date":"1119248843","6":"1119248843"}]},"1304":{"script_id":"1304","0":"1304","script_name":"php_funcinfo.vim","1":"php_funcinfo.vim","script_type":"ftplugin","2":"ftplugin","summary":"Quick help on PHP functions","3":"Quick help on PHP functions","description":"A filetype plugin file for PHP. Displays a list of built-in PHP functions, their prototypes and short descriptions.\r\n\r\nIntended to be quick-reference-under-hand while editing a PHP script. You hit a hotkey, it opens a list of all PHP functions and displays a short synopsis for the word under cursor, if that is found.\r\n\r\nThe plugin is =UNFINISHED=, so there are some bugs:\r\n- Some bugs in function list updating. Flicker. And somewhere in moving back-and-forth, wrong entries begin to show up.\r\n- Syntax highlighting of the function prototype is quite messy.\r\n- No mappings to put the selected function call back into the text.\r\n- Speedup might help.\r\n\r\nAlso planned:\r\n- Parse the XML source of the manual thoroughly, including predefined constants and variables, dividing functions into sections, etc.\r\n- Kind of integration with external help, like Vim format by J\u00c3\u00b6rn Horstmann (http:\/\/planetxml.de\/vim-php-manual.php), or HTML format (will probably have to write a Vim browser) or CHM.\r\n\r\nAnybody who cares, feel free to take over the development of this plugin.\r\n\r\nZIP file is 80 Kb.","4":"A filetype plugin file for PHP. Displays a list of built-in PHP functions, their prototypes and short descriptions.\r\n\r\nIntended to be quick-reference-under-hand while editing a PHP script. You hit a hotkey, it opens a list of all PHP functions and displays a short synopsis for the word under cursor, if that is found.\r\n\r\nThe plugin is =UNFINISHED=, so there are some bugs:\r\n- Some bugs in function list updating. Flicker. And somewhere in moving back-and-forth, wrong entries begin to show up.\r\n- Syntax highlighting of the function prototype is quite messy.\r\n- No mappings to put the selected function call back into the text.\r\n- Speedup might help.\r\n\r\nAlso planned:\r\n- Parse the XML source of the manual thoroughly, including predefined constants and variables, dividing functions into sections, etc.\r\n- Kind of integration with external help, like Vim format by J\u00c3\u00b6rn Horstmann (http:\/\/planetxml.de\/vim-php-manual.php), or HTML format (will probably have to write a Vim browser) or CHM.\r\n\r\nAnybody who cares, feel free to take over the development of this plugin.\r\n\r\nZIP file is 80 Kb.","install_details":"Put php_funcinfo.vim and php_funcinfo.txt (this is the list of functions, not docs) in\r\n~\/.vim\/after\/ftplugin (Unix) or\r\n$VIM\\vimfiles\\after\\ftplugin (Windows)\r\n\r\nThe default mapping for the hotkey is <F2>, which interferes with the EasyHTML plugin, and EasyHTML is loaded by the default php ftplugin. That's why the script must go to the \/after directory. I suppose that nobody needs EasyHTML while editing PHP code. Or you can change the mapping.","5":"Put php_funcinfo.vim and php_funcinfo.txt (this is the list of functions, not docs) in\r\n~\/.vim\/after\/ftplugin (Unix) or\r\n$VIM\\vimfiles\\after\\ftplugin (Windows)\r\n\r\nThe default mapping for the hotkey is <F2>, which interferes with the EasyHTML plugin, and EasyHTML is loaded by the default php ftplugin. That's why the script must go to the \/after directory. I suppose that nobody needs EasyHTML while editing PHP code. Or you can change the mapping.","first_name":"kAtremer","6":"kAtremer","last_name":"","7":"","releases":[{"0":"1304","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"php_funcinfo.zip","4":"php_funcinfo.zip","src_id":"4366","5":"4366","creation_date":"1118825625","6":"1118825625"}]},"1303":{"script_id":"1303","0":"1303","script_name":"recycle.dll and recycle.vim","1":"recycle.dll and recycle.vim","script_type":"utility","2":"utility","summary":"Backup directly into Recycle Bin on Win32","3":"Backup directly into Recycle Bin on Win32","description":"The idea is stolen from Aditor (http:\/\/aditor.swrus.com\/). When backuping, the file is dropped to Recycle Bin instead of a temporary directory. As multiple files from one place may be deleted and will be stored in the bin, the bin may serve as a kind of versioning system.\r\n\r\nCall the DLL with\r\n    libcallnr('recycle', 'Recycle', 'd:\\path\\file.ext')\r\n\r\nReturns 1 on ok, 0 on error, -1 on user cancel (although the latter has little chance to happen, as the DLL deletes the file silenly).\r\n\r\nThere was a version that just deleted the file specified. Nothing wrong with it, but Vim said \"New\" when writing to the file, which is not true. So, for now, the DLL copies the file, adding the ~ suffix to it, and then deletes the copy. It overwrites any file~ that may occur to exist. And when restored from the bin, the original file is not overwritten, but a copy with ~ appears in the same directory.\r\n\r\nA .vim plugin is there, too. It adds an autocommand which backups the file to the Recycle Bin on each write, and disables Vim's own backup procedure. If the recycle fails, normal backup is enabled.\r\n\r\nIt does not honor the 'patchmode' option for now, does not load at all when it is set.\r\n\r\nPlanned:\r\n- honor 'patchmode'.\r\n- use the 'backupext' option instead of ~. The same with 'patchmode'.\r\n\r\nDecide:\r\n- copy the file with \"~\" or 'backupext' added (like now) or just delete the file (like it was)?\r\n- add an autocommand on FileWritePre?\r\n\r\nZIP archive is 2.4 Kb.\r\nThe DLL is 2.5 Kb.\r\nSource inside.","4":"The idea is stolen from Aditor (http:\/\/aditor.swrus.com\/). When backuping, the file is dropped to Recycle Bin instead of a temporary directory. As multiple files from one place may be deleted and will be stored in the bin, the bin may serve as a kind of versioning system.\r\n\r\nCall the DLL with\r\n    libcallnr('recycle', 'Recycle', 'd:\\path\\file.ext')\r\n\r\nReturns 1 on ok, 0 on error, -1 on user cancel (although the latter has little chance to happen, as the DLL deletes the file silenly).\r\n\r\nThere was a version that just deleted the file specified. Nothing wrong with it, but Vim said \"New\" when writing to the file, which is not true. So, for now, the DLL copies the file, adding the ~ suffix to it, and then deletes the copy. It overwrites any file~ that may occur to exist. And when restored from the bin, the original file is not overwritten, but a copy with ~ appears in the same directory.\r\n\r\nA .vim plugin is there, too. It adds an autocommand which backups the file to the Recycle Bin on each write, and disables Vim's own backup procedure. If the recycle fails, normal backup is enabled.\r\n\r\nIt does not honor the 'patchmode' option for now, does not load at all when it is set.\r\n\r\nPlanned:\r\n- honor 'patchmode'.\r\n- use the 'backupext' option instead of ~. The same with 'patchmode'.\r\n\r\nDecide:\r\n- copy the file with \"~\" or 'backupext' added (like now) or just delete the file (like it was)?\r\n- add an autocommand on FileWritePre?\r\n\r\nZIP archive is 2.4 Kb.\r\nThe DLL is 2.5 Kb.\r\nSource inside.","install_details":"Put the recycle.dll and recycle.vim in $VIM\\vimfiles\\plugin.","5":"Put the recycle.dll and recycle.vim in $VIM\\vimfiles\\plugin.","first_name":"kAtremer","6":"kAtremer","last_name":"","7":"","releases":[{"0":"1303","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"recycle.zip","4":"recycle.zip","src_id":"4365","5":"4365","creation_date":"1118823517","6":"1118823517"}]},"1302":{"script_id":"1302","0":"1302","script_name":"maximize.dll","1":"maximize.dll","script_type":"utility","2":"utility","summary":"Maximizing plugin for Win32 gVim","3":"Maximizing plugin for Win32 gVim","description":"Maximizes gVim window on startup.\r\n\r\n\r\nReason:\r\n\r\n\"simalt ~x\" does not work in a Russian Win2000, although it did in WinME, with corresponding Russian letter instead of \"x\". Everything always works fullscreen on my computer, and Vim is the core part of my work, so I maximized its window by hands each time, and searched for an automated solution.\r\n\r\n\r\nDetails:\r\n\r\nThis can be done by a DLL, which must be called with libcallnr() function:\r\n\r\n    call libcallnr('maximize', 'Maximize', 1)\r\n\r\nIt takes one numeric parameter: 1 means maximize the window and 0 restores it back. It returns 1 on success, 0 on fault.\r\n\r\n\r\nZIP archive is 4.4 Kb.\r\nSource inside.","4":"Maximizes gVim window on startup.\r\n\r\n\r\nReason:\r\n\r\n\"simalt ~x\" does not work in a Russian Win2000, although it did in WinME, with corresponding Russian letter instead of \"x\". Everything always works fullscreen on my computer, and Vim is the core part of my work, so I maximized its window by hands each time, and searched for an automated solution.\r\n\r\n\r\nDetails:\r\n\r\nThis can be done by a DLL, which must be called with libcallnr() function:\r\n\r\n    call libcallnr('maximize', 'Maximize', 1)\r\n\r\nIt takes one numeric parameter: 1 means maximize the window and 0 restores it back. It returns 1 on success, 0 on fault.\r\n\r\n\r\nZIP archive is 4.4 Kb.\r\nSource inside.","install_details":"Put maximize.vim and maximize.dll in $VIM\\vimfiles\\plugin\r\n\r\nFor Cream, you will also have to write:\r\n    let g:CREAM_WINPOS=0\r\nin your cream-conf.vim","5":"Put maximize.vim and maximize.dll in $VIM\\vimfiles\\plugin\r\n\r\nFor Cream, you will also have to write:\r\n    let g:CREAM_WINPOS=0\r\nin your cream-conf.vim","first_name":"kAtremer","6":"kAtremer","last_name":"","7":"","releases":[{"0":"1302","vim_version":"6.0","1":"6.0","script_version":"1.1a","2":"1.1a","version_comment":"- tidied up the files\r\n- made maximize.vim for installation as a plugin (mainly to support Cream)","3":"- tidied up the files\r\n- made maximize.vim for installation as a plugin (mainly to support Cream)","package":"maximize.zip","4":"maximize.zip","src_id":"7804","5":"7804","creation_date":"1192532991","6":"1192532991"},{"0":"1302","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"maximize.zip","4":"maximize.zip","src_id":"4364","5":"4364","creation_date":"1118821650","6":"1118821650"}]},"1300":{"script_id":"1300","0":"1300","script_name":"Shortcut functions for KeepCase script (","1":"Shortcut functions for KeepCase script (","script_type":"utility","2":"utility","summary":"Makes substitutions using Michael Geddes' KeepCase functions easier","3":"Makes substitutions using Michael Geddes' KeepCase functions easier","description":"This is a very simple script that allows you to easily do case-preserving text replacements over an arbitrary range. See vimscript #6 by Michael Geddes for the functions this script depends on.\r\n\r\nFor example:\r\n\r\n:'<,'>call S('building','campus')\r\n\r\nwill replace all occurrences of \"building\" with \"campus\", \"BUILDING_ID\" with \"CAMPUS_ID\", \"getBuilding\" with \"getCampus\", etc. across the currently selected range.\r\n\r\nAlso included is the SS(pat,sub) function which uses KeepCaseSameLen for the substitutions instead of KeepCase.\r\n\r\nThanks to Michael Geddes for a great script!","4":"This is a very simple script that allows you to easily do case-preserving text replacements over an arbitrary range. See vimscript #6 by Michael Geddes for the functions this script depends on.\r\n\r\nFor example:\r\n\r\n:'<,'>call S('building','campus')\r\n\r\nwill replace all occurrences of \"building\" with \"campus\", \"BUILDING_ID\" with \"CAMPUS_ID\", \"getBuilding\" with \"getCampus\", etc. across the currently selected range.\r\n\r\nAlso included is the SS(pat,sub) function which uses KeepCaseSameLen for the substitutions instead of KeepCase.\r\n\r\nThanks to Michael Geddes for a great script!","install_details":"Just copy this script and vimscript #6 to ~\/.vim\/plugin and restart VIM.","5":"Just copy this script and vimscript #6 to ~\/.vim\/plugin and restart VIM.","first_name":"Paul","6":"Paul","last_name":"Hoepfner-Homme","7":"Hoepfner-Homme","releases":[{"0":"1300","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"keepcasefun.vim","4":"keepcasefun.vim","src_id":"4360","5":"4360","creation_date":"1118683604","6":"1118683604"}]},"1299":{"script_id":"1299","0":"1299","script_name":"Project Browser or File explorer for vim","1":"Project Browser or File explorer for vim","script_type":"utility","2":"utility","summary":"Easy project navigation by listing the files","3":"Easy project navigation by listing the files","description":"Emulates the project file browser similar to some popular code browsers.      \r\nThis will list all the files in the project in a new window and allow user to open any file by mouse click\/<CR>\/O\/V\/H. This will come very handy when you are dealing with huge number of files and you really dont want to worry about the project directory structure, but just about the filename you are working on.  \r\n\r\nMore information about the key maps and configuration can be found in the fileexplorer.vim file.\r\n\r\nFeel free to contact me, in case you have any questions\/feedback.","4":"Emulates the project file browser similar to some popular code browsers.      \r\nThis will list all the files in the project in a new window and allow user to open any file by mouse click\/<CR>\/O\/V\/H. This will come very handy when you are dealing with huge number of files and you really dont want to worry about the project directory structure, but just about the filename you are working on.  \r\n\r\nMore information about the key maps and configuration can be found in the fileexplorer.vim file.\r\n\r\nFeel free to contact me, in case you have any questions\/feedback.","install_details":"Copy this file in your .vim\/plugin folder. I have tried this on free BSD. This should also work on linux and cygwin. ","5":"Copy this file in your .vim\/plugin folder. I have tried this on free BSD. This should also work on linux and cygwin. ","first_name":"Pradeep","6":"Pradeep","last_name":"Kudethur","7":"Kudethur","releases":[{"0":"1299","vim_version":"6.0","1":"6.0","script_version":"1.2","2":"1.2","version_comment":"1. \"More faster than before...................\u00e2\u0080\u009d. We need not do the find operation every time we open the vim, since new file addition is not very frequent to the source base. When one opens the vim, he can just do \"ctrl-p\", which will get the file list from the local database (by default stored in \"filelist\"). If new file\/files are added then one can type 'R' in the file explorer, which will execute the find command from the project root folder and update the file list database. \r\nOne can also rebuild the file list database, while opening the file explorer by pressing F5 (similar to the older versions) \r\nNOTE: All the key mappings can be tuned according to the convenience \r\n\r\n2. Removed duplicate file names from the file explorer. The project might have duplicate file names but in different folders, we can just display one name for all those duplicate and the back end Csope will always support getting the right file (it will give suggestion for duplicate filename). But one advantage of having duplicate files in the file explorer is to know the number of duplicate files, even before selecting\/clicking. There is a knob in the script to enable duplicate files displayed \"fileExplorerDuplicateRemove\". \r\n\r\n3. Also there were some junk files starting with '.' character in my project, by default filenames starting with \u00e2\u0080\u0098.\u00e2\u0080\u0099 character is filtered from the file explorer. If you wish to turn of this filtering feature, then you can change \"fileExplorerDotRemove\"\r\n","3":"1. \"More faster than before...................\u00e2\u0080\u009d. We need not do the find operation every time we open the vim, since new file addition is not very frequent to the source base. When one opens the vim, he can just do \"ctrl-p\", which will get the file list from the local database (by default stored in \"filelist\"). If new file\/files are added then one can type 'R' in the file explorer, which will execute the find command from the project root folder and update the file list database. \r\nOne can also rebuild the file list database, while opening the file explorer by pressing F5 (similar to the older versions) \r\nNOTE: All the key mappings can be tuned according to the convenience \r\n\r\n2. Removed duplicate file names from the file explorer. The project might have duplicate file names but in different folders, we can just display one name for all those duplicate and the back end Csope will always support getting the right file (it will give suggestion for duplicate filename). But one advantage of having duplicate files in the file explorer is to know the number of duplicate files, even before selecting\/clicking. There is a knob in the script to enable duplicate files displayed \"fileExplorerDuplicateRemove\". \r\n\r\n3. Also there were some junk files starting with '.' character in my project, by default filenames starting with \u00e2\u0080\u0098.\u00e2\u0080\u0099 character is filtered from the file explorer. If you wish to turn of this filtering feature, then you can change \"fileExplorerDotRemove\"\r\n","package":"fileexplore.vim","4":"fileexplore.vim","src_id":"4390","5":"4390","creation_date":"1119586992","6":"1119586992"},{"0":"1299","vim_version":"6.0","1":"6.0","script_version":"1.1","2":"1.1","version_comment":"Some minor enhancement for keys <CR> and mouse left button double click. In version 1.0 these keys were responsible for opening the file in the new window (split was based on 'splitBehavior' in the script). But I felt, that everytime opening in a new window might not scale\/be the requirement. Hence I have mapped these two keys to open the file in the previous window. Previous window is the one, you were before going to the file explorer.\r\n\r\nNote: \r\n1. This implementation has a minor problem, which I faced. You are working on a split window session, you close the same and later switch to file explorer for opening a desired file. If you press the <CR> or double click left mouse button, then the file will be opened in the file explorer window itself (which might not be desired).\r\n\r\nWork around: Make sure the previous window exists, before you goto file explorer for opening file using <CR> or mouse click option. In the above case you can just switch to a valid window and then go to the file explorer for file selection using <CR> or mouse click option.\r\n\r\n2. The key 'O' (capital 'o' and not zero) still holds the same old mapping, i.e opening file in new window( the split was based on 'splitBehavior' in the script).","3":"Some minor enhancement for keys <CR> and mouse left button double click. In version 1.0 these keys were responsible for opening the file in the new window (split was based on 'splitBehavior' in the script). But I felt, that everytime opening in a new window might not scale\/be the requirement. Hence I have mapped these two keys to open the file in the previous window. Previous window is the one, you were before going to the file explorer.\r\n\r\nNote: \r\n1. This implementation has a minor problem, which I faced. You are working on a split window session, you close the same and later switch to file explorer for opening a desired file. If you press the <CR> or double click left mouse button, then the file will be opened in the file explorer window itself (which might not be desired).\r\n\r\nWork around: Make sure the previous window exists, before you goto file explorer for opening file using <CR> or mouse click option. In the above case you can just switch to a valid window and then go to the file explorer for file selection using <CR> or mouse click option.\r\n\r\n2. The key 'O' (capital 'o' and not zero) still holds the same old mapping, i.e opening file in new window( the split was based on 'splitBehavior' in the script).","package":"fileexplore.vim","4":"fileexplore.vim","src_id":"4368","5":"4368","creation_date":"1118870213","6":"1118870213"},{"0":"1299","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"fileexplore.vim","4":"fileexplore.vim","src_id":"4355","5":"4355","creation_date":"1118364186","6":"1118364186"}]},"1298":{"script_id":"1298","0":"1298","script_name":"Color Scheme Explorer","1":"Color Scheme Explorer","script_type":"utility","2":"utility","summary":"Easy color scheme browsing","3":"Easy color scheme browsing","description":"Color Scheme Explorer display a list of all available color schemes you have installed on your computer. Once opened, you are able to scroll through the list and select the color scheme of your choice. Once you have selected the color scheme you would like to see, your color scheme will change to reflect that scheme. If you would like to see another scheme, simply select a different one from the list. After you are done explorering all the color schemes, you can press \\'q\\' to quick explorering...\r\n\r\nBy default the command to involke the Color Scheme Explorer is \\':ColorSchemeExplorer\\'","4":"Color Scheme Explorer display a list of all available color schemes you have installed on your computer. Once opened, you are able to scroll through the list and select the color scheme of your choice. Once you have selected the color scheme you would like to see, your color scheme will change to reflect that scheme. If you would like to see another scheme, simply select a different one from the list. After you are done explorering all the color schemes, you can press \\'q\\' to quick explorering...\r\n\r\nBy default the command to involke the Color Scheme Explorer is \\':ColorSchemeExplorer\\'","install_details":"Unzip this file in your vimfiles directory.","5":"Unzip this file in your vimfiles directory.","first_name":"jeff","6":"jeff","last_name":"lanzarotta","7":"lanzarotta","releases":[{"0":"1298","vim_version":"6.0","1":"6.0","script_version":"7.0.1","2":"7.0.1","version_comment":"Initial upload","3":"Initial upload","package":"csExplorer.zip","4":"csExplorer.zip","src_id":"4354","5":"4354","creation_date":"1118299720","6":"1118299720"}]},"1297":{"script_id":"1297","0":"1297","script_name":"rsl.vim","1":"rsl.vim","script_type":"syntax","2":"syntax","summary":"Basic syntax for RSL (droidarena.net).","3":"Basic syntax for RSL (droidarena.net).","description":"I just wanted to get something going, so I added all the events\/commands\/functions, etc.  There are a number of changes I still want to make still.  All suggestions welcome.","4":"I just wanted to get something going, so I added all the events\/commands\/functions, etc.  There are a number of changes I still want to make still.  All suggestions welcome.","install_details":"It's probably simplest to just put this file in your ~\/.vim dir, which (by default) is at the top of your runtimepath.  You'll also need a 'au BufNewFile,BufRead *.rsl setf rsl' in your vimrc.  I'm considering putting that right in the source file, but I think it's inappropriate to do so.","5":"It's probably simplest to just put this file in your ~\/.vim dir, which (by default) is at the top of your runtimepath.  You'll also need a 'au BufNewFile,BufRead *.rsl setf rsl' in your vimrc.  I'm considering putting that right in the source file, but I think it's inappropriate to do so.","first_name":"Paul","6":"Paul","last_name":"Miller","7":"Miller","releases":[{"0":"1297","vim_version":"6.0","1":"6.0","script_version":"1.2.1","2":"1.2.1","version_comment":"I added a couple syntax errors for some things I was screwing up regularly.  If you know of a few more gotchas that should be red, please let me know.\r\n\r\nNew (lame) errors:\r\n   - _ADD &nr0 1 -- looks fine to me, it's not.  the rhs and lhs must both be\r\n     nr-registers...\r\n\r\n  - [section_name] ; this executes during something -- looks fine to me.  It's not.\r\n    The section won't ever execute ever.  Strictly speaking comments should not be on\r\n    the same line as ANY code, but I find that they work everywhere except this.","3":"I added a couple syntax errors for some things I was screwing up regularly.  If you know of a few more gotchas that should be red, please let me know.\r\n\r\nNew (lame) errors:\r\n   - _ADD &nr0 1 -- looks fine to me, it's not.  the rhs and lhs must both be\r\n     nr-registers...\r\n\r\n  - [section_name] ; this executes during something -- looks fine to me.  It's not.\r\n    The section won't ever execute ever.  Strictly speaking comments should not be on\r\n    the same line as ANY code, but I find that they work everywhere except this.","package":"rsl.vim","4":"rsl.vim","src_id":"4395","5":"4395","creation_date":"1119946093","6":"1119946093"},{"0":"1297","vim_version":"6.0","1":"6.0","script_version":"1.2","2":"1.2","version_comment":"... corrected bugs with the message functions (one was missing).\r\n\r\n... fixed a problem with branch highlighting when static data is on the line (e.g.\r\n    IFGT &nr7 2 go_here wasn't blue-ing the go_here).","3":"... corrected bugs with the message functions (one was missing).\r\n\r\n... fixed a problem with branch highlighting when static data is on the line (e.g.\r\n    IFGT &nr7 2 go_here wasn't blue-ing the go_here).","package":"rsl.vim","4":"rsl.vim","src_id":"4381","5":"4381","creation_date":"1119371049","6":"1119371049"},{"0":"1297","vim_version":"6.0","1":"6.0","script_version":"1.1","2":"1.1","version_comment":"I made dozens of needed improvements to the highlighting.  I would call this version useable.","3":"I made dozens of needed improvements to the highlighting.  I would call this version useable.","package":"rsl.vim","4":"rsl.vim","src_id":"4343","5":"4343","creation_date":"1117947989","6":"1117947989"},{"0":"1297","vim_version":"6.0","1":"6.0","script_version":"1.0.1","2":"1.0.1","version_comment":"I _KNEW_ if I uploaded a copy, it'd be the wrong one.  But here is my real version 1.0 -- with a bug fix.","3":"I _KNEW_ if I uploaded a copy, it'd be the wrong one.  But here is my real version 1.0 -- with a bug fix.","package":"rsl.vim","4":"rsl.vim","src_id":"4340","5":"4340","creation_date":"1117803835","6":"1117803835"},{"0":"1297","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"rsl.vim","4":"rsl.vim","src_id":"4339","5":"4339","creation_date":"1117803255","6":"1117803255"}]},"1296":{"script_id":"1296","0":"1296","script_name":"form.vim","1":"form.vim","script_type":"syntax","2":"syntax","summary":"FORM syntax file","3":"FORM syntax file","description":"This is a minor upgrade for the sytax file that comes with the vim distribution, now including some changes due to the latest release FORM 3.x .","4":"This is a minor upgrade for the sytax file that comes with the vim distribution, now including some changes due to the latest release FORM 3.x .","install_details":"Replace this file with the previous form.vim on your system in the syntax tree.","5":"Replace this file with the previous form.vim on your system in the syntax tree.","first_name":"Michael M.","6":"Michael M.","last_name":"Tung","7":"Tung","releases":[{"0":"1296","vim_version":"7.0","1":"7.0","script_version":"2.0","2":"2.0","version_comment":"This version includes the syntax upgrade to FORM 3.2 provided by Thomas Reiter.","3":"This version includes the syntax upgrade to FORM 3.2 provided by Thomas Reiter.","package":"form.vim","4":"form.vim","src_id":"9386","5":"9386","creation_date":"1224762115","6":"1224762115"},{"0":"1296","vim_version":"6.0","1":"6.0","script_version":"1.1","2":"1.1","version_comment":"Initial upload","3":"Initial upload","package":"form.vim","4":"form.vim","src_id":"4338","5":"4338","creation_date":"1117784509","6":"1117784509"}]},"1295":{"script_id":"1295","0":"1295","script_name":"removed","1":"removed","script_type":"utility","2":"utility","summary":"removed","3":"removed","description":"removed (why there's no 'delete script' ?)","4":"removed (why there's no 'delete script' ?)","install_details":"do not download","5":"do not download","first_name":"Rafal","6":"Rafal","last_name":"Sulejman","7":"Sulejman","releases":[{"0":"1295","vim_version":"6.0","1":"6.0","script_version":"removed","2":"removed","version_comment":"Removed","3":"Removed","package":"removed","4":"removed","src_id":"4475","5":"4475","creation_date":"1123493525","6":"1123493525"}]},"1294":{"script_id":"1294","0":"1294","script_name":"nightshade.vim","1":"nightshade.vim","script_type":"color scheme","2":"color scheme","summary":"Bright colors on a black background with a 2nd colorization script for printing","3":"Bright colors on a black background with a 2nd colorization script for printing","description":"NightShade uses a black background with bright highlighting.\r\nNightShade_Print uses similar colors but is designed for printing.\r\n\r\nI put the macro below in my .vimrc file to allow a single key\r\nto change to the nightshade_print colorization, print, then change back.\r\n\r\n   map <F1> :colorscheme nightshade_print<CR> :hardcopy<CR> :colorscheme nightshade<CR>\r\n","4":"NightShade uses a black background with bright highlighting.\r\nNightShade_Print uses similar colors but is designed for printing.\r\n\r\nI put the macro below in my .vimrc file to allow a single key\r\nto change to the nightshade_print colorization, print, then change back.\r\n\r\n   map <F1> :colorscheme nightshade_print<CR> :hardcopy<CR> :colorscheme nightshade<CR>\r\n","install_details":"tar -xvzf nightshade.tar.gz\r\nmove the nightshade.vim and nightshade_print.vim files to the vim colors subdirectory.\r\nIf desired, create a macro to switch to the print colorscheme, print, and switch back as described in the README file.","5":"tar -xvzf nightshade.tar.gz\r\nmove the nightshade.vim and nightshade_print.vim files to the vim colors subdirectory.\r\nIf desired, create a macro to switch to the print colorscheme, print, and switch back as described in the README file.","first_name":"Dave","6":"Dave","last_name":"Turner","7":"Turner","releases":[{"0":"1294","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"nightshade.tar.gz","4":"nightshade.tar.gz","src_id":"4335","5":"4335","creation_date":"1117734961","6":"1117734961"}]},"1293":{"script_id":"1293","0":"1293","script_name":"Pida","1":"Pida","script_type":"utility","2":"utility","summary":"A graphical IDE that uses Vim as its editor over the client-server protocol.","3":"A graphical IDE that uses Vim as its editor over the client-server protocol.","description":"I personally believe that Pida offers a unique experience for programmers and other Vim users. It is essentially an IDE, except that it lives entirely outside the text editor (Vim) and all the other tools it uses.\r\n\r\nIt is written in Python, and uses the GTK toolkit.\r\n\r\nOnce installed, you can run Pida to connect to existing \"vim -g\" or \"vim --servername <name>\" sessions, or run in embedded mode, to embed a single instance of Vim much like a conventional IDE.\r\n\r\nPlease visit http:\/\/pida.berlios.de\/ for the application website (there may be newer verisons there) for more details, or see a (large) screenshot of pida being used to develop itself at http:\/\/pida.berlios.de\/images\/5\/5c\/Pida_embed.png.\r\n\r\nPida is still early at this stage, and I very much appreciate all types of bug reporting, advice, criticism etc.","4":"I personally believe that Pida offers a unique experience for programmers and other Vim users. It is essentially an IDE, except that it lives entirely outside the text editor (Vim) and all the other tools it uses.\r\n\r\nIt is written in Python, and uses the GTK toolkit.\r\n\r\nOnce installed, you can run Pida to connect to existing \"vim -g\" or \"vim --servername <name>\" sessions, or run in embedded mode, to embed a single instance of Vim much like a conventional IDE.\r\n\r\nPlease visit http:\/\/pida.berlios.de\/ for the application website (there may be newer verisons there) for more details, or see a (large) screenshot of pida being used to develop itself at http:\/\/pida.berlios.de\/images\/5\/5c\/Pida_embed.png.\r\n\r\nPida is still early at this stage, and I very much appreciate all types of bug reporting, advice, criticism etc.","install_details":"Decompress the package and use the command:\r\n\r\npython setup.py install\r\n\r\n(you may need root access)\r\n\r\nNote: We also provide Debian packages at http:\/\/pida.berlios.de\/","5":"Decompress the package and use the command:\r\n\r\npython setup.py install\r\n\r\n(you may need root access)\r\n\r\nNote: We also provide Debian packages at http:\/\/pida.berlios.de\/","first_name":"Ali","6":"Ali","last_name":"Afshar","7":"Afshar","releases":[{"0":"1293","vim_version":"6.0","1":"6.0","script_version":"0.2.2","2":"0.2.2","version_comment":";Pastebin plugin : Allows pasting of entered, and yanked text to the rafb.net\r\nand #Pida pastebins.\r\n\r\n;Culebra plugin : Editor using GTSourceView, including syntax highlighting,\r\nblock indent, block comment, and intelligent Python code completion, can be used in\r\nplace of Vim.\r\n\r\n;Per-filetype Plugins : Plugins can be optionally displayed and hidden for\r\ndifferent file-types.\r\n\r\n;Mercurial support : Basic support has been added to the project plugin to\r\nsupport the Mercurial version control system.\r\n\r\n;Filetype handling : Plugins can be configured to be displayed per filetype.\r\n\r\n;Terminal support : Xterm can be used in place of the internal VTE widget.\r\n\r\n;Layout : Added options for alternate layouts.\r\n\r\n;Buffer list : Display parent directory of buffer filename in buffer list.\r\n\r\n;First time-run wizard to select required components.","3":";Pastebin plugin : Allows pasting of entered, and yanked text to the rafb.net\r\nand #Pida pastebins.\r\n\r\n;Culebra plugin : Editor using GTSourceView, including syntax highlighting,\r\nblock indent, block comment, and intelligent Python code completion, can be used in\r\nplace of Vim.\r\n\r\n;Per-filetype Plugins : Plugins can be optionally displayed and hidden for\r\ndifferent file-types.\r\n\r\n;Mercurial support : Basic support has been added to the project plugin to\r\nsupport the Mercurial version control system.\r\n\r\n;Filetype handling : Plugins can be configured to be displayed per filetype.\r\n\r\n;Terminal support : Xterm can be used in place of the internal VTE widget.\r\n\r\n;Layout : Added options for alternate layouts.\r\n\r\n;Buffer list : Display parent directory of buffer filename in buffer list.\r\n\r\n;First time-run wizard to select required components.","package":"pida_0.2.2.tar.gz","4":"pida_0.2.2.tar.gz","src_id":"4460","5":"4460","creation_date":"1123221635","6":"1123221635"}]},"1292":{"script_id":"1292","0":"1292","script_name":"keywords.vim","1":"keywords.vim","script_type":"utility","2":"utility","summary":"mappings to move and quote iskeyword text","3":"mappings to move and quote iskeyword text","description":"This scripts provides two functionalities that use the iskeyword setting of\r\nthe current buffer.\r\n\r\nThe following mappings are provided for moving keywords in normal mode:\r\n\r\n    <C-Up>   : exchange the current keyword with the previous one.\r\n    <C-Down> : exchange the current keyword with the next one.\r\n\r\nThese mappings can be changed by changing the value of the following variables.\r\n\r\n    let g:keywords_MoveWordL = '<C-Up>'\r\n    let g:keywords_MoveWordR = '<C-Down>'\r\n\r\nAlso there exists mappings for adding\/deleting \"quotes\" to\/from a keyword or a\r\nvisually selected area. The mappings are as follows:\r\n\r\n   qw, q\"  : double quote\r\n   qs, q'  : single quote\r\n   qe, q`  : quote execute\r\n   q[, q]  : quote with square brackets\r\n   q{, q}  : quote with brackets\r\n   q(, q)  : quote with parantheses\r\n   q<, q>  : quote with xml style tag.\r\n\r\nIf you wish to provide a different map leader than 'q' use this variable:\r\n\r\n   let g:keywords_MapLeader = 'q'\r\n\r\nThere is one normal mode mapping for removing quotes from a keyword:\r\n\r\n   wq  :  removes non iskeyword material around the current keyword.\r\n\r\nConsider sending an email if you have any comments or suggestions :-)\r\n","4":"This scripts provides two functionalities that use the iskeyword setting of\r\nthe current buffer.\r\n\r\nThe following mappings are provided for moving keywords in normal mode:\r\n\r\n    <C-Up>   : exchange the current keyword with the previous one.\r\n    <C-Down> : exchange the current keyword with the next one.\r\n\r\nThese mappings can be changed by changing the value of the following variables.\r\n\r\n    let g:keywords_MoveWordL = '<C-Up>'\r\n    let g:keywords_MoveWordR = '<C-Down>'\r\n\r\nAlso there exists mappings for adding\/deleting \"quotes\" to\/from a keyword or a\r\nvisually selected area. The mappings are as follows:\r\n\r\n   qw, q\"  : double quote\r\n   qs, q'  : single quote\r\n   qe, q`  : quote execute\r\n   q[, q]  : quote with square brackets\r\n   q{, q}  : quote with brackets\r\n   q(, q)  : quote with parantheses\r\n   q<, q>  : quote with xml style tag.\r\n\r\nIf you wish to provide a different map leader than 'q' use this variable:\r\n\r\n   let g:keywords_MapLeader = 'q'\r\n\r\nThere is one normal mode mapping for removing quotes from a keyword:\r\n\r\n   wq  :  removes non iskeyword material around the current keyword.\r\n\r\nConsider sending an email if you have any comments or suggestions :-)\r\n","install_details":"put this script into the vim plugin directory or source it from within vim","5":"put this script into the vim plugin directory or source it from within vim","first_name":"Anders","6":"Anders","last_name":"Th\u00c3\u00b8gersen","7":"Th\u00c3\u00b8gersen","releases":[{"0":"1292","vim_version":"6.0","1":"6.0","script_version":"0.2","2":"0.2","version_comment":"Discovered a small bug.","3":"Discovered a small bug.","package":"keywords.vim","4":"keywords.vim","src_id":"4324","5":"4324","creation_date":"1117212709","6":"1117212709"},{"0":"1292","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"keywords.vim","4":"keywords.vim","src_id":"4323","5":"4323","creation_date":"1117212416","6":"1117212416"}]},"1291":{"script_id":"1291","0":"1291","script_name":"luarefvim","1":"luarefvim","script_type":"utility","2":"utility","summary":"Lua reference manual","3":"Lua reference manual","description":"This a Vim help file containing references for Lua 5.0 and 5.1, and it is -- with a few exceptions and adaptations -- a copy of the Lua 5.0 and Lua 5.1 reference manuals. Lua is a lightweight script language; see http:\/\/www.lua.org .\r\n\r\nSimilarly to CRefVim (from where a lot of ideas were drawn), you can easily search for references for words under the cursor, visually selected words, and manual contents.","4":"This a Vim help file containing references for Lua 5.0 and 5.1, and it is -- with a few exceptions and adaptations -- a copy of the Lua 5.0 and Lua 5.1 reference manuals. Lua is a lightweight script language; see http:\/\/www.lua.org .\r\n\r\nSimilarly to CRefVim (from where a lot of ideas were drawn), you can easily search for references for words under the cursor, visually selected words, and manual contents.","install_details":"This reference consists of three files: the manual itself, lua50refvim.txt for Lua version 5.0 and lua51refvim.txt for Lua version 5.1, a plugin file, luarefvim.vim, to load key bindings, and a help file syntax extension, help.vim. To install luarefvim, copy the manual for the version you want, the plugin and the help files to their respective locations: lua5Xrefvim.txt to $VIMUSERHOME\/doc, luarefvim.vim to $VIMUSERHOME\/plugin, and help.vim to $VIMUSERHOME\/after\/syntax, where $VIMUSERHOME is $HOME\/.vim on Un*x systems or $HOME\/vimfiles on Win32.\r\n\r\nFinally, to generate the tags, change dir to $VIMUSERHOME\/doc, start Vim, and issue ':helptags .' . For more information on installing help files, call ':help add-local-help'.","5":"This reference consists of three files: the manual itself, lua50refvim.txt for Lua version 5.0 and lua51refvim.txt for Lua version 5.1, a plugin file, luarefvim.vim, to load key bindings, and a help file syntax extension, help.vim. To install luarefvim, copy the manual for the version you want, the plugin and the help files to their respective locations: lua5Xrefvim.txt to $VIMUSERHOME\/doc, luarefvim.vim to $VIMUSERHOME\/plugin, and help.vim to $VIMUSERHOME\/after\/syntax, where $VIMUSERHOME is $HOME\/.vim on Un*x systems or $HOME\/vimfiles on Win32.\r\n\r\nFinally, to generate the tags, change dir to $VIMUSERHOME\/doc, start Vim, and issue ':helptags .' . For more information on installing help files, call ':help add-local-help'.","first_name":"Luis","6":"Luis","last_name":"Carvalho","7":"Carvalho","releases":[{"0":"1291","vim_version":"6.0","1":"6.0","script_version":"0.2","2":"0.2","version_comment":"Added reference manual for Lua version 5.1.","3":"Added reference manual for Lua version 5.1.","package":"luarefvim.zip","4":"luarefvim.zip","src_id":"6470","5":"6470","creation_date":"1164472337","6":"1164472337"},{"0":"1291","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"luarefvim.zip","4":"luarefvim.zip","src_id":"4321","5":"4321","creation_date":"1117108413","6":"1117108413"}]},"1290":{"script_id":"1290","0":"1290","script_name":"LogiPat","1":"LogiPat","script_type":"utility","2":"utility","summary":"Boolean-Logic Patterns","3":"Boolean-Logic Patterns","description":"LogiPat takes Boolean logic arguments and produces a regular expression which is used to search for a line satisfying the logic.  The search register (@\/) is initialized with the resulting regular expression, so repeating such searches is as easy as repeating any search.  A series of examples follows:\r\n\r\n:LogiPat \"abc\"\r\n\t\twill search for lines containing the string \"abc\"\r\n\r\n:LogiPat !\"abc\"\r\n\t\twill search for lines which don't contain the string \"abc\"\r\n\r\n:LogiPat \"abc\"|\"def\"\r\n\t\twill search for lines which contain either the string \"abc\" or the string \"def\"\r\n\r\n:LogiPat !(\"abc\"|\"def\")\r\n\t\twill search for lines which don't contain either of the strings \"abc\" or \"def\"\r\n\r\n:LogiPat \"abc\"&\"def\"\r\n\t\twill search for lines which contain both of the strings \"abc\" and \"def\"\r\n\r\n:let pat= LogiPat('!\"abc\"')\r\n\t\twill return the regular expression which will match all lines not containing \"abc\".  The double quotes are needed to pass normal patterns to LogiPat, and differentiate such patterns from boolean logic operators.\r\n\r\n(alpha\/beta version available at http:\/\/www.drchip.org\/astronaut\/vim\/index.html#LOGIPAT)\r\n","4":"LogiPat takes Boolean logic arguments and produces a regular expression which is used to search for a line satisfying the logic.  The search register (@\/) is initialized with the resulting regular expression, so repeating such searches is as easy as repeating any search.  A series of examples follows:\r\n\r\n:LogiPat \"abc\"\r\n\t\twill search for lines containing the string \"abc\"\r\n\r\n:LogiPat !\"abc\"\r\n\t\twill search for lines which don't contain the string \"abc\"\r\n\r\n:LogiPat \"abc\"|\"def\"\r\n\t\twill search for lines which contain either the string \"abc\" or the string \"def\"\r\n\r\n:LogiPat !(\"abc\"|\"def\")\r\n\t\twill search for lines which don't contain either of the strings \"abc\" or \"def\"\r\n\r\n:LogiPat \"abc\"&\"def\"\r\n\t\twill search for lines which contain both of the strings \"abc\" and \"def\"\r\n\r\n:let pat= LogiPat('!\"abc\"')\r\n\t\twill return the regular expression which will match all lines not containing \"abc\".  The double quotes are needed to pass normal patterns to LogiPat, and differentiate such patterns from boolean logic operators.\r\n\r\n(alpha\/beta version available at http:\/\/www.drchip.org\/astronaut\/vim\/index.html#LOGIPAT)\r\n","install_details":"LogiPat is distributed via a \"vimball\":  To install it:\r\nvim LogiPat.vba.gz\r\n:so %\r\n:q","5":"LogiPat is distributed via a \"vimball\":  To install it:\r\nvim LogiPat.vba.gz\r\n:so %\r\n:q","first_name":"Charles","6":"Charles","last_name":"Campbell","7":"Campbell","releases":[{"0":"1290","vim_version":"7.0","1":"7.0","script_version":"3","2":"3","version_comment":"New: :ELP will echo the search pattern that logipat generates.\r\nFixed: LP_Or fixed; it encapsulates its output in \\%(...\\) parentheses\r\n","3":"New: :ELP will echo the search pattern that logipat generates.\r\nFixed: LP_Or fixed; it encapsulates its output in \\%(...\\) parentheses\r\n","package":"LogiPat.vba.gz","4":"LogiPat.vba.gz","src_id":"19635","5":"19635","creation_date":"1363182076","6":"1363182076"},{"0":"1290","vim_version":"6.0","1":"6.0","script_version":"2","2":"2","version_comment":"bugfix : LPF and LogiPatFlags now work\r\n","3":"bugfix : LPF and LogiPatFlags now work\r\n","package":"LogiPat.vim.gz","4":"LogiPat.vim.gz","src_id":"5190","5":"5190","creation_date":"1139812875","6":"1139812875"},{"0":"1290","vim_version":"6.0","1":"6.0","script_version":"1","2":"1","version_comment":"Transforms Boolean logic patterns into regular expression patterns.  \"abc\"|\"def\", !\"ghi\", etc","3":"Transforms Boolean logic patterns into regular expression patterns.  \"abc\"|\"def\", !\"ghi\", etc","package":"LogiPat.vim.gz","4":"LogiPat.vim.gz","src_id":"4315","5":"4315","creation_date":"1116832996","6":"1116832996"}]},"1289":{"script_id":"1289","0":"1289","script_name":"otherfile.vim","1":"otherfile.vim","script_type":"utility","2":"utility","summary":"Allows you to quickly switch between .h\/.c, .h\/.cc, .ads\/.adb etc","3":"Allows you to quickly switch between .h\/.c, .h\/.cc, .ads\/.adb etc","description":"Press F8 to switch between header and source files, or any other kind of paired files.\r\nIn the present state, handles C\/C++\/Ada files, but can be (really) easily modified to handle more.\r\nIf no alternate file is found, asks for the file name to create. Press ESC to cancel if you want.\r\nBy default maps <F8> to do the job; you may change this (see the end of file).","4":"Press F8 to switch between header and source files, or any other kind of paired files.\r\nIn the present state, handles C\/C++\/Ada files, but can be (really) easily modified to handle more.\r\nIf no alternate file is found, asks for the file name to create. Press ESC to cancel if you want.\r\nBy default maps <F8> to do the job; you may change this (see the end of file).","install_details":"Just put this file in your Vim \"plugin\" directory (or ~\/.vim\/plugin) or load it manually via \"source\" Vim command.","5":"Just put this file in your Vim \"plugin\" directory (or ~\/.vim\/plugin) or load it manually via \"source\" Vim command.","first_name":"Andrey","6":"Andrey","last_name":"Tarantsov","7":"Tarantsov","releases":[{"0":"1289","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"other.vim","4":"other.vim","src_id":"4312","5":"4312","creation_date":"1116732268","6":"1116732268"}]},"1288":{"script_id":"1288","0":"1288","script_name":"otherfile.vim","1":"otherfile.vim","script_type":"utility","2":"utility","summary":"Allows you to quickly switch between .h\/.c, .h\/.cc, .ads\/.adb etc","3":"Allows you to quickly switch between .h\/.c, .h\/.cc, .ads\/.adb etc","description":"Press F8 to switch between header and source files, or any other kind of paired files.\r\nIn the present state, handles C\/C++\/Ada files, but can be (really) easily modified to handle more.\r\nIf no alternate file is found, asks for the file name to create. Press ESC to cancel if you want.\r\nBy default maps <F8> to do the job; you may change this (see the end of file).","4":"Press F8 to switch between header and source files, or any other kind of paired files.\r\nIn the present state, handles C\/C++\/Ada files, but can be (really) easily modified to handle more.\r\nIf no alternate file is found, asks for the file name to create. Press ESC to cancel if you want.\r\nBy default maps <F8> to do the job; you may change this (see the end of file).","install_details":"Just put this file in your Vim \\\"plugin\\\" directory (or ~\/.vim\/plugin) or load it manually via \\\"source\\\" Vim command.","5":"Just put this file in your Vim \\\"plugin\\\" directory (or ~\/.vim\/plugin) or load it manually via \\\"source\\\" Vim command.","first_name":"Andrey","6":"Andrey","last_name":"Tarantsov","7":"Tarantsov","releases":[{"0":"1288","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"other.vim","4":"other.vim","src_id":"4311","5":"4311","creation_date":"1116732258","6":"1116732258"}]},"1287":{"script_id":"1287","0":"1287","script_name":"tabs.vim","1":"tabs.vim","script_type":"utility","2":"utility","summary":"Allows to quickly switch between buffers and displays them as tabs.","3":"Allows to quickly switch between buffers and displays them as tabs.","description":"Adds a special \"tab line\" at the bottom of Vim main window. Make a tab for the current buffer by pressing \\t. The tab gets highlighted when the buffer is activated. Switch between tabs by pressing \\1, \\2, ..., \\9.\r\nSee detailed instructions at the top of the script's source.","4":"Adds a special \"tab line\" at the bottom of Vim main window. Make a tab for the current buffer by pressing \\t. The tab gets highlighted when the buffer is activated. Switch between tabs by pressing \\1, \\2, ..., \\9.\r\nSee detailed instructions at the top of the script's source.","install_details":"Copy the script to your Vim \"plugin\" directory, or to ~\/.vim\/plugin\/.\r\nAlso you may source the script manually when you need it.","5":"Copy the script to your Vim \"plugin\" directory, or to ~\/.vim\/plugin\/.\r\nAlso you may source the script manually when you need it.","first_name":"Andrey","6":"Andrey","last_name":"Tarantsov","7":"Tarantsov","releases":[{"0":"1287","vim_version":"6.0","1":"6.0","script_version":"1.0a","2":"1.0a","version_comment":"Here's a working version; the previous one was incidentally made unusable during preparation for publication. Sorry!","3":"Here's a working version; the previous one was incidentally made unusable during preparation for publication. Sorry!","package":"tabs.vim","4":"tabs.vim","src_id":"4309","5":"4309","creation_date":"1116646013","6":"1116646013"},{"0":"1287","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"tabs.vim","4":"tabs.vim","src_id":"4308","5":"4308","creation_date":"1116638937","6":"1116638937"}]},"1286":{"script_id":"1286","0":"1286","script_name":"sadic.tgz","1":"sadic.tgz","script_type":"utility","2":"utility","summary":"Japanese to  English and English to Japanese translator","3":"Japanese to  English and English to Japanese translator","description":"This is a handy utility to translate text from Japanese to English and vice versa. \r\nIt uses the excite.co.jp services to translate the text then displays the result in \r\nthe standard output.\r\n\r\nsadict was created to be integrated with vim and mutt , \r\nIf you add the following lines into your ~\/.vimrc \r\n\r\nvmap j :w! \/tmp\/.vim.msg.en<cr>:!sadic -j  < \/tmp\/.vim.msg.en<cr>\r\nvmap ,j :w! \/tmp\/.vim.msg.en<cr><esc>`>o<cr><esc>:r !sadic -j < \/tmp\/.vim.msg.en<cr>\r\nvmap e :w! \/tmp\/.vim.msg.jp<cr>:!sadic < \/tmp\/.msg.jp<cr>\r\nvmap ,e :w! \/tmp\/.vim.msg.jp<cr><esc>`>o<cr><esc>:r !sadic < \/tmp\/.vim.msg.jp<cr>\r\n\r\nThen you can visually select a text region (by pressing Shift-V then\r\nmoving the cursor), then when you press \"j\" , the text will be translated \r\nfrom English to Japanese.\r\n\r\n\",j\" translates the text from english to Japanese then appends the result (japanese text) \r\nright after the visually selection region.\r\n\r\nThe \"e\" and \",e\" mappings do the same thing except that they translate text from\r\nJapanese to English.\r\n\r\nFor Mutt , you can add the following into your .muttrc\r\nmacro pager   j          \"v\\n| nkf -e | sadic -j | less \\nq<left>\"\r\nmacro pager   e         \"v\\n| nkf -e | sadic  | less \\nq<left>\"\r\n\r\nThen , while viewing your e-mails , you can press \"j\" to translate from English\r\nto Japanese. and \"e\" to translate from Japanese to English.","4":"This is a handy utility to translate text from Japanese to English and vice versa. \r\nIt uses the excite.co.jp services to translate the text then displays the result in \r\nthe standard output.\r\n\r\nsadict was created to be integrated with vim and mutt , \r\nIf you add the following lines into your ~\/.vimrc \r\n\r\nvmap j :w! \/tmp\/.vim.msg.en<cr>:!sadic -j  < \/tmp\/.vim.msg.en<cr>\r\nvmap ,j :w! \/tmp\/.vim.msg.en<cr><esc>`>o<cr><esc>:r !sadic -j < \/tmp\/.vim.msg.en<cr>\r\nvmap e :w! \/tmp\/.vim.msg.jp<cr>:!sadic < \/tmp\/.msg.jp<cr>\r\nvmap ,e :w! \/tmp\/.vim.msg.jp<cr><esc>`>o<cr><esc>:r !sadic < \/tmp\/.vim.msg.jp<cr>\r\n\r\nThen you can visually select a text region (by pressing Shift-V then\r\nmoving the cursor), then when you press \"j\" , the text will be translated \r\nfrom English to Japanese.\r\n\r\n\",j\" translates the text from english to Japanese then appends the result (japanese text) \r\nright after the visually selection region.\r\n\r\nThe \"e\" and \",e\" mappings do the same thing except that they translate text from\r\nJapanese to English.\r\n\r\nFor Mutt , you can add the following into your .muttrc\r\nmacro pager   j          \"v\\n| nkf -e | sadic -j | less \\nq<left>\"\r\nmacro pager   e         \"v\\n| nkf -e | sadic  | less \\nq<left>\"\r\n\r\nThen , while viewing your e-mails , you can press \"j\" to translate from English\r\nto Japanese. and \"e\" to translate from Japanese to English.","install_details":"0- Download and extract sadic.tgz somewhere\r\n\r\n1- Edit the file \"install\" and change the variable \"prefix\".  The default\r\ninstallation path is your home directory $HOME\/bin . The location \"prefix\"\r\nmust be in your shell $PATH.\r\n\r\n2- Run the installation script $.\/install\r\n\r\n3- Add the following into your vimrc  :\r\n\r\nvmap j :w! \/tmp\/.vim.msg.en<cr>:!sadic -j  < \/tmp\/.vim.msg.en<cr>\r\nvmap ,j :w! \/tmp\/.vim.msg.en<cr><esc>`>o<cr><esc>:r !sadic -j < \/tmp\/.vim.msg.en<cr>\r\nvmap e :w! \/tmp\/.vim.msg.jp<cr>:!sadic < \/tmp\/.msg.jp<cr>\r\nvmap ,e :w! \/tmp\/.vim.msg.jp<cr><esc>`>o<cr><esc>:r !sadic < \/tmp\/.vim.msg.jp<cr>\r\n\r\n4- Add the following in your .muttrc :\r\n\r\nmacro pager   j          \"v\\n| nkf -e | sadic -j | less \\nq<left>\"\r\nmacro pager   e         \"v\\n| nkf -e | sadic  | less \\nq<left>\"\r\n\r\n","5":"0- Download and extract sadic.tgz somewhere\r\n\r\n1- Edit the file \"install\" and change the variable \"prefix\".  The default\r\ninstallation path is your home directory $HOME\/bin . The location \"prefix\"\r\nmust be in your shell $PATH.\r\n\r\n2- Run the installation script $.\/install\r\n\r\n3- Add the following into your vimrc  :\r\n\r\nvmap j :w! \/tmp\/.vim.msg.en<cr>:!sadic -j  < \/tmp\/.vim.msg.en<cr>\r\nvmap ,j :w! \/tmp\/.vim.msg.en<cr><esc>`>o<cr><esc>:r !sadic -j < \/tmp\/.vim.msg.en<cr>\r\nvmap e :w! \/tmp\/.vim.msg.jp<cr>:!sadic < \/tmp\/.msg.jp<cr>\r\nvmap ,e :w! \/tmp\/.vim.msg.jp<cr><esc>`>o<cr><esc>:r !sadic < \/tmp\/.vim.msg.jp<cr>\r\n\r\n4- Add the following in your .muttrc :\r\n\r\nmacro pager   j          \"v\\n| nkf -e | sadic -j | less \\nq<left>\"\r\nmacro pager   e         \"v\\n| nkf -e | sadic  | less \\nq<left>\"\r\n\r\n","first_name":"saber","6":"saber","last_name":"zrelli","7":"zrelli","releases":[{"0":"1286","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial Upload ","3":"Initial Upload ","package":"sadic.tgz","4":"sadic.tgz","src_id":"4306","5":"4306","creation_date":"1116580952","6":"1116580952"}]},"1285":{"script_id":"1285","0":"1285","script_name":"nasl.vim","1":"nasl.vim","script_type":"syntax","2":"syntax","summary":"small and more automated nasl syntax file","3":"small and more automated nasl syntax file","description":"Small syntax file for the Nessus Attack Scripting Language. It uses the built-in functions and constants found in nasl_init.c and the keywords found in nasl_grammar.tab.c. Arguments like english:, deutsch:, data:,etc are matched using regexes instead of fixed names.","4":"Small syntax file for the Nessus Attack Scripting Language. It uses the built-in functions and constants found in nasl_init.c and the keywords found in nasl_grammar.tab.c. Arguments like english:, deutsch:, data:,etc are matched using regexes instead of fixed names.","install_details":"add this to your .vimrc:\r\nsyntax on\r\nau BufEnter *.nasl setfiletype nasl\r\n\r\nand place nasl.vim inside your ~\/.vim\/syntax\/ directory (or any\r\nother syntax directory below your 'runtimepath')\r\n\r\nThanks Thomas Arendsen","5":"add this to your .vimrc:\r\nsyntax on\r\nau BufEnter *.nasl setfiletype nasl\r\n\r\nand place nasl.vim inside your ~\/.vim\/syntax\/ directory (or any\r\nother syntax directory below your 'runtimepath')\r\n\r\nThanks Thomas Arendsen","first_name":"Herman","6":"Herman","last_name":"Polloni","7":"Polloni","releases":[{"0":"1285","vim_version":"6.0","1":"6.0","script_version":"0.3","2":"0.3","version_comment":"Added hilighting for parenthesis and bracket matching errors","3":"Added hilighting for parenthesis and bracket matching errors","package":"nasl.vim","4":"nasl.vim","src_id":"4313","5":"4313","creation_date":"1116760545","6":"1116760545"},{"0":"1285","vim_version":"6.0","1":"6.0","script_version":"0.2","2":"0.2","version_comment":"functions inside a parenthesis now display correctly.","3":"functions inside a parenthesis now display correctly.","package":"nasl.vim","4":"nasl.vim","src_id":"4307","5":"4307","creation_date":"1116595022","6":"1116595022"},{"0":"1285","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"nasl.vim","4":"nasl.vim","src_id":"4301","5":"4301","creation_date":"1116539258","6":"1116539258"}]},"1284":{"script_id":"1284","0":"1284","script_name":"TortoiseSVN.vim","1":"TortoiseSVN.vim","script_type":"utility","2":"utility","summary":"Support for TortoiseSVN (a subversion client for Windows)","3":"Support for TortoiseSVN (a subversion client for Windows)","description":"TortoiseSVN.vim will commit the current buffer to your subversion \r\nrepository everytime you update the file or once per session (see \r\n|tortoiseSvnCommitOnce|). The advantage over using command line svn \r\ncommands is that you get the TortoiseSVN GUI for committing files, \r\nbrowsing the repository etc.\r\n\r\nSome aspects of this plugin can be configured by setting the following \r\nvariables in your |vimrc| file.\r\n\r\n    g:tortoiseSvnCmd :: The path to \"TortoiseProc.exe\".\r\n\r\n    g:tortoiseSvnCommitOnce, b:tortoiseSvnCommitOnce :: If true, the \r\n    buffer will be committed to the subversion repository only once \r\n    (i.e., when saving the file for the first time).\r\n\r\n    g:tortoiseSvnMenuPrefix :: If empty (''), no menu will be installed.\r\n\r\n    g:tortoiseSvnStartCmd :: A command for detaching TortoiseProc.exe \r\n    from the shell (e.g., start).\r\n\r\n    g:tortoiseSvnInstallAutoCmd :: If false, no autocmd will be \r\n    installed.\r\n","4":"TortoiseSVN.vim will commit the current buffer to your subversion \r\nrepository everytime you update the file or once per session (see \r\n|tortoiseSvnCommitOnce|). The advantage over using command line svn \r\ncommands is that you get the TortoiseSVN GUI for committing files, \r\nbrowsing the repository etc.\r\n\r\nSome aspects of this plugin can be configured by setting the following \r\nvariables in your |vimrc| file.\r\n\r\n    g:tortoiseSvnCmd :: The path to \"TortoiseProc.exe\".\r\n\r\n    g:tortoiseSvnCommitOnce, b:tortoiseSvnCommitOnce :: If true, the \r\n    buffer will be committed to the subversion repository only once \r\n    (i.e., when saving the file for the first time).\r\n\r\n    g:tortoiseSvnMenuPrefix :: If empty (''), no menu will be installed.\r\n\r\n    g:tortoiseSvnStartCmd :: A command for detaching TortoiseProc.exe \r\n    from the shell (e.g., start).\r\n\r\n    g:tortoiseSvnInstallAutoCmd :: If false, no autocmd will be \r\n    installed.\r\n","install_details":"This plugin relies on TortoiseSVN (http:\/\/tortoisesvn.tigris.org\/) to be \r\ninstalled. Windows only.\r\n\r\nCopy TortoiseSVN.vim to your plugin directory (e.g., ~\/.vim\/plugins\/).  \r\nMake sure |g:tortoiseSvnCmd| points to \"TortoiseProc.exe\".\r\n\r\n\r\nAlso available via git\r\nhttp:\/\/github.com\/tomtom\/TortoiseSVN_vim","5":"This plugin relies on TortoiseSVN (http:\/\/tortoisesvn.tigris.org\/) to be \r\ninstalled. Windows only.\r\n\r\nCopy TortoiseSVN.vim to your plugin directory (e.g., ~\/.vim\/plugins\/).  \r\nMake sure |g:tortoiseSvnCmd| points to \"TortoiseProc.exe\".\r\n\r\n\r\nAlso available via git\r\nhttp:\/\/github.com\/tomtom\/TortoiseSVN_vim","first_name":"Tom","6":"Tom","last_name":"Link","7":"Link","releases":[{"0":"1284","vim_version":"6.0","1":"6.0","script_version":"0.3","2":"0.3","version_comment":"- g:tortoiseSvnInstallAutoCmd: 0=disable autocmd; 1=commit on BufUnload; 2=commit on BufWritePost\r\n- most function accept now a filename as optional argument\r\n- fixed problem with some \"fileless\" buffers\r\n- fixed problem when leaving vim\r\n","3":"- g:tortoiseSvnInstallAutoCmd: 0=disable autocmd; 1=commit on BufUnload; 2=commit on BufWritePost\r\n- most function accept now a filename as optional argument\r\n- fixed problem with some \"fileless\" buffers\r\n- fixed problem when leaving vim\r\n","package":"TortoiseSVN.zip","4":"TortoiseSVN.zip","src_id":"4506","5":"4506","creation_date":"1124595391","6":"1124595391"},{"0":"1284","vim_version":"6.0","1":"6.0","script_version":"0.2","2":"0.2","version_comment":"- Make sure this works with cmd.exe as &shell (which is Windows standard)\r\n- Make <SID>CanonicFileName(fname) &shell sensible\r\n- Fixed a cut&paste error in the menu\r\n","3":"- Make sure this works with cmd.exe as &shell (which is Windows standard)\r\n- Make <SID>CanonicFileName(fname) &shell sensible\r\n- Fixed a cut&paste error in the menu\r\n","package":"TortoiseSVN.zip","4":"TortoiseSVN.zip","src_id":"4298","5":"4298","creation_date":"1116499662","6":"1116499662"},{"0":"1284","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"TortoiseSVN.zip","4":"TortoiseSVN.zip","src_id":"4288","5":"4288","creation_date":"1116331533","6":"1116331533"}]},"1283":{"script_id":"1283","0":"1283","script_name":"TinyBufferExplorer","1":"TinyBufferExplorer","script_type":"utility","2":"utility","summary":"A 1-file buffer list plugin with Grouping","3":"A 1-file buffer list plugin with Grouping","description":"[Key features]\r\n\r\n    1. incremental collection of buffers\r\n      - buffer information are collected in the background\r\n      - less time requred showing lists\r\n\r\n    2. grouping\r\n      - it suppresses excessive information\r\n      - it's easy to switch among groups\r\n      - defined groups:\r\n        - Directory groups corresponding to buffers\r\n        - MRU(Most Recently Used buffers) group\r\n        - Search group\r\n        - [new] All buffers group\r\n\r\n    3. ease of accessing buffers and groups\r\n      - the MRU group can list buffers you are likely to edit\r\n      - the group list supports you switching among groups\r\n      - it's easy to switch to the Directory group in which\r\n        the current buffer is\r\n\r\n    4. [new] selectable UIs\r\n      - \"Fullfeatured\" (default), SimpleGroup and Minimal\r\n      - \"SimpleGroup\": one window, supports switching groups\r\n      - \"Minimal\": one window, shows all buffers\r\n\r\n    5. customizable list format (Fullfeatured UI only)\r\n\r\n[How to use it? (and screenshots)]\r\n\r\nThere are 3 UIs now. (You can choose by command)\r\n\r\nFullfeatured UI: \r\n  execute :TinyBufferExplorer or :TBE.\r\n  http:\/\/bitbucket.org\/shu\/tinybufferexplorer\/downloads\/fullfeatured.png\r\n\r\nSimpleGroup UI:\r\n  execute :TBESimpleGroup.\r\n  http:\/\/bitbucket.org\/shu\/tinybufferexplorer\/downloads\/simplegroup.png\r\n\r\nMinimal UI:\r\n  execute :TBEMinimal.\r\n  http:\/\/bitbucket.org\/shu\/tinybufferexplorer\/downloads\/minimal.png\r\n\r\nFor more detailed descriptions, read tbe.vim(in clumsy English).\r\n","4":"[Key features]\r\n\r\n    1. incremental collection of buffers\r\n      - buffer information are collected in the background\r\n      - less time requred showing lists\r\n\r\n    2. grouping\r\n      - it suppresses excessive information\r\n      - it's easy to switch among groups\r\n      - defined groups:\r\n        - Directory groups corresponding to buffers\r\n        - MRU(Most Recently Used buffers) group\r\n        - Search group\r\n        - [new] All buffers group\r\n\r\n    3. ease of accessing buffers and groups\r\n      - the MRU group can list buffers you are likely to edit\r\n      - the group list supports you switching among groups\r\n      - it's easy to switch to the Directory group in which\r\n        the current buffer is\r\n\r\n    4. [new] selectable UIs\r\n      - \"Fullfeatured\" (default), SimpleGroup and Minimal\r\n      - \"SimpleGroup\": one window, supports switching groups\r\n      - \"Minimal\": one window, shows all buffers\r\n\r\n    5. customizable list format (Fullfeatured UI only)\r\n\r\n[How to use it? (and screenshots)]\r\n\r\nThere are 3 UIs now. (You can choose by command)\r\n\r\nFullfeatured UI: \r\n  execute :TinyBufferExplorer or :TBE.\r\n  http:\/\/bitbucket.org\/shu\/tinybufferexplorer\/downloads\/fullfeatured.png\r\n\r\nSimpleGroup UI:\r\n  execute :TBESimpleGroup.\r\n  http:\/\/bitbucket.org\/shu\/tinybufferexplorer\/downloads\/simplegroup.png\r\n\r\nMinimal UI:\r\n  execute :TBEMinimal.\r\n  http:\/\/bitbucket.org\/shu\/tinybufferexplorer\/downloads\/minimal.png\r\n\r\nFor more detailed descriptions, read tbe.vim(in clumsy English).\r\n","install_details":"Put this plugin in your plugin directory(e.g. $VIMRUNTIME\/plugin).\r\nThen restart Vim or :source it. \r\n","5":"Put this plugin in your plugin directory(e.g. $VIMRUNTIME\/plugin).\r\nThen restart Vim or :source it. \r\n","first_name":"Shuhei","6":"Shuhei","last_name":"Kubota","7":"Kubota","releases":[{"0":"1283","vim_version":"7.0","1":"7.0","script_version":"2.0b3","2":"2.0b3","version_comment":"added renaming in Fullfeatured and SimpleGroup. <F2>","3":"added renaming in Fullfeatured and SimpleGroup. <F2>","package":"tbe.vim","4":"tbe.vim","src_id":"17954","5":"17954","creation_date":"1336993287","6":"1336993287"},{"0":"1283","vim_version":"7.0","1":"7.0","script_version":"2.0b2","2":"2.0b2","version_comment":"* fixed leak of buffer in collecting DirectoryGroups\r\n* speed up","3":"* fixed leak of buffer in collecting DirectoryGroups\r\n* speed up","package":"tbe.vim","4":"tbe.vim","src_id":"17119","5":"17119","creation_date":"1324957048","6":"1324957048"},{"0":"1283","vim_version":"7.0","1":"7.0","script_version":"2.0b1","2":"2.0b1","version_comment":"This is a makeover. (may have some bugs inside...)\r\n\r\n+ selectable UIs\r\n+ ALL group\r\n+ a performance tuning (drawing)","3":"This is a makeover. (may have some bugs inside...)\r\n\r\n+ selectable UIs\r\n+ ALL group\r\n+ a performance tuning (drawing)","package":"tbe.vim","4":"tbe.vim","src_id":"13030","5":"13030","creation_date":"1274338580","6":"1274338580"},{"0":"1283","vim_version":"6.0","1":"6.0","script_version":"1.0.1","2":"1.0.1","version_comment":"bug fix. (improved not to hijack your yank)","3":"bug fix. (improved not to hijack your yank)","package":"tbe.vim","4":"tbe.vim","src_id":"11363","5":"11363","creation_date":"1252815679","6":"1252815679"},{"0":"1283","vim_version":"6.0","1":"6.0","script_version":"1.0.0","2":"1.0.0","version_comment":"renewed with grouping and incremental collection of buffers","3":"renewed with grouping and incremental collection of buffers","package":"tbe.vim","4":"tbe.vim","src_id":"5328","5":"5328","creation_date":"1140921100","6":"1140921100"},{"0":"1283","vim_version":"6.0","1":"6.0","script_version":"0.3.1","2":"0.3.1","version_comment":"Initial upload","3":"Initial upload","package":"tbe.vim","4":"tbe.vim","src_id":"4281","5":"4281","creation_date":"1116126764","6":"1116126764"}]},"1282":{"script_id":"1282","0":"1282","script_name":"tagselect","1":"tagselect","script_type":"utility","2":"utility","summary":"Provides a better :tselect command.","3":"Provides a better :tselect command.","description":"If you don't like the more prompt that comes up when there are too many\r\nhits to the :tselect and the related commands, then try this plugin.\r\nUseful even with finding help topics in a help window (see :help {subject}\r\nand see the tip on the usage below).\r\n                                                                           \r\n  Use :Tselect command instead of :tselect to bring up the :tselect output\r\n  in a vim window. You can then search and press enter on the line(s) of\r\n  the tag which you would like to select. If you don't want to select any\r\n  tag you can quit by pressing \"q\". You can also start typing the number\r\n  of the tag instead of moving the cursor to the line and pressing enter.\r\n                                                                           \r\n  To select another tag index for the same tag, you can use :Tselect\r\n  without arguments or just use :tselect itself.\r\n                                                                           \r\n  You can also use :Stselect, :Tjump and :Stjump commands to execute\r\n  :stselect, :tjump and :stjump commands respectively.\r\n                                                                           \r\n  The normal mode commands, \"g]\" and \"g^]\" (g] and g_CTRL-]) and their\r\n  corresponding visual mode commands (v_g] and v_g_CTRL-]) and window\r\n  split commands (CTRL-W_g] and CTRL-W_g-CTRL-]) will be remapped to use\r\n  the plugin. To disable these maps, set g:no_tagselect_maps in your\r\n  vimrc.\r\n                                                                           \r\n  You can also use :Tags command to show the output of :tags command in\r\n  a vim window. You can then search and press enter on the line of the tag\r\n  which you would like to jump to. The plugin executes the appropriate\r\n  command (:tag or :pop) with the right index.\r\n                                                                           \r\n  Use g:tagselectWinSize to set the preferred size of the window. The\r\n  default is -1, which is to take just as much as required (up to the\r\n  maximum), but you can set it to empty string to make the window as high\r\n  as possible, or any +ve number to limit its size.\r\n                                                                           \r\n  Use g:tagselectExpandCurWord to configure if <cword> and <cWORD> tokens\r\n  will be expanded or not.\r\nTips:\r\n  - You can intermix the usage of the plugin commands with that of\r\n    built-in commands (ie., :tn, :tp followed by a :Tselect)\r\n  - You can use :Ts instead of the full :Tselect, as long as there are no\r\n    other commands which could confuse the usage. The same applies to\r\n    :Tjump (:Tj) and other commands.\r\n  - The [Tag Select] buffer is set to to \"tagselect\" filetype, so this\r\n    allows you to customize the look & feel (colors, maps etc.) by\r\n    creating syntax\/tagselect.vim and ftplugin\/tagselect.vim files in your\r\n    runtime.\r\n  - In a help window, you can use the :Tselect \/<pattern> command to do\r\n    very powerful and handy lookup of the help topics. Using this\r\n    technique to find the help topic you want is fun and easy and you are\r\n    sure to bump into features that you are not aware of (both in Vim and\r\n    in plugins that you installed). E.g., to find all the topics that have\r\n    \"shell\" in its name,\r\n        :h\r\n        :Tselect \/shell\r\nLimitations:\r\n  - Executes tag commands (:tselect :stselect) twice, once to show the\r\n    list, and once to jump to the selected tag. This means, if the tag\r\n    search takes considerable time, then the time could potentially be\r\n    doubled (which is usually not a problem because Vim seems to cache the\r\n    last tag results). This could probably be fixed in Vim7 using the new\r\n    tag functions.\r\n\r\n\r\n\r\n\r\nSearch_key_words: tag tags tagselect tselect stselect tjump stjump visual explorer hari krishna dara","4":"If you don't like the more prompt that comes up when there are too many\r\nhits to the :tselect and the related commands, then try this plugin.\r\nUseful even with finding help topics in a help window (see :help {subject}\r\nand see the tip on the usage below).\r\n                                                                           \r\n  Use :Tselect command instead of :tselect to bring up the :tselect output\r\n  in a vim window. You can then search and press enter on the line(s) of\r\n  the tag which you would like to select. If you don't want to select any\r\n  tag you can quit by pressing \"q\". You can also start typing the number\r\n  of the tag instead of moving the cursor to the line and pressing enter.\r\n                                                                           \r\n  To select another tag index for the same tag, you can use :Tselect\r\n  without arguments or just use :tselect itself.\r\n                                                                           \r\n  You can also use :Stselect, :Tjump and :Stjump commands to execute\r\n  :stselect, :tjump and :stjump commands respectively.\r\n                                                                           \r\n  The normal mode commands, \"g]\" and \"g^]\" (g] and g_CTRL-]) and their\r\n  corresponding visual mode commands (v_g] and v_g_CTRL-]) and window\r\n  split commands (CTRL-W_g] and CTRL-W_g-CTRL-]) will be remapped to use\r\n  the plugin. To disable these maps, set g:no_tagselect_maps in your\r\n  vimrc.\r\n                                                                           \r\n  You can also use :Tags command to show the output of :tags command in\r\n  a vim window. You can then search and press enter on the line of the tag\r\n  which you would like to jump to. The plugin executes the appropriate\r\n  command (:tag or :pop) with the right index.\r\n                                                                           \r\n  Use g:tagselectWinSize to set the preferred size of the window. The\r\n  default is -1, which is to take just as much as required (up to the\r\n  maximum), but you can set it to empty string to make the window as high\r\n  as possible, or any +ve number to limit its size.\r\n                                                                           \r\n  Use g:tagselectExpandCurWord to configure if <cword> and <cWORD> tokens\r\n  will be expanded or not.\r\nTips:\r\n  - You can intermix the usage of the plugin commands with that of\r\n    built-in commands (ie., :tn, :tp followed by a :Tselect)\r\n  - You can use :Ts instead of the full :Tselect, as long as there are no\r\n    other commands which could confuse the usage. The same applies to\r\n    :Tjump (:Tj) and other commands.\r\n  - The [Tag Select] buffer is set to to \"tagselect\" filetype, so this\r\n    allows you to customize the look & feel (colors, maps etc.) by\r\n    creating syntax\/tagselect.vim and ftplugin\/tagselect.vim files in your\r\n    runtime.\r\n  - In a help window, you can use the :Tselect \/<pattern> command to do\r\n    very powerful and handy lookup of the help topics. Using this\r\n    technique to find the help topic you want is fun and easy and you are\r\n    sure to bump into features that you are not aware of (both in Vim and\r\n    in plugins that you installed). E.g., to find all the topics that have\r\n    \"shell\" in its name,\r\n        :h\r\n        :Tselect \/shell\r\nLimitations:\r\n  - Executes tag commands (:tselect :stselect) twice, once to show the\r\n    list, and once to jump to the selected tag. This means, if the tag\r\n    search takes considerable time, then the time could potentially be\r\n    doubled (which is usually not a problem because Vim seems to cache the\r\n    last tag results). This could probably be fixed in Vim7 using the new\r\n    tag functions.\r\n\r\n\r\n\r\n\r\nSearch_key_words: tag tags tagselect tselect stselect tjump stjump visual explorer hari krishna dara","install_details":"Copy the file into your plugin directory. Requires Vim 6.3\r\n\r\nThe plugin depends on the genutils (vimscript #197) plugin, which itself has a dependency on the multvals (vimscript #171), so make sure you install these two as well.","5":"Copy the file into your plugin directory. Requires Vim 6.3\r\n\r\nThe plugin depends on the genutils (vimscript #197) plugin, which itself has a dependency on the multvals (vimscript #171), so make sure you install these two as well.","first_name":"Hari Krishna","6":"Hari Krishna","last_name":"Dara","7":"Dara","releases":[{"0":"1282","vim_version":"6.0","1":"6.0","script_version":"1.2","2":"1.2","version_comment":"New commands: Stselect, Tjump and Stjump on the lines of stselect,\r\ntjump and stjump respectively. Their corresponding normal and visual\r\ncommands are also mapped.\r\n","3":"New commands: Stselect, Tjump and Stjump on the lines of stselect,\r\ntjump and stjump respectively. Their corresponding normal and visual\r\ncommands are also mapped.\r\n","package":"tagselect.vim","4":"tagselect.vim","src_id":"4356","5":"4356","creation_date":"1118506306","6":"1118506306"},{"0":"1282","vim_version":"6.0","1":"6.0","script_version":"1.1","2":"1.1","version_comment":"- New :Tags command for built-in :tags command.\r\n- Fixed a couple of major bugs:\r\n  - entering the tag index directly is broken.\r\n  - bug in selecting tag indexes > 99\r\n- Minor improvements.\r\n","3":"- New :Tags command for built-in :tags command.\r\n- Fixed a couple of major bugs:\r\n  - entering the tag index directly is broken.\r\n  - bug in selecting tag indexes > 99\r\n- Minor improvements.\r\n","package":"tagselect.vim","4":"tagselect.vim","src_id":"4334","5":"4334","creation_date":"1117734537","6":"1117734537"},{"0":"1282","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"tagselect.vim","4":"tagselect.vim","src_id":"4277","5":"4277","creation_date":"1115917429","6":"1115917429"}]},"1281":{"script_id":"1281","0":"1281","script_name":"crontab.vim","1":"crontab.vim","script_type":"syntax","2":"syntax","summary":"Syntax highlight for crontab files","3":"Syntax highlight for crontab files","description":"I've made a patch to the crontab.vim script, and the maintainer appears to be offline. So I've upload the script here.","4":"I've made a patch to the crontab.vim script, and the maintainer appears to be offline. So I've upload the script here.","install_details":"Put the script in the normal place. (usually \/usr\/share\/vim\/syntax)","5":"Put the script in the normal place. (usually \/usr\/share\/vim\/syntax)","first_name":"Ruben","6":"Ruben","last_name":"Justo","7":"Justo","releases":[{"0":"1281","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"crontab.vim","4":"crontab.vim","src_id":"4267","5":"4267","creation_date":"1115778044","6":"1115778044"}]},"1280":{"script_id":"1280","0":"1280","script_name":"[obsolete]ToggleOnly.vim","1":"[obsolete]ToggleOnly.vim","script_type":"utility","2":"utility","summary":"Simple enhancement of ^W ^O","3":"Simple enhancement of ^W ^O","description":"[I expanded all the tabs to spaces, and it's still all messed up :( ]\r\n\r\n\"\r\n\"                                ToggleOnly.vim:                           \r\n\"\r\n\"                A reworking of the ^W^O \"Only window\" idea of maximizing\r\n\"                the current window, but also maximize the new one as you\r\n\"                switch windows.  (Actually, it's evolved to have nothing\r\n\"                in common with   :only   anymore, but I liked the ^W^O,\r\n\"                and <C-W><C-_> had no catchy name.)\r\n\"\r\n\"\r\n\" Version:       1.1\r\n\"\r\n\" Author:        Eric Arnold ( eric_p_arnold in_the_vicinity_of yahoo.com )\r\n\"\r\n\" Description:   Remaps ^W^O   ^W^W   ^W^K   and a few related keys to\r\n\"                fully expand the current window without closing any.\r\n\"                Emphasis is on simplicity, key ergonomics and usability.\r\n\"                I wanted something I would actually use all the time.\r\n\"                Your [personal preference] milage may vary.  I used the\r\n\"                ^W keys to move through windows before, so tried to\r\n\"                integrate smoothly with them.  Small bumps in the\r\n\"                original are smoothed out, i.e. ^W^J and ^W^K wrap\r\n\"                around.\r\n\"\r\n\" <C-W><C-O>     Toggle the Only Window Mode ON\/OFF.   \r\n\"                <C-W><C-O>   <C-W><C-_>   <C-W>o   are synonymous.\r\n\"                <C-W>O toggles auto-expand.\r\n\"                The rest of the keys are only mapped when Only Window Mode ON.\r\n\"\r\n\" Mouse          Window will resize when the mouse cursor enters it or\r\n\"                its [clicked]statusbar.  See config section.\r\n\"\r\n\"\r\n\" <C-W><C-K>     Up one window, resize to full, wrap around at top.\r\n\"\r\n\" <C-W><C-W>     Next\/Down one window, ditto.  \r\n\"                <C-W><C-J> is synonymous.\r\n\"\r\n\" <C-W>w or j    Next window, and resize to 1\/2 total &lines, giving the\r\n\"                previous window the other half, wrap around at bottom.\r\n\"                These provide a way to move around with a little more\r\n\"                visibility without leaving Only Window Mode.\r\n\"\r\n\" <C-W>k         Previous window, ditto.\r\n\"\r\n\"\r\n\"        Note:  if  \"g:ToggleOnlyAutoExpand\"  is set (true by default),\r\n\"        windows will be expanded when *anything* moves the cursor into\r\n\"        them.\r\n\"\r\n\"\r\n\"\r\n\"    Configuration Notes:    \r\n\"\r\n\"        Whether you need to click on the statusbar depends on how you\r\n\"        have \"&mousefocus\" set.  You can tone down the aggressive\r\n\"        behavior of the auto-expand by turning \"&mousefocus\" off,\r\n\"        without disabliing auto-expand altogether.\r\n\"\r\n\"\r\n\"        \"timeout\" and \"ttimeout\" are turned off since it's extra\r\n\"        annoying when it times out to the default ^W^O, which closes all\r\n\"        other windows.  You may want to reset these if you have\r\n\"        mappings like   ,s  and   ,st    which depend on a timeout \r\n\"        for  ,s   to be accepted, or some other key, i.e.  ,s<ESC>   \r\n\"        works without timeouts.\r\n\"        \"g:ToggleOnlyTimeouts\"  is \"exe\"'d, so get your syntax\r\n\"        right.  If want timeouts, try something like this in your\r\n\"        \".vimrc\":\r\n\"\r\n\"    let g:ToggleOnlyTimeouts = 'set timeout ttimeout timeoutlen=2000 ttimeoutlen=2000'\r\n\"\r\n\"        An autocommand is set for \"BufEnter\" to resize any window, \r\n\"        which allows you to mouse into a window and have it resize.\r\n\"        This is controled by:\r\n\"\r\n\"    let g:ToggleOnlyAutoExpand = 1\r\n\"\r\n\"        To save space when the windows are minimized, \"&winminheight\" is\r\n\"        set to zero.  This is changed with:\r\n\"\r\n\"    let g:ToggleOnlywinminheight = 0\r\n\"\r\n\"\r\n\"\r\n\"    Updated:        Wed Jun 08, 6\/8\/2005 5:14:07 PM\r\n\"          General overall refinement.\r\n\"     -    Now uses ^K and k, ^W and w, which is better than O and o.\r\n\"     -    All keys wrap around at top\/bottom, not just ^W.\r\n\"     -    Added a BufEnter autocommand so mouse will trigger resize\r\n\"     -    Keymaps are more correct (nnoremap instead of map), and are\r\n\"          only mapped when ^W^O toggles them on.\r\n\"     -    Set &winminheight to 0 to save space around statusbars.\r\n\"     -    Added a few config options.  Keymap timeout issue addressed, and\r\n\"          config option added.\r\n\"     -    Added a two window auto expand option\r\n\r\n","4":"[I expanded all the tabs to spaces, and it's still all messed up :( ]\r\n\r\n\"\r\n\"                                ToggleOnly.vim:                           \r\n\"\r\n\"                A reworking of the ^W^O \"Only window\" idea of maximizing\r\n\"                the current window, but also maximize the new one as you\r\n\"                switch windows.  (Actually, it's evolved to have nothing\r\n\"                in common with   :only   anymore, but I liked the ^W^O,\r\n\"                and <C-W><C-_> had no catchy name.)\r\n\"\r\n\"\r\n\" Version:       1.1\r\n\"\r\n\" Author:        Eric Arnold ( eric_p_arnold in_the_vicinity_of yahoo.com )\r\n\"\r\n\" Description:   Remaps ^W^O   ^W^W   ^W^K   and a few related keys to\r\n\"                fully expand the current window without closing any.\r\n\"                Emphasis is on simplicity, key ergonomics and usability.\r\n\"                I wanted something I would actually use all the time.\r\n\"                Your [personal preference] milage may vary.  I used the\r\n\"                ^W keys to move through windows before, so tried to\r\n\"                integrate smoothly with them.  Small bumps in the\r\n\"                original are smoothed out, i.e. ^W^J and ^W^K wrap\r\n\"                around.\r\n\"\r\n\" <C-W><C-O>     Toggle the Only Window Mode ON\/OFF.   \r\n\"                <C-W><C-O>   <C-W><C-_>   <C-W>o   are synonymous.\r\n\"                <C-W>O toggles auto-expand.\r\n\"                The rest of the keys are only mapped when Only Window Mode ON.\r\n\"\r\n\" Mouse          Window will resize when the mouse cursor enters it or\r\n\"                its [clicked]statusbar.  See config section.\r\n\"\r\n\"\r\n\" <C-W><C-K>     Up one window, resize to full, wrap around at top.\r\n\"\r\n\" <C-W><C-W>     Next\/Down one window, ditto.  \r\n\"                <C-W><C-J> is synonymous.\r\n\"\r\n\" <C-W>w or j    Next window, and resize to 1\/2 total &lines, giving the\r\n\"                previous window the other half, wrap around at bottom.\r\n\"                These provide a way to move around with a little more\r\n\"                visibility without leaving Only Window Mode.\r\n\"\r\n\" <C-W>k         Previous window, ditto.\r\n\"\r\n\"\r\n\"        Note:  if  \"g:ToggleOnlyAutoExpand\"  is set (true by default),\r\n\"        windows will be expanded when *anything* moves the cursor into\r\n\"        them.\r\n\"\r\n\"\r\n\"\r\n\"    Configuration Notes:    \r\n\"\r\n\"        Whether you need to click on the statusbar depends on how you\r\n\"        have \"&mousefocus\" set.  You can tone down the aggressive\r\n\"        behavior of the auto-expand by turning \"&mousefocus\" off,\r\n\"        without disabliing auto-expand altogether.\r\n\"\r\n\"\r\n\"        \"timeout\" and \"ttimeout\" are turned off since it's extra\r\n\"        annoying when it times out to the default ^W^O, which closes all\r\n\"        other windows.  You may want to reset these if you have\r\n\"        mappings like   ,s  and   ,st    which depend on a timeout \r\n\"        for  ,s   to be accepted, or some other key, i.e.  ,s<ESC>   \r\n\"        works without timeouts.\r\n\"        \"g:ToggleOnlyTimeouts\"  is \"exe\"'d, so get your syntax\r\n\"        right.  If want timeouts, try something like this in your\r\n\"        \".vimrc\":\r\n\"\r\n\"    let g:ToggleOnlyTimeouts = 'set timeout ttimeout timeoutlen=2000 ttimeoutlen=2000'\r\n\"\r\n\"        An autocommand is set for \"BufEnter\" to resize any window, \r\n\"        which allows you to mouse into a window and have it resize.\r\n\"        This is controled by:\r\n\"\r\n\"    let g:ToggleOnlyAutoExpand = 1\r\n\"\r\n\"        To save space when the windows are minimized, \"&winminheight\" is\r\n\"        set to zero.  This is changed with:\r\n\"\r\n\"    let g:ToggleOnlywinminheight = 0\r\n\"\r\n\"\r\n\"\r\n\"    Updated:        Wed Jun 08, 6\/8\/2005 5:14:07 PM\r\n\"          General overall refinement.\r\n\"     -    Now uses ^K and k, ^W and w, which is better than O and o.\r\n\"     -    All keys wrap around at top\/bottom, not just ^W.\r\n\"     -    Added a BufEnter autocommand so mouse will trigger resize\r\n\"     -    Keymaps are more correct (nnoremap instead of map), and are\r\n\"          only mapped when ^W^O toggles them on.\r\n\"     -    Set &winminheight to 0 to save space around statusbars.\r\n\"     -    Added a few config options.  Keymap timeout issue addressed, and\r\n\"          config option added.\r\n\"     -    Added a two window auto expand option\r\n\r\n","install_details":"Put into plugin directory.","5":"Put into plugin directory.","first_name":"Eric","6":"Eric","last_name":"Arnold","7":"Arnold","releases":[{"0":"1280","vim_version":"6.0","1":"6.0","script_version":"1.1","2":"1.1","version_comment":"\"\tUpdated:\t\tWed Jun 08, 6\/8\/2005 5:14:07 PM\r\n\" \t\tGeneral overall refinement.\r\n\" \t-\tNow uses ^K and k, ^W and w, which is better than O and o.\r\n\" \t-\tAll keys wrap around at top\/bottom, not just ^W.\r\n\" \t-\tAdded a BufEnter autocommand so mouse will trigger resize\r\n\" \t-\tKeymaps are more correct (nnoremap instead of map), and are\r\n\" \t\tonly mapped when ^W^O toggles them on.\r\n\"\t-\tSet &winminheight to 0 to save space around statusbars.\r\n\"\t-\tAdded a few config options.  Keymap timeout issue addressed, and\r\n\"\t\tconfig option added.\r\n\"\t-\tAdded a two window auto expand option\r\n","3":"\"\tUpdated:\t\tWed Jun 08, 6\/8\/2005 5:14:07 PM\r\n\" \t\tGeneral overall refinement.\r\n\" \t-\tNow uses ^K and k, ^W and w, which is better than O and o.\r\n\" \t-\tAll keys wrap around at top\/bottom, not just ^W.\r\n\" \t-\tAdded a BufEnter autocommand so mouse will trigger resize\r\n\" \t-\tKeymaps are more correct (nnoremap instead of map), and are\r\n\" \t\tonly mapped when ^W^O toggles them on.\r\n\"\t-\tSet &winminheight to 0 to save space around statusbars.\r\n\"\t-\tAdded a few config options.  Keymap timeout issue addressed, and\r\n\"\t\tconfig option added.\r\n\"\t-\tAdded a two window auto expand option\r\n","package":"ToggleOnly.vim","4":"ToggleOnly.vim","src_id":"4353","5":"4353","creation_date":"1118272850","6":"1118272850"}]},"1279":{"script_id":"1279","0":"1279","script_name":"ToggleOptions.vim","1":"ToggleOptions.vim","script_type":"utility","2":"utility","summary":"Quick toggling of options","3":"Quick toggling of options","description":"This allows \"toggling\" of more complex operations, like switching off \"diffthis\".  It also reduces the number of key mappings used overall by placing the operations under a key activated command window menu, i.e. if the key map is <leader>o  and <leader> is \",\":\r\n     ,o\r\ndisplays an option list in the command window:\r\n     wrap, Wrapscan, list, binary, modifiable, diff, virtualedit, uhex\r\nso the full command\r\n    ,od\r\ntoggles \"diff\" mode on\/off for a window (including foldcolumn=0)\r\n    ,om\r\ntoggles \"modifiable\" and \"readonly\" together.\r\n\r\nYou should edit the script to add what want.  E.g.  add your item to the menu call string:\r\n\r\n    let l:char = s:Char_menu( \"{w}rap, {W}rapscan, {l}ist, {b}inary, {m}odifiable, {d}iff, {v}irtualedit, uhe{x}\" )\r\n\r\nwhere {text} is in a different color, then add an elseif clause:\r\n\r\n    elseif l:char ==# 'm'\r\n        if &modifiable && !&readonly\r\n            set nomodifiable\r\n            set readonly\r\n        else\r\n            set modifiable\r\n            set noreadonly\r\n        endif\r\n        set readonly?\r\n        set modifiable?\r\n","4":"This allows \"toggling\" of more complex operations, like switching off \"diffthis\".  It also reduces the number of key mappings used overall by placing the operations under a key activated command window menu, i.e. if the key map is <leader>o  and <leader> is \",\":\r\n     ,o\r\ndisplays an option list in the command window:\r\n     wrap, Wrapscan, list, binary, modifiable, diff, virtualedit, uhex\r\nso the full command\r\n    ,od\r\ntoggles \"diff\" mode on\/off for a window (including foldcolumn=0)\r\n    ,om\r\ntoggles \"modifiable\" and \"readonly\" together.\r\n\r\nYou should edit the script to add what want.  E.g.  add your item to the menu call string:\r\n\r\n    let l:char = s:Char_menu( \"{w}rap, {W}rapscan, {l}ist, {b}inary, {m}odifiable, {d}iff, {v}irtualedit, uhe{x}\" )\r\n\r\nwhere {text} is in a different color, then add an elseif clause:\r\n\r\n    elseif l:char ==# 'm'\r\n        if &modifiable && !&readonly\r\n            set nomodifiable\r\n            set readonly\r\n        else\r\n            set modifiable\r\n            set noreadonly\r\n        endif\r\n        set readonly?\r\n        set modifiable?\r\n","install_details":"Put it in the plugin directory.  Change the <leader>o  key map as desired.","5":"Put it in the plugin directory.  Change the <leader>o  key map as desired.","first_name":"Eric","6":"Eric","last_name":"Arnold","7":"Arnold","releases":[{"0":"1279","vim_version":"6.0","1":"6.0","script_version":"1","2":"1","version_comment":"Initial upload","3":"Initial upload","package":"ToggleOptions.vim","4":"ToggleOptions.vim","src_id":"4262","5":"4262","creation_date":"1115655021","6":"1115655021"}]},"1278":{"script_id":"1278","0":"1278","script_name":"quantum.vim","1":"quantum.vim","script_type":"syntax","2":"syntax","summary":"quantum syntax file","3":"quantum syntax file","description":"Syntax file for SPSS quantum and ccount (http:\/\/pan-data.dyndns.org\/ccount\/) data manipulation and tabulation software packages.  Very basic (only a few colors) highlighting used, to be compliant with UNIX interfaces (such as SecureCRT) as well.","4":"Syntax file for SPSS quantum and ccount (http:\/\/pan-data.dyndns.org\/ccount\/) data manipulation and tabulation software packages.  Very basic (only a few colors) highlighting used, to be compliant with UNIX interfaces (such as SecureCRT) as well.","install_details":"drop into syntax directory, modify input files, and enjoy!","5":"drop into syntax directory, modify input files, and enjoy!","first_name":"matt","6":"matt","last_name":"skawinski","7":"skawinski","releases":[{"0":"1278","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"quantum.vim","4":"quantum.vim","src_id":"4261","5":"4261","creation_date":"1115651569","6":"1115651569"}]},"1277":{"script_id":"1277","0":"1277","script_name":"vsearch.vim","1":"vsearch.vim","script_type":"utility","2":"utility","summary":"Allows text to be searched vertically","3":"Allows text to be searched vertically","description":"This script enables the command \":VS\" which allows you to search for patterns vertically (column-wise)\r\n\r\n\" Usage:\r\n\"  1) .,$VS <pattern> [Preferred approach, shows multiple occurence in a line]\r\n\"      [ Use @: to search for further hits]\r\n\"  2)  [range]VS <pattern> [Only first occurence in a line shown]\r\n\"\r\n\" Pre-requisites:\r\n\"   :set nocp cpo+=<\r\n","4":"This script enables the command \":VS\" which allows you to search for patterns vertically (column-wise)\r\n\r\n\" Usage:\r\n\"  1) .,$VS <pattern> [Preferred approach, shows multiple occurence in a line]\r\n\"      [ Use @: to search for further hits]\r\n\"  2)  [range]VS <pattern> [Only first occurence in a line shown]\r\n\"\r\n\" Pre-requisites:\r\n\"   :set nocp cpo+=<\r\n","install_details":":source vsearch.vim\r\nOR\r\ndrop the file under:\r\n$HOME\/.vim\/plugin\r\n","5":":source vsearch.vim\r\nOR\r\ndrop the file under:\r\n$HOME\/.vim\/plugin\r\n","first_name":"Arun","6":"Arun","last_name":"E","7":"E","releases":[{"0":"1277","vim_version":"6.0","1":"6.0","script_version":"1.6","2":"1.6","version_comment":"Enabled for vim7","3":"Enabled for vim7","package":"vsearch.vim","4":"vsearch.vim","src_id":"6427","5":"6427","creation_date":"1163682840","6":"1163682840"},{"0":"1277","vim_version":"6.0","1":"6.0","script_version":"1.5","2":"1.5","version_comment":"Significant performance boost! (hence given 1.5) and some usage cleanup\r\nNew usage:\r\n\" Usage:\r\n\"  :[range]VS <pattern>\r\n\"       - Use @: to search for further hits\r\n\"       - Range default: whole file\r\n\"       - Search starts from cursor\r\n","3":"Significant performance boost! (hence given 1.5) and some usage cleanup\r\nNew usage:\r\n\" Usage:\r\n\"  :[range]VS <pattern>\r\n\"       - Use @: to search for further hits\r\n\"       - Range default: whole file\r\n\"       - Search starts from cursor\r\n","package":"vsearch.vim","4":"vsearch.vim","src_id":"4257","5":"4257","creation_date":"1115522881","6":"1115522881"},{"0":"1277","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"vsearch.vim","4":"vsearch.vim","src_id":"4255","5":"4255","creation_date":"1115486849","6":"1115486849"}]},"1276":{"script_id":"1276","0":"1276","script_name":"autoscroll","1":"autoscroll","script_type":"utility","2":"utility","summary":"autoscroll the screen, see the context of current line clearly","3":"autoscroll the screen, see the context of current line clearly","description":"auto scroll the screen:\r\nwhen there are still  certain lines between current line and the top or bottom boundry of the current window, the screen would scroll automatic, so that you can see the context of current line always.\r\nwhen in insert mode, if current line is quite near the bottom boundry of current window, and if you press enter, some extra blank spaces would appear so that the current line not  be too close to the boundry.","4":"auto scroll the screen:\r\nwhen there are still  certain lines between current line and the top or bottom boundry of the current window, the screen would scroll automatic, so that you can see the context of current line always.\r\nwhen in insert mode, if current line is quite near the bottom boundry of current window, and if you press enter, some extra blank spaces would appear so that the current line not  be too close to the boundry.","install_details":" \r\n\r\n\" File: autoscroll.vim\r\n\" Author:LiuXiangqian (www.lvying.org)\r\n\" Version: 0.04\r\n\" Last Modify: May 6, 2005\r\n\" ChangeLog:\r\n\" Version 0.02:\r\n\"   1.add autoscroll in insert mode \r\n\"   2.correct(or mistake) some grammar mistakes(or correct ones) in the documentation\r\n\"   3.separate the Installation part of documentation to Installation and\r\n\"     Configuration\r\n\" Version 0.03\r\n\"   1. some more bug of cursor position mistakes fixed\r\n\"   2. fix the bug when the cursor is at the end of a line, an <Enter> would make\r\n\"      a character down to the current line\r\n\" Version 0.04\r\n\"   1. fix the bug when the character at the end of the line is a multibyte character\r\n\"      in insert mode, an <Enter> would pull the last character to the next line.\r\n\" Installation:\r\n\" -------------\r\n\" 1.copy the autoscroll.vim script to  $HOME\/.vim\/plugin directory or where\r\n\"   the vim program can find the script at startup. Or you can put autoscroll.vim\r\n\"   some other place, and then use :so PATH_TO_AUTOSCROLL_SCRIPT\/autoscroll.vim \r\n\"   in $HOME\/.vimrc to execute the script. Refer to ':help add-plugin', \r\n\"   ':help add-global-plugin' and ':help runtimepath' for more details about\r\n\"   vim plugins. Refer to ':help so' for more details about read Ex commands from\r\n\"   a file.\r\n\" 2.Restart vim\r\n\" Configuration:\r\n\" -------------\r\n\" 1.Set topScrollNumber and bottomScrollNumber variable, if you do not\r\n\"   set these two variables explicitly, they would both get default value of 5.\r\n\"   TopScrollNumber is the amount of lines above your cursor lines when the\r\n\"   auto down scroll occurs in normal and insert mode. As you may dope out, \r\n\"   bottomScrollNumber is the amount of lines down to your cursor line when the\r\n\"   auto up scroll occurs in normal and insert mode. You may set these \r\n\"   two variables using let in you .vimrc\r\n\"   For example,\r\n\"             let topScrollNumber = 8\r\n\"             let bottomScrollNumber = 8\r\n\" 2.Set the updatetime variable. Refer to :help updatetime to see\r\n\"   what's the meaning of variable updatetime. You may set this variable using\r\n\"   let in your .vimrc. For example,\r\n\"             let updatetime = 100\r\n\"   this variable only affect the auto scroll behavior in normal mode.\r\n\"   Note: You should set this variable explicitly in your .vimrc.\r\n\" 3.Set the variable bottomRowNumberInsertMode. This variable would get \r\n\"   default value of 5 if you don't set it explicitly. This variable is the \r\n\"   amount of line below your current line when you press Enter to produce a\r\n\"   new line near the bottom of the screen, if there are not enough lines \r\n\"   below current line to be displayed, coequal height of blank space would \r\n\"   be displayed. You may set this variable using let in your .vimrc.\r\n\"   For example,\r\n\"             let bottomRowNumberInsertMode = 9\r\n\" 4.If you use <UP> and <DOWN> to scroll in insert mode, you need no changes\r\n\"   for the key binding, but if you bind some other keys to scroll in insert\r\n\"   mode, you have to change your key binding to let it auto scroll at the same \r\n\"   time. For example, if you bind the key combine Ctrl+k and Ctrl+j to scroll \r\n\"   up and down in insert mode, you should configure the key binding as below:\r\n\"           inoremap <C-K> <ESC>:call Check_Scroll()<CR>a<UP>\r\n\"           inoremap <C-J> <ESC>:call Check_Scroll()<CR>a<DOWN>\r\n\"   If you want to bind the key <UP> and <DOWN> to other operation in insert\r\n\"   mode, you have to comment the keymap definition of <UP> and <DOWN> below . \r\n\" Usage:\r\n\" -----\r\n\"   Just enjoy the convenience of see the context of current line all the time.\r\n\" Known BUGS:\r\n\" ---------\r\n\" 1.If you set wrap display and the length of a line is larger than your set of \r\n\"   textwidth, the cursor would jump back by force and you should quick enough to\r\n\"   move your cursor rushing across this line, So I suggest set updatetime to \r\n\"   match your speed of moving the cusor, 100ms is a good choice in my opinion.\r\n\" 2.The auto scroll act based on lines separate by line break, not lines wraped\r\n\"   by vim(This may not be suppose to a bug)\r\n\" 3.If you place the cursor at the second column of one line, and then press <ENTER>, \r\n\"   the cursor would jump to the beginning of the line and pull the first character to\r\n\"   next line also, this happens when you are in the insert mode. So you may want to \r\n\"   bind the auto scroll version of <ENTER> to some other keys such as <C-CR>, Then you\r\n\"   should change the key binding of <CR> below to\r\n\"              inoremap <C-CR> <Esc>:call Check_Scroll_Insert()<CR>i<CR>\r\n\" IMPORTANT ATTENTION:\r\n\" --------------------\r\n\" 4.Sometimes, the cursor may be locked, (seems random so far to me, the reason \r\n\"   remains unknown, but the probability is very very very small), and you can not\r\n\"   change the position of the cursor and the mode of VIM, if you are using GVIM,\r\n\"   you can still select  file -> save in the menu bar to save your unsaved files\r\n\"   since VIM isn't crack except for the lock.\r\n\"   Unfortunately, if you are using vim in console and there is no gui menu,\r\n\"   I haven't find a way to save my unsaved file,if you find one,please contact me\r\n\"   at smartLitchi@gmail.com. Appreciate all your help~~.Before you find one, carefully\r\n\"   enough to using this plugin in console vim.\r\n\" Acknowledgement:\r\n\" ---------------\r\n\"   This script is base on redhair's autoscroll.vim\r\n\"   (See x-4-6 in vim board of newsmth.net)\r\n\"   I should express my appreciate to redhair@smth\r\n\" TODO: \r\n\"   I wouldn't add new function to this script except for bug fixes.\r\n\" Bug Report:\r\n\" ----------\r\n\"   Please send an E-mail to smartLitchi@gmail.com if you find an bug, or you\r\n\"   can send a personal message to truelvying@newsmth. Best wishes.\r\n\" License:\r\n\" -------\r\n\"   This plugin has the same license as vim.\r\n\r\n\" If you want to change the key bind <CR> in insert mode, please\r\n\" change the follow line. Refer to the Known BUGS part 3 for more details\r\ninoremap <CR> <Esc>:call Check_Scroll_Insert()<CR>i<CR>\r\n\r\n\" If you want to change the key bind <UP> and <LEFT> in insert mode\r\n\" Please change the follow two lines\r\n\" Refer to the Configuration part 4 for more details.\r\ninoremap <UP> <ESC>:call Check_Scroll()<CR>a<UP>\r\ninoremap <DOWN> <ESC>:call Check_Scroll()<CR>a<DOWN>\r\n","5":" \r\n\r\n\" File: autoscroll.vim\r\n\" Author:LiuXiangqian (www.lvying.org)\r\n\" Version: 0.04\r\n\" Last Modify: May 6, 2005\r\n\" ChangeLog:\r\n\" Version 0.02:\r\n\"   1.add autoscroll in insert mode \r\n\"   2.correct(or mistake) some grammar mistakes(or correct ones) in the documentation\r\n\"   3.separate the Installation part of documentation to Installation and\r\n\"     Configuration\r\n\" Version 0.03\r\n\"   1. some more bug of cursor position mistakes fixed\r\n\"   2. fix the bug when the cursor is at the end of a line, an <Enter> would make\r\n\"      a character down to the current line\r\n\" Version 0.04\r\n\"   1. fix the bug when the character at the end of the line is a multibyte character\r\n\"      in insert mode, an <Enter> would pull the last character to the next line.\r\n\" Installation:\r\n\" -------------\r\n\" 1.copy the autoscroll.vim script to  $HOME\/.vim\/plugin directory or where\r\n\"   the vim program can find the script at startup. Or you can put autoscroll.vim\r\n\"   some other place, and then use :so PATH_TO_AUTOSCROLL_SCRIPT\/autoscroll.vim \r\n\"   in $HOME\/.vimrc to execute the script. Refer to ':help add-plugin', \r\n\"   ':help add-global-plugin' and ':help runtimepath' for more details about\r\n\"   vim plugins. Refer to ':help so' for more details about read Ex commands from\r\n\"   a file.\r\n\" 2.Restart vim\r\n\" Configuration:\r\n\" -------------\r\n\" 1.Set topScrollNumber and bottomScrollNumber variable, if you do not\r\n\"   set these two variables explicitly, they would both get default value of 5.\r\n\"   TopScrollNumber is the amount of lines above your cursor lines when the\r\n\"   auto down scroll occurs in normal and insert mode. As you may dope out, \r\n\"   bottomScrollNumber is the amount of lines down to your cursor line when the\r\n\"   auto up scroll occurs in normal and insert mode. You may set these \r\n\"   two variables using let in you .vimrc\r\n\"   For example,\r\n\"             let topScrollNumber = 8\r\n\"             let bottomScrollNumber = 8\r\n\" 2.Set the updatetime variable. Refer to :help updatetime to see\r\n\"   what's the meaning of variable updatetime. You may set this variable using\r\n\"   let in your .vimrc. For example,\r\n\"             let updatetime = 100\r\n\"   this variable only affect the auto scroll behavior in normal mode.\r\n\"   Note: You should set this variable explicitly in your .vimrc.\r\n\" 3.Set the variable bottomRowNumberInsertMode. This variable would get \r\n\"   default value of 5 if you don't set it explicitly. This variable is the \r\n\"   amount of line below your current line when you press Enter to produce a\r\n\"   new line near the bottom of the screen, if there are not enough lines \r\n\"   below current line to be displayed, coequal height of blank space would \r\n\"   be displayed. You may set this variable using let in your .vimrc.\r\n\"   For example,\r\n\"             let bottomRowNumberInsertMode = 9\r\n\" 4.If you use <UP> and <DOWN> to scroll in insert mode, you need no changes\r\n\"   for the key binding, but if you bind some other keys to scroll in insert\r\n\"   mode, you have to change your key binding to let it auto scroll at the same \r\n\"   time. For example, if you bind the key combine Ctrl+k and Ctrl+j to scroll \r\n\"   up and down in insert mode, you should configure the key binding as below:\r\n\"           inoremap <C-K> <ESC>:call Check_Scroll()<CR>a<UP>\r\n\"           inoremap <C-J> <ESC>:call Check_Scroll()<CR>a<DOWN>\r\n\"   If you want to bind the key <UP> and <DOWN> to other operation in insert\r\n\"   mode, you have to comment the keymap definition of <UP> and <DOWN> below . \r\n\" Usage:\r\n\" -----\r\n\"   Just enjoy the convenience of see the context of current line all the time.\r\n\" Known BUGS:\r\n\" ---------\r\n\" 1.If you set wrap display and the length of a line is larger than your set of \r\n\"   textwidth, the cursor would jump back by force and you should quick enough to\r\n\"   move your cursor rushing across this line, So I suggest set updatetime to \r\n\"   match your speed of moving the cusor, 100ms is a good choice in my opinion.\r\n\" 2.The auto scroll act based on lines separate by line break, not lines wraped\r\n\"   by vim(This may not be suppose to a bug)\r\n\" 3.If you place the cursor at the second column of one line, and then press <ENTER>, \r\n\"   the cursor would jump to the beginning of the line and pull the first character to\r\n\"   next line also, this happens when you are in the insert mode. So you may want to \r\n\"   bind the auto scroll version of <ENTER> to some other keys such as <C-CR>, Then you\r\n\"   should change the key binding of <CR> below to\r\n\"              inoremap <C-CR> <Esc>:call Check_Scroll_Insert()<CR>i<CR>\r\n\" IMPORTANT ATTENTION:\r\n\" --------------------\r\n\" 4.Sometimes, the cursor may be locked, (seems random so far to me, the reason \r\n\"   remains unknown, but the probability is very very very small), and you can not\r\n\"   change the position of the cursor and the mode of VIM, if you are using GVIM,\r\n\"   you can still select  file -> save in the menu bar to save your unsaved files\r\n\"   since VIM isn't crack except for the lock.\r\n\"   Unfortunately, if you are using vim in console and there is no gui menu,\r\n\"   I haven't find a way to save my unsaved file,if you find one,please contact me\r\n\"   at smartLitchi@gmail.com. Appreciate all your help~~.Before you find one, carefully\r\n\"   enough to using this plugin in console vim.\r\n\" Acknowledgement:\r\n\" ---------------\r\n\"   This script is base on redhair's autoscroll.vim\r\n\"   (See x-4-6 in vim board of newsmth.net)\r\n\"   I should express my appreciate to redhair@smth\r\n\" TODO: \r\n\"   I wouldn't add new function to this script except for bug fixes.\r\n\" Bug Report:\r\n\" ----------\r\n\"   Please send an E-mail to smartLitchi@gmail.com if you find an bug, or you\r\n\"   can send a personal message to truelvying@newsmth. Best wishes.\r\n\" License:\r\n\" -------\r\n\"   This plugin has the same license as vim.\r\n\r\n\" If you want to change the key bind <CR> in insert mode, please\r\n\" change the follow line. Refer to the Known BUGS part 3 for more details\r\ninoremap <CR> <Esc>:call Check_Scroll_Insert()<CR>i<CR>\r\n\r\n\" If you want to change the key bind <UP> and <LEFT> in insert mode\r\n\" Please change the follow two lines\r\n\" Refer to the Configuration part 4 for more details.\r\ninoremap <UP> <ESC>:call Check_Scroll()<CR>a<UP>\r\ninoremap <DOWN> <ESC>:call Check_Scroll()<CR>a<DOWN>\r\n","first_name":"xiangqian","6":"xiangqian","last_name":"liu","7":"liu","releases":[{"0":"1276","vim_version":"6.0","1":"6.0","script_version":"0.04","2":"0.04","version_comment":"Initial upload","3":"Initial upload","package":"autoscroll_004.vim","4":"autoscroll_004.vim","src_id":"4248","5":"4248","creation_date":"1115354807","6":"1115354807"}]},"1275":{"script_id":"1275","0":"1275","script_name":"SpotlightOpen","1":"SpotlightOpen","script_type":"utility","2":"utility","summary":"Open files using MacOS Tiger's Spotlight","3":"Open files using MacOS Tiger's Spotlight","description":"This is based on Ciaran McCreesh's locateopen script. I modified it so it uses Spotlight instead of slocate. So this script will only run on MacOS 10.4 or later.\r\n\r\nIt allows you to open files in VIM by just typing (part of) the filename. You don't have to type their full path. If there's more than one match, you can choose a file from a menu.\r\n\r\nUsage is the same, except the command names have \"Spot\" in place of \"Locate\":\r\n\r\n:SpotEdit <file>\r\n:SpotSplit <file>\r\n:SpotSource <file>\r\n:SpotRead <file>\r\n\r\n\r\nUser-definable options (see script header):\r\n\r\n- You can choose whether the typed name must match the filename exactly, its beginning, or any part of the filename.\r\n\r\n- You can limit the search to a certain filetype.\r\n\r\n\r\nI use the following in my .vimrc:\r\n\r\nlet g:spotlightopen_match = 1\r\nlet g:spotlightopen_limitftype = \"public.plain-text\"\r\n\r\nwhich means that it will look for any plain text files beginning with a given name. So for example\r\n\r\n:SpotEdit PrefsW\r\n\r\nwould find PrefsWindow.c and PrefsWindow.h - but not PrefsWindow.o (since it's a binary file and not plain text).\r\n\r\n\r\nTodo:\r\n\r\n- Option to exclude matches from the trash...","4":"This is based on Ciaran McCreesh's locateopen script. I modified it so it uses Spotlight instead of slocate. So this script will only run on MacOS 10.4 or later.\r\n\r\nIt allows you to open files in VIM by just typing (part of) the filename. You don't have to type their full path. If there's more than one match, you can choose a file from a menu.\r\n\r\nUsage is the same, except the command names have \"Spot\" in place of \"Locate\":\r\n\r\n:SpotEdit <file>\r\n:SpotSplit <file>\r\n:SpotSource <file>\r\n:SpotRead <file>\r\n\r\n\r\nUser-definable options (see script header):\r\n\r\n- You can choose whether the typed name must match the filename exactly, its beginning, or any part of the filename.\r\n\r\n- You can limit the search to a certain filetype.\r\n\r\n\r\nI use the following in my .vimrc:\r\n\r\nlet g:spotlightopen_match = 1\r\nlet g:spotlightopen_limitftype = \"public.plain-text\"\r\n\r\nwhich means that it will look for any plain text files beginning with a given name. So for example\r\n\r\n:SpotEdit PrefsW\r\n\r\nwould find PrefsWindow.c and PrefsWindow.h - but not PrefsWindow.o (since it's a binary file and not plain text).\r\n\r\n\r\nTodo:\r\n\r\n- Option to exclude matches from the trash...","install_details":"Just copy the script into your VIM's plugin directory.","5":"Just copy the script into your VIM's plugin directory.","first_name":"Ruediger","6":"Ruediger","last_name":"Hanke","7":"Hanke","releases":[{"0":"1275","vim_version":"6.0","1":"6.0","script_version":"0.9","2":"0.9","version_comment":"Initial upload","3":"Initial upload","package":"spotlight.vim","4":"spotlight.vim","src_id":"4246","5":"4246","creation_date":"1115286246","6":"1115286246"}]},"1274":{"script_id":"1274","0":"1274","script_name":"Mathematica Indent File","1":"Mathematica Indent File","script_type":"indent","2":"indent","summary":"Indentation file for Mathematica code","3":"Indentation file for Mathematica code","description":"[ Note: As of May 2005, this is included in Vim7 ]\r\n\r\nThis is a simple file that allows rudimentary auto indenting of Mathematica code.  Combine it with vimscript #1273, it makes editing Mathematica package code a breeze.","4":"[ Note: As of May 2005, this is included in Vim7 ]\r\n\r\nThis is a simple file that allows rudimentary auto indenting of Mathematica code.  Combine it with vimscript #1273, it makes editing Mathematica package code a breeze.","install_details":"  * copy this file to $HOME\/.vim\/indent\/mma.vim\r\n    (%HOME%\\vimfiles\\indent\\mma.vim for windows)\r\n\r\n  * Open a Mathematica file **\r\n\r\n**Note that both Mathematica and Matlab use .m file extensions, so if you are editing Mathematica .m files, you need to either manually :set ft=mma or edit your filetype.vim file.\r\n\r\nI use the following autocommand in filetype.vim:\r\n\r\n   au! BufRead,BufNewFile *.m      set ft=mma sw=2","5":"  * copy this file to $HOME\/.vim\/indent\/mma.vim\r\n    (%HOME%\\vimfiles\\indent\\mma.vim for windows)\r\n\r\n  * Open a Mathematica file **\r\n\r\n**Note that both Mathematica and Matlab use .m file extensions, so if you are editing Mathematica .m files, you need to either manually :set ft=mma or edit your filetype.vim file.\r\n\r\nI use the following autocommand in filetype.vim:\r\n\r\n   au! BufRead,BufNewFile *.m      set ft=mma sw=2","first_name":"steve","6":"steve","last_name":"layland","7":"layland","releases":[{"0":"1274","vim_version":"6.0","1":"6.0","script_version":"1.1","2":"1.1","version_comment":"* mo betta indenting\r\n* doesn't indent { if &si==1","3":"* mo betta indenting\r\n* doesn't indent { if &si==1","package":"mma.vim","4":"mma.vim","src_id":"4254","5":"4254","creation_date":"1115485285","6":"1115485285"},{"0":"1274","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"mma.vim","4":"mma.vim","src_id":"4242","5":"4242","creation_date":"1115214119","6":"1115214119"}]},"1273":{"script_id":"1273","0":"1273","script_name":"Mathematica Syntax File","1":"Mathematica Syntax File","script_type":"syntax","2":"syntax","summary":"Syntax highlighting file for Mathematica code","3":"Syntax highlighting file for Mathematica code","description":"[ Note, as of May 2005,  this is included in Vim7 ]\r\n\r\nThis file greatly extends the old Mathematica syntax highlighting that has traditionally come with vim.  It has substantial support for Mathematica patterns, operators, and includes comments notation goodies, such as special function comments beginning with (**.  Try it out and let me know what you think.\r\n\r\nAdd autoindenting vimscript #1274, salt and pepper to taste.","4":"[ Note, as of May 2005,  this is included in Vim7 ]\r\n\r\nThis file greatly extends the old Mathematica syntax highlighting that has traditionally come with vim.  It has substantial support for Mathematica patterns, operators, and includes comments notation goodies, such as special function comments beginning with (**.  Try it out and let me know what you think.\r\n\r\nAdd autoindenting vimscript #1274, salt and pepper to taste.","install_details":"Install instructions are also in the file.\r\n\r\nBasically:\r\n\r\n   * Drop mma.vim into $HOME\/.vim\/syntax\/\r\n     (%HOME%\\vimfiles\\syntax\\ for Windows)\r\n \r\n   * Open a Mathematica file**\r\n\r\n**Note that both Mathematica and Matlab use .m file extensions, so if you are editing Mathematica .m files, you need to either manually :set ft=mma or edit your filetype.vim file.\r\n\r\nI use the following autocommand in filetype.vim:\r\n\r\n   au! BufRead,BufNewFile *.m      set ft=mma sw=2","5":"Install instructions are also in the file.\r\n\r\nBasically:\r\n\r\n   * Drop mma.vim into $HOME\/.vim\/syntax\/\r\n     (%HOME%\\vimfiles\\syntax\\ for Windows)\r\n \r\n   * Open a Mathematica file**\r\n\r\n**Note that both Mathematica and Matlab use .m file extensions, so if you are editing Mathematica .m files, you need to either manually :set ft=mma or edit your filetype.vim file.\r\n\r\nI use the following autocommand in filetype.vim:\r\n\r\n   au! BufRead,BufNewFile *.m      set ft=mma sw=2","first_name":"steve","6":"steve","last_name":"layland","7":"layland","releases":[{"0":"1273","vim_version":"6.0","1":"6.0","script_version":"1.3","2":"1.3","version_comment":"* Added a bunch of keywords\r\n* Cleaned up for addition to vim build","3":"* Added a bunch of keywords\r\n* Cleaned up for addition to vim build","package":"mma.vim","4":"mma.vim","src_id":"4300","5":"4300","creation_date":"1116531828","6":"1116531828"},{"0":"1273","vim_version":"6.0","1":"6.0","script_version":"1.2","2":"1.2","version_comment":"* forgot map... teehee","3":"* forgot map... teehee","package":"mma.vim","4":"mma.vim","src_id":"4252","5":"4252","creation_date":"1115405721","6":"1115405721"},{"0":"1273","vim_version":"6.0","1":"6.0","script_version":"1.2","2":"1.2","version_comment":"Quick fixes.\r\n* Special comment titles correctly terminate\r\n* emphasis only for words","3":"Quick fixes.\r\n* Special comment titles correctly terminate\r\n* emphasis only for words","package":"mma.vim","4":"mma.vim","src_id":"4251","5":"4251","creation_date":"1115403369","6":"1115403369"},{"0":"1273","vim_version":"6.0","1":"6.0","script_version":"1.1","2":"1.1","version_comment":"* Fixed some overly greedy highlighting inside of comments.\r\n* Added a bunch of keywords for symbols not often used as Functions (like String, GoldenRatio, etc...)\r\n* Will tackle folding next.","3":"* Fixed some overly greedy highlighting inside of comments.\r\n* Added a bunch of keywords for symbols not often used as Functions (like String, GoldenRatio, etc...)\r\n* Will tackle folding next.","package":"mma.vim","4":"mma.vim","src_id":"4247","5":"4247","creation_date":"1115336748","6":"1115336748"},{"0":"1273","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"mma.vim","4":"mma.vim","src_id":"4241","5":"4241","creation_date":"1115213504","6":"1115213504"}]},"1272":{"script_id":"1272","0":"1272","script_name":"php_check_syntax.vim","1":"php_check_syntax.vim","script_type":"ftplugin","2":"ftplugin","summary":"Check the syntax when saving or reading a php file","3":"Check the syntax when saving or reading a php file","description":"This plugin is superseded by vimscript #1431.\r\n\r\nThis ftplugin is based on Klaus Horsten's php_console (vimscript #779). In \r\nopposition to php_console, it only checks the syntax. It does this automatically\r\nwhen opening or closing a file.\r\n\r\nIf you use this as a ftplugin, the script will miss the first BufRead event \r\nas this is when it's being loaded.\r\n\r\nIf php isn't in your path, set the g:php_check_syntax_cmd variable \r\n(including the -l switch).\r\n","4":"This plugin is superseded by vimscript #1431.\r\n\r\nThis ftplugin is based on Klaus Horsten's php_console (vimscript #779). In \r\nopposition to php_console, it only checks the syntax. It does this automatically\r\nwhen opening or closing a file.\r\n\r\nIf you use this as a ftplugin, the script will miss the first BufRead event \r\nas this is when it's being loaded.\r\n\r\nIf php isn't in your path, set the g:php_check_syntax_cmd variable \r\n(including the -l switch).\r\n","install_details":"Save this file either in ~\/.vim\/ftplugin\/php\/ or ~\/.vim\/plugin\/.\r\n\r\n\r\nAlso available via git\r\nhttp:\/\/github.com\/tomtom\/vimtlib\/tree\/master\r\n","5":"Save this file either in ~\/.vim\/ftplugin\/php\/ or ~\/.vim\/plugin\/.\r\n\r\n\r\nAlso available via git\r\nhttp:\/\/github.com\/tomtom\/vimtlib\/tree\/master\r\n","first_name":"Tom","6":"Tom","last_name":"Link","7":"Link","releases":[{"0":"1272","vim_version":"6.0","1":"6.0","script_version":"0.2","2":"0.2","version_comment":"Reset makeprg & errorformat to its initial value. Don't set shellpipe.","3":"Reset makeprg & errorformat to its initial value. Don't set shellpipe.","package":"php_check_syntax.vim","4":"php_check_syntax.vim","src_id":"4240","5":"4240","creation_date":"1115186844","6":"1115186844"}]},"1271":{"script_id":"1271","0":"1271","script_name":"rubikscube.vim","1":"rubikscube.vim","script_type":"game","2":"game","summary":"a rubik's cube game in vim script","3":"a rubik's cube game in vim script","description":"Commands:     \r\n\r\n- u, d, l, r, f, b to turn up, down, left, right, front and back faces clockwise (whatever cube orientation) \r\n- c, m, v to turn the three belts clockwise\r\n- shift + letter for turning counterclockwise - ctrl + letter for half turn \r\n- the whole cube can turn with the four arrows and Pgup\/Pgdown keys\r\n- sramble cube with s key, reset it with S\r\n\r\nTODO:\r\n- more configurable display\r\n- add some edit technique with a solver algorithm - in order to solve a real cube :-) \r\n- chrono + high score stuff \r\n- support for 4x4 and 5x5 cubes \r\n- write moves in letters when done\r\n- some optimization (seems to be slow on old or \"slow networked display\" machines) \r\n- etc.\r\n","4":"Commands:     \r\n\r\n- u, d, l, r, f, b to turn up, down, left, right, front and back faces clockwise (whatever cube orientation) \r\n- c, m, v to turn the three belts clockwise\r\n- shift + letter for turning counterclockwise - ctrl + letter for half turn \r\n- the whole cube can turn with the four arrows and Pgup\/Pgdown keys\r\n- sramble cube with s key, reset it with S\r\n\r\nTODO:\r\n- more configurable display\r\n- add some edit technique with a solver algorithm - in order to solve a real cube :-) \r\n- chrono + high score stuff \r\n- support for 4x4 and 5x5 cubes \r\n- write moves in letters when done\r\n- some optimization (seems to be slow on old or \"slow networked display\" machines) \r\n- etc.\r\n","install_details":"Source the file in an empty buffer.\r\n\r\nUse preferably the gui, for colors. This should work with gvim version > 6.1 (apparently cursor() fonction is not present on earlier versions)\r\n\r\nVersion used for development is 6.3.4\r\n\r\n**** SAVE EVERYTHING BEFORE DOING IT ****\r\n","5":"Source the file in an empty buffer.\r\n\r\nUse preferably the gui, for colors. This should work with gvim version > 6.1 (apparently cursor() fonction is not present on earlier versions)\r\n\r\nVersion used for development is 6.3.4\r\n\r\n**** SAVE EVERYTHING BEFORE DOING IT ****\r\n","first_name":"olivier","6":"olivier","last_name":"vermersch","7":"vermersch","releases":[{"0":"1271","vim_version":"6.0","1":"6.0","script_version":"v0.2","2":"v0.2","version_comment":"v0.2:\n - scramble\/reset key \n - possibility to rotate the whole cube \n - simplified display\n - now use the up\/down\/left\/right\/back\/front convention for move keys\n - belt moves (c, m, v)\n - magenta color instead of lightred for orange face\n - use \"normal!\" instead of unset mappings for display\n","3":"v0.2:\n - scramble\/reset key \n - possibility to rotate the whole cube \n - simplified display\n - now use the up\/down\/left\/right\/back\/front convention for move keys\n - belt moves (c, m, v)\n - magenta color instead of lightred for orange face\n - use \"normal!\" instead of unset mappings for display\n","package":"rubikscube.vim","4":"rubikscube.vim","src_id":"4285","5":"4285","creation_date":"1116264805","6":"1116264805"},{"0":"1271","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"rubikscube.vim","4":"rubikscube.vim","src_id":"4233","5":"4233","creation_date":"1115124603","6":"1115124603"}]},"1270":{"script_id":"1270","0":"1270","script_name":"drc_indent","1":"drc_indent","script_type":"indent","2":"indent","summary":"DrC's indent scripts (currently: sh LaTeX vim maple)","3":"DrC's indent scripts (currently: sh LaTeX vim maple)","description":"DrChip's indent files; some are modified from the distribution (such as the ones for sh, vim) and some are new (maple, tex). They're what I use.  Indenting is one of those \"Irrationality Reigns\" topics; everyone seems to have a lock on the Right Way to do it.  So, my Right Way may not be yours (sorry!).\r\n","4":"DrChip's indent files; some are modified from the distribution (such as the ones for sh, vim) and some are new (maple, tex). They're what I use.  Indenting is one of those \"Irrationality Reigns\" topics; everyone seems to have a lock on the Right Way to do it.  So, my Right Way may not be yours (sorry!).\r\n","install_details":"1. ***IMPORTANT*** Copy any current .vim\/indent\/*.vim  (or ...vimfiles\\indent\\*.vim) files to a safe location\r\n2. Place drc_indent.tar.gz in your $HOME\/.vim or ..wherever..\\vimfiles directory\r\n3. gunzip drc_indent.tar.gz\r\n4. tar -oxvf drc_indent.tar\r\n5. Have  \"filetype plugin indent on\" in your <.vimrc>\r\n6. If you don't like the new indenting, just remove\/delete the associated indent file, or copy the old one(s) back.\r\n","5":"1. ***IMPORTANT*** Copy any current .vim\/indent\/*.vim  (or ...vimfiles\\indent\\*.vim) files to a safe location\r\n2. Place drc_indent.tar.gz in your $HOME\/.vim or ..wherever..\\vimfiles directory\r\n3. gunzip drc_indent.tar.gz\r\n4. tar -oxvf drc_indent.tar\r\n5. Have  \"filetype plugin indent on\" in your <.vimrc>\r\n6. If you don't like the new indenting, just remove\/delete the associated indent file, or copy the old one(s) back.\r\n","first_name":"Charles","6":"Charles","last_name":"Campbell","7":"Campbell","releases":[{"0":"1270","vim_version":"6.0","1":"6.0","script_version":"1","2":"1","version_comment":"Initial upload","3":"Initial upload","package":"drc_indent.tar.gz","4":"drc_indent.tar.gz","src_id":"4232","5":"4232","creation_date":"1115119597","6":"1115119597"}]},"1269":{"script_id":"1269","0":"1269","script_name":"drcstubs","1":"drcstubs","script_type":"ftplugin","2":"ftplugin","summary":"Imaps to provide active stubs  (currently: c, LaTeX, sh, vim)","3":"Imaps to provide active stubs  (currently: c, LaTeX, sh, vim)","description":"All of the DrCStubs ftplugin scripts provide maps which work during insert mode.  One may use either the shorthand or longhand maps to invoke the corresponding imap.  They are invoked whenever a string is followed by a backquote.\r\n\r\nOne major advantage of these imaps is that they, in turn, take advantage of the user's cindent settings and\/or indentation scripts.  Thus the result should be as if the user had typed them him\/herself.\r\n\r\n  * These imaps will not operate if \"set paste:\" is on.\r\n  * They work well with vimscript#1270 indenting scripts\r\n\r\nIn the maps below:\r\n\r\n An \"X\" is where the cursor will end up after the map is invoked.\r\n An \"Y\" is where the cursor will end up after an <esc> is pressed.\r\n A  \"|\" means a newline.\r\n\r\nAnother form of help is available by typing >\r\n\r\n :Drcstubs\r\n\r\n------------------\r\nC LANGUAGE SUPPORT\r\n------------------\r\n     Shorthand    Longhand     Expands\r\n     Map          Map          To\r\n     ---------    --------     -------\r\n     i`           if`          if(X) {Y}\r\n     e`           els[e]`      else {X}\r\n     ei`          eli[f]`      else if(X) {Y}\r\n     f`           for\\=`       for(X;;) {Y}\r\n     w`           wh[ile]`     while(X) {Y}\r\n     s`           sw[itch]`    switch(X) {Y}\r\n     c`           ca[se]`      case X: Y break;\r\n     d`           defa[ult]`   default: Y break;\r\n     `            do`          do {X} while(Y);\r\n     E`           Ed[bg]`      Edbg((\\\"func(X)\\\"Y));\r\n     R`           Rd[bg]`      Rdbg((\\\"funcX\\\"Y));\r\n     D`           Dp[rintf]`   Dprintf((1,\\\"X\\\"Y));\r\n                  in[clude]`   #include X\r\n                  de[fine]`    #define X\r\n                  #`           #ifdef X ... #endif\r\n\r\n-------------\r\nLATEX SUPPORT\r\n-------------\r\n       Environments And Abbreviations\r\n     Shorthand    Longhand     Expands\r\n     Map          Map          To\r\n     ---------    --------     -------\r\n     align`                    \\begin{align}|X|\\end{align}\r\n     arr`         array`       \\left[\\begin{array}{ccc}|X|\\end{array}\\right]\r\n     ctr`         center`      \\begin{center}|X|\\end{center}\r\n     desc`        description` \\begin{description}|\\item[X]|\\end{sdescription}\r\n     enum`        enumerate`   \\begin{enumerate}|\\item X|\\end{enumerate}\r\n     eps`         epsf`        \\begin{figure}[H]\\centering\\framebox{\\epsfbox{X.eps}}\\end{figure}\r\n     eqn`         equation`    \\begin{equation}|X|\\end{equation}\r\n     eqna`        eqnarray`    \\begin{eqnarray}|X&=& Y \\\\|\\end{eqnarray}\r\n     fig`         figure`      \\begin{figure}[H]\\centering \\framebox{X} \\caption{CAPTION HERE} \\end{figure}\r\n     flalign`                  \\begin{flalign}|X|\\end{flalign}\r\n     frac`                     \\frac{X}{Y}\r\n     gat`         gather`      \\begin{gather}|X|\\end{gather}\r\n     i`                        \\item X\r\n     i`                        \\item[X] Y        (if vim v7, and in a description block)\r\n     item`        itemize`     \\begin{itemize}|\\item X|\\end{itemize}\r\n     mat`         matrix`      \\left[|\\begin{array}{cc}| X &   & \\\\|&   & |\\end{array}|\\right]\r\n     mini`        minipage`    \\begin{minipage}[H]{4in}|X|\\end{minipage}\r\n     multc`       multicol`    \\multicolumn{1}{X|c|}{MultiColumn} \r\n     multl`       multline`    \\begin{multline}|X|\\end{multline}\r\n     split`                    \\begin{equation}\\begin{split}|X|\\end{split}\\end{equation}\r\n     tab`         tabular`     (too long for here)\r\n     v`                        \\verb`X`\r\n     verb`        verbatim`    \\begin{verbatim}|X|\\end{verbatim}\r\n\r\n         Script Style Support\r\n     Shorthand    Longhand     Expands\r\n     Map          Map          To\r\n     ---------    --------     -------\r\n     bf`                       \\textbf{}\r\n     it`                       \\textit{}\r\n     rm`                       \\textrm{}\r\n     sc`                       \\textsc{}\r\n     sf`                       \\textsf{}\r\n     sl`                       \\textsl{}\r\n     tt`                       \\texttt{}\r\n     mtt`                      \\mathtt{}\r\n     mrm`                      \\mathrm{}\r\n     mbf`                      \\mathbf{}\r\n     msf`                      \\mathsf{}\r\n     mtt`                      \\mathtt{}\r\n     mit`                      \\mathit{}\r\n     mcal`                     \\mathcal{}\r\n\r\n                 Greek Letters:\r\n     Shorthand    Expands        Shorthand    Expands\r\n     Map          To             Map          To\r\n     ---------    -------        ---------    -------\r\n     a`           \\alpha        v             \\nu\r\n     b`           \\beta         f             \\xi\r\n     g`           \\gamma        p             \\pi\r\n     d`           \\delta        vp            \\varpi\r\n     e`           \\epsilon      r             \\rho\r\n     ve`          \\varepsilon   vr            \\varrho\r\n     z`           \\zeta         s             \\sigma\r\n     n`           \\eta          v             \\varsigma\r\n     t`           \\theta        t             \\tau\r\n     vt`          \\vartheta     u             \\upsilon\r\n     io`          \\iota         h             \\phi\r\n     k`           \\kappa        vh            \\varphi\r\n     l`           \\lambda       x             \\chi\r\n     m`           \\mu           q             \\psi\r\n     w`           \\omega\r\n\r\n\r\n----------\r\nSH SUPPORT\r\n----------\r\n     Shorthand    Longhand     Expands\r\n     Map          Map          To\r\n     ---------    --------     -------\r\n     ca[se]`      c`           case X in|Y|esac\r\n     fo[r]`       f`           for X in Y ; do|Z|done\r\n     if`          i`           if [[ X ]]; then|Y|fi\r\n     eli[f]`      ei`          elif [[ X ]]; then|Y\r\n     els[e]`      e`           else|X\r\n     fu[nction]`               function X|{|Y|}\r\n     wh[ile]`     w`           while [[ X ]]; do|Y|done\r\n\r\n\r\n-----------\r\nVIM SUPPORT\r\n-----------\r\n     Shorthand    Longhand     Expands\r\n     Map          Map          To\r\n     ---------    --------     -------\r\n     i            if           if X|endif\r\n     e            els[e]       else|X\r\n     ei           eli[f]       elseif X\r\n                  fu[nction]   fun! X(Y)|endfun\r\n     w            wh[ile]      while X|endwhile\r\n     F            Df[unc]      call Dfunc(\"func(X)\")|Y\r\n     R            Dr[et]       call Dret(\"return func X\")\r\n     D            De[echo]     call Decho(\"X\")|Y\r\n\r\n(alpha\/beta version available at http:\/\/www.drchip.org\/astronaut\/vim\/index.html#DRCSTUBS)\r\n","4":"All of the DrCStubs ftplugin scripts provide maps which work during insert mode.  One may use either the shorthand or longhand maps to invoke the corresponding imap.  They are invoked whenever a string is followed by a backquote.\r\n\r\nOne major advantage of these imaps is that they, in turn, take advantage of the user's cindent settings and\/or indentation scripts.  Thus the result should be as if the user had typed them him\/herself.\r\n\r\n  * These imaps will not operate if \"set paste:\" is on.\r\n  * They work well with vimscript#1270 indenting scripts\r\n\r\nIn the maps below:\r\n\r\n An \"X\" is where the cursor will end up after the map is invoked.\r\n An \"Y\" is where the cursor will end up after an <esc> is pressed.\r\n A  \"|\" means a newline.\r\n\r\nAnother form of help is available by typing >\r\n\r\n :Drcstubs\r\n\r\n------------------\r\nC LANGUAGE SUPPORT\r\n------------------\r\n     Shorthand    Longhand     Expands\r\n     Map          Map          To\r\n     ---------    --------     -------\r\n     i`           if`          if(X) {Y}\r\n     e`           els[e]`      else {X}\r\n     ei`          eli[f]`      else if(X) {Y}\r\n     f`           for\\=`       for(X;;) {Y}\r\n     w`           wh[ile]`     while(X) {Y}\r\n     s`           sw[itch]`    switch(X) {Y}\r\n     c`           ca[se]`      case X: Y break;\r\n     d`           defa[ult]`   default: Y break;\r\n     `            do`          do {X} while(Y);\r\n     E`           Ed[bg]`      Edbg((\\\"func(X)\\\"Y));\r\n     R`           Rd[bg]`      Rdbg((\\\"funcX\\\"Y));\r\n     D`           Dp[rintf]`   Dprintf((1,\\\"X\\\"Y));\r\n                  in[clude]`   #include X\r\n                  de[fine]`    #define X\r\n                  #`           #ifdef X ... #endif\r\n\r\n-------------\r\nLATEX SUPPORT\r\n-------------\r\n       Environments And Abbreviations\r\n     Shorthand    Longhand     Expands\r\n     Map          Map          To\r\n     ---------    --------     -------\r\n     align`                    \\begin{align}|X|\\end{align}\r\n     arr`         array`       \\left[\\begin{array}{ccc}|X|\\end{array}\\right]\r\n     ctr`         center`      \\begin{center}|X|\\end{center}\r\n     desc`        description` \\begin{description}|\\item[X]|\\end{sdescription}\r\n     enum`        enumerate`   \\begin{enumerate}|\\item X|\\end{enumerate}\r\n     eps`         epsf`        \\begin{figure}[H]\\centering\\framebox{\\epsfbox{X.eps}}\\end{figure}\r\n     eqn`         equation`    \\begin{equation}|X|\\end{equation}\r\n     eqna`        eqnarray`    \\begin{eqnarray}|X&=& Y \\\\|\\end{eqnarray}\r\n     fig`         figure`      \\begin{figure}[H]\\centering \\framebox{X} \\caption{CAPTION HERE} \\end{figure}\r\n     flalign`                  \\begin{flalign}|X|\\end{flalign}\r\n     frac`                     \\frac{X}{Y}\r\n     gat`         gather`      \\begin{gather}|X|\\end{gather}\r\n     i`                        \\item X\r\n     i`                        \\item[X] Y        (if vim v7, and in a description block)\r\n     item`        itemize`     \\begin{itemize}|\\item X|\\end{itemize}\r\n     mat`         matrix`      \\left[|\\begin{array}{cc}| X &   & \\\\|&   & |\\end{array}|\\right]\r\n     mini`        minipage`    \\begin{minipage}[H]{4in}|X|\\end{minipage}\r\n     multc`       multicol`    \\multicolumn{1}{X|c|}{MultiColumn} \r\n     multl`       multline`    \\begin{multline}|X|\\end{multline}\r\n     split`                    \\begin{equation}\\begin{split}|X|\\end{split}\\end{equation}\r\n     tab`         tabular`     (too long for here)\r\n     v`                        \\verb`X`\r\n     verb`        verbatim`    \\begin{verbatim}|X|\\end{verbatim}\r\n\r\n         Script Style Support\r\n     Shorthand    Longhand     Expands\r\n     Map          Map          To\r\n     ---------    --------     -------\r\n     bf`                       \\textbf{}\r\n     it`                       \\textit{}\r\n     rm`                       \\textrm{}\r\n     sc`                       \\textsc{}\r\n     sf`                       \\textsf{}\r\n     sl`                       \\textsl{}\r\n     tt`                       \\texttt{}\r\n     mtt`                      \\mathtt{}\r\n     mrm`                      \\mathrm{}\r\n     mbf`                      \\mathbf{}\r\n     msf`                      \\mathsf{}\r\n     mtt`                      \\mathtt{}\r\n     mit`                      \\mathit{}\r\n     mcal`                     \\mathcal{}\r\n\r\n                 Greek Letters:\r\n     Shorthand    Expands        Shorthand    Expands\r\n     Map          To             Map          To\r\n     ---------    -------        ---------    -------\r\n     a`           \\alpha        v             \\nu\r\n     b`           \\beta         f             \\xi\r\n     g`           \\gamma        p             \\pi\r\n     d`           \\delta        vp            \\varpi\r\n     e`           \\epsilon      r             \\rho\r\n     ve`          \\varepsilon   vr            \\varrho\r\n     z`           \\zeta         s             \\sigma\r\n     n`           \\eta          v             \\varsigma\r\n     t`           \\theta        t             \\tau\r\n     vt`          \\vartheta     u             \\upsilon\r\n     io`          \\iota         h             \\phi\r\n     k`           \\kappa        vh            \\varphi\r\n     l`           \\lambda       x             \\chi\r\n     m`           \\mu           q             \\psi\r\n     w`           \\omega\r\n\r\n\r\n----------\r\nSH SUPPORT\r\n----------\r\n     Shorthand    Longhand     Expands\r\n     Map          Map          To\r\n     ---------    --------     -------\r\n     ca[se]`      c`           case X in|Y|esac\r\n     fo[r]`       f`           for X in Y ; do|Z|done\r\n     if`          i`           if [[ X ]]; then|Y|fi\r\n     eli[f]`      ei`          elif [[ X ]]; then|Y\r\n     els[e]`      e`           else|X\r\n     fu[nction]`               function X|{|Y|}\r\n     wh[ile]`     w`           while [[ X ]]; do|Y|done\r\n\r\n\r\n-----------\r\nVIM SUPPORT\r\n-----------\r\n     Shorthand    Longhand     Expands\r\n     Map          Map          To\r\n     ---------    --------     -------\r\n     i            if           if X|endif\r\n     e            els[e]       else|X\r\n     ei           eli[f]       elseif X\r\n                  fu[nction]   fun! X(Y)|endfun\r\n     w            wh[ile]      while X|endwhile\r\n     F            Df[unc]      call Dfunc(\"func(X)\")|Y\r\n     R            Dr[et]       call Dret(\"return func X\")\r\n     D            De[echo]     call Decho(\"X\")|Y\r\n\r\n(alpha\/beta version available at http:\/\/www.drchip.org\/astronaut\/vim\/index.html#DRCSTUBS)\r\n","install_details":"1. Place drcstubs.tar.gz in your $HOME\/.vim or ..wherever..\\vimfiles directory\r\n2. gunzip drcstubs.tar.gz\r\n3. tar -oxvf drcstubs.tar\r\n4. Have  \"filetype plugin indent on\" in your <.vimrc>\r\n","5":"1. Place drcstubs.tar.gz in your $HOME\/.vim or ..wherever..\\vimfiles directory\r\n2. gunzip drcstubs.tar.gz\r\n3. tar -oxvf drcstubs.tar\r\n4. Have  \"filetype plugin indent on\" in your <.vimrc>\r\n","first_name":"Charles","6":"Charles","last_name":"Campbell","7":"Campbell","releases":[{"0":"1269","vim_version":"7.0","1":"7.0","script_version":"3","2":"3","version_comment":"New mappings and menu support in stub (template) files for c, sh, tex, and vim","3":"New mappings and menu support in stub (template) files for c, sh, tex, and vim","package":"drcstubs.vba.gz","4":"drcstubs.vba.gz","src_id":"12760","5":"12760","creation_date":"1270133174","6":"1270133174"},{"0":"1269","vim_version":"6.0","1":"6.0","script_version":"1","2":"1","version_comment":"Initial upload","3":"Initial upload","package":"drcstubs.tar.gz","4":"drcstubs.tar.gz","src_id":"4231","5":"4231","creation_date":"1115118847","6":"1115118847"}]},"1268":{"script_id":"1268","0":"1268","script_name":"acsb","1":"acsb","script_type":"utility","2":"utility","summary":"CScope frontend (multi queries, multi stacks)","3":"CScope frontend (multi queries, multi stacks)","description":"A cscope frontend supporting\r\no Multiple queries\r\n   It uses a buffer for listing the results of cscope queries.\r\no Multiple tag stacks\r\n   Supports multiple tag stacks for serious code analyzis.\r\n   The stacks are shown in a buffer.\r\nMore information (e.g. usage) can be found at the beginning of the script file.\r\nIt uses its own tag stack and not the one that vim has built in. It means that\r\nif you use both vim's ctags support and this script in parallel the two tag stacks\r\nwill not interfere.\r\n\r\n","4":"A cscope frontend supporting\r\no Multiple queries\r\n   It uses a buffer for listing the results of cscope queries.\r\no Multiple tag stacks\r\n   Supports multiple tag stacks for serious code analyzis.\r\n   The stacks are shown in a buffer.\r\nMore information (e.g. usage) can be found at the beginning of the script file.\r\nIt uses its own tag stack and not the one that vim has built in. It means that\r\nif you use both vim's ctags support and this script in parallel the two tag stacks\r\nwill not interfere.\r\n\r\n","install_details":"Copy this file into ~\/.vim\/plugins\/\r\nEdit the keybindings in the beginning of the script file. It is very likely that the default clashes with your settings.\r\n","5":"Copy this file into ~\/.vim\/plugins\/\r\nEdit the keybindings in the beginning of the script file. It is very likely that the default clashes with your settings.\r\n","first_name":"Gabor","6":"Gabor","last_name":"Fekete","7":"Fekete","releases":[{"0":"1268","vim_version":"6.0","1":"6.0","script_version":"200608xx","2":"200608xx","version_comment":"Updated the documentation","3":"Updated the documentation","package":"acsb.tar.gz","4":"acsb.tar.gz","src_id":"6081","5":"6081","creation_date":"1155904059","6":"1155904059"},{"0":"1268","vim_version":"6.0","1":"6.0","script_version":"200608xx","2":"200608xx","version_comment":"o Fix: don't rebuild the database when not needed\r\no Mod: Use strings instead of numbers for ACSBfindsym.\r\no Add: support for separate cscope.out directory in the source tree.\r\nE.g. If your source code is at \/home\/joe\/code, then you can have\r\nthe cscope.* files built in \/home\/joe\/code\/cscope-data\/.\r\no Add: C-R rebuilds the database.\r\n","3":"o Fix: don't rebuild the database when not needed\r\no Mod: Use strings instead of numbers for ACSBfindsym.\r\no Add: support for separate cscope.out directory in the source tree.\r\nE.g. If your source code is at \/home\/joe\/code, then you can have\r\nthe cscope.* files built in \/home\/joe\/code\/cscope-data\/.\r\no Add: C-R rebuilds the database.\r\n","package":"acsb.tar.gz","4":"acsb.tar.gz","src_id":"6080","5":"6080","creation_date":"1155902618","6":"1155902618"}]},"1267":{"script_id":"1267","0":"1267","script_name":"teol.vim","1":"teol.vim","script_type":"utility","2":"utility","summary":":TEOL <string> and :TSOL <string>; toggles string at end\/start of line(s)","3":":TEOL <string> and :TSOL <string>; toggles string at end\/start of line(s)","description":"This is a vim remake of an old macro I had for Multi-Edit, handy it was though\r\nnot so necessary with VIM, given A and :s but this will not mess up your cursor\r\nposition, works on a range, etc. It has some use.\r\n\r\nThere are default\/example mappings for both visual and normal modes:\r\n\r\nFor end of line toggling:\r\n\r\n<leader>;    toggles \";\" at end of line.\r\n<leader>,    toggles \",\" at end of line.\r\n<leader>:    toggles \":\" at end of line.\r\n\r\n\r\nFor start of line: (start of line for this is first non white space char, like\r\n^ as opposed to 0 )\r\n\r\n<leader>s,    toggles \", \" at start of line.\r\n<leader>s:    toggles \": \" at start of line.\r\n\r\n\r\nNOTE that you can toggle strings not just chars; I.e. \":TSOL --\", \":TEOL --\"\r\nand so on.","4":"This is a vim remake of an old macro I had for Multi-Edit, handy it was though\r\nnot so necessary with VIM, given A and :s but this will not mess up your cursor\r\nposition, works on a range, etc. It has some use.\r\n\r\nThere are default\/example mappings for both visual and normal modes:\r\n\r\nFor end of line toggling:\r\n\r\n<leader>;    toggles \";\" at end of line.\r\n<leader>,    toggles \",\" at end of line.\r\n<leader>:    toggles \":\" at end of line.\r\n\r\n\r\nFor start of line: (start of line for this is first non white space char, like\r\n^ as opposed to 0 )\r\n\r\n<leader>s,    toggles \", \" at start of line.\r\n<leader>s:    toggles \": \" at start of line.\r\n\r\n\r\nNOTE that you can toggle strings not just chars; I.e. \":TSOL --\", \":TEOL --\"\r\nand so on.","install_details":"Just drop in plugins folder, nothing more nothing less.\r\nOptional: Edit file as desired for mappings; mappings could be placed elsewhere if wanted as they are in the style of: \u00e2\u0080\u009cnnoremap    <leader>;    :TEOL;<cr>\u00e2\u0080\u009d","5":"Just drop in plugins folder, nothing more nothing less.\r\nOptional: Edit file as desired for mappings; mappings could be placed elsewhere if wanted as they are in the style of: \u00e2\u0080\u009cnnoremap    <leader>;    :TEOL;<cr>\u00e2\u0080\u009d","first_name":"Robert","6":"Robert","last_name":"KellyIV","7":"KellyIV","releases":[{"0":"1267","vim_version":"6.0","1":"6.0","script_version":"0.2-","2":"0.2-","version_comment":"Initial upload","3":"Initial upload","package":"teol.vim","4":"teol.vim","src_id":"4217","5":"4217","creation_date":"1114698144","6":"1114698144"}]},"1266":{"script_id":"1266","0":"1266","script_name":"Emacs outline mode","1":"Emacs outline mode","script_type":"syntax","2":"syntax","summary":"Imitates Emacsen","3":"Imitates Emacsen","description":"This is really just a foldexpr function and a few syntax lines.  If you have ever used outline-mode in Emacs, then using this will be obvious.  Just use vim's fold manipulation commands to expand and collapse sections.\r\n\r\nFor the rest, it's really just like any other type of outline mode, except that it uses asterisks at the beginning of a line to indicate the level of the section, as opposed to numerical indexes.  This is very convenient when you'd like to be able to organize information, and also be able to easily RE-organize it without changing a bunch of numbers around.  Good for keeping notes on several topics in one file.   ...or for whatever.  :)","4":"This is really just a foldexpr function and a few syntax lines.  If you have ever used outline-mode in Emacs, then using this will be obvious.  Just use vim's fold manipulation commands to expand and collapse sections.\r\n\r\nFor the rest, it's really just like any other type of outline mode, except that it uses asterisks at the beginning of a line to indicate the level of the section, as opposed to numerical indexes.  This is very convenient when you'd like to be able to organize information, and also be able to easily RE-organize it without changing a bunch of numbers around.  Good for keeping notes on several topics in one file.   ...or for whatever.  :)","install_details":"Place in ~\/.vim\/syntax\/","5":"Place in ~\/.vim\/syntax\/","first_name":"Tye","6":"Tye","last_name":"Zdrojewski","7":"Zdrojewski","releases":[{"0":"1266","vim_version":"6.0","1":"6.0","script_version":"2.0","2":"2.0","version_comment":"- Rewritten to use syntax-folding instead of a fold expression\r\n- Eliminated slowness in folds containing large amounts of text.  A *vast* performance improvement!\r\n","3":"- Rewritten to use syntax-folding instead of a fold expression\r\n- Eliminated slowness in folds containing large amounts of text.  A *vast* performance improvement!\r\n","package":"outline.vim","4":"outline.vim","src_id":"6852","5":"6852","creation_date":"1173504860","6":"1173504860"},{"0":"1266","vim_version":"6.0","1":"6.0","script_version":"1.1","2":"1.1","version_comment":"Initial upload","3":"Initial upload","package":"outline.vim","4":"outline.vim","src_id":"4213","5":"4213","creation_date":"1114671531","6":"1114671531"}]},"1265":{"script_id":"1265","0":"1265","script_name":"IComplete","1":"IComplete","script_type":"utility","2":"utility","summary":"IComplete is a C\/C++\/Java\/C# code completion system using the omnifunc framework","3":"IComplete is a C\/C++\/Java\/C# code completion system using the omnifunc framework","description":"There is a new vim plugin OmniCppComplete at:\r\nhttp:\/\/www.vim.org\/scripts\/script.php?script_id=1520\r\nIt works better, is easier to setup and is also better maintained, so please use that.\r\n\r\nIMPORTANT: I will NOT maintain icomplete in future anymore, if you are interested in improving it, please tell me, and you can take over maintainership.\r\n\r\n------------------------------------\r\n\r\n**** Features ****\r\n- Automatic generation of a tags file for the current source file by building a tree of included files. \r\n- Listing members (also inherited ones) of a class\r\n For QString s; s. only non-static members are suggested, for QString:: only static ones. \r\n- Listing all function signatures of overloading methods\r\n- Recognizes return values of methods.\r\nQWidget w; w.rect().topLeft(). \/\/ Lists completions for a QPoint \r\n- Uses the scope of the cursor position\r\n- Recognizes, if you are inside a method-definition and completes also private or protected variables for this class. For a global scope, only public members are suggested. \r\n- Works in both console and graphical vim\r\n- Uses a cache system for increased spead.\r\n- Understands namespaces\r\n- Automatic completions after . and ->\r\n\r\n------------------------------------\r\n\r\nQuick start: press <Ctrl-X><Ctrl-O> at any code position in insert mode.\r\n\r\nFor more usage information and screenshots or if you want to donate a little bit, then look at:\r\nhttp:\/\/icomplete.sourceforge.net\r\n","4":"There is a new vim plugin OmniCppComplete at:\r\nhttp:\/\/www.vim.org\/scripts\/script.php?script_id=1520\r\nIt works better, is easier to setup and is also better maintained, so please use that.\r\n\r\nIMPORTANT: I will NOT maintain icomplete in future anymore, if you are interested in improving it, please tell me, and you can take over maintainership.\r\n\r\n------------------------------------\r\n\r\n**** Features ****\r\n- Automatic generation of a tags file for the current source file by building a tree of included files. \r\n- Listing members (also inherited ones) of a class\r\n For QString s; s. only non-static members are suggested, for QString:: only static ones. \r\n- Listing all function signatures of overloading methods\r\n- Recognizes return values of methods.\r\nQWidget w; w.rect().topLeft(). \/\/ Lists completions for a QPoint \r\n- Uses the scope of the cursor position\r\n- Recognizes, if you are inside a method-definition and completes also private or protected variables for this class. For a global scope, only public members are suggested. \r\n- Works in both console and graphical vim\r\n- Uses a cache system for increased spead.\r\n- Understands namespaces\r\n- Automatic completions after . and ->\r\n\r\n------------------------------------\r\n\r\nQuick start: press <Ctrl-X><Ctrl-O> at any code position in insert mode.\r\n\r\nFor more usage information and screenshots or if you want to donate a little bit, then look at:\r\nhttp:\/\/icomplete.sourceforge.net\r\n","install_details":"Make sure you have exuberant-ctags (from http:\/\/ctags.sourceforge.net) installed.\r\n\r\nAfter that unpack the .tar.bz2 tarball, an run these commands:\r\n\r\n        # .\/configure\r\n        # make\r\n        # su\r\n        $ make install\r\n\r\nThis will install a command line program 'icomplete' to \/usr\/local\/bin\/icomplete and copies the actual vim scripts to\r\n\/usr\/share\/vim\/vimfiles\/plugin\/icomplete.vim\r\n\/usr\/share\/vim\/vimfiles\/autoload\/cppcomplete.vim\r\n\r\nIf you have vim installed in a different directory, look at the README in the package it explains, how to change these paths.\r\n\r\nIf it still does not work, try to put these lines in your ~\/.vimrc:\r\n\r\nautocmd Filetype cpp,c,java,cs set omnifunc=cppcomplete#Complete\r\n\r\nMake sure you have a vim version with the autocmd feature enabled, which should be the case in most cases anyway.","5":"Make sure you have exuberant-ctags (from http:\/\/ctags.sourceforge.net) installed.\r\n\r\nAfter that unpack the .tar.bz2 tarball, an run these commands:\r\n\r\n        # .\/configure\r\n        # make\r\n        # su\r\n        $ make install\r\n\r\nThis will install a command line program 'icomplete' to \/usr\/local\/bin\/icomplete and copies the actual vim scripts to\r\n\/usr\/share\/vim\/vimfiles\/plugin\/icomplete.vim\r\n\/usr\/share\/vim\/vimfiles\/autoload\/cppcomplete.vim\r\n\r\nIf you have vim installed in a different directory, look at the README in the package it explains, how to change these paths.\r\n\r\nIf it still does not work, try to put these lines in your ~\/.vimrc:\r\n\r\nautocmd Filetype cpp,c,java,cs set omnifunc=cppcomplete#Complete\r\n\r\nMake sure you have a vim version with the autocmd feature enabled, which should be the case in most cases anyway.","first_name":"Martin","6":"Martin","last_name":"Stubenschrott","7":"Stubenschrott","releases":[{"0":"1265","vim_version":"7.0","1":"7.0","script_version":"0.5","2":"0.5","version_comment":"        * IMPORTANT: Last and final release of icomplete, use OmniCppComplete in future\r\n        * autocompletion on . or -> (patch by Sanjaya Karunase)\r\n        * add ability to change name of .icomplete_taglist (Tim Murison)\r\n        * fixed some segfaults (thanks Johannes Winkelmann)\r\n        * cleaned up the doc\r\n","3":"        * IMPORTANT: Last and final release of icomplete, use OmniCppComplete in future\r\n        * autocompletion on . or -> (patch by Sanjaya Karunase)\r\n        * add ability to change name of .icomplete_taglist (Tim Murison)\r\n        * fixed some segfaults (thanks Johannes Winkelmann)\r\n        * cleaned up the doc\r\n","package":"icomplete-0.5.tar.bz2","4":"icomplete-0.5.tar.bz2","src_id":"7855","5":"7855","creation_date":"1193913103","6":"1193913103"},{"0":"1265","vim_version":"7.0","1":"7.0","script_version":"0.4","2":"0.4","version_comment":"Apr 19, 2006:\r\n\t* version 0.4\r\n\t* completely new namespace support (by Maxime Coste)\r\n\t* -t option to specify different tags filename (patch by Yuxuan Wang)\r\n\t* completely new #include file parser, fixes problem of macos which does not understand \\\\s codes in regexps\r\n\t* fixes segfault (replaced mmap with fread)\r\n\t* improved java support\r\n\t* including a shell script to create a java tags file for system classes\r\n\t* placeholders work for more than two arguments now (forgot the 'g' in the\r\n\tsubstitute command)\r\n\t* added sys\/types.h in parse.h and tree.h which solves compiling under\r\n\tMacOS X\r\n","3":"Apr 19, 2006:\r\n\t* version 0.4\r\n\t* completely new namespace support (by Maxime Coste)\r\n\t* -t option to specify different tags filename (patch by Yuxuan Wang)\r\n\t* completely new #include file parser, fixes problem of macos which does not understand \\\\s codes in regexps\r\n\t* fixes segfault (replaced mmap with fread)\r\n\t* improved java support\r\n\t* including a shell script to create a java tags file for system classes\r\n\t* placeholders work for more than two arguments now (forgot the 'g' in the\r\n\tsubstitute command)\r\n\t* added sys\/types.h in parse.h and tree.h which solves compiling under\r\n\tMacOS X\r\n","package":"icomplete-0.4.tar.bz2","4":"icomplete-0.4.tar.bz2","src_id":"5582","5":"5582","creation_date":"1145443809","6":"1145443809"}]},"1264":{"script_id":"1264","0":"1264","script_name":"Quick access file Menu","1":"Quick access file Menu","script_type":"utility","2":"utility","summary":"Add files in current Directory in Menu for quick access","3":"Add files in current Directory in Menu for quick access","description":"This utility pulls all  the file names of a particular type  and present it in menu(currently *.c *.h and *.a51 8051 assembly).This utility is usefull when your compiler generates many object and temp files in current directory  and navigating to select files using  explorer becomes painful.","4":"This utility pulls all  the file names of a particular type  and present it in menu(currently *.c *.h and *.a51 8051 assembly).This utility is usefull when your compiler generates many object and temp files in current directory  and navigating to select files using  explorer becomes painful.","install_details":"Just drop it in plugin directory.and you will see the new menu as CFiles ASMFiles and HFiles they indicates C source files in current directory ,Assembly files and header files.When you select header file from menu it splits the screen to open the file and other files it opens in current workspace.\r\n\r\nYou can change its behaviour by editing the plugin for all three types.\r\n\r\n(In case you want to edit this script follow the seach of \"FLAG\" word in file.)","5":"Just drop it in plugin directory.and you will see the new menu as CFiles ASMFiles and HFiles they indicates C source files in current directory ,Assembly files and header files.When you select header file from menu it splits the screen to open the file and other files it opens in current workspace.\r\n\r\nYou can change its behaviour by editing the plugin for all three types.\r\n\r\n(In case you want to edit this script follow the seach of \"FLAG\" word in file.)","first_name":"vijayandra","6":"vijayandra","last_name":"singh","7":"singh","releases":[{"0":"1264","vim_version":"6.0","1":"6.0","script_version":"1.01","2":"1.01","version_comment":"Added FLAG word so user can change it for different kind of file according to need.","3":"Added FLAG word so user can change it for different kind of file according to need.","package":"filemenu.vim","4":"filemenu.vim","src_id":"4183","5":"4183","creation_date":"1113944631","6":"1113944631"}]},"1262":{"script_id":"1262","0":"1262","script_name":"tex_umlaute","1":"tex_umlaute","script_type":"ftplugin","2":"ftplugin","summary":"replaces German Umlauts with their TeX encodings on save","3":"replaces German Umlauts with their TeX encodings on save","description":"This script is based on vimscript #907 by Timo Teifel. Main reason I wrote this is that I was annoyed by the different encoded Umlauts in TeX files of different authors. Some write {\\\"a}, some \\\"a, some \\\"{a} some even \"a.\r\n\r\nOn loading all occurances of TeX encoded German Umlauts will be replaced by their normal counterparts. On writing they are replaced by a clean standard encoding (\\\"a for an \u00c3\u00a4, \\ss{} for \u00c3\u009f).\r\n\r\nCan be simply extended for other chars or utf-8 codings if there is need for...","4":"This script is based on vimscript #907 by Timo Teifel. Main reason I wrote this is that I was annoyed by the different encoded Umlauts in TeX files of different authors. Some write {\\\"a}, some \\\"a, some \\\"{a} some even \"a.\r\n\r\nOn loading all occurances of TeX encoded German Umlauts will be replaced by their normal counterparts. On writing they are replaced by a clean standard encoding (\\\"a for an \u00c3\u00a4, \\ss{} for \u00c3\u009f).\r\n\r\nCan be simply extended for other chars or utf-8 codings if there is need for...","install_details":"just put it in ~\/.vim\/plugin\/ folder","5":"just put it in ~\/.vim\/plugin\/ folder","first_name":"Frank","6":"Frank","last_name":"Thieme","7":"Thieme","releases":[{"0":"1262","vim_version":"6.0","1":"6.0","script_version":"1.2","2":"1.2","version_comment":"- now (n)german style is really (n)german style (forgot to change after copy & paste)","3":"- now (n)german style is really (n)german style (forgot to change after copy & paste)","package":"tex_umlaute.vim","4":"tex_umlaute.vim","src_id":"4352","5":"4352","creation_date":"1118230497","6":"1118230497"},{"0":"1262","vim_version":"6.0","1":"6.0","script_version":"1.1","2":"1.1","version_comment":"Now detects Umlauts in style \\\"{a} and writes \\\"a instead of {\\\"a}. This is because of kerning between letters is disturbed badly by {\\\"a} style.","3":"Now detects Umlauts in style \\\"{a} and writes \\\"a instead of {\\\"a}. This is because of kerning between letters is disturbed badly by {\\\"a} style.","package":"tex_umlaute.vim","4":"tex_umlaute.vim","src_id":"4341","5":"4341","creation_date":"1117813136","6":"1117813136"},{"0":"1262","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"tex_umlaute.vim","4":"tex_umlaute.vim","src_id":"4170","5":"4170","creation_date":"1113567483","6":"1113567483"}]},"1261":{"script_id":"1261","0":"1261","script_name":"cstol.vim","1":"cstol.vim","script_type":"syntax","2":"syntax","summary":"Colorizes OASIS CSTOL files","3":"Colorizes OASIS CSTOL files","description":"Colorizes OASIS CSTOL ( http:\/\/lasp.colorado.edu\/oasis\/#User%20Interface ) files.  There are some small regular expression bugs, but overall CSTOL scripts are much more readable with this syntax coloration than without it.  I welcome bug reports.","4":"Colorizes OASIS CSTOL ( http:\/\/lasp.colorado.edu\/oasis\/#User%20Interface ) files.  There are some small regular expression bugs, but overall CSTOL scripts are much more readable with this syntax coloration than without it.  I welcome bug reports.","install_details":"Copy this file into your ~\/.vim\/syntax directory.  Then, when opening a CSTOL file, type :set syntax=cstol ... alternatively, put the following in your .vimrc:\r\n\r\nau BufRead,BufNewFile *.prc setfiletype cstol","5":"Copy this file into your ~\/.vim\/syntax directory.  Then, when opening a CSTOL file, type :set syntax=cstol ... alternatively, put the following in your .vimrc:\r\n\r\nau BufRead,BufNewFile *.prc setfiletype cstol","first_name":"Monique","6":"Monique","last_name":"Mudama","7":"Mudama","releases":[{"0":"1261","vim_version":"6.0","1":"6.0","script_version":"1.2","2":"1.2","version_comment":"Initial upload","3":"Initial upload","package":"cstol.vim","4":"cstol.vim","src_id":"4158","5":"4158","creation_date":"1113343490","6":"1113343490"}]},"1260":{"script_id":"1260","0":"1260","script_name":"tmda_filter.vim","1":"tmda_filter.vim","script_type":"syntax","2":"syntax","summary":"colorizes tmda filter files","3":"colorizes tmda filter files","description":"Colorizes the filter files used by TMDA ( http:\/\/www.tmda.net\/ ), the Tagged Message Delivery Agent.\r\n\r\nI don't use all of the features of TMDA, so please let me know of any things that should be colorized and aren't.","4":"Colorizes the filter files used by TMDA ( http:\/\/www.tmda.net\/ ), the Tagged Message Delivery Agent.\r\n\r\nI don't use all of the features of TMDA, so please let me know of any things that should be colorized and aren't.","install_details":"copy into your ~\/.vim\/syntax directory.  I also created a .vim\/filetype.vim with the following contents:\r\n\r\nau BufRead,BufNewFile *\/.tmda\/filters\/* setfiletype tmda_filter","5":"copy into your ~\/.vim\/syntax directory.  I also created a .vim\/filetype.vim with the following contents:\r\n\r\nau BufRead,BufNewFile *\/.tmda\/filters\/* setfiletype tmda_filter","first_name":"Monique","6":"Monique","last_name":"Mudama","7":"Mudama","releases":[{"0":"1260","vim_version":"6.0","1":"6.0","script_version":"1.2","2":"1.2","version_comment":"Initial upload","3":"Initial upload","package":"tmda_filter.vim","4":"tmda_filter.vim","src_id":"4157","5":"4157","creation_date":"1113342644","6":"1113342644"}]},"1259":{"script_id":"1259","0":"1259","script_name":"sienna","1":"sienna","script_type":"color scheme","2":"color scheme","summary":"Color scheme with harmonic colors easy to distinguish (dark and light styles).","3":"Color scheme with harmonic colors easy to distinguish (dark and light styles).","description":"This color scheme has both dark and light styles with harmonic colors easy to distinguish. Terminals are not supported, therefore you should only try it if you use the GUI version of Vim.\r\n\r\nThe versions of this color scheme older than 1.20 contain the light style only.","4":"This color scheme has both dark and light styles with harmonic colors easy to distinguish. Terminals are not supported, therefore you should only try it if you use the GUI version of Vim.\r\n\r\nThe versions of this color scheme older than 1.20 contain the light style only.","install_details":"Just put it in \"~\/.vim\/colors\" or in \"<your vim directory>\\vimfiles\\colors\" on Windows. Do \":colo sienna\" to apply it. If you want to install it as your default color scheme, just add \":colo sienna\" to your vimrc file.\r\n\r\nYou can choose the style by adding one of the following lines to your vimrc or gvimrc file before sourcing the color scheme:\r\n\r\nlet g:sienna_style = 'dark'\r\nlet g:sienna_style = 'light'\r\n\r\nIf none of above lines is given, the light style is choosen.\r\n\r\nYou can switch between these styles by using the :Colo command, like \":Colo dark\" or \":Colo light\" (many thanks to Pan Shizhu for the idea).\r\n\r\nHappy Vimming!","5":"Just put it in \"~\/.vim\/colors\" or in \"<your vim directory>\\vimfiles\\colors\" on Windows. Do \":colo sienna\" to apply it. If you want to install it as your default color scheme, just add \":colo sienna\" to your vimrc file.\r\n\r\nYou can choose the style by adding one of the following lines to your vimrc or gvimrc file before sourcing the color scheme:\r\n\r\nlet g:sienna_style = 'dark'\r\nlet g:sienna_style = 'light'\r\n\r\nIf none of above lines is given, the light style is choosen.\r\n\r\nYou can switch between these styles by using the :Colo command, like \":Colo dark\" or \":Colo light\" (many thanks to Pan Shizhu for the idea).\r\n\r\nHappy Vimming!","first_name":"Georg","6":"Georg","last_name":"Dahn","7":"Dahn","releases":[{"0":"1259","vim_version":"7.0","1":"7.0","script_version":"1.6.2","2":"1.6.2","version_comment":"Changed background of FoldColumn to Normal background.","3":"Changed background of FoldColumn to Normal background.","package":"sienna.vim","4":"sienna.vim","src_id":"21188","5":"21188","creation_date":"1386850430","6":"1386850430"},{"0":"1259","vim_version":"7.0","1":"7.0","script_version":"1.6.1","2":"1.6.1","version_comment":"added CursorColumn, CursorLine, and CursorLineNr.","3":"added CursorColumn, CursorLine, and CursorLineNr.","package":"sienna.vim","4":"sienna.vim","src_id":"20787","5":"20787","creation_date":"1378893384","6":"1378893384"},{"0":"1259","vim_version":"6.0","1":"6.0","script_version":"1.6","2":"1.6","version_comment":"Added colors for popup menu (Vim 7 only). Set background of light scheme to white.","3":"Added colors for popup menu (Vim 7 only). Set background of light scheme to white.","package":"sienna.vim","4":"sienna.vim","src_id":"5617","5":"5617","creation_date":"1146014868","6":"1146014868"}]},"1258":{"script_id":"1258","0":"1258","script_name":"custom","1":"custom","script_type":"color scheme","2":"color scheme","summary":"good color scheme","3":"good color scheme","description":"good color scheme with dark background","4":"good color scheme with dark background","install_details":"copy into \/colors directory","5":"copy into \/colors directory","first_name":"Ravi","6":"Ravi","last_name":"Jammula","7":"Jammula","releases":[{"0":"1258","vim_version":"6.0","1":"6.0","script_version":"1.2","2":"1.2","version_comment":"Minor Adjustments, Removed Settings other than Highlighting","3":"Minor Adjustments, Removed Settings other than Highlighting","package":"custom.vim","4":"custom.vim","src_id":"4497","5":"4497","creation_date":"1124261827","6":"1124261827"},{"0":"1258","vim_version":"6.0","1":"6.0","script_version":"1.1","2":"1.1","version_comment":"Removed settings other than colors.","3":"Removed settings other than colors.","package":"custom.vim","4":"custom.vim","src_id":"4147","5":"4147","creation_date":"1113177959","6":"1113177959"},{"0":"1258","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"custom.vim","4":"custom.vim","src_id":"4145","5":"4145","creation_date":"1113131247","6":"1113131247"}]},"1257":{"script_id":"1257","0":"1257","script_name":"wood.vim","1":"wood.vim","script_type":"color scheme","2":"color scheme","summary":"Wood cabin color scheme","3":"Wood cabin color scheme","description":"This color scheme is based on the aqua.vim color scheme, but using wood color tones instead of aqua blue. The colors are of neutral intensity, low contrast, not too dark and not too bright. It is meant to be an occasional change of pace from the typical color schemes.\r\n","4":"This color scheme is based on the aqua.vim color scheme, but using wood color tones instead of aqua blue. The colors are of neutral intensity, low contrast, not too dark and not too bright. It is meant to be an occasional change of pace from the typical color schemes.\r\n","install_details":"Place the wood.vim file in your ~\/.vim\/colors\/ directory and load it using :colorscheme wood\r\nor restart Vim and the color scheme will appear in the menu.\r\n","5":"Place the wood.vim file in your ~\/.vim\/colors\/ directory and load it using :colorscheme wood\r\nor restart Vim and the color scheme will appear in the menu.\r\n","first_name":"Fred","6":"Fred","last_name":"Daoud","7":"Daoud","releases":[{"0":"1257","vim_version":"6.0","1":"6.0","script_version":"0.9","2":"0.9","version_comment":"Initial upload","3":"Initial upload","package":"wood.vim","4":"wood.vim","src_id":"4142","5":"4142","creation_date":"1113049321","6":"1113049321"}]},"1256":{"script_id":"1256","0":"1256","script_name":"aspvbs.vim","1":"aspvbs.vim","script_type":"indent","2":"indent","summary":"indenting for asp vbs files","3":"indenting for asp vbs files","description":"Having to write active server pages with visual basic script included is pain enough. Vim eases this and with this automatic indenter even more.\r\n\r\nThis script tries to be very smart and will probably fail horribly. Since version 0.4 (there is no 0.3) aspvbs.vim will do indenting based on the context. That means when you are in an html context, the html indenter will be used, otherwise the ASPVBS indenter.\r\n\r\nBut wait, there is even more! The script tries to pick up the previous indent of each block, so when you open a new ASP block with <% the indent of the last ASP block will be resumed.\r\n\r\nThe script works best when an opening <% and a closing %> are placed on a line on their own. You can most definitely break the script by writing code like '%><html><\/html><% ...'\r\n\r\nHere is an example of its indenting sprinkled with comments:\r\n\r\n<%\r\nfunction baz\r\n    if asd then\r\n        bcd\r\n%> \r\n<html>\r\n    <head>\r\n        <title><%=myTitle%><\/title>\r\n    <\/head>\r\n    <body>\r\n<% If myPage = 1 Then %>\r\n        <table> <!-- the indent of body is continued -->\r\n            <tr>\r\n                ...\r\n            <\/tr>\r\n        <\/table>\r\n<% End If %> <!-- the indent of < % if mypage = 1 is picked up -->\r\n    <\/body> <!-- the indent of <\/table> is continued\r\n<%\r\n        ' the indent of line 4 is continued (inside if)\r\n        efg\r\n    end if ' if asd then is closed\r\n\r\n    ' normal asp indent here\r\n    if foo then\r\n        select case blah\r\n            case foo\r\n                Response.Redirect \"google\"\r\n        end select\r\n    else\r\n        Response.Redirect \"yahoo\"\r\n    end if\r\n    =this_is_a_statement()\r\n%>\r\n<\/html>\r\nTest1<%testin1%>Test2<%testin2%>test3<%statement\r\n\r\n    ' for the previous line, the html indenter wins\r\n    =this_is_a_statement2()\r\nend function ' close function baz\r\n%>\r\n\r\n","4":"Having to write active server pages with visual basic script included is pain enough. Vim eases this and with this automatic indenter even more.\r\n\r\nThis script tries to be very smart and will probably fail horribly. Since version 0.4 (there is no 0.3) aspvbs.vim will do indenting based on the context. That means when you are in an html context, the html indenter will be used, otherwise the ASPVBS indenter.\r\n\r\nBut wait, there is even more! The script tries to pick up the previous indent of each block, so when you open a new ASP block with <% the indent of the last ASP block will be resumed.\r\n\r\nThe script works best when an opening <% and a closing %> are placed on a line on their own. You can most definitely break the script by writing code like '%><html><\/html><% ...'\r\n\r\nHere is an example of its indenting sprinkled with comments:\r\n\r\n<%\r\nfunction baz\r\n    if asd then\r\n        bcd\r\n%> \r\n<html>\r\n    <head>\r\n        <title><%=myTitle%><\/title>\r\n    <\/head>\r\n    <body>\r\n<% If myPage = 1 Then %>\r\n        <table> <!-- the indent of body is continued -->\r\n            <tr>\r\n                ...\r\n            <\/tr>\r\n        <\/table>\r\n<% End If %> <!-- the indent of < % if mypage = 1 is picked up -->\r\n    <\/body> <!-- the indent of <\/table> is continued\r\n<%\r\n        ' the indent of line 4 is continued (inside if)\r\n        efg\r\n    end if ' if asd then is closed\r\n\r\n    ' normal asp indent here\r\n    if foo then\r\n        select case blah\r\n            case foo\r\n                Response.Redirect \"google\"\r\n        end select\r\n    else\r\n        Response.Redirect \"yahoo\"\r\n    end if\r\n    =this_is_a_statement()\r\n%>\r\n<\/html>\r\nTest1<%testin1%>Test2<%testin2%>test3<%statement\r\n\r\n    ' for the previous line, the html indenter wins\r\n    =this_is_a_statement2()\r\nend function ' close function baz\r\n%>\r\n\r\n","install_details":"Copy the script into your $VIMRUNTIME\/indent\/ folder and make sure you use the filetype feature. You should at least have \"filetype indent on\" in your vimrc","5":"Copy the script into your $VIMRUNTIME\/indent\/ folder and make sure you use the filetype feature. You should at least have \"filetype indent on\" in your vimrc","first_name":"Tilmann","6":"Tilmann","last_name":"Bitterberg","7":"Bitterberg","releases":[{"0":"1256","vim_version":"6.0","1":"6.0","script_version":"0.4","2":"0.4","version_comment":"Major feature enhancements. Context based indenting, resuming indent and tons of other stuff.","3":"Major feature enhancements. Context based indenting, resuming indent and tons of other stuff.","package":"aspvbs.vim","4":"aspvbs.vim","src_id":"4243","5":"4243","creation_date":"1115218622","6":"1115218622"},{"0":"1256","vim_version":"6.0","1":"6.0","script_version":"0.2","2":"0.2","version_comment":"Incorporated case insensity fixes by Tavish Robinson,\r\nadded indent on ending keywords,\r\nadded class keyword,\r\nspeed improvements","3":"Incorporated case insensity fixes by Tavish Robinson,\r\nadded indent on ending keywords,\r\nadded class keyword,\r\nspeed improvements","package":"aspvbs.vim","4":"aspvbs.vim","src_id":"4196","5":"4196","creation_date":"1114221490","6":"1114221490"},{"0":"1256","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"aspvbs.vim","4":"aspvbs.vim","src_id":"4141","5":"4141","creation_date":"1113040765","6":"1113040765"}]},"1255":{"script_id":"1255","0":"1255","script_name":"pike.vim","1":"pike.vim","script_type":"syntax","2":"syntax","summary":"pike syntax highlighting","3":"pike syntax highlighting","description":"Borrowed a few things from (the much superior) lpc.vim by Shizhu Pan -- which fixed bug with parens among other things, quit highlighting arrays\/mappings as a single giant identifier, and updated the predef function list dramatically.\r\n\r\nIt is otherwise the original syntax file written by Francesco Chemolli.","4":"Borrowed a few things from (the much superior) lpc.vim by Shizhu Pan -- which fixed bug with parens among other things, quit highlighting arrays\/mappings as a single giant identifier, and updated the predef function list dramatically.\r\n\r\nIt is otherwise the original syntax file written by Francesco Chemolli.","install_details":"It's probably simplest to just put this file in your ~\/.vim dir, which (by default) is at the top of your runtimepath.","5":"It's probably simplest to just put this file in your ~\/.vim dir, which (by default) is at the top of your runtimepath.","first_name":"Paul","6":"Paul","last_name":"Miller","7":"Miller","releases":[{"0":"1255","vim_version":"6.0","1":"6.0","script_version":"1.0.7","2":"1.0.7","version_comment":"The pikeRange highlighter was missing ranges without a number on both ends.   This syntax file appears to finally be relatively bug free...","3":"The pikeRange highlighter was missing ranges without a number on both ends.   This syntax file appears to finally be relatively bug free...","package":"pike.vim","4":"pike.vim","src_id":"4161","5":"4161","creation_date":"1113395943","6":"1113395943"},{"0":"1255","vim_version":"6.0","1":"6.0","script_version":"1.0.6","2":"1.0.6","version_comment":"Sadly, I had introduced a bug in the last \"release.\"  I'm obviously not very good at this, but I think _this_ version may be the last one for a while. ","3":"Sadly, I had introduced a bug in the last \"release.\"  I'm obviously not very good at this, but I think _this_ version may be the last one for a while. ","package":"pike.vim","4":"pike.vim","src_id":"4150","5":"4150","creation_date":"1113205219","6":"1113205219"},{"0":"1255","vim_version":"6.0","1":"6.0","script_version":"1.0.5","2":"1.0.5","version_comment":"By copying how perl.vim does numbers, I was able to fix a bunch of problems with the number highlighting in pike.vim.  *whew*  This should be the last update for a while.","3":"By copying how perl.vim does numbers, I was able to fix a bunch of problems with the number highlighting in pike.vim.  *whew*  This should be the last update for a while.","package":"pike.vim","4":"pike.vim","src_id":"4149","5":"4149","creation_date":"1113199124","6":"1113199124"},{"0":"1255","vim_version":"6.0","1":"6.0","script_version":"1.0.3","2":"1.0.3","version_comment":"Yet another tiny update.  The special functions are nolonger predef:: colored.","3":"Yet another tiny update.  The special functions are nolonger predef:: colored.","package":"pike.vim","4":"pike.vim","src_id":"4140","5":"4140","creation_date":"1112966803","6":"1112966803"},{"0":"1255","vim_version":"6.0","1":"6.0","script_version":"1.0.2","2":"1.0.2","version_comment":"yet another miniature fix.  throw is an Exception instead of a predef:: now.","3":"yet another miniature fix.  throw is an Exception instead of a predef:: now.","package":"pike.vim","4":"pike.vim","src_id":"4139","5":"4139","creation_date":"1112966409","6":"1112966409"},{"0":"1255","vim_version":"6.0","1":"6.0","script_version":"1.0.1","2":"1.0.1","version_comment":"I changed the way the predef:: matching is done so it won't hit member functions that have a co-incidentally similar name.","3":"I changed the way the predef:: matching is done so it won't hit member functions that have a co-incidentally similar name.","package":"pike.vim","4":"pike.vim","src_id":"4138","5":"4138","creation_date":"1112964374","6":"1112964374"},{"0":"1255","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"pike.vim","4":"pike.vim","src_id":"4136","5":"4136","creation_date":"1112951090","6":"1112951090"}]},"1254":{"script_id":"1254","0":"1254","script_name":"VIMEN","1":"VIMEN","script_type":"utility","2":"utility","summary":"Vim Is More than Editor Now","3":"Vim Is More than Editor Now","description":"VIMEN is a mini IDE to work with VIM(Gvim) and GDB.\r\nSEE Screen Shots: http:\/\/sourceforge.net\/project\/screenshots.php?group_id=134978&ssid=9952","4":"VIMEN is a mini IDE to work with VIM(Gvim) and GDB.\r\nSEE Screen Shots: http:\/\/sourceforge.net\/project\/screenshots.php?group_id=134978&ssid=9952","install_details":"SEE README","5":"SEE README","first_name":"hao","6":"hao","last_name":"hu","7":"hu","releases":[{"0":"1254","vim_version":"6.0","1":"6.0","script_version":"0.00.0002a","2":"0.00.0002a","version_comment":"Add \"How to\" in README:\r\n-------------------------------------\r\nHOW To Use\r\n----------\r\n1. Easy, just like this:\r\n    python vimen.py <your_executable_file>\r\n2. In opened VIM window, you can use the following function key:\r\n  <F5>    start\/continue debugging\r\n  <F6>    toggel break point\r\n  <F7>    step into\r\n  <F8>    step over\r\n  <S-F7>  step out\r\n  <C-F8>  step until\r\n  <S-F5>  stop debugging\r\n  <F12>   set program arguments\r\n3. A Balloon Value Function is also available.\r\n\r\nRequest\r\n-------\r\n1. Python 2.4\r\n2. \"pyparsing\" (from http:\/\/sourceforge.net\/projects\/pyparsing\/)\r\n3. \"ctypes\" (from http:\/\/sourceforge.net\/projects\/ctypes)\r\n   or \"pywin32\" (from http:\/\/sourceforge.net\/projects\/pywin32\/)\r\n","3":"Add \"How to\" in README:\r\n-------------------------------------\r\nHOW To Use\r\n----------\r\n1. Easy, just like this:\r\n    python vimen.py <your_executable_file>\r\n2. In opened VIM window, you can use the following function key:\r\n  <F5>    start\/continue debugging\r\n  <F6>    toggel break point\r\n  <F7>    step into\r\n  <F8>    step over\r\n  <S-F7>  step out\r\n  <C-F8>  step until\r\n  <S-F5>  stop debugging\r\n  <F12>   set program arguments\r\n3. A Balloon Value Function is also available.\r\n\r\nRequest\r\n-------\r\n1. Python 2.4\r\n2. \"pyparsing\" (from http:\/\/sourceforge.net\/projects\/pyparsing\/)\r\n3. \"ctypes\" (from http:\/\/sourceforge.net\/projects\/ctypes)\r\n   or \"pywin32\" (from http:\/\/sourceforge.net\/projects\/pywin32\/)\r\n","package":"vimen_0_00_0002a.zip","4":"vimen_0_00_0002a.zip","src_id":"4133","5":"4133","creation_date":"1112837047","6":"1112837047"}]},"1253":{"script_id":"1253","0":"1253","script_name":"greens","1":"greens","script_type":"color scheme","2":"color scheme","summary":"A green\/red\/yellow colorscheme","3":"A green\/red\/yellow colorscheme","description":"A green\/red\/yellow colorscheme. It looks OK with light or dark background, 8 or 256 colors terminal or GUI vim. And diff mode colors are easy to discern.\r\n\r\nSet background=light or dark in your .vimrc or from vim cmdline will cause greens.vim to reload colorscheme. If you find vim fails to detect your terminal background, you may use this trick.\r\n\r\nAnd also, greens.vim will not change your terminal's background color, you should set bg color in your terminal settings.\r\n\r\nFollowing are screenshots of urxvt-256color with light(yellow,white) and dark(black) background, editing C++ source code and python source code in diff mode.\r\n\r\nhttp:\/\/elefant.name\/files\/greens-light.png\r\nhttp:\/\/elefant.name\/files\/greens-diff-light.png\r\nhttp:\/\/elefant.name\/files\/greens-diff-white.png\r\nhttp:\/\/elefant.name\/files\/greens-dark.png\r\nhttp:\/\/elefant.name\/files\/greens-diff-dark.png\r\n\r\nNote for bold fonts: If your terminal doesn't display bold fonts well, or you just don't like bold fonts, you may edit greens.vim's function s:Style(style) as below (comment out any style, directly return \"\"):\r\n\r\nfunction! s:Style(style)\r\n\" if &t_Co < 256\r\n    return \"\"\r\n\" else\r\n\"   return \"cterm=\" . a:style . \" gui=\" . a:style\r\n\" endif\r\nendfunction","4":"A green\/red\/yellow colorscheme. It looks OK with light or dark background, 8 or 256 colors terminal or GUI vim. And diff mode colors are easy to discern.\r\n\r\nSet background=light or dark in your .vimrc or from vim cmdline will cause greens.vim to reload colorscheme. If you find vim fails to detect your terminal background, you may use this trick.\r\n\r\nAnd also, greens.vim will not change your terminal's background color, you should set bg color in your terminal settings.\r\n\r\nFollowing are screenshots of urxvt-256color with light(yellow,white) and dark(black) background, editing C++ source code and python source code in diff mode.\r\n\r\nhttp:\/\/elefant.name\/files\/greens-light.png\r\nhttp:\/\/elefant.name\/files\/greens-diff-light.png\r\nhttp:\/\/elefant.name\/files\/greens-diff-white.png\r\nhttp:\/\/elefant.name\/files\/greens-dark.png\r\nhttp:\/\/elefant.name\/files\/greens-diff-dark.png\r\n\r\nNote for bold fonts: If your terminal doesn't display bold fonts well, or you just don't like bold fonts, you may edit greens.vim's function s:Style(style) as below (comment out any style, directly return \"\"):\r\n\r\nfunction! s:Style(style)\r\n\" if &t_Co < 256\r\n    return \"\"\r\n\" else\r\n\"   return \"cterm=\" . a:style . \" gui=\" . a:style\r\n\" endif\r\nendfunction","install_details":"","5":"","first_name":"Yuheng","6":"Yuheng","last_name":"Xie","7":"Xie","releases":[{"0":"1253","vim_version":"6.0","1":"6.0","script_version":"2016.12.07","2":"2016.12.07","version_comment":"trivally changed MatchParen's color","3":"trivally changed MatchParen's color","package":"greens.vim","4":"greens.vim","src_id":"25653","5":"25653","creation_date":"1511250805","6":"1511250805"},{"0":"1253","vim_version":"6.0","1":"6.0","script_version":"2016.12.07","2":"2016.12.07","version_comment":"Make compatible with VIM 6.4","3":"Make compatible with VIM 6.4","package":"greens.vim","4":"greens.vim","src_id":"24785","5":"24785","creation_date":"1481096302","6":"1481096302"}]},"1252":{"script_id":"1252","0":"1252","script_name":"trt.vim","1":"trt.vim","script_type":"syntax","2":"syntax","summary":"Test Real Time scripting language for C testing.","3":"Test Real Time scripting language for C testing.","description":"This is a syntax file for TRT (Rational Test Real Time), a scripting tool for testing programs written in C.","4":"This is a syntax file for TRT (Rational Test Real Time), a scripting tool for testing programs written in C.","install_details":"Put this file in the syntax directory of vim.\r\nAdd the two following lines in your filetype.vim to add detection of .pts, .def, .hts files :\r\n\r\n\" TRT scripts\r\nau BufNewFile,BufRead *.pts,*.hts,*.def setf trt","5":"Put this file in the syntax directory of vim.\r\nAdd the two following lines in your filetype.vim to add detection of .pts, .def, .hts files :\r\n\r\n\" TRT scripts\r\nau BufNewFile,BufRead *.pts,*.hts,*.def setf trt","first_name":"Samuel","6":"Samuel","last_name":"Hangou\u00c3\u00abt","7":"Hangou\u00c3\u00abt","releases":[{"0":"1252","vim_version":"6.0","1":"6.0","script_version":"1.3","2":"1.3","version_comment":"Improve colorisation patterns\r\nRemove match of numbers in comments (very dangerous !)","3":"Improve colorisation patterns\r\nRemove match of numbers in comments (very dangerous !)","package":"trt.vim","4":"trt.vim","src_id":"4589","5":"4589","creation_date":"1126832198","6":"1126832198"},{"0":"1252","vim_version":"6.0","1":"6.0","script_version":"1.2","2":"1.2","version_comment":"Improved the management of syntax typing errors.","3":"Improved the management of syntax typing errors.","package":"trt.vim","4":"trt.vim","src_id":"4272","5":"4272","creation_date":"1115879639","6":"1115879639"},{"0":"1252","vim_version":"6.0","1":"6.0","script_version":"1.1","2":"1.1","version_comment":"Added C syntax inside { } blocks, parens'errors display, correct a little bug by putting keepend in # region matching definition, and complete the list of keywords from TRT user manual.","3":"Added C syntax inside { } blocks, parens'errors display, correct a little bug by putting keepend in # region matching definition, and complete the list of keywords from TRT user manual.","package":"trt.vim","4":"trt.vim","src_id":"4229","5":"4229","creation_date":"1115024504","6":"1115024504"},{"0":"1252","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"trt.vim","4":"trt.vim","src_id":"4120","5":"4120","creation_date":"1112607511","6":"1112607511"}]},"1251":{"script_id":"1251","0":"1251","script_name":"timekeeper","1":"timekeeper","script_type":"utility","2":"utility","summary":"keeps a journal of used time","3":"keeps a journal of used time","description":"Keeps a log of used (wasted) time. The script will trigger every hour whereupon the script will beep and you'll enter a description of what you'll be doing during the next hour.\r\n\r\nKeys:\r\n<Leader>E to insert a new hour entry\r\n<Leader>D to insert a new date entry\r\n\r\nCommands:\r\nAutojournal on | off for setting off and on the autojournalling feature\r\n\r\nThe script will uninstall (remove itself from memory) after the current journal is closed.","4":"Keeps a log of used (wasted) time. The script will trigger every hour whereupon the script will beep and you'll enter a description of what you'll be doing during the next hour.\r\n\r\nKeys:\r\n<Leader>E to insert a new hour entry\r\n<Leader>D to insert a new date entry\r\n\r\nCommands:\r\nAutojournal on | off for setting off and on the autojournalling feature\r\n\r\nThe script will uninstall (remove itself from memory) after the current journal is closed.","install_details":"You will need to edit j.vim to suit your needs (you'll have to change at least the directory that'll keep your journal). You'll' probably not want to put it into the plugins directory, but source it as needed.","5":"You will need to edit j.vim to suit your needs (you'll have to change at least the directory that'll keep your journal). You'll' probably not want to put it into the plugins directory, but source it as needed.","first_name":"Damir","6":"Damir","last_name":"Prdi\u010d","7":"Prdič","releases":[{"0":"1251","vim_version":"6.0","1":"6.0","script_version":"0.54","2":"0.54","version_comment":"bugfixes","3":"bugfixes","package":"j.vim","4":"j.vim","src_id":"4105","5":"4105","creation_date":"1112227597","6":"1112227597"}]},"1250":{"script_id":"1250","0":"1250","script_name":"Teradata syntax","1":"Teradata syntax","script_type":"syntax","2":"syntax","summary":"Teradata SQL, BTEQ Commands (Teradata V2R4,V2R5)","3":"Teradata SQL, BTEQ Commands (Teradata V2R4,V2R5)","description":"Syntax file for Teradata database and BTEQ commands.","4":"Syntax file for Teradata database and BTEQ commands.","install_details":"","5":"","first_name":"Lubomir","6":"Lubomir","last_name":"Husar","7":"Husar","releases":[{"0":"1250","vim_version":"6.0","1":"6.0","script_version":"1.2","2":"1.2","version_comment":"Minor corrections, some keywords added","3":"Minor corrections, some keywords added","package":"teradata.vim","4":"teradata.vim","src_id":"4415","5":"4415","creation_date":"1120806548","6":"1120806548"},{"0":"1250","vim_version":"6.0","1":"6.0","script_version":"1.1","2":"1.1","version_comment":"Initial upload","3":"Initial upload","package":"teradata.vim","4":"teradata.vim","src_id":"4092","5":"4092","creation_date":"1112076787","6":"1112076787"}]},"1249":{"script_id":"1249","0":"1249","script_name":"vc_diff","1":"vc_diff","script_type":"utility","2":"utility","summary":"show difference of source code using","3":"show difference of source code using","description":"Programers often want to check the difference using cvs\/svn diff when they change source codes on cvs\/svn environment.This script do that.\r\nStep to use this script:\r\n1. cd source code directory which is controled by svn or cvs.\r\n2. run vim and execute \":Vcdiff\" to make a patch file.\r\n3. move a cursor to source code name on vim.\r\n4. execute \":call Vcshow\" to check difference between current and original codes.","4":"Programers often want to check the difference using cvs\/svn diff when they change source codes on cvs\/svn environment.This script do that.\r\nStep to use this script:\r\n1. cd source code directory which is controled by svn or cvs.\r\n2. run vim and execute \":Vcdiff\" to make a patch file.\r\n3. move a cursor to source code name on vim.\r\n4. execute \":call Vcshow\" to check difference between current and original codes.","install_details":"copy vc_diff.vim in $VIM\/plugin","5":"copy vc_diff.vim in $VIM\/plugin","first_name":"ichiro","6":"ichiro","last_name":"inoue","7":"inoue","releases":[{"0":"1249","vim_version":"7.0","1":"7.0","script_version":"1.1","2":"1.1","version_comment":"Support svn and change script name.","3":"Support svn and change script name.","package":"vc_diff.vim","4":"vc_diff.vim","src_id":"6038","5":"6038","creation_date":"1154654124","6":"1154654124"},{"0":"1249","vim_version":"6.0","1":"6.0","script_version":"1.00","2":"1.00","version_comment":"Initial upload","3":"Initial upload","package":"cvs_diff.vim","4":"cvs_diff.vim","src_id":"4091","5":"4091","creation_date":"1112065346","6":"1112065346"}]},"1248":{"script_id":"1248","0":"1248","script_name":"cccs.vim","1":"cccs.vim","script_type":"syntax","2":"syntax","summary":"Syntax file for Clearcase config specs","3":"Syntax file for Clearcase config specs","description":"Colours your Clearcase config specs.","4":"Colours your Clearcase config specs.","install_details":"","5":"","first_name":"Jean-Alain","6":"Jean-Alain","last_name":"Geay","7":"Geay","releases":[{"0":"1248","vim_version":"5.7","1":"5.7","script_version":"0.2","2":"0.2","version_comment":"Added a paragraph on filetype detection, added syntax highlighting for functions created_since and created_by, plus a few minor adjustments","3":"Added a paragraph on filetype detection, added syntax highlighting for functions created_since and created_by, plus a few minor adjustments","package":"cccs.vim","4":"cccs.vim","src_id":"4239","5":"4239","creation_date":"1115175594","6":"1115175594"},{"0":"1248","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"cccs.vim","4":"cccs.vim","src_id":"4073","5":"4073","creation_date":"1111746460","6":"1111746460"}]},"1247":{"script_id":"1247","0":"1247","script_name":"swig","1":"swig","script_type":"syntax","2":"syntax","summary":"SWIG syntax","3":"SWIG syntax","description":"The standard Vim cannot recognise SWIG (http:\/\/www.swig.org) description file.\r\nI write some simple scripts for highlinghting SWIG description file.\r\n\r\nAny advice could be sent to mrkissinger@gmail.com","4":"The standard Vim cannot recognise SWIG (http:\/\/www.swig.org) description file.\r\nI write some simple scripts for highlinghting SWIG description file.\r\n\r\nAny advice could be sent to mrkissinger@gmail.com","install_details":"cd ~\/.vim\r\ntar xfz swig.tar.gz","5":"cd ~\/.vim\r\ntar xfz swig.tar.gz","first_name":"Beau","6":"Beau","last_name":"Kissinger","7":"Kissinger","releases":[{"0":"1247","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"swig.tar.gz","4":"swig.tar.gz","src_id":"4065","5":"4065","creation_date":"1111655477","6":"1111655477"}]},"1246":{"script_id":"1246","0":"1246","script_name":"Omap.vim","1":"Omap.vim","script_type":"utility","2":"utility","summary":"create user-defined operator mappings","3":"create user-defined operator mappings","description":"A slightly more maintained version of this script is here: https:\/\/github.com\/bencollerson\/Omap.vim\r\n\r\nOmap.vim provides the :Omap command, among others, which creates user-defined operator commands (like y c d and g?, see :help operator for more info).\r\n\r\nTo demonstrate, this command can be used to add functionality to other scripts. You can use Omap.vim in conjuction with EnhancedCommentify.vim (vimscript #23) to create a commenting operator. Assuming both EnhancedCommentify.vim and Omap.vim are installed in your vim plugin directory, add the following commands to your .vimrc file:\r\n\r\n    let g:EnhCommentifyUserBindings = 'yes'\r\n    runtime plugin\/Omap.vim\r\n    Omap <silent> <unique> <leader>c <Plug>Commentj\r\n    Omap <silent> <unique> <leader>u <Plug>DeCommentj\r\n\r\nThis will stop the default mappings being defined by EnhancedCommentify.vim and in their place create comment (\\c) and uncomment (\\u) operators.\r\n\r\nThis allows commenting to be carried out over areas defined by vim motions and text objects. For example: \r\n\r\n    \\cc  --  comments a line\r\n    .  --  comments the next line (repeats last command)\r\n    3\\cc  --  comments three lines\r\n    \\uu  --  uncomments a line\r\n    \\c4j  --  comments the current line and the four following lines\r\n    \\caB  --  comments a block of code\r\n\r\nNote that the dot (.) command (see :help .) works to repeat Omaps even though they are mappings. A command, :DotCommandSet, is defined by Omap.vim which allows other mappings to similarly be repeated using the dot command. \r\n\r\nFor more detailed help see the help documentation in the archive below.\r\n","4":"A slightly more maintained version of this script is here: https:\/\/github.com\/bencollerson\/Omap.vim\r\n\r\nOmap.vim provides the :Omap command, among others, which creates user-defined operator commands (like y c d and g?, see :help operator for more info).\r\n\r\nTo demonstrate, this command can be used to add functionality to other scripts. You can use Omap.vim in conjuction with EnhancedCommentify.vim (vimscript #23) to create a commenting operator. Assuming both EnhancedCommentify.vim and Omap.vim are installed in your vim plugin directory, add the following commands to your .vimrc file:\r\n\r\n    let g:EnhCommentifyUserBindings = 'yes'\r\n    runtime plugin\/Omap.vim\r\n    Omap <silent> <unique> <leader>c <Plug>Commentj\r\n    Omap <silent> <unique> <leader>u <Plug>DeCommentj\r\n\r\nThis will stop the default mappings being defined by EnhancedCommentify.vim and in their place create comment (\\c) and uncomment (\\u) operators.\r\n\r\nThis allows commenting to be carried out over areas defined by vim motions and text objects. For example: \r\n\r\n    \\cc  --  comments a line\r\n    .  --  comments the next line (repeats last command)\r\n    3\\cc  --  comments three lines\r\n    \\uu  --  uncomments a line\r\n    \\c4j  --  comments the current line and the four following lines\r\n    \\caB  --  comments a block of code\r\n\r\nNote that the dot (.) command (see :help .) works to repeat Omaps even though they are mappings. A command, :DotCommandSet, is defined by Omap.vim which allows other mappings to similarly be repeated using the dot command. \r\n\r\nFor more detailed help see the help documentation in the archive below.\r\n","install_details":"To install, unzip Omap.zip placing Omap.vim in your vim plugins directory and Omap.txt in your vim doc directory. \r\n\r\nRun :helptags on your doc directory to install documentation into the vim help system.\r\n","5":"To install, unzip Omap.zip placing Omap.vim in your vim plugins directory and Omap.txt in your vim doc directory. \r\n\r\nRun :helptags on your doc directory to install documentation into the vim help system.\r\n","first_name":"Ben","6":"Ben","last_name":"Collerson","7":"Collerson","releases":[{"0":"1246","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"Omap.zip","4":"Omap.zip","src_id":"4061","5":"4061","creation_date":"1111533413","6":"1111533413"}]},"1245":{"script_id":"1245","0":"1245","script_name":"cvsmenu.vim (updated)","1":"cvsmenu.vim (updated)","script_type":"utility","2":"utility","summary":"CVS(NT) integration plugin (Script #58 continued since 2005)","3":"CVS(NT) integration plugin (Script #58 continued since 2005)","description":"Supports most cvs commands and adds some extended functions. It also works with CVSNT quite well and has some support for multiple encodings. Part of the top-level menus are as follows (screen shot: http:\/\/wyw.dcweb.cn\/download.asp?path=vim&file=vim_session.png):\r\n\r\n- Info\r\n- Setting (switches and update)\r\n- Keyword\r\n- Directory (directory operations; screen shot: http:\/\/wyw.dcweb.cn\/download.asp?path=vim&file=cvs_localstatus.png)\r\n- Extra (operations on a specific revision, etc.)\r\n- Diff (in the split-window style of Vim; screen shot: http:\/\/wyw.dcweb.cn\/download.asp?path=vim&file=cvs_diff.png)\r\n- Annotate (screen shot: http:\/\/wyw.dcweb.cn\/download.asp?path=vim&file=cvs_annotate.png)\r\n- History\r\n- Log (screen shot: http:\/\/wyw.dcweb.cn\/download.asp?path=vim&file=cvs_log.png)\r\n- Status\r\n- Local status (offline: displays status and version info)\r\n- Check out\r\n- Query update (like WinCVS\/gCVS)\r\n- Update (conflicts will be highlighted)\r\n- Add\r\n- Commit\r\n\r\nThe output can be sorted and is often clickable: it is easy to open conflicting files, etc. It works on single files as well as on whole directories, when called from fileexplorer. It also includes highlighting \/ mappings to navigate through cvs output or show conflicts.\r\n\r\nThe menu is displayed in GUI versions of Vim. However, it is useful even in text-only Vim. --- You may choose to use `wildmenu', or you can use key sequences similar to the hot keys in menu. E.g. `alt-c, i' is used to commit with the GUI menu; so `,ci' could be used in text-mode Vim to commit. The leader key, currently `,', can be easily modified in the script.\r\n\r\nThis is the re-release of Mr Thorsten Maerz's original script (vimscript #58), which was last updated in 2002. It now includes many bug fixes and enhancements. The latest revision of the cvsmenu script can also be found in the SourceForge CVS:\r\n\r\n:pserver:anonymous@ezytools.cvs.sourceforge.net:\/cvsroot\/ezytools\/VimTools\/cvsmenu.vim\r\n\r\nCvsMenu is able to update itself using this anonymous CVS. Find the menu items under `CVS > Settings > Install'.","4":"Supports most cvs commands and adds some extended functions. It also works with CVSNT quite well and has some support for multiple encodings. Part of the top-level menus are as follows (screen shot: http:\/\/wyw.dcweb.cn\/download.asp?path=vim&file=vim_session.png):\r\n\r\n- Info\r\n- Setting (switches and update)\r\n- Keyword\r\n- Directory (directory operations; screen shot: http:\/\/wyw.dcweb.cn\/download.asp?path=vim&file=cvs_localstatus.png)\r\n- Extra (operations on a specific revision, etc.)\r\n- Diff (in the split-window style of Vim; screen shot: http:\/\/wyw.dcweb.cn\/download.asp?path=vim&file=cvs_diff.png)\r\n- Annotate (screen shot: http:\/\/wyw.dcweb.cn\/download.asp?path=vim&file=cvs_annotate.png)\r\n- History\r\n- Log (screen shot: http:\/\/wyw.dcweb.cn\/download.asp?path=vim&file=cvs_log.png)\r\n- Status\r\n- Local status (offline: displays status and version info)\r\n- Check out\r\n- Query update (like WinCVS\/gCVS)\r\n- Update (conflicts will be highlighted)\r\n- Add\r\n- Commit\r\n\r\nThe output can be sorted and is often clickable: it is easy to open conflicting files, etc. It works on single files as well as on whole directories, when called from fileexplorer. It also includes highlighting \/ mappings to navigate through cvs output or show conflicts.\r\n\r\nThe menu is displayed in GUI versions of Vim. However, it is useful even in text-only Vim. --- You may choose to use `wildmenu', or you can use key sequences similar to the hot keys in menu. E.g. `alt-c, i' is used to commit with the GUI menu; so `,ci' could be used in text-mode Vim to commit. The leader key, currently `,', can be easily modified in the script.\r\n\r\nThis is the re-release of Mr Thorsten Maerz's original script (vimscript #58), which was last updated in 2002. It now includes many bug fixes and enhancements. The latest revision of the cvsmenu script can also be found in the SourceForge CVS:\r\n\r\n:pserver:anonymous@ezytools.cvs.sourceforge.net:\/cvsroot\/ezytools\/VimTools\/cvsmenu.vim\r\n\r\nCvsMenu is able to update itself using this anonymous CVS. Find the menu items under `CVS > Settings > Install'.","install_details":"Copy to the Vim plugin directory: generally ~\/.vim\/plugin in UNIXs, and $VIM\\vimfiles\\plugin (or $HOME\\vimfiles\\plugin) in Windows.\r\n\r\nChoose `CVS > Settings > Install > Install updates' in the menu, or the shortcut `,cgii', to checkout and install the latest script and documentation.","5":"Copy to the Vim plugin directory: generally ~\/.vim\/plugin in UNIXs, and $VIM\\vimfiles\\plugin (or $HOME\\vimfiles\\plugin) in Windows.\r\n\r\nChoose `CVS > Settings > Install > Install updates' in the menu, or the shortcut `,cgii', to checkout and install the latest script and documentation.","first_name":"Yongwei","6":"Yongwei","last_name":"Wu","7":"Wu","releases":[{"0":"1245","vim_version":"6.0","1":"6.0","script_version":"1.150","2":"1.150","version_comment":"Fix the issue that \"CVS > Revert changes\" discards tag\/branch information;\r\nFix some issues related to fileencoding.","3":"Fix the issue that \"CVS > Revert changes\" discards tag\/branch information;\r\nFix some issues related to fileencoding.","package":"cvsmenu.vim","4":"cvsmenu.vim","src_id":"11423","5":"11423","creation_date":"1253763533","6":"1253763533"},{"0":"1245","vim_version":"6.0","1":"6.0","script_version":"1.147","2":"1.147","version_comment":"Fix the issue that the global fileencoding can be accidentally changed by \"let &fileencoding=\"; fix the problem that the log message is not converted to the CVScmdencoding.","3":"Fix the issue that the global fileencoding can be accidentally changed by \"let &fileencoding=\"; fix the problem that the log message is not converted to the CVScmdencoding.","package":"cvsmenu.vim","4":"cvsmenu.vim","src_id":"8868","5":"8868","creation_date":"1214707910","6":"1214707910"},{"0":"1245","vim_version":"6.0","1":"6.0","script_version":"1.145","2":"1.145","version_comment":"Fix the bug that the local status is not automatically refreshed when committing a file not in the current directory.","3":"Fix the bug that the local status is not automatically refreshed when committing a file not in the current directory.","package":"cvsmenu.vim","4":"cvsmenu.vim","src_id":"8101","5":"8101","creation_date":"1198968802","6":"1198968802"},{"0":"1245","vim_version":"6.0","1":"6.0","script_version":"1.144","2":"1.144","version_comment":"Fix the bug that shortcut keys cannot be created in Unix when the path of cvsmenu.vim contains spaces.\r\n","3":"Fix the bug that shortcut keys cannot be created in Unix when the path of cvsmenu.vim contains spaces.\r\n","package":"cvsmenu.vim","4":"cvsmenu.vim","src_id":"7839","5":"7839","creation_date":"1193438998","6":"1193438998"},{"0":"1245","vim_version":"6.0","1":"6.0","script_version":"1.143","2":"1.143","version_comment":"Fix the bug that the file path cannot contain spaces (in Unix and Cygwin).","3":"Fix the bug that the file path cannot contain spaces (in Unix and Cygwin).","package":"cvsmenu.vim","4":"cvsmenu.vim","src_id":"7737","5":"7737","creation_date":"1191232729","6":"1191232729"},{"0":"1245","vim_version":"6.0","1":"6.0","script_version":"1.142","2":"1.142","version_comment":"Shorten `CVScvsoutputencoding' to `CVScmdencoding';\r\nAdd a new control variable g:CVSfileencoding to ensure the result of CVS-Diff and CVS-Annotate is correct;\r\nSet the appropriate fileencoding in CVSDoCommand.","3":"Shorten `CVScvsoutputencoding' to `CVScmdencoding';\r\nAdd a new control variable g:CVSfileencoding to ensure the result of CVS-Diff and CVS-Annotate is correct;\r\nSet the appropriate fileencoding in CVSDoCommand.","package":"cvsmenu.vim","4":"cvsmenu.vim","src_id":"7088","5":"7088","creation_date":"1178697960","6":"1178697960"},{"0":"1245","vim_version":"6.0","1":"6.0","script_version":"1.140","2":"1.140","version_comment":"Re-enable password piping on Windows (tested to work with CVSNT 2.5.02 Build 2115) to make update cvsmenu.vim smoother; Change the name pattern of temporary log message file to make CVSeasylogmessage work with different versions of CVS (tested with more than 4 different CVS clients); Make some minor bug fixes.","3":"Re-enable password piping on Windows (tested to work with CVSNT 2.5.02 Build 2115) to make update cvsmenu.vim smoother; Change the name pattern of temporary log message file to make CVSeasylogmessage work with different versions of CVS (tested with more than 4 different CVS clients); Make some minor bug fixes.","package":"cvsmenu.vim","4":"cvsmenu.vim","src_id":"6316","5":"6316","creation_date":"1161485259","6":"1161485259"},{"0":"1245","vim_version":"6.0","1":"6.0","script_version":"1.136","2":"1.136","version_comment":"When vimming a CVS log message, ensure there is an empty line at the beginning, make editing start in insert mode, and make a normal-mode ENTER finish editing (can be disabled by put `let g:CVSeasylogmessage=0' in (.|_)vimrc).","3":"When vimming a CVS log message, ensure there is an empty line at the beginning, make editing start in insert mode, and make a normal-mode ENTER finish editing (can be disabled by put `let g:CVSeasylogmessage=0' in (.|_)vimrc).","package":"cvsmenu.vim","4":"cvsmenu.vim","src_id":"6311","5":"6311","creation_date":"1161370430","6":"1161370430"},{"0":"1245","vim_version":"6.0","1":"6.0","script_version":"1.135","2":"1.135","version_comment":"Display a message and cease to CVS diff if the file is newly added; allow using `q' to close the CVS history window.","3":"Display a message and cease to CVS diff if the file is newly added; allow using `q' to close the CVS history window.","package":"cvsmenu.vim","4":"cvsmenu.vim","src_id":"6304","5":"6304","creation_date":"1161293016","6":"1161293016"},{"0":"1245","vim_version":"6.0","1":"6.0","script_version":"1.133","2":"1.133","version_comment":"Use the corresponding version instead of the most recent version in the repository to Diff, as the command line `cvs diff ...' does.","3":"Use the corresponding version instead of the most recent version in the repository to Diff, as the command line `cvs diff ...' does.","package":"cvsmenu.vim","4":"cvsmenu.vim","src_id":"6286","5":"6286","creation_date":"1160979006","6":"1160979006"},{"0":"1245","vim_version":"6.0","1":"6.0","script_version":"1.132","2":"1.132","version_comment":"Fix the display problem of `Directory > Local status'; clean up the code a little.","3":"Fix the display problem of `Directory > Local status'; clean up the code a little.","package":"cvsmenu.vim","4":"cvsmenu.vim","src_id":"6280","5":"6280","creation_date":"1160783689","6":"1160783689"},{"0":"1245","vim_version":"6.0","1":"6.0","script_version":"1.127","2":"1.127","version_comment":"Fix the bug that `Checkout to' does not work.","3":"Fix the bug that `Checkout to' does not work.","package":"cvsmenu.vim","4":"cvsmenu.vim","src_id":"6264","5":"6264","creation_date":"1160457662","6":"1160457662"},{"0":"1245","vim_version":"6.0","1":"6.0","script_version":"1.126","2":"1.126","version_comment":"Allow non-ASCII filename to be used when encoding=utf-8.","3":"Allow non-ASCII filename to be used when encoding=utf-8.","package":"cvsmenu.vim","4":"cvsmenu.vim","src_id":"6159","5":"6159","creation_date":"1157961198","6":"1157961198"},{"0":"1245","vim_version":"6.0","1":"6.0","script_version":"1.125","2":"1.125","version_comment":"Truncate the Vim title after the file name so that the file name is always visible when the directory name is long.","3":"Truncate the Vim title after the file name so that the file name is always visible when the directory name is long.","package":"cvsmenu.vim","4":"cvsmenu.vim","src_id":"6134","5":"6134","creation_date":"1157169491","6":"1157169491"},{"0":"1245","vim_version":"6.0","1":"6.0","script_version":"1.124","2":"1.124","version_comment":"Map `q' to quickly close the buffer opened by cvs annotate and cvs log.","3":"Map `q' to quickly close the buffer opened by cvs annotate and cvs log.","package":"cvsmenu.vim","4":"cvsmenu.vim","src_id":"6082","5":"6082","creation_date":"1156040312","6":"1156040312"},{"0":"1245","vim_version":"6.0","1":"6.0","script_version":"1.123","2":"1.123","version_comment":"Update broken links and make self-update work again.","3":"Update broken links and make self-update work again.","package":"cvsmenu.vim","4":"cvsmenu.vim","src_id":"5734","5":"5734","creation_date":"1148199546","6":"1148199546"},{"0":"1245","vim_version":"6.0","1":"6.0","script_version":"1.122","2":"1.122","version_comment":"Update CVS info due to the SourceForge site change to make updating itself continue to work.","3":"Update CVS info due to the SourceForge site change to make updating itself continue to work.","package":"cvsmenu.vim","4":"cvsmenu.vim","src_id":"5687","5":"5687","creation_date":"1147493345","6":"1147493345"},{"0":"1245","vim_version":"6.0","1":"6.0","script_version":"1.121","2":"1.121","version_comment":"- Use extracted cvs command (w\/o `-q' etc.) to match with CVSdontconvertfor; - Ensure correct message escaping on Windows when shell=cmd.exe (regardless of shellxquote); - Documentation is updated to reflect my changes: be sure to use `CVS - Settings - Install - Install updates' (or `Download updates' followed by `Install buffer as help' on the help file buffer) to get it.","3":"- Use extracted cvs command (w\/o `-q' etc.) to match with CVSdontconvertfor; - Ensure correct message escaping on Windows when shell=cmd.exe (regardless of shellxquote); - Documentation is updated to reflect my changes: be sure to use `CVS - Settings - Install - Install updates' (or `Download updates' followed by `Install buffer as help' on the help file buffer) to get it.","package":"cvsmenu.vim","4":"cvsmenu.vim","src_id":"4770","5":"4770","creation_date":"1132166400","6":"1132166400"},{"0":"1245","vim_version":"6.0","1":"6.0","script_version":"1.118","2":"1.118","version_comment":"- Deal with \"`\" correctly under Unix;\r\n- Make no-reload-prompt trick work when the committed file is not in the current directory.","3":"- Deal with \"`\" correctly under Unix;\r\n- Make no-reload-prompt trick work when the committed file is not in the current directory.","package":"cvsmenu.vim","4":"cvsmenu.vim","src_id":"4725","5":"4725","creation_date":"1131508891","6":"1131508891"},{"0":"1245","vim_version":"6.0","1":"6.0","script_version":"1.116","2":"1.116","version_comment":"- Do not allow to commit if the current file has not a name;\r\n- Fix a bug when executing `:w file' on an unsaved named buffer.","3":"- Do not allow to commit if the current file has not a name;\r\n- Fix a bug when executing `:w file' on an unsaved named buffer.","package":"cvsmenu.vim","4":"cvsmenu.vim","src_id":"4713","5":"4713","creation_date":"1130823220","6":"1130823220"},{"0":"1245","vim_version":"6.0","1":"6.0","script_version":"1.114","2":"1.114","version_comment":"- Work around a problem that unedit of CVSNT may prompt to revert changes;\r\n- Allow the ouput encoding of cvs be different from the Vim encoding (e.g., to make Chinese in annotate and the error message of CVSNT display correctly, one may now use `let CVScvsoutputencoding=\"gbk\"' in .vimrc).","3":"- Work around a problem that unedit of CVSNT may prompt to revert changes;\r\n- Allow the ouput encoding of cvs be different from the Vim encoding (e.g., to make Chinese in annotate and the error message of CVSNT display correctly, one may now use `let CVScvsoutputencoding=\"gbk\"' in .vimrc).","package":"cvsmenu.vim","4":"cvsmenu.vim","src_id":"4673","5":"4673","creation_date":"1129268592","6":"1129268592"},{"0":"1245","vim_version":"6.0","1":"6.0","script_version":"1.112","2":"1.112","version_comment":"- Rename CVSaddspaceafterannotate to CVSspacesinannotate;\r\n- Display two missing parameters in CVS - Info;\r\n- Avoid the reload prompt after commit;\r\n- Do not allow to commit if the current buffer is modified.","3":"- Rename CVSaddspaceafterannotate to CVSspacesinannotate;\r\n- Display two missing parameters in CVS - Info;\r\n- Avoid the reload prompt after commit;\r\n- Do not allow to commit if the current buffer is modified.","package":"cvsmenu.vim","4":"cvsmenu.vim","src_id":"4612","5":"4612","creation_date":"1127420578","6":"1127420578"},{"0":"1245","vim_version":"6.0","1":"6.0","script_version":"1.109","2":"1.109","version_comment":"Fix problems with CVS annotation highlighting.","3":"Fix problems with CVS annotation highlighting.","package":"cvsmenu.vim","4":"cvsmenu.vim","src_id":"4414","5":"4414","creation_date":"1120709968","6":"1120709968"},{"0":"1245","vim_version":"6.0","1":"6.0","script_version":"1.107","2":"1.107","version_comment":"- Allow space adjustment of output of \"CVS - Annotate\"  (assign a positive value to g:CVSaddspaceafterannotate) so that files that use TABs can align better.\r\n- Output of \"CVS - Annotate\" is now highlighted.","3":"- Allow space adjustment of output of \"CVS - Annotate\"  (assign a positive value to g:CVSaddspaceafterannotate) so that files that use TABs can align better.\r\n- Output of \"CVS - Annotate\" is now highlighted.","package":"cvsmenu.vim","4":"cvsmenu.vim","src_id":"4351","5":"4351","creation_date":"1118211669","6":"1118211669"},{"0":"1245","vim_version":"6.0","1":"6.0","script_version":"1.104","2":"1.104","version_comment":"- Do not remap keys for new buffers output by cvs annotate, history, and log.\r\n- Correct the help message for output buffer.","3":"- Do not remap keys for new buffers output by cvs annotate, history, and log.\r\n- Correct the help message for output buffer.","package":"cvsmenu.vim","4":"cvsmenu.vim","src_id":"4207","5":"4207","creation_date":"1114659729","6":"1114659729"},{"0":"1245","vim_version":"6.0","1":"6.0","script_version":"1.102","2":"1.102","version_comment":"Make menu commands like \"CVS - Directory - Update\" work in insert mode.","3":"Make menu commands like \"CVS - Directory - Update\" work in insert mode.","package":"cvsmenu.vim","4":"cvsmenu.vim","src_id":"4184","5":"4184","creation_date":"1113949253","6":"1113949253"},{"0":"1245","vim_version":"6.0","1":"6.0","script_version":"1.100","2":"1.100","version_comment":"Do not reload-after-commit after a directory commit (to avoid an error).\r\n\r\nFix CVSInstallAsPlugin and CVSInstallAsHelp so that the plugin and its help are installed to where the script is currently installed.","3":"Do not reload-after-commit after a directory commit (to avoid an error).\r\n\r\nFix CVSInstallAsPlugin and CVSInstallAsHelp so that the plugin and its help are installed to where the script is currently installed.","package":"cvsmenu.vim","4":"cvsmenu.vim","src_id":"4175","5":"4175","creation_date":"1113712706","6":"1113712706"},{"0":"1245","vim_version":"6.0","1":"6.0","script_version":"1.97","2":"1.97","version_comment":"Fix the broken key mapping. Now it is possible to use key sequences similar to the menu hot keys. E.g. `alt-c, i' is used to commit when the GUI menu exists; so `,ci' could be used in text-mode Vim to commit.","3":"Fix the broken key mapping. Now it is possible to use key sequences similar to the menu hot keys. E.g. `alt-c, i' is used to commit when the GUI menu exists; so `,ci' could be used in text-mode Vim to commit.","package":"cvsmenu.vim","4":"cvsmenu.vim","src_id":"4121","5":"4121","creation_date":"1112645615","6":"1112645615"},{"0":"1245","vim_version":"6.0","1":"6.0","script_version":"1.96","2":"1.96","version_comment":"Make sure the special characters \"&\", \"<\", \">\", \"|\", and \"^\" are handled correctly if shell is cmd.exe and shellxquote is \\\" (there will be miscellaneous gotchas if the shell is command.com or shellxquote is empty).\r\n\r\nChange the prefixing spaces in menu items to appending spaces to make wildmenu users happier (when wim includes longest).","3":"Make sure the special characters \"&\", \"<\", \">\", \"|\", and \"^\" are handled correctly if shell is cmd.exe and shellxquote is \\\" (there will be miscellaneous gotchas if the shell is command.com or shellxquote is empty).\r\n\r\nChange the prefixing spaces in menu items to appending spaces to make wildmenu users happier (when wim includes longest).","package":"cvsmenu.vim","4":"cvsmenu.vim","src_id":"4089","5":"4089","creation_date":"1112035033","6":"1112035033"},{"0":"1245","vim_version":"6.0","1":"6.0","script_version":"1.94","2":"1.94","version_comment":"Initial upload","3":"Initial upload","package":"cvsmenu.vim","4":"cvsmenu.vim","src_id":"4058","5":"4058","creation_date":"1111518678","6":"1111518678"}]},"1244":{"script_id":"1244","0":"1244","script_name":"Embedded Vim Preprocessor","1":"Embedded Vim Preprocessor","script_type":"utility","2":"utility","summary":"Embedded Vim Preprocessor","3":"Embedded Vim Preprocessor","description":"This is a basic Preprocessor Engine \r\n\r\n   It contains a script for processing Embedded Vim code in any file by using the following statements:\r\n\r\n\r\n*Now: Includes statmens were added, it supports nested including, and each included file will be proccesed too.\r\n\r\n<?vim:include=\"file_source.html\">\r\n\r\n...any text...\r\n<?vim>\r\n   ...\r\n  {pure vim statements}\r\n   ...\r\n<\/?vim>\r\n...any text...\r\n\r\n\r\n\r\nor\r\n...any text...<?vim={a vim expresion}>...any text...\r\n_________________________________________________________________________\r\n\r\n\r\n****WRITE THE FOLLOWING FILE:****\r\n---------File.txt--------------------\r\n<?vim:include=\"headerfile.txt\">\r\nYou can use it on any file\r\n<?vim>\r\nlet i=0\r\nwhile i<11\r\n<\/?vim>\r\nThe i value is: <?vim=\"actually \".i >\r\n<?vim>let i=i+1 | endw<\/?vim>\r\n---------------------------------------\r\n\r\n*****TYPE ':%PPEV'****\r\n\r\n\r\n****AND YOU WILL GET THE FOLLOWING FILE****\r\n-----------File2.txt---------------------\r\nHeader of the included file\r\nYou can use it on any file\r\nThe i value is: actually 0\r\nThe i value is: actually 1\r\nThe i value is: actually 2\r\nThe i value is: actually 3\r\nThe i value is: actually 4\r\nThe i value is: actually 5\r\nThe i value is: actually 6\r\nThe i value is: actually 7\r\nThe i value is: actually 8\r\nThe i value is: actually 9\r\nThe i value is: actually 10\r\n--------------------------------------\r\n_________________________________________________________________________\r\nCurrent Features:\r\n  *You can use  embedded  Vim code with any file, then\r\n  *using ':%PPEV' command it generates another file(any name) with the Embedded Vim Code processed\r\n  *<?vim> <\/?vim> statements\r\n  *<?vim={expr}> statement\r\n  *<?vim:include=\"{file}\"> statement\r\nFuture versions:\r\n  *ifdef\r\n  *ifndef\r\n  *define\r\n\r\n ","4":"This is a basic Preprocessor Engine \r\n\r\n   It contains a script for processing Embedded Vim code in any file by using the following statements:\r\n\r\n\r\n*Now: Includes statmens were added, it supports nested including, and each included file will be proccesed too.\r\n\r\n<?vim:include=\"file_source.html\">\r\n\r\n...any text...\r\n<?vim>\r\n   ...\r\n  {pure vim statements}\r\n   ...\r\n<\/?vim>\r\n...any text...\r\n\r\n\r\n\r\nor\r\n...any text...<?vim={a vim expresion}>...any text...\r\n_________________________________________________________________________\r\n\r\n\r\n****WRITE THE FOLLOWING FILE:****\r\n---------File.txt--------------------\r\n<?vim:include=\"headerfile.txt\">\r\nYou can use it on any file\r\n<?vim>\r\nlet i=0\r\nwhile i<11\r\n<\/?vim>\r\nThe i value is: <?vim=\"actually \".i >\r\n<?vim>let i=i+1 | endw<\/?vim>\r\n---------------------------------------\r\n\r\n*****TYPE ':%PPEV'****\r\n\r\n\r\n****AND YOU WILL GET THE FOLLOWING FILE****\r\n-----------File2.txt---------------------\r\nHeader of the included file\r\nYou can use it on any file\r\nThe i value is: actually 0\r\nThe i value is: actually 1\r\nThe i value is: actually 2\r\nThe i value is: actually 3\r\nThe i value is: actually 4\r\nThe i value is: actually 5\r\nThe i value is: actually 6\r\nThe i value is: actually 7\r\nThe i value is: actually 8\r\nThe i value is: actually 9\r\nThe i value is: actually 10\r\n--------------------------------------\r\n_________________________________________________________________________\r\nCurrent Features:\r\n  *You can use  embedded  Vim code with any file, then\r\n  *using ':%PPEV' command it generates another file(any name) with the Embedded Vim Code processed\r\n  *<?vim> <\/?vim> statements\r\n  *<?vim={expr}> statement\r\n  *<?vim:include=\"{file}\"> statement\r\nFuture versions:\r\n  *ifdef\r\n  *ifndef\r\n  *define\r\n\r\n ","install_details":"Just source the evcp.vim file.\r\nIt contains install instructions, step by step tutorial, and example files generated with EVP","5":"Just source the evcp.vim file.\r\nIt contains install instructions, step by step tutorial, and example files generated with EVP","first_name":"Jess","6":"Jess","last_name":"me","7":"me","releases":[{"0":"1244","vim_version":"6.0","1":"6.0","script_version":"1.0.1","2":"1.0.1","version_comment":"Bug fixed: Now you don't need to escape quotes in normal text\r\nBug fixed: Empty processing lines, and other overwrite errors were fixed.\r\nNew Features: <?vim:include=\"\"> statement, unix and windows support","3":"Bug fixed: Now you don't need to escape quotes in normal text\r\nBug fixed: Empty processing lines, and other overwrite errors were fixed.\r\nNew Features: <?vim:include=\"\"> statement, unix and windows support","package":"evcp1.0.1.tar.gz","4":"evcp1.0.1.tar.gz","src_id":"4077","5":"4077","creation_date":"1111796491","6":"1111796491"},{"0":"1244","vim_version":"6.0","1":"6.0","script_version":"v1.0","2":"v1.0","version_comment":"Initial upload","3":"Initial upload","package":"evp-1.0.tar.gz","4":"evp-1.0.tar.gz","src_id":"4053","5":"4053","creation_date":"1111422090","6":"1111422090"}]},"1243":{"script_id":"1243","0":"1243","script_name":"desert256.vim","1":"desert256.vim","script_type":"color scheme","2":"color scheme","summary":"A slightly-modified desert theme, for 88- and 256-color xterms.","3":"A slightly-modified desert theme, for 88- and 256-color xterms.","description":"These are the colors of the \"desert\" theme by Hans Fugal with a few small modifications (namely that I lowered the intensity of the normal white and made the normal and nontext backgrounds black), modified to work with 88- and 256-color xterms.\r\n\r\nThe original \"desert\" theme is available as part of the vim distribution or at http:\/\/hans.fugal.net\/vim\/colors\/.\r\n\r\nThe real feature of this color scheme, with a wink to the \"inkpot\" theme, is the programmatic approximation of the gui colors to the palettes of 88- and 256- color xterms.  The functions that do this (folded away, for readability) are calibrated to the colors used for Thomas E. Dickey's xterm (version 200), which is available at http:\/\/dickey.his.com\/xterm\/xterm.html.\r\n\r\nI struggled with trying to parse the rgb.txt file to avoid the necessity of converting color names to #rrggbb form, but decided it was just not worth the effort.  Maybe someone seeing this may decide otherwise...","4":"These are the colors of the \"desert\" theme by Hans Fugal with a few small modifications (namely that I lowered the intensity of the normal white and made the normal and nontext backgrounds black), modified to work with 88- and 256-color xterms.\r\n\r\nThe original \"desert\" theme is available as part of the vim distribution or at http:\/\/hans.fugal.net\/vim\/colors\/.\r\n\r\nThe real feature of this color scheme, with a wink to the \"inkpot\" theme, is the programmatic approximation of the gui colors to the palettes of 88- and 256- color xterms.  The functions that do this (folded away, for readability) are calibrated to the colors used for Thomas E. Dickey's xterm (version 200), which is available at http:\/\/dickey.his.com\/xterm\/xterm.html.\r\n\r\nI struggled with trying to parse the rgb.txt file to avoid the necessity of converting color names to #rrggbb form, but decided it was just not worth the effort.  Maybe someone seeing this may decide otherwise...","install_details":"Copy this file into ~\/.vim\/colors (or $VIM\/vimfiles\/colors in Windows).  Start it from within vim using :colorscheme desert256.","5":"Copy this file into ~\/.vim\/colors (or $VIM\/vimfiles\/colors in Windows).  Start it from within vim using :colorscheme desert256.","first_name":"Henry","6":"Henry","last_name":"So, Jr.","7":"So, Jr.","releases":[{"0":"1243","vim_version":"6.0","1":"6.0","script_version":"1.0.1","2":"1.0.1","version_comment":"Minor attribute tweaks to keep the appearance of things the same on more systems. Fixed the reverse video issue with :help.","3":"Minor attribute tweaks to keep the appearance of things the same on more systems. Fixed the reverse video issue with :help.","package":"desert256.vim","4":"desert256.vim","src_id":"4055","5":"4055","creation_date":"1111431665","6":"1111431665"},{"0":"1243","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"desert256.vim","4":"desert256.vim","src_id":"4052","5":"4052","creation_date":"1111411557","6":"1111411557"}]},"1242":{"script_id":"1242","0":"1242","script_name":"Markdown syntax","1":"Markdown syntax","script_type":"syntax","2":"syntax","summary":"Syntax file for Markdown text-to-HTML language","3":"Syntax file for Markdown text-to-HTML language","description":"A syntax file for the Markdown text-to-HTML tool http:\/\/daringfireball.net\/projects\/markdown\/\r\n\r\nThe latest version and installation details are available on Github at http:\/\/github.com\/plasticboy\/vim-markdown\/\r\nPlease submit patches there.","4":"A syntax file for the Markdown text-to-HTML tool http:\/\/daringfireball.net\/projects\/markdown\/\r\n\r\nThe latest version and installation details are available on Github at http:\/\/github.com\/plasticboy\/vim-markdown\/\r\nPlease submit patches there.","install_details":"","5":"","first_name":"Ben","6":"Ben","last_name":"Williams","7":"Williams","releases":[{"0":"1242","vim_version":"6.0","1":"6.0","script_version":"9","2":"9","version_comment":"Numerous link and emphasis fixes.","3":"Numerous link and emphasis fixes.","package":"mkd.vim","4":"mkd.vim","src_id":"10630","5":"10630","creation_date":"1242676848","6":"1242676848"},{"0":"1242","vim_version":"6.0","1":"6.0","script_version":"8","2":"8","version_comment":"Really fix matching bold and underline characters inside of words.","3":"Really fix matching bold and underline characters inside of words.","package":"mkd.vim","4":"mkd.vim","src_id":"8622","5":"8622","creation_date":"1209541284","6":"1209541284"},{"0":"1242","vim_version":"6.0","1":"6.0","script_version":"7","2":"7","version_comment":"Fixes several bugs, most thanks to David Wolever:\r\n    * Don\u00e2\u0080\u0099t match bold and underline characters inside of words.\r\n    * Don\u00e2\u0080\u0099t match code blocks that aren\u00e2\u0080\u0099t preceded by a blank line.\r\n    * Fix double back-tick code blocks without a back-tick inside of them.\r\n    * Fix # headings being matched anywhere in the line.\r\n    * Match <pre> and <code> tags.\r\n\r\n","3":"Fixes several bugs, most thanks to David Wolever:\r\n    * Don\u00e2\u0080\u0099t match bold and underline characters inside of words.\r\n    * Don\u00e2\u0080\u0099t match code blocks that aren\u00e2\u0080\u0099t preceded by a blank line.\r\n    * Fix double back-tick code blocks without a back-tick inside of them.\r\n    * Fix # headings being matched anywhere in the line.\r\n    * Match <pre> and <code> tags.\r\n\r\n","package":"mkd.vim","4":"mkd.vim","src_id":"8375","5":"8375","creation_date":"1204372856","6":"1204372856"},{"0":"1242","vim_version":"6.0","1":"6.0","script_version":"6","2":"6","version_comment":"Enables spellchecking in Vim 7 and adds highlighting for reference-style links thanks to Will Norris.","3":"Enables spellchecking in Vim 7 and adds highlighting for reference-style links thanks to Will Norris.","package":"mkd.vim","4":"mkd.vim","src_id":"6127","5":"6127","creation_date":"1157106894","6":"1157106894"},{"0":"1242","vim_version":"6.0","1":"6.0","script_version":"5","2":"5","version_comment":"Fixes numbered headings being highlighted as list items and horizontal rules being highlighted as headings. Thanks to Stephen Haberman.","3":"Fixes numbered headings being highlighted as list items and horizontal rules being highlighted as headings. Thanks to Stephen Haberman.","package":"mkd.vim","4":"mkd.vim","src_id":"4845","5":"4845","creation_date":"1133441392","6":"1133441392"},{"0":"1242","vim_version":"6.0","1":"6.0","script_version":"4","2":"4","version_comment":"Fixes stuff in parentheses being highlighted when not part of a link structure. ","3":"Fixes stuff in parentheses being highlighted when not part of a link structure. ","package":"mkd.vim","4":"mkd.vim","src_id":"4515","5":"4515","creation_date":"1124867875","6":"1124867875"},{"0":"1242","vim_version":"6.0","1":"6.0","script_version":"3","2":"3","version_comment":"Fixes a problem with indented lists being highlighted as code blocks.","3":"Fixes a problem with indented lists being highlighted as code blocks.","package":"mkd.vim","4":"mkd.vim","src_id":"4245","5":"4245","creation_date":"1115272368","6":"1115272368"},{"0":"1242","vim_version":"6.0","1":"6.0","script_version":"2","2":"2","version_comment":"Initial upload","3":"Initial upload","package":"mkd.vim","4":"mkd.vim","src_id":"4050","5":"4050","creation_date":"1111389495","6":"1111389495"}]},"1241":{"script_id":"1241","0":"1241","script_name":"octave.vim","1":"octave.vim","script_type":"syntax","2":"syntax","summary":"Syntax highlighting for GNU Octave","3":"Syntax highlighting for GNU Octave","description":"Syntax highlighting for GNU Octave. It inherits the Matlab syntax highlighting and adds a few extra things like endif etc.","4":"Syntax highlighting for GNU Octave. It inherits the Matlab syntax highlighting and adds a few extra things like endif etc.","install_details":"Installation details from Paul Laub - thanks Paul!\r\nHere's what to do to get octave.vim working. \r\n\r\n1. Put octave vim in vim's syntax subdirectory. \r\n\r\n2. Directory above this subdirectory is the main vim directory. Find\r\nthe file named filetype.vim. Change \"matlab\" to \"octave\". With that,\r\nfiles with the *.m extension will be associated with octave.vim. Test\r\nby opening an octave file in vim. Keywords like endfunction should be\r\nhighlighted.\r\n\r\n3. (Optionally) modify the file synmenu.vim to include an Octave item\r\nin the syntax menu of the GUI version of vim. [I don't use menus so I\r\ncan't say more about how to do this.]\r\n\r\nAlso, since your script inherits formatting done by the matlab.vim\r\nfile, I'd advise people NOT  to delete matlab.vim and rename\r\noctave.vim to matlab.vim.\r\n\r\nAn alternative is to copy octave.vim to ~\/.vim\/syntax and add the following to ~\/.vimrc:\r\n\" Octave Syntax\r\naugroup filetypedetect\r\n     au! BufRead,BufNewFile *.m setfiletype octave\r\naugroup END\r\n","5":"Installation details from Paul Laub - thanks Paul!\r\nHere's what to do to get octave.vim working. \r\n\r\n1. Put octave vim in vim's syntax subdirectory. \r\n\r\n2. Directory above this subdirectory is the main vim directory. Find\r\nthe file named filetype.vim. Change \"matlab\" to \"octave\". With that,\r\nfiles with the *.m extension will be associated with octave.vim. Test\r\nby opening an octave file in vim. Keywords like endfunction should be\r\nhighlighted.\r\n\r\n3. (Optionally) modify the file synmenu.vim to include an Octave item\r\nin the syntax menu of the GUI version of vim. [I don't use menus so I\r\ncan't say more about how to do this.]\r\n\r\nAlso, since your script inherits formatting done by the matlab.vim\r\nfile, I'd advise people NOT  to delete matlab.vim and rename\r\noctave.vim to matlab.vim.\r\n\r\nAn alternative is to copy octave.vim to ~\/.vim\/syntax and add the following to ~\/.vimrc:\r\n\" Octave Syntax\r\naugroup filetypedetect\r\n     au! BufRead,BufNewFile *.m setfiletype octave\r\naugroup END\r\n","first_name":"S\u00c3\u00b8ren","6":"S\u00c3\u00b8ren","last_name":"Hauberg","7":"Hauberg","releases":[{"0":"1241","vim_version":"6.0","1":"6.0","script_version":"1.0.1","2":"1.0.1","version_comment":"I forgot to add end_switch, so I've just added that one. The only thing I think is missing is multiline strings, but I don't know how to do that. (If you do please help me)","3":"I forgot to add end_switch, so I've just added that one. The only thing I think is missing is multiline strings, but I don't know how to do that. (If you do please help me)","package":"octave.vim","4":"octave.vim","src_id":"4051","5":"4051","creation_date":"1111409207","6":"1111409207"},{"0":"1241","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"octave.vim","4":"octave.vim","src_id":"4039","5":"4039","creation_date":"1111050559","6":"1111050559"}]},"1240":{"script_id":"1240","0":"1240","script_name":"Guardian 2.0","1":"Guardian 2.0","script_type":"color scheme","2":"color scheme","summary":"A rich and stylish syntax highlighting for coders","3":"A rich and stylish syntax highlighting for coders","description":"Originally intended for XHTML and CSS editing in 2005, I grew to love this colors scheme - been using it as my default one for all these years.\r\n\r\nRich syntax highlighting with colors, bolds and italics in a semantic way designed to be practical and helpful for coders especially.\r\n\r\nIn 2017 updated the whole scheme to better suit modern monitors with better calibrated colors, better contrasts and higher precision.\r\n\r\nSCREENSHOT: https:\/\/pbs.twimg.com\/media\/C3mO6yJWYAALQTn.jpg:large","4":"Originally intended for XHTML and CSS editing in 2005, I grew to love this colors scheme - been using it as my default one for all these years.\r\n\r\nRich syntax highlighting with colors, bolds and italics in a semantic way designed to be practical and helpful for coders especially.\r\n\r\nIn 2017 updated the whole scheme to better suit modern monitors with better calibrated colors, better contrasts and higher precision.\r\n\r\nSCREENSHOT: https:\/\/pbs.twimg.com\/media\/C3mO6yJWYAALQTn.jpg:large","install_details":"A) UNIX\/Linux: Download to ~\/.vim\/colors\/.\r\nB) Win32: Download to <vim directory>\/vimfiles\/colors\/.\r\n\r\nThe colors scheme is then applied by typing :colors Guardian2","5":"A) UNIX\/Linux: Download to ~\/.vim\/colors\/.\r\nB) Win32: Download to <vim directory>\/vimfiles\/colors\/.\r\n\r\nThe colors scheme is then applied by typing :colors Guardian2","first_name":"Miikka-Markus","6":"Miikka-Markus","last_name":"Leskinen","7":"Leskinen","releases":[{"0":"1240","vim_version":"7.0","1":"7.0","script_version":"2.0","2":"2.0","version_comment":"Updated for modern Ultra HD monitors. Deeper colors.","3":"Updated for modern Ultra HD monitors. Deeper colors.","package":"guardian2.vim","4":"guardian2.vim","src_id":"24941","5":"24941","creation_date":"1485970468","6":"1485970468"}]},"1239":{"script_id":"1239","0":"1239","script_name":"autoit.vim","1":"autoit.vim","script_type":"syntax","2":"syntax","summary":"AutoIt syntax file","3":"AutoIt syntax file","description":"This is a syntax file for AutoIt v3, available from http:\/\/www.autoitscript.com\/autoit3\/.\r\n\r\nThis is an updated version of Riccardo Casini's original script:\r\nhttp:\/\/www.vim.org\/scripts\/script.php?script_id=968\r\n\r\nVersion 1.5 is included with the official Vim distribution beginning with version 7.1, but I will continue to update the syntax file as necessary for future versions of AutoIt.  These updates, along with change details, will be posted here.","4":"This is a syntax file for AutoIt v3, available from http:\/\/www.autoitscript.com\/autoit3\/.\r\n\r\nThis is an updated version of Riccardo Casini's original script:\r\nhttp:\/\/www.vim.org\/scripts\/script.php?script_id=968\r\n\r\nVersion 1.5 is included with the official Vim distribution beginning with version 7.1, but I will continue to update the syntax file as necessary for future versions of AutoIt.  These updates, along with change details, will be posted here.","install_details":"For Vim version 7.1 and above, which includes support for AutoIt by default, simply replace syntax\\autoit.vim in your Vim installation directory with the latest version of the AutoIt syntax file.\r\n\r\nFor older versions of Vim, which do not support AutoIt by default, follow these instructions:\r\n    1) copy the file in your current vim syntax folder\r\n    2) add the following line in your filetype.vim file, in the correct position, to recognize .au3 files by extension:\r\n    \"au BufNewFile,BufRead *.au3 setf autoit3\"","5":"For Vim version 7.1 and above, which includes support for AutoIt by default, simply replace syntax\\autoit.vim in your Vim installation directory with the latest version of the AutoIt syntax file.\r\n\r\nFor older versions of Vim, which do not support AutoIt by default, follow these instructions:\r\n    1) copy the file in your current vim syntax folder\r\n    2) add the following line in your filetype.vim file, in the correct position, to recognize .au3 files by extension:\r\n    \"au BufNewFile,BufRead *.au3 setf autoit3\"","first_name":"Jared","6":"Jared","last_name":"Breland","7":"Breland","releases":[{"0":"1239","vim_version":"7.0","1":"7.0","script_version":"1.10","2":"1.10","version_comment":"Updated for AutoIt 3.3.6.0","3":"Updated for AutoIt 3.3.6.0","package":"autoit.vim","4":"autoit.vim","src_id":"12827","5":"12827","creation_date":"1271218486","6":"1271218486"},{"0":"1239","vim_version":"7.0","1":"7.0","script_version":"1.9","2":"1.9","version_comment":"updated for AutoIt 3.3.0.0\r\nadded the MANY new constants and UDFs added in recent versions","3":"updated for AutoIt 3.3.0.0\r\nadded the MANY new constants and UDFs added in recent versions","package":"autoit.vim","4":"autoit.vim","src_id":"10617","5":"10617","creation_date":"1242547299","6":"1242547299"},{"0":"1239","vim_version":"7.0","1":"7.0","script_version":"1.8","2":"1.8","version_comment":"updated for AutoIt 3.2.12.1","3":"updated for AutoIt 3.2.12.1","package":"autoit.vim","4":"autoit.vim","src_id":"9327","5":"9327","creation_date":"1223586547","6":"1223586547"},{"0":"1239","vim_version":"7.0","1":"7.0","script_version":"1.7","2":"1.7","version_comment":"updated for AutoIt 3.2.10.0","3":"updated for AutoIt 3.2.10.0","package":"autoit.vim","4":"autoit.vim","src_id":"8344","5":"8344","creation_date":"1203861774","6":"1203861774"},{"0":"1239","vim_version":"6.0","1":"6.0","script_version":"1.6","2":"1.6","version_comment":"updated for AutoIt 3.2.4.9","3":"updated for AutoIt 3.2.4.9","package":"autoit.vim","4":"autoit.vim","src_id":"7226","5":"7226","creation_date":"1181480726","6":"1181480726"},{"0":"1239","vim_version":"6.0","1":"6.0","script_version":"1.5","2":"1.5","version_comment":"updated for AutoIt 3.2.2.0\r\nupdated constant and option strings to recognize ' and \" quotes\r\nmore cleanup for inclusion in Vim distribution","3":"updated for AutoIt 3.2.2.0\r\nupdated constant and option strings to recognize ' and \" quotes\r\nmore cleanup for inclusion in Vim distribution","package":"autoit.vim","4":"autoit.vim","src_id":"6608","5":"6608","creation_date":"1168522416","6":"1168522416"},{"0":"1239","vim_version":"6.0","1":"6.0","script_version":"1.4","2":"1.4","version_comment":"Updated for AutoIt 3.2.0.1","3":"Updated for AutoIt 3.2.0.1","package":"autoit.vim","4":"autoit.vim","src_id":"6105","5":"6105","creation_date":"1156680553","6":"1156680553"},{"0":"1239","vim_version":"6.0","1":"6.0","script_version":"1.3","2":"1.3","version_comment":"Updated for AutoIt 3.1.1.123-beta\r\nAdded new keywords and functions\r\nAdded Styles section\r\nAdded Constants section\r\nAdded Send Key section\r\nChanged variable formatting to match PHP style","3":"Updated for AutoIt 3.1.1.123-beta\r\nAdded new keywords and functions\r\nAdded Styles section\r\nAdded Constants section\r\nAdded Send Key section\r\nChanged variable formatting to match PHP style","package":"autoit.vim","4":"autoit.vim","src_id":"5686","5":"5686","creation_date":"1147483907","6":"1147483907"},{"0":"1239","vim_version":"6.0","1":"6.0","script_version":"1.2","2":"1.2","version_comment":"Updated for AutoIt 3.1.1.78-beta;\r\nAdded new keywords and functions;\r\nAdded section for options","3":"Updated for AutoIt 3.1.1.78-beta;\r\nAdded new keywords and functions;\r\nAdded section for options","package":"autoit.vim","4":"autoit.vim","src_id":"4653","5":"4653","creation_date":"1128646092","6":"1128646092"},{"0":"1239","vim_version":"6.0","1":"6.0","script_version":"1.1","2":"1.1","version_comment":"Initial upload","3":"Initial upload","package":"autoit.vim","4":"autoit.vim","src_id":"4027","5":"4027","creation_date":"1110918620","6":"1110918620"}]},"1238":{"script_id":"1238","0":"1238","script_name":"Mark","1":"Mark","script_type":"utility","2":"utility","summary":"a little script to highlight several words in different colors simultaneously","3":"a little script to highlight several words in different colors simultaneously","description":"This script is written to highlight several words in different colors simultaneously. For example, when you are browsing a big program file, you could highlight some key variables. This will make it easier to trace the source code.\r\n\r\nI found Ingo Karkat has a fork development on mark.vim and you may be interest to check it out:\r\nhttp:\/\/www.vim.org\/scripts\/script.php?script_id=2666\r\nmark.vim continues to be developed in my taste. :-)\r\n\r\nUsage:\r\n\r\nHighlighting:\r\n  Normal mode:\r\n    \\m mark\/unmark the word under (or before) the cursor\r\n          Place the cursor under the word to be highlighted, press \\m, then the word will be colored.\r\n    \\r manually input a regular expression\r\n          To highlight an arbitrary regular expression, press \\r and input the regexp.\r\n    \\n clear this mark (i.e. the mark under the cursor), or mute\/unmute all highlighted marks\r\n          To clear all marks (instead of mute them), please use \\m in muted state.\r\n  Visual mode:\r\n    \\m mark\/unmark a visual selection\r\n          Select some text in Visual mode, press \\m, then the selection will be colored.\r\n    \\r manually input a regular expression (base on the selection text)\r\n  Command line:\r\n    :Mark regexp   to mark a regular expression\r\n    :Mark regexp   with exactly the same regexp to unmark it\r\n    :Mark          to mute all marks\r\n    :Mark          to show all marks again\r\nSearching:\r\n  Normal mode:\r\n    * # \\* \\# \\\/ \\? use these six keys to jump to the other marks\r\n    and you could also use VIM's \/ and ? to search, since the mark patterns have\r\n    been added to the search history.\r\n\r\nHere is a sumerization of * # \\* \\# \\\/ \\?:\r\n\r\n\" First of all, \\#, \\? and # behave just like \\*, \\\/ and *, respectively,\r\n\" except that \\#, \\? and # search backward.\r\n\"\r\n\" \\*, \\\/ and *'s behaviors differ base on whether the cursor is currently\r\n\" placed over an active mark:\r\n\"\r\n\"       Cursor over mark                  Cursor not over mark\r\n\" ---------------------------------------------------------------------------\r\n\"  \\*   jump to the next occurrence of      jump to the next occurrence of\r\n\"       current mark, and remember it       \"last mark\".\r\n\"       as \"last mark\".\r\n\"\r\n\"  \\\/   jump to the next occurrence of        same as left\r\n\"       ANY mark.\r\n\"\r\n\"   *   if \\* is the most recently used,        do VIM's original *\r\n\"       do a \\*; otherwise (\\\/ is the\r\n\"       most recently used), do a \\\/.\r\n\r\nScreenshot:\r\nhttp:\/\/elefant.name\/files\/vim_screenshot.png (1.1.11-g, It is also the screenshot of my colorscheme vimscript #1253.)\r\n\r\nBugs and Notes:\r\nSome words which have been already colored by syntax scripts could not be highlighted in VIM 7.0 or before. Please upgrade your VIM to a newer version.\r\n\r\nmark.vim should be re-sourced after any changing to colors. For example, if you\r\n:set background=dark  OR\r\n:colorscheme default\r\nyou should\r\n:source PATH_OF_PLUGINS\/mark.vim\r\nafter that. Otherwise, you won't see the colors.\r\nUnfortunately, it seems that .gvimrc runs after plugin scripts. So if you set any color settings in .gvimrc, you have to add one line to the end of .gvimrc to source mark.vim.","4":"This script is written to highlight several words in different colors simultaneously. For example, when you are browsing a big program file, you could highlight some key variables. This will make it easier to trace the source code.\r\n\r\nI found Ingo Karkat has a fork development on mark.vim and you may be interest to check it out:\r\nhttp:\/\/www.vim.org\/scripts\/script.php?script_id=2666\r\nmark.vim continues to be developed in my taste. :-)\r\n\r\nUsage:\r\n\r\nHighlighting:\r\n  Normal mode:\r\n    \\m mark\/unmark the word under (or before) the cursor\r\n          Place the cursor under the word to be highlighted, press \\m, then the word will be colored.\r\n    \\r manually input a regular expression\r\n          To highlight an arbitrary regular expression, press \\r and input the regexp.\r\n    \\n clear this mark (i.e. the mark under the cursor), or mute\/unmute all highlighted marks\r\n          To clear all marks (instead of mute them), please use \\m in muted state.\r\n  Visual mode:\r\n    \\m mark\/unmark a visual selection\r\n          Select some text in Visual mode, press \\m, then the selection will be colored.\r\n    \\r manually input a regular expression (base on the selection text)\r\n  Command line:\r\n    :Mark regexp   to mark a regular expression\r\n    :Mark regexp   with exactly the same regexp to unmark it\r\n    :Mark          to mute all marks\r\n    :Mark          to show all marks again\r\nSearching:\r\n  Normal mode:\r\n    * # \\* \\# \\\/ \\? use these six keys to jump to the other marks\r\n    and you could also use VIM's \/ and ? to search, since the mark patterns have\r\n    been added to the search history.\r\n\r\nHere is a sumerization of * # \\* \\# \\\/ \\?:\r\n\r\n\" First of all, \\#, \\? and # behave just like \\*, \\\/ and *, respectively,\r\n\" except that \\#, \\? and # search backward.\r\n\"\r\n\" \\*, \\\/ and *'s behaviors differ base on whether the cursor is currently\r\n\" placed over an active mark:\r\n\"\r\n\"       Cursor over mark                  Cursor not over mark\r\n\" ---------------------------------------------------------------------------\r\n\"  \\*   jump to the next occurrence of      jump to the next occurrence of\r\n\"       current mark, and remember it       \"last mark\".\r\n\"       as \"last mark\".\r\n\"\r\n\"  \\\/   jump to the next occurrence of        same as left\r\n\"       ANY mark.\r\n\"\r\n\"   *   if \\* is the most recently used,        do VIM's original *\r\n\"       do a \\*; otherwise (\\\/ is the\r\n\"       most recently used), do a \\\/.\r\n\r\nScreenshot:\r\nhttp:\/\/elefant.name\/files\/vim_screenshot.png (1.1.11-g, It is also the screenshot of my colorscheme vimscript #1253.)\r\n\r\nBugs and Notes:\r\nSome words which have been already colored by syntax scripts could not be highlighted in VIM 7.0 or before. Please upgrade your VIM to a newer version.\r\n\r\nmark.vim should be re-sourced after any changing to colors. For example, if you\r\n:set background=dark  OR\r\n:colorscheme default\r\nyou should\r\n:source PATH_OF_PLUGINS\/mark.vim\r\nafter that. Otherwise, you won't see the colors.\r\nUnfortunately, it seems that .gvimrc runs after plugin scripts. So if you set any color settings in .gvimrc, you have to add one line to the end of .gvimrc to source mark.vim.","install_details":"Just drop the script file \"mark.vim\" into the plugin directory. Restart VIM.\r\n\r\nAdd ! in viminfo if you want marks restorable on next vim start. E.g.:\r\n  set viminfo='64,<8192,s1024,!,h\r\n\r\nIf you want to use another leader instead of default \"\\\", you may say in your .vimrc\r\n    let mapleader = \",\"\r\nThat will use ,m ,r ,n instead of \\m \\r \\n as the trigger.\r\n\r\nIf you set any color settings in .gvimrc, you should also add\r\n    source PATH_OF_PLUGINS\/mark.vim\r\nto the end of .gvimrc (see above).\r\n\r\nIf you want different colors or more colors, you may define MarkWord1-6, 7, 8...\r\nin your vimrc file. Just to pay attention that there should be no lines like\r\n    colorscheme xxxx\r\n    set background=dark\r\nrun after you have set your colors. It's due to the same reason.","5":"Just drop the script file \"mark.vim\" into the plugin directory. Restart VIM.\r\n\r\nAdd ! in viminfo if you want marks restorable on next vim start. E.g.:\r\n  set viminfo='64,<8192,s1024,!,h\r\n\r\nIf you want to use another leader instead of default \"\\\", you may say in your .vimrc\r\n    let mapleader = \",\"\r\nThat will use ,m ,r ,n instead of \\m \\r \\n as the trigger.\r\n\r\nIf you set any color settings in .gvimrc, you should also add\r\n    source PATH_OF_PLUGINS\/mark.vim\r\nto the end of .gvimrc (see above).\r\n\r\nIf you want different colors or more colors, you may define MarkWord1-6, 7, 8...\r\nin your vimrc file. Just to pay attention that there should be no lines like\r\n    colorscheme xxxx\r\n    set background=dark\r\nrun after you have set your colors. It's due to the same reason.","first_name":"Yuheng","6":"Yuheng","last_name":"Xie","7":"Xie","releases":[{"0":"1238","vim_version":"6.0","1":"6.0","script_version":"1.2.2-g","2":"1.2.2-g","version_comment":"default state to muted when vim restarts, press \\n to reshow all marks in last vim session.","3":"default state to muted when vim restarts, press \\n to reshow all marks in last vim session.","package":"mark.vim","4":"mark.vim","src_id":"26365","5":"26365","creation_date":"1548868807","6":"1548868807"},{"0":"1238","vim_version":"6.0","1":"6.0","script_version":"1.2.1-g","2":"1.2.1-g","version_comment":"fix multi-lines mark searching\/unmarking","3":"fix multi-lines mark searching\/unmarking","package":"mark.vim","4":"mark.vim","src_id":"26362","5":"26362","creation_date":"1548644184","6":"1548644184"},{"0":"1238","vim_version":"6.0","1":"6.0","script_version":"1.2-g","2":"1.2-g","version_comment":"1. Instead of clear all marks, \\n now simply mutes them, press \\n once more to show them again\r\n2. To clear all marks (instead of mute them), press \\m (to create a new mark) when muted\r\n3. Marks are now savable if 'viminfo' has the ! flag. E.g. set viminfo='64,<8192,s1024,!,h","3":"1. Instead of clear all marks, \\n now simply mutes them, press \\n once more to show them again\r\n2. To clear all marks (instead of mute them), press \\m (to create a new mark) when muted\r\n3. Marks are now savable if 'viminfo' has the ! flag. E.g. set viminfo='64,<8192,s1024,!,h","package":"mark.vim","4":"mark.vim","src_id":"26348","5":"26348","creation_date":"1547502544","6":"1547502544"},{"0":"1238","vim_version":"6.0","1":"6.0","script_version":"1.1.13-g","2":"1.1.13-g","version_comment":"fix unnamed-register content after visual marking","3":"fix unnamed-register content after visual marking","package":"mark.vim","4":"mark.vim","src_id":"26334","5":"26334","creation_date":"1547053114","6":"1547053114"},{"0":"1238","vim_version":"6.0","1":"6.0","script_version":"1.1.12-g","2":"1.1.12-g","version_comment":"fixed errors when no marks found","3":"fixed errors when no marks found","package":"mark.vim","4":"mark.vim","src_id":"25652","5":"25652","creation_date":"1511250058","6":"1511250058"},{"0":"1238","vim_version":"6.0","1":"6.0","script_version":"1.1.11-g","2":"1.1.11-g","version_comment":"make compatible with vim 6.4; default mark colors now use 256 color names if available.","3":"make compatible with vim 6.4; default mark colors now use 256 color names if available.","package":"mark.vim","4":"mark.vim","src_id":"24806","5":"24806","creation_date":"1481982032","6":"1481982032"},{"0":"1238","vim_version":"7.2","1":"7.2","script_version":"1.1.10-g","2":"1.1.10-g","version_comment":"This is a small bug fix for 1.1.9-g, reload highlights after :split etc.","3":"This is a small bug fix for 1.1.9-g, reload highlights after :split etc.","package":"mark.vim","4":"mark.vim","src_id":"22972","5":"22972","creation_date":"1425280258","6":"1425280258"},{"0":"1238","vim_version":"7.0","1":"7.0","script_version":"1.1.9-g","2":"1.1.9-g","version_comment":"added call to VIM 7.1 matchadd(), make highlighting keywords possible","3":"added call to VIM 7.1 matchadd(), make highlighting keywords possible","package":"mark.vim","4":"mark.vim","src_id":"22275","5":"22275","creation_date":"1406650263","6":"1406650263"},{"0":"1238","vim_version":"7.0","1":"7.0","script_version":"1.1.8-g","2":"1.1.8-g","version_comment":"1.1.8 global version. It differ from 1.1.8 that colors will be shared between buffers, instead of localized to buffers as in 1.1.8.\r\nIf you would like to have the same words highlighted in different files, use this.\r\nIf you would like to have different words highlighted in different files, use 1.1.8.","3":"1.1.8 global version. It differ from 1.1.8 that colors will be shared between buffers, instead of localized to buffers as in 1.1.8.\r\nIf you would like to have the same words highlighted in different files, use this.\r\nIf you would like to have different words highlighted in different files, use 1.1.8.","package":"mark.vim","4":"mark.vim","src_id":"8603","5":"8603","creation_date":"1209086639","6":"1209086639"},{"0":"1238","vim_version":"6.0","1":"6.0","script_version":"1.1.8","2":"1.1.8","version_comment":"Added \\* \\# \\\/ \\? for the ability of jumping to ANY mark, even when the cursor is not currently over any mark.\r\n","3":"Added \\* \\# \\\/ \\? for the ability of jumping to ANY mark, even when the cursor is not currently over any mark.\r\n","package":"mark.vim","4":"mark.vim","src_id":"5400","5":"5400","creation_date":"1141953858","6":"1141953858"},{"0":"1238","vim_version":"6.0","1":"6.0","script_version":"1.1.7","2":"1.1.7","version_comment":"bug fix again","3":"bug fix again","package":"mark.vim","4":"mark.vim","src_id":"4632","5":"4632","creation_date":"1128027803","6":"1128027803"},{"0":"1238","vim_version":"6.0","1":"6.0","script_version":"1.1.5","2":"1.1.5","version_comment":"Thank Luc Hermitte for the big improvement to my script:\r\n1) now can use :Mark to trigger the function.\r\n2) \\r on visual mode to input a regexp base on the selection\r\n3) may alter the leader (instead of default \"\\\") in .vimrc","3":"Thank Luc Hermitte for the big improvement to my script:\r\n1) now can use :Mark to trigger the function.\r\n2) \\r on visual mode to input a regexp base on the selection\r\n3) may alter the leader (instead of default \"\\\") in .vimrc","package":"mark.vim","4":"mark.vim","src_id":"4598","5":"4598","creation_date":"1127163240","6":"1127163240"},{"0":"1238","vim_version":"6.0","1":"6.0","script_version":"1.1.4","2":"1.1.4","version_comment":"use map-<silent> to avoid echo on the command line","3":"use map-<silent> to avoid echo on the command line","package":"mark.vim","4":"mark.vim","src_id":"4322","5":"4322","creation_date":"1117130368","6":"1117130368"},{"0":"1238","vim_version":"6.0","1":"6.0","script_version":"1.1.2","2":"1.1.2","version_comment":"\\n now first try to clear this mark (i.e. the mark under the cursor), before clearing all marks. \r\nmapped * and # for jumping to the next and previous occurrence of this mark. \r\nmark patterns now also added to the search history","3":"\\n now first try to clear this mark (i.e. the mark under the cursor), before clearing all marks. \r\nmapped * and # for jumping to the next and previous occurrence of this mark. \r\nmark patterns now also added to the search history","package":"mark.vim","4":"mark.vim","src_id":"4059","5":"4059","creation_date":"1111520029","6":"1111520029"}]},"1237":{"script_id":"1237","0":"1237","script_name":"MS SQL Server Syntax","1":"MS SQL Server Syntax","script_type":"syntax","2":"syntax","summary":"Microsoft SQL Server 2000 T-SQL (Transact-SQL) Syntax","3":"Microsoft SQL Server 2000 T-SQL (Transact-SQL) Syntax","description":"Syntax file for M$ SQL Server 2000 Transact-SQL\r\n\r\nI added all reserved words, system functions and stored procedures.\r\n\r\nNotes:\r\n- All types, statements, and operators are colored as Keyword.\r\n- All keywords must be UPPER_CASED.\r\n- @local_variables (lower_cased) are colored as Special\r\n- User-defined types in the form of \"Some_User_Defined_Type\" are colored as Type. (you must append the ending \"_Type\")\r\n- @@SYSTEM_VARIABLES are colored as PreProc. Must be UPPER_CASED too.","4":"Syntax file for M$ SQL Server 2000 Transact-SQL\r\n\r\nI added all reserved words, system functions and stored procedures.\r\n\r\nNotes:\r\n- All types, statements, and operators are colored as Keyword.\r\n- All keywords must be UPPER_CASED.\r\n- @local_variables (lower_cased) are colored as Special\r\n- User-defined types in the form of \"Some_User_Defined_Type\" are colored as Type. (you must append the ending \"_Type\")\r\n- @@SYSTEM_VARIABLES are colored as PreProc. Must be UPPER_CASED too.","install_details":"Put it into \/syntax\/sql.vim","5":"Put it into \/syntax\/sql.vim","first_name":"Aquila","6":"Aquila","last_name":"Deus","7":"Deus","releases":[{"0":"1237","vim_version":"6.0","1":"6.0","script_version":"0.99","2":"0.99","version_comment":"Initial upload","3":"Initial upload","package":"sql.vim","4":"sql.vim","src_id":"4008","5":"4008","creation_date":"1110659516","6":"1110659516"}]},"1236":{"script_id":"1236","0":"1236","script_name":"xhtml.vim","1":"xhtml.vim","script_type":"syntax","2":"syntax","summary":"XHTML syntax highlighting","3":"XHTML syntax highlighting","description":"Syntax highlighting for Extensible HyperText Markup Language.\r\nHandles XHTML 1.0 (Strict, Transitional and Frameset) and XHTML 1.1;\r\nXHTML 2.0 (as of 7th Working Draft), including XML Events and XForms, is also highlighted.\r\n\r\nSyntax of the following languages embedded in XHTML document can be highlighted: MathML, SVG, CSS, JavaScript, VBScript, SSI and XSSI.\r\n\r\nThere is also special highlighting for XHTML events (\"on...\" attributes with JavaScript content), however it is possible to disable it by setting the following variable:\r\n    xhtml_no_events_rendering\r\n(just insert line \"let xhtml_no_events_rendering=1\" to your .vimrc file).\r\n\r\nCSS highlighting in \"style\" attributes is availaible too; you can disable it by setting this variable:\r\n    xhtml_no_inline_css_rendering\r\n","4":"Syntax highlighting for Extensible HyperText Markup Language.\r\nHandles XHTML 1.0 (Strict, Transitional and Frameset) and XHTML 1.1;\r\nXHTML 2.0 (as of 7th Working Draft), including XML Events and XForms, is also highlighted.\r\n\r\nSyntax of the following languages embedded in XHTML document can be highlighted: MathML, SVG, CSS, JavaScript, VBScript, SSI and XSSI.\r\n\r\nThere is also special highlighting for XHTML events (\"on...\" attributes with JavaScript content), however it is possible to disable it by setting the following variable:\r\n    xhtml_no_events_rendering\r\n(just insert line \"let xhtml_no_events_rendering=1\" to your .vimrc file).\r\n\r\nCSS highlighting in \"style\" attributes is availaible too; you can disable it by setting this variable:\r\n    xhtml_no_inline_css_rendering\r\n","install_details":"Requires mathml.vim (vimscript #1235) and svg.vim (vimscript #935) (for version 1.0.1+ you need mathml.vim v. 1.0.1+ and svg.vim v. 1.1.1+).\r\nHowever, you can choose not to use MathML and SVG syntax files \u00e2\u0080\u0093 in that case you will have to set the following variables in your .vimrc:\r\n    xhtml_no_embedded_mathml\r\n    xhtml_no_embedded_svg\r\n\r\nDrop xhtml.vim into your syntax directory. You should also disable (e.g. rename or delete) XHTML syntax file that comes with distribution, to avoid unnecessary sourcing of HTML syntax file.\r\n\r\nProbably you have got already appropriate entry in filetype.vim (for *.html, *.htm, *.shtml and *.stm files), but it's good idea to add also *.xhtml and *.xht files recognizing:\r\n    au BufNewFile,BufRead *.xhtml,*.xht setf xhtml","5":"Requires mathml.vim (vimscript #1235) and svg.vim (vimscript #935) (for version 1.0.1+ you need mathml.vim v. 1.0.1+ and svg.vim v. 1.1.1+).\r\nHowever, you can choose not to use MathML and SVG syntax files \u00e2\u0080\u0093 in that case you will have to set the following variables in your .vimrc:\r\n    xhtml_no_embedded_mathml\r\n    xhtml_no_embedded_svg\r\n\r\nDrop xhtml.vim into your syntax directory. You should also disable (e.g. rename or delete) XHTML syntax file that comes with distribution, to avoid unnecessary sourcing of HTML syntax file.\r\n\r\nProbably you have got already appropriate entry in filetype.vim (for *.html, *.htm, *.shtml and *.stm files), but it's good idea to add also *.xhtml and *.xht files recognizing:\r\n    au BufNewFile,BufRead *.xhtml,*.xht setf xhtml","first_name":"Micha\u0142","6":"Michał","last_name":"G\u00c3\u00b3rny","7":"G\u00c3\u00b3rny","releases":[{"0":"1236","vim_version":"6.0","1":"6.0","script_version":"1.2","2":"1.2","version_comment":"Added xml-stylesheet processing instruction attributes","3":"Added xml-stylesheet processing instruction attributes","package":"xhtml.vim","4":"xhtml.vim","src_id":"5481","5":"5481","creation_date":"1143088760","6":"1143088760"},{"0":"1236","vim_version":"6.0","1":"6.0","script_version":"1.1","2":"1.1","version_comment":"XHTML 2.0 updated to 7th Working Draft; some other minor changes","3":"XHTML 2.0 updated to 7th Working Draft; some other minor changes","package":"xhtml.vim","4":"xhtml.vim","src_id":"4385","5":"4385","creation_date":"1119432965","6":"1119432965"},{"0":"1236","vim_version":"6.0","1":"6.0","script_version":"1.0.3","2":"1.0.3","version_comment":"Fixed XML declaration attribs highlighting","3":"Fixed XML declaration attribs highlighting","package":"xhtml.vim","4":"xhtml.vim","src_id":"4347","5":"4347","creation_date":"1118154693","6":"1118154693"},{"0":"1236","vim_version":"6.0","1":"6.0","script_version":"1.0.2","2":"1.0.2","version_comment":"Corrected XHTML2-style links rendering on h1-h6 elements","3":"Corrected XHTML2-style links rendering on h1-h6 elements","package":"xhtml.vim","4":"xhtml.vim","src_id":"4169","5":"4169","creation_date":"1113565572","6":"1113565572"},{"0":"1236","vim_version":"6.0","1":"6.0","script_version":"1.0.1","2":"1.0.1","version_comment":"Few small corrections","3":"Few small corrections","package":"xhtml.vim","4":"xhtml.vim","src_id":"4153","5":"4153","creation_date":"1113215179","6":"1113215179"},{"0":"1236","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"xhtml.vim","4":"xhtml.vim","src_id":"4003","5":"4003","creation_date":"1110532366","6":"1110532366"}]},"1235":{"script_id":"1235","0":"1235","script_name":"mathml.vim","1":"mathml.vim","script_type":"syntax","2":"syntax","summary":"MathML syntax highlighting","3":"MathML syntax highlighting","description":"File for Mathematical Markup Language 2.0 syntax highlighting.\r\nUses XML syntax file.","4":"File for Mathematical Markup Language 2.0 syntax highlighting.\r\nUses XML syntax file.","install_details":"Put mathml.vim in your syntax directory\r\nand add the following line to your filetype.vim file:\r\n\r\nau BufNewFile,BufRead *.mml setf mathml","5":"Put mathml.vim in your syntax directory\r\nand add the following line to your filetype.vim file:\r\n\r\nau BufNewFile,BufRead *.mml setf mathml","first_name":"Micha\u0142","6":"Michał","last_name":"G\u00c3\u00b3rny","7":"G\u00c3\u00b3rny","releases":[{"0":"1235","vim_version":"6.0","1":"6.0","script_version":"1.1","2":"1.1","version_comment":"Added xml-stylesheet processing instruction attributes","3":"Added xml-stylesheet processing instruction attributes","package":"mathml.vim","4":"mathml.vim","src_id":"5479","5":"5479","creation_date":"1143088150","6":"1143088150"},{"0":"1235","vim_version":"6.0","1":"6.0","script_version":"1.0.2","2":"1.0.2","version_comment":"Fixed XML declaration attribs highlighting","3":"Fixed XML declaration attribs highlighting","package":"mathml.vim","4":"mathml.vim","src_id":"4350","5":"4350","creation_date":"1118163092","6":"1118163092"},{"0":"1235","vim_version":"6.0","1":"6.0","script_version":"1.0.1","2":"1.0.1","version_comment":"Compatibility changes","3":"Compatibility changes","package":"mathml.vim","4":"mathml.vim","src_id":"4152","5":"4152","creation_date":"1113215023","6":"1113215023"},{"0":"1235","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"mathml.vim","4":"mathml.vim","src_id":"3998","5":"3998","creation_date":"1110469530","6":"1110469530"}]},"1234":{"script_id":"1234","0":"1234","script_name":"YankRing.vim","1":"YankRing.vim","script_type":"utility","2":"utility","summary":"Maintains a history of previous yanks, changes and deletes","3":"Maintains a history of previous yanks, changes and deletes","description":"Vim already maintains a list of numbered registers containing the last 9 deletes.  These previous deletes can be referenced using [register]p, so \"1p will paste the last delete, \"2p the 2nd last delete.  For more information see |quote_number|.\r\n\r\nVim does not provide any mechanism to reference previous yanked, deleted or changed text.  In Emacs this feature is called the \"kill ring\".\r\n\r\nThe YankRing plugin allows the user to configure the number of yanked, deleted and changed text.  A split window can be used to choose which element(s) from the yankring you wish to paste.  Alternately after text has been pasted (using p), it can be replaced with a previous value from the yankring with a single key stroke.\r\n\r\nThe captured text is stored in a file (location configurable) and is instantly available (also configurable) to any other instance of Vim also running on the same machine.  This can especially be useful on *nix machines when you are sshed in running Vim in multiple terminals.\r\n\r\nStoring the capture text in a file allows the text to be shared easily between multiple instances of Vim running in X, Windows, SSH or Screen.\r\n\r\nA tutorial is included to take you through the various features of the plugin.  After you have installed the plugin just run:\r\n     :h yankring.txt\r\n     :h yankring-tutorial\r\n\r\nThe yankring can be interacted with in two ways:  a GUI or via maps.\r\n\r\nThe yankring supports all of Vim motions and text-objects.  There are very few new keystrokes the user must learn.   One keystroke to open the yankring to choose which item to paste is all that is required.  It has been designed work seamlessly with Vim\r\n\r\nAll the mappings and behaviours are configurable via global variables you can optionally specify in your vimrc.\r\n\r\nThe plugin can be toggled on and off, and supports:\r\n    Ranges\r\n    Registers\r\n    Counts\r\n    All visual modes (characterwise, linewise and blockwise)\r\n    All motions\r\n    All text-objects\r\n\r\nExamples:\r\n    yy - Adds the current line to the yankring.\r\n    dd - Adds the current line to the yankring and deletes it.\r\n   5yw - Adds 5 words to the yankring.\r\n  \"ade - Deletes the word, and puts it into both the yankring and the \"a register.\r\n    cw - Changes the word and stores the previous value in the yankring.\r\n10\"zyy - Places 10 lines into both the yankring and the \"z register.\r\n :1,4YRYankRange   - Similar to 1,4y\r\n :3,$YRDeleteRange  - Similar to 3,$d\r\n\r\nIf you wish to paste previous values from the yankring and do not want to use the GUI, there are only two additional maps you must learn (these are configurable via your vimrc if needed).  The purpose of the yankring is to gain access to previously yanked (or deleted) elements.  The YRReplace command will replace the previously pasted text with a different entry from the yankring.  By default, I choose <C-P> (P for previous) to replace the text last pasted while moving backwards through your previous text from the yankring and <C-N> (N for next) to replace the previous paste while moving forward through the yankring.\r\n\r\nA separate buffer window to allow you to easily interact with the contents of the yankring.  The window is similar to many other plugins: TagList, SelectBuf and so on.  You can use the mouse or standard Vim keys (p, gp, P, ...).  Visual mode is used to support counts, pasting multiple times and reversing the order of pasted elements.\r\n\r\nThe GUI significantly simplifies your interaction with the yankring for basic functions.  But often it useful to take advantage of the more powerful features of the yankring.\r\n\r\nHere is a small section from the tutorial (using maps) so you have some idea of how you interact with the plugin gaining access to previous yanks.  Using the GUI for basic operations is self explanatory.\r\n\r\n:h yankring-tutorial\r\n\r\n---- Partial Tutorial ----\r\nTo understand how to use the yankring, the following example should demonstrate the various features.\r\n\r\nAssume we have this buffer: \r\n        one\r\n        two\r\n        three\r\n        four\r\n        five\r\n\r\nNow yank (yy) each line separately starting at line 1.  Display the\r\ncontents of the yankring. \r\n        :YRShow  \r\n            --- YankRing ---\r\n            Elem  Content\r\n            5     five^@\r\n            4     four^@\r\n            3     three^@\r\n            2     two^@\r\n            1     one^@\r\nSince we yanked the text starting at line 1 and finishing at line 5, the most current yankring element is the last one, the contents of line 5.  \r\n\"five^@\" is displayed, the \"^@\" is a newline character (since we issued a \"yy\").\r\n\r\nNow, go to the end of the file and press p.  The resulting buffer appears as: \r\n        one\r\n        two\r\n        three\r\n        four\r\n        five\r\n        five\r\nNow press <C-P> to move backwards through the yankring, this results in: \r\n        one\r\n        two\r\n        three\r\n        four\r\n        five\r\n        four\r\nNow press 2<C-P>.  This would be the same as pressing <C-P> two times in a row.  This results in: \r\n        one\r\n        two\r\n        three\r\n        four\r\n        five\r\n        two\r\nNow press <C-N> to move forwards through the yankring, this results in: \r\n        one\r\n        two\r\n        three\r\n        four\r\n        five\r\n        three\r\n\r\nYou can create a map to display a buffer displaying the yankring's contents:\r\n    nnoremap <silent> <F11> :YRShow<CR>\r\n\r\nYRShow creates a new split buffer (you can configure where it should be and it's size)\r\n        :YRShow  \r\n            AutoClose=1;Cmds:<enter>,[g]p,[p]P,d,r,a,u,q,<space>;Help=?\r\n            --- YankRing ---\r\n            Elem  Content\r\n            3     three^@\r\n            2     two^@\r\n            1     one^@\r\n            5     five^@\r\n            4     four^@\r\nYou can simply hit \"p\", <enter>, double click on an item and it will be pasted into your document.  The window will automatically close (by default) after you have made a choice.  The element will be pasted into the correct buffer if you have multiple split windows.\r\n\r\nYou can paste multiple items using visual mode.\r\nYou can also remove items from the yankring.\r\n\r\n---- Partial Tutorial ----\r\n\r\nConcentrating on the last line of the buffer you could see how we were able to replace our pasted text with lines yanked previously.  This is a feature Vim only has for deletes, and is limited to 9.  This plugin enables the same features for both yanks, deletes and changes, the size of the history is configurable.\r\n\r\n\r\n\r\n","4":"Vim already maintains a list of numbered registers containing the last 9 deletes.  These previous deletes can be referenced using [register]p, so \"1p will paste the last delete, \"2p the 2nd last delete.  For more information see |quote_number|.\r\n\r\nVim does not provide any mechanism to reference previous yanked, deleted or changed text.  In Emacs this feature is called the \"kill ring\".\r\n\r\nThe YankRing plugin allows the user to configure the number of yanked, deleted and changed text.  A split window can be used to choose which element(s) from the yankring you wish to paste.  Alternately after text has been pasted (using p), it can be replaced with a previous value from the yankring with a single key stroke.\r\n\r\nThe captured text is stored in a file (location configurable) and is instantly available (also configurable) to any other instance of Vim also running on the same machine.  This can especially be useful on *nix machines when you are sshed in running Vim in multiple terminals.\r\n\r\nStoring the capture text in a file allows the text to be shared easily between multiple instances of Vim running in X, Windows, SSH or Screen.\r\n\r\nA tutorial is included to take you through the various features of the plugin.  After you have installed the plugin just run:\r\n     :h yankring.txt\r\n     :h yankring-tutorial\r\n\r\nThe yankring can be interacted with in two ways:  a GUI or via maps.\r\n\r\nThe yankring supports all of Vim motions and text-objects.  There are very few new keystrokes the user must learn.   One keystroke to open the yankring to choose which item to paste is all that is required.  It has been designed work seamlessly with Vim\r\n\r\nAll the mappings and behaviours are configurable via global variables you can optionally specify in your vimrc.\r\n\r\nThe plugin can be toggled on and off, and supports:\r\n    Ranges\r\n    Registers\r\n    Counts\r\n    All visual modes (characterwise, linewise and blockwise)\r\n    All motions\r\n    All text-objects\r\n\r\nExamples:\r\n    yy - Adds the current line to the yankring.\r\n    dd - Adds the current line to the yankring and deletes it.\r\n   5yw - Adds 5 words to the yankring.\r\n  \"ade - Deletes the word, and puts it into both the yankring and the \"a register.\r\n    cw - Changes the word and stores the previous value in the yankring.\r\n10\"zyy - Places 10 lines into both the yankring and the \"z register.\r\n :1,4YRYankRange   - Similar to 1,4y\r\n :3,$YRDeleteRange  - Similar to 3,$d\r\n\r\nIf you wish to paste previous values from the yankring and do not want to use the GUI, there are only two additional maps you must learn (these are configurable via your vimrc if needed).  The purpose of the yankring is to gain access to previously yanked (or deleted) elements.  The YRReplace command will replace the previously pasted text with a different entry from the yankring.  By default, I choose <C-P> (P for previous) to replace the text last pasted while moving backwards through your previous text from the yankring and <C-N> (N for next) to replace the previous paste while moving forward through the yankring.\r\n\r\nA separate buffer window to allow you to easily interact with the contents of the yankring.  The window is similar to many other plugins: TagList, SelectBuf and so on.  You can use the mouse or standard Vim keys (p, gp, P, ...).  Visual mode is used to support counts, pasting multiple times and reversing the order of pasted elements.\r\n\r\nThe GUI significantly simplifies your interaction with the yankring for basic functions.  But often it useful to take advantage of the more powerful features of the yankring.\r\n\r\nHere is a small section from the tutorial (using maps) so you have some idea of how you interact with the plugin gaining access to previous yanks.  Using the GUI for basic operations is self explanatory.\r\n\r\n:h yankring-tutorial\r\n\r\n---- Partial Tutorial ----\r\nTo understand how to use the yankring, the following example should demonstrate the various features.\r\n\r\nAssume we have this buffer: \r\n        one\r\n        two\r\n        three\r\n        four\r\n        five\r\n\r\nNow yank (yy) each line separately starting at line 1.  Display the\r\ncontents of the yankring. \r\n        :YRShow  \r\n            --- YankRing ---\r\n            Elem  Content\r\n            5     five^@\r\n            4     four^@\r\n            3     three^@\r\n            2     two^@\r\n            1     one^@\r\nSince we yanked the text starting at line 1 and finishing at line 5, the most current yankring element is the last one, the contents of line 5.  \r\n\"five^@\" is displayed, the \"^@\" is a newline character (since we issued a \"yy\").\r\n\r\nNow, go to the end of the file and press p.  The resulting buffer appears as: \r\n        one\r\n        two\r\n        three\r\n        four\r\n        five\r\n        five\r\nNow press <C-P> to move backwards through the yankring, this results in: \r\n        one\r\n        two\r\n        three\r\n        four\r\n        five\r\n        four\r\nNow press 2<C-P>.  This would be the same as pressing <C-P> two times in a row.  This results in: \r\n        one\r\n        two\r\n        three\r\n        four\r\n        five\r\n        two\r\nNow press <C-N> to move forwards through the yankring, this results in: \r\n        one\r\n        two\r\n        three\r\n        four\r\n        five\r\n        three\r\n\r\nYou can create a map to display a buffer displaying the yankring's contents:\r\n    nnoremap <silent> <F11> :YRShow<CR>\r\n\r\nYRShow creates a new split buffer (you can configure where it should be and it's size)\r\n        :YRShow  \r\n            AutoClose=1;Cmds:<enter>,[g]p,[p]P,d,r,a,u,q,<space>;Help=?\r\n            --- YankRing ---\r\n            Elem  Content\r\n            3     three^@\r\n            2     two^@\r\n            1     one^@\r\n            5     five^@\r\n            4     four^@\r\nYou can simply hit \"p\", <enter>, double click on an item and it will be pasted into your document.  The window will automatically close (by default) after you have made a choice.  The element will be pasted into the correct buffer if you have multiple split windows.\r\n\r\nYou can paste multiple items using visual mode.\r\nYou can also remove items from the yankring.\r\n\r\n---- Partial Tutorial ----\r\n\r\nConcentrating on the last line of the buffer you could see how we were able to replace our pasted text with lines yanked previously.  This is a feature Vim only has for deletes, and is limited to 9.  This plugin enables the same features for both yanks, deletes and changes, the size of the history is configurable.\r\n\r\n\r\n\r\n","install_details":"YankRing 4.0 and above, uses new features of Vim 7.2 which allows it to support all motions and text-objects Vim provides.  \r\nIf you are using Vim 7.1 or below it will still work as it did in previous versions.\r\nYankRing 3.0, Vim 7 is required.\r\nYankRing 2.2 requires Vim 6.2 or higher.\r\n\r\nCopy the yankring.vim script to your $HOME\/.vim\/plugin (or $VIM\/vimfiles\/plugin for windows) directory.  \r\nCopy yankring.txt to your $HOME\/.vim\/doc (or $VIM\/vimfiles\/doc for windows) directory.\r\n\r\nTo update the Vim Help, run:\r\n:helptags $HOME\/.vim\/doc  (Unix)\r\n:helptags $VIM\/vimfiles\/doc  (Windows) ","5":"YankRing 4.0 and above, uses new features of Vim 7.2 which allows it to support all motions and text-objects Vim provides.  \r\nIf you are using Vim 7.1 or below it will still work as it did in previous versions.\r\nYankRing 3.0, Vim 7 is required.\r\nYankRing 2.2 requires Vim 6.2 or higher.\r\n\r\nCopy the yankring.vim script to your $HOME\/.vim\/plugin (or $VIM\/vimfiles\/plugin for windows) directory.  \r\nCopy yankring.txt to your $HOME\/.vim\/doc (or $VIM\/vimfiles\/doc for windows) directory.\r\n\r\nTo update the Vim Help, run:\r\n:helptags $HOME\/.vim\/doc  (Unix)\r\n:helptags $VIM\/vimfiles\/doc  (Windows) ","first_name":"David","6":"David","last_name":"Fishburn","7":"Fishburn","releases":[{"0":"1234","vim_version":"7.0","1":"7.0","script_version":"20.0","2":"20.0","version_comment":"NF: YankRing uses new Vim 8.1 TextYankPost event which allows the removal of quite a few normal mode maps.\r\n\r\nNF: All YankRing maps now use <unique>.  If a mapping already exists Vim will report an error.  Now the user will know if there are conflicts. (tenfyzhong, pull #12)\r\n\r\nNF: New option g:yankring_paste_visual_reset_default_register default(0).  When in visual mode and we are pasting text from the default register, the default register gets replaced with the overwritten text.  This option will put the contents that were just pasted back into the default register.  This will allow you to paste multiple times in visual mode without having to use the YankRing replace feature.\r\n","3":"NF: YankRing uses new Vim 8.1 TextYankPost event which allows the removal of quite a few normal mode maps.\r\n\r\nNF: All YankRing maps now use <unique>.  If a mapping already exists Vim will report an error.  Now the user will know if there are conflicts. (tenfyzhong, pull #12)\r\n\r\nNF: New option g:yankring_paste_visual_reset_default_register default(0).  When in visual mode and we are pasting text from the default register, the default register gets replaced with the overwritten text.  This option will put the contents that were just pasted back into the default register.  This will allow you to paste multiple times in visual mode without having to use the YankRing replace feature.\r\n","package":"yankring_200.zip","4":"yankring_200.zip","src_id":"26344","5":"26344","creation_date":"1547376712","6":"1547376712"},{"0":"1234","vim_version":"7.0","1":"7.0","script_version":"19.0","2":"19.0","version_comment":"Mostly documentation updates.","3":"Mostly documentation updates.","package":"yankring_190.zip","4":"yankring_190.zip","src_id":"23487","5":"23487","creation_date":"1438015904","6":"1438015904"},{"0":"1234","vim_version":"7.0","1":"7.0","script_version":"18.0","2":"18.0","version_comment":"NF: Handle the @: command (Lingnan Dai).\r\n\r\nNF: Added new global option to specify the YankRing buffer name, g:yankring_buffer_name (\u00c5\u00a0tefan Sakal\u00c3\u00adk).\r\n\r\nBF: Did not properly highlight new commands in the YankRing window (Thilo Six).\r\n","3":"NF: Handle the @: command (Lingnan Dai).\r\n\r\nNF: Added new global option to specify the YankRing buffer name, g:yankring_buffer_name (\u00c5\u00a0tefan Sakal\u00c3\u00adk).\r\n\r\nBF: Did not properly highlight new commands in the YankRing window (Thilo Six).\r\n","package":"yankring_180.zip","4":"yankring_180.zip","src_id":"20842","5":"20842","creation_date":"1380067560","6":"1380067560"},{"0":"1234","vim_version":"7.0","1":"7.0","script_version":"17.0","2":"17.0","version_comment":"NF: The yankring_history_dir option can now take a comma separated list.  First valid directory found will be used (Alex Bel).\r\n\r\nNF: YankRing can now monitor inserted text and place it in the ring. This is disabled by default, but can be enabled either through the YankRing window or via your .vimrc using the new option:\r\n    g:yankring_record_insert = 1 (Alexandre Viau).\r\n\r\nBF: When g:yankring_persist = 0, the YankRing was still reading and writing to the yankring file (Vladimir Marek).\r\n\r\nBF: The YankRing menu entry, \"Replace with Next\", was performing the \"Replace with Previous\" action (Thilo Six).\r\n","3":"NF: The yankring_history_dir option can now take a comma separated list.  First valid directory found will be used (Alex Bel).\r\n\r\nNF: YankRing can now monitor inserted text and place it in the ring. This is disabled by default, but can be enabled either through the YankRing window or via your .vimrc using the new option:\r\n    g:yankring_record_insert = 1 (Alexandre Viau).\r\n\r\nBF: When g:yankring_persist = 0, the YankRing was still reading and writing to the yankring file (Vladimir Marek).\r\n\r\nBF: The YankRing menu entry, \"Replace with Next\", was performing the \"Replace with Previous\" action (Thilo Six).\r\n","package":"yankring_170.zip","4":"yankring_170.zip","src_id":"19967","5":"19967","creation_date":"1367190292","6":"1367190292"},{"0":"1234","vim_version":"7.0","1":"7.0","script_version":"16.0","2":"16.0","version_comment":"BF: YankRing could report \"YR: A register cannot be specified in replace mode\" when using clipboard = unnamed or unnamedplus.  This can often happen when fetching previous values from the YankRing (i.e. <C-N> or <C-P>).","3":"BF: YankRing could report \"YR: A register cannot be specified in replace mode\" when using clipboard = unnamed or unnamedplus.  This can often happen when fetching previous values from the YankRing (i.e. <C-N> or <C-P>).","package":"yankring_160.zip","4":"yankring_160.zip","src_id":"19401","5":"19401","creation_date":"1358712962","6":"1358712962"},{"0":"1234","vim_version":"7.0","1":"7.0","script_version":"15.0","2":"15.0","version_comment":"NF: Automatically turn off relativenumber for the YankRing window (Emma Tramp).\r\n\r\nNF: The YankRing window supports 1-9 to choose to paste those items for quicker access to the top 9 items.\r\n\r\nBF: When re-executing a macro using @<letter> and the macro used f, F, t, T, a \"Press ENTER to continue\" prompt was displayed (Greg Sexton).\r\n\r\nBF: Some documentation updates and script tweaks (Dominique Pell\u00c3\u00a9).\r\n\r\nBF: The 0 register was updated during delete operations (Christian Brabandt).\r\n\r\nBF: When running a macro (@a), pressing @ displays a YankRing prompt (YR:Enter character:) to choose which macro name to run.  This prompt was displayed twice leading to a \"Press ENTER or type command to continue\" Vim message.  This change suppresses the \"Press ENTER\" message (Greg Sexton).\r\n\r\nBF: The YankRing prevented you from re-running the last macro using @@.\r\n\r\nBF: YRToggle (to disable \/ enable the YankRing) did not unmap @.\r\n\r\nBF: When prompted for a macro to run, if an invalid value was provided, Vim could report \"E354: Invalid register name\".\r\n\r\nBF: When using a Vim instance with < 80 columns and using a horizontal YankRing window after opening and closing the YankRing window the Vim window did not shrink back to its original size (Eric Weir).\r\n\r\nBF: Updated documented values of yankring_window_height and yankring_window_width (Paul).\r\n\r\nBF: It was not possible to paste from the * register if the clipboard option contains unnamedplus before unnamed (Marcin Szamotulski).\r\n","3":"NF: Automatically turn off relativenumber for the YankRing window (Emma Tramp).\r\n\r\nNF: The YankRing window supports 1-9 to choose to paste those items for quicker access to the top 9 items.\r\n\r\nBF: When re-executing a macro using @<letter> and the macro used f, F, t, T, a \"Press ENTER to continue\" prompt was displayed (Greg Sexton).\r\n\r\nBF: Some documentation updates and script tweaks (Dominique Pell\u00c3\u00a9).\r\n\r\nBF: The 0 register was updated during delete operations (Christian Brabandt).\r\n\r\nBF: When running a macro (@a), pressing @ displays a YankRing prompt (YR:Enter character:) to choose which macro name to run.  This prompt was displayed twice leading to a \"Press ENTER or type command to continue\" Vim message.  This change suppresses the \"Press ENTER\" message (Greg Sexton).\r\n\r\nBF: The YankRing prevented you from re-running the last macro using @@.\r\n\r\nBF: YRToggle (to disable \/ enable the YankRing) did not unmap @.\r\n\r\nBF: When prompted for a macro to run, if an invalid value was provided, Vim could report \"E354: Invalid register name\".\r\n\r\nBF: When using a Vim instance with < 80 columns and using a horizontal YankRing window after opening and closing the YankRing window the Vim window did not shrink back to its original size (Eric Weir).\r\n\r\nBF: Updated documented values of yankring_window_height and yankring_window_width (Paul).\r\n\r\nBF: It was not possible to paste from the * register if the clipboard option contains unnamedplus before unnamed (Marcin Szamotulski).\r\n","package":"yankring_150.zip","4":"yankring_150.zip","src_id":"19300","5":"19300","creation_date":"1357170043","6":"1357170043"},{"0":"1234","vim_version":"7.0","1":"7.0","script_version":"14.0","2":"14.0","version_comment":"NF: The YankRing window supports 1-9 to choose to paste those items for quicker access to the top 9 items.\r\nNF: The YankRing now maps the @ key to run macros.  Not all actions performed during the macro are recorded by the YankRing as a number of items had to be unmapped to support the replay of actions which can prompt the user for input (i.e. t and f) (Asis Hallab).\r\nBF: When flipping between applications the system clipboard was not added to the YankRing in all cases.\r\nBF: The YankRing could report E121: Undefined variable: g:yankring_manual_clipboard_check (Thilo Six).\r\nBF: The YankRing could report: E132: Function call depth is higher than 'maxfuncdepth'.  When executing a YRClear or YRPop or when flipping between applications (Marcin Szamotulski).\r\nBF: Strange behaviour when opening the YankRing with :e [YankRing] instead of :YRShow (Marcin Szamotulski).\r\n","3":"NF: The YankRing window supports 1-9 to choose to paste those items for quicker access to the top 9 items.\r\nNF: The YankRing now maps the @ key to run macros.  Not all actions performed during the macro are recorded by the YankRing as a number of items had to be unmapped to support the replay of actions which can prompt the user for input (i.e. t and f) (Asis Hallab).\r\nBF: When flipping between applications the system clipboard was not added to the YankRing in all cases.\r\nBF: The YankRing could report E121: Undefined variable: g:yankring_manual_clipboard_check (Thilo Six).\r\nBF: The YankRing could report: E132: Function call depth is higher than 'maxfuncdepth'.  When executing a YRClear or YRPop or when flipping between applications (Marcin Szamotulski).\r\nBF: Strange behaviour when opening the YankRing with :e [YankRing] instead of :YRShow (Marcin Szamotulski).\r\n","package":"yankring_140.zip","4":"yankring_140.zip","src_id":"17721","5":"17721","creation_date":"1333593875","6":"1333593875"},{"0":"1234","vim_version":"7.0","1":"7.0","script_version":"13.0","2":"13.0","version_comment":"NF: [p, ]p, [P, ]P are now supported within the YankRing window (Alexandre Provencio).\r\n\r\nNF: When using the console version of Vim the yankring was not detecting the \"+ register automatically as the FocusGained event does not fire in console mode.  When new elements are added or the YankRing is shown the clipboard will be checked for new values (Giuseppe Rota).\r\n\r\nNF: Added a new option, g:yankring_manual_clipboard_check which when enabled will manually check for clipboard changes at certain times within the YankRing.  This option is not used if the GUI is running as the FocusGained will perform checks at appropriate times (Erik Westrup).\r\n\r\nBF: With clipboard=unnamed replacing the previous paste with a different value from the YankRing did not work in all cases (Chris Lott).\r\n\r\nBF: Under certain conditions the YankRing would still check the system clipboard even if g:yankring_clipboard_monitor == 0.  This can lead to delays when attempting to access the clipboard when running in console mode.  Starting Vim with the -X switch removes the delay (Erik Westrup).\r\n\r\nBF: Incorrect syntax setting cpoptions (Thilo Six).\r\n","3":"NF: [p, ]p, [P, ]P are now supported within the YankRing window (Alexandre Provencio).\r\n\r\nNF: When using the console version of Vim the yankring was not detecting the \"+ register automatically as the FocusGained event does not fire in console mode.  When new elements are added or the YankRing is shown the clipboard will be checked for new values (Giuseppe Rota).\r\n\r\nNF: Added a new option, g:yankring_manual_clipboard_check which when enabled will manually check for clipboard changes at certain times within the YankRing.  This option is not used if the GUI is running as the FocusGained will perform checks at appropriate times (Erik Westrup).\r\n\r\nBF: With clipboard=unnamed replacing the previous paste with a different value from the YankRing did not work in all cases (Chris Lott).\r\n\r\nBF: Under certain conditions the YankRing would still check the system clipboard even if g:yankring_clipboard_monitor == 0.  This can lead to delays when attempting to access the clipboard when running in console mode.  Starting Vim with the -X switch removes the delay (Erik Westrup).\r\n\r\nBF: Incorrect syntax setting cpoptions (Thilo Six).\r\n","package":"yankring_130.zip","4":"yankring_130.zip","src_id":"17538","5":"17538","creation_date":"1330399576","6":"1330399576"},{"0":"1234","vim_version":"7.0","1":"7.0","script_version":"12.0","2":"12.0","version_comment":"NF: Added support for the clipboard option \"unnamedplus\" which was added after 7.3 (Hong Xu).\r\n\r\nNF: When displaying the YankRing using YRShow, a new command \"R\" has been added to display all of Vim's registers [0-9a-z].\r\n\r\nBF: YRMapsDelete did not remove the normal mode @ map, which interfers with recorded macros (Philippe Vaucher ).\r\n","3":"NF: Added support for the clipboard option \"unnamedplus\" which was added after 7.3 (Hong Xu).\r\n\r\nNF: When displaying the YankRing using YRShow, a new command \"R\" has been added to display all of Vim's registers [0-9a-z].\r\n\r\nBF: YRMapsDelete did not remove the normal mode @ map, which interfers with recorded macros (Philippe Vaucher ).\r\n","package":"yankring_120.zip","4":"yankring_120.zip","src_id":"16536","5":"16536","creation_date":"1316220010","6":"1316220010"},{"0":"1234","vim_version":"7.0","1":"7.0","script_version":"11.0","2":"11.0","version_comment":"NF: Documented the global variables to customize the location of the YankRing menu.\r\n\r\nNF: The YankRing menu now shows the maps used for the default actions to help learn them more easily.\r\n\r\nNF: Added g:yankring_menu_root and g:yankring_menu_priority (David Barsam).\r\n\r\nNF: Added a warning indicating a stored value has been truncated based on g:yankring_max_element_length and a new option to suppress this warning, g:yankring_warn_on_truncate (Hans-G\u00c3\u00bcnter).\r\n\r\nBF: The YRAfterMaps() function (if it exists) was not re-run if YRToggle was used to disable and enable the YankRing.\r\n\r\nBF: Multibyte strings may not have been pasted correctly (Dr. Chip).\r\n\r\nBF: When pasting a string of 1111's, and additional -1 could also be included in the output.\r\n","3":"NF: Documented the global variables to customize the location of the YankRing menu.\r\n\r\nNF: The YankRing menu now shows the maps used for the default actions to help learn them more easily.\r\n\r\nNF: Added g:yankring_menu_root and g:yankring_menu_priority (David Barsam).\r\n\r\nNF: Added a warning indicating a stored value has been truncated based on g:yankring_max_element_length and a new option to suppress this warning, g:yankring_warn_on_truncate (Hans-G\u00c3\u00bcnter).\r\n\r\nBF: The YRAfterMaps() function (if it exists) was not re-run if YRToggle was used to disable and enable the YankRing.\r\n\r\nBF: Multibyte strings may not have been pasted correctly (Dr. Chip).\r\n\r\nBF: When pasting a string of 1111's, and additional -1 could also be included in the output.\r\n","package":"yankring_110.zip","4":"yankring_110.zip","src_id":"13554","5":"13554","creation_date":"1281573562","6":"1281573562"},{"0":"1234","vim_version":"7.0","1":"7.0","script_version":"10.0","2":"10.0","version_comment":"NF: Change the buffer name to [YankRing] to resemble other non-user buffers.\r\n\r\nNF: Added g:yankring_min_element_length which can prevent items from being added to the YankRing if they are too small.  For example, single character deletes (Vedran M).\r\n\r\nBF: When shifting focus back to Vim, the YankRing may incorrectly report: \"YR:Failed to change to the yankring buffer, please contact author\".\r\n\r\nBF: When entering Vim for the first time and hitting \"p\" nothing was pasted (Mark Huiskes).\r\n\r\nBF: When entering Vim for the first time and the yankring_clipboard_monitor = 1, the clipboard entry was not automatically added to the yankring.\r\n\r\nBF: When overriding the default and setting g:yankring_window_use_bottom = 0, the YankRing would report the error (Sergey Khorev):  E21: Cannot make changes, 'modifiable' is off\r\n","3":"NF: Change the buffer name to [YankRing] to resemble other non-user buffers.\r\n\r\nNF: Added g:yankring_min_element_length which can prevent items from being added to the YankRing if they are too small.  For example, single character deletes (Vedran M).\r\n\r\nBF: When shifting focus back to Vim, the YankRing may incorrectly report: \"YR:Failed to change to the yankring buffer, please contact author\".\r\n\r\nBF: When entering Vim for the first time and hitting \"p\" nothing was pasted (Mark Huiskes).\r\n\r\nBF: When entering Vim for the first time and the yankring_clipboard_monitor = 1, the clipboard entry was not automatically added to the yankring.\r\n\r\nBF: When overriding the default and setting g:yankring_window_use_bottom = 0, the YankRing would report the error (Sergey Khorev):  E21: Cannot make changes, 'modifiable' is off\r\n","package":"yankring_100.zip","4":"yankring_100.zip","src_id":"12258","5":"12258","creation_date":"1264995064","6":"1264995064"},{"0":"1234","vim_version":"7.0","1":"7.0","script_version":"9.0","2":"9.0","version_comment":"BF: You cannot execute a macro with \":normal @a\".  It is still not possible, but you can execute it with \":normal! @a\" (A S Budden).  \r\nBF: When g:yankring_persist = 0 the YankRing could go into an infinite loop (A S Budden).  \r\nBF: When replaying a macro which used any of the zap keys (f,F,t,T,\/,?) you were prompted again for the string to match on (Ovidiu C).\r\nBF: When checking the clipboard for changes (g:yankring_clipboard_monitor == 1) only add the item if it is not already in the ring.  Previously, the item was moved to the top of the YankRing each time you flipped focus.\r\n","3":"BF: You cannot execute a macro with \":normal @a\".  It is still not possible, but you can execute it with \":normal! @a\" (A S Budden).  \r\nBF: When g:yankring_persist = 0 the YankRing could go into an infinite loop (A S Budden).  \r\nBF: When replaying a macro which used any of the zap keys (f,F,t,T,\/,?) you were prompted again for the string to match on (Ovidiu C).\r\nBF: When checking the clipboard for changes (g:yankring_clipboard_monitor == 1) only add the item if it is not already in the ring.  Previously, the item was moved to the top of the YankRing each time you flipped focus.\r\n","package":"yankring_90.zip","4":"yankring_90.zip","src_id":"11289","5":"11289","creation_date":"1251595581","6":"1251595581"},{"0":"1234","vim_version":"7.0","1":"7.0","script_version":"8.0","2":"8.0","version_comment":"NF: Changed the implementation of YRGetSearch() (David Liang).\r\nBF: Under some unknown circumstances, the yankring can fail to change to the correct buffer.  Put in code to double check and abort.\r\nBF: Yanking and pasting a line which ends in a backslash resulted in the backslash being replaced by \"@@@\".\r\nBF: When repeating a command (\".\") which used any of the zap keys (f,F,t,T,\/,?) you were prompted again for the string to match on (Vasilii Pascal).\r\n","3":"NF: Changed the implementation of YRGetSearch() (David Liang).\r\nBF: Under some unknown circumstances, the yankring can fail to change to the correct buffer.  Put in code to double check and abort.\r\nBF: Yanking and pasting a line which ends in a backslash resulted in the backslash being replaced by \"@@@\".\r\nBF: When repeating a command (\".\") which used any of the zap keys (f,F,t,T,\/,?) you were prompted again for the string to match on (Vasilii Pascal).\r\n","package":"yankring_80.zip","4":"yankring_80.zip","src_id":"9731","5":"9731","creation_date":"1230607529","6":"1230607529"},{"0":"1234","vim_version":"7.0","1":"7.0","script_version":"7.0","2":"7.0","version_comment":"NF: Added support for the \/ and ? motions so that y\/search is supported (Vasilii Pascal).\r\nNF: When the YankRing window is displayed (or updated) an additional check is made against the default register.  If it has changed since the YankRing recorded it, the value will be added to the history.\r\nNF: Added support for more motions h, j, k, l, H, M, L, ^, 0, -, +, _.  And a pile of g motions g_, g^, gm, g$, gk, gj, gg, ge, gE.\r\nNF: The YankRing window will display a message it is operating in a limited mode if not using Vim 7.2 or the correct patch level.\r\nBF: Correction to some internal code which could lead to an endless loop (John Beckett).\r\nBF: Opening and closing the YankRing window with \"set report=0\" reported \"1 line less\" messages (Bill McCarthy).\r\nBF: Changed the default value of g:yankring_paste_check_default_buffer to check if the default paste buffer has changed when pressing 'p'.  For example, if a plugin has changed the default registers it will be pasted rather than the top item from the YankRing.\r\nBF: YRMapsDelete did not remove all the maps created by the YankRing.\r\nBF: Under particular circumstances, yanking text with embedded @ characters were not properly stored and retrieved from the YankRing (Andrew Long).\r\nBF: Changed to use xmaps instead of vmaps so that the maps only work in visual mode and not select mode (David Liang).\r\n","3":"NF: Added support for the \/ and ? motions so that y\/search is supported (Vasilii Pascal).\r\nNF: When the YankRing window is displayed (or updated) an additional check is made against the default register.  If it has changed since the YankRing recorded it, the value will be added to the history.\r\nNF: Added support for more motions h, j, k, l, H, M, L, ^, 0, -, +, _.  And a pile of g motions g_, g^, gm, g$, gk, gj, gg, ge, gE.\r\nNF: The YankRing window will display a message it is operating in a limited mode if not using Vim 7.2 or the correct patch level.\r\nBF: Correction to some internal code which could lead to an endless loop (John Beckett).\r\nBF: Opening and closing the YankRing window with \"set report=0\" reported \"1 line less\" messages (Bill McCarthy).\r\nBF: Changed the default value of g:yankring_paste_check_default_buffer to check if the default paste buffer has changed when pressing 'p'.  For example, if a plugin has changed the default registers it will be pasted rather than the top item from the YankRing.\r\nBF: YRMapsDelete did not remove all the maps created by the YankRing.\r\nBF: Under particular circumstances, yanking text with embedded @ characters were not properly stored and retrieved from the YankRing (Andrew Long).\r\nBF: Changed to use xmaps instead of vmaps so that the maps only work in visual mode and not select mode (David Liang).\r\n","package":"yankring_70.zip","4":"yankring_70.zip","src_id":"9504","5":"9504","creation_date":"1226716313","6":"1226716313"},{"0":"1234","vim_version":"7.0","1":"7.0","script_version":"6.1","2":"6.1","version_comment":"BF: If the g:yankring_history_dir contains spaces (default on Windows) an error was reported.  A simple work around was to let g:yankring_history_dir = 'c:\\Vim' or no spaces (Matt).  \r\nAll Windows users should download this version.\r\n","3":"BF: If the g:yankring_history_dir contains spaces (default on Windows) an error was reported.  A simple work around was to let g:yankring_history_dir = 'c:\\Vim' or no spaces (Matt).  \r\nAll Windows users should download this version.\r\n","package":"yankring_61.zip","4":"yankring_61.zip","src_id":"9421","5":"9421","creation_date":"1225457192","6":"1225457192"},{"0":"1234","vim_version":"7.0","1":"7.0","script_version":"6.0","2":"6.0","version_comment":"NF: The YankRing now maintains the history in a file.  This means if you are running multiple instances of Vim, they all see the same yankring whether you are using X, Windows, SSH or Screen.\r\nNF: The location and name of the file is configurable by the user.\r\nNF: The g:yankring_separator is no longer used and has been removed.\r\nNF: The g:yankring_max_element_length can be used to limit the size of an element in the yankring.\r\nNF: The g:yankring_share_between_instances can be used to indicate whether each instance of Vim running on a machine should share the history file or whether each should have their own individual history file.\r\nNF: The g:yankring_clipboard_monitor can be used to indicate whether changes to the system clipboard should be added to the YankRing (default is on).\r\nNF: The YankRing window can toggle the clipboard monitor by pressing 'c'.  See the help in the window by pressing ?.\r\nNF: Added some highlighting to the YankRing window (Marty Grenfell).\r\n","3":"NF: The YankRing now maintains the history in a file.  This means if you are running multiple instances of Vim, they all see the same yankring whether you are using X, Windows, SSH or Screen.\r\nNF: The location and name of the file is configurable by the user.\r\nNF: The g:yankring_separator is no longer used and has been removed.\r\nNF: The g:yankring_max_element_length can be used to limit the size of an element in the yankring.\r\nNF: The g:yankring_share_between_instances can be used to indicate whether each instance of Vim running on a machine should share the history file or whether each should have their own individual history file.\r\nNF: The g:yankring_clipboard_monitor can be used to indicate whether changes to the system clipboard should be added to the YankRing (default is on).\r\nNF: The YankRing window can toggle the clipboard monitor by pressing 'c'.  See the help in the window by pressing ?.\r\nNF: Added some highlighting to the YankRing window (Marty Grenfell).\r\n","package":"yankring_60.zip","4":"yankring_60.zip","src_id":"9415","5":"9415","creation_date":"1225329523","6":"1225329523"},{"0":"1234","vim_version":"7.0","1":"7.0","script_version":"5.0","2":"5.0","version_comment":"NF: The yankring can recognize certain Vim commands which do not change the contents of a buffer and not attempt to capture it.\r\nNF: The global variables which allow you to customize the behaviour are now space separated instead of comma separated.  This provides greater flexibility but will require you to modify your vimrc (if you have customized it). (Andy Wokula)\r\nBF: If using <C-O> from within insert mode, the yankring inserted characters into the buffer instead of capturing the changes, this was fixed by Andy Wokula (Agathoklis Hatzimanikas).\r\nBF: The yankring did not properly account for all the different forms of counts \"5yy\" worked but \"y5y\" did not (Edwin Shao).\r\n","3":"NF: The yankring can recognize certain Vim commands which do not change the contents of a buffer and not attempt to capture it.\r\nNF: The global variables which allow you to customize the behaviour are now space separated instead of comma separated.  This provides greater flexibility but will require you to modify your vimrc (if you have customized it). (Andy Wokula)\r\nBF: If using <C-O> from within insert mode, the yankring inserted characters into the buffer instead of capturing the changes, this was fixed by Andy Wokula (Agathoklis Hatzimanikas).\r\nBF: The yankring did not properly account for all the different forms of counts \"5yy\" worked but \"y5y\" did not (Edwin Shao).\r\n","package":"yankring_50.zip","4":"yankring_50.zip","src_id":"9263","5":"9263","creation_date":"1222052629","6":"1222052629"},{"0":"1234","vim_version":"7.0","1":"7.0","script_version":"4.1","2":"4.1","version_comment":"NF: The yankring now allows you to override which operators should be ignored (yankring_ignore_operator).  By default this is set for the standard Vim operators which do not modify any registers (Examples: = and gu) (Andy Wokula).\r\nNF: The yankring did not map v_x (Matt Tolton).\r\nBF: The expression register (quote=) was not accounted for correctly (Agathoklis Hatzimanikas).\r\nBF: Using the v:operator variable must be escaped when used in a regular expression.\r\n","3":"NF: The yankring now allows you to override which operators should be ignored (yankring_ignore_operator).  By default this is set for the standard Vim operators which do not modify any registers (Examples: = and gu) (Andy Wokula).\r\nNF: The yankring did not map v_x (Matt Tolton).\r\nBF: The expression register (quote=) was not accounted for correctly (Agathoklis Hatzimanikas).\r\nBF: Using the v:operator variable must be escaped when used in a regular expression.\r\n","package":"yankring_41.zip","4":"yankring_41.zip","src_id":"9098","5":"9098","creation_date":"1218310689","6":"1218310689"},{"0":"1234","vim_version":"7.0","1":"7.0","script_version":"4.0","2":"4.0","version_comment":"NF: The yankring by default now captures all |text-objects| and all motions (|motion.txt|) which Vim supports.  Version 3.0 only supported a subset of the basic motion commands.\r\nNF: Prior to this version only predefined maps triggered the capture of data into the yankring.  These maps only supported yanks and deletes.  The yankring now also supports operator-pending mode, which allows a greater range of operations to be automatically captured and added to the yankring.  \r\nOperating pending mode functionality requires Vim 7.2 or Vim 7.1 with patch #205.  If using Vim 7.1 you can determine this with: \r\n       echo has(\"patch205\")\r\nNF: Prior to this version only yanks and deletes were registered in the yankring.  Changes are now also captured into the yankring.\r\nNF: The yankring will also capture the system cliboard when focus is returned to the vim window.  This is useful if you copy text between applications.\r\nNF: The yankring window always opened bottom horizontal.  Now it can be opened top or bottom and horizontal or vertically.  This can be controlled via variables in your .vimrc.\r\nBF: The yankring has an option to persist between instances of Vim by storing the values in global variables within the viminfo.  This has led to some unusual ordering of items in the ring from conflicts between instances.  This option has been turn off by default.\r\nBF: Their was an issue with yanking using y$.\r\n","3":"NF: The yankring by default now captures all |text-objects| and all motions (|motion.txt|) which Vim supports.  Version 3.0 only supported a subset of the basic motion commands.\r\nNF: Prior to this version only predefined maps triggered the capture of data into the yankring.  These maps only supported yanks and deletes.  The yankring now also supports operator-pending mode, which allows a greater range of operations to be automatically captured and added to the yankring.  \r\nOperating pending mode functionality requires Vim 7.2 or Vim 7.1 with patch #205.  If using Vim 7.1 you can determine this with: \r\n       echo has(\"patch205\")\r\nNF: Prior to this version only yanks and deletes were registered in the yankring.  Changes are now also captured into the yankring.\r\nNF: The yankring will also capture the system cliboard when focus is returned to the vim window.  This is useful if you copy text between applications.\r\nNF: The yankring window always opened bottom horizontal.  Now it can be opened top or bottom and horizontal or vertically.  This can be controlled via variables in your .vimrc.\r\nBF: The yankring has an option to persist between instances of Vim by storing the values in global variables within the viminfo.  This has led to some unusual ordering of items in the ring from conflicts between instances.  This option has been turn off by default.\r\nBF: Their was an issue with yanking using y$.\r\n","package":"yankring_40.zip","4":"yankring_40.zip","src_id":"8849","5":"8849","creation_date":"1214331309","6":"1214331309"},{"0":"1234","vim_version":"7.0","1":"7.0","script_version":"3.0","2":"3.0","version_comment":"NF: Converted the yankring to use the new Vim7's List object which means it is no longer compatible with Vim6.\r\nNF: By default the yankring will now maintain the yankring's items persistently by default.  It does this via the |viminfo| file. This means the contents of the yankring rely on the internal variables of only 1 Vim instance.\r\nBF: YRToggle was not unmapping 'gp' and 'gP'.\r\nBF: YRSearch prompted the user for a regex even if one was provided on the command line.\r\nBF: If g:yankring_manage_numbered_reg is enabled, the \".\" operator did not correctly repeat the previous action (Pedro DeRose).","3":"NF: Converted the yankring to use the new Vim7's List object which means it is no longer compatible with Vim6.\r\nNF: By default the yankring will now maintain the yankring's items persistently by default.  It does this via the |viminfo| file. This means the contents of the yankring rely on the internal variables of only 1 Vim instance.\r\nBF: YRToggle was not unmapping 'gp' and 'gP'.\r\nBF: YRSearch prompted the user for a regex even if one was provided on the command line.\r\nBF: If g:yankring_manage_numbered_reg is enabled, the \".\" operator did not correctly repeat the previous action (Pedro DeRose).","package":"yankring_30.zip","4":"yankring_30.zip","src_id":"7629","5":"7629","creation_date":"1189196848","6":"1189196848"},{"0":"1234","vim_version":"6.0","1":"6.0","script_version":"2.2","2":"2.2","version_comment":"BF: If you pressed '?' to toggle the display of the help in the\r\nyankring window, the yankring window would close.  This also applied to\r\n'a', which allowed you to toggle the autoclose feature.","3":"BF: If you pressed '?' to toggle the display of the help in the\r\nyankring window, the yankring window would close.  This also applied to\r\n'a', which allowed you to toggle the autoclose feature.","package":"yankring_22.zip","4":"yankring_22.zip","src_id":"4692","5":"4692","creation_date":"1129895617","6":"1129895617"},{"0":"1234","vim_version":"6.0","1":"6.0","script_version":"2.1","2":"2.1","version_comment":"NF: Much improved usability, the yankring now has a \"GUI\" to service \r\n    the yankring.  If YRShow or YRSearch is used, a split buffer is\r\n    opened which displays all the elements in the yankring.  There\r\n    are a number of maps that allow you to interact with the\r\n    contents.  The window can be positioned vertically or\r\n    horizontally as well as being sized all through options \r\n    specified in your vimrc.\r\nNF: Added the ability for the yankring to override Vim's numbered \r\n    registers.  Instead of the numbered registers holding the last\r\n    yanked value, and the 9 previous deletes, they will now reflect\r\n    the top 10 items in the yankring.  This allows you to reference\r\n    them directly with \"5p.\r\nNF: YRPop can now delete any items from the yankring, rather \r\n    that just from the top.\r\nNF: YRSetTop has been removed, it is no longer required as the\r\n    internal representation of the yankring has changed.\r\nBF: If g:yankring_ignore_duplicate is set (which is the default)\r\n    you could get some unpredicable results when moving \r\n    backwards and forwards (<C-P> and <C-N>) through the \r\n    previous values.\r\n","3":"NF: Much improved usability, the yankring now has a \"GUI\" to service \r\n    the yankring.  If YRShow or YRSearch is used, a split buffer is\r\n    opened which displays all the elements in the yankring.  There\r\n    are a number of maps that allow you to interact with the\r\n    contents.  The window can be positioned vertically or\r\n    horizontally as well as being sized all through options \r\n    specified in your vimrc.\r\nNF: Added the ability for the yankring to override Vim's numbered \r\n    registers.  Instead of the numbered registers holding the last\r\n    yanked value, and the 9 previous deletes, they will now reflect\r\n    the top 10 items in the yankring.  This allows you to reference\r\n    them directly with \"5p.\r\nNF: YRPop can now delete any items from the yankring, rather \r\n    that just from the top.\r\nNF: YRSetTop has been removed, it is no longer required as the\r\n    internal representation of the yankring has changed.\r\nBF: If g:yankring_ignore_duplicate is set (which is the default)\r\n    you could get some unpredicable results when moving \r\n    backwards and forwards (<C-P> and <C-N>) through the \r\n    previous values.\r\n","package":"yankring_21.zip","4":"yankring_21.zip","src_id":"4667","5":"4667","creation_date":"1129058569","6":"1129058569"},{"0":"1234","vim_version":"6.0","1":"6.0","script_version":"2.0 Beta1a","2":"2.0 Beta1a","version_comment":"Some people reported an error when selecting the first item from the yankring. ","3":"Some people reported an error when selecting the first item from the yankring. ","package":"yankring_20_beta1a.zip","4":"yankring_20_beta1a.zip","src_id":"4512","5":"4512","creation_date":"1124706425","6":"1124706425"},{"0":"1234","vim_version":"6.0","1":"6.0","script_version":"2.0 Beta1","2":"2.0 Beta1","version_comment":"Added a new split buffer that allows you to visually interact with the yankring.  This makes using it much better, no more commands you need to remember.\r\nPrevious commands are still available.  The new buffer is configurable.  Please see the tutorial for further details.\r\n\r\nFeedback is greatly appreciated.","3":"Added a new split buffer that allows you to visually interact with the yankring.  This makes using it much better, no more commands you need to remember.\r\nPrevious commands are still available.  The new buffer is configurable.  Please see the tutorial for further details.\r\n\r\nFeedback is greatly appreciated.","package":"yankring_20_beta1.zip","4":"yankring_20_beta1.zip","src_id":"4503","5":"4503","creation_date":"1124520438","6":"1124520438"},{"0":"1234","vim_version":"6.0","1":"6.0","script_version":"1.6","2":"1.6","version_comment":"NF: YRSearch is similar to YRGetElem.  Given a regular expression it will interactively display all the elements in the yankring that match the regular expression.  You can enter the number of the element to paste it.  If you have many elements within the yankring, this can help you identify them more easily.\r\nNF: Updated the default history size from 30 to 100, which is partially the reason for the YRSearch command.\r\nNF: By default it supports \"gp\" and \"gP\", in addition to \"p\" and \"P\".\r\nNF: Added support for the expression register (:h quote=).  Here is an example of how it is used:\r\n       \"=\"X\"<CR>P\r\n","3":"NF: YRSearch is similar to YRGetElem.  Given a regular expression it will interactively display all the elements in the yankring that match the regular expression.  You can enter the number of the element to paste it.  If you have many elements within the yankring, this can help you identify them more easily.\r\nNF: Updated the default history size from 30 to 100, which is partially the reason for the YRSearch command.\r\nNF: By default it supports \"gp\" and \"gP\", in addition to \"p\" and \"P\".\r\nNF: Added support for the expression register (:h quote=).  Here is an example of how it is used:\r\n       \"=\"X\"<CR>P\r\n","package":"yankring_16.zip","4":"yankring_16.zip","src_id":"4256","5":"4256","creation_date":"1115493982","6":"1115493982"},{"0":"1234","vim_version":"6.0","1":"6.0","script_version":"1.5","2":"1.5","version_comment":"NF: The yankring now respects the cpoptions setting, if 'y' is included and you press '.', the previous yank command is executed and added to the yankring.  You can also add this behaviour by setting this in your |vimrc|: \r\n       let g:yankring_dot_repeat_yank = 1\r\n\r\nNF: Duplicates will not be added to the yankring by default.  If a duplicate is found, the element will be moved to the top of the yankring.  This can be controlled by setting this in your |vimrc|: \r\n       let g:yankring_ignore_duplicate = 0 (1 is default)\r\n\r\nBF: Regression from version 1.4, the '.' operator may incorrectly insert garbage.\r\n","3":"NF: The yankring now respects the cpoptions setting, if 'y' is included and you press '.', the previous yank command is executed and added to the yankring.  You can also add this behaviour by setting this in your |vimrc|: \r\n       let g:yankring_dot_repeat_yank = 1\r\n\r\nNF: Duplicates will not be added to the yankring by default.  If a duplicate is found, the element will be moved to the top of the yankring.  This can be controlled by setting this in your |vimrc|: \r\n       let g:yankring_ignore_duplicate = 0 (1 is default)\r\n\r\nBF: Regression from version 1.4, the '.' operator may incorrectly insert garbage.\r\n","package":"yankring_15.zip","4":"yankring_15.zip","src_id":"4110","5":"4110","creation_date":"1112333274","6":"1112333274"},{"0":"1234","vim_version":"6.0","1":"6.0","script_version":"1.4","2":"1.4","version_comment":"NF: YRToggle has been updated.  If you toggle the yankring off (disable) the maps it creates are removed.  Calling YRToggle again will recreate the maps.  This truly disables the yankring, where the previous version attempted to do this via code.\r\nBF: Using the '.' operator was not corrected replaying operations that did not move text in some way (g~t_) changed the case of the text but a '.' did not replay it.\r\nBF: When replacing previously pasted text the yankring did not respect what key was used to paste the text originally.  All replaced items were pasted using 'p', even if you had originally pasted the text with 'P'.\r\n","3":"NF: YRToggle has been updated.  If you toggle the yankring off (disable) the maps it creates are removed.  Calling YRToggle again will recreate the maps.  This truly disables the yankring, where the previous version attempted to do this via code.\r\nBF: Using the '.' operator was not corrected replaying operations that did not move text in some way (g~t_) changed the case of the text but a '.' did not replay it.\r\nBF: When replacing previously pasted text the yankring did not respect what key was used to paste the text originally.  All replaced items were pasted using 'p', even if you had originally pasted the text with 'P'.\r\n","package":"yankring_14.zip","4":"yankring_14.zip","src_id":"4086","5":"4086","creation_date":"1111929330","6":"1111929330"}]},"1233":{"script_id":"1233","0":"1233","script_name":"gentypes.py","1":"gentypes.py","script_type":"utility","2":"utility","summary":"Colorize types you use while editing code (Linux)","3":"Colorize types you use while editing code (Linux)","description":"While browsing Vim documentation I encountered a nice tip about how to get highlithing of user-defined types. I decided to extend it a little to also support types defined elsewhere, that the source file may use (i.e. included files).\r\n\r\nThe script is written in Python and also requires CPP preprocessor (tested with 3.3 and 3.4) as well as exuberant ctags program.","4":"While browsing Vim documentation I encountered a nice tip about how to get highlithing of user-defined types. I decided to extend it a little to also support types defined elsewhere, that the source file may use (i.e. included files).\r\n\r\nThe script is written in Python and also requires CPP preprocessor (tested with 3.3 and 3.4) as well as exuberant ctags program.","install_details":"Download the script, make it executable, then put it to some directory in your PATH variable. Add the following lines to .vimrc file:\r\n\r\n\" load the types.vim highlighting file, if it exists\r\nautocmd BufRead,BufNewFile *.{c,h,C,H,cc,hh,cpp,hpp,cxx,hxx} let fname = expand('<afile>:p:h') . '\/types.vim'\r\nautocmd BufRead,BufNewFile *.{c,h,C,H,cc,hh,cpp,hpp,cxx,hxx} if filereadable(fname)\r\nautocmd BufRead,BufNewFile *.{c,h,C,H,cc,hh,cpp,hpp,cxx,hxx}   exe 'so ' . fname\r\nautocmd BufRead,BufNewFile *.{c,h,C,H,cc,hh,cpp,hpp,cxx,hxx} endif\r\n\r\nNext, cd to the directory with your source files, and invoke the script on files you would like to generate highlighting for, e.g.\r\ngentypes.py foo.c bar.c\r\nIt should leave types.vim file in the directory. The next time you edit these files Vim should highlight types defined in them and in the files they include. ","5":"Download the script, make it executable, then put it to some directory in your PATH variable. Add the following lines to .vimrc file:\r\n\r\n\" load the types.vim highlighting file, if it exists\r\nautocmd BufRead,BufNewFile *.{c,h,C,H,cc,hh,cpp,hpp,cxx,hxx} let fname = expand('<afile>:p:h') . '\/types.vim'\r\nautocmd BufRead,BufNewFile *.{c,h,C,H,cc,hh,cpp,hpp,cxx,hxx} if filereadable(fname)\r\nautocmd BufRead,BufNewFile *.{c,h,C,H,cc,hh,cpp,hpp,cxx,hxx}   exe 'so ' . fname\r\nautocmd BufRead,BufNewFile *.{c,h,C,H,cc,hh,cpp,hpp,cxx,hxx} endif\r\n\r\nNext, cd to the directory with your source files, and invoke the script on files you would like to generate highlighting for, e.g.\r\ngentypes.py foo.c bar.c\r\nIt should leave types.vim file in the directory. The next time you edit these files Vim should highlight types defined in them and in the files they include. ","first_name":"Krzysztof","6":"Krzysztof","last_name":"Wrzalik","7":"Wrzalik","releases":[{"0":"1233","vim_version":"6.0","1":"6.0","script_version":"0.1.1","2":"0.1.1","version_comment":"Slightly changed to allow -I\/path\/to\/includes, so that nonstandard locations can be used. Example usage:\r\ngentypes.py -I\/usr\/include\/gtk-2.0 gtk-demo.c","3":"Slightly changed to allow -I\/path\/to\/includes, so that nonstandard locations can be used. Example usage:\r\ngentypes.py -I\/usr\/include\/gtk-2.0 gtk-demo.c","package":"gentypes.py","4":"gentypes.py","src_id":"3979","5":"3979","creation_date":"1110264891","6":"1110264891"},{"0":"1233","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"gentypes.py","4":"gentypes.py","src_id":"3978","5":"3978","creation_date":"1110255675","6":"1110255675"}]},"1232":{"script_id":"1232","0":"1232","script_name":"DoTagStuff","1":"DoTagStuff","script_type":"syntax","2":"syntax","summary":"Syntax Highlight based on tags","3":"Syntax Highlight based on tags","description":"Extract information from a tags file (exuberant ctags), and generate syntax highlighting scripts for functions, globals, macros, etc.\r\n\r\nSomewhat \"raw\" extraction from my working environment; i.e., not particularly generic; e.g., hard-coded color settings for the various types of tokens identified (functions, macros, etc.).  Easily changed, but by editing the c.vim included that is intended to go in your \"after\/syntax\" vim directory.\r\n\r\n*Not* very polished, but perhaps helpful.\r\n\r\nFor a sample of the results, see:  http:\/\/castandcrew.com\/~gary\/DoTagStuff\/\r\n\r\nNOTE: You *must* include the --fields option to ctags that includes \"language of source file containing tag\" (i.e., \"--fields=l\" ; I use --fields=+Kl).  It's needed so that  the language type of each tag is included in the tags file.  This is needed to properly form syntax groups (e.g., cStaticFunction or perlExternalFunction -- to get the \"c\" or \"perl\" parts).","4":"Extract information from a tags file (exuberant ctags), and generate syntax highlighting scripts for functions, globals, macros, etc.\r\n\r\nSomewhat \"raw\" extraction from my working environment; i.e., not particularly generic; e.g., hard-coded color settings for the various types of tokens identified (functions, macros, etc.).  Easily changed, but by editing the c.vim included that is intended to go in your \"after\/syntax\" vim directory.\r\n\r\n*Not* very polished, but perhaps helpful.\r\n\r\nFor a sample of the results, see:  http:\/\/castandcrew.com\/~gary\/DoTagStuff\/\r\n\r\nNOTE: You *must* include the --fields option to ctags that includes \"language of source file containing tag\" (i.e., \"--fields=l\" ; I use --fields=+Kl).  It's needed so that  the language type of each tag is included in the tags file.  This is needed to properly form syntax groups (e.g., cStaticFunction or perlExternalFunction -- to get the \"c\" or \"perl\" parts).","install_details":"Unzip the bundle; it will expand into a HighlightTags directory; see README for more info.","5":"Unzip the bundle; it will expand into a HighlightTags directory; see README for more info.","first_name":"Gary","6":"Gary","last_name":"Holloway","7":"Holloway","releases":[{"0":"1232","vim_version":"6.0","1":"6.0","script_version":"1.2.2","2":"1.2.2","version_comment":"Fixed typo in README; added note that samples are intended only for gui (i.e., only set guifg\/guibg).","3":"Fixed typo in README; added note that samples are intended only for gui (i.e., only set guifg\/guibg).","package":"HighlightTags.zip","4":"HighlightTags.zip","src_id":"4004","5":"4004","creation_date":"1110538577","6":"1110538577"},{"0":"1232","vim_version":"6.0","1":"6.0","script_version":"1.2","2":"1.2","version_comment":"Added more debugging output (when run with -D).\r\n\r\nAdded note to README:  Must use --fields=l option to ctags to include the file language in the tag entries (needed for syntax names).","3":"Added more debugging output (when run with -D).\r\n\r\nAdded note to README:  Must use --fields=l option to ctags to include the file language in the tag entries (needed for syntax names).","package":"HighlightTags.zip","4":"HighlightTags.zip","src_id":"3995","5":"3995","creation_date":"1110453333","6":"1110453333"},{"0":"1232","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"HighlightTags.zip","4":"HighlightTags.zip","src_id":"3975","5":"3975","creation_date":"1110225511","6":"1110225511"}]},"1231":{"script_id":"1231","0":"1231","script_name":"mom.vim","1":"mom.vim","script_type":"syntax","2":"syntax","summary":"Syntax highlighting for the troff macro package","3":"Syntax highlighting for the troff macro package","description":"Syntax highlighting for mom, a troff macro package, or as mom's homepage (http:\/\/faustus.dyn.ca\/mom\/mom.html) states: \"mom is a typesetting and formatting package used to create high-quality, PostScript documents for printing.\"\r\n\r\nThis script is specialized for mom, although that is a troff macro package, this script does only have limited troff highlighting capabilities.\r\n","4":"Syntax highlighting for mom, a troff macro package, or as mom's homepage (http:\/\/faustus.dyn.ca\/mom\/mom.html) states: \"mom is a typesetting and formatting package used to create high-quality, PostScript documents for printing.\"\r\n\r\nThis script is specialized for mom, although that is a troff macro package, this script does only have limited troff highlighting capabilities.\r\n","install_details":"Vim knows mom files (extension .mom), but highlights them as simple troff files. So you have to overwrite this behavior in your ~\/vim\/filetype.vim file, as described in the vim online help for \"filetype\". Add the following line to that file, as described in the vim help:\r\n\r\n        au! BufRead,BufNewFile *.mom    setfiletype mom\r\n","5":"Vim knows mom files (extension .mom), but highlights them as simple troff files. So you have to overwrite this behavior in your ~\/vim\/filetype.vim file, as described in the vim online help for \"filetype\". Add the following line to that file, as described in the vim help:\r\n\r\n        au! BufRead,BufNewFile *.mom    setfiletype mom\r\n","first_name":"Christian","6":"Christian","last_name":"Br\u00c3\u00bcssow","7":"Br\u00c3\u00bcssow","releases":[{"0":"1231","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"mom.vim","4":"mom.vim","src_id":"3974","5":"3974","creation_date":"1110104208","6":"1110104208"}]},"1230":{"script_id":"1230","0":"1230","script_name":"Rainbow Parenthesis","1":"Rainbow Parenthesis","script_type":"syntax","2":"syntax","summary":"Highlight matching parens in a rainbow of colors","3":"Highlight matching parens in a rainbow of colors","description":"This script highlights matching parenthesis with a rainbow of colors. This make it visually very obvious which matches what. Most useful for Lisp.","4":"This script highlights matching parenthesis with a rainbow of colors. This make it visually very obvious which matches what. Most useful for Lisp.","install_details":"I dropped it into my ~\/.vim\/plugin directory. This make it show up all the time UNLESS you have syntax highlighting active. (because it\\'s cleared out by the act of loading syntax highlighting) SO you must add a line like\r\n\r\nruntime plugin\/RainbowParenthsis.vim\r\n\r\nto the END of your ~\/.vim\/syntax\/lisp.vim file (or the syntax file for whatever language you are using)\r\nYou may also source it directly with :so <filename>.","5":"I dropped it into my ~\/.vim\/plugin directory. This make it show up all the time UNLESS you have syntax highlighting active. (because it\\'s cleared out by the act of loading syntax highlighting) SO you must add a line like\r\n\r\nruntime plugin\/RainbowParenthsis.vim\r\n\r\nto the END of your ~\/.vim\/syntax\/lisp.vim file (or the syntax file for whatever language you are using)\r\nYou may also source it directly with :so <filename>.","first_name":"john","6":"john","last_name":"gilmore","7":"gilmore","releases":[{"0":"1230","vim_version":"6.0","1":"6.0","script_version":"1.1","2":"1.1","version_comment":"Now works nice(r) with more complex syntax highlighting (like c, for instance)","3":"Now works nice(r) with more complex syntax highlighting (like c, for instance)","package":"RainbowParenthsis.vim","4":"RainbowParenthsis.vim","src_id":"4007","5":"4007","creation_date":"1110646687","6":"1110646687"},{"0":"1230","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"RainbowParenthsis.vim","4":"RainbowParenthsis.vim","src_id":"3970","5":"3970","creation_date":"1110048247","6":"1110048247"}]},"1229":{"script_id":"1229","0":"1229","script_name":"crontab.freebsd.vim","1":"crontab.freebsd.vim","script_type":"syntax","2":"syntax","summary":"FreeBSD crontab syntax","3":"FreeBSD crontab syntax","description":"Crontab syntax, with FreeBSD extensions.\r\nUnderstands comments, environment variable assignmnents, date parts extensions (ranges, steps), @reboot etc, and some highlighting for executed commands (strings, percent sign).","4":"Crontab syntax, with FreeBSD extensions.\r\nUnderstands comments, environment variable assignmnents, date parts extensions (ranges, steps), @reboot etc, and some highlighting for executed commands (strings, percent sign).","install_details":"Copy script into ~\/.vim\/syntax directory, and modify ~\/.vim\/filetype.vim to pick this one instead of default crontab.vim.","5":"Copy script into ~\/.vim\/syntax directory, and modify ~\/.vim\/filetype.vim to pick this one instead of default crontab.vim.","first_name":"Alexander","6":"Alexander","last_name":"Pravking","7":"Pravking","releases":[{"0":"1229","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"crontab.freebsd.vim","4":"crontab.freebsd.vim","src_id":"3963","5":"3963","creation_date":"1109935242","6":"1109935242"}]},"1228":{"script_id":"1228","0":"1228","script_name":"recent.vim","1":"recent.vim","script_type":"utility","2":"utility","summary":"List recent edited files","3":"List recent edited files","description":"Save all written files into file ~\/.vim\/recent._files.\r\nAdd command :recent to open a buffer listing all edited files.","4":"Save all written files into file ~\/.vim\/recent._files.\r\nAdd command :recent to open a buffer listing all edited files.","install_details":"see README ","5":"see README ","first_name":"nguyen","6":"nguyen","last_name":"tien hai","7":"tien hai","releases":[{"0":"1228","vim_version":"6.0","1":"6.0","script_version":"1.3","2":"1.3","version_comment":"no add cvs adn svn temp file\r\nformat edited file list better way\r\n","3":"no add cvs adn svn temp file\r\nformat edited file list better way\r\n","package":"recent-1.3.tar.gz","4":"recent-1.3.tar.gz","src_id":"4002","5":"4002","creation_date":"1110527863","6":"1110527863"},{"0":"1228","vim_version":"6.0","1":"6.0","script_version":"1.2","2":"1.2","version_comment":"edited file list is managed better way","3":"edited file list is managed better way","package":"recent-1.2.tar.bz2","4":"recent-1.2.tar.bz2","src_id":"3985","5":"3985","creation_date":"1110337565","6":"1110337565"},{"0":"1228","vim_version":"6.0","1":"6.0","script_version":"1.1","2":"1.1","version_comment":"simplified installation","3":"simplified installation","package":"recent-1.1.tar.gz","4":"recent-1.1.tar.gz","src_id":"3959","5":"3959","creation_date":"1109924591","6":"1109924591"}]},"1227":{"script_id":"1227","0":"1227","script_name":"explorer+reader.vim","1":"explorer+reader.vim","script_type":"utility","2":"utility","summary":"preview many text files quickly","3":"preview many text files quickly","description":"with this script you can quickly preview files\r\nin a directory. For example execute these commands\r\nin a directory with many text files\r\n:cd dir_with_many_text_files\r\n:vi .\r\nor\r\n:vi dir_with_many_text_files\r\nthen by pressing page down you will preview files.\r\nPressing down will scroll the preview one line at a time and \r\npressing page down while on the preview \r\nit will focus on the explorer window","4":"with this script you can quickly preview files\r\nin a directory. For example execute these commands\r\nin a directory with many text files\r\n:cd dir_with_many_text_files\r\n:vi .\r\nor\r\n:vi dir_with_many_text_files\r\nthen by pressing page down you will preview files.\r\nPressing down will scroll the preview one line at a time and \r\npressing page down while on the preview \r\nit will focus on the explorer window","install_details":"copy the lines from the script in\r\n\" Set up mappings for this buffer\r\nportion of the explorer.vim plugin \r\n\r\nyou might want to copy the explorer.vim \r\nin a new place, modify it  and source\r\nit every time you want to use the mappings.\r\nIf you copy it then you also have to comment\r\nor delete the loaded_explorer check in the \r\nbeggining of the file\r\n","5":"copy the lines from the script in\r\n\" Set up mappings for this buffer\r\nportion of the explorer.vim plugin \r\n\r\nyou might want to copy the explorer.vim \r\nin a new place, modify it  and source\r\nit every time you want to use the mappings.\r\nIf you copy it then you also have to comment\r\nor delete the loaded_explorer check in the \r\nbeggining of the file\r\n","first_name":"kosmas","6":"kosmas","last_name":"karavopoulos","7":"karavopoulos","releases":[{"0":"1227","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"explorer+reader.vim.zip","4":"explorer+reader.vim.zip","src_id":"3941","5":"3941","creation_date":"1109653137","6":"1109653137"}]},"1226":{"script_id":"1226","0":"1226","script_name":"Vim klip for Serence Klipfolio (Windows","1":"Vim klip for Serence Klipfolio (Windows","script_type":"utility","2":"utility","summary":"Klip that queries vim.sf.net for recent scripts","3":"Klip that queries vim.sf.net for recent scripts","description":"For vim script lovers like myself who like to stay updated on the recently released vim scripts. Requires the (windows-only) klipfolio application from Serence.com. This klip is also avialable at: http:\/\/www.klipfarm.com\/farm.php?page=info&klip=4122","4":"For vim script lovers like myself who like to stay updated on the recently released vim scripts. Requires the (windows-only) klipfolio application from Serence.com. This klip is also avialable at: http:\/\/www.klipfarm.com\/farm.php?page=info&klip=4122","install_details":"copy into %klip_install_folder%\\myklips","5":"copy into %klip_install_folder%\\myklips","first_name":"M","6":"M","last_name":"K","7":"K","releases":[{"0":"1226","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"gvim.klip","4":"gvim.klip","src_id":"3940","5":"3940","creation_date":"1109648666","6":"1109648666"}]},"1225":{"script_id":"1225","0":"1225","script_name":"DotOutlineTree","1":"DotOutlineTree","script_type":"utility","2":"utility","summary":"Helps you edit structured text.","3":"Helps you edit structured text.","description":"This plugin makes an outline tree of a buffer.\r\nAlso this plugin enables jumping to a node and operating nodes.\r\n\r\nCurrently, it supports three formats:\r\n\r\n    - reStructuredText\r\n    - TaskPaper\r\n    - dot-structured text (.. title)\r\n\r\nFor more detailed descriptions, read dot.vim.","4":"This plugin makes an outline tree of a buffer.\r\nAlso this plugin enables jumping to a node and operating nodes.\r\n\r\nCurrently, it supports three formats:\r\n\r\n    - reStructuredText\r\n    - TaskPaper\r\n    - dot-structured text (.. title)\r\n\r\nFor more detailed descriptions, read dot.vim.","install_details":"Put this plugin in your plugin directory(e.g. $VIMRUNTIME\/plugin).\r\nThen restart VIM.\r\n","5":"Put this plugin in your plugin directory(e.g. $VIMRUNTIME\/plugin).\r\nThen restart VIM.\r\n","first_name":"Shuhei","6":"Shuhei","last_name":"Kubota","7":"Kubota","releases":[{"0":"1225","vim_version":"8.2","1":"8.2","script_version":"1.6","2":"1.6","version_comment":"retry type detection","3":"retry type detection","package":"dot.vim","4":"dot.vim","src_id":"27928","5":"27928","creation_date":"1643217821","6":"1643217821"},{"0":"1225","vim_version":"7.0","1":"7.0","script_version":"1.5","2":"1.5","version_comment":"markdown support","3":"markdown support","package":"dot.vim","4":"dot.vim","src_id":"27885","5":"27885","creation_date":"1641295179","6":"1641295179"},{"0":"1225","vim_version":"7.0","1":"7.0","script_version":"v1.4","2":"v1.4","version_comment":"make things work","3":"make things work","package":"dot.vim","4":"dot.vim","src_id":"27829","5":"27829","creation_date":"1638910370","6":"1638910370"},{"0":"1225","vim_version":"7.0","1":"7.0","script_version":"1.3","2":"1.3","version_comment":"more rest support.\r\n(improved overline-and-underline style support)\r\nthanks to Lin.","3":"more rest support.\r\n(improved overline-and-underline style support)\r\nthanks to Lin.","package":"dot.vim","4":"dot.vim","src_id":"16953","5":"16953","creation_date":"1322135104","6":"1322135104"},{"0":"1225","vim_version":"7.0","1":"7.0","script_version":"1.2.3","2":"1.2.3","version_comment":"rest: do not treat transitions and empty lines as sections.","3":"rest: do not treat transitions and empty lines as sections.","package":"dot.vim","4":"dot.vim","src_id":"16393","5":"16393","creation_date":"1314585714","6":"1314585714"},{"0":"1225","vim_version":"7.0","1":"7.0","script_version":"1.2.2","2":"1.2.2","version_comment":"changed EOL characters in this script.\r\n","3":"changed EOL characters in this script.\r\n","package":"dot.vim","4":"dot.vim","src_id":"12121","5":"12121","creation_date":"1263781740","6":"1263781740"},{"0":"1225","vim_version":"7.0","1":"7.0","script_version":"1.2.1","2":"1.2.1","version_comment":"* using &filetype to detect the document type\r\n    - 'rst', 'rest', 'taskpaper'\r\n* stripping leading spaces in rest documents\r\n* (explicit declaration of magic regexp)\r\nthanks to Sergey Khorev!","3":"* using &filetype to detect the document type\r\n    - 'rst', 'rest', 'taskpaper'\r\n* stripping leading spaces in rest documents\r\n* (explicit declaration of magic regexp)\r\nthanks to Sergey Khorev!","package":"dot.vim","4":"dot.vim","src_id":"12034","5":"12034","creation_date":"1263005710","6":"1263005710"},{"0":"1225","vim_version":"7.0","1":"7.0","script_version":"1.2.0","2":"1.2.0","version_comment":"arbitrary string heading for 'dot-structured' format, outline tree.\r\n\r\n* arbitrary string heading\r\n    - let b:DOT_headingMark = '#'\r\n* outline tree folding\r\n    - let b:DOT_foldTree = 1\r\n    - to expand tree, press l or r\r\n","3":"arbitrary string heading for 'dot-structured' format, outline tree.\r\n\r\n* arbitrary string heading\r\n    - let b:DOT_headingMark = '#'\r\n* outline tree folding\r\n    - let b:DOT_foldTree = 1\r\n    - to expand tree, press l or r\r\n","package":"dot.vim","4":"dot.vim","src_id":"11989","5":"11989","creation_date":"1262270067","6":"1262270067"}]},"1224":{"script_id":"1224","0":"1224","script_name":"my _vimrc (for Windows 2000\/XP\/7 users)","1":"my _vimrc (for Windows 2000\/XP\/7 users)","script_type":"utility","2":"utility","summary":"My very own _vimrc.","3":"My very own _vimrc.","description":"This _vimrc is currently used on my home and office machines running WinXP\/ Win7 and Linux boxes - all running gvim 7.3. However, it has been known to run on older Linuxes (running vim 5.x and above). I dont think it has any platform specific customization and has been reasonably commented. Contains tips from friends, this site and other sources.\r\n\r\nThis is not exactly the best _vimrc but my humble contribution. If you find a mistake or have a suggestion\/query - do leave a comment below or at my blog - http:\/\/tinyurl.com\/3jvty","4":"This _vimrc is currently used on my home and office machines running WinXP\/ Win7 and Linux boxes - all running gvim 7.3. However, it has been known to run on older Linuxes (running vim 5.x and above). I dont think it has any platform specific customization and has been reasonably commented. Contains tips from friends, this site and other sources.\r\n\r\nThis is not exactly the best _vimrc but my humble contribution. If you find a mistake or have a suggestion\/query - do leave a comment below or at my blog - http:\/\/tinyurl.com\/3jvty","install_details":"copy it into your vim installation folder (e.g: c:\\vim in my case).","5":"copy it into your vim installation folder (e.g: c:\\vim in my case).","first_name":"M","6":"M","last_name":"K","7":"K","releases":[{"0":"1224","vim_version":"7.0","1":"7.0","script_version":"1.0.6","2":"1.0.6","version_comment":"Added support for Unicode multi-byte files. Minor tweak to default font size","3":"Added support for Unicode multi-byte files. Minor tweak to default font size","package":"_vimrc","4":"_vimrc","src_id":"23584","5":"23584","creation_date":"1441905689","6":"1441905689"},{"0":"1224","vim_version":"7.0","1":"7.0","script_version":"1.0.5","2":"1.0.5","version_comment":"Status line now also shows character code at cursor.","3":"Status line now also shows character code at cursor.","package":"_vimrc","4":"_vimrc","src_id":"15848","5":"15848","creation_date":"1307700215","6":"1307700215"},{"0":"1224","vim_version":"7.0","1":"7.0","script_version":"1.0.4","2":"1.0.4","version_comment":"Minor fix to limit custom font only on Windows.","3":"Minor fix to limit custom font only on Windows.","package":"_vimrc","4":"_vimrc","src_id":"13027","5":"13027","creation_date":"1274260647","6":"1274260647"},{"0":"1224","vim_version":"7.0","1":"7.0","script_version":"1.0.3","2":"1.0.3","version_comment":"Added small tweaks, most notably the recently popular \"highlight current\" to give it the \"ultraedit\" look","3":"Added small tweaks, most notably the recently popular \"highlight current\" to give it the \"ultraedit\" look","package":"_vimrc","4":"_vimrc","src_id":"10163","5":"10163","creation_date":"1236715318","6":"1236715318"},{"0":"1224","vim_version":"7.0","1":"7.0","script_version":"1.0.2","2":"1.0.2","version_comment":"I have added a few firefox-like tab-related shortcuts to the script file (E.g Ctrl+T = new Tab, Ctrl+F4 = close current tab)","3":"I have added a few firefox-like tab-related shortcuts to the script file (E.g Ctrl+T = new Tab, Ctrl+F4 = close current tab)","package":"_vimrc","4":"_vimrc","src_id":"6201","5":"6201","creation_date":"1158648728","6":"1158648728"},{"0":"1224","vim_version":"6.0","1":"6.0","script_version":"1.0.1","2":"1.0.1","version_comment":"Minor correction made in the autocmd for java files (thanks to a anonymous visitor who left a comment on my blog).","3":"Minor correction made in the autocmd for java files (thanks to a anonymous visitor who left a comment on my blog).","package":"_vimrc","4":"_vimrc","src_id":"3950","5":"3950","creation_date":"1109748397","6":"1109748397"},{"0":"1224","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"_vimrc","4":"_vimrc","src_id":"3930","5":"3930","creation_date":"1109556046","6":"1109556046"}]},"1223":{"script_id":"1223","0":"1223","script_name":"plist.vim","1":"plist.vim","script_type":"syntax","2":"syntax","summary":"Old-Style ASCII Property List","3":"Old-Style ASCII Property List","description":"Property Lists were a configuration file format commonly used in the OpenStep framework. Currently, Apple has updated Property Lists to be XML-based, but Cocoa still supports the old-style Property Lists as well.\r\n\r\nProperty Lists are also available to the GNUStep libraries.\r\n\r\nMore information about property lists may be found at:\r\nhttp:\/\/developer.apple.com\/documentation\/Cocoa\/Conceptual\/PropertyLists\/Concepts\/OldStylePListsConcept.html\r\n\r\nAll suggestions to improve this syntax file are welcome.","4":"Property Lists were a configuration file format commonly used in the OpenStep framework. Currently, Apple has updated Property Lists to be XML-based, but Cocoa still supports the old-style Property Lists as well.\r\n\r\nProperty Lists are also available to the GNUStep libraries.\r\n\r\nMore information about property lists may be found at:\r\nhttp:\/\/developer.apple.com\/documentation\/Cocoa\/Conceptual\/PropertyLists\/Concepts\/OldStylePListsConcept.html\r\n\r\nAll suggestions to improve this syntax file are welcome.","install_details":"Add to your syntax directory and run \":setf plist\" when you have a property list file open.\r\n\r\nTo autodetect Property Lists with the extension .plist add the following to your vimrc:\r\n\r\naugroup filetypedetect\r\n  au! BufNewFile,BufRead *.plist setf plist\r\naugroup END","5":"Add to your syntax directory and run \":setf plist\" when you have a property list file open.\r\n\r\nTo autodetect Property Lists with the extension .plist add the following to your vimrc:\r\n\r\naugroup filetypedetect\r\n  au! BufNewFile,BufRead *.plist setf plist\r\naugroup END","first_name":"Matthew","6":"Matthew","last_name":"Jimenez","7":"Jimenez","releases":[{"0":"1223","vim_version":"6.0","1":"6.0","script_version":"1.3","2":"1.3","version_comment":"Comment and comment errors should work properly in dictionaries and arrays","3":"Comment and comment errors should work properly in dictionaries and arrays","package":"plist.vim","4":"plist.vim","src_id":"4063","5":"4063","creation_date":"1111587622","6":"1111587622"},{"0":"1223","vim_version":"6.0","1":"6.0","script_version":"1.2","2":"1.2","version_comment":"Array are allowed to be outside of dictionaries.\r\nKey-Value pairs in dictionaries can have unquoted numbers as value.","3":"Array are allowed to be outside of dictionaries.\r\nKey-Value pairs in dictionaries can have unquoted numbers as value.","package":"plist.vim","4":"plist.vim","src_id":"3934","5":"3934","creation_date":"1109571963","6":"1109571963"},{"0":"1223","vim_version":"6.0","1":"6.0","script_version":"1.1","2":"1.1","version_comment":"Dictionaries are acceptable values for keys in other dictionaries.","3":"Dictionaries are acceptable values for keys in other dictionaries.","package":"plist.vim","4":"plist.vim","src_id":"3926","5":"3926","creation_date":"1109537935","6":"1109537935"},{"0":"1223","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"plist.vim","4":"plist.vim","src_id":"3925","5":"3925","creation_date":"1109537084","6":"1109537084"}]},"1222":{"script_id":"1222","0":"1222","script_name":"OCaml instructions signature + parser","1":"OCaml instructions signature + parser","script_type":"utility","2":"utility","summary":"Script that parses and provides signature of instructions","3":"Script that parses and provides signature of instructions","description":"Project is closed!\r\nAnyone who would like to continue it please let me know.\r\n\r\n\r\nIf you have any suggestions or have found a bug please write to me: \r\n125783@student.pwr.wroc.pl\r\n\r\nIf you want to know how OCaml understands your instructions try this small script.\r\nThis script just shows you the signature of instruction - shows the OCaml answer after parsing.\r\n\r\nVer 0.81\r\nRemember to clear the buffer!! (see description below)\r\n\r\nVer 0.79:\r\nExample (returning the first and the last element of the list):\r\nlet example a = \r\n  if (List.length a)=0 then failwith \"Empty list!!\"\r\n  else List.hd a, List.hd (List.rev a);;\r\nexample [1;2;3;4];;\r\n\r\n:OCamlSigParseAllF\r\n# let example a  =\r\n  if (List.length a)=0 then failwith \\\"Error!!!\\\"\r\n  else List.hd a, List.hd (List.rev a);;\r\n      val example : 'a list -> 'a * 'a = <fun>\r\n# example [1;2;3;4];;\r\n- : int * int = (1, 4)\r\n\r\nIf you want to use menu type:\r\n:OCamlSigMenu\r\n\r\nFor parsing one instruction type\r\n:OCamlSigParseInstruction\r\n\r\nFor parsing whole program:\r\n:OCamlSigParseAll\r\nor (for full parsing information)\r\n:OCamlSigParseF \r\n\r\nTo close Status Window:\r\n:OCamlSigStatusWinClose\r\n\r\nTo open Status Window:\r\n:OCamlSigStatusWinShow\r\n\r\nIf you want to see the buffer (list of parsed and remembered instructions):\r\n:OCamlSigShowOCamlBuffer\r\n\r\nFor clearing this buffer:\r\n:OCamlSigClearOCamlBuffer\r\n\r\nIf the plugin cannot find OCaml edit the plugin file, find this line:\r\nlet s:OCamlPath = \"\"\r\nand set it to path where you have \"ocaml\" file\r\n","4":"Project is closed!\r\nAnyone who would like to continue it please let me know.\r\n\r\n\r\nIf you have any suggestions or have found a bug please write to me: \r\n125783@student.pwr.wroc.pl\r\n\r\nIf you want to know how OCaml understands your instructions try this small script.\r\nThis script just shows you the signature of instruction - shows the OCaml answer after parsing.\r\n\r\nVer 0.81\r\nRemember to clear the buffer!! (see description below)\r\n\r\nVer 0.79:\r\nExample (returning the first and the last element of the list):\r\nlet example a = \r\n  if (List.length a)=0 then failwith \"Empty list!!\"\r\n  else List.hd a, List.hd (List.rev a);;\r\nexample [1;2;3;4];;\r\n\r\n:OCamlSigParseAllF\r\n# let example a  =\r\n  if (List.length a)=0 then failwith \\\"Error!!!\\\"\r\n  else List.hd a, List.hd (List.rev a);;\r\n      val example : 'a list -> 'a * 'a = <fun>\r\n# example [1;2;3;4];;\r\n- : int * int = (1, 4)\r\n\r\nIf you want to use menu type:\r\n:OCamlSigMenu\r\n\r\nFor parsing one instruction type\r\n:OCamlSigParseInstruction\r\n\r\nFor parsing whole program:\r\n:OCamlSigParseAll\r\nor (for full parsing information)\r\n:OCamlSigParseF \r\n\r\nTo close Status Window:\r\n:OCamlSigStatusWinClose\r\n\r\nTo open Status Window:\r\n:OCamlSigStatusWinShow\r\n\r\nIf you want to see the buffer (list of parsed and remembered instructions):\r\n:OCamlSigShowOCamlBuffer\r\n\r\nFor clearing this buffer:\r\n:OCamlSigClearOCamlBuffer\r\n\r\nIf the plugin cannot find OCaml edit the plugin file, find this line:\r\nlet s:OCamlPath = \"\"\r\nand set it to path where you have \"ocaml\" file\r\n","install_details":"You need OCaml for using this script!\r\nJust copy the file to ~\/.vim\/plugin\r\nIf you want (for shortcut for parsing one instruction) you can add to ~\/.vimrc something like:\r\nautocmd FileType omlet nmap <F4> :OCamlSigParseInstruction <RETURN> \r\nfor shortcut for parsing all:\r\nautocmd FileType omlet nmap <S-F4> :OCamlSigParseAll <RETURN> \r\n\r\nYou can add other shortcuts if you want","5":"You need OCaml for using this script!\r\nJust copy the file to ~\/.vim\/plugin\r\nIf you want (for shortcut for parsing one instruction) you can add to ~\/.vimrc something like:\r\nautocmd FileType omlet nmap <F4> :OCamlSigParseInstruction <RETURN> \r\nfor shortcut for parsing all:\r\nautocmd FileType omlet nmap <S-F4> :OCamlSigParseAll <RETURN> \r\n\r\nYou can add other shortcuts if you want","first_name":"Grzegorz","6":"Grzegorz","last_name":"Dymarek","7":"Dymarek","releases":[{"0":"1222","vim_version":"6.0","1":"6.0","script_version":"0.81","2":"0.81","version_comment":"Improved recognition of imperative programming","3":"Improved recognition of imperative programming","package":"OCamlSig.vim","4":"OCamlSig.vim","src_id":"4210","5":"4210","creation_date":"1114662824","6":"1114662824"},{"0":"1222","vim_version":"6.0","1":"6.0","script_version":"0.80","2":"0.80","version_comment":"Should now work everything fine (structuers, types, etc) but sometimes bit slow. Clear the buffer then. (see description)","3":"Should now work everything fine (structuers, types, etc) but sometimes bit slow. Clear the buffer then. (see description)","package":"OCamlSig.vim","4":"OCamlSig.vim","src_id":"4134","5":"4134","creation_date":"1112837702","6":"1112837702"},{"0":"1222","vim_version":"6.0","1":"6.0","script_version":"0.80-beta2","2":"0.80-beta2","version_comment":"Bug fixes","3":"Bug fixes","package":"OCamlSig.vim","4":"OCamlSig.vim","src_id":"4107","5":"4107","creation_date":"1112263760","6":"1112263760"},{"0":"1222","vim_version":"6.0","1":"6.0","script_version":"0.80-beta","2":"0.80-beta","version_comment":"Should recognize types and structures (tested on trees)","3":"Should recognize types and structures (tested on trees)","package":"OCamlSig.vim","4":"OCamlSig.vim","src_id":"4045","5":"4045","creation_date":"1111311076","6":"1111311076"},{"0":"1222","vim_version":"6.0","1":"6.0","script_version":"0.79a","2":"0.79a","version_comment":"Repaired ver of 0.79 (0.79 doesn't work good - bug: instraction recognition)","3":"Repaired ver of 0.79 (0.79 doesn't work good - bug: instraction recognition)","package":"OCamlSig.vim","4":"OCamlSig.vim","src_id":"4014","5":"4014","creation_date":"1110787876","6":"1110787876"},{"0":"1222","vim_version":"6.0","1":"6.0","script_version":"0.79","2":"0.79","version_comment":"Added status window and a few improvements. Now you can work more effectively. No need to clear buffer so often.","3":"Added status window and a few improvements. Now you can work more effectively. No need to clear buffer so often.","package":"OCalmSig.vim","4":"OCalmSig.vim","src_id":"4006","5":"4006","creation_date":"1110594722","6":"1110594722"},{"0":"1222","vim_version":"6.0","1":"6.0","script_version":"0.72","2":"0.72","version_comment":"Don't have to be in first line of instruction to parse it,\r\n\"Inteligent\" buffer - doesn't add instructions that shouldn't be there (hence: buffer doesn't grow so fast - faster parsing)","3":"Don't have to be in first line of instruction to parse it,\r\n\"Inteligent\" buffer - doesn't add instructions that shouldn't be there (hence: buffer doesn't grow so fast - faster parsing)","package":"OCalmSig.vim","4":"OCalmSig.vim","src_id":"3969","5":"3969","creation_date":"1110036286","6":"1110036286"},{"0":"1222","vim_version":"6.0","1":"6.0","script_version":"0.7","2":"0.7","version_comment":"Added menu, error and warning handling, recognizing functions in functions, parsing instructions that calls functions, can also parse whole buffer, interpretating instructions that have strings in \" \"","3":"Added menu, error and warning handling, recognizing functions in functions, parsing instructions that calls functions, can also parse whole buffer, interpretating instructions that have strings in \" \"","package":"OCalmSig.vim","4":"OCalmSig.vim","src_id":"3964","5":"3964","creation_date":"1109941520","6":"1109941520"},{"0":"1222","vim_version":"6.0","1":"6.0","script_version":"0.2","2":"0.2","version_comment":"Faster execution, more comfortable, no need to have csh, don't have to save file before running (working on buffer). Just better OCaml instructions signature plugin (not script)","3":"Faster execution, more comfortable, no need to have csh, don't have to save file before running (working on buffer). Just better OCaml instructions signature plugin (not script)","package":"OCalmSig.vim","4":"OCalmSig.vim","src_id":"3953","5":"3953","creation_date":"1109782471","6":"1109782471"},{"0":"1222","vim_version":"6.0","1":"6.0","script_version":"0.13","2":"0.13","version_comment":"Hanging eliminated","3":"Hanging eliminated","package":"ocaml.sign.csh","4":"ocaml.sign.csh","src_id":"3942","5":"3942","creation_date":"1109659218","6":"1109659218"},{"0":"1222","vim_version":"6.0","1":"6.0","script_version":"0.12","2":"0.12","version_comment":"Recognizing instructions that take\/are in more then one line","3":"Recognizing instructions that take\/are in more then one line","package":"ocaml.sign.csh","4":"ocaml.sign.csh","src_id":"3938","5":"3938","creation_date":"1109583117","6":"1109583117"},{"0":"1222","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"ocaml.sign.csh","4":"ocaml.sign.csh","src_id":"3923","5":"3923","creation_date":"1109507414","6":"1109507414"}]},"1221":{"script_id":"1221","0":"1221","script_name":"monkeyd configuration syntax","1":"monkeyd configuration syntax","script_type":"syntax","2":"syntax","summary":"Syntax highlighting for monkeyd http server configuration files","3":"Syntax highlighting for monkeyd http server configuration files","description":"Syntax highlighting for monkeyd http server configuration files","4":"Syntax highlighting for monkeyd http server configuration files","install_details":"Place in ~\/.vimrc\/syntax\/.\r\nYou may wish to create a ~\/.vim\/ftdetect\/monkey.vim file containing something like:\r\n    au BufNewFile,BufRead \/*\/etc\/monkeyd\/* set filetype=monkeyd","5":"Place in ~\/.vimrc\/syntax\/.\r\nYou may wish to create a ~\/.vim\/ftdetect\/monkey.vim file containing something like:\r\n    au BufNewFile,BufRead \/*\/etc\/monkeyd\/* set filetype=monkeyd","first_name":"Ciaran","6":"Ciaran","last_name":"McCreesh","7":"McCreesh","releases":[{"0":"1221","vim_version":"6.0","1":"6.0","script_version":"20050227","2":"20050227","version_comment":"Initial upload","3":"Initial upload","package":"monkeyd.vim","4":"monkeyd.vim","src_id":"3922","5":"3922","creation_date":"1109496489","6":"1109496489"}]},"1220":{"script_id":"1220","0":"1220","script_name":"OpenGLSL","1":"OpenGLSL","script_type":"syntax","2":"syntax","summary":"OpenGL Shading Language syntax script","3":"OpenGL Shading Language syntax script","description":"A syntax script for builtin functions, uniform variables, constants and types for the OpenGL Shading Language V1.1 (http:\/\/www.opengl.org\/documentation\/oglsl.html)\r\n","4":"A syntax script for builtin functions, uniform variables, constants and types for the OpenGL Shading Language V1.1 (http:\/\/www.opengl.org\/documentation\/oglsl.html)\r\n","install_details":"drop gls.vim into your ~\/.vim\/syntax\/ directory and add something like:\r\n\r\n     autocmd BufNewFile,BufRead *.vp,*.fp,*.vert,*.frag,*.shd,*.gls set filetype=gls cindent comments=sr:\/*,mbl:*,ex:*\/,:\/\/\r\n\r\nto your .vimrc\r\n\r\nAlternatively install into the $VIMRUNTIME\/syntax\/ directory and add the above rule to $VIMRUNTIME\/filetype.vim.","5":"drop gls.vim into your ~\/.vim\/syntax\/ directory and add something like:\r\n\r\n     autocmd BufNewFile,BufRead *.vp,*.fp,*.vert,*.frag,*.shd,*.gls set filetype=gls cindent comments=sr:\/*,mbl:*,ex:*\/,:\/\/\r\n\r\nto your .vimrc\r\n\r\nAlternatively install into the $VIMRUNTIME\/syntax\/ directory and add the above rule to $VIMRUNTIME\/filetype.vim.","first_name":"Adam","6":"Adam","last_name":"Butcher","7":"Butcher","releases":[{"0":"1220","vim_version":"6.0","1":"6.0","script_version":"0.12","2":"0.12","version_comment":"Removed arrayof operator bug and suggested more reasonable file extensions.\r\n","3":"Removed arrayof operator bug and suggested more reasonable file extensions.\r\n","package":"gls.vim","4":"gls.vim","src_id":"3921","5":"3921","creation_date":"1109414515","6":"1109414515"},{"0":"1220","vim_version":"6.0","1":"6.0","script_version":"0.11","2":"0.11","version_comment":"Added components rgba and stpq.","3":"Added components rgba and stpq.","package":"gls.vim","4":"gls.vim","src_id":"3919","5":"3919","creation_date":"1109409165","6":"1109409165"},{"0":"1220","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Fixed typo gl_vertex.","3":"Fixed typo gl_vertex.","package":"gls.vim","4":"gls.vim","src_id":"3918","5":"3918","creation_date":"1109403168","6":"1109403168"}]},"1219":{"script_id":"1219","0":"1219","script_name":"darkblack.vim","1":"darkblack.vim","script_type":"color scheme","2":"color scheme","summary":"A black background color scheme based on darkblue.","3":"A black background color scheme based on darkblue.","description":"Darkblack is an alteration to the darkblue colorscheme by Bohdan Vlasyuk.\r\nIt provides a black background and fonts with light colors to keep them visible.\r\n\r\nDesign for gui, but should look good on cterm as well.","4":"Darkblack is an alteration to the darkblue colorscheme by Bohdan Vlasyuk.\r\nIt provides a black background and fonts with light colors to keep them visible.\r\n\r\nDesign for gui, but should look good on cterm as well.","install_details":"Add to colors directory and run \":colorscheme darkblack\"\r\n\r\nRun dos2unix on darkblack.vim if vim gives the message \"E492: Not an editor command: ^M\"","5":"Add to colors directory and run \":colorscheme darkblack\"\r\n\r\nRun dos2unix on darkblack.vim if vim gives the message \"E492: Not an editor command: ^M\"","first_name":"Matthew","6":"Matthew","last_name":"Jimenez","7":"Jimenez","releases":[{"0":"1219","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"darkblack.vim","4":"darkblack.vim","src_id":"3911","5":"3911","creation_date":"1109335817","6":"1109335817"}]},"1218":{"script_id":"1218","0":"1218","script_name":"The NERD Commenter","1":"The NERD Commenter","script_type":"utility","2":"utility","summary":"A plugin that allows for easy commenting of code for many filetypes.","3":"A plugin that allows for easy commenting of code for many filetypes.","description":"Grab the latest dev version from github: https:\/\/github.com\/scrooloose\/nerdcommenter.\r\n\r\nThe following key mappings are provided by default (there is also a menu\r\nprovided that contains menu items corresponding to all the below mappings):\r\n\r\nMost of the following mappings are for normal\/visual mode only. The\r\n|NERDComInsertComment| mapping is for insert mode only.\r\n\r\n[count]<leader>cc |NERDComComment|\r\nComment out the current line or text selected in visual mode.\r\n\r\n\r\n[count]<leader>cn |NERDComNestedComment|\r\nSame as <leader>cc but forces nesting.\r\n\r\n\r\n[count]<leader>c<space> |NERDComToggleComment|\r\nToggles the comment state of the selected line(s). If the topmost selected\r\nline is commented, all selected lines are uncommented and vice versa.\r\n\r\n\r\n[count]<leader>cm |NERDComMinimalComment|\r\nComments the given lines using only one set of multipart delimiters.\r\n\r\n\r\n[count]<leader>ci |NERDComInvertComment|\r\nToggles the comment state of the selected line(s) individually.\r\n\r\n\r\n[count]<leader>cs |NERDComSexyComment|\r\nComments out the selected lines ``sexily''\r\n\r\n\r\n[count]<leader>cy |NERDComYankComment|\r\nSame as <leader>cc except that the commented line(s) are yanked first.\r\n\r\n\r\n<leader>c$ |NERDComEOLComment|\r\nComments the current line from the cursor to the end of line.\r\n\r\n\r\n<leader>cA |NERDComAppendComment|\r\nAdds comment delimiters to the end of line and goes into insert mode between\r\nthem.\r\n\r\n\r\n|NERDComInsertComment|\r\nAdds comment delimiters at the current cursor position and inserts between.\r\nDisabled by default.\r\n\r\n\r\n<leader>ca |NERDComAltDelim|\r\nSwitches to the alternative set of delimiters.\r\n\r\n\r\n[count]<leader>cl\r\n[count]<leader>cb    |NERDComAlignedComment|\r\nSame as |NERDComComment| except that the delimiters are aligned down the\r\nleft side (<leader>cl) or both sides (<leader>cb).\r\n\r\n\r\n[count]<leader>cu |NERDComUncommentLine|\r\nUncomments the selected line(s).\r\n","4":"Grab the latest dev version from github: https:\/\/github.com\/scrooloose\/nerdcommenter.\r\n\r\nThe following key mappings are provided by default (there is also a menu\r\nprovided that contains menu items corresponding to all the below mappings):\r\n\r\nMost of the following mappings are for normal\/visual mode only. The\r\n|NERDComInsertComment| mapping is for insert mode only.\r\n\r\n[count]<leader>cc |NERDComComment|\r\nComment out the current line or text selected in visual mode.\r\n\r\n\r\n[count]<leader>cn |NERDComNestedComment|\r\nSame as <leader>cc but forces nesting.\r\n\r\n\r\n[count]<leader>c<space> |NERDComToggleComment|\r\nToggles the comment state of the selected line(s). If the topmost selected\r\nline is commented, all selected lines are uncommented and vice versa.\r\n\r\n\r\n[count]<leader>cm |NERDComMinimalComment|\r\nComments the given lines using only one set of multipart delimiters.\r\n\r\n\r\n[count]<leader>ci |NERDComInvertComment|\r\nToggles the comment state of the selected line(s) individually.\r\n\r\n\r\n[count]<leader>cs |NERDComSexyComment|\r\nComments out the selected lines ``sexily''\r\n\r\n\r\n[count]<leader>cy |NERDComYankComment|\r\nSame as <leader>cc except that the commented line(s) are yanked first.\r\n\r\n\r\n<leader>c$ |NERDComEOLComment|\r\nComments the current line from the cursor to the end of line.\r\n\r\n\r\n<leader>cA |NERDComAppendComment|\r\nAdds comment delimiters to the end of line and goes into insert mode between\r\nthem.\r\n\r\n\r\n|NERDComInsertComment|\r\nAdds comment delimiters at the current cursor position and inserts between.\r\nDisabled by default.\r\n\r\n\r\n<leader>ca |NERDComAltDelim|\r\nSwitches to the alternative set of delimiters.\r\n\r\n\r\n[count]<leader>cl\r\n[count]<leader>cb    |NERDComAlignedComment|\r\nSame as |NERDComComment| except that the delimiters are aligned down the\r\nleft side (<leader>cl) or both sides (<leader>cb).\r\n\r\n\r\n[count]<leader>cu |NERDComUncommentLine|\r\nUncomments the selected line(s).\r\n","install_details":"The NERD Commenter requires Vim 7 or higher.\r\n\r\nExtract the plugin files in your ~\/.vim (*nix) or ~\/vimfiles (Windows). You\r\nshould have 2 files: \r\n    plugin\/NERD_commenter.vim\r\n    doc\/NERD_commenter.txt\r\n\r\nNext, to finish installing the help file run: \r\n    :helptags ~\/.vim\/doc\r\n\r\nSee |add-local-help| for more details.\r\n\r\nMake sure that you have filetype plugins enabled, as the script makes use of\r\n|'commentstring'| where possible (which is usually set in a filetype plugin).\r\nSee |filetype-plugin-on| for details, but basically, stick this in your vimrc \r\n    filetype plugin on","5":"The NERD Commenter requires Vim 7 or higher.\r\n\r\nExtract the plugin files in your ~\/.vim (*nix) or ~\/vimfiles (Windows). You\r\nshould have 2 files: \r\n    plugin\/NERD_commenter.vim\r\n    doc\/NERD_commenter.txt\r\n\r\nNext, to finish installing the help file run: \r\n    :helptags ~\/.vim\/doc\r\n\r\nSee |add-local-help| for more details.\r\n\r\nMake sure that you have filetype plugins enabled, as the script makes use of\r\n|'commentstring'| where possible (which is usually set in a filetype plugin).\r\nSee |filetype-plugin-on| for details, but basically, stick this in your vimrc \r\n    filetype plugin on","first_name":"Marty","6":"Marty","last_name":"Grenfell","7":"Grenfell","releases":[{"0":"1218","vim_version":"7.0","1":"7.0","script_version":"2.3.0","2":"2.3.0","version_comment":"- remove all filetypes which have a &commentstring in the standard vim runtime\r\n  for vim > 7.0 unless the script stores an alternate set of delimiters\r\n- make the script complain if the user doesnt have filetype plugins enabled\r\n- use <leader> instead of comma to start the default mappings\r\n- fix a couple of bugs with sexy comments - thanks to Tim Smart\r\n- lots of refactoring\r\n","3":"- remove all filetypes which have a &commentstring in the standard vim runtime\r\n  for vim > 7.0 unless the script stores an alternate set of delimiters\r\n- make the script complain if the user doesnt have filetype plugins enabled\r\n- use <leader> instead of comma to start the default mappings\r\n- fix a couple of bugs with sexy comments - thanks to Tim Smart\r\n- lots of refactoring\r\n","package":"nerdcommenter.zip","4":"nerdcommenter.zip","src_id":"14455","5":"14455","creation_date":"1291754500","6":"1291754500"},{"0":"1218","vim_version":"7.0","1":"7.0","script_version":"2.2.2","2":"2.2.2","version_comment":"- remove the NERDShutup option and the message is\r\n  suppresses, this makes the plugin silently rely on\r\n  &commentstring for unknown filetypes.\r\n- add support for dhcpd, limits, ntp, resolv, rgb, sysctl,\r\n  udevconf and udevrules. Thanks to Thilo Six.\r\n- match filetypes case insensitively\r\n- add support for mp (metapost), thanks to Andrey Skvortsov.\r\n- add support for htmlcheetah, thanks to Simon Hengel.\r\n- add support for javacc, thanks to Matt Tolton.\r\n- make <%# %> the default delims for eruby, thanks to tpope.\r\n- add support for javascript.jquery, thanks to Ivan Devat.\r\n- add support for cucumber and pdf. Fix sass and railslog\r\n  delims, thanks to tpope\r\n","3":"- remove the NERDShutup option and the message is\r\n  suppresses, this makes the plugin silently rely on\r\n  &commentstring for unknown filetypes.\r\n- add support for dhcpd, limits, ntp, resolv, rgb, sysctl,\r\n  udevconf and udevrules. Thanks to Thilo Six.\r\n- match filetypes case insensitively\r\n- add support for mp (metapost), thanks to Andrey Skvortsov.\r\n- add support for htmlcheetah, thanks to Simon Hengel.\r\n- add support for javacc, thanks to Matt Tolton.\r\n- make <%# %> the default delims for eruby, thanks to tpope.\r\n- add support for javascript.jquery, thanks to Ivan Devat.\r\n- add support for cucumber and pdf. Fix sass and railslog\r\n  delims, thanks to tpope\r\n","package":"NERD_commenter.zip","4":"NERD_commenter.zip","src_id":"10318","5":"10318","creation_date":"1238392231","6":"1238392231"},{"0":"1218","vim_version":"7.0","1":"7.0","script_version":"2.2.1","2":"2.2.1","version_comment":"- add support for newlisp and clojure, thanks to Matthew Lee Hinman.\r\n- fix automake comments, thanks to Elias Pipping\r\n- make haml comments default to -# with \/ as the alternative delimiter,\r\n  thanks to tpope\r\n- add support for actionscript and processing thanks to Edwin Benavides\r\n- add support for ps1 (powershell), thanks to Jason Mills\r\n- add support for hostsaccess, thanks to Thomas Rowe\r\n- add support for CVScommit\r\n- add support for asciidoc, git and gitrebase. Thanks to Simon Ruderich.\r\n- use # for gitcommit comments, thanks to Simon Ruderich.\r\n- add support for mako and genshi, thanks to Keitheis.\r\n- add support for conkyrc, thanks to David\r\n- add support for SVNannotate, thanks to Miguel Jaque Barbero.\r\n- add support for sieve, thanks to Stefan Walk\r\n- add support for objj, thanks to Adam Thorsen.\r\n","3":"- add support for newlisp and clojure, thanks to Matthew Lee Hinman.\r\n- fix automake comments, thanks to Elias Pipping\r\n- make haml comments default to -# with \/ as the alternative delimiter,\r\n  thanks to tpope\r\n- add support for actionscript and processing thanks to Edwin Benavides\r\n- add support for ps1 (powershell), thanks to Jason Mills\r\n- add support for hostsaccess, thanks to Thomas Rowe\r\n- add support for CVScommit\r\n- add support for asciidoc, git and gitrebase. Thanks to Simon Ruderich.\r\n- use # for gitcommit comments, thanks to Simon Ruderich.\r\n- add support for mako and genshi, thanks to Keitheis.\r\n- add support for conkyrc, thanks to David\r\n- add support for SVNannotate, thanks to Miguel Jaque Barbero.\r\n- add support for sieve, thanks to Stefan Walk\r\n- add support for objj, thanks to Adam Thorsen.\r\n","package":"NERD_commenter.zip","4":"NERD_commenter.zip","src_id":"9497","5":"9497","creation_date":"1226572077","6":"1226572077"},{"0":"1218","vim_version":"7.0","1":"7.0","script_version":"2.2.0","2":"2.2.0","version_comment":"- rewrote the mappings system to be more \"standard\".\r\n  - removed all the mapping options. Now, mappings to <plug>\r\n    mappings are used\r\n  - see :help NERDComMappings, and :help\r\n    NERDCreateDefaultMappings for more info\r\n- remove \"prepend comments\" and \"right aligned comments\".\r\n- add support for applescript, calbire, man, SVNcommit,\r\n  potwiki, txt2tags and SVNinfo.  Thanks to nicothakis,\r\n  timberke, sgronblo, mntnoe, Bernhard Grotz, John O'Shea,\r\n  Fran\u00c3\u00a7ois and Giacomo Mariani respectively.\r\n- bugfix for haskell delimiters. Thanks to mntnoe.","3":"- rewrote the mappings system to be more \"standard\".\r\n  - removed all the mapping options. Now, mappings to <plug>\r\n    mappings are used\r\n  - see :help NERDComMappings, and :help\r\n    NERDCreateDefaultMappings for more info\r\n- remove \"prepend comments\" and \"right aligned comments\".\r\n- add support for applescript, calbire, man, SVNcommit,\r\n  potwiki, txt2tags and SVNinfo.  Thanks to nicothakis,\r\n  timberke, sgronblo, mntnoe, Bernhard Grotz, John O'Shea,\r\n  Fran\u00c3\u00a7ois and Giacomo Mariani respectively.\r\n- bugfix for haskell delimiters. Thanks to mntnoe.","package":"NERD_commenter.zip","4":"NERD_commenter.zip","src_id":"9303","5":"9303","creation_date":"1223032477","6":"1223032477"},{"0":"1218","vim_version":"7.0","1":"7.0","script_version":"2.1.18","2":"2.1.18","version_comment":"- add support for llvm. Thanks to nicothakis.\r\n- add support for xquery. Thanks to Phillip Kovalev.\r\n- fixed haskell delimiters (hackily). Thanks to Elias\r\n  Pipping.\r\n- add support for mailcap. Thanks to Pascal Brueckner.\r\n- add support for stata. Thanks to Jer\u00c3\u00b3nimo Carballo.\r\n- applied a patch from ewfalor to fix an error in the help\r\n  file with the NERDMapleader doc\r\n- disable the insert mode ctrl-c mapping by default, see\r\n  :help NERDComInsertComment if you wish to restore it\r\n","3":"- add support for llvm. Thanks to nicothakis.\r\n- add support for xquery. Thanks to Phillip Kovalev.\r\n- fixed haskell delimiters (hackily). Thanks to Elias\r\n  Pipping.\r\n- add support for mailcap. Thanks to Pascal Brueckner.\r\n- add support for stata. Thanks to Jer\u00c3\u00b3nimo Carballo.\r\n- applied a patch from ewfalor to fix an error in the help\r\n  file with the NERDMapleader doc\r\n- disable the insert mode ctrl-c mapping by default, see\r\n  :help NERDComInsertComment if you wish to restore it\r\n","package":"NERD_commenter.zip","4":"NERD_commenter.zip","src_id":"9031","5":"9031","creation_date":"1217128748","6":"1217128748"},{"0":"1218","vim_version":"7.0","1":"7.0","script_version":"2.1.16","2":"2.1.16","version_comment":"compatibility fix for vim7.2, cheers to Ben Schmidt, David Fishburn, and\r\nErik Falor for the emails, and to JaGoTerr for posting the issue.\r\n","3":"compatibility fix for vim7.2, cheers to Ben Schmidt, David Fishburn, and\r\nErik Falor for the emails, and to JaGoTerr for posting the issue.\r\n","package":"NERD_commenter.zip","4":"NERD_commenter.zip","src_id":"8860","5":"8860","creation_date":"1214502525","6":"1214502525"},{"0":"1218","vim_version":"7.0","1":"7.0","script_version":"2.1.15","2":"2.1.15","version_comment":"- added pamconf support, thanks to Martin Kustermann\r\n- added mason support, thanks to Indri\u00c3\u00b0i Einarsson\r\n- added map support, thanks to Chris\r\n- added bzr support, thanks to Stromnov\r\n- added group support, thanks to Krzysztof A. Adamski\r\n- change license to wtfpl\r\n","3":"- added pamconf support, thanks to Martin Kustermann\r\n- added mason support, thanks to Indri\u00c3\u00b0i Einarsson\r\n- added map support, thanks to Chris\r\n- added bzr support, thanks to Stromnov\r\n- added group support, thanks to Krzysztof A. Adamski\r\n- change license to wtfpl\r\n","package":"NERD_commenter.zip","4":"NERD_commenter.zip","src_id":"8833","5":"8833","creation_date":"1214068328","6":"1214068328"},{"0":"1218","vim_version":"7.0","1":"7.0","script_version":"2.1.14","2":"2.1.14","version_comment":"- added support for gitconfig, tar, nerdtree\r\n- added support for dtrace, thanks to nicothakis for the post\r\n","3":"- added support for gitconfig, tar, nerdtree\r\n- added support for dtrace, thanks to nicothakis for the post\r\n","package":"NERD_commenter.zip","4":"NERD_commenter.zip","src_id":"8700","5":"8700","creation_date":"1210972956","6":"1210972956"},{"0":"1218","vim_version":"7.0","1":"7.0","script_version":"2.1.13","2":"2.1.13","version_comment":" - added support for rib, pyrex\/cython, liquid, services, gitcommit,\r\n  vimperator, and slice. Thanks to spookypeanut, Greg Jandl, Christophe\r\n  Benz, A Pontus, and Stromnov for emailing me and\/or posting issues.\r\n- set the NERDRemoveExtraSpaces option to 1 by default as the doc states\r\n- other fixes: (thanks to Zhang Shuhan for all his emails and testing)\r\n    * made the sexy comment mapping fall back to normal commenting if sexy\r\n      comments arent possible for the current filetype\r\n    * fixed some bugs with sexy comments\r\n    * made the uncommenting side of toggle comments slightly more robust\r\n    * fixed a bug where some extra spaces werent being removed (although\r\n      the currect options were set)\r\n","3":" - added support for rib, pyrex\/cython, liquid, services, gitcommit,\r\n  vimperator, and slice. Thanks to spookypeanut, Greg Jandl, Christophe\r\n  Benz, A Pontus, and Stromnov for emailing me and\/or posting issues.\r\n- set the NERDRemoveExtraSpaces option to 1 by default as the doc states\r\n- other fixes: (thanks to Zhang Shuhan for all his emails and testing)\r\n    * made the sexy comment mapping fall back to normal commenting if sexy\r\n      comments arent possible for the current filetype\r\n    * fixed some bugs with sexy comments\r\n    * made the uncommenting side of toggle comments slightly more robust\r\n    * fixed a bug where some extra spaces werent being removed (although\r\n      the currect options were set)\r\n","package":"NERD_commenter.zip","4":"NERD_commenter.zip","src_id":"8643","5":"8643","creation_date":"1209840822","6":"1209840822"},{"0":"1218","vim_version":"7.0","1":"7.0","script_version":"2.1.12","2":"2.1.12","version_comment":"- added support for patran and dakota, thx to Jacobo Diaz for the email\r\n- added support for gentoo-env-d, gentoo-init-d, gentoo-make-conf, grub, modconf and sudoers filetypes, thx to Li Jin for the patch.\r\n- added support for SVNdiff, gitAnnotate, gitdiff. Thx to nicothakis for posting the issue\r\n","3":"- added support for patran and dakota, thx to Jacobo Diaz for the email\r\n- added support for gentoo-env-d, gentoo-init-d, gentoo-make-conf, grub, modconf and sudoers filetypes, thx to Li Jin for the patch.\r\n- added support for SVNdiff, gitAnnotate, gitdiff. Thx to nicothakis for posting the issue\r\n","package":"NERD_commenter.zip","4":"NERD_commenter.zip","src_id":"8510","5":"8510","creation_date":"1206915568","6":"1206915568"},{"0":"1218","vim_version":"7.0","1":"7.0","script_version":"2.1.11","2":"2.1.11","version_comment":"- fixed a bug with the selection option and visual commenting (again).  Thanks to Ingo Karkat (again).\r\n","3":"- fixed a bug with the selection option and visual commenting (again).  Thanks to Ingo Karkat (again).\r\n","package":"NERD_commenter.zip","4":"NERD_commenter.zip","src_id":"8335","5":"8335","creation_date":"1203738631","6":"1203738631"},{"0":"1218","vim_version":"7.0","1":"7.0","script_version":"2.1.10","2":"2.1.10","version_comment":"- added support for Wikipedia (thanks to Chen Xing)\r\n- added support for mplayerconf\r\n- bugfixes (thanks to Ingo Karkat for the bug report\/patch)\r\n- added support for mkd (thanks to Stefano Zacchiroli)\r\n","3":"- added support for Wikipedia (thanks to Chen Xing)\r\n- added support for mplayerconf\r\n- bugfixes (thanks to Ingo Karkat for the bug report\/patch)\r\n- added support for mkd (thanks to Stefano Zacchiroli)\r\n","package":"NERD_commenter.zip","4":"NERD_commenter.zip","src_id":"8325","5":"8325","creation_date":"1203645458","6":"1203645458"},{"0":"1218","vim_version":"7.0","1":"7.0","script_version":"2.1.9","2":"2.1.9","version_comment":"- added support for mrxvtrc and aap, thx to Marco for the emails\r\n- added dummy support for SVNAnnotate, SVKAnnotate and CVSAnnotate, thx to nicothakis for posting the issue\r\n","3":"- added support for mrxvtrc and aap, thx to Marco for the emails\r\n- added dummy support for SVNAnnotate, SVKAnnotate and CVSAnnotate, thx to nicothakis for posting the issue\r\n","package":"NERD_commenter.zip","4":"NERD_commenter.zip","src_id":"8161","5":"8161","creation_date":"1200664589","6":"1200664589"},{"0":"1218","vim_version":"7.0","1":"7.0","script_version":"2.1.8","2":"2.1.8","version_comment":"- fixed a couple of bugs with the NERDSpaceDelims option, thx to David Miani and Jeremy Hinegardner\r\n- added dummy support for lhaskell, thx to pipp for posting the issue\r\n- added an alternative set of delims for the plsql filetype, thx to Kuchma Michael\r\n- added support for spectre, thx to Brett Warneke\r\n- added support for scala, thx to Renald Buter\r\n- added support for asymptote, thx to Vladimir Lomov\r\n- made NERDDefaultNesting enabled by default as this seems more intuitive, thx to marco for the suggestion\r\n","3":"- fixed a couple of bugs with the NERDSpaceDelims option, thx to David Miani and Jeremy Hinegardner\r\n- added dummy support for lhaskell, thx to pipp for posting the issue\r\n- added an alternative set of delims for the plsql filetype, thx to Kuchma Michael\r\n- added support for spectre, thx to Brett Warneke\r\n- added support for scala, thx to Renald Buter\r\n- added support for asymptote, thx to Vladimir Lomov\r\n- made NERDDefaultNesting enabled by default as this seems more intuitive, thx to marco for the suggestion\r\n","package":"NERD_commenter.zip","4":"NERD_commenter.zip","src_id":"8051","5":"8051","creation_date":"1197573560","6":"1197573560"},{"0":"1218","vim_version":"7.0","1":"7.0","script_version":"2.1.6","2":"2.1.6","version_comment":"- added support for gentoo-conf-d thanks to tinoucas for posting the issue and the patch\r\n- added support for the D filetype. Thanks to Greg Weber for the email.\r\n- added dummy support for cobol, cheers to timberke for posting the issue.\r\n- added support for velocity. Thanks to Bruce Sherrod for the email.\r\n","3":"- added support for gentoo-conf-d thanks to tinoucas for posting the issue and the patch\r\n- added support for the D filetype. Thanks to Greg Weber for the email.\r\n- added dummy support for cobol, cheers to timberke for posting the issue.\r\n- added support for velocity. Thanks to Bruce Sherrod for the email.\r\n","package":"NERD_commenter.vim","4":"NERD_commenter.vim","src_id":"7827","5":"7827","creation_date":"1193326376","6":"1193326376"},{"0":"1218","vim_version":"7.0","1":"7.0","script_version":"2.1.5","2":"2.1.5","version_comment":"- added support for lilypond, bbx and lytex. Thanks to Eyolf \u00c3\u0098strem for the email.\r\n- added an alterative set of delimiters for the dosbatch filetype, thanks to Ingo Karkat for the email.\r\n- added support for the markdown filetype. Thanks to Nicolas Weber for posting the issue.\r\n","3":"- added support for lilypond, bbx and lytex. Thanks to Eyolf \u00c3\u0098strem for the email.\r\n- added an alterative set of delimiters for the dosbatch filetype, thanks to Ingo Karkat for the email.\r\n- added support for the markdown filetype. Thanks to Nicolas Weber for posting the issue.\r\n","package":"NERD_commenter.vim","4":"NERD_commenter.vim","src_id":"7786","5":"7786","creation_date":"1192203324","6":"1192203324"},{"0":"1218","vim_version":"7.0","1":"7.0","script_version":"2.1.4","2":"2.1.4","version_comment":"- added support for the ahk filetype. Cheers to Don Hatlestad for the email.\r\n- added support for desktop and xsd filetypes. Thanks to Christophe Benz.\r\n- added dummy support for Rails-log\r\n- fixed a bunch of bugs in the comment delimiter setup process, thanks to Cheng Fang for the email :D\r\n- hardcore refactoring and removal of seldomly used, overly-complex functionality\r\n- the script now requires vim 7\r\n","3":"- added support for the ahk filetype. Cheers to Don Hatlestad for the email.\r\n- added support for desktop and xsd filetypes. Thanks to Christophe Benz.\r\n- added dummy support for Rails-log\r\n- fixed a bunch of bugs in the comment delimiter setup process, thanks to Cheng Fang for the email :D\r\n- hardcore refactoring and removal of seldomly used, overly-complex functionality\r\n- the script now requires vim 7\r\n","package":"NERD_commenter.vim","4":"NERD_commenter.vim","src_id":"7731","5":"7731","creation_date":"1191041356","6":"1191041356"},{"0":"1218","vim_version":"6.0","1":"6.0","script_version":"2.1.3","2":"2.1.3","version_comment":"- fixed numerous bugs that were causing tabs to permanently be converted to spaces, even if noexpandtab was set. Thanks to Heptite on #vim for working with me to track them down :)\r\n- added dummy support for \"lookupfile\". Thanks to David Fishburn for the email.\r\n- added support for \"rst\", thanks to Niels Aan de Brugh for the email.\r\n","3":"- fixed numerous bugs that were causing tabs to permanently be converted to spaces, even if noexpandtab was set. Thanks to Heptite on #vim for working with me to track them down :)\r\n- added dummy support for \"lookupfile\". Thanks to David Fishburn for the email.\r\n- added support for \"rst\", thanks to Niels Aan de Brugh for the email.\r\n","package":"NERD_commenter.vim","4":"NERD_commenter.vim","src_id":"7570","5":"7570","creation_date":"1188252683","6":"1188252683"},{"0":"1218","vim_version":"6.0","1":"6.0","script_version":"2.1.2","2":"2.1.2","version_comment":"Added support for the vera and ldif filetypes. Thanks to Normandie\r\nAzucena and Florian Apolloner for the emails.\r\n","3":"Added support for the vera and ldif filetypes. Thanks to Normandie\r\nAzucena and Florian Apolloner for the emails.\r\n","package":"NERD_commenter.vim","4":"NERD_commenter.vim","src_id":"7543","5":"7543","creation_date":"1187750393","6":"1187750393"},{"0":"1218","vim_version":"6.0","1":"6.0","script_version":"2.1.1","2":"2.1.1","version_comment":"- added dummy support for SVNcommitlog and vcscommit. Thanks to John O'Shea for the email.\r\n- added support for Groovy. Thanks to Jason Mills for the email.\r\n","3":"- added dummy support for SVNcommitlog and vcscommit. Thanks to John O'Shea for the email.\r\n- added support for Groovy. Thanks to Jason Mills for the email.\r\n","package":"NERD_commenter.vim","4":"NERD_commenter.vim","src_id":"7525","5":"7525","creation_date":"1187459843","6":"1187459843"},{"0":"1218","vim_version":"6.0","1":"6.0","script_version":"2.1.0","2":"2.1.0","version_comment":"- now the script resets the delimiters when the filetype of the buffer changes (thanks to James Hales for the patch)\r\n- added formal support\/doc for prepending a count to many of the commenting maps so you can go, eg, 5,cc to comment 5 lines from normal  mode. Thanks again to James Hales for the patch.\r\n- added support for the \"gams\" filetype that Jorge Rodrigues created.\r\n- added support for the \"objc\" filetype, thanks to Rainer M\u00c3\u00bcller for the email.\r\n- added support for the \"sass\" filetype that Dmitry Ilyashevich created.","3":"- now the script resets the delimiters when the filetype of the buffer changes (thanks to James Hales for the patch)\r\n- added formal support\/doc for prepending a count to many of the commenting maps so you can go, eg, 5,cc to comment 5 lines from normal  mode. Thanks again to James Hales for the patch.\r\n- added support for the \"gams\" filetype that Jorge Rodrigues created.\r\n- added support for the \"objc\" filetype, thanks to Rainer M\u00c3\u00bcller for the email.\r\n- added support for the \"sass\" filetype that Dmitry Ilyashevich created.","package":"NERD_commenter.vim","4":"NERD_commenter.vim","src_id":"7466","5":"7466","creation_date":"1186544366","6":"1186544366"},{"0":"1218","vim_version":"6.0","1":"6.0","script_version":"2.0.7","2":"2.0.7","version_comment":"Added support for eclass and ebuild filetypes. Thanks to Alex Tarkovsky\r\nfor the email.\r\n","3":"Added support for eclass and ebuild filetypes. Thanks to Alex Tarkovsky\r\nfor the email.\r\n","package":"NERD_commenter.vim","4":"NERD_commenter.vim","src_id":"7391","5":"7391","creation_date":"1185081216","6":"1185081216"},{"0":"1218","vim_version":"6.0","1":"6.0","script_version":"2.0.6","2":"2.0.6","version_comment":"- Changed the default setting of NERDMapleader to \",c\", meaning all the maps now start with ,c instead of \\c. This is to stop a major mapping clash with the vcscommand plugin. Anyone wanting to keep the \\c map leader should read :help NERDMapleader.\r\n- Added support for debcontrol and dummy support for debchangelog filetypes, thanks to Stefano Zacchiroli for the email.\r\n- Made it so that the NERDShutUp option now only controls the \"Pleeease email the delimiters...\" requests. It no longer affects the general output of the script.\r\n- Simplified the names of the help tags. \r\n","3":"- Changed the default setting of NERDMapleader to \",c\", meaning all the maps now start with ,c instead of \\c. This is to stop a major mapping clash with the vcscommand plugin. Anyone wanting to keep the \\c map leader should read :help NERDMapleader.\r\n- Added support for debcontrol and dummy support for debchangelog filetypes, thanks to Stefano Zacchiroli for the email.\r\n- Made it so that the NERDShutUp option now only controls the \"Pleeease email the delimiters...\" requests. It no longer affects the general output of the script.\r\n- Simplified the names of the help tags. \r\n","package":"NERD_commenter.vim","4":"NERD_commenter.vim","src_id":"7309","5":"7309","creation_date":"1183096916","6":"1183096916"},{"0":"1218","vim_version":"6.0","1":"6.0","script_version":"2.0.5","2":"2.0.5","version_comment":"- Added support for autoit, autohotkey and docbk filetypes (thanks to  Michael B\u00c3\u00b6hler)\r\n- Added support for cmake (thanks to Aaron Small)\r\n- Added support for htmldjango and django filetypes (thanks to Ramiro  Morales)\r\n- Improved the delimiters for eruby again\r\n- Applied a patch from Seth Mason to fix some pathing issues with the help  file installation.\r\n","3":"- Added support for autoit, autohotkey and docbk filetypes (thanks to  Michael B\u00c3\u00b6hler)\r\n- Added support for cmake (thanks to Aaron Small)\r\n- Added support for htmldjango and django filetypes (thanks to Ramiro  Morales)\r\n- Improved the delimiters for eruby again\r\n- Applied a patch from Seth Mason to fix some pathing issues with the help  file installation.\r\n","package":"NERD_commenter.vim","4":"NERD_commenter.vim","src_id":"7253","5":"7253","creation_date":"1181958512","6":"1181958512"},{"0":"1218","vim_version":"6.0","1":"6.0","script_version":"2.0.4","2":"2.0.4","version_comment":"- Added support for verilog_systemverilog and systemverilog filetypes\r\n  (Thanks to Alexey for the email)\r\n- Added support for fstab, thanks to Lizendir for the email.\r\n- Added support for the smarty filetype.\r\n- Improved the delimiters for eruby.\r\n- Added dummy support for changelog filetype.\r\n","3":"- Added support for verilog_systemverilog and systemverilog filetypes\r\n  (Thanks to Alexey for the email)\r\n- Added support for fstab, thanks to Lizendir for the email.\r\n- Added support for the smarty filetype.\r\n- Improved the delimiters for eruby.\r\n- Added dummy support for changelog filetype.\r\n","package":"NERD_commenter.vim","4":"NERD_commenter.vim","src_id":"7097","5":"7097","creation_date":"1178857340","6":"1178857340"},{"0":"1218","vim_version":"6.0","1":"6.0","script_version":"2.0.3","2":"2.0.3","version_comment":"- Added dummy support for the csv filetype (thx to Mark Woodward for the\r\n  email)\r\n- Added dummy support for vo_base and otl filetypes (thanks to fREW for\r\n  the email)\r\n","3":"- Added dummy support for the csv filetype (thx to Mark Woodward for the\r\n  email)\r\n- Added dummy support for vo_base and otl filetypes (thanks to fREW for\r\n  the email)\r\n","package":"NERD_commenter.vim","4":"NERD_commenter.vim","src_id":"7060","5":"7060","creation_date":"1178155328","6":"1178155328"},{"0":"1218","vim_version":"6.0","1":"6.0","script_version":"2.0.2","2":"2.0.2","version_comment":"Minor bug fix that was stopping nested comments from working","3":"Minor bug fix that was stopping nested comments from working","package":"NERD_commenter.vim","4":"NERD_commenter.vim","src_id":"6977","5":"6977","creation_date":"1176495503","6":"1176495503"},{"0":"1218","vim_version":"6.0","1":"6.0","script_version":"2.0.1","2":"2.0.1","version_comment":"- Fixed the visual bell for the |NERDComToEOLMap| map.\r\n- Added another possible value to the NERDMenuMode option which causes the\r\n  menu to be displayed under 'Plugin -> Comment'. See :h NERDMenuMode.\r\n  This new menu mode is now the default.\r\n- Added support for the occam filetype (thanks to Anders for emailing me)\r\n- Made the main commenting function (NERDComment) available outside the\r\n  script. See :h NERD_com_NERDComment\r\n- bug fixes and refactoring\r\n","3":"- Fixed the visual bell for the |NERDComToEOLMap| map.\r\n- Added another possible value to the NERDMenuMode option which causes the\r\n  menu to be displayed under 'Plugin -> Comment'. See :h NERDMenuMode.\r\n  This new menu mode is now the default.\r\n- Added support for the occam filetype (thanks to Anders for emailing me)\r\n- Made the main commenting function (NERDComment) available outside the\r\n  script. See :h NERD_com_NERDComment\r\n- bug fixes and refactoring\r\n","package":"NERD_commenter.vim","4":"NERD_commenter.vim","src_id":"6972","5":"6972","creation_date":"1176350007","6":"1176350007"},{"0":"1218","vim_version":"6.0","1":"6.0","script_version":"2.0.0","2":"2.0.0","version_comment":"- NOTE: renamed the script to  NERD_commenter.vim. When you install this\r\n  version you must delete the old files: NERD_comments.vim and \r\n  NERD_comments.txt.\r\n- Reworked the mappings and main entry point function for the script to\r\n  avoid causing visual-bells and screen scrolling.\r\n- Changes to the script options (see |NERD_com-Customisation| for\r\n  details):\r\n    - They are all camel case now instead of underscored.\r\n    - Converted all of the regular expression options into simple boolean\r\n      options for simplicity.\r\n    - All the options are now stated positively, eg.\r\n      NERD_dont_remove_spaces_regexp has become NERDRemoveExtraSpaces.\r\n    - Some of the option names have been changed (other than in the above\r\n      ways)\r\n    - Some have been removed altogether, namely: NERD_create_h_filetype\r\n      (why was a commenting script creating a filetype?!),\r\n      NERD_left_align_regexp, NERD_right_align_regexp, \r\n\r\n- Removed all the NERD_use_alt_style_XXX_coms options and replaced them\r\n  with a better system. Now if a filetype has alternative delims, the\r\n  script will check whether an option of the form\r\n  \"NERD_<&filetype>_alt_style\" exists, and if it does then alt delims will\r\n  be used. See |NERD_com-cust-delims| for details.\r\n- The script no longer removes extra spaces for sexy comments for the\r\n  NERDRemoveExtraSpaces option (it will still remove spaces if\r\n  NERDSpaceDelims is set).\r\n- Added dummy support for viminfo and rtf.\r\n- Added support for the \"gentoo-package-\\(keywords\\|mask\\|use\\)\"\r\n  filetypes.\r\n- Added '#' comments as an alternative for the asm filetype\r\n\r\nThanks to Markus Klinik and Anders for bug reports, and again to Anders\r\nfor his patch. Thanks to John O'Shea and fREW for the filetype\r\ninformation.\r\n","3":"- NOTE: renamed the script to  NERD_commenter.vim. When you install this\r\n  version you must delete the old files: NERD_comments.vim and \r\n  NERD_comments.txt.\r\n- Reworked the mappings and main entry point function for the script to\r\n  avoid causing visual-bells and screen scrolling.\r\n- Changes to the script options (see |NERD_com-Customisation| for\r\n  details):\r\n    - They are all camel case now instead of underscored.\r\n    - Converted all of the regular expression options into simple boolean\r\n      options for simplicity.\r\n    - All the options are now stated positively, eg.\r\n      NERD_dont_remove_spaces_regexp has become NERDRemoveExtraSpaces.\r\n    - Some of the option names have been changed (other than in the above\r\n      ways)\r\n    - Some have been removed altogether, namely: NERD_create_h_filetype\r\n      (why was a commenting script creating a filetype?!),\r\n      NERD_left_align_regexp, NERD_right_align_regexp, \r\n\r\n- Removed all the NERD_use_alt_style_XXX_coms options and replaced them\r\n  with a better system. Now if a filetype has alternative delims, the\r\n  script will check whether an option of the form\r\n  \"NERD_<&filetype>_alt_style\" exists, and if it does then alt delims will\r\n  be used. See |NERD_com-cust-delims| for details.\r\n- The script no longer removes extra spaces for sexy comments for the\r\n  NERDRemoveExtraSpaces option (it will still remove spaces if\r\n  NERDSpaceDelims is set).\r\n- Added dummy support for viminfo and rtf.\r\n- Added support for the \"gentoo-package-\\(keywords\\|mask\\|use\\)\"\r\n  filetypes.\r\n- Added '#' comments as an alternative for the asm filetype\r\n\r\nThanks to Markus Klinik and Anders for bug reports, and again to Anders\r\nfor his patch. Thanks to John O'Shea and fREW for the filetype\r\ninformation.\r\n","package":"NERD_commenter.vim","4":"NERD_commenter.vim","src_id":"6938","5":"6938","creation_date":"1175544996","6":"1175544996"}]},"1217":{"script_id":"1217","0":"1217","script_name":"Perldoc from VIM","1":"Perldoc from VIM","script_type":"ftplugin","2":"ftplugin","summary":"Perldoc from VIM","3":"Perldoc from VIM","description":"This script gives you direct access to perldoc documentation from inside VIM.\r\nPerldoc support is automatically activated when editing perl files.\r\n\r\nRequirements: \"perl\" v5.004 (or better) and \"perldoc\" must be accessible from your command line. Also, module Pod::Text::Termcap must be installed.\r\n\r\nUsage: After installing (see below), edit a perlfile, press <F3>, enter name of wanted perldoc-page.\r\nA new window is opened (presuming the wanted page exists), hopefully containing what you're looking for - a perldoc page, tuned up with some VIM syntaxhighlighting, generated from POD informations.\r\n\r\nPerldoc pages that have already been retrieved earlier are taken from cache.\r\nThis speeds up the search and avoids double generation of VIM's synhighlight-commands.\r\n\r\nYou'll need to specify a directory where the cached perldoc-pages will be stored. This is done in the 2nd line of pdoc4vim.vim (you'll be guided there automatically if a valid entry couldn't be found).\r\nOf course you can change the perldoc-key (default: F3) too, just check out the first lines from pdoc4vim.vim.","4":"This script gives you direct access to perldoc documentation from inside VIM.\r\nPerldoc support is automatically activated when editing perl files.\r\n\r\nRequirements: \"perl\" v5.004 (or better) and \"perldoc\" must be accessible from your command line. Also, module Pod::Text::Termcap must be installed.\r\n\r\nUsage: After installing (see below), edit a perlfile, press <F3>, enter name of wanted perldoc-page.\r\nA new window is opened (presuming the wanted page exists), hopefully containing what you're looking for - a perldoc page, tuned up with some VIM syntaxhighlighting, generated from POD informations.\r\n\r\nPerldoc pages that have already been retrieved earlier are taken from cache.\r\nThis speeds up the search and avoids double generation of VIM's synhighlight-commands.\r\n\r\nYou'll need to specify a directory where the cached perldoc-pages will be stored. This is done in the 2nd line of pdoc4vim.vim (you'll be guided there automatically if a valid entry couldn't be found).\r\nOf course you can change the perldoc-key (default: F3) too, just check out the first lines from pdoc4vim.vim.","install_details":"- Store pdoc4vim.vim somewhere it doesn't bother you, e.g. in $vim\/vimfiles directory.\r\n- Add this line to the file $vim\/vimfiles\/ftplugin\/perl.vim (create if it doesn't exist):\r\n  source <path to pdoc4vim.vim>\r\n  e.g.: source $vim\/vimfiles\/pdoc4vim.vim\r\n- Open an existing *.pl-file (or create a new one, starting with :set filetype=perl),\r\n  press F3. Follow instructions on screen.","5":"- Store pdoc4vim.vim somewhere it doesn't bother you, e.g. in $vim\/vimfiles directory.\r\n- Add this line to the file $vim\/vimfiles\/ftplugin\/perl.vim (create if it doesn't exist):\r\n  source <path to pdoc4vim.vim>\r\n  e.g.: source $vim\/vimfiles\/pdoc4vim.vim\r\n- Open an existing *.pl-file (or create a new one, starting with :set filetype=perl),\r\n  press F3. Follow instructions on screen.","first_name":"Johannes","6":"Johannes","last_name":"Petzold","7":"Petzold","releases":[{"0":"1217","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"pdoc4vim.vim","4":"pdoc4vim.vim","src_id":"3906","5":"3906","creation_date":"1109260342","6":"1109260342"}]},"1216":{"script_id":"1216","0":"1216","script_name":"cool.vim","1":"cool.vim","script_type":"syntax","2":"syntax","summary":"Syntax Highlighting for COOL (Classroom Object Oriented Language)","3":"Syntax Highlighting for COOL (Classroom Object Oriented Language)","description":"Highlight all basic contructs in cool.","4":"Highlight all basic contructs in cool.","install_details":"place in your .vim\/syntax folder \r\nyou also need to set up a rule to associate .cool or .cl files with cool\r\n\r\n\"Cool files\r\nau BufNewFile,BufRead *.cool setf cool\r\n","5":"place in your .vim\/syntax folder \r\nyou also need to set up a rule to associate .cool or .cl files with cool\r\n\r\n\"Cool files\r\nau BufNewFile,BufRead *.cool setf cool\r\n","first_name":"John","6":"John","last_name":"Carrino","7":"Carrino","releases":[{"0":"1216","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"cool.vim","4":"cool.vim","src_id":"3900","5":"3900","creation_date":"1109163990","6":"1109163990"}]},"1215":{"script_id":"1215","0":"1215","script_name":"Super Shell Indent","1":"Super Shell Indent","script_type":"indent","2":"indent","summary":"Improved indentation for shell scripts","3":"Improved indentation for shell scripts","description":"This is a shell indentation script that calculates the indent level based on begin\/end syntax pairs, as opposed to complex conditionals and pattern matching.\r\n\r\nThis script also introduces indentation for:\r\n\r\n           case blocks \r\n           paren blocks\r\n           '[[' blocks\r\n           line continuation\r\n\r\nIt's slower than the stock indentation, but IMHO, it doesn the \"right\" thing much more often.  :)\r\n\r\n","4":"This is a shell indentation script that calculates the indent level based on begin\/end syntax pairs, as opposed to complex conditionals and pattern matching.\r\n\r\nThis script also introduces indentation for:\r\n\r\n           case blocks \r\n           paren blocks\r\n           '[[' blocks\r\n           line continuation\r\n\r\nIt's slower than the stock indentation, but IMHO, it doesn the \"right\" thing much more often.  :)\r\n\r\n","install_details":"This script was written for and tested on vim 6.3.  Earlier versions may not do the right thing...\r\n\r\nPlace in ~\/.vim\/indent\/ and let 'er rip!","5":"This script was written for and tested on vim 6.3.  Earlier versions may not do the right thing...\r\n\r\nPlace in ~\/.vim\/indent\/ and let 'er rip!","first_name":"Tye","6":"Tye","last_name":"Zdrojewski","7":"Zdrojewski","releases":[{"0":"1215","vim_version":"6.0","1":"6.0","script_version":"1.6","2":"1.6","version_comment":"Noticeable performance improvement","3":"Noticeable performance improvement","package":"sh.vim","4":"sh.vim","src_id":"4371","5":"4371","creation_date":"1119013027","6":"1119013027"},{"0":"1215","vim_version":"6.0","1":"6.0","script_version":"1.5","2":"1.5","version_comment":"- Fixed indentation of first line in a file\r\n- Fixed ignoring of certain keywords in comments\r\n- Tested on 6.2\r\n","3":"- Fixed indentation of first line in a file\r\n- Fixed ignoring of certain keywords in comments\r\n- Tested on 6.2\r\n","package":"sh.vim","4":"sh.vim","src_id":"4097","5":"4097","creation_date":"1112168183","6":"1112168183"},{"0":"1215","vim_version":"6.0","1":"6.0","script_version":"1.4","2":"1.4","version_comment":"- Fixed infinite loop\r\n- Ignore line-continuation chars in comments and strings","3":"- Fixed infinite loop\r\n- Ignore line-continuation chars in comments and strings","package":"sh.vim","4":"sh.vim","src_id":"3965","5":"3965","creation_date":"1109943790","6":"1109943790"},{"0":"1215","vim_version":"6.0","1":"6.0","script_version":"1.3","2":"1.3","version_comment":"- fixed elif (again)\r\n","3":"- fixed elif (again)\r\n","package":"sh.vim","4":"sh.vim","src_id":"3905","5":"3905","creation_date":"1109242501","6":"1109242501"},{"0":"1215","vim_version":"6.0","1":"6.0","script_version":"1.2","2":"1.2","version_comment":"- Ignore open\/close pairs that are in strings\r\n- Fixed super_sh_indent_echo\r\n- Fixed else\/elif\r\n","3":"- Ignore open\/close pairs that are in strings\r\n- Fixed super_sh_indent_echo\r\n- Fixed else\/elif\r\n","package":"sh.vim","4":"sh.vim","src_id":"3904","5":"3904","creation_date":"1109241829","6":"1109241829"},{"0":"1215","vim_version":"6.0","1":"6.0","script_version":"1.1","2":"1.1","version_comment":"Initial upload","3":"Initial upload","package":"sh.vim","4":"sh.vim","src_id":"3899","5":"3899","creation_date":"1109144732","6":"1109144732"}]},"1214":{"script_id":"1214","0":"1214","script_name":"cvsdiff.vim","1":"cvsdiff.vim","script_type":"utility","2":"utility","summary":"visual cvs diff utility for vim diffsplit, horizontal or vertical","3":"visual cvs diff utility for vim diffsplit, horizontal or vertical","description":"vim plugin to for visual display of cvs diff in vim using vim diffsplit\r\n\r\n1) used as vim command, format :Cvsdiff [v] [version #]\r\n    :Cvsdiff     \r\n       -- diff between opened file and lastest cvs version, \r\n           horizontal split\r\n    :Cvsdiff  v\r\n       -- diff between opened file and lastest cvs version, \r\n           vertical split\r\n    :Cvsdiff <version #>  example  :Cvsdiff 1.2\r\n       -- diff between opened file and cvs version #, horizontal split\r\n    :Cvsdiff v <version #>  example  :Cvsdiff v 1.2\r\n       -- diff between opened file and cvs version #, vertical split\r\n2) map to key \r\n    can create mapping in ~\/.vimrc by adding following lines, examples\r\n    map <F8> <Plug>Cvsdiff\r\n        -- press F8 in vim, show diff to cvs last version, horizontal split\r\n    map <F7> <Plug>Cvsdiffv\r\n        -- press F7 in vim, show diff to cvs last version, vertical split\r\n\r\nerror report: \r\n    eji@yahoo-inc.com\r\n    feel free to customize it, distribute it or do whatever you want.\r\n\r\n","4":"vim plugin to for visual display of cvs diff in vim using vim diffsplit\r\n\r\n1) used as vim command, format :Cvsdiff [v] [version #]\r\n    :Cvsdiff     \r\n       -- diff between opened file and lastest cvs version, \r\n           horizontal split\r\n    :Cvsdiff  v\r\n       -- diff between opened file and lastest cvs version, \r\n           vertical split\r\n    :Cvsdiff <version #>  example  :Cvsdiff 1.2\r\n       -- diff between opened file and cvs version #, horizontal split\r\n    :Cvsdiff v <version #>  example  :Cvsdiff v 1.2\r\n       -- diff between opened file and cvs version #, vertical split\r\n2) map to key \r\n    can create mapping in ~\/.vimrc by adding following lines, examples\r\n    map <F8> <Plug>Cvsdiff\r\n        -- press F8 in vim, show diff to cvs last version, horizontal split\r\n    map <F7> <Plug>Cvsdiffv\r\n        -- press F7 in vim, show diff to cvs last version, vertical split\r\n\r\nerror report: \r\n    eji@yahoo-inc.com\r\n    feel free to customize it, distribute it or do whatever you want.\r\n\r\n","install_details":"copy this file to your vim plugin directory, normally ~\/.vim\/plugin\r\nif not, can manally source this file in vim or add into ~\/.vimrc\r\n   :source cvsdiff.vim","5":"copy this file to your vim plugin directory, normally ~\/.vim\/plugin\r\nif not, can manally source this file in vim or add into ~\/.vimrc\r\n   :source cvsdiff.vim","first_name":"Eric","6":"Eric","last_name":"Ji","7":"Ji","releases":[{"0":"1214","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"cvsdiff.vim","4":"cvsdiff.vim","src_id":"3897","5":"3897","creation_date":"1109119679","6":"1109119679"}]},"1213":{"script_id":"1213","0":"1213","script_name":"Vim JDE","1":"Vim JDE","script_type":"utility","2":"utility","summary":"Vim - Just a Development Envirement (Java\/C++)","3":"Vim - Just a Development Envirement (Java\/C++)","description":"Just  a  Development Environment  for VIM . (VJDE)\r\nAnd now , It's support C++\/C by ctags\r\n(VIM>=700  , +ruby future is on , JDK 1.5 support , JDK1.4 (maybe, not tested))\r\n\r\nIt's Had  been tested on Leopard 10.5.1 .\r\n\r\nuse <c-space> as the Code completion key!\r\nchange it by \r\n:let g:vjde_completion_key='<c-space>'\r\n\r\ndoc http:\/\/www.hiibox.com\/vjde-tut\/index.htm .\r\nA quick refrence create by Andrea Spadaccini http:\/\/media.cqic.com.cn\/vjde-tut\/vJDE_qr.pdf\r\n\r\nEnglish Version will coming soon.\r\nJust work for :\r\n       Project manager (load\/store  your VJDE settings)\r\n       Code completion ( working for java and jsp,taglib,html,xml,xsl,xsd) (VIM 7.0 required)\r\n       Source tools( variable extract local, member,argument,  extract number or String to constance , fix build\r\n                             unreported exception error ( depends on getqflist() )\r\n        Source tools ( Override methods, implements interface,extract import, sort import)\r\n       Create javadoc (depends on jcommentor.vim)\r\n       Create getter\/setter stub.\r\n       Generate constructor of class which has all member;\r\n(2009-04-03\r\n      Support for annotation completion.\r\nNew(2005-09-08)\r\n       Use readtags for tags parse.\r\n       Bug fix.\r\nNew(2005-09-02)\r\n       Code completion for more language available .(require ctags)\r\n       let g:vjde_ctags_exts='vim;rb'\r\n       Code template more powerfull!\r\n      Put your own definition file , such as c.iab,vim.iab,cpp.iab ruby.iab to ~\/.vim\/vjde\/\r\n       let g:vjde_iab_exts='c;vim;cpp;rb'\r\n      in you c\/c++\/vim\/ruby file, you can use <c-j>\r\n      \r\nNew(2005-09-01)\r\n       More beautiful document viewer. ^_^\r\n       C++\/C Code completion support for both GUI and Console\r\n       C++\/C parameter information support for both GUI and Console\r\n       use:\r\n       ctags --c++-kinds=+px -R .\r\n       For search speed , Befor your use Code completion,\r\n      use:\r\n       :call VjdeCppGenerateIdx()\r\n      to generate a index file for your every tag file.\r\n      see vcde.txt for detail\r\nNew (2005-08-27)\r\n       Add JAVA document preview in GUI mode\r\n       Add code template like (for block...) in console mode.\r\n       Improved Preview window.\r\nNew (2005-09-01)\r\n        More beautiful document window.^_^\r\n        C++\/C preview support\r\n       C++\/C parameter information support.\r\n\r\nNew (2005-08-22)\r\n         Add import statement for classes .\r\n         Add code template like (for block, while block...)\r\n         Create javadoc (depends on jcommentor.vim)\r\n         Create getter\/setter stub.\r\n         Generate constructor of class which has all member;\r\n         Allow    write your own template file in: ~\/vim\/.vjde\/iab.vjde\r\n                                see vimfile\/plugin\/vjde\/tlds\/iab.vjde for detail.\r\n         Bugfix for vim install on a folder like : c:\\program files\\vim..\r\n         Add menu shortcut.\r\nNew (2005-04-30) Add sensitive java code support for dot '.' , '@',\r\n       Add sensitive Jsp code support for '<' ':' and space.\r\nNew . Code completion support for packages.\r\n         import java.net.<CTR>-x<CTR>-u\r\n\r\n         or in coding:\r\n               java.io.<CTR>-x<CTR>-u\r\n\r\n        Code completion      \r\n\t\tThis future is depends on JDK, the java reflect API.\r\n               available for\r\n                System.<CTR>-x<CTR>-u\r\n                System.o<CTR>-x<CTR>-u\r\n                System.out.<CTR>-x<CTR>-u\r\n            \r\n               a[+-*\/%&|^=] str.<CTR>-x<CTR>-u\r\n              \r\n               return str.<CTR>-x<CTR>-u\r\n                \r\n                new Something(str.<CTR>-x<CTR>-u\r\n         Use it , enjoy it.\r\n         Completion for jsp\r\n                <jsp:<CTR>-x<CTR>-u\r\n                <jsp:include <CTR>-x<CTR>-u\r\n                <jsp:include flush=\"<CTR>-x<CTR>-u\r\n                <jsp:us<CTR>-x<CTR>-u\r\n         Completion for taglib (ie. STL)\r\n           <%@ taglib prefix=\"c\" uri=\"http:\/\/java.sun.com\/jsp\/jstl\/core\";%>\r\n             :XMLns stl_c c\r\n             <c:<CTR>-x<CTR>-u\r\n             <c:out <CTR>-x<CTR>-u\r\n             .....\r\n \r\n         Completion for xml ....(See doc for detail...)\r\n\r\n\r\n        Definition search ( User Command    :Vjdei)\r\n                you can list a class or a field or a method detail\r\n                For example:\r\n                 System.out.println(str.toUpperCase().tr....\r\n                Place cursor on the class System, the detail of System  would be shown , Constructor, fields\r\n,methods, inner class ...\r\n\r\n            \r\nTODO list :\r\n\r\n\r\nTanks for every one who's name is occurred in my source code. ^_^ \r\n\r\n","4":"Just  a  Development Environment  for VIM . (VJDE)\r\nAnd now , It's support C++\/C by ctags\r\n(VIM>=700  , +ruby future is on , JDK 1.5 support , JDK1.4 (maybe, not tested))\r\n\r\nIt's Had  been tested on Leopard 10.5.1 .\r\n\r\nuse <c-space> as the Code completion key!\r\nchange it by \r\n:let g:vjde_completion_key='<c-space>'\r\n\r\ndoc http:\/\/www.hiibox.com\/vjde-tut\/index.htm .\r\nA quick refrence create by Andrea Spadaccini http:\/\/media.cqic.com.cn\/vjde-tut\/vJDE_qr.pdf\r\n\r\nEnglish Version will coming soon.\r\nJust work for :\r\n       Project manager (load\/store  your VJDE settings)\r\n       Code completion ( working for java and jsp,taglib,html,xml,xsl,xsd) (VIM 7.0 required)\r\n       Source tools( variable extract local, member,argument,  extract number or String to constance , fix build\r\n                             unreported exception error ( depends on getqflist() )\r\n        Source tools ( Override methods, implements interface,extract import, sort import)\r\n       Create javadoc (depends on jcommentor.vim)\r\n       Create getter\/setter stub.\r\n       Generate constructor of class which has all member;\r\n(2009-04-03\r\n      Support for annotation completion.\r\nNew(2005-09-08)\r\n       Use readtags for tags parse.\r\n       Bug fix.\r\nNew(2005-09-02)\r\n       Code completion for more language available .(require ctags)\r\n       let g:vjde_ctags_exts='vim;rb'\r\n       Code template more powerfull!\r\n      Put your own definition file , such as c.iab,vim.iab,cpp.iab ruby.iab to ~\/.vim\/vjde\/\r\n       let g:vjde_iab_exts='c;vim;cpp;rb'\r\n      in you c\/c++\/vim\/ruby file, you can use <c-j>\r\n      \r\nNew(2005-09-01)\r\n       More beautiful document viewer. ^_^\r\n       C++\/C Code completion support for both GUI and Console\r\n       C++\/C parameter information support for both GUI and Console\r\n       use:\r\n       ctags --c++-kinds=+px -R .\r\n       For search speed , Befor your use Code completion,\r\n      use:\r\n       :call VjdeCppGenerateIdx()\r\n      to generate a index file for your every tag file.\r\n      see vcde.txt for detail\r\nNew (2005-08-27)\r\n       Add JAVA document preview in GUI mode\r\n       Add code template like (for block...) in console mode.\r\n       Improved Preview window.\r\nNew (2005-09-01)\r\n        More beautiful document window.^_^\r\n        C++\/C preview support\r\n       C++\/C parameter information support.\r\n\r\nNew (2005-08-22)\r\n         Add import statement for classes .\r\n         Add code template like (for block, while block...)\r\n         Create javadoc (depends on jcommentor.vim)\r\n         Create getter\/setter stub.\r\n         Generate constructor of class which has all member;\r\n         Allow    write your own template file in: ~\/vim\/.vjde\/iab.vjde\r\n                                see vimfile\/plugin\/vjde\/tlds\/iab.vjde for detail.\r\n         Bugfix for vim install on a folder like : c:\\program files\\vim..\r\n         Add menu shortcut.\r\nNew (2005-04-30) Add sensitive java code support for dot '.' , '@',\r\n       Add sensitive Jsp code support for '<' ':' and space.\r\nNew . Code completion support for packages.\r\n         import java.net.<CTR>-x<CTR>-u\r\n\r\n         or in coding:\r\n               java.io.<CTR>-x<CTR>-u\r\n\r\n        Code completion      \r\n\t\tThis future is depends on JDK, the java reflect API.\r\n               available for\r\n                System.<CTR>-x<CTR>-u\r\n                System.o<CTR>-x<CTR>-u\r\n                System.out.<CTR>-x<CTR>-u\r\n            \r\n               a[+-*\/%&|^=] str.<CTR>-x<CTR>-u\r\n              \r\n               return str.<CTR>-x<CTR>-u\r\n                \r\n                new Something(str.<CTR>-x<CTR>-u\r\n         Use it , enjoy it.\r\n         Completion for jsp\r\n                <jsp:<CTR>-x<CTR>-u\r\n                <jsp:include <CTR>-x<CTR>-u\r\n                <jsp:include flush=\"<CTR>-x<CTR>-u\r\n                <jsp:us<CTR>-x<CTR>-u\r\n         Completion for taglib (ie. STL)\r\n           <%@ taglib prefix=\"c\" uri=\"http:\/\/java.sun.com\/jsp\/jstl\/core\";%>\r\n             :XMLns stl_c c\r\n             <c:<CTR>-x<CTR>-u\r\n             <c:out <CTR>-x<CTR>-u\r\n             .....\r\n \r\n         Completion for xml ....(See doc for detail...)\r\n\r\n\r\n        Definition search ( User Command    :Vjdei)\r\n                you can list a class or a field or a method detail\r\n                For example:\r\n                 System.out.println(str.toUpperCase().tr....\r\n                Place cursor on the class System, the detail of System  would be shown , Constructor, fields\r\n,methods, inner class ...\r\n\r\n            \r\nTODO list :\r\n\r\n\r\nTanks for every one who's name is occurred in my source code. ^_^ \r\n\r\n","install_details":"unzip this file\r\n         tar -xzf vjde.tgz  \/usr\/share\/vim\/vimfiles\r\n         chmod +x \/usr\/share\/vim\/vimfiles\/plugin\/vjde\/readtags\r\n\r\nstart vim\r\n          :helptags \/usr\/share\/vim\/vimfiles\/doc\r\n          :h vjde\r\n\r\nTo use VJDE GUI preview , add the preview.dll of old version for the latest version.","5":"unzip this file\r\n         tar -xzf vjde.tgz  \/usr\/share\/vim\/vimfiles\r\n         chmod +x \/usr\/share\/vim\/vimfiles\/plugin\/vjde\/readtags\r\n\r\nstart vim\r\n          :helptags \/usr\/share\/vim\/vimfiles\/doc\r\n          :h vjde\r\n\r\nTo use VJDE GUI preview , add the preview.dll of old version for the latest version.","first_name":"JiuTian","6":"JiuTian","last_name":"Zhang","7":"Zhang","releases":[{"0":"1213","vim_version":"7.0","1":"7.0","script_version":"2.7.0","2":"2.7.0","version_comment":"new version.bug fix. add <c-x><c-o> after HashMap<String,String> abc =new <c-x><c-o> . ","3":"new version.bug fix. add <c-x><c-o> after HashMap<String,String> abc =new <c-x><c-o> . ","package":"vjde.tgz","4":"vjde.tgz","src_id":"24430","5":"24430","creation_date":"1470287345","6":"1470287345"},{"0":"1213","vim_version":"7.0","1":"7.0","script_version":"2.6.18","2":"2.6.18","version_comment":"change the encoding of somefiles","3":"change the encoding of somefiles","package":"vjde.tgz","4":"vjde.tgz","src_id":"17026","5":"17026","creation_date":"1323066815","6":"1323066815"},{"0":"1213","vim_version":"7.0","1":"7.0","script_version":"2.6.17","2":"2.6.17","version_comment":"Bug fix for smartcase or caseignore option.\r\nFixed by Silver Gibiansky.","3":"Bug fix for smartcase or caseignore option.\r\nFixed by Silver Gibiansky.","package":"vjde.tgz","4":"vjde.tgz","src_id":"16253","5":"16253","creation_date":"1313213068","6":"1313213068"},{"0":"1213","vim_version":"7.0","1":"7.0","script_version":"2.6.16","2":"2.6.16","version_comment":"add \r\nlet g:vjde_tab_cfu=1\r\nin your _vimrc,\r\nthen you can use <tab> to finish the completion.\r\nSystem.<tab>\r\nSystem.<c-x><c-u> \r\nwill show the same result.","3":"add \r\nlet g:vjde_tab_cfu=1\r\nin your _vimrc,\r\nthen you can use <tab> to finish the completion.\r\nSystem.<tab>\r\nSystem.<c-x><c-u> \r\nwill show the same result.","package":"vjde.tgz","4":"vjde.tgz","src_id":"15998","5":"15998","creation_date":"1309275200","6":"1309275200"},{"0":"1213","vim_version":"7.0","1":"7.0","script_version":"2.16.5","2":"2.16.5","version_comment":"add completion for constructor:\r\nArrayList<String> abc = new <c-x><c-u> \r\nwill completion\r\nArrayList<String> abc = new ArrayList<String>(","3":"add completion for constructor:\r\nArrayList<String> abc = new <c-x><c-u> \r\nwill completion\r\nArrayList<String> abc = new ArrayList<String>(","package":"vjde.tgz","4":"vjde.tgz","src_id":"15997","5":"15997","creation_date":"1309269914","6":"1309269914"},{"0":"1213","vim_version":"7.0","1":"7.0","script_version":"2.16.4","2":"2.16.4","version_comment":"1. improved for completion :\r\nnew java.<c-x><c-u>\r\n2. add <leader>ii to implements a interface with an anonymous class.\r\nnew Thread(new Runnable() {   <--here ,<leader>ii\r\n\r\nwould add the function of Runnable.","3":"1. improved for completion :\r\nnew java.<c-x><c-u>\r\n2. add <leader>ii to implements a interface with an anonymous class.\r\nnew Thread(new Runnable() {   <--here ,<leader>ii\r\n\r\nwould add the function of Runnable.","package":"vjde.tgz","4":"vjde.tgz","src_id":"14254","5":"14254","creation_date":"1289729461","6":"1289729461"},{"0":"1213","vim_version":"7.0","1":"7.0","script_version":"2.16.2","2":"2.16.2","version_comment":"bug fix for LINUX and MAC OS . ","3":"bug fix for LINUX and MAC OS . ","package":"vjde.tgz","4":"vjde.tgz","src_id":"10992","5":"10992","creation_date":"1247287196","6":"1247287196"},{"0":"1213","vim_version":"7.0","1":"7.0","script_version":"2.16.1","2":"2.16.1","version_comment":"completion bug fix for something like javax.naming.* \r\n","3":"completion bug fix for something like javax.naming.* \r\n","package":"vjde.tgz","4":"vjde.tgz","src_id":"10894","5":"10894","creation_date":"1245939409","6":"1245939409"},{"0":"1213","vim_version":"7.0","1":"7.0","script_version":"2.16.0","2":"2.16.0","version_comment":"Support for annotation completion.\r\nLine completion support :\r\nI just support for one line\r\n@Actions ( { @Action ( results={@Result \r\n","3":"Support for annotation completion.\r\nLine completion support :\r\nI just support for one line\r\n@Actions ( { @Action ( results={@Result \r\n","package":"vjde.tgz","4":"vjde.tgz","src_id":"10098","5":"10098","creation_date":"1236152202","6":"1236152202"},{"0":"1213","vim_version":"7.0","1":"7.0","script_version":"2.15.2","2":"2.15.2","version_comment":"bug fix for java code completion in jsp.","3":"bug fix for java code completion in jsp.","package":"vjde.tgz","4":"vjde.tgz","src_id":"10014","5":"10014","creation_date":"1235413430","6":"1235413430"},{"0":"1213","vim_version":"7.0","1":"7.0","script_version":"2.15.1","2":"2.15.1","version_comment":"improve for taglib completion in jsp file.","3":"improve for taglib completion in jsp file.","package":"vjde.tgz","4":"vjde.tgz","src_id":"10012","5":"10012","creation_date":"1235403130","6":"1235403130"},{"0":"1213","vim_version":"7.0","1":"7.0","script_version":"2.15.0","2":"2.15.0","version_comment":"add completion support for taglib, It's automaticaly enabled for JSTL,JSF.\r\nonce your input <%@ taglib prefix=\"<c-x><c-u> , you can select your taglib\r\n<c:<c-x><c-u>\r\n:h g:vjde_taglib_uri","3":"add completion support for taglib, It's automaticaly enabled for JSTL,JSF.\r\nonce your input <%@ taglib prefix=\"<c-x><c-u> , you can select your taglib\r\n<c:<c-x><c-u>\r\n:h g:vjde_taglib_uri","package":"vjde.tgz","4":"vjde.tgz","src_id":"10000","5":"10000","creation_date":"1235177677","6":"1235177677"},{"0":"1213","vim_version":"7.0","1":"7.0","script_version":"2.14.6","2":"2.14.6","version_comment":"bug fix for package completion. tested on jdk.1.6.0_01,\r\ncompiled with ant , options target=\"1.4\" source=\"1.4\"","3":"bug fix for package completion. tested on jdk.1.6.0_01,\r\ncompiled with ant , options target=\"1.4\" source=\"1.4\"","package":"vjde.tgz","4":"vjde.tgz","src_id":"9806","5":"9806","creation_date":"1231819069","6":"1231819069"},{"0":"1213","vim_version":"6.0","1":"6.0","script_version":"2.14.4","2":"2.14.4","version_comment":"compile with JDK1.5","3":"compile with JDK1.5","package":"vjde.tgz","4":"vjde.tgz","src_id":"8448","5":"8448","creation_date":"1205389798","6":"1205389798"},{"0":"1213","vim_version":"7.0","1":"7.0","script_version":"2.14.2","2":"2.14.2","version_comment":"Fix completion for this.<c-x><c-u> \r\nFix for VjdeDtd2Data","3":"Fix completion for this.<c-x><c-u> \r\nFix for VjdeDtd2Data","package":"vjde.tgz","4":"vjde.tgz","src_id":"8060","5":"8060","creation_date":"1197759895","6":"1197759895"},{"0":"1213","vim_version":"7.0","1":"7.0","script_version":"2.14.1","2":"2.14.1","version_comment":"bug fix for linux system.","3":"bug fix for linux system.","package":"vjde.tgz","4":"vjde.tgz","src_id":"7489","5":"7489","creation_date":"1186782462","6":"1186782462"},{"0":"1213","vim_version":"7.0","1":"7.0","script_version":"2.14","2":"2.14","version_comment":"completion for parameters of a constructor \r\ncompletion for name of the package which is come from JDK.","3":"completion for parameters of a constructor \r\ncompletion for name of the package which is come from JDK.","package":"vjde.tgz","4":"vjde.tgz","src_id":"7411","5":"7411","creation_date":"1185323930","6":"1185323930"},{"0":"1213","vim_version":"7.0","1":"7.0","script_version":"2.13.3","2":"2.13.3","version_comment":"Buf fix for parameter preview.\r\n    System.arraycopy(<c-x><c-u>\r\nAfter a \"(\", use <c-x><c-u> would show the parameter info of this function.","3":"Buf fix for parameter preview.\r\n    System.arraycopy(<c-x><c-u>\r\nAfter a \"(\", use <c-x><c-u> would show the parameter info of this function.","package":"vjde.tgz","4":"vjde.tgz","src_id":"6520","5":"6520","creation_date":"1166405447","6":"1166405447"},{"0":"1213","vim_version":"7.0","1":"7.0","script_version":"2.13.2","2":"2.13.2","version_comment":"Fix a bug of document viewer : Once  vim lost the focus, the document viewer can't be found , can't be closed .^_^","3":"Fix a bug of document viewer : Once  vim lost the focus, the document viewer can't be found , can't be closed .^_^","package":"vjde.tgz","4":"vjde.tgz","src_id":"6191","5":"6191","creation_date":"1158537983","6":"1158537983"},{"0":"1213","vim_version":"7.0","1":"7.0","script_version":"2.13.1","2":"2.13.1","version_comment":"Bug fix for cast statement.\r\nAdd JavaDoc viewer. During your completion, use the <f1> to call the JavaDoc Viewer. Setup your JavaDoc Path in vimrc:\r\nlet g:vjde_javadoc_path='e:\/downloads\/java\/docs\/api'\r\n\r\nAdd Function to remove all import statement which is not used.\r\nUse the command <leader>ri . Remove Import.\r\n\r\nA clear version.","3":"Bug fix for cast statement.\r\nAdd JavaDoc viewer. During your completion, use the <f1> to call the JavaDoc Viewer. Setup your JavaDoc Path in vimrc:\r\nlet g:vjde_javadoc_path='e:\/downloads\/java\/docs\/api'\r\n\r\nAdd Function to remove all import statement which is not used.\r\nUse the command <leader>ri . Remove Import.\r\n\r\nA clear version.","package":"vjde.tgz","4":"vjde.tgz","src_id":"6178","5":"6178","creation_date":"1158177620","6":"1158177620"},{"0":"1213","vim_version":"7.0","1":"7.0","script_version":"2.12.5","2":"2.12.5","version_comment":"Bug fix for code template.\r\nTake affect on code template completion . For example  i<alt-.>\r\nto generate if () { \r\n} ","3":"Bug fix for code template.\r\nTake affect on code template completion . For example  i<alt-.>\r\nto generate if () { \r\n} ","package":"vjde.tgz","4":"vjde.tgz","src_id":"6085","5":"6085","creation_date":"1156124767","6":"1156124767"},{"0":"1213","vim_version":"7.0","1":"7.0","script_version":"2.12.4","2":"2.12.4","version_comment":"修改了 代码模板 提 示的 bug.\r\n用于 if<alt-.> 这样的提示．","3":"修改了 代码模板 提 示的 bug.\r\n用于 if<alt-.> 这样的提示．","package":"vjde.tgz","4":"vjde.tgz","src_id":"6084","5":"6084","creation_date":"1156117339","6":"1156117339"},{"0":"1213","vim_version":"7.0","1":"7.0","script_version":"2.12.3","2":"2.12.3","version_comment":"Bug fix for java package completion. Thanks for Attila Piros. ^_^","3":"Bug fix for java package completion. Thanks for Attila Piros. ^_^","package":"vjde.tgz","4":"vjde.tgz","src_id":"5960","5":"5960","creation_date":"1153094982","6":"1153094982"},{"0":"1213","vim_version":"7.0","1":"7.0","script_version":"2.12.2","2":"2.12.2","version_comment":"remove stl_fn.vim from autoload\/xml.\r\n\r\nyou can remove this file by yourself.","3":"remove stl_fn.vim from autoload\/xml.\r\n\r\nyou can remove this file by yourself.","package":"vjde.tgz","4":"vjde.tgz","src_id":"5890","5":"5890","creation_date":"1151517595","6":"1151517595"},{"0":"1213","vim_version":"7.0","1":"7.0","script_version":"2.12.1","2":"2.12.1","version_comment":"Use the xml completion for java taglib completion.\r\nSome Bug fix","3":"Use the xml completion for java taglib completion.\r\nSome Bug fix","package":"vjde.tgz","4":"vjde.tgz","src_id":"5875","5":"5875","creation_date":"1151350224","6":"1151350224"},{"0":"1213","vim_version":"7.0","1":"7.0","script_version":"2.12.0","2":"2.12.0","version_comment":"Bug fix for vim7.0 \r\nUse popup menu to select code template.\r\nIf your want to use the old version,\r\nadd following in your .vimrc\r\ng:vjde_iab_old=1","3":"Bug fix for vim7.0 \r\nUse popup menu to select code template.\r\nIf your want to use the old version,\r\nadd following in your .vimrc\r\ng:vjde_iab_old=1","package":"vjde.tgz","4":"vjde.tgz","src_id":"5706","5":"5706","creation_date":"1147734741","6":"1147734741"},{"0":"1213","vim_version":"7.0","1":"7.0","script_version":"2.11.4","2":"2.11.4","version_comment":"Fix a minor bug.\r\nAdd a simple auto completion for ruby.\r\n:h vjde-ruby\r\nfor detail.","3":"Fix a minor bug.\r\nAdd a simple auto completion for ruby.\r\n:h vjde-ruby\r\nfor detail.","package":"vjde.tgz","4":"vjde.tgz","src_id":"5536","5":"5536","creation_date":"1144628690","6":"1144628690"},{"0":"1213","vim_version":"7.0","1":"7.0","script_version":"2.11.3","2":"2.11.3","version_comment":"bug fix for Project menu.\r\nremove ruby require for taglib completion.","3":"bug fix for Project menu.\r\nremove ruby require for taglib completion.","package":"vjde.tgz","4":"vjde.tgz","src_id":"5520","5":"5520","creation_date":"1144176145","6":"1144176145"},{"0":"1213","vim_version":"7.0","1":"7.0","script_version":"2.11.2","2":"2.11.2","version_comment":"Add a dtd to xmldata ruby script.\r\nAdd a taglib define (TLD) to xmldata ruby script.\r\n:h vjde-xmldata\r\n\r\nMove html , taglib completion to htmlcomplete#CompleteTags\r\nxmlcomplete#CompleteTags\r\nAdd command \r\nVjdeTld2Data \r\nVjdeDtd2Data\r\n\r\nsee \r\n:h vjde-taglib\r\n:h vjde-xml","3":"Add a dtd to xmldata ruby script.\r\nAdd a taglib define (TLD) to xmldata ruby script.\r\n:h vjde-xmldata\r\n\r\nMove html , taglib completion to htmlcomplete#CompleteTags\r\nxmlcomplete#CompleteTags\r\nAdd command \r\nVjdeTld2Data \r\nVjdeDtd2Data\r\n\r\nsee \r\n:h vjde-taglib\r\n:h vjde-xml","package":"vjde.tgz","4":"vjde.tgz","src_id":"5514","5":"5514","creation_date":"1144103306","6":"1144103306"},{"0":"1213","vim_version":"7.0","1":"7.0","script_version":"2.11.1","2":"2.11.1","version_comment":"Java completion improved.\r\nUsing JDK 1.4 compiled.\r\nUse <c-x><c-u> to start completion in popupmenu.\r\nA simple c# support added.\r\n\r\nRemove My own Preview GUI support!!!","3":"Java completion improved.\r\nUsing JDK 1.4 compiled.\r\nUse <c-x><c-u> to start completion in popupmenu.\r\nA simple c# support added.\r\n\r\nRemove My own Preview GUI support!!!","package":"vjde.tgz","4":"vjde.tgz","src_id":"5495","5":"5495","creation_date":"1143652466","6":"1143652466"},{"0":"1213","vim_version":"6.0","1":"6.0","script_version":"2.11.0","2":"2.11.0","version_comment":"Support the latest Vim .\r\nRemove html suport , Should use omni xhtml to instead .","3":"Support the latest Vim .\r\nRemove html suport , Should use omni xhtml to instead .","package":"vjde.tgz","4":"vjde.tgz","src_id":"5470","5":"5470","creation_date":"1142893096","6":"1142893096"},{"0":"1213","vim_version":"6.0","1":"6.0","script_version":"2.10.01","2":"2.10.01","version_comment":"Add fix tools for other language.\r\nBug fix for c++ reference .","3":"Add fix tools for other language.\r\nBug fix for c++ reference .","package":"vjde.tgz","4":"vjde.tgz","src_id":"4983","5":"4983","creation_date":"1137445523","6":"1137445523"},{"0":"1213","vim_version":"6.0","1":"6.0","script_version":"2.10.00","2":"2.10.00","version_comment":"Add <c-l> for console completion key in insert mode.(c++\/c\/java users,)\r\nFix a minor bug for corperation of taglist plugin.\r\nAdd auto_ptr<T t> code completion support.\r\nWhile use following coding:\r\n \tauto_ptr<MyClass> MyClassPtr;\r\n        MyClassPtr ptr1 = new ...;\r\n        ptr1->\r\n           \r\nVJDE will completion for MyClass , not for auto_ptr.\r\nFor use this new function , your had to add a file:\r\n\t~\/.vim\/vjde\/ptr.lst\r\n\r\nThis file contains all of your used something like auto_ptr\r\nMy own file looks like:\r\n\tIceInternal::Handle\r\n\tIceInteranl::ProxyHandle\r\n\tstd::auto_ptr\r\n\tauto_ptr","3":"Add <c-l> for console completion key in insert mode.(c++\/c\/java users,)\r\nFix a minor bug for corperation of taglist plugin.\r\nAdd auto_ptr<T t> code completion support.\r\nWhile use following coding:\r\n \tauto_ptr<MyClass> MyClassPtr;\r\n        MyClassPtr ptr1 = new ...;\r\n        ptr1->\r\n           \r\nVJDE will completion for MyClass , not for auto_ptr.\r\nFor use this new function , your had to add a file:\r\n\t~\/.vim\/vjde\/ptr.lst\r\n\r\nThis file contains all of your used something like auto_ptr\r\nMy own file looks like:\r\n\tIceInternal::Handle\r\n\tIceInteranl::ProxyHandle\r\n\tstd::auto_ptr\r\n\tauto_ptr","package":"vjde.tgz","4":"vjde.tgz","src_id":"4949","5":"4949","creation_date":"1136503724","6":"1136503724"},{"0":"1213","vim_version":"6.0","1":"6.0","script_version":"2.02.09","2":"2.02.09","version_comment":"Since the VIM autoload the script from the sub-directory , So, the loading order\r\nmust be correctly. \r\nFix it for VIM70aa-154","3":"Since the VIM autoload the script from the sub-directory , So, the loading order\r\nmust be correctly. \r\nFix it for VIM70aa-154","package":"vjde.tgz","4":"vjde.tgz","src_id":"4656","5":"4656","creation_date":"1128717698","6":"1128717698"},{"0":"1213","vim_version":"6.0","1":"6.0","script_version":"2.02.08","2":"2.02.08","version_comment":"Change the API structure to fit the latest VIM.\r\nchange VjdeCompletionFun(line,base,col,findstart)\r\nto VjdeCompletionFun0(findstart,base)\r\n\r\n","3":"Change the API structure to fit the latest VIM.\r\nchange VjdeCompletionFun(line,base,col,findstart)\r\nto VjdeCompletionFun0(findstart,base)\r\n\r\n","package":"vjde.tgz","4":"vjde.tgz","src_id":"4595","5":"4595","creation_date":"1127083939","6":"1127083939"},{"0":"1213","vim_version":"6.0","1":"6.0","script_version":"2.02.07","2":"2.02.07","version_comment":"Add gtk tags for window version.\r\nAdd more power full struct support which ctags not supported!\r\nlike \r\n   typedef struct {\r\n        int a;\r\n        int b;\r\n   } SA;\r\n   SA sa;\r\n   sa.<c-space>\r\n","3":"Add gtk tags for window version.\r\nAdd more power full struct support which ctags not supported!\r\nlike \r\n   typedef struct {\r\n        int a;\r\n        int b;\r\n   } SA;\r\n   SA sa;\r\n   sa.<c-space>\r\n","package":"vjde.tgz","4":"vjde.tgz","src_id":"4564","5":"4564","creation_date":"1126462191","6":"1126462191"},{"0":"1213","vim_version":"6.0","1":"6.0","script_version":"2.02.07","2":"2.02.07","version_comment":"I forget to remove the ruby require for cpp completion.^_^\r\nYou can remove  it by your self . \r\nplugin\/vjde\/vjde_cpp_completion.vim  line 3 and line 4","3":"I forget to remove the ruby require for cpp completion.^_^\r\nYou can remove  it by your self . \r\nplugin\/vjde\/vjde_cpp_completion.vim  line 3 and line 4","package":"vjde.tgz","4":"vjde.tgz","src_id":"4561","5":"4561","creation_date":"1126220848","6":"1126220848"},{"0":"1213","vim_version":"6.0","1":"6.0","script_version":"2.02.06","2":"2.02.06","version_comment":"Add pure vim ctags support ( use vim +readtags) . \r\nIt's slowly than ruby+readtags\r\nTo  use this feature , for your vimrc , add this line\r\ng:vjde_ctags_ruby=0","3":"Add pure vim ctags support ( use vim +readtags) . \r\nIt's slowly than ruby+readtags\r\nTo  use this feature , for your vimrc , add this line\r\ng:vjde_ctags_ruby=0","package":"vjde.tgz","4":"vjde.tgz","src_id":"4560","5":"4560","creation_date":"1126214870","6":"1126214870"},{"0":"1213","vim_version":"6.0","1":"6.0","script_version":"2.02.05","2":"2.02.05","version_comment":"Use readtags instead of ruby parser for tags parsing.(more quickly)\r\nLinux GUI version bug fixed.\r\nsee vcde.txt for detail.\r\nuse : gcc -static -o plugin\/vjde\/readtags src\/readtags.c -DREADTAGS_MAIN\r\ncompile readtags on win32 and mandrake","3":"Use readtags instead of ruby parser for tags parsing.(more quickly)\r\nLinux GUI version bug fixed.\r\nsee vcde.txt for detail.\r\nuse : gcc -static -o plugin\/vjde\/readtags src\/readtags.c -DREADTAGS_MAIN\r\ncompile readtags on win32 and mandrake","package":"vjde.tgz","4":"vjde.tgz","src_id":"4559","5":"4559","creation_date":"1126138596","6":"1126138596"},{"0":"1213","vim_version":"6.0","1":"6.0","script_version":"2.02.04","2":"2.02.04","version_comment":"Improve the seach speed for a member of a function.\r\nImprove for the complex defination of c++ variable, like:\r\n   boost::multi_index<string,char>::index idx;\r\n   idx.<c-space>\r\n   boost::multi_index<string,char>::index::<c-space>\r\n\r\n","3":"Improve the seach speed for a member of a function.\r\nImprove for the complex defination of c++ variable, like:\r\n   boost::multi_index<string,char>::index idx;\r\n   idx.<c-space>\r\n   boost::multi_index<string,char>::index::<c-space>\r\n\r\n","package":"vjde.tgz","4":"vjde.tgz","src_id":"4555","5":"4555","creation_date":"1125976112","6":"1125976112"},{"0":"1213","vim_version":"6.0","1":"6.0","script_version":"2.02.03","2":"2.02.03","version_comment":"Bug fix . ^_^","3":"Bug fix . ^_^","package":"vjde.tgz","4":"vjde.tgz","src_id":"4551","5":"4551","creation_date":"1125890706","6":"1125890706"},{"0":"1213","vim_version":"6.0","1":"6.0","script_version":"2.02.02","2":"2.02.02","version_comment":"Some bugfix for linux user.\r\nI found that sometimes I will crash your GVIM under linux.\r\nSo, It's recommened use preview in console mode is usefull for LINUX user.","3":"Some bugfix for linux user.\r\nI found that sometimes I will crash your GVIM under linux.\r\nSo, It's recommened use preview in console mode is usefull for LINUX user.","package":"vjde.tgz","4":"vjde.tgz","src_id":"4549","5":"4549","creation_date":"1125777643","6":"1125777643"},{"0":"1213","vim_version":"6.0","1":"6.0","script_version":"2.02.01","2":"2.02.01","version_comment":"All of ctags supported language is supported for code completion .\r\nsetup variable:  \r\ng:vjde_ctags_exts='rb;vim' \r\ncan be used for VJDE self. Then , I can use <c-space> in vim and\r\nruby file to popup a completion preview window or in console.\r\n\r\nIabbr support Every language with filetype can be detected by VIM\r\nput something like ruby.iab and vim.iab to ~\/.vim\/vjde\/ , then , setup:\r\ng:vjde_iab_exts='rb;vim'\r\nThen, I can use <c-j> in ruby or vim file to select code template .\r\n\r\nAnd , add ruby.vjde to ~\/.vim\/vjde\/, the menu Vim JDE->Wizard->ruby\r\nWorld be append, and , in a ruby file, select a template ....","3":"All of ctags supported language is supported for code completion .\r\nsetup variable:  \r\ng:vjde_ctags_exts='rb;vim' \r\ncan be used for VJDE self. Then , I can use <c-space> in vim and\r\nruby file to popup a completion preview window or in console.\r\n\r\nIabbr support Every language with filetype can be detected by VIM\r\nput something like ruby.iab and vim.iab to ~\/.vim\/vjde\/ , then , setup:\r\ng:vjde_iab_exts='rb;vim'\r\nThen, I can use <c-j> in ruby or vim file to select code template .\r\n\r\nAnd , add ruby.vjde to ~\/.vim\/vjde\/, the menu Vim JDE->Wizard->ruby\r\nWorld be append, and , in a ruby file, select a template ....","package":"vjde.tgz","4":"vjde.tgz","src_id":"4546","5":"4546","creation_date":"1125618981","6":"1125618981"},{"0":"1213","vim_version":"6.0","1":"6.0","script_version":"2.02.00","2":"2.02.00","version_comment":"More beautifull docment window for Java . ^_^\r\nc++ preview supported ! \r\nc++ parameter info preview supported .\r\nsee http:\/\/www.publicinfo.com.cn\/wfc\/index.html for snapshot\r\n\r\n","3":"More beautifull docment window for Java . ^_^\r\nc++ preview supported ! \r\nc++ parameter info preview supported .\r\nsee http:\/\/www.publicinfo.com.cn\/wfc\/index.html for snapshot\r\n\r\n","package":"vjde.tgz","4":"vjde.tgz","src_id":"4543","5":"4543","creation_date":"1125540816","6":"1125540816"},{"0":"1213","vim_version":"6.0","1":"6.0","script_version":"2.01.00","2":"2.01.00","version_comment":"Add a document preview window for Java code .\r\nhttp:\/\/www.publicinfo.com.cn\/wfc\/index_g.html\r\nAdd code block template (iab) for console user.\r\nhttp:\/\/www.publicinfo.com.cn\/wfc\/index_c.html","3":"Add a document preview window for Java code .\r\nhttp:\/\/www.publicinfo.com.cn\/wfc\/index_g.html\r\nAdd code block template (iab) for console user.\r\nhttp:\/\/www.publicinfo.com.cn\/wfc\/index_c.html","package":"vjde.tgz","4":"vjde.tgz","src_id":"4531","5":"4531","creation_date":"1125112526","6":"1125112526"},{"0":"1213","vim_version":"6.0","1":"6.0","script_version":"2.00.13","2":"2.00.13","version_comment":"minor changed","3":"minor changed","package":"vjde.tgz","4":"vjde.tgz","src_id":"4508","5":"4508","creation_date":"1124676896","6":"1124676896"},{"0":"1213","vim_version":"6.0","1":"6.0","script_version":"2.00.12","2":"2.00.12","version_comment":"mirror bugfix for 2.00.12. ","3":"mirror bugfix for 2.00.12. ","package":"vjde.tgz","4":"vjde.tgz","src_id":"4500","5":"4500","creation_date":"1124391026","6":"1124391026"},{"0":"1213","vim_version":"6.0","1":"6.0","script_version":"2.00.11","2":"2.00.11","version_comment":"fix for bugs . when the vim home is contains a space , VJDE is not avaliable.\r\nAdd menu shortcut for menu.\r\n\r\nThanks for any advice.","3":"fix for bugs . when the vim home is contains a space , VJDE is not avaliable.\r\nAdd menu shortcut for menu.\r\n\r\nThanks for any advice.","package":"vjde.tgz","4":"vjde.tgz","src_id":"4498","5":"4498","creation_date":"1124314112","6":"1124314112"}]},"1212":{"script_id":"1212","0":"1212","script_name":"AddIfndefGuard","1":"AddIfndefGuard","script_type":"utility","2":"utility","summary":"Add the #ifndef\/#define\/#endif guard to a C\/C++ header file","3":"Add the #ifndef\/#define\/#endif guard to a C\/C++ header file","description":"When one writes a header file for C\/C++, compile errors will occur if the same header script is included more than once. A common solution is to add\r\n     #ifndef FILENAME_H\r\n     #define FILENAME_H\r\nto the start of a file, and\r\n     #endif\r\nto the end. This solves the problem.\r\n\r\nHowever this is mechanical and routine. So the computer should do it. So here's a script to do it.\r\n\r\nIt will add those lines to the top of the file you call it in. It will change FILENAME to be the uppercase name of that file, ommiting the file extension. It will not (yet) check to see if a #define\/#ifndef\/#endif black has already been added. It will not check the filename, so it can be called on anyfile.","4":"When one writes a header file for C\/C++, compile errors will occur if the same header script is included more than once. A common solution is to add\r\n     #ifndef FILENAME_H\r\n     #define FILENAME_H\r\nto the start of a file, and\r\n     #endif\r\nto the end. This solves the problem.\r\n\r\nHowever this is mechanical and routine. So the computer should do it. So here's a script to do it.\r\n\r\nIt will add those lines to the top of the file you call it in. It will change FILENAME to be the uppercase name of that file, ommiting the file extension. It will not (yet) check to see if a #define\/#ifndef\/#endif black has already been added. It will not check the filename, so it can be called on anyfile.","install_details":"Unzip the file. Read the README (if you want). Place AddIfndefGuard.vim to the plugins directory. (On UNIX it's ~\/.vim\/plugins\/)","5":"Unzip the file. Read the README (if you want). Place AddIfndefGuard.vim to the plugins directory. (On UNIX it's ~\/.vim\/plugins\/)","first_name":"Rory","6":"Rory","last_name":"McCann","7":"McCann","releases":[{"0":"1212","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"AddIfndefGuard.zip","4":"AddIfndefGuard.zip","src_id":"3895","5":"3895","creation_date":"1109082491","6":"1109082491"}]},"1211":{"script_id":"1211","0":"1211","script_name":"XML Indent","1":"XML Indent","script_type":"indent","2":"indent","summary":"My XML Indent (align attributes)","3":"My XML Indent (align attributes)","description":"It aligns all attributes of a tag to the same column\r\n\r\n<!-- there are 10 spaces before \"xmlns:c=...\" -->\r\n<jsp:root xmlns:jsp=\"http:\/\/java.sun.com\/JSP\/Page\"\r\n          xmlns:c=\"http:\/\/java.sun.com\/jstl\/core\"\r\n          xmlns:tf=\"urn:jsptagdir:\/WEB-INF\/tags\">\r\n\r\n<jsp:root\r\n  xmlns:jsp=\"http:\/\/java.sun.com\/JSP\/Page\"\r\n  xmlns:c=\"http:\/\/java.sun.com\/jstl\/core\"\r\n  xmlns:tf=\"urn:jsptagdir:\/WEB-INF\/tags\">\r\n\r\n\r\n(The original indent\/xml.vim does only the second type of indent)","4":"It aligns all attributes of a tag to the same column\r\n\r\n<!-- there are 10 spaces before \"xmlns:c=...\" -->\r\n<jsp:root xmlns:jsp=\"http:\/\/java.sun.com\/JSP\/Page\"\r\n          xmlns:c=\"http:\/\/java.sun.com\/jstl\/core\"\r\n          xmlns:tf=\"urn:jsptagdir:\/WEB-INF\/tags\">\r\n\r\n<jsp:root\r\n  xmlns:jsp=\"http:\/\/java.sun.com\/JSP\/Page\"\r\n  xmlns:c=\"http:\/\/java.sun.com\/jstl\/core\"\r\n  xmlns:tf=\"urn:jsptagdir:\/WEB-INF\/tags\">\r\n\r\n\r\n(The original indent\/xml.vim does only the second type of indent)","install_details":"Overide the original indent\/xml.vim with this file","5":"Overide the original indent\/xml.vim with this file","first_name":"Aquila","6":"Aquila","last_name":"Deus","7":"Deus","releases":[{"0":"1211","vim_version":"6.0","1":"6.0","script_version":"0.993","2":"0.993","version_comment":"Indent multi-line <!-- --> and <%-- --%>","3":"Indent multi-line <!-- --> and <%-- --%>","package":"xml.vim","4":"xml.vim","src_id":"4174","5":"4174","creation_date":"1113692389","6":"1113692389"},{"0":"1211","vim_version":"6.0","1":"6.0","script_version":"0.992","2":"0.992","version_comment":"Fix bug with <!DOCTYPE","3":"Fix bug with <!DOCTYPE","package":"xml.vim","4":"xml.vim","src_id":"3912","5":"3912","creation_date":"1109362871","6":"1109362871"},{"0":"1211","vim_version":"6.0","1":"6.0","script_version":"0.991","2":"0.991","version_comment":"fix <!-- --> problem. Now the line after comment tag is always aligned to the open tag of comment (regardless of the contents inside comment)","3":"fix <!-- --> problem. Now the line after comment tag is always aligned to the open tag of comment (regardless of the contents inside comment)","package":"xml.vim","4":"xml.vim","src_id":"3903","5":"3903","creation_date":"1109204223","6":"1109204223"},{"0":"1211","vim_version":"6.0","1":"6.0","script_version":"0.99","2":"0.99","version_comment":"Initial upload","3":"Initial upload","package":"xml.vim","4":"xml.vim","src_id":"3891","5":"3891","creation_date":"1109041833","6":"1109041833"}]},"1210":{"script_id":"1210","0":"1210","script_name":"latexmenu","1":"latexmenu","script_type":"utility","2":"utility","summary":"Generates a \"tableofcontents\"-navigation-menu for the gui menubar.","3":"Generates a \"tableofcontents\"-navigation-menu for the gui menubar.","description":"This plugin adds a function GenerateLatexMenu() which parses a latexfile\r\nfor \\chapter's, \\section's, etc. and generates a \"Navigation\"-menu in the gui-menubar\r\nwhere you can jump quickly into the different sections.\r\n","4":"This plugin adds a function GenerateLatexMenu() which parses a latexfile\r\nfor \\chapter's, \\section's, etc. and generates a \"Navigation\"-menu in the gui-menubar\r\nwhere you can jump quickly into the different sections.\r\n","install_details":"- copy latexmenu.vim into your .vim\/plugin directory\r\n- open a .tex-File\r\n- :call GenerateLatexMenu()","5":"- copy latexmenu.vim into your .vim\/plugin directory\r\n- open a .tex-File\r\n- :call GenerateLatexMenu()","first_name":"Philipp","6":"Philipp","last_name":"Braunbarth","7":"Braunbarth","releases":[{"0":"1210","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"latexmenu.vim","4":"latexmenu.vim","src_id":"3889","5":"3889","creation_date":"1108972423","6":"1108972423"}]},"1209":{"script_id":"1209","0":"1209","script_name":"cvsvimdiff","1":"cvsvimdiff","script_type":"utility","2":"utility","summary":"cvs diff + vimdiff","3":"cvs diff + vimdiff","description":"Perform cvs diff invoking vimdiff.\r\n\r\nThis script does not aim at supporting cvs as vimscript #90, it simply enables people acquainted with \"cvs diff\" to see its output in a handier way.","4":"Perform cvs diff invoking vimdiff.\r\n\r\nThis script does not aim at supporting cvs as vimscript #90, it simply enables people acquainted with \"cvs diff\" to see its output in a handier way.","install_details":"just download the script and use it as you would have used \"cvs diff\"","5":"just download the script and use it as you would have used \"cvs diff\"","first_name":"Stefano","6":"Stefano","last_name":"Zacchiroli","7":"Zacchiroli","releases":[{"0":"1209","vim_version":"7.0","1":"7.0","script_version":"1.3","2":"1.3","version_comment":"- use mktemp instead of tempfile since the former is more portable (thanks to Dale Kiefling for the patch)\r\n- add a -r option to diff against a specific version (thanks to Prasun Ratn for the patch)","3":"- use mktemp instead of tempfile since the former is more portable (thanks to Dale Kiefling for the patch)\r\n- add a -r option to diff against a specific version (thanks to Prasun Ratn for the patch)","package":"cvsvimdiff","4":"cvsvimdiff","src_id":"7515","5":"7515","creation_date":"1187321276","6":"1187321276"},{"0":"1209","vim_version":"6.0","1":"6.0","script_version":"1.2","2":"1.2","version_comment":"integrated a patch from Geoff Buchan which adds the \"-g\" flag for firing gvimdiff instead of vimdiff","3":"integrated a patch from Geoff Buchan which adds the \"-g\" flag for firing gvimdiff instead of vimdiff","package":"cvsvimdiff","4":"cvsvimdiff","src_id":"6474","5":"6474","creation_date":"1164619564","6":"1164619564"},{"0":"1209","vim_version":"6.0","1":"6.0","script_version":"1.1","2":"1.1","version_comment":"Integrated a patch from Ami Chayun for diffing against file changed in the repository and avoiding side-effect changes of local files.","3":"Integrated a patch from Ami Chayun for diffing against file changed in the repository and avoiding side-effect changes of local files.","package":"cvsvimdiff","4":"cvsvimdiff","src_id":"4953","5":"4953","creation_date":"1136728807","6":"1136728807"},{"0":"1209","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"cvsvimdiff","4":"cvsvimdiff","src_id":"3882","5":"3882","creation_date":"1108798386","6":"1108798386"}]},"1208":{"script_id":"1208","0":"1208","script_name":"vimCU","1":"vimCU","script_type":"utility","2":"utility","summary":"comment\/uncomment functionalities for every language","3":"comment\/uncomment functionalities for every language","description":"vimCU is a set of ViM functions that you can use to customize your ViM editor to comment\/uncomment source code of every language you like.\r\n\r\nComment key binding defaults to \",#\" while uncomment key binding to \",3\" (mnemonic: same key as comment, but without shift). In command mode the current line will be commented\/uncommented, in visual mode all selected lines will.\r\n\r\nIn order to support commenting in the language of your choice you've to define how comments are handled in that language defining the following local variables:\r\n\r\n- variable \"b:CommentType\". A string formed using \"s\" and\/or \"m\" chars; \"s\" means that your language supports single line comment like, e.g., bash script, perl or similar, that are comments formed adding something at the beginning and at the end of a line; \"m\" means that your language supports multi line comment like, e.g. ANSI C, OCaml, or similar, that are comments that extends from a character set to another character set; \"ms\" or \"sm\" mean that your language supports both kinds of comments like, e.g., C++.\r\n\r\n- variables: \"b:beginOfCommentSingle\", \"b:endOfCommentSingle\". Strings that are used to begin and end a single line comment. These strings are added at the begin and at the end of the line you want to commend.\r\n\r\n- variables: \"b:beginOfCommentMulti\", \"b:endOfCommentMulti\". Strings that are used to begin and end a multi line comment. These strings are added before and after the line(s) you are commenting on a line by themeselves.\r\n\r\nFor example, in order to support C++, just add to your ~\/.vim\/ftplugin\/cpp.vim the following lines:\r\n      let b:CommentType = \"ms\"\r\n      let b:beginOfCommentSingle = \"\/\/ \"\r\n      let b:endOfCommentSingle = \"\"\r\n      let b:beginOfCommentMulti = \"\/*\"\r\n      let b:endOfCommentMulti = \"*\/\"\r\n","4":"vimCU is a set of ViM functions that you can use to customize your ViM editor to comment\/uncomment source code of every language you like.\r\n\r\nComment key binding defaults to \",#\" while uncomment key binding to \",3\" (mnemonic: same key as comment, but without shift). In command mode the current line will be commented\/uncommented, in visual mode all selected lines will.\r\n\r\nIn order to support commenting in the language of your choice you've to define how comments are handled in that language defining the following local variables:\r\n\r\n- variable \"b:CommentType\". A string formed using \"s\" and\/or \"m\" chars; \"s\" means that your language supports single line comment like, e.g., bash script, perl or similar, that are comments formed adding something at the beginning and at the end of a line; \"m\" means that your language supports multi line comment like, e.g. ANSI C, OCaml, or similar, that are comments that extends from a character set to another character set; \"ms\" or \"sm\" mean that your language supports both kinds of comments like, e.g., C++.\r\n\r\n- variables: \"b:beginOfCommentSingle\", \"b:endOfCommentSingle\". Strings that are used to begin and end a single line comment. These strings are added at the begin and at the end of the line you want to commend.\r\n\r\n- variables: \"b:beginOfCommentMulti\", \"b:endOfCommentMulti\". Strings that are used to begin and end a multi line comment. These strings are added before and after the line(s) you are commenting on a line by themeselves.\r\n\r\nFor example, in order to support C++, just add to your ~\/.vim\/ftplugin\/cpp.vim the following lines:\r\n      let b:CommentType = \"ms\"\r\n      let b:beginOfCommentSingle = \"\/\/ \"\r\n      let b:endOfCommentSingle = \"\"\r\n      let b:beginOfCommentMulti = \"\/*\"\r\n      let b:endOfCommentMulti = \"*\/\"\r\n","install_details":"Just copy vimCU.vim somewhere (e.g. ~\/.vim\/vimCU.vim) and source it from your ~\/.vimrc, e.g.:\r\n      source ~\/.vim\/vimCU.vim\r\n... and of course define the above variables for your favorite language! :-)","5":"Just copy vimCU.vim somewhere (e.g. ~\/.vim\/vimCU.vim) and source it from your ~\/.vimrc, e.g.:\r\n      source ~\/.vim\/vimCU.vim\r\n... and of course define the above variables for your favorite language! :-)","first_name":"Stefano","6":"Stefano","last_name":"Zacchiroli","7":"Zacchiroli","releases":[{"0":"1208","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"vimCU.vim","4":"vimCU.vim","src_id":"3881","5":"3881","creation_date":"1108796686","6":"1108796686"}]},"1207":{"script_id":"1207","0":"1207","script_name":"DNA Tools","1":"DNA Tools","script_type":"utility","2":"utility","summary":"few utils for people working with DNA sequences","3":"few utils for people working with DNA sequences","description":"My $0.02 worth of...\r\nWorking with DNA sequences, especially if you don't have a Unix machine handy might need a few tools. Some of the modifications are simple enough that even a trivial Vim script would deal with.\r\nWhat you can do:\r\n- get the reverse-complement of a sequence\r\n- count A\/T\/C\/Gs in a sequence and get a very crude Tm for a primer\r\n- brush-up a few file formats (PS from ClustalX, FASTA etc).\r\n\r\nMany thanks to Will Nater and Tim Chase for helping!\r\n\r\nVersion \"1.0\" means that, up to now, I did not have any screwed-up sequence, but this is far from saying that it's definitely foolproof.","4":"My $0.02 worth of...\r\nWorking with DNA sequences, especially if you don't have a Unix machine handy might need a few tools. Some of the modifications are simple enough that even a trivial Vim script would deal with.\r\nWhat you can do:\r\n- get the reverse-complement of a sequence\r\n- count A\/T\/C\/Gs in a sequence and get a very crude Tm for a primer\r\n- brush-up a few file formats (PS from ClustalX, FASTA etc).\r\n\r\nMany thanks to Will Nater and Tim Chase for helping!\r\n\r\nVersion \"1.0\" means that, up to now, I did not have any screwed-up sequence, but this is far from saying that it's definitely foolproof.","install_details":"Just drop it in your plugins directory. It will also install a menu entry for each function (Tools\/Cleanup and Tools\/DNA)","5":"Just drop it in your plugins directory. It will also install a menu entry for each function (Tools\/Cleanup and Tools\/DNA)","first_name":"Alexandru","6":"Alexandru","last_name":"Constantinescu","7":"Constantinescu","releases":[{"0":"1207","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"DNA_Tools.vim","4":"DNA_Tools.vim","src_id":"3868","5":"3868","creation_date":"1108457121","6":"1108457121"}]},"1206":{"script_id":"1206","0":"1206","script_name":"ProvideX Syntax","1":"ProvideX Syntax","script_type":"syntax","2":"syntax","summary":"The language blows.  But working with it doesn\\'t have to.","3":"The language blows.  But working with it doesn\\'t have to.","description":"ProvideX is a Business Basic dialect used within the popular Mas90\/200 accounting product lines, as well as many other business software products.\r\n\r\nI do not advocate the use of providex.  I only hope to aide those who have found themselves in the position of working with it as I have :-)\r\n\r\nPointers were taken from many syntax files, mainly the basic.vim syntax file from Allan Kelly. <allan@fruitloaf.co.uk>\r\n\r\nUpdate: I no longer work with ProvideX!  Congratulations are welcome :-)","4":"ProvideX is a Business Basic dialect used within the popular Mas90\/200 accounting product lines, as well as many other business software products.\r\n\r\nI do not advocate the use of providex.  I only hope to aide those who have found themselves in the position of working with it as I have :-)\r\n\r\nPointers were taken from many syntax files, mainly the basic.vim syntax file from Allan Kelly. <allan@fruitloaf.co.uk>\r\n\r\nUpdate: I no longer work with ProvideX!  Congratulations are welcome :-)","install_details":"Install the file to $VIMRUNTIME\/syntax\/  and add the lines\r\n\r\n\" ProvideX\r\nau BufNewFile,BufRead *.pvs           call <SID>FTVB(\"providex\")\r\n\r\nto your $VIMRUNTIME\/filetype.vim file.","5":"Install the file to $VIMRUNTIME\/syntax\/  and add the lines\r\n\r\n\" ProvideX\r\nau BufNewFile,BufRead *.pvs           call <SID>FTVB(\"providex\")\r\n\r\nto your $VIMRUNTIME\/filetype.vim file.","first_name":"Leonard","6":"Leonard","last_name":"Clark","7":"Clark","releases":[{"0":"1206","vim_version":"6.0","1":"6.0","script_version":"1.1","2":"1.1","version_comment":"A little cleanup.\r\nRemoved annoying parens brain-child I thought was cool at first.\r\n","3":"A little cleanup.\r\nRemoved annoying parens brain-child I thought was cool at first.\r\n","package":"providex.vim","4":"providex.vim","src_id":"4204","5":"4204","creation_date":"1114513450","6":"1114513450"},{"0":"1206","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"providex.vim","4":"providex.vim","src_id":"3866","5":"3866","creation_date":"1108380851","6":"1108380851"}]},"1205":{"script_id":"1205","0":"1205","script_name":"Java Syntax & Folding","1":"Java Syntax & Folding","script_type":"syntax","2":"syntax","summary":"Java Syntax & Folding","3":"Java Syntax & Folding","description":"Modified from the original syntax\/java.vim to support syntax folding. I also removed a lot of unncessary syntax defs including error detection, standard classes, etc.\r\n\r\n\r\nKnown issues:\r\n\r\n- Method declaration is also folded currently, this is very ugly...","4":"Modified from the original syntax\/java.vim to support syntax folding. I also removed a lot of unncessary syntax defs including error detection, standard classes, etc.\r\n\r\n\r\nKnown issues:\r\n\r\n- Method declaration is also folded currently, this is very ugly...","install_details":"Replace the original syntax\/java.vim with this file. Following is my folding setting in vimrc:\r\n\r\nset foldclose=all\r\nset foldcolumn=1\r\nset foldenable\r\nset foldmethod=syntax\r\nset foldopen=all\r\n","5":"Replace the original syntax\/java.vim with this file. Following is my folding setting in vimrc:\r\n\r\nset foldclose=all\r\nset foldcolumn=1\r\nset foldenable\r\nset foldmethod=syntax\r\nset foldopen=all\r\n","first_name":"Aquila","6":"Aquila","last_name":"Deus","7":"Deus","releases":[{"0":"1205","vim_version":"6.0","1":"6.0","script_version":"0.9","2":"0.9","version_comment":"Initial upload","3":"Initial upload","package":"java.vim","4":"java.vim","src_id":"3864","5":"3864","creation_date":"1108340298","6":"1108340298"}]},"1204":{"script_id":"1204","0":"1204","script_name":"oo","1":"oo","script_type":"utility","2":"utility","summary":"Java code commpletion","3":"Java code commpletion","description":"This plugin is used for Java code completion. It's depends on ctags , \r\nvim which +ruby future is enabled.\r\nFor generate tags :\r\n         ctags --fileds=+ai   .....\r\nFor  generate tags Index file:\r\n         :ruby generateIndex(\"\/usr\/java\/jdk\/src\/tags\",2)\r\nThe second parameter which value is 2  is recommand.\r\n\r\nOnce you vim version is 7.00aa \r\n         :set cfu=OocompleteFun\r\nYou can use <CTRL>-x<CTRL>-u for this samle:\r\n        String str=\"\";\r\n        str.to\r\n                ^<CTRL>-X<CTRL>-U\r\nFor c++ user:\r\n         SomeClass * abc;\r\n         abc->So\r\n                        ^<CTRL>-X<CTRL>-U\r\nBoth java and c++\r\n         Abc::So\r\n                        ^<CTRL>-X<CTRL>-U\r\nThen toByteArray, toUpperCase...  would be selectable.\r\n\r\nvim version is 6.xx\r\n         :Oofun String to\r\nFirst parameter is name of the class , the second is the function name ( partly)\r\nThen toByteArray, toUpperCase...  would be show in command window.\r\n\r\nOne command is added, It's used to check variable type\r\n         :Ootype varname\r\n\r\nTODO list :\r\n         ctags's support for jdk1.5 , something incorrectly. like ,java.util.Vector\r\n         Advanced varible define selector. Something lik normal command gd\r\n\r\n         The last, my poor document  and my poor English, \r\n\r\n","4":"This plugin is used for Java code completion. It's depends on ctags , \r\nvim which +ruby future is enabled.\r\nFor generate tags :\r\n         ctags --fileds=+ai   .....\r\nFor  generate tags Index file:\r\n         :ruby generateIndex(\"\/usr\/java\/jdk\/src\/tags\",2)\r\nThe second parameter which value is 2  is recommand.\r\n\r\nOnce you vim version is 7.00aa \r\n         :set cfu=OocompleteFun\r\nYou can use <CTRL>-x<CTRL>-u for this samle:\r\n        String str=\"\";\r\n        str.to\r\n                ^<CTRL>-X<CTRL>-U\r\nFor c++ user:\r\n         SomeClass * abc;\r\n         abc->So\r\n                        ^<CTRL>-X<CTRL>-U\r\nBoth java and c++\r\n         Abc::So\r\n                        ^<CTRL>-X<CTRL>-U\r\nThen toByteArray, toUpperCase...  would be selectable.\r\n\r\nvim version is 6.xx\r\n         :Oofun String to\r\nFirst parameter is name of the class , the second is the function name ( partly)\r\nThen toByteArray, toUpperCase...  would be show in command window.\r\n\r\nOne command is added, It's used to check variable type\r\n         :Ootype varname\r\n\r\nTODO list :\r\n         ctags's support for jdk1.5 , something incorrectly. like ,java.util.Vector\r\n         Advanced varible define selector. Something lik normal command gd\r\n\r\n         The last, my poor document  and my poor English, \r\n\r\n","install_details":"tar -xzf oocomplete.tgz -C$VIMFILES\r\n\r\nVIMFILES is your vim script dir , for Mandrake10.1  is\r\n        \/usr\/share\/vim\/vimfiles\r\n\r\nFor windows: may be\r\n        d:\\vim\\vimfiles","5":"tar -xzf oocomplete.tgz -C$VIMFILES\r\n\r\nVIMFILES is your vim script dir , for Mandrake10.1  is\r\n        \/usr\/share\/vim\/vimfiles\r\n\r\nFor windows: may be\r\n        d:\\vim\\vimfiles","first_name":"JiuTian","6":"JiuTian","last_name":"Zhang","7":"Zhang","releases":[{"0":"1204","vim_version":"6.0","1":"6.0","script_version":"1.00.2","2":"1.00.2","version_comment":"More effective for Java and c++ .\r\nVariable type search is improved.","3":"More effective for Java and c++ .\r\nVariable type search is improved.","package":"oocomplete.tgz","4":"oocomplete.tgz","src_id":"3863","5":"3863","creation_date":"1108340286","6":"1108340286"},{"0":"1204","vim_version":"6.0","1":"6.0","script_version":"1.00.1","2":"1.00.1","version_comment":"Simply support for c++","3":"Simply support for c++","package":"oocomplete.tgz","4":"oocomplete.tgz","src_id":"3862","5":"3862","creation_date":"1108318010","6":"1108318010"},{"0":"1204","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"oocomplete.tgz","4":"oocomplete.tgz","src_id":"3859","5":"3859","creation_date":"1108249494","6":"1108249494"}]},"1203":{"script_id":"1203","0":"1203","script_name":"WhereFrom","1":"WhereFrom","script_type":"utility","2":"utility","summary":"WhereFrom helps one locate where maps, functions, or commands are defined","3":"WhereFrom helps one locate where maps, functions, or commands are defined","description":"The WhereFrom and WF commands search the runtimepath (see |'runtimepath'|) to determine where the setting, function, map, or command was defined.  With the \"!\", WhereFrom will continue looking for more than one instance.\r\n\r\n    WhereFrom[!] functionname(s)      WF[!] functionname(s)\r\n    WhereFrom[!] map(s)               WF[!] map(s)\r\n    WhereFrom[!] setting(s)           WF[!] setting(s)\r\n    WhereFrom[!] command(s)           WF[!] command(s)\r\n\r\n\r\nWF-style commands are available only if the command has not been previously defined, and are provided as a shorthand.\r\n\r\nA search is undertaken only for functions, commands, and maps, and then only if the function, command, or map is known to the currently running vim.  Determining where settings are set is done using vim's built-in method.\r\n\r\nThese commands don't search all *.vim files that you may have; it only examines those that lie on your runtimepath in the common directories plugin, ftplugin, colors, compilier, indent, syntax, and the after\/ variants.  In addition, it also searches the AsNeeded directory (see vimscript#915)\r\n\r\n(alpha\/beta version available at http:\/\/www.drchip.org\/astronaut\/vim\/index.html#WHEREFROM)\r\n","4":"The WhereFrom and WF commands search the runtimepath (see |'runtimepath'|) to determine where the setting, function, map, or command was defined.  With the \"!\", WhereFrom will continue looking for more than one instance.\r\n\r\n    WhereFrom[!] functionname(s)      WF[!] functionname(s)\r\n    WhereFrom[!] map(s)               WF[!] map(s)\r\n    WhereFrom[!] setting(s)           WF[!] setting(s)\r\n    WhereFrom[!] command(s)           WF[!] command(s)\r\n\r\n\r\nWF-style commands are available only if the command has not been previously defined, and are provided as a shorthand.\r\n\r\nA search is undertaken only for functions, commands, and maps, and then only if the function, command, or map is known to the currently running vim.  Determining where settings are set is done using vim's built-in method.\r\n\r\nThese commands don't search all *.vim files that you may have; it only examines those that lie on your runtimepath in the common directories plugin, ftplugin, colors, compilier, indent, syntax, and the after\/ variants.  In addition, it also searches the AsNeeded directory (see vimscript#915)\r\n\r\n(alpha\/beta version available at http:\/\/www.drchip.org\/astronaut\/vim\/index.html#WHEREFROM)\r\n","install_details":"* As usual with plugins: install it into your .vim\/plugin (Windows: vimfiles\\plugin) directory.\r\n\r\n* gunzip WhereFrom.vim.gz\r\n\r\nThe next time you run vim, the embedded HelpExtractor (vimscript#748) will make the help for WhereFrom available (and remove itself from the WhereFrom script).","5":"* As usual with plugins: install it into your .vim\/plugin (Windows: vimfiles\\plugin) directory.\r\n\r\n* gunzip WhereFrom.vim.gz\r\n\r\nThe next time you run vim, the embedded HelpExtractor (vimscript#748) will make the help for WhereFrom available (and remove itself from the WhereFrom script).","first_name":"Charles","6":"Charles","last_name":"Campbell","7":"Campbell","releases":[{"0":"1203","vim_version":"6.0","1":"6.0","script_version":"2","2":"2","version_comment":"* Now includes $HOME\/.vimrc on the list of files to be searched\r\n* GetLatestVimScripts auto-update enabled\r\n* Gives a message if unable to find a command\/map\/option\r\n","3":"* Now includes $HOME\/.vimrc on the list of files to be searched\r\n* GetLatestVimScripts auto-update enabled\r\n* Gives a message if unable to find a command\/map\/option\r\n","package":"WhereFrom.vim.gz","4":"WhereFrom.vim.gz","src_id":"4188","5":"4188","creation_date":"1114001839","6":"1114001839"}]},"1202":{"script_id":"1202","0":"1202","script_name":"bsh.vim","1":"bsh.vim","script_type":"syntax","2":"syntax","summary":"Syntax Highlighting for Shell \u00c2\u00bbbsh\u00c2\u00ab","3":"Syntax Highlighting for Shell \u00c2\u00bbbsh\u00c2\u00ab","description":"Syntax Highlighting for Shell \u00c2\u00bbbsh\u00c2\u00ab\r\n(DOS, Windows, Linux, FreeBSD, SCO...; 32+64Bit Arithm.)\r\nDownload of the Shell (Freeware):  http:\/\/www.schellong.de\r\n(Base: sh.vim)","4":"Syntax Highlighting for Shell \u00c2\u00bbbsh\u00c2\u00ab\r\n(DOS, Windows, Linux, FreeBSD, SCO...; 32+64Bit Arithm.)\r\nDownload of the Shell (Freeware):  http:\/\/www.schellong.de\r\n(Base: sh.vim)","install_details":"Copy bsh.vim -> ...\/syntax\/\r\n(Extension of filetype.vim, synmenu.vim)","5":"Copy bsh.vim -> ...\/syntax\/\r\n(Extension of filetype.vim, synmenu.vim)","first_name":"Helmut","6":"Helmut","last_name":"Schellong","7":"Schellong","releases":[{"0":"1202","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"bsh.vim","4":"bsh.vim","src_id":"3850","5":"3850","creation_date":"1108070393","6":"1108070393"}]},"1201":{"script_id":"1201","0":"1201","script_name":"c.vim","1":"c.vim","script_type":"syntax","2":"syntax","summary":"Extended original c.vim","3":"Extended original c.vim","description":"An extended and modified version of the original c.vim","4":"An extended and modified version of the original c.vim","install_details":"Save or rename ...\/syntax\/c.vim\r\nCopy new c.vim  ->  ...\/syntax","5":"Save or rename ...\/syntax\/c.vim\r\nCopy new c.vim  ->  ...\/syntax","first_name":"Helmut","6":"Helmut","last_name":"Schellong","7":"Schellong","releases":[{"0":"1201","vim_version":"6.0","1":"6.0","script_version":"1.1","2":"1.1","version_comment":"Improved goto LABEL; - LABEL: - LABEL:;","3":"Improved goto LABEL; - LABEL: - LABEL:;","package":"c.vim","4":"c.vim","src_id":"4083","5":"4083","creation_date":"1111876360","6":"1111876360"},{"0":"1201","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"c.vim","4":"c.vim","src_id":"3849","5":"3849","creation_date":"1108069546","6":"1108069546"}]},"1200":{"script_id":"1200","0":"1200","script_name":"namazu.vim","1":"namazu.vim","script_type":"utility","2":"utility","summary":"A frontend to the namazu command-line client.(not mknmz)","3":"A frontend to the namazu command-line client.(not mknmz)","description":"Namazu is a full text search engine.\r\nSee http:\/\/www.namazu.org\/.\r\n\r\nnamazu.vim has the following features.\r\n   - searching from the namazu index.\r\n   - open a file from search result. (now, only a plain text file)\r\n\r\n\" Options:\r\n\"\r\n\"   let g:namazu_cmd   = '\/path\/to\/namazu'\r\n\"                        (default: namazu)\r\n\"\r\n\"   let g:namazu_index = '\/path\/to\/indexdirectory'\r\n\"                        (Can be a space-separated list)\r\n\"\r\n\"   let g:namazu_range = NUMBER\r\n\"                        Set the number of documents shown to NUMBER.\r\n\"                        (default: 30)\r\n\"\r\n\"   let g:namazu_color = NUMBER\r\n\"                        Set this to zero to disable syntax\r\n\"                        highlighting.  (default: 1)\r\n\"\r\n\" Usage:\r\n\"\r\n\"   Type :Namazu<CR> to start searching.\r\n\"\r\n\"   <enter> : Open a selected file.\r\n\"   r       : Research.\r\n\"   s       : Set a sort METHOD (score, date)\r\n\"   k       : Move to a previous result.\r\n\"   j       : Move to a next result.\r\n\"   h       : Move to a previous page.\r\n\"   l       : Move to a next page.\r\n\"   q       : Close the namazu window.\r\n\"","4":"Namazu is a full text search engine.\r\nSee http:\/\/www.namazu.org\/.\r\n\r\nnamazu.vim has the following features.\r\n   - searching from the namazu index.\r\n   - open a file from search result. (now, only a plain text file)\r\n\r\n\" Options:\r\n\"\r\n\"   let g:namazu_cmd   = '\/path\/to\/namazu'\r\n\"                        (default: namazu)\r\n\"\r\n\"   let g:namazu_index = '\/path\/to\/indexdirectory'\r\n\"                        (Can be a space-separated list)\r\n\"\r\n\"   let g:namazu_range = NUMBER\r\n\"                        Set the number of documents shown to NUMBER.\r\n\"                        (default: 30)\r\n\"\r\n\"   let g:namazu_color = NUMBER\r\n\"                        Set this to zero to disable syntax\r\n\"                        highlighting.  (default: 1)\r\n\"\r\n\" Usage:\r\n\"\r\n\"   Type :Namazu<CR> to start searching.\r\n\"\r\n\"   <enter> : Open a selected file.\r\n\"   r       : Research.\r\n\"   s       : Set a sort METHOD (score, date)\r\n\"   k       : Move to a previous result.\r\n\"   j       : Move to a next result.\r\n\"   h       : Move to a previous page.\r\n\"   l       : Move to a next page.\r\n\"   q       : Close the namazu window.\r\n\"","install_details":"Put namazu.vim into your vim plugin directory.\r\nAnd then, you need namazu command-line client, of course.\r\n","5":"Put namazu.vim into your vim plugin directory.\r\nAnd then, you need namazu command-line client, of course.\r\n","first_name":"Kyosuke","6":"Kyosuke","last_name":"Takayama","7":"Takayama","releases":[{"0":"1200","vim_version":"6.0","1":"6.0","script_version":"0.01","2":"0.01","version_comment":"Initial upload","3":"Initial upload","package":"namazu.vim","4":"namazu.vim","src_id":"3846","5":"3846","creation_date":"1108016595","6":"1108016595"}]},"1199":{"script_id":"1199","0":"1199","script_name":"increment_new.vim","1":"increment_new.vim","script_type":"utility","2":"utility","summary":"Subsitute a pattern with incremented values ENHANCED","3":"Subsitute a pattern with incremented values ENHANCED","description":"This is a great (I think) improvement of the plugin increment.vim made by William Natter (natter at magma.ca) (vimscript #842). \r\n\r\nI tried to contact William, but his mailbox does not exist... So here it goes.\r\n\r\nAs William wrote:\r\n\"This is a handy plugin that makes easy replacing your favorite pattern (\"@\" by default) with a sequence of incremented values using the \"Inc\" command.  \"\r\n\r\nBesides what the original script can do, it has two new features:\r\n    a) Now you are able to search for a pattern and replace the Nth word from the beginning of the line with the incremental number. \r\n    b) And also you can get a confirmation message before change.\r\n\r\nThe help file is also greatly improved.\r\n\r\nHere is an example:\r\n\r\n       You have: (beginning with spaces only)\r\n           ----- cut -----\r\n                   LMsgInstall6 = 7; \/\/ @\r\n                 LMsgInstall7 = 8;   \/\/ @\r\n               LMsgInstall8 = 9;     \/\/ @\r\n\r\n               {STANDALONE}\r\n               LErrConnectionStandAlone1 = 10; \/\/THIS\r\n               LErrConnectionStandAlone3 = 7; \/\/THIS\r\n               LErrConnectionStandAlone5 = 12; \/\/THIS\r\n           {some text}\r\n               LMsgExitConfirm = 30;\r\n           ...\r\n           ----- cut -----\r\n\r\n       You do: (with confirmation) \r\n           :'<,'>Inc p^\\ *\\\\\\<\\[A-Za-z0-9_]*\\\\\\>\\ =\\ [0-9]* w3 i25 s100 c\r\n                                   (Note that I had to use tree \"\\\" before the \"<\" sign. Since Vim 7 the \"<\" and \">\" have to be skiped by a \"\\\")\r\n\r\n       You get:\r\n           ----- cut -----\r\n                   LMsgInstall6 = 100; \/\/ @\r\n                 LMsgInstall7 = 125;   \/\/ @\r\n               LMsgInstall8 = 150;     \/\/ @\r\n\r\n               {STANDALONE}\r\n               LErrConnectionStandAlone1 = 175; \/\/THIS\r\n               LErrConnectionStandAlone3 = 200; \/\/THIS\r\n               LErrConnectionStandAlone5 = 225; \/\/THIS\r\n           {some text}\r\n               LMsgExitConfirm = 250;\r\n           ...\r\n           ----- cut -----\r\n\r\n       Then you do: (without confirmation)\r\n           :'<,'>Inc pTHIS w3 i3 s5\r\n\r\n       You get:\r\n           ----- cut -----\r\n                   LMsgInstall6 = 100; \/\/ @\r\n                 LMsgInstall7 = 125;   \/\/ @\r\n               LMsgInstall8 = 150;     \/\/ @\r\n\r\n               {STANDALONE}\r\n               LErrConnectionStandAlone1 = 5; \/\/THIS\r\n               LErrConnectionStandAlone3 = 8; \/\/THIS\r\n               LErrConnectionStandAlone5 = 11; \/\/THIS\r\n           {some text}\r\n               LMsgExitConfirm = 250;\r\n           ...\r\n           ----- cut -----\r\n\r\n       Then you do: (without confirmation)\r\n           :'<,'>Inc\r\n\r\n       You get:\r\n           ----- cut -----\r\n                   LMsgInstall6 = 100; \/\/ 0\r\n                 LMsgInstall7 = 125;   \/\/ 1\r\n               LMsgInstall8 = 150;     \/\/ 2\r\n\r\n               {STANDALONE}\r\n               LErrConnectionStandAlone1 = 5; \/\/THIS\r\n               LErrConnectionStandAlone3 = 8; \/\/THIS\r\n               LErrConnectionStandAlone5 = 11; \/\/THIS\r\n           {some text}\r\n               LMsgExitConfirm = 250;\r\n           ...\r\n           ----- cut -----\r\n\r\nHope it helps.\r\n\r\nKeywords: Inc Increment increment increment.vimnumber numbers num replace substitute subst pattern regex","4":"This is a great (I think) improvement of the plugin increment.vim made by William Natter (natter at magma.ca) (vimscript #842). \r\n\r\nI tried to contact William, but his mailbox does not exist... So here it goes.\r\n\r\nAs William wrote:\r\n\"This is a handy plugin that makes easy replacing your favorite pattern (\"@\" by default) with a sequence of incremented values using the \"Inc\" command.  \"\r\n\r\nBesides what the original script can do, it has two new features:\r\n    a) Now you are able to search for a pattern and replace the Nth word from the beginning of the line with the incremental number. \r\n    b) And also you can get a confirmation message before change.\r\n\r\nThe help file is also greatly improved.\r\n\r\nHere is an example:\r\n\r\n       You have: (beginning with spaces only)\r\n           ----- cut -----\r\n                   LMsgInstall6 = 7; \/\/ @\r\n                 LMsgInstall7 = 8;   \/\/ @\r\n               LMsgInstall8 = 9;     \/\/ @\r\n\r\n               {STANDALONE}\r\n               LErrConnectionStandAlone1 = 10; \/\/THIS\r\n               LErrConnectionStandAlone3 = 7; \/\/THIS\r\n               LErrConnectionStandAlone5 = 12; \/\/THIS\r\n           {some text}\r\n               LMsgExitConfirm = 30;\r\n           ...\r\n           ----- cut -----\r\n\r\n       You do: (with confirmation) \r\n           :'<,'>Inc p^\\ *\\\\\\<\\[A-Za-z0-9_]*\\\\\\>\\ =\\ [0-9]* w3 i25 s100 c\r\n                                   (Note that I had to use tree \"\\\" before the \"<\" sign. Since Vim 7 the \"<\" and \">\" have to be skiped by a \"\\\")\r\n\r\n       You get:\r\n           ----- cut -----\r\n                   LMsgInstall6 = 100; \/\/ @\r\n                 LMsgInstall7 = 125;   \/\/ @\r\n               LMsgInstall8 = 150;     \/\/ @\r\n\r\n               {STANDALONE}\r\n               LErrConnectionStandAlone1 = 175; \/\/THIS\r\n               LErrConnectionStandAlone3 = 200; \/\/THIS\r\n               LErrConnectionStandAlone5 = 225; \/\/THIS\r\n           {some text}\r\n               LMsgExitConfirm = 250;\r\n           ...\r\n           ----- cut -----\r\n\r\n       Then you do: (without confirmation)\r\n           :'<,'>Inc pTHIS w3 i3 s5\r\n\r\n       You get:\r\n           ----- cut -----\r\n                   LMsgInstall6 = 100; \/\/ @\r\n                 LMsgInstall7 = 125;   \/\/ @\r\n               LMsgInstall8 = 150;     \/\/ @\r\n\r\n               {STANDALONE}\r\n               LErrConnectionStandAlone1 = 5; \/\/THIS\r\n               LErrConnectionStandAlone3 = 8; \/\/THIS\r\n               LErrConnectionStandAlone5 = 11; \/\/THIS\r\n           {some text}\r\n               LMsgExitConfirm = 250;\r\n           ...\r\n           ----- cut -----\r\n\r\n       Then you do: (without confirmation)\r\n           :'<,'>Inc\r\n\r\n       You get:\r\n           ----- cut -----\r\n                   LMsgInstall6 = 100; \/\/ 0\r\n                 LMsgInstall7 = 125;   \/\/ 1\r\n               LMsgInstall8 = 150;     \/\/ 2\r\n\r\n               {STANDALONE}\r\n               LErrConnectionStandAlone1 = 5; \/\/THIS\r\n               LErrConnectionStandAlone3 = 8; \/\/THIS\r\n               LErrConnectionStandAlone5 = 11; \/\/THIS\r\n           {some text}\r\n               LMsgExitConfirm = 250;\r\n           ...\r\n           ----- cut -----\r\n\r\nHope it helps.\r\n\r\nKeywords: Inc Increment increment increment.vimnumber numbers num replace substitute subst pattern regex","install_details":"- Put increment_new.vim into a plugin directory.\r\n- Put increment_new.txt into a doc directory.\r\n\r\n  (see :set runtimepath)\r\n\r\nFor example in *nix OS:\r\n    - The plugin directory should be: ~\/.vim\/plugin\r\n    - The doc directory should be: ~\/.vim\/doc\r\n\r\n    Something like:\r\n        mkdir ~\/.vim\r\n        cd ~\/.vim\r\n        tar -zxvf increment_new.tar.gz\r\n\r\nFor example in Windows:\r\n    - The plugin directory should be: %PROGRAMFILES%\\Vim\\vimfiles\\plugin\r\n    - The doc directory should be: %PROGRAMFILES%\\Vim\\vimfiles\\doc\r\n\r\n    (To extract the files from a tar.gz in windows, I use a great program called 7Zip (http:\/\/www.7-zip.org)\r\n\r\n-Install Help\r\n    To be able to do:\r\n        :help Inc\r\n    in vim, you have to do, for example:\r\n        :helptags ~\/.vim\/doc\r\nor\r\n        :helptags C:\\Program Files\\Vim\\vimfiles\\doc\r\n\r\n","5":"- Put increment_new.vim into a plugin directory.\r\n- Put increment_new.txt into a doc directory.\r\n\r\n  (see :set runtimepath)\r\n\r\nFor example in *nix OS:\r\n    - The plugin directory should be: ~\/.vim\/plugin\r\n    - The doc directory should be: ~\/.vim\/doc\r\n\r\n    Something like:\r\n        mkdir ~\/.vim\r\n        cd ~\/.vim\r\n        tar -zxvf increment_new.tar.gz\r\n\r\nFor example in Windows:\r\n    - The plugin directory should be: %PROGRAMFILES%\\Vim\\vimfiles\\plugin\r\n    - The doc directory should be: %PROGRAMFILES%\\Vim\\vimfiles\\doc\r\n\r\n    (To extract the files from a tar.gz in windows, I use a great program called 7Zip (http:\/\/www.7-zip.org)\r\n\r\n-Install Help\r\n    To be able to do:\r\n        :help Inc\r\n    in vim, you have to do, for example:\r\n        :helptags ~\/.vim\/doc\r\nor\r\n        :helptags C:\\Program Files\\Vim\\vimfiles\\doc\r\n\r\n","first_name":"Ely","6":"Ely","last_name":"Schoenfeld","7":"Schoenfeld","releases":[{"0":"1199","vim_version":"7.0","1":"7.0","script_version":"1.1","2":"1.1","version_comment":"Changes in documentation for better installation instructions and since something changed in the regular expression matching in Vim7.\r\nNow I have to escape the \"<\" and \">\" with \"\\\"","3":"Changes in documentation for better installation instructions and since something changed in the regular expression matching in Vim7.\r\nNow I have to escape the \"<\" and \">\" with \"\\\"","package":"increment_new.tar.gz","4":"increment_new.tar.gz","src_id":"7296","5":"7296","creation_date":"1182592037","6":"1182592037"},{"0":"1199","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"increment_new.tar.gz","4":"increment_new.tar.gz","src_id":"3830","5":"3830","creation_date":"1107523600","6":"1107523600"}]},"1198":{"script_id":"1198","0":"1198","script_name":"nodiff.vim","1":"nodiff.vim","script_type":"utility","2":"utility","summary":"defines Nodiff command to get out of diff mode","3":"defines Nodiff command to get out of diff mode","description":"This script provides :Nodiff command, which turns off the diff mode in each window.  When called as :Nodiff! it will turn off the diff mode in all existing buffers including the hidden ones.","4":"This script provides :Nodiff command, which turns off the diff mode in each window.  When called as :Nodiff! it will turn off the diff mode in all existing buffers including the hidden ones.","install_details":"Just copy this script to the plugin directory or source it from the vimrc file.","5":"Just copy this script to the plugin directory or source it from the vimrc file.","first_name":"Pavol","6":"Pavol","last_name":"Juhas","7":"Juhas","releases":[{"0":"1198","vim_version":"6.0","1":"6.0","script_version":"1.2","2":"1.2","version_comment":"fixed bug, Nodiff! now checks the last buffer","3":"fixed bug, Nodiff! now checks the last buffer","package":"nodiff.vim","4":"nodiff.vim","src_id":"3829","5":"3829","creation_date":"1107501129","6":"1107501129"},{"0":"1198","vim_version":"6.0","1":"6.0","script_version":"1.1","2":"1.1","version_comment":"Initial upload","3":"Initial upload","package":"nodiff.vim","4":"nodiff.vim","src_id":"3828","5":"3828","creation_date":"1107431163","6":"1107431163"}]},"1197":{"script_id":"1197","0":"1197","script_name":"ocaml.annot.pl","1":"ocaml.annot.pl","script_type":"utility","2":"utility","summary":"Displays OCaml type annotations","3":"Displays OCaml type annotations","description":"When editing a OCaml file for which annotations have been compiled, press <F3> and get a message with the type of the value under the cursor.\r\n\r\nI didn't want to use the python code from original ocaml.vim in omlet.vim (script_id=1196), so I wrote this tiny hack using an external perl script -- no need for feature \"perl\". I only print out the first line, because I found no convenient way to print everything without having the message bar to grow big, mess the screen and have a prompt... To be continued.\r\n","4":"When editing a OCaml file for which annotations have been compiled, press <F3> and get a message with the type of the value under the cursor.\r\n\r\nI didn't want to use the python code from original ocaml.vim in omlet.vim (script_id=1196), so I wrote this tiny hack using an external perl script -- no need for feature \"perl\". I only print out the first line, because I found no convenient way to print everything without having the message bar to grow big, mess the screen and have a prompt... To be continued.\r\n","install_details":"Add this to your .vimrc, supposing you put ocaml.annot.pl in you ~\/.vim\/scripts:\r\n\r\nautocmd FileType omlet nmap <F3> :exec 'echomsg (system(\"~\/.vim\/scripts\/ocaml.annot.pl' bufname('%') (line2byte(line('.'))+col('.')-1) '\"))'<RETURN>\r\n","5":"Add this to your .vimrc, supposing you put ocaml.annot.pl in you ~\/.vim\/scripts:\r\n\r\nautocmd FileType omlet nmap <F3> :exec 'echomsg (system(\"~\/.vim\/scripts\/ocaml.annot.pl' bufname('%') (line2byte(line('.'))+col('.')-1) '\"))'<RETURN>\r\n","first_name":"David","6":"David","last_name":"Baelde","7":"Baelde","releases":[{"0":"1197","vim_version":"7.0","1":"7.0","script_version":"0.2","2":"0.2","version_comment":"Update from John Alfred Nathanael Chee: print multi-line types, and slightly tighter parsing of the annot file.","3":"Update from John Alfred Nathanael Chee: print multi-line types, and slightly tighter parsing of the annot file.","package":"ocaml.annot.pl","4":"ocaml.annot.pl","src_id":"13870","5":"13870","creation_date":"1284917860","6":"1284917860"},{"0":"1197","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"ocaml.annot.pl","4":"ocaml.annot.pl","src_id":"3827","5":"3827","creation_date":"1107376761","6":"1107376761"}]},"1196":{"script_id":"1196","0":"1196","script_name":"omlet.vim","1":"omlet.vim","script_type":"indent","2":"indent","summary":"Much better OCaml indentation, and more...","3":"Much better OCaml indentation, and more...","description":"OMLet provides a much better indentation for Caml\/OCaml files than the official one. It mostly behaves as tuareg-mode for emacs does. Omlet supports most of the language features, including objects. I believe that the result is already very convincing, check at (http:\/\/perso.ens-lyon.fr\/david.baelde\/productions\/omlet.php). You are no more forced to switch to emacs for editing OCaml! And omlet also provides nice folding...\r\n\r\nOMLet is nearly stable, and will then be included as official OCaml indentation file in VIm. For now, it is available in the Debian package ocaml-tools.","4":"OMLet provides a much better indentation for Caml\/OCaml files than the official one. It mostly behaves as tuareg-mode for emacs does. Omlet supports most of the language features, including objects. I believe that the result is already very convincing, check at (http:\/\/perso.ens-lyon.fr\/david.baelde\/productions\/omlet.php). You are no more forced to switch to emacs for editing OCaml! And omlet also provides nice folding...\r\n\r\nOMLet is nearly stable, and will then be included as official OCaml indentation file in VIm. For now, it is available in the Debian package ocaml-tools.","install_details":"See the file INSTALL included in the tarball, or run make install blindly...\r\n","5":"See the file INSTALL included in the tarball, or run make install blindly...\r\n","first_name":"David","6":"David","last_name":"Baelde","7":"Baelde","releases":[{"0":"1196","vim_version":"6.0","1":"6.0","script_version":"0.13","2":"0.13","version_comment":"Add: support for 'c', \"=\" and [|..|]\r\nBug: parsing of expression and comment un-skipping\r\nComments are now always aligned on the next block","3":"Add: support for 'c', \"=\" and [|..|]\r\nBug: parsing of expression and comment un-skipping\r\nComments are now always aligned on the next block","package":"omlet-0.13.tar.gz","4":"omlet-0.13.tar.gz","src_id":"4135","5":"4135","creation_date":"1112926946","6":"1112926946"},{"0":"1196","vim_version":"6.0","1":"6.0","script_version":"0.12","2":"0.12","version_comment":"Bug: omlet now overrides correctly the caml.vim files: autodetect used to do a useless job for syntax and ftplugin...\r\nAdd: OCaml modeline\r\nAdd: * in the middle of comments is customizable\r\nBug: Auto indent is less tricked by keyword prefixed names\r\nBug: Many minor bugs\r\n","3":"Bug: omlet now overrides correctly the caml.vim files: autodetect used to do a useless job for syntax and ftplugin...\r\nAdd: OCaml modeline\r\nAdd: * in the middle of comments is customizable\r\nBug: Auto indent is less tricked by keyword prefixed names\r\nBug: Many minor bugs\r\n","package":"omlet-0.12.tar.gz","4":"omlet-0.12.tar.gz","src_id":"4074","5":"4074","creation_date":"1111750824","6":"1111750824"},{"0":"1196","vim_version":"6.0","1":"6.0","script_version":"0.11","2":"0.11","version_comment":"Bug: The parsing functions were weak, and were rewritten.\r\nAdd: More infix operators are now understood.\r\nBug: Many other bugs corrected by the way..","3":"Bug: The parsing functions were weak, and were rewritten.\r\nAdd: More infix operators are now understood.\r\nBug: Many other bugs corrected by the way..","package":"omlet-0.11.tar.gz","4":"omlet-0.11.tar.gz","src_id":"4020","5":"4020","creation_date":"1110824085","6":"1110824085"},{"0":"1196","vim_version":"6.0","1":"6.0","script_version":"0.10","2":"0.10","version_comment":"Bug: indentation after while\/for\r\nBug: parenthesis on the master keyword's line\r\nBug: ! was not parsed correctly\r\nBetter integration with the official file, new syntax & code annotations...","3":"Bug: indentation after while\/for\r\nBug: parenthesis on the master keyword's line\r\nBug: ! was not parsed correctly\r\nBetter integration with the official file, new syntax & code annotations...","package":"omlet-0.10.tar.gz","4":"omlet-0.10.tar.gz","src_id":"3996","5":"3996","creation_date":"1110464694","6":"1110464694"},{"0":"1196","vim_version":"6.0","1":"6.0","script_version":"0.9","2":"0.9","version_comment":"Bug: folding works whatever the value of ocaml_indent_struct is\r\nBug: issues with patterns\r\nAnd cleaning, optimizations...","3":"Bug: folding works whatever the value of ocaml_indent_struct is\r\nBug: issues with patterns\r\nAnd cleaning, optimizations...","package":"omlet-0.9.tar.gz","4":"omlet-0.9.tar.gz","src_id":"3993","5":"3993","creation_date":"1110436803","6":"1110436803"},{"0":"1196","vim_version":"6.0","1":"6.0","script_version":"0.8","2":"0.8","version_comment":"Bug Corrected again the type definition indentation\r\nBug Better handling of comments when parsing\r\nAdd Better installation procedure, including system-wide installation\r\n","3":"Bug Corrected again the type definition indentation\r\nBug Better handling of comments when parsing\r\nAdd Better installation procedure, including system-wide installation\r\n","package":"omlet-0.8.tar.gz","4":"omlet-0.8.tar.gz","src_id":"3947","5":"3947","creation_date":"1109693152","6":"1109693152"},{"0":"1196","vim_version":"6.0","1":"6.0","script_version":"0.7","2":"0.7","version_comment":"Add Flexible indentation nearly everywhere\r\nAdd Much more customization","3":"Add Flexible indentation nearly everywhere\r\nAdd Much more customization","package":"omlet.tar.gz","4":"omlet.tar.gz","src_id":"3909","5":"3909","creation_date":"1109330937","6":"1109330937"},{"0":"1196","vim_version":"6.0","1":"6.0","script_version":"0.6","2":"0.6","version_comment":"Bug: Sum type definition\r\nAdd: Polymorphic variants\r\nAdd: Customization is starting\r\nMany minor fixes...","3":"Bug: Sum type definition\r\nAdd: Polymorphic variants\r\nAdd: Customization is starting\r\nMany minor fixes...","package":"omlet.tar.gz","4":"omlet.tar.gz","src_id":"3879","5":"3879","creation_date":"1108752266","6":"1108752266"},{"0":"1196","vim_version":"6.0","1":"6.0","script_version":"0.5","2":"0.5","version_comment":"Add Plugins from the official files\r\nCleaning of indentation code, minor fixes","3":"Add Plugins from the official files\r\nCleaning of indentation code, minor fixes","package":"omlet.tar.gz","4":"omlet.tar.gz","src_id":"3867","5":"3867","creation_date":"1108393386","6":"1108393386"},{"0":"1196","vim_version":"6.0","1":"6.0","script_version":"0.4","2":"0.4","version_comment":"Add: indent 'and' in let\/and\/...\/in\r\nBug: file didn't load twice correctly\r\nAnd more work on having it working for everybody","3":"Add: indent 'and' in let\/and\/...\/in\r\nBug: file didn't load twice correctly\r\nAnd more work on having it working for everybody","package":"omlet.tar.gz","4":"omlet.tar.gz","src_id":"3844","5":"3844","creation_date":"1107929601","6":"1107929601"},{"0":"1196","vim_version":"6.0","1":"6.0","script_version":"0.3","2":"0.3","version_comment":"Add: Indentation of ;;\r\nBug: Variables names beginning with let\r\nBug: Toplevel \"let\" after end of modules\/classes\r\nBug: Many Makefile fixes","3":"Add: Indentation of ;;\r\nBug: Variables names beginning with let\r\nBug: Toplevel \"let\" after end of modules\/classes\r\nBug: Many Makefile fixes","package":"omlet.tar.gz","4":"omlet.tar.gz","src_id":"3842","5":"3842","creation_date":"1107881369","6":"1107881369"},{"0":"1196","vim_version":"6.0","1":"6.0","script_version":"0.2","2":"0.2","version_comment":"Minor (|| and && added) and major (bug with then let _ = ... ; ...) enhancements","3":"Minor (|| and && added) and major (bug with then let _ = ... ; ...) enhancements","package":"omlet.tar.gz","4":"omlet.tar.gz","src_id":"3833","5":"3833","creation_date":"1107627110","6":"1107627110"},{"0":"1196","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Minor correction in Makefile.","3":"Minor correction in Makefile.","package":"omlet.tar.gz","4":"omlet.tar.gz","src_id":"3826","5":"3826","creation_date":"1107360446","6":"1107360446"}]},"1195":{"script_id":"1195","0":"1195","script_name":"vis","1":"vis","script_type":"utility","2":"utility","summary":"Extended Visual Mode Commands, Substitutes, and Searches","3":"Extended Visual Mode Commands, Substitutes, and Searches","description":"I'm hereby making the <vis.vim> script, long available at http:\/\/www.drchip.org\/astronaut\/vim\/index.html#VIS, also available here at vim.sf.net.  There are two commands made available: B and S.\r\n\r\n\r\n----------------\r\nVisual Commands:\r\n----------------\r\n\r\n    B\r\n\r\n    Use V, v, or ctrl-v to visually mark some region.  Then use\r\n       :B cmd     (this command will appear as:   :'<,'>B cmd)\r\n\r\n    The command will then be applied to just the visually selected region.\r\n    For examples:\r\n\r\n      Use ctrl-v to select a column and then do a substitute on just that column.  \r\n      ctrl-v ..move.. :B s\/pattern\/becomes\/\r\n    \r\n      Use ctrl-v to select a column, then apply an external filter to just that column.\r\n      ctrl-v ..move.. :B !sort\r\n\r\n\r\n----------------\r\nVisual Searches:\r\n----------------\r\n\r\n    S\r\n\r\n    Use V, v, or ctrl-v to visually mark some region.  Then use\r\n        :S pattern   (this search will appear as     :'<,'>S pattern)\r\n\r\n    The search will then be applied to just the visually selected region.\r\n    It may be repeated with n and N commands, too (without having to\r\n    re-mark the region).  A plain S will apply the last :S-pattern\r\n    to the latest selected region.\r\n\r\n\r\n-----------------\r\nRelated Subjects:\r\n-----------------\r\n\r\n * For incrementing\/decrementing numbers, dates, and letters in a column: see vimscript#670 and vimtip#150\r\n * For sorting based on a column (column-restricted, whole lines but column-keyed), see vimtip#588\r\n * For overwriting visual blocks with other visual blocks: see vimtip#808\r\n * For more on applying substitutes to a visual block: see vimtip#63\r\n * For swapping pairs of visual blocks: see vimtip#329\r\n\r\n(alpha\/beta version available at http:\/\/www.drchip.org\/astronaut\/vim\/index.html#VIS)\r\n","4":"I'm hereby making the <vis.vim> script, long available at http:\/\/www.drchip.org\/astronaut\/vim\/index.html#VIS, also available here at vim.sf.net.  There are two commands made available: B and S.\r\n\r\n\r\n----------------\r\nVisual Commands:\r\n----------------\r\n\r\n    B\r\n\r\n    Use V, v, or ctrl-v to visually mark some region.  Then use\r\n       :B cmd     (this command will appear as:   :'<,'>B cmd)\r\n\r\n    The command will then be applied to just the visually selected region.\r\n    For examples:\r\n\r\n      Use ctrl-v to select a column and then do a substitute on just that column.  \r\n      ctrl-v ..move.. :B s\/pattern\/becomes\/\r\n    \r\n      Use ctrl-v to select a column, then apply an external filter to just that column.\r\n      ctrl-v ..move.. :B !sort\r\n\r\n\r\n----------------\r\nVisual Searches:\r\n----------------\r\n\r\n    S\r\n\r\n    Use V, v, or ctrl-v to visually mark some region.  Then use\r\n        :S pattern   (this search will appear as     :'<,'>S pattern)\r\n\r\n    The search will then be applied to just the visually selected region.\r\n    It may be repeated with n and N commands, too (without having to\r\n    re-mark the region).  A plain S will apply the last :S-pattern\r\n    to the latest selected region.\r\n\r\n\r\n-----------------\r\nRelated Subjects:\r\n-----------------\r\n\r\n * For incrementing\/decrementing numbers, dates, and letters in a column: see vimscript#670 and vimtip#150\r\n * For sorting based on a column (column-restricted, whole lines but column-keyed), see vimtip#588\r\n * For overwriting visual blocks with other visual blocks: see vimtip#808\r\n * For more on applying substitutes to a visual block: see vimtip#63\r\n * For swapping pairs of visual blocks: see vimtip#329\r\n\r\n(alpha\/beta version available at http:\/\/www.drchip.org\/astronaut\/vim\/index.html#VIS)\r\n","install_details":"vim vis.vba.gz\r\n:so %\r\n\r\n(uses vimscript#1502's vimball archiver)\r\n","5":"vim vis.vba.gz\r\n:so %\r\n\r\n(uses vimscript#1502's vimball archiver)\r\n","first_name":"Charles","6":"Charles","last_name":"Campbell","7":"Campbell","releases":[{"0":"1195","vim_version":"7.0","1":"7.0","script_version":"20","2":"20","version_comment":"Split into a plugin\/autoload pair (faster vim startup).\r\nCedit bypassed in vis.vim (bugfix).\r\nFixed bug where VisBlockCmd() effectively shortened a visual block selection due to a short last line.","3":"Split into a plugin\/autoload pair (faster vim startup).\r\nCedit bypassed in vis.vim (bugfix).\r\nFixed bug where VisBlockCmd() effectively shortened a visual block selection due to a short last line.","package":"vis.vba.gz","4":"vis.vba.gz","src_id":"19723","5":"19723","creation_date":"1364567639","6":"1364567639"},{"0":"1195","vim_version":"7.0","1":"7.0","script_version":"19","2":"19","version_comment":"improvement -- cecutil updated to use keepjumps (vim 7.0)\r\nbugfix -- small mod made to allow AlignMaps to work with visual blocks (...:B norm \\somemap)\r\nbugfix -- works around formatoption setting\r\n","3":"improvement -- cecutil updated to use keepjumps (vim 7.0)\r\nbugfix -- small mod made to allow AlignMaps to work with visual blocks (...:B norm \\somemap)\r\nbugfix -- works around formatoption setting\r\n","package":"vis.vba.gz","4":"vis.vba.gz","src_id":"5847","5":"5847","creation_date":"1150805314","6":"1150805314"},{"0":"1195","vim_version":"6.0","1":"6.0","script_version":"18","2":"18","version_comment":"Bugfix - vis.vim now works around a virtcol() behavior difference between ve=all vs ve=block\r\n(effect -- a ctrl-v selected region, with ve=block and a short last line, didn't build a search pattern for the entire block)","3":"Bugfix - vis.vim now works around a virtcol() behavior difference between ve=all vs ve=block\r\n(effect -- a ctrl-v selected region, with ve=block and a short last line, didn't build a search pattern for the entire block)","package":"vis.tar.gz","4":"vis.tar.gz","src_id":"4529","5":"4529","creation_date":"1125056954","6":"1125056954"},{"0":"1195","vim_version":"6.0","1":"6.0","script_version":"17","2":"17","version_comment":"Vis.vim now uses cecutil.vim functions; I've now included them in the tarball to make installation simpler.","3":"Vis.vim now uses cecutil.vim functions; I've now included them in the tarball to make installation simpler.","package":"vis.tar.gz","4":"vis.tar.gz","src_id":"4199","5":"4199","creation_date":"1114413687","6":"1114413687"},{"0":"1195","vim_version":"6.0","1":"6.0","script_version":"16","2":"16","version_comment":"* Both B and S visual mode commands now use <q-args> instead of <args>\r\n* Visual character selections (v) didn't restrict itself to the selected region when either ignorecase is used or if only one or two lines were in the region.\r\n","3":"* Both B and S visual mode commands now use <q-args> instead of <args>\r\n* Visual character selections (v) didn't restrict itself to the selected region when either ignorecase is used or if only one or two lines were in the region.\r\n","package":"vis.vim.gz","4":"vis.vim.gz","src_id":"4164","5":"4164","creation_date":"1113476965","6":"1113476965"},{"0":"1195","vim_version":"6.0","1":"6.0","script_version":"15","2":"15","version_comment":"Visual Commands, Substitutes, and Searches (visual line, character, and block)\r\n","3":"Visual Commands, Substitutes, and Searches (visual line, character, and block)\r\n","package":"vis.vim.gz","4":"vis.vim.gz","src_id":"3823","5":"3823","creation_date":"1107239324","6":"1107239324"}]},"1194":{"script_id":"1194","0":"1194","script_name":"vfp8.vim","1":"vfp8.vim","script_type":"syntax","2":"syntax","summary":"Visual FoxPro 8 syntax file","3":"Visual FoxPro 8 syntax file","description":"Visual FoxPro 8 syntax file heavilly based on vfp.vim (from Edward franks).\r\nI added the typical uppercase conversion for FoxPro keywords and functions but I dropped the 4 letter abbreviations.","4":"Visual FoxPro 8 syntax file heavilly based on vfp.vim (from Edward franks).\r\nI added the typical uppercase conversion for FoxPro keywords and functions but I dropped the 4 letter abbreviations.","install_details":"copy to ~\/.vim\/syntax\r\n","5":"copy to ~\/.vim\/syntax\r\n","first_name":"beno\u00c3\u00aet","6":"beno\u00c3\u00aet","last_name":"liessens","7":"liessens","releases":[{"0":"1194","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"vfp8.vim","4":"vfp8.vim","src_id":"3815","5":"3815","creation_date":"1107090235","6":"1107090235"}]},"1193":{"script_id":"1193","0":"1193","script_name":"expander.vim","1":"expander.vim","script_type":"utility","2":"utility","summary":"flexible expansion of abbreviations\/templates","3":"flexible expansion of abbreviations\/templates","description":"expander.vim requires Vim's Python interface-----\r\n\r\nexpander expands abbreviations. Its abbreviations can take arguments that are repeated in the expanded text. For instance, for C++ iterators you can type:\r\n\r\n@fib@vector<char>@vec<C-e>\r\n\r\nand this expands to:\r\n\r\nfor(vector<char>::iterator i = vec.begin(); i != vec.end(); ++i) {\r\n    *\r\n}\r\n\r\nWith your cursor in the place of the *. Defining new abbreviations is easy. The above one was defined like this:\r\n\r\n\"fib\": \"\"\"\r\nfor($1::iterator i = $2.begin(); i != $2.end(); ++i) {\r\n$#$0\r\n}\"\"\"\r\n\r\nWhen expander expands this, it replaces the string $# with spaces equal to your shiftwidth, it puts the cursor at $0, and it replaces $1, $2, etc, with the first, second, etc, arguments.","4":"expander.vim requires Vim's Python interface-----\r\n\r\nexpander expands abbreviations. Its abbreviations can take arguments that are repeated in the expanded text. For instance, for C++ iterators you can type:\r\n\r\n@fib@vector<char>@vec<C-e>\r\n\r\nand this expands to:\r\n\r\nfor(vector<char>::iterator i = vec.begin(); i != vec.end(); ++i) {\r\n    *\r\n}\r\n\r\nWith your cursor in the place of the *. Defining new abbreviations is easy. The above one was defined like this:\r\n\r\n\"fib\": \"\"\"\r\nfor($1::iterator i = $2.begin(); i != $2.end(); ++i) {\r\n$#$0\r\n}\"\"\"\r\n\r\nWhen expander expands this, it replaces the string $# with spaces equal to your shiftwidth, it puts the cursor at $0, and it replaces $1, $2, etc, with the first, second, etc, arguments.","install_details":"Untar expander.tar.bz2 in your ~\/.vim so that expander.vim goes into plugin\/ and expander.txt goes into doc\/. Run :helptags ~\/.vim\/doc.\r\n:help expander","5":"Untar expander.tar.bz2 in your ~\/.vim so that expander.vim goes into plugin\/ and expander.txt goes into doc\/. Run :helptags ~\/.vim\/doc.\r\n:help expander","first_name":"Michael","6":"Michael","last_name":"Benfield","7":"Benfield","releases":[{"0":"1193","vim_version":"6.0","1":"6.0","script_version":"1","2":"1","version_comment":"Initial upload","3":"Initial upload","package":"expander.tar.bz2","4":"expander.tar.bz2","src_id":"3814","5":"3814","creation_date":"1107080427","6":"1107080427"}]},"1192":{"script_id":"1192","0":"1192","script_name":"AutoUpload","1":"AutoUpload","script_type":"utility","2":"utility","summary":"Put file to remote location with one click","3":"Put file to remote location with one click","description":"Usage:\r\n1. Create autoupload.info (or .autoupload.info) file. Files like those are called 'maps'.\r\n\r\n2. Each line in map is an entry in format:\r\n\tfilename : {ftp|dav|scp|etc...}:\/\/address\r\n\t\tor\r\n\tfilename | {ftp|dav|scp|etc...}:\/\/address\r\n\r\n   >> Address must end with file name! <<\r\n   Example entry:\r\n   localfile.txt | scp:\/\/me@mymachine.com\/tmp\/remfile.txt\r\n\r\n3. Or as an alternative:\r\n    - to first or last lines of buffer to upload add pattern:\r\n               [text]{white}autoupload:remotepath1[;remotepath2[...]]\r\n Example line:\r\n autoupload:scp:\/\/me@mymachine.com\/tmp\/remfile.txt ;ftp:\/\/a@b.com\/c.txt\r\n\r\n4. Then while editing some file pressing <Leader>up ('u' key and 'p' key) will cause script to:\r\n   - read autoupload.info (.autoupload.info) from dir in which active buffer is stored (or from absolute path if customized that way), or scan first and last lines of active buffer,\r\n   - store buffer into remote location(s) extracted.\r\n\r\nIf no entry for actual buffer is found in autoupload.info, then .autoupload.info is examined.\r\n\r\nCustomization:\r\n\r\ng:autoUploadMaps (default: \"autoupload.info:.autoupload.info\")\r\n\r\nFile names\/paths to maps.\r\n\r\nCan contain multiple file names separated  by : or |  Files will be examined in order given in this variable.  Paths can be:\r\n- absolute,\r\n- realtive - they will be appended to path in which actual buffer is stored!\r\n\r\ng:autoUploadScanLines (default: 3)\r\n\r\nScript  can  scan last  and  first lines of a buffer for pattern:\r\n[text]{white}autoupload:remotepath1[;remotepath2[...]]\r\nFields are separated by ';'  or  '|'.  ';' is used because ':' is always a part of protocol for example ftp:\/\/... \r\nThis variable  contains number of  lines  to scan.\r\n\r\ng:autoUploadModelineStart (default: 'autoupload:')\r\n\r\nPattern which 'modeline' should begin with. Can contain regex.\r\n\r\ng:autoUploadUseBuffer (default: 1, possible: 0, 1, 2)\r\n\r\nIf  g:autoUploadUseBuffer  is  set to 0, then no scan is done.\r\nIf  g:autoUploadUseBuffer>g:autoUploadUseMaps then  script will scan  buffer  before  maps.\r\nIf g:autoUploadUseBuffer<=g:autoUploadUseMaps then  script will scan  maps  before  buffer.\r\n\r\ng:autoUploadUseMaps (default: 1, possible: 0, 1, 2)\r\nIf  g:autoUploadUseMaps is set to 0 , then no no maps are searched.\r\nIf g:autoUploadUseMaps=>g:autoUploadUseBuffer then  script will  scan  maps before  buffer.\r\nIf  g:autoUploadUseMaps<g:autoUploadUseBuffer then  script will  scan  buffer before  maps.\r\n\r\ng:autoUploadStopAfterFirstUpload (default: 1)\r\n\r\nIf set to 1 then  maximum one upload  will be done  no matter  how many maps will  have proper entries  and  how  many proper entries will be in one map. In  other  words: Find first remote  location that is assigned to actual buffer, use it and return to editor.  This one variable turns off all multiple upload possibilities.\r\n\r\ng:autoUploadStopAfterFirstMap\t(default: 1)\r\n\r\nIf 1, then processing of maps will stop after first  map  that  had  at  least one matching entry.  So you can assign  multiple remote locations to one file using one map  and  if variable g:autoUploadStopAfterFirstUpload  will be set to 0 then multiple uploads of the same file will be taken according to data in first map that has matching entry.\r\n\r\nCombinations of two last options:\r\n\r\ng:autoUploadStopAfterFirstUpload = 0\r\ng:autoUploadStopAfterFirstMap\t= 1\r\n\r\nThis will do multiple uploads to addresses taken from only one map  ( first one that has some match).\r\n\r\ng:autoUploadStopAfterFirstUpload = 0\r\ng:autoUploadStopAfterFirstMap\t= 0\r\n\r\nThis will  upload  current  buffer  to  every assigned remote location - multiple locations per map and multiple maps will be used.\r\n\r\n:call MG_AutoUpload()\t\tMap this to some key combination\r\n\r\nExample_customization:\r\n\tlet g:autoUploadMaps = \".autoupload.info:\/root\/.remote.inf\"\r\n\tlet g:autoUploadStopAfterFirstUpload = 0\r\n\tnnoremap <F12> :call MG_AutoUpload()<CR>\r\n\r\nWorth_to_read:\r\n:help netrw\r\n\r\nWarning:\r\nGlobal map files are dangerous because file names can repeat (index.php main.c, etc). You should use it for special cases only.\r\n","4":"Usage:\r\n1. Create autoupload.info (or .autoupload.info) file. Files like those are called 'maps'.\r\n\r\n2. Each line in map is an entry in format:\r\n\tfilename : {ftp|dav|scp|etc...}:\/\/address\r\n\t\tor\r\n\tfilename | {ftp|dav|scp|etc...}:\/\/address\r\n\r\n   >> Address must end with file name! <<\r\n   Example entry:\r\n   localfile.txt | scp:\/\/me@mymachine.com\/tmp\/remfile.txt\r\n\r\n3. Or as an alternative:\r\n    - to first or last lines of buffer to upload add pattern:\r\n               [text]{white}autoupload:remotepath1[;remotepath2[...]]\r\n Example line:\r\n autoupload:scp:\/\/me@mymachine.com\/tmp\/remfile.txt ;ftp:\/\/a@b.com\/c.txt\r\n\r\n4. Then while editing some file pressing <Leader>up ('u' key and 'p' key) will cause script to:\r\n   - read autoupload.info (.autoupload.info) from dir in which active buffer is stored (or from absolute path if customized that way), or scan first and last lines of active buffer,\r\n   - store buffer into remote location(s) extracted.\r\n\r\nIf no entry for actual buffer is found in autoupload.info, then .autoupload.info is examined.\r\n\r\nCustomization:\r\n\r\ng:autoUploadMaps (default: \"autoupload.info:.autoupload.info\")\r\n\r\nFile names\/paths to maps.\r\n\r\nCan contain multiple file names separated  by : or |  Files will be examined in order given in this variable.  Paths can be:\r\n- absolute,\r\n- realtive - they will be appended to path in which actual buffer is stored!\r\n\r\ng:autoUploadScanLines (default: 3)\r\n\r\nScript  can  scan last  and  first lines of a buffer for pattern:\r\n[text]{white}autoupload:remotepath1[;remotepath2[...]]\r\nFields are separated by ';'  or  '|'.  ';' is used because ':' is always a part of protocol for example ftp:\/\/... \r\nThis variable  contains number of  lines  to scan.\r\n\r\ng:autoUploadModelineStart (default: 'autoupload:')\r\n\r\nPattern which 'modeline' should begin with. Can contain regex.\r\n\r\ng:autoUploadUseBuffer (default: 1, possible: 0, 1, 2)\r\n\r\nIf  g:autoUploadUseBuffer  is  set to 0, then no scan is done.\r\nIf  g:autoUploadUseBuffer>g:autoUploadUseMaps then  script will scan  buffer  before  maps.\r\nIf g:autoUploadUseBuffer<=g:autoUploadUseMaps then  script will scan  maps  before  buffer.\r\n\r\ng:autoUploadUseMaps (default: 1, possible: 0, 1, 2)\r\nIf  g:autoUploadUseMaps is set to 0 , then no no maps are searched.\r\nIf g:autoUploadUseMaps=>g:autoUploadUseBuffer then  script will  scan  maps before  buffer.\r\nIf  g:autoUploadUseMaps<g:autoUploadUseBuffer then  script will  scan  buffer before  maps.\r\n\r\ng:autoUploadStopAfterFirstUpload (default: 1)\r\n\r\nIf set to 1 then  maximum one upload  will be done  no matter  how many maps will  have proper entries  and  how  many proper entries will be in one map. In  other  words: Find first remote  location that is assigned to actual buffer, use it and return to editor.  This one variable turns off all multiple upload possibilities.\r\n\r\ng:autoUploadStopAfterFirstMap\t(default: 1)\r\n\r\nIf 1, then processing of maps will stop after first  map  that  had  at  least one matching entry.  So you can assign  multiple remote locations to one file using one map  and  if variable g:autoUploadStopAfterFirstUpload  will be set to 0 then multiple uploads of the same file will be taken according to data in first map that has matching entry.\r\n\r\nCombinations of two last options:\r\n\r\ng:autoUploadStopAfterFirstUpload = 0\r\ng:autoUploadStopAfterFirstMap\t= 1\r\n\r\nThis will do multiple uploads to addresses taken from only one map  ( first one that has some match).\r\n\r\ng:autoUploadStopAfterFirstUpload = 0\r\ng:autoUploadStopAfterFirstMap\t= 0\r\n\r\nThis will  upload  current  buffer  to  every assigned remote location - multiple locations per map and multiple maps will be used.\r\n\r\n:call MG_AutoUpload()\t\tMap this to some key combination\r\n\r\nExample_customization:\r\n\tlet g:autoUploadMaps = \".autoupload.info:\/root\/.remote.inf\"\r\n\tlet g:autoUploadStopAfterFirstUpload = 0\r\n\tnnoremap <F12> :call MG_AutoUpload()<CR>\r\n\r\nWorth_to_read:\r\n:help netrw\r\n\r\nWarning:\r\nGlobal map files are dangerous because file names can repeat (index.php main.c, etc). You should use it for special cases only.\r\n","install_details":"Copy it into plugins directory.","5":"Copy it into plugins directory.","first_name":"Mariusz","6":"Mariusz","last_name":"Gniazdowski","7":"Gniazdowski","releases":[{"0":"1192","vim_version":"6.0","1":"6.0","script_version":"1.2","2":"1.2","version_comment":"Remote locations can now be contained in buffers (in 'modelines'). Bugfixes.","3":"Remote locations can now be contained in buffers (in 'modelines'). Bugfixes.","package":"autoupload.vim","4":"autoupload.vim","src_id":"3817","5":"3817","creation_date":"1107105101","6":"1107105101"},{"0":"1192","vim_version":"6.0","1":"6.0","script_version":"1.1","2":"1.1","version_comment":"Feature enhancements: multiple 'maps' files, multiple uploads, more verbosity, absolute paths.","3":"Feature enhancements: multiple 'maps' files, multiple uploads, more verbosity, absolute paths.","package":"autoupload.vim","4":"autoupload.vim","src_id":"3812","5":"3812","creation_date":"1107022750","6":"1107022750"},{"0":"1192","vim_version":"6.0","1":"6.0","script_version":"1.01","2":"1.01","version_comment":"Serious bug fixed ( file name like \"bbcc\" was matching file name \"aabbcc\" and uploaded at wrong address )","3":"Serious bug fixed ( file name like \"bbcc\" was matching file name \"aabbcc\" and uploaded at wrong address )","package":"autoupload.vim","4":"autoupload.vim","src_id":"3811","5":"3811","creation_date":"1106992561","6":"1106992561"},{"0":"1192","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"autoupload.vim","4":"autoupload.vim","src_id":"3807","5":"3807","creation_date":"1106927011","6":"1106927011"}]},"1191":{"script_id":"1191","0":"1191","script_name":"wc.vim","1":"wc.vim","script_type":"utility","2":"utility","summary":"Manuscript word counter - Strunk & White style","3":"Manuscript word counter - Strunk & White style","description":"Provides word count for manuscripts (essay or story documents), compliant with standard author rules (such as Strunk & White style lexicon for English grammar).\r\n\r\nStandard word count utilities (like unix 'wc') do not provide an accurate count because they count breaks between words.  In fiction writing, some sentences--like this one--have more words than breaks between words..\r\n\r\nTo use, install and type :WC\r\n\r\nLine ranges are supported.\r\n\r\nTo count the lines of a particular section of a document, insert a new line with 8 dashes, and the count will stop at that line.\r\n--------\r\nLike that.\r\n\r\nThe word count also ignores the common author mark for section breaks using asterisk as shown below.\r\n \r\n* * * \r\n\r\nThis script is based on the sed 'wc' example provided in the GNU info pages; the algorithm replaces each whitespace seperated word by a single character and then counts the length of the string.\r\n\r\n","4":"Provides word count for manuscripts (essay or story documents), compliant with standard author rules (such as Strunk & White style lexicon for English grammar).\r\n\r\nStandard word count utilities (like unix 'wc') do not provide an accurate count because they count breaks between words.  In fiction writing, some sentences--like this one--have more words than breaks between words..\r\n\r\nTo use, install and type :WC\r\n\r\nLine ranges are supported.\r\n\r\nTo count the lines of a particular section of a document, insert a new line with 8 dashes, and the count will stop at that line.\r\n--------\r\nLike that.\r\n\r\nThe word count also ignores the common author mark for section breaks using asterisk as shown below.\r\n \r\n* * * \r\n\r\nThis script is based on the sed 'wc' example provided in the GNU info pages; the algorithm replaces each whitespace seperated word by a single character and then counts the length of the string.\r\n\r\n","install_details":"Copy to vim plugin directory.\r\nUse with :WC command.\r\n\r\n","5":"Copy to vim plugin directory.\r\nUse with :WC command.\r\n\r\n","first_name":"jcline","6":"jcline","last_name":"","7":"","releases":[{"0":"1191","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"wc.vim","4":"wc.vim","src_id":"3804","5":"3804","creation_date":"1106918919","6":"1106918919"}]},"1190":{"script_id":"1190","0":"1190","script_name":"hcc.vim","1":"hcc.vim","script_type":"syntax","2":"syntax","summary":"Syntax for Handel-C","3":"Syntax for Handel-C","description":"Syntax file for the Handel-C language. Extends the standard C syntax file with the special types and statements found in Handel-C. ","4":"Syntax file for the Handel-C language. Extends the standard C syntax file with the special types and statements found in Handel-C. ","install_details":"Place hcc.vam in .vim\/syntax or the Windows equivalent. \r\n\r\nTo auto-detect handel-c files based on extensions .hcc and .hch write the following (or add the relevant parts) to .vim\/filetype.vim\r\n\r\nif exists(\"did_load_filetypes\")\r\nfinish\r\nendif\r\naugroup filetypedetect\r\nau! BufRead,BufNewFile *.hcc setfiletype hcc\r\nau! BufRead,BufNewFile *.hch setfiletype hcc\r\naugroup END","5":"Place hcc.vam in .vim\/syntax or the Windows equivalent. \r\n\r\nTo auto-detect handel-c files based on extensions .hcc and .hch write the following (or add the relevant parts) to .vim\/filetype.vim\r\n\r\nif exists(\"did_load_filetypes\")\r\nfinish\r\nendif\r\naugroup filetypedetect\r\nau! BufRead,BufNewFile *.hcc setfiletype hcc\r\nau! BufRead,BufNewFile *.hch setfiletype hcc\r\naugroup END","first_name":"Andreas","6":"Andreas","last_name":"Fidjeland","7":"Fidjeland","releases":[{"0":"1190","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"hcc.vim","4":"hcc.vim","src_id":"3803","5":"3803","creation_date":"1106890283","6":"1106890283"}]},"1189":{"script_id":"1189","0":"1189","script_name":"matrix.vim","1":"matrix.vim","script_type":"game","2":"game","summary":"Matrix screensaver for VIM","3":"Matrix screensaver for VIM","description":"Matrix screensaver for VIM, inspired by Chris Allegretta's cmatrix.\r\n\r\nAlso available on github for Vundle users:\r\nhttps:\/\/github.com\/uguu-org\/vim-matrix-screensaver","4":"Matrix screensaver for VIM, inspired by Chris Allegretta's cmatrix.\r\n\r\nAlso available on github for Vundle users:\r\nhttps:\/\/github.com\/uguu-org\/vim-matrix-screensaver","install_details":":so matrix.vim or add script to plugin directory.\r\nstart screensaver with :Matrix, press keys a few times to exit.","5":":so matrix.vim or add script to plugin directory.\r\nstart screensaver with :Matrix, press keys a few times to exit.","first_name":"Don","6":"Don","last_name":"Yang","7":"Yang","releases":[{"0":"1189","vim_version":"6.0","1":"6.0","script_version":"1.10","2":"1.10","version_comment":"Added license text.","3":"Added license text.","package":"matrix.vim","4":"matrix.vim","src_id":"18650","5":"18650","creation_date":"1348254585","6":"1348254585"},{"0":"1189","vim_version":"6.0","1":"6.0","script_version":"1.10","2":"1.10","version_comment":"Disable cursorline\/cursorcolumn\/spell before starting (thanks to Diederick Niehorster for the suggestion).","3":"Disable cursorline\/cursorcolumn\/spell before starting (thanks to Diederick Niehorster for the suggestion).","package":"matrix.vim","4":"matrix.vim","src_id":"8687","5":"8687","creation_date":"1210723575","6":"1210723575"},{"0":"1189","vim_version":"6.0","1":"6.0","script_version":"1.09","2":"1.09","version_comment":"Multiwindow support (thanks to S. Lockwood-Childs for the patch!)","3":"Multiwindow support (thanks to S. Lockwood-Childs for the patch!)","package":"matrix.vim","4":"matrix.vim","src_id":"6533","5":"6533","creation_date":"1166693852","6":"1166693852"},{"0":"1189","vim_version":"6.0","1":"6.0","script_version":"1.08","2":"1.08","version_comment":"added silent! to cursor positioning code to stop drawing numbers during animation.\r\n(Thanks to David Eggum for the suggestion).","3":"added silent! to cursor positioning code to stop drawing numbers during animation.\r\n(Thanks to David Eggum for the suggestion).","package":"matrix.vim","4":"matrix.vim","src_id":"4648","5":"4648","creation_date":"1128367925","6":"1128367925"},{"0":"1189","vim_version":"6.0","1":"6.0","script_version":"1.07","2":"1.07","version_comment":"Disable showmatch (stops random bells on inserting parentheses)","3":"Disable showmatch (stops random bells on inserting parentheses)","package":"matrix.vim","4":"matrix.vim","src_id":"4643","5":"4643","creation_date":"1128269645","6":"1128269645"},{"0":"1189","vim_version":"6.0","1":"6.0","script_version":"1.06","2":"1.06","version_comment":"make new buffer modifiable before running","3":"make new buffer modifiable before running","package":"matrix.vim","4":"matrix.vim","src_id":"4036","5":"4036","creation_date":"1111004593","6":"1111004593"},{"0":"1189","vim_version":"6.0","1":"6.0","script_version":"1.05","2":"1.05","version_comment":"Added sleep to consume less CPU (also fixes undo bell issue)\r\nRemoved frame counter","3":"Added sleep to consume less CPU (also fixes undo bell issue)\r\nRemoved frame counter","package":"matrix.vim","4":"matrix.vim","src_id":"3801","5":"3801","creation_date":"1106817882","6":"1106817882"},{"0":"1189","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"matrix.vim","4":"matrix.vim","src_id":"3799","5":"3799","creation_date":"1106779886","6":"1106779886"}]},"1188":{"script_id":"1188","0":"1188","script_name":"cleanswap","1":"cleanswap","script_type":"utility","2":"utility","summary":"capture useful text from, and delete, all the vim swap files in ~\/.vim\/swap","3":"capture useful text from, and delete, all the vim swap files in ~\/.vim\/swap","description":"This is a super-simple bash script for cleaning up my ~\/.vim\/swap directory.  I have vim put all its swap files there (set directory=~\/.vim\/swap) so I can find them in one place.\r\n\r\nWhen I run this script, it recovers using each swap file and compares the results against the current version of the file.  If there is no difference, the swap file is automatically deleted. If there are differences, vimdiff is launched so I can recover any changes saved only in the swap file.  When the script is don running, all my swap files are gone.\r\n\r\nWarning: This script has only been tested on Linux, and that only a couple times. It may accidentally delete any file on your system.  If you have any other vim sessions running, I assume bad things will happen if you also run this script.  Use at your own risk!","4":"This is a super-simple bash script for cleaning up my ~\/.vim\/swap directory.  I have vim put all its swap files there (set directory=~\/.vim\/swap) so I can find them in one place.\r\n\r\nWhen I run this script, it recovers using each swap file and compares the results against the current version of the file.  If there is no difference, the swap file is automatically deleted. If there are differences, vimdiff is launched so I can recover any changes saved only in the swap file.  When the script is don running, all my swap files are gone.\r\n\r\nWarning: This script has only been tested on Linux, and that only a couple times. It may accidentally delete any file on your system.  If you have any other vim sessions running, I assume bad things will happen if you also run this script.  Use at your own risk!","install_details":"Copy this to some directory in your PATH.  Run it.","5":"Copy this to some directory in your PATH.  Run it.","first_name":"Chris","6":"Chris","last_name":"Houser","7":"Houser","releases":[{"0":"1188","vim_version":"7.0","1":"7.0","script_version":"0.1","2":"0.1","version_comment":"Improvements in stability, bug fixes... you know, that sort of thing.","3":"Improvements in stability, bug fixes... you know, that sort of thing.","package":"cleanswap","4":"cleanswap","src_id":"6265","5":"6265","creation_date":"1160469101","6":"1160469101"},{"0":"1188","vim_version":"6.0","1":"6.0","script_version":"0.0","2":"0.0","version_comment":"Initial upload","3":"Initial upload","package":"cleanswap","4":"cleanswap","src_id":"3789","5":"3789","creation_date":"1106398037","6":"1106398037"}]},"1187":{"script_id":"1187","0":"1187","script_name":"cream-replacemulti","1":"cream-replacemulti","script_type":"utility","2":"utility","summary":"Replace text across multiple files","3":"Replace text across multiple files","description":"\r\nThis script replaces text across multiple files. It is a pure Vim implementation and does not depend on external utilties that do similar things (like sed, grep, cat, or Find). As such, it is cross-platform and has been tested on both Windows95\/XP and Linux.\r\n\r\nReplace Multi is intended to be used in the GUI version of Vim, gVim. It presents a rather hackish dialog to take user input for the Find, Replace, and Path components and present options for Case Sensitivity and the use of Vim's Regular Expressions. (Some day in the future it might be adapted to work from the command line without a dialog.)\r\n\r\nIn testing, Replace Multi performed a replacment operation on 1000 small files in 25 seconds. (2.80Ghz Pentium 4 Windows XP machine with 1Gb of RAM.) Obviously Vim and system settings could vary this greatly, but as a benchmark this is about 40 files\/second.\r\n\r\n\r\nThis is one of many custom utilities and functions for gVim from the Cream project (http:\/\/cream.sourceforge.net), a configuration of Vim for those of us familiar with Apple and Windows software.\r\n\r\n","4":"\r\nThis script replaces text across multiple files. It is a pure Vim implementation and does not depend on external utilties that do similar things (like sed, grep, cat, or Find). As such, it is cross-platform and has been tested on both Windows95\/XP and Linux.\r\n\r\nReplace Multi is intended to be used in the GUI version of Vim, gVim. It presents a rather hackish dialog to take user input for the Find, Replace, and Path components and present options for Case Sensitivity and the use of Vim's Regular Expressions. (Some day in the future it might be adapted to work from the command line without a dialog.)\r\n\r\nIn testing, Replace Multi performed a replacment operation on 1000 small files in 25 seconds. (2.80Ghz Pentium 4 Windows XP machine with 1Gb of RAM.) Obviously Vim and system settings could vary this greatly, but as a benchmark this is about 40 files\/second.\r\n\r\n\r\nThis is one of many custom utilities and functions for gVim from the Cream project (http:\/\/cream.sourceforge.net), a configuration of Vim for those of us familiar with Apple and Windows software.\r\n\r\n","install_details":"\r\nThis script is dependant on MultVals (http:\/\/www.vim.org\/script.php?script_id=171).\r\n\r\nJust drop cream-replacemulti.vim and multvals.vim into your plugins directory. Then (re)start Vim and use the command line to call function Cream_replacemulti():\r\n\r\n  :call Cream_replacemulti()\r\n\r\nor use mappings like:\r\n\r\n  imap <C-F3> <C-o>:call Cream_replacemulti()<CR>\r\n  vmap <C-F3> :<C-u>call Cream_replacemulti()<CR>\r\n  nmap <C-F3>      :call Cream_replacemulti()<CR>\r\n\r\n","5":"\r\nThis script is dependant on MultVals (http:\/\/www.vim.org\/script.php?script_id=171).\r\n\r\nJust drop cream-replacemulti.vim and multvals.vim into your plugins directory. Then (re)start Vim and use the command line to call function Cream_replacemulti():\r\n\r\n  :call Cream_replacemulti()\r\n\r\nor use mappings like:\r\n\r\n  imap <C-F3> <C-o>:call Cream_replacemulti()<CR>\r\n  vmap <C-F3> :<C-u>call Cream_replacemulti()<CR>\r\n  nmap <C-F3>      :call Cream_replacemulti()<CR>\r\n\r\n","first_name":"Steve","6":"Steve","last_name":"Hall","7":"Hall","releases":[{"0":"1187","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"cream-replacemulti.vim","4":"cream-replacemulti.vim","src_id":"3787","5":"3787","creation_date":"1106223188","6":"1106223188"}]},"1186":{"script_id":"1186","0":"1186","script_name":"rotate.vim","1":"rotate.vim","script_type":"utility","2":"utility","summary":"This file enables Vim to rotate text (counter) clockwise, put it upside down,etc","3":"This file enables Vim to rotate text (counter) clockwise, put it upside down,etc","description":"This script enables Vim to do things like rotate text (counter) clockwise (l\/r), put it upside down (u),\r\nexchange lines and columns (x), reorder it from right to left (h) or from bottom to top (v).\r\nThe command :<range>Rot [arg] allows a range in which this will be done.\r\nIf no range is specified the current line is taken. The optional argument (in parenthesis) specifies which\r\noperation is performed. If none is given, lines and columns are exchanged.\r\nThe command :Rotv [arg] operates on the last visual area and is good for use in Visual mode.\r\nThe corresponding commands :<range>Srot [arg] and :Srotv [arg] open the result in a new window.\r\nAny comments are welcome.\r\n\r\n","4":"This script enables Vim to do things like rotate text (counter) clockwise (l\/r), put it upside down (u),\r\nexchange lines and columns (x), reorder it from right to left (h) or from bottom to top (v).\r\nThe command :<range>Rot [arg] allows a range in which this will be done.\r\nIf no range is specified the current line is taken. The optional argument (in parenthesis) specifies which\r\noperation is performed. If none is given, lines and columns are exchanged.\r\nThe command :Rotv [arg] operates on the last visual area and is good for use in Visual mode.\r\nThe corresponding commands :<range>Srot [arg] and :Srotv [arg] open the result in a new window.\r\nAny comments are welcome.\r\n\r\n","install_details":"Put it in your plugin directory.\r\n\r\n","5":"Put it in your plugin directory.\r\n\r\n","first_name":"Jens","6":"Jens","last_name":"Paulus","7":"Paulus","releases":[{"0":"1186","vim_version":"6.0","1":"6.0","script_version":"1.6","2":"1.6","version_comment":"New version which fixes bad performance when operating on huge text files\r\n\r\n","3":"New version which fixes bad performance when operating on huge text files\r\n\r\n","package":"rotate.vim","4":"rotate.vim","src_id":"3856","5":"3856","creation_date":"1108162691","6":"1108162691"},{"0":"1186","vim_version":"6.0","1":"6.0","script_version":"1.2","2":"1.2","version_comment":"A slightly improved version\r\n\r\n","3":"A slightly improved version\r\n\r\n","package":"rotate.vim","4":"rotate.vim","src_id":"3808","5":"3808","creation_date":"1106931734","6":"1106931734"},{"0":"1186","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"rotate.vim","4":"rotate.vim","src_id":"3779","5":"3779","creation_date":"1105972327","6":"1105972327"}]},"1185":{"script_id":"1185","0":"1185","script_name":"turbo.vim","1":"turbo.vim","script_type":"color scheme","2":"color scheme","summary":"Color scheme based on Turbo Pascal and Turbo C++","3":"Color scheme based on Turbo Pascal and Turbo C++","description":"I missed the colors of Borland's Turbo Pascal and Turbo C++ for DOS, so I tried to duplicate them as well as I could remember them.","4":"I missed the colors of Borland's Turbo Pascal and Turbo C++ for DOS, so I tried to duplicate them as well as I could remember them.","install_details":"","5":"","first_name":"Bryant","6":"Bryant","last_name":"Casteel","7":"Casteel","releases":[{"0":"1185","vim_version":"7.0","1":"7.0","script_version":"1.21","2":"1.21","version_comment":"Fixed a small error for the command line color scheme","3":"Fixed a small error for the command line color scheme","package":"turbo.vim","4":"turbo.vim","src_id":"7305","5":"7305","creation_date":"1182945407","6":"1182945407"},{"0":"1185","vim_version":"6.0","1":"6.0","script_version":"1.2","2":"1.2","version_comment":"I changed this a little so that it would work better from the command line whether the background color is light or dark.","3":"I changed this a little so that it would work better from the command line whether the background color is light or dark.","package":"turbo.vim","4":"turbo.vim","src_id":"7291","5":"7291","creation_date":"1182535611","6":"1182535611"},{"0":"1185","vim_version":"6.0","1":"6.0","script_version":"1.1","2":"1.1","version_comment":"I realized that the old version has Windows newline characters and doesn't work when loaded in Unix environments. This fixes it to use only the Unix character. (It still works fine in Windows.)","3":"I realized that the old version has Windows newline characters and doesn't work when loaded in Unix environments. This fixes it to use only the Unix character. (It still works fine in Windows.)","package":"turbo.vim","4":"turbo.vim","src_id":"6632","5":"6632","creation_date":"1169223214","6":"1169223214"},{"0":"1185","vim_version":"6.0","1":"6.0","script_version":"1","2":"1","version_comment":"Initial upload","3":"Initial upload","package":"turbo.vim","4":"turbo.vim","src_id":"3778","5":"3778","creation_date":"1105965297","6":"1105965297"}]},"1184":{"script_id":"1184","0":"1184","script_name":"uniface.vim","1":"uniface.vim","script_type":"syntax","2":"syntax","summary":"Uniface Proc language syntax file","3":"Uniface Proc language syntax file","description":"This is a syntax file for the Uniface 7 Proc language.\r\nUniface is a 4GL of compuware. ","4":"This is a syntax file for the Uniface 7 Proc language.\r\nUniface is a 4GL of compuware. ","install_details":"Just copy the uniface.vim into the syntax directory and add this line to filetypes.vim:\r\n\r\n\" Uniface\r\nau BufNewFile,BufRead *.proc\t\t\tsetf uniface\r\n\r\nNormaly uniface doesn't work with files, so there is no file extension. I chose .proc.","5":"Just copy the uniface.vim into the syntax directory and add this line to filetypes.vim:\r\n\r\n\" Uniface\r\nau BufNewFile,BufRead *.proc\t\t\tsetf uniface\r\n\r\nNormaly uniface doesn't work with files, so there is no file extension. I chose .proc.","first_name":"Peter","6":"Peter","last_name":"Storch","7":"Storch","releases":[{"0":"1184","vim_version":"6.0","1":"6.0","script_version":"1.1","2":"1.1","version_comment":"Some Keywords were missing.","3":"Some Keywords were missing.","package":"uniface.vim","4":"uniface.vim","src_id":"3858","5":"3858","creation_date":"1108210818","6":"1108210818"},{"0":"1184","vim_version":"6.0","1":"6.0","script_version":"1","2":"1","version_comment":"Initial upload","3":"Initial upload","package":"uniface.vim","4":"uniface.vim","src_id":"3777","5":"3777","creation_date":"1105961077","6":"1105961077"}]},"1183":{"script_id":"1183","0":"1183","script_name":"MultipleSearch2.vim","1":"MultipleSearch2.vim","script_type":"utility","2":"utility","summary":"Improve Multiple search","3":"Improve Multiple search","description":"Improved version allow you to navigate your searches, to initialise search with a void search and continue with lat vim search.\r\n\r\nMultipleSearch allows you to have the results of multiple searches displayed \r\non the screen at the same time.  Each search highlights its results in a \r\ndifferent color, and all searches are displayed at once.  After the maximum \r\nnumber of colors is used, the script starts over with the first color. \r\n\r\nThe command syntax is: \r\n:Search <pattern1> \r\nwhich will highlight all occurrences of <pattern1> in the current buffer.  A \r\nsubsequent :Search <pattern2> will highlight all occurrences of <pattern2> \r\nin the current buffer, retaining the highlighting of <pattern1> as well. \r\n<pattern1> and <pattern2> are any search pattern like you would use in a \r\nnormal \/<pattern> search. \r\n\r\nThe :Search command honors Vim\\'s \\'ignorecase\\' and \\'smartcase\\' settings for \r\nits own search.  You can use the \\\\c and \\\\C flags in the search pattern to \r\nforce case matching no matter the setting of \\'ignorecase\\' and \\'smartcase\\'. \r\n\r\nThe :SearchBuffers command works just like :Search, but the search occurs in all currently listed buffers (i.e., appear in the output of :ls).  The match in all buffers will have the same color.  This is different than  :bufdo Search <pattern> because in that case, each buffer will highlight the match in a different color.  Thanks to Jeff Mei for the suggestion! \r\n\r\nTo clear the highlighting, issue the command \r\n:SearchReset (for the current buffer) or :SearchBuffersReset (for all buffers). \r\n\r\nYou can specify the maximum number of different colors to use by setting the \r\ng:MultipleSearchMaxColors variable in your .vimrc.  The default setting is \r\nfour, but the script should handle as much as your terminal \/ GUI can \r\ndisplay.  The g:MultipleSearchColorSequence variable lets you list the \r\ncolors you want displayed, and in what order.  To make the text more \r\nreadable, you can set the g:MultipleSearchTextColorSequence variable to a \r\nlist of colors for the text, each position corresponding to the color in the \r\nsame position in g:MultipleSearchColorSequence. \r\n\r\nIf you change one of the preference variables, you can issue the command \r\n:SearchReinit \r\nto update the script with your new selections. \r\n  \r\ninstall details \r\nCopy the MultipleSearch.vim file into your local plugins directory, restart (g)vim, and you are ready to go. \r\n  \r\n\r\n ","4":"Improved version allow you to navigate your searches, to initialise search with a void search and continue with lat vim search.\r\n\r\nMultipleSearch allows you to have the results of multiple searches displayed \r\non the screen at the same time.  Each search highlights its results in a \r\ndifferent color, and all searches are displayed at once.  After the maximum \r\nnumber of colors is used, the script starts over with the first color. \r\n\r\nThe command syntax is: \r\n:Search <pattern1> \r\nwhich will highlight all occurrences of <pattern1> in the current buffer.  A \r\nsubsequent :Search <pattern2> will highlight all occurrences of <pattern2> \r\nin the current buffer, retaining the highlighting of <pattern1> as well. \r\n<pattern1> and <pattern2> are any search pattern like you would use in a \r\nnormal \/<pattern> search. \r\n\r\nThe :Search command honors Vim\\'s \\'ignorecase\\' and \\'smartcase\\' settings for \r\nits own search.  You can use the \\\\c and \\\\C flags in the search pattern to \r\nforce case matching no matter the setting of \\'ignorecase\\' and \\'smartcase\\'. \r\n\r\nThe :SearchBuffers command works just like :Search, but the search occurs in all currently listed buffers (i.e., appear in the output of :ls).  The match in all buffers will have the same color.  This is different than  :bufdo Search <pattern> because in that case, each buffer will highlight the match in a different color.  Thanks to Jeff Mei for the suggestion! \r\n\r\nTo clear the highlighting, issue the command \r\n:SearchReset (for the current buffer) or :SearchBuffersReset (for all buffers). \r\n\r\nYou can specify the maximum number of different colors to use by setting the \r\ng:MultipleSearchMaxColors variable in your .vimrc.  The default setting is \r\nfour, but the script should handle as much as your terminal \/ GUI can \r\ndisplay.  The g:MultipleSearchColorSequence variable lets you list the \r\ncolors you want displayed, and in what order.  To make the text more \r\nreadable, you can set the g:MultipleSearchTextColorSequence variable to a \r\nlist of colors for the text, each position corresponding to the color in the \r\nsame position in g:MultipleSearchColorSequence. \r\n\r\nIf you change one of the preference variables, you can issue the command \r\n:SearchReinit \r\nto update the script with your new selections. \r\n  \r\ninstall details \r\nCopy the MultipleSearch.vim file into your local plugins directory, restart (g)vim, and you are ready to go. \r\n  \r\n\r\n ","install_details":"put in plugin","5":"put in plugin","first_name":"belarbi","6":"belarbi","last_name":"benamar","7":"benamar","releases":[{"0":"1183","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"MultipleSearch2.vim","4":"MultipleSearch2.vim","src_id":"3775","5":"3775","creation_date":"1105952113","6":"1105952113"}]},"1182":{"script_id":"1182","0":"1182","script_name":"tesei.vim","1":"tesei.vim","script_type":"syntax","2":"syntax","summary":"syntax higlighting for Tesei (KP1878BM1 1878ВМ1) assembler","3":"syntax higlighting for Tesei (KP1878BM1 1878ВМ1) assembler","description":"This is syntax higlighting script for\r\nTesei (KP1878BM1 1878ВМ1)\r\nmicrocontrollers (produced by Angstrem)  assembler.","4":"This is syntax higlighting script for\r\nTesei (KP1878BM1 1878ВМ1)\r\nmicrocontrollers (produced by Angstrem)  assembler.","install_details":"copy this file to your ~\/.vim\/syntax catalogue.","5":"copy this file to your ~\/.vim\/syntax catalogue.","first_name":"Kirill","6":"Kirill","last_name":"Frolov","7":"Frolov","releases":[{"0":"1182","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"tesei.vim","4":"tesei.vim","src_id":"3772","5":"3772","creation_date":"1105773213","6":"1105773213"}]},"1181":{"script_id":"1181","0":"1181","script_name":"avr.vim","1":"avr.vim","script_type":"syntax","2":"syntax","summary":"syntax higlighting for Atmel AVR assembler","3":"syntax higlighting for Atmel AVR assembler","description":"This is syntax higlighting script for\r\nAtmel AVR assembler.","4":"This is syntax higlighting script for\r\nAtmel AVR assembler.","install_details":"copy this file to your ~\/.vim\/syntax catalogue.","5":"copy this file to your ~\/.vim\/syntax catalogue.","first_name":"Kirill","6":"Kirill","last_name":"Frolov","7":"Frolov","releases":[{"0":"1181","vim_version":"6.0","1":"6.0","script_version":"0.2","2":"0.2","version_comment":"added keywords for avra assembler, more IO register names added too","3":"added keywords for avra assembler, more IO register names added too","package":"avr.vim","4":"avr.vim","src_id":"3773","5":"3773","creation_date":"1105781142","6":"1105781142"},{"0":"1181","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"avr.vim","4":"avr.vim","src_id":"3771","5":"3771","creation_date":"1105773035","6":"1105773035"}]},"1180":{"script_id":"1180","0":"1180","script_name":"fileaccess","1":"fileaccess","script_type":"utility","2":"utility","summary":"access time based simple file explorer for vim","3":"access time based simple file explorer for vim","description":"At first, this script looks like mruex.vim script. Please choose favarite one among them.\r\n\r\nWhen we work, we access many files, and in general they are in different directories. Thus we have to type related( or absolute ) path or move to the directory which includes the file which we want to access. \r\n\r\nThis script help you to omit to type such a tiresome work. This script keeps file name and its absolute directory information which you accessed, and you can briefly access the file which you read or wrote previously.","4":"At first, this script looks like mruex.vim script. Please choose favarite one among them.\r\n\r\nWhen we work, we access many files, and in general they are in different directories. Thus we have to type related( or absolute ) path or move to the directory which includes the file which we want to access. \r\n\r\nThis script help you to omit to type such a tiresome work. This script keeps file name and its absolute directory information which you accessed, and you can briefly access the file which you read or wrote previously.","install_details":"1 - put in your plugin directory, and access some files.\r\n2 - type :FileAcess\r\n3 - window will change and you can see some files which you accessed in\r\n    former times. And move cursor on a line which includes the file name\r\n    you want to open again and return.\r\n    If you want to keep file list window, put 'o' in stead of return.","5":"1 - put in your plugin directory, and access some files.\r\n2 - type :FileAcess\r\n3 - window will change and you can see some files which you accessed in\r\n    former times. And move cursor on a line which includes the file name\r\n    you want to open again and return.\r\n    If you want to keep file list window, put 'o' in stead of return.","first_name":"Masashi","6":"Masashi","last_name":"Watanabe","7":"Watanabe","releases":[{"0":"1180","vim_version":"6.0","1":"6.0","script_version":"0.8","2":"0.8","version_comment":"Initial upload","3":"Initial upload","package":"fileaccess.vim","4":"fileaccess.vim","src_id":"3770","5":"3770","creation_date":"1105740960","6":"1105740960"}]},"1179":{"script_id":"1179","0":"1179","script_name":"context_complete.vim","1":"context_complete.vim","script_type":"utility","2":"utility","summary":"Context sensitive word completion","3":"Context sensitive word completion","description":"The focus of this script is to provide context-sensitive word completion - taking advantage of the popular ctags utility and Vim's built-in perl features. \r\n\r\nSuppose you have an instance of an object (o), and you've typed:\r\n\r\no.set_\r\n\r\nWhile you are still in insert mode, press CTRL-J, and this script will then look up the first member of that object that starts with \"set_\" and complete it for you, like this:\r\n\r\no.set_range(integer max, integer min)\r\n\r\nIf this isn't the completion that you want, then press CTRL-J again for the next member that starts with \"set_\":\r\n\r\no.set_name(string name)\r\n\r\nand again for the next one:\r\n\r\no.set_value\r\n\r\nIf you've gone too far then you can go back with CTRL-K. After each completion you are left in insert mode - so you can just continue typing when you've found the one you want.\r\n\r\nThe object can also be replaced with a struct, class, 'this', or 'super'.\r\n\r\nCompletions can also be made after the open parentheses to complete the list of parameters:\r\n\r\no.set_range(<c-j>\r\n\r\nOr after the function:\r\n\r\no.get_name().compar<c-j>\r\n\r\nPressing CTRL-S will skip through the function parameters, visually selecting each in turn - useful for filling in the parameters after completing a function.","4":"The focus of this script is to provide context-sensitive word completion - taking advantage of the popular ctags utility and Vim's built-in perl features. \r\n\r\nSuppose you have an instance of an object (o), and you've typed:\r\n\r\no.set_\r\n\r\nWhile you are still in insert mode, press CTRL-J, and this script will then look up the first member of that object that starts with \"set_\" and complete it for you, like this:\r\n\r\no.set_range(integer max, integer min)\r\n\r\nIf this isn't the completion that you want, then press CTRL-J again for the next member that starts with \"set_\":\r\n\r\no.set_name(string name)\r\n\r\nand again for the next one:\r\n\r\no.set_value\r\n\r\nIf you've gone too far then you can go back with CTRL-K. After each completion you are left in insert mode - so you can just continue typing when you've found the one you want.\r\n\r\nThe object can also be replaced with a struct, class, 'this', or 'super'.\r\n\r\nCompletions can also be made after the open parentheses to complete the list of parameters:\r\n\r\no.set_range(<c-j>\r\n\r\nOr after the function:\r\n\r\no.get_name().compar<c-j>\r\n\r\nPressing CTRL-S will skip through the function parameters, visually selecting each in turn - useful for filling in the parameters after completing a function.","install_details":"Unpack the tar file into ~\/.vim. Then from any vim window type :helptags ~\/.vim\/doc. You can read the installation details at :help context_complete-setup","5":"Unpack the tar file into ~\/.vim. Then from any vim window type :helptags ~\/.vim\/doc. You can read the installation details at :help context_complete-setup","first_name":"David","6":"David","last_name":"Larson","7":"Larson","releases":[{"0":"1179","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Major upgrade.\r\n- context completion continues after a function (var.getObject().<c-j>)\r\n- search pattern and keywords are configurable\r\n- added a new mapping to highlight parameter items in turn\r\n- added a tag cache file for mega-fast searching.\r\n- *much* more.","3":"Major upgrade.\r\n- context completion continues after a function (var.getObject().<c-j>)\r\n- search pattern and keywords are configurable\r\n- added a new mapping to highlight parameter items in turn\r\n- added a tag cache file for mega-fast searching.\r\n- *much* more.","package":"context_complete1.0.tar","4":"context_complete1.0.tar","src_id":"3960","5":"3960","creation_date":"1109930765","6":"1109930765"},{"0":"1179","vim_version":"6.0","1":"6.0","script_version":"0.5","2":"0.5","version_comment":"- completes 'this.<c-q>'\r\n- completes 'super.<c-q>'\r\n- object type guessing is smarter - limits tag choises to members of the current object.\r\n- more bug fixes and documentation.","3":"- completes 'this.<c-q>'\r\n- completes 'super.<c-q>'\r\n- object type guessing is smarter - limits tag choises to members of the current object.\r\n- more bug fixes and documentation.","package":"context_complete.tar","4":"context_complete.tar","src_id":"3848","5":"3848","creation_date":"1108035907","6":"1108035907"},{"0":"1179","vim_version":"6.0","1":"6.0","script_version":"0.4","2":"0.4","version_comment":"- implemented a basic understanding of class inheritance.\r\n- tag searching is now *much* faster - uses binary searching whenever possible.\r\n- function parameter completions are given when asked after \"(\". e.g.: util.do_suff(<c-q>\r\n- completion suggestions are now sorted.","3":"- implemented a basic understanding of class inheritance.\r\n- tag searching is now *much* faster - uses binary searching whenever possible.\r\n- function parameter completions are given when asked after \"(\". e.g.: util.do_suff(<c-q>\r\n- completion suggestions are now sorted.","package":"context_complete.tar","4":"context_complete.tar","src_id":"3818","5":"3818","creation_date":"1107164513","6":"1107164513"},{"0":"1179","vim_version":"6.0","1":"6.0","script_version":"0.3","2":"0.3","version_comment":"- static members are completed: i.e. ClassName::<c-q>\r\n- C structs are now understood and treated like classes\r\n- local variable definition detection is much better... it uses more of vim's built-in features. (yay!)\r\n- more bug fixes. Finding the definition of a local variable is much more solid.","3":"- static members are completed: i.e. ClassName::<c-q>\r\n- C structs are now understood and treated like classes\r\n- local variable definition detection is much better... it uses more of vim's built-in features. (yay!)\r\n- more bug fixes. Finding the definition of a local variable is much more solid.","package":"context_complete.vim","4":"context_complete.vim","src_id":"3792","5":"3792","creation_date":"1106586854","6":"1106586854"}]},"1178":{"script_id":"1178","0":"1178","script_name":"PVCS access","1":"PVCS access","script_type":"utility","2":"utility","summary":"Difference and browsing abilities for a PVCS archive.","3":"Difference and browsing abilities for a PVCS archive.","description":"Allows PVCS users to view differences by previous version, specified version, or between two versions in vdiff or gvim diff formats.\r\n\r\nAllows user to browse all archive versions of the current file.\r\n\r\nTested with version 6.0.10. Refer to your PVCS documentation for support.\r\n","4":"Allows PVCS users to view differences by previous version, specified version, or between two versions in vdiff or gvim diff formats.\r\n\r\nAllows user to browse all archive versions of the current file.\r\n\r\nTested with version 6.0.10. Refer to your PVCS documentation for support.\r\n","install_details":"Place in your script directory (usually vimfiles) and launch from within vim.\r\n\r\nModify to match your environment before usage.","5":"Place in your script directory (usually vimfiles) and launch from within vim.\r\n\r\nModify to match your environment before usage.","first_name":"Lee","6":"Lee","last_name":"Riemenschneider","7":"Riemenschneider","releases":[{"0":"1178","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"pvcs.vim","4":"pvcs.vim","src_id":"3768","5":"3768","creation_date":"1105687021","6":"1105687021"}]},"1177":{"script_id":"1177","0":"1177","script_name":"OAL Syntax","1":"OAL Syntax","script_type":"syntax","2":"syntax","summary":"Syntax and indenting for the BridgePoint OAL","3":"Syntax and indenting for the BridgePoint OAL","description":"Provides filetype, syntax, and indenting for OAL (Object Action Language) files. OAL is used with the BridgePoint UML modeling tool available from Mentor Graphics.\r\nThis also supports archetype files for BridgePoint, as they use much of the same syntax as OAL.\r\n\r\nFiles named *.oal and *.arc will be automatically recognized.\r\n","4":"Provides filetype, syntax, and indenting for OAL (Object Action Language) files. OAL is used with the BridgePoint UML modeling tool available from Mentor Graphics.\r\nThis also supports archetype files for BridgePoint, as they use much of the same syntax as OAL.\r\n\r\nFiles named *.oal and *.arc will be automatically recognized.\r\n","install_details":"unzip to runtimepath","5":"unzip to runtimepath","first_name":"Lee","6":"Lee","last_name":"Riemenschneider","7":"Riemenschneider","releases":[{"0":"1177","vim_version":"6.0","1":"6.0","script_version":"2.0","2":"2.0","version_comment":"Added support for archetype files.","3":"Added support for archetype files.","package":"oal_syntax.zip","4":"oal_syntax.zip","src_id":"22710","5":"22710","creation_date":"1418930064","6":"1418930064"},{"0":"1177","vim_version":"7.0","1":"7.0","script_version":"1.3","2":"1.3","version_comment":"Removed filetype.vim and replaced with ftdetect usage. Also got rid of vimfiles directory in archive.","3":"Removed filetype.vim and replaced with ftdetect usage. Also got rid of vimfiles directory in archive.","package":"oal_syntax.zip","4":"oal_syntax.zip","src_id":"22709","5":"22709","creation_date":"1418920187","6":"1418920187"},{"0":"1177","vim_version":"6.0","1":"6.0","script_version":"1.2","2":"1.2","version_comment":"Fixed error output of function redefinition on opening second OAL file in same window.","3":"Fixed error output of function redefinition on opening second OAL file in same window.","package":"oal_syntax.zip","4":"oal_syntax.zip","src_id":"3767","5":"3767","creation_date":"1105682769","6":"1105682769"},{"0":"1177","vim_version":"6.0","1":"6.0","script_version":"1.1","2":"1.1","version_comment":"Previous version had a bug in the indent script.","3":"Previous version had a bug in the indent script.","package":"oal_syntax.zip","4":"oal_syntax.zip","src_id":"3766","5":"3766","creation_date":"1105618941","6":"1105618941"},{"0":"1177","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"oal_syntax.zip","4":"oal_syntax.zip","src_id":"3756","5":"3756","creation_date":"1105357391","6":"1105357391"}]},"1176":{"script_id":"1176","0":"1176","script_name":"oceanlight","1":"oceanlight","script_type":"color scheme","2":"color scheme","summary":"Pale blue and green winter colors","3":"Pale blue and green winter colors","description":"A light pale blue and green colorscheme originally based on oceandeep by Tom Regner (vimscript #368), intended to be easy on the eyes and not kill you with contrast. GUI only.","4":"A light pale blue and green colorscheme originally based on oceandeep by Tom Regner (vimscript #368), intended to be easy on the eyes and not kill you with contrast. GUI only.","install_details":"Copy to your vim colors directory as usual.","5":"Copy to your vim colors directory as usual.","first_name":"H\u00c3\u00a5kan","6":"H\u00c3\u00a5kan","last_name":"Wikstr\u00c3\u00b6m","7":"Wikstr\u00c3\u00b6m","releases":[{"0":"1176","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"oceanlight.vim","4":"oceanlight.vim","src_id":"3753","5":"3753","creation_date":"1105221172","6":"1105221172"}]},"1175":{"script_id":"1175","0":"1175","script_name":"C# Syntax","1":"C# Syntax","script_type":"syntax","2":"syntax","summary":"Syntax for C# 2.0 (keywords: C-sharp, C sharp, CSharp)","3":"Syntax for C# 2.0 (keywords: C-sharp, C sharp, CSharp)","description":"Syntax for C# 2.0.\r\n\r\n\r\nTODO:\r\n\r\n- Folding\r\n- Xml tag in \/** *\/","4":"Syntax for C# 2.0.\r\n\r\n\r\nTODO:\r\n\r\n- Folding\r\n- Xml tag in \/** *\/","install_details":"just override your original syntax\/cs.vim with this one.","5":"just override your original syntax\/cs.vim with this one.","first_name":"Aquila","6":"Aquila","last_name":"Deus","7":"Deus","releases":[{"0":"1175","vim_version":"6.0","1":"6.0","script_version":"0.9","2":"0.9","version_comment":"Initial upload","3":"Initial upload","package":"cs.vim","4":"cs.vim","src_id":"3752","5":"3752","creation_date":"1105148989","6":"1105148989"}]},"1174":{"script_id":"1174","0":"1174","script_name":"Rhythmbox Control Plugin","1":"Rhythmbox Control Plugin","script_type":"utility","2":"utility","summary":"This plugin can control Rhythmbox in VIM","3":"This plugin can control Rhythmbox in VIM","description":"This plugin makes you be able to control Rhythmbox in VIM.\r\n\r\nYou can change default Key-Map in rhythmbox.vim.\r\n\r\ndefault key\r\n\r\nF7 = current song\r\nShift + F7 = play\/stop\r\nF8 = Previous Song\r\nF9 = Next Song","4":"This plugin makes you be able to control Rhythmbox in VIM.\r\n\r\nYou can change default Key-Map in rhythmbox.vim.\r\n\r\ndefault key\r\n\r\nF7 = current song\r\nShift + F7 = play\/stop\r\nF8 = Previous Song\r\nF9 = Next Song","install_details":"","5":"","first_name":"JinHyung","6":"JinHyung","last_name":"Park","7":"Park","releases":[{"0":"1174","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"rhythmbox-vim.tgz","4":"rhythmbox-vim.tgz","src_id":"3750","5":"3750","creation_date":"1105127092","6":"1105127092"}]},"1173":{"script_id":"1173","0":"1173","script_name":"tComment","1":"tComment","script_type":"utility","2":"utility","summary":"An extensible & universal comment plugin that also handles embedded filetypes","3":"An extensible & universal comment plugin that also handles embedded filetypes","description":":TComment works like a toggle, i.e., it will comment out text that \r\ncontains uncommented lines, and it will uncomment already \r\ncommented text (i.e. text that contains no uncommented lines).\r\n\r\nIf the file-type is properly defined, :TComment will figure out which \r\ncomment string to use based on the values of &commentstring or &comments. \r\nFor some filetypes, the comment definition is explicitly defined. You can \r\n|tcomment#DefineType()| to add your own definitions.\r\n\r\nTComment knows how to deal with embedded code of a different filetype \r\nthan the main filetype, e.g., ruby\/python\/perl regions in vim scripts, HTML or \r\nJavaScript in php code etc.\r\n\r\nAs operator (the prefix can be customized via g:tcommentMapLeaderOp1 \r\nand g:tcommentMapLeaderOp2):\r\n\r\n    gc{motion}   :: Toggle comments (for small comments within one line \r\n                    the &filetype_inline style will be used, if \r\n                    defined)\r\n    gcc          :: Toggle comment for the current line\r\n    gC{motion}   :: Comment region\r\n    gCc          :: Comment the current line\r\n\r\nPrimary key maps:\r\n\r\n    <c-_><c-_>   :: :TComment\r\n    <c-_><space> :: :TComment <QUERY COMMENT-BEGIN ?COMMENT-END>\r\n    <c-_>b       :: :TCommentBlock\r\n    <c-_>a       :: :TCommentAs <QUERY COMMENT TYPE>\r\n    <c-_>n       :: :TCommentAs &filetype <QUERY COUNT>\r\n    <c-_>s       :: :TCommentAs &filetype_<QUERY COMMENT SUBTYPE>\r\n    <c-_>i       :: :TCommentInline\r\n    <c-_>r       :: :TCommentRight\r\n    <c-_>p       :: Comment the current inner paragraph\r\n\r\nThere is also a secondary set of key maps with <Leader>_ as leader (more \r\npreferable on terminals).\r\n\r\nThe full documentation is available here:\r\nhttp:\/\/github.com\/tomtom\/tcomment_vim\/blob\/master\/doc\/tcomment.txt\r\n\r\nDemo:\r\nhttp:\/\/vimsomnia.blogspot.com\/2010\/11\/tcomment-vim-plugin.html\r\n\r\nAlso available via git\r\nhttp:\/\/github.com\/tomtom\/tcomment_vim","4":":TComment works like a toggle, i.e., it will comment out text that \r\ncontains uncommented lines, and it will uncomment already \r\ncommented text (i.e. text that contains no uncommented lines).\r\n\r\nIf the file-type is properly defined, :TComment will figure out which \r\ncomment string to use based on the values of &commentstring or &comments. \r\nFor some filetypes, the comment definition is explicitly defined. You can \r\n|tcomment#DefineType()| to add your own definitions.\r\n\r\nTComment knows how to deal with embedded code of a different filetype \r\nthan the main filetype, e.g., ruby\/python\/perl regions in vim scripts, HTML or \r\nJavaScript in php code etc.\r\n\r\nAs operator (the prefix can be customized via g:tcommentMapLeaderOp1 \r\nand g:tcommentMapLeaderOp2):\r\n\r\n    gc{motion}   :: Toggle comments (for small comments within one line \r\n                    the &filetype_inline style will be used, if \r\n                    defined)\r\n    gcc          :: Toggle comment for the current line\r\n    gC{motion}   :: Comment region\r\n    gCc          :: Comment the current line\r\n\r\nPrimary key maps:\r\n\r\n    <c-_><c-_>   :: :TComment\r\n    <c-_><space> :: :TComment <QUERY COMMENT-BEGIN ?COMMENT-END>\r\n    <c-_>b       :: :TCommentBlock\r\n    <c-_>a       :: :TCommentAs <QUERY COMMENT TYPE>\r\n    <c-_>n       :: :TCommentAs &filetype <QUERY COUNT>\r\n    <c-_>s       :: :TCommentAs &filetype_<QUERY COMMENT SUBTYPE>\r\n    <c-_>i       :: :TCommentInline\r\n    <c-_>r       :: :TCommentRight\r\n    <c-_>p       :: Comment the current inner paragraph\r\n\r\nThere is also a secondary set of key maps with <Leader>_ as leader (more \r\npreferable on terminals).\r\n\r\nThe full documentation is available here:\r\nhttp:\/\/github.com\/tomtom\/tcomment_vim\/blob\/master\/doc\/tcomment.txt\r\n\r\nDemo:\r\nhttp:\/\/vimsomnia.blogspot.com\/2010\/11\/tcomment-vim-plugin.html\r\n\r\nAlso available via git\r\nhttp:\/\/github.com\/tomtom\/tcomment_vim","install_details":"Edit the vba file and type:\r\n\r\n    :so %\r\n\r\nSee :help vimball for details. If you use vim 7.0, you may need to \r\nupdate your vimball installation first.","5":"Edit the vba file and type:\r\n\r\n    :so %\r\n\r\nSee :help vimball for details. If you use vim 7.0, you may need to \r\nupdate your vimball installation first.","first_name":"Tom","6":"Tom","last_name":"Link","7":"Link","releases":[{"0":"1173","vim_version":"7.0","1":"7.0","script_version":"4.00","2":"4.00","version_comment":"- FIX #190: use len() is str(display)width() is not defined\n- Fix comments in Laravel blade filetype\n- Merge pull request #193 from jaguadoromero\/blade_comments_fix\n- Add rust_inline\n- Merge pull request #194 from alanjcfs\/add-rust-inline\n- FIX #197: Rmd support\n- FIX #197: rmd defaults to markdown\n- Add # as comment sign for qmake project files\n- Merge pull request #200 from t-b\/add-qmake\n- ultralight refactoring\n- Do not call setline() if it would not change it\n- Use CamelCase for function names etc.\n- Merge pull request #207 from blueyed\/setline\n- CLOSE #208: Add support for Cabal files (thanks to mn720)\n- FIX #202: Make it easier to customize C-style line comments via g:tcomment#commentstring_c\n- FIX #201: tcommentModeExtra: Use \"j^\" instead of \"l^\"; NEW >|\n- Further refactoring\n- Bump major version number due to possibly incompatible changes\n- More refactoring (not backward-compatible)\n- FIX #210: Move `call tcomment#deprecated#Check()` to autoload\/tcomment.vim\n- Add support for cdl files\n- Merge pull request #211 from t-b\/feature\/add_cdl_support\n- FIX #212: s\/g:tcomment_textoject_inlinecomment\/g:tcomment_textobject_inlinecomment\/\n- Run the deprecation checks eagerly (closes #215, closes #216)\n- Merge pull request #217 from chocolateboy\/eager-faster-deprecation\n- FIX #210: Performance improvement for tcomment#deprecated#Check()\n- FIX #218: Missing quote\n- FIX #214: Guess filetype in perl files\n- FIX #219: vim 7.4 compatibility\n- FIX #191: Properly escape backslashes (for forth, nroff etc.); explicitly support forth\n- FIX #213: Make whitespace optional\n- EXPERIMENTAL: g:tcomment#filetype#guess defaults to 1\n- FIX #213: Make whitespace conditional only at the end of a line\n- FIX #220: don't escape backslashes in commentstring_rx\n- In block mode: make sure to comment empty lines\n- Block comment: Handle whitespace < prefix\n- tcomment#filetype#GetAlt: s\/[.]\/_\/g in filetype names\n- g:tcomment#filetype#map_user, g:tcomment#filetype#syntax_map_user: Make it easier to customize the respective parameters\n- tcomment#filetype#GetAlt(): cdef.guess > g:tcomment#filetype#guess_{filetype} > g:tcomment#filetype#guess\n- FIX #222, FIX #224: g:tcomment#filetype#guess defaults to 0 again\n- FIX #225: Process g:tcomment_types after autoload\/tcomment\/types\/*.vim files\n- Add type#Define for pug\n- Merge pull request #226 from bootleq\/pug\n- FIX #228: guard_rx: Use replacements only on certain lines\n- FIX #229: Re-enable some filetype-specific guess params\n- Support for the terraform filetype\n- Merge pull request #230 from Hinidu\/patch-1\n- Add Meson build system defenition\n- Merge pull request #231 from rkuchumov\/master\n- Possibly FIX #232\n- FIX #232: Try synID() with tran = 1 and 0\n- ++Support for tsx, jsx\n- NEW tcomment#DebugInfo()\n- NEW tcomment#debug#CollectInfo()\n- FIX #186 Support xml tags in jsx files\n- FIX #159 use js-style comments for xmlAttrib; tcomment#filetype#Guess(): one-off error\n- ft: jinja: there are no comment blocks\n- FIX tcomment#syntax#GetSyntaxName: Make sure filetype key is in cdef\n- Support julia and stata\n- tcomment#syntax#GetSyntaxName(): Make sure cdef includes filetype field\n- Support for julia\n- Merge pull request #242 from PietroPate\/master\n- Merge pull request #240 from blueyed\/jinja-comments\n- Support for julia block comments\n- stata block comments\n- FIX #245: Missing comma\n- Merge pull request #243 from PietroPate\/master\n- Add support for igorpro files\n- Add cucumber comment definition\n- Merge pull request #247 from pylipp\/feature\/support-cucumber\n- FIX #248 handle jsx special case for uncommenting\n- Merge pull request #246 from t-b\/add-igor-pro\n- tcomment#syntax#GetSyntaxName(): Make sure the rules in g:tcomment#syntax#substitute are applied before those in g:tcomment#syntax#substitute_by_filetype\n- add taskrc filetype\n- Merge pull request #249 from dsifford\/dsifford-add-taskrc-type\n- types\/default.vim: fasm filetype\n- Merge pull request #251 from dsirov\/add-filetype-fasm\n- add FSharp comment type\n- Merge pull request #252 from josselinauguste\/master\n- Add javascriptreact\/typescriptreact filetypes\n- Add support for bibtex files\n- Merge pull request #259 from t-b\/add-bibtex\n- Add Maude filetype\n- Add support for go.mod\n- Merge pull request #262 from josa42\/add-go-mod\n- Merge pull request #261 from magnusmb\/master\n- Merge pull request #256 from Chris-Slade\/master\n- Support for choose: Conditionally select a comment definition from a list of candidates (fixes https:\/\/github.com\/tomtom\/tcomment_vim\/commit\/0f94e969a14a0cd664ca67de38b640eaf54583ad?email_token=AAAJR5ACHF5PPVOR2JSULJDRD6UP3A5CNFSM4KF5DZ62YY3PNVWWK3TUL52HS4DFVVBW63LNNF2EG33NNVSW45FKMNXW23LFNZ2F62LEZYBDV5IA)\n- FIX bib commentdef (use `if` condition proposed by enno)\n- Add support for Agda files\n- FIX #265 NEW g:tcomment_map_modifier, g:tcomment_opmap_modifier: Configure use of <silent> etc.\n- Merge pull request #264 from akiomik\/patch-1\n- Add qml inline comment definition\n- Merge pull request #267 from pylipp\/patch-1\n- FIX #269 Support for cuda\n- support Swift\n- Support dot\n- Add alternative version of typescript\n- Merge pull request #271 from bradleymackey\/master\n- Merge pull request #273 from amadeus\/fix\/typescript-alt\n- Merge pull request #272 from tamago324\/support-dot\n- Add support for Snakemake files\n- Merge pull request #275 from mnsmar\/patch-1\n- adding sbt filetype\n- Merge pull request #276 from vito-c\/vito\n- Add support for spss\n- tcomment#GuessCommentType(): Enrich return value\n- Support Vim9 script and functions\n- Merge pull request #278 from itchyny\/support-vim9-script\n- Add Stylus support\n- Merge pull request #281 from herrbischoff\/patch-1\n- C-style comments: Support for \/\/\/ etc. FIXES #282\n- Restrict use of \/\/\/ to the rust filetype FIXES #282\n- Add support for bindzone and named type files\n- Merge pull request #286 from alteriks\/bind_named\n- Fix function call\n- Merge pull request #287 from aca\/master\n- XML style comments: don't escape \"-\" but \"<!--\" and \"-->\" FIX #288\n- Add nix_inline type\n- Merge pull request #293 from SuperSandro2000\/patch-1\n- Add support for Svelte by mapping to HTML\n- Merge pull request #296 from trygveaa\/add-svelte\n- Support for custom TCommentGetCommentstring() function FIXES #284\nSHA256 checksum: 6a3f85cfb3506ebff3872ffb6812d74086dbc290ea86e74dac7205a925caa9b5","3":"- FIX #190: use len() is str(display)width() is not defined\n- Fix comments in Laravel blade filetype\n- Merge pull request #193 from jaguadoromero\/blade_comments_fix\n- Add rust_inline\n- Merge pull request #194 from alanjcfs\/add-rust-inline\n- FIX #197: Rmd support\n- FIX #197: rmd defaults to markdown\n- Add # as comment sign for qmake project files\n- Merge pull request #200 from t-b\/add-qmake\n- ultralight refactoring\n- Do not call setline() if it would not change it\n- Use CamelCase for function names etc.\n- Merge pull request #207 from blueyed\/setline\n- CLOSE #208: Add support for Cabal files (thanks to mn720)\n- FIX #202: Make it easier to customize C-style line comments via g:tcomment#commentstring_c\n- FIX #201: tcommentModeExtra: Use \"j^\" instead of \"l^\"; NEW >|\n- Further refactoring\n- Bump major version number due to possibly incompatible changes\n- More refactoring (not backward-compatible)\n- FIX #210: Move `call tcomment#deprecated#Check()` to autoload\/tcomment.vim\n- Add support for cdl files\n- Merge pull request #211 from t-b\/feature\/add_cdl_support\n- FIX #212: s\/g:tcomment_textoject_inlinecomment\/g:tcomment_textobject_inlinecomment\/\n- Run the deprecation checks eagerly (closes #215, closes #216)\n- Merge pull request #217 from chocolateboy\/eager-faster-deprecation\n- FIX #210: Performance improvement for tcomment#deprecated#Check()\n- FIX #218: Missing quote\n- FIX #214: Guess filetype in perl files\n- FIX #219: vim 7.4 compatibility\n- FIX #191: Properly escape backslashes (for forth, nroff etc.); explicitly support forth\n- FIX #213: Make whitespace optional\n- EXPERIMENTAL: g:tcomment#filetype#guess defaults to 1\n- FIX #213: Make whitespace conditional only at the end of a line\n- FIX #220: don't escape backslashes in commentstring_rx\n- In block mode: make sure to comment empty lines\n- Block comment: Handle whitespace < prefix\n- tcomment#filetype#GetAlt: s\/[.]\/_\/g in filetype names\n- g:tcomment#filetype#map_user, g:tcomment#filetype#syntax_map_user: Make it easier to customize the respective parameters\n- tcomment#filetype#GetAlt(): cdef.guess > g:tcomment#filetype#guess_{filetype} > g:tcomment#filetype#guess\n- FIX #222, FIX #224: g:tcomment#filetype#guess defaults to 0 again\n- FIX #225: Process g:tcomment_types after autoload\/tcomment\/types\/*.vim files\n- Add type#Define for pug\n- Merge pull request #226 from bootleq\/pug\n- FIX #228: guard_rx: Use replacements only on certain lines\n- FIX #229: Re-enable some filetype-specific guess params\n- Support for the terraform filetype\n- Merge pull request #230 from Hinidu\/patch-1\n- Add Meson build system defenition\n- Merge pull request #231 from rkuchumov\/master\n- Possibly FIX #232\n- FIX #232: Try synID() with tran = 1 and 0\n- ++Support for tsx, jsx\n- NEW tcomment#DebugInfo()\n- NEW tcomment#debug#CollectInfo()\n- FIX #186 Support xml tags in jsx files\n- FIX #159 use js-style comments for xmlAttrib; tcomment#filetype#Guess(): one-off error\n- ft: jinja: there are no comment blocks\n- FIX tcomment#syntax#GetSyntaxName: Make sure filetype key is in cdef\n- Support julia and stata\n- tcomment#syntax#GetSyntaxName(): Make sure cdef includes filetype field\n- Support for julia\n- Merge pull request #242 from PietroPate\/master\n- Merge pull request #240 from blueyed\/jinja-comments\n- Support for julia block comments\n- stata block comments\n- FIX #245: Missing comma\n- Merge pull request #243 from PietroPate\/master\n- Add support for igorpro files\n- Add cucumber comment definition\n- Merge pull request #247 from pylipp\/feature\/support-cucumber\n- FIX #248 handle jsx special case for uncommenting\n- Merge pull request #246 from t-b\/add-igor-pro\n- tcomment#syntax#GetSyntaxName(): Make sure the rules in g:tcomment#syntax#substitute are applied before those in g:tcomment#syntax#substitute_by_filetype\n- add taskrc filetype\n- Merge pull request #249 from dsifford\/dsifford-add-taskrc-type\n- types\/default.vim: fasm filetype\n- Merge pull request #251 from dsirov\/add-filetype-fasm\n- add FSharp comment type\n- Merge pull request #252 from josselinauguste\/master\n- Add javascriptreact\/typescriptreact filetypes\n- Add support for bibtex files\n- Merge pull request #259 from t-b\/add-bibtex\n- Add Maude filetype\n- Add support for go.mod\n- Merge pull request #262 from josa42\/add-go-mod\n- Merge pull request #261 from magnusmb\/master\n- Merge pull request #256 from Chris-Slade\/master\n- Support for choose: Conditionally select a comment definition from a list of candidates (fixes https:\/\/github.com\/tomtom\/tcomment_vim\/commit\/0f94e969a14a0cd664ca67de38b640eaf54583ad?email_token=AAAJR5ACHF5PPVOR2JSULJDRD6UP3A5CNFSM4KF5DZ62YY3PNVWWK3TUL52HS4DFVVBW63LNNF2EG33NNVSW45FKMNXW23LFNZ2F62LEZYBDV5IA)\n- FIX bib commentdef (use `if` condition proposed by enno)\n- Add support for Agda files\n- FIX #265 NEW g:tcomment_map_modifier, g:tcomment_opmap_modifier: Configure use of <silent> etc.\n- Merge pull request #264 from akiomik\/patch-1\n- Add qml inline comment definition\n- Merge pull request #267 from pylipp\/patch-1\n- FIX #269 Support for cuda\n- support Swift\n- Support dot\n- Add alternative version of typescript\n- Merge pull request #271 from bradleymackey\/master\n- Merge pull request #273 from amadeus\/fix\/typescript-alt\n- Merge pull request #272 from tamago324\/support-dot\n- Add support for Snakemake files\n- Merge pull request #275 from mnsmar\/patch-1\n- adding sbt filetype\n- Merge pull request #276 from vito-c\/vito\n- Add support for spss\n- tcomment#GuessCommentType(): Enrich return value\n- Support Vim9 script and functions\n- Merge pull request #278 from itchyny\/support-vim9-script\n- Add Stylus support\n- Merge pull request #281 from herrbischoff\/patch-1\n- C-style comments: Support for \/\/\/ etc. FIXES #282\n- Restrict use of \/\/\/ to the rust filetype FIXES #282\n- Add support for bindzone and named type files\n- Merge pull request #286 from alteriks\/bind_named\n- Fix function call\n- Merge pull request #287 from aca\/master\n- XML style comments: don't escape \"-\" but \"<!--\" and \"-->\" FIX #288\n- Add nix_inline type\n- Merge pull request #293 from SuperSandro2000\/patch-1\n- Add support for Svelte by mapping to HTML\n- Merge pull request #296 from trygveaa\/add-svelte\n- Support for custom TCommentGetCommentstring() function FIXES #284\nSHA256 checksum: 6a3f85cfb3506ebff3872ffb6812d74086dbc290ea86e74dac7205a925caa9b5","package":"tcomment.zip","4":"tcomment.zip","src_id":"28106","5":"28106","creation_date":"1658504346","6":"1658504346"},{"0":"1173","vim_version":"7.0","1":"7.0","script_version":"3.08","2":"3.08","version_comment":"- FIX #137: Prefer \/\/ for rust comments\n- FIX #138: Support for jinja filetype (see https:\/\/github.com\/Glench\/Vim-Jinja2-Syntax)\n- FIX #140: s:MapOp(): Don't evaluate registers to define op functions\n- s:MapOp: Remove count argument\n- support Tupfile comments\n- Merge pull request #141 from cfillion\/tup-comments\n- FIX #123: GuessFileType(): don't use indent(); properly handle tabs\n- GuessFileType(): Use strwidth() (FIX #144)\n- autoload: Add Makefile support\n- Merge pull request #146 from JIghtuse\/master\n- FIX #147: Add definition for robot file; re-enable col attribute (comment mode only)\n- FIX #148: Prefer \/\/ for java comments\n- Merge pull request #149 from phphong\/change-java-default\n- support commenting for the fish shell\n- Merge pull request #150 from philolo1\/support_fish\n- Add support for Facebook JSX\n- Merge pull request #151 from epeli\/jsx\n- CLOSE #152: postprocess_uncomment option\n- Support for markdown\n- Set markdown comment to <!--- ... --->\n- FIX #153: map tblgen -> cpp\n- runtime! autoload\/tcomment\/types\/*.vim\n- s:CommentDef(): If mixedindent is true, add 1 to cbeg only if not in inline comment-mode (experimental)\n- s:AddModeExtra(): Make sure not to include duplicates\n- Add Elm Comment Definition\n- Merge pull request #156 from bradurani\/patch-1\n- Properly handle MAJOR.MINOR sub-filetypes\n- FIX #160: Add license\n- [jq] adding jq support\n- Merge pull request #161 from vito-c\/vito\n- FIX #162: Ignore col option for inline comments\n- notlib stub\n- g:tcomment#filetype_map may match MAJ.MIN-style filetypes (FIX #162)\n- adding support for solidiy\n- merge\n- Merge pull request #163 from mhhf\/master\n- FIX #164: s:ProcessLine() returns a list when g:tcomment#blank_lines == 0\n- FIX #167: Define :Tlibtrace etc. also if an older version of tlib is installed\n- Support for octave, matlab block comments (Malte Neuss)\n- Fix blade block comment\n- markdown: use <!-- ... --> (FIX #171)\n- Merge pull request #170 from adriaanzon\/patch-1\n- add support for proto\n- Merge pull request #172 from timfeirg\/master\n- Detect PHP regions in Blade\n- Merge pull request #173 from adriaanzon\/blade\n- Add comment style for TypeScript (same as JavaScript)\n- Merge pull request #175 from johngrimes\/typescript\n- Support for cypher (CLOSE #178)\n- Support for the nix filetype\n- AppleScript\n- Merge pull request #181 from squm\/master\n- Merge pull request #180 from Hinidu\/patch-1\n- FIX #183: Remove the comment string only once\n- FIX #184: Special handling of &cms=% %s\n- <Plug>TCommen_gC map: force line-wise operation\n- Added nim.\n- Merge pull request #185 from rosshadden\/master\n- s:GuessVimOptionsCommentString(): Don't expect cms to be a proper format string\n- Add basic Vue support\n- Merge pull request #187 from adriaanzon\/vue\nSHA256 checksum: e38384a93873d91dd4ab811535d616aad14f0789d7e84e7da1a479357788bf1d","3":"- FIX #137: Prefer \/\/ for rust comments\n- FIX #138: Support for jinja filetype (see https:\/\/github.com\/Glench\/Vim-Jinja2-Syntax)\n- FIX #140: s:MapOp(): Don't evaluate registers to define op functions\n- s:MapOp: Remove count argument\n- support Tupfile comments\n- Merge pull request #141 from cfillion\/tup-comments\n- FIX #123: GuessFileType(): don't use indent(); properly handle tabs\n- GuessFileType(): Use strwidth() (FIX #144)\n- autoload: Add Makefile support\n- Merge pull request #146 from JIghtuse\/master\n- FIX #147: Add definition for robot file; re-enable col attribute (comment mode only)\n- FIX #148: Prefer \/\/ for java comments\n- Merge pull request #149 from phphong\/change-java-default\n- support commenting for the fish shell\n- Merge pull request #150 from philolo1\/support_fish\n- Add support for Facebook JSX\n- Merge pull request #151 from epeli\/jsx\n- CLOSE #152: postprocess_uncomment option\n- Support for markdown\n- Set markdown comment to <!--- ... --->\n- FIX #153: map tblgen -> cpp\n- runtime! autoload\/tcomment\/types\/*.vim\n- s:CommentDef(): If mixedindent is true, add 1 to cbeg only if not in inline comment-mode (experimental)\n- s:AddModeExtra(): Make sure not to include duplicates\n- Add Elm Comment Definition\n- Merge pull request #156 from bradurani\/patch-1\n- Properly handle MAJOR.MINOR sub-filetypes\n- FIX #160: Add license\n- [jq] adding jq support\n- Merge pull request #161 from vito-c\/vito\n- FIX #162: Ignore col option for inline comments\n- notlib stub\n- g:tcomment#filetype_map may match MAJ.MIN-style filetypes (FIX #162)\n- adding support for solidiy\n- merge\n- Merge pull request #163 from mhhf\/master\n- FIX #164: s:ProcessLine() returns a list when g:tcomment#blank_lines == 0\n- FIX #167: Define :Tlibtrace etc. also if an older version of tlib is installed\n- Support for octave, matlab block comments (Malte Neuss)\n- Fix blade block comment\n- markdown: use <!-- ... --> (FIX #171)\n- Merge pull request #170 from adriaanzon\/patch-1\n- add support for proto\n- Merge pull request #172 from timfeirg\/master\n- Detect PHP regions in Blade\n- Merge pull request #173 from adriaanzon\/blade\n- Add comment style for TypeScript (same as JavaScript)\n- Merge pull request #175 from johngrimes\/typescript\n- Support for cypher (CLOSE #178)\n- Support for the nix filetype\n- AppleScript\n- Merge pull request #181 from squm\/master\n- Merge pull request #180 from Hinidu\/patch-1\n- FIX #183: Remove the comment string only once\n- FIX #184: Special handling of &cms=% %s\n- <Plug>TCommen_gC map: force line-wise operation\n- Added nim.\n- Merge pull request #185 from rosshadden\/master\n- s:GuessVimOptionsCommentString(): Don't expect cms to be a proper format string\n- Add basic Vue support\n- Merge pull request #187 from adriaanzon\/vue\nSHA256 checksum: e38384a93873d91dd4ab811535d616aad14f0789d7e84e7da1a479357788bf1d","package":"tcomment.zip","4":"tcomment.zip","src_id":"25374","5":"25374","creation_date":"1499143648","6":"1499143648"},{"0":"1173","vim_version":"7.0","1":"7.0","script_version":"3.07","2":"3.07","version_comment":"- FIX #137: Prefer \/\/ for rust comments\n- FIX #138: Support for jinja filetype (see https:\/\/github.com\/Glench\/Vim-Jinja2-Syntax)\n- FIX #140: s:MapOp(): Don't evaluate registers to define op functions\n- s:MapOp: Remove count argument\n- support Tupfile comments\n- Merge pull request #141 from cfillion\/tup-comments\n- FIX #123: GuessFileType(): don't use indent(); properly handle tabs\n- GuessFileType(): Use strwidth() (FIX #144)\n- autoload: Add Makefile support\n- Merge pull request #146 from JIghtuse\/master\n- FIX #147: Add definition for robot file; re-enable col attribute (comment mode only)\n- FIX #148: Prefer \/\/ for java comments\n- Merge pull request #149 from phphong\/change-java-default\n- support commenting for the fish shell\n- Merge pull request #150 from philolo1\/support_fish\n- Add support for Facebook JSX\n- Merge pull request #151 from epeli\/jsx\n- CLOSE #152: postprocess_uncomment option\n- Support for markdown\nMD5 checksum: 4d11779a42c22ea2dbb5f1309b29bce3","3":"- FIX #137: Prefer \/\/ for rust comments\n- FIX #138: Support for jinja filetype (see https:\/\/github.com\/Glench\/Vim-Jinja2-Syntax)\n- FIX #140: s:MapOp(): Don't evaluate registers to define op functions\n- s:MapOp: Remove count argument\n- support Tupfile comments\n- Merge pull request #141 from cfillion\/tup-comments\n- FIX #123: GuessFileType(): don't use indent(); properly handle tabs\n- GuessFileType(): Use strwidth() (FIX #144)\n- autoload: Add Makefile support\n- Merge pull request #146 from JIghtuse\/master\n- FIX #147: Add definition for robot file; re-enable col attribute (comment mode only)\n- FIX #148: Prefer \/\/ for java comments\n- Merge pull request #149 from phphong\/change-java-default\n- support commenting for the fish shell\n- Merge pull request #150 from philolo1\/support_fish\n- Add support for Facebook JSX\n- Merge pull request #151 from epeli\/jsx\n- CLOSE #152: postprocess_uncomment option\n- Support for markdown\nMD5 checksum: 4d11779a42c22ea2dbb5f1309b29bce3","package":"tcomment.vba","4":"tcomment.vba","src_id":"23636","5":"23636","creation_date":"1443787569","6":"1443787569"},{"0":"1173","vim_version":"7.0","1":"7.0","script_version":"3.07","2":"3.07","version_comment":"- FIX #135: Old map in help docs\n- FIX #136: Uncomment omaps must not call *Anyway; fix handling of U in s:GuessCommentMode()\nMD5 checksum: 1c9d1e9f1de51c7ddcd049839eb686aa","3":"- FIX #135: Old map in help docs\n- FIX #136: Uncomment omaps must not call *Anyway; fix handling of U in s:GuessCommentMode()\nMD5 checksum: 1c9d1e9f1de51c7ddcd049839eb686aa","package":"tcomment.vba","4":"tcomment.vba","src_id":"23021","5":"23021","creation_date":"1426320867","6":"1426320867"},{"0":"1173","vim_version":"7.0","1":"7.0","script_version":"3.06","2":"3.06","version_comment":"- Define toml type\n- Merge pull request #133 from moorereason\/toml\n- FIX #134: s:Printf1() fix regexp\nMD5 checksum: 279fcee28dcde33c347fa2ffa48da054","3":"- Define toml type\n- Merge pull request #133 from moorereason\/toml\n- FIX #134: s:Printf1() fix regexp\nMD5 checksum: 279fcee28dcde33c347fa2ffa48da054","package":"tcomment.vba","4":"tcomment.vba","src_id":"22982","5":"22982","creation_date":"1425668722","6":"1425668722"},{"0":"1173","vim_version":"7.0","1":"7.0","script_version":"3.05","2":"3.05","version_comment":"- add lilypond support\n- Make sure to uncomment if mode = U\n- Rename some <Plug> maps (replace \"-\" with \"_\")\n- Make handling of the mode argument more correct\n- FIX #117: Add support for liquid\n- Add AppleScript support\n- Add definition for Vader [1]\n- Add definition for \"cram\"\n- FIX #122: s:MapOp(): Define specialiced opfunc when necessary (this should also FIX #114)\n- Use '# %s' for gitconfig files, as with the others (ft=git*)\n- add autohotkey comment format\n- Improved support for Rnw files (g:tcommentGuessFileType_rnoweb = \"r\")\n- CLOSE #128: K comment mode\n- Actually CLOSE #128: s:CommentDef(), s:AddModeExtra(): check for mode==K\n- FIX #132: Handle mixed \"\/\/\" % \"\/* ... *\/\" C-like linewise comments   - tcomment#GetLineC(...), g:tcommentLineC_fmt   - use for more filetypes   - s:Count(), s:Printf1()\nMD5 checksum: a63f84ff30a8d9e5dfa7f43b800c05bf","3":"- add lilypond support\n- Make sure to uncomment if mode = U\n- Rename some <Plug> maps (replace \"-\" with \"_\")\n- Make handling of the mode argument more correct\n- FIX #117: Add support for liquid\n- Add AppleScript support\n- Add definition for Vader [1]\n- Add definition for \"cram\"\n- FIX #122: s:MapOp(): Define specialiced opfunc when necessary (this should also FIX #114)\n- Use '# %s' for gitconfig files, as with the others (ft=git*)\n- add autohotkey comment format\n- Improved support for Rnw files (g:tcommentGuessFileType_rnoweb = \"r\")\n- CLOSE #128: K comment mode\n- Actually CLOSE #128: s:CommentDef(), s:AddModeExtra(): check for mode==K\n- FIX #132: Handle mixed \"\/\/\" % \"\/* ... *\/\" C-like linewise comments   - tcomment#GetLineC(...), g:tcommentLineC_fmt   - use for more filetypes   - s:Count(), s:Printf1()\nMD5 checksum: a63f84ff30a8d9e5dfa7f43b800c05bf","package":"tcomment.vba","4":"tcomment.vba","src_id":"22948","5":"22948","creation_date":"1424803325","6":"1424803325"},{"0":"1173","vim_version":"7.0","1":"7.0","script_version":"3.04","2":"3.04","version_comment":"- tcomment#OperatorLine*: Use L as comment_type\n- EndColRx: Use $ if pos >= strdisplaywidth of line (fix gc$ for certain filetypes)\n- FIX #101: CommentBlock: Don't remove leading whitespace This caused problems when uncommenting block comments with blank\/empty middle comment markers\n- FIX #102: g:tcomment#must_escape_expression_backslash: Allow customization of pre-7.2-407 special case\n- add noweb filetype\n- Add support for asterisk\n- CLOSE #105: Use g< and g> for explicit uncommenting and commenting - Rename g:tcommentMapLeaderOp2 to g:tcommentMapLeaderCommentAnyway - g:tcommentMapLeaderUncommentAnyway - C, U comment modes - s:GetTempOption()\n- FIX #105: Allow count for visual g<, g>; fix g<; add -bar to command definitions\n- Make <Plug>TComment-Comment, <Plug>TComment-Uncomment <silent>\n- Add support for elixir file type\n- CLOSE #107: Fix help on g:tcomment#options_comments and g:tcomment#options_commentstring\n- jade support (http:\/\/jade-lang.com\/)\n- Support for context\n- added comment definition for purescript\n- FIX #112: g:tcomment#options_comments, g:tcomment#options_commentstring: check g:tcommentOptions for whitespace preference\nMD5 checksum: 839a0aa6e7f5d6ef85a7d787609a323b","3":"- tcomment#OperatorLine*: Use L as comment_type\n- EndColRx: Use $ if pos >= strdisplaywidth of line (fix gc$ for certain filetypes)\n- FIX #101: CommentBlock: Don't remove leading whitespace This caused problems when uncommenting block comments with blank\/empty middle comment markers\n- FIX #102: g:tcomment#must_escape_expression_backslash: Allow customization of pre-7.2-407 special case\n- add noweb filetype\n- Add support for asterisk\n- CLOSE #105: Use g< and g> for explicit uncommenting and commenting - Rename g:tcommentMapLeaderOp2 to g:tcommentMapLeaderCommentAnyway - g:tcommentMapLeaderUncommentAnyway - C, U comment modes - s:GetTempOption()\n- FIX #105: Allow count for visual g<, g>; fix g<; add -bar to command definitions\n- Make <Plug>TComment-Comment, <Plug>TComment-Uncomment <silent>\n- Add support for elixir file type\n- CLOSE #107: Fix help on g:tcomment#options_comments and g:tcomment#options_commentstring\n- jade support (http:\/\/jade-lang.com\/)\n- Support for context\n- added comment definition for purescript\n- FIX #112: g:tcomment#options_comments, g:tcomment#options_commentstring: check g:tcommentOptions for whitespace preference\nMD5 checksum: 839a0aa6e7f5d6ef85a7d787609a323b","package":"tcomment.vba","4":"tcomment.vba","src_id":"22422","5":"22422","creation_date":"1410690430","6":"1410690430"},{"0":"1173","vim_version":"7.0","1":"7.0","script_version":"3.03","2":"3.03","version_comment":"- GetStartEnd: ignore empty lines when determining the indentation level\n- FIX #96: StartColRx(): Use \"^\" only for col < 1 (not <= 1)\n- FIX #97: Set startcol depending on comment_mode\nMD5 checksum: c6a7ac7e915d5cf7a710aa8f118b50de","3":"- GetStartEnd: ignore empty lines when determining the indentation level\n- FIX #96: StartColRx(): Use \"^\" only for col < 1 (not <= 1)\n- FIX #97: Set startcol depending on comment_mode\nMD5 checksum: c6a7ac7e915d5cf7a710aa8f118b50de","package":"tcomment.vba","4":"tcomment.vba","src_id":"21766","5":"21766","creation_date":"1397402717","6":"1397402717"},{"0":"1173","vim_version":"7.0","1":"7.0","script_version":"3.02","2":"3.02","version_comment":"- b:tcomment_def_{NAME}: Buffer-local configuration (closes #93)\n- FIX #94: if line(\"'<\") == line(\"'>\") and col('.') is before the first character, use G mode\n- FIX 95: GetStartEnd(): Don't set cbeg to 0 on empty lines\nMD5 checksum: 5bca91c102f1192cccb75708659f825c","3":"- b:tcomment_def_{NAME}: Buffer-local configuration (closes #93)\n- FIX #94: if line(\"'<\") == line(\"'>\") and col('.') is before the first character, use G mode\n- FIX 95: GetStartEnd(): Don't set cbeg to 0 on empty lines\nMD5 checksum: 5bca91c102f1192cccb75708659f825c","package":"tcomment.vba","4":"tcomment.vba","src_id":"21708","5":"21708","creation_date":"1396378873","6":"1396378873"},{"0":"1173","vim_version":"7.0","1":"7.0","script_version":"3.01","2":"3.01","version_comment":"- Support for vimwiki (closes #80)\n- Better handling of commentstrings like \"%%%s\"\n- Support for verilog & verilog_systemverilog (closes #81)\n- verlog inline comments\n- Improved support for constructing comments from the &comments option\n- Typo (fixes #82)\n- Misc improvements to handling &comment, &commentstring; count for c-style comments only changes the first part of the comment; enable counts for gcb\n- Ignore count for xmaps\n- Re-enable custom verilog definitions (after debugging)\n- Use strdisplaywidth() only with vim >= 7.3 (fixes #83)\n- Disallow unsupported comment types (e.g. insert comments when only linewise comments are allowed)\n- Remove custom javaScript comment definitions (use javascript)\n- Misc changes to operator maps; gc$ maps to R-type comments (fixes #84)\n- x\/v op map: Use R type comment if cend ~~ col('$') (fixes #85)\n- Maps are not <silent> any more (display error\/warning message if any)\n- If comment_mode == 'i', also check if it should rather be 'G'\n- Make op maps silent again\n- Improve configurability of mappings.\n- Consistently use virtcol(); block comments properly support mixedindent\n- Removed some superfluous :exec commands from map definitions\n- Fix regression with text objects.\n- <c-_>NUMBER maps always set the count argument for the subsequent map (makes it easier to insert \/** *\/ type of comments)\n- Misc changes (fixes #88)\n- Let g:tcomment_types override default settings\n- Support for blade.php (closes #90)\n- Support for QML files (Qt Meta Language)\n- FIX #92: GuessFileType(): avoid \"E706: Variable type mismatch\"\nMD5 checksum: 10b548c1bfc946206ec46fca58ae5a62","3":"- Support for vimwiki (closes #80)\n- Better handling of commentstrings like \"%%%s\"\n- Support for verilog & verilog_systemverilog (closes #81)\n- verlog inline comments\n- Improved support for constructing comments from the &comments option\n- Typo (fixes #82)\n- Misc improvements to handling &comment, &commentstring; count for c-style comments only changes the first part of the comment; enable counts for gcb\n- Ignore count for xmaps\n- Re-enable custom verilog definitions (after debugging)\n- Use strdisplaywidth() only with vim >= 7.3 (fixes #83)\n- Disallow unsupported comment types (e.g. insert comments when only linewise comments are allowed)\n- Remove custom javaScript comment definitions (use javascript)\n- Misc changes to operator maps; gc$ maps to R-type comments (fixes #84)\n- x\/v op map: Use R type comment if cend ~~ col('$') (fixes #85)\n- Maps are not <silent> any more (display error\/warning message if any)\n- If comment_mode == 'i', also check if it should rather be 'G'\n- Make op maps silent again\n- Improve configurability of mappings.\n- Consistently use virtcol(); block comments properly support mixedindent\n- Removed some superfluous :exec commands from map definitions\n- Fix regression with text objects.\n- <c-_>NUMBER maps always set the count argument for the subsequent map (makes it easier to insert \/** *\/ type of comments)\n- Misc changes (fixes #88)\n- Let g:tcomment_types override default settings\n- Support for blade.php (closes #90)\n- Support for QML files (Qt Meta Language)\n- FIX #92: GuessFileType(): avoid \"E706: Variable type mismatch\"\nMD5 checksum: 10b548c1bfc946206ec46fca58ae5a62","package":"tcomment.vba","4":"tcomment.vba","src_id":"21688","5":"21688","creation_date":"1396032194","6":"1396032194"},{"0":"1173","vim_version":"7.0","1":"7.0","script_version":"3.00","2":"3.00","version_comment":"- Help template\n- Add asciidoc (\/\/) and expect (#) definitions\n- Fix xs commentstring\n- Accept js as alias for javascript (fixes #70)\n- Adding hy support\n- s:GetStartEnd(): Make sure end >= begin (fixes #73)\n- strip_whitespace defaults to 1 (fixes #54)\n- \"whitespace\" option: Consistently use partial matching\n- mixedindent option: Check only in s:StartColRx()\n- s:CommentDef(): Minor optimization\n- Support for remind filetype (closes #74)\n- tcomment#TypeExists(name, ...): takes a mode as optional second argument\n- R comments: Properly set cend to col('$')\n- s:StartPosRx(), s:EndPosRx(): Ignore lnum in I mode\n- s:StartColRx(): Takes a col as second argument\n- Renamed g:tcommentBlankLines to g:tcomment#blank_lines (can be 0, 1, 2)\n- s:GetCustomCommentString(): Take into account whether a custom comment style is defined for block & inline comments\n- g:tcomment#rstrip_on_uncomment: Remove right-hand whitespace on uncomment\n- Use a loop, not :s\n- g:tcomment#ignore_comment_def\n- mixedindent option defaults to 1\n- mixedindent defaults to 1\nMD5 checksum: c2668f9147783d47e640133e51ba20e4","3":"- Help template\n- Add asciidoc (\/\/) and expect (#) definitions\n- Fix xs commentstring\n- Accept js as alias for javascript (fixes #70)\n- Adding hy support\n- s:GetStartEnd(): Make sure end >= begin (fixes #73)\n- strip_whitespace defaults to 1 (fixes #54)\n- \"whitespace\" option: Consistently use partial matching\n- mixedindent option: Check only in s:StartColRx()\n- s:CommentDef(): Minor optimization\n- Support for remind filetype (closes #74)\n- tcomment#TypeExists(name, ...): takes a mode as optional second argument\n- R comments: Properly set cend to col('$')\n- s:StartPosRx(), s:EndPosRx(): Ignore lnum in I mode\n- s:StartColRx(): Takes a col as second argument\n- Renamed g:tcommentBlankLines to g:tcomment#blank_lines (can be 0, 1, 2)\n- s:GetCustomCommentString(): Take into account whether a custom comment style is defined for block & inline comments\n- g:tcomment#rstrip_on_uncomment: Remove right-hand whitespace on uncomment\n- Use a loop, not :s\n- g:tcomment#ignore_comment_def\n- mixedindent option defaults to 1\n- mixedindent defaults to 1\nMD5 checksum: c2668f9147783d47e640133e51ba20e4","package":"tcomment.vba","4":"tcomment.vba","src_id":"21333","5":"21333","creation_date":"1389947096","6":"1389947096"},{"0":"1173","vim_version":"7.0","1":"7.0","script_version":"2.09","2":"2.09","version_comment":"- Adds Scala support\n- Support for (firefox) chromemanifest filetype\n- g:tcommentMaps: If true, set maps (fixes #42)\n- addon-info\n- Enable replacements for xml\/html\/... (fixes #44)\n- Experimental option g:tcomment#mixed_indentation: Deal with inconsistent indentation styles (fixes #43)\n- Experimental option 'mixedindent': Deal with inconsistent indentation styles (fixes #43)\n- s:DoReplacements(): Handle an empty list of tokens correctly\n- mixedindent: Set virtual column to strdisplaywidth(indentStr, cbeg) + 1\n- mixedindent: mixedindentUndo previous change; use \\%>v again\n- Call :redraw only when tcomment#Complete* was called for the first time if v:version < 703\n- s:FEscapeCommentString(): Correctly deal comment string that include %\n- More flexible handling of \"dotted\" filetypes (fixes #45)\n- Undo previous changes (s:FEscapeCommentString) (fixes #46)\n- Map erubyExpression syntax to ruby filetype\n- s:StartColRx(pos): Use ^ for pos 0-1 (fixes #47)\n- If mixedindent: use col - 1\n- Derive g:tcommentLineC from g:tcommentInlineC so that you can set g:tcommentLineC without having to set g:tcommentInlineC\n- mixedindent: Adjust column only for inline comments\n- g:tcommentModeExtra: Basic support for preferring block-type comments 'B' uncommenting doesn't work properly when called from operator maps\n- Support for gcb maps (block comments) and experimental support for '#' mode extra for operator maps (fixes #49)\n- opextra =~'#*: Adjust for commentstring containing printf placeholders (%) (closes #49)\n- s:GuessFileType(): If there is no custom definition for the fallback filetype, use the filetype (fixes #45)\n- g:tcomment#filetype_map now works on filetype parts (when using dotted filetype) & special support for rails-views (fixes #45)\n- Support for postfix main (thanks to ypid)\n- strip_whitespace option (closes #54)\n- Support for cmake.\n- Support for markdown.\n- Support for sshdconfig.\n- Support for sshconfig.\n- Support for gnuplot (fixes #56)\n- Support slim template\n- s:CommentDef(): Uncommenting: correct string for &selection == inclusive (fixes #53)\n- Support for esmtprc.\n- \"whitespace\" option: Define whether to surround commented text with whitespace\n- Experimental inline comment text object (not functional yet)\n- tcomment#DefineType(name, commentdef, ?cdef={}, ?anyway=0)\n- s:SetWhitespaceMode(cdef): Add whitespace if mode = \"both\" and the commentstring doesn't include whitespace\n- Support for R6RS scheme block comments (fixes #60)\n- Support for upstart.\n- Support for racket filetype (fixes #60)\n- Added form support\n- Adding htmljinja support (same as htmldjango).\n- Adding lua support\n- Objective C++\n- Support for salt stacks (closes #66); sort order of filetypes\n- Support for dustjs (closes #67)\nMD5 checksum: d507f7e6d171034a45e2d349561d29f1","3":"- Adds Scala support\n- Support for (firefox) chromemanifest filetype\n- g:tcommentMaps: If true, set maps (fixes #42)\n- addon-info\n- Enable replacements for xml\/html\/... (fixes #44)\n- Experimental option g:tcomment#mixed_indentation: Deal with inconsistent indentation styles (fixes #43)\n- Experimental option 'mixedindent': Deal with inconsistent indentation styles (fixes #43)\n- s:DoReplacements(): Handle an empty list of tokens correctly\n- mixedindent: Set virtual column to strdisplaywidth(indentStr, cbeg) + 1\n- mixedindent: mixedindentUndo previous change; use \\%>v again\n- Call :redraw only when tcomment#Complete* was called for the first time if v:version < 703\n- s:FEscapeCommentString(): Correctly deal comment string that include %\n- More flexible handling of \"dotted\" filetypes (fixes #45)\n- Undo previous changes (s:FEscapeCommentString) (fixes #46)\n- Map erubyExpression syntax to ruby filetype\n- s:StartColRx(pos): Use ^ for pos 0-1 (fixes #47)\n- If mixedindent: use col - 1\n- Derive g:tcommentLineC from g:tcommentInlineC so that you can set g:tcommentLineC without having to set g:tcommentInlineC\n- mixedindent: Adjust column only for inline comments\n- g:tcommentModeExtra: Basic support for preferring block-type comments 'B' uncommenting doesn't work properly when called from operator maps\n- Support for gcb maps (block comments) and experimental support for '#' mode extra for operator maps (fixes #49)\n- opextra =~'#*: Adjust for commentstring containing printf placeholders (%) (closes #49)\n- s:GuessFileType(): If there is no custom definition for the fallback filetype, use the filetype (fixes #45)\n- g:tcomment#filetype_map now works on filetype parts (when using dotted filetype) & special support for rails-views (fixes #45)\n- Support for postfix main (thanks to ypid)\n- strip_whitespace option (closes #54)\n- Support for cmake.\n- Support for markdown.\n- Support for sshdconfig.\n- Support for sshconfig.\n- Support for gnuplot (fixes #56)\n- Support slim template\n- s:CommentDef(): Uncommenting: correct string for &selection == inclusive (fixes #53)\n- Support for esmtprc.\n- \"whitespace\" option: Define whether to surround commented text with whitespace\n- Experimental inline comment text object (not functional yet)\n- tcomment#DefineType(name, commentdef, ?cdef={}, ?anyway=0)\n- s:SetWhitespaceMode(cdef): Add whitespace if mode = \"both\" and the commentstring doesn't include whitespace\n- Support for R6RS scheme block comments (fixes #60)\n- Support for upstart.\n- Support for racket filetype (fixes #60)\n- Added form support\n- Adding htmljinja support (same as htmldjango).\n- Adding lua support\n- Objective C++\n- Support for salt stacks (closes #66); sort order of filetypes\n- Support for dustjs (closes #67)\nMD5 checksum: d507f7e6d171034a45e2d349561d29f1","package":"tcomment.vba","4":"tcomment.vba","src_id":"20935","5":"20935","creation_date":"1382118298","6":"1382118298"},{"0":"1173","vim_version":"7.0","1":"7.0","script_version":"2.08","2":"2.08","version_comment":"- Enable count for gc operator maps (use e.g. 3gc2l instead of gc3c2l; maybe remove gc<count>c maps later on)\n- <count>gc operator maps: use v:count instead of v:count1\n- fixed unlet\n- Merge branch 'master' of https:\/\/github.com\/grassofhust\/tcomment_vim\n- Added vhdl to tcomment#DefineType\n- tcomment#GuessCommentType(): Make filetype guessing accessible for other plugins\n- FIX: didn't guess filetype correctly for lines containing only one character\n- Guess filetype: Improved handling of empty lines\n- g:tcommentSyntaxMap: support additional info on how to handle empty lines\n- g:tcommentSyntaxMap: support filetype key: explicitly map syntax name per filetype (fixes #39)\n- Fix typo\n- Add `g:tcommentGuessFileType_smarty = 1`\n- Define\/handle 'ini' file type (e.g. for php.ini)\nMD5 checksum: 702082a857ddeaf75d3b4fd884363173","3":"- Enable count for gc operator maps (use e.g. 3gc2l instead of gc3c2l; maybe remove gc<count>c maps later on)\n- <count>gc operator maps: use v:count instead of v:count1\n- fixed unlet\n- Merge branch 'master' of https:\/\/github.com\/grassofhust\/tcomment_vim\n- Added vhdl to tcomment#DefineType\n- tcomment#GuessCommentType(): Make filetype guessing accessible for other plugins\n- FIX: didn't guess filetype correctly for lines containing only one character\n- Guess filetype: Improved handling of empty lines\n- g:tcommentSyntaxMap: support additional info on how to handle empty lines\n- g:tcommentSyntaxMap: support filetype key: explicitly map syntax name per filetype (fixes #39)\n- Fix typo\n- Add `g:tcommentGuessFileType_smarty = 1`\n- Define\/handle 'ini' file type (e.g. for php.ini)\nMD5 checksum: 702082a857ddeaf75d3b4fd884363173","package":"tcomment.vba","4":"tcomment.vba","src_id":"19247","5":"19247","creation_date":"1356679267","6":"1356679267"},{"0":"1173","vim_version":"7.0","1":"7.0","script_version":"2.07","2":"2.07","version_comment":"- Avoid duplicate tag in help file (reported by utkarshkukreti)\n- add puppet type\n- Use \\r instead of ^M\n- support for haml and coffeescript\n- Support for gitignore\n- Merge branch 'master' of https:\/\/github.com\/ignovak\/tcomment_vim\n- Enable \"filetype guessing\" for eruby (fixes #25)\n- g:tcommentModeExtra: Always modify how commenting works\n- g:tcommentModeExtra: >> ... Like > but also move the cursor to the next line\n- adding gnu smalltalk comment style\n- Add comment definition for \"smarty\"\n- Sort definition for \"sql\"\n- Merge branch 'master' of https:\/\/github.com\/clutt0n\/tcomment_vim\n- added support for jasmine.coffee (cf. https:\/\/github.com\/claco\/jasmine.vim)\n- fixed jasmine (have to use syntax instead of filetype)\n- Block comments: set &sel = exclusive (fixes #30; bug 1)\n- Merge branch 'master' of https:\/\/github.com\/paulwittmann\/tcomment_vim\n- spec files for issue 30\n- Inline comments: Include the current character if selection == inclusive (fixes #30 bug 2)\n- gC in visual mode: call :TCommentMaybeInline! (fixes #30 bug 3)\n- Added Clojure and Clojurescript support. Thou the comment is a single ';' it is a widely adopted convention to comment whole lines with ';;'\n- command line completion: also offer rx*= arguments\n- Merge branch 'master' of https:\/\/github.com\/ssedano\/tcomment_vim\n- clojure: use \";\" for inline comments\n- TCommentRight used wrong column\n- b:tcommentOptions: buffer-local options\n- Deal with mode argument (concatenate with commentMode)\n- Removed visual\/selection maps for :TCommentRight\n- <c-_>cc and <c-_>ca maps to temporary set options (count, as) on the fly\n- <c-_>1 .. <c-_>9 maps to invoke :TComment count=N (repeat the comment string N times)\n- clojure: use the \"count\" property instead of hardcoding the double semicolon (\";;\")\n- Enable inline comments for insert & normal mode (create empty comments, which isn't always that useful; fixes #33)\n- When guessing a filetype, make sure to use custom definitions when no syntax name is found\n- gc<count>c maps that set the \"count\" attribute\n- Make sure to ignore %%s in commentstrings\n- gc<Count>c{motion} maps work as toggle\n- Enable <c-_><Count> maps for insert mode\n- Monkey language comment style\nMD5 checksum: 0853c50ebdcd4c52a31b2ad2d514d1e0","3":"- Avoid duplicate tag in help file (reported by utkarshkukreti)\n- add puppet type\n- Use \\r instead of ^M\n- support for haml and coffeescript\n- Support for gitignore\n- Merge branch 'master' of https:\/\/github.com\/ignovak\/tcomment_vim\n- Enable \"filetype guessing\" for eruby (fixes #25)\n- g:tcommentModeExtra: Always modify how commenting works\n- g:tcommentModeExtra: >> ... Like > but also move the cursor to the next line\n- adding gnu smalltalk comment style\n- Add comment definition for \"smarty\"\n- Sort definition for \"sql\"\n- Merge branch 'master' of https:\/\/github.com\/clutt0n\/tcomment_vim\n- added support for jasmine.coffee (cf. https:\/\/github.com\/claco\/jasmine.vim)\n- fixed jasmine (have to use syntax instead of filetype)\n- Block comments: set &sel = exclusive (fixes #30; bug 1)\n- Merge branch 'master' of https:\/\/github.com\/paulwittmann\/tcomment_vim\n- spec files for issue 30\n- Inline comments: Include the current character if selection == inclusive (fixes #30 bug 2)\n- gC in visual mode: call :TCommentMaybeInline! (fixes #30 bug 3)\n- Added Clojure and Clojurescript support. Thou the comment is a single ';' it is a widely adopted convention to comment whole lines with ';;'\n- command line completion: also offer rx*= arguments\n- Merge branch 'master' of https:\/\/github.com\/ssedano\/tcomment_vim\n- clojure: use \";\" for inline comments\n- TCommentRight used wrong column\n- b:tcommentOptions: buffer-local options\n- Deal with mode argument (concatenate with commentMode)\n- Removed visual\/selection maps for :TCommentRight\n- <c-_>cc and <c-_>ca maps to temporary set options (count, as) on the fly\n- <c-_>1 .. <c-_>9 maps to invoke :TComment count=N (repeat the comment string N times)\n- clojure: use the \"count\" property instead of hardcoding the double semicolon (\";;\")\n- Enable inline comments for insert & normal mode (create empty comments, which isn't always that useful; fixes #33)\n- When guessing a filetype, make sure to use custom definitions when no syntax name is found\n- gc<count>c maps that set the \"count\" attribute\n- Make sure to ignore %%s in commentstrings\n- gc<Count>c{motion} maps work as toggle\n- Enable <c-_><Count> maps for insert mode\n- Monkey language comment style\nMD5 checksum: 0853c50ebdcd4c52a31b2ad2d514d1e0","package":"tcomment.vba","4":"tcomment.vba","src_id":"19019","5":"19019","creation_date":"1353655196","6":"1353655196"},{"0":"1173","vim_version":"7.0","1":"7.0","script_version":"2.06","2":"2.06","version_comment":"- tcomment#Comment(): Remove last item in search history (reported by Raimond)\n- Add config for conkyrc filetype.\n- Add config for 'robots' filetype.\n- tcomment#GetCommentDef(name)\n- g:tcomment_types: override tcomment's default comment styles (fix #12)\n- Fixed ft-guessing of htmldjango files\n- Add definitions for dnsmasq, pac, resolv and squid.\n- Avoid the problem reported in https:\/\/github.com\/tomtom\/tcomment_vim\/pull\/18\n- Handle nested comments in c mode (fix #19)\nMD5 checksum: 0e23f194638256fb4fa4a729df645966","3":"- tcomment#Comment(): Remove last item in search history (reported by Raimond)\n- Add config for conkyrc filetype.\n- Add config for 'robots' filetype.\n- tcomment#GetCommentDef(name)\n- g:tcomment_types: override tcomment's default comment styles (fix #12)\n- Fixed ft-guessing of htmldjango files\n- Add definitions for dnsmasq, pac, resolv and squid.\n- Avoid the problem reported in https:\/\/github.com\/tomtom\/tcomment_vim\/pull\/18\n- Handle nested comments in c mode (fix #19)\nMD5 checksum: 0e23f194638256fb4fa4a729df645966","package":"tcomment.vba","4":"tcomment.vba","src_id":"17289","5":"17289","creation_date":"1327167818","6":"1327167818"},{"0":"1173","vim_version":"7.0","1":"7.0","script_version":"2.05","2":"2.05","version_comment":"- Explicit support for python (thanks to brendanarnold)\n- Support for samba (thanks Dominic)\n- .gitignore\n- Define new types: debsources and debcontrol\n- Removed some whitespace as proposed by blueyed\n- Add config for typoscript filetype.\n- EXPERIMENTAL commentstring_rx: Support for using regexps to uncomment code\n- s:ProcessedLine: Don't substitute(rv, '\\n', '\\\\\\n', 'g')\n- Try to handle char-type text objects (disabled by default)\n- scss (SASS) filetype\n- Add config for 'nginx' filetype.\nMD5 checksum: 0e23f194638256fb4fa4a729df645966","3":"- Explicit support for python (thanks to brendanarnold)\n- Support for samba (thanks Dominic)\n- .gitignore\n- Define new types: debsources and debcontrol\n- Removed some whitespace as proposed by blueyed\n- Add config for typoscript filetype.\n- EXPERIMENTAL commentstring_rx: Support for using regexps to uncomment code\n- s:ProcessedLine: Don't substitute(rv, '\\n', '\\\\\\n', 'g')\n- Try to handle char-type text objects (disabled by default)\n- scss (SASS) filetype\n- Add config for 'nginx' filetype.\nMD5 checksum: 0e23f194638256fb4fa4a729df645966","package":"tcomment.vba","4":"tcomment.vba","src_id":"15731","5":"15731","creation_date":"1306393856","6":"1306393856"},{"0":"1173","vim_version":"7.0","1":"7.0","script_version":"2.04","2":"2.04","version_comment":"- Support for fstab\n- g:tcommentOptions: Other key-value options used by |tcomment#Comment()|.\n- Support for django (thanks to Jim Tinsky)\n- g:tcomment#syntax_substitute: Rewrite syntax names\n- django support: minor correction\nMD5 checksum: 994e5886d185857848b5472d5457b232","3":"- Support for fstab\n- g:tcommentOptions: Other key-value options used by |tcomment#Comment()|.\n- Support for django (thanks to Jim Tinsky)\n- g:tcomment#syntax_substitute: Rewrite syntax names\n- django support: minor correction\nMD5 checksum: 994e5886d185857848b5472d5457b232","package":"tcomment.vba","4":"tcomment.vba","src_id":"14811","5":"14811","creation_date":"1295549191","6":"1295549191"},{"0":"1173","vim_version":"7.0","1":"7.0","script_version":"2.03","2":"2.03","version_comment":"- s:PrintF(): Silently ignore malformed format strings\n- Deal with major.minor pseudo-filetypes\n- go-lang\n- Remove s:SPrintF() since vim now has printf()\nMD5 checksum: 4a13ffb1b1d46bbd2dc8dcee77507983","3":"- s:PrintF(): Silently ignore malformed format strings\n- Deal with major.minor pseudo-filetypes\n- go-lang\n- Remove s:SPrintF() since vim now has printf()\nMD5 checksum: 4a13ffb1b1d46bbd2dc8dcee77507983","package":"tcomment.vba","4":"tcomment.vba","src_id":"14452","5":"14452","creation_date":"1291703328","6":"1291703328"},{"0":"1173","vim_version":"7.0","1":"7.0","script_version":"2.1","2":"2.1","version_comment":"Minor bug fix.","3":"Minor bug fix.","package":"tcomment.vba","4":"tcomment.vba","src_id":"13972","5":"13972","creation_date":"1286009727","6":"1286009727"},{"0":"1173","vim_version":"7.0","1":"7.0","script_version":"2.0","2":"2.0","version_comment":"- Support for erlang (thanks to Zhang Jinzhu)\r\n- Support for x86conf\r\n- Changed comment string for eruby (proposed by Vinicius Baggio)\r\n- NEW: Enabled key=value pairs to configure commenting\r\n- CHANGE: Moved the definition of some variables from plugin\/tComment.vim to autoload\/tcomment.vim\r\n- CHANGE: Renamed the file plugin\/tComment.vim to plugin\/tcomment.vim\r\n- CHANGE: Renamed certain global functions to tcomment#...\r\n","3":"- Support for erlang (thanks to Zhang Jinzhu)\r\n- Support for x86conf\r\n- Changed comment string for eruby (proposed by Vinicius Baggio)\r\n- NEW: Enabled key=value pairs to configure commenting\r\n- CHANGE: Moved the definition of some variables from plugin\/tComment.vim to autoload\/tcomment.vim\r\n- CHANGE: Renamed the file plugin\/tComment.vim to plugin\/tcomment.vim\r\n- CHANGE: Renamed certain global functions to tcomment#...\r\n","package":"tcomment.vba","4":"tcomment.vba","src_id":"13831","5":"13831","creation_date":"1284492859","6":"1284492859"},{"0":"1173","vim_version":"7.0","1":"7.0","script_version":"1.10","2":"1.10","version_comment":"- tcomment#Operator defines w:tcommentPos if invoked repeatedly\r\n- s:GuessFileType: use len(getline()) instead of col()","3":"- tcomment#Operator defines w:tcommentPos if invoked repeatedly\r\n- s:GuessFileType: use len(getline()) instead of col()","package":"tComment.vba.gz","4":"tComment.vba.gz","src_id":"11513","5":"11513","creation_date":"1255243151","6":"1255243151"},{"0":"1173","vim_version":"7.0","1":"7.0","script_version":"1.9","2":"1.9","version_comment":"- Fix left offset for inline comments (via operator binding)\r\n","3":"- Fix left offset for inline comments (via operator binding)\r\n","package":"tComment.vba.gz","4":"tComment.vba.gz","src_id":"8689","5":"8689","creation_date":"1210820721","6":"1210820721"},{"0":"1173","vim_version":"7.0","1":"7.0","script_version":"1.8a","2":"1.8a","version_comment":"The file autoload\/tcomment.vim was packed as autoload\/tComment.vim. If you installed 1.8, please rename that file or remove autoload\/tComment.vim and use this vimball.","3":"The file autoload\/tcomment.vim was packed as autoload\/tComment.vim. If you installed 1.8, please rename that file or remove autoload\/tComment.vim and use this vimball.","package":"tComment.vba.gz","4":"tComment.vba.gz","src_id":"8640","5":"8640","creation_date":"1209760980","6":"1209760980"},{"0":"1173","vim_version":"7.0","1":"7.0","script_version":"1.8","2":"1.8","version_comment":"- Definitly require vim7\r\n- Split the plugin into autoload & plugin.\r\n- g:TCommentFileTypes is a list (this could cause problems when updating in certain situations)\r\n- Fixed some block comment strings\r\n- Removed extraneous newline in some block comments.\r\n- Maps for visal mode (thanks Krzysztof Goj)\r\n","3":"- Definitly require vim7\r\n- Split the plugin into autoload & plugin.\r\n- g:TCommentFileTypes is a list (this could cause problems when updating in certain situations)\r\n- Fixed some block comment strings\r\n- Removed extraneous newline in some block comments.\r\n- Maps for visal mode (thanks Krzysztof Goj)\r\n","package":"tComment.vba.gz","4":"tComment.vba.gz","src_id":"8627","5":"8627","creation_date":"1209616418","6":"1209616418"},{"0":"1173","vim_version":"7.0","1":"7.0","script_version":"1.7","2":"1.7","version_comment":"- gc{motion} (see g:tcommentMapLeaderOp1) functions as a comment toggle \r\noperator (i.e., something like gcl... works, mostly); gC{motion} (see \r\ng:tcommentMapLeaderOp2) will unconditionally comment the text.\r\n- TCommentAs takes an optional second argument (the comment level)\r\n- New \"n\" map: TCommentAs &filetype [COUNT]\r\n- Defined mail comments\/citations\r\n- g:tcommentSyntaxMap: Map syntax names to filetypes for buffers with \r\nmixed syntax groups that don't match the filetypeEmbeddedsyntax scheme (e.g.  \r\n'vimRubyRegion', which should be commented as ruby syntax, not as vim \r\nsyntax)\r\n- FIX: Comments in vim*Region\r\n- TComment: The use of the type argument has slightly changed (IG -> i, \r\nnew: >)\r\n","3":"- gc{motion} (see g:tcommentMapLeaderOp1) functions as a comment toggle \r\noperator (i.e., something like gcl... works, mostly); gC{motion} (see \r\ng:tcommentMapLeaderOp2) will unconditionally comment the text.\r\n- TCommentAs takes an optional second argument (the comment level)\r\n- New \"n\" map: TCommentAs &filetype [COUNT]\r\n- Defined mail comments\/citations\r\n- g:tcommentSyntaxMap: Map syntax names to filetypes for buffers with \r\nmixed syntax groups that don't match the filetypeEmbeddedsyntax scheme (e.g.  \r\n'vimRubyRegion', which should be commented as ruby syntax, not as vim \r\nsyntax)\r\n- FIX: Comments in vim*Region\r\n- TComment: The use of the type argument has slightly changed (IG -> i, \r\nnew: >)\r\n","package":"tComment.vba.gz","4":"tComment.vba.gz","src_id":"7588","5":"7588","creation_date":"1188470346","6":"1188470346"},{"0":"1173","vim_version":"7.0","1":"7.0","script_version":"1.6","2":"1.6","version_comment":"- Ignore sql when guessing the comment string in php files; tComment \r\nsometimes chooses the wrong comment string because the use of sql syntax \r\nis used too loosely in php files; if you want to comment embedded sql \r\ncode you have to use TCommentAs\r\n- Use keepjumps in commands.\r\n- Map <c-_>p & <L>_p to vip:TComment<cr>\r\n- Made key maps configurable via g:tcommentMapLeader1 and \r\ng:tcommentMapLeader2\r\n","3":"- Ignore sql when guessing the comment string in php files; tComment \r\nsometimes chooses the wrong comment string because the use of sql syntax \r\nis used too loosely in php files; if you want to comment embedded sql \r\ncode you have to use TCommentAs\r\n- Use keepjumps in commands.\r\n- Map <c-_>p & <L>_p to vip:TComment<cr>\r\n- Made key maps configurable via g:tcommentMapLeader1 and \r\ng:tcommentMapLeader2\r\n","package":"tComment.vba.gz","4":"tComment.vba.gz","src_id":"7046","5":"7046","creation_date":"1177977683","6":"1177977683"},{"0":"1173","vim_version":"6.0","1":"6.0","script_version":"1.5","2":"1.5","version_comment":"- \"Inline\" visual comments (uses the &filetype_inline style if \r\navailable; doesn't check if the filetype actually supports this kind of \r\ncomments); tComment can't currently deduce inline comment styles from \r\n&comments or &commentstring (I personally hardly ever use them); default \r\nmap: <c-_>i or <c-_>I\r\n- In visual mode: if the selection spans several lines, normal mode is \r\nselected; if the selection covers only a part of one line, inline mode \r\nis selected\r\n- Fixed problem with lines containing ^M or ^@ characters.\r\n- It's no longer necessary to call TCommentCollectFileTypes() after \r\ndefining a new filetype via TCommentDefineType()\r\n- Disabled single <c-_> mappings\r\n- Renamed TCommentVisualBlock to TCommentRight\r\n- FIX: Forgot 'x' in ExtractCommentsPart() (thanks to Fredrik Acosta)\r\n","3":"- \"Inline\" visual comments (uses the &filetype_inline style if \r\navailable; doesn't check if the filetype actually supports this kind of \r\ncomments); tComment can't currently deduce inline comment styles from \r\n&comments or &commentstring (I personally hardly ever use them); default \r\nmap: <c-_>i or <c-_>I\r\n- In visual mode: if the selection spans several lines, normal mode is \r\nselected; if the selection covers only a part of one line, inline mode \r\nis selected\r\n- Fixed problem with lines containing ^M or ^@ characters.\r\n- It's no longer necessary to call TCommentCollectFileTypes() after \r\ndefining a new filetype via TCommentDefineType()\r\n- Disabled single <c-_> mappings\r\n- Renamed TCommentVisualBlock to TCommentRight\r\n- FIX: Forgot 'x' in ExtractCommentsPart() (thanks to Fredrik Acosta)\r\n","package":"tComment.zip","4":"tComment.zip","src_id":"5475","5":"5475","creation_date":"1143020680","6":"1143020680"},{"0":"1173","vim_version":"6.0","1":"6.0","script_version":"1.4","2":"1.4","version_comment":"- Fixed problem when &commentstring was invalid (e.g. lua)\r\n- perl_block\r\n- <c-_>s mapped to :TCommentAs <c-r>=&ft<cr>","3":"- Fixed problem when &commentstring was invalid (e.g. lua)\r\n- perl_block\r\n- <c-_>s mapped to :TCommentAs <c-r>=&ft<cr>","package":"tComment.zip","4":"tComment.zip","src_id":"4037","5":"4037","creation_date":"1111007757","6":"1111007757"},{"0":"1173","vim_version":"6.0","1":"6.0","script_version":"1.3","2":"1.3","version_comment":"- slightly improved recognition of embedded syntax\r\n- if no commentstring is defined in whatever way, reconstruct one from \r\n&comments\r\n- The TComment... commands now have bang variants that don't act as toggles \r\nbut always comment out the selected text\r\n- fixed problem with commentstrings containing backslashes\r\n- comment as visual block (allows commenting text to the right of the main \r\ntext, i.e., this command doesn't work on whole lines but on the text to the \r\nright of the cursor)\r\n- enable multimode for dsl, vim filetypes\r\n- added explicit support for some other file types I ran into\r\n","3":"- slightly improved recognition of embedded syntax\r\n- if no commentstring is defined in whatever way, reconstruct one from \r\n&comments\r\n- The TComment... commands now have bang variants that don't act as toggles \r\nbut always comment out the selected text\r\n- fixed problem with commentstrings containing backslashes\r\n- comment as visual block (allows commenting text to the right of the main \r\ntext, i.e., this command doesn't work on whole lines but on the text to the \r\nright of the cursor)\r\n- enable multimode for dsl, vim filetypes\r\n- added explicit support for some other file types I ran into\r\n","package":"tComment.zip","4":"tComment.zip","src_id":"4019","5":"4019","creation_date":"1110801492","6":"1110801492"},{"0":"1173","vim_version":"6.0","1":"6.0","script_version":"0.2","2":"0.2","version_comment":"- Fixed uncommenting of non-aligned comments\r\n- improved support for block comments (with middle lines and indentation)\r\n- using TCommentBlock for file types that don't have block comments creates \r\nsingle line comments\r\n- the default key bindings have slightly changed\r\n- removed the TCommentAsBlock command (TCommentAs provides its functionality)\r\n- removed g:tcommentSetCMS","3":"- Fixed uncommenting of non-aligned comments\r\n- improved support for block comments (with middle lines and indentation)\r\n- using TCommentBlock for file types that don't have block comments creates \r\nsingle line comments\r\n- the default key bindings have slightly changed\r\n- removed the TCommentAsBlock command (TCommentAs provides its functionality)\r\n- removed g:tcommentSetCMS","package":"tComment.zip","4":"tComment.zip","src_id":"3758","5":"3758","creation_date":"1105435333","6":"1105435333"},{"0":"1173","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"tComment.zip","4":"tComment.zip","src_id":"3749","5":"3749","creation_date":"1105090617","6":"1105090617"}]},"1172":{"script_id":"1172","0":"1172","script_name":"templates","1":"templates","script_type":"utility","2":"utility","summary":"Load filetype templates for new files","3":"Load filetype templates for new files","description":"This plugin lets you use filetype-dependent templates for new files, using a simple but effective mechanism.\r\n\r\nIt is, in various ways, a more sophisticated approach to the same problem that vimscript #1160 addresses, but doesn't try to do quite as much.\r\n\r\nWhen you start a fresh buffer, setting a filetype on it will load the corresponding template. E.g. open Vim and issue\r\n\r\n    :setf html\r\n\r\nYou should find a skeleton HTML file, ready to fill in.\r\n\r\nOne new command has been added for convenience: it is called :New and takes exactly one argument. It will open a new empty window and set the filetype for it to the argument given.\r\n\r\nA handful of templates are included, but the real purpose of the plugin is to allow you to easily create your own.","4":"This plugin lets you use filetype-dependent templates for new files, using a simple but effective mechanism.\r\n\r\nIt is, in various ways, a more sophisticated approach to the same problem that vimscript #1160 addresses, but doesn't try to do quite as much.\r\n\r\nWhen you start a fresh buffer, setting a filetype on it will load the corresponding template. E.g. open Vim and issue\r\n\r\n    :setf html\r\n\r\nYou should find a skeleton HTML file, ready to fill in.\r\n\r\nOne new command has been added for convenience: it is called :New and takes exactly one argument. It will open a new empty window and set the filetype for it to the argument given.\r\n\r\nA handful of templates are included, but the real purpose of the plugin is to allow you to easily create your own.","install_details":"Cloning from GitHub using a plugin manager is recommended.\r\nhttps:\/\/github.com\/ap\/vim-templates\r\n\r\nOtherwise download and unzip in your .vim directory.","5":"Cloning from GitHub using a plugin manager is recommended.\r\nhttps:\/\/github.com\/ap\/vim-templates\r\n\r\nOtherwise download and unzip in your .vim directory.","first_name":"Aristotle","6":"Aristotle","last_name":"Pagaltzis","7":"Pagaltzis","releases":[{"0":"1172","vim_version":"7.0","1":"7.0","script_version":"0caaee5c66","2":"0caaee5c66","version_comment":"Better compatibility; better handling of edge cases; (extremely) minimal responsiveness for HTML template","3":"Better compatibility; better handling of edge cases; (extremely) minimal responsiveness for HTML template","package":"templates.zip","4":"templates.zip","src_id":"27880","5":"27880","creation_date":"1641032851","6":"1641032851"}]},"1171":{"script_id":"1171","0":"1171","script_name":"DetectIndent","1":"DetectIndent","script_type":"utility","2":"utility","summary":"Automatically detect indent (expandtab, shiftwidth, tabstop) settings","3":"Automatically detect indent (expandtab, shiftwidth, tabstop) settings","description":"This script provides a command which will attempt to guess the correct indent settings for an open file, for use when there is no modeline available. Note that this is a pure vim implementation, and doesn't require any external applications or interpreters.\r\n\r\nUsage:\r\n\r\n:DetectIndent\r\n\r\nMay also be used in an autocommand, for example:\r\n\r\n:autocmd BufReadPost * :DetectIndent\r\n\r\nOptions:\r\n\r\nTo prefer 'expandtab' to 'noexpandtab' when no detection is possible: \r\n:let g:detectindent_preferred_expandtab = 1\r\n\r\nTo specify a preferred indent level when no detection is possible:\r\n:let g:detectindent_preferred_indent = 4\r\n\r\nNotes:\r\n\r\nDetection is by no means perfect. It won't work if files use especially perverse combinations of spaces and tabs, or weird tab widths. Bug reports and patches encouraged...\r\n\r\nKeeping things up to date on vim.org is a nuisance. For the latest version, visit:\r\n\r\n    http:\/\/github.com\/ciaranm\/detectindent","4":"This script provides a command which will attempt to guess the correct indent settings for an open file, for use when there is no modeline available. Note that this is a pure vim implementation, and doesn't require any external applications or interpreters.\r\n\r\nUsage:\r\n\r\n:DetectIndent\r\n\r\nMay also be used in an autocommand, for example:\r\n\r\n:autocmd BufReadPost * :DetectIndent\r\n\r\nOptions:\r\n\r\nTo prefer 'expandtab' to 'noexpandtab' when no detection is possible: \r\n:let g:detectindent_preferred_expandtab = 1\r\n\r\nTo specify a preferred indent level when no detection is possible:\r\n:let g:detectindent_preferred_indent = 4\r\n\r\nNotes:\r\n\r\nDetection is by no means perfect. It won't work if files use especially perverse combinations of spaces and tabs, or weird tab widths. Bug reports and patches encouraged...\r\n\r\nKeeping things up to date on vim.org is a nuisance. For the latest version, visit:\r\n\r\n    http:\/\/github.com\/ciaranm\/detectindent","install_details":"Place in ~\/.vim\/plugin\/ and ~\/.vim\/doc\/","5":"Place in ~\/.vim\/plugin\/ and ~\/.vim\/doc\/","first_name":"Ciaran","6":"Ciaran","last_name":"McCreesh","7":"McCreesh","releases":[{"0":"1171","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"detectindent-1.0.tar.bz2","4":"detectindent-1.0.tar.bz2","src_id":"3743","5":"3743","creation_date":"1104771961","6":"1104771961"}]},"1170":{"script_id":"1170","0":"1170","script_name":"Abc-Menu","1":"Abc-Menu","script_type":"utility","2":"utility","summary":"Adds alphabetic menus of commands","3":"Adds alphabetic menus of commands","description":"Abc-Menu installs some more menu-Items for easier access and \r\nremembering.\r\n\r\nvim is a very powerfull editor with tons of functions and even \r\nmore documentation. I always found new functions and i was looking\r\nfor a way to search them quickly. index.txt was my friend so far :)\r\n\r\nSometime I have my little daughter laying in my arm and I have only \r\none hand for writing. In this case, some functions of vim are very hard\r\nto reach.\r\n\r\nThis file helps me in both cases.\r\nI made an alphabetical menu for some of the functions for the normal mode.\r\nThe reason for strict alphabetical order  is to make using the menu\r\nlike typing the commands and help to remember to type the command next time \r\nor to be able to use another vim on another maching without this special menu.\r\n\r\nThere are some special sub-menus\r\n i = shift\r\n k = control\r\n l = alt\r\nI think ijkl are keys that everyone knows. You won't find them in the Abc-Menu.\r\n\r\nExample for using the menu:\r\nIf you want to reach all commands in Normal mode with Uppercase characters\r\ntype following keys:\r\n  alt      invoke menu  (or alt-n together)\r\n    n      normal-Mode commands\r\n     i    shift-commands \r\n\r\nLook at the bottom of the screen. Every command has a little tip. I took most\r\ntips from index.txt.\r\n\r\ntested with gvim 6.2, windows XP\r\nKnoppix 3.7: the tips are missing,  Hotkey only in left textarea possible\r\n \r\nScreenshots:\r\nhttp:\/\/jochen-behrens.de\/vim\/vim-menu-g.png\r\nhttp:\/\/jochen-behrens.de\/vim\/vim-menu-n.png","4":"Abc-Menu installs some more menu-Items for easier access and \r\nremembering.\r\n\r\nvim is a very powerfull editor with tons of functions and even \r\nmore documentation. I always found new functions and i was looking\r\nfor a way to search them quickly. index.txt was my friend so far :)\r\n\r\nSometime I have my little daughter laying in my arm and I have only \r\none hand for writing. In this case, some functions of vim are very hard\r\nto reach.\r\n\r\nThis file helps me in both cases.\r\nI made an alphabetical menu for some of the functions for the normal mode.\r\nThe reason for strict alphabetical order  is to make using the menu\r\nlike typing the commands and help to remember to type the command next time \r\nor to be able to use another vim on another maching without this special menu.\r\n\r\nThere are some special sub-menus\r\n i = shift\r\n k = control\r\n l = alt\r\nI think ijkl are keys that everyone knows. You won't find them in the Abc-Menu.\r\n\r\nExample for using the menu:\r\nIf you want to reach all commands in Normal mode with Uppercase characters\r\ntype following keys:\r\n  alt      invoke menu  (or alt-n together)\r\n    n      normal-Mode commands\r\n     i    shift-commands \r\n\r\nLook at the bottom of the screen. Every command has a little tip. I took most\r\ntips from index.txt.\r\n\r\ntested with gvim 6.2, windows XP\r\nKnoppix 3.7: the tips are missing,  Hotkey only in left textarea possible\r\n \r\nScreenshots:\r\nhttp:\/\/jochen-behrens.de\/vim\/vim-menu-g.png\r\nhttp:\/\/jochen-behrens.de\/vim\/vim-menu-n.png","install_details":"Drop this file in your plugin dir\r\nThe next start of vim will show some new menus.\r\n","5":"Drop this file in your plugin dir\r\nThe next start of vim will show some new menus.\r\n","first_name":"Jochen","6":"Jochen","last_name":"Behrens","7":"Behrens","releases":[{"0":"1170","vim_version":"6.0","1":"6.0","script_version":"0.9","2":"0.9","version_comment":"Initial upload","3":"Initial upload","package":"abc-menu.txt","4":"abc-menu.txt","src_id":"3738","5":"3738","creation_date":"1104382110","6":"1104382110"}]},"1169":{"script_id":"1169","0":"1169","script_name":"GoboLinux ColorScheme","1":"GoboLinux ColorScheme","script_type":"color scheme","2":"color scheme","summary":"First Version","3":"First Version","description":"ColorScheme[1] based in the GoboLinux's official site[2]\r\n\r\n[1] http:\/\/img.photobucket.com\/albums\/v106\/teivan\/Computador\/gobo_vim.png\r\n[2] http:\/\/gobolinux.org","4":"ColorScheme[1] based in the GoboLinux's official site[2]\r\n\r\n[1] http:\/\/img.photobucket.com\/albums\/v106\/teivan\/Computador\/gobo_vim.png\r\n[2] http:\/\/gobolinux.org","install_details":"Just copy do ~\/.vim\/colors\/","5":"Just copy do ~\/.vim\/colors\/","first_name":"Uthyr","6":"Uthyr","last_name":"Cordeiro","7":"Cordeiro","releases":[{"0":"1169","vim_version":"6.0","1":"6.0","script_version":"0.2","2":"0.2","version_comment":"Solved ^M problem with dos2unix :)","3":"Solved ^M problem with dos2unix :)","package":"gobo.vim","4":"gobo.vim","src_id":"3746","5":"3746","creation_date":"1104992251","6":"1104992251"},{"0":"1169","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"gobo.vim","4":"gobo.vim","src_id":"3736","5":"3736","creation_date":"1104355778","6":"1104355778"}]},"1168":{"script_id":"1168","0":"1168","script_name":"C# Indent","1":"C# Indent","script_type":"indent","2":"indent","summary":"Indent for C# (keywords: C-sharp, C sharp, CSharp)","3":"Indent for C# (keywords: C-sharp, C sharp, CSharp)","description":"Indent C# files, based on the built-in function cindent()\r\n\r\nFeatures:\r\n\r\n- Indent single-line attribute\r\n","4":"Indent C# files, based on the built-in function cindent()\r\n\r\nFeatures:\r\n\r\n- Indent single-line attribute\r\n","install_details":"just override your original indent\/cs.vim with this one.","5":"just override your original indent\/cs.vim with this one.","first_name":"Aquila","6":"Aquila","last_name":"Deus","7":"Deus","releases":[{"0":"1168","vim_version":"6.0","1":"6.0","script_version":"0.9","2":"0.9","version_comment":"Initial upload","3":"Initial upload","package":"cs.vim","4":"cs.vim","src_id":"3734","5":"3734","creation_date":"1104274233","6":"1104274233"}]},"1167":{"script_id":"1167","0":"1167","script_name":"substitute.vim","1":"substitute.vim","script_type":"utility","2":"utility","summary":"Fast mappings for performing substitutions","3":"Fast mappings for performing substitutions","description":" Visual and normal mode mappings for easy access to substitutions with the\r\n s\/\/\/ command.\r\n\r\n This script will make it easy to replace the word under the cursor, or the\r\n visually selected text across the whole file. If more than one line is\r\n selected the substitution will only occur on the selected lines.\r\n\r\nsubstitute.vim provides the following two mappings for both visual and normal\r\nmode:\r\n\r\n   ;;  Run :substitute on the current buffer without prompting.\r\n\r\n   ;'  The same, only prompt for each.\r\n\r\n   ';  Perform substitution on the lines that match a multi-repeat\r\n       expression, prompting for each.\r\n\r\nThese mappings can be changed as specified in the following section.\r\n\r\nIt is also possible to press <C-R><C-R> while in command line mode to insert\r\nthe text that is replaced into the commandline.\r\n\r\n When the search and replace has completed the cursor can be returned to where\r\n the search started by jumping to mark ' (pressing '' or `').\r\n\r\n github: https:\/\/github.com\/aklt\/vim-substitute \r\n\r\nNote:\r\n - The contents of a register (default \"9) is overwritten\r\n\r\n","4":" Visual and normal mode mappings for easy access to substitutions with the\r\n s\/\/\/ command.\r\n\r\n This script will make it easy to replace the word under the cursor, or the\r\n visually selected text across the whole file. If more than one line is\r\n selected the substitution will only occur on the selected lines.\r\n\r\nsubstitute.vim provides the following two mappings for both visual and normal\r\nmode:\r\n\r\n   ;;  Run :substitute on the current buffer without prompting.\r\n\r\n   ;'  The same, only prompt for each.\r\n\r\n   ';  Perform substitution on the lines that match a multi-repeat\r\n       expression, prompting for each.\r\n\r\nThese mappings can be changed as specified in the following section.\r\n\r\nIt is also possible to press <C-R><C-R> while in command line mode to insert\r\nthe text that is replaced into the commandline.\r\n\r\n When the search and replace has completed the cursor can be returned to where\r\n the search started by jumping to mark ' (pressing '' or `').\r\n\r\n github: https:\/\/github.com\/aklt\/vim-substitute \r\n\r\nNote:\r\n - The contents of a register (default \"9) is overwritten\r\n\r\n","install_details":"Place substitute.vim into the plugin directory, or source it from within vim.","5":"Place substitute.vim into the plugin directory, or source it from within vim.","first_name":"Anders","6":"Anders","last_name":"Th\u00c3\u00b8gersen","7":"Th\u00c3\u00b8gersen","releases":[{"0":"1167","vim_version":"6.0","1":"6.0","script_version":"1.3","2":"1.3","version_comment":"Minor fixes","3":"Minor fixes","package":"vim-substitute.zip","4":"vim-substitute.zip","src_id":"24963","5":"24963","creation_date":"1486990956","6":"1486990956"},{"0":"1167","vim_version":"7.0","1":"7.0","script_version":"1.2","2":"1.2","version_comment":"Added GlobalMap mapping, SingleWordSize option.\r\n\r\nCan now also be found at http:\/\/github.com","3":"Added GlobalMap mapping, SingleWordSize option.\r\n\r\nCan now also be found at http:\/\/github.com","package":"substitute.vba.gz","4":"substitute.vba.gz","src_id":"14654","5":"14654","creation_date":"1293654256","6":"1293654256"},{"0":"1167","vim_version":"6.0","1":"6.0","script_version":"1.1","2":"1.1","version_comment":"Use VimBall and GetLatestVimscripts","3":"Use VimBall and GetLatestVimscripts","package":"substitute.vba.gz","4":"substitute.vba.gz","src_id":"10093","5":"10093","creation_date":"1236092919","6":"1236092919"},{"0":"1167","vim_version":"6.0","1":"6.0","script_version":"1.04","2":"1.04","version_comment":"Added a separate helpfile and the possibility of changing\r\nmappings and the register that the script uses.\r\n","3":"Added a separate helpfile and the possibility of changing\r\nmappings and the register that the script uses.\r\n","package":"substitute.vim","4":"substitute.vim","src_id":"4628","5":"4628","creation_date":"1127825475","6":"1127825475"},{"0":"1167","vim_version":"6.0","1":"6.0","script_version":"1.03","2":"1.03","version_comment":"Changed the meaning of the ;' mapping, and added <unique> to the map\r\ndefinitions.  Added the Escape function so $ and ^ are only escaped when they\r\nappear at the beginning, or at the end.\r\n","3":"Changed the meaning of the ;' mapping, and added <unique> to the map\r\ndefinitions.  Added the Escape function so $ and ^ are only escaped when they\r\nappear at the beginning, or at the end.\r\n","package":"substitute.vim","4":"substitute.vim","src_id":"3760","5":"3760","creation_date":"1105561422","6":"1105561422"},{"0":"1167","vim_version":"6.0","1":"6.0","script_version":"1.01","2":"1.01","version_comment":"The check to see if the mappings already exist has been removed.  It is probably better to let the user add his or her preferred mappings by modifying the script.","3":"The check to see if the mappings already exist has been removed.  It is probably better to let the user add his or her preferred mappings by modifying the script.","package":"substitute.vim","4":"substitute.vim","src_id":"3731","5":"3731","creation_date":"1104118128","6":"1104118128"},{"0":"1167","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"substitute.vim","4":"substitute.vim","src_id":"3728","5":"3728","creation_date":"1103968259","6":"1103968259"}]},"1166":{"script_id":"1166","0":"1166","script_name":"Wiked","1":"Wiked","script_type":"utility","2":"utility","summary":"Syntax file for file.wiki","3":"Syntax file for file.wiki","description":"its a plugin for Vim to build a console-wiki with html-export.\r\ni took a wiked and extended it, with thinks i want.\r\n","4":"its a plugin for Vim to build a console-wiki with html-export.\r\ni took a wiked and extended it, with thinks i want.\r\n","install_details":"- tar xzf wiked.tgz  -C ~\/.vim\r\n- cat ~\/.vim\/wikifiletype.vim >>  ~\/.vim\/filetype.vim\r\n- rm ~\/.vim\/wikifiletype.vim\r\n- vim ~\/.vim\/tools\/unknown.wiki\r\n- read sourcecode if you want to change something","5":"- tar xzf wiked.tgz  -C ~\/.vim\r\n- cat ~\/.vim\/wikifiletype.vim >>  ~\/.vim\/filetype.vim\r\n- rm ~\/.vim\/wikifiletype.vim\r\n- vim ~\/.vim\/tools\/unknown.wiki\r\n- read sourcecode if you want to change something","first_name":"Madd","6":"Madd","last_name":"Sauer","7":"Sauer","releases":[{"0":"1166","vim_version":"6.0","1":"6.0","script_version":"1.04beta","2":"1.04beta","version_comment":"Initial upload","3":"Initial upload","package":"wiked.tgz","4":"wiked.tgz","src_id":"3727","5":"3727","creation_date":"1103962706","6":"1103962706"}]},"1165":{"script_id":"1165","0":"1165","script_name":"tolerable.vim","1":"tolerable.vim","script_type":"color scheme","2":"color scheme","summary":"A black-on-white scheme inspired by BBEdit","3":"A black-on-white scheme inspired by BBEdit","description":"This  black-on-white colorscheme uses simple, easily identifiable colors, but shouldn't be too gaudy. The scheme was inspired by BBEdit and other Mac OS text editors that have adopted similar color schemes. Unlike BBEdit, comments are low-contrast, and split boundaries are not too stark.","4":"This  black-on-white colorscheme uses simple, easily identifiable colors, but shouldn't be too gaudy. The scheme was inspired by BBEdit and other Mac OS text editors that have adopted similar color schemes. Unlike BBEdit, comments are low-contrast, and split boundaries are not too stark.","install_details":"","5":"","first_name":"Ian","6":"Ian","last_name":"Langworth","7":"Langworth","releases":[{"0":"1165","vim_version":"6.0","1":"6.0","script_version":"1.1","2":"1.1","version_comment":"Trying to better fulfill my creed of \"no bold\"","3":"Trying to better fulfill my creed of \"no bold\"","package":"tolerable.vim","4":"tolerable.vim","src_id":"3741","5":"3741","creation_date":"1104433092","6":"1104433092"},{"0":"1165","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"tolerable.vim","4":"tolerable.vim","src_id":"3726","5":"3726","creation_date":"1103831197","6":"1103831197"}]},"1164":{"script_id":"1164","0":"1164","script_name":"EditJava","1":"EditJava","script_type":"utility","2":"utility","summary":"lookup source file for classname under cursor","3":"lookup source file for classname under cursor","description":"Place cursor over a java classname and enter the scripts map key sequence (I  map it to \",g\"). The base java file name is <cword> . \".java\" \r\n\r\nFirst if the cursor is over a package classname like 'java.util.Map', then if the cursor is over 'Map', the java\/util\/Map.java file is opened else if the cursor is over, say, 'util', then the java\/util directory is opened. \r\n\r\nOtherwise, the script looks for a file with the filename in local directory and  if it exists, opens it.\r\n\r\nIf not, it looks for an explicit import file with the filename, if it can be found  in the java source path, then it opens it. If not found, use 'locate' command to look for filename plus import package directories prepended. If found then open it.\r\n\r\nIf not, it looks for a file in \"$JAVA_HOME\/src\/java\/lang\" and if found opens it. \r\n\r\nIf not it then looks for a match using any of the implicit import statements, those ending in * and in the java source path. If found open it. Otherwise use 'locate' command to search for filename plus import package path prepended and if found open it.\r\n\r\nLastly, if not found by any of the above methods it then attempts to find a file using the package path. The current file might be in a parallel junit directory or in some parallel directory structure. If this is found in the java source path then it is opened otherwise it uses \"locate' command to search for the file and if found opens it.\r\n\r\nEditJava plus the bufexplorer.vim script, \r\nthe \"edit cwd\" Tip #2:\r\nmap ,d :e <C-R>=expand(\"%:p:h\")<CR><CR>  \r\nand the mapping allowing one to toggle between files\r\nmap gg :e#^M \r\nwith the buffer edit commands (where N is an integer)\r\n:bp\r\n:bpN\r\n:bn\r\n:bpN                         \r\nprovide one with a collection of tools to view and navigate Java sources.\r\n","4":"Place cursor over a java classname and enter the scripts map key sequence (I  map it to \",g\"). The base java file name is <cword> . \".java\" \r\n\r\nFirst if the cursor is over a package classname like 'java.util.Map', then if the cursor is over 'Map', the java\/util\/Map.java file is opened else if the cursor is over, say, 'util', then the java\/util directory is opened. \r\n\r\nOtherwise, the script looks for a file with the filename in local directory and  if it exists, opens it.\r\n\r\nIf not, it looks for an explicit import file with the filename, if it can be found  in the java source path, then it opens it. If not found, use 'locate' command to look for filename plus import package directories prepended. If found then open it.\r\n\r\nIf not, it looks for a file in \"$JAVA_HOME\/src\/java\/lang\" and if found opens it. \r\n\r\nIf not it then looks for a match using any of the implicit import statements, those ending in * and in the java source path. If found open it. Otherwise use 'locate' command to search for filename plus import package path prepended and if found open it.\r\n\r\nLastly, if not found by any of the above methods it then attempts to find a file using the package path. The current file might be in a parallel junit directory or in some parallel directory structure. If this is found in the java source path then it is opened otherwise it uses \"locate' command to search for the file and if found opens it.\r\n\r\nEditJava plus the bufexplorer.vim script, \r\nthe \"edit cwd\" Tip #2:\r\nmap ,d :e <C-R>=expand(\"%:p:h\")<CR><CR>  \r\nand the mapping allowing one to toggle between files\r\nmap gg :e#^M \r\nwith the buffer edit commands (where N is an integer)\r\n:bp\r\n:bpN\r\n:bn\r\n:bpN                         \r\nprovide one with a collection of tools to view and navigate Java sources.\r\n","install_details":"Place script in your vim script directory:\r\n$HOME\/vimscripts\/javae.vim\r\n\r\nAdd the following to your .vimrc file:\r\n\r\n\" Set my Leader character\r\nlet mapleader = \",\"\r\n\r\n\" Source javae.vim\r\nsource $HOME\/vimscripts\/javae.vim\r\n\r\n\" Create a java source path in .vimrc \r\n\" (I currently have 17 source paths in my .vimrc):\r\nlet $JAVASOURCEPATH =\"$JAVA_HOME\/src\" .\r\n  \\\",$HOME\/java\/xerces\/xerces\/src\" .\r\n  \\\",$HOME\/java\/xerces\/xalan\/src\" .\r\n  \\\",$HOME\/java\/jboss\/jboss\" .\r\n  \\\",$HOME\/myproject\/src\/java\"\r\n\r\n\" Creating a mapping to call the script in .vimrc:\r\n\" goto\r\nmap <Leader>g :call EditJava('e',$JAVASOURCEPATH)<CR> \r\n\" open horizontal\r\nmap <Leader>h :call EditJava('sp',$JAVASOURCEPATH)<CR>\r\n\" open vertical\r\nmap <Leader>v :call EditJava('vsp',$JAVASOURCEPATH)<CR>\r\n\r\nDefine behavior\r\nSet g:javae_use_locate_cmd  to 0 if you do not wish to use a 'locate\" command. The default is to use the 'locate' command:\r\nlet g:javae_use_locate_cmd = 1\r\n\r\nSet the name of the 'locate' command. The default value for g:javae_locate_cmd is \"slocate\". If you wish to use a different command put the folloing in your .vimrc:\r\nlet g:javae_locate_cmd = <command_name>\r\n\r\nIf using a 'locate' command, then one can force javae to allways prompt even when there is only one match by setting g:javae_locateopen_alwaysprompt to 1. \r\nThe default is to only prompt when there is more than one file:\r\nlet g:javae_locateopen_alwaysprompt = 0\r\n\r\nAlso, one can set whether or not to get an error message if in response to a prompt an incorrect value is entered. To not see any error messages set g:javae_locateopen_showerror to 0. The default is to see error messages\r\nlet g:javae_locateopen_showerror = 1\r\n\r\nWhen switching to another buffer the current buffer may need to be saved. The g:javae_automatic_update flag allows one to control this behavior. Setting it to 0:\r\nlet g:javae_syntax_based = 0\r\nwill not automatically update the current buffer if it needs to be saved allowing you to automatically see the new buffer, rather you must first manually save the current buffer and re-run the search.\r\nThe default is to allow for automatic updates:\r\nlet g:javae_syntax_based = 1.\r\n\r\nImport statements do not occur after the first class or interface declaration. While searching the current file for all import statements one can either read each line of the current file or stop after the first class or interface declaration. In addition, what looks like an import statement might be in a comment. If the flag g:javae_syntax_based is set to 0:\r\nlet g:javae_syntax_based=0\r\nthen each line in the file is read. \r\nOn the other hand if it is set to 1:\r\nlet g:javae_syntax_based = 1\r\nthe default value, then the search for import statements skips comments and stops after the first class or interface declaration. The reason one might not wish to use the g:javae_syntax_based flag is that under the covers java syntax values are used to determine when one is in a comment or declaration and if the user has modified the default java syntax values found in java.vim, then the syntax base code may not work.\r\n\r\n","5":"Place script in your vim script directory:\r\n$HOME\/vimscripts\/javae.vim\r\n\r\nAdd the following to your .vimrc file:\r\n\r\n\" Set my Leader character\r\nlet mapleader = \",\"\r\n\r\n\" Source javae.vim\r\nsource $HOME\/vimscripts\/javae.vim\r\n\r\n\" Create a java source path in .vimrc \r\n\" (I currently have 17 source paths in my .vimrc):\r\nlet $JAVASOURCEPATH =\"$JAVA_HOME\/src\" .\r\n  \\\",$HOME\/java\/xerces\/xerces\/src\" .\r\n  \\\",$HOME\/java\/xerces\/xalan\/src\" .\r\n  \\\",$HOME\/java\/jboss\/jboss\" .\r\n  \\\",$HOME\/myproject\/src\/java\"\r\n\r\n\" Creating a mapping to call the script in .vimrc:\r\n\" goto\r\nmap <Leader>g :call EditJava('e',$JAVASOURCEPATH)<CR> \r\n\" open horizontal\r\nmap <Leader>h :call EditJava('sp',$JAVASOURCEPATH)<CR>\r\n\" open vertical\r\nmap <Leader>v :call EditJava('vsp',$JAVASOURCEPATH)<CR>\r\n\r\nDefine behavior\r\nSet g:javae_use_locate_cmd  to 0 if you do not wish to use a 'locate\" command. The default is to use the 'locate' command:\r\nlet g:javae_use_locate_cmd = 1\r\n\r\nSet the name of the 'locate' command. The default value for g:javae_locate_cmd is \"slocate\". If you wish to use a different command put the folloing in your .vimrc:\r\nlet g:javae_locate_cmd = <command_name>\r\n\r\nIf using a 'locate' command, then one can force javae to allways prompt even when there is only one match by setting g:javae_locateopen_alwaysprompt to 1. \r\nThe default is to only prompt when there is more than one file:\r\nlet g:javae_locateopen_alwaysprompt = 0\r\n\r\nAlso, one can set whether or not to get an error message if in response to a prompt an incorrect value is entered. To not see any error messages set g:javae_locateopen_showerror to 0. The default is to see error messages\r\nlet g:javae_locateopen_showerror = 1\r\n\r\nWhen switching to another buffer the current buffer may need to be saved. The g:javae_automatic_update flag allows one to control this behavior. Setting it to 0:\r\nlet g:javae_syntax_based = 0\r\nwill not automatically update the current buffer if it needs to be saved allowing you to automatically see the new buffer, rather you must first manually save the current buffer and re-run the search.\r\nThe default is to allow for automatic updates:\r\nlet g:javae_syntax_based = 1.\r\n\r\nImport statements do not occur after the first class or interface declaration. While searching the current file for all import statements one can either read each line of the current file or stop after the first class or interface declaration. In addition, what looks like an import statement might be in a comment. If the flag g:javae_syntax_based is set to 0:\r\nlet g:javae_syntax_based=0\r\nthen each line in the file is read. \r\nOn the other hand if it is set to 1:\r\nlet g:javae_syntax_based = 1\r\nthe default value, then the search for import statements skips comments and stops after the first class or interface declaration. The reason one might not wish to use the g:javae_syntax_based flag is that under the covers java syntax values are used to determine when one is in a comment or declaration and if the user has modified the default java syntax values found in java.vim, then the syntax base code may not work.\r\n\r\n","first_name":"richard","6":"richard","last_name":"emberson","7":"emberson","releases":[{"0":"1164","vim_version":"6.0","1":"6.0","script_version":"1.4","2":"1.4","version_comment":"Now looks a the package path to see if the file being searched for is in a parallel directory structure. Whether or not to automatically save the current buffer, if needed, is controled by a flag. Lastly, java syntax can be used to identify when the first class\/interface declaration has occurred and the search for import statements should stop.","3":"Now looks a the package path to see if the file being searched for is in a parallel directory structure. Whether or not to automatically save the current buffer, if needed, is controled by a flag. Lastly, java syntax can be used to identify when the first class\/interface declaration has occurred and the search for import statements should stop.","package":"javae.vim","4":"javae.vim","src_id":"3796","5":"3796","creation_date":"1106667892","6":"1106667892"},{"0":"1164","vim_version":"6.0","1":"6.0","script_version":"1.3","2":"1.3","version_comment":"Added ability to use the system \"locate\" command to\r\nfind the java file if it can not be located in the java path\r\nexplicitly passed in as a paramenter. Also, fixed a couple\r\nof bugs.","3":"Added ability to use the system \"locate\" command to\r\nfind the java file if it can not be located in the java path\r\nexplicitly passed in as a paramenter. Also, fixed a couple\r\nof bugs.","package":"javae.vim","4":"javae.vim","src_id":"3776","5":"3776","creation_date":"1105958684","6":"1105958684"},{"0":"1164","vim_version":"6.0","1":"6.0","script_version":"1.2","2":"1.2","version_comment":"The entry point function, 'EditJava', now takes a command \r\nargument which is executed if a matching file or directory is \r\nfound. This allows the user to parameterize the call with their \r\nchoice of opening a new window for the source file, e.g., the \r\ncommand can be:\r\ne, vsplit, new, split, vertical, sview, vnew , etc.\r\n\r\nAlso, the 'EditJava' method was refactored.","3":"The entry point function, 'EditJava', now takes a command \r\nargument which is executed if a matching file or directory is \r\nfound. This allows the user to parameterize the call with their \r\nchoice of opening a new window for the source file, e.g., the \r\ncommand can be:\r\ne, vsplit, new, split, vertical, sview, vnew , etc.\r\n\r\nAlso, the 'EditJava' method was refactored.","package":"javae.vim","4":"javae.vim","src_id":"3742","5":"3742","creation_date":"1104737880","6":"1104737880"},{"0":"1164","vim_version":"6.0","1":"6.0","script_version":"1.1","2":"1.1","version_comment":"Now if there is a package path classname such as java.util.Map\r\nin ones code, then with cursor over Map, the Map.java file\r\nis opened and if cursor is over for example 'util' then the\r\njava\/util directory is opened. All of the other means of opening\r\nthe java file under the cursor are still there.","3":"Now if there is a package path classname such as java.util.Map\r\nin ones code, then with cursor over Map, the Map.java file\r\nis opened and if cursor is over for example 'util' then the\r\njava\/util directory is opened. All of the other means of opening\r\nthe java file under the cursor are still there.","package":"javae.vim","4":"javae.vim","src_id":"3733","5":"3733","creation_date":"1104147694","6":"1104147694"},{"0":"1164","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"javae.vim","4":"javae.vim","src_id":"3725","5":"3725","creation_date":"1103812817","6":"1103812817"}]},"1163":{"script_id":"1163","0":"1163","script_name":"html_danish","1":"html_danish","script_type":"utility","2":"utility","summary":"Change danish special characters (\u00c3\u00a6\u00c3\u00b8\u00c3\u00a5) to their html-version and vice versa","3":"Change danish special characters (\u00c3\u00a6\u00c3\u00b8\u00c3\u00a5) to their html-version and vice versa","description":"Useful for people developing Danish (or perhaps Norwegian) websites in HTML or PHP.\r\n\r\nUpon loading a HTML or PHP-file, this script replaces all instances of the HTML entities of the Danish characters (aelig, oslash, aring) with the normal characters (\u00c3\u00a6,\u00c3\u00b8,\u00c3\u00a5) for easy reading.\r\n\r\nUpon saving the normal Danish characters are replaced with the HTML encoded.\r\n\r\nInspired by the html_umlaute: vimscript #907  and the html_portuguese: vimscript #924","4":"Useful for people developing Danish (or perhaps Norwegian) websites in HTML or PHP.\r\n\r\nUpon loading a HTML or PHP-file, this script replaces all instances of the HTML entities of the Danish characters (aelig, oslash, aring) with the normal characters (\u00c3\u00a6,\u00c3\u00b8,\u00c3\u00a5) for easy reading.\r\n\r\nUpon saving the normal Danish characters are replaced with the HTML encoded.\r\n\r\nInspired by the html_umlaute: vimscript #907  and the html_portuguese: vimscript #924","install_details":"put it into vim plugin folder (\/usr\/share\/vim\/vim61\/plugin) or in your ~\/.vim\/plugin\/ folder.","5":"put it into vim plugin folder (\/usr\/share\/vim\/vim61\/plugin) or in your ~\/.vim\/plugin\/ folder.","first_name":"sune","6":"sune","last_name":"vuorela","7":"vuorela","releases":[{"0":"1163","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"html_da.vim","4":"html_da.vim","src_id":"3723","5":"3723","creation_date":"1103733642","6":"1103733642"}]},"1162":{"script_id":"1162","0":"1162","script_name":"jexplorer","1":"jexplorer","script_type":"utility","2":"utility","summary":"package\/class browser for Java.","3":"package\/class browser for Java.","description":"This plugin allows browse Java package system.\r\n\r\nrequirments:\r\n  1. exuberant ctags ( or at least tags file )\r\n  2. grep,sed,uniq - utility ( sorry widnows folk)\r\n  3. maltvals.vim && tree.vim   plugins for vim\r\n  \r\nJExplorer command  opens window with explorer in it.\r\n<SPACE> - pressed on a class or a member will show a prototype of the thing\r\nO  - pressed on a class or a member will try to open file with the tag and take you to the tag (currently it works only for tag files generated with relative paths).\r\ni  - pressed on a packge or  a class will generate import statment.\r\ni  - pressed on a function will import (write an empty function) this function.\r\n     (for last to cases visual selection allowed)\r\n\r\nBUGS and LIMITATION:\r\n    1. currently works only for unix-like systems\r\n    2.  Rather slow: on a 15Mb tag file (jdk src) it take 8s to open defalul package\r\n           for ather packages it is a bit faster (no more then 2s)\r\n    3. opens java files only in case tag file was generated with relative paths.\r\n \r\nWITHOUT YOUR FEEDBACK IT WON'T BE IMPROVED,\r\nso let me know if yuo have some thoughts about it.\r\n\r\n    \r\n","4":"This plugin allows browse Java package system.\r\n\r\nrequirments:\r\n  1. exuberant ctags ( or at least tags file )\r\n  2. grep,sed,uniq - utility ( sorry widnows folk)\r\n  3. maltvals.vim && tree.vim   plugins for vim\r\n  \r\nJExplorer command  opens window with explorer in it.\r\n<SPACE> - pressed on a class or a member will show a prototype of the thing\r\nO  - pressed on a class or a member will try to open file with the tag and take you to the tag (currently it works only for tag files generated with relative paths).\r\ni  - pressed on a packge or  a class will generate import statment.\r\ni  - pressed on a function will import (write an empty function) this function.\r\n     (for last to cases visual selection allowed)\r\n\r\nBUGS and LIMITATION:\r\n    1. currently works only for unix-like systems\r\n    2.  Rather slow: on a 15Mb tag file (jdk src) it take 8s to open defalul package\r\n           for ather packages it is a bit faster (no more then 2s)\r\n    3. opens java files only in case tag file was generated with relative paths.\r\n \r\nWITHOUT YOUR FEEDBACK IT WON'T BE IMPROVED,\r\nso let me know if yuo have some thoughts about it.\r\n\r\n    \r\n","install_details":"1. unpack archive to your vimfile directory (~\/.vim for unix-like systemes) \r\n2. Add paths to tag files to your 'tags' option\r\n       a) set global tags option\r\n       b)  create jexplorer.vim file under \"ftplugin\" directory ( see :h ftplugin) and wite :\r\n            setlocal tags=\/user\/home\/Sonic\/java\/jdksrc\/tags\r\n            this will set tags option locally to a JExplorer buffer.\r\n\r\n","5":"1. unpack archive to your vimfile directory (~\/.vim for unix-like systemes) \r\n2. Add paths to tag files to your 'tags' option\r\n       a) set global tags option\r\n       b)  create jexplorer.vim file under \"ftplugin\" directory ( see :h ftplugin) and wite :\r\n            setlocal tags=\/user\/home\/Sonic\/java\/jdksrc\/tags\r\n            this will set tags option locally to a JExplorer buffer.\r\n\r\n","first_name":"Yury","6":"Yury","last_name":"Altukhou","7":"Altukhou","releases":[{"0":"1162","vim_version":"6.0","1":"6.0","script_version":"0.5beta","2":"0.5beta","version_comment":"Initial upload","3":"Initial upload","package":"jexplorer.zip","4":"jexplorer.zip","src_id":"3721","5":"3721","creation_date":"1103681081","6":"1103681081"}]},"1161":{"script_id":"1161","0":"1161","script_name":"foldcol.vim","1":"foldcol.vim","script_type":"utility","2":"utility","summary":"fold\/unfold by visual-blocks (columns)","3":"fold\/unfold by visual-blocks (columns)","description":"foldcol.vim is a plugin which implements two maps:\r\n\r\nctrl-v move \\fc  : select a visual block, then \\fc will fold the region away\r\n\r\n\\fc : when not in visual-block mode (ie. in normal mode), a \\fc will undo the visual-block folds produced by foldcol.vim.\r\n\r\n(alpha\/beta version available at http:\/\/www.drchip.org\/astronaut\/vim\/index.html#FOLDCOL)\r\n","4":"foldcol.vim is a plugin which implements two maps:\r\n\r\nctrl-v move \\fc  : select a visual block, then \\fc will fold the region away\r\n\r\n\\fc : when not in visual-block mode (ie. in normal mode), a \\fc will undo the visual-block folds produced by foldcol.vim.\r\n\r\n(alpha\/beta version available at http:\/\/www.drchip.org\/astronaut\/vim\/index.html#FOLDCOL)\r\n","install_details":"Put the script into your .vim\/plugin (Windows: vimfiles\\plugin) directory.\r\n\r\nYou'll also need Vince Negri's conceal-ownsyntax patch, which is available at vimscript#302, to apply the patch, and to re-compile vim.  It is hoped that vim 7.0 will already incorporate the conceal-ownsyntax patch, although that hasn't happened yet.\r\n","5":"Put the script into your .vim\/plugin (Windows: vimfiles\\plugin) directory.\r\n\r\nYou'll also need Vince Negri's conceal-ownsyntax patch, which is available at vimscript#302, to apply the patch, and to re-compile vim.  It is hoped that vim 7.0 will already incorporate the conceal-ownsyntax patch, although that hasn't happened yet.\r\n","first_name":"Charles","6":"Charles","last_name":"Campbell","7":"Campbell","releases":[{"0":"1161","vim_version":"6.0","1":"6.0","script_version":"2","2":"2","version_comment":"Initial upload","3":"Initial upload","package":"foldcol.vim.gz","4":"foldcol.vim.gz","src_id":"3720","5":"3720","creation_date":"1103621768","6":"1103621768"}]},"1160":{"script_id":"1160","0":"1160","script_name":"tSkeleton","1":"tSkeleton","script_type":"utility","2":"utility","summary":"File Templates and Code Skeletons\/Snippets","3":"File Templates and Code Skeletons\/Snippets","description":"Demo:\r\nhttp:\/\/vimsomnia.blogspot.com\/2010\/11\/tskeleton-and-stakeholders-vim-plugins.html\r\n\r\nAlso available via git\r\nhttp:\/\/github.com\/tomtom\/tskeleton_vim\r\n\r\nAdditional bits\/snippets:\r\nhttps:\/\/github.com\/tomtom\/tskeletons\r\n\r\ntSkeleton provides file templates and code skeletons (snippets). These \r\ntemplates may contain special tags that are replaced with some computed \r\nvalue (e.g., variables, user input ...), vimscript code, or place \r\nholders\/jump positions (when used in conjunction with imap.vim or \r\n|TSkeletonMapGoToNextTag()|.\r\n\r\n\r\nFile templates:\r\n\r\nIn order to add support for a new filetype, save a skeleton file to \r\n~\/.vim\/skeletons\/file.suffix and add something like this to your .vimrc \r\nfile:\r\n\r\n    autocmd BufNewFile *.suffix       TSkeletonSetup template.suffix\r\n    autocmd BufNewFile \/here\/*.suffix TSkeletonSetup othertemplate.suffix\r\n\r\nAlternatively, you can store templates as:\r\n\r\n    ~\/vimfiles\/skeletons\/templates\/GROUP\/FILETYPE PATTERN\r\n\r\n\r\nCode skeletons:\r\n\r\nSmaller skeleton bits are stored in SKELETONS\/bits\/FILETYPE\/ or \r\nSKELETONS\/bits\/general\/. I.e., code skeletons can be filetype specific \r\nor generally available.\r\n\r\nThe filenames of the bits may be grouped in submenus as in:\r\n\r\n    ..\/tex\/&Define.%5Cnew&command\r\n    ..\/tex\/&Define.%5Cnew&environment\r\n\r\nThis will create skeletons for \\newcommand and \\newenvironment but will \r\ngroup the skeletons under the TSkel.Define. menu with the respective \r\naccelerators.\r\n\r\n\r\nDefault key maps:\r\n\r\n    <Leader>## ... Expand name under cursor\r\n    <Leader>#t ... Insert code skeleton via command line\r\n    <c-\\><c-\\> ... In insert mode, expand the bit before the cursor (on \r\n                   a German keyboard this happens to be <c-#><c-#>)\r\n\r\n\r\nGeneral remarks:\r\n\r\nA list of special tags:\r\n\r\n    <+FILE NAME ROOT+> :: the file name root\r\n    <+FILE NAME+>      :: the file name\r\n    <+FILE SUFFIX+>    :: the file suffix\r\n    <+FILE DIRNAME+>   :: the file's directory\r\n    <+NOTE+>           :: a note\r\n    <+DATE+>           :: the current date (the format is controlled via \r\n                          g:tskelDateFormat)\r\n    <+AUTHOR+>         :: the author's name (g:tskelUserName)\r\n    <+EMAIL+>          :: the author's e-mail (g:tskelUserEmail)\r\n    <+WEBSITE+>        :: the author's homepage (g:tskelUserWWW)\r\n    <+LICENSE+>        :: the name of the license this file is released \r\n                          under (g:tskelLicense)\r\n\r\ntSkeleton also supports the following pseudo-tags:\r\n    <+CURSOR+>         :: where to place the cursor after insertion\r\n    <+&NAME+>          :: a vim option\r\n    <+g:NAME+>         :: a global variable\r\n    <+b:NAME+>         :: a buffer local variable\r\n    <+?QUERY?+>        :: query the user\r\n    <+?VAR|QUERY?+>    :: query the user and propose some choices from \r\n                          the variable ${VAR}\r\n    <+bit:BIT>, <+bit:BIT|\"DEFAULT\">, <+bit:BIT|COMMANDS> :: insert a \r\n                          bit; if the bit isn't defined for the current \r\n                          filetype, use DEFAULT; if DEFAULT matches \".*\" \r\n                          insert it as a string; otherwise interpret it \r\n                          as a command sequence to be fed to normal\r\n    <+tskel:TSKELETON> ... :: same as the above\r\n    <+include(TSKELETON)+> :: Another synonym for the above.\r\n    <+call:FUNCTION(ARGS)+> :: Insert the result value of some function\r\n    <+execute(EX COMMAND)+> :: Run a vim command.\r\n\r\nFlow control:\r\n    <+if(CONDITION)+>\r\n    <+elseif(CONDITION)+>\r\n    <+else+>\r\n    <+endif+>\r\n\r\nLoops:\r\n    <+for(VAR in LIST)+>\r\n    <+endfor+>, <+endfor(VAR)+>\r\n\r\nVariables:\r\n    <+let(VAR=VALUE)+>\r\n\r\nInteraction:\r\n    <+input(VAR, QUERY, [DEFAULT], [COMPLETION])+>\r\n\r\nOther:\r\n    <+nl+>\r\n    <+joinline+>\r\n    <+nop+>\r\n\r\nA wiki like table could then be constructed using a skeleton like this:\r\n\r\n    <+input('s:my_rows?!', 'Rows: ')+>\r\n    <+input('s:my_cols?!', 'Cols: ')+>\r\n    <+for(i in range(s:my_rows))+>\r\n    |<+for(j in range(s:my_cols))+> <+CURSOR+> |<+endfor(j)+><+nop+>\r\n    <+endfor(i)+>\r\n\r\nUnknown tags are kept in the expanded skeleton. These tags can be used \r\nas cursor jump marks. This syntax was originally used by imap (vimscript \r\n#244 or vimscript #475). If you don't want to install imap, you can also  \r\nuse |TSkeletonMapGoToNextTag()|.\r\n\r\nYou can use vimscript #3326 to enhance your templates with dynamic placeholders.\r\n","4":"Demo:\r\nhttp:\/\/vimsomnia.blogspot.com\/2010\/11\/tskeleton-and-stakeholders-vim-plugins.html\r\n\r\nAlso available via git\r\nhttp:\/\/github.com\/tomtom\/tskeleton_vim\r\n\r\nAdditional bits\/snippets:\r\nhttps:\/\/github.com\/tomtom\/tskeletons\r\n\r\ntSkeleton provides file templates and code skeletons (snippets). These \r\ntemplates may contain special tags that are replaced with some computed \r\nvalue (e.g., variables, user input ...), vimscript code, or place \r\nholders\/jump positions (when used in conjunction with imap.vim or \r\n|TSkeletonMapGoToNextTag()|.\r\n\r\n\r\nFile templates:\r\n\r\nIn order to add support for a new filetype, save a skeleton file to \r\n~\/.vim\/skeletons\/file.suffix and add something like this to your .vimrc \r\nfile:\r\n\r\n    autocmd BufNewFile *.suffix       TSkeletonSetup template.suffix\r\n    autocmd BufNewFile \/here\/*.suffix TSkeletonSetup othertemplate.suffix\r\n\r\nAlternatively, you can store templates as:\r\n\r\n    ~\/vimfiles\/skeletons\/templates\/GROUP\/FILETYPE PATTERN\r\n\r\n\r\nCode skeletons:\r\n\r\nSmaller skeleton bits are stored in SKELETONS\/bits\/FILETYPE\/ or \r\nSKELETONS\/bits\/general\/. I.e., code skeletons can be filetype specific \r\nor generally available.\r\n\r\nThe filenames of the bits may be grouped in submenus as in:\r\n\r\n    ..\/tex\/&Define.%5Cnew&command\r\n    ..\/tex\/&Define.%5Cnew&environment\r\n\r\nThis will create skeletons for \\newcommand and \\newenvironment but will \r\ngroup the skeletons under the TSkel.Define. menu with the respective \r\naccelerators.\r\n\r\n\r\nDefault key maps:\r\n\r\n    <Leader>## ... Expand name under cursor\r\n    <Leader>#t ... Insert code skeleton via command line\r\n    <c-\\><c-\\> ... In insert mode, expand the bit before the cursor (on \r\n                   a German keyboard this happens to be <c-#><c-#>)\r\n\r\n\r\nGeneral remarks:\r\n\r\nA list of special tags:\r\n\r\n    <+FILE NAME ROOT+> :: the file name root\r\n    <+FILE NAME+>      :: the file name\r\n    <+FILE SUFFIX+>    :: the file suffix\r\n    <+FILE DIRNAME+>   :: the file's directory\r\n    <+NOTE+>           :: a note\r\n    <+DATE+>           :: the current date (the format is controlled via \r\n                          g:tskelDateFormat)\r\n    <+AUTHOR+>         :: the author's name (g:tskelUserName)\r\n    <+EMAIL+>          :: the author's e-mail (g:tskelUserEmail)\r\n    <+WEBSITE+>        :: the author's homepage (g:tskelUserWWW)\r\n    <+LICENSE+>        :: the name of the license this file is released \r\n                          under (g:tskelLicense)\r\n\r\ntSkeleton also supports the following pseudo-tags:\r\n    <+CURSOR+>         :: where to place the cursor after insertion\r\n    <+&NAME+>          :: a vim option\r\n    <+g:NAME+>         :: a global variable\r\n    <+b:NAME+>         :: a buffer local variable\r\n    <+?QUERY?+>        :: query the user\r\n    <+?VAR|QUERY?+>    :: query the user and propose some choices from \r\n                          the variable ${VAR}\r\n    <+bit:BIT>, <+bit:BIT|\"DEFAULT\">, <+bit:BIT|COMMANDS> :: insert a \r\n                          bit; if the bit isn't defined for the current \r\n                          filetype, use DEFAULT; if DEFAULT matches \".*\" \r\n                          insert it as a string; otherwise interpret it \r\n                          as a command sequence to be fed to normal\r\n    <+tskel:TSKELETON> ... :: same as the above\r\n    <+include(TSKELETON)+> :: Another synonym for the above.\r\n    <+call:FUNCTION(ARGS)+> :: Insert the result value of some function\r\n    <+execute(EX COMMAND)+> :: Run a vim command.\r\n\r\nFlow control:\r\n    <+if(CONDITION)+>\r\n    <+elseif(CONDITION)+>\r\n    <+else+>\r\n    <+endif+>\r\n\r\nLoops:\r\n    <+for(VAR in LIST)+>\r\n    <+endfor+>, <+endfor(VAR)+>\r\n\r\nVariables:\r\n    <+let(VAR=VALUE)+>\r\n\r\nInteraction:\r\n    <+input(VAR, QUERY, [DEFAULT], [COMPLETION])+>\r\n\r\nOther:\r\n    <+nl+>\r\n    <+joinline+>\r\n    <+nop+>\r\n\r\nA wiki like table could then be constructed using a skeleton like this:\r\n\r\n    <+input('s:my_rows?!', 'Rows: ')+>\r\n    <+input('s:my_cols?!', 'Cols: ')+>\r\n    <+for(i in range(s:my_rows))+>\r\n    |<+for(j in range(s:my_cols))+> <+CURSOR+> |<+endfor(j)+><+nop+>\r\n    <+endfor(i)+>\r\n\r\nUnknown tags are kept in the expanded skeleton. These tags can be used \r\nas cursor jump marks. This syntax was originally used by imap (vimscript \r\n#244 or vimscript #475). If you don't want to install imap, you can also  \r\nuse |TSkeletonMapGoToNextTag()|.\r\n\r\nYou can use vimscript #3326 to enhance your templates with dynamic placeholders.\r\n","install_details":"This script requires tlib (vimscript #1863).\r\n\r\nEdit the vba file and type:\r\n\r\n    :so %\r\n\r\nSee :help vimball for details. If you use vim 7.0, you probably need to \r\nupdate vimball (vimscript #1502) first.\r\n\r\nIMPORTANT: When updating from an older version, please remove the cache \r\nfiles in ~\/vimfiles\/cache\/tskel_*\/** (or select \"Reset\" from the menu) \r\nand (if existent) the directories ~\/vimfiles\/skeletons\/menu, \r\n~\/vimfiles\/skeletons\/bbits.\r\n\r\n\r\nIf you don't already have some skeletons, you may want to download \r\nthe file tSkeleton-Samples.zip from the list below.\r\n\r\n\r\nThe files are stored in ~\/vimfiles\/skeletons or ~\/.vim\/skeletons (see \r\ng:tskelDir). The directory structure should look like this:\r\n\r\n    skeletons\/\r\n        NAME.SUFFIX (templates for new files)\r\n        templates\/\r\n            GROUP\/ (templates for new files)\r\n                FILETYPE PATTERN.SUFFIX\r\n        map\/\r\n            FILETYPE (map files for conditional expansion)\r\n        bits\/\r\n            FILETYPE.txt (single line templates)\r\n            general\/\r\n                GENERAL CODE SKELETONS ...\r\n            FILETYPE\/\r\n                FILETYPE SPECIFIC CODE SKELETONS: ONE SKELETON PER FILE ...\r\n\r\n\r\nYou might want to use imaps.vim's (vimscript #244 or vimscript #475) place \r\nholders in conjunction with this plugin..\r\n\r\n\r\nIf you don't use imaps.vim, you can :call TSkeletonMapGoToNextTag(). \r\nLike imaps, this will map <c-j> to a function that makes the cursor jump \r\nto the next tag.\r\n\r\n\r\nATTENTION:\r\n\r\nIf you had an older version (pre 4.0) installed, you might also want to \r\nremove the older cache directories in ~\/.vim\/skeletons\/ (eg menu, \r\nbbits).\r\n\r\nIf you add a new skeleton or template, you'll also have to do \r\n:TSkeletonBitReset to make the plugin rescan the source directory.\r\n\r\nIf you update from 1.0, be aware that the default \"markup\" for place \r\nholders has changed.\r\n\r\ntSkeleton up to 2.1 is not compatible with vim7 up to patch 8. You need \r\nat least vim 7.0.08 to use this plugin. For windows, current executables \r\nincluding patches can be downloaded from the cream website.\r\n\r\ntSkeleton 3 can cause an unpatched vim7 to crash. I'm not sure about \r\nthat though. If this happens to you, please update (vim) to a more \r\nrecent version.\r\n","5":"This script requires tlib (vimscript #1863).\r\n\r\nEdit the vba file and type:\r\n\r\n    :so %\r\n\r\nSee :help vimball for details. If you use vim 7.0, you probably need to \r\nupdate vimball (vimscript #1502) first.\r\n\r\nIMPORTANT: When updating from an older version, please remove the cache \r\nfiles in ~\/vimfiles\/cache\/tskel_*\/** (or select \"Reset\" from the menu) \r\nand (if existent) the directories ~\/vimfiles\/skeletons\/menu, \r\n~\/vimfiles\/skeletons\/bbits.\r\n\r\n\r\nIf you don't already have some skeletons, you may want to download \r\nthe file tSkeleton-Samples.zip from the list below.\r\n\r\n\r\nThe files are stored in ~\/vimfiles\/skeletons or ~\/.vim\/skeletons (see \r\ng:tskelDir). The directory structure should look like this:\r\n\r\n    skeletons\/\r\n        NAME.SUFFIX (templates for new files)\r\n        templates\/\r\n            GROUP\/ (templates for new files)\r\n                FILETYPE PATTERN.SUFFIX\r\n        map\/\r\n            FILETYPE (map files for conditional expansion)\r\n        bits\/\r\n            FILETYPE.txt (single line templates)\r\n            general\/\r\n                GENERAL CODE SKELETONS ...\r\n            FILETYPE\/\r\n                FILETYPE SPECIFIC CODE SKELETONS: ONE SKELETON PER FILE ...\r\n\r\n\r\nYou might want to use imaps.vim's (vimscript #244 or vimscript #475) place \r\nholders in conjunction with this plugin..\r\n\r\n\r\nIf you don't use imaps.vim, you can :call TSkeletonMapGoToNextTag(). \r\nLike imaps, this will map <c-j> to a function that makes the cursor jump \r\nto the next tag.\r\n\r\n\r\nATTENTION:\r\n\r\nIf you had an older version (pre 4.0) installed, you might also want to \r\nremove the older cache directories in ~\/.vim\/skeletons\/ (eg menu, \r\nbbits).\r\n\r\nIf you add a new skeleton or template, you'll also have to do \r\n:TSkeletonBitReset to make the plugin rescan the source directory.\r\n\r\nIf you update from 1.0, be aware that the default \"markup\" for place \r\nholders has changed.\r\n\r\ntSkeleton up to 2.1 is not compatible with vim7 up to patch 8. You need \r\nat least vim 7.0.08 to use this plugin. For windows, current executables \r\nincluding patches can be downloaded from the cream website.\r\n\r\ntSkeleton 3 can cause an unpatched vim7 to crash. I'm not sure about \r\nthat though. If this happens to you, please update (vim) to a more \r\nrecent version.\r\n","first_name":"Tom","6":"Tom","last_name":"Link","7":"Link","releases":[{"0":"1160","vim_version":"7.0","1":"7.0","script_version":"5.02","2":"5.02","version_comment":"- Check version of stakeholders if g:tskeleton#enable_stakeholders is true.\nMD5 checksum: c7f28770f5153dd8b072d9fd2b1308ef","3":"- Check version of stakeholders if g:tskeleton#enable_stakeholders is true.\nMD5 checksum: c7f28770f5153dd8b072d9fd2b1308ef","package":"tskeleton.vba","4":"tskeleton.vba","src_id":"22104","5":"22104","creation_date":"1403976232","6":"1403976232"},{"0":"1160","vim_version":"7.0","1":"7.0","script_version":"5.01","2":"5.01","version_comment":"- Help template\n- TSkeletonSetup: Optional bang (always fill in buffer)\n- FIX #9: TSkeletonSetup: <q-args> doesn't require escaping whitespace\n- FIX #10: RetrieveBit: Chomp at most one newline (require tlib 1.10)\n- FIX #11: Don't include :HiLink in doc\nMD5 checksum: 40554c506d28c41491f3e219301829d8","3":"- Help template\n- TSkeletonSetup: Optional bang (always fill in buffer)\n- FIX #9: TSkeletonSetup: <q-args> doesn't require escaping whitespace\n- FIX #10: RetrieveBit: Chomp at most one newline (require tlib 1.10)\n- FIX #11: Don't include :HiLink in doc\nMD5 checksum: 40554c506d28c41491f3e219301829d8","package":"tskeleton.vba","4":"tskeleton.vba","src_id":"22099","5":"22099","creation_date":"1403894278","6":"1403894278"},{"0":"1160","vim_version":"7.0","1":"7.0","script_version":"5.00","2":"5.00","version_comment":"- Fix mysterious border case: Expansion after < in viki mode\n- Support for $ENVIRONMENT_VARIABLES\n- tskeleton#FillIn(): Make sure folding is disabled when expanding tags\n- g:tskelNewBufferIsDirty: Optionally, mark new files from templates as modified\n- g:tskelNewBufferIsDirty: Set based on the value of &hidden\n- Adding user setting for a \"COMPANY\" tag.\n- Call TSkeletonMapGoToNextTag() if g:tskelMapGoToNextTag\n- The expansion of <\/name> type of tags was inserted at the wrong column\n- tskeleton#Placeholders(): Make sure filetype is not empty\n- Echo v:exception when catching errors\n- Experimental: Also cache parsed bits\/minibits\n- Experimental: partial support for snippets (\u00c3\u00a0 la snipMate)\n- Allow 0-9 in place holders\n- Use g:snippets_dir if set\n- snippets: slightly improved parsing\n- Improved support for snippets\n- g:tskelBitsDir is a path now (comma-separated list)\n- tskeleton#GoToNextTag(): support for numbered place holders\n- FIX: Escape menu items\n- FIX: tskeleton#FetchMiniBits(): undefined a:filename (after previous commit)\n- New defaults: enable snippets; enable stakeholders if loaded; enable g:tskelMapGoToNextTag\n- Move tskeleton#ProcessTag_functions_with_parentheses() to tags.vim\n- tskeleton#functions#FiletypeBits_vim(): Don't add items to menu\n- snippets: Put snippets in Snippets submenu\n- skeleton#GetDestBuffer(); postprocess attribute for bits => make snippet's `...` syntax work\n- Setup stakeholders right after inserting the snippet in the destination buffer\n- Replace g:tskelBitsDir with g:tskelGlobalBitsPath and g:tskelLocalBitsDirs (skeletons can be directory\/project local)\n- g:tskelMapGoToNextTag is a key\/map now\n- g:tskeleton#max_basename: Remove len of the cache dir name from the max filesize\n- FIX: Unknown variable r\n- tskeleton#TagRx(): better support for embedded strings\n- duplicate help tags (fixes #6)\n- addon-info\n- tskeleton#EditBit(): Re-enable editing non-existing bits\n- tskeleton#EditBit(): reset bit defs for correct filetype\n- tskeleton#GoToNextTag(): correct selection if &sel != exclusive (fixes #7)\n- tskeleton#FillIn(): Ensure &sel is \"exclusive\" (fixes #8)\nMD5 checksum: a87f571652f29bd910cb47fb91153094","3":"- Fix mysterious border case: Expansion after < in viki mode\n- Support for $ENVIRONMENT_VARIABLES\n- tskeleton#FillIn(): Make sure folding is disabled when expanding tags\n- g:tskelNewBufferIsDirty: Optionally, mark new files from templates as modified\n- g:tskelNewBufferIsDirty: Set based on the value of &hidden\n- Adding user setting for a \"COMPANY\" tag.\n- Call TSkeletonMapGoToNextTag() if g:tskelMapGoToNextTag\n- The expansion of <\/name> type of tags was inserted at the wrong column\n- tskeleton#Placeholders(): Make sure filetype is not empty\n- Echo v:exception when catching errors\n- Experimental: Also cache parsed bits\/minibits\n- Experimental: partial support for snippets (\u00c3\u00a0 la snipMate)\n- Allow 0-9 in place holders\n- Use g:snippets_dir if set\n- snippets: slightly improved parsing\n- Improved support for snippets\n- g:tskelBitsDir is a path now (comma-separated list)\n- tskeleton#GoToNextTag(): support for numbered place holders\n- FIX: Escape menu items\n- FIX: tskeleton#FetchMiniBits(): undefined a:filename (after previous commit)\n- New defaults: enable snippets; enable stakeholders if loaded; enable g:tskelMapGoToNextTag\n- Move tskeleton#ProcessTag_functions_with_parentheses() to tags.vim\n- tskeleton#functions#FiletypeBits_vim(): Don't add items to menu\n- snippets: Put snippets in Snippets submenu\n- skeleton#GetDestBuffer(); postprocess attribute for bits => make snippet's `...` syntax work\n- Setup stakeholders right after inserting the snippet in the destination buffer\n- Replace g:tskelBitsDir with g:tskelGlobalBitsPath and g:tskelLocalBitsDirs (skeletons can be directory\/project local)\n- g:tskelMapGoToNextTag is a key\/map now\n- g:tskeleton#max_basename: Remove len of the cache dir name from the max filesize\n- FIX: Unknown variable r\n- tskeleton#TagRx(): better support for embedded strings\n- duplicate help tags (fixes #6)\n- addon-info\n- tskeleton#EditBit(): Re-enable editing non-existing bits\n- tskeleton#EditBit(): reset bit defs for correct filetype\n- tskeleton#GoToNextTag(): correct selection if &sel != exclusive (fixes #7)\n- tskeleton#FillIn(): Ensure &sel is \"exclusive\" (fixes #8)\nMD5 checksum: a87f571652f29bd910cb47fb91153094","package":"tskeleton.vba","4":"tskeleton.vba","src_id":"20692","5":"20692","creation_date":"1377022181","6":"1377022181"},{"0":"1160","vim_version":"7.0","1":"7.0","script_version":"4.13","2":"4.13","version_comment":"- g:tskeleton#conceal_cchar: Conceal placeholders\n- Use noautocmd\n- Call tskeleton#PrepareBits() on FileType events\n- debug\n- s:EvalBitProcess(): Remove whole line comments (i.e. tskel:before\/after sections may contain comments)\n- Add TSkelPlaceHolder to all syntax clusters\n- s:Eol(): No special treatment for insertmode\n- Cache syntax clusters\nMD5 checksum: c484c1da8c23e9abe02dde370cd094a1","3":"- g:tskeleton#conceal_cchar: Conceal placeholders\n- Use noautocmd\n- Call tskeleton#PrepareBits() on FileType events\n- debug\n- s:EvalBitProcess(): Remove whole line comments (i.e. tskel:before\/after sections may contain comments)\n- Add TSkelPlaceHolder to all syntax clusters\n- s:Eol(): No special treatment for insertmode\n- Cache syntax clusters\nMD5 checksum: c484c1da8c23e9abe02dde370cd094a1","package":"tskeleton.vba","4":"tskeleton.vba","src_id":"17416","5":"17416","creation_date":"1328794856","6":"1328794856"},{"0":"1160","vim_version":"7.0","1":"7.0","script_version":"4.12","2":"4.12","version_comment":"- C modifier in place holders prevented parsing of subsequent modifiers (fix #3)\n- skeletons\/README\nMD5 checksum: 8d2aefc5b25058d211c1f427fc564bec","3":"- C modifier in place holders prevented parsing of subsequent modifiers (fix #3)\n- skeletons\/README\nMD5 checksum: 8d2aefc5b25058d211c1f427fc564bec","package":"tskeleton.vba","4":"tskeleton.vba","src_id":"17076","5":"17076","creation_date":"1324111089","6":"1324111089"},{"0":"1160","vim_version":"7.0","1":"7.0","script_version":"4.11","2":"4.11","version_comment":"- .gitignore\n- Don't assume users have the set of standard templates installed (distributed separatedly)\nMD5 checksum: b3f679c5dd30e9baca8965605ce4b364","3":"- .gitignore\n- Don't assume users have the set of standard templates installed (distributed separatedly)\nMD5 checksum: b3f679c5dd30e9baca8965605ce4b364","package":"tskeleton.vba","4":"tskeleton.vba","src_id":"15993","5":"15993","creation_date":"1309200648","6":"1309200648"},{"0":"1160","vim_version":"7.0","1":"7.0","script_version":"4.10","2":"4.10","version_comment":"- Improved integration with stakeholders.vim\n- s:SelectTagMode(): CursorSet() should respect value of g:tskelSelectTagMode\n- tskeleton#GoToNextTag(): Missed last character for <++> tags if &sel wasn't \"exclusive\"\n- FIX: further &selection-related issues\nMD5 checksum: d126a6069b3d4452c0402f3db12286a0","3":"- Improved integration with stakeholders.vim\n- s:SelectTagMode(): CursorSet() should respect value of g:tskelSelectTagMode\n- tskeleton#GoToNextTag(): Missed last character for <++> tags if &sel wasn't \"exclusive\"\n- FIX: further &selection-related issues\nMD5 checksum: d126a6069b3d4452c0402f3db12286a0","package":"tskeleton.vba","4":"tskeleton.vba","src_id":"14266","5":"14266","creation_date":"1289811271","6":"1289811271"},{"0":"1160","vim_version":"7.0","1":"7.0","script_version":"4.9","2":"4.9","version_comment":"- CHANGE: Renamed plugin\/tSkeleton.vim to plugin\/tskeleton.vim\r\n- CHANGE: Moved the definition of some variables from plugin\/tSkeleton.vim to autoload\/tskeleton.vim\r\n- If g:tskelMapLeader is empty, don't define maps.\r\n- Don't build a menu if g:tskelMenuPrefix == ''.\r\n- If g:tskelDontSetup is defined and g:tskelMenuPrefix == '', autoload\/tskeleton.vim won't be loaded on startup.\r\n- Don't create g:tskelBitsDir if it doesn't exist\r\n- \"Mini bits\": Load all .tskelmini files from the current file's  directory upwards\r\n- s:InsertDefault handles <+CURSOR+> tags\r\n- tskeleton#HyperComplete_query(): Set w:tskeleton_hypercomplete\r\n- FIX: g:tskelHyperType = \"pum\" didn't work properly.\r\n","3":"- CHANGE: Renamed plugin\/tSkeleton.vim to plugin\/tskeleton.vim\r\n- CHANGE: Moved the definition of some variables from plugin\/tSkeleton.vim to autoload\/tskeleton.vim\r\n- If g:tskelMapLeader is empty, don't define maps.\r\n- Don't build a menu if g:tskelMenuPrefix == ''.\r\n- If g:tskelDontSetup is defined and g:tskelMenuPrefix == '', autoload\/tskeleton.vim won't be loaded on startup.\r\n- Don't create g:tskelBitsDir if it doesn't exist\r\n- \"Mini bits\": Load all .tskelmini files from the current file's  directory upwards\r\n- s:InsertDefault handles <+CURSOR+> tags\r\n- tskeleton#HyperComplete_query(): Set w:tskeleton_hypercomplete\r\n- FIX: g:tskelHyperType = \"pum\" didn't work properly.\r\n","package":"tskeleton.vba","4":"tskeleton.vba","src_id":"13833","5":"13833","creation_date":"1284493238","6":"1284493238"},{"0":"1160","vim_version":"7.0","1":"7.0","script_version":"4.7","2":"4.7","version_comment":"- TSkeletonMapHyperComplete() (default: <c-space>): Map a magic key that expands skeletons or, if no matching templates were found, completions, tags, words etc.\r\n- Minibits: Allow single words as bit definition: \"word\" expands to \"word<+CURSOR+>\"\r\n- TSkeletonSetup: allow full filenames as argument\r\n- Auto templates: don't cd into the templates directory\r\n- tskeleton#ExpandBitUnderCursor(): Third argument is a dictionary.\r\n- FIX: Problem with <+name\/expandsion+> kind of tags when located at the beginning or end of a line\r\n- s:GetBitDefs()\r\n- Improved tskeleton#Complete() (for use as completefunc or omnifunc)\r\n- FIX: Cursor positioning after expanding templates without a <+CURSOR+> tag\r\n- Don't build the menu for tSkeleton scratch buffers\r\n- Require tlib 0.29\r\n","3":"- TSkeletonMapHyperComplete() (default: <c-space>): Map a magic key that expands skeletons or, if no matching templates were found, completions, tags, words etc.\r\n- Minibits: Allow single words as bit definition: \"word\" expands to \"word<+CURSOR+>\"\r\n- TSkeletonSetup: allow full filenames as argument\r\n- Auto templates: don't cd into the templates directory\r\n- tskeleton#ExpandBitUnderCursor(): Third argument is a dictionary.\r\n- FIX: Problem with <+name\/expandsion+> kind of tags when located at the beginning or end of a line\r\n- s:GetBitDefs()\r\n- Improved tskeleton#Complete() (for use as completefunc or omnifunc)\r\n- FIX: Cursor positioning after expanding templates without a <+CURSOR+> tag\r\n- Don't build the menu for tSkeleton scratch buffers\r\n- Require tlib 0.29\r\n","package":"tSkeleton.vba.gz","4":"tSkeleton.vba.gz","src_id":"11545","5":"11545","creation_date":"1255877693","6":"1255877693"},{"0":"1160","vim_version":"7.0","1":"7.0","script_version":"4.5","2":"4.5","version_comment":"- Make sure tlib is loaded even if it is installed in a different rtp-directory\r\n- Call s:InitBufferMenu() earlier.\r\n- C modifier: Consider _ whitespace\r\n- g:tskelMarkerExtra (extra markers for tskeleton#GoToNextTag)\r\n","3":"- Make sure tlib is loaded even if it is installed in a different rtp-directory\r\n- Call s:InitBufferMenu() earlier.\r\n- C modifier: Consider _ whitespace\r\n- g:tskelMarkerExtra (extra markers for tskeleton#GoToNextTag)\r\n","package":"tSkeleton.vba.gz","4":"tSkeleton.vba.gz","src_id":"9595","5":"9595","creation_date":"1228209398","6":"1228209398"},{"0":"1160","vim_version":"7.0","1":"7.0","script_version":"4.3","2":"4.3","version_comment":"- bbcode group\r\n- tskelKeyword_{&ft} and tskelGroup_{&ft} variables can be buffer-local\r\n- Case-sensitivity can be configured via [bg]:tskelCaseSensitive and \r\n[bg]:tskelCaseSensitive_{&filetype}\r\n","3":"- bbcode group\r\n- tskelKeyword_{&ft} and tskelGroup_{&ft} variables can be buffer-local\r\n- Case-sensitivity can be configured via [bg]:tskelCaseSensitive and \r\n[bg]:tskelCaseSensitive_{&filetype}\r\n","package":"tSkeleton.vba.gz","4":"tSkeleton.vba.gz","src_id":"8126","5":"8126","creation_date":"1199504402","6":"1199504402"},{"0":"1160","vim_version":"7.0","1":"7.0","script_version":"4.2","2":"4.2","version_comment":"- Enable <+CURSOR\/foo+>. After expansion \"foo\" will be selected.\r\n- New (old) default values: removed 'abbreviations' from g:tskelTypes \r\nand set g:tskelAutoAbbrevs to 0 in order to minimize surprises.\r\n- Enabled tex-Skeletons for the viki filetype\r\n- FIX: Place the cursor at the end of an inserted bit that contains no \r\ncursor marker (which was the original behaviour).\r\n- Split html bits into html and html_common; the java group includes \r\nhtml_common.\r\n- CHANGE: Made bit names case-sensitive\r\n- NEW: select() tag (similar to the query tag)\r\n","3":"- Enable <+CURSOR\/foo+>. After expansion \"foo\" will be selected.\r\n- New (old) default values: removed 'abbreviations' from g:tskelTypes \r\nand set g:tskelAutoAbbrevs to 0 in order to minimize surprises.\r\n- Enabled tex-Skeletons for the viki filetype\r\n- FIX: Place the cursor at the end of an inserted bit that contains no \r\ncursor marker (which was the original behaviour).\r\n- Split html bits into html and html_common; the java group includes \r\nhtml_common.\r\n- CHANGE: Made bit names case-sensitive\r\n- NEW: select() tag (similar to the query tag)\r\n","package":"tSkeleton.vba.gz","4":"tSkeleton.vba.gz","src_id":"7941","5":"7941","creation_date":"1194863528","6":"1194863528"},{"0":"1160","vim_version":"7.0","1":"7.0","script_version":"4.1","2":"4.1","version_comment":"- Automatically define iabbreviations by adding [bg]:tskelAbbrevPostfix \r\n(default: '#') to the bit name (i.e., a bit with the file \"foo.bar\" will \r\nby default create the menu entry \"TSkel.foo.bar\" for the bit \"bar\" and \r\nthe abbreviation \"bar#\"). If this causes problems, set \r\ng:tskelAutoAbbrevs to 0.\r\n- Bits can have a <tskel:abbrev> section that defines the abbreviation.\r\n- New type 'abbreviations': This will make your abbreviations accessible \r\nas templates (in case you can't remember their names)\r\n- New experimental <tskel:condition> section (a vim expression) that \r\nchecks if a bit is eligible in the current context.\r\n- New <+input()+> tag.\r\n- New <+execute()+> tag.\r\n- New <+let(VAR=VALUE)+> tag.\r\n- <+include(NAME)+> as synonym for <+bit:NAME+>.\r\n- Experimental <+if()+> ... <+elseif()+> ... <+else+> ... <+endif+>, \r\n<+for(var in list)+> ... <+endfor+> tags.\r\n- Special tags <+nop+>, <+joinline+>, <+nl+> to prevent certain \r\nproblems.\r\n- These special tags have to be lower case.\r\n- Made tskeleton#GoToNextTag() smarter in recognizing something like: \r\n<+\/DEFAULT+>.\r\n- Defined <Leader>## and <Leader>#<space> (see g:tskelMapLeader) as \r\nvisual command (the user will be queried for the name of a skeleton)\r\n- Some functions have moved and changed names. It should now be possible \r\nto plug-in custom template expanders (or re-use others).\r\n- Use append() via tlib#buffer#InsertText() to insert bits. This could \r\ncause old problems to reappear although it seems to work fine.\r\n- The markup should now be properly configurable (per buffer; you can \r\nset template-specific markers in the tskel:here_before section).\r\n- Require tlib 0.14\r\n- The default value for g:tskelUseBufferCache is 0 as many people might \r\nfind the accumulation of cached information somewhat surprising. Unless \r\nyou use tag\/functions type of skeleton bit, it's unnecessary anyway.\r\n- Removed the dependency on genutils.\r\n- The g:tskelMarkerCursor variable was removed and replaced with \r\ng:tskelMarkerCursor_mark and g:tskelMarkerCursor_rx.\r\n","3":"- Automatically define iabbreviations by adding [bg]:tskelAbbrevPostfix \r\n(default: '#') to the bit name (i.e., a bit with the file \"foo.bar\" will \r\nby default create the menu entry \"TSkel.foo.bar\" for the bit \"bar\" and \r\nthe abbreviation \"bar#\"). If this causes problems, set \r\ng:tskelAutoAbbrevs to 0.\r\n- Bits can have a <tskel:abbrev> section that defines the abbreviation.\r\n- New type 'abbreviations': This will make your abbreviations accessible \r\nas templates (in case you can't remember their names)\r\n- New experimental <tskel:condition> section (a vim expression) that \r\nchecks if a bit is eligible in the current context.\r\n- New <+input()+> tag.\r\n- New <+execute()+> tag.\r\n- New <+let(VAR=VALUE)+> tag.\r\n- <+include(NAME)+> as synonym for <+bit:NAME+>.\r\n- Experimental <+if()+> ... <+elseif()+> ... <+else+> ... <+endif+>, \r\n<+for(var in list)+> ... <+endfor+> tags.\r\n- Special tags <+nop+>, <+joinline+>, <+nl+> to prevent certain \r\nproblems.\r\n- These special tags have to be lower case.\r\n- Made tskeleton#GoToNextTag() smarter in recognizing something like: \r\n<+\/DEFAULT+>.\r\n- Defined <Leader>## and <Leader>#<space> (see g:tskelMapLeader) as \r\nvisual command (the user will be queried for the name of a skeleton)\r\n- Some functions have moved and changed names. It should now be possible \r\nto plug-in custom template expanders (or re-use others).\r\n- Use append() via tlib#buffer#InsertText() to insert bits. This could \r\ncause old problems to reappear although it seems to work fine.\r\n- The markup should now be properly configurable (per buffer; you can \r\nset template-specific markers in the tskel:here_before section).\r\n- Require tlib 0.14\r\n- The default value for g:tskelUseBufferCache is 0 as many people might \r\nfind the accumulation of cached information somewhat surprising. Unless \r\nyou use tag\/functions type of skeleton bit, it's unnecessary anyway.\r\n- Removed the dependency on genutils.\r\n- The g:tskelMarkerCursor variable was removed and replaced with \r\ng:tskelMarkerCursor_mark and g:tskelMarkerCursor_rx.\r\n","package":"tSkeleton.vba.gz","4":"tSkeleton.vba.gz","src_id":"7696","5":"7696","creation_date":"1190201070","6":"1190201070"},{"0":"1160","vim_version":"7.0","1":"7.0","script_version":"4.0","2":"4.0","version_comment":"- Renamed g:tskelPattern* variables to g:tskelMarker*\r\n- If g:tskelMarkerHiGroup is non-empty, place holders will be \r\nhighlighted in this group.\r\n- Re-enable 'mini' in g:tskelTypes.\r\n- Calling TSkeletonBit with no argument, brings up the menu.\r\n- Require tlib 0.12\r\n- CHANGE: The cache is now stored in ~\/vimfiles\/cache\/ (use \r\ntlib#cache#Filename)\r\n- INCOMPATIBLE CHANGE: Use autoload\/tskeleton.vim\r\n- FIX: Problem with cache name\r\n- FIX: Problem in s:IsDefined()\r\n- FIX: TSkeletonEditBit completion didn't work before expanding a bit.\r\n- FIX: Command-line completion when tSkeleton wasn't invoked yet (and \r\nmenu wasn't built).\r\n","3":"- Renamed g:tskelPattern* variables to g:tskelMarker*\r\n- If g:tskelMarkerHiGroup is non-empty, place holders will be \r\nhighlighted in this group.\r\n- Re-enable 'mini' in g:tskelTypes.\r\n- Calling TSkeletonBit with no argument, brings up the menu.\r\n- Require tlib 0.12\r\n- CHANGE: The cache is now stored in ~\/vimfiles\/cache\/ (use \r\ntlib#cache#Filename)\r\n- INCOMPATIBLE CHANGE: Use autoload\/tskeleton.vim\r\n- FIX: Problem with cache name\r\n- FIX: Problem in s:IsDefined()\r\n- FIX: TSkeletonEditBit completion didn't work before expanding a bit.\r\n- FIX: Command-line completion when tSkeleton wasn't invoked yet (and \r\nmenu wasn't built).\r\n","package":"tSkeleton.vba.gz","4":"tSkeleton.vba.gz","src_id":"7633","5":"7633","creation_date":"1189226312","6":"1189226312"},{"0":"1160","vim_version":"7.0","1":"7.0","script_version":"3.5","2":"3.5","version_comment":"- FIX: Minor problem with auto-templates\r\n","3":"- FIX: Minor problem with auto-templates\r\n","package":"tSkeleton.vba.gz","4":"tSkeleton.vba.gz","src_id":"7379","5":"7379","creation_date":"1184753120","6":"1184753120"},{"0":"1160","vim_version":"7.0","1":"7.0","script_version":"3.4","2":"3.4","version_comment":"- Automatically reset bits information after editing a bit.\r\n- Automatically define autocommands for templates with the form \"NAME \r\nPATTERN\" (where \"#\" in the pattern is replaced with \"*\"), i.e. the \r\ntemplate file \"text #%2ffoo%2f#.txt\" will define a template for all new \r\nfiles matching \"*\/foo\/*.txt\"; the filetype will be set to \"text\"\r\n- These \"auto templates\" must be located in \r\n~\/.vim\/skeletons\/templates\/GROUP\/\r\n- TSkeletonCB_FILENAME(), TSkeletonCB_DIRNAME()\r\n- FIX: TSkeletonGoToNextTag() didn't work properly with ### type of \r\nmarkers.\r\n- FIX: TSkeletonLateExpand(): tag at first column\r\n- FIX: In templates, empty lines sometimes were not inserted in the \r\ndocument\r\n- FIX: Build menu on SessionLoadPost event.\r\n- FIX: Protect against autocommands that move the cursor on a BufEnter \r\nevent\r\n- FIX: Some special characters in the skeleton bit expansion were escaped \r\ntwice with backslashes.\r\n- Require tlib 0.9\r\n- Make sure &foldmethod=manual in the scratch buffer\r\n","3":"- Automatically reset bits information after editing a bit.\r\n- Automatically define autocommands for templates with the form \"NAME \r\nPATTERN\" (where \"#\" in the pattern is replaced with \"*\"), i.e. the \r\ntemplate file \"text #%2ffoo%2f#.txt\" will define a template for all new \r\nfiles matching \"*\/foo\/*.txt\"; the filetype will be set to \"text\"\r\n- These \"auto templates\" must be located in \r\n~\/.vim\/skeletons\/templates\/GROUP\/\r\n- TSkeletonCB_FILENAME(), TSkeletonCB_DIRNAME()\r\n- FIX: TSkeletonGoToNextTag() didn't work properly with ### type of \r\nmarkers.\r\n- FIX: TSkeletonLateExpand(): tag at first column\r\n- FIX: In templates, empty lines sometimes were not inserted in the \r\ndocument\r\n- FIX: Build menu on SessionLoadPost event.\r\n- FIX: Protect against autocommands that move the cursor on a BufEnter \r\nevent\r\n- FIX: Some special characters in the skeleton bit expansion were escaped \r\ntwice with backslashes.\r\n- Require tlib 0.9\r\n- Make sure &foldmethod=manual in the scratch buffer\r\n","package":"tSkeleton.vba.gz","4":"tSkeleton.vba.gz","src_id":"7366","5":"7366","creation_date":"1184663540","6":"1184663540"},{"0":"1160","vim_version":"7.0","1":"7.0","script_version":"3.3","2":"3.3","version_comment":"- New :TSkeletonEditBit command\r\n- FIX: Embedded <tskel> tags in file templates didn't work\r\n","3":"- New :TSkeletonEditBit command\r\n- FIX: Embedded <tskel> tags in file templates didn't work\r\n","package":"tSkeleton.vba.gz","4":"tSkeleton.vba.gz","src_id":"7140","5":"7140","creation_date":"1179444816","6":"1179444816"},{"0":"1160","vim_version":"7.0","1":"7.0","script_version":"3.2","2":"3.2","version_comment":"- \"tags\" & \"functions\" types are disabled by default due to a noticeable \r\ndelay on initialization; add 'tags' and 'functions' to g:tskelTypes to \r\nre-enable them (with the new caching strategy, it's usable, but can \r\nproduce much noise; but this depends of course on the way you handle \r\ntags)\r\n- Improved caching strategy: cache filetype bits in \r\nskeletons\/cache_bits; cache buffer-specific bits in \r\nskeletons\/cache_bbits\/&filetype\/path (set g:tskelUseBufferCache to 0 to \r\nturn this off; this speeds up things quite a lot but creates many files \r\non the long run, so you might want to purge the cache from time to time)\r\n- embedded <tskel:> tags are now extracted on initialization and not \r\nwhen the skeleton is expanded (I'm not sure yet if it is better this \r\nway)\r\n- CHANGE: dropped support for the ~\/.vim\/skeletons\/prefab subdirectory; \r\nyou'll have to move the templates, if any, to ~\/.vim\/skeletons\r\n- FIX: :TSkeletonEdit, :TSkeletonSetup command-line completion\r\n- FIX: Problem with fold markers in bits when &fdm was marker\r\n- FIX: Problems with PrepareBits()\r\n- FIX: Problems when the skeletons\/menu\/ subdirectory didn't exist\r\n- TSkeletonExecInDestBuffer(code): speed-up\r\n- Moved functions from EncodeURL.vim to tlib.vim\r\n- Updated the manual\r\n- Renamed the skeletons\/menu subdirectory to skeletons\/cache_menu\r\n","3":"- \"tags\" & \"functions\" types are disabled by default due to a noticeable \r\ndelay on initialization; add 'tags' and 'functions' to g:tskelTypes to \r\nre-enable them (with the new caching strategy, it's usable, but can \r\nproduce much noise; but this depends of course on the way you handle \r\ntags)\r\n- Improved caching strategy: cache filetype bits in \r\nskeletons\/cache_bits; cache buffer-specific bits in \r\nskeletons\/cache_bbits\/&filetype\/path (set g:tskelUseBufferCache to 0 to \r\nturn this off; this speeds up things quite a lot but creates many files \r\non the long run, so you might want to purge the cache from time to time)\r\n- embedded <tskel:> tags are now extracted on initialization and not \r\nwhen the skeleton is expanded (I'm not sure yet if it is better this \r\nway)\r\n- CHANGE: dropped support for the ~\/.vim\/skeletons\/prefab subdirectory; \r\nyou'll have to move the templates, if any, to ~\/.vim\/skeletons\r\n- FIX: :TSkeletonEdit, :TSkeletonSetup command-line completion\r\n- FIX: Problem with fold markers in bits when &fdm was marker\r\n- FIX: Problems with PrepareBits()\r\n- FIX: Problems when the skeletons\/menu\/ subdirectory didn't exist\r\n- TSkeletonExecInDestBuffer(code): speed-up\r\n- Moved functions from EncodeURL.vim to tlib.vim\r\n- Updated the manual\r\n- Renamed the skeletons\/menu subdirectory to skeletons\/cache_menu\r\n","package":"tSkeleton.vba.gz","4":"tSkeleton.vba.gz","src_id":"7115","5":"7115","creation_date":"1179224577","6":"1179224577"},{"0":"1160","vim_version":"7.0","1":"7.0","script_version":"3.1","2":"3.1","version_comment":"- Tag-based code completion for vim\r\n- Made the supported skeleton types configurable via g:tskelTypes\r\n- FIX: Tag-based skeletons the name of which contain blanks\r\n- FIX: Undid shortcut that prevented the <+bit:+> tag from working\r\n- Preliminary support for using keys like <space> for insert mode \r\nexpansion.\r\n","3":"- Tag-based code completion for vim\r\n- Made the supported skeleton types configurable via g:tskelTypes\r\n- FIX: Tag-based skeletons the name of which contain blanks\r\n- FIX: Undid shortcut that prevented the <+bit:+> tag from working\r\n- Preliminary support for using keys like <space> for insert mode \r\nexpansion.\r\n","package":"tSkeleton.vba.gz","4":"tSkeleton.vba.gz","src_id":"7030","5":"7030","creation_date":"1177580622","6":"1177580622"},{"0":"1160","vim_version":"7.0","1":"7.0","script_version":"3.0","2":"3.0","version_comment":"This version is probably less stable than the predecessor. Or maybe not.\r\n- Partial rewrite for vim7 (drop vim6 support)\r\n- Now depends on tlib (vimscript #1863)\r\n- \"query\" now uses a more sophisticated version from autoload\/tlib.vim\r\n- The default value for g:tskelQueryType is \"query\".\r\n- Experimental (proof of concept) code completion for vim script \r\n(already sourced user-defined functions only). Use :delf \r\nTSkelFiletypeBits_prototypes_vim to disable this as it can take some \r\ntime on initialization.\r\n- Experimental (proof of concept) tags-based code completion for ruby.  \r\nUse :delf TSkelProcessTag_ruby to disable this. It's only partially \r\nuseful as it simply works on method names and knows nothing about \r\nclasses, modules etc. But it gives you an argument list to fill in. It \r\nshouldn't be too difficult to adapt this for other filetypes for which \r\nsuch an approach could be more useful.\r\n- The code makes it now possible to somehow plug in custom bit types by \r\ndefining TSkelFiletypeBits_{NAME}(dict, filetype), or \r\nTSkelFiletypeBits_{NAME}_{FILETYPE}(dict, filetype), \r\nTSkelBufferBits_{NAME}(dict, filetype), \r\nTSkelBufferBits_{NAME}_{FILETYPE}(dict, filetype).\r\n- FIX s:RetrieveAgent_read(): Delete last line, which should fix the \r\nproblem with extraneous return characters in recursively included \r\nskeleton bits.\r\n- FIX: bits containing backslashes\r\n- FIX TSkeletonGoToNextTag(): Moving cursor when no tag was found.\r\n- FIX: Minibits are now properly displayed in the menu.\r\n","3":"This version is probably less stable than the predecessor. Or maybe not.\r\n- Partial rewrite for vim7 (drop vim6 support)\r\n- Now depends on tlib (vimscript #1863)\r\n- \"query\" now uses a more sophisticated version from autoload\/tlib.vim\r\n- The default value for g:tskelQueryType is \"query\".\r\n- Experimental (proof of concept) code completion for vim script \r\n(already sourced user-defined functions only). Use :delf \r\nTSkelFiletypeBits_prototypes_vim to disable this as it can take some \r\ntime on initialization.\r\n- Experimental (proof of concept) tags-based code completion for ruby.  \r\nUse :delf TSkelProcessTag_ruby to disable this. It's only partially \r\nuseful as it simply works on method names and knows nothing about \r\nclasses, modules etc. But it gives you an argument list to fill in. It \r\nshouldn't be too difficult to adapt this for other filetypes for which \r\nsuch an approach could be more useful.\r\n- The code makes it now possible to somehow plug in custom bit types by \r\ndefining TSkelFiletypeBits_{NAME}(dict, filetype), or \r\nTSkelFiletypeBits_{NAME}_{FILETYPE}(dict, filetype), \r\nTSkelBufferBits_{NAME}(dict, filetype), \r\nTSkelBufferBits_{NAME}_{FILETYPE}(dict, filetype).\r\n- FIX s:RetrieveAgent_read(): Delete last line, which should fix the \r\nproblem with extraneous return characters in recursively included \r\nskeleton bits.\r\n- FIX: bits containing backslashes\r\n- FIX TSkeletonGoToNextTag(): Moving cursor when no tag was found.\r\n- FIX: Minibits are now properly displayed in the menu.\r\n","package":"tSkeleton.vba.gz","4":"tSkeleton.vba.gz","src_id":"7023","5":"7023","creation_date":"1177411507","6":"1177411507"},{"0":"1160","vim_version":"6.0","1":"6.0","script_version":"3.0samples","2":"3.0samples","version_comment":"This files contains some templates to be used with this plugin. They were previously distributed with the plugin.","3":"This files contains some templates to be used with this plugin. They were previously distributed with the plugin.","package":"tSkeleton-Samples.zip","4":"tSkeleton-Samples.zip","src_id":"7022","5":"7022","creation_date":"1177411294","6":"1177411294"},{"0":"1160","vim_version":"6.0","1":"6.0","script_version":"2.3a","2":"2.3a","version_comment":"Support for current versions of genutils (> 2.0), really","3":"Support for current versions of genutils (> 2.0), really","package":"tSkeleton.zip","4":"tSkeleton.zip","src_id":"6245","5":"6245","creation_date":"1159909084","6":"1159909084"},{"0":"1160","vim_version":"6.0","1":"6.0","script_version":"2.2","2":"2.2","version_comment":"- Don't display query menu, when there is only one eligible bit\r\n- EncodeURL.vim now correctly en\/decoded urls\r\n- UTF8 compatibility -- use col() instead of virtcol() (thanks to Elliot Shank)\r\n","3":"- Don't display query menu, when there is only one eligible bit\r\n- EncodeURL.vim now correctly en\/decoded urls\r\n- UTF8 compatibility -- use col() instead of virtcol() (thanks to Elliot Shank)\r\n","package":"tSkeleton.zip","4":"tSkeleton.zip","src_id":"6220","5":"6220","creation_date":"1158980205","6":"1158980205"},{"0":"1160","vim_version":"6.0","1":"6.0","script_version":"2.1","2":"2.1","version_comment":"- Don't accidentally remove torn off menus; rebuild the menu less often\r\n- Maintain insert mode (don't switch back to normal mode) in <c-\\><c-\\> imap\r\n- If no menu support is available, use the <SID>Query function to let the user select among eligible bits (see also g:tskelQueryType)\r\n- Create a normal and an insert mode menu\r\n- Fixed selection of eligible bits\r\n- Ensure that g:tskelDir ends with a (back)slash\r\n- Search for 'skeletons\/' in &runtimepath & set g:tskelDir accordingly\r\n- If a template is named \"#.suffix\", an autocmd is created automatically.\r\n- Set g:tskelQueryType to 'popup' only if gui is win32 or gtk.\r\n- Minor tweak for vim 7.0 compatibility\r\n","3":"- Don't accidentally remove torn off menus; rebuild the menu less often\r\n- Maintain insert mode (don't switch back to normal mode) in <c-\\><c-\\> imap\r\n- If no menu support is available, use the <SID>Query function to let the user select among eligible bits (see also g:tskelQueryType)\r\n- Create a normal and an insert mode menu\r\n- Fixed selection of eligible bits\r\n- Ensure that g:tskelDir ends with a (back)slash\r\n- Search for 'skeletons\/' in &runtimepath & set g:tskelDir accordingly\r\n- If a template is named \"#.suffix\", an autocmd is created automatically.\r\n- Set g:tskelQueryType to 'popup' only if gui is win32 or gtk.\r\n- Minor tweak for vim 7.0 compatibility\r\n","package":"tSkeleton.zip","4":"tSkeleton.zip","src_id":"5676","5":"5676","creation_date":"1147298742","6":"1147298742"},{"0":"1160","vim_version":"6.0","1":"6.0","script_version":"2.0","2":"2.0","version_comment":"- You can define \"groups of bits\" (e.g. in php mode, all html bits are \r\n  available too)\r\n- context sensitive expansions (only very few examples yet); this causes \r\n  some slowdown; if it is too slow, delete the files in .vim\/skeletons\/map\/\r\n- one-line \"mini bits\" defined in either \r\n  .\/vim\/skeletons\/bits\/{&filetype}.txt or in $PWD\/.tskelmini\r\n- Added a few LaTeX, HTML and many Viki skeleton bits\r\n- Added EncodeURL.vim\r\n- Hierarchical bits menu by calling a bit \"SUBMENU.BITNAME\" (the \"namespace\" \r\n  is flat though; the prefix has no effect on the bit name; see the \"bib\" \r\n  directory for an example)\r\n- the bit file may have an ampersand (&) in their names to define the \r\n  keyboard shortcut\r\n- Some special characters in bit names may be encoded as hex (%XX as in \r\n  URLs)\r\n- Insert mode: map g:tskelMapInsert ('<c-\\><c-\\>', which happens to be the \r\n  <c-#> key on a German qwertz keyboard) to TSkeletonExpandBitUnderCursor()\r\n- New <tskel:msg> tag in skeleton bits\r\n- g:tskelKeyword_{&filetype} variable to define keywords by regexp (when \r\n  'iskeyword' isn't flexible enough)\r\n- removed the g:tskelSimpleBits option\r\n- Fixed some problems with the menu\r\n- Less use of globpath()\r\n","3":"- You can define \"groups of bits\" (e.g. in php mode, all html bits are \r\n  available too)\r\n- context sensitive expansions (only very few examples yet); this causes \r\n  some slowdown; if it is too slow, delete the files in .vim\/skeletons\/map\/\r\n- one-line \"mini bits\" defined in either \r\n  .\/vim\/skeletons\/bits\/{&filetype}.txt or in $PWD\/.tskelmini\r\n- Added a few LaTeX, HTML and many Viki skeleton bits\r\n- Added EncodeURL.vim\r\n- Hierarchical bits menu by calling a bit \"SUBMENU.BITNAME\" (the \"namespace\" \r\n  is flat though; the prefix has no effect on the bit name; see the \"bib\" \r\n  directory for an example)\r\n- the bit file may have an ampersand (&) in their names to define the \r\n  keyboard shortcut\r\n- Some special characters in bit names may be encoded as hex (%XX as in \r\n  URLs)\r\n- Insert mode: map g:tskelMapInsert ('<c-\\><c-\\>', which happens to be the \r\n  <c-#> key on a German qwertz keyboard) to TSkeletonExpandBitUnderCursor()\r\n- New <tskel:msg> tag in skeleton bits\r\n- g:tskelKeyword_{&filetype} variable to define keywords by regexp (when \r\n  'iskeyword' isn't flexible enough)\r\n- removed the g:tskelSimpleBits option\r\n- Fixed some problems with the menu\r\n- Less use of globpath()\r\n","package":"tSkeleton.zip","4":"tSkeleton.zip","src_id":"4488","5":"4488","creation_date":"1123801063","6":"1123801063"},{"0":"1160","vim_version":"6.0","1":"6.0","script_version":"1.5","2":"1.5","version_comment":"- Menu of small skeleton \"bits\"\r\n- TSkeletonLateExpand() (mapped to <Leader>#x)\r\n- Disabled <Leader># mapping (use it as a prefix only)\r\n- Fixed copy & paste error (loaded_genutils)\r\n- g:tskelDir defaults to $HOME .\"\/vimfiles\/skeletons\/\" on Win32\r\n- Some speedup\r\n","3":"- Menu of small skeleton \"bits\"\r\n- TSkeletonLateExpand() (mapped to <Leader>#x)\r\n- Disabled <Leader># mapping (use it as a prefix only)\r\n- Fixed copy & paste error (loaded_genutils)\r\n- g:tskelDir defaults to $HOME .\"\/vimfiles\/skeletons\/\" on Win32\r\n- Some speedup\r\n","package":"tSkeleton.zip","4":"tSkeleton.zip","src_id":"4447","5":"4447","creation_date":"1122545453","6":"1122545453"},{"0":"1160","vim_version":"6.0","1":"6.0","script_version":"1.4","2":"1.4","version_comment":"- Popup menu with possible completions if TSkeletonExpandBitUnderCursor() is \r\ncalled for an unknown code skeleton (if there is only one possible completion, \r\nthis one is automatically selected)\r\n- Make sure not to change the alternate file and not to distort the window \r\nlayout\r\n- require genutils\r\n- Syntax highlighting for code skeletons\r\n- Skeleton bits can now be expanded anywhere in the line. This makes it \r\npossible to sensibly use small bits like date or time.\r\n- Minor adjustments\r\n- g:tskelMapLeader for easy customization of key mapping (changed the map \r\nleader to \"<Leader>#\" in order to avoid a conflict with Align; set \r\ng:tskelMapLeader to \"<Leader>t\" to get the old mappings)\r\n- Utility function: TSkeletonGoToNextTag(); imaps.vim like key bindings via TSkeletonMapGoToNextTag()\r\n","3":"- Popup menu with possible completions if TSkeletonExpandBitUnderCursor() is \r\ncalled for an unknown code skeleton (if there is only one possible completion, \r\nthis one is automatically selected)\r\n- Make sure not to change the alternate file and not to distort the window \r\nlayout\r\n- require genutils\r\n- Syntax highlighting for code skeletons\r\n- Skeleton bits can now be expanded anywhere in the line. This makes it \r\npossible to sensibly use small bits like date or time.\r\n- Minor adjustments\r\n- g:tskelMapLeader for easy customization of key mapping (changed the map \r\nleader to \"<Leader>#\" in order to avoid a conflict with Align; set \r\ng:tskelMapLeader to \"<Leader>t\" to get the old mappings)\r\n- Utility function: TSkeletonGoToNextTag(); imaps.vim like key bindings via TSkeletonMapGoToNextTag()\r\n","package":"tSkeleton.zip","4":"tSkeleton.zip","src_id":"4297","5":"4297","creation_date":"1116492943","6":"1116492943"},{"0":"1160","vim_version":"6.0","1":"6.0","script_version":"1.3","2":"1.3","version_comment":"- TSkeletonCleanUpBibEntry (mapped to <Leader>tc for bib files)\r\n- complete set of bibtex entries\r\n- fixed problem with [&bg]: tags\r\n- fixed typo that caused some slowdown\r\n- other bug fixes\r\n- a query must be enclosed in question marks as in <+?Which ID?+>\r\n- the \"test_tSkeleton\" skeleton can be used to test if tSkeleton is working\r\n- and: after\/before blocks must not contain function definitions\r\n","3":"- TSkeletonCleanUpBibEntry (mapped to <Leader>tc for bib files)\r\n- complete set of bibtex entries\r\n- fixed problem with [&bg]: tags\r\n- fixed typo that caused some slowdown\r\n- other bug fixes\r\n- a query must be enclosed in question marks as in <+?Which ID?+>\r\n- the \"test_tSkeleton\" skeleton can be used to test if tSkeleton is working\r\n- and: after\/before blocks must not contain function definitions\r\n","package":"tSkeleton.zip","4":"tSkeleton.zip","src_id":"3972","5":"3972","creation_date":"1110078422","6":"1110078422"},{"0":"1160","vim_version":"6.0","1":"6.0","script_version":"1.2","2":"1.2","version_comment":"- new pseudo tags: bit (recursive code skeletons), call (insert function result)\r\n- before & after sections in bit definitions may contain function definitions\r\n- fixed: no bit name given in <SID>SelectBit()\r\n- don't use ={motion} to indent text, but simply shift it\r\n","3":"- new pseudo tags: bit (recursive code skeletons), call (insert function result)\r\n- before & after sections in bit definitions may contain function definitions\r\n- fixed: no bit name given in <SID>SelectBit()\r\n- don't use ={motion} to indent text, but simply shift it\r\n","package":"tSkeleton.zip","4":"tSkeleton.zip","src_id":"3951","5":"3951","creation_date":"1109759465","6":"1109759465"},{"0":"1160","vim_version":"6.0","1":"6.0","script_version":"1.1","2":"1.1","version_comment":"- Skeleton bits (small inline skeletons or whatever you want to call it)\r\n- User-defined tags\r\n- Modifiers <+NAME:MODIFIERS+> (c=capitalize, u=toupper, l=tolower, s\/\/=substitute)\r\n- the default markup for tags has changed to <+TAG+> (for \"compatibility\" with \r\nimaps.vim), the cursor position is marked as <+CURSOR+> (but this can be \r\nchanged by setting g:tskelPatternLeft, g:tskelPatternRight, and \r\ng:tskelPatternCursor)\r\n- in the not so simple mode, skeleton bits can contain vim code that is \r\nevaluated after expanding the template tags (see ...\/skeletons\/bits\/vim\/if for \r\nan example)\r\n- function TSkeletonExpandBitUnderCursor(), which is mapped to <Leader>#\r\n- utility function: TSkeletonIncreaseRevisionNumber()\r\n","3":"- Skeleton bits (small inline skeletons or whatever you want to call it)\r\n- User-defined tags\r\n- Modifiers <+NAME:MODIFIERS+> (c=capitalize, u=toupper, l=tolower, s\/\/=substitute)\r\n- the default markup for tags has changed to <+TAG+> (for \"compatibility\" with \r\nimaps.vim), the cursor position is marked as <+CURSOR+> (but this can be \r\nchanged by setting g:tskelPatternLeft, g:tskelPatternRight, and \r\ng:tskelPatternCursor)\r\n- in the not so simple mode, skeleton bits can contain vim code that is \r\nevaluated after expanding the template tags (see ...\/skeletons\/bits\/vim\/if for \r\nan example)\r\n- function TSkeletonExpandBitUnderCursor(), which is mapped to <Leader>#\r\n- utility function: TSkeletonIncreaseRevisionNumber()\r\n","package":"tSkeleton.zip","4":"tSkeleton.zip","src_id":"3786","5":"3786","creation_date":"1106214557","6":"1106214557"},{"0":"1160","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"tSkeleton.zip","4":"tSkeleton.zip","src_id":"3718","5":"3718","creation_date":"1103582718","6":"1103582718"}]},"1159":{"script_id":"1159","0":"1159","script_name":"pagemaker6","1":"pagemaker6","script_type":"syntax","2":"syntax","summary":"Syntax for Adobe Pagemaker 6 files","3":"Syntax for Adobe Pagemaker 6 files","description":"A syntax highlighting scheme for Adobe Pagemaker 6. This file was created by Aurelio Marinho Jargas.","4":"A syntax highlighting scheme for Adobe Pagemaker 6. This file was created by Aurelio Marinho Jargas.","install_details":"Save the file in your ~\/.vim\/syntax\/ directory and either use :set syntax=pm6 or add the following line to your vimrc file: \r\nau BufNewFile,BufRead *.pm6 set ft=pm6","5":"Save the file in your ~\/.vim\/syntax\/ directory and either use :set syntax=pm6 or add the following line to your vimrc file: \r\nau BufNewFile,BufRead *.pm6 set ft=pm6","first_name":"Alexandre","6":"Alexandre","last_name":"Lima","7":"Lima","releases":[{"0":"1159","vim_version":"6.0","1":"6.0","script_version":"20010730","2":"20010730","version_comment":"Initial upload","3":"Initial upload","package":"pagemaker.vim","4":"pagemaker.vim","src_id":"3712","5":"3712","creation_date":"1103270976","6":"1103270976"}]},"1158":{"script_id":"1158","0":"1158","script_name":"unhtml","1":"unhtml","script_type":"utility","2":"utility","summary":"Converts HTML tags to a simpler syntax","3":"Converts HTML tags to a simpler syntax","description":"This script converts HTML tags into txt2tags marks. It was created by Aurelio Marinho Jargas, creator of txt2tags. For more info on txt2tags, visit http:\/\/txt2tags.sf.net\/ .\r\n\r\nINSTRUCTIONS\r\n1. Open the HTML file on Vim and execute :so \/path\/to\/unhtml.vim\r\n2. A new <yourfile>.html.t2t will be saved.\r\n3. Check the new .t2t file and correct by hand what has left.","4":"This script converts HTML tags into txt2tags marks. It was created by Aurelio Marinho Jargas, creator of txt2tags. For more info on txt2tags, visit http:\/\/txt2tags.sf.net\/ .\r\n\r\nINSTRUCTIONS\r\n1. Open the HTML file on Vim and execute :so \/path\/to\/unhtml.vim\r\n2. A new <yourfile>.html.t2t will be saved.\r\n3. Check the new .t2t file and correct by hand what has left.","install_details":"","5":"","first_name":"Alexandre","6":"Alexandre","last_name":"Lima","7":"Lima","releases":[{"0":"1158","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"unhtml.vim","4":"unhtml.vim","src_id":"3709","5":"3709","creation_date":"1103108081","6":"1103108081"}]},"1157":{"script_id":"1157","0":"1157","script_name":"txt2tags","1":"txt2tags","script_type":"syntax","2":"syntax","summary":"Syntax highlighting for txt2tags documents","3":"Syntax highlighting for txt2tags documents","description":"A syntax highlighting scheme for txt2tags. Both txt2tags and this syntax file were created by Aurelio Marinho Jargas.\r\ntxt2tags' official site: http:\/\/txt2tags.sf.net\/","4":"A syntax highlighting scheme for txt2tags. Both txt2tags and this syntax file were created by Aurelio Marinho Jargas.\r\ntxt2tags' official site: http:\/\/txt2tags.sf.net\/","install_details":"Save the file in your ~\/.vim\/syntax\/ directory, and either use :set syntax=txt2tags or add the following line to your vimrc file:\r\nau BufNewFile,BufRead *.t2t set ft=txt2tags","5":"Save the file in your ~\/.vim\/syntax\/ directory, and either use :set syntax=txt2tags or add the following line to your vimrc file:\r\nau BufNewFile,BufRead *.t2t set ft=txt2tags","first_name":"Alexandre","6":"Alexandre","last_name":"Lima","7":"Lima","releases":[{"0":"1157","vim_version":"6.0","1":"6.0","script_version":"20040714","2":"20040714","version_comment":"Initial upload","3":"Initial upload","package":"txt2tags.vim","4":"txt2tags.vim","src_id":"3708","5":"3708","creation_date":"1103107614","6":"1103107614"}]},"1156":{"script_id":"1156","0":"1156","script_name":"ledger.vim","1":"ledger.vim","script_type":"indent","2":"indent","summary":"indenting for Ledger accounting files","3":"indenting for Ledger accounting files","description":"Sets the indenting for a ledger file used with the ledger (http:\/\/ledger.sourceforge.net\/) accounting system","4":"Sets the indenting for a ledger file used with the ledger (http:\/\/ledger.sourceforge.net\/) accounting system","install_details":"add this to your filetype.vim, or make a ledger.vim in ftdetect with the following lines:\r\n\r\n\" Ledger files with .ldg extentions\r\nau BufNewFile,BufRead *.ldg,*.ledger        setf ledger\r\n\r\nnake sure to name your $LEDGER file with a .ldg or .ledger extention","5":"add this to your filetype.vim, or make a ledger.vim in ftdetect with the following lines:\r\n\r\n\" Ledger files with .ldg extentions\r\nau BufNewFile,BufRead *.ldg,*.ledger        setf ledger\r\n\r\nnake sure to name your $LEDGER file with a .ldg or .ledger extention","first_name":"Allan","6":"Allan","last_name":"Neal","7":"Neal","releases":[{"0":"1156","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"ledger.vim","4":"ledger.vim","src_id":"3694","5":"3694","creation_date":"1102634520","6":"1102634520"}]},"1155":{"script_id":"1155","0":"1155","script_name":"ledger.vim","1":"ledger.vim","script_type":"syntax","2":"syntax","summary":"Syntax highlighting for ledger (accounting system) files","3":"Syntax highlighting for ledger (accounting system) files","description":"Highlights the syntax for Ledger (http:\/\/ledger.sourceforge.net\/) command line accounting package.","4":"Highlights the syntax for Ledger (http:\/\/ledger.sourceforge.net\/) command line accounting package.","install_details":"add this to your filetype.vim, or make a ledger.vim in ftdetect with the following lines:\r\n\r\n\" Ledger files with .ldg extentions\r\nau BufNewFile,BufRead *.ldg,*.ledger        setf ledger\r\n\r\nnake sure to name your $LEDGER file with a .ldg or .ledger extention","5":"add this to your filetype.vim, or make a ledger.vim in ftdetect with the following lines:\r\n\r\n\" Ledger files with .ldg extentions\r\nau BufNewFile,BufRead *.ldg,*.ledger        setf ledger\r\n\r\nnake sure to name your $LEDGER file with a .ldg or .ledger extention","first_name":"Allan","6":"Allan","last_name":"Neal","7":"Neal","releases":[{"0":"1155","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"ledger.vim","4":"ledger.vim","src_id":"3693","5":"3693","creation_date":"1102634444","6":"1102634444"}]},"1154":{"script_id":"1154","0":"1154","script_name":"JavaKit","1":"JavaKit","script_type":"utility","2":"utility","summary":"A collection of tools for developing java apps","3":"A collection of tools for developing java apps","description":"A collection of tools for developping java applications.  The installation guide is in the readme.txt file.","4":"A collection of tools for developping java applications.  The installation guide is in the readme.txt file.","install_details":"","5":"","first_name":"Yiu","6":"Yiu","last_name":"Wing","7":"Wing","releases":[{"0":"1154","vim_version":"7.0","1":"7.0","script_version":"2.1","2":"2.1","version_comment":"This is a major release which turns vim into a java IDE.   Debugging with jdb is enabled.  Users can easily access the full functionalities provided by jdb.  The completion feature has been much improved to provide supports for generic types and long expressions.","3":"This is a major release which turns vim into a java IDE.   Debugging with jdb is enabled.  Users can easily access the full functionalities provided by jdb.  The completion feature has been much improved to provide supports for generic types and long expressions.","package":"javakit.zip","4":"javakit.zip","src_id":"8658","5":"8658","creation_date":"1210187417","6":"1210187417"},{"0":"1154","vim_version":"6.0","1":"6.0","script_version":"1.1","2":"1.1","version_comment":"Initial upload","3":"Initial upload","package":"JavaKit.zip","4":"JavaKit.zip","src_id":"3692","5":"3692","creation_date":"1102631085","6":"1102631085"}]},"1153":{"script_id":"1153","0":"1153","script_name":"xbl.vim","1":"xbl.vim","script_type":"syntax","2":"syntax","summary":"Syntax highlighting for Extensible Binding Language (XBL)","3":"Syntax highlighting for Extensible Binding Language (XBL)","description":"Syntax highlighting for Extensible Binding Language (XBL). The main purpose of the script is to syntax highlight javascript code contained in CDATA blocks.\r\n\r\nThe script is a hack; my understanding of VIM scripting is almost nil. I look forward to improvements made by anyone.\r\n\r\nTo have vim detect the file type from files with the .xbl extension,\r\njust add the following two lines to the \"filetype.vim\" file in the\r\ndirectory that contains the \"syntax\" directory:\r\n\r\n\" XBL\r\nau BufNewFile,BufRead *.xbl   setf xbl\r\n\r\nTo have xbl syntax coloration appear in the syntax drop-down menu, just\r\nadd the line:\r\n \r\nan 50.120.240 &Syntax.WXYZ.XBL :cal SetSyn(\"xbl\")<CR>\r\n\r\nto the \"synmenu.vim\" file (the value 240 in 50.120.240 might differ\r\naccording to what is already in your own file).\r\n\r\n-- Thanks to Xavier Grosjean <xavcap AT c-est-simple DOT com> for\r\ninformation on file type detection and menu updating.\r\n\r\nUse \":set syntax=xbl\" to turn it on for non-xbl files after the file is opened.\r\n","4":"Syntax highlighting for Extensible Binding Language (XBL). The main purpose of the script is to syntax highlight javascript code contained in CDATA blocks.\r\n\r\nThe script is a hack; my understanding of VIM scripting is almost nil. I look forward to improvements made by anyone.\r\n\r\nTo have vim detect the file type from files with the .xbl extension,\r\njust add the following two lines to the \"filetype.vim\" file in the\r\ndirectory that contains the \"syntax\" directory:\r\n\r\n\" XBL\r\nau BufNewFile,BufRead *.xbl   setf xbl\r\n\r\nTo have xbl syntax coloration appear in the syntax drop-down menu, just\r\nadd the line:\r\n \r\nan 50.120.240 &Syntax.WXYZ.XBL :cal SetSyn(\"xbl\")<CR>\r\n\r\nto the \"synmenu.vim\" file (the value 240 in 50.120.240 might differ\r\naccording to what is already in your own file).\r\n\r\n-- Thanks to Xavier Grosjean <xavcap AT c-est-simple DOT com> for\r\ninformation on file type detection and menu updating.\r\n\r\nUse \":set syntax=xbl\" to turn it on for non-xbl files after the file is opened.\r\n","install_details":"Just copy the file, xbl.vim, to your syntax directory.\r\nSee http:\/\/www.x2ii.info for latest version.","5":"Just copy the file, xbl.vim, to your syntax directory.\r\nSee http:\/\/www.x2ii.info for latest version.","first_name":"Kurt","6":"Kurt","last_name":"Brown","7":"Brown","releases":[{"0":"1153","vim_version":"6.0","1":"6.0","script_version":"1.1","2":"1.1","version_comment":"Updated contact info.","3":"Updated contact info.","package":"xbl.vim","4":"xbl.vim","src_id":"6225","5":"6225","creation_date":"1159188119","6":"1159188119"},{"0":"1153","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"xbl.vim","4":"xbl.vim","src_id":"3691","5":"3691","creation_date":"1102593579","6":"1102593579"}]},"1152":{"script_id":"1152","0":"1152","script_name":"remote PHP debugger","1":"remote PHP debugger","script_type":"utility","2":"utility","summary":"remote debugger interface to DBGp protocol.","3":"remote debugger interface to DBGp protocol.","description":"This python script provide debugger interface to DBGp protocol.\r\n( but, only tested on Xdebug2.0 - http:\/\/www.xdebug.org\/ )\r\n\r\nscreen shot:  http:\/\/segv74.homeip.net:7000\/debugger.gif \r\n\r\nRequirements)\r\n- DBGp protocol enabled debugging module. such as xdebug.\r\n  ( I don't know there are free DBGp debugger except xdebug )\r\n-  vim 6.3 ( only tested on vim 6.3 ) with !!!!!!!!!!!!\r\n- python 2.3+ interface , +sign feature  !!!!!!!!!!!!\r\n  ( < python 2.2 don't have socket timeout. sorry for my lasiness. )\r\n- this vim script. ( debugger.vim \/ debugger.py )\r\n\r\nUsage)\r\n1. setup xdebug 2.0 correctly. or other DBGp enabled server.\r\n   ( with proper remote debug option )\r\n\r\n2. press <F5> and browse php file within 5 seconds. :-)\r\n    If you did setup correctly, server will make connection to vim.\r\n    [ you can change port by editing last line of debugger.vim ]\r\n\r\n    all the windows currently opened will be closed and debugger interface will be shown.\r\n\r\n3. in debuggin mode\r\n<F1> : resizing windows\r\n<F2> : step into\r\n<F3> : step over\r\n<F4> : step out\r\n\r\n<F6> : stop debugging\r\n\r\n<F11> : shows all variables\r\n<F12> : shows variable on current cursor \r\n\r\n,e : evalute expression and display result. cursor is automatically move to watch window. type line and just press enter.\r\n\r\ncommand line command)\r\n:Bp    : toggle breakpoint on current line\r\n:Up    : goto upper level of stack\r\n:Dn    : goto lower level of stack\r\n\r\n4. press <F6> to stop debugging.\r\n    then, debugger windows will be closed and windows will be restored.\r\n    ( holy :mksession feature )\r\n\r\n5. notes\r\n-  you will see python's exception message. almost of them occurred when connection is closed. xdebug dosen't send message for last file\/line information.\r\njust press <F6> to restore sesson. sometimes are xdebug's bug.\r\n- to use with a lot of people with same time, it may needs DBGp proxy. you may download MIT licensed(?) version of it from activestate's komodo's evalution copy. and, you have to change this script a little.\r\n- it doesn't all features of DBGp. very essential part of it.\r\n\r\n*** there will be no future release plan of this script.***\r\ncurrently I'm working on PHP interface on vim, and I will use my php version of this debugger. maybe someday you can see it. so, I really appriciate if someone upgrade this script.\r\n\r\nVERY IMPORTANT TIP)\r\nIf you turn off syntax highlighting, It will increase speed very much !!!!!!\r\n:syn off (but, not pretty)\r\n","4":"This python script provide debugger interface to DBGp protocol.\r\n( but, only tested on Xdebug2.0 - http:\/\/www.xdebug.org\/ )\r\n\r\nscreen shot:  http:\/\/segv74.homeip.net:7000\/debugger.gif \r\n\r\nRequirements)\r\n- DBGp protocol enabled debugging module. such as xdebug.\r\n  ( I don't know there are free DBGp debugger except xdebug )\r\n-  vim 6.3 ( only tested on vim 6.3 ) with !!!!!!!!!!!!\r\n- python 2.3+ interface , +sign feature  !!!!!!!!!!!!\r\n  ( < python 2.2 don't have socket timeout. sorry for my lasiness. )\r\n- this vim script. ( debugger.vim \/ debugger.py )\r\n\r\nUsage)\r\n1. setup xdebug 2.0 correctly. or other DBGp enabled server.\r\n   ( with proper remote debug option )\r\n\r\n2. press <F5> and browse php file within 5 seconds. :-)\r\n    If you did setup correctly, server will make connection to vim.\r\n    [ you can change port by editing last line of debugger.vim ]\r\n\r\n    all the windows currently opened will be closed and debugger interface will be shown.\r\n\r\n3. in debuggin mode\r\n<F1> : resizing windows\r\n<F2> : step into\r\n<F3> : step over\r\n<F4> : step out\r\n\r\n<F6> : stop debugging\r\n\r\n<F11> : shows all variables\r\n<F12> : shows variable on current cursor \r\n\r\n,e : evalute expression and display result. cursor is automatically move to watch window. type line and just press enter.\r\n\r\ncommand line command)\r\n:Bp    : toggle breakpoint on current line\r\n:Up    : goto upper level of stack\r\n:Dn    : goto lower level of stack\r\n\r\n4. press <F6> to stop debugging.\r\n    then, debugger windows will be closed and windows will be restored.\r\n    ( holy :mksession feature )\r\n\r\n5. notes\r\n-  you will see python's exception message. almost of them occurred when connection is closed. xdebug dosen't send message for last file\/line information.\r\njust press <F6> to restore sesson. sometimes are xdebug's bug.\r\n- to use with a lot of people with same time, it may needs DBGp proxy. you may download MIT licensed(?) version of it from activestate's komodo's evalution copy. and, you have to change this script a little.\r\n- it doesn't all features of DBGp. very essential part of it.\r\n\r\n*** there will be no future release plan of this script.***\r\ncurrently I'm working on PHP interface on vim, and I will use my php version of this debugger. maybe someday you can see it. so, I really appriciate if someone upgrade this script.\r\n\r\nVERY IMPORTANT TIP)\r\nIf you turn off syntax highlighting, It will increase speed very much !!!!!!\r\n:syn off (but, not pretty)\r\n","install_details":"put all files in ~\/.vim\/plugin directory.\r\n","5":"put all files in ~\/.vim\/plugin directory.\r\n","first_name":"Seung Woo","6":"Seung Woo","last_name":"Shin","7":"Shin","releases":[{"0":"1152","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"debugger.tgz","4":"debugger.tgz","src_id":"3688","5":"3688","creation_date":"1102413357","6":"1102413357"}]},"1151":{"script_id":"1151","0":"1151","script_name":"globalreplace.vim","1":"globalreplace.vim","script_type":"utility","2":"utility","summary":"Prompted global search and replace","3":"Prompted global search and replace","description":"Instead of typing %s\/foo\/bar\/gc every time you want to search and replace in a file simply call this function and get prompted for the text to find and what to replace it with.\r\n\r\nI looked for something like this, but didn't find it, hope it's useful (my first, and admittedly unimpressive script)\r\n\r\np.s.\r\n\r\nYou might want to tack \"I\" onto the regexp to make it case sensitive, so it'll look like this:\r\nexecute \"%s\/\".l:find.\"\/\".l:replace.\"\/gcI\"\r\n","4":"Instead of typing %s\/foo\/bar\/gc every time you want to search and replace in a file simply call this function and get prompted for the text to find and what to replace it with.\r\n\r\nI looked for something like this, but didn't find it, hope it's useful (my first, and admittedly unimpressive script)\r\n\r\np.s.\r\n\r\nYou might want to tack \"I\" onto the regexp to make it case sensitive, so it'll look like this:\r\nexecute \"%s\/\".l:find.\"\/\".l:replace.\"\/gcI\"\r\n","install_details":"Simply drop the script in your .vim\/plugin directory\r\n\r\nI mapped it as follows\r\nmap <Leader>gr :call MISC_GlobalReplace()<cr>","5":"Simply drop the script in your .vim\/plugin directory\r\n\r\nI mapped it as follows\r\nmap <Leader>gr :call MISC_GlobalReplace()<cr>","first_name":"Chris","6":"Chris","last_name":"Rummel","7":"Rummel","releases":[{"0":"1151","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"globalreplace.vim","4":"globalreplace.vim","src_id":"3686","5":"3686","creation_date":"1102301060","6":"1102301060"}]},"1150":{"script_id":"1150","0":"1150","script_name":"cygwin_utils.vim","1":"cygwin_utils.vim","script_type":"utility","2":"utility","summary":"utility functions for invoking *nix cmds in Windows\/Cygwin (for use  in scripts)","3":"utility functions for invoking *nix cmds in Windows\/Cygwin (for use  in scripts)","description":"\"   This script has been created as a means to hopefully make using\r\n\"   cygwin easier, so that scripts that utilize *nix commands can be\r\n\"   ported to windows.\r\n\"\r\n\"   Right now this script provides only a few funtions, but it may grow\r\n\"   over time.\r\n\"\r\n\"   I'm making sure that each function will be safe to use under *nix\r\n\"   (specifically linux, since that's what I use) by confirming that vim\r\n\"   is running under windows before executing any windows\/cygwin\r\n\"   specific commands.\r\n\"\r\n\" Platform:\r\n\"   Windows:\r\n\"     Requires cygwin (http:\/\/cygwin.com).\r\n\"   *nux:\r\n\"     Should be safe to use any function defined within on *nix systems\r\n\"     since each function checks the platform before running system\r\n\"     specific commands.\r\n\"\r\n\"     However, if you don't want *nix users to have a dependency on this\r\n\"     plugin, you may define proxy functions that first check if a function\r\n\"     is defined before using it.\r\n\"\r\n\"     Ex. Defining a proxy function for translating paths based on OS.\r\n\"       function! s:DeterminePath (path)\r\n\"         if exists(\"*CygwinPath\")\r\n\"           return CygwinPath(a:path)\r\n\"         endif\r\n\"         return a:path\r\n\"       endfunction\r\n\"\r\n\" Configuration:\r\n\"   Note: Configuration is only necessary on Windows machines.\r\n\"\r\n\"   g:CygwinHome\r\n\"     Set this to the location of your cygwin installation dir.\r\n\"     Ex.\r\n\"       let g:CygwinHome = 'c:\/cygwin'\r\n\"     Note: Be careful using '\\\\' in double quoted strings since\r\n\"     that represents the start of an escape character in vim.\r\n\"\r\n\"   On windows you will need to add your cygwin\/bin directory to\r\n\"   your WINDOWS path.\r\n\"     PATH=%CYGWIN_HOME%\\bin;%PATH%\r\n\"   So that unix commands can be executed from your dos console.\r\n\"\r\n\"   Also, I had issues using Windows' default temp directory.\r\n\"   Vim continually had issues accessing temp files (that I have\r\n\"   no control over).  It seems it was due to the spaces in the\r\n\"   directory path, so I changed my system %TMP% and %TEMP%\r\n\"   variables to point to c:\\cygwin\\tmp instead, and that solved\r\n\"   my issues.  You may have to do the same.\r\n\"\r\n\" Limitations:\r\n\"   All file and directory paths used in cygwin commands need to\r\n\"   be absolute.  When the vim shell is set to a cygwin shell, the\r\n\"   shell defaults to executing in the user's home directory.\r\n\"   Because of this, relative paths cannot be used.\r\n","4":"\"   This script has been created as a means to hopefully make using\r\n\"   cygwin easier, so that scripts that utilize *nix commands can be\r\n\"   ported to windows.\r\n\"\r\n\"   Right now this script provides only a few funtions, but it may grow\r\n\"   over time.\r\n\"\r\n\"   I'm making sure that each function will be safe to use under *nix\r\n\"   (specifically linux, since that's what I use) by confirming that vim\r\n\"   is running under windows before executing any windows\/cygwin\r\n\"   specific commands.\r\n\"\r\n\" Platform:\r\n\"   Windows:\r\n\"     Requires cygwin (http:\/\/cygwin.com).\r\n\"   *nux:\r\n\"     Should be safe to use any function defined within on *nix systems\r\n\"     since each function checks the platform before running system\r\n\"     specific commands.\r\n\"\r\n\"     However, if you don't want *nix users to have a dependency on this\r\n\"     plugin, you may define proxy functions that first check if a function\r\n\"     is defined before using it.\r\n\"\r\n\"     Ex. Defining a proxy function for translating paths based on OS.\r\n\"       function! s:DeterminePath (path)\r\n\"         if exists(\"*CygwinPath\")\r\n\"           return CygwinPath(a:path)\r\n\"         endif\r\n\"         return a:path\r\n\"       endfunction\r\n\"\r\n\" Configuration:\r\n\"   Note: Configuration is only necessary on Windows machines.\r\n\"\r\n\"   g:CygwinHome\r\n\"     Set this to the location of your cygwin installation dir.\r\n\"     Ex.\r\n\"       let g:CygwinHome = 'c:\/cygwin'\r\n\"     Note: Be careful using '\\\\' in double quoted strings since\r\n\"     that represents the start of an escape character in vim.\r\n\"\r\n\"   On windows you will need to add your cygwin\/bin directory to\r\n\"   your WINDOWS path.\r\n\"     PATH=%CYGWIN_HOME%\\bin;%PATH%\r\n\"   So that unix commands can be executed from your dos console.\r\n\"\r\n\"   Also, I had issues using Windows' default temp directory.\r\n\"   Vim continually had issues accessing temp files (that I have\r\n\"   no control over).  It seems it was due to the spaces in the\r\n\"   directory path, so I changed my system %TMP% and %TEMP%\r\n\"   variables to point to c:\\cygwin\\tmp instead, and that solved\r\n\"   my issues.  You may have to do the same.\r\n\"\r\n\" Limitations:\r\n\"   All file and directory paths used in cygwin commands need to\r\n\"   be absolute.  When the vim shell is set to a cygwin shell, the\r\n\"   shell defaults to executing in the user's home directory.\r\n\"   Because of this, relative paths cannot be used.\r\n","install_details":"put in your plugin directory and read the Description section of the plugin for configuration details.","5":"put in your plugin directory and read the Description section of the plugin for configuration details.","first_name":"Eric","6":"Eric","last_name":"Van Dewoestine","7":"Van Dewoestine","releases":[{"0":"1150","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"cygwin_utils.vim","4":"cygwin_utils.vim","src_id":"3682","5":"3682","creation_date":"1102258031","6":"1102258031"}]},"1149":{"script_id":"1149","0":"1149","script_name":"GetFDCText.vim","1":"GetFDCText.vim","script_type":"utility","2":"utility","summary":"Returns a string, to be displayed for a closed fold","3":"Returns a string, to be displayed for a closed fold","description":"Tries to find a meaningful text that should be displayed in the folded column.\r\nIf something is meaningful is decided by a regular expression provided by the user.\r\nIt does *not* decide when and how a fold is made, nor what is to be folded away.\r\n\r\n","4":"Tries to find a meaningful text that should be displayed in the folded column.\r\nIf something is meaningful is decided by a regular expression provided by the user.\r\nIt does *not* decide when and how a fold is made, nor what is to be folded away.\r\n\r\n","install_details":"Drop the script in your plugin directory and set some of the script specific variables in \r\nyour .vimrc or _vimrc as appropriate. For details on the variables please have a look in the\r\ndocumentation that comes with the plugin.\r\n","5":"Drop the script in your plugin directory and set some of the script specific variables in \r\nyour .vimrc or _vimrc as appropriate. For details on the variables please have a look in the\r\ndocumentation that comes with the plugin.\r\n","first_name":"Lars","6":"Lars","last_name":"Wilke","7":"Wilke","releases":[{"0":"1149","vim_version":"6.0","1":"6.0","script_version":"0.1.0","2":"0.1.0","version_comment":"Now it is really gzipped.","3":"Now it is really gzipped.","package":"GetFDCText.tar.gz","4":"GetFDCText.tar.gz","src_id":"3681","5":"3681","creation_date":"1102240751","6":"1102240751"},{"0":"1149","vim_version":"6.0","1":"6.0","script_version":"0.1.0","2":"0.1.0","version_comment":"Initial upload","3":"Initial upload","package":"GetFDCText.tar.gz","4":"GetFDCText.tar.gz","src_id":"3680","5":"3680","creation_date":"1102240285","6":"1102240285"}]},"1148":{"script_id":"1148","0":"1148","script_name":"perl-test-manage.vim","1":"perl-test-manage.vim","script_type":"utility","2":"utility","summary":"Keep Track of the Number of Tests in a Perl Test File","3":"Keep Track of the Number of Tests in a Perl Test File","description":"NOTE!!! This script is deprecated and was superseded by the Test-Count CPAN module:\r\n\r\nhttp:\/\/search.cpan.org\/dist\/Test-Count\/\r\n\r\nPlease look into Test-Count which, despite being written in Perl, also supports some other programming languages and is more generic.\r\n\r\n========================\r\n \r\nThis script helps keeping track of the number of tests in a Perl test\r\nfile (t\/*.t) by counting '# TEST' comments.\r\n\r\nIn order to keep track of the number of tests you need to have a statement\r\nlike:\r\n\r\n    use Test::More tests => 20\r\n\r\nat the beginning of the test file. Then you need to make sure, every test\r\nhas a corresponding '# TEST' comment. If you run several tests in a loop,\r\nyou can append asterisks plus number to the comment. So for example the \r\ncomment:\r\n\r\n    # TEST*3*5\r\n\r\nwill add 15 tests to the test number.\r\n\r\n","4":"NOTE!!! This script is deprecated and was superseded by the Test-Count CPAN module:\r\n\r\nhttp:\/\/search.cpan.org\/dist\/Test-Count\/\r\n\r\nPlease look into Test-Count which, despite being written in Perl, also supports some other programming languages and is more generic.\r\n\r\n========================\r\n \r\nThis script helps keeping track of the number of tests in a Perl test\r\nfile (t\/*.t) by counting '# TEST' comments.\r\n\r\nIn order to keep track of the number of tests you need to have a statement\r\nlike:\r\n\r\n    use Test::More tests => 20\r\n\r\nat the beginning of the test file. Then you need to make sure, every test\r\nhas a corresponding '# TEST' comment. If you run several tests in a loop,\r\nyou can append asterisks plus number to the comment. So for example the \r\ncomment:\r\n\r\n    # TEST*3*5\r\n\r\nwill add 15 tests to the test number.\r\n\r\n","install_details":"","5":"","first_name":"Shlomi","6":"Shlomi","last_name":"Fish","7":"Fish","releases":[{"0":"1148","vim_version":"6.0","1":"6.0","script_version":"0.3.0","2":"0.3.0","version_comment":"Refactoring","3":"Refactoring","package":"perl-test-manage.vim","4":"perl-test-manage.vim","src_id":"4948","5":"4948","creation_date":"1136462727","6":"1136462727"},{"0":"1148","vim_version":"6.0","1":"6.0","script_version":"0.2","2":"0.2","version_comment":"Initial upload","3":"Initial upload","package":"perl-test-manage.vim","4":"perl-test-manage.vim","src_id":"3672","5":"3672","creation_date":"1101959561","6":"1101959561"}]},"1147":{"script_id":"1147","0":"1147","script_name":"bufkill.vim","1":"bufkill.vim","script_type":"utility","2":"utility","summary":"Unload\/delete\/wipe a buffer, keep its window(s), display last accessed buffer(s)","3":"Unload\/delete\/wipe a buffer, keep its window(s), display last accessed buffer(s)","description":"NOTE! This location is no longer the latest code - it's moved to github, and set up as a pathogen-style bundle, here:\r\n\r\nhttps:\/\/github.com\/qpkorr\/vim-bufkill\r\n\r\n\r\nBasic Usage:\r\nWhen you want to unload\/delete\/wipe a buffer, use:\r\n  :bun\/:bd\/:bw to close the window as well (vim command), or\r\n  :BUN\/:BD\/:BW to leave the window(s) intact (this script).\r\nTo move backwards and forwards through the chronological \r\nlist of buffers accessed, use :BB and :BF, respectively.\r\nMappings are also defined.\r\n\r\nDetailed Description: \r\nThis is a script to \r\na) unload, delete or wipe a buffer without closing the window (or windows) \r\n    it was displayed in\r\nb) in its place, display the buffer most recently used in each window \r\n    it was displayed in.  This selection is taken from the full list of \r\n    buffers ever displayed in each respective window (since vim was started)\r\nc) allow one level of undo in case you kill a buffer then change your mind\r\nd) allow various customizations via option variables\r\n\r\nSince the script maintains a list of buffer access order for each window, \r\ncommands are also provided to move backwards and forwards between \r\nthe buffers in this order, similar to going backwards and forwards in a\r\nweb browser.\r\n\r\nThe inspiration for this script came from\r\na) my own frustration with vim's lack of this functionality\r\nb) the description of the emacs kill-buffer command in vimtip #622\r\n   (this script basically duplicates this command I believe,\r\n   not sure about the undo functionality)\r\nc) comments and many mails from Keith Roberts when the issue was \r\n   raised in the vim@vim.org mailing list.","4":"NOTE! This location is no longer the latest code - it's moved to github, and set up as a pathogen-style bundle, here:\r\n\r\nhttps:\/\/github.com\/qpkorr\/vim-bufkill\r\n\r\n\r\nBasic Usage:\r\nWhen you want to unload\/delete\/wipe a buffer, use:\r\n  :bun\/:bd\/:bw to close the window as well (vim command), or\r\n  :BUN\/:BD\/:BW to leave the window(s) intact (this script).\r\nTo move backwards and forwards through the chronological \r\nlist of buffers accessed, use :BB and :BF, respectively.\r\nMappings are also defined.\r\n\r\nDetailed Description: \r\nThis is a script to \r\na) unload, delete or wipe a buffer without closing the window (or windows) \r\n    it was displayed in\r\nb) in its place, display the buffer most recently used in each window \r\n    it was displayed in.  This selection is taken from the full list of \r\n    buffers ever displayed in each respective window (since vim was started)\r\nc) allow one level of undo in case you kill a buffer then change your mind\r\nd) allow various customizations via option variables\r\n\r\nSince the script maintains a list of buffer access order for each window, \r\ncommands are also provided to move backwards and forwards between \r\nthe buffers in this order, similar to going backwards and forwards in a\r\nweb browser.\r\n\r\nThe inspiration for this script came from\r\na) my own frustration with vim's lack of this functionality\r\nb) the description of the emacs kill-buffer command in vimtip #622\r\n   (this script basically duplicates this command I believe,\r\n   not sure about the undo functionality)\r\nc) comments and many mails from Keith Roberts when the issue was \r\n   raised in the vim@vim.org mailing list.","install_details":"The usual - drop the file into your $HOME\/.vim\/plugin directory (unix)\r\nor $HOME\/vimfiles\/plugin directory (Windows), etc.\r\nUse the commands\/mappings defined to invoke the functionality \r\n(or redefine them elsewhere to what you want), and set the \r\nUser Configurable Variables as desired.  You should be able to make\r\nany customisations to the controls in your vimrc file, such that \r\nupdating to new versions of this script won't affect your settings.","5":"The usual - drop the file into your $HOME\/.vim\/plugin directory (unix)\r\nor $HOME\/vimfiles\/plugin directory (Windows), etc.\r\nUse the commands\/mappings defined to invoke the functionality \r\n(or redefine them elsewhere to what you want), and set the \r\nUser Configurable Variables as desired.  You should be able to make\r\nany customisations to the controls in your vimrc file, such that \r\nupdating to new versions of this script won't affect your settings.","first_name":"John","6":"John","last_name":"Orr","7":"Orr","releases":[{"0":"1147","vim_version":"7.0","1":"7.0","script_version":"1.11","2":"1.11","version_comment":"Major bug fixes by David Emett, especially relating to\r\nthe creation of new buffers when the last buffer is killed.\r\nAlso improved restoring of column on console vim.\r\nKey mappings can be disabled by setting g:BufKillCreateMappings to 0\r\n(thanks to various contributors)\r\n","3":"Major bug fixes by David Emett, especially relating to\r\nthe creation of new buffers when the last buffer is killed.\r\nAlso improved restoring of column on console vim.\r\nKey mappings can be disabled by setting g:BufKillCreateMappings to 0\r\n(thanks to various contributors)\r\n","package":"bufkill.vim","4":"bufkill.vim","src_id":"19161","5":"19161","creation_date":"1355184145","6":"1355184145"},{"0":"1147","vim_version":"7.0","1":"7.0","script_version":"1.10","2":"1.10","version_comment":"Improved handling of quickfix buffers, and various other fixes","3":"Improved handling of quickfix buffers, and various other fixes","package":"bufkill.vim","4":"bufkill.vim","src_id":"15905","5":"15905","creation_date":"1308194155","6":"1308194155"},{"0":"1147","vim_version":"7.0","1":"7.0","script_version":"1.9","2":"1.9","version_comment":"Remove unnecessary mapping delays, and a debug message","3":"Remove unnecessary mapping delays, and a debug message","package":"bufkill.vim","4":"bufkill.vim","src_id":"14660","5":"14660","creation_date":"1293748867","6":"1293748867"},{"0":"1147","vim_version":"7.0","1":"7.0","script_version":"1.8","2":"1.8","version_comment":"Improved mapping handling, and robustness","3":"Improved mapping handling, and robustness","package":"bufkill.vim","4":"bufkill.vim","src_id":"14658","5":"14658","creation_date":"1293714008","6":"1293714008"},{"0":"1147","vim_version":"7.0","1":"7.0","script_version":"1.7","2":"1.7","version_comment":"Convert to Vim 7 lists instead of string-based lists.\r\nAdd buffer navigation (move backwards and forwards through most recently used buffers), support for scratch buffer removal.\r\nImproved honouring of the 'confirm' vim option - thanks Magnus Thor Torfason\r\nAdded (opt-in) Ctrl-^ override support to preserve cursor column.\r\nMinor additional improvements.\r\n","3":"Convert to Vim 7 lists instead of string-based lists.\r\nAdd buffer navigation (move backwards and forwards through most recently used buffers), support for scratch buffer removal.\r\nImproved honouring of the 'confirm' vim option - thanks Magnus Thor Torfason\r\nAdded (opt-in) Ctrl-^ override support to preserve cursor column.\r\nMinor additional improvements.\r\n","package":"bufkill.vim","4":"bufkill.vim","src_id":"13169","5":"13169","creation_date":"1276342379","6":"1276342379"},{"0":"1147","vim_version":"6.0","1":"6.0","script_version":"1.2","2":"1.2","version_comment":"Add column-saving support, to ensure returning to a buffer means positioning the cursor not only at the right line, but also column.\r\nLast version that will (should...) work with Vim 6.0.","3":"Add column-saving support, to ensure returning to a buffer means positioning the cursor not only at the right line, but also column.\r\nLast version that will (should...) work with Vim 6.0.","package":"bufkill.vim","4":"bufkill.vim","src_id":"13168","5":"13168","creation_date":"1276342178","6":"1276342178"},{"0":"1147","vim_version":"6.0","1":"6.0","script_version":"1.1","2":"1.1","version_comment":"Fix handling of modified, un-named buffers","3":"Fix handling of modified, un-named buffers","package":"bufkill.vim","4":"bufkill.vim","src_id":"3671","5":"3671","creation_date":"1101940036","6":"1101940036"},{"0":"1147","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"bufkill.vim","4":"bufkill.vim","src_id":"3670","5":"3670","creation_date":"1101921588","6":"1101921588"}]},"1146":{"script_id":"1146","0":"1146","script_name":"ccimpl.vim","1":"ccimpl.vim","script_type":"ftplugin","2":"ftplugin","summary":"Generates a skeleton implementation of classes defined in a C++ header file.","3":"Generates a skeleton implementation of classes defined in a C++ header file.","description":"This script defines a function Implement(), that when called from a C++ header file generates a skeleton implementation of the classes defined in the header, in a new vertical window.\r\n\r\nThis is great for defining and documenting the interface to a class and then using this function to generate a skeleton implementation to be filled in.\r\n\r\nTODO: Handle functions outside of classes and thus C compatibility.\r\n            Implement static member initialization.","4":"This script defines a function Implement(), that when called from a C++ header file generates a skeleton implementation of the classes defined in the header, in a new vertical window.\r\n\r\nThis is great for defining and documenting the interface to a class and then using this function to generate a skeleton implementation to be filled in.\r\n\r\nTODO: Handle functions outside of classes and thus C compatibility.\r\n            Implement static member initialization.","install_details":"Place the script in the plugins directory.","5":"Place the script in the plugins directory.","first_name":"Neil","6":"Neil","last_name":"Vice","7":"Vice","releases":[{"0":"1146","vim_version":"6.0","1":"6.0","script_version":"0.6","2":"0.6","version_comment":"Defined g:h_extensions variable as a comma separated list of c++ header-file extentions that the script will support.\r\nImproved robustness and fixed some minor issues.","3":"Defined g:h_extensions variable as a comma separated list of c++ header-file extentions that the script will support.\r\nImproved robustness and fixed some minor issues.","package":"ccimpl.vim","4":"ccimpl.vim","src_id":"4875","5":"4875","creation_date":"1134155232","6":"1134155232"},{"0":"1146","vim_version":"6.0","1":"6.0","script_version":"0.5","2":"0.5","version_comment":"Fixed bug where if g:InterFunctionGap = 1 then no newline was inserted at the end of the file.\r\nFixed bug where the header file was not #included if the implementation file began empty.","3":"Fixed bug where if g:InterFunctionGap = 1 then no newline was inserted at the end of the file.\r\nFixed bug where the header file was not #included if the implementation file began empty.","package":"ccimpl.vim","4":"ccimpl.vim","src_id":"4271","5":"4271","creation_date":"1115878861","6":"1115878861"},{"0":"1146","vim_version":"6.0","1":"6.0","script_version":"0.4.1","2":"0.4.1","version_comment":"Added global variable \\\"g:cxx_extension\\\" (defaults to \\\"cpp\\\") to use as extension of generated source file.","3":"Added global variable \\\"g:cxx_extension\\\" (defaults to \\\"cpp\\\") to use as extension of generated source file.","package":"ccimpl.vim","4":"ccimpl.vim","src_id":"4270","5":"4270","creation_date":"1115871419","6":"1115871419"},{"0":"1146","vim_version":"6.0","1":"6.0","script_version":"0.4","2":"0.4","version_comment":"Fixed to correctly handle destructors.\r\nFixed bug where 'method-like' constructs in attribute comments would cause them to be treated as methods.\r\nNo longer copies comments to the implementation by default - set g:implComments=1 to achieve the old functionality.","3":"Fixed to correctly handle destructors.\r\nFixed bug where 'method-like' constructs in attribute comments would cause them to be treated as methods.\r\nNo longer copies comments to the implementation by default - set g:implComments=1 to achieve the old functionality.","package":"ccimpl.vim","4":"ccimpl.vim","src_id":"4225","5":"4225","creation_date":"1114893135","6":"1114893135"},{"0":"1146","vim_version":"6.0","1":"6.0","script_version":"0.3","2":"0.3","version_comment":"Improved window handling - may fix incompatibilities with other plugins.\r\nHandles default parameters.\r\nIgnores brackets in Doxygen comment blocks.\r\nAdded 'g:fnTypeSepLine' flag that when set to 1 (default 0) forces return types onto a separate line.","3":"Improved window handling - may fix incompatibilities with other plugins.\r\nHandles default parameters.\r\nIgnores brackets in Doxygen comment blocks.\r\nAdded 'g:fnTypeSepLine' flag that when set to 1 (default 0) forces return types onto a separate line.","package":"ccimpl.vim","4":"ccimpl.vim","src_id":"4206","5":"4206","creation_date":"1114583100","6":"1114583100"},{"0":"1146","vim_version":"6.0","1":"6.0","script_version":"0.2.1","2":"0.2.1","version_comment":"Prevented the absence of a namespace declaration from causing errors.","3":"Prevented the absence of a namespace declaration from causing errors.","package":"ccimpl.vim","4":"ccimpl.vim","src_id":"4203","5":"4203","creation_date":"1114491145","6":"1114491145"},{"0":"1146","vim_version":"6.0","1":"6.0","script_version":"0.2","2":"0.2","version_comment":"Added support for namespaces.\nImproved comment indenting.\nFixed bug: functions including namespace directives would be ignored.\nFixed bug: the end of a class would be ignored if not at the start of the line.\n","3":"Added support for namespaces.\nImproved comment indenting.\nFixed bug: functions including namespace directives would be ignored.\nFixed bug: the end of a class would be ignored if not at the start of the line.\n","package":"ccimpl.vim","4":"ccimpl.vim","src_id":"3690","5":"3690","creation_date":"1102557076","6":"1102557076"},{"0":"1146","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"ccimpl.vim","4":"ccimpl.vim","src_id":"3669","5":"3669","creation_date":"1101883688","6":"1101883688"}]},"1145":{"script_id":"1145","0":"1145","script_name":"C-fold","1":"C-fold","script_type":"ftplugin","2":"ftplugin","summary":"Automates folding and unfolding C & C++ comments and code blocks.","3":"Automates folding and unfolding C & C++ comments and code blocks.","description":"Automatically folds all blocks (i.e. { } ) in C and C++ and defines a function that performs a command e.g. zo on all folds beginning with text that matches a given pattern.\r\n\r\nThis allows for the following mappings defined by the plugin:\r\n\r\n      z[ - Opens all doxygen-style comments\r\n      z] - Closes all doxygen-style comments\r\n      z{ - Opens all code blocks (i.e. {  })\r\n      z} - Closes all code blocks","4":"Automatically folds all blocks (i.e. { } ) in C and C++ and defines a function that performs a command e.g. zo on all folds beginning with text that matches a given pattern.\r\n\r\nThis allows for the following mappings defined by the plugin:\r\n\r\n      z[ - Opens all doxygen-style comments\r\n      z] - Closes all doxygen-style comments\r\n      z{ - Opens all code blocks (i.e. {  })\r\n      z} - Closes all code blocks","install_details":"Extract the archive from your home directory. This will extract the following files:\r\n      .vim\/plugins\/cfold.vim\r\n      .vim\/after\/syntax\/c.vim\r\n\r\nAlso requires the folding of Doxygen-style comments. This requires vimscript #5. This can be done easily by adding the 'fold' keyword to the end of the 'doxygenComment' region in the 'doxygen.vim' syntax file:\r\n\r\n      syn region doxygenComment start= ... keepend fold\r\n\r\nAdditional languages can be supported as appropriate (e.g. Java) by copying 'c.vim' and renaming to the syntax file for the language (e.g. java.vim).\r\n","5":"Extract the archive from your home directory. This will extract the following files:\r\n      .vim\/plugins\/cfold.vim\r\n      .vim\/after\/syntax\/c.vim\r\n\r\nAlso requires the folding of Doxygen-style comments. This requires vimscript #5. This can be done easily by adding the 'fold' keyword to the end of the 'doxygenComment' region in the 'doxygen.vim' syntax file:\r\n\r\n      syn region doxygenComment start= ... keepend fold\r\n\r\nAdditional languages can be supported as appropriate (e.g. Java) by copying 'c.vim' and renaming to the syntax file for the language (e.g. java.vim).\r\n","first_name":"Neil","6":"Neil","last_name":"Vice","7":"Vice","releases":[{"0":"1145","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"cfold.tar.bz2","4":"cfold.tar.bz2","src_id":"3668","5":"3668","creation_date":"1101786032","6":"1101786032"}]},"1144":{"script_id":"1144","0":"1144","script_name":"jhdark","1":"jhdark","script_type":"color scheme","2":"color scheme","summary":"A dark colorscheme for gui and console","3":"A dark colorscheme for gui and console","description":"See http:\/\/planetxml.de\/vim-colorscheme.php for a screenshot.","4":"See http:\/\/planetxml.de\/vim-colorscheme.php for a screenshot.","install_details":"","5":"","first_name":"J\u00c3\u00b6rn","6":"J\u00c3\u00b6rn","last_name":"Horstmann","7":"Horstmann","releases":[{"0":"1144","vim_version":"6.0","1":"6.0","script_version":"1.1","2":"1.1","version_comment":"Small improvements for better contrast.","3":"Small improvements for better contrast.","package":"jhdark.vim","4":"jhdark.vim","src_id":"4467","5":"4467","creation_date":"1123309619","6":"1123309619"},{"0":"1144","vim_version":"6.0","1":"6.0","script_version":"0.9","2":"0.9","version_comment":"Initial upload","3":"Initial upload","package":"jhdark.vim","4":"jhdark.vim","src_id":"3667","5":"3667","creation_date":"1101705345","6":"1101705345"}]},"1143":{"script_id":"1143","0":"1143","script_name":"inkpot","1":"inkpot","script_type":"color scheme","2":"color scheme","summary":"Inkpot, a dark scheme for GUI and 88\/256 colour terms","3":"Inkpot, a dark scheme for GUI and 88\/256 colour terms","description":"A darkish scheme which works in the GUI and in some 88 colour terminals (urxvt, for example) and 256 colour terminals (xterm with TERM=xterm-256 seems to work). This won't work in regular 8\/16 colour terms, and depending upon your setup you may need to sacrifice a few goats to get the 88\/256 things to work.\r\n\r\nKeeping things up to date on vim.org is a nuisance. For the latest version, visit:\r\n\r\n    http:\/\/github.com\/ciaranm\/inkpot","4":"A darkish scheme which works in the GUI and in some 88 colour terminals (urxvt, for example) and 256 colour terminals (xterm with TERM=xterm-256 seems to work). This won't work in regular 8\/16 colour terms, and depending upon your setup you may need to sacrifice a few goats to get the 88\/256 things to work.\r\n\r\nKeeping things up to date on vim.org is a nuisance. For the latest version, visit:\r\n\r\n    http:\/\/github.com\/ciaranm\/inkpot","install_details":"Place in your ~\/.vim\/colors\/","5":"Place in your ~\/.vim\/colors\/","first_name":"Ciaran","6":"Ciaran","last_name":"McCreesh","7":"McCreesh","releases":[{"0":"1143","vim_version":"6.0","1":"6.0","script_version":"20091127","2":"20091127","version_comment":"Less garish search highlighting.\r\n\r\nUpdates will only be uploaded to vim.org sporadically. See github for the most recent version.","3":"Less garish search highlighting.\r\n\r\nUpdates will only be uploaded to vim.org sporadically. See github for the most recent version.","package":"inkpot.vim","4":"inkpot.vim","src_id":"11833","5":"11833","creation_date":"1259578478","6":"1259578478"},{"0":"1143","vim_version":"7.0","1":"7.0","script_version":"20060523","2":"20060523","version_comment":"Some updates for the new vim7 syntax groups.","3":"Some updates for the new vim7 syntax groups.","package":"inkpot.vim","4":"inkpot.vim","src_id":"5747","5":"5747","creation_date":"1148380153","6":"1148380153"}]},"1142":{"script_id":"1142","0":"1142","script_name":"header.vim","1":"header.vim","script_type":"utility","2":"utility","summary":"Adds a header -author, path, timestamp- when a new file is created.","3":"Adds a header -author, path, timestamp- when a new file is created.","description":"When a new file is created the plugin inserts automatically a customizable header on the top -filetype, author, timestamp-. When the file it's no new -so it's already created- the plugin checks the 'last modified' field in line number five -if this exists- and then it updates its value. It's my first vim plugin and it's very plain -I beg pardon to vim's gurus for my daring!- I didn't find anything alike, so I had to write my own script. Any correction or modification will be welcome. \r\n","4":"When a new file is created the plugin inserts automatically a customizable header on the top -filetype, author, timestamp-. When the file it's no new -so it's already created- the plugin checks the 'last modified' field in line number five -if this exists- and then it updates its value. It's my first vim plugin and it's very plain -I beg pardon to vim's gurus for my daring!- I didn't find anything alike, so I had to write my own script. Any correction or modification will be welcome. \r\n","install_details":"Easy! Copy the file to vim's plugin directory (global or personal) and run vim.","5":"Easy! Copy the file to vim's plugin directory (global or personal) and run vim.","first_name":"Francisco","6":"Francisco","last_name":"Piedrafita","7":"Piedrafita","releases":[{"0":"1142","vim_version":"7.0","1":"7.0","script_version":"0.2.0","2":"0.2.0","version_comment":"<Juno Devel> has improved the script. Instead of relying on matching the filetype with system calls, he founded that letting vim determining the filetype itself was easier and more robust).","3":"<Juno Devel> has improved the script. Instead of relying on matching the filetype with system calls, he founded that letting vim determining the filetype itself was easier and more robust).","package":"header.vim","4":"header.vim","src_id":"20985","5":"20985","creation_date":"1383209483","6":"1383209483"},{"0":"1142","vim_version":"7.0","1":"7.0","script_version":"0.1.3","2":"0.1.3","version_comment":"Some little bugs fixed","3":"Some little bugs fixed","package":"header.vim","4":"header.vim","src_id":"8632","5":"8632","creation_date":"1209652199","6":"1209652199"}]},"1141":{"script_id":"1141","0":"1141","script_name":"Cisco ACL syntax highlighting rules","1":"Cisco ACL syntax highlighting rules","script_type":"color scheme","2":"color scheme","summary":"provides highlighting for files with Cisco ACLs","3":"provides highlighting for files with Cisco ACLs","description":"This syntax highlighting script can be used for files which contain Cisco ACL rules. This is particulary usefull for Cisco ACL framework administration. (e.g. keeping ACLs in cvs, editing them and loading to Cisco boxes automatically)\r\n\r\nThis script can be used with aclcheck (http:\/\/techie.devnull.cz\/aclcheck)","4":"This syntax highlighting script can be used for files which contain Cisco ACL rules. This is particulary usefull for Cisco ACL framework administration. (e.g. keeping ACLs in cvs, editing them and loading to Cisco boxes automatically)\r\n\r\nThis script can be used with aclcheck (http:\/\/techie.devnull.cz\/aclcheck)","install_details":"copy ciscoacl.vim to your ~\/.vim\/syntax directory and add following lines to your ~\/.vimrc file:\r\n\r\naugroup filetype\r\n        au! BufRead,BufNewFile *.crules     set filetype=ciscoacl\r\n        au! BufRead,BufNewFile *.acl        set filetype=ciscoacl\r\naugroup END\r\n\r\nEvery file with .crules or .acl suffix will be displayed in vim using Cisco ACL highlighting rules.","5":"copy ciscoacl.vim to your ~\/.vim\/syntax directory and add following lines to your ~\/.vimrc file:\r\n\r\naugroup filetype\r\n        au! BufRead,BufNewFile *.crules     set filetype=ciscoacl\r\n        au! BufRead,BufNewFile *.acl        set filetype=ciscoacl\r\naugroup END\r\n\r\nEvery file with .crules or .acl suffix will be displayed in vim using Cisco ACL highlighting rules.","first_name":"Vladimir","6":"Vladimir","last_name":"Kotal","7":"Kotal","releases":[{"0":"1141","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"ciscoacl.vim","4":"ciscoacl.vim","src_id":"3651","5":"3651","creation_date":"1101193553","6":"1101193553"}]},"1140":{"script_id":"1140","0":"1140","script_name":"FileTree","1":"FileTree","script_type":"syntax","2":"syntax","summary":"A file tree similar to opsplorer","3":"A file tree similar to opsplorer","description":"A file tree exporer based on the tree.vim script.\r\nSince version 1.0 it has CD command and directory stack similar to shell's one.\r\nYou can use RFileTree command to split it on the right side of the window or similar LFileTree,BFileTree,TFileTree commands. FileTree command uses default values for placing window.\r\n\r\nI will gladly accept any \\(comments\\|bug reports\\|request for feature\\)\\+","4":"A file tree exporer based on the tree.vim script.\r\nSince version 1.0 it has CD command and directory stack similar to shell's one.\r\nYou can use RFileTree command to split it on the right side of the window or similar LFileTree,BFileTree,TFileTree commands. FileTree command uses default values for placing window.\r\n\r\nI will gladly accept any \\(comments\\|bug reports\\|request for feature\\)\\+","install_details":"To install this plugin you have to have tree.vim script installed.\r\nIf you have it installed then unpack archive to a vim directory.\r\nAnd ofcouse use :helptags <doc.dir>\r\nWhere <doc.dir> - directory where you have unpacked doc\/FileTree.txt","5":"To install this plugin you have to have tree.vim script installed.\r\nIf you have it installed then unpack archive to a vim directory.\r\nAnd ofcouse use :helptags <doc.dir>\r\nWhere <doc.dir> - directory where you have unpacked doc\/FileTree.txt","first_name":"Yury","6":"Yury","last_name":"Altukhou","7":"Altukhou","releases":[{"0":"1140","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Now it is work for systems with backslashes in paths. Added \"CD\" command and directory stack. Fixed coloring for terminal users.Also added few options and commands to show window up on any side.","3":"Now it is work for systems with backslashes in paths. Added \"CD\" command and directory stack. Fixed coloring for terminal users.Also added few options and commands to show window up on any side.","package":"FileTree.tgz","4":"FileTree.tgz","src_id":"3662","5":"3662","creation_date":"1101433934","6":"1101433934"},{"0":"1140","vim_version":"6.0","1":"6.0","script_version":"0.9","2":"0.9","version_comment":"Initial upload","3":"Initial upload","package":"FileTree.tgz","4":"FileTree.tgz","src_id":"3650","5":"3650","creation_date":"1101190048","6":"1101190048"}]},"1139":{"script_id":"1139","0":"1139","script_name":"tree","1":"tree","script_type":"utility","2":"utility","summary":"A treeview framework","3":"A treeview framework","description":"tree is an abstract framework for tree views. I've written a FileTree plugin based on it, which behaves like  Patrick Schiel's opsplore script. It takes callback functions to comunicate with the model  upon which it works. I plan to write JExplorer based on it.\r\nSee tree.txt for more detales.\r\n\r\n","4":"tree is an abstract framework for tree views. I've written a FileTree plugin based on it, which behaves like  Patrick Schiel's opsplore script. It takes callback functions to comunicate with the model  upon which it works. I plan to write JExplorer based on it.\r\nSee tree.txt for more detales.\r\n\r\n","install_details":"Unpack archive into vim directory. ","5":"Unpack archive into vim directory. ","first_name":"Yury","6":"Yury","last_name":"Altukhou","7":"Altukhou","releases":[{"0":"1139","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"small changes in the api, now tree window can be shown at any side.","3":"small changes in the api, now tree window can be shown at any side.","package":"tree.tgz","4":"tree.tgz","src_id":"3661","5":"3661","creation_date":"1101433430","6":"1101433430"},{"0":"1139","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"small changes in the api, now tree window can be shown at any side.","3":"small changes in the api, now tree window can be shown at any side.","package":"tree.tgz","4":"tree.tgz","src_id":"3660","5":"3660","creation_date":"1101433397","6":"1101433397"},{"0":"1139","vim_version":"6.0","1":"6.0","script_version":"0.9","2":"0.9","version_comment":"Initial upload","3":"Initial upload","package":"tree.tgz","4":"tree.tgz","src_id":"3649","5":"3649","creation_date":"1101189655","6":"1101189655"}]},"1138":{"script_id":"1138","0":"1138","script_name":"scilab.tar.gz","1":"scilab.tar.gz","script_type":"indent","2":"indent","summary":"Indent file for Scilab.","3":"Indent file for Scilab.","description":"Script provides indenting for Scilab, a scientific software package for numerical computations similar to Matlab (http:\/\/www.scilab.org). Screenshot: http:\/\/vamo.euweb.cz\/vim\/scilab\/scilab.png\r\nThere is a script for syntax hilighting (vimscript#1137).","4":"Script provides indenting for Scilab, a scientific software package for numerical computations similar to Matlab (http:\/\/www.scilab.org). Screenshot: http:\/\/vamo.euweb.cz\/vim\/scilab\/scilab.png\r\nThere is a script for syntax hilighting (vimscript#1137).","install_details":"Like a standard indent file.","5":"Like a standard indent file.","first_name":"Vaclav","6":"Vaclav","last_name":"Mocek","7":"Mocek","releases":[{"0":"1138","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"scilab.vim.gz","4":"scilab.vim.gz","src_id":"3645","5":"3645","creation_date":"1100953305","6":"1100953305"}]},"1137":{"script_id":"1137","0":"1137","script_name":"scilab.tar.gz","1":"scilab.tar.gz","script_type":"syntax","2":"syntax","summary":"Syntax file for Scilab.","3":"Syntax file for Scilab.","description":"Script provides syntax hilighting for Scilab, a scientific software package for numerical computations similar to Matlab  (http:\/\/www.scilab.org).  Screenshot: http:\/\/vamo.euweb.cz\/vim\/scilab\/scilab.png\r\nThere is a script for indenting (vimscript#1138).","4":"Script provides syntax hilighting for Scilab, a scientific software package for numerical computations similar to Matlab  (http:\/\/www.scilab.org).  Screenshot: http:\/\/vamo.euweb.cz\/vim\/scilab\/scilab.png\r\nThere is a script for indenting (vimscript#1138).","install_details":"Like a standard syntax file.","5":"Like a standard syntax file.","first_name":"Vaclav","6":"Vaclav","last_name":"Mocek","7":"Mocek","releases":[{"0":"1137","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"scilab.vim.gz","4":"scilab.vim.gz","src_id":"3644","5":"3644","creation_date":"1100953289","6":"1100953289"}]},"1136":{"script_id":"1136","0":"1136","script_name":"vcbc.vim","1":"vcbc.vim","script_type":"color scheme","2":"color scheme","summary":"Colorscheme based on Visual C++ 6.0 and Beyond Compare (for diffs).","3":"Colorscheme based on Visual C++ 6.0 and Beyond Compare (for diffs).","description":"A colorscheme based on the colors in Visual C++ 6.0 for syntax highlighting with some modifications, and a colors for diffs based on the colors for Beyond Compare.","4":"A colorscheme based on the colors in Visual C++ 6.0 for syntax highlighting with some modifications, and a colors for diffs based on the colors for Beyond Compare.","install_details":"Place in your $VIMRUNTIME\/colors or $HOME\/vimfiles\/colors.","5":"Place in your $VIMRUNTIME\/colors or $HOME\/vimfiles\/colors.","first_name":"Rajas","6":"Rajas","last_name":"Sambhare","7":"Sambhare","releases":[{"0":"1136","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"vcbc.vim","4":"vcbc.vim","src_id":"3641","5":"3641","creation_date":"1100779092","6":"1100779092"}]},"1135":{"script_id":"1135","0":"1135","script_name":"Japanese Keymapping","1":"Japanese Keymapping","script_type":"utility","2":"utility","summary":"Provides keymapping for Japanese Hiragana and Katakana letters","3":"Provides keymapping for Japanese Hiragana and Katakana letters","description":"This packages contains keymappings for 2 Japanese alphabets, Hiragana and Katakana. This one allows on to enter the phonetic equivalent of the characters and it will translated into the correct unicode character for that letter.","4":"This packages contains keymappings for 2 Japanese alphabets, Hiragana and Katakana. This one allows on to enter the phonetic equivalent of the characters and it will translated into the correct unicode character for that letter.","install_details":"Place kana.vim in your keymap directory. (or see the README)","5":"Place kana.vim in your keymap directory. (or see the README)","first_name":"Rory","6":"Rory","last_name":"McCann","7":"McCann","releases":[{"0":"1135","vim_version":"6.0","1":"6.0","script_version":"1.2","2":"1.2","version_comment":"Forgot to include the README with the last version.","3":"Forgot to include the README with the last version.","package":"kana.zip","4":"kana.zip","src_id":"3824","5":"3824","creation_date":"1107256865","6":"1107256865"},{"0":"1135","vim_version":"6.0","1":"6.0","script_version":"1.1","2":"1.1","version_comment":"Dan Kenigsberg noticed some deficiencies and suggested this one instead.\r\n","3":"Dan Kenigsberg noticed some deficiencies and suggested this one instead.\r\n","package":"kana.zip","4":"kana.zip","src_id":"3821","5":"3821","creation_date":"1107235181","6":"1107235181"},{"0":"1135","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"JapaneseCharacter.tar.bz2","4":"JapaneseCharacter.tar.bz2","src_id":"3638","5":"3638","creation_date":"1100587324","6":"1100587324"}]},"1134":{"script_id":"1134","0":"1134","script_name":"scratch.vim","1":"scratch.vim","script_type":"utility","2":"utility","summary":"a plugin to create a scratch buffer","3":"a plugin to create a scratch buffer","description":"    this script creates a scratch buffer like what emacs does for you, you can write anything there, but its content will not be saved, so DONT put any important things in scrath buffer! Several commands and keymaps will help you.\r\n\r\n\r\nUsage:\r\n    you can press <F4>s to open the scratch buffer window, and close it by press <F4>s again. the contents of the scratch buffer will not be lost until you quit Vim.\r\n\r\n    <F4><S-s> will paste from register \" to the scratch buffer. A blank line is added between pasting.\r\n\r\n    You can have only one scratch buffer open in a single Vim instance.\r\n\r\n    scratch.vim itself contains detailed description in both English and Chinese.\r\n\r\n\r\n    this scratch.vim is part of Bruce Who's vim package which is not fully finished.\r\n\r\n========================================\r\n\r\n中文简介(chinese)\r\n此脚本用于创建一个scratch缓冲区，你可以在这里打草稿，写一些临时的内容而不必创建一个文件，呵呵。但是退出vim后这个缓冲区的内容会消失，所以不要在这里写重要的东西！还定义了一些命令和快捷键。\r\n\r\nscratch.vim本身有更详细的说明。","4":"    this script creates a scratch buffer like what emacs does for you, you can write anything there, but its content will not be saved, so DONT put any important things in scrath buffer! Several commands and keymaps will help you.\r\n\r\n\r\nUsage:\r\n    you can press <F4>s to open the scratch buffer window, and close it by press <F4>s again. the contents of the scratch buffer will not be lost until you quit Vim.\r\n\r\n    <F4><S-s> will paste from register \" to the scratch buffer. A blank line is added between pasting.\r\n\r\n    You can have only one scratch buffer open in a single Vim instance.\r\n\r\n    scratch.vim itself contains detailed description in both English and Chinese.\r\n\r\n\r\n    this scratch.vim is part of Bruce Who's vim package which is not fully finished.\r\n\r\n========================================\r\n\r\n中文简介(chinese)\r\n此脚本用于创建一个scratch缓冲区，你可以在这里打草稿，写一些临时的内容而不必创建一个文件，呵呵。但是退出vim后这个缓冲区的内容会消失，所以不要在这里写重要的东西！还定义了一些命令和快捷键。\r\n\r\nscratch.vim本身有更详细的说明。","install_details":"Drop it into one of your plugin directories","5":"Drop it into one of your plugin directories","first_name":"Bruce","6":"Bruce","last_name":"Who","7":"Who","releases":[{"0":"1134","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"scratch.vim","4":"scratch.vim","src_id":"3634","5":"3634","creation_date":"1100454985","6":"1100454985"}]},"1133":{"script_id":"1133","0":"1133","script_name":"css.vim","1":"css.vim","script_type":"syntax","2":"syntax","summary":"CSS with ASP.NET Support","3":"CSS with ASP.NET Support","description":"CSS with ASP.NET Support (.css.aspx)\r\n\r\nIt colors only directives, not C# or VB.NET code.","4":"CSS with ASP.NET Support (.css.aspx)\r\n\r\nIt colors only directives, not C# or VB.NET code.","install_details":"Override vim\/vim63\/syntax\/css.vim with the script. (Copying to vimfiles\/syntax\/ may not work) \r\n\r\nAdd the following line to your vimrc: \r\nau BufRead,BufNewFile *.css.aspx setlocal filetype=css \r\n","5":"Override vim\/vim63\/syntax\/css.vim with the script. (Copying to vimfiles\/syntax\/ may not work) \r\n\r\nAdd the following line to your vimrc: \r\nau BufRead,BufNewFile *.css.aspx setlocal filetype=css \r\n","first_name":"Aquila","6":"Aquila","last_name":"Deus","7":"Deus","releases":[{"0":"1133","vim_version":"6.0","1":"6.0","script_version":"0.9","2":"0.9","version_comment":"Initial upload","3":"Initial upload","package":"css.vim","4":"css.vim","src_id":"3633","5":"3633","creation_date":"1100427547","6":"1100427547"}]},"1132":{"script_id":"1132","0":"1132","script_name":"javascript.vim","1":"javascript.vim","script_type":"syntax","2":"syntax","summary":"JavaScript with ASP.NET support","3":"JavaScript with ASP.NET support","description":"JavaScript with ASP.NET support (.js.aspx)\r\n\r\nIt colors only directives, not C# or VB.NET code.","4":"JavaScript with ASP.NET support (.js.aspx)\r\n\r\nIt colors only directives, not C# or VB.NET code.","install_details":"Override vim\/vim63\/syntax\/javascript.vim with the script. (Copying to vimfiles\/syntax\/ may not work)\r\n\r\nAdd the following line to your vimrc:\r\nau BufRead,BufNewFile *.js.aspx setlocal filetype=javascript\r\n","5":"Override vim\/vim63\/syntax\/javascript.vim with the script. (Copying to vimfiles\/syntax\/ may not work)\r\n\r\nAdd the following line to your vimrc:\r\nau BufRead,BufNewFile *.js.aspx setlocal filetype=javascript\r\n","first_name":"Aquila","6":"Aquila","last_name":"Deus","7":"Deus","releases":[{"0":"1132","vim_version":"6.0","1":"6.0","script_version":"0.9","2":"0.9","version_comment":"Initial upload","3":"Initial upload","package":"javascript.vim","4":"javascript.vim","src_id":"3632","5":"3632","creation_date":"1100427395","6":"1100427395"}]},"1131":{"script_id":"1131","0":"1131","script_name":"jhlight.vim","1":"jhlight.vim","script_type":"color scheme","2":"color scheme","summary":"A colorscheme with a light grey background","3":"A colorscheme with a light grey background","description":"A screenshot is available at http:\/\/planetxml.de\/vim-colorscheme.php","4":"A screenshot is available at http:\/\/planetxml.de\/vim-colorscheme.php","install_details":"","5":"","first_name":"J\u00c3\u00b6rn","6":"J\u00c3\u00b6rn","last_name":"Horstmann","7":"Horstmann","releases":[{"0":"1131","vim_version":"6.0","1":"6.0","script_version":"1.1","2":"1.1","version_comment":"Small improvements for better contrast.","3":"Small improvements for better contrast.","package":"jhlight.vim","4":"jhlight.vim","src_id":"4468","5":"4468","creation_date":"1123309726","6":"1123309726"},{"0":"1131","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"jhlight.vim","4":"jhlight.vim","src_id":"3631","5":"3631","creation_date":"1100412553","6":"1100412553"}]},"1130":{"script_id":"1130","0":"1130","script_name":"vim_faq.vim","1":"vim_faq.vim","script_type":"utility","2":"utility","summary":"script to install the Vim FAQ as a Vim help file","3":"script to install the Vim FAQ as a Vim help file","description":"This is the script with which Yegappan Lakshmanan generated the Vim FAQ in Vim Help format. \r\n\r\nIf you're just interested in the Vim FAQ in Vim Help format you might as well get it here: http:\/\/www.geocities.com\/yegappan\/vim_faq_help.txt . But if you'd like to help (Yegappan and) me improve this script (or just have a look at this script out of curiosity) you might want to download this script.\r\n\r\nThere's no documentation. The script should have enough comments to explain itself.","4":"This is the script with which Yegappan Lakshmanan generated the Vim FAQ in Vim Help format. \r\n\r\nIf you're just interested in the Vim FAQ in Vim Help format you might as well get it here: http:\/\/www.geocities.com\/yegappan\/vim_faq_help.txt . But if you'd like to help (Yegappan and) me improve this script (or just have a look at this script out of curiosity) you might want to download this script.\r\n\r\nThere's no documentation. The script should have enough comments to explain itself.","install_details":"Installation is straightforward: either put vim_faq.vim in your plugin directory or source vim_faq.vim.\r\n\r\nThis should supply with just one new function: VimifyAndInstallFaq( ..., ...)","5":"Installation is straightforward: either put vim_faq.vim in your plugin directory or source vim_faq.vim.\r\n\r\nThis should supply with just one new function: VimifyAndInstallFaq( ..., ...)","first_name":"Paul","6":"Paul","last_name":"Bolle","7":"Bolle","releases":[{"0":"1130","vim_version":"6.0","1":"6.0","script_version":"0.2","2":"0.2","version_comment":"Initial upload","3":"Initial upload","package":"vim_faq.vim","4":"vim_faq.vim","src_id":"3630","5":"3630","creation_date":"1100402269","6":"1100402269"}]},"1129":{"script_id":"1129","0":"1129","script_name":"deleted","1":"deleted","script_type":"ftplugin","2":"ftplugin","summary":"deleted","3":"deleted","description":"deleted","4":"deleted","install_details":"","5":"","first_name":"Eric","6":"Eric","last_name":"Van Dewoestine","7":"Van Dewoestine","releases":[{"0":"1129","vim_version":"6.0","1":"6.0","script_version":"deleted","2":"deleted","version_comment":"removed","3":"removed","package":"deleted","4":"deleted","src_id":"9527","5":"9527","creation_date":"1227129530","6":"1227129530"}]},"1128":{"script_id":"1128","0":"1128","script_name":"synmark.vim","1":"synmark.vim","script_type":"utility","2":"utility","summary":"Highlight text at a fixed location","3":"Highlight text at a fixed location","description":"This plugin provides commands for highlighting text at a fixed position. This \nworks by dropping \"marks\" for the start and end of a region to be \nhighlighted. It is mainly of use for other plugins, which display some \nexternally provided text, and need to highlight some externally prescribed \nportions of it.\n","4":"This plugin provides commands for highlighting text at a fixed position. This \nworks by dropping \"marks\" for the start and end of a region to be \nhighlighted. It is mainly of use for other plugins, which display some \nexternally provided text, and need to highlight some externally prescribed \nportions of it.\n","install_details":"Standard. The archive includes the plugin, synmark.vim, to be placed in some \n'plugin' directory, and a help file, synmark.txt, which goes into a parallel \n'doc' directory. Then, :helptags should be run for that directory.","5":"Standard. The archive includes the plugin, synmark.vim, to be placed in some \n'plugin' directory, and a help file, synmark.txt, which goes into a parallel \n'doc' directory. Then, :helptags should be run for that directory.","first_name":"moshe","6":"moshe","last_name":"kamensky","7":"kamensky","releases":[{"0":"1128","vim_version":"6.0","1":"6.0","script_version":"0.2","2":"0.2","version_comment":"1. Prevent errors when marking a region end without marking its start\n2. Changed the package directory structure for easier installation","3":"1. Prevent errors when marking a region end without marking its start\n2. Changed the package directory structure for easier installation","package":"synmark-0.2.tar.gz","4":"synmark-0.2.tar.gz","src_id":"3647","5":"3647","creation_date":"1101108519","6":"1101108519"},{"0":"1128","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"synmark-0.1.tar.gz","4":"synmark-0.1.tar.gz","src_id":"3624","5":"3624","creation_date":"1100348218","6":"1100348218"}]},"1127":{"script_id":"1127","0":"1127","script_name":"vim2ansi","1":"vim2ansi","script_type":"utility","2":"utility","summary":"Convert highlighted text into ansi control sequence","3":"Convert highlighted text into ansi control sequence","description":"This is a script to convert current window into ansi color control sequence according to the vim syntax highlighting\r\nUsage of the script is similar to 2html.vim.","4":"This is a script to convert current window into ansi color control sequence according to the vim syntax highlighting\r\nUsage of the script is similar to 2html.vim.","install_details":"1.unzip all files\r\n2.place the file into corresponding directory\r\n3.restart vim and type :TOansi to run","5":"1.unzip all files\r\n2.place the file into corresponding directory\r\n3.restart vim and type :TOansi to run","first_name":"Rogerz","6":"Rogerz","last_name":"Zhang","7":"Zhang","releases":[{"0":"1127","vim_version":"6.0","1":"6.0","script_version":"1.3b","2":"1.3b","version_comment":"Help document added","3":"Help document added","package":"vim2ansi.v1.3b.tgz","4":"vim2ansi.v1.3b.tgz","src_id":"3890","5":"3890","creation_date":"1109013796","6":"1109013796"},{"0":"1127","vim_version":"6.0","1":"6.0","script_version":"1.3a","2":"1.3a","version_comment":"2004\/12\/14 Ver 1.3a\r\n\tFix a bug when source file contains \"<\"\r\n\tEnglish readme added","3":"2004\/12\/14 Ver 1.3a\r\n\tFix a bug when source file contains \"<\"\r\n\tEnglish readme added","package":"vim2ansi.v1.3a.zip","4":"vim2ansi.v1.3a.zip","src_id":"3703","5":"3703","creation_date":"1102963042","6":"1102963042"},{"0":"1127","vim_version":"6.0","1":"6.0","script_version":"1.3","2":"1.3","version_comment":"2004 Nov 15, \tGreatly improved processing speed\r\n","3":"2004 Nov 15, \tGreatly improved processing speed\r\n","package":"vim2ansi.v1.3.zip","4":"vim2ansi.v1.3.zip","src_id":"3635","5":"3635","creation_date":"1100458760","6":"1100458760"},{"0":"1127","vim_version":"6.0","1":"6.0","script_version":"1.2","2":"1.2","version_comment":"2004 Nov 12,\tGuess color from RGB when in gui\r\n","3":"2004 Nov 12,\tGuess color from RGB when in gui\r\n","package":"vim2ansi.v1.2.zip","4":"vim2ansi.v1.2.zip","src_id":"3623","5":"3623","creation_date":"1100318514","6":"1100318514"},{"0":"1127","vim_version":"6.0","1":"6.0","script_version":"1.1","2":"1.1","version_comment":"Initial upload","3":"Initial upload","package":"vim2ansi.v1.1.zip","4":"vim2ansi.v1.1.zip","src_id":"3617","5":"3617","creation_date":"1100118550","6":"1100118550"}]},"1126":{"script_id":"1126","0":"1126","script_name":"lxTrace","1":"lxTrace","script_type":"utility","2":"utility","summary":"lxTrace provides vim-script developers with a simple traceing utility.","3":"lxTrace provides vim-script developers with a simple traceing utility.","description":"  FILE:                      vim_lxtrace.vim\r\n  AUTHOR:               Staale Flock, Staale -- lexholm .. no\r\n  VERSION:               0.1\r\n  LASTMODIFIED:    10 Nov 2004\r\n\r\n  PURPOSE:\r\n\t\tTo provide vim scripts with a simple tracing utility.\r\n\t\t\r\n  WHY:\r\n \t\tI have been working on some vim-scripts and read a lot of them\r\n \t\tthe last two weeks and I thought I needed a Tracing utility to\r\n \t\tease analysis of how some scripts works.\r\n \t\t\r\n  REQUIREMENT:\r\n \t\tNone (tested with vim\/gvim 6.3 on a debian system), this script \r\n \t\tshould work as a standalone plugin.\r\n \t\tBut I'm primarly using it with the winmanager plugin\r\n\t\t(http:\/\/www.vim.org\/scripts\/script.php?script_id=95 ) and as such most\r\n \t\tof my testing is done with this plugin integrated in the winmanager\r\n \t\tworkspace.\r\n \t\t\r\n  INSTALLATION:\r\n  \t\tPlace this file in your plugin directory (~\/.vim\/plugin\/)\r\n\r\n  \t\tWhen you start vim again and open a vim file for editing you should\r\n  \t\tget a message that lxTrace has installed it's documentation.\r\n  \t\tTo get you started you could try :h lxTrace\r\n\r\n  \t\tIf you have installed winmanager you should add LxTrace to the\r\n  \t\tg:winManagerWindowLayout in your vimrc file. My line looks like\r\n  \t\tthis:\r\n\t\t\tlet g:winManagerWindowLayout = 'FileExplorer,TagList|BufExplorer,LxTrace'\r\n  \t\t\r\n  TIPS:\r\n  \t\tDocumentation (when written..:o) is found at the bottom of this file. \r\n  \t\tThanks to code from vimspell.vim it should be self-installing the first\r\n  \t\ttime this module is loaded. When installed you could try \r\n  \t\t\t:help lxTrace\r\n \r\n  NOTE:\r\n\t\t10 Nov 2004 (v 0.1) This is my initial upload. The module probably \r\n\t\tmisses functionality and has undetected bugs. So feel free to\r\n\t\tsuggest improvements.\r\n\t\t\r\n\r\n  Best Regards\r\n  Staale Flock, (staale -- lexholm .. no)\r\n  Norway\r\n","4":"  FILE:                      vim_lxtrace.vim\r\n  AUTHOR:               Staale Flock, Staale -- lexholm .. no\r\n  VERSION:               0.1\r\n  LASTMODIFIED:    10 Nov 2004\r\n\r\n  PURPOSE:\r\n\t\tTo provide vim scripts with a simple tracing utility.\r\n\t\t\r\n  WHY:\r\n \t\tI have been working on some vim-scripts and read a lot of them\r\n \t\tthe last two weeks and I thought I needed a Tracing utility to\r\n \t\tease analysis of how some scripts works.\r\n \t\t\r\n  REQUIREMENT:\r\n \t\tNone (tested with vim\/gvim 6.3 on a debian system), this script \r\n \t\tshould work as a standalone plugin.\r\n \t\tBut I'm primarly using it with the winmanager plugin\r\n\t\t(http:\/\/www.vim.org\/scripts\/script.php?script_id=95 ) and as such most\r\n \t\tof my testing is done with this plugin integrated in the winmanager\r\n \t\tworkspace.\r\n \t\t\r\n  INSTALLATION:\r\n  \t\tPlace this file in your plugin directory (~\/.vim\/plugin\/)\r\n\r\n  \t\tWhen you start vim again and open a vim file for editing you should\r\n  \t\tget a message that lxTrace has installed it's documentation.\r\n  \t\tTo get you started you could try :h lxTrace\r\n\r\n  \t\tIf you have installed winmanager you should add LxTrace to the\r\n  \t\tg:winManagerWindowLayout in your vimrc file. My line looks like\r\n  \t\tthis:\r\n\t\t\tlet g:winManagerWindowLayout = 'FileExplorer,TagList|BufExplorer,LxTrace'\r\n  \t\t\r\n  TIPS:\r\n  \t\tDocumentation (when written..:o) is found at the bottom of this file. \r\n  \t\tThanks to code from vimspell.vim it should be self-installing the first\r\n  \t\ttime this module is loaded. When installed you could try \r\n  \t\t\t:help lxTrace\r\n \r\n  NOTE:\r\n\t\t10 Nov 2004 (v 0.1) This is my initial upload. The module probably \r\n\t\tmisses functionality and has undetected bugs. So feel free to\r\n\t\tsuggest improvements.\r\n\t\t\r\n\r\n  Best Regards\r\n  Staale Flock, (staale -- lexholm .. no)\r\n  Norway\r\n","install_details":"","5":"","first_name":"Staale","6":"Staale","last_name":"Flock","7":"Flock","releases":[{"0":"1126","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"vim_lxtrace.vim","4":"vim_lxtrace.vim","src_id":"3616","5":"3616","creation_date":"1100110746","6":"1100110746"}]},"1125":{"script_id":"1125","0":"1125","script_name":"vimUnit","1":"vimUnit","script_type":"utility","2":"utility","summary":"vimUnit is a unit testing tool inspiered by tools like junit.","3":"vimUnit is a unit testing tool inspiered by tools like junit.","description":" UPDATE:\r\n                Dane Summers has a fork witch probably is more up to date: vimunit fork: https:\/\/github.com\/dsummersl\/vimunit\r\n\r\n  PURPOSE:\r\n\t\tTo provide vim scripts with a simple unit testing framework and tools.\r\n\t\tThe framework and tools should resemble JUnit's interface definitions\r\n\t\tto ease usage of both frameworks (and others based on JUnit). \r\n\t\tObviously vim scripts are not java so I will only try to implement the\r\n\t\tstuff useful to vim scripts. As a first milestone I think the \r\n\t\tjunit.Assert and junit.TestResult classes to get a vim-script\r\n\t\tunit-testing environment going.\r\n\t\t\r\n  WHY:\r\n \t\tWell, I have been working on some vim-scripts and read a lot of them\r\n \t\tthe last two weeks and I really, really miss my unit-test (and\r\n \t\tmock-object, but that is fare fetched I think..:O) tools to get my own\r\n \t\tstuff of the ground (and making modifications to your's).\r\n \t\t\r\n  THOUGHTS:\r\n\t\tWriting unit-test code against a UI environment is often very difficult \r\n\t\tor demanding to creative solutions to be productive. We would like to \r\n\t\thave a mock-object framework to go with the unit-testing framework.\r\n\t\t\r\n  INSTALLATION:\r\n  \t\tPlace this file in your plugin directory (~\/.vim\/ftplugin\/)\r\n  \t\tWhen you start vim again and open a vim file for editing you should\r\n  \t\tget a message that vimUnit has installed its documentation.\r\n  \t\tTo get you started you could try :h vimUnit or :h VUAutoRun\r\n  \t\t\r\n  TIPS:\r\n  \t\tDocumentation (when written..:o) is found at the bottom of this file. \r\n  \t\tThanks to code from vimspell.vim it should be self-installing the first\r\n  \t\ttime this module is loaded\r\n\r\n  \t\tIf your new to test-first principles and thinking you should start\r\n  \t\twith the article: \r\n  \t\t\thttp:\/\/junit.sourceforge.net\/doc\/testinfected\/testing.htm\r\n  \t\tAnd then surf the web on these locations:\r\n  \t\t\thttp:\/\/www.junit.org\/\r\n  \t\t\thttp:\/\/xprogramming.com\/\r\n  \t\t\thttp:\/\/www.extremeprogramming.org\/\r\n \r\n  NOTE:\r\n\t\t8 Nov 2004 (v 0.1) This is my initial upload. The module is fare \r\n\t\tfrom finished. But as I could do with some input from other vim users\r\n\t\tSo I have chosen to let people know I'm working on it. \r\n\r\n\t\tTo be conform with vim-script naming conventions functions are\r\n\t\tprepended with VU (VimUnit). So stuff you would normaly would call \r\n\t\tVUAssert are called VUAssert, TestRunner* are called VURunner and so on.\r\n\t\tGlobal variables starts with vimUnit*\r\n\t\t\r\n\r\n  Best Regards\r\n  Staale Flock,  (staale -- lexholm .. no)","4":" UPDATE:\r\n                Dane Summers has a fork witch probably is more up to date: vimunit fork: https:\/\/github.com\/dsummersl\/vimunit\r\n\r\n  PURPOSE:\r\n\t\tTo provide vim scripts with a simple unit testing framework and tools.\r\n\t\tThe framework and tools should resemble JUnit's interface definitions\r\n\t\tto ease usage of both frameworks (and others based on JUnit). \r\n\t\tObviously vim scripts are not java so I will only try to implement the\r\n\t\tstuff useful to vim scripts. As a first milestone I think the \r\n\t\tjunit.Assert and junit.TestResult classes to get a vim-script\r\n\t\tunit-testing environment going.\r\n\t\t\r\n  WHY:\r\n \t\tWell, I have been working on some vim-scripts and read a lot of them\r\n \t\tthe last two weeks and I really, really miss my unit-test (and\r\n \t\tmock-object, but that is fare fetched I think..:O) tools to get my own\r\n \t\tstuff of the ground (and making modifications to your's).\r\n \t\t\r\n  THOUGHTS:\r\n\t\tWriting unit-test code against a UI environment is often very difficult \r\n\t\tor demanding to creative solutions to be productive. We would like to \r\n\t\thave a mock-object framework to go with the unit-testing framework.\r\n\t\t\r\n  INSTALLATION:\r\n  \t\tPlace this file in your plugin directory (~\/.vim\/ftplugin\/)\r\n  \t\tWhen you start vim again and open a vim file for editing you should\r\n  \t\tget a message that vimUnit has installed its documentation.\r\n  \t\tTo get you started you could try :h vimUnit or :h VUAutoRun\r\n  \t\t\r\n  TIPS:\r\n  \t\tDocumentation (when written..:o) is found at the bottom of this file. \r\n  \t\tThanks to code from vimspell.vim it should be self-installing the first\r\n  \t\ttime this module is loaded\r\n\r\n  \t\tIf your new to test-first principles and thinking you should start\r\n  \t\twith the article: \r\n  \t\t\thttp:\/\/junit.sourceforge.net\/doc\/testinfected\/testing.htm\r\n  \t\tAnd then surf the web on these locations:\r\n  \t\t\thttp:\/\/www.junit.org\/\r\n  \t\t\thttp:\/\/xprogramming.com\/\r\n  \t\t\thttp:\/\/www.extremeprogramming.org\/\r\n \r\n  NOTE:\r\n\t\t8 Nov 2004 (v 0.1) This is my initial upload. The module is fare \r\n\t\tfrom finished. But as I could do with some input from other vim users\r\n\t\tSo I have chosen to let people know I'm working on it. \r\n\r\n\t\tTo be conform with vim-script naming conventions functions are\r\n\t\tprepended with VU (VimUnit). So stuff you would normaly would call \r\n\t\tVUAssert are called VUAssert, TestRunner* are called VURunner and so on.\r\n\t\tGlobal variables starts with vimUnit*\r\n\t\t\r\n\r\n  Best Regards\r\n  Staale Flock,  (staale -- lexholm .. no)","install_details":"  Place this file in your plugin directory (~\/.vim\/ftplugin\/). \tWhen you start vim again and open a vim file for editing you should get a message that vimUnit has installed its documentation. \r\n\r\nTo get you started you could try :h vimUnit or :h VUAutoRun","5":"  Place this file in your plugin directory (~\/.vim\/ftplugin\/). \tWhen you start vim again and open a vim file for editing you should get a message that vimUnit has installed its documentation. \r\n\r\nTo get you started you could try :h vimUnit or :h VUAutoRun","first_name":"Staale","6":"Staale","last_name":"Flock","7":"Flock","releases":[{"0":"1125","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"vim_unit.vim","4":"vim_unit.vim","src_id":"3614","5":"3614","creation_date":"1099979863","6":"1099979863"}]},"1124":{"script_id":"1124","0":"1124","script_name":"UpdateModDate.vim","1":"UpdateModDate.vim","script_type":"utility","2":"utility","summary":"Updates a date stamp within a file whenever it is saved.","3":"Updates a date stamp within a file whenever it is saved.","description":"This script uses an autocmd hook to run a function whenever a file is saved.\r\nThe function then looks if it finds a special token (by default %DATE_TAG%) within the file, and if it's found, a datestamp on the same line is updated to the current date.\r\n\r\nThis script will run on all systems that provide date(1), so it should work on unix systems, as well as on cygwin.\r\n\r\nIf no special token is found, nothing is done at all.\r\nIf there are multiple tokens within the file, only the first one from the beginning of the buffer will be updated.\r\n\r\nThe date format and the special token are fully configureable.","4":"This script uses an autocmd hook to run a function whenever a file is saved.\r\nThe function then looks if it finds a special token (by default %DATE_TAG%) within the file, and if it's found, a datestamp on the same line is updated to the current date.\r\n\r\nThis script will run on all systems that provide date(1), so it should work on unix systems, as well as on cygwin.\r\n\r\nIf no special token is found, nothing is done at all.\r\nIf there are multiple tokens within the file, only the first one from the beginning of the buffer will be updated.\r\n\r\nThe date format and the special token are fully configureable.","install_details":"Put the file into your plugin directory (~\/.vim\/plugin). It will then automatically be loaded.\r\n\r\nTo see an example of the script doing it's work, just put the following line in a file and save it, the date should then be updated automatically:\r\n%DATE_TAG% Last Modified: Sun Nov  7 21:54:49 UTC 2004.\r\nIf it works once, but not thereafter, it is because your date -u uses a different output format then that on my machine. See below on how to set the DatePattern to match your date output.\r\n\r\nYou can add whitespace, comments, whatever to that line, just do not change %DATE_TAG% or anything within the date part, and pay attention that the special date token (%DATE_TAG%) and the date are on the same line.\r\n\r\nThere are 3 variables you can set from your vimrc file:\r\n*** UMD_DateToken: This is the string the script uses to find the correct line. It defaults to '%DATE_TAG%'\r\n*** UMD_DateCommand: This is the command that will be executed to get the current date. It defaults to  'date -u | tr -d \"\\n\"' (this gets the date with UTC time and removes the trailing newline.\r\n*** UMD_DatePattern: This is a regexp that defines which part of the line with the special token should be substituted with the new date. Make sure it matches if you change the DateCommand. It defaults to '\\w\\+\\s\\+\\w\\+\\s\\+\\d\\+\\s\\+\\d\\{2\\}:\\d\\{2\\}:\\d\\{2\\}\\s\\+UTC\\s\\+\\d\\+', which matches the date -u output.\r\n\r\nThe easy way to get a working UMD_DatePattern:\r\nIn vim use \r\n:r!date <options-you-want> \r\nto read the output of date with the options you want into the current buffer.\r\nNow start a vim search and construct a pattern that matches your date string within the search (hlmatch\/incsearch should be on, so you see what is currently matched). Once the pattern matches the whole date string, enclose it in '' and set UMD_DatePattern to that string in your vimrc.","5":"Put the file into your plugin directory (~\/.vim\/plugin). It will then automatically be loaded.\r\n\r\nTo see an example of the script doing it's work, just put the following line in a file and save it, the date should then be updated automatically:\r\n%DATE_TAG% Last Modified: Sun Nov  7 21:54:49 UTC 2004.\r\nIf it works once, but not thereafter, it is because your date -u uses a different output format then that on my machine. See below on how to set the DatePattern to match your date output.\r\n\r\nYou can add whitespace, comments, whatever to that line, just do not change %DATE_TAG% or anything within the date part, and pay attention that the special date token (%DATE_TAG%) and the date are on the same line.\r\n\r\nThere are 3 variables you can set from your vimrc file:\r\n*** UMD_DateToken: This is the string the script uses to find the correct line. It defaults to '%DATE_TAG%'\r\n*** UMD_DateCommand: This is the command that will be executed to get the current date. It defaults to  'date -u | tr -d \"\\n\"' (this gets the date with UTC time and removes the trailing newline.\r\n*** UMD_DatePattern: This is a regexp that defines which part of the line with the special token should be substituted with the new date. Make sure it matches if you change the DateCommand. It defaults to '\\w\\+\\s\\+\\w\\+\\s\\+\\d\\+\\s\\+\\d\\{2\\}:\\d\\{2\\}:\\d\\{2\\}\\s\\+UTC\\s\\+\\d\\+', which matches the date -u output.\r\n\r\nThe easy way to get a working UMD_DatePattern:\r\nIn vim use \r\n:r!date <options-you-want> \r\nto read the output of date with the options you want into the current buffer.\r\nNow start a vim search and construct a pattern that matches your date string within the search (hlmatch\/incsearch should be on, so you see what is currently matched). Once the pattern matches the whole date string, enclose it in '' and set UMD_DatePattern to that string in your vimrc.","first_name":"Christian","6":"Christian","last_name":"Aichinger","7":"Aichinger","releases":[{"0":"1124","vim_version":"6.0","1":"6.0","script_version":"1.2","2":"1.2","version_comment":"I've changed the default UDM_DatePattern a bit, to better match different date -u outputs. \r\nIt does now match the date part less strictly, but the time part more exactly. I hope this solves the \"it works once but not thereafter\" problem for most people.","3":"I've changed the default UDM_DatePattern a bit, to better match different date -u outputs. \r\nIt does now match the date part less strictly, but the time part more exactly. I hope this solves the \"it works once but not thereafter\" problem for most people.","package":"UpdateModDate.vim","4":"UpdateModDate.vim","src_id":"3613","5":"3613","creation_date":"1099916277","6":"1099916277"},{"0":"1124","vim_version":"6.0","1":"6.0","script_version":"1.1","2":"1.1","version_comment":"The script now starts to search for the DateToken from the very top of the file, and it will only update the first occurance.\r\n\r\nI changed the script so that the values for DateToken, DatePattern, DateCommand aren't hardcoded any more.\r\nYou can now define UMD_DateToken, UMD_DatePattern and UMD_DateCommand in your vimrc.\r\n\r\nThe default values are:\r\nlet s:UMD_DateToken = '%DATE_TAG%'\r\nlet s:UMD_DatePattern = '\\w\\{3\\}\\s\\w\\{3\\}\\s\\+\\d\\+\\s\\+\\d\\+:\\d\\+:\\d\\+\\s\\+UTC\\s\\+\\d\\+'\r\nlet UMD_DateCommand = 'date -u | tr -d \"\\n\"'\r\n","3":"The script now starts to search for the DateToken from the very top of the file, and it will only update the first occurance.\r\n\r\nI changed the script so that the values for DateToken, DatePattern, DateCommand aren't hardcoded any more.\r\nYou can now define UMD_DateToken, UMD_DatePattern and UMD_DateCommand in your vimrc.\r\n\r\nThe default values are:\r\nlet s:UMD_DateToken = '%DATE_TAG%'\r\nlet s:UMD_DatePattern = '\\w\\{3\\}\\s\\w\\{3\\}\\s\\+\\d\\+\\s\\+\\d\\+:\\d\\+:\\d\\+\\s\\+UTC\\s\\+\\d\\+'\r\nlet UMD_DateCommand = 'date -u | tr -d \"\\n\"'\r\n","package":"UpdateModDate.vim","4":"UpdateModDate.vim","src_id":"3612","5":"3612","creation_date":"1099835496","6":"1099835496"}]},"1123":{"script_id":"1123","0":"1123","script_name":"lpl.vim","1":"lpl.vim","script_type":"syntax","2":"syntax","summary":"Syntax file for LPL (Linear\/Logical Programming Language)","3":"Syntax file for LPL (Linear\/Logical Programming Language)","description":"A syntax highlighting file for LPL (Linear\/Logical Programming Language)\r\n\r\n\"LPL contains a powerful modelling language and a complete modelling environment and it is possible to specify complex mathematical models in a concise way.\" \r\nhttp:\/\/www.virtual-optima.com\/en\/products.html","4":"A syntax highlighting file for LPL (Linear\/Logical Programming Language)\r\n\r\n\"LPL contains a powerful modelling language and a complete modelling environment and it is possible to specify complex mathematical models in a concise way.\" \r\nhttp:\/\/www.virtual-optima.com\/en\/products.html","install_details":"Copy lpl.vim to your $VIMRUNTIME\/syntax\/ directory.\r\nAdd the following to $VIMRUNTIME\/filetype.vim:\r\n\r\n\" LPL\r\nau BufNewFile,BufRead *.lpl     setf lpl\r\n\r\nThis file has DOS line endings. If you want to use the script on a Unix machine, open the file with vim, :set ff=unix and save.","5":"Copy lpl.vim to your $VIMRUNTIME\/syntax\/ directory.\r\nAdd the following to $VIMRUNTIME\/filetype.vim:\r\n\r\n\" LPL\r\nau BufNewFile,BufRead *.lpl     setf lpl\r\n\r\nThis file has DOS line endings. If you want to use the script on a Unix machine, open the file with vim, :set ff=unix and save.","first_name":"Roberto","6":"Roberto","last_name":"Bonvallet","7":"Bonvallet","releases":[{"0":"1123","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"lpl.vim","4":"lpl.vim","src_id":"3610","5":"3610","creation_date":"1099825293","6":"1099825293"}]},"1122":{"script_id":"1122","0":"1122","script_name":"lingo.vim","1":"lingo.vim","script_type":"syntax","2":"syntax","summary":"Syntax highlighting for LINGO (Linear, INteractive and General Optimizer)","3":"Syntax highlighting for LINGO (Linear, INteractive and General Optimizer)","description":"A syntax highlighting file for LINGO (Linear, INteractive and General Optimizer).\r\n\r\nLINGO is a language and tool for modelling and solving optimization problems (http:\/\/www.lindo.com\/cgi\/frameset.cgi?leftlingo.html;lingof.html). \r\n\r\nThis syntax is NOT related to Macromedia Director Lingo scripting language. If you came here by mistake, please browse vimscript #503, vimscript #1010 or vimscript #1012.\r\n\r\nPlease e-mail comments and suggestions with subject \"vim\".","4":"A syntax highlighting file for LINGO (Linear, INteractive and General Optimizer).\r\n\r\nLINGO is a language and tool for modelling and solving optimization problems (http:\/\/www.lindo.com\/cgi\/frameset.cgi?leftlingo.html;lingof.html). \r\n\r\nThis syntax is NOT related to Macromedia Director Lingo scripting language. If you came here by mistake, please browse vimscript #503, vimscript #1010 or vimscript #1012.\r\n\r\nPlease e-mail comments and suggestions with subject \"vim\".","install_details":"Copy lingo.vim to your syntax\/ directory.\r\n\r\nAdd the following to filetype.vim:\r\n\r\n- - - - - - - - -\r\n\" LINGO\r\nau BufNewFile,BufRead *.lingo     setf lingo \r\n- - - - - - - - -","5":"Copy lingo.vim to your syntax\/ directory.\r\n\r\nAdd the following to filetype.vim:\r\n\r\n- - - - - - - - -\r\n\" LINGO\r\nau BufNewFile,BufRead *.lingo     setf lingo \r\n- - - - - - - - -","first_name":"Juan","6":"Juan","last_name":"Cataldo","7":"Cataldo","releases":[{"0":"1122","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"lingo.vim","4":"lingo.vim","src_id":"3607","5":"3607","creation_date":"1099608382","6":"1099608382"}]},"1121":{"script_id":"1121","0":"1121","script_name":"anttestreport","1":"anttestreport","script_type":"syntax","2":"syntax","summary":"coloring plain text reports created by ant for JUnit tests.","3":"coloring plain text reports created by ant for JUnit tests.","description":"My plugin tries to color  Test reports created by ant  the following way :\r\nIt colors all good things in green and bad things in red or some kind of. Also It shadows meaningless things. \r\nAnd yet I tried to fold long stack traces. So take a look. Comments are welcome.","4":"My plugin tries to color  Test reports created by ant  the following way :\r\nIt colors all good things in green and bad things in red or some kind of. Also It shadows meaningless things. \r\nAnd yet I tried to fold long stack traces. So take a look. Comments are welcome.","install_details":" To install add anttestreport.vim to any syntax directory and add the following lines to the filetype.vim :\r\n\\\" Ant Test Report\r\nau BufNewFile,BufRead TEST-*.txt\t\t\tsetf anttestreport\r\n","5":" To install add anttestreport.vim to any syntax directory and add the following lines to the filetype.vim :\r\n\\\" Ant Test Report\r\nau BufNewFile,BufRead TEST-*.txt\t\t\tsetf anttestreport\r\n","first_name":"Yury","6":"Yury","last_name":"Altukhou","7":"Altukhou","releases":[{"0":"1121","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"anttestreport.vim","4":"anttestreport.vim","src_id":"3598","5":"3598","creation_date":"1099462498","6":"1099462498"}]},"1120":{"script_id":"1120","0":"1120","script_name":"PHP-correct-Indenting","1":"PHP-correct-Indenting","script_type":"indent","2":"indent","summary":"The official VIm indent script for PHP","3":"The official VIm indent script for PHP","description":"GitHub: https:\/\/github.com\/2072\/PHP-Indenting-for-VIm\r\n\r\n(The version 1.39 of this script is included in VIM 7.4)\r\n\r\nFeatures:\r\n- Indents PHP code as \"perfectly\" as possible.\r\n- Comments' content or non-PHP code are ignored and don't break the algorithm.\r\n- Non-PHP code, multi-line \/**\/ comments and \"Here Document\" content remain unchanged.\r\n- HTML <Script.*> tags' content is indented as PHP and like if it was part of the surrounding PHP code.\r\n- Fast optimized indenting, the script knows when it's indenting large blocks and skips some unnecessary tests.\r\n- Support folding (fold markers don't break the indenting)\r\n- Auto-formatting for comments (using the Vim option formatoptions=qroc).\r\n- Indent correctly complex \"non bracketed blocks\":\r\n\r\n    Example: (start of line spaces are replaced by ____)\r\n<?php\r\nif (!isset($History_lst_sel)) \r\n____if (!isset($History_lst_sel)) \r\n________if (!isset($History_lst_sel)) {\r\n____________$History_lst_sel=0;\r\n________} else\r\n____________$foo=\"truc\";\r\n____else\r\n_______$bla= \"foo\";\r\n$command_hist = TRUE;\r\n?>\r\n\r\n- Direct indenting, the text is indented as you type it.\r\n- switch\/case are indented correctly.\r\n- Well commented source code.\r\n- Bug free as far as I know.\r\n\r\nA more complete example of its capabilities:\r\n\r\n<?php\r\nif ($foo=\"thing\") \/\/ as you see an opened bracket isn't needed to indent correctly :)\r\n____if (foo(\"something\"))\r\n____{\r\n________somethingelse(\"blabla\");\r\n?>\r\n\r\n\r\n<html>\r\n<head>\r\n<title>SOME HTML CODE<\/title>\r\n<?\r\n________echo \"Something here\";\r\n?>\r\n________<script type=\"text\/javascript\">\r\n________\/\/ Note the indentation of the script as if part of PHP\r\n\r\n________var truc=0;\r\n________if (truc) {\r\n____________nothing();\r\n________}\r\n\r\n________<\/script>\r\n\r\n<\/head>\r\n<body>\r\n\r\n<b>some closing and oppening bracket here } } {\r\nnothing to indent here\r\n<\/b>\r\n\r\n<\/body>\r\n<\/html>\r\n\r\n\r\n<?\r\n________Somethingelse(true);\r\n____}\r\n\r\nif (foo)\r\n____\/* a useless comment here\r\n____with useless code:\r\n____if (broken code) {\r\n___________________blabla();\r\n____*\/\r\n____if (testHereDocument()) {\r\n\r\n\r\n________echo <<<HEREDOC\r\nHere is an Here Document style\r\necho, very useful.\r\nThe following code isn't indented\r\nif (test)\r\nwhile (foo) {\r\nnothing();\r\n}\r\nHEREDOC;\r\n\r\n____}\r\n\r\nbye();\r\n?>\r\n\r\nThat's all folks!\r\n\r\nThis script can also be found there: (with a colorful example)\r\nhttp:\/\/www.2072productions.com\/to\/phpindent.txt\r\n\r\n\r\nEnjoy :)","4":"GitHub: https:\/\/github.com\/2072\/PHP-Indenting-for-VIm\r\n\r\n(The version 1.39 of this script is included in VIM 7.4)\r\n\r\nFeatures:\r\n- Indents PHP code as \"perfectly\" as possible.\r\n- Comments' content or non-PHP code are ignored and don't break the algorithm.\r\n- Non-PHP code, multi-line \/**\/ comments and \"Here Document\" content remain unchanged.\r\n- HTML <Script.*> tags' content is indented as PHP and like if it was part of the surrounding PHP code.\r\n- Fast optimized indenting, the script knows when it's indenting large blocks and skips some unnecessary tests.\r\n- Support folding (fold markers don't break the indenting)\r\n- Auto-formatting for comments (using the Vim option formatoptions=qroc).\r\n- Indent correctly complex \"non bracketed blocks\":\r\n\r\n    Example: (start of line spaces are replaced by ____)\r\n<?php\r\nif (!isset($History_lst_sel)) \r\n____if (!isset($History_lst_sel)) \r\n________if (!isset($History_lst_sel)) {\r\n____________$History_lst_sel=0;\r\n________} else\r\n____________$foo=\"truc\";\r\n____else\r\n_______$bla= \"foo\";\r\n$command_hist = TRUE;\r\n?>\r\n\r\n- Direct indenting, the text is indented as you type it.\r\n- switch\/case are indented correctly.\r\n- Well commented source code.\r\n- Bug free as far as I know.\r\n\r\nA more complete example of its capabilities:\r\n\r\n<?php\r\nif ($foo=\"thing\") \/\/ as you see an opened bracket isn't needed to indent correctly :)\r\n____if (foo(\"something\"))\r\n____{\r\n________somethingelse(\"blabla\");\r\n?>\r\n\r\n\r\n<html>\r\n<head>\r\n<title>SOME HTML CODE<\/title>\r\n<?\r\n________echo \"Something here\";\r\n?>\r\n________<script type=\"text\/javascript\">\r\n________\/\/ Note the indentation of the script as if part of PHP\r\n\r\n________var truc=0;\r\n________if (truc) {\r\n____________nothing();\r\n________}\r\n\r\n________<\/script>\r\n\r\n<\/head>\r\n<body>\r\n\r\n<b>some closing and oppening bracket here } } {\r\nnothing to indent here\r\n<\/b>\r\n\r\n<\/body>\r\n<\/html>\r\n\r\n\r\n<?\r\n________Somethingelse(true);\r\n____}\r\n\r\nif (foo)\r\n____\/* a useless comment here\r\n____with useless code:\r\n____if (broken code) {\r\n___________________blabla();\r\n____*\/\r\n____if (testHereDocument()) {\r\n\r\n\r\n________echo <<<HEREDOC\r\nHere is an Here Document style\r\necho, very useful.\r\nThe following code isn't indented\r\nif (test)\r\nwhile (foo) {\r\nnothing();\r\n}\r\nHEREDOC;\r\n\r\n____}\r\n\r\nbye();\r\n?>\r\n\r\nThat's all folks!\r\n\r\nThis script can also be found there: (with a colorful example)\r\nhttp:\/\/www.2072productions.com\/to\/phpindent.txt\r\n\r\n\r\nEnjoy :)","install_details":"Just make sure the name of the file is php.vim and copy it under your vimfiles\/indent folder.\r\nPHP syntax coloring must be turned on.\r\n\r\nFor alternative install solutions (Pathogen and Vundle) please read https:\/\/github.com\/2072\/PHP-Indenting-for-VIm\/blob\/master\/README.md\r\n\r\nAvailable options:\r\n\r\nJust type :help php-indent","5":"Just make sure the name of the file is php.vim and copy it under your vimfiles\/indent folder.\r\nPHP syntax coloring must be turned on.\r\n\r\nFor alternative install solutions (Pathogen and Vundle) please read https:\/\/github.com\/2072\/PHP-Indenting-for-VIm\/blob\/master\/README.md\r\n\r\nAvailable options:\r\n\r\nJust type :help php-indent","first_name":"John","6":"John","last_name":"Wellesz","7":"Wellesz","releases":[{"0":"1120","vim_version":"8.0","1":"8.0","script_version":"1.70","2":"1.70","version_comment":"This page is no longer updated, see the Github page of this project for future releases:\r\n\r\nhttps:\/\/github.com\/2072\/PHP-Indenting-for-VIm","3":"This page is no longer updated, see the Github page of this project for future releases:\r\n\r\nhttps:\/\/github.com\/2072\/PHP-Indenting-for-VIm","package":"php.vim","4":"php.vim","src_id":"26644","5":"26644","creation_date":"1563779455","6":"1563779455"},{"0":"1120","vim_version":"7.4","1":"7.4","script_version":"1.52","2":"1.52","version_comment":"- Fix issue #34 where indentation could get wrong with arrays defined using the short [] declaration.\r\n\r\n- Fix an edge case in conditional block declarations when the ')' of the condition is put on the same line as the following '{' (complement to issue #4)\r\n\r\n","3":"- Fix issue #34 where indentation could get wrong with arrays defined using the short [] declaration.\r\n\r\n- Fix an edge case in conditional block declarations when the ')' of the condition is put on the same line as the following '{' (complement to issue #4)\r\n\r\n","package":"php.vim","4":"php.vim","src_id":"22030","5":"22030","creation_date":"1402925548","6":"1402925548"},{"0":"1120","vim_version":"7.4","1":"7.4","script_version":"1.49","2":"1.49","version_comment":"- Added support for 'finally', 'use', 'trait' and 'final' keywords\r\n\r\n- Implemented support for multi-line block declarations (issue #4).\r\n\r\n- Added support (with some restrictions) for multi-line string declarations (issue #22).\r\n\r\n- Fix issue with lines following a {} block defined on a single line if this {} block was just beneath a '{'\r\n\r\n- Fix issue #32 ('case:\/default:' indentation issues in complex 'switch' blocks)\r\n\r\n- Fix issue #17 where closures' content would get extra indenting.\r\n\r\n- Fix handing of ^}\\s*else\\n{ blocks which were not detected as new blocks and resulted in wrong indentation.\r\n\r\n- Fix issue #23 where the script could hang in some specific cases involving closing braces at column 0;\r\n\r\n- Fix issue #6 where nested switches would not indent correctly.\r\n\r\n- No longer add 'w' to formatoptions VIm' setting as no other file-type plug-in uses it by default. This prevents leaving trailing white spaces when text wrapping.\r\n","3":"- Added support for 'finally', 'use', 'trait' and 'final' keywords\r\n\r\n- Implemented support for multi-line block declarations (issue #4).\r\n\r\n- Added support (with some restrictions) for multi-line string declarations (issue #22).\r\n\r\n- Fix issue with lines following a {} block defined on a single line if this {} block was just beneath a '{'\r\n\r\n- Fix issue #32 ('case:\/default:' indentation issues in complex 'switch' blocks)\r\n\r\n- Fix issue #17 where closures' content would get extra indenting.\r\n\r\n- Fix handing of ^}\\s*else\\n{ blocks which were not detected as new blocks and resulted in wrong indentation.\r\n\r\n- Fix issue #23 where the script could hang in some specific cases involving closing braces at column 0;\r\n\r\n- Fix issue #6 where nested switches would not indent correctly.\r\n\r\n- No longer add 'w' to formatoptions VIm' setting as no other file-type plug-in uses it by default. This prevents leaving trailing white spaces when text wrapping.\r\n","package":"php.vim","4":"php.vim","src_id":"21779","5":"21779","creation_date":"1397602535","6":"1397602535"},{"0":"1120","vim_version":"7.3","1":"7.3","script_version":"1.39","2":"1.39","version_comment":"- Also add 'StorageClass' syntax identifier (with an upper-case 'C') as it also exists in the syntax file.","3":"- Also add 'StorageClass' syntax identifier (with an upper-case 'C') as it also exists in the syntax file.","package":"php-indent_1-39.zip","4":"php-indent_1-39.zip","src_id":"20615","5":"20615","creation_date":"1375997121","6":"1375997121"},{"0":"1120","vim_version":"7.3","1":"7.3","script_version":"1.38","2":"1.38","version_comment":"Changes: 1.38\r\n- Fix an incredibly old bug that managed to survive unnoticed until today: the\r\n  PHP code identifier routine was missing a few syntax names (Define,\r\n  Structure, Storageclass and Exception). If you started indenting on such a\r\n  line, nothing would happen as the script thought it wasn't actual PHP code...\r\n\r\nChanges: 1.37\r\n- Fix a bug for inline script element [imicky]\r\n- Fix issue #11: https:\/\/github.com\/2072\/PHP-Indenting-for-VIm\/issues\/11\r\n\r\nChanges: 1.36\r\n- Added support for short array declaration (Thanks to Warren Seymour)\r\n\r\nChanges: 1.35\r\n- New option: PHP_outdentSLComments to add extra indentation to single-line\r\n  comments.\r\n","3":"Changes: 1.38\r\n- Fix an incredibly old bug that managed to survive unnoticed until today: the\r\n  PHP code identifier routine was missing a few syntax names (Define,\r\n  Structure, Storageclass and Exception). If you started indenting on such a\r\n  line, nothing would happen as the script thought it wasn't actual PHP code...\r\n\r\nChanges: 1.37\r\n- Fix a bug for inline script element [imicky]\r\n- Fix issue #11: https:\/\/github.com\/2072\/PHP-Indenting-for-VIm\/issues\/11\r\n\r\nChanges: 1.36\r\n- Added support for short array declaration (Thanks to Warren Seymour)\r\n\r\nChanges: 1.35\r\n- New option: PHP_outdentSLComments to add extra indentation to single-line\r\n  comments.\r\n","package":"php-indent_1-38.zip","4":"php-indent_1-38.zip","src_id":"20592","5":"20592","creation_date":"1375435575","6":"1375435575"},{"0":"1120","vim_version":"7.0","1":"7.0","script_version":"1.34","2":"1.34","version_comment":"- Fix: string with \/* would be treated as comment start when using single quote. (Thanks to Manic Chuang for the fix)","3":"- Fix: string with \/* would be treated as comment start when using single quote. (Thanks to Manic Chuang for the fix)","package":"php.vim","4":"php.vim","src_id":"15001","5":"15001","creation_date":"1297701327","6":"1297701327"},{"0":"1120","vim_version":"7.3","1":"7.3","script_version":"1.33_fixed","2":"1.33_fixed","version_comment":"Fixes a formatting issue concerning php.vim itself, (CRLF back to LF)","3":"Fixes a formatting issue concerning php.vim itself, (CRLF back to LF)","package":"php.vim","4":"php.vim","src_id":"13998","5":"13998","creation_date":"1286316418","6":"1286316418"},{"0":"1120","vim_version":"7.0","1":"7.0","script_version":"1.33","2":"1.33","version_comment":"- Rewrote Switch(){case:default:} handling from scratch in a simpler more logical and infallible way.\r\n- Added a new option: PHP_outdentphpescape to indent PHP tags as the surrounding code.","3":"- Rewrote Switch(){case:default:} handling from scratch in a simpler more logical and infallible way.\r\n- Added a new option: PHP_outdentphpescape to indent PHP tags as the surrounding code.","package":"php.vim","4":"php.vim","src_id":"13433","5":"13433","creation_date":"1280448244","6":"1280448244"},{"0":"1120","vim_version":"7.0","1":"7.0","script_version":"1.30","2":"1.30","version_comment":"- Fixed empty case\/default identation again :\/\r\n- The ResetOptions() function will be called each time the ftplugin calls this script, previously it was executed on BufWinEnter and Syntax events.","3":"- Fixed empty case\/default identation again :\/\r\n- The ResetOptions() function will be called each time the ftplugin calls this script, previously it was executed on BufWinEnter and Syntax events.","package":"php.vim","4":"php.vim","src_id":"9543","5":"9543","creation_date":"1227344227","6":"1227344227"},{"0":"1120","vim_version":"7.0","1":"7.0","script_version":"1.29","2":"1.29","version_comment":"Fixed php file detection for ResetOptions() used for comments formatting. It now uses the same tests as filetype.vim. ResetOptions() will be correctly called for *.phtml, *.ctp and *.inc files.","3":"Fixed php file detection for ResetOptions() used for comments formatting. It now uses the same tests as filetype.vim. ResetOptions() will be correctly called for *.phtml, *.ctp and *.inc files.","package":"php.vim","4":"php.vim","src_id":"9400","5":"9400","creation_date":"1225028163","6":"1225028163"},{"0":"1120","vim_version":"7.0","1":"7.0","script_version":"1.28","2":"1.28","version_comment":"- Added support for NOWDOC tags ($foo = <<<'bar')\r\n- New option: PHP_vintage_case_default_indent (default off)\r\n- End HEREDOC delimiters were not considered as such if they were not followed by a ';'.\r\n- if a \"case\" was preceded by another \"case\" on the previous line, the second \"case\" was indented incorrectly.\r\n- '\/*' character sequences found on a line starting by a '#' were not dismissed by the indenting algorithm and could cause indentation problem in some cases.\r\n- Fix some indentation errors on multi line conditions and multi line statements.\r\n- Fix when array indenting is broken and a closing ');' is placed at the start of the line, following lines will be indented correctly.\r\n- Minor fixes and optimizations.","3":"- Added support for NOWDOC tags ($foo = <<<'bar')\r\n- New option: PHP_vintage_case_default_indent (default off)\r\n- End HEREDOC delimiters were not considered as such if they were not followed by a ';'.\r\n- if a \"case\" was preceded by another \"case\" on the previous line, the second \"case\" was indented incorrectly.\r\n- '\/*' character sequences found on a line starting by a '#' were not dismissed by the indenting algorithm and could cause indentation problem in some cases.\r\n- Fix some indentation errors on multi line conditions and multi line statements.\r\n- Fix when array indenting is broken and a closing ');' is placed at the start of the line, following lines will be indented correctly.\r\n- Minor fixes and optimizations.","package":"php.vim","4":"php.vim","src_id":"8779","5":"8779","creation_date":"1213063206","6":"1213063206"},{"0":"1120","vim_version":"7.0","1":"7.0","script_version":"1.24","2":"1.24","version_comment":"- Added compatibility with the latest version of php.vim syntax file by Peter Hodge (http:\/\/www.vim.org\/scripts\/script.php?script_id=1571)\r\nThis fixes wrong indentation and ultra-slow indenting on large php files...\r\n- fixed spelling in comments\r\n","3":"- Added compatibility with the latest version of php.vim syntax file by Peter Hodge (http:\/\/www.vim.org\/scripts\/script.php?script_id=1571)\r\nThis fixes wrong indentation and ultra-slow indenting on large php files...\r\n- fixed spelling in comments\r\n","package":"php.vim","4":"php.vim","src_id":"6783","5":"6783","creation_date":"1172335770","6":"1172335770"},{"0":"1120","vim_version":"6.0","1":"6.0","script_version":"1.23","2":"1.23","version_comment":"- <script> html tags are now correctly indented the same way their content is.\r\n- <?.*?> (on a single line) php declarations are now always considered as non-php code and let untouched.","3":"- <script> html tags are now correctly indented the same way their content is.\r\n- <?.*?> (on a single line) php declarations are now always considered as non-php code and let untouched.","package":"php.vim","4":"php.vim","src_id":"4975","5":"4975","creation_date":"1137276650","6":"1137276650"},{"0":"1120","vim_version":"6.0","1":"6.0","script_version":"1.22","2":"1.22","version_comment":"- PHPDoc comments are now indented according to the surrounding code.\r\n- This is also true for '\/* *\/' multi-line comments when the second line begins by a '*'.\r\n- Single line '\/* *\/' comments are also indented.","3":"- PHPDoc comments are now indented according to the surrounding code.\r\n- This is also true for '\/* *\/' multi-line comments when the second line begins by a '*'.\r\n- Single line '\/* *\/' comments are also indented.","package":"php.vim","4":"php.vim","src_id":"4964","5":"4964","creation_date":"1137085296","6":"1137085296"},{"0":"1120","vim_version":"6.0","1":"6.0","script_version":"1.21","2":"1.21","version_comment":"- 'try' and 'catch' were not registered as block starters so the '{' after a 'try' or 'catch' could be wrongly indented... \r\n(thanks to Gert Muller for finding this issue)","3":"- 'try' and 'catch' were not registered as block starters so the '{' after a 'try' or 'catch' could be wrongly indented... \r\n(thanks to Gert Muller for finding this issue)","package":"php.vim","4":"php.vim","src_id":"4952","5":"4952","creation_date":"1136669647","6":"1136669647"},{"0":"1120","vim_version":"6.0","1":"6.0","script_version":"1.20","2":"1.20","version_comment":"- Line beginning by a single or double quote followed by a space would cause problems... this was related to the bug correction of version 1.10 - Thanks to David F. for finding this (he was lucky). \r\n- Changed the way this script set the 'formatoptions' setting, now it uses '-=' and '+=' \r\n- New option: PHP_autoformatcomment (defaults to 1), if set to 0 the 'formatoptions' setting will not be altered. \r\n- When PHP_autoformatcomment is not 0, the 'comments' setting is set to the type of comments that PHP supports.","3":"- Line beginning by a single or double quote followed by a space would cause problems... this was related to the bug correction of version 1.10 - Thanks to David F. for finding this (he was lucky). \r\n- Changed the way this script set the 'formatoptions' setting, now it uses '-=' and '+=' \r\n- New option: PHP_autoformatcomment (defaults to 1), if set to 0 the 'formatoptions' setting will not be altered. \r\n- When PHP_autoformatcomment is not 0, the 'comments' setting is set to the type of comments that PHP supports.","package":"php.vim","4":"php.vim","src_id":"4791","5":"4791","creation_date":"1132583422","6":"1132583422"},{"0":"1120","vim_version":"6.0","1":"6.0","script_version":"1.19","2":"1.19","version_comment":"- Indentation of '*\/' delimiter of '\/**\/' won't be broken by strings or '\/\/' comments containing the \"\/*\" character sequence.\r\n- I Forgot to register 'interface' and 'abstract' as block starters so the '{' after them could be wrongly indented...","3":"- Indentation of '*\/' delimiter of '\/**\/' won't be broken by strings or '\/\/' comments containing the \"\/*\" character sequence.\r\n- I Forgot to register 'interface' and 'abstract' as block starters so the '{' after them could be wrongly indented...","package":"php.vim","4":"php.vim","src_id":"4776","5":"4776","creation_date":"1132307215","6":"1132307215"},{"0":"1120","vim_version":"6.0","1":"6.0","script_version":"1.181","2":"1.181","version_comment":"- I Forgot to register 'class' as a block starter so the '{' after a 'class' could be wrongly indented...","3":"- I Forgot to register 'class' as a block starter so the '{' after a 'class' could be wrongly indented...","package":"php.vim","4":"php.vim","src_id":"4590","5":"4590","creation_date":"1126892227","6":"1126892227"},{"0":"1120","vim_version":"6.0","1":"6.0","script_version":"1.18","2":"1.18","version_comment":"- No more problem with Vim 6.3 and UTF-8.\r\n- Opening braces \"{\" are always indented according to their block starter.","3":"- No more problem with Vim 6.3 and UTF-8.\r\n- Opening braces \"{\" are always indented according to their block starter.","package":"php.vim","4":"php.vim","src_id":"4587","5":"4587","creation_date":"1126793688","6":"1126793688"},{"0":"1120","vim_version":"6.0","1":"6.0","script_version":"1.17","2":"1.17","version_comment":"- Now starting and ending '*' of multiline '\/* *\/' comments are aligned on the '*' of the '\/*' comment starter.\r\n- Some code improvements that make indentation faster.\r\n- Now following parts of split lines are indented:\r\n    Instead of:\r\n\t$foo=\r\n\t\"foo\"\r\n\t.\"foo\";\r\n\r\n    You have:\r\n\t$foo=\r\n\t    \"foo\"\r\n\t   .\"foo\";\r\n\r\n- If a \"case : break;\" was declared on a single line, the following \"case\" was not indented correctly.\r\n- If a <\/script> html tag was preceded by a \"?>\" it wasn't indented.\r\n- Some other minor corrections and improvements.","3":"- Now starting and ending '*' of multiline '\/* *\/' comments are aligned on the '*' of the '\/*' comment starter.\r\n- Some code improvements that make indentation faster.\r\n- Now following parts of split lines are indented:\r\n    Instead of:\r\n\t$foo=\r\n\t\"foo\"\r\n\t.\"foo\";\r\n\r\n    You have:\r\n\t$foo=\r\n\t    \"foo\"\r\n\t   .\"foo\";\r\n\r\n- If a \"case : break;\" was declared on a single line, the following \"case\" was not indented correctly.\r\n- If a <\/script> html tag was preceded by a \"?>\" it wasn't indented.\r\n- Some other minor corrections and improvements.","package":"php.vim","4":"php.vim","src_id":"4411","5":"4411","creation_date":"1120667464","6":"1120667464"},{"0":"1120","vim_version":"6.0","1":"6.0","script_version":"1.15","2":"1.15","version_comment":"- Corrected some problems with the indentation of multiline \"array()\" declarations.\r\n- Added auto-formatting for comments (using the Vim option formatoptions=qroc).\r\n- Added the script option PHP_BracesAtCodeLevel to indent the '{' and '}' at the same level than the code they contain.\r\n- Some code cleaning and typo corrections (Thanks to Emanuele Giaquinta for his patches)","3":"- Corrected some problems with the indentation of multiline \"array()\" declarations.\r\n- Added auto-formatting for comments (using the Vim option formatoptions=qroc).\r\n- Added the script option PHP_BracesAtCodeLevel to indent the '{' and '}' at the same level than the code they contain.\r\n- Some code cleaning and typo corrections (Thanks to Emanuele Giaquinta for his patches)","package":"php.vim","4":"php.vim","src_id":"4387","5":"4387","creation_date":"1119538591","6":"1119538591"},{"0":"1120","vim_version":"6.0","1":"6.0","script_version":"1.12","2":"1.12","version_comment":"- The bug involving searchpair() and utf-8 encoding in Vim 6.3 will not make this script to hang but you'll have to be careful to not write '\/* *\/' comments with other '\/*' inside the comments else the indentation won't be correct.\r\nNOTE: This is true only if you are using utf-8 and vim 6.3.","3":"- The bug involving searchpair() and utf-8 encoding in Vim 6.3 will not make this script to hang but you'll have to be careful to not write '\/* *\/' comments with other '\/*' inside the comments else the indentation won't be correct.\r\nNOTE: This is true only if you are using utf-8 and vim 6.3.","package":"php.vim","4":"php.vim","src_id":"4330","5":"4330","creation_date":"1117548793","6":"1117548793"},{"0":"1120","vim_version":"6.0","1":"6.0","script_version":"1.11","2":"1.11","version_comment":"If the \"case\" of a \"switch\" wasn't alone on its line and if the \"switch\" was at col 0 (or at default indenting) the lines following the \"case\" were not indented.","3":"If the \"case\" of a \"switch\" wasn't alone on its line and if the \"switch\" was at col 0 (or at default indenting) the lines following the \"case\" were not indented.","package":"php.vim","4":"php.vim","src_id":"4291","5":"4291","creation_date":"1116340904","6":"1116340904"},{"0":"1120","vim_version":"6.0","1":"6.0","script_version":"1.10","2":"1.10","version_comment":"Lines beginning by a single or double quote were not indented in some cases.","3":"Lines beginning by a single or double quote were not indented in some cases.","package":"php.vim","4":"php.vim","src_id":"3893","5":"3893","creation_date":"1109050219","6":"1109050219"},{"0":"1120","vim_version":"6.0","1":"6.0","script_version":"1.09","2":"1.09","version_comment":"The javaScript code was not always directly indented when typing.","3":"The javaScript code was not always directly indented when typing.","package":"php.vim","4":"php.vim","src_id":"3838","5":"3838","creation_date":"1107790696","6":"1107790696"},{"0":"1120","vim_version":"6.0","1":"6.0","script_version":"1.08","2":"1.08","version_comment":"- End comment tags '*\/' are indented like start tags '\/*'.\r\n- When typing a multiline comment, '}' are indented according to other commented '{'.\r\n- Added a new option 'PHP_removeCRwhenUnix' to automatically remove CR at end of lines when the file format is Unix.\r\n- Changed the file format of this very file to Unix.\r\n- This version seems to correct several issues some people had with 1.07.","3":"- End comment tags '*\/' are indented like start tags '\/*'.\r\n- When typing a multiline comment, '}' are indented according to other commented '{'.\r\n- Added a new option 'PHP_removeCRwhenUnix' to automatically remove CR at end of lines when the file format is Unix.\r\n- Changed the file format of this very file to Unix.\r\n- This version seems to correct several issues some people had with 1.07.","package":"php.vim","4":"php.vim","src_id":"3754","5":"3754","creation_date":"1105286741","6":"1105286741"},{"0":"1120","vim_version":"6.0","1":"6.0","script_version":"1.07","2":"1.07","version_comment":"- Added support for \"Here document\" tags: \r\n-   HereDoc end tag are indented properly. \r\n-   HereDoc content remain unchanged. \r\n- All the code that is outside PHP delimiter remains unchanged. \r\n- New feature: The content of <script.*> html tag is considered as PHP and indented according to the surrounding PHP code. \r\n- \"else if\" are detected as \"elseif\". \r\n- Multiline \/**\/ are indented when the user type it but remain unchanged when indenting from their beginning. \r\n- Fixed indenting of \/\/ and # comments. \r\n- php_sync_method option is set to 0 (fromstart). This is required for complex php script else the indent may fail. \r\n- Files with non PHP code at the beginning could alter the indent of the following PHP code. \r\n- Other minor improvments and corrections.","3":"- Added support for \"Here document\" tags: \r\n-   HereDoc end tag are indented properly. \r\n-   HereDoc content remain unchanged. \r\n- All the code that is outside PHP delimiter remains unchanged. \r\n- New feature: The content of <script.*> html tag is considered as PHP and indented according to the surrounding PHP code. \r\n- \"else if\" are detected as \"elseif\". \r\n- Multiline \/**\/ are indented when the user type it but remain unchanged when indenting from their beginning. \r\n- Fixed indenting of \/\/ and # comments. \r\n- php_sync_method option is set to 0 (fromstart). This is required for complex php script else the indent may fail. \r\n- Files with non PHP code at the beginning could alter the indent of the following PHP code. \r\n- Other minor improvments and corrections.","package":"php.vim","4":"php.vim","src_id":"3732","5":"3732","creation_date":"1104126446","6":"1104126446"},{"0":"1120","vim_version":"6.0","1":"6.0","script_version":"1.06","2":"1.06","version_comment":"- Switch block were no longer indented correctly...\r\n- Added an option to use a default indenting instead of 0.\r\n- A problem with ^\\s*);\\= lines where ending a non '{}' structure.\r\n- Changed script local variable to be buffer local variable instead.\r\n","3":"- Switch block were no longer indented correctly...\r\n- Added an option to use a default indenting instead of 0.\r\n- A problem with ^\\s*);\\= lines where ending a non '{}' structure.\r\n- Changed script local variable to be buffer local variable instead.\r\n","package":"php.vim","4":"php.vim","src_id":"3714","5":"3714","creation_date":"1103486131","6":"1103486131"},{"0":"1120","vim_version":"6.0","1":"6.0","script_version":"1.05","2":"1.05","version_comment":"Lines containing \"<?php.* ?>\" and \"?> .*<?php\" (start and end tag on the same line) are no longer indented at col 1 but as normal code.","3":"Lines containing \"<?php.* ?>\" and \"?> .*<?php\" (start and end tag on the same line) are no longer indented at col 1 but as normal code.","package":"php.vim","4":"php.vim","src_id":"3710","5":"3710","creation_date":"1103123624","6":"1103123624"},{"0":"1120","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"php.vim","4":"php.vim","src_id":"3595","5":"3595","creation_date":"1099299175","6":"1099299175"}]},"1119":{"script_id":"1119","0":"1119","script_name":"mod_tcsoft.vim","1":"mod_tcsoft.vim","script_type":"color scheme","2":"color scheme","summary":"modified version of tcsoft.vim-color-scheme","3":"modified version of tcsoft.vim-color-scheme","description":"mod_tcsoft.vim is based on the tcsoft-color scheme (http:\/\/www.vim.org\/scripts\/script.php?script_id=641),\r\nmade by Ingo Fabbri <vim@tcsoft.net>\r\n\r\nI changed the cursor and the background-colors. Hope you like it.\r\n\r\nScreenshot: http:\/\/www.uni-hildesheim.de\/~akel0055\/screens\/mod_tcsoft2.png\r\n\r\n Author: Andr\u00c3\u00a9 Kelpe <fs111 at web dot de>\r\n Last change Sa Okt 30 13:34:52 CEST 2004\r\n","4":"mod_tcsoft.vim is based on the tcsoft-color scheme (http:\/\/www.vim.org\/scripts\/script.php?script_id=641),\r\nmade by Ingo Fabbri <vim@tcsoft.net>\r\n\r\nI changed the cursor and the background-colors. Hope you like it.\r\n\r\nScreenshot: http:\/\/www.uni-hildesheim.de\/~akel0055\/screens\/mod_tcsoft2.png\r\n\r\n Author: Andr\u00c3\u00a9 Kelpe <fs111 at web dot de>\r\n Last change Sa Okt 30 13:34:52 CEST 2004\r\n","install_details":"just put it in your .vim\/colors\/-directory and set :colo mod_tcsoft in your .vimrc if you like it","5":"just put it in your .vim\/colors\/-directory and set :colo mod_tcsoft in your .vimrc if you like it","first_name":"Andr\u00c3\u00a9","6":"Andr\u00c3\u00a9","last_name":"Kelpe","7":"Kelpe","releases":[{"0":"1119","vim_version":"6.0","1":"6.0","script_version":"1.1","2":"1.1","version_comment":"More Modifications:\r\n\r\nFolded, FoldCoulumn, TODO, Search and Comment modified. \r\n\r\nHope you like the changes","3":"More Modifications:\r\n\r\nFolded, FoldCoulumn, TODO, Search and Comment modified. \r\n\r\nHope you like the changes","package":"mod_tcsoft.vim","4":"mod_tcsoft.vim","src_id":"3761","5":"3761","creation_date":"1105578664","6":"1105578664"},{"0":"1119","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"mod_tcsoft.vim","4":"mod_tcsoft.vim","src_id":"3591","5":"3591","creation_date":"1099110357","6":"1099110357"}]},"1118":{"script_id":"1118","0":"1118","script_name":"reverse.vim","1":"reverse.vim","script_type":"utility","2":"utility","summary":"reverse (1st line becomes last ...) the lines in a file","3":"reverse (1st line becomes last ...) the lines in a file","description":"This file has a vim script to reverse the lines in the file.\r\n(line 1 swapped with last line say 5, line 2 swapped with line4 ...)\r\n\r\nI build it because I had such a requirement and could not \r\nthink of anything quicker on Windows. \r\n\r\nUnix people have lot better tricks-). \r\n\r\n\r\nHow to use :\r\nMethod 1: press <F2> if you wanna reverse all the lines\r\nMethod 2: select lines in visual mode and press <F2> \r\n                if you wanna swap only the highlighted lines\r\nMethod 3: To reverse line1 to line2 use :line1,line2 Reverse \r\n","4":"This file has a vim script to reverse the lines in the file.\r\n(line 1 swapped with last line say 5, line 2 swapped with line4 ...)\r\n\r\nI build it because I had such a requirement and could not \r\nthink of anything quicker on Windows. \r\n\r\nUnix people have lot better tricks-). \r\n\r\n\r\nHow to use :\r\nMethod 1: press <F2> if you wanna reverse all the lines\r\nMethod 2: select lines in visual mode and press <F2> \r\n                if you wanna swap only the highlighted lines\r\nMethod 3: To reverse line1 to line2 use :line1,line2 Reverse \r\n","install_details":"simply source the file using \r\n:source <filepath>\\\\reverse.vim\r\nor source it in your vimrc file\r\nfor automatically sourcing this everytime \r\n\r\nCaution: This script maps <F2> key, so if you have already mapped <F2> \r\nkey you should change the mapping in this file to some other key\r\n","5":"simply source the file using \r\n:source <filepath>\\\\reverse.vim\r\nor source it in your vimrc file\r\nfor automatically sourcing this everytime \r\n\r\nCaution: This script maps <F2> key, so if you have already mapped <F2> \r\nkey you should change the mapping in this file to some other key\r\n","first_name":"Amit","6":"Amit","last_name":"Jain","7":"Jain","releases":[{"0":"1118","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"reverse.vim","4":"reverse.vim","src_id":"3590","5":"3590","creation_date":"1099055451","6":"1099055451"}]},"1117":{"script_id":"1117","0":"1117","script_name":"ooosetup.vim","1":"ooosetup.vim","script_type":"syntax","2":"syntax","summary":"OpenOffice.org 1.x\/StarOffice 5.2,6,7 setup response file syntax","3":"OpenOffice.org 1.x\/StarOffice 5.2,6,7 setup response file syntax","description":"This script provides syntax highlighting for the OpenOffice 1.x and StarOffice 5.2, 6.x, 7.x setup responses file as documented by http:\/\/installation.openoffice.org\/01RESPONSE_SO52_final_rev2.pdf\r\n\r\nA test suite for the highlighting is provided (TestSuite.OOo) to help discover bugs. Do not use it with the setup program.\r\n\r\nRelease notes for 1.0 :\r\n- syntax is quite strict about spaces (stricter than the setup program). The TestSuite.OOo will show you what is recognized.\r\n- the Module_Specify may not correctly highlight module sets definitions. Patches are welcome.","4":"This script provides syntax highlighting for the OpenOffice 1.x and StarOffice 5.2, 6.x, 7.x setup responses file as documented by http:\/\/installation.openoffice.org\/01RESPONSE_SO52_final_rev2.pdf\r\n\r\nA test suite for the highlighting is provided (TestSuite.OOo) to help discover bugs. Do not use it with the setup program.\r\n\r\nRelease notes for 1.0 :\r\n- syntax is quite strict about spaces (stricter than the setup program). The TestSuite.OOo will show you what is recognized.\r\n- the Module_Specify may not correctly highlight module sets definitions. Patches are welcome.","install_details":"Put syntax\/ooosetup.vim in your $HOME\/vimfiles\/syntax directory.\r\nTestSuite.OOo is not used by the script.\r\n\r\nTo activate highlighting when editing a response file :\r\n  syntax on\r\n  setf ooosetup","5":"Put syntax\/ooosetup.vim in your $HOME\/vimfiles\/syntax directory.\r\nTestSuite.OOo is not used by the script.\r\n\r\nTo activate highlighting when editing a response file :\r\n  syntax on\r\n  setf ooosetup","first_name":"Olivier","6":"Olivier","last_name":"Mengu\u00c3\u00a9","7":"Mengu\u00c3\u00a9","releases":[{"0":"1117","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"ooosetup-vim-1.0.zip","4":"ooosetup-vim-1.0.zip","src_id":"3589","5":"3589","creation_date":"1099041099","6":"1099041099"}]},"1116":{"script_id":"1116","0":"1116","script_name":"MapleSyrup","1":"MapleSyrup","script_type":"ftplugin","2":"ftplugin","summary":"indenting, autoalign, and matchit support for Maple V","3":"indenting, autoalign, and matchit support for Maple V","description":"This package contains support for writing Maple V code:\r\n\r\n * indent\/maple.vim: indenting support for Maple V\r\n * ftplugin\/AutoAlign.vim: auto-align support for :=\r\n   (needs Align.vim from vimscript#294; to learn more about AutoAlign, see vimscript#884)\r\n * ftplugin\/maple.vim: and matchit support (matchit.vim is available via vimscript#39).\r\n * plugin\/cecutil.vim: \r\n * It contains tags for GetLatestVimScripts support which promote maintaining up-to-date copies (see vimscript#642).\r\n\r\nThe indenting support works with\r\n\r\n\tif for while else elif od end fi\r\n\r\nand indents the code appropriately as you type.  Indents are taken using the current setting of the vim's shiftwidth option (see :he shiftwidth).\r\n\r\nAutoAlignment keeps your := lined up in blocks, thereby promoting legibility.\r\n\r\nThe Matchit expression supports  (see vimscript#39)\r\n\r\n   if     elif    else  fi\r\n   for    od\r\n   while  od\r\n   proc   RETURN  end\r\n\r\nI usually prefer to have (at least) two windows open; the top one with vim editing Maple V code (file.mv) and the bottom one running Maple V itself.  I then work with Maple (using Windows) by changing the file as needed in Vim, putting the cursor at the end of the following statement, then pressing <cr>.\r\n\r\n\tread `c:\\\\some\\\\path\\\\to\\\\Maple\\\\file.mv`;\r\n\r\nThat causes the worksheet to be updated according to the <file.mv> instructions.  Of course, I can always maximize Maple when I need to so as to see more at one time.\r\n\r\nWhy \"maplesyrup\"?  I just couldn't resist the name!  :)\r\n\r\n(alpha\/beta version available at http:\/\/www.drchip.org\/astronaut\/vim\/index.html#MAPLESYRUP)\r\n","4":"This package contains support for writing Maple V code:\r\n\r\n * indent\/maple.vim: indenting support for Maple V\r\n * ftplugin\/AutoAlign.vim: auto-align support for :=\r\n   (needs Align.vim from vimscript#294; to learn more about AutoAlign, see vimscript#884)\r\n * ftplugin\/maple.vim: and matchit support (matchit.vim is available via vimscript#39).\r\n * plugin\/cecutil.vim: \r\n * It contains tags for GetLatestVimScripts support which promote maintaining up-to-date copies (see vimscript#642).\r\n\r\nThe indenting support works with\r\n\r\n\tif for while else elif od end fi\r\n\r\nand indents the code appropriately as you type.  Indents are taken using the current setting of the vim's shiftwidth option (see :he shiftwidth).\r\n\r\nAutoAlignment keeps your := lined up in blocks, thereby promoting legibility.\r\n\r\nThe Matchit expression supports  (see vimscript#39)\r\n\r\n   if     elif    else  fi\r\n   for    od\r\n   while  od\r\n   proc   RETURN  end\r\n\r\nI usually prefer to have (at least) two windows open; the top one with vim editing Maple V code (file.mv) and the bottom one running Maple V itself.  I then work with Maple (using Windows) by changing the file as needed in Vim, putting the cursor at the end of the following statement, then pressing <cr>.\r\n\r\n\tread `c:\\\\some\\\\path\\\\to\\\\Maple\\\\file.mv`;\r\n\r\nThat causes the worksheet to be updated according to the <file.mv> instructions.  Of course, I can always maximize Maple when I need to so as to see more at one time.\r\n\r\nWhy \"maplesyrup\"?  I just couldn't resist the name!  :)\r\n\r\n(alpha\/beta version available at http:\/\/www.drchip.org\/astronaut\/vim\/index.html#MAPLESYRUP)\r\n","install_details":"1. Place maplesyrup.tar.gz in your .vim\/  (Windows:  vimfiles\\) directory\r\n2. gunzip maplesyrup.tar.gz\r\n3. tar -oxvf maplesyrup.tar\r\n4. Be sure that your <.vimrc> has the following lines to enable plugin and indent scripts\r\n\r\n\t\"  Initialize: {{{1\r\n\tset nocp\r\n\tif version >= 600\r\n\t  filetype plugin indent on\r\n\tendif\r\n\r\n5. For AutoAlign'ing := statements, you'll also need to get Align.vim (vimscript#294).\r\n6. For matchit (extended % key use), you'll need to get matchit.vim (vimscript#39).","5":"1. Place maplesyrup.tar.gz in your .vim\/  (Windows:  vimfiles\\) directory\r\n2. gunzip maplesyrup.tar.gz\r\n3. tar -oxvf maplesyrup.tar\r\n4. Be sure that your <.vimrc> has the following lines to enable plugin and indent scripts\r\n\r\n\t\"  Initialize: {{{1\r\n\tset nocp\r\n\tif version >= 600\r\n\t  filetype plugin indent on\r\n\tendif\r\n\r\n5. For AutoAlign'ing := statements, you'll also need to get Align.vim (vimscript#294).\r\n6. For matchit (extended % key use), you'll need to get matchit.vim (vimscript#39).","first_name":"Charles","6":"Charles","last_name":"Campbell","7":"Campbell","releases":[{"0":"1116","vim_version":"6.0","1":"6.0","script_version":"2","2":"2","version_comment":"An improvement to the maple indenting file is included","3":"An improvement to the maple indenting file is included","package":"maplesyrup.tar.gz","4":"maplesyrup.tar.gz","src_id":"3592","5":"3592","creation_date":"1099290511","6":"1099290511"},{"0":"1116","vim_version":"6.0","1":"6.0","script_version":"1","2":"1","version_comment":"Initial upload","3":"Initial upload","package":"maplesyrup.tar.gz","4":"maplesyrup.tar.gz","src_id":"3588","5":"3588","creation_date":"1099030247","6":"1099030247"}]},"1115":{"script_id":"1115","0":"1115","script_name":"BodySnatcher","1":"BodySnatcher","script_type":"utility","2":"utility","summary":"Generate CSS from HTML doc BODY attribs - updates Web docs quickly. Perl req'd.","3":"Generate CSS from HTML doc BODY attribs - updates Web docs quickly. Perl req'd.","description":"if ! has('perl')\r\n    move along, nothing to see here ;-)\r\nendif\r\n\r\nThis plugin does a search of lines of a .html document and parses the statement of the <body> attributes. In modern times we prefer to use CSS to control presentational aspects of Web pages like text color, background, and link color.  When designing a site from scratch we'd plan that ahead of time. When updating a handful of pages that were not originally authored with CSS in mind, a script like this saves time by pulling out the expected HTML attributes and converting them to CSS declarations.\r\n\r\nUpdate 13:07(TZ=EDT) - 28.Oct.2004 -\r\n   My thanks to the dozen or so people who have downloaded version 1.3, and please update to\r\nto version 1.4. Important bugs are fixed in this new release.\r\n\r\nFor more info and an md5 sum to check against, see this tool's home page at\r\nhttp:\/\/intrepid.perlmonk.org\/VIMtools\/BSn\/index.html","4":"if ! has('perl')\r\n    move along, nothing to see here ;-)\r\nendif\r\n\r\nThis plugin does a search of lines of a .html document and parses the statement of the <body> attributes. In modern times we prefer to use CSS to control presentational aspects of Web pages like text color, background, and link color.  When designing a site from scratch we'd plan that ahead of time. When updating a handful of pages that were not originally authored with CSS in mind, a script like this saves time by pulling out the expected HTML attributes and converting them to CSS declarations.\r\n\r\nUpdate 13:07(TZ=EDT) - 28.Oct.2004 -\r\n   My thanks to the dozen or so people who have downloaded version 1.3, and please update to\r\nto version 1.4. Important bugs are fixed in this new release.\r\n\r\nFor more info and an md5 sum to check against, see this tool's home page at\r\nhttp:\/\/intrepid.perlmonk.org\/VIMtools\/BSn\/index.html","install_details":"Place the script somewhere in a \"plugin\/\" directory in VIMRUNTIME, such as\r\n       ~\/.vim\/plugin\r\n ... the plugin does a mapping    <mapleader>))\r\n ... change this if you wish.\r\n\r\nNOTE: An external Perl module (not part of core Perl distribution) is required: Text::Balanced (see http:\/\/search.cpan.org\/src\/DCONWAY\/  for latest version).","5":"Place the script somewhere in a \"plugin\/\" directory in VIMRUNTIME, such as\r\n       ~\/.vim\/plugin\r\n ... the plugin does a mapping    <mapleader>))\r\n ... change this if you wish.\r\n\r\nNOTE: An external Perl module (not part of core Perl distribution) is required: Text::Balanced (see http:\/\/search.cpan.org\/src\/DCONWAY\/  for latest version).","first_name":"S\u00c3\u00b6ren","6":"S\u00c3\u00b6ren","last_name":"Andersen","7":"Andersen","releases":[{"0":"1115","vim_version":"6.0","1":"6.0","script_version":"1.4","2":"1.4","version_comment":"Many bugs fixed.\r\n   - Does the right thing when there is just a plain <body> tag\r\n   - Also make no changes if the <body> tag contains a STYLE= attribute\r\n   - Broken handling of body declaration that is spread over multiple lines is fixed","3":"Many bugs fixed.\r\n   - Does the right thing when there is just a plain <body> tag\r\n   - Also make no changes if the <body> tag contains a STYLE= attribute\r\n   - Broken handling of body declaration that is spread over multiple lines is fixed","package":"BodySnatcher.vim","4":"BodySnatcher.vim","src_id":"3581","5":"3581","creation_date":"1098957367","6":"1098957367"},{"0":"1115","vim_version":"6.0","1":"6.0","script_version":"1.3","2":"1.3","version_comment":"Initial upload","3":"Initial upload","package":"BodySnatcher.vim","4":"BodySnatcher.vim","src_id":"3580","5":"3580","creation_date":"1098912434","6":"1098912434"}]},"1114":{"script_id":"1114","0":"1114","script_name":"pmd.vim","1":"pmd.vim","script_type":"utility","2":"utility","summary":"Integrates PMD using Vim quickfix mode","3":"Integrates PMD using Vim quickfix mode","description":"PMD (see http:\/\/pmd.sourceforge.net) is a utility that scans Java source code to find potential problems, unused variables, unnecessary imports, etc.  This plugin integrates PMD with Vim using Vim's quickfix features (see :help quickfix).\r\n\r\nTo invoke PMD from Vim, either issue the command :Pmd or enter <Leader>pmd from command mode.  The latter keystroke command may be customized.  See the pmd.vim file for details.\r\n\r\nThe :Pmd command may take one argument, which the file or directory to run PMD against.  If left out, PMD will run against the filename of the current buffer, which is also the behavior of the <Leader>pmd keystroke command.","4":"PMD (see http:\/\/pmd.sourceforge.net) is a utility that scans Java source code to find potential problems, unused variables, unnecessary imports, etc.  This plugin integrates PMD with Vim using Vim's quickfix features (see :help quickfix).\r\n\r\nTo invoke PMD from Vim, either issue the command :Pmd or enter <Leader>pmd from command mode.  The latter keystroke command may be customized.  See the pmd.vim file for details.\r\n\r\nThe :Pmd command may take one argument, which the file or directory to run PMD against.  If left out, PMD will run against the filename of the current buffer, which is also the behavior of the <Leader>pmd keystroke command.","install_details":"Copy the pmd.vim file into the plugin directory or source it as needed.  There are two settings.  The command to run PMD should be set in the Pmd_Cmd variable.  The PMD rulesets to use should be set in the Pmd_Rulesets variable.  See the pmd.vim file for details.","5":"Copy the pmd.vim file into the plugin directory or source it as needed.  There are two settings.  The command to run PMD should be set in the Pmd_Cmd variable.  The PMD rulesets to use should be set in the Pmd_Rulesets variable.  See the pmd.vim file for details.","first_name":"Henry","6":"Henry","last_name":"So, Jr.","7":"So, Jr.","releases":[{"0":"1114","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"pmd.vim","4":"pmd.vim","src_id":"3577","5":"3577","creation_date":"1098817930","6":"1098817930"}]},"1113":{"script_id":"1113","0":"1113","script_name":"TWiki-Syntax","1":"TWiki-Syntax","script_type":"syntax","2":"syntax","summary":"Syntaxfile for TWiki-Syntax","3":"Syntaxfile for TWiki-Syntax","description":"Syntaxfile for TWiki syntax (http:\/\/www.twiki.org)\r\nOne can configure Mozilla to use an external editor for editing HTML-edit-fields. So when one uses vim, he gets his code highlighted.\r\n\r\nFor configuring mozilla, go to http:\/\/mozex.mozdev.org\r\n\r\nStill isn't ready, so email feedback to me or, better, join the project on http:\/\/www.sourceforge.net\/projects\/vim-twiki\r\n","4":"Syntaxfile for TWiki syntax (http:\/\/www.twiki.org)\r\nOne can configure Mozilla to use an external editor for editing HTML-edit-fields. So when one uses vim, he gets his code highlighted.\r\n\r\nFor configuring mozilla, go to http:\/\/mozex.mozdev.org\r\n\r\nStill isn't ready, so email feedback to me or, better, join the project on http:\/\/www.sourceforge.net\/projects\/vim-twiki\r\n","install_details":"Tarfile contains:\r\nREADME\r\nLICENSE\r\nscripts.vim\r\nftplugin\/twiki.vim\r\nsyntax\/twiki.vim","5":"Tarfile contains:\r\nREADME\r\nLICENSE\r\nscripts.vim\r\nftplugin\/twiki.vim\r\nsyntax\/twiki.vim","first_name":"Rainer","6":"Rainer","last_name":"Thierfelder","7":"Thierfelder","releases":[{"0":"1113","vim_version":"6.0","1":"6.0","script_version":"0.7","2":"0.7","version_comment":"New Version from sourceforge (just released)","3":"New Version from sourceforge (just released)","package":"vim-twiki-0.7.tar.gz","4":"vim-twiki-0.7.tar.gz","src_id":"6460","5":"6460","creation_date":"1164186372","6":"1164186372"},{"0":"1113","vim_version":"6.0","1":"6.0","script_version":"0.6","2":"0.6","version_comment":"Split into two files, syntax and ftplugin. Improvements from 'ehaar'. Changed license to GPL.","3":"Split into two files, syntax and ftplugin. Improvements from 'ehaar'. Changed license to GPL.","package":"vim-twiki.tar","4":"vim-twiki.tar","src_id":"5360","5":"5360","creation_date":"1141446876","6":"1141446876"},{"0":"1113","vim_version":"6.0","1":"6.0","script_version":"0.5","2":"0.5","version_comment":"Initial upload","3":"Initial upload","package":"twiki.vim","4":"twiki.vim","src_id":"3572","5":"3572","creation_date":"1098667114","6":"1098667114"}]},"1112":{"script_id":"1112","0":"1112","script_name":"pydoc.vim","1":"pydoc.vim","script_type":"utility","2":"utility","summary":"Pulls external python documentation into a Vim window.","3":"Pulls external python documentation into a Vim window.","description":"This utility will invoke the external pydoc script (pydoc.py comes with the standard Python installation) and use it to retrieve relevant documentation. This information is displayed in a new Vim window just like the internal Vim help. Remaps the 'K' command to provide for easy access. For example, let's say you're editing a program that uses the 'os' module. Simply position the cursor over 'os' and hit K and a new window will appear (in Vim) with the full module documentation. As a cool side effect, the pydoc buffers are now candidates for text completion, so this script provides a quick and easy way of loading a module's identifiers into your completion list.\r\n\r\nAndre Kelpe has kindly emailed me to let me know he has a script vimscript #910 that does much the same thing. Unfortunately, it doesn't show up when you do a search for Python so I was unaware of it :-(. Apologies to Andre, but we are in discussion about possibly merging the two as they both have some cool features.\r\n\r\nEDIT\r\n10.25.2004 (mention the other pydoc script)","4":"This utility will invoke the external pydoc script (pydoc.py comes with the standard Python installation) and use it to retrieve relevant documentation. This information is displayed in a new Vim window just like the internal Vim help. Remaps the 'K' command to provide for easy access. For example, let's say you're editing a program that uses the 'os' module. Simply position the cursor over 'os' and hit K and a new window will appear (in Vim) with the full module documentation. As a cool side effect, the pydoc buffers are now candidates for text completion, so this script provides a quick and easy way of loading a module's identifiers into your completion list.\r\n\r\nAndre Kelpe has kindly emailed me to let me know he has a script vimscript #910 that does much the same thing. Unfortunately, it doesn't show up when you do a search for Python so I was unaware of it :-(. Apologies to Andre, but we are in discussion about possibly merging the two as they both have some cool features.\r\n\r\nEDIT\r\n10.25.2004 (mention the other pydoc script)","install_details":"Please read the script for full installation details.","5":"Please read the script for full installation details.","first_name":"Mike","6":"Mike","last_name":"Repass","7":"Repass","releases":[{"0":"1112","vim_version":"6.0","1":"6.0","script_version":"0.4","2":"0.4","version_comment":"Initial upload","3":"Initial upload","package":"pydoc.vim","4":"pydoc.vim","src_id":"3570","5":"3570","creation_date":"1098626981","6":"1098626981"}]},"1111":{"script_id":"1111","0":"1111","script_name":"rcs.vim","1":"rcs.vim","script_type":"utility","2":"utility","summary":"Automatically handle RCS files","3":"Automatically handle RCS files","description":"This is a set of autocommands, commands, and a menu to help you handle RCS controlled files.\r\n\r\nIf you try to modify a readonly file that has a RCS\/<file>,v counterpart you will be asked if you want to check the file out for modification, and when you unload the buffer you'll be prompted if you want to check the file back in, and allowed to enter a log message.\r\n\r\nMost of the commands have corresponding menu items, which should be fairly self-explanatory.\r\n\r\nDetails are in the auto-generated help file, see \":help rcs.txt\".","4":"This is a set of autocommands, commands, and a menu to help you handle RCS controlled files.\r\n\r\nIf you try to modify a readonly file that has a RCS\/<file>,v counterpart you will be asked if you want to check the file out for modification, and when you unload the buffer you'll be prompted if you want to check the file back in, and allowed to enter a log message.\r\n\r\nMost of the commands have corresponding menu items, which should be fairly self-explanatory.\r\n\r\nDetails are in the auto-generated help file, see \":help rcs.txt\".","install_details":"Place rcs.vim in your plugin directory.  See \":help 'runtimepath'\".  If the help file isn't automatically generated, try doing \":RCSUpdateHelp ~\/.vim\/doc\".","5":"Place rcs.vim in your plugin directory.  See \":help 'runtimepath'\".  If the help file isn't automatically generated, try doing \":RCSUpdateHelp ~\/.vim\/doc\".","first_name":"Christian J.","6":"Christian J.","last_name":"Robinson","7":"Robinson","releases":[{"0":"1111","vim_version":"8.0","1":"8.0","script_version":"0.16.0","2":"0.16.0","version_comment":"- Always load the menu to simplify the script logic\r\n- Support Windows","3":"- Always load the menu to simplify the script logic\r\n- Support Windows","package":"rcs.vim","4":"rcs.vim","src_id":"26402","5":"26402","creation_date":"1551006410","6":"1551006410"},{"0":"1111","vim_version":"7.0","1":"7.0","script_version":"0.15.2","2":"0.15.2","version_comment":"- Suggestions by Jon Peatfield for the checkout routine:\r\n  + Prompt the user on checkout if there were \"unlocked\" changes\r\n  + Check for a lock by another user\r\n- A few minor changes and fixes","3":"- Suggestions by Jon Peatfield for the checkout routine:\r\n  + Prompt the user on checkout if there were \"unlocked\" changes\r\n  + Check for a lock by another user\r\n- A few minor changes and fixes","package":"rcs.vim","4":"rcs.vim","src_id":"13110","5":"13110","creation_date":"1275692266","6":"1275692266"},{"0":"1111","vim_version":"7.0","1":"7.0","script_version":"0.14","2":"0.14","version_comment":"- Detect RCS's ,v files in the file's cwd as well (Jon Peatfield)","3":"- Detect RCS's ,v files in the file's cwd as well (Jon Peatfield)","package":"rcs.vim","4":"rcs.vim","src_id":"12897","5":"12897","creation_date":"1272140309","6":"1272140309"},{"0":"1111","vim_version":"7.0","1":"7.0","script_version":"0.13.1","2":"0.13.1","version_comment":"- Fix error when g:rcs_plugin_* isn't set (Sven Bischof)\r\n- Prompt the user when the file is unwritten and :RCSci is used (Sven Bischof)\r\n- Sometimes the help file wasn't being generated--try a different method (Sven Bischof)","3":"- Fix error when g:rcs_plugin_* isn't set (Sven Bischof)\r\n- Prompt the user when the file is unwritten and :RCSci is used (Sven Bischof)\r\n- Sometimes the help file wasn't being generated--try a different method (Sven Bischof)","package":"rcs.vim","4":"rcs.vim","src_id":"9168","5":"9168","creation_date":"1219673559","6":"1219673559"},{"0":"1111","vim_version":"7.0","1":"7.0","script_version":"0.12","2":"0.12","version_comment":"- Try to safely escape shell commands","3":"- Try to safely escape shell commands","package":"rcs.vim","4":"rcs.vim","src_id":"8807","5":"8807","creation_date":"1213568216","6":"1213568216"},{"0":"1111","vim_version":"7.0","1":"7.0","script_version":"0.11.1","2":"0.11.1","version_comment":"- Use matchadd() instead of :2match -- less likelihood of a \"collision\" with another plugin\r\n- Make entering the log messages easier\r\n- Don't go into diff mode if a diff is already open in Vim\r\n- Allow diffing of two consecutive revisions from the log view\r\n- misc. minor changes","3":"- Use matchadd() instead of :2match -- less likelihood of a \"collision\" with another plugin\r\n- Make entering the log messages easier\r\n- Don't go into diff mode if a diff is already open in Vim\r\n- Allow diffing of two consecutive revisions from the log view\r\n- misc. minor changes","package":"rcs.vim","4":"rcs.vim","src_id":"8760","5":"8760","creation_date":"1212723394","6":"1212723394"},{"0":"1111","vim_version":"7.0","1":"7.0","script_version":"0.10","2":"0.10","version_comment":"- Abandoned Vim 6 support\r\n- Allow editing of individual revision log messages from the log display\r\n- Auto-install a help file if possible","3":"- Abandoned Vim 6 support\r\n- Allow editing of individual revision log messages from the log display\r\n- Auto-install a help file if possible","package":"rcs.vim","4":"rcs.vim","src_id":"8619","5":"8619","creation_date":"1209476213","6":"1209476213"},{"0":"1111","vim_version":"6.0","1":"6.0","script_version":"0.4","2":"0.4","version_comment":"- Open the folds where the cursor is located when the file is checked out on the FileChangedRO event\r\n- Internal documentation added\r\n- Code clean up","3":"- Open the folds where the cursor is located when the file is checked out on the FileChangedRO event\r\n- Internal documentation added\r\n- Code clean up","package":"rcs.vim","4":"rcs.vim","src_id":"8534","5":"8534","creation_date":"1207646905","6":"1207646905"},{"0":"1111","vim_version":"6.0","1":"6.0","script_version":"0.3","2":"0.3","version_comment":"- Preserve the cursor position when reloading the file. (Mical Ward)","3":"- Preserve the cursor position when reloading the file. (Mical Ward)","package":"rcs.vim","4":"rcs.vim","src_id":"6101","5":"6101","creation_date":"1156575791","6":"1156575791"},{"0":"1111","vim_version":"6.0","1":"6.0","script_version":"0.2","2":"0.2","version_comment":"- Minor changes to make it compatible with Vim 7.","3":"- Minor changes to make it compatible with Vim 7.","package":"rcs.vim","4":"rcs.vim","src_id":"5538","5":"5538","creation_date":"1144719834","6":"1144719834"},{"0":"1111","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"rcs.vim","4":"rcs.vim","src_id":"3569","5":"3569","creation_date":"1098495420","6":"1098495420"}]},"1110":{"script_id":"1110","0":"1110","script_name":"edifile.vim","1":"edifile.vim","script_type":"syntax","2":"syntax","summary":"Simple syntax highlighting for EDI files","3":"Simple syntax highlighting for EDI files","description":"Currently simply highlights GS\/GE, ST\/SE segments in the Comment color, also highlights all other segment names in the Keyword color. It then also highlights the field seperators and segment terminator characters.","4":"Currently simply highlights GS\/GE, ST\/SE segments in the Comment color, also highlights all other segment names in the Keyword color. It then also highlights the field seperators and segment terminator characters.","install_details":"Just drop it into the ~\/.vim\/syntax folder, and setup your ~\/.vim\/filetypes.vim file as needed for your edi filename style.","5":"Just drop it into the ~\/.vim\/syntax folder, and setup your ~\/.vim\/filetypes.vim file as needed for your edi filename style.","first_name":"Jeremy","6":"Jeremy","last_name":"Cowgar","7":"Cowgar","releases":[{"0":"1110","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"edifile.vim","4":"edifile.vim","src_id":"3562","5":"3562","creation_date":"1098212864","6":"1098212864"}]},"1109":{"script_id":"1109","0":"1109","script_name":"bulgarian.vim","1":"bulgarian.vim","script_type":"utility","2":"utility","summary":"Bulgarian phonetic keymap for vim","3":"Bulgarian phonetic keymap for vim","description":"A phonetic bulgarian cyrillic keymap (UTF-8)\r\n\r\nThis phonetic map is quite similar to the way the Gtk cyrillic input module works: for your convenience, some symbols can be entered in different ways; for instance, to enter the \"shcha\" you can type \"sj\" (as in the gtk module) or \"sht\".","4":"A phonetic bulgarian cyrillic keymap (UTF-8)\r\n\r\nThis phonetic map is quite similar to the way the Gtk cyrillic input module works: for your convenience, some symbols can be entered in different ways; for instance, to enter the \"shcha\" you can type \"sj\" (as in the gtk module) or \"sht\".","install_details":"Just copy the file to $VIM\/vimfiles\/keymap; to enter cyrillic mode, issue the command:\r\n:set keymap=bulgarian","5":"Just copy the file to $VIM\/vimfiles\/keymap; to enter cyrillic mode, issue the command:\r\n:set keymap=bulgarian","first_name":"Alberto","6":"Alberto","last_name":"Mardegan","7":"Mardegan","releases":[{"0":"1109","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"bulgarian.vim","4":"bulgarian.vim","src_id":"3558","5":"3558","creation_date":"1098072030","6":"1098072030"}]},"1108":{"script_id":"1108","0":"1108","script_name":"WhatsMissing.vim","1":"WhatsMissing.vim","script_type":"utility","2":"utility","summary":"Shows what is missing (or not) between 2 buffers","3":"Shows what is missing (or not) between 2 buffers","description":"This plugin contains functions\/commands that will cycle through one \r\nbuffer (the source) and compare the its contents against the contents of\r\nanother buffer (the target).\r\n\r\nNOTE:  This is not a poor man's 'diff', since the source and target must be \r\n              similar in appearance.  See example below for a better understanding.\r\n                                                                              \r\nDepending on the options specified and command chosen, it will open a split\r\nwindow (the result) and display either the entries that are:\r\n   - missing from the target buffer\r\n   or\r\n   - contained in both buffers\r\n   \r\nThe plugin has created a menu, Plugin->WhatMissing.  There are a few entries: \r\n    WhatsMissing\r\n    WhatsNotMissing\r\n    Remove Matches\r\n\r\nThese menu items are also available in visual mode.  These menu items simply call the commands: \r\n    :WhatsMissing\r\n    :WhatsNotMissing\r\n    :WhatsNotMissingRemoveMatches\r\n\r\nThe behavior of whatsmissing.vim are governed by several options. Options can be specified using the WMSetOption command.  As mentioned above, the <Tab> button can be used for both option name and option value completion.\r\n                                                                            \r\nYou can check the value of a specific option by: \r\n    :WMGetOption option_name\r\n \r\nHere are the various options: \r\n   mode  \r\n       - Values: \"word\" or \"line\".  \r\n       - WhatsMissing will move through the source buffer one |word| at a\r\n         time, and checks this value against the target buffer.  It will \r\n         also automatically escape the following characters: \r\n               '\\\\\/.*$^~[]'\r\n         If the \"line\" mode is chosen the comparison between the source \r\n         and target buffer is performed a line at a time. \r\n                                                                            \r\n   ignore_case \r\n       - Values: \"0\" or \"1\".  \r\n       - The \"default\" for WhatsMissing is to use the |'ignorecase'| option\r\n         of the target buffer.  Otherwise the user is allowed to override\r\n         it. \r\n                                                                            \r\n   ignore_whitespace\r\n       - Values: \"0\" or \"1\".  \r\n       - If in \"line\" mode, you can choose to ignore leading and trailing\r\n         whitespace for the comparison. \r\n\r\n\r\nWhatsMissing\r\n-------------------\r\nConsider the case where you are maintaining a Vim syntax file.  It has entries like this:\r\n*************\r\nsyn keyword sqlFunction\tcount sum avg min max debug_eng isnull\r\nsyn keyword sqlFunction\tgreater lesser argn string ymd todate\r\nsyn keyword sqlFunction sp_addalias\r\nsyn keyword sqlFunction sp_addauditrecord\r\nsyn keyword sqlKeyword\treplicate rereceive resend reset\r\nsyn keyword sqlKeyword\tresolve resource respect\r\nsyn keyword sqlKeyword\trestrict result retain\r\nsyn keyword sqlStatement allocate alter backup begin call case\r\nsyn keyword sqlStatement checkpoint clear close commit configure connect\r\nsyn keyword sqlStatement create deallocate declare delete describe\r\nsyn keyword sqlType\tchar long varchar text\r\nsyn keyword sqlType\tbigint decimal double float int integer numeric \r\n*************\r\n\r\nIn order to create the syntax file in the first place you had to find the above words from somewhere.  In this case, I simply used grep against the source code to find various API method names, keywords, functions and so on.\r\n\r\nSo in the end after running grep repeatedly and massaging the output, I end up with a file like this:\r\n**************\r\nabs\r\nabsolute\r\naction\r\nactiv\r\nexpanded\r\nexperience_estimate\r\nexplanation\r\nexplicit\r\nexpress\r\nexprtype\r\nremainder\r\nremote\r\nremove\r\nrename\r\nreorganize\r\nreplicate \r\nrereceive \r\nresend \r\nreset\r\nvalue\r\nvalues\r\nvarbinary\r\nvarchar\r\nvarexists\r\n**************\r\n\r\nAt this point you want to update your Vim syntax file to include all the new method names, keywords, functions and so on that are missing from the existing syntax file.\r\n\r\nYou cannot run Diff against this, since the lines are completely different, you need to compare the words.\r\n\r\nAfter running :WhatsMissing, you end up with a split buffer showing (in this case), only the words missing.  This reduces the work required to determine which syntax elements to add to your file.\r\n***************\r\n(19 of 24) items missing from: syntax.vim\r\n----------\r\nabs\r\nabsolute\r\naction\r\nactiv\r\nexpanded\r\nexperience_estimate\r\nexplanation\r\nexplicit\r\nexpress\r\nexprtype\r\nremainder\r\nremote\r\nremove\r\nrename\r\nreorganize\r\nvalue\r\nvalues\r\nvarbinary\r\nvarexists\r\n----------\r\nWMOptions:\r\nmode=word ignore_case=  ignore_whitespace=0\r\n***************\r\n\r\nOf course, the above example is for Vim syntax files, but it can be used for anything.\r\n\r\n\r\nWhatsNotMissing\r\n-----------------------\r\nIs nearly identical to WhatsMissing, except it will tell you which words are in both files.  I use this in conjunction with WhatsNotMissingRemoveMatches.\r\n\r\n\r\nWhatsNotMissingRemoveMatches\r\n----------------------------------------------\r\nWhen I create my syntax files, I run a process against source files\r\nto generate a list of syntax items.  I then compare this file to my \r\nmysyntax.vim file using the WhatsMissing command.  Any items missing \r\nI added to the mysyntax.vim file.\r\n                                                                            \r\nThere can be times though, that I generate my syntax list file, but \r\nsince this can be an less than exact science, I already have another \r\nfile with a list of words that I have already analyzed and determined \r\nthey are not valid syntax items.  So when the target software releases \r\na new version, I have to go through this process a second time.  So, \r\nthe steps become:\r\n    1.  I generate a list of syntax items.\r\n    2.  Using WhatsNotMissing, I check this new list against another \r\n        list of items I already know should not be included in the \r\n        mysyntax.vim file.\r\n    3.  WhatsNotMissingRemoveMatches will loop through the matches \r\n        and remove them from step 1.\r\n    4.  Now I run WhatsMissing from the file in step 1 against \r\n        the mysyntax.vim file.\r\n    5.  Now the list of words which are missing, I go through each one \r\n        and either add them word to mysyntax.vim or I add it to \r\n        file (from step 2) which is a list of exclusions.\r\n    6.  The list of exclusions is now ready for the next time the software \r\n        release happens, I do not have to redo that work.\r\n\r\n","4":"This plugin contains functions\/commands that will cycle through one \r\nbuffer (the source) and compare the its contents against the contents of\r\nanother buffer (the target).\r\n\r\nNOTE:  This is not a poor man's 'diff', since the source and target must be \r\n              similar in appearance.  See example below for a better understanding.\r\n                                                                              \r\nDepending on the options specified and command chosen, it will open a split\r\nwindow (the result) and display either the entries that are:\r\n   - missing from the target buffer\r\n   or\r\n   - contained in both buffers\r\n   \r\nThe plugin has created a menu, Plugin->WhatMissing.  There are a few entries: \r\n    WhatsMissing\r\n    WhatsNotMissing\r\n    Remove Matches\r\n\r\nThese menu items are also available in visual mode.  These menu items simply call the commands: \r\n    :WhatsMissing\r\n    :WhatsNotMissing\r\n    :WhatsNotMissingRemoveMatches\r\n\r\nThe behavior of whatsmissing.vim are governed by several options. Options can be specified using the WMSetOption command.  As mentioned above, the <Tab> button can be used for both option name and option value completion.\r\n                                                                            \r\nYou can check the value of a specific option by: \r\n    :WMGetOption option_name\r\n \r\nHere are the various options: \r\n   mode  \r\n       - Values: \"word\" or \"line\".  \r\n       - WhatsMissing will move through the source buffer one |word| at a\r\n         time, and checks this value against the target buffer.  It will \r\n         also automatically escape the following characters: \r\n               '\\\\\/.*$^~[]'\r\n         If the \"line\" mode is chosen the comparison between the source \r\n         and target buffer is performed a line at a time. \r\n                                                                            \r\n   ignore_case \r\n       - Values: \"0\" or \"1\".  \r\n       - The \"default\" for WhatsMissing is to use the |'ignorecase'| option\r\n         of the target buffer.  Otherwise the user is allowed to override\r\n         it. \r\n                                                                            \r\n   ignore_whitespace\r\n       - Values: \"0\" or \"1\".  \r\n       - If in \"line\" mode, you can choose to ignore leading and trailing\r\n         whitespace for the comparison. \r\n\r\n\r\nWhatsMissing\r\n-------------------\r\nConsider the case where you are maintaining a Vim syntax file.  It has entries like this:\r\n*************\r\nsyn keyword sqlFunction\tcount sum avg min max debug_eng isnull\r\nsyn keyword sqlFunction\tgreater lesser argn string ymd todate\r\nsyn keyword sqlFunction sp_addalias\r\nsyn keyword sqlFunction sp_addauditrecord\r\nsyn keyword sqlKeyword\treplicate rereceive resend reset\r\nsyn keyword sqlKeyword\tresolve resource respect\r\nsyn keyword sqlKeyword\trestrict result retain\r\nsyn keyword sqlStatement allocate alter backup begin call case\r\nsyn keyword sqlStatement checkpoint clear close commit configure connect\r\nsyn keyword sqlStatement create deallocate declare delete describe\r\nsyn keyword sqlType\tchar long varchar text\r\nsyn keyword sqlType\tbigint decimal double float int integer numeric \r\n*************\r\n\r\nIn order to create the syntax file in the first place you had to find the above words from somewhere.  In this case, I simply used grep against the source code to find various API method names, keywords, functions and so on.\r\n\r\nSo in the end after running grep repeatedly and massaging the output, I end up with a file like this:\r\n**************\r\nabs\r\nabsolute\r\naction\r\nactiv\r\nexpanded\r\nexperience_estimate\r\nexplanation\r\nexplicit\r\nexpress\r\nexprtype\r\nremainder\r\nremote\r\nremove\r\nrename\r\nreorganize\r\nreplicate \r\nrereceive \r\nresend \r\nreset\r\nvalue\r\nvalues\r\nvarbinary\r\nvarchar\r\nvarexists\r\n**************\r\n\r\nAt this point you want to update your Vim syntax file to include all the new method names, keywords, functions and so on that are missing from the existing syntax file.\r\n\r\nYou cannot run Diff against this, since the lines are completely different, you need to compare the words.\r\n\r\nAfter running :WhatsMissing, you end up with a split buffer showing (in this case), only the words missing.  This reduces the work required to determine which syntax elements to add to your file.\r\n***************\r\n(19 of 24) items missing from: syntax.vim\r\n----------\r\nabs\r\nabsolute\r\naction\r\nactiv\r\nexpanded\r\nexperience_estimate\r\nexplanation\r\nexplicit\r\nexpress\r\nexprtype\r\nremainder\r\nremote\r\nremove\r\nrename\r\nreorganize\r\nvalue\r\nvalues\r\nvarbinary\r\nvarexists\r\n----------\r\nWMOptions:\r\nmode=word ignore_case=  ignore_whitespace=0\r\n***************\r\n\r\nOf course, the above example is for Vim syntax files, but it can be used for anything.\r\n\r\n\r\nWhatsNotMissing\r\n-----------------------\r\nIs nearly identical to WhatsMissing, except it will tell you which words are in both files.  I use this in conjunction with WhatsNotMissingRemoveMatches.\r\n\r\n\r\nWhatsNotMissingRemoveMatches\r\n----------------------------------------------\r\nWhen I create my syntax files, I run a process against source files\r\nto generate a list of syntax items.  I then compare this file to my \r\nmysyntax.vim file using the WhatsMissing command.  Any items missing \r\nI added to the mysyntax.vim file.\r\n                                                                            \r\nThere can be times though, that I generate my syntax list file, but \r\nsince this can be an less than exact science, I already have another \r\nfile with a list of words that I have already analyzed and determined \r\nthey are not valid syntax items.  So when the target software releases \r\na new version, I have to go through this process a second time.  So, \r\nthe steps become:\r\n    1.  I generate a list of syntax items.\r\n    2.  Using WhatsNotMissing, I check this new list against another \r\n        list of items I already know should not be included in the \r\n        mysyntax.vim file.\r\n    3.  WhatsNotMissingRemoveMatches will loop through the matches \r\n        and remove them from step 1.\r\n    4.  Now I run WhatsMissing from the file in step 1 against \r\n        the mysyntax.vim file.\r\n    5.  Now the list of words which are missing, I go through each one \r\n        and either add them word to mysyntax.vim or I add it to \r\n        file (from step 2) which is a list of exclusions.\r\n    6.  The list of exclusions is now ready for the next time the software \r\n        release happens, I do not have to redo that work.\r\n\r\n","install_details":"The zip file contains the necessary path structure.\r\n\r\nOn *nix, unzip into:\r\n$HOME\/.vim\/\r\n\r\nOn Windows unzip into:\r\nvim\/vimfiles\/\r\n\r\nFiles:\r\nplugin\/whatsmissing.vim\r\nautoload\/whatsmissing.vim\r\ndoc\/whatsmissing.txt \r\n\r\nTo update the Vim Help, run:\r\n:helptags $HOME\/.vim\/doc  (Unix)\r\n:helptags $VIM\/vimfiles\/doc  (Windows) \r\n","5":"The zip file contains the necessary path structure.\r\n\r\nOn *nix, unzip into:\r\n$HOME\/.vim\/\r\n\r\nOn Windows unzip into:\r\nvim\/vimfiles\/\r\n\r\nFiles:\r\nplugin\/whatsmissing.vim\r\nautoload\/whatsmissing.vim\r\ndoc\/whatsmissing.txt \r\n\r\nTo update the Vim Help, run:\r\n:helptags $HOME\/.vim\/doc  (Unix)\r\n:helptags $VIM\/vimfiles\/doc  (Windows) \r\n","first_name":"David","6":"David","last_name":"Fishburn","7":"Fishburn","releases":[{"0":"1108","vim_version":"7.0","1":"7.0","script_version":"5.0","2":"5.0","version_comment":"New Features:\r\n\r\nAdded filename completion to WhatsMissing and WhatsNotMissing\r\n\r\nAdded new command WhatsNotMissingRemoveMatches, see description and :h WhatsMissing.txt for more details.\r\n\r\n","3":"New Features:\r\n\r\nAdded filename completion to WhatsMissing and WhatsNotMissing\r\n\r\nAdded new command WhatsNotMissingRemoveMatches, see description and :h WhatsMissing.txt for more details.\r\n\r\n","package":"whatsmissing_5.zip","4":"whatsmissing_5.zip","src_id":"18831","5":"18831","creation_date":"1350519683","6":"1350519683"},{"0":"1108","vim_version":"7.0","1":"7.0","script_version":"4.0","2":"4.0","version_comment":"- Added a number of new or missing Vim Events (to be ignored)\r\n\r\n- Converted to an autoload plugin (for faster Vim loading)\r\n\r\n- Correctly handled the cpo for 'a' and 'A'\r\n\r\n- Added a few more examples are more explicity defined which is the source and target files from the WhatsMissing command line\r\n","3":"- Added a number of new or missing Vim Events (to be ignored)\r\n\r\n- Converted to an autoload plugin (for faster Vim loading)\r\n\r\n- Correctly handled the cpo for 'a' and 'A'\r\n\r\n- Added a few more examples are more explicity defined which is the source and target files from the WhatsMissing command line\r\n","package":"whatmissing_4.zip","4":"whatmissing_4.zip","src_id":"18793","5":"18793","creation_date":"1350088738","6":"1350088738"},{"0":"1108","vim_version":"6.0","1":"6.0","script_version":"3.0","2":"3.0","version_comment":"There was a logic error when prompting the user for the options.  Ignore case value was reversed.","3":"There was a logic error when prompting the user for the options.  Ignore case value was reversed.","package":"WhatsMissing.vim","4":"WhatsMissing.vim","src_id":"17299","5":"17299","creation_date":"1327289584","6":"1327289584"},{"0":"1108","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Documentation and GetLastestVimScripts support","3":"Documentation and GetLastestVimScripts support","package":"WhatsMissing.zip","4":"WhatsMissing.zip","src_id":"3557","5":"3557","creation_date":"1098040580","6":"1098040580"}]},"1107":{"script_id":"1107","0":"1107","script_name":"AutumnLeaf","1":"AutumnLeaf","script_type":"color scheme","2":"color scheme","summary":"Practical, beautiful seasonal colors.","3":"Practical, beautiful seasonal colors.","description":"Update 2\/2017: I recommend downloading a modification of this scheme made by 7 LI.\r\nYou can get it here: vimscript #4109\r\n\r\n\r\nThe colors of a Finnish autumn morning captured and packed in a nice color scheme which is light orange\/blue\/green and doesn't strain the eye.\r\n\r\nThis scheme was created to serve more as a tool for users who work with code such as C\/C++ or Perl. Also handy with XHTML\/HTML\/CSS and why not plain text too.\r\n\r\nRich syntax highlightings, cterm supported.","4":"Update 2\/2017: I recommend downloading a modification of this scheme made by 7 LI.\r\nYou can get it here: vimscript #4109\r\n\r\n\r\nThe colors of a Finnish autumn morning captured and packed in a nice color scheme which is light orange\/blue\/green and doesn't strain the eye.\r\n\r\nThis scheme was created to serve more as a tool for users who work with code such as C\/C++ or Perl. Also handy with XHTML\/HTML\/CSS and why not plain text too.\r\n\r\nRich syntax highlightings, cterm supported.","install_details":"A) UNIX\/Linux: Download to ~\/.vim\/colors\/.\r\nB) Win32: Download to <vim directory>\/vimfiles\/colors\/.\r\n\r\nOpen Vim, type :colors AutumnLeaf. If you like the theme, edit your _vimrc (Win) or .vimrc (Un*x) and add this line:\r\n    colorscheme AutumnLeaf\r\nthus making this scheme your default one.\r\n","5":"A) UNIX\/Linux: Download to ~\/.vim\/colors\/.\r\nB) Win32: Download to <vim directory>\/vimfiles\/colors\/.\r\n\r\nOpen Vim, type :colors AutumnLeaf. If you like the theme, edit your _vimrc (Win) or .vimrc (Un*x) and add this line:\r\n    colorscheme AutumnLeaf\r\nthus making this scheme your default one.\r\n","first_name":"Miikka-Markus","6":"Miikka-Markus","last_name":"Leskinen","7":"Leskinen","releases":[{"0":"1107","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"autumnleaf.vim","4":"autumnleaf.vim","src_id":"3553","5":"3553","creation_date":"1097996990","6":"1097996990"}]},"1106":{"script_id":"1106","0":"1106","script_name":"java_src_link.vim","1":"java_src_link.vim","script_type":"ftplugin","2":"ftplugin","summary":"effective searching of src files for children, impls, tests, return values, args","3":"effective searching of src files for children, impls, tests, return values, args","description":"\"   Filetype plugin for java that allows you to jump to\r\n\"   another java src file by searching your configured\r\n\"   src path for the class name under the cursor.\r\n\"\r\n\"   For a given class name, supports finding children of it, implementations\r\n\"   of it, methods that return it, methods that take it as an argument, test\r\n\"   cases for it, or all references of it.\r\n\"\r\n\" Platform:\r\n\"   This plugin uses the system find and grep commands extensively,\r\n\"   so if you are having issues, it's probably due to incompatibility\r\n\"   with one of those.  You can take a look at s:find_cmd, s:content_grep,\r\n\"   and s:*_regex variables to see if they can be modified to suit your\r\n\"   system.\r\n\"\r\n\"   If you find that you do have to modify any of these, feel free to\r\n\"   send me your changes, and I will see if they are compatable or make\r\n\"   alternate configurations available for users to choose from.\r\n\"\r\n\"   All my testing was done with\r\n\"     GNU find version 4.1.20\r\n\"     GNU grep version 2.5.1\r\n\"\r\n\"   Linux:\r\n\"     All testing has been done on linux so various flavors of linux\r\n\"     should be supported (as well as other *nix systems).\r\n\"\r\n\"   Windows:\r\n\"     Works in conjunction with cygwin_utils.vim plugin.\r\n\"     Make sure to read the Description comments in cygwin_utils.vim for\r\n\"     configuration instructions and other notes.\r\n\"\r\n\"     Note: I've found that the 'find' command runs considerably\r\n\"     slower on Windows enviroments.  So if you have serveral\r\n\"     paths in you g:JavaSrcPaths variable, then searching may\r\n\"     be a bit slow.\r\n\"\r\n\" Usage:\r\n\"   When editing a java file the following commands are created\r\n\"    :FindSrc\r\n\"    :FindImpl\r\n\"    :FindChildren\r\n\"    :ContextualFindSrc\r\n\"    :FindTest\r\n\"    :FindArgument\r\n\"    :FindReturned\r\n\"    :FindReferenced\r\n\"\r\n\"   FindSrc: will search for the src file for the class name under the\r\n\"   cursor and execute the configured g:JavaSrcCmd on it (unless\r\n\"   g:JavaSrcUseGrep is set to 1), which could do any number of\r\n\"   things such as edit, argadd, split, etc.\r\n\"\r\n\"   FindImpl: behaves just like FindSrc, except instead of searching for\r\n\"   the class name under the cursor, it searches for classes that\r\n\"   implement that class.\r\n\"\r\n\"   FindChildren: behaves just like FindSrc, except instead of searching\r\n\"   for the class name under the cursor, it searches for classes that\r\n\"   extend that class.\r\n\"\r\n\"   ContextualFindSrc: is a convenience command that decides which of the\r\n\"   above commands to execute (FindSrc, FindImpl, or FindChildren) based\r\n\"   on your position in the file.\r\n\"   - If you are on the class declaration line (public class Foo), then\r\n\"     it will execute FindChildren.\r\n\"   - If you are on the interface declaration line (public interface Foo),\r\n\"     then it will execute FindImpl.\r\n\"   - Any where else in the file, FindSrc will be executed.\r\n\"\r\n\"   FindTest: behaves like FindSrc, except instead of searching\r\n\"   for the class name under the cursor, it searches for the test\r\n\"   case src file for the class.\r\n\"     This command assumes that test case src files follow the junit\r\n\"     naming conventions of \"<classname>Test.java\" where the <classname>\r\n\"     is the name of the class under the cursor.\r\n\"\r\n\"   FindArgument: behaves like FindSrc, except instead of searching\r\n\"   for the class name under the cursor, it searches for all src files\r\n\"   that have a method that takes as an argument, that class.\r\n\"\r\n\"   FindReturned: behaves like FindSrc, except instead of searching\r\n\"   for the class name under the cursor, it searches for all src files\r\n\"   that have a method that returns that class.\r\n\"\r\n\"   FindReferenced: behaves like FindSrc, except instead of searching\r\n\"   for the class name under the cursor, it searches for all src files\r\n\"   that reference that class.\r\n\"\r\n\"   Note: All of the above commands (with the exception of ContextualFindSrc)\r\n\"   can also be invoked with an argument.\r\n\"     Ex.\r\n\"       FindSrc org.bar.Foo\r\n\"   This will invoke the command so it searches for the class name provided\r\n\"   rather than the one under the cursor.  You may use fully qualified\r\n\"   (org.bar.Foo) or un-qualified (Foo) class names.\r\n\"\r\n\"   Note: All of these find commands will attempt to filter out\r\n\"   results that reference a different class that has the same\r\n\"   class name as the one to search for.  It does this by attempting\r\n\"   to locate the package name of the class to search for.\r\n\"\r\n\"     For example: If you have two classes with the name Foo\r\n\"     one in com.bar.Foo and the other in com.bar.baz.Foo, and you\r\n\"     start a search for the class Foo, then this plugin will attempt\r\n\"     to determine which Foo you are searching for.\r\n\"\r\n\"     If you are editing one of the Foo classes, and you initiated the\r\n\"     search with the cursor on the class declaration (public class Foo),\r\n\"     then the package (package com.bar;)  declaration of the file will\r\n\"     be used to narrow the results to the correct Foo class.\r\n\"\r\n\"     If you are in another file (say Bar.java) and you start a search\r\n\"     for Foo, then the plugin will look to see if you used the fully\r\n\"     qualified class name (com.bar.Foo) or if you imported the class\r\n\"     (import com.bar.Foo;).  If you did either then the package name\r\n\"     will be grabbed from there.  If you have done neither, then the\r\n\"     plugin will return results for all Foo occurances regardless\r\n\"     of package name.\r\n\"\r\n\"     So the moral of the story is, that if you want accurate results\r\n\"     you should get in the habit of importing each class seperately\r\n\"     and avoiding the * imports (import com.bar.*;).  This is a good\r\n\"     habit anyways, that makes your code easier to read, navigate, and\r\n\"     understand by others.\r\n\"\r\n\" Configuration:\r\n\"   The following describes the global variables you can set in\r\n\"   your vimrc to change the behavior of this plugin.\r\n\"\r\n\"     g:JavaSrcPaths\r\n\"       No default.  Use this variable to set a comma seperated list\r\n\"       of the paths you wish to have searched. Each path should be\r\n\"       the parent directory of where your package structure begins.\r\n\"       So for \/a\/path\/src\/java\/org\/acme\/, assumming packages begin\r\n\"       as org, you would use \/a\/path\/src\/java as the path to search.\r\n\"\r\n\"       Ex.  let g:JavaSrcPaths=\r\n\"              \\ \"\/a\/path\/src\/java,\" .\r\n\"              \\ \"\/another\/path\/src\/java\"\r\n\"\r\n\"     g:JavaSrcTestPaths\r\n\"       No default. Same as g:JavaSrcPaths but used by FindTest to\r\n\"       locate unit testing src files.\r\n\"\r\n\"     g:JavaSrcShowResults\r\n\"       Defaults to 0.  When set to 1, the Find commands will open\r\n\"       a small preview window when multiple results have been found.\r\n\"       In that window you can hit <enter> on the file you wish\r\n\"       to open or use 'A' to load all results into the arg list.\r\n\"\r\n\"       Ex. let g:JavaSrcShowResults=1\r\n\"\r\n\"     g:JavaSrcUseGrep\r\n\"       Defaults to 1.  When set to 1, the Find commands will use vim's\r\n\"       :grep command to grep the results so that results can be\r\n\"       navigated through using the quickfix command :cnext :cprev\r\n\"       :copen, etc.\r\n\"       Note: When g:JavaSrcShowResults is set, then grep is not used\r\n\"             regardless of whether g:JavaSrcUseGrep is set or not.\r\n\"\r\n\"       Ex. let g:JavaSrcUseGrep=1\r\n\"\r\n\"       Use\r\n\"         :help quickfix.txt\r\n\"       to get more info on how grep and the quickfix paradigm works.\r\n\"\r\n\"     Note: When both g:JavaSrcShowResults and g:JavaSrcUseGrep are set\r\n\"           to 0, then the g:JavaSrcCmd is executed on all files found\r\n\"           with no preview or quickfix window.\r\n\"\r\n\"     g:JavaSrcCwindow\r\n\"       Defaults to 1.  Used to determine whether or not to execute\r\n\"       :cwindow to open the grep results after searching.  If set\r\n\"       to 1, the window will be opened after every Find command.\r\n\"       If set to 0, the window will remain closed and you can open\r\n\"       it manually.\r\n\"       Note:  Only used when g:JavaSrcUseGrep is set to 1 and\r\n\"              g:JavaSrcShowResults is set to 0.\r\n\"\r\n\"       Ex. let g:JavaSrcCwindow=1\r\n\"\r\n\"     g:JavaSrcCmd\r\n\"       Defaults to \"split <file>\".  Use this variable to set the\r\n\"       command you wish to be invoked when using :Find* commands.\r\n\"       The \"<file>\" will be replace with the file to open.\r\n\"       Note: When g:JavaSrcShowResults is set to 0 and\r\n\"             g:JavaSrcUseGrep is set to 1, this variable is not\r\n\"             used.  Instead the quickfix commands are used.\r\n\"\r\n\"       Ex. let g:JavaSrcCmd=\"topleft split <file>\"\r\n\"       Ex. let g:JavaSrcCmd=\"argedit <file>\"\r\n\"       Ex. let g:JavaSrcCmd=\"call g:MyOpenFile(<file>)\"\r\n\"\r\n\" Command Mapping:\r\n\"   You may find it easier to map a command to something more convenient.\r\n\"   For example, here is my mapping that allows me to simply hit\r\n\"   <enter> on a class name to have it search for results based on the\r\n\"   context (as described above).\r\n\"\r\n\"     autocmd FileType java map <silent> <buffer> <cr> :ContextualFindSrc<cr>\r\n\"\r\n\" Limitations:\r\n\"   - FindChildren and FindImpl are limited to examining class names\r\n\"     that follow \"extends\" | \"implements\" on the same line.  So src files\r\n\"     that put each class on it's own line or wrap long extends \/ implements\r\n\"     statements may not be found.\r\n\"     This is a limitation of grep, which is used to find the files.\r\n\"     This could be solved by further examining the contents of src files\r\n\"     but would have a big impact on performance.\r\n\"   - FindReturned only searches for methods with \"public\" | \"private\" |\r\n\"     \"protected\" so as not to grab too many files.  Also the scope identifier\r\n\"     must appear on the same line as the class name.\r\n\"     As with the limitation on FindChildren and FileImpl, this is due to\r\n\"     grep examining the files one line at a time, which prevents examining\r\n\"     other lines to determine any sort of context.\r\n\"\r\n\" Todo:\r\n\"   - Extend beyond class based searching and add method and field based\r\n\"     searches (fields should be easy, methods could be hard to get reliable\r\n\"     results).\r\n","4":"\"   Filetype plugin for java that allows you to jump to\r\n\"   another java src file by searching your configured\r\n\"   src path for the class name under the cursor.\r\n\"\r\n\"   For a given class name, supports finding children of it, implementations\r\n\"   of it, methods that return it, methods that take it as an argument, test\r\n\"   cases for it, or all references of it.\r\n\"\r\n\" Platform:\r\n\"   This plugin uses the system find and grep commands extensively,\r\n\"   so if you are having issues, it's probably due to incompatibility\r\n\"   with one of those.  You can take a look at s:find_cmd, s:content_grep,\r\n\"   and s:*_regex variables to see if they can be modified to suit your\r\n\"   system.\r\n\"\r\n\"   If you find that you do have to modify any of these, feel free to\r\n\"   send me your changes, and I will see if they are compatable or make\r\n\"   alternate configurations available for users to choose from.\r\n\"\r\n\"   All my testing was done with\r\n\"     GNU find version 4.1.20\r\n\"     GNU grep version 2.5.1\r\n\"\r\n\"   Linux:\r\n\"     All testing has been done on linux so various flavors of linux\r\n\"     should be supported (as well as other *nix systems).\r\n\"\r\n\"   Windows:\r\n\"     Works in conjunction with cygwin_utils.vim plugin.\r\n\"     Make sure to read the Description comments in cygwin_utils.vim for\r\n\"     configuration instructions and other notes.\r\n\"\r\n\"     Note: I've found that the 'find' command runs considerably\r\n\"     slower on Windows enviroments.  So if you have serveral\r\n\"     paths in you g:JavaSrcPaths variable, then searching may\r\n\"     be a bit slow.\r\n\"\r\n\" Usage:\r\n\"   When editing a java file the following commands are created\r\n\"    :FindSrc\r\n\"    :FindImpl\r\n\"    :FindChildren\r\n\"    :ContextualFindSrc\r\n\"    :FindTest\r\n\"    :FindArgument\r\n\"    :FindReturned\r\n\"    :FindReferenced\r\n\"\r\n\"   FindSrc: will search for the src file for the class name under the\r\n\"   cursor and execute the configured g:JavaSrcCmd on it (unless\r\n\"   g:JavaSrcUseGrep is set to 1), which could do any number of\r\n\"   things such as edit, argadd, split, etc.\r\n\"\r\n\"   FindImpl: behaves just like FindSrc, except instead of searching for\r\n\"   the class name under the cursor, it searches for classes that\r\n\"   implement that class.\r\n\"\r\n\"   FindChildren: behaves just like FindSrc, except instead of searching\r\n\"   for the class name under the cursor, it searches for classes that\r\n\"   extend that class.\r\n\"\r\n\"   ContextualFindSrc: is a convenience command that decides which of the\r\n\"   above commands to execute (FindSrc, FindImpl, or FindChildren) based\r\n\"   on your position in the file.\r\n\"   - If you are on the class declaration line (public class Foo), then\r\n\"     it will execute FindChildren.\r\n\"   - If you are on the interface declaration line (public interface Foo),\r\n\"     then it will execute FindImpl.\r\n\"   - Any where else in the file, FindSrc will be executed.\r\n\"\r\n\"   FindTest: behaves like FindSrc, except instead of searching\r\n\"   for the class name under the cursor, it searches for the test\r\n\"   case src file for the class.\r\n\"     This command assumes that test case src files follow the junit\r\n\"     naming conventions of \"<classname>Test.java\" where the <classname>\r\n\"     is the name of the class under the cursor.\r\n\"\r\n\"   FindArgument: behaves like FindSrc, except instead of searching\r\n\"   for the class name under the cursor, it searches for all src files\r\n\"   that have a method that takes as an argument, that class.\r\n\"\r\n\"   FindReturned: behaves like FindSrc, except instead of searching\r\n\"   for the class name under the cursor, it searches for all src files\r\n\"   that have a method that returns that class.\r\n\"\r\n\"   FindReferenced: behaves like FindSrc, except instead of searching\r\n\"   for the class name under the cursor, it searches for all src files\r\n\"   that reference that class.\r\n\"\r\n\"   Note: All of the above commands (with the exception of ContextualFindSrc)\r\n\"   can also be invoked with an argument.\r\n\"     Ex.\r\n\"       FindSrc org.bar.Foo\r\n\"   This will invoke the command so it searches for the class name provided\r\n\"   rather than the one under the cursor.  You may use fully qualified\r\n\"   (org.bar.Foo) or un-qualified (Foo) class names.\r\n\"\r\n\"   Note: All of these find commands will attempt to filter out\r\n\"   results that reference a different class that has the same\r\n\"   class name as the one to search for.  It does this by attempting\r\n\"   to locate the package name of the class to search for.\r\n\"\r\n\"     For example: If you have two classes with the name Foo\r\n\"     one in com.bar.Foo and the other in com.bar.baz.Foo, and you\r\n\"     start a search for the class Foo, then this plugin will attempt\r\n\"     to determine which Foo you are searching for.\r\n\"\r\n\"     If you are editing one of the Foo classes, and you initiated the\r\n\"     search with the cursor on the class declaration (public class Foo),\r\n\"     then the package (package com.bar;)  declaration of the file will\r\n\"     be used to narrow the results to the correct Foo class.\r\n\"\r\n\"     If you are in another file (say Bar.java) and you start a search\r\n\"     for Foo, then the plugin will look to see if you used the fully\r\n\"     qualified class name (com.bar.Foo) or if you imported the class\r\n\"     (import com.bar.Foo;).  If you did either then the package name\r\n\"     will be grabbed from there.  If you have done neither, then the\r\n\"     plugin will return results for all Foo occurances regardless\r\n\"     of package name.\r\n\"\r\n\"     So the moral of the story is, that if you want accurate results\r\n\"     you should get in the habit of importing each class seperately\r\n\"     and avoiding the * imports (import com.bar.*;).  This is a good\r\n\"     habit anyways, that makes your code easier to read, navigate, and\r\n\"     understand by others.\r\n\"\r\n\" Configuration:\r\n\"   The following describes the global variables you can set in\r\n\"   your vimrc to change the behavior of this plugin.\r\n\"\r\n\"     g:JavaSrcPaths\r\n\"       No default.  Use this variable to set a comma seperated list\r\n\"       of the paths you wish to have searched. Each path should be\r\n\"       the parent directory of where your package structure begins.\r\n\"       So for \/a\/path\/src\/java\/org\/acme\/, assumming packages begin\r\n\"       as org, you would use \/a\/path\/src\/java as the path to search.\r\n\"\r\n\"       Ex.  let g:JavaSrcPaths=\r\n\"              \\ \"\/a\/path\/src\/java,\" .\r\n\"              \\ \"\/another\/path\/src\/java\"\r\n\"\r\n\"     g:JavaSrcTestPaths\r\n\"       No default. Same as g:JavaSrcPaths but used by FindTest to\r\n\"       locate unit testing src files.\r\n\"\r\n\"     g:JavaSrcShowResults\r\n\"       Defaults to 0.  When set to 1, the Find commands will open\r\n\"       a small preview window when multiple results have been found.\r\n\"       In that window you can hit <enter> on the file you wish\r\n\"       to open or use 'A' to load all results into the arg list.\r\n\"\r\n\"       Ex. let g:JavaSrcShowResults=1\r\n\"\r\n\"     g:JavaSrcUseGrep\r\n\"       Defaults to 1.  When set to 1, the Find commands will use vim's\r\n\"       :grep command to grep the results so that results can be\r\n\"       navigated through using the quickfix command :cnext :cprev\r\n\"       :copen, etc.\r\n\"       Note: When g:JavaSrcShowResults is set, then grep is not used\r\n\"             regardless of whether g:JavaSrcUseGrep is set or not.\r\n\"\r\n\"       Ex. let g:JavaSrcUseGrep=1\r\n\"\r\n\"       Use\r\n\"         :help quickfix.txt\r\n\"       to get more info on how grep and the quickfix paradigm works.\r\n\"\r\n\"     Note: When both g:JavaSrcShowResults and g:JavaSrcUseGrep are set\r\n\"           to 0, then the g:JavaSrcCmd is executed on all files found\r\n\"           with no preview or quickfix window.\r\n\"\r\n\"     g:JavaSrcCwindow\r\n\"       Defaults to 1.  Used to determine whether or not to execute\r\n\"       :cwindow to open the grep results after searching.  If set\r\n\"       to 1, the window will be opened after every Find command.\r\n\"       If set to 0, the window will remain closed and you can open\r\n\"       it manually.\r\n\"       Note:  Only used when g:JavaSrcUseGrep is set to 1 and\r\n\"              g:JavaSrcShowResults is set to 0.\r\n\"\r\n\"       Ex. let g:JavaSrcCwindow=1\r\n\"\r\n\"     g:JavaSrcCmd\r\n\"       Defaults to \"split <file>\".  Use this variable to set the\r\n\"       command you wish to be invoked when using :Find* commands.\r\n\"       The \"<file>\" will be replace with the file to open.\r\n\"       Note: When g:JavaSrcShowResults is set to 0 and\r\n\"             g:JavaSrcUseGrep is set to 1, this variable is not\r\n\"             used.  Instead the quickfix commands are used.\r\n\"\r\n\"       Ex. let g:JavaSrcCmd=\"topleft split <file>\"\r\n\"       Ex. let g:JavaSrcCmd=\"argedit <file>\"\r\n\"       Ex. let g:JavaSrcCmd=\"call g:MyOpenFile(<file>)\"\r\n\"\r\n\" Command Mapping:\r\n\"   You may find it easier to map a command to something more convenient.\r\n\"   For example, here is my mapping that allows me to simply hit\r\n\"   <enter> on a class name to have it search for results based on the\r\n\"   context (as described above).\r\n\"\r\n\"     autocmd FileType java map <silent> <buffer> <cr> :ContextualFindSrc<cr>\r\n\"\r\n\" Limitations:\r\n\"   - FindChildren and FindImpl are limited to examining class names\r\n\"     that follow \"extends\" | \"implements\" on the same line.  So src files\r\n\"     that put each class on it's own line or wrap long extends \/ implements\r\n\"     statements may not be found.\r\n\"     This is a limitation of grep, which is used to find the files.\r\n\"     This could be solved by further examining the contents of src files\r\n\"     but would have a big impact on performance.\r\n\"   - FindReturned only searches for methods with \"public\" | \"private\" |\r\n\"     \"protected\" so as not to grab too many files.  Also the scope identifier\r\n\"     must appear on the same line as the class name.\r\n\"     As with the limitation on FindChildren and FileImpl, this is due to\r\n\"     grep examining the files one line at a time, which prevents examining\r\n\"     other lines to determine any sort of context.\r\n\"\r\n\" Todo:\r\n\"   - Extend beyond class based searching and add method and field based\r\n\"     searches (fields should be easy, methods could be hard to get reliable\r\n\"     results).\r\n","install_details":"Put java_src_link.vim into your ftplugin directory.\r\n\r\nWindows users will need cygwin_utils.vim (vimscript #1150)","5":"Put java_src_link.vim into your ftplugin directory.\r\n\r\nWindows users will need cygwin_utils.vim (vimscript #1150)","first_name":"Eric","6":"Eric","last_name":"Van Dewoestine","7":"Van Dewoestine","releases":[{"0":"1106","vim_version":"6.0","1":"6.0","script_version":"0.4","2":"0.4","version_comment":"- Now supported on Windows platform.","3":"- Now supported on Windows platform.","package":"java_src_link.vim","4":"java_src_link.vim","src_id":"3685","5":"3685","creation_date":"1102259253","6":"1102259253"}]},"1105":{"script_id":"1105","0":"1105","script_name":"ptu","1":"ptu","script_type":"syntax","2":"syntax","summary":"This Script is for the editing Test Script of Rational Test Real Time","3":"This Script is for the editing Test Script of Rational Test Real Time","description":"This Script is for the editing Test Script of Rational Test Real Time. The basic keywords are taken care of and the colorscheme is also applicable to the Native code written in \"#\" which is not in the default editor.\r\nThe script is minimal and I have plans to make it better. Suggestions invited.\r\n","4":"This Script is for the editing Test Script of Rational Test Real Time. The basic keywords are taken care of and the colorscheme is also applicable to the Native code written in \"#\" which is not in the default editor.\r\nThe script is minimal and I have plans to make it better. Suggestions invited.\r\n","install_details":"Refer to general Installation of syntax files.","5":"Refer to general Installation of syntax files.","first_name":"apurva","6":"apurva","last_name":"shukla","7":"shukla","releases":[{"0":"1105","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"ptu.vim","4":"ptu.vim","src_id":"3540","5":"3540","creation_date":"1097564904","6":"1097564904"}]},"1104":{"script_id":"1104","0":"1104","script_name":"ACScope","1":"ACScope","script_type":"utility","2":"utility","summary":"Another CScope frontend","3":"Another CScope frontend","description":"A CScope frontend provides having multiple query results around. It uses windows, so the results won't get away.\r\nFor usage see the comments in the script file.\r\n\r\nIt uses two windows, one for listing the queries done and\r\nanother for listing the result of the selected query.\r\nIt can be used parallel with the normal cscope frontend of\r\nvim because they use different settings and key bindings.\r\n","4":"A CScope frontend provides having multiple query results around. It uses windows, so the results won't get away.\r\nFor usage see the comments in the script file.\r\n\r\nIt uses two windows, one for listing the queries done and\r\nanother for listing the result of the selected query.\r\nIt can be used parallel with the normal cscope frontend of\r\nvim because they use different settings and key bindings.\r\n","install_details":"Copy it into your plugins directory (~\/.vim\/plugin)","5":"Copy it into your plugins directory (~\/.vim\/plugin)","first_name":"Gabor","6":"Gabor","last_name":"Fekete","7":"Fekete","releases":[{"0":"1104","vim_version":"6.0","1":"6.0","script_version":"0.2","2":"0.2","version_comment":"bugfix: store proper filename in the tagstack","3":"bugfix: store proper filename in the tagstack","package":"acscope.vim","4":"acscope.vim","src_id":"4227","5":"4227","creation_date":"1114931460","6":"1114931460"},{"0":"1104","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"acscope.vim","4":"acscope.vim","src_id":"3539","5":"3539","creation_date":"1097561001","6":"1097561001"}]},"1103":{"script_id":"1103","0":"1103","script_name":"VB.NET Indent","1":"VB.NET Indent","script_type":"indent","2":"indent","summary":"Indent for VB.NET (Visual Basic .NET)","3":"Indent for VB.NET (Visual Basic .NET)","description":"(silently) Modified from indent\/vb.vim\r\n\r\nThere may still be some bugs, I haven't tested all syntax...\r\n\r\nTODO:\r\n\r\n- Add support for multi-line \"If\" without \"Then\"","4":"(silently) Modified from indent\/vb.vim\r\n\r\nThere may still be some bugs, I haven't tested all syntax...\r\n\r\nTODO:\r\n\r\n- Add support for multi-line \"If\" without \"Then\"","install_details":"just copy it to vimfiles\/indent\/vbnet.vim\r\n\r\nthen add the following line to your _vimrc or .vimrc\r\n\r\nautocmd BufRead,BufNewFile *.vb setlocal filetype=vbnet\r\n","5":"just copy it to vimfiles\/indent\/vbnet.vim\r\n\r\nthen add the following line to your _vimrc or .vimrc\r\n\r\nautocmd BufRead,BufNewFile *.vb setlocal filetype=vbnet\r\n","first_name":"Aquila","6":"Aquila","last_name":"Deus","7":"Deus","releases":[{"0":"1103","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Support for .NET 2","3":"Support for .NET 2","package":"vbnet.vim","4":"vbnet.vim","src_id":"3702","5":"3702","creation_date":"1102890049","6":"1102890049"},{"0":"1103","vim_version":"6.0","1":"6.0","script_version":"0.9.6","2":"0.9.6","version_comment":"Fix If [multi-line cond] Then indent bug","3":"Fix If [multi-line cond] Then indent bug","package":"vbnet.vim","4":"vbnet.vim","src_id":"3609","5":"3609","creation_date":"1099772540","6":"1099772540"},{"0":"1103","vim_version":"6.0","1":"6.0","script_version":"0.9.5","2":"0.9.5","version_comment":"Fix two bugs in Try-Catch and in ReadOnly\/WriteOnly Property","3":"Fix two bugs in Try-Catch and in ReadOnly\/WriteOnly Property","package":"vbnet.vim","4":"vbnet.vim","src_id":"3606","5":"3606","creation_date":"1099607510","6":"1099607510"},{"0":"1103","vim_version":"6.0","1":"6.0","script_version":"0.9.4","2":"0.9.4","version_comment":"Attribute now works perfectly!","3":"Attribute now works perfectly!","package":"vbnet.vim","4":"vbnet.vim","src_id":"3600","5":"3600","creation_date":"1099501431","6":"1099501431"},{"0":"1103","vim_version":"6.0","1":"6.0","script_version":"0.9.3","2":"0.9.3","version_comment":"Support single-lined attribute","3":"Support single-lined attribute","package":"vbnet.vim","4":"vbnet.vim","src_id":"3597","5":"3597","creation_date":"1099332104","6":"1099332104"},{"0":"1103","vim_version":"6.0","1":"6.0","script_version":"0.9.2","2":"0.9.2","version_comment":"Support \"_\" at the end of line","3":"Support \"_\" at the end of line","package":"vbnet.vim","4":"vbnet.vim","src_id":"3571","5":"3571","creation_date":"1098652146","6":"1098652146"},{"0":"1103","vim_version":"6.0","1":"6.0","script_version":"0.9.1","2":"0.9.1","version_comment":"- Fix bugs in class\/method\/property declaration\r\n- Add # directive support","3":"- Fix bugs in class\/method\/property declaration\r\n- Add # directive support","package":"vbnet.vim","4":"vbnet.vim","src_id":"3550","5":"3550","creation_date":"1097982588","6":"1097982588"},{"0":"1103","vim_version":"6.0","1":"6.0","script_version":"0.9","2":"0.9","version_comment":"Initial upload","3":"Initial upload","package":"vbnet.vim","4":"vbnet.vim","src_id":"3538","5":"3538","creation_date":"1097556396","6":"1097556396"}]},"1102":{"script_id":"1102","0":"1102","script_name":"VB.NET Syntax","1":"VB.NET Syntax","script_type":"syntax","2":"syntax","summary":"Syntax highlightening for VB.NET (Visual Basic .NET)","3":"Syntax highlightening for VB.NET (Visual Basic .NET)","description":"It's modified from the syntax\/vb.vim. All VB.NET (Visual Basic .NET) keywords have been added.\r\n","4":"It's modified from the syntax\/vb.vim. All VB.NET (Visual Basic .NET) keywords have been added.\r\n","install_details":"just copy it to vimfiles\/syntax\/vbnet.vim\r\n\r\nthen add the following line to your _vimrc or .vimrc\r\n\r\nautocmd BufRead,BufNewFile *.vb setlocal filetype=vbnet\r\n\r\n\r\n","5":"just copy it to vimfiles\/syntax\/vbnet.vim\r\n\r\nthen add the following line to your _vimrc or .vimrc\r\n\r\nautocmd BufRead,BufNewFile *.vb setlocal filetype=vbnet\r\n\r\n\r\n","first_name":"Aquila","6":"Aquila","last_name":"Deus","7":"Deus","releases":[{"0":"1102","vim_version":"6.0","1":"6.0","script_version":"1.3","2":"1.3","version_comment":"support for .NET 2.0 and matchit","3":"support for .NET 2.0 and matchit","package":"vbnet.vim","4":"vbnet.vim","src_id":"3701","5":"3701","creation_date":"1102890009","6":"1102890009"},{"0":"1102","vim_version":"6.0","1":"6.0","script_version":"1.2","2":"1.2","version_comment":"(i forgot)","3":"(i forgot)","package":"vbnet.vim","4":"vbnet.vim","src_id":"3596","5":"3596","creation_date":"1099331967","6":"1099331967"},{"0":"1102","vim_version":"6.0","1":"6.0","script_version":"1.1","2":"1.1","version_comment":"Add support for # directives.","3":"Add support for # directives.","package":"vbnet.vim","4":"vbnet.vim","src_id":"3551","5":"3551","creation_date":"1097982801","6":"1097982801"},{"0":"1102","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"vbnet.vim","4":"vbnet.vim","src_id":"3537","5":"3537","creation_date":"1097556150","6":"1097556150"}]},"1101":{"script_id":"1101","0":"1101","script_name":"hamster.vim","1":"hamster.vim","script_type":"ftplugin","2":"ftplugin","summary":"Hamster (Classic | Playground) filetype plugin","3":"Hamster (Classic | Playground) filetype plugin","description":"Hamster (Classic | Playground)\r\n\r\nHamster is a local server for news and mail. It's a windows-32-bit-program. It allows the use of multiple news- and mailserver and combines them to one mail- and newsserver for the news\/mail-client. It load faster than a normal newsreader because many threads can run simultaneous. It contains scorefile for news and mail, a build-in script language, the GUI allows translation to other languages, it can be used in a network and that's not all features...\r\nhttp:\/\/www.tglsoft.de\/misc\/hamster_en.htm\r\nhttp:\/\/www.elbiah.de\/hamster\/index.htm\r\n\r\nThe filetype plugin defines various behaviours and variables.\r\nAdds matchit.vim support.\r\nCreates standard motion mappings (i.e. [[,]],[],][,...).\r\nCase sensitivity.\r\nComment support.","4":"Hamster (Classic | Playground)\r\n\r\nHamster is a local server for news and mail. It's a windows-32-bit-program. It allows the use of multiple news- and mailserver and combines them to one mail- and newsserver for the news\/mail-client. It load faster than a normal newsreader because many threads can run simultaneous. It contains scorefile for news and mail, a build-in script language, the GUI allows translation to other languages, it can be used in a network and that's not all features...\r\nhttp:\/\/www.tglsoft.de\/misc\/hamster_en.htm\r\nhttp:\/\/www.elbiah.de\/hamster\/index.htm\r\n\r\nThe filetype plugin defines various behaviours and variables.\r\nAdds matchit.vim support.\r\nCreates standard motion mappings (i.e. [[,]],[],][,...).\r\nCase sensitivity.\r\nComment support.","install_details":"Copy hamster.vim into your .vim\/ftplugin (Unix) or vimfiles\/ftplugin (Windows) directory.\r\n\r\nEdit your .vim|vimfiles\/filetype.vim and add the following entry:\r\n\r\n\" Hamster Classic | Playground files\r\n\" NNTP and Mail local server\r\nau BufNewFile,BufRead *.hsc,*.hsm setfiletype hamster\r\n ","5":"Copy hamster.vim into your .vim\/ftplugin (Unix) or vimfiles\/ftplugin (Windows) directory.\r\n\r\nEdit your .vim|vimfiles\/filetype.vim and add the following entry:\r\n\r\n\" Hamster Classic | Playground files\r\n\" NNTP and Mail local server\r\nau BufNewFile,BufRead *.hsc,*.hsm setfiletype hamster\r\n ","first_name":"David","6":"David","last_name":"Fishburn","7":"Fishburn","releases":[{"0":"1101","vim_version":"6.0","1":"6.0","script_version":"2.0.6.0","2":"2.0.6.0","version_comment":"Initial upload","3":"Initial upload","package":"hamster.vim","4":"hamster.vim","src_id":"3534","5":"3534","creation_date":"1097239642","6":"1097239642"}]},"1100":{"script_id":"1100","0":"1100","script_name":"clearsilver","1":"clearsilver","script_type":"syntax","2":"syntax","summary":"syntax files for *.cs and *.hdf","3":"syntax files for *.cs and *.hdf","description":"These are syntax files for managing clearsilver templates (see http:\/\/clearsilver.net).  cs.vim will add formatting to <?cs ... ?> embedded in html syntax (it depends on runtime! syntax\/html.vim).  hdf.vim is syntax highlighting for Hierarchical Data Format (HDF) files.\r\n\r\ncs.vim conflicts with the C# .cs extention.  So if you are also using vim to edit C# files you will have to... figure it out.","4":"These are syntax files for managing clearsilver templates (see http:\/\/clearsilver.net).  cs.vim will add formatting to <?cs ... ?> embedded in html syntax (it depends on runtime! syntax\/html.vim).  hdf.vim is syntax highlighting for Hierarchical Data Format (HDF) files.\r\n\r\ncs.vim conflicts with the C# .cs extention.  So if you are also using vim to edit C# files you will have to... figure it out.","install_details":"cp clearsilver.vim ~\/.vim\r\ncd ~\/.vim\r\ntar -xf clearsilver.vim\r\n\r\nthis will put two files in ~\/.vim\/syntax\r\n\r\nYou also need to update ~\/.vim\/filetype.vim with:\r\n\r\nif exists(\"did_load_myfiletypes\")\r\nfinish\r\nendif\r\nlet did_load_myfiletypes= 1\r\n\r\naugroup filetypedetect\r\n au BufNewFile,BufReadPost *.hdf setf hdf\r\n au BufNewFile,BufReadPost *.cs setf cs\r\naugroup END","5":"cp clearsilver.vim ~\/.vim\r\ncd ~\/.vim\r\ntar -xf clearsilver.vim\r\n\r\nthis will put two files in ~\/.vim\/syntax\r\n\r\nYou also need to update ~\/.vim\/filetype.vim with:\r\n\r\nif exists(\"did_load_myfiletypes\")\r\nfinish\r\nendif\r\nlet did_load_myfiletypes= 1\r\n\r\naugroup filetypedetect\r\n au BufNewFile,BufReadPost *.hdf setf hdf\r\n au BufNewFile,BufReadPost *.cs setf cs\r\naugroup END","first_name":"culley","6":"culley","last_name":"harrelson","7":"harrelson","releases":[{"0":"1100","vim_version":"6.0","1":"6.0","script_version":".01","2":".01","version_comment":"Initial upload","3":"Initial upload","package":"clearsilver.tar","4":"clearsilver.tar","src_id":"3532","5":"3532","creation_date":"1097230562","6":"1097230562"}]},"1099":{"script_id":"1099","0":"1099","script_name":"hamster.vim","1":"hamster.vim","script_type":"indent","2":"indent","summary":"Hamster (Classic | Playground) indent file","3":"Hamster (Classic | Playground) indent file","description":"Hamster (Classic | Playground)\r\n\r\nHamster is a local server for news and mail. It's a windows-32-bit-program. It allows the use of multiple news- and mailserver and combines them to one mail- and newsserver for the news\/mail-client. It load faster than a normal newsreader because many threads can run simultaneous. It contains scorefile for news and mail, a build-in script language, the GUI allows translation to other languages, it can be used in a network and that's not all features...\r\nhttp:\/\/www.tglsoft.de\/misc\/hamster_en.htm\r\nhttp:\/\/www.elbiah.de\/hamster\/index.htm\r\n\r\nThis is an indent file for the builtin scripting language. ","4":"Hamster (Classic | Playground)\r\n\r\nHamster is a local server for news and mail. It's a windows-32-bit-program. It allows the use of multiple news- and mailserver and combines them to one mail- and newsserver for the news\/mail-client. It load faster than a normal newsreader because many threads can run simultaneous. It contains scorefile for news and mail, a build-in script language, the GUI allows translation to other languages, it can be used in a network and that's not all features...\r\nhttp:\/\/www.tglsoft.de\/misc\/hamster_en.htm\r\nhttp:\/\/www.elbiah.de\/hamster\/index.htm\r\n\r\nThis is an indent file for the builtin scripting language. ","install_details":"Copy hamster.vim into your .vim\/indent (Unix) or vimfiles\/indent (Windows) directory.\r\n\r\nEdit your .vim|vimfiles\/filetype.vim and add the following entry:\r\n\r\n\" Hamster Classic | Playground files\r\n\" NNTP and Mail local server\r\nau BufNewFile,BufRead *.hsc,*.hsm setfiletype hamster ","5":"Copy hamster.vim into your .vim\/indent (Unix) or vimfiles\/indent (Windows) directory.\r\n\r\nEdit your .vim|vimfiles\/filetype.vim and add the following entry:\r\n\r\n\" Hamster Classic | Playground files\r\n\" NNTP and Mail local server\r\nau BufNewFile,BufRead *.hsc,*.hsm setfiletype hamster ","first_name":"David","6":"David","last_name":"Fishburn","7":"Fishburn","releases":[{"0":"1099","vim_version":"7.0","1":"7.0","script_version":"2.0.6.1","2":"2.0.6.1","version_comment":"Added b:undo_indent and cpo support.","3":"Added b:undo_indent and cpo support.","package":"hamster.vim","4":"hamster.vim","src_id":"27780","5":"27780","creation_date":"1634034361","6":"1634034361"},{"0":"1099","vim_version":"6.0","1":"6.0","script_version":"2.0.6.0","2":"2.0.6.0","version_comment":"Initial upload","3":"Initial upload","package":"hamster.vim","4":"hamster.vim","src_id":"3528","5":"3528","creation_date":"1097177349","6":"1097177349"}]},"1098":{"script_id":"1098","0":"1098","script_name":"hamster.vim","1":"hamster.vim","script_type":"syntax","2":"syntax","summary":"Hamster (Classic | Playground) syntax file","3":"Hamster (Classic | Playground) syntax file","description":"\r\nHamster (Classic | Playground) \r\n\r\nHamster is a local server for news and mail. It's a windows-32-bit-program. It allows the use of multiple news- and mailserver and combines them to one mail- and newsserver for the news\/mail-client. It load faster than a normal newsreader because many threads can run simultaneous. It contains scorefile for news and mail, a build-in script language, the GUI allows translation to other languages, it can be used in a network and that's not all features...\r\nhttp:\/\/www.tglsoft.de\/misc\/hamster_en.htm\r\nhttp:\/\/www.elbiah.de\/hamster\/index.htm\r\n\r\nThis is a syntax file for the builtin scripting language.\r\n","4":"\r\nHamster (Classic | Playground) \r\n\r\nHamster is a local server for news and mail. It's a windows-32-bit-program. It allows the use of multiple news- and mailserver and combines them to one mail- and newsserver for the news\/mail-client. It load faster than a normal newsreader because many threads can run simultaneous. It contains scorefile for news and mail, a build-in script language, the GUI allows translation to other languages, it can be used in a network and that's not all features...\r\nhttp:\/\/www.tglsoft.de\/misc\/hamster_en.htm\r\nhttp:\/\/www.elbiah.de\/hamster\/index.htm\r\n\r\nThis is a syntax file for the builtin scripting language.\r\n","install_details":"Copy hamster.vim into your .vim\/syntax (Unix) or vimfiles\/syntax (Windows) directory.\r\n\r\nEdit your .vim|vimfiles\/filetype.vim and add the following entry:\r\n\r\n\" Hamster Classic | Playground files \r\n\" NNTP and Mail local server\r\nau BufNewFile,BufRead *.hsc,*.hsm\t\tsetfiletype hamster\r\n","5":"Copy hamster.vim into your .vim\/syntax (Unix) or vimfiles\/syntax (Windows) directory.\r\n\r\nEdit your .vim|vimfiles\/filetype.vim and add the following entry:\r\n\r\n\" Hamster Classic | Playground files \r\n\" NNTP and Mail local server\r\nau BufNewFile,BufRead *.hsc,*.hsm\t\tsetfiletype hamster\r\n","first_name":"David","6":"David","last_name":"Fishburn","7":"Fishburn","releases":[{"0":"1098","vim_version":"6.0","1":"6.0","script_version":"2.0.6.0a","2":"2.0.6.0a","version_comment":"Minor tweak with the naming convention of the syntax items for a different plugin.  No functional change.","3":"Minor tweak with the naming convention of the syntax items for a different plugin.  No functional change.","package":"hamster.vim","4":"hamster.vim","src_id":"3781","5":"3781","creation_date":"1106075260","6":"1106075260"},{"0":"1098","vim_version":"6.0","1":"6.0","script_version":"2.0.6.0","2":"2.0.6.0","version_comment":"Initial upload","3":"Initial upload","package":"hamster.vim","4":"hamster.vim","src_id":"3527","5":"3527","creation_date":"1097177132","6":"1097177132"}]},"1097":{"script_id":"1097","0":"1097","script_name":"txt2tags menu","1":"txt2tags menu","script_type":"utility","2":"utility","summary":"gVim menu for txt2tags","3":"gVim menu for txt2tags","description":"gVIM script to support txt2tags (http:\/\/txt2tags.sourceforge.net\/)\r\n\r\nScreenshot: http:\/\/img.photobucket.com\/albums\/v106\/teivan\/Computador\/t2tmenu.png","4":"gVIM script to support txt2tags (http:\/\/txt2tags.sourceforge.net\/)\r\n\r\nScreenshot: http:\/\/img.photobucket.com\/albums\/v106\/teivan\/Computador\/t2tmenu.png","install_details":"Just copy the file t2t.vim to ~\/.vim\/plugin\/  =]\r\n\r\nRead more about txt2tags: http:\/\/txt2tags.sourceforge.net\/\r\n","5":"Just copy the file t2t.vim to ~\/.vim\/plugin\/  =]\r\n\r\nRead more about txt2tags: http:\/\/txt2tags.sourceforge.net\/\r\n","first_name":"Uthyr","6":"Uthyr","last_name":"Cordeiro","7":"Cordeiro","releases":[{"0":"1097","vim_version":"6.0","1":"6.0","script_version":"0.5","2":"0.5","version_comment":"Proproc -> PreProc\r\nThanks to Gustavo Roberto Rodrigues Gon\u00c3\u00a7alves for find the mistake :)","3":"Proproc -> PreProc\r\nThanks to Gustavo Roberto Rodrigues Gon\u00c3\u00a7alves for find the mistake :)","package":"t2t.vim","4":"t2t.vim","src_id":"4482","5":"4482","creation_date":"1123652948","6":"1123652948"},{"0":"1097","vim_version":"6.0","1":"6.0","script_version":"0.4","2":"0.4","version_comment":"New itens.","3":"New itens.","package":"t2t.vim","4":"t2t.vim","src_id":"4032","5":"4032","creation_date":"1110970303","6":"1110970303"},{"0":"1097","vim_version":"6.0","1":"6.0","script_version":"0.3","2":"0.3","version_comment":"add new options.","3":"add new options.","package":"t2t.vim","4":"t2t.vim","src_id":"3735","5":"3735","creation_date":"1104319604","6":"1104319604"},{"0":"1097","vim_version":"6.0","1":"6.0","script_version":"0.2","2":"0.2","version_comment":"* Removed ^M with dos2unix.\r\n* New imenu.","3":"* Removed ^M with dos2unix.\r\n* New imenu.","package":"t2t.vim","4":"t2t.vim","src_id":"3525","5":"3525","creation_date":"1097129615","6":"1097129615"},{"0":"1097","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"t2t.vim","4":"t2t.vim","src_id":"3522","5":"3522","creation_date":"1097103142","6":"1097103142"}]},"1096":{"script_id":"1096","0":"1096","script_name":"buffer-perlpython.pl","1":"buffer-perlpython.pl","script_type":"utility","2":"utility","summary":"run 'perl -cw' or 'pychecker' over the buffer, display results in a new window","3":"run 'perl -cw' or 'pychecker' over the buffer, display results in a new window","description":"Bindings to check or run perl\/python and display the results in a new window.\r\n\r\nWhen scripting:\r\n\r\nF1: perl -cw or pychecker over the current buffer, results in a new window\r\nF2: close the current window\r\nF3: perl\/python (actually run the script) the buffer, output in a new window","4":"Bindings to check or run perl\/python and display the results in a new window.\r\n\r\nWhen scripting:\r\n\r\nF1: perl -cw or pychecker over the current buffer, results in a new window\r\nF2: close the current window\r\nF3: perl\/python (actually run the script) the buffer, output in a new window","install_details":"Have this in my .vimrc, so using autocmds works for mapping F1\/F2\/F3. If you source it from anywhere other than your .vimrc you'll need to do so before opening the .py\/.pl\/.cgi file for the mappings to work.","5":"Have this in my .vimrc, so using autocmds works for mapping F1\/F2\/F3. If you source it from anywhere other than your .vimrc you'll need to do so before opening the .py\/.pl\/.cgi file for the mappings to work.","first_name":"Adam","6":"Adam","last_name":"Moore","7":"Moore","releases":[{"0":"1096","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"buffer-perlpython.vim","4":"buffer-perlpython.vim","src_id":"3510","5":"3510","creation_date":"1096655545","6":"1096655545"}]},"1095":{"script_id":"1095","0":"1095","script_name":"TabLaTeX","1":"TabLaTeX","script_type":"ftplugin","2":"ftplugin","summary":"A small and simple script for writing LaTeX documents","3":"A small and simple script for writing LaTeX documents","description":"TabLaTeX is a small and very simple Vim 6.x plugin that eases editing LaTeX documents. The script is focused on fast editing and not in completeness, so only the most used features of LaTeX are supported. You might find interesting that most commands are inspired in the tab-completion feature of the bash shell.\r\n\r\nHomepage: http:\/\/www.cavecanen.org\/latex\/tablatex\/","4":"TabLaTeX is a small and very simple Vim 6.x plugin that eases editing LaTeX documents. The script is focused on fast editing and not in completeness, so only the most used features of LaTeX are supported. You might find interesting that most commands are inspired in the tab-completion feature of the bash shell.\r\n\r\nHomepage: http:\/\/www.cavecanen.org\/latex\/tablatex\/","install_details":"Under *nix: run the install.sh file\r\nOther OSes: Copy the tablatex.vim file on the <vimdir>\/ftplugin\/tex directory","5":"Under *nix: run the install.sh file\r\nOther OSes: Copy the tablatex.vim file on the <vimdir>\/ftplugin\/tex directory","first_name":"Pedro","6":"Pedro","last_name":"Diaz","7":"Diaz","releases":[{"0":"1095","vim_version":"6.0","1":"6.0","script_version":"1.1","2":"1.1","version_comment":"Made the script less cheesy. Now all mappings and options are local to the buffer.\r\n\r\nInitial folding support (only for environments, for now)","3":"Made the script less cheesy. Now all mappings and options are local to the buffer.\r\n\r\nInitial folding support (only for environments, for now)","package":"tablatex1.1.tar.bz2","4":"tablatex1.1.tar.bz2","src_id":"3526","5":"3526","creation_date":"1097134177","6":"1097134177"},{"0":"1095","vim_version":"6.0","1":"6.0","script_version":"1","2":"1","version_comment":"Initial upload","3":"Initial upload","package":"tablatex1.tar.bz2","4":"tablatex1.tar.bz2","src_id":"3507","5":"3507","creation_date":"1096531665","6":"1096531665"}]},"1094":{"script_id":"1094","0":"1094","script_name":"cream-statusline-prototype","1":"cream-statusline-prototype","script_type":"utility","2":"utility","summary":"Display current function prototype in statusline","3":"Display current function prototype in statusline","description":"\r\nToggles the display of the current function prototype on the statusline with key <F8>. This is a basic illustration of how to write code to accomplish this...feel free to embellish!\r\n\r\n\r\nUSAGE\r\n\r\nBy default, the <F8> key will toggle the display of the current prototype in the statusline. The prototype is recalculated each time it is toggled ON.\r\n\r\n\r\nThis is one of many custom utilities and functions for gVim from the Cream project (http:\/\/cream.sourceforge.net), a configuration of Vim for those of us familiar with Apple and Windows software.\r\n\r\n","4":"\r\nToggles the display of the current function prototype on the statusline with key <F8>. This is a basic illustration of how to write code to accomplish this...feel free to embellish!\r\n\r\n\r\nUSAGE\r\n\r\nBy default, the <F8> key will toggle the display of the current prototype in the statusline. The prototype is recalculated each time it is toggled ON.\r\n\r\n\r\nThis is one of many custom utilities and functions for gVim from the Cream project (http:\/\/cream.sourceforge.net), a configuration of Vim for those of us familiar with Apple and Windows software.\r\n\r\n","install_details":"\r\nThis script is dependant on:\r\n\r\n* Exhuberant ctags (http:\/\/ctags.sf.net)\r\n* taglist.vim (http:\/\/vim.sourceforge.net\/scripts\/script.php?script_id=273, alternate: http:\/\/www.geocities.com\/yegappan\/taglist)\r\n\r\nJust install exuberant ctags and drop both taglist.vim and this file into your plugins directory. Then (re)start Vim and use key <F8> to toggle the prototype on and off.\r\n\r\n","5":"\r\nThis script is dependant on:\r\n\r\n* Exhuberant ctags (http:\/\/ctags.sf.net)\r\n* taglist.vim (http:\/\/vim.sourceforge.net\/scripts\/script.php?script_id=273, alternate: http:\/\/www.geocities.com\/yegappan\/taglist)\r\n\r\nJust install exuberant ctags and drop both taglist.vim and this file into your plugins directory. Then (re)start Vim and use key <F8> to toggle the prototype on and off.\r\n\r\n","first_name":"Steve","6":"Steve","last_name":"Hall","7":"Hall","releases":[{"0":"1094","vim_version":"6.0","1":"6.0","script_version":"1.01","2":"1.01","version_comment":"* Improved restoration of existing statusline by escaping pipe\/bar and space chars.\r\n* Silenced errors when searching for tags file and it doesn't exist.\r\n","3":"* Improved restoration of existing statusline by escaping pipe\/bar and space chars.\r\n* Silenced errors when searching for tags file and it doesn't exist.\r\n","package":"cream-statusline-prototype.vim","4":"cream-statusline-prototype.vim","src_id":"3508","5":"3508","creation_date":"1096555408","6":"1096555408"},{"0":"1094","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"cream-statusline-prototype.vim","4":"cream-statusline-prototype.vim","src_id":"3505","5":"3505","creation_date":"1096490293","6":"1096490293"}]},"1093":{"script_id":"1093","0":"1093","script_name":"Archive","1":"Archive","script_type":"utility","2":"utility","summary":"Open archives in vim as a tree or flat list, w\/ nesting support.","3":"Open archives in vim as a tree or flat list, w\/ nesting support.","description":"Archive is a vim plugin which allows you to browse archive files (zip, jar, tar, tar.gz, tar.bz2, etc) in vim as a tree (supporting nested archives) or as a flat list.\r\n\r\nNote that you must currently have java 1.5 or greater installed as a prerequisite.\r\n\r\nhttp:\/\/github.com\/ervandew\/archive","4":"Archive is a vim plugin which allows you to browse archive files (zip, jar, tar, tar.gz, tar.bz2, etc) in vim as a tree (supporting nested archives) or as a flat list.\r\n\r\nNote that you must currently have java 1.5 or greater installed as a prerequisite.\r\n\r\nhttp:\/\/github.com\/ervandew\/archive","install_details":"Requires that java and javac be on your path.\r\n\r\nUnzip the archive.zip file into your vimfiles location of choice after which you can then start viewing archive files in vim.","5":"Requires that java and javac be on your path.\r\n\r\nUnzip the archive.zip file into your vimfiles location of choice after which you can then start viewing archive files in vim.","first_name":"Eric","6":"Eric","last_name":"Van Dewoestine","7":"Van Dewoestine","releases":[{"0":"1093","vim_version":"7.0","1":"7.0","script_version":"1.1","2":"1.1","version_comment":"Fixes a few issues, mostly Windows related.","3":"Fixes a few issues, mostly Windows related.","package":"archive.zip","4":"archive.zip","src_id":"15210","5":"15210","creation_date":"1300047757","6":"1300047757"},{"0":"1093","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"New and improved archive viewer broken out from eclim.","3":"New and improved archive viewer broken out from eclim.","package":"archive.zip","4":"archive.zip","src_id":"14908","5":"14908","creation_date":"1296339354","6":"1296339354"}]},"1092":{"script_id":"1092","0":"1092","script_name":"blitzbasic.vim","1":"blitzbasic.vim","script_type":"syntax","2":"syntax","summary":"syntax file for blitzbasic source code","3":"syntax file for blitzbasic source code","description":"Just a syntax file. Who will use vim to edit blitzbasic programs is another question :)","4":"Just a syntax file. Who will use vim to edit blitzbasic programs is another question :)","install_details":"Read the FAQ, or do it the wrong way like me: put blitzbasic.vim into \/usr\/share\/vim\/vim63\/syntax\/, and edit  \/usr\/share\/vim\/vim63\/filetype.vim, addings this:\r\n\" BlitzBasic\r\nau BufNewFile,BufRead *.bb\t\t\tcall <SID>FTVB(\"blitzbasic\")","5":"Read the FAQ, or do it the wrong way like me: put blitzbasic.vim into \/usr\/share\/vim\/vim63\/syntax\/, and edit  \/usr\/share\/vim\/vim63\/filetype.vim, addings this:\r\n\" BlitzBasic\r\nau BufNewFile,BufRead *.bb\t\t\tcall <SID>FTVB(\"blitzbasic\")","first_name":"elias","6":"elias","last_name":"pschernig","7":"pschernig","releases":[{"0":"1092","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"blitzbasic.vim","4":"blitzbasic.vim","src_id":"3498","5":"3498","creation_date":"1096353701","6":"1096353701"}]},"1091":{"script_id":"1091","0":"1091","script_name":"VimRegEx.vim","1":"VimRegEx.vim","script_type":"utility","2":"utility","summary":"Regular Expression Developer for Vim","3":"Regular Expression Developer for Vim","description":"Start with one of the commands\r\n\r\n:Vimrex\r\n  or\r\n:VimRegEx\r\n\r\nThe first opens within the current (g)vim session, the second starts a new (g)vim\r\n\r\n'z?' or the menu 'Usage' button opens a usage buffer.\r\n\r\nVimRegEx.vim is a plugin that aids in development\/construction\/analysis of Vim regular expressions.  It is not a search utility, although it certainly does that.  It is a development\/learning environment that allows writing Vim regular expressions, element-by-element analysis of these expressions, and execution of the expressions against source text with the results illustrated both verbally in text and graphically in different highlighting for different types of regular expression atoms.\r\n\r\nIt allows you to see, in verbal\/graphical analytical terms, just what is being searched for and what will result with a given Vim regular expression.\r\n\r\nThere are comparable tools on the net for other environments (notably .NET, Perl, and Python), but nothing exists for Vim ... until now!\r\n\r\nThe plugin is written specifically for Vim, so you can build your regular expressions as you would in Vim.  In other tools, you'd have to make allowances for backslash escaping specific elements (like '(', ')', '+', '?', etc.) to use what you had developed in those tools.  You'd also have to make substitutions, like '\\<' for '\\b' for word boundary ('\\b' has its own meaning in Vim), and '\\(...\\)\\@=' for '(?=...)'.  This renders these other tools all but useless for Vim.\r\n\r\nVimRegEx has its own built in documentation, a rich set of variables for tuning its performance\/appearance to your liking in your vimrc, an easy menu driven interface for gvim as well as easy to use keyboard mappings for the same commands in vim.  There's also file generation capability to save your windows in text or html.\r\n\r\nIf you've been struggling with a regular expression and can't seem to get it to do what you want, maybe what you think you're doing isn't what Vim sees.  See what Vim sees in VimRegEx.  In the VimRegEx enviroment, what you see is what you get!","4":"Start with one of the commands\r\n\r\n:Vimrex\r\n  or\r\n:VimRegEx\r\n\r\nThe first opens within the current (g)vim session, the second starts a new (g)vim\r\n\r\n'z?' or the menu 'Usage' button opens a usage buffer.\r\n\r\nVimRegEx.vim is a plugin that aids in development\/construction\/analysis of Vim regular expressions.  It is not a search utility, although it certainly does that.  It is a development\/learning environment that allows writing Vim regular expressions, element-by-element analysis of these expressions, and execution of the expressions against source text with the results illustrated both verbally in text and graphically in different highlighting for different types of regular expression atoms.\r\n\r\nIt allows you to see, in verbal\/graphical analytical terms, just what is being searched for and what will result with a given Vim regular expression.\r\n\r\nThere are comparable tools on the net for other environments (notably .NET, Perl, and Python), but nothing exists for Vim ... until now!\r\n\r\nThe plugin is written specifically for Vim, so you can build your regular expressions as you would in Vim.  In other tools, you'd have to make allowances for backslash escaping specific elements (like '(', ')', '+', '?', etc.) to use what you had developed in those tools.  You'd also have to make substitutions, like '\\<' for '\\b' for word boundary ('\\b' has its own meaning in Vim), and '\\(...\\)\\@=' for '(?=...)'.  This renders these other tools all but useless for Vim.\r\n\r\nVimRegEx has its own built in documentation, a rich set of variables for tuning its performance\/appearance to your liking in your vimrc, an easy menu driven interface for gvim as well as easy to use keyboard mappings for the same commands in vim.  There's also file generation capability to save your windows in text or html.\r\n\r\nIf you've been struggling with a regular expression and can't seem to get it to do what you want, maybe what you think you're doing isn't what Vim sees.  See what Vim sees in VimRegEx.  In the VimRegEx enviroment, what you see is what you get!","install_details":"NOTE: REQUIRES vsutil.vim\r\nhttp:\/\/www.vim.org\/scripts\/script.php?script_id=1056\r\nplace both in your .vim|vimfiles plugin dir\r\n\r\n","5":"NOTE: REQUIRES vsutil.vim\r\nhttp:\/\/www.vim.org\/scripts\/script.php?script_id=1056\r\nplace both in your .vim|vimfiles plugin dir\r\n\r\n","first_name":"Dave","6":"Dave","last_name":"Silvia","7":"Silvia","releases":[{"0":"1091","vim_version":"6.0","1":"6.0","script_version":"1.1","2":"1.1","version_comment":"Version 1.1\r\nDate:        10\/12\/2004\r\nFixed:\r\n- Problem with UNIX type\r\n  systems and have a single\r\n  quote in the filename for\r\n  the usage file.  Removed\r\n  the single quotes.","3":"Version 1.1\r\nDate:        10\/12\/2004\r\nFixed:\r\n- Problem with UNIX type\r\n  systems and have a single\r\n  quote in the filename for\r\n  the usage file.  Removed\r\n  the single quotes.","package":"VimRegEx.vim","4":"VimRegEx.vim","src_id":"3536","5":"3536","creation_date":"1097550949","6":"1097550949"},{"0":"1091","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Version 1.0 Initial Release","3":"Version 1.0 Initial Release","package":"VimRegEx.vim","4":"VimRegEx.vim","src_id":"3535","5":"3535","creation_date":"1097381464","6":"1097381464"}]},"1090":{"script_id":"1090","0":"1090","script_name":"InsertTry.vim","1":"InsertTry.vim","script_type":"ftplugin","2":"ftplugin","summary":"put java's try catch around marked lines","3":"put java's try catch around marked lines","description":"mark some lines and type \u00c2\u00act\r\nthe marked lines will be enclosed in a try block with an additional catch and finally block\r\n\r\nWhre is the \u00c2\u00ac key? Feel free to change this.\r\n\r\ncustomize:\r\n:let b:java_InsertTry_Style=\"Java\" | \"C\" | \"JavaShort\"                         default = \"Java\"\r\n:let b:java_InsertTry_Goto=\"catch\" | \".\"                                                   default = \"catch\"\r\n\r\n","4":"mark some lines and type \u00c2\u00act\r\nthe marked lines will be enclosed in a try block with an additional catch and finally block\r\n\r\nWhre is the \u00c2\u00ac key? Feel free to change this.\r\n\r\ncustomize:\r\n:let b:java_InsertTry_Style=\"Java\" | \"C\" | \"JavaShort\"                         default = \"Java\"\r\n:let b:java_InsertTry_Goto=\"catch\" | \".\"                                                   default = \"catch\"\r\n\r\n","install_details":"simply copy to\r\n${VIMRUNTIME}\/ftplugin\/java\/","5":"simply copy to\r\n${VIMRUNTIME}\/ftplugin\/java\/","first_name":"Roman","6":"Roman","last_name":"Wagner","7":"Wagner","releases":[{"0":"1090","vim_version":"6.0","1":"6.0","script_version":"0.2","2":"0.2","version_comment":"* bugs deleted\r\n* new features ( see description )","3":"* bugs deleted\r\n* new features ( see description )","package":"InsertTry.vim","4":"InsertTry.vim","src_id":"3497","5":"3497","creation_date":"1096337283","6":"1096337283"},{"0":"1090","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"InsertTry.vim","4":"InsertTry.vim","src_id":"3493","5":"3493","creation_date":"1096288033","6":"1096288033"}]},"1089":{"script_id":"1089","0":"1089","script_name":"sas.vim","1":"sas.vim","script_type":"indent","2":"indent","summary":"SAS indent file","3":"SAS indent file","description":"SAS indent file.","4":"SAS indent file.","install_details":"Unix or Linux: copy the script into $HOME\/.vim\/indent or in $VIM\/vimfiles\r\nWindows: copy the script into $VIM_INSTALL_DIR\\vimfiles\\indent","5":"Unix or Linux: copy the script into $HOME\/.vim\/indent or in $VIM\/vimfiles\r\nWindows: copy the script into $VIM_INSTALL_DIR\\vimfiles\\indent","first_name":"Jianzhong","6":"Jianzhong","last_name":"Liu","7":"Liu","releases":[{"0":"1089","vim_version":"6.0","1":"6.0","script_version":"0.3","2":"0.3","version_comment":"1. correct a bug of comments \r\n2. correct a bug of statement %IF ... %THEN %DO; \r\n3. TODO: fault tolerance (missing RUN) within a macro","3":"1. correct a bug of comments \r\n2. correct a bug of statement %IF ... %THEN %DO; \r\n3. TODO: fault tolerance (missing RUN) within a macro","package":"sas.vim","4":"sas.vim","src_id":"4193","5":"4193","creation_date":"1114178900","6":"1114178900"},{"0":"1089","vim_version":"6.0","1":"6.0","script_version":"0.2","2":"0.2","version_comment":"1. Fixed a bug for if statement\r\n2. More flexibility for statements with do\r\n3. Add fault tolerance for missing \"run;\" statements at the end of data\/proc step","3":"1. Fixed a bug for if statement\r\n2. More flexibility for statements with do\r\n3. Add fault tolerance for missing \"run;\" statements at the end of data\/proc step","package":"sas.vim","4":"sas.vim","src_id":"3488","5":"3488","creation_date":"1096146281","6":"1096146281"}]},"1088":{"script_id":"1088","0":"1088","script_name":"cfengine.vim","1":"cfengine.vim","script_type":"syntax","2":"syntax","summary":"Alternate Cfengine Syntax Highlighting","3":"Alternate Cfengine Syntax Highlighting","description":"An improved version of cfengine syntax highlighting.  I started this syntax highlight before I realize that one already exists.  This scripts doesn't highlight everything, but it highlights sections, classes and identifiers.  It highlights boolean operators in the classes, and highlights the variable operators.  It also handles embedded PHP.  If you use other languages to generate cfengine you can add them into the syntax highlight easily.","4":"An improved version of cfengine syntax highlighting.  I started this syntax highlight before I realize that one already exists.  This scripts doesn't highlight everything, but it highlights sections, classes and identifiers.  It highlights boolean operators in the classes, and highlights the variable operators.  It also handles embedded PHP.  If you use other languages to generate cfengine you can add them into the syntax highlight easily.","install_details":"","5":"","first_name":"Christian","6":"Christian","last_name":"Pearce","7":"Pearce","releases":[{"0":"1088","vim_version":"6.0","1":"6.0","script_version":"0.3","2":"0.3","version_comment":"Fixed PHP highlighting inside strings","3":"Fixed PHP highlighting inside strings","package":"cfengine.vim","4":"cfengine.vim","src_id":"3543","5":"3543","creation_date":"1097741066","6":"1097741066"},{"0":"1088","vim_version":"6.0","1":"6.0","script_version":"0.2","2":"0.2","version_comment":"Fixed TODO\r\nImproved the class pattern match to allow for oneliners\r\nAdded define=classname to the list of things to be highlighted\r\n","3":"Fixed TODO\r\nImproved the class pattern match to allow for oneliners\r\nAdded define=classname to the list of things to be highlighted\r\n","package":"cfengine.vim","4":"cfengine.vim","src_id":"3480","5":"3480","creation_date":"1096012097","6":"1096012097"},{"0":"1088","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"cfengine.vim","4":"cfengine.vim","src_id":"3475","5":"3475","creation_date":"1095928570","6":"1095928570"}]},"1087":{"script_id":"1087","0":"1087","script_name":"tpp.vim","1":"tpp.vim","script_type":"syntax","2":"syntax","summary":"Syntax highlighting for tpp presentation files","3":"Syntax highlighting for tpp presentation files","description":"TPP (http:\/\/synflood.at\/tpp\/) is a presentation tool for the Linux\/Unix commandline.","4":"TPP (http:\/\/synflood.at\/tpp\/) is a presentation tool for the Linux\/Unix commandline.","install_details":"Installation details in English and German can be found at http:\/\/www.technixen.net\/modules.php?op=modload&name=Downloads&file=index&req=viewdownloaddetails&lid=7&ttitle=tpp.vim","5":"Installation details in English and German can be found at http:\/\/www.technixen.net\/modules.php?op=modload&name=Downloads&file=index&req=viewdownloaddetails&lid=7&ttitle=tpp.vim","first_name":"Patricia","6":"Patricia","last_name":"Jung","7":"Jung","releases":[{"0":"1087","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"tpp.vim","4":"tpp.vim","src_id":"3463","5":"3463","creation_date":"1095586630","6":"1095586630"}]},"1086":{"script_id":"1086","0":"1086","script_name":"Black Angus","1":"Black Angus","script_type":"color scheme","2":"color scheme","summary":"This is a mainly green on black color scheme (Gui & term)","3":"This is a mainly green on black color scheme (Gui & term)","description":"This is a mainly green on black color scheme.  I have tried to keep the vim \/ gvim colors as \r\nconsistant as possible.  This works well with the std_c syntax highlighting.\r\nEnjoy.","4":"This is a mainly green on black color scheme.  I have tried to keep the vim \/ gvim colors as \r\nconsistant as possible.  This works well with the std_c syntax highlighting.\r\nEnjoy.","install_details":"Put it into your vimfiles\/color\/ folder","5":"Put it into your vimfiles\/color\/ folder","first_name":"Angus","6":"Angus","last_name":"Salkeld","7":"Salkeld","releases":[{"0":"1086","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"black_angus.vim","4":"black_angus.vim","src_id":"3448","5":"3448","creation_date":"1095083775","6":"1095083775"}]},"1085":{"script_id":"1085","0":"1085","script_name":"earth.vim","1":"earth.vim","script_type":"color scheme","2":"color scheme","summary":"Green base for colorscheme","3":"Green base for colorscheme","description":"This is a colorscheme that's easy on the eyes. It has an earthy feel to it, as I have used a lot of green and brown shades.","4":"This is a colorscheme that's easy on the eyes. It has an earthy feel to it, as I have used a lot of green and brown shades.","install_details":"Drop it into the colors folder and invoke using \r\n:colorscheme earth","5":"Drop it into the colors folder and invoke using \r\n:colorscheme earth","first_name":"Shrinath","6":"Shrinath","last_name":"V","7":"V","releases":[{"0":"1085","vim_version":"6.0","1":"6.0","script_version":"0.2","2":"0.2","version_comment":"I had used an earlier colorscheme as the base. Forgot to modify details :)","3":"I had used an earlier colorscheme as the base. Forgot to modify details :)","package":"earth.vim","4":"earth.vim","src_id":"3447","5":"3447","creation_date":"1095034523","6":"1095034523"},{"0":"1085","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"earth.vim","4":"earth.vim","src_id":"3446","5":"3446","creation_date":"1095034312","6":"1095034312"}]},"1084":{"script_id":"1084","0":"1084","script_name":"multiAPIsyntax","1":"multiAPIsyntax","script_type":"syntax","2":"syntax","summary":"Syntax for Qt, KDE, wxWidgets, GTK1, GTK2 libraries","3":"Syntax for Qt, KDE, wxWidgets, GTK1, GTK2 libraries","description":"This is a new version of former script vimscript #787.\r\nThis script scans Qt 3.x, KDE 3.x, wxWidgets, GTK 1.2.x and GTK 2.x headers, then creates vim syntax file (cType definitons for all classes\/structs) for highlighting and plain list of classes for vim word-completion (for use with vimscript #213). multiAPIsyntax supports command line options like --qt, --kde, --wx, --gtk1, --gtk2, so you may choose which libraries to scan.","4":"This is a new version of former script vimscript #787.\r\nThis script scans Qt 3.x, KDE 3.x, wxWidgets, GTK 1.2.x and GTK 2.x headers, then creates vim syntax file (cType definitons for all classes\/structs) for highlighting and plain list of classes for vim word-completion (for use with vimscript #213). multiAPIsyntax supports command line options like --qt, --kde, --wx, --gtk1, --gtk2, so you may choose which libraries to scan.","install_details":"Requires Perl; no additional Perl modules are required. Uses pkg-config to obtain GTK2 location. Uses gtk-config and wx-config to obtain GTK 1.2.x and wxWidgets locations. Uses $QTDIR and $KDEDIR environment variables to obtain Qt and KDE locations. To create syntax file and completion-list for Qt and KDE (for cvim plugin) use:\r\nmultiAPIsyntax --qt --kde -s ~\/.vim\/after\/syntax\/c.vim -l ~\/.vim\/wordlists\/qtkde.list","5":"Requires Perl; no additional Perl modules are required. Uses pkg-config to obtain GTK2 location. Uses gtk-config and wx-config to obtain GTK 1.2.x and wxWidgets locations. Uses $QTDIR and $KDEDIR environment variables to obtain Qt and KDE locations. To create syntax file and completion-list for Qt and KDE (for cvim plugin) use:\r\nmultiAPIsyntax --qt --kde -s ~\/.vim\/after\/syntax\/c.vim -l ~\/.vim\/wordlists\/qtkde.list","first_name":"Pawel","6":"Pawel","last_name":"Stolowski","7":"Stolowski","releases":[{"0":"1084","vim_version":"6.0","1":"6.0","script_version":"1.4","2":"1.4","version_comment":"Fixed trivial bug with help (-h) not being shown.","3":"Fixed trivial bug with help (-h) not being shown.","package":"multiAPIsyntax","4":"multiAPIsyntax","src_id":"3453","5":"3453","creation_date":"1095206742","6":"1095206742"},{"0":"1084","vim_version":"6.0","1":"6.0","script_version":"1.3","2":"1.3","version_comment":"Initial upload","3":"Initial upload","package":"multiAPIsyntax","4":"multiAPIsyntax","src_id":"3444","5":"3444","creation_date":"1094991591","6":"1094991591"}]},"1083":{"script_id":"1083","0":"1083","script_name":"multiwin.vim","1":"multiwin.vim","script_type":"utility","2":"utility","summary":"MultiWin: use VIM like a Rolodex","3":"MultiWin: use VIM like a Rolodex","description":"This script manipulates noequalalways, splitbelow, winheight, winminheight, and laststatus to make each buffer (either loaded by command line or via :new) occupy its own window.  All inactive windows are minimized to only statuslines.  This gives the appearance of a Rolodex.  Simply click on a status line and that window is maximized.\r\n\r\nNote: once vim is loaded, you must use :new (or :split) to \"add\" a window to the list.  Using :e will change the buffer in the current window.\r\n\r\nThis has same effect of using -o on the vim command line when you run vim with multiple filenames on the command line, or \"Edit with single vim\" context menu in Windows Explorer when multiple files are selected.\r\n\r\nThis script will not run if vim is set to compatible or is in diff mode.\r\n\r\nYou can disable the automatic-ness of this script by setting g:singlewin in your vimrc\r\n\r\nThis script is compatible with vim 6.3 and 7.0. \r\n\r\nI'd would like to give credit where credit is due:\r\nAntoine J. Mechelynck - the initial idea of playing with winheight and the other options\r\nCharles E. Campbell, Jr. - enlightening me on the use of sball\r\nBram - for deflecting my attempts at sliding a patch in and making me think of alternate ways to trick vim into maximizing the current window.and for showing me eventhandler()\r\nBreadman - for showing me wincmd _\r\n","4":"This script manipulates noequalalways, splitbelow, winheight, winminheight, and laststatus to make each buffer (either loaded by command line or via :new) occupy its own window.  All inactive windows are minimized to only statuslines.  This gives the appearance of a Rolodex.  Simply click on a status line and that window is maximized.\r\n\r\nNote: once vim is loaded, you must use :new (or :split) to \"add\" a window to the list.  Using :e will change the buffer in the current window.\r\n\r\nThis has same effect of using -o on the vim command line when you run vim with multiple filenames on the command line, or \"Edit with single vim\" context menu in Windows Explorer when multiple files are selected.\r\n\r\nThis script will not run if vim is set to compatible or is in diff mode.\r\n\r\nYou can disable the automatic-ness of this script by setting g:singlewin in your vimrc\r\n\r\nThis script is compatible with vim 6.3 and 7.0. \r\n\r\nI'd would like to give credit where credit is due:\r\nAntoine J. Mechelynck - the initial idea of playing with winheight and the other options\r\nCharles E. Campbell, Jr. - enlightening me on the use of sball\r\nBram - for deflecting my attempts at sliding a patch in and making me think of alternate ways to trick vim into maximizing the current window.and for showing me eventhandler()\r\nBreadman - for showing me wincmd _\r\n","install_details":"Place this script into your vimfiles\\plugin directory.\r\n\r\nWARNING!  This will override settings to noequalalways, splitbelow, winheight, winminheight, and laststatusline.","5":"Place this script into your vimfiles\\plugin directory.\r\n\r\nWARNING!  This will override settings to noequalalways, splitbelow, winheight, winminheight, and laststatusline.","first_name":"Patrick","6":"Patrick","last_name":"Avery","7":"Avery","releases":[{"0":"1083","vim_version":"6.0","1":"6.0","script_version":"1.4","2":"1.4","version_comment":"MultiWin now keeps quickfix windows at a certain height (default: 10 lines).\r\n\r\nMultiWin now reacts to files opened by drag-drop and via the Explorer context menu \"Edit with existing Vim\" command.","3":"MultiWin now keeps quickfix windows at a certain height (default: 10 lines).\r\n\r\nMultiWin now reacts to files opened by drag-drop and via the Explorer context menu \"Edit with existing Vim\" command.","package":"multiwin.vim","4":"multiwin.vim","src_id":"3724","5":"3724","creation_date":"1103801961","6":"1103801961"},{"0":"1083","vim_version":"6.0","1":"6.0","script_version":"1.3","2":"1.3","version_comment":"Added extra mappings (gf opens a new window for filename under cursor, Alt-Left and Alt-Right change the current window) and added documentation via DrChip's HelpExtractor.","3":"Added extra mappings (gf opens a new window for filename under cursor, Alt-Left and Alt-Right change the current window) and added documentation via DrChip's HelpExtractor.","package":"multiwin.vim","4":"multiwin.vim","src_id":"3518","5":"3518","creation_date":"1096871675","6":"1096871675"},{"0":"1083","vim_version":"6.0","1":"6.0","script_version":"1.2","2":"1.2","version_comment":"Added a runtime toggle to suspend multiwin's actions (<Leader>win).","3":"Added a runtime toggle to suspend multiwin's actions (<Leader>win).","package":"multiwin.vim","4":"multiwin.vim","src_id":"3509","5":"3509","creation_date":"1096638226","6":"1096638226"},{"0":"1083","vim_version":"6.0","1":"6.0","script_version":"1.1","2":"1.1","version_comment":"Replaced of the WinHeightKludge function with wincmd _ and stacked the VimEnter event... all thanks to Breadman!","3":"Replaced of the WinHeightKludge function with wincmd _ and stacked the VimEnter event... all thanks to Breadman!","package":"multiwin.vim","4":"multiwin.vim","src_id":"3449","5":"3449","creation_date":"1095107564","6":"1095107564"}]},"1082":{"script_id":"1082","0":"1082","script_name":"MS Word from VIM","1":"MS Word from VIM","script_type":"utility","2":"utility","summary":"Interact with MS Word from VIM","3":"Interact with MS Word from VIM","description":"To interact with Microsoft Word from VIM\r\nCurrently supports use of Word's Thesaurus and Speller\r\n\r\nCopyright (C) 2004 Suresh Govindachar  <initial><last name><at><yahoo>\r\n\r\nSystem Requirements:\r\n  \r\n   Windows (with MS Word)\r\n   VIM with embedded perl support\r\n   The perl module Win32::OLE (good way to get this is to have external perl)\r\n\r\nExports: \r\n \r\n   The following four commands are exported to the end-user:\r\n   \r\n      :WordThesaurus    [<cword>]\r\n      :WordSpell        [<cword>]\r\n      :WordAnagram      [<cword>]\r\n      :<range>WordCheckSpelling \r\n   \r\n   In regard to the first three commands:\r\n   \r\n    - Each command can be issued with no arguments or with one argument.\r\n      When no argument is provided, the <cword> (see :help cword) is \r\n      used as the argument.\r\n    - After execution, the \"result\" is appended below the current line.\r\n    - The \"result\" for the Thesaurus command is all \r\n      the synonyms and the antonyms.\r\n    - The \"result\" for the Spell command is all \r\n      the spelling suggestions.\r\n    - The \"result\" for the Anagram command is all \r\n      the anagrams of the given letters.\r\n   \r\n   Try the following:\r\n   \r\n      :WordThesaurus beautiful\r\n      :WordAnagram   abt\r\n      :WordSpell     helo\r\n      :WordSpell     b?t*\r\n   \r\n   In regard to the fourth command (:<range>WordCheckSpelling):\r\n      \r\n    - The default range is the whole buffer -- in order for\r\n      quickfix commands to work, there has to be a file \r\n      associated with the buffer.\r\n   \r\n    - Results are:\r\n   \r\n      - highlighting as Error each misspelled word in the range\r\n        (the filetype is set to nothing so that the only colored\r\n        stuff are the misspelled words)\r\n   \r\n      - ability to use the quickfix commands (:cfirst, :cn, etc) to \r\n        visit each misspelled word and to look at suggestions on spelling it.\r\n   \r\n      - Sub commands (of the :<range>WordCheckSpelling command):\r\n   \r\n           :WordShowMisspelled\r\n                Highlights misspelled words (there won't be any other highlighting)                 \r\n           :WordHideMisspelled\r\n                Restores highlighting based on filetype \r\n           The next five commands extend the corresponding quickfix \r\n                commands (:cfirst, :clast, :cc, :cn, :cp) by\r\n                loading the search register with the appropriate \r\n                misspelled word\r\n                    :Wordfirst\r\n                    :Wordlast\r\n                    :Wordc\r\n                    :Wordn\r\n                    :Wordp\r\n   \r\n      - Optional (controlled by g:no_plugin_maps or g:no_word_maps) \r\n        normal-mode maps:\r\n           <Leader>ws :WordShowMisspelled<CR>\r\n           <Leader>wh :WordHideMisspelled<CR>\r\n           <Leader>wc :Wordc<CR>\r\n           <Leader>wn :Wordn<CR>\r\n           <Leader>wp :Wordp<CR>\r\n\r\nTested on:\r\n\r\n   Windows 98 with Word 97 (and Vim 6.3, ActiveState's perl 5.8).\r\n   Anagram and WildCard NOT supported by Microsoft in later versions of MSWord -- see\r\n   http:\/\/support.microsoft.com\/default.aspx?scid=kb;en-us;224722 !!!\r\n\r\nKnown issue:\r\n  \r\n   Sometimes Windows and\/or Word is sluggish and things\r\n   time-out with a \"no service available\" or some such \r\n   error message -- when this happens, just reissue the command.\r\n\r\nAcknowledgment:                                                              \r\n\r\n   Although I conceived and developed this plugin, I\r\n   learnt how to interact with Microsoft Word for \r\n   accessing its Thesaurus and Spelling from: \r\n\r\n    - Chad DeMeyer   (microsoft.public.word.word97vba)\r\n    - Steven Manross (perl-win32-users@listserv.ActiveState.com)\r\n    - Greg Chapman   (perl-win32-users@listserv.ActiveState.com)\r\n    - http:\/\/www.perlmonks.com\/index.pl?node_id=119006\r\n\r\nDisclaimer:                                                                 \r\n\r\n   The material provided here is provided as-is without any warranty --\r\n   without even the implied warranty of merchantability or fitness for a\r\n   particular purpose.  The author assumes no responsibility for errors or\r\n   omissions or for any sort of damages resulting from the use of or\r\n   reliance on the provided material.\r\n","4":"To interact with Microsoft Word from VIM\r\nCurrently supports use of Word's Thesaurus and Speller\r\n\r\nCopyright (C) 2004 Suresh Govindachar  <initial><last name><at><yahoo>\r\n\r\nSystem Requirements:\r\n  \r\n   Windows (with MS Word)\r\n   VIM with embedded perl support\r\n   The perl module Win32::OLE (good way to get this is to have external perl)\r\n\r\nExports: \r\n \r\n   The following four commands are exported to the end-user:\r\n   \r\n      :WordThesaurus    [<cword>]\r\n      :WordSpell        [<cword>]\r\n      :WordAnagram      [<cword>]\r\n      :<range>WordCheckSpelling \r\n   \r\n   In regard to the first three commands:\r\n   \r\n    - Each command can be issued with no arguments or with one argument.\r\n      When no argument is provided, the <cword> (see :help cword) is \r\n      used as the argument.\r\n    - After execution, the \"result\" is appended below the current line.\r\n    - The \"result\" for the Thesaurus command is all \r\n      the synonyms and the antonyms.\r\n    - The \"result\" for the Spell command is all \r\n      the spelling suggestions.\r\n    - The \"result\" for the Anagram command is all \r\n      the anagrams of the given letters.\r\n   \r\n   Try the following:\r\n   \r\n      :WordThesaurus beautiful\r\n      :WordAnagram   abt\r\n      :WordSpell     helo\r\n      :WordSpell     b?t*\r\n   \r\n   In regard to the fourth command (:<range>WordCheckSpelling):\r\n      \r\n    - The default range is the whole buffer -- in order for\r\n      quickfix commands to work, there has to be a file \r\n      associated with the buffer.\r\n   \r\n    - Results are:\r\n   \r\n      - highlighting as Error each misspelled word in the range\r\n        (the filetype is set to nothing so that the only colored\r\n        stuff are the misspelled words)\r\n   \r\n      - ability to use the quickfix commands (:cfirst, :cn, etc) to \r\n        visit each misspelled word and to look at suggestions on spelling it.\r\n   \r\n      - Sub commands (of the :<range>WordCheckSpelling command):\r\n   \r\n           :WordShowMisspelled\r\n                Highlights misspelled words (there won't be any other highlighting)                 \r\n           :WordHideMisspelled\r\n                Restores highlighting based on filetype \r\n           The next five commands extend the corresponding quickfix \r\n                commands (:cfirst, :clast, :cc, :cn, :cp) by\r\n                loading the search register with the appropriate \r\n                misspelled word\r\n                    :Wordfirst\r\n                    :Wordlast\r\n                    :Wordc\r\n                    :Wordn\r\n                    :Wordp\r\n   \r\n      - Optional (controlled by g:no_plugin_maps or g:no_word_maps) \r\n        normal-mode maps:\r\n           <Leader>ws :WordShowMisspelled<CR>\r\n           <Leader>wh :WordHideMisspelled<CR>\r\n           <Leader>wc :Wordc<CR>\r\n           <Leader>wn :Wordn<CR>\r\n           <Leader>wp :Wordp<CR>\r\n\r\nTested on:\r\n\r\n   Windows 98 with Word 97 (and Vim 6.3, ActiveState's perl 5.8).\r\n   Anagram and WildCard NOT supported by Microsoft in later versions of MSWord -- see\r\n   http:\/\/support.microsoft.com\/default.aspx?scid=kb;en-us;224722 !!!\r\n\r\nKnown issue:\r\n  \r\n   Sometimes Windows and\/or Word is sluggish and things\r\n   time-out with a \"no service available\" or some such \r\n   error message -- when this happens, just reissue the command.\r\n\r\nAcknowledgment:                                                              \r\n\r\n   Although I conceived and developed this plugin, I\r\n   learnt how to interact with Microsoft Word for \r\n   accessing its Thesaurus and Spelling from: \r\n\r\n    - Chad DeMeyer   (microsoft.public.word.word97vba)\r\n    - Steven Manross (perl-win32-users@listserv.ActiveState.com)\r\n    - Greg Chapman   (perl-win32-users@listserv.ActiveState.com)\r\n    - http:\/\/www.perlmonks.com\/index.pl?node_id=119006\r\n\r\nDisclaimer:                                                                 \r\n\r\n   The material provided here is provided as-is without any warranty --\r\n   without even the implied warranty of merchantability or fitness for a\r\n   particular purpose.  The author assumes no responsibility for errors or\r\n   omissions or for any sort of damages resulting from the use of or\r\n   reliance on the provided material.\r\n","install_details":"Place in your vimfiles\/plugin directory (and source\r\nit or restart VIM).","5":"Place in your vimfiles\/plugin directory (and source\r\nit or restart VIM).","first_name":"Suresh","6":"Suresh","last_name":"Govindachar","7":"Govindachar","releases":[{"0":"1082","vim_version":"6.0","1":"6.0","script_version":"1.11","2":"1.11","version_comment":"Minor tweak:  set iskeyword to a-z,A-Z to better highlight misspelled words (restore iskeyword to original value after redraw'ing has highlighted misspelled words)","3":"Minor tweak:  set iskeyword to a-z,A-Z to better highlight misspelled words (restore iskeyword to original value after redraw'ing has highlighted misspelled words)","package":"word.vim","4":"word.vim","src_id":"3438","5":"3438","creation_date":"1094771521","6":"1094771521"},{"0":"1082","vim_version":"6.0","1":"6.0","script_version":"1.10","2":"1.10","version_comment":"New feature:  given a range of lines, figure out possible spellings for each misspelled word therein and set-up quickfix to navigate to each misspelled word (with spelling suggestions as the quickfix 'error' message) \r\n\r\nPrevious features:  Thesaurus, anagram, wild-card based spelling\r\n   ","3":"New feature:  given a range of lines, figure out possible spellings for each misspelled word therein and set-up quickfix to navigate to each misspelled word (with spelling suggestions as the quickfix 'error' message) \r\n\r\nPrevious features:  Thesaurus, anagram, wild-card based spelling\r\n   ","package":"word.vim","4":"word.vim","src_id":"3436","5":"3436","creation_date":"1094751175","6":"1094751175"}]},"1081":{"script_id":"1081","0":"1081","script_name":"HiColors","1":"HiColors","script_type":"syntax","2":"syntax","summary":"Colorscheme display and editor","3":"Colorscheme display and editor","description":"You'll get to see your colornames' colors and edit your colorscheme with the hicolors ftplugin\/syntax\/help files.  Leftclick on any colorname and you'll bring up the help page on that colorname (if any).\r\n\r\nTo see an example, click on\r\n\r\n\thttp:\/\/www.drchip.org\/astronaut\/vim\/colors\/hicolors.html\r\n\r\nto see hicolors displaying the astronaut colorscheme (vimscript#122) color selections for the various highlighting groups.\r\n\r\nThis script is auto-installable via GetLatestVimScripts, too (vimscript#642).\r\n\r\nUse it with vimscript#625 (colorscheme sampler) to see what highlighting groups are supported and what the colors will be.\r\n\r\nBring up the colorscheme editor on each color by right-clicking on the color's name.  Use the mouse's left button to click and drag on the colorbars to select and change colors.  It works with both the gui and those console vims which support the mouse!  You can then write the colorscheme (you'll be prompted for a filename), cancel the change, or indicate that the change is done for that colorname.\r\n\r\n----------------------------------------------------------------------------------------\r\nUSAGE\r\n\r\n    :help hicolors\r\n    <leftmouse>    on a colorname to bring up help on that colorname\r\n    <rightmouse>   on a colorname to bring up the colorscheme editor for that color\r\n      <leftmouse>  click&drag on any colorbar to change the color for that colorname\r\n      <leftmouse>  to select WriteColorscheme, Cancel, or Done\r\n\r\n----------------------------------------------------------------------------------------\r\n\r\n(alpha\/beta version available at http:\/\/www.drchip.org\/astronaut\/vim\/index.html#HICOLORS)\r\n","4":"You'll get to see your colornames' colors and edit your colorscheme with the hicolors ftplugin\/syntax\/help files.  Leftclick on any colorname and you'll bring up the help page on that colorname (if any).\r\n\r\nTo see an example, click on\r\n\r\n\thttp:\/\/www.drchip.org\/astronaut\/vim\/colors\/hicolors.html\r\n\r\nto see hicolors displaying the astronaut colorscheme (vimscript#122) color selections for the various highlighting groups.\r\n\r\nThis script is auto-installable via GetLatestVimScripts, too (vimscript#642).\r\n\r\nUse it with vimscript#625 (colorscheme sampler) to see what highlighting groups are supported and what the colors will be.\r\n\r\nBring up the colorscheme editor on each color by right-clicking on the color's name.  Use the mouse's left button to click and drag on the colorbars to select and change colors.  It works with both the gui and those console vims which support the mouse!  You can then write the colorscheme (you'll be prompted for a filename), cancel the change, or indicate that the change is done for that colorname.\r\n\r\n----------------------------------------------------------------------------------------\r\nUSAGE\r\n\r\n    :help hicolors\r\n    <leftmouse>    on a colorname to bring up help on that colorname\r\n    <rightmouse>   on a colorname to bring up the colorscheme editor for that color\r\n      <leftmouse>  click&drag on any colorbar to change the color for that colorname\r\n      <leftmouse>  to select WriteColorscheme, Cancel, or Done\r\n\r\n----------------------------------------------------------------------------------------\r\n\r\n(alpha\/beta version available at http:\/\/www.drchip.org\/astronaut\/vim\/index.html#HICOLORS)\r\n","install_details":"hicolors is now distributed as a vimball!  (see :help vimball)\r\n\r\nvim hicolors.vba.gz\r\n:so %\r\n:q\r\n\r\nFor windows users who aren't using a cygwin\/gcc compiled vim:\r\nvim -u NONE -N syntax\\hicolors.vim\r\n:set ff=dos\r\n:wq\r\nvim -u NONE -N doc\\hicolors.txt\r\n:set ff=dos\r\n:wq\r\nvim -u NONE -N ftplugin\\hicolors.vim\r\n:set ff=dos\r\n:wq","5":"hicolors is now distributed as a vimball!  (see :help vimball)\r\n\r\nvim hicolors.vba.gz\r\n:so %\r\n:q\r\n\r\nFor windows users who aren't using a cygwin\/gcc compiled vim:\r\nvim -u NONE -N syntax\\hicolors.vim\r\n:set ff=dos\r\n:wq\r\nvim -u NONE -N doc\\hicolors.txt\r\n:set ff=dos\r\n:wq\r\nvim -u NONE -N ftplugin\\hicolors.vim\r\n:set ff=dos\r\n:wq","first_name":"Charles","6":"Charles","last_name":"Campbell","7":"Campbell","releases":[{"0":"1081","vim_version":"7.0","1":"7.0","script_version":"8","2":"8","version_comment":"* Vim 7.0's new colors are all included!\r\n* When one changes the colorscheme, all colors that should be \"Ignore\"d now are so linked; these colors aren't specified by the current colorscheme.\r\n\r\nTo use:  :help hicolors\r\n","3":"* Vim 7.0's new colors are all included!\r\n* When one changes the colorscheme, all colors that should be \"Ignore\"d now are so linked; these colors aren't specified by the current colorscheme.\r\n\r\nTo use:  :help hicolors\r\n","package":"hicolors.vba.gz","4":"hicolors.vba.gz","src_id":"5642","5":"5642","creation_date":"1146808632","6":"1146808632"},{"0":"1081","vim_version":"6.0","1":"6.0","script_version":"7","2":"7","version_comment":"The colorscheme editor in hicolors.vim now supports editing colorschemes for 256-color xterms.","3":"The colorscheme editor in hicolors.vim now supports editing colorschemes for 256-color xterms.","package":"hicolors.tar.gz","4":"hicolors.tar.gz","src_id":"5345","5":"5345","creation_date":"1141220430","6":"1141220430"},{"0":"1081","vim_version":"6.0","1":"6.0","script_version":"6","2":"6","version_comment":"1) + - < > keyboard interface installed (intended for use when mouse support is lacking)\r\n2) a help file, hicolorshelp.txt, included (:he hicolors-usage)\r\n","3":"1) + - < > keyboard interface installed (intended for use when mouse support is lacking)\r\n2) a help file, hicolorshelp.txt, included (:he hicolors-usage)\r\n","package":"hicolors.tar.gz","4":"hicolors.tar.gz","src_id":"4787","5":"4787","creation_date":"1132558433","6":"1132558433"},{"0":"1081","vim_version":"6.0","1":"6.0","script_version":"5","2":"5","version_comment":"Bug fix: now handles highlighting groups that are defined without explicit colorization (ie. something with just gui=reverse, for example).","3":"Bug fix: now handles highlighting groups that are defined without explicit colorization (ie. something with just gui=reverse, for example).","package":"hicolors.tar.gz","4":"hicolors.tar.gz","src_id":"4162","5":"4162","creation_date":"1113396175","6":"1113396175"},{"0":"1081","vim_version":"6.0","1":"6.0","script_version":"4","2":"4","version_comment":"Hicolors: now has a super colorscheme editor with a rightmouse click!  And, it still provides its special colorized list of your colorscheme's colornames via help, plus links to any more help with a leftmouse click.\r\n","3":"Hicolors: now has a super colorscheme editor with a rightmouse click!  And, it still provides its special colorized list of your colorscheme's colornames via help, plus links to any more help with a leftmouse click.\r\n","package":"hicolors.tar.gz","4":"hicolors.tar.gz","src_id":"3564","5":"3564","creation_date":"1098279403","6":"1098279403"},{"0":"1081","vim_version":"6.0","1":"6.0","script_version":"3","2":"3","version_comment":"Now includes script-id for GetLatestVimScripts semi-automatic updating and installation\r\n","3":"Now includes script-id for GetLatestVimScripts semi-automatic updating and installation\r\n","package":"hicolors.tar.gz","4":"hicolors.tar.gz","src_id":"3418","5":"3418","creation_date":"1094199008","6":"1094199008"}]},"1080":{"script_id":"1080","0":"1080","script_name":"xmms.vim","1":"xmms.vim","script_type":"utility","2":"utility","summary":"Control xmms from within VIM","3":"Control xmms from within VIM","description":"This script maps xmms control functions to the following functionkeys:\r\n\r\nF6        Decrease volume by 5%\r\nF7        Increase volume by 5%\r\nF8        Show title of currently playing song\r\nF9        Open XMMS\r\nS-F9    Close XMMS\r\nF10      Start playing\r\nS-F10  Stop playing\r\nF11      Pause playing\r\nS-F11  Toggle shuffle\r\nF12      Play next\r\nS-F12  Play previous","4":"This script maps xmms control functions to the following functionkeys:\r\n\r\nF6        Decrease volume by 5%\r\nF7        Increase volume by 5%\r\nF8        Show title of currently playing song\r\nF9        Open XMMS\r\nS-F9    Close XMMS\r\nF10      Start playing\r\nS-F10  Stop playing\r\nF11      Pause playing\r\nS-F11  Toggle shuffle\r\nF12      Play next\r\nS-F12  Play previous","install_details":"Make sure you have installed xmmsctrl, if not it is available from this URL: http:\/\/user.it.uu.se\/~adavid\/utils.\r\n\r\nUnpack the archive and install the file xmms.vim into your plugins folder.\r\nThe file xmms.sxw is an OpenOffice swriter file that contains a form that shows the standard keymap, print it to attach it above your functions keys.","5":"Make sure you have installed xmmsctrl, if not it is available from this URL: http:\/\/user.it.uu.se\/~adavid\/utils.\r\n\r\nUnpack the archive and install the file xmms.vim into your plugins folder.\r\nThe file xmms.sxw is an OpenOffice swriter file that contains a form that shows the standard keymap, print it to attach it above your functions keys.","first_name":"Martijn","6":"Martijn","last_name":"Ras","7":"Ras","releases":[{"0":"1080","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"xmms.tar.bz2","4":"xmms.tar.bz2","src_id":"3414","5":"3414","creation_date":"1094186524","6":"1094186524"}]},"1079":{"script_id":"1079","0":"1079","script_name":"replvim.sh","1":"replvim.sh","script_type":"utility","2":"utility","summary":"Allow a read eval print loop and vim to play nicely together","3":"Allow a read eval print loop and vim to play nicely together","description":"UNIX command-line only\r\n\r\n Usage : replvim.sh [options] replname code_type file\r\n\r\nRuns a screen\/vim session on the given file so that one window\r\nholds a repl and another window holds vim. \r\nHit:\r\n<leader>e    to eval the current expression \r\n<leader>r     to evaluate the given marked range\r\n<leader>f     to evaluate the whole file\r\nctrl-a <TAB>  to switch windows to the repl \r\nctrl-a \\      to exit everything \r\nSet the leader in vim with \r\n:let mapleader = \",\" \r\nreplacing \",\" with the key you like the most\r\n\r\nArguments (wrap these in an alias or sh script):\r\n replname   The repl being used (ocaml, bigloo, chicken have been tested)\r\n code_type  Can be 'lisp' for lisp-like or 'ocaml' \r\n file               The file for vim to edit\r\n\r\nOptions:\r\n --lines n   Use n lines of screen space for the repl\r\n --nopipe   Use files instead of pipes. This can be used when vim 6.3\r\n                    gives FSYNC errors when writing to pipes on some OSes.\r\n --echo      Echo the commands being sent to the repl and allow access\r\n                   to them in the readline history\r\n\r\nRequires (on your PATH):\r\n  socat (http:\/\/www.dest-unreach.org\/socat\/)\r\n  screen (http:\/\/www.gnu.org\/software\/screen\/)\r\nif you don't have these your life will be much richer for obtaining them\r\n\r\n(at saul (dot alien-science org)) welcomes your fixes and extensions\r\n\r\n","4":"UNIX command-line only\r\n\r\n Usage : replvim.sh [options] replname code_type file\r\n\r\nRuns a screen\/vim session on the given file so that one window\r\nholds a repl and another window holds vim. \r\nHit:\r\n<leader>e    to eval the current expression \r\n<leader>r     to evaluate the given marked range\r\n<leader>f     to evaluate the whole file\r\nctrl-a <TAB>  to switch windows to the repl \r\nctrl-a \\      to exit everything \r\nSet the leader in vim with \r\n:let mapleader = \",\" \r\nreplacing \",\" with the key you like the most\r\n\r\nArguments (wrap these in an alias or sh script):\r\n replname   The repl being used (ocaml, bigloo, chicken have been tested)\r\n code_type  Can be 'lisp' for lisp-like or 'ocaml' \r\n file               The file for vim to edit\r\n\r\nOptions:\r\n --lines n   Use n lines of screen space for the repl\r\n --nopipe   Use files instead of pipes. This can be used when vim 6.3\r\n                    gives FSYNC errors when writing to pipes on some OSes.\r\n --echo      Echo the commands being sent to the repl and allow access\r\n                   to them in the readline history\r\n\r\nRequires (on your PATH):\r\n  socat (http:\/\/www.dest-unreach.org\/socat\/)\r\n  screen (http:\/\/www.gnu.org\/software\/screen\/)\r\nif you don't have these your life will be much richer for obtaining them\r\n\r\n(at saul (dot alien-science org)) welcomes your fixes and extensions\r\n\r\n","install_details":"install screen\r\ninstall socat\r\nreplvim.sh replname code_type file","5":"install screen\r\ninstall socat\r\nreplvim.sh replname code_type file","first_name":"Saul","6":"Saul","last_name":"Hazledine","7":"Hazledine","releases":[{"0":"1079","vim_version":"6.0","1":"6.0","script_version":"0.3","2":"0.3","version_comment":"Fixed issue with FSYNC error message. Opened repl to user input. Added readline support to repl. Added options to echo commands that are sent to repl and to change initial size of repl window.","3":"Fixed issue with FSYNC error message. Opened repl to user input. Added readline support to repl. Added options to echo commands that are sent to repl and to change initial size of repl window.","package":"replvim.sh","4":"replvim.sh","src_id":"3499","5":"3499","creation_date":"1096371257","6":"1096371257"},{"0":"1079","vim_version":"6.0","1":"6.0","script_version":"0.2","2":"0.2","version_comment":"More sensible handling of lisp expressions.","3":"More sensible handling of lisp expressions.","package":"replvim.sh","4":"replvim.sh","src_id":"3441","5":"3441","creation_date":"1094955026","6":"1094955026"},{"0":"1079","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Tested on Solaris, OpenBSD and Linux.","3":"Tested on Solaris, OpenBSD and Linux.","package":"replvim.sh","4":"replvim.sh","src_id":"3419","5":"3419","creation_date":"1094215815","6":"1094215815"},{"0":"1079","vim_version":"6.0","1":"6.0","script_version":"0.0","2":"0.0","version_comment":"Initial upload","3":"Initial upload","package":"replvim.sh","4":"replvim.sh","src_id":"3413","5":"3413","creation_date":"1094128960","6":"1094128960"}]},"1078":{"script_id":"1078","0":"1078","script_name":"VUT","1":"VUT","script_type":"utility","2":"utility","summary":"Vim Universal Templates","3":"Vim Universal Templates","description":"VUT - Vim Universal Templates are direct continuation\r\nof VHT Script #988. Difference is you can define comment\r\nstrings and use editable or library tags in every type of\r\nfile (html, xhtml, css, javascript, cpp, tex, vim, etc.).\r\n\r\nWhen migrating from VHT - \r\nHAVE TO CHANGE\r\n- change name of core file from *.htmlmain into *.vutmain\r\n- default comment strings are \/*, *\/, script package\r\n  is providing configuration for popular types of files:\r\n\txhtml, html, tex, vim\r\n\r\nNOT HAVE TO CHANGE\r\n- extensions of files are still the same (vhl, vht)\r\n\r\nOld commands are saved for backwards compatibility but added new set of\r\ncommands beginning with VUT or VUL. Note - VH commands may be dropped in\r\nfuture.\r\n\r\nAdditional changes:\r\n- VULupdate\/VUTupdate can take name of library as an argument. Example:\r\n\t:VULupdate panel.vhl\r\n\tThis will update contents of LibraryItem panel.vhl regardless of cursor\r\n\tposition. Superuseful in connection with :argdo family. Argument had be\r\n\ta full path with .vhl extension.\r\n- added: use ~\/Library\/ for global library items for VULshow.  \r\n- fixed: VUTcommit.\r\n","4":"VUT - Vim Universal Templates are direct continuation\r\nof VHT Script #988. Difference is you can define comment\r\nstrings and use editable or library tags in every type of\r\nfile (html, xhtml, css, javascript, cpp, tex, vim, etc.).\r\n\r\nWhen migrating from VHT - \r\nHAVE TO CHANGE\r\n- change name of core file from *.htmlmain into *.vutmain\r\n- default comment strings are \/*, *\/, script package\r\n  is providing configuration for popular types of files:\r\n\txhtml, html, tex, vim\r\n\r\nNOT HAVE TO CHANGE\r\n- extensions of files are still the same (vhl, vht)\r\n\r\nOld commands are saved for backwards compatibility but added new set of\r\ncommands beginning with VUT or VUL. Note - VH commands may be dropped in\r\nfuture.\r\n\r\nAdditional changes:\r\n- VULupdate\/VUTupdate can take name of library as an argument. Example:\r\n\t:VULupdate panel.vhl\r\n\tThis will update contents of LibraryItem panel.vhl regardless of cursor\r\n\tposition. Superuseful in connection with :argdo family. Argument had be\r\n\ta full path with .vhl extension.\r\n- added: use ~\/Library\/ for global library items for VULshow.  \r\n- fixed: VUTcommit.\r\n","install_details":"copy zip archive to you vimfiles\/.vim directory. unzip it.\r\nGLVS AutoInstall compatible.\r\n\r\nInstall help with :helptags ~\/doc\r\n","5":"copy zip archive to you vimfiles\/.vim directory. unzip it.\r\nGLVS AutoInstall compatible.\r\n\r\nInstall help with :helptags ~\/doc\r\n","first_name":"Mikolaj","6":"Mikolaj","last_name":"Machowski","7":"Machowski","releases":[{"0":"1078","vim_version":"6.0","1":"6.0","script_version":"1.2","2":"1.2","version_comment":"- added: VUXinsert commands can take range (also visual)\r\n- added: VULadd command - choose region and call function\r\n\twith obligatory name argument, and immediately commit it.\r\n","3":"- added: VUXinsert commands can take range (also visual)\r\n- added: VULadd command - choose region and call function\r\n\twith obligatory name argument, and immediately commit it.\r\n","package":"vut.zip","4":"vut.zip","src_id":"3422","5":"3422","creation_date":"1094225705","6":"1094225705"},{"0":"1078","vim_version":"6.0","1":"6.0","script_version":"1.1","2":"1.1","version_comment":"- added: library hints are given with proper relative paths to insert in\r\n  BeginLibraryItem declaration\r\n- added: libraries in global dir (~\/Library) can be put in filetype\r\n  directories and only them will be shown. Example for ~\/projekt\/some.js\r\n  VULcheckout will show libraries (.vhl files) in:\r\n\t~\/projekt\r\n\t~\/projekt\/Library\r\n\t~\/Library\r\n\t~\/Library\/javascript\r\n  Note: hierarchy in ~\/Library have to be in filetypes, not file\r\n  extensions.\r\n- added: command completion for VUXcheckout, VUXupdate (Vim 6.2\r\n  required)\r\n- added: GLVS line for AutoInstall in script\r\n- added: shell scriptlet for comment strings\r\n","3":"- added: library hints are given with proper relative paths to insert in\r\n  BeginLibraryItem declaration\r\n- added: libraries in global dir (~\/Library) can be put in filetype\r\n  directories and only them will be shown. Example for ~\/projekt\/some.js\r\n  VULcheckout will show libraries (.vhl files) in:\r\n\t~\/projekt\r\n\t~\/projekt\/Library\r\n\t~\/Library\r\n\t~\/Library\/javascript\r\n  Note: hierarchy in ~\/Library have to be in filetypes, not file\r\n  extensions.\r\n- added: command completion for VUXcheckout, VUXupdate (Vim 6.2\r\n  required)\r\n- added: GLVS line for AutoInstall in script\r\n- added: shell scriptlet for comment strings\r\n","package":"vut.zip","4":"vut.zip","src_id":"3412","5":"3412","creation_date":"1094125779","6":"1094125779"},{"0":"1078","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"vut.zip","4":"vut.zip","src_id":"3404","5":"3404","creation_date":"1094034077","6":"1094034077"}]},"1077":{"script_id":"1077","0":"1077","script_name":"lindo.vim","1":"lindo.vim","script_type":"syntax","2":"syntax","summary":"Syntax highlighting for LINDO (Linear, INteractive, and Discrete Optimizer)","3":"Syntax highlighting for LINDO (Linear, INteractive, and Discrete Optimizer)","description":"A syntax highlighting file for LINDO (Linear, INteractive, and Discrete Optimizer).\r\n\r\nPlease e-mail comments and suggestions with subject \"vim\".\r\n\r\n","4":"A syntax highlighting file for LINDO (Linear, INteractive, and Discrete Optimizer).\r\n\r\nPlease e-mail comments and suggestions with subject \"vim\".\r\n\r\n","install_details":"Copy lindo.vim to your syntax\/ directory.\r\n\r\nAdd the following to filetype.vim:\r\n\r\n- - - - - - - - -\r\n\" LINDO\r\nau BufNewFile,BufRead *.lindo     setf lindo \r\n- - - - - - - - -","5":"Copy lindo.vim to your syntax\/ directory.\r\n\r\nAdd the following to filetype.vim:\r\n\r\n- - - - - - - - -\r\n\" LINDO\r\nau BufNewFile,BufRead *.lindo     setf lindo \r\n- - - - - - - - -","first_name":"Juan","6":"Juan","last_name":"Cataldo","7":"Cataldo","releases":[{"0":"1077","vim_version":"6.0","1":"6.0","script_version":"0.2","2":"0.2","version_comment":"Added more LINDO statements (taken from the \"com\" command output)","3":"Added more LINDO statements (taken from the \"com\" command output)","package":"lindo.vim","4":"lindo.vim","src_id":"3578","5":"3578","creation_date":"1098860410","6":"1098860410"},{"0":"1077","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"lindo.vim","4":"lindo.vim","src_id":"3399","5":"3399","creation_date":"1093946268","6":"1093946268"}]},"1076":{"script_id":"1076","0":"1076","script_name":"cscope_win","1":"cscope_win","script_type":"utility","2":"utility","summary":"Display cscope output in a separate window similar to emacs","3":"Display cscope output in a separate window similar to emacs","description":"This plugin is a c source code browser which uses the standard cscope utility. It is similar to the csqf option provided in vim. But it has an additional advantage of maintaining the tag stacks which is not available while using csqf.\r\nThis script doesn't create a cscope connection. The user needs to create a cscope connection before using this script.\r\nIt is very much similar to the cscope window of emacs\/xemacs.","4":"This plugin is a c source code browser which uses the standard cscope utility. It is similar to the csqf option provided in vim. But it has an additional advantage of maintaining the tag stacks which is not available while using csqf.\r\nThis script doesn't create a cscope connection. The user needs to create a cscope connection before using this script.\r\nIt is very much similar to the cscope window of emacs\/xemacs.","install_details":"copy it to your plugin directory","5":"copy it to your plugin directory","first_name":"Shivakumar","6":"Shivakumar","last_name":"T","7":"T","releases":[{"0":"1076","vim_version":"6.0","1":"6.0","script_version":"2.0","2":"2.0","version_comment":"The new cscope_win plugin doesn't require cscope support in vim. It directly invokes the cscope utility thus having more flexibilty in displaying the results in a more organised fashion. It also requires the sort utility. All cscope commands are accessed through the \"CS\" command. The suboptions to this command are same as VIM's cscope interface commands.\r\nType :CS help for a list of supported options. \r\n-------------------------------------------------------------------------------------\r\nThe following options are provided to configure the cscope plugin.\r\n\r\ng:csAppendResults: Option to specify whether new search results should be appended to the previous results\r\n0 => Don't append\r\n1 => Append\r\n\r\ng:csMaxConn: Option to specify the maximum number of cscope connections\r\n\r\ng:csCaseSensitive: Option to specify whether search should be case sensitive\r\n1  => case sensitive\r\n0  => case insensitive\r\n-1 => decide based on 'ignorecase' option in vim\r\n\r\ng:csWinSize: Option to specify the cscope window height\r\n\r\nThe following key mapings are provided to invoke the cscope plugin\r\n<CTRL-\\>s: Find this C symbol\r\n<CTRL-\\>g  Find this definition\r\n<CTRL-\\>d  Find functions called by this function\r\n<CTRL-\\>c  Find functions calling this function\r\n<CTRL-\\>t  Find assignments to\r\n<CTRL-\\>e  Find this egrep pattern\r\n<CTRL-\\>f  Find this file\r\n<CTRL-\\>i  Find files #including this file\r\n\r\n<CTRL-\\>\\: Toggle the option to append or clear the search results\r\n\r\n","3":"The new cscope_win plugin doesn't require cscope support in vim. It directly invokes the cscope utility thus having more flexibilty in displaying the results in a more organised fashion. It also requires the sort utility. All cscope commands are accessed through the \"CS\" command. The suboptions to this command are same as VIM's cscope interface commands.\r\nType :CS help for a list of supported options. \r\n-------------------------------------------------------------------------------------\r\nThe following options are provided to configure the cscope plugin.\r\n\r\ng:csAppendResults: Option to specify whether new search results should be appended to the previous results\r\n0 => Don't append\r\n1 => Append\r\n\r\ng:csMaxConn: Option to specify the maximum number of cscope connections\r\n\r\ng:csCaseSensitive: Option to specify whether search should be case sensitive\r\n1  => case sensitive\r\n0  => case insensitive\r\n-1 => decide based on 'ignorecase' option in vim\r\n\r\ng:csWinSize: Option to specify the cscope window height\r\n\r\nThe following key mapings are provided to invoke the cscope plugin\r\n<CTRL-\\>s: Find this C symbol\r\n<CTRL-\\>g  Find this definition\r\n<CTRL-\\>d  Find functions called by this function\r\n<CTRL-\\>c  Find functions calling this function\r\n<CTRL-\\>t  Find assignments to\r\n<CTRL-\\>e  Find this egrep pattern\r\n<CTRL-\\>f  Find this file\r\n<CTRL-\\>i  Find files #including this file\r\n\r\n<CTRL-\\>\\: Toggle the option to append or clear the search results\r\n\r\n","package":"cscope_win.vim","4":"cscope_win.vim","src_id":"5399","5":"5399","creation_date":"1141953536","6":"1141953536"}]},"1075":{"script_id":"1075","0":"1075","script_name":"netrw.vim","1":"netrw.vim","script_type":"utility","2":"utility","summary":"Network oriented reading, writing, and browsing (keywords: netrw ftp scp)","3":"Network oriented reading, writing, and browsing (keywords: netrw ftp scp)","description":"                STARTING WITH v66, NETRW REQUIRES VIM 7.0\r\n\r\nNetrw supports reading and writing files across networks.  One may use urls for filenames or one may use netrw's Nread and Nwrite commands. Netrw as provided here supports remote and local directory browsing, and supports  editing files across the network using a variety of methods.  Please report any bugs to NdrOchip@ScampbellPfamily.AbizM - NOSPAM.\r\n\r\n    Example:  vim ftp:\/\/user@machine\/path\r\n\r\n(the following table should be columnar if fixed-width fonts are used in your browser)\r\n\r\n    REMOTE EDITING\r\n        :e dav:\/\/machine[:port]\/path                      uses cadaver\r\n        :e fetch:\/\/[user@]machine\/path                  uses fetch\r\n        :e ftp:\/\/[user@]machine[[:#]port]\/path          uses ftp   autodetects <.netrc>\r\n        :e http:\/\/[user@]machine\/path                    uses http  uses wget\r\n        :e rcp:\/\/[user@]machine\/path                     uses rcp\r\n        :e rsync:\/\/[user@]machine[:port]\/path         uses rsync\r\n        :e scp:\/\/[user@]machine[[:#]port]\/path        uses scp\r\n        :e sftp:\/\/[user@]machine\/path                    uses sftp\r\n\r\n    REMOTE READING\r\n        :Nread ?                                                     give help\r\n        :Nread \"machine:path\"                                 uses rcp\r\n        :Nread \"machine path\"                                 uses ftp   with <.netrc>\r\n        :Nread \"machine id password path\"              uses ftp\r\n        :Nread \"dav:\/\/machine[:port]\/path\"                uses cadaver\r\n        :Nread \"fetch:\/\/[user@]machine\/path\"            uses fetch\r\n        :Nread \"ftp:\/\/[user@]machine[[:#]port]\/path\"    uses ftp   autodetects <.netrc>\r\n        :Nread \"http:\/\/[user@]machine\/path\"              uses http  uses wget\r\n        :Nread \"rcp:\/\/[user@]machine\/path\"               uses rcp\r\n        :Nread \"rsync:\/\/[user@]machine[:port]\/path\"   uses rsync\r\n        :Nread \"scp:\/\/[user@]machine[[:#]port]\/path\"  uses scp\r\n        :Nread \"sftp:\/\/[user@]machine\/path\"             uses sftp\r\n\r\n    REMOTE WRITING\r\n        :Nwrite ?                                                      give help\r\n        :Nwrite \"machine:path\"                                  uses rcp\r\n        :Nwrite \"machine path\"                                  uses ftp   with <.netrc>\r\n        :Nwrite \"machine id password path\"               uses ftp\r\n        :Nwrite \"dav:\/\/machine[:port]\/path\"                  uses cadaver\r\n        :Nwrite \"ftp:\/\/[user@]machine[[:#]port]\/path\"     uses ftp   autodetects <.netrc>\r\n        :Nwrite \"rcp:\/\/[user@]machine\/path\"                uses rcp\r\n        :Nwrite \"rsync:\/\/[user@]machine[:port]\/path\"    uses rsync\r\n        :Nwrite \"scp:\/\/[user@]machine[[:#]port]\/path\"   uses scp\r\n        :Nwrite \"sftp:\/\/[user@]machine\/path\"               uses sftp\r\n        http: not supported!\r\n\r\n    REMOTE DIRECTORY BROWSING\r\n        :e [protocol]:\/\/[user]@hostname\/path\/\r\n        :Nread [protocol]:\/\/[user]@hostname\/path\/\r\n\r\n    LOCAL DIRECTORY BROWSING\r\n        :e \/some\/path\/to\/a\/directory\r\n\r\nNetrw supports browsing both local and remote directories.  For remote directory browsing, one must include a trailing slash (\/) on the path!  The interface resembles the file explorer that comes with vim v6.3 and earlier.  Variables which control netrw's optional behavior are named differently, however.\r\n\r\nFor remote directory browsing, the [protocol]:\/\/[user]@hostname\/path\/ is user-directory relative.  If you want to specify a full path, use another slash before the path: [protocol]:\/\/[user]@hostname\/\/path\/.\r\n\r\nNetrw supports many file-explorer maps, such as o v d D etc.  Look at the help for netrw-o, for example.  One may also use :Explore and relatives to explore directories with the current file.\r\n\r\nThe netrw.vba.gz vimball supports the \"x\" key to execute a file handler for various filetypes.  The file-handling is done in various ways:\r\n\r\n    * Under Windows, rundll32 is used with the FileProtocolHandler\r\n    * If unix and kfmclient exists and is executable, it is used\r\n    * If unix and gnome-open exists and is executable, it is used\r\n    * Otherwise, the NetrwFileHandler.vim file handling script is used\r\n\r\nWith this feature, one may press the \"x\" key when the cursor is atop a filename and invoke an extension-based file handler to do things like display image files, invoke ghostscript on PostScript files, run OpenOffice or Word, etc.\r\n\r\nRECENT NETRWs REQUIRE VIM V7.2\r\n\r\n(alpha\/beta version available at http:\/\/www.drchip.org\/astronaut\/vim\/index.html#NETRW)\r\n","4":"                STARTING WITH v66, NETRW REQUIRES VIM 7.0\r\n\r\nNetrw supports reading and writing files across networks.  One may use urls for filenames or one may use netrw's Nread and Nwrite commands. Netrw as provided here supports remote and local directory browsing, and supports  editing files across the network using a variety of methods.  Please report any bugs to NdrOchip@ScampbellPfamily.AbizM - NOSPAM.\r\n\r\n    Example:  vim ftp:\/\/user@machine\/path\r\n\r\n(the following table should be columnar if fixed-width fonts are used in your browser)\r\n\r\n    REMOTE EDITING\r\n        :e dav:\/\/machine[:port]\/path                      uses cadaver\r\n        :e fetch:\/\/[user@]machine\/path                  uses fetch\r\n        :e ftp:\/\/[user@]machine[[:#]port]\/path          uses ftp   autodetects <.netrc>\r\n        :e http:\/\/[user@]machine\/path                    uses http  uses wget\r\n        :e rcp:\/\/[user@]machine\/path                     uses rcp\r\n        :e rsync:\/\/[user@]machine[:port]\/path         uses rsync\r\n        :e scp:\/\/[user@]machine[[:#]port]\/path        uses scp\r\n        :e sftp:\/\/[user@]machine\/path                    uses sftp\r\n\r\n    REMOTE READING\r\n        :Nread ?                                                     give help\r\n        :Nread \"machine:path\"                                 uses rcp\r\n        :Nread \"machine path\"                                 uses ftp   with <.netrc>\r\n        :Nread \"machine id password path\"              uses ftp\r\n        :Nread \"dav:\/\/machine[:port]\/path\"                uses cadaver\r\n        :Nread \"fetch:\/\/[user@]machine\/path\"            uses fetch\r\n        :Nread \"ftp:\/\/[user@]machine[[:#]port]\/path\"    uses ftp   autodetects <.netrc>\r\n        :Nread \"http:\/\/[user@]machine\/path\"              uses http  uses wget\r\n        :Nread \"rcp:\/\/[user@]machine\/path\"               uses rcp\r\n        :Nread \"rsync:\/\/[user@]machine[:port]\/path\"   uses rsync\r\n        :Nread \"scp:\/\/[user@]machine[[:#]port]\/path\"  uses scp\r\n        :Nread \"sftp:\/\/[user@]machine\/path\"             uses sftp\r\n\r\n    REMOTE WRITING\r\n        :Nwrite ?                                                      give help\r\n        :Nwrite \"machine:path\"                                  uses rcp\r\n        :Nwrite \"machine path\"                                  uses ftp   with <.netrc>\r\n        :Nwrite \"machine id password path\"               uses ftp\r\n        :Nwrite \"dav:\/\/machine[:port]\/path\"                  uses cadaver\r\n        :Nwrite \"ftp:\/\/[user@]machine[[:#]port]\/path\"     uses ftp   autodetects <.netrc>\r\n        :Nwrite \"rcp:\/\/[user@]machine\/path\"                uses rcp\r\n        :Nwrite \"rsync:\/\/[user@]machine[:port]\/path\"    uses rsync\r\n        :Nwrite \"scp:\/\/[user@]machine[[:#]port]\/path\"   uses scp\r\n        :Nwrite \"sftp:\/\/[user@]machine\/path\"               uses sftp\r\n        http: not supported!\r\n\r\n    REMOTE DIRECTORY BROWSING\r\n        :e [protocol]:\/\/[user]@hostname\/path\/\r\n        :Nread [protocol]:\/\/[user]@hostname\/path\/\r\n\r\n    LOCAL DIRECTORY BROWSING\r\n        :e \/some\/path\/to\/a\/directory\r\n\r\nNetrw supports browsing both local and remote directories.  For remote directory browsing, one must include a trailing slash (\/) on the path!  The interface resembles the file explorer that comes with vim v6.3 and earlier.  Variables which control netrw's optional behavior are named differently, however.\r\n\r\nFor remote directory browsing, the [protocol]:\/\/[user]@hostname\/path\/ is user-directory relative.  If you want to specify a full path, use another slash before the path: [protocol]:\/\/[user]@hostname\/\/path\/.\r\n\r\nNetrw supports many file-explorer maps, such as o v d D etc.  Look at the help for netrw-o, for example.  One may also use :Explore and relatives to explore directories with the current file.\r\n\r\nThe netrw.vba.gz vimball supports the \"x\" key to execute a file handler for various filetypes.  The file-handling is done in various ways:\r\n\r\n    * Under Windows, rundll32 is used with the FileProtocolHandler\r\n    * If unix and kfmclient exists and is executable, it is used\r\n    * If unix and gnome-open exists and is executable, it is used\r\n    * Otherwise, the NetrwFileHandler.vim file handling script is used\r\n\r\nWith this feature, one may press the \"x\" key when the cursor is atop a filename and invoke an extension-based file handler to do things like display image files, invoke ghostscript on PostScript files, run OpenOffice or Word, etc.\r\n\r\nRECENT NETRWs REQUIRE VIM V7.2\r\n\r\n(alpha\/beta version available at http:\/\/www.drchip.org\/astronaut\/vim\/index.html#NETRW)\r\n","install_details":"netrw is now distributed as a vimball!  (see :help vimball)\r\nYou'll need a vimball plugin v18 or later (see vimscript#1502).\r\n(if you have vim 7.1a or later, you probably can skip this step)\r\n\r\n(if you're updating from the vim 7.0 distribution, please remove all runtime plugin\/netrw*.vim and autoload\/netrw*.vim first)\r\n\r\nvim netrw.vba.gz\r\n:so %\r\n:q\r\n\r\nand that's it!","5":"netrw is now distributed as a vimball!  (see :help vimball)\r\nYou'll need a vimball plugin v18 or later (see vimscript#1502).\r\n(if you have vim 7.1a or later, you probably can skip this step)\r\n\r\n(if you're updating from the vim 7.0 distribution, please remove all runtime plugin\/netrw*.vim and autoload\/netrw*.vim first)\r\n\r\nvim netrw.vba.gz\r\n:so %\r\n:q\r\n\r\nand that's it!","first_name":"Charles","6":"Charles","last_name":"Campbell","7":"Campbell","releases":[{"0":"1075","vim_version":"7.3","1":"7.3","script_version":"150","2":"150","version_comment":":Lexplore : toggles a netrw Explorer window on the left hand side of the display -\r\ns-leftmouse : may be used to mark files -\r\nfor cygwin: g:netrw_cygdrive can be used to override default \"\/cygdrive\" -\r\n:Ntree : use this command to change the treetop in tree-style listings -\r\nMany bug fixes.","3":":Lexplore : toggles a netrw Explorer window on the left hand side of the display -\r\ns-leftmouse : may be used to mark files -\r\nfor cygwin: g:netrw_cygdrive can be used to override default \"\/cygdrive\" -\r\n:Ntree : use this command to change the treetop in tree-style listings -\r\nMany bug fixes.","package":"netrw.vba.gz","4":"netrw.vba.gz","src_id":"21427","5":"21427","creation_date":"1391533021","6":"1391533021"},{"0":"1075","vim_version":"7.0","1":"7.0","script_version":"147","2":"147","version_comment":"More ways to choose targets for moving\/copying files: a \"Targets\" entry for menus, [count]Th for count-th history, [count]Tb for count-th bookmark; u and U maps now take counts.   Various bug fixes (two fixes for windows users, for example).","3":"More ways to choose targets for moving\/copying files: a \"Targets\" entry for menus, [count]Th for count-th history, [count]Tb for count-th bookmark; u and U maps now take counts.   Various bug fixes (two fixes for windows users, for example).","package":"netrw.vba.gz","4":"netrw.vba.gz","src_id":"19823","5":"19823","creation_date":"1366119651","6":"1366119651"},{"0":"1075","vim_version":"7.3","1":"7.3","script_version":"142","2":"142","version_comment":"g:netrw_winsize's meaning changed!  Now describes percentage of current netrw buffer window to be used for the new window.\r\nBug fix: NetrwRemoteListing() uses shellescape to handle subdirectories having spaces.\r\nBug fix: NetrwMethod() attempts to issue an error message when given a malformed url\r\n","3":"g:netrw_winsize's meaning changed!  Now describes percentage of current netrw buffer window to be used for the new window.\r\nBug fix: NetrwRemoteListing() uses shellescape to handle subdirectories having spaces.\r\nBug fix: NetrwMethod() attempts to issue an error message when given a malformed url\r\n","package":"netrw.vba.gz","4":"netrw.vba.gz","src_id":"15782","5":"15782","creation_date":"1306873504","6":"1306873504"},{"0":"1075","vim_version":"7.3","1":"7.3","script_version":"141","2":"141","version_comment":"included -s:... support for Windows ftp\r\nrestored 2-leftmouse for :Rex-like return\r\nadded balloon help for items in banner\r\ng:netrw_cursor (g:netrw_cursorcolumn is deprecated) supports additional argument values for cursorline and cursorcolumn control in netrw directory listings.\r\n:Texplore starts from netrw's idea of the current directory rather than pwd's\r\n","3":"included -s:... support for Windows ftp\r\nrestored 2-leftmouse for :Rex-like return\r\nadded balloon help for items in banner\r\ng:netrw_cursor (g:netrw_cursorcolumn is deprecated) supports additional argument values for cursorline and cursorcolumn control in netrw directory listings.\r\n:Texplore starts from netrw's idea of the current directory rather than pwd's\r\n","package":"netrw.vba.gz","4":"netrw.vba.gz","src_id":"15352","5":"15352","creation_date":"1301672022","6":"1301672022"},{"0":"1075","vim_version":"7.0","1":"7.0","script_version":"136","2":"136","version_comment":"This one is mostly a bugfix release.  There's also\r\nT:  (a new map)  puts the file or directory into a background tab\r\nelinks now uses -source instead of -dump\r\n","3":"This one is mostly a bugfix release.  There's also\r\nT:  (a new map)  puts the file or directory into a background tab\r\nelinks now uses -source instead of -dump\r\n","package":"netrw.vba.gz","4":"netrw.vba.gz","src_id":"11979","5":"11979","creation_date":"1262102461","6":"1262102461"},{"0":"1075","vim_version":"7.0","1":"7.0","script_version":"135","2":"135","version_comment":"A bugfix release -- see  :he netrw-history  -- ","3":"A bugfix release -- see  :he netrw-history  -- ","package":"netrw.vba.gz","4":"netrw.vba.gz","src_id":"9816","5":"9816","creation_date":"1231956291","6":"1231956291"},{"0":"1075","vim_version":"7.0","1":"7.0","script_version":"134","2":"134","version_comment":"* dav: will use curl if cadaver isn't available\r\n* [N] added to various Explore commands\r\n* bookmarks should now reliably be retained\r\n* various bugfixes (x for remote jpgs, for example)\r\n","3":"* dav: will use curl if cadaver isn't available\r\n* [N] added to various Explore commands\r\n* bookmarks should now reliably be retained\r\n* various bugfixes (x for remote jpgs, for example)\r\n","package":"netrw.vba.gz","4":"netrw.vba.gz","src_id":"9389","5":"9389","creation_date":"1224776557","6":"1224776557"},{"0":"1075","vim_version":"7.0","1":"7.0","script_version":"133","2":"133","version_comment":"[*] security improvements (you'll need vim 7.2 for this version)\r\n[*] uses cursorline for thin\/long\/tree listing styles\r\n[*] currently trying elinks for http -- comments, please!  I have one dislike so far, so it may be changed back in the future.\r\n[*] various bug fixes\r\n","3":"[*] security improvements (you'll need vim 7.2 for this version)\r\n[*] uses cursorline for thin\/long\/tree listing styles\r\n[*] currently trying elinks for http -- comments, please!  I have one dislike so far, so it may be changed back in the future.\r\n[*] various bug fixes\r\n","package":"netrw.vba.gz","4":"netrw.vba.gz","src_id":"9221","5":"9221","creation_date":"1220424503","6":"1220424503"},{"0":"1075","vim_version":"7.0","1":"7.0","script_version":"v128","2":"v128","version_comment":"Needs fnameescape() and shellescape(), so you'll need an up-to-date vim with this one: vim v7.2b or later.\r\n","3":"Needs fnameescape() and shellescape(), so you'll need an up-to-date vim with this one: vim v7.2b or later.\r\n","package":"netrw.vba.gz","4":"netrw.vba.gz","src_id":"9048","5":"9048","creation_date":"1217424769","6":"1217424769"},{"0":"1075","vim_version":"7.0","1":"7.0","script_version":"123","2":"123","version_comment":"Marked files now keeps a \"global\" marked file list.  The global marked file list is used to support tag processing and vimdiff'ing.\r\nSeveral bugs fixed and security enhancements.\r\n","3":"Marked files now keeps a \"global\" marked file list.  The global marked file list is used to support tag processing and vimdiff'ing.\r\nSeveral bugs fixed and security enhancements.\r\n","package":"netrw.vba.gz","4":"netrw.vba.gz","src_id":"8501","5":"8501","creation_date":"1206705510","6":"1206705510"},{"0":"1075","vim_version":"7.0","1":"7.0","script_version":"122","2":"122","version_comment":"Mainly a bugfix release (sorting sequence improvements).","3":"Mainly a bugfix release (sorting sequence improvements).","package":"netrw.vba.gz","4":"netrw.vba.gz","src_id":"8351","5":"8351","creation_date":"1204012847","6":"1204012847"},{"0":"1075","vim_version":"7.0","1":"7.0","script_version":"121","2":"121","version_comment":"Bugfixes: netrw attempts to retain the alternate file.  v120 broke an explicit :Explore dirname ; fixed.\r\n","3":"Bugfixes: netrw attempts to retain the alternate file.  v120 broke an explicit :Explore dirname ; fixed.\r\n","package":"netrw.vba.gz","4":"netrw.vba.gz","src_id":"8262","5":"8262","creation_date":"1202809119","6":"1202809119"},{"0":"1075","vim_version":"7.0","1":"7.0","script_version":"120","2":"120","version_comment":"Marked file system extended (mt, mh, mu, ms) and bugs removed.  One may now have multiple tree listings.  Bugfix: P works with trees.  Changed q -> qb for query-bookmarks, qf added to provide information about file under cursor.  Explore now has four special listing modes: *\/filepat, *\/\/filepat, **\/pattern, and **\/\/pattern.  gh is now a shortcut for toggling hiding of files and directories which begin with a dot.  The menu now includes entries for Explore.\r\n","3":"Marked file system extended (mt, mh, mu, ms) and bugs removed.  One may now have multiple tree listings.  Bugfix: P works with trees.  Changed q -> qb for query-bookmarks, qf added to provide information about file under cursor.  Explore now has four special listing modes: *\/filepat, *\/\/filepat, **\/pattern, and **\/\/pattern.  gh is now a shortcut for toggling hiding of files and directories which begin with a dot.  The menu now includes entries for Explore.\r\n","package":"netrw.vba.gz","4":"netrw.vba.gz","src_id":"8248","5":"8248","creation_date":"1202549836","6":"1202549836"},{"0":"1075","vim_version":"7.0","1":"7.0","script_version":"118","2":"118","version_comment":"Netrw has some bug fixes: with :Explore c:\/path\/, spaces in directory names with s:NetrwOptionRestore(), and with P\r\n","3":"Netrw has some bug fixes: with :Explore c:\/path\/, spaces in directory names with s:NetrwOptionRestore(), and with P\r\n","package":"netrw.vba.gz","4":"netrw.vba.gz","src_id":"8133","5":"8133","creation_date":"1199690871","6":"1199690871"},{"0":"1075","vim_version":"7.0","1":"7.0","script_version":"116","2":"116","version_comment":"bug fixes -- removed some unnecessary directory refreshes, and this version does a better job of retaining user options when editing files under the aegis of netrw's browser","3":"bug fixes -- removed some unnecessary directory refreshes, and this version does a better job of retaining user options when editing files under the aegis of netrw's browser","package":"netrw.vba.gz","4":"netrw.vba.gz","src_id":"8042","5":"8042","creation_date":"1197468455","6":"1197468455"},{"0":"1075","vim_version":"7.0","1":"7.0","script_version":"115","2":"115","version_comment":"* New: :Explore handles path\/**\/filename\r\n* Bugfixes: (shellslash use improved, remote editing of *.tar.gz and *.tar.bz2, sourcing remote files via ftp, etc)\r\n","3":"* New: :Explore handles path\/**\/filename\r\n* Bugfixes: (shellslash use improved, remote editing of *.tar.gz and *.tar.bz2, sourcing remote files via ftp, etc)\r\n","package":"netrw.vba.gz","4":"netrw.vba.gz","src_id":"7901","5":"7901","creation_date":"1194502878","6":"1194502878"},{"0":"1075","vim_version":"7.0","1":"7.0","script_version":"114","2":"114","version_comment":"mT now supports generating tags files for remote marked files\r\nNetrw's menus are New&Improved!","3":"mT now supports generating tags files for remote marked files\r\nNetrw's menus are New&Improved!","package":"netrw.vba.gz","4":"netrw.vba.gz","src_id":"7738","5":"7738","creation_date":"1191309598","6":"1191309598"},{"0":"1075","vim_version":"7.0","1":"7.0","script_version":"113","2":"113","version_comment":"New: the \"x\" command has been extended to use Mac OS\/X's open facility\r\n\r\nBugfix: cursor position restored after deleting or renaming files\r\nBugfix: ftplugins, autocmds, etc can change settings after netrw opens a file\r\nBugfix: strlen() -> s:Strlen(), which handles utf-8 characters better\r\n","3":"New: the \"x\" command has been extended to use Mac OS\/X's open facility\r\n\r\nBugfix: cursor position restored after deleting or renaming files\r\nBugfix: ftplugins, autocmds, etc can change settings after netrw opens a file\r\nBugfix: strlen() -> s:Strlen(), which handles utf-8 characters better\r\n","package":"netrw.vba.gz","4":"netrw.vba.gz","src_id":"7725","5":"7725","creation_date":"1190902003","6":"1190902003"},{"0":"1075","vim_version":"7.0","1":"7.0","script_version":"112","2":"112","version_comment":"Added mx (|netrw-mx|) for executing arbitrary commands on marked files\r\nAdded the :NetrwClean[!] command\r\nBugfix: More option save\/restore work for s:NetrwBrowseChgDir(); s:NetrwOptionSave() and s:NetrwOptionRestore() now take a parameter specifying the type of variables to be used for saving and restoring (either \"w:\" or \"s:\").  The formatoptions, for example, is saved & restored.\r\n","3":"Added mx (|netrw-mx|) for executing arbitrary commands on marked files\r\nAdded the :NetrwClean[!] command\r\nBugfix: More option save\/restore work for s:NetrwBrowseChgDir(); s:NetrwOptionSave() and s:NetrwOptionRestore() now take a parameter specifying the type of variables to be used for saving and restoring (either \"w:\" or \"s:\").  The formatoptions, for example, is saved & restored.\r\n","package":"netrw.vba.gz","4":"netrw.vba.gz","src_id":"7617","5":"7617","creation_date":"1188901577","6":"1188901577"},{"0":"1075","vim_version":"7.0","1":"7.0","script_version":"111","2":"111","version_comment":"Included a \"marked file\" system: one may mark files (with mf or shift-leftmouse); one may then rename, delete, obtain, compress\/decompress, and create tags with the marked files.\r\n\r\nA double-clicked leftmouse (in gvim) will return one from a file to the netrw browser buffer used to edit it.\r\n\r\nAnd, some bug fixes!\r\n","3":"Included a \"marked file\" system: one may mark files (with mf or shift-leftmouse); one may then rename, delete, obtain, compress\/decompress, and create tags with the marked files.\r\n\r\nA double-clicked leftmouse (in gvim) will return one from a file to the netrw browser buffer used to edit it.\r\n\r\nAnd, some bug fixes!\r\n","package":"netrw.vba.gz","4":"netrw.vba.gz","src_id":"7503","5":"7503","creation_date":"1187175900","6":"1187175900"},{"0":"1075","vim_version":"7.0","1":"7.0","script_version":"110","2":"110","version_comment":"New Features:\r\n* added [ and ] maps to NetrwTreeListing (bounce across open directories)\r\n* preview window may be shown vertically as well as the default horizontally\r\n\r\nBug Fixes:\r\n* g:netrw_shq more consistently used to support \"x\" for special file browsing\r\n* more [Scratch] buffers are now named properly\r\n* c mapping now works when directory names have spaces\r\n* options retained in original buffers after a split + :Explore\r\n* Fixed remote file deletion\/renaming (again)\r\n* Using <leftmouse to a non-netrw window was causing an error message\r\n","3":"New Features:\r\n* added [ and ] maps to NetrwTreeListing (bounce across open directories)\r\n* preview window may be shown vertically as well as the default horizontally\r\n\r\nBug Fixes:\r\n* g:netrw_shq more consistently used to support \"x\" for special file browsing\r\n* more [Scratch] buffers are now named properly\r\n* c mapping now works when directory names have spaces\r\n* options retained in original buffers after a split + :Explore\r\n* Fixed remote file deletion\/renaming (again)\r\n* Using <leftmouse to a non-netrw window was causing an error message\r\n","package":"netrw.vba.gz","4":"netrw.vba.gz","src_id":"7273","5":"7273","creation_date":"1182353796","6":"1182353796"},{"0":"1075","vim_version":"7.0","1":"7.0","script_version":"109","2":"109","version_comment":"One may select an error\/message window vs echoerr messages\r\nVarious bug fixes (scp -P and ssh -p for ports, Explore attempts to expand $name)\r\n","3":"One may select an error\/message window vs echoerr messages\r\nVarious bug fixes (scp -P and ssh -p for ports, Explore attempts to expand $name)\r\n","package":"netrw.vba.gz","4":"netrw.vba.gz","src_id":"7079","5":"7079","creation_date":"1178622189","6":"1178622189"},{"0":"1075","vim_version":"7.0","1":"7.0","script_version":"108","2":"108","version_comment":"Netrw now supports sourcing remote files and supports preview (with a \"p\").  Numerous bug fixes.  Works with Microsoft-based ftp servers.","3":"Netrw now supports sourcing remote files and supports preview (with a \"p\").  Numerous bug fixes.  Works with Microsoft-based ftp servers.","package":"netrw.vba.gz","4":"netrw.vba.gz","src_id":"6895","5":"6895","creation_date":"1174458931","6":"1174458931"},{"0":"1075","vim_version":"7.0","1":"7.0","script_version":"107","2":"107","version_comment":"(browser) tree display mode\r\n(browser) amiga supported\r\nnumerous bug fixes","3":"(browser) tree display mode\r\n(browser) amiga supported\r\nnumerous bug fixes","package":"netrw.vba.gz","4":"netrw.vba.gz","src_id":"6577","5":"6577","creation_date":"1167805940","6":"1167805940"},{"0":"1075","vim_version":"7.0","1":"7.0","script_version":"104","2":"104","version_comment":"* NEW: netrw now has a tree listing style (see :help g:netrw_liststyle)\r\n* MOD: as suggested by Rodolfo Borges, :Explore and variants will position the cursor on the file that had just been edited\r\n* MOD: changed default g:netrw_sort_sequence order\r\n* MOD: changed b, Nb to simply mb  (make bookmark)\r\n* MOD: changed B, NB to simply gb  (goto bookmark)\r\n* MOD: attempts to retain the alternate file\r\n","3":"* NEW: netrw now has a tree listing style (see :help g:netrw_liststyle)\r\n* MOD: as suggested by Rodolfo Borges, :Explore and variants will position the cursor on the file that had just been edited\r\n* MOD: changed default g:netrw_sort_sequence order\r\n* MOD: changed b, Nb to simply mb  (make bookmark)\r\n* MOD: changed B, NB to simply gb  (goto bookmark)\r\n* MOD: attempts to retain the alternate file\r\n","package":"netrw.vba.gz","4":"netrw.vba.gz","src_id":"6180","5":"6180","creation_date":"1158241836","6":"1158241836"},{"0":"1075","vim_version":"7.0","1":"7.0","script_version":"103","2":"103","version_comment":"\"t\" now opens tabbed windows for the file under the cursor, plus numerous bug fixes!\r\n","3":"\"t\" now opens tabbed windows for the file under the cursor, plus numerous bug fixes!\r\n","package":"netrw.vba.gz","4":"netrw.vba.gz","src_id":"6119","5":"6119","creation_date":"1157014788","6":"1157014788"},{"0":"1075","vim_version":"6.0","1":"6.0","script_version":"102","2":"102","version_comment":"new stuff: g:netrw_menu support included; :Texplore command implemented; <leftmouse> acts as a <cr> for selecting a file; <rightmouse> acts as a <del> for deleting a file\r\nbugfixes : g:netrw_keepdir==0 had stopped working; NetOptionSave\/Restore now saves\/restores the unnamed register; NetSplit and (Local,Net)BrowseChgDir() were both splitting windows.  This affected o, v, and g:netrw_browse_split; works around wildignore setting\r\n","3":"new stuff: g:netrw_menu support included; :Texplore command implemented; <leftmouse> acts as a <cr> for selecting a file; <rightmouse> acts as a <del> for deleting a file\r\nbugfixes : g:netrw_keepdir==0 had stopped working; NetOptionSave\/Restore now saves\/restores the unnamed register; NetSplit and (Local,Net)BrowseChgDir() were both splitting windows.  This affected o, v, and g:netrw_browse_split; works around wildignore setting\r\n","package":"netrw.vba.gz","4":"netrw.vba.gz","src_id":"5982","5":"5982","creation_date":"1153732888","6":"1153732888"},{"0":"1075","vim_version":"7.0","1":"7.0","script_version":"100","2":"100","version_comment":"- numerous bug fixes addressing problems with Windows lacking cygwin\r\n- user NFH_*() functions were being unused inadvertently\r\n- [NP]Explore *\/pat and **\/\/pat now wrap\r\n- Bookmarks and History added to menu\r\n- g:netrw_shq has a better default, and is tunable by the user\r\n- bugfix: hiding pattern candidate separators included some characters it shouldn't have (tnx to Osei Poku)\r\n","3":"- numerous bug fixes addressing problems with Windows lacking cygwin\r\n- user NFH_*() functions were being unused inadvertently\r\n- [NP]Explore *\/pat and **\/\/pat now wrap\r\n- Bookmarks and History added to menu\r\n- g:netrw_shq has a better default, and is tunable by the user\r\n- bugfix: hiding pattern candidate separators included some characters it shouldn't have (tnx to Osei Poku)\r\n","package":"netrw.vba.gz","4":"netrw.vba.gz","src_id":"5814","5":"5814","creation_date":"1149757198","6":"1149757198"},{"0":"1075","vim_version":"7.0","1":"7.0","script_version":"99","2":"99","version_comment":"Since the vim 7.0 release:\r\n  g:netrw_browse_split=3 for opening files in new tabs implemented.\r\n  deletes temporary file at end of NetRead()\r\n  visual mode based Obtain implemented for remote systems.\r\n added -complete=dir to the various Explore commands\r\n\r\n  \r\n  \r\n  \r\n","3":"Since the vim 7.0 release:\r\n  g:netrw_browse_split=3 for opening files in new tabs implemented.\r\n  deletes temporary file at end of NetRead()\r\n  visual mode based Obtain implemented for remote systems.\r\n added -complete=dir to the various Explore commands\r\n\r\n  \r\n  \r\n  \r\n","package":"netrw.vba.gz","4":"netrw.vba.gz","src_id":"5682","5":"5682","creation_date":"1147440065","6":"1147440065"},{"0":"1075","vim_version":"7.0","1":"7.0","script_version":"93","2":"93","version_comment":":Explore *\/pattern implemented - search for files containing a pattern in the current directory\r\n:Explore **\/\/pattern implemented - search for files containing a pattern in the directory and subdirectories\r\nMoved DrChip.Netrw menu to a top-level Netrw menu, with priority 80\r\nbugfix - :Nexplore or :Pexplore, issued without first having done an Explore now gives an appropriate error message\r\nbugfix - removed FocusGained event from causing a slow-browser refresh for Windows\r\nbugfix - now handles spaces in filenames and directory names when using ftp-based browsing\r\n","3":":Explore *\/pattern implemented - search for files containing a pattern in the current directory\r\n:Explore **\/\/pattern implemented - search for files containing a pattern in the directory and subdirectories\r\nMoved DrChip.Netrw menu to a top-level Netrw menu, with priority 80\r\nbugfix - :Nexplore or :Pexplore, issued without first having done an Explore now gives an appropriate error message\r\nbugfix - removed FocusGained event from causing a slow-browser refresh for Windows\r\nbugfix - now handles spaces in filenames and directory names when using ftp-based browsing\r\n","package":"netrw.vba.gz","4":"netrw.vba.gz","src_id":"5607","5":"5607","creation_date":"1145948316","6":"1145948316"},{"0":"1075","vim_version":"6.0","1":"6.0","script_version":"81","2":"81","version_comment":"ShellCmdPost and FocusGained used to refresh local browser directory listings when g:netrw_fastmode <= 1.\r\n","3":"ShellCmdPost and FocusGained used to refresh local browser directory listings when g:netrw_fastmode <= 1.\r\n","package":"netrw.tar.gz","4":"netrw.tar.gz","src_id":"5439","5":"5439","creation_date":"1142419427","6":"1142419427"},{"0":"1075","vim_version":"7.0","1":"7.0","script_version":"79","2":"79","version_comment":"* directories now displayed with nowrap\r\n* g:netrw_fastbrowse introduced, allows for control of speed vs always-obtain directory listing\r\n* bugfix with wide listing, column width < largest filename hangup\r\n* semi-colons should now work with temporary files\r\n","3":"* directories now displayed with nowrap\r\n* g:netrw_fastbrowse introduced, allows for control of speed vs always-obtain directory listing\r\n* bugfix with wide listing, column width < largest filename hangup\r\n* semi-colons should now work with temporary files\r\n","package":"netrw.tar.gz","4":"netrw.tar.gz","src_id":"5395","5":"5395","creation_date":"1141893619","6":"1141893619"},{"0":"1075","vim_version":"6.0","1":"6.0","script_version":"77","2":"77","version_comment":"New stuff!\r\ng:netrw_browsex_viewer implemented.  NetBrowseX does better at figuring out whether KDE or gnome is actually being used.\r\nUse the \"P\" map to edit a file\/directory in the previously used window (like Explorer's O)\r\nUse g:netrw_browse_split to specify horizontal\/vertical splitting of the window when editing a file from a browser window\r\nSome bugfixes, too!\r\n","3":"New stuff!\r\ng:netrw_browsex_viewer implemented.  NetBrowseX does better at figuring out whether KDE or gnome is actually being used.\r\nUse the \"P\" map to edit a file\/directory in the previously used window (like Explorer's O)\r\nUse g:netrw_browse_split to specify horizontal\/vertical splitting of the window when editing a file from a browser window\r\nSome bugfixes, too!\r\n","package":"netrw.tar.gz","4":"netrw.tar.gz","src_id":"5004","5":"5004","creation_date":"1138258949","6":"1138258949"},{"0":"1075","vim_version":"6.0","1":"6.0","script_version":"74","2":"74","version_comment":"(vim v7.0 req'd)\r\n* Reads remote zip&tar files.\r\n* netrwSettings now uses autoloading\r\n* Many bugfixes (ctrl-L, ch==1 Hit-Enter, W95's E121, etc).\r\n* And more! (see :help netrw-history)\r\n","3":"(vim v7.0 req'd)\r\n* Reads remote zip&tar files.\r\n* netrwSettings now uses autoloading\r\n* Many bugfixes (ctrl-L, ch==1 Hit-Enter, W95's E121, etc).\r\n* And more! (see :help netrw-history)\r\n","package":"netrw.tar.gz","4":"netrw.tar.gz","src_id":"4683","5":"4683","creation_date":"1129705487","6":"1129705487"},{"0":"1075","vim_version":"6.0","1":"6.0","script_version":"68","2":"68","version_comment":"Netrw now takes advantage of autoload (and requires 7.0).\r\n\"i\" now cycles between thin, long, and wide listing styles.\r\n\"O\" now obtains a file: remote browsing file -> local copy.\r\nDouble-click-leftmouse selects word under mouse.\r\nNetrw now works around the report setting.\r\nPasswords which contain blanks will now be surrounded by double-quotes automatically.\r\nNetrw now seems to work with a few more Windows situations.\r\n","3":"Netrw now takes advantage of autoload (and requires 7.0).\r\n\"i\" now cycles between thin, long, and wide listing styles.\r\n\"O\" now obtains a file: remote browsing file -> local copy.\r\nDouble-click-leftmouse selects word under mouse.\r\nNetrw now works around the report setting.\r\nPasswords which contain blanks will now be surrounded by double-quotes automatically.\r\nNetrw now seems to work with a few more Windows situations.\r\n","package":"netrw.tar.gz","4":"netrw.tar.gz","src_id":"4545","5":"4545","creation_date":"1125562036","6":"1125562036"},{"0":"1075","vim_version":"6.0","1":"6.0","script_version":"62","2":"62","version_comment":"Document upgrade - :NetrwSettings command allows easy editing and review of all netrw variable settings\r\nBugfix - Concurrent Explore **\/pattern searches allowed\r\n\r\nLast vim 6.3 release (unless a major problem appears); future ones will be 7.0 only","3":"Document upgrade - :NetrwSettings command allows easy editing and review of all netrw variable settings\r\nBugfix - Concurrent Explore **\/pattern searches allowed\r\n\r\nLast vim 6.3 release (unless a major problem appears); future ones will be 7.0 only","package":"netrw.tar.gz","4":"netrw.tar.gz","src_id":"4495","5":"4495","creation_date":"1124093902","6":"1124093902"},{"0":"1075","vim_version":"6.0","1":"6.0","script_version":"60","2":"60","version_comment":"Vim 7.0 only:\r\n* \"Match # of #\" indicator for Explore **\/*.c\r\n* :Explore **\/*.c  will now work from a non-netrw-browser window\r\n* :Explore **\/patterns can now be run in separate browser windows\r\n\r\nVim6.3 and Vim7.0:\r\n* active banner (hitting <cr> in banner region will cause various things to happen)\r\n* bugfixes\r\n","3":"Vim 7.0 only:\r\n* \"Match # of #\" indicator for Explore **\/*.c\r\n* :Explore **\/*.c  will now work from a non-netrw-browser window\r\n* :Explore **\/patterns can now be run in separate browser windows\r\n\r\nVim6.3 and Vim7.0:\r\n* active banner (hitting <cr> in banner region will cause various things to happen)\r\n* bugfixes\r\n","package":"netrw.tar.gz","4":"netrw.tar.gz","src_id":"4486","5":"4486","creation_date":"1123746974","6":"1123746974"},{"0":"1075","vim_version":"6.0","1":"6.0","script_version":"58","2":"58","version_comment":"* Explore and relatives can now handle **\/pattern (v7)\r\n* Nexplore and Pexplore introduced (v7)\r\n* Various bugfixes\r\n","3":"* Explore and relatives can now handle **\/pattern (v7)\r\n* Nexplore and Pexplore introduced (v7)\r\n* Various bugfixes\r\n","package":"netrw.tar.gz","4":"netrw.tar.gz","src_id":"4461","5":"4461","creation_date":"1123246519","6":"1123246519"},{"0":"1075","vim_version":"6.0","1":"6.0","script_version":"56","2":"56","version_comment":"Netrw now avoids changing directory when g:netrw_keepdir is false\r\nNetrw's LocalBrowse() now bypasses the autochdir option\r\nNetrw now uses vim's rename() instead of system + local_rename variable\r\n-bar used with :Explore :Sexplore etc to allow multiple commands to be separated by bars\r\nbrowser listings now use the \"nowrap\" option\r\nbrowser: some unuseful error messages now suppressed\r\n\r\nIf you're using vim7, you need to have an up-to-date one supporting the sort command.","3":"Netrw now avoids changing directory when g:netrw_keepdir is false\r\nNetrw's LocalBrowse() now bypasses the autochdir option\r\nNetrw now uses vim's rename() instead of system + local_rename variable\r\n-bar used with :Explore :Sexplore etc to allow multiple commands to be separated by bars\r\nbrowser listings now use the \"nowrap\" option\r\nbrowser: some unuseful error messages now suppressed\r\n\r\nIf you're using vim7, you need to have an up-to-date one supporting the sort command.","package":"netrw.tar.gz","4":"netrw.tar.gz","src_id":"4453","5":"4453","creation_date":"1122889264","6":"1122889264"},{"0":"1075","vim_version":"6.0","1":"6.0","script_version":"54","2":"54","version_comment":"* <amatch> used instead of <afile> in the transparency support (BufReadCmd, FileReadCmd, FileWriteCmd)\r\n* For backwards compatibility, Explore and Sexplore have been implemented.  In addition, Hexplore and Vexplore commands are available, too.\r\n* ***netrw*** prepended to various error messages netrw may emit\r\n* g:netrw_port used instead of b:netrw_port for scp\r\n* any leading [:#] is removed from port numbers\r\n* backslashes as well as slashes placed in various patterns (ex. g:netrw_sort_sequence) to better support Windows\r\n","3":"* <amatch> used instead of <afile> in the transparency support (BufReadCmd, FileReadCmd, FileWriteCmd)\r\n* For backwards compatibility, Explore and Sexplore have been implemented.  In addition, Hexplore and Vexplore commands are available, too.\r\n* ***netrw*** prepended to various error messages netrw may emit\r\n* g:netrw_port used instead of b:netrw_port for scp\r\n* any leading [:#] is removed from port numbers\r\n* backslashes as well as slashes placed in various patterns (ex. g:netrw_sort_sequence) to better support Windows\r\n","package":"netrw.tar.gz","4":"netrw.tar.gz","src_id":"3986","5":"3986","creation_date":"1110373635","6":"1110373635"},{"0":"1075","vim_version":"6.0","1":"6.0","script_version":"51","2":"51","version_comment":"FileWriteCmd event used (supports :[range]w url) supports directory history stack, automatic cygwin use detected (windows), error messages remain visible, bug fixes\r\n","3":"FileWriteCmd event used (supports :[range]w url) supports directory history stack, automatic cygwin use detected (windows), error messages remain visible, bug fixes\r\n","package":"netrw.tar.gz","4":"netrw.tar.gz","src_id":"3533","5":"3533","creation_date":"1097239535","6":"1097239535"},{"0":"1075","vim_version":"6.0","1":"6.0","script_version":"48","2":"48","version_comment":"Many things (see :help netrw-history), including:\r\nremote browsing with ftp, bookmarks, nrml\/hide\/show, improved x, bugfixes, alt-o\/v, preview\r\n","3":"Many things (see :help netrw-history), including:\r\nremote browsing with ftp, bookmarks, nrml\/hide\/show, improved x, bugfixes, alt-o\/v, preview\r\n","package":"netrw.tar.gz","4":"netrw.tar.gz","src_id":"3440","5":"3440","creation_date":"1094814206","6":"1094814206"}]},"1074":{"script_id":"1074","0":"1074","script_name":"python_calltips","1":"python_calltips","script_type":"utility","2":"utility","summary":"Display Python code calltips and allows you to auto-complete your Python code","3":"Display Python code calltips and allows you to auto-complete your Python code","description":"This script simualate code calltips in a new bottow window of Vim.\r\nIn fact, it display python help doc strings of word under the cursor\r\nby scanning the imported modules in the current file.\r\nthis file Reference :    http:\/\/vim.sourceforge.net\/scripts\/script.php?script_id=73 \r\n\r\nNote: Because Python language is dynamic and the type of object is certain \r\n         when running, the calltips is only displayed for the part of all object.   \r\n\r\nIt require Python and Vim compiled with \"+python\" \r\nand MAKE SURE \"set iskeyword+=.\"\r\n    \r\nIt work well in my box in Win2000\/XP + Vim6.3 + python2.3. \r\nIt can also work in GNU\/Linux.\r\nNote: as I know, Vim6.2 come into conflict with Python2.3, becase Vim6.2\r\n         is compiled with Python2.1. you can update vim version to 6.3.\r\n        Maybe yours not.\r\n\r\nMore detail is in the header of script file. \r\n\r\nI write a tip(vimtip #778) about the script for all Pythoner. I wish you enjoy it.","4":"This script simualate code calltips in a new bottow window of Vim.\r\nIn fact, it display python help doc strings of word under the cursor\r\nby scanning the imported modules in the current file.\r\nthis file Reference :    http:\/\/vim.sourceforge.net\/scripts\/script.php?script_id=73 \r\n\r\nNote: Because Python language is dynamic and the type of object is certain \r\n         when running, the calltips is only displayed for the part of all object.   \r\n\r\nIt require Python and Vim compiled with \"+python\" \r\nand MAKE SURE \"set iskeyword+=.\"\r\n    \r\nIt work well in my box in Win2000\/XP + Vim6.3 + python2.3. \r\nIt can also work in GNU\/Linux.\r\nNote: as I know, Vim6.2 come into conflict with Python2.3, becase Vim6.2\r\n         is compiled with Python2.1. you can update vim version to 6.3.\r\n        Maybe yours not.\r\n\r\nMore detail is in the header of script file. \r\n\r\nI write a tip(vimtip #778) about the script for all Pythoner. I wish you enjoy it.","install_details":"Put the plugin into \"$VIMRUNTIME\/ftplugin\" folder\r\n","5":"Put the plugin into \"$VIMRUNTIME\/ftplugin\" folder\r\n","first_name":"tocer","6":"tocer","last_name":"deng","7":"deng","releases":[{"0":"1074","vim_version":"6.0","1":"6.0","script_version":"1.01","2":"1.01","version_comment":"Nothing to do except IGNORE a exception when press '.' key in a string","3":"Nothing to do except IGNORE a exception when press '.' key in a string","package":"python_calltips.vim","4":"python_calltips.vim","src_id":"4287","5":"4287","creation_date":"1116297972","6":"1116297972"},{"0":"1074","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Change:\r\n1.get rid of  F4 key. You can get tips without any extral keys\r\n2.support multi buffers\r\n3.hightlight calltips syntax..\r\nThank Staale flock and Levin Du help","3":"Change:\r\n1.get rid of  F4 key. You can get tips without any extral keys\r\n2.support multi buffers\r\n3.hightlight calltips syntax..\r\nThank Staale flock and Levin Du help","package":"python_calltips.vim","4":"python_calltips.vim","src_id":"3620","5":"3620","creation_date":"1100151779","6":"1100151779"},{"0":"1074","vim_version":"6.0","1":"6.0","script_version":"0.85","2":"0.85","version_comment":"Fix  the  clash with winmanager.vim and  minibufexpl.vim   plugin.\r\nThanks Staale Flock","3":"Fix  the  clash with winmanager.vim and  minibufexpl.vim   plugin.\r\nThanks Staale Flock","package":"python_calltips.vim","4":"python_calltips.vim","src_id":"3573","5":"3573","creation_date":"1098669545","6":"1098669545"},{"0":"1074","vim_version":"6.0","1":"6.0","script_version":"0.8","2":"0.8","version_comment":"Snapshot in Linux","3":"Snapshot in Linux","package":"calltips-linux.png","4":"calltips-linux.png","src_id":"3474","5":"3474","creation_date":"1095900979","6":"1095900979"},{"0":"1074","vim_version":"6.0","1":"6.0","script_version":"0.8","2":"0.8","version_comment":"Snapshot in win2000","3":"Snapshot in win2000","package":"calltips-windows.gif","4":"calltips-windows.gif","src_id":"3473","5":"3473","creation_date":"1095900933","6":"1095900933"},{"0":"1074","vim_version":"6.0","1":"6.0","script_version":"0.8","2":"0.8","version_comment":"1.Rewrap the plugin, and change name to python_calltips.vim. In version 0.8, the plugin don't run automatically \r\n\r\n2.Add two function to start or end the plugin. You can run function \r\n  :call DoCalltips()        #start running \r\n  :call EndCalltips()       #end running \r\n\r\n3.if you use gVim, you can click  menu to start or end it in \"Tools\" menu :  \"Start Calltips\" and \"End Calltips\"","3":"1.Rewrap the plugin, and change name to python_calltips.vim. In version 0.8, the plugin don't run automatically \r\n\r\n2.Add two function to start or end the plugin. You can run function \r\n  :call DoCalltips()        #start running \r\n  :call EndCalltips()       #end running \r\n\r\n3.if you use gVim, you can click  menu to start or end it in \"Tools\" menu :  \"Start Calltips\" and \"End Calltips\"","package":"python_calltips.vim","4":"python_calltips.vim","src_id":"3470","5":"3470","creation_date":"1095892220","6":"1095892220"},{"0":"1074","vim_version":"6.0","1":"6.0","script_version":"0.7","2":"0.7","version_comment":"1.More variable can be display calltips.\r\n2.Refresh automatically if you don't press key until 5s in \"Nomal\" mode","3":"1.More variable can be display calltips.\r\n2.Refresh automatically if you don't press key until 5s in \"Nomal\" mode","package":"pyCallTips.py","4":"pyCallTips.py","src_id":"3445","5":"3445","creation_date":"1095013803","6":"1095013803"},{"0":"1074","vim_version":"6.0","1":"6.0","script_version":"0.6","2":"0.6","version_comment":"1.add \"CT_unmapkeys()\" and \"CT_mapkeys()\" function\r\n2.add calltips of buitin types such as string, list, dictionay, file\r\n3.thank Guilherme Salgado. He fix a bug in linux, and I know the script work well in linux","3":"1.add \"CT_unmapkeys()\" and \"CT_mapkeys()\" function\r\n2.add calltips of buitin types such as string, list, dictionay, file\r\n3.thank Guilherme Salgado. He fix a bug in linux, and I know the script work well in linux","package":"pyCallTips.py","4":"pyCallTips.py","src_id":"3427","5":"3427","creation_date":"1094348273","6":"1094348273"},{"0":"1074","vim_version":"6.0","1":"6.0","script_version":"0.5","2":"0.5","version_comment":"Congratulate China win 32 gold medal in Olympiad Game.\r\nand thanks montumba, without his help, I can't release 0.5 so quickly.","3":"Congratulate China win 32 gold medal in Olympiad Game.\r\nand thanks montumba, without his help, I can't release 0.5 so quickly.","package":"pyCallTips.py","4":"pyCallTips.py","src_id":"3397","5":"3397","creation_date":"1093826616","6":"1093826616"},{"0":"1074","vim_version":"6.0","1":"6.0","script_version":"0.3","2":"0.3","version_comment":"add builtin function","3":"add builtin function","package":"pyCallTips.py","4":"pyCallTips.py","src_id":"3396","5":"3396","creation_date":"1093641012","6":"1093641012"}]},"1073":{"script_id":"1073","0":"1073","script_name":"fasm compiler","1":"fasm compiler","script_type":"ftplugin","2":"ftplugin","summary":"a compiler script for Fasm","3":"a compiler script for Fasm","description":"A compiler script for Flat Assembler with a workable errorformat.","4":"A compiler script for Flat Assembler with a workable errorformat.","install_details":"put it in your  ~\/.vim\/compiler (unix)  or \r\n$vim\/vimfiles\/compiler (win32) directory. ","5":"put it in your  ~\/.vim\/compiler (unix)  or \r\n$vim\/vimfiles\/compiler (win32) directory. ","first_name":"6","6":"6","last_name":"+","7":"+","releases":[{"0":"1073","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"fasm.vim","4":"fasm.vim","src_id":"3390","5":"3390","creation_date":"1093549667","6":"1093549667"}]},"1072":{"script_id":"1072","0":"1072","script_name":"ConfirmQuit.vim","1":"ConfirmQuit.vim","script_type":"utility","2":"utility","summary":"Provides a confirm dialog when you try to quit vim","3":"Provides a confirm dialog when you try to quit vim","description":"A friend of mine was complaining that he closed vim unintentionally too often and wanted some sort of \"Are you sure?\" type of confirmation.  Thus, I wrote this plugin which will cause you to be prompted to confirm your desire to quit when you execute :q, :x, or :qw.\r\n\r\nNOTE:  This plugin requires graphical vim.","4":"A friend of mine was complaining that he closed vim unintentionally too often and wanted some sort of \"Are you sure?\" type of confirmation.  Thus, I wrote this plugin which will cause you to be prompted to confirm your desire to quit when you execute :q, :x, or :qw.\r\n\r\nNOTE:  This plugin requires graphical vim.","install_details":"Stick confirmQuit.vim in your plugin directory.  See \":help plugin\" in vim for more information.","5":"Stick confirmQuit.vim in your plugin directory.  See \":help plugin\" in vim for more information.","first_name":"Leif","6":"Leif","last_name":"Wickland","7":"Wickland","releases":[{"0":"1072","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"confirmQuit.vim","4":"confirmQuit.vim","src_id":"3389","5":"3389","creation_date":"1093538201","6":"1093538201"}]},"1071":{"script_id":"1071","0":"1071","script_name":"BufOnly.vim","1":"BufOnly.vim","script_type":"utility","2":"utility","summary":"Delete all the buffers except the current\/named buffer","3":"Delete all the buffers except the current\/named buffer","description":":BufOnly without an argument will unload all buffers but the current one.\r\n\r\n:BufOnly with an argument will close all buffers but the supplied buffer name\/number.","4":":BufOnly without an argument will unload all buffers but the current one.\r\n\r\n:BufOnly with an argument will close all buffers but the supplied buffer name\/number.","install_details":"Either :source it or put it in your plugin directory.","5":"Either :source it or put it in your plugin directory.","first_name":"Christian J.","6":"Christian J.","last_name":"Robinson","7":"Robinson","releases":[{"0":"1071","vim_version":"9.0","1":"9.0","script_version":"0.2","2":"0.2","version_comment":"- Update for Vim 9 (no features added)","3":"- Update for Vim 9 (no features added)","package":"BufOnly.vim","4":"BufOnly.vim","src_id":"28140","5":"28140","creation_date":"1661151448","6":"1661151448"},{"0":"1071","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"BufOnly.vim","4":"BufOnly.vim","src_id":"3388","5":"3388","creation_date":"1093517485","6":"1093517485"}]},"1070":{"script_id":"1070","0":"1070","script_name":"dsPIC30f","1":"dsPIC30f","script_type":"syntax","2":"syntax","summary":"dsPIC30f syntax file","3":"dsPIC30f syntax file","description":"As many new instructions were added for the PIC30f microcontrollers, this the new syntax file for PIC assembly language.","4":"As many new instructions were added for the PIC30f microcontrollers, this the new syntax file for PIC assembly language.","install_details":"","5":"","first_name":"yves","6":"yves","last_name":"kerleguer","7":"kerleguer","releases":[{"0":"1070","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"pic30f.vim","4":"pic30f.vim","src_id":"3387","5":"3387","creation_date":"1093504914","6":"1093504914"}]},"1069":{"script_id":"1069","0":"1069","script_name":"vimsh","1":"vimsh","script_type":"indent","2":"indent","summary":"simple Vim script shell command line interpreters","3":"simple Vim script shell command line interpreters","description":"vimsh and vimsh.bat are simple Vim script shell command line interpreters\r\nfor  UNIX and MSDOS respectively.  You type Vim script code into a .vimsh\r\nfile  then, using the appropriate interpreter, execute the file from  the\r\ncommand line.   The interpreter takes this code and encapsulates it  into\r\na  Vim  script function and calls the function, capturing any output  and\r\necho-ing it to the shell command line.\r\n\r\nExamples and doc files included in package","4":"vimsh and vimsh.bat are simple Vim script shell command line interpreters\r\nfor  UNIX and MSDOS respectively.  You type Vim script code into a .vimsh\r\nfile  then, using the appropriate interpreter, execute the file from  the\r\ncommand line.   The interpreter takes this code and encapsulates it  into\r\na  Vim  script function and calls the function, capturing any output  and\r\necho-ing it to the shell command line.\r\n\r\nExamples and doc files included in package","install_details":"Choose a location in your PATH and place either vimsh (UNIX) or vimsh.bat (MSDOS) or both.","5":"Choose a location in your PATH and place either vimsh (UNIX) or vimsh.bat (MSDOS) or both.","first_name":"Dave","6":"Dave","last_name":"Silvia","7":"Silvia","releases":[{"0":"1069","vim_version":"6.0","1":"6.0","script_version":"1.1","2":"1.1","version_comment":"Added - command line arguments to scripts","3":"Added - command line arguments to scripts","package":"vimsh.zip","4":"vimsh.zip","src_id":"3395","5":"3395","creation_date":"1093603090","6":"1093603090"},{"0":"1069","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"vimsh.zip","4":"vimsh.zip","src_id":"3385","5":"3385","creation_date":"1093468525","6":"1093468525"}]},"1068":{"script_id":"1068","0":"1068","script_name":"abap.vim","1":"abap.vim","script_type":"syntax","2":"syntax","summary":"Syntax highlighting for SAP ABAP \/ 4","3":"Syntax highlighting for SAP ABAP \/ 4","description":"An alternate version of SAP ABAP syntax highlighting with:\r\n\r\n1. correct ABAP special table\/structure\/symbol matching\r\n2. enhanced comprehensive keyword recognition.\r\n3. OO support\r\n\r\nCurrently this is the default for .abap files as used in VIM\r\n\r\nPlease mail comments and suggestions to: lailoken@gmail.com","4":"An alternate version of SAP ABAP syntax highlighting with:\r\n\r\n1. correct ABAP special table\/structure\/symbol matching\r\n2. enhanced comprehensive keyword recognition.\r\n3. OO support\r\n\r\nCurrently this is the default for .abap files as used in VIM\r\n\r\nPlease mail comments and suggestions to: lailoken@gmail.com","install_details":"Copy script to syntax\/ directory\r\n\r\nEdit filetype.vim and add:\r\n-- \r\n\" (SAP) ABAP\r\nau BufNewFile,BufRead *.abap    \t\tsetf abap\r\n-- \r\n\r\nNOTE: You will have to re-do this if you upgrade\/re-install VIM.","5":"Copy script to syntax\/ directory\r\n\r\nEdit filetype.vim and add:\r\n-- \r\n\" (SAP) ABAP\r\nau BufNewFile,BufRead *.abap    \t\tsetf abap\r\n-- \r\n\r\nNOTE: You will have to re-do this if you upgrade\/re-install VIM.","first_name":"Marius","6":"Marius","last_name":"Piedallu van Wyk","7":"Piedallu van Wyk","releases":[{"0":"1068","vim_version":"6.0","1":"6.0","script_version":"2.1","2":"2.1","version_comment":"Fixed match keyword word boundaries.\r\nOther small issues.","3":"Fixed match keyword word boundaries.\r\nOther small issues.","package":"abap.vim","4":"abap.vim","src_id":"18866","5":"18866","creation_date":"1350993553","6":"1350993553"},{"0":"1068","vim_version":"6.0","1":"6.0","script_version":"2.0","2":"2.0","version_comment":"Made syntax be more OO friendly.","3":"Made syntax be more OO friendly.","package":"abap.vim","4":"abap.vim","src_id":"18796","5":"18796","creation_date":"1350139626","6":"1350139626"},{"0":"1068","vim_version":"6.0","1":"6.0","script_version":"0.6","2":"0.6","version_comment":"Added support for better multi-token statements. 'BEGIN OF'\r\nAdded better multi-token end and begin matching\r\nAdded better table\/field matching (wuith special fields)\r\nAdded Include recognition.","3":"Added support for better multi-token statements. 'BEGIN OF'\r\nAdded better multi-token end and begin matching\r\nAdded better table\/field matching (wuith special fields)\r\nAdded Include recognition.","package":"abap.vim","4":"abap.vim","src_id":"3386","5":"3386","creation_date":"1093482273","6":"1093482273"},{"0":"1068","vim_version":"6.0","1":"6.0","script_version":"0.5","2":"0.5","version_comment":"Initial upload","3":"Initial upload","package":"abap.vim","4":"abap.vim","src_id":"3381","5":"3381","creation_date":"1093409130","6":"1093409130"}]},"1067":{"script_id":"1067","0":"1067","script_name":"mingw.vim","1":"mingw.vim","script_type":"utility","2":"utility","summary":"Vim compiler file for MinGW.","3":"Vim compiler file for MinGW.","description":"This is Vim compiler file for MinGW gcc distribution (http:\/\/www.mingw.org\/). It use output from make (yes, you will need to write Makefile), and do proper redirection to Vim's temporary file.  ","4":"This is Vim compiler file for MinGW gcc distribution (http:\/\/www.mingw.org\/). It use output from make (yes, you will need to write Makefile), and do proper redirection to Vim's temporary file.  ","install_details":"Script use \"redir.exe\" file which comes with MinGW's default binutils distribution, so make sure to check it. Place script file in your \"vim6x\\compiler\" directory and run \":compiler mingw\". Compilation goes through \":make\" and errors from output you can see with \":copen\" and \":cwin\".","5":"Script use \"redir.exe\" file which comes with MinGW's default binutils distribution, so make sure to check it. Place script file in your \"vim6x\\compiler\" directory and run \":compiler mingw\". Compilation goes through \":make\" and errors from output you can see with \":copen\" and \":cwin\".","first_name":"Sanel","6":"Sanel","last_name":"Zukan","7":"Zukan","releases":[{"0":"1067","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"mingw.vim","4":"mingw.vim","src_id":"3373","5":"3373","creation_date":"1093310000","6":"1093310000"}]},"1066":{"script_id":"1066","0":"1066","script_name":"cecutil","1":"cecutil","script_type":"utility","2":"utility","summary":"Some utilities used by several of my scripts (window positioning, mark handling)","3":"Some utilities used by several of my scripts (window positioning, mark handling)","description":" [CECUTIL V15 OR LATER REQUIRES VIMBALL V18 OR LATER FOR UNPACKING]\r\n\r\nThese routines are used by several of my utilities.  I'm loading them onto vim.sf.net to make it easier for GetLatestVimScripts to automate updates with them.\r\n\r\nMarks:\r\n     call SaveMark(markname)       let savemark= SaveMark(markname)\r\n     call RestoreMark(markname)    call RestoreMark(savemark)\r\n     call DestroyMark(markname)\r\n     commands: SM RM DM\r\n\r\nWindow Position:\r\n     call SaveWinPosn()        let winposn= SaveWinPosn()\r\n     call RestoreWinPosn()     call RestoreWinPosn(winposn)\r\n    \\swp : save current window\/buffer's position\r\n    \\rwp : restore current window\/buffer's previous position\r\n     commands: SWP RWP\r\n\r\nUser Maps:\r\n    call SaveUserMaps(mapmode,maplead,mapchx,suffix)\r\n\r\n    This function sets up a script-variable (ie. a variable that can generally be accessed only from within cecutil's own functions; see |s:|) called s:restoremap.  The selected user's maps are appended to this variable; the RestoreUserMaps() (|cecutil-restoreusermaps|) function uses the contents of this variable to restore user maps.\r\n\r\n    Some examples follow:\r\n\r\n        call SaveUserMaps(\"n\",\"\",\"webWEBjklh$0%;,nN\",\"HiMtchBrkt\")\r\n            normal mode maps for w, e, b, W, E, B, j, k, l, etc\r\n            (if any) are all saved in the variable\r\n            s:restoremaps_HiMtchBrkt >\r\n\r\n        call SaveUserMaps(\"n\",\"\",\"<up>\",\"DrawIt\")\r\n            the normal mode map (if any) for the <up> key is saved in\r\n            the variable s:restoremaps_DrawIt >\r\n\r\n        call SaveUserMaps(\"n\",\"\",\":F(\",\"HiMtchBrkt\")\r\n            the normal mode map for F( (if any) is saved in the\r\n            variable s:restoremaps_HiMtchBrkt\r\n\r\n    call RestoreUserMaps(suffix)\r\n\r\n        The usermaps saved by SaveUserMaps() with the given suffix will be restored (ie. s:restoremaps_{suffix}).  Example:\r\n\r\n        call RestoreUserMaps(\"HiMtchBrkt\")\r\n            will restore all user maps redefined for the HiMtchBrkt plugin\r\n\r\n(alpha\/beta version available at http:\/\/www.drchip.org\/astronaut\/vim\/index.html#CECUTIL)\r\n","4":" [CECUTIL V15 OR LATER REQUIRES VIMBALL V18 OR LATER FOR UNPACKING]\r\n\r\nThese routines are used by several of my utilities.  I'm loading them onto vim.sf.net to make it easier for GetLatestVimScripts to automate updates with them.\r\n\r\nMarks:\r\n     call SaveMark(markname)       let savemark= SaveMark(markname)\r\n     call RestoreMark(markname)    call RestoreMark(savemark)\r\n     call DestroyMark(markname)\r\n     commands: SM RM DM\r\n\r\nWindow Position:\r\n     call SaveWinPosn()        let winposn= SaveWinPosn()\r\n     call RestoreWinPosn()     call RestoreWinPosn(winposn)\r\n    \\swp : save current window\/buffer's position\r\n    \\rwp : restore current window\/buffer's previous position\r\n     commands: SWP RWP\r\n\r\nUser Maps:\r\n    call SaveUserMaps(mapmode,maplead,mapchx,suffix)\r\n\r\n    This function sets up a script-variable (ie. a variable that can generally be accessed only from within cecutil's own functions; see |s:|) called s:restoremap.  The selected user's maps are appended to this variable; the RestoreUserMaps() (|cecutil-restoreusermaps|) function uses the contents of this variable to restore user maps.\r\n\r\n    Some examples follow:\r\n\r\n        call SaveUserMaps(\"n\",\"\",\"webWEBjklh$0%;,nN\",\"HiMtchBrkt\")\r\n            normal mode maps for w, e, b, W, E, B, j, k, l, etc\r\n            (if any) are all saved in the variable\r\n            s:restoremaps_HiMtchBrkt >\r\n\r\n        call SaveUserMaps(\"n\",\"\",\"<up>\",\"DrawIt\")\r\n            the normal mode map (if any) for the <up> key is saved in\r\n            the variable s:restoremaps_DrawIt >\r\n\r\n        call SaveUserMaps(\"n\",\"\",\":F(\",\"HiMtchBrkt\")\r\n            the normal mode map for F( (if any) is saved in the\r\n            variable s:restoremaps_HiMtchBrkt\r\n\r\n    call RestoreUserMaps(suffix)\r\n\r\n        The usermaps saved by SaveUserMaps() with the given suffix will be restored (ie. s:restoremaps_{suffix}).  Example:\r\n\r\n        call RestoreUserMaps(\"HiMtchBrkt\")\r\n            will restore all user maps redefined for the HiMtchBrkt plugin\r\n\r\n(alpha\/beta version available at http:\/\/www.drchip.org\/astronaut\/vim\/index.html#CECUTIL)\r\n","install_details":"1. Get vimball v18 if you don't have it already (vimscript#1502).  Please remove any vestiges of an older vimball first.\r\n    (if you have vim 7.1a or later, you probably can skip this step)\r\n2. vim cecutil.vba.gz\r\n    :so %\r\n    :q\r\n\r\nWorks well with AsNeeded, too (vimscript#915).","5":"1. Get vimball v18 if you don't have it already (vimscript#1502).  Please remove any vestiges of an older vimball first.\r\n    (if you have vim 7.1a or later, you probably can skip this step)\r\n2. vim cecutil.vba.gz\r\n    :so %\r\n    :q\r\n\r\nWorks well with AsNeeded, too (vimscript#915).","first_name":"Charles","6":"Charles","last_name":"Campbell","7":"Campbell","releases":[{"0":"1066","vim_version":"7.0","1":"7.0","script_version":"17","2":"17","version_comment":"A new function, QArgSplitter(), now comes with cecutil.","3":"A new function, QArgSplitter(), now comes with cecutil.","package":"cecutil.vba.gz","4":"cecutil.vba.gz","src_id":"7618","5":"7618","creation_date":"1188909905","6":"1188909905"},{"0":"1066","vim_version":"7.0","1":"7.0","script_version":"16","2":"16","version_comment":"Changed com to com! so AsNeeded (vimscript#915) is happier.\r\n\r\nFixed a bug concerning maps which don't use the mapleader option are still saved and restored properly.\r\n","3":"Changed com to com! so AsNeeded (vimscript#915) is happier.\r\n\r\nFixed a bug concerning maps which don't use the mapleader option are still saved and restored properly.\r\n","package":"cecutil.vba.gz","4":"cecutil.vba.gz","src_id":"6974","5":"6974","creation_date":"1176365373","6":"1176365373"},{"0":"1066","vim_version":"7.0","1":"7.0","script_version":"15","2":"15","version_comment":"* (-new-)  map restoration improved\r\n* (change) b:(varname) now use b:cecutil_(varname)\r\n* (bugfix) bypass for report option for DestroyMark() included\r\n* (bugfix) SaveWinPosn() and RestoreWinPosn() now handle an empty buffer","3":"* (-new-)  map restoration improved\r\n* (change) b:(varname) now use b:cecutil_(varname)\r\n* (bugfix) bypass for report option for DestroyMark() included\r\n* (bugfix) SaveWinPosn() and RestoreWinPosn() now handle an empty buffer","package":"cecutil.vba.gz","4":"cecutil.vba.gz","src_id":"6205","5":"6205","creation_date":"1158668536","6":"1158668536"},{"0":"1066","vim_version":"6.0","1":"6.0","script_version":"14","2":"14","version_comment":"SaveUserMaps' mapmode argument, heretofore just a single letter (see |maparg()|), now accepts a leading \"u\".  If present, SaveUserMaps() will do an unmap.\r\nBypasses for si, so, and siso options included.\r\n","3":"SaveUserMaps' mapmode argument, heretofore just a single letter (see |maparg()|), now accepts a leading \"u\".  If present, SaveUserMaps() will do an unmap.\r\nBypasses for si, so, and siso options included.\r\n","package":"cecutil.vim.gz","4":"cecutil.vim.gz","src_id":"5001","5":"5001","creation_date":"1138176847","6":"1138176847"}]},"1065":{"script_id":"1065","0":"1065","script_name":"click.vim","1":"click.vim","script_type":"syntax","2":"syntax","summary":"Syntax file for the click language","3":"Syntax file for the click language","description":"This is the syntax file for the click language of the Click Modular Router Project.\r\n(http:\/\/www.pdos.lcs.mit.edu\/click\/)\r\n\r\nThe syntax file has the following benefits:\r\n- Keyword highlighting\r\n- Decimal and hexadecimal number highlighting\r\n- Highlighting of\r\n  - Ethernet MAC addresses\r\n  - IPv4 addresses\r\n  - IPv6 addresses (to be improved)\r\n","4":"This is the syntax file for the click language of the Click Modular Router Project.\r\n(http:\/\/www.pdos.lcs.mit.edu\/click\/)\r\n\r\nThe syntax file has the following benefits:\r\n- Keyword highlighting\r\n- Decimal and hexadecimal number highlighting\r\n- Highlighting of\r\n  - Ethernet MAC addresses\r\n  - IPv4 addresses\r\n  - IPv6 addresses (to be improved)\r\n","install_details":"Put the file into your syntax directory and make your ViM click-aware by following the instructions described in \":help 43.2\".","5":"Put the file into your syntax directory and make your ViM click-aware by following the instructions described in \":help 43.2\".","first_name":"Soeren","6":"Soeren","last_name":"Sonntag","7":"Sonntag","releases":[{"0":"1065","vim_version":"6.0","1":"6.0","script_version":"0.3","2":"0.3","version_comment":"Added highlighting for classes and instances.\r\nChanged mappings for protocols.\r\nImproved string highlighting.","3":"Added highlighting for classes and instances.\r\nChanged mappings for protocols.\r\nImproved string highlighting.","package":"click.vim","4":"click.vim","src_id":"3374","5":"3374","creation_date":"1093316309","6":"1093316309"},{"0":"1065","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"click.vim","4":"click.vim","src_id":"3368","5":"3368","creation_date":"1093250172","6":"1093250172"}]},"1064":{"script_id":"1064","0":"1064","script_name":"asp.vim","1":"asp.vim","script_type":"utility","2":"utility","summary":"Macros and menus for ASP documents","3":"Macros and menus for ASP documents","description":"Almost each ASP keyword may be accessed by its short cut (and by the menu if using a GUI) in each of 3 modes.\r\nIf you don't like to use \"<F5>\" as a trigger you can change it to, for examle \"?\".\r\nOpen asp.vim in Vim editor and substitute :%s\/<F5>\/?\/g\r\n","4":"Almost each ASP keyword may be accessed by its short cut (and by the menu if using a GUI) in each of 3 modes.\r\nIf you don't like to use \"<F5>\" as a trigger you can change it to, for examle \"?\".\r\nOpen asp.vim in Vim editor and substitute :%s\/<F5>\/?\/g\r\n","install_details":"Copy to plugin directory. \r\n  ","5":"Copy to plugin directory. \r\n  ","first_name":"Branislav","6":"Branislav","last_name":"Sobotka","7":"Sobotka","releases":[{"0":"1064","vim_version":"6.0","1":"6.0","script_version":"1.1","2":"1.1","version_comment":"Some bugs fixed.\r\nAdded:\r\n- Server variables constants\r\n- Content type constants\r\n- map for new asp file and include file \r\n\r\n","3":"Some bugs fixed.\r\nAdded:\r\n- Server variables constants\r\n- Content type constants\r\n- map for new asp file and include file \r\n\r\n","package":"asp.vim","4":"asp.vim","src_id":"3561","5":"3561","creation_date":"1098151452","6":"1098151452"},{"0":"1064","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"asp.vim","4":"asp.vim","src_id":"3366","5":"3366","creation_date":"1093234607","6":"1093234607"}]},"1063":{"script_id":"1063","0":"1063","script_name":"HC12 syntax highlighting","1":"HC12 syntax highlighting","script_type":"syntax","2":"syntax","summary":"Syntax file for 68HC11\/12 Assembly","3":"Syntax file for 68HC11\/12 Assembly","description":"Contains the syntax defiinitions for writing assembly code for the Motorola 68HC11\/12 family of microcontrollers.","4":"Contains the syntax defiinitions for writing assembly code for the Motorola 68HC11\/12 family of microcontrollers.","install_details":"","5":"","first_name":"John","6":"John","last_name":"Byrnes","7":"Byrnes","releases":[{"0":"1063","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"asmhc12.vim","4":"asmhc12.vim","src_id":"3365","5":"3365","creation_date":"1093088095","6":"1093088095"}]},"1062":{"script_id":"1062","0":"1062","script_name":"greputils","1":"greputils","script_type":"utility","2":"utility","summary":"Interface with grep, find and id-utils (not just another grep wrapper)","3":"Interface with grep, find and id-utils (not just another grep wrapper)","description":"Derived from my original idutils.vim, this script is a lot more powerful and useful than ever. The commands that make use of Vim built-in grep are especially useful and unique (thanks to Tim Chase for the idea).\r\n\r\n  - There are many plugins that wrap the Vim built-in :grep command and try\r\n    to simplify the usage. However this plugin aims at providing two\r\n    specific features:\r\n        - Escape the arguments such that the arguments can be passed to the\r\n          external grep\/lid\/find literally. This avoids unwanted\r\n          interpretations by the shell, thus allowing you to concentrate on\r\n          the regular expression patterns rather than how to escape them.\r\n          This has been tested well on both windows and UNIX with\r\n          sh\/bash\/cmd as command shells.\r\n        - Allow you to preview the results before letting Vim handle them as\r\n          part of quickfix. This, besides allowing you to further filter the\r\n          results, also prevents Vim from adding buffers for files that are\r\n          uninteresting and thus help reduce the number of buffers. It also\r\n          supports basic quickfix commands that can be used to open a buffer \r\n          without needing to convert it to a quickfix window. You can\r\n          consider it as a lightweight quickfix window. The preview window\r\n          is also great if you just want to take a peak at the results, not\r\n          really navigate them (such as to get an estimate of where all a\r\n          reference is found).\r\n    - Also provides commands to run the Vim built-in :g\/re\/p on multiple\r\n      buffers using :argdo, :bufdo and :windo commands and redirect the\r\n      output to the grep-results preview window. You can then convert the\r\n      results to a quickfix window, or use the preview window to navigate.\r\n    - As a bonus, the plugin also works around Vim problem with creating a\r\n      number of unnamed buffers as you close and open quickfix window\r\n      several times. This helps keep buffer list uncluttered.\r\n                                                                              \r\n  - The command merely wraps the built-in :grep, :grepadd, :cfile and\r\n    :cgetfile commands to create the quickfix list. The rest of the quickfix\r\n    commands work just like they do on the quickfix results created by using\r\n    only the built-in functionality. This also means that the plugin assume\r\n    that you have the options such as 'grepprg', 'shellpipe' are properly\r\n    set. Read the help on quickfix for the full list of commands and options\r\n    that you have.\r\n                                                                              \r\n      :h quickfix \r\n                                                                              \r\n  - Other than the preview functionality which enables filtering, the plugin\r\n    also provides an easy way to specify a number of filter commands that\r\n    you can chain on the output of the grep\/lid\/find, each prefixed with\r\n    \"+f\". The arguments to the filter command are themselves escaped, the\r\n    same way as the grep command arguments as described above.\r\n  - Supports GNU \"grep\" and MS Windows \"findstr\" for running \"find-in-file\"\r\n    kind of searches, id-utils \"lid\" for running index searches, and GNU\r\n    \"find\" to search for file names. If you need to add support for a new\r\n    grep command or a grep-like tool, it is just a matter of modifying a few\r\n    internal variables and possibly adding a new set of commands.\r\n  - On windows, setting multiple ID files for IDPATH doesn't work, so the\r\n    plugin provides a workaround by running \"lid\" separately on each ID file\r\n    if there are multiple ID files separated by \";\" in the IDPATH.\r\n  - Make sure that the 'grepprg' and 'shellpipe' options are properly set\r\n    and that the built-in :grep itself works. For GNU id-utils, make sure\r\n    IDPATH environmental variable is set or path to the ID file is specified\r\n    with the \"-f\" argument in the g:greputilsLidcmd setting. You can also\r\n    specify the \"-f ID\" arguments to the :IDGrep command.\r\n  - Uses EscapeCommand() function from genutils.vim plugin that supports\r\n    Cygwin \"bash\", MS Windows \"cmd\" and Unix \"sh\" for shell escaping. Other\r\n    environments are untested.\r\n  - Defines the following commands:\r\n                                                                              \r\n      Grep, GrepAdd, IDGrep, IDGrepAdd, Find, FindAdd\r\n      Grepp, GreppAdd, IDGrepp, IDGreppAdd, Findp, FindpAdd\r\n                                                                              \r\n    The second set of commands are used to open the results in a preview\r\n    window instead of directly in the quickfix window. And those that have a\r\n    suffix of \"Add\" add the new list of results to the existing list,\r\n    instead of replacing them (just like in :grepadd). This can be very\r\n    useful in combination with the preview commands.\r\n                                                                              \r\n    You can open the preview window at anytime using GrepPreview command.\r\n    Once you are in the preview window, you can filter the results using the\r\n    regular Vim commands, and when you would like to browse the results\r\n    using Vim quickfix commands, just use Cfile and Cgetfile commands, which\r\n    are functionally equivalent to the built-in cfile and cgetfile commands\r\n    respectively, except that they don't take a filename as argument use the\r\n    current preview window contents to create the error-list. There are\r\n    also, GOpen, GClose and GWindow commands defined on the lines of copen,\r\n    cclose and cwindow respectively.\r\n                                                                              \r\n    Use the GrepPreviewSetup command to convert an arbitrary buffer\r\n    containing :grep output as a preview window. This is useful to take\r\n    advantage of the quickfix like functionality that the plugin provides on\r\n    grep results generated by your own commands.\r\n                                                                              \r\n    If cmdalias.vim is installed, it also creates aliases for the Grep,\r\n    GrepAdd, Cfile and Cgetfile commands to the corresponding built-in\r\n    commands, i.e., grep, grepadd, cfile and cgetfile respectively.\r\n                                                                              \r\n    The preview window supports the following commands:\r\n      preview command     quickfix command ~\r\n      GG [count]          cc [count]\r\n      [count]GNext        [count]cnext\r\n      [count]GPrev        [count]cNext, cprevious\r\n      <CR>                <CR>\r\n      <2-LeftMouse>       <2-LeftMouse>\r\n                                                                              \r\n    The commands supports [count] argument just like the corresponding\r\n    quickfix command.\r\n                                                                              \r\n  General Syntax:\r\n      <grep command> [<grep\/lid\/find options> ...] <regex\/keyword>\r\n                     [<filename patterns>\/<more options>]\r\n                     [+f <filter arguments> ...]\r\n                                                                              \r\n    Note that typically you have to pass in at least one filename pattern to\r\n    grep\/findstr where as you don't pass in any for lid.\r\n  - Also defines the following commands:\r\n                                                                              \r\n      ArgGrep, ArgGrepAdd, BufGrep, BufGrepAdd, WinGrep, WinGrepAdd\r\n                                                                              \r\n    You can use the above commands to run Vim's built-in g\/re\/p command to\r\n    find matches across buffers loaded in the current session, without\r\n    needing any external tools. Each of the above commands (and their \"Add\"\r\n    variants), run g\/re\/p command on a bunch of buffers loaded using one of\r\n    :argdo, :bufdo and :windo commands respectively. These commands are\r\n    designed to always open the results in the preview window. If you like,\r\n    you can convert it to a quickfix result, by using :Cfile or :Cgetfile\r\n    command.\r\n                                                                              \r\n  General Syntax:\r\n      [range]<Arg|Buf|Win>Grep[Add] [<pattern>]\r\n                                                                              \r\n    If you don't specify a pattern, the current value in search register\r\n    (@\/) will be used, which essentially means that the last search pattern\r\n    will be used. See also g:greputilsVimGrepSepChar setting under\r\n    installation section.\r\n                                                                              \r\n    The range, if not specified, defaults to all the lines in all the\r\n    applicable buffers. If you explicitly specify a range, please note that\r\n    a range such as \"%\" or \"1,$\" is translated to the absolute line numbers\r\n    with reference to the current buffer by Vim itself, so it is not the\r\n    same as not specifying at all. This means, if there are 100 lines in the\r\n    current buffer, specifying \"%\" or \"1,$\" is equivalent to specifying\r\n    \"1,100\" as the range. The range is more useful with the \"GrepBufs\"\r\n    command mentioned below.\r\n  - Also defines \"GrepBufs\" command that can be used to grep for a Vim\r\n    regular expression pattern in the specified set of buffers (or the\r\n    current buffer). If no pattern is specified it will default to the\r\n    current search pattern. Buffers can be specified by name (see :h\r\n    bufname()) or by their number using the #<bufno> notation. You can also\r\n    complete the buffer names by using the completion character (<Tab>).\r\n                                                                              \r\n  General Syntax:\r\n      [range]GrepBufs[Add] [pattern] [buffer ...]\r\n                                                                              \r\n    This by syntax is very close to the Unix grep command. The main\r\n    difference being that it uses Vim regex and it searches the buffers\r\n    already loaded instead of those on the file system.\r\n                                                                              \r\n    The range has same semantics as for any of the \"arg\", \"buf\" or \"win\" grep\r\n    commands, but it is more useful here while limiting the grep for one\r\n    buffer alone.\r\n                                                                              \r\nExamples:\r\n  The following examples assume that you are using GNU grep for both the\r\n  'grepprg' and as the g:greputilsFiltercmd.\r\n                                                                              \r\n  - Run GNU grep from the directory of the current file recursively while\r\n    limiting the search only for Java files.\r\n      Grep -r --include=*.java \\<main\\> %:h\r\n  - Run lid while filtering the lines that are not from Java source.\r\n      IDGrep main +f \\.java\r\n  - Run lid while filtering the lines that contain src.\r\n      IDGrep main +f -v src\r\n  - Find Java files starting with A and ending with z under src.\r\n      Find src -iname A*z.java\r\n                                                                              \r\n  - To search for the current word in all the files and filter the results\r\n    not containing \\.java in the grepped output. This will potentially\r\n    return all the occurences in the java files only. \r\n      IDGrep <cword> +f \\.java \r\n                                                                              \r\n  - If any argument contains spaces, then you need to protect them by\r\n    prefixing them with a backslash.  The following will filter those lines\r\n    that don't contain \"public static\".\r\n      IDGrep <cword> +f public\\ static\r\n                                                                              \r\n  - Run \":bufdo g\/public static\/p\" and show output in preview window:\r\n      BufGrep public\\ static\r\n\r\n\r\n\r\n\r\n\r\nSearch_key_words: idutils greputils greputil id-utils gnu id grep gid mkid lid windo argdo bufdo Hari Krishna Dara","4":"Derived from my original idutils.vim, this script is a lot more powerful and useful than ever. The commands that make use of Vim built-in grep are especially useful and unique (thanks to Tim Chase for the idea).\r\n\r\n  - There are many plugins that wrap the Vim built-in :grep command and try\r\n    to simplify the usage. However this plugin aims at providing two\r\n    specific features:\r\n        - Escape the arguments such that the arguments can be passed to the\r\n          external grep\/lid\/find literally. This avoids unwanted\r\n          interpretations by the shell, thus allowing you to concentrate on\r\n          the regular expression patterns rather than how to escape them.\r\n          This has been tested well on both windows and UNIX with\r\n          sh\/bash\/cmd as command shells.\r\n        - Allow you to preview the results before letting Vim handle them as\r\n          part of quickfix. This, besides allowing you to further filter the\r\n          results, also prevents Vim from adding buffers for files that are\r\n          uninteresting and thus help reduce the number of buffers. It also\r\n          supports basic quickfix commands that can be used to open a buffer \r\n          without needing to convert it to a quickfix window. You can\r\n          consider it as a lightweight quickfix window. The preview window\r\n          is also great if you just want to take a peak at the results, not\r\n          really navigate them (such as to get an estimate of where all a\r\n          reference is found).\r\n    - Also provides commands to run the Vim built-in :g\/re\/p on multiple\r\n      buffers using :argdo, :bufdo and :windo commands and redirect the\r\n      output to the grep-results preview window. You can then convert the\r\n      results to a quickfix window, or use the preview window to navigate.\r\n    - As a bonus, the plugin also works around Vim problem with creating a\r\n      number of unnamed buffers as you close and open quickfix window\r\n      several times. This helps keep buffer list uncluttered.\r\n                                                                              \r\n  - The command merely wraps the built-in :grep, :grepadd, :cfile and\r\n    :cgetfile commands to create the quickfix list. The rest of the quickfix\r\n    commands work just like they do on the quickfix results created by using\r\n    only the built-in functionality. This also means that the plugin assume\r\n    that you have the options such as 'grepprg', 'shellpipe' are properly\r\n    set. Read the help on quickfix for the full list of commands and options\r\n    that you have.\r\n                                                                              \r\n      :h quickfix \r\n                                                                              \r\n  - Other than the preview functionality which enables filtering, the plugin\r\n    also provides an easy way to specify a number of filter commands that\r\n    you can chain on the output of the grep\/lid\/find, each prefixed with\r\n    \"+f\". The arguments to the filter command are themselves escaped, the\r\n    same way as the grep command arguments as described above.\r\n  - Supports GNU \"grep\" and MS Windows \"findstr\" for running \"find-in-file\"\r\n    kind of searches, id-utils \"lid\" for running index searches, and GNU\r\n    \"find\" to search for file names. If you need to add support for a new\r\n    grep command or a grep-like tool, it is just a matter of modifying a few\r\n    internal variables and possibly adding a new set of commands.\r\n  - On windows, setting multiple ID files for IDPATH doesn't work, so the\r\n    plugin provides a workaround by running \"lid\" separately on each ID file\r\n    if there are multiple ID files separated by \";\" in the IDPATH.\r\n  - Make sure that the 'grepprg' and 'shellpipe' options are properly set\r\n    and that the built-in :grep itself works. For GNU id-utils, make sure\r\n    IDPATH environmental variable is set or path to the ID file is specified\r\n    with the \"-f\" argument in the g:greputilsLidcmd setting. You can also\r\n    specify the \"-f ID\" arguments to the :IDGrep command.\r\n  - Uses EscapeCommand() function from genutils.vim plugin that supports\r\n    Cygwin \"bash\", MS Windows \"cmd\" and Unix \"sh\" for shell escaping. Other\r\n    environments are untested.\r\n  - Defines the following commands:\r\n                                                                              \r\n      Grep, GrepAdd, IDGrep, IDGrepAdd, Find, FindAdd\r\n      Grepp, GreppAdd, IDGrepp, IDGreppAdd, Findp, FindpAdd\r\n                                                                              \r\n    The second set of commands are used to open the results in a preview\r\n    window instead of directly in the quickfix window. And those that have a\r\n    suffix of \"Add\" add the new list of results to the existing list,\r\n    instead of replacing them (just like in :grepadd). This can be very\r\n    useful in combination with the preview commands.\r\n                                                                              \r\n    You can open the preview window at anytime using GrepPreview command.\r\n    Once you are in the preview window, you can filter the results using the\r\n    regular Vim commands, and when you would like to browse the results\r\n    using Vim quickfix commands, just use Cfile and Cgetfile commands, which\r\n    are functionally equivalent to the built-in cfile and cgetfile commands\r\n    respectively, except that they don't take a filename as argument use the\r\n    current preview window contents to create the error-list. There are\r\n    also, GOpen, GClose and GWindow commands defined on the lines of copen,\r\n    cclose and cwindow respectively.\r\n                                                                              \r\n    Use the GrepPreviewSetup command to convert an arbitrary buffer\r\n    containing :grep output as a preview window. This is useful to take\r\n    advantage of the quickfix like functionality that the plugin provides on\r\n    grep results generated by your own commands.\r\n                                                                              \r\n    If cmdalias.vim is installed, it also creates aliases for the Grep,\r\n    GrepAdd, Cfile and Cgetfile commands to the corresponding built-in\r\n    commands, i.e., grep, grepadd, cfile and cgetfile respectively.\r\n                                                                              \r\n    The preview window supports the following commands:\r\n      preview command     quickfix command ~\r\n      GG [count]          cc [count]\r\n      [count]GNext        [count]cnext\r\n      [count]GPrev        [count]cNext, cprevious\r\n      <CR>                <CR>\r\n      <2-LeftMouse>       <2-LeftMouse>\r\n                                                                              \r\n    The commands supports [count] argument just like the corresponding\r\n    quickfix command.\r\n                                                                              \r\n  General Syntax:\r\n      <grep command> [<grep\/lid\/find options> ...] <regex\/keyword>\r\n                     [<filename patterns>\/<more options>]\r\n                     [+f <filter arguments> ...]\r\n                                                                              \r\n    Note that typically you have to pass in at least one filename pattern to\r\n    grep\/findstr where as you don't pass in any for lid.\r\n  - Also defines the following commands:\r\n                                                                              \r\n      ArgGrep, ArgGrepAdd, BufGrep, BufGrepAdd, WinGrep, WinGrepAdd\r\n                                                                              \r\n    You can use the above commands to run Vim's built-in g\/re\/p command to\r\n    find matches across buffers loaded in the current session, without\r\n    needing any external tools. Each of the above commands (and their \"Add\"\r\n    variants), run g\/re\/p command on a bunch of buffers loaded using one of\r\n    :argdo, :bufdo and :windo commands respectively. These commands are\r\n    designed to always open the results in the preview window. If you like,\r\n    you can convert it to a quickfix result, by using :Cfile or :Cgetfile\r\n    command.\r\n                                                                              \r\n  General Syntax:\r\n      [range]<Arg|Buf|Win>Grep[Add] [<pattern>]\r\n                                                                              \r\n    If you don't specify a pattern, the current value in search register\r\n    (@\/) will be used, which essentially means that the last search pattern\r\n    will be used. See also g:greputilsVimGrepSepChar setting under\r\n    installation section.\r\n                                                                              \r\n    The range, if not specified, defaults to all the lines in all the\r\n    applicable buffers. If you explicitly specify a range, please note that\r\n    a range such as \"%\" or \"1,$\" is translated to the absolute line numbers\r\n    with reference to the current buffer by Vim itself, so it is not the\r\n    same as not specifying at all. This means, if there are 100 lines in the\r\n    current buffer, specifying \"%\" or \"1,$\" is equivalent to specifying\r\n    \"1,100\" as the range. The range is more useful with the \"GrepBufs\"\r\n    command mentioned below.\r\n  - Also defines \"GrepBufs\" command that can be used to grep for a Vim\r\n    regular expression pattern in the specified set of buffers (or the\r\n    current buffer). If no pattern is specified it will default to the\r\n    current search pattern. Buffers can be specified by name (see :h\r\n    bufname()) or by their number using the #<bufno> notation. You can also\r\n    complete the buffer names by using the completion character (<Tab>).\r\n                                                                              \r\n  General Syntax:\r\n      [range]GrepBufs[Add] [pattern] [buffer ...]\r\n                                                                              \r\n    This by syntax is very close to the Unix grep command. The main\r\n    difference being that it uses Vim regex and it searches the buffers\r\n    already loaded instead of those on the file system.\r\n                                                                              \r\n    The range has same semantics as for any of the \"arg\", \"buf\" or \"win\" grep\r\n    commands, but it is more useful here while limiting the grep for one\r\n    buffer alone.\r\n                                                                              \r\nExamples:\r\n  The following examples assume that you are using GNU grep for both the\r\n  'grepprg' and as the g:greputilsFiltercmd.\r\n                                                                              \r\n  - Run GNU grep from the directory of the current file recursively while\r\n    limiting the search only for Java files.\r\n      Grep -r --include=*.java \\<main\\> %:h\r\n  - Run lid while filtering the lines that are not from Java source.\r\n      IDGrep main +f \\.java\r\n  - Run lid while filtering the lines that contain src.\r\n      IDGrep main +f -v src\r\n  - Find Java files starting with A and ending with z under src.\r\n      Find src -iname A*z.java\r\n                                                                              \r\n  - To search for the current word in all the files and filter the results\r\n    not containing \\.java in the grepped output. This will potentially\r\n    return all the occurences in the java files only. \r\n      IDGrep <cword> +f \\.java \r\n                                                                              \r\n  - If any argument contains spaces, then you need to protect them by\r\n    prefixing them with a backslash.  The following will filter those lines\r\n    that don't contain \"public static\".\r\n      IDGrep <cword> +f public\\ static\r\n                                                                              \r\n  - Run \":bufdo g\/public static\/p\" and show output in preview window:\r\n      BufGrep public\\ static\r\n\r\n\r\n\r\n\r\n\r\nSearch_key_words: idutils greputils greputil id-utils gnu id grep gid mkid lid windo argdo bufdo Hari Krishna Dara","install_details":"- Drop the file in your plugin directory or source it from your vimrc.\r\n- Requires genutils (vimscript#197) and multvals (vimscript #171) plugins\r\n  also to be installed.\r\n                                                                           \r\nOptional Settings:\r\n    g:greputilsLidcmd, g:greputilsFindcmd, g:greputilsFiltercmd,\r\n    g:greputilsFindMsgFmt, g:greputilsAutoCopen, g:greputilsVimGrepCmd,\r\n    g:greputilsVimGrepAddCmd, g:greputilsGrepCompMode,\r\n    g:greputilsLidCompMode, g:greputilsFindCompMode,\r\n    g:greputilsExpandCurWord, g:greputilsVimGrepSepChar,\r\n    g:greputilsPreserveLastResults, g:greputilsPreserveAllResults,\r\n    g:greputilsPreviewCreateFolds\r\n                                                                           \r\n  - Use g:greputilsLidcmd and g:greputilsFiltercmd to set the path\/name to\r\n    the lid and GNU or compatible find executable (defaults to \"lid\").\r\n  - Use g:greputilsFiltercmd to set the path\/name of the command that you\r\n    would like to use as the filter when \"+f\" option is used (defaults to\r\n    \"grep\").\r\n  - Set g:greputilsFindMsgFmt to change the message (%m) part of the find\r\n    results. You can specify anything that is accepted in the argument for\r\n    \"-printf\" find option.\r\n  - Use g:greputilsAutoCopen to specify if the error list window should\r\n    automatically be opened or closed based on whether there are any\r\n    results or not (runs :cwindow command at the end).\r\n  - Use g:greputilsVimGrepCmd and g:greputilsVimGrepAddCmd to have the\r\n    plugin run a different command than the built-in :grep command to\r\n    generate the results. This is mainly useful to use the plugin as a\r\n    wrapper to finally invoke another plugin after the arguments are\r\n    escaped and 'shellpipe' is properly set. The callee typically can just\r\n    run the :grep command on the arguments and do additional setup.\r\n  - Use g:greputilsGrepCompMode, g:greputilsLidCompMode and\r\n    g:greputilsFindCompMode to change the completion mode for Grep, IDGrep\r\n    and Find commands respectively. The default completion mode for Grep\r\n    and Find are \"file\" to match that of the built-in commands, where as\r\n    it is set to \"tag\" for IDGrep (except the -f argument to specify an ID\r\n    file, you never need to pass filenam to lid). When completion mode is\r\n    \"file\", Vim automatically expands filename meta-characters such as \"%\"\r\n    and \"#\" on the command-line, so you still need to escape then. If this\r\n    is an issue for you, then you should switch to \"tag\" or a different\r\n    completion mode. When completion mode is not \"file\", the plugin\r\n    expands the filename meta characters in the file arguments anyway, and\r\n    this can be considered as an advantage (think about passing patterns\r\n    to the command literally). However it is still useful to have\r\n    \"<cword>\" and \"<cWORD>\" expand inside the patterns, in which case you\r\n    can set g:greputilsExpandCurWord setting.  Changing this option at\r\n    runtime requires you to reload the plugin.\r\n  - When completion mode is not set to \"file\", you can set\r\n    g:greputilsExpandCurWord to have the plugin expand \"<cword>\" and\r\n    \"<cWORD>\" tokens. This essentially gives you all the goodness of file\r\n    completion while still being able to do tag completions.\r\n  - For Vim built-in grep operations such as :BufGrep, if you want to\r\n    change the character sorrounding the pattern from the default '\/' to\r\n    something else (see |E146|), you can use the\r\n    g:greputilsVimGrepSepChar. This is useful if you have a lot of \"\/\"\r\n    characters in your pattern.\r\n  - The plugin normally preserves the previous results in the preview\r\n    window, which you can retrieve by doing an undo immediately after\r\n    generating the new results, inside the preview window. If you don't\r\n    like this, you can disable this feature by resetting\r\n    g:greputilsPreserveLastResults setting. You can instead set the\r\n    g:greputilsPreserveAllResults to preserve all the changes done in the\r\n    preview window, by user and the plugin itself.\r\n  - While using the *pAdd commands (that add results to preview window),\r\n    the individual set of results are folded together to be able to\r\n    identify them better. You can disable this feature by resetting the\r\n    g:greputilsPreviewCreateFolds setting.\r\n","5":"- Drop the file in your plugin directory or source it from your vimrc.\r\n- Requires genutils (vimscript#197) and multvals (vimscript #171) plugins\r\n  also to be installed.\r\n                                                                           \r\nOptional Settings:\r\n    g:greputilsLidcmd, g:greputilsFindcmd, g:greputilsFiltercmd,\r\n    g:greputilsFindMsgFmt, g:greputilsAutoCopen, g:greputilsVimGrepCmd,\r\n    g:greputilsVimGrepAddCmd, g:greputilsGrepCompMode,\r\n    g:greputilsLidCompMode, g:greputilsFindCompMode,\r\n    g:greputilsExpandCurWord, g:greputilsVimGrepSepChar,\r\n    g:greputilsPreserveLastResults, g:greputilsPreserveAllResults,\r\n    g:greputilsPreviewCreateFolds\r\n                                                                           \r\n  - Use g:greputilsLidcmd and g:greputilsFiltercmd to set the path\/name to\r\n    the lid and GNU or compatible find executable (defaults to \"lid\").\r\n  - Use g:greputilsFiltercmd to set the path\/name of the command that you\r\n    would like to use as the filter when \"+f\" option is used (defaults to\r\n    \"grep\").\r\n  - Set g:greputilsFindMsgFmt to change the message (%m) part of the find\r\n    results. You can specify anything that is accepted in the argument for\r\n    \"-printf\" find option.\r\n  - Use g:greputilsAutoCopen to specify if the error list window should\r\n    automatically be opened or closed based on whether there are any\r\n    results or not (runs :cwindow command at the end).\r\n  - Use g:greputilsVimGrepCmd and g:greputilsVimGrepAddCmd to have the\r\n    plugin run a different command than the built-in :grep command to\r\n    generate the results. This is mainly useful to use the plugin as a\r\n    wrapper to finally invoke another plugin after the arguments are\r\n    escaped and 'shellpipe' is properly set. The callee typically can just\r\n    run the :grep command on the arguments and do additional setup.\r\n  - Use g:greputilsGrepCompMode, g:greputilsLidCompMode and\r\n    g:greputilsFindCompMode to change the completion mode for Grep, IDGrep\r\n    and Find commands respectively. The default completion mode for Grep\r\n    and Find are \"file\" to match that of the built-in commands, where as\r\n    it is set to \"tag\" for IDGrep (except the -f argument to specify an ID\r\n    file, you never need to pass filenam to lid). When completion mode is\r\n    \"file\", Vim automatically expands filename meta-characters such as \"%\"\r\n    and \"#\" on the command-line, so you still need to escape then. If this\r\n    is an issue for you, then you should switch to \"tag\" or a different\r\n    completion mode. When completion mode is not \"file\", the plugin\r\n    expands the filename meta characters in the file arguments anyway, and\r\n    this can be considered as an advantage (think about passing patterns\r\n    to the command literally). However it is still useful to have\r\n    \"<cword>\" and \"<cWORD>\" expand inside the patterns, in which case you\r\n    can set g:greputilsExpandCurWord setting.  Changing this option at\r\n    runtime requires you to reload the plugin.\r\n  - When completion mode is not set to \"file\", you can set\r\n    g:greputilsExpandCurWord to have the plugin expand \"<cword>\" and\r\n    \"<cWORD>\" tokens. This essentially gives you all the goodness of file\r\n    completion while still being able to do tag completions.\r\n  - For Vim built-in grep operations such as :BufGrep, if you want to\r\n    change the character sorrounding the pattern from the default '\/' to\r\n    something else (see |E146|), you can use the\r\n    g:greputilsVimGrepSepChar. This is useful if you have a lot of \"\/\"\r\n    characters in your pattern.\r\n  - The plugin normally preserves the previous results in the preview\r\n    window, which you can retrieve by doing an undo immediately after\r\n    generating the new results, inside the preview window. If you don't\r\n    like this, you can disable this feature by resetting\r\n    g:greputilsPreserveLastResults setting. You can instead set the\r\n    g:greputilsPreserveAllResults to preserve all the changes done in the\r\n    preview window, by user and the plugin itself.\r\n  - While using the *pAdd commands (that add results to preview window),\r\n    the individual set of results are folded together to be able to\r\n    identify them better. You can disable this feature by resetting the\r\n    g:greputilsPreviewCreateFolds setting.\r\n","first_name":"Hari Krishna","6":"Hari Krishna","last_name":"Dara","7":"Dara","releases":[{"0":"1062","vim_version":"6.0","1":"6.0","script_version":"2.8","2":"2.8","version_comment":"- Support for inversing the search pattern. You can pass \"!\" to built-in grep commands.\r\n- Fixed broken GrepBufs command.\r\n","3":"- Support for inversing the search pattern. You can pass \"!\" to built-in grep commands.\r\n- Fixed broken GrepBufs command.\r\n","package":"greputils.vim","4":"greputils.vim","src_id":"4434","5":"4434","creation_date":"1121365234","6":"1121365234"},{"0":"1062","vim_version":"6.0","1":"6.0","script_version":"2.7","2":"2.7","version_comment":"Fixed broken Cfile command.\r\n","3":"Fixed broken Cfile command.\r\n","package":"greputils.vim","4":"greputils.vim","src_id":"4433","5":"4433","creation_date":"1121356722","6":"1121356722"},{"0":"1062","vim_version":"6.0","1":"6.0","script_version":"2.6","2":"2.6","version_comment":"Just added support for specifying range for all the built-in grep commands. Useful mainly for GrepBufs command.\r\n","3":"Just added support for specifying range for all the built-in grep commands. Useful mainly for GrepBufs command.\r\n","package":"greputils.vim","4":"greputils.vim","src_id":"4432","5":"4432","creation_date":"1121355937","6":"1121355937"},{"0":"1062","vim_version":"6.0","1":"6.0","script_version":"2.5","2":"2.5","version_comment":"- Better handling of unsaved and unnamed buffers while doing built-in grep.\r\n- New setting g:greputilsPreserveAllResults to be able to undo over\r\n  several search results, as far as Vim allows you to do.\r\n- Better integration with selectbuf so that the built-in grep performs\r\n  better, if both plugins are installed (need to get the latest\r\n  selectbuf).\r\n- Much better handling of opening and closing preview window. Requires\r\n  the latest version genutils.vim.\r\n- Misc. bug fixes. Update documentation.\r\n","3":"- Better handling of unsaved and unnamed buffers while doing built-in grep.\r\n- New setting g:greputilsPreserveAllResults to be able to undo over\r\n  several search results, as far as Vim allows you to do.\r\n- Better integration with selectbuf so that the built-in grep performs\r\n  better, if both plugins are installed (need to get the latest\r\n  selectbuf).\r\n- Much better handling of opening and closing preview window. Requires\r\n  the latest version genutils.vim.\r\n- Misc. bug fixes. Update documentation.\r\n","package":"greputils.vim","4":"greputils.vim","src_id":"4035","5":"4035","creation_date":"1110982782","6":"1110982782"},{"0":"1062","vim_version":"6.0","1":"6.0","script_version":"2.4","2":"2.4","version_comment":"- Augmented the built-in grep (:WinGrep, :ArgGrep, :BufGrep)\r\n  functionality with the new command :GrepBufs to grep specified\r\n  buffers only. This is very similar to unix :grep command with given\r\n  filenames.\r\n- New commands :GOpen, :GClose and :GWindow on the lines of :copen,\r\n  :cclose and :cwindow to work with the preview window. The existing\r\n  commands :GNext, :GPrev and :GG commands now work globally, just like\r\n  the :cnext, :cprev and :cc commands.\r\n- Fixed misc. bugs.\r\n","3":"- Augmented the built-in grep (:WinGrep, :ArgGrep, :BufGrep)\r\n  functionality with the new command :GrepBufs to grep specified\r\n  buffers only. This is very similar to unix :grep command with given\r\n  filenames.\r\n- New commands :GOpen, :GClose and :GWindow on the lines of :copen,\r\n  :cclose and :cwindow to work with the preview window. The existing\r\n  commands :GNext, :GPrev and :GG commands now work globally, just like\r\n  the :cnext, :cprev and :cc commands.\r\n- Fixed misc. bugs.\r\n","package":"greputils.vim","4":"greputils.vim","src_id":"3560","5":"3560","creation_date":"1098124354","6":"1098124354"},{"0":"1062","vim_version":"6.0","1":"6.0","script_version":"2.3","2":"2.3","version_comment":"\t- Misc. improvements for Grep Preview window.\r\n\t  - The Grep Preview window now implements undo functionality to be able\r\n\t    to undo and recover the previous result set.\r\n\t  - When you add results to the existing results, the results sets are\r\n\t    folded such that you can easily distinguish them.\r\n\t  - Preview window shouldn't be resized if it is already visible.\r\n\t- The grep commands that utilize the Vim's built-in grep functionality\r\n\t  are refined and are more useful than ever.\r\n\t  - They now have command-line completion enabled to complete tags.\r\n\t  - <cword> and <cWORD> were not being expanded for Vim-grep\r\n\t    commands.\r\n\t  - Cleanup the grep window for \"pattern not found\" error messages and\r\n\t    such.\r\n\t  - The current buffer is restored at the end of the operation.\r\n\t  - Vim event generation is disabled. This provides a significant\r\n\t    improvement in the speed as well as avoid side effects. This along\r\n\t    with the above improvement also makes the grep operation look\r\n\t    completely tranparent.\r\n\t- New useful GrepPreviewSetup command.\r\n\t- On windows, setting multiple ID files in IDPATH doesn't work, as it\r\n\t  does on *NIX. The plugin works around this problem by invoking lid on\r\n\t  individual ID files and gathering all the results.\r\n\t- If you use findstr on windows, grepping on a single file doesn't\r\n\t  generate the results in the right format (no filename prefix etc.).\r\n\t  The plugin now works around this issue.\r\n\t- See help on new settings g:greputilsVimGrepSepChar,\r\n\t  g:greputilsPreviewCreateFolds and g:greputilsPreserveLastResults.\r\n","3":"\t- Misc. improvements for Grep Preview window.\r\n\t  - The Grep Preview window now implements undo functionality to be able\r\n\t    to undo and recover the previous result set.\r\n\t  - When you add results to the existing results, the results sets are\r\n\t    folded such that you can easily distinguish them.\r\n\t  - Preview window shouldn't be resized if it is already visible.\r\n\t- The grep commands that utilize the Vim's built-in grep functionality\r\n\t  are refined and are more useful than ever.\r\n\t  - They now have command-line completion enabled to complete tags.\r\n\t  - <cword> and <cWORD> were not being expanded for Vim-grep\r\n\t    commands.\r\n\t  - Cleanup the grep window for \"pattern not found\" error messages and\r\n\t    such.\r\n\t  - The current buffer is restored at the end of the operation.\r\n\t  - Vim event generation is disabled. This provides a significant\r\n\t    improvement in the speed as well as avoid side effects. This along\r\n\t    with the above improvement also makes the grep operation look\r\n\t    completely tranparent.\r\n\t- New useful GrepPreviewSetup command.\r\n\t- On windows, setting multiple ID files in IDPATH doesn't work, as it\r\n\t  does on *NIX. The plugin works around this problem by invoking lid on\r\n\t  individual ID files and gathering all the results.\r\n\t- If you use findstr on windows, grepping on a single file doesn't\r\n\t  generate the results in the right format (no filename prefix etc.).\r\n\t  The plugin now works around this issue.\r\n\t- See help on new settings g:greputilsVimGrepSepChar,\r\n\t  g:greputilsPreviewCreateFolds and g:greputilsPreserveLastResults.\r\n","package":"greputils.vim","4":"greputils.vim","src_id":"3364","5":"3364","creation_date":"1093040845","6":"1093040845"},{"0":"1062","vim_version":"6.0","1":"6.0","script_version":"6.2","2":"6.2","version_comment":"- Added BufGrep, WinGrep and ArgGrep commands that use the Vim's built-in g\/re\/p command with :bufdo, :windo and :argdo respectively to do search. This is an experimental feature, please try it and give feedback.\r\n- Also fixed a couple or more of minor bugs.\r\n","3":"- Added BufGrep, WinGrep and ArgGrep commands that use the Vim's built-in g\/re\/p command with :bufdo, :windo and :argdo respectively to do search. This is an experimental feature, please try it and give feedback.\r\n- Also fixed a couple or more of minor bugs.\r\n","package":"greputils.vim","4":"greputils.vim","src_id":"3363","5":"3363","creation_date":"1093040642","6":"1093040642"},{"0":"1062","vim_version":"6.0","1":"6.0","script_version":"2.1","2":"2.1","version_comment":"Requires Vim 6.3\r\n- Added support for running GNU find command and open the files from preview or through quickfix result.\r\n- Basic quickfix like commands have been added to the [Grep Preview] window. This is very useful if you want to quickly reach one or two files by running \"find\" or \"lid\" and don't care about the full results.\r\n- The default completion mode for grep has been changed to \"file\" from \"tag\", which is what is more useful.\r\n- Fixed :Cfile and :Cgetfile to work correctly if the current directory has changed since the results are generated.\r\n","3":"Requires Vim 6.3\r\n- Added support for running GNU find command and open the files from preview or through quickfix result.\r\n- Basic quickfix like commands have been added to the [Grep Preview] window. This is very useful if you want to quickly reach one or two files by running \"find\" or \"lid\" and don't care about the full results.\r\n- The default completion mode for grep has been changed to \"file\" from \"tag\", which is what is more useful.\r\n- Fixed :Cfile and :Cgetfile to work correctly if the current directory has changed since the results are generated.\r\n","package":"greputils.vim","4":"greputils.vim","src_id":"3362","5":"3362","creation_date":"1093040607","6":"1093040607"},{"0":"1062","vim_version":"6.0","1":"6.0","script_version":"2.0","2":"2.0","version_comment":"This is an enhanced version of idutils.vim, made more generic and supports regular :grep command too. See description for information on the new version. Needs Vim 6.3\r\n","3":"This is an enhanced version of idutils.vim, made more generic and supports regular :grep command too. See description for information on the new version. Needs Vim 6.3\r\n","package":"greputils.vim","4":"greputils.vim","src_id":"3361","5":"3361","creation_date":"1093040559","6":"1093040559"}]},"1061":{"script_id":"1061","0":"1061","script_name":"actionscript.vim","1":"actionscript.vim","script_type":"syntax","2":"syntax","summary":"ActionScript 3.0 syntax file","3":"ActionScript 3.0 syntax file","description":"Updated Igor Dvorsky's ActionScript 1.0 color syntax file vimscript #413 to include ActionScript 2.0 and ActionScript 3.0 keywords.","4":"Updated Igor Dvorsky's ActionScript 1.0 color syntax file vimscript #413 to include ActionScript 2.0 and ActionScript 3.0 keywords.","install_details":"ActionScript files end with \".as\" but by default that file type is associated with Atlas in filetype.vim. You should remove this association and create a new one for ActionScript .  ","5":"ActionScript files end with \".as\" but by default that file type is associated with Atlas in filetype.vim. You should remove this association and create a new one for ActionScript .  ","first_name":"Richard","6":"Richard","last_name":"Leider","7":"Leider","releases":[{"0":"1061","vim_version":"6.0","1":"6.0","script_version":"0.3","2":"0.3","version_comment":"Updated to include support for core ActionScript 3.0.","3":"Updated to include support for core ActionScript 3.0.","package":"actionscript.vim","4":"actionscript.vim","src_id":"10123","5":"10123","creation_date":"1236277884","6":"1236277884"},{"0":"1061","vim_version":"6.0","1":"6.0","script_version":"0.21","2":"0.21","version_comment":"Changed the way braces match so empty parentheses no longer show error color.  Thanks to Chris Miles for this fix.","3":"Changed the way braces match so empty parentheses no longer show error color.  Thanks to Chris Miles for this fix.","package":"actionscript.vim","4":"actionscript.vim","src_id":"4660","5":"4660","creation_date":"1128946252","6":"1128946252"},{"0":"1061","vim_version":"6.0","1":"6.0","script_version":"0.2","2":"0.2","version_comment":"Updated syntax file to include AS 2.0 Classes, Functions, Properties and Constants added in Flash 8.","3":"Updated syntax file to include AS 2.0 Classes, Functions, Properties and Constants added in Flash 8.","package":"actionscript.vim","4":"actionscript.vim","src_id":"4633","5":"4633","creation_date":"1128028687","6":"1128028687"},{"0":"1061","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"actionscript.vim","4":"actionscript.vim","src_id":"3354","5":"3354","creation_date":"1092912610","6":"1092912610"}]},"1060":{"script_id":"1060","0":"1060","script_name":"Vive.vim","1":"Vive.vim","script_type":"utility","2":"utility","summary":"Single or multi line Vim script code executed with a keystroke","3":"Single or multi line Vim script code executed with a keystroke","description":"Enter Vim script code, multi or single line, and have it executed with a single key stroke.  Results are captured and entered into the buffer for examination. For proto-typing, learning, scratchpad, testing, and other uses.  See http:\/\/dsilvia.home.mchsi.com for doc","4":"Enter Vim script code, multi or single line, and have it executed with a single key stroke.  Results are captured and entered into the buffer for examination. For proto-typing, learning, scratchpad, testing, and other uses.  See http:\/\/dsilvia.home.mchsi.com for doc","install_details":"NOTE: REQUIRES vsutil_vim.zip http:\/\/www.vim.org\/scripts\/script.php?script_id=1056\r\nUnzip into your .vim|vimfiles directory","5":"NOTE: REQUIRES vsutil_vim.zip http:\/\/www.vim.org\/scripts\/script.php?script_id=1056\r\nUnzip into your .vim|vimfiles directory","first_name":"Dave","6":"Dave","last_name":"Silvia","7":"Silvia","releases":[{"0":"1060","vim_version":"6.0","1":"6.0","script_version":"2.0.1","2":"2.0.1","version_comment":"Added:\r\n -  Check for VSUTIL\r\n -  save of cpoptions and reset\r\n    after removing C to allow\r\n    continuation lines\r\nFixed:\r\n  -  Continuation lines\r\n    in input script.","3":"Added:\r\n -  Check for VSUTIL\r\n -  save of cpoptions and reset\r\n    after removing C to allow\r\n    continuation lines\r\nFixed:\r\n  -  Continuation lines\r\n    in input script.","package":"Vive_vim.zip","4":"Vive_vim.zip","src_id":"3521","5":"3521","creation_date":"1096960074","6":"1096960074"},{"0":"1060","vim_version":"6.0","1":"6.0","script_version":"2.0","2":"2.0","version_comment":"Version 2.0\r\nDate:        9\/21\/2004\r\n Added:\r\n   -  Menu item for Read Script\r\n   -  Menu item for Execute Script\r\n   -  Menu item Vim verbose mode\r\n   -  Menu item for debug mode\r\n","3":"Version 2.0\r\nDate:        9\/21\/2004\r\n Added:\r\n   -  Menu item for Read Script\r\n   -  Menu item for Execute Script\r\n   -  Menu item Vim verbose mode\r\n   -  Menu item for debug mode\r\n","package":"Vive_vim.zip","4":"Vive_vim.zip","src_id":"3466","5":"3466","creation_date":"1095821188","6":"1095821188"},{"0":"1060","vim_version":"6.0","1":"6.0","script_version":"1.3","2":"1.3","version_comment":"Version 1.3\r\n Fixed:\r\n   -  If command opens new edit\r\n      buffers, be sure to return\r\n      to the Vive window\/buffer\r\n      on completion of ViveFunc","3":"Version 1.3\r\n Fixed:\r\n   -  If command opens new edit\r\n      buffers, be sure to return\r\n      to the Vive window\/buffer\r\n      on completion of ViveFunc","package":"Vive_vim.zip","4":"Vive_vim.zip","src_id":"3379","5":"3379","creation_date":"1093356926","6":"1093356926"},{"0":"1060","vim_version":"6.0","1":"6.0","script_version":"1.2","2":"1.2","version_comment":"Version 1.2\r\n Fixed:\r\n   -  If command\/function\/script\r\n      invoked from outside Vive\r\n      requested input, Vive would\r\n      halt with no indication.\r\n      Removed 'silent' from Vive\r\n      function call to correct.\r\n    - If first command contained\r\n      :r, redirect to g:ViveFile\r\n      would trip a Warning message\r\n      about appending to a readonly\r\n      file, but _only_ on the first\r\n      command.  Now we do a :r\r\n      command at startup to\r\n      eliminate the problem.\r\n      Not sure why this happens,\r\n      it just does!:-<","3":"Version 1.2\r\n Fixed:\r\n   -  If command\/function\/script\r\n      invoked from outside Vive\r\n      requested input, Vive would\r\n      halt with no indication.\r\n      Removed 'silent' from Vive\r\n      function call to correct.\r\n    - If first command contained\r\n      :r, redirect to g:ViveFile\r\n      would trip a Warning message\r\n      about appending to a readonly\r\n      file, but _only_ on the first\r\n      command.  Now we do a :r\r\n      command at startup to\r\n      eliminate the problem.\r\n      Not sure why this happens,\r\n      it just does!:-<","package":"Vive_vim.zip","4":"Vive_vim.zip","src_id":"3355","5":"3355","creation_date":"1092932887","6":"1092932887"},{"0":"1060","vim_version":"6.0","1":"6.0","script_version":"1.1c","2":"1.1c","version_comment":"Incorporated documentation\r\nsuggestions from Peter Yang","3":"Incorporated documentation\r\nsuggestions from Peter Yang","package":"Vive_vim.zip","4":"Vive_vim.zip","src_id":"3353","5":"3353","creation_date":"1092894889","6":"1092894889"},{"0":"1060","vim_version":"6.0","1":"6.0","script_version":"1.1b","2":"1.1b","version_comment":"Added documentation","3":"Added documentation","package":"Vive_vim.zip","4":"Vive_vim.zip","src_id":"3352","5":"3352","creation_date":"1092889497","6":"1092889497"},{"0":"1060","vim_version":"6.0","1":"6.0","script_version":"1.1","2":"1.1","version_comment":"Version 1.1\r\n  Fixed:\r\n    -  Problem with multiple windows\r\n       putting the 'Results:' label\r\n       in the wrong window.\r\n  Added:\r\n    -  Some new command line switches\r\n    -  Performance enhancements","3":"Version 1.1\r\n  Fixed:\r\n    -  Problem with multiple windows\r\n       putting the 'Results:' label\r\n       in the wrong window.\r\n  Added:\r\n    -  Some new command line switches\r\n    -  Performance enhancements","package":"Vive.vim","4":"Vive.vim","src_id":"3351","5":"3351","creation_date":"1092848128","6":"1092848128"},{"0":"1060","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"Vive.vim","4":"Vive.vim","src_id":"3349","5":"3349","creation_date":"1092772147","6":"1092772147"}]},"1059":{"script_id":"1059","0":"1059","script_name":"pygtk_color","1":"pygtk_color","script_type":"utility","2":"utility","summary":"PyGtk2 color selection dialog","3":"PyGtk2 color selection dialog","description":"This will add a menu item in gvim called 'Color' that will allow you to insert a web style hex color value (like '#ffffff'), or python RGB tuple (like (255,255,255) ) after the current line (if you know how to insert at current position, send me an email: david.konsumer at gmail. )\r\n\r\nScreenshot: http:\/\/konsumer.memebot.com\/vim_color_select.png\r\n\r\nIncluded is a python script called 'color_select' that requires pygtk.\r\n\r\nIn windows, you could write one using VB, or install python and pygtk to use it.\r\n\r\nMaybe eventually I'll write a wxwindows dialog for everybody.\r\n\r\nThe reason I did this, instead of using http:\/\/www.vim.org\/scripts\/script.php?script_id=927 was that I wanted to be able to grab color values from the screen, and I like the gtk2 color dialog alot.\r\n\r\nI tested this on Debian unstable with gvim 6.3, python  2.3.4 and pygtk 2.","4":"This will add a menu item in gvim called 'Color' that will allow you to insert a web style hex color value (like '#ffffff'), or python RGB tuple (like (255,255,255) ) after the current line (if you know how to insert at current position, send me an email: david.konsumer at gmail. )\r\n\r\nScreenshot: http:\/\/konsumer.memebot.com\/vim_color_select.png\r\n\r\nIncluded is a python script called 'color_select' that requires pygtk.\r\n\r\nIn windows, you could write one using VB, or install python and pygtk to use it.\r\n\r\nMaybe eventually I'll write a wxwindows dialog for everybody.\r\n\r\nThe reason I did this, instead of using http:\/\/www.vim.org\/scripts\/script.php?script_id=927 was that I wanted to be able to grab color values from the screen, and I like the gtk2 color dialog alot.\r\n\r\nI tested this on Debian unstable with gvim 6.3, python  2.3.4 and pygtk 2.","install_details":"On linux, Put color_select in your path and chmod 755 it.\r\nPut pygtk_color.vim into your plugin folder (~\/.vim\/plugin\/ or \/usr\/share\/vim\/vim63\/plugin\/ for me.)","5":"On linux, Put color_select in your path and chmod 755 it.\r\nPut pygtk_color.vim into your plugin folder (~\/.vim\/plugin\/ or \/usr\/share\/vim\/vim63\/plugin\/ for me.)","first_name":"David","6":"David","last_name":"Konsumer","7":"Konsumer","releases":[{"0":"1059","vim_version":"6.0","1":"6.0","script_version":"1","2":"1","version_comment":"Initial upload","3":"Initial upload","package":"pygtk_color.tgz","4":"pygtk_color.tgz","src_id":"3348","5":"3348","creation_date":"1092766454","6":"1092766454"}]},"1058":{"script_id":"1058","0":"1058","script_name":"Menu Autohide","1":"Menu Autohide","script_type":"utility","2":"utility","summary":"A plugin to hide the menubar when the window shrinks.","3":"A plugin to hide the menubar when the window shrinks.","description":"This plugin hides the GUI menu bar when the window is reduced to just a few lines and shows it again when the window is made larger.\r\n\r\nThis behavior can significantly save on screen space when you're in the habit of temporarily collecting random information in a new vim which then gets stuffed into a corner of the screen.\r\n\r\n","4":"This plugin hides the GUI menu bar when the window is reduced to just a few lines and shows it again when the window is made larger.\r\n\r\nThis behavior can significantly save on screen space when you're in the habit of temporarily collecting random information in a new vim which then gets stuffed into a corner of the screen.\r\n\r\n","install_details":"Copy into your .vim\/plugin\/ directory.","5":"Copy into your .vim\/plugin\/ directory.","first_name":"Peter","6":"Peter","last_name":"Wilson","7":"Wilson","releases":[{"0":"1058","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"menu-autohide.vim","4":"menu-autohide.vim","src_id":"3345","5":"3345","creation_date":"1092761740","6":"1092761740"}]},"1057":{"script_id":"1057","0":"1057","script_name":"DavesVimPack","1":"DavesVimPack","script_type":"utility","2":"utility","summary":"Not Very Popular: Bad Reviews","3":"Not Very Popular: Bad Reviews","description":"BYE-BYE!  WE GONE!\r\n","4":"BYE-BYE!  WE GONE!\r\n","install_details":"","5":"","first_name":"Dave","6":"Dave","last_name":"Silvia","7":"Silvia","releases":[{"0":"1057","vim_version":"6.0","1":"6.0","script_version":"0.0","2":"0.0","version_comment":"DEFUNCT BY POPULAR DEMAND!","3":"DEFUNCT BY POPULAR DEMAND!","package":"DavesVimPack.txt","4":"DavesVimPack.txt","src_id":"3356","5":"3356","creation_date":"1092934511","6":"1092934511"}]},"1056":{"script_id":"1056","0":"1056","script_name":"vsutil.vim","1":"vsutil.vim","script_type":"utility","2":"utility","summary":"function primitives for Vim scripts.","3":"function primitives for Vim scripts.","description":"Primitive functions for Vim Scripts.  Used by various of my Vim Scripts.  See doc\/vsutil.[html|rtf|ans|txt|doc] for detailed information.","4":"Primitive functions for Vim Scripts.  Used by various of my Vim Scripts.  See doc\/vsutil.[html|rtf|ans|txt|doc] for detailed information.","install_details":"unzip in .vim|vimfiles","5":"unzip in .vim|vimfiles","first_name":"Dave","6":"Dave","last_name":"Silvia","7":"Silvia","releases":[{"0":"1056","vim_version":"6.0","1":"6.0","script_version":"1.4","2":"1.4","version_comment":"Added:\r\n -  g:VSUTIL, g:VSUTILMAJ, g:VSUTILMIN","3":"Added:\r\n -  g:VSUTIL, g:VSUTILMAJ, g:VSUTILMIN","package":"vsutil.vim","4":"vsutil.vim","src_id":"3516","5":"3516","creation_date":"1096848112","6":"1096848112"},{"0":"1056","vim_version":"6.0","1":"6.0","script_version":"1.3.1 beta","2":"1.3.1 beta","version_comment":"Additions for VimRegEx\r\nNo doc update yet\r\nUse previous package for\r\ndocumentation","3":"Additions for VimRegEx\r\nNo doc update yet\r\nUse previous package for\r\ndocumentation","package":"vsutil.vim","4":"vsutil.vim","src_id":"3494","5":"3494","creation_date":"1096323960","6":"1096323960"},{"0":"1056","vim_version":"6.0","1":"6.0","script_version":"1.3","2":"1.3","version_comment":"Version 1.3\r\nDate:        9\/24\/2004\r\n Modified:\r\n  -  IsStrLit() now returns 1 for single\r\n     quotes and 2 for double quotes\r\n New:\r\n  -  Added ExpandDosEnvVar()","3":"Version 1.3\r\nDate:        9\/24\/2004\r\n Modified:\r\n  -  IsStrLit() now returns 1 for single\r\n     quotes and 2 for double quotes\r\n New:\r\n  -  Added ExpandDosEnvVar()","package":"vsutil_vim.zip","4":"vsutil_vim.zip","src_id":"3485","5":"3485","creation_date":"1096058066","6":"1096058066"},{"0":"1056","vim_version":"6.0","1":"6.0","script_version":"1.2","2":"1.2","version_comment":"Added Substrmatch() and RelativePath()\r\nSee docs for details","3":"Added Substrmatch() and RelativePath()\r\nSee docs for details","package":"vsutil_vim.zip","4":"vsutil_vim.zip","src_id":"3462","5":"3462","creation_date":"1095541490","6":"1095541490"},{"0":"1056","vim_version":"6.0","1":"6.0","script_version":"1.1","2":"1.1","version_comment":"Initial upload","3":"Initial upload","package":"vsutil_vim.zip","4":"vsutil_vim.zip","src_id":"3331","5":"3331","creation_date":"1092415019","6":"1092415019"}]},"1055":{"script_id":"1055","0":"1055","script_name":"curBuf.vim","1":"curBuf.vim","script_type":"utility","2":"utility","summary":"source\/execute current file from toolbar or function key","3":"source\/execute current file from toolbar or function key","description":"Defines commands and key mappings for vim\/gvim, and gvim toolbar icons and menu entries for sourcing or executing the current buffer's file.  Completely configurable from your vimrc.","4":"Defines commands and key mappings for vim\/gvim, and gvim toolbar icons and menu entries for sourcing or executing the current buffer's file.  Completely configurable from your vimrc.","install_details":"unzip into vimfiles","5":"unzip into vimfiles","first_name":"Dave","6":"Dave","last_name":"Silvia","7":"Silvia","releases":[{"0":"1055","vim_version":"6.0","1":"6.0","script_version":"1.1","2":"1.1","version_comment":"Initial upload","3":"Initial upload","package":"curBuf_vim.zip","4":"curBuf_vim.zip","src_id":"3327","5":"3327","creation_date":"1092414327","6":"1092414327"}]},"1054":{"script_id":"1054","0":"1054","script_name":"InteractHL.vim","1":"InteractHL.vim","script_type":"utility","2":"utility","summary":"Interactively generate colorscheme or syncolor.vim","3":"Interactively generate colorscheme or syncolor.vim","description":"Commands:\r\n  Syncolor\r\n    creates syncolor.vim file\r\n  ColorScheme bg name\r\n    creates <name>.vim file with colorscheme header setting background='<bg>' [dark|light] and\r\n    colors_name='<name>'\r\n  IactHl\r\n    creates Hilite.vim file\r\n\r\nFiles are created in g:HiliteFilesDir, default '~'\r\n\r\nUtility to interactively create highlight commands file (syncolor.vim|<name>.vim|Hilite.vim) which can be copied to appropriate  runtimepath directory as for automatic execution at Vim startup.  Previous settings are saved in a file named 'yymmddhhmmssHilite.vim'.\r\nUse: ?? for online key mapping reference.\r\n\r\nThe utility opens 3 windows, the top window displays the major highlight groups with their names highlighted according to the current settings.  The middle window lists the highlight commands currently in effect to produce the output shown in the top window.  The bottom window lists the RGB names available for the current Vim release.\r\n\r\nPlace the cursor on the line you wish to modify in the middle window.  Place the cursor on the RGB value you want in the bottom window.  Use the mapped key sequences to set the line.  The key sequences are:\r\n\r\nfg   Set foreground to RGB value\r\nbg  Set background to RGB value\r\nno  Set attributes to 'NONE'\r\nbo  Add 'bold' to attributes\r\nit    Add 'italic' to attributes\r\nre   Add 'reverse' to attributes\r\nst   Add 'standout' to attributes\r\nun  Add 'underline' to attributes","4":"Commands:\r\n  Syncolor\r\n    creates syncolor.vim file\r\n  ColorScheme bg name\r\n    creates <name>.vim file with colorscheme header setting background='<bg>' [dark|light] and\r\n    colors_name='<name>'\r\n  IactHl\r\n    creates Hilite.vim file\r\n\r\nFiles are created in g:HiliteFilesDir, default '~'\r\n\r\nUtility to interactively create highlight commands file (syncolor.vim|<name>.vim|Hilite.vim) which can be copied to appropriate  runtimepath directory as for automatic execution at Vim startup.  Previous settings are saved in a file named 'yymmddhhmmssHilite.vim'.\r\nUse: ?? for online key mapping reference.\r\n\r\nThe utility opens 3 windows, the top window displays the major highlight groups with their names highlighted according to the current settings.  The middle window lists the highlight commands currently in effect to produce the output shown in the top window.  The bottom window lists the RGB names available for the current Vim release.\r\n\r\nPlace the cursor on the line you wish to modify in the middle window.  Place the cursor on the RGB value you want in the bottom window.  Use the mapped key sequences to set the line.  The key sequences are:\r\n\r\nfg   Set foreground to RGB value\r\nbg  Set background to RGB value\r\nno  Set attributes to 'NONE'\r\nbo  Add 'bold' to attributes\r\nit    Add 'italic' to attributes\r\nre   Add 'reverse' to attributes\r\nst   Add 'standout' to attributes\r\nun  Add 'underline' to attributes","install_details":"NOTE:  REQUIRES vsutil_vim.zip http:\/\/www.vim.org\/scripts\/script.php?script_id=1056\r\nunzip into vimfiles.","5":"NOTE:  REQUIRES vsutil_vim.zip http:\/\/www.vim.org\/scripts\/script.php?script_id=1056\r\nunzip into vimfiles.","first_name":"Dave","6":"Dave","last_name":"Silvia","7":"Silvia","releases":[{"0":"1054","vim_version":"6.0","1":"6.0","script_version":"1.2b","2":"1.2b","version_comment":"minor fix.  Added '^' to search for highlight keyword in top window so that exact match for highlight is displayed.","3":"minor fix.  Added '^' to search for highlight keyword in top window so that exact match for highlight is displayed.","package":"interactHL_vim.zip","4":"interactHL_vim.zip","src_id":"3443","5":"3443","creation_date":"1094956745","6":"1094956745"},{"0":"1054","vim_version":"6.0","1":"6.0","script_version":"1.2","2":"1.2","version_comment":"Version 1.1\r\n  Added:\r\n    -  g:HiliteFilesDir global\r\n    -  added Syncolor command\r\n       to have generated file\r\n       named 'syncolor.vim'\r\n    -  added ColorScheme command\r\n       which takes 2 arguments.\r\n       1) bg - light|dark\r\n       2) name - for colors_name=\r\n          and file <name>.vim\r\n","3":"Version 1.1\r\n  Added:\r\n    -  g:HiliteFilesDir global\r\n    -  added Syncolor command\r\n       to have generated file\r\n       named 'syncolor.vim'\r\n    -  added ColorScheme command\r\n       which takes 2 arguments.\r\n       1) bg - light|dark\r\n       2) name - for colors_name=\r\n          and file <name>.vim\r\n","package":"interactHL_vim.zip","4":"interactHL_vim.zip","src_id":"3401","5":"3401","creation_date":"1094011508","6":"1094011508"},{"0":"1054","vim_version":"6.0","1":"6.0","script_version":"1.1 b","2":"1.1 b","version_comment":"decoupled vsutil.vim.\r\nvsutil.vim is now a separate package","3":"decoupled vsutil.vim.\r\nvsutil.vim is now a separate package","package":"InteractHL_vim.zip","4":"InteractHL_vim.zip","src_id":"3328","5":"3328","creation_date":"1092414530","6":"1092414530"},{"0":"1054","vim_version":"6.0","1":"6.0","script_version":"1.1 zip","2":"1.1 zip","version_comment":"Added code to search\r\nfor rgb.txt.  If not found,\r\nuse rbg.txt included with\r\nthe zip.  If that's not there\r\neither, abort with echoerr","3":"Added code to search\r\nfor rgb.txt.  If not found,\r\nuse rbg.txt included with\r\nthe zip.  If that's not there\r\neither, abort with echoerr","package":"InteractHL_vim.zip","4":"InteractHL_vim.zip","src_id":"3325","5":"3325","creation_date":"1092403847","6":"1092403847"},{"0":"1054","vim_version":"6.0","1":"6.0","script_version":"1.0 zip b","2":"1.0 zip b","version_comment":"corrected vsutil.vim SortR","3":"corrected vsutil.vim SortR","package":"InteractHL_vim.zip","4":"InteractHL_vim.zip","src_id":"3323","5":"3323","creation_date":"1092397935","6":"1092397935"},{"0":"1054","vim_version":"6.0","1":"6.0","script_version":"1.0 zip","2":"1.0 zip","version_comment":"Made zip file containing\r\nvsuitl.vim also for utility\r\nfunctions used by IactHl","3":"Made zip file containing\r\nvsuitl.vim also for utility\r\nfunctions used by IactHl","package":"InteractHL_vim.zip","4":"InteractHL_vim.zip","src_id":"3321","5":"3321","creation_date":"1092394413","6":"1092394413"},{"0":"1054","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"interactHL.vim","4":"interactHL.vim","src_id":"3319","5":"3319","creation_date":"1092361513","6":"1092361513"}]},"1053":{"script_id":"1053","0":"1053","script_name":"browser.vim","1":"browser.vim","script_type":"utility","2":"utility","summary":"web browser plugin","3":"web browser plugin","description":"This plugin provides vim with web browsing and html formatting capabilities. \nIt includes support for history, bookmarks, text highlighting and more. The \nmain motivation is browsing documentation available in html, so don't expect \nto see any flash animation :)\r\n\r\nThe plugin is implemented using vim's ability to embed perl, so you will \r\nneed to have a perl enabled version of vim to use it. In addition, several \r\nperl modules are required. The full details are in the INSTALL file.\r\n\r\nDocumentation is available in pod form in 'browser.pod', and as a usual vim \r\nhelp file.\r\n\r\nI wrote and tested it with vim version 6.3 and perl 5.8.4 on linux. I expect \r\nit to work on any variant of unix. An effort was made to make it work on other \r\nplatforms as well, but this remains mostly untested.\r\n\r\nPlease send me any feedback.\r\n\r\nEnjoy!\r\n","4":"This plugin provides vim with web browsing and html formatting capabilities. \nIt includes support for history, bookmarks, text highlighting and more. The \nmain motivation is browsing documentation available in html, so don't expect \nto see any flash animation :)\r\n\r\nThe plugin is implemented using vim's ability to embed perl, so you will \r\nneed to have a perl enabled version of vim to use it. In addition, several \r\nperl modules are required. The full details are in the INSTALL file.\r\n\r\nDocumentation is available in pod form in 'browser.pod', and as a usual vim \r\nhelp file.\r\n\r\nI wrote and tested it with vim version 6.3 and perl 5.8.4 on linux. I expect \r\nit to work on any variant of unix. An effort was made to make it work on other \r\nplatforms as well, but this remains mostly untested.\r\n\r\nPlease send me any feedback.\r\n\r\nEnjoy!\r\n","install_details":"unpack using\r\n\r\ntar -xzvf browse-<ver>.tar.gz\r\n\r\nand then follow the INSTALL file. You will also need the synmark.vim plugin, \nvimscript #1128\n","5":"unpack using\r\n\r\ntar -xzvf browse-<ver>.tar.gz\r\n\r\nand then follow the INSTALL file. You will also need the synmark.vim plugin, \nvimscript #1128\n","first_name":"moshe","6":"moshe","last_name":"kamensky","7":"kamensky","releases":[{"0":"1053","vim_version":"6.0","1":"6.0","script_version":"1.1","2":"1.1","version_comment":"Mainly bug fixes. New features:\n\n- Added the uri history:\/\/n to access the n-th newest item in the history. \n  Similarly, the :History command may now accecpt a numeric argument.\n- The last access time for each link now appears on the history page\n- Added the g:browser_connect_timeout variable to control when we give up \n  connecting to a remote site\n- Added support for homepage in the plugin. :Browse and similar commands can \n  now be called with no arguments.\n- Changed the loading of the plugin so that vim startup time is improved.\n- Added a command for showing the current mappings, and a command to extend \n  this list for user defined mappings\n","3":"Mainly bug fixes. New features:\n\n- Added the uri history:\/\/n to access the n-th newest item in the history. \n  Similarly, the :History command may now accecpt a numeric argument.\n- The last access time for each link now appears on the history page\n- Added the g:browser_connect_timeout variable to control when we give up \n  connecting to a remote site\n- Added support for homepage in the plugin. :Browse and similar commands can \n  now be called with no arguments.\n- Changed the loading of the plugin so that vim startup time is improved.\n- Added a command for showing the current mappings, and a command to extend \n  this list for user defined mappings\n","package":"browser-1.1.tar.gz","4":"browser-1.1.tar.gz","src_id":"4025","5":"4025","creation_date":"1110889977","6":"1110889977"},{"0":"1053","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"* Added a sidebar\n* Added context menu entries\n* Support for opening links with external applications (using mailcap)\n* The conceal patch is no longer used. The synmark.vim plugin is used \ninstead.\n* Global browsing history\n* Both history and bookmarks can be viewed as browser pages\n* More support for inline images (viewing, etc.)\n* Page can be updated when modifying its source\n* Use vim commands as scheme handlers\n* Some improvements to standalone versions (vimbrowse)\n* Improved documentation, added glossary","3":"* Added a sidebar\n* Added context menu entries\n* Support for opening links with external applications (using mailcap)\n* The conceal patch is no longer used. The synmark.vim plugin is used \ninstead.\n* Global browsing history\n* Both history and bookmarks can be viewed as browser pages\n* More support for inline images (viewing, etc.)\n* Page can be updated when modifying its source\n* Use vim commands as scheme handlers\n* Some improvements to standalone versions (vimbrowse)\n* Improved documentation, added glossary","package":"browser-1.0.tar.gz","4":"browser-1.0.tar.gz","src_id":"3654","5":"3654","creation_date":"1101288622","6":"1101288622"},{"0":"1053","vim_version":"6.0","1":"6.0","script_version":"0.4","2":"0.4","version_comment":"Main Improvements:\n  - Added support for all inputs in a form (file, textarea, multi-options)\n  - Improved searching capabilities: Added the possibility to customize the \n    search engine, added :Dictionary and :Thesaurus commands. The searching \n    commands can now have no arguments, taking the word under the cursor, or  \n    the visaully select words as arguments, instead (Thanks to Aditya Mahajan \n    for the ideas)\n  - The browser buffer is now non-modifiable by default. It becomes \n    modifiable only when changing form input values (again thanks to Aditya \n    Mahajan)\n  - Added the possibility to save inline images to a file\n  - Removed the dependence on HTML-Format. The only dependency that remains \n    for formatting is HTML::TreeBuilder (which is more widely available).\n  - There is no longer need to patch HTML::TreeBuilder to view encodings \n    correctly.\n  - I think vimbrowse.pl finally works on windows (didn't test, though). Some \n    environment variables might need to be set.\n  - Various other features and bug fixes - see the ChangeLog for details\n","3":"Main Improvements:\n  - Added support for all inputs in a form (file, textarea, multi-options)\n  - Improved searching capabilities: Added the possibility to customize the \n    search engine, added :Dictionary and :Thesaurus commands. The searching \n    commands can now have no arguments, taking the word under the cursor, or  \n    the visaully select words as arguments, instead (Thanks to Aditya Mahajan \n    for the ideas)\n  - The browser buffer is now non-modifiable by default. It becomes \n    modifiable only when changing form input values (again thanks to Aditya \n    Mahajan)\n  - Added the possibility to save inline images to a file\n  - Removed the dependence on HTML-Format. The only dependency that remains \n    for formatting is HTML::TreeBuilder (which is more widely available).\n  - There is no longer need to patch HTML::TreeBuilder to view encodings \n    correctly.\n  - I think vimbrowse.pl finally works on windows (didn't test, though). Some \n    environment variables might need to be set.\n  - Various other features and bug fixes - see the ChangeLog for details\n","package":"browser-0.4.tar.gz","4":"browser-0.4.tar.gz","src_id":"3489","5":"3489","creation_date":"1096200797","6":"1096200797"},{"0":"1053","vim_version":"6.0","1":"6.0","script_version":"0.3.1","2":"0.3.1","version_comment":"Fixed silly bug","3":"Fixed silly bug","package":"browser-0.3.1.tar.gz","4":"browser-0.3.1.tar.gz","src_id":"3459","5":"3459","creation_date":"1095406318","6":"1095406318"},{"0":"1053","vim_version":"6.0","1":"6.0","script_version":"0.3","2":"0.3","version_comment":"Bugfix release: encoding works correctly; setting options has effect also after \r\nthe plugin is loaded; Various other fixes - see the ChangeLog for details","3":"Bugfix release: encoding works correctly; setting options has effect also after \r\nthe plugin is loaded; Various other fixes - see the ChangeLog for details","package":"browser-0.3.tar.gz","4":"browser-0.3.tar.gz","src_id":"3458","5":"3458","creation_date":"1095404062","6":"1095404062"},{"0":"1053","vim_version":"6.0","1":"6.0","script_version":"0.2","2":"0.2","version_comment":"Main Improvements:\r\n\t- Added forms support. All input kinds are supported except for \r\n\t  textarea, file and multiple choice options. Thus, eg, google can be \r\n\t  used\r\n\t- Made less system dependent. No known system dependent parts   remain.  Most features should now work on any platform. Partially tested on windows, thanks to Suresh Govindachar.\r\n\t- A command line (perl) script, 'vimbrowse.pl', now allows lunching \r\n\t  vim as a browser from the command line.\r\n\t- Numerous bugs were fixed.\r\n\r\nSee the file 'ChangeLog' for some more details","3":"Main Improvements:\r\n\t- Added forms support. All input kinds are supported except for \r\n\t  textarea, file and multiple choice options. Thus, eg, google can be \r\n\t  used\r\n\t- Made less system dependent. No known system dependent parts   remain.  Most features should now work on any platform. Partially tested on windows, thanks to Suresh Govindachar.\r\n\t- A command line (perl) script, 'vimbrowse.pl', now allows lunching \r\n\t  vim as a browser from the command line.\r\n\t- Numerous bugs were fixed.\r\n\r\nSee the file 'ChangeLog' for some more details","package":"browser-0.2.tar.gz","4":"browser-0.2.tar.gz","src_id":"3426","5":"3426","creation_date":"1094345881","6":"1094345881"},{"0":"1053","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Fixed the INSTALL file - forgot one dependancy","3":"Fixed the INSTALL file - forgot one dependancy","package":"browser-0.1.tar.gz","4":"browser-0.1.tar.gz","src_id":"3311","5":"3311","creation_date":"1092095635","6":"1092095635"},{"0":"1053","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"browser-0.1.tar.gz","4":"browser-0.1.tar.gz","src_id":"3310","5":"3310","creation_date":"1092094690","6":"1092094690"}]},"1052":{"script_id":"1052","0":"1052","script_name":"The Mail Suite (tms)","1":"The Mail Suite (tms)","script_type":"utility","2":"utility","summary":"Send, Receive and Organize mail from within VIM","3":"Send, Receive and Organize mail from within VIM","description":"____________________________________________________________\r\nThe Mail Suite (TMS):  Send, Receive and Organize Mail\r\n                       via an Editable User Interface (EUI)\r\n                       using VIM As the Editor\r\n                       (on WINDOWS and on Unix)\r\n                       (relies on perl)\r\n____________________________________________________________\r\nMotivation    \r\n\r\nPeople who know VIM (especially those who have discovered\r\nexplorer.vim) are aware of the speed, the customized form\r\nand, once learned, the ease of issuing commands and\r\nprocessing the results of the commands while in VIM.  This\r\nplugin, The Mail Suite (tms), exploits that power of VIM in\r\nthe domain of electronic mail: for the tasks of sending,\r\nreceiving and organizing mail.\r\n\r\n____________________________________________________________\r\nThe Command Set (Overview) \r\n\r\nSince The Mail Suite builds on VIM's command set, there are\r\nonly a handful of new commands (or tasks):\r\n\r\n   - Get emails (from a POP3 server) and save in raw (.eml) format\r\n   - Send a buffer (even one without a file) or files as an email (via a SMTP server)\r\n   - Index (create a ''table of contents'' for) a folder of emails\r\n   - Open an email from the index (and then open the next or the previous email)\r\n   - Reply, Forward or Acknowledge an email\r\n   - Delete, Move or Copy emails\r\n\r\n____________________________________________________________\r\nContrast of Interfaces for Mail Clients \r\n\r\nHere's a contrast that makes an aspect of the power of VIM\r\nas a user interface clear:  other email clients need lots\r\nmore commands than the mail-specific commands listed above\r\nsince they need to provide a user interface;  and their\r\ninterface is restrictive (compared to that of VIM) in regard\r\nto the means for navigating and manipulating the stuff on\r\nthe screen and in not allowing keystroke customization.\r\n\r\n","4":"____________________________________________________________\r\nThe Mail Suite (TMS):  Send, Receive and Organize Mail\r\n                       via an Editable User Interface (EUI)\r\n                       using VIM As the Editor\r\n                       (on WINDOWS and on Unix)\r\n                       (relies on perl)\r\n____________________________________________________________\r\nMotivation    \r\n\r\nPeople who know VIM (especially those who have discovered\r\nexplorer.vim) are aware of the speed, the customized form\r\nand, once learned, the ease of issuing commands and\r\nprocessing the results of the commands while in VIM.  This\r\nplugin, The Mail Suite (tms), exploits that power of VIM in\r\nthe domain of electronic mail: for the tasks of sending,\r\nreceiving and organizing mail.\r\n\r\n____________________________________________________________\r\nThe Command Set (Overview) \r\n\r\nSince The Mail Suite builds on VIM's command set, there are\r\nonly a handful of new commands (or tasks):\r\n\r\n   - Get emails (from a POP3 server) and save in raw (.eml) format\r\n   - Send a buffer (even one without a file) or files as an email (via a SMTP server)\r\n   - Index (create a ''table of contents'' for) a folder of emails\r\n   - Open an email from the index (and then open the next or the previous email)\r\n   - Reply, Forward or Acknowledge an email\r\n   - Delete, Move or Copy emails\r\n\r\n____________________________________________________________\r\nContrast of Interfaces for Mail Clients \r\n\r\nHere's a contrast that makes an aspect of the power of VIM\r\nas a user interface clear:  other email clients need lots\r\nmore commands than the mail-specific commands listed above\r\nsince they need to provide a user interface;  and their\r\ninterface is restrictive (compared to that of VIM) in regard\r\nto the means for navigating and manipulating the stuff on\r\nthe screen and in not allowing keystroke customization.\r\n\r\n","install_details":"____________________________________________________________\r\nSystem Requirements \r\n\r\nTMS has been tested on Windows 98 and Linux.  It requires\r\nVIM with perl support.  The perl module libnet is required\r\n(and one easy way to provide this is to have external perl\r\ntoo).\r\n\r\n____________________________________________________________\r\nInstallation \r\n\r\nEssentially, extracting tms.tar.gz into the vimfiles\r\ndirectory (on Windows) or into the ~\/.vim directory (on\r\nUnix) while preserving folder names; then regenerate the\r\nhelp-tags (using the command :helptags).\r\n\r\nExtracting deploys the following files below the vimfiles or\r\n.vim directory:\r\n\r\n       ftdetect\/index.vim\r\n       ftplugin\/index.vim\r\n       syntax\/index.vim\r\n       plugin\/tms.vim\r\n       mail\/_tmsrc.example\r\n       mail\/tms.vim\r\n       after\/ftplugin\/mail.vim\r\n       doc\/tms.txt\r\n\r\nThe help-tags can be regenerated, for example, by executing\r\n'':helptags $vim\\vimfiles\\doc'' from within vim.\r\n\r\n","5":"____________________________________________________________\r\nSystem Requirements \r\n\r\nTMS has been tested on Windows 98 and Linux.  It requires\r\nVIM with perl support.  The perl module libnet is required\r\n(and one easy way to provide this is to have external perl\r\ntoo).\r\n\r\n____________________________________________________________\r\nInstallation \r\n\r\nEssentially, extracting tms.tar.gz into the vimfiles\r\ndirectory (on Windows) or into the ~\/.vim directory (on\r\nUnix) while preserving folder names; then regenerate the\r\nhelp-tags (using the command :helptags).\r\n\r\nExtracting deploys the following files below the vimfiles or\r\n.vim directory:\r\n\r\n       ftdetect\/index.vim\r\n       ftplugin\/index.vim\r\n       syntax\/index.vim\r\n       plugin\/tms.vim\r\n       mail\/_tmsrc.example\r\n       mail\/tms.vim\r\n       after\/ftplugin\/mail.vim\r\n       doc\/tms.txt\r\n\r\nThe help-tags can be regenerated, for example, by executing\r\n'':helptags $vim\\vimfiles\\doc'' from within vim.\r\n\r\n","first_name":"Suresh","6":"Suresh","last_name":"Govindachar","7":"Govindachar","releases":[{"0":"1052","vim_version":"6.0","1":"6.0","script_version":"1.14","2":"1.14","version_comment":" - Added requested \"custom completion\" feature to complete the mail-folder in commands such as :TMSMakeIndex\r\n\r\n - Hereby explicitly revealing existence of the command :TMSShowIndex <mail-folder>\r\n\r\n - Added test of perl version (require 5.8.0)\r\n\r\n","3":" - Added requested \"custom completion\" feature to complete the mail-folder in commands such as :TMSMakeIndex\r\n\r\n - Hereby explicitly revealing existence of the command :TMSShowIndex <mail-folder>\r\n\r\n - Added test of perl version (require 5.8.0)\r\n\r\n","package":"tms_1_14.tar.gz","4":"tms_1_14.tar.gz","src_id":"3432","5":"3432","creation_date":"1094661599","6":"1094661599"},{"0":"1052","vim_version":"6.0","1":"6.0","script_version":"1.13","2":"1.13","version_comment":"See mail\/release_notes:  The main new feature is an illustration of filtering, and the use of quickfix commands (:cn, :copen etc.) to visit mail folders which have new mail. ","3":"See mail\/release_notes:  The main new feature is an illustration of filtering, and the use of quickfix commands (:cn, :copen etc.) to visit mail folders which have new mail. ","package":"tms_1_13.tar.gz","4":"tms_1_13.tar.gz","src_id":"3430","5":"3430","creation_date":"1094404639","6":"1094404639"},{"0":"1052","vim_version":"6.0","1":"6.0","script_version":"1.12","2":"1.12","version_comment":"See mail\/release_notes (minor updates including \r\nuse of VimEnter event to capture passwords).\r\nWelcome all feedback.","3":"See mail\/release_notes (minor updates including \r\nuse of VimEnter event to capture passwords).\r\nWelcome all feedback.","package":"tms_1_12.tar.gz","4":"tms_1_12.tar.gz","src_id":"3333","5":"3333","creation_date":"1092472160","6":"1092472160"},{"0":"1052","vim_version":"6.0","1":"6.0","script_version":"1.11","2":"1.11","version_comment":"Automated method for getting the passwords\r\nfor the various mail servers didn't work since it\r\nwas run during VIM's start-up.  Have added a \r\nmanual method for setting passwords.  Needs to\r\nbe done only ONCE -- see mail\/release_notes.\r\n(Do keep me informed of positive or negative \r\nexperience with using tms.)\r\n\r\n","3":"Automated method for getting the passwords\r\nfor the various mail servers didn't work since it\r\nwas run during VIM's start-up.  Have added a \r\nmanual method for setting passwords.  Needs to\r\nbe done only ONCE -- see mail\/release_notes.\r\n(Do keep me informed of positive or negative \r\nexperience with using tms.)\r\n\r\n","package":"tms_1_11.tar.gz","4":"tms_1_11.tar.gz","src_id":"3316","5":"3316","creation_date":"1092213994","6":"1092213994"}]},"1051":{"script_id":"1051","0":"1051","script_name":"groff keymap","1":"groff keymap","script_type":"utility","2":"utility","summary":" groff latin1\/cp1252\/utf-8 keymap conversion file","3":" groff latin1\/cp1252\/utf-8 keymap conversion file","description":"This is a demonstration of the kind of abuse vim can handle and the\r\nmischief you can accomplish without delving into VimL \r\nprogramming. You don't need emacs to brew coffee....\r\n\r\nThis keymap works with groff and the default Western fonts\r\nsupplied with the PostScript output device. It should work with ATT ditroff\r\nas well because I used the old ATT syntax, but you may be in for a disappointing\r\nsurprise in such case: accented characters will be mostly faked.\r\n\r\nThis file covers codepage win-1252, because that's what I use in my\r\nworkstation. If you use some sort of Unix, your default codepage\r\nwill be ISO-8859-1, also known as Latin-1.  There are several\r\nobvious differences, all additions in the decimal codepoints 128-159\r\nare control codes in Latin-1.\r\n\r\nIf you need a different keymap, say for latin2 or cyrillic, you are\r\nwelcome to use these example files as a starting point. As well,\r\nI'll appreciate if you contribute them back to this package in order to\r\nhave a centralized distribution (you are welcome to take over\r\nownership, I don't look much at this package anymore!). I strongly\r\nrecommend that in such case, you use groff 1.19.1 or a later version\r\nbecause it can handle proper unicode decomposition.\r\n\r\nWhile testing these keymap files I discovered an intersting\r\nside-effect due to the way vim manages keymap files. Namely, that\r\nthe _active_ key mappings are those you can actually access with the\r\nkeyboard while in insert mode. If you can switch your keyboard\r\nmappings on-the-fly, as recent versions of Windows, can, you can\r\ntype several different Western Europe languages by switching\r\nkeyboard mappings at the OS level.\r\n\r\nFor example, in my keyboard with an Standard Spanish layout, there\r\nis no way to access directly an etsset \u00c2\u00ab\u00c3\u009f\u00c2\u00bb using this keymap,\r\ntherefore the keymapping doesn't work. That is, I can type\r\n<ctr-k>ss but it won't expand to the troff request \\(ss --- \\[ss] in\r\nnative groff parlance --- but rather the 8-byte code \u00c2\u00ab\u00c3\u009f\u00c2\u00bb as defined\r\nin the encoding; if I switch the keyboard driver to some German keybaord\r\ndriver (e.g., Swiss German) it will work though.\r\n","4":"This is a demonstration of the kind of abuse vim can handle and the\r\nmischief you can accomplish without delving into VimL \r\nprogramming. You don't need emacs to brew coffee....\r\n\r\nThis keymap works with groff and the default Western fonts\r\nsupplied with the PostScript output device. It should work with ATT ditroff\r\nas well because I used the old ATT syntax, but you may be in for a disappointing\r\nsurprise in such case: accented characters will be mostly faked.\r\n\r\nThis file covers codepage win-1252, because that's what I use in my\r\nworkstation. If you use some sort of Unix, your default codepage\r\nwill be ISO-8859-1, also known as Latin-1.  There are several\r\nobvious differences, all additions in the decimal codepoints 128-159\r\nare control codes in Latin-1.\r\n\r\nIf you need a different keymap, say for latin2 or cyrillic, you are\r\nwelcome to use these example files as a starting point. As well,\r\nI'll appreciate if you contribute them back to this package in order to\r\nhave a centralized distribution (you are welcome to take over\r\nownership, I don't look much at this package anymore!). I strongly\r\nrecommend that in such case, you use groff 1.19.1 or a later version\r\nbecause it can handle proper unicode decomposition.\r\n\r\nWhile testing these keymap files I discovered an intersting\r\nside-effect due to the way vim manages keymap files. Namely, that\r\nthe _active_ key mappings are those you can actually access with the\r\nkeyboard while in insert mode. If you can switch your keyboard\r\nmappings on-the-fly, as recent versions of Windows, can, you can\r\ntype several different Western Europe languages by switching\r\nkeyboard mappings at the OS level.\r\n\r\nFor example, in my keyboard with an Standard Spanish layout, there\r\nis no way to access directly an etsset \u00c2\u00ab\u00c3\u009f\u00c2\u00bb using this keymap,\r\ntherefore the keymapping doesn't work. That is, I can type\r\n<ctr-k>ss but it won't expand to the troff request \\(ss --- \\[ss] in\r\nnative groff parlance --- but rather the 8-byte code \u00c2\u00ab\u00c3\u009f\u00c2\u00bb as defined\r\nin the encoding; if I switch the keyboard driver to some German keybaord\r\ndriver (e.g., Swiss German) it will work though.\r\n","install_details":"Install files in $VIM\/vimfiles\/keymap for a global installation.\r\n\r\nFor a local installation use $HOME\/.vim\/keymap if using some UNIX\/Linux, or $HOME\/vimfiles\/keymap if using windows.\r\n ","5":"Install files in $VIM\/vimfiles\/keymap for a global installation.\r\n\r\nFor a local installation use $HOME\/.vim\/keymap if using some UNIX\/Linux, or $HOME\/vimfiles\/keymap if using windows.\r\n ","first_name":"Pedro Alejandro","6":"Pedro Alejandro","last_name":"L\u00c3\u00b3pez-Valencia","7":"L\u00c3\u00b3pez-Valencia","releases":[{"0":"1051","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"groff_keymap-1_0.tbz","4":"groff_keymap-1_0.tbz","src_id":"3298","5":"3298","creation_date":"1091518873","6":"1091518873"}]},"1050":{"script_id":"1050","0":"1050","script_name":"delete.py","1":"delete.py","script_type":"indent","2":"indent","summary":"Makes the delete key remove 'softtabspace' characters, similar to backspace","3":"Makes the delete key remove 'softtabspace' characters, similar to backspace","description":"I usually edit Python code that has a lot of whitespace indenting.\r\nThe backspace key works nicely, and I'm able to delete indents,\r\nbut I'm unable to do so with the <Del> key.\r\nI've searched the web, searched the scripts and tips, asked on the vim mailing list,\r\nasked on IRC and read a lot of documentation.\r\nIn the end, I found it easier to write a Python script that gave me the desired behaviour.\r\nSo, here it is. It works for me.","4":"I usually edit Python code that has a lot of whitespace indenting.\r\nThe backspace key works nicely, and I'm able to delete indents,\r\nbut I'm unable to do so with the <Del> key.\r\nI've searched the web, searched the scripts and tips, asked on the vim mailing list,\r\nasked on IRC and read a lot of documentation.\r\nIn the end, I found it easier to write a Python script that gave me the desired behaviour.\r\nSo, here it is. It works for me.","install_details":"(for *nix)\r\nNote that you need Python-support compiled in to your Vim.\r\n(On Debian, just apt-get install vim-python)\r\nSave the script to your .vim\/indent folder.\r\nAdd these two lines to your .vimrc:\r\ninoremap <silent> <Del> <ESC>:pyfile ~\/.vim\/indent\/delete.py<CR>i\r\nnnoremap <silent> <Del> :pyfile ~\/.vim\/indent\/delete.py<CR>\r\n","5":"(for *nix)\r\nNote that you need Python-support compiled in to your Vim.\r\n(On Debian, just apt-get install vim-python)\r\nSave the script to your .vim\/indent folder.\r\nAdd these two lines to your .vimrc:\r\ninoremap <silent> <Del> <ESC>:pyfile ~\/.vim\/indent\/delete.py<CR>i\r\nnnoremap <silent> <Del> :pyfile ~\/.vim\/indent\/delete.py<CR>\r\n","first_name":"Alexander","6":"Alexander","last_name":"R\u00c3\u00b8dseth","7":"R\u00c3\u00b8dseth","releases":[{"0":"1050","vim_version":"6.0","1":"6.0","script_version":"0.4","2":"0.4","version_comment":"Fixed a bug that made it unable to delete lines when there was only a single character left.","3":"Fixed a bug that made it unable to delete lines when there was only a single character left.","package":"delete.py","4":"delete.py","src_id":"3286","5":"3286","creation_date":"1091092074","6":"1091092074"},{"0":"1050","vim_version":"6.0","1":"6.0","script_version":"0.3","2":"0.3","version_comment":"Made deletion of characters at the end of the line move the cursor one to the left, in order to avoid leaving the cursor at an nonexistant character.","3":"Made deletion of characters at the end of the line move the cursor one to the left, in order to avoid leaving the cursor at an nonexistant character.","package":"delete.py","4":"delete.py","src_id":"3285","5":"3285","creation_date":"1091091042","6":"1091091042"},{"0":"1050","vim_version":"6.0","1":"6.0","script_version":"0.2","2":"0.2","version_comment":"Initial upload","3":"Initial upload","package":"delete.py","4":"delete.py","src_id":"3284","5":"3284","creation_date":"1091089575","6":"1091089575"}]},"1049":{"script_id":"1049","0":"1049","script_name":"octave.vim","1":"octave.vim","script_type":"ftplugin","2":"ftplugin","summary":"Send Octave code from a VIM buffer to Octave","3":"Send Octave code from a VIM buffer to Octave","description":"Send Octave code from a VIM buffer to Octave using funnel.pl from vimscript #221. Contains\r\n\r\nREADME.octave_with_vim\r\nftplugin\/octave.vim\r\nftplugin\/funnel.pl\r\n\r\nftplugin\/funnel.pl is from Larry Clapp (vimscript #221). It is used for creating \r\na pipe that Octave is listening to.\r\n\r\nYou can help improving these files via my subversion repository at http:\/\/kriemhild.uft.uni-bremen.de\/svn\/vim","4":"Send Octave code from a VIM buffer to Octave using funnel.pl from vimscript #221. Contains\r\n\r\nREADME.octave_with_vim\r\nftplugin\/octave.vim\r\nftplugin\/funnel.pl\r\n\r\nftplugin\/funnel.pl is from Larry Clapp (vimscript #221). It is used for creating \r\na pipe that Octave is listening to.\r\n\r\nYou can help improving these files via my subversion repository at http:\/\/kriemhild.uft.uni-bremen.de\/svn\/vim","install_details":"See README.octave_with_vim. You will need some perl modules for funnel.pl.","5":"See README.octave_with_vim. You will need some perl modules for funnel.pl.","first_name":"Johannes","6":"Johannes","last_name":"Ranke","7":"Ranke","releases":[{"0":"1049","vim_version":"6.0","1":"6.0","script_version":"0.01-8","2":"0.01-8","version_comment":"Small improvement of README file","3":"Small improvement of README file","package":"octave_with_vim_0.01-8.tar.gz","4":"octave_with_vim_0.01-8.tar.gz","src_id":"3288","5":"3288","creation_date":"1091149168","6":"1091149168"},{"0":"1049","vim_version":"6.0","1":"6.0","script_version":"0.01","2":"0.01","version_comment":"Initial upload","3":"Initial upload","package":"octave_with_vim_0.01-6.tar.gz","4":"octave_with_vim_0.01-6.tar.gz","src_id":"3282","5":"3282","creation_date":"1091006757","6":"1091006757"}]},"1048":{"script_id":"1048","0":"1048","script_name":"R.vim","1":"R.vim","script_type":"ftplugin","2":"ftplugin","summary":"Send R code from a VIM buffer to R","3":"Send R code from a VIM buffer to R","description":"The plugin is not maintained any more. Please use the excellent vimscript #2628. It even lets you use the \"r\" key to send a visual selection to R (let vimrplugin_map_r=1) if you got used to this using my plugin. The following is only kept for archiving purposes.\r\n\r\nSend R code from a VIM buffer to R on Unix type systems using funnel.pl from vimscript #221. Contains\r\n\r\nREADME.R_with_vim\r\nftplugin\/r.vim\r\nftplugin\/rnoweb.vim\r\nftplugin\/funnel.pl\r\nsyntax\/rhelp.vim\r\nsyntax\/rnoweb.vim\r\nMakefile.rnoweb\r\n\r\nFernando Henrique Ferraz Pereira da Rosa is now a coauthor of this plugin (starting from version 0.03). He helped me fixing a bug and started the syntax file for mixed highlighting of Latex and R syntax (syntax\/rnoweb.vim).\r\n\r\nI set up a small project page for this plugin, featuring a screenshot:\r\n\r\nhttp:\/\/www.uft.uni-bremen.de\/chemie\/ranke\/?page=vim_R_linux\r\n\r\nYou can browse the subversion repository where these files are at home: http:\/\/kriemhild.uft.uni-bremen.de\/viewcvs\/?root=vim\r\n\r\nAlternatives for Mac Os X include vimscript #1741 and vimscript #2104.\r\n\r\nUnder Windows, I am now using a quite simple solution, consisting of the installation of the rcom package for R which requires statconnDCOM from http:\/\/rcom.univie.ac.at and ActiveState Perl in the PATH (watch out if you use R tools, because GNU perl does not have the DCOM interface, so ActiveState perl needs to be first in the path).\r\nMy ftplugin\/r.vim under Windows:\r\n\r\nperl << EOF\r\nsub rsourceclipboard\r\n{\r\n    use Win32::OLE;\r\n    my $R = Win32::OLE->GetActiveObject('RCOMServerLib.StatConnector')\r\n          || Win32::OLE->new('RCOMServerLib.StatConnector');\r\n    $R->Evaluate(\"source('clipboard', echo=TRUE)\");\r\n    $R->Close;\r\n}\r\nEOF\r\n\r\nvnoremap <buffer> r \"*y:perl rsourceclipboard<CR>\r\n\r\nThis means that the visual selection is pasted to the clipboard and the clipboard content is sourced by R when the key \"r\" is pressed in visual mode.\r\n\r\n\r\n\r\n","4":"The plugin is not maintained any more. Please use the excellent vimscript #2628. It even lets you use the \"r\" key to send a visual selection to R (let vimrplugin_map_r=1) if you got used to this using my plugin. The following is only kept for archiving purposes.\r\n\r\nSend R code from a VIM buffer to R on Unix type systems using funnel.pl from vimscript #221. Contains\r\n\r\nREADME.R_with_vim\r\nftplugin\/r.vim\r\nftplugin\/rnoweb.vim\r\nftplugin\/funnel.pl\r\nsyntax\/rhelp.vim\r\nsyntax\/rnoweb.vim\r\nMakefile.rnoweb\r\n\r\nFernando Henrique Ferraz Pereira da Rosa is now a coauthor of this plugin (starting from version 0.03). He helped me fixing a bug and started the syntax file for mixed highlighting of Latex and R syntax (syntax\/rnoweb.vim).\r\n\r\nI set up a small project page for this plugin, featuring a screenshot:\r\n\r\nhttp:\/\/www.uft.uni-bremen.de\/chemie\/ranke\/?page=vim_R_linux\r\n\r\nYou can browse the subversion repository where these files are at home: http:\/\/kriemhild.uft.uni-bremen.de\/viewcvs\/?root=vim\r\n\r\nAlternatives for Mac Os X include vimscript #1741 and vimscript #2104.\r\n\r\nUnder Windows, I am now using a quite simple solution, consisting of the installation of the rcom package for R which requires statconnDCOM from http:\/\/rcom.univie.ac.at and ActiveState Perl in the PATH (watch out if you use R tools, because GNU perl does not have the DCOM interface, so ActiveState perl needs to be first in the path).\r\nMy ftplugin\/r.vim under Windows:\r\n\r\nperl << EOF\r\nsub rsourceclipboard\r\n{\r\n    use Win32::OLE;\r\n    my $R = Win32::OLE->GetActiveObject('RCOMServerLib.StatConnector')\r\n          || Win32::OLE->new('RCOMServerLib.StatConnector');\r\n    $R->Evaluate(\"source('clipboard', echo=TRUE)\");\r\n    $R->Close;\r\n}\r\nEOF\r\n\r\nvnoremap <buffer> r \"*y:perl rsourceclipboard<CR>\r\n\r\nThis means that the visual selection is pasted to the clipboard and the clipboard content is sourced by R when the key \"r\" is pressed in visual mode.\r\n\r\n\r\n\r\n","install_details":"For working with vim and R it is convenient to open a fresh xterm on a\r\nfresh virtual desktop, covering the left half of the screen, and start vim,\r\ncheck if the filetype is set correctly (:set ft), set it if necessary (e.g.\r\nwith :set ft=r) and press <F2>. This will open a second xterm listening to an R\r\ninterpreter.  You can then send visually highlighted code from vim to R with\r\nthe vmap \"r\".\r\n\r\nCaution: If there are adjacent tabs in the source code (can be made visible\r\nwith :set list, then they show up as ^I^I), then your R console will list\r\nthe contents of your working directory in the middle of interpreting your\r\ncode and most likely get confused. I don't recommend using tabs anyway (use\r\nthe vim option expandtab, as set in r.vim). A workaround for existing code\r\nis to execute it with the R command source().\r\n\r\n-----\r\n\r\nAs an alternative to this plugin on www.vim.org you can also install my Debian\r\npackage if you are using the Debian distribution:\r\n\r\n\t$ su\r\n\t$ echo \"deb http:\/\/www.uft.uni-bremen.de\/chemie\/ranke\/debs .\/\" >> \/etc\/apt\/sources.list\r\n\t$ apt-get update\r\n\t$ apt-get install vim-r-plugin\r\n\t\r\nNote that you have to activate addons like this plugin since vim version\r\n7.1-022+1, July 2007. For system-wide activation, use\r\n\r\n    $ vim-addons -w install r-plugin\r\n\r\n(details in README.Debian). You can then ignore the rest of this file.\r\n\r\n-----\r\n\r\nMaking this plugin work requires the installation of the perl script,\r\nftplugin\/funnel.pl. It just has to be in your $PATH and executable, so if you\r\nare the only one working with the plugin on your machine, e.g.\r\n\r\nmv ftplugin\/funnel.pl ~\/bin\r\nchmod +x ~\/bin\/funnel.pl\r\n\r\n(be sure ~\/bin is in your $PATH variable) or if you have superuser privileges\r\nyou can put funnel.pl it into \/usr\/local\/bin.\r\n\r\nfunnel.pl requires two perl libraries:\r\n\r\n\tIO::Pty and Term::ReadLine\r\n\r\nIf you add the lines\r\n\r\n\tau BufNewFile,BufRead *.R     setf r\r\n\tau BufNewFile,BufRead *.R     set syntax=r\r\n\r\nto your ~.vim\/filetype.vim file (or create one with only these lines) then the\r\nvimscript r.vim will be activated upon opening any file with a filename\r\nmatching *.R. The whole set of commands available at this point is elucidated\r\nin ftplugin\/r.vim.\r\n\r\nI am also including my syntax files for R help files and R noweb files (Sweave files)\r\nas well as a Makefile for processing R noweb files from within vim with :make. The \r\nsyntax files are part of vim starting from version 7.\r\n\r\nI have one report of the funnel.pl not working on Mac OS X with the default perl on this\r\nOS. If anybody gets this to work, please drop me a line.","5":"For working with vim and R it is convenient to open a fresh xterm on a\r\nfresh virtual desktop, covering the left half of the screen, and start vim,\r\ncheck if the filetype is set correctly (:set ft), set it if necessary (e.g.\r\nwith :set ft=r) and press <F2>. This will open a second xterm listening to an R\r\ninterpreter.  You can then send visually highlighted code from vim to R with\r\nthe vmap \"r\".\r\n\r\nCaution: If there are adjacent tabs in the source code (can be made visible\r\nwith :set list, then they show up as ^I^I), then your R console will list\r\nthe contents of your working directory in the middle of interpreting your\r\ncode and most likely get confused. I don't recommend using tabs anyway (use\r\nthe vim option expandtab, as set in r.vim). A workaround for existing code\r\nis to execute it with the R command source().\r\n\r\n-----\r\n\r\nAs an alternative to this plugin on www.vim.org you can also install my Debian\r\npackage if you are using the Debian distribution:\r\n\r\n\t$ su\r\n\t$ echo \"deb http:\/\/www.uft.uni-bremen.de\/chemie\/ranke\/debs .\/\" >> \/etc\/apt\/sources.list\r\n\t$ apt-get update\r\n\t$ apt-get install vim-r-plugin\r\n\t\r\nNote that you have to activate addons like this plugin since vim version\r\n7.1-022+1, July 2007. For system-wide activation, use\r\n\r\n    $ vim-addons -w install r-plugin\r\n\r\n(details in README.Debian). You can then ignore the rest of this file.\r\n\r\n-----\r\n\r\nMaking this plugin work requires the installation of the perl script,\r\nftplugin\/funnel.pl. It just has to be in your $PATH and executable, so if you\r\nare the only one working with the plugin on your machine, e.g.\r\n\r\nmv ftplugin\/funnel.pl ~\/bin\r\nchmod +x ~\/bin\/funnel.pl\r\n\r\n(be sure ~\/bin is in your $PATH variable) or if you have superuser privileges\r\nyou can put funnel.pl it into \/usr\/local\/bin.\r\n\r\nfunnel.pl requires two perl libraries:\r\n\r\n\tIO::Pty and Term::ReadLine\r\n\r\nIf you add the lines\r\n\r\n\tau BufNewFile,BufRead *.R     setf r\r\n\tau BufNewFile,BufRead *.R     set syntax=r\r\n\r\nto your ~.vim\/filetype.vim file (or create one with only these lines) then the\r\nvimscript r.vim will be activated upon opening any file with a filename\r\nmatching *.R. The whole set of commands available at this point is elucidated\r\nin ftplugin\/r.vim.\r\n\r\nI am also including my syntax files for R help files and R noweb files (Sweave files)\r\nas well as a Makefile for processing R noweb files from within vim with :make. The \r\nsyntax files are part of vim starting from version 7.\r\n\r\nI have one report of the funnel.pl not working on Mac OS X with the default perl on this\r\nOS. If anybody gets this to work, please drop me a line.","first_name":"Johannes","6":"Johannes","last_name":"Ranke","7":"Ranke","releases":[{"0":"1048","vim_version":"6.0","1":"6.0","script_version":"0.5-80","2":"0.5-80","version_comment":"- Cleaned up ftplugin\/*.vim files\r\n- Added shiftwidth=2 and expandtab to ftplugin\/rnoweb.vim\r\n- Added documentation on using vim-addon-manager to activate the plugin under Debian based distributions","3":"- Cleaned up ftplugin\/*.vim files\r\n- Added shiftwidth=2 and expandtab to ftplugin\/rnoweb.vim\r\n- Added documentation on using vim-addon-manager to activate the plugin under Debian based distributions","package":"R_with_vim_0.5-80.tar.gz","4":"R_with_vim_0.5-80.tar.gz","src_id":"7976","5":"7976","creation_date":"1195627242","6":"1195627242"},{"0":"1048","vim_version":"6.0","1":"6.0","script_version":"0.5-62","2":"0.5-62","version_comment":"- Update of R help file syntax for new items in R 2.3.0\r\n- Fixed tabbing in ftplugin\/r.vim to suit emacs edited scripts.\r\n- Added a note about the problem with adjacent tabs being pasted to the R console (see README.R_with_vim)\r\n- Small fixes","3":"- Update of R help file syntax for new items in R 2.3.0\r\n- Fixed tabbing in ftplugin\/r.vim to suit emacs edited scripts.\r\n- Added a note about the problem with adjacent tabs being pasted to the R console (see README.R_with_vim)\r\n- Small fixes","package":"R_with_vim_0.5-62.tar.gz","4":"R_with_vim_0.5-62.tar.gz","src_id":"5751","5":"5751","creation_date":"1148435705","6":"1148435705"},{"0":"1048","vim_version":"6.0","1":"6.0","script_version":"0.5-54","2":"0.5-54","version_comment":"- Up-to-date version of the R help and R noweb syntax files. Both of them are now part of vim 7. \r\n- Added ftplugin\/rnoweb.vim and Makefile.rnoweb for R noweb files.","3":"- Up-to-date version of the R help and R noweb syntax files. Both of them are now part of vim 7. \r\n- Added ftplugin\/rnoweb.vim and Makefile.rnoweb for R noweb files.","package":"R_with_vim_0.5-54.tar.gz","4":"R_with_vim_0.5-54.tar.gz","src_id":"5579","5":"5579","creation_date":"1145358208","6":"1145358208"},{"0":"1048","vim_version":"6.0","1":"6.0","script_version":"0.5-38","2":"0.5-38","version_comment":"- switched to funnel.pl from VIlisp 2.3\r\n- carefully reviewed and extended the R help file syntax highlighting","3":"- switched to funnel.pl from VIlisp 2.3\r\n- carefully reviewed and extended the R help file syntax highlighting","package":"R_with_vim_0.5-38.tar.gz","4":"R_with_vim_0.5-38.tar.gz","src_id":"5342","5":"5342","creation_date":"1141137708","6":"1141137708"},{"0":"1048","vim_version":"6.0","1":"6.0","script_version":"0.03-33","2":"0.03-33","version_comment":"Fixed the problem with the xterm not closing. Installation is also easier now because the bash script R-managed is not needed any more.","3":"Fixed the problem with the xterm not closing. Installation is also easier now because the bash script R-managed is not needed any more.","package":"R_with_vim_0.03-36.tar.gz","4":"R_with_vim_0.03-36.tar.gz","src_id":"4478","5":"4478","creation_date":"1123547422","6":"1123547422"},{"0":"1048","vim_version":"6.0","1":"6.0","script_version":"0.03-29","2":"0.03-29","version_comment":"Fernando Henrique Ferraz Pereira da Rosa inspired me to improve the \r\nplugin. Also added mixed syntax highlighting for Sweave files according\r\nto the tip of his.","3":"Fernando Henrique Ferraz Pereira da Rosa inspired me to improve the \r\nplugin. Also added mixed syntax highlighting for Sweave files according\r\nto the tip of his.","package":"R_with_vim_0.03-29.tar.gz","4":"R_with_vim_0.03-29.tar.gz","src_id":"4459","5":"4459","creation_date":"1123220824","6":"1123220824"},{"0":"1048","vim_version":"6.0","1":"6.0","script_version":"0.01-8","2":"0.01-8","version_comment":"Small improvement of README file","3":"Small improvement of README file","package":"R_with_vim_0.01-8.tar.gz","4":"R_with_vim_0.01-8.tar.gz","src_id":"3289","5":"3289","creation_date":"1091149260","6":"1091149260"},{"0":"1048","vim_version":"6.0","1":"6.0","script_version":"0.01","2":"0.01","version_comment":"Initial upload","3":"Initial upload","package":"R_with_vim_0.01-6.tar.gz","4":"R_with_vim_0.01-6.tar.gz","src_id":"3281","5":"3281","creation_date":"1091006419","6":"1091006419"}]},"1047":{"script_id":"1047","0":"1047","script_name":"ST20 compiler plugin","1":"ST20 compiler plugin","script_type":"utility","2":"utility","summary":"Vim compiler plugin for ST20 C compiler","3":"Vim compiler plugin for ST20 C compiler","description":"ST20 C compiler plugin. \r\nRead the heading of the file for more information.","4":"ST20 C compiler plugin. \r\nRead the heading of the file for more information.","install_details":"Simply drop into $VIMRUNTIME\/compiler and\r\n:compiler st20_c\r\nwhen you need it.","5":"Simply drop into $VIMRUNTIME\/compiler and\r\n:compiler st20_c\r\nwhen you need it.","first_name":"Wenzhi","6":"Wenzhi","last_name":"Liang","7":"Liang","releases":[{"0":"1047","vim_version":"6.0","1":"6.0","script_version":"0.2","2":"0.2","version_comment":"Turn on warning by default. It is also possible to configure it in .vimrc.","3":"Turn on warning by default. It is also possible to configure it in .vimrc.","package":"st20_c.vim","4":"st20_c.vim","src_id":"4067","5":"4067","creation_date":"1111667175","6":"1111667175"},{"0":"1047","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"st20_c.vim","4":"st20_c.vim","src_id":"3280","5":"3280","creation_date":"1091003365","6":"1091003365"}]},"1046":{"script_id":"1046","0":"1046","script_name":"monday","1":"monday","script_type":"utility","2":"utility","summary":"Lets you use ctrl-a and ctrl-x on names of months and weekdays","3":"Lets you use ctrl-a and ctrl-x on names of months and weekdays","description":"Monday.vim extends the normal-mode commands <ctrl-a> and <ctrl-x> so that they can be applied to the names of months and weekdays. For example, if you are standing on the word \"July\" and presses <ctrl-a>, the word is replaced by \"August\".\r\n\r\nThe script tries to preserve the case of the letters, and can handle the following three variants:\r\n\r\n(1) All lower-case (\"july\" becomes \"august\").\r\n(2) All upper-case (\"JULY\" becomes \"AUGUST\").\r\n(3) First letter upper-case, the rest lower-case (\"July\" becomes \"August\").\r\n\r\nTodo:\r\n\r\nOnly English is supported; although it's easy to add any word pairs you want, the script cannot yet handle words that have two or more possible successors\/predecessors.  For example, the 4th month is called \"April\" in both English and Swedish, but its successor is called \"May\" and \"Maj\", respectively. So, if you add the Swedish months and then try to increment the word \"April\", the script won't be able to figure out which word (\"May\" or \"Maj\")  it should be replaced with.\r\n","4":"Monday.vim extends the normal-mode commands <ctrl-a> and <ctrl-x> so that they can be applied to the names of months and weekdays. For example, if you are standing on the word \"July\" and presses <ctrl-a>, the word is replaced by \"August\".\r\n\r\nThe script tries to preserve the case of the letters, and can handle the following three variants:\r\n\r\n(1) All lower-case (\"july\" becomes \"august\").\r\n(2) All upper-case (\"JULY\" becomes \"AUGUST\").\r\n(3) First letter upper-case, the rest lower-case (\"July\" becomes \"August\").\r\n\r\nTodo:\r\n\r\nOnly English is supported; although it's easy to add any word pairs you want, the script cannot yet handle words that have two or more possible successors\/predecessors.  For example, the 4th month is called \"April\" in both English and Swedish, but its successor is called \"May\" and \"Maj\", respectively. So, if you add the Swedish months and then try to increment the word \"April\", the script won't be able to figure out which word (\"May\" or \"Maj\")  it should be replaced with.\r\n","install_details":"Just drop the script in your local plugin directory (e.g. ~\/.vim\/plugin).","5":"Just drop the script in your local plugin directory (e.g. ~\/.vim\/plugin).","first_name":"Stefan","6":"Stefan","last_name":"Karlsson","7":"Karlsson","releases":[{"0":"1046","vim_version":"6.0","1":"6.0","script_version":"0.3","2":"0.3","version_comment":"Added support for 1st, 2nd, 3rd, etc. (idea by Chris Ottrey). Also fixed some bugs.","3":"Added support for 1st, 2nd, 3rd, etc. (idea by Chris Ottrey). Also fixed some bugs.","package":"monday.vim","4":"monday.vim","src_id":"4249","5":"4249","creation_date":"1115354964","6":"1115354964"},{"0":"1046","vim_version":"6.0","1":"6.0","script_version":"0.2","2":"0.2","version_comment":"Corrected a problem related to the 'ignorecase' option (all changed words became lower-case). Thanks to Anton Berezin  for pointing this out and for providing a patch.","3":"Corrected a problem related to the 'ignorecase' option (all changed words became lower-case). Thanks to Anton Berezin  for pointing this out and for providing a patch.","package":"monday.vim","4":"monday.vim","src_id":"3406","5":"3406","creation_date":"1094046564","6":"1094046564"}]},"1045":{"script_id":"1045","0":"1045","script_name":"sf.vim","1":"sf.vim","script_type":"color scheme","2":"color scheme","summary":"vim.sf.net colorscheme (GUI only)","3":"vim.sf.net colorscheme (GUI only)","description":"Since I found these colors very nice and appropriate, here's\r\na colorscheme trying to match the webpage colors.\r\nComments\/feedback welcome as usual.\r\n\r\n\r\n","4":"Since I found these colors very nice and appropriate, here's\r\na colorscheme trying to match the webpage colors.\r\nComments\/feedback welcome as usual.\r\n\r\n\r\n","install_details":"drop it in .vim\/colors for example\r\n\r\n\r\n","5":"drop it in .vim\/colors for example\r\n\r\n\r\n","first_name":"Christian","6":"Christian","last_name":"MICHON","7":"MICHON","releases":[{"0":"1045","vim_version":"6.0","1":"6.0","script_version":"1.1","2":"1.1","version_comment":"changed Special...\r\n\r\n","3":"changed Special...\r\n\r\n","package":"sf.vim","4":"sf.vim","src_id":"3278","5":"3278","creation_date":"1090992605","6":"1090992605"}]},"1044":{"script_id":"1044","0":"1044","script_name":"uc.vim","1":"uc.vim","script_type":"ftplugin","2":"ftplugin","summary":"filetype plugin for Intel Microcode","3":"filetype plugin for Intel Microcode","description":"filetype plugin for Microcode","4":"filetype plugin for Microcode","install_details":"in the distribution, place the downloaded uc.vim in your ftplugin directory (e.g. on windows vimfiles\/ftplugin or on unix .vim\/ftplugin).\r\n\r\nCreate a file \\\"filetype.vim\\\" which contains an autocommand for your filetype.\r\n(Autocommands were explained in section |40.3|.)  Example: >\r\n\r\naugroup filetypedetect\r\nau BufNewFile,BufRead *.uc setf uc\r\naugroup END","5":"in the distribution, place the downloaded uc.vim in your ftplugin directory (e.g. on windows vimfiles\/ftplugin or on unix .vim\/ftplugin).\r\n\r\nCreate a file \\\"filetype.vim\\\" which contains an autocommand for your filetype.\r\n(Autocommands were explained in section |40.3|.)  Example: >\r\n\r\naugroup filetypedetect\r\nau BufNewFile,BufRead *.uc setf uc\r\naugroup END","first_name":"wei","6":"wei","last_name":"Gui","7":"Gui","releases":[{"0":"1044","vim_version":"6.0","1":"6.0","script_version":"0.01","2":"0.01","version_comment":"Initial upload","3":"Initial upload","package":"uc.vim","4":"uc.vim","src_id":"3271","5":"3271","creation_date":"1090654854","6":"1090654854"}]},"1043":{"script_id":"1043","0":"1043","script_name":"uc.vim","1":"uc.vim","script_type":"indent","2":"indent","summary":"indent file for Intel Network Processor Microcode","3":"indent file for Intel Network Processor Microcode","description":"indent for Microcode","4":"indent for Microcode","install_details":"in the distribution, place the downloaded uc.vim in your indent directory (e.g. on windows vimfiles\/ftplugin or on unix .vim\/ftplugin).\r\n\r\nCreate a file \"filetype.vim\" which contains an autocommand for your filetype.\r\n(Autocommands were explained in section |40.3|.)  Example: >\r\n\r\naugroup filetypedetect\r\nau BufNewFile,BufRead *.uc setf uc\r\naugroup END","5":"in the distribution, place the downloaded uc.vim in your indent directory (e.g. on windows vimfiles\/ftplugin or on unix .vim\/ftplugin).\r\n\r\nCreate a file \"filetype.vim\" which contains an autocommand for your filetype.\r\n(Autocommands were explained in section |40.3|.)  Example: >\r\n\r\naugroup filetypedetect\r\nau BufNewFile,BufRead *.uc setf uc\r\naugroup END","first_name":"wei","6":"wei","last_name":"Gui","7":"Gui","releases":[{"0":"1043","vim_version":"6.0","1":"6.0","script_version":"0.01","2":"0.01","version_comment":"Initial upload","3":"Initial upload","package":"uc.vim","4":"uc.vim","src_id":"3270","5":"3270","creation_date":"1090654695","6":"1090654695"}]},"1042":{"script_id":"1042","0":"1042","script_name":"cube.vim","1":"cube.vim","script_type":"syntax","2":"syntax","summary":"Cube engine script syntax file","3":"Cube engine script syntax file","description":"This is a syntax file for Cube Engine cfg files. It applies to autoexec.cfg, package.cfg and any other file which uses Cube script.\r\n\r\nMore info about Cube Engine here: http:\/\/cube.sourceforge.net\/\r\n\r\nThis is my first syntax file. Maybe it isn't the best, but it works very well.\r\n\r\nFeatures:\r\n - Support for keyboard keys names only after \"bind\" command. (MOUSE1, MOUSE2,... is also supported)\r\n - Support for entities names only after \"newent\" and \"clearents\" commands.\r\n - Support for all cube commands of version 2004_05_22, except \"keymap\" (which you should not use, according to docs).\r\n - Recognizes special aliases \"level_trigger_xx\" and \"nextmap_xx\".\r\n\r\nI don't know if it will work on Vim 5.","4":"This is a syntax file for Cube Engine cfg files. It applies to autoexec.cfg, package.cfg and any other file which uses Cube script.\r\n\r\nMore info about Cube Engine here: http:\/\/cube.sourceforge.net\/\r\n\r\nThis is my first syntax file. Maybe it isn't the best, but it works very well.\r\n\r\nFeatures:\r\n - Support for keyboard keys names only after \"bind\" command. (MOUSE1, MOUSE2,... is also supported)\r\n - Support for entities names only after \"newent\" and \"clearents\" commands.\r\n - Support for all cube commands of version 2004_05_22, except \"keymap\" (which you should not use, according to docs).\r\n - Recognizes special aliases \"level_trigger_xx\" and \"nextmap_xx\".\r\n\r\nI don't know if it will work on Vim 5.","install_details":"Put the file on ~\/.vim\/syntax\/ directory. Then, when opening some Cube cfg file, type:\r\n:set syntax=cube\r\n\r\nYou can also put this line at top or bottom of your Cube cfg file:\r\n\/\/ vim: set syntax=cube\r\nThis will make vim automatically apply the Cube syntax.","5":"Put the file on ~\/.vim\/syntax\/ directory. Then, when opening some Cube cfg file, type:\r\n:set syntax=cube\r\n\r\nYou can also put this line at top or bottom of your Cube cfg file:\r\n\/\/ vim: set syntax=cube\r\nThis will make vim automatically apply the Cube syntax.","first_name":"Denilson","6":"Denilson","last_name":"S\u00c3\u00a1","7":"S\u00c3\u00a1","releases":[{"0":"1042","vim_version":"6.0","1":"6.0","script_version":"1.1","2":"1.1","version_comment":"Added a few missing keywords. Just that.","3":"Added a few missing keywords. Just that.","package":"cube.vim","4":"cube.vim","src_id":"4146","5":"4146","creation_date":"1113152974","6":"1113152974"},{"0":"1042","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"cube.vim","4":"cube.vim","src_id":"3263","5":"3263","creation_date":"1090579969","6":"1090579969"}]},"1041":{"script_id":"1041","0":"1041","script_name":"CodeReviewer.vim","1":"CodeReviewer.vim","script_type":"utility","2":"utility","summary":"Utility for code reviews (using quickfix)","3":"Utility for code reviews (using quickfix)","description":"If you do code reviews on a regular basis, this script could be of help to you. This tip is about - \r\n1. Helping the reviewer review code \r\n2. Helping the author in collating reviews from various peers \r\n3. Helping the author in fixing the review comments\r\n\r\nTypical review session: \r\n1. A reviewer open the code to review, positions the cursor on the line he\/she wants to comment on and types \"\\ic\" - this puts the file name, the line number, the reviewer's initials and the defect type in the review file\r\n2. The comment is typed next to the line number and can span multiple lines\r\n3. Send the comments to the author of the code \r\n4. The author collates the inputs from various reviewers into one file (by simply concatenating them) and sorts it. Now the comments are arranged per file, in the order of line numbers (in a file called say, all_comments.txt) \r\n5. Using the :cfile all_comments.txt (or :CheckReview) the author can now navigate through all the comments.\r\n\r\nThis script is based on vimtip #761. Thanks to all for feedback! Specifically to Salman for providing an implementation for automating the step between saving position in the file being reviewed and inserting a comment in the review file.","4":"If you do code reviews on a regular basis, this script could be of help to you. This tip is about - \r\n1. Helping the reviewer review code \r\n2. Helping the author in collating reviews from various peers \r\n3. Helping the author in fixing the review comments\r\n\r\nTypical review session: \r\n1. A reviewer open the code to review, positions the cursor on the line he\/she wants to comment on and types \"\\ic\" - this puts the file name, the line number, the reviewer's initials and the defect type in the review file\r\n2. The comment is typed next to the line number and can span multiple lines\r\n3. Send the comments to the author of the code \r\n4. The author collates the inputs from various reviewers into one file (by simply concatenating them) and sorts it. Now the comments are arranged per file, in the order of line numbers (in a file called say, all_comments.txt) \r\n5. Using the :cfile all_comments.txt (or :CheckReview) the author can now navigate through all the comments.\r\n\r\nThis script is based on vimtip #761. Thanks to all for feedback! Specifically to Salman for providing an implementation for automating the step between saving position in the file being reviewed and inserting a comment in the review file.","install_details":"Read CodeReviewer.txt for install details","5":"Read CodeReviewer.txt for install details","first_name":"Karthick","6":"Karthick","last_name":"Gururaj","7":"Gururaj","releases":[{"0":"1041","vim_version":"6.0","1":"6.0","script_version":"0.2.0","2":"0.2.0","version_comment":"Sorting implemented using vim scripts (external sort utility not needed now), updates to syntax file","3":"Sorting implemented using vim scripts (external sort utility not needed now), updates to syntax file","package":"CodeReviewer.tar.gz","4":"CodeReviewer.tar.gz","src_id":"4686","5":"4686","creation_date":"1129763733","6":"1129763733"},{"0":"1041","vim_version":"6.0","1":"6.0","script_version":"0.1.0","2":"0.1.0","version_comment":"Initial upload","3":"Initial upload","package":"CodeReviewer.tar.gz","4":"CodeReviewer.tar.gz","src_id":"3258","5":"3258","creation_date":"1090450633","6":"1090450633"}]},"1040":{"script_id":"1040","0":"1040","script_name":"vimtabs.vim","1":"vimtabs.vim","script_type":"utility","2":"utility","summary":"plugin for mozilla-like tabs","3":"plugin for mozilla-like tabs","description":"When pressing <F2> and arrow keys, you get to switch quickly between buffers.\r\nThis plugin is usable in both console and gui mode.\r\n","4":"When pressing <F2> and arrow keys, you get to switch quickly between buffers.\r\nThis plugin is usable in both console and gui mode.\r\n","install_details":"drop it in .vim\/plugin\r\n\r\n","5":"drop it in .vim\/plugin\r\n\r\n","first_name":"Christian","6":"Christian","last_name":"MICHON","7":"MICHON","releases":[{"0":"1040","vim_version":"6.0","1":"6.0","script_version":"1.1","2":"1.1","version_comment":"Added 'hidden' option\r\n\r\n","3":"Added 'hidden' option\r\n\r\n","package":"vimtabs.vim","4":"vimtabs.vim","src_id":"3255","5":"3255","creation_date":"1090388628","6":"1090388628"}]},"1039":{"script_id":"1039","0":"1039","script_name":"array.vim","1":"array.vim","script_type":"utility","2":"utility","summary":"Implements multi-dimensional arrays in vim.","3":"Implements multi-dimensional arrays in vim.","description":"array.vim implements multi-dimensional arrays in vim.  It has creation, deletion, manipulation, utility, and infomation commands\/functions.  Usage is as simple as\r\n\r\nlet myVar=b:array:1:2:3:\r\n\r\nIncludes an example usage file.  Use ARRAYSYN and ARRAYUSE for information or see included documentation.","4":"array.vim implements multi-dimensional arrays in vim.  It has creation, deletion, manipulation, utility, and infomation commands\/functions.  Usage is as simple as\r\n\r\nlet myVar=b:array:1:2:3:\r\n\r\nIncludes an example usage file.  Use ARRAYSYN and ARRAYUSE for information or see included documentation.","install_details":"NOTE:  REQUIRES vsutil_vim.zip http:\/\/www.vim.org\/scripts\/script.php?script_id=1056\r\nunzip into .vim|vimfiles directory.","5":"NOTE:  REQUIRES vsutil_vim.zip http:\/\/www.vim.org\/scripts\/script.php?script_id=1056\r\nunzip into .vim|vimfiles directory.","first_name":"Dave","6":"Dave","last_name":"Silvia","7":"Silvia","releases":[{"0":"1039","vim_version":"6.0","1":"6.0","script_version":"1.2","2":"1.2","version_comment":"Version 1.2\r\n  Added:\r\n    -  ARRAYPUT puts elements\r\n       of one array into another\r\n\r\nRemoved ARRAYMAN use\r\ndocumentation instead.\r\n","3":"Version 1.2\r\n  Added:\r\n    -  ARRAYPUT puts elements\r\n       of one array into another\r\n\r\nRemoved ARRAYMAN use\r\ndocumentation instead.\r\n","package":"array_vim.zip","4":"array_vim.zip","src_id":"3408","5":"3408","creation_date":"1094087397","6":"1094087397"},{"0":"1039","vim_version":"6.0","1":"6.0","script_version":"1.1 c","2":"1.1 c","version_comment":"decoupled vsutil.vim\r\nvsutil.vim is now a separate package","3":"decoupled vsutil.vim\r\nvsutil.vim is now a separate package","package":"array_vim.zip","4":"array_vim.zip","src_id":"3329","5":"3329","creation_date":"1092414677","6":"1092414677"},{"0":"1039","vim_version":"6.0","1":"6.0","script_version":"1.0b","2":"1.0b","version_comment":"added .txt, .rtf, word .doc, and html versions of arrayman\r\nNOTE: the directory arrayman_files, though empty, is\r\n           necessary.  If deleted, the html is also deleted","3":"added .txt, .rtf, word .doc, and html versions of arrayman\r\nNOTE: the directory arrayman_files, though empty, is\r\n           necessary.  If deleted, the html is also deleted","package":"array_vim.zip","4":"array_vim.zip","src_id":"3260","5":"3260","creation_date":"1090474908","6":"1090474908"},{"0":"1039","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"array_vim.zip","4":"array_vim.zip","src_id":"3251","5":"3251","creation_date":"1090327715","6":"1090327715"}]},"1038":{"script_id":"1038","0":"1038","script_name":"vimgrep.vim","1":"vimgrep.vim","script_type":"utility","2":"utility","summary":"Editing utilities using grep\/find without external grep\/find programs","3":"Editing utilities using grep\/find without external grep\/find programs","description":"grep\/find utility wholly contained in Vim.  Commands implemented specifically to aid the editing task, not just find pattern matches.  Vimgrep() provides grep utility without an external grep type program.  It includes :help documentation grep-ing, selective or mass editing of files with matches, and display of output to command line or a named buffer.  Vimfind() provides find utility without an external find type program and offers same selective\/mass editing as Vimgrep(). See doc directory in package for various documentation file formats and select one for more information.","4":"grep\/find utility wholly contained in Vim.  Commands implemented specifically to aid the editing task, not just find pattern matches.  Vimgrep() provides grep utility without an external grep type program.  It includes :help documentation grep-ing, selective or mass editing of files with matches, and display of output to command line or a named buffer.  Vimfind() provides find utility without an external find type program and offers same selective\/mass editing as Vimgrep(). See doc directory in package for various documentation file formats and select one for more information.","install_details":"NOTE:  REQUIRES vsutil_vim.zip http:\/\/www.vim.org\/scripts\/script.php?script_id=1056\r\nUnzip into your .vim|vimfiles directory.","5":"NOTE:  REQUIRES vsutil_vim.zip http:\/\/www.vim.org\/scripts\/script.php?script_id=1056\r\nUnzip into your .vim|vimfiles directory.","first_name":"Dave","6":"Dave","last_name":"Silvia","7":"Silvia","releases":[{"0":"1038","vim_version":"6.0","1":"6.0","script_version":"3.2","2":"3.2","version_comment":"Version 3.2\r\n  Added:\r\n    -  VimfindEdit\/EditVimfind()\r\n       operates the same as\r\n       VimgrepEdit\/EditVimgrep()\r\n       VimgrepEditDel functionality\r\n       also applies.","3":"Version 3.2\r\n  Added:\r\n    -  VimfindEdit\/EditVimfind()\r\n       operates the same as\r\n       VimgrepEdit\/EditVimgrep()\r\n       VimgrepEditDel functionality\r\n       also applies.","package":"vimgrep.zip","4":"vimgrep.zip","src_id":"3407","5":"3407","creation_date":"1094062184","6":"1094062184"},{"0":"1038","vim_version":"6.0","1":"6.0","script_version":"3.1","2":"3.1","version_comment":"Version 3.1\r\n  Enhanced:\r\n   -  Rewrote s:vimGrep() for\r\n      search optimization.","3":"Version 3.1\r\n  Enhanced:\r\n   -  Rewrote s:vimGrep() for\r\n      search optimization.","package":"vimgrep_vim.zip","4":"vimgrep_vim.zip","src_id":"3357","5":"3357","creation_date":"1092935529","6":"1092935529"},{"0":"1038","vim_version":"6.0","1":"6.0","script_version":"3.0 b","2":"3.0 b","version_comment":"decoupled vsutil.vim\r\ndecoupled curBuf.vim\r\nthese are now separate packages","3":"decoupled vsutil.vim\r\ndecoupled curBuf.vim\r\nthese are now separate packages","package":"vimgrep_vim.zip","4":"vimgrep_vim.zip","src_id":"3330","5":"3330","creation_date":"1092414776","6":"1092414776"},{"0":"1038","vim_version":"6.0","1":"6.0","script_version":"3.0","2":"3.0","version_comment":"Version 3.0\r\n  New:\r\n   -  Rewrote to change optional\r\n      arguments to switches instead\r\n      of positional arguments.\r\n      Simplifies usage.\r\n   -  Changed documentation to\r\n      reflect same.\r\n  Misc:\r\n   -  Some minor code clean up\r\n   -  Removed use of dummy file\r\n      for empty Vim session.","3":"Version 3.0\r\n  New:\r\n   -  Rewrote to change optional\r\n      arguments to switches instead\r\n      of positional arguments.\r\n      Simplifies usage.\r\n   -  Changed documentation to\r\n      reflect same.\r\n  Misc:\r\n   -  Some minor code clean up\r\n   -  Removed use of dummy file\r\n      for empty Vim session.","package":"vimgrep_vim.zip","4":"vimgrep_vim.zip","src_id":"3313","5":"3313","creation_date":"1092177767","6":"1092177767"},{"0":"1038","vim_version":"6.0","1":"6.0","script_version":"2.2","2":"2.2","version_comment":" Version 2.2\r\n  Fixed:\r\n   -  Inappropriate inclusion of\r\n      command\/function arguments.\r\n  New:\r\n   -  Added BuiltInHelp\r\n   -  Added VimfindToBuf\r\n   -  Added VimfindList\r\n   -  Added VimgrepList\r\n   -  Added VimgrepHelpList\r\n   -  Added Command\/Function Help\r\n      menu\/mapped '??'\r\n\r\n      Vim[find|grep]List opens a\r\n      buffer listing file name\r\n      results from the respective\r\n      function.  Then simply cursor\r\n      to a line in the list, and\r\n      press 'o' to open the listed\r\n      file in an edit buffer.","3":" Version 2.2\r\n  Fixed:\r\n   -  Inappropriate inclusion of\r\n      command\/function arguments.\r\n  New:\r\n   -  Added BuiltInHelp\r\n   -  Added VimfindToBuf\r\n   -  Added VimfindList\r\n   -  Added VimgrepList\r\n   -  Added VimgrepHelpList\r\n   -  Added Command\/Function Help\r\n      menu\/mapped '??'\r\n\r\n      Vim[find|grep]List opens a\r\n      buffer listing file name\r\n      results from the respective\r\n      function.  Then simply cursor\r\n      to a line in the list, and\r\n      press 'o' to open the listed\r\n      file in an edit buffer.","package":"vimgrep_vim.zip","4":"vimgrep_vim.zip","src_id":"3308","5":"3308","creation_date":"1091993916","6":"1091993916"},{"0":"1038","vim_version":"6.0","1":"6.0","script_version":"2.1","2":"2.1","version_comment":"Many's the slip\r\nTwixt cup and lip\r\n\r\nSomehow the wrong version\r\ngot put into the zip\r\nThis is the corrected one","3":"Many's the slip\r\nTwixt cup and lip\r\n\r\nSomehow the wrong version\r\ngot put into the zip\r\nThis is the corrected one","package":"vimgrep_vim.zip","4":"vimgrep_vim.zip","src_id":"3300","5":"3300","creation_date":"1091576588","6":"1091576588"},{"0":"1038","vim_version":"6.0","1":"6.0","script_version":"2.1","2":"2.1","version_comment":"Version 2.1\r\n  Fixed:\r\n   -  echo-ed results scrolling off\r\n      command line by adding Pause()\r\n   -  problem with file argument\r\n      being '\/' would append '\/*' to\r\n      search which always failed.\r\n      Now only appends extra '\/' if\r\n      file argument does not end in\r\n      '\/' or '\\'.\r\n  Enhanced:\r\n   -  Stopped search after first match\r\n      if FNonly.  Do no search at all\r\n      if srchpat == '\\%$'\r\n  New:\r\n   -  Added Vimfind\r\n      (inspired by email from\r\n        Hari Krishna Dara)","3":"Version 2.1\r\n  Fixed:\r\n   -  echo-ed results scrolling off\r\n      command line by adding Pause()\r\n   -  problem with file argument\r\n      being '\/' would append '\/*' to\r\n      search which always failed.\r\n      Now only appends extra '\/' if\r\n      file argument does not end in\r\n      '\/' or '\\'.\r\n  Enhanced:\r\n   -  Stopped search after first match\r\n      if FNonly.  Do no search at all\r\n      if srchpat == '\\%$'\r\n  New:\r\n   -  Added Vimfind\r\n      (inspired by email from\r\n        Hari Krishna Dara)","package":"vimgrep_vim.zip","4":"vimgrep_vim.zip","src_id":"3299","5":"3299","creation_date":"1091574281","6":"1091574281"},{"0":"1038","vim_version":"6.0","1":"6.0","script_version":"2.0","2":"2.0","version_comment":"Version 2.0\r\n  Changed script name to vimgrep.vim\r\n  Introduced naming convention for\r\n  commands and functions.  Commands\r\n  begin Vimgrep[\\w*], functions and\r\n  variables begin [\\w*]Vimgrep\r\n\r\n  Function MiniVimGrep() obsoleted.\r\n  Replaced with Vimgrep().\r\n  Wrapper exists to maintain\r\n  backward compatibility.\r\n\r\n  New:\r\n   -  Added opening of edit buffers\r\n      for successfully grep-ed files.\r\n   -  Added help files grep-ing.\r\n   -  Added delete of edit\/help\r\n      buffers.\r\n   -  Added gvim menu\/toolbar items\r\n      and key mappings for deleting.\r\n   -  Included documentation files.\r\n   -  rewrote, beefed up, made more\r\n      robust, and otherwise enhanced.","3":"Version 2.0\r\n  Changed script name to vimgrep.vim\r\n  Introduced naming convention for\r\n  commands and functions.  Commands\r\n  begin Vimgrep[\\w*], functions and\r\n  variables begin [\\w*]Vimgrep\r\n\r\n  Function MiniVimGrep() obsoleted.\r\n  Replaced with Vimgrep().\r\n  Wrapper exists to maintain\r\n  backward compatibility.\r\n\r\n  New:\r\n   -  Added opening of edit buffers\r\n      for successfully grep-ed files.\r\n   -  Added help files grep-ing.\r\n   -  Added delete of edit\/help\r\n      buffers.\r\n   -  Added gvim menu\/toolbar items\r\n      and key mappings for deleting.\r\n   -  Included documentation files.\r\n   -  rewrote, beefed up, made more\r\n      robust, and otherwise enhanced.","package":"vimgrep_vim.zip","4":"vimgrep_vim.zip","src_id":"3292","5":"3292","creation_date":"1091324944","6":"1091324944"},{"0":"1038","vim_version":"6.0","1":"6.0","script_version":"1.1","2":"1.1","version_comment":"The two public functions are:\r\n\r\n     MiniVimGrep(pattern,file(s),[match case],[file names only])\r\n     BufMiniGrep(pattern,[match case],[file names only])\r\n\r\nwhere optional\r\n\r\n      'match case' is zero or non-zero\r\n      'file names only' is zero or non-zero\r\n\r\n\r\nMiniVimGrep() operates on file(s) arguments and BufMiniGrep() operates on open buffers.\r\n\r\nVersion 1.1\r\n  For grep-ing in open buffers:\r\n   -  Added BufMiniGrep for grep-ing all open buffers\r\n   -  Added code to set cursor to line 1, col 1 in the file in case it is\r\n      being done with open buffers.  Then the cursor is set back to its\r\n      original position.\r\n   -  Added code to allow passing '%' or '' for file, meaning current buffer\r\n   -  Added augroup and autocmd to save the buffer number so it can be used\r\n      to return to the original buffer if grep-ing in open buffers\r\n\r\n  For multiple files\r\n   -  Added code to check for comma and newline file name separators.\r\n      Comma allows the user to specify 'file' argument as\r\n      \"file1,file2,...\", while newline allows 'file' argument to be\r\n      something like glob(expand(\"%:p:h\").\"\/*\") or\r\n      glob(\"<some-path>\/*\")\r\n   -  Added code to check if file is the same as the original open\r\n      buffer, if so, don't do bdelete.\r\n   -  Added second optional argument for returning file names only.\r\n      If non-zero, just return file names, not the matching lines.\r\n\r\n  Misc\r\n   -  Added code to test for empty files\r\n   -  Added code to test for directories","3":"The two public functions are:\r\n\r\n     MiniVimGrep(pattern,file(s),[match case],[file names only])\r\n     BufMiniGrep(pattern,[match case],[file names only])\r\n\r\nwhere optional\r\n\r\n      'match case' is zero or non-zero\r\n      'file names only' is zero or non-zero\r\n\r\n\r\nMiniVimGrep() operates on file(s) arguments and BufMiniGrep() operates on open buffers.\r\n\r\nVersion 1.1\r\n  For grep-ing in open buffers:\r\n   -  Added BufMiniGrep for grep-ing all open buffers\r\n   -  Added code to set cursor to line 1, col 1 in the file in case it is\r\n      being done with open buffers.  Then the cursor is set back to its\r\n      original position.\r\n   -  Added code to allow passing '%' or '' for file, meaning current buffer\r\n   -  Added augroup and autocmd to save the buffer number so it can be used\r\n      to return to the original buffer if grep-ing in open buffers\r\n\r\n  For multiple files\r\n   -  Added code to check for comma and newline file name separators.\r\n      Comma allows the user to specify 'file' argument as\r\n      \"file1,file2,...\", while newline allows 'file' argument to be\r\n      something like glob(expand(\"%:p:h\").\"\/*\") or\r\n      glob(\"<some-path>\/*\")\r\n   -  Added code to check if file is the same as the original open\r\n      buffer, if so, don't do bdelete.\r\n   -  Added second optional argument for returning file names only.\r\n      If non-zero, just return file names, not the matching lines.\r\n\r\n  Misc\r\n   -  Added code to test for empty files\r\n   -  Added code to test for directories","package":"minigrep.vim","4":"minigrep.vim","src_id":"3253","5":"3253","creation_date":"1090361344","6":"1090361344"},{"0":"1038","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"minigrep.vim","4":"minigrep.vim","src_id":"3249","5":"3249","creation_date":"1090262718","6":"1090262718"}]},"1037":{"script_id":"1037","0":"1037","script_name":"HTMLxC.vim","1":"HTMLxC.vim","script_type":"utility","2":"utility","summary":"Edit hex color codes in HTML files easily using rgb decimal; Perl req\\'d.","3":"Edit hex color codes in HTML files easily using rgb decimal; Perl req\\'d.","description":"I\\'ve found that the default installed programs on my platform include several that specify colors as decimal r,g,b but none offer to show the color as the hexadecimal triplet used in HTML. It got to be very annoying to have to use a color browser or other graphics tool, then manually convert a color I liked to hex, before being able to even try out a color in a Web page I was building.\r\n\r\nThis small plugin utility just identifies the hex color spec under the cursor and pop-up dialogs (on GUI Vim) or prompts on the Vim commandline (on console Vim) for a decimal r g b -style spec (space-separated) and then inserts it as hex in replacement of the existing hex string.","4":"I\\'ve found that the default installed programs on my platform include several that specify colors as decimal r,g,b but none offer to show the color as the hexadecimal triplet used in HTML. It got to be very annoying to have to use a color browser or other graphics tool, then manually convert a color I liked to hex, before being able to even try out a color in a Web page I was building.\r\n\r\nThis small plugin utility just identifies the hex color spec under the cursor and pop-up dialogs (on GUI Vim) or prompts on the Vim commandline (on console Vim) for a decimal r g b -style spec (space-separated) and then inserts it as hex in replacement of the existing hex string.","install_details":"Requires that Vim have been compiled with support for Perl (embedded perl interpreter). Someone is likely to come along and say this can be written in Vim w\/o Perl. That\\'s fine. I like programming in Perl. I like my Vim to have Perl.\r\n\r\nJust place the HTMLxC.vim file in a plugin\/ dir in one of your $VIMRUNTIME locations. It then can be loaded with an \\\"au\\\" command from an initialization script or explicitly w\/ \\\":runtime!\\\" or \\\":source\\\". It does a key mapping ... <leader>*  (literally asterix) to call the plugin function.","5":"Requires that Vim have been compiled with support for Perl (embedded perl interpreter). Someone is likely to come along and say this can be written in Vim w\/o Perl. That\\'s fine. I like programming in Perl. I like my Vim to have Perl.\r\n\r\nJust place the HTMLxC.vim file in a plugin\/ dir in one of your $VIMRUNTIME locations. It then can be loaded with an \\\"au\\\" command from an initialization script or explicitly w\/ \\\":runtime!\\\" or \\\":source\\\". It does a key mapping ... <leader>*  (literally asterix) to call the plugin function.","first_name":"S\u00c3\u00b6ren","6":"S\u00c3\u00b6ren","last_name":"Andersen","7":"Andersen","releases":[{"0":"1037","vim_version":"6.0","1":"6.0","script_version":"1.2","2":"1.2","version_comment":"Initial upload","3":"Initial upload","package":"HTMLxC.vim","4":"HTMLxC.vim","src_id":"3247","5":"3247","creation_date":"1090216201","6":"1090216201"}]},"1036":{"script_id":"1036","0":"1036","script_name":"cream-iso3166-1","1":"cream-iso3166-1","script_type":"utility","2":"utility","summary":"Find ISO 3166-1 country codes and names","3":"Find ISO 3166-1 country codes and names","description":"\r\nFind the matching ISO3166-1 (http:\/\/en.wikipedia.org\/wiki\/ISO_3166-1) country code or name when passed the other.\r\n\r\n\r\nUsage\r\n\r\n  Cream_iso3166_1(word, ...)\r\n\r\no Test {word} for match of iso3166_1-compliant country name, 3- or 2-letter abbreviation, or 3-digit numerical code:\r\n  * Returns name if {word} matches either abbreviation.\r\n  * Returns 2-letter if {word} matches name or number.\r\n  * Returns 0 if no match is made.\r\no Use {optional} argument to force a given return:\r\n  * Returns 3-letter if {optional} is \"3\" and {word} matches.\r\n  * Returns 2-letter if {optional} is \"2\" and {word} matches.\r\n  * Returns name if {optional} is \"name\" and {word} matches.\r\n  * Returns number if {optional} is \"number\" and {word} matches.\r\n  * Returns 0 if no match is made.\r\no Matching is case-insensitive. But return values are capitalized according to the standard. (Name is title case, abbreviations are UPPER CASE.)\r\n\r\n\r\nExamples\r\n\r\n  :echo Cream_iso3166_1(\"AND\")               returns \"Andorra\"\r\n  :echo Cream_iso3166_1(\"AD\")                  returns \"Andorra\"\r\n  :echo Cream_iso3166_1(\"Andorra\")          returns \"AD\"\r\n  :echo Cream_iso3166_1(\"020\")                 returns \"AD\"\r\n\r\n  Return format forced:\r\n\r\n  :echo Cream_iso3166_1(\"AND\", \"3\")        returns \"AND\"\r\n  :echo Cream_iso3166_1(\"AD\", \"3\")           returns \"AND\"\r\n  :echo Cream_iso3166_1(\"Andorra\", \"3\")   returns \"AND\"\r\n  :echo Cream_iso3166_1(\"020\", \"3\")          returns \"AND\"\r\n\r\n  :echo Cream_iso3166_1(\"020\", \"2\")          returns \"AD\"\r\n  :echo Cream_iso3166_1(\"020\", \"name\")   returns \"Andorra\"\r\n  :echo Cream_iso3166_1(\"AD\", \"number\") returns \"020\"\r\n\r\n  Name or abbreviation unmatched:\r\n\r\n  :echo Cream_iso3166_1(\"not-a-name\")     returns 0\r\n  :echo Cream_iso3166_1(\"not\")                   returns 0\r\n\r\n","4":"\r\nFind the matching ISO3166-1 (http:\/\/en.wikipedia.org\/wiki\/ISO_3166-1) country code or name when passed the other.\r\n\r\n\r\nUsage\r\n\r\n  Cream_iso3166_1(word, ...)\r\n\r\no Test {word} for match of iso3166_1-compliant country name, 3- or 2-letter abbreviation, or 3-digit numerical code:\r\n  * Returns name if {word} matches either abbreviation.\r\n  * Returns 2-letter if {word} matches name or number.\r\n  * Returns 0 if no match is made.\r\no Use {optional} argument to force a given return:\r\n  * Returns 3-letter if {optional} is \"3\" and {word} matches.\r\n  * Returns 2-letter if {optional} is \"2\" and {word} matches.\r\n  * Returns name if {optional} is \"name\" and {word} matches.\r\n  * Returns number if {optional} is \"number\" and {word} matches.\r\n  * Returns 0 if no match is made.\r\no Matching is case-insensitive. But return values are capitalized according to the standard. (Name is title case, abbreviations are UPPER CASE.)\r\n\r\n\r\nExamples\r\n\r\n  :echo Cream_iso3166_1(\"AND\")               returns \"Andorra\"\r\n  :echo Cream_iso3166_1(\"AD\")                  returns \"Andorra\"\r\n  :echo Cream_iso3166_1(\"Andorra\")          returns \"AD\"\r\n  :echo Cream_iso3166_1(\"020\")                 returns \"AD\"\r\n\r\n  Return format forced:\r\n\r\n  :echo Cream_iso3166_1(\"AND\", \"3\")        returns \"AND\"\r\n  :echo Cream_iso3166_1(\"AD\", \"3\")           returns \"AND\"\r\n  :echo Cream_iso3166_1(\"Andorra\", \"3\")   returns \"AND\"\r\n  :echo Cream_iso3166_1(\"020\", \"3\")          returns \"AND\"\r\n\r\n  :echo Cream_iso3166_1(\"020\", \"2\")          returns \"AD\"\r\n  :echo Cream_iso3166_1(\"020\", \"name\")   returns \"Andorra\"\r\n  :echo Cream_iso3166_1(\"AD\", \"number\") returns \"020\"\r\n\r\n  Name or abbreviation unmatched:\r\n\r\n  :echo Cream_iso3166_1(\"not-a-name\")     returns 0\r\n  :echo Cream_iso3166_1(\"not\")                   returns 0\r\n\r\n","install_details":"\r\nSimply copy this file and paste it into your vimrc. Or you can drop the entire file into your plugins directory. \r\n\r\n","5":"\r\nSimply copy this file and paste it into your vimrc. Or you can drop the entire file into your plugins directory. \r\n\r\n","first_name":"Steve","6":"Steve","last_name":"Hall","7":"Hall","releases":[{"0":"1036","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"cream-iso3166-1.vim","4":"cream-iso3166-1.vim","src_id":"3245","5":"3245","creation_date":"1090094191","6":"1090094191"}]},"1035":{"script_id":"1035","0":"1035","script_name":"cream-iso639.vim","1":"cream-iso639.vim","script_type":"utility","2":"utility","summary":"Find ISO 639 language abbreviations and names","3":"Find ISO 639 language abbreviations and names","description":"Find the matching ISO 639 (http:\/\/www.loc.gov\/standards\/iso639-2\/langcodes.html) language abbreviation or name when passed the other.\r\n\r\nUsage\r\n\r\n  Cream_iso639(word, ...)\r\n\r\no Test {word} for match of ISO639-compliant language name, 3- or 2-letter abbreviation:\r\n  * Returns name if {word} matches either abbreviation.\r\n  * Returns 3-letter if {word} matches name.\r\n  * Returns 0 if no match is made.\r\no Use {optional} argument to force a given return:\r\n  * Returns 3-letter if {optional} is \"3\" and {word} matches.\r\n  * Returns 2-letter if {optional} is \"2\" and {word} matches. (If no 2-letter exists, the 3-letter is returned.)\r\n  * Returns name if {optional} is \"name\" and {word} matches.\r\n  * Returns 0 if no match is made.\r\no Matching is case-insensitive. But return values are capitalized according to the standard. (Name is title case, abbreviations are lower case.)\r\no In a number of cases, ISO639-2 allows multiple descriptive names for a language. \r\n  * When passed the matching abbreviation, the function will return the preferred description (listed first in the ISO list). \r\n  * Conversely, any of the listed descriptions can be matched, not just the preferred.\r\n\r\nExamples\r\n\r\n  Condition where 2- and 3-letter abbreviations exist a language:\r\n\r\n  :echo Cream_iso639(\"abk\")                      returns \"Abkhazian\"\r\n  :echo Cream_iso639(\"ab\")                        returns \"Abkhazian\"\r\n  :echo Cream_iso639(\"Abkhazian\")           returns \"abk\"\r\n\r\n  :echo Cream_iso639(\"Abkhazian\", \"3\")    returns \"abk\"\r\n  :echo Cream_iso639(\"abk\", \"3\")                returns \"abk\"\r\n  :echo Cream_iso639(\"ab\", \"3\")                  returns \"abk\"\r\n  :echo Cream_iso639(\"Abkhazian\", \"2\")    returns \"ab\"\r\n  :echo Cream_iso639(\"abk\", \"2\")                returns \"ab\"\r\n  :echo Cream_iso639(\"ab\", \"2\")                  returns \"ab\"\r\n  :echo Cream_iso639(\"Abkhazian\", \"name\")  returns \"Abkhazian\"\r\n  :echo Cream_iso639(\"abk\", \"name\")        returns \"Abkhazian\"\r\n  :echo Cream_iso639(\"ab\", \"name\")          returns \"Abkhazian\"\r\n\r\n  Condition where a 2-letter abbreviation doesn't exist for language:\r\n\r\n  :echo Cream_iso639(\"Achinese\")             returns \"ace\"\r\n  :echo Cream_iso639(\"ace\")                       returns \"Achinese\"\r\n  :echo Cream_iso639(\"Achinese\", \"2\")      returns \"ace\"\r\n  :echo Cream_iso639(\"ace\", \"2\")               returns \"ace\"\r\n\r\n  Name or abbreviation unmatched:\r\n\r\n  :echo Cream_iso639(\"not-a-name\")         returns 0\r\n  :echo Cream_iso639(\"not\")                       returns 0\r\n\r\n","4":"Find the matching ISO 639 (http:\/\/www.loc.gov\/standards\/iso639-2\/langcodes.html) language abbreviation or name when passed the other.\r\n\r\nUsage\r\n\r\n  Cream_iso639(word, ...)\r\n\r\no Test {word} for match of ISO639-compliant language name, 3- or 2-letter abbreviation:\r\n  * Returns name if {word} matches either abbreviation.\r\n  * Returns 3-letter if {word} matches name.\r\n  * Returns 0 if no match is made.\r\no Use {optional} argument to force a given return:\r\n  * Returns 3-letter if {optional} is \"3\" and {word} matches.\r\n  * Returns 2-letter if {optional} is \"2\" and {word} matches. (If no 2-letter exists, the 3-letter is returned.)\r\n  * Returns name if {optional} is \"name\" and {word} matches.\r\n  * Returns 0 if no match is made.\r\no Matching is case-insensitive. But return values are capitalized according to the standard. (Name is title case, abbreviations are lower case.)\r\no In a number of cases, ISO639-2 allows multiple descriptive names for a language. \r\n  * When passed the matching abbreviation, the function will return the preferred description (listed first in the ISO list). \r\n  * Conversely, any of the listed descriptions can be matched, not just the preferred.\r\n\r\nExamples\r\n\r\n  Condition where 2- and 3-letter abbreviations exist a language:\r\n\r\n  :echo Cream_iso639(\"abk\")                      returns \"Abkhazian\"\r\n  :echo Cream_iso639(\"ab\")                        returns \"Abkhazian\"\r\n  :echo Cream_iso639(\"Abkhazian\")           returns \"abk\"\r\n\r\n  :echo Cream_iso639(\"Abkhazian\", \"3\")    returns \"abk\"\r\n  :echo Cream_iso639(\"abk\", \"3\")                returns \"abk\"\r\n  :echo Cream_iso639(\"ab\", \"3\")                  returns \"abk\"\r\n  :echo Cream_iso639(\"Abkhazian\", \"2\")    returns \"ab\"\r\n  :echo Cream_iso639(\"abk\", \"2\")                returns \"ab\"\r\n  :echo Cream_iso639(\"ab\", \"2\")                  returns \"ab\"\r\n  :echo Cream_iso639(\"Abkhazian\", \"name\")  returns \"Abkhazian\"\r\n  :echo Cream_iso639(\"abk\", \"name\")        returns \"Abkhazian\"\r\n  :echo Cream_iso639(\"ab\", \"name\")          returns \"Abkhazian\"\r\n\r\n  Condition where a 2-letter abbreviation doesn't exist for language:\r\n\r\n  :echo Cream_iso639(\"Achinese\")             returns \"ace\"\r\n  :echo Cream_iso639(\"ace\")                       returns \"Achinese\"\r\n  :echo Cream_iso639(\"Achinese\", \"2\")      returns \"ace\"\r\n  :echo Cream_iso639(\"ace\", \"2\")               returns \"ace\"\r\n\r\n  Name or abbreviation unmatched:\r\n\r\n  :echo Cream_iso639(\"not-a-name\")         returns 0\r\n  :echo Cream_iso639(\"not\")                       returns 0\r\n\r\n","install_details":"\r\nSimply copy this file and paste it into your vimrc. Or you can drop the entire file into your plugins directory.\r\n\r\n","5":"\r\nSimply copy this file and paste it into your vimrc. Or you can drop the entire file into your plugins directory.\r\n\r\n","first_name":"Steve","6":"Steve","last_name":"Hall","7":"Hall","releases":[{"0":"1035","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"cream-iso639.vim","4":"cream-iso639.vim","src_id":"3244","5":"3244","creation_date":"1090074538","6":"1090074538"}]},"1034":{"script_id":"1034","0":"1034","script_name":"OOP.vim","1":"OOP.vim","script_type":"utility","2":"utility","summary":"Object Oriented Programming","3":"Object Oriented Programming","description":"This is my first try to make O.O.P. style in vim, i'm only a beginner in Vim, but i'm sure it will be usable for you all.\r\n\r\nSimple and easy. This is the first version so expect bugs!!\r\n\r\nThis is only an utility, and I will not assume any responsibility using it.\r\n","4":"This is my first try to make O.O.P. style in vim, i'm only a beginner in Vim, but i'm sure it will be usable for you all.\r\n\r\nSimple and easy. This is the first version so expect bugs!!\r\n\r\nThis is only an utility, and I will not assume any responsibility using it.\r\n","install_details":"You only need to source the OOP.vim file like this:\r\n\r\nso <path>\/oop.vim\r\n\r\nOr take it to your initialization files, it has another file called CarsOOPSample.vim, it's an OOP sample take a look.","5":"You only need to source the OOP.vim file like this:\r\n\r\nso <path>\/oop.vim\r\n\r\nOr take it to your initialization files, it has another file called CarsOOPSample.vim, it's an OOP sample take a look.","first_name":"Jess","6":"Jess","last_name":"me","7":"me","releases":[{"0":"1034","vim_version":"6.0","1":"6.0","script_version":"0.0.1a","2":"0.0.1a","version_comment":"Initial upload","3":"Initial upload","package":"oop-vim-0.0.1a.tar.gz","4":"oop-vim-0.0.1a.tar.gz","src_id":"3242","5":"3242","creation_date":"1090031944","6":"1090031944"}]},"1033":{"script_id":"1033","0":"1033","script_name":"commenter","1":"commenter","script_type":"utility","2":"utility","summary":"A handy comment\/uncomment plugin","3":"A handy comment\/uncomment plugin","description":"Usage：\r\n   In normal mode，press <Leader>c to comment\/uncomment current line.\r\n   If current line is blank line and no non-blank line before it, insert file header comment. The file header comment use template files. These templates should be placed to  ~\/.vim\/plugin\/templates\/ directory. template file name is same as cvim plugin.\r\n   If current line is function declaration line, and if g:DoxygenFuncDesc is set to 1, insert Doxygen style function comment. Else use function comment template file.\r\n   In visual mode, press <Leader>c to comment\/uncomment blocks. This only applies to c source or header files.\r\n\r\nMainly targeted:  c,h,cpp file modification\r\nAlso applicable：   java,sh,vim,awk,sed,perl,python file modification","4":"Usage：\r\n   In normal mode，press <Leader>c to comment\/uncomment current line.\r\n   If current line is blank line and no non-blank line before it, insert file header comment. The file header comment use template files. These templates should be placed to  ~\/.vim\/plugin\/templates\/ directory. template file name is same as cvim plugin.\r\n   If current line is function declaration line, and if g:DoxygenFuncDesc is set to 1, insert Doxygen style function comment. Else use function comment template file.\r\n   In visual mode, press <Leader>c to comment\/uncomment blocks. This only applies to c source or header files.\r\n\r\nMainly targeted:  c,h,cpp file modification\r\nAlso applicable：   java,sh,vim,awk,sed,perl,python file modification","install_details":"Linux: Copy commenter.vim to $HOME\/.vim\/plugin\/","5":"Linux: Copy commenter.vim to $HOME\/.vim\/plugin\/","first_name":"Sparks","6":"Sparks","last_name":"Lu","7":"Lu","releases":[{"0":"1033","vim_version":"6.0","1":"6.0","script_version":"0.8.1","2":"0.8.1","version_comment":"Use <Leader>ch to add #ifndef\/#define\/#endif lines for header files\r\nInsert comment symbol at beginning of line for block comment","3":"Use <Leader>ch to add #ifndef\/#define\/#endif lines for header files\r\nInsert comment symbol at beginning of line for block comment","package":"commenter.vim","4":"commenter.vim","src_id":"4662","5":"4662","creation_date":"1128981334","6":"1128981334"},{"0":"1033","vim_version":"6.0","1":"6.0","script_version":"0.8","2":"0.8","version_comment":"Allow any count of whitespace after comment symbol when uncommont line.\r\nInsert commont symbol immediately before first non-whitespace character instead of beginning of line.","3":"Allow any count of whitespace after comment symbol when uncommont line.\r\nInsert commont symbol immediately before first non-whitespace character instead of beginning of line.","package":"commenter.vim","4":"commenter.vim","src_id":"3887","5":"3887","creation_date":"1108941728","6":"1108941728"},{"0":"1033","vim_version":"6.0","1":"6.0","script_version":"0.7","2":"0.7","version_comment":"Use <Leader>c to commenter\/uncommenter instead of Ctrl-c.\r\nPython supported.","3":"Use <Leader>c to commenter\/uncommenter instead of Ctrl-c.\r\nPython supported.","package":"commenter.vim","4":"commenter.vim","src_id":"3541","5":"3541","creation_date":"1097615642","6":"1097615642"},{"0":"1033","vim_version":"6.0","1":"6.0","script_version":"0.6.1","2":"0.6.1","version_comment":"Initial upload","3":"Initial upload","package":"commenter.vim","4":"commenter.vim","src_id":"3238","5":"3238","creation_date":"1089942853","6":"1089942853"}]},"1032":{"script_id":"1032","0":"1032","script_name":"cream-iso639-2","1":"cream-iso639-2","script_type":"utility","2":"utility","summary":"(removed)","3":"(removed)","description":"Please see:\r\n\r\n  http:\/\/vim.sourceforge.net\/scripts\/script.php?script_id=1035\r\n\r\nfor an updated and more complete version that supports both 2 and 3 letter abbreviations.\r\n\r\n","4":"Please see:\r\n\r\n  http:\/\/vim.sourceforge.net\/scripts\/script.php?script_id=1035\r\n\r\nfor an updated and more complete version that supports both 2 and 3 letter abbreviations.\r\n\r\n","install_details":"","5":"","first_name":"Steve","6":"Steve","last_name":"Hall","7":"Hall","releases":[{"0":"1032","vim_version":"6.0","1":"6.0","script_version":"final","2":"final","version_comment":"This script now obsolete. Please reference the new one above.","3":"This script now obsolete. Please reference the new one above.","package":"null","4":"null","src_id":"3246","5":"3246","creation_date":"1090124400","6":"1090124400"}]},"1031":{"script_id":"1031","0":"1031","script_name":"uc.vim","1":"uc.vim","script_type":"syntax","2":"syntax","summary":"syntax for Intel Network Processor Microcode","3":"syntax for Intel Network Processor Microcode","description":"syntax color file for Intel Network Processor Microcode","4":"syntax color file for Intel Network Processor Microcode","install_details":"in the distribution, place the downloaded uc.vim in your syntax directory (e.g. on windows vimfiles\/syntax or on unix .vim\/syntax).\r\n\r\nCreate a file \"filetype.vim\" which contains an autocommand for your filetype.\r\n(Autocommands were explained in section |40.3|.)  Example: >\r\n\r\n\taugroup filetypedetect\r\n\tau BufNewFile,BufRead *.uc setf uc\r\n\taugroup END","5":"in the distribution, place the downloaded uc.vim in your syntax directory (e.g. on windows vimfiles\/syntax or on unix .vim\/syntax).\r\n\r\nCreate a file \"filetype.vim\" which contains an autocommand for your filetype.\r\n(Autocommands were explained in section |40.3|.)  Example: >\r\n\r\n\taugroup filetypedetect\r\n\tau BufNewFile,BufRead *.uc setf uc\r\n\taugroup END","first_name":"wei","6":"wei","last_name":"Gui","7":"Gui","releases":[{"0":"1031","vim_version":"6.0","1":"6.0","script_version":"0.04","2":"0.04","version_comment":"fix bug that Number not perporly colored in comments","3":"fix bug that Number not perporly colored in comments","package":"uc.vim","4":"uc.vim","src_id":"3274","5":"3274","creation_date":"1090780232","6":"1090780232"},{"0":"1031","vim_version":"6.0","1":"6.0","script_version":"0.03","2":"0.03","version_comment":"add options manipulate the syntax:\r\nuc_comment_strings\tstrings and numbers inside a comment\r\nuc_space_errors\t\ttrailing white space and spaces before a <Tab>\r\nuc_no_trail_space_error\t ... but no trailing spaces\r\nuc_no_tab_space_error\t ... but no spaces before a <Tab>\r\nuc_no_bracket_error\tdon't highlight {}; inside [] as errors\r\n\r\nadd syntax color for transfer register\r\nfix some misconfig\r\nuc_no_if0\t\tdon't highlight \"#if 0\" blocks as comments\r\n","3":"add options manipulate the syntax:\r\nuc_comment_strings\tstrings and numbers inside a comment\r\nuc_space_errors\t\ttrailing white space and spaces before a <Tab>\r\nuc_no_trail_space_error\t ... but no trailing spaces\r\nuc_no_tab_space_error\t ... but no spaces before a <Tab>\r\nuc_no_bracket_error\tdon't highlight {}; inside [] as errors\r\n\r\nadd syntax color for transfer register\r\nfix some misconfig\r\nuc_no_if0\t\tdon't highlight \"#if 0\" blocks as comments\r\n","package":"uc.vim","4":"uc.vim","src_id":"3269","5":"3269","creation_date":"1090654408","6":"1090654408"},{"0":"1031","vim_version":"6.0","1":"6.0","script_version":"0.02","2":"0.02","version_comment":"Intel MicroCode\r\nadd syntax color for register variable","3":"Intel MicroCode\r\nadd syntax color for register variable","package":"uc.vim","4":"uc.vim","src_id":"3243","5":"3243","creation_date":"1090035091","6":"1090035091"},{"0":"1031","vim_version":"6.0","1":"6.0","script_version":"0.01","2":"0.01","version_comment":"Initial upload","3":"Initial upload","package":"uc.vim","4":"uc.vim","src_id":"3232","5":"3232","creation_date":"1089880437","6":"1089880437"}]},"1030":{"script_id":"1030","0":"1030","script_name":"scalefont","1":"scalefont","script_type":"utility","2":"utility","summary":"Switch between your favourite font\/gui settings","3":"Switch between your favourite font\/gui settings","description":"Sometimes you want to change the font size without changing the window \r\ngeometry. This plugin tries to set the 'guifont', 'columns', and 'lines' to \r\nappropriate values in order to achieve this goal. You can define modes to \r\nquickly switch between your favourite gui configuration: fonts, window \r\nposition and size, guioption settings etc.\r\n","4":"Sometimes you want to change the font size without changing the window \r\ngeometry. This plugin tries to set the 'guifont', 'columns', and 'lines' to \r\nappropriate values in order to achieve this goal. You can define modes to \r\nquickly switch between your favourite gui configuration: fonts, window \r\nposition and size, guioption settings etc.\r\n","install_details":"It is important to correctly configure the plugin because it will set \r\nthe font and the window size when being loaded unless the \r\ng:scaleFontDontSetOnStartup variable was defined.\r\n\r\nEdit the vba file and type: >\r\n\r\n    :so %\r\n\r\n<   See :help vimball for details. If you have difficulties or use vim 7.0, \r\n    please make sure, you have the current version of vimball\r\n    (vimscript #1502) installed.\r\n\r\nEdit |vimrc|:\r\n\r\n    Set g:scaleFontSize, g:scaleFontWidth, and g:scaleFont according to your \r\n    likings. \"#{SIZE}\" and \"#{WIDTH}\" will be replaced with the appropriate \r\n    values. On non-Windows systems you also have to define \r\n    ScaleFontMaximizeWindow().\r\n\r\n    Examples: >\r\n\r\n        let g:scaleFontSize  = 11\r\n        let g:scaleFontWidth = 8\r\n      \r\n<   Unix: >\r\n\r\n        let g:scaleFont = \"-misc-fixed-medium-r-semicondensed-*-#{SIZE}-120-*-*-c-*-iso8859-15\"\r\n\r\n<   Windows: >\r\n\r\n        let g:scaleFont = \"Lucida_Console:h#{SIZE}:cANSI\"\"\r\n\r\nCheck if ScaleFontMaximizeWindow() function is functional on your \r\nsystem. If not, redefine the function in |vimrc|.\r\n\r\nRestart vim.\r\n\r\n\r\nAlso available via git\r\nhttp:\/\/github.com\/tomtom\/scalefont_vim","5":"It is important to correctly configure the plugin because it will set \r\nthe font and the window size when being loaded unless the \r\ng:scaleFontDontSetOnStartup variable was defined.\r\n\r\nEdit the vba file and type: >\r\n\r\n    :so %\r\n\r\n<   See :help vimball for details. If you have difficulties or use vim 7.0, \r\n    please make sure, you have the current version of vimball\r\n    (vimscript #1502) installed.\r\n\r\nEdit |vimrc|:\r\n\r\n    Set g:scaleFontSize, g:scaleFontWidth, and g:scaleFont according to your \r\n    likings. \"#{SIZE}\" and \"#{WIDTH}\" will be replaced with the appropriate \r\n    values. On non-Windows systems you also have to define \r\n    ScaleFontMaximizeWindow().\r\n\r\n    Examples: >\r\n\r\n        let g:scaleFontSize  = 11\r\n        let g:scaleFontWidth = 8\r\n      \r\n<   Unix: >\r\n\r\n        let g:scaleFont = \"-misc-fixed-medium-r-semicondensed-*-#{SIZE}-120-*-*-c-*-iso8859-15\"\r\n\r\n<   Windows: >\r\n\r\n        let g:scaleFont = \"Lucida_Console:h#{SIZE}:cANSI\"\"\r\n\r\nCheck if ScaleFontMaximizeWindow() function is functional on your \r\nsystem. If not, redefine the function in |vimrc|.\r\n\r\nRestart vim.\r\n\r\n\r\nAlso available via git\r\nhttp:\/\/github.com\/tomtom\/scalefont_vim","first_name":"Tom","6":"Tom","last_name":"Link","7":"Link","releases":[{"0":"1030","vim_version":"7.0","1":"7.0","script_version":"1.4","2":"1.4","version_comment":"BufExec & WinExec options","3":"BufExec & WinExec options","package":"scalefont.vba.gz","4":"scalefont.vba.gz","src_id":"10001","5":"10001","creation_date":"1235221572","6":"1235221572"},{"0":"1030","vim_version":"7.0","1":"7.0","script_version":"1.3","2":"1.3","version_comment":"- Partial rewrite for vim7.0\r\n- Default configuration is now done with a dictionary.\r\n- On mode changes, always evaluate g:scaleFontExec__0 unless g:scaleFontAlwaysResetGuioptions is 0.\r\n- FIX: Error when switching back to Normal.\r\n- g:scaleFontMenuPrefix was replaced with g:scaleFontMenu\r\n- Load only in gui\r\n- s:ScaleFontSetSize(mode, ...): Arguments have changed\r\n","3":"- Partial rewrite for vim7.0\r\n- Default configuration is now done with a dictionary.\r\n- On mode changes, always evaluate g:scaleFontExec__0 unless g:scaleFontAlwaysResetGuioptions is 0.\r\n- FIX: Error when switching back to Normal.\r\n- g:scaleFontMenuPrefix was replaced with g:scaleFontMenu\r\n- Load only in gui\r\n- s:ScaleFontSetSize(mode, ...): Arguments have changed\r\n","package":"scalefont.vba.gz","4":"scalefont.vba.gz","src_id":"8408","5":"8408","creation_date":"1204860528","6":"1204860528"},{"0":"1030","vim_version":"6.0","1":"6.0","script_version":"1.1","2":"1.1","version_comment":"New variable g:scaleFontExec_{MODE}, the content of which will be executed before reconfiguring the window geometry. This can be used to set guioptions as needed (e.g., for a full screen mode without menu bar and all as for NormalFull). If this variable isn't set, the variable g:scaleFontExec_0 will be executed that resets the guioptions to its initial value.  ScaleFontMaximizeWindow() is defined for OS other than Windows too (kind of). Build modes menu (see g:scaleFontMenuPrefix).","3":"New variable g:scaleFontExec_{MODE}, the content of which will be executed before reconfiguring the window geometry. This can be used to set guioptions as needed (e.g., for a full screen mode without menu bar and all as for NormalFull). If this variable isn't set, the variable g:scaleFontExec_0 will be executed that resets the guioptions to its initial value.  ScaleFontMaximizeWindow() is defined for OS other than Windows too (kind of). Build modes menu (see g:scaleFontMenuPrefix).","package":"scalefont.zip","4":"scalefont.zip","src_id":"4123","5":"4123","creation_date":"1112697438","6":"1112697438"},{"0":"1030","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"We can now set the window\/frame position too (e.g.  NormalNarrowLeft and NormalWideTop); new standard modes: NormalMax, NormalNarrowLeft, NormalWideTop, bigMax; :ScaleFont as an alias to :ScaleFontMode; removed mode \"0\" from the mode list","3":"We can now set the window\/frame position too (e.g.  NormalNarrowLeft and NormalWideTop); new standard modes: NormalMax, NormalNarrowLeft, NormalWideTop, bigMax; :ScaleFont as an alias to :ScaleFontMode; removed mode \"0\" from the mode list","package":"scalefont.zip","4":"scalefont.zip","src_id":"3717","5":"3717","creation_date":"1103582527","6":"1103582527"},{"0":"1030","vim_version":"6.0","1":"6.0","script_version":"0.2","2":"0.2","version_comment":"Take care of whether the font size is increased or decreased; command line completion for ScaleFontMode; ability to define the desired lines and cols parameters per mode (if one of these variables is -1, the window will be maximized; on non-Windows systems you have to define ScaleFontMaximizeWindow() first); new standard modes \"largeMax\" and \"LargeMax\" (maximize the window)","3":"Take care of whether the font size is increased or decreased; command line completion for ScaleFontMode; ability to define the desired lines and cols parameters per mode (if one of these variables is -1, the window will be maximized; on non-Windows systems you have to define ScaleFontMaximizeWindow() first); new standard modes \"largeMax\" and \"LargeMax\" (maximize the window)","package":"scalefont.zip","4":"scalefont.zip","src_id":"3552","5":"3552","creation_date":"1097995913","6":"1097995913"},{"0":"1030","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"scalefont.vim","4":"scalefont.vim","src_id":"3230","5":"3230","creation_date":"1089859365","6":"1089859365"}]},"1029":{"script_id":"1029","0":"1029","script_name":"msvc2003","1":"msvc2003","script_type":"utility","2":"utility","summary":"Support Miscrosoft Visual C++ 2003 ToolKit","3":"Support Miscrosoft Visual C++ 2003 ToolKit","description":"Next version editing...","4":"Next version editing...","install_details":"\r\n","5":"\r\n","first_name":"zhang","6":"zhang","last_name":"bin","7":"bin","releases":[{"0":"1029","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"msvc2003.vim","4":"msvc2003.vim","src_id":"3225","5":"3225","creation_date":"1089766069","6":"1089766069"}]},"1028":{"script_id":"1028","0":"1028","script_name":"log.vim","1":"log.vim","script_type":"syntax","2":"syntax","summary":"coloring errors and warnings of make\/gcc output","3":"coloring errors and warnings of make\/gcc output","description":"This script easily colors errors and warnings in the output of a make \/ gcc call.\r\nIt's syntax matches mixed German\/English, which depends on the linux\/make\/gcc installation.\r\n","4":"This script easily colors errors and warnings in the output of a make \/ gcc call.\r\nIt's syntax matches mixed German\/English, which depends on the linux\/make\/gcc installation.\r\n","install_details":"Add it to your .vimfiles\/after\/syntax directory and source it when editing the make output.\r\nYou can add an autocmd to do this automatically when entering *.log files, which should\r\ncontain make's output (e.g. 'make >make.log 2>&1').\r\n","5":"Add it to your .vimfiles\/after\/syntax directory and source it when editing the make output.\r\nYou can add an autocmd to do this automatically when entering *.log files, which should\r\ncontain make's output (e.g. 'make >make.log 2>&1').\r\n","first_name":"thomas","6":"thomas","last_name":"ramming","7":"ramming","releases":[{"0":"1028","vim_version":"6.0","1":"6.0","script_version":"0.2","2":"0.2","version_comment":"added (copied) syntax highlightings for strings numbers, remarks, 'attention' etc.","3":"added (copied) syntax highlightings for strings numbers, remarks, 'attention' etc.","package":"log.vim","4":"log.vim","src_id":"3337","5":"3337","creation_date":"1092630087","6":"1092630087"},{"0":"1028","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"log.vim","4":"log.vim","src_id":"3214","5":"3214","creation_date":"1089242226","6":"1089242226"}]},"1027":{"script_id":"1027","0":"1027","script_name":"errsign","1":"errsign","script_type":"utility","2":"utility","summary":"Puts \">>\" signs at lines with errors","3":"Puts \">>\" signs at lines with errors","description":"This is a very simple script. It may be very bugous.\r\nJust type \\es and it puts \">>\" signs at all error lines.","4":"This is a very simple script. It may be very bugous.\r\nJust type \\es and it puts \">>\" signs at all error lines.","install_details":"Put errsign.vim into your plugins\/ directory","5":"Put errsign.vim into your plugins\/ directory","first_name":"Ilya","6":"Ilya","last_name":"Skriblovsky","7":"Skriblovsky","releases":[{"0":"1027","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"errsign.vim","4":"errsign.vim","src_id":"3213","5":"3213","creation_date":"1089209097","6":"1089209097"}]},"1026":{"script_id":"1026","0":"1026","script_name":"Visual Mark","1":"Visual Mark","script_type":"utility","2":"utility","summary":"Visual mark, similar to UltraEdit's bookmark","3":"Visual mark, similar to UltraEdit's bookmark","description":"This script uses Vim's \"sign\" capability to provide visual marks, similar to UltraEdit's bookmark. \r\n\r\n1.  For gvim, use \"Ctrl + F2\" to toggle a visual mark. \r\n     For both vim and gvim, use \"mm\" to toggle a visual mark.\r\n2.  Use \"F2\" to navigate through the visual marks forward in the file.\r\n3.  Use \"Shift + F2\" to navigate backwards.\r\n\r\nIf you do not like the highlighting scheme, you could change \"SignColor\" in the script.  Feedbacks are welcome. :-)\r\n\r\n","4":"This script uses Vim's \"sign\" capability to provide visual marks, similar to UltraEdit's bookmark. \r\n\r\n1.  For gvim, use \"Ctrl + F2\" to toggle a visual mark. \r\n     For both vim and gvim, use \"mm\" to toggle a visual mark.\r\n2.  Use \"F2\" to navigate through the visual marks forward in the file.\r\n3.  Use \"Shift + F2\" to navigate backwards.\r\n\r\nIf you do not like the highlighting scheme, you could change \"SignColor\" in the script.  Feedbacks are welcome. :-)\r\n\r\n","install_details":"Drop it in your Vim plugin directory.","5":"Drop it in your Vim plugin directory.","first_name":"Brian","6":"Brian","last_name":"Wang","7":"Wang","releases":[{"0":"1026","vim_version":"6.0","1":"6.0","script_version":"0.4","2":"0.4","version_comment":"Fixed a very nasty bug in the get_number function (Thank you,  Evgeny Filatov :-)","3":"Fixed a very nasty bug in the get_number function (Thank you,  Evgeny Filatov :-)","package":"visualmark.vim","4":"visualmark.vim","src_id":"4700","5":"4700","creation_date":"1130374966","6":"1130374966"},{"0":"1026","vim_version":"6.0","1":"6.0","script_version":"0.3","2":"0.3","version_comment":"Important bug fixes:  \r\n    - Now the script should work for the console version of VIM.  (The sign list is sorted in gvim, but in vim, it is not...)\r\n    - Map \"mm\" to toggle visual marks","3":"Important bug fixes:  \r\n    - Now the script should work for the console version of VIM.  (The sign list is sorted in gvim, but in vim, it is not...)\r\n    - Map \"mm\" to toggle visual marks","package":"visualmark.vim","4":"visualmark.vim","src_id":"4024","5":"4024","creation_date":"1110847049","6":"1110847049"}]},"1025":{"script_id":"1025","0":"1025","script_name":"xmlwf.vim","1":"xmlwf.vim","script_type":"utility","2":"utility","summary":"A compiler plugin for the xmlwf xml well-formedness checker","3":"A compiler plugin for the xmlwf xml well-formedness checker","description":"xmlwf is a command-line utility for checking whether an xml document is well-formed.  This plugin will enable you to use xmlwf through Vim to check the well-formedness of the xml file you are editing.  Vim will take you right to the errors, if there are any.","4":"xmlwf is a command-line utility for checking whether an xml document is well-formed.  This plugin will enable you to use xmlwf through Vim to check the well-formedness of the xml file you are editing.  Vim will take you right to the errors, if there are any.","install_details":"You must have the xmlwf utility on your system.  I believe it is part of the Expat library.  Copy the file to your compiler directory, usually ~\/.vim\/compiler\/.  To use it, open an xml file and type \":compiler xmlwf\".\r\nThen, \":make\".  It should take you directly to the first error in the document, if there are any.  Note: the xmlwf.vim file has UNIX line endings, so if you get a bunch of garbage when you try to use it on a windows machine (via cygwin, for example) just save the file with DOS line endings.","5":"You must have the xmlwf utility on your system.  I believe it is part of the Expat library.  Copy the file to your compiler directory, usually ~\/.vim\/compiler\/.  To use it, open an xml file and type \":compiler xmlwf\".\r\nThen, \":make\".  It should take you directly to the first error in the document, if there are any.  Note: the xmlwf.vim file has UNIX line endings, so if you get a bunch of garbage when you try to use it on a windows machine (via cygwin, for example) just save the file with DOS line endings.","first_name":"Robert","6":"Robert","last_name":"Rowsome","7":"Rowsome","releases":[{"0":"1025","vim_version":"6.0","1":"6.0","script_version":"0.2","2":"0.2","version_comment":"Updated my contact info","3":"Updated my contact info","package":"xmlwf.vim","4":"xmlwf.vim","src_id":"18417","5":"18417","creation_date":"1345150400","6":"1345150400"},{"0":"1025","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"xmlwf.vim","4":"xmlwf.vim","src_id":"3206","5":"3206","creation_date":"1089123122","6":"1089123122"}]},"1024":{"script_id":"1024","0":"1024","script_name":"IndentHL","1":"IndentHL","script_type":"syntax","2":"syntax","summary":"Vim Syntax Highlighting for indent whitespace","3":"Vim Syntax Highlighting for indent whitespace","description":"Tabs and spaces are colored in slightly different colors from lightest to\r\ndarkest for dark background or from darkest to lightest for light background\r\nexample (x is darkest color and z lightest):\r\n\r\n    function foo()\r\n    x if b\r\n    x y echo \\'something\\'\r\n    x y while c\r\n    x y z echo \\'something else\\'\r\n    x y endwhile\r\n    x endif\r\n    endfunction\r\n    \r\nActually it forms vertical stripes\r\n\r\nYou can switch it off and on by \r\n   :call OnOffIndentHi()\r\n","4":"Tabs and spaces are colored in slightly different colors from lightest to\r\ndarkest for dark background or from darkest to lightest for light background\r\nexample (x is darkest color and z lightest):\r\n\r\n    function foo()\r\n    x if b\r\n    x y echo \\'something\\'\r\n    x y while c\r\n    x y z echo \\'something else\\'\r\n    x y endwhile\r\n    x endif\r\n    endfunction\r\n    \r\nActually it forms vertical stripes\r\n\r\nYou can switch it off and on by \r\n   :call OnOffIndentHi()\r\n","install_details":"Put script in  ~\/.vim\/after\/syntax\/php.vim\r\n               or \r\n               ~\/.vim\/after\/syntax\/c.vim\r\n               and\r\n               ~\/.vim\/after\/syntax\/php.vim\r\n               and\r\n               ~\/.vim\/after\/syntax\/vim.vim\r\n               and\r\n               ~\/.vim\/after\/syntax\/html.vim\r\n                                                    \r\nI haven\\'t test it with other syntaxes but hopefully works","5":"Put script in  ~\/.vim\/after\/syntax\/php.vim\r\n               or \r\n               ~\/.vim\/after\/syntax\/c.vim\r\n               and\r\n               ~\/.vim\/after\/syntax\/php.vim\r\n               and\r\n               ~\/.vim\/after\/syntax\/vim.vim\r\n               and\r\n               ~\/.vim\/after\/syntax\/html.vim\r\n                                                    \r\nI haven\\'t test it with other syntaxes but hopefully works","first_name":"Vedran","6":"Vedran","last_name":"Sajko","7":"Sajko","releases":[{"0":"1024","vim_version":"6.0","1":"6.0","script_version":"0.2","2":"0.2","version_comment":"support for light background,\r\ncorrected some bugs\r\nand some checking added\r\n","3":"support for light background,\r\ncorrected some bugs\r\nand some checking added\r\n","package":"IndentHL.vim","4":"IndentHL.vim","src_id":"3210","5":"3210","creation_date":"1089183824","6":"1089183824"},{"0":"1024","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"IndentHL.vim","4":"IndentHL.vim","src_id":"3204","5":"3204","creation_date":"1089097211","6":"1089097211"}]},"1023":{"script_id":"1023","0":"1023","script_name":"aftersyntax.vim","1":"aftersyntax.vim","script_type":"syntax","2":"syntax","summary":"Allows a single language (filetype) to have multiple .vim\/after\/syntax\/ files","3":"Allows a single language (filetype) to have multiple .vim\/after\/syntax\/ files","description":"Currently one may have a single syntax file per filetype in the .vim\/after\/syntax directory.  Such files are loaded after the main syntax handling file, and are used to provide additional customized syntax highlighting.  But, what if you want two or more such files for some filetype?  <aftersyntax.vim> solves just that problem...\r\n\r\nFor example, consider the C language and Andreechtchev Eugeni's opengl.vim extension for recognizing OpenGL functions and constants (vimscript#752) plus my blockhl.vim (vimscript#104) for highlighting leading tabs based on {} depth:\r\n\r\n\tExample:\r\n\t1. cd .vim\/after\/syntax\r\n\t2. mkdir c\r\n\t3. mv (wherever)\/aftersyntax.vim c.vim\r\n\t4. mv opengl.vim  c\r\n\t5. mv blockhl.vim c\r\n\r\nEvery time a C file is opened, both opengl.vim and blockhl.vim are sourced to provide their extra highlighting.\r\n","4":"Currently one may have a single syntax file per filetype in the .vim\/after\/syntax directory.  Such files are loaded after the main syntax handling file, and are used to provide additional customized syntax highlighting.  But, what if you want two or more such files for some filetype?  <aftersyntax.vim> solves just that problem...\r\n\r\nFor example, consider the C language and Andreechtchev Eugeni's opengl.vim extension for recognizing OpenGL functions and constants (vimscript#752) plus my blockhl.vim (vimscript#104) for highlighting leading tabs based on {} depth:\r\n\r\n\tExample:\r\n\t1. cd .vim\/after\/syntax\r\n\t2. mkdir c\r\n\t3. mv (wherever)\/aftersyntax.vim c.vim\r\n\t4. mv opengl.vim  c\r\n\t5. mv blockhl.vim c\r\n\r\nEvery time a C file is opened, both opengl.vim and blockhl.vim are sourced to provide their extra highlighting.\r\n","install_details":"(see the example above)\r\n1. cd .vim\/after\/syntax\r\n2. mkdir [the filetype you want multiple-file support for]\r\n3. mv or cp (ren or copy) aftersyntax.vim [new filetype].vim\r\n4. put whatever additional syntax highlighting files you wish in the\r\n   .vim\/after\/syntax\/[filetype]\/\r\n   directory.   They'll all be sourced for that filetype.\r\n\r\nNote for non-Unix users:\r\n\r\n1. Type vim\r\n   :echo &rtp\r\n\r\n   This will give you your \"runtimepath\".  (see :help 'rtp')\r\n   You'll see something like\r\n\r\n   \t   somepath\/vimfiles\r\n   \t   home:vimfiles\r\n   \t   somepath:vimfiles\r\n\r\n2. Under that directory, you may have such things as (I'll use\r\n   forward slashes (\/) here as vim usually displays them, although\r\n   they may \"actually\" use backslashes (\\) or dev:[some.path.vimfiles],\r\n   etc)\r\n\r\n   ...\/after\r\n   ...\/after\/syntax\r\n   ...\/doc\r\n   ...\/plugin\r\n\r\n   etc.  See :help 'rtp' for more...\r\n\r\n3. You may then rename\/copy this script into the ...\/after\/syntax\r\n   directory, make a subdirectory as for Unix, and put your syntax\r\n   files in it.\r\n","5":"(see the example above)\r\n1. cd .vim\/after\/syntax\r\n2. mkdir [the filetype you want multiple-file support for]\r\n3. mv or cp (ren or copy) aftersyntax.vim [new filetype].vim\r\n4. put whatever additional syntax highlighting files you wish in the\r\n   .vim\/after\/syntax\/[filetype]\/\r\n   directory.   They'll all be sourced for that filetype.\r\n\r\nNote for non-Unix users:\r\n\r\n1. Type vim\r\n   :echo &rtp\r\n\r\n   This will give you your \"runtimepath\".  (see :help 'rtp')\r\n   You'll see something like\r\n\r\n   \t   somepath\/vimfiles\r\n   \t   home:vimfiles\r\n   \t   somepath:vimfiles\r\n\r\n2. Under that directory, you may have such things as (I'll use\r\n   forward slashes (\/) here as vim usually displays them, although\r\n   they may \"actually\" use backslashes (\\) or dev:[some.path.vimfiles],\r\n   etc)\r\n\r\n   ...\/after\r\n   ...\/after\/syntax\r\n   ...\/doc\r\n   ...\/plugin\r\n\r\n   etc.  See :help 'rtp' for more...\r\n\r\n3. You may then rename\/copy this script into the ...\/after\/syntax\r\n   directory, make a subdirectory as for Unix, and put your syntax\r\n   files in it.\r\n","first_name":"Charles","6":"Charles","last_name":"Campbell","7":"Campbell","releases":[{"0":"1023","vim_version":"6.0","1":"6.0","script_version":"1","2":"1","version_comment":"Initial upload","3":"Initial upload","package":"aftersyntax.vim.bz2","4":"aftersyntax.vim.bz2","src_id":"3203","5":"3203","creation_date":"1088747555","6":"1088747555"}]},"1022":{"script_id":"1022","0":"1022","script_name":"Phoenity (discontinued)","1":"Phoenity (discontinued)","script_type":"game","2":"game","summary":"This script has been discontinued","3":"This script has been discontinued","description":"-","4":"-","install_details":"","5":"","first_name":"Char","6":"Char","last_name":"Only","7":"Only","releases":[{"0":"1022","vim_version":"6.0","1":"6.0","script_version":"0.0","2":"0.0","version_comment":"Dummy script","3":"Dummy script","package":"dummy.txt","4":"dummy.txt","src_id":"3618","5":"3618","creation_date":"1100134357","6":"1100134357"}]},"1021":{"script_id":"1021","0":"1021","script_name":"feralstub.vim","1":"feralstub.vim","script_type":"utility","2":"utility","summary":"Flexible stubs. (inspired by Dr.Chip's C-Stubs)","3":"Flexible stubs. (inspired by Dr.Chip's C-Stubs)","description":"The idea of this plugin (collection) is to allow you to easily setup and manage ex commands that happen when you (in insert mode) type a keyword (of your choice) and pretty a special char(easily configurable). For instance:\r\nfts`\r\nfts is the keyword (Feral Time Stamp)\r\n'`' is the special char that is used to invoke the main script.\r\n\r\nThis will result in:\r\n[Feral:176\/04@06:50]\r\nI.e. results in replacing fts with the string '[Feral:176\/04@06:50]'\r\n\r\nYou can add your own keywords via script functions and each keyword is dependant on a given file type.\r\n\r\nSo to define a global 'if' keyword you would do something like:\r\ncall FeralStub_AddNewExecute('', '\\<i\\%[f]\\>', \"norm! ciwif\\<CR>endif\\<ESC>kA \\<ESC>\")\r\n\r\nAn to define a 'if' keyword only for say .vim files:\r\ncall FeralStub_AddNewExecute('vim', '\\<i\\%[f]\\>', \"norm! ciwif\\<CR>endif\\<ESC>kA \\<ESC>\")\r\n\r\nOr to define an 'if' keyword for the current file type:\r\ncall FeralStub_AddNewExecute(&ft, '\\<i\\%[f]\\>', \"norm! ciwif\\<CR>endif\\<ESC>kA \\<ESC>\")\r\n\r\nSee the documentation in feralstub.vim for more specifics.\r\n\r\nIn brief:\r\ncall FeralStub_AddNewExecute(<filetype>, <match_pattern>, <ex_command_to_execute_when_keyword_matches_match_pattern>)\r\nOr\r\ncall FeralStub_AddNewFunction(<filetype>, <match_pattern>, <Global_Function_To_call_when_keyword_mattches_match_pattern>)\r\n\r\n\r\nThe end result is an easy way to add a new entry into this stub system, and to easily allow such entries to be added from various locations such as plugin, ftplugin or a script that is sourced on a per project basis (via autocommands for instance).\r\n\r\nThe match_pattern is fed directly to match() so what you can match is very flexable\r\nThe ex_command_to_execute_when_keyword_matches_match_pattern is fed directly to :execute\r\nThe Global_Function_To_call_when_keyword_mattches_match_pattern is fed directly to :call\r\n\r\n\r\nThe only downside I can foresee with this is:\r\n1. exit and restart vim to get a new pattern into the system.\r\n2. the 'ex' pattern is a pain but generally just i_CTRL-R_CTRL-R a recorded macro and the hard part is done.\r\n3. This makes extensive use of curly-braces-names and lots of vars.\r\n\r\n\r\n\r\n\r\nYou can easily change the default '`. special char to something else via two lines in your .vimrc (or the like)\r\nExamples: (in .vimrc)\r\nTo Specify A Different Typable Char:\r\nimap\t<unique>\t~\t<Plug>FeralStub_DO\r\nlet g:FeralStub_CharToInsertOnFailure = '~'\r\n\r\nTo Specify A Non Typable Char:\r\nimap\t<unique>\t<F12>\t<Plug>FeralStub_DO\r\nlet g:FeralStub_CharToInsertOnFailure = ''","4":"The idea of this plugin (collection) is to allow you to easily setup and manage ex commands that happen when you (in insert mode) type a keyword (of your choice) and pretty a special char(easily configurable). For instance:\r\nfts`\r\nfts is the keyword (Feral Time Stamp)\r\n'`' is the special char that is used to invoke the main script.\r\n\r\nThis will result in:\r\n[Feral:176\/04@06:50]\r\nI.e. results in replacing fts with the string '[Feral:176\/04@06:50]'\r\n\r\nYou can add your own keywords via script functions and each keyword is dependant on a given file type.\r\n\r\nSo to define a global 'if' keyword you would do something like:\r\ncall FeralStub_AddNewExecute('', '\\<i\\%[f]\\>', \"norm! ciwif\\<CR>endif\\<ESC>kA \\<ESC>\")\r\n\r\nAn to define a 'if' keyword only for say .vim files:\r\ncall FeralStub_AddNewExecute('vim', '\\<i\\%[f]\\>', \"norm! ciwif\\<CR>endif\\<ESC>kA \\<ESC>\")\r\n\r\nOr to define an 'if' keyword for the current file type:\r\ncall FeralStub_AddNewExecute(&ft, '\\<i\\%[f]\\>', \"norm! ciwif\\<CR>endif\\<ESC>kA \\<ESC>\")\r\n\r\nSee the documentation in feralstub.vim for more specifics.\r\n\r\nIn brief:\r\ncall FeralStub_AddNewExecute(<filetype>, <match_pattern>, <ex_command_to_execute_when_keyword_matches_match_pattern>)\r\nOr\r\ncall FeralStub_AddNewFunction(<filetype>, <match_pattern>, <Global_Function_To_call_when_keyword_mattches_match_pattern>)\r\n\r\n\r\nThe end result is an easy way to add a new entry into this stub system, and to easily allow such entries to be added from various locations such as plugin, ftplugin or a script that is sourced on a per project basis (via autocommands for instance).\r\n\r\nThe match_pattern is fed directly to match() so what you can match is very flexable\r\nThe ex_command_to_execute_when_keyword_matches_match_pattern is fed directly to :execute\r\nThe Global_Function_To_call_when_keyword_mattches_match_pattern is fed directly to :call\r\n\r\n\r\nThe only downside I can foresee with this is:\r\n1. exit and restart vim to get a new pattern into the system.\r\n2. the 'ex' pattern is a pain but generally just i_CTRL-R_CTRL-R a recorded macro and the hard part is done.\r\n3. This makes extensive use of curly-braces-names and lots of vars.\r\n\r\n\r\n\r\n\r\nYou can easily change the default '`. special char to something else via two lines in your .vimrc (or the like)\r\nExamples: (in .vimrc)\r\nTo Specify A Different Typable Char:\r\nimap\t<unique>\t~\t<Plug>FeralStub_DO\r\nlet g:FeralStub_CharToInsertOnFailure = '~'\r\n\r\nTo Specify A Non Typable Char:\r\nimap\t<unique>\t<F12>\t<Plug>FeralStub_DO\r\nlet g:FeralStub_CharToInsertOnFailure = ''","install_details":"To install unzip and place the files in their corresponding directories (each file lists where it should go and each file is in the directory it should go in)\r\n\r\n.\/vim\/plugin\\feralstub.vim\r\n.\/vim\/plugin\\feralstub_global.vim\r\n.\/vim\/ftplugin\\vim\\feralstubs_vim.vim\r\n\r\nHowever, '.\/vim\/ftplugin\\vim\\feralstubs_vim.vim' is an optional example","5":"To install unzip and place the files in their corresponding directories (each file lists where it should go and each file is in the directory it should go in)\r\n\r\n.\/vim\/plugin\\feralstub.vim\r\n.\/vim\/plugin\\feralstub_global.vim\r\n.\/vim\/ftplugin\\vim\\feralstubs_vim.vim\r\n\r\nHowever, '.\/vim\/ftplugin\\vim\\feralstubs_vim.vim' is an optional example","first_name":"Robert","6":"Robert","last_name":"KellyIV","7":"KellyIV","releases":[{"0":"1021","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"feralstub.zip","4":"feralstub.zip","src_id":"3178","5":"3178","creation_date":"1088061864","6":"1088061864"}]},"1020":{"script_id":"1020","0":"1020","script_name":"revolutions.vim","1":"revolutions.vim","script_type":"color scheme","2":"color scheme","summary":"Matrix Revolutions colorscheme (GUI only)","3":"Matrix Revolutions colorscheme (GUI only)","description":"\r\nDark background, greenish theme.\r\nEasy on the eyes, yet still readable.\r\nFor **long** coding hours :)\r\n\r\nInspired from the original matrix.vim theme,\r\nbut with different palettes and rules.\r\n","4":"\r\nDark background, greenish theme.\r\nEasy on the eyes, yet still readable.\r\nFor **long** coding hours :)\r\n\r\nInspired from the original matrix.vim theme,\r\nbut with different palettes and rules.\r\n","install_details":"\r\nDrop it inside .vim\/colors\r\n:color revolutions\r\n","5":"\r\nDrop it inside .vim\/colors\r\n:color revolutions\r\n","first_name":"Christian","6":"Christian","last_name":"MICHON","7":"MICHON","releases":[{"0":"1020","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"revolutions.vim","4":"revolutions.vim","src_id":"3175","5":"3175","creation_date":"1087966157","6":"1087966157"}]},"1019":{"script_id":"1019","0":"1019","script_name":"updt.vim","1":"updt.vim","script_type":"syntax","2":"syntax","summary":"Vim syntax file for ClearCase update log.","3":"Vim syntax file for ClearCase update log.","description":"A simple syntax file for coloring a Clear Case update log\r\nfile.","4":"A simple syntax file for coloring a Clear Case update log\r\nfile.","install_details":"Put it somewhere in your rtp\/syntax and the following to you\r\nfiletype detection:\r\n\r\naugroup filetypedetect\r\n    au BufNewFile,BufRead *.updt     setf updt\r\naugroup END","5":"Put it somewhere in your rtp\/syntax and the following to you\r\nfiletype detection:\r\n\r\naugroup filetypedetect\r\n    au BufNewFile,BufRead *.updt     setf updt\r\naugroup END","first_name":"Wenzhi","6":"Wenzhi","last_name":"Liang","7":"Liang","releases":[{"0":"1019","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"updt.vim","4":"updt.vim","src_id":"3174","5":"3174","creation_date":"1087962888","6":"1087962888"}]},"1018":{"script_id":"1018","0":"1018","script_name":"potwiki.vim","1":"potwiki.vim","script_type":"utility","2":"utility","summary":"Maintain a Wiki of plain text files","3":"Maintain a Wiki of plain text files","description":"If you like to keep notes in plain text files you might like this script.\r\npotwiki provides functions and mappings for conveniently maintaining \r\na Wiki of text files with vim.\r\n\r\nThe Wiki is a collection of text files in a single directory. These files\r\ncan contain hyper links to each other in the form of WikiWords.\r\n\r\nA WikiWord is a word which starts with an upper case letter and contains\r\nat least one lower case letter and another upper case letter in this\r\norder -- it's in 'camel case', e.g.\r\n\r\n  ThisIsAWikiWord\r\n\r\nSuch a WikiWord links to a file of exactly the same name in your\r\nWiki directory.\r\n\r\nWhen opening a Wiki file potwiki scans your Wiki directory to find\r\nwhich WikiWords are valid links. WikiWords without a corresponding\r\nfile are highlighted as errors (otherwise it doesn't matter).\r\n\r\nAfter installing the plugin see :help potwiki for further documentation.\r\n\r\n   The default mappings are defined as follow (By default, <Leader> stands\r\n   for '\\\\'. See |Leader| for more info) :\r\n\r\n   <Leader>ww   - open the Wiki HomePage\r\n   <Leader>wi   - open the Wiki index\r\n   <Leader>wf   - follow a WikiWord (can be used in any buffer!)\r\n   <Leader>we   - edit a Wiki file\r\n\r\n   The following mappings are present when editing a Wiki file:\r\n\r\n   <Leader><Leader> - close the file\r\n   <CR>             - follow the WikiWord under the cursor\r\n   <Tab>            - move to the next WikiWord\r\n   <BS>             - move to the previous WikiWord\r\n   <Leader>wr       - reload WikiWords\r\n","4":"If you like to keep notes in plain text files you might like this script.\r\npotwiki provides functions and mappings for conveniently maintaining \r\na Wiki of text files with vim.\r\n\r\nThe Wiki is a collection of text files in a single directory. These files\r\ncan contain hyper links to each other in the form of WikiWords.\r\n\r\nA WikiWord is a word which starts with an upper case letter and contains\r\nat least one lower case letter and another upper case letter in this\r\norder -- it's in 'camel case', e.g.\r\n\r\n  ThisIsAWikiWord\r\n\r\nSuch a WikiWord links to a file of exactly the same name in your\r\nWiki directory.\r\n\r\nWhen opening a Wiki file potwiki scans your Wiki directory to find\r\nwhich WikiWords are valid links. WikiWords without a corresponding\r\nfile are highlighted as errors (otherwise it doesn't matter).\r\n\r\nAfter installing the plugin see :help potwiki for further documentation.\r\n\r\n   The default mappings are defined as follow (By default, <Leader> stands\r\n   for '\\\\'. See |Leader| for more info) :\r\n\r\n   <Leader>ww   - open the Wiki HomePage\r\n   <Leader>wi   - open the Wiki index\r\n   <Leader>wf   - follow a WikiWord (can be used in any buffer!)\r\n   <Leader>we   - edit a Wiki file\r\n\r\n   The following mappings are present when editing a Wiki file:\r\n\r\n   <Leader><Leader> - close the file\r\n   <CR>             - follow the WikiWord under the cursor\r\n   <Tab>            - move to the next WikiWord\r\n   <BS>             - move to the previous WikiWord\r\n   <Leader>wr       - reload WikiWords\r\n","install_details":"Just drop potwiki.vim in your plugin directory (usually ~\/.vim\/plugin).\r\n\r\npotwiki automatically installs its documentation the next time you start vim.\r\n","5":"Just drop potwiki.vim in your plugin directory (usually ~\/.vim\/plugin).\r\n\r\npotwiki automatically installs its documentation the next time you start vim.\r\n","first_name":"Edwin","6":"Edwin","last_name":"Steiner","7":"Steiner","releases":[{"0":"1018","vim_version":"6.0","1":"6.0","script_version":"1.25","2":"1.25","version_comment":"Allow appending a configurable suffix to the names of WikiFiles.\r\n(contributed by Anders Carling)","3":"Allow appending a configurable suffix to the names of WikiFiles.\r\n(contributed by Anders Carling)","package":"potwiki.vim","4":"potwiki.vim","src_id":"9316","5":"9316","creation_date":"1223327253","6":"1223327253"},{"0":"1018","vim_version":"6.0","1":"6.0","script_version":"1.24","2":"1.24","version_comment":"Fixed bug causing \"E121: Undefined variable: g:potwiki_dir\"","3":"Fixed bug causing \"E121: Undefined variable: g:potwiki_dir\"","package":"potwiki.vim","4":"potwiki.vim","src_id":"6200","5":"6200","creation_date":"1158577143","6":"1158577143"},{"0":"1018","vim_version":"6.0","1":"6.0","script_version":"1.23","2":"1.23","version_comment":"Fixed regressions from 1.21, non-silent opening of WikiPages.","3":"Fixed regressions from 1.21, non-silent opening of WikiPages.","package":"potwiki.vim","4":"potwiki.vim","src_id":"6189","5":"6189","creation_date":"1158493655","6":"1158493655"},{"0":"1018","vim_version":"6.0","1":"6.0","script_version":"1.22","2":"1.22","version_comment":"Work-around for a bug in vim 7 <buffer> maps.","3":"Work-around for a bug in vim 7 <buffer> maps.","package":"potwiki.vim","4":"potwiki.vim","src_id":"5822","5":"5822","creation_date":"1149871958","6":"1149871958"},{"0":"1018","vim_version":"6.0","1":"6.0","script_version":"1.21","2":"1.21","version_comment":"autowrite when doing \\ww, \\wi, \\we, \\wf, ...","3":"autowrite when doing \\ww, \\wi, \\we, \\wf, ...","package":"potwiki.vim","4":"potwiki.vim","src_id":"4012","5":"4012","creation_date":"1110774187","6":"1110774187"},{"0":"1018","vim_version":"6.0","1":"6.0","script_version":"1.20","2":"1.20","version_comment":"Better potwiki-autowrite: write file only if changed, also autowrite\nwhen following another WikiWord with <CR>.\nPut the following in your .vimrc to use autowrite:\n    let potwiki_autowrite=1","3":"Better potwiki-autowrite: write file only if changed, also autowrite\nwhen following another WikiWord with <CR>.\nPut the following in your .vimrc to use autowrite:\n    let potwiki_autowrite=1","package":"potwiki.vim","4":"potwiki.vim","src_id":"3898","5":"3898","creation_date":"1109130876","6":"1109130876"},{"0":"1018","vim_version":"6.0","1":"6.0","script_version":"1.19","2":"1.19","version_comment":"Better interaction with :syntax on | enable | off.\nIf you want to use these commands put the line 'call PotwikiSyntax()' in a file called\n~\/.vim\/syntax\/potwiki.vim (You can also add customizations after this line.)","3":"Better interaction with :syntax on | enable | off.\nIf you want to use these commands put the line 'call PotwikiSyntax()' in a file called\n~\/.vim\/syntax\/potwiki.vim (You can also add customizations after this line.)","package":"potwiki.vim","4":"potwiki.vim","src_id":"3256","5":"3256","creation_date":"1090420039","6":"1090420039"},{"0":"1018","vim_version":"6.0","1":"6.0","script_version":"1.16","2":"1.16","version_comment":"fix navigation if more than one WikiWord is on a line (contributed by Michael Fitz)","3":"fix navigation if more than one WikiWord is on a line (contributed by Michael Fitz)","package":"potwiki.vim","4":"potwiki.vim","src_id":"3252","5":"3252","creation_date":"1090327726","6":"1090327726"},{"0":"1018","vim_version":"6.0","1":"6.0","script_version":"1.15","2":"1.15","version_comment":"fixed disappearing colors, work with hls set, better error handling,\nuse 'potwiki' filetype and syntax, removed umlauts from defaults\n(avoids problems with UTF-8 locales)","3":"fixed disappearing colors, work with hls set, better error handling,\nuse 'potwiki' filetype and syntax, removed umlauts from defaults\n(avoids problems with UTF-8 locales)","package":"potwiki.vim","4":"potwiki.vim","src_id":"3219","5":"3219","creation_date":"1089537586","6":"1089537586"},{"0":"1018","vim_version":"6.0","1":"6.0","script_version":"1.11","2":"1.11","version_comment":"work correctly when ignorecase is set,\nadded option: potwiki_ignore","3":"work correctly when ignorecase is set,\nadded option: potwiki_ignore","package":"potwiki.vim","4":"potwiki.vim","src_id":"3191","5":"3191","creation_date":"1088563742","6":"1088563742"},{"0":"1018","vim_version":"6.0","1":"6.0","script_version":"1.4","2":"1.4","version_comment":"Initial upload","3":"Initial upload","package":"potwiki.vim","4":"potwiki.vim","src_id":"3164","5":"3164","creation_date":"1087710901","6":"1087710901"}]},"1017":{"script_id":"1017","0":"1017","script_name":"redcode.vim","1":"redcode.vim","script_type":"syntax","2":"syntax","summary":"redcode assembler syntax","3":"redcode assembler syntax","description":"This file provides syntax definitions for the redcode assembly language.","4":"This file provides syntax definitions for the redcode assembly language.","install_details":"Put redcode.vim in ~\/.vim\/syntax\/ . \r\nYou may want to add a line to ~\/.vimrc or ~\/.vim\/filetype.vim to autodetect redcode assembly files.","5":"Put redcode.vim in ~\/.vim\/syntax\/ . \r\nYou may want to add a line to ~\/.vimrc or ~\/.vim\/filetype.vim to autodetect redcode assembly files.","first_name":"Lorenz","6":"Lorenz","last_name":"Wegener","7":"Wegener","releases":[{"0":"1017","vim_version":"6.0","1":"6.0","script_version":"1.1","2":"1.1","version_comment":"Initial upload","3":"Initial upload","package":"redcode.vim","4":"redcode.vim","src_id":"3161","5":"3161","creation_date":"1087657839","6":"1087657839"}]},"1016":{"script_id":"1016","0":"1016","script_name":"corewars.vim","1":"corewars.vim","script_type":"syntax","2":"syntax","summary":"syntax definitions for corewars cw-assembler","3":"syntax definitions for corewars cw-assembler","description":"This file provides syntax definitions of the corewars cw-assembly language.","4":"This file provides syntax definitions of the corewars cw-assembly language.","install_details":"Put corewars.vim in ~\/.vim\/syntax .\r\nYou may want to add a line to ~\/.vimrc or ~\/.vim\/filetype.vim to autodetect *.cw files.","5":"Put corewars.vim in ~\/.vim\/syntax .\r\nYou may want to add a line to ~\/.vimrc or ~\/.vim\/filetype.vim to autodetect *.cw files.","first_name":"Lorenz","6":"Lorenz","last_name":"Wegener","7":"Wegener","releases":[{"0":"1016","vim_version":"6.0","1":"6.0","script_version":"1.2","2":"1.2","version_comment":"Initial upload","3":"Initial upload","package":"corewars.vim","4":"corewars.vim","src_id":"3160","5":"3160","creation_date":"1087657630","6":"1087657630"}]},"1015":{"script_id":"1015","0":"1015","script_name":"check-mutt-attachments.vim","1":"check-mutt-attachments.vim","script_type":"utility","2":"utility","summary":"Script not to forget to attach files mentioned in an email","3":"Script not to forget to attach files mentioned in an email","description":"When using Vim to write an email from say Mutt, one can mention things like \"I am attaching the email I was telling you about\" and then forget to attach it.\r\n\r\nThis script prompts the user when exiting Vim pointing out that an attachment is mentioned in the message, and that may require something attached to the message.\r\n\r\nThis implements a suggestion made at: http:\/\/groups.google.fr\/groups?hl=fr&lr=&ie=UTF-8&selm=caq406%24rq4%241%40FreeBSD.csie.NCTU.edu.tw","4":"When using Vim to write an email from say Mutt, one can mention things like \"I am attaching the email I was telling you about\" and then forget to attach it.\r\n\r\nThis script prompts the user when exiting Vim pointing out that an attachment is mentioned in the message, and that may require something attached to the message.\r\n\r\nThis implements a suggestion made at: http:\/\/groups.google.fr\/groups?hl=fr&lr=&ie=UTF-8&selm=caq406%24rq4%241%40FreeBSD.csie.NCTU.edu.tw","install_details":"Drop the file in your plugin directory.\r\n\r\nIf you want to use it with software other than Mutt, tweak the autocmd line.","5":"Drop the file in your plugin directory.\r\n\r\nIf you want to use it with software other than Mutt, tweak the autocmd line.","first_name":"Hugo","6":"Hugo","last_name":"Haas","7":"Haas","releases":[{"0":"1015","vim_version":"6.0","1":"6.0","script_version":"20040620f2","2":"20040620f2","version_comment":"Fixed bug in regular expression which was making it always match.","3":"Fixed bug in regular expression which was making it always match.","package":"check-mutt-attachments.vim","4":"check-mutt-attachments.vim","src_id":"3165","5":"3165","creation_date":"1087713119","6":"1087713119"},{"0":"1015","vim_version":"6.0","1":"6.0","script_version":"20040620f","2":"20040620f","version_comment":"Added detection of French hints in addition to English ones.","3":"Added detection of French hints in addition to English ones.","package":"check-mutt-attachments.vim","4":"check-mutt-attachments.vim","src_id":"3162","5":"3162","creation_date":"1087692882","6":"1087692882"},{"0":"1015","vim_version":"6.0","1":"6.0","script_version":"20040620","2":"20040620","version_comment":"Initial upload","3":"Initial upload","package":"check-mutt-attachments.vim","4":"check-mutt-attachments.vim","src_id":"3159","5":"3159","creation_date":"1087636083","6":"1087636083"}]},"1014":{"script_id":"1014","0":"1014","script_name":"clipbrd","1":"clipbrd","script_type":"utility","2":"utility","summary":"Clipboard and other register content editor.","3":"Clipboard and other register content editor.","description":"Requires Vim 6.3\r\n\r\nSee vimtip#805 for an easy way to use the plugin as an external editor for most applications on windows.\r\n\r\nThis is a very simple utility that allows you to quickly view and edit contents (only those that are not read-only) of various registers that Vim supports. Most useful to quickly view and modify system clipboard using a shortcut (see Installation section). I often use this technique to even strip off the RTF to simple-text while copying from one application to other (that suppot RTF format, such as IE to Outlook).\r\n\r\n- Execute the default map (\\cb or <Leader>cb) or :ClipBrd command to view\r\n  the default register (\"*\", the clipboard register). You can also specify\r\n  the register name as an argument to the :ClipBrd command.\r\n- The register name is remembered (until you change it again by explicitly\r\n  specifying it) so that you don't have to specify it everytime you run\r\n  :ClipBrd command.\r\n- The \"[Clip Board]\" buffer is like a regular Vim file buffer, as you can\r\n  write (:w, :w!, :wq, :wq!), reload (:e, :e!) and quit (:q, :q!) the\r\n  buffer using the built-in Vim commands. Writing without the bang will\r\n  make the plugin prompt you for confirmation and where available, you can\r\n  click \"Cancel\" to prevent the buffer from quitting.\r\n- To refresh contents from the register, use :e or :e! command, or just\r\n  close and reopen the buffer. To quit without saving, just use the :q!\r\n  command.\r\n- Even other buffer commands and settings work as expected, e.g., you can\r\n  :hide the buffer if you can't decide to save or quit, and the contents\r\n  should remain the same when you come back, unless a different register\r\n  is explicitly specified while opening the clipboard. Setting 'bufhidden'\r\n  to \"hide\" or 'hidden' also should do the same.\r\n\r\n\r\nSearch_key_words: clipboard register genutils edit hari krishna dara","4":"Requires Vim 6.3\r\n\r\nSee vimtip#805 for an easy way to use the plugin as an external editor for most applications on windows.\r\n\r\nThis is a very simple utility that allows you to quickly view and edit contents (only those that are not read-only) of various registers that Vim supports. Most useful to quickly view and modify system clipboard using a shortcut (see Installation section). I often use this technique to even strip off the RTF to simple-text while copying from one application to other (that suppot RTF format, such as IE to Outlook).\r\n\r\n- Execute the default map (\\cb or <Leader>cb) or :ClipBrd command to view\r\n  the default register (\"*\", the clipboard register). You can also specify\r\n  the register name as an argument to the :ClipBrd command.\r\n- The register name is remembered (until you change it again by explicitly\r\n  specifying it) so that you don't have to specify it everytime you run\r\n  :ClipBrd command.\r\n- The \"[Clip Board]\" buffer is like a regular Vim file buffer, as you can\r\n  write (:w, :w!, :wq, :wq!), reload (:e, :e!) and quit (:q, :q!) the\r\n  buffer using the built-in Vim commands. Writing without the bang will\r\n  make the plugin prompt you for confirmation and where available, you can\r\n  click \"Cancel\" to prevent the buffer from quitting.\r\n- To refresh contents from the register, use :e or :e! command, or just\r\n  close and reopen the buffer. To quit without saving, just use the :q!\r\n  command.\r\n- Even other buffer commands and settings work as expected, e.g., you can\r\n  :hide the buffer if you can't decide to save or quit, and the contents\r\n  should remain the same when you come back, unless a different register\r\n  is explicitly specified while opening the clipboard. Setting 'bufhidden'\r\n  to \"hide\" or 'hidden' also should do the same.\r\n\r\n\r\nSearch_key_words: clipboard register genutils edit hari krishna dara","install_details":"Requires Vim 6.3\r\n\r\n- Place the file in your plugin directory.\r\n- Also install the latest genutils.vim.\r\n- If you don't like the default map (\\cb), change it by placing the\r\n  following in your vimrc (change <Your Map> appropriately):\r\n    nmap <unique> <silent> <Your Map> <Plug>ClipBrdOpen\r\n- If you want to change the default register from \"*\" to something else,\r\n  put the following in your vimrc:\r\n    let g:clipbrdDefaultReg = '+' \r\n  The default register is significant only the first time you invoke the\r\n  ClipBrd without specifying any register.  \r\n- You can optionally create a program shortcut with the following as the\r\n  command:\r\n                                                                         \r\n    gvim +ClipBrd +only\r\n                                                                         \r\n  This allows you to use the shortcut to quickly view and edit the\r\n  system clipboard. I find it extremely useful. Place the shortcut in a\r\n  quick reach (like the windows taskbar) and you will have a powerful\r\n  clipboard editor handy all the time.\r\n","5":"Requires Vim 6.3\r\n\r\n- Place the file in your plugin directory.\r\n- Also install the latest genutils.vim.\r\n- If you don't like the default map (\\cb), change it by placing the\r\n  following in your vimrc (change <Your Map> appropriately):\r\n    nmap <unique> <silent> <Your Map> <Plug>ClipBrdOpen\r\n- If you want to change the default register from \"*\" to something else,\r\n  put the following in your vimrc:\r\n    let g:clipbrdDefaultReg = '+' \r\n  The default register is significant only the first time you invoke the\r\n  ClipBrd without specifying any register.  \r\n- You can optionally create a program shortcut with the following as the\r\n  command:\r\n                                                                         \r\n    gvim +ClipBrd +only\r\n                                                                         \r\n  This allows you to use the shortcut to quickly view and edit the\r\n  system clipboard. I find it extremely useful. Place the shortcut in a\r\n  quick reach (like the windows taskbar) and you will have a powerful\r\n  clipboard editor handy all the time.\r\n","first_name":"Hari Krishna","6":"Hari Krishna","last_name":"Dara","7":"Dara","releases":[{"0":"1014","vim_version":"7.0","1":"7.0","script_version":"2.0","2":"2.0","version_comment":"- Updated to work with the latest version of genutils.vim\r\n- Bug fix: space in the plugin buffer name could cause issues.\r\n- Improved <C-G> in the plugin window to show some useful information.\r\n","3":"- Updated to work with the latest version of genutils.vim\r\n- Bug fix: space in the plugin buffer name could cause issues.\r\n- Improved <C-G> in the plugin window to show some useful information.\r\n","package":"clipbrd.vim","4":"clipbrd.vim","src_id":"7201","5":"7201","creation_date":"1180971526","6":"1180971526"},{"0":"1014","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"clipbrd.vim","4":"clipbrd.vim","src_id":"3149","5":"3149","creation_date":"1087568701","6":"1087568701"}]},"1013":{"script_id":"1013","0":"1013","script_name":"PLI-Tools","1":"PLI-Tools","script_type":"utility","2":"utility","summary":"Syntax, Indent and Goodies for IBM's Mainframe-PLI","3":"Syntax, Indent and Goodies for IBM's Mainframe-PLI","description":"Syntax-highlighting and indenting for IBM's PLI on mainframes (MVS; LE\/390; z\/OS etc.) when using the PLIOPT-Compiler.\r\nDoes recognize embedded SQL and CICS.\r\nSupports matchit-plugin\r\nSmart uppercasing (only source, no strings and\/or comments)\r\n","4":"Syntax-highlighting and indenting for IBM's PLI on mainframes (MVS; LE\/390; z\/OS etc.) when using the PLIOPT-Compiler.\r\nDoes recognize embedded SQL and CICS.\r\nSupports matchit-plugin\r\nSmart uppercasing (only source, no strings and\/or comments)\r\n","install_details":"1) copy the 3 pli.vim-files in the correct directories:\r\nftplugin\\pli.vim\r\nsyntax\\pli.vim\r\nindent\\pli.vim\r\n\r\n\r\n2) add into your runtime\\filetype.vim this lines:\r\n---BEG\r\n\" PLI\r\nau BufNewFile,BufRead *.PLI\t\tsetf pli\r\n---END\r\n\r\n3) add into your runtime\\synmenu.vim this lines (maybe you have to change the position-numbers):\r\n---BEG\r\nan 50.80.235 &Syntax.PQ.PLI :cal SetSyn(\"pli\")<CR>\r\n---END\r\n\r\n4) Be sure you use a color-schema which defines these highlights (or modify your schema or syntax\\pli.vim).\r\nItems marked by '*****' are very usually not in your environment!\r\n\r\n---BEG\r\nBuiltin   *****     \r\nCICS_Statement   *****\r\nComment\r\nError\r\nIdentifier\r\nIncludeFile   *****\r\nLabel\r\nNumber\r\nOperator\r\nPreProc   *****\r\nSQL_Statement   *****\r\nStatement\r\nString\r\nTodo\r\nType\r\n---END\r\n\r\n5) Vartabs\r\nTo have comfortable tabstops you should install vimscript #785 too, or you have to deactivate the corresponding line in runtime\\ftplugin\\PLI.vim.","5":"1) copy the 3 pli.vim-files in the correct directories:\r\nftplugin\\pli.vim\r\nsyntax\\pli.vim\r\nindent\\pli.vim\r\n\r\n\r\n2) add into your runtime\\filetype.vim this lines:\r\n---BEG\r\n\" PLI\r\nau BufNewFile,BufRead *.PLI\t\tsetf pli\r\n---END\r\n\r\n3) add into your runtime\\synmenu.vim this lines (maybe you have to change the position-numbers):\r\n---BEG\r\nan 50.80.235 &Syntax.PQ.PLI :cal SetSyn(\"pli\")<CR>\r\n---END\r\n\r\n4) Be sure you use a color-schema which defines these highlights (or modify your schema or syntax\\pli.vim).\r\nItems marked by '*****' are very usually not in your environment!\r\n\r\n---BEG\r\nBuiltin   *****     \r\nCICS_Statement   *****\r\nComment\r\nError\r\nIdentifier\r\nIncludeFile   *****\r\nLabel\r\nNumber\r\nOperator\r\nPreProc   *****\r\nSQL_Statement   *****\r\nStatement\r\nString\r\nTodo\r\nType\r\n---END\r\n\r\n5) Vartabs\r\nTo have comfortable tabstops you should install vimscript #785 too, or you have to deactivate the corresponding line in runtime\\ftplugin\\PLI.vim.","first_name":"Michael","6":"Michael","last_name":"Fitz","7":"Fitz","releases":[{"0":"1013","vim_version":"6.0","1":"6.0","script_version":"2.0","2":"2.0","version_comment":"Some minor improvements and corrections.\r\nExpanded for z\/OS (thanks to Ricky Wu, see #2685)","3":"Some minor improvements and corrections.\r\nExpanded for z\/OS (thanks to Ricky Wu, see #2685)","package":"PLI_tools.ZIP","4":"PLI_tools.ZIP","src_id":"21376","5":"21376","creation_date":"1390673945","6":"1390673945"},{"0":"1013","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"pli_tools.zip","4":"pli_tools.zip","src_id":"3146","5":"3146","creation_date":"1087473680","6":"1087473680"}]},"1012":{"script_id":"1012","0":"1012","script_name":"lingodirector.vim","1":"lingodirector.vim","script_type":"color scheme","2":"color scheme","summary":"original Director Lingo script colors","3":"original Director Lingo script colors","description":"These are the original script colors as Macromedia Director uses them. This color scheme will probably only make sense with the Lingo syntax file (vimscript #1010). This way you can not only see the colors your are used to, you can also convert them to HTML to put colored Lingo code snippets on your webpage.\r\nYou can even choose whether or not to put the line numbers in.\r\n\r\nScreenshots:\r\nhttp:\/\/www.oxpal.com\/downloads\/vim\/lingodirector_nonumber.png\r\nhttp:\/\/www.oxpal.com\/downloads\/vim\/lingodirector_number.png\r\n\r\nTo create an HTML output: \r\n* Open a lingo file. \r\n* Select this color scheme. \r\n* Type \":set number!\" to toggle the line numbers on and off\r\n* Then either choose the menu option \"Sytnax>Convert to HTML\", or type \":runtime! syntax\/2html.vim\"\r\n* You are then in the output file, wich you can save, or copy","4":"These are the original script colors as Macromedia Director uses them. This color scheme will probably only make sense with the Lingo syntax file (vimscript #1010). This way you can not only see the colors your are used to, you can also convert them to HTML to put colored Lingo code snippets on your webpage.\r\nYou can even choose whether or not to put the line numbers in.\r\n\r\nScreenshots:\r\nhttp:\/\/www.oxpal.com\/downloads\/vim\/lingodirector_nonumber.png\r\nhttp:\/\/www.oxpal.com\/downloads\/vim\/lingodirector_number.png\r\n\r\nTo create an HTML output: \r\n* Open a lingo file. \r\n* Select this color scheme. \r\n* Type \":set number!\" to toggle the line numbers on and off\r\n* Then either choose the menu option \"Sytnax>Convert to HTML\", or type \":runtime! syntax\/2html.vim\"\r\n* You are then in the output file, wich you can save, or copy","install_details":"Download and move to the ~\/.vim\/colors Folder. You can then choose the scheme from the menu (Edit>Color Scheme>lingodirector) or type \r\n:colorscheme lingodirector\r\n\r\nIf you want a colorscheme as default you simply write the command in your ~\/.vimrc file - in this case: \r\ncolorscheme lingodirector","5":"Download and move to the ~\/.vim\/colors Folder. You can then choose the scheme from the menu (Edit>Color Scheme>lingodirector) or type \r\n:colorscheme lingodirector\r\n\r\nIf you want a colorscheme as default you simply write the command in your ~\/.vimrc file - in this case: \r\ncolorscheme lingodirector","first_name":"Thomas","6":"Thomas","last_name":"Schmall","7":"Schmall","releases":[{"0":"1012","vim_version":"6.0","1":"6.0","script_version":"1.1","2":"1.1","version_comment":"added hi CursorLineNr  ","3":"added hi CursorLineNr  ","package":"lingodirector.vim","4":"lingodirector.vim","src_id":"19564","5":"19564","creation_date":"1361617458","6":"1361617458"},{"0":"1012","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"lingodirector.vim","4":"lingodirector.vim","src_id":"3141","5":"3141","creation_date":"1087414915","6":"1087414915"}]},"1011":{"script_id":"1011","0":"1011","script_name":"buflist","1":"buflist","script_type":"utility","2":"utility","summary":"Buffer browser","3":"Buffer browser","description":"The buffer browser plugin provides you an easy way to switch from a buffer to another. The layout has been inspired on the taglist script.\r\n\r\nPress the <F4> key to toggle the buffer list on and off. Help can be displayed by pressing the 'h' key. \r\n\r\nGeneral keymaps:\r\n\r\n- <S-F3>\/<S-F4> to decrease\/increase window height by 1\r\n- <C-S-F3>\/<C-S-F4> to decrease\/increase window height by 5\r\n\r\nUsage when not in buffer list:\r\n\r\n- <F4> to open\/access buffer list panel\r\n- \\\\0 to \\\\9 to mark window with number\r\n- \\\\p to mark window as preview window\r\n\r\nUsage when in buffer list:\r\n\r\n- h to toggle help\r\n- q to close buffer list (same as CTRL-W q)\r\n- p to preview file in preview window\r\n- d to delete currently selected buffer\r\n- u to update buffer list\r\n- x to toggle path display\r\n- s to toggle sorting by buffer number\/name\/extension\r\n- n\/N to edit file in new window below\/above <F4> \r\n- <CR> to edit file in last window visited before <F4>\r\n- \\\\0 to \\\\9 to edit file in window marked 0 to 9\r\n- <F4> to go back to <F4> window\r\n- <S-F3> to decrease buffer list width by 1\r\n- <S-F4> to increase buffer list width by 1\r\n- <C-S-F3> to decrease buffer list width by 5\r\n- <C-S-F4> to increase buffer list width by 5\r\n\r\nRemark: the \\ is in fact defined as <Leader>, it might thus change regarding your environment settings.\r\n\r\nChange log:\r\n\r\nFrom 1.6 to 1.7:\r\n\r\n- g:BufList_Hide set to 1 or 0 whether the buflist panel shall be respectively hidden or not once buffer is selected (<CR> key).\r\n- Copy buffer no longer erased when buffer is selected or when panel is updated.\r\n\r\nFrom 1.5 to 1.6:\r\n\r\n- buffer path display bug fix\r\n- nonumber set for buffer list (thanks to Ian)\r\n- <C-S-F3>\/<C-S-F4> for increasing\/decreasing window size\r\n","4":"The buffer browser plugin provides you an easy way to switch from a buffer to another. The layout has been inspired on the taglist script.\r\n\r\nPress the <F4> key to toggle the buffer list on and off. Help can be displayed by pressing the 'h' key. \r\n\r\nGeneral keymaps:\r\n\r\n- <S-F3>\/<S-F4> to decrease\/increase window height by 1\r\n- <C-S-F3>\/<C-S-F4> to decrease\/increase window height by 5\r\n\r\nUsage when not in buffer list:\r\n\r\n- <F4> to open\/access buffer list panel\r\n- \\\\0 to \\\\9 to mark window with number\r\n- \\\\p to mark window as preview window\r\n\r\nUsage when in buffer list:\r\n\r\n- h to toggle help\r\n- q to close buffer list (same as CTRL-W q)\r\n- p to preview file in preview window\r\n- d to delete currently selected buffer\r\n- u to update buffer list\r\n- x to toggle path display\r\n- s to toggle sorting by buffer number\/name\/extension\r\n- n\/N to edit file in new window below\/above <F4> \r\n- <CR> to edit file in last window visited before <F4>\r\n- \\\\0 to \\\\9 to edit file in window marked 0 to 9\r\n- <F4> to go back to <F4> window\r\n- <S-F3> to decrease buffer list width by 1\r\n- <S-F4> to increase buffer list width by 1\r\n- <C-S-F3> to decrease buffer list width by 5\r\n- <C-S-F4> to increase buffer list width by 5\r\n\r\nRemark: the \\ is in fact defined as <Leader>, it might thus change regarding your environment settings.\r\n\r\nChange log:\r\n\r\nFrom 1.6 to 1.7:\r\n\r\n- g:BufList_Hide set to 1 or 0 whether the buflist panel shall be respectively hidden or not once buffer is selected (<CR> key).\r\n- Copy buffer no longer erased when buffer is selected or when panel is updated.\r\n\r\nFrom 1.5 to 1.6:\r\n\r\n- buffer path display bug fix\r\n- nonumber set for buffer list (thanks to Ian)\r\n- <C-S-F3>\/<C-S-F4> for increasing\/decreasing window size\r\n","install_details":"Copy the buflist.vim file into your $VIM\/vimfiles\/plugin directory and restart VIM","5":"Copy the buflist.vim file into your $VIM\/vimfiles\/plugin directory and restart VIM","first_name":"Fabien","6":"Fabien","last_name":"Bouleau","7":"Bouleau","releases":[{"0":"1011","vim_version":"6.0","1":"6.0","script_version":"1.7","2":"1.7","version_comment":"Added g:BufList_Hide variable to autohide the buffer list when <CR> is pressed. Update of buflist panel and pressing <CR> do not erase copy buffer anylonger.","3":"Added g:BufList_Hide variable to autohide the buffer list when <CR> is pressed. Update of buflist panel and pressing <CR> do not erase copy buffer anylonger.","package":"buflist.vim","4":"buflist.vim","src_id":"5371","5":"5371","creation_date":"1141607617","6":"1141607617"},{"0":"1011","vim_version":"6.0","1":"6.0","script_version":"1.6","2":"1.6","version_comment":"Buffer path display bug fix, nonumber set for buffer list (thanks to Ian), added <C-S-F3>\/<C-S-F4> for increasing\/decreasing window size\r\n","3":"Buffer path display bug fix, nonumber set for buffer list (thanks to Ian), added <C-S-F3>\/<C-S-F4> for increasing\/decreasing window size\r\n","package":"buflist.vim","4":"buflist.vim","src_id":"3339","5":"3339","creation_date":"1092651531","6":"1092651531"}]},"1010":{"script_id":"1010","0":"1010","script_name":"lingo.vim","1":"lingo.vim","script_type":"syntax","2":"syntax","summary":"Lingo syntax highlighting","3":"Lingo syntax highlighting","description":"This is the syntax highlighting script for Macromedia Directors Lingo scripting language.\r\n\r\nI updated the file to the current version (MX2004). There might be some things missing. Feel free to add a new version here or contact me, if you want\/did enhancements. \r\n\r\nThis is an enhanced version of the lingo syntax file by Robert Robbins. I uploaded it as new script, because I stripped off the color definitions and entered new types.\r\n\r\nI now also created an color scheme, so you get the original Director syntax colors (vimscript #1012). This way you can convert them to HTML and put them on your website. Read the description at the color scheme for details.\r\n\r\nScreenshot:\r\nhttp:\/\/www.oxpal.com\/downloads\/vim\/lingodirector_nonumber.png","4":"This is the syntax highlighting script for Macromedia Directors Lingo scripting language.\r\n\r\nI updated the file to the current version (MX2004). There might be some things missing. Feel free to add a new version here or contact me, if you want\/did enhancements. \r\n\r\nThis is an enhanced version of the lingo syntax file by Robert Robbins. I uploaded it as new script, because I stripped off the color definitions and entered new types.\r\n\r\nI now also created an color scheme, so you get the original Director syntax colors (vimscript #1012). This way you can convert them to HTML and put them on your website. Read the description at the color scheme for details.\r\n\r\nScreenshot:\r\nhttp:\/\/www.oxpal.com\/downloads\/vim\/lingodirector_nonumber.png","install_details":"Put the lingo.vim file in ~\/.vim\/syntax\/ folder. \r\nYou may want  to add a line in your ~\/.vimrc or in ~\/.vim\/filetype.vim to load this syntax file for all *.ls files (this way the automatic highlighting will also work when starting the external editor from within Director).","5":"Put the lingo.vim file in ~\/.vim\/syntax\/ folder. \r\nYou may want  to add a line in your ~\/.vimrc or in ~\/.vim\/filetype.vim to load this syntax file for all *.ls files (this way the automatic highlighting will also work when starting the external editor from within Director).","first_name":"Thomas","6":"Thomas","last_name":"Schmall","7":"Schmall","releases":[{"0":"1010","vim_version":"6.0","1":"6.0","script_version":"1.2","2":"1.2","version_comment":"included keywords: bitmap, index, mapImageToStage","3":"included keywords: bitmap, index, mapImageToStage","package":"lingo.vim","4":"lingo.vim","src_id":"3639","5":"3639","creation_date":"1100670289","6":"1100670289"},{"0":"1010","vim_version":"6.0","1":"6.0","script_version":"1.1","2":"1.1","version_comment":"- entered some more keywords, and #\r\n- entered TODO commands for comments (not an original lingo feature)","3":"- entered some more keywords, and #\r\n- entered TODO commands for comments (not an original lingo feature)","package":"lingo.vim","4":"lingo.vim","src_id":"3296","5":"3296","creation_date":"1091515395","6":"1091515395"},{"0":"1010","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"lingo.vim","4":"lingo.vim","src_id":"3122","5":"3122","creation_date":"1087157456","6":"1087157456"}]},"1009":{"script_id":"1009","0":"1009","script_name":"srec.vim","1":"srec.vim","script_type":"syntax","2":"syntax","summary":"syntax file for s-record","3":"syntax file for s-record","description":"There's a filetype srec for S-record in filetype.vim. But no corresponding ftplugin and syntax, now, here it is.\r\nThe color schema is based on $VIMRUNTIME\/syntax\/hex.vim","4":"There's a filetype srec for S-record in filetype.vim. But no corresponding ftplugin and syntax, now, here it is.\r\nThe color schema is based on $VIMRUNTIME\/syntax\/hex.vim","install_details":"Just drop into $VIMRUNTIME\/syntax.","5":"Just drop into $VIMRUNTIME\/syntax.","first_name":"zhao","6":"zhao","last_name":"fei","7":"fei","releases":[{"0":"1009","vim_version":"6.0","1":"6.0","script_version":"6.3b","2":"6.3b","version_comment":"Initial upload","3":"Initial upload","package":"srec.vim","4":"srec.vim","src_id":"3119","5":"3119","creation_date":"1087146980","6":"1087146980"}]},"1008":{"script_id":"1008","0":"1008","script_name":"srec.vim","1":"srec.vim","script_type":"ftplugin","2":"ftplugin","summary":"ftplugin for Motolora s-record, correct checksum","3":"ftplugin for Motolora s-record, correct checksum","description":"the ftplugin can detect whether the current record's format is\r\ncorrect,\r\nif the data count is wrong, it will produce a message:\r\n========================\r\n    The data count of this record(3) is wrong!\r\n========================\r\nin which the 3 is the line number of the record.\r\nif the checksum is absense, the message will be:\r\n========================\r\nThis record looks have no checksum, press <C-K> to generate checksum for it\r\n========================\r\nIf the checksum is present, but wrong, it will complain about:\r\n========================\r\nThe Check sum is wrong!, should be: 0x27, Press <C-K> to correct it\r\n========================\r\n the 0x27 is the right CheckSum for it.\r\n\r\nAnytime You can press <C-K> to correct the checksum of current record. regardless of whether the checksum is already contained in the recorder. but if the data count is incorrect, nothing will be done.\r\n\r\nWith this plugin, one can easily modify existing s-record file, and then re-generate the checksum.\r\n:%norm ^K\r\n","4":"the ftplugin can detect whether the current record's format is\r\ncorrect,\r\nif the data count is wrong, it will produce a message:\r\n========================\r\n    The data count of this record(3) is wrong!\r\n========================\r\nin which the 3 is the line number of the record.\r\nif the checksum is absense, the message will be:\r\n========================\r\nThis record looks have no checksum, press <C-K> to generate checksum for it\r\n========================\r\nIf the checksum is present, but wrong, it will complain about:\r\n========================\r\nThe Check sum is wrong!, should be: 0x27, Press <C-K> to correct it\r\n========================\r\n the 0x27 is the right CheckSum for it.\r\n\r\nAnytime You can press <C-K> to correct the checksum of current record. regardless of whether the checksum is already contained in the recorder. but if the data count is incorrect, nothing will be done.\r\n\r\nWith this plugin, one can easily modify existing s-record file, and then re-generate the checksum.\r\n:%norm ^K\r\n","install_details":"Drop into $VIMRUNTIME\/ftplugin.\r\nNote: You needn't modify file type detection line to filetype.vim. It's already there.","5":"Drop into $VIMRUNTIME\/ftplugin.\r\nNote: You needn't modify file type detection line to filetype.vim. It's already there.","first_name":"zhao","6":"zhao","last_name":"fei","7":"fei","releases":[{"0":"1008","vim_version":"6.0","1":"6.0","script_version":"6.3b","2":"6.3b","version_comment":"Initial upload","3":"Initial upload","package":"srec.vim","4":"srec.vim","src_id":"3118","5":"3118","creation_date":"1087146580","6":"1087146580"}]},"1007":{"script_id":"1007","0":"1007","script_name":"Lynx Offline Documentation Browser","1":"Lynx Offline Documentation Browser","script_type":"utility","2":"utility","summary":"Lets you browse offline html docs in a buffer","3":"Lets you browse offline html docs in a buffer","description":"Inspired by the Info browser script, I present this script for bowsing html documentaion offline in a vim buffer via lynx. \r\n\r\n:Lynx index.html will create your buffer, then browsing is a matter of using the usual \"tag\" keys Ctrl-] and Ctrl-T. A link is indicated by lynx as a number in square brackets. Place the cursor over this (on the '[') and use Ctrl-] to follow the link.\r\n\r\nIt probably could be tidied up and also follow http: links as well as file: links but this is all I need to browse the wxPython docs offline which was what I wrote it for. Improvements welcome.\r\n\r\nThis has been tested on a Slackware 9.1 box with Vim 6.2. YMMV.\r\n","4":"Inspired by the Info browser script, I present this script for bowsing html documentaion offline in a vim buffer via lynx. \r\n\r\n:Lynx index.html will create your buffer, then browsing is a matter of using the usual \"tag\" keys Ctrl-] and Ctrl-T. A link is indicated by lynx as a number in square brackets. Place the cursor over this (on the '[') and use Ctrl-] to follow the link.\r\n\r\nIt probably could be tidied up and also follow http: links as well as file: links but this is all I need to browse the wxPython docs offline which was what I wrote it for. Improvements welcome.\r\n\r\nThis has been tested on a Slackware 9.1 box with Vim 6.2. YMMV.\r\n","install_details":"Put it in your vim plugins directory .... ","5":"Put it in your vim plugins directory .... ","first_name":"John","6":"John","last_name":"Connors","7":"Connors","releases":[{"0":"1007","vim_version":"6.0","1":"6.0","script_version":"0.01","2":"0.01","version_comment":"Initial upload","3":"Initial upload","package":"lynx.vim","4":"lynx.vim","src_id":"3114","5":"3114","creation_date":"1086961768","6":"1086961768"}]},"1006":{"script_id":"1006","0":"1006","script_name":"Olive","1":"Olive","script_type":"color scheme","2":"color scheme","summary":"Dark olive background and green-orange colors colorscheme","3":"Dark olive background and green-orange colors colorscheme","description":"Changed name from greenorange to olive ^_%\r\n\r\nThis colorscheme has dark olive green background, and some bright green-yellow color.\r\nOnly tested on java, c, vim, and LaTeX files. Not tested for long coding session :P\r\n\r\nGUI only. Some screenshots at http:\/\/cherry.f2g.net\/olive.html\r\n\r\nThanks.\r\n","4":"Changed name from greenorange to olive ^_%\r\n\r\nThis colorscheme has dark olive green background, and some bright green-yellow color.\r\nOnly tested on java, c, vim, and LaTeX files. Not tested for long coding session :P\r\n\r\nGUI only. Some screenshots at http:\/\/cherry.f2g.net\/olive.html\r\n\r\nThanks.\r\n","install_details":"Put in $VIMRUNTIME\/colors and type :colo olive","5":"Put in $VIMRUNTIME\/colors and type :colo olive","first_name":"Char","6":"Char","last_name":"Only","7":"Only","releases":[{"0":"1006","vim_version":"5.7","1":"5.7","script_version":"0.181","2":"0.181","version_comment":"Fixed some highlight settings.","3":"Fixed some highlight settings.","package":"olive.vim","4":"olive.vim","src_id":"3157","5":"3157","creation_date":"1087600946","6":"1087600946"},{"0":"1006","vim_version":"5.7","1":"5.7","script_version":"0.18","2":"0.18","version_comment":"Changed background color to dark olive (and changed the colorscheme name too :-), added fold and statusline color.","3":"Changed background color to dark olive (and changed the colorscheme name too :-), added fold and statusline color.","package":"olive.vim","4":"olive.vim","src_id":"3156","5":"3156","creation_date":"1087598148","6":"1087598148"}]},"1005":{"script_id":"1005","0":"1005","script_name":"Phrases","1":"Phrases","script_type":"utility","2":"utility","summary":"Find and highlight words\/phrases used repeatedly","3":"Find and highlight words\/phrases used repeatedly","description":"To start highlighting visually select the region in question and press <Enter>, to stop it\r\npress <Enter> once again.\r\n","4":"To start highlighting visually select the region in question and press <Enter>, to stop it\r\npress <Enter> once again.\r\n","install_details":"Drop it in the plugin directory!","5":"Drop it in the plugin directory!","first_name":"Klaus","6":"Klaus","last_name":"Bosau","7":"Bosau","releases":[{"0":"1005","vim_version":"6.0","1":"6.0","script_version":"0.9","2":"0.9","version_comment":"Initial upload","3":"Initial upload","package":"phrases.vim","4":"phrases.vim","src_id":"3108","5":"3108","creation_date":"1086801839","6":"1086801839"}]},"1004":{"script_id":"1004","0":"1004","script_name":"Docbook XSL compiler file","1":"Docbook XSL compiler file","script_type":"ftplugin","2":"ftplugin","summary":"DocBook XSL compiler file","3":"DocBook XSL compiler file","description":"Most people compile docbook documents with tools like jade or openjade. Other tools, like xsltproc, are possible.\r\n\r\nBasically, this script is a bound of commands in order to compile docbook documents correctly using xsltproc. It just set a few vim parameters like makeprg, errorformat and stringcomments.","4":"Most people compile docbook documents with tools like jade or openjade. Other tools, like xsltproc, are possible.\r\n\r\nBasically, this script is a bound of commands in order to compile docbook documents correctly using xsltproc. It just set a few vim parameters like makeprg, errorformat and stringcomments.","install_details":"Place this script under $VIM\/compiler.\r\n\r\nTo use it, type :compiler xsltproc.","5":"Place this script under $VIM\/compiler.\r\n\r\nTo use it, type :compiler xsltproc.","first_name":"Diego","6":"Diego","last_name":"Pino","7":"Pino","releases":[{"0":"1004","vim_version":"6.0","1":"6.0","script_version":"0.2","2":"0.2","version_comment":"Some bug fixes\r\n\r\nNow make command accepts parameters. Useful if you want to compile with -xinclude option.","3":"Some bug fixes\r\n\r\nNow make command accepts parameters. Useful if you want to compile with -xinclude option.","package":"xsltproc.vim","4":"xsltproc.vim","src_id":"3145","5":"3145","creation_date":"1087460233","6":"1087460233"},{"0":"1004","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"xsltproc.vim","4":"xsltproc.vim","src_id":"3099","5":"3099","creation_date":"1086426426","6":"1086426426"}]},"1003":{"script_id":"1003","0":"1003","script_name":"SearchInBuffers.vim","1":"SearchInBuffers.vim","script_type":"utility","2":"utility","summary":"Perform the current search in all the open buffers","3":"Perform the current search in all the open buffers","description":"This plugin allow you to search the current search pattern in all the buffers currently opened into VIM.\r\n\r\nJust do a search in whatsoever way into the current buffer and then run :SIB to process the same search in all the other open buffers.\r\n\r\nUse the quickfix commands (:cn, :cp, ...) to navigate through the patterns found, :cclose to close the found's list, that's all.\r\n\r\nDo ':help quickfix.txt' for more details.\r\n","4":"This plugin allow you to search the current search pattern in all the buffers currently opened into VIM.\r\n\r\nJust do a search in whatsoever way into the current buffer and then run :SIB to process the same search in all the other open buffers.\r\n\r\nUse the quickfix commands (:cn, :cp, ...) to navigate through the patterns found, :cclose to close the found's list, that's all.\r\n\r\nDo ':help quickfix.txt' for more details.\r\n","install_details":"Copy the SearchInBuffers.vim file into the VIM plugin directory.","5":"Copy the SearchInBuffers.vim file into the VIM plugin directory.","first_name":"Francesco","6":"Francesco","last_name":"Bradascio","7":"Bradascio","releases":[{"0":"1003","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"SearchInBuffers.vim","4":"SearchInBuffers.vim","src_id":"3097","5":"3097","creation_date":"1086421523","6":"1086421523"}]},"1002":{"script_id":"1002","0":"1002","script_name":"glsl.vim","1":"glsl.vim","script_type":"syntax","2":"syntax","summary":"Syntax file for the OpenGL Shading Language GLSL GLSlang","3":"Syntax file for the OpenGL Shading Language GLSL GLSlang","description":"Syntax file for the OpenGL Shading Language.  The following is highlighted (as defined in the\r\nOrange Book):\r\n\r\n  - All gl_ variables\r\n  - All built-in functions\r\n  - All keywords\r\n\r\nThe syntax file was modified from c.vim, so you can expect that your GLSL shaders\r\nwill be highlighted similar to C files.\r\n\r\nAll reserverd keywords (that GLSL currently does not use) are highlighted as errors.\r\n\r\nKeywords: glsl glslang opengl shading language","4":"Syntax file for the OpenGL Shading Language.  The following is highlighted (as defined in the\r\nOrange Book):\r\n\r\n  - All gl_ variables\r\n  - All built-in functions\r\n  - All keywords\r\n\r\nThe syntax file was modified from c.vim, so you can expect that your GLSL shaders\r\nwill be highlighted similar to C files.\r\n\r\nAll reserverd keywords (that GLSL currently does not use) are highlighted as errors.\r\n\r\nKeywords: glsl glslang opengl shading language","install_details":"Place glsl.vim in your syntax directory:\r\n\r\ncp glsl.vim $HOME\/.vim\/syntax\/.\r\n\r\nEnable highlighting with glsl.vim in your .vimrc with:\r\n\r\nau BufNewFile,BufRead *.frag,*.vert,*.fp,*.vp,*.glsl setf glsl\r\n\r\nor explicitly set the syntax with:\r\n\r\nset syntax=glsl","5":"Place glsl.vim in your syntax directory:\r\n\r\ncp glsl.vim $HOME\/.vim\/syntax\/.\r\n\r\nEnable highlighting with glsl.vim in your .vimrc with:\r\n\r\nau BufNewFile,BufRead *.frag,*.vert,*.fp,*.vp,*.glsl setf glsl\r\n\r\nor explicitly set the syntax with:\r\n\r\nset syntax=glsl","first_name":"Nathan","6":"Nathan","last_name":"Cournia","7":"Cournia","releases":[{"0":"1002","vim_version":"6.0","1":"6.0","script_version":"1.10.00","2":"1.10.00","version_comment":"- Updated syntax to match GLSL 1.10.59\r\n- Swizzles no longer conflict with structure member vars.\r\n  For example: the .s in gl_Light[0].shininess is no\r\n  longer incorrectly highlighted. (Thanks Nico Galoppo)","3":"- Updated syntax to match GLSL 1.10.59\r\n- Swizzles no longer conflict with structure member vars.\r\n  For example: the .s in gl_Light[0].shininess is no\r\n  longer incorrectly highlighted. (Thanks Nico Galoppo)","package":"glsl.vim","4":"glsl.vim","src_id":"3194","5":"3194","creation_date":"1088592382","6":"1088592382"},{"0":"1002","vim_version":"6.0","1":"6.0","script_version":"1.00.01","2":"1.00.01","version_comment":"- The following are now highlighted correctly:\r\n    - .p swizzle\r\n    - gl_MultiTexCoordN","3":"- The following are now highlighted correctly:\r\n    - .p swizzle\r\n    - gl_MultiTexCoordN","package":"glsl.vim","4":"glsl.vim","src_id":"3176","5":"3176","creation_date":"1087986890","6":"1087986890"},{"0":"1002","vim_version":"6.0","1":"6.0","script_version":"1","2":"1","version_comment":"Initial upload","3":"Initial upload","package":"glsl.vim","4":"glsl.vim","src_id":"3096","5":"3096","creation_date":"1086366270","6":"1086366270"}]},"1001":{"script_id":"1001","0":"1001","script_name":"2htmlj","1":"2htmlj","script_type":"syntax","2":"syntax","summary":"Slightly modified 2html.vim script for use with javadoc","3":"Slightly modified 2html.vim script for use with javadoc","description":"I have modified the great 2html.vim script contained in the distribution for use with javadoc documents. My changes may be of use to others as well.\r\n\r\nSpecific purpose: when creating Java API Documents with the -linksource option, the documents include copies of source code but (glaring omission) the html source pages are not syntax-highlighted.\r\n\r\nMy changes to the 2html.vim script allow the resulting html documents to be exchanged with those in the src-html folder thus creating syntax-highlighted html pages in the API documentation.\r\n\r\nThe key addition is the \"id\" attribute at the beginning of each code line so that every line of code can be reached like this: Hello.html#line.15.\r\n\r\nWhat was: <span class=\"lnr\"> 11<\/span>\r\nis now: <span id=\"line.11\" class=\"lnr\"> 11<\/span>\r\n\r\nI also added the options of short_name and short_title so that Hello.java becomes Hello.html not Hello.java.html and that the html document title is the name of the source file.\r\n\r\nPlease see my comments in the script.\r\n\r\nNote: I tried hard not to break anything in the existing script. I would appreciate any feedback. Thanks.","4":"I have modified the great 2html.vim script contained in the distribution for use with javadoc documents. My changes may be of use to others as well.\r\n\r\nSpecific purpose: when creating Java API Documents with the -linksource option, the documents include copies of source code but (glaring omission) the html source pages are not syntax-highlighted.\r\n\r\nMy changes to the 2html.vim script allow the resulting html documents to be exchanged with those in the src-html folder thus creating syntax-highlighted html pages in the API documentation.\r\n\r\nThe key addition is the \"id\" attribute at the beginning of each code line so that every line of code can be reached like this: Hello.html#line.15.\r\n\r\nWhat was: <span class=\"lnr\"> 11<\/span>\r\nis now: <span id=\"line.11\" class=\"lnr\"> 11<\/span>\r\n\r\nI also added the options of short_name and short_title so that Hello.java becomes Hello.html not Hello.java.html and that the html document title is the name of the source file.\r\n\r\nPlease see my comments in the script.\r\n\r\nNote: I tried hard not to break anything in the existing script. I would appreciate any feedback. Thanks.","install_details":"You must place this file in the Vim syntax folder (on my Mac, it's at: \/Applications\/vim\/Vim.app\/runtime\/syntax). You may rename it as 2html.vim and replace the existing script if you wish (please save the original if you do).\r\n\r\nTo use the javadoc functionality (with script saved as 2html.vim):\r\n:let javadoc = 1\r\n:runtime! syntax\/2html.vim \r\n\r\nTo hide line numbers but still have the id references to line numbers:\r\n:let javadoc_no_lnr = 1\r\n:runtime! syntax\/2html.vim","5":"You must place this file in the Vim syntax folder (on my Mac, it's at: \/Applications\/vim\/Vim.app\/runtime\/syntax). You may rename it as 2html.vim and replace the existing script if you wish (please save the original if you do).\r\n\r\nTo use the javadoc functionality (with script saved as 2html.vim):\r\n:let javadoc = 1\r\n:runtime! syntax\/2html.vim \r\n\r\nTo hide line numbers but still have the id references to line numbers:\r\n:let javadoc_no_lnr = 1\r\n:runtime! syntax\/2html.vim","first_name":"Charles","6":"Charles","last_name":"Shooshan","7":"Shooshan","releases":[{"0":"1001","vim_version":"6.0","1":"6.0","script_version":"1.1","2":"1.1","version_comment":"Minor change so Windows GUI will leave path off html short_title. Line 206 of code changed from: let s:source_file = expand(\"%\") to: let s:source_file = expand(\"%:t\") .","3":"Minor change so Windows GUI will leave path off html short_title. Line 206 of code changed from: let s:source_file = expand(\"%\") to: let s:source_file = expand(\"%:t\") .","package":"2htmlj.vim","4":"2htmlj.vim","src_id":"3089","5":"3089","creation_date":"1086099644","6":"1086099644"},{"0":"1001","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"2htmlj.vim","4":"2htmlj.vim","src_id":"3078","5":"3078","creation_date":"1086038538","6":"1086038538"}]},"1000":{"script_id":"1000","0":"1000","script_name":"gtk-vim-syntax","1":"gtk-vim-syntax","script_type":"syntax","2":"syntax","summary":"Syntax highlighting for GLib, Gtk+, Xlib, Gimp, Gstreamer, and more.","3":"Syntax highlighting for GLib, Gtk+, Xlib, Gimp, Gstreamer, and more.","description":"A collection of C extension syntax files for xlib, glib (gobject, gio), gdk-pixbuf, gtk2 (gdk2), gtk3 (gdk3), atk, at-spi, pango, cairo, clutter, gimp, gstreamer, dbus-glib, json-glib, libglade, gtksourceview, gnome-desktop, libgsf, libnotify, librsvg, libunique, libwnck, gtkglext, vte, poppler, evince.\r\n\r\nThe xlib one was originally created by Hwanjin Choe (vimscript #570), the others were generated from gtk-doc declaration lists and support enabling\/disabling of highlighting of deprecated declarations.","4":"A collection of C extension syntax files for xlib, glib (gobject, gio), gdk-pixbuf, gtk2 (gdk2), gtk3 (gdk3), atk, at-spi, pango, cairo, clutter, gimp, gstreamer, dbus-glib, json-glib, libglade, gtksourceview, gnome-desktop, libgsf, libnotify, librsvg, libunique, libwnck, gtkglext, vte, poppler, evince.\r\n\r\nThe xlib one was originally created by Hwanjin Choe (vimscript #570), the others were generated from gtk-doc declaration lists and support enabling\/disabling of highlighting of deprecated declarations.","install_details":"Include selected files in your ~\/.vim\/after\/syntax\/c.vim with :run glib.vim. See README in the tarball for details.","5":"Include selected files in your ~\/.vim\/after\/syntax\/c.vim with :run glib.vim. See README in the tarball for details.","first_name":"David","6":"David","last_name":"Necas","7":"Necas","releases":[{"0":"1000","vim_version":"6.0","1":"6.0","script_version":"20130716","2":"20130716","version_comment":"All syntax files were updated to recent version of the libraries and files for gusb, gudev and fftw3 were added. Deprecated symbols, broken by changes in gtk-doc,works again. FooPrivate types were filtered out. Support for Vim 5.7 was dropped, version 6.0 is now required. Sample c.vim.example was updated (thx to David King).","3":"All syntax files were updated to recent version of the libraries and files for gusb, gudev and fftw3 were added. Deprecated symbols, broken by changes in gtk-doc,works again. FooPrivate types were filtered out. Support for Vim 5.7 was dropped, version 6.0 is now required. Sample c.vim.example was updated (thx to David King).","package":"gtk-vim-syntax.tar.gz","4":"gtk-vim-syntax.tar.gz","src_id":"20534","5":"20534","creation_date":"1374008731","6":"1374008731"},{"0":"1000","vim_version":"5.7","1":"5.7","script_version":"20121015","2":"20121015","version_comment":"This is the first Gtk+3 version of gtk-vim-syntax.  A number of Gnome2-era syntax files was removed (libgnome, ORBit, libglade, liboil, ...) although a Gtk+2 syntax file is still kept as many non-Gnome developers may find it useful.  All GLib files were consolidated to glib.vim; standalone gobject.vim and gio.vim are gone.  Similarly, all Gtk+ files were consolidated to gtk2.vim or gtk3.vim (depending on the version); standalone gdk.vim is gone.  Therefore, it is likely you will need to update your vim configuration.","3":"This is the first Gtk+3 version of gtk-vim-syntax.  A number of Gnome2-era syntax files was removed (libgnome, ORBit, libglade, liboil, ...) although a Gtk+2 syntax file is still kept as many non-Gnome developers may find it useful.  All GLib files were consolidated to glib.vim; standalone gobject.vim and gio.vim are gone.  Similarly, all Gtk+ files were consolidated to gtk2.vim or gtk3.vim (depending on the version); standalone gdk.vim is gone.  Therefore, it is likely you will need to update your vim configuration.","package":"gtk-vim-syntax.tar.gz","4":"gtk-vim-syntax.tar.gz","src_id":"18814","5":"18814","creation_date":"1350332804","6":"1350332804"},{"0":"1000","vim_version":"5.7","1":"5.7","script_version":"20110314","2":"20110314","version_comment":"Syntax names of gobject-introspection and json-glib introduced in the previous release contained dashes which made them invalid vim identifiers.  They were renamed to gobjectintrospection and jsonglib.","3":"Syntax names of gobject-introspection and json-glib introduced in the previous release contained dashes which made them invalid vim identifiers.  They were renamed to gobjectintrospection and jsonglib.","package":"gtk-vim-syntax.tar.gz","4":"gtk-vim-syntax.tar.gz","src_id":"15217","5":"15217","creation_date":"1300118648","6":"1300118648"},{"0":"1000","vim_version":"5.7","1":"5.7","script_version":"20110214","2":"20110214","version_comment":"A GStreamer syntax file was added.  This is still a Gtk+ 2\/Gnome 2 version, probably the last.","3":"A GStreamer syntax file was added.  This is still a Gtk+ 2\/Gnome 2 version, probably the last.","package":"gtk-vim-syntax.tar.gz","4":"gtk-vim-syntax.tar.gz","src_id":"15022","5":"15022","creation_date":"1297844058","6":"1297844058"},{"0":"1000","vim_version":"5.7","1":"5.7","script_version":"20091024","2":"20091024","version_comment":"Keyword `if' that appeared in the previous version among GObject identifiers due to some gtk-doc misparsing was removed.","3":"Keyword `if' that appeared in the previous version among GObject identifiers due to some gtk-doc misparsing was removed.","package":"gtk-vim-syntax.tar.gz","4":"gtk-vim-syntax.tar.gz","src_id":"11573","5":"11573","creation_date":"1256368681","6":"1256368681"},{"0":"1000","vim_version":"5.7","1":"5.7","script_version":"20091021","2":"20091021","version_comment":"Syntaxes were updated to versions corresponding to GNOME 2.28.  Two new files were added: for libsoup and libunique.","3":"Syntaxes were updated to versions corresponding to GNOME 2.28.  Two new files were added: for libsoup and libunique.","package":"gtk-vim-syntax.tar.gz","4":"gtk-vim-syntax.tar.gz","src_id":"11555","5":"11555","creation_date":"1256123026","6":"1256123026"},{"0":"1000","vim_version":"5.7","1":"5.7","script_version":"20090402","2":"20090402","version_comment":"All syntax files were updated to Gnome 2.26 versions; clutter and goocanvas syntax files were added.","3":"All syntax files were updated to Gnome 2.26 versions; clutter and goocanvas syntax files were added.","package":"gtk-vim-syntax.tar.gz","4":"gtk-vim-syntax.tar.gz","src_id":"10338","5":"10338","creation_date":"1238681288","6":"1238681288"},{"0":"1000","vim_version":"5.7","1":"5.7","script_version":"20090105","2":"20090105","version_comment":"GObject syntax file missing in the last release was re-added.","3":"GObject syntax file missing in the last release was re-added.","package":"gtk-vim-syntax.tar.gz","4":"gtk-vim-syntax.tar.gz","src_id":"9761","5":"9761","creation_date":"1231148589","6":"1231148589"},{"0":"1000","vim_version":"5.7","1":"5.7","script_version":"20090102","2":"20090102","version_comment":"Everything was updated to Gnome 2.24.  GIO and evince syntax files were added.","3":"Everything was updated to Gnome 2.24.  GIO and evince syntax files were added.","package":"gtk-vim-syntax.tar.gz","4":"gtk-vim-syntax.tar.gz","src_id":"9747","5":"9747","creation_date":"1230910988","6":"1230910988"},{"0":"1000","vim_version":"5.7","1":"5.7","script_version":"20070925","2":"20070925","version_comment":"All files were updated to Gnome 2.20 versions of the respective libraries. (GLib to 2.14, Gtk+ to 2.12, ...). Syntax file for linc was dropped, files for at-spi, gail, dbus-glib, gtksourceview, gnome-desktop, gnome-vfs, liboil and poppler were added.","3":"All files were updated to Gnome 2.20 versions of the respective libraries. (GLib to 2.14, Gtk+ to 2.12, ...). Syntax file for linc was dropped, files for at-spi, gail, dbus-glib, gtksourceview, gnome-desktop, gnome-vfs, liboil and poppler were added.","package":"gtk-vim-syntax.tar.gz","4":"gtk-vim-syntax.tar.gz","src_id":"7712","5":"7712","creation_date":"1190718735","6":"1190718735"},{"0":"1000","vim_version":"5.7","1":"5.7","script_version":"20061121","2":"20061121","version_comment":"Variables (e.g. gtk_major_version or glib_mem_profiler_table) were added, they are highlighted as Identifiers by default (suggestions how to differentiate them from functions are welcome).\r\n\r\nThe synax files were cleaned up bit: hi-links are created only for symbol classes actually present in the file, deprecation stuff is completely excluded from files that contain no deprecated symbols.","3":"Variables (e.g. gtk_major_version or glib_mem_profiler_table) were added, they are highlighted as Identifiers by default (suggestions how to differentiate them from functions are welcome).\r\n\r\nThe synax files were cleaned up bit: hi-links are created only for symbol classes actually present in the file, deprecation stuff is completely excluded from files that contain no deprecated symbols.","package":"gtk-vim-syntax.tar.gz","4":"gtk-vim-syntax.tar.gz","src_id":"6457","5":"6457","creation_date":"1164101736","6":"1164101736"},{"0":"1000","vim_version":"5.7","1":"5.7","script_version":"20061120","2":"20061120","version_comment":"Syntax highlighting files for librsvg, libwnck, libgsf and libnotify were added.","3":"Syntax highlighting files for librsvg, libwnck, libgsf and libnotify were added.","package":"gtk-vim-syntax.tar.gz","4":"gtk-vim-syntax.tar.gz","src_id":"6449","5":"6449","creation_date":"1164012877","6":"1164012877"},{"0":"1000","vim_version":"5.7","1":"5.7","script_version":"20061119","2":"20061119","version_comment":"atk syntax was updated to 1.12, cairo to 1.2, gdk, gdk-pixbuf and gtk+ to 2.10, glib and gobject to 2.12, libglade to 2.6, gnome libs to 2.16, pango to 1.14 and vte to 0.14.","3":"atk syntax was updated to 1.12, cairo to 1.2, gdk, gdk-pixbuf and gtk+ to 2.10, glib and gobject to 2.12, libglade to 2.6, gnome libs to 2.16, pango to 1.14 and vte to 0.14.","package":"gtk-vim-syntax.tar.gz","4":"gtk-vim-syntax.tar.gz","src_id":"6440","5":"6440","creation_date":"1163932267","6":"1163932267"},{"0":"1000","vim_version":"5.7","1":"5.7","script_version":"20060423","2":"20060423","version_comment":"Syntax files for Gnome libs were updated to 2.14.","3":"Syntax files for Gnome libs were updated to 2.14.","package":"gtk-vim-syntax.tar.gz","4":"gtk-vim-syntax.tar.gz","src_id":"5589","5":"5589","creation_date":"1145798640","6":"1145798640"},{"0":"1000","vim_version":"5.7","1":"5.7","script_version":"2006-03-20","2":"2006-03-20","version_comment":"Pango syntax file was updated to 1.12.","3":"Pango syntax file was updated to 1.12.","package":"gtk-vim-syntax.tar.gz","4":"gtk-vim-syntax.tar.gz","src_id":"5469","5":"5469","creation_date":"1142852555","6":"1142852555"},{"0":"1000","vim_version":"5.7","1":"5.7","script_version":"2006-03-19","2":"2006-03-19","version_comment":"GLib syntax file was updated to 2.10.","3":"GLib syntax file was updated to 2.10.","package":"gtk-vim-syntax.tar.gz","4":"gtk-vim-syntax.tar.gz","src_id":"5459","5":"5459","creation_date":"1142777340","6":"1142777340"},{"0":"1000","vim_version":"5.7","1":"5.7","script_version":"2005-09-06","2":"2005-09-06","version_comment":"Deprecated symbol handling was improved.  Syntax items for deprecated symbols have their own groups (fooDeprecatedFunction instead of fooFunction) so it's possible to link them to something else than normal symbols.  By default, they are not highlighted at all (like before).  If you set\r\n\r\n:let foo_enable_deprecated = 1\r\n\r\nthey are linked to the same highligt groups as normal symbols.  If you set\r\n\r\n:let foo_deprecated_errors = 1\r\n\r\nthey are linked to Error.\r\n\r\nGLib, GObject, Gdk, Gkd-Pixbuf, Gtk+ syntax files were updated to 2.8. Atk and Pango to 1.10. Cairo was newly added.  As a side effect, missing highlighting of GdkPixmap, GdkWindow, and GdkBitmap was fixed.","3":"Deprecated symbol handling was improved.  Syntax items for deprecated symbols have their own groups (fooDeprecatedFunction instead of fooFunction) so it's possible to link them to something else than normal symbols.  By default, they are not highlighted at all (like before).  If you set\r\n\r\n:let foo_enable_deprecated = 1\r\n\r\nthey are linked to the same highligt groups as normal symbols.  If you set\r\n\r\n:let foo_deprecated_errors = 1\r\n\r\nthey are linked to Error.\r\n\r\nGLib, GObject, Gdk, Gkd-Pixbuf, Gtk+ syntax files were updated to 2.8. Atk and Pango to 1.10. Cairo was newly added.  As a side effect, missing highlighting of GdkPixmap, GdkWindow, and GdkBitmap was fixed.","package":"gtk-vim-syntax.tar.gz","4":"gtk-vim-syntax.tar.gz","src_id":"4556","5":"4556","creation_date":"1126012805","6":"1126012805"},{"0":"1000","vim_version":"5.7","1":"5.7","script_version":"20050308","2":"20050308","version_comment":"Functions taking filename arguments that were incorrectly highlighted as constants since GLib and Gtk+ 2.6 are highlighted as functions again.","3":"Functions taking filename arguments that were incorrectly highlighted as constants since GLib and Gtk+ 2.6 are highlighted as functions again.","package":"gtk-vim-syntax.tar.gz","4":"gtk-vim-syntax.tar.gz","src_id":"3977","5":"3977","creation_date":"1110251907","6":"1110251907"},{"0":"1000","vim_version":"5.7","1":"5.7","script_version":"20050225","2":"20050225","version_comment":"Bug fixed: union types were not highlighted.","3":"Bug fixed: union types were not highlighted.","package":"gtk-vim-syntax.tar.gz","4":"gtk-vim-syntax.tar.gz","src_id":"3910","5":"3910","creation_date":"1109331011","6":"1109331011"},{"0":"1000","vim_version":"5.7","1":"5.7","script_version":"20050123","2":"20050123","version_comment":"Libglade syntax highlighting was added.","3":"Libglade syntax highlighting was added.","package":"gtk-vim-syntax.tar.gz","4":"gtk-vim-syntax.tar.gz","src_id":"3790","5":"3790","creation_date":"1106482374","6":"1106482374"},{"0":"1000","vim_version":"5.7","1":"5.7","script_version":"20041222","2":"20041222","version_comment":"Gtk+ and GLib syntax files were updated to 2.6, Pango and Atk to 1.8, Gimp to 2.2, Gnome to 2.8.","3":"Gtk+ and GLib syntax files were updated to 2.6, Pango and Atk to 1.8, Gimp to 2.2, Gnome to 2.8.","package":"gtk-vim-syntax.tar.gz","4":"gtk-vim-syntax.tar.gz","src_id":"3722","5":"3722","creation_date":"1103682583","6":"1103682583"},{"0":"1000","vim_version":"6.0","1":"6.0","script_version":"20040815","2":"20040815","version_comment":"Syntax highlighting file for GtkGLExt was added.","3":"Syntax highlighting file for GtkGLExt was added.","package":"gtk-vim-syntax.tar.gz","4":"gtk-vim-syntax.tar.gz","src_id":"3335","5":"3335","creation_date":"1092543319","6":"1092543319"},{"0":"1000","vim_version":"5.7","1":"5.7","script_version":"20040813","2":"20040813","version_comment":"Fixed bug: many last enum values were not highlighted.","3":"Fixed bug: many last enum values were not highlighted.","package":"gtk-vim-syntax.tar.gz","4":"gtk-vim-syntax.tar.gz","src_id":"3320","5":"3320","creation_date":"1092365910","6":"1092365910"},{"0":"1000","vim_version":"5.7","1":"5.7","script_version":"20040611","2":"20040611","version_comment":"Quite a few missing enums were fixed.  Parameterless macros like\r\n\r\n#define gimp_get_data gimp_procedural_db_get_data\r\n\r\nare highlighted as Macro (not Constant as the previous version did) -- if the generator can figure out gimp_procedural_db_get_data is a function.","3":"Quite a few missing enums were fixed.  Parameterless macros like\r\n\r\n#define gimp_get_data gimp_procedural_db_get_data\r\n\r\nare highlighted as Macro (not Constant as the previous version did) -- if the generator can figure out gimp_procedural_db_get_data is a function.","package":"gtk-vim-syntax.tar.gz","4":"gtk-vim-syntax.tar.gz","src_id":"3111","5":"3111","creation_date":"1086923512","6":"1086923512"},{"0":"1000","vim_version":"5.7","1":"5.7","script_version":"20040605","2":"20040605","version_comment":"Parameterless macros were separated to somethingDefine syntax groups, highlighted as Constant by default.  This fixes highlighting of things like NULL or FALSE as macros and is more compatible with Hwanjin Choe's original files.","3":"Parameterless macros were separated to somethingDefine syntax groups, highlighted as Constant by default.  This fixes highlighting of things like NULL or FALSE as macros and is more compatible with Hwanjin Choe's original files.","package":"gtk-vim-syntax.tar.gz","4":"gtk-vim-syntax.tar.gz","src_id":"3098","5":"3098","creation_date":"1086423938","6":"1086423938"},{"0":"1000","vim_version":"5.7","1":"5.7","script_version":"20040531","2":"20040531","version_comment":"Initial upload","3":"Initial upload","package":"gtk-vim-syntax.tar.gz","4":"gtk-vim-syntax.tar.gz","src_id":"3074","5":"3074","creation_date":"1086002012","6":"1086002012"}]},"999":{"script_id":"999","0":"999","script_name":"TransferChinese.vim","1":"TransferChinese.vim","script_type":"utility","2":"utility","summary":"Transfer Chinese to Chinese","3":"Transfer Chinese to Chinese","description":"To mimic what gu and gU do for ascii,\r\nI defined two new maps, gS and gT, to transfer between\r\nthe simplified Chinese and the traditional Chinese.\r\n\r\nFeatures:\r\n\r\n(a) \"quick and dirty\" way to transfer Chinese to Chinese\r\n(b) 20% of efforts for solving 80% of problems\r\n(c) 2172 Chinese pairs are used for one-to-one map\r\n(d) cursor position is kept after gS or gT\r\n(e) [range] for visual mode is supported","4":"To mimic what gu and gU do for ascii,\r\nI defined two new maps, gS and gT, to transfer between\r\nthe simplified Chinese and the traditional Chinese.\r\n\r\nFeatures:\r\n\r\n(a) \"quick and dirty\" way to transfer Chinese to Chinese\r\n(b) 20% of efforts for solving 80% of problems\r\n(c) 2172 Chinese pairs are used for one-to-one map\r\n(d) cursor position is kept after gS or gT\r\n(e) [range] for visual mode is supported","install_details":"      \r\nThis file should reside in the plugins directory,\r\nto be automatically sourced. If not, you can manually\r\nsource this file using ':source TransferChinese.vim'.\r\n\r\nUsage:\r\n\r\n[range]gS  (transfer from Traditional to Simplified)\r\n[range]gT  (transfer from Simplified to Traditional)\r\n\r\n[range]:ChineseToggle<CR>  (toggle between Chinese, for fun)\r\n\r\n\r\n【安民告示】\r\n\r\nThis tool is obsolete.\r\nThe same feature can be found in VimIM with less memory consumption.\r\n\r\n(1) download:\r\n    (1.1) http:\/\/vim.sourceforge.net\/scripts\/script.php?script_id=2506\r\n    (1.2) http:\/\/vimim.googlecode.com\/svn\/trunk\/plugin\/vimim.vim\r\n(2) installation:\r\n    (2.1) 插上程式文件 vimim.vim\r\n    (2.2) 插上字库文件 vimim.cjk.txt \r\n(3) usage:\r\n    (3.1) 〖简体变繁体〗 :VimIM \r\n    (3.2) 〖繁体变简体〗 :VimIM ","5":"      \r\nThis file should reside in the plugins directory,\r\nto be automatically sourced. If not, you can manually\r\nsource this file using ':source TransferChinese.vim'.\r\n\r\nUsage:\r\n\r\n[range]gS  (transfer from Traditional to Simplified)\r\n[range]gT  (transfer from Simplified to Traditional)\r\n\r\n[range]:ChineseToggle<CR>  (toggle between Chinese, for fun)\r\n\r\n\r\n【安民告示】\r\n\r\nThis tool is obsolete.\r\nThe same feature can be found in VimIM with less memory consumption.\r\n\r\n(1) download:\r\n    (1.1) http:\/\/vim.sourceforge.net\/scripts\/script.php?script_id=2506\r\n    (1.2) http:\/\/vimim.googlecode.com\/svn\/trunk\/plugin\/vimim.vim\r\n(2) installation:\r\n    (2.1) 插上程式文件 vimim.vim\r\n    (2.2) 插上字库文件 vimim.cjk.txt \r\n(3) usage:\r\n    (3.1) 〖简体变繁体〗 :VimIM \r\n    (3.2) 〖繁体变简体〗 :VimIM ","first_name":"Vim","6":"Vim","last_name":"IM","7":"IM","releases":[{"0":"999","vim_version":"6.0","1":"6.0","script_version":"0.9.0","2":"0.9.0","version_comment":"Initial upload","3":"Initial upload","package":"TransferChinese.zip","4":"TransferChinese.zip","src_id":"3073","5":"3073","creation_date":"1085934758","6":"1085934758"}]},"998":{"script_id":"998","0":"998","script_name":"menu_pt_br.vim(fix)","1":"menu_pt_br.vim(fix)","script_type":"utility","2":"utility","summary":"Fix of menu translation","3":"Fix of menu translation","description":"there was a line break at the Toggle \\ Insert \\ Mode translation that was causing a startup message error. Just joined the line.","4":"there was a line break at the Toggle \\ Insert \\ Mode translation that was causing a startup message error. Just joined the line.","install_details":"Just copy over the existing file.","5":"Just copy over the existing file.","first_name":"leonardo","6":"leonardo","last_name":"postacchini","7":"postacchini","releases":[{"0":"998","vim_version":"6.0","1":"6.0","script_version":"6.0","2":"6.0","version_comment":"Initial upload","3":"Initial upload","package":"menu_pt_br.vim","4":"menu_pt_br.vim","src_id":"3061","5":"3061","creation_date":"1085513512","6":"1085513512"}]},"997":{"script_id":"997","0":"997","script_name":"Window Sizes","1":"Window Sizes","script_type":"utility","2":"utility","summary":"Allows multiple windows to have specific vertical sizes","3":"Allows multiple windows to have specific vertical sizes","description":"History:\r\n\r\n1.0:  Initial version\r\n\r\n1.1:  Added mapping <leader>tog to toggle the behavior of observing fixed\r\nwindow heights.  If disabled, vertically split windows can be used without a\r\nproblem.  Added two functions, WindowSizesEnabled and WindowSizesMaxEnabled,\r\nwhich return whether fixed sizes are observed and whether window maxing is\r\nenabled, respectively.\r\n\r\nPlugin to keep the vertical sizes of windows within specifications.  For\r\nexample, if you're using the Decho.vim plugin, you could force the DBG\r\nwindow to always be 10 lines high and for all other windows to automatically\r\nmaximize upon entry.  Or, you could specify explicit sizes for two windows\r\nand let all the remaining space be shared equally among the other windows.\r\n\r\nThis is a bit different from using equalalways and winheight=999 because it\r\nwill always honor the vertical height settings of individual windows, using\r\nthe maximizing or equalization only on those windows that don't have\r\nanything set explicitly.\r\n\r\nCaveat (and it's a big one):  No support for vertical splits.  If you have a\r\nvertical split, the behavior is undefined (well, it's not undefined, but\r\nit's ugly).\r\n\r\nUsage (default mappings):\r\n\r\n<leader>max:  Toggle whether windows without an explicit fixed size will\r\nautomatically maximize upon entry or whether all un-fixed-size windows will\r\nsimply share the vertical space left over once the fixed windows have taken\r\ntheir share of the space.\r\n\r\n<leader>fix:  If the current window has a preferred fixed vertical size,\r\nremove it, allowing this window to expand and contract according to the\r\ng:WindowSizes_windowMax setting.\r\n\r\n<leader>tog:  Toggle the fixed-window-size behavior; the <leader>max\r\nbehavior is controlled separately.  If fixed-window-sizes are not being\r\nobserved, then all windows are maximized blindly upon entering (without\r\nregard to their preferred height) if maximizing is enabled.\r\n\r\n<s-up>:  Increases the current windows's size by the value of the\r\nWindowSizes_increment variables (see below); using this mapping results in\r\nfixing the window height.\r\n\r\n<s-down>:  Decreases the current windows's size by the value of the\r\nWindowSizes_increment variables (see below); using this mapping results in\r\nfixing the window height.\r\n\r\nVariables (configuration):\r\ng:WindowSizes_windowMax:  If 1, then windows are maximized (the <leader>max\r\nmapping merely toggles this value between 1 and 0).\r\n\r\nb:preferredWindowSize:  If defined, the fixed vertical size of the current\r\nwindow -- the window will be this size vertically (tweaked by the\r\n<leader>fix, <s-up> and <s-down> mappings).  If not defined, a prompt is\r\ndisplayed for the user to specify a fixed vertical height for the current\r\nwindow where the current height is used as the default value (hit <ESC> to\r\nget out of it).\r\n\r\ng:WindowSizes_increment:  If defined, this is the increment by which to\r\nincrease or decrease the current window's size if using the <s-up> or\r\n<s-down> mappings.  If not defined, 5 is used.\r\n\r\nb:WindowSizes_increment:  If defined in a given window, this is the\r\nincrement by which to increase or decrease the current window's size when\r\nusing the <s-up> or <s-down> mappings.  If not defined, the global version\r\n(g:WindowSizes_increment) is used (if even THAT's not defined, 5 is used).\r\n\r\nFunctions (for use in the statusline, for example):\r\n\r\nWindowSizesEnabled:  Returns 1 if the preferred heights of windows is\r\ncurrently being observed (toggle with the <leader>tog mapping).\r\n\r\nWindowSizesMaxEnabled:  Returns 1 if the current window is going to get as\r\nmuch vertical real estate as possible (taking into consideration the\r\nWindowSizesEnabled setting and the presence of other windows).\r\n\r\nTips:\r\n\r\n- Always have at least one window without a specified size so it can take\r\n  over the remaining vertical space.\r\n\r\n- Always make sure that the total size of the fixed windows is less than the\r\n  actual number of lines visible on-screen!  (The behavior otherwise is\r\n  undefined -- that is, not tested by me.)\r\n\r\n- To restore a window to not having a preferred size, unlet\r\n  b:preferredWindowSize (just use the <leader>fix mapping).\r\n\r\nTODO:\r\n\r\n- Observe the 'laststatus' value.\r\n\r\n- Figure out how to change all the global variables to script or some such\r\n  so they don't pollute the global variable pool.\r\n","4":"History:\r\n\r\n1.0:  Initial version\r\n\r\n1.1:  Added mapping <leader>tog to toggle the behavior of observing fixed\r\nwindow heights.  If disabled, vertically split windows can be used without a\r\nproblem.  Added two functions, WindowSizesEnabled and WindowSizesMaxEnabled,\r\nwhich return whether fixed sizes are observed and whether window maxing is\r\nenabled, respectively.\r\n\r\nPlugin to keep the vertical sizes of windows within specifications.  For\r\nexample, if you're using the Decho.vim plugin, you could force the DBG\r\nwindow to always be 10 lines high and for all other windows to automatically\r\nmaximize upon entry.  Or, you could specify explicit sizes for two windows\r\nand let all the remaining space be shared equally among the other windows.\r\n\r\nThis is a bit different from using equalalways and winheight=999 because it\r\nwill always honor the vertical height settings of individual windows, using\r\nthe maximizing or equalization only on those windows that don't have\r\nanything set explicitly.\r\n\r\nCaveat (and it's a big one):  No support for vertical splits.  If you have a\r\nvertical split, the behavior is undefined (well, it's not undefined, but\r\nit's ugly).\r\n\r\nUsage (default mappings):\r\n\r\n<leader>max:  Toggle whether windows without an explicit fixed size will\r\nautomatically maximize upon entry or whether all un-fixed-size windows will\r\nsimply share the vertical space left over once the fixed windows have taken\r\ntheir share of the space.\r\n\r\n<leader>fix:  If the current window has a preferred fixed vertical size,\r\nremove it, allowing this window to expand and contract according to the\r\ng:WindowSizes_windowMax setting.\r\n\r\n<leader>tog:  Toggle the fixed-window-size behavior; the <leader>max\r\nbehavior is controlled separately.  If fixed-window-sizes are not being\r\nobserved, then all windows are maximized blindly upon entering (without\r\nregard to their preferred height) if maximizing is enabled.\r\n\r\n<s-up>:  Increases the current windows's size by the value of the\r\nWindowSizes_increment variables (see below); using this mapping results in\r\nfixing the window height.\r\n\r\n<s-down>:  Decreases the current windows's size by the value of the\r\nWindowSizes_increment variables (see below); using this mapping results in\r\nfixing the window height.\r\n\r\nVariables (configuration):\r\ng:WindowSizes_windowMax:  If 1, then windows are maximized (the <leader>max\r\nmapping merely toggles this value between 1 and 0).\r\n\r\nb:preferredWindowSize:  If defined, the fixed vertical size of the current\r\nwindow -- the window will be this size vertically (tweaked by the\r\n<leader>fix, <s-up> and <s-down> mappings).  If not defined, a prompt is\r\ndisplayed for the user to specify a fixed vertical height for the current\r\nwindow where the current height is used as the default value (hit <ESC> to\r\nget out of it).\r\n\r\ng:WindowSizes_increment:  If defined, this is the increment by which to\r\nincrease or decrease the current window's size if using the <s-up> or\r\n<s-down> mappings.  If not defined, 5 is used.\r\n\r\nb:WindowSizes_increment:  If defined in a given window, this is the\r\nincrement by which to increase or decrease the current window's size when\r\nusing the <s-up> or <s-down> mappings.  If not defined, the global version\r\n(g:WindowSizes_increment) is used (if even THAT's not defined, 5 is used).\r\n\r\nFunctions (for use in the statusline, for example):\r\n\r\nWindowSizesEnabled:  Returns 1 if the preferred heights of windows is\r\ncurrently being observed (toggle with the <leader>tog mapping).\r\n\r\nWindowSizesMaxEnabled:  Returns 1 if the current window is going to get as\r\nmuch vertical real estate as possible (taking into consideration the\r\nWindowSizesEnabled setting and the presence of other windows).\r\n\r\nTips:\r\n\r\n- Always have at least one window without a specified size so it can take\r\n  over the remaining vertical space.\r\n\r\n- Always make sure that the total size of the fixed windows is less than the\r\n  actual number of lines visible on-screen!  (The behavior otherwise is\r\n  undefined -- that is, not tested by me.)\r\n\r\n- To restore a window to not having a preferred size, unlet\r\n  b:preferredWindowSize (just use the <leader>fix mapping).\r\n\r\nTODO:\r\n\r\n- Observe the 'laststatus' value.\r\n\r\n- Figure out how to change all the global variables to script or some such\r\n  so they don't pollute the global variable pool.\r\n","install_details":"Pop into your plugin directory; see the variables section for potential configuration (though none is explicitly required).","5":"Pop into your plugin directory; see the variables section for potential configuration (though none is explicitly required).","first_name":"Salman","6":"Salman","last_name":"Halim","7":"Halim","releases":[{"0":"997","vim_version":"6.0","1":"6.0","script_version":"1.2","2":"1.2","version_comment":"Added the ability to toggle the behaviour on or off.","3":"Added the ability to toggle the behaviour on or off.","package":"WindowSizes.vim","4":"WindowSizes.vim","src_id":"5301","5":"5301","creation_date":"1140613156","6":"1140613156"},{"0":"997","vim_version":"6.0","1":"6.0","script_version":"1.1","2":"1.1","version_comment":"Added ability to disable the behavior where preferred heights are observed -- useful with vertically split windows (not perfect, but at least vertical splits are usable now).  Added two functions to return whether the main sizing behavior as well as the window maxing are enabled.","3":"Added ability to disable the behavior where preferred heights are observed -- useful with vertically split windows (not perfect, but at least vertical splits are usable now).  Added two functions to return whether the main sizing behavior as well as the window maxing are enabled.","package":"WindowSizes.vim","4":"WindowSizes.vim","src_id":"3062","5":"3062","creation_date":"1085562763","6":"1085562763"},{"0":"997","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"WindowSizes.vim","4":"WindowSizes.vim","src_id":"3060","5":"3060","creation_date":"1085483845","6":"1085483845"}]},"996":{"script_id":"996","0":"996","script_name":"tbf-vimfiles","1":"tbf-vimfiles","script_type":"syntax","2":"syntax","summary":"Collection of syntax files for C, C#, Java, NSIS and Doxygen","3":"Collection of syntax files for C, C#, Java, NSIS and Doxygen","description":"A random collection of vim files I use. Containing syntax files for C, C# and Java featuring syntax based folding support. Also contains highlighting for doxygen comments in C and C#. And contains a simple syntax highligher for NSIS.\r\n\r\nUsage for folding in C, C++, C# and Java: First of all { code blocks; }  are recognized. Should cover most language constructs, like classes, functions, branches, loops. Additonally explicitly defined regions are supported. In C# you use pairs for \"#region\/#endregion\" pragmas for that purpose. In C (and C++) explicit regions are marked by \"\/* region *\/\" and \"\/* endregion *\/\". The region markers for Java are \"\/\/ region\" and \"\/\/endregion\".\r\n\r\n","4":"A random collection of vim files I use. Containing syntax files for C, C# and Java featuring syntax based folding support. Also contains highlighting for doxygen comments in C and C#. And contains a simple syntax highligher for NSIS.\r\n\r\nUsage for folding in C, C++, C# and Java: First of all { code blocks; }  are recognized. Should cover most language constructs, like classes, functions, branches, loops. Additonally explicitly defined regions are supported. In C# you use pairs for \"#region\/#endregion\" pragmas for that purpose. In C (and C++) explicit regions are marked by \"\/* region *\/\" and \"\/* endregion *\/\". The region markers for Java are \"\/\/ region\" and \"\/\/endregion\".\r\n\r\n","install_details":"Just place the files in ~\/.vim or $VIMRUNTIME, as suggested by the tarballs directory structure.","5":"Just place the files in ~\/.vim or $VIMRUNTIME, as suggested by the tarballs directory structure.","first_name":"Mathias","6":"Mathias","last_name":"Hasselmann","7":"Hasselmann","releases":[{"0":"996","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"tbf-vimfiles.tar.gz","4":"tbf-vimfiles.tar.gz","src_id":"3053","5":"3053","creation_date":"1085295142","6":"1085295142"}]},"995":{"script_id":"995","0":"995","script_name":"nant compiler script","1":"nant compiler script","script_type":"utility","2":"utility","summary":"NAnt support for the make command","3":"NAnt support for the make command","description":"This tiny compiler script teaches vim's :make command to utilize nant (http:\/\/nant.sf.net). Trival. Error strings are not that perfect yet. But works for me.","4":"This tiny compiler script teaches vim's :make command to utilize nant (http:\/\/nant.sf.net). Trival. Error strings are not that perfect yet. But works for me.","install_details":"Just copy this file to ~\/.vim\/compiler or $VIMRUNTIME\/compiler - as you prefer.","5":"Just copy this file to ~\/.vim\/compiler or $VIMRUNTIME\/compiler - as you prefer.","first_name":"Mathias","6":"Mathias","last_name":"Hasselmann","7":"Hasselmann","releases":[{"0":"995","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"nant.vim","4":"nant.vim","src_id":"3052","5":"3052","creation_date":"1085294451","6":"1085294451"}]},"994":{"script_id":"994","0":"994","script_name":"FiletypeRegisters","1":"FiletypeRegisters","script_type":"utility","2":"utility","summary":"Localize register contents based on filetype","3":"Localize register contents based on filetype","description":"Plugin to keep certain registers (specified by the global variable\r\ng:localRegisters) specific to individual filetypes.  For example, if editing\r\na Java file in one window and a Vim script in another, one may want to\r\nsearch for a variable name in the Java window that has no bearing in the Vim\r\nwindow; however, ordinary functionality would clobber the Vim window search\r\nregister value, requiring the use of search history if the original\r\nexpression was complicated.\r\n\r\nThis relies on my getVar.vim (vimscript #353).\r\n\r\nMappings (default):\r\n\r\n<Leader>im -- used to import one register from another filetype\r\n\r\nCommands:\r\n\r\nCopyregister -- used to import one register from another filetype (the\r\nmapping just executes this command)\r\n\r\nCustomizations:\r\n\r\nBy default, no registers are localized (so no behavior changes should be\r\nnoticed).  To localize registers, place an assignment to g:localRegisters\r\ninside your _vimrc:\r\n\r\nlet g:localRegisters=\"abcm\/\"\r\n\r\nThe above allows registers a, b, c, m and the search register to be\r\nlocalized based on filetype (all Vim scripts get one copy, all Java files\r\nanother etc.).\r\n\r\nTo change the default mapping for importing register contents from another\r\nfiletype, create a normal mode mapping to <Plug>CopyRegister in your _vimrc.\r\n\r\nTODO:\r\n\r\n- Keith Roberts:  Allow certain filetypes to retain global settings through\r\n  the use of an option (set through an ftplugin, for example) -- these would\r\n  inherit the settings of the last window, in all likelihood, rather than\r\n  setting their own.\r\n\r\n- Maybe allow certain filetypes to ALWAYS keep in synch with others?\r\n","4":"Plugin to keep certain registers (specified by the global variable\r\ng:localRegisters) specific to individual filetypes.  For example, if editing\r\na Java file in one window and a Vim script in another, one may want to\r\nsearch for a variable name in the Java window that has no bearing in the Vim\r\nwindow; however, ordinary functionality would clobber the Vim window search\r\nregister value, requiring the use of search history if the original\r\nexpression was complicated.\r\n\r\nThis relies on my getVar.vim (vimscript #353).\r\n\r\nMappings (default):\r\n\r\n<Leader>im -- used to import one register from another filetype\r\n\r\nCommands:\r\n\r\nCopyregister -- used to import one register from another filetype (the\r\nmapping just executes this command)\r\n\r\nCustomizations:\r\n\r\nBy default, no registers are localized (so no behavior changes should be\r\nnoticed).  To localize registers, place an assignment to g:localRegisters\r\ninside your _vimrc:\r\n\r\nlet g:localRegisters=\"abcm\/\"\r\n\r\nThe above allows registers a, b, c, m and the search register to be\r\nlocalized based on filetype (all Vim scripts get one copy, all Java files\r\nanother etc.).\r\n\r\nTo change the default mapping for importing register contents from another\r\nfiletype, create a normal mode mapping to <Plug>CopyRegister in your _vimrc.\r\n\r\nTODO:\r\n\r\n- Keith Roberts:  Allow certain filetypes to retain global settings through\r\n  the use of an option (set through an ftplugin, for example) -- these would\r\n  inherit the settings of the last window, in all likelihood, rather than\r\n  setting their own.\r\n\r\n- Maybe allow certain filetypes to ALWAYS keep in synch with others?\r\n","install_details":"Pop it into the plugin directory and assign a value to g:localRegisters inside your _vimrc.","5":"Pop it into the plugin directory and assign a value to g:localRegisters inside your _vimrc.","first_name":"Salman","6":"Salman","last_name":"Halim","7":"Halim","releases":[{"0":"994","vim_version":"6.0","1":"6.0","script_version":"1.1","2":"1.1","version_comment":"1.1:  Added ability for different filetypes to have their own set of stored\r\nregisters.  Note that if a filetype has explicit registers set, it does NOT\r\nautomatically also get localized storage of the global ones -- they have to\r\nbe explicitly included in the local version (setup through the call to\r\nSetfiletyperegisters).  Suggested by Keith Roberts.\r\n","3":"1.1:  Added ability for different filetypes to have their own set of stored\r\nregisters.  Note that if a filetype has explicit registers set, it does NOT\r\nautomatically also get localized storage of the global ones -- they have to\r\nbe explicitly included in the local version (setup through the call to\r\nSetfiletyperegisters).  Suggested by Keith Roberts.\r\n","package":"FiletypeRegisters.vim","4":"FiletypeRegisters.vim","src_id":"3046","5":"3046","creation_date":"1085061663","6":"1085061663"},{"0":"994","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"FiletypeRegisters.vim","4":"FiletypeRegisters.vim","src_id":"3044","5":"3044","creation_date":"1085058515","6":"1085058515"}]},"993":{"script_id":"993","0":"993","script_name":"aspvbs.vim","1":"aspvbs.vim","script_type":"syntax","2":"syntax","summary":"ASP\/VBScript syntax highlighting","3":"ASP\/VBScript syntax highlighting","description":"This is the asbvbs.vim script found in the VIM distrobution. The latest version rests here. This syntax highlighting provides syntax for ASP\/VBScript files.","4":"This is the asbvbs.vim script found in the VIM distrobution. The latest version rests here. This syntax highlighting provides syntax for ASP\/VBScript files.","install_details":"Place aspvbs.vim in your syntax folder.","5":"Place aspvbs.vim in your syntax folder.","first_name":"Devin","6":"Devin","last_name":"Weaver","7":"Weaver","releases":[{"0":"993","vim_version":"6.0","1":"6.0","script_version":"1.17","2":"1.17","version_comment":"Fixed bug with Response.Write(\"foo\") syntax","3":"Fixed bug with Response.Write(\"foo\") syntax","package":"aspvbs.vim","4":"aspvbs.vim","src_id":"3042","5":"3042","creation_date":"1085005128","6":"1085005128"}]},"992":{"script_id":"992","0":"992","script_name":"rpl","1":"rpl","script_type":"indent","2":"indent","summary":"RPL\/2 indent file","3":"RPL\/2 indent file","description":"RPL\/2 indent file has to be used with RPL\/2 syntax file.","4":"RPL\/2 indent file has to be used with RPL\/2 syntax file.","install_details":"","5":"","first_name":"BERTRAND","6":"BERTRAND","last_name":"Jo\u00c3\u00abl","7":"Jo\u00c3\u00abl","releases":[{"0":"992","vim_version":"6.0","1":"6.0","script_version":"0.3","2":"0.3","version_comment":"Improve the last rpl.vim...","3":"Improve the last rpl.vim...","package":"rpl.vim","4":"rpl.vim","src_id":"7398","5":"7398","creation_date":"1185162676","6":"1185162676"},{"0":"992","vim_version":"6.0","1":"6.0","script_version":"0.2","2":"0.2","version_comment":"Initial upload","3":"Initial upload","package":"rpl.vim","4":"rpl.vim","src_id":"3039","5":"3039","creation_date":"1084971674","6":"1084971674"}]},"991":{"script_id":"991","0":"991","script_name":"rpl","1":"rpl","script_type":"ftplugin","2":"ftplugin","summary":"RPL\/2 ftplugin file","3":"RPL\/2 ftplugin file","description":"This file has to be used with the RPL\/2 syntax file.","4":"This file has to be used with the RPL\/2 syntax file.","install_details":"","5":"","first_name":"BERTRAND","6":"BERTRAND","last_name":"Jo\u00c3\u00abl","7":"Jo\u00c3\u00abl","releases":[{"0":"991","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Minor modifications...","3":"Minor modifications...","package":"rpl.vim","4":"rpl.vim","src_id":"3040","5":"3040","creation_date":"1084971859","6":"1084971859"}]},"990":{"script_id":"990","0":"990","script_name":"rpl","1":"rpl","script_type":"syntax","2":"syntax","summary":"Syntax description file for RPL\/2","3":"Syntax description file for RPL\/2","description":"Syntax file required to colorize RPL\/2 scientific language.","4":"Syntax file required to colorize RPL\/2 scientific language.","install_details":"","5":"","first_name":"BERTRAND","6":"BERTRAND","last_name":"Jo\u00c3\u00abl","7":"Jo\u00c3\u00abl","releases":[{"0":"990","vim_version":"6.0","1":"6.0","script_version":"0.15.26","2":"0.15.26","version_comment":"Fix some mistakes...","3":"Fix some mistakes...","package":"rpl.vim","4":"rpl.vim","src_id":"7397","5":"7397","creation_date":"1185162594","6":"1185162594"},{"0":"990","vim_version":"6.0","1":"6.0","script_version":"0.15.15","2":"0.15.15","version_comment":"Initial upload","3":"Initial upload","package":"rpl.vim","4":"rpl.vim","src_id":"3037","5":"3037","creation_date":"1084971425","6":"1084971425"}]},"989":{"script_id":"989","0":"989","script_name":"pdftotext","1":"pdftotext","script_type":"utility","2":"utility","summary":"Allow vim to read in a PDF file as plain text","3":"Allow vim to read in a PDF file as plain text","description":"This plugin will invoke the pdftotext utility to filter a PDF file that is being edited in vim and convert it to plain text in the current buffer. Requires that pdftotext is installed. It is included in the xpdf package (available from http:\/\/www.foolabs.com\/xpdf\/).","4":"This plugin will invoke the pdftotext utility to filter a PDF file that is being edited in vim and convert it to plain text in the current buffer. Requires that pdftotext is installed. It is included in the xpdf package (available from http:\/\/www.foolabs.com\/xpdf\/).","install_details":"Drop pdftotext.vim file into your .vim\/plugin\/ directory and try to edit a file ending in .pdf.","5":"Drop pdftotext.vim file into your .vim\/plugin\/ directory and try to edit a file ending in .pdf.","first_name":"Marc","6":"Marc","last_name":"Prud'hommeaux","7":"Prud'hommeaux","releases":[{"0":"989","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"pdftotext.vim","4":"pdftotext.vim","src_id":"3033","5":"3033","creation_date":"1084908845","6":"1084908845"}]},"988":{"script_id":"988","0":"988","script_name":"VHT","1":"VHT","script_type":"ftplugin","2":"ftplugin","summary":"Vim HTML Templates","3":"Vim HTML Templates","description":"VHT is Vim implementation of Macromedia Dreamweaver(tm) templates and libraries. Templates make possible to share the same document template across whole project, libraries allow for sharing the same snippet of code in many documents. This plugin makes possible to commit and update code from repositories and take care about file paths in links and image tags, always changing them to be relative to currently edited file.\r\n\r\nVHT doesn't provide immediate way to propagate changes across whole site. There is too many ways to maintain project in Vim. From session files, through project plugins from vim-online to simple file with list of files and opening it with \"vim `cat fileslist`\".\r\n\r\nAll commands work nice with :argdo, :windo, :bufdo set of commands.\r\nBut you have previously set b:vhtemplate for each file.\r\n","4":"VHT is Vim implementation of Macromedia Dreamweaver(tm) templates and libraries. Templates make possible to share the same document template across whole project, libraries allow for sharing the same snippet of code in many documents. This plugin makes possible to commit and update code from repositories and take care about file paths in links and image tags, always changing them to be relative to currently edited file.\r\n\r\nVHT doesn't provide immediate way to propagate changes across whole site. There is too many ways to maintain project in Vim. From session files, through project plugins from vim-online to simple file with list of files and opening it with \"vim `cat fileslist`\".\r\n\r\nAll commands work nice with :argdo, :windo, :bufdo set of commands.\r\nBut you have previously set b:vhtemplate for each file.\r\n","install_details":"Put vht.vim into your .vim\/ftplugin\/html\/ directory\r\n\r\nAbout installation of help file read :help add-local-help\r\n\r\nFor new version checking you can use GetLatestVimScripts script.\r\n","5":"Put vht.vim into your .vim\/ftplugin\/html\/ directory\r\n\r\nAbout installation of help file read :help add-local-help\r\n\r\nFor new version checking you can use GetLatestVimScripts script.\r\n","first_name":"Mikolaj","6":"Mikolaj","last_name":"Machowski","7":"Machowski","releases":[{"0":"988","vim_version":"6.0","1":"6.0","script_version":"1.4","2":"1.4","version_comment":"- fixed: don't require taglist for working\r\n- added: VHLstrip, VHTstrip commands for removing tags\r\n- added: VHLinsert, VHTinsert commands to insert library\/editable region\r\n  templates\r\n- added: adding .vhl extension to library names when\r\n\tuser forgot about it\r\n- added: silent unnecessary error messages during\r\n\tVHTcommit - everything is working, Vim is overcautious\r\n- added: GLVS AutoInstall compatible\r\n- remove unnecessary function calls - replace with variable\r\n\tassignment\r\n","3":"- fixed: don't require taglist for working\r\n- added: VHLstrip, VHTstrip commands for removing tags\r\n- added: VHLinsert, VHTinsert commands to insert library\/editable region\r\n  templates\r\n- added: adding .vhl extension to library names when\r\n\tuser forgot about it\r\n- added: silent unnecessary error messages during\r\n\tVHTcommit - everything is working, Vim is overcautious\r\n- added: GLVS AutoInstall compatible\r\n- remove unnecessary function calls - replace with variable\r\n\tassignment\r\n","package":"vht.zip","4":"vht.zip","src_id":"3384","5":"3384","creation_date":"1093447408","6":"1093447408"},{"0":"988","vim_version":"6.0","1":"6.0","script_version":"1.3","2":"1.3","version_comment":"Bugfix release (serious one):\r\n- Fixed support for window.open() JS\r\n- Fixed adding multiple definitions to Tlist_Ctags_Cmd when editing\r\n  multiple html files.\r\n","3":"Bugfix release (serious one):\r\n- Fixed support for window.open() JS\r\n- Fixed adding multiple definitions to Tlist_Ctags_Cmd when editing\r\n  multiple html files.\r\n","package":"vht.zip","4":"vht.zip","src_id":"3166","5":"3166","creation_date":"1087833077","6":"1087833077"},{"0":"988","vim_version":"6.0","1":"6.0","script_version":"1.2","2":"1.2","version_comment":"Major enhancements:\n- real support for Vim6.0 - get rid of cursor() function\n- support for window.open JS method\n- support for taglist.vim - it is possible to navigate in files using\n  not only standard ctags locations like anchors and js functions but\n  also editable regions and used libraries.\n- security check for format of regions' names, also available as new\n  command :VHTcheck\n","3":"Major enhancements:\n- real support for Vim6.0 - get rid of cursor() function\n- support for window.open JS method\n- support for taglist.vim - it is possible to navigate in files using\n  not only standard ctags locations like anchors and js functions but\n  also editable regions and used libraries.\n- security check for format of regions' names, also available as new\n  command :VHTcheck\n","package":"vht.zip","4":"vht.zip","src_id":"3104","5":"3104","creation_date":"1086606582","6":"1086606582"},{"0":"988","vim_version":"6.0","1":"6.0","script_version":"1.1","2":"1.1","version_comment":"Major enhancements:\n- support for links in url() - CSS and location - JS contexts\n- unification of functions for parsing links\n- before messing with links check if file exists: prevents unpredictable\n  Vim behaviour when file doesn't exists\n- two new commands:\n\tVHTshow - show currently assigned template and all available in\n\tproject\n\tVHLshow - show all available libraries in project\n","3":"Major enhancements:\n- support for links in url() - CSS and location - JS contexts\n- unification of functions for parsing links\n- before messing with links check if file exists: prevents unpredictable\n  Vim behaviour when file doesn't exists\n- two new commands:\n\tVHTshow - show currently assigned template and all available in\n\tproject\n\tVHLshow - show all available libraries in project\n","package":"vht.zip","4":"vht.zip","src_id":"3034","5":"3034","creation_date":"1084928452","6":"1084928452"},{"0":"988","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"vht.zip","4":"vht.zip","src_id":"3027","5":"3027","creation_date":"1084674510","6":"1084674510"}]},"987":{"script_id":"987","0":"987","script_name":"DoxygenToolkit.vim","1":"DoxygenToolkit.vim","script_type":"utility","2":"utility","summary":"Simplify Doxygen documentation in C, C++, Python.","3":"Simplify Doxygen documentation in C, C++, Python.","description":"Currently five purposes have been defined :\r\n\r\nGenerates a doxygen license comment.  The tag text is configurable.\r\n\r\nGenerates a doxygen author skeleton.  The tag text is configurable.\r\n\r\nGenerates a doxygen comment skeleton for a C, C++ or Python function or class,\r\nincluding @brief, @param (for each named argument), and @return.  The tag\r\ntext as well as a comment block header and footer are configurable.\r\n(Consequently, you can have \\brief, etc. if you wish, with little effort.)\r\n\r\nIgnore code fragment placed in a block defined by #ifdef ... #endif (C\/C++).  The\r\nblock name must be given to the function.  All of the corresponding blocks\r\nin all the file will be treated and placed in a new block DOX_SKIP_BLOCK (or\r\nany other name that you have configured).  Then you have to update\r\nPREDEFINED value in your doxygen configuration file with correct block name.\r\nYou also have to set ENABLE_PREPROCESSING to YES.\r\n\r\nGenerate a doxygen group (begining and ending). The tag text is\r\nconfigurable.\r\n\r\nUse:\r\n- Type of comments (C\/C++: \/\/\/ or \/** ... *\/, Python: ## and # ) :\r\n  In vim, default C++ comments are : \/** ... *\/. But if you prefer to use \/\/\/\r\n  Doxygen comments just add 'let g:DoxygenToolkit_commentType = \"C++\"'\r\n  (without quotes) in your .vimrc file\r\n\r\n- License :\r\n  In vim, place the cursor on the line that will follow doxygen license\r\n  comment.  Then, execute the command :DoxLic.  This will generate license\r\n  comment and leave the cursor on the line just after.\r\n\r\n- Author :\r\n  In vim, place the cursor on the line that will follow doxygen author\r\n  comment.  Then, execute the command :DoxAuthor.  This will generate the\r\n  skeleton and leave the cursor just after @author tag if no variable\r\n  define it, or just after the skeleton.\r\n\r\n- Function \/ class comment :\r\n  In vim, place the cursor on the line of the function header (or returned\r\n  value of the function) or the class.  Then execute the command :Dox.  This\r\n  will generate the skeleton and leave the cursor after the @brief tag.\r\n\r\n- Ignore code fragment (C\/C++ only) :\r\n  In vim, if you want to ignore all code fragment placed in a block such as :\r\n    #ifdef DEBUG\r\n    ...\r\n    #endif\r\n  You only have to execute the command :DoxUndoc(DEBUG) !\r\n  \r\n- Group :\r\n  In vim, execute the command :DoxBlock to insert a doxygen block on the\r\n  following line.\r\n\r\nLimitations:\r\n- Assumes that the function name (and the following opening parenthesis) is\r\n  at least on the third line after current cursor position.\r\n- Not able to update a comment block after it's been written.\r\n- Blocks delimiters (header and footer) are only included for function\r\n  comment.\r\n- Assumes that cindent is used.\r\n- Comments in function parameters (such as void foo(int bar \/* ... *\/, baz))\r\n  are not yet supported.\r\n\r\n\r\nExample:\r\nGiven:\r\nint\r\n  foo(char mychar,\r\n      int myint,\r\n      double* myarray,\r\n      int mask = DEFAULT)\r\n{ \/\/...\r\n}\r\n\r\nIssuing the :Dox command with the cursor on the function declaration would\r\ngenerate\r\n\r\n\/**\r\n * @brief\r\n *\r\n * @param mychar\r\n * @param myint\r\n * @param myarray\r\n * @param mask\r\n *\r\n * @return\r\n *\/\r\n\r\n\r\nTo customize the output of the script, see the g:DoxygenToolkit_*\r\nvariables in the script's source.  These variables can be set in your\r\n.vimrc.\r\n\r\nFor example, my .vimrc contains:\r\nlet g:DoxygenToolkit_briefTag_pre=\"@Synopsis  \"\r\nlet g:DoxygenToolkit_paramTag_pre=\"@Param \"\r\nlet g:DoxygenToolkit_returnTag=\"@Returns   \"\r\nlet g:DoxygenToolkit_blockHeader=\"--------------------------------------------------------------------------\"\r\nlet g:DoxygenToolkit_blockFooter=\"----------------------------------------------------------------------------\"\r\nlet g:DoxygenToolkit_authorName=\"Mathias Lorente\"\r\nlet g:DoxygenToolkit_licenseTag=\"My own license\"   <-- !!! Does not end with \"\\<enter>\"","4":"Currently five purposes have been defined :\r\n\r\nGenerates a doxygen license comment.  The tag text is configurable.\r\n\r\nGenerates a doxygen author skeleton.  The tag text is configurable.\r\n\r\nGenerates a doxygen comment skeleton for a C, C++ or Python function or class,\r\nincluding @brief, @param (for each named argument), and @return.  The tag\r\ntext as well as a comment block header and footer are configurable.\r\n(Consequently, you can have \\brief, etc. if you wish, with little effort.)\r\n\r\nIgnore code fragment placed in a block defined by #ifdef ... #endif (C\/C++).  The\r\nblock name must be given to the function.  All of the corresponding blocks\r\nin all the file will be treated and placed in a new block DOX_SKIP_BLOCK (or\r\nany other name that you have configured).  Then you have to update\r\nPREDEFINED value in your doxygen configuration file with correct block name.\r\nYou also have to set ENABLE_PREPROCESSING to YES.\r\n\r\nGenerate a doxygen group (begining and ending). The tag text is\r\nconfigurable.\r\n\r\nUse:\r\n- Type of comments (C\/C++: \/\/\/ or \/** ... *\/, Python: ## and # ) :\r\n  In vim, default C++ comments are : \/** ... *\/. But if you prefer to use \/\/\/\r\n  Doxygen comments just add 'let g:DoxygenToolkit_commentType = \"C++\"'\r\n  (without quotes) in your .vimrc file\r\n\r\n- License :\r\n  In vim, place the cursor on the line that will follow doxygen license\r\n  comment.  Then, execute the command :DoxLic.  This will generate license\r\n  comment and leave the cursor on the line just after.\r\n\r\n- Author :\r\n  In vim, place the cursor on the line that will follow doxygen author\r\n  comment.  Then, execute the command :DoxAuthor.  This will generate the\r\n  skeleton and leave the cursor just after @author tag if no variable\r\n  define it, or just after the skeleton.\r\n\r\n- Function \/ class comment :\r\n  In vim, place the cursor on the line of the function header (or returned\r\n  value of the function) or the class.  Then execute the command :Dox.  This\r\n  will generate the skeleton and leave the cursor after the @brief tag.\r\n\r\n- Ignore code fragment (C\/C++ only) :\r\n  In vim, if you want to ignore all code fragment placed in a block such as :\r\n    #ifdef DEBUG\r\n    ...\r\n    #endif\r\n  You only have to execute the command :DoxUndoc(DEBUG) !\r\n  \r\n- Group :\r\n  In vim, execute the command :DoxBlock to insert a doxygen block on the\r\n  following line.\r\n\r\nLimitations:\r\n- Assumes that the function name (and the following opening parenthesis) is\r\n  at least on the third line after current cursor position.\r\n- Not able to update a comment block after it's been written.\r\n- Blocks delimiters (header and footer) are only included for function\r\n  comment.\r\n- Assumes that cindent is used.\r\n- Comments in function parameters (such as void foo(int bar \/* ... *\/, baz))\r\n  are not yet supported.\r\n\r\n\r\nExample:\r\nGiven:\r\nint\r\n  foo(char mychar,\r\n      int myint,\r\n      double* myarray,\r\n      int mask = DEFAULT)\r\n{ \/\/...\r\n}\r\n\r\nIssuing the :Dox command with the cursor on the function declaration would\r\ngenerate\r\n\r\n\/**\r\n * @brief\r\n *\r\n * @param mychar\r\n * @param myint\r\n * @param myarray\r\n * @param mask\r\n *\r\n * @return\r\n *\/\r\n\r\n\r\nTo customize the output of the script, see the g:DoxygenToolkit_*\r\nvariables in the script's source.  These variables can be set in your\r\n.vimrc.\r\n\r\nFor example, my .vimrc contains:\r\nlet g:DoxygenToolkit_briefTag_pre=\"@Synopsis  \"\r\nlet g:DoxygenToolkit_paramTag_pre=\"@Param \"\r\nlet g:DoxygenToolkit_returnTag=\"@Returns   \"\r\nlet g:DoxygenToolkit_blockHeader=\"--------------------------------------------------------------------------\"\r\nlet g:DoxygenToolkit_blockFooter=\"----------------------------------------------------------------------------\"\r\nlet g:DoxygenToolkit_authorName=\"Mathias Lorente\"\r\nlet g:DoxygenToolkit_licenseTag=\"My own license\"   <-- !!! Does not end with \"\\<enter>\"","install_details":"Copy to your '~\/.vim\/plugin' directory","5":"Copy to your '~\/.vim\/plugin' directory","first_name":"Mathias","6":"Mathias","last_name":"Lorente","7":"Lorente","releases":[{"0":"987","vim_version":"7.0","1":"7.0","script_version":"0.2.13","2":"0.2.13","version_comment":"Correct insertion position and 'xxx_post' parameters.\r\n   - Insert position is correct when g:DoxygenToolkit_compactOneLineDoc = \"yes\" and let g:DoxygenToolkit_commentType = \"C++\" are set.\r\n   - When you define:\r\n        g:DoxygenToolkit_briefTag_pre = \"@brief \"\r\n        g:DoxygenToolkit_briefTag_post = \"<++>\"\r\n        g:DoxygenToolkit_briefTag_funcName = \"yes\"\r\n     Documentation generated with these parameters is something like:\r\n        \/\/\/ @brief foo <++>\r\n     You can configure similarly parameters to get something like:\r\n        \/\/\/ @brief foo <++>\r\n        \/\/\/ @param bar <++>\r\n        \/\/\/ @param baz <++>","3":"Correct insertion position and 'xxx_post' parameters.\r\n   - Insert position is correct when g:DoxygenToolkit_compactOneLineDoc = \"yes\" and let g:DoxygenToolkit_commentType = \"C++\" are set.\r\n   - When you define:\r\n        g:DoxygenToolkit_briefTag_pre = \"@brief \"\r\n        g:DoxygenToolkit_briefTag_post = \"<++>\"\r\n        g:DoxygenToolkit_briefTag_funcName = \"yes\"\r\n     Documentation generated with these parameters is something like:\r\n        \/\/\/ @brief foo <++>\r\n     You can configure similarly parameters to get something like:\r\n        \/\/\/ @brief foo <++>\r\n        \/\/\/ @param bar <++>\r\n        \/\/\/ @param baz <++>","package":"DoxygenToolkit.vim","4":"DoxygenToolkit.vim","src_id":"14064","5":"14064","creation_date":"1287234387","6":"1287234387"},{"0":"987","vim_version":"7.0","1":"7.0","script_version":"0.2.12","2":"0.2.12","version_comment":"Position the cursor at the right position for one line documentation.\r\n(thanks to brian kropf)","3":"Position the cursor at the right position for one line documentation.\r\n(thanks to brian kropf)","package":"DoxygenToolkit.vim","4":"DoxygenToolkit.vim","src_id":"13796","5":"13796","creation_date":"1284050466","6":"1284050466"},{"0":"987","vim_version":"7.0","1":"7.0","script_version":"0.2.11","2":"0.2.11","version_comment":"Remove trailing blank characters where they are not needed. (Thanks to Lukas Gr\u00c3\u00a4sslin)","3":"Remove trailing blank characters where they are not needed. (Thanks to Lukas Gr\u00c3\u00a4sslin)","package":"DoxygenToolkit.vim","4":"DoxygenToolkit.vim","src_id":"13675","5":"13675","creation_date":"1282775272","6":"1282775272"},{"0":"987","vim_version":"7.0","1":"7.0","script_version":"0.2.10","2":"0.2.10","version_comment":"'extern' keyword added in list of values to ignore for return type.","3":"'extern' keyword added in list of values to ignore for return type.","package":"DoxygenToolkit.vim","4":"DoxygenToolkit.vim","src_id":"13524","5":"13524","creation_date":"1281293989","6":"1281293989"},{"0":"987","vim_version":"7.0","1":"7.0","script_version":"0.2.9","2":"0.2.9","version_comment":"Correct bugs related to templates and add support for throw statement (many thanks to Dennis Lubert):\r\n- Template parameter of different type from class and typename are recognized.\r\n- Indentation mistake while detecting template.\r\n- New options are available: g:DoxygenToolkit_throwTag_pre (default set to '@throw ', can be changed to '@exception ' and g:DoxygenToolkit_throwTag_post\r\n","3":"Correct bugs related to templates and add support for throw statement (many thanks to Dennis Lubert):\r\n- Template parameter of different type from class and typename are recognized.\r\n- Indentation mistake while detecting template.\r\n- New options are available: g:DoxygenToolkit_throwTag_pre (default set to '@throw ', can be changed to '@exception ' and g:DoxygenToolkit_throwTag_post\r\n","package":"DoxygenToolkit.vim","4":"DoxygenToolkit.vim","src_id":"13521","5":"13521","creation_date":"1281272523","6":"1281272523"},{"0":"987","vim_version":"7.0","1":"7.0","script_version":"0.2.8","2":"0.2.8","version_comment":"Add support for documentation of template parameters.\r\n(Thanks to Dennis)","3":"Add support for documentation of template parameters.\r\n(Thanks to Dennis)","package":"DoxygenToolkit.vim","4":"DoxygenToolkit.vim","src_id":"13505","5":"13505","creation_date":"1281131877","6":"1281131877"},{"0":"987","vim_version":"7.0","1":"7.0","script_version":"0.2.7","2":"0.2.7","version_comment":"Increase comparibility with c\/c++ IDE","3":"Increase comparibility with c\/c++ IDE","package":"DoxygenToolkit.vim","4":"DoxygenToolkit.vim","src_id":"11878","5":"11878","creation_date":"1260115227","6":"1260115227"},{"0":"987","vim_version":"7.0","1":"7.0","script_version":"0.2.6","2":"0.2.6","version_comment":"Bug correction (thanks to Jhon Do):\r\nDoxygenToolkit_briefTag_funcName and other xxx_xxName parameters should work properly now.","3":"Bug correction (thanks to Jhon Do):\r\nDoxygenToolkit_briefTag_funcName and other xxx_xxName parameters should work properly now.","package":"DoxygenToolkit.vim","4":"DoxygenToolkit.vim","src_id":"11765","5":"11765","creation_date":"1258666143","6":"1258666143"},{"0":"987","vim_version":"7.0","1":"7.0","script_version":"0.2.5","2":"0.2.5","version_comment":"DoxLic function is corrected (thanks to Roland Kammerer). Date and name are properly set.","3":"DoxLic function is corrected (thanks to Roland Kammerer). Date and name are properly set.","package":"DoxygenToolkit.vim","4":"DoxygenToolkit.vim","src_id":"11228","5":"11228","creation_date":"1250858927","6":"1250858927"},{"0":"987","vim_version":"7.0","1":"7.0","script_version":"0.2.4","2":"0.2.4","version_comment":"Bug correction (thanks to Anders Bo Rasmussen)\r\n   - C++: now functions like  void foo(type &bar); are correctly documented.\r\n          The parameter's name is 'bar' (and no more '&bar').","3":"Bug correction (thanks to Anders Bo Rasmussen)\r\n   - C++: now functions like  void foo(type &bar); are correctly documented.\r\n          The parameter's name is 'bar' (and no more '&bar').","package":"DoxygenToolkit.vim","4":"DoxygenToolkit.vim","src_id":"10579","5":"10579","creation_date":"1242074864","6":"1242074864"},{"0":"987","vim_version":"7.0","1":"7.0","script_version":"0.2.3","2":"0.2.3","version_comment":"Added @version tag into the DocBlock generated by DoxygenAuthorFunc() (thanks to Dave Walter).","3":"Added @version tag into the DocBlock generated by DoxygenAuthorFunc() (thanks to Dave Walter).","package":"DoxygenToolkit.vim","4":"DoxygenToolkit.vim","src_id":"10284","5":"10284","creation_date":"1238059388","6":"1238059388"},{"0":"987","vim_version":"7.0","1":"7.0","script_version":"0.2.2","2":"0.2.2","version_comment":"Comments are now allowed in function declaration. Example:\r\n- C\/C++:   void func( int foo, \/\/ first param\r\n                                   int bar  \/* second param *\/);\r\n\r\n- Python:  def func( foo,  # first param\r\n                                 bar ) # second param","3":"Comments are now allowed in function declaration. Example:\r\n- C\/C++:   void func( int foo, \/\/ first param\r\n                                   int bar  \/* second param *\/);\r\n\r\n- Python:  def func( foo,  # first param\r\n                                 bar ) # second param","package":"DoxygenToolkit.vim","4":"DoxygenToolkit.vim","src_id":"9847","5":"9847","creation_date":"1232468197","6":"1232468197"},{"0":"987","vim_version":"7.0","1":"7.0","script_version":"0.2.1","2":"0.2.1","version_comment":"Bug correction (many thanks to Alexey Radkov)\r\n- C\/C++: following function\/method are now correctly documented:\r\n   - operator(),\r\n   - constructor with initialization parameter(s),\r\n   - pure virtual method,\r\n   - const method.\r\n\r\n- Python:\r\n   - Single line function are now correctly documented.","3":"Bug correction (many thanks to Alexey Radkov)\r\n- C\/C++: following function\/method are now correctly documented:\r\n   - operator(),\r\n   - constructor with initialization parameter(s),\r\n   - pure virtual method,\r\n   - const method.\r\n\r\n- Python:\r\n   - Single line function are now correctly documented.","package":"DoxygenToolkit.vim","4":"DoxygenToolkit.vim","src_id":"9823","5":"9823","creation_date":"1232013498","6":"1232013498"},{"0":"987","vim_version":"7.0","1":"7.0","script_version":"0.2.0","2":"0.2.0","version_comment":"The main function has been rewritten (I hope it is cleaner).\r\n - There is now support for function pointer as parameter (C\/C++).\r\n - You can configure the script to get one line documentation (for\r\n   attribute instance for example, you need to set\r\n   g:DoxygenToolkit_compactOneLineDoc to \"yes\").\r\n\r\n - NEW: Support Python scripts:\r\n   - Function\/method are not scanned, so by default they are considered\r\n      as if they always return something (modify this behavior by defining\r\n      g:DoxygenToolkit_python_autoFunctionReturn to \"no\")\r\n   - self parameter is automatically ignored when scanning function\r\n      parameters (you can change this behavior by defining\r\n      g:DoxygenToolkit_python_autoRemoveSelfParam to \"no\")","3":"The main function has been rewritten (I hope it is cleaner).\r\n - There is now support for function pointer as parameter (C\/C++).\r\n - You can configure the script to get one line documentation (for\r\n   attribute instance for example, you need to set\r\n   g:DoxygenToolkit_compactOneLineDoc to \"yes\").\r\n\r\n - NEW: Support Python scripts:\r\n   - Function\/method are not scanned, so by default they are considered\r\n      as if they always return something (modify this behavior by defining\r\n      g:DoxygenToolkit_python_autoFunctionReturn to \"no\")\r\n   - self parameter is automatically ignored when scanning function\r\n      parameters (you can change this behavior by defining\r\n      g:DoxygenToolkit_python_autoRemoveSelfParam to \"no\")","package":"DoxygenToolkit.vim","4":"DoxygenToolkit.vim","src_id":"9809","5":"9809","creation_date":"1231861548","6":"1231861548"},{"0":"987","vim_version":"6.0","1":"6.0","script_version":"0.1.17","2":"0.1.17","version_comment":"Number of lines scanned is now configurable. Default value is still 10 lines. (Thanks to Spencer Collyer for this improvement).\r\n","3":"Number of lines scanned is now configurable. Default value is still 10 lines. (Thanks to Spencer Collyer for this improvement).\r\n","package":"DoxygenToolkit.vim","4":"DoxygenToolkit.vim","src_id":"6978","5":"6978","creation_date":"1176627433","6":"1176627433"},{"0":"987","vim_version":"6.0","1":"6.0","script_version":"0.1.16","2":"0.1.16","version_comment":"Bug correction : now, function that returns null pointer are correctly documented (thanks to Ronald WAHL for his report and patch).\r\n","3":"Bug correction : now, function that returns null pointer are correctly documented (thanks to Ronald WAHL for his report and patch).\r\n","package":"DoxygenToolkit.vim","4":"DoxygenToolkit.vim","src_id":"6809","5":"6809","creation_date":"1172555622","6":"1172555622"},{"0":"987","vim_version":"6.0","1":"6.0","script_version":"0.1.15","2":"0.1.15","version_comment":"Generated documentation with block header\/footer activated do not integrate header and footer anymore.\r\n","3":"Generated documentation with block header\/footer activated do not integrate header and footer anymore.\r\n","package":"DoxygenToolkit.vim","4":"DoxygenToolkit.vim","src_id":"6735","5":"6735","creation_date":"1171164598","6":"1171164598"},{"0":"987","vim_version":"6.0","1":"6.0","script_version":"0.1.14","2":"0.1.14","version_comment":"New option available for cinoptions : g:DoxygenToolkit_cinoptions (default value is still c1C1)\r\nThanks to Arnaud GODET for this. Now comment can have different indentation style.\r\n","3":"New option available for cinoptions : g:DoxygenToolkit_cinoptions (default value is still c1C1)\r\nThanks to Arnaud GODET for this. Now comment can have different indentation style.\r\n","package":"DoxygenToolkit.vim","4":"DoxygenToolkit.vim","src_id":"6376","5":"6376","creation_date":"1162609171","6":"1162609171"},{"0":"987","vim_version":"6.0","1":"6.0","script_version":"0.1.13","2":"0.1.13","version_comment":"Changes for linux kernel comment style","3":"Changes for linux kernel comment style","package":"DoxygenToolkit.vim","4":"DoxygenToolkit.vim","src_id":"4177","5":"4177","creation_date":"1113752698","6":"1113752698"},{"0":"987","vim_version":"6.0","1":"6.0","script_version":"0.1.12","2":"0.1.12","version_comment":"Fixed indentation in comments (suggested by Soh Kok Hong and required by other users)","3":"Fixed indentation in comments (suggested by Soh Kok Hong and required by other users)","package":"DoxygenToolkit.vim","4":"DoxygenToolkit.vim","src_id":"4048","5":"4048","creation_date":"1111383733","6":"1111383733"},{"0":"987","vim_version":"6.0","1":"6.0","script_version":"0.1.12","2":"0.1.12","version_comment":"Now you can use your own comment tag (not only C or C++). In this case, you have to define: 'g:DoxygenToolkit_startCommentTag', 'g:DoxygenToolkit_interCommentTag' and 'g:DoxygenToolkit_endCommentTag' in your .vimrc file.","3":"Now you can use your own comment tag (not only C or C++). In this case, you have to define: 'g:DoxygenToolkit_startCommentTag', 'g:DoxygenToolkit_interCommentTag' and 'g:DoxygenToolkit_endCommentTag' in your .vimrc file.","package":"DoxygenToolkit.vim","4":"DoxygenToolkit.vim","src_id":"3800","5":"3800","creation_date":"1106816636","6":"1106816636"},{"0":"987","vim_version":"6.0","1":"6.0","script_version":"0.1.11","2":"0.1.11","version_comment":"The real 0.1.11 version...\r\nSorry for my mistake (thank to Jason Mills who pointed me out this error....)","3":"The real 0.1.11 version...\r\nSorry for my mistake (thank to Jason Mills who pointed me out this error....)","package":"DoxygenToolkit.vim","4":"DoxygenToolkit.vim","src_id":"3646","5":"3646","creation_date":"1101097226","6":"1101097226"},{"0":"987","vim_version":"6.0","1":"6.0","script_version":"0.1.10","2":"0.1.10","version_comment":"Bug correction for constructors \/ destructor and functions preceded by spaces (or tabs).","3":"Bug correction for constructors \/ destructor and functions preceded by spaces (or tabs).","package":"DoxygenToolkit.vim","4":"DoxygenToolkit.vim","src_id":"3086","5":"3086","creation_date":"1086084241","6":"1086084241"},{"0":"987","vim_version":"6.0","1":"6.0","script_version":"0.1.9","2":"0.1.9","version_comment":"Fixed filename bug when including doxygen author comment whereas file has not been open directly on commamd line.\r\nNow \/\/\/ or \/** doxygen comments are correctly integrated (except for license).","3":"Fixed filename bug when including doxygen author comment whereas file has not been open directly on commamd line.\r\nNow \/\/\/ or \/** doxygen comments are correctly integrated (except for license).","package":"DoxygenToolkit.vim","4":"DoxygenToolkit.vim","src_id":"3058","5":"3058","creation_date":"1085470856","6":"1085470856"},{"0":"987","vim_version":"6.0","1":"6.0","script_version":"0.1.8","2":"0.1.8","version_comment":"Some changes and bug correction for some configuration (thanks to Jason Mills).","3":"Some changes and bug correction for some configuration (thanks to Jason Mills).","package":"DoxygenToolkit.vim","4":"DoxygenToolkit.vim","src_id":"3054","5":"3054","creation_date":"1085360957","6":"1085360957"},{"0":"987","vim_version":"6.0","1":"6.0","script_version":"0.1.7","2":"0.1.7","version_comment":"Bug correction in DoxygenUndocumentFunc.","3":"Bug correction in DoxygenUndocumentFunc.","package":"DoxygenToolkit.vim","4":"DoxygenToolkit.vim","src_id":"3029","5":"3029","creation_date":"1084756367","6":"1084756367"},{"0":"987","vim_version":"6.0","1":"6.0","script_version":"0.1.6","2":"0.1.6","version_comment":"Few code modification and new functionalities","3":"Few code modification and new functionalities","package":"DoxygenToolkit.vim","4":"DoxygenToolkit.vim","src_id":"3025","5":"3025","creation_date":"1084521031","6":"1084521031"},{"0":"987","vim_version":"6.0","1":"6.0","script_version":"0.1.5","2":"0.1.5","version_comment":"Initial upload","3":"Initial upload","package":"DoxygenToolkit.vim","4":"DoxygenToolkit.vim","src_id":"3023","5":"3023","creation_date":"1084517534","6":"1084517534"}]},"986":{"script_id":"986","0":"986","script_name":"ASPJScript","1":"ASPJScript","script_type":"syntax","2":"syntax","summary":"ASP JScript Support","3":"ASP JScript Support","description":"These three files will enable support for ASP in JScript mode.\r\n\r\nScreenshot at: http:\/\/vi-improved.com\/aspjscript.png (large)","4":"These three files will enable support for ASP in JScript mode.\r\n\r\nScreenshot at: http:\/\/vi-improved.com\/aspjscript.png (large)","install_details":"Unzip the files in your vim directory.  If you want it to work automatically, you will also need to edit your filetype.vim to source aspjscript.vim which require jscript.vim or, more simply, you can just add \r\nau BufNewFile,BufRead *.asp :set ft=aspjscript \" all my .asp files ARE jscript\r\ninto your .vimrc (_vimrc)\r\n\r\nHope this helps you... join #vim on irc.freenode.net for all your vim help needs :)","5":"Unzip the files in your vim directory.  If you want it to work automatically, you will also need to edit your filetype.vim to source aspjscript.vim which require jscript.vim or, more simply, you can just add \r\nau BufNewFile,BufRead *.asp :set ft=aspjscript \" all my .asp files ARE jscript\r\ninto your .vimrc (_vimrc)\r\n\r\nHope this helps you... join #vim on irc.freenode.net for all your vim help needs :)","first_name":"Robert","6":"Robert","last_name":"Melton","7":"Melton","releases":[{"0":"986","vim_version":"6.0","1":"6.0","script_version":"1.1","2":"1.1","version_comment":"Now includes matchit.vim stuff for html tag matching.","3":"Now includes matchit.vim stuff for html tag matching.","package":"aspjscript.zip","4":"aspjscript.zip","src_id":"3065","5":"3065","creation_date":"1085733758","6":"1085733758"},{"0":"986","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"aspjscript.zip","4":"aspjscript.zip","src_id":"3021","5":"3021","creation_date":"1084378558","6":"1084378558"}]},"985":{"script_id":"985","0":"985","script_name":"metacosm.vim","1":"metacosm.vim","script_type":"color scheme","2":"color scheme","summary":"Evening & Torte + Special Sauce == Good","3":"Evening & Torte + Special Sauce == Good","description":"You can get this script in the sampler pack at http:\/\/vim.sourceforge.net\/scripts\/script.php?script_id=625 as the other 99 top rated themes. \r\n\r\nA major goal of this colorscheme is to have all the elements of the editor properly themed, including listchars, fold columns, folds, comments, line numbers and everything else you can think off -- if you find something that seems to stick out from the rest, please email me.  I make this a point because I dislike themes that are nice, dark and soothing except for showing painfully bright line numbers and\/or listchars. \r\n\r\nScreenshot at: http:\/\/vi-improved.org\/metacosm.png","4":"You can get this script in the sampler pack at http:\/\/vim.sourceforge.net\/scripts\/script.php?script_id=625 as the other 99 top rated themes. \r\n\r\nA major goal of this colorscheme is to have all the elements of the editor properly themed, including listchars, fold columns, folds, comments, line numbers and everything else you can think off -- if you find something that seems to stick out from the rest, please email me.  I make this a point because I dislike themes that are nice, dark and soothing except for showing painfully bright line numbers and\/or listchars. \r\n\r\nScreenshot at: http:\/\/vi-improved.org\/metacosm.png","install_details":"Put in your colors directory, select by doing :colo metacosm\r\n\r\nHope this helps you... join #vim on irc.freenode.net for all your vim help needs :)","5":"Put in your colors directory, select by doing :colo metacosm\r\n\r\nHope this helps you... join #vim on irc.freenode.net for all your vim help needs :)","first_name":"Robert","6":"Robert","last_name":"Melton","7":"Melton","releases":[{"0":"985","vim_version":"7.0","1":"7.0","script_version":"7.02","2":"7.02","version_comment":"The WarningMsg was hard to read (blue on black) and has been updated.","3":"The WarningMsg was hard to read (blue on black) and has been updated.","package":"metacosm.vim","4":"metacosm.vim","src_id":"10743","5":"10743","creation_date":"1244205225","6":"1244205225"},{"0":"985","vim_version":"7.0","1":"7.0","script_version":"7.01","2":"7.01","version_comment":"Small correction. ","3":"Small correction. ","package":"metacosm.vim","4":"metacosm.vim","src_id":"10737","5":"10737","creation_date":"1244167141","6":"1244167141"},{"0":"985","vim_version":"7.0","1":"7.0","script_version":"7.0","2":"7.0","version_comment":"I haven't uploaded a new version in awhile, so here it is...","3":"I haven't uploaded a new version in awhile, so here it is...","package":"metacosm.vim","4":"metacosm.vim","src_id":"10733","5":"10733","creation_date":"1244137704","6":"1244137704"},{"0":"985","vim_version":"7.0","1":"7.0","script_version":"5.0","2":"5.0","version_comment":"Improvements everywhere... ","3":"Improvements everywhere... ","package":"metacosm.vim","4":"metacosm.vim","src_id":"7611","5":"7611","creation_date":"1188591093","6":"1188591093"},{"0":"985","vim_version":"6.0","1":"6.0","script_version":"2.0","2":"2.0","version_comment":"Major Update: Many updates.  Dropped support for console (was horrible anyway).  Added in many more syntax groups to make sure look was always consistant, cleaned up massively, groups by \"type\" of highlight, and a few color changes (mostly brightness shifts, better cleaner colors for splits) ","3":"Major Update: Many updates.  Dropped support for console (was horrible anyway).  Added in many more syntax groups to make sure look was always consistant, cleaned up massively, groups by \"type\" of highlight, and a few color changes (mostly brightness shifts, better cleaner colors for splits) ","package":"metacosm.vim","4":"metacosm.vim","src_id":"3163","5":"3163","creation_date":"1087694901","6":"1087694901"},{"0":"985","vim_version":"6.0","1":"6.0","script_version":"1.6","2":"1.6","version_comment":"Fixed FoldColumn Highlighting (Thanks reltuk)","3":"Fixed FoldColumn Highlighting (Thanks reltuk)","package":"metacosm.vim","4":"metacosm.vim","src_id":"3150","5":"3150","creation_date":"1087570358","6":"1087570358"},{"0":"985","vim_version":"6.0","1":"6.0","script_version":"1.5","2":"1.5","version_comment":"ff=unix now (same error, again, silly me)","3":"ff=unix now (same error, again, silly me)","package":"metacosm.vim","4":"metacosm.vim","src_id":"3072","5":"3072","creation_date":"1085930470","6":"1085930470"},{"0":"985","vim_version":"6.0","1":"6.0","script_version":"1.4","2":"1.4","version_comment":"change the color of the active status bar","3":"change the color of the active status bar","package":"metacosm.vim","4":"metacosm.vim","src_id":"3070","5":"3070","creation_date":"1085929259","6":"1085929259"}]},"984":{"script_id":"984","0":"984","script_name":"mappinggroup.vim","1":"mappinggroup.vim","script_type":"utility","2":"utility","summary":"Map function keys to act like a multilevel menu","3":"Map function keys to act like a multilevel menu","description":"This plugin allows you to map function keys to perform different tasks: running a normal command, calling a function, or call a function that will load a new set of mappings.  The plugin supports multilevel key mapping function keys such that after loading a new set of key mappings, it's possible to go back to the previous configuration of function key mappings.\r\n\r\nIt is useful to help loading different key map configurations, and also good for key mapping not so frequently used functions.\r\n","4":"This plugin allows you to map function keys to perform different tasks: running a normal command, calling a function, or call a function that will load a new set of mappings.  The plugin supports multilevel key mapping function keys such that after loading a new set of key mappings, it's possible to go back to the previous configuration of function key mappings.\r\n\r\nIt is useful to help loading different key map configurations, and also good for key mapping not so frequently used functions.\r\n","install_details":"Drop the mappinggroup.vim into your plugin directory and read the usage in that file to learn how to setup your own mappings.  An example.vim file is included to show how I use this plugin.\r\n","5":"Drop the mappinggroup.vim into your plugin directory and read the usage in that file to learn how to setup your own mappings.  An example.vim file is included to show how I use this plugin.\r\n","first_name":"Chao-Kuo","6":"Chao-Kuo","last_name":"Lin","7":"Lin","releases":[{"0":"984","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"mappinggroup.tar.gz","4":"mappinggroup.tar.gz","src_id":"3019","5":"3019","creation_date":"1084375930","6":"1084375930"}]},"983":{"script_id":"983","0":"983","script_name":"onsgmls.vim","1":"onsgmls.vim","script_type":"utility","2":"utility","summary":"A compiler plugin for the onsgmls (or nsgmls) SGML\/XML validator","3":"A compiler plugin for the onsgmls (or nsgmls) SGML\/XML validator","description":"Lets you validate XML and SGML documents with onsgmls (from the OpenSP suite) or nsgmls (from James Clark's SP suite).  According to Vim's documentation, \"The idea is to save the error messages from the compiler in a file and use Vim to jump to the errors one by one.  You can examine each problem and fix it, without having to remember all the error messages.\" \r\n  ","4":"Lets you validate XML and SGML documents with onsgmls (from the OpenSP suite) or nsgmls (from James Clark's SP suite).  According to Vim's documentation, \"The idea is to save the error messages from the compiler in a file and use Vim to jump to the errors one by one.  You can examine each problem and fix it, without having to remember all the error messages.\" \r\n  ","install_details":"You must have either the onsgmls or nsgmls parser.  The OpenSP suite contains the onsgmls parser, and can be downloaded here: http:\/\/sourceforge.net\/projects\/openjade\/\r\n\r\ncopy the plugin file to your compiler directory (usually ~\/.vim\/compiler\/).  If you use nsgmls, just replace all the instances of \"onsgmls\" in the file with \"nsgmls\" (and rename the file to nsgmls.vim)\r\n\r\nTo use it, open an xml or sgml file and type \":compiler onsgmls\", followed by \":make\".  If there are errors, you can display all at the bottom of the screen with \":cw\".  From there, you can hit Enter on an error (or double click it in Gvim) to navigate to it.  \r\n\r\nFor more info on using  quickfix commands, type \":help quickfix\"\r\n\r\nImprovements and fixes are appreciated and encouraged.  Just email me.  Thanks.","5":"You must have either the onsgmls or nsgmls parser.  The OpenSP suite contains the onsgmls parser, and can be downloaded here: http:\/\/sourceforge.net\/projects\/openjade\/\r\n\r\ncopy the plugin file to your compiler directory (usually ~\/.vim\/compiler\/).  If you use nsgmls, just replace all the instances of \"onsgmls\" in the file with \"nsgmls\" (and rename the file to nsgmls.vim)\r\n\r\nTo use it, open an xml or sgml file and type \":compiler onsgmls\", followed by \":make\".  If there are errors, you can display all at the bottom of the screen with \":cw\".  From there, you can hit Enter on an error (or double click it in Gvim) to navigate to it.  \r\n\r\nFor more info on using  quickfix commands, type \":help quickfix\"\r\n\r\nImprovements and fixes are appreciated and encouraged.  Just email me.  Thanks.","first_name":"Robert","6":"Robert","last_name":"Rowsome","7":"Rowsome","releases":[{"0":"983","vim_version":"7.0","1":"7.0","script_version":"0.2","2":"0.2","version_comment":"Updated my contact info","3":"Updated my contact info","package":"onsgmls.vim","4":"onsgmls.vim","src_id":"18416","5":"18416","creation_date":"1345150326","6":"1345150326"},{"0":"983","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"onsgmls.vim","4":"onsgmls.vim","src_id":"3008","5":"3008","creation_date":"1084178873","6":"1084178873"}]},"982":{"script_id":"982","0":"982","script_name":"Simple templates","1":"Simple templates","script_type":"utility","2":"utility","summary":"Simple template insertion","3":"Simple template insertion","description":"These are three very simple mappings that save me a lot of time...\r\n\r\nJust create a directory with templates (i.e. a latex article, a copyright notice, a function header,...).  Edit TEMPLATE_HOME in the script, and you'll be able to use the following commands:\r\n\r\n:TT c  --> print template TEMPLATE_HOME\/c on top of file (template top)\r\n:TH f  --> print template TEMPLATE_HOME\/f on current line (template here)\r\n:LST   --> lists contents of templates directory\r\n\r\nHope you find it useful!\r\n\r\n","4":"These are three very simple mappings that save me a lot of time...\r\n\r\nJust create a directory with templates (i.e. a latex article, a copyright notice, a function header,...).  Edit TEMPLATE_HOME in the script, and you'll be able to use the following commands:\r\n\r\n:TT c  --> print template TEMPLATE_HOME\/c on top of file (template top)\r\n:TH f  --> print template TEMPLATE_HOME\/f on current line (template here)\r\n:LST   --> lists contents of templates directory\r\n\r\nHope you find it useful!\r\n\r\n","install_details":"Just copy to your .vimrc or put it on your plugins directory","5":"Just copy to your .vimrc or put it on your plugins directory","first_name":"Javier","6":"Javier","last_name":"Cardona","7":"Cardona","releases":[{"0":"982","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"templates.vim","4":"templates.vim","src_id":"3007","5":"3007","creation_date":"1084158128","6":"1084158128"}]},"981":{"script_id":"981","0":"981","script_name":"GtkFileChooser","1":"GtkFileChooser","script_type":"utility","2":"utility","summary":"Patch that adds GtkFileChooser support to gvim (GTK 2.4+)","3":"Patch that adds GtkFileChooser support to gvim (GTK 2.4+)","description":"This patch makes GTK\/GNOME VIM use new GtkFileChooser for opening and saving files. It requires at least version 2.4 of GTK+ .\r\n\r\nComments are welcome :)","4":"This patch makes GTK\/GNOME VIM use new GtkFileChooser for opening and saving files. It requires at least version 2.4 of GTK+ .\r\n\r\nComments are welcome :)","install_details":"Diff was made against 6.2.426 but should apply to earlier versions with some tweaking.","5":"Diff was made against 6.2.426 but should apply to earlier versions with some tweaking.","first_name":"Krzysztof","6":"Krzysztof","last_name":"Luks","7":"Luks","releases":[{"0":"981","vim_version":"6.0","1":"6.0","script_version":"0.2","2":"0.2","version_comment":" * this patch no longer makes changes to configure.in and config.h\r\n * removed extraneous printf\r\n * tested with VIM 6.3b","3":" * this patch no longer makes changes to configure.in and config.h\r\n * removed extraneous printf\r\n * tested with VIM 6.3b","package":"vim-gtkfilechooser_20040519.diff","4":"vim-gtkfilechooser_20040519.diff","src_id":"3036","5":"3036","creation_date":"1084962911","6":"1084962911"},{"0":"981","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"vim-gtkfilechooser_20040508.diff.gz","4":"vim-gtkfilechooser_20040508.diff.gz","src_id":"3006","5":"3006","creation_date":"1084097272","6":"1084097272"}]},"980":{"script_id":"980","0":"980","script_name":"ssa.vim","1":"ssa.vim","script_type":"syntax","2":"syntax","summary":"syntax highlighting for SubStationAlpha","3":"syntax highlighting for SubStationAlpha","description":"Simple highlighting for SubStationAlpha scripts, highlights dialogs and TextSub codes.","4":"Simple highlighting for SubStationAlpha scripts, highlights dialogs and TextSub codes.","install_details":"Add ssa.vim to syntax directory, and add these lines to filetype.vim:\r\n\r\n\" SubStationAlpha\r\nau BufNewFile,BufRead *.ssa setf ssa\r\n","5":"Add ssa.vim to syntax directory, and add these lines to filetype.vim:\r\n\r\n\" SubStationAlpha\r\nau BufNewFile,BufRead *.ssa setf ssa\r\n","first_name":"Don","6":"Don","last_name":"Yang","7":"Yang","releases":[{"0":"980","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"ssa.vim","4":"ssa.vim","src_id":"2999","5":"2999","creation_date":"1083855649","6":"1083855649"}]},"979":{"script_id":"979","0":"979","script_name":"idf.vim","1":"idf.vim","script_type":"syntax","2":"syntax","summary":"Syntax highlighting for EnergyPlus IDF files.","3":"Syntax highlighting for EnergyPlus IDF files.","description":"Idf.vim provides basic syntax support for EnergyPlus IDF files.","4":"Idf.vim provides basic syntax support for EnergyPlus IDF files.","install_details":"Drop it in a \"syntax\" directory.","5":"Drop it in a \"syntax\" directory.","first_name":"Christian","6":"Christian","last_name":"Schiefer","7":"Schiefer","releases":[{"0":"979","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"idf.vim","4":"idf.vim","src_id":"2998","5":"2998","creation_date":"1083847139","6":"1083847139"}]},"978":{"script_id":"978","0":"978","script_name":"svn-diff.vim","1":"svn-diff.vim","script_type":"ftplugin","2":"ftplugin","summary":"Show diff  when commiting changes on a subversion repository","3":"Show diff  when commiting changes on a subversion repository","description":"This script will show you the output of 'svn diff' when commiting changes against a subversion repository. \r\n\r\nIt open a new windows showing the diff, to help you summarizing the changes you are commiting.\r\n\r\n\r\n","4":"This script will show you the output of 'svn diff' when commiting changes against a subversion repository. \r\n\r\nIt open a new windows showing the diff, to help you summarizing the changes you are commiting.\r\n\r\n\r\n","install_details":"Just drop the script in ~\/.vim\/ftplugin\/.\r\n","5":"Just drop the script in ~\/.vim\/ftplugin\/.\r\n","first_name":"Michael","6":"Michael","last_name":"Scherer","7":"Scherer","releases":[{"0":"978","vim_version":"6.0","1":"6.0","script_version":"0.5","2":"0.5","version_comment":"Better indentation, do not preview if nothing was modified ( patch from Marius Gedminas ).","3":"Better indentation, do not preview if nothing was modified ( patch from Marius Gedminas ).","package":"svn.vim","4":"svn.vim","src_id":"3853","5":"3853","creation_date":"1108113271","6":"1108113271"},{"0":"978","vim_version":"6.0","1":"6.0","script_version":"0.4","2":"0.4","version_comment":"No more TODO list, now everything i in pure vim function.","3":"No more TODO list, now everything i in pure vim function.","package":"svn.vim","4":"svn.vim","src_id":"3841","5":"3841","creation_date":"1107870249","6":"1107870249"},{"0":"978","vim_version":"6.0","1":"6.0","script_version":"0.3","2":"0.3","version_comment":"integrate patch that people send :\r\n- no longer ask for confirmation when closing windows\r\n- place focus where it belong","3":"integrate patch that people send :\r\n- no longer ask for confirmation when closing windows\r\n- place focus where it belong","package":"svn.vim","4":"svn.vim","src_id":"3819","5":"3819","creation_date":"1107178084","6":"1107178084"},{"0":"978","vim_version":"6.0","1":"6.0","script_version":"0.2","2":"0.2","version_comment":"Fixed a stupid bug regarding the svn diff command","3":"Fixed a stupid bug regarding the svn diff command","package":"svn.vim","4":"svn.vim","src_id":"3100","5":"3100","creation_date":"1086509177","6":"1086509177"},{"0":"978","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"svn-diff.vim","4":"svn-diff.vim","src_id":"2994","5":"2994","creation_date":"1083744858","6":"1083744858"}]},"977":{"script_id":"977","0":"977","script_name":"Maxscript","1":"Maxscript","script_type":"syntax","2":"syntax","summary":"Simple syntax highlighting for Maxscript","3":"Simple syntax highlighting for Maxscript","description":"Syntax highlighting for Maxscript language. Maxscript is a part of 3DSMax rendering software.","4":"Syntax highlighting for Maxscript language. Maxscript is a part of 3DSMax rendering software.","install_details":"","5":"","first_name":"Jens","6":"Jens","last_name":"Berlips","7":"Berlips","releases":[{"0":"977","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"ms.vim","4":"ms.vim","src_id":"2991","5":"2991","creation_date":"1083597360","6":"1083597360"}]},"976":{"script_id":"976","0":"976","script_name":"Tibet","1":"Tibet","script_type":"color scheme","2":"color scheme","summary":"A Colorscheme Inspired in Tibetan coloring","3":"A Colorscheme Inspired in Tibetan coloring","description":"Just a new colorscheme based in desert that is inspired in tibetan coloring.\r\nFor those who like Dark Red backgrounds....","4":"Just a new colorscheme based in desert that is inspired in tibetan coloring.\r\nFor those who like Dark Red backgrounds....","install_details":"","5":"","first_name":"Miguel","6":"Miguel","last_name":"Figueiredo","7":"Figueiredo","releases":[{"0":"976","vim_version":"6.0","1":"6.0","script_version":"0.2","2":"0.2","version_comment":"Changed LineNr","3":"Changed LineNr","package":"tibet.vim","4":"tibet.vim","src_id":"2987","5":"2987","creation_date":"1083262839","6":"1083262839"},{"0":"976","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"tibet.vim","4":"tibet.vim","src_id":"2986","5":"2986","creation_date":"1083262596","6":"1083262596"}]},"975":{"script_id":"975","0":"975","script_name":"Siebel VB Script (SVB)","1":"Siebel VB Script (SVB)","script_type":"syntax","2":"syntax","summary":"Syntax File for files with extensions .sbl","3":"Syntax File for files with extensions .sbl","description":"Siebel VBScript Syntax File. Since SVB is based on VBScript, this file takes the basic work by Johannes Zellner <johannes@zellner.org> on VB syntax files and adds support for Siebel specific stuff","4":"Siebel VBScript Syntax File. Since SVB is based on VBScript, this file takes the basic work by Johannes Zellner <johannes@zellner.org> on VB syntax files and adds support for Siebel specific stuff","install_details":"Just take sbl.vim and put it into $VIM\/vimfiles\/syntax (where $VIM is where ur Vim is installed). Its that simple.","5":"Just take sbl.vim and put it into $VIM\/vimfiles\/syntax (where $VIM is where ur Vim is installed). Its that simple.","first_name":"M","6":"M","last_name":"K","7":"K","releases":[{"0":"975","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"sbl.vim","4":"sbl.vim","src_id":"2982","5":"2982","creation_date":"1083119942","6":"1083119942"}]},"974":{"script_id":"974","0":"974","script_name":"indent\/python.vim","1":"indent\/python.vim","script_type":"indent","2":"indent","summary":"An alternative indentation script for python","3":"An alternative indentation script for python","description":"This indentation script for python tries to match more closely what is suggested in PEP 8 (http:\/\/www.python.org\/peps\/pep-0008.html).  In particular, it handles continuation lines implied by open (parentheses), [brackets] and {braces} correctly and it indents multiline if\/for\/while statements differently.\r\n\r\nComments are welcome!\r\n","4":"This indentation script for python tries to match more closely what is suggested in PEP 8 (http:\/\/www.python.org\/peps\/pep-0008.html).  In particular, it handles continuation lines implied by open (parentheses), [brackets] and {braces} correctly and it indents multiline if\/for\/while statements differently.\r\n\r\nComments are welcome!\r\n","install_details":"Drop the script in your ~\/.vim\/indent directory.","5":"Drop the script in your ~\/.vim\/indent directory.","first_name":"Eric","6":"Eric","last_name":"Mc Sween","7":"Mc Sween","releases":[{"0":"974","vim_version":"6.0","1":"6.0","script_version":"0.3","2":"0.3","version_comment":"Changes:\r\n- Update one shiftwidth instead of aligning with parens that stand at the end of a line.","3":"Changes:\r\n- Update one shiftwidth instead of aligning with parens that stand at the end of a line.","package":"python.vim","4":"python.vim","src_id":"4316","5":"4316","creation_date":"1116843238","6":"1116843238"},{"0":"974","vim_version":"6.0","1":"6.0","script_version":"0.2","2":"0.2","version_comment":"Changes:\r\n- Fix: skip parentheses in strings and comments.\r\n- Line up elif\/else and except\/finally with the most probable corresponding if or try statement.\r\n- Dedent after 'pass'. (Jeffrey Collins)","3":"Changes:\r\n- Fix: skip parentheses in strings and comments.\r\n- Line up elif\/else and except\/finally with the most probable corresponding if or try statement.\r\n- Dedent after 'pass'. (Jeffrey Collins)","package":"python.vim","4":"python.vim","src_id":"3105","5":"3105","creation_date":"1086624535","6":"1086624535"},{"0":"974","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"python.vim","4":"python.vim","src_id":"2981","5":"2981","creation_date":"1082987635","6":"1082987635"}]},"973":{"script_id":"973","0":"973","script_name":"rest.vim","1":"rest.vim","script_type":"syntax","2":"syntax","summary":"A reStructuredText syntax mode","3":"A reStructuredText syntax mode","description":"A reStructuredText Syntax highlighting mode for vim","4":"A reStructuredText Syntax highlighting mode for vim","install_details":"Drop the file in your ~\/.vim\/syntax\/ directory, and set syntax=rest.","5":"Drop the file in your ~\/.vim\/syntax\/ directory, and set syntax=rest.","first_name":"estienne","6":"estienne","last_name":"swart","7":"swart","releases":[{"0":"973","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"rest.tar.gz","4":"rest.tar.gz","src_id":"2979","5":"2979","creation_date":"1082953865","6":"1082953865"}]},"972":{"script_id":"972","0":"972","script_name":"chela_light","1":"chela_light","script_type":"color scheme","2":"color scheme","summary":"A light color scheme","3":"A light color scheme","description":"This is a light color scheme. I haven't included support for terminals yet, so only try it if you have the GUI running.\r\n\r\nMy goal was to make a color scheme that (1) doesn't scare you when you do a \":vert diffsplit\" :-), and (2) is more or less consistent with the standard Windows XP look.\r\n\r\nI'm pretty satisfied with the look, but if you're used to sit in front of the computer for 48 hours straight, you should either get yourself a life (recommended) or use a dark color scheme such as \"ps_color\" (vimscript #760) by P. Shizhu.\r\n\r\nOn Windows XP I prefer the Lucida Console font (\"set guifont=Lucida_Console:h10:cANSI\"), so this color scheme probably looks best with that font. On Linux it looks pretty OK with Bitstream Vera Sans Mono.","4":"This is a light color scheme. I haven't included support for terminals yet, so only try it if you have the GUI running.\r\n\r\nMy goal was to make a color scheme that (1) doesn't scare you when you do a \":vert diffsplit\" :-), and (2) is more or less consistent with the standard Windows XP look.\r\n\r\nI'm pretty satisfied with the look, but if you're used to sit in front of the computer for 48 hours straight, you should either get yourself a life (recommended) or use a dark color scheme such as \"ps_color\" (vimscript #760) by P. Shizhu.\r\n\r\nOn Windows XP I prefer the Lucida Console font (\"set guifont=Lucida_Console:h10:cANSI\"), so this color scheme probably looks best with that font. On Linux it looks pretty OK with Bitstream Vera Sans Mono.","install_details":"Just drop it in your local color scheme directory (e.g. ~\/.vim\/colors\/) and then execute the command \":colorscheme chela_light\".","5":"Just drop it in your local color scheme directory (e.g. ~\/.vim\/colors\/) and then execute the command \":colorscheme chela_light\".","first_name":"Stefan","6":"Stefan","last_name":"Karlsson","7":"Karlsson","releases":[{"0":"972","vim_version":"6.0","1":"6.0","script_version":"1.9","2":"1.9","version_comment":"(1) Made MatchParen less scary. (2) Various minor changes for vim 7.","3":"(1) Made MatchParen less scary. (2) Various minor changes for vim 7.","package":"chela_light.vim","4":"chela_light.vim","src_id":"6052","5":"6052","creation_date":"1155043283","6":"1155043283"},{"0":"972","vim_version":"6.0","1":"6.0","script_version":"1.8","2":"1.8","version_comment":"Changed \"MatchParen\" from red to gren. The red color made it look to much like an error.","3":"Changed \"MatchParen\" from red to gren. The red color made it look to much like an error.","package":"chela_light.vim","4":"chela_light.vim","src_id":"5555","5":"5555","creation_date":"1145015435","6":"1145015435"}]},"971":{"script_id":"971","0":"971","script_name":"folds.vim","1":"folds.vim","script_type":"utility","2":"utility","summary":"Folds the continuous same lines more than 4 to 2 lines and 1 folded line","3":"Folds the continuous same lines more than 4 to 2 lines and 1 folded line","description":"Checking long long log files are boring jobs especially those files contain\r\nthe continuous same lines. \r\nBut why don\\\\\\'t you fold the continuous same lines with this \\\\\\\"folds.vim\\\\\\\".\r\nIt folds the continuous same lines more than 4 to 2 lines and one folded line.\r\nFolds.vim contains\r\n{range}Fold0: Fold the continuous same lines. No column arguments. \r\n{range}Fold1 c1 c2:\r\n            Fold the continuous same lines of columns b\/n c1 and c2.\r\n{range}Fold2 c1 c2:\r\n            Fold the continuous same lines ignoring columns b\/n c1 and c2.\r\nNote that column number c1 and c2 starts with 0, but not 1.","4":"Checking long long log files are boring jobs especially those files contain\r\nthe continuous same lines. \r\nBut why don\\\\\\'t you fold the continuous same lines with this \\\\\\\"folds.vim\\\\\\\".\r\nIt folds the continuous same lines more than 4 to 2 lines and one folded line.\r\nFolds.vim contains\r\n{range}Fold0: Fold the continuous same lines. No column arguments. \r\n{range}Fold1 c1 c2:\r\n            Fold the continuous same lines of columns b\/n c1 and c2.\r\n{range}Fold2 c1 c2:\r\n            Fold the continuous same lines ignoring columns b\/n c1 and c2.\r\nNote that column number c1 and c2 starts with 0, but not 1.","install_details":"Sorce it when you want or put it in \\\\\\\"vim\/vimfiles\/plugun\\\\\\\" folder.","5":"Sorce it when you want or put it in \\\\\\\"vim\/vimfiles\/plugun\\\\\\\" folder.","first_name":"Yasuoki","6":"Yasuoki","last_name":"Mutoh","7":"Mutoh","releases":[{"0":"971","vim_version":"6.0","1":"6.0","script_version":"0.0","2":"0.0","version_comment":"Initial upload","3":"Initial upload","package":"folds.vim","4":"folds.vim","src_id":"2972","5":"2972","creation_date":"1082763936","6":"1082763936"}]},"970":{"script_id":"970","0":"970","script_name":"IncrediBuild.vim","1":"IncrediBuild.vim","script_type":"utility","2":"utility","summary":"Allows building using IncrediBuild, using Vim's quickfix system","3":"Allows building using IncrediBuild, using Vim's quickfix system","description":"This plugin allows building using IncrediBuild, using Vim's quickfix system.\r\n\r\nSee http:\/\/www.xoreax.com\/main.htm for more details on IncrediBuild.","4":"This plugin allows building using IncrediBuild, using Vim's quickfix system.\r\n\r\nSee http:\/\/www.xoreax.com\/main.htm for more details on IncrediBuild.","install_details":"Copy incredibuild.vim to your plugin directory.\r\nEdit the 'USER SETTINGS' section of incredibuild.vim to your liking.\r\nNote that IncrediBuild's executables must be in your path.","5":"Copy incredibuild.vim to your plugin directory.\r\nEdit the 'USER SETTINGS' section of incredibuild.vim to your liking.\r\nNote that IncrediBuild's executables must be in your path.","first_name":"Andy","6":"Andy","last_name":"Berdan","7":"Berdan","releases":[{"0":"970","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"incredibuild.vim","4":"incredibuild.vim","src_id":"2970","5":"2970","creation_date":"1082712633","6":"1082712633"}]},"969":{"script_id":"969","0":"969","script_name":"pic18fxxx","1":"pic18fxxx","script_type":"syntax","2":"syntax","summary":"pic assembly syntax for 18fxxx","3":"pic assembly syntax for 18fxxx","description":"as the assembly\/pic syntax file was made for 16fxx family, I made changes to this file for 18fxxx assembly.","4":"as the assembly\/pic syntax file was made for 16fxx family, I made changes to this file for 18fxxx assembly.","install_details":"","5":"","first_name":"yves","6":"yves","last_name":"kerleguer","7":"kerleguer","releases":[{"0":"969","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"pic18f.vim","4":"pic18f.vim","src_id":"2963","5":"2963","creation_date":"1082536387","6":"1082536387"}]},"968":{"script_id":"968","0":"968","script_name":"autoit.vim","1":"autoit.vim","script_type":"syntax","2":"syntax","summary":"colorize AutoIt scripting language, from Hiddensoft","3":"colorize AutoIt scripting language, from Hiddensoft","description":"syntax file for script languages AutoIt and AutoIt-GUI.\r\nThey are Open Source and freely available at \"http:\/\/www.hiddensoft.com\"","4":"syntax file for script languages AutoIt and AutoIt-GUI.\r\nThey are Open Source and freely available at \"http:\/\/www.hiddensoft.com\"","install_details":"The rules are the same as all the other syntax files:\r\n    1) copy the file in your current vim syntax folder\r\n    2) add the following line in your filetype.vim file, in the correct position, to recognize .au3 files by extension:\r\n    \"au BufNewFile, BufRead *.au3 setf autoit\"","5":"The rules are the same as all the other syntax files:\r\n    1) copy the file in your current vim syntax folder\r\n    2) add the following line in your filetype.vim file, in the correct position, to recognize .au3 files by extension:\r\n    \"au BufNewFile, BufRead *.au3 setf autoit\"","first_name":"Riccardo","6":"Riccardo","last_name":"Casini","7":"Casini","releases":[{"0":"968","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"autoit.txt","4":"autoit.txt","src_id":"2961","5":"2961","creation_date":"1082516913","6":"1082516913"}]},"967":{"script_id":"967","0":"967","script_name":"php.vim for php5","1":"php.vim for php5","script_type":"syntax","2":"syntax","summary":"Syntax file for php5","3":"Syntax file for php5","description":"This is a syntax file for the popular scripting language: php, version 5","4":"This is a syntax file for the popular scripting language: php, version 5","install_details":"","5":"","first_name":"Michiel","6":"Michiel","last_name":"van Vaardegem","7":"van Vaardegem","releases":[{"0":"967","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"php.vim","4":"php.vim","src_id":"2955","5":"2955","creation_date":"1082370640","6":"1082370640"}]},"966":{"script_id":"966","0":"966","script_name":"asmx86","1":"asmx86","script_type":"syntax","2":"syntax","summary":"A Simple x86-ASM syntax for VIM","3":"A Simple x86-ASM syntax for VIM","description":"This is a simple X86 assembly language syntax for VIM.  It's fairly indiscriminant about the assembler syntax you choose to use.  It recognises the mnemonics for \"classic\" intel opcodes, and the GNU (gas) \"mode\" characters appended to these opcodes.  This syntax script contains all known opcodes for the i486 instruction set, and register set.  \r\n\r\nHistory:\r\nThis syntax was hacked using the asm-m68k syntax as a starting point.  (I built this using my intel 486 System Programmer Manual as a reference.)  Because I do a great deal of hacking on assembly language, for several architectures, I felt that a proper (Or at least somewhat better than all-cyan... ;-) syntax highlighting for each one was in order.  Because (at this time), I hack a lot on x86 ASM, I've whipped this up, to help me work on it.  This would not have been possible without several good scripts (C, C++, and m68kASM) to use as starting points, and to rip code from.\r\n\r\nDetails:\r\n\r\nIt is aware of the \"arcane\" instructions for dealing with protected memory activities.  It is also aware of the \"CR\", \"DR\", and \"TR\" register sets.  The syntax does not, at this time, check for validity of operands to your opcodes (To do so would make it unable to be assembler independant.)  It does not know about the conditional jump mnemonics however.  (It merely considers any j.{1,5} string to be a valid jump.)  \r\n\r\nThe FPU instruction set is only partially recognised at this time.  \r\n\r\nThe colour scheme is a bit over-done, perhaps, but I find it useful when debugging some complex projects.  (I've divided the opcodes into several classes... I\/O, mov's, arithmetic, branching, other.)  \r\n\r\nI don't really change it much.  I whipped it up, because I needed some good colour highlighting on my editing of x86 code.  As such, I don't expect to maintain it.  If anyone does wish to take over the maintanance of it, or improve it in any way, I'd be much appreciative.\r\n\r\nKnown Bugs:\r\n\r\nIt gets a bit quirky sometimes on complex nesting of comment types.  The syntax is CPP aware, and tries to \"grey-out\" #if 0, etc.  If nesting several classes of comment, or placing your code shortly after a few variations of comment, you'll possibly have commented lines get syntax highlighted, or your uncommented lines get highlighted as comments.  I've not really figured out why.  A simple \"^L\" to force a redraw seems to solve the problem in any case, so it may just be a bug in the parser unit of my particular version of VIM (Which may be a bit old by now.)\r\n\r\nAny Assembly language isn't easy to hack.  Having a Syntax for it will not make you master it over night.  Having a syntax for a language you're familiar with will make your life much easier though.  \r\n\r\nAlso, expect a few other ASM syntaxes, as I may get to them (Perhaps PPC, Alpha, SH, MiPS, perhaps even a classic PDP11... ;-) \r\n\r\nSorry about being *REALLY* verbose.","4":"This is a simple X86 assembly language syntax for VIM.  It's fairly indiscriminant about the assembler syntax you choose to use.  It recognises the mnemonics for \"classic\" intel opcodes, and the GNU (gas) \"mode\" characters appended to these opcodes.  This syntax script contains all known opcodes for the i486 instruction set, and register set.  \r\n\r\nHistory:\r\nThis syntax was hacked using the asm-m68k syntax as a starting point.  (I built this using my intel 486 System Programmer Manual as a reference.)  Because I do a great deal of hacking on assembly language, for several architectures, I felt that a proper (Or at least somewhat better than all-cyan... ;-) syntax highlighting for each one was in order.  Because (at this time), I hack a lot on x86 ASM, I've whipped this up, to help me work on it.  This would not have been possible without several good scripts (C, C++, and m68kASM) to use as starting points, and to rip code from.\r\n\r\nDetails:\r\n\r\nIt is aware of the \"arcane\" instructions for dealing with protected memory activities.  It is also aware of the \"CR\", \"DR\", and \"TR\" register sets.  The syntax does not, at this time, check for validity of operands to your opcodes (To do so would make it unable to be assembler independant.)  It does not know about the conditional jump mnemonics however.  (It merely considers any j.{1,5} string to be a valid jump.)  \r\n\r\nThe FPU instruction set is only partially recognised at this time.  \r\n\r\nThe colour scheme is a bit over-done, perhaps, but I find it useful when debugging some complex projects.  (I've divided the opcodes into several classes... I\/O, mov's, arithmetic, branching, other.)  \r\n\r\nI don't really change it much.  I whipped it up, because I needed some good colour highlighting on my editing of x86 code.  As such, I don't expect to maintain it.  If anyone does wish to take over the maintanance of it, or improve it in any way, I'd be much appreciative.\r\n\r\nKnown Bugs:\r\n\r\nIt gets a bit quirky sometimes on complex nesting of comment types.  The syntax is CPP aware, and tries to \"grey-out\" #if 0, etc.  If nesting several classes of comment, or placing your code shortly after a few variations of comment, you'll possibly have commented lines get syntax highlighted, or your uncommented lines get highlighted as comments.  I've not really figured out why.  A simple \"^L\" to force a redraw seems to solve the problem in any case, so it may just be a bug in the parser unit of my particular version of VIM (Which may be a bit old by now.)\r\n\r\nAny Assembly language isn't easy to hack.  Having a Syntax for it will not make you master it over night.  Having a syntax for a language you're familiar with will make your life much easier though.  \r\n\r\nAlso, expect a few other ASM syntaxes, as I may get to them (Perhaps PPC, Alpha, SH, MiPS, perhaps even a classic PDP11... ;-) \r\n\r\nSorry about being *REALLY* verbose.","install_details":"Dunno for sure.  I hacked it up, in place in my \/usr\/share\/vim\/...... directory.  Place it somewhere where VIM will get it.  I think you need to hack your filetype.vim file to make it think that .asm, .S, .s, and such are assembly language files to use this syntax (asmx86.vim).  The \"default\" m68k line in there which comes pre-installed could just be changed to asmx86.vim.  Maybe a multiplexing system for this can be cooked up?","5":"Dunno for sure.  I hacked it up, in place in my \/usr\/share\/vim\/...... directory.  Place it somewhere where VIM will get it.  I think you need to hack your filetype.vim file to make it think that .asm, .S, .s, and such are assembly language files to use this syntax (asmx86.vim).  The \"default\" m68k line in there which comes pre-installed could just be changed to asmx86.vim.  Maybe a multiplexing system for this can be cooked up?","first_name":"Adam","6":"Adam","last_name":"Martin","7":"Martin","releases":[{"0":"966","vim_version":"6.0","1":"6.0","script_version":"0.4","2":"0.4","version_comment":"Initial upload","3":"Initial upload","package":"asmx86.vim","4":"asmx86.vim","src_id":"2942","5":"2942","creation_date":"1082158594","6":"1082158594"}]},"965":{"script_id":"965","0":"965","script_name":"uptime.vim","1":"uptime.vim","script_type":"utility","2":"utility","summary":"Display Vim uptimes","3":"Display Vim uptimes","description":"This script displays vim uptimes.\r\n\r\nUsage:\r\n\r\n:Uptime\r\n:Uptime regular (gvim has been up for 2 days, 1 hour, 17 minutes and 2 seconds)\r\n:Uptime short (2d 01:17:02)\r\n:Uptime seconds (264)\r\n\r\nSee :help uptime.txt for details.\r\n\r\nRequirements:\r\n\r\nThis plugin has not been tested on Vim versions below 6.2\r\n","4":"This script displays vim uptimes.\r\n\r\nUsage:\r\n\r\n:Uptime\r\n:Uptime regular (gvim has been up for 2 days, 1 hour, 17 minutes and 2 seconds)\r\n:Uptime short (2d 01:17:02)\r\n:Uptime seconds (264)\r\n\r\nSee :help uptime.txt for details.\r\n\r\nRequirements:\r\n\r\nThis plugin has not been tested on Vim versions below 6.2\r\n","install_details":"Install the .vim file to your local or global plugins directory. You may also want to install the .txt file into the docs directory.","5":"Install the .vim file to your local or global plugins directory. You may also want to install the .txt file into the docs directory.","first_name":"Ciaran","6":"Ciaran","last_name":"McCreesh","7":"McCreesh","releases":[{"0":"965","vim_version":"6.0","1":"6.0","script_version":"1.3","2":"1.3","version_comment":"* moved the :echo so that Uptime() can be used in statusline (thanks to Salman Halim)\r\n* added in short aliases for the format names","3":"* moved the :echo so that Uptime() can be used in statusline (thanks to Salman Halim)\r\n* added in short aliases for the format names","package":"uptime-1.3.tar.bz2","4":"uptime-1.3.tar.bz2","src_id":"3051","5":"3051","creation_date":"1085227562","6":"1085227562"},{"0":"965","vim_version":"6.0","1":"6.0","script_version":"1.2","2":"1.2","version_comment":"* added optional argument controlling output format ('short', 'regular', 'seconds')\r\n* added help document","3":"* added optional argument controlling output format ('short', 'regular', 'seconds')\r\n* added help document","package":"uptime-1.2.tar.bz2","4":"uptime-1.2.tar.bz2","src_id":"3050","5":"3050","creation_date":"1085218862","6":"1085218862"},{"0":"965","vim_version":"6.0","1":"6.0","script_version":"1.1","2":"1.1","version_comment":"Initial upload","3":"Initial upload","package":"uptime.vim","4":"uptime.vim","src_id":"2941","5":"2941","creation_date":"1082139484","6":"1082139484"}]},"964":{"script_id":"964","0":"964","script_name":"nexus.vim","1":"nexus.vim","script_type":"syntax","2":"syntax","summary":"Syntax highlighting for Nexus file format","3":"Syntax highlighting for Nexus file format","description":"This is a syntax highlighting for Nexus, a file format used by many programs in evolutionary biology, like GDA, Paup*, Mesquite, ModelTest, MrBayes and MacClade. A formal description can be found at\r\n\r\nMaddison, D.R., D.L. Swofford, and W.P. Maddison. 1997. NEXUS: An extensible file format for systematic information. Systematic Biology 46: 590-621\r\n\r\nwhile some examples and a short description can be found at\r\n\r\nhttp:\/\/workshop.molecularevolution.org\/resources\/fileformats\/\r\n\r\nThe syntax also takes in consideration some reserved words (private block) used for MrBayes. For the most curious, a screenshot can be seen at\r\n\r\nhttp:\/\/carvalho.webhop.net\/nexus_vim.png","4":"This is a syntax highlighting for Nexus, a file format used by many programs in evolutionary biology, like GDA, Paup*, Mesquite, ModelTest, MrBayes and MacClade. A formal description can be found at\r\n\r\nMaddison, D.R., D.L. Swofford, and W.P. Maddison. 1997. NEXUS: An extensible file format for systematic information. Systematic Biology 46: 590-621\r\n\r\nwhile some examples and a short description can be found at\r\n\r\nhttp:\/\/workshop.molecularevolution.org\/resources\/fileformats\/\r\n\r\nThe syntax also takes in consideration some reserved words (private block) used for MrBayes. For the most curious, a screenshot can be seen at\r\n\r\nhttp:\/\/carvalho.webhop.net\/nexus_vim.png","install_details":"Just put nexus.vim in the syntax folder under $VIMRUNTIME, and call the syntax with :cal SetSyn(\"nexus\").","5":"Just put nexus.vim in the syntax folder under $VIMRUNTIME, and call the syntax with :cal SetSyn(\"nexus\").","first_name":"Luis","6":"Luis","last_name":"Carvalho","7":"Carvalho","releases":[{"0":"964","vim_version":"6.0","1":"6.0","script_version":"0.2","2":"0.2","version_comment":"Fixed some minor bugs, added nexus prefix as suggested by Olivier Mengue' and added nexusPublic to define public blocks.","3":"Fixed some minor bugs, added nexus prefix as suggested by Olivier Mengue' and added nexusPublic to define public blocks.","package":"nexus.vim","4":"nexus.vim","src_id":"2947","5":"2947","creation_date":"1082198050","6":"1082198050"},{"0":"964","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"nexus.vim","4":"nexus.vim","src_id":"2936","5":"2936","creation_date":"1081980705","6":"1081980705"}]},"963":{"script_id":"963","0":"963","script_name":"FTP Completion","1":"FTP Completion","script_type":"utility","2":"utility","summary":"complete files in command line for ftp.","3":"complete files in command line for ftp.","description":"Vim can edit file on ftp server like following.\r\n:e ftp:\/\/ftp.vim.org\/pub\/vim\/patches\/6.2.001\r\n\r\nThis script help the user typing of path.\r\nIf you type ...\r\n:e ftp:\/\/ftp.vim.org\/pub\/vim\/patches\/\r\nand type <c-g><tab>\r\n:e ftp:\/\/ftp.vim.org\/pub\/vim\/patches\/6.2.001\r\nand type <c-g><c-n>\r\n:e ftp:\/\/ftp.vim.org\/pub\/vim\/patches\/6.2.002\r\nand type <c-g><c-p>\r\n:e ftp:\/\/ftp.vim.org\/pub\/vim\/patches\/6.2.001\r\n","4":"Vim can edit file on ftp server like following.\r\n:e ftp:\/\/ftp.vim.org\/pub\/vim\/patches\/6.2.001\r\n\r\nThis script help the user typing of path.\r\nIf you type ...\r\n:e ftp:\/\/ftp.vim.org\/pub\/vim\/patches\/\r\nand type <c-g><tab>\r\n:e ftp:\/\/ftp.vim.org\/pub\/vim\/patches\/6.2.001\r\nand type <c-g><c-n>\r\n:e ftp:\/\/ftp.vim.org\/pub\/vim\/patches\/6.2.002\r\nand type <c-g><c-p>\r\n:e ftp:\/\/ftp.vim.org\/pub\/vim\/patches\/6.2.001\r\n","install_details":"Copy ftpcmpl.vim to your $vimruntime\/plugin.\r\n\r\nThis script use curl for getting list of ftp directory.\r\n(http:\/\/curl.haxx.se\/)\r\n\r\nEnjoy.","5":"Copy ftpcmpl.vim to your $vimruntime\/plugin.\r\n\r\nThis script use curl for getting list of ftp directory.\r\n(http:\/\/curl.haxx.se\/)\r\n\r\nEnjoy.","first_name":"Yasuhiro","6":"Yasuhiro","last_name":"Matsumoto","7":"Matsumoto","releases":[{"0":"963","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"ftpcmpl.vim","4":"ftpcmpl.vim","src_id":"2934","5":"2934","creation_date":"1081906521","6":"1081906521"}]},"962":{"script_id":"962","0":"962","script_name":"RemoteSaveAll.vim","1":"RemoteSaveAll.vim","script_type":"utility","2":"utility","summary":":RWALL[!] - save modified files in all running vim instances, also :WALL[!]","3":":RWALL[!] - save modified files in all running vim instances, also :WALL[!]","description":"(1)  This script (plugin) defines command :RWALL which saves all modified files in all running vim instances. Command takes no arguments. Bang can be used (:RWALL!) in which case the command which is sent to all running vims is :wall!. Without bang, the command which is sent to all running vims is :wall.\r\n\r\nLocal vim is also saved.\r\n\r\n\"All running vim instances\" include only servername-enabled vims. Vim instances with servername disabled will not be saved. :RWALL\/:WALL uses vim clientserver feature to execute \":wall[!]\" command in other running vims.\r\n\r\nSynonym :WALL is set equivalent to :RWALL\r\n\r\n(2) To do this from shell (to signal all running vims to save their modified file)\r\nyou can use either one of the following shell scripts:\r\n\r\n(2a) Shell script RWALL.sh -- requires that RemoteSaveAll.vim be installed\r\n\r\n#!\/bin\/sh\r\n# Description: save  modified files in all running vims\r\n# this script requires that plugin RemoteSaveAll.vim be installed\r\n# in the plugin directory\r\nvim -c 'RWALL' -c 'q!'\r\n\r\n(2b) Shell script savevims.sh -- does not require RemoteSaveAll.vim plugin\r\n\r\n#!\/bin\/sh\r\n# Description: save  modified files in all running vims\r\nfor srv in `vim --serverlist`; do\r\n    vim --servername \"$srv\" --remote_send '<C-\\><C-N>:wall<CR>'\r\ndone\r\n\r\n(3) To check that your running vims are 'servername-enabled' and can be remotely saved, do:\r\n          vim --serverlist \r\nat shell prompt, or\r\n          :echo serverlist()\r\nin vim. If nothing is printed, then no running vims are detected.\r\n","4":"(1)  This script (plugin) defines command :RWALL which saves all modified files in all running vim instances. Command takes no arguments. Bang can be used (:RWALL!) in which case the command which is sent to all running vims is :wall!. Without bang, the command which is sent to all running vims is :wall.\r\n\r\nLocal vim is also saved.\r\n\r\n\"All running vim instances\" include only servername-enabled vims. Vim instances with servername disabled will not be saved. :RWALL\/:WALL uses vim clientserver feature to execute \":wall[!]\" command in other running vims.\r\n\r\nSynonym :WALL is set equivalent to :RWALL\r\n\r\n(2) To do this from shell (to signal all running vims to save their modified file)\r\nyou can use either one of the following shell scripts:\r\n\r\n(2a) Shell script RWALL.sh -- requires that RemoteSaveAll.vim be installed\r\n\r\n#!\/bin\/sh\r\n# Description: save  modified files in all running vims\r\n# this script requires that plugin RemoteSaveAll.vim be installed\r\n# in the plugin directory\r\nvim -c 'RWALL' -c 'q!'\r\n\r\n(2b) Shell script savevims.sh -- does not require RemoteSaveAll.vim plugin\r\n\r\n#!\/bin\/sh\r\n# Description: save  modified files in all running vims\r\nfor srv in `vim --serverlist`; do\r\n    vim --servername \"$srv\" --remote_send '<C-\\><C-N>:wall<CR>'\r\ndone\r\n\r\n(3) To check that your running vims are 'servername-enabled' and can be remotely saved, do:\r\n          vim --serverlist \r\nat shell prompt, or\r\n          :echo serverlist()\r\nin vim. If nothing is printed, then no running vims are detected.\r\n","install_details":"Copy the file RemoteSaveAll.vim into your personal plugin directory (~\/.vim\/plugin).\r\n","5":"Copy the file RemoteSaveAll.vim into your personal plugin directory (~\/.vim\/plugin).\r\n","first_name":"Yakov","6":"Yakov","last_name":"Lerner","7":"Lerner","releases":[{"0":"962","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"RemoteSaveAll.vim","4":"RemoteSaveAll.vim","src_id":"2933","5":"2933","creation_date":"1081777175","6":"1081777175"}]},"961":{"script_id":"961","0":"961","script_name":"DumpStr.vim","1":"DumpStr.vim","script_type":"utility","2":"utility","summary":"dump vimscript string to clearly see multi-byte chars, bytes, and codes of both","3":"dump vimscript string to clearly see multi-byte chars, bytes, and codes of both","description":"When debugging vimscript, you sometimes need to clearly see what's inside the string value: which unprintable characters it contains ? Does it contain any multibyte chars ? In which positions ?\r\n\r\nFor buffer characters, you can use 'ga' to see them clearly. To see characters of strings (variables, registers etc),  you can use DumpStr.vim.\r\n\r\nUsage: \r\n  - :source DumpStr.vim \r\n  - :call TestDumpStr()        \" test\/demo\r\n  - :call DumpStr(string_variable)\r\n  - :call DumpStr(@Register)\r\n\r\nWhen string has multi-byte characters, DumpStr prints in following format:\r\n\r\nString length:   M bytes, N chars\r\n                   (string has multibyte characters) ( encoding=ENC )\r\nChar dump:       decimalCode(char) ...\r\nBytes:          \"...\"\r\nByte dump:       decimalCode(byte) ....\r\n\r\nWhen string has no multi-byte characters, DumpStr dumps in this format:\r\n\r\nString length:   M bytes (no multibyte characters) ( encoding=ENC )\r\nBytes:          \"...\"\r\nByte dump:       decimalCode(byte) ....\r\n\r\n","4":"When debugging vimscript, you sometimes need to clearly see what's inside the string value: which unprintable characters it contains ? Does it contain any multibyte chars ? In which positions ?\r\n\r\nFor buffer characters, you can use 'ga' to see them clearly. To see characters of strings (variables, registers etc),  you can use DumpStr.vim.\r\n\r\nUsage: \r\n  - :source DumpStr.vim \r\n  - :call TestDumpStr()        \" test\/demo\r\n  - :call DumpStr(string_variable)\r\n  - :call DumpStr(@Register)\r\n\r\nWhen string has multi-byte characters, DumpStr prints in following format:\r\n\r\nString length:   M bytes, N chars\r\n                   (string has multibyte characters) ( encoding=ENC )\r\nChar dump:       decimalCode(char) ...\r\nBytes:          \"...\"\r\nByte dump:       decimalCode(byte) ....\r\n\r\nWhen string has no multi-byte characters, DumpStr dumps in this format:\r\n\r\nString length:   M bytes (no multibyte characters) ( encoding=ENC )\r\nBytes:          \"...\"\r\nByte dump:       decimalCode(byte) ....\r\n\r\n","install_details":"","5":"","first_name":"Yakov","6":"Yakov","last_name":"Lerner","7":"Lerner","releases":[{"0":"961","vim_version":"6.0","1":"6.0","script_version":"0.5","2":"0.5","version_comment":"Initial upload","3":"Initial upload","package":"DumpStr.vim","4":"DumpStr.vim","src_id":"2931","5":"2931","creation_date":"1081699480","6":"1081699480"}]},"960":{"script_id":"960","0":"960","script_name":"replace","1":"replace","script_type":"utility","2":"utility","summary":"quick replacing of expressions","3":"quick replacing of expressions","description":"Vim plugin that asks the user for a string to replace, as well as the string he wants to replace with. By default, the script is called by the <F4> shortcut.\n","4":"Vim plugin that asks the user for a string to replace, as well as the string he wants to replace with. By default, the script is called by the <F4> shortcut.\n","install_details":"To install it, simply copy the script to $HOME\/.vim\/plugin.\n","5":"To install it, simply copy the script to $HOME\/.vim\/plugin.\n","first_name":"Helder","6":"Helder","last_name":"Correia","7":"Correia","releases":[{"0":"960","vim_version":"6.0","1":"6.0","script_version":"2004.0","2":"2004.0","version_comment":"Initial upload","3":"Initial upload","package":"replace.vim","4":"replace.vim","src_id":"2928","5":"2928","creation_date":"1081525781","6":"1081525781"}]},"959":{"script_id":"959","0":"959","script_name":"latex_pt","1":"latex_pt","script_type":"utility","2":"utility","summary":"replaces LaTeX portuguese codes by the real characters and vice-versa","3":"replaces LaTeX portuguese codes by the real characters and vice-versa","description":"Replaces LaTeX portuguese codes by the real characters when the user opens a LaTeX source document. When the user saves the document, the special characters are written back in LaTeX code form. Some characters like '\u00c3\u00ae' and '\u00c3\u00b2' don't exist in portuguese but they are handled as well.\n","4":"Replaces LaTeX portuguese codes by the real characters when the user opens a LaTeX source document. When the user saves the document, the special characters are written back in LaTeX code form. Some characters like '\u00c3\u00ae' and '\u00c3\u00b2' don't exist in portuguese but they are handled as well.\n","install_details":"Read the script for information on this topic.\n","5":"Read the script for information on this topic.\n","first_name":"Helder","6":"Helder","last_name":"Correia","7":"Correia","releases":[{"0":"959","vim_version":"6.0","1":"6.0","script_version":"2004.0","2":"2004.0","version_comment":"Initial upload","3":"Initial upload","package":"latex_pt.vim","4":"latex_pt.vim","src_id":"2924","5":"2924","creation_date":"1081431925","6":"1081431925"}]},"958":{"script_id":"958","0":"958","script_name":"blugrine","1":"blugrine","script_type":"color scheme","2":"color scheme","summary":"based on bluegreen colorscheme by Joao Estevao","3":"based on bluegreen colorscheme by Joao Estevao","description":"blue, green and white are the main colors over a black background\n","4":"blue, green and white are the main colors over a black background\n","install_details":"copy the script to $HOME\/.vim\/colors\/\n","5":"copy the script to $HOME\/.vim\/colors\/\n","first_name":"Helder","6":"Helder","last_name":"Correia","7":"Correia","releases":[{"0":"958","vim_version":"6.0","1":"6.0","script_version":"2004.0","2":"2004.0","version_comment":"Initial upload","3":"Initial upload","package":"blugrine.vim","4":"blugrine.vim","src_id":"2923","5":"2923","creation_date":"1081415840","6":"1081415840"}]},"957":{"script_id":"957","0":"957","script_name":"YAPosting","1":"YAPosting","script_type":"utility","2":"utility","summary":"Yet Another Posting script","3":"Yet Another Posting script","description":"This script was designed in order to have a simple but reliable, comprehensive and reusable set of mappings, functions and syntax in order to improve the Mailing and Posting edition. It does 'clean' the quotes in the mail (removes empty quoted lines, condense quote signs and remove signature), it changes Microsoft Outlook Express quote header to a standard quote header and put the quote where it belongs, it can remove quoted or not quoted paragraphs and it can reformat your text into a justified text inside margins.\r\n\r\nThe script has been totally rewritten for version 2.0, with a python backend written  from scratch to replace the Perl Text::Format module.\r\n\r\nNow the main page of this script is: https:\/\/github.com\/guyzmo\/vim-yaposting\r\n\r\nTo install it, the script is Vundle\/Pathogen ready.\r\n         \r\nNB: This script offers a similar, yet different way to Justify a text than : vimscript #177\r\n\r\nHave fun!","4":"This script was designed in order to have a simple but reliable, comprehensive and reusable set of mappings, functions and syntax in order to improve the Mailing and Posting edition. It does 'clean' the quotes in the mail (removes empty quoted lines, condense quote signs and remove signature), it changes Microsoft Outlook Express quote header to a standard quote header and put the quote where it belongs, it can remove quoted or not quoted paragraphs and it can reformat your text into a justified text inside margins.\r\n\r\nThe script has been totally rewritten for version 2.0, with a python backend written  from scratch to replace the Perl Text::Format module.\r\n\r\nNow the main page of this script is: https:\/\/github.com\/guyzmo\/vim-yaposting\r\n\r\nTo install it, the script is Vundle\/Pathogen ready.\r\n         \r\nNB: This script offers a similar, yet different way to Justify a text than : vimscript #177\r\n\r\nHave fun!","install_details":"You need to have vim compiled against Python >=2.6 installed.\r\nYou can install it by adding Bundle('guyzmo\/vim-yaposting') in your vimrc, if you use Vundle.\r\nOtherwise, the python module in pylibs shall go to your python path accessible from vim, and the vimscript file to ~\/.vim\/ftplugin\/mail\/","5":"You need to have vim compiled against Python >=2.6 installed.\r\nYou can install it by adding Bundle('guyzmo\/vim-yaposting') in your vimrc, if you use Vundle.\r\nOtherwise, the python module in pylibs shall go to your python path accessible from vim, and the vimscript file to ~\/.vim\/ftplugin\/mail\/","first_name":"Bernard","6":"Bernard","last_name":"PRATZ","7":"PRATZ","releases":[{"0":"957","vim_version":"7.2","1":"7.2","script_version":"2","2":"2","version_comment":"* rebuilt from scratch\r\n* switched to python backend\r\n* updated script for best Vundle compatibility\r\n* improved formatting features","3":"* rebuilt from scratch\r\n* switched to python backend\r\n* updated script for best Vundle compatibility\r\n* improved formatting features","package":"yaposting_v2.tar.gz","4":"yaposting_v2.tar.gz","src_id":"19664","5":"19664","creation_date":"1363714070","6":"1363714070"},{"0":"957","vim_version":"6.0","1":"6.0","script_version":"0.2","2":"0.2","version_comment":"* Added support for utf-8 encoded characters for the justify format feature\r\n* Added '<Lead>n' shortcut to add \"cut here\" marks :\r\n-----8<-----8<-----\r\n----->8----->8-----\r\n* Verified support for vim >7 (verified with 7.1) but shall work with older vims.\r\nTODO\r\n* Need to be improved to be more vim script compliant (better use of <Lead>, of function declaration, use of range etc...)\r\n* Need to have better support of typographic rules (don't add spaces around quotes for example when justifying the text)\r\n* Need to improve OE quote fixing rules...","3":"* Added support for utf-8 encoded characters for the justify format feature\r\n* Added '<Lead>n' shortcut to add \"cut here\" marks :\r\n-----8<-----8<-----\r\n----->8----->8-----\r\n* Verified support for vim >7 (verified with 7.1) but shall work with older vims.\r\nTODO\r\n* Need to be improved to be more vim script compliant (better use of <Lead>, of function declaration, use of range etc...)\r\n* Need to have better support of typographic rules (don't add spaces around quotes for example when justifying the text)\r\n* Need to improve OE quote fixing rules...","package":"yaposting.vim","4":"yaposting.vim","src_id":"15470","5":"15470","creation_date":"1303135316","6":"1303135316"},{"0":"957","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"yaposting.vim","4":"yaposting.vim","src_id":"2920","5":"2920","creation_date":"1081378675","6":"1081378675"}]},"956":{"script_id":"956","0":"956","script_name":"php-doc","1":"php-doc","script_type":"utility","2":"utility","summary":"Basic phpdoc support for vim.","3":"Basic phpdoc support for vim.","description":"This is based on a phpdoc.vim by Karl Heinz Marbaise <khmarbaise@gmx.de>.\r\n\r\nGo to http:\/\/www.phpcult.com\/vim\/ to see what it does, and for detailed instructions on how to use it. ","4":"This is based on a phpdoc.vim by Karl Heinz Marbaise <khmarbaise@gmx.de>.\r\n\r\nGo to http:\/\/www.phpcult.com\/vim\/ to see what it does, and for detailed instructions on how to use it. ","install_details":"put the file in your plugin path, or in your ~\/.vim\/\r\nmodify the .vimrc and say : \r\n\r\nsource ~\/.vim\/php-doc.vim\r\nmap <C-R> :exe PhpDoc()<CR>\r\nmap <C-F> :exe PhpDocVarBlock()<CR>\r\n\r\n\r\nAgain, go to http:\/\/www.phpcult.com\/vim\/ for more info. ","5":"put the file in your plugin path, or in your ~\/.vim\/\r\nmodify the .vimrc and say : \r\n\r\nsource ~\/.vim\/php-doc.vim\r\nmap <C-R> :exe PhpDoc()<CR>\r\nmap <C-F> :exe PhpDocVarBlock()<CR>\r\n\r\n\r\nAgain, go to http:\/\/www.phpcult.com\/vim\/ for more info. ","first_name":"Vid","6":"Vid","last_name":"Luther","7":"Luther","releases":[{"0":"956","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"php-doc.vim","4":"php-doc.vim","src_id":"2918","5":"2918","creation_date":"1081268612","6":"1081268612"}]},"955":{"script_id":"955","0":"955","script_name":"ToggleComment","1":"ToggleComment","script_type":"utility","2":"utility","summary":"Simple, flexibel, language-independent mappings to de-\/commentify","3":"Simple, flexibel, language-independent mappings to de-\/commentify","description":"This utility draws heavily from vimtip #271 and additional note 2002-07-06.\r\nYet it's different in one or more aspects from other tips and scripts I'm\r\naware off.\r\n\r\nFeatures:\r\n\r\n- de-\/commtify lines in normal mode (with count) and visual mode\r\n- use the same keys for commenting and decommenting\r\n- language independent, you define different mappings for various languages\r\n  and\/or one comment-command for different filetypes\r\n- simple and flexibel, to change the comment characters from '#' to '# ' e.g.,\r\n  just change a mapping in your .vimrc, not the script\r\n- comment-style: comments are indented like the uncommented line\r\n- no hlsearch problem, last search pattern and .-command are preserved\r\n- inserted comment characters are protected from further expansion\r\n- might be adapted to other comment styles (first column comments, ...)\r\n\r\nExample:\r\n\r\nCommented text looks like this:\r\n\r\n    #if uncommented:\r\n        \/* comment the line *\/\r\n    <!-- else: -->\r\n        \/\/ uncomment the\r\n        \/\/ lines\r\n        no comment\r\n\r\nYou would put or remove this comments (cursor on the first line), by typing:\r\n    ,# ,* ,< 2,\/\r\n","4":"This utility draws heavily from vimtip #271 and additional note 2002-07-06.\r\nYet it's different in one or more aspects from other tips and scripts I'm\r\naware off.\r\n\r\nFeatures:\r\n\r\n- de-\/commtify lines in normal mode (with count) and visual mode\r\n- use the same keys for commenting and decommenting\r\n- language independent, you define different mappings for various languages\r\n  and\/or one comment-command for different filetypes\r\n- simple and flexibel, to change the comment characters from '#' to '# ' e.g.,\r\n  just change a mapping in your .vimrc, not the script\r\n- comment-style: comments are indented like the uncommented line\r\n- no hlsearch problem, last search pattern and .-command are preserved\r\n- inserted comment characters are protected from further expansion\r\n- might be adapted to other comment styles (first column comments, ...)\r\n\r\nExample:\r\n\r\nCommented text looks like this:\r\n\r\n    #if uncommented:\r\n        \/* comment the line *\/\r\n    <!-- else: -->\r\n        \/\/ uncomment the\r\n        \/\/ lines\r\n        no comment\r\n\r\nYou would put or remove this comments (cursor on the first line), by typing:\r\n    ,# ,* ,< 2,\/\r\n","install_details":"Put the file ToggleComment.vim in your plugin directory or just copy\/paste\r\nthe two functions in your .vimrc file.\r\n\r\nThen define mappings in your .vimrc, like for example:\r\n\r\nmap ,# :call CommentLineToEnd('#')<CR>+\r\nmap ,* :call CommentLinePincer('\/* ', ' *\/')<CR>+\r\n\r\nand\/or map Meta-c (Alt-c) and Meta-Shift-C for different FileTypes.\r\n\r\nFor more detailed description and installation instructions see the README file.\r\n","5":"Put the file ToggleComment.vim in your plugin directory or just copy\/paste\r\nthe two functions in your .vimrc file.\r\n\r\nThen define mappings in your .vimrc, like for example:\r\n\r\nmap ,# :call CommentLineToEnd('#')<CR>+\r\nmap ,* :call CommentLinePincer('\/* ', ' *\/')<CR>+\r\n\r\nand\/or map Meta-c (Alt-c) and Meta-Shift-C for different FileTypes.\r\n\r\nFor more detailed description and installation instructions see the README file.\r\n","first_name":"Andreas","6":"Andreas","last_name":"V\u00c3\u00b6lter","7":"V\u00c3\u00b6lter","releases":[{"0":"955","vim_version":"6.0","1":"6.0","script_version":"1.6","2":"1.6","version_comment":"Initial upload","3":"Initial upload","package":"ToggleComment.tar","4":"ToggleComment.tar","src_id":"2917","5":"2917","creation_date":"1081243042","6":"1081243042"}]},"954":{"script_id":"954","0":"954","script_name":"xml2latex","1":"xml2latex","script_type":"utility","2":"utility","summary":"Convert XML files to LaTeX tabbing environment","3":"Convert XML files to LaTeX tabbing environment","description":"This script converts your XML files into a LaTeX tabbing environment, creating tab stops according to the max number of tabs on the file, changes the tab chars into \\> chat marking chars and put \\\\ on the end of all the lines of the XML file.\r\nI use it inside a \\begin{tt} \\end{tt} block here to get all my < and > chars converted correctly.\r\nIt's well known that the \\begin{verbatim} \\end{verbatim} does the trick, but I wrote this script because I need to apply some font changes (bold,tiny) on the XML code.","4":"This script converts your XML files into a LaTeX tabbing environment, creating tab stops according to the max number of tabs on the file, changes the tab chars into \\> chat marking chars and put \\\\ on the end of all the lines of the XML file.\r\nI use it inside a \\begin{tt} \\end{tt} block here to get all my < and > chars converted correctly.\r\nIt's well known that the \\begin{verbatim} \\end{verbatim} does the trick, but I wrote this script because I need to apply some font changes (bold,tiny) on the XML code.","install_details":"Just copy it to your ~\/.vim\/plugin directory and use ,x or :Xml2latex to convert your file.","5":"Just copy it to your ~\/.vim\/plugin directory and use ,x or :Xml2latex to convert your file.","first_name":"Eustaquio","6":"Eustaquio","last_name":"Rangel de Oliveira Jr.","7":"Rangel de Oliveira Jr.","releases":[{"0":"954","vim_version":"6.0","1":"6.0","script_version":"0.2","2":"0.2","version_comment":"I just changed the local vars with s: (hey, I didn't know about s:, it's my first script heheh). :-)","3":"I just changed the local vars with s: (hey, I didn't know about s:, it's my first script heheh). :-)","package":"xml2latex.vim","4":"xml2latex.vim","src_id":"2932","5":"2932","creation_date":"1081753505","6":"1081753505"},{"0":"954","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"xml2latex.vim","4":"xml2latex.vim","src_id":"2915","5":"2915","creation_date":"1081168112","6":"1081168112"}]},"953":{"script_id":"953","0":"953","script_name":"multiselect","1":"multiselect","script_type":"utility","2":"utility","summary":"Create multiple selections and operate","3":"Create multiple selections and operate","description":"This plugin extends the Vim's visual mode functionality by allowing you to\r\nselect non-contiguous regions and execute commands on them. It makes it really\r\neasy to select multiple regions using mouse, as you can use Ctrl+Mouse\r\ncombination just like in MS Word. There are a number of operations to very\r\neasily manipulate selections such as modifying the regions\r\n(add\/delete\/inverte\/clear), hiding, refreshing, saving and restoring etc. You\r\ncan execute both normal and :ex mode commands in one shot on all the regions.\r\nThe selections are also local to the buffer, so you can have separate selectins\r\nfor each buffer.\r\n\r\nUsage:\r\n\r\nOnce installed, the features are available in all the buffers. To create\r\nselection regions you can use mouse or keyboard.\r\n    - To use mouse, hold Ctrl key and make a visual selection using the\r\n      LeftMouse button just like you normally do. Once the mouse button is\r\n      released, the selection gets automatically added as a new selection\r\n      region. If you are selecting only one line, you can release the mouse\r\n      button without having to drag.\r\n    - To use keyboard, make a visual selection using |visual-mode| commands or\r\n      mouse and press <Enter> to create a new region out of it. The <Enter> (or\r\n      <CR>) key is mapped only if it is not already mapped in visual mode. The\r\n      cursor is placed in the direction of the selection such that it is easier\r\n      to continue moving the cursor for making further selections.\r\n    - To clear part or the whole of a region from selection, repeat the\r\n      same exact procedure over that region. You can however mix mouse and\r\n      keyboard usage. The procedure is equivalent to running the |:MSInvert|\r\n      command as describe in |multiselect-commands|.\r\n    - Once you repeat the procedure to create all the regions that you need to\r\n      act on, use one of the |:MSExecCmd| or |:MSExecNormalCmd| (or one of their\r\n      equivalent maps) to execute commands on them. Ex:\r\n        - Delete all the lines in the current selections >\r\n            MSExecCmd d\r\n        - Convert all the characters in the current selections to upper case. >\r\n            MSExecNormalCmd gU\r\n    - Use |:MSClear| (or its map) to clear the selection.\r\n\r\n\r\nWith the support of multiselect in other plugins, it becomes very useful. E.g., you can execute perfoce commands such as submitting files (using vimscript#240) on a group of selected files, using the multiselect support in selectbuf plugin (vimscript #107). It is possible to extend netrw plugin to support operations on multiple files too.\r\n\r\n\r\n\r\n\r\nSearch_key_words: multiselect multiple selection select selections mouse hari_vim Hari Krishna Dara","4":"This plugin extends the Vim's visual mode functionality by allowing you to\r\nselect non-contiguous regions and execute commands on them. It makes it really\r\neasy to select multiple regions using mouse, as you can use Ctrl+Mouse\r\ncombination just like in MS Word. There are a number of operations to very\r\neasily manipulate selections such as modifying the regions\r\n(add\/delete\/inverte\/clear), hiding, refreshing, saving and restoring etc. You\r\ncan execute both normal and :ex mode commands in one shot on all the regions.\r\nThe selections are also local to the buffer, so you can have separate selectins\r\nfor each buffer.\r\n\r\nUsage:\r\n\r\nOnce installed, the features are available in all the buffers. To create\r\nselection regions you can use mouse or keyboard.\r\n    - To use mouse, hold Ctrl key and make a visual selection using the\r\n      LeftMouse button just like you normally do. Once the mouse button is\r\n      released, the selection gets automatically added as a new selection\r\n      region. If you are selecting only one line, you can release the mouse\r\n      button without having to drag.\r\n    - To use keyboard, make a visual selection using |visual-mode| commands or\r\n      mouse and press <Enter> to create a new region out of it. The <Enter> (or\r\n      <CR>) key is mapped only if it is not already mapped in visual mode. The\r\n      cursor is placed in the direction of the selection such that it is easier\r\n      to continue moving the cursor for making further selections.\r\n    - To clear part or the whole of a region from selection, repeat the\r\n      same exact procedure over that region. You can however mix mouse and\r\n      keyboard usage. The procedure is equivalent to running the |:MSInvert|\r\n      command as describe in |multiselect-commands|.\r\n    - Once you repeat the procedure to create all the regions that you need to\r\n      act on, use one of the |:MSExecCmd| or |:MSExecNormalCmd| (or one of their\r\n      equivalent maps) to execute commands on them. Ex:\r\n        - Delete all the lines in the current selections >\r\n            MSExecCmd d\r\n        - Convert all the characters in the current selections to upper case. >\r\n            MSExecNormalCmd gU\r\n    - Use |:MSClear| (or its map) to clear the selection.\r\n\r\n\r\nWith the support of multiselect in other plugins, it becomes very useful. E.g., you can execute perfoce commands such as submitting files (using vimscript#240) on a group of selected files, using the multiselect support in selectbuf plugin (vimscript #107). It is possible to extend netrw plugin to support operations on multiple files too.\r\n\r\n\r\n\r\n\r\nSearch_key_words: multiselect multiple selection select selections mouse hari_vim Hari Krishna Dara","install_details":"Requires:  genutils (vimscript#197)\r\n- Extract the zip archives in to your runtime directory (.vim or vimfiles\r\n  under your HOME directory).\r\n- Start a new instance or go to an existing instance of vim.\r\n- Execute:\r\n    :helpt <your runtime directory>\/doc\r\n  This should generate the help tags for the selectbuf plugin help.\r\n- Type :help multiselect to read the help and finish configuration.\r\n\r\nFor version older than 2.0, you need to download the non-autoload versions of genutils and multvals (vimscript#171) plugins.","5":"Requires:  genutils (vimscript#197)\r\n- Extract the zip archives in to your runtime directory (.vim or vimfiles\r\n  under your HOME directory).\r\n- Start a new instance or go to an existing instance of vim.\r\n- Execute:\r\n    :helpt <your runtime directory>\/doc\r\n  This should generate the help tags for the selectbuf plugin help.\r\n- Type :help multiselect to read the help and finish configuration.\r\n\r\nFor version older than 2.0, you need to download the non-autoload versions of genutils and multvals (vimscript#171) plugins.","first_name":"Hari Krishna","6":"Hari Krishna","last_name":"Dara","7":"Dara","releases":[{"0":"953","vim_version":"7.0","1":"7.0","script_version":"2.2","2":"2.2","version_comment":"Changed public API to not autoload script. It doesn't make sense for\r\npublic API to load the script if it is not already loaded. This will\r\nalso cause problems when the plugin is disabled, but other plugins try\r\nto use it. ","3":"Changed public API to not autoload script. It doesn't make sense for\r\npublic API to load the script if it is not already loaded. This will\r\nalso cause problems when the plugin is disabled, but other plugins try\r\nto use it. ","package":"multiselect-2.2.zip","4":"multiselect-2.2.zip","src_id":"6162","5":"6162","creation_date":"1157995543","6":"1157995543"},{"0":"953","vim_version":"7.0","1":"7.0","script_version":"2.0","2":"2.0","version_comment":"- All the functionality has been rewritten to take advantage of new Vim7\r\n  features such as Lists. The programmatic API is not backwards compatible.\r\n- The plugin is now autoloaded, so it will not be (auto)loaded until you execute\r\n  the first mapping\/command. This will help improve the startup time of your Vim\r\n  session.\r\n- Misc. bug fixes have been fixed in the ares of |:MSInvert| and |:MSAdd|.\r\n- The g:multiselTmpMark is no longer required. The plugin now\r\n  uses getpos() and setpos() to avoid overwriting any user marks.\r\n- New setting |g:multiselQuickSelAdds|.\r\n- New commands |:MSMatchAddByDiffHlGroup| and |:MSVMatchAddByDiffHlGroup| to\r\n  select regions in a |vimdiff| window. ","3":"- All the functionality has been rewritten to take advantage of new Vim7\r\n  features such as Lists. The programmatic API is not backwards compatible.\r\n- The plugin is now autoloaded, so it will not be (auto)loaded until you execute\r\n  the first mapping\/command. This will help improve the startup time of your Vim\r\n  session.\r\n- Misc. bug fixes have been fixed in the ares of |:MSInvert| and |:MSAdd|.\r\n- The g:multiselTmpMark is no longer required. The plugin now\r\n  uses getpos() and setpos() to avoid overwriting any user marks.\r\n- New setting |g:multiselQuickSelAdds|.\r\n- New commands |:MSMatchAddByDiffHlGroup| and |:MSVMatchAddByDiffHlGroup| to\r\n  select regions in a |vimdiff| window. ","package":"multiselect-2.0.zip","4":"multiselect-2.0.zip","src_id":"6141","5":"6141","creation_date":"1157323930","6":"1157323930"},{"0":"953","vim_version":"6.0","1":"6.0","script_version":"1.3","2":"1.3","version_comment":"- New commands MSMatchAddBySynGroup and MSVMatchAddBySynGroup to select\r\n  lines automatically by their syntax group in a given range. Useful to\r\n  select all lines in comments (or more specifically perl pod) etc. and\r\n  do operations such as running a spell check on them.\r\n- New global function MSAddSelectionsByExpr() for creating new commands\r\n  such as MSMatchAddBySynGroup and MSMatchAdd by the user.\r\n","3":"- New commands MSMatchAddBySynGroup and MSVMatchAddBySynGroup to select\r\n  lines automatically by their syntax group in a given range. Useful to\r\n  select all lines in comments (or more specifically perl pod) etc. and\r\n  do operations such as running a spell check on them.\r\n- New global function MSAddSelectionsByExpr() for creating new commands\r\n  such as MSMatchAddBySynGroup and MSMatchAdd by the user.\r\n","package":"multiselect.vim","4":"multiselect.vim","src_id":"4040","5":"4040","creation_date":"1111085845","6":"1111085845"},{"0":"953","vim_version":"6.0","1":"6.0","script_version":"1.2","2":"1.2","version_comment":"- MSInvert command now works better.","3":"- MSInvert command now works better.","package":"multiselect.vim","4":"multiselect.vim","src_id":"3584","5":"3584","creation_date":"1098991200","6":"1098991200"},{"0":"953","vim_version":"6.0","1":"6.0","script_version":"1.1","2":"1.1","version_comment":"- Full support for mouse in making multiple selections. Works pretty\r\n  much like in MS word.\r\n- Improved behavior for MSInvert.\r\n\r\nGet the latest multvals.vim and genutils.vim plugins.","3":"- Full support for mouse in making multiple selections. Works pretty\r\n  much like in MS word.\r\n- Improved behavior for MSInvert.\r\n\r\nGet the latest multvals.vim and genutils.vim plugins.","package":"multiselect.vim","4":"multiselect.vim","src_id":"3568","5":"3568","creation_date":"1098293501","6":"1098293501"},{"0":"953","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"multiselect.vim","4":"multiselect.vim","src_id":"2911","5":"2911","creation_date":"1081099901","6":"1081099901"}]},"952":{"script_id":"952","0":"952","script_name":"psql.vim","1":"psql.vim","script_type":"color scheme","2":"color scheme","summary":"PostgreSQL hightlighting.","3":"PostgreSQL hightlighting.","description":"This sets up highlighting for *.psql files, which contain PostgreSQL SQL.\r\nYou may also need to make an entry for *.psql in your filetype.vim .","4":"This sets up highlighting for *.psql files, which contain PostgreSQL SQL.\r\nYou may also need to make an entry for *.psql in your filetype.vim .","install_details":"Instructions for a global install.\r\nAdd psql.vim to your syntax directory. (\/usr\/share\/vim\/vim61\/syntax\/ under RH 7.3, your install location may vary). \r\nThen add these two lines to filetype.vim\r\n\" PostgreSQL\r\nau BufNewFile,BufRead *.psql                    setf psql\r\n\r\nPlease report bugs and desired features.\r\nCurrently, most keywords  seem to work.","5":"Instructions for a global install.\r\nAdd psql.vim to your syntax directory. (\/usr\/share\/vim\/vim61\/syntax\/ under RH 7.3, your install location may vary). \r\nThen add these two lines to filetype.vim\r\n\" PostgreSQL\r\nau BufNewFile,BufRead *.psql                    setf psql\r\n\r\nPlease report bugs and desired features.\r\nCurrently, most keywords  seem to work.","first_name":"Devdas","6":"Devdas","last_name":"Bhagat","7":"Bhagat","releases":[{"0":"952","vim_version":"5.7","1":"5.7","script_version":"0.04","2":"0.04","version_comment":"Added procedural, trusted, language, handler and validator as keywords","3":"Added procedural, trusted, language, handler and validator as keywords","package":"psql.vim","4":"psql.vim","src_id":"2943","5":"2943","creation_date":"1082164327","6":"1082164327"},{"0":"952","vim_version":"5.7","1":"5.7","script_version":"0.03","2":"0.03","version_comment":"Added a few more keywords, colorised the mathematical operators.\r\nOperators will now be highlighted like functions instead of statements.","3":"Added a few more keywords, colorised the mathematical operators.\r\nOperators will now be highlighted like functions instead of statements.","package":"psql.vim","4":"psql.vim","src_id":"2916","5":"2916","creation_date":"1081174897","6":"1081174897"},{"0":"952","vim_version":"5.7","1":"5.7","script_version":"0.02","2":"0.02","version_comment":"Added support for aggregates and most functions. Right now, the functions are from 7.3.3, I will update to 7.4 later today, hopefully.\r\nThanks to David Fetter for coming up with a neat way to obtain the function listing.\r\npsql -E \\df\r\nAnother hint from David:\r\nset $PSQL_EDITOR to vim -c ':set ft=psql' to obtain the same highlighting in psql.\r\n\r\n","3":"Added support for aggregates and most functions. Right now, the functions are from 7.3.3, I will update to 7.4 later today, hopefully.\r\nThanks to David Fetter for coming up with a neat way to obtain the function listing.\r\npsql -E \\df\r\nAnother hint from David:\r\nset $PSQL_EDITOR to vim -c ':set ft=psql' to obtain the same highlighting in psql.\r\n\r\n","package":"psql.vim","4":"psql.vim","src_id":"2909","5":"2909","creation_date":"1080999218","6":"1080999218"},{"0":"952","vim_version":"5.7","1":"5.7","script_version":"0.01","2":"0.01","version_comment":"Initial upload","3":"Initial upload","package":"psql.vim","4":"psql.vim","src_id":"2908","5":"2908","creation_date":"1080995989","6":"1080995989"}]},"951":{"script_id":"951","0":"951","script_name":"aspnet.vim","1":"aspnet.vim","script_type":"syntax","2":"syntax","summary":"Provides ASP.NET syntax highlighting.","3":"Provides ASP.NET syntax highlighting.","description":"Provides ASP.NET syntax highlighting.  This is a modified version of the aspnet.vim file provided my Mark Feeney, to better handle a few things, such as the following:\r\n\r\n<img src=\"<%# DataBind.Eval(Container.DataItem, \"ImageFilePath\") %>\"\/>","4":"Provides ASP.NET syntax highlighting.  This is a modified version of the aspnet.vim file provided my Mark Feeney, to better handle a few things, such as the following:\r\n\r\n<img src=\"<%# DataBind.Eval(Container.DataItem, \"ImageFilePath\") %>\"\/>","install_details":"Copy this script to ~\/.vim\/syntax\r\nCreate the file ~\/.vim\/ftdetect\/aspnet.vim\r\n\r\n~\/.vim\/ftdetect\/aspnet.vim\r\n-------------------------------------\r\nau BufRead,BufNewFile *.aspx,*.asmx,*.ascx      set filetype=aspnet\r\n-------------------------------------","5":"Copy this script to ~\/.vim\/syntax\r\nCreate the file ~\/.vim\/ftdetect\/aspnet.vim\r\n\r\n~\/.vim\/ftdetect\/aspnet.vim\r\n-------------------------------------\r\nau BufRead,BufNewFile *.aspx,*.asmx,*.ascx      set filetype=aspnet\r\n-------------------------------------","first_name":"Stacey","6":"Stacey","last_name":"Abshire","7":"Abshire","releases":[{"0":"951","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"aspnet.vim","4":"aspnet.vim","src_id":"2906","5":"2906","creation_date":"1080927023","6":"1080927023"}]},"950":{"script_id":"950","0":"950","script_name":"af.vim","1":"af.vim","script_type":"color scheme","2":"color scheme","summary":"A nice dark color scheme with milk colors","3":"A nice dark color scheme with milk colors","description":"A nice dark color scheme with milk colors based on desert.","4":"A nice dark color scheme with milk colors based on desert.","install_details":"copy the theme to ~\/.vim\/colors\n:colorscheme af","5":"copy the theme to ~\/.vim\/colors\n:colorscheme af","first_name":"Stanislav","6":"Stanislav","last_name":"Lechev","7":"Lechev","releases":[{"0":"950","vim_version":"5.7","1":"5.7","script_version":"1.1","2":"1.1","version_comment":"Fixed scheme name in file...","3":"Fixed scheme name in file...","package":"af.vim","4":"af.vim","src_id":"2900","5":"2900","creation_date":"1080774850","6":"1080774850"}]},"949":{"script_id":"949","0":"949","script_name":"qf.vim","1":"qf.vim","script_type":"utility","2":"utility","summary":"Allow :grep to work with multiple programs","3":"Allow :grep to work with multiple programs","description":"This script is based fully on vimtip #688. It provides commands for manipulating vim's :grep command via grepprg and grepformat without loosing current settings. That is, all this package does is manipulate the settings of vim's grepprg and grepformat variables. Hopefully the package makes it possible to use multiple different progams in conjuctions with vim's built in grep command.  There is very little magic in the script...but it is convenient.\r\n\r\nThe basic command is :QF which allows any registered quick-fix command to be executed. \r\nE.g.  QF <id> <args> <-- finds the program corresponding to \"id\" in the\r\ntable and executes it with the specified arguments \"args\"\r\ne.g. :QF grep foobar *.cpp <-- will grep all cpp files for foobar\r\n\r\nAny number of grep like commands can be registered, and ad-hoc commands can be run also. Look at the bottom for the file for the complete list of commands. An look at the top of the file to work out how to register specific commands. Command registrations allows for less typing, nothing more.\r\n\r\nQFlid <pattern> <-- will search for pattern in the id-utils database\r\ne.g QFlid static   <-- will find all lines with the word \"static\" using GNU\r\nid-utils\r\n\r\nQFgrep <pattern> <files> <-- works just like the grep command\r\ne.g. :QFgrep static *.cpp <-- will find all lines matching \"static\" in the .cpp files of the current directory\r\n\r\n\r\nQFrgrep <pattern> <dir> <-- recursive grep\r\ne.g. :QFrgrep static src  <-- will recursively grep the src directory for all\r\nfiles containing static\r\n\r\n\r\nQFlocate <pattern> <-- will search for files in the slocate database\r\nE.g. :QFlocate pattern <-- will locate all files matching pattern via the\r\nslocate functionality available on linux and elsewhere\r\n\r\nQFfind <args> <-- works just like find\r\nE.g. QFfind . -name '*.cpp' <-- will find all cpp files under the current\r\ndirectory\r\n\r\nQFload Allows a saved Quick-fix window which was previously saved to be \r\nrestored\r\nE.g. :QFload \/tmp\/foo <-- will load contents of \/tmp\/foo into quick-fix buffer assuming \/tmp\/foo contains the contents of a previously save quick-fix buffer\r\n\r\n","4":"This script is based fully on vimtip #688. It provides commands for manipulating vim's :grep command via grepprg and grepformat without loosing current settings. That is, all this package does is manipulate the settings of vim's grepprg and grepformat variables. Hopefully the package makes it possible to use multiple different progams in conjuctions with vim's built in grep command.  There is very little magic in the script...but it is convenient.\r\n\r\nThe basic command is :QF which allows any registered quick-fix command to be executed. \r\nE.g.  QF <id> <args> <-- finds the program corresponding to \"id\" in the\r\ntable and executes it with the specified arguments \"args\"\r\ne.g. :QF grep foobar *.cpp <-- will grep all cpp files for foobar\r\n\r\nAny number of grep like commands can be registered, and ad-hoc commands can be run also. Look at the bottom for the file for the complete list of commands. An look at the top of the file to work out how to register specific commands. Command registrations allows for less typing, nothing more.\r\n\r\nQFlid <pattern> <-- will search for pattern in the id-utils database\r\ne.g QFlid static   <-- will find all lines with the word \"static\" using GNU\r\nid-utils\r\n\r\nQFgrep <pattern> <files> <-- works just like the grep command\r\ne.g. :QFgrep static *.cpp <-- will find all lines matching \"static\" in the .cpp files of the current directory\r\n\r\n\r\nQFrgrep <pattern> <dir> <-- recursive grep\r\ne.g. :QFrgrep static src  <-- will recursively grep the src directory for all\r\nfiles containing static\r\n\r\n\r\nQFlocate <pattern> <-- will search for files in the slocate database\r\nE.g. :QFlocate pattern <-- will locate all files matching pattern via the\r\nslocate functionality available on linux and elsewhere\r\n\r\nQFfind <args> <-- works just like find\r\nE.g. QFfind . -name '*.cpp' <-- will find all cpp files under the current\r\ndirectory\r\n\r\nQFload Allows a saved Quick-fix window which was previously saved to be \r\nrestored\r\nE.g. :QFload \/tmp\/foo <-- will load contents of \/tmp\/foo into quick-fix buffer assuming \/tmp\/foo contains the contents of a previously save quick-fix buffer\r\n\r\n","install_details":"Drop qf.vim into your plugin directory, or source it directly.","5":"Drop qf.vim into your plugin directory, or source it directly.","first_name":"Mike","6":"Mike","last_name":"Sharpe","7":"Sharpe","releases":[{"0":"949","vim_version":"6.0","1":"6.0","script_version":"1.1","2":"1.1","version_comment":"New commands from the original author of vimtip#688","3":"New commands from the original author of vimtip#688","package":"qf.vim","4":"qf.vim","src_id":"6834","5":"6834","creation_date":"1172998381","6":"1172998381"},{"0":"949","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"qf.vim","4":"qf.vim","src_id":"2892","5":"2892","creation_date":"1080596708","6":"1080596708"}]},"948":{"script_id":"948","0":"948","script_name":"Scons compiler plugin","1":"Scons compiler plugin","script_type":"utility","2":"utility","summary":"Compiler plugin for scons.","3":"Compiler plugin for scons.","description":"Replace autoconf\/automake with scons, and here is the compiler plugin to allow you to keep building and debugging from within vim.","4":"Replace autoconf\/automake with scons, and here is the compiler plugin to allow you to keep building and debugging from within vim.","install_details":"Just put it in your ~\/.vim\/compiler directory.","5":"Just put it in your ~\/.vim\/compiler directory.","first_name":"Michael","6":"Michael","last_name":"Brailsford","7":"Brailsford","releases":[{"0":"948","vim_version":"6.0","1":"6.0","script_version":"0.5","2":"0.5","version_comment":"Initial upload","3":"Initial upload","package":"scons.vim","4":"scons.vim","src_id":"2878","5":"2878","creation_date":"1080355038","6":"1080355038"}]},"947":{"script_id":"947","0":"947","script_name":"2tex.vim","1":"2tex.vim","script_type":"syntax","2":"syntax","summary":"Transform a file into TEX file, using the current syntax highlighting","3":"Transform a file into TEX file, using the current syntax highlighting","description":"This script is based on the script 2html.vim. It transforms a file into a TEX file using current highlighting, using the \"color\" latex package.\r\nSorry, the code is really bad, and this project is not maintained anymore.","4":"This script is based on the script 2html.vim. It transforms a file into a TEX file using current highlighting, using the \"color\" latex package.\r\nSorry, the code is really bad, and this project is not maintained anymore.","install_details":"put this script in ~\/.vim\/syntax\/2tex.vim","5":"put this script in ~\/.vim\/syntax\/2tex.vim","first_name":"Francois","6":"Francois","last_name":"Rigault","7":"Rigault","releases":[{"0":"947","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"add support for non-gui vim","3":"add support for non-gui vim","package":"2tex.vim","4":"2tex.vim","src_id":"2874","5":"2874","creation_date":"1080289924","6":"1080289924"}]},"946":{"script_id":"946","0":"946","script_name":"StyleChecker (+perl)","1":"StyleChecker (+perl)","script_type":"utility","2":"utility","summary":"Tool for finding and highlighting repeated words in file","3":"Tool for finding and highlighting repeated words in file","description":"\"      Repetition of words is sign of bad style in most languages. This script\n\"      will help to track repetition of words in LaTeX, HTML and mail files.\n\"\n\"      LaTeX: don't take into account \\keywords\n\"      HTML: don't highlight content of tags\n\"      Mail: don't look in quoted messages, headers and signatures \n\"\n\"      There is also support for any other filetype. StyleChecker will\n\"      highlight there only repeated words in comments.\n\"\n\"      This script requires Perl interface. Theoretically it could be done in\n\"      pure VimL but multiple iterations through long lists of words make it\n\"      practically impossible - vote for arrays in VimL!\n\"\n\" Installation:\n\"      Put this file into your .vim\/macros directory and source it from local\n\"      ftplugins. Of course you can place this file in .vim\/plugin directory\n\"      but this file will be sourced every time you open Vim.\n\"\n\" Usage:\n\"      Default shorcut for style checking is ,, . You can change it by placing\n\"      in .vimrc: \n\"            map <YourShortcut> <Plug>StyleChecker\n\"\n\"      After execution of map script will highlight repeated words.\n\"      Next execution of map restore original highlighting of file.\n\"      In console Vim offending words will be highlighted with 8 colors, in GUI\n\"      with 16. \n\"      Thanks to Perl's pragma locale, language specific letters will be\n\"      treated properly. \n\"\n\" Settings:\n\"      Behavior of StyleChecker you can control through variables. They are\n\"      Vim variables, there is no need to play with Perl.\n\" More about setting variables in file.","4":"\"      Repetition of words is sign of bad style in most languages. This script\n\"      will help to track repetition of words in LaTeX, HTML and mail files.\n\"\n\"      LaTeX: don't take into account \\keywords\n\"      HTML: don't highlight content of tags\n\"      Mail: don't look in quoted messages, headers and signatures \n\"\n\"      There is also support for any other filetype. StyleChecker will\n\"      highlight there only repeated words in comments.\n\"\n\"      This script requires Perl interface. Theoretically it could be done in\n\"      pure VimL but multiple iterations through long lists of words make it\n\"      practically impossible - vote for arrays in VimL!\n\"\n\" Installation:\n\"      Put this file into your .vim\/macros directory and source it from local\n\"      ftplugins. Of course you can place this file in .vim\/plugin directory\n\"      but this file will be sourced every time you open Vim.\n\"\n\" Usage:\n\"      Default shorcut for style checking is ,, . You can change it by placing\n\"      in .vimrc: \n\"            map <YourShortcut> <Plug>StyleChecker\n\"\n\"      After execution of map script will highlight repeated words.\n\"      Next execution of map restore original highlighting of file.\n\"      In console Vim offending words will be highlighted with 8 colors, in GUI\n\"      with 16. \n\"      Thanks to Perl's pragma locale, language specific letters will be\n\"      treated properly. \n\"\n\" Settings:\n\"      Behavior of StyleChecker you can control through variables. They are\n\"      Vim variables, there is no need to play with Perl.\n\" More about setting variables in file.","install_details":"\"      Put this file into your .vim\/macros directory and source it from local\n\"      ftplugins. Of course you can place this file in .vim\/plugin directory\n\"      but this file will be sourced every time you open Vim.","5":"\"      Put this file into your .vim\/macros directory and source it from local\n\"      ftplugins. Of course you can place this file in .vim\/plugin directory\n\"      but this file will be sourced every time you open Vim.","first_name":"Mikolaj","6":"Mikolaj","last_name":"Machowski","7":"Machowski","releases":[{"0":"946","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"stylechecker.vim","4":"stylechecker.vim","src_id":"2867","5":"2867","creation_date":"1080265492","6":"1080265492"}]},"945":{"script_id":"945","0":"945","script_name":"groovy.vim","1":"groovy.vim","script_type":"syntax","2":"syntax","summary":"syntax file for the groovy programming language","3":"syntax file for the groovy programming language","description":"Syntax file for the Groovy programming language. It relies on the java.vim syntax file.\r\nI was inspired by java.vim and ruby.vim syntax definition, so I thank the authors of those scripts.\r\n","4":"Syntax file for the Groovy programming language. It relies on the java.vim syntax file.\r\nI was inspired by java.vim and ruby.vim syntax definition, so I thank the authors of those scripts.\r\n","install_details":"1) copy the file in the (global or user's $HOME\/.vim\/syntax\/) syntax folder\r\n\r\n2) add this line to recognize groovy files by filename extension:\r\n  au BufNewFile,BufRead *.groovy  setf groovy\r\n\r\n  in the global vim filetype.vim file or inside $HOME\/.vim\/filetype.vim\r\n  [groovy is still not recognized by vim! :-( ]\r\n\r\n3) add this part to recognize by content groovy script (no extension needed :-)\r\n  if did_filetype()\r\n    finish\r\n  endif\r\n  if getline(1) =~ '^#!.*[\/\\\\]groovy\\>'\r\n    setf groovy\r\n  endif\r\n\r\n  in the global scripts.vim file or in $HOME\/.vim\/scripts.vim\r\n\r\n\r\n 4) open\/write a .groovy file or a groovy script :-)\r\n","5":"1) copy the file in the (global or user's $HOME\/.vim\/syntax\/) syntax folder\r\n\r\n2) add this line to recognize groovy files by filename extension:\r\n  au BufNewFile,BufRead *.groovy  setf groovy\r\n\r\n  in the global vim filetype.vim file or inside $HOME\/.vim\/filetype.vim\r\n  [groovy is still not recognized by vim! :-( ]\r\n\r\n3) add this part to recognize by content groovy script (no extension needed :-)\r\n  if did_filetype()\r\n    finish\r\n  endif\r\n  if getline(1) =~ '^#!.*[\/\\\\]groovy\\>'\r\n    setf groovy\r\n  endif\r\n\r\n  in the global scripts.vim file or in $HOME\/.vim\/scripts.vim\r\n\r\n\r\n 4) open\/write a .groovy file or a groovy script :-)\r\n","first_name":"Alessio","6":"Alessio","last_name":"Pace","7":"Pace","releases":[{"0":"945","vim_version":"6.0","1":"6.0","script_version":"0.1.9b","2":"0.1.9b","version_comment":"groovy's specific classes highlighted separatly from java's (if enabled)","3":"groovy's specific classes highlighted separatly from java's (if enabled)","package":"groovy.vim","4":"groovy.vim","src_id":"2926","5":"2926","creation_date":"1081465675","6":"1081465675"},{"0":"945","vim_version":"6.0","1":"6.0","script_version":"0.1.9","2":"0.1.9","version_comment":"-scripts does not depend at runtime from java.vim;\r\n-highlight for ${params} in strings","3":"-scripts does not depend at runtime from java.vim;\r\n-highlight for ${params} in strings","package":"groovy.vim","4":"groovy.vim","src_id":"2907","5":"2907","creation_date":"1080976421","6":"1080976421"},{"0":"945","vim_version":"6.0","1":"6.0","script_version":"0.1.7","2":"0.1.7","version_comment":"Attempts to recognize all the groovy methods at: http:\/\/groovy.codehaus.org\/groovy-jdk.html","3":"Attempts to recognize all the groovy methods at: http:\/\/groovy.codehaus.org\/groovy-jdk.html","package":"groovy.vim","4":"groovy.vim","src_id":"2896","5":"2896","creation_date":"1080638215","6":"1080638215"},{"0":"945","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"groovy.vim","4":"groovy.vim","src_id":"2864","5":"2864","creation_date":"1080213522","6":"1080213522"}]},"944":{"script_id":"944","0":"944","script_name":"n3.vim","1":"n3.vim","script_type":"syntax","2":"syntax","summary":"RDF Notation 3 Syntax File","3":"RDF Notation 3 Syntax File","description":"This is a syntax file to highlight Notation 3 documents for describing RDF (meta-)data.\r\n\r\nIt handles basic highlighting, but has not currently any complex error detecting features (e.g. for non-closed statements etc), nor any fold regions defined.\r\n\r\nAbout Notation 3 (excerpt from: http:\/\/www.w3.org\/DesignIssues\/Notation3.html):\r\n\r\n\"This is a langauge which is a compact and readable alternative to RDF's XML syntax, but also is extended to allow greater expressiveness.\"\r\n\r\nThat said, download this and see if it helps you in semantic endeavours.\r\n\r\nComments, suggestions and assistance are all welcome!\r\n","4":"This is a syntax file to highlight Notation 3 documents for describing RDF (meta-)data.\r\n\r\nIt handles basic highlighting, but has not currently any complex error detecting features (e.g. for non-closed statements etc), nor any fold regions defined.\r\n\r\nAbout Notation 3 (excerpt from: http:\/\/www.w3.org\/DesignIssues\/Notation3.html):\r\n\r\n\"This is a langauge which is a compact and readable alternative to RDF's XML syntax, but also is extended to allow greater expressiveness.\"\r\n\r\nThat said, download this and see if it helps you in semantic endeavours.\r\n\r\nComments, suggestions and assistance are all welcome!\r\n","install_details":"Drop in your syntax directory (\"~\/.vim\/syntax\/\" on unix-style systems).\r\n\r\nTo add as a filetype, add this in your \"~\/.vim\/filetype.vim\":\r\n    \" RDF Notation 3 Syntax\r\n    augroup filetypedetect\r\n        au BufNewFile,BufRead *.n3  setfiletype n3\r\n    augroup END\r\n\r\nSee also the built-in help in Vim:\r\n    :help mysyntaxfile\r\n    :help usr_43.txt\r\n","5":"Drop in your syntax directory (\"~\/.vim\/syntax\/\" on unix-style systems).\r\n\r\nTo add as a filetype, add this in your \"~\/.vim\/filetype.vim\":\r\n    \" RDF Notation 3 Syntax\r\n    augroup filetypedetect\r\n        au BufNewFile,BufRead *.n3  setfiletype n3\r\n    augroup END\r\n\r\nSee also the built-in help in Vim:\r\n    :help mysyntaxfile\r\n    :help usr_43.txt\r\n","first_name":"Niklas","6":"Niklas","last_name":"Lindstr\u00c3\u00b6m","7":"Lindstr\u00c3\u00b6m","releases":[{"0":"944","vim_version":"6.0","1":"6.0","script_version":"1.1","2":"1.1","version_comment":"Highlighting \"ClassNames\" and \"propertyNames\" separately.","3":"Highlighting \"ClassNames\" and \"propertyNames\" separately.","package":"n3.vim","4":"n3.vim","src_id":"6882","5":"6882","creation_date":"1174015255","6":"1174015255"},{"0":"944","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"n3.vim","4":"n3.vim","src_id":"2858","5":"2858","creation_date":"1080063437","6":"1080063437"}]},"943":{"script_id":"943","0":"943","script_name":"ProjectBrowse","1":"ProjectBrowse","script_type":"utility","2":"utility","summary":"Browse a list of files below a root directory","3":"Browse a list of files below a root directory","description":"Generate a list of files below a set of root directories for rapidly finding and editing medium sized source trees. Intended for moderate sized programming projects with several thousand header and source files, but will be useful to anyone editing large numbers of files in a structured directory layout. ( e.g.: websites, config files, etc )\r\n\r\nThe file list can be set to appear either in a new buffer or in the local buffer. Place the cursor on the line of the file of interest and hit return. Although searching may be done in any way, the suggested usage is the \/ ( slash search ) command. The buffer is set locally to be case insensitive and not use highlighting. Press \/ and then type the first few characters of the file of interest followed by return ( twice ).\r\n\r\nI created this script in response to the browser that ships with the popular Visual Assist program by Whole Tomato Software for MS Visual .NET. I prefer to use vim for all my editing and ctags is great, but when you have another developer telling you to \"Go to file SomeWierdFileDeepInTheDirectoryStructure.cpp\" it can be pretty slow and painful sometimes. This browser solves that problem directly.\r\n\r\nThis script has been under nearly daily usage by myself and several others. Now it has been highly optimized to cache the search results to a file. Special thanks to Steven An.\r\n\r\nPlease feel free to email me with bugs or feature requests, or just if you like it. I am required to use gvim and .NET extensively, so i am interested in additional features or tips that you want to see.\r\n","4":"Generate a list of files below a set of root directories for rapidly finding and editing medium sized source trees. Intended for moderate sized programming projects with several thousand header and source files, but will be useful to anyone editing large numbers of files in a structured directory layout. ( e.g.: websites, config files, etc )\r\n\r\nThe file list can be set to appear either in a new buffer or in the local buffer. Place the cursor on the line of the file of interest and hit return. Although searching may be done in any way, the suggested usage is the \/ ( slash search ) command. The buffer is set locally to be case insensitive and not use highlighting. Press \/ and then type the first few characters of the file of interest followed by return ( twice ).\r\n\r\nI created this script in response to the browser that ships with the popular Visual Assist program by Whole Tomato Software for MS Visual .NET. I prefer to use vim for all my editing and ctags is great, but when you have another developer telling you to \"Go to file SomeWierdFileDeepInTheDirectoryStructure.cpp\" it can be pretty slow and painful sometimes. This browser solves that problem directly.\r\n\r\nThis script has been under nearly daily usage by myself and several others. Now it has been highly optimized to cache the search results to a file. Special thanks to Steven An.\r\n\r\nPlease feel free to email me with bugs or feature requests, or just if you like it. I am required to use gvim and .NET extensively, so i am interested in additional features or tips that you want to see.\r\n","install_details":"REQUIRES: the unix find command. The script assumes that find is in your path, but you can set the direct path to the directory explicitly. See s:find_path var.\r\n\r\nRecommended mapping: use alt-o to open the browser. put this in your .vimrc\r\nmap <A-o> :ProjectBrowseCached<CR>\r\nmap <A-O> :ProjectBrowse c:\\Projects\\ c:\\Libraries c:\\Includes<CR>\r\n\r\nThe first command will open the cached file list. The second (shift-O) will refresh the list with new files.\r\n\r\ns:filter var defaults to nothing. set it to only include cpp and header files, etc.\r\n\r\ns:splitBehavior default to none. set it to vert or horiz to open the browser in a new buffer.","5":"REQUIRES: the unix find command. The script assumes that find is in your path, but you can set the direct path to the directory explicitly. See s:find_path var.\r\n\r\nRecommended mapping: use alt-o to open the browser. put this in your .vimrc\r\nmap <A-o> :ProjectBrowseCached<CR>\r\nmap <A-O> :ProjectBrowse c:\\Projects\\ c:\\Libraries c:\\Includes<CR>\r\n\r\nThe first command will open the cached file list. The second (shift-O) will refresh the list with new files.\r\n\r\ns:filter var defaults to nothing. set it to only include cpp and header files, etc.\r\n\r\ns:splitBehavior default to none. set it to vert or horiz to open the browser in a new buffer.","first_name":"Jon","6":"Jon","last_name":"Heiner","7":"Heiner","releases":[{"0":"943","vim_version":"6.0","1":"6.0","script_version":"1.2","2":"1.2","version_comment":"Now caches the list of files in your project, making this an extraordinarily fast way to access medium sized source trees. This plugin has been under considerable use over the past few years and is quite robust. Special thanks to Steven An for adding the caching.","3":"Now caches the list of files in your project, making this an extraordinarily fast way to access medium sized source trees. This plugin has been under considerable use over the past few years and is quite robust. Special thanks to Steven An for adding the caching.","package":"projectbrowse.vim","4":"projectbrowse.vim","src_id":"6725","5":"6725","creation_date":"1170800267","6":"1170800267"},{"0":"943","vim_version":"6.0","1":"6.0","script_version":"1.1","2":"1.1","version_comment":"Better usability for opening in current buffer. Will prompt for save if local buffer is modified. Will hide current buffer if modified and not saved. Various cleanup.","3":"Better usability for opening in current buffer. Will prompt for save if local buffer is modified. Will hide current buffer if modified and not saved. Various cleanup.","package":"projectbrowse.vim","4":"projectbrowse.vim","src_id":"4943","5":"4943","creation_date":"1136388090","6":"1136388090"},{"0":"943","vim_version":"6.0","1":"6.0","script_version":"1.0a","2":"1.0a","version_comment":"Initial upload","3":"Initial upload","package":"projectbrowse.vim","4":"projectbrowse.vim","src_id":"2857","5":"2857","creation_date":"1080059757","6":"1080059757"}]},"942":{"script_id":"942","0":"942","script_name":"pqmagic.vim","1":"pqmagic.vim","script_type":"syntax","2":"syntax","summary":"Syntax Highlighting for \"PowerQuest PartitionMagic 7 Pro Scripting Files\"","3":"Syntax Highlighting for \"PowerQuest PartitionMagic 7 Pro Scripting Files\"","description":"Syntax Highlighting for \"PowerQuest PartitionMagic 7 Pro Scripting Files\"","4":"Syntax Highlighting for \"PowerQuest PartitionMagic 7 Pro Scripting Files\"","install_details":"Copy the file to your vimfile\/syntax directory.\r\n\r\nAdd the following line to your filetype.vim:\r\n\r\naugroup filetypedetect\r\n\" PowerQuest PartitionMagic Pro Script File\r\nau BufNewFile,BufRead *.pqs\t\t\t\tsetf pqmagic\r\naugroup END","5":"Copy the file to your vimfile\/syntax directory.\r\n\r\nAdd the following line to your filetype.vim:\r\n\r\naugroup filetypedetect\r\n\" PowerQuest PartitionMagic Pro Script File\r\nau BufNewFile,BufRead *.pqs\t\t\t\tsetf pqmagic\r\naugroup END","first_name":"G\u00c3\u00bcnther","6":"G\u00c3\u00bcnther","last_name":"Pfannhauser","7":"Pfannhauser","releases":[{"0":"942","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"pqmagic.vim","4":"pqmagic.vim","src_id":"2855","5":"2855","creation_date":"1080031853","6":"1080031853"}]},"941":{"script_id":"941","0":"941","script_name":"edifact.vim","1":"edifact.vim","script_type":"syntax","2":"syntax","summary":"Syntax script for generic EDIFACT messages (extensible)","3":"Syntax script for generic EDIFACT messages (extensible)","description":"This syntax script will colorize UN\/EDIFACT messages.\r\nAll formatting errors are reported with the \"Error\" highlighting.\r\n\r\nHooks are provided for extensibility (including EDIFACT messages in another syntax) and to define a more specific syntax (coloring known tags, checking segment definitions with mandatory\/conditionnal data...).\r\n\r\n\r\nFor more information about EDIFACT:\r\n- http:\/\/www.unece.org\/trade\/untdid\/\r\n- http:\/\/www.gefeg.com\/jswg\/index.htm","4":"This syntax script will colorize UN\/EDIFACT messages.\r\nAll formatting errors are reported with the \"Error\" highlighting.\r\n\r\nHooks are provided for extensibility (including EDIFACT messages in another syntax) and to define a more specific syntax (coloring known tags, checking segment definitions with mandatory\/conditionnal data...).\r\n\r\n\r\nFor more information about EDIFACT:\r\n- http:\/\/www.unece.org\/trade\/untdid\/\r\n- http:\/\/www.gefeg.com\/jswg\/index.htm","install_details":"Drop into your personnal syntax directory: $HOME\/{.vim|vimfiles}\/syntax ({Unix|Windows}).\r\n\r\nTo manually colorize a file:\r\n  :syntax on\r\n  :set syntax=edifact\r\n\r\nTo assign edifact syntax to files, add this to your ~\/{.vim|vimfiles}\/filetype.vim:\r\n  augroup filetypedetect\r\n    au! BufNewFile,BufRead *.edifact,*.edi,*.EDIFACT,*.EDI set filetype=edifact\r\n  augroup END\r\n\r\nSee also the built-in help in Vim:\r\n    :help 'filetype'\r\n    :help mysyntaxfile\r\n    :help filetype-plugin\r\n","5":"Drop into your personnal syntax directory: $HOME\/{.vim|vimfiles}\/syntax ({Unix|Windows}).\r\n\r\nTo manually colorize a file:\r\n  :syntax on\r\n  :set syntax=edifact\r\n\r\nTo assign edifact syntax to files, add this to your ~\/{.vim|vimfiles}\/filetype.vim:\r\n  augroup filetypedetect\r\n    au! BufNewFile,BufRead *.edifact,*.edi,*.EDIFACT,*.EDI set filetype=edifact\r\n  augroup END\r\n\r\nSee also the built-in help in Vim:\r\n    :help 'filetype'\r\n    :help mysyntaxfile\r\n    :help filetype-plugin\r\n","first_name":"Olivier","6":"Olivier","last_name":"Mengu\u00c3\u00a9","7":"Mengu\u00c3\u00a9","releases":[{"0":"941","vim_version":"6.0","1":"6.0","script_version":"2.0","2":"2.0","version_comment":"Improved error reporting to ease editing:\r\n- unclosed segments\r\n- invalid text between segments\r\n- error stops at the next quote, which may be just before the beginning of a\r\nvalid segment\r\nRenamed edifactStar  to edifactAsterisk, edifactQuote to edifactApostrophe to\r\nuse the same terms as in the standards.\r\nImproved grammar with @edifactSegmentHook to plug more specific segment definition.\r\nAdded 'keepend' to edifactSegment.\r\nAdded sample parsing for TXT segment that checks data element lengths.\r\nDid tests of derived syntax reusing this syntax.","3":"Improved error reporting to ease editing:\r\n- unclosed segments\r\n- invalid text between segments\r\n- error stops at the next quote, which may be just before the beginning of a\r\nvalid segment\r\nRenamed edifactStar  to edifactAsterisk, edifactQuote to edifactApostrophe to\r\nuse the same terms as in the standards.\r\nImproved grammar with @edifactSegmentHook to plug more specific segment definition.\r\nAdded 'keepend' to edifactSegment.\r\nAdded sample parsing for TXT segment that checks data element lengths.\r\nDid tests of derived syntax reusing this syntax.","package":"edifact.vim","4":"edifact.vim","src_id":"2862","5":"2862","creation_date":"1080192400","6":"1080192400"},{"0":"941","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"edifact.vim","4":"edifact.vim","src_id":"2851","5":"2851","creation_date":"1079972477","6":"1079972477"}]},"940":{"script_id":"940","0":"940","script_name":"screen.vim","1":"screen.vim","script_type":"utility","2":"utility","summary":"screen-like keybindings for buffers and windows","3":"screen-like keybindings for buffers and windows","description":"This plugin provides screen-like keybindings for common window or buffer movements.  By screen-like, I mean that they are like the keybindings of the GNU screen(1) utility for multiplexing terminals.  <C-a><Space>, for example, will go to the next buffer.  <C-a>a will flip between the current and last-edited buffer.  <C-a>c will create a new buffer.  Other mappings are documented in the script itself.","4":"This plugin provides screen-like keybindings for common window or buffer movements.  By screen-like, I mean that they are like the keybindings of the GNU screen(1) utility for multiplexing terminals.  <C-a><Space>, for example, will go to the next buffer.  <C-a>a will flip between the current and last-edited buffer.  <C-a>c will create a new buffer.  Other mappings are documented in the script itself.","install_details":"Drop it in the plugin directory in your vimruntime path.","5":"Drop it in the plugin directory in your vimruntime path.","first_name":"Ricardo","6":"Ricardo","last_name":"Signes","7":"Signes","releases":[{"0":"940","vim_version":"6.0","1":"6.0","script_version":"1.4","2":"1.4","version_comment":"^Ac will now only display the newly-created buffer.","3":"^Ac will now only display the newly-created buffer.","package":"screen.vim","4":"screen.vim","src_id":"3748","5":"3748","creation_date":"1105027959","6":"1105027959"},{"0":"940","vim_version":"6.0","1":"6.0","script_version":"1.2","2":"1.2","version_comment":"I've added a leader-\" mapping to bring up the buffer explorer, as C-a \" does in screen 4","3":"I've added a leader-\" mapping to bring up the buffer explorer, as C-a \" does in screen 4","package":"screen.vim","4":"screen.vim","src_id":"3216","5":"3216","creation_date":"1089352410","6":"1089352410"},{"0":"940","vim_version":"6.0","1":"6.0","script_version":"1","2":"1","version_comment":"Initial upload","3":"Initial upload","package":"screen.vim","4":"screen.vim","src_id":"2844","5":"2844","creation_date":"1079601955","6":"1079601955"}]},"939":{"script_id":"939","0":"939","script_name":"sccs.vim","1":"sccs.vim","script_type":"utility","2":"utility","summary":"Compare delta's from SCCS files, visually selectable","3":"Compare delta's from SCCS files, visually selectable","description":"A scipt that interfaces with SCCS to view differences between revisions. It is not as complete as sccs-menu.vim vimscript #43, but it adds the benefit of visually selection of delta's, no need to remember relevant version numbers.\r\n\r\nSummary of it's use:\r\n,s Compares the current file with the last stored revision\r\n,S Compares current file with visually selectable revision\r\n,R Compares two visually selectable revisions","4":"A scipt that interfaces with SCCS to view differences between revisions. It is not as complete as sccs-menu.vim vimscript #43, but it adds the benefit of visually selection of delta's, no need to remember relevant version numbers.\r\n\r\nSummary of it's use:\r\n,s Compares the current file with the last stored revision\r\n,S Compares current file with visually selectable revision\r\n,R Compares two visually selectable revisions","install_details":"Copy it to your plugin directory, and read the comments in the file.","5":"Copy it to your plugin directory, and read the comments in the file.","first_name":"erik","6":"erik","last_name":"janssen","7":"janssen","releases":[{"0":"939","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"sccs.vim","4":"sccs.vim","src_id":"2842","5":"2842","creation_date":"1079574061","6":"1079574061"}]},"938":{"script_id":"938","0":"938","script_name":"newheader.vim","1":"newheader.vim","script_type":"utility","2":"utility","summary":"Create function header comment according to a template","3":"Create function header comment according to a template","description":"Just Another headerformatting script for C\/C++. This one does not create headers conform some documenting standard but allows you to specify a template. The template may contain some keywords which are expanded. Start by pressing F7 while the cursor is on or a little above the function in question. If the script finds existing comments just above the function it will neatly format it into the template if the right keyword is found. Example (looking horrible in proportional fonts):\r\n\r\n\" Example _c_header template file:\r\n\" ==============================\r\n\r\n\" \/****************************************************************************\r\n\"  *\r\n\"  * NAME:        name                                    (date)\r\n\"  *\r\n\"  * DESCRIPTION: text\r\n\"  *\r\n\"  * ARGUMENTS:   args\r\n\"  *\r\n\"  * RETURNS:     -\r\n\"  *\r\n\"  * PRE:         -\r\n\"  *\r\n\"  * POST:        -\r\n\"  ***************************************************************************\/\r\n\" \r\n\r\n\" Suppose you have this function:\r\n\" ===============================\r\n\r\n\" \/* \r\n\"  * This is just a comment that is long enough to show the features of\r\n\"  * newheader.vim. It will do some indenting for you and list your function\r\n\"  * arguments\r\n\"  *\/\r\n\" \r\n\" static void show_header( int width, int length,\r\n\"                          byte font, Language *language_selection,\r\n\"                      byte color )\r\n\" {\r\n\"      ....\r\n\" }\r\n\r\n\r\n\" Result\r\n\" ======\r\n\r\n\" Place the cursor one or more lines before the function and press F7. It\r\n\" gives you:\r\n\"\r\n\" \/****************************************************************************\r\n\"  *\r\n\"  * NAME:        show_header                                    (2000 okt 27)\r\n\"  *\r\n\"  * DESCRIPTION: This is just a comment that is long enough to show the\r\n\"  *              features of newheader.vim. It will do some indenting for you\r\n\"  *              and list your function arguments\r\n\"  *\r\n\"  * ARGUMENTS:   width:\r\n\"  *              length:\r\n\"  *              font:\r\n\"  *              *language_selection:\r\n\"  *              color:\r\n\"  *\r\n\"  * RETURNS:     -\r\n\"  *\r\n\"  * PRE:         -\r\n\"  *\r\n\"  * POST:        -\r\n\"  ****************************************************************************\/\r\n\" \r\n\" static void show_header( int width, int length,\r\n\"                          byte font, Language *language_selection,\r\n\"                      byte color )\r\n\" {\r\n\"      ....\r\n\" }\r\n\r\ndisclaimer:\r\nI'm using it a few years now, and it is a big timesaver. However, every new project requires me to do another generalisation on the script. If you think it may be usefull for you but produces odd results, drop me line.","4":"Just Another headerformatting script for C\/C++. This one does not create headers conform some documenting standard but allows you to specify a template. The template may contain some keywords which are expanded. Start by pressing F7 while the cursor is on or a little above the function in question. If the script finds existing comments just above the function it will neatly format it into the template if the right keyword is found. Example (looking horrible in proportional fonts):\r\n\r\n\" Example _c_header template file:\r\n\" ==============================\r\n\r\n\" \/****************************************************************************\r\n\"  *\r\n\"  * NAME:        name                                    (date)\r\n\"  *\r\n\"  * DESCRIPTION: text\r\n\"  *\r\n\"  * ARGUMENTS:   args\r\n\"  *\r\n\"  * RETURNS:     -\r\n\"  *\r\n\"  * PRE:         -\r\n\"  *\r\n\"  * POST:        -\r\n\"  ***************************************************************************\/\r\n\" \r\n\r\n\" Suppose you have this function:\r\n\" ===============================\r\n\r\n\" \/* \r\n\"  * This is just a comment that is long enough to show the features of\r\n\"  * newheader.vim. It will do some indenting for you and list your function\r\n\"  * arguments\r\n\"  *\/\r\n\" \r\n\" static void show_header( int width, int length,\r\n\"                          byte font, Language *language_selection,\r\n\"                      byte color )\r\n\" {\r\n\"      ....\r\n\" }\r\n\r\n\r\n\" Result\r\n\" ======\r\n\r\n\" Place the cursor one or more lines before the function and press F7. It\r\n\" gives you:\r\n\"\r\n\" \/****************************************************************************\r\n\"  *\r\n\"  * NAME:        show_header                                    (2000 okt 27)\r\n\"  *\r\n\"  * DESCRIPTION: This is just a comment that is long enough to show the\r\n\"  *              features of newheader.vim. It will do some indenting for you\r\n\"  *              and list your function arguments\r\n\"  *\r\n\"  * ARGUMENTS:   width:\r\n\"  *              length:\r\n\"  *              font:\r\n\"  *              *language_selection:\r\n\"  *              color:\r\n\"  *\r\n\"  * RETURNS:     -\r\n\"  *\r\n\"  * PRE:         -\r\n\"  *\r\n\"  * POST:        -\r\n\"  ****************************************************************************\/\r\n\" \r\n\" static void show_header( int width, int length,\r\n\"                          byte font, Language *language_selection,\r\n\"                      byte color )\r\n\" {\r\n\"      ....\r\n\" }\r\n\r\ndisclaimer:\r\nI'm using it a few years now, and it is a big timesaver. However, every new project requires me to do another generalisation on the script. If you think it may be usefull for you but produces odd results, drop me line.","install_details":"Copy to your plugin dir. Creating a header is currently mapped to F7. A menu is created in the GUI, which may be deleted if you don't like that","5":"Copy to your plugin dir. Creating a header is currently mapped to F7. A menu is created in the GUI, which may be deleted if you don't like that","first_name":"erik","6":"erik","last_name":"janssen","7":"janssen","releases":[{"0":"938","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"newheader.vim","4":"newheader.vim","src_id":"2839","5":"2839","creation_date":"1079482124","6":"1079482124"}]},"937":{"script_id":"937","0":"937","script_name":"autosession.vim","1":"autosession.vim","script_type":"utility","2":"utility","summary":"Vim plugin for autosaving & autoloading session","3":"Vim plugin for autosaving & autoloading session","description":"Vim plugin for autosaving & autoloading session.\r\n\r\n  - Automatically works if no file is openned from command line and session isn't mannualy changed (i.e. session is unattended).\r\n  - remembers a different session for each working directory.\r\n  - easy: just run Vim with no parameters, and last session will be restored.\r\n  - for desktops: just click on the Vim icon and you'll get your last session.\r\n","4":"Vim plugin for autosaving & autoloading session.\r\n\r\n  - Automatically works if no file is openned from command line and session isn't mannualy changed (i.e. session is unattended).\r\n  - remembers a different session for each working directory.\r\n  - easy: just run Vim with no parameters, and last session will be restored.\r\n  - for desktops: just click on the Vim icon and you'll get your last session.\r\n","install_details":"Just copy the file (autosession.vim) into a Vim plugin directory (for example, into \/usr\/share\/vim\/vim6x\/plugin\/).","5":"Just copy the file (autosession.vim) into a Vim plugin directory (for example, into \/usr\/share\/vim\/vim6x\/plugin\/).","first_name":"Adrian","6":"Adrian","last_name":"Ferrer","7":"Ferrer","releases":[{"0":"937","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"autosession.vim","4":"autosession.vim","src_id":"2836","5":"2836","creation_date":"1079425652","6":"1079425652"}]},"936":{"script_id":"936","0":"936","script_name":"Karma Decompiler","1":"Karma Decompiler","script_type":"game","2":"game","summary":"Makes statistics based on Karma","3":"Makes statistics based on Karma","description":"Karma DeKompiler\r\nNewsPaper Edition\r\n\r\nDedications To:\r\n\r\n1. Bogdan AGAPIE and I know everything. I know some VIM. He knows the rest.\r\n\r\n2. Kevin LEGAN, my former boss, because vIM is the second nature for hIM.\r\n\r\n\r\nThe purpose of the program:\r\nTo find how many votes of each kind generated the total score.\r\nExample:\r\nIf the total score is 1, from 8 votes, the only combination that generates this total score is:\r\n- 1 votes of  4 points\r\n- 2 vote  of  1 points\r\n- 5 votes of -1 points\r\nAfter the program generates these numbers, it will display a visual statistic and it will make some recommendations based on that statistic ( the recommendations will be in the next release ).\r\n\r\nConstructive criticism is welcomed, but I can also handle some encouragement :-)\r\n\r\n\r\nFrequently unAsked Questions:\r\n\r\nQ1) Why \"Decompiler\"?\r\nA1) Because is not always possible to find the original combination that generated the total score.\r\nExample:\r\nTotal score = 2155\r\nVotes = 659 \r\nThere are at least 3 valid combinations:\r\n\r\n- 516 votes of  4 points\r\n- 117 votes of  1 points\r\n- 26  votes of -1 points\r\n \r\n- 518 votes of  4 points\r\n- 112 votes of  1 points\r\n- 29  votes of -1 points\r\n\r\n- 520 votes of  4 points\r\n- 107 votes of  1 points\r\n- 32  votes of -1 points\r\n\r\nHowever, in all of them, the number of \"4-points\" votes is much bigger than the number of \"1-points\" votes, which means this script is appreciated as \"Life changing\".\r\n\r\n\r\nQ2) Why \"DeKompiler\"?\r\nA2) Because it's \"Karma\" and not \"Carma\".\r\n\r\n\r\nQ3) Why \"NewsPaper Edition\"?\r\nA3) Sometimes, newspapers give the reader verifiable data, failing to mention that is not the only possible data. The program will generate only one valid combination, even if there are more than one. A \"Respectable NewsPaper Edition\" is not possible, at least with the current Karma rating.\r\n\r\n\r\nQ4) Why the first version is 0?\r\nA4) Because, the first revision has exactly 0 code.\r\n\r\n\r\nQ5) What's the idea behind the program?\r\nA5) The program generates all the possible combination, in a common sense range, and it displays the first one found. If no combination is found, it means that there is an error on the site or (most probable) the user did not enter valid results.\r\n\r\n\r\nQ6) Why do I have to change the values for \"score\" and \"votes\" INSIDE the script?\r\nA6) Because the author learned vim 2 days before and he did not find how to read variables from the keyboard. Nevertheless,...it will be fixed in the new versions.","4":"Karma DeKompiler\r\nNewsPaper Edition\r\n\r\nDedications To:\r\n\r\n1. Bogdan AGAPIE and I know everything. I know some VIM. He knows the rest.\r\n\r\n2. Kevin LEGAN, my former boss, because vIM is the second nature for hIM.\r\n\r\n\r\nThe purpose of the program:\r\nTo find how many votes of each kind generated the total score.\r\nExample:\r\nIf the total score is 1, from 8 votes, the only combination that generates this total score is:\r\n- 1 votes of  4 points\r\n- 2 vote  of  1 points\r\n- 5 votes of -1 points\r\nAfter the program generates these numbers, it will display a visual statistic and it will make some recommendations based on that statistic ( the recommendations will be in the next release ).\r\n\r\nConstructive criticism is welcomed, but I can also handle some encouragement :-)\r\n\r\n\r\nFrequently unAsked Questions:\r\n\r\nQ1) Why \"Decompiler\"?\r\nA1) Because is not always possible to find the original combination that generated the total score.\r\nExample:\r\nTotal score = 2155\r\nVotes = 659 \r\nThere are at least 3 valid combinations:\r\n\r\n- 516 votes of  4 points\r\n- 117 votes of  1 points\r\n- 26  votes of -1 points\r\n \r\n- 518 votes of  4 points\r\n- 112 votes of  1 points\r\n- 29  votes of -1 points\r\n\r\n- 520 votes of  4 points\r\n- 107 votes of  1 points\r\n- 32  votes of -1 points\r\n\r\nHowever, in all of them, the number of \"4-points\" votes is much bigger than the number of \"1-points\" votes, which means this script is appreciated as \"Life changing\".\r\n\r\n\r\nQ2) Why \"DeKompiler\"?\r\nA2) Because it's \"Karma\" and not \"Carma\".\r\n\r\n\r\nQ3) Why \"NewsPaper Edition\"?\r\nA3) Sometimes, newspapers give the reader verifiable data, failing to mention that is not the only possible data. The program will generate only one valid combination, even if there are more than one. A \"Respectable NewsPaper Edition\" is not possible, at least with the current Karma rating.\r\n\r\n\r\nQ4) Why the first version is 0?\r\nA4) Because, the first revision has exactly 0 code.\r\n\r\n\r\nQ5) What's the idea behind the program?\r\nA5) The program generates all the possible combination, in a common sense range, and it displays the first one found. If no combination is found, it means that there is an error on the site or (most probable) the user did not enter valid results.\r\n\r\n\r\nQ6) Why do I have to change the values for \"score\" and \"votes\" INSIDE the script?\r\nA6) Because the author learned vim 2 days before and he did not find how to read variables from the keyboard. Nevertheless,...it will be fixed in the new versions.","install_details":"- Gently copy the file karma.vim in the vim's folder\r\n- Open the file karma.vim, using the command :e karma.vim\r\n- Change, in the first two lines, the score and the votes\r\n( Take some real examples from the site )\r\n- Save the file, :w \r\n- Run the script, typing :source karma.vim\r\n- If you see something on the screen, enjoy!\r\n\r\nHint: try first the default values from the file.","5":"- Gently copy the file karma.vim in the vim's folder\r\n- Open the file karma.vim, using the command :e karma.vim\r\n- Change, in the first two lines, the score and the votes\r\n( Take some real examples from the site )\r\n- Save the file, :w \r\n- Run the script, typing :source karma.vim\r\n- If you see something on the screen, enjoy!\r\n\r\nHint: try first the default values from the file.","first_name":"Sergiu","6":"Sergiu","last_name":"Funieru","7":"Funieru","releases":[{"0":"936","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"The first functional version.","3":"The first functional version.","package":"Karma.vim","4":"Karma.vim","src_id":"2832","5":"2832","creation_date":"1079226056","6":"1079226056"},{"0":"936","vim_version":"6.0","1":"6.0","script_version":"0.0","2":"0.0","version_comment":"Initial upload","3":"Initial upload","package":"idea.vim","4":"idea.vim","src_id":"2831","5":"2831","creation_date":"1079226010","6":"1079226010"}]},"935":{"script_id":"935","0":"935","script_name":"svg.vim","1":"svg.vim","script_type":"syntax","2":"syntax","summary":"SVG syntax file","3":"SVG syntax file","description":"File for Scalable Vector Graphics syntax highlighting\r\n\r\nThis script highlights SVG 1.0 and 1.1 syntax as described at http:\/\/www.w3.org\/TR\/SVG\/\r\nSVG is an XML application, so svg.vim needs XML syntax file to work properly.\r\n","4":"File for Scalable Vector Graphics syntax highlighting\r\n\r\nThis script highlights SVG 1.0 and 1.1 syntax as described at http:\/\/www.w3.org\/TR\/SVG\/\r\nSVG is an XML application, so svg.vim needs XML syntax file to work properly.\r\n","install_details":"Put svg.vim in your syntax directory\r\nand add the following line to your filetype.vim file:\r\n\r\nau BufNewFile,BufRead *.svg setf svg\r\n","5":"Put svg.vim in your syntax directory\r\nand add the following line to your filetype.vim file:\r\n\r\nau BufNewFile,BufRead *.svg setf svg\r\n","first_name":"Micha\u0142","6":"Michał","last_name":"G\u00c3\u00b3rny","7":"G\u00c3\u00b3rny","releases":[{"0":"935","vim_version":"6.0","1":"6.0","script_version":"1.2","2":"1.2","version_comment":"Added xml-stylesheet processing instruction attributes","3":"Added xml-stylesheet processing instruction attributes","package":"svg.vim","4":"svg.vim","src_id":"5478","5":"5478","creation_date":"1143088055","6":"1143088055"},{"0":"935","vim_version":"6.0","1":"6.0","script_version":"1.1.3","2":"1.1.3","version_comment":"svgEvent and svgEventAttr can be in xhtmlAttribHook cluster now\r\n","3":"svgEvent and svgEventAttr can be in xhtmlAttribHook cluster now\r\n","package":"svg.vim","4":"svg.vim","src_id":"4384","5":"4384","creation_date":"1119432765","6":"1119432765"},{"0":"935","vim_version":"6.0","1":"6.0","script_version":"1.1.2","2":"1.1.2","version_comment":"Fixed XML declaration attribs highlighting","3":"Fixed XML declaration attribs highlighting","package":"svg.vim","4":"svg.vim","src_id":"4348","5":"4348","creation_date":"1118162975","6":"1118162975"},{"0":"935","vim_version":"6.0","1":"6.0","script_version":"1.1.1","2":"1.1.1","version_comment":"Compatibility changes","3":"Compatibility changes","package":"svg.vim","4":"svg.vim","src_id":"4151","5":"4151","creation_date":"1113214810","6":"1113214810"},{"0":"935","vim_version":"6.0","1":"6.0","script_version":"1.1","2":"1.1","version_comment":"Added highlighting for embedded ECMAScript (also in events), rendering for title and desc elements","3":"Added highlighting for embedded ECMAScript (also in events), rendering for title and desc elements","package":"svg.vim","4":"svg.vim","src_id":"3997","5":"3997","creation_date":"1110469314","6":"1110469314"},{"0":"935","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"svg.vim","4":"svg.vim","src_id":"2827","5":"2827","creation_date":"1079110345","6":"1079110345"}]},"934":{"script_id":"934","0":"934","script_name":"ftpsync","1":"ftpsync","script_type":"utility","2":"utility","summary":"Synchronize files with a remote server","3":"Synchronize files with a remote server","description":"The FtpUpdate script provides you the ability to synchronize your files with a server. The main idea when I created this script was to use GVim to edit the files on my local PC, which one has SVN or GIT, rather than directly on the remote server in a shared directory (similar to the staging concept in GIT).\r\n\r\nWith S-F7, you can define the server and the remote path used. The settings can be set for the buffer only or globally if you have many files to synchronize from\/to the same directory. You can set both, and then buffer settings will preempt global settings. \r\n\r\nKey mapping:\r\n\r\n  - <S-F5> and <S-F6>: allow you to update your file respectively from and to the server. Asks for the synchronization parameters if needed.\r\n  - <S-F7>: set the synchronization parameters.\r\n  - <S-F8>: display the synchronization parameters of the current buffer.\r\n\r\nPublic functions:\r\n\r\n  - FtpGetParam(): display the synchronization parameters of the current buffer.\r\n  - FtpSetParam(...): set the synchronization parameters\r\n  - FtpSetServer(...): set the server parameter\r\n  - FtpSetPath(...): set the path parameter\r\n  - FtpUpdate(): put the buffer to the remote server\r\n  - FtpRefresh(): get the file from the remote server\r\n\r\nNote that you can set both global parameters and buffer parameters for a specific buffer which needs different parameters. The buffer settings are taken into account before the global ones.\r\n\r\nFurther more, through the FtpSetPath or FtpSetServer functions, you can set only a specific path or server for a buffer, the second parameter (path or server) being taken from the global variable.\r\n\r\nExample:\r\n\r\nWith <S-F7> you set global parameters srv1 and path \/home\/user1. Then for a specific buffer you type :call FtpSetPath() and set \/home\/dummy2 as buffer path (or type :call FtpSetPath(\"\/home\/user2\",\"b\")).\r\nThen using <S-F5> or <S-F6> on this buffer will use ftp:\/\/srv1\/home\/user2 and ftp:\/\/srv1\/home\/user1 for the other ones.\r\n\r\nThe protocol used is FTP. Writing and reading are performed through netrw.vim plugin, i.e. as typing \r\n\r\n    :write <proto>:\/\/<server>\/<path>\/<file>\r\n    or \r\n    :read <proto>:\/\/<server>\/<path>\/<file>\r\n\r\nNote that <proto> is set in g:FtpSync_Proto (scp by default).\r\n","4":"The FtpUpdate script provides you the ability to synchronize your files with a server. The main idea when I created this script was to use GVim to edit the files on my local PC, which one has SVN or GIT, rather than directly on the remote server in a shared directory (similar to the staging concept in GIT).\r\n\r\nWith S-F7, you can define the server and the remote path used. The settings can be set for the buffer only or globally if you have many files to synchronize from\/to the same directory. You can set both, and then buffer settings will preempt global settings. \r\n\r\nKey mapping:\r\n\r\n  - <S-F5> and <S-F6>: allow you to update your file respectively from and to the server. Asks for the synchronization parameters if needed.\r\n  - <S-F7>: set the synchronization parameters.\r\n  - <S-F8>: display the synchronization parameters of the current buffer.\r\n\r\nPublic functions:\r\n\r\n  - FtpGetParam(): display the synchronization parameters of the current buffer.\r\n  - FtpSetParam(...): set the synchronization parameters\r\n  - FtpSetServer(...): set the server parameter\r\n  - FtpSetPath(...): set the path parameter\r\n  - FtpUpdate(): put the buffer to the remote server\r\n  - FtpRefresh(): get the file from the remote server\r\n\r\nNote that you can set both global parameters and buffer parameters for a specific buffer which needs different parameters. The buffer settings are taken into account before the global ones.\r\n\r\nFurther more, through the FtpSetPath or FtpSetServer functions, you can set only a specific path or server for a buffer, the second parameter (path or server) being taken from the global variable.\r\n\r\nExample:\r\n\r\nWith <S-F7> you set global parameters srv1 and path \/home\/user1. Then for a specific buffer you type :call FtpSetPath() and set \/home\/dummy2 as buffer path (or type :call FtpSetPath(\"\/home\/user2\",\"b\")).\r\nThen using <S-F5> or <S-F6> on this buffer will use ftp:\/\/srv1\/home\/user2 and ftp:\/\/srv1\/home\/user1 for the other ones.\r\n\r\nThe protocol used is FTP. Writing and reading are performed through netrw.vim plugin, i.e. as typing \r\n\r\n    :write <proto>:\/\/<server>\/<path>\/<file>\r\n    or \r\n    :read <proto>:\/\/<server>\/<path>\/<file>\r\n\r\nNote that <proto> is set in g:FtpSync_Proto (scp by default).\r\n","install_details":"Copy the ftpsync.vim file into your $VIM\/vimfiles\/plugin directory and restart VIM","5":"Copy the ftpsync.vim file into your $VIM\/vimfiles\/plugin directory and restart VIM","first_name":"Fabien","6":"Fabien","last_name":"Bouleau","7":"Bouleau","releases":[{"0":"934","vim_version":"6.0","1":"6.0","script_version":"1.2","2":"1.2","version_comment":"Added g:FtpSync_Proto to select protocol (scp is default). See vim help on ftp for more details.","3":"Added g:FtpSync_Proto to select protocol (scp is default). See vim help on ftp for more details.","package":"ftpsync.vim","4":"ftpsync.vim","src_id":"5372","5":"5372","creation_date":"1141608071","6":"1141608071"},{"0":"934","vim_version":"6.0","1":"6.0","script_version":"1.1","2":"1.1","version_comment":"Bug fix in displaying path with S-F8","3":"Bug fix in displaying path with S-F8","package":"ftpsync.vim","4":"ftpsync.vim","src_id":"3457","5":"3457","creation_date":"1095386665","6":"1095386665"},{"0":"934","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Added <S-F7> to set parameters without passing by <S-F5>\r\nAdded <S-F8> to display buffer parameters\r\nUpdated the documentation","3":"Added <S-F7> to set parameters without passing by <S-F5>\r\nAdded <S-F8> to display buffer parameters\r\nUpdated the documentation","package":"ftpsync.vim","4":"ftpsync.vim","src_id":"3375","5":"3375","creation_date":"1093321278","6":"1093321278"},{"0":"934","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"ftpsync.vim","4":"ftpsync.vim","src_id":"2825","5":"2825","creation_date":"1079072896","6":"1079072896"}]},"933":{"script_id":"933","0":"933","script_name":"database-client","1":"database-client","script_type":"utility","2":"utility","summary":"Database client - connect directly to database without external utility","3":"Database client - connect directly to database without external utility","description":"Perl DBI:: module is database independent interface for Perl\r\n\r\ndatabase-client.vim uses this Perl module and allows you make multiple connections to database, send SQL commands and receive data from database\r\n\r\nRequirements: Vim '+perl' feature, installed Perl (5.8.x version or above), DBI perl module\r\n","4":"Perl DBI:: module is database independent interface for Perl\r\n\r\ndatabase-client.vim uses this Perl module and allows you make multiple connections to database, send SQL commands and receive data from database\r\n\r\nRequirements: Vim '+perl' feature, installed Perl (5.8.x version or above), DBI perl module\r\n","install_details":"Copy this file to ~\/.vim\/plugin directory","5":"Copy this file to ~\/.vim\/plugin directory","first_name":"\u013dubom\u00c3\u00adr","6":"Ľubom\u00c3\u00adr","last_name":"Host","7":"Host","releases":[{"0":"933","vim_version":"6.0","1":"6.0","script_version":"0.2","2":"0.2","version_comment":"Enhanced function SQL_Connect()","3":"Enhanced function SQL_Connect()","package":"database-client.vim","4":"database-client.vim","src_id":"2824","5":"2824","creation_date":"1079051191","6":"1079051191"},{"0":"933","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"database-client.vim","4":"database-client.vim","src_id":"2822","5":"2822","creation_date":"1078880919","6":"1078880919"}]},"932":{"script_id":"932","0":"932","script_name":"TogFullscreen.vim","1":"TogFullscreen.vim","script_type":"utility","2":"utility","summary":"Toggle fullscreen mode in Windows","3":"Toggle fullscreen mode in Windows","description":"A simple script that allows you to quickly toggle the Gvim window between regular & fullscreen modes. Matches the functionality of the F11 key in IExplorer.\r\n\r\nKeys:\r\nF11 - toggle fullscreen","4":"A simple script that allows you to quickly toggle the Gvim window between regular & fullscreen modes. Matches the functionality of the F11 key in IExplorer.\r\n\r\nKeys:\r\nF11 - toggle fullscreen","install_details":"","5":"","first_name":"andy","6":"andy","last_name":"fischer","7":"fischer","releases":[{"0":"932","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"TogFullscreen.vim","4":"TogFullscreen.vim","src_id":"2821","5":"2821","creation_date":"1078862312","6":"1078862312"}]},"931":{"script_id":"931","0":"931","script_name":"VimIRC.vim","1":"VimIRC.vim","script_type":"utility","2":"utility","summary":"An IRC client script","3":"An IRC client script","description":"This is an IRC client which runs on Vim.  It has some of the features\r\nIRC users might expect, such as multiple servers connectivity, DCC\r\nSEND\/CHAT features etc..  Read the plugin file for more feature info and\r\nusage instructions.\r\n\r\nFor those who are unfamiliar with IRC in general, I recommend visiting\r\nthis site first: http:\/\/www.irchelp.org\/\r\n\r\nIf you have any questions, problems, or suggestions etc., \/query or\r\ne-mail the maintainer.  Do not direct them to the channel #vim please.\r\n\r\nScreenshots:\r\n  http:\/\/www.dd.iij4u.or.jp\/~madokam\/img\/vimirc04.png\r\n  http:\/\/www.dd.iij4u.or.jp\/~madokam\/img\/vimirc05.png (invoking web browser)\r\n\r\nHere is a minimum set of knowledge required to start\/exit the script:\r\n\r\nTo start it, type\r\n\r\n:VimIRC<CR>\r\n\r\nThen you'll be prompted for some user info (nick, full name etc.).\r\n\r\nUpon successfull connection, try some normal commands you're familiar\r\nwith (\"j\", \"k\", \"<C-W>-\"things and so on).  Typing \"i\" or \"I\" will let\r\nyou in to the IRC-command mode, where you can enter commands such as\r\n\"\/join #vim\" and messages.\r\n\r\nTo quit, just press \"Q\".\r\n\r\nAnother method of quitting: get out of the loop with \"<C-C>\", then type\r\n\r\n:VimIRCQuit<CR>\r\n\r\nIf you change your mind and want to get online again, press \"<Space>\" on\r\nany of the VimIRC windows.\r\n\r\nHave fun!","4":"This is an IRC client which runs on Vim.  It has some of the features\r\nIRC users might expect, such as multiple servers connectivity, DCC\r\nSEND\/CHAT features etc..  Read the plugin file for more feature info and\r\nusage instructions.\r\n\r\nFor those who are unfamiliar with IRC in general, I recommend visiting\r\nthis site first: http:\/\/www.irchelp.org\/\r\n\r\nIf you have any questions, problems, or suggestions etc., \/query or\r\ne-mail the maintainer.  Do not direct them to the channel #vim please.\r\n\r\nScreenshots:\r\n  http:\/\/www.dd.iij4u.or.jp\/~madokam\/img\/vimirc04.png\r\n  http:\/\/www.dd.iij4u.or.jp\/~madokam\/img\/vimirc05.png (invoking web browser)\r\n\r\nHere is a minimum set of knowledge required to start\/exit the script:\r\n\r\nTo start it, type\r\n\r\n:VimIRC<CR>\r\n\r\nThen you'll be prompted for some user info (nick, full name etc.).\r\n\r\nUpon successfull connection, try some normal commands you're familiar\r\nwith (\"j\", \"k\", \"<C-W>-\"things and so on).  Typing \"i\" or \"I\" will let\r\nyou in to the IRC-command mode, where you can enter commands such as\r\n\"\/join #vim\" and messages.\r\n\r\nTo quit, just press \"Q\".\r\n\r\nAnother method of quitting: get out of the loop with \"<C-C>\", then type\r\n\r\n:VimIRCQuit<CR>\r\n\r\nIf you change your mind and want to get online again, press \"<Space>\" on\r\nany of the VimIRC windows.\r\n\r\nHave fun!","install_details":"Just drop the file into your plugin directory.\r\n\r\nRequirements:\r\n  Vim 6.2 or later with perl interface enabled\r\n  Perl 5.6 or later (5.8 or later if you want multibyte support)","5":"Just drop the file into your plugin directory.\r\n\r\nRequirements:\r\n  Vim 6.2 or later with perl interface enabled\r\n  Perl 5.6 or later (5.8 or later if you want multibyte support)","first_name":"Madoka","6":"Madoka","last_name":"Machitani","7":"Machitani","releases":[{"0":"931","vim_version":"6.0","1":"6.0","script_version":"0.9.28","2":"0.9.28","version_comment":"This is an \"I'm really sorry\" fixes release:\r\n* Contrary to what I've said previously, erroneous nickname still caused endless loop when loggin-on.\r\n* When receiving chat messages or something, Vim would cause this error: \"Usage: VIBUF::Append(vimbuf, lnum, @lines)\".","3":"This is an \"I'm really sorry\" fixes release:\r\n* Contrary to what I've said previously, erroneous nickname still caused endless loop when loggin-on.\r\n* When receiving chat messages or something, Vim would cause this error: \"Usage: VIBUF::Append(vimbuf, lnum, @lines)\".","package":"vimirc.vim","4":"vimirc.vim","src_id":"4171","5":"4171","creation_date":"1113587947","6":"1113587947"},{"0":"931","vim_version":"6.0","1":"6.0","script_version":"0.9.27","2":"0.9.27","version_comment":"New maps and some fixes.\r\n* Maps: \"r\" \/ \"R\".  They do just the opposite of \"q\" \/ \"Q\": reconnect to disconnected servers.\r\n* When someone tried to contact (query) you but with different case, the message was totally discarded.\r\n* When you tried to logon with erroneous nickname, it resulted in endless loop.\r\n* Port number was not reused when reconnecting manually with command \"\/server\" (i.e., without arg), failing to reconnect if it was other than the default 6667.\r\n* Global commands (e.g. \"\/gquit\") could not be executed on disconnected servers.\r\n* Window resizing (\"<C-L>\") should perform a bit better now.\r\n* Added tips for opening hidden buffers.","3":"New maps and some fixes.\r\n* Maps: \"r\" \/ \"R\".  They do just the opposite of \"q\" \/ \"Q\": reconnect to disconnected servers.\r\n* When someone tried to contact (query) you but with different case, the message was totally discarded.\r\n* When you tried to logon with erroneous nickname, it resulted in endless loop.\r\n* Port number was not reused when reconnecting manually with command \"\/server\" (i.e., without arg), failing to reconnect if it was other than the default 6667.\r\n* Global commands (e.g. \"\/gquit\") could not be executed on disconnected servers.\r\n* Window resizing (\"<C-L>\") should perform a bit better now.\r\n* Added tips for opening hidden buffers.","package":"vimirc.vim","4":"vimirc.vim","src_id":"4165","5":"4165","creation_date":"1113516734","6":"1113516734"},{"0":"931","vim_version":"6.0","1":"6.0","script_version":"0.9.26","2":"0.9.26","version_comment":"Small fixes:\r\n* When updating hidden buffers, \"E19: Mark has invalid line number\" could occur (quite rarely, I believe).\r\n* NOTICE messages sent from the one you were chatting with could not be displayed in the chat buffer.","3":"Small fixes:\r\n* When updating hidden buffers, \"E19: Mark has invalid line number\" could occur (quite rarely, I believe).\r\n* NOTICE messages sent from the one you were chatting with could not be displayed in the chat buffer.","package":"vimirc.vim","4":"vimirc.vim","src_id":"4155","5":"4155","creation_date":"1113300879","6":"1113300879"},{"0":"931","vim_version":"6.0","1":"6.0","script_version":"0.9.25","2":"0.9.25","version_comment":"* VimIRC now uses stacks for putting messages.  You'll notice the efficiency of it especially when updating channels-lists.\r\n* Some multi-key commands (\"<C-W>t\", etc.) weren't handled properly.\r\n* User mode couldn't be set after auto-reconnecting servers (after disconnect).\r\n* You can now omit your nick or the current channel for the command \"\/MODE\".  E.g.: Entering \"\/MODE +w\" on a non-channel buffer will set the specified mode on you.\r\n* Added abbrev: \"\/MO[DE]\"\r\n* The manner of beeping has become a bit modest.","3":"* VimIRC now uses stacks for putting messages.  You'll notice the efficiency of it especially when updating channels-lists.\r\n* Some multi-key commands (\"<C-W>t\", etc.) weren't handled properly.\r\n* User mode couldn't be set after auto-reconnecting servers (after disconnect).\r\n* You can now omit your nick or the current channel for the command \"\/MODE\".  E.g.: Entering \"\/MODE +w\" on a non-channel buffer will set the specified mode on you.\r\n* Added abbrev: \"\/MO[DE]\"\r\n* The manner of beeping has become a bit modest.","package":"vimirc.vim","4":"vimirc.vim","src_id":"4143","5":"4143","creation_date":"1113078671","6":"1113078671"},{"0":"931","vim_version":"6.0","1":"6.0","script_version":"0.9.24","2":"0.9.24","version_comment":"Some trivial fixes (I'm only listing a few):\r\n* For some unknown reason (to me), cursor position could not be restored sometimes when re-opening hidden channels.  The issue itself might still remain for the time being.\r\n* Nick and command windows could embarrassingly remain open after parting channels with \"q\" key, for some event-related reason.","3":"Some trivial fixes (I'm only listing a few):\r\n* For some unknown reason (to me), cursor position could not be restored sometimes when re-opening hidden channels.  The issue itself might still remain for the time being.\r\n* Nick and command windows could embarrassingly remain open after parting channels with \"q\" key, for some event-related reason.","package":"vimirc.vim","4":"vimirc.vim","src_id":"4137","5":"4137","creation_date":"1112960072","6":"1112960072"},{"0":"931","vim_version":"6.0","1":"6.0","script_version":"0.9.23","2":"0.9.23","version_comment":"This contains rather big improvements:\r\n* Messages can now be received even while offline (i.e., out of the main-loop).  Note that you have to move cursor around periodically for this functionality to be triggered.  The same applies to the next item.\r\n* Timer-related functions (displaying the current time, auto-pinging to keep alive, etc.) will be executed while offline, too.\r\n* Fix on normal mode commands: \"@\" commands (\"@:\" etc.) weren't implemented; two-key commands (\"f\", \"t\", etc.) could not accept count.","3":"This contains rather big improvements:\r\n* Messages can now be received even while offline (i.e., out of the main-loop).  Note that you have to move cursor around periodically for this functionality to be triggered.  The same applies to the next item.\r\n* Timer-related functions (displaying the current time, auto-pinging to keep alive, etc.) will be executed while offline, too.\r\n* Fix on normal mode commands: \"@\" commands (\"@:\" etc.) weren't implemented; two-key commands (\"f\", \"t\", etc.) could not accept count.","package":"vimirc.vim","4":"vimirc.vim","src_id":"4126","5":"4126","creation_date":"1112766806","6":"1112766806"},{"0":"931","vim_version":"6.0","1":"6.0","script_version":"0.9.22","2":"0.9.22","version_comment":"Trivial fixes release:\r\n* Window configuration could get corrupted if you received server messages when the server buffer was hidden and the channels-list was open.\r\n* While typing count for a normal mode command, entering two consecutive zeros nullified the entire input.\r\n* While offline, count for normal mode commands (i.e., maps) could not be handled.\r\n* Really trivial, but \"<C-W><C-P>\" now opens the previous channel ABOVE the current window, which you would find more intuitive.\r\n* When opening hidden channels, cursor was moved to the bottom, which was bad for grasping the flow of conversation.\r\n* \"\/PART\"ing channels with some particular multibyte characters could fail.","3":"Trivial fixes release:\r\n* Window configuration could get corrupted if you received server messages when the server buffer was hidden and the channels-list was open.\r\n* While typing count for a normal mode command, entering two consecutive zeros nullified the entire input.\r\n* While offline, count for normal mode commands (i.e., maps) could not be handled.\r\n* Really trivial, but \"<C-W><C-P>\" now opens the previous channel ABOVE the current window, which you would find more intuitive.\r\n* When opening hidden channels, cursor was moved to the bottom, which was bad for grasping the flow of conversation.\r\n* \"\/PART\"ing channels with some particular multibyte characters could fail.","package":"vimirc.vim","4":"vimirc.vim","src_id":"4118","5":"4118","creation_date":"1112595869","6":"1112595869"},{"0":"931","vim_version":"6.0","1":"6.0","script_version":"0.9.21","2":"0.9.21","version_comment":"* Commands \"<C-N>\" \/ \"<C-P>\" now accepts count: \"3<C-N>\" opens the third next channel or server as seen on the info-bar from the current one.\r\n* Also, commands starting with \"<C-W>\" can now accept count before and\/or after it.\r\n* Nicks window could become empty for some unknown reason.  I still don't know why, but tried to fix it.\r\n* Hitting \"i\" after key-prompt could result in insert mode on a non-command buffer.","3":"* Commands \"<C-N>\" \/ \"<C-P>\" now accepts count: \"3<C-N>\" opens the third next channel or server as seen on the info-bar from the current one.\r\n* Also, commands starting with \"<C-W>\" can now accept count before and\/or after it.\r\n* Nicks window could become empty for some unknown reason.  I still don't know why, but tried to fix it.\r\n* Hitting \"i\" after key-prompt could result in insert mode on a non-command buffer.","package":"vimirc.vim","4":"vimirc.vim","src_id":"4114","5":"4114","creation_date":"1112477478","6":"1112477478"},{"0":"931","vim_version":"6.0","1":"6.0","script_version":"0.9.20","2":"0.9.20","version_comment":"* Nick window could be embarrassingly left open, if you sent\/received query message while on a buffer other than the chat buffer.\r\n* Command \"\/ACTION\" didn't work as described in the help message.  Let me replace the command with \"\/DES[CRIBE]\".\r\n* Added a small new command \"\/WHOA[MI]\".  Might be useful when you forgot who you were after changing nicks several times.\r\n* Changed abbrev: \"\/T[OPIC]\" => \"\/TO[PIC]\", \"\/MS[G]\" => \"\/M[SG]\"\r\n* Added abbrev: \"\/T[IME]\", \"\/WH[O]\", \"\/WHOI[S]\"","3":"* Nick window could be embarrassingly left open, if you sent\/received query message while on a buffer other than the chat buffer.\r\n* Command \"\/ACTION\" didn't work as described in the help message.  Let me replace the command with \"\/DES[CRIBE]\".\r\n* Added a small new command \"\/WHOA[MI]\".  Might be useful when you forgot who you were after changing nicks several times.\r\n* Changed abbrev: \"\/T[OPIC]\" => \"\/TO[PIC]\", \"\/MS[G]\" => \"\/M[SG]\"\r\n* Added abbrev: \"\/T[IME]\", \"\/WH[O]\", \"\/WHOI[S]\"","package":"vimirc.vim","4":"vimirc.vim","src_id":"4108","5":"4108","creation_date":"1112305345","6":"1112305345"},{"0":"931","vim_version":"6.0","1":"6.0","script_version":"0.9.19","2":"0.9.19","version_comment":"* Many IRC commands are made abbreviatable, e.g.: \"\/server\" can now be typed as \"\/s\".  See Tip 8 for more.\r\n* Could not obtain your host address (required when doing DCC sessions) upon logon, if you logged in with a nick containing some special characters.\r\n* statusline message was inappropriate for chat buffers.\r\n* Cursor scrolled to the bottom when you executed \"\/list\", which was not what I intended.\r\n* Made \"\/help\" message not to disappear automatically.","3":"* Many IRC commands are made abbreviatable, e.g.: \"\/server\" can now be typed as \"\/s\".  See Tip 8 for more.\r\n* Could not obtain your host address (required when doing DCC sessions) upon logon, if you logged in with a nick containing some special characters.\r\n* statusline message was inappropriate for chat buffers.\r\n* Cursor scrolled to the bottom when you executed \"\/list\", which was not what I intended.\r\n* Made \"\/help\" message not to disappear automatically.","package":"vimirc.vim","4":"vimirc.vim","src_id":"4106","5":"4106","creation_date":"1112250377","6":"1112250377"},{"0":"931","vim_version":"6.0","1":"6.0","script_version":"0.9.18","2":"0.9.18","version_comment":"* If you logged in servers with nick longer than what they accept, VimIRC failed to recognize you as the user.\r\n* It is now possible to open, internally or externally, IRC server-like strings by hitting \"<CR>\" \/ \"<C-CR>\" \/ \"<S-CR>\" on them.\r\n* Channel-like strings in buffers other than channels-list are also made accessible with \"<CR>\" etc..","3":"* If you logged in servers with nick longer than what they accept, VimIRC failed to recognize you as the user.\r\n* It is now possible to open, internally or externally, IRC server-like strings by hitting \"<CR>\" \/ \"<C-CR>\" \/ \"<S-CR>\" on them.\r\n* Channel-like strings in buffers other than channels-list are also made accessible with \"<CR>\" etc..","package":"vimirc.vim","4":"vimirc.vim","src_id":"4090","5":"4090","creation_date":"1112037401","6":"1112037401"},{"0":"931","vim_version":"6.0","1":"6.0","script_version":"0.9.17","2":"0.9.17","version_comment":"Some fixes on normal-mode commands:\r\n* If you hit special keys after \"<C-W>\" or number, you could get stuck.\r\n* When keys like \"jk\" were typed fast, the second key could not be processed.\r\n* If you (casually) kept pressing \"<CR>\" for a few seconds, the same URL was opened many many times.","3":"Some fixes on normal-mode commands:\r\n* If you hit special keys after \"<C-W>\" or number, you could get stuck.\r\n* When keys like \"jk\" were typed fast, the second key could not be processed.\r\n* If you (casually) kept pressing \"<CR>\" for a few seconds, the same URL was opened many many times.","package":"vimirc.vim","4":"vimirc.vim","src_id":"4075","5":"4075","creation_date":"1111777297","6":"1111777297"},{"0":"931","vim_version":"6.0","1":"6.0","script_version":"0.9.16","2":"0.9.16","version_comment":"* \"auto-join\"ing could fail if you logged in multiple servers simultaneously.\r\n* DCC-chat buffers were not treated as such.\r\n* Subtle fixes\/improvements have been done on buffer\/window manipulation (closing command window quietly, etc.).","3":"* \"auto-join\"ing could fail if you logged in multiple servers simultaneously.\r\n* DCC-chat buffers were not treated as such.\r\n* Subtle fixes\/improvements have been done on buffer\/window manipulation (closing command window quietly, etc.).","package":"vimirc.vim","4":"vimirc.vim","src_id":"4066","5":"4066","creation_date":"1111657457","6":"1111657457"},{"0":"931","vim_version":"6.0","1":"6.0","script_version":"0.9.15","2":"0.9.15","version_comment":"Design change, and new commands:\r\n* Abolished multi-window mode, which was the default mode, but wasn't very useful.  Therefore, \"g:vimirc_winmode\" has no meaning now.  (The original design was done because I couldn't think of any way to update hidden buffers.  The problem was solved long time ago.)\r\n* Instead of the above, added a new command prefix \"SPLIT\".  Prepend it to commands such as \"\/JOIN\", \"\/LIST\", like this: \"\/split join #chan\".  See Tip 6 & 7 for more.\r\n* Added normal-mode commands: \"<C-W><C-N>\", \"<C-W><C-P>\".  They do the same thing as \"<C-N>\" and \"<C-P>\" (walking through channels), with windows split open.","3":"Design change, and new commands:\r\n* Abolished multi-window mode, which was the default mode, but wasn't very useful.  Therefore, \"g:vimirc_winmode\" has no meaning now.  (The original design was done because I couldn't think of any way to update hidden buffers.  The problem was solved long time ago.)\r\n* Instead of the above, added a new command prefix \"SPLIT\".  Prepend it to commands such as \"\/JOIN\", \"\/LIST\", like this: \"\/split join #chan\".  See Tip 6 & 7 for more.\r\n* Added normal-mode commands: \"<C-W><C-N>\", \"<C-W><C-P>\".  They do the same thing as \"<C-N>\" and \"<C-P>\" (walking through channels), with windows split open.","package":"vimirc.vim","4":"vimirc.vim","src_id":"4060","5":"4060","creation_date":"1111532471","6":"1111532471"},{"0":"931","vim_version":"6.0","1":"6.0","script_version":"0.9.14","2":"0.9.14","version_comment":"Small fixes release:\r\n* Pressing <F1> caused an error.\r\n* When closing channels etc., newly active one sometimes didn't get highlighted properly.\r\n* Key prompts could not accept key after special keys such as \"<S-CR>\" were hit.\r\n* (single-window mode) Hitting \"<C-W><CR>\" \/ \"<C-CR>\" \/ \"<S-CR>\" on channels list now opens the channel in a new window.","3":"Small fixes release:\r\n* Pressing <F1> caused an error.\r\n* When closing channels etc., newly active one sometimes didn't get highlighted properly.\r\n* Key prompts could not accept key after special keys such as \"<S-CR>\" were hit.\r\n* (single-window mode) Hitting \"<C-W><CR>\" \/ \"<C-CR>\" \/ \"<S-CR>\" on channels list now opens the channel in a new window.","package":"vimirc.vim","4":"vimirc.vim","src_id":"4043","5":"4043","creation_date":"1111196297","6":"1111196297"},{"0":"931","vim_version":"6.0","1":"6.0","script_version":"0.9.13","2":"0.9.13","version_comment":"This contains an important fix:\r\n* Nicks including \"_\" or \"|\" were not considered to be nicks, which could lead to various troubles\/misbehaviors.\r\n* (single-window mode) Hitting \"<C-W><CR>\" on the info-bar opened the specified channel etc. in a new window, but with bad window configuration.","3":"This contains an important fix:\r\n* Nicks including \"_\" or \"|\" were not considered to be nicks, which could lead to various troubles\/misbehaviors.\r\n* (single-window mode) Hitting \"<C-W><CR>\" on the info-bar opened the specified channel etc. in a new window, but with bad window configuration.","package":"vimirc.vim","4":"vimirc.vim","src_id":"4030","5":"4030","creation_date":"1110948916","6":"1110948916"},{"0":"931","vim_version":"6.0","1":"6.0","script_version":"0.9.12","2":"0.9.12","version_comment":"* \"\/help\" wasn't working.\r\n* Added a timeout feature to the \"hit any key\" prompt.  Prompts with rotating cursor automatically disappear after a few seconds if you give no response to them.  (This might save you from getting disconnected from servers.)\r\n* (GUI) When hiding Vim cursor, attributes such as underline still remained, which was annoying.","3":"* \"\/help\" wasn't working.\r\n* Added a timeout feature to the \"hit any key\" prompt.  Prompts with rotating cursor automatically disappear after a few seconds if you give no response to them.  (This might save you from getting disconnected from servers.)\r\n* (GUI) When hiding Vim cursor, attributes such as underline still remained, which was annoying.","package":"vimirc.vim","4":"vimirc.vim","src_id":"4022","5":"4022","creation_date":"1110840464","6":"1110840464"},{"0":"931","vim_version":"6.0","1":"6.0","script_version":"0.9.11","2":"0.9.11","version_comment":"* Added a small new feature to \"autojoin\".  If you wish to display list of channels upon logon, add the word \"list\" to g:vimirc_autojoin.  See the doc for detail.\r\n* Special-key commands preceded by count (\"10<BS>\" etc.) could not be executed.\r\n* Forgot to map \"ZZ\" and \"ZQ\" to VimIRC's quit function.\r\n* Quit keys could direct the quit command to a wrong server.","3":"* Added a small new feature to \"autojoin\".  If you wish to display list of channels upon logon, add the word \"list\" to g:vimirc_autojoin.  See the doc for detail.\r\n* Special-key commands preceded by count (\"10<BS>\" etc.) could not be executed.\r\n* Forgot to map \"ZZ\" and \"ZQ\" to VimIRC's quit function.\r\n* Quit keys could direct the quit command to a wrong server.","package":"vimirc.vim","4":"vimirc.vim","src_id":"4000","5":"4000","creation_date":"1110500192","6":"1110500192"},{"0":"931","vim_version":"6.0","1":"6.0","script_version":"0.9.10","2":"0.9.10","version_comment":"Important fixes for normal mode key-handling issues.\r\n* Added a `shocmd' functionality for multi-key commands.  This might prevent that you get stuck in a pending mode without noticing it, being unable to get new messages.\r\n* Added several normal commands I've forgotten to do (\",\", \"''\", etc.).\r\n* Added new quit commands: \"ZZ\" and \"ZQ\".  (Equivalent to \"q\" and \"Q\" respectively.)\r\n* Special keys (\"<BS>\" etc.) are now safely handled (I should have read \":h getchar()\" much earlier).","3":"Important fixes for normal mode key-handling issues.\r\n* Added a `shocmd' functionality for multi-key commands.  This might prevent that you get stuck in a pending mode without noticing it, being unable to get new messages.\r\n* Added several normal commands I've forgotten to do (\",\", \"''\", etc.).\r\n* Added new quit commands: \"ZZ\" and \"ZQ\".  (Equivalent to \"q\" and \"Q\" respectively.)\r\n* Special keys (\"<BS>\" etc.) are now safely handled (I should have read \":h getchar()\" much earlier).","package":"vimirc.vim","4":"vimirc.vim","src_id":"3955","5":"3955","creation_date":"1109829048","6":"1109829048"},{"0":"931","vim_version":"6.0","1":"6.0","script_version":"0.9.9","2":"0.9.9","version_comment":"Sorry for updating so often.  As always, I've introduced a new problem to the previous release.\r\n* (Main-loop issue) Pressing the same key for a long time (well, less than a dozen seconds) could make Vim to crash.\r\n* (Ditto) Pressing \"<F1>\" opened Vim's help file, which was not what I expected.\r\n* Made Vim's cursor invisible while you are online.  The Annoying blinks now totally disappear (GUI only).","3":"Sorry for updating so often.  As always, I've introduced a new problem to the previous release.\r\n* (Main-loop issue) Pressing the same key for a long time (well, less than a dozen seconds) could make Vim to crash.\r\n* (Ditto) Pressing \"<F1>\" opened Vim's help file, which was not what I expected.\r\n* Made Vim's cursor invisible while you are online.  The Annoying blinks now totally disappear (GUI only).","package":"vimirc.vim","4":"vimirc.vim","src_id":"3949","5":"3949","creation_date":"1109740696","6":"1109740696"},{"0":"931","vim_version":"6.0","1":"6.0","script_version":"0.9.8","2":"0.9.8","version_comment":"* Hitting keys such as \"<C-CR>\" while in VimIRC's main-loop caused endless recursion (E132).\r\n* Re-sorted key-handling order slightly, to achieve faster movement of motion commands.  (I'm not sure I did well.)\r\n* Added some error-handling, so as not to get thrown out of the loop for simple errors (e.g., pattern not found).","3":"* Hitting keys such as \"<C-CR>\" while in VimIRC's main-loop caused endless recursion (E132).\r\n* Re-sorted key-handling order slightly, to achieve faster movement of motion commands.  (I'm not sure I did well.)\r\n* Added some error-handling, so as not to get thrown out of the loop for simple errors (e.g., pattern not found).","package":"vimirc.vim","4":"vimirc.vim","src_id":"3943","5":"3943","creation_date":"1109660287","6":"1109660287"},{"0":"931","vim_version":"6.0","1":"6.0","script_version":"0.9.7","2":"0.9.7","version_comment":"Quick fix release.\r\n* Hitting \"q\" on command buffers sometimes failed to quit VimIRC.\r\n* \"\/WHOIS\" command seems to have failed sometimes.","3":"Quick fix release.\r\n* Hitting \"q\" on command buffers sometimes failed to quit VimIRC.\r\n* \"\/WHOIS\" command seems to have failed sometimes.","package":"vimirc.vim","4":"vimirc.vim","src_id":"3933","5":"3933","creation_date":"1109569309","6":"1109569309"},{"0":"931","vim_version":"6.0","1":"6.0","script_version":"0.9.6","2":"0.9.6","version_comment":"* URLs starting with \"www\" couldn't be opened properly.\r\n* Added maps \"q\" and \"Q\".  Pressing \"Q\" will quit VimIRC, whereas \"q\" will just close chat\/channel, if the cursor is on one.","3":"* URLs starting with \"www\" couldn't be opened properly.\r\n* Added maps \"q\" and \"Q\".  Pressing \"Q\" will quit VimIRC, whereas \"q\" will just close chat\/channel, if the cursor is on one.","package":"vimirc.vim","4":"vimirc.vim","src_id":"3927","5":"3927","creation_date":"1109543688","6":"1109543688"},{"0":"931","vim_version":"6.0","1":"6.0","script_version":"0.9.5","2":"0.9.5","version_comment":"This is a bug fix release, with some minor improvements:\r\n* Undefined subroutine (&find_channel) was called.  This caused several misbehaviours including the one below.\r\n* (single window) Highlights in the info-bar couldn't be cleared after bringing hidden channels (with new messages) to the foreground.\r\n* (single window) Attempts to highlight the current channel\/server in the info-bar, so that you can easily locate where you are in (see the 3rd screenshot).","3":"This is a bug fix release, with some minor improvements:\r\n* Undefined subroutine (&find_channel) was called.  This caused several misbehaviours including the one below.\r\n* (single window) Highlights in the info-bar couldn't be cleared after bringing hidden channels (with new messages) to the foreground.\r\n* (single window) Attempts to highlight the current channel\/server in the info-bar, so that you can easily locate where you are in (see the 3rd screenshot).","package":"vimirc.vim","4":"vimirc.vim","src_id":"3920","5":"3920","creation_date":"1109412415","6":"1109412415"},{"0":"931","vim_version":"6.0","1":"6.0","script_version":"0.9.4","2":"0.9.4","version_comment":"Fixes for the following items:\r\n* Paste commands (p and P) have been disabled in command buffers by mistake.\r\n* Single-window mode: channels-list didn't show up in the info-bar.\r\n* DCC chat: Multibyte (Japanese) characters had not been decoded.","3":"Fixes for the following items:\r\n* Paste commands (p and P) have been disabled in command buffers by mistake.\r\n* Single-window mode: channels-list didn't show up in the info-bar.\r\n* DCC chat: Multibyte (Japanese) characters had not been decoded.","package":"vimirc.vim","4":"vimirc.vim","src_id":"3880","5":"3880","creation_date":"1108777377","6":"1108777377"},{"0":"931","vim_version":"6.0","1":"6.0","script_version":"0.9.3","2":"0.9.3","version_comment":"This is a buf fix release, with a tiny new command:\r\n* Command: \"\/UNSET option\".  Clears the current setting of an option.\r\n* In the previous release, maps for the key \"<CR>\" were made invalid on some types of buffers.\r\n* Hitting \"i\" after hit-any-key prompt to (re)enter the command mode resulted in a strange, non-insert mode.\r\n* Slightly changed the behavior of \"i\".  It now opens a new input line when typed on an already open command buffer (formerly it left the cursor on the same line, which wasn't very useful).\r\n* Removed the command \"\/SEARCH\", which was not meaningful and had been made available probably by accident.  The functionality itself is available as a normal mode search command (\/ or ?).","3":"This is a buf fix release, with a tiny new command:\r\n* Command: \"\/UNSET option\".  Clears the current setting of an option.\r\n* In the previous release, maps for the key \"<CR>\" were made invalid on some types of buffers.\r\n* Hitting \"i\" after hit-any-key prompt to (re)enter the command mode resulted in a strange, non-insert mode.\r\n* Slightly changed the behavior of \"i\".  It now opens a new input line when typed on an already open command buffer (formerly it left the cursor on the same line, which wasn't very useful).\r\n* Removed the command \"\/SEARCH\", which was not meaningful and had been made available probably by accident.  The functionality itself is available as a normal mode search command (\/ or ?).","package":"vimirc.vim","4":"vimirc.vim","src_id":"3874","5":"3874","creation_date":"1108628292","6":"1108628292"},{"0":"931","vim_version":"6.0","1":"6.0","script_version":"0.9.2","2":"0.9.2","version_comment":"Minor fix, and an experimental new feature.\r\n* Hitting <CR> near a URL-like string may open it with external web browser.  The relevant option is \"vimirc_browser\".  See the doc for detail.\r\n\r\nThis is not much tested.  Feel free to notify me of any errors\/misbehaviours you encounter with this feature.","3":"Minor fix, and an experimental new feature.\r\n* Hitting <CR> near a URL-like string may open it with external web browser.  The relevant option is \"vimirc_browser\".  See the doc for detail.\r\n\r\nThis is not much tested.  Feel free to notify me of any errors\/misbehaviours you encounter with this feature.","package":"vimirc.vim","4":"vimirc.vim","src_id":"3869","5":"3869","creation_date":"1108506252","6":"1108506252"},{"0":"931","vim_version":"6.0","1":"6.0","script_version":"0.9.1","2":"0.9.1","version_comment":"Several minor fixes\/improvements:\r\n* (GUI) File selector dialog now pops up for DCC SEND.  Omit filename argument to use this feature, when executing from the command buffer (see \"\/dcc help\" for syntax).\r\n* Tries to fix the annoying window scrolling you might have suffered when opening command buffers.","3":"Several minor fixes\/improvements:\r\n* (GUI) File selector dialog now pops up for DCC SEND.  Omit filename argument to use this feature, when executing from the command buffer (see \"\/dcc help\" for syntax).\r\n* Tries to fix the annoying window scrolling you might have suffered when opening command buffers.","package":"vimirc.vim","4":"vimirc.vim","src_id":"3865","5":"3865","creation_date":"1108364834","6":"1108364834"},{"0":"931","vim_version":"6.0","1":"6.0","script_version":"0.9","2":"0.9","version_comment":"I've added authenticated logon feature (apparently most users won't need this, only for completeness).  You can specify password for servers in any of the following ways:\r\n  1. (on Vim's command line) :VimIRC -p password\r\n  2. (in VimIRC's command buffer) \/server irc.server.com password\r\n  3. (in .vimrc) let vimirc_pass = 'password' or 'password1@server1,...'","3":"I've added authenticated logon feature (apparently most users won't need this, only for completeness).  You can specify password for servers in any of the following ways:\r\n  1. (on Vim's command line) :VimIRC -p password\r\n  2. (in VimIRC's command buffer) \/server irc.server.com password\r\n  3. (in .vimrc) let vimirc_pass = 'password' or 'password1@server1,...'","package":"vimirc.vim","4":"vimirc.vim","src_id":"3813","5":"3813","creation_date":"1107042722","6":"1107042722"},{"0":"931","vim_version":"6.0","1":"6.0","script_version":"0.8.12","2":"0.8.12","version_comment":"* Due to the previous (0.8.11) change to argument handling, \"\/[G]AWAY\" and \"\/[G]QUIT\" commands have been made to treat arguments (comment) improperly, resulting in awaying impossibility etc..\r\n* I've made channels lists to be cached by default.  The variable \"vimirc_listexpire\", defaulting to a week, defines the longevity of them.  See the doc in the source for detail.\r\n* Added a window-size restoration functionality.  Hit <C-L> in normal mode when any window has got a bad width\/height.","3":"* Due to the previous (0.8.11) change to argument handling, \"\/[G]AWAY\" and \"\/[G]QUIT\" commands have been made to treat arguments (comment) improperly, resulting in awaying impossibility etc..\r\n* I've made channels lists to be cached by default.  The variable \"vimirc_listexpire\", defaulting to a week, defines the longevity of them.  See the doc in the source for detail.\r\n* Added a window-size restoration functionality.  Hit <C-L> in normal mode when any window has got a bad width\/height.","package":"vimirc.vim","4":"vimirc.vim","src_id":"3793","5":"3793","creation_date":"1106607763","6":"1106607763"},{"0":"931","vim_version":"6.0","1":"6.0","script_version":"0.8.11","2":"0.8.11","version_comment":"* The previous (0.8.10) fix with the main-loop issue seems to have introduced another one: you would have no way re-entering the loop if you had been gotten out of it by Vim errors, which shouldn't normally happen though.\r\n* As in Vim, key pressed after the 'Hit any key to continue' prompt will now be utilized as a normal mode command.\r\n* Added a mechanism of argument expansion, which currently expands only '%', into the current channel.  See Tip 5 in the source for usage.","3":"* The previous (0.8.10) fix with the main-loop issue seems to have introduced another one: you would have no way re-entering the loop if you had been gotten out of it by Vim errors, which shouldn't normally happen though.\r\n* As in Vim, key pressed after the 'Hit any key to continue' prompt will now be utilized as a normal mode command.\r\n* Added a mechanism of argument expansion, which currently expands only '%', into the current channel.  See Tip 5 in the source for usage.","package":"vimirc.vim","4":"vimirc.vim","src_id":"3788","5":"3788","creation_date":"1106241324","6":"1106241324"},{"0":"931","vim_version":"6.0","1":"6.0","script_version":"0.8.10","2":"0.8.10","version_comment":"In a recent update, I introduced a bug which could cause some difficulty in getting out of the main-loop (for writing messages etc.).  This has been fixed, I hope.\r\nAlso, sending multiple messages at a time is now made possible.  See Tip 3 in the source.","3":"In a recent update, I introduced a bug which could cause some difficulty in getting out of the main-loop (for writing messages etc.).  This has been fixed, I hope.\r\nAlso, sending multiple messages at a time is now made possible.  See Tip 3 in the source.","package":"vimirc.vim","4":"vimirc.vim","src_id":"3784","5":"3784","creation_date":"1106114890","6":"1106114890"},{"0":"931","vim_version":"6.0","1":"6.0","script_version":"0.8.9","2":"0.8.9","version_comment":"Again, several tiny fixes\/improvements:\r\n* VimIRCQuit didn't actually quit when executed from inside VimIRC's main-loop.\r\n* Operations (typing <CR>) on nicks window could have been directed to other servers erroneously.\r\n* Repetitive normal mode commands (such as jjjjjjjjj) might now work slightly faster (unnoticeably perhaps).\r\n* Chat windows now have nicks window.\r\n* etc.","3":"Again, several tiny fixes\/improvements:\r\n* VimIRCQuit didn't actually quit when executed from inside VimIRC's main-loop.\r\n* Operations (typing <CR>) on nicks window could have been directed to other servers erroneously.\r\n* Repetitive normal mode commands (such as jjjjjjjjj) might now work slightly faster (unnoticeably perhaps).\r\n* Chat windows now have nicks window.\r\n* etc.","package":"vimirc.vim","4":"vimirc.vim","src_id":"3774","5":"3774","creation_date":"1105945580","6":"1105945580"},{"0":"931","vim_version":"6.0","1":"6.0","script_version":"0.8.8","2":"0.8.8","version_comment":"Bug Fix: Horribly enough, sending \"\/ME\" messages has been unable for quite some time (sorry!).\r\nNo new features and no big improvements this time (sorry again!).","3":"Bug Fix: Horribly enough, sending \"\/ME\" messages has been unable for quite some time (sorry!).\r\nNo new features and no big improvements this time (sorry again!).","package":"vimirc.vim","4":"vimirc.vim","src_id":"3755","5":"3755","creation_date":"1105317048","6":"1105317048"},{"0":"931","vim_version":"6.0","1":"6.0","script_version":"0.8.7","2":"0.8.7","version_comment":"Trivial fixes with single window mode:\r\n1. Channel-list buffers were not visited upon in the <C-P> \/ <C-N> walkthru.\r\n2. Cursor stayed on the command window after you finished sending messages\/commands, which wasn't useful.","3":"Trivial fixes with single window mode:\r\n1. Channel-list buffers were not visited upon in the <C-P> \/ <C-N> walkthru.\r\n2. Cursor stayed on the command window after you finished sending messages\/commands, which wasn't useful.","package":"vimirc.vim","4":"vimirc.vim","src_id":"3064","5":"3064","creation_date":"1085703299","6":"1085703299"},{"0":"931","vim_version":"6.0","1":"6.0","script_version":"0.8.6","2":"0.8.6","version_comment":"Only small fixes this time.\r\n1. The command :VimIRCQuit was causing an error.\r\n2. Warnings on the usage of shift() function were seen on some perl versions. (Thanks to alexander for notifying this, also for the above.)\r\n3. Mode strings on channels were not handled properly (I didn't understand the syntax).\r\n4. You could not enter channels with correct keys (\/join #chan key) after you first failed in entering.","3":"Only small fixes this time.\r\n1. The command :VimIRCQuit was causing an error.\r\n2. Warnings on the usage of shift() function were seen on some perl versions. (Thanks to alexander for notifying this, also for the above.)\r\n3. Mode strings on channels were not handled properly (I didn't understand the syntax).\r\n4. You could not enter channels with correct keys (\/join #chan key) after you first failed in entering.","package":"vimirc.vim","4":"vimirc.vim","src_id":"3010","5":"3010","creation_date":"1084265219","6":"1084265219"},{"0":"931","vim_version":"6.0","1":"6.0","script_version":"0.8.5","2":"0.8.5","version_comment":"Fix: VimIRC was eating too much (around 90% all the time) of CPU-time (shudder!).  Thanks to alexander for pointing this out.\r\nNew commands: [DE]OP and [DE]VOICE.  See \/help if you don't know of these commands.\r\nChange: g:vimirc_server and '-s' startup option can now have multiple server name, separated by commas.  Thanks again to alexander, by whom it was suggested.","3":"Fix: VimIRC was eating too much (around 90% all the time) of CPU-time (shudder!).  Thanks to alexander for pointing this out.\r\nNew commands: [DE]OP and [DE]VOICE.  See \/help if you don't know of these commands.\r\nChange: g:vimirc_server and '-s' startup option can now have multiple server name, separated by commas.  Thanks again to alexander, by whom it was suggested.","package":"vimirc.vim","4":"vimirc.vim","src_id":"2977","5":"2977","creation_date":"1082882644","6":"1082882644"},{"0":"931","vim_version":"6.0","1":"6.0","script_version":"0.8.4","2":"0.8.4","version_comment":"New commands: GQUIT and GAWAY.  Sends QUIT\/AWAY commands to all the connected servers at once.\r\n\r\nBug fixes:\r\n1. topics etc. for not joined channels were displayed in newly, undesirably created channel buffers.\r\n2. Manual reconnection with \"\/server\" (without arg) wasn't possible sometimes if multiple connections to servers had been opened.","3":"New commands: GQUIT and GAWAY.  Sends QUIT\/AWAY commands to all the connected servers at once.\r\n\r\nBug fixes:\r\n1. topics etc. for not joined channels were displayed in newly, undesirably created channel buffers.\r\n2. Manual reconnection with \"\/server\" (without arg) wasn't possible sometimes if multiple connections to servers had been opened.","package":"vimirc.vim","4":"vimirc.vim","src_id":"2964","5":"2964","creation_date":"1082589972","6":"1082589972"},{"0":"931","vim_version":"6.0","1":"6.0","script_version":"0.8.3","2":"0.8.3","version_comment":"Bug fixes\/Improvements:\r\n1. Server-specific auto-join settings were not processed properly.\r\n2. Characters other than alpha-numerics and underscore could not be used in command aliases.\r\n3. Command \"ALIAS\" will now accept definitions with and without leading slashes: \"\/alias \/j \/join\", \"\/alias j join\".","3":"Bug fixes\/Improvements:\r\n1. Server-specific auto-join settings were not processed properly.\r\n2. Characters other than alpha-numerics and underscore could not be used in command aliases.\r\n3. Command \"ALIAS\" will now accept definitions with and without leading slashes: \"\/alias \/j \/join\", \"\/alias j join\".","package":"vimirc.vim","4":"vimirc.vim","src_id":"2960","5":"2960","creation_date":"1082455233","6":"1082455233"},{"0":"931","vim_version":"6.0","1":"6.0","script_version":"0.8.2","2":"0.8.2","version_comment":"New commands: ALIAS\/UNALIAS, with which you'll be able to define\/undefine aliases of commands.  Example: \/alias \/j \/join.  Definitions will be saved in a config file, and restored automatically on startup.","3":"New commands: ALIAS\/UNALIAS, with which you'll be able to define\/undefine aliases of commands.  Example: \/alias \/j \/join.  Definitions will be saved in a config file, and restored automatically on startup.","package":"vimirc.vim","4":"vimirc.vim","src_id":"2950","5":"2950","creation_date":"1082351915","6":"1082351915"},{"0":"931","vim_version":"6.0","1":"6.0","script_version":"0.8.1","2":"0.8.1","version_comment":"Bug fixes:\r\n1. Since its implementation, timer functionality hasn't been working as expected: the direction of comparison operator was wrong and timers have been executed instantly (silly!).\r\n2. netsplit handling wasn't working as expected.\r\n3. search() function caused an error with some special patterns such as \"\\z\".","3":"Bug fixes:\r\n1. Since its implementation, timer functionality hasn't been working as expected: the direction of comparison operator was wrong and timers have been executed instantly (silly!).\r\n2. netsplit handling wasn't working as expected.\r\n3. search() function caused an error with some special patterns such as \"\\z\".","package":"vimirc.vim","4":"vimirc.vim","src_id":"2948","5":"2948","creation_date":"1082311971","6":"1082311971"},{"0":"931","vim_version":"6.0","1":"6.0","script_version":"0.8","2":"0.8","version_comment":"A rather big change:\r\nSingle-window mode (g:vimirc_winmode == 'single') has become much useful.  Each channel\/server will now take its own window, and updates for hidden buffers will be done in the background.  See the 2nd screenshot for an idea how it will work.\r\n\r\nNew commands:\r\n1. SET: Use this command to set or show the values of internal options.  Usage: \"\/SET option value\".  Omit arguments to see the list of settable options.\r\n2. <C-N> \/ <C-P> (Normal mode): Cycle through channels\/servers.  Useful in single-window mode.\r\n\r\nA Fix: \"\/JOIN 0\" was not working.","3":"A rather big change:\r\nSingle-window mode (g:vimirc_winmode == 'single') has become much useful.  Each channel\/server will now take its own window, and updates for hidden buffers will be done in the background.  See the 2nd screenshot for an idea how it will work.\r\n\r\nNew commands:\r\n1. SET: Use this command to set or show the values of internal options.  Usage: \"\/SET option value\".  Omit arguments to see the list of settable options.\r\n2. <C-N> \/ <C-P> (Normal mode): Cycle through channels\/servers.  Useful in single-window mode.\r\n\r\nA Fix: \"\/JOIN 0\" was not working.","package":"vimirc.vim","4":"vimirc.vim","src_id":"2944","5":"2944","creation_date":"1082189509","6":"1082189509"},{"0":"931","vim_version":"6.0","1":"6.0","script_version":"0.7.2","2":"0.7.2","version_comment":"Small change\/improvement in logging:\r\n1. Timestamps are added to separate each session.\r\n2. Logs for channels\/chats will now be taken safely (well, in most cases) if those windows have been closed abnormally, i.e. with commands other than \"\/(QUIT|PART|QUERY)\".","3":"Small change\/improvement in logging:\r\n1. Timestamps are added to separate each session.\r\n2. Logs for channels\/chats will now be taken safely (well, in most cases) if those windows have been closed abnormally, i.e. with commands other than \"\/(QUIT|PART|QUERY)\".","package":"vimirc.vim","4":"vimirc.vim","src_id":"2927","5":"2927","creation_date":"1081472669","6":"1081472669"},{"0":"931","vim_version":"6.0","1":"6.0","script_version":"0.7.1","2":"0.7.1","version_comment":"Added a logging feature.  Logs will be taken for each channel separately.  See \"Options\" section for how to enable this feature.\r\n\r\nSome minor fixes\/improvements have also been done.","3":"Added a logging feature.  Logs will be taken for each channel separately.  See \"Options\" section for how to enable this feature.\r\n\r\nSome minor fixes\/improvements have also been done.","package":"vimirc.vim","4":"vimirc.vim","src_id":"2922","5":"2922","creation_date":"1081415699","6":"1081415699"},{"0":"931","vim_version":"6.0","1":"6.0","script_version":"0.7","2":"0.7","version_comment":"WARNING: You might encounter \"Missing endfunction\" error while sourcing this version (I haven't confirmed it myself), which should mean, VimIRC is unusable.  If you do see the error, you'll have to compile vim yourself with patches at least up to 6.2.412, or stick to the older version for some time untill 6.3 is out.\r\n\r\nAdded a significant internal working: timer.  New\/improved features related to this include: auto-away.  See \"Options\" section for how to enable this feature.\r\n\r\nAdded a command: CTCP.  Usage: \/CTCP nick COMMAND.\r\n\r\nBug fixes:\r\n1. \"\/AWAY message\" was sending \"1\" instead of \"message\".\r\n2. When a CTCP message was encountered which VimIRC didn't know of, ERRMSG response was always sent back to the originator, even if it was directed to channels.","3":"WARNING: You might encounter \"Missing endfunction\" error while sourcing this version (I haven't confirmed it myself), which should mean, VimIRC is unusable.  If you do see the error, you'll have to compile vim yourself with patches at least up to 6.2.412, or stick to the older version for some time untill 6.3 is out.\r\n\r\nAdded a significant internal working: timer.  New\/improved features related to this include: auto-away.  See \"Options\" section for how to enable this feature.\r\n\r\nAdded a command: CTCP.  Usage: \/CTCP nick COMMAND.\r\n\r\nBug fixes:\r\n1. \"\/AWAY message\" was sending \"1\" instead of \"message\".\r\n2. When a CTCP message was encountered which VimIRC didn't know of, ERRMSG response was always sent back to the originator, even if it was directed to channels.","package":"vimirc.vim","4":"vimirc.vim","src_id":"2912","5":"2912","creation_date":"1081142494","6":"1081142494"},{"0":"931","vim_version":"6.0","1":"6.0","script_version":"0.6.7","2":"0.6.7","version_comment":"Change: I rather improved the auto-join (channels on logon) feature to enable server-specific channel settings.  See \"Options\" section in the plugin for detail.\r\n\r\nBug fixes:\r\n1. \"\/QUIT\"ting caused an error when channels-list window was open.\r\n2. Quit messages like \"Client Quit\" was regarded as netsplit (silly!)","3":"Change: I rather improved the auto-join (channels on logon) feature to enable server-specific channel settings.  See \"Options\" section in the plugin for detail.\r\n\r\nBug fixes:\r\n1. \"\/QUIT\"ting caused an error when channels-list window was open.\r\n2. Quit messages like \"Client Quit\" was regarded as netsplit (silly!)","package":"vimirc.vim","4":"vimirc.vim","src_id":"2901","5":"2901","creation_date":"1080797140","6":"1080797140"},{"0":"931","vim_version":"6.0","1":"6.0","script_version":"0.6.6","2":"0.6.6","version_comment":"0.6.5 (already removed) contained a serious bug: You cannot login to server!\r\nPlease replace it with this one if you downloaded it.  Sorry.\r\n\r\nHere's a copy of the release note for that version:\r\n\r\nA new feature: Auto-reconnect and rejoin.  This is not much tested.  Please let me know if you find any cases where VimIRC doesn't start reconnecting when it should.\r\n\r\nFixes:\r\n1. On terminal vim without \"Cursor\" highlight group defined, VimIRC was unusable due to the \"No such highlight\" error.  Thanks to morbuz, who notified me of this and tested the fixed version.\r\n2. :VimIRCQuit could cause an endless loop.\r\n3. (Fixed in the previous ver.) Cooperation of vim and perl failed, if strings to be passed to vim contained double-quotes or backslashes.","3":"0.6.5 (already removed) contained a serious bug: You cannot login to server!\r\nPlease replace it with this one if you downloaded it.  Sorry.\r\n\r\nHere's a copy of the release note for that version:\r\n\r\nA new feature: Auto-reconnect and rejoin.  This is not much tested.  Please let me know if you find any cases where VimIRC doesn't start reconnecting when it should.\r\n\r\nFixes:\r\n1. On terminal vim without \"Cursor\" highlight group defined, VimIRC was unusable due to the \"No such highlight\" error.  Thanks to morbuz, who notified me of this and tested the fixed version.\r\n2. :VimIRCQuit could cause an endless loop.\r\n3. (Fixed in the previous ver.) Cooperation of vim and perl failed, if strings to be passed to vim contained double-quotes or backslashes.","package":"vimirc.vim","4":"vimirc.vim","src_id":"2898","5":"2898","creation_date":"1080706315","6":"1080706315"},{"0":"931","vim_version":"6.0","1":"6.0","script_version":"0.6.4","2":"0.6.4","version_comment":"New features: \r\n1. Auto-joining channels upon logon\r\n2. Auto-idetification of nicks.\r\nThe settings are \"vimirc_autojoin\", \"vimirc_nickpass\" respectively.  See the source for details.\r\n\r\nA change: the way nicks are displayed has been changed: newly entered, and actively speaking figures will now be displayed on top.  I did this partly for efficiency reason, among others.  If you prefer the older behavior though, wait for some time till I make it configurable.","3":"New features: \r\n1. Auto-joining channels upon logon\r\n2. Auto-idetification of nicks.\r\nThe settings are \"vimirc_autojoin\", \"vimirc_nickpass\" respectively.  See the source for details.\r\n\r\nA change: the way nicks are displayed has been changed: newly entered, and actively speaking figures will now be displayed on top.  I did this partly for efficiency reason, among others.  If you prefer the older behavior though, wait for some time till I make it configurable.","package":"vimirc.vim","4":"vimirc.vim","src_id":"2887","5":"2887","creation_date":"1080517317","6":"1080517317"},{"0":"931","vim_version":"6.0","1":"6.0","script_version":"0.6.3","2":"0.6.3","version_comment":"A fix: \"\/me message\" wasn't sending proper ACTION.  Sorry.\r\nA new feature: Direct conversation over IRC network (\/query nick) will now be displayed in a separate window as with DCC Chat.","3":"A fix: \"\/me message\" wasn't sending proper ACTION.  Sorry.\r\nA new feature: Direct conversation over IRC network (\/query nick) will now be displayed in a separate window as with DCC Chat.","package":"vimirc.vim","4":"vimirc.vim","src_id":"2859","5":"2859","creation_date":"1080088155","6":"1080088155"},{"0":"931","vim_version":"6.0","1":"6.0","script_version":"0.6.2","2":"0.6.2","version_comment":"Some fixes\/improvements:\r\n1. Added normal-mode commands: some characterwise motions, search (* \/ #) and jumplist movement (<C-O> \/ <C-I>).\r\n2. Fixed an issue of recursive call of the main-loop, which caused pressing i\/I lead to a strange non-insert mode.\r\n3. When connected to multiple servers, \"\/quit\"ting from one server resulted in all other windows but one being closed.","3":"Some fixes\/improvements:\r\n1. Added normal-mode commands: some characterwise motions, search (* \/ #) and jumplist movement (<C-O> \/ <C-I>).\r\n2. Fixed an issue of recursive call of the main-loop, which caused pressing i\/I lead to a strange non-insert mode.\r\n3. When connected to multiple servers, \"\/quit\"ting from one server resulted in all other windows but one being closed.","package":"vimirc.vim","4":"vimirc.vim","src_id":"2853","5":"2853","creation_date":"1080026114","6":"1080026114"},{"0":"931","vim_version":"6.0","1":"6.0","script_version":"0.6.1","2":"0.6.1","version_comment":"A small bug-fix: Currently active window was not restored when someone joined\/parted channels.","3":"A small bug-fix: Currently active window was not restored when someone joined\/parted channels.","package":"vimirc.vim","4":"vimirc.vim","src_id":"2850","5":"2850","creation_date":"1079929817","6":"1079929817"},{"0":"931","vim_version":"6.0","1":"6.0","script_version":"0.6","2":"0.6","version_comment":"New features added:\r\n1. DCC CHAT\/SEND.  Type \"\/dcc help\" for the usage.  Also look into the plugin file for the .vimrc settings.  This is not much tested, so if you find any misbehaviors, or incompatibilities with other clients, let me know via e-mail.\r\n2. Single window mode.  .vimrc setting is: let vimirc_winmode = 'single'","3":"New features added:\r\n1. DCC CHAT\/SEND.  Type \"\/dcc help\" for the usage.  Also look into the plugin file for the .vimrc settings.  This is not much tested, so if you find any misbehaviors, or incompatibilities with other clients, let me know via e-mail.\r\n2. Single window mode.  .vimrc setting is: let vimirc_winmode = 'single'","package":"vimirc.vim","4":"vimirc.vim","src_id":"2849","5":"2849","creation_date":"1079917223","6":"1079917223"},{"0":"931","vim_version":"6.0","1":"6.0","script_version":"0.5.3","2":"0.5.3","version_comment":"A new feature:\r\nAdded a map (<CR>) to the nicks window, with which you can operate some action with selected nick(s), such as querying, changing privileges.\r\n\r\nFixes:\r\n1. The issue of inaccessibility to Japanese channels.\r\n2. Older nick was still used internally when you had to change nicks when logging on.\r\n3. Could not parse mode commands like \"+vv nick1 nick2\".  Characters @\/+ will now be added\/removed properly.","3":"A new feature:\r\nAdded a map (<CR>) to the nicks window, with which you can operate some action with selected nick(s), such as querying, changing privileges.\r\n\r\nFixes:\r\n1. The issue of inaccessibility to Japanese channels.\r\n2. Older nick was still used internally when you had to change nicks when logging on.\r\n3. Could not parse mode commands like \"+vv nick1 nick2\".  Characters @\/+ will now be added\/removed properly.","package":"vimirc.vim","4":"vimirc.vim","src_id":"2828","5":"2828","creation_date":"1079137037","6":"1079137037"},{"0":"931","vim_version":"6.0","1":"6.0","script_version":"0.5.2","2":"0.5.2","version_comment":"1. Removed the \"plugin_\" part from the global variables, just to keep them short.  Please change your settings accordingly.  Sorry for the inconvenience.\r\n2. Japanese text input\/output.  Thanks go to Yasuhiro Matsumoto & Taro Muraoka, who have been helpful on this.  This is still incomplete: you cannot join channels with Japanese characters.\r\n3. Made command windows appear just below the current window.  This is a tentative feature.\r\n4. And some other fixes\/changes too trivial to mention.","3":"1. Removed the \"plugin_\" part from the global variables, just to keep them short.  Please change your settings accordingly.  Sorry for the inconvenience.\r\n2. Japanese text input\/output.  Thanks go to Yasuhiro Matsumoto & Taro Muraoka, who have been helpful on this.  This is still incomplete: you cannot join channels with Japanese characters.\r\n3. Made command windows appear just below the current window.  This is a tentative feature.\r\n4. And some other fixes\/changes too trivial to mention.","package":"vimirc.vim","4":"vimirc.vim","src_id":"2823","5":"2823","creation_date":"1079024937","6":"1079024937"},{"0":"931","vim_version":"6.0","1":"6.0","script_version":"0.5.1","2":"0.5.1","version_comment":"Fixed some bugs:\r\n1. When you connected to a new server with \/server command, the old command window remained open.\r\n2. While connected to multiple servers, [iI] sometimes opened a command window for a wrong server.\r\n3. \/list command did not open a list window on some servers.","3":"Fixed some bugs:\r\n1. When you connected to a new server with \/server command, the old command window remained open.\r\n2. While connected to multiple servers, [iI] sometimes opened a command window for a wrong server.\r\n3. \/list command did not open a list window on some servers.","package":"vimirc.vim","4":"vimirc.vim","src_id":"2818","5":"2818","creation_date":"1078807832","6":"1078807832"},{"0":"931","vim_version":"6.0","1":"6.0","script_version":"0.5","2":"0.5","version_comment":"Added a new feature: \/list command will now open up a separate buffer, where you can sort the list by keys 'o' or 'O'.  Also, you can select a channel to join\r\nby hitting <CR>. \r\n\r\nDid some minor fixes inculding: handle operator and voice privileges properly.","3":"Added a new feature: \/list command will now open up a separate buffer, where you can sort the list by keys 'o' or 'O'.  Also, you can select a channel to join\r\nby hitting <CR>. \r\n\r\nDid some minor fixes inculding: handle operator and voice privileges properly.","package":"vimirc.vim","4":"vimirc.vim","src_id":"2814","5":"2814","creation_date":"1078704245","6":"1078704245"},{"0":"931","vim_version":"6.0","1":"6.0","script_version":"0.4","2":"0.4","version_comment":"Initial upload","3":"Initial upload","package":"vimirc.vim","4":"vimirc.vim","src_id":"2809","5":"2809","creation_date":"1078569948","6":"1078569948"}]},"930":{"script_id":"930","0":"930","script_name":"virata.vim","1":"virata.vim","script_type":"syntax","2":"syntax","summary":"Virata AConfig Configuration Script","3":"Virata AConfig Configuration Script","description":"Virata AConfig Configuration Script Syntax\nis used in AConfig scripts to build ISOS firmware.\nThis syntax can be detected by a combination of the following:\n 1) The file extension \".hw\", \".sw\", \".pkg\" and \".module\",\n 2) The file name pattern \"mk.*\\.cfg\",\n 3) The string \"Virata\" or \"Conexant\" in the first 5 lines,\n 4) The subdirectory \"\/atmos\/\" in the scripts' full path.\nNote that due to mergers Virata has become part of Conexant.","4":"Virata AConfig Configuration Script Syntax\nis used in AConfig scripts to build ISOS firmware.\nThis syntax can be detected by a combination of the following:\n 1) The file extension \".hw\", \".sw\", \".pkg\" and \".module\",\n 2) The file name pattern \"mk.*\\.cfg\",\n 3) The string \"Virata\" or \"Conexant\" in the first 5 lines,\n 4) The subdirectory \"\/atmos\/\" in the scripts' full path.\nNote that due to mergers Virata has become part of Conexant.","install_details":"The virata syntax file is already located in Vim's shared syntax directory.  To use this newer version just place the file in your local user syntax directory or replace the old one. ","5":"The virata syntax file is already located in Vim's shared syntax directory.  To use this newer version just place the file in your local user syntax directory or replace the old one. ","first_name":"Manuel","6":"Manuel","last_name":"Stol","7":"Stol","releases":[{"0":"930","vim_version":"7.0","1":"7.0","script_version":"2.0","2":"2.0","version_comment":"Improved highlight matching.\r\nUpdate to newer Vim version.","3":"Improved highlight matching.\r\nUpdate to newer Vim version.","package":"virata.vim","4":"virata.vim","src_id":"25282","5":"25282","creation_date":"1496746565","6":"1496746565"},{"0":"930","vim_version":"6.0","1":"6.0","script_version":"1.8","2":"1.8","version_comment":"Initial upload","3":"Initial upload","package":"virata.vim","4":"virata.vim","src_id":"2808","5":"2808","creation_date":"1078545671","6":"1078545671"}]},"929":{"script_id":"929","0":"929","script_name":"timelog.vim","1":"timelog.vim","script_type":"ftplugin","2":"ftplugin","summary":"Vim {,ft}plugin for keeping track of one's time.","3":"Vim {,ft}plugin for keeping track of one's time.","description":"\" What:   timelog.vim:  Vim {,ft}plugin for keeping track of one's time.\r\n\" Usage:  source the file, or stick it in your ftplugin directory and\r\n\"         have ft=timelog on your modeline.\r\n\"         Keys:  n new job\r\n\"                t go\r\n\"                q stop \r\n\"                s[1-9] sort by that column\r\n\r\nWhat is it?\r\n===========\r\n\r\nA simple time tracking utility.\r\n\r\nWhy?\r\n====\r\n\r\nI tried karm and gtt and didn't like them.  I find it useful - someone\r\nelse might too.\r\n\r\nInstallation\r\n============\r\n\r\nDrop it in ~\/vim\/ftplugin\/.  When you open a file with the modline telling\r\nvim that the filetype is \"timelog\":\r\n\r\n\" vim:ft=timelog:\r\n\r\nit'll be sourced.  I personally have an alias to check out (RCS) my\r\ntimelog file, open it with vim and check it back in when I'm finished.\r\n\r\nUsage\r\n=====\r\n\r\n\r\nKeys:\r\n   n new job\r\n   t start timing highlighted job (or job with the cursor on it)\r\n   q stop timing\r\n   s[1-9] sort by that column\r\n\r\n\r\nHere's an example of what mine could look like:\r\n\r\n\" vim:ft=timelog:\r\n\" usage:\r\n\"   t go\r\n\"   q stop\r\n\"   n new job\r\n\"   s[1-9] sort by that column\r\n\" dates in yy-mm-dd time in hh:mm:ss\r\nstart     last      time      what?\r\n--------  --------  --------  -------\r\n03-11-03  03-11-03  00:10:23  O  ----    Write doc for timelog.vim \r\n02-11-19  03-10-19  05:19:02  C  0712    something\r\n02-11-19  02-11-19  00:14:41  C  0977    something else\r\n03-11-03  03-11-03  00:00:00  N  ----    blah\r\n\r\nThe first 3 columns are what timelog.vim give you - when the job was\r\ncreated, when it was last modified and time spent on it.  The rest can be\r\nwhatever you like.  For me here I have a tag for whether the job is New,\r\nOpen or Completed (N, O, C), a reference nuber for the job if I have one\r\nand a description.\r\n\r\nThere can be several timlog blocks seperated by white space and can have\r\ntext between.  Each timelog block can be sorted seperately.\r\n\r\nBugs?\r\n=====\r\n\r\nWell, the seconds aren't quite seconds and not all motions highlight the\r\nline the cursor ends up on.","4":"\" What:   timelog.vim:  Vim {,ft}plugin for keeping track of one's time.\r\n\" Usage:  source the file, or stick it in your ftplugin directory and\r\n\"         have ft=timelog on your modeline.\r\n\"         Keys:  n new job\r\n\"                t go\r\n\"                q stop \r\n\"                s[1-9] sort by that column\r\n\r\nWhat is it?\r\n===========\r\n\r\nA simple time tracking utility.\r\n\r\nWhy?\r\n====\r\n\r\nI tried karm and gtt and didn't like them.  I find it useful - someone\r\nelse might too.\r\n\r\nInstallation\r\n============\r\n\r\nDrop it in ~\/vim\/ftplugin\/.  When you open a file with the modline telling\r\nvim that the filetype is \"timelog\":\r\n\r\n\" vim:ft=timelog:\r\n\r\nit'll be sourced.  I personally have an alias to check out (RCS) my\r\ntimelog file, open it with vim and check it back in when I'm finished.\r\n\r\nUsage\r\n=====\r\n\r\n\r\nKeys:\r\n   n new job\r\n   t start timing highlighted job (or job with the cursor on it)\r\n   q stop timing\r\n   s[1-9] sort by that column\r\n\r\n\r\nHere's an example of what mine could look like:\r\n\r\n\" vim:ft=timelog:\r\n\" usage:\r\n\"   t go\r\n\"   q stop\r\n\"   n new job\r\n\"   s[1-9] sort by that column\r\n\" dates in yy-mm-dd time in hh:mm:ss\r\nstart     last      time      what?\r\n--------  --------  --------  -------\r\n03-11-03  03-11-03  00:10:23  O  ----    Write doc for timelog.vim \r\n02-11-19  03-10-19  05:19:02  C  0712    something\r\n02-11-19  02-11-19  00:14:41  C  0977    something else\r\n03-11-03  03-11-03  00:00:00  N  ----    blah\r\n\r\nThe first 3 columns are what timelog.vim give you - when the job was\r\ncreated, when it was last modified and time spent on it.  The rest can be\r\nwhatever you like.  For me here I have a tag for whether the job is New,\r\nOpen or Completed (N, O, C), a reference nuber for the job if I have one\r\nand a description.\r\n\r\nThere can be several timlog blocks seperated by white space and can have\r\ntext between.  Each timelog block can be sorted seperately.\r\n\r\nBugs?\r\n=====\r\n\r\nWell, the seconds aren't quite seconds and not all motions highlight the\r\nline the cursor ends up on.","install_details":"Drop it in ~\/vim\/ftplugin\/.  When you open a file with the modline telling\r\nvim that the filetype is \"timelog\":\r\n\r\n\" vim:ft=timelog:\r\n\r\nit'll be sourced.","5":"Drop it in ~\/vim\/ftplugin\/.  When you open a file with the modline telling\r\nvim that the filetype is \"timelog\":\r\n\r\n\" vim:ft=timelog:\r\n\r\nit'll be sourced.","first_name":"Andrew","6":"Andrew","last_name":"Woods","7":"Woods","releases":[{"0":"929","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"timelog.vim","4":"timelog.vim","src_id":"2806","5":"2806","creation_date":"1078464963","6":"1078464963"}]},"928":{"script_id":"928","0":"928","script_name":"XpMenu","1":"XpMenu","script_type":"utility","2":"utility","summary":"Make vim use WinXP style menu.","3":"Make vim use WinXP style menu.","description":"This script and dll simulate WinXP style menu.\r\nThis module works on Win2K only.(don't support others)\r\nYou can build it with Microsoft Platform SDK.\r\nEnjoy!\r\n\r\n--\r\nscreenshot:\r\nhttp:\/\/hp.vector.co.jp\/authors\/VA020411\/Vim\/xpmenu\/screenshot.jpg\r\nThis use japanese font.\r\n","4":"This script and dll simulate WinXP style menu.\r\nThis module works on Win2K only.(don't support others)\r\nYou can build it with Microsoft Platform SDK.\r\nEnjoy!\r\n\r\n--\r\nscreenshot:\r\nhttp:\/\/hp.vector.co.jp\/authors\/VA020411\/Vim\/xpmenu\/screenshot.jpg\r\nThis use japanese font.\r\n","install_details":"copy xpmenu.vim to $VIMRUNTIME\/plugin\r\ncopy xpmenu.dll to $VIM\r\n","5":"copy xpmenu.vim to $VIMRUNTIME\/plugin\r\ncopy xpmenu.dll to $VIM\r\n","first_name":"Yasuhiro","6":"Yasuhiro","last_name":"Matsumoto","7":"Matsumoto","releases":[{"0":"928","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"xpmenu.tar.bz2","4":"xpmenu.tar.bz2","src_id":"2804","5":"2804","creation_date":"1078432414","6":"1078432414"}]},"927":{"script_id":"927","0":"927","script_name":"colorsel.vim","1":"colorsel.vim","script_type":"utility","2":"utility","summary":"A RGB\/HSV color selector","3":"A RGB\/HSV color selector","description":"A simple interactive RGB\/HSV color selector modelled after Gimp2 RGB\/HSV color selector. Needs gvim and :set nocp (and probably a high-color display).\r\n\r\nUsage: :so colorsel.vim and\r\n\r\n:ColorSel [color]\r\n\r\nstarts the color selector.  The optional color argument can be in rrggbb or rgb form or a CSS named color.\r\n\r\nj, k (or arrows) change active channel.\r\n\r\nh, l (or arrows), b, w (or pgdown, pgup), 0, $ (or home, end) change channel values (by 1, by `word' and to 0\/maximum).\r\n\r\ny yanks the current color as #rrggbb to the unnamed register, \"xy to register x.\r\n\r\n\"xp\/\"xP gets the color from register x.\r\n\r\nx swaps the current and alternate color.\r\n\r\nq immediately quits.\r\n\r\nThe swatch and slider sizes are configurable, palettes and alternate colors can be switched off, see the source.","4":"A simple interactive RGB\/HSV color selector modelled after Gimp2 RGB\/HSV color selector. Needs gvim and :set nocp (and probably a high-color display).\r\n\r\nUsage: :so colorsel.vim and\r\n\r\n:ColorSel [color]\r\n\r\nstarts the color selector.  The optional color argument can be in rrggbb or rgb form or a CSS named color.\r\n\r\nj, k (or arrows) change active channel.\r\n\r\nh, l (or arrows), b, w (or pgdown, pgup), 0, $ (or home, end) change channel values (by 1, by `word' and to 0\/maximum).\r\n\r\ny yanks the current color as #rrggbb to the unnamed register, \"xy to register x.\r\n\r\n\"xp\/\"xP gets the color from register x.\r\n\r\nx swaps the current and alternate color.\r\n\r\nq immediately quits.\r\n\r\nThe swatch and slider sizes are configurable, palettes and alternate colors can be switched off, see the source.","install_details":"","5":"","first_name":"David","6":"David","last_name":"Necas","7":"Necas","releases":[{"0":"927","vim_version":"7.0","1":"7.0","script_version":"20110107","2":"20110107","version_comment":"Arguments in the form of \"guifg=#001234 guibg=White\" are supported now and buffer detection was fixed.  Thanks to Ingo Karkat and Tom for the patches.","3":"Arguments in the form of \"guifg=#001234 guibg=White\" are supported now and buffer detection was fixed.  Thanks to Ingo Karkat and Tom for the patches.","package":"colorsel.zip","4":"colorsel.zip","src_id":"15488","5":"15488","creation_date":"1303308167","6":"1303308167"},{"0":"927","vim_version":"7.0","1":"7.0","script_version":"20100406","2":"20100406","version_comment":"The plug-in now uses the autoload mechanism and, consequently, no longer comes in a single Vim file.  Pressing 'f' now also cycles through a state when no text displayed at all.  (Changes by Ingo Karkat)","3":"The plug-in now uses the autoload mechanism and, consequently, no longer comes in a single Vim file.  Pressing 'f' now also cycles through a state when no text displayed at all.  (Changes by Ingo Karkat)","package":"colorsel.zip","4":"colorsel.zip","src_id":"12789","5":"12789","creation_date":"1270546798","6":"1270546798"},{"0":"927","vim_version":"6.0","1":"6.0","script_version":"20100401","2":"20100401","version_comment":"The color swatch shows text (with changeable proprties), ColorSel can directly edit a hlighlight group and there were several improvements to working with two colors. (Modifications by Ingo Karkat)","3":"The color swatch shows text (with changeable proprties), ColorSel can directly edit a hlighlight group and there were several improvements to working with two colors. (Modifications by Ingo Karkat)","package":"colorsel.vim","4":"colorsel.vim","src_id":"12759","5":"12759","creation_date":"1270120530","6":"1270120530"},{"0":"927","vim_version":"6.0","1":"6.0","script_version":"20090505","2":"20090505","version_comment":"Colours can be stored to a palette (vim registers are used for that).  The colour swatch can be split to show an alternate colour.  Vim 6.2 is required now.  A few small bugs were fixed.  (Enhancements thanks to Ingo Karkat.)","3":"Colours can be stored to a palette (vim registers are used for that).  The colour swatch can be split to show an alternate colour.  Vim 6.2 is required now.  A few small bugs were fixed.  (Enhancements thanks to Ingo Karkat.)","package":"colorsel.vim","4":"colorsel.vim","src_id":"10529","5":"10529","creation_date":"1241508260","6":"1241508260"},{"0":"927","vim_version":"6.0","1":"6.0","script_version":"20090428","2":"20090428","version_comment":"ColorSel can be run with an rgb argument (in addition to rrggbb) or with a named color argument (basic CSS colors are supported).  If it is run with a bogus argument, the color is set to black.\r\n\r\nImprovements thanks to Martin Junger.","3":"ColorSel can be run with an rgb argument (in addition to rrggbb) or with a named color argument (basic CSS colors are supported).  If it is run with a bogus argument, the color is set to black.\r\n\r\nImprovements thanks to Martin Junger.","package":"colorsel.vim","4":"colorsel.vim","src_id":"10470","5":"10470","creation_date":"1240903744","6":"1240903744"},{"0":"927","vim_version":"6.0","1":"6.0","script_version":"20051121","2":"20051121","version_comment":"Compatibility with Vim 7 was fixed (thanks to Markus Trenkwalder).","3":"Compatibility with Vim 7 was fixed (thanks to Markus Trenkwalder).","package":"colorsel.vim","4":"colorsel.vim","src_id":"4784","5":"4784","creation_date":"1132550420","6":"1132550420"},{"0":"927","vim_version":"6.0","1":"6.0","script_version":"20040416","2":"20040416","version_comment":"ColorSel now accepts an optional rrggbb color argument (with optional # prefix) to set the color to (either in an existing selector or when creating a new one). Thanks to Thomas Link for the idea.","3":"ColorSel now accepts an optional rrggbb color argument (with optional # prefix) to set the color to (either in an existing selector or when creating a new one). Thanks to Thomas Link for the idea.","package":"colorsel.vim","4":"colorsel.vim","src_id":"2938","5":"2938","creation_date":"1082091095","6":"1082091095"},{"0":"927","vim_version":"6.0","1":"6.0","script_version":"20040303","2":"20040303","version_comment":"Initial upload","3":"Initial upload","package":"colorsel.vim","4":"colorsel.vim","src_id":"2795","5":"2795","creation_date":"1078241530","6":"1078241530"}]},"926":{"script_id":"926","0":"926","script_name":"russian-phonetic_utf-8.vim","1":"russian-phonetic_utf-8.vim","script_type":"utility","2":"utility","summary":"\"Phonetic\" Cyrillic keymap","3":"\"Phonetic\" Cyrillic keymap","description":"A \"phonetic\" keymap for Cyrillic, for use under UTF-8 encoding.\r\n\r\nThis is the keymap I use when I type Russian in gvim; it may or may not suit you. For instance, it uses several \"dead keys\" which might take some getting used to. Or you might want to use it as a starting point, then alter it to suit your tastes.\r\n\r\nSee also, among others\r\n    :help 'keymap'\r\n    :help keymap-file-format\r\n    vimtip #246\r\n    vimscript #789\r\n\r\nand for a Bulgarian keymap (no ery, no eh-oborotnoye) using a slightly different but similar approach, see vimscript#1109\r\n\r\nVersion history:\r\n\r\n2004-10-17    1.1     Enhancement: combining acute accent added\r\n                                  (for explicit stress, e.g. b\u00c3\u00b3lshaya \"bigger\" vs. bolsh\u00c3\u00a1ya \"big\")\r\n2004-03-01    1.01    Bugfix: Normal mode version of mapping\r\n2004-02-29    1.0     Initial release\r\n","4":"A \"phonetic\" keymap for Cyrillic, for use under UTF-8 encoding.\r\n\r\nThis is the keymap I use when I type Russian in gvim; it may or may not suit you. For instance, it uses several \"dead keys\" which might take some getting used to. Or you might want to use it as a starting point, then alter it to suit your tastes.\r\n\r\nSee also, among others\r\n    :help 'keymap'\r\n    :help keymap-file-format\r\n    vimtip #246\r\n    vimscript #789\r\n\r\nand for a Bulgarian keymap (no ery, no eh-oborotnoye) using a slightly different but similar approach, see vimscript#1109\r\n\r\nVersion history:\r\n\r\n2004-10-17    1.1     Enhancement: combining acute accent added\r\n                                  (for explicit stress, e.g. b\u00c3\u00b3lshaya \"bigger\" vs. bolsh\u00c3\u00a1ya \"big\")\r\n2004-03-01    1.01    Bugfix: Normal mode version of mapping\r\n2004-02-29    1.0     Initial release\r\n","install_details":"Just drop this file into $VIM\/vimfiles\/keymap (for system-wide availability) or into ~\/.vim\/keymap [on Unix] or ~\/vimfiles\/keymap [on Windows] (for private use by a single user).\r\n\r\nThis keymap changes the cursor color to bright red when it is active; to change that, or disable it, change or comment-out the line (near the top) setting the lCursor highlight.\r\n\r\nThere are three other lines you may want to change: mappings defining the <F8> key to toggle the keymap on or off in all modes including Normal. (My Belgian keyboard doesn't AFAIK include a Ctrl-^ key.) Change the {lhs} to anything that suits you, or comment them away.\r\n\r\nHappy Vimming!\r\nTony.","5":"Just drop this file into $VIM\/vimfiles\/keymap (for system-wide availability) or into ~\/.vim\/keymap [on Unix] or ~\/vimfiles\/keymap [on Windows] (for private use by a single user).\r\n\r\nThis keymap changes the cursor color to bright red when it is active; to change that, or disable it, change or comment-out the line (near the top) setting the lCursor highlight.\r\n\r\nThere are three other lines you may want to change: mappings defining the <F8> key to toggle the keymap on or off in all modes including Normal. (My Belgian keyboard doesn't AFAIK include a Ctrl-^ key.) Change the {lhs} to anything that suits you, or comment them away.\r\n\r\nHappy Vimming!\r\nTony.","first_name":"Antoine","6":"Antoine","last_name":"Mechelynck","7":"Mechelynck","releases":[{"0":"926","vim_version":"6.0","1":"6.0","script_version":"1.1","2":"1.1","version_comment":"Enhancement: combining acute accent added (for explicit stress).","3":"Enhancement: combining acute accent added (for explicit stress).","package":"russian-phonetic_utf-8.vim","4":"russian-phonetic_utf-8.vim","src_id":"3554","5":"3554","creation_date":"1098001802","6":"1098001802"}]},"925":{"script_id":"925","0":"925","script_name":"AutoFold.vim","1":"AutoFold.vim","script_type":"utility","2":"utility","summary":"A script to automate folding based on markers and syntax.","3":"A script to automate folding based on markers and syntax.","description":"This script is an attempt at merging syntax and marker based folding.  \r\n\r\nFolding based on markers is available for all filetypes.  Currently both the {{{ \/ }}} and the {{{# \/ }}}# (where # designates the fold level) marking types are supported.\r\n\r\nSyntax folding is currently only available for C, Perl, Python, Shell, and Vim filetypes.\r\n\r\nIncludes function to check and update the foldmarker and line break formats just before saving the file.\r\n\r\nAs of version 1.3, includes functions to insert (zf) and remove (zd) fold markers that behave similarly to those in the marker fold method.","4":"This script is an attempt at merging syntax and marker based folding.  \r\n\r\nFolding based on markers is available for all filetypes.  Currently both the {{{ \/ }}} and the {{{# \/ }}}# (where # designates the fold level) marking types are supported.\r\n\r\nSyntax folding is currently only available for C, Perl, Python, Shell, and Vim filetypes.\r\n\r\nIncludes function to check and update the foldmarker and line break formats just before saving the file.\r\n\r\nAs of version 1.3, includes functions to insert (zf) and remove (zd) fold markers that behave similarly to those in the marker fold method.","install_details":"Download file and save it in ~\/.vim\/plugin\/ to have it automatically load or use :source AutoFold.vim to manually load it.","5":"Download file and save it in ~\/.vim\/plugin\/ to have it automatically load or use :source AutoFold.vim to manually load it.","first_name":"Dave","6":"Dave","last_name":"Vehrs","7":"Vehrs","releases":[{"0":"925","vim_version":"6.0","1":"6.0","script_version":"1.3.2","2":"1.3.2","version_comment":" Updates to UpdateFoldMarkers.","3":" Updates to UpdateFoldMarkers.","package":"AutoFold.vim","4":"AutoFold.vim","src_id":"5336","5":"5336","creation_date":"1141038442","6":"1141038442"},{"0":"925","vim_version":"6.0","1":"6.0","script_version":"1.3.1","2":"1.3.1","version_comment":"Improvements to RemoveFoldMarkers and UpdateFoldMarkers.  Thanks to Eric for the perl folding patch and the formating ideas.","3":"Improvements to RemoveFoldMarkers and UpdateFoldMarkers.  Thanks to Eric for the perl folding patch and the formating ideas.","package":"AutoFold.vim","4":"AutoFold.vim","src_id":"3884","5":"3884","creation_date":"1108888953","6":"1108888953"},{"0":"925","vim_version":"6.0","1":"6.0","script_version":"1.3","2":"1.3","version_comment":"Added functions to insert and remove fold markers. General cleanup. More improvements to UpdateFoldMarkers(). Added \"Fold Hints\".","3":"Added functions to insert and remove fold markers. General cleanup. More improvements to UpdateFoldMarkers(). Added \"Fold Hints\".","package":"AutoFold.vim","4":"AutoFold.vim","src_id":"3834","5":"3834","creation_date":"1107627270","6":"1107627270"},{"0":"925","vim_version":"6.0","1":"6.0","script_version":"1.2.2","2":"1.2.2","version_comment":"Improved fold marker fixing and added fixing for --- breaks.  ","3":"Improved fold marker fixing and added fixing for --- breaks.  ","package":"AutoFold.vim","4":"AutoFold.vim","src_id":"3820","5":"3820","creation_date":"1107212602","6":"1107212602"},{"0":"925","vim_version":"6.0","1":"6.0","script_version":"1.2.1","2":"1.2.1","version_comment":"Vim syntax fix. Configured FoldOpen options. Added function to check and fix the fold marker positioning with autocmd to run just before writing the file.  Improved Marker folding.","3":"Vim syntax fix. Configured FoldOpen options. Added function to check and fix the fold marker positioning with autocmd to run just before writing the file.  Improved Marker folding.","package":"AutoFold.vim","4":"AutoFold.vim","src_id":"3809","5":"3809","creation_date":"1106931934","6":"1106931934"},{"0":"925","vim_version":"6.0","1":"6.0","script_version":"1.2","2":"1.2","version_comment":"Added Fold text style & width configuration items.  Thanks to Wolfgang H. for patches and ideas. ","3":"Added Fold text style & width configuration items.  Thanks to Wolfgang H. for patches and ideas. ","package":"AutoFold.vim","4":"AutoFold.vim","src_id":"3542","5":"3542","creation_date":"1097633694","6":"1097633694"},{"0":"925","vim_version":"6.0","1":"6.0","script_version":"1.1","2":"1.1","version_comment":"Consolidated SFT_SetFoldText subfunctions to improve performance.  Python, Perl, Shell, and Vim folding pattern clean ups.  Added initial C language support.","3":"Consolidated SFT_SetFoldText subfunctions to improve performance.  Python, Perl, Shell, and Vim folding pattern clean ups.  Added initial C language support.","package":"AutoFold.vim","4":"AutoFold.vim","src_id":"2975","5":"2975","creation_date":"1082839255","6":"1082839255"},{"0":"925","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"AutoFold.vim","4":"AutoFold.vim","src_id":"2789","5":"2789","creation_date":"1078003898","6":"1078003898"}]},"924":{"script_id":"924","0":"924","script_name":"html_portuquese","1":"html_portuquese","script_type":"utility","2":"utility","summary":"Change the Brazilian Portuguese html charsets (ccedil) to char (\u00c3\u00a7).","3":"Change the Brazilian Portuguese html charsets (ccedil) to char (\u00c3\u00a7).","description":"Useful for all people who edit Brazilian Portuguese websites in HTML or PHP with Vim.\r\nOn loading a HTML or PHP file, this script replaces all the html-encoded (ccedil, atilde, etc) with their normal Ascii-Chars (\u00c3\u00a7,\u00c3\u00a3, etc) so they're more easily readable.\r\n\r\nWhen you save the file, all Ascii-Chars are replaced by the HTML Encoding.","4":"Useful for all people who edit Brazilian Portuguese websites in HTML or PHP with Vim.\r\nOn loading a HTML or PHP file, this script replaces all the html-encoded (ccedil, atilde, etc) with their normal Ascii-Chars (\u00c3\u00a7,\u00c3\u00a3, etc) so they're more easily readable.\r\n\r\nWhen you save the file, all Ascii-Chars are replaced by the HTML Encoding.","install_details":"put it into vim plugin folder (\/usr\/share\/vim\/vim61\/plugin) or in your ~\/.vim\/plugin\/ folder","5":"put it into vim plugin folder (\/usr\/share\/vim\/vim61\/plugin) or in your ~\/.vim\/plugin\/ folder","first_name":"Rubens","6":"Rubens","last_name":"Marins","7":"Marins","releases":[{"0":"924","vim_version":"6.0","1":"6.0","script_version":"1.1","2":"1.1","version_comment":"fixed a bug typo with acute string","3":"fixed a bug typo with acute string","package":"html_portguese.vim","4":"html_portguese.vim","src_id":"2791","5":"2791","creation_date":"1078054343","6":"1078054343"},{"0":"924","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"html_portguese.vim","4":"html_portguese.vim","src_id":"2788","5":"2788","creation_date":"1077952177","6":"1077952177"}]},"923":{"script_id":"923","0":"923","script_name":"timestamp.vim","1":"timestamp.vim","script_type":"utility","2":"utility","summary":"Plugin to automatically timestamp files","3":"Plugin to automatically timestamp files","description":"When a file is written, and the filename matches |timestamp_automask|, this plugin will search the first and last |timestamp_modelines| lines of your file. If it finds the regexp |timestamp_regexp| then it will replace it with a timestamp. The timestamp is computed by first doing a |token_substitution| on |timestamp_rep| and passing the result to |strftime()|.\r\n\r\nThe plugin tries to stay out of your way, and make the change as transparent as possible. Your search (and all other) history is unaltered, however you might find an extra mark in your jumplist.\r\n\r\nAll the default variables and actions can be changed by buffer \/ global vim variables. See |timestamp_examples for two simple examples.\r\n\r\nBy default, this plugin will timestamp ANY file that matches the regexp |timestamp_regexp| in the first and last 'modelines' (default 5) lines of your file. The default value of |timestamp_regexp| will EITHER match 'TIMESTAMP' or a time (in the format of strftime(\"%c\")) FOLLOWED by a 'Last changed:' or 'Last modified:'. For instance, if you create a new file and want to stamp it with a creation date and a last modified date, make the first few lines: >\r\n\r\n    Created:            TIMESTAMP\r\n    Last Modified:      TIMESTAMP\r\n\r\nWhen you first write the file, these lines will change to: >\r\n\r\n    Created:            Thu 26 Feb 2004 03:15:54 PM CST\r\n    Last Modified:      Thu 26 Feb 2004 03:15:55 PM CST\r\n\r\nOn subsequent writes of the file, the first line will remain unchanged and the second will be stamped with the time of writing.\r\n\r\nNOTE: If you find that on subsequent writes of the file, the second line is also unchanged, it is probably because the time returned by strftime is NOT is the format above. [Look closely and see if there is a leading 0 or timezone missing]. If you are using version 1.11 and higher and still have this problem, please report it to me. As a temporary fix, you can put the line >\r\n\r\n    let timestamp_regexp = '\\v\\C%(<Last %([cC]hanged?|[Mm]odified):\\s+)@<=.*$'\r\n\r\nin your .vimrc. This however has the disadvantage of eating all the text after the colon in any timestamp line.\r\n\r\nRead the complete htmlised documentation at http:\/\/math.stanford.edu\/~gautam\/opensource\/xterm16\/timestamp-doc.html","4":"When a file is written, and the filename matches |timestamp_automask|, this plugin will search the first and last |timestamp_modelines| lines of your file. If it finds the regexp |timestamp_regexp| then it will replace it with a timestamp. The timestamp is computed by first doing a |token_substitution| on |timestamp_rep| and passing the result to |strftime()|.\r\n\r\nThe plugin tries to stay out of your way, and make the change as transparent as possible. Your search (and all other) history is unaltered, however you might find an extra mark in your jumplist.\r\n\r\nAll the default variables and actions can be changed by buffer \/ global vim variables. See |timestamp_examples for two simple examples.\r\n\r\nBy default, this plugin will timestamp ANY file that matches the regexp |timestamp_regexp| in the first and last 'modelines' (default 5) lines of your file. The default value of |timestamp_regexp| will EITHER match 'TIMESTAMP' or a time (in the format of strftime(\"%c\")) FOLLOWED by a 'Last changed:' or 'Last modified:'. For instance, if you create a new file and want to stamp it with a creation date and a last modified date, make the first few lines: >\r\n\r\n    Created:            TIMESTAMP\r\n    Last Modified:      TIMESTAMP\r\n\r\nWhen you first write the file, these lines will change to: >\r\n\r\n    Created:            Thu 26 Feb 2004 03:15:54 PM CST\r\n    Last Modified:      Thu 26 Feb 2004 03:15:55 PM CST\r\n\r\nOn subsequent writes of the file, the first line will remain unchanged and the second will be stamped with the time of writing.\r\n\r\nNOTE: If you find that on subsequent writes of the file, the second line is also unchanged, it is probably because the time returned by strftime is NOT is the format above. [Look closely and see if there is a leading 0 or timezone missing]. If you are using version 1.11 and higher and still have this problem, please report it to me. As a temporary fix, you can put the line >\r\n\r\n    let timestamp_regexp = '\\v\\C%(<Last %([cC]hanged?|[Mm]odified):\\s+)@<=.*$'\r\n\r\nin your .vimrc. This however has the disadvantage of eating all the text after the colon in any timestamp line.\r\n\r\nRead the complete htmlised documentation at http:\/\/math.stanford.edu\/~gautam\/opensource\/xterm16\/timestamp-doc.html","install_details":"Extract the files by:  \"tar -xjvf timestamp.tbz2\" (Use WinRAR if you're using M$ Window$ and don't have bzip2)\r\n\r\nPut 'timestamp.vim' in $VIMRUNTIME\/plugin for global installation. Put it in ~\/.vim\/plugin for local installation. Put 'timestamp.txt' in $VIMRUNTIME\/doc (for global) or in ~\/.vim\/doc for local installation. Don't forget to run ':helptags ~\/.vim\/doc'\r\n\r\nDo ':help add-global-plugin' and ':help add-local-help' for more information installing plugins.","5":"Extract the files by:  \"tar -xjvf timestamp.tbz2\" (Use WinRAR if you're using M$ Window$ and don't have bzip2)\r\n\r\nPut 'timestamp.vim' in $VIMRUNTIME\/plugin for global installation. Put it in ~\/.vim\/plugin for local installation. Put 'timestamp.txt' in $VIMRUNTIME\/doc (for global) or in ~\/.vim\/doc for local installation. Don't forget to run ':helptags ~\/.vim\/doc'\r\n\r\nDo ':help add-global-plugin' and ':help add-local-help' for more information installing plugins.","first_name":"gi1242","6":"gi1242","last_name":"gi1242","7":"gi1242","releases":[{"0":"923","vim_version":"7.0","1":"7.0","script_version":"1.21","2":"1.21","version_comment":"Add |DisableTimestamp|, |EnableTimestamp| and |b:timestamp_disable| to enable \/ disable time stamping temporarily.","3":"Add |DisableTimestamp|, |EnableTimestamp| and |b:timestamp_disable| to enable \/ disable time stamping temporarily.","package":"timestamp-1.21.tbz2","4":"timestamp-1.21.tbz2","src_id":"10283","5":"10283","creation_date":"1238020818","6":"1238020818"},{"0":"923","vim_version":"7.0","1":"7.0","script_version":"1.20","2":"1.20","version_comment":"Optionally ignore missing \"AM\/PM\" in default timestamp. Thanks to Fabian Holler for pointing this out.","3":"Optionally ignore missing \"AM\/PM\" in default timestamp. Thanks to Fabian Holler for pointing this out.","package":"timestamp-1.20.tbz2","4":"timestamp-1.20.tbz2","src_id":"7284","5":"7284","creation_date":"1182434983","6":"1182434983"},{"0":"923","vim_version":"7.0","1":"7.0","script_version":"1.19","2":"1.19","version_comment":"Better preserves your undo history: Timestamping is not done unless writing the timestamp will cause a change.","3":"Better preserves your undo history: Timestamping is not done unless writing the timestamp will cause a change.","package":"timestamp-1.19.tbz2","4":"timestamp-1.19.tbz2","src_id":"5722","5":"5722","creation_date":"1147971372","6":"1147971372"},{"0":"923","vim_version":"7.0","1":"7.0","script_version":"1.18","2":"1.18","version_comment":"Minor bugfix: Timestamping now works with zipped files \/ netrw. Also your jumplist is preserved. (This version works on vim6.4 and vim7)","3":"Minor bugfix: Timestamping now works with zipped files \/ netrw. Also your jumplist is preserved. (This version works on vim6.4 and vim7)","package":"timestamp-1.18.tgz","4":"timestamp-1.18.tgz","src_id":"5516","5":"5516","creation_date":"1144147852","6":"1144147852"},{"0":"923","vim_version":"6.0","1":"6.0","script_version":"1.17","2":"1.17","version_comment":"Reduce Vim's initial load time significantly. On my system, Vim with timestamp-1.16 loads in about 1.1 seconds. With timestamp-1.17, it loads in only 0.3 seconds! The system calls to initialise the uid \/ username were taking time. Calls to these functions have been disabled by default, and further postponed untill the are necessary (and not on Vim startup). These calls can be enabled by setting the variable |timestamp_UseSystemCalls|.","3":"Reduce Vim's initial load time significantly. On my system, Vim with timestamp-1.16 loads in about 1.1 seconds. With timestamp-1.17, it loads in only 0.3 seconds! The system calls to initialise the uid \/ username were taking time. Calls to these functions have been disabled by default, and further postponed untill the are necessary (and not on Vim startup). These calls can be enabled by setting the variable |timestamp_UseSystemCalls|.","package":"timestamp-1.17.tbz2","4":"timestamp-1.17.tbz2","src_id":"3627","5":"3627","creation_date":"1100380439","6":"1100380439"},{"0":"923","vim_version":"6.0","1":"6.0","script_version":"1.16","2":"1.16","version_comment":"No changes in the script. Updated the documentation to include a note to windows users having trouble with the timezone. Thanks to Shishir Ramam for pointing this out.","3":"No changes in the script. Updated the documentation to include a note to windows users having trouble with the timezone. Thanks to Shishir Ramam for pointing this out.","package":"timestamp-1.16.tbz2","4":"timestamp-1.16.tbz2","src_id":"3487","5":"3487","creation_date":"1096111272","6":"1096111272"},{"0":"923","vim_version":"6.0","1":"6.0","script_version":"1.16","2":"1.16","version_comment":"Made all g:timestamp_* variables also available as buffer local variables except for g:timestamp_automask. Thanks to Lars Wilke for doing this. Also fixed default values for |timestamp_hostname|, |timestamp_Hostname|, |timestamp_userid| and |timestamp_username|. Thanks again to Lars Wilke for testing on various platforms.","3":"Made all g:timestamp_* variables also available as buffer local variables except for g:timestamp_automask. Thanks to Lars Wilke for doing this. Also fixed default values for |timestamp_hostname|, |timestamp_Hostname|, |timestamp_userid| and |timestamp_username|. Thanks again to Lars Wilke for testing on various platforms.","package":"timestamp-1.16.tbz2","4":"timestamp-1.16.tbz2","src_id":"3460","5":"3460","creation_date":"1095451684","6":"1095451684"},{"0":"923","vim_version":"6.0","1":"6.0","script_version":"1.15","2":"1.15","version_comment":"Modified the default timestamp regexp to support timestamps in other languages by default. This only works if the day and month names in your language do not use accented characters. If accented characters are present you should set the default timestamp regexp in your .vimrc. English users should not notice any difference.","3":"Modified the default timestamp regexp to support timestamps in other languages by default. This only works if the day and month names in your language do not use accented characters. If accented characters are present you should set the default timestamp regexp in your .vimrc. English users should not notice any difference.","package":"timestamp.tbz2","4":"timestamp.tbz2","src_id":"3250","5":"3250","creation_date":"1090315865","6":"1090315865"},{"0":"923","vim_version":"6.0","1":"6.0","script_version":"1.14","2":"1.14","version_comment":"Now also works in compatible mode.","3":"Now also works in compatible mode.","package":"timestamp.tbz2","4":"timestamp.tbz2","src_id":"3045","5":"3045","creation_date":"1085059362","6":"1085059362"},{"0":"923","vim_version":"6.0","1":"6.0","script_version":"1.13","2":"1.13","version_comment":"A bug caused timestamp.vim to make changes in all lines in the |timestamp_modelines| range. Corrected the code so that now changes are made only when there is a timestamp in a particular line. This makes undoing changes a lot nicer, and keeps timestamp-ing out of your way. Also cleaned up some code :)","3":"A bug caused timestamp.vim to make changes in all lines in the |timestamp_modelines| range. Corrected the code so that now changes are made only when there is a timestamp in a particular line. This makes undoing changes a lot nicer, and keeps timestamp-ing out of your way. Also cleaned up some code :)","package":"timestamp.tbz2","4":"timestamp.tbz2","src_id":"2888","5":"2888","creation_date":"1080552391","6":"1080552391"},{"0":"923","vim_version":"6.0","1":"6.0","script_version":"1.12","2":"1.12","version_comment":"Some Micro$oft machines don't support the timezone ('%Z'). Made the timezone optional in the default settings. The script (with default settings) should now work on both Linux \/ Window$ machines. Thanks to Krall Ed-P27726 for testing this.","3":"Some Micro$oft machines don't support the timezone ('%Z'). Made the timezone optional in the default settings. The script (with default settings) should now work on both Linux \/ Window$ machines. Thanks to Krall Ed-P27726 for testing this.","package":"timestamp.tbz2","4":"timestamp.tbz2","src_id":"2820","5":"2820","creation_date":"1078830551","6":"1078830551"},{"0":"923","vim_version":"6.0","1":"6.0","script_version":"1.11","2":"1.11","version_comment":"The format of strftime(\"%c\") is not standard among all systems \/ locales. This caused default timestamps on some systems to fail. Changed the default value of \"timestamp_rep\" to the expanded version of \"%c\", and included a note in the documentation on how to fix this problem.","3":"The format of strftime(\"%c\") is not standard among all systems \/ locales. This caused default timestamps on some systems to fail. Changed the default value of \"timestamp_rep\" to the expanded version of \"%c\", and included a note in the documentation on how to fix this problem.","package":"timestamp.tbz2","4":"timestamp.tbz2","src_id":"2817","5":"2817","creation_date":"1078747711","6":"1078747711"},{"0":"923","vim_version":"6.0","1":"6.0","script_version":"1.1","2":"1.1","version_comment":"Does not modify any marks or the search history list. Tries to make timestamping as \"transparent\" as possible.","3":"Does not modify any marks or the search history list. Tries to make timestamping as \"transparent\" as possible.","package":"timestamp.tbz2","4":"timestamp.tbz2","src_id":"2807","5":"2807","creation_date":"1078492309","6":"1078492309"}]},"922":{"script_id":"922","0":"922","script_name":"svncommand.vim","1":"svncommand.vim","script_type":"utility","2":"utility","summary":"Subversion (svn) integration plugin","3":"Subversion (svn) integration plugin","description":"This is no longer maintained. See vcscommand vimscript #90 for a suitable replacement.\r\n\r\n\r\n\r\nThis is almost a straight port of cvscommand.vim to support subversion. There's some stuff hacked out, some stuff hacked in, and a lot of s\/CVS\/SVN\/g going on.\r\n\r\nCurrent support is for single file type ops, just like cvscommand.vim. The commandset available is basically: status, info, update, revert, diff, annotate, commit, add, log, vimdiff, review. It can also parse a svn commit buffer and execute a diff based on that (you'll have to setup a mapping for SVNCommitDiff to do this).\r\n\r\nThere is no support for properties, operating on whole directories, or anything super advanced.\r\n\r\nAs of 1.67.3 there is limited svk (http:\/\/svk.elixus.org) support via the SVNCommandAutoSVK. Useful stuff like diff and log work okay, the rest is YMMV for now.","4":"This is no longer maintained. See vcscommand vimscript #90 for a suitable replacement.\r\n\r\n\r\n\r\nThis is almost a straight port of cvscommand.vim to support subversion. There's some stuff hacked out, some stuff hacked in, and a lot of s\/CVS\/SVN\/g going on.\r\n\r\nCurrent support is for single file type ops, just like cvscommand.vim. The commandset available is basically: status, info, update, revert, diff, annotate, commit, add, log, vimdiff, review. It can also parse a svn commit buffer and execute a diff based on that (you'll have to setup a mapping for SVNCommitDiff to do this).\r\n\r\nThere is no support for properties, operating on whole directories, or anything super advanced.\r\n\r\nAs of 1.67.3 there is limited svk (http:\/\/svk.elixus.org) support via the SVNCommandAutoSVK. Useful stuff like diff and log work okay, the rest is YMMV for now.","install_details":"plop svncommand.vim in ~\/.vim\/plugin and away you go. Read the script for things that can be customized out of the box. Hack the script to do whatever else you want.","5":"plop svncommand.vim in ~\/.vim\/plugin and away you go. Read the script for things that can be customized out of the box. Hack the script to do whatever else you want.","first_name":"Adam","6":"Adam","last_name":"Lazur","7":"Lazur","releases":[{"0":"922","vim_version":"6.0","1":"6.0","script_version":"1.67.3","2":"1.67.3","version_comment":"- fix svn info (doh!)\r\n- add quick hack svk support via SVNCommandAutoSVK variable\r\n","3":"- fix svn info (doh!)\r\n- add quick hack svk support via SVNCommandAutoSVK variable\r\n","package":"svncommand-1.67.3.tar.gz","4":"svncommand-1.67.3.tar.gz","src_id":"4179","5":"4179","creation_date":"1113845055","6":"1113845055"},{"0":"922","vim_version":"6.0","1":"6.0","script_version":"1.67.2","2":"1.67.2","version_comment":"    - re-added SVNInfo which got reverted in previous version\r\n    - pass -v to \"svn status\" for SVNStatus()\r\n    - add SVNCommitDiff for grabbing a diff from the files listed in svn-commit.tmp","3":"    - re-added SVNInfo which got reverted in previous version\r\n    - pass -v to \"svn status\" for SVNStatus()\r\n    - add SVNCommitDiff for grabbing a diff from the files listed in svn-commit.tmp","package":"svncommand-1.67.2.tar.gz","4":"svncommand-1.67.2.tar.gz","src_id":"4176","5":"4176","creation_date":"1113724304","6":"1113724304"},{"0":"922","vim_version":"6.0","1":"6.0","script_version":"1.67.1","2":"1.67.1","version_comment":"- updated to match version 1.67 cvscommand.vim\r\n- included svn commit and svnlog syntax highlighting","3":"- updated to match version 1.67 cvscommand.vim\r\n- included svn commit and svnlog syntax highlighting","package":"svncommand-1.67.1.tar.gz","4":"svncommand-1.67.1.tar.gz","src_id":"4173","5":"4173","creation_date":"1113686387","6":"1113686387"},{"0":"922","vim_version":"6.0","1":"6.0","script_version":"2","2":"2","version_comment":"added svn info support","3":"added svn info support","package":"svncommand.vim","4":"svncommand.vim","src_id":"2784","5":"2784","creation_date":"1077742033","6":"1077742033"},{"0":"922","vim_version":"6.0","1":"6.0","script_version":"1","2":"1","version_comment":"Initial upload","3":"Initial upload","package":"svncommand.vim","4":"svncommand.vim","src_id":"2782","5":"2782","creation_date":"1077740640","6":"1077740640"}]},"921":{"script_id":"921","0":"921","script_name":"bufmenu2","1":"bufmenu2","script_type":"utility","2":"utility","summary":"More balanced buffers menu hierarchy","3":"More balanced buffers menu hierarchy","description":"If you are used to opening zillions buffers like I am,\r\nif furthermore, the files you edit have same first letter,\r\nyou might have faced a poor buffer menu with just\r\none submenu title displaying this first letter\r\nand all your file names in this same submenu pane.\r\nYou're puzzled about that ?\r\nI was. I searched for a script doing a nicer job. None :(\r\nI wrote it myself. Not very quickly wrote, not very quick\r\nat execution on my 350 Mhz ppc, BUT you should try\r\nit to see if more balanced hierarchy fits your need.\r\nHey this is free ;)\r\nScreenshots of the difference on a silly example\r\nare available there : http:\/\/lauranger.free.fr\/bufmenu_two.html","4":"If you are used to opening zillions buffers like I am,\r\nif furthermore, the files you edit have same first letter,\r\nyou might have faced a poor buffer menu with just\r\none submenu title displaying this first letter\r\nand all your file names in this same submenu pane.\r\nYou're puzzled about that ?\r\nI was. I searched for a script doing a nicer job. None :(\r\nI wrote it myself. Not very quickly wrote, not very quick\r\nat execution on my 350 Mhz ppc, BUT you should try\r\nit to see if more balanced hierarchy fits your need.\r\nHey this is free ;)\r\nScreenshots of the difference on a silly example\r\nare available there : http:\/\/lauranger.free.fr\/bufmenu_two.html","install_details":"Just drop this script in your plugin directory.\r\nIf you are a bit paranoid, just source it to try it before.\r\nTo see effect, open 10 buffers more than &menuitem\r\n(remember you can set &menuitem to a lower value ;-) ).\r\n","5":"Just drop this script in your plugin directory.\r\nIf you are a bit paranoid, just source it to try it before.\r\nTo see effect, open 10 buffers more than &menuitem\r\n(remember you can set &menuitem to a lower value ;-) ).\r\n","first_name":"Laurent","6":"Laurent","last_name":"G","7":"G","releases":[{"0":"921","vim_version":"6.0","1":"6.0","script_version":"1.0.2","2":"1.0.2","version_comment":"Small precisions about install.","3":"Small precisions about install.","package":"bufmenu2.vim","4":"bufmenu2.vim","src_id":"2893","5":"2893","creation_date":"1080608902","6":"1080608902"}]},"920":{"script_id":"920","0":"920","script_name":"tex_autoclose.vim","1":"tex_autoclose.vim","script_type":"ftplugin","2":"ftplugin","summary":"TeX \/ LaTeX ftplugin to automatically close environments","3":"TeX \/ LaTeX ftplugin to automatically close environments","description":"Provides mappings to automatically close environments.\r\n\r\nPressing \"\\c\" in normal mode (or <C-\\>c in insert mode) will cause the last open environment to be closed. (If a fold is started on the \\begin{env} line, then it will be automatically closed on the \\close{env} line.)\r\n\r\nAlso pressing \"<C-\\>}\" in insert mode when the cursor is at the end of a \"\\begin{environment}\" will automatically generate a \"\\close{environment}\". It will leave the cursor at the end of the \"\\begin{environment}\" (in insert mode), so that the user can enter arguments [if any].\r\n\r\nSmall and functional. Suggestions welcome.\r\n\r\nGit-hub page: https:\/\/github.com\/gi1242\/vim-tex-autoclose\r\n","4":"Provides mappings to automatically close environments.\r\n\r\nPressing \"\\c\" in normal mode (or <C-\\>c in insert mode) will cause the last open environment to be closed. (If a fold is started on the \\begin{env} line, then it will be automatically closed on the \\close{env} line.)\r\n\r\nAlso pressing \"<C-\\>}\" in insert mode when the cursor is at the end of a \"\\begin{environment}\" will automatically generate a \"\\close{environment}\". It will leave the cursor at the end of the \"\\begin{environment}\" (in insert mode), so that the user can enter arguments [if any].\r\n\r\nSmall and functional. Suggestions welcome.\r\n\r\nGit-hub page: https:\/\/github.com\/gi1242\/vim-tex-autoclose\r\n","install_details":"drop the script into your $VIMRUNTIME\/ftplugin directory for global instalation.\r\nPut it in ~\/.vim\/ftplugin for local installation.","5":"drop the script into your $VIMRUNTIME\/ftplugin directory for global instalation.\r\nPut it in ~\/.vim\/ftplugin for local installation.","first_name":"gi1242","6":"gi1242","last_name":"gi1242","7":"gi1242","releases":[{"0":"920","vim_version":"7.3","1":"7.3","script_version":"1.3","2":"1.3","version_comment":"Fixed indent of end environments, and exposed API for ab-prefix plugin.","3":"Fixed indent of end environments, and exposed API for ab-prefix plugin.","package":"tex_autoclose.vim","4":"tex_autoclose.vim","src_id":"22603","5":"22603","creation_date":"1415150337","6":"1415150337"},{"0":"920","vim_version":"7.0","1":"7.0","script_version":"1.2","2":"1.2","version_comment":"Disabled \"}\" auto closing environments by default. This ruined the change history (and didn't account for fold markers). Provided \"<C-\\>c\" to close the last open environment. (Also fix a UTF8 bug, thanks to Molin Pascal)","3":"Disabled \"}\" auto closing environments by default. This ruined the change history (and didn't account for fold markers). Provided \"<C-\\>c\" to close the last open environment. (Also fix a UTF8 bug, thanks to Molin Pascal)","package":"tex_autoclose.vim","4":"tex_autoclose.vim","src_id":"10281","5":"10281","creation_date":"1238003948","6":"1238003948"},{"0":"920","vim_version":"6.0","1":"6.0","script_version":"1.1","2":"1.1","version_comment":"Now pressing \"}\" in insertmode will show the matching \"{\". No other functionality has been modified.","3":"Now pressing \"}\" in insertmode will show the matching \"{\". No other functionality has been modified.","package":"tex_autoclose.vim","4":"tex_autoclose.vim","src_id":"2929","5":"2929","creation_date":"1081533703","6":"1081533703"},{"0":"920","vim_version":"6.0","1":"6.0","script_version":"1.01","2":"1.01","version_comment":"Disabled the mapping \"\\}\". To insert a literal \"}\" in latex, you have to use \"\\}\", which conflicts with this mapping. If you do NOT want \"}\" to automatically close an environment, use \"^V}\"","3":"Disabled the mapping \"\\}\". To insert a literal \"}\" in latex, you have to use \"\\}\", which conflicts with this mapping. If you do NOT want \"}\" to automatically close an environment, use \"^V}\"","package":"tex_autoclose.vim","4":"tex_autoclose.vim","src_id":"2826","5":"2826","creation_date":"1079101757","6":"1079101757"},{"0":"920","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"tex_autoclose.vim","4":"tex_autoclose.vim","src_id":"2774","5":"2774","creation_date":"1077559330","6":"1077559330"}]},"919":{"script_id":"919","0":"919","script_name":"sqlldr.vim","1":"sqlldr.vim","script_type":"syntax","2":"syntax","summary":"Oracle SQL*Loader syntax","3":"Oracle SQL*Loader syntax","description":"Based on keyword list in O'Reilly scarab beetle book (Oracle SQL*Loader ISBN 1-56592-948-9). Derived from sql.vim.","4":"Based on keyword list in O'Reilly scarab beetle book (Oracle SQL*Loader ISBN 1-56592-948-9). Derived from sql.vim.","install_details":"copy to $VIMRUNTIME\/syntax. in addition, you can modify filetype.vim so  that, e.g., *.ctl and *.control files are recognized as SQL*Loader files.\r\n\r\n< au BufNewFile,BufRead *.vbs,*.dsm,*.ctl setf vb\r\n---\r\n> au BufNewFile,BufRead *.vbs,*.dsm setf vb\r\n---\r\n> \" SQL*Loader (Oracle)\r\n> au BufNewFile,BufRead *.ctl,*.control setf sqlldr\r\n\r\n","5":"copy to $VIMRUNTIME\/syntax. in addition, you can modify filetype.vim so  that, e.g., *.ctl and *.control files are recognized as SQL*Loader files.\r\n\r\n< au BufNewFile,BufRead *.vbs,*.dsm,*.ctl setf vb\r\n---\r\n> au BufNewFile,BufRead *.vbs,*.dsm setf vb\r\n---\r\n> \" SQL*Loader (Oracle)\r\n> au BufNewFile,BufRead *.ctl,*.control setf sqlldr\r\n\r\n","first_name":"A.S.","6":"A.S.","last_name":"Drury","7":"Drury","releases":[{"0":"919","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"sqlldr.vim","4":"sqlldr.vim","src_id":"2772","5":"2772","creation_date":"1077522517","6":"1077522517"}]},"918":{"script_id":"918","0":"918","script_name":"CSS 2.1 Specification","1":"CSS 2.1 Specification","script_type":"utility","2":"utility","summary":"CSS 2.1 Specification in Vim help format","3":"CSS 2.1 Specification in Vim help format","description":"Specification of CSS 2.1 for fast looking through with Vim :help and :helpgrep commands.","4":"Specification of CSS 2.1 for fast looking through with Vim :help and :helpgrep commands.","install_details":":help add-local-help","5":":help add-local-help","first_name":"Mikolaj","6":"Mikolaj","last_name":"Machowski","7":"Machowski","releases":[{"0":"918","vim_version":"6.0","1":"6.0","script_version":"1.2","2":"1.2","version_comment":"Add *css* tag at the beginning of file.","3":"Add *css* tag at the beginning of file.","package":"css21.zip","4":"css21.zip","src_id":"4596","5":"4596","creation_date":"1127106647","6":"1127106647"},{"0":"918","vim_version":"6.0","1":"6.0","script_version":"1.1","2":"1.1","version_comment":"Add info about XHTML 1.0 spec in Vim help format on vim-online","3":"Add info about XHTML 1.0 spec in Vim help format on vim-online","package":"css21.zip","4":"css21.zip","src_id":"4511","5":"4511","creation_date":"1124705197","6":"1124705197"},{"0":"918","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"css21.zip","4":"css21.zip","src_id":"2769","5":"2769","creation_date":"1077447185","6":"1077447185"}]},"917":{"script_id":"917","0":"917","script_name":"fdcc.vim","1":"fdcc.vim","script_type":"syntax","2":"syntax","summary":"Locale or FDCC (Formal Definitions of Cultural Conventions, see ISO TR 14652)","3":"Locale or FDCC (Formal Definitions of Cultural Conventions, see ISO TR 14652)","description":"Glibc uses locale (or fdcc) files to define cultural conventions.  The files are usualy named \r\nxx_ZZ where xx is the ISO language code and ZZ is the ISO country code.\r\n\r\nThe highlighter has the following features:\r\n* highlights only valid keys with various LC_ sections\r\n* Shows bad <UNNNN> unicode as an error","4":"Glibc uses locale (or fdcc) files to define cultural conventions.  The files are usualy named \r\nxx_ZZ where xx is the ISO language code and ZZ is the ISO country code.\r\n\r\nThe highlighter has the following features:\r\n* highlights only valid keys with various LC_ sections\r\n* Shows bad <UNNNN> unicode as an error","install_details":"Syntax file\r\n---------------\r\nCopy the file to your .vim\/syntax directory\r\n\r\nin a locale file type: set syntax=fdcc\r\n\r\nFiletype detection\r\n-------------------------\r\nSlightly harder as locale files do not have any specific suffix - but here's what to do\r\n\r\nInsert this after the Diff section in your scripts.vim file.  It does initial patern matching and then looks within the file to determine if it is a locale file.  The double quotes below are escaped on this site so remove those escapes.  In fact it will pronbably mess up all back slashes aswell.  Oh well.\r\n\r\n  \" CVS diff\r\n  else\r\n    let lnum = 1\r\n    while getline(lnum) =~ \"^? \" && lnum < line(\"$\")\r\n      let lnum = lnum + 1\r\n    endwhile\r\n    if getline(lnum) =~ '^Index:\\s\\+\\f\\+$'\r\n      set ft=diff\r\n\r\n      \" locale input files: Formal Definitions of Cultural Conventions\r\n      \" filename must be like en_US, fr_FR@euro or en_US.UTF-8\r\n    \"elseif expand(\"%\") =~ '\\(\\l\\l_\\u\\u\\($\\|[.@]\\)\\|i18n\\|POSIX\\|translit_*\\)'\r\n    elseif expand(\"%\") =~ '\\a\\a_\\a\\a\\($\\|[.@]\\)\\|i18n$\\|POSIX$\\|translit_'\r\n      let lnum = 1\r\n      while lnum < 100 && lnum < line(\"$\")\r\n        if getline(lnum) =~ '^LC_\\(IDENTIFICATION\\|CTYPE\\|COLLATE\\|MONETARY\\|NUMERIC\\|TIME\\|MESSAGES\\|PAPER\\|TELEPHONE\\|MEASUREMENT\\|NAME\\|ADDRESS\\)$'\r\n          setf fdcc\r\n          break\r\n        endif\r\n        let lnum = lnum + 1\r\n      endwhile\r\n    endif\r\n\r\n  endif\r\n\r\n  unlet s:line2 s:line3 s:line4 s:line5\r\n\r\nendif\r\n\r\n","5":"Syntax file\r\n---------------\r\nCopy the file to your .vim\/syntax directory\r\n\r\nin a locale file type: set syntax=fdcc\r\n\r\nFiletype detection\r\n-------------------------\r\nSlightly harder as locale files do not have any specific suffix - but here's what to do\r\n\r\nInsert this after the Diff section in your scripts.vim file.  It does initial patern matching and then looks within the file to determine if it is a locale file.  The double quotes below are escaped on this site so remove those escapes.  In fact it will pronbably mess up all back slashes aswell.  Oh well.\r\n\r\n  \" CVS diff\r\n  else\r\n    let lnum = 1\r\n    while getline(lnum) =~ \"^? \" && lnum < line(\"$\")\r\n      let lnum = lnum + 1\r\n    endwhile\r\n    if getline(lnum) =~ '^Index:\\s\\+\\f\\+$'\r\n      set ft=diff\r\n\r\n      \" locale input files: Formal Definitions of Cultural Conventions\r\n      \" filename must be like en_US, fr_FR@euro or en_US.UTF-8\r\n    \"elseif expand(\"%\") =~ '\\(\\l\\l_\\u\\u\\($\\|[.@]\\)\\|i18n\\|POSIX\\|translit_*\\)'\r\n    elseif expand(\"%\") =~ '\\a\\a_\\a\\a\\($\\|[.@]\\)\\|i18n$\\|POSIX$\\|translit_'\r\n      let lnum = 1\r\n      while lnum < 100 && lnum < line(\"$\")\r\n        if getline(lnum) =~ '^LC_\\(IDENTIFICATION\\|CTYPE\\|COLLATE\\|MONETARY\\|NUMERIC\\|TIME\\|MESSAGES\\|PAPER\\|TELEPHONE\\|MEASUREMENT\\|NAME\\|ADDRESS\\)$'\r\n          setf fdcc\r\n          break\r\n        endif\r\n        let lnum = lnum + 1\r\n      endwhile\r\n    endif\r\n\r\n  endif\r\n\r\n  unlet s:line2 s:line3 s:line4 s:line5\r\n\r\nendif\r\n\r\n","first_name":"Dwayne","6":"Dwayne","last_name":"Bailey","7":"Bailey","releases":[{"0":"917","vim_version":"6.0","1":"6.0","script_version":"20040330","2":"20040330","version_comment":"Minor update\r\n* Added missing keywords for LC_IDENTIFICATION, LC_CTYPE and LC_COLLATE","3":"Minor update\r\n* Added missing keywords for LC_IDENTIFICATION, LC_CTYPE and LC_COLLATE","package":"fdcc.vim","4":"fdcc.vim","src_id":"2894","5":"2894","creation_date":"1080623872","6":"1080623872"},{"0":"917","vim_version":"6.0","1":"6.0","script_version":"20040118","2":"20040118","version_comment":"Initial upload","3":"Initial upload","package":"fdcc.vim","4":"fdcc.vim","src_id":"2766","5":"2766","creation_date":"1077255181","6":"1077255181"}]},"916":{"script_id":"916","0":"916","script_name":"Nibble","1":"Nibble","script_type":"game","2":"game","summary":"Nibble or Snake game for Vim.","3":"Nibble or Snake game for Vim.","description":"- Based on my memories from the first PC game that I played called Nibble (or Nibbles?) written for DOS I think in Basic.\r\n- Recreated the first 5 levels that I remember, very easy to add new levels\r\n  (see s:InitLevel() function).\r\n- Use :Nibble command to start the game.\r\n- Use 'h', 'j', 'k' and 'l' keys to control the direction of the snake and\r\n  drive it on to the aim (call it a sleeping mouse :).\r\n- Use 'q' to quit, <C-C> or <C-Break> to stop and <Space> to pause.\r\n- You have 3 lives to expend. The current number of lives, level and the score\r\n  is displayed.\r\n- If the snake touches the border, the blocks or itself you loose a life.\r\n- Game ends when all the lives are consumed or you complete all the levels.\r\n\r\nGood exerciese to practice hjkl key movements, even for experienced Vi users,\r\nas you need to sometimes react very quickly.\r\n\r\n\r\n\r\nSearch_key_words: nibble nibbles snake game games hari krishna dara","4":"- Based on my memories from the first PC game that I played called Nibble (or Nibbles?) written for DOS I think in Basic.\r\n- Recreated the first 5 levels that I remember, very easy to add new levels\r\n  (see s:InitLevel() function).\r\n- Use :Nibble command to start the game.\r\n- Use 'h', 'j', 'k' and 'l' keys to control the direction of the snake and\r\n  drive it on to the aim (call it a sleeping mouse :).\r\n- Use 'q' to quit, <C-C> or <C-Break> to stop and <Space> to pause.\r\n- You have 3 lives to expend. The current number of lives, level and the score\r\n  is displayed.\r\n- If the snake touches the border, the blocks or itself you loose a life.\r\n- Game ends when all the lives are consumed or you complete all the levels.\r\n\r\nGood exerciese to practice hjkl key movements, even for experienced Vi users,\r\nas you need to sometimes react very quickly.\r\n\r\n\r\n\r\nSearch_key_words: nibble nibbles snake game games hari krishna dara","install_details":"- Vim 7.0 (Preferably GUI version).\r\n- Extract the zip file into your runtime directory. \r\n- Install genutils.vim (vimscript #197)\r\n- For a more uniform movement of the snake across both horizontally and vertically, use a font that gives you a more square looking block (MS windows raster fonts on the console are a good example, but I couldn't find a way to set these on a GUI version), and also resize Vim window to have equal number of rows and columns. If you find such a font for GUI version, please let me know.","5":"- Vim 7.0 (Preferably GUI version).\r\n- Extract the zip file into your runtime directory. \r\n- Install genutils.vim (vimscript #197)\r\n- For a more uniform movement of the snake across both horizontally and vertically, use a font that gives you a more square looking block (MS windows raster fonts on the console are a good example, but I couldn't find a way to set these on a GUI version), and also resize Vim window to have equal number of rows and columns. If you find such a font for GUI version, please let me know.","first_name":"Hari Krishna","6":"Hari Krishna","last_name":"Dara","7":"Dara","releases":[{"0":"916","vim_version":"7.0","1":"7.0","script_version":"2.0","2":"2.0","version_comment":"Just updated to work with Vim7. It now uses the new Vim7 Lists and\r\nDictionaries so much cleaner code than before. No longer uses multvals.\r\n","3":"Just updated to work with Vim7. It now uses the new Vim7 Lists and\r\nDictionaries so much cleaner code than before. No longer uses multvals.\r\n","package":"nibble-2.0.zip","4":"nibble-2.0.zip","src_id":"6711","5":"6711","creation_date":"1170431358","6":"1170431358"},{"0":"916","vim_version":"6.0","1":"6.0","script_version":"1.1","2":"1.1","version_comment":"Updated with Bram's feedback.\r\n- Space should resume paused game.\r\n- When paused, should be able to close the game window and still be able to resume it.\r\n- Highlighting definition may not work on all the color schemes.\r\n\r\nAlso clears out any pending key strokes before starting a new level.","3":"Updated with Bram's feedback.\r\n- Space should resume paused game.\r\n- When paused, should be able to close the game window and still be able to resume it.\r\n- Highlighting definition may not work on all the color schemes.\r\n\r\nAlso clears out any pending key strokes before starting a new level.","package":"nibble-1.1.zip","4":"nibble-1.1.zip","src_id":"2768","5":"2768","creation_date":"1077298088","6":"1077298088"},{"0":"916","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"nibble-1.0.zip","4":"nibble-1.0.zip","src_id":"2764","5":"2764","creation_date":"1077215319","6":"1077215319"}]},"915":{"script_id":"915","0":"915","script_name":"AsNeeded","1":"AsNeeded","script_type":"utility","2":"utility","summary":"Loads plugins as-needed (functions\/maps\/commands)  (autoload)","3":"Loads plugins as-needed (functions\/maps\/commands)  (autoload)","description":"  [AsNeeded V14 AND LATER REQUIRES VIMBALL V18 OR LATER FOR UNPACKING]\r\n\r\nThe AsNeeded plugin loads plugins from the .vim\/AsNeeded directory only as they're needed.  One major advantage over vim 7.0's autoload method is: plugins don't need to be changed!   Just put the plugin in the AsNeeded directory (usually under .vim\/ or vimfiles\\).  It'll work even better if you type :MkAsNeeded while in vim after having updated your AsNeeded directory, too.\r\n\r\nSo, how does it work?  Well, whenever a plugin attempts to execute a function that hasn't been loaded yet, AsNeeded will find the script in the AsNeeded directory, load the script, and execute the function.\r\n\r\nAnd, whenever you want to execute a command that's not been loaded yet, and you've run :MkAsNeeded, then the plugin will be transparently loaded and the command executed!  If you didn't do :MkAsNeeded, or you wish to use a map, then instead you can use\r\n\r\n\t:AN map\r\n\t:AN command [arguments]\r\n\r\nand AsNeeded will locate the map or command, load the script, and make the map or command available for your subsequent use.  Alternatively, you can use\r\n\r\n\t:ANX map\r\n\t:ANX command [arguments]\r\n\r\nand AsNeeded will do what :AN would do plus attempt to execute the map or command.\r\n\r\nFor even faster loading of your desired function, map, or command, you can (as of v6) use\r\n\r\n\t:MkAsNeeded\r\n\r\nThis command will create a <ANtags> file in your AsNeeded subdirectory which basically lists your maps, functions, and commands and couples them with their associated source file.  When you then use :AN, :AsNeeded, or :ANX, AsNeeded will use that file to quickly load the associated source file.\r\n\r\nAnd, now for a user testimonal!\r\n\r\n    Zdenek Sekera (by permission)\r\n\r\n    I use FuncUndefined sometimes but most of the\r\n    time I use the AsNeeded mechanism of Dr.Chips,\r\n    which is very clever, very complete and completely\r\n    unintrusive, there is almost nothing to do once\r\n    the mechanics is setup.  It even finds functions\r\n    (mappings as well!!) inside a file of a different\r\n    name, etc...  Very pleasant.\r\n\r\n(alpha\/beta version available at http:\/\/www.drchip.org\/astronaut\/vim\/index.html#ASNEEDED)\r\n","4":"  [AsNeeded V14 AND LATER REQUIRES VIMBALL V18 OR LATER FOR UNPACKING]\r\n\r\nThe AsNeeded plugin loads plugins from the .vim\/AsNeeded directory only as they're needed.  One major advantage over vim 7.0's autoload method is: plugins don't need to be changed!   Just put the plugin in the AsNeeded directory (usually under .vim\/ or vimfiles\\).  It'll work even better if you type :MkAsNeeded while in vim after having updated your AsNeeded directory, too.\r\n\r\nSo, how does it work?  Well, whenever a plugin attempts to execute a function that hasn't been loaded yet, AsNeeded will find the script in the AsNeeded directory, load the script, and execute the function.\r\n\r\nAnd, whenever you want to execute a command that's not been loaded yet, and you've run :MkAsNeeded, then the plugin will be transparently loaded and the command executed!  If you didn't do :MkAsNeeded, or you wish to use a map, then instead you can use\r\n\r\n\t:AN map\r\n\t:AN command [arguments]\r\n\r\nand AsNeeded will locate the map or command, load the script, and make the map or command available for your subsequent use.  Alternatively, you can use\r\n\r\n\t:ANX map\r\n\t:ANX command [arguments]\r\n\r\nand AsNeeded will do what :AN would do plus attempt to execute the map or command.\r\n\r\nFor even faster loading of your desired function, map, or command, you can (as of v6) use\r\n\r\n\t:MkAsNeeded\r\n\r\nThis command will create a <ANtags> file in your AsNeeded subdirectory which basically lists your maps, functions, and commands and couples them with their associated source file.  When you then use :AN, :AsNeeded, or :ANX, AsNeeded will use that file to quickly load the associated source file.\r\n\r\nAnd, now for a user testimonal!\r\n\r\n    Zdenek Sekera (by permission)\r\n\r\n    I use FuncUndefined sometimes but most of the\r\n    time I use the AsNeeded mechanism of Dr.Chips,\r\n    which is very clever, very complete and completely\r\n    unintrusive, there is almost nothing to do once\r\n    the mechanics is setup.  It even finds functions\r\n    (mappings as well!!) inside a file of a different\r\n    name, etc...  Very pleasant.\r\n\r\n(alpha\/beta version available at http:\/\/www.drchip.org\/astronaut\/vim\/index.html#ASNEEDED)\r\n","install_details":"1. In your <.vimrc>: to enable plugins,\r\n   set nocp\r\n   if version >= 600\r\n     filetype plugin on\r\n   endif\r\n\r\n2. Make a <.vim\/AsNeeded> directory:\r\n   cd .vim\r\n   mkdir AsNeeded\r\n\r\n3. Put whatever plugins you want into the AsNeeded directory\r\n\r\n4. Use vim 7.1 or later, or update vim 7.0's vimball plugin with vimscript#1502.\r\n\r\n5. vim AsNeeded.vba.gz\r\n     :so %\r\n    :q\r\n","5":"1. In your <.vimrc>: to enable plugins,\r\n   set nocp\r\n   if version >= 600\r\n     filetype plugin on\r\n   endif\r\n\r\n2. Make a <.vim\/AsNeeded> directory:\r\n   cd .vim\r\n   mkdir AsNeeded\r\n\r\n3. Put whatever plugins you want into the AsNeeded directory\r\n\r\n4. Use vim 7.1 or later, or update vim 7.0's vimball plugin with vimscript#1502.\r\n\r\n5. vim AsNeeded.vba.gz\r\n     :so %\r\n    :q\r\n","first_name":"Charles","6":"Charles","last_name":"Campbell","7":"Campbell","releases":[{"0":"915","vim_version":"7.0","1":"7.0","script_version":"16","2":"16","version_comment":"<*> ANtags now smaller (uses relative paths)\r\n<*> saves and restore magic setting\r\n<*> MkAsNeeded creates a menu: DrChip.ANmenu full of commands that AsNeeded can load\r\n<*> Improved cmdsrch\r\n","3":"<*> ANtags now smaller (uses relative paths)\r\n<*> saves and restore magic setting\r\n<*> MkAsNeeded creates a menu: DrChip.ANmenu full of commands that AsNeeded can load\r\n<*> Improved cmdsrch\r\n","package":"AsNeeded.vba.gz","4":"AsNeeded.vba.gz","src_id":"9224","5":"9224","creation_date":"1220523189","6":"1220523189"},{"0":"915","vim_version":"6.0","1":"6.0","script_version":"15","2":"15","version_comment":"Various bugfixes to automatic updating of ANtags and improvements to handling of no user-specified mapleader.\r\n","3":"Various bugfixes to automatic updating of ANtags and improvements to handling of no user-specified mapleader.\r\n","package":"AsNeeded.vba.gz","4":"AsNeeded.vba.gz","src_id":"6778","5":"6778","creation_date":"1172232647","6":"1172232647"},{"0":"915","vim_version":"7.0","1":"7.0","script_version":"14","2":"14","version_comment":"(-NEW-)  Setting a variable, g:AsNeededAutoMake, to something like \"ls -1l\", lets AsNeeded keep ANtags and ANcmds up-to-date automatically!\r\n(bugfix) Taglist does a quick-loading trick that involved using FuncUndefined autocmds.  AsNeeded now defers to taglist instead of issuing a warning.\r\n(bugfix) ei=all was inadvertently being left on; thus no autocmds were operational after AsNeeded successfully loaded a function.  Fixed!\r\n(bugfix) included |'patchmode'| in the SaveSettings() and RestoreSettings() bypass functions\r\n","3":"(-NEW-)  Setting a variable, g:AsNeededAutoMake, to something like \"ls -1l\", lets AsNeeded keep ANtags and ANcmds up-to-date automatically!\r\n(bugfix) Taglist does a quick-loading trick that involved using FuncUndefined autocmds.  AsNeeded now defers to taglist instead of issuing a warning.\r\n(bugfix) ei=all was inadvertently being left on; thus no autocmds were operational after AsNeeded successfully loaded a function.  Fixed!\r\n(bugfix) included |'patchmode'| in the SaveSettings() and RestoreSettings() bypass functions\r\n","package":"AsNeeded.vba.gz","4":"AsNeeded.vba.gz","src_id":"6204","5":"6204","creation_date":"1158666945","6":"1158666945"},{"0":"915","vim_version":"7.0","1":"7.0","script_version":"13","2":"13","version_comment":"AsNeeded now uses Thomas's idea for producing a \"ANcmds.vim\" plugin with skeleton commands. Plus some bugfixes.  With this feature, commands in scripts in the AsNeeded\/ directory act as if they're always available, even when the scripts haven't been loaded.\r\n","3":"AsNeeded now uses Thomas's idea for producing a \"ANcmds.vim\" plugin with skeleton commands. Plus some bugfixes.  With this feature, commands in scripts in the AsNeeded\/ directory act as if they're always available, even when the scripts haven't been loaded.\r\n","package":"AsNeeded.vba.gz","4":"AsNeeded.vba.gz","src_id":"5719","5":"5719","creation_date":"1147937460","6":"1147937460"},{"0":"915","vim_version":"6.0","1":"6.0","script_version":"12","2":"12","version_comment":"(bugfix) AsNeeded needs to work around several options that the user may set.  However, if a plugin changed one of these, AsNeeded \"restored\" the option at the time that AsNeeded was invoked, thereby overriding whatever the plugin\/map etc may have set.  AsNeeded now restores the options, then sources the plugin\/map etc.","3":"(bugfix) AsNeeded needs to work around several options that the user may set.  However, if a plugin changed one of these, AsNeeded \"restored\" the option at the time that AsNeeded was invoked, thereby overriding whatever the plugin\/map etc may have set.  AsNeeded now restores the options, then sources the plugin\/map etc.","package":"AsNeeded.vim.gz","4":"AsNeeded.vim.gz","src_id":"5429","5":"5429","creation_date":"1142325176","6":"1142325176"},{"0":"915","vim_version":"6.0","1":"6.0","script_version":"11","2":"11","version_comment":"Bugfixes (success message itself sometimes caused an error, internally used buffers now wiped silently, keeps\/restores lz)\r\n","3":"Bugfixes (success message itself sometimes caused an error, internally used buffers now wiped silently, keeps\/restores lz)\r\n","package":"AsNeeded.vim.gz","4":"AsNeeded.vim.gz","src_id":"5145","5":"5145","creation_date":"1139561484","6":"1139561484"},{"0":"915","vim_version":"6.0","1":"6.0","script_version":"10","2":"10","version_comment":"bugfix: maps with backslashes are escaped so they can be found\r\nbugfix: report option workaround\r\n","3":"bugfix: maps with backslashes are escaped so they can be found\r\nbugfix: report option workaround\r\n","package":"AsNeeded.vim.gz","4":"AsNeeded.vim.gz","src_id":"4789","5":"4789","creation_date":"1132559255","6":"1132559255"},{"0":"915","vim_version":"6.0","1":"6.0","script_version":"9","2":"9","version_comment":"MakeANtags command and function search patterns improved\r\n","3":"MakeANtags command and function search patterns improved\r\n","package":"AsNeeded.vim.gz","4":"AsNeeded.vim.gz","src_id":"4423","5":"4423","creation_date":"1121148713","6":"1121148713"},{"0":"915","vim_version":"6.0","1":"6.0","script_version":"8","2":"8","version_comment":"Another bug fix; this time, for some maps, tags were being generated but not executed.  Fixed!\r\n","3":"Another bug fix; this time, for some maps, tags were being generated but not executed.  Fixed!\r\n","package":"AsNeeded.vim.gz","4":"AsNeeded.vim.gz","src_id":"3877","5":"3877","creation_date":"1108641557","6":"1108641557"},{"0":"915","vim_version":"6.0","1":"6.0","script_version":"7","2":"7","version_comment":"MakeANtags now warns the user when no tags were found for each scriptfile it examines in the AsNeeded directory.\r\nTwo bugfixes: MakeANtags was missing some maps and, under Windows, was omitting backslashes in paths.  Fixed!\r\n","3":"MakeANtags now warns the user when no tags were found for each scriptfile it examines in the AsNeeded directory.\r\nTwo bugfixes: MakeANtags was missing some maps and, under Windows, was omitting backslashes in paths.  Fixed!\r\n","package":"AsNeeded.vim.gz","4":"AsNeeded.vim.gz","src_id":"3870","5":"3870","creation_date":"1108546159","6":"1108546159"}]},"914":{"script_id":"914","0":"914","script_name":"sieve.vim","1":"sieve.vim","script_type":"syntax","2":"syntax","summary":"sieve mail filter syntax file","3":"sieve mail filter syntax file","description":"The sieve syntax file is based on 'Sieve: A Mail Filtering Language' (RFC3028) by The Internet Society 2001 (http:\/\/www.faqs.org\/rfcs\/rfc3028.html).\r\n\r\nSieve is a proposed internet-standard language for effectively filtering mail. It can delete mail, redirect messages other mail boces or automatically save mail into a specific folder.\r\n\r\nA good overview of the language and its capabilities can be found at http:\/\/www.cyrusoft.com\/sieve\/.\r\n\r\nFor an installation follow the instructions in ':help syntax'.","4":"The sieve syntax file is based on 'Sieve: A Mail Filtering Language' (RFC3028) by The Internet Society 2001 (http:\/\/www.faqs.org\/rfcs\/rfc3028.html).\r\n\r\nSieve is a proposed internet-standard language for effectively filtering mail. It can delete mail, redirect messages other mail boces or automatically save mail into a specific folder.\r\n\r\nA good overview of the language and its capabilities can be found at http:\/\/www.cyrusoft.com\/sieve\/.\r\n\r\nFor an installation follow the instructions in ':help syntax'.","install_details":":help syntax","5":":help syntax","first_name":"Michael M.","6":"Michael M.","last_name":"Tung","7":"Tung","releases":[{"0":"914","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"sieve.vim","4":"sieve.vim","src_id":"2761","5":"2761","creation_date":"1077183421","6":"1077183421"}]},"913":{"script_id":"913","0":"913","script_name":"po.vim","1":"po.vim","script_type":"syntax","2":"syntax","summary":"Gettext PO syntax highlighting","3":"Gettext PO syntax highlighting","description":"This version of po.vim enhances the default PO syntax highlighting within vim to add the following new features and improvements:\r\n\r\n* Gettext context entries are highlighted\r\n* Allows spell checking in msgstr\r\n\r\nPlease test and report bugs or ask for new feature by emailing dwayne@translate.org.za\r\n\r\nNOTE: The long list of original features have been upstreamed and are available in a default vim installation.","4":"This version of po.vim enhances the default PO syntax highlighting within vim to add the following new features and improvements:\r\n\r\n* Gettext context entries are highlighted\r\n* Allows spell checking in msgstr\r\n\r\nPlease test and report bugs or ask for new feature by emailing dwayne@translate.org.za\r\n\r\nNOTE: The long list of original features have been upstreamed and are available in a default vim installation.","install_details":"Installing the syntax highlighter\r\n--------------------------------------------\r\nPlace in your local .vim\/syntax\r\nor\r\nOn Fedora place in \/usr\/share\/vim\/vim71\/syntax for the new PO highlighting to be available to everyone.  This should be a similar place for other distributions.\r\n\r\nEnabling spell checking\r\n---------------------------\r\nTo enable the Afrikaans (af) spell checker type:\r\n:set spell spelllang=af\r\n\r\nNow for further help on using spell checking:\r\n:help spell","5":"Installing the syntax highlighter\r\n--------------------------------------------\r\nPlace in your local .vim\/syntax\r\nor\r\nOn Fedora place in \/usr\/share\/vim\/vim71\/syntax for the new PO highlighting to be available to everyone.  This should be a similar place for other distributions.\r\n\r\nEnabling spell checking\r\n---------------------------\r\nTo enable the Afrikaans (af) spell checker type:\r\n:set spell spelllang=af\r\n\r\nNow for further help on using spell checking:\r\n:help spell","first_name":"Dwayne","6":"Dwayne","last_name":"Bailey","7":"Bailey","releases":[{"0":"913","vim_version":"7.0","1":"7.0","script_version":"20080108","2":"20080108","version_comment":"Further improvement to spell checking [Contributed by Leonardo Fontenelle]","3":"Further improvement to spell checking [Contributed by Leonardo Fontenelle]","package":"po.vim","4":"po.vim","src_id":"8528","5":"8528","creation_date":"1207532399","6":"1207532399"},{"0":"913","vim_version":"7.0","1":"7.0","script_version":"20070823","2":"20070823","version_comment":"Adds the ability to spell check translated text (Contributed by: Leonardo Fontenelle)","3":"Adds the ability to spell check translated text (Contributed by: Leonardo Fontenelle)","package":"po.vim","4":"po.vim","src_id":"7547","5":"7547","creation_date":"1187833573","6":"1187833573"},{"0":"913","vim_version":"6.0","1":"6.0","script_version":"20060127","2":"20060127","version_comment":"* Highlight msgctxt (message context tags) - new in Gettext\r\n* Message context is shown highlighted as a comment\r\n* Unset plural forms in headers are now also highlighted","3":"* Highlight msgctxt (message context tags) - new in Gettext\r\n* Message context is shown highlighted as a comment\r\n* Unset plural forms in headers are now also highlighted","package":"po.vim","4":"po.vim","src_id":"5006","5":"5006","creation_date":"1138370099","6":"1138370099"},{"0":"913","vim_version":"6.0","1":"6.0","script_version":"20041113","2":"20041113","version_comment":"msguniq and msgcat conflicts are highlighted correctly even if the #-#-#-#-# is split over two lines.","3":"msguniq and msgcat conflicts are highlighted correctly even if the #-#-#-#-# is split over two lines.","package":"po.vim","4":"po.vim","src_id":"3625","5":"3625","creation_date":"1100350492","6":"1100350492"},{"0":"913","vim_version":"6.0","1":"6.0","script_version":"20040209","2":"20040209","version_comment":"Initial upload","3":"Initial upload","package":"po.vim","4":"po.vim","src_id":"2758","5":"2758","creation_date":"1077171005","6":"1077171005"}]},"912":{"script_id":"912","0":"912","script_name":"adam.vim : Adam's Good Color Scheme","1":"adam.vim : Adam's Good Color Scheme","script_type":"color scheme","2":"color scheme","summary":"A well colored, dark background color scheme.","3":"A well colored, dark background color scheme.","description":"Not being totally satisfied with other color schemes out there, I created my own scheme.\r\n\r\nIt has a dark blue-grey background and uses a diverse set of attractive and constracting colors for foreground text.\r\n\r\nI use it largely for Java and XSL development although I'm also quite content with how C++ and ASP code looks in it too.\r\n\r\nThe only draw back to this color scheme is that while on a CRT monitor the colors appear quite clear and constrasting, the contrast dies out a bit on my laptop's screen. (For use on laptop screens, I would recommend making the background black.)","4":"Not being totally satisfied with other color schemes out there, I created my own scheme.\r\n\r\nIt has a dark blue-grey background and uses a diverse set of attractive and constracting colors for foreground text.\r\n\r\nI use it largely for Java and XSL development although I'm also quite content with how C++ and ASP code looks in it too.\r\n\r\nThe only draw back to this color scheme is that while on a CRT monitor the colors appear quite clear and constrasting, the contrast dies out a bit on my laptop's screen. (For use on laptop screens, I would recommend making the background black.)","install_details":"Place in VIM's colors directory, like any other color scheme.","5":"Place in VIM's colors directory, like any other color scheme.","first_name":"Adam","6":"Adam","last_name":"Krouskop","7":"Krouskop","releases":[{"0":"912","vim_version":"6.0","1":"6.0","script_version":"1.0.1","2":"1.0.1","version_comment":"Initial upload had incorrect header comments.","3":"Initial upload had incorrect header comments.","package":"adam.vim","4":"adam.vim","src_id":"2757","5":"2757","creation_date":"1077109545","6":"1077109545"}]},"911":{"script_id":"911","0":"911","script_name":"nedit2","1":"nedit2","script_type":"color scheme","2":"color scheme","summary":"Color scheme based on nedit","3":"Color scheme based on nedit","description":"A simple color scheme based on nedit (Vladimir Vrzic)","4":"A simple color scheme based on nedit (Vladimir Vrzic)","install_details":"Usage: put in your $VIMDIR\/colors directory \r\n  then type \":colorscheme nedit2\"","5":"Usage: put in your $VIMDIR\/colors directory \r\n  then type \":colorscheme nedit2\"","first_name":"Marco","6":"Marco","last_name":"Dalla Stella","7":"Dalla Stella","releases":[{"0":"911","vim_version":"6.0","1":"6.0","script_version":"2.0.2","2":"2.0.2","version_comment":"A minor fix on cursor color.","3":"A minor fix on cursor color.","package":"nedit2.vim","4":"nedit2.vim","src_id":"2829","5":"2829","creation_date":"1079168755","6":"1079168755"},{"0":"911","vim_version":"6.0","1":"6.0","script_version":"2.0.1","2":"2.0.1","version_comment":"Sorry, I uploaded the wrong one!","3":"Sorry, I uploaded the wrong one!","package":"nedit2.vim","4":"nedit2.vim","src_id":"2748","5":"2748","creation_date":"1076642206","6":"1076642206"},{"0":"911","vim_version":"6.0","1":"6.0","script_version":"2.0","2":"2.0","version_comment":"Initial upload","3":"Initial upload","package":"nedit2.vim","4":"nedit2.vim","src_id":"2746","5":"2746","creation_date":"1076641056","6":"1076641056"}]},"910":{"script_id":"910","0":"910","script_name":"python_pydoc.vim","1":"python_pydoc.vim","script_type":"utility","2":"utility","summary":"Python documentation view- and search-tool (uses pydoc)","3":"Python documentation view- and search-tool (uses pydoc)","description":"This plugin integrates the Python documentation view and search tool pydoc into Vim. It allows you to view the documentation of a Python module or class by typing:\r\n\r\n:Pydoc foo.bar.baz (e.g. :Pydoc re.compile)\r\n\r\nOr search a word (uses pydoc -k) in the documentation by typing:\r\n\r\n:PydocSearch foobar (e.g. :PydocSearch socket)\r\n\r\nVim will split the current window to show the Python documentation found by pydoc (the buffer will be called '__doc__', Pythonic, isn't it ;-) ). The name may cause problems if you have a file with the same name, but usually this should not happen.\r\n\r\npydoc.vim also allows you to view the documentation of the 'word' (see :help word) under the cursor by pressing <Leader>pw or the 'WORD' (see :help WORD) under the cursor by pressing <Leader>pW. This is very useful if you want to jump to the docs of a module or class found by 'PydocSearch' or if you want to see the docs of a module\/class in your source code. Additionally K is mapped to show invoke pydoc as well, when you are editing python files.\r\n\r\nThe script is developed in GitHub at:\r\n\r\nhttp:\/\/github.com\/fs111\/pydoc.vim\r\n\r\nIf you want to use the script and pydoc is not in your PATH, just put a line like this in your .vimrc:\r\n\r\nlet g:pydoc_cmd = '\/usr\/bin\/pydoc'\r\n\r\nor more portable\r\n\r\nlet g:pydoc_cmd = 'python -m pydoc'\r\n\r\nIf you want to open pydoc files in vertical splits or tabs, give the appropriate command in your .vimrc with:\r\n\r\nlet g:pydoc_open_cmd = 'vsplit'\r\n\r\nor\r\n\r\nlet g:pydoc_open_cmd = 'tabnew'\r\n\r\nThe script will highlight the search term by default. To disable this behaviour put in your .vimrc:\r\n\r\nlet g:pydoc_highlight=0\r\n\r\nMany, many thanks to all the fine folks that contributed patches so far!","4":"This plugin integrates the Python documentation view and search tool pydoc into Vim. It allows you to view the documentation of a Python module or class by typing:\r\n\r\n:Pydoc foo.bar.baz (e.g. :Pydoc re.compile)\r\n\r\nOr search a word (uses pydoc -k) in the documentation by typing:\r\n\r\n:PydocSearch foobar (e.g. :PydocSearch socket)\r\n\r\nVim will split the current window to show the Python documentation found by pydoc (the buffer will be called '__doc__', Pythonic, isn't it ;-) ). The name may cause problems if you have a file with the same name, but usually this should not happen.\r\n\r\npydoc.vim also allows you to view the documentation of the 'word' (see :help word) under the cursor by pressing <Leader>pw or the 'WORD' (see :help WORD) under the cursor by pressing <Leader>pW. This is very useful if you want to jump to the docs of a module or class found by 'PydocSearch' or if you want to see the docs of a module\/class in your source code. Additionally K is mapped to show invoke pydoc as well, when you are editing python files.\r\n\r\nThe script is developed in GitHub at:\r\n\r\nhttp:\/\/github.com\/fs111\/pydoc.vim\r\n\r\nIf you want to use the script and pydoc is not in your PATH, just put a line like this in your .vimrc:\r\n\r\nlet g:pydoc_cmd = '\/usr\/bin\/pydoc'\r\n\r\nor more portable\r\n\r\nlet g:pydoc_cmd = 'python -m pydoc'\r\n\r\nIf you want to open pydoc files in vertical splits or tabs, give the appropriate command in your .vimrc with:\r\n\r\nlet g:pydoc_open_cmd = 'vsplit'\r\n\r\nor\r\n\r\nlet g:pydoc_open_cmd = 'tabnew'\r\n\r\nThe script will highlight the search term by default. To disable this behaviour put in your .vimrc:\r\n\r\nlet g:pydoc_highlight=0\r\n\r\nMany, many thanks to all the fine folks that contributed patches so far!","install_details":"In order to install pydoc.vim download it from vim.org or clone the repository on githubi and put it in your .vim\/ftplugin directory. pydoc.vim is also fully\r\ncompatible with pathogen, so cloning the repository into your bundle directory is also a valid way to install it. (I do this myself. see https:\/\/github.com\/fs111\/dotvim).\r\n\r\nIf the pydoc-command is not in your PATH, you can put a line like let g:pydoc_cmd = \"\/usr\/bin\/pydoc\"  in your .vimrc to get it working. The script will highlight the search-term by default. To disable this behaviour put \"let g:pydoc_highlight=0\" in your .vimrc.\r\n\r\nNote: You do not need a python enabled version of vim to use pydoc.vim, everything is done with plain vim scripting and should work on any version >6.","5":"In order to install pydoc.vim download it from vim.org or clone the repository on githubi and put it in your .vim\/ftplugin directory. pydoc.vim is also fully\r\ncompatible with pathogen, so cloning the repository into your bundle directory is also a valid way to install it. (I do this myself. see https:\/\/github.com\/fs111\/dotvim).\r\n\r\nIf the pydoc-command is not in your PATH, you can put a line like let g:pydoc_cmd = \"\/usr\/bin\/pydoc\"  in your .vimrc to get it working. The script will highlight the search-term by default. To disable this behaviour put \"let g:pydoc_highlight=0\" in your .vimrc.\r\n\r\nNote: You do not need a python enabled version of vim to use pydoc.vim, everything is done with plain vim scripting and should work on any version >6.","first_name":"Andr\u00c3\u00a9","6":"Andr\u00c3\u00a9","last_name":"Kelpe","7":"Kelpe","releases":[{"0":"910","vim_version":"7.0","1":"7.0","script_version":"2.0","2":"2.0","version_comment":"pydoc.vim has completely changed: It is now a ftplugin instead of a plugin. It supports the K mapping and has a pathogen friendly repository on github.","3":"pydoc.vim has completely changed: It is now a ftplugin instead of a plugin. It supports the K mapping and has a pathogen friendly repository on github.","package":"python_pydoc.vim","4":"python_pydoc.vim","src_id":"18164","5":"18164","creation_date":"1340143374","6":"1340143374"},{"0":"910","vim_version":"6.0","1":"6.0","script_version":"1.3.6","2":"1.3.6","version_comment":"included fix by Thomas Vander Stichele for 'K' handling: https:\/\/github.com\/fs111\/pydoc.vim\/commit\/14ffe6cdd74e086271e4eb07ba94fe4bd5b94e26","3":"included fix by Thomas Vander Stichele for 'K' handling: https:\/\/github.com\/fs111\/pydoc.vim\/commit\/14ffe6cdd74e086271e4eb07ba94fe4bd5b94e26","package":"pydoc.vim","4":"pydoc.vim","src_id":"14691","5":"14691","creation_date":"1294331312","6":"1294331312"},{"0":"910","vim_version":"6.0","1":"6.0","script_version":"1.3.5","2":"1.3.5","version_comment":" disabled call to \"syn on\" in Highlight, since that seems to interfere with NERDTree and also avoid using global variables, as suggested by Jason Mills","3":" disabled call to \"syn on\" in Highlight, since that seems to interfere with NERDTree and also avoid using global variables, as suggested by Jason Mills","package":"pydoc.vim","4":"pydoc.vim","src_id":"14349","5":"14349","creation_date":"1290460007","6":"1290460007"},{"0":"910","vim_version":"6.0","1":"6.0","script_version":"1.3.3","2":"1.3.3","version_comment":"small bugfix: when pydoc.vim is an ftplugin, it gives a warning of redefining a command. From now on it uses command! to avoid this. Thanks to Jason Mills for the patch.","3":"small bugfix: when pydoc.vim is an ftplugin, it gives a warning of redefining a command. From now on it uses command! to avoid this. Thanks to Jason Mills for the patch.","package":"pydoc.vim","4":"pydoc.vim","src_id":"14079","5":"14079","creation_date":"1287522024","6":"1287522024"},{"0":"910","vim_version":"6.0","1":"6.0","script_version":"1.3.2","2":"1.3.2","version_comment":"filter colons out of the search term so that you can use <leader>pW on constructs that end in a colon like \"if xxx in sys.modules:\" Thanks to Jonathan Hartley for making me aware of that problem.","3":"filter colons out of the search term so that you can use <leader>pW on constructs that end in a colon like \"if xxx in sys.modules:\" Thanks to Jonathan Hartley for making me aware of that problem.","package":"pydoc.vim","4":"pydoc.vim","src_id":"13092","5":"13092","creation_date":"1275501602","6":"1275501602"},{"0":"910","vim_version":"6.0","1":"6.0","script_version":"1.3.1","2":"1.3.1","version_comment":"new option ('g:pydoc_wh') to control the window height of the pydoc window implemented by Matthias Vogelgesang","3":"new option ('g:pydoc_wh') to control the window height of the pydoc window implemented by Matthias Vogelgesang","package":"pydoc.vim","4":"pydoc.vim","src_id":"12812","5":"12812","creation_date":"1271003171","6":"1271003171"},{"0":"910","vim_version":"6.0","1":"6.0","script_version":"1.2","2":"1.2","version_comment":"Lots of changes from Romain Chossart, thanks for that!\r\n\r\n- The buffer is not displayed (actually, it is displayed then deleted\r\nquickly) when \"no Python doc found\". If the buffer was already\r\ndisplayed, it does a \"u\" to go back to the last pydoc. A message is\r\ndisplayed if no corresponding doc is found.\r\nI did that because otherwise, it forces the user to close (or to type\r\n\"u\") for \"uninteresting results\".\r\n(implementation is not very pretty, but it does the job).\r\n- The mappings are only set for \"python\" and \"man\" filetypes (the\r\nlatter being useful for pydoc search inside pydoc)\r\n- Added two mappings : <leader>pk (for pydoc -k word) and <leader>pK\r\n(for pydoc -k WORD)","3":"Lots of changes from Romain Chossart, thanks for that!\r\n\r\n- The buffer is not displayed (actually, it is displayed then deleted\r\nquickly) when \"no Python doc found\". If the buffer was already\r\ndisplayed, it does a \"u\" to go back to the last pydoc. A message is\r\ndisplayed if no corresponding doc is found.\r\nI did that because otherwise, it forces the user to close (or to type\r\n\"u\") for \"uninteresting results\".\r\n(implementation is not very pretty, but it does the job).\r\n- The mappings are only set for \"python\" and \"man\" filetypes (the\r\nlatter being useful for pydoc search inside pydoc)\r\n- Added two mappings : <leader>pk (for pydoc -k word) and <leader>pK\r\n(for pydoc -k WORD)","package":"pydoc.vim","4":"pydoc.vim","src_id":"12723","5":"12723","creation_date":"1269792056","6":"1269792056"},{"0":"910","vim_version":"6.0","1":"6.0","script_version":"1.1.1","2":"1.1.1","version_comment":"The highlighting of the search-term is now optional and can be disabled.\r\nSet in  this in your .vimrc to disable the highlighting:\r\n\r\nlet g:pydoc_highlight=0\r\n\r\n","3":"The highlighting of the search-term is now optional and can be disabled.\r\nSet in  this in your .vimrc to disable the highlighting:\r\n\r\nlet g:pydoc_highlight=0\r\n\r\n","package":"pydoc.vim","4":"pydoc.vim","src_id":"3973","5":"3973","creation_date":"1110082051","6":"1110082051"},{"0":"910","vim_version":"6.0","1":"6.0","script_version":"1.1","2":"1.1","version_comment":"This updates adds a simple highlighting to pydoc.vim. All occurrences of your search-term will be highlighted. It uses gui=reverse to be color-scheme independent. ","3":"This updates adds a simple highlighting to pydoc.vim. All occurrences of your search-term will be highlighted. It uses gui=reverse to be color-scheme independent. ","package":"pydoc.vim","4":"pydoc.vim","src_id":"3637","5":"3637","creation_date":"1100519857","6":"1100519857"},{"0":"910","vim_version":"6.0","1":"6.0","script_version":"1.0.6","2":"1.0.6","version_comment":"Version 1.0.5 contains some debug code (call to \"input\" twice), this versions removes it. Sorry for that.","3":"Version 1.0.5 contains some debug code (call to \"input\" twice), this versions removes it. Sorry for that.","package":"pydoc.vim","4":"pydoc.vim","src_id":"3530","5":"3530","creation_date":"1097215734","6":"1097215734"},{"0":"910","vim_version":"6.0","1":"6.0","script_version":"1.0.4","2":"1.0.4","version_comment":"Changed the defaut mappings, because many other scripts are using the Function-keys. New mappings are <leader>pw for the current word and <leader>pW for the current Word.\r\n ","3":"Changed the defaut mappings, because many other scripts are using the Function-keys. New mappings are <leader>pw for the current word and <leader>pW for the current Word.\r\n ","package":"pydoc.vim","4":"pydoc.vim","src_id":"3239","5":"3239","creation_date":"1089957641","6":"1089957641"},{"0":"910","vim_version":"6.0","1":"6.0","script_version":"1.0.3","2":"1.0.3","version_comment":"another small bugfix, I hope the last for today!!","3":"another small bugfix, I hope the last for today!!","package":"pydoc.vim","4":"pydoc.vim","src_id":"2753","5":"2753","creation_date":"1076993549","6":"1076993549"},{"0":"910","vim_version":"6.0","1":"6.0","script_version":"1.0.2","2":"1.0.2","version_comment":"missing blank in \"pydoc -k\" fixed","3":"missing blank in \"pydoc -k\" fixed","package":"pydoc.vim","4":"pydoc.vim","src_id":"2752","5":"2752","creation_date":"1076992348","6":"1076992348"},{"0":"910","vim_version":"6.0","1":"6.0","script_version":"1.0.1","2":"1.0.1","version_comment":"This version uses the g:pydoc_cmd variable which makes the script usable if the pydoc command is not in  your PATH. This may also work an Windows, but I can't test that. Feedback welcome. Just put a line like \r\n\r\nlet g:pydoc_cmd = \"\/usr\/bin\/pydoc\"\r\n\r\ninto your .vimrc and the scritp will use the specified command.\r\n","3":"This version uses the g:pydoc_cmd variable which makes the script usable if the pydoc command is not in  your PATH. This may also work an Windows, but I can't test that. Feedback welcome. Just put a line like \r\n\r\nlet g:pydoc_cmd = \"\/usr\/bin\/pydoc\"\r\n\r\ninto your .vimrc and the scritp will use the specified command.\r\n","package":"pydoc.vim","4":"pydoc.vim","src_id":"2749","5":"2749","creation_date":"1076912196","6":"1076912196"},{"0":"910","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"pydoc.vim","4":"pydoc.vim","src_id":"2744","5":"2744","creation_date":"1076580412","6":"1076580412"}]},"909":{"script_id":"909","0":"909","script_name":"unicodeswitch.vim","1":"unicodeswitch.vim","script_type":"ftplugin","2":"ftplugin","summary":" Vim file plugin for editing files with unicode codes.","3":" Vim file plugin for editing files with unicode codes.","description":"Vim file plugin for editing files with unicode codes.\r\n\r\nIt changes all of the codes to the accented characters for viewing, and turns all accented characters into the code when writing.\r\n\r\ne.g. it changes \\u00E9 to \u00c3\u00a9 when viewing, and puts \\u00E9 when writing (java-style encoding). Set g:ucs_encode_java (in your .vimrc file)\r\n\r\nBy default, it works for all the accented characters in the Unicode Latin-1 supplement, but you can quickly change it for your needs.\r\n\r\nYou can also set it to work with html encoding (&#nnn;). Set g:ucs_encode_html (in your .vimrc file)\r\n\r\nYou can also set it to convert accented characters to octal encoding ( \\340 ). Set g:ucs_encode_octal in your\r\n.vimrc file\r\n\r\n\r\nIf you want to turn the switching on and off for reading and\/or writing, you can easily do so by commenting out the autocmd lines.  e.g. if you comment out the BufWrite autocmds, then you can read in \\u00aa style and write out the utf encoding.  Or, you could swap the BufRead and BufWrite commands, and do the opposite transformation.\r\n\r\nfor help with the accented characters, see :help digraph\r\n\r\ncopied\/mangled from vimscript #284, which does it for TeX codes\r\n","4":"Vim file plugin for editing files with unicode codes.\r\n\r\nIt changes all of the codes to the accented characters for viewing, and turns all accented characters into the code when writing.\r\n\r\ne.g. it changes \\u00E9 to \u00c3\u00a9 when viewing, and puts \\u00E9 when writing (java-style encoding). Set g:ucs_encode_java (in your .vimrc file)\r\n\r\nBy default, it works for all the accented characters in the Unicode Latin-1 supplement, but you can quickly change it for your needs.\r\n\r\nYou can also set it to work with html encoding (&#nnn;). Set g:ucs_encode_html (in your .vimrc file)\r\n\r\nYou can also set it to convert accented characters to octal encoding ( \\340 ). Set g:ucs_encode_octal in your\r\n.vimrc file\r\n\r\n\r\nIf you want to turn the switching on and off for reading and\/or writing, you can easily do so by commenting out the autocmd lines.  e.g. if you comment out the BufWrite autocmds, then you can read in \\u00aa style and write out the utf encoding.  Or, you could swap the BufRead and BufWrite commands, and do the opposite transformation.\r\n\r\nfor help with the accented characters, see :help digraph\r\n\r\ncopied\/mangled from vimscript #284, which does it for TeX codes\r\n","install_details":"Usage: put in your $VIMDIR\/plugin directory, set one of the variables\r\n  either \r\n let g:ucs_encode_java = 1 \r\nor \r\n let g:ucs_encode_html = 1 \r\nor\r\n let g:ucs_encode_octal = 1\r\nin your .vimrc file\r\n","5":"Usage: put in your $VIMDIR\/plugin directory, set one of the variables\r\n  either \r\n let g:ucs_encode_java = 1 \r\nor \r\n let g:ucs_encode_html = 1 \r\nor\r\n let g:ucs_encode_octal = 1\r\nin your .vimrc file\r\n","first_name":"Roger","6":"Roger","last_name":"Pilkey","7":"Pilkey","releases":[{"0":"909","vim_version":"6.0","1":"6.0","script_version":"1.7","2":"1.7","version_comment":"added octal ( \\233 )switch, fixed up the html switch","3":"added octal ( \\233 )switch, fixed up the html switch","package":"unicodeswitch.vim","4":"unicodeswitch.vim","src_id":"7160","5":"7160","creation_date":"1179945061","6":"1179945061"},{"0":"909","vim_version":"6.0","1":"6.0","script_version":"1.6","2":"1.6","version_comment":"bugfix: correct the hex char match variable to only match up to 4 chars.","3":"bugfix: correct the hex char match variable to only match up to 4 chars.","package":"unicodeswitch.vim","4":"unicodeswitch.vim","src_id":"3084","5":"3084","creation_date":"1086078031","6":"1086078031"},{"0":"909","vim_version":"6.0","1":"6.0","script_version":"1.5","2":"1.5","version_comment":"fix for higher numbered chars (above \\u00ff)","3":"fix for higher numbered chars (above \\u00ff)","package":"unicodeswitch.vim","4":"unicodeswitch.vim","src_id":"2985","5":"2985","creation_date":"1083261172","6":"1083261172"},{"0":"909","vim_version":"6.0","1":"6.0","script_version":"1.4","2":"1.4","version_comment":"Same as 1.3, but with unix line endings","3":"Same as 1.3, but with unix line endings","package":"unicodeswitch.vim","4":"unicodeswitch.vim","src_id":"2763","5":"2763","creation_date":"1077209489","6":"1077209489"},{"0":"909","vim_version":"6.0","1":"6.0","script_version":"1.3","2":"1.3","version_comment":"added html-style encoding (&#nnn;) and made the script more modular","3":"added html-style encoding (&#nnn;) and made the script more modular","package":"unicodeswitch.vim","4":"unicodeswitch.vim","src_id":"2760","5":"2760","creation_date":"1077173232","6":"1077173232"},{"0":"909","vim_version":"6.0","1":"6.0","script_version":"1.2","2":"1.2","version_comment":"fix write error, oops.","3":"fix write error, oops.","package":"unicodeswitch.vim","4":"unicodeswitch.vim","src_id":"2745","5":"2745","creation_date":"1076585397","6":"1076585397"},{"0":"909","vim_version":"6.0","1":"6.0","script_version":"1.1","2":"1.1","version_comment":"Initial upload","3":"Initial upload","package":"unicodeswitch.vim","4":"unicodeswitch.vim","src_id":"2743","5":"2743","creation_date":"1076571359","6":"1076571359"}]},"908":{"script_id":"908","0":"908","script_name":"deleted","1":"deleted","script_type":"utility","2":"utility","summary":"deleted","3":"deleted","description":"deleted","4":"deleted","install_details":"\r\n","5":"\r\n","first_name":"Antony","6":"Antony","last_name":"Scriven","7":"Scriven","releases":[{"0":"908","vim_version":"7.0","1":"7.0","script_version":"0.2","2":"0.2","version_comment":"empty","3":"empty","package":"nvi.vim","4":"nvi.vim","src_id":"24566","5":"24566","creation_date":"1475092423","6":"1475092423"}]},"907":{"script_id":"907","0":"907","script_name":"html_umlaute","1":"html_umlaute","script_type":"ftplugin","2":"ftplugin","summary":"replaces german Umlaute with their HTML Encoding on saving","3":"replaces german Umlaute with their HTML Encoding on saving","description":"Useful for all people who edit german websites with Vim.\r\nOn loading a HTML file, this script replaces all the html-encoded german Umlaute (&*uml;) with their normal Ascii-Chars (\u00c3\u00a4,\u00c3\u00b6,\u00c3\u00bc, and \u00c3\u009f) so they're more easily readable.\r\n\r\nWhen you save the file, all Ascii-Chars are replaced by the HTML Encoding. Could be extended to handle other chars as well (except for < > and \" which could only be replaced context-sensitive...) but I decided to use it only for these german letters...","4":"Useful for all people who edit german websites with Vim.\r\nOn loading a HTML file, this script replaces all the html-encoded german Umlaute (&*uml;) with their normal Ascii-Chars (\u00c3\u00a4,\u00c3\u00b6,\u00c3\u00bc, and \u00c3\u009f) so they're more easily readable.\r\n\r\nWhen you save the file, all Ascii-Chars are replaced by the HTML Encoding. Could be extended to handle other chars as well (except for < > and \" which could only be replaced context-sensitive...) but I decided to use it only for these german letters...","install_details":"put it into your ~\/.vim\/plugin\/ folder","5":"put it into your ~\/.vim\/plugin\/ folder","first_name":"Timo","6":"Timo","last_name":"Teifel","7":"Teifel","releases":[{"0":"907","vim_version":"6.0","1":"6.0","script_version":"1.1","2":"1.1","version_comment":"Initial upload","3":"Initial upload","package":"html_umlaute.vim","4":"html_umlaute.vim","src_id":"2740","5":"2740","creation_date":"1076506044","6":"1076506044"}]},"906":{"script_id":"906","0":"906","script_name":"Editable User Interface (EUI, eui_vim)","1":"Editable User Interface (EUI, eui_vim)","script_type":"utility","2":"utility","summary":"The use of a text editor as the user interface to applications.","3":"The use of a text editor as the user interface to applications.","description":"____________________________________________________________\r\nOverview\r\n\r\nThe plugin eui_vim concerns the use of a text editor as the user\r\ninterface to applications:  the \"Editable User Interface\".\r\n\r\nIt presents an alternative to incorporating applications into the\r\ntext editor as a tightly bound, monolithic product and to\r\nresisting any integration of the text-editor with other\r\napplications for non-text-editing functions.  \r\n\r\nThe conceptualization of the ''Editable User Interface'' helps\r\ndefine and delimit the role of the text editor in facilitating the\r\nuse of diverse applications.  In such a role, the text editor is\r\ndelimited to being an interface only, i.e., in regard to support\r\nof non-text-editing tasks, it is delimited to \r\n\r\n  * rendering user input,\r\n  * transferring user commands and data to the external application,\r\n  * responding to (text-editing) commands from the external application and\r\n  * rendering the external application's output to the user.  \r\n\r\n(In the above, rendering refers to display of text.)\r\n\r\nAs a specific example of the abstraction \"Editable User Interface\", \r\nthe code presented here, eui_vim.vim and eui_vim.pl illustrate how \r\none can use the Vim editor as an user interface to other applications.\r\n\r\n____________________________________________________________\r\nValue\r\n\r\nMost of the value of this plugin lies in the ideas expounded \r\nin eui_vim.txt or in http:\/\/www.sonic.net\/~suresh\/eui\/ \r\n(and, perhaps, by way of the comments in the .vim and .pl code).\r\n\r\n____________________________________________________________\r\nTable of Contents of eui_vim.txt\r\n\r\nIntroduction\r\n  Graphical, Keyboard and Pseudo-keyboard User Interfaces\r\n  Editable User Interface\r\n    The Text Editor\r\n    The PC as a Product\r\nUsers' Guide\r\n  Preliminaries\r\n    System Requirements\r\n    Download\r\n    Installation\r\n  Tutorial\r\n    :EUIProcess foo\r\n    :EUIProcess list\r\n    :EUIProcess demo_plot\r\n    How the transfers are done\r\n      Format of the fifo-file\r\n    :EUIProcess quit\r\n    Automatic clean-up\r\nExample Applications\r\n  VimPuppy\r\n  Vimms\r\nAuthor\r\nClaims\r\nCopyright\r\nDisclaimer\r\n\r\n","4":"____________________________________________________________\r\nOverview\r\n\r\nThe plugin eui_vim concerns the use of a text editor as the user\r\ninterface to applications:  the \"Editable User Interface\".\r\n\r\nIt presents an alternative to incorporating applications into the\r\ntext editor as a tightly bound, monolithic product and to\r\nresisting any integration of the text-editor with other\r\napplications for non-text-editing functions.  \r\n\r\nThe conceptualization of the ''Editable User Interface'' helps\r\ndefine and delimit the role of the text editor in facilitating the\r\nuse of diverse applications.  In such a role, the text editor is\r\ndelimited to being an interface only, i.e., in regard to support\r\nof non-text-editing tasks, it is delimited to \r\n\r\n  * rendering user input,\r\n  * transferring user commands and data to the external application,\r\n  * responding to (text-editing) commands from the external application and\r\n  * rendering the external application's output to the user.  \r\n\r\n(In the above, rendering refers to display of text.)\r\n\r\nAs a specific example of the abstraction \"Editable User Interface\", \r\nthe code presented here, eui_vim.vim and eui_vim.pl illustrate how \r\none can use the Vim editor as an user interface to other applications.\r\n\r\n____________________________________________________________\r\nValue\r\n\r\nMost of the value of this plugin lies in the ideas expounded \r\nin eui_vim.txt or in http:\/\/www.sonic.net\/~suresh\/eui\/ \r\n(and, perhaps, by way of the comments in the .vim and .pl code).\r\n\r\n____________________________________________________________\r\nTable of Contents of eui_vim.txt\r\n\r\nIntroduction\r\n  Graphical, Keyboard and Pseudo-keyboard User Interfaces\r\n  Editable User Interface\r\n    The Text Editor\r\n    The PC as a Product\r\nUsers' Guide\r\n  Preliminaries\r\n    System Requirements\r\n    Download\r\n    Installation\r\n  Tutorial\r\n    :EUIProcess foo\r\n    :EUIProcess list\r\n    :EUIProcess demo_plot\r\n    How the transfers are done\r\n      Format of the fifo-file\r\n    :EUIProcess quit\r\n    Automatic clean-up\r\nExample Applications\r\n  VimPuppy\r\n  Vimms\r\nAuthor\r\nClaims\r\nCopyright\r\nDisclaimer\r\n\r\n","install_details":"____________________________________________________________\r\nSystem Requirements\r\n\r\nEui_vim has been tested on Windows 98 with the ''Big version with\r\nGUI'' Vim 6.2 (requires +clientserver, but perl support is not\r\nrequired).  It is unlikely to work as-is on unix (the port to \r\nunix is likely to be simpler).\r\n\r\n____________________________________________________________\r\nInstallation\r\n\r\nEssentially, unzip eui_vim.zip into the vimfiles directory while\r\npreserving folder names and regenerate the help-tags.  \r\n\r\nUnzipping deploys three files:  \r\n\r\n    vimfiles\\plugin\\eui_vim.vim,\r\n    vimfiles\\perl\\eui_vim.pl     and \r\n    vimfiles\\doc\\eui_vim.txt \r\n\r\nThe help-tags can be regenerated, for example, by executing\r\n\":helptags $vim\\vimfiles\\doc\" from within vim.\r\n\r\nIn systems that don't have perl, eui_vim.pl can be replaced by a\r\nself-contained executable, eui_vim.exe available from the author.\r\n\r\n","5":"____________________________________________________________\r\nSystem Requirements\r\n\r\nEui_vim has been tested on Windows 98 with the ''Big version with\r\nGUI'' Vim 6.2 (requires +clientserver, but perl support is not\r\nrequired).  It is unlikely to work as-is on unix (the port to \r\nunix is likely to be simpler).\r\n\r\n____________________________________________________________\r\nInstallation\r\n\r\nEssentially, unzip eui_vim.zip into the vimfiles directory while\r\npreserving folder names and regenerate the help-tags.  \r\n\r\nUnzipping deploys three files:  \r\n\r\n    vimfiles\\plugin\\eui_vim.vim,\r\n    vimfiles\\perl\\eui_vim.pl     and \r\n    vimfiles\\doc\\eui_vim.txt \r\n\r\nThe help-tags can be regenerated, for example, by executing\r\n\":helptags $vim\\vimfiles\\doc\" from within vim.\r\n\r\nIn systems that don't have perl, eui_vim.pl can be replaced by a\r\nself-contained executable, eui_vim.exe available from the author.\r\n\r\n","first_name":"Suresh","6":"Suresh","last_name":"Govindachar","7":"Govindachar","releases":[{"0":"906","vim_version":"6.0","1":"6.0","script_version":"1.01Edit","2":"1.01Edit","version_comment":"Initial upload","3":"Initial upload","package":"eui_vim.zip","4":"eui_vim.zip","src_id":"2739","5":"2739","creation_date":"1076417083","6":"1076417083"}]},"905":{"script_id":"905","0":"905","script_name":"sql.vim","1":"sql.vim","script_type":"syntax","2":"syntax","summary":"Oracle 9i update of the sql.vim syntax file","3":"Oracle 9i update of the sql.vim syntax file","description":"Update of the sql.vim syntax file. It supports all the Oracle 9i keywords and builtin functions.\r\nFuture plans are to support the builtin packages","4":"Update of the sql.vim syntax file. It supports all the Oracle 9i keywords and builtin functions.\r\nFuture plans are to support the builtin packages","install_details":"Replace with the original sql.vim file. The scripts is an extension of the original one, nothing was removed.","5":"Replace with the original sql.vim file. The scripts is an extension of the original one, nothing was removed.","first_name":"David","6":"David","last_name":"Kalosi","7":"Kalosi","releases":[{"0":"905","vim_version":"6.0","1":"6.0","script_version":"1","2":"1","version_comment":"Initial upload","3":"Initial upload","package":"sql.vim","4":"sql.vim","src_id":"2736","5":"2736","creation_date":"1076397225","6":"1076397225"}]},"904":{"script_id":"904","0":"904","script_name":"yiheb-il.vim","1":"yiheb-il.vim","script_type":"utility","2":"utility","summary":"Yiddish\/Hebrew keyboard map, Israeli layout + finials on shift, Unicode","3":"Yiddish\/Hebrew keyboard map, Israeli layout + finials on shift, Unicode","description":"Yiddish\/Hebrew keyboard map, finial letters on shifted keys, releasing punctu keys + 'oilwq', maps yiddish + nikud. Unicode.","4":"Yiddish\/Hebrew keyboard map, finial letters on shifted keys, releasing punctu keys + 'oilwq', maps yiddish + nikud. Unicode.","install_details":"put in ~\/.vim\/keymap\/\r\n :set keymap=yi\r\noptionally:\r\n :set rl\r\nand select a proper font, for either gvim or termimal\r\nfor example:\r\n :set guifont=-misc-fixed-medium-r-normal-*-*-140-*-*-c-*-iso10646-1\r\noptionally:\r\n:set revins\r\nhelp hebrew\r\nfor more info","5":"put in ~\/.vim\/keymap\/\r\n :set keymap=yi\r\noptionally:\r\n :set rl\r\nand select a proper font, for either gvim or termimal\r\nfor example:\r\n :set guifont=-misc-fixed-medium-r-normal-*-*-140-*-*-c-*-iso10646-1\r\noptionally:\r\n:set revins\r\nhelp hebrew\r\nfor more info","first_name":"Oyd E","6":"Oyd E","last_name":"Leven","7":"Leven","releases":[{"0":"904","vim_version":"6.0","1":"6.0","script_version":"0.01","2":"0.01","version_comment":"Initial upload","3":"Initial upload","package":"yiheb-il.vim","4":"yiheb-il.vim","src_id":"2734","5":"2734","creation_date":"1076316652","6":"1076316652"}]},"903":{"script_id":"903","0":"903","script_name":"fvl.vim","1":"fvl.vim","script_type":"utility","2":"utility","summary":"Send Lisp code to an interpreter running in a Vim window","3":"Send Lisp code to an interpreter running in a Vim window","description":"Fred's Vim Lisp\r\n\r\nThis plugin allows you to run a Lisp interpreter in a Vim window and send Lisp expressions to it. You can send selected lines, a [count] number of lines, or a range of lines.\r\n\r\nfvl.vim defines a handful of commands:\r\n    LispOpen     opens the lisp window and starts the lisp interpreter\r\n    LispClose    close the lisp window and terminate lisp. This happens automatically when the lisp buffer is closed.\r\n    LispRefresh  try and read from lisp when your in a pinch.\r\n    LispDo       like perldo. Evaluate a lisp expression. You MUST escape quotes.\r\n    LispCount    evaluate [count] lines.\r\n    LispRange    evaluate a range of lines.\r\n\r\nIn practice, all you need to remember is LispDo and possibly LispRange.\r\nI've added the following mapping to my .vimrc file:\r\n\r\nmap <C-L> :LispRange\r\n\r\nThat map allows you to hit <C-L> to send a single line to the lisp interpreter, or select a few lines and send them all together.\r\n\r\n\r\nNOTE: There is already another script that does similar things to fvl.vim, vimscript #221 (VIlisp.vim). What's the difference? Mostly, fvl.vim requires only one file (the plugin file) to work and is a bit easier to setup (imho).\r\n","4":"Fred's Vim Lisp\r\n\r\nThis plugin allows you to run a Lisp interpreter in a Vim window and send Lisp expressions to it. You can send selected lines, a [count] number of lines, or a range of lines.\r\n\r\nfvl.vim defines a handful of commands:\r\n    LispOpen     opens the lisp window and starts the lisp interpreter\r\n    LispClose    close the lisp window and terminate lisp. This happens automatically when the lisp buffer is closed.\r\n    LispRefresh  try and read from lisp when your in a pinch.\r\n    LispDo       like perldo. Evaluate a lisp expression. You MUST escape quotes.\r\n    LispCount    evaluate [count] lines.\r\n    LispRange    evaluate a range of lines.\r\n\r\nIn practice, all you need to remember is LispDo and possibly LispRange.\r\nI've added the following mapping to my .vimrc file:\r\n\r\nmap <C-L> :LispRange\r\n\r\nThat map allows you to hit <C-L> to send a single line to the lisp interpreter, or select a few lines and send them all together.\r\n\r\n\r\nNOTE: There is already another script that does similar things to fvl.vim, vimscript #221 (VIlisp.vim). What's the difference? Mostly, fvl.vim requires only one file (the plugin file) to work and is a bit easier to setup (imho).\r\n","install_details":"REQUIREMENTS:\r\n  vim (compiled with +perl and +windows)\r\n  perl5\r\n  perl Expect module (# cpan Expect)\r\n  gcl, clisp, or some other lisp interpreter\r\n\r\nStep 1:\r\n Edit the perl variables at the top of the script file to your liking. Important ones to look at are $LispInterp and $LispPrompt. $LispInterp is the name of the interpreter you'd like to use. $LispPrompt should contain a regurlar expression that matches the prompt that your interpreter issues (\"^.*>\" will probably work).\r\n\r\nStep 2:\r\n Copy the fvl.vim to your vim plugin directory\r\n\r\nStep 3:\r\n Add a mapping or two to LispRange and\/or LispCount.\r\n\r\nYou should be all set.\r\n\r\nfvl.vim will probably work with any program that runs on a read\/evaluate loop if the $LispPrompt variable is set correctly.\r\n","5":"REQUIREMENTS:\r\n  vim (compiled with +perl and +windows)\r\n  perl5\r\n  perl Expect module (# cpan Expect)\r\n  gcl, clisp, or some other lisp interpreter\r\n\r\nStep 1:\r\n Edit the perl variables at the top of the script file to your liking. Important ones to look at are $LispInterp and $LispPrompt. $LispInterp is the name of the interpreter you'd like to use. $LispPrompt should contain a regurlar expression that matches the prompt that your interpreter issues (\"^.*>\" will probably work).\r\n\r\nStep 2:\r\n Copy the fvl.vim to your vim plugin directory\r\n\r\nStep 3:\r\n Add a mapping or two to LispRange and\/or LispCount.\r\n\r\nYou should be all set.\r\n\r\nfvl.vim will probably work with any program that runs on a read\/evaluate loop if the $LispPrompt variable is set correctly.\r\n","first_name":"Ray","6":"Ray","last_name":"Wallace","7":"Wallace","releases":[{"0":"903","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"fvl.vim","4":"fvl.vim","src_id":"2731","5":"2731","creation_date":"1076246600","6":"1076246600"}]},"902":{"script_id":"902","0":"902","script_name":"ratfor.vim","1":"ratfor.vim","script_type":"syntax","2":"syntax","summary":"Vim syntax file for RATFOR","3":"Vim syntax file for RATFOR","description":"RATFOR is a dialect of FORTRAN made by\r\nthe creators of C. RATFOR is a preprocessor that provides C like control flow to FORTRAN.\r\n  \r\nSo ratfor.vim implements this idea.\r\n ","4":"RATFOR is a dialect of FORTRAN made by\r\nthe creators of C. RATFOR is a preprocessor that provides C like control flow to FORTRAN.\r\n  \r\nSo ratfor.vim implements this idea.\r\n ","install_details":"Put ratfor.vim where vim could see it.\r\n\r\nUsualy ratfor scripts use .r as name extension. So add the next lines in filetype.vim\r\n\r\n\" RATFOR (Rational Fortran)\r\naugroup filetypedetect\r\nau BufNewFile,BufRead *.r       setf ratfor\r\nau BufNewFile,BufRead *.ratfor  setf ratfor\r\naugroup END\r\n","5":"Put ratfor.vim where vim could see it.\r\n\r\nUsualy ratfor scripts use .r as name extension. So add the next lines in filetype.vim\r\n\r\n\" RATFOR (Rational Fortran)\r\naugroup filetypedetect\r\nau BufNewFile,BufRead *.r       setf ratfor\r\nau BufNewFile,BufRead *.ratfor  setf ratfor\r\naugroup END\r\n","first_name":"Patricio","6":"Patricio","last_name":"Toledo","7":"Toledo","releases":[{"0":"902","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"ratfor.vim","4":"ratfor.vim","src_id":"2730","5":"2730","creation_date":"1076240235","6":"1076240235"}]},"901":{"script_id":"901","0":"901","script_name":"C# Plugin Added","1":"C# Plugin Added","script_type":"utility","2":"utility","summary":"Intellisense for C#","3":"Intellisense for C#","description":"Here is the new intellisense plugin for C#. This enables the context sensitive completion and online help.\r\nDue to size restrictions, I could not post the package here. To download the visit http:\/\/sourceforge.net\/projects\/insenvim and download the insenvim1.2 package.\r\nThis is only for Windows.","4":"Here is the new intellisense plugin for C#. This enables the context sensitive completion and online help.\r\nDue to size restrictions, I could not post the package here. To download the visit http:\/\/sourceforge.net\/projects\/insenvim and download the insenvim1.2 package.\r\nThis is only for Windows.","install_details":"Setup is included.","5":"Setup is included.","first_name":"Ravi","6":"Ravi","last_name":"Shankar","7":"Shankar","releases":[{"0":"901","vim_version":"6.0","1":"6.0","script_version":"1.2","2":"1.2","version_comment":"Initial upload","3":"Initial upload","package":"changelog.txt","4":"changelog.txt","src_id":"2728","5":"2728","creation_date":"1076127358","6":"1076127358"}]},"900":{"script_id":"900","0":"900","script_name":"Tower of Hanoi","1":"Tower of Hanoi","script_type":"game","2":"game","summary":"Tower of Hanoi game for Vim","3":"Tower of Hanoi game for Vim","description":"Continuing the tradition of creating games for Vim, here is a Tower of Hanoi implementation. Best played in GUI version of Vim.\r\n\r\n- Comes with two modes, a demo mode and a play mode. \r\n- You can start the game by using the command :Hanoi optionally passing the number of disks as an argument. \r\n- If no argument is passed, you are prompted to enter a value. \r\n- The maximum number of disks is determined based on the size of your vim window.\r\n- You will be prompted to choose between demo or play mode.\r\n- In demo mode, the script plays for you, just sit and relax.\r\n- In play mode, you can use h, j, k, l keys to move the disks from pole to pole. The disk with dashes represents the current disk that you can move.\r\n- Keys h and k select the current pole, and thus the top most disk on the pole.\r\n- Keys k and j move the disk up and down.\r\n- In play mode, you can pause the game by pressing <Space>, and come back by using :Hanoi command again.\r\n- You can stop the game at any time by pressing <C-C> or <C-Break>\r\n\r\nGood exerciese to practice hjkl key movements, if you are new to Vi realm :)\r\n\r\n\r\n\r\nSearch_key_words: tower hanoi game games hari krishna dara","4":"Continuing the tradition of creating games for Vim, here is a Tower of Hanoi implementation. Best played in GUI version of Vim.\r\n\r\n- Comes with two modes, a demo mode and a play mode. \r\n- You can start the game by using the command :Hanoi optionally passing the number of disks as an argument. \r\n- If no argument is passed, you are prompted to enter a value. \r\n- The maximum number of disks is determined based on the size of your vim window.\r\n- You will be prompted to choose between demo or play mode.\r\n- In demo mode, the script plays for you, just sit and relax.\r\n- In play mode, you can use h, j, k, l keys to move the disks from pole to pole. The disk with dashes represents the current disk that you can move.\r\n- Keys h and k select the current pole, and thus the top most disk on the pole.\r\n- Keys k and j move the disk up and down.\r\n- In play mode, you can pause the game by pressing <Space>, and come back by using :Hanoi command again.\r\n- You can stop the game at any time by pressing <C-C> or <C-Break>\r\n\r\nGood exerciese to practice hjkl key movements, if you are new to Vi realm :)\r\n\r\n\r\n\r\nSearch_key_words: tower hanoi game games hari krishna dara","install_details":"- Requires Vim 7 GUI version.\r\n- Extract the zip file into your runtime directory.\r\n- The plugin is loaded only on demand.\r\n- Requires genutils.vim (vimscript #197)","5":"- Requires Vim 7 GUI version.\r\n- Extract the zip file into your runtime directory.\r\n- The plugin is loaded only on demand.\r\n- Requires genutils.vim (vimscript #197)","first_name":"Hari Krishna","6":"Hari Krishna","last_name":"Dara","7":"Dara","releases":[{"0":"900","vim_version":"7.0","1":"7.0","script_version":"2.0","2":"2.0","version_comment":"Just made compatible with Vim7. Also removed dependency on multvals, as it now uses Vim7 Lists and Dictionaries.","3":"Just made compatible with Vim7. Also removed dependency on multvals, as it now uses Vim7 Lists and Dictionaries.","package":"hanoi-2.0.zip","4":"hanoi-2.0.zip","src_id":"6731","5":"6731","creation_date":"1170874697","6":"1170874697"},{"0":"900","vim_version":"6.0","1":"6.0","script_version":"1.3","2":"1.3","version_comment":"Updated with more feedback.\r\n- Space should resume paused game.\r\n- When paused, should be able to close the game window and still be able to resume it.\r\n- Highlighting definition may not work on all the color schemes.","3":"Updated with more feedback.\r\n- Space should resume paused game.\r\n- When paused, should be able to close the game window and still be able to resume it.\r\n- Highlighting definition may not work on all the color schemes.","package":"hanoi-1.3.zip","4":"hanoi-1.3.zip","src_id":"2767","5":"2767","creation_date":"1077297998","6":"1077297998"},{"0":"900","vim_version":"6.0","1":"6.0","script_version":"1.2","2":"1.2","version_comment":"Just minor improvements, mostly scripting related for my satisfaction (and for the ease of adding any new features in the future). It now shows the number of moves and a message when the game is paused.","3":"Just minor improvements, mostly scripting related for my satisfaction (and for the ease of adding any new features in the future). It now shows the number of moves and a message when the game is paused.","package":"hanoi-1.2.zip","4":"hanoi-1.2.zip","src_id":"2765","5":"2765","creation_date":"1077215863","6":"1077215863"},{"0":"900","vim_version":"6.0","1":"6.0","script_version":"1.1","2":"1.1","version_comment":"Fixed some incompatibilities\/problems reported by Anoine J. Mechelynck. If you are facing other problems please report them to me.","3":"Fixed some incompatibilities\/problems reported by Anoine J. Mechelynck. If you are facing other problems please report them to me.","package":"hanoi-1.1.zip","4":"hanoi-1.1.zip","src_id":"2735","5":"2735","creation_date":"1076350477","6":"1076350477"},{"0":"900","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"hanoi-1.0.zip","4":"hanoi-1.0.zip","src_id":"2725","5":"2725","creation_date":"1076008681","6":"1076008681"}]},"899":{"script_id":"899","0":"899","script_name":"nesC","1":"nesC","script_type":"syntax","2":"syntax","summary":"nesC syntax highlighting","3":"nesC syntax highlighting","description":"nesC keyword highlighting (based on the C++ syntax script)","4":"nesC keyword highlighting (based on the C++ syntax script)","install_details":"just copy it to wherever you have the others :)","5":"just copy it to wherever you have the others :)","first_name":"Joao","6":"Joao","last_name":"Girao","7":"Girao","releases":[{"0":"899","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"nc.vim","4":"nc.vim","src_id":"2721","5":"2721","creation_date":"1075879541","6":"1075879541"}]},"898":{"script_id":"898","0":"898","script_name":"CharTab","1":"CharTab","script_type":"utility","2":"utility","summary":"ascii table with some nice features","3":"ascii table with some nice features","description":"This script provides a character table. Yes, yet another one :-). \r\n\r\nBut it has some nice features:                                      \r\n  - it takes advantage of syntax-highlighting\r\n  - it allows to toggle base of codes without leaving buffer\r\n  - it opens in currently active window, so no rearrangement of windows occur\r\n  - special codes are viewed with their real names (NUL, ETX,...)\r\n  - quitting is very simple and fast - just one keystroke\r\n","4":"This script provides a character table. Yes, yet another one :-). \r\n\r\nBut it has some nice features:                                      \r\n  - it takes advantage of syntax-highlighting\r\n  - it allows to toggle base of codes without leaving buffer\r\n  - it opens in currently active window, so no rearrangement of windows occur\r\n  - special codes are viewed with their real names (NUL, ETX,...)\r\n  - quitting is very simple and fast - just one keystroke\r\n","install_details":"To use this script copy it into your local plugin-directory\r\nUnix:    ~.\/.vim\/plugin\r\nWindows: c:\\vimfiles\\plugin\r\nAfter starting VIM this script is sourced automatically.\r\n                                                           \r\nBy default press <Leader>ct to view character table.\r\nMemory aid, ct = (c)haracter (t)able\r\n\r\nSee header of script for how to configure.","5":"To use this script copy it into your local plugin-directory\r\nUnix:    ~.\/.vim\/plugin\r\nWindows: c:\\vimfiles\\plugin\r\nAfter starting VIM this script is sourced automatically.\r\n                                                           \r\nBy default press <Leader>ct to view character table.\r\nMemory aid, ct = (c)haracter (t)able\r\n\r\nSee header of script for how to configure.","first_name":"Christian","6":"Christian","last_name":"Habermann","7":"Habermann","releases":[{"0":"898","vim_version":"6.0","1":"6.0","script_version":"1.0.0","2":"1.0.0","version_comment":"Initial upload","3":"Initial upload","package":"chartab.vim","4":"chartab.vim","src_id":"2717","5":"2717","creation_date":"1075798324","6":"1075798324"}]},"897":{"script_id":"897","0":"897","script_name":"ViewOutput","1":"ViewOutput","script_type":"utility","2":"utility","summary":"scroll back and search [long] output of vim command","3":"scroll back and search [long] output of vim command","description":"If you want to scroll backward (and forward) and search within long output of the vim command (such as :au, :let), execute command with prefix VO. \r\n\r\nVO (viewoutput) will place output of vim command in new buffer where you can search and view it using vim commands. Example:\r\n\r\n      :VO au\r\n      :VO let","4":"If you want to scroll backward (and forward) and search within long output of the vim command (such as :au, :let), execute command with prefix VO. \r\n\r\nVO (viewoutput) will place output of vim command in new buffer where you can search and view it using vim commands. Example:\r\n\r\n      :VO au\r\n      :VO let","install_details":"Drop viewoutput.vim into your ~\/.vim\/plugin directory.\r\n\r\nTo change the command that creates the preview window (the default is \"new\"),\r\nyou can edit definition of g:viewoutput_newbuffer variable at the beginning of\r\nscript:\r\n\r\nlet g:viewoutput_newbuffer=\"5new\"     | \" create preview window 5 lines high\r\nlet g:viewoutput_newbuffer=\"bot 5new\" | \" bottom preview window 5 lines high\r\n","5":"Drop viewoutput.vim into your ~\/.vim\/plugin directory.\r\n\r\nTo change the command that creates the preview window (the default is \"new\"),\r\nyou can edit definition of g:viewoutput_newbuffer variable at the beginning of\r\nscript:\r\n\r\nlet g:viewoutput_newbuffer=\"5new\"     | \" create preview window 5 lines high\r\nlet g:viewoutput_newbuffer=\"bot 5new\" | \" bottom preview window 5 lines high\r\n","first_name":"Yakov","6":"Yakov","last_name":"Lerner","7":"Lerner","releases":[{"0":"897","vim_version":"6.0","1":"6.0","script_version":"2.0","2":"2.0","version_comment":"Fixed bug with 'VO map' (silent map produced output without newlines). Saving output to register rather than tempfile. Improvements thanks to Antony Scriven and Charles Campbell. Config variable  g:viewoutput_newbuffer added.","3":"Fixed bug with 'VO map' (silent map produced output without newlines). Saving output to register rather than tempfile. Improvements thanks to Antony Scriven and Charles Campbell. Config variable  g:viewoutput_newbuffer added.","package":"viewoutput.vim","4":"viewoutput.vim","src_id":"2722","5":"2722","creation_date":"1075882853","6":"1075882853"},{"0":"897","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"viewoutput.vim","4":"viewoutput.vim","src_id":"2716","5":"2716","creation_date":"1075775948","6":"1075775948"}]},"896":{"script_id":"896","0":"896","script_name":"perl_synwrite.vim","1":"perl_synwrite.vim","script_type":"ftplugin","2":"ftplugin","summary":"checks Perl syntax before allowing file write","3":"checks Perl syntax before allowing file write","description":"This plugin causes write attempts to fail if the contents of the buffer produce an error when run through \"perl -c\"\r\n\r\nThe plugin uses can use autocommands for the BufWriteCmd and FileWriteCmd events, but by default only provides a :Write command to check-then-write.","4":"This plugin causes write attempts to fail if the contents of the buffer produce an error when run through \"perl -c\"\r\n\r\nThe plugin uses can use autocommands for the BufWriteCmd and FileWriteCmd events, but by default only provides a :Write command to check-then-write.","install_details":"Put this file in one of the locations described in :help ftplugin such as \"~\/.vim\/after\/ftplugin\";  if you want autocommands, which are quirky, define perl_synwrite_au = 1","5":"Put this file in one of the locations described in :help ftplugin such as \"~\/.vim\/after\/ftplugin\";  if you want autocommands, which are quirky, define perl_synwrite_au = 1","first_name":"Ricardo","6":"Ricardo","last_name":"Signes","7":"Signes","releases":[{"0":"896","vim_version":"6.0","1":"6.0","script_version":"5","2":"5","version_comment":"work with shebang of \"#!perl\"\r\nbetter internals","3":"work with shebang of \"#!perl\"\r\nbetter internals","package":"perl_synwrite.vim","4":"perl_synwrite.vim","src_id":"4979","5":"4979","creation_date":"1137430085","6":"1137430085"},{"0":"896","vim_version":"6.0","1":"6.0","script_version":"4","2":"4","version_comment":"respect tainting, include a bit more information","3":"respect tainting, include a bit more information","package":"perl_synwrite.vim","4":"perl_synwrite.vim","src_id":"4944","5":"4944","creation_date":"1136394561","6":"1136394561"}]},"895":{"script_id":"895","0":"895","script_name":"Toggle","1":"Toggle","script_type":"utility","2":"utility","summary":"allows you to toggle bool (true\/false) and other words with a shortcut","3":"allows you to toggle bool (true\/false) and other words with a shortcut","description":"In this version, the script can toggle:\r\n    True     <->     False\r\n    true     <->     false\r\n    on       <->     off\r\n    yes      <->     no\r\n    define  <->     undef\r\n    +        <->     -\r\n    >        <->     <\r\n    &&    <->     ||\r\n    &     <->      |\r\n    positive and negative numbers\r\n\r\nMove the cursor on the word\/char\/number to be toggled and press\r\n      <C-T>  in insert mode \r\nor\r\n      +     in normal \/ visual mode.\r\n\r\nThis shortcut can be modified in the script file - of course...\r\n\r\nIf the cursor is positioned on a number, the script looks for a corresponding + or - sign for that number. \r\nIf it's found, it will be replaced by the other one. If none is found, a - sign is inserted before the number.","4":"In this version, the script can toggle:\r\n    True     <->     False\r\n    true     <->     false\r\n    on       <->     off\r\n    yes      <->     no\r\n    define  <->     undef\r\n    +        <->     -\r\n    >        <->     <\r\n    &&    <->     ||\r\n    &     <->      |\r\n    positive and negative numbers\r\n\r\nMove the cursor on the word\/char\/number to be toggled and press\r\n      <C-T>  in insert mode \r\nor\r\n      +     in normal \/ visual mode.\r\n\r\nThis shortcut can be modified in the script file - of course...\r\n\r\nIf the cursor is positioned on a number, the script looks for a corresponding + or - sign for that number. \r\nIf it's found, it will be replaced by the other one. If none is found, a - sign is inserted before the number.","install_details":"put this plugin into your ~\/.vim\/plugin folder or source it in your ~\/.vimrc","5":"put this plugin into your ~\/.vim\/plugin folder or source it in your ~\/.vimrc","first_name":"Timo","6":"Timo","last_name":"Teifel","7":"Teifel","releases":[{"0":"895","vim_version":"7.0","1":"7.0","script_version":"0.6","2":"0.6","version_comment":"Add Python True\/False toggle, kindly provided by Christian Tabedzki","3":"Add Python True\/False toggle, kindly provided by Christian Tabedzki","package":"toggle.vim","4":"toggle.vim","src_id":"26272","5":"26272","creation_date":"1542260151","6":"1542260151"},{"0":"895","vim_version":"7.0","1":"7.0","script_version":"0.5","2":"0.5","version_comment":"- Keeps the keyword case when toggling (thanks to Jan Christoph Ebersbach for this code)\r\n- bugfix for && and || toggling","3":"- Keeps the keyword case when toggling (thanks to Jan Christoph Ebersbach for this code)\r\n- bugfix for && and || toggling","package":"toggle.vim","4":"toggle.vim","src_id":"13834","5":"13834","creation_date":"1284550467","6":"1284550467"},{"0":"895","vim_version":"7.0","1":"7.0","script_version":"0.4","2":"0.4","version_comment":"default mapping uses + in normal and visual mode instead of <C-T>\r\nadded toggle entries: && <--> ||   and & <--> | \r\ninternal optimizations","3":"default mapping uses + in normal and visual mode instead of <C-T>\r\nadded toggle entries: && <--> ||   and & <--> | \r\ninternal optimizations","package":"toggle.vim","4":"toggle.vim","src_id":"13821","5":"13821","creation_date":"1284452276","6":"1284452276"},{"0":"895","vim_version":"6.0","1":"6.0","script_version":"0.3","2":"0.3","version_comment":"I added define\/undef as new words.\r\nI added a mapping for visual mode (it actually quits visual mode and calls the Toggle function. But now it works, if you clicked with the mouse on the word and accidentally switched on visual mode...)\r\nI realised that <C-S-T> is the same than <C-T> I didn't intent to break these mappings, but since I didn't find another suitable keymapping, I now use <C-T>. Anyone who doesn't like that can change that easily.","3":"I added define\/undef as new words.\r\nI added a mapping for visual mode (it actually quits visual mode and calls the Toggle function. But now it works, if you clicked with the mouse on the word and accidentally switched on visual mode...)\r\nI realised that <C-S-T> is the same than <C-T> I didn't intent to break these mappings, but since I didn't find another suitable keymapping, I now use <C-T>. Anyone who doesn't like that can change that easily.","package":"toggle.vim","4":"toggle.vim","src_id":"2727","5":"2727","creation_date":"1076060703","6":"1076060703"},{"0":"895","vim_version":"6.0","1":"6.0","script_version":"0.2","2":"0.2","version_comment":"Initial upload","3":"Initial upload","package":"toggle.vim","4":"toggle.vim","src_id":"2714","5":"2714","creation_date":"1075734730","6":"1075734730"}]},"894":{"script_id":"894","0":"894","script_name":"Viewing Procmail Log","1":"Viewing Procmail Log","script_type":"syntax","2":"syntax","summary":"Seeing only the interesting parts of procmail log","3":"Seeing only the interesting parts of procmail log","description":"Here is a syntax file for viewing Procmail log.  The syntax works at least w\/ vim 6.2.\r\n\r\nI have commented [out] my preferred colors; otherwise did my best to have reasonable colors wrt dark background.\r\n\r\nRefer to http:\/\/www103.pair.com\/parv\/comp\/unix\/cf\/vim\/procmail.vim for any updates.  Before you replace the syntax file from here, mind that the one exeternally available is not as generous regarding other syntax.  For one, the external one starts w\/ \"syn clear\" unconditionally.","4":"Here is a syntax file for viewing Procmail log.  The syntax works at least w\/ vim 6.2.\r\n\r\nI have commented [out] my preferred colors; otherwise did my best to have reasonable colors wrt dark background.\r\n\r\nRefer to http:\/\/www103.pair.com\/parv\/comp\/unix\/cf\/vim\/procmail.vim for any updates.  Before you replace the syntax file from here, mind that the one exeternally available is not as generous regarding other syntax.  For one, the external one starts w\/ \"syn clear\" unconditionally.","install_details":"Associate it just like any other syntax\/highlight file.  If your log file is named \"procmail.log*\", then...\r\n\r\n  au BufNewFile,BufRead procmail.log* so \/path\/to\/procmail-log.vim\r\n  au BufNewFile,BufRead procmail.log* set syn=procmail-log","5":"Associate it just like any other syntax\/highlight file.  If your log file is named \"procmail.log*\", then...\r\n\r\n  au BufNewFile,BufRead procmail.log* so \/path\/to\/procmail-log.vim\r\n  au BufNewFile,BufRead procmail.log* set syn=procmail-log","first_name":"parv","6":"parv","last_name":".","7":".","releases":[{"0":"894","vim_version":"6.0","1":"6.0","script_version":"0.2","2":"0.2","version_comment":"Initial upload","3":"Initial upload","package":"procmail-log.vim","4":"procmail-log.vim","src_id":"2709","5":"2709","creation_date":"1075675733","6":"1075675733"}]},"893":{"script_id":"893","0":"893","script_name":"gtags.vim","1":"gtags.vim","script_type":"utility","2":"utility","summary":"Integrates GNU GLOBAL source code tag system with VIM.","3":"Integrates GNU GLOBAL source code tag system with VIM.","description":"SUPPORT OF THIS SCRIPT ON THIS SITE HAS BEEN ENDED.\r\nInstead, please use gtags.vim included in the latest GNU GLOBAL. [http:\/\/www.gnu.org\/software\/global\/]\r\nThank you.","4":"SUPPORT OF THIS SCRIPT ON THIS SITE HAS BEEN ENDED.\r\nInstead, please use gtags.vim included in the latest GNU GLOBAL. [http:\/\/www.gnu.org\/software\/global\/]\r\nThank you.","install_details":"N\/A","5":"N\/A","first_name":"Shigio","6":"Shigio","last_name":"Yamaguchi","7":"Yamaguchi","releases":[{"0":"893","vim_version":"6.0","1":"6.0","script_version":"0.2","2":"0.2","version_comment":"Copyright description added.\r\nSome usage description added.\r\n- Input completion.\r\n- Quickfix command.\r\n- The -P command.\r\n","3":"Copyright description added.\r\nSome usage description added.\r\n- Input completion.\r\n- Quickfix command.\r\n- The -P command.\r\n","package":"gtags.vim","4":"gtags.vim","src_id":"2925","5":"2925","creation_date":"1081446479","6":"1081446479"}]},"892":{"script_id":"892","0":"892","script_name":"winpos.vim","1":"winpos.vim","script_type":"utility","2":"utility","summary":"save \/ restore window positions","3":"save \/ restore window positions","description":"Save \/ restore GVIM window positions quickly through function keys.\r\n\r\nShift + F1\/F2\/F3\/F4 to save window position, F1\/F2\/F3\/F4 to restore.\r\nEdit script to set default positions.","4":"Save \/ restore GVIM window positions quickly through function keys.\r\n\r\nShift + F1\/F2\/F3\/F4 to save window position, F1\/F2\/F3\/F4 to restore.\r\nEdit script to set default positions.","install_details":":source winpos.vim or place in plugin directory.","5":":source winpos.vim or place in plugin directory.","first_name":"Don","6":"Don","last_name":"Yang","7":"Yang","releases":[{"0":"892","vim_version":"6.0","1":"6.0","script_version":"1.1","2":"1.1","version_comment":"add mappings for insert mode","3":"add mappings for insert mode","package":"winpos.vim","4":"winpos.vim","src_id":"2810","5":"2810","creation_date":"1078661527","6":"1078661527"},{"0":"892","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"winpos.vim","4":"winpos.vim","src_id":"2707","5":"2707","creation_date":"1075658675","6":"1075658675"}]},"891":{"script_id":"891","0":"891","script_name":"pylint.vim","1":"pylint.vim","script_type":"utility","2":"utility","summary":"compiler plugin for python style checking tool","3":"compiler plugin for python style checking tool","description":"Compiler plugin for PyLint ( http:\/\/www.logilab.org\/projects\/pylint\/ ), a style checking tool for Python. ","4":"Compiler plugin for PyLint ( http:\/\/www.logilab.org\/projects\/pylint\/ ), a style checking tool for Python. ","install_details":"just copy script to ~\/.vim\/compiler\/","5":"just copy script to ~\/.vim\/compiler\/","first_name":"Oleksandr","6":"Oleksandr","last_name":"Tymoshenko","7":"Tymoshenko","releases":[{"0":"891","vim_version":"6.0","1":"6.0","script_version":"0.5","2":"0.5","version_comment":"- Fix redefinition of Pylint command for multiple buffers\r\n- Do not jump to the first error if check is initiated by buffer write\r\n- Write buffer when calling Pylint command directly\r\n- Use\/define CompilerSet command","3":"- Fix redefinition of Pylint command for multiple buffers\r\n- Do not jump to the first error if check is initiated by buffer write\r\n- Write buffer when calling Pylint command directly\r\n- Use\/define CompilerSet command","package":"pylint.vim","4":"pylint.vim","src_id":"10365","5":"10365","creation_date":"1239241239","6":"1239241239"},{"0":"891","vim_version":"6.0","1":"6.0","script_version":"0.4","2":"0.4","version_comment":"- Code rate is displayed on demand\r\n- Open quickfix window on buffer save\r\n- A couple of knobs to manage functions mentioned above\r\n- Documentation reworked\r\nSubmitted by: Artur Wroblewski <wrobell@pld-linux.org>","3":"- Code rate is displayed on demand\r\n- Open quickfix window on buffer save\r\n- A couple of knobs to manage functions mentioned above\r\n- Documentation reworked\r\nSubmitted by: Artur Wroblewski <wrobell@pld-linux.org>","package":"pylint.vim","4":"pylint.vim","src_id":"8710","5":"8710","creation_date":"1211343919","6":"1211343919"},{"0":"891","vim_version":"6.0","1":"6.0","script_version":"0.3","2":"0.3","version_comment":"Improved usability. submitted by Tim Farley <tofarley@gmail.com>. ","3":"Improved usability. submitted by Tim Farley <tofarley@gmail.com>. ","package":"pylint.vim","4":"pylint.vim","src_id":"5156","5":"5156","creation_date":"1139633167","6":"1139633167"},{"0":"891","vim_version":"6.0","1":"6.0","script_version":"0.2","2":"0.2","version_comment":"upoad bug fix","3":"upoad bug fix","package":"pylint.vim","4":"pylint.vim","src_id":"2710","5":"2710","creation_date":"1075685115","6":"1075685115"},{"0":"891","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"pylint.vim","4":"pylint.vim","src_id":"2704","5":"2704","creation_date":"1075628795","6":"1075628795"}]},"890":{"script_id":"890","0":"890","script_name":"edo_sea","1":"edo_sea","script_type":"color scheme","2":"color scheme","summary":"A blueish color scheme with a dark background","3":"A blueish color scheme with a dark background","description":"A low-contrast, blueish, color scheme with a dark background. Tweaked to maximize usability with syntax highlighting.","4":"A low-contrast, blueish, color scheme with a dark background. Tweaked to maximize usability with syntax highlighting.","install_details":"place in your \"colors\" folder","5":"place in your \"colors\" folder","first_name":"Ed","6":"Ed","last_name":"O.","7":"O.","releases":[{"0":"890","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"edo_sea.vim","4":"edo_sea.vim","src_id":"2699","5":"2699","creation_date":"1075467118","6":"1075467118"}]},"889":{"script_id":"889","0":"889","script_name":"EvalSelection.vim","1":"EvalSelection.vim","script_type":"utility","2":"utility","summary":"evaluate selected code (vim, bash, ruby, python, perl, (mz)scheme, tcl, R, SPSS)","3":"evaluate selected code (vim, bash, ruby, python, perl, (mz)scheme, tcl, R, SPSS)","description":"Evaluate source code selected in a visual region. The result can be displayed \r\nin an interaction log, appended to the text, replace the text, or saved in the \r\n@e register. This is useful for performing small text manipulation tasks or \r\ncalculations that aren't worth the trouble of creating a new file or switching \r\nto a different program, but which are too big for being handled in the command \r\nline.\r\n\r\nThe key bindings follow this scheme:\r\n\r\n    <Leader>e{LANGUAGE}{MODE} :: work on the visual region\r\n    <Leader>E{LANGUAGE}{MODE} :: work on the contents of the e-register\r\n    <Leader>x{MODE}           :: work on the visual region (derives LANGUAGE \r\n                                 from the buffer's 'filetype')\r\n\r\nLANGUAGE being one of:\r\n\r\n    v :: vim (comments at the end of line after vim code could cause problems)\r\n    r :: ruby (requires compiled-in ruby support)\r\n    s :: sh (using system())\r\n    e :: calculator, evaluate formula (using either ruby, python, perl, tcl, \r\n         or vim)\r\n\r\nI haven't actually tested the following three bindings because I use \r\nneither of them. Anyway, as I happen to use a Vim with +tcl, +python and \r\n+perl support compiled in, I added them to the standard bindings:\r\n\r\n    y :: python (requires compiled-in python support)\r\n    p :: perl (requires compiled-in perl support)\r\n    t :: tcl (requires compiled-in tcl support)\r\n    z :: mzscheme (requires compiled-in mzscheme support)\r\n\r\nIf ruby-support is compiled in, the following languages are available too \r\n(but see |EvalSelection-Interaction| below):\r\n    \r\n    c :: scheme\r\n        set g:evalSelectionSchemeInterpreter to \"Gauche\" or \"Chicken\"\r\n    l :: lisp\r\n        set g:evalSelectionLispInterpreter to \"CLisp\"\r\n    o :: ocaml\r\n        set g:evalSelectionOCamlInterpreter to \"OCaml\" or \"OCamlClean\"\r\n    R :: R\r\n        set g:evalSelectionRInterpreter \"R\", \"RClean\", or \"RDCOM\"\r\n    S :: SPSS\r\n        limited support (no return values), the (one-way) communication with \r\n        SPSS is done via OLE automation\r\n\r\nMODE being one of:\r\n\r\n    x :: just evaluate and put the result in the e-register\r\n    e :: the same as x\r\n    p :: echo\/print the result on the command line\r\n    a :: append the result to visual region\r\n    r :: replace visual region with the result\r\n    l :: insert the result in a temporary interaction log\r\n\r\n\r\nCommands:\r\n\r\n    EvalSelectionCmdLine LANG :: Simulate a command line for LANG; due to the \r\n    primitive handling of input\/output, no input commands (like read, get kind \r\n    of stuff) can be used; all output is redirected to the log. Exit with ^D + \r\n    Enter, i.e. enter the ^D character.\r\n\r\n    EvalSelectionSetup{LANG}  :: Set up interaction with external interpreter \r\n    (but see below)\r\n\r\n    EvalSelectionQuit INTERPRETER :: Quit interaction with an \r\n    external interpreter\r\n","4":"Evaluate source code selected in a visual region. The result can be displayed \r\nin an interaction log, appended to the text, replace the text, or saved in the \r\n@e register. This is useful for performing small text manipulation tasks or \r\ncalculations that aren't worth the trouble of creating a new file or switching \r\nto a different program, but which are too big for being handled in the command \r\nline.\r\n\r\nThe key bindings follow this scheme:\r\n\r\n    <Leader>e{LANGUAGE}{MODE} :: work on the visual region\r\n    <Leader>E{LANGUAGE}{MODE} :: work on the contents of the e-register\r\n    <Leader>x{MODE}           :: work on the visual region (derives LANGUAGE \r\n                                 from the buffer's 'filetype')\r\n\r\nLANGUAGE being one of:\r\n\r\n    v :: vim (comments at the end of line after vim code could cause problems)\r\n    r :: ruby (requires compiled-in ruby support)\r\n    s :: sh (using system())\r\n    e :: calculator, evaluate formula (using either ruby, python, perl, tcl, \r\n         or vim)\r\n\r\nI haven't actually tested the following three bindings because I use \r\nneither of them. Anyway, as I happen to use a Vim with +tcl, +python and \r\n+perl support compiled in, I added them to the standard bindings:\r\n\r\n    y :: python (requires compiled-in python support)\r\n    p :: perl (requires compiled-in perl support)\r\n    t :: tcl (requires compiled-in tcl support)\r\n    z :: mzscheme (requires compiled-in mzscheme support)\r\n\r\nIf ruby-support is compiled in, the following languages are available too \r\n(but see |EvalSelection-Interaction| below):\r\n    \r\n    c :: scheme\r\n        set g:evalSelectionSchemeInterpreter to \"Gauche\" or \"Chicken\"\r\n    l :: lisp\r\n        set g:evalSelectionLispInterpreter to \"CLisp\"\r\n    o :: ocaml\r\n        set g:evalSelectionOCamlInterpreter to \"OCaml\" or \"OCamlClean\"\r\n    R :: R\r\n        set g:evalSelectionRInterpreter \"R\", \"RClean\", or \"RDCOM\"\r\n    S :: SPSS\r\n        limited support (no return values), the (one-way) communication with \r\n        SPSS is done via OLE automation\r\n\r\nMODE being one of:\r\n\r\n    x :: just evaluate and put the result in the e-register\r\n    e :: the same as x\r\n    p :: echo\/print the result on the command line\r\n    a :: append the result to visual region\r\n    r :: replace visual region with the result\r\n    l :: insert the result in a temporary interaction log\r\n\r\n\r\nCommands:\r\n\r\n    EvalSelectionCmdLine LANG :: Simulate a command line for LANG; due to the \r\n    primitive handling of input\/output, no input commands (like read, get kind \r\n    of stuff) can be used; all output is redirected to the log. Exit with ^D + \r\n    Enter, i.e. enter the ^D character.\r\n\r\n    EvalSelectionSetup{LANG}  :: Set up interaction with external interpreter \r\n    (but see below)\r\n\r\n    EvalSelectionQuit INTERPRETER :: Quit interaction with an \r\n    external interpreter\r\n","install_details":"Requires multvals.vim (vimscript #171), +ruby (for interaction with an interpreter)\r\n\r\nIf you have +ruby support compiled in and if you want to talk to an external interpreter, make sure that g:evalSelectionRubyDir points to the directory where EvalSelection.rb resides. Default values are:\r\n\r\n    Win32: $VIM.\"\/vimfiles\/ruby\/\"\r\n    Else:  \"~\/.vim\/ruby\/\"\r\n\r\n\r\nAlso available via git\r\nhttp:\/\/github.com\/tomtom\/vimtlib\/tree\/master\r\n","5":"Requires multvals.vim (vimscript #171), +ruby (for interaction with an interpreter)\r\n\r\nIf you have +ruby support compiled in and if you want to talk to an external interpreter, make sure that g:evalSelectionRubyDir points to the directory where EvalSelection.rb resides. Default values are:\r\n\r\n    Win32: $VIM.\"\/vimfiles\/ruby\/\"\r\n    Else:  \"~\/.vim\/ruby\/\"\r\n\r\n\r\nAlso available via git\r\nhttp:\/\/github.com\/tomtom\/vimtlib\/tree\/master\r\n","first_name":"Tom","6":"Tom","last_name":"Link","7":"Link","releases":[{"0":"889","vim_version":"7.0","1":"7.0","script_version":"0.16","2":"0.16","version_comment":"- MzScheme support (thanks to Mark Smithfield)\r\n- Catch errors on EvalSelectionQuit (you'll have to manually kill zombie \r\nprocesses)\r\n","3":"- MzScheme support (thanks to Mark Smithfield)\r\n- Catch errors on EvalSelectionQuit (you'll have to manually kill zombie \r\nprocesses)\r\n","package":"EvalSelection.vba.gz","4":"EvalSelection.vba.gz","src_id":"7221","5":"7221","creation_date":"1181262278","6":"1181262278"},{"0":"889","vim_version":"7.0","1":"7.0","script_version":"0.15","2":"0.15","version_comment":"- Escape backslashes in EvalSelectionTalk()\r\n- SPSS: Insert a space before variable names (like SPSS itself)\r\n","3":"- Escape backslashes in EvalSelectionTalk()\r\n- SPSS: Insert a space before variable names (like SPSS itself)\r\n","package":"EvalSelection.vba.gz","4":"EvalSelection.vba.gz","src_id":"7111","5":"7111","creation_date":"1179144975","6":"1179144975"},{"0":"889","vim_version":"6.0","1":"6.0","script_version":"0.14","2":"0.14","version_comment":"Fixed some menu-related problems; <LocalLeader>r shortkey for SPSS  andR (work similarly to ctrl-r in the spss editor); display a more usefulerror message when communication via OLE goes wrong; possibility to savethe interaction log; post setup & tear down hooks for externalinterpreters","3":"Fixed some menu-related problems; <LocalLeader>r shortkey for SPSS  andR (work similarly to ctrl-r in the spss editor); display a more usefulerror message when communication via OLE goes wrong; possibility to savethe interaction log; post setup & tear down hooks for externalinterpreters","package":"EvalSelection.zip","4":"EvalSelection.zip","src_id":"4362","5":"4362","creation_date":"1118737732","6":"1118737732"},{"0":"889","vim_version":"6.0","1":"6.0","script_version":"0.13","2":"0.13","version_comment":"R: set working directory and load .Rdata if available, word completion, catch errors, build objects menu; SPSS: show data window, build menu; g:evalSelectionLogCommands defaults to 1; revamped log","3":"R: set working directory and load .Rdata if available, word completion, catch errors, build objects menu; SPSS: show data window, build menu; g:evalSelectionLogCommands defaults to 1; revamped log","package":"EvalSelection.zip","4":"EvalSelection.zip","src_id":"3873","5":"3873","creation_date":"1108551380","6":"1108551380"},{"0":"889","vim_version":"6.0","1":"6.0","script_version":"0.10","2":"0.10","version_comment":"capture interaction with R via R(D)COM; \"RDCOM\" uses a 2nd instance of gvim as a pager (it doesn't start RCmdr any more); \"RDCOM Commander\" uses RCmdr; \"RDCOM Clean\" and \"RDCOM Commander Clean\" modes; take care of R functions with void results (like data, help.search ...)","3":"capture interaction with R via R(D)COM; \"RDCOM\" uses a 2nd instance of gvim as a pager (it doesn't start RCmdr any more); \"RDCOM Commander\" uses RCmdr; \"RDCOM Clean\" and \"RDCOM Commander Clean\" modes; take care of R functions with void results (like data, help.search ...)","package":"EvalSelection.zip","4":"EvalSelection.zip","src_id":"3861","5":"3861","creation_date":"1108286617","6":"1108286617"},{"0":"889","vim_version":"6.0","1":"6.0","script_version":"0.9","2":"0.9","version_comment":"support for interaction with R and SPSS via win32 COM\/OLE; calculator shortcuts","3":"support for interaction with R and SPSS via win32 COM\/OLE; calculator shortcuts","package":"EvalSelection.zip","4":"EvalSelection.zip","src_id":"3857","5":"3857","creation_date":"1108178731","6":"1108178731"},{"0":"889","vim_version":"6.0","1":"6.0","script_version":"0.8","2":"0.8","version_comment":"improved interaction with external interpreters (still not fully usable but it's getting better); reunified EvalSelection.vim and EvalSelectionRuby.vim","3":"improved interaction with external interpreters (still not fully usable but it's getting better); reunified EvalSelection.vim and EvalSelectionRuby.vim","package":"EvalSelection.zip","4":"EvalSelection.zip","src_id":"2997","5":"2997","creation_date":"1083802369","6":"1083802369"},{"0":"889","vim_version":"6.0","1":"6.0","script_version":"0.7","2":"0.7","version_comment":"Small improvements with external interpreters (e.g., multi-line commands in R); moved code depending on +ruby to EvalSelectionRuby.vim (thanks to Grant  Bowman for pointing out this problem); saved all files in unix  format; added python, perl, and tcl (but I can't tell if they work)","3":"Small improvements with external interpreters (e.g., multi-line commands in R); moved code depending on +ruby to EvalSelectionRuby.vim (thanks to Grant  Bowman for pointing out this problem); saved all files in unix  format; added python, perl, and tcl (but I can't tell if they work)","package":"EvalSelection.zip","4":"EvalSelection.zip","src_id":"2990","5":"2990","creation_date":"1083578593","6":"1083578593"},{"0":"889","vim_version":"6.0","1":"6.0","script_version":"0.6","2":"0.6","version_comment":"Use of redir; EvalSelectionCmdLine (CLI-like interaction); interaction with external interpreter (lisp, scheme, R, ocaml; experimental & requires +ruby support); separated logs; removed bc support","3":"Use of redir; EvalSelectionCmdLine (CLI-like interaction); interaction with external interpreter (lisp, scheme, R, ocaml; experimental & requires +ruby support); separated logs; removed bc support","package":"EvalSelection.vim","4":"EvalSelection.vim","src_id":"2819","5":"2819","creation_date":"1078818916","6":"1078818916"},{"0":"889","vim_version":"6.0","1":"6.0","script_version":"0.382","2":"0.382","version_comment":"l-Mode for logging","3":"l-Mode for logging","package":"EvalSelection.vim","4":"EvalSelection.vim","src_id":"2700","5":"2700","creation_date":"1075508611","6":"1075508611"}]},"888":{"script_id":"888","0":"888","script_name":"armasm","1":"armasm","script_type":"syntax","2":"syntax","summary":"Syntax highlighting for ARM assembler","3":"Syntax highlighting for ARM assembler","description":"Syntax highlighting for ARM assembly language. It includes V2, V3, V4, V5, T, E, M, XS, and VFP extensions, but no V6 or T2 syntax. It is based on Aleksandar Veselinovic's PIC16F84 Assembler syntax file (pic.vim in the standard installation).","4":"Syntax highlighting for ARM assembly language. It includes V2, V3, V4, V5, T, E, M, XS, and VFP extensions, but no V6 or T2 syntax. It is based on Aleksandar Veselinovic's PIC16F84 Assembler syntax file (pic.vim in the standard installation).","install_details":"Copy to $HOME\/.vim\/syntax or $VIM\/vimfiles\/syntax\r\n:call SetSyn(\"armasm\")\r\n\r\nYou may want to consider adding the following to your .vimrc as well:\r\nlet asmsyntax='armasm'\r\nlet filetype_inc='armasm'","5":"Copy to $HOME\/.vim\/syntax or $VIM\/vimfiles\/syntax\r\n:call SetSyn(\"armasm\")\r\n\r\nYou may want to consider adding the following to your .vimrc as well:\r\nlet asmsyntax='armasm'\r\nlet filetype_inc='armasm'","first_name":"Gerald","6":"Gerald","last_name":"Williams","7":"Williams","releases":[{"0":"888","vim_version":"6.0","1":"6.0","script_version":"1.2","2":"1.2","version_comment":"Converted file to Unix-style line endings (sorry about that)","3":"Converted file to Unix-style line endings (sorry about that)","package":"armasm.vim","4":"armasm.vim","src_id":"4029","5":"4029","creation_date":"1110947996","6":"1110947996"},{"0":"888","vim_version":"6.0","1":"6.0","script_version":"1.1","2":"1.1","version_comment":"Limited quotes (\",',|,||) to one line","3":"Limited quotes (\",',|,||) to one line","package":"armasm.vim","4":"armasm.vim","src_id":"2935","5":"2935","creation_date":"1081949382","6":"1081949382"},{"0":"888","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"armasm.vim","4":"armasm.vim","src_id":"2692","5":"2692","creation_date":"1075357339","6":"1075357339"}]},"887":{"script_id":"887","0":"887","script_name":"docbkhelper","1":"docbkhelper","script_type":"utility","2":"utility","summary":"some menus and mappings to ease editing DocBook XML","3":"some menus and mappings to ease editing DocBook XML","description":"As a plugin, docbkhelper adds a Plugin.Docbook.New Book menu item that creates a new DocBook buffer, with a basic skeleton. An ftplugin later adds other menu items and key mappings to add chapters, paras, sections, emphases, itemized lists... When invoked in visual modes, most of these mappings turn the selected text into a chapter, para, section...\r\n\r\nYou must install xmledit, http:\/\/www.vim.org\/scripts\/script.php?script_id=301 for docbkhelper mappings rely on xmledit's key mappings.","4":"As a plugin, docbkhelper adds a Plugin.Docbook.New Book menu item that creates a new DocBook buffer, with a basic skeleton. An ftplugin later adds other menu items and key mappings to add chapters, paras, sections, emphases, itemized lists... When invoked in visual modes, most of these mappings turn the selected text into a chapter, para, section...\r\n\r\nYou must install xmledit, http:\/\/www.vim.org\/scripts\/script.php?script_id=301 for docbkhelper mappings rely on xmledit's key mappings.","install_details":"Just unzip the file in your ~\/.vim directory and restart vim.","5":"Just unzip the file in your ~\/.vim directory and restart vim.","first_name":"Cedric","6":"Cedric","last_name":"Bouvier","7":"Bouvier","releases":[{"0":"887","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"docbkhelper.zip","4":"docbkhelper.zip","src_id":"2691","5":"2691","creation_date":"1075354835","6":"1075354835"}]},"886":{"script_id":"886","0":"886","script_name":"FormatComment.vim","1":"FormatComment.vim","script_type":"utility","2":"utility","summary":"Format-block (do a 'gq' format) on the comment the cursor is in","3":"Format-block (do a 'gq' format) on the comment the cursor is in","description":"\" Format-block (do a 'gq' format) on the comment the cursor is in; the type of\r\n\" comment is determined by context (i.e., \/*...*\/, \/\/..., #..., etc.).\r\n\"\r\n\" EXAMPLE SETUP\r\n\"\tmap gqc :call FormatComment()<CR>\r\n\r\nDEPENDENCIES:\r\n   FormatBlock.vim ( vimscript #885 )\r\n\r\nMy *actual* setup is:\r\n\r\n\" gqc - Format comment; comment-type is determined by context (i.e., \/*...*\/,\r\n\"       \/\/..., #..., etc.).\r\n\"\r\n\" NOTE: This will probably not work properly in C source for vim versions prior\r\n\"       to 6 because some of the search-patterns used are more advanced than\r\n\"       were available prior to version 6.\r\nexe SILENT . 'map <unique> gqc :call FormatComment()<CR>'\r\n\r\nWhere SILENT is set to '' or 'silent! ', depending upon vim's version (does it have silent?)\r\n\r\nThere is some stuff in there to handle our organization's \"standard function header\" comments specially; that 'if' block should be easily located and removed, or modified to your tastes.  If left as-is, you probably wouldn't trigger it anyway (so I left it in there as an example\/template).\r\n\r\nAlso, we use the convention that single-line 'C' comments should use the \/\/-style, while multi-line comments should use the \/*...*\/-style; so that's built into the function.  i.e., If a long \/\/-style comment gets formatted onto multiple lines, it will be converted to \/*...*\/-style; while a \/*...*\/-style comment that fits onto a single line will be converted to \/\/-style.  If this is not to your liking, it should be easily remedied; there are function calls made to to the conversions, simply comment the call(s) out (or remove them).\r\n\r\nThis function allows quick entry\/editing of comments without worrying about the line-break formatting.  Once finished, simply hit 'gqc' and the comment is reformatted.","4":"\" Format-block (do a 'gq' format) on the comment the cursor is in; the type of\r\n\" comment is determined by context (i.e., \/*...*\/, \/\/..., #..., etc.).\r\n\"\r\n\" EXAMPLE SETUP\r\n\"\tmap gqc :call FormatComment()<CR>\r\n\r\nDEPENDENCIES:\r\n   FormatBlock.vim ( vimscript #885 )\r\n\r\nMy *actual* setup is:\r\n\r\n\" gqc - Format comment; comment-type is determined by context (i.e., \/*...*\/,\r\n\"       \/\/..., #..., etc.).\r\n\"\r\n\" NOTE: This will probably not work properly in C source for vim versions prior\r\n\"       to 6 because some of the search-patterns used are more advanced than\r\n\"       were available prior to version 6.\r\nexe SILENT . 'map <unique> gqc :call FormatComment()<CR>'\r\n\r\nWhere SILENT is set to '' or 'silent! ', depending upon vim's version (does it have silent?)\r\n\r\nThere is some stuff in there to handle our organization's \"standard function header\" comments specially; that 'if' block should be easily located and removed, or modified to your tastes.  If left as-is, you probably wouldn't trigger it anyway (so I left it in there as an example\/template).\r\n\r\nAlso, we use the convention that single-line 'C' comments should use the \/\/-style, while multi-line comments should use the \/*...*\/-style; so that's built into the function.  i.e., If a long \/\/-style comment gets formatted onto multiple lines, it will be converted to \/*...*\/-style; while a \/*...*\/-style comment that fits onto a single line will be converted to \/\/-style.  If this is not to your liking, it should be easily remedied; there are function calls made to to the conversions, simply comment the call(s) out (or remove them).\r\n\r\nThis function allows quick entry\/editing of comments without worrying about the line-break formatting.  Once finished, simply hit 'gqc' and the comment is reformatted.","install_details":"I put this in my autoload directory (~\/vim\/autoload), so the function is automagically loaded as needed via an autocommand:\r\n\r\nautocmd FuncUndefined * exe 'runtime autoload\/' . expand('<afile>') . '.vim'","5":"I put this in my autoload directory (~\/vim\/autoload), so the function is automagically loaded as needed via an autocommand:\r\n\r\nautocmd FuncUndefined * exe 'runtime autoload\/' . expand('<afile>') . '.vim'","first_name":"Gary","6":"Gary","last_name":"Holloway","7":"Holloway","releases":[{"0":"886","vim_version":"6.0","1":"6.0","script_version":"1.4","2":"1.4","version_comment":"Initial upload","3":"Initial upload","package":"FormatComment.vim","4":"FormatComment.vim","src_id":"2690","5":"2690","creation_date":"1075311058","6":"1075311058"}]},"885":{"script_id":"885","0":"885","script_name":"FormatBlock","1":"FormatBlock","script_type":"utility","2":"utility","summary":"Format (i.e., gqq) a block of lines above\/below the current line","3":"Format (i.e., gqq) a block of lines above\/below the current line","description":"\" Format (i.e., gqq) a block of lines above\/below the current line from the\r\n\" line matching <beg_pattern> to the line matching <end_pattern>; intervening\r\n\" lines of the block should match <in_pattern>, if given.\r\n\"\r\n\r\n\" EXAMPLE SETUP\r\n\" Format block (do a 'gq' format) on a C-style statement (i.e., from cursor's\r\n\" line to line ending with ';'):\r\n\"\r\n\"\tmap gqs :call FormatBlock('', ';$', '')<CR>\r\n\r\nPrimarily used as a \"helper\" function to FormatComment ( vimscript #886 )","4":"\" Format (i.e., gqq) a block of lines above\/below the current line from the\r\n\" line matching <beg_pattern> to the line matching <end_pattern>; intervening\r\n\" lines of the block should match <in_pattern>, if given.\r\n\"\r\n\r\n\" EXAMPLE SETUP\r\n\" Format block (do a 'gq' format) on a C-style statement (i.e., from cursor's\r\n\" line to line ending with ';'):\r\n\"\r\n\"\tmap gqs :call FormatBlock('', ';$', '')<CR>\r\n\r\nPrimarily used as a \"helper\" function to FormatComment ( vimscript #886 )","install_details":"I put this in my autoload directory (~\/vim\/autoload), so the function is automagically loaded as needed via an autocommand:\r\n\r\nautocmd FuncUndefined * exe 'runtime autoload\/' . expand('<afile>') . '.vim'","5":"I put this in my autoload directory (~\/vim\/autoload), so the function is automagically loaded as needed via an autocommand:\r\n\r\nautocmd FuncUndefined * exe 'runtime autoload\/' . expand('<afile>') . '.vim'","first_name":"Gary","6":"Gary","last_name":"Holloway","7":"Holloway","releases":[{"0":"885","vim_version":"6.0","1":"6.0","script_version":"1.3","2":"1.3","version_comment":"Initial upload","3":"Initial upload","package":"FormatBlock.vim","4":"FormatBlock.vim","src_id":"2689","5":"2689","creation_date":"1075310609","6":"1075310609"}]},"884":{"script_id":"884","0":"884","script_name":"AutoAlign","1":"AutoAlign","script_type":"ftplugin","2":"ftplugin","summary":"Automatically align as you type (autoalign): bib c c++ html maple matlab tex vim","3":"Automatically align as you type (autoalign): bib c c++ html maple matlab tex vim","description":"[AutoAlign V12 AND LATER REQUIRES VIMBALL V18 OR LATER TO UNPACK]\r\n                               [AutoAlign also requires vimscript#294]\r\n\r\n Note:  this plugin is not a right-margin justification tool; see vimscript#177 for that\r\n\r\nAutoAlign is currently composed of one regular plugin and six ftplugins.  As you type statements such as (for vim)\r\n\r\n\tlet xyz= 1\r\n\tlet x= 2\r\n\r\nthe ftplugin\/vim\/AutoAlign script will call upon the Align command to line up those equal signs, resulting in aligned equal signs (which can't be usefully shown here due to browsers' use of proportional fonts).\r\n\r\nSimilarly the c ftplugin will do so for\r\n\r\n\tx= 3;\r\n\txy[0]= 4;\r\n\tabc->def= 5;\r\n\r\n\tone= 2;\r\n\r\n(it only applies to what you're currently typing, it doesn't take any previously existing lines into account).  For c++,\r\n= signs, <<, and >> operators get aligned.  For maple, :=.  \r\n\r\nFormer Version Notes:\r\n   5: AutoAlign maps and functions changed to allow use of \".\" to repeat entry of =... expressions.  Uses g:mapleader instead of a built-in backslash to access AlignMaps.  First release of AutoAlign using vim's user-help. \r\n   4: Now supports: bib c cpp tex vim. AutoAlign now breaks the undo sequence at every align operation, so one undo undoes the entire AutoAlign.  Bugfix: (with virtual edit) has been fixed (when backspacing over ==).  Bugfix: unwanted beeping due to virtual edit being off fixed\r\n   3: Now supported: bib c tex vim.  :AA toggles AutoAlign on and off. AutoAlign now auto-aligns only blocks of alignable text.  cecutil.vim included (SaveMark, SaveWinPosn, etc)\r\n\r\n(alpha\/beta version available at http:\/\/www.drchip.org\/astronaut\/vim\/index.html#AUTOALIGN)\r\n","4":"[AutoAlign V12 AND LATER REQUIRES VIMBALL V18 OR LATER TO UNPACK]\r\n                               [AutoAlign also requires vimscript#294]\r\n\r\n Note:  this plugin is not a right-margin justification tool; see vimscript#177 for that\r\n\r\nAutoAlign is currently composed of one regular plugin and six ftplugins.  As you type statements such as (for vim)\r\n\r\n\tlet xyz= 1\r\n\tlet x= 2\r\n\r\nthe ftplugin\/vim\/AutoAlign script will call upon the Align command to line up those equal signs, resulting in aligned equal signs (which can't be usefully shown here due to browsers' use of proportional fonts).\r\n\r\nSimilarly the c ftplugin will do so for\r\n\r\n\tx= 3;\r\n\txy[0]= 4;\r\n\tabc->def= 5;\r\n\r\n\tone= 2;\r\n\r\n(it only applies to what you're currently typing, it doesn't take any previously existing lines into account).  For c++,\r\n= signs, <<, and >> operators get aligned.  For maple, :=.  \r\n\r\nFormer Version Notes:\r\n   5: AutoAlign maps and functions changed to allow use of \".\" to repeat entry of =... expressions.  Uses g:mapleader instead of a built-in backslash to access AlignMaps.  First release of AutoAlign using vim's user-help. \r\n   4: Now supports: bib c cpp tex vim. AutoAlign now breaks the undo sequence at every align operation, so one undo undoes the entire AutoAlign.  Bugfix: (with virtual edit) has been fixed (when backspacing over ==).  Bugfix: unwanted beeping due to virtual edit being off fixed\r\n   3: Now supported: bib c tex vim.  :AA toggles AutoAlign on and off. AutoAlign now auto-aligns only blocks of alignable text.  cecutil.vim included (SaveMark, SaveWinPosn, etc)\r\n\r\n(alpha\/beta version available at http:\/\/www.drchip.org\/astronaut\/vim\/index.html#AUTOALIGN)\r\n","install_details":"1. Get vimball v18 or later (vimscript#1502) if you  haven't done so already.  Be sure to remove all vestiges of any older vimball versions, too.  (if you have vim 7.1a or later, you probably can skip this step)\r\n2. vim AutoAlign.vba.gz\r\n   :so %\r\n   :q\r\n3. AutoAlign uses vimscript#294 (Align, AlignMaps); you'll also need that if you haven't gotten it yet.","5":"1. Get vimball v18 or later (vimscript#1502) if you  haven't done so already.  Be sure to remove all vestiges of any older vimball versions, too.  (if you have vim 7.1a or later, you probably can skip this step)\r\n2. vim AutoAlign.vba.gz\r\n   :so %\r\n   :q\r\n3. AutoAlign uses vimscript#294 (Align, AlignMaps); you'll also need that if you haven't gotten it yet.","first_name":"Charles","6":"Charles","last_name":"Campbell","7":"Campbell","releases":[{"0":"884","vim_version":"7.3","1":"7.3","script_version":"14","2":"14","version_comment":"various bugfixes","3":"various bugfixes","package":"AutoAlign.vba.gz","4":"AutoAlign.vba.gz","src_id":"21105","5":"21105","creation_date":"1385414286","6":"1385414286"},{"0":"884","vim_version":"7.0","1":"7.0","script_version":"13","2":"13","version_comment":"AutoAlign leaves \".\" alone when it starts; thus, one can now insert \"= 0\", for example, and re-apply it with vim's \".\" operator.  Tnx to Antony Scriven!\r\nSome bug fixes for C++'s > and < auto-aligning.\r\nAutoAlign now passes the pluginkiller test. (vimscript#1489)","3":"AutoAlign leaves \".\" alone when it starts; thus, one can now insert \"= 0\", for example, and re-apply it with vim's \".\" operator.  Tnx to Antony Scriven!\r\nSome bug fixes for C++'s > and < auto-aligning.\r\nAutoAlign now passes the pluginkiller test. (vimscript#1489)","package":"AutoAlign.vba.gz","4":"AutoAlign.vba.gz","src_id":"7510","5":"7510","creation_date":"1187272169","6":"1187272169"},{"0":"884","vim_version":"7.0","1":"7.0","script_version":"12","2":"12","version_comment":"Fixed a bug with ftplugin\/bib\/AutoAlign.vim (ie. for LaTeX *.bib files)","3":"Fixed a bug with ftplugin\/bib\/AutoAlign.vim (ie. for LaTeX *.bib files)","package":"AutoAlign.vba.gz","4":"AutoAlign.vba.gz","src_id":"6207","5":"6207","creation_date":"1158668891","6":"1158668891"},{"0":"884","vim_version":"6.0","1":"6.0","script_version":"11","2":"11","version_comment":"I inadvertently left debugging on in AutoAlign v10; this one has debugging de-activated.\r\nPlus some bugfixes.","3":"I inadvertently left debugging on in AutoAlign v10; this one has debugging de-activated.\r\nPlus some bugfixes.","package":"AutoAlign.tar.gz","4":"AutoAlign.tar.gz","src_id":"5482","5":"5482","creation_date":"1143099464","6":"1143099464"},{"0":"884","vim_version":"6.0","1":"6.0","script_version":"10","2":"10","version_comment":"Works with ve= and ve=all.  Uses startinsert or startinsert!, depending on whether the cursor in inside the line or being used to append.","3":"Works with ve= and ve=all.  Uses startinsert or startinsert!, depending on whether the cursor in inside the line or being used to append.","package":"AutoAlign.tar.gz","4":"AutoAlign.tar.gz","src_id":"5468","5":"5468","creation_date":"1142852022","6":"1142852022"},{"0":"884","vim_version":"6.0","1":"6.0","script_version":"7","2":"7","version_comment":"AutoAlign now supports html\r\nAutoAlign now has b:autoalign_suspend# for suspend-alignment patterns\r\nAn undefined b:autoalign_reqdpat# no longer causes an error\r\n","3":"AutoAlign now supports html\r\nAutoAlign now has b:autoalign_suspend# for suspend-alignment patterns\r\nAn undefined b:autoalign_reqdpat# no longer causes an error\r\n","package":"AutoAlign.tar.gz","4":"AutoAlign.tar.gz","src_id":"4815","5":"4815","creation_date":"1133166974","6":"1133166974"},{"0":"884","vim_version":"6.0","1":"6.0","script_version":"6","2":"6","version_comment":"AutoAlign is now split into a plugin containing the majority of vimscript; the supported ftplugins contain the invoking imaps and pattern definitions that the plugin uses.  Matlab support added.  Should be easy to add more languages should anyone wish to contribute the needed patterns!  Currently supported: bib c cpp maple matlab tex vim\r\n","3":"AutoAlign is now split into a plugin containing the majority of vimscript; the supported ftplugins contain the invoking imaps and pattern definitions that the plugin uses.  Matlab support added.  Should be easy to add more languages should anyone wish to contribute the needed patterns!  Currently supported: bib c cpp maple matlab tex vim\r\n","package":"AutoAlign.tar.gz","4":"AutoAlign.tar.gz","src_id":"4099","5":"4099","creation_date":"1112173779","6":"1112173779"}]},"883":{"script_id":"883","0":"883","script_name":"ods.vim","1":"ods.vim","script_type":"syntax","2":"syntax","summary":"syntax highlighting for ODS Toolbox rule language","3":"syntax highlighting for ODS Toolbox rule language","description":" basic syntax highlighting for ODS Toolbox rule language","4":" basic syntax highlighting for ODS Toolbox rule language","install_details":"","5":"","first_name":"granite","6":"granite","last_name":"granite","7":"granite","releases":[{"0":"883","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"ods.vim","4":"ods.vim","src_id":"2685","5":"2685","creation_date":"1075264776","6":"1075264776"}]},"882":{"script_id":"882","0":"882","script_name":"fluxkeys.vim","1":"fluxkeys.vim","script_type":"syntax","2":"syntax","summary":"syntaxhighlighting for key-files of fluxbox","3":"syntaxhighlighting for key-files of fluxbox","description":"this syntax-file enables some basic syntaxhighlighting for keyfiles used by the fluxbox-windowmanager (http:\/\/www.fluxbox.org)","4":"this syntax-file enables some basic syntaxhighlighting for keyfiles used by the fluxbox-windowmanager (http:\/\/www.fluxbox.org)","install_details":"just put fluxkeys.vim into $HOME\/.vim\/syntax\/   and add a   \" ! vim:ft=fluxkeys\" at the end of your key file.","5":"just put fluxkeys.vim into $HOME\/.vim\/syntax\/   and add a   \" ! vim:ft=fluxkeys\" at the end of your key file.","first_name":"Mathias","6":"Mathias","last_name":"Gumz","7":"Gumz","releases":[{"0":"882","vim_version":"6.0","1":"6.0","script_version":"1.1.1","2":"1.1.1","version_comment":"updated syntax to match fluxbox-1.1.1, thanx to Harry Bullen who provided the updated version","3":"updated syntax to match fluxbox-1.1.1, thanx to Harry Bullen who provided the updated version","package":"fluxkeys.vim","4":"fluxkeys.vim","src_id":"11641","5":"11641","creation_date":"1257088046","6":"1257088046"},{"0":"882","vim_version":"6.0","1":"6.0","script_version":"0.9.13-r1","2":"0.9.13-r1","version_comment":"enhanced highlighting for MacroCmd and some other minor parameters","3":"enhanced highlighting for MacroCmd and some other minor parameters","package":"fluxkeys.vim","4":"fluxkeys.vim","src_id":"4389","5":"4389","creation_date":"1119580460","6":"1119580460"},{"0":"882","vim_version":"6.0","1":"6.0","script_version":"0.9.13","2":"0.9.13","version_comment":"synced with fluxbox-0.9.13, added much better highlighting and visual error feedback","3":"synced with fluxbox-0.9.13, added much better highlighting and visual error feedback","package":"fluxkeys.vim","4":"fluxkeys.vim","src_id":"4388","5":"4388","creation_date":"1119573193","6":"1119573193"},{"0":"882","vim_version":"6.0","1":"6.0","script_version":"0.1-r1","2":"0.1-r1","version_comment":"updated maintainer info","3":"updated maintainer info","package":"fluxkeys.vim","4":"fluxkeys.vim","src_id":"2681","5":"2681","creation_date":"1075182041","6":"1075182041"}]},"881":{"script_id":"881","0":"881","script_name":"buttercream.vim","1":"buttercream.vim","script_type":"color scheme","2":"color scheme","summary":"Smooth and colorful yellowish theme","3":"Smooth and colorful yellowish theme","description":"A script which sports a pale yellow background and while it has lots of colors it is still very smooth and usable for long sessions. Screenshot available: http:\/\/hakan.prinsig.se\/files\/images\/gvim-buttercream.png","4":"A script which sports a pale yellow background and while it has lots of colors it is still very smooth and usable for long sessions. Screenshot available: http:\/\/hakan.prinsig.se\/files\/images\/gvim-buttercream.png","install_details":"Just copy it to your ~\/.vim\/colors directory on *NIX, on Windows copy it to the vimfiles\/colors\/ directory under the vim installation directory.","5":"Just copy it to your ~\/.vim\/colors directory on *NIX, on Windows copy it to the vimfiles\/colors\/ directory under the vim installation directory.","first_name":"H\u00c3\u00a5kan","6":"H\u00c3\u00a5kan","last_name":"Wikstr\u00c3\u00b6m","7":"Wikstr\u00c3\u00b6m","releases":[{"0":"881","vim_version":"6.0","1":"6.0","script_version":"1.1","2":"1.1","version_comment":"Paler colors - the background is now #FFFFDE.This looks more like I intended it to look like in the first place - thanks to my new flatscreen that displays colors correctly (unlike my old very pale CRT).","3":"Paler colors - the background is now #FFFFDE.This looks more like I intended it to look like in the first place - thanks to my new flatscreen that displays colors correctly (unlike my old very pale CRT).","package":"buttercream.vim","4":"buttercream.vim","src_id":"5551","5":"5551","creation_date":"1144935898","6":"1144935898"}]},"880":{"script_id":"880","0":"880","script_name":"passwd","1":"passwd","script_type":"syntax","2":"syntax","summary":"syntax of the \/etc\/passwd file","3":"syntax of the \/etc\/passwd file","description":"This is highlighting syntax for the \/etc\/passwd file.","4":"This is highlighting syntax for the \/etc\/passwd file.","install_details":"Drop it into your syntax directory:\r\n  1. mkdir -p ~\/.vim\/syntax\r\n  2. mv passwd.vim ~\/.vim\/syntax\/.\r\n\r\nThen, use\r\n       :setf passwd\r\n\r\n, or add this to your ~\/.vim\/filetypes.vim to enable auto-detection:\r\n  augroup filetypedetect\r\n  au BufNewFile,BufRead passwd   setf passwd\r\n  augroup END ","5":"Drop it into your syntax directory:\r\n  1. mkdir -p ~\/.vim\/syntax\r\n  2. mv passwd.vim ~\/.vim\/syntax\/.\r\n\r\nThen, use\r\n       :setf passwd\r\n\r\n, or add this to your ~\/.vim\/filetypes.vim to enable auto-detection:\r\n  augroup filetypedetect\r\n  au BufNewFile,BufRead passwd   setf passwd\r\n  augroup END ","first_name":"Yakov","6":"Yakov","last_name":"Lerner","7":"Lerner","releases":[{"0":"880","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"passwd.vim","4":"passwd.vim","src_id":"2676","5":"2676","creation_date":"1075084057","6":"1075084057"}]},"879":{"script_id":"879","0":"879","script_name":"RegExpRef","1":"RegExpRef","script_type":"utility","2":"utility","summary":"short reference of regular expression metacharacters","3":"short reference of regular expression metacharacters","description":"This text-file is an overview of the most used regular expression metacharacters of Vim and GNU's grep tool.","4":"This text-file is an overview of the most used regular expression metacharacters of Vim and GNU's grep tool.","install_details":"Copy the file regexpref.txt to\r\nUnix: ~\/.vim\/doc\r\nWindows: c:\\vimfiles\\doc\r\n\r\nTo add this file to the Vim's help system do:\r\nUnix: helptags ~\/.vim\/doc\r\nWindows: helptags c:\\vimfiles\\doc\r\n\r\nAdd a mapping like\r\n  map <Leader>re :help regexpref<cr>\r\nto get quick access to the reference.\r\n\r\nPressing \\re will then view the reference.\r\n\r\nMemory aid: re = (r)egular (e)xpression ","5":"Copy the file regexpref.txt to\r\nUnix: ~\/.vim\/doc\r\nWindows: c:\\vimfiles\\doc\r\n\r\nTo add this file to the Vim's help system do:\r\nUnix: helptags ~\/.vim\/doc\r\nWindows: helptags c:\\vimfiles\\doc\r\n\r\nAdd a mapping like\r\n  map <Leader>re :help regexpref<cr>\r\nto get quick access to the reference.\r\n\r\nPressing \\re will then view the reference.\r\n\r\nMemory aid: re = (r)egular (e)xpression ","first_name":"Christian","6":"Christian","last_name":"Habermann","7":"Habermann","releases":[{"0":"879","vim_version":"6.0","1":"6.0","script_version":"1.0.0","2":"1.0.0","version_comment":"Initial upload","3":"Initial upload","package":"regexpref.txt","4":"regexpref.txt","src_id":"2674","5":"2674","creation_date":"1075015777","6":"1075015777"}]},"878":{"script_id":"878","0":"878","script_name":"Posting","1":"Posting","script_type":"utility","2":"utility","summary":"Mappings primarily intended to ease preparing of USENET\/eMail articles","3":"Mappings primarily intended to ease preparing of USENET\/eMail articles","description":"\"Posting\" provides a few mappings I once messed around with in order to ease preparing USENET\/email articles with GVim. (Due to a malfunction at vim.org I had to register again. Version 1.3 can be found at http:\/\/www.vim.org\/scripts\/script.php?script_id=851.) \r\n","4":"\"Posting\" provides a few mappings I once messed around with in order to ease preparing USENET\/email articles with GVim. (Due to a malfunction at vim.org I had to register again. Version 1.3 can be found at http:\/\/www.vim.org\/scripts\/script.php?script_id=851.) \r\n","install_details":":source posting.vim \r\n:Post 72 \r\n","5":":source posting.vim \r\n:Post 72 \r\n","first_name":"Tim","6":"Tim","last_name":"Allen","7":"Allen","releases":[{"0":"878","vim_version":"6.0","1":"6.0","script_version":"1.31","2":"1.31","version_comment":"Initial upload","3":"Initial upload","package":"posting.vim","4":"posting.vim","src_id":"2673","5":"2673","creation_date":"1074931695","6":"1074931695"}]},"877":{"script_id":"877","0":"877","script_name":"GVColors","1":"GVColors","script_type":"utility","2":"utility","summary":"Uses gvim to display X-windows colors (keywords: colorlist rgb.txt)","3":"Uses gvim to display X-windows colors (keywords: colorlist rgb.txt)","description":"<gvcolors.vim> displays a list of colors available under X-windows in their own\r\ncolor.  It is based on vimtip#634 contributed by mohsin at\r\nhttp:\/\/www.cs.albany.edu\/~mosh.\r\n\r\nThe script intercepts several motions and sets up syntax highlighting to\r\ndisplay the named colors.\r\n\r\nExample:\r\n\r\n  gvim gvcolors.vim\r\n  :GVColors\r\n\r\nMotions:\r\n\t   j      move display down one line\r\n\t   k      move display up   one line\r\n\t ctrl-d   move display down &scroll lines (see :he 'scroll')\r\n\t ctrl-u   move display up   &scroll lines (see :he 'scroll')\r\n\t ctrl-f   move display down one page\r\n\t ctrl-b   move display up   one page\r\n\t pageup   same as ctrl-b\r\n\t pagedown same as ctrl-f\r\n\r\nSpecial care to show just a single page of colors is taken because\r\nVim is limited to displaying approximately 224 colors with syntax\r\nhighlighting.\r\n\r\nHistory\/Features:\r\n\r\nv3: Supports use of the mouse and slider bars.\r\n\r\nv2: Looks up colors in \/usr\/X11R6\/lib\/X11\/rgb.txt,\r\nwhich may be overridden by let g:rgbtxtfile=\"path\";\r\nnow shows red:green:blue assignments as well as\r\nthe colored text! \r\n\r\n(alpha\/beta version available at http:\/\/www.drchip.org\/astronaut\/vim\/index.html#GVCOLORS)\r\n","4":"<gvcolors.vim> displays a list of colors available under X-windows in their own\r\ncolor.  It is based on vimtip#634 contributed by mohsin at\r\nhttp:\/\/www.cs.albany.edu\/~mosh.\r\n\r\nThe script intercepts several motions and sets up syntax highlighting to\r\ndisplay the named colors.\r\n\r\nExample:\r\n\r\n  gvim gvcolors.vim\r\n  :GVColors\r\n\r\nMotions:\r\n\t   j      move display down one line\r\n\t   k      move display up   one line\r\n\t ctrl-d   move display down &scroll lines (see :he 'scroll')\r\n\t ctrl-u   move display up   &scroll lines (see :he 'scroll')\r\n\t ctrl-f   move display down one page\r\n\t ctrl-b   move display up   one page\r\n\t pageup   same as ctrl-b\r\n\t pagedown same as ctrl-f\r\n\r\nSpecial care to show just a single page of colors is taken because\r\nVim is limited to displaying approximately 224 colors with syntax\r\nhighlighting.\r\n\r\nHistory\/Features:\r\n\r\nv3: Supports use of the mouse and slider bars.\r\n\r\nv2: Looks up colors in \/usr\/X11R6\/lib\/X11\/rgb.txt,\r\nwhich may be overridden by let g:rgbtxtfile=\"path\";\r\nnow shows red:green:blue assignments as well as\r\nthe colored text! \r\n\r\n(alpha\/beta version available at http:\/\/www.drchip.org\/astronaut\/vim\/index.html#GVCOLORS)\r\n","install_details":"Put <gvcolors.vim> wherever its convenient (its *not* a plugin):\r\n\r\n  gvim gvcolors.vba.gz\r\n  :so %","5":"Put <gvcolors.vim> wherever its convenient (its *not* a plugin):\r\n\r\n  gvim gvcolors.vba.gz\r\n  :so %","first_name":"Charles","6":"Charles","last_name":"Campbell","7":"Campbell","releases":[{"0":"877","vim_version":"7.0","1":"7.0","script_version":"6","2":"6","version_comment":"* allows rightmouse to click between dark & bright backgrounds\r\n* double-click with leftmouse will pull the color line up to the top of the screen, thereby displaying its rgb values\r\n* Vim version 7 now supports 1000s of highlighting groups; gvcolors takes advantage of that\r\n* Looks in some more places for where the rgb.txt file may be.\r\n","3":"* allows rightmouse to click between dark & bright backgrounds\r\n* double-click with leftmouse will pull the color line up to the top of the screen, thereby displaying its rgb values\r\n* Vim version 7 now supports 1000s of highlighting groups; gvcolors takes advantage of that\r\n* Looks in some more places for where the rgb.txt file may be.\r\n","package":"gvcolors.vba.gz","4":"gvcolors.vba.gz","src_id":"7775","5":"7775","creation_date":"1192025556","6":"1192025556"},{"0":"877","vim_version":"6.0","1":"6.0","script_version":"5","2":"5","version_comment":"Quicker refresh when moving in the text via the scrollbar.  Up to 188 colors can be shown at a time; this is a slight reduction to avoid problems with Vim's limited quantity of concurrently displayable colors.","3":"Quicker refresh when moving in the text via the scrollbar.  Up to 188 colors can be shown at a time; this is a slight reduction to avoid problems with Vim's limited quantity of concurrently displayable colors.","package":"gvcolors.vim","4":"gvcolors.vim","src_id":"3222","5":"3222","creation_date":"1089712007","6":"1089712007"},{"0":"877","vim_version":"6.0","1":"6.0","script_version":"4","2":"4","version_comment":"Shift-Leftmouse will toggle gvcolors' background between dark and light.\r\nBugfix: full screen displays can result in too many colors for Vim to\r\ndisplay at one time; gvcolors now limits itself to 192 colors (any more\r\nwill be set to \"Ignore\" highlighting).\r\n","3":"Shift-Leftmouse will toggle gvcolors' background between dark and light.\r\nBugfix: full screen displays can result in too many colors for Vim to\r\ndisplay at one time; gvcolors now limits itself to 192 colors (any more\r\nwill be set to \"Ignore\" highlighting).\r\n","package":"gvcolors.vim","4":"gvcolors.vim","src_id":"2903","5":"2903","creation_date":"1080896147","6":"1080896147"}]},"876":{"script_id":"876","0":"876","script_name":"automation.vim","1":"automation.vim","script_type":"color scheme","2":"color scheme","summary":"Light Grey Color Scheme","3":"Light Grey Color Scheme","description":"This color scheme was created to give the look of a modern IDE.  It has a very light grey background , grey gutter and blue comments with grey background.  ","4":"This color scheme was created to give the look of a modern IDE.  It has a very light grey background , grey gutter and blue comments with grey background.  ","install_details":"","5":"","first_name":"Ken","6":"Ken","last_name":"McConnell","7":"McConnell","releases":[{"0":"876","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"automation.vim","4":"automation.vim","src_id":"2663","5":"2663","creation_date":"1074153945","6":"1074153945"}]},"875":{"script_id":"875","0":"875","script_name":"bufman.vim","1":"bufman.vim","script_type":"ftplugin","2":"ftplugin","summary":"Quickly switch between buffers without knowing their numbers.","3":"Quickly switch between buffers without knowing their numbers.","description":"Easily switch between buffers without knowing their numbers. \r\n\r\nThe SHIFT+F1...SHIFT+F12 keys are mapped to switch to the Nth listed buffer (not buffer #N). Quite handy.\r\n\r\nThere are also other mappings to switch to the next and previous buffer and to close the current buffer.\r\n\r\nNo windows that consume precious screen-space will be created.","4":"Easily switch between buffers without knowing their numbers. \r\n\r\nThe SHIFT+F1...SHIFT+F12 keys are mapped to switch to the Nth listed buffer (not buffer #N). Quite handy.\r\n\r\nThere are also other mappings to switch to the next and previous buffer and to close the current buffer.\r\n\r\nNo windows that consume precious screen-space will be created.","install_details":"Copy the file to your plugins directory or :source it. Read the file for detailed instructions.","5":"Copy the file to your plugins directory or :source it. Read the file for detailed instructions.","first_name":"Gustavo","6":"Gustavo","last_name":"Picon","7":"Picon","releases":[{"0":"875","vim_version":"6.0","1":"6.0","script_version":"1.4","2":"1.4","version_comment":"Initial upload","3":"Initial upload","package":"bufman.vim","4":"bufman.vim","src_id":"2662","5":"2662","creation_date":"1074008628","6":"1074008628"}]},"874":{"script_id":"874","0":"874","script_name":"emacsmode","1":"emacsmode","script_type":"ftplugin","2":"ftplugin","summary":"Parse Emacs -*- Mode lines and set equivalent Vim options","3":"Parse Emacs -*- Mode lines and set equivalent Vim options","description":"This is a script to read the Emacs -*- Mode -*- lines that can be found at the\r\ntop of many source code files.  I don't use Emacs, but a lot of source files have the lines.\r\n\r\nI tested this out by using it on the Mozilla code base, so the cases that are\r\nhandled are what appear there.  If there are other options that you find in\r\nother Emacs mode lines, send me an email so that I can get them added.\r\n","4":"This is a script to read the Emacs -*- Mode -*- lines that can be found at the\r\ntop of many source code files.  I don't use Emacs, but a lot of source files have the lines.\r\n\r\nI tested this out by using it on the Mozilla code base, so the cases that are\r\nhandled are what appear there.  If there are other options that you find in\r\nother Emacs mode lines, send me an email so that I can get them added.\r\n","install_details":"o install, simply copy emacsmode.vim an emacsmode.pl to your ~\/.vim\/plugin\/\r\ndirectory.  If you have a perl enabled Vim, you can omit the emacsmode.pl\r\nscript, since it won't ever be called.\r\n\r\nIf you install into the perl runtime directory (i.e. \/usr\/share\/vim,) and you\r\ndon't have a perl enabled Vim, you'll have to change one line in emacsmode.vim\r\nto point to the place where emacsmode.pl is installed.\r\n","5":"o install, simply copy emacsmode.vim an emacsmode.pl to your ~\/.vim\/plugin\/\r\ndirectory.  If you have a perl enabled Vim, you can omit the emacsmode.pl\r\nscript, since it won't ever be called.\r\n\r\nIf you install into the perl runtime directory (i.e. \/usr\/share\/vim,) and you\r\ndon't have a perl enabled Vim, you'll have to change one line in emacsmode.vim\r\nto point to the place where emacsmode.pl is installed.\r\n","first_name":"Jerry","6":"Jerry","last_name":"Talkington","7":"Talkington","releases":[{"0":"874","vim_version":"6.0","1":"6.0","script_version":"0.03","2":"0.03","version_comment":"Fixes a bug that would generate an error if a -*- line was present without a Mode: declaration.","3":"Fixes a bug that would generate an error if a -*- line was present without a Mode: declaration.","package":"emacsmode-0.03.tar.gz","4":"emacsmode-0.03.tar.gz","src_id":"2886","5":"2886","creation_date":"1080473765","6":"1080473765"},{"0":"874","vim_version":"6.0","1":"6.0","script_version":"0.02","2":"0.02","version_comment":"Fixes a stupid bug that would cause error messages when a file didn't contain the -*- Mode -*- line.","3":"Fixes a stupid bug that would cause error messages when a file didn't contain the -*- Mode -*- line.","package":"emacsmode.tar.gz","4":"emacsmode.tar.gz","src_id":"2659","5":"2659","creation_date":"1073897643","6":"1073897643"}]},"873":{"script_id":"873","0":"873","script_name":"srec.vim","1":"srec.vim","script_type":"syntax","2":"syntax","summary":"SREC syntax","3":"SREC syntax","description":"Colorizes SREC (Motorola S-Record) files.","4":"Colorizes SREC (Motorola S-Record) files.","install_details":"","5":"","first_name":"peter","6":"peter","last_name":"sommerfeld","7":"sommerfeld","releases":[{"0":"873","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"srec.vim","4":"srec.vim","src_id":"2648","5":"2648","creation_date":"1073297481","6":"1073297481"}]},"872":{"script_id":"872","0":"872","script_name":"Syntax context abbreviations","1":"Syntax context abbreviations","script_type":"utility","2":"utility","summary":"Abbreviations that only happen outside comments","3":"Abbreviations that only happen outside comments","description":"Abbreviations in language files can sometimes be annoying if they are not intended for inside comments (capitalisation is a good example). Support for <buffer> is included.\r\n\r\nThis script allows you to create abbreviations that do not happen inside comments.\r\nSynabbrev[!] [<buffer>] {lhs} {RHS}\r\n\r\neg \r\nSynabbrev to To\r\n\r\n\r\n\r\n\r\n","4":"Abbreviations in language files can sometimes be annoying if they are not intended for inside comments (capitalisation is a good example). Support for <buffer> is included.\r\n\r\nThis script allows you to create abbreviations that do not happen inside comments.\r\nSynabbrev[!] [<buffer>] {lhs} {RHS}\r\n\r\neg \r\nSynabbrev to To\r\n\r\n\r\n\r\n\r\n","install_details":"Add to ~\/vimfiles\/plugin  or  ~\/.vim\/plugin\r\nAdd to ftplugin files as appropriate","5":"Add to ~\/vimfiles\/plugin  or  ~\/.vim\/plugin\r\nAdd to ftplugin files as appropriate","first_name":"Michael","6":"Michael","last_name":"Geddes","7":"Geddes","releases":[{"0":"872","vim_version":"6.0","1":"6.0","script_version":"0.1unix","2":"0.1unix","version_comment":"fileformat=unix","3":"fileformat=unix","package":"synabbrev.vim","4":"synabbrev.vim","src_id":"10252","5":"10252","creation_date":"1237532876","6":"1237532876"},{"0":"872","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"synabbrev.vim","4":"synabbrev.vim","src_id":"2643","5":"2643","creation_date":"1072922643","6":"1072922643"}]},"871":{"script_id":"871","0":"871","script_name":"allout.vim","1":"allout.vim","script_type":"ftplugin","2":"ftplugin","summary":"Tools for handling Allout (outline) files","3":"Tools for handling Allout (outline) files","description":"Allout files are a handy synoptic (or tree-like) representation of a document.  Such files were originally introduced as a GNU Emacs mode.  Vim offers tools and help for browsing or editing these Allout files.\r\n\r\nOnce installed, syntax colouring of Allout files should work in standard Vim.  Allout specific commands and mappings require a Python-enabled Vim.\r\n","4":"Allout files are a handy synoptic (or tree-like) representation of a document.  Such files were originally introduced as a GNU Emacs mode.  Vim offers tools and help for browsing or editing these Allout files.\r\n\r\nOnce installed, syntax colouring of Allout files should work in standard Vim.  Allout specific commands and mappings require a Python-enabled Vim.\r\n","install_details":"Refetch a recent Allout-Vim  from:\r\n\r\n    http:\/\/fp-etc.progiciels-bpi.ca\/showfile.html?mode=archives\r\n\r\nWhen on Unix (or Linux), fech a .tgz archive from above, unpack it and look at README.\r\n\r\nIf on Windows, fetch a .zip archive from above, move to the directory holding ftplugin\/, syntax\/, etc. and unpack the archive once there.  For more advice about how to get the Python part of the tool in motion with Vim, visit and read:\r\n\r\n    http:\/\/fp-etc.progiciels-bpi.ca\/showfile.html?name=allout\/vim\/README\r\n\r\nfor more detailed installation instructions.\r\n\r\n","5":"Refetch a recent Allout-Vim  from:\r\n\r\n    http:\/\/fp-etc.progiciels-bpi.ca\/showfile.html?mode=archives\r\n\r\nWhen on Unix (or Linux), fech a .tgz archive from above, unpack it and look at README.\r\n\r\nIf on Windows, fetch a .zip archive from above, move to the directory holding ftplugin\/, syntax\/, etc. and unpack the archive once there.  For more advice about how to get the Python part of the tool in motion with Vim, visit and read:\r\n\r\n    http:\/\/fp-etc.progiciels-bpi.ca\/showfile.html?name=allout\/vim\/README\r\n\r\nfor more detailed installation instructions.\r\n\r\n","first_name":"Fran\u00c3\u00a7ois","6":"Fran\u00c3\u00a7ois","last_name":"Pinard","7":"Pinard","releases":[{"0":"871","vim_version":"6.0","1":"6.0","script_version":"031231","2":"031231","version_comment":"Initial upload","3":"Initial upload","package":"allout-vim-031231.zip","4":"allout-vim-031231.zip","src_id":"2641","5":"2641","creation_date":"1072870142","6":"1072870142"}]},"870":{"script_id":"870","0":"870","script_name":"changeColorScheme.vim","1":"changeColorScheme.vim","script_type":"utility","2":"utility","summary":"change color schemes","3":"change color schemes","description":" Got ideas from following tips and scripts \r\n vimtip #341, vimtip #358, vimscript #668, vimscript #109 \r\n\r\n Usage:\r\n When this script is loaded, it will populate an array with each of color \r\n scheme's file path.  You can then load different color schemes using \r\n NextColorScheme(), PreviousColorScheme() or RandomColorScheme(). \r\n\r\n Or if you don't like current color scheme you can call\r\n RemoveCurrentColorScheme() to remove the file.\r\n\r\n There are 4 main functions \r\n   1. You can either call them directly\r\n      :call NextColorScheme()\r\n      :call PreviousColorScheme() \r\n      :call RandomColorScheme()\r\n      :call RemoveCurrentColorScheme()\r\n\r\n   2. You can map and save them in your [._]gvimrc.\r\n      map <F4>   :call NextColorScheme()<CR>\r\n      map <S-F4> :call PreviousColorScheme()<CR>\r\n      map <C-F4> :call RandomColorScheme()<CR>\r\n      map <F3>   :call RemoveCurrentColorScheme()<CR>\r\n\r\n   3. You can also start each vim session with random color scheme by \r\n      adding following line in your [._]gvimrc\r\n      call RandomColorScheme()\r\n\r\n Tip: \r\n You can change your rulerformat in your [._]vimrc to display the name of \r\n current color scheme on status line.\r\n\r\n First, add this line to display status information \r\n     set ruler \r\n\r\n And add %{g:colors_name} in rulerformat to display name of current color \r\n  scheme. For example,\r\n     set rulerformat=%55(:%{g:colors_name}:\\ %5l,%-6(%c%V%)\\ %P%) \r\n\r\n However, you will see an error message if you didn't load color scheme at\r\n startup. So you might want to add %{GetColorSyntaxName()} instead.\r\n     set rulerformat=%55(:%{GetColorSyntaxName()}:\\ %5l,%-6(%c%V%)\\ %P%) \r\n\r\n GetColorSyntaxName() function is included in this script. It returns\r\n the value of g:colors_name if it exists, otherwise an empty string. If you\r\n are using a console version, then you might have to copy\r\n GetColorSyntaxName() into .vimrc, because I think the plugin files get\r\n loaded after evaluating .vimrc.\r\n","4":" Got ideas from following tips and scripts \r\n vimtip #341, vimtip #358, vimscript #668, vimscript #109 \r\n\r\n Usage:\r\n When this script is loaded, it will populate an array with each of color \r\n scheme's file path.  You can then load different color schemes using \r\n NextColorScheme(), PreviousColorScheme() or RandomColorScheme(). \r\n\r\n Or if you don't like current color scheme you can call\r\n RemoveCurrentColorScheme() to remove the file.\r\n\r\n There are 4 main functions \r\n   1. You can either call them directly\r\n      :call NextColorScheme()\r\n      :call PreviousColorScheme() \r\n      :call RandomColorScheme()\r\n      :call RemoveCurrentColorScheme()\r\n\r\n   2. You can map and save them in your [._]gvimrc.\r\n      map <F4>   :call NextColorScheme()<CR>\r\n      map <S-F4> :call PreviousColorScheme()<CR>\r\n      map <C-F4> :call RandomColorScheme()<CR>\r\n      map <F3>   :call RemoveCurrentColorScheme()<CR>\r\n\r\n   3. You can also start each vim session with random color scheme by \r\n      adding following line in your [._]gvimrc\r\n      call RandomColorScheme()\r\n\r\n Tip: \r\n You can change your rulerformat in your [._]vimrc to display the name of \r\n current color scheme on status line.\r\n\r\n First, add this line to display status information \r\n     set ruler \r\n\r\n And add %{g:colors_name} in rulerformat to display name of current color \r\n  scheme. For example,\r\n     set rulerformat=%55(:%{g:colors_name}:\\ %5l,%-6(%c%V%)\\ %P%) \r\n\r\n However, you will see an error message if you didn't load color scheme at\r\n startup. So you might want to add %{GetColorSyntaxName()} instead.\r\n     set rulerformat=%55(:%{GetColorSyntaxName()}:\\ %5l,%-6(%c%V%)\\ %P%) \r\n\r\n GetColorSyntaxName() function is included in this script. It returns\r\n the value of g:colors_name if it exists, otherwise an empty string. If you\r\n are using a console version, then you might have to copy\r\n GetColorSyntaxName() into .vimrc, because I think the plugin files get\r\n loaded after evaluating .vimrc.\r\n","install_details":"Copy changeColorScheme.vim in your plugin directory","5":"Copy changeColorScheme.vim in your plugin directory","first_name":"Hosup","6":"Hosup","last_name":"Chung","7":"Chung","releases":[{"0":"870","vim_version":"6.0","1":"6.0","script_version":"0.4","2":"0.4","version_comment":"added RemoveCurrentColorScheme() function (requested by auto didakto). If you don't like current color scheme, you can call RemoveCurrentColorScheme() to delete the color scheme file.","3":"added RemoveCurrentColorScheme() function (requested by auto didakto). If you don't like current color scheme, you can call RemoveCurrentColorScheme() to delete the color scheme file.","package":"changeColorScheme.vim","4":"changeColorScheme.vim","src_id":"13396","5":"13396","creation_date":"1279912140","6":"1279912140"},{"0":"870","vim_version":"6.0","1":"6.0","script_version":"0.3","2":"0.3","version_comment":"updated code to handle file not found error due to color schemes were removed","3":"updated code to handle file not found error due to color schemes were removed","package":"changeColorScheme.vim","4":"changeColorScheme.vim","src_id":"5463","5":"5463","creation_date":"1142832848","6":"1142832848"},{"0":"870","vim_version":"6.0","1":"6.0","script_version":"0.2","2":"0.2","version_comment":"Updated RandomColorScheme()","3":"Updated RandomColorScheme()","package":"changeColorScheme.vim","4":"changeColorScheme.vim","src_id":"5055","5":"5055","creation_date":"1138988452","6":"1138988452"},{"0":"870","vim_version":"6.0","1":"6.0","script_version":"0.12","2":"0.12","version_comment":"I finally tested this plugin on OS X and Linux\r\nWhen searching color schemes, substituting eol didn't work on Linux.\r\nI'm using \"\\n\" instead of '\\n' now, and it seems working.","3":"I finally tested this plugin on OS X and Linux\r\nWhen searching color schemes, substituting eol didn't work on Linux.\r\nI'm using \"\\n\" instead of '\\n' now, and it seems working.","package":"changeColorScheme.vim","4":"changeColorScheme.vim","src_id":"3344","5":"3344","creation_date":"1092746440","6":"1092746440"}]},"869":{"script_id":"869","0":"869","script_name":"changesqlcase.vim","1":"changesqlcase.vim","script_type":"utility","2":"utility","summary":"Upper case sql keywords from a visual mode selection.","3":"Upper case sql keywords from a visual mode selection.","description":"Description:\r\nThis plugin is a function that wraps around a big substitution expression.\r\nThe goal is to be able up upper case sql keywords from a visual selection.\r\nIt is quite similar to this script:\r\n\r\nhttp:\/\/www.vim.org\/scripts\/script.php?script_id=305\r\n\r\nwhich uses insert mode abbreviations to capitalize as you type.  My script\r\nwill be useful if you need to clean up existing scripts or if you are\r\nprogramming in another language and want to format sql inside of a string\r\nvariable.  \r\n\r\nThe sql keyword list is taken from the postgresql 7.4 docs:\r\n\r\nhttp:\/\/www.postgresql.org\/docs\/current\/static\/sql-keywords-appendix.html#KEYWORDS-TABLE\r\n\r\nPlease send a patch to include keywords specific to the database you are\r\nworking with.\r\n\r\nInstallation:\r\n\r\nPlace this script in your ~\/.vim\/plugin\/ directory or source from your vimrc\r\nfile. To use the script create a visual map:\r\n\r\nvmap <leader>uc  :call ChangeSqlCase()<cr>\r\n\r\nCustomization:\r\n1. Add the confirmation flag to the substitution if you are mostly doing\r\nsingle lines.  If you turn on confirmation on a multi-line visual selection\r\nyou will need to cancel out of the confirmation for each line.\r\n2. delete any keywords that cause you grief.\r\n3. add any keywords that are missing for your database\r\n\r\nTodo:\r\n1. This script could be modified to accept a database variable that altered\r\nthe keyword list.\r\n2. lowercase as well as uppercase\r\n\r\nBugs:\r\n\r\nAs noted in the vim manual |10.3|:\r\n\r\n   When using Visual mode to select part of a line, or using CTRL-V to\r\n  select a block of text, the colon commands will still apply to whole\r\n  lines.  This might change in a future version of Vim.\r\n\r\nSo if you select just the string in side of the quotes in the following\r\nexample:\r\n\r\ntest=\"select * from example\" { dont update me }\r\n\r\nthe word 'update' after the end quote will also change case.  \r\n","4":"Description:\r\nThis plugin is a function that wraps around a big substitution expression.\r\nThe goal is to be able up upper case sql keywords from a visual selection.\r\nIt is quite similar to this script:\r\n\r\nhttp:\/\/www.vim.org\/scripts\/script.php?script_id=305\r\n\r\nwhich uses insert mode abbreviations to capitalize as you type.  My script\r\nwill be useful if you need to clean up existing scripts or if you are\r\nprogramming in another language and want to format sql inside of a string\r\nvariable.  \r\n\r\nThe sql keyword list is taken from the postgresql 7.4 docs:\r\n\r\nhttp:\/\/www.postgresql.org\/docs\/current\/static\/sql-keywords-appendix.html#KEYWORDS-TABLE\r\n\r\nPlease send a patch to include keywords specific to the database you are\r\nworking with.\r\n\r\nInstallation:\r\n\r\nPlace this script in your ~\/.vim\/plugin\/ directory or source from your vimrc\r\nfile. To use the script create a visual map:\r\n\r\nvmap <leader>uc  :call ChangeSqlCase()<cr>\r\n\r\nCustomization:\r\n1. Add the confirmation flag to the substitution if you are mostly doing\r\nsingle lines.  If you turn on confirmation on a multi-line visual selection\r\nyou will need to cancel out of the confirmation for each line.\r\n2. delete any keywords that cause you grief.\r\n3. add any keywords that are missing for your database\r\n\r\nTodo:\r\n1. This script could be modified to accept a database variable that altered\r\nthe keyword list.\r\n2. lowercase as well as uppercase\r\n\r\nBugs:\r\n\r\nAs noted in the vim manual |10.3|:\r\n\r\n   When using Visual mode to select part of a line, or using CTRL-V to\r\n  select a block of text, the colon commands will still apply to whole\r\n  lines.  This might change in a future version of Vim.\r\n\r\nSo if you select just the string in side of the quotes in the following\r\nexample:\r\n\r\ntest=\"select * from example\" { dont update me }\r\n\r\nthe word 'update' after the end quote will also change case.  \r\n","install_details":"","5":"","first_name":"culley","6":"culley","last_name":"harrelson","7":"harrelson","releases":[{"0":"869","vim_version":"6.0","1":"6.0","script_version":"0.1.2","2":"0.1.2","version_comment":"removed confirmation flag-- it was causing too many problems for multi-line selections","3":"removed confirmation flag-- it was causing too many problems for multi-line selections","package":"changesqlcase.vim","4":"changesqlcase.vim","src_id":"2642","5":"2642","creation_date":"1072877600","6":"1072877600"},{"0":"869","vim_version":"6.0","1":"6.0","script_version":"0.1.1","2":"0.1.1","version_comment":"set confirmation flag as the default behavior","3":"set confirmation flag as the default behavior","package":"changesqlcase.vim","4":"changesqlcase.vim","src_id":"2640","5":"2640","creation_date":"1072868809","6":"1072868809"},{"0":"869","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"changesqlcase.vim","4":"changesqlcase.vim","src_id":"2638","5":"2638","creation_date":"1072855211","6":"1072855211"}]},"868":{"script_id":"868","0":"868","script_name":"Redundant phonetic\/visual Hebrew keyboar","1":"Redundant phonetic\/visual Hebrew keyboar","script_type":"utility","2":"utility","summary":"Phonetic\/visual keyboard map for hebrew ISO-8859-8 chars","3":"Phonetic\/visual keyboard map for hebrew ISO-8859-8 chars","description":"Phonetic\/visual hebrew keyboard map, redundancy in that for example all 'o' 'u' and 'v' are mapped to hebrew 'vaf', and so on.","4":"Phonetic\/visual hebrew keyboard map, redundancy in that for example all 'o' 'u' and 'v' are mapped to hebrew 'vaf', and so on.","install_details":"better\r\n:set noallowrevins\r\nsince we fake that in the script, then\r\n:so <script.vim>","5":"better\r\n:set noallowrevins\r\nsince we fake that in the script, then\r\n:so <script.vim>","first_name":"Oyd E","6":"Oyd E","last_name":"Leven","7":"Leven","releases":[{"0":"868","vim_version":"5.7","1":"5.7","script_version":"0.01","2":"0.01","version_comment":"Initial upload","3":"Initial upload","package":"heb.phon2.vim","4":"heb.phon2.vim","src_id":"2632","5":"2632","creation_date":"1072457033","6":"1072457033"}]},"867":{"script_id":"867","0":"867","script_name":"phonetic\/visual hebrew keyboard mapphone","1":"phonetic\/visual hebrew keyboard mapphone","script_type":"utility","2":"utility","summary":"phonetic\/visual alternative hebrew keyboard map, ISO-8859-8 chars","3":"phonetic\/visual alternative hebrew keyboard map, ISO-8859-8 chars","description":"A phonetic\/visual Hebrew alphabet keyboard map, for entering to ISO-8859-8 hebrew chars.\r\nDifferent than the 'internal' map.\r\n\r\nThe usage of 'reversed-insert' mode is configurable.","4":"A phonetic\/visual Hebrew alphabet keyboard map, for entering to ISO-8859-8 hebrew chars.\r\nDifferent than the 'internal' map.\r\n\r\nThe usage of 'reversed-insert' mode is configurable.","install_details":"better\r\n:set noallowrevins\r\nsince we fake that in the script, then\r\n:so <script.vim>","5":"better\r\n:set noallowrevins\r\nsince we fake that in the script, then\r\n:so <script.vim>","first_name":"Oyd E","6":"Oyd E","last_name":"Leven","7":"Leven","releases":[{"0":"867","vim_version":"5.7","1":"5.7","script_version":"0.01","2":"0.01","version_comment":"Initial upload","3":"Initial upload","package":"heb.phon1.vim","4":"heb.phon1.vim","src_id":"2631","5":"2631","creation_date":"1072456802","6":"1072456802"}]},"866":{"script_id":"866","0":"866","script_name":"Israelli hebrew shifted","1":"Israelli hebrew shifted","script_type":"utility","2":"utility","summary":"An alternative Hebrew keyboard map, for ISO-8859-8 usage.","3":"An alternative Hebrew keyboard map, for ISO-8859-8 usage.","description":"A Hebrew alphabet keyboard map, according to the standart Israelli keyboard layout, on a US-ASCII keyboard, to ISO-8859-8 hebrew chars.Instade of using punctuation keys for ending(finial) letters, we use shifted keys, rendering three obvious advatages.\r\nAlso, the usage of 'reversed-insert' mode is configurable.","4":"A Hebrew alphabet keyboard map, according to the standart Israelli keyboard layout, on a US-ASCII keyboard, to ISO-8859-8 hebrew chars.Instade of using punctuation keys for ending(finial) letters, we use shifted keys, rendering three obvious advatages.\r\nAlso, the usage of 'reversed-insert' mode is configurable.","install_details":"better\r\n:set noallowrevins\r\nsince we fake that in the script, then\r\n:so <script.vim>","5":"better\r\n:set noallowrevins\r\nsince we fake that in the script, then\r\n:so <script.vim>","first_name":"Oyd E","6":"Oyd E","last_name":"Leven","7":"Leven","releases":[{"0":"866","vim_version":"5.7","1":"5.7","script_version":"0.01","2":"0.01","version_comment":"Initial upload","3":"Initial upload","package":"heb.il.shift.vim","4":"heb.il.shift.vim","src_id":"2630","5":"2630","creation_date":"1072456527","6":"1072456527"}]},"865":{"script_id":"865","0":"865","script_name":"unmswin.vim","1":"unmswin.vim","script_type":"utility","2":"utility","summary":"Undo the action of mswin.vim","3":"Undo the action of mswin.vim","description":"This undoes the actions of the mswin.vim described under :help :behave. It restores the changed options (except guioptions) to their default (which was not necessarily what they were set to before invoking mswin, but that can't be helped) and undoes the mappings (except Ctrl-Q and Alt-Space, which are not deemed harmful).","4":"This undoes the actions of the mswin.vim described under :help :behave. It restores the changed options (except guioptions) to their default (which was not necessarily what they were set to before invoking mswin, but that can't be helped) and undoes the mappings (except Ctrl-Q and Alt-Space, which are not deemed harmful).","install_details":"just drop the file in ~\/.vim\/macros (on Unix), or in ~\/vimfiles\/macros (on Windows, if $HOME exists -- in Dos\/Windows parlance, that would be %HOME%\\vimfiles\\macros), or in $VIM\/vimfiles\/macros (for system-wide availability on any platform).\r\n\r\nInvoke it by doing :runtime macros\/unmswin.vim","5":"just drop the file in ~\/.vim\/macros (on Unix), or in ~\/vimfiles\/macros (on Windows, if $HOME exists -- in Dos\/Windows parlance, that would be %HOME%\\vimfiles\\macros), or in $VIM\/vimfiles\/macros (for system-wide availability on any platform).\r\n\r\nInvoke it by doing :runtime macros\/unmswin.vim","first_name":"Antoine","6":"Antoine","last_name":"Mechelynck","7":"Mechelynck","releases":[{"0":"865","vim_version":"6.0","1":"6.0","script_version":"0.1 BETA","2":"0.1 BETA","version_comment":"Initial upload","3":"Initial upload","package":"unmswin.vim","4":"unmswin.vim","src_id":"2627","5":"2627","creation_date":"1072348981","6":"1072348981"}]},"864":{"script_id":"864","0":"864","script_name":"visual_studio.vim","1":"visual_studio.vim","script_type":"utility","2":"utility","summary":"Vim and Microsoft Visual Studio .NET integration","3":"Vim and Microsoft Visual Studio .NET integration","description":"\r\nNEW IN VERSION 1.2\r\n\r\n* Switch between multiple instance of Visual Studio\r\n* Build projects and access project file heirarchy directly from Vim\r\n* Support for Visual Studio 2003, 2005 and 2008\r\n\r\nThanks to Henrik \u00c3\u0096hman for contributions to this version.\r\n\r\nSee the visual_studio.vim help page for more information:\r\n  http:\/\/www.plan10.com\/vim\/visual-studio\/doc\/1.2\r\n","4":"\r\nNEW IN VERSION 1.2\r\n\r\n* Switch between multiple instance of Visual Studio\r\n* Build projects and access project file heirarchy directly from Vim\r\n* Support for Visual Studio 2003, 2005 and 2008\r\n\r\nThanks to Henrik \u00c3\u0096hman for contributions to this version.\r\n\r\nSee the visual_studio.vim help page for more information:\r\n  http:\/\/www.plan10.com\/vim\/visual-studio\/doc\/1.2\r\n","install_details":"\r\nRequirements\r\n\r\n* Vim 7.0 or above\r\n* Python 2.4.  Please install the version of python that vim was built with. For vim 7.0 this is python 2.4.\r\n  http:\/\/www.python.org\/download\/releases\/2.4.4\r\n* Python for Windows extensions.  Please install the version specific the the Python release.\r\n  http:\/\/sourceforge.net\/project\/showfiles.php?group_id=78018\r\n\r\nInstallation instructions\r\n\r\n* Download the file visual_studio.zip. This contains the files visual_studio.vim and visual_studio.py.\r\n* Unpack the files into your plugin directory, for example: $VIM\\vimfiles\\plugin.\r\n","5":"\r\nRequirements\r\n\r\n* Vim 7.0 or above\r\n* Python 2.4.  Please install the version of python that vim was built with. For vim 7.0 this is python 2.4.\r\n  http:\/\/www.python.org\/download\/releases\/2.4.4\r\n* Python for Windows extensions.  Please install the version specific the the Python release.\r\n  http:\/\/sourceforge.net\/project\/showfiles.php?group_id=78018\r\n\r\nInstallation instructions\r\n\r\n* Download the file visual_studio.zip. This contains the files visual_studio.vim and visual_studio.py.\r\n* Unpack the files into your plugin directory, for example: $VIM\\vimfiles\\plugin.\r\n","first_name":"Michael","6":"Michael","last_name":"Graz","7":"Graz","releases":[{"0":"864","vim_version":"7.0","1":"7.0","script_version":"1.2","2":"1.2","version_comment":"Support for more VS versions, multiple VS solutions, VS projects and VS project files.\r\n","3":"Support for more VS versions, multiple VS solutions, VS projects and VS project files.\r\n","package":"visual_studio.zip","4":"visual_studio.zip","src_id":"7729","5":"7729","creation_date":"1191023799","6":"1191023799"},{"0":"864","vim_version":"6.0","1":"6.0","script_version":"1.1","2":"1.1","version_comment":"Support for building, compiling, viewing output window and other enhancements.","3":"Support for building, compiling, viewing output window and other enhancements.","package":"visual_studio.zip","4":"visual_studio.zip","src_id":"2989","5":"2989","creation_date":"1083440785","6":"1083440785"},{"0":"864","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"visual_studio.zip","4":"visual_studio.zip","src_id":"2626","5":"2626","creation_date":"1072221608","6":"1072221608"}]},"863":{"script_id":"863","0":"863","script_name":"BlackBeauty","1":"BlackBeauty","script_type":"color scheme","2":"color scheme","summary":"A beautiful (if you like dark background) color scheme with dark background","3":"A beautiful (if you like dark background) color scheme with dark background","description":"This is the color scheme i generally use. Being dark background, its easy to eyes. Just put this in $HOME\/.vim\/colors directory in UNIX. I never use windows, hence i dont know where to put this in windows. But it should be at the appropriate location where you put all the color schemes.","4":"This is the color scheme i generally use. Being dark background, its easy to eyes. Just put this in $HOME\/.vim\/colors directory in UNIX. I never use windows, hence i dont know where to put this in windows. But it should be at the appropriate location where you put all the color schemes.","install_details":"","5":"","first_name":"Surya Kiran","6":"Surya Kiran","last_name":"Gullapalli","7":"Gullapalli","releases":[{"0":"863","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"blackbeauty.vim","4":"blackbeauty.vim","src_id":"2623","5":"2623","creation_date":"1072127247","6":"1072127247"}]},"862":{"script_id":"862","0":"862","script_name":"cscope quickfix","1":"cscope quickfix","script_type":"utility","2":"utility","summary":"enables to use cscope with quickfix.","3":"enables to use cscope with quickfix.","description":"Overview\r\n-------------\r\nThis script enables to use cscope with quickfix.\r\n\r\nPreparation\r\n-----------------\r\nYou must prepare cscope and cscope database (cscope.out file).\r\ncscope is a tag tool like ctags, but unlike ctags, it is a cross referencing tool.\r\nIf you don't know about cscope see:\r\n:help cscope\r\nhttp:\/\/cscope.sourceforge.net\/\r\nhttp:\/\/iamphet.nm.ru\/cscope\/ (Win32)\r\n\r\nFeature 1\r\n--------------\r\nThis script adds a command \":Cscope\", which is very similar to \":cscope find\" command. But, this \":Cscope\" command can be used with quickfix, and isn't needed cscope connection. So, you don't have to install vim with --enable-cscope.\r\n\r\nFeature 2\r\n--------------\r\nThis script adds keymap macro as follows:\r\n<C-\\> s: Find this C symbol\r\n<C-\\> g: Find this definition\r\n<C-\\> d: Find functions called by this function\r\n<C-\\> c: Find functions calling this function\r\n<C-\\> t: Find this text string\r\n<C-\\> e: Find this egrep pattern\r\n<C-\\> f: Find this file\r\n<C-\\> i: Find files #including this file\r\n\"this\" means <cword> or <cfile> on the cursor.\r\n\r\nFeature 3\r\n--------------\r\nThis script adds Tools and Popup menu as follows:\r\n\"Symbols\": Find this C symbol\r\n\"Defines\": Find this definition\r\n\"Calls\": Find functions called by this function\r\n\"Globals\": Find functions calling this function\r\n\"Texts\": Find this text string\r\n\"Egrep\": Find this egrep pattern\r\n\"File\": Find this file\r\n\"Includes\": Find files #including this file\r\n\"Update cscope.out\"\r\n\r\nFunction\r\n--------------\r\nRunCscope({type}, {pattern} [,{file}])\r\n\r\nCommand\r\n---------------\r\nCscope {type} {pattern} [{file}]\r\n\r\nVariables\r\n--------------\r\n0: disable, 1: enable\r\ng:Cscope_OpenQuickfixWindow (default: 1)\r\ng:Cscope_JumpError (default: 1)\r\ng:Cscope_Keymap (default: 1)\r\ng:Cscope_PopupMenu (default: 0)\r\ng:Cscope_ToolMenu (default: 1)","4":"Overview\r\n-------------\r\nThis script enables to use cscope with quickfix.\r\n\r\nPreparation\r\n-----------------\r\nYou must prepare cscope and cscope database (cscope.out file).\r\ncscope is a tag tool like ctags, but unlike ctags, it is a cross referencing tool.\r\nIf you don't know about cscope see:\r\n:help cscope\r\nhttp:\/\/cscope.sourceforge.net\/\r\nhttp:\/\/iamphet.nm.ru\/cscope\/ (Win32)\r\n\r\nFeature 1\r\n--------------\r\nThis script adds a command \":Cscope\", which is very similar to \":cscope find\" command. But, this \":Cscope\" command can be used with quickfix, and isn't needed cscope connection. So, you don't have to install vim with --enable-cscope.\r\n\r\nFeature 2\r\n--------------\r\nThis script adds keymap macro as follows:\r\n<C-\\> s: Find this C symbol\r\n<C-\\> g: Find this definition\r\n<C-\\> d: Find functions called by this function\r\n<C-\\> c: Find functions calling this function\r\n<C-\\> t: Find this text string\r\n<C-\\> e: Find this egrep pattern\r\n<C-\\> f: Find this file\r\n<C-\\> i: Find files #including this file\r\n\"this\" means <cword> or <cfile> on the cursor.\r\n\r\nFeature 3\r\n--------------\r\nThis script adds Tools and Popup menu as follows:\r\n\"Symbols\": Find this C symbol\r\n\"Defines\": Find this definition\r\n\"Calls\": Find functions called by this function\r\n\"Globals\": Find functions calling this function\r\n\"Texts\": Find this text string\r\n\"Egrep\": Find this egrep pattern\r\n\"File\": Find this file\r\n\"Includes\": Find files #including this file\r\n\"Update cscope.out\"\r\n\r\nFunction\r\n--------------\r\nRunCscope({type}, {pattern} [,{file}])\r\n\r\nCommand\r\n---------------\r\nCscope {type} {pattern} [{file}]\r\n\r\nVariables\r\n--------------\r\n0: disable, 1: enable\r\ng:Cscope_OpenQuickfixWindow (default: 1)\r\ng:Cscope_JumpError (default: 1)\r\ng:Cscope_Keymap (default: 1)\r\ng:Cscope_PopupMenu (default: 0)\r\ng:Cscope_ToolMenu (default: 1)","install_details":"Copy cscope_quickfix.vim file to plugin directory.\r\nIf you don't want to open quickfix window after :Cscope command, put a line in .vimrc like:\r\nlet Cscope_OpenQuickfixWindow = 0\r\nIf you don't want to jump first item after :Cscope command, put a line in .vimrc like:\r\nlet Cscope_JumpError = 0\r\nIf you want to use Popup menu for :Cscope command, put a line in .vimrc like: \r\nlet Cscope_PopupMenu = 1\r\nIf you don't want to use Tools menu for :Cscope command, put a line in .vimrc like: \r\nlet Cscope_ToolsMenu = 0","5":"Copy cscope_quickfix.vim file to plugin directory.\r\nIf you don't want to open quickfix window after :Cscope command, put a line in .vimrc like:\r\nlet Cscope_OpenQuickfixWindow = 0\r\nIf you don't want to jump first item after :Cscope command, put a line in .vimrc like:\r\nlet Cscope_JumpError = 0\r\nIf you want to use Popup menu for :Cscope command, put a line in .vimrc like: \r\nlet Cscope_PopupMenu = 1\r\nIf you don't want to use Tools menu for :Cscope command, put a line in .vimrc like: \r\nlet Cscope_ToolsMenu = 0","first_name":"k","6":"k","last_name":"kino","7":"kino","releases":[{"0":"862","vim_version":"6.0","1":"6.0","script_version":"0.2","2":"0.2","version_comment":"Add menus.\r\nEnables to be back to the place before jumping with :crew.\r\n","3":"Add menus.\r\nEnables to be back to the place before jumping with :crew.\r\n","package":"cscope_quickfix.vim","4":"cscope_quickfix.vim","src_id":"2635","5":"2635","creation_date":"1072682931","6":"1072682931"},{"0":"862","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"cscope_quickfix.vim","4":"cscope_quickfix.vim","src_id":"2621","5":"2621","creation_date":"1071997305","6":"1071997305"}]},"861":{"script_id":"861","0":"861","script_name":"Viki\/Deplate","1":"Viki\/Deplate","script_type":"utility","2":"utility","summary":"A personal wiki for Vim","3":"A personal wiki for Vim","description":"VIKI Forum (questions, feature requests): http:\/\/sourceforge.net\/projects\/deplate\/forums\/forum\/700962\r\nBug tracker: https:\/\/github.com\/tomtom\/viki_vim\/issues\r\nMarkup: http:\/\/deplate.sourceforge.net\/Markup.html (http:\/\/deplate.sourceforge.net\/markup.txt)\r\nDemo: http:\/\/vimsomnia.blogspot.com\/2010\/11\/vikitasks-viki-demonstration-personal.html\r\n\r\nQUICKSTART\r\nThis plugin adds wiki-like hypertext capabilities to Vim. You can use viki as a \"minor\" mode (i.e., as an add-on to any other mode) or as a full-fledged wiki mode. There is also an add-on plugin for \"wikifying\" latex documents by turning some latex commands into wiki names. If viki is properly configured, activating a reference to an image, a webpage etc. will view that resource in an external viewer.\r\n\r\nFrom http:\/\/sourceforge.net\/projects\/deplate\/ you can download a ruby based tool to convert viki markup to html, latex, or docbook. On its homepage (http:\/\/deplate.sf.net) you can read a more detailled specification of the markup.\r\n\r\n\r\nMINOR WIKI MODE:\r\nUse the hypertext facility with any filetype. Just type :VikiMinorMode and all wiki names and URLs will be highlighted.\r\n\r\n\r\nFULL WIKI MODE:\r\nIn full mode, viki becomes a personal wiki (http:\/\/c2.com\/cgi\/wiki?PersonalWiki). The full wiki mode included syntax highlighting (for headings, lists, tables, textstyles etc.), folding support, and additional key bindings (i.e., you can press <c-tab> or <s-c-tab> to move the cursor to the next\/previous viki name). By default, the viki filetype is enabled for all files with a .viki suffix. The viki markup is explained at http:\/\/deplate.sourceforge.net\/Markup.html (http:\/\/deplate.sourceforge.net\/markup.txt)\r\n\r\n\r\nWIKIS:\r\nIn case you missed out on wikis, a wiki is a simple way of creating hypertexts. In its very basic form creating a hyperlink is as easy as writing a word in CamelCase or by enclosing a word in brackets--as in [[destination]] or [-destination-]. A wiki is a simple tool to organize ideas, notes etc. See http:\/\/en.wikipedia.org\/wiki\/Wiki for details.\r\n\r\n\r\nRELATED PLUGIN:\r\n- vikitasks (vimscript #2894): Distributed TODO lists\r\n- hookcursormoved (vimscript #2037): Enhanced detection of hyperlinks to inexistent destinations.\r\n- vxfold (vimscript #3004) by Marko Mahnič: Provides org-mode like fold cycling\r\n- VOoM (vimscript #2657): A two-pane outliner with support for viki\r\n\r\n\r\nAlso available via git\r\nhttp:\/\/github.com\/tomtom\/viki_vim","4":"VIKI Forum (questions, feature requests): http:\/\/sourceforge.net\/projects\/deplate\/forums\/forum\/700962\r\nBug tracker: https:\/\/github.com\/tomtom\/viki_vim\/issues\r\nMarkup: http:\/\/deplate.sourceforge.net\/Markup.html (http:\/\/deplate.sourceforge.net\/markup.txt)\r\nDemo: http:\/\/vimsomnia.blogspot.com\/2010\/11\/vikitasks-viki-demonstration-personal.html\r\n\r\nQUICKSTART\r\nThis plugin adds wiki-like hypertext capabilities to Vim. You can use viki as a \"minor\" mode (i.e., as an add-on to any other mode) or as a full-fledged wiki mode. There is also an add-on plugin for \"wikifying\" latex documents by turning some latex commands into wiki names. If viki is properly configured, activating a reference to an image, a webpage etc. will view that resource in an external viewer.\r\n\r\nFrom http:\/\/sourceforge.net\/projects\/deplate\/ you can download a ruby based tool to convert viki markup to html, latex, or docbook. On its homepage (http:\/\/deplate.sf.net) you can read a more detailled specification of the markup.\r\n\r\n\r\nMINOR WIKI MODE:\r\nUse the hypertext facility with any filetype. Just type :VikiMinorMode and all wiki names and URLs will be highlighted.\r\n\r\n\r\nFULL WIKI MODE:\r\nIn full mode, viki becomes a personal wiki (http:\/\/c2.com\/cgi\/wiki?PersonalWiki). The full wiki mode included syntax highlighting (for headings, lists, tables, textstyles etc.), folding support, and additional key bindings (i.e., you can press <c-tab> or <s-c-tab> to move the cursor to the next\/previous viki name). By default, the viki filetype is enabled for all files with a .viki suffix. The viki markup is explained at http:\/\/deplate.sourceforge.net\/Markup.html (http:\/\/deplate.sourceforge.net\/markup.txt)\r\n\r\n\r\nWIKIS:\r\nIn case you missed out on wikis, a wiki is a simple way of creating hypertexts. In its very basic form creating a hyperlink is as easy as writing a word in CamelCase or by enclosing a word in brackets--as in [[destination]] or [-destination-]. A wiki is a simple tool to organize ideas, notes etc. See http:\/\/en.wikipedia.org\/wiki\/Wiki for details.\r\n\r\n\r\nRELATED PLUGIN:\r\n- vikitasks (vimscript #2894): Distributed TODO lists\r\n- hookcursormoved (vimscript #2037): Enhanced detection of hyperlinks to inexistent destinations.\r\n- vxfold (vimscript #3004) by Marko Mahnič: Provides org-mode like fold cycling\r\n- VOoM (vimscript #2657): A two-pane outliner with support for viki\r\n\r\n\r\nAlso available via git\r\nhttp:\/\/github.com\/tomtom\/viki_vim","install_details":"Open the vba file and type:\r\n\r\n    :so %\r\n\r\nSee :help vimball for details. Also, make sure to read |viki-customization|. If you have difficulties to install this plugin or if you use vim 7.0, please make sure to use the current version of vimball (vimscript #1502).\r\n\r\nRequirements:\r\n- tlib (vimscript #1863)\r\n\r\nOptional enhancements:\r\n- hookcursormoved (vimscript #2037): Enhanced detection of hyperlinks to inexistent destinations.\r\n\r\nThis plugin relies on the use of filetype plugins. Your .vimrc file should thus contain these lines:\r\n\r\n    set nocompatible\r\n    filetype plugin indent on\r\n    syntax on\r\n\r\nBy default, vim doesn't allow to |abandon| a modified buffer unless |hidden| is set. If get a \"cannot abandon buffer\"-message, please read the help on |g:vikiHide| and |abandon| to find out how to avoid this problem.\r\n\r\n\r\nThere is also a ruby-based tool for converting viki markup to html, latex, or docbook. Download deplate from the sourceforge project site: http:\/\/sourceforge.net\/projects\/deplate\/\r\n","5":"Open the vba file and type:\r\n\r\n    :so %\r\n\r\nSee :help vimball for details. Also, make sure to read |viki-customization|. If you have difficulties to install this plugin or if you use vim 7.0, please make sure to use the current version of vimball (vimscript #1502).\r\n\r\nRequirements:\r\n- tlib (vimscript #1863)\r\n\r\nOptional enhancements:\r\n- hookcursormoved (vimscript #2037): Enhanced detection of hyperlinks to inexistent destinations.\r\n\r\nThis plugin relies on the use of filetype plugins. Your .vimrc file should thus contain these lines:\r\n\r\n    set nocompatible\r\n    filetype plugin indent on\r\n    syntax on\r\n\r\nBy default, vim doesn't allow to |abandon| a modified buffer unless |hidden| is set. If get a \"cannot abandon buffer\"-message, please read the help on |g:vikiHide| and |abandon| to find out how to avoid this problem.\r\n\r\n\r\nThere is also a ruby-based tool for converting viki markup to html, latex, or docbook. Download deplate from the sourceforge project site: http:\/\/sourceforge.net\/projects\/deplate\/\r\n","first_name":"Tom","6":"Tom","last_name":"Link","7":"Link","releases":[{"0":"861","vim_version":"7.0","1":"7.0","script_version":"4.09","2":"4.09","version_comment":"- viki#fileword_suffixes: Also search for files with theses suffixes in |viki#CollectFileWords()|.\n- Don't use :HiLink\n- NEW :Vikifind command\n- Vikifind: add matches for file basename only\n- viki#Find(): When matching file names, allow use of [ _-] as whitespace; require trag >= 1.3\n- viki#GetInterVikiDef(): optional argument: include_files\n- VikiAnchor_rx(): use \"\\n\"\n- viki_viki#SetupBuffer(): Setup &path\n- remove _tplugin.vim\n- Improved viki#DirListing()\n- Moved g:vikiOpenFileWith_ANY related code to tlib_vim\n- Moved tinykeymap-related code to listitem_vim\n- Require tlib >= 1.15\n- Improve :Vikifind etc.\n- g:vikiOpenUrlWith_ANY: FIX xdg string\n- various minor changes\n- s\/TLibTrace\/Tlibtrace\/g\n- s:GetHead: disable iconv\n- viki#DirListing(): \"filter\" doesn't exclude dirs\n- FIX maps in \"major mode\"\n- Disable debug message\n- syntax\/*.vim: More conceal definitions\nMD5 checksum: 4921508fcf82aac578f7740d28ed151d","3":"- viki#fileword_suffixes: Also search for files with theses suffixes in |viki#CollectFileWords()|.\n- Don't use :HiLink\n- NEW :Vikifind command\n- Vikifind: add matches for file basename only\n- viki#Find(): When matching file names, allow use of [ _-] as whitespace; require trag >= 1.3\n- viki#GetInterVikiDef(): optional argument: include_files\n- VikiAnchor_rx(): use \"\\n\"\n- viki_viki#SetupBuffer(): Setup &path\n- remove _tplugin.vim\n- Improved viki#DirListing()\n- Moved g:vikiOpenFileWith_ANY related code to tlib_vim\n- Moved tinykeymap-related code to listitem_vim\n- Require tlib >= 1.15\n- Improve :Vikifind etc.\n- g:vikiOpenUrlWith_ANY: FIX xdg string\n- various minor changes\n- s\/TLibTrace\/Tlibtrace\/g\n- s:GetHead: disable iconv\n- viki#DirListing(): \"filter\" doesn't exclude dirs\n- FIX maps in \"major mode\"\n- Disable debug message\n- syntax\/*.vim: More conceal definitions\nMD5 checksum: 4921508fcf82aac578f7740d28ed151d","package":"viki.zip","4":"viki.zip","src_id":"23954","5":"23954","creation_date":"1453827938","6":"1453827938"},{"0":"861","vim_version":"7.0","1":"7.0","script_version":"4.08","2":"4.08","version_comment":"- Incoporate changes from pull request 12\n- viki#InterVikiDest(): Use g:vikiIndex (again)\n- viki#InterVikiDest: FIX check if i_index exists\n- viki_viki#CompleteExtendedNameDef(): Use match() instead of =~ (work-around)\n- iskeyword+=192-255\n- Allow digits in interviki names\n- FIX #13: viki_viki#SetupBuffer(): remove \"::\" from interviki names for use in interviki_rx\n- vikiBaseDirs: A list of directories where to look for \"file words\" and \"hyper words\"\n- CollectVikiWords(): Use correct directory for hypewords\n- Priority lists: Highlight #Y, #Z as comments (like #X)\n- viki#DirListing(): Improve display for \"**\/*.*\" pattern (requires proper rewrite)\n- FIX #14: Move definition of g:vikiFoldMethodVersion back to plugin\/viki.vim\n- syntax: g:vikiIndentedPriorityLists can also be window- or buffer-local\n- If the SetSyntax plugin is installed, set tw to 0 the cursor is over priority lists\n- syn cluster vikiPriorityListGen\nMD5 checksum: 059e1b085b663c1d2d498756fbba39f6","3":"- Incoporate changes from pull request 12\n- viki#InterVikiDest(): Use g:vikiIndex (again)\n- viki#InterVikiDest: FIX check if i_index exists\n- viki_viki#CompleteExtendedNameDef(): Use match() instead of =~ (work-around)\n- iskeyword+=192-255\n- Allow digits in interviki names\n- FIX #13: viki_viki#SetupBuffer(): remove \"::\" from interviki names for use in interviki_rx\n- vikiBaseDirs: A list of directories where to look for \"file words\" and \"hyper words\"\n- CollectVikiWords(): Use correct directory for hypewords\n- Priority lists: Highlight #Y, #Z as comments (like #X)\n- viki#DirListing(): Improve display for \"**\/*.*\" pattern (requires proper rewrite)\n- FIX #14: Move definition of g:vikiFoldMethodVersion back to plugin\/viki.vim\n- syntax: g:vikiIndentedPriorityLists can also be window- or buffer-local\n- If the SetSyntax plugin is installed, set tw to 0 the cursor is over priority lists\n- syn cluster vikiPriorityListGen\nMD5 checksum: 059e1b085b663c1d2d498756fbba39f6","package":"viki.zip","4":"viki.zip","src_id":"22597","5":"22597","creation_date":"1415036823","6":"1415036823"},{"0":"861","vim_version":"7.0","1":"7.0","script_version":"4.07","2":"4.07","version_comment":"- Incoporate changes from pull request 12\n- viki#InterVikiDest(): Use g:vikiIndex (again)\n- viki#InterVikiDest: FIX check if i_index exists\n- viki_viki#CompleteExtendedNameDef(): Use match() instead of =~ (work-around)\n- iskeyword+=192-255\nMD5 checksum: 64d81aebd79f239ea8be3a201e38cbef","3":"- Incoporate changes from pull request 12\n- viki#InterVikiDest(): Use g:vikiIndex (again)\n- viki#InterVikiDest: FIX check if i_index exists\n- viki_viki#CompleteExtendedNameDef(): Use match() instead of =~ (work-around)\n- iskeyword+=192-255\nMD5 checksum: 64d81aebd79f239ea8be3a201e38cbef","package":"viki.zip","4":"viki.zip","src_id":"21713","5":"21713","creation_date":"1396459111","6":"1396459111"},{"0":"861","vim_version":"7.0","1":"7.0","script_version":"4.06","2":"4.06","version_comment":"- Help template\n- FIX viki#DirListing(): correctly process file patterns\nMD5 checksum: 0bdb3097b73a9855892d60124d0d581f","3":"- Help template\n- FIX viki#DirListing(): correctly process file patterns\nMD5 checksum: 0bdb3097b73a9855892d60124d0d581f","package":"viki.zip","4":"viki.zip","src_id":"20937","5":"20937","creation_date":"1382283100","6":"1382283100"},{"0":"861","vim_version":"7.0","1":"7.0","script_version":"4.05","2":"4.05","version_comment":"- Files region: replace listing only if it has changed\n- Fix possible typo that breaks a default configuration on some systems - 'Please define g:vikiOpenUrlWith_http or g:vikiOpenUrlWith_ANY'\n- In region header: allow space after <<\n- Merge branch 'master' of https:\/\/github.com\/NickHu\/viki_vim\n- addon-info\n- tinykeymap: p, n: move to previous\/next list item\n- viki#GetIndent(): special handling of !!!|+++|???|### markers\n- viki#GetIndent(): Fixed indentation for marker list items (???, !!!, +++, ###)\n- Syntax: Accept tags (:word) and contacts (@name) anywhere in a priority list item\n- Add accdb & mdb to g:vikiSpecialFiles\n- g:viki#code_syntax (prepare for syntax highlighting in #Code regions)\n- Don't call viki#UpdateHeadings() on InsertLeave events\n- viki#UpdateHeadings(): Avoid superfluous checks\n- FIX: Highlighting of symbols within strings and similar syntax groups\n- viki#UpdateHeadings(): Restore the search register (@\/)\n- viki#OpenLink(): Use tlib#dir#NativeName() when opening directories\n- Require tlib 1.05\n- #Files: Files in the cd are inserted as [[basename.ext]!] not as [[basename.ext][basename.ext]!] when conceal is enabled\n- #Files: glob can refer to an interviki\n- #Files takes an optional \"format\" argument\n- viki#Files: slightly improved file tree display; cache isdirectory() info\n- NEW #Grep regions; <LL>vu and <LL>vU update #Files and #Grep regions; require tlib 1.06\n- #Files, #Grep regions: separate multiple patterns with \"|\"\n- Finally enable support for proper highlighting of #Code regions\n- Use xdg-open with &\n- g:viki#code_syntax: Always enable these filetypes for #Code; g:viki#code_syntax_map: map #Code syntax arg to vim filetypes\nMD5 checksum: 8b08d2dd760471dd912511da3ad62818","3":"- Files region: replace listing only if it has changed\n- Fix possible typo that breaks a default configuration on some systems - 'Please define g:vikiOpenUrlWith_http or g:vikiOpenUrlWith_ANY'\n- In region header: allow space after <<\n- Merge branch 'master' of https:\/\/github.com\/NickHu\/viki_vim\n- addon-info\n- tinykeymap: p, n: move to previous\/next list item\n- viki#GetIndent(): special handling of !!!|+++|???|### markers\n- viki#GetIndent(): Fixed indentation for marker list items (???, !!!, +++, ###)\n- Syntax: Accept tags (:word) and contacts (@name) anywhere in a priority list item\n- Add accdb & mdb to g:vikiSpecialFiles\n- g:viki#code_syntax (prepare for syntax highlighting in #Code regions)\n- Don't call viki#UpdateHeadings() on InsertLeave events\n- viki#UpdateHeadings(): Avoid superfluous checks\n- FIX: Highlighting of symbols within strings and similar syntax groups\n- viki#UpdateHeadings(): Restore the search register (@\/)\n- viki#OpenLink(): Use tlib#dir#NativeName() when opening directories\n- Require tlib 1.05\n- #Files: Files in the cd are inserted as [[basename.ext]!] not as [[basename.ext][basename.ext]!] when conceal is enabled\n- #Files: glob can refer to an interviki\n- #Files takes an optional \"format\" argument\n- viki#Files: slightly improved file tree display; cache isdirectory() info\n- NEW #Grep regions; <LL>vu and <LL>vU update #Files and #Grep regions; require tlib 1.06\n- #Files, #Grep regions: separate multiple patterns with \"|\"\n- Finally enable support for proper highlighting of #Code regions\n- Use xdg-open with &\n- g:viki#code_syntax: Always enable these filetypes for #Code; g:viki#code_syntax_map: map #Code syntax arg to vim filetypes\nMD5 checksum: 8b08d2dd760471dd912511da3ad62818","package":"viki.zip","4":"viki.zip","src_id":"20932","5":"20932","creation_date":"1382117844","6":"1382117844"},{"0":"861","vim_version":"7.0","1":"7.0","script_version":"4.04","2":"4.04","version_comment":"- #Files: error when the region started\/ended at last line\n- Support for tinykeymaps plugin (move list item)\n- Moved definitions of functions and global variables from ftplugin\/viki.vim to autoload\/viki.vim (fixes #5)\n- Moved listitem_move to autoload\/tinykeymap\/map\n- g:viki#cmd_no_fnameescape: Don't pre-process arguments for some file-viewer commands\n- vikiPriorityLists syntax: Make date more explicit; allow dates in tags\n- tinykeymap: listitem_move: Highlight the current line\n- #Files: improved display of file properties; sort argument\nMD5 checksum: e90c38e13fd9dc00edab65879dde2967","3":"- #Files: error when the region started\/ended at last line\n- Support for tinykeymaps plugin (move list item)\n- Moved definitions of functions and global variables from ftplugin\/viki.vim to autoload\/viki.vim (fixes #5)\n- Moved listitem_move to autoload\/tinykeymap\/map\n- g:viki#cmd_no_fnameescape: Don't pre-process arguments for some file-viewer commands\n- vikiPriorityLists syntax: Make date more explicit; allow dates in tags\n- tinykeymap: listitem_move: Highlight the current line\n- #Files: improved display of file properties; sort argument\nMD5 checksum: e90c38e13fd9dc00edab65879dde2967","package":"viki.zip","4":"viki.zip","src_id":"18706","5":"18706","creation_date":"1348830826","6":"1348830826"},{"0":"861","vim_version":"7.0","1":"7.0","script_version":"4.03","2":"4.03","version_comment":"- #Files: Error when glob pattern started with [*?]\n- #Files head: call iconv() if encodings differ\nMD5 checksum: 44dbf4bf6d6a985e3b140781636f8fdc","3":"- #Files: Error when glob pattern started with [*?]\n- #Files head: call iconv() if encodings differ\nMD5 checksum: 44dbf4bf6d6a985e3b140781636f8fdc","package":"viki.zip","4":"viki.zip","src_id":"18500","5":"18500","creation_date":"1346086704","6":"1346086704"},{"0":"861","vim_version":"7.0","1":"7.0","script_version":"4.02","2":"4.02","version_comment":"- Define a viki#MinorMode(...) function again.\n- Start a new fold at each heading (fixes #5)\n- Add g:vikiNameSuffix to g:ft_ignore_pat (fixes #8)\n- Conceal markup of extended links with names (fixes #7)\n- Hide markup of extended links & use cchar (fixes #7)\n- Improved #Files region: highligh as extended links; emulate tree\n- Conceal extended links markup: allow modifiers\n- If has('conceal') and extended markup is concealed #Files regions display only the filenames tail\n- #Files: modfied display of deep file listings\n- #Files: Make sure pattern is evaluated with respect to the buffer's directory\n- #Files: Error when region begins on last line\nMD5 checksum: 44dbf4bf6d6a985e3b140781636f8fdc","3":"- Define a viki#MinorMode(...) function again.\n- Start a new fold at each heading (fixes #5)\n- Add g:vikiNameSuffix to g:ft_ignore_pat (fixes #8)\n- Conceal markup of extended links with names (fixes #7)\n- Hide markup of extended links & use cchar (fixes #7)\n- Improved #Files region: highligh as extended links; emulate tree\n- Conceal extended links markup: allow modifiers\n- If has('conceal') and extended markup is concealed #Files regions display only the filenames tail\n- #Files: modfied display of deep file listings\n- #Files: Make sure pattern is evaluated with respect to the buffer's directory\n- #Files: Error when region begins on last line\nMD5 checksum: 44dbf4bf6d6a985e3b140781636f8fdc","package":"viki.zip","4":"viki.zip","src_id":"18487","5":"18487","creation_date":"1345871883","6":"1345871883"},{"0":"861","vim_version":"7.0","1":"7.0","script_version":"4.01","2":"4.01","version_comment":"- Escape special character when loading \"autoload\/viki\/enc_{&enc}.vim\"\n- Support for xdg\n- Register 3gp as special file\n- viki#SetAnchorMarks(): Hide errors\n- :EditWrapper(): Fix slashes on windows\n- g:vikiIndentedPriorityLists: if 0, allow priority lists not to be indented\n- s:EditWrapper(): Correct filenames only if g:vikiDirSeparator == '\\'\n- s:UpdateHeadings(): Use silent! when searching for headers\nMD5 checksum: 918f9422bc3678ccd8c0eb71abad6f6b","3":"- Escape special character when loading \"autoload\/viki\/enc_{&enc}.vim\"\n- Support for xdg\n- Register 3gp as special file\n- viki#SetAnchorMarks(): Hide errors\n- :EditWrapper(): Fix slashes on windows\n- g:vikiIndentedPriorityLists: if 0, allow priority lists not to be indented\n- s:EditWrapper(): Correct filenames only if g:vikiDirSeparator == '\\'\n- s:UpdateHeadings(): Use silent! when searching for headers\nMD5 checksum: 918f9422bc3678ccd8c0eb71abad6f6b","package":"viki.zip","4":"viki.zip","src_id":"17799","5":"17799","creation_date":"1334933760","6":"1334933760"},{"0":"861","vim_version":"7.0","1":"7.0","script_version":"4.00","2":"4.00","version_comment":"- Use conceal to hide bold & typewriter markup and to replace some symbols\n- concealed symbols: ARROWL, ARROWR\n- Use conceal for ArrowTilde*, ARRORLR\n- syntax: Properly highlight tskeleton placeholders in viki syntax\n- Undo special treatment of TSkelPlaceHolder (this should be handled by tskeleton)\n- viki#DirListing(): Don't insert an empty line if the listing is empty\n- g:viki#autoupdate_files: Optionally update all Files regions when setting viki filetype\n- viki#FilesUpdateAll(): call winrestview() only if the view has changed\n- viki#Balloon(): Also show directory listings\n- g:viki#use_texmath: if true, load syntax\/texmath.vim\n- g:vikiNameSuffix: Defaults to .viki\n- g:vikiFamily defaults to viki\n- g:vikiUseParentSuffix default to 1\n- g:vikiHighlightMath defaults to 'latex'\n- g:vikiSaveHistory defaults to 1 if &viminfo includes '!'\n- g:vikiSpecialFilesExtra: Define extra file extensions in .vimrc\n- g:vikiSpecialProtocolsExtra: Define extra special protocols in .vimrc\n- If hidden is off and the buffer is dirty, query the user what to do\n- Rename g:viki#autoupdate_files to g:vikiAutoupdateFiles\n- Syntax: Enable highlighting of spell errors (thanks tlapicka)\n- Cleanup (thanks tlapicka)\n- If b:vikiTextstylesVer == 1: Syntax for vikiColor, vikiContinousColor, and vikiExample (proposed by tlapicka)\n- docs: consistently use .viki as suffix.\n- g:vikiFoldLevel: Set the foldlevel of viki files\n- Use filetypedetect group for BufRead,BufNewFile events\n- vikiUpperCharacters, vikiLowerCharacters: Improved definitions for utf8 & latin1\n- Create ii text object by default.\nMD5 checksum: 95f40e8f6c015161196620f5f6a7e5f1","3":"- Use conceal to hide bold & typewriter markup and to replace some symbols\n- concealed symbols: ARROWL, ARROWR\n- Use conceal for ArrowTilde*, ARRORLR\n- syntax: Properly highlight tskeleton placeholders in viki syntax\n- Undo special treatment of TSkelPlaceHolder (this should be handled by tskeleton)\n- viki#DirListing(): Don't insert an empty line if the listing is empty\n- g:viki#autoupdate_files: Optionally update all Files regions when setting viki filetype\n- viki#FilesUpdateAll(): call winrestview() only if the view has changed\n- viki#Balloon(): Also show directory listings\n- g:viki#use_texmath: if true, load syntax\/texmath.vim\n- g:vikiNameSuffix: Defaults to .viki\n- g:vikiFamily defaults to viki\n- g:vikiUseParentSuffix default to 1\n- g:vikiHighlightMath defaults to 'latex'\n- g:vikiSaveHistory defaults to 1 if &viminfo includes '!'\n- g:vikiSpecialFilesExtra: Define extra file extensions in .vimrc\n- g:vikiSpecialProtocolsExtra: Define extra special protocols in .vimrc\n- If hidden is off and the buffer is dirty, query the user what to do\n- Rename g:viki#autoupdate_files to g:vikiAutoupdateFiles\n- Syntax: Enable highlighting of spell errors (thanks tlapicka)\n- Cleanup (thanks tlapicka)\n- If b:vikiTextstylesVer == 1: Syntax for vikiColor, vikiContinousColor, and vikiExample (proposed by tlapicka)\n- docs: consistently use .viki as suffix.\n- g:vikiFoldLevel: Set the foldlevel of viki files\n- Use filetypedetect group for BufRead,BufNewFile events\n- vikiUpperCharacters, vikiLowerCharacters: Improved definitions for utf8 & latin1\n- Create ii text object by default.\nMD5 checksum: 95f40e8f6c015161196620f5f6a7e5f1","package":"viki.vba","4":"viki.vba","src_id":"17494","5":"17494","creation_date":"1329671015","6":"1329671015"},{"0":"861","vim_version":"7.0","1":"7.0","script_version":"3.20","2":"3.20","version_comment":"- Use syn-conceal if available\n- viki#SetAnchorMarks(): call QuickfixsignsSet('', ['marks']): specify \"marks\"\n- Register docx, pptx, xlsx as special extensions\n- viki_viki#SetupBuffer: Allow brackets in extended viki links\n- compiler\/deplate: Space was not escaped (thanks to E Peron)\n- don't set fold* if vikiFoldMethodVersion<1\n- .gitignore\n- Don't check for has('vim_starting')\n- Moved s:MatchList() to autoload\/viki.vim\n- New: viki#SelectListItem(), viki#ShiftListItem(), viki#MoveListItem()\n- Use vimdedoc.rb to generate the help file from source\n- Enable {fn} macros as hyperlinks\n- VikiDefine: define interviki commands with command!\n- Duplicate help tags (fix #2)\n- vnoremap <buffer> <expr> ii for viki#SelectListItem('.')\n- VikiFoldLevel(): Always check if vikiFolds == \"\"\n- #Files region: allow optional \"head\" argument\n- Configurable option for how to handle malformed viki names\n- Make sure g:VIKIBACKREFS is a dictionary\n- New VikiFoldLevel version 8: headings only, uses cached info about heading levels for speed-up\n- Enable VikiFoldLevel() v8 to fold list items\n- Enable VikiFoldLevel() v8 to inversely fold headings (H)\n- Remove support for multiple folding methods (g:vikiFoldMethodVersion)\nMD5 checksum: 18b8b9837ebb7451d56a90ccfc1de854","3":"- Use syn-conceal if available\n- viki#SetAnchorMarks(): call QuickfixsignsSet('', ['marks']): specify \"marks\"\n- Register docx, pptx, xlsx as special extensions\n- viki_viki#SetupBuffer: Allow brackets in extended viki links\n- compiler\/deplate: Space was not escaped (thanks to E Peron)\n- don't set fold* if vikiFoldMethodVersion<1\n- .gitignore\n- Don't check for has('vim_starting')\n- Moved s:MatchList() to autoload\/viki.vim\n- New: viki#SelectListItem(), viki#ShiftListItem(), viki#MoveListItem()\n- Use vimdedoc.rb to generate the help file from source\n- Enable {fn} macros as hyperlinks\n- VikiDefine: define interviki commands with command!\n- Duplicate help tags (fix #2)\n- vnoremap <buffer> <expr> ii for viki#SelectListItem('.')\n- VikiFoldLevel(): Always check if vikiFolds == \"\"\n- #Files region: allow optional \"head\" argument\n- Configurable option for how to handle malformed viki names\n- Make sure g:VIKIBACKREFS is a dictionary\n- New VikiFoldLevel version 8: headings only, uses cached info about heading levels for speed-up\n- Enable VikiFoldLevel() v8 to fold list items\n- Enable VikiFoldLevel() v8 to inversely fold headings (H)\n- Remove support for multiple folding methods (g:vikiFoldMethodVersion)\nMD5 checksum: 18b8b9837ebb7451d56a90ccfc1de854","package":"viki.vba","4":"viki.vba","src_id":"17285","5":"17285","creation_date":"1327166891","6":"1327166891"},{"0":"861","vim_version":"7.0","1":"7.0","script_version":"3.19","2":"3.19","version_comment":"- Use tlib#balloon#Register() if available\n- viki#Edit(): Switch to homepage only if we are in a viki-enabled buffer\n- Run VimEnter command immediately if !has('vim_starting')\n- Transcode balloon text (guess the file encoding based on the value of &fenc)\n- Don't rely on g:vikiEnabled to be set when loading syntax\/viki.vim\n- Removed g:vikiEnabled variable (use g:viki#quit for checking when to quit)\n- Act more graciously if g:vikiHomePage is empty\nMD5 checksum: 64ebd14609764e98b91f1e233e121e32","3":"- Use tlib#balloon#Register() if available\n- viki#Edit(): Switch to homepage only if we are in a viki-enabled buffer\n- Run VimEnter command immediately if !has('vim_starting')\n- Transcode balloon text (guess the file encoding based on the value of &fenc)\n- Don't rely on g:vikiEnabled to be set when loading syntax\/viki.vim\n- Removed g:vikiEnabled variable (use g:viki#quit for checking when to quit)\n- Act more graciously if g:vikiHomePage is empty\nMD5 checksum: 64ebd14609764e98b91f1e233e121e32","package":"viki.vba","4":"viki.vba","src_id":"14236","5":"14236","creation_date":"1289498382","6":"1289498382"},{"0":"861","vim_version":"7.0","1":"7.0","script_version":"3.18","2":"3.18","version_comment":"- g:vikiFoldMethodVersion defaults to 7 (a simpler method that relies on \"=\" though)\r\n- Syntax for tasks lists\r\n","3":"- g:vikiFoldMethodVersion defaults to 7 (a simpler method that relies on \"=\" though)\r\n- Syntax for tasks lists\r\n","package":"Viki.vba","4":"Viki.vba","src_id":"12755","5":"12755","creation_date":"1270055091","6":"1270055091"},{"0":"861","vim_version":"7.0","1":"7.0","script_version":"3.17","2":"3.17","version_comment":"- FIX: g:vikiOpenUrlWith_ANY for Windows\r\n- Moved definition of fold related variables to ftplugin\/viki.vim\r\n- viki_viki: Anchors in URLs can start with an upper case character\r\n- viki#RestoreCursorPosition(): use winrestview() (reported by Marko Mahnic)\r\n","3":"- FIX: g:vikiOpenUrlWith_ANY for Windows\r\n- Moved definition of fold related variables to ftplugin\/viki.vim\r\n- viki_viki: Anchors in URLs can start with an upper case character\r\n- viki#RestoreCursorPosition(): use winrestview() (reported by Marko Mahnic)\r\n","package":"Viki.vba.gz","4":"Viki.vba.gz","src_id":"12582","5":"12582","creation_date":"1268162387","6":"1268162387"},{"0":"861","vim_version":"7.0","1":"7.0","script_version":"3.16","2":"3.16","version_comment":"- CHANGE: Moved the definition of some variables from plugin\/viki.vim to autoload\/viki.vim (this could require some changes in after\/* user configuration)\r\n- viki#Balloon(), g:vikiBalloonLines: Display text from the target file in a balloon tooltip if &balloonexpr is set to viki#Balloon().\r\n- Renamed VikiMode() to viki#Mode()\r\n- Renamed viki#MakeName() to VikiMakeName()\r\n- Renamed viki#Define() to VikiDefine()\r\n- Removed g:vikiIndex (the index name has to be made explicit in VikiDefine()) in order to reduce startup time\r\n- Set g:vikiMenuPrefix = \"\" in order to reduce startup time\r\n- Registered eml as special file\r\n- Define g:vikiSaveHistory in plugin\/viki.vim (reported by Marko Mahnic)\r\n- FIX: Handling of cursor positions (reported by Marko Mahnic)","3":"- CHANGE: Moved the definition of some variables from plugin\/viki.vim to autoload\/viki.vim (this could require some changes in after\/* user configuration)\r\n- viki#Balloon(), g:vikiBalloonLines: Display text from the target file in a balloon tooltip if &balloonexpr is set to viki#Balloon().\r\n- Renamed VikiMode() to viki#Mode()\r\n- Renamed viki#MakeName() to VikiMakeName()\r\n- Renamed viki#Define() to VikiDefine()\r\n- Removed g:vikiIndex (the index name has to be made explicit in VikiDefine()) in order to reduce startup time\r\n- Set g:vikiMenuPrefix = \"\" in order to reduce startup time\r\n- Registered eml as special file\r\n- Define g:vikiSaveHistory in plugin\/viki.vim (reported by Marko Mahnic)\r\n- FIX: Handling of cursor positions (reported by Marko Mahnic)","package":"Viki.vba.gz","4":"Viki.vba.gz","src_id":"12447","5":"12447","creation_date":"1266671409","6":"1266671409"},{"0":"861","vim_version":"7.0","1":"7.0","script_version":"3.13","2":"3.13","version_comment":"- Extended viki links: decode %HH in local filenames (this may cause problems with file names containing an unencoded %)\r\n- Require tlib 0.32\r\n- viki#ExecExternal(): Escape !\r\n- special file: xmind\r\n- Make regexp for inexistent links case sensitive\r\n- viki#HomePage()\r\n- viki#GetInterVikis()\r\n","3":"- Extended viki links: decode %HH in local filenames (this may cause problems with file names containing an unencoded %)\r\n- Require tlib 0.32\r\n- viki#ExecExternal(): Escape !\r\n- special file: xmind\r\n- Make regexp for inexistent links case sensitive\r\n- viki#HomePage()\r\n- viki#GetInterVikis()\r\n","package":"Viki.vba.gz","4":"Viki.vba.gz","src_id":"11933","5":"11933","creation_date":"1261423952","6":"1261423952"},{"0":"861","vim_version":"7.0","1":"7.0","script_version":"3.11","2":"3.11","version_comment":"- Default values for g:vikiOpenUrlWith_ANY and g:vikiOpenFileWith_ANY on Macs (thanks mboniou)\r\n- Correct default value for g:vikiOpenFileWith_ANY @ Windows\r\n- Disabled regions' #END-syntax\r\n- Don't define interviki commands if a command of the same name already exists.\r\n","3":"- Default values for g:vikiOpenUrlWith_ANY and g:vikiOpenFileWith_ANY on Macs (thanks mboniou)\r\n- Correct default value for g:vikiOpenFileWith_ANY @ Windows\r\n- Disabled regions' #END-syntax\r\n- Don't define interviki commands if a command of the same name already exists.\r\n","package":"Viki.vba.gz","4":"Viki.vba.gz","src_id":"10254","5":"10254","creation_date":"1237545706","6":"1237545706"},{"0":"861","vim_version":"7.0","1":"7.0","script_version":"3.10","2":"3.10","version_comment":"From this version on, viki requires vim 7.2's shellescape() and fnameescape() functions.\r\n\r\n- VikiOpenSpecialFile() uses fnameescape()\r\n- FIX: automatically set marks (#m? type of anchors)\r\n- Anchor regexp can be configured via g:vikiAnchorNameRx\r\n","3":"From this version on, viki requires vim 7.2's shellescape() and fnameescape() functions.\r\n\r\n- VikiOpenSpecialFile() uses fnameescape()\r\n- FIX: automatically set marks (#m? type of anchors)\r\n- Anchor regexp can be configured via g:vikiAnchorNameRx\r\n","package":"Viki.vba.gz","4":"Viki.vba.gz","src_id":"9201","5":"9201","creation_date":"1220163535","6":"1220163535"},{"0":"861","vim_version":"7.0","1":"7.0","script_version":"3.8","2":"3.8","version_comment":"- FIX: viki#MarkInexistentInElement() for pre 7.0.009 vim (thanks to M Brandmeyer)\r\n- FIX: Make sure tlib is loaded even if it is installed in a different rtp-directory (thanks to M Brandmeyer)\r\n- Added dia to g:vikiSpecialFiles\r\n- FIX: Scrambled window when opening an url from vim (thanks A Moell)","3":"- FIX: viki#MarkInexistentInElement() for pre 7.0.009 vim (thanks to M Brandmeyer)\r\n- FIX: Make sure tlib is loaded even if it is installed in a different rtp-directory (thanks to M Brandmeyer)\r\n- Added dia to g:vikiSpecialFiles\r\n- FIX: Scrambled window when opening an url from vim (thanks A Moell)","package":"Viki.vba.gz","4":"Viki.vba.gz","src_id":"8835","5":"8835","creation_date":"1214085281","6":"1214085281"},{"0":"861","vim_version":"7.0","1":"7.0","script_version":"3.7","2":"3.7","version_comment":"- In a file that doesn't contain headings, return 0 instead of '=' as \r\ndefault value if g:vikiFoldMethodVersion == 4.\r\n- FIX: \"=\" in if expressions in certain versions of VikiFoldLevel()\r\n","3":"- In a file that doesn't contain headings, return 0 instead of '=' as \r\ndefault value if g:vikiFoldMethodVersion == 4.\r\n- FIX: \"=\" in if expressions in certain versions of VikiFoldLevel()\r\n","package":"Viki.vba.gz","4":"Viki.vba.gz","src_id":"8153","5":"8153","creation_date":"1200390731","6":"1200390731"},{"0":"861","vim_version":"7.0","1":"7.0","script_version":"3.6","2":"3.6","version_comment":"- Forgot to define a default value for g:viki_intervikis.","3":"- Forgot to define a default value for g:viki_intervikis.","package":"Viki.vba.gz","4":"Viki.vba.gz","src_id":"8152","5":"8152","creation_date":"1200285719","6":"1200285719"},{"0":"861","vim_version":"7.0","1":"7.0","script_version":"3.5","2":"3.5","version_comment":"- Don't try to append an empty anchor to an url (Thanks RM Schmid).\r\n- New variable g:viki_interviki to define intervikis in ~\/.vimrc without loading autoload\/viki.vim\r\n- Minor updates to the help file.","3":"- Don't try to append an empty anchor to an url (Thanks RM Schmid).\r\n- New variable g:viki_interviki to define intervikis in ~\/.vimrc without loading autoload\/viki.vim\r\n- Minor updates to the help file.","package":"Viki.vba.gz","4":"Viki.vba.gz","src_id":"8149","5":"8149","creation_date":"1200221086","6":"1200221086"},{"0":"861","vim_version":"7.0","1":"7.0","script_version":"3.4","2":"3.4","version_comment":"- Promote anchors to VikiOpenSpecialProtocol().\r\n- viki_viki: Enabled #INCLUDE\r\n- Put the poor-man's math highlighting into syntax\/texmath.vim so that \r\nit can be included from other syntax files.\r\n- Cascade menu of intervikis\r\n- FIX: don't register viki names as known\/unknown more than once\r\n","3":"- Promote anchors to VikiOpenSpecialProtocol().\r\n- viki_viki: Enabled #INCLUDE\r\n- Put the poor-man's math highlighting into syntax\/texmath.vim so that \r\nit can be included from other syntax files.\r\n- Cascade menu of intervikis\r\n- FIX: don't register viki names as known\/unknown more than once\r\n","package":"Viki.vba.gz","4":"Viki.vba.gz","src_id":"8127","5":"8127","creation_date":"1199504432","6":"1199504432"},{"0":"861","vim_version":"7.0","1":"7.0","script_version":"3.3","2":"3.3","version_comment":"- Use hookcursormoved >= 0.3\r\n- Backslash-save command-line completion\r\n- Mark unknown intervikis as inexistent\r\n","3":"- Use hookcursormoved >= 0.3\r\n- Backslash-save command-line completion\r\n- Mark unknown intervikis as inexistent\r\n","package":"Viki.vba.gz","4":"Viki.vba.gz","src_id":"7790","5":"7790","creation_date":"1192229070","6":"1192229070"},{"0":"861","vim_version":"7.0","1":"7.0","script_version":"3.2","2":"3.2","version_comment":"- viki_viki.vim: Wrong value for b:vikiCmdDestIdx and \r\nb:vikiCmdAnchorIdx.\r\n- Moved :VikiMinorModeViki, :VikiMinorModeLaTeX, and \r\n:VikiMinorModeAnyWord to plugin\/viki.vim\r\n","3":"- viki_viki.vim: Wrong value for b:vikiCmdDestIdx and \r\nb:vikiCmdAnchorIdx.\r\n- Moved :VikiMinorModeViki, :VikiMinorModeLaTeX, and \r\n:VikiMinorModeAnyWord to plugin\/viki.vim\r\n","package":"Viki.vba.gz","4":"Viki.vba.gz","src_id":"7754","5":"7754","creation_date":"1191578311","6":"1191578311"},{"0":"861","vim_version":"7.0","1":"7.0","script_version":"3.1","2":"3.1","version_comment":"- Slightly improved performance of s:MarkInexistent() and \r\nviki#HookCheckPreviousPosition().\r\n","3":"- Slightly improved performance of s:MarkInexistent() and \r\nviki#HookCheckPreviousPosition().\r\n","package":"Viki.vba.gz","4":"Viki.vba.gz","src_id":"7752","5":"7752","creation_date":"1191501626","6":"1191501626"},{"0":"861","vim_version":"7.0","1":"7.0","script_version":"3.0","2":"3.0","version_comment":"- VikiFolds() rev4: The text body is set to max heading level + 1 in \r\norder to avoid lookups and thus speed-up the code.\r\n- g:vikiPromote: Don't set viki minor modes for any files opened via \r\nviki, unless this variable is set\r\n- Added support for 'l' vikiFolds to the default fold expression.\r\n- Added support for the {ref} macro (the referenced label has to be in \r\nthe same file though)\r\n- INCOMPATIBLE CHANGE: Moved most function to autoload\/viki.vim; moved \r\nsupport for deplate\/viki markup to vikiDeplate.vim.\r\n- The argument of the VikiMode() has changed. (But this function \r\nshouldn't be used anyway.)\r\n- With g:vikiFoldMethodVersion=4 (the default), the text body is at the \r\nlevel of the heading. This uses \"=\" for the body, which can be a problem \r\non slow machines. With g:vikiFoldMethodVersion=5, the body is below the \r\nlowest heading, which can cause other problem.\r\n- :VikiEditInVim ... edit special files in vim\r\n- Set the default value for g:vikiCacheInexistent in order not to \r\nsurprise users with the abundance of cached data.\r\n- Require tlib 0.15\r\n- Use tlib#progressbar\r\n- Improved (poor-man's) tex\/math syntax highlighting\r\n- Removed norm! commands form s:MarkInexistent().\r\n- FIX: Wrong value for b:vikiSimpleNameAnchorIdx when simple viki names \r\nweren't disabled.\r\n- Optionally use hookcursormoved (vimscript #2037) for improved detection of hyperlinks to \r\ninexistent sources. If this plugin causes difficulties, please tell me \r\nand temporarily remove it.\r\n- Use matchlist() instead of substitute(), which could speed things up a \r\nlittle.\r\n","3":"- VikiFolds() rev4: The text body is set to max heading level + 1 in \r\norder to avoid lookups and thus speed-up the code.\r\n- g:vikiPromote: Don't set viki minor modes for any files opened via \r\nviki, unless this variable is set\r\n- Added support for 'l' vikiFolds to the default fold expression.\r\n- Added support for the {ref} macro (the referenced label has to be in \r\nthe same file though)\r\n- INCOMPATIBLE CHANGE: Moved most function to autoload\/viki.vim; moved \r\nsupport for deplate\/viki markup to vikiDeplate.vim.\r\n- The argument of the VikiMode() has changed. (But this function \r\nshouldn't be used anyway.)\r\n- With g:vikiFoldMethodVersion=4 (the default), the text body is at the \r\nlevel of the heading. This uses \"=\" for the body, which can be a problem \r\non slow machines. With g:vikiFoldMethodVersion=5, the body is below the \r\nlowest heading, which can cause other problem.\r\n- :VikiEditInVim ... edit special files in vim\r\n- Set the default value for g:vikiCacheInexistent in order not to \r\nsurprise users with the abundance of cached data.\r\n- Require tlib 0.15\r\n- Use tlib#progressbar\r\n- Improved (poor-man's) tex\/math syntax highlighting\r\n- Removed norm! commands form s:MarkInexistent().\r\n- FIX: Wrong value for b:vikiSimpleNameAnchorIdx when simple viki names \r\nweren't disabled.\r\n- Optionally use hookcursormoved (vimscript #2037) for improved detection of hyperlinks to \r\ninexistent sources. If this plugin causes difficulties, please tell me \r\nand temporarily remove it.\r\n- Use matchlist() instead of substitute(), which could speed things up a \r\nlittle.\r\n","package":"Viki.vba.gz","4":"Viki.vba.gz","src_id":"7749","5":"7749","creation_date":"1191492321","6":"1191492321"},{"0":"861","vim_version":"7.0","1":"7.0","script_version":"2.4","2":"2.4","version_comment":"- The shortcuts automatically defined by VikiDefine may now take an \r\noptional argument (the file on an interviki) (:WIKI thus is the same as \r\n:VikiEdit WIKI:: and supports the same command-line completion)\r\n- Read \".vikiWords\" in parent directories (top-down); \r\ng:vikiHyperWordsFiles: Changed order (read global words first)\r\n- In .vikiWords: destination can be an interviki name (if not, it is \r\nassumed to be a relative filename); if destination is -, the word will \r\nbe removed from the jump table; blanks in \"hyperwords\" will be replaced \r\nwith \\s\\+ in the regular expression.\r\n- New :VikiBrowse command.\r\n- FIX: wrong value for &comments\r\n- FIX: need to reset filetype on color-scheme change (because of viki's \r\nown styles)\r\n- FIX: Caching of inexistent viki names.\r\n- In minor mode, don't map keys that trigger a check for inexistent \r\nlinks.\r\n- Don't highlight textstyles (emphasized, typewriter) in comments.\r\n- Removed configuration by: VikiInexistentColor(), \r\ng:vikiInexistentColor, VikiHyperLinkColor(), g:vikiHyperLinkColor; use \r\ng:viki_highlight_hyperlink_light, g:viki_highlight_hyperlink_dark, \r\ng:viki_highlight_inexistent_light, g:viki_highlight_inexistent_dark \r\ninstead. By default, links are no longer made bold.\r\n- The new default fold expression (g:vikiFoldMethodVersion=4) support \r\nonly hH folds (normal and inverse headings based; see g:vikiFolds). \r\nPrevious fold methods can be used by setting g:vikiFoldMethodVersion.\r\n","3":"- The shortcuts automatically defined by VikiDefine may now take an \r\noptional argument (the file on an interviki) (:WIKI thus is the same as \r\n:VikiEdit WIKI:: and supports the same command-line completion)\r\n- Read \".vikiWords\" in parent directories (top-down); \r\ng:vikiHyperWordsFiles: Changed order (read global words first)\r\n- In .vikiWords: destination can be an interviki name (if not, it is \r\nassumed to be a relative filename); if destination is -, the word will \r\nbe removed from the jump table; blanks in \"hyperwords\" will be replaced \r\nwith \\s\\+ in the regular expression.\r\n- New :VikiBrowse command.\r\n- FIX: wrong value for &comments\r\n- FIX: need to reset filetype on color-scheme change (because of viki's \r\nown styles)\r\n- FIX: Caching of inexistent viki names.\r\n- In minor mode, don't map keys that trigger a check for inexistent \r\nlinks.\r\n- Don't highlight textstyles (emphasized, typewriter) in comments.\r\n- Removed configuration by: VikiInexistentColor(), \r\ng:vikiInexistentColor, VikiHyperLinkColor(), g:vikiHyperLinkColor; use \r\ng:viki_highlight_hyperlink_light, g:viki_highlight_hyperlink_dark, \r\ng:viki_highlight_inexistent_light, g:viki_highlight_inexistent_dark \r\ninstead. By default, links are no longer made bold.\r\n- The new default fold expression (g:vikiFoldMethodVersion=4) support \r\nonly hH folds (normal and inverse headings based; see g:vikiFolds). \r\nPrevious fold methods can be used by setting g:vikiFoldMethodVersion.\r\n","package":"Viki.vba.gz","4":"Viki.vba.gz","src_id":"7560","5":"7560","creation_date":"1188130607","6":"1188130607"},{"0":"861","vim_version":"7.0","1":"7.0","script_version":"2.3","2":"2.3","version_comment":"- Require tlib >= 0.9\r\n- FIX: Use absolute file names when editing a local file (avoid problem \r\nwhen opening a file in a different window with a different CWD).\r\n- New folding routine. Use the old folding method by setting \r\ng:vikiFoldMethodVersion to 1.\r\n","3":"- Require tlib >= 0.9\r\n- FIX: Use absolute file names when editing a local file (avoid problem \r\nwhen opening a file in a different window with a different CWD).\r\n- New folding routine. Use the old folding method by setting \r\ng:vikiFoldMethodVersion to 1.\r\n","package":"Viki.vba.gz","4":"Viki.vba.gz","src_id":"7365","5":"7365","creation_date":"1184663431","6":"1184663431"},{"0":"861","vim_version":"7.0","1":"7.0","script_version":"2.2","2":"2.2","version_comment":"- Re-Enabled the previously (2.1) made and then disabled change concerning re-entering a viki buffer\r\n- Don't try to use cached values for buffers that have no file attached yet (thanks to Erik Olsson)\r\n- Require tlib >= 0.8\r\n","3":"- Re-Enabled the previously (2.1) made and then disabled change concerning re-entering a viki buffer\r\n- Don't try to use cached values for buffers that have no file attached yet (thanks to Erik Olsson)\r\n- Require tlib >= 0.8\r\n","package":"Viki.vba.gz","4":"Viki.vba.gz","src_id":"7300","5":"7300","creation_date":"1182677792","6":"1182677792"},{"0":"861","vim_version":"7.0","1":"7.0","script_version":"2.1","2":"2.1","version_comment":"- Cache inexistent patterns (experimental)\r\n- s:EditWrapper: Don't escape ' '.\r\n- FIX: VikiMode(): Error message about b:did_ftplugin not being defined\r\n- FIX: Check if g:netrw_browsex_viewer is defined (thanks to Erik Olsson for pointing this and some other problems out)\r\n- ftplugin\/viki.vim: FIX: Problem with heading in the last line. Disabled vikiFolds type 's'\r\n- Always check the current line for inexistent links when re-entering a viki buffer\r\n","3":"- Cache inexistent patterns (experimental)\r\n- s:EditWrapper: Don't escape ' '.\r\n- FIX: VikiMode(): Error message about b:did_ftplugin not being defined\r\n- FIX: Check if g:netrw_browsex_viewer is defined (thanks to Erik Olsson for pointing this and some other problems out)\r\n- ftplugin\/viki.vim: FIX: Problem with heading in the last line. Disabled vikiFolds type 's'\r\n- Always check the current line for inexistent links when re-entering a viki buffer\r\n","package":"Viki.vba.gz","4":"Viki.vba.gz","src_id":"7298","5":"7298","creation_date":"1182664942","6":"1182664942"},{"0":"861","vim_version":"7.0","1":"7.0","script_version":"2.0","2":"2.0","version_comment":"- Got rid of multvals & genutils dependencies (use vim7 lists instead)\r\n- New dependency: tlib.vim (vimscript #1863)\r\n- INCOMPATIBLE CHANGE: The format of g:vikiMapFunctionality has changed.\r\n- INCOMPATIBLE CHANGE: g:vikiSpecialFiles is now a list!\r\n- Viki now has a special #Files region that can be automatically \r\nupdated. This way we can start thinking about using viki for as \r\nproject\/file management tool. This is for vim only and not supported yet \r\nin deplate. New related maps & commands: :VikiFilesUpdate (<LL>vu), \r\n:VikiFilesUpdateAll (<LL>vU), :VikiFilesCmd, :VikiFilesCall, \r\n:VikiFilesExec (<LL>vx), and VikiFileExec.\r\n- VikiGoParent() (mapped to <LL>v<bs> or <LL>v<up>): If b:vikiParent is \r\ndefined, open this viki name, otherwise follow the backlink.\r\n- New :VikiEditTab command.\r\n- Map <LL>vt to open in tab.\r\n- Map <LL>v<left> to open go back.\r\n- Keys listed in g:vikiMapQParaKeys are now mapped to \r\ns:VikiMarkInexistentInParagraphVisible() which checks only the visible \r\narea and thus avoids scrolling.\r\n- Highlight lines containing blanks (which vim doesn't treat as \r\nparagraph separators)\r\n- When following a link, check if it is an special viki name before \r\nassuming it's a simple one.\r\n- Map [[, ]], [], ][\r\n- If an interviki has an index file, a viki name like [[INTERVIKI::]] \r\nwill now open the index file. In order to browse the directory, use \r\n[[INTERVIKI::.]]. If no index file is defined, the directory will be \r\nopened either way.\r\n- Set the default value of g:vikiFeedbackMin to &lines.\r\n- Added ws as special files to be opened with :WsOpen if existent.\r\n- Replaced most occurences of <SID> with s:\r\n- Use tlib#InputList() for selecting back references.\r\n- g:vikiOpenFileWith_ANY now uses g:netrw_browsex_viewer by default.\r\n- CHANGE: g:vikiSaveHistory: We now rely on viminfo's \"!\" option to save \r\nback-references.\r\n- FIX: VikiEdit now works properly with protocols that are to be opened \r\nwith an external viewer\r\n- FIX: VikiEdit completion, which is more usable now\r\n","3":"- Got rid of multvals & genutils dependencies (use vim7 lists instead)\r\n- New dependency: tlib.vim (vimscript #1863)\r\n- INCOMPATIBLE CHANGE: The format of g:vikiMapFunctionality has changed.\r\n- INCOMPATIBLE CHANGE: g:vikiSpecialFiles is now a list!\r\n- Viki now has a special #Files region that can be automatically \r\nupdated. This way we can start thinking about using viki for as \r\nproject\/file management tool. This is for vim only and not supported yet \r\nin deplate. New related maps & commands: :VikiFilesUpdate (<LL>vu), \r\n:VikiFilesUpdateAll (<LL>vU), :VikiFilesCmd, :VikiFilesCall, \r\n:VikiFilesExec (<LL>vx), and VikiFileExec.\r\n- VikiGoParent() (mapped to <LL>v<bs> or <LL>v<up>): If b:vikiParent is \r\ndefined, open this viki name, otherwise follow the backlink.\r\n- New :VikiEditTab command.\r\n- Map <LL>vt to open in tab.\r\n- Map <LL>v<left> to open go back.\r\n- Keys listed in g:vikiMapQParaKeys are now mapped to \r\ns:VikiMarkInexistentInParagraphVisible() which checks only the visible \r\narea and thus avoids scrolling.\r\n- Highlight lines containing blanks (which vim doesn't treat as \r\nparagraph separators)\r\n- When following a link, check if it is an special viki name before \r\nassuming it's a simple one.\r\n- Map [[, ]], [], ][\r\n- If an interviki has an index file, a viki name like [[INTERVIKI::]] \r\nwill now open the index file. In order to browse the directory, use \r\n[[INTERVIKI::.]]. If no index file is defined, the directory will be \r\nopened either way.\r\n- Set the default value of g:vikiFeedbackMin to &lines.\r\n- Added ws as special files to be opened with :WsOpen if existent.\r\n- Replaced most occurences of <SID> with s:\r\n- Use tlib#InputList() for selecting back references.\r\n- g:vikiOpenFileWith_ANY now uses g:netrw_browsex_viewer by default.\r\n- CHANGE: g:vikiSaveHistory: We now rely on viminfo's \"!\" option to save \r\nback-references.\r\n- FIX: VikiEdit now works properly with protocols that are to be opened \r\nwith an external viewer\r\n- FIX: VikiEdit completion, which is more usable now\r\n","package":"Viki.vba.gz","4":"Viki.vba.gz","src_id":"7132","5":"7132","creation_date":"1179383265","6":"1179383265"},{"0":"861","vim_version":"7.0","1":"7.0","script_version":"1.13","2":"1.13","version_comment":"- Intervikis can now be defined as function ('*Function(\"%s\")', this \r\nbreaks conversion via deplate) or format string ('%\/foo\/%s\/bar', not yet \r\nsupported by deplate)\r\n- Task lists take optional tags, eg #A [tag] foo; they may also be \r\ntagged with the letters G-Z, which are highlighted as general task (not \r\nsupported by deplate)\r\n- Automatically set marks for labels prefixed with \"m\" (eg #ma -> 'a, \r\n#mB -> 'B)\r\n- Two new g:vikiNameTypes: w = (Hyper)Words, f = File names in cwd as \r\nhyperwords (experimental, not implemented in deplate)\r\n- In extended viki names: add the suffix only if the destination hasn't \r\ngot one\r\n- A buffer local b:vikiOpenInWindow allows links to be redirected to a \r\ncertain window (ie, if b:vikiOpenInWindow = 2, pressing <c-cr> behaves \r\nlike <LocalLeader>v2); this is useful if you use some kind of \r\ndirectory\/catalog metafile; possible values: absolute number, +\/- \r\nrelative number, \"last\"\r\n- Switched back to old regexp for simple names in order to avoid \r\nhighlighting of names like LaTeX\r\n- VikiEdit opens the homepage only if b:vikiFamily is set\r\n- Map <LocalLeader>vF to <LocalLeader>vn<LocalLeader>vf\r\n- Improved syntax for (nested) macros\r\n- Set &suffixesadd so that you can use vim's own gf in some situations\r\n- SYNTAX: Allow empty lines as region delimiters (deplate 0.8.1)\r\n- FIX: simple viki names with anchors where not recognised\r\n- FIX: don't mark simple (inter)viki names as inexistent that expand to \r\nlinks matching g:vikiSpecialProtocols\r\n- FIX: file names containing %\r\n- FIX: added a patch (VikiMarkInexistentInElement) by Kevin Kleinfelter \r\nfor compatibility with an unpatched vim70 (untested)\r\n- FIX: disabling simple names (s) also properly disables the name types: \r\nScwf\r\n","3":"- Intervikis can now be defined as function ('*Function(\"%s\")', this \r\nbreaks conversion via deplate) or format string ('%\/foo\/%s\/bar', not yet \r\nsupported by deplate)\r\n- Task lists take optional tags, eg #A [tag] foo; they may also be \r\ntagged with the letters G-Z, which are highlighted as general task (not \r\nsupported by deplate)\r\n- Automatically set marks for labels prefixed with \"m\" (eg #ma -> 'a, \r\n#mB -> 'B)\r\n- Two new g:vikiNameTypes: w = (Hyper)Words, f = File names in cwd as \r\nhyperwords (experimental, not implemented in deplate)\r\n- In extended viki names: add the suffix only if the destination hasn't \r\ngot one\r\n- A buffer local b:vikiOpenInWindow allows links to be redirected to a \r\ncertain window (ie, if b:vikiOpenInWindow = 2, pressing <c-cr> behaves \r\nlike <LocalLeader>v2); this is useful if you use some kind of \r\ndirectory\/catalog metafile; possible values: absolute number, +\/- \r\nrelative number, \"last\"\r\n- Switched back to old regexp for simple names in order to avoid \r\nhighlighting of names like LaTeX\r\n- VikiEdit opens the homepage only if b:vikiFamily is set\r\n- Map <LocalLeader>vF to <LocalLeader>vn<LocalLeader>vf\r\n- Improved syntax for (nested) macros\r\n- Set &suffixesadd so that you can use vim's own gf in some situations\r\n- SYNTAX: Allow empty lines as region delimiters (deplate 0.8.1)\r\n- FIX: simple viki names with anchors where not recognised\r\n- FIX: don't mark simple (inter)viki names as inexistent that expand to \r\nlinks matching g:vikiSpecialProtocols\r\n- FIX: file names containing %\r\n- FIX: added a patch (VikiMarkInexistentInElement) by Kevin Kleinfelter \r\nfor compatibility with an unpatched vim70 (untested)\r\n- FIX: disabling simple names (s) also properly disables the name types: \r\nScwf\r\n","package":"viki.zip","4":"viki.zip","src_id":"6853","5":"6853","creation_date":"1173615560","6":"1173615560"},{"0":"861","vim_version":"6.0","1":"6.0","script_version":"1.12","2":"1.12","version_comment":"- Define some keywords in syntax file (useful for omnicompletion)\r\n- Define :VIKI command as an alias for :VikiHome\r\n- FIX: Problem with names containing spaces\r\n- FIX: Extended names with suffix & interviki\r\n- FIX: Indentation of priority lists.\r\n- FIX: VikiDefine created wrong (old-fashioned) VikiEdit commands under \r\ncertain conditions.\r\n- FIX: Directories in extended viki names + interviki names were marked \r\nas inexistent\r\n- FIX: Syntax highlighting of regions or commands the headline of which \r\nspanned several lines\r\n- Added ppt to g:vikiSpecialFiles.\r\n","3":"- Define some keywords in syntax file (useful for omnicompletion)\r\n- Define :VIKI command as an alias for :VikiHome\r\n- FIX: Problem with names containing spaces\r\n- FIX: Extended names with suffix & interviki\r\n- FIX: Indentation of priority lists.\r\n- FIX: VikiDefine created wrong (old-fashioned) VikiEdit commands under \r\ncertain conditions.\r\n- FIX: Directories in extended viki names + interviki names were marked \r\nas inexistent\r\n- FIX: Syntax highlighting of regions or commands the headline of which \r\nspanned several lines\r\n- Added ppt to g:vikiSpecialFiles.\r\n","package":"Viki.zip","4":"Viki.zip","src_id":"6219","5":"6219","creation_date":"1158979919","6":"1158979919"},{"0":"861","vim_version":"6.0","1":"6.0","script_version":"1.11","2":"1.11","version_comment":"- Enable [[INTERVIKI::]]\r\n- VikiEdit also creates commands for intervikis that have no index\r\n- Respect \"!\" and \"*\" modifiers in extended viki links\r\n- New g:vikiMapFunctionalityMinor variable\r\n- New g:vikiMapLeader variable\r\n- CHANGE: Don't map VikiMarkInexistent in minor mode (see \r\ng:vikiMapFunctionalityMinor)\r\n- CHANGE: new attributes for g:vikiMapFunctionality: c, m[fb], i, I\r\n- SYNTAX: cterm support for todo lists, emphasize\r\n- FIX: Erroneous cursor movement\r\n- FIX: VikiEdit didn't check if a file was already opened, which caused \r\na file to be opened in two buffers under certain conditions\r\n- FIX: Error in <SID>MapMarkInexistent()\r\n- FIX: VikiEdit: Non-viki names were not quoted\r\n- FIX: Use fnamemodify() to expand tildes in filenames\r\n- FIX: Inexistent quoted viki names with an interviki prefix weren't \r\nproperly highlighted\r\n- FIX: Minor problem with suffixes & extended viki names\r\n- FIX: Use keepjumps\r\n- FIX: Catch E325\r\n- FIX: Don't catch errors in <SID>EditWrapper() if the command matches \r\ng:vikiNoWrapper (due to possible compatibility problems eg with :Explore \r\nin vim 6.4)\r\n- OBSOLETE: Negative arguments to VikiMode or VikiMinorMode are obsolete \r\n(or they became the default to be precise)\r\n- OBSOLETE: g:vikiMapMouse\r\n- REMOVED: mapping to <LocalLeader><c-cr>\r\n- DEPRECATED: VikiModeMaybe\r\n","3":"- Enable [[INTERVIKI::]]\r\n- VikiEdit also creates commands for intervikis that have no index\r\n- Respect \"!\" and \"*\" modifiers in extended viki links\r\n- New g:vikiMapFunctionalityMinor variable\r\n- New g:vikiMapLeader variable\r\n- CHANGE: Don't map VikiMarkInexistent in minor mode (see \r\ng:vikiMapFunctionalityMinor)\r\n- CHANGE: new attributes for g:vikiMapFunctionality: c, m[fb], i, I\r\n- SYNTAX: cterm support for todo lists, emphasize\r\n- FIX: Erroneous cursor movement\r\n- FIX: VikiEdit didn't check if a file was already opened, which caused \r\na file to be opened in two buffers under certain conditions\r\n- FIX: Error in <SID>MapMarkInexistent()\r\n- FIX: VikiEdit: Non-viki names were not quoted\r\n- FIX: Use fnamemodify() to expand tildes in filenames\r\n- FIX: Inexistent quoted viki names with an interviki prefix weren't \r\nproperly highlighted\r\n- FIX: Minor problem with suffixes & extended viki names\r\n- FIX: Use keepjumps\r\n- FIX: Catch E325\r\n- FIX: Don't catch errors in <SID>EditWrapper() if the command matches \r\ng:vikiNoWrapper (due to possible compatibility problems eg with :Explore \r\nin vim 6.4)\r\n- OBSOLETE: Negative arguments to VikiMode or VikiMinorMode are obsolete \r\n(or they became the default to be precise)\r\n- OBSOLETE: g:vikiMapMouse\r\n- REMOVED: mapping to <LocalLeader><c-cr>\r\n- DEPRECATED: VikiModeMaybe\r\n","package":"Viki.zip","4":"Viki.zip","src_id":"5585","5":"5585","creation_date":"1145532364","6":"1145532364"},{"0":"861","vim_version":"6.0","1":"6.0","script_version":"1.10","2":"1.10","version_comment":"- Pseudo anchors (not supported by deplate): jump to a line number, e.g. [[file#l=10]] or [[file#line=10]]; find an regexp, e.g. [[file#rx=\\\\d]]; execute some vim code, e.g. [[file#vim=call Whatever()]]; you can also define your own handlers: VikiAnchor_{type}(arg)\r\n- g:vikiFolds: new 'b' flag: the body has a higher level than all \r\nheadings (gives you some kind of outliner experience; the default value \r\nfor g:vikiFolds was changed to 'h')\r\n- FIX: VikiFindAnchor didn't work properly in some situations\r\n- FIX: Escape blanks when following a link (this could cause problems in \r\nsome situations, not always)\r\n- FIX: Don't try to mark inexistent links when pressing enter if the current \r\nline is empty.\r\n- FIX: Restore vertical cursor position in window after looking for \r\ninexistent links.\r\n- FIX: Backslashes got lost in some situations.\r\n","3":"- Pseudo anchors (not supported by deplate): jump to a line number, e.g. [[file#l=10]] or [[file#line=10]]; find an regexp, e.g. [[file#rx=\\\\d]]; execute some vim code, e.g. [[file#vim=call Whatever()]]; you can also define your own handlers: VikiAnchor_{type}(arg)\r\n- g:vikiFolds: new 'b' flag: the body has a higher level than all \r\nheadings (gives you some kind of outliner experience; the default value \r\nfor g:vikiFolds was changed to 'h')\r\n- FIX: VikiFindAnchor didn't work properly in some situations\r\n- FIX: Escape blanks when following a link (this could cause problems in \r\nsome situations, not always)\r\n- FIX: Don't try to mark inexistent links when pressing enter if the current \r\nline is empty.\r\n- FIX: Restore vertical cursor position in window after looking for \r\ninexistent links.\r\n- FIX: Backslashes got lost in some situations.\r\n","package":"Viki.zip","4":"Viki.zip","src_id":"5438","5":"5438","creation_date":"1142419079","6":"1142419079"},{"0":"861","vim_version":"6.0","1":"6.0","script_version":"1.9","2":"1.9","version_comment":"- Register mp3, ogg and some other multimedia related suffixes as \r\nspecial files\r\n- Add a menu of Intervikis if g:vikiMenuPrefix is != ''\r\n- g:vikiMapKeys can contain \"\\n\" and \" \" (supplement g:vikiMapKeys with \r\nthe variables g:vikiMapQParaKeys and g:vikiMapBeforeKeys)\r\n- FIX: <SID>IsSupportedType\r\n- FIX: Only the first inexistent link in a line was highlighted\r\n- FIX: Set &buflisted when editing an existing buffer\r\n- FIX: VikiDefine: Non-viki index names weren't quoted\r\n- FIX: In \"minor mode\", vikiFamily wasn't correctly set in some \r\nsituations; other problems related to b:vikiFamily\r\n- FIX: AnyWord works again\r\n- Removed: VikiMinorModeMaybe\r\n- VikiDefine now takes an optional fourth argument (an index file; \r\ndefault=Index) and automatically creates a vim command with the name of \r\nthe interviki that opens this index file\r\n","3":"- Register mp3, ogg and some other multimedia related suffixes as \r\nspecial files\r\n- Add a menu of Intervikis if g:vikiMenuPrefix is != ''\r\n- g:vikiMapKeys can contain \"\\n\" and \" \" (supplement g:vikiMapKeys with \r\nthe variables g:vikiMapQParaKeys and g:vikiMapBeforeKeys)\r\n- FIX: <SID>IsSupportedType\r\n- FIX: Only the first inexistent link in a line was highlighted\r\n- FIX: Set &buflisted when editing an existing buffer\r\n- FIX: VikiDefine: Non-viki index names weren't quoted\r\n- FIX: In \"minor mode\", vikiFamily wasn't correctly set in some \r\nsituations; other problems related to b:vikiFamily\r\n- FIX: AnyWord works again\r\n- Removed: VikiMinorModeMaybe\r\n- VikiDefine now takes an optional fourth argument (an index file; \r\ndefault=Index) and automatically creates a vim command with the name of \r\nthe interviki that opens this index file\r\n","package":"Viki.zip","4":"Viki.zip","src_id":"5299","5":"5299","creation_date":"1140604309","6":"1140604309"},{"0":"861","vim_version":"6.0","1":"6.0","script_version":"1.8","2":"1.8","version_comment":"- Fold lists too (see also g:vikiFolds)\r\n- Allow interviki names in extended viki names (e.g., \r\n[[WIKI::WikiName][Display Name]])\r\n- Renamed <SID>GetSimpleRx4SimpleWikiName() to \r\nVikiGetSimpleRx4SimpleWikiName() (required in some occasions; increased the \r\nversion number so that we can check against it)\r\n- Fix: Problem with urls\/fnames containing '!' and other special characters \r\n(which now have to be escaped by the handler; so if you defined a custom \r\nhandler, e.g. g:vikiOpenFileWith_ANY, please adapt its definition)\r\n- Fix: VikiEdit! opens the homepage only when b:vikiEnabled is defined in the \r\ncurrent buffer (we assume that for the homepage the global configuration is in \r\neffect)\r\n- Fix: Problem when g:vikiMarkInexistent was false\/0\r\n- Fix: Removed \\c from the regular expression for extended names, which caused \r\nFindNext to malfunction and caused a serious slowdown when matching of \r\nbad\/unknown links\r\n- Fix: Re-set viki minor mode after entering a buffer\r\n- The state argument in Viki(Minor)Mode is now mostly ignored\r\n- Fix: A simple name's anchor was ignored\r\n","3":"- Fold lists too (see also g:vikiFolds)\r\n- Allow interviki names in extended viki names (e.g., \r\n[[WIKI::WikiName][Display Name]])\r\n- Renamed <SID>GetSimpleRx4SimpleWikiName() to \r\nVikiGetSimpleRx4SimpleWikiName() (required in some occasions; increased the \r\nversion number so that we can check against it)\r\n- Fix: Problem with urls\/fnames containing '!' and other special characters \r\n(which now have to be escaped by the handler; so if you defined a custom \r\nhandler, e.g. g:vikiOpenFileWith_ANY, please adapt its definition)\r\n- Fix: VikiEdit! opens the homepage only when b:vikiEnabled is defined in the \r\ncurrent buffer (we assume that for the homepage the global configuration is in \r\neffect)\r\n- Fix: Problem when g:vikiMarkInexistent was false\/0\r\n- Fix: Removed \\c from the regular expression for extended names, which caused \r\nFindNext to malfunction and caused a serious slowdown when matching of \r\nbad\/unknown links\r\n- Fix: Re-set viki minor mode after entering a buffer\r\n- The state argument in Viki(Minor)Mode is now mostly ignored\r\n- Fix: A simple name's anchor was ignored\r\n","package":"Viki.zip","4":"Viki.zip","src_id":"4803","5":"4803","creation_date":"1132739964","6":"1132739964"},{"0":"861","vim_version":"6.0","1":"6.0","script_version":"1.7","2":"1.7","version_comment":"- g:vikiHomePage: If you call VikiEdit! (with \"bang\"), the homepage is opened \r\nfirst so that its customizations are in effect. Also, if you call :VikiHome or \r\n:VikiEdit *, the homepage is opened.\r\n- basic highlighting & indentation of emacs-planner style task lists (sort of)\r\n- command line completion for :VikiEdit\r\n- new command\/function VikiDefine for defining intervikis\r\n- added <LocalLeader>ve map for :VikiEdit\r\n- fixed problem in VikiEdit (when the cursor was on a valid viki link, the \r\ntext argument was ignored)\r\n- fixed opening special files\/urls in a designated window\r\n- fixed highlighting of comments\r\n- vikiLowerCharacters and vikiUpperCharacters can be buffer local\r\n- fixed problem when an url contained an ampersand\r\n- fixed error message when the &hidden option wasn't set (see g:vikiHide)\r\n","3":"- g:vikiHomePage: If you call VikiEdit! (with \"bang\"), the homepage is opened \r\nfirst so that its customizations are in effect. Also, if you call :VikiHome or \r\n:VikiEdit *, the homepage is opened.\r\n- basic highlighting & indentation of emacs-planner style task lists (sort of)\r\n- command line completion for :VikiEdit\r\n- new command\/function VikiDefine for defining intervikis\r\n- added <LocalLeader>ve map for :VikiEdit\r\n- fixed problem in VikiEdit (when the cursor was on a valid viki link, the \r\ntext argument was ignored)\r\n- fixed opening special files\/urls in a designated window\r\n- fixed highlighting of comments\r\n- vikiLowerCharacters and vikiUpperCharacters can be buffer local\r\n- fixed problem when an url contained an ampersand\r\n- fixed error message when the &hidden option wasn't set (see g:vikiHide)\r\n","package":"Viki.zip","4":"Viki.zip","src_id":"4710","5":"4710","creation_date":"1130734759","6":"1130734759"},{"0":"861","vim_version":"6.0","1":"6.0","script_version":"1.6.3","2":"1.6.3","version_comment":"- file type URLs (file:\/\/) are now treated like special files\r\n- indent: if g:vikiIndentDesc is '::', align a definition's description to the \r\nfirst non-blank position after the '::' separator\r\n- b:vikiDisableType\r\n- Put AnyWord-related stuff into a file of its own.\r\n- indentation for notices (!!!, ??? etc.)\r\n- When creating a new file by following a link, the desired window number was ignored\r\n- (VikiOpenSpecialFile) Escape blanks in the filename\r\n- Set &include and &define (ftplugin)\r\n- Set g:vikiFolds to '' to avoid using Headings for folds (which may cause a \r\nmajor slowdown on slower machines)\r\n- renamed <SID>DecodeFileUrl(dest) to VikiDecomposeUrl()\r\n- fixed problem with table highlighting\r\n","3":"- file type URLs (file:\/\/) are now treated like special files\r\n- indent: if g:vikiIndentDesc is '::', align a definition's description to the \r\nfirst non-blank position after the '::' separator\r\n- b:vikiDisableType\r\n- Put AnyWord-related stuff into a file of its own.\r\n- indentation for notices (!!!, ??? etc.)\r\n- When creating a new file by following a link, the desired window number was ignored\r\n- (VikiOpenSpecialFile) Escape blanks in the filename\r\n- Set &include and &define (ftplugin)\r\n- Set g:vikiFolds to '' to avoid using Headings for folds (which may cause a \r\nmajor slowdown on slower machines)\r\n- renamed <SID>DecodeFileUrl(dest) to VikiDecomposeUrl()\r\n- fixed problem with table highlighting\r\n","package":"Viki.zip","4":"Viki.zip","src_id":"4640","5":"4640","creation_date":"1128125867","6":"1128125867"},{"0":"861","vim_version":"6.0","1":"6.0","script_version":"1.6.1","2":"1.6.1","version_comment":"- fixed indentation bug\r\n- removed forgotten debug message\r\n","3":"- fixed indentation bug\r\n- removed forgotten debug message\r\n","package":"Viki.zip","4":"Viki.zip","src_id":"3831","5":"3831","creation_date":"1107589973","6":"1107589973"},{"0":"861","vim_version":"6.0","1":"6.0","script_version":"1.6","2":"1.6","version_comment":"- new command: VikiEdit NAME ... allows editing of arbitrary viki names (also understands extended and interviki formats)\r\n- support for some regions\/commands\/macros: #INC\/#INCLUDE, #IMG, #Img (requires an id to be defined), {img}\r\n- b:vikiInverseFold: Inverse folding of subsections\r\n- g:vikiFreeMarker: Search for the plain anchor text if no explicitly marked anchor was found.\r\n- setting the b:vikiNoSimpleNames to true prevents viki from recognizing simple viki names\r\n- made some script local functions global so that it should be easier to integrate viki with other plugins\r\n- fixed moving cursor on <SID>VikiMarkInexistent()\r\n- fixed typo: b:VikiEnabled, which should be b:vikiEnabled (thanks to Ned Konz)\r\n","3":"- new command: VikiEdit NAME ... allows editing of arbitrary viki names (also understands extended and interviki formats)\r\n- support for some regions\/commands\/macros: #INC\/#INCLUDE, #IMG, #Img (requires an id to be defined), {img}\r\n- b:vikiInverseFold: Inverse folding of subsections\r\n- g:vikiFreeMarker: Search for the plain anchor text if no explicitly marked anchor was found.\r\n- setting the b:vikiNoSimpleNames to true prevents viki from recognizing simple viki names\r\n- made some script local functions global so that it should be easier to integrate viki with other plugins\r\n- fixed moving cursor on <SID>VikiMarkInexistent()\r\n- fixed typo: b:VikiEnabled, which should be b:vikiEnabled (thanks to Ned Konz)\r\n","package":"Viki.zip","4":"Viki.zip","src_id":"3798","5":"3798","creation_date":"1106688962","6":"1106688962"},{"0":"861","vim_version":"6.0","1":"6.0","script_version":"1.5.2","2":"1.5.2","version_comment":"- changed default markup of textstyles: __emphasize__, ''code''; the \r\nprevious markup can be re-enabled by setting g:vikiTextstylesVer to 1)\r\n- fixed problem with VikiQuote\r\n- on follow-link, check for yet unsaved buffers too\r\n","3":"- changed default markup of textstyles: __emphasize__, ''code''; the \r\nprevious markup can be re-enabled by setting g:vikiTextstylesVer to 1)\r\n- fixed problem with VikiQuote\r\n- on follow-link, check for yet unsaved buffers too\r\n","package":"Viki.zip","4":"Viki.zip","src_id":"3576","5":"3576","creation_date":"1098777067","6":"1098777067"},{"0":"861","vim_version":"6.0","1":"6.0","script_version":"1.5.1","2":"1.5.1","version_comment":"- depends on multvals >= 3.8.0\r\n- new viki family \"AnyWord\" (see |viki-any-word|), which turns any word into a \r\npotential viki link\r\n- <LocalLeader>vq, VikiQuote: mark selected text as a quoted viki name \r\n(requires imaps.vim, vimscript #244 or vimscript #475)\r\n- check for null links when pressing <space>, <cr>, ], and some other keys \r\n(defined in g:vikiMapKeys)\r\n- a global suffix for viki files can be defined by g:vikiNameSuffix\r\n- fix syntax problem when checking for links to inexistent files\r\n","3":"- depends on multvals >= 3.8.0\r\n- new viki family \"AnyWord\" (see |viki-any-word|), which turns any word into a \r\npotential viki link\r\n- <LocalLeader>vq, VikiQuote: mark selected text as a quoted viki name \r\n(requires imaps.vim, vimscript #244 or vimscript #475)\r\n- check for null links when pressing <space>, <cr>, ], and some other keys \r\n(defined in g:vikiMapKeys)\r\n- a global suffix for viki files can be defined by g:vikiNameSuffix\r\n- fix syntax problem when checking for links to inexistent files\r\n","package":"Viki.zip","4":"Viki.zip","src_id":"3492","5":"3492","creation_date":"1096279246","6":"1096279246"},{"0":"861","vim_version":"6.0","1":"6.0","script_version":"1.5","2":"1.5","version_comment":"- different highlighting for links to existing and non-existing files\r\n- added key bindings <LL>vs (split) and <LL>vv (split vertically)\r\n- added key bindings <LL>v1 through to <LL>v4: open the viki link \r\nunder cursor in the windows 1 to 4\r\n- handle variables g:vikiSplit, b:vikiSplit\r\n- don't indent regions\r\n- regions can be indented\r\n- When a file doesn't exist, ESC or \"n\" aborts creation\r\n","3":"- different highlighting for links to existing and non-existing files\r\n- added key bindings <LL>vs (split) and <LL>vv (split vertically)\r\n- added key bindings <LL>v1 through to <LL>v4: open the viki link \r\nunder cursor in the windows 1 to 4\r\n- handle variables g:vikiSplit, b:vikiSplit\r\n- don't indent regions\r\n- regions can be indented\r\n- When a file doesn't exist, ESC or \"n\" aborts creation\r\n","package":"Viki.zip","4":"Viki.zip","src_id":"3435","5":"3435","creation_date":"1094729179","6":"1094729179"},{"0":"861","vim_version":"6.0","1":"6.0","script_version":"1.4","2":"1.4","version_comment":"- fixed problem with table highlighting that could cause vim to hang\r\n- it is now possible to selectivly disable simple or quoted viki names\r\n- indent plugin\r\n","3":"- fixed problem with table highlighting that could cause vim to hang\r\n- it is now possible to selectivly disable simple or quoted viki names\r\n- indent plugin\r\n","package":"Viki.zip","4":"Viki.zip","src_id":"3358","5":"3358","creation_date":"1092963672","6":"1092963672"},{"0":"861","vim_version":"6.0","1":"6.0","script_version":"1.3.1","2":"1.3.1","version_comment":"- fixed bug when VikiGoBack was called without a definitiv back-reference (e.g. via <LocalLeader>vb)\r\n- fixed encoding problems with latin-1 characters\r\n","3":"- fixed bug when VikiGoBack was called without a definitiv back-reference (e.g. via <LocalLeader>vb)\r\n- fixed encoding problems with latin-1 characters\r\n","package":"Viki.zip","4":"Viki.zip","src_id":"3315","5":"3315","creation_date":"1092201242","6":"1092201242"},{"0":"861","vim_version":"6.0","1":"6.0","script_version":"1.3","2":"1.3","version_comment":"- basic ctags support (see |viki-tags|)\r\n- mini-ftplugin for bibtex files (use record labels as anchors)\r\n- added mapping <LocalLeader><c-cr>: follow link in other window (if any)\r\n- disabled the highlighting of italic char styles (i.e., \/text\/)\r\n- the ftplugin doesn't set deplate as the compiler; renamed the compiler plugin to deplate\r\n- fix: VikiFoldLevel()\r\n","3":"- basic ctags support (see |viki-tags|)\r\n- mini-ftplugin for bibtex files (use record labels as anchors)\r\n- added mapping <LocalLeader><c-cr>: follow link in other window (if any)\r\n- disabled the highlighting of italic char styles (i.e., \/text\/)\r\n- the ftplugin doesn't set deplate as the compiler; renamed the compiler plugin to deplate\r\n- fix: VikiFoldLevel()\r\n","package":"Viki.zip","4":"Viki.zip","src_id":"3304","5":"3304","creation_date":"1091772462","6":"1091772462"},{"0":"861","vim_version":"6.0","1":"6.0","script_version":"1.2.103","2":"1.2.103","version_comment":"- syntax file: fix nested regexp problem\r\n- deplate: conversion to html\/latex; download from \r\nhttp:\/\/sourceforge.net\/projects\/deplate\/\r\n- made syntax a little bit more restrictive (*WORD* now matches \/\\*\\w+\\*\/ instead of \/\\*\\S+\\*\/)\r\n- interviki definitions can now be buffer local variables, too\r\n- fixed <SID>DecodeFileUrl(dest)\r\n- some kind of compiler plugin (uses deplate)\r\n- removed g\/b:vikiMarkupEndsWithNewline variable\r\n- saved all files in unix format (thanks to Grant Bowman for the hint)\r\n- removed international characters from g:vikiLowerCharacters and \r\ng:vikiUpperCharacters because of difficulties with different encodings (thanks to Grant Bowman for pointing out this problem); non-english-speaking users have to set these variables in their vimrc file\r\n- g:vikiExplorer (for viewing directories)\r\n- preliminary support for \"soft\" anchors (b:vikiAnchorRx)\r\n- improved VikiOpenSpecialProtocol(url); g:vikiOpenUrlWith_{PROTOCOL}, \r\ng:vikiOpenUrlWith_ANY\r\n- improved VikiOpenSpecialFile(file); g:vikiOpenFileWith_{SUFFIX}, \r\ng:vikiOpenFileWith_ANY\r\n- anchors may contain upper characters (but must begin with a lower char)\r\n- some support for Mozilla ThunderBird mailbox-URLs (this requires spaces to be encoded as %20)\r\n- changed g:vikiDefSep to '\u00e2\u0080\u00a1\u00e2\u0080\u00a1\u00e2\u0080\u00a1'\r\n","3":"- syntax file: fix nested regexp problem\r\n- deplate: conversion to html\/latex; download from \r\nhttp:\/\/sourceforge.net\/projects\/deplate\/\r\n- made syntax a little bit more restrictive (*WORD* now matches \/\\*\\w+\\*\/ instead of \/\\*\\S+\\*\/)\r\n- interviki definitions can now be buffer local variables, too\r\n- fixed <SID>DecodeFileUrl(dest)\r\n- some kind of compiler plugin (uses deplate)\r\n- removed g\/b:vikiMarkupEndsWithNewline variable\r\n- saved all files in unix format (thanks to Grant Bowman for the hint)\r\n- removed international characters from g:vikiLowerCharacters and \r\ng:vikiUpperCharacters because of difficulties with different encodings (thanks to Grant Bowman for pointing out this problem); non-english-speaking users have to set these variables in their vimrc file\r\n- g:vikiExplorer (for viewing directories)\r\n- preliminary support for \"soft\" anchors (b:vikiAnchorRx)\r\n- improved VikiOpenSpecialProtocol(url); g:vikiOpenUrlWith_{PROTOCOL}, \r\ng:vikiOpenUrlWith_ANY\r\n- improved VikiOpenSpecialFile(file); g:vikiOpenFileWith_{SUFFIX}, \r\ng:vikiOpenFileWith_ANY\r\n- anchors may contain upper characters (but must begin with a lower char)\r\n- some support for Mozilla ThunderBird mailbox-URLs (this requires spaces to be encoded as %20)\r\n- changed g:vikiDefSep to '\u00e2\u0080\u00a1\u00e2\u0080\u00a1\u00e2\u0080\u00a1'\r\n","package":"Viki.zip","4":"Viki.zip","src_id":"2993","5":"2993","creation_date":"1083646564","6":"1083646564"},{"0":"861","vim_version":"6.0","1":"6.0","script_version":"1.0.5","2":"1.0.5","version_comment":"Bug fixes. This version should work now with g:vikiUseParentSuffix set to 0, which, well, is the default value.","3":"Bug fixes. This version should work now with g:vikiUseParentSuffix set to 0, which, well, is the default value.","package":"Viki.zip","4":"Viki.zip","src_id":"2723","5":"2723","creation_date":"1075943448","6":"1075943448"},{"0":"861","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"- \"Syntax\" changes\r\n- Extended names: For compatibility reasons with other wikis, the anchor is now in the reference part.\r\n- For compatibility reasons with other wikis, prepending an anchor with b:commentStart is optional.\r\n- g:vikiUseParentSuffix\r\n- Renamed variables & functions (basically s\/Wiki\/Viki\/g)\r\n- added a ftplugin stub, moved the description to a help file\r\n- \"[--]\" is reference to current file\r\n- Folding support (at section level)\r\n- \"Intervikis\"\r\n- More highlighting\r\n- g:vikiFamily, b:vikiFamily\r\n- VikiGoBack() (experimental option: persistent history data)\r\n- rudimentary LaTeX support (\"soft\" viki names)\r\n- removed call to \"simplify()\"","3":"- \"Syntax\" changes\r\n- Extended names: For compatibility reasons with other wikis, the anchor is now in the reference part.\r\n- For compatibility reasons with other wikis, prepending an anchor with b:commentStart is optional.\r\n- g:vikiUseParentSuffix\r\n- Renamed variables & functions (basically s\/Wiki\/Viki\/g)\r\n- added a ftplugin stub, moved the description to a help file\r\n- \"[--]\" is reference to current file\r\n- Folding support (at section level)\r\n- \"Intervikis\"\r\n- More highlighting\r\n- g:vikiFamily, b:vikiFamily\r\n- VikiGoBack() (experimental option: persistent history data)\r\n- rudimentary LaTeX support (\"soft\" viki names)\r\n- removed call to \"simplify()\"","package":"Viki.zip","4":"Viki.zip","src_id":"2705","5":"2705","creation_date":"1075631481","6":"1075631481"},{"0":"861","vim_version":"6.0","1":"6.0","script_version":"380","2":"380","version_comment":"Initial upload","3":"Initial upload","package":"Viki.vim","4":"Viki.vim","src_id":"2615","5":"2615","creation_date":"1071804849","6":"1071804849"}]},"860":{"script_id":"860","0":"860","script_name":"inform.vim","1":"inform.vim","script_type":"indent","2":"indent","summary":"Indenting for Inform","3":"Indenting for Inform","description":"Just your basic indent script. Works fairly well in most circumstances, though the odd issue still exists with multi-line conditions, and object definitions may not come out as you like them to.\r\n\r\nIncludes a rudimentary ftplugin script.","4":"Just your basic indent script. Works fairly well in most circumstances, though the odd issue still exists with multi-line conditions, and object definitions may not come out as you like them to.\r\n\r\nIncludes a rudimentary ftplugin script.","install_details":"See the included README file (or, in fact, your Vim manual) for installation instructions.","5":"See the included README file (or, in fact, your Vim manual) for installation instructions.","first_name":"Martin","6":"Martin","last_name":"Bays","7":"Bays","releases":[{"0":"860","vim_version":"6.0","1":"6.0","script_version":"0.5","2":"0.5","version_comment":"Initial upload","3":"Initial upload","package":"informindent.tgz","4":"informindent.tgz","src_id":"2606","5":"2606","creation_date":"1071659204","6":"1071659204"}]},"859":{"script_id":"859","0":"859","script_name":"Destructive Paste","1":"Destructive Paste","script_type":"utility","2":"utility","summary":"Pastes the register, replacing text","3":"Pastes the register, replacing text","description":"[register]<Leader>Dp  - destructively pastes the register after the cursor, includes destructive paste of vertical blocks.\r\n\r\n[register]<Leader>DP - destructively pastes before the cursor.","4":"[register]<Leader>Dp  - destructively pastes the register after the cursor, includes destructive paste of vertical blocks.\r\n\r\n[register]<Leader>DP - destructively pastes before the cursor.","install_details":"Install as a plugin.","5":"Install as a plugin.","first_name":"Michael","6":"Michael","last_name":"Geddes","7":"Geddes","releases":[{"0":"859","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"destpaste.vim","4":"destpaste.vim","src_id":"2601","5":"2601","creation_date":"1071514638","6":"1071514638"}]},"858":{"script_id":"858","0":"858","script_name":"LocateOpen","1":"LocateOpen","script_type":"utility","2":"utility","summary":"Open files without having to supply a path","3":"Open files without having to supply a path","description":"This script is now being maintained by user \"yokomizor\" on Github. See https:\/\/github.com\/yokomizor\/LocateOpen for updates.\r\n\r\nThis script uses slocate (or a similar application) to allow the user to open a file without having to enter a path. If multiple files are found the user is given the choice of which file to open.\r\n\r\nUsage:\r\n\r\n:LocateEdit somefile.txt\r\n:LocateSplit somefile.txt\r\n:LocateSource somefile.vim\r\n:LocateRead somefile.txt\r\n\r\nOptions:\r\n\r\nTo enable case insensitive mode:\r\n:let g:locateopen_ignorecase = 1\r\n\r\nTo disable smart case mode:\r\n:let g:locateopen_smartcase = 0\r\n\r\nTo enable always prompt mode:\r\n:let g:locateopen_alwaysprompt = 1\r\n\r\nRequirements:\r\n\r\nYou need 'slocate' or a similar application. This probably means that you need to be on Linux, or possibly another Unix-like OS. Most Linux distributions seem to ship with slocate by default, so this probably isn't a problem. This script will almost certainly not work on Windows, sorry.\r\n\r\nAn up-to-date locate database helps, too. If you find that this script gives out of date information (eg doesn't list some files or still shows old files), you may want to consider putting updatedb on a cron...\r\n\r\nFinally, I've not tested on Vim below 6.2.\r\n\r\nPossible Todo List:\r\n\r\n* Help document\r\n* Less inefficient 'array' handling","4":"This script is now being maintained by user \"yokomizor\" on Github. See https:\/\/github.com\/yokomizor\/LocateOpen for updates.\r\n\r\nThis script uses slocate (or a similar application) to allow the user to open a file without having to enter a path. If multiple files are found the user is given the choice of which file to open.\r\n\r\nUsage:\r\n\r\n:LocateEdit somefile.txt\r\n:LocateSplit somefile.txt\r\n:LocateSource somefile.vim\r\n:LocateRead somefile.txt\r\n\r\nOptions:\r\n\r\nTo enable case insensitive mode:\r\n:let g:locateopen_ignorecase = 1\r\n\r\nTo disable smart case mode:\r\n:let g:locateopen_smartcase = 0\r\n\r\nTo enable always prompt mode:\r\n:let g:locateopen_alwaysprompt = 1\r\n\r\nRequirements:\r\n\r\nYou need 'slocate' or a similar application. This probably means that you need to be on Linux, or possibly another Unix-like OS. Most Linux distributions seem to ship with slocate by default, so this probably isn't a problem. This script will almost certainly not work on Windows, sorry.\r\n\r\nAn up-to-date locate database helps, too. If you find that this script gives out of date information (eg doesn't list some files or still shows old files), you may want to consider putting updatedb on a cron...\r\n\r\nFinally, I've not tested on Vim below 6.2.\r\n\r\nPossible Todo List:\r\n\r\n* Help document\r\n* Less inefficient 'array' handling","install_details":"Install the .vim file to ~\/.vim\/plugins\/ or your global plugins directory. No post-install configuration should be required, although you may want to edit the script if your distribution uses a strange locate version...","5":"Install the .vim file to ~\/.vim\/plugins\/ or your global plugins directory. No post-install configuration should be required, although you may want to edit the script if your distribution uses a strange locate version...","first_name":"Ciaran","6":"Ciaran","last_name":"McCreesh","7":"McCreesh","releases":[{"0":"858","vim_version":"6.0","1":"6.0","script_version":"1.3","2":"1.3","version_comment":"Fix rlocate support.","3":"Fix rlocate support.","package":"locateopen.vim","4":"locateopen.vim","src_id":"4978","5":"4978","creation_date":"1137426095","6":"1137426095"},{"0":"858","vim_version":"6.0","1":"6.0","script_version":"1.1","2":"1.1","version_comment":"Added :LocateRead","3":"Added :LocateRead","package":"locateopen.vim","4":"locateopen.vim","src_id":"3759","5":"3759","creation_date":"1105441528","6":"1105441528"},{"0":"858","vim_version":"6.0","1":"6.0","script_version":"0.8.0","2":"0.8.0","version_comment":"* smart case mode\r\n* always prompt mode\r\n* :LocateSource","3":"* smart case mode\r\n* always prompt mode\r\n* :LocateSource","package":"locateopen.vim","4":"locateopen.vim","src_id":"2661","5":"2661","creation_date":"1074003727","6":"1074003727"},{"0":"858","vim_version":"6.0","1":"6.0","script_version":"0.6.2","2":"0.6.2","version_comment":"Added case insensitive mode","3":"Added case insensitive mode","package":"locateopen.vim","4":"locateopen.vim","src_id":"2614","5":"2614","creation_date":"1071767770","6":"1071767770"},{"0":"858","vim_version":"6.0","1":"6.0","script_version":"0.6.1","2":"0.6.1","version_comment":"Initial upload","3":"Initial upload","package":"locateopen.vim","4":"locateopen.vim","src_id":"2595","5":"2595","creation_date":"1071423232","6":"1071423232"}]},"857":{"script_id":"857","0":"857","script_name":"table_format.vim","1":"table_format.vim","script_type":"utility","2":"utility","summary":"Formatting utility to arrange text into neat columns","3":"Formatting utility to arrange text into neat columns","description":"The plugin script table_format.vim is a text formatting tool.  It\r\narranges words or groups of words on consecutive lines into a neatly\r\nformatted table.\r\n\r\nThere are two keyboard shortcuts defined: \\t and \\T.  Each work\r\nslightly differently.\r\n\r\n- \\t (lowercase 't') is referred to as a mode 0 table command.  This\r\n  means that words separated by a single space are arranged into\r\n  columns padded with one or more spaces.\r\n\r\n- \\T (uppercase 'T') is referred to as a mode 1 table command.  Here\r\n  fields consist of groups of words separated by one space.  The field\r\n  boundaries are sequences of two or more spaces.  After formatting\r\n  into a table, the padding between fields (groups of words) is three\r\n  of more spaces.\r\n\r\n- The \\t and \\T (specifically <Leader>t and <Leader>T) mappings exist\r\n  for normal and visual mode.  In normal mode the range to be made\r\n  into a table is from the current line (cursor position) until the\r\n  next paragraph break (ie blank line).\r\n\r\n- For visual mode table formatting works for both linewise visual and\r\n  blockwise visual modes.  First highlight the text in visual mode\r\n  with 'V' then movement (linewise visual) or '<c-v>' or '<c-q> then\r\n  movement (blockwise visual) and then type <Leader>t or <Leader>T (ie\r\n  \\t or \\T)\r\n\r\n- The \\t and \\T mappings utilize the vim mapleader variable.  For\r\n  example, if mapleader=',', then the mappings in table_format.vim are\r\n  ,t and ,T\r\n\r\n- The one-space\/one-padding for mode 0 and two-space\/three-padding for\r\n  mode 1 are defaults and can be overridden.\r\n\r\n- The internal table formatting functions can be called directly:\r\n\r\n    :[range]call Table(space_split, space_padding, max_field_length,\r\n        col_start, col_end)\r\n\r\n  All of the parameters are optional.\r\n\r\n    space_split\r\n        - The number of consecutive spaces that indicate a column\r\n          boundary\r\n        - default: 1\r\n\r\n    space_padding\r\n        - The minimum number of spaces that are placed in between\r\n          fields after formatting to make a column boundary.\r\n        - default: 1\r\n\r\n    max_field_length\r\n        - The maximum length of a field (word or group of words).  A\r\n          value of 0 (the default) means that a field can be any\r\n          length\r\n        - default: 0\r\n\r\n    col_start\r\n        - The beginning column position for formatting.  A value of 0\r\n          (the default) means to start at the beginning of the line.\r\n        - default: 0\r\n\r\n    col_end\r\n        - The end column position for formatting.  A value of 0 (the\r\n          default) means to format through the end of the line.\r\n        - default: 0\r\n\r\n    There is an alternate version of the above function where the\r\n    range can be passed in directly:\r\n\r\n    :call TableRange(firstline, lastline, space_split, space_padding,\r\n        max_field_length, col_start, col_end)\r\n","4":"The plugin script table_format.vim is a text formatting tool.  It\r\narranges words or groups of words on consecutive lines into a neatly\r\nformatted table.\r\n\r\nThere are two keyboard shortcuts defined: \\t and \\T.  Each work\r\nslightly differently.\r\n\r\n- \\t (lowercase 't') is referred to as a mode 0 table command.  This\r\n  means that words separated by a single space are arranged into\r\n  columns padded with one or more spaces.\r\n\r\n- \\T (uppercase 'T') is referred to as a mode 1 table command.  Here\r\n  fields consist of groups of words separated by one space.  The field\r\n  boundaries are sequences of two or more spaces.  After formatting\r\n  into a table, the padding between fields (groups of words) is three\r\n  of more spaces.\r\n\r\n- The \\t and \\T (specifically <Leader>t and <Leader>T) mappings exist\r\n  for normal and visual mode.  In normal mode the range to be made\r\n  into a table is from the current line (cursor position) until the\r\n  next paragraph break (ie blank line).\r\n\r\n- For visual mode table formatting works for both linewise visual and\r\n  blockwise visual modes.  First highlight the text in visual mode\r\n  with 'V' then movement (linewise visual) or '<c-v>' or '<c-q> then\r\n  movement (blockwise visual) and then type <Leader>t or <Leader>T (ie\r\n  \\t or \\T)\r\n\r\n- The \\t and \\T mappings utilize the vim mapleader variable.  For\r\n  example, if mapleader=',', then the mappings in table_format.vim are\r\n  ,t and ,T\r\n\r\n- The one-space\/one-padding for mode 0 and two-space\/three-padding for\r\n  mode 1 are defaults and can be overridden.\r\n\r\n- The internal table formatting functions can be called directly:\r\n\r\n    :[range]call Table(space_split, space_padding, max_field_length,\r\n        col_start, col_end)\r\n\r\n  All of the parameters are optional.\r\n\r\n    space_split\r\n        - The number of consecutive spaces that indicate a column\r\n          boundary\r\n        - default: 1\r\n\r\n    space_padding\r\n        - The minimum number of spaces that are placed in between\r\n          fields after formatting to make a column boundary.\r\n        - default: 1\r\n\r\n    max_field_length\r\n        - The maximum length of a field (word or group of words).  A\r\n          value of 0 (the default) means that a field can be any\r\n          length\r\n        - default: 0\r\n\r\n    col_start\r\n        - The beginning column position for formatting.  A value of 0\r\n          (the default) means to start at the beginning of the line.\r\n        - default: 0\r\n\r\n    col_end\r\n        - The end column position for formatting.  A value of 0 (the\r\n          default) means to format through the end of the line.\r\n        - default: 0\r\n\r\n    There is an alternate version of the above function where the\r\n    range can be passed in directly:\r\n\r\n    :call TableRange(firstline, lastline, space_split, space_padding,\r\n        max_field_length, col_start, col_end)\r\n","install_details":"To install place table_format.vim into your vim plugin directory.\r\n","5":"To install place table_format.vim into your vim plugin directory.\r\n","first_name":"Michael","6":"Michael","last_name":"Graz","7":"Graz","releases":[{"0":"857","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"table_format.vim","4":"table_format.vim","src_id":"2594","5":"2594","creation_date":"1071422427","6":"1071422427"}]},"856":{"script_id":"856","0":"856","script_name":"NSIS 2.0+ Syntax","1":"NSIS 2.0+ Syntax","script_type":"syntax","2":"syntax","summary":"Syntax highlighting for NSIS 2.0 and above","3":"Syntax highlighting for NSIS 2.0 and above","description":"Syntax highlighting for NSIS 2.0 and above, which added many new instructions and attributes since the 1.x tree, not supported by the previous scripts.","4":"Syntax highlighting for NSIS 2.0 and above, which added many new instructions and attributes since the 1.x tree, not supported by the previous scripts.","install_details":"Drop it in your syntax folder, and overwrite your existing nsis.vim.","5":"Drop it in your syntax folder, and overwrite your existing nsis.vim.","first_name":"Scott","6":"Scott","last_name":"Barker","7":"Barker","releases":[{"0":"856","vim_version":"6.0","1":"6.0","script_version":"1.3","2":"1.3","version_comment":"1.3:\r\n-\tAdded:\r\nDirVerify, UninstPage, GetInstDirError\r\n","3":"1.3:\r\n-\tAdded:\r\nDirVerify, UninstPage, GetInstDirError\r\n","package":"nsis.vim","4":"nsis.vim","src_id":"2591","5":"2591","creation_date":"1071383774","6":"1071383774"},{"0":"856","vim_version":"6.0","1":"6.0","script_version":"1.1","2":"1.1","version_comment":"1.1:\t\r\n-\tAdded:\r\nNop, LangString, SetBrandingImage, the \/a switch for File, the \/e switch for SubSection,\r\nthe \/o switch for Section, $PLUGINSDIR, !ifmacrodef, !ifmacrondef, IDD_LICENSE_FSRB, IDD_LICENSE_FSCB,\r\nthe \/FINAL switch for SetCompressor and the \/SD switch for MessageBox.\r\n-\tChanged:\r\nInitPluginsDir, IfSilent, CreateFont and SetCtlColors are not attributes, they're commands.\r\nEnabledBitmap and DisabledBitmap are obselete.\r\nLoadLanguageFile is an instruction, it's... hmm... atrribute?\r\nUninstaller now has un.onMouseOverSection and un.onSelChange too.\r\nThere is no un.onInstSuccess and un.onInstFailed, it's un.onUninstSuccess and un.onUninstFailed.","3":"1.1:\t\r\n-\tAdded:\r\nNop, LangString, SetBrandingImage, the \/a switch for File, the \/e switch for SubSection,\r\nthe \/o switch for Section, $PLUGINSDIR, !ifmacrodef, !ifmacrondef, IDD_LICENSE_FSRB, IDD_LICENSE_FSCB,\r\nthe \/FINAL switch for SetCompressor and the \/SD switch for MessageBox.\r\n-\tChanged:\r\nInitPluginsDir, IfSilent, CreateFont and SetCtlColors are not attributes, they're commands.\r\nEnabledBitmap and DisabledBitmap are obselete.\r\nLoadLanguageFile is an instruction, it's... hmm... atrribute?\r\nUninstaller now has un.onMouseOverSection and un.onSelChange too.\r\nThere is no un.onInstSuccess and un.onInstFailed, it's un.onUninstSuccess and un.onUninstFailed.","package":"nsis.vim","4":"nsis.vim","src_id":"2590","5":"2590","creation_date":"1071377546","6":"1071377546"},{"0":"856","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"nsis.vim","4":"nsis.vim","src_id":"2589","5":"2589","creation_date":"1071281619","6":"1071281619"}]},"855":{"script_id":"855","0":"855","script_name":"FX HLSL","1":"FX HLSL","script_type":"syntax","2":"syntax","summary":"Syntax Rules for Microsoft HLSL and FX files","3":"Syntax Rules for Microsoft HLSL and FX files","description":"These rules provide syntax hilighting and a set of useful \"iabbrev\" macros for use when writing HLSL (High Level Shading Language) code for DirectX 9 and above. File types includ e.hlsl and .fx -- the abbreviations are provided to reate template declarations for various tweakable data types in FX, including floats, float vectors, matrices, textures and samplers, render passes, etc. They are found defined at the end of the file.\r\n\r\nFinally, the shiftwidth is set to 4 to match common shading-language editing tools such as the defaults for Visual Studio.NET and NVIDIA FX Composer.","4":"These rules provide syntax hilighting and a set of useful \"iabbrev\" macros for use when writing HLSL (High Level Shading Language) code for DirectX 9 and above. File types includ e.hlsl and .fx -- the abbreviations are provided to reate template declarations for various tweakable data types in FX, including floats, float vectors, matrices, textures and samplers, render passes, etc. They are found defined at the end of the file.\r\n\r\nFinally, the shiftwidth is set to 4 to match common shading-language editing tools such as the defaults for Visual Studio.NET and NVIDIA FX Composer.","install_details":"Install in \"syntax\" and set automated application rules as normal. I suggest trapping files with extensions .hlsl .fx and .fxh","5":"Install in \"syntax\" and set automated application rules as normal. I suggest trapping files with extensions .hlsl .fx and .fxh","first_name":"Kevin","6":"Kevin","last_name":"Bjorke","7":"Bjorke","releases":[{"0":"855","vim_version":"6.0","1":"6.0","script_version":"1","2":"1","version_comment":"Initial upload","3":"Initial upload","package":"fx.vim","4":"fx.vim","src_id":"2587","5":"2587","creation_date":"1071235697","6":"1071235697"}]},"854":{"script_id":"854","0":"854","script_name":"less.vim","1":"less.vim","script_type":"color scheme","2":"color scheme","summary":"Less is More - A minimal color scheme","3":"Less is More - A minimal color scheme","description":"Less is More: A minimal color scheme.\r\n\r\nSet on a Black background w\/ LightGray as normal text. Similar to a typical unix console.  Designed to work equally well on 8 or 16 colors, terminal or gui. \r\n\r\nBased on Jeff Solomon's highlights @ http:\/\/www-vlsi.stanford.edu\/~jsolomon\/vim\/\r\nCheck out his syntax files. Nice improvements for C, Perl, Tcl, and others.","4":"Less is More: A minimal color scheme.\r\n\r\nSet on a Black background w\/ LightGray as normal text. Similar to a typical unix console.  Designed to work equally well on 8 or 16 colors, terminal or gui. \r\n\r\nBased on Jeff Solomon's highlights @ http:\/\/www-vlsi.stanford.edu\/~jsolomon\/vim\/\r\nCheck out his syntax files. Nice improvements for C, Perl, Tcl, and others.","install_details":"~\/.vim\/colors\/less.vim\r\n:colorscheme less","5":"~\/.vim\/colors\/less.vim\r\n:colorscheme less","first_name":"Brian","6":"Brian","last_name":"Nelson","7":"Nelson","releases":[{"0":"854","vim_version":"6.0","1":"6.0","script_version":"1.1","2":"1.1","version_comment":"update email","3":"update email","package":"less.vim","4":"less.vim","src_id":"3715","5":"3715","creation_date":"1103552234","6":"1103552234"}]},"853":{"script_id":"853","0":"853","script_name":"File-local variables","1":"File-local variables","script_type":"utility","2":"utility","summary":"Set\/let per-file-variables \u00c3\u00a0 la Emacs","3":"Set\/let per-file-variables \u00c3\u00a0 la Emacs","description":"This plugin tries to mimic Emacs's file local variables feature. File local \r\nvariables are kept in a section in the last g:localVariablesRange \r\n(default=30) lines of a file (this variable also defines the maximum number \r\nof file local variables). E.g., in this example >\r\n\r\n    Local Variables:\r\n    foo:1\r\n    bar:\"bla\"\r\n    End:\r\n\r\nthe variable b:foo will be set to \"1\" (which, in vim, equals 1), b:bar \r\nto \"bla\" after opening the file.\r\n\r\nThe beginning of the section is marked with g:localVariablesBegText \r\n(default=\"Local Variables:\"), the end with g:localVariablesEndText \r\n(default=\"End:\"). These markers can be surrounded by arbitrary prefix and \r\nsuffix markers. These (optional) prefixes and suffixes must be consistent for \r\nthe whole section. The prefix and suffix are defined by the end-marker. \r\nExample: >\r\n\r\n    ### Local Variables: ###\r\n    ### foo:1 ###\r\n    ### bar:\"bla\" ###\r\n    ### End: ###\r\n<\r\n                                                    *g:localVariablesDownCaseHyphenedNames*\r\n                                                    *localvariables-hyphens*\r\nIf a variable name contains a hyphen (\"-\"), the variable name will be \r\ntranslated into a buffer local variable in camel case, i.e. \"comment-start\" \r\nbecomes \"b:commentStart\". A hyphendized variable's scope is always \"b\". If \r\ng:localVariablesDownCaseHyphenedNames (default=1) is true, then the variable \r\nname will be downcased first for compatibility reasons -- as (emacs) lisp is \r\ncase insensitive. I.e., \"COMMENT-START\" becomes \"b:commentStart\", too.\r\n\r\n\r\n                                                    *localvariables-values*\r\nA small note on value handling: For security reasons, all normal values \r\n(i.e., anything but |localvariables-special|) are put in quotes unless \r\nthe value already matches \"^\\\\([\\\"']\\\\)[^\\\"]*\\\\1$\".\r\n\r\n\r\n                                                    *localvariables-transpose*\r\nIn order to be \"compatible\" with, e.g, Emacs's file local variables, it might be \r\nnecessary to translate some variable names.\r\n\r\nYou can use also variables with the prefix \"g:localVariableX\" for \r\ntranslating variable names without scope definitions. Example: >\r\n\r\n    let g:localVariableXtabWidth = \"&tabstop\"\r\n    ---\r\n    ### Local Variables: ###\r\n    ### tab-width:4 ###\r\n    ### End: ###\r\n\r\nThis would set the buffer-local option |tabstop| to 4. (Which could of course \r\nbe achieved with a vim line, too.)\r\n\r\nAs an alternative, you can also define a function with the prefix \r\n\"LocalVariableX\" which will be called with the value as single argument.  \r\nThis provides a controlled way for executing commands when loading\/editing \r\na file. By defining a function \"LocalVariableXmode\", this can be used to \r\nreuse Emacs's mode annotations for files that don't match the usual file \r\npatterns. Example: >\r\n\r\n    fun! LocalVariableXfoo(arg)\r\n        if a:arg == \"0\"\r\n            GoFoo\r\n        elseif a:arg == \"1\"\r\n            GoBar\r\n        endif\r\n    endfun\r\n    ---\r\n    ### Local Variables: ###\r\n    ### foo:0 ###\r\n    ### End: ###\r\n\r\nThis example would execute GoFoo or GoBar depending on the value of the file \r\nlocal variable foo.\r\n\r\n\r\n                                                    *localvariables-definition*\r\nA variable definition has the form (as regexp): >\r\n\r\n\t((scope char:)?(variable|special name)|hyphened name):value\r\n\r\nIf no scope character is given, the variable is buffer local (\"b\"-scope).\r\n\r\nIf the scope character is \"&\", |setlocal| will be used to set the variable.\r\n\r\n                                                      *localvariables-special*\r\nIf the scope is \":\", the variable name is interpreted as a special name:\r\n\r\n                                                      *localvariables-execute*\r\n- execute: The value of s:localVariablesAllowExec can't be changed by this \r\n  script. (The first 4 letters of \"execute\" are essential.)\r\n\r\n                                                      *localvariables-events*\r\n                                                      *LocalVariablesRegisterHook*\r\n- On{event}: The value is registered for execution when the denoted \r\n  autocommand event occurs. You have to register LocalVariables for use with \r\n  this event by using the command >\r\n\r\n  \t:LocalVariablesRegisterHook EVENT\r\n<\r\n  Use this feature, e.g., for recompiling some files after saving.\r\n\r\n                                                      *s:localVariablesAllowExec*\r\nThe value of s:localVariablesAllowExec (default=1) defines if the execution \r\nof special variables is allowed. Values: >\r\n\r\n\t0 ... disable\r\n\t1 ... query user, default = no\r\n\t2 ... query user, default = yes\r\n\t3 ... allow\r\n\r\nNOTE: You most likely have to edit the plugin to change this variable.\r\n\r\nNOTE: A change from 0 to [1-3] takes effect only after reloading the plugin!\r\n\r\nNOTE: |input()| appears to make problems when opening a file - vim (6.2) \r\nappears to hang. When a gui is running, use |inputdialog()| for querying \r\nthe user. I don't know if |input()| works on a terminal.\r\n\r\n                                                      *localvariables-security-risks*\r\nCAVEAT: Be aware that \"special values\" are evaluated with |execute|.  \r\nThis potentially pushes vim ahead in the era of computer viruses\/worms. \r\nTake care.\r\n\r\nExample:\r\nExecute >\r\n\r\n\tLocalVariablesRegisterHook! BufWritePre\r\n\t\r\nand put something like this at the end of a file: >\r\n\r\n\t### Local Variables: ###\r\n\t### b:variable1:1 ###\r\n\t### g:variable2:\"2\" ###\r\n\t### variable3:\"three\" ###\r\n\t### tab-width:4 ###\r\n\t### ::exec:echo \"Got it!\" ###\r\n\t### ::OnBufWritePre:call inputdialog(\"You shouldn't have written this text\") ###\r\n\t### End: ###\r\n","4":"This plugin tries to mimic Emacs's file local variables feature. File local \r\nvariables are kept in a section in the last g:localVariablesRange \r\n(default=30) lines of a file (this variable also defines the maximum number \r\nof file local variables). E.g., in this example >\r\n\r\n    Local Variables:\r\n    foo:1\r\n    bar:\"bla\"\r\n    End:\r\n\r\nthe variable b:foo will be set to \"1\" (which, in vim, equals 1), b:bar \r\nto \"bla\" after opening the file.\r\n\r\nThe beginning of the section is marked with g:localVariablesBegText \r\n(default=\"Local Variables:\"), the end with g:localVariablesEndText \r\n(default=\"End:\"). These markers can be surrounded by arbitrary prefix and \r\nsuffix markers. These (optional) prefixes and suffixes must be consistent for \r\nthe whole section. The prefix and suffix are defined by the end-marker. \r\nExample: >\r\n\r\n    ### Local Variables: ###\r\n    ### foo:1 ###\r\n    ### bar:\"bla\" ###\r\n    ### End: ###\r\n<\r\n                                                    *g:localVariablesDownCaseHyphenedNames*\r\n                                                    *localvariables-hyphens*\r\nIf a variable name contains a hyphen (\"-\"), the variable name will be \r\ntranslated into a buffer local variable in camel case, i.e. \"comment-start\" \r\nbecomes \"b:commentStart\". A hyphendized variable's scope is always \"b\". If \r\ng:localVariablesDownCaseHyphenedNames (default=1) is true, then the variable \r\nname will be downcased first for compatibility reasons -- as (emacs) lisp is \r\ncase insensitive. I.e., \"COMMENT-START\" becomes \"b:commentStart\", too.\r\n\r\n\r\n                                                    *localvariables-values*\r\nA small note on value handling: For security reasons, all normal values \r\n(i.e., anything but |localvariables-special|) are put in quotes unless \r\nthe value already matches \"^\\\\([\\\"']\\\\)[^\\\"]*\\\\1$\".\r\n\r\n\r\n                                                    *localvariables-transpose*\r\nIn order to be \"compatible\" with, e.g, Emacs's file local variables, it might be \r\nnecessary to translate some variable names.\r\n\r\nYou can use also variables with the prefix \"g:localVariableX\" for \r\ntranslating variable names without scope definitions. Example: >\r\n\r\n    let g:localVariableXtabWidth = \"&tabstop\"\r\n    ---\r\n    ### Local Variables: ###\r\n    ### tab-width:4 ###\r\n    ### End: ###\r\n\r\nThis would set the buffer-local option |tabstop| to 4. (Which could of course \r\nbe achieved with a vim line, too.)\r\n\r\nAs an alternative, you can also define a function with the prefix \r\n\"LocalVariableX\" which will be called with the value as single argument.  \r\nThis provides a controlled way for executing commands when loading\/editing \r\na file. By defining a function \"LocalVariableXmode\", this can be used to \r\nreuse Emacs's mode annotations for files that don't match the usual file \r\npatterns. Example: >\r\n\r\n    fun! LocalVariableXfoo(arg)\r\n        if a:arg == \"0\"\r\n            GoFoo\r\n        elseif a:arg == \"1\"\r\n            GoBar\r\n        endif\r\n    endfun\r\n    ---\r\n    ### Local Variables: ###\r\n    ### foo:0 ###\r\n    ### End: ###\r\n\r\nThis example would execute GoFoo or GoBar depending on the value of the file \r\nlocal variable foo.\r\n\r\n\r\n                                                    *localvariables-definition*\r\nA variable definition has the form (as regexp): >\r\n\r\n\t((scope char:)?(variable|special name)|hyphened name):value\r\n\r\nIf no scope character is given, the variable is buffer local (\"b\"-scope).\r\n\r\nIf the scope character is \"&\", |setlocal| will be used to set the variable.\r\n\r\n                                                      *localvariables-special*\r\nIf the scope is \":\", the variable name is interpreted as a special name:\r\n\r\n                                                      *localvariables-execute*\r\n- execute: The value of s:localVariablesAllowExec can't be changed by this \r\n  script. (The first 4 letters of \"execute\" are essential.)\r\n\r\n                                                      *localvariables-events*\r\n                                                      *LocalVariablesRegisterHook*\r\n- On{event}: The value is registered for execution when the denoted \r\n  autocommand event occurs. You have to register LocalVariables for use with \r\n  this event by using the command >\r\n\r\n  \t:LocalVariablesRegisterHook EVENT\r\n<\r\n  Use this feature, e.g., for recompiling some files after saving.\r\n\r\n                                                      *s:localVariablesAllowExec*\r\nThe value of s:localVariablesAllowExec (default=1) defines if the execution \r\nof special variables is allowed. Values: >\r\n\r\n\t0 ... disable\r\n\t1 ... query user, default = no\r\n\t2 ... query user, default = yes\r\n\t3 ... allow\r\n\r\nNOTE: You most likely have to edit the plugin to change this variable.\r\n\r\nNOTE: A change from 0 to [1-3] takes effect only after reloading the plugin!\r\n\r\nNOTE: |input()| appears to make problems when opening a file - vim (6.2) \r\nappears to hang. When a gui is running, use |inputdialog()| for querying \r\nthe user. I don't know if |input()| works on a terminal.\r\n\r\n                                                      *localvariables-security-risks*\r\nCAVEAT: Be aware that \"special values\" are evaluated with |execute|.  \r\nThis potentially pushes vim ahead in the era of computer viruses\/worms. \r\nTake care.\r\n\r\nExample:\r\nExecute >\r\n\r\n\tLocalVariablesRegisterHook! BufWritePre\r\n\t\r\nand put something like this at the end of a file: >\r\n\r\n\t### Local Variables: ###\r\n\t### b:variable1:1 ###\r\n\t### g:variable2:\"2\" ###\r\n\t### variable3:\"three\" ###\r\n\t### tab-width:4 ###\r\n\t### ::exec:echo \"Got it!\" ###\r\n\t### ::OnBufWritePre:call inputdialog(\"You shouldn't have written this text\") ###\r\n\t### End: ###\r\n","install_details":"1. Extract the archive to your vimfiles directory. Run |helptags| on this directory.\r\n\r\n2. Insert something like this into your .vimrc: >\r\n\r\n\tautocmd BufReadPost * call LocalVariablesCheck()\r\n\t\r\nOr rather: >\r\n\r\n\tautocmd BufEnter    * call LocalVariablesCheck()\r\n\r\n3. Optionally, read |localvariables-security-risks| and register some events as in: >\r\n\r\n\tLocalVariablesRegisterHook! BufWritePre\r\n\r\nWhen calling LocalVariablesCheck(), the buffer will only be scanned once.  \r\nForce an re-evaluation of file local variables by calling \r\nLocalVariablesReCheck().\r\n\r\nAlso available via git\r\nhttp:\/\/github.com\/tomtom\/vimtlib\/tree\/master\r\n","5":"1. Extract the archive to your vimfiles directory. Run |helptags| on this directory.\r\n\r\n2. Insert something like this into your .vimrc: >\r\n\r\n\tautocmd BufReadPost * call LocalVariablesCheck()\r\n\t\r\nOr rather: >\r\n\r\n\tautocmd BufEnter    * call LocalVariablesCheck()\r\n\r\n3. Optionally, read |localvariables-security-risks| and register some events as in: >\r\n\r\n\tLocalVariablesRegisterHook! BufWritePre\r\n\r\nWhen calling LocalVariablesCheck(), the buffer will only be scanned once.  \r\nForce an re-evaluation of file local variables by calling \r\nLocalVariablesReCheck().\r\n\r\nAlso available via git\r\nhttp:\/\/github.com\/tomtom\/vimtlib\/tree\/master\r\n","first_name":"Tom","6":"Tom","last_name":"Link","7":"Link","releases":[{"0":"853","vim_version":"6.0","1":"6.0","script_version":"2.0","2":"2.0","version_comment":"Security fixes; support for autocmd events","3":"Security fixes; support for autocmd events","package":"localvariables.zip","4":"localvariables.zip","src_id":"2834","5":"2834","creation_date":"1079264170","6":"1079264170"},{"0":"853","vim_version":"6.0","1":"6.0","script_version":"183","2":"183","version_comment":"Bug fixes. You can now define a function of the name LocalVariableX{name} for translating variable names. This is useful for handling Emacs's \"mode\" pseudo-variable.","3":"Bug fixes. You can now define a function of the name LocalVariableX{name} for translating variable names. This is useful for handling Emacs's \"mode\" pseudo-variable.","package":"localvariables.vim","4":"localvariables.vim","src_id":"2616","5":"2616","creation_date":"1071805224","6":"1071805224"},{"0":"853","vim_version":"6.0","1":"6.0","script_version":"143","2":"143","version_comment":"Initial upload","3":"Initial upload","package":"localvariables.vim","4":"localvariables.vim","src_id":"2578","5":"2578","creation_date":"1070938511","6":"1070938511"}]},"852":{"script_id":"852","0":"852","script_name":"Gothic","1":"Gothic","script_type":"color scheme","2":"color scheme","summary":"Dark background and eye-resting colors","3":"Dark background and eye-resting colors","description":"Ideal color scheme for TFT users and long-hour users with dark background and eye-resting colors.\r\n\r\nSnapshot available at http:\/\/www.junglebit.net\/vim\/vimgothic.png","4":"Ideal color scheme for TFT users and long-hour users with dark background and eye-resting colors.\r\n\r\nSnapshot available at http:\/\/www.junglebit.net\/vim\/vimgothic.png","install_details":"Copy the script in the color folder of the vim installation directory (eg. \/usr\/share\/vim\/vim61\/colors)\r\n\r\nInsert the line \"colorscheme gothic\" to your ~\/.vimrc file or simply call \":colorscheme gothic\" from inside the Vim application\r\n","5":"Copy the script in the color folder of the vim installation directory (eg. \/usr\/share\/vim\/vim61\/colors)\r\n\r\nInsert the line \"colorscheme gothic\" to your ~\/.vimrc file or simply call \":colorscheme gothic\" from inside the Vim application\r\n","first_name":"Ste","6":"Ste","last_name":"Df","7":"Df","releases":[{"0":"852","vim_version":"6.0","1":"6.0","script_version":"2.0","2":"2.0","version_comment":"console fix and retouch of gui side","3":"console fix and retouch of gui side","package":"gothic.vim","4":"gothic.vim","src_id":"5958","5":"5958","creation_date":"1153005164","6":"1153005164"},{"0":"852","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Console Fix","3":"Console Fix","package":"gothic.vim","4":"gothic.vim","src_id":"2577","5":"2577","creation_date":"1070931564","6":"1070931564"}]},"851":{"script_id":"851","0":"851","script_name":"Posting","1":"Posting","script_type":"utility","2":"utility","summary":"Mappings primarily intended to ease preparing of USENET\/eMail articles","3":"Mappings primarily intended to ease preparing of USENET\/eMail articles","description":"\"Posting\" provides a few mappings I once messed around with in order to ease preparing USENET\/email articles with GVim. (Due to a malfunction at vim.org I had to register again. Earlier versions can be found at http:\/\/www.vim.org\/scripts\/script.php?script_id=487.)","4":"\"Posting\" provides a few mappings I once messed around with in order to ease preparing USENET\/email articles with GVim. (Due to a malfunction at vim.org I had to register again. Earlier versions can be found at http:\/\/www.vim.org\/scripts\/script.php?script_id=487.)","install_details":":source posting.vim \r\n:Post 72 \r\n","5":":source posting.vim \r\n:Post 72 \r\n","first_name":"Tim","6":"Tim","last_name":"Allen","7":"Allen","releases":[{"0":"851","vim_version":"6.0","1":"6.0","script_version":"1.4","2":"1.4","version_comment":"- Added paste command variants 'Footnoted' and 'Tabled'\r\n- Top-posting: Footnotes appear at the proper place now\r\n- <Cr> turns on Scan mode automatically\r\n- Zoom in\/out works for Lucida_Console too\r\n- Improved format=flowed support\r\n- Works for console Vim too now\r\n- Various minor changes (also bugfixes)\r\n","3":"- Added paste command variants 'Footnoted' and 'Tabled'\r\n- Top-posting: Footnotes appear at the proper place now\r\n- <Cr> turns on Scan mode automatically\r\n- Zoom in\/out works for Lucida_Console too\r\n- Improved format=flowed support\r\n- Works for console Vim too now\r\n- Various minor changes (also bugfixes)\r\n","package":"posting.vim","4":"posting.vim","src_id":"3173","5":"3173","creation_date":"1087884403","6":"1087884403"},{"0":"851","vim_version":"6.0","1":"6.0","script_version":"1.3","2":"1.3","version_comment":"Initial upload","3":"Initial upload","package":"posting.vim","4":"posting.vim","src_id":"2573","5":"2573","creation_date":"1070918113","6":"1070918113"}]},"850":{"script_id":"850","0":"850","script_name":"Pydiction","1":"Pydiction","script_type":"utility","2":"utility","summary":"Tab-complete your Python code","3":"Tab-complete your Python code","description":"Pydiction allows you to Tab-complete Python code in Vim such as keywords, built-ins, standard library, and third-party modules.\r\n\r\nFor the latest version of Pydiction and full documentation, see: http:\/\/rkulla.github.io\/pydiction\/\r\n\r\nIt doesn't require installing any dependencies. It simply consists of three files:\r\n\r\n    python_pydiction.vim   -- Vim plugin that autocompletes Python code.\r\n    complete-dict              -- Dictionary file of Python keywords, modules, etc.\r\n    pydiction.py                -- Python script to add more words to complete-dict.\r\n\r\nThe bundled dictionary comes with most terms you will likely need in your day-to-day Python programming, and the included\r\nPython script allows you to easily append new modules to the dictionary. So you don't have to wait around for me to add them.\r\nAnd you can teach Pydiction to complete your project's own API very quickly. Some third-party libraries already supported are:\r\n`Django` `Flask` `Requests` `Twisted` `Numpy` `Psycopg2` `PyGreSQL` `SQLite3` `MySQLdb` `OpenGL` `Pygame` `wxPython`\r\n `PyGTK` `PyQT4` `OpenID` `lxml` `urwid` `Celery` `Scrapy` and more.","4":"Pydiction allows you to Tab-complete Python code in Vim such as keywords, built-ins, standard library, and third-party modules.\r\n\r\nFor the latest version of Pydiction and full documentation, see: http:\/\/rkulla.github.io\/pydiction\/\r\n\r\nIt doesn't require installing any dependencies. It simply consists of three files:\r\n\r\n    python_pydiction.vim   -- Vim plugin that autocompletes Python code.\r\n    complete-dict              -- Dictionary file of Python keywords, modules, etc.\r\n    pydiction.py                -- Python script to add more words to complete-dict.\r\n\r\nThe bundled dictionary comes with most terms you will likely need in your day-to-day Python programming, and the included\r\nPython script allows you to easily append new modules to the dictionary. So you don't have to wait around for me to add them.\r\nAnd you can teach Pydiction to complete your project's own API very quickly. Some third-party libraries already supported are:\r\n`Django` `Flask` `Requests` `Twisted` `Numpy` `Psycopg2` `PyGreSQL` `SQLite3` `MySQLdb` `OpenGL` `Pygame` `wxPython`\r\n `PyGTK` `PyQT4` `OpenID` `lxml` `urwid` `Celery` `Scrapy` and more.","install_details":"If you have Pathogen installed:\r\n\r\n    cd ~\/.vim\/bundle\r\n    git clone https:\/\/github.com\/rkulla\/pydiction.git\r\n\r\nor use a plugin manager like Vimogen (https:\/\/github.com\/rkulla\/vimogen) to install and manage Pydiction and all of your plugins.\r\n\r\nOtherwise:\r\n\r\n    - UNIX\/LINUX\/OSX: Put python_pydiction.vim in ~\/.vim\/after\/ftplugin\/\r\n    (Create this directory if doesn't yet exist. Vim looks there automatically)\r\n\r\n    - WINDOWS: Put python_pydiction.vim in C:\\vim\\vimfiles\\ftplugin\\\r\n    (Assuming you installed Vim to C:\\vim\\)\r\n\r\n    You may install complete-dict and pydiction.py anywhere (see the Configuration section),\r\n    but only python_pydiction.vim in the ftplugin directory because for .vim files only.\r\n\r\nConfiguration\r\n==========\r\nIn your vimrc file, first add the following line to enable filetype plugins:\r\n\r\n    filetype plugin on\r\n\r\nthen make sure you set g:pydiction_location to the full path of where you installed complete-dict. Ex:\r\n\r\n    let g:pydiction_location = '\/path\/to\/complete-dict'\r\n\r\nfor example, if you used Pathogen to install Pydiction, you would set this to:\r\n\r\n    let g:pydiction_location = '\/home\/user\/.vim\/bundle\/pydiction\/complete-dict'\r\n\r\nand the dictionary will be available to all of your virtualenv's as well.\r\n\r\nYou can change the height of the completion menu by setting g:pydiction_menu_height in your vimrc:\r\n\r\n    let g:pydiction_menu_height = 3\r\n\r\nThe default menu height is 8, meaning 8 items at a time will be shown. Some people prefer more or less and you can make it as large as you want since it will automatically know where to position the menu to be visible.\r\n\r\nNote: If you were using a version of Pydiction less than 1.0, make sure you delete the old pydiction way of doing things from your vimrc. You should ***NOT*** have this in your vimrc anymore:\r\n\r\n        if has(\"autocmd\")\r\n           autocmd FileType python set complete+=k\/path\/to\/pydiction iskeyword+=.,(\r\n        endif \" has(\"autocmd\")\r\n\r\nIf you want to configure other things, such as how to get Pydiction to work with other plugins like `SnipMate` or the color of the menu, see the `Tips` section of the documentation.","5":"If you have Pathogen installed:\r\n\r\n    cd ~\/.vim\/bundle\r\n    git clone https:\/\/github.com\/rkulla\/pydiction.git\r\n\r\nor use a plugin manager like Vimogen (https:\/\/github.com\/rkulla\/vimogen) to install and manage Pydiction and all of your plugins.\r\n\r\nOtherwise:\r\n\r\n    - UNIX\/LINUX\/OSX: Put python_pydiction.vim in ~\/.vim\/after\/ftplugin\/\r\n    (Create this directory if doesn't yet exist. Vim looks there automatically)\r\n\r\n    - WINDOWS: Put python_pydiction.vim in C:\\vim\\vimfiles\\ftplugin\\\r\n    (Assuming you installed Vim to C:\\vim\\)\r\n\r\n    You may install complete-dict and pydiction.py anywhere (see the Configuration section),\r\n    but only python_pydiction.vim in the ftplugin directory because for .vim files only.\r\n\r\nConfiguration\r\n==========\r\nIn your vimrc file, first add the following line to enable filetype plugins:\r\n\r\n    filetype plugin on\r\n\r\nthen make sure you set g:pydiction_location to the full path of where you installed complete-dict. Ex:\r\n\r\n    let g:pydiction_location = '\/path\/to\/complete-dict'\r\n\r\nfor example, if you used Pathogen to install Pydiction, you would set this to:\r\n\r\n    let g:pydiction_location = '\/home\/user\/.vim\/bundle\/pydiction\/complete-dict'\r\n\r\nand the dictionary will be available to all of your virtualenv's as well.\r\n\r\nYou can change the height of the completion menu by setting g:pydiction_menu_height in your vimrc:\r\n\r\n    let g:pydiction_menu_height = 3\r\n\r\nThe default menu height is 8, meaning 8 items at a time will be shown. Some people prefer more or less and you can make it as large as you want since it will automatically know where to position the menu to be visible.\r\n\r\nNote: If you were using a version of Pydiction less than 1.0, make sure you delete the old pydiction way of doing things from your vimrc. You should ***NOT*** have this in your vimrc anymore:\r\n\r\n        if has(\"autocmd\")\r\n           autocmd FileType python set complete+=k\/path\/to\/pydiction iskeyword+=.,(\r\n        endif \" has(\"autocmd\")\r\n\r\nIf you want to configure other things, such as how to get Pydiction to work with other plugins like `SnipMate` or the color of the menu, see the `Tips` section of the documentation.","first_name":"ryan","6":"ryan","last_name":"kulla","7":"kulla","releases":[{"0":"850","vim_version":"7.0","1":"7.0","script_version":"1.2.3","2":"1.2.3","version_comment":"Adds scrapy, lxml, urwid and celery. Adds better completion defaults. Removes extra blank lines. Adds better checking for missing attributes. ","3":"Adds scrapy, lxml, urwid and celery. Adds better completion defaults. Removes extra blank lines. Adds better checking for missing attributes. ","package":"pydiction-1.2.3.zip","4":"pydiction-1.2.3.zip","src_id":"21842","5":"21842","creation_date":"1398781439","6":"1398781439"},{"0":"850","vim_version":"7.0","1":"7.0","script_version":"1.2.2","2":"1.2.2","version_comment":"Adds latest 2.7 versions of every built-in\/stdlib thing and includes Django, Flask, Requests, Psycopg2 and more.  Also adds more completion marker info to the dictionary such as what is a root module, and what version of python and which operating system was use to generated dictionary items.","3":"Adds latest 2.7 versions of every built-in\/stdlib thing and includes Django, Flask, Requests, Psycopg2 and more.  Also adds more completion marker info to the dictionary such as what is a root module, and what version of python and which operating system was use to generated dictionary items.","package":"pydiction-1.2.2.zip","4":"pydiction-1.2.2.zip","src_id":"21735","5":"21735","creation_date":"1396645702","6":"1396645702"},{"0":"850","vim_version":"7.0","1":"7.0","script_version":"1.2.1","2":"1.2.1","version_comment":"Updated file structure for Pathogen and misc. code cleanup","3":"Updated file structure for Pathogen and misc. code cleanup","package":"pydiction-1.2.1.zip","4":"pydiction-1.2.1.zip","src_id":"19587","5":"19587","creation_date":"1362352730","6":"1362352730"},{"0":"850","vim_version":"7.0","1":"7.0","script_version":"1.2","2":"1.2","version_comment":"Added \"from module\" completion, Tab backwards support, and more third party libs. ","3":"Added \"from module\" completion, Tab backwards support, and more third party libs. ","package":"pydiction-1.2.zip","4":"pydiction-1.2.zip","src_id":"11062","5":"11062","creation_date":"1248480105","6":"1248480105"},{"0":"850","vim_version":"7.0","1":"7.0","script_version":"1.1","2":"1.1","version_comment":"Added quoted string method completion, ZSI Web Services module completion and fixed a bug with the -v option.","3":"Added quoted string method completion, ZSI Web Services module completion and fixed a bug with the -v option.","package":"pydiction-1.1.zip","4":"pydiction-1.1.zip","src_id":"11040","5":"11040","creation_date":"1248088182","6":"1248088182"},{"0":"850","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"I Rewrote everything. It's now an ftplugin and uses the Tab key for completion. The dictionary generator works much better and you have more options. ","3":"I Rewrote everything. It's now an ftplugin and uses the Tab key for completion. The dictionary generator works much better and you have more options. ","package":"pydiction-1.0.zip","4":"pydiction-1.0.zip","src_id":"11028","5":"11028","creation_date":"1247904975","6":"1247904975"},{"0":"850","vim_version":"6.0","1":"6.0","script_version":"0.5","2":"0.5","version_comment":"Added support for ldap, cleaned up some code and included a gnu license.","3":"Added support for ldap, cleaned up some code and included a gnu license.","package":"pydiction-0.5.tar.gz","4":"pydiction-0.5.tar.gz","src_id":"2668","5":"2668","creation_date":"1074476357","6":"1074476357"},{"0":"850","vim_version":"6.0","1":"6.0","script_version":"0.4","2":"0.4","version_comment":"support for Numeric and numarray","3":"support for Numeric and numarray","package":"pydiction-0.4.tar.gz","4":"pydiction-0.4.tar.gz","src_id":"2605","5":"2605","creation_date":"1071592467","6":"1071592467"},{"0":"850","vim_version":"6.0","1":"6.0","script_version":"0.3","2":"0.3","version_comment":"This version allows you to supply multiple module names to pydiction.py and it will auto-append them to the pydiction file. The included pydiction file now contains support for wxPython and Twisted.","3":"This version allows you to supply multiple module names to pydiction.py and it will auto-append them to the pydiction file. The included pydiction file now contains support for wxPython and Twisted.","package":"pydiction-0.3.tar.gz","4":"pydiction-0.3.tar.gz","src_id":"2600","5":"2600","creation_date":"1071505870","6":"1071505870"},{"0":"850","vim_version":"6.0","1":"6.0","script_version":"0.2","2":"0.2","version_comment":"Added support for Pygame to pydiction. And im supplying the source code to the pydiction generator so people can extend pydiction so that they can have auto-completion for their own modules\/functions\/etc","3":"Added support for Pygame to pydiction. And im supplying the source code to the pydiction generator so people can extend pydiction so that they can have auto-completion for their own modules\/functions\/etc","package":"pydiction-0.2.tar.gz","4":"pydiction-0.2.tar.gz","src_id":"2559","5":"2559","creation_date":"1070730266","6":"1070730266"},{"0":"850","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"pydiction","4":"pydiction","src_id":"2555","5":"2555","creation_date":"1070681762","6":"1070681762"}]},"849":{"script_id":"849","0":"849","script_name":"latex-mik.vim","1":"latex-mik.vim","script_type":"utility","2":"utility","summary":"LaTeX support (MikTeX) for GVIM on Win32-systems","3":"LaTeX support (MikTeX) for GVIM on Win32-systems","description":"This script adds a menu for LaTeX-related functions for .tex, .bib-files\r\n\r\nTo process multiple file LaTeX-projects, enter the project name (e.g.\r\n``myproject'') at the prompt, if ``myproject.tex'' is the main file.\r\n\r\nMenu options address:\r\n\r\n  (pdf)latex\r\n  bibtex\r\n  makeindex\r\n  yap (dvi-viewer)\r\n  dvips\r\n  gsview32\r\n  tth\r\n\r\nLatex-mik supports entering commands and environments.","4":"This script adds a menu for LaTeX-related functions for .tex, .bib-files\r\n\r\nTo process multiple file LaTeX-projects, enter the project name (e.g.\r\n``myproject'') at the prompt, if ``myproject.tex'' is the main file.\r\n\r\nMenu options address:\r\n\r\n  (pdf)latex\r\n  bibtex\r\n  makeindex\r\n  yap (dvi-viewer)\r\n  dvips\r\n  gsview32\r\n  tth\r\n\r\nLatex-mik supports entering commands and environments.","install_details":"For installation, please put the script file (latex-mik.vim) into the vim plugin-directory\r\n","5":"For installation, please put the script file (latex-mik.vim) into the vim plugin-directory\r\n","first_name":"Volker","6":"Volker","last_name":"Kiefel","7":"Kiefel","releases":[{"0":"849","vim_version":"6.0","1":"6.0","script_version":"v0.7","2":"v0.7","version_comment":"Bugfix (problem related to current working directory), more LaTeX environments  supported","3":"Bugfix (problem related to current working directory), more LaTeX environments  supported","package":"latex-mik-0_7.zip","4":"latex-mik-0_7.zip","src_id":"4607","5":"4607","creation_date":"1127341857","6":"1127341857"},{"0":"849","vim_version":"6.0","1":"6.0","script_version":"v0.6","2":"v0.6","version_comment":"Important functions mapped to key sequences","3":"Important functions mapped to key sequences","package":"latex-mik-0_6.zip","4":"latex-mik-0_6.zip","src_id":"2666","5":"2666","creation_date":"1074419508","6":"1074419508"},{"0":"849","vim_version":"6.0","1":"6.0","script_version":"v0.5","2":"v0.5","version_comment":"Documentation corrected","3":"Documentation corrected","package":"latex-mik-0_5.zip","4":"latex-mik-0_5.zip","src_id":"2629","5":"2629","creation_date":"1072429104","6":"1072429104"}]},"848":{"script_id":"848","0":"848","script_name":"SrchRplcHiGrp.vim","1":"SrchRplcHiGrp.vim","script_type":"utility","2":"utility","summary":"Search and\/or replace based on a syntax highlight group","3":"Search and\/or replace based on a syntax highlight group","description":"\tSR = Search and\/or Replace\t\t\t\r\n\r\nThis plugin defines some commands to allow you to:\r\n1.  Search for characters with a particular syntax highlight group\r\n2.  Search and replace characters with a particular syntax highlight group\r\n\r\nCommands:\r\n\tSRDispHiGrp\t\t\t\t\r\n\t\tDisplays the syntax id and name the of the syntax group \r\n\t\twhich has been chosen.\r\n\r\n\tSRChooseHiGrp[!]       \t\t\t\r\n                Before you can run the search and replace command (:SRHiGrp),\r\n                you must choose which syntax group id you want to operate on.  \r\n                The top level syntax id of the current cursor position is\r\n                chosen (ie. the top-level one versus the final one).\r\n\r\n                The optional bang lets SRChooseHiGrp use the translated\r\n                syntax ID. This is final one versus the top-level one. \r\n\r\n                Assuming we were using a SQL file and placed the cursor on the\r\n                FROM word, then using the SyntaxAttr plugin\r\n                (http:\/\/vim.sourceforge.net\/script.php?script_id=383)\r\n                it displays both the top-level and translated \r\n                (or final) highlight group as follows: \r\n                  group: sqlKeyword->Statement guifg=#ffff00(#ffff00) \r\n \r\n\r\n\t\tExamples: \r\n\t\t  :SRChooseHiGrp \r\n                      Will operate on only sqlKeyword syntax groups\r\n\r\n\t\t  :SRChooseHiGrp! \r\n                      Will operate on all Statement syntax groups.  Based on\r\n                      |group-name|, the Statement group will highlight the\r\n                      same color for the following highlight groups:\r\n                            Conditional\t\r\n                            Repeat\t\t\r\n                            Label\t\t\r\n                            Operator\t\r\n                            Keyword\t\r\n                            Exception\t\r\n                      Therefore SRChooseHiGrp! will operate over all of the\r\n                      above syntax groups.\r\n\r\n\tSRHiGrp[!] \t       \t\t\t      \t\r\n                This command will perform a search and replace over a visual\r\n                range.  It works in all visual modes, characterwise (v),\r\n                linewise (V) and blockwise (<C-V>).\r\n\r\n\t\tIt optionally takes takes 2 parameters.\r\n\r\n                Parameter 1 controls what characters are matched.  The default\r\n                for this value is \\(\\w\\+\\>\\).  This expression is appended to\r\n                the \\%# which starts the match from the current cursor\r\n                position.  This expression must specify a submatch \\(...\\).\r\n\r\n\t\tParameter 2 controls what to do with the matched string.  The\r\n\t\tdefault for this value is \\U\\1.  This expression will cause\r\n\t\tthe matched string to be UPPER cased.  The \\1 refers to the \r\n                submatch from the first parameter.\r\n\r\n\t\tIf the parameters are not supplied, the user will be prompted\r\n\t\tto enter the expression(s).\r\n\r\n                The optional bang (!) works the same as SRHiGrp, but will\r\n                operate on all syntax groups that are NOT the chosen one\r\n                (SRChooseHiGrp).\r\n\r\n\t\tSyntax: \r\n\t\t[range]SRHiGrp[!] 'from-pattern','to-string'\r\n\r\n \r\n\tSRSearch[!]  \t       \t\t\t      \t\r\n                This command will perform a forward search starting at the current\r\n                cursor position for a specified highlight group name.  The range defaults\r\n                to the entire file.  It supports all visual modes, characterwise (v),\r\n                linewise (V) and blockwise (<C-V>).\r\n\r\n                It will optionally take a regular expression and match on both the syntax\r\n                group and the regular expression.\r\n\r\n                When using SRSearch! it NOT match the syntax group.\r\n\r\n==============================================================================\r\n3. Examples\t\t\t\t\t*srchrplchigrp-examples*\r\n\r\n   SRHiGrp\r\n   -------\r\n\r\n\tFirst place your cursor on an item that is syntax colored the way\r\n\tyou want:\r\n\t\t:SRChooseHiGrp\r\n \r\n\tNext, visually select a block of text\r\n\t(all visual modes are supported)\r\n\t\t:SRHiGrp\r\n\t\tor\r\n\t\t:SRHiGrp '\\(\\w\\+\\>\\)'\r\n\t\tor\r\n\t\t:SRHiGrp '\\(\\w\\+\\>\\)', '\\U\\1'\r\n\r\n\tIf you had the following in a SQL file:\r\n\t\tif exists( select 1\r\n\t\t            from sys.sysprocedure sp\r\n\t\t             key join sys.sysuserperm sup\r\n\t\t           where sp.proc_name = 'sp_http_course_detail'\r\n\t\t             and sup.user_name = user_name()             ) then\r\n\t\t    drop procedure sp_http_course_detail;\r\n\t\tend if;\r\n\r\n\tWhere the keywords (if, exists, select, from ...) are all \r\n\thighlighted yellow (based on my colorscheme).  After I visually\r\n\tselect the area and run the command taking default prompts:\r\n\t\t:'<,'>SRHiGrp \r\n\r\n\tThe result is:\r\n\t\tIF EXISTS( SELECT 1\r\n\t\t            FROM sys.sysprocedure sp\r\n\t\t             KEY JOIN sys.sysuserperm sup\r\n\t\t           WHERE sp.proc_name = 'sp_http_course_detail'\r\n\t\t             AND sup.user_name = user_name()             ) THEN\r\n\t\t    DROP PROCEDURE sp_http_course_detail;\r\n\t\tEND IF;\r\n\r\n\tWhere the keywords (if, exists, select, from ...) are all \r\n\thighlighted yellow (based on my colorscheme).  After I visually\r\n\tselect the area and run the command taking default prompts: \r\n\t\t:'<,'>SRHiGrp!\r\n\r\n\tThe result is:\r\n\t\tif exists( select 1\r\n\t\t            from SYS.SYSPROCEDURE SP\r\n\t\t             key join SYS.SYSUSERPERM SUP\r\n\t\t           where SP.PROC_NAME = 'SP_HTTP_COURSE_DETAIL'\r\n\t\t             and SUP.USER_NAME = USER_NAME()             ) then\r\n\t\t    drop procedure SP_HTTP_COURSE_DETAIL;\r\n\t\tend if; \r\n\r\n\r\n   SRSearch\r\n   --------------\r\n\tSRSearch simply does a forward search for the specified highlight\r\n        group.  You must first use SRChooseHiGrp to choose a highlight group.\r\n        Find the next item highlighted as that syntax group:  \r\n\t\t:SRSearch \r\n\t\t:1,5SRSearch \r\n\t\t:'<,'>SRSearch \r\n \r\n        Find the next item highlighted that is NOT that syntax group: \r\n\t\t:SRSearch!\r\n\t\t:1,5SRSearch! \r\n\t\t:'<,'>SRSearch! \r\n \r\n        Find the next item highlighted as that syntax group and matches\r\n        the regular expression supplied: \r\n\t\t:SRSearch something\r\n\t\t:SRSearch \\(first\\|second\\|word\\)\r\n \r\n        Find the next item highlighted that is NOT that syntax group and \r\n        matches the regular expression supplied: \r\n\t\t:SRSearch! \\(first\\|second\\|word\\)\r\n \r\n        The results of the search is displayed in the command line and is\r\n        highlighted in the color of the syntax group.  This will remind you\r\n        which group was searched for. \r\n            SRSearch - Match found - Group ID: 171  Name: sqlKeyword\r\n            SRSearch - Match NOT found - Group ID: 171  Name: sqlKeyword\r\n            SRSearch - Match found - Group ID: 171  Name: sqlKeyword  Regex: \\(first\\|second\\|word\\)\r\n            SRSearch - Match NOT found - Group ID: 171  Name: sqlKeyword  Regex \\(first\\|second\\|word\\)\r\n\r\n","4":"\tSR = Search and\/or Replace\t\t\t\r\n\r\nThis plugin defines some commands to allow you to:\r\n1.  Search for characters with a particular syntax highlight group\r\n2.  Search and replace characters with a particular syntax highlight group\r\n\r\nCommands:\r\n\tSRDispHiGrp\t\t\t\t\r\n\t\tDisplays the syntax id and name the of the syntax group \r\n\t\twhich has been chosen.\r\n\r\n\tSRChooseHiGrp[!]       \t\t\t\r\n                Before you can run the search and replace command (:SRHiGrp),\r\n                you must choose which syntax group id you want to operate on.  \r\n                The top level syntax id of the current cursor position is\r\n                chosen (ie. the top-level one versus the final one).\r\n\r\n                The optional bang lets SRChooseHiGrp use the translated\r\n                syntax ID. This is final one versus the top-level one. \r\n\r\n                Assuming we were using a SQL file and placed the cursor on the\r\n                FROM word, then using the SyntaxAttr plugin\r\n                (http:\/\/vim.sourceforge.net\/script.php?script_id=383)\r\n                it displays both the top-level and translated \r\n                (or final) highlight group as follows: \r\n                  group: sqlKeyword->Statement guifg=#ffff00(#ffff00) \r\n \r\n\r\n\t\tExamples: \r\n\t\t  :SRChooseHiGrp \r\n                      Will operate on only sqlKeyword syntax groups\r\n\r\n\t\t  :SRChooseHiGrp! \r\n                      Will operate on all Statement syntax groups.  Based on\r\n                      |group-name|, the Statement group will highlight the\r\n                      same color for the following highlight groups:\r\n                            Conditional\t\r\n                            Repeat\t\t\r\n                            Label\t\t\r\n                            Operator\t\r\n                            Keyword\t\r\n                            Exception\t\r\n                      Therefore SRChooseHiGrp! will operate over all of the\r\n                      above syntax groups.\r\n\r\n\tSRHiGrp[!] \t       \t\t\t      \t\r\n                This command will perform a search and replace over a visual\r\n                range.  It works in all visual modes, characterwise (v),\r\n                linewise (V) and blockwise (<C-V>).\r\n\r\n\t\tIt optionally takes takes 2 parameters.\r\n\r\n                Parameter 1 controls what characters are matched.  The default\r\n                for this value is \\(\\w\\+\\>\\).  This expression is appended to\r\n                the \\%# which starts the match from the current cursor\r\n                position.  This expression must specify a submatch \\(...\\).\r\n\r\n\t\tParameter 2 controls what to do with the matched string.  The\r\n\t\tdefault for this value is \\U\\1.  This expression will cause\r\n\t\tthe matched string to be UPPER cased.  The \\1 refers to the \r\n                submatch from the first parameter.\r\n\r\n\t\tIf the parameters are not supplied, the user will be prompted\r\n\t\tto enter the expression(s).\r\n\r\n                The optional bang (!) works the same as SRHiGrp, but will\r\n                operate on all syntax groups that are NOT the chosen one\r\n                (SRChooseHiGrp).\r\n\r\n\t\tSyntax: \r\n\t\t[range]SRHiGrp[!] 'from-pattern','to-string'\r\n\r\n \r\n\tSRSearch[!]  \t       \t\t\t      \t\r\n                This command will perform a forward search starting at the current\r\n                cursor position for a specified highlight group name.  The range defaults\r\n                to the entire file.  It supports all visual modes, characterwise (v),\r\n                linewise (V) and blockwise (<C-V>).\r\n\r\n                It will optionally take a regular expression and match on both the syntax\r\n                group and the regular expression.\r\n\r\n                When using SRSearch! it NOT match the syntax group.\r\n\r\n==============================================================================\r\n3. Examples\t\t\t\t\t*srchrplchigrp-examples*\r\n\r\n   SRHiGrp\r\n   -------\r\n\r\n\tFirst place your cursor on an item that is syntax colored the way\r\n\tyou want:\r\n\t\t:SRChooseHiGrp\r\n \r\n\tNext, visually select a block of text\r\n\t(all visual modes are supported)\r\n\t\t:SRHiGrp\r\n\t\tor\r\n\t\t:SRHiGrp '\\(\\w\\+\\>\\)'\r\n\t\tor\r\n\t\t:SRHiGrp '\\(\\w\\+\\>\\)', '\\U\\1'\r\n\r\n\tIf you had the following in a SQL file:\r\n\t\tif exists( select 1\r\n\t\t            from sys.sysprocedure sp\r\n\t\t             key join sys.sysuserperm sup\r\n\t\t           where sp.proc_name = 'sp_http_course_detail'\r\n\t\t             and sup.user_name = user_name()             ) then\r\n\t\t    drop procedure sp_http_course_detail;\r\n\t\tend if;\r\n\r\n\tWhere the keywords (if, exists, select, from ...) are all \r\n\thighlighted yellow (based on my colorscheme).  After I visually\r\n\tselect the area and run the command taking default prompts:\r\n\t\t:'<,'>SRHiGrp \r\n\r\n\tThe result is:\r\n\t\tIF EXISTS( SELECT 1\r\n\t\t            FROM sys.sysprocedure sp\r\n\t\t             KEY JOIN sys.sysuserperm sup\r\n\t\t           WHERE sp.proc_name = 'sp_http_course_detail'\r\n\t\t             AND sup.user_name = user_name()             ) THEN\r\n\t\t    DROP PROCEDURE sp_http_course_detail;\r\n\t\tEND IF;\r\n\r\n\tWhere the keywords (if, exists, select, from ...) are all \r\n\thighlighted yellow (based on my colorscheme).  After I visually\r\n\tselect the area and run the command taking default prompts: \r\n\t\t:'<,'>SRHiGrp!\r\n\r\n\tThe result is:\r\n\t\tif exists( select 1\r\n\t\t            from SYS.SYSPROCEDURE SP\r\n\t\t             key join SYS.SYSUSERPERM SUP\r\n\t\t           where SP.PROC_NAME = 'SP_HTTP_COURSE_DETAIL'\r\n\t\t             and SUP.USER_NAME = USER_NAME()             ) then\r\n\t\t    drop procedure SP_HTTP_COURSE_DETAIL;\r\n\t\tend if; \r\n\r\n\r\n   SRSearch\r\n   --------------\r\n\tSRSearch simply does a forward search for the specified highlight\r\n        group.  You must first use SRChooseHiGrp to choose a highlight group.\r\n        Find the next item highlighted as that syntax group:  \r\n\t\t:SRSearch \r\n\t\t:1,5SRSearch \r\n\t\t:'<,'>SRSearch \r\n \r\n        Find the next item highlighted that is NOT that syntax group: \r\n\t\t:SRSearch!\r\n\t\t:1,5SRSearch! \r\n\t\t:'<,'>SRSearch! \r\n \r\n        Find the next item highlighted as that syntax group and matches\r\n        the regular expression supplied: \r\n\t\t:SRSearch something\r\n\t\t:SRSearch \\(first\\|second\\|word\\)\r\n \r\n        Find the next item highlighted that is NOT that syntax group and \r\n        matches the regular expression supplied: \r\n\t\t:SRSearch! \\(first\\|second\\|word\\)\r\n \r\n        The results of the search is displayed in the command line and is\r\n        highlighted in the color of the syntax group.  This will remind you\r\n        which group was searched for. \r\n            SRSearch - Match found - Group ID: 171  Name: sqlKeyword\r\n            SRSearch - Match NOT found - Group ID: 171  Name: sqlKeyword\r\n            SRSearch - Match found - Group ID: 171  Name: sqlKeyword  Regex: \\(first\\|second\\|word\\)\r\n            SRSearch - Match NOT found - Group ID: 171  Name: sqlKeyword  Regex \\(first\\|second\\|word\\)\r\n\r\n","install_details":"Unzip into your vimfiles(windows) or .vim(Unix) directory (using directory structure).\r\nRun the following to update the Vim help files:\r\n:helptags $VIM\/vimfiles\/doc\r\n:helptags $VIM\/.vim\/doc\r\n\r\n ","5":"Unzip into your vimfiles(windows) or .vim(Unix) directory (using directory structure).\r\nRun the following to update the Vim help files:\r\n:helptags $VIM\/vimfiles\/doc\r\n:helptags $VIM\/.vim\/doc\r\n\r\n ","first_name":"David","6":"David","last_name":"Fishburn","7":"Fishburn","releases":[{"0":"848","vim_version":"7.0","1":"7.0","script_version":"7.0","2":"7.0","version_comment":"Changed SRSeach.  \r\n\r\nIt will first look for the next item that has the syntax group chosen via SRChooseHiGrp.  \r\n\r\nIt will also take an optional regular expression and not only find that syntax group, but also match the regular expression.\r\n\r\nAdded SRSearch!, which will find the next item that is NOT what was chosen via SRChooseHiGrp.  \r\n\r\nSame applied with the regular expression, so if I put my cursor on a comment and \r\n    :SRChooseHiGrp.\r\n\r\nThen ran \r\n    :SRSearch! something\r\n\r\nIt will find the word \"something\" that is NOT in a comment.\r\n","3":"Changed SRSeach.  \r\n\r\nIt will first look for the next item that has the syntax group chosen via SRChooseHiGrp.  \r\n\r\nIt will also take an optional regular expression and not only find that syntax group, but also match the regular expression.\r\n\r\nAdded SRSearch!, which will find the next item that is NOT what was chosen via SRChooseHiGrp.  \r\n\r\nSame applied with the regular expression, so if I put my cursor on a comment and \r\n    :SRChooseHiGrp.\r\n\r\nThen ran \r\n    :SRSearch! something\r\n\r\nIt will find the word \"something\" that is NOT in a comment.\r\n","package":"SrchRplHiGrp_v70.zip","4":"SrchRplHiGrp_v70.zip","src_id":"23549","5":"23549","creation_date":"1440509755","6":"1440509755"},{"0":"848","vim_version":"7.0","1":"7.0","script_version":"6.0","2":"6.0","version_comment":"- Changed to save and restore cp options on load\r\n\r\n- Changed to use Vim's autoload mechanism to load only when required (speeds Vim's load time and memory usage)\r\n\r\n- When using SRHiGrp! (operate over non-matching areas) the plugin always reported \"Did not find highlight group\" (Mathieu Westphal)\r\n\r\n- SRHiGrp now defaults the range to the entire file, instead of the current row\r\n","3":"- Changed to save and restore cp options on load\r\n\r\n- Changed to use Vim's autoload mechanism to load only when required (speeds Vim's load time and memory usage)\r\n\r\n- When using SRHiGrp! (operate over non-matching areas) the plugin always reported \"Did not find highlight group\" (Mathieu Westphal)\r\n\r\n- SRHiGrp now defaults the range to the entire file, instead of the current row\r\n","package":"SrchRplHiGrp_v60.zip","4":"SrchRplHiGrp_v60.zip","src_id":"23488","5":"23488","creation_date":"1438016294","6":"1438016294"},{"0":"848","vim_version":"7.0","1":"7.0","script_version":"5.0","2":"5.0","version_comment":"When using SRSearch only stop at the next match when clearly moving between gaps of the highlight group (Sergio).\r\n","3":"When using SRSearch only stop at the next match when clearly moving between gaps of the highlight group (Sergio).\r\n","package":"SrchRplHiGrp_v50.zip","4":"SrchRplHiGrp_v50.zip","src_id":"14668","5":"14668","creation_date":"1293912116","6":"1293912116"},{"0":"848","vim_version":"7.0","1":"7.0","script_version":"4.0","2":"4.0","version_comment":"Fixed an undefined variable and some boundary conditions.","3":"Fixed an undefined variable and some boundary conditions.","package":"SrchRplHiGrp_v40.zip","4":"SrchRplHiGrp_v40.zip","src_id":"8203","5":"8203","creation_date":"1201715940","6":"1201715940"},{"0":"848","vim_version":"6.0","1":"6.0","script_version":"2.0","2":"2.0","version_comment":"New command, SRSearch, so you can find characters with a specific syntax highlight group.\r\n\r\nChanged SRHiGrp to escape the regex provided.  This saves you from having to escape the expression yourself.\r\n","3":"New command, SRSearch, so you can find characters with a specific syntax highlight group.\r\n\r\nChanged SRHiGrp to escape the regex provided.  This saves you from having to escape the expression yourself.\r\n","package":"SrchRplHiGrp.zip","4":"SrchRplHiGrp.zip","src_id":"5541","5":"5541","creation_date":"1144784746","6":"1144784746"},{"0":"848","vim_version":"6.0","1":"6.0","script_version":"0.15","2":"0.15","version_comment":"Changed SRChooseGrp to default to the top-level syntax group instead of the translated group.  Using SRChooseGrp! will choose the translated group (which will effect more values).\r\nAdded a help file.\r\nRemoved SRHiGrpNot and replaced it with SRHiGrp!.\r\nUpdated the examples.\r\nMost of this work was done by Dr. Chip (thanks!).","3":"Changed SRChooseGrp to default to the top-level syntax group instead of the translated group.  Using SRChooseGrp! will choose the translated group (which will effect more values).\r\nAdded a help file.\r\nRemoved SRHiGrpNot and replaced it with SRHiGrp!.\r\nUpdated the examples.\r\nMost of this work was done by Dr. Chip (thanks!).","package":"SrchRplHiGrp.zip","4":"SrchRplHiGrp.zip","src_id":"2654","5":"2654","creation_date":"1073679918","6":"1073679918"}]},"847":{"script_id":"847","0":"847","script_name":"howto ftplugin","1":"howto ftplugin","script_type":"ftplugin","2":"ftplugin","summary":"ftplugin for browsing HOWTO files","3":"ftplugin for browsing HOWTO files","description":"ftplugin for browsing HOWTO files\r\n<LocalLeader><CR> switches between TOC and HOWTO body (from <1> to <2> below)\r\n<LocalLeader><Space> goes to the next topic in the HOWTO (from <2> to <3>)\r\n\r\nExample:\r\n<<BEGIN>>\r\nTable of Contents\r\n1. How can I help? <1>\r\n    1.1. Assisting with the Net-HOWTO\r\n...\r\n-----------------------------------------------------------------------------\r\nChapter 1. How can I help? <2>\r\n...\r\n-----------------------------------------------------------------------------\r\n1.1. Assisting with the Net-HOWTO <3>\r\n<<END>>\r\n","4":"ftplugin for browsing HOWTO files\r\n<LocalLeader><CR> switches between TOC and HOWTO body (from <1> to <2> below)\r\n<LocalLeader><Space> goes to the next topic in the HOWTO (from <2> to <3>)\r\n\r\nExample:\r\n<<BEGIN>>\r\nTable of Contents\r\n1. How can I help? <1>\r\n    1.1. Assisting with the Net-HOWTO\r\n...\r\n-----------------------------------------------------------------------------\r\nChapter 1. How can I help? <2>\r\n...\r\n-----------------------------------------------------------------------------\r\n1.1. Assisting with the Net-HOWTO <3>\r\n<<END>>\r\n","install_details":"- copy ftplugin\/howto.vim to ~\/.vim\/ftplugin\/\r\n- copy ftdetect\/howto.vim to ~\/.vim\/ftdetect\/\r\n- make sure the following line is in your vimrc\r\n  filetype plugin on\r\n","5":"- copy ftplugin\/howto.vim to ~\/.vim\/ftplugin\/\r\n- copy ftdetect\/howto.vim to ~\/.vim\/ftdetect\/\r\n- make sure the following line is in your vimrc\r\n  filetype plugin on\r\n","first_name":"John","6":"John","last_name":"Sumsion","7":"Sumsion","releases":[{"0":"847","vim_version":"6.0","1":"6.0","script_version":"1.1","2":"1.1","version_comment":"made trailing decimal after outline numbers optional","3":"made trailing decimal after outline numbers optional","package":"howto.zip","4":"howto.zip","src_id":"2549","5":"2549","creation_date":"1070639767","6":"1070639767"},{"0":"847","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"howto.zip","4":"howto.zip","src_id":"2548","5":"2548","creation_date":"1070636384","6":"1070636384"}]},"846":{"script_id":"846","0":"846","script_name":"mars.vim","1":"mars.vim","script_type":"color scheme","2":"color scheme","summary":"Dark red color scheme","3":"Dark red color scheme","description":"I was getting tired of black and blue colorschemes , thought I'd try to spice things up a bit :-).  Still I kept the colors dark or muted where I thought it made sense.  Check out a screen shot at http:\/\/www.geocities.com\/aldy0169\/vim\/\r\n\r\nenjoy.","4":"I was getting tired of black and blue colorschemes , thought I'd try to spice things up a bit :-).  Still I kept the colors dark or muted where I thought it made sense.  Check out a screen shot at http:\/\/www.geocities.com\/aldy0169\/vim\/\r\n\r\nenjoy.","install_details":"drop it in your '~\/.vim\/colors' directory  and run ':colorscheme mars'\r\n\r\nsee ':help colorscheme' for details","5":"drop it in your '~\/.vim\/colors' directory  and run ':colorscheme mars'\r\n\r\nsee ':help colorscheme' for details","first_name":"Timothy","6":"Timothy","last_name":"Aldrich","7":"Aldrich","releases":[{"0":"846","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"mars.vim","4":"mars.vim","src_id":"2547","5":"2547","creation_date":"1070631867","6":"1070631867"}]},"845":{"script_id":"845","0":"845","script_name":"pyab","1":"pyab","script_type":"utility","2":"utility","summary":"Abbreviates standard python modules","3":"Abbreviates standard python modules","description":"This project died in 2003 and has been rewritten as 'pydiction' (See: http:\/\/www.vim.org\/scripts\/script.php?script_id=850)","4":"This project died in 2003 and has been rewritten as 'pydiction' (See: http:\/\/www.vim.org\/scripts\/script.php?script_id=850)","install_details":":source pyab.vim","5":":source pyab.vim","first_name":"ryan","6":"ryan","last_name":"kulla","7":"kulla","releases":[{"0":"845","vim_version":"6.0","1":"6.0","script_version":"0.2","2":"0.2","version_comment":"I\\'ve since made a much better way of doing this. \\\"pydiction\\\": http:\/\/www.vim.org\/scripts\/script.php?script_id=850","3":"I\\'ve since made a much better way of doing this. \\\"pydiction\\\": http:\/\/www.vim.org\/scripts\/script.php?script_id=850","package":"pyab.vim","4":"pyab.vim","src_id":"2556","5":"2556","creation_date":"1070681998","6":"1070681998"},{"0":"845","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"pyab.vim","4":"pyab.vim","src_id":"2546","5":"2546","creation_date":"1070622987","6":"1070622987"}]},"844":{"script_id":"844","0":"844","script_name":"ptl.vim","1":"ptl.vim","script_type":"syntax","2":"syntax","summary":"Syntax File for the Python Template Language","3":"Syntax File for the Python Template Language","description":"Syntax File for the Python Template Language:\r\n\r\nhttp:\/\/www.mems-exchange.org\/software\/quixote\/doc\/PTL.html\r\n\r\nA language used by the Web application framework, Quixote (http:\/\/www.mems-exchange.org\/software\/quixote\/), which is mostly Python with embedded HTML.\r\n\r\nUses python.vim and html.vim.","4":"Syntax File for the Python Template Language:\r\n\r\nhttp:\/\/www.mems-exchange.org\/software\/quixote\/doc\/PTL.html\r\n\r\nA language used by the Web application framework, Quixote (http:\/\/www.mems-exchange.org\/software\/quixote\/), which is mostly Python with embedded HTML.\r\n\r\nUses python.vim and html.vim.","install_details":"Copy the file to your ~\/.vim\/syntax directory as usual.","5":"Copy the file to your ~\/.vim\/syntax directory as usual.","first_name":"estienne","6":"estienne","last_name":"swart","7":"swart","releases":[{"0":"844","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"ptl-0.1.tar.gz","4":"ptl-0.1.tar.gz","src_id":"2544","5":"2544","creation_date":"1070608833","6":"1070608833"}]},"843":{"script_id":"843","0":"843","script_name":"nasl.vim","1":"nasl.vim","script_type":"syntax","2":"syntax","summary":"syntax highlighting for Nessus nasl scripts","3":"syntax highlighting for Nessus nasl scripts","description":"Performs syntax highlighting for Nessus Attack Scripting\r\nLanguage (NASL) scripts.\r\n\r\nThis is still in rapid development, and by no means finished.  But, it's already useful, so I thought I would share it.","4":"Performs syntax highlighting for Nessus Attack Scripting\r\nLanguage (NASL) scripts.\r\n\r\nThis is still in rapid development, and by no means finished.  But, it's already useful, so I thought I would share it.","install_details":"Put the script in the same place where your other syntax scripts are located (on my Debian Linux system that would be \/usr\/share\/vim\/vim61\/syntax).   If you don't have access to that directory, then you can put it somewhere in your ~\/.vim directory, not sure where...\r\n\r\nTo have the nasl files be automatically recognized by the .nasl filename, you will need to edit the filetype.vim file on your system, adding an entry like this:\r\n\r\n\" Nasl script file\r\nau BufNewFile,BufRead *.nasl                    setf nasl\r\n\r\nThat way, the nasl.vim file will load automatically upon running :syntax enable, as long as you're editing a file which ends in .nasl (I'll work on having .inc files recognized as well).","5":"Put the script in the same place where your other syntax scripts are located (on my Debian Linux system that would be \/usr\/share\/vim\/vim61\/syntax).   If you don't have access to that directory, then you can put it somewhere in your ~\/.vim directory, not sure where...\r\n\r\nTo have the nasl files be automatically recognized by the .nasl filename, you will need to edit the filetype.vim file on your system, adding an entry like this:\r\n\r\n\" Nasl script file\r\nau BufNewFile,BufRead *.nasl                    setf nasl\r\n\r\nThat way, the nasl.vim file will load automatically upon running :syntax enable, as long as you're editing a file which ends in .nasl (I'll work on having .inc files recognized as well).","first_name":"Markus","6":"Markus","last_name":"DeShon","7":"DeShon","releases":[{"0":"843","vim_version":"6.0","1":"6.0","script_version":"0.3","2":"0.3","version_comment":"Have now added all the functions from all the .inc files.","3":"Have now added all the functions from all the .inc files.","package":"nasl.vim","4":"nasl.vim","src_id":"2588","5":"2588","creation_date":"1071243483","6":"1071243483"},{"0":"843","vim_version":"6.0","1":"6.0","script_version":"0.2","2":"0.2","version_comment":"This is a much better version, includes all builtin functions.  I will add the functions from all the standard .inc files next.","3":"This is a much better version, includes all builtin functions.  I will add the functions from all the standard .inc files next.","package":"nasl.vim","4":"nasl.vim","src_id":"2545","5":"2545","creation_date":"1070616259","6":"1070616259"},{"0":"843","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"nasl.vim","4":"nasl.vim","src_id":"2543","5":"2543","creation_date":"1070561281","6":"1070561281"}]},"842":{"script_id":"842","0":"842","script_name":"increment.vim","1":"increment.vim","script_type":"utility","2":"utility","summary":"Subsitute a pattern with incremented values","3":"Subsitute a pattern with incremented values","description":"This is a handy plugin that makes easy replacing your favorite pattern (\"@\" by default) with a sequence of incremented values using the \"Inc\" command.\r\n\r\nExamples:\r\n\r\nIf you have a file that only contains the following lines:\r\n\r\n   This is line @\r\n   This is line @\r\n   This is line @\r\n   This is line @\r\n\r\nBy typing \":1,4Inc\", you obtain:\r\n\r\n   This is line 0\r\n   This is line 1\r\n   This is line 2\r\n   This is line 3\r\n\r\nBetter yet...  With \":Inc i11 s4 pblah\",\r\n\r\n   This is a list: [blah, blah, blah, blah, blah, blah, blah]\r\n\r\nbecomes\r\n\r\n   This is a list: [4, 15, 26, 37, 48, 59, 70]\r\n\r\nYou can also repeat the same value several times.  Consider:\r\n\r\n   case\r\n      addr@: begin value@ = offset@+incr@; end\r\n      addr@: begin value@ = offset@+incr@; end\r\n      addr@: begin value@ = offset@+incr@; end\r\n   end\r\n\r\nAfter \":%Inc r4\", you obtain:\r\n\r\n   case\r\n      addr0: begin value0 = offset0+incr0; end\r\n      addr1: begin value1 = offset1+incr1; end\r\n      addr2: begin value2 = offset2+incr2; end\r\n   end\r\n\r\nI have just added support for bases and right alignment.  You just have to specify the width of your alignment:\r\n\r\n   `define MEM_ADD0 @\r\n   `define MEM_ADD1 @\r\n   `define MEM_ADD2 @\r\n   `define MEM_ADD3 @\r\n\r\nbecomes, after running \":%Inc w3 i128 f0\":\r\n\r\n   `define MEM_ADD0 000\r\n   `define MEM_ADD1 128\r\n   `define MEM_ADD2 256\r\n   `define MEM_ADD3 384\r\n\r\nor, after running \":%Inc w3 i128 f0 h\":\r\n\r\n   `define MEM_ADD0 000\r\n   `define MEM_ADD1 080\r\n   `define MEM_ADD2 100\r\n   `define MEM_ADD3 180\r\n\r\nMany thanks to Stanislas Sitar (vimscript #145), Ely Schoenfeld (vimscript #1199), Charles E Campbell's (vimtip #150, vimscript #670) and Neil Bird (vimscript #189).\r\n\r\nNote: I need to merge with Ely's version, and to update the documentation.  Sorry if this causes any inconvenience in the meantime.\r\n\r\nHappy Vimming!","4":"This is a handy plugin that makes easy replacing your favorite pattern (\"@\" by default) with a sequence of incremented values using the \"Inc\" command.\r\n\r\nExamples:\r\n\r\nIf you have a file that only contains the following lines:\r\n\r\n   This is line @\r\n   This is line @\r\n   This is line @\r\n   This is line @\r\n\r\nBy typing \":1,4Inc\", you obtain:\r\n\r\n   This is line 0\r\n   This is line 1\r\n   This is line 2\r\n   This is line 3\r\n\r\nBetter yet...  With \":Inc i11 s4 pblah\",\r\n\r\n   This is a list: [blah, blah, blah, blah, blah, blah, blah]\r\n\r\nbecomes\r\n\r\n   This is a list: [4, 15, 26, 37, 48, 59, 70]\r\n\r\nYou can also repeat the same value several times.  Consider:\r\n\r\n   case\r\n      addr@: begin value@ = offset@+incr@; end\r\n      addr@: begin value@ = offset@+incr@; end\r\n      addr@: begin value@ = offset@+incr@; end\r\n   end\r\n\r\nAfter \":%Inc r4\", you obtain:\r\n\r\n   case\r\n      addr0: begin value0 = offset0+incr0; end\r\n      addr1: begin value1 = offset1+incr1; end\r\n      addr2: begin value2 = offset2+incr2; end\r\n   end\r\n\r\nI have just added support for bases and right alignment.  You just have to specify the width of your alignment:\r\n\r\n   `define MEM_ADD0 @\r\n   `define MEM_ADD1 @\r\n   `define MEM_ADD2 @\r\n   `define MEM_ADD3 @\r\n\r\nbecomes, after running \":%Inc w3 i128 f0\":\r\n\r\n   `define MEM_ADD0 000\r\n   `define MEM_ADD1 128\r\n   `define MEM_ADD2 256\r\n   `define MEM_ADD3 384\r\n\r\nor, after running \":%Inc w3 i128 f0 h\":\r\n\r\n   `define MEM_ADD0 000\r\n   `define MEM_ADD1 080\r\n   `define MEM_ADD2 100\r\n   `define MEM_ADD3 180\r\n\r\nMany thanks to Stanislas Sitar (vimscript #145), Ely Schoenfeld (vimscript #1199), Charles E Campbell's (vimtip #150, vimscript #670) and Neil Bird (vimscript #189).\r\n\r\nNote: I need to merge with Ely's version, and to update the documentation.  Sorry if this causes any inconvenience in the meantime.\r\n\r\nHappy Vimming!","install_details":"Download \"increment.tar.gz\" and put it in your user \".vim\" or \"vimfiles\" directory.  For *nix, type:\r\n\r\ngunzip -c increment.tar.gz | tar xvf -\r\n\r\nThis will populate a \"doc\" directory with an \"increment.txt\" file, and a \"plugin\" directory with an \"increment.vim\" file.\r\n\r\nFor other operating systems, I'm sorry: I don't use them...  I believe \"gzip\" should know how to deal with that file.","5":"Download \"increment.tar.gz\" and put it in your user \".vim\" or \"vimfiles\" directory.  For *nix, type:\r\n\r\ngunzip -c increment.tar.gz | tar xvf -\r\n\r\nThis will populate a \"doc\" directory with an \"increment.txt\" file, and a \"plugin\" directory with an \"increment.vim\" file.\r\n\r\nFor other operating systems, I'm sorry: I don't use them...  I believe \"gzip\" should know how to deal with that file.","first_name":"William","6":"William","last_name":"Natter","7":"Natter","releases":[{"0":"842","vim_version":"7.0","1":"7.0","script_version":"1.1","2":"1.1","version_comment":"Added support for hexadecimal and octal bases, and for right-alignment","3":"Added support for hexadecimal and octal bases, and for right-alignment","package":"increment.vim","4":"increment.vim","src_id":"7541","5":"7541","creation_date":"1187694497","6":"1187694497"},{"0":"842","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"increment.tar.gz","4":"increment.tar.gz","src_id":"2542","5":"2542","creation_date":"1070525812","6":"1070525812"}]},"841":{"script_id":"841","0":"841","script_name":"yo-speller","1":"yo-speller","script_type":"utility","2":"utility","summary":"NOTE: this only for russian users! Spell YO letter in the buffer.","3":"NOTE: this only for russian users! Spell YO letter in the buffer.","description":"Russian home-page of this project is http:\/\/python.anabar.ru\/yo.htm\r\nThere you can find analogous macros for XEmacs writen by me in ELisp.\r\n\r\nThis programs check russhian text to find words with E letter and chage to the YO letter if needed. For example: \"avtogidropod'emnik\" -> \"avtogidropodyomnik\". Words were letter yo must be, changed silently. And if this word may be with yo and may be without (vse-vsyo, chem-chyom) there are prompt a dialog.\r\n\r\nScript correctly work with case: \"Word\" change to \"Another\", \"word\" to \"another\" and \"WORD\" to \"ANOTHER\", \"wORd\" dont change, because it is no word :)\r\n\r\nExperiment show this if not very hard, because most of word chanded automatically. The database contain 60000 words (in all cases)","4":"Russian home-page of this project is http:\/\/python.anabar.ru\/yo.htm\r\nThere you can find analogous macros for XEmacs writen by me in ELisp.\r\n\r\nThis programs check russhian text to find words with E letter and chage to the YO letter if needed. For example: \"avtogidropod'emnik\" -> \"avtogidropodyomnik\". Words were letter yo must be, changed silently. And if this word may be with yo and may be without (vse-vsyo, chem-chyom) there are prompt a dialog.\r\n\r\nScript correctly work with case: \"Word\" change to \"Another\", \"word\" to \"another\" and \"WORD\" to \"ANOTHER\", \"wORd\" dont change, because it is no word :)\r\n\r\nExperiment show this if not very hard, because most of word chanded automatically. The database contain 60000 words (in all cases)","install_details":"First step: install text.py utility from this site: vimscript#840\r\n\r\nSecond and last: open yo.py and change path in first line. There must be absolutly path to your yo.dat file, like this:\r\n\r\nyo_path = r\"...\\Vim\\python\\yo.dat\"    # FIXME here\r\n\r\nThen you can use it: open your russhian file and run the command\r\n:pyf <path_if_necessary>yo.py\r\n\r\nIf you need to change yo base, edit yo.txt file, changes are apply automatically","5":"First step: install text.py utility from this site: vimscript#840\r\n\r\nSecond and last: open yo.py and change path in first line. There must be absolutly path to your yo.dat file, like this:\r\n\r\nyo_path = r\"...\\Vim\\python\\yo.dat\"    # FIXME here\r\n\r\nThen you can use it: open your russhian file and run the command\r\n:pyf <path_if_necessary>yo.py\r\n\r\nIf you need to change yo base, edit yo.txt file, changes are apply automatically","first_name":"Eugene","6":"Eugene","last_name":"Minkovskii","7":"Minkovskii","releases":[{"0":"841","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"More simple installation, more simple update yo-base, more faster initialization when you call macros second time.","3":"More simple installation, more simple update yo-base, more faster initialization when you call macros second time.","package":"yobase.ZIP","4":"yobase.ZIP","src_id":"2597","5":"2597","creation_date":"1071466297","6":"1071466297"},{"0":"841","vim_version":"6.0","1":"6.0","script_version":"0.0","2":"0.0","version_comment":"Initial upload","3":"Initial upload","package":"yobase.zip","4":"yobase.zip","src_id":"2541","5":"2541","creation_date":"1070522350","6":"1070522350"}]},"840":{"script_id":"840","0":"840","script_name":"text.py","1":"text.py","script_type":"utility","2":"utility","summary":"This is utility to easy access to vim buffer. For pythonic macrowriters","3":"This is utility to easy access to vim buffer. For pythonic macrowriters","description":"This is text.py module for easy association of vim buffer to python language. Module provides Text-calss, which has access vim buffer contents, and has many of string, sequense and file-object methods. You may use slice, may use assignment to slice of buffer, and you can use step argument in this assignment in python 2.3 notation. You can use all of string methods like .upper(), .lower(), .center() etc. You can use many of sequence methods like .append(), .extend(), .reverse() etc. You can use a lot of binary operators like +=, *=; membership test \"in\" etc. Moreover, Text-instance provide some facilities to work with regular expressions including situations when text in buffer is in multibyte encoding. Searching takes place in unicode, but module provides some new match object: \"NoUniMatchObj\". This object has all of original match objects attributes but when you expect to get a string, you get a string not unicode. And when you expect to get address (byte-offset) you get address in encoded string too.\r\n\r\nSimple example:\r\n~~~~~~~~~~~~~~~\r\nimport text\r\nt = text.Text()\r\nfor i in t.re.finditer(my_regexp):    # search my_regexp in buffer\r\n    try:\r\n        t.replace_i(i.start(),            # interactive replace fragment of\r\n                    i.end(),              #   buffer from i.start() to i.end()\r\n                                          #   where i is an instance of\r\n                                          #   NoUniMatchObj\r\n                    [\"replasement one\",   # There are a lot of substitutions,\r\n                     my_function(i), ...])#   user can choose one of them.\r\n    except t.exceptions.CancelDialog:\r\n        pass                            # handler of Cancel button\r\nt.center(80)                            # centering contents of buffer\r\nt.apply_to_lines(my_other_function)     # apply my_other_function line by line \r\n\r\nAnother powerful example you can see in vimscript#841\r\n\r\nThis utility very useful if you need to do python-substitution using confirmation dialogs, for example if you need to choose a lot of various replacements. This is useful too if you work with utf-8 encoding etc.\r\n\r\nRussian mirror: http:\/\/python.anabar.ru\/emin.htm#textpy\r\n","4":"This is text.py module for easy association of vim buffer to python language. Module provides Text-calss, which has access vim buffer contents, and has many of string, sequense and file-object methods. You may use slice, may use assignment to slice of buffer, and you can use step argument in this assignment in python 2.3 notation. You can use all of string methods like .upper(), .lower(), .center() etc. You can use many of sequence methods like .append(), .extend(), .reverse() etc. You can use a lot of binary operators like +=, *=; membership test \"in\" etc. Moreover, Text-instance provide some facilities to work with regular expressions including situations when text in buffer is in multibyte encoding. Searching takes place in unicode, but module provides some new match object: \"NoUniMatchObj\". This object has all of original match objects attributes but when you expect to get a string, you get a string not unicode. And when you expect to get address (byte-offset) you get address in encoded string too.\r\n\r\nSimple example:\r\n~~~~~~~~~~~~~~~\r\nimport text\r\nt = text.Text()\r\nfor i in t.re.finditer(my_regexp):    # search my_regexp in buffer\r\n    try:\r\n        t.replace_i(i.start(),            # interactive replace fragment of\r\n                    i.end(),              #   buffer from i.start() to i.end()\r\n                                          #   where i is an instance of\r\n                                          #   NoUniMatchObj\r\n                    [\"replasement one\",   # There are a lot of substitutions,\r\n                     my_function(i), ...])#   user can choose one of them.\r\n    except t.exceptions.CancelDialog:\r\n        pass                            # handler of Cancel button\r\nt.center(80)                            # centering contents of buffer\r\nt.apply_to_lines(my_other_function)     # apply my_other_function line by line \r\n\r\nAnother powerful example you can see in vimscript#841\r\n\r\nThis utility very useful if you need to do python-substitution using confirmation dialogs, for example if you need to choose a lot of various replacements. This is useful too if you work with utf-8 encoding etc.\r\n\r\nRussian mirror: http:\/\/python.anabar.ru\/emin.htm#textpy\r\n","install_details":"1) Make in your harddrive some directory for python-vim programs (let it name   is \/pythonvim\/). And put text.py into this directory.\r\n2) Instract python to use this directory like sourse of modules. One way to   do this is put following string into your .vimrc file:\r\n:py import sys; sys.path.insert(0, r\"\/pythonvim\/\")\r\n   NOTE: in some systems you must put absolute address into sys.path list.\r\n   NOTE: be careful about slash direction, this is system-depended.\r\n\r\nThat is all. Happy vimming.\r\n\r\n--------------------------------------------------------------------------------\r\nCompatibility note:\r\n\r\nThis program writen for Python 2.3. But it is already compatible with\r\nPython 2.2. And for compatibility with Python 2.1 you may do some actions:\r\nsome code need to be comment and some to uncomment.\r\n\r\nFor compatibility with python 2.1 open this program in vim and execute\r\n  following command:\r\n:%s\/^\\(\\s*\\)\\(.*#<p21c>\\)$\/\\1## \\2\/|%s\/^\\(\\s*\\)##\\s\\+\\(.*#<p21u>\\)$\/\\1\\2\/|w!\r\nBe careful, use copy&paste:\r\n      1) put cursor after the colon and type y$\r\n      2) Then type : to go into command line and type <C-R>\"\r\nThis command comment section using 'yield' statement and import generators\r\n  feature. Then it is uncomment compatibility blocks: raise instraction in\r\n  finditer() method and import nested_scopes feature.\r\nFor undoing this changes execute in vim following command:\r\n:%s\/^\\(\\s*\\)\\(.*#<p21u>\\)$\/\\1## \\2\/|%s\/^\\(\\s*\\)##\\s\\+\\(.*#<p21c>\\)$\/\\1\\2\/|w!\r\n ","5":"1) Make in your harddrive some directory for python-vim programs (let it name   is \/pythonvim\/). And put text.py into this directory.\r\n2) Instract python to use this directory like sourse of modules. One way to   do this is put following string into your .vimrc file:\r\n:py import sys; sys.path.insert(0, r\"\/pythonvim\/\")\r\n   NOTE: in some systems you must put absolute address into sys.path list.\r\n   NOTE: be careful about slash direction, this is system-depended.\r\n\r\nThat is all. Happy vimming.\r\n\r\n--------------------------------------------------------------------------------\r\nCompatibility note:\r\n\r\nThis program writen for Python 2.3. But it is already compatible with\r\nPython 2.2. And for compatibility with Python 2.1 you may do some actions:\r\nsome code need to be comment and some to uncomment.\r\n\r\nFor compatibility with python 2.1 open this program in vim and execute\r\n  following command:\r\n:%s\/^\\(\\s*\\)\\(.*#<p21c>\\)$\/\\1## \\2\/|%s\/^\\(\\s*\\)##\\s\\+\\(.*#<p21u>\\)$\/\\1\\2\/|w!\r\nBe careful, use copy&paste:\r\n      1) put cursor after the colon and type y$\r\n      2) Then type : to go into command line and type <C-R>\"\r\nThis command comment section using 'yield' statement and import generators\r\n  feature. Then it is uncomment compatibility blocks: raise instraction in\r\n  finditer() method and import nested_scopes feature.\r\nFor undoing this changes execute in vim following command:\r\n:%s\/^\\(\\s*\\)\\(.*#<p21u>\\)$\/\\1## \\2\/|%s\/^\\(\\s*\\)##\\s\\+\\(.*#<p21c>\\)$\/\\1\\2\/|w!\r\n ","first_name":"Eugene","6":"Eugene","last_name":"Minkovskii","7":"Minkovskii","releases":[{"0":"840","vim_version":"6.0","1":"6.0","script_version":"1.0.4","2":"1.0.4","version_comment":"1.0.4 -- Some spell check of documentation. Thanks to all helpers.\r\n         new raise instractions with some help for developers.\r\n         Bugfix in re.subn() method.","3":"1.0.4 -- Some spell check of documentation. Thanks to all helpers.\r\n         new raise instractions with some help for developers.\r\n         Bugfix in re.subn() method.","package":"text104.zip","4":"text104.zip","src_id":"2571","5":"2571","creation_date":"1070854588","6":"1070854588"},{"0":"840","vim_version":"6.0","1":"6.0","script_version":"1.0.3","2":"1.0.3","version_comment":"Initial upload","3":"Initial upload","package":"text103.zip","4":"text103.zip","src_id":"2540","5":"2540","creation_date":"1070511575","6":"1070511575"}]},"839":{"script_id":"839","0":"839","script_name":"python.vim","1":"python.vim","script_type":"color scheme","2":"color scheme","summary":"'python' colour scheme","3":"'python' colour scheme","description":"Only supports gvim, because there is not much you can do with only 2 shades of green in cterm. \r\n\r\nA colour scheme for people editing python, its very 'green' and 'pythonic', its also very 'untidy' and 'unfinished'. The next version should be alot cleaner.\r\n\r\nps: I modified an existing colour scheme I already had installed, I cannot remember which, so If you recognise your own work, umm.. get over it :) ","4":"Only supports gvim, because there is not much you can do with only 2 shades of green in cterm. \r\n\r\nA colour scheme for people editing python, its very 'green' and 'pythonic', its also very 'untidy' and 'unfinished'. The next version should be alot cleaner.\r\n\r\nps: I modified an existing colour scheme I already had installed, I cannot remember which, so If you recognise your own work, umm.. get over it :) ","install_details":"drop it into .vim\/colors","5":"drop it into .vim\/colors","first_name":"Timothy","6":"Timothy","last_name":"Stebbing","7":"Stebbing","releases":[{"0":"839","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"python.vim","4":"python.vim","src_id":"2538","5":"2538","creation_date":"1070482141","6":"1070482141"}]},"838":{"script_id":"838","0":"838","script_name":"macro.vim","1":"macro.vim","script_type":"syntax","2":"syntax","summary":"Syntax coloring for (VAX) Macro assembly","3":"Syntax coloring for (VAX) Macro assembly","description":"Provides syntax coloring for (VAX) Macro and\/or Macro32 source code.","4":"Provides syntax coloring for (VAX) Macro and\/or Macro32 source code.","install_details":"Unpack the tarball and place \"macro.vim\" in <vimruntime>\/syntax\/macro.vim.\r\n\r\n\"filetype.vim.diff\" contains a \"diff -u\" of the \"filetype.vim\" script. It adds the capability to recognize Macro files (extension \".mar\") or hazard a guess on the \".mac\" extension.","5":"Unpack the tarball and place \"macro.vim\" in <vimruntime>\/syntax\/macro.vim.\r\n\r\n\"filetype.vim.diff\" contains a \"diff -u\" of the \"filetype.vim\" script. It adds the capability to recognize Macro files (extension \".mar\") or hazard a guess on the \".mac\" extension.","first_name":"tom","6":"tom","last_name":"uijldert","7":"uijldert","releases":[{"0":"838","vim_version":"5.7","1":"5.7","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"macro.tgz","4":"macro.tgz","src_id":"2537","5":"2537","creation_date":"1070330983","6":"1070330983"}]},"837":{"script_id":"837","0":"837","script_name":"PureBasic Syntax file","1":"PureBasic Syntax file","script_type":"syntax","2":"syntax","summary":"Syntax highlighting for PureBasic","3":"Syntax highlighting for PureBasic","description":"All keywords and predefined functions are highlighted as well as type suffixes, constants and numbers. The folding of procedures still needs some tweaking.\r\n","4":"All keywords and predefined functions are highlighted as well as type suffixes, constants and numbers. The folding of procedures still needs some tweaking.\r\n","install_details":"besides copying the file into the syntax directory and additional entry for filetype.vim has to be made, associating the extension pb:\r\n\r\n\"PureBasic\r\nau BufNewFile,BufRead *.pb setf purebasic","5":"besides copying the file into the syntax directory and additional entry for filetype.vim has to be made, associating the extension pb:\r\n\r\n\"PureBasic\r\nau BufNewFile,BufRead *.pb setf purebasic","first_name":"Guido","6":"Guido","last_name":"Treutwein","7":"Treutwein","releases":[{"0":"837","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"purebasic.vim","4":"purebasic.vim","src_id":"2534","5":"2534","creation_date":"1070245980","6":"1070245980"}]},"836":{"script_id":"836","0":"836","script_name":"selected-resizer","1":"selected-resizer","script_type":"utility","2":"utility","summary":"resizes a window to the selected block of text","3":"resizes a window to the selected block of text","description":"This script allows you to highlight some text and then hit Control-r to automatically change the size of the window to the area of the selected text.","4":"This script allows you to highlight some text and then hit Control-r to automatically change the size of the window to the area of the selected text.","install_details":"Put selected-resizer.vim in your vim\/plugins directory or :source it.","5":"Put selected-resizer.vim in your vim\/plugins directory or :source it.","first_name":"ryan","6":"ryan","last_name":"kulla","7":"kulla","releases":[{"0":"836","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"selected-resizer.vim","4":"selected-resizer.vim","src_id":"2533","5":"2533","creation_date":"1070234988","6":"1070234988"}]},"835":{"script_id":"835","0":"835","script_name":"systemc_syntax.tar.gz","1":"systemc_syntax.tar.gz","script_type":"syntax","2":"syntax","summary":"Syntax file for SystemC files","3":"Syntax file for SystemC files","description":"This download contains vim syntax files for SystemC.\r\nIf you are wondering what SystemC is:\r\n1. Visit www.systemc.org\r\n2. You probably don't need this package","4":"This download contains vim syntax files for SystemC.\r\nIf you are wondering what SystemC is:\r\n1. Visit www.systemc.org\r\n2. You probably don't need this package","install_details":"Refer to the README in the package for install details.","5":"Refer to the README in the package for install details.","first_name":"Karthick","6":"Karthick","last_name":"Gururaj","7":"Gururaj","releases":[{"0":"835","vim_version":"6.0","1":"6.0","script_version":"1.1","2":"1.1","version_comment":"Removed an empty systemc_syntax.tar that crept into the main package","3":"Removed an empty systemc_syntax.tar that crept into the main package","package":"systemc_syntax.tar.gz","4":"systemc_syntax.tar.gz","src_id":"2536","5":"2536","creation_date":"1070318080","6":"1070318080"},{"0":"835","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"systemc_syntax.tar.gz","4":"systemc_syntax.tar.gz","src_id":"2531","5":"2531","creation_date":"1070171593","6":"1070171593"}]},"834":{"script_id":"834","0":"834","script_name":"RTF 1.6 Spec in Vim Help Format","1":"RTF 1.6 Spec in Vim Help Format","script_type":"utility","2":"utility","summary":"Specification of RTF in easy and fast Vim help format.","3":"Specification of RTF in easy and fast Vim help format.","description":"Specification of most widely understand format of word processor file format.","4":"Specification of most widely understand format of word processor file format.","install_details":":help add-local-help","5":":help add-local-help","first_name":"Mikolaj","6":"Mikolaj","last_name":"Machowski","7":"Machowski","releases":[{"0":"834","vim_version":"6.0","1":"6.0","script_version":"1.8","2":"1.8","version_comment":"Initial upload","3":"Initial upload","package":"rtf16.zip","4":"rtf16.zip","src_id":"2528","5":"2528","creation_date":"1070104263","6":"1070104263"}]},"833":{"script_id":"833","0":"833","script_name":"httpclog","1":"httpclog","script_type":"syntax","2":"syntax","summary":"Syntax highlighting for a combined http log file","3":"Syntax highlighting for a combined http log file","description":"This syntax file highlights apache logs, specifically the \"combined\" format ones.  The \"combined\" format includes the user agent and the referrer in the logfile.  This version is very basic.","4":"This syntax file highlights apache logs, specifically the \"combined\" format ones.  The \"combined\" format includes the user agent and the referrer in the logfile.  This version is very basic.","install_details":"Upload the script to your vimfiles\/syntax directory.\r\nAdd the following to your .vimrc or filetype.vim:\r\n\r\naugroup filetypedetect\r\n\tau BufNewFile,BufRead access.log*\tsetf httpclog\r\naugroup END","5":"Upload the script to your vimfiles\/syntax directory.\r\nAdd the following to your .vimrc or filetype.vim:\r\n\r\naugroup filetypedetect\r\n\tau BufNewFile,BufRead access.log*\tsetf httpclog\r\naugroup END","first_name":"Ben","6":"Ben","last_name":"Damm","7":"Damm","releases":[{"0":"833","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"httpclog.vim","4":"httpclog.vim","src_id":"2524","5":"2524","creation_date":"1070031112","6":"1070031112"}]},"832":{"script_id":"832","0":"832","script_name":"smartmake","1":"smartmake","script_type":"utility","2":"utility","summary":"A somehow smarter version of the make command","3":"A somehow smarter version of the make command","description":"This plugin provides a smart version of the :make command: Before running the compiler, it scans the current and all parent directories to figure out which compiler to use. It provides a command called \"SmartMake\". When neither \"no_plugin_maps\" nor \"no_smartmake_maps\" are set F7 will be bound to that command. Currently supported compile flavours: make, ant and nant.","4":"This plugin provides a smart version of the :make command: Before running the compiler, it scans the current and all parent directories to figure out which compiler to use. It provides a command called \"SmartMake\". When neither \"no_plugin_maps\" nor \"no_smartmake_maps\" are set F7 will be bound to that command. Currently supported compile flavours: make, ant and nant.","install_details":"Just copy it into your plugin-Directory (e.g. $HOME\/.vim\/plugins).","5":"Just copy it into your plugin-Directory (e.g. $HOME\/.vim\/plugins).","first_name":"Mathias","6":"Mathias","last_name":"Hasselmann","7":"Hasselmann","releases":[{"0":"832","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"smartmake.vim","4":"smartmake.vim","src_id":"2523","5":"2523","creation_date":"1069923024","6":"1069923024"}]},"831":{"script_id":"831","0":"831","script_name":"xmaslights.vim","1":"xmaslights.vim","script_type":"color scheme","2":"color scheme","summary":"Make your text appear as animated Christmas lights","3":"Make your text appear as animated Christmas lights","description":"xmaslights.vim is a Python script for Vim that make your text appear as animated Christmas lights.  It changes the color of the different syntax highliting components randomly on a timer\/loop.  It was tested with the win32 gvim binary and may need modification to work on other platforms.","4":"xmaslights.vim is a Python script for Vim that make your text appear as animated Christmas lights.  It changes the color of the different syntax highliting components randomly on a timer\/loop.  It was tested with the win32 gvim binary and may need modification to work on other platforms.","install_details":"Save the file to your .vim\/plugins directory or load it with :source xmaslights.vim .\r\n\r\nstart it in vim with the command \":py xmas()\"","5":"Save the file to your .vim\/plugins directory or load it with :source xmaslights.vim .\r\n\r\nstart it in vim with the command \":py xmas()\"","first_name":"ryan","6":"ryan","last_name":"kulla","7":"kulla","releases":[{"0":"831","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"xmaslights.vim","4":"xmaslights.vim","src_id":"2521","5":"2521","creation_date":"1069881332","6":"1069881332"}]},"830":{"script_id":"830","0":"830","script_name":"TT2 syntax","1":"TT2 syntax","script_type":"syntax","2":"syntax","summary":" Syntax Highlight for Template-Toolkit 2.x","3":" Syntax Highlight for Template-Toolkit 2.x","description":"* THIS SCRIPT WILL BE NO LONGER MAINTAINED *\r\nMaintainer was handed over. Please visit below to find updated version.\r\nhttp:\/\/github.com\/petdance\/vim-perl\r\n\r\nSyntax Highlight for Template-Toolkit 2.x\r\n( http:\/\/search.cpan.org\/~abw\/Template-Toolkit\/ )\r\n Contain Perl code in PERL\/RAWPERL directive. (runtime sytax\/perl.vim)\r\n No fold.\r\n HTML syntax for including TT2 syntax. ( tt2html.vim \/ unfinished )\r\n Can define START_TAG\/END_TAG for your style.\r\n","4":"* THIS SCRIPT WILL BE NO LONGER MAINTAINED *\r\nMaintainer was handed over. Please visit below to find updated version.\r\nhttp:\/\/github.com\/petdance\/vim-perl\r\n\r\nSyntax Highlight for Template-Toolkit 2.x\r\n( http:\/\/search.cpan.org\/~abw\/Template-Toolkit\/ )\r\n Contain Perl code in PERL\/RAWPERL directive. (runtime sytax\/perl.vim)\r\n No fold.\r\n HTML syntax for including TT2 syntax. ( tt2html.vim \/ unfinished )\r\n Can define START_TAG\/END_TAG for your style.\r\n","install_details":"Add this lines in your \"filetype.vim\":\r\n\r\nau BufNewFile,BufRead *.tt2 call s:AdjustTT2Type()\r\n\r\nfunc! s:AdjustTT2Type()\r\n    if ( getline(1) . getline(2) . getline(3) =~ '<\\chtml'\r\n              && getline(1) . getline(2) . getline(3) !~ '<[%?]' )\r\n       || getline(1) =~ '<!DOCTYPE HTML'\r\n        setf tt2html\r\n    else\r\n        setf tt2\r\n    endif \r\nendfunc\r\n\r\nTo define START_TAG and END_TAG you like, you can set any pair of tags to 'b:tt2_syn_tags':\r\n    \"ASP\"\r\n    :let b:tt2_syn_tags = '<% %>'\r\n    \"PHP\"\r\n    :let b:tt2_syn_tags = '<? ?>'\r\n    \"TT2 and HTML\"\r\n    :let b:tt2_syn_tags = '\\[% %] <!-- -->'\r\n","5":"Add this lines in your \"filetype.vim\":\r\n\r\nau BufNewFile,BufRead *.tt2 call s:AdjustTT2Type()\r\n\r\nfunc! s:AdjustTT2Type()\r\n    if ( getline(1) . getline(2) . getline(3) =~ '<\\chtml'\r\n              && getline(1) . getline(2) . getline(3) !~ '<[%?]' )\r\n       || getline(1) =~ '<!DOCTYPE HTML'\r\n        setf tt2html\r\n    else\r\n        setf tt2\r\n    endif \r\nendfunc\r\n\r\nTo define START_TAG and END_TAG you like, you can set any pair of tags to 'b:tt2_syn_tags':\r\n    \"ASP\"\r\n    :let b:tt2_syn_tags = '<% %>'\r\n    \"PHP\"\r\n    :let b:tt2_syn_tags = '<? ?>'\r\n    \"TT2 and HTML\"\r\n    :let b:tt2_syn_tags = '\\[% %] <!-- -->'\r\n","first_name":"atsushi","6":"atsushi","last_name":"moriki","7":"moriki","releases":[{"0":"830","vim_version":"6.0","1":"6.0","script_version":"0.1.3","2":"0.1.3","version_comment":"Changed fileformat from 'dos' to 'unix'\r\nDeleted 'echo' that print obstructive message","3":"Changed fileformat from 'dos' to 'unix'\r\nDeleted 'echo' that print obstructive message","package":"tt2.tar.gz","4":"tt2.tar.gz","src_id":"6881","5":"6881","creation_date":"1173964587","6":"1173964587"},{"0":"830","vim_version":"6.0","1":"6.0","script_version":"0.1.3","2":"0.1.3","version_comment":"Changed fileformat from 'dos' to 'unix'\r\nDeleted 'echo' that print obstructive message","3":"Changed fileformat from 'dos' to 'unix'\r\nDeleted 'echo' that print obstructive message","package":"tt2.zip","4":"tt2.zip","src_id":"6880","5":"6880","creation_date":"1173964551","6":"1173964551"},{"0":"830","vim_version":"6.0","1":"6.0","script_version":"0.1.2","2":"0.1.2","version_comment":"full-directive comment, lower case reserved words.","3":"full-directive comment, lower case reserved words.","package":"tt2.tar.gz","4":"tt2.tar.gz","src_id":"2647","5":"2647","creation_date":"1073041915","6":"1073041915"},{"0":"830","vim_version":"6.0","1":"6.0","script_version":"0.1.2","2":"0.1.2","version_comment":"full-directive comment, lower case reserved words, upload zip-archive.","3":"full-directive comment, lower case reserved words, upload zip-archive.","package":"tt2.zip","4":"tt2.zip","src_id":"2646","5":"2646","creation_date":"1073041871","6":"1073041871"},{"0":"830","vim_version":"6.0","1":"6.0","script_version":"0.1.1","2":"0.1.1","version_comment":"Initial upload","3":"Initial upload","package":"tt2.tar.gz","4":"tt2.tar.gz","src_id":"2519","5":"2519","creation_date":"1069797021","6":"1069797021"}]},"829":{"script_id":"829","0":"829","script_name":"gq","1":"gq","script_type":"utility","2":"utility","summary":"Multipurpose e-mail message beautifier","3":"Multipurpose e-mail message beautifier","description":"gq.vim provides shortcut \"q\", a variant on Vim's built-in beautifier\r\n\"gq\" with enhanced e-mail support. Use it just as you'd use \"gq\" when\r\nin Visual mode. - Features:\r\n\r\n - It's capable of dealing with lists being part of quotations.\r\n   (Vim's 'comments' engine \"gq\" depends on can't do this.)\r\n - Quote marks may appear in conjunction with enclosed initials\r\n   denoting the author's name.\r\n - It can perform basic tasks on malformed quoting-markup. (remove\r\n   enclosed whitespace, reposition initials, convert badly wrapped\r\n   lines)\r\n - It's configurable. (Have a look at gq.vim to see how this can be\r\n   accomplished..)\r\n\r\nA quote sample to illustrate how it works..\r\n\r\n  > AB> > 1. qtqt qtqtq. qtqtqt qtqtqt qtqtq tqtqt tqqtt qtqt qtqt.\r\n  > >AB > 2. qtqt qtqtq. qtqtqt qtqtqt qtqtq tqtqt tqqtt qtqt qtqt.\r\n  >CD > - qtqt qtqtq qtqtqt qtqtqt qtqtq, tqtqt tqqtt qtqt qtqt.\r\n  > CD> * qtqt qtqtq qtqtqt qtqtqt qtqtq, tqtqt tqqtt qtqt qtqt.\r\n  > qtqt qtqtq qtqtqt. qtqtqt qtqtq tqtqt, tqqtt qtqt qtqt qtqt qt\r\n  qtqt qtqtqt.\r\n\r\n\r\n\"Vipgq\" (:setl fo=tcrqn ai com=n:>,fb:-,fb:* tw=36):\r\n\r\n  > AB> > 1. qtqt qtqtq. qtqtqt\r\n  > qtqtqt qtqtq tqtqt tqqtt qtqt\r\n  > qtqt.\r\n  > >AB > 2. qtqt qtqtq. qtqtqt\r\n  > >qtqtqt qtqtq tqtqt tqqtt qtqt\r\n  > >qtqt.\r\n  >CD > - qtqt qtqtq qtqtqt qtqtqt\r\n  >qtqtq, tqtqt tqqtt qtqt qtqt.\r\n  >CD> * qtqt qtqtq qtqtqt qtqtqt\r\n  >qtqtq, tqtqt tqqtt qtqt qtqt.\r\n  >qtqt qtqtq qtqtqt. qtqtqt qtqtq\r\n  >tqtqt, tqqtt qtqt qtqt qtqt qt\r\n  qtqt qtqtqt.\r\n\r\n\r\n\"Vipgq\" (:setl fo=tcrqn ai com=n:>,fb:-,fb:*,n:A,n:B,n:C,n:D tw=36):\r\n\r\n  > AB> > 1. qtqt qtqtq. qtqtqt\r\n  > AB> > qtqtqt qtqtq tqtqt tqqtt\r\n  > AB> > qtqt qtqt.\r\n  > >AB > 2. qtqt qtqtq. qtqtqt\r\n  > >AB > qtqtqt qtqtq tqtqt tqqtt\r\n  > >AB > qtqt qtqt.\r\n  >CD > - qtqt qtqtq qtqtqt qtqtqt\r\n  >CD > qtqtq, tqtqt tqqtt qtqt\r\n  >CD > qtqt.\r\n  > CD> * qtqt qtqtq qtqtqt qtqtqt\r\n  > CD> qtqtq, tqtqt tqqtt qtqt\r\n  > CD> qtqt.\r\n  > qtqt qtqtq qtqtqt. qtqtqt qtqtq\r\n  > tqtqt, tqqtt qtqt qtqt qtqt qt\r\n  qtqt qtqtqt.\r\n\r\n\r\n\"Vipq\" (:setl fo=tcqn ai com=n:>,fb:-,fb:* tw=36):\r\n\r\n  AB>>> 1. qtqt qtqtq. qtqtqt qtqtqt\r\n  AB>>>    qtqtq tqtqt tqqtt qtqt\r\n  AB>>>    qtqt.\r\n  AB>>> 2. qtqt qtqtq. qtqtqt qtqtqt\r\n  AB>>>    qtqtq tqtqt tqqtt qtqt\r\n  AB>>>    qtqt.\r\n  CD>> - qtqt qtqtq qtqtqt qtqtqt\r\n  CD>>   qtqtq, tqtqt tqqtt qtqt\r\n  CD>>   qtqt.\r\n  CD>> * qtqt qtqtq qtqtqt qtqtqt\r\n  CD>>   qtqtq, tqtqt tqqtt qtqt\r\n  CD>>   qtqt.\r\n  > qtqt qtqtq qtqtqt. qtqtqt qtqtq\r\n  > tqtqt, tqqtt qtqt qtqt qtqt qt\r\n  > qtqt qtqtqt.\r\n","4":"gq.vim provides shortcut \"q\", a variant on Vim's built-in beautifier\r\n\"gq\" with enhanced e-mail support. Use it just as you'd use \"gq\" when\r\nin Visual mode. - Features:\r\n\r\n - It's capable of dealing with lists being part of quotations.\r\n   (Vim's 'comments' engine \"gq\" depends on can't do this.)\r\n - Quote marks may appear in conjunction with enclosed initials\r\n   denoting the author's name.\r\n - It can perform basic tasks on malformed quoting-markup. (remove\r\n   enclosed whitespace, reposition initials, convert badly wrapped\r\n   lines)\r\n - It's configurable. (Have a look at gq.vim to see how this can be\r\n   accomplished..)\r\n\r\nA quote sample to illustrate how it works..\r\n\r\n  > AB> > 1. qtqt qtqtq. qtqtqt qtqtqt qtqtq tqtqt tqqtt qtqt qtqt.\r\n  > >AB > 2. qtqt qtqtq. qtqtqt qtqtqt qtqtq tqtqt tqqtt qtqt qtqt.\r\n  >CD > - qtqt qtqtq qtqtqt qtqtqt qtqtq, tqtqt tqqtt qtqt qtqt.\r\n  > CD> * qtqt qtqtq qtqtqt qtqtqt qtqtq, tqtqt tqqtt qtqt qtqt.\r\n  > qtqt qtqtq qtqtqt. qtqtqt qtqtq tqtqt, tqqtt qtqt qtqt qtqt qt\r\n  qtqt qtqtqt.\r\n\r\n\r\n\"Vipgq\" (:setl fo=tcrqn ai com=n:>,fb:-,fb:* tw=36):\r\n\r\n  > AB> > 1. qtqt qtqtq. qtqtqt\r\n  > qtqtqt qtqtq tqtqt tqqtt qtqt\r\n  > qtqt.\r\n  > >AB > 2. qtqt qtqtq. qtqtqt\r\n  > >qtqtqt qtqtq tqtqt tqqtt qtqt\r\n  > >qtqt.\r\n  >CD > - qtqt qtqtq qtqtqt qtqtqt\r\n  >qtqtq, tqtqt tqqtt qtqt qtqt.\r\n  >CD> * qtqt qtqtq qtqtqt qtqtqt\r\n  >qtqtq, tqtqt tqqtt qtqt qtqt.\r\n  >qtqt qtqtq qtqtqt. qtqtqt qtqtq\r\n  >tqtqt, tqqtt qtqt qtqt qtqt qt\r\n  qtqt qtqtqt.\r\n\r\n\r\n\"Vipgq\" (:setl fo=tcrqn ai com=n:>,fb:-,fb:*,n:A,n:B,n:C,n:D tw=36):\r\n\r\n  > AB> > 1. qtqt qtqtq. qtqtqt\r\n  > AB> > qtqtqt qtqtq tqtqt tqqtt\r\n  > AB> > qtqt qtqt.\r\n  > >AB > 2. qtqt qtqtq. qtqtqt\r\n  > >AB > qtqtqt qtqtq tqtqt tqqtt\r\n  > >AB > qtqt qtqt.\r\n  >CD > - qtqt qtqtq qtqtqt qtqtqt\r\n  >CD > qtqtq, tqtqt tqqtt qtqt\r\n  >CD > qtqt.\r\n  > CD> * qtqt qtqtq qtqtqt qtqtqt\r\n  > CD> qtqtq, tqtqt tqqtt qtqt\r\n  > CD> qtqt.\r\n  > qtqt qtqtq qtqtqt. qtqtqt qtqtq\r\n  > tqtqt, tqqtt qtqt qtqt qtqt qt\r\n  qtqt qtqtqt.\r\n\r\n\r\n\"Vipq\" (:setl fo=tcqn ai com=n:>,fb:-,fb:* tw=36):\r\n\r\n  AB>>> 1. qtqt qtqtq. qtqtqt qtqtqt\r\n  AB>>>    qtqtq tqtqt tqqtt qtqt\r\n  AB>>>    qtqt.\r\n  AB>>> 2. qtqt qtqtq. qtqtqt qtqtqt\r\n  AB>>>    qtqtq tqtqt tqqtt qtqt\r\n  AB>>>    qtqt.\r\n  CD>> - qtqt qtqtq qtqtqt qtqtqt\r\n  CD>>   qtqtq, tqtqt tqqtt qtqt\r\n  CD>>   qtqt.\r\n  CD>> * qtqt qtqtq qtqtqt qtqtqt\r\n  CD>>   qtqtq, tqtqt tqqtt qtqt\r\n  CD>>   qtqt.\r\n  > qtqt qtqtq qtqtqt. qtqtqt qtqtq\r\n  > tqtqt, tqqtt qtqt qtqt qtqt qt\r\n  > qtqt qtqtqt.\r\n","install_details":"Copy gq.vim to your plugin directory (see \":h add-global-plugin\") or,\r\nalternatively, issue \":so gq.vim\" prior to composing (for details see\r\n\":h load-vim-script\").\r\n","5":"Copy gq.vim to your plugin directory (see \":h add-global-plugin\") or,\r\nalternatively, issue \":so gq.vim\" prior to composing (for details see\r\n\":h load-vim-script\").\r\n","first_name":"Klaus","6":"Klaus","last_name":"Bosau","7":"Bosau","releases":[{"0":"829","vim_version":"6.0","1":"6.0","script_version":"0.91","2":"0.91","version_comment":"Just separated the markup engine. You may use \",r\" or \":requote\" now to fix up bad quoting for the whole file while keeping lines as long as they initially were.\r\n","3":"Just separated the markup engine. You may use \",r\" or \":requote\" now to fix up bad quoting for the whole file while keeping lines as long as they initially were.\r\n","package":"gq.vim","4":"gq.vim","src_id":"2974","5":"2974","creation_date":"1082818631","6":"1082818631"},{"0":"829","vim_version":"6.0","1":"6.0","script_version":"0.9","2":"0.9","version_comment":"Initial upload","3":"Initial upload","package":"gq.vim","4":"gq.vim","src_id":"2516","5":"2516","creation_date":"1069770709","6":"1069770709"}]},"828":{"script_id":"828","0":"828","script_name":"VimNotes","1":"VimNotes","script_type":"utility","2":"utility","summary":"A script to help keep an organized collection of notes with linking.","3":"A script to help keep an organized collection of notes with linking.","description":"This is a simple script that helps keep a collection of notes organized and allows vim help style linking. \r\n\r\nVimNotes will:\r\n1.  Automatically create an Index of links and display it in a Menu in Gvim.\r\n2.  Tag file is automatically regenerated every time a VimNote is saved.\r\n3.  \r\n\r\nVimNotes Configuration:  \r\n\r\nVimNotes has a few configuration options at the top of the VimNotes.vim file.\r\nYou should review these and make any desired changes.\r\n\r\nDefault Notes Directory:         \r\nby default all notes are kept in a single directory.\r\n\r\n  let g:VN_DefaultDir = \"~\/Notes\"\r\n\r\nFolds:\r\nVimNotes can be configured to fold note subsections (1) or not (0)\r\n\r\n  let g:VN_FoldEnable = \"1\"\r\n\r\n\r\nNote Header Configuration:\r\nThe default (\"d\") header will include filename, created date and last\r\nmodified date and by whom.  Or you can use a minimalist (\"m\") header.\r\n\r\n  let g:VN_Header = \"d\"\r\n\r\nNote Section Divider:\r\nSetting this to \"1\" will place a divider line of ---- between note sections.\r\nSetting it to \"0\", will disable a visible seperater.\r\n  let g:VN_SectionSep = \"1\"\r\n\r\nDefault Web Browser:\r\nVimNotes can open links in a browser of your choosing.\r\nExamples: \r\n  let g:VN_DefaultBrowser = \"konqueror\"\r\n  let g:VN_DefaultBrowser = \"links -g\"\r\n  let g:VN_DefaultBrowser = \"konsole -e lynx\"\r\n  let g:VN_DefaultBrowser = \"xterm -e lynx\"\r\n  let g:VN_DefaultBrowser = \"mozilla\"\r\n\r\nKeymappings:\r\nIf you would like to change any of the keymappings for this script,\r\nadd the following lines:\r\n               map <-key-to-use> <PLUG><-function-to-map>\r\n               map! <-key-to-use> <PLUG><-function-to-map>\r\nDefault Config:\r\n               VN_NewFile                    <F2>\r\n               VN_NewSection              <F3>\r\n               VN_Search                     <F4>\r\n               VN_OpenHTTPLink         <F5>\r\n      Note: VN_NewFile is always available, however VN_NewSection, \r\n               VN_Search, and VN_OpenHTTPLink are only available if the\r\n               current buffer is a VimNote.\r\n\r\n Example:\r\n               map  <F1> <Plug>VN_Search\r\n               map! <F1> <Plug>VN_Search\r\n\r\nCustomizing Syntax Colors:\r\n  You can link the group to an existing syntax group with this command:\r\n       highlight link <vimnotes-group>  <group>\r\n  You can find the available group names in your current syntax file:\r\n       \/usr\/local\/share\/vim\/vim62\/colors\/\r\nDefault Config:\r\n               highlight link VN_Bullet          Comment\r\n               highlight link VN_Checkbox        Function\r\n               highlight link VN_CheckboxDone    Comment\r\n               highlight link VN_HyperTextJump   Function\r\n               highlight link VN_HyperTextEntry  Identifier\r\n               highlight link VN_Divider         Comment\r\n               highlight link VN_Header          Comment\r\n               highlight link VN_HeaderTopic     Function\r\n               highlight link VN_HTTP            String\r\n               highlight link VN_NumberedList    Comment\r\n               highlight link VN_Topic           Comment\r\n\r\n","4":"This is a simple script that helps keep a collection of notes organized and allows vim help style linking. \r\n\r\nVimNotes will:\r\n1.  Automatically create an Index of links and display it in a Menu in Gvim.\r\n2.  Tag file is automatically regenerated every time a VimNote is saved.\r\n3.  \r\n\r\nVimNotes Configuration:  \r\n\r\nVimNotes has a few configuration options at the top of the VimNotes.vim file.\r\nYou should review these and make any desired changes.\r\n\r\nDefault Notes Directory:         \r\nby default all notes are kept in a single directory.\r\n\r\n  let g:VN_DefaultDir = \"~\/Notes\"\r\n\r\nFolds:\r\nVimNotes can be configured to fold note subsections (1) or not (0)\r\n\r\n  let g:VN_FoldEnable = \"1\"\r\n\r\n\r\nNote Header Configuration:\r\nThe default (\"d\") header will include filename, created date and last\r\nmodified date and by whom.  Or you can use a minimalist (\"m\") header.\r\n\r\n  let g:VN_Header = \"d\"\r\n\r\nNote Section Divider:\r\nSetting this to \"1\" will place a divider line of ---- between note sections.\r\nSetting it to \"0\", will disable a visible seperater.\r\n  let g:VN_SectionSep = \"1\"\r\n\r\nDefault Web Browser:\r\nVimNotes can open links in a browser of your choosing.\r\nExamples: \r\n  let g:VN_DefaultBrowser = \"konqueror\"\r\n  let g:VN_DefaultBrowser = \"links -g\"\r\n  let g:VN_DefaultBrowser = \"konsole -e lynx\"\r\n  let g:VN_DefaultBrowser = \"xterm -e lynx\"\r\n  let g:VN_DefaultBrowser = \"mozilla\"\r\n\r\nKeymappings:\r\nIf you would like to change any of the keymappings for this script,\r\nadd the following lines:\r\n               map <-key-to-use> <PLUG><-function-to-map>\r\n               map! <-key-to-use> <PLUG><-function-to-map>\r\nDefault Config:\r\n               VN_NewFile                    <F2>\r\n               VN_NewSection              <F3>\r\n               VN_Search                     <F4>\r\n               VN_OpenHTTPLink         <F5>\r\n      Note: VN_NewFile is always available, however VN_NewSection, \r\n               VN_Search, and VN_OpenHTTPLink are only available if the\r\n               current buffer is a VimNote.\r\n\r\n Example:\r\n               map  <F1> <Plug>VN_Search\r\n               map! <F1> <Plug>VN_Search\r\n\r\nCustomizing Syntax Colors:\r\n  You can link the group to an existing syntax group with this command:\r\n       highlight link <vimnotes-group>  <group>\r\n  You can find the available group names in your current syntax file:\r\n       \/usr\/local\/share\/vim\/vim62\/colors\/\r\nDefault Config:\r\n               highlight link VN_Bullet          Comment\r\n               highlight link VN_Checkbox        Function\r\n               highlight link VN_CheckboxDone    Comment\r\n               highlight link VN_HyperTextJump   Function\r\n               highlight link VN_HyperTextEntry  Identifier\r\n               highlight link VN_Divider         Comment\r\n               highlight link VN_Header          Comment\r\n               highlight link VN_HeaderTopic     Function\r\n               highlight link VN_HTTP            String\r\n               highlight link VN_NumberedList    Comment\r\n               highlight link VN_Topic           Comment\r\n\r\n","install_details":"Save the file to your .vim\/plugins directory or load it with :source Vimnotes.vim\r\n\r\nCreate default VimNotes directory (i.e. ~\/Notes).","5":"Save the file to your .vim\/plugins directory or load it with :source Vimnotes.vim\r\n\r\nCreate default VimNotes directory (i.e. ~\/Notes).","first_name":"Dave","6":"Dave","last_name":"Vehrs","7":"Vehrs","releases":[{"0":"828","vim_version":"6.0","1":"6.0","script_version":"0.2.6","2":"0.2.6","version_comment":"Patches submitted by Richard Bair including Win32 & glob fixes, and Gvim menu cleanups.  Many Thanks. ","3":"Patches submitted by Richard Bair including Win32 & glob fixes, and Gvim menu cleanups.  Many Thanks. ","package":"VimNotes.vim","4":"VimNotes.vim","src_id":"3090","5":"3090","creation_date":"1086113498","6":"1086113498"},{"0":"828","vim_version":"6.0","1":"6.0","script_version":"0.2.5","2":"0.2.5","version_comment":"Patches submited by Ronald Hoellwarth including modifiable file headerstrings and date format, Win32 support added to the VN_ProcTFM function and many vim syntax improvements & corrections.  Many Thanks.","3":"Patches submited by Ronald Hoellwarth including modifiable file headerstrings and date format, Win32 support added to the VN_ProcTFM function and many vim syntax improvements & corrections.  Many Thanks.","package":"VimNotes.vim","4":"VimNotes.vim","src_id":"2532","5":"2532","creation_date":"1070201736","6":"1070201736"},{"0":"828","vim_version":"6.0","1":"6.0","script_version":"0.2","2":"0.2","version_comment":"Added display of tag index for console.  Open list window by pressing F6.","3":"Added display of tag index for console.  Open list window by pressing F6.","package":"VimNotes.vim","4":"VimNotes.vim","src_id":"2518","5":"2518","creation_date":"1069782990","6":"1069782990"},{"0":"828","vim_version":"6.0","1":"6.0","script_version":"0.0","2":"0.0","version_comment":"Script documentation and example of a VimNote.","3":"Script documentation and example of a VimNote.","package":"VimNote-Docs.txt","4":"VimNote-Docs.txt","src_id":"2509","5":"2509","creation_date":"1069521734","6":"1069521734"},{"0":"828","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"VimNotes.vim","4":"VimNotes.vim","src_id":"2508","5":"2508","creation_date":"1069521649","6":"1069521649"}]},"827":{"script_id":"827","0":"827","script_name":"Intellisense : JSP Plugin","1":"Intellisense : JSP Plugin","script_type":"utility","2":"utility","summary":"Intellisense capability to JSP scripts","3":"Intellisense capability to JSP scripts","description":"This is the JSP plugin of Intellisense. \r\nYou need Intellisense core package for this to work, which you can download from http:\/\/insenvim.sourceforge.net or http:\/\/sourceforge.net\/projects\/insenvim.\r\nYou also need Java and HTML plugin for this to work.\r\nA new HTML plugin is available, and you should install it. It fixes one big problem.","4":"This is the JSP plugin of Intellisense. \r\nYou need Intellisense core package for this to work, which you can download from http:\/\/insenvim.sourceforge.net or http:\/\/sourceforge.net\/projects\/insenvim.\r\nYou also need Java and HTML plugin for this to work.\r\nA new HTML plugin is available, and you should install it. It fixes one big problem.","install_details":"Copy the jspft.dll to %VIM_INTELLISENSE% directory.\r\nCopy jsp_vis.vim to %VIMRUNTIME%\\ftplugin","5":"Copy the jspft.dll to %VIM_INTELLISENSE% directory.\r\nCopy jsp_vis.vim to %VIMRUNTIME%\\ftplugin","first_name":"Ravi","6":"Ravi","last_name":"Shankar","7":"Shankar","releases":[{"0":"827","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"jspft.zip","4":"jspft.zip","src_id":"2506","5":"2506","creation_date":"1069469244","6":"1069469244"}]},"826":{"script_id":"826","0":"826","script_name":"mp.vim","1":"mp.vim","script_type":"indent","2":"indent","summary":"Identation file for MetaPost","3":"Identation file for MetaPost","description":"This is identation file for MetaPost language. I'm not write same file for MetaFont only because I not use this powerfull program, but it is very similar to MetaPost language and if somebody ask me to write it I may be do this.\r\n\r\nSo this is citation from mp.vim where I wrote about indent in MetaPost\r\n\r\n\" Identation Rules: {{{1 \r\n\" First of all, MetaPost language don't expect any identation rules.\r\n\" This screept need for you only if you (not MetaPost) need to do\r\n\" exactly code. If you don't need to use indentation, see\r\n\" :help filetype-indent-off\r\n\"\r\n\" Note: Every rules of identation in MetaPost or TeX languages (and in some\r\n\" other of course) is very subjective. I can release only my vision of this\r\n\" promlem.\r\n\"\r\n\" ..........................................................................\r\n\" Example of correct (by me) identation {{{2\r\n\" shiftwidth=4\r\n\" ==========================================================================\r\n\" for i=0 upto 99:\r\n\"     z[i] = (0,1u) rotated (i*360\/100);\r\n\" endfor\r\n\" draw z0 -- z10 -- z20\r\n\"         withpen ...     % <- 2sw because breaked line\r\n\"         withcolor ...;  % <- same as previous\r\n\" draw z0 for i=1 upto 99:\r\n\"             -- z[i]             % <- 1sw from left end of 'for' satement\r\n\"         endfor withpen ...      % <- 0sw from left end of 'for' satement\r\n\"                 withcolor ...;  % <- 2sw because breaked line\r\n\" draw if One:     % <- This is internal if (like 'for' above)\r\n\"          one\r\n\"      elsif Other:\r\n\"          other\r\n\"      fi withpen ...;\r\n\" if one:          % <- This is external if\r\n\"     draw one;\r\n\" elseif other:\r\n\"     draw other;\r\n\" fi\r\n\" draw z0; draw z1;\r\n\" }}}\r\n\" }}}\r\n","4":"This is identation file for MetaPost language. I'm not write same file for MetaFont only because I not use this powerfull program, but it is very similar to MetaPost language and if somebody ask me to write it I may be do this.\r\n\r\nSo this is citation from mp.vim where I wrote about indent in MetaPost\r\n\r\n\" Identation Rules: {{{1 \r\n\" First of all, MetaPost language don't expect any identation rules.\r\n\" This screept need for you only if you (not MetaPost) need to do\r\n\" exactly code. If you don't need to use indentation, see\r\n\" :help filetype-indent-off\r\n\"\r\n\" Note: Every rules of identation in MetaPost or TeX languages (and in some\r\n\" other of course) is very subjective. I can release only my vision of this\r\n\" promlem.\r\n\"\r\n\" ..........................................................................\r\n\" Example of correct (by me) identation {{{2\r\n\" shiftwidth=4\r\n\" ==========================================================================\r\n\" for i=0 upto 99:\r\n\"     z[i] = (0,1u) rotated (i*360\/100);\r\n\" endfor\r\n\" draw z0 -- z10 -- z20\r\n\"         withpen ...     % <- 2sw because breaked line\r\n\"         withcolor ...;  % <- same as previous\r\n\" draw z0 for i=1 upto 99:\r\n\"             -- z[i]             % <- 1sw from left end of 'for' satement\r\n\"         endfor withpen ...      % <- 0sw from left end of 'for' satement\r\n\"                 withcolor ...;  % <- 2sw because breaked line\r\n\" draw if One:     % <- This is internal if (like 'for' above)\r\n\"          one\r\n\"      elsif Other:\r\n\"          other\r\n\"      fi withpen ...;\r\n\" if one:          % <- This is external if\r\n\"     draw one;\r\n\" elseif other:\r\n\"     draw other;\r\n\" fi\r\n\" draw z0; draw z1;\r\n\" }}}\r\n\" }}}\r\n","install_details":"Just put this file into $RUNTIMES\/ident\/ directory","5":"Just put this file into $RUNTIMES\/ident\/ directory","first_name":"Eugene","6":"Eugene","last_name":"Minkovskii","7":"Minkovskii","releases":[{"0":"826","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Bugfix","3":"Bugfix","package":"mp.vim","4":"mp.vim","src_id":"2503","5":"2503","creation_date":"1069380038","6":"1069380038"}]},"825":{"script_id":"825","0":"825","script_name":"find_in_files","1":"find_in_files","script_type":"utility","2":"utility","summary":"To find a string in the files in current directory","3":"To find a string in the files in current directory","description":"All of us when working in list of files come across the problem of searching for string in the files and then if the string is found, we manually open that file and go to a specific line. \r\n\r\nAll this can be done with a stroke of key using this script.\r\n\r\nThis script is used to find a string in files in current directory. This script copies the finding in a buffer and opens it in the same window. \r\n\r\nTo go to a particular line\/file in which the string is found. Click F2 on the top of the line in the buffer.\r\n\r\nProcedure:\r\n1. execute :CALL \"<string>\" in gvim\r\n\tThis will execute windows findstr command and will open the file in the same buffer\r\n2. Go to a line\/file in the new buffer that you want to open.\r\n3. Press F2\r\n\r\nResult:\r\nIt will open up a file in a same window and will go to that line.\r\n\r\nHow to Execute:\r\n1. :CALL \"<string>\"\r\n\tWill search for String in all the files in current dorectory\r\n2. Press <F3>, this will search all files in directory for string on which the cursor exists\r\n3. Press <F4>, this will seach current file for string on which the cursor exists.","4":"All of us when working in list of files come across the problem of searching for string in the files and then if the string is found, we manually open that file and go to a specific line. \r\n\r\nAll this can be done with a stroke of key using this script.\r\n\r\nThis script is used to find a string in files in current directory. This script copies the finding in a buffer and opens it in the same window. \r\n\r\nTo go to a particular line\/file in which the string is found. Click F2 on the top of the line in the buffer.\r\n\r\nProcedure:\r\n1. execute :CALL \"<string>\" in gvim\r\n\tThis will execute windows findstr command and will open the file in the same buffer\r\n2. Go to a line\/file in the new buffer that you want to open.\r\n3. Press F2\r\n\r\nResult:\r\nIt will open up a file in a same window and will go to that line.\r\n\r\nHow to Execute:\r\n1. :CALL \"<string>\"\r\n\tWill search for String in all the files in current dorectory\r\n2. Press <F3>, this will search all files in directory for string on which the cursor exists\r\n3. Press <F4>, this will seach current file for string on which the cursor exists.","install_details":"1. untar the file\r\n2. copy find_in_files.vim in plugin directory","5":"1. untar the file\r\n2. copy find_in_files.vim in plugin directory","first_name":"Sappy","6":"Sappy","last_name":"Goel","7":"Goel","releases":[{"0":"825","vim_version":"6.0","1":"6.0","script_version":"1.01","2":"1.01","version_comment":"changes to use grep and copen as suggested by Gary Johnson","3":"changes to use grep and copen as suggested by Gary Johnson","package":"find_in_files.zip","4":"find_in_files.zip","src_id":"2522","5":"2522","creation_date":"1069886762","6":"1069886762"},{"0":"825","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"find_in_files.zip","4":"find_in_files.zip","src_id":"2498","5":"2498","creation_date":"1069279581","6":"1069279581"}]},"824":{"script_id":"824","0":"824","script_name":"asmM68k.vim","1":"asmM68k.vim","script_type":"syntax","2":"syntax","summary":"ASM syntax file for Motorola 68k processors","3":"ASM syntax file for Motorola 68k processors","description":"Highlighting for M68K assembly keywords, does not highlight opcodes without a size postfix in order to reduce bugs.\r\nI\\\\\\'m sure there are better syntax files for the M68k, I just didn\\\\\\'t have any installed.","4":"Highlighting for M68K assembly keywords, does not highlight opcodes without a size postfix in order to reduce bugs.\r\nI\\\\\\'m sure there are better syntax files for the M68k, I just didn\\\\\\'t have any installed.","install_details":"put in ...\/syntax dir, and set $ASMSYNTAX env var.","5":"put in ...\/syntax dir, and set $ASMSYNTAX env var.","first_name":"Oyd E","6":"Oyd E","last_name":"Leven","7":"Leven","releases":[{"0":"824","vim_version":"5.7","1":"5.7","script_version":"0.01","2":"0.01","version_comment":"Initial upload","3":"Initial upload","package":"asmM68k.vim","4":"asmM68k.vim","src_id":"2492","5":"2492","creation_date":"1069140659","6":"1069140659"}]},"823":{"script_id":"823","0":"823","script_name":"yum.vim","1":"yum.vim","script_type":"syntax","2":"syntax","summary":"Syntax highlighting for yum.conf","3":"Syntax highlighting for yum.conf","description":"Provides syntax highlighting for yum.conf (Yellowdog Updater Modified) used by Fedora, ASP Linux, and others.","4":"Provides syntax highlighting for yum.conf (Yellowdog Updater Modified) used by Fedora, ASP Linux, and others.","install_details":"","5":"","first_name":"David","6":"David","last_name":"Necas","7":"Necas","releases":[{"0":"823","vim_version":"5.7","1":"5.7","script_version":"20031117","2":"20031117","version_comment":"Initial upload","3":"Initial upload","package":"yum.vim","4":"yum.vim","src_id":"2491","5":"2491","creation_date":"1069076970","6":"1069076970"}]},"822":{"script_id":"822","0":"822","script_name":"avrasm.vim","1":"avrasm.vim","script_type":"syntax","2":"syntax","summary":"Atmel AVR assembler syntax file","3":"Atmel AVR assembler syntax file","description":"Syntax file for Atmel AVR microcontrollers assembler. Please send your suggestions, comments, bug reports etc. to finn@sendmail.cz","4":"Syntax file for Atmel AVR microcontrollers assembler. Please send your suggestions, comments, bug reports etc. to finn@sendmail.cz","install_details":"For local installation put the avrasm.vim file in your ~\/.vim\/syntax directory, for global installation put it in $VIMRUNTIME\/syntax directory ","5":"For local installation put the avrasm.vim file in your ~\/.vim\/syntax directory, for global installation put it in $VIMRUNTIME\/syntax directory ","first_name":"Jan","6":"Jan","last_name":"N\u00c3\u00a1rovec","7":"N\u00c3\u00a1rovec","releases":[{"0":"822","vim_version":"6.0","1":"6.0","script_version":"0.2","2":"0.2","version_comment":"Added some instructions.","3":"Added some instructions.","package":"avrasm.vim","4":"avrasm.vim","src_id":"2670","5":"2670","creation_date":"1074747597","6":"1074747597"}]},"821":{"script_id":"821","0":"821","script_name":"BlockWork","1":"BlockWork","script_type":"utility","2":"utility","summary":"Adjust list numbering (increment) and other work with (visual) block selections","3":"Adjust list numbering (increment) and other work with (visual) block selections","description":"Function to Work with Selected Blocks --\r\nIncludes vmap assignments for incrementing, decrementing, and re-sequencing integers in a selected block.\r\n\r\nPurpose:\r\nSimplifies editing numbered lists or other sequences of numbers.  \r\nIncludes function to apply most any command to a selected 'visual block' of text.\r\n\r\nJustification:\r\nVim includes CTRL-A and CTRL-X to add and subtract from integers under the cursor, however neither of these works on selections.\r\nThere are search and replace techniques to handle multiple changes on a range of lines (e.g. s\/-\\?\\d\\+\/\\=submatch(0)+1\/g').\r\nHowever, this won't work on a 'visual block' selection.\r\n\r\nExample:\r\nThe first item was deleted from the following list,\r\nand you want to decrement all the numbers by 1.\r\n     2) show 35\r\n     3) show 19\r\n     4) show 85\r\n     ...\r\n   134) show 12\r\nUsing this plugin, you would position the cursor on the 2, \r\nselect the column of numbers, and decrement -- i.e. type:\r\n   <C-V>132jb<C-X> \r\n(where <C-V> and <C-X> are CTRL-V and CTRL-X respectively)\r\n\r\nRe-sequencing (To Automatically Correct A Sequence):\r\nThere is also a feature to re-sequence a selection of numbers (automatically eliminating all missing numbers).  Note that I've mapped the re-sequence function to <M-S-A> and <M-S-X>  (that's Alt plus Shift and A or X).  (The functional interface within the script allows easy adaptation for other scripters.)\r\n\r\nIssues and challenges with the techniques employed are discussed in the file.\r\n\r\n---\r\n2005-09-02: When I created this, I had imagined that I would update it a some point, but \r\nit has served me well since I had created it.  I mostly use this script to re-sequence numbers.\r\n\r\nNote that there are now at least four scripts that perform this functionality.\r\nvimscript #670 - visincr.vim - Charles E Campbell (along with vimtip #150, handles dates!!!)\r\nvimscript #145 - increment.vim - Stanislav Sitar\r\nvimscript #156 - increment.vim - Srinath Avadhanula\r\nvimscript #842 - increment.vim - William Natter (sequences on a substitution character)\r\nvimscript #189 - renumber.vim - Neil Bird (only re-sequences, but handles hex)\r\nvimscript #821 - blockwork.vim - John Aldridge\r\nvimscript #1046 - monday.vim - Stefan Karlsson (increments month and weekday names)\r\n\r\nSpeak up if there are others.","4":"Function to Work with Selected Blocks --\r\nIncludes vmap assignments for incrementing, decrementing, and re-sequencing integers in a selected block.\r\n\r\nPurpose:\r\nSimplifies editing numbered lists or other sequences of numbers.  \r\nIncludes function to apply most any command to a selected 'visual block' of text.\r\n\r\nJustification:\r\nVim includes CTRL-A and CTRL-X to add and subtract from integers under the cursor, however neither of these works on selections.\r\nThere are search and replace techniques to handle multiple changes on a range of lines (e.g. s\/-\\?\\d\\+\/\\=submatch(0)+1\/g').\r\nHowever, this won't work on a 'visual block' selection.\r\n\r\nExample:\r\nThe first item was deleted from the following list,\r\nand you want to decrement all the numbers by 1.\r\n     2) show 35\r\n     3) show 19\r\n     4) show 85\r\n     ...\r\n   134) show 12\r\nUsing this plugin, you would position the cursor on the 2, \r\nselect the column of numbers, and decrement -- i.e. type:\r\n   <C-V>132jb<C-X> \r\n(where <C-V> and <C-X> are CTRL-V and CTRL-X respectively)\r\n\r\nRe-sequencing (To Automatically Correct A Sequence):\r\nThere is also a feature to re-sequence a selection of numbers (automatically eliminating all missing numbers).  Note that I've mapped the re-sequence function to <M-S-A> and <M-S-X>  (that's Alt plus Shift and A or X).  (The functional interface within the script allows easy adaptation for other scripters.)\r\n\r\nIssues and challenges with the techniques employed are discussed in the file.\r\n\r\n---\r\n2005-09-02: When I created this, I had imagined that I would update it a some point, but \r\nit has served me well since I had created it.  I mostly use this script to re-sequence numbers.\r\n\r\nNote that there are now at least four scripts that perform this functionality.\r\nvimscript #670 - visincr.vim - Charles E Campbell (along with vimtip #150, handles dates!!!)\r\nvimscript #145 - increment.vim - Stanislav Sitar\r\nvimscript #156 - increment.vim - Srinath Avadhanula\r\nvimscript #842 - increment.vim - William Natter (sequences on a substitution character)\r\nvimscript #189 - renumber.vim - Neil Bird (only re-sequences, but handles hex)\r\nvimscript #821 - blockwork.vim - John Aldridge\r\nvimscript #1046 - monday.vim - Stefan Karlsson (increments month and weekday names)\r\n\r\nSpeak up if there are others.","install_details":"To use this file as a plugin, place it in the plugin directory.\r\nTo just try it out, download it anywhere and open it with Vim.\r\nThere are only four mapping assignments, which should be un-obtrusive (but they can be easily changed).\r\nAdditional instructions are at the beginning of the file.","5":"To use this file as a plugin, place it in the plugin directory.\r\nTo just try it out, download it anywhere and open it with Vim.\r\nThere are only four mapping assignments, which should be un-obtrusive (but they can be easily changed).\r\nAdditional instructions are at the beginning of the file.","first_name":"John","6":"John","last_name":"Aldridge","7":"Aldridge","releases":[{"0":"821","vim_version":"6.0","1":"6.0","script_version":"0.0","2":"0.0","version_comment":"Initial upload","3":"Initial upload","package":"blockwork.vim","4":"blockwork.vim","src_id":"2488","5":"2488","creation_date":"1068765147","6":"1068765147"}]},"820":{"script_id":"820","0":"820","script_name":"Mouse Toggle","1":"Mouse Toggle","script_type":"utility","2":"utility","summary":"Toggles mouse on\/off.","3":"Toggles mouse on\/off.","description":"Toggles mouse between default setting (set it as mouse_default), and unset.  Simple concept, but pretty effective.  I use it to swap between internal Vim mouse handling for window resizing etc. and X window mouse handling for clipboard operations from\/to xterm.  The basic script can, of course, be modified to toggle any setting (e.g. autoindent\/no autoindent), or even rotate between a group of settings (e.g. various cinoptions).  Depending on your <Leader> setting, use it as follows: <Leader>m to toggle (default: backslash-m).","4":"Toggles mouse between default setting (set it as mouse_default), and unset.  Simple concept, but pretty effective.  I use it to swap between internal Vim mouse handling for window resizing etc. and X window mouse handling for clipboard operations from\/to xterm.  The basic script can, of course, be modified to toggle any setting (e.g. autoindent\/no autoindent), or even rotate between a group of settings (e.g. various cinoptions).  Depending on your <Leader> setting, use it as follows: <Leader>m to toggle (default: backslash-m).","install_details":"Copy to ~\/.vim\/plugin\/","5":"Copy to ~\/.vim\/plugin\/","first_name":"Kobus","6":"Kobus","last_name":"Retief","7":"Retief","releases":[{"0":"820","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"mouse_toggle.vim","4":"mouse_toggle.vim","src_id":"2487","5":"2487","creation_date":"1068728506","6":"1068728506"}]},"819":{"script_id":"819","0":"819","script_name":"rgbasm.vim","1":"rgbasm.vim","script_type":"syntax","2":"syntax","summary":"Syntax file for the GameBoy assembler RGBASM","3":"Syntax file for the GameBoy assembler RGBASM","description":"Syntax file for the Rednex-GameBoy Assembler (rgbasm) Assembly language.","4":"Syntax file for the Rednex-GameBoy Assembler (rgbasm) Assembly language.","install_details":"put in syntax dir, make asmselect choose syntax, for example, set env var $asmsyntax to 'rgbasm' ","5":"put in syntax dir, make asmselect choose syntax, for example, set env var $asmsyntax to 'rgbasm' ","first_name":"Oyd E","6":"Oyd E","last_name":"Leven","7":"Leven","releases":[{"0":"819","vim_version":"5.7","1":"5.7","script_version":"0.01","2":"0.01","version_comment":"Initial upload","3":"Initial upload","package":"rgbasm.vim","4":"rgbasm.vim","src_id":"2486","5":"2486","creation_date":"1068710269","6":"1068710269"}]},"818":{"script_id":"818","0":"818","script_name":"ephtml","1":"ephtml","script_type":"syntax","2":"syntax","summary":"extended perl html syntax highlighting","3":"extended perl html syntax highlighting","description":"Provides support for highlighting Perl inside html:\r\n\r\n    <ephtml> ... perl ... <\/ephtml>\r\n    <ep-comment> ...comment... <\/ep-comment>\r\n","4":"Provides support for highlighting Perl inside html:\r\n\r\n    <ephtml> ... perl ... <\/ephtml>\r\n    <ep-comment> ...comment... <\/ep-comment>\r\n","install_details":"Put <ephtml.vim> into your .vim\/syntax directory.\r\nModify .vim\/filetype.vim according to Vim's :help new-filetype","5":"Put <ephtml.vim> into your .vim\/syntax directory.\r\nModify .vim\/filetype.vim according to Vim's :help new-filetype","first_name":"Charles","6":"Charles","last_name":"Campbell","7":"Campbell","releases":[{"0":"818","vim_version":"6.0","1":"6.0","script_version":"1","2":"1","version_comment":"Initial upload","3":"Initial upload","package":"ephtml.vim","4":"ephtml.vim","src_id":"2482","5":"2482","creation_date":"1068457356","6":"1068457356"}]},"817":{"script_id":"817","0":"817","script_name":"HHCS","1":"HHCS","script_type":"color scheme","2":"color scheme","summary":"Six low contrast dark colorschemes for happy hacking.","3":"Six low contrast dark colorschemes for happy hacking.","description":"    Low contrast dark colorschemes.\r\n    No bold. No italic. For very small font. (I'm using 7.5pts font in NotePC)\r\n    Fullcolor gui only.\r\n    Six variations with a feeling of unification. So it is easy to change hh<theme> by session, filetype, account, mood or \"Today's Lucky Color\".\r\n\r\n    Try hhspring first.\r\n","4":"    Low contrast dark colorschemes.\r\n    No bold. No italic. For very small font. (I'm using 7.5pts font in NotePC)\r\n    Fullcolor gui only.\r\n    Six variations with a feeling of unification. So it is easy to change hh<theme> by session, filetype, account, mood or \"Today's Lucky Color\".\r\n\r\n    Try hhspring first.\r\n","install_details":"    $ tar xvfz HHCS_<ver>.tar.gz\r\n    $ mv HappyHackingColorScheme\/hh*.vim $VIMRUNTIME\/colors\/\r\n    $ vim HappyHackingColorScheme\/htmltest.html\r\n    :color hhazure\r\n    :color hhorange\r\n    :color hhpink\r\n    :color hhspring\r\n    :color hhteal\r\n    :color hhviolet","5":"    $ tar xvfz HHCS_<ver>.tar.gz\r\n    $ mv HappyHackingColorScheme\/hh*.vim $VIMRUNTIME\/colors\/\r\n    $ vim HappyHackingColorScheme\/htmltest.html\r\n    :color hhazure\r\n    :color hhorange\r\n    :color hhpink\r\n    :color hhspring\r\n    :color hhteal\r\n    :color hhviolet","first_name":"Hideyuki","6":"Hideyuki","last_name":"HIRAUCHI","7":"HIRAUCHI","releases":[{"0":"817","vim_version":"6.0","1":"6.0","script_version":"1.2","2":"1.2","version_comment":"[BUG_FIX]hhazure,hhviolet.Error.bg:more clear.\r\n[MAJOR_CHANGE]all.CursorIM.bg:CursorIM.bg=Comment.fg\r\n[MINOR_CHANGE]all.NumberNr,Folded,FoldColumn.fg:more blightness\r\n[MINOR_CHANGE]all.Identifier.fg:less brightness\r\n","3":"[BUG_FIX]hhazure,hhviolet.Error.bg:more clear.\r\n[MAJOR_CHANGE]all.CursorIM.bg:CursorIM.bg=Comment.fg\r\n[MINOR_CHANGE]all.NumberNr,Folded,FoldColumn.fg:more blightness\r\n[MINOR_CHANGE]all.Identifier.fg:less brightness\r\n","package":"HHCS_1.2.tar.gz","4":"HHCS_1.2.tar.gz","src_id":"2526","5":"2526","creation_date":"1070053523","6":"1070053523"},{"0":"817","vim_version":"6.0","1":"6.0","script_version":"1.1","2":"1.1","version_comment":"[MAJOR_CHANGE]differentiate hhorange-hhpink-hhviolet-hhazure:","3":"[MAJOR_CHANGE]differentiate hhorange-hhpink-hhviolet-hhazure:","package":"HHCS_1.1.tar.gz","4":"HHCS_1.1.tar.gz","src_id":"2478","5":"2478","creation_date":"1068347986","6":"1068347986"}]},"816":{"script_id":"816","0":"816","script_name":"enumratingptn","1":"enumratingptn","script_type":"utility","2":"utility","summary":"Enumerate vimonline's rating pattern.","3":"Enumerate vimonline's rating pattern.","description":"For vim script creators.","4":"For vim script creators.","install_details":"$ vim enumratingptn.vim      \r\n:so %                        \r\n:call Rating(1, 6)           \r\n> L<1> H<1> U<4>             \r\n                             \r\n:call Rating(42, 37)         \r\n> L<15> H<2> U<20>           \r\n> L<13> H<7> U<17>           \r\n> L<11> H<12> U<14>          \r\n> L<9> H<17> U<11>           \r\n> L<7> H<22> U<8>            \r\n> L<5> H<27> U<5>            \r\n> L<3> H<32> U<2>            ","5":"$ vim enumratingptn.vim      \r\n:so %                        \r\n:call Rating(1, 6)           \r\n> L<1> H<1> U<4>             \r\n                             \r\n:call Rating(42, 37)         \r\n> L<15> H<2> U<20>           \r\n> L<13> H<7> U<17>           \r\n> L<11> H<12> U<14>          \r\n> L<9> H<17> U<11>           \r\n> L<7> H<22> U<8>            \r\n> L<5> H<27> U<5>            \r\n> L<3> H<32> U<2>            ","first_name":"Hideyuki","6":"Hideyuki","last_name":"HIRAUCHI","7":"HIRAUCHI","releases":[{"0":"816","vim_version":"6.0","1":"6.0","script_version":"1.3","2":"1.3","version_comment":"[BUG_FIX]","3":"[BUG_FIX]","package":"enumratingptn.vim","4":"enumratingptn.vim","src_id":"2575","5":"2575","creation_date":"1070922071","6":"1070922071"},{"0":"816","vim_version":"6.0","1":"6.0","script_version":"1.1","2":"1.1","version_comment":"[BUG_FIX]FastRating","3":"[BUG_FIX]FastRating","package":"enumratingptn.vim","4":"enumratingptn.vim","src_id":"2471","5":"2471","creation_date":"1068223068","6":"1068223068"},{"0":"816","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"initial upload","3":"initial upload","package":"enumratingptn.vim","4":"enumratingptn.vim","src_id":"2470","5":"2470","creation_date":"1068216557","6":"1068216557"}]},"815":{"script_id":"815","0":"815","script_name":"HHCS_D","1":"HHCS_D","script_type":"color scheme","2":"color scheme","summary":"Seven dark colorschemes for happy hacking.","3":"Seven dark colorschemes for happy hacking.","description":"    Black background and lightgray text.\r\n    Outer has some unique feature. (LineNr&Fold, NonText, etc...)\r\n    No bold. No italic. For very small font. (I'm using 7.5pts font in NotePC)\r\n    Six colorschemes are using only 15 cterm colors, hhdred is using 16 cterm colors. But now, they are almost gui only.\r\n    Seven variations with a feeling of unification. So it is easy to change hhd<theme> by session, filetype, account, mood or \"Today's Lucky Color\".\r\n\r\n    Try hhdgray first.\r\n\r\ncterms\r\n    dos: Terrible. No underline. lightred=>red, lightgreen=>green, and so on.\r\n    xterm: Terrible. lightred=>red, lightgreen=>green, and so on.\r\n    gnometerm: May be compatible. Please send report(simply OK or NG) to me.\r\n\r\nOptions\r\n    format:                                                           \r\n           hhcs_<gui|cterm|both>_<theme|all>_<target>=\"value\"         \r\n    target:                                                           \r\n       linenr                                                         \r\n           \"light\"      : underline, fg=black,        bg=light<theme> \r\n           \"dark\"       : underline, fg=black,        bg=dark<theme>  \r\n           \"normal\"     : none,      fg=light<theme>, bg=black        \r\n       nontext                                                        \r\n           \"underlined\" : underline, fg=dark<theme>,  bg=black        \r\n           \"normal\"     : none,      fg=dark<theme>,  bg=black        \r\n    example:                                                             \r\n       This is original settings.                                 \r\n           :let hhcs_both_all_linenr  =\"light\"                    \r\n           :let hhcs_both_all_nontext =\"underlined\"               \r\n       This is prototype settings.                                \r\n           :let hhcs_both_all_linenr  =\"dark\"                     \r\n           :let hhcs_both_all_nontext =\"underlined\"               \r\n       If you don't want to eccentric feature, try this.          \r\n           :let hhcs_both_all_linenr  =\"normal\"                   \r\n           :let hhcs_both_all_nontext =\"normal\"                   \r\n       Normal, except hhdgray(gui), hhdgreen(cterm).              \r\n           :let hhcs_both_all_linenr        =\"normal\"             \r\n           :let hhcs_both_all_nontext       =\"normal\"             \r\n           :let hhcs_gui_hhdgray_linenr     =\"light\"              \r\n           :let hhcs_gui_hhdgray_nontext    =\"underlined\"         \r\n           :let hhcs_cterm_hhdgreen_linenr  =\"dark\"               \r\n           :let hhcs_cterm_hhdgreen_nontext =\"underlined\"         \r\n       For poor cterm                                             \r\n           :let hhcs_cterm_all_linenr     =\"normal\"               ","4":"    Black background and lightgray text.\r\n    Outer has some unique feature. (LineNr&Fold, NonText, etc...)\r\n    No bold. No italic. For very small font. (I'm using 7.5pts font in NotePC)\r\n    Six colorschemes are using only 15 cterm colors, hhdred is using 16 cterm colors. But now, they are almost gui only.\r\n    Seven variations with a feeling of unification. So it is easy to change hhd<theme> by session, filetype, account, mood or \"Today's Lucky Color\".\r\n\r\n    Try hhdgray first.\r\n\r\ncterms\r\n    dos: Terrible. No underline. lightred=>red, lightgreen=>green, and so on.\r\n    xterm: Terrible. lightred=>red, lightgreen=>green, and so on.\r\n    gnometerm: May be compatible. Please send report(simply OK or NG) to me.\r\n\r\nOptions\r\n    format:                                                           \r\n           hhcs_<gui|cterm|both>_<theme|all>_<target>=\"value\"         \r\n    target:                                                           \r\n       linenr                                                         \r\n           \"light\"      : underline, fg=black,        bg=light<theme> \r\n           \"dark\"       : underline, fg=black,        bg=dark<theme>  \r\n           \"normal\"     : none,      fg=light<theme>, bg=black        \r\n       nontext                                                        \r\n           \"underlined\" : underline, fg=dark<theme>,  bg=black        \r\n           \"normal\"     : none,      fg=dark<theme>,  bg=black        \r\n    example:                                                             \r\n       This is original settings.                                 \r\n           :let hhcs_both_all_linenr  =\"light\"                    \r\n           :let hhcs_both_all_nontext =\"underlined\"               \r\n       This is prototype settings.                                \r\n           :let hhcs_both_all_linenr  =\"dark\"                     \r\n           :let hhcs_both_all_nontext =\"underlined\"               \r\n       If you don't want to eccentric feature, try this.          \r\n           :let hhcs_both_all_linenr  =\"normal\"                   \r\n           :let hhcs_both_all_nontext =\"normal\"                   \r\n       Normal, except hhdgray(gui), hhdgreen(cterm).              \r\n           :let hhcs_both_all_linenr        =\"normal\"             \r\n           :let hhcs_both_all_nontext       =\"normal\"             \r\n           :let hhcs_gui_hhdgray_linenr     =\"light\"              \r\n           :let hhcs_gui_hhdgray_nontext    =\"underlined\"         \r\n           :let hhcs_cterm_hhdgreen_linenr  =\"dark\"               \r\n           :let hhcs_cterm_hhdgreen_nontext =\"underlined\"         \r\n       For poor cterm                                             \r\n           :let hhcs_cterm_all_linenr     =\"normal\"               ","install_details":"    $ tar xvfz HHCS_D_<ver>.tar.gz\r\n    $ mv HappyHackingColorScheme_Dark\/hhd*.vim $VIMRUNTIME\/colors\/\r\n    :color hhdblue\r\n    :color hhdcyan\r\n    :color hhdgray\r\n    :color hhdgreen\r\n    :color hhdmagenta\r\n    :color hhdred\r\n    :color hhdyellow\r\n","5":"    $ tar xvfz HHCS_D_<ver>.tar.gz\r\n    $ mv HappyHackingColorScheme_Dark\/hhd*.vim $VIMRUNTIME\/colors\/\r\n    :color hhdblue\r\n    :color hhdcyan\r\n    :color hhdgray\r\n    :color hhdgreen\r\n    :color hhdmagenta\r\n    :color hhdred\r\n    :color hhdyellow\r\n","first_name":"Hideyuki","6":"Hideyuki","last_name":"HIRAUCHI","7":"HIRAUCHI","releases":[{"0":"815","vim_version":"6.0","1":"6.0","script_version":"1.3","2":"1.3","version_comment":"[MINOR_CHANGE]Add options. Now, If you don't want to eccentric feature, you can off it.","3":"[MINOR_CHANGE]Add options. Now, If you don't want to eccentric feature, you can off it.","package":"HHCS_D_1.3.tar.gz","4":"HHCS_D_1.3.tar.gz","src_id":"2475","5":"2475","creation_date":"1068243643","6":"1068243643"}]},"814":{"script_id":"814","0":"814","script_name":"white.vim","1":"white.vim","script_type":"color scheme","2":"color scheme","summary":"I like white background. May be you do too.","3":"I like white background. May be you do too.","description":"I like white background. May be you do too.\r\nSo be it. \r\nTake a look at screenshots - http:\/\/mah.bip.ru\/vim_color.php\r\n\r\n----\r\nIt is uploaded as .txt  - didn't mean it.","4":"I like white background. May be you do too.\r\nSo be it. \r\nTake a look at screenshots - http:\/\/mah.bip.ru\/vim_color.php\r\n\r\n----\r\nIt is uploaded as .txt  - didn't mean it.","install_details":"common colorscheme installation","5":"common colorscheme installation","first_name":"Maksim","6":"Maksim","last_name":"Kim","7":"Kim","releases":[{"0":"814","vim_version":"6.0","1":"6.0","script_version":"0.9","2":"0.9","version_comment":"Initial upload","3":"Initial upload","package":"white.txt","4":"white.txt","src_id":"2456","5":"2456","creation_date":"1067987101","6":"1067987101"}]},"813":{"script_id":"813","0":"813","script_name":"mail.vim","1":"mail.vim","script_type":"syntax","2":"syntax","summary":"Syntax file for emails. Update of the default vim script to include URLs etc","3":"Syntax file for emails. Update of the default vim script to include URLs etc","description":"Updates the default VIM email syntax script to also do the following:\r\n\r\n1. Highlight URLs and email addresses in the message \/ quoted message\r\n2. Highlight signatures in the quoted message\r\n3. Highlight headers in the quoted message\r\n\r\nLook at http:\/\/www.math.uchicago.edu\/~gautam\/vim\/xterm16\/email.html for a screenshot. This file is now part of the standard vim distribution, and will be shipped with future releases (6.3 and later).","4":"Updates the default VIM email syntax script to also do the following:\r\n\r\n1. Highlight URLs and email addresses in the message \/ quoted message\r\n2. Highlight signatures in the quoted message\r\n3. Highlight headers in the quoted message\r\n\r\nLook at http:\/\/www.math.uchicago.edu\/~gautam\/vim\/xterm16\/email.html for a screenshot. This file is now part of the standard vim distribution, and will be shipped with future releases (6.3 and later).","install_details":"For local installation put the mail.vim file in your .vim\/syntax directory. For global installation put it in $VIMRUNTIME\/syntax directory\r\n\r\nIf not enabled by default do\r\n:set ft=mail\r\n:syn on","5":"For local installation put the mail.vim file in your .vim\/syntax directory. For global installation put it in $VIMRUNTIME\/syntax directory\r\n\r\nIf not enabled by default do\r\n:set ft=mail\r\n:syn on","first_name":"gi1242","6":"gi1242","last_name":"gi1242","7":"gi1242","releases":[{"0":"813","vim_version":"6.0","1":"6.0","script_version":"1.1","2":"1.1","version_comment":"Now highlights email addresses and URLs in different colors. Also highlights the quote markers of quoted headers \/ quoted signatures correctly.","3":"Now highlights email addresses and URLs in different colors. Also highlights the quote markers of quoted headers \/ quoted signatures correctly.","package":"mail.vim","4":"mail.vim","src_id":"2713","5":"2713","creation_date":"1075732010","6":"1075732010"},{"0":"813","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial Upload","3":"Initial Upload","package":"mail.vim","4":"mail.vim","src_id":"2455","5":"2455","creation_date":"1067984869","6":"1067984869"}]},"812":{"script_id":"812","0":"812","script_name":"billw.vim","1":"billw.vim","script_type":"color scheme","2":"color scheme","summary":"Black color scheme with some contrast","3":"Black color scheme with some contrast","description":"A dark color scheme with high (but pleasant) contrast with a black background. This is better suited for lcd displays. Based on the Billw color theme from Emacs.\r\n","4":"A dark color scheme with high (but pleasant) contrast with a black background. This is better suited for lcd displays. Based on the Billw color theme from Emacs.\r\n","install_details":"Copy file to your (local or global) colors folder.\r\n","5":"Copy file to your (local or global) colors folder.\r\n","first_name":"Luis","6":"Luis","last_name":"Carvalho","7":"Carvalho","releases":[{"0":"812","vim_version":"6.0","1":"6.0","script_version":"0.2","2":"0.2","version_comment":"Some minor (but long delayed!) updates: line numbering, user colors, colors for athena\/motif users.","3":"Some minor (but long delayed!) updates: line numbering, user colors, colors for athena\/motif users.","package":"billw.vim","4":"billw.vim","src_id":"4296","5":"4296","creation_date":"1116492366","6":"1116492366"},{"0":"812","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"billw.vim","4":"billw.vim","src_id":"2450","5":"2450","creation_date":"1067968270","6":"1067968270"}]},"811":{"script_id":"811","0":"811","script_name":"darkblue2.vim","1":"darkblue2.vim","script_type":"color scheme","2":"color scheme","summary":"A nice mixture of blue, green and cyan in a color scheme for programmers.","3":"A nice mixture of blue, green and cyan in a color scheme for programmers.","description":"A nice mixture of blue, green and cyan in a somewhat dark color scheme for programmers, easy to the eyes. Based on the Dark Blue 2 color theme from Emacs.\r\n","4":"A nice mixture of blue, green and cyan in a somewhat dark color scheme for programmers, easy to the eyes. Based on the Dark Blue 2 color theme from Emacs.\r\n","install_details":"Copy file to your (local or global) colors folder.\r\n","5":"Copy file to your (local or global) colors folder.\r\n","first_name":"Luis","6":"Luis","last_name":"Carvalho","7":"Carvalho","releases":[{"0":"811","vim_version":"6.0","1":"6.0","script_version":"0.2","2":"0.2","version_comment":"Some minor (but long delayed!) updates: line numbering, user colors, colors for athena\/motif users.","3":"Some minor (but long delayed!) updates: line numbering, user colors, colors for athena\/motif users.","package":"darkblue2.vim","4":"darkblue2.vim","src_id":"4295","5":"4295","creation_date":"1116491903","6":"1116491903"},{"0":"811","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"darkblue2.vim","4":"darkblue2.vim","src_id":"2449","5":"2449","creation_date":"1067967838","6":"1067967838"}]},"810":{"script_id":"810","0":"810","script_name":"robinhood.vim","1":"robinhood.vim","script_type":"color scheme","2":"color scheme","summary":"A greenish color scheme","3":"A greenish color scheme","description":"Easy to the eyes, with some contrast but still pleasant. It's greenish, a bit dark and good for programming. Based on the Robin Hood color theme from Emacs.","4":"Easy to the eyes, with some contrast but still pleasant. It's greenish, a bit dark and good for programming. Based on the Robin Hood color theme from Emacs.","install_details":"Copy file to your (local or global) colors folder.","5":"Copy file to your (local or global) colors folder.","first_name":"Luis","6":"Luis","last_name":"Carvalho","7":"Carvalho","releases":[{"0":"810","vim_version":"6.0","1":"6.0","script_version":"0.2","2":"0.2","version_comment":"Some minor (but long delayed!) updates: line numbering, user colors, colors for athena\/motif users.","3":"Some minor (but long delayed!) updates: line numbering, user colors, colors for athena\/motif users.","package":"robinhood.vim","4":"robinhood.vim","src_id":"4294","5":"4294","creation_date":"1116491483","6":"1116491483"},{"0":"810","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"robinhood.vim","4":"robinhood.vim","src_id":"2448","5":"2448","creation_date":"1067967639","6":"1067967639"}]},"809":{"script_id":"809","0":"809","script_name":"Smart Diffsplit","1":"Smart Diffsplit","script_type":"utility","2":"utility","summary":"Diffsplit that restores window settings","3":"Diffsplit that restores window settings","description":":VDiff[!] <filename>       : Open a vertial difference between the current file that restores buffer settings\r\n:HDiff[!] <filename>       : Open a horizontal difference between the current file that restores buffer settings\r\n                                                                                                                \r\nIn both cases the ! causes the specified buffer not to be unloaded when a\r\nwindow is closed, or another window is opened.  In this case, the settings\r\nwill be restored using the original settings of the first buffer.\r\n","4":":VDiff[!] <filename>       : Open a vertial difference between the current file that restores buffer settings\r\n:HDiff[!] <filename>       : Open a horizontal difference between the current file that restores buffer settings\r\n                                                                                                                \r\nIn both cases the ! causes the specified buffer not to be unloaded when a\r\nwindow is closed, or another window is opened.  In this case, the settings\r\nwill be restored using the original settings of the first buffer.\r\n","install_details":"Load at startup (place in ~\/vimfiles\/plugin  or  ~\/.vim\/plugin)","5":"Load at startup (place in ~\/vimfiles\/plugin  or  ~\/.vim\/plugin)","first_name":"Michael","6":"Michael","last_name":"Geddes","7":"Geddes","releases":[{"0":"809","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"diffsplit.vim","4":"diffsplit.vim","src_id":"2446","5":"2446","creation_date":"1067962151","6":"1067962151"}]},"808":{"script_id":"808","0":"808","script_name":"vimcommander","1":"vimcommander","script_type":"utility","2":"utility","summary":"totalcommander-like two-panel tree file explorer for vim","3":"totalcommander-like two-panel tree file explorer for vim","description":"This is an adaptation of opsplorer (vimscript #362), intended to be more like the Total Comander (http:\/\/www.ghisler.com) file explorer.\r\n\r\nThis opens two panels of file explorers on the top half of the vim screen.\r\nTargets for moving and copying defaults to the other panel, like totalcmd. TAB switches between panels.\r\nVimcommander keys are mostly totalcommander's:\r\nF3 - view\r\nF4 - edit\r\nF5 - copy\r\nF6 - move\r\nF7 - create dir\r\nF8 - del\r\nOthers: C-U, C-Left\/C-Right, C-R, BS, DEL, C-H, etc.\r\nSelection of files\/dirs also works: INS, +, -. Then copy\/move\/del selected files.\r\n\r\nSuggested binding is\r\nnoremap <silent> <F11> :cal VimCommanderToggle()<CR>\r\n\r\nTested on Linux. I have reports that it doesn't work on Windows.\r\n\r\nIf you want to contribute, note that vimcommander is hosted at github: http:\/\/github.com\/lpenz\/vimcommander\/.","4":"This is an adaptation of opsplorer (vimscript #362), intended to be more like the Total Comander (http:\/\/www.ghisler.com) file explorer.\r\n\r\nThis opens two panels of file explorers on the top half of the vim screen.\r\nTargets for moving and copying defaults to the other panel, like totalcmd. TAB switches between panels.\r\nVimcommander keys are mostly totalcommander's:\r\nF3 - view\r\nF4 - edit\r\nF5 - copy\r\nF6 - move\r\nF7 - create dir\r\nF8 - del\r\nOthers: C-U, C-Left\/C-Right, C-R, BS, DEL, C-H, etc.\r\nSelection of files\/dirs also works: INS, +, -. Then copy\/move\/del selected files.\r\n\r\nSuggested binding is\r\nnoremap <silent> <F11> :cal VimCommanderToggle()<CR>\r\n\r\nTested on Linux. I have reports that it doesn't work on Windows.\r\n\r\nIf you want to contribute, note that vimcommander is hosted at github: http:\/\/github.com\/lpenz\/vimcommander\/.","install_details":"Drop vimcommander.vim in ~\/.vim\/plugin\r\nPut in you .vimrc a map to VimCommanderToggle():\r\nnoremap <silent> <F11> :cal VimCommanderToggle()<CR>\r\n","5":"Drop vimcommander.vim in ~\/.vim\/plugin\r\nPut in you .vimrc a map to VimCommanderToggle():\r\nnoremap <silent> <F11> :cal VimCommanderToggle()<CR>\r\n","first_name":"Leandro","6":"Leandro","last_name":"Penz","7":"Penz","releases":[{"0":"808","vim_version":"6.0","1":"6.0","script_version":"0.81","2":"0.81","version_comment":"Improved windows compatibility.","3":"Improved windows compatibility.","package":"vimcommander_0.81.vba","4":"vimcommander_0.81.vba","src_id":"19655","5":"19655","creation_date":"1363488660","6":"1363488660"},{"0":"808","vim_version":"6.0","1":"6.0","script_version":"0.80","2":"0.80","version_comment":"C-H is no longer toggles hidden file showing, as it overwrites backspace binding in some terminals.","3":"C-H is no longer toggles hidden file showing, as it overwrites backspace binding in some terminals.","package":"vimcommander_0.80.vba","4":"vimcommander_0.80.vba","src_id":"12703","5":"12703","creation_date":"1269477191","6":"1269477191"},{"0":"808","vim_version":"7.0","1":"7.0","script_version":"0.79","2":"0.79","version_comment":"Windows path handling working, thanks to Zacco!\r\nUsing vimball format from now on.","3":"Windows path handling working, thanks to Zacco!\r\nUsing vimball format from now on.","package":"vimcommander_0.79.vba","4":"vimcommander_0.79.vba","src_id":"12478","5":"12478","creation_date":"1266960302","6":"1266960302"},{"0":"808","vim_version":"6.0","1":"6.0","script_version":"0.78","2":"0.78","version_comment":"Change dir dialog, required in windows.","3":"Change dir dialog, required in windows.","package":"vimcommander.vim","4":"vimcommander.vim","src_id":"12254","5":"12254","creation_date":"1264960320","6":"1264960320"},{"0":"808","vim_version":"6.0","1":"6.0","script_version":"0.77","2":"0.77","version_comment":"Version scheme changed.\r\nAccepting initial directories from global configuration variables.","3":"Version scheme changed.\r\nAccepting initial directories from global configuration variables.","package":"vimcommander.vim","4":"vimcommander.vim","src_id":"12166","5":"12166","creation_date":"1264249223","6":"1264249223"},{"0":"808","vim_version":"6.0","1":"6.0","script_version":"76","2":"76","version_comment":"Directory escaping was missing. Thanks devix for the fix.","3":"Directory escaping was missing. Thanks devix for the fix.","package":"vimcommander.vim","4":"vimcommander.vim","src_id":"9822","5":"9822","creation_date":"1231974815","6":"1231974815"},{"0":"808","vim_version":"6.0","1":"6.0","script_version":"75","2":"75","version_comment":"If hidden files were enabled, the glob coud become '**', taking a very long time to build the tree. Thanks go to Oleg Popov for the fix","3":"If hidden files were enabled, the glob coud become '**', taking a very long time to build the tree. Thanks go to Oleg Popov for the fix","package":"vimcommander.vim","4":"vimcommander.vim","src_id":"8019","5":"8019","creation_date":"1196688800","6":"1196688800"},{"0":"808","vim_version":"6.0","1":"6.0","script_version":"74","2":"74","version_comment":"Works with 'splitright'. Thanks to Vladimir Marek again!","3":"Works with 'splitright'. Thanks to Vladimir Marek again!","package":"vimcommander.vim","4":"vimcommander.vim","src_id":"7542","5":"7542","creation_date":"1187719320","6":"1187719320"},{"0":"808","vim_version":"6.0","1":"6.0","script_version":"73","2":"73","version_comment":"Files with spaces working now, thanks to Vladim\u00c3\u00adr Marek!","3":"Files with spaces working now, thanks to Vladim\u00c3\u00adr Marek!","package":"vimcommander.vim","4":"vimcommander.vim","src_id":"7301","5":"7301","creation_date":"1182696531","6":"1182696531"},{"0":"808","vim_version":"6.0","1":"6.0","script_version":"69","2":"69","version_comment":"+ and - bound to kPlus and kMinus.","3":"+ and - bound to kPlus and kMinus.","package":"vimcommander.vim","4":"vimcommander.vim","src_id":"5533","5":"5533","creation_date":"1144566460","6":"1144566460"},{"0":"808","vim_version":"6.0","1":"6.0","script_version":"68","2":"68","version_comment":"Fix: directories with spaces. New: local copy.\r\nNew version numbering scheme.","3":"Fix: directories with spaces. New: local copy.\r\nNew version numbering scheme.","package":"vimcommander.vim","4":"vimcommander.vim","src_id":"5413","5":"5413","creation_date":"1142060093","6":"1142060093"},{"0":"808","vim_version":"6.0","1":"6.0","script_version":"1.54.2.9","2":"1.54.2.9","version_comment":"Now vimcommander keeps the previous window open, preventing the break of C-O among other things.","3":"Now vimcommander keeps the previous window open, preventing the break of C-O among other things.","package":"vimcommander.vim","4":"vimcommander.vim","src_id":"4642","5":"4642","creation_date":"1128255070","6":"1128255070"},{"0":"808","vim_version":"6.0","1":"6.0","script_version":"1.54.2.8","2":"1.54.2.8","version_comment":"Does not come back to the begining of last open file when switching off.\r\nmkdir was not working when dir had spaces.\r\nFixes to make S-F4 working, and to prevent error report when canceling interactive questions.\r\n","3":"Does not come back to the begining of last open file when switching off.\r\nmkdir was not working when dir had spaces.\r\nFixes to make S-F4 working, and to prevent error report when canceling interactive questions.\r\n","package":"vimcommander.vim","4":"vimcommander.vim","src_id":"4269","5":"4269","creation_date":"1115838857","6":"1115838857"},{"0":"808","vim_version":"6.0","1":"6.0","script_version":"1.54.2.2","2":"1.54.2.2","version_comment":"Directory change is optional. Fixed <leader>o\/<C-O>.","3":"Directory change is optional. Fixed <leader>o\/<C-O>.","package":"vimcommander.vim","4":"vimcommander.vim","src_id":"2787","5":"2787","creation_date":"1077820063","6":"1077820063"},{"0":"808","vim_version":"6.0","1":"6.0","script_version":"1.54.2.1","2":"1.54.2.1","version_comment":"ToggleHiddenFiles and key conflict solved.\r\nFixed typo in doc.\r\n","3":"ToggleHiddenFiles and key conflict solved.\r\nFixed typo in doc.\r\n","package":"vimcommander.vim","4":"vimcommander.vim","src_id":"2675","5":"2675","creation_date":"1075022258","6":"1075022258"},{"0":"808","vim_version":"6.0","1":"6.0","script_version":"1.52","2":"1.52","version_comment":"Self-installing documentation created. Directory history implemented. Bugfix: does not overwrite \" register; does not lose track of last buffer anymore. Uses only the window where its openend. Some changes in the layout also. Licensing info appended.","3":"Self-installing documentation created. Directory history implemented. Bugfix: does not overwrite \" register; does not lose track of last buffer anymore. Uses only the window where its openend. Some changes in the layout also. Licensing info appended.","package":"vimcommander.vim","4":"vimcommander.vim","src_id":"2497","5":"2497","creation_date":"1069254764","6":"1069254764"},{"0":"808","vim_version":"6.0","1":"6.0","script_version":"1.41","2":"1.41","version_comment":"Bugfix: remembers last panel visited and proper closure now working.","3":"Bugfix: remembers last panel visited and proper closure now working.","package":"vimcommander.vim","4":"vimcommander.vim","src_id":"2490","5":"2490","creation_date":"1068904680","6":"1068904680"},{"0":"808","vim_version":"6.0","1":"6.0","script_version":"1.39","2":"1.39","version_comment":"Bugfix: move is now working. Alternate keys for C-. Options for the window are saved\/restored when entering\/exiting.","3":"Bugfix: move is now working. Alternate keys for C-. Options for the window are saved\/restored when entering\/exiting.","package":"vimcommander.vim","4":"vimcommander.vim","src_id":"2484","5":"2484","creation_date":"1068658038","6":"1068658038"},{"0":"808","vim_version":"6.0","1":"6.0","script_version":"1.35","2":"1.35","version_comment":"Fullscreen. Toggle improved. Selection of files thru <INS>, + and - implemented. Generally more similar to wincmd.","3":"Fullscreen. Toggle improved. Selection of files thru <INS>, + and - implemented. Generally more similar to wincmd.","package":"vimcommander.vim","4":"vimcommander.vim","src_id":"2479","5":"2479","creation_date":"1068369736","6":"1068369736"},{"0":"808","vim_version":"6.0","1":"6.0","script_version":"1.16","2":"1.16","version_comment":"New: \r\nF7 - create directory\r\nC-U exchange panels\r\nF11 - switch buffer-vimcommander\r\nC-Right\/C-Left - puts dir under cursor on other panel\r\nCopy, move & del work with dirs (CAUTION ADVISED)\r\nFixed: \r\ncopy, move & paste for files with spaces.\r\n\r\nRemoving keys & compatibility with opsplorer.\r\n","3":"New: \r\nF7 - create directory\r\nC-U exchange panels\r\nF11 - switch buffer-vimcommander\r\nC-Right\/C-Left - puts dir under cursor on other panel\r\nCopy, move & del work with dirs (CAUTION ADVISED)\r\nFixed: \r\ncopy, move & paste for files with spaces.\r\n\r\nRemoving keys & compatibility with opsplorer.\r\n","package":"vimcommander.vim","4":"vimcommander.vim","src_id":"2464","5":"2464","creation_date":"1068143385","6":"1068143385"},{"0":"808","vim_version":"6.0","1":"6.0","script_version":"1.7","2":"1.7","version_comment":"Initial upload","3":"Initial upload","package":"vimcommander.vim","4":"vimcommander.vim","src_id":"2443","5":"2443","creation_date":"1067680092","6":"1067680092"}]},"807":{"script_id":"807","0":"807","script_name":"dks-il2+tex.vim","1":"dks-il2+tex.vim","script_type":"utility","2":"utility","summary":"Mapping deadkeys (accents)","3":"Mapping deadkeys (accents)","description":"Central European chars in latin2 (cp1250, pl2) and TeX encoding\r\n\r\nThe most of Central European accented characters are defined,\r\nalso in TeX encoding. Changing encoding between these codes. I used to work\r\nwith:\r\n\r\n- 'digraphs', but not all CTRL-K {char1} {char2} work the way that I want;\r\n  it does not work in command-line mode and in search also.\r\n- 'keymap' (see 'loadkeymap') but it does not works to me anyway, and in\r\n  $vim\/keymap\/accents.vim there are no all CZ, HU and SK chars from\r\n  mentioned encodings (I think there are just East European characters).\r\n  \r\nThis 'keymap' shows more MSWord \"compatibility\" for Central Europe (I\r\nthink), for those who works half-time with Word it is very useful :-) \r\n\r\nUsage: Use [=+:;.,^] + <char> to write an accented character: <char> with\r\nacute, ve, etc.\r\n\r\n- <leader>at - convert the file from accents to TeX and map TeX deadkeys\r\n- <leader>ta - convert the file from TeX to accents and map accent dedakeys\r\n- <leader>da - map accent dedakeys\r\n- <leader>dt - map TeX deadkeys\r\n- <leader>du - unmap deadkeys\r\n\r\n<leader> is usually a '\\\\'","4":"Central European chars in latin2 (cp1250, pl2) and TeX encoding\r\n\r\nThe most of Central European accented characters are defined,\r\nalso in TeX encoding. Changing encoding between these codes. I used to work\r\nwith:\r\n\r\n- 'digraphs', but not all CTRL-K {char1} {char2} work the way that I want;\r\n  it does not work in command-line mode and in search also.\r\n- 'keymap' (see 'loadkeymap') but it does not works to me anyway, and in\r\n  $vim\/keymap\/accents.vim there are no all CZ, HU and SK chars from\r\n  mentioned encodings (I think there are just East European characters).\r\n  \r\nThis 'keymap' shows more MSWord \"compatibility\" for Central Europe (I\r\nthink), for those who works half-time with Word it is very useful :-) \r\n\r\nUsage: Use [=+:;.,^] + <char> to write an accented character: <char> with\r\nacute, ve, etc.\r\n\r\n- <leader>at - convert the file from accents to TeX and map TeX deadkeys\r\n- <leader>ta - convert the file from TeX to accents and map accent dedakeys\r\n- <leader>da - map accent dedakeys\r\n- <leader>dt - map TeX deadkeys\r\n- <leader>du - unmap deadkeys\r\n\r\n<leader> is usually a '\\\\'","install_details":"Put one of the files into $HOME\/.vim\/plugin\/.","5":"Put one of the files into $HOME\/.vim\/plugin\/.","first_name":"Milan","6":"Milan","last_name":"Berta","7":"Berta","releases":[{"0":"807","vim_version":"6.0","1":"6.0","script_version":"2.0","2":"2.0","version_comment":"In single file: mapping encoding (latin2, win, or pl2) and TeX, copnvert current file between them.","3":"In single file: mapping encoding (latin2, win, or pl2) and TeX, copnvert current file between them.","package":"dks-accents+tex-v2.0.tgz","4":"dks-accents+tex-v2.0.tgz","src_id":"2879","5":"2879","creation_date":"1080376615","6":"1080376615"},{"0":"807","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"dks.vim.tgz","4":"dks.vim.tgz","src_id":"2435","5":"2435","creation_date":"1067508300","6":"1067508300"}]},"806":{"script_id":"806","0":"806","script_name":"truegrid.vim","1":"truegrid.vim","script_type":"syntax","2":"syntax","summary":"A syntax highlighting file for TrueGrid input files.","3":"A syntax highlighting file for TrueGrid input files.","description":"truegrid.vim provides syntax highlighting for TrueGrid input files.  It does not have all of the commands available in TrueGrid, as there are so many.  If you add a lot of commands, or make any other substantive changes, email them to me, and I will roll them in.","4":"truegrid.vim provides syntax highlighting for TrueGrid input files.  It does not have all of the commands available in TrueGrid, as there are so many.  If you add a lot of commands, or make any other substantive changes, email them to me, and I will roll them in.","install_details":"Place truegrid.vim file in ~\/.vim\/syntax\/ folder.  For more details, read the comments at the top of the file itself.\r\n","5":"Place truegrid.vim file in ~\/.vim\/syntax\/ folder.  For more details, read the comments at the top of the file itself.\r\n","first_name":"Neil","6":"Neil","last_name":"Hodge","7":"Hodge","releases":[{"0":"806","vim_version":"6.0","1":"6.0","script_version":"0.1.3","2":"0.1.3","version_comment":"2004-03-02: Made a few improvements to the more experimental parts of the syntax; some of these constructs (re: the \"bi\" command) are very complex, with some very odd behavior, and as such, will be ongoing until they are fixed.\r\n\r\n2004-01-29: Added more keywords.\r\n\r\n2004-01-22: Played around a bit with folding; it will probably be included (as an option) in some future release.  Started to clean up all of the definitions, to prepare for the next release.  Added many more keywords.\r\n\r\n2004-01-15: Made changes to some of the more complex syntax constructs.  Created highlighting that will aid the user in knowing if a statement is closed (e.g., if-endif).  Added visual indicators for lines greater than 80 characters.\r\n\r\n2003-12-31: Reorganizing the way things are defined to make the highlighting much more flexible and powerful.  This is a work in progress.\r\n\r\n2003-12-12: Figured how to highlight items differently depending on context, and how to make a highlighted region span multiple lines, and how to create nested highlight groups.  Still trying to figure out how to implement these features gracefully.\r\n\r\n2003-12-11: Reset some of the tab parameters to accomodate truegrid's line length restriction.  Changed the highlighting of arbitrary strings (echo, becho, title, head, and mhead commands).  Mostly figured out how to make a pattern match differently depending on context; still working on some of the details.","3":"2004-03-02: Made a few improvements to the more experimental parts of the syntax; some of these constructs (re: the \"bi\" command) are very complex, with some very odd behavior, and as such, will be ongoing until they are fixed.\r\n\r\n2004-01-29: Added more keywords.\r\n\r\n2004-01-22: Played around a bit with folding; it will probably be included (as an option) in some future release.  Started to clean up all of the definitions, to prepare for the next release.  Added many more keywords.\r\n\r\n2004-01-15: Made changes to some of the more complex syntax constructs.  Created highlighting that will aid the user in knowing if a statement is closed (e.g., if-endif).  Added visual indicators for lines greater than 80 characters.\r\n\r\n2003-12-31: Reorganizing the way things are defined to make the highlighting much more flexible and powerful.  This is a work in progress.\r\n\r\n2003-12-12: Figured how to highlight items differently depending on context, and how to make a highlighted region span multiple lines, and how to create nested highlight groups.  Still trying to figure out how to implement these features gracefully.\r\n\r\n2003-12-11: Reset some of the tab parameters to accomodate truegrid's line length restriction.  Changed the highlighting of arbitrary strings (echo, becho, title, head, and mhead commands).  Mostly figured out how to make a pattern match differently depending on context; still working on some of the details.","package":"truegrid.vim.gz","4":"truegrid.vim.gz","src_id":"2803","5":"2803","creation_date":"1078407819","6":"1078407819"},{"0":"806","vim_version":"6.0","1":"6.0","script_version":"0.1.2","2":"0.1.2","version_comment":"From the changelog:\r\n\r\n2003-11-25: Added many keywords.  Fixed numeric highlighting (hopefully for good).  Organized file format so that others can add keywords in a more organized manner.\r\n\r\n2003-11-24: Added more information to the instructions for DOS\/UNIX differences.  Also added NOTES section for myself.  Corrected syntax for fortran \".\" operators.  Noticed that number regexes are broken again; working to correct.  Continued reorganization of keywords.\r\n\r\n2003-11-12: Added a bunch of keywords.  Fixed up the number regexes.\r\n","3":"From the changelog:\r\n\r\n2003-11-25: Added many keywords.  Fixed numeric highlighting (hopefully for good).  Organized file format so that others can add keywords in a more organized manner.\r\n\r\n2003-11-24: Added more information to the instructions for DOS\/UNIX differences.  Also added NOTES section for myself.  Corrected syntax for fortran \".\" operators.  Noticed that number regexes are broken again; working to correct.  Continued reorganization of keywords.\r\n\r\n2003-11-12: Added a bunch of keywords.  Fixed up the number regexes.\r\n","package":"truegrid.vim.gz","4":"truegrid.vim.gz","src_id":"2515","5":"2515","creation_date":"1069754284","6":"1069754284"},{"0":"806","vim_version":"6.0","1":"6.0","script_version":"0.1.0","2":"0.1.0","version_comment":"Initial upload","3":"Initial upload","package":"truegrid.vim.gz","4":"truegrid.vim.gz","src_id":"2433","5":"2433","creation_date":"1067433935","6":"1067433935"}]},"805":{"script_id":"805","0":"805","script_name":"zrf.vim","1":"zrf.vim","script_type":"syntax","2":"syntax","summary":"Syntax file for Zillions of Games' ZRF","3":"Syntax file for Zillions of Games' ZRF","description":"This is a syntax file for proper highlighting of Zillions Rule Files (ZRF) which are used to describe games in Zillions of Games. Zillions of Games is a universal gaming environment that allows the definition of new games by the user. For more details simply visit http:\/\/www.zillionsofgames.com.","4":"This is a syntax file for proper highlighting of Zillions Rule Files (ZRF) which are used to describe games in Zillions of Games. Zillions of Games is a universal gaming environment that allows the definition of new games by the user. For more details simply visit http:\/\/www.zillionsofgames.com.","install_details":"See file zrf_vim.txt contained in the ZIP file. Basically just add\r\n\r\n    au BufNewFile,BufRead *.zrf    setf zrf  (for vim 6.x)\r\n\r\nor\r\n\r\n    au BufNewFile,BufRead *.zrf    call s:StarSet('zrf')  (for vim 7.x)\r\n\r\nto your $VIMRUNTIME\/filetype.vim file and enjoy.","5":"See file zrf_vim.txt contained in the ZIP file. Basically just add\r\n\r\n    au BufNewFile,BufRead *.zrf    setf zrf  (for vim 6.x)\r\n\r\nor\r\n\r\n    au BufNewFile,BufRead *.zrf    call s:StarSet('zrf')  (for vim 7.x)\r\n\r\nto your $VIMRUNTIME\/filetype.vim file and enjoy.","first_name":"Jochen","6":"Jochen","last_name":"Schoof","7":"Schoof","releases":[{"0":"805","vim_version":"7.0","1":"7.0","script_version":"1.2","2":"1.2","version_comment":"Updated the installation description to also match vim 7.x.\r\nNo changes in zrf.vim file except version number and date.\r\nSyntax file can be used in both vim 6.x and 7.x.","3":"Updated the installation description to also match vim 7.x.\r\nNo changes in zrf.vim file except version number and date.\r\nSyntax file can be used in both vim 6.x and 7.x.","package":"zrf_vim.zip","4":"zrf_vim.zip","src_id":"9941","5":"9941","creation_date":"1234210721","6":"1234210721"},{"0":"805","vim_version":"6.0","1":"6.0","script_version":"1.1","2":"1.1","version_comment":"Initial upload","3":"Initial upload","package":"zrf_vim.zip","4":"zrf_vim.zip","src_id":"2428","5":"2428","creation_date":"1067343249","6":"1067343249"}]},"804":{"script_id":"804","0":"804","script_name":"expand.vim","1":"expand.vim","script_type":"utility","2":"utility","summary":"method to simply an quickly post expand a cmd.  \"index ff<c-cr>\" for example.","3":"method to simply an quickly post expand a cmd.  \"index ff<c-cr>\" for example.","description":"method to simply an quickly post expand a cmd.  \"index ff<c-cr>\" for example.\r\n(<c-cr> being mapped to this cmd.)\r\n\r\nNOTE this is a QUICKY!\r\nFor what it is worth, hopefully useful to someone :)\r\n\r\nThe reason for this over a basic mapping, or DrC.Stubs is the ability to\r\nspecify the variable(s) to work on.\r\n\r\nI.e.\r\n  iInd < m_array.size() for<c-cr>\r\n\r\n  for    (    iInd = 0; iInd < m_array.size(); iInd++)\r\n  {\r\n      <cursor>\r\n  }\r\n\r\nor\r\n  m_array ff<c-cr>\r\n\r\n  for(int i=0;i<m_array.length; i++){\r\n      <cursor>\r\n  }\/\/end for loop over array m_array[i]\r\n\r\nNOTE that the command function shold leave the cursor in a position that a\r\nnormal mode `o` will place the cursor at the desired location. Kind of a HACK\r\nbut good enough for now.","4":"method to simply an quickly post expand a cmd.  \"index ff<c-cr>\" for example.\r\n(<c-cr> being mapped to this cmd.)\r\n\r\nNOTE this is a QUICKY!\r\nFor what it is worth, hopefully useful to someone :)\r\n\r\nThe reason for this over a basic mapping, or DrC.Stubs is the ability to\r\nspecify the variable(s) to work on.\r\n\r\nI.e.\r\n  iInd < m_array.size() for<c-cr>\r\n\r\n  for    (    iInd = 0; iInd < m_array.size(); iInd++)\r\n  {\r\n      <cursor>\r\n  }\r\n\r\nor\r\n  m_array ff<c-cr>\r\n\r\n  for(int i=0;i<m_array.length; i++){\r\n      <cursor>\r\n  }\/\/end for loop over array m_array[i]\r\n\r\nNOTE that the command function shold leave the cursor in a position that a\r\nnormal mode `o` will place the cursor at the desired location. Kind of a HACK\r\nbut good enough for now.","install_details":"Drop in ~\/.vim\/plugin or the like.","5":"Drop in ~\/.vim\/plugin or the like.","first_name":"Robert","6":"Robert","last_name":"KellyIV","7":"KellyIV","releases":[{"0":"804","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"expand.vim","4":"expand.vim","src_id":"2427","5":"2427","creation_date":"1067274705","6":"1067274705"}]},"803":{"script_id":"803","0":"803","script_name":"XQuery syntax","1":"XQuery syntax","script_type":"syntax","2":"syntax","summary":"XQuery syntax","3":"XQuery syntax","description":"see http:\/\/jmvanel.free.fr\/vim\/","4":"see http:\/\/jmvanel.free.fr\/vim\/","install_details":"","5":"","first_name":"Jean-Marc","6":"Jean-Marc","last_name":"Vanel","7":"Vanel","releases":[{"0":"803","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"xquery.vim","4":"xquery.vim","src_id":"2425","5":"2425","creation_date":"1067175619","6":"1067175619"}]},"802":{"script_id":"802","0":"802","script_name":"gramadoir.vim","1":"gramadoir.vim","script_type":"utility","2":"utility","summary":"Interface to an Irish language grammar checker","3":"Interface to an Irish language grammar checker","description":"An Gramadoir is a command line\r\ngrammar checking engine for \r\nminority languages.  It is fully\r\nimplemented for Irish (Gaelic) at the\r\nmoment with some other languages\r\nin the works.  See\r\nhttp:\/\/borel.slu.edu\/gramadoir\/\r\nfor more information.  \r\n\r\nThis plugin provides a split screen\r\ninterface to the grammar checker,\r\nwith the text you are editing on top\r\nand a buffer containing the errors\r\noutput by An Gramadoir below.\r\n\r\nPressing <Leader>g once runs\r\nthe grammar checker and opens\r\nthe error buffer.  Each successive\r\nuse of <Leader>g moves the buffers to\r\nthe next error, in parallel.  Syntax \r\nhighlighting shows the erroneous text \r\nin red.  \r\n\r\nPressing <Leader>a stops the grammar\r\nchecker and returns to normal editing.","4":"An Gramadoir is a command line\r\ngrammar checking engine for \r\nminority languages.  It is fully\r\nimplemented for Irish (Gaelic) at the\r\nmoment with some other languages\r\nin the works.  See\r\nhttp:\/\/borel.slu.edu\/gramadoir\/\r\nfor more information.  \r\n\r\nThis plugin provides a split screen\r\ninterface to the grammar checker,\r\nwith the text you are editing on top\r\nand a buffer containing the errors\r\noutput by An Gramadoir below.\r\n\r\nPressing <Leader>g once runs\r\nthe grammar checker and opens\r\nthe error buffer.  Each successive\r\nuse of <Leader>g moves the buffers to\r\nthe next error, in parallel.  Syntax \r\nhighlighting shows the erroneous text \r\nin red.  \r\n\r\nPressing <Leader>a stops the grammar\r\nchecker and returns to normal editing.","install_details":"Drop gramadoir.vim into your plugin\r\ndirectory.     I usually also map <F3> to \r\n<Plug>Gr in my ~\/.vimrc.","5":"Drop gramadoir.vim into your plugin\r\ndirectory.     I usually also map <F3> to \r\n<Plug>Gr in my ~\/.vimrc.","first_name":"Kevin","6":"Kevin","last_name":"Scannell","7":"Scannell","releases":[{"0":"802","vim_version":"6.0","1":"6.0","script_version":"0.5","2":"0.5","version_comment":"Calls new perl backend grammar checker.  Simplified ignore file format.","3":"Calls new perl backend grammar checker.  Simplified ignore file format.","package":"gramadoir.vim","4":"gramadoir.vim","src_id":"3283","5":"3283","creation_date":"1091010356","6":"1091010356"},{"0":"802","vim_version":"6.0","1":"6.0","script_version":"0.4.1","2":"0.4.1","version_comment":"<Leader>n now adds the current error to a user\r\n\"ignore file\".   Some bug fixes for correctly dealing with errors\r\nsplit across lines.  ","3":"<Leader>n now adds the current error to a user\r\n\"ignore file\".   Some bug fixes for correctly dealing with errors\r\nsplit across lines.  ","package":"gramadoir.vim","4":"gramadoir.vim","src_id":"2732","5":"2732","creation_date":"1076263880","6":"1076263880"},{"0":"802","vim_version":"6.0","1":"6.0","script_version":"0.3","2":"0.3","version_comment":"Initial upload","3":"Initial upload","package":"gramadoir.vim","4":"gramadoir.vim","src_id":"2424","5":"2424","creation_date":"1067086686","6":"1067086686"}]},"801":{"script_id":"801","0":"801","script_name":"javaDoc.vim","1":"javaDoc.vim","script_type":"utility","2":"utility","summary":"Look up javadoc Help file from Vim [Unix Only]","3":"Look up javadoc Help file from Vim [Unix Only]","description":"Hi All,\r\nThis script looks up javaDoc HTML help files for J2SE and J2EE api classes.\r\nFirst of all I am not sure if there is already a utility to do this or not, so here is my version.\r\n\r\nAbout the script.\r\nFirst the script runs only on Unix boxes, Windows users are more that welcome to port it .\r\nMake sure that the following unix commands are present in directories mentioned in your $PATH variable.\r\ndirname,grep,xlswin,awk\r\nIt also uses a shell script provided along with this package.\r\nIt is heavily commented and can be easily modified.\r\n\r\nWhat it does and what it doesn't\r\nIt opens javaDoc HTML file in an external browser from VIM.\r\nIt can open the HTML in either Netscape (Netscape 4.x, 6,7.x, Mozilla , Firebird ) or\r\na text browser such as lynx or links. Personally I prefer to open help in netscape when I am using gvim and in a text browser when I am using vim.\r\nCurrently It only supports looking up classes and not methods , or members.\r\n\r\nHow it works.\r\nIt opens javaDoc HTML file in an external browser from VIM.\r\nIt can open the HTML in either Netscape (Netscape 4.x, 6,7.x, Mozilla , Firebird ) or\r\na text browser such as lynx or links.\r\nPersonally I prefer to open help in netscape when I am using gvim\r\nand in a text browser when I am using vim.\r\nCurrently It only supports looking up classes and not methods , or members.\r\n\r\nHow it works.\r\nYou have two ways to lookup help\r\n1)\r\nTo use the mapping <Leader>jh, the cursor has to be placed on the class name\r\nwhose help file is to be looked up. i.e.\r\nif your source is \"Connection conn = null;\"\r\nThe cursor will have to be on the word Connection.\r\nThe script can't do a reverse mapping of variable name to class name and look-up help. i.e.\r\nyou can't use the variable conn to look up help for connection.\r\n\r\n2)Use the :Javadoc command and supply the Class name as an argument.\r\ni.e. :Javadoc Connection\r\n","4":"Hi All,\r\nThis script looks up javaDoc HTML help files for J2SE and J2EE api classes.\r\nFirst of all I am not sure if there is already a utility to do this or not, so here is my version.\r\n\r\nAbout the script.\r\nFirst the script runs only on Unix boxes, Windows users are more that welcome to port it .\r\nMake sure that the following unix commands are present in directories mentioned in your $PATH variable.\r\ndirname,grep,xlswin,awk\r\nIt also uses a shell script provided along with this package.\r\nIt is heavily commented and can be easily modified.\r\n\r\nWhat it does and what it doesn't\r\nIt opens javaDoc HTML file in an external browser from VIM.\r\nIt can open the HTML in either Netscape (Netscape 4.x, 6,7.x, Mozilla , Firebird ) or\r\na text browser such as lynx or links. Personally I prefer to open help in netscape when I am using gvim and in a text browser when I am using vim.\r\nCurrently It only supports looking up classes and not methods , or members.\r\n\r\nHow it works.\r\nIt opens javaDoc HTML file in an external browser from VIM.\r\nIt can open the HTML in either Netscape (Netscape 4.x, 6,7.x, Mozilla , Firebird ) or\r\na text browser such as lynx or links.\r\nPersonally I prefer to open help in netscape when I am using gvim\r\nand in a text browser when I am using vim.\r\nCurrently It only supports looking up classes and not methods , or members.\r\n\r\nHow it works.\r\nYou have two ways to lookup help\r\n1)\r\nTo use the mapping <Leader>jh, the cursor has to be placed on the class name\r\nwhose help file is to be looked up. i.e.\r\nif your source is \"Connection conn = null;\"\r\nThe cursor will have to be on the word Connection.\r\nThe script can't do a reverse mapping of variable name to class name and look-up help. i.e.\r\nyou can't use the variable conn to look up help for connection.\r\n\r\n2)Use the :Javadoc command and supply the Class name as an argument.\r\ni.e. :Javadoc Connection\r\n","install_details":"Extract the provided .tar.gz file .\r\nPut the javadoc.vim in your plugin directory of $VIMRUNTIME or ~\/.vim.\r\nPut the javadoc.txt in your doc directory of $VIMRUNTIME or ~\/.vim.\r\nRun\r\n:helptags ~\/.vim\/doc or :helptags $VIMRUNTIME\/doc\r\nPlace the included shell script in a convenient location .\r\nMake sure to give execute permissions to the shell script.\r\n\r\nSettings                            *javadoc-settings* \r\nNow for stuff in your .vimrc file.\r\nThe script uses a trick to support several javaDoc locations, \r\ne.g. J2SE, J2EE, and any generated javadoc of your Code also.\r\nFirst define a global variable g_no_of_ID_Files to\r\nnumber of unique locations of your javaDocs.\r\ne.g. If you have J2SE and J2EE Api javadocs i.e. 2 javadocs,\r\n\r\nlet g:no_of_ID_Files=2\r\n\r\nThe define the actual locations of these API's\r\nThe file I use to look-up class name is \"allclasses-frame.html\",\r\nSo specify locations to the allclasses-frame.html for each javadoc.\r\nIf you have javaDoc of thirdparty APIs or you own Code, make sure that the allclasses-frames.html is present in it. \r\n\r\ne.g.\r\nlet g:javadoc_ID_File_1=\"\/user\/abcd\/docs\/javadoc\/JDK\/java\/api\/allclasses-frame.html\"\r\nlet g:javadoc_ID_File_2=\"\/user\/abcd\/docs\/javadoc\/\/J2EE\/java\/api\/allclasses-frame.html\"\r\n\r\nNote the first variable g:no_of_ID_Files determines how many g:_javadoc_ID_File_<cnt> should be defined.\r\n\r\nNext specify the location of the included shell script\r\nlet g:srchJdoc_loc=\"\/user\/abcd\/softwares\/usr\/bin\/srchJdoc.sh\"\r\n\r\nNext specify the commands for a GUI browser and a text browser,\r\nNote:- I use Netscape as my GUI browser and links as my text browser and\r\nthe executables for both are in my $PATH. You may want to specify the full-path\r\ndepending on your situation.\r\n\r\nlet g:javadoc_netscape_cmd=\"netscape\"\r\nlet g:javadoc_textbrowser_cmd=\"links\"\r\n\r\nBy default the Helpfile is opended using the text browser defined in g:javadoc_textbrowser_cmd.\r\nIf you want to open it using the GUI browser add the following too.\r\n\r\nlet g:jhelp_use_gui_browser=1\r\n\r\nNote:-Usually I prefer text browser, when I am using VIM from a terminal and GUI browser\r\nwhen I am using GVIM in X. For that you can put the above line in ~\/.gvimrc. This way\r\neverytime u use vim, a text browser will be used and whenever you use gvim, GUI browser will be used.\r\n","5":"Extract the provided .tar.gz file .\r\nPut the javadoc.vim in your plugin directory of $VIMRUNTIME or ~\/.vim.\r\nPut the javadoc.txt in your doc directory of $VIMRUNTIME or ~\/.vim.\r\nRun\r\n:helptags ~\/.vim\/doc or :helptags $VIMRUNTIME\/doc\r\nPlace the included shell script in a convenient location .\r\nMake sure to give execute permissions to the shell script.\r\n\r\nSettings                            *javadoc-settings* \r\nNow for stuff in your .vimrc file.\r\nThe script uses a trick to support several javaDoc locations, \r\ne.g. J2SE, J2EE, and any generated javadoc of your Code also.\r\nFirst define a global variable g_no_of_ID_Files to\r\nnumber of unique locations of your javaDocs.\r\ne.g. If you have J2SE and J2EE Api javadocs i.e. 2 javadocs,\r\n\r\nlet g:no_of_ID_Files=2\r\n\r\nThe define the actual locations of these API's\r\nThe file I use to look-up class name is \"allclasses-frame.html\",\r\nSo specify locations to the allclasses-frame.html for each javadoc.\r\nIf you have javaDoc of thirdparty APIs or you own Code, make sure that the allclasses-frames.html is present in it. \r\n\r\ne.g.\r\nlet g:javadoc_ID_File_1=\"\/user\/abcd\/docs\/javadoc\/JDK\/java\/api\/allclasses-frame.html\"\r\nlet g:javadoc_ID_File_2=\"\/user\/abcd\/docs\/javadoc\/\/J2EE\/java\/api\/allclasses-frame.html\"\r\n\r\nNote the first variable g:no_of_ID_Files determines how many g:_javadoc_ID_File_<cnt> should be defined.\r\n\r\nNext specify the location of the included shell script\r\nlet g:srchJdoc_loc=\"\/user\/abcd\/softwares\/usr\/bin\/srchJdoc.sh\"\r\n\r\nNext specify the commands for a GUI browser and a text browser,\r\nNote:- I use Netscape as my GUI browser and links as my text browser and\r\nthe executables for both are in my $PATH. You may want to specify the full-path\r\ndepending on your situation.\r\n\r\nlet g:javadoc_netscape_cmd=\"netscape\"\r\nlet g:javadoc_textbrowser_cmd=\"links\"\r\n\r\nBy default the Helpfile is opended using the text browser defined in g:javadoc_textbrowser_cmd.\r\nIf you want to open it using the GUI browser add the following too.\r\n\r\nlet g:jhelp_use_gui_browser=1\r\n\r\nNote:-Usually I prefer text browser, when I am using VIM from a terminal and GUI browser\r\nwhen I am using GVIM in X. For that you can put the above line in ~\/.gvimrc. This way\r\neverytime u use vim, a text browser will be used and whenever you use gvim, GUI browser will be used.\r\n","first_name":"vim","6":"vim","last_name":"power","7":"power","releases":[{"0":"801","vim_version":"6.0","1":"6.0","script_version":"v2","2":"v2","version_comment":"This is the second release. This contains lots of changes.\r\nMade compatible as per the write-plugin document, provided help file.\r\nNote:- The name of the plugin has been changed from javaDoc.vim to all lowercase\r\njavadoc.vim, So be sure to remove the earlier version.","3":"This is the second release. This contains lots of changes.\r\nMade compatible as per the write-plugin document, provided help file.\r\nNote:- The name of the plugin has been changed from javaDoc.vim to all lowercase\r\njavadoc.vim, So be sure to remove the earlier version.","package":"javadoc.tar.gz","4":"javadoc.tar.gz","src_id":"2429","5":"2429","creation_date":"1067349619","6":"1067349619"},{"0":"801","vim_version":"6.0","1":"6.0","script_version":"1","2":"1","version_comment":"Initial upload","3":"Initial upload","package":"javaDoc.tar.gz","4":"javaDoc.tar.gz","src_id":"2423","5":"2423","creation_date":"1066838287","6":"1066838287"}]},"800":{"script_id":"800","0":"800","script_name":"MixCase.vim","1":"MixCase.vim","script_type":"utility","2":"utility","summary":"Mix Case of typed text in the h\u00c3\u0085\u00c2\u00a9ke\u00c2\u00ae$ way (python required)","3":"Mix Case of typed text in the h\u00c3\u0085\u00c2\u00a9ke\u00c2\u00ae$ way (python required)","description":"==============================================================================\r\n1. Intoduction\r\n\r\nThis plugin does nothing very useful\r\nit modifies words :\r\n- in the hackers way (m\u00c2\u00a1x(\u00c3\u00a3$e)\r\n- in the Cambridge way : it ceganhs the odrer of the lreetts which doesn't\r\n              afceft the raitaeidbly vrey mcuh (when the wdors are not too lnog)\r\n\r\nIt now uses an ini file to customize the mi\u00c3\u0097\u00c3\u00a74$3 table the way you want.\r\nEventually, you can have many ini files to swap between many types of\r\nmI\u00c3\u0097ca5i\u00c3\u0091G\r\n\r\nNo mapping is provided as you know better than me where you want to map your\r\ncommands. Another reason is that mapping is often used for useful commands which\r\nis not the case here.\r\n\r\nThis plugin provides the following commands and functions : ~\r\nTo Mix ranges of text :\r\n :MCCambridge\r\n :MCHackerz\r\n\r\nTo Mix word under cursor and, eventually substitute all occurence :\r\n :MCHackerzMixWordUnderCurs\r\n :MCHackerzMixNSubstWordUnderCurs\r\n :MCHackerzMixSearchPattern\r\n :MCCambridgeMixWordUnderCurs\r\n :MCCambridgeMixNSubstWordUnderCurs\r\n :MCCambridgeMixSearchPattern\r\n\r\nThese commands are long to type to easily know what they do but you can map them :\r\nfor exemple, you can add\r\nmap <F2>   :MCHackerzMixWordUnderCurs<CR>\r\nin your .vimrc\r\n\r\n\r\nTo use in \\= expressions :\r\n function MixCase(...)\r\n function MixCambridge(...)\r\n\r\nTo manage ini file at runtime\r\n :MCSetIniFile\r\n :MCGoIniDir\r\n\r\nPlease, feel free to send me any comment. If you miss something (linked to\r\nm;\u00c3\u0097\u00c2\u00a24Z3, of course), I'd add it with pleasure.\r\nIf you are to vote -1, i'd be pleased to know what was wrong and what you were waiting for ;-)\r\n\r\n==============================================================================\r\n2. Content of the archive\r\n\r\n    MixCase.vim            : The plugin (-> \/plugin)\r\n    MixCase.py              : The python part of the plugin\r\n    MixCase.ini              : The default ini file\r\n    mixcase.txt                : The help file\r\n    MixCaseInv.ini          : an alternate ini file\r\n    MixCaseUTF-8.ini    : an UTF-8 encoded ini file\r\n","4":"==============================================================================\r\n1. Intoduction\r\n\r\nThis plugin does nothing very useful\r\nit modifies words :\r\n- in the hackers way (m\u00c2\u00a1x(\u00c3\u00a3$e)\r\n- in the Cambridge way : it ceganhs the odrer of the lreetts which doesn't\r\n              afceft the raitaeidbly vrey mcuh (when the wdors are not too lnog)\r\n\r\nIt now uses an ini file to customize the mi\u00c3\u0097\u00c3\u00a74$3 table the way you want.\r\nEventually, you can have many ini files to swap between many types of\r\nmI\u00c3\u0097ca5i\u00c3\u0091G\r\n\r\nNo mapping is provided as you know better than me where you want to map your\r\ncommands. Another reason is that mapping is often used for useful commands which\r\nis not the case here.\r\n\r\nThis plugin provides the following commands and functions : ~\r\nTo Mix ranges of text :\r\n :MCCambridge\r\n :MCHackerz\r\n\r\nTo Mix word under cursor and, eventually substitute all occurence :\r\n :MCHackerzMixWordUnderCurs\r\n :MCHackerzMixNSubstWordUnderCurs\r\n :MCHackerzMixSearchPattern\r\n :MCCambridgeMixWordUnderCurs\r\n :MCCambridgeMixNSubstWordUnderCurs\r\n :MCCambridgeMixSearchPattern\r\n\r\nThese commands are long to type to easily know what they do but you can map them :\r\nfor exemple, you can add\r\nmap <F2>   :MCHackerzMixWordUnderCurs<CR>\r\nin your .vimrc\r\n\r\n\r\nTo use in \\= expressions :\r\n function MixCase(...)\r\n function MixCambridge(...)\r\n\r\nTo manage ini file at runtime\r\n :MCSetIniFile\r\n :MCGoIniDir\r\n\r\nPlease, feel free to send me any comment. If you miss something (linked to\r\nm;\u00c3\u0097\u00c2\u00a24Z3, of course), I'd add it with pleasure.\r\nIf you are to vote -1, i'd be pleased to know what was wrong and what you were waiting for ;-)\r\n\r\n==============================================================================\r\n2. Content of the archive\r\n\r\n    MixCase.vim            : The plugin (-> \/plugin)\r\n    MixCase.py              : The python part of the plugin\r\n    MixCase.ini              : The default ini file\r\n    mixcase.txt                : The help file\r\n    MixCaseInv.ini          : an alternate ini file\r\n    MixCaseUTF-8.ini    : an UTF-8 encoded ini file\r\n","install_details":"4. Installation\r\n\r\nNote : this plugin uses python\r\n\r\nIt needs four files : MixCase.vim, mixcase.txt, MixCase.py and\r\nMixCase.ini\r\n\r\nMixCase.vim is to be dropped in the plugins directory, mixcase.txt in the doc\r\ndirectory and MixCase.py in a directory declared in the python path by a\r\nlittle >\r\n\tlet $PYTHONPATH=$PYTHONPATH . \"\/MyDirectory\/Python\"\r\nin your .vimrc\r\nBy default, the ini file is to be dropped in the vim directory. I must admit\r\nit is not a very clever choice but I didn't know where to put it. Anyway, you\r\ncan customize this in defining g:MC_DefaultIni in your .vimrc.\r\nlet g:MC_DefaultIni = Path\/MixCase.ini\r\n\r\nRemember that you can change the ini file at runtime with :MCSetIniFile \r\n\r\nTo init the help tags, start Vim and do either\r\n:helptags ~\/.vim\/doc (for unix)\r\nor\r\n:helptags ~\\vimfiles\\doc (for MSWindows)\r\nto rebuild the tags file. Do \":help add-local-help\" for more details.\r\n","5":"4. Installation\r\n\r\nNote : this plugin uses python\r\n\r\nIt needs four files : MixCase.vim, mixcase.txt, MixCase.py and\r\nMixCase.ini\r\n\r\nMixCase.vim is to be dropped in the plugins directory, mixcase.txt in the doc\r\ndirectory and MixCase.py in a directory declared in the python path by a\r\nlittle >\r\n\tlet $PYTHONPATH=$PYTHONPATH . \"\/MyDirectory\/Python\"\r\nin your .vimrc\r\nBy default, the ini file is to be dropped in the vim directory. I must admit\r\nit is not a very clever choice but I didn't know where to put it. Anyway, you\r\ncan customize this in defining g:MC_DefaultIni in your .vimrc.\r\nlet g:MC_DefaultIni = Path\/MixCase.ini\r\n\r\nRemember that you can change the ini file at runtime with :MCSetIniFile \r\n\r\nTo init the help tags, start Vim and do either\r\n:helptags ~\/.vim\/doc (for unix)\r\nor\r\n:helptags ~\\vimfiles\\doc (for MSWindows)\r\nto rebuild the tags file. Do \":help add-local-help\" for more details.\r\n","first_name":"jean-christophe","6":"jean-christophe","last_name":"clavier","7":"clavier","releases":[{"0":"800","vim_version":"7.0","1":"7.0","script_version":"0.5","2":"0.5","version_comment":"Python code is now compatible with python3 (yes, i know, i could have done this before :-) )","3":"Python code is now compatible with python3 (yes, i know, i could have done this before :-) )","package":"MixCase.tar.gz","4":"MixCase.tar.gz","src_id":"24448","5":"24448","creation_date":"1471294775","6":"1471294775"},{"0":"800","vim_version":"6.0","1":"6.0","script_version":"0.4","2":"0.4","version_comment":"Bug Correction","3":"Bug Correction","package":"MixCase.zip","4":"MixCase.zip","src_id":"3190","5":"3190","creation_date":"1088512975","6":"1088512975"},{"0":"800","vim_version":"6.0","1":"6.0","script_version":"0.3","2":"0.3","version_comment":"Added ini file to customize the mixcase table and a tip to allow the mix of utf-8 encoded texts (or anything else).","3":"Added ini file to customize the mixcase table and a tip to allow the mix of utf-8 encoded texts (or anything else).","package":"MixCase.zip","4":"MixCase.zip","src_id":"3184","5":"3184","creation_date":"1088171779","6":"1088171779"},{"0":"800","vim_version":"6.0","1":"6.0","script_version":"0.2","2":"0.2","version_comment":"Added vim type help file","3":"Added vim type help file","package":"MixCase.zip","4":"MixCase.zip","src_id":"2510","5":"2510","creation_date":"1069636741","6":"1069636741"},{"0":"800","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"MixCase.zip","4":"MixCase.zip","src_id":"2418","5":"2418","creation_date":"1066712748","6":"1066712748"}]},"799":{"script_id":"799","0":"799","script_name":"FindMakefile","1":"FindMakefile","script_type":"utility","2":"utility","summary":"Change directory to one containing a Makefile","3":"Change directory to one containing a Makefile","description":"Change directory to the directory containing the current file and then repeatedly \"cd ..\" until .\/Makefile exists.\r\nYou run it by enterning :call FindMakefile()\r\nI've mapped <F4> to a function that calls FindMakefile () and then does \"mak %<.o\"\r\nI needed this because using tags to jump to a source file sometimes left me with the wrong current working directory for this to work.","4":"Change directory to the directory containing the current file and then repeatedly \"cd ..\" until .\/Makefile exists.\r\nYou run it by enterning :call FindMakefile()\r\nI've mapped <F4> to a function that calls FindMakefile () and then does \"mak %<.o\"\r\nI needed this because using tags to jump to a source file sometimes left me with the wrong current working directory for this to work.","install_details":"Add the function to your .vimrc file.","5":"Add the function to your .vimrc file.","first_name":"Craig","6":"Craig","last_name":"Emery","7":"Emery","releases":[{"0":"799","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"FindMakefile.vim","4":"FindMakefile.vim","src_id":"2416","5":"2416","creation_date":"1066626956","6":"1066626956"}]},"798":{"script_id":"798","0":"798","script_name":"Walk.vim","1":"Walk.vim","script_type":"utility","2":"utility","summary":"apply a vim command to the files of a directory tree and more (python required)","3":"apply a vim command to the files of a directory tree and more (python required)","description":"This plugin intends to provide facilities to manage sets of files. For\r\nexample :\r\n. to create files from visited directory trees and files\r\n. to apply Vim commands on opened files\r\nIn fact, it autorizes files and dirs manipulation in many ways\r\n\r\nAs this plugin can manage many parameters, i decided to put these parameters\r\nin an ini file. Doing so allows you to deal with many mass treatments.\r\nIn this ini file, you can specify\r\n. a set of root dirs which trees will be visited. For Each root dir, you can\r\n  define other parameters you estimate useful\r\n. Parameters that contain strings to be written in the outfile :\r\n  . at begining and end of the file (can be connect string for command\r\n    files)\r\n  . entering and going out the root dirs\r\n  . entering and going out the visited dirs\r\n  . before and after the files found\r\n  These parameters can contain vim commands (between {{...}}) so you can do\r\n  whatever you want with the file names\r\n. You also have parameters that define\r\n  . a wildcard to filter the files\r\n  . a vim command to apply to the files found\r\n    This command may be written in the iniFile but may also be passed as a\r\n    parameter of the Walk command. If one command is written in the ini file\r\n    and another is passed to the Walk command, the inifile one is\r\n    overwritten by the parameter\r\n    If you want a result to be written in the outfile, this result may be\r\n    written in a register (cf help)\r\n  . the name of the outfile\r\nYou've got a complete example of ini file (example.ini) that can be used to\r\nsee how this plugin reacts. You just have to modify <SourceDir> and\r\n<OutFile> parameter.\r\nOther iniFile examples have been put in the package :\r\n. One is to generate a tag file with the names of the files found (exTagGen)\r\n. Another is to generate a file to prepare a syntax file to color the names\r\n  of the files found (to be used after exTagGen) (exColTagGen)\r\n  This is not very useful for source files but may be interesting to manage\r\n  simple text files with cross references\r\n. The last is to generate a directory tree (good for CDs' TOC) (exTreeGen)\r\n\r\nFeatures\r\nWGoIniDir     : Change the current dir to the inifiles dir. This is to ease\r\n                manipulation of inifiles\r\nWSetIniFile   : Initialise the inifile global variable\r\nWAddIniFile   : Add the filename passed to the inifile global variable\r\nWEditIniFile  : edits the inifile which name in passed. If this file is\r\n                empty, it is initialized with the content of \"skeleton.ini\"\r\n\r\nWalk          : launch the action, taking the inifiles wich names are\r\n                written in the inifile global variable. Walk accepts an optional\r\n                parameter that contains a vim command to be applied on the\r\n                files found. A powerful way of using this is to define\r\n                user-commands (:help user-commands)\r\n\r\nThere is other ways to launch the walk operation : you can call the walk\r\nfunction that way :\r\n:call Walk(cmd,inifile)\r\nAll the arguments must be provided (with no completion).\r\n:call Walk(\"\",iniFile)\r\nYou can write more than one ini files in the \"i\" register and type\r\n:call Walk(\"\",\"\") or\r\n:call Walk(cmd,\"\")\r\n\r\nNote : if you use the windows way of calling directories (with \\), you must\r\nbe careful : you have to write\r\n:call Walk(cmd,'D:\\my\\directory\\myIniFile.ini')\r\nor\r\n:call Walk(cmd,\"D:\\\\my\\\\directory\\\\myIniFile.ini\")\r\n\r\nNote2: This plugin may be difficult to understand at first glance. Don't hesitate to ask me if you need some more explanation...\r\n\r\n\r\nAdvertising :\r\nHave you heard of this other funny script ?\r\n\r\nIf you find this script  too serious, try this other one : \r\nhttp:\/\/www.vim.org\/scripts\/script.php?script_id=800\r\nWith this script you'll be able to MixCase like the best HaR\u00c3\u0090co\u00c2\u00ae\u00c3\u0089 mI\u00c3\u0097CaSE mAs+\u00c3\u00aaR and make your coding very new style ;-)","4":"This plugin intends to provide facilities to manage sets of files. For\r\nexample :\r\n. to create files from visited directory trees and files\r\n. to apply Vim commands on opened files\r\nIn fact, it autorizes files and dirs manipulation in many ways\r\n\r\nAs this plugin can manage many parameters, i decided to put these parameters\r\nin an ini file. Doing so allows you to deal with many mass treatments.\r\nIn this ini file, you can specify\r\n. a set of root dirs which trees will be visited. For Each root dir, you can\r\n  define other parameters you estimate useful\r\n. Parameters that contain strings to be written in the outfile :\r\n  . at begining and end of the file (can be connect string for command\r\n    files)\r\n  . entering and going out the root dirs\r\n  . entering and going out the visited dirs\r\n  . before and after the files found\r\n  These parameters can contain vim commands (between {{...}}) so you can do\r\n  whatever you want with the file names\r\n. You also have parameters that define\r\n  . a wildcard to filter the files\r\n  . a vim command to apply to the files found\r\n    This command may be written in the iniFile but may also be passed as a\r\n    parameter of the Walk command. If one command is written in the ini file\r\n    and another is passed to the Walk command, the inifile one is\r\n    overwritten by the parameter\r\n    If you want a result to be written in the outfile, this result may be\r\n    written in a register (cf help)\r\n  . the name of the outfile\r\nYou've got a complete example of ini file (example.ini) that can be used to\r\nsee how this plugin reacts. You just have to modify <SourceDir> and\r\n<OutFile> parameter.\r\nOther iniFile examples have been put in the package :\r\n. One is to generate a tag file with the names of the files found (exTagGen)\r\n. Another is to generate a file to prepare a syntax file to color the names\r\n  of the files found (to be used after exTagGen) (exColTagGen)\r\n  This is not very useful for source files but may be interesting to manage\r\n  simple text files with cross references\r\n. The last is to generate a directory tree (good for CDs' TOC) (exTreeGen)\r\n\r\nFeatures\r\nWGoIniDir     : Change the current dir to the inifiles dir. This is to ease\r\n                manipulation of inifiles\r\nWSetIniFile   : Initialise the inifile global variable\r\nWAddIniFile   : Add the filename passed to the inifile global variable\r\nWEditIniFile  : edits the inifile which name in passed. If this file is\r\n                empty, it is initialized with the content of \"skeleton.ini\"\r\n\r\nWalk          : launch the action, taking the inifiles wich names are\r\n                written in the inifile global variable. Walk accepts an optional\r\n                parameter that contains a vim command to be applied on the\r\n                files found. A powerful way of using this is to define\r\n                user-commands (:help user-commands)\r\n\r\nThere is other ways to launch the walk operation : you can call the walk\r\nfunction that way :\r\n:call Walk(cmd,inifile)\r\nAll the arguments must be provided (with no completion).\r\n:call Walk(\"\",iniFile)\r\nYou can write more than one ini files in the \"i\" register and type\r\n:call Walk(\"\",\"\") or\r\n:call Walk(cmd,\"\")\r\n\r\nNote : if you use the windows way of calling directories (with \\), you must\r\nbe careful : you have to write\r\n:call Walk(cmd,'D:\\my\\directory\\myIniFile.ini')\r\nor\r\n:call Walk(cmd,\"D:\\\\my\\\\directory\\\\myIniFile.ini\")\r\n\r\nNote2: This plugin may be difficult to understand at first glance. Don't hesitate to ask me if you need some more explanation...\r\n\r\n\r\nAdvertising :\r\nHave you heard of this other funny script ?\r\n\r\nIf you find this script  too serious, try this other one : \r\nhttp:\/\/www.vim.org\/scripts\/script.php?script_id=800\r\nWith this script you'll be able to MixCase like the best HaR\u00c3\u0090co\u00c2\u00ae\u00c3\u0089 mI\u00c3\u0097CaSE mAs+\u00c3\u00aaR and make your coding very new style ;-)","install_details":"Warning : this plugin uses python\r\n\r\nIt is made of four files : Walk.vim, Walk.py, FicIni.py and walk.txt.\r\nThe .vim file is to be dropped in the plugins directory, the .txt in the doc\r\ndirectory and the .py in a directory declared in the python path by a little >\r\n\tlet $PYTHONPATH=$PYTHONPATH . \"\/MyDirectory\/Python\"\r\nin your .vimrc\r\n\r\nyou also have an .ini file examples (example.ini, exTagGen.ini,\r\nexColTagGen.ini and exTreeGen) and a skeleton for .ini files (skeleton.ini).\r\nThese files are to be dropped in an inifiles directory (you decide).\r\nSkeleton.ini is used by the WEditIniFile command.\r\nTo use the examples, you'll have to edit them to change the <SourceDir> and\r\nthe <OutFile> parameter\r\n\r\nTo ease the edition of the ini files, you have to init another variable in\r\nyour .vimrc ($WALKINIDIR): >\r\n\tlet $WALKINIDIR = \"MyDirectory\/iniFiles\"\r\n\r\nTo init the help tags, start Vim and do either\r\n:helptags ~\/.vim\/doc (for unix)\r\nor\r\n:helptags ~\\vimfiles\\doc (for MSWindows)\r\nto rebuild the tags file. Do \":help add-local-help\" for more details.\r\n\r\nNOTE:\r\nFicIni.py provides a class to parse xml ini files (details in FicIni.py)\r\n\r\n","5":"Warning : this plugin uses python\r\n\r\nIt is made of four files : Walk.vim, Walk.py, FicIni.py and walk.txt.\r\nThe .vim file is to be dropped in the plugins directory, the .txt in the doc\r\ndirectory and the .py in a directory declared in the python path by a little >\r\n\tlet $PYTHONPATH=$PYTHONPATH . \"\/MyDirectory\/Python\"\r\nin your .vimrc\r\n\r\nyou also have an .ini file examples (example.ini, exTagGen.ini,\r\nexColTagGen.ini and exTreeGen) and a skeleton for .ini files (skeleton.ini).\r\nThese files are to be dropped in an inifiles directory (you decide).\r\nSkeleton.ini is used by the WEditIniFile command.\r\nTo use the examples, you'll have to edit them to change the <SourceDir> and\r\nthe <OutFile> parameter\r\n\r\nTo ease the edition of the ini files, you have to init another variable in\r\nyour .vimrc ($WALKINIDIR): >\r\n\tlet $WALKINIDIR = \"MyDirectory\/iniFiles\"\r\n\r\nTo init the help tags, start Vim and do either\r\n:helptags ~\/.vim\/doc (for unix)\r\nor\r\n:helptags ~\\vimfiles\\doc (for MSWindows)\r\nto rebuild the tags file. Do \":help add-local-help\" for more details.\r\n\r\nNOTE:\r\nFicIni.py provides a class to parse xml ini files (details in FicIni.py)\r\n\r\n","first_name":"jean-christophe","6":"jean-christophe","last_name":"clavier","7":"clavier","releases":[{"0":"798","vim_version":"6.0","1":"6.0","script_version":"0.9","2":"0.9","version_comment":"Added a tutorial and a way to call python functions","3":"Added a tutorial and a way to call python functions","package":"walk.zip","4":"walk.zip","src_id":"7212","5":"7212","creation_date":"1181175067","6":"1181175067"},{"0":"798","vim_version":"6.0","1":"6.0","script_version":"0.7","2":"0.7","version_comment":"added vim help file, reduced use of registers, allowed use of multiple out files and other minor features","3":"added vim help file, reduced use of registers, allowed use of multiple out files and other minor features","package":"Walk.zip","4":"Walk.zip","src_id":"2512","5":"2512","creation_date":"1069661170","6":"1069661170"},{"0":"798","vim_version":"6.0","1":"6.0","script_version":"0.6","2":"0.6","version_comment":"Oups, i uploaded the wrong package","3":"Oups, i uploaded the wrong package","package":"Walk.zip","4":"Walk.zip","src_id":"2504","5":"2504","creation_date":"1069399062","6":"1069399062"},{"0":"798","vim_version":"6.0","1":"6.0","script_version":"0.4","2":"0.4","version_comment":"automaticaly opens the outfile at the end","3":"automaticaly opens the outfile at the end","package":"VimWalk.zip","4":"VimWalk.zip","src_id":"2421","5":"2421","creation_date":"1066795186","6":"1066795186"},{"0":"798","vim_version":"6.0","1":"6.0","script_version":"0.3","2":"0.3","version_comment":"Added commands to ease the parameters passing","3":"Added commands to ease the parameters passing","package":"VimWalk.zip","4":"VimWalk.zip","src_id":"2420","5":"2420","creation_date":"1066789530","6":"1066789530"},{"0":"798","vim_version":"6.0","1":"6.0","script_version":"0.2","2":"0.2","version_comment":"Correction of a typing error in the description of the plugin : the register used for the directory was not \"n\" and is now \"d\"","3":"Correction of a typing error in the description of the plugin : the register used for the directory was not \"n\" and is now \"d\"","package":"vimWalk.zip","4":"vimWalk.zip","src_id":"2417","5":"2417","creation_date":"1066699268","6":"1066699268"}]},"797":{"script_id":"797","0":"797","script_name":"preview.vim","1":"preview.vim","script_type":"utility","2":"utility","summary":"Preview current file in selected browser.","3":"Preview current file in selected browser.","description":"This has been tested on windows only. It  can probably be made to work on linux but is untested on that platform..(one day ;-)) \r\n(If anyone modifies this script to work on both platforms, please feel free to upload the modified script)\r\n\r\nPressing <S-F12> will prompt you for the browser you would like to preview the current file in. Browsers can be added by modifying the appropriately commented lines in the script.  (make sure to modify the current paths for browsers on your system).\r\n\r\nThere is also the option to include only files of a specific type. These are .php, .php3, .jsp, .asp, .html, .htm, and .vim at the moment but others can easily be added.\r\n\r\nIf the file is in your server directory (http:\\\\localhost\\) or a sub directory of it, it will be previewed through the server - NOT as a local file. \r\n\r\negs http:\\\\localhost\\test.php\r\n        http:\\\\localhost\\examples\\chapter04\\index.php\r\n\r\nOtherwise it will be previewed simply as a local file\r\neg    c:\\mysite\\index.html\r\n","4":"This has been tested on windows only. It  can probably be made to work on linux but is untested on that platform..(one day ;-)) \r\n(If anyone modifies this script to work on both platforms, please feel free to upload the modified script)\r\n\r\nPressing <S-F12> will prompt you for the browser you would like to preview the current file in. Browsers can be added by modifying the appropriately commented lines in the script.  (make sure to modify the current paths for browsers on your system).\r\n\r\nThere is also the option to include only files of a specific type. These are .php, .php3, .jsp, .asp, .html, .htm, and .vim at the moment but others can easily be added.\r\n\r\nIf the file is in your server directory (http:\\\\localhost\\) or a sub directory of it, it will be previewed through the server - NOT as a local file. \r\n\r\negs http:\\\\localhost\\test.php\r\n        http:\\\\localhost\\examples\\chapter04\\index.php\r\n\r\nOtherwise it will be previewed simply as a local file\r\neg    c:\\mysite\\index.html\r\n","install_details":"place in your  plugin directory","5":"place in your  plugin directory","first_name":"Mark","6":"Mark","last_name":"Woodward","7":"Woodward","releases":[{"0":"797","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"preview.vim","4":"preview.vim","src_id":"2413","5":"2413","creation_date":"1066500818","6":"1066500818"}]},"796":{"script_id":"796","0":"796","script_name":"bmichaelsen","1":"bmichaelsen","script_type":"color scheme","2":"color scheme","summary":"Colorscheme matching PrettyBlueish and Purplehaze","3":"Colorscheme matching PrettyBlueish and Purplehaze","description":"This colorscheme matches the PrettyBlueish\r\nGtk-theme and the Purplehaze Fluxbox-theme\r\nIt is based on the Zellner colorscheme maintained by Ron Aaron <ronaharon at yahoo.com>\r\nKudos to him, I just did some minor modifications.\r\nMaybe someone will find this useful.\r\nScreenshots with GTK-Vim and vim in xterm:\r\nhttp:\/\/michaelsen.kicks-ass.net\/bjoern\/vimscreen2.png\r\nhttp:\/\/michaelsen.kicks-ass.net\/bjoern\/vimscreen1.png (big)","4":"This colorscheme matches the PrettyBlueish\r\nGtk-theme and the Purplehaze Fluxbox-theme\r\nIt is based on the Zellner colorscheme maintained by Ron Aaron <ronaharon at yahoo.com>\r\nKudos to him, I just did some minor modifications.\r\nMaybe someone will find this useful.\r\nScreenshots with GTK-Vim and vim in xterm:\r\nhttp:\/\/michaelsen.kicks-ass.net\/bjoern\/vimscreen2.png\r\nhttp:\/\/michaelsen.kicks-ass.net\/bjoern\/vimscreen1.png (big)","install_details":"(linux users:) copy the file to \/usr\/share\/vim\/vim62\/colors\/bmichaelsen.vim and put\r\n:colorscheme bmichaelsen\r\ninto your ~\/.vimrc\r\n","5":"(linux users:) copy the file to \/usr\/share\/vim\/vim62\/colors\/bmichaelsen.vim and put\r\n:colorscheme bmichaelsen\r\ninto your ~\/.vimrc\r\n","first_name":"Bj\u00c3\u00b6rn","6":"Bj\u00c3\u00b6rn","last_name":"Michaelsen","7":"Michaelsen","releases":[{"0":"796","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"bmichaelsen.vim","4":"bmichaelsen.vim","src_id":"2412","5":"2412","creation_date":"1066483514","6":"1066483514"}]},"795":{"script_id":"795","0":"795","script_name":"xterm16.vim","1":"xterm16.vim","script_type":"color scheme","2":"color scheme","summary":"An adjustable contrast color scheme for GUI and 8, 16 or 256 color terminals.","3":"An adjustable contrast color scheme for GUI and 8, 16 or 256 color terminals.","description":"An adjustable contrast fully customisable color scheme for GUI & 8, 16 or 256 color terminals, designed to minimise eyestrain. The main features are:\r\n\r\n\t- Four color maps:\r\n\t    'allblue'   : A colormap with most foreground colors blueish (to\r\n\t\t          minimize contrast etc.)\r\n\t    'soft'      : A colormap with foreground colors of similar\r\n\t\t          intensities to reduce eyestrain.\r\n\t    'softlight' : A colormap with a bright background (for web\r\n\t\t          hosting etc.)\r\n\t    'standard'  : A colormap for use on terminals with only 8\/16\r\n\t\t\t   colors.\r\n\t  The first three colormaps will work only on 256 color capable\r\n\t  terminals or the GUI. The last one will work anywhere.\r\n\r\n\t- Adjustable brightness \/ contrast. Lets you easily adjust the\r\n\t  brightness and contrast settings. Extremely useful (for instance)\r\n\t  when there is a glare on your monitor, or for long late dim light\r\n\t  dim light late at night :)\r\n\r\n\t- Terminal and GUI support. If you use xterm, rxvt or mrxvt (compiled\r\n\t  with 256 colors), then the colors on your terminal will be almost\r\n\t  identical to your GUI colors. On any other terminal emulator, a few\r\n\t  scripts (included) and parts of this help are designed to help you\r\n\t  get the colors you want.\r\n\r\n\t- LCD \/ CRT Monitor support. The color response of LCD and CRT\r\n\t  monitors is pretty different. This color scheme has an option to\r\n\t  adjust colors on CRT monitors to give a similar appearance.\r\n\r\n\t- Customizable colors. If you find any color unreadable or ugly, you\r\n\t  can change it easily. When adjusting the brightness, your custom\r\n\t  colors will be suitably adjusted too!\r\n\r\n\t- Customizable highlighting groups. If you don't like the highlighting\r\n\t  of any particular group, you can change it to suit your needs. This\r\n\t  is useful for instance if you want the cursor to be brighter than\r\n\t  everything else \/ etc.\r\n\r\nThe first screenshot below is also the complete documentation and description.\r\n\r\nScreenshots:\r\n\r\nhttp:\/\/www.math.cmu.edu\/~gautam\/per\/opensource\/xterm16\/xterm16-doc.html [Complete documentation and description]\r\nhttp:\/\/www.math.cmu.edu\/~gautam\/per\/opensource\/xterm16\/xterm16-src.html [HTMLised source]\r\nhttp:\/\/www.math.cmu.edu\/~gautam\/per\/opensource\/xterm16\/c-source.html [HTMLised C code]\r\nhttp:\/\/www.math.cmu.edu\/~gautam\/per\/opensource\/xterm16\/timestamp-doc.html [Another VIM help file]\r\nhttp:\/\/www.math.cmu.edu\/~gautam\/per\/opensource\/xterm16\/email.html [HTMLised email]\r\nhttp:\/\/www.math.cmu.edu\/~gautam\/per\/opensource\/xterm16\/mrxvt.png [Transparent background in mrxvt]\r\n\r\n(On javascript enabled 'good' browsers, you should be able to adjust the Brightness, colormap and monitor type in each of the HTMLised screenshots above.)\r\n","4":"An adjustable contrast fully customisable color scheme for GUI & 8, 16 or 256 color terminals, designed to minimise eyestrain. The main features are:\r\n\r\n\t- Four color maps:\r\n\t    'allblue'   : A colormap with most foreground colors blueish (to\r\n\t\t          minimize contrast etc.)\r\n\t    'soft'      : A colormap with foreground colors of similar\r\n\t\t          intensities to reduce eyestrain.\r\n\t    'softlight' : A colormap with a bright background (for web\r\n\t\t          hosting etc.)\r\n\t    'standard'  : A colormap for use on terminals with only 8\/16\r\n\t\t\t   colors.\r\n\t  The first three colormaps will work only on 256 color capable\r\n\t  terminals or the GUI. The last one will work anywhere.\r\n\r\n\t- Adjustable brightness \/ contrast. Lets you easily adjust the\r\n\t  brightness and contrast settings. Extremely useful (for instance)\r\n\t  when there is a glare on your monitor, or for long late dim light\r\n\t  dim light late at night :)\r\n\r\n\t- Terminal and GUI support. If you use xterm, rxvt or mrxvt (compiled\r\n\t  with 256 colors), then the colors on your terminal will be almost\r\n\t  identical to your GUI colors. On any other terminal emulator, a few\r\n\t  scripts (included) and parts of this help are designed to help you\r\n\t  get the colors you want.\r\n\r\n\t- LCD \/ CRT Monitor support. The color response of LCD and CRT\r\n\t  monitors is pretty different. This color scheme has an option to\r\n\t  adjust colors on CRT monitors to give a similar appearance.\r\n\r\n\t- Customizable colors. If you find any color unreadable or ugly, you\r\n\t  can change it easily. When adjusting the brightness, your custom\r\n\t  colors will be suitably adjusted too!\r\n\r\n\t- Customizable highlighting groups. If you don't like the highlighting\r\n\t  of any particular group, you can change it to suit your needs. This\r\n\t  is useful for instance if you want the cursor to be brighter than\r\n\t  everything else \/ etc.\r\n\r\nThe first screenshot below is also the complete documentation and description.\r\n\r\nScreenshots:\r\n\r\nhttp:\/\/www.math.cmu.edu\/~gautam\/per\/opensource\/xterm16\/xterm16-doc.html [Complete documentation and description]\r\nhttp:\/\/www.math.cmu.edu\/~gautam\/per\/opensource\/xterm16\/xterm16-src.html [HTMLised source]\r\nhttp:\/\/www.math.cmu.edu\/~gautam\/per\/opensource\/xterm16\/c-source.html [HTMLised C code]\r\nhttp:\/\/www.math.cmu.edu\/~gautam\/per\/opensource\/xterm16\/timestamp-doc.html [Another VIM help file]\r\nhttp:\/\/www.math.cmu.edu\/~gautam\/per\/opensource\/xterm16\/email.html [HTMLised email]\r\nhttp:\/\/www.math.cmu.edu\/~gautam\/per\/opensource\/xterm16\/mrxvt.png [Transparent background in mrxvt]\r\n\r\n(On javascript enabled 'good' browsers, you should be able to adjust the Brightness, colormap and monitor type in each of the HTMLised screenshots above.)\r\n","install_details":"For local installation, put the |xterm16.vim| file in your ~\/.vim\/colors directory. To install globally put it in $VIMRUNTIME\/colors. Finally add the following lines to your {.vimrc}: >\r\n\r\n    \" let xterm16_brightness = 'default'     \" Change if needed\r\n    \" let xterm16_colormap = 'allblue'       \" Change if needed\r\n    colo xterm16\r\n\r\nIf you want to change the default colors on your terminal (to match those in the screenshots) look at the file \"xterm16.txt\" (in Vim if you want it to look pretty) for details. (You can also view it online at the above links)","5":"For local installation, put the |xterm16.vim| file in your ~\/.vim\/colors directory. To install globally put it in $VIMRUNTIME\/colors. Finally add the following lines to your {.vimrc}: >\r\n\r\n    \" let xterm16_brightness = 'default'     \" Change if needed\r\n    \" let xterm16_colormap = 'allblue'       \" Change if needed\r\n    colo xterm16\r\n\r\nIf you want to change the default colors on your terminal (to match those in the screenshots) look at the file \"xterm16.txt\" (in Vim if you want it to look pretty) for details. (You can also view it online at the above links)","first_name":"gi1242","6":"gi1242","last_name":"gi1242","7":"gi1242","releases":[{"0":"795","vim_version":"7.0","1":"7.0","script_version":"2.43","2":"2.43","version_comment":"Added highlighting groups for the Tab line (thanks to Paddy Newman).","3":"Added highlighting groups for the Tab line (thanks to Paddy Newman).","package":"xterm16-2.43.tbz2","4":"xterm16-2.43.tbz2","src_id":"6172","5":"6172","creation_date":"1158060940","6":"1158060940"},{"0":"795","vim_version":"7.0","1":"7.0","script_version":"2.42","2":"2.42","version_comment":"Fixed glaring documentation error (should set t_Co=256, and not 16). Minor highlighting group bugfixes. ","3":"Fixed glaring documentation error (should set t_Co=256, and not 16). Minor highlighting group bugfixes. ","package":"xterm16-2.42.tbz2","4":"xterm16-2.42.tbz2","src_id":"5721","5":"5721","creation_date":"1147968277","6":"1147968277"},{"0":"795","vim_version":"7.0","1":"7.0","script_version":"2.41","2":"2.41","version_comment":"Minor changes to highlighting groups: Added cursorline & cursorcollumn (thanks to Georg Dhan for pointing this out). Also made sure that Comments are a different color than other highlighting groups in the 'allblue' colormap.","3":"Minor changes to highlighting groups: Added cursorline & cursorcollumn (thanks to Georg Dhan for pointing this out). Also made sure that Comments are a different color than other highlighting groups in the 'allblue' colormap.","package":"xterm16-2.41.tbz2","4":"xterm16-2.41.tbz2","src_id":"5565","5":"5565","creation_date":"1145178821","6":"1145178821"},{"0":"795","vim_version":"7.0","1":"7.0","script_version":"2.4","2":"2.4","version_comment":"Added an \"allblue\" colormap (makes all foreground colors a shade of blue). Also added a \"softlight\" colormap with light background for webhosting. Added syntax items for Vim7 (is still backward compatible to vim6.4)","3":"Added an \"allblue\" colormap (makes all foreground colors a shade of blue). Also added a \"softlight\" colormap with light background for webhosting. Added syntax items for Vim7 (is still backward compatible to vim6.4)","package":"xterm16-2.4.tbz2","4":"xterm16-2.4.tbz2","src_id":"5515","5":"5515","creation_date":"1144144334","6":"1144144334"},{"0":"795","vim_version":"6.0","1":"6.0","script_version":"2.2","2":"2.2","version_comment":"Now fully supports rxvt and mrxvt when compiled with 256 colors. Included an option for transparency with mrxvt. Added a perl script to make changing colors on 16 color terminals easier. Few minor color modifications (StatusLine, StatusLineNC). I mainly wrote this so I can switch to mrxvt with transparency without changing my precious colors :)","3":"Now fully supports rxvt and mrxvt when compiled with 256 colors. Included an option for transparency with mrxvt. Added a perl script to make changing colors on 16 color terminals easier. Few minor color modifications (StatusLine, StatusLineNC). I mainly wrote this so I can switch to mrxvt with transparency without changing my precious colors :)","package":"xterm16-2.2.tbz2","4":"xterm16-2.2.tbz2","src_id":"4342","5":"4342","creation_date":"1117880063","6":"1117880063"},{"0":"795","vim_version":"6.0","1":"6.0","script_version":"2.1","2":"2.1","version_comment":"Improved version to support adjustable brightness and contrast, CRT \/ LCD monitors. Includes a new 'soft' colormap, where all foreground colors are of almost 'equal' intensity for long late night coding sessions. This version takes advantage of xterm's color support. If you use xterm (compiled with 256 colors), then this script can adjust the colors automatically (without making you mess with .Xresources etc). [Ofcourse, it works on other terminals \/ GUI too].","3":"Improved version to support adjustable brightness and contrast, CRT \/ LCD monitors. Includes a new 'soft' colormap, where all foreground colors are of almost 'equal' intensity for long late night coding sessions. This version takes advantage of xterm's color support. If you use xterm (compiled with 256 colors), then this script can adjust the colors automatically (without making you mess with .Xresources etc). [Ofcourse, it works on other terminals \/ GUI too].","package":"xterm16-2.1.tbz2","4":"xterm16-2.1.tbz2","src_id":"3636","5":"3636","creation_date":"1100511976","6":"1100511976"},{"0":"795","vim_version":"6.0","1":"6.0","script_version":"1.3","2":"1.3","version_comment":"Changed the Diff \/ Fold highlighting groups. Added files to change default colors of ctheme (thanks to Juhapekka Tolvanen) and rxvt.","3":"Changed the Diff \/ Fold highlighting groups. Added files to change default colors of ctheme (thanks to Juhapekka Tolvanen) and rxvt.","package":"xterm16.tbz2","4":"xterm16.tbz2","src_id":"2520","5":"2520","creation_date":"1069855765","6":"1069855765"},{"0":"795","vim_version":"6.0","1":"6.0","script_version":"1.2","2":"1.2","version_comment":"Added support to remap the unreadable darkblue on the linux console. Disabled HTML groups from using cterm attributes and used colors instead. Added options to customise GUI colors. All options added here can be disabled.","3":"Added support to remap the unreadable darkblue on the linux console. Disabled HTML groups from using cterm attributes and used colors instead. Added options to customise GUI colors. All options added here can be disabled.","package":"xterm16.tbz2","4":"xterm16.tbz2","src_id":"2463","5":"2463","creation_date":"1068135333","6":"1068135333"},{"0":"795","vim_version":"6.0","1":"6.0","script_version":"1.1","2":"1.1","version_comment":"Minor Changes to highlighting groups. Now includes files to change colors on xterm, konsole or gnome-terminal to make the red \/ dark blue colors more readable.","3":"Minor Changes to highlighting groups. Now includes files to change colors on xterm, konsole or gnome-terminal to make the red \/ dark blue colors more readable.","package":"xterm16.tbz2","4":"xterm16.tbz2","src_id":"2451","5":"2451","creation_date":"1067982792","6":"1067982792"}]},"794":{"script_id":"794","0":"794","script_name":"promela.vim","1":"promela.vim","script_type":"syntax","2":"syntax","summary":"Promela syntax highlighting","3":"Promela syntax highlighting","description":"This is syntax highlighting for the Promela language used with SPIN\r\n(http:\/\/spinroot.com\/spin\/whatispin.html).","4":"This is syntax highlighting for the Promela language used with SPIN\r\n(http:\/\/spinroot.com\/spin\/whatispin.html).","install_details":"Untar and copy promela.vim file to your Vim syntax directory. See included\r\nREADME for more detail.","5":"Untar and copy promela.vim file to your Vim syntax directory. See included\r\nREADME for more detail.","first_name":"pieter","6":"pieter","last_name":"loubser","7":"loubser","releases":[{"0":"794","vim_version":"6.0","1":"6.0","script_version":"0.3","2":"0.3","version_comment":"Other C-like comments '\/\/' highlighting added","3":"Other C-like comments '\/\/' highlighting added","package":"promela-vim.tgz","4":"promela-vim.tgz","src_id":"2502","5":"2502","creation_date":"1069379800","6":"1069379800"},{"0":"794","vim_version":"6.0","1":"6.0","script_version":"0.2","2":"0.2","version_comment":"#define highlighting over multiple lines is now fixed.","3":"#define highlighting over multiple lines is now fixed.","package":"promela-vim.tgz","4":"promela-vim.tgz","src_id":"2434","5":"2434","creation_date":"1067496376","6":"1067496376"},{"0":"794","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"promela-vim.tgz","4":"promela-vim.tgz","src_id":"2405","5":"2405","creation_date":"1066290161","6":"1066290161"}]},"793":{"script_id":"793","0":"793","script_name":"ttcn-ftplugin","1":"ttcn-ftplugin","script_type":"ftplugin","2":"ftplugin","summary":"TTCN-3 ftplugin file","3":"TTCN-3 ftplugin file","description":"This is a simple ftplugin for TTCN-3. You should put settings that are specific to TTCN in this file.","4":"This is a simple ftplugin for TTCN-3. You should put settings that are specific to TTCN in this file.","install_details":"Just drop the file in your local ftplugin directory (e.g. ~\/.vim\/ftplugin).\r\n\r\nNote: If you want to make Vim automatically detect the file type *.ttcn, see the \"install details\" section of the TTCN-3 syntax highlighting script (vimscript #753).","5":"Just drop the file in your local ftplugin directory (e.g. ~\/.vim\/ftplugin).\r\n\r\nNote: If you want to make Vim automatically detect the file type *.ttcn, see the \"install details\" section of the TTCN-3 syntax highlighting script (vimscript #753).","first_name":"Stefan","6":"Stefan","last_name":"Karlsson","7":"Karlsson","releases":[{"0":"793","vim_version":"6.0","1":"6.0","script_version":"0.4","2":"0.4","version_comment":"1. Fixed so that Vim's gf, [i, ]i, etc. commands works for ttcn files.\r\n2. Moved some settings to the indent plugin, so make sure you download the latest ttcn-indent script as well!","3":"1. Fixed so that Vim's gf, [i, ]i, etc. commands works for ttcn files.\r\n2. Moved some settings to the indent plugin, so make sure you download the latest ttcn-indent script as well!","package":"ttcn.vim","4":"ttcn.vim","src_id":"2939","5":"2939","creation_date":"1082128055","6":"1082128055"}]},"792":{"script_id":"792","0":"792","script_name":"simpleandfriendly.vim","1":"simpleandfriendly.vim","script_type":"color scheme","2":"color scheme","summary":"A simple color scheme - with some eye-friendly colors.","3":"A simple color scheme - with some eye-friendly colors.","description":"This colors evolved over a long time. I tried to use very eye-friendly colors and put some optical emphasis on comments.\r\n\r\nScreenshot: http:\/\/www.oxpal.com\/downloads\/vim\/simpleandfriendly_split.png\r\n\r\nI looked for more subtle colors than those of the VI-distrib. I took a default-scheme and changed around, 'til I liked it. Not sure if the commands are enough for hardcore programmers that work with complex syntax, so please let me know where I can enhance it. ","4":"This colors evolved over a long time. I tried to use very eye-friendly colors and put some optical emphasis on comments.\r\n\r\nScreenshot: http:\/\/www.oxpal.com\/downloads\/vim\/simpleandfriendly_split.png\r\n\r\nI looked for more subtle colors than those of the VI-distrib. I took a default-scheme and changed around, 'til I liked it. Not sure if the commands are enough for hardcore programmers that work with complex syntax, so please let me know where I can enhance it. ","install_details":"Download and move to the ~\/.vim\/colors Folder. You can then choose the scheme from the menu (Edit>Color Scheme>simpleandfriendly) or type \r\n:colorscheme simpleandfriendly\r\n\r\nIf you want a color scheme as default you simply write the command in your ~\/.vimrc file - in this case:\r\ncolorscheme simpleandfriendly\r\n","5":"Download and move to the ~\/.vim\/colors Folder. You can then choose the scheme from the menu (Edit>Color Scheme>simpleandfriendly) or type \r\n:colorscheme simpleandfriendly\r\n\r\nIf you want a color scheme as default you simply write the command in your ~\/.vimrc file - in this case:\r\ncolorscheme simpleandfriendly\r\n","first_name":"Thomas","6":"Thomas","last_name":"Schmall","7":"Schmall","releases":[{"0":"792","vim_version":"6.0","1":"6.0","script_version":"1.4","2":"1.4","version_comment":"Added highlighting for current line.","3":"Added highlighting for current line.","package":"simpleandfriendly.vim","4":"simpleandfriendly.vim","src_id":"11645","5":"11645","creation_date":"1257128096","6":"1257128096"},{"0":"792","vim_version":"6.0","1":"6.0","script_version":"1.3","2":"1.3","version_comment":"line number colors changed","3":"line number colors changed","package":"simpleandfriendly.vim","4":"simpleandfriendly.vim","src_id":"3643","5":"3643","creation_date":"1100877599","6":"1100877599"},{"0":"792","vim_version":"6.0","1":"6.0","script_version":"1.2","2":"1.2","version_comment":"included title, number and const","3":"included title, number and const","package":"simpleandfriendly.vim","4":"simpleandfriendly.vim","src_id":"3131","5":"3131","creation_date":"1087209923","6":"1087209923"},{"0":"792","vim_version":"6.0","1":"6.0","script_version":"1.1","2":"1.1","version_comment":"- included more color definitions (operator (bold), identifier, error, special and todo) \r\n- changed some colors (identifier and type aso)","3":"- included more color definitions (operator (bold), identifier, error, special and todo) \r\n- changed some colors (identifier and type aso)","package":"simpleandfriendly.vim","4":"simpleandfriendly.vim","src_id":"3121","5":"3121","creation_date":"1087155892","6":"1087155892"},{"0":"792","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"uploaded again, because of the wrong file ending","3":"uploaded again, because of the wrong file ending","package":"simpleandfriendly.vim","4":"simpleandfriendly.vim","src_id":"2400","5":"2400","creation_date":"1066151196","6":"1066151196"}]},"791":{"script_id":"791","0":"791","script_name":"Relaxed Green","1":"Relaxed Green","script_type":"color scheme","2":"color scheme","summary":"Relaxed green color scheme for vim and gvim.","3":"Relaxed green color scheme for vim and gvim.","description":"Simple color scheme.  Easy on the eyes for long coding sessions.","4":"Simple color scheme.  Easy on the eyes for long coding sessions.","install_details":"Place script in your .vim\/colors directory and load it with:\n    :colorscheme relaxedgreen","5":"Place script in your .vim\/colors directory and load it with:\n    :colorscheme relaxedgreen","first_name":"Dave","6":"Dave","last_name":"Vehrs","7":"Vehrs","releases":[{"0":"791","vim_version":"6.0","1":"6.0","script_version":"0.6.4","2":"0.6.4","version_comment":"Updated and cleaned up.","3":"Updated and cleaned up.","package":"relaxedgreen.vim","4":"relaxedgreen.vim","src_id":"6742","5":"6742","creation_date":"1171400307","6":"1171400307"},{"0":"791","vim_version":"7.0","1":"7.0","script_version":"0.6.3","2":"0.6.3","version_comment":"Tweaked the colors for popup menus and the tab bar.","3":"Tweaked the colors for popup menus and the tab bar.","package":"relaxedgreen.vim","4":"relaxedgreen.vim","src_id":"6069","5":"6069","creation_date":"1155561969","6":"1155561969"},{"0":"791","vim_version":"7.0","1":"7.0","script_version":"0.6.2a","2":"0.6.2a","version_comment":"Fixed three typos\/bugs (thanks to Dave.Nyc@[REMOVED].net for the heads up) and some general GUI color cleanups.","3":"Fixed three typos\/bugs (thanks to Dave.Nyc@[REMOVED].net for the heads up) and some general GUI color cleanups.","package":"relaxedgreen.vim","4":"relaxedgreen.vim","src_id":"5775","5":"5775","creation_date":"1148645936","6":"1148645936"},{"0":"791","vim_version":"7.0","1":"7.0","script_version":"0.6.2","2":"0.6.2","version_comment":"More Vim 7.0 patches.","3":"More Vim 7.0 patches.","package":"relaxedgreen.vim","4":"relaxedgreen.vim","src_id":"5770","5":"5770","creation_date":"1148608146","6":"1148608146"},{"0":"791","vim_version":"7.0","1":"7.0","script_version":"0.6.1","2":"0.6.1","version_comment":"Added support for Vim 7 Pmenu* items.","3":"Added support for Vim 7 Pmenu* items.","package":"relaxedgreen.vim","4":"relaxedgreen.vim","src_id":"5352","5":"5352","creation_date":"1141305418","6":"1141305418"},{"0":"791","vim_version":"6.0","1":"6.0","script_version":"0.6","2":"0.6","version_comment":"Added support for new Vim 7a tags (Tabline* + Spell*).","3":"Added support for new Vim 7a tags (Tabline* + Spell*).","package":"relaxedgreen.vim","4":"relaxedgreen.vim","src_id":"5340","5":"5340","creation_date":"1141123111","6":"1141123111"},{"0":"791","vim_version":"6.0","1":"6.0","script_version":"0.5","2":"0.5","version_comment":"Minor update.","3":"Minor update.","package":"relaxedgreen.vim","4":"relaxedgreen.vim","src_id":"3860","5":"3860","creation_date":"1108277436","6":"1108277436"},{"0":"791","vim_version":"6.0","1":"6.0","script_version":"0.4","2":"0.4","version_comment":"Minor update.","3":"Minor update.","package":"relaxedgreen.vim","4":"relaxedgreen.vim","src_id":"3855","5":"3855","creation_date":"1108146578","6":"1108146578"},{"0":"791","vim_version":"6.0","1":"6.0","script_version":"0.3","2":"0.3","version_comment":"Minor update.","3":"Minor update.","package":"relaxedgreen.vim","4":"relaxedgreen.vim","src_id":"3810","5":"3810","creation_date":"1106932338","6":"1106932338"},{"0":"791","vim_version":"6.0","1":"6.0","script_version":"0.2","2":"0.2","version_comment":"Small adjustments.","3":"Small adjustments.","package":"relaxedgreen.vim","4":"relaxedgreen.vim","src_id":"2976","5":"2976","creation_date":"1082879912","6":"1082879912"},{"0":"791","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"relaxedgreen.vim","4":"relaxedgreen.vim","src_id":"2394","5":"2394","creation_date":"1066057731","6":"1066057731"}]},"790":{"script_id":"790","0":"790","script_name":"python.vim","1":"python.vim","script_type":"syntax","2":"syntax","summary":"Enhanced version of the python syntax highlighting script","3":"Enhanced version of the python syntax highlighting script","description":"Enhanced version of the original (from vim6.1) python.vim for Python programming language.\r\n\r\nThe changes since the original python.vim are:\r\n\r\n- added support for Python 3 syntax highlighting\r\n- added :Python2Syntax and :Python3Syntax commands which allow to\r\n  switch between Python 2 and Python 3 syntaxes respectively without\r\n  reloads\/restarts\r\n- changed strings highlighting;\r\n- enhanced special symbols highlighting inside strings;\r\n- enhanced numbers highlighting;\r\n- added optional highlighting for %-formatting inside strings;\r\n- added highlighting for some error conditions (wrong symbols in source file,\r\n  mixing spaces and tabs, wrong number values,\r\n  wrong %-formatting inside strings);\r\n- added highlighting for magic comments: source code encoding\r\n  and #! (executable) strings;\r\n- added highlighting for new exceptions and builtins introduced in python 2.3, 2.4 and 2.5;\r\n- added highlighting for doctests;\r\n- added highlighting for new @decorator syntax introduced in Python 2.4a2;\r\n- added highlighting for trailing-space errors (triggered by new\r\n  option: python_highlight_space_errors);\r\n- added highlighting for variable name errors;\r\n- added highlighting for hex number errors;\r\n\r\nCheck the comments in the python.vim header for details how to report bugs and feature requests.","4":"Enhanced version of the original (from vim6.1) python.vim for Python programming language.\r\n\r\nThe changes since the original python.vim are:\r\n\r\n- added support for Python 3 syntax highlighting\r\n- added :Python2Syntax and :Python3Syntax commands which allow to\r\n  switch between Python 2 and Python 3 syntaxes respectively without\r\n  reloads\/restarts\r\n- changed strings highlighting;\r\n- enhanced special symbols highlighting inside strings;\r\n- enhanced numbers highlighting;\r\n- added optional highlighting for %-formatting inside strings;\r\n- added highlighting for some error conditions (wrong symbols in source file,\r\n  mixing spaces and tabs, wrong number values,\r\n  wrong %-formatting inside strings);\r\n- added highlighting for magic comments: source code encoding\r\n  and #! (executable) strings;\r\n- added highlighting for new exceptions and builtins introduced in python 2.3, 2.4 and 2.5;\r\n- added highlighting for doctests;\r\n- added highlighting for new @decorator syntax introduced in Python 2.4a2;\r\n- added highlighting for trailing-space errors (triggered by new\r\n  option: python_highlight_space_errors);\r\n- added highlighting for variable name errors;\r\n- added highlighting for hex number errors;\r\n\r\nCheck the comments in the python.vim header for details how to report bugs and feature requests.","install_details":"Place python.vim file in ~\/.vim\/syntax\/ folder.\r\n\r\nCheck the comments in the python.vim header for additional options.","5":"Place python.vim file in ~\/.vim\/syntax\/ folder.\r\n\r\nCheck the comments in the python.vim header for additional options.","first_name":"Dmitry","6":"Dmitry","last_name":"Vasiliev","7":"Vasiliev","releases":[{"0":"790","vim_version":"7.0","1":"7.0","script_version":"3.3.6","2":"3.3.6","version_comment":"- Highlight 'yield from' statement introduced in Python 3.3. Reported by Elizabeth Myers.\r\n","3":"- Highlight 'yield from' statement introduced in Python 3.3. Reported by Elizabeth Myers.\r\n","package":"python.vim","4":"python.vim","src_id":"21056","5":"21056","creation_date":"1384806905","6":"1384806905"},{"0":"790","vim_version":"7.0","1":"7.0","script_version":"3.3.5","2":"3.3.5","version_comment":"- Highlight 'import', 'from' and 'as' as include statements.\r\n  Patch by pydave at GitHub.\r\n- Added new option 'python_highlight_file_headers_as_comments' (disabled by\r\n  default) to highlight shebang and coding file headers as comments.\r\n  Proposed by pydave at GitHub.","3":"- Highlight 'import', 'from' and 'as' as include statements.\r\n  Patch by pydave at GitHub.\r\n- Added new option 'python_highlight_file_headers_as_comments' (disabled by\r\n  default) to highlight shebang and coding file headers as comments.\r\n  Proposed by pydave at GitHub.","package":"python.vim","4":"python.vim","src_id":"20737","5":"20737","creation_date":"1377952783","6":"1377952783"},{"0":"790","vim_version":"7.0","1":"7.0","script_version":"3.3.4","2":"3.3.4","version_comment":"Highlight True and False as booleans. Patch by Yuri Habrusiev.","3":"Highlight True and False as booleans. Patch by Yuri Habrusiev.","package":"python.vim","4":"python.vim","src_id":"20632","5":"20632","creation_date":"1376235035","6":"1376235035"},{"0":"790","vim_version":"7.0","1":"7.0","script_version":"3.3.3","2":"3.3.3","version_comment":"More lightweight syntax reloading. Patch by Will Gray.","3":"More lightweight syntax reloading. Patch by Will Gray.","package":"python.vim","4":"python.vim","src_id":"20262","5":"20262","creation_date":"1370174592","6":"1370174592"},{"0":"790","vim_version":"7.0","1":"7.0","script_version":"3.3.2","2":"3.3.2","version_comment":"Fixed behavior of b:python_version_2 variable. Reported by Will Gray.","3":"Fixed behavior of b:python_version_2 variable. Reported by Will Gray.","package":"python.vim","4":"python.vim","src_id":"20259","5":"20259","creation_date":"1370100193","6":"1370100193"},{"0":"790","vim_version":"7.0","1":"7.0","script_version":"3.3.1","2":"3.3.1","version_comment":"Script was moved to its own repository: https:\/\/github.com\/hdima\/python-syntax","3":"Script was moved to its own repository: https:\/\/github.com\/hdima\/python-syntax","package":"python.vim","4":"python.vim","src_id":"20103","5":"20103","creation_date":"1368390084","6":"1368390084"},{"0":"790","vim_version":"7.0","1":"7.0","script_version":"3.3.0","2":"3.3.0","version_comment":"Merge Python 2 and Python 3 script versions into the single python.vim script.\r\n\r\nSee the comments in the script header for details how to switch between highlighting for Python 2 and Python 3.","3":"Merge Python 2 and Python 3 script versions into the single python.vim script.\r\n\r\nSee the comments in the script header for details how to switch between highlighting for Python 2 and Python 3.","package":"python.vim","4":"python.vim","src_id":"19619","5":"19619","creation_date":"1362931298","6":"1362931298"},{"0":"790","vim_version":"7.0","1":"7.0","script_version":"3.0.7","2":"3.0.7","version_comment":"Updated email and URL","3":"Updated email and URL","package":"python3.0.vim","4":"python3.0.vim","src_id":"17430","5":"17430","creation_date":"1328972272","6":"1328972272"},{"0":"790","vim_version":"7.0","1":"7.0","script_version":"2.6.7","2":"2.6.7","version_comment":"Updated email and URL","3":"Updated email and URL","package":"python.vim","4":"python.vim","src_id":"17429","5":"17429","creation_date":"1328972235","6":"1328972235"},{"0":"790","vim_version":"7.0","1":"7.0","script_version":"3.0.6","2":"3.0.6","version_comment":"- Fixed highlighting for str.format syntax. Patch by Anton Butanaev.","3":"- Fixed highlighting for str.format syntax. Patch by Anton Butanaev.","package":"python3.0.vim","4":"python3.0.vim","src_id":"14268","5":"14268","creation_date":"1289827878","6":"1289827878"},{"0":"790","vim_version":"7.0","1":"7.0","script_version":"3.0.5","2":"3.0.5","version_comment":"- Fixed bytes escapes highlighting. Patch by Anton Butanaev.\r\n- Fixed highlighting for erroneous numbers.\r\n","3":"- Fixed bytes escapes highlighting. Patch by Anton Butanaev.\r\n- Fixed highlighting for erroneous numbers.\r\n","package":"python3.0.vim","4":"python3.0.vim","src_id":"14240","5":"14240","creation_date":"1289557217","6":"1289557217"},{"0":"790","vim_version":"7.0","1":"7.0","script_version":"3.0.4","2":"3.0.4","version_comment":"- Applied patch by Anton Butanaev which fixes highlighting for raw bytes literals","3":"- Applied patch by Anton Butanaev which fixes highlighting for raw bytes literals","package":"python3.0.vim","4":"python3.0.vim","src_id":"14216","5":"14216","creation_date":"1289322479","6":"1289322479"},{"0":"790","vim_version":"7.0","1":"7.0","script_version":"3.0.3","2":"3.0.3","version_comment":"- Applied patch by Andrea Riciputi with new configuration options \"python_highlight_builtin_objs\" and \"python_highlight_builtin_funcs\"","3":"- Applied patch by Andrea Riciputi with new configuration options \"python_highlight_builtin_objs\" and \"python_highlight_builtin_funcs\"","package":"python3.0.vim","4":"python3.0.vim","src_id":"12805","5":"12805","creation_date":"1270837564","6":"1270837564"},{"0":"790","vim_version":"7.0","1":"7.0","script_version":"2.6.6","2":"2.6.6","version_comment":"- Applied patch by Andrea Riciputi with new configuration options \"python_highlight_builtin_objs\" and \"python_highlight_builtin_funcs\"","3":"- Applied patch by Andrea Riciputi with new configuration options \"python_highlight_builtin_objs\" and \"python_highlight_builtin_funcs\"","package":"python.vim","4":"python.vim","src_id":"12804","5":"12804","creation_date":"1270837466","6":"1270837466"},{"0":"790","vim_version":"7.0","1":"7.0","script_version":"3.0.2","2":"3.0.2","version_comment":"- Applied patch by Caleb Adamantine which fixes highlighting for decorators","3":"- Applied patch by Caleb Adamantine which fixes highlighting for decorators","package":"python3.0.vim","4":"python3.0.vim","src_id":"11057","5":"11057","creation_date":"1248426796","6":"1248426796"},{"0":"790","vim_version":"7.0","1":"7.0","script_version":"2.6.5","2":"2.6.5","version_comment":"- Applied patch by Caleb Adamantine which fixes highlighting for decorators","3":"- Applied patch by Caleb Adamantine which fixes highlighting for decorators","package":"python.vim","4":"python.vim","src_id":"11056","5":"11056","creation_date":"1248426730","6":"1248426730"},{"0":"790","vim_version":"6.0","1":"6.0","script_version":"3.0.1","2":"3.0.1","version_comment":"- Fixed compatibility with pyrex.vim","3":"- Fixed compatibility with pyrex.vim","package":"python3.0.vim","4":"python3.0.vim","src_id":"10509","5":"10509","creation_date":"1241364410","6":"1241364410"},{"0":"790","vim_version":"6.0","1":"6.0","script_version":"2.6.4","2":"2.6.4","version_comment":"- Fixed compatibility with pyrex.vim","3":"- Fixed compatibility with pyrex.vim","package":"python.vim","4":"python.vim","src_id":"10508","5":"10508","creation_date":"1241364382","6":"1241364382"},{"0":"790","vim_version":"6.0","1":"6.0","script_version":"3.0.0","2":"3.0.0","version_comment":"*Warning: For Python 3.0 only!*\r\n\r\n- Added support for non-ASCII identifiers;\r\n- Added support for new text strings and binary data (bytes);\r\n- Updated support for numeric literals;\r\n- Updated support for str.format;\r\n- Added new builtins introduced in Python 2.6: \"ascii\", \"exec\", \"memoryview\", \"print\";\r\n- Added new keyword \"nonlocal\";\r\n- Removed exception \"StandardError\";\r\n- Removed builtins: \"apply\", \"basestring\", \"buffer\", \"callable\", \"coerce\", \"execfile\", \"file\", \"help\", \"intern\", \"long\", \"raw_input\", \"reduce\", \"reload\", \"unichr\", \"unicode\", \"xrange\";","3":"*Warning: For Python 3.0 only!*\r\n\r\n- Added support for non-ASCII identifiers;\r\n- Added support for new text strings and binary data (bytes);\r\n- Updated support for numeric literals;\r\n- Updated support for str.format;\r\n- Added new builtins introduced in Python 2.6: \"ascii\", \"exec\", \"memoryview\", \"print\";\r\n- Added new keyword \"nonlocal\";\r\n- Removed exception \"StandardError\";\r\n- Removed builtins: \"apply\", \"basestring\", \"buffer\", \"callable\", \"coerce\", \"execfile\", \"file\", \"help\", \"intern\", \"long\", \"raw_input\", \"reduce\", \"reload\", \"unichr\", \"unicode\", \"xrange\";","package":"python3.0.vim","4":"python3.0.vim","src_id":"9627","5":"9627","creation_date":"1228666628","6":"1228666628"},{"0":"790","vim_version":"6.0","1":"6.0","script_version":"2.6.3","2":"2.6.3","version_comment":"- Return back trailing 'L' support for numbers. Actually it was changed for future Python 3.0 syntax but in wrong file;","3":"- Return back trailing 'L' support for numbers. Actually it was changed for future Python 3.0 syntax but in wrong file;","package":"python.vim","4":"python.vim","src_id":"9293","5":"9293","creation_date":"1222693048","6":"1222693048"},{"0":"790","vim_version":"6.0","1":"6.0","script_version":"2.6.2","2":"2.6.2","version_comment":"- Added \"VMSError\" exception;\r\n- Added support for b\"...\" syntax;\r\n- Added support for str.format brace escaping;","3":"- Added \"VMSError\" exception;\r\n- Added support for b\"...\" syntax;\r\n- Added support for str.format brace escaping;","package":"python.vim","4":"python.vim","src_id":"9271","5":"9271","creation_date":"1222111552","6":"1222111552"},{"0":"790","vim_version":"6.0","1":"6.0","script_version":"2.6.1","2":"2.6.1","version_comment":"First Python 2.6 compatible release. Changes:\r\n\r\n- Added new builtins and exceptions introduced in Python 2.6: \"bin\", \"bytearray\", \"bytes\", \"format\", \"next\", \"BufferError\", \"BytesWarning\";\r\n- Added builtin \"__debug__\";\r\n- Added global variables: \"__doc__\", \"__file__\", \"__name__\", \"__package__\";\r\n- Removed \"OverflowWarning\" (removed in Python 2.5);\r\n- Added option \"python_print_as_function\" for highlight \"print\" as a function;\r\n- Added support for new integer literal syntax \"0o\" and \"0b\";\r\n- Added support for string.Template syntax controlled by \"python_highlight_string_templates\" option;\r\n- Added support for str.format syntax controlled by \"python_highlight_string_format\" option;\r\n- Removed highlighting for \"--\" and \"++\" because it is a valid Python expressions which can be interpreted as \"a + +b\";","3":"First Python 2.6 compatible release. Changes:\r\n\r\n- Added new builtins and exceptions introduced in Python 2.6: \"bin\", \"bytearray\", \"bytes\", \"format\", \"next\", \"BufferError\", \"BytesWarning\";\r\n- Added builtin \"__debug__\";\r\n- Added global variables: \"__doc__\", \"__file__\", \"__name__\", \"__package__\";\r\n- Removed \"OverflowWarning\" (removed in Python 2.5);\r\n- Added option \"python_print_as_function\" for highlight \"print\" as a function;\r\n- Added support for new integer literal syntax \"0o\" and \"0b\";\r\n- Added support for string.Template syntax controlled by \"python_highlight_string_templates\" option;\r\n- Added support for str.format syntax controlled by \"python_highlight_string_format\" option;\r\n- Removed highlighting for \"--\" and \"++\" because it is a valid Python expressions which can be interpreted as \"a + +b\";","package":"python.vim","4":"python.vim","src_id":"9262","5":"9262","creation_date":"1222021448","6":"1222021448"},{"0":"790","vim_version":"6.0","1":"6.0","script_version":"2.5.6","2":"2.5.6","version_comment":"- Applied patch by Pedro Algarvio to enable spell checking only for\r\n  the right spots (strings and comments);\r\n","3":"- Applied patch by Pedro Algarvio to enable spell checking only for\r\n  the right spots (strings and comments);\r\n","package":"python.vim","4":"python.vim","src_id":"6716","5":"6716","creation_date":"1170568285","6":"1170568285"},{"0":"790","vim_version":"7.0","1":"7.0","script_version":"2.5.5","2":"2.5.5","version_comment":"- added new warnings (ImportWarning, UnicodeWarning) introduced in Python 2.5;","3":"- added new warnings (ImportWarning, UnicodeWarning) introduced in Python 2.5;","package":"python.vim","4":"python.vim","src_id":"6230","5":"6230","creation_date":"1159247964","6":"1159247964"},{"0":"790","vim_version":"6.0","1":"6.0","script_version":"2.5.4","2":"2.5.4","version_comment":"- added highlighting for erroneous operators: &&, ||, ++, --, ===\r\n  (inspired by http:\/\/www.vim.org\/tips\/tip.php?tip_id=969, thanks\r\n  Jeroen Ruigrok van der Werven for the link);\r\n- added highlighting for new 'with' statement and 'BaseException',\r\n  'GeneratorExit' exceptions introduced in Python 2.5;\r\n- added highlighting for 'OverflowWarning' exception which had been\r\n  forgotten;\r\n- returned more robust recognition for function names;","3":"- added highlighting for erroneous operators: &&, ||, ++, --, ===\r\n  (inspired by http:\/\/www.vim.org\/tips\/tip.php?tip_id=969, thanks\r\n  Jeroen Ruigrok van der Werven for the link);\r\n- added highlighting for new 'with' statement and 'BaseException',\r\n  'GeneratorExit' exceptions introduced in Python 2.5;\r\n- added highlighting for 'OverflowWarning' exception which had been\r\n  forgotten;\r\n- returned more robust recognition for function names;","package":"python.vim","4":"python.vim","src_id":"5677","5":"5677","creation_date":"1147318305","6":"1147318305"},{"0":"790","vim_version":"6.0","1":"6.0","script_version":"2.5.3","2":"2.5.3","version_comment":"- fixed %-formatting highlighting for raw unicode strings;","3":"- fixed %-formatting highlighting for raw unicode strings;","package":"python.vim","4":"python.vim","src_id":"5373","5":"5373","creation_date":"1141614484","6":"1141614484"},{"0":"790","vim_version":"6.0","1":"6.0","script_version":"2.5.2","2":"2.5.2","version_comment":"- slightly simplified option handling;\r\n- fixed regexp for indentation errors;\r\n- fixed highlighting for backslashed symbols inside strings;\r\n- added highlighting for trailing-space errors (triggered by new\r\n  option: python_highlight_space_errors);\r\n- added highlighting for variable name errors;\r\n- added highlighting for hex number errors;","3":"- slightly simplified option handling;\r\n- fixed regexp for indentation errors;\r\n- fixed highlighting for backslashed symbols inside strings;\r\n- added highlighting for trailing-space errors (triggered by new\r\n  option: python_highlight_space_errors);\r\n- added highlighting for variable name errors;\r\n- added highlighting for hex number errors;","package":"python.vim","4":"python.vim","src_id":"4998","5":"4998","creation_date":"1137979915","6":"1137979915"},{"0":"790","vim_version":"6.0","1":"6.0","script_version":"2.5.1","2":"2.5.1","version_comment":"- added new builtins 'all' and 'any' (Python 2.5a0)","3":"- added new builtins 'all' and 'any' (Python 2.5a0)","package":"python.vim","4":"python.vim","src_id":"4009","5":"4009","creation_date":"1110688591","6":"1110688591"},{"0":"790","vim_version":"6.0","1":"6.0","script_version":"2.4.2","2":"2.4.2","version_comment":"- added highlighting for new @decorator syntax introduced in Python 2.4a2","3":"- added highlighting for new @decorator syntax introduced in Python 2.4a2","package":"python.vim","4":"python.vim","src_id":"3303","5":"3303","creation_date":"1091687144","6":"1091687144"},{"0":"790","vim_version":"6.0","1":"6.0","script_version":"2.4.1","2":"2.4.1","version_comment":"- new versioning scheme (based on python version numbers);\r\n- added highlighting for new types\/builtins introduced in python 2.4\r\n   (set, frozenset, reversed, sorted);\r\n- new option added: python_slow_sync (set this for slow but more\r\n  robust syntax synchronization);\r\n- added highlighting for doctests;","3":"- new versioning scheme (based on python version numbers);\r\n- added highlighting for new types\/builtins introduced in python 2.4\r\n   (set, frozenset, reversed, sorted);\r\n- new option added: python_slow_sync (set this for slow but more\r\n  robust syntax synchronization);\r\n- added highlighting for doctests;","package":"python.vim","4":"python.vim","src_id":"2840","5":"2840","creation_date":"1079503647","6":"1079503647"},{"0":"790","vim_version":"6.0","1":"6.0","script_version":"1.19","2":"1.19","version_comment":"- new option added: python_highlight_indent_errors;\r\n- python_highlight_all now not override previously\r\n  set options, for example code\r\n      let python_highlight_indent_errors = 0\r\n      let python_highlight_all = 1\r\n  set all highlight options except indentation\r\n  errors highlighting option;","3":"- new option added: python_highlight_indent_errors;\r\n- python_highlight_all now not override previously\r\n  set options, for example code\r\n      let python_highlight_indent_errors = 0\r\n      let python_highlight_all = 1\r\n  set all highlight options except indentation\r\n  errors highlighting option;","package":"python.vim","4":"python.vim","src_id":"2410","5":"2410","creation_date":"1066369484","6":"1066369484"},{"0":"790","vim_version":"6.0","1":"6.0","script_version":"1.17","2":"1.17","version_comment":"Initial upload","3":"Initial upload","package":"python.vim","4":"python.vim","src_id":"2392","5":"2392","creation_date":"1066006473","6":"1066006473"}]},"789":{"script_id":"789","0":"789","script_name":"set_utf8.vim","1":"set_utf8.vim","script_type":"utility","2":"utility","summary":"Switching to Unicode in an orderly manner","3":"Switching to Unicode in an orderly manner","description":"This script endeavours to set the various options required to allow (g)vim to process Unicode files properly, without, for instance, messing up keyboard input.","4":"This script endeavours to set the various options required to allow (g)vim to process Unicode files properly, without, for instance, messing up keyboard input.","install_details":"Installation:\r\n1) Copy this script to your \"user scripts\" direcory,\r\n   i.e.: (direectory names below as required by the corresponding shell)\r\n\to for Unix (with sh or similar):\r\n\t  $HOME\/.vim\/scripts\r\n\r\n\to for Windows (with COMMAND.COM, CMD.EXE or similar)\r\n\t  - if you have a HOME directory\r\n\t    %HOME%\\vimfiles\\scripts\r\n\r\n\t  - if you don't; but have a VIM directory\r\n\t    %VIM%\\vimfiles\\scriprs\r\n\r\n\t  - otherwise, it will usually be something similar to one of the\r\n\t    following, depending on where you installed Vim (take your pick):\r\n\t    C:\\VIM\\vimfiles\\scripts\r\n\t    \"C:Program Files\\VIM\\vimfiles\\scripts\"\r\n\t    C:\\PROGRA~1\\VIM\\vimfiles\\scripts\r\n\t    C:\\vimfiles\\scripts\r\n\r\n 2) Open the script in a text editor such as Vim.\r\n There are two settings at the end which you might want to comment away.\r\n\r\n\r\nHow to use it: simply add the following line to your vimrc, if and when you\r\nwant to switch over to UTF-8 processing:\r\n\r\n \truntime scripts\/set_utf8.vim\r\n","5":"Installation:\r\n1) Copy this script to your \"user scripts\" direcory,\r\n   i.e.: (direectory names below as required by the corresponding shell)\r\n\to for Unix (with sh or similar):\r\n\t  $HOME\/.vim\/scripts\r\n\r\n\to for Windows (with COMMAND.COM, CMD.EXE or similar)\r\n\t  - if you have a HOME directory\r\n\t    %HOME%\\vimfiles\\scripts\r\n\r\n\t  - if you don't; but have a VIM directory\r\n\t    %VIM%\\vimfiles\\scriprs\r\n\r\n\t  - otherwise, it will usually be something similar to one of the\r\n\t    following, depending on where you installed Vim (take your pick):\r\n\t    C:\\VIM\\vimfiles\\scripts\r\n\t    \"C:Program Files\\VIM\\vimfiles\\scripts\"\r\n\t    C:\\PROGRA~1\\VIM\\vimfiles\\scripts\r\n\t    C:\\vimfiles\\scripts\r\n\r\n 2) Open the script in a text editor such as Vim.\r\n There are two settings at the end which you might want to comment away.\r\n\r\n\r\nHow to use it: simply add the following line to your vimrc, if and when you\r\nwant to switch over to UTF-8 processing:\r\n\r\n \truntime scripts\/set_utf8.vim\r\n","first_name":"Antoine","6":"Antoine","last_name":"Mechelynck","7":"Mechelynck","releases":[{"0":"789","vim_version":"6.0","1":"6.0","script_version":"1.01","2":"1.01","version_comment":"no change, except the script's ends-of-line are now in \"unix\" format for compatibility across platforms.","3":"no change, except the script's ends-of-line are now in \"unix\" format for compatibility across platforms.","package":"set_utf8.vim","4":"set_utf8.vim","src_id":"2391","5":"2391","creation_date":"1065973120","6":"1065973120"},{"0":"789","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"set_utf8.vim","4":"set_utf8.vim","src_id":"2390","5":"2390","creation_date":"1065970119","6":"1065970119"}]},"788":{"script_id":"788","0":"788","script_name":"tokens.vim","1":"tokens.vim","script_type":"utility","2":"utility","summary":"Use tokens (input()) to extend abbreviations","3":"Use tokens (input()) to extend abbreviations","description":"This is fairly rough at the moment but what it does is allow tokens within abbreviations that you will be prompted to replace. These are based on the following digraphs:\r\n\r\n<C-K>Cu    -  if you use this token you will be prompted at every occurence\r\n                    \r\n<C-K>MW  -  you will only be prompted once and every subsequent use\r\n                        of this token will be the input you entered.\r\n\r\n<C-K>TH    -  Place this where you'd like the cursor to end up.\r\n                        This is a bit buggy at the moment so any comments  \r\n                         are welcomed.\r\n\r\n<C-K><< and >>  -  If you want to provide a message as to what you're\r\n                                  replacing use these. The only stipulation is that the \r\n                                  message be exactly 15 chars including << and >>\r\n\r\n<C-K>',    -   Because this plugin uses liblist.vim, commas need to be \r\n                     entered using this digraph.\r\n\r\n                ***   Requires:  liblist.vim   ***\r\nhttp:\/\/www.vim.org\/scripts\/script.php?script_id=166\r\n\r\nThe mapping used is <leader>et\r\n\r\nReading the script probably explains things better than I'm doing here but here's a few egs. (These are all insert mode by the way)\r\nEg1\r\n     type   dic\r\n     hit <leader>et\r\n     you'll see the prompt  <<   class name  >>\r\n     type in foo and hit <CR>\r\n     the string   <div class=\"foo\">|<\/div>   will be inserted with the cursor at the pipe.\r\n(this uses the 'Cu','<<>>' and 'TH' digraphs)\r\nEg2\r\n     type hd\r\n     hit <leader>et\r\n     you'll see the prompt  <<header level?>>\r\n     type in 2 and hit <CR>\r\n     the string <h2>|<\/h2> will be inserted again with the cursor at the pipe\r\n(this uses the 'MW','<<>>' and 'TH' digraphs)    \r\n\r\nKnown issues:\r\n    For some reason you can't place the 'TH' digraph at the end of the string. It  executes once OK but then stops.\r\n\r\n\r\nAs I'm not a programmer this could more than likely do with a complete overhaul. If anybody would like to help out or make suggestions, email markwoodwardATbigpond.com. I'd appreciate some input as I think the ideas pretty impressive but my executions not ;-)\r\n     ","4":"This is fairly rough at the moment but what it does is allow tokens within abbreviations that you will be prompted to replace. These are based on the following digraphs:\r\n\r\n<C-K>Cu    -  if you use this token you will be prompted at every occurence\r\n                    \r\n<C-K>MW  -  you will only be prompted once and every subsequent use\r\n                        of this token will be the input you entered.\r\n\r\n<C-K>TH    -  Place this where you'd like the cursor to end up.\r\n                        This is a bit buggy at the moment so any comments  \r\n                         are welcomed.\r\n\r\n<C-K><< and >>  -  If you want to provide a message as to what you're\r\n                                  replacing use these. The only stipulation is that the \r\n                                  message be exactly 15 chars including << and >>\r\n\r\n<C-K>',    -   Because this plugin uses liblist.vim, commas need to be \r\n                     entered using this digraph.\r\n\r\n                ***   Requires:  liblist.vim   ***\r\nhttp:\/\/www.vim.org\/scripts\/script.php?script_id=166\r\n\r\nThe mapping used is <leader>et\r\n\r\nReading the script probably explains things better than I'm doing here but here's a few egs. (These are all insert mode by the way)\r\nEg1\r\n     type   dic\r\n     hit <leader>et\r\n     you'll see the prompt  <<   class name  >>\r\n     type in foo and hit <CR>\r\n     the string   <div class=\"foo\">|<\/div>   will be inserted with the cursor at the pipe.\r\n(this uses the 'Cu','<<>>' and 'TH' digraphs)\r\nEg2\r\n     type hd\r\n     hit <leader>et\r\n     you'll see the prompt  <<header level?>>\r\n     type in 2 and hit <CR>\r\n     the string <h2>|<\/h2> will be inserted again with the cursor at the pipe\r\n(this uses the 'MW','<<>>' and 'TH' digraphs)    \r\n\r\nKnown issues:\r\n    For some reason you can't place the 'TH' digraph at the end of the string. It  executes once OK but then stops.\r\n\r\n\r\nAs I'm not a programmer this could more than likely do with a complete overhaul. If anybody would like to help out or make suggestions, email markwoodwardATbigpond.com. I'd appreciate some input as I think the ideas pretty impressive but my executions not ;-)\r\n     ","install_details":"place in your plugins directory","5":"place in your plugins directory","first_name":"Mark","6":"Mark","last_name":"Woodward","7":"Woodward","releases":[{"0":"788","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"tokens.vim","4":"tokens.vim","src_id":"2389","5":"2389","creation_date":"1065942845","6":"1065942845"}]},"787":{"script_id":"787","0":"787","script_name":"qt2vimsyntax","1":"qt2vimsyntax","script_type":"syntax","2":"syntax","summary":"syntax definition for Trolltech Qt library (C++)","3":"syntax definition for Trolltech Qt library (C++)","description":"A perl script that creates syntax definition for Trolltech' Qt library (http:\/\/www.trolltech.com) by scanning all qt includes and gaining class names. Assumes $QTDIR environment is set; if not, \/usr\/lib\/qt is scanned. ","4":"A perl script that creates syntax definition for Trolltech' Qt library (http:\/\/www.trolltech.com) by scanning all qt includes and gaining class names. Assumes $QTDIR environment is set; if not, \/usr\/lib\/qt is scanned. ","install_details":"This is not a ready-to-install syntax file, you have to generate one with this script:\r\n.\/qt2vimsyntax > ~\/.vim\/after\/syntax\/c.vim\r\nThis will create it for your qt installation (qt header files required!) and place it in your personal vim directory.","5":"This is not a ready-to-install syntax file, you have to generate one with this script:\r\n.\/qt2vimsyntax > ~\/.vim\/after\/syntax\/c.vim\r\nThis will create it for your qt installation (qt header files required!) and place it in your personal vim directory.","first_name":"Pawel","6":"Pawel","last_name":"Stolowski","7":"Stolowski","releases":[{"0":"787","vim_version":"5.7","1":"5.7","script_version":"1.1","2":"1.1","version_comment":"Fixed small typo in regexp matching that caused many basic classes to be missed.","3":"Fixed small typo in regexp matching that caused many basic classes to be missed.","package":"qt2vimsyntax","4":"qt2vimsyntax","src_id":"2403","5":"2403","creation_date":"1066229811","6":"1066229811"},{"0":"787","vim_version":"5.7","1":"5.7","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"qt2vimsyntax","4":"qt2vimsyntax","src_id":"2385","5":"2385","creation_date":"1065842374","6":"1065842374"}]},"786":{"script_id":"786","0":"786","script_name":"delek.vim","1":"delek.vim","script_type":"color scheme","2":"color scheme","summary":"Colors good for dark and light background","3":"Colors good for dark and light background","description":"This colors work well for me using a light or a dark background.","4":"This colors work well for me using a light or a dark background.","install_details":"","5":"","first_name":"David","6":"David","last_name":"Schweikert","7":"Schweikert","releases":[{"0":"786","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"delek.vim","4":"delek.vim","src_id":"2382","5":"2382","creation_date":"1065664857","6":"1065664857"}]},"785":{"script_id":"785","0":"785","script_name":"vartabs.vim","1":"vartabs.vim","script_type":"ftplugin","2":"ftplugin","summary":"Make your TAB-Key stop at arbitrary positions","3":"Make your TAB-Key stop at arbitrary positions","description":"The usual <TAB> stops at any 'shiftwidth' position.\r\nSometimes (eg. when programming in RPG or \/370-ASM) it is useful to have arbitrary positions (eg. for \/370-ASM they are 10,16,71).\r\n\r\nThis script will give you this feature depending on the filetype.","4":"The usual <TAB> stops at any 'shiftwidth' position.\r\nSometimes (eg. when programming in RPG or \/370-ASM) it is useful to have arbitrary positions (eg. for \/370-ASM they are 10,16,71).\r\n\r\nThis script will give you this feature depending on the filetype.","install_details":"1) Copy VARTABS.VIM into your plugin-directory\r\n2) Add in the approbiate filetype-plugin the following line (numbers must be ascending!):\r\n  :call VarTab_SetStops([10,16,71]) means: <TAB> will now stop on column 10, 16, 71, <S-TAB> will do in reverse direction.","5":"1) Copy VARTABS.VIM into your plugin-directory\r\n2) Add in the approbiate filetype-plugin the following line (numbers must be ascending!):\r\n  :call VarTab_SetStops([10,16,71]) means: <TAB> will now stop on column 10, 16, 71, <S-TAB> will do in reverse direction.","first_name":"Michael","6":"Michael","last_name":"Fitz","7":"Fitz","releases":[{"0":"785","vim_version":"7.0","1":"7.0","script_version":"2.0","2":"2.0","version_comment":"Now allows Lists as argument in VarTab_SetStops (eg.: :call VarTab_SetStops[10,16,72])\r\nOld String-argument furthermore supported for backwards-compatibility.\r\nInternal logic completely switched to Lists.","3":"Now allows Lists as argument in VarTab_SetStops (eg.: :call VarTab_SetStops[10,16,72])\r\nOld String-argument furthermore supported for backwards-compatibility.\r\nInternal logic completely switched to Lists.","package":"VARTABS.VIM","4":"VARTABS.VIM","src_id":"22261","5":"22261","creation_date":"1406327347","6":"1406327347"},{"0":"785","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"VARTABS.VIM","4":"VARTABS.VIM","src_id":"2378","5":"2378","creation_date":"1065518752","6":"1065518752"}]},"784":{"script_id":"784","0":"784","script_name":"fluka.vim","1":"fluka.vim","script_type":"color scheme","2":"color scheme","summary":"Syntax highlight for FLUKA","3":"Syntax highlight for FLUKA","description":"Provides syntax highlithing for the FLUKA simulation input file.","4":"Provides syntax highlithing for the FLUKA simulation input file.","install_details":"Place the fluka.vim to the syntax directory.\r\nApply the patch patch -p1 fluka-vim.patch to allow the filetype.vim to check if the file with .inp extension is a fluka file.","5":"Place the fluka.vim to the syntax directory.\r\nApply the patch patch -p1 fluka-vim.patch to allow the filetype.vim to check if the file with .inp extension is a fluka file.","first_name":"Vasilis","6":"Vasilis","last_name":"Vlachoudis","7":"Vlachoudis","releases":[{"0":"784","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"fluka-vim.tgz","4":"fluka-vim.tgz","src_id":"2377","5":"2377","creation_date":"1065508289","6":"1065508289"}]},"783":{"script_id":"783","0":"783","script_name":"gdm.vim","1":"gdm.vim","script_type":"syntax","2":"syntax","summary":"Syntax highlighting for gdm.conf","3":"Syntax highlighting for gdm.conf","description":"Provides syntax highlighting for GNOME Display Manager (gdm) configuration file gdm.conf.","4":"Provides syntax highlighting for GNOME Display Manager (gdm) configuration file gdm.conf.","install_details":"","5":"","first_name":"David","6":"David","last_name":"Necas","7":"Necas","releases":[{"0":"783","vim_version":"5.7","1":"5.7","script_version":"20031006","2":"20031006","version_comment":"Initial upload","3":"Initial upload","package":"gdm.vim","4":"gdm.vim","src_id":"2375","5":"2375","creation_date":"1065440895","6":"1065440895"}]},"782":{"script_id":"782","0":"782","script_name":"oasis.vim","1":"oasis.vim","script_type":"syntax","2":"syntax","summary":"OASIS-CC Syntax","3":"OASIS-CC Syntax","description":"This file provides syntax definitions for OASIS-CC.\r\n\r\nNote that this syntax file only fully defines the statements commonly used in configuring the OASIS-CC database (i.e. if blocks and insert\/delete\/update commands).  The full range of CSTOL commands have not been taken into consideration by this script.","4":"This file provides syntax definitions for OASIS-CC.\r\n\r\nNote that this syntax file only fully defines the statements commonly used in configuring the OASIS-CC database (i.e. if blocks and insert\/delete\/update commands).  The full range of CSTOL commands have not been taken into consideration by this script.","install_details":"Place in your personal syntax directory (e.g. ${HOME}\/.vim\/syntax), and either add a modeline to all OASIS-CC files (\"vim:ft=oasis\") or associate an extention such as .prc with the oasis file type:\r\n\r\nif exists (\"oasis_filetypes\")\r\n    finish\r\nendif\r\naugroup filetypedetect\r\n    \" associate OASIS-CC Procedures with the oasis file type\r\n    au! BufRead,BufNewFile *.prc        setfiletype oasis\r\n    \" associate OASIS-CC Macros with the oasis file type\r\n    au! BufRead,BufNewFile *.mac        setfiletype oasis\r\naugroup end","5":"Place in your personal syntax directory (e.g. ${HOME}\/.vim\/syntax), and either add a modeline to all OASIS-CC files (\"vim:ft=oasis\") or associate an extention such as .prc with the oasis file type:\r\n\r\nif exists (\"oasis_filetypes\")\r\n    finish\r\nendif\r\naugroup filetypedetect\r\n    \" associate OASIS-CC Procedures with the oasis file type\r\n    au! BufRead,BufNewFile *.prc        setfiletype oasis\r\n    \" associate OASIS-CC Macros with the oasis file type\r\n    au! BufRead,BufNewFile *.mac        setfiletype oasis\r\naugroup end","first_name":"David","6":"David","last_name":"Morris","7":"Morris","releases":[{"0":"782","vim_version":"5.7","1":"5.7","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"oasis.vim","4":"oasis.vim","src_id":"2374","5":"2374","creation_date":"1065435856","6":"1065435856"}]},"781":{"script_id":"781","0":"781","script_name":"pyfold","1":"pyfold","script_type":"syntax","2":"syntax","summary":"Python Syntax Folding for class\/def statements only","3":"Python Syntax Folding for class\/def statements only","description":"This script acts as a syntax-file addon to the standard python.vim syntax file.  When expression folding is used, all classes and functions will be folded automatically.\r\n\r\nEach fold ends upon one of two conditions:\r\n\r\n1) A line is detected with an indent less than or equal to the previous fold beginning line (that is not in a multi-line string).\r\n\r\n2) A line with the same indent as a class or def statement is detected that contains the string \"#\\s*end\\s\\+\\<\\(class\\|def\\)\\>\".   (i.e. \"    #end class MyClass\").\r\n\r\nNote that script vimscript #515 provides a similar functionality, but includes marker folding and limited block statement folding.  This script was written to provide class and function folding only, allow \"#end \\(class\\|def\\)\" lines to end a fold and still be included in the fold, and to increase the speed creating folds in large files.","4":"This script acts as a syntax-file addon to the standard python.vim syntax file.  When expression folding is used, all classes and functions will be folded automatically.\r\n\r\nEach fold ends upon one of two conditions:\r\n\r\n1) A line is detected with an indent less than or equal to the previous fold beginning line (that is not in a multi-line string).\r\n\r\n2) A line with the same indent as a class or def statement is detected that contains the string \"#\\s*end\\s\\+\\<\\(class\\|def\\)\\>\".   (i.e. \"    #end class MyClass\").\r\n\r\nNote that script vimscript #515 provides a similar functionality, but includes marker folding and limited block statement folding.  This script was written to provide class and function folding only, allow \"#end \\(class\\|def\\)\" lines to end a fold and still be included in the fold, and to increase the speed creating folds in large files.","install_details":"To install, place python.vim in your personal vim syntax directory (e.g. ${HOME}\/.vim\/syntax).\r\n\r\nTo use the syntax folding, add either type the command \" :set foldmethod=expr \" or add the following modeline to the top or bottom of your python file:\r\n\r\n# vim6:fdm=expr","5":"To install, place python.vim in your personal vim syntax directory (e.g. ${HOME}\/.vim\/syntax).\r\n\r\nTo use the syntax folding, add either type the command \" :set foldmethod=expr \" or add the following modeline to the top or bottom of your python file:\r\n\r\n# vim6:fdm=expr","first_name":"David","6":"David","last_name":"Morris","7":"Morris","releases":[{"0":"781","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"python.vim","4":"python.vim","src_id":"2373","5":"2373","creation_date":"1065435073","6":"1065435073"}]},"780":{"script_id":"780","0":"780","script_name":"sessions.vim","1":"sessions.vim","script_type":"utility","2":"utility","summary":"named shortcuts to groups of files","3":"named shortcuts to groups of files","description":"This plugin introduces following additions to regular session management (see\r\nhelp on viminfo, mkview, mksession):\r\n- short commands for session saving, loading, clearing and merging:\r\n  :SS <name> --- save session <name>\r\n  :SL <name> --- load session <name>\r\n  :SN <name> --- clear buffer list and set new current session name.\r\n  :SS without parameter saves current session loaded with :SL or created\r\n      with SN.\r\n  :SM <name> --- merge session <name> into current one.\r\n\r\n- All sessions are stored and loaded out of specific directory named\r\n  'sessions' in &runtimepath. \r\n  Note: it is nessessary to create this directory manually before using\r\n  plugin. E.g. 'mkdir -p ~\/.vim\/sessions' will do on Unix-like systems.\r\n\r\n- Session name argument does not need to have path prefix or extension. It's\r\n  also may be completed from already saved session names.\r\n\r\n- Major difference to built-in session mechanism is that saved session by\r\n  default does not contain any mapping, window layout, line number or\r\n  unlisted buffer information whatsoever. There's just file list and current\r\n  working directory\/file. This is done intentionally, with robustness and\r\n  loading speed in mind (see help on viminfo to learn how to store file\r\n  marks across sessions). To enable old-stype session files, set variable\r\n  g:Sessions_Old_style = 1 in your .vimrc.\r\n","4":"This plugin introduces following additions to regular session management (see\r\nhelp on viminfo, mkview, mksession):\r\n- short commands for session saving, loading, clearing and merging:\r\n  :SS <name> --- save session <name>\r\n  :SL <name> --- load session <name>\r\n  :SN <name> --- clear buffer list and set new current session name.\r\n  :SS without parameter saves current session loaded with :SL or created\r\n      with SN.\r\n  :SM <name> --- merge session <name> into current one.\r\n\r\n- All sessions are stored and loaded out of specific directory named\r\n  'sessions' in &runtimepath. \r\n  Note: it is nessessary to create this directory manually before using\r\n  plugin. E.g. 'mkdir -p ~\/.vim\/sessions' will do on Unix-like systems.\r\n\r\n- Session name argument does not need to have path prefix or extension. It's\r\n  also may be completed from already saved session names.\r\n\r\n- Major difference to built-in session mechanism is that saved session by\r\n  default does not contain any mapping, window layout, line number or\r\n  unlisted buffer information whatsoever. There's just file list and current\r\n  working directory\/file. This is done intentionally, with robustness and\r\n  loading speed in mind (see help on viminfo to learn how to store file\r\n  marks across sessions). To enable old-stype session files, set variable\r\n  g:Sessions_Old_style = 1 in your .vimrc.\r\n","install_details":"Don't forget to create directory 'sessions' somewhere in &runtimepath.\r\n","5":"Don't forget to create directory 'sessions' somewhere in &runtimepath.\r\n","first_name":"Andrew","6":"Andrew","last_name":"Rodionoff","7":"Rodionoff","releases":[{"0":"780","vim_version":"6.0","1":"6.0","script_version":"0.2","2":"0.2","version_comment":"Added MRU list feature. File encodings are now stored in minisession.","3":"Added MRU list feature. File encodings are now stored in minisession.","package":"sessions.vim","4":"sessions.vim","src_id":"2384","5":"2384","creation_date":"1065705355","6":"1065705355"},{"0":"780","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"sessions.vim","4":"sessions.vim","src_id":"2369","5":"2369","creation_date":"1065274372","6":"1065274372"}]},"779":{"script_id":"779","0":"779","script_name":"php_console.vim","1":"php_console.vim","script_type":"ftplugin","2":"ftplugin","summary":"Use php console application for debug messages (for windows)","3":"Use php console application for debug messages (for windows)","description":"This is for windows.\r\n\r\nFor unix see http:\/\/vim.sourceforge.net\/scripts\/script.php?script_id=326.\r\n(But you can adapt this also for unix. Just the path-reference to the php.exe is different.)\r\n\r\nGo into your php-file and :call ParsePhpFile().\r\n\r\nWrite a mapping to automat this. E.g. \r\nmap <F5> :call ParsePhpFile()<cr>\r\nimap <F5> <esc>:call ParsePhpFile()<cr>\r\n\r\nNow you can debug your php-file without leaving vim. \r\n\r\nYou can jump to the error lines by clicking on the compiler output in the window that opens below.\r\n\r\nAfter finishing removing the errors you can open your php-file in the browser.\r\n\r\nAdvantages:\r\n* You do not rely on apache. This means:\r\n* You can open the php-files everywhere in the filesystem (also outside of htdocs).\r\n* There is no difference between the console and the browser output. (When there is no error output you see the normal html output.)\r\n* Roundtrip error checking is possible without leaving vim.\r\n","4":"This is for windows.\r\n\r\nFor unix see http:\/\/vim.sourceforge.net\/scripts\/script.php?script_id=326.\r\n(But you can adapt this also for unix. Just the path-reference to the php.exe is different.)\r\n\r\nGo into your php-file and :call ParsePhpFile().\r\n\r\nWrite a mapping to automat this. E.g. \r\nmap <F5> :call ParsePhpFile()<cr>\r\nimap <F5> <esc>:call ParsePhpFile()<cr>\r\n\r\nNow you can debug your php-file without leaving vim. \r\n\r\nYou can jump to the error lines by clicking on the compiler output in the window that opens below.\r\n\r\nAfter finishing removing the errors you can open your php-file in the browser.\r\n\r\nAdvantages:\r\n* You do not rely on apache. This means:\r\n* You can open the php-files everywhere in the filesystem (also outside of htdocs).\r\n* There is no difference between the console and the browser output. (When there is no error output you see the normal html output.)\r\n* Roundtrip error checking is possible without leaving vim.\r\n","install_details":"Put it in the ftplugin directory. \r\nTo do this you can create a \"php\" directory there and drop it into it.\r\nBut vim should also recognize it in this form \"php_XXXXXX.vim\".\r\nGo into the environment variables of windows and set a path to the php.exe.\r\nIf you do not see a complete compiler output check the errorformat.","5":"Put it in the ftplugin directory. \r\nTo do this you can create a \"php\" directory there and drop it into it.\r\nBut vim should also recognize it in this form \"php_XXXXXX.vim\".\r\nGo into the environment variables of windows and set a path to the php.exe.\r\nIf you do not see a complete compiler output check the errorformat.","first_name":"Klaus","6":"Klaus","last_name":"Horsten","7":"Horsten","releases":[{"0":"779","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Renamed file to make it get sourced from the ftplugin directory.","3":"Renamed file to make it get sourced from the ftplugin directory.","package":"php_console.vim","4":"php_console.vim","src_id":"2388","5":"2388","creation_date":"1065933175","6":"1065933175"},{"0":"779","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"PhpConsole.vim","4":"PhpConsole.vim","src_id":"2365","5":"2365","creation_date":"1065060049","6":"1065060049"}]},"778":{"script_id":"778","0":"778","script_name":"ntp.vim","1":"ntp.vim","script_type":"syntax","2":"syntax","summary":"Syntax highlighting for ntp.conf","3":"Syntax highlighting for ntp.conf","description":"Provides syntax highlighting for NTP (Network Time Protocol) daemon configuration file ntp.conf.","4":"Provides syntax highlighting for NTP (Network Time Protocol) daemon configuration file ntp.conf.","install_details":"","5":"","first_name":"David","6":"David","last_name":"Necas","7":"Necas","releases":[{"0":"778","vim_version":"5.7","1":"5.7","script_version":"20031001","2":"20031001","version_comment":"Initial upload","3":"Initial upload","package":"ntp.vim","4":"ntp.vim","src_id":"2363","5":"2363","creation_date":"1065002950","6":"1065002950"}]},"777":{"script_id":"777","0":"777","script_name":"highlight_cursor.vim","1":"highlight_cursor.vim","script_type":"ftplugin","2":"ftplugin","summary":"legacy workaround for a 486: highlights your cursor as a reverse character block","3":"legacy workaround for a 486: highlights your cursor as a reverse character block","description":"When I installed Debian on my mother's old 486, I was sad to discover that the cursor was invisible in Vim!\r\n\r\nThis workaround is useful if for some reason your cursor disappears or is missing, invisible, hidden, or intermittent.\r\n\r\nIt highlights the cursor so it appears as a reverse block.\r\n\r\nUse Ctrl-C or Ctrl-H to toggle on\/off.\r\n\r\nOnly works in buffers, not in ex mode (Vim's commandline).\r\n\r\nBy the way it was a 486 DX.  Fast!  :D","4":"When I installed Debian on my mother's old 486, I was sad to discover that the cursor was invisible in Vim!\r\n\r\nThis workaround is useful if for some reason your cursor disappears or is missing, invisible, hidden, or intermittent.\r\n\r\nIt highlights the cursor so it appears as a reverse block.\r\n\r\nUse Ctrl-C or Ctrl-H to toggle on\/off.\r\n\r\nOnly works in buffers, not in ex mode (Vim's commandline).\r\n\r\nBy the way it was a 486 DX.  Fast!  :D","install_details":"Drop it in your ~\/.vim\/plugin directory.","5":"Drop it in your ~\/.vim\/plugin directory.","first_name":"joey","6":"joey","last_name":"twiddle","7":"twiddle","releases":[{"0":"777","vim_version":"6.0","1":"6.0","script_version":"1","2":"1","version_comment":"Initial upload","3":"Initial upload","package":"highlight_cursor.vim","4":"highlight_cursor.vim","src_id":"2358","5":"2358","creation_date":"1064783467","6":"1064783467"}]},"776":{"script_id":"776","0":"776","script_name":"whereis.vim","1":"whereis.vim","script_type":"utility","2":"utility","summary":"simple whereis (Win32 Only)","3":"simple whereis (Win32 Only)","description":"Whereis is a simple mechanism looking filename in deep directory.","4":"Whereis is a simple mechanism looking filename in deep directory.","install_details":"Copy the vgrep.vim script to the .vim\/plugin directory.\r\ncommand :Whereis   \r\n               :Vwhereis  view for founded\r\nmore information in whereis.vim\r\n","5":"Copy the vgrep.vim script to the .vim\/plugin directory.\r\ncommand :Whereis   \r\n               :Vwhereis  view for founded\r\nmore information in whereis.vim\r\n","first_name":"lechee","6":"lechee","last_name":"lai","7":"lai","releases":[{"0":"776","vim_version":"6.0","1":"6.0","script_version":"1.1","2":"1.1","version_comment":"Fixed Win98 have different bare output\r\nadd syntax for .dir match your extension","3":"Fixed Win98 have different bare output\r\nadd syntax for .dir match your extension","package":"whereis11.zip","4":"whereis11.zip","src_id":"2350","5":"2350","creation_date":"1064338634","6":"1064338634"},{"0":"776","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"whereis.vim","4":"whereis.vim","src_id":"2349","5":"2349","creation_date":"1064259763","6":"1064259763"}]},"775":{"script_id":"775","0":"775","script_name":"vimcdoc","1":"vimcdoc","script_type":"utility","2":"utility","summary":"Vim online documentation Chinese version","3":"Vim online documentation Chinese version","description":"This is an effort to translate the wonderful Vim online help into \r\nChinese. The targetted Vim version is 6.4. We've already translated\r\n*all* the documents including the user manual as well as the reference\r\nmanaul.\r\n\r\nSee our web page:\r\n\r\nhttp:\/\/vimcdoc.sf.net (English)\r\nhttp:\/\/vcd.gro.clinux.org (Chinese GB)\r\n\r\nfor more detail.","4":"This is an effort to translate the wonderful Vim online help into \r\nChinese. The targetted Vim version is 6.4. We've already translated\r\n*all* the documents including the user manual as well as the reference\r\nmanaul.\r\n\r\nSee our web page:\r\n\r\nhttp:\/\/vimcdoc.sf.net (English)\r\nhttp:\/\/vcd.gro.clinux.org (Chinese GB)\r\n\r\nfor more detail.","install_details":"See INSTALL in the package. There is win32 installation program\r\navailable on our home page too.","5":"See INSTALL in the package. There is win32 installation program\r\navailable on our home page too.","first_name":"Wenzhi","6":"Wenzhi","last_name":"Liang","7":"Liang","releases":[{"0":"775","vim_version":"6.0","1":"6.0","script_version":"0.9.0","2":"0.9.0","version_comment":"This is a major milestone release! All Vim documentation are now translated and updated against Vim 6.4. This release is almost single-handedly made possible by Willis, who has only joined us for no more than a month. Everybody is encouraged to upgrade (hint: read the INSTALL file). Online HTML version will be updated shortly. \r\n\r\nPLEASE NOTE that the attached package is a dummy one as the real one is too big. Please\r\ndownload from our website.","3":"This is a major milestone release! All Vim documentation are now translated and updated against Vim 6.4. This release is almost single-handedly made possible by Willis, who has only joined us for no more than a month. Everybody is encouraged to upgrade (hint: read the INSTALL file). Online HTML version will be updated shortly. \r\n\r\nPLEASE NOTE that the attached package is a dummy one as the real one is too big. Please\r\ndownload from our website.","package":"vimcdoc-0.9.0.tar.gz","4":"vimcdoc-0.9.0.tar.gz","src_id":"5473","5":"5473","creation_date":"1142940479","6":"1142940479"},{"0":"775","vim_version":"6.0","1":"6.0","script_version":"0.8.0","2":"0.8.0","version_comment":"With four new files and many bug fixes.","3":"With four new files and many bug fixes.","package":"vimcdoc-0.8.0.tar.gz","4":"vimcdoc-0.8.0.tar.gz","src_id":"4485","5":"4485","creation_date":"1123730256","6":"1123730256"},{"0":"775","vim_version":"6.0","1":"6.0","script_version":"0.7.0","2":"0.7.0","version_comment":"Fully compatible with the new Vim 6.3.","3":"Fully compatible with the new Vim 6.3.","package":"vimcdoc-0.7.0.tar.gz","4":"vimcdoc-0.7.0.tar.gz","src_id":"3208","5":"3208","creation_date":"1089178765","6":"1089178765"},{"0":"775","vim_version":"6.0","1":"6.0","script_version":"0.6.1","2":"0.6.1","version_comment":"This is mainly a bug fix release. Quite few changes really.\r\nAlso, this would be the last vimcdoc release for Vim 6.2\r\nand below.","3":"This is mainly a bug fix release. Quite few changes really.\r\nAlso, this would be the last vimcdoc release for Vim 6.2\r\nand below.","package":"vimcdoc-0.6.1.tar.gz","4":"vimcdoc-0.6.1.tar.gz","src_id":"3087","5":"3087","creation_date":"1086091356","6":"1086091356"},{"0":"775","vim_version":"6.0","1":"6.0","script_version":"0.6.0","2":"0.6.0","version_comment":"Yet another major release from the hard working vimcdoc team! Three important pieces were finished: windows.txt, pattern.txt and quickfix.txt. Enjoy the new release and wish you a very happy new year!","3":"Yet another major release from the hard working vimcdoc team! Three important pieces were finished: windows.txt, pattern.txt and quickfix.txt. Enjoy the new release and wish you a very happy new year!","package":"vimcdoc-0.6.0.tar.gz","4":"vimcdoc-0.6.0.tar.gz","src_id":"2660","5":"2660","creation_date":"1073940595","6":"1073940595"},{"0":"775","vim_version":"6.0","1":"6.0","script_version":"0.5.0","2":"0.5.0","version_comment":"Milestone release. All user manual are reviewed and of good quality.","3":"Milestone release. All user manual are reviewed and of good quality.","package":"vimcdoc-0.5.0.tar.gz","4":"vimcdoc-0.5.0.tar.gz","src_id":"2414","5":"2414","creation_date":"1066542795","6":"1066542795"}]},"774":{"script_id":"774","0":"774","script_name":"lebrief.vim","1":"lebrief.vim","script_type":"utility","2":"utility","summary":"guide brief 3.1 user familiar with vim","3":"guide brief 3.1 user familiar with vim","description":"A basic script help brief style user familiar in vim not all command are maped. it also great for BIOS develop guys switch their editor in vim. yap I'm a BIOS porting guy. ","4":"A basic script help brief style user familiar in vim not all command are maped. it also great for BIOS develop guys switch their editor in vim. yap I'm a BIOS porting guy. ","install_details":"copy lebrief.vim to plugin directory\r\n\r\nHistory: \r\nThis script grew from an idea posted by Yegappan iakshmanan vimscript#265\r\n\r\nmore accompany script vimscript#42, vimtip#450, vimscript#521","5":"copy lebrief.vim to plugin directory\r\n\r\nHistory: \r\nThis script grew from an idea posted by Yegappan iakshmanan vimscript#265\r\n\r\nmore accompany script vimscript#42, vimtip#450, vimscript#521","first_name":"lechee","6":"lechee","last_name":"lai","7":"lai","releases":[{"0":"774","vim_version":"6.0","1":"6.0","script_version":"1.1","2":"1.1","version_comment":"Add some comment ","3":"Add some comment ","package":"leBrief.vim","4":"leBrief.vim","src_id":"2354","5":"2354","creation_date":"1064447957","6":"1064447957"},{"0":"774","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"leBrief.vim","4":"leBrief.vim","src_id":"2344","5":"2344","creation_date":"1064168562","6":"1064168562"}]},"773":{"script_id":"773","0":"773","script_name":"vgrep","1":"vgrep","script_type":"utility","2":"utility","summary":"another grep in wide look","3":"another grep in wide look","description":"vgrep.vim is working for some people have complex project with deep directory \r\n\r\nThe vgrep.vim plugin script is work another grep unlike unix grep which use different output for look, if you didn't have such grep download at http:\/\/www.interlog.com\/~tcharron\/grep.html and patch with grep20f.dif \r\n\r\nwide format via unix format  \r\n ============ Wide Output Format =================\r\n File: C:\\vim\\vim62\\plugin\\vgrep.vim             \r\n     1: File: vgrep.vim                          \r\n    17: let loaded_vgrep = 1                     \r\n File: C:\\vim\\vim62\\plugin\\testtttt1\\testtttt2\\testtttt3\\whereis.vim           \r\n     1: File: whereis.vim                        \r\n =================================================\r\n save you eye see real code \r\n ============ Unix Output ========================\r\n plugin\\vgrep.vim:1: file...\r\n plugin\\vgrep.vim:17: let...\r\n plugin\\testtttt1\\testtttt2\\testtttt2\\whereis.vim:1: file ...\r\n =================================================\r\n\r\n","4":"vgrep.vim is working for some people have complex project with deep directory \r\n\r\nThe vgrep.vim plugin script is work another grep unlike unix grep which use different output for look, if you didn't have such grep download at http:\/\/www.interlog.com\/~tcharron\/grep.html and patch with grep20f.dif \r\n\r\nwide format via unix format  \r\n ============ Wide Output Format =================\r\n File: C:\\vim\\vim62\\plugin\\vgrep.vim             \r\n     1: File: vgrep.vim                          \r\n    17: let loaded_vgrep = 1                     \r\n File: C:\\vim\\vim62\\plugin\\testtttt1\\testtttt2\\testtttt3\\whereis.vim           \r\n     1: File: whereis.vim                        \r\n =================================================\r\n save you eye see real code \r\n ============ Unix Output ========================\r\n plugin\\vgrep.vim:1: file...\r\n plugin\\vgrep.vim:17: let...\r\n plugin\\testtttt1\\testtttt2\\testtttt2\\whereis.vim:1: file ...\r\n =================================================\r\n\r\n","install_details":"Copy the vgrep.vim script to the .vim\/plugin directory.\r\nSet Vgrep_Key variable to the key you prefer to invoke\r\n\r\ndownload full version 1.1 (include gnugrep.exe and grep.dif and grp.vim)","5":"Copy the vgrep.vim script to the .vim\/plugin directory.\r\nSet Vgrep_Key variable to the key you prefer to invoke\r\n\r\ndownload full version 1.1 (include gnugrep.exe and grep.dif and grp.vim)","first_name":"lechee","6":"lechee","last_name":"lai","7":"lai","releases":[{"0":"773","vim_version":"7.0","1":"7.0","script_version":"1.4.1","2":"1.4.1","version_comment":"fix vgrep skip ansi text","3":"fix vgrep skip ansi text","package":"vim_vgrep141.tar.gz","4":"vim_vgrep141.tar.gz","src_id":"8959","5":"8959","creation_date":"1216261590","6":"1216261590"},{"0":"773","vim_version":"7.0","1":"7.0","script_version":"1.4","2":"1.4","version_comment":"upgrade to vim 7 and use vgrep instead g2w.pl source code is include","3":"upgrade to vim 7 and use vgrep instead g2w.pl source code is include","package":"vim_vgrep.tar.gz","4":"vim_vgrep.tar.gz","src_id":"8958","5":"8958","creation_date":"1216233550","6":"1216233550"},{"0":"773","vim_version":"6.0","1":"6.0","script_version":"1.3","2":"1.3","version_comment":"Add unix grep support via g2w.pl (included)","3":"Add unix grep support via g2w.pl (included)","package":"vgrep13.zip","4":"vgrep13.zip","src_id":"3380","5":"3380","creation_date":"1093381276","6":"1093381276"},{"0":"773","vim_version":"6.0","1":"6.0","script_version":"1.2","2":"1.2","version_comment":"Minor Bugfix\r\n","3":"Minor Bugfix\r\n","package":"vgrep.vim","4":"vgrep.vim","src_id":"2361","5":"2361","creation_date":"1064867011","6":"1064867011"},{"0":"773","vim_version":"6.0","1":"6.0","script_version":"1.1","2":"1.1","version_comment":"some bugfix \r\nAdd TurboGrep support\r\nAdd OakGrep Support\r\n","3":"some bugfix \r\nAdd TurboGrep support\r\nAdd OakGrep Support\r\n","package":"vgrep11.zip","4":"vgrep11.zip","src_id":"2355","5":"2355","creation_date":"1064528515","6":"1064528515"},{"0":"773","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"vgrep.zip","4":"vgrep.zip","src_id":"2341","5":"2341","creation_date":"1063989236","6":"1063989236"}]},"772":{"script_id":"772","0":"772","script_name":"umber-green","1":"umber-green","script_type":"color scheme","2":"color scheme","summary":"Umber and green monochrome monitor nostalgia.","3":"Umber and green monochrome monitor nostalgia.","description":"I just grabbed the colorscheme_template and tried to satisfy my nostalgia for old green and  umber-toned monochrome monitors with a nice contrast in both low-light and (less so) bright environments.  Just a few colours, highlighting only the most important stuff. Works nicely so far for editing .c files on with my CRT using a gvim. I'll have to work on it yet (i.e. making it work in a console), so if you have comments, wishes or recommendations...","4":"I just grabbed the colorscheme_template and tried to satisfy my nostalgia for old green and  umber-toned monochrome monitors with a nice contrast in both low-light and (less so) bright environments.  Just a few colours, highlighting only the most important stuff. Works nicely so far for editing .c files on with my CRT using a gvim. I'll have to work on it yet (i.e. making it work in a console), so if you have comments, wishes or recommendations...","install_details":"Put along with your other colourscheme scripts ( $VIM\/colors or ~\/.vim\/colors ) and type :colo umber-green. Put \"colo umber-green\" in your .vimrc to make it default.","5":"Put along with your other colourscheme scripts ( $VIM\/colors or ~\/.vim\/colors ) and type :colo umber-green. Put \"colo umber-green\" in your .vimrc to make it default.","first_name":"Horror","6":"Horror","last_name":"Vacui","7":"Vacui","releases":[{"0":"772","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"umber-green.vim","4":"umber-green.vim","src_id":"2338","5":"2338","creation_date":"1063724986","6":"1063724986"}]},"771":{"script_id":"771","0":"771","script_name":"ocamlhelp.vim","1":"ocamlhelp.vim","script_type":"utility","2":"utility","summary":"Text-help reader for Objective Caml with hypertext (kinda) and syntax h\/l","3":"Text-help reader for Objective Caml with hypertext (kinda) and syntax h\/l","description":"Objective Caml txt-format reference manual reader, with syntax coloring of\r\nexamples. :edit ocaml-<current version>-refman.txt, press <Enter> on\r\nhighlighted section numbers to jump.\r\n","4":"Objective Caml txt-format reference manual reader, with syntax coloring of\r\nexamples. :edit ocaml-<current version>-refman.txt, press <Enter> on\r\nhighlighted section numbers to jump.\r\n","install_details":"","5":"","first_name":"Andrew","6":"Andrew","last_name":"Rodionoff","7":"Rodionoff","releases":[{"0":"771","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"ocamlhelp.vim","4":"ocamlhelp.vim","src_id":"2329","5":"2329","creation_date":"1063373242","6":"1063373242"}]},"770":{"script_id":"770","0":"770","script_name":"Source Control","1":"Source Control","script_type":"utility","2":"utility","summary":"Common interface to source-control","3":"Common interface to source-control","description":"This is designed to be a generic source-control solution.  It handles multiple different\r\nrepository types at once.\r\n\r\nCurrently, there are integrations for Visual Source Safe and StarTeam (only tested under win32).\r\n\r\nIt is designed to be easily extensible, with different source-control modules being loaded on demand.\r\n\r\nThere is some documentation, including how to create source-control modules.\r\n","4":"This is designed to be a generic source-control solution.  It handles multiple different\r\nrepository types at once.\r\n\r\nCurrently, there are integrations for Visual Source Safe and StarTeam (only tested under win32).\r\n\r\nIt is designed to be easily extensible, with different source-control modules being loaded on demand.\r\n\r\nThere is some documentation, including how to create source-control modules.\r\n","install_details":"Unzip into   .vim\/  or vimfiles\/\r\n\r\nDon't forget to run :helptags ~\/vimfiles\/doc\r\n\r\n","5":"Unzip into   .vim\/  or vimfiles\/\r\n\r\nDon't forget to run :helptags ~\/vimfiles\/doc\r\n\r\n","first_name":"Michael","6":"Michael","last_name":"Geddes","7":"Geddes","releases":[{"0":"770","vim_version":"6.0","1":"6.0","script_version":"2.4","2":"2.4","version_comment":"General:\r\n  Update file status when doing \\ss\r\n  Make sure status is updated (For starteam)\r\nStarTeam:\r\n Auto-Update status when checking out an 'Unknown' file.\r\n Preserve file status\r\n\r\n","3":"General:\r\n  Update file status when doing \\ss\r\n  Make sure status is updated (For starteam)\r\nStarTeam:\r\n Auto-Update status when checking out an 'Unknown' file.\r\n Preserve file status\r\n\r\n","package":"srcctl.zip","4":"srcctl.zip","src_id":"2447","5":"2447","creation_date":"1067962918","6":"1067962918"},{"0":"770","vim_version":"6.0","1":"6.0","script_version":"2.3","2":"2.3","version_comment":"Broke some stuff - now fixed","3":"Broke some stuff - now fixed","package":"srcctl.zip","4":"srcctl.zip","src_id":"2327","5":"2327","creation_date":"1063306071","6":"1063306071"}]},"769":{"script_id":"769","0":"769","script_name":"table.vim","1":"table.vim","script_type":"utility","2":"utility","summary":"smarter table editing\/navigation","3":"smarter table editing\/navigation","description":"In vimtip#547 I described some functions that enable easier navigation\r\nand editing of tables. I have considerably enhanced the functionality\r\nand placed all the relevant code in a script file.\r\n\r\nThe idea of the script is to automatically extract fields from a table\r\nrow and use that information to create maps that aid in editing and\r\nnavigation of the table. The user first marks a table row as table\r\nheading. The line does not literally have to be the table heading, but\r\nit should be representative of the typical row of the table in\r\nquestion.\r\n\r\nAfter this step the script maps tab and shift-tab keys to move between\r\nfields. These mappings work in both insert and normal modes. The tab\r\nmapping is especially useful in insert mode as it inserts the correct\r\namount of padding to reach the start of the next field. \r\n\r\nThe script also has an alignment feature that aligns the fields of the\r\nrow with that of the heading. Editing a pre-existing table frequently\r\nleads to misaligned rows and this feature alleviates the need to\r\nmanually add\/remove padding.\r\n\r\nFor more details about the script check the documentation in the script package. I also intend to post a tip documenting the use of the script. The tip will most likely be numbered vimtip #554","4":"In vimtip#547 I described some functions that enable easier navigation\r\nand editing of tables. I have considerably enhanced the functionality\r\nand placed all the relevant code in a script file.\r\n\r\nThe idea of the script is to automatically extract fields from a table\r\nrow and use that information to create maps that aid in editing and\r\nnavigation of the table. The user first marks a table row as table\r\nheading. The line does not literally have to be the table heading, but\r\nit should be representative of the typical row of the table in\r\nquestion.\r\n\r\nAfter this step the script maps tab and shift-tab keys to move between\r\nfields. These mappings work in both insert and normal modes. The tab\r\nmapping is especially useful in insert mode as it inserts the correct\r\namount of padding to reach the start of the next field. \r\n\r\nThe script also has an alignment feature that aligns the fields of the\r\nrow with that of the heading. Editing a pre-existing table frequently\r\nleads to misaligned rows and this feature alleviates the need to\r\nmanually add\/remove padding.\r\n\r\nFor more details about the script check the documentation in the script package. I also intend to post a tip documenting the use of the script. The tip will most likely be numbered vimtip #554","install_details":"To install the script, place table.vim in the vim macros directory \r\nand source it in your vimrc using:\r\nsource $VIMRUNTIME\/macros\/table.vim\r\n\r\nIf you simply want to check the functionality of the script, place\r\nthe script file in your current directory, open vim in the same \r\ndirectory and use \r\n:so table.vim\r\n","5":"To install the script, place table.vim in the vim macros directory \r\nand source it in your vimrc using:\r\nsource $VIMRUNTIME\/macros\/table.vim\r\n\r\nIf you simply want to check the functionality of the script, place\r\nthe script file in your current directory, open vim in the same \r\ndirectory and use \r\n:so table.vim\r\n","first_name":"usman","6":"usman","last_name":"latif","7":"latif","releases":[{"0":"769","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"table.zip","4":"table.zip","src_id":"2322","5":"2322","creation_date":"1063217425","6":"1063217425"}]},"768":{"script_id":"768","0":"768","script_name":"mis.vim","1":"mis.vim","script_type":"syntax","2":"syntax","summary":"Syntax file for Minimal Instruction Set (MIS)","3":"Syntax file for Minimal Instruction Set (MIS)","description":"This script provides syntax highlighting for the (rather obscure) MIS programming language.\r\n\r\nIt assumes the following conventions:\r\n\r\n* names of pointers to address locations end in \"_@\".. Ex. mypointer_@\r\n* names of pointers to pointers end in \"_@@\".. Ex. mypointer_@@\r\n\r\nIf these conventions are followed, the syntax will be highlighted accordingly. ","4":"This script provides syntax highlighting for the (rather obscure) MIS programming language.\r\n\r\nIt assumes the following conventions:\r\n\r\n* names of pointers to address locations end in \"_@\".. Ex. mypointer_@\r\n* names of pointers to pointers end in \"_@@\".. Ex. mypointer_@@\r\n\r\nIf these conventions are followed, the syntax will be highlighted accordingly. ","install_details":"Drop the file into your ~\/.vim\/syntax directory (create one if it doesn't exist), and add the following to your ~\/.vimrc\r\n\r\nautocmd BufRead,BufNewFile *.mis  setfiletype mis","5":"Drop the file into your ~\/.vim\/syntax directory (create one if it doesn't exist), and add the following to your ~\/.vimrc\r\n\r\nautocmd BufRead,BufNewFile *.mis  setfiletype mis","first_name":"Dennis","6":"Dennis","last_name":"Craven","7":"Craven","releases":[{"0":"768","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"mis.vim","4":"mis.vim","src_id":"2321","5":"2321","creation_date":"1063204214","6":"1063204214"}]},"767":{"script_id":"767","0":"767","script_name":"ttcn-dict","1":"ttcn-dict","script_type":"utility","2":"utility","summary":"TTCN-3 dictionary (keyword completion) file","3":"TTCN-3 dictionary (keyword completion) file","description":"This package provides keyword completion for TTCN-3.\r\n\r\nIn insert mode you hit ctrl-x ctrl-k to get suggestions of keywords that could complete the currently typed word.\r\n\r\nNote: ctrl-x ctrl-k is the Vim built-in method for dictionary completion; check out vimtip #91 and vimtip #102 for cool stuff and adjustments you can make!\r\n","4":"This package provides keyword completion for TTCN-3.\r\n\r\nIn insert mode you hit ctrl-x ctrl-k to get suggestions of keywords that could complete the currently typed word.\r\n\r\nNote: ctrl-x ctrl-k is the Vim built-in method for dictionary completion; check out vimtip #91 and vimtip #102 for cool stuff and adjustments you can make!\r\n","install_details":"1. Drop the file in some directory (e.g. ~\/.vim\/dicts).\r\n2. Download the TTCN ftplugin (vimscript #793).\r\n3. If necessary, adjust the path to the dict file in the ftplugin.","5":"1. Drop the file in some directory (e.g. ~\/.vim\/dicts).\r\n2. Download the TTCN ftplugin (vimscript #793).\r\n3. If necessary, adjust the path to the dict file in the ftplugin.","first_name":"Stefan","6":"Stefan","last_name":"Karlsson","7":"Karlsson","releases":[{"0":"767","vim_version":"6.0","1":"6.0","script_version":"0.3.1","2":"0.3.1","version_comment":"The previous version of this utility contained both the dictionary file and a ftplugin. However, I decided to split them and the ftplugin is now a separate script.","3":"The previous version of this utility contained both the dictionary file and a ftplugin. However, I decided to split them and the ftplugin is now a separate script.","package":"ttcn.dict","4":"ttcn.dict","src_id":"2397","5":"2397","creation_date":"1066131320","6":"1066131320"}]},"766":{"script_id":"766","0":"766","script_name":"VHDL indent","1":"VHDL indent","script_type":"indent","2":"indent","summary":"indent file for VHDL","3":"indent file for VHDL","description":"This is indent file for VHDL\r\nThe new versions are made by Janez Strangelj(jkranjski_at_email_dot_si)","4":"This is indent file for VHDL\r\nThe new versions are made by Janez Strangelj(jkranjski_at_email_dot_si)","install_details":"copy it to \/vim\/vim6x\/indent\/vhdl.vim","5":"copy it to \/vim\/vim6x\/indent\/vhdl.vim","first_name":"N.J.","6":"N.J.","last_name":"Heo","7":"Heo","releases":[{"0":"766","vim_version":"6.0","1":"6.0","script_version":"0.3","2":"0.3","version_comment":"This code is made by Janez Strangelj(jkranjski_at_email_dot_si)","3":"This code is made by Janez Strangelj(jkranjski_at_email_dot_si)","package":"vhdl.vim","4":"vhdl.vim","src_id":"2672","5":"2672","creation_date":"1074807651","6":"1074807651"},{"0":"766","vim_version":"6.0","1":"6.0","script_version":"0.2","2":"0.2","version_comment":" By Janez Stangelj","3":" By Janez Stangelj","package":"vhdl.vim","4":"vhdl.vim","src_id":"2583","5":"2583","creation_date":"1071027575","6":"1071027575"},{"0":"766","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"vhdl.vim","4":"vhdl.vim","src_id":"2315","5":"2315","creation_date":"1063013407","6":"1063013407"}]},"765":{"script_id":"765","0":"765","script_name":"gvim with tabs","1":"gvim with tabs","script_type":"utility","2":"utility","summary":"patch to add tabs to gvim","3":"patch to add tabs to gvim","description":"I'am not author this patch. I don't know his author, but I use it over year and it's great. Patch is on http:\/\/www.ascs.muni.cz\/~smrt\/vim\/ and it's for GTK gvim 6.1.\r\n\r\nTHIS PATCH IS PROBABLE LOST FOR EVERY TIME","4":"I'am not author this patch. I don't know his author, but I use it over year and it's great. Patch is on http:\/\/www.ascs.muni.cz\/~smrt\/vim\/ and it's for GTK gvim 6.1.\r\n\r\nTHIS PATCH IS PROBABLE LOST FOR EVERY TIME","install_details":"All known information is on http:\/\/www.ascs.muni.cz\/~smrt\/vim\/\r\n\r\nDon't download empty.vim, this is only upload script pacifier.","5":"All known information is on http:\/\/www.ascs.muni.cz\/~smrt\/vim\/\r\n\r\nDon't download empty.vim, this is only upload script pacifier.","first_name":"Petr","6":"Petr","last_name":"Mach","7":"Mach","releases":[{"0":"765","vim_version":"6.0","1":"6.0","script_version":"1","2":"1","version_comment":"Initial upload","3":"Initial upload","package":"empty.vim","4":"empty.vim","src_id":"2314","5":"2314","creation_date":"1063013045","6":"1063013045"}]},"764":{"script_id":"764","0":"764","script_name":"don't click","1":"don't click","script_type":"game","2":"game","summary":"this is result stupid bug in upload script","3":"this is result stupid bug in upload script","description":"I try 100x upload script, but I get error every. I tried anything, until I found bug. If version is set to 0, upload failed.","4":"I try 100x upload script, but I get error every. I tried anything, until I found bug. If version is set to 0, upload failed.","install_details":"Delete this, if you can do it.","5":"Delete this, if you can do it.","first_name":"Petr","6":"Petr","last_name":"Mach","7":"Mach","releases":[{"0":"764","vim_version":"6.0","1":"6.0","script_version":"1","2":"1","version_comment":"Initial upload","3":"Initial upload","package":"empty.vim","4":"empty.vim","src_id":"2313","5":"2313","creation_date":"1063012984","6":"1063012984"}]},"763":{"script_id":"763","0":"763","script_name":"hlcontext.vim","1":"hlcontext.vim","script_type":"utility","2":"utility","summary":"based on VIMTIP#548: Using H and L keys as context sensitive pagedown\/pageup","3":"based on VIMTIP#548: Using H and L keys as context sensitive pagedown\/pageup","description":"This is based on VIMTIP #548: Using H and L keys as context sensitive pagedown\/pageup by Usman Latif (original tip) and johann-guenter.simon's scrolloff fix\/tip\r\n\r\nAll I have done is stuff the above in a script and add <plug> and (possible) a little clean up. Original tip is included in script file.\r\n\r\nIn short this makes H and L context sensitive; If H is invoked when cursor is not at the top of the window it will be placed at the top of the window, if it is at the top of the window <pageup> and keep cursor at top of window. Same idea for L (save go down)\r\n\r\nIf you like you can remap <plug>HLContextPlug_H and <plug>HLContextPlug_L to different keys\r\n\r\nComments and whatnot welcome of course.","4":"This is based on VIMTIP #548: Using H and L keys as context sensitive pagedown\/pageup by Usman Latif (original tip) and johann-guenter.simon's scrolloff fix\/tip\r\n\r\nAll I have done is stuff the above in a script and add <plug> and (possible) a little clean up. Original tip is included in script file.\r\n\r\nIn short this makes H and L context sensitive; If H is invoked when cursor is not at the top of the window it will be placed at the top of the window, if it is at the top of the window <pageup> and keep cursor at top of window. Same idea for L (save go down)\r\n\r\nIf you like you can remap <plug>HLContextPlug_H and <plug>HLContextPlug_L to different keys\r\n\r\nComments and whatnot welcome of course.","install_details":"Drop in plugin directory, i.e. \"~\/.vim\/plugin\/\"","5":"Drop in plugin directory, i.e. \"~\/.vim\/plugin\/\"","first_name":"Robert","6":"Robert","last_name":"KellyIV","7":"KellyIV","releases":[{"0":"763","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"hlcontext.vim","4":"hlcontext.vim","src_id":"2309","5":"2309","creation_date":"1062986826","6":"1062986826"}]},"762":{"script_id":"762","0":"762","script_name":"deleted","1":"deleted","script_type":"utility","2":"utility","summary":"deleted","3":"deleted","description":"Deleted. This is the only way to delete a deprecated or bad script on vim.sourceforge.net. Please influence the holders that this get changed. Postings in the message board are so far ignored.","4":"Deleted. This is the only way to delete a deprecated or bad script on vim.sourceforge.net. Please influence the holders that this get changed. Postings in the message board are so far ignored.","install_details":"deleted","5":"deleted","first_name":"Klaus","6":"Klaus","last_name":"Horsten","7":"Horsten","releases":[{"0":"762","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"deleted","3":"deleted","package":"deleted","4":"deleted","src_id":"2411","5":"2411","creation_date":"1066430870","6":"1066430870"}]},"761":{"script_id":"761","0":"761","script_name":"lpc.vim","1":"lpc.vim","script_type":"syntax","2":"syntax","summary":"Syntax highlight for LPC","3":"Syntax highlight for LPC","description":"LPC stands for a simple, memory-efficient language: Lars Pensj| C.\r\n\r\nThis script is already coming with Vim 6.2, but the official version may not be quite up to date.\r\n\r\n","4":"LPC stands for a simple, memory-efficient language: Lars Pensj| C.\r\n\r\nThis script is already coming with Vim 6.2, but the official version may not be quite up to date.\r\n\r\n","install_details":"Put it into ~\/.vim\/syntax\/ , or $VIM\\vimfiles\\syntax\\ for Windows.\r\n\r\nLPC source cannot be automatically recognized well, if you are using Vim 6.2 or above, see   :help lpc.vim   for instructions.\r\n\r\notherwise, you are strongly recommended to upgrade to Vim 6.3.\r\n\r\n","5":"Put it into ~\/.vim\/syntax\/ , or $VIM\\vimfiles\\syntax\\ for Windows.\r\n\r\nLPC source cannot be automatically recognized well, if you are using Vim 6.2 or above, see   :help lpc.vim   for instructions.\r\n\r\notherwise, you are strongly recommended to upgrade to Vim 6.3.\r\n\r\n","first_name":"Pan","6":"Pan","last_name":"Shizhu","7":"Shizhu","releases":[{"0":"761","vim_version":"6.0","1":"6.0","script_version":"0.8","2":"0.8","version_comment":"Thanks for Sebatian, he provided highlighting for closures.","3":"Thanks for Sebatian, he provided highlighting for closures.","package":"lpc.vim","4":"lpc.vim","src_id":"3169","5":"3169","creation_date":"1087852012","6":"1087852012"},{"0":"761","vim_version":"6.0","1":"6.0","script_version":"0.7","2":"0.7","version_comment":"Initial upload","3":"Initial upload","package":"lpc.vim","4":"lpc.vim","src_id":"2300","5":"2300","creation_date":"1062693992","6":"1062693992"}]},"760":{"script_id":"760","0":"760","script_name":"peaksea","1":"peaksea","script_type":"color scheme","2":"color scheme","summary":"Refined color, contains both gui and cterm256 for dark and light background","3":"Refined color, contains both gui and cterm256 for dark and light background","description":"The peak sea color (peaksea.vim) is the new version of the well-known colorscheme ps_color.\r\n\r\nNow the color contains light-background scheme for gui and 256 color term, with dark-background scheme supporting gui and 256 and 16 color term.\r\n\r\nYou can fire any issues at http:\/\/code.google.com\/p\/peaksea\/issues\/list\r\n","4":"The peak sea color (peaksea.vim) is the new version of the well-known colorscheme ps_color.\r\n\r\nNow the color contains light-background scheme for gui and 256 color term, with dark-background scheme supporting gui and 256 and 16 color term.\r\n\r\nYou can fire any issues at http:\/\/code.google.com\/p\/peaksea\/issues\/list\r\n","install_details":"put the peaksea.vim in your $HOME\/.vim\/colors\/ (or %HOME%\\vimfiles\\colors for Windows)\r\n\r\nTo enable the scheme, you can put in ~\/.vimrc the following:\r\n\r\nif ! has(\"gui_running\")\r\n    set t_Co=256\r\nendif\r\n\" feel free to choose :set background=light for a different style\r\nset background=dark\r\ncolors peaksea\r\n\r\nThe newest version of most modern terminal emulators have 256 color support, the following has been tested:\r\nworks great: xterm, konsole 4.2+, gnome-terminal, xfce4-terminal, putty for windows, mintty for cygwin and mintty for mingw\/msys\r\nworks after some tweaks: screen (recompile and add a .screenrc, google for details.), konsole 3.x (I had provided a patch at https:\/\/bugs.kde.org\/show_bug.cgi?id=169013)\r\nworks with issue: rxvt (no 256-color by default, needs hack for 256-color support)\r\n\r\nIn case you cannot make 256-color work for your terminal, the 16-color support has no difference from the ps_color.vim, you'll need to tune color codes for 16-color to work, the instructions can be found inside the old ps_color.vim. There are predefined konsole and xfce4-terminal profile at http:\/\/code.google.com\/p\/peaksea\/source\/browse\/trunk\r\n\r\nNote: if you don't like the dark-black background and want it be pure black: simply search for the following line\r\nhi Normal guifg=#d0d0d0 guibg=#202020 gui=NONE\r\nand change #202020 into #000000.\r\n","5":"put the peaksea.vim in your $HOME\/.vim\/colors\/ (or %HOME%\\vimfiles\\colors for Windows)\r\n\r\nTo enable the scheme, you can put in ~\/.vimrc the following:\r\n\r\nif ! has(\"gui_running\")\r\n    set t_Co=256\r\nendif\r\n\" feel free to choose :set background=light for a different style\r\nset background=dark\r\ncolors peaksea\r\n\r\nThe newest version of most modern terminal emulators have 256 color support, the following has been tested:\r\nworks great: xterm, konsole 4.2+, gnome-terminal, xfce4-terminal, putty for windows, mintty for cygwin and mintty for mingw\/msys\r\nworks after some tweaks: screen (recompile and add a .screenrc, google for details.), konsole 3.x (I had provided a patch at https:\/\/bugs.kde.org\/show_bug.cgi?id=169013)\r\nworks with issue: rxvt (no 256-color by default, needs hack for 256-color support)\r\n\r\nIn case you cannot make 256-color work for your terminal, the 16-color support has no difference from the ps_color.vim, you'll need to tune color codes for 16-color to work, the instructions can be found inside the old ps_color.vim. There are predefined konsole and xfce4-terminal profile at http:\/\/code.google.com\/p\/peaksea\/source\/browse\/trunk\r\n\r\nNote: if you don't like the dark-black background and want it be pure black: simply search for the following line\r\nhi Normal guifg=#d0d0d0 guibg=#202020 gui=NONE\r\nand change #202020 into #000000.\r\n","first_name":"Pan","6":"Pan","last_name":"Shizhu","7":"Shizhu","releases":[{"0":"760","vim_version":"8.0","1":"8.0","script_version":"3.6","2":"3.6","version_comment":"Add Vim 8.0 support.","3":"Add Vim 8.0 support.","package":"peaksea.vim","4":"peaksea.vim","src_id":"24721","5":"24721","creation_date":"1478826497","6":"1478826497"},{"0":"760","vim_version":"6.0","1":"6.0","script_version":"3.5","2":"3.5","version_comment":"This version adds CursorIM support, which integrates well with vimim and other input methods.\r\n\r\nIf you use gvim and vimim, you will found it useful. Otherwise, it has no difference with the previous version.","3":"This version adds CursorIM support, which integrates well with vimim and other input methods.\r\n\r\nIf you use gvim and vimim, you will found it useful. Otherwise, it has no difference with the previous version.","package":"peaksea.vim","4":"peaksea.vim","src_id":"15675","5":"15675","creation_date":"1305774838","6":"1305774838"},{"0":"760","vim_version":"6.0","1":"6.0","script_version":"3.4","2":"3.4","version_comment":"For light-background terminal we always assume 256color support.\r\nTransparency is supported in 256color mode, search the text \"transparency\" in peaksea.vim for details.\r\n\r\n","3":"For light-background terminal we always assume 256color support.\r\nTransparency is supported in 256color mode, search the text \"transparency\" in peaksea.vim for details.\r\n\r\n","package":"peaksea.vim","4":"peaksea.vim","src_id":"12309","5":"12309","creation_date":"1265354012","6":"1265354012"},{"0":"760","vim_version":"6.0","1":"6.0","script_version":"3.3","2":"3.3","version_comment":"Anton Sharnov thinks it is better to leave the foreground color as is for spell error in 256-color cterm. If you agree this, the version 3.3 is for you, else you can just edit the source. Also, your can search for text 'transparency' within the peaksea.vim to know how to get cterm background transparency.","3":"Anton Sharnov thinks it is better to leave the foreground color as is for spell error in 256-color cterm. If you agree this, the version 3.3 is for you, else you can just edit the source. Also, your can search for text 'transparency' within the peaksea.vim to know how to get cterm background transparency.","package":"peaksea.vim","4":"peaksea.vim","src_id":"9419","5":"9419","creation_date":"1225437487","6":"1225437487"},{"0":"760","vim_version":"6.0","1":"6.0","script_version":"3.2","2":"3.2","version_comment":"This version adds 256 color term support, a good color scheme has to support 256color term.\r\nThe old ps_color got a name now: peak sea color.","3":"This version adds 256 color term support, a good color scheme has to support 256color term.\r\nThe old ps_color got a name now: peak sea color.","package":"peaksea.vim","4":"peaksea.vim","src_id":"8752","5":"8752","creation_date":"1212566620","6":"1212566620"},{"0":"760","vim_version":"7.0","1":"7.0","script_version":"3.00","2":"3.00","version_comment":"This version reads the 'background' option instead of setting it. Hence you must do :set background=dark or :set background=light before :colo ps_color. (Note that it is incompatible with previous versions!) Some highlightings are made more harmonize with others. Adds an option to enable cterm background transparency.","3":"This version reads the 'background' option instead of setting it. Hence you must do :set background=dark or :set background=light before :colo ps_color. (Note that it is incompatible with previous versions!) Some highlightings are made more harmonize with others. Adds an option to enable cterm background transparency.","package":"ps_color.vim","4":"ps_color.vim","src_id":"6328","5":"6328","creation_date":"1161641918","6":"1161641918"},{"0":"760","vim_version":"7.0","1":"7.0","script_version":"2.9","2":"2.9","version_comment":"This version adds new highlight groups for Vim 7. All the existing Vim 6 highlight groups unchanged. So you don't need to upgrade if using Vim 6. This script was tested both under Vim 6 and Vim 7.","3":"This version adds new highlight groups for Vim 7. All the existing Vim 6 highlight groups unchanged. So you don't need to upgrade if using Vim 6. This script was tested both under Vim 6 and Vim 7.","package":"ps_color.vim","4":"ps_color.vim","src_id":"5986","5":"5986","creation_date":"1153789828","6":"1153789828"},{"0":"760","vim_version":"7.0","1":"7.0","script_version":"0.9","2":"0.9","version_comment":"This is an optional utility for \"ps_color\" scheme, now it works both under Vim 6 and Vim 7.","3":"This is an optional utility for \"ps_color\" scheme, now it works both under Vim 6 and Vim 7.","package":"reloaded.vim","4":"reloaded.vim","src_id":"5985","5":"5985","creation_date":"1153789666","6":"1153789666"},{"0":"760","vim_version":"6.0","1":"6.0","script_version":"2.82","2":"2.82","version_comment":"This version change the default background color to the popular \"dark grey\". It can still be changed anyway.","3":"This version change the default background color to the popular \"dark grey\". It can still be changed anyway.","package":"ps_color.vim","4":"ps_color.vim","src_id":"3642","5":"3642","creation_date":"1100822182","6":"1100822182"},{"0":"760","vim_version":"6.0","1":"6.0","script_version":"0.6","2":"0.6","version_comment":"This is a utility to tune the whole color scheme in HSL color space. There are some minor fix since version 0.5...\r\n\r\nFor me it's great fun, I'll be happy if you found it interesting. ","3":"This is a utility to tune the whole color scheme in HSL color space. There are some minor fix since version 0.5...\r\n\r\nFor me it's great fun, I'll be happy if you found it interesting. ","package":"reloaded.vim","4":"reloaded.vim","src_id":"3237","5":"3237","creation_date":"1089923998","6":"1089923998"},{"0":"760","vim_version":"6.0","1":"6.0","script_version":"n\/a","2":"n\/a","version_comment":"Initial upload","3":"Initial upload","package":"ps_color.vim","4":"ps_color.vim","src_id":"2299","5":"2299","creation_date":"1062693167","6":"1062693167"}]},"759":{"script_id":"759","0":"759","script_name":"LogCVSCommit","1":"LogCVSCommit","script_type":"utility","2":"utility","summary":"Script to log CVS commits","3":"Script to log CVS commits","description":"I use this bit of vimscript to edit CVS commit messages.\r\nThe message, including the affected files, is timestamped and\r\nwritten to a log file.  The log entry format looks like:\r\n________________________________________________________________________________\r\nThu Sep  4 09:30:44 PDT 2003\r\n----------------------------\r\nISSUE00007620 -- resolved\r\nModified Files:\r\n Tag: TEST_11_I6\r\n\tgrounddb\/create\/update_gcsapp_schema.sql \r\n\tgrounddb\/create\/gcsapp\/table\/ans.sql\r\n","4":"I use this bit of vimscript to edit CVS commit messages.\r\nThe message, including the affected files, is timestamped and\r\nwritten to a log file.  The log entry format looks like:\r\n________________________________________________________________________________\r\nThu Sep  4 09:30:44 PDT 2003\r\n----------------------------\r\nISSUE00007620 -- resolved\r\nModified Files:\r\n Tag: TEST_11_I6\r\n\tgrounddb\/create\/update_gcsapp_schema.sql \r\n\tgrounddb\/create\/gcsapp\/table\/ans.sql\r\n","install_details":"1. copy script to ~\/.vim\/plugin\r\n2. You'll need to set a shell environment variable like this:\r\n    export CVSEDITOR='gvim -f +LogCVSCommit'\r\n\r\nMight work with windows, don't know.\r\n","5":"1. copy script to ~\/.vim\/plugin\r\n2. You'll need to set a shell environment variable like this:\r\n    export CVSEDITOR='gvim -f +LogCVSCommit'\r\n\r\nMight work with windows, don't know.\r\n","first_name":"Travis","6":"Travis","last_name":"Hume","7":"Hume","releases":[{"0":"759","vim_version":"6.0","1":"6.0","script_version":"0.01","2":"0.01","version_comment":"Initial upload","3":"Initial upload","package":"LogCVSCommit.vim","4":"LogCVSCommit.vim","src_id":"2298","5":"2298","creation_date":"1062689669","6":"1062689669"}]},"758":{"script_id":"758","0":"758","script_name":"dusk","1":"dusk","script_type":"color scheme","2":"color scheme","summary":"Soft colors on a dark background (GUI only)","3":"Soft colors on a dark background (GUI only)","description":"Soft, low contrast colors on a dark blue-black background. GUI-only. Dusk is a companion to the light background color scheme dawn (vimscript #577).","4":"Soft, low contrast colors on a dark blue-black background. GUI-only. Dusk is a companion to the light background color scheme dawn (vimscript #577).","install_details":"","5":"","first_name":"Ajit","6":"Ajit","last_name":"Thakkar","7":"Thakkar","releases":[{"0":"758","vim_version":"6.0","1":"6.0","script_version":"1.1","2":"1.1","version_comment":"Minor tweaks","3":"Minor tweaks","package":"dusk.vim","4":"dusk.vim","src_id":"4806","5":"4806","creation_date":"1132832845","6":"1132832845"},{"0":"758","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"dusk.vim","4":"dusk.vim","src_id":"2297","5":"2297","creation_date":"1062686710","6":"1062686710"}]},"757":{"script_id":"757","0":"757","script_name":"showpairs-mutated","1":"showpairs-mutated","script_type":"syntax","2":"syntax","summary":"Higlights the matching brace or surrounding ones.","3":"Higlights the matching brace or surrounding ones.","description":"This is a modified version of the script showpairs\n(vimscript #626), written originally by\nAnthony Kruize. When the cursor is on a brace, the matching one is\nhiglighted. Otherwise, the current surrounding braces (up to the depth of three) are emphasised.\n","4":"This is a modified version of the script showpairs\n(vimscript #626), written originally by\nAnthony Kruize. When the cursor is on a brace, the matching one is\nhiglighted. Otherwise, the current surrounding braces (up to the depth of three) are emphasised.\n","install_details":"Just put the script into your $HOME\/.vim\/plugin directory.","5":"Just put the script into your $HOME\/.vim\/plugin directory.","first_name":"Szymon","6":"Szymon","last_name":"Kielbasa","7":"Kielbasa","releases":[{"0":"757","vim_version":"6.0","1":"6.0","script_version":"1.2","2":"1.2","version_comment":"Initial upload","3":"Initial upload","package":"showpairs.vim","4":"showpairs.vim","src_id":"2294","5":"2294","creation_date":"1062639323","6":"1062639323"}]},"756":{"script_id":"756","0":"756","script_name":"python_encoding.vim","1":"python_encoding.vim","script_type":"ftplugin","2":"ftplugin","summary":"Recognize python source file encoding directive(PEP 0263)","3":"Recognize python source file encoding directive(PEP 0263)","description":"A newly added feature of python 2.3 is PEP 0263(http:\/\/www.python.org\/peps\/pep-0263.html). Now you can add a magic comment that defines the encoding of the source file. This script recognizes this directive and changes Vim's encoding accordingly.\r\n","4":"A newly added feature of python 2.3 is PEP 0263(http:\/\/www.python.org\/peps\/pep-0263.html). Now you can add a magic comment that defines the encoding of the source file. This script recognizes this directive and changes Vim's encoding accordingly.\r\n","install_details":"Just put it in your ftplugin directory.","5":"Just put it in your ftplugin directory.","first_name":"Sangpil","6":"Sangpil","last_name":"Yoon","7":"Yoon","releases":[{"0":"756","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"python_encoding.vim","4":"python_encoding.vim","src_id":"2292","5":"2292","creation_date":"1062532067","6":"1062532067"}]},"755":{"script_id":"755","0":"755","script_name":"VDLGBX.DLL","1":"VDLGBX.DLL","script_type":"utility","2":"utility","summary":"Comfortable user-definable dialog-boxes for use in GVIM and some other goodies","3":"Comfortable user-definable dialog-boxes for use in GVIM and some other goodies","description":"Allows to compose and use arbitrary dialog boxes within your scripts.\r\nFeatures:\r\n* simple textfield\r\n* password-field\r\n* checkboxes\r\n* listboxes\r\n* comboboxes\r\n\r\nHTML-authoring-support:\r\nCreate an <IMG SRC=\"xxx\" WIDTH=\"nnn\" HEIGHT=\"nnn\"\/>-Tag out from simple the filename\r\nTranslate foreign chars to HTML-entities (eg. \u00c3\u00a4 -> &aauml;)\r\n\r\nColor-choosing\r\nAllows to choose a color (using the standard windows-dialog) and returns the RGB-values in whatever format you want (so far an arbitrary printf-formatstring can do it...)","4":"Allows to compose and use arbitrary dialog boxes within your scripts.\r\nFeatures:\r\n* simple textfield\r\n* password-field\r\n* checkboxes\r\n* listboxes\r\n* comboboxes\r\n\r\nHTML-authoring-support:\r\nCreate an <IMG SRC=\"xxx\" WIDTH=\"nnn\" HEIGHT=\"nnn\"\/>-Tag out from simple the filename\r\nTranslate foreign chars to HTML-entities (eg. \u00c3\u00a4 -> &aauml;)\r\n\r\nColor-choosing\r\nAllows to choose a color (using the standard windows-dialog) and returns the RGB-values in whatever format you want (so far an arbitrary printf-formatstring can do it...)","install_details":"Copy VDLGBX.DLL into the runtime-folder (eg. vim61).\r\nRead and execute VDLGBX.VIM - it's both a documentation and testing run.","5":"Copy VDLGBX.DLL into the runtime-folder (eg. vim61).\r\nRead and execute VDLGBX.VIM - it's both a documentation and testing run.","first_name":"Michael","6":"Michael","last_name":"Fitz","7":"Fitz","releases":[{"0":"755","vim_version":"6.0","1":"6.0","script_version":"1.4","2":"1.4","version_comment":"New Feature:\r\nCOLOR: Get RGB-values from standard color-choosing-dialog in (almost) any format you like","3":"New Feature:\r\nCOLOR: Get RGB-values from standard color-choosing-dialog in (almost) any format you like","package":"VDLGBX.zip","4":"VDLGBX.zip","src_id":"3287","5":"3287","creation_date":"1091117914","6":"1091117914"},{"0":"755","vim_version":"6.0","1":"6.0","script_version":"1.3","2":"1.3","version_comment":"Some bugs fixed. \r\nNew features: \r\nPasswordfield, HTML-Translate","3":"Some bugs fixed. \r\nNew features: \r\nPasswordfield, HTML-Translate","package":"VDLGBX.zip","4":"VDLGBX.zip","src_id":"2816","5":"2816","creation_date":"1078737094","6":"1078737094"},{"0":"755","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"VDLGBX.zip","4":"VDLGBX.zip","src_id":"2291","5":"2291","creation_date":"1062500444","6":"1062500444"}]},"754":{"script_id":"754","0":"754","script_name":"ttcn-indent","1":"ttcn-indent","script_type":"indent","2":"indent","summary":"TTCN-3 indent file","3":"TTCN-3 indent file","description":"This is a simple indent file for TTCN-3.","4":"This is a simple indent file for TTCN-3.","install_details":"Drop the file in your local indent directory (e.g. ~\/.vim\/indent).\r\n\r\nNote: If you want to make Vim automatically detect the file type *.ttcn, see the \"install details\" section of the TTCN-3 syntax highlighting script (vimscript #753).","5":"Drop the file in your local indent directory (e.g. ~\/.vim\/indent).\r\n\r\nNote: If you want to make Vim automatically detect the file type *.ttcn, see the \"install details\" section of the TTCN-3 syntax highlighting script (vimscript #753).","first_name":"Stefan","6":"Stefan","last_name":"Karlsson","7":"Karlsson","releases":[{"0":"754","vim_version":"6.0","1":"6.0","script_version":"0.5","2":"0.5","version_comment":"Updated for Vim 6.3 (the script uses cindent, which was modified in Vim 6.3).","3":"Updated for Vim 6.3 (the script uses cindent, which was modified in Vim 6.3).","package":"ttcn.vim","4":"ttcn.vim","src_id":"3261","5":"3261","creation_date":"1090505280","6":"1090505280"},{"0":"754","vim_version":"6.0","1":"6.0","script_version":"0.4","2":"0.4","version_comment":"Made some minor adjustments. In order for things to work, you must download the new \"ttcn-ftplugin\" as well.","3":"Made some minor adjustments. In order for things to work, you must download the new \"ttcn-ftplugin\" as well.","package":"ttcn.vim","4":"ttcn.vim","src_id":"2940","5":"2940","creation_date":"1082128494","6":"1082128494"}]},"753":{"script_id":"753","0":"753","script_name":"ttcn-syntax","1":"ttcn-syntax","script_type":"syntax","2":"syntax","summary":"TTCN-3 syntax highlighting file","3":"TTCN-3 syntax highlighting file","description":"I couldn't find any syntax file for TTCN-3, so I made my own. The file is based on ETSI document no. ES 201 873-1 (V2.2.1 2003-02).\r\n\r\nFor information about TTCN-3, see http:\/\/www.etsi.org.\r\n\r\nFolds: If the variable \"g:ttcn_fold\" is defined (e.g. by \":let g:ttcn_fold = 1\" in your .vimrc file), folds will automatically be defined for each {...} block.\r\n","4":"I couldn't find any syntax file for TTCN-3, so I made my own. The file is based on ETSI document no. ES 201 873-1 (V2.2.1 2003-02).\r\n\r\nFor information about TTCN-3, see http:\/\/www.etsi.org.\r\n\r\nFolds: If the variable \"g:ttcn_fold\" is defined (e.g. by \":let g:ttcn_fold = 1\" in your .vimrc file), folds will automatically be defined for each {...} block.\r\n","install_details":"Just drop the file in your local syntax directory (e.g. ~\/.vim\/syntax). \r\n\r\nIf you want Vim to automatically detect the file type *.ttcn, you should edit your \"filetype.vim\" file (on linux it should be located in ~\/.vim). For example, my filetype.vim looks like this:\r\n\r\nif exists(\"did_load_filetypes\")\r\n    finish\r\nendif\r\naugroup filetypedetect\r\n    au BufNewFile,BufRead *.ttcn  setf ttcn    << This is the line!\r\n    au BufNewFile,BufRead *.antlr setf antlr\r\naugroup END\r\n\r\n\r\n","5":"Just drop the file in your local syntax directory (e.g. ~\/.vim\/syntax). \r\n\r\nIf you want Vim to automatically detect the file type *.ttcn, you should edit your \"filetype.vim\" file (on linux it should be located in ~\/.vim). For example, my filetype.vim looks like this:\r\n\r\nif exists(\"did_load_filetypes\")\r\n    finish\r\nendif\r\naugroup filetypedetect\r\n    au BufNewFile,BufRead *.ttcn  setf ttcn    << This is the line!\r\n    au BufNewFile,BufRead *.antlr setf antlr\r\naugroup END\r\n\r\n\r\n","first_name":"Stefan","6":"Stefan","last_name":"Karlsson","7":"Karlsson","releases":[{"0":"753","vim_version":"6.0","1":"6.0","script_version":"1.1","2":"1.1","version_comment":"Added spell checking support (only comments are spell checked) for those who use Vim 7.","3":"Added spell checking support (only comments are spell checked) for those who use Vim 7.","package":"ttcn.vim","4":"ttcn.vim","src_id":"4483","5":"4483","creation_date":"1123676831","6":"1123676831"},{"0":"753","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Added variable g:ttcn_minlines. If this variable is set (e.g. let g:ttcn_minlines=100) it will be used to set \"minlines\" in the syntax synchronization. If it is not set \":syn sync fromstart\" will be used. Thanks to John Orr for pointing out a problem that led to this change.","3":"Added variable g:ttcn_minlines. If this variable is set (e.g. let g:ttcn_minlines=100) it will be used to set \"minlines\" in the syntax synchronization. If it is not set \":syn sync fromstart\" will be used. Thanks to John Orr for pointing out a problem that led to this change.","package":"ttcn.vim","4":"ttcn.vim","src_id":"3461","5":"3461","creation_date":"1095490415","6":"1095490415"}]},"752":{"script_id":"752","0":"752","script_name":"opengl.vim","1":"opengl.vim","script_type":"syntax","2":"syntax","summary":"OpenGL C syntax highlighting","3":"OpenGL C syntax highlighting","description":"OpenGL C syntax highlighting.\r\n","4":"OpenGL C syntax highlighting.\r\n","install_details":"just source it from your ~\/.vim\/syntax\/c.vim\r\nor add line to your .vimrc (C:\\VIM\\_VIMRC on MS)\r\nautocmd FileType c,cpp source \/path\/to\/opengl.vim","5":"just source it from your ~\/.vim\/syntax\/c.vim\r\nor add line to your .vimrc (C:\\VIM\\_VIMRC on MS)\r\nautocmd FileType c,cpp source \/path\/to\/opengl.vim","first_name":"Eugene","6":"Eugene","last_name":"Andreeshchev","7":"Andreeshchev","releases":[{"0":"752","vim_version":"6.0","1":"6.0","script_version":"1.5","2":"1.5","version_comment":"Added OpenGL ES 2.0 and EGL symbols (without vendor extensions, for now).\r\nCan be disabled with following variables: c_opengl_no_gles2, c_opengl_no_egl.\r\n\r\nThanks to Simon Hosie [sh1 at broadcom dot com]!","3":"Added OpenGL ES 2.0 and EGL symbols (without vendor extensions, for now).\r\nCan be disabled with following variables: c_opengl_no_gles2, c_opengl_no_egl.\r\n\r\nThanks to Simon Hosie [sh1 at broadcom dot com]!","package":"opengl.vim","4":"opengl.vim","src_id":"7583","5":"7583","creation_date":"1188435197","6":"1188435197"},{"0":"752","vim_version":"6.0","1":"6.0","script_version":"1.4.1","2":"1.4.1","version_comment":"Added support for GLUT.","3":"Added support for GLUT.","package":"opengl.vim","4":"opengl.vim","src_id":"2465","5":"2465","creation_date":"1068154071","6":"1068154071"},{"0":"752","vim_version":"6.0","1":"6.0","script_version":"1.4","2":"1.4","version_comment":"Updated to OpenGL 1.4 ARB extensions for OpenGL Shading Language.\n","3":"Updated to OpenGL 1.4 ARB extensions for OpenGL Shading Language.\n","package":"opengl.vim","4":"opengl.vim","src_id":"2438","5":"2438","creation_date":"1067544728","6":"1067544728"},{"0":"752","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"opengl.vim","4":"opengl.vim","src_id":"2285","5":"2285","creation_date":"1062235635","6":"1062235635"}]},"751":{"script_id":"751","0":"751","script_name":"winhelp","1":"winhelp","script_type":"utility","2":"utility","summary":"A script for easy lookup in Windows .chm and .hlp help files.","3":"A script for easy lookup in Windows .chm and .hlp help files.","description":"This script lets you setup a collection of help files in Windows .hlp and\r\n.chm format and search for the word under the cursor in them. The current\r\nfiles and state is stored in the scricpt file for further sessions. Use the\r\nnew winhelp dropdown menu to add or remove files.\r\nCheck out tip #506\r\nhttp:\/\/www.vim.org\/tips\/tip.php?tip_id=506\r\nand tip #232\r\nhttp:\/\/www.vim.org\/tips\/tip.php?tip_id=232\r\n\r\nThe default keymappings for normal mode are: \r\nCtrl+Shift+F1 - pops up a menu with the help files and search the selected\r\nfile for the word under the cursor.\r\nCtrl+F1 - search the current help file for the word. Use the winhelp menu\r\nfor setting the current help file.\r\n\r\nBUGS\/Features\r\n-If the path to a.chm file has any spaces does not keyhh or hh works\r\nproperly. I think this is a known issue with Windows HTML help. Bob solved\r\nit by linking directories and I think that is the only way.\r\n-If you do an ALT+TAB to get away from a .chm file may you see an temporary\r\n extra copy in the taskbar. Note that the icons for .chm is the ones\r\n normally used for .hlp files.\r\n -It will probably take some time before you get used to how keyhh works. \r\n In my experience does it work very well but sometimes do you have to look twice to see it. :)   \r\n-The popup menu can be incorrect after removing a file from  the collection. After a restart is it OK. \r\n ","4":"This script lets you setup a collection of help files in Windows .hlp and\r\n.chm format and search for the word under the cursor in them. The current\r\nfiles and state is stored in the scricpt file for further sessions. Use the\r\nnew winhelp dropdown menu to add or remove files.\r\nCheck out tip #506\r\nhttp:\/\/www.vim.org\/tips\/tip.php?tip_id=506\r\nand tip #232\r\nhttp:\/\/www.vim.org\/tips\/tip.php?tip_id=232\r\n\r\nThe default keymappings for normal mode are: \r\nCtrl+Shift+F1 - pops up a menu with the help files and search the selected\r\nfile for the word under the cursor.\r\nCtrl+F1 - search the current help file for the word. Use the winhelp menu\r\nfor setting the current help file.\r\n\r\nBUGS\/Features\r\n-If the path to a.chm file has any spaces does not keyhh or hh works\r\nproperly. I think this is a known issue with Windows HTML help. Bob solved\r\nit by linking directories and I think that is the only way.\r\n-If you do an ALT+TAB to get away from a .chm file may you see an temporary\r\n extra copy in the taskbar. Note that the icons for .chm is the ones\r\n normally used for .hlp files.\r\n -It will probably take some time before you get used to how keyhh works. \r\n In my experience does it work very well but sometimes do you have to look twice to see it. :)   \r\n-The popup menu can be incorrect after removing a file from  the collection. After a restart is it OK. \r\n ","install_details":"The script must be in the $VIM\/vimfiles\/plugin\/ directory.\r\nFor the .hlp files is the script using Windows winhelp program. You can test with a \"winhelp helpfile.hlp\" from the command line. If no luck can you try to replace winhelp with winhlp32 in the script but I belive this is the same.\r\nFor the .chm files is keyhh from this page used\r\nhttp:\/\/www.keyworks.net\/keyhh.htm \r\nIt worked for me but I dont know if you need the HTML workshop installed?\r\nMy suggestion is to visit MSDN in case of problems. Here is a direct\r\nlink to the HTML help downloads from MSDN\r\n http:\/\/msdn.microsoft.com\/library\/default.asp?url=\/library\/en-us\/htmlhelp\/html\/hwMicrosoftHTMLHelpDownloads.asp\r\n\r\nMSDN is also the main source for .chm files. The Platform SDK has a complete set of .chm files for Windows. Borland has some .hlp files here\r\nhttp:\/\/info.borland.com\/techpubs\/bcppbuilder\/v5\/updates\/ent.html\r\nthere the most interesting are\r\nB5MS.ZIP - Win32 API documentation old but useful with stuff like\r\nOpenGL1.1, a similar file can be downloaded from the lcc compiler page\r\nB5SCL.ZIP - Standard C++ library help with STL\r\nB5RTL.ZIP - C lib reference\r\n \r\nJava users should take a look at tip #232 mentioned above. \r\n","5":"The script must be in the $VIM\/vimfiles\/plugin\/ directory.\r\nFor the .hlp files is the script using Windows winhelp program. You can test with a \"winhelp helpfile.hlp\" from the command line. If no luck can you try to replace winhelp with winhlp32 in the script but I belive this is the same.\r\nFor the .chm files is keyhh from this page used\r\nhttp:\/\/www.keyworks.net\/keyhh.htm \r\nIt worked for me but I dont know if you need the HTML workshop installed?\r\nMy suggestion is to visit MSDN in case of problems. Here is a direct\r\nlink to the HTML help downloads from MSDN\r\n http:\/\/msdn.microsoft.com\/library\/default.asp?url=\/library\/en-us\/htmlhelp\/html\/hwMicrosoftHTMLHelpDownloads.asp\r\n\r\nMSDN is also the main source for .chm files. The Platform SDK has a complete set of .chm files for Windows. Borland has some .hlp files here\r\nhttp:\/\/info.borland.com\/techpubs\/bcppbuilder\/v5\/updates\/ent.html\r\nthere the most interesting are\r\nB5MS.ZIP - Win32 API documentation old but useful with stuff like\r\nOpenGL1.1, a similar file can be downloaded from the lcc compiler page\r\nB5SCL.ZIP - Standard C++ library help with STL\r\nB5RTL.ZIP - C lib reference\r\n \r\nJava users should take a look at tip #232 mentioned above. \r\n","first_name":"Peter","6":"Peter","last_name":"Puck","7":"Puck","releases":[{"0":"751","vim_version":"6.0","1":"6.0","script_version":"2.0","2":"2.0","version_comment":"Fixed so that help files can be in a path with spaces, thanks to Bob Davis for the bug report. It still does not work properly for .chm files in such paths but the bug is not in the script.\r\nFixed some other bugs and updated the documentation.","3":"Fixed so that help files can be in a path with spaces, thanks to Bob Davis for the bug report. It still does not work properly for .chm files in such paths but the bug is not in the script.\r\nFixed some other bugs and updated the documentation.","package":"winhelp.vim","4":"winhelp.vim","src_id":"2301","5":"2301","creation_date":"1062745473","6":"1062745473"},{"0":"751","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"winhelp.vim","4":"winhelp.vim","src_id":"2278","5":"2278","creation_date":"1062101818","6":"1062101818"}]},"750":{"script_id":"750","0":"750","script_name":"aiseered.vim","1":"aiseered.vim","script_type":"color scheme","2":"color scheme","summary":"A color scheme with a dark red background.","3":"A color scheme with a dark red background.","description":"(For those who are interested: \"aiSee\" is a trade mark which is expected to be pronounced \"I see\".)\r\n\r\nI find this scheme quite pleasant -- even though any red, including dark red, is always said to be a bad choice for a background.\r\n\r\nAnyway, I'm not selling a pig in a poke here: http:\/\/www.aisee.com\/aiseered.png\r\n\r\nI've written the scheme especially for working with files in GDL\/VCG format (hence the naming), and it goes well together with vimscript #706. It also works quite fine for C\/C++ and I've heard of people using it for editing Ruby. However, I wouldn't recommend using it for editing HTML if you do care for your eyes.\r\n\r\naiseered was tested with gVim 6.2 under Windows 2000 and with gVim 6.3 under Ubuntu Linux.\r\n\r\nYour feedback is appreciated.","4":"(For those who are interested: \"aiSee\" is a trade mark which is expected to be pronounced \"I see\".)\r\n\r\nI find this scheme quite pleasant -- even though any red, including dark red, is always said to be a bad choice for a background.\r\n\r\nAnyway, I'm not selling a pig in a poke here: http:\/\/www.aisee.com\/aiseered.png\r\n\r\nI've written the scheme especially for working with files in GDL\/VCG format (hence the naming), and it goes well together with vimscript #706. It also works quite fine for C\/C++ and I've heard of people using it for editing Ruby. However, I wouldn't recommend using it for editing HTML if you do care for your eyes.\r\n\r\naiseered was tested with gVim 6.2 under Windows 2000 and with gVim 6.3 under Ubuntu Linux.\r\n\r\nYour feedback is appreciated.","install_details":"gVim\/Windows users:\r\n------------------------------\r\nSimply put the downloaded VIM file to your Vim color schemes directory (for Vim 6.3, it is usually C:\\Vim\\vim63\\colors or C:\\Program Files\\Vim\\vim63\\colors) and then use the Vim command \r\n:color aiseered\r\nto switch the coloring on. \r\n\r\ngVim\/Linux users:\r\n-------------------------\r\nCopy the downloaded VIM file to the directory $VIMRUNTIME\/colors\/ and use the command\r\n:color aiseered\r\nto switch the coloring on. \r\n\r\nIf you are not sure about the value of $VIMRUNTIME, try ~\/.vim or type \r\n:help runtime \r\n","5":"gVim\/Windows users:\r\n------------------------------\r\nSimply put the downloaded VIM file to your Vim color schemes directory (for Vim 6.3, it is usually C:\\Vim\\vim63\\colors or C:\\Program Files\\Vim\\vim63\\colors) and then use the Vim command \r\n:color aiseered\r\nto switch the coloring on. \r\n\r\ngVim\/Linux users:\r\n-------------------------\r\nCopy the downloaded VIM file to the directory $VIMRUNTIME\/colors\/ and use the command\r\n:color aiseered\r\nto switch the coloring on. \r\n\r\nIf you are not sure about the value of $VIMRUNTIME, try ~\/.vim or type \r\n:help runtime \r\n","first_name":"Alexander","6":"Alexander","last_name":"Evstiougov","7":"Evstiougov","releases":[{"0":"750","vim_version":"6.0","1":"6.0","script_version":"0.2","2":"0.2","version_comment":"This version is for gVim\/Linux","3":"This version is for gVim\/Linux","package":"aiseered.vim","4":"aiseered.vim","src_id":"3794","5":"3794","creation_date":"1106640724","6":"1106640724"},{"0":"750","vim_version":"6.0","1":"6.0","script_version":"0.2win","2":"0.2win","version_comment":"Minor enhancements.","3":"Minor enhancements.","package":"aiseered.vim","4":"aiseered.vim","src_id":"2310","5":"2310","creation_date":"1062998055","6":"1062998055"},{"0":"750","vim_version":"6.0","1":"6.0","script_version":"0.1win","2":"0.1win","version_comment":"Initial upload; useful for gVim only.","3":"Initial upload; useful for gVim only.","package":"aiseered.vim","4":"aiseered.vim","src_id":"2275","5":"2275","creation_date":"1062076694","6":"1062076694"}]},"749":{"script_id":"749","0":"749","script_name":"pic.vim","1":"pic.vim","script_type":"color scheme","2":"color scheme","summary":"Add support for 18fxx2 Microchip microcontrollers","3":"Add support for 18fxx2 Microchip microcontrollers","description":"Add support for 18fxx2 Microchip microcontrollers.","4":"Add support for 18fxx2 Microchip microcontrollers.","install_details":"","5":"","first_name":"Diego","6":"Diego","last_name":"Belotti","7":"Belotti","releases":[{"0":"749","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"pic.vim","4":"pic.vim","src_id":"2272","5":"2272","creation_date":"1061922490","6":"1061922490"}]},"748":{"script_id":"748","0":"748","script_name":"HelpExtractor","1":"HelpExtractor","script_type":"utility","2":"utility","summary":"plugin writer aid; allows plugin and help to be distributed as one file","3":"plugin writer aid; allows plugin and help to be distributed as one file","description":"(this plugin has largely been superceded by script#1502 for vim7.0)\r\n\r\nThe HelpExtractor is a bit of vim code that allows one to merge the plugin with the help.  In addition, helptags is run automatically for the user.\r\n\r\nTypical use under Unix\/Linux\/Cygwin, done from the .vim (vimfiles) directory:\r\n\r\n    cat plugin\/yourplugin.vim HelpExtractor.vim doc\/yourplugin.txt > yourplugin.vim\r\n\r\nHelpExtractor will modify the accompanying plugin the first time the user runs Vim (it will delete the extraction code) and will generate the associated help file.  The distributed file will then have the following format:\r\n\r\n    [Plugin]\r\n    [HelpExtractor]\r\n    [HelpFile]\r\n\r\nWhen vim is next executed, the HelpExtractor modifies the plugin to be:\r\n\r\n    [Plugin]\r\n\r\nand creates a file in the user's .vim\/doc directory containing the [Helpfile].  Since the HelpExtractor also runs helptags automatically, the associated help is immediately available without any actions being required of the user.  Notice that the [HelpExtractor] itself disappears.\r\n\r\n","4":"(this plugin has largely been superceded by script#1502 for vim7.0)\r\n\r\nThe HelpExtractor is a bit of vim code that allows one to merge the plugin with the help.  In addition, helptags is run automatically for the user.\r\n\r\nTypical use under Unix\/Linux\/Cygwin, done from the .vim (vimfiles) directory:\r\n\r\n    cat plugin\/yourplugin.vim HelpExtractor.vim doc\/yourplugin.txt > yourplugin.vim\r\n\r\nHelpExtractor will modify the accompanying plugin the first time the user runs Vim (it will delete the extraction code) and will generate the associated help file.  The distributed file will then have the following format:\r\n\r\n    [Plugin]\r\n    [HelpExtractor]\r\n    [HelpFile]\r\n\r\nWhen vim is next executed, the HelpExtractor modifies the plugin to be:\r\n\r\n    [Plugin]\r\n\r\nand creates a file in the user's .vim\/doc directory containing the [Helpfile].  Since the HelpExtractor also runs helptags automatically, the associated help is immediately available without any actions being required of the user.  Notice that the [HelpExtractor] itself disappears.\r\n\r\n","install_details":"1. make .vim (vimfiles) your current directory\r\n2. place HelpExtractor.tar.gz in the .vim (vimfiles) directory\r\n3. gunzip HelpExtractor.tar.gz\r\n4. tar -oxvf HelpExtractor.tar\r\n5. vim\r\n    :helptags ~\/.vim\/doc\r\n    :wq\r\n\r\nWill create VIMSCRIPT\/HelpExtractor.vim and doc\/HelpExtractor.txt.  ","5":"1. make .vim (vimfiles) your current directory\r\n2. place HelpExtractor.tar.gz in the .vim (vimfiles) directory\r\n3. gunzip HelpExtractor.tar.gz\r\n4. tar -oxvf HelpExtractor.tar\r\n5. vim\r\n    :helptags ~\/.vim\/doc\r\n    :wq\r\n\r\nWill create VIMSCRIPT\/HelpExtractor.vim and doc\/HelpExtractor.txt.  ","first_name":"Charles","6":"Charles","last_name":"Campbell","7":"Campbell","releases":[{"0":"748","vim_version":"6.0","1":"6.0","script_version":"3","2":"3","version_comment":"HelpExtractor v2 exhibited odd behavior when one attempted to source a plugin using it from a non-standard location.  Remember, the HelpExtractor is trying to extract documentation from the file, put it in the .vim\/doc (vimfiles\\doc) directory, and remove the extractor code.  An error message is now produced and the extraction is \"finish\"d, leaving the plugin operational but with the extractor code and help intact (but not available via :help).\r\n","3":"HelpExtractor v2 exhibited odd behavior when one attempted to source a plugin using it from a non-standard location.  Remember, the HelpExtractor is trying to extract documentation from the file, put it in the .vim\/doc (vimfiles\\doc) directory, and remove the extractor code.  An error message is now produced and the extraction is \"finish\"d, leaving the plugin operational but with the extractor code and help intact (but not available via :help).\r\n","package":"HelpExtractor.tar.gz","4":"HelpExtractor.tar.gz","src_id":"4319","5":"4319","creation_date":"1117005174","6":"1117005174"},{"0":"748","vim_version":"6.0","1":"6.0","script_version":"2","2":"2","version_comment":"HelpExtractor will create a doc directory for the user if it doesn't currently exist under Linux\/Unix.  It now also cooperates with the GetLatestVimScripts automatic updating.\r\n","3":"HelpExtractor will create a doc directory for the user if it doesn't currently exist under Linux\/Unix.  It now also cooperates with the GetLatestVimScripts automatic updating.\r\n","package":"HelpExtractor.vim","4":"HelpExtractor.vim","src_id":"3434","5":"3434","creation_date":"1094719883","6":"1094719883"}]},"747":{"script_id":"747","0":"747","script_name":"Intellisense for Vim","1":"Intellisense for Vim","script_type":"utility","2":"utility","summary":"Java, XML, HTML, C++, JSP, SQL, C#","3":"Java, XML, HTML, C++, JSP, SQL, C#","description":"This is intellisense for Java, XML, HTML, C++, JSP, SQL, C#. This new version is incompatible with the previous version(s).\r\nIMPORTANT: Uninstall any previous versions if you have and then install the new version. \r\n\r\nTHIS IS FOR WINDOWS ONLY! \r\n\r\nUsage Tips\r\n----------------\r\n1. Pressing '.' (in java) or pressing '<'  in XML\/Html brings the list window\r\n2. Pressing <C-Space> brings context sensitive lists (for both java and HTML\/XML).\r\nIn HTML\/XML this brings the list of attributes for the tags, or auto-completes the attributes)\r\nTry C-Space at different points.\r\n\r\nWhile tool tip is shown, you can use mouse to move to next function or use <C-Left> or <C-Right>\r\n\r\n<C-S-Space> in java, brings the tooltip for the current function.\r\n\r\nSQL\r\n------\r\nThe SQL plugin provides completion for both static and dynamic data.  A tutorial is provided in intellisense.txt.  See :h intellisense-sql.\r\n\r\nDynamic lists (drawn directly from your database):\r\n    Table List \r\n        - All tables for all schema owners\r\n    Procedure List\r\n        - All stored procedures for all schema owners\r\n    View List\r\n        - All stored procedures for all schema owners\r\n    Column List\r\n        - For the selected table, the columns that are part of the table    \r\n    Table \/ Procedure Description\r\n        - For the selected table\/procedure, describe it    \r\n\r\n\r\nStatic lists (drawn directly from your Vim SQL syntax file):\r\n    Statements\r\n        - Select, Insert, Update, Delete, Create, Alter, ...\r\n    Functions\r\n        - Min, Max, Trim, Round, Date, ...\r\n    Keywords\r\n        - Index, Database, Having, Group, With\r\n    Types\r\n        - Integer, Char, Varchar, Date, DateTime, Timestamp, ...\r\n    Operators\r\n        - Like, Where, And, Or, In, Exists, ...\r\n    Database Options\r\n        - Isolation_level, On_error, Qualify_owners, Fire_triggers\r\n\r\n","4":"This is intellisense for Java, XML, HTML, C++, JSP, SQL, C#. This new version is incompatible with the previous version(s).\r\nIMPORTANT: Uninstall any previous versions if you have and then install the new version. \r\n\r\nTHIS IS FOR WINDOWS ONLY! \r\n\r\nUsage Tips\r\n----------------\r\n1. Pressing '.' (in java) or pressing '<'  in XML\/Html brings the list window\r\n2. Pressing <C-Space> brings context sensitive lists (for both java and HTML\/XML).\r\nIn HTML\/XML this brings the list of attributes for the tags, or auto-completes the attributes)\r\nTry C-Space at different points.\r\n\r\nWhile tool tip is shown, you can use mouse to move to next function or use <C-Left> or <C-Right>\r\n\r\n<C-S-Space> in java, brings the tooltip for the current function.\r\n\r\nSQL\r\n------\r\nThe SQL plugin provides completion for both static and dynamic data.  A tutorial is provided in intellisense.txt.  See :h intellisense-sql.\r\n\r\nDynamic lists (drawn directly from your database):\r\n    Table List \r\n        - All tables for all schema owners\r\n    Procedure List\r\n        - All stored procedures for all schema owners\r\n    View List\r\n        - All stored procedures for all schema owners\r\n    Column List\r\n        - For the selected table, the columns that are part of the table    \r\n    Table \/ Procedure Description\r\n        - For the selected table\/procedure, describe it    \r\n\r\n\r\nStatic lists (drawn directly from your Vim SQL syntax file):\r\n    Statements\r\n        - Select, Insert, Update, Delete, Create, Alter, ...\r\n    Functions\r\n        - Min, Max, Trim, Round, Date, ...\r\n    Keywords\r\n        - Index, Database, Having, Group, With\r\n    Types\r\n        - Integer, Char, Varchar, Date, DateTime, Timestamp, ...\r\n    Operators\r\n        - Like, Where, And, Or, In, Exists, ...\r\n    Database Options\r\n        - Isolation_level, On_error, Qualify_owners, Fire_triggers\r\n\r\n","install_details":"Setup is available. \r\nFor more information read the intellisense.txt which is accompanied with the download for install details.\r\nAfter setup completes update Vim's documentation using the helptags command:\r\n:helptags $VIM\\vimfiles\\doc\r\n:h intellisense\r\n\r\n","5":"Setup is available. \r\nFor more information read the intellisense.txt which is accompanied with the download for install details.\r\nAfter setup completes update Vim's documentation using the helptags command:\r\n:helptags $VIM\\vimfiles\\doc\r\n:h intellisense\r\n\r\n","first_name":"Ravi","6":"Ravi","last_name":"Shankar","7":"Shankar","releases":[{"0":"747","vim_version":"6.0","1":"6.0","script_version":"1.3","2":"1.3","version_comment":"This is just the changelog. You can download from http:\/\/insenvim.sourceforge.net\r\nChangelog only is given due to space constraints.","3":"This is just the changelog. You can download from http:\/\/insenvim.sourceforge.net\r\nChangelog only is given due to space constraints.","package":"changelog.txt","4":"changelog.txt","src_id":"3545","5":"3545","creation_date":"1097750371","6":"1097750371"}]},"746":{"script_id":"746","0":"746","script_name":"cmdalias.vim","1":"cmdalias.vim","script_type":"utility","2":"utility","summary":"Create aliases for Vim commands.","3":"Create aliases for Vim commands.","description":"Sometimes we want to to change the behavior of a built-in command so end up creating a custom command, and we wish to reuse the built-in command name for it. E.g., :Runtime to replace :runtime, :Find to replace :find. I myself wanted to replace :qa with :QA (see http:\/\/vim.wikia.com\/wiki\/Tabclose_instead_of_quit-all), but it is hard to remember to type :QA instead of :qa everytime, that is why I created this plugin.\r\n\r\nThis plugin is just a wrapper on top of command-line abbreviations (:cabbr), to work around the big disadvantages of :cabbr. With plain :cabbr, the expansion happens anywhere the abbreviation appears while typing command-line. E.g., if you create abbreviation from runtime->Runtime, then the following will not work as you expect:\r\n\r\n:cnoreabbr runtime Runtime\r\n:%s\/runtime\/runduration\/g\r\n\r\nWhat would actually execute is:\r\n\r\n:%s\/Runtime\/runduration\/g\r\n\r\nWhich is not the same. The other problem is cabbr's trigger not only at the command-line, but also at search prompt, at the input prompt and any other prompts (see :help getcmdtype()). To avoid those unexpected expansions, cmdalias utilizes a light-weight wrapper function that expands the abbreviation only when it is typed as the first word of the ex command (\":\" prompt). So, instead of the below:\r\n\r\n:cnoreabbr runtime Runtime\r\n\r\nYou would use this:\r\n\r\n:call CmdAlias('runtime', 'Runtime')\r\n\r\nor simply,\r\n\r\n:Alias runtime Runtime\r\n\r\nThese aliases pretty much work like the bash aliases. If you don't want the expansion to temporarily happen even at the beginning of a command, you have two options:\r\n- After entering the command and before typing the next command press <C-V> (e.g., <C-V><Space>)\r\n- Start the command-line with a space and then enter the command.\r\n\r\nThe CmdAlias() function takes a 3rd optional argument called \"flags\" for which you can pass options such as \"<buffer>\" to make the alias local to the current buffer.\r\n\r\nHere is the description from file header for more details:\r\nUsage:\r\n    :call CmdAlias('<lhs>', '<rhs>', [flags])\r\n    or\r\n    :Alias <lhs> <rhs> [flags]\r\n                                                                             \r\n    :UnAlias <lhs> ...\r\n    :Aliases [<lhs> ...]\r\n                                                                             \r\nEx:\r\n    :Alias runtime Runtime\r\n    :Alias find Find\r\n    :Aliases\r\n    :UnAlias find\r\n                                                                             \r\nDescription:\r\n  - Vim doesn't allow us to create user-defined commands unless they start\r\n    with an uppercase letter. I find this annoying and constrained when it\r\n    comes to overriding built-in commands with my own. To override built-in\r\n    commands, we often have to create a new command that has the same name\r\n    as the built-in but starting with an uppercase letter (e.g., \"Cd\"\r\n    instead of \"cd\"), and remember to use that everytime (besides the\r\n    fact that typing uppercase letters take more effort). An alternative is\r\n    to use the :cabbr to create an abbreviation for the built-in command\r\n    (:cmap is not good) to the user-defined command (e.g., \"cabbr cd Cd\").\r\n    But this would generally cause more inconvenience because the\r\n    abbreviation gets expanded no matter where in the command-line you use\r\n    it. This is where the plugin comes to your rescue by arranging the cabbr\r\n    to expand only if typed as the first word in the command-line, in a\r\n    sense working like the aliases in csh or bash.\r\n  - The plugin provides a function to define command-line abbreviations such\r\n    a way that they are expanded only if they are typed as the first word of\r\n    a command (at \":\" prompt). The same rules that apply to creating a\r\n    :cabbr apply to the second argument of CmdAlias() function too. You can\r\n    pass in optional flags (such as <buffer>) to the :cabbr command through\r\n    the third argument.\r\n  - The :cabbr's created this way, work like the bash aliases, except that\r\n    in this case, the alias is substituted in-place followed by the rules\r\n    mentioned in the |abbreviations|, and no arguments can be defined.\r\nDrawbacks:\r\n  - If the <rhs> is not of the same size as <lhs>, the in-place expansion\r\n    feels odd.\r\n  - Since the expansion is in-place, Vim command-line history saves the\r\n    <rhs>, not the <lhs>. This means, you can't retrieve a command from\r\n    history by partially typing the <lhs> (you have to instead type the\r\n    <rhs> for this purpose).\r\n\r\n\r\n\r\nSearch_key_words: cmdalias Hari Krishna Dara cmap alias cmdalias.vim","4":"Sometimes we want to to change the behavior of a built-in command so end up creating a custom command, and we wish to reuse the built-in command name for it. E.g., :Runtime to replace :runtime, :Find to replace :find. I myself wanted to replace :qa with :QA (see http:\/\/vim.wikia.com\/wiki\/Tabclose_instead_of_quit-all), but it is hard to remember to type :QA instead of :qa everytime, that is why I created this plugin.\r\n\r\nThis plugin is just a wrapper on top of command-line abbreviations (:cabbr), to work around the big disadvantages of :cabbr. With plain :cabbr, the expansion happens anywhere the abbreviation appears while typing command-line. E.g., if you create abbreviation from runtime->Runtime, then the following will not work as you expect:\r\n\r\n:cnoreabbr runtime Runtime\r\n:%s\/runtime\/runduration\/g\r\n\r\nWhat would actually execute is:\r\n\r\n:%s\/Runtime\/runduration\/g\r\n\r\nWhich is not the same. The other problem is cabbr's trigger not only at the command-line, but also at search prompt, at the input prompt and any other prompts (see :help getcmdtype()). To avoid those unexpected expansions, cmdalias utilizes a light-weight wrapper function that expands the abbreviation only when it is typed as the first word of the ex command (\":\" prompt). So, instead of the below:\r\n\r\n:cnoreabbr runtime Runtime\r\n\r\nYou would use this:\r\n\r\n:call CmdAlias('runtime', 'Runtime')\r\n\r\nor simply,\r\n\r\n:Alias runtime Runtime\r\n\r\nThese aliases pretty much work like the bash aliases. If you don't want the expansion to temporarily happen even at the beginning of a command, you have two options:\r\n- After entering the command and before typing the next command press <C-V> (e.g., <C-V><Space>)\r\n- Start the command-line with a space and then enter the command.\r\n\r\nThe CmdAlias() function takes a 3rd optional argument called \"flags\" for which you can pass options such as \"<buffer>\" to make the alias local to the current buffer.\r\n\r\nHere is the description from file header for more details:\r\nUsage:\r\n    :call CmdAlias('<lhs>', '<rhs>', [flags])\r\n    or\r\n    :Alias <lhs> <rhs> [flags]\r\n                                                                             \r\n    :UnAlias <lhs> ...\r\n    :Aliases [<lhs> ...]\r\n                                                                             \r\nEx:\r\n    :Alias runtime Runtime\r\n    :Alias find Find\r\n    :Aliases\r\n    :UnAlias find\r\n                                                                             \r\nDescription:\r\n  - Vim doesn't allow us to create user-defined commands unless they start\r\n    with an uppercase letter. I find this annoying and constrained when it\r\n    comes to overriding built-in commands with my own. To override built-in\r\n    commands, we often have to create a new command that has the same name\r\n    as the built-in but starting with an uppercase letter (e.g., \"Cd\"\r\n    instead of \"cd\"), and remember to use that everytime (besides the\r\n    fact that typing uppercase letters take more effort). An alternative is\r\n    to use the :cabbr to create an abbreviation for the built-in command\r\n    (:cmap is not good) to the user-defined command (e.g., \"cabbr cd Cd\").\r\n    But this would generally cause more inconvenience because the\r\n    abbreviation gets expanded no matter where in the command-line you use\r\n    it. This is where the plugin comes to your rescue by arranging the cabbr\r\n    to expand only if typed as the first word in the command-line, in a\r\n    sense working like the aliases in csh or bash.\r\n  - The plugin provides a function to define command-line abbreviations such\r\n    a way that they are expanded only if they are typed as the first word of\r\n    a command (at \":\" prompt). The same rules that apply to creating a\r\n    :cabbr apply to the second argument of CmdAlias() function too. You can\r\n    pass in optional flags (such as <buffer>) to the :cabbr command through\r\n    the third argument.\r\n  - The :cabbr's created this way, work like the bash aliases, except that\r\n    in this case, the alias is substituted in-place followed by the rules\r\n    mentioned in the |abbreviations|, and no arguments can be defined.\r\nDrawbacks:\r\n  - If the <rhs> is not of the same size as <lhs>, the in-place expansion\r\n    feels odd.\r\n  - Since the expansion is in-place, Vim command-line history saves the\r\n    <rhs>, not the <lhs>. This means, you can't retrieve a command from\r\n    history by partially typing the <lhs> (you have to instead type the\r\n    <rhs> for this purpose).\r\n\r\n\r\n\r\nSearch_key_words: cmdalias Hari Krishna Dara cmap alias cmdalias.vim","install_details":"Source it from your vimrc or just drop it in your plugin directory.\r\n\r\nFor versions prior to 2.0:\r\nRequires curcmdmode.vim(1.0) (vimscript #745). ","5":"Source it from your vimrc or just drop it in your plugin directory.\r\n\r\nFor versions prior to 2.0:\r\nRequires curcmdmode.vim(1.0) (vimscript #745). ","first_name":"Hari Krishna","6":"Hari Krishna","last_name":"Dara","7":"Dara","releases":[{"0":"746","vim_version":"7.0","1":"7.0","script_version":"3.0","2":"3.0","version_comment":"Improvements due to renewed interest in the plugin.\r\n- Added Alias command that is easier to use than calling CmdAlias()\r\n  function.\r\n- Added UnAlias and Aliases commands to give a more authentic \"alias\"\r\n  like feel to the plugin.\r\n- Detect aliases after certain configurable commands. The default\r\n  commands are: verbose, debug, silent, redir.\r\n- Better usage error detection.","3":"Improvements due to renewed interest in the plugin.\r\n- Added Alias command that is easier to use than calling CmdAlias()\r\n  function.\r\n- Added UnAlias and Aliases commands to give a more authentic \"alias\"\r\n  like feel to the plugin.\r\n- Detect aliases after certain configurable commands. The default\r\n  commands are: verbose, debug, silent, redir.\r\n- Better usage error detection.","package":"cmdalias.vim","4":"cmdalias.vim","src_id":"11356","5":"11356","creation_date":"1252607479","6":"1252607479"},{"0":"746","vim_version":"7.0","1":"7.0","script_version":"2.0","2":"2.0","version_comment":"Release 2.0 for Vim 7.0. Essentially have rewritten the plugin for Vim\r\n7.0. Now the plugin is very simple safe and reliable and doesn't even\r\ndepend on any other plugins (thanks to the new getcmdtype() function).\r\nAlso added support for passing additional flags to the CmdAlias()\r\nfunction.\r\n","3":"Release 2.0 for Vim 7.0. Essentially have rewritten the plugin for Vim\r\n7.0. Now the plugin is very simple safe and reliable and doesn't even\r\ndepend on any other plugins (thanks to the new getcmdtype() function).\r\nAlso added support for passing additional flags to the CmdAlias()\r\nfunction.\r\n","package":"cmdalias.vim","4":"cmdalias.vim","src_id":"5662","5":"5662","creation_date":"1147112020","6":"1147112020"},{"0":"746","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"cmdalias.vim","4":"cmdalias.vim","src_id":"2267","5":"2267","creation_date":"1061830730","6":"1061830730"}]},"745":{"script_id":"745","0":"745","script_name":"curcmdmode","1":"curcmdmode","script_type":"utility","2":"utility","summary":"*obsolete* Script library to extend the notion of Vim's mode() function","3":"*obsolete* Script library to extend the notion of Vim's mode() function","description":"This plugin has no value in Vim7 since it has a new built-in function called getcmdtype().\r\n\r\nThis plugin provides a small library of functions and mappings and a framework to extend Vim's command-line mode in a way that is not possible by using Vim's built-in features alone.\r\n\r\nThis was originally part of the chcmdmode.vim plugin, but I have extracted the generic part out and created this new plugin which can be shared by multiple scripts. For description and usage please see the script header.\r\n","4":"This plugin has no value in Vim7 since it has a new built-in function called getcmdtype().\r\n\r\nThis plugin provides a small library of functions and mappings and a framework to extend Vim's command-line mode in a way that is not possible by using Vim's built-in features alone.\r\n\r\nThis was originally part of the chcmdmode.vim plugin, but I have extracted the generic part out and created this new plugin which can be shared by multiple scripts. For description and usage please see the script header.\r\n","install_details":"Source it from your vimrc or just drop it in your plugin directory.\r\n\r\nRequires genutils.vim(1.7), (vimscript #197)","5":"Source it from your vimrc or just drop it in your plugin directory.\r\n\r\nRequires genutils.vim(1.7), (vimscript #197)","first_name":"Hari Krishna","6":"Hari Krishna","last_name":"Dara","7":"Dara","releases":[{"0":"745","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"curcmdmode.vim","4":"curcmdmode.vim","src_id":"2266","5":"2266","creation_date":"1061830710","6":"1061830710"}]},"744":{"script_id":"744","0":"744","script_name":"dhcpd.vim","1":"dhcpd.vim","script_type":"syntax","2":"syntax","summary":"syntax highligting for dhcpd.conf","3":"syntax highligting for dhcpd.conf","description":"dhcpd.vim provides syntax highlighting for ISC DHCP server configuration files dhcpd.conf.","4":"dhcpd.vim provides syntax highlighting for ISC DHCP server configuration files dhcpd.conf.","install_details":"","5":"","first_name":"David","6":"David","last_name":"Necas","7":"Necas","releases":[{"0":"744","vim_version":"5.7","1":"5.7","script_version":"20030825","2":"20030825","version_comment":"Initial upload","3":"Initial upload","package":"dhcpd.vim","4":"dhcpd.vim","src_id":"2261","5":"2261","creation_date":"1061819853","6":"1061819853"}]},"743":{"script_id":"743","0":"743","script_name":"svn.vim","1":"svn.vim","script_type":"utility","2":"utility","summary":"A simple svn utility for vim.","3":"A simple svn utility for vim.","description":"A simple utility for using SVN within vim.  Mostly just aliases for combining writing your file, commiting and updating your repository within vim.  I use gvim, so the default editor ``Commit'' or ``Svn commit'' doesn't work.  For this reason, with a little bit of trickery I made my system open up the log addition inline.  This means with two simple commands, you've written your current file, commited your repository, and updated your changes...without leaving your vim window :)\r\n\r\nYou can also do this with key mappings, so makes it even easier.\r\n\r\nIts still somewhat primative, though its coming along.\r\nCheck back frequently for updates.\r\nSuggestions and Patches are always welcome!\r\n\r\nHappy Vimming!","4":"A simple utility for using SVN within vim.  Mostly just aliases for combining writing your file, commiting and updating your repository within vim.  I use gvim, so the default editor ``Commit'' or ``Svn commit'' doesn't work.  For this reason, with a little bit of trickery I made my system open up the log addition inline.  This means with two simple commands, you've written your current file, commited your repository, and updated your changes...without leaving your vim window :)\r\n\r\nYou can also do this with key mappings, so makes it even easier.\r\n\r\nIts still somewhat primative, though its coming along.\r\nCheck back frequently for updates.\r\nSuggestions and Patches are always welcome!\r\n\r\nHappy Vimming!","install_details":"cd ~\/.vim\r\ntar zxvf svn-<version>.tgz\r\n","5":"cd ~\/.vim\r\ntar zxvf svn-<version>.tgz\r\n","first_name":"Scott","6":"Scott","last_name":"McCoy","7":"McCoy","releases":[{"0":"743","vim_version":"6.0","1":"6.0","script_version":"0.003002","2":"0.003002","version_comment":"Just a bug fix.  \\\\l (:Svn log) was running through 'windo' (oops)","3":"Just a bug fix.  \\\\l (:Svn log) was running through 'windo' (oops)","package":"svn-vim-0.003002.tgz","4":"svn-vim-0.003002.tgz","src_id":"2305","5":"2305","creation_date":"1062816475","6":"1062816475"},{"0":"743","vim_version":"6.0","1":"6.0","script_version":"0.003001","2":"0.003001","version_comment":"Fixed an ugly bug that made it not play well with other plugins :)","3":"Fixed an ugly bug that made it not play well with other plugins :)","package":"svn-vim-0.003001.tgz","4":"svn-vim-0.003001.tgz","src_id":"2289","5":"2289","creation_date":"1062352603","6":"1062352603"},{"0":"743","vim_version":"6.0","1":"6.0","script_version":"0.003","2":"0.003","version_comment":"Added Documentation, fixed a few minor glitches, added Key Mappings...still waiting for feedback from people on more things this needs.","3":"Added Documentation, fixed a few minor glitches, added Key Mappings...still waiting for feedback from people on more things this needs.","package":"svn-vim-0.003.tgz","4":"svn-vim-0.003.tgz","src_id":"2286","5":"2286","creation_date":"1062281587","6":"1062281587"},{"0":"743","vim_version":"6.0","1":"6.0","script_version":"0.002","2":"0.002","version_comment":"the \"SVN commit\" and Commit methods now open up a window inline, manually fetching the repository status and generating a little file exactly like the one svn generates, then a new 'Complete' command was added that wraps a small sh script around the commit information you provided, which is then given to svn commit as the editor, and then removed.  The window is then closed, and its all done quietly.  I also added 'Svn log' and 'Log' commands that open up the log in a new window and move your cursor to the top :)  This thing is almost cool now","3":"the \"SVN commit\" and Commit methods now open up a window inline, manually fetching the repository status and generating a little file exactly like the one svn generates, then a new 'Complete' command was added that wraps a small sh script around the commit information you provided, which is then given to svn commit as the editor, and then removed.  The window is then closed, and its all done quietly.  I also added 'Svn log' and 'Log' commands that open up the log in a new window and move your cursor to the top :)  This thing is almost cool now","package":"svn.vim","4":"svn.vim","src_id":"2280","5":"2280","creation_date":"1062130326","6":"1062130326"},{"0":"743","vim_version":"6.0","1":"6.0","script_version":"0.001003","2":"0.001003","version_comment":"Added 'Add' keyword and handler.\r\nSome other stuff I forget...maybe I should put this thing under svn :)","3":"Added 'Add' keyword and handler.\r\nSome other stuff I forget...maybe I should put this thing under svn :)","package":"svn.vim","4":"svn.vim","src_id":"2279","5":"2279","creation_date":"1062117512","6":"1062117512"},{"0":"743","vim_version":"6.0","1":"6.0","script_version":"0.001001","2":"0.001001","version_comment":"Fixed a little bug where I should have been using a global variable and the only reason it worked without the global was my version of vim :-\/  Sorry guys.","3":"Fixed a little bug where I should have been using a global variable and the only reason it worked without the global was my version of vim :-\/  Sorry guys.","package":"svn.vim","4":"svn.vim","src_id":"2260","5":"2260","creation_date":"1061801307","6":"1061801307"},{"0":"743","vim_version":"6.0","1":"6.0","script_version":"0.001","2":"0.001","version_comment":"Initial upload","3":"Initial upload","package":"svn.vim","4":"svn.vim","src_id":"2259","5":"2259","creation_date":"1061764376","6":"1061764376"}]},"742":{"script_id":"742","0":"742","script_name":"SwapHeader","1":"SwapHeader","script_type":"utility","2":"utility","summary":"This script allows to switch between source and header files.","3":"This script allows to switch between source and header files.","description":"This script allows to switch between source and header files.","4":"This script allows to switch between source and header files.","install_details":"Copy swapheader.vim to your plugins directory. To switch between source \r\n and header files type ':call SwapHeaderFile(0)' or press <C-F6> if you like open file in same window, if you like open file in vertically split window type  ':call SwapHeaderFile(1)' or <C-S-F6>.\r\n\r\nGlobal Configuration Variables:\r\n    defaultHeaderExtension : Sets header extension, by default '\\\\.h'.\r\n    defaultSourceExtension : Sets source extension, by default '\\\\.cpp'.\r\n    enableSwapHeaderMap : If it's equal to 1, keymapping for <C-F6> and <C-S-F6> is enabled, otherwise it's disabled, by default 1.\r\n","5":"Copy swapheader.vim to your plugins directory. To switch between source \r\n and header files type ':call SwapHeaderFile(0)' or press <C-F6> if you like open file in same window, if you like open file in vertically split window type  ':call SwapHeaderFile(1)' or <C-S-F6>.\r\n\r\nGlobal Configuration Variables:\r\n    defaultHeaderExtension : Sets header extension, by default '\\\\.h'.\r\n    defaultSourceExtension : Sets source extension, by default '\\\\.cpp'.\r\n    enableSwapHeaderMap : If it's equal to 1, keymapping for <C-F6> and <C-S-F6> is enabled, otherwise it's disabled, by default 1.\r\n","first_name":"Evgeny","6":"Evgeny","last_name":"Podjachev","7":"Podjachev","releases":[{"0":"742","vim_version":"6.0","1":"6.0","script_version":"1.0.0","2":"1.0.0","version_comment":"Initial upload","3":"Initial upload","package":"swapheader.vim","4":"swapheader.vim","src_id":"2255","5":"2255","creation_date":"1061612620","6":"1061612620"}]},"741":{"script_id":"741","0":"741","script_name":"movewin.vim","1":"movewin.vim","script_type":"utility","2":"utility","summary":"Move GUI window using the keyboard","3":"Move GUI window using the keyboard","description":"Move GUI window using the keyboard, for those who don't like to use the mouse.\r\n\r\nAfter loading the script, call :MoveWin.  Use hjkl and shift+hjkl keys to move the window, press any other key when done.","4":"Move GUI window using the keyboard, for those who don't like to use the mouse.\r\n\r\nAfter loading the script, call :MoveWin.  Use hjkl and shift+hjkl keys to move the window, press any other key when done.","install_details":"Add script to plugin directory, or :source script.  :MoveWin to use","5":"Add script to plugin directory, or :source script.  :MoveWin to use","first_name":"Don","6":"Don","last_name":"Yang","7":"Yang","releases":[{"0":"741","vim_version":"6.0","1":"6.0","script_version":"1.01","2":"1.01","version_comment":"redraw title when lazyredraw is not set (after patch 6.2.440)","3":"redraw title when lazyredraw is not set (after patch 6.2.440)","package":"movewin.vim","4":"movewin.vim","src_id":"2914","5":"2914","creation_date":"1081165490","6":"1081165490"},{"0":"741","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"movewin.vim","4":"movewin.vim","src_id":"2254","5":"2254","creation_date":"1061594960","6":"1061594960"}]},"740":{"script_id":"740","0":"740","script_name":"sbutils","1":"sbutils","script_type":"utility","2":"utility","summary":"Some utilities I find useful","3":"Some utilities I find useful","description":"This is a collection of utilities that i will be updating regularly. I'm putting it online just in case somebody wants exactly what's there, if you're just browsing, you should probably skip this version.\r\n\r\nStarting with 2 utils:\r\n\r\n1. Count the no. of occurences of a -PERL- regex in a range ( :<range>Count <regex>)\r\n2. Insert a timestamp, formatted according to a time-format string at the current cursor position in the command mode ( <Leader>t) where <Leader> is usually '\\'\r\n3. Comment a block of C-code by selecting a range and hitting <Leader>C - it replaces \/* and *\/ inside with {{{ and }}} to cope with nested comments.\r\n\r\n","4":"This is a collection of utilities that i will be updating regularly. I'm putting it online just in case somebody wants exactly what's there, if you're just browsing, you should probably skip this version.\r\n\r\nStarting with 2 utils:\r\n\r\n1. Count the no. of occurences of a -PERL- regex in a range ( :<range>Count <regex>)\r\n2. Insert a timestamp, formatted according to a time-format string at the current cursor position in the command mode ( <Leader>t) where <Leader> is usually '\\'\r\n3. Comment a block of C-code by selecting a range and hitting <Leader>C - it replaces \/* and *\/ inside with {{{ and }}} to cope with nested comments.\r\n\r\n","install_details":"Source from ~\/.vimrc (:source sb.vim)","5":"Source from ~\/.vimrc (:source sb.vim)","first_name":"sapan","6":"sapan","last_name":"bhatia","7":"bhatia","releases":[{"0":"740","vim_version":"6.0","1":"6.0","script_version":"0.11","2":"0.11","version_comment":"New util:\r\nTo select a range and put it within C comments, replacing internal \/* and *\/ with {{{ and }}} to cope with nesting (well, i find it useful:)","3":"New util:\r\nTo select a range and put it within C comments, replacing internal \/* and *\/ with {{{ and }}} to cope with nesting (well, i find it useful:)","package":"sb.vim","4":"sb.vim","src_id":"2258","5":"2258","creation_date":"1061715932","6":"1061715932"},{"0":"740","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"sb.vim","4":"sb.vim","src_id":"2251","5":"2251","creation_date":"1061534711","6":"1061534711"}]},"739":{"script_id":"739","0":"739","script_name":"yaml.vim","1":"yaml.vim","script_type":"color scheme","2":"color scheme","summary":"Syntax coloring and functions for YAML","3":"Syntax coloring and functions for YAML","description":"A wonderful syntax coloring script for http:\/\/yaml.org by Igor Vergeichik <iverg@mail.ru>\n","4":"A wonderful syntax coloring script for http:\/\/yaml.org by Igor Vergeichik <iverg@mail.ru>\n","install_details":"Save the file in ~\/.vim\/yaml.vim\nAdd the following line to your .vimrc\n\n    au BufNewFile,BufRead *.yaml,*.yml so ~\/.vim\/yaml.vim","5":"Save the file in ~\/.vim\/yaml.vim\nAdd the following line to your .vimrc\n\n    au BufNewFile,BufRead *.yaml,*.yml so ~\/.vim\/yaml.vim","first_name":"Clark","6":"Clark","last_name":"Evans","7":"Evans","releases":[{"0":"739","vim_version":"6.0","1":"6.0","script_version":".1","2":".1","version_comment":"Initial upload","3":"Initial upload","package":"yaml.vim","4":"yaml.vim","src_id":"2249","5":"2249","creation_date":"1061458090","6":"1061458090"}]},"738":{"script_id":"738","0":"738","script_name":"gor.vim","1":"gor.vim","script_type":"color scheme","2":"color scheme","summary":"Green-Orangish Colorscheme","3":"Green-Orangish Colorscheme","description":"As u all know what to do.","4":"As u all know what to do.","install_details":"Put it in one of your colors directories.\r\n  ex. $HOME\/.vim\/colors\/\r\n  ex. $HOME\\vimfiles\\colors\\\r\n  ex. $VIM\\vimfiles\\colors\\\r\nThen, just do :colorscheme gor ","5":"Put it in one of your colors directories.\r\n  ex. $HOME\/.vim\/colors\/\r\n  ex. $HOME\\vimfiles\\colors\\\r\n  ex. $VIM\\vimfiles\\colors\\\r\nThen, just do :colorscheme gor ","first_name":"jokes","6":"jokes","last_name":"us","7":"us","releases":[{"0":"738","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"gor.vim","4":"gor.vim","src_id":"2245","5":"2245","creation_date":"1061422817","6":"1061422817"}]},"737":{"script_id":"737","0":"737","script_name":"mdl.vim","1":"mdl.vim","script_type":"syntax","2":"syntax","summary":"Syntax hilighting for the PRESPEC language","3":"Syntax hilighting for the PRESPEC language","description":"Prespec is a declarative language for program specialization. This file contains syntax hilighting\r\nrules for it.","4":"Prespec is a declarative language for program specialization. This file contains syntax hilighting\r\nrules for it.","install_details":"","5":"","first_name":"sapan","6":"sapan","last_name":"bhatia","7":"bhatia","releases":[{"0":"737","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"mdl.vim","4":"mdl.vim","src_id":"2244","5":"2244","creation_date":"1061303899","6":"1061303899"}]},"736":{"script_id":"736","0":"736","script_name":"kickstart.vim","1":"kickstart.vim","script_type":"syntax","2":"syntax","summary":"Syntax highlighting for RedHat kickstart files","3":"Syntax highlighting for RedHat kickstart files","description":"kickstart.vim provides syntax highlighting for RedHat Linux kickstart configuration files.","4":"kickstart.vim provides syntax highlighting for RedHat Linux kickstart configuration files.","install_details":"","5":"","first_name":"David","6":"David","last_name":"Necas","7":"Necas","releases":[{"0":"736","vim_version":"5.7","1":"5.7","script_version":"20100210","2":"20100210","version_comment":"%pre and %post are highlighted using sh syntax","3":"%pre and %post are highlighted using sh syntax","package":"kickstart.vim","4":"kickstart.vim","src_id":"12351","5":"12351","creation_date":"1265798066","6":"1265798066"},{"0":"736","vim_version":"5.7","1":"5.7","script_version":"20030723","2":"20030723","version_comment":"Initial upload","3":"Initial upload","package":"kickstart.vim","4":"kickstart.vim","src_id":"2239","5":"2239","creation_date":"1061209822","6":"1061209822"}]},"735":{"script_id":"735","0":"735","script_name":"pam.vim","1":"pam.vim","script_type":"syntax","2":"syntax","summary":"Syntax highlighting for PAM (Pluggable Authentication Modules)","3":"Syntax highlighting for PAM (Pluggable Authentication Modules)","description":"pam.vim provides syntax highlighting for Linux-PAM (Pluggable Authentication Modules) configuration files.","4":"pam.vim provides syntax highlighting for Linux-PAM (Pluggable Authentication Modules) configuration files.","install_details":"","5":"","first_name":"David","6":"David","last_name":"Necas","7":"Necas","releases":[{"0":"735","vim_version":"5.7","1":"5.7","script_version":"20060424","2":"20060424","version_comment":"`include' keyword was added and some pam module options were updated.","3":"`include' keyword was added and some pam module options were updated.","package":"pam.vim","4":"pam.vim","src_id":"5601","5":"5601","creation_date":"1145873780","6":"1145873780"},{"0":"735","vim_version":"5.7","1":"5.7","script_version":"20030818","2":"20030818","version_comment":"Initial upload","3":"Initial upload","package":"pam.vim","4":"pam.vim","src_id":"2238","5":"2238","creation_date":"1061209554","6":"1061209554"}]},"734":{"script_id":"734","0":"734","script_name":"sql.vim","1":"sql.vim","script_type":"syntax","2":"syntax","summary":"Oracle 9i Syntax highlighting (SQL, SQL+)","3":"Oracle 9i Syntax highlighting (SQL, SQL+)","description":"This is a drop-in for the original sql.vim file delivered with vim 6.2. It should do highlighting of all documented Oracle 9iR2  SQL commands\/keywords and SQL+ commands. \r\nPL\/SQL blocks within a SQL file will be marked as one uniform block without further highlighting. \r\nI tried to stick to the Oracle Documentation concerning keywords and commands as far as possible, so not everything you would expect to be a keyword is one (e.g. DUAL).\r\n","4":"This is a drop-in for the original sql.vim file delivered with vim 6.2. It should do highlighting of all documented Oracle 9iR2  SQL commands\/keywords and SQL+ commands. \r\nPL\/SQL blocks within a SQL file will be marked as one uniform block without further highlighting. \r\nI tried to stick to the Oracle Documentation concerning keywords and commands as far as possible, so not everything you would expect to be a keyword is one (e.g. DUAL).\r\n","install_details":"put this file (sql.vim) into <vimdirectory>\/syntax\/ or ~\/.vim\/syntax ","5":"put this file (sql.vim) into <vimdirectory>\/syntax\/ or ~\/.vim\/syntax ","first_name":"Johannes","6":"Johannes","last_name":"Gritsch","7":"Gritsch","releases":[{"0":"734","vim_version":"6.0","1":"6.0","script_version":"0.2.1","2":"0.2.1","version_comment":"2003-08-25      repaired minor glitches, added \"create global temporary table\"\r\n2003-08-25      some simplifications to reduce length of file (still 10k!)\r\n","3":"2003-08-25      repaired minor glitches, added \"create global temporary table\"\r\n2003-08-25      some simplifications to reduce length of file (still 10k!)\r\n","package":"sql.vim","4":"sql.vim","src_id":"2284","5":"2284","creation_date":"1062231643","6":"1062231643"},{"0":"734","vim_version":"6.0","1":"6.0","script_version":"0.2","2":"0.2","version_comment":"minor bug fixes:\r\n2003-08-18      parsing of SQL+ commands: lines ending with \"-\\s*\" accepted as continuation lines\r\n2003-08-18      not everything starting with \":\" is a bind variable\r\n2003-08-18      `with' has to be treated as a statement\r\n2003-09-19      handling of splitted commands is correct (hopefully)","3":"minor bug fixes:\r\n2003-08-18      parsing of SQL+ commands: lines ending with \"-\\s*\" accepted as continuation lines\r\n2003-08-18      not everything starting with \":\" is a bind variable\r\n2003-08-18      `with' has to be treated as a statement\r\n2003-09-19      handling of splitted commands is correct (hopefully)","package":"sql.vim","4":"sql.vim","src_id":"2242","5":"2242","creation_date":"1061276995","6":"1061276995"}]},"733":{"script_id":"733","0":"733","script_name":"quicksession.vim","1":"quicksession.vim","script_type":"utility","2":"utility","summary":"Easily switch between a multitude of session files","3":"Easily switch between a multitude of session files","description":"QuickSession is a plugin which allows you to switch quickly\r\nbetween your vim session files. When you organized your whole work by creating a number of vim session files (by :mks)\r\nthis plugin can save you some time. This pluign allows you\r\nto change the sessions inside one vim instance. Before using this plugin you must create a meta session file which contains  \r\nreferences to all your session files. Once you have created this you can edit this file later on by the plugin itself. Refer to the usage description section inside the plugin.\r\nYou start the plugin by pressing \\qq or by entering the command :QuickSession.","4":"QuickSession is a plugin which allows you to switch quickly\r\nbetween your vim session files. When you organized your whole work by creating a number of vim session files (by :mks)\r\nthis plugin can save you some time. This pluign allows you\r\nto change the sessions inside one vim instance. Before using this plugin you must create a meta session file which contains  \r\nreferences to all your session files. Once you have created this you can edit this file later on by the plugin itself. Refer to the usage description section inside the plugin.\r\nYou start the plugin by pressing \\qq or by entering the command :QuickSession.","install_details":"Simple copy the file into your private plugin directory.","5":"Simple copy the file into your private plugin directory.","first_name":"Johann","6":"Johann","last_name":"Pfefferl","7":"Pfefferl","releases":[{"0":"733","vim_version":"6.0","1":"6.0","script_version":"1.6","2":"1.6","version_comment":"Initial upload","3":"Initial upload","package":"quicksession.vim","4":"quicksession.vim","src_id":"2226","5":"2226","creation_date":"1060663270","6":"1060663270"}]},"732":{"script_id":"732","0":"732","script_name":"folddigest.vim","1":"folddigest.vim","script_type":"utility","2":"utility","summary":"Show fold digest tree view.","3":"Show fold digest tree view.","description":"Required: Vim 6.2\r\n\r\nUsage:\r\n        :call FoldDigest()\r\n\r\n    Transform all folds in the current buffer into digest tree form, and\r\n    show it in another buffer.  The buffer is called FOLDDIGEST.  It shows\r\n    not only all fold start positions, but also a tree depended on original\r\n    folds hierarchy.\r\n\r\n    In a FOLDDIGEST, you can move around the cursor, and when type <CR> jump\r\n    to fold at under it.  If you enter FOLDDIGEST window from other windows,\r\n    when depended buffer is availabeled, it will be synchronized\r\n    automatically.  If you want to force synchronize, type \"r\" in a\r\n    FOLDDIGEST buffer.\r\n\r\nOptions:\r\n\r\n    'folddigest_options'\r\n                string (default \"\")\r\n        Set string flag which you need.  If you want to use more than two,\r\n        join by comma.\r\n\r\n          flexnumwidth  Narrow line number width as possible.\r\n          nofoldclose   don't close folds after \":call FoldDigest()\".\r\n          vertical      Use :vsplit for FOLDDIGEST. (default :split)\r\n\r\n    'folddigest_size'\r\n                number (default 0)\r\n        FOLDDIGEST window size.  When 'folddigest_options' has \"vertical\"\r\n        flag, this value is interpretted as window height, and doesn't then\r\n        as window width.  If zero was specified height\/width become half of\r\n        current window.\r\n\r\n    ex:\r\n        :let folddigest_options = \"vertical,flexnumwidth\"\r\n        :let folddigest_size = 30","4":"Required: Vim 6.2\r\n\r\nUsage:\r\n        :call FoldDigest()\r\n\r\n    Transform all folds in the current buffer into digest tree form, and\r\n    show it in another buffer.  The buffer is called FOLDDIGEST.  It shows\r\n    not only all fold start positions, but also a tree depended on original\r\n    folds hierarchy.\r\n\r\n    In a FOLDDIGEST, you can move around the cursor, and when type <CR> jump\r\n    to fold at under it.  If you enter FOLDDIGEST window from other windows,\r\n    when depended buffer is availabeled, it will be synchronized\r\n    automatically.  If you want to force synchronize, type \"r\" in a\r\n    FOLDDIGEST buffer.\r\n\r\nOptions:\r\n\r\n    'folddigest_options'\r\n                string (default \"\")\r\n        Set string flag which you need.  If you want to use more than two,\r\n        join by comma.\r\n\r\n          flexnumwidth  Narrow line number width as possible.\r\n          nofoldclose   don't close folds after \":call FoldDigest()\".\r\n          vertical      Use :vsplit for FOLDDIGEST. (default :split)\r\n\r\n    'folddigest_size'\r\n                number (default 0)\r\n        FOLDDIGEST window size.  When 'folddigest_options' has \"vertical\"\r\n        flag, this value is interpretted as window height, and doesn't then\r\n        as window width.  If zero was specified height\/width become half of\r\n        current window.\r\n\r\n    ex:\r\n        :let folddigest_options = \"vertical,flexnumwidth\"\r\n        :let folddigest_size = 30","install_details":"Put the file at one of your plugin directories. \r\n  ex. $HOME\/.vim\/plugin\/ \r\n  ex. $HOME\\vimfiles\\plugin\\ \r\n  ex. $VIM\\vimfiles\\plugin\\","5":"Put the file at one of your plugin directories. \r\n  ex. $HOME\/.vim\/plugin\/ \r\n  ex. $HOME\\vimfiles\\plugin\\ \r\n  ex. $VIM\\vimfiles\\plugin\\","first_name":"Taro","6":"Taro","last_name":"MURAOKA","7":"MURAOKA","releases":[{"0":"732","vim_version":"6.0","1":"6.0","script_version":"1.0.1","2":"1.0.1","version_comment":"Fix some bugs, and remove obsoleted code.","3":"Fix some bugs, and remove obsoleted code.","package":"folddigest.vim","4":"folddigest.vim","src_id":"2230","5":"2230","creation_date":"1060763333","6":"1060763333"}]},"731":{"script_id":"731","0":"731","script_name":"xmidas.vim","1":"xmidas.vim","script_type":"syntax","2":"syntax","summary":"Color syntax highlighting within VIM for the X-Midas language.","3":"Color syntax highlighting within VIM for the X-Midas language.","description":"Color syntax highlighting within VIM for the X-Midas language.","4":"Color syntax highlighting within VIM for the X-Midas language.","install_details":"Add to your syntax subdir and :so(urce) it after opening an X-Midas macro file.","5":"Add to your syntax subdir and :so(urce) it after opening an X-Midas macro file.","first_name":"Lance","6":"Lance","last_name":"Luvaul","7":"Luvaul","releases":[{"0":"731","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"xmidas.vim","4":"xmidas.vim","src_id":"2219","5":"2219","creation_date":"1060506088","6":"1060506088"}]},"730":{"script_id":"730","0":"730","script_name":"co.vim","1":"co.vim","script_type":"ftplugin","2":"ftplugin","summary":"\"Aspect Oriented\" script: Comment out a hunk of text in many languages","3":"\"Aspect Oriented\" script: Comment out a hunk of text in many languages","description":"This script creates a mapping, ;co, which will comment out a hunk\r\nof about 20 differant file types.\r\n\r\nIt's primitive, but I like it.\r\n\r\n","4":"This script creates a mapping, ;co, which will comment out a hunk\r\nof about 20 differant file types.\r\n\r\nIt's primitive, but I like it.\r\n\r\n","install_details":"put it in your script dir.\r\n","5":"put it in your script dir.\r\n","first_name":"rich","6":"rich","last_name":"paul","7":"paul","releases":[{"0":"730","vim_version":"6.0","1":"6.0","script_version":"2.0","2":"2.0","version_comment":"Added a few more file types.\r\n","3":"Added a few more file types.\r\n","package":"co.vim","4":"co.vim","src_id":"3478","5":"3478","creation_date":"1095961445","6":"1095961445"},{"0":"730","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"co.vim","4":"co.vim","src_id":"2214","5":"2214","creation_date":"1060257113","6":"1060257113"}]},"729":{"script_id":"729","0":"729","script_name":"sudo.vim","1":"sudo.vim","script_type":"utility","2":"utility","summary":"Allows one to edit a file with privileges from an unprivileged session.","3":"Allows one to edit a file with privileges from an unprivileged session.","description":"\"   sudo.vim:  A vim plugin by Rich Paul (vim@rich-paul.net)\r\n\"\r\n\"   This script eases use of vim with sudo by adding the ability to\r\n\"   edit one file with root privileges without running the whole\r\n\"   session that way.\r\n\"\r\n\"   Usage:  put it in the plugin directory, and\r\n\"       (command line): vim sudo:\/etc\/passwd\r\n\"       (within vim):   :e sudo:\/etc\/passwd\r\n\"\r\n\"   sudo will ask for your password if need be.\r\n\"\r\n","4":"\"   sudo.vim:  A vim plugin by Rich Paul (vim@rich-paul.net)\r\n\"\r\n\"   This script eases use of vim with sudo by adding the ability to\r\n\"   edit one file with root privileges without running the whole\r\n\"   session that way.\r\n\"\r\n\"   Usage:  put it in the plugin directory, and\r\n\"       (command line): vim sudo:\/etc\/passwd\r\n\"       (within vim):   :e sudo:\/etc\/passwd\r\n\"\r\n\"   sudo will ask for your password if need be.\r\n\"\r\n","install_details":"\"   Usage:  put it in the plugin directory, and\r\n","5":"\"   Usage:  put it in the plugin directory, and\r\n","first_name":"rich","6":"rich","last_name":"paul","7":"paul","releases":[{"0":"729","vim_version":"6.0","1":"6.0","script_version":"2.0","2":"2.0","version_comment":"removed \"'echo hi'\" from the script.\r\n","3":"removed \"'echo hi'\" from the script.\r\n","package":"sudo.vim","4":"sudo.vim","src_id":"3477","5":"3477","creation_date":"1095960929","6":"1095960929"},{"0":"729","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"sudo.vim","4":"sudo.vim","src_id":"2213","5":"2213","creation_date":"1060255667","6":"1060255667"}]},"728":{"script_id":"728","0":"728","script_name":"Hanoi Tower","1":"Hanoi Tower","script_type":"game","2":"game","summary":"Let your vim moves the hanoi tower to get tired.","3":"Let your vim moves the hanoi tower to get tired.","description":"The Hanoi Tower is the famous case study for illustrating the recursive algorithm.\r\nAnd this is the simplest implementation written in vim macro.","4":"The Hanoi Tower is the famous case study for illustrating the recursive algorithm.\r\nAnd this is the simplest implementation written in vim macro.","install_details":"vi +\"source hanoi.vim\"\r\nthen press \"g\" to start,\r\nor append the tower as longer as you wish before start.","5":"vi +\"source hanoi.vim\"\r\nthen press \"g\" to start,\r\nor append the tower as longer as you wish before start.","first_name":"Samuel","6":"Samuel","last_name":"Yang","7":"Yang","releases":[{"0":"728","vim_version":"6.0","1":"6.0","script_version":"1.1","2":"1.1","version_comment":"add feature of aborting for endless recursive loop","3":"add feature of aborting for endless recursive loop","package":"hanoi.vim","4":"hanoi.vim","src_id":"2211","5":"2211","creation_date":"1060192328","6":"1060192328"},{"0":"728","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"hanoi.vim","4":"hanoi.vim","src_id":"2209","5":"2209","creation_date":"1060177490","6":"1060177490"}]},"727":{"script_id":"727","0":"727","script_name":"local_vimrc.vim","1":"local_vimrc.vim","script_type":"utility","2":"utility","summary":"Load local vimrs's from $HOME to the current directory","3":"Load local vimrs's from $HOME to the current directory","description":"Note: this plugin is maintained on github: https:\/\/github.com\/LucHermitte\/local_vimrc\r\nThe last standalone version is available at: http:\/\/code.google.com\/p\/lh-vim\/source\/browse\/misc\/trunk\/plugin\/local_vimrc.vim\r\n\r\n---------------------------------\r\n\r\nThe aim of local_vimrcis to apply settings on files from a same project.\r\n\r\nA project is defined by a root directory: everything under the root directory belongs to the project. No need to register every single file in the project, they all belong. \r\n\r\nThis plugin recursively sources the _vimrc_local.vim files present from $HOME to the directory of the current buffer every time we change buffer.\r\n\r\nExample: current dir is ~\/a\/b\/c. Files are sourced in this order:\r\n~\/_vimrc_local.vim, then ~\/a\/_vimrc_local.vim, ~\/a\/b\/_vimrc_local.vim, and finally ~\/a\/b\/c\/_vimrc_local.vim\r\n\r\nNo messages issued if some of _vimrc_local.vim does not exist.\r\n\r\n\r\nSee the official plugin homepage for more details.","4":"Note: this plugin is maintained on github: https:\/\/github.com\/LucHermitte\/local_vimrc\r\nThe last standalone version is available at: http:\/\/code.google.com\/p\/lh-vim\/source\/browse\/misc\/trunk\/plugin\/local_vimrc.vim\r\n\r\n---------------------------------\r\n\r\nThe aim of local_vimrcis to apply settings on files from a same project.\r\n\r\nA project is defined by a root directory: everything under the root directory belongs to the project. No need to register every single file in the project, they all belong. \r\n\r\nThis plugin recursively sources the _vimrc_local.vim files present from $HOME to the directory of the current buffer every time we change buffer.\r\n\r\nExample: current dir is ~\/a\/b\/c. Files are sourced in this order:\r\n~\/_vimrc_local.vim, then ~\/a\/_vimrc_local.vim, ~\/a\/b\/_vimrc_local.vim, and finally ~\/a\/b\/c\/_vimrc_local.vim\r\n\r\nNo messages issued if some of _vimrc_local.vim does not exist.\r\n\r\n\r\nSee the official plugin homepage for more details.","install_details":"As the plugin have a dependency to lh-vim-lib, use vim-addon-manager (or any other vim-pi compatible plugin manager) to install it\r\n   :UpdateAddons local_vimrc","5":"As the plugin have a dependency to lh-vim-lib, use vim-addon-manager (or any other vim-pi compatible plugin manager) to install it\r\n   :UpdateAddons local_vimrc","first_name":"Luc","6":"Luc","last_name":"Hermitte","7":"Hermitte","releases":[{"0":"727","vim_version":"6.0","1":"6.0","script_version":"1.3","2":"1.3","version_comment":"Initial upload","3":"Initial upload","package":"local_vimrc.vim","4":"local_vimrc.vim","src_id":"2208","5":"2208","creation_date":"1060136303","6":"1060136303"}]},"726":{"script_id":"726","0":"726","script_name":"tagMenu","1":"tagMenu","script_type":"utility","2":"utility","summary":"Popup menu showing tags","3":"Popup menu showing tags","description":"Sometimes when the size of tag file is large, and you are searching for a   particular tag, it is cumbersome to ^N through the list of tags. This plugin is aimed to solve this. A hidden menu containing the list of tags is  created. This can be accessed using CTRL-K, or any other mapping that you  want","4":"Sometimes when the size of tag file is large, and you are searching for a   particular tag, it is cumbersome to ^N through the list of tags. This plugin is aimed to solve this. A hidden menu containing the list of tags is  created. This can be accessed using CTRL-K, or any other mapping that you  want","install_details":"1. Copy the tagsMenu.vim script to $HOME\/.vim\/plugin directory. Refer to':help add-plugin', ':help add-global-plugin', and ':help runtimepath' for more details.                                                              \r\n2. Restart Vim                                                             \r\n3. Use \":Tags\" command to create the menu of tags.                         \r\n","5":"1. Copy the tagsMenu.vim script to $HOME\/.vim\/plugin directory. Refer to':help add-plugin', ':help add-global-plugin', and ':help runtimepath' for more details.                                                              \r\n2. Restart Vim                                                             \r\n3. Use \":Tags\" command to create the menu of tags.                         \r\n","first_name":"Aditya","6":"Aditya","last_name":"Mahajan","7":"Mahajan","releases":[{"0":"726","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"tagsMenu.vim","4":"tagsMenu.vim","src_id":"2205","5":"2205","creation_date":"1060085152","6":"1060085152"}]},"725":{"script_id":"725","0":"725","script_name":"wiki.vim","1":"wiki.vim","script_type":"syntax","2":"syntax","summary":"Syntax file for Wikis","3":"Syntax file for Wikis","description":"Little syntax file to use a wiki-editor with VIM (if your browser - like W3M - allow this action).\r\nNOTE: Madd Sauer has write a very good an improved WIKI-file for VIM. Please visit for the future\r\nhttp:\/\/www.vim.org\/scripts\/script.php?script_id=1166 :-)","4":"Little syntax file to use a wiki-editor with VIM (if your browser - like W3M - allow this action).\r\nNOTE: Madd Sauer has write a very good an improved WIKI-file for VIM. Please visit for the future\r\nhttp:\/\/www.vim.org\/scripts\/script.php?script_id=1166 :-)","install_details":"To use this syntax file:\r\n1. mkdir ~\/.vim\/syntax\r\n2. mv ~\/wiki.vim ~\/.vim\/syntax\/wiki.vim\r\n3. :set syntax=wiki \r\n\r\n","5":"To use this syntax file:\r\n1. mkdir ~\/.vim\/syntax\r\n2. mv ~\/wiki.vim ~\/.vim\/syntax\/wiki.vim\r\n3. :set syntax=wiki \r\n\r\n","first_name":"Andreas","6":"Andreas","last_name":"Kneib","7":"Kneib","releases":[{"0":"725","vim_version":"6.0","1":"6.0","script_version":"1.03","2":"1.03","version_comment":"make WikiLink simple (see File)","3":"make WikiLink simple (see File)","package":"wiki.vim","4":"wiki.vim","src_id":"2207","5":"2207","creation_date":"1060100869","6":"1060100869"},{"0":"725","vim_version":"6.0","1":"6.0","script_version":"1.02","2":"1.02","version_comment":"add several improvements","3":"add several improvements","package":"wiki.vim","4":"wiki.vim","src_id":"2204","5":"2204","creation_date":"1060085053","6":"1060085053"},{"0":"725","vim_version":"6.0","1":"6.0","script_version":"1.01","2":"1.01","version_comment":"Add syntax for Wikilinks like \"WikiWord\" ","3":"Add syntax for Wikilinks like \"WikiWord\" ","package":"wiki.vim","4":"wiki.vim","src_id":"2200","5":"2200","creation_date":"1059918144","6":"1059918144"},{"0":"725","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"wiki.vim","4":"wiki.vim","src_id":"2197","5":"2197","creation_date":"1059842407","6":"1059842407"}]},"724":{"script_id":"724","0":"724","script_name":"trash.vim","1":"trash.vim","script_type":"utility","2":"utility","summary":"script for trashing dd d, D, <Del> erasing actions--- version: 0.1","3":"script for trashing dd d, D, <Del> erasing actions--- version: 0.1","description":"Trashed at: 01\/08\/03 - 08:20:34 from file: C:\\Vim\\vimfiles\\plugin\\trash.vim {{{\r\n\" Location of the stored files: ~\/vim\/trash \r\n\" Command: Trashon   - start trashing -- default on\r\n\" Command: Trashoff  - stop trashing -- recommended for encrypted files\r\n\" Command: Trashview - view the trash file -- as a readonly file\r\n<<<<< end deleted text }}}\r\n","4":"Trashed at: 01\/08\/03 - 08:20:34 from file: C:\\Vim\\vimfiles\\plugin\\trash.vim {{{\r\n\" Location of the stored files: ~\/vim\/trash \r\n\" Command: Trashon   - start trashing -- default on\r\n\" Command: Trashoff  - stop trashing -- recommended for encrypted files\r\n\" Command: Trashview - view the trash file -- as a readonly file\r\n<<<<< end deleted text }}}\r\n","install_details":"-- You must creat in your vim directory a trash directory with the name \"trash\":  ~\/vim\/trash ","5":"-- You must creat in your vim directory a trash directory with the name \"trash\":  ~\/vim\/trash ","first_name":"nicolaie","6":"nicolaie","last_name":"george","7":"george","releases":[{"0":"724","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"the small problem with buffers without name has been solved","3":"the small problem with buffers without name has been solved","package":"trash.vim","4":"trash.vim","src_id":"2198","5":"2198","creation_date":"1059868656","6":"1059868656"},{"0":"724","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"trash.vim","4":"trash.vim","src_id":"2196","5":"2196","creation_date":"1059696954","6":"1059696954"}]},"723":{"script_id":"723","0":"723","script_name":"mupad.vim","1":"mupad.vim","script_type":"syntax","2":"syntax","summary":"Syntax file for MuPAD","3":"Syntax file for MuPAD","description":"This is a syntax file for MuPAD programs. \r\n\r\nhttp:\/\/www.mupad.de\/contrib.shtml","4":"This is a syntax file for MuPAD programs. \r\n\r\nhttp:\/\/www.mupad.de\/contrib.shtml","install_details":"Just put it in your ~\/.vim\/syntax \r\nand add\r\n\r\nau BufNewFile,BufRead *.mu  exe \"source ~\/.vim\/syntax\/mupad.vim\"\r\n\r\nto your ~\/.vimrc\r\n\r\n\r\n","5":"Just put it in your ~\/.vim\/syntax \r\nand add\r\n\r\nau BufNewFile,BufRead *.mu  exe \"source ~\/.vim\/syntax\/mupad.vim\"\r\n\r\nto your ~\/.vimrc\r\n\r\n\r\n","first_name":"Fabio","6":"Fabio","last_name":"Stumbo","7":"Stumbo","releases":[{"0":"723","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Small change in the way the names of procedures are highlighted. Moreover, they are highlighted also if the name is specified after the command \"name\"","3":"Small change in the way the names of procedures are highlighted. Moreover, they are highlighted also if the name is specified after the command \"name\"","package":"mupad.vim","4":"mupad.vim","src_id":"3009","5":"3009","creation_date":"1084180995","6":"1084180995"},{"0":"723","vim_version":"6.0","1":"6.0","script_version":"0.4","2":"0.4","version_comment":"Added Axiom, Category and Domain library","3":"Added Axiom, Category and Domain library","package":"mupad.vim","4":"mupad.vim","src_id":"2712","5":"2712","creation_date":"1075716633","6":"1075716633"},{"0":"723","vim_version":"6.0","1":"6.0","script_version":"0.3","2":"0.3","version_comment":"Corrected some bug \r\nRedefined all colors (see the colors section)\r\nAdded all builtin functions (mupad 2.5.3)\r\nAdded the Type library\r\nImproved sanity check","3":"Corrected some bug \r\nRedefined all colors (see the colors section)\r\nAdded all builtin functions (mupad 2.5.3)\r\nAdded the Type library\r\nImproved sanity check","package":"mupad.vim","4":"mupad.vim","src_id":"2650","5":"2650","creation_date":"1073463845","6":"1073463845"},{"0":"723","vim_version":"6.0","1":"6.0","script_version":"0.2","2":"0.2","version_comment":"Added definition syntax with semicolon checking and made some clean up","3":"Added definition syntax with semicolon checking and made some clean up","package":"mupad.vim","4":"mupad.vim","src_id":"2246","5":"2246","creation_date":"1061436167","6":"1061436167"},{"0":"723","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"mupad.vim","4":"mupad.vim","src_id":"2192","5":"2192","creation_date":"1059476551","6":"1059476551"}]},"722":{"script_id":"722","0":"722","script_name":"cygwin.vim","1":"cygwin.vim","script_type":"utility","2":"utility","summary":"Compiler plugin for cygwin-tools used from the win32 native version of Vim","3":"Compiler plugin for cygwin-tools used from the win32 native version of Vim","description":"This file is useful with gcc and other programs run from make, when these tools come from Cygwin and the version of Vim used is the win32 native version.\r\nIn other environments, Vim default settings are perfect.\r\n\r\nReason: the filenames (for whom gcc reports errors) are expressed in the UNIX form, and Vim is unable to open them from the quickfix window. Hence the filtering used to replace '\/' (root) by {cygpath -m \/}.\r\nSince the version 20040616, this plugin is also able to follow symbolic links -- defined from cygwin.\r\n\r\nAt this time, it has only be tested with gcc, but I guess it should be useful with other compilers built for cygwin.\r\n\r\n\r\nImprovments are certainly posible. Any feedback is welcomed!","4":"This file is useful with gcc and other programs run from make, when these tools come from Cygwin and the version of Vim used is the win32 native version.\r\nIn other environments, Vim default settings are perfect.\r\n\r\nReason: the filenames (for whom gcc reports errors) are expressed in the UNIX form, and Vim is unable to open them from the quickfix window. Hence the filtering used to replace '\/' (root) by {cygpath -m \/}.\r\nSince the version 20040616, this plugin is also able to follow symbolic links -- defined from cygwin.\r\n\r\nAt this time, it has only be tested with gcc, but I guess it should be useful with other compilers built for cygwin.\r\n\r\n\r\nImprovments are certainly posible. Any feedback is welcomed!","install_details":"Copy the file into one of your {rtp}\/compiler\/ directory, and be sure that $TERM or $OSTYPE value 'cygwin' before doing a:\r\n  :compiler cygwin\r\nand then\r\n  :make target\r\n\r\nThe version 20040616 requires Perl (tested OK with cygwin's one) and cygUtils (more precisely: realpath).","5":"Copy the file into one of your {rtp}\/compiler\/ directory, and be sure that $TERM or $OSTYPE value 'cygwin' before doing a:\r\n  :compiler cygwin\r\nand then\r\n  :make target\r\n\r\nThe version 20040616 requires Perl (tested OK with cygwin's one) and cygUtils (more precisely: realpath).","first_name":"Luc","6":"Luc","last_name":"Hermitte","7":"Hermitte","releases":[{"0":"722","vim_version":"6.0","1":"6.0","script_version":"20040616","2":"20040616","version_comment":"Now follows symbolic links (requires perl and realpath)","3":"Now follows symbolic links (requires perl and realpath)","package":"compiler-cygwin.tar.gz","4":"compiler-cygwin.tar.gz","src_id":"3139","5":"3139","creation_date":"1087383429","6":"1087383429"},{"0":"722","vim_version":"6.0","1":"6.0","script_version":"20040213","2":"20040213","version_comment":"Fix: Do not try to convert non absolute pathes","3":"Fix: Do not try to convert non absolute pathes","package":"cygwin.vim","4":"cygwin.vim","src_id":"2988","5":"2988","creation_date":"1083317883","6":"1083317883"},{"0":"722","vim_version":"6.0","1":"6.0","script_version":"20030331","2":"20030331","version_comment":"Initial upload","3":"Initial upload","package":"cygwin.vim","4":"cygwin.vim","src_id":"2191","5":"2191","creation_date":"1059471417","6":"1059471417"}]},"721":{"script_id":"721","0":"721","script_name":"MSIL Assembly","1":"MSIL Assembly","script_type":"syntax","2":"syntax","summary":"Syntax file for the .NET Microsoft Intermediate Language Assembly","3":"Syntax file for the .NET Microsoft Intermediate Language Assembly","description":"Syntax file for the .NET Microsoft Intermediate Language Assembly. Quite complete -- I hope so, at least.","4":"Syntax file for the .NET Microsoft Intermediate Language Assembly. Quite complete -- I hope so, at least.","install_details":"","5":"","first_name":"Nicolas","6":"Nicolas","last_name":"Herry","7":"Herry","releases":[{"0":"721","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"ilasm.vim","4":"ilasm.vim","src_id":"2188","5":"2188","creation_date":"1059214211","6":"1059214211"}]},"720":{"script_id":"720","0":"720","script_name":"SideBar.vim","1":"SideBar.vim","script_type":"utility","2":"utility","summary":"Auto-shrinking container of vertically aligned material","3":"Auto-shrinking container of vertically aligned material","description":"There are many fine plugins that use persistent windows to display useful\r\ninformation (e.g. TagList plugin) or to provide bookmark-like portal to\r\nother files and buffers (e.g. Project or Buffer explorers etc.). There is\r\none major drawback to using them: you have to sacrifice precious screen real\r\nestate. One way to compensate is to put those auxillary windows in\r\n'side-pocket', and to open and close it when needed. So here comes SideBar.\r\n\r\nAs a stand-alone plugin it's pretty useless. It's really a framework that\r\nallows easy creation of SideBar-contained plugins. As an example I've\r\nincluded my very simplistic rewrite of excellent Project plugin by Aric\r\nBlumer. Note that it doesn't even try to manage its window. Just 'register'\r\nit in SideBar with following command (to learn more of ProjectJr, read its\r\ncomments):\r\n:SideBarAddCmd ProjectJr ~\/main.prj\r\n\r\nNow you have mini-project in your side-pocket. Use :SideBarEnter or\r\n:SideBarEnterToggle to quickly enter\/leave it. If you close its window\r\n(without destroying its buffer), or make it 'only', next invocation of one\r\nof those commands will bring SideBar back. Of course, it's best to map these\r\ncommands to some handy keys, e.g. <Tab>.\r\n\r\nYou can have as many projects\/other buffers managed by SideBar as you wish.\r\nRegister these buffers with :SideBarAddCmd <any ex command> and switch\r\nbetween them with :SideBarCycle\r\n\r\nTo hack deep inside SideBar, another command is provided:\r\n:SideBarExec <any ex command> will execute <any ex command> in SideBar\r\ncontext without buffer registration. Note that you can use 's:' prefix to\r\ncall plugin-local functions and modify its variables, so proceed with\r\ncaution. To call functions local to your script, use <SID> prefix as\r\nusual.\r\n","4":"There are many fine plugins that use persistent windows to display useful\r\ninformation (e.g. TagList plugin) or to provide bookmark-like portal to\r\nother files and buffers (e.g. Project or Buffer explorers etc.). There is\r\none major drawback to using them: you have to sacrifice precious screen real\r\nestate. One way to compensate is to put those auxillary windows in\r\n'side-pocket', and to open and close it when needed. So here comes SideBar.\r\n\r\nAs a stand-alone plugin it's pretty useless. It's really a framework that\r\nallows easy creation of SideBar-contained plugins. As an example I've\r\nincluded my very simplistic rewrite of excellent Project plugin by Aric\r\nBlumer. Note that it doesn't even try to manage its window. Just 'register'\r\nit in SideBar with following command (to learn more of ProjectJr, read its\r\ncomments):\r\n:SideBarAddCmd ProjectJr ~\/main.prj\r\n\r\nNow you have mini-project in your side-pocket. Use :SideBarEnter or\r\n:SideBarEnterToggle to quickly enter\/leave it. If you close its window\r\n(without destroying its buffer), or make it 'only', next invocation of one\r\nof those commands will bring SideBar back. Of course, it's best to map these\r\ncommands to some handy keys, e.g. <Tab>.\r\n\r\nYou can have as many projects\/other buffers managed by SideBar as you wish.\r\nRegister these buffers with :SideBarAddCmd <any ex command> and switch\r\nbetween them with :SideBarCycle\r\n\r\nTo hack deep inside SideBar, another command is provided:\r\n:SideBarExec <any ex command> will execute <any ex command> in SideBar\r\ncontext without buffer registration. Note that you can use 's:' prefix to\r\ncall plugin-local functions and modify its variables, so proceed with\r\ncaution. To call functions local to your script, use <SID> prefix as\r\nusual.\r\n","install_details":"","5":"","first_name":"Andrew","6":"Andrew","last_name":"Rodionoff","7":"Rodionoff","releases":[{"0":"720","vim_version":"6.0","1":"6.0","script_version":"0.3","2":"0.3","version_comment":"Some behaviour improvements (see comments). Added two mini-plugins.","3":"Some behaviour improvements (see comments). Added two mini-plugins.","package":"SideBar-0.3.zip","4":"SideBar-0.3.zip","src_id":"2356","5":"2356","creation_date":"1064582376","6":"1064582376"},{"0":"720","vim_version":"6.0","1":"6.0","script_version":"0.2","2":"0.2","version_comment":"New :SideBarSwallow command, some config  options\nImproved functionality in ProjectJr plugin\n","3":"New :SideBarSwallow command, some config  options\nImproved functionality in ProjectJr plugin\n","package":"SideBar.zip","4":"SideBar.zip","src_id":"2233","5":"2233","creation_date":"1060867985","6":"1060867985"},{"0":"720","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"SideBar.zip","4":"SideBar.zip","src_id":"2181","5":"2181","creation_date":"1058966218","6":"1058966218"}]},"719":{"script_id":"719","0":"719","script_name":"nuvola.vim","1":"nuvola.vim","script_type":"color scheme","2":"color scheme","summary":"Color scheme for the Gnome2 \"nuvola\" theme","3":"Color scheme for the Gnome2 \"nuvola\" theme","description":"This is mainly a GUI colorscheme fitting into the Gnome2 SVG theme \"nuvola\".\r\nhttp:\/\/librsvg.sourceforge.net\/theme.php\r\nThis theme was created by David Vignoni\r\nhttp:\/\/projects.dims.org\/~dave\/svg.html\r\nThe windows have a blue frame and a light background.","4":"This is mainly a GUI colorscheme fitting into the Gnome2 SVG theme \"nuvola\".\r\nhttp:\/\/librsvg.sourceforge.net\/theme.php\r\nThis theme was created by David Vignoni\r\nhttp:\/\/projects.dims.org\/~dave\/svg.html\r\nThe windows have a blue frame and a light background.","install_details":"Put in ~\/.vim\/colors or (<your-vim-dir>\\vimfiles\\colors on Windows) and do\r\n:colorscheme nuvola","5":"Put in ~\/.vim\/colors or (<your-vim-dir>\\vimfiles\\colors on Windows) and do\r\n:colorscheme nuvola","first_name":"Johann","6":"Johann","last_name":"Pfefferl","7":"Pfefferl","releases":[{"0":"719","vim_version":"6.0","1":"6.0","script_version":"1.14","2":"1.14","version_comment":"Some modifications to the choosen colors.\r\n- Comments are now more readable\r\n- darker background\r\n- more contrast","3":"Some modifications to the choosen colors.\r\n- Comments are now more readable\r\n- darker background\r\n- more contrast","package":"nuvola.vim","4":"nuvola.vim","src_id":"2222","5":"2222","creation_date":"1060595989","6":"1060595989"},{"0":"719","vim_version":"6.0","1":"6.0","script_version":"1.8","2":"1.8","version_comment":"Initial upload","3":"Initial upload","package":"nuvola.vim","4":"nuvola.vim","src_id":"2178","5":"2178","creation_date":"1058855376","6":"1058855376"}]},"718":{"script_id":"718","0":"718","script_name":"browser-like-scrolling-for-readonly-file","1":"browser-like-scrolling-for-readonly-file","script_type":"utility","2":"utility","summary":"convenient, browser-like scrolling for viewing readonly files","3":"convenient, browser-like scrolling for viewing readonly files","description":"If, when viewing readonly files in vim, you wish that up\/down arrows behaved like in web browser (each down arrow scrolls the view 1 line down, except near end of file; each arrow-up scrolls the view 1 line up, except near beginning of file) \r\n-- then this plugin does it.\r\n\r\nTo check the difference, just source the script (':so ro_positioning.vim' if not installed) and try the help (:he) and\r\ntry arrows down. You'll notice that up\/down arrows behave more conveniently. \r\n\r\nThis plugin remaps arrow-up and arrow-down in readonly files to behave more conveniently. No remappings are done for non-readonly files.\r\n\r\nIf you want to enable this mode for arbitrary writable file, do:\r\n     :set ro\r\n     :e\r\n","4":"If, when viewing readonly files in vim, you wish that up\/down arrows behaved like in web browser (each down arrow scrolls the view 1 line down, except near end of file; each arrow-up scrolls the view 1 line up, except near beginning of file) \r\n-- then this plugin does it.\r\n\r\nTo check the difference, just source the script (':so ro_positioning.vim' if not installed) and try the help (:he) and\r\ntry arrows down. You'll notice that up\/down arrows behave more conveniently. \r\n\r\nThis plugin remaps arrow-up and arrow-down in readonly files to behave more conveniently. No remappings are done for non-readonly files.\r\n\r\nIf you want to enable this mode for arbitrary writable file, do:\r\n     :set ro\r\n     :e\r\n","install_details":"Just copy the included file (ro_positioning.vim) into either personal plugin directory (~\/.vim\/plugin\/.), or into global plugin directory ($VIMRUNTIME\/plugin\/.)\r\n\r\nTo copy into the personal plugin directory:\r\n\r\n  mkdir -p ~\/.vim\/plugin; cp ro_positioning.vim ~\/.vim\/plugin\/.\r\n\r\nTo copy into the global plugin directory:\r\n\r\n  cp ro_positioning.vim $VIMRUNTIME\/plugin\/.\r\n\r\nParameters: no parameters.\r\n\r\nCommands and keys: arrow up, arrow down\r\n","5":"Just copy the included file (ro_positioning.vim) into either personal plugin directory (~\/.vim\/plugin\/.), or into global plugin directory ($VIMRUNTIME\/plugin\/.)\r\n\r\nTo copy into the personal plugin directory:\r\n\r\n  mkdir -p ~\/.vim\/plugin; cp ro_positioning.vim ~\/.vim\/plugin\/.\r\n\r\nTo copy into the global plugin directory:\r\n\r\n  cp ro_positioning.vim $VIMRUNTIME\/plugin\/.\r\n\r\nParameters: no parameters.\r\n\r\nCommands and keys: arrow up, arrow down\r\n","first_name":"Yakov","6":"Yakov","last_name":"Lerner","7":"Lerner","releases":[{"0":"718","vim_version":"6.0","1":"6.0","script_version":"1.1","2":"1.1","version_comment":"fixed switch to\/from readonly windows","3":"fixed switch to\/from readonly windows","package":"ro_positioning.vim","4":"ro_positioning.vim","src_id":"2182","5":"2182","creation_date":"1059017440","6":"1059017440"},{"0":"718","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"ro_positioning.vim","4":"ro_positioning.vim","src_id":"2177","5":"2177","creation_date":"1058851255","6":"1058851255"}]},"717":{"script_id":"717","0":"717","script_name":"sfl.vim","1":"sfl.vim","script_type":"syntax","2":"syntax","summary":"VIM Syntax file for SFL hardware description language.","3":"VIM Syntax file for SFL hardware description language.","description":"SFL, Structured Function description Language, is a one of the Hardware Description Language. SFL is Register Transfer Level HDL, the programming style is like C or Pascal.\r\nPlease see here: http:\/\/www.onlab.ntt.co.jp\/mn\/parthenon\/pack.html\r\n\r\nSFL can be converted to Verilog HDL by sfl2vl. \r\nPlease see here: http:\/\/shimizu-lab.dt.u-tokai.ac.jp\/pgm\/sfl2vl\/index.html\r\n\r\nThis syntax was designed for dark background.","4":"SFL, Structured Function description Language, is a one of the Hardware Description Language. SFL is Register Transfer Level HDL, the programming style is like C or Pascal.\r\nPlease see here: http:\/\/www.onlab.ntt.co.jp\/mn\/parthenon\/pack.html\r\n\r\nSFL can be converted to Verilog HDL by sfl2vl. \r\nPlease see here: http:\/\/shimizu-lab.dt.u-tokai.ac.jp\/pgm\/sfl2vl\/index.html\r\n\r\nThis syntax was designed for dark background.","install_details":"Put the file to $HOME\/.vim\/colors, then add this line to $HOME\/.vimrc\r\n\"colorscheme sfl\".\r\nYou may need to add following line in addition,\r\n\"syntax enable\".","5":"Put the file to $HOME\/.vim\/colors, then add this line to $HOME\/.vimrc\r\n\"colorscheme sfl\".\r\nYou may need to add following line in addition,\r\n\"syntax enable\".","first_name":"Yoshihiro","6":"Yoshihiro","last_name":"Iida","7":"Iida","releases":[{"0":"717","vim_version":"6.0","1":"6.0","script_version":"2.1","2":"2.1","version_comment":"The syntax file has changed more similar Verilog or VHDL color.","3":"The syntax file has changed more similar Verilog or VHDL color.","package":"sfl.vim","4":"sfl.vim","src_id":"2755","5":"2755","creation_date":"1077006305","6":"1077006305"},{"0":"717","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Distinguishes colors between control signals and data signals.\r\nVersion 1.0 is stable Vim syntax for SFL.","3":"Distinguishes colors between control signals and data signals.\r\nVersion 1.0 is stable Vim syntax for SFL.","package":"sfl.vim","4":"sfl.vim","src_id":"2173","5":"2173","creation_date":"1058697168","6":"1058697168"},{"0":"717","vim_version":"6.0","1":"6.0","script_version":"0.3","2":"0.3","version_comment":"Supports all of SFL and Verilog keywords.\r\nDetects reserved port name of SFL and Verilog.","3":"Supports all of SFL and Verilog keywords.\r\nDetects reserved port name of SFL and Verilog.","package":"sfl.vim","4":"sfl.vim","src_id":"2171","5":"2171","creation_date":"1058608241","6":"1058608241"},{"0":"717","vim_version":"6.0","1":"6.0","script_version":"0.2","2":"0.2","version_comment":"Initial upload","3":"Initial upload","package":"sfl.vim","4":"sfl.vim","src_id":"2169","5":"2169","creation_date":"1058587599","6":"1058587599"}]},"716":{"script_id":"716","0":"716","script_name":"brainfuck syntax","1":"brainfuck syntax","script_type":"syntax","2":"syntax","summary":"brainfuck syntax support","3":"brainfuck syntax support","description":"Support for the brainfuck programming language.","4":"Support for the brainfuck programming language.","install_details":"","5":"","first_name":"Mathias","6":"Mathias","last_name":"Panzenb\u00c3\u00b6ck","7":"Panzenb\u00c3\u00b6ck","releases":[{"0":"716","vim_version":"5.7","1":"5.7","script_version":"1.0.3","2":"1.0.3","version_comment":"Updated my email address and added version information.","3":"Updated my email address and added version information.","package":"brainfuck.vim","4":"brainfuck.vim","src_id":"22518","5":"22518","creation_date":"1413046440","6":"1413046440"},{"0":"716","vim_version":"5.7","1":"5.7","script_version":"1.0.2","2":"1.0.2","version_comment":"Fixed comment matching and encoding of the vim script.","3":"Fixed comment matching and encoding of the vim script.","package":"brainfuck.vim","4":"brainfuck.vim","src_id":"14054","5":"14054","creation_date":"1287067629","6":"1287067629"},{"0":"716","vim_version":"6.0","1":"6.0","script_version":"1.0.1","2":"1.0.1","version_comment":"'delcommand HiLink' was missing.","3":"'delcommand HiLink' was missing.","package":"brainfuck.vim","4":"brainfuck.vim","src_id":"2189","5":"2189","creation_date":"1059362164","6":"1059362164"},{"0":"716","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"brainfuck.vim","4":"brainfuck.vim","src_id":"2168","5":"2168","creation_date":"1058537118","6":"1058537118"}]},"707":{"script_id":"707","0":"707","script_name":"msp.vim","1":"msp.vim","script_type":"syntax","2":"syntax","summary":"TI MSP430 Assembly Syntax","3":"TI MSP430 Assembly Syntax","description":"Provides assembly language syntax highlighting for theTI MSP430 family of processors","4":"Provides assembly language syntax highlighting for theTI MSP430 family of processors","install_details":"Put in you syntax directory, and follow help directions for new-filetype","5":"Put in you syntax directory, and follow help directions for new-filetype","first_name":"Russell","6":"Russell","last_name":"Brinkmann","7":"Brinkmann","releases":[{"0":"707","vim_version":"6.0","1":"6.0","script_version":"1.1","2":"1.1","version_comment":"Add minimal support for C style comments, which the IAR compiler understands.","3":"Add minimal support for C style comments, which the IAR compiler understands.","package":"msp.vim","4":"msp.vim","src_id":"2212","5":"2212","creation_date":"1060192509","6":"1060192509"},{"0":"707","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"msp.vim","4":"msp.vim","src_id":"2159","5":"2159","creation_date":"1058525345","6":"1058525345"}]},"706":{"script_id":"706","0":"706","script_name":"gdl.vim","1":"gdl.vim","script_type":"syntax","2":"syntax","summary":"GDL\/VCG syntax highlighting file","3":"GDL\/VCG syntax highlighting file","description":"gdl.vim is a syntax highlighting package for the graph description language GDL (fka VCG).\r\n\r\nWhenever you open a .gdl or .vcg file, the package automatically analyzes the text and marks keywords, attribute specifications, comments, etc. using customizable colors. Whenever you start writing a new GDL document, it automatically analyzes the new text for the proper spelling\/syntax, highlighting correct items.\r\n\r\nBenefit to you: your GDL file is easier to read and you can understand GDL source code faster.\r\n\r\ngdl.vim is intended to go beyond simple syntax and spell-checking. It should also check attribute-value pairs for type correctness. In some cases, it will even check if a specified number is within the valid range.\r\n\r\nThe package was tested under Vim 5.6\/Linux, gVim 6.1\/WinNT4.0, gVim 6.2\/Win2000, and gVim6.3\/Win2000.\r\n\r\nFor further information, screenshots, etc., visit http:\/\/www.aiSee.com\/gdledit\r\n\r\nYour feedback is appreciated.","4":"gdl.vim is a syntax highlighting package for the graph description language GDL (fka VCG).\r\n\r\nWhenever you open a .gdl or .vcg file, the package automatically analyzes the text and marks keywords, attribute specifications, comments, etc. using customizable colors. Whenever you start writing a new GDL document, it automatically analyzes the new text for the proper spelling\/syntax, highlighting correct items.\r\n\r\nBenefit to you: your GDL file is easier to read and you can understand GDL source code faster.\r\n\r\ngdl.vim is intended to go beyond simple syntax and spell-checking. It should also check attribute-value pairs for type correctness. In some cases, it will even check if a specified number is within the valid range.\r\n\r\nThe package was tested under Vim 5.6\/Linux, gVim 6.1\/WinNT4.0, gVim 6.2\/Win2000, and gVim6.3\/Win2000.\r\n\r\nFor further information, screenshots, etc., visit http:\/\/www.aiSee.com\/gdledit\r\n\r\nYour feedback is appreciated.","install_details":"Unix users:\r\n-------------------------\r\nYou can simply copy the downloaded VIM file to your home directory and then use the Vim command\r\n:source ~\/gdl.vim\r\n\r\nAlternatively, perform the following steps:\r\n\r\n1. Copy the downloaded VIM file to the directory $VIMRUNTIME\/syntax\/\r\n2. Add the following line to your .vimrc file (this file is usually to be found in your home directory):\r\n:autocmd BufNewFile,BufRead *.{gdl,vcg} source $VIMRUNTIME\/syntax\/gdl.vim\r\n\r\nIf you are not sure about the value of $VIMRUNTIME, try ~\/.vim or type\r\n:help runtime\r\n\r\nNow, Vim should automatically recognize GDL and VCG files. You can switch highlighting off and on in the editor by using the commands\r\n:syn off\r\n:syn on\r\n\r\nThere may be some highlighting irregularities if you use an old Vim version which is not capable of matching the new line character \\n. (Type \":help \\n\" if you are not sure.) As a work-around, it is sufficient to begin each new line of your GDL code with one or several white spaces. If you use Vim 6.x, don't bother.\r\n\r\nFor further details about Vim syntax highlighting, see\r\n:help syntax\r\n\r\nWindows users:\r\n-------------------------\r\nYou can simply copy the downloaded VIM file to C:\\ and then use the Vim command \r\n:source C:\\gdl.vim\r\nto switch highlighting on.\r\n\r\nIf you would like Vim to automatically recognize GDL and VCG files, add the following two lines:\r\n\r\n\" Graph Description Language\r\nau BufNewFile,BufRead *.{gdl,vcg} source C:\\gdl.vim\r\n\r\nto your filetype.vim file, which is usually to be found in the directory C:\\Vim\\vim63\\ or C:\\Program Files\\Vim\\vim63\\.\r\n\r\nThis script also works fine in conjunction with vimscript #750.","5":"Unix users:\r\n-------------------------\r\nYou can simply copy the downloaded VIM file to your home directory and then use the Vim command\r\n:source ~\/gdl.vim\r\n\r\nAlternatively, perform the following steps:\r\n\r\n1. Copy the downloaded VIM file to the directory $VIMRUNTIME\/syntax\/\r\n2. Add the following line to your .vimrc file (this file is usually to be found in your home directory):\r\n:autocmd BufNewFile,BufRead *.{gdl,vcg} source $VIMRUNTIME\/syntax\/gdl.vim\r\n\r\nIf you are not sure about the value of $VIMRUNTIME, try ~\/.vim or type\r\n:help runtime\r\n\r\nNow, Vim should automatically recognize GDL and VCG files. You can switch highlighting off and on in the editor by using the commands\r\n:syn off\r\n:syn on\r\n\r\nThere may be some highlighting irregularities if you use an old Vim version which is not capable of matching the new line character \\n. (Type \":help \\n\" if you are not sure.) As a work-around, it is sufficient to begin each new line of your GDL code with one or several white spaces. If you use Vim 6.x, don't bother.\r\n\r\nFor further details about Vim syntax highlighting, see\r\n:help syntax\r\n\r\nWindows users:\r\n-------------------------\r\nYou can simply copy the downloaded VIM file to C:\\ and then use the Vim command \r\n:source C:\\gdl.vim\r\nto switch highlighting on.\r\n\r\nIf you would like Vim to automatically recognize GDL and VCG files, add the following two lines:\r\n\r\n\" Graph Description Language\r\nau BufNewFile,BufRead *.{gdl,vcg} source C:\\gdl.vim\r\n\r\nto your filetype.vim file, which is usually to be found in the directory C:\\Vim\\vim63\\ or C:\\Program Files\\Vim\\vim63\\.\r\n\r\nThis script also works fine in conjunction with vimscript #750.","first_name":"Alexander","6":"Alexander","last_name":"Evstiougov","7":"Evstiougov","releases":[{"0":"706","vim_version":"5.7","1":"5.7","script_version":"1.9","2":"1.9","version_comment":"Added support for custom composite edge arrows.","3":"Added support for custom composite edge arrows.","package":"gdl.vim","4":"gdl.vim","src_id":"3876","5":"3876","creation_date":"1108638255","6":"1108638255"},{"0":"706","vim_version":"6.0","1":"6.0","script_version":"1.9win","2":"1.9win","version_comment":"This one's for those who work under Windows.","3":"This one's for those who work under Windows.","package":"gdl.vim","4":"gdl.vim","src_id":"3875","5":"3875","creation_date":"1108638183","6":"1108638183"},{"0":"706","vim_version":"5.7","1":"5.7","script_version":"1.8","2":"1.8","version_comment":"Added support for the new edge arrow styles.","3":"Added support for the new edge arrow styles.","package":"gdl.vim","4":"gdl.vim","src_id":"3765","5":"3765","creation_date":"1105618574","6":"1105618574"},{"0":"706","vim_version":"6.0","1":"6.0","script_version":"1.8win","2":"1.8win","version_comment":"This one's for those who work under Windows.","3":"This one's for those who work under Windows.","package":"gdl.vim","4":"gdl.vim","src_id":"3764","5":"3764","creation_date":"1105618466","6":"1105618466"},{"0":"706","vim_version":"5.7","1":"5.7","script_version":"1.6","2":"1.6","version_comment":"Added support for new GDL attributes which will be introduced in the next aiSee release.","3":"Added support for new GDL attributes which will be introduced in the next aiSee release.","package":"gdl.vim","4":"gdl.vim","src_id":"2324","5":"2324","creation_date":"1063267338","6":"1063267338"},{"0":"706","vim_version":"6.0","1":"6.0","script_version":"1.6win","2":"1.6win","version_comment":"This one's for those who work under Windows.","3":"This one's for those who work under Windows.","package":"gdl.vim","4":"gdl.vim","src_id":"2323","5":"2323","creation_date":"1063267107","6":"1063267107"}]},"705":{"script_id":"705","0":"705","script_name":"deleted","1":"deleted","script_type":"utility","2":"utility","summary":"deleted","3":"deleted","description":"deleted","4":"deleted","install_details":"","5":"","first_name":"Antony","6":"Antony","last_name":"Scriven","7":"Scriven","releases":[{"0":"705","vim_version":"7.0","1":"7.0","script_version":"0.3.3","2":"0.3.3","version_comment":"empty","3":"empty","package":"sketch.vim","4":"sketch.vim","src_id":"24567","5":"24567","creation_date":"1475092610","6":"1475092610"}]},"704":{"script_id":"704","0":"704","script_name":"isi2bib","1":"isi2bib","script_type":"utility","2":"utility","summary":"Convert a bibliographic database from ISI to BibTeX format","3":"Convert a bibliographic database from ISI to BibTeX format","description":"Function:\r\nConvert a bibliographic database from ISI (Institute of Scientific Information, Web of Science) export format to BibTeX format.\r\n\r\nNoninteractive Usage:\r\nFrom the command line, cd to the directory of the ISI database, and issue the command\r\n\tvim -u NONE -c \":ru isi2bib.vim\" fname\r\nwhere fname is the name of the ISI database file. The BibTeX database will be saved in base(fname).bib where base(fname) is the ISI file name without an extension.\r\n\r\nDescription:\r\nBibTeX keys are constructed as follows: (last name of first author).(last two digits of year).(disambiguation mark) where the disambiguation mark is a lower case letter that is used only when needed. For example, a key could be Smith03 if it is unique but will be Smith03f if it is the 7th key starting with Smith03.\r\n\r\nOnly records of type(PT) article are converted. Other record types are ignored. Only the author(AU), title(TI), pages(BP,EP), year(PY), volume(VL) and journal(JI) fields are converted.\r\n\r\nRecent ISI records (1996 and later) use both lower- and upper-case. The case is respected and protected by braces when necessary. Older (pre-1996) ISI records use only upper case. A crude conversion to mixed case is made.\r\n\r\nSome manual cleanup of the title fields will be required; for example, to use math mode for symbols, etc.","4":"Function:\r\nConvert a bibliographic database from ISI (Institute of Scientific Information, Web of Science) export format to BibTeX format.\r\n\r\nNoninteractive Usage:\r\nFrom the command line, cd to the directory of the ISI database, and issue the command\r\n\tvim -u NONE -c \":ru isi2bib.vim\" fname\r\nwhere fname is the name of the ISI database file. The BibTeX database will be saved in base(fname).bib where base(fname) is the ISI file name without an extension.\r\n\r\nDescription:\r\nBibTeX keys are constructed as follows: (last name of first author).(last two digits of year).(disambiguation mark) where the disambiguation mark is a lower case letter that is used only when needed. For example, a key could be Smith03 if it is unique but will be Smith03f if it is the 7th key starting with Smith03.\r\n\r\nOnly records of type(PT) article are converted. Other record types are ignored. Only the author(AU), title(TI), pages(BP,EP), year(PY), volume(VL) and journal(JI) fields are converted.\r\n\r\nRecent ISI records (1996 and later) use both lower- and upper-case. The case is respected and protected by braces when necessary. Older (pre-1996) ISI records use only upper case. A crude conversion to mixed case is made.\r\n\r\nSome manual cleanup of the title fields will be required; for example, to use math mode for symbols, etc.","install_details":"Place somewhere in your runtimepath (typically ~\/.vim or $HOME\/vimfiles).","5":"Place somewhere in your runtimepath (typically ~\/.vim or $HOME\/vimfiles).","first_name":"Ajit","6":"Ajit","last_name":"Thakkar","7":"Thakkar","releases":[{"0":"704","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"isi2bib.vim","4":"isi2bib.vim","src_id":"2150","5":"2150","creation_date":"1058254099","6":"1058254099"}]},"703":{"script_id":"703","0":"703","script_name":"xmmsctrl.vim","1":"xmmsctrl.vim","script_type":"utility","2":"utility","summary":"Interaction with XMMS via 'smart' buffer","3":"Interaction with XMMS via 'smart' buffer","description":"Install the file into plugins\/ folder as usual.\r\nDon't forget to install xmmsctrl utility (search xmms.org or freshmeat).\r\nAlso read comments in file to customize xmms songchange plugin for maximum\r\neffect.\r\n\r\n","4":"Install the file into plugins\/ folder as usual.\r\nDon't forget to install xmmsctrl utility (search xmms.org or freshmeat).\r\nAlso read comments in file to customize xmms songchange plugin for maximum\r\neffect.\r\n\r\n","install_details":"","5":"","first_name":"Andrew","6":"Andrew","last_name":"Rodionoff","7":"Rodionoff","releases":[{"0":"703","vim_version":"6.0","1":"6.0","script_version":"0.2","2":"0.2","version_comment":"Command-line support (Blake Matheny), minor tweaks and fixes.","3":"Command-line support (Blake Matheny), minor tweaks and fixes.","package":"xmmsctrl.vim","4":"xmmsctrl.vim","src_id":"2362","5":"2362","creation_date":"1064930793","6":"1064930793"},{"0":"703","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"xmmsctrl.vim","4":"xmmsctrl.vim","src_id":"2146","5":"2146","creation_date":"1058018246","6":"1058018246"}]},"702":{"script_id":"702","0":"702","script_name":"parrot.vim","1":"parrot.vim","script_type":"syntax","2":"syntax","summary":"Syntax file for Parrot Assembly code","3":"Syntax file for Parrot Assembly code","description":"Simple syntax-matching for Parrot v 0.10  Assembly code.","4":"Simple syntax-matching for Parrot v 0.10  Assembly code.","install_details":"Copy to your ~\/.vim\/syntax or wherever you keep local syntax description files.\r\n\r\nYou might want to add the following to your .vimrc:\r\n\r\n  autocmd BufEnter,BufRead,BufNewFile *.pasm setfiletype parrot\r\n\r\nThat's it.","5":"Copy to your ~\/.vim\/syntax or wherever you keep local syntax description files.\r\n\r\nYou might want to add the following to your .vimrc:\r\n\r\n  autocmd BufEnter,BufRead,BufNewFile *.pasm setfiletype parrot\r\n\r\nThat's it.","first_name":"Kevin","6":"Kevin","last_name":"Harris","7":"Harris","releases":[{"0":"702","vim_version":"6.0","1":"6.0","script_version":"0.2","2":"0.2","version_comment":"Fixed ParrotString so that it works as expected. Removed some comments.","3":"Fixed ParrotString so that it works as expected. Removed some comments.","package":"parrot.vim","4":"parrot.vim","src_id":"2148","5":"2148","creation_date":"1058194362","6":"1058194362"},{"0":"702","vim_version":"6.0","1":"6.0","script_version":"0.10","2":"0.10","version_comment":"Initial upload","3":"Initial upload","package":"parrot.vim","4":"parrot.vim","src_id":"2142","5":"2142","creation_date":"1057914527","6":"1057914527"}]},"701":{"script_id":"701","0":"701","script_name":"cg.vim","1":"cg.vim","script_type":"syntax","2":"syntax","summary":"Syntax highlighting for Cg language","3":"Syntax highlighting for Cg language","description":"Syntax highlighting script for the Cg hardware shading language.\r\n\r\nSee http:\/\/www.nvidia.com\/cg and http:\/\/www.cgshaders.org for more information.","4":"Syntax highlighting script for the Cg hardware shading language.\r\n\r\nSee http:\/\/www.nvidia.com\/cg and http:\/\/www.cgshaders.org for more information.","install_details":"Copy the script into the usual place for syntax scripts.","5":"Copy the script into the usual place for syntax scripts.","first_name":"Rev","6":"Rev","last_name":"Lebaredian","7":"Lebaredian","releases":[{"0":"701","vim_version":"6.0","1":"6.0","script_version":".1","2":".1","version_comment":"Initial upload","3":"Initial upload","package":"cg.vim","4":"cg.vim","src_id":"2139","5":"2139","creation_date":"1057855933","6":"1057855933"}]},"700":{"script_id":"700","0":"700","script_name":"OIL.vim","1":"OIL.vim","script_type":"syntax","2":"syntax","summary":"A syntax file for the OSEK Implementation Language (OIL).","3":"A syntax file for the OSEK Implementation Language (OIL).","description":"This is the first version of a syntax file for OSEK Implementation Language (OIL) and OSEK Run Time Interface (ORTI). \r\nSee \"http:\/\/www.osek-vdx.org\" for more information about OIL and ORTI.","4":"This is the first version of a syntax file for OSEK Implementation Language (OIL) and OSEK Run Time Interface (ORTI). \r\nSee \"http:\/\/www.osek-vdx.org\" for more information about OIL and ORTI.","install_details":"1.) Copy the file to $VIM\/syntax. \r\n\r\n2.) Add to your $VIM\/filetype.vim : \r\nCUT FROM HERE--------> \r\nau BufEnter,BufRead,BufNewFile *.oil                 setfiletype oil\r\nau BufEnter,BufRead,BufNewFile *.OIL               setfiletype oil\r\nau BufEnter,BufRead,BufNewFile *.oilbase\t        setfiletype oil\r\nau BufEnter,BufRead,BufNewFile *.orti                setfiletype oil\r\nau BufEnter,BufRead,BufNewFile *.ORTI             setfiletype oil\r\n<--------CUT UNTIL HERE ","5":"1.) Copy the file to $VIM\/syntax. \r\n\r\n2.) Add to your $VIM\/filetype.vim : \r\nCUT FROM HERE--------> \r\nau BufEnter,BufRead,BufNewFile *.oil                 setfiletype oil\r\nau BufEnter,BufRead,BufNewFile *.OIL               setfiletype oil\r\nau BufEnter,BufRead,BufNewFile *.oilbase\t        setfiletype oil\r\nau BufEnter,BufRead,BufNewFile *.orti                setfiletype oil\r\nau BufEnter,BufRead,BufNewFile *.ORTI             setfiletype oil\r\n<--------CUT UNTIL HERE ","first_name":"Christian","6":"Christian","last_name":"Drothler","7":"Drothler","releases":[{"0":"700","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"oil.vim","4":"oil.vim","src_id":"2137","5":"2137","creation_date":"1057744308","6":"1057744308"}]},"699":{"script_id":"699","0":"699","script_name":"NEdit","1":"NEdit","script_type":"color scheme","2":"color scheme","summary":"A color scheme mimicking the way NEdit highlights C++ code","3":"A color scheme mimicking the way NEdit highlights C++ code","description":"This color scheme takes the colors from NEdit (http:\/\/www.nedit.org\/) C++ defaults. Note that NEdit recognizes a bit more syntax, so this \"Vim version\" is somewhat inferior to the original.","4":"This color scheme takes the colors from NEdit (http:\/\/www.nedit.org\/) C++ defaults. Note that NEdit recognizes a bit more syntax, so this \"Vim version\" is somewhat inferior to the original.","install_details":"In Vim 6, simply copy this file into your \"$VIMRUNTIME\/colors\/\" or \"$HOME\/.vim\/colors\/\", then use \":colorscheme oceandeep\". Otherwise, just \":source\" it.\r\n\r\nThe script might work fine in Vim 5.7 as well.","5":"In Vim 6, simply copy this file into your \"$VIMRUNTIME\/colors\/\" or \"$HOME\/.vim\/colors\/\", then use \":colorscheme oceandeep\". Otherwise, just \":source\" it.\r\n\r\nThe script might work fine in Vim 5.7 as well.","first_name":"Vladimir","6":"Vladimir","last_name":"Vrzic","7":"Vrzic","releases":[{"0":"699","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"nedit.vim","4":"nedit.vim","src_id":"2134","5":"2134","creation_date":"1057655406","6":"1057655406"}]},"698":{"script_id":"698","0":"698","script_name":"Visual C++","1":"Visual C++","script_type":"color scheme","2":"color scheme","summary":"A color scheme resembling the MS Visual C++ IDE","3":"A color scheme resembling the MS Visual C++ IDE","description":"A simple color scheme resembling the MS Visual C++ IDE, with maybe a little more highlighting (ie. constants).","4":"A simple color scheme resembling the MS Visual C++ IDE, with maybe a little more highlighting (ie. constants).","install_details":"In Vim 6, simply copy this file into your \"$VIMRUNTIME\/colors\/\" or \"$HOME\/.vim\/colors\/\", then use \":colorscheme oceandeep\". Otherwise, just \":source\" it.\r\n\r\nThe script might work fine in Vim 5.7 as well.","5":"In Vim 6, simply copy this file into your \"$VIMRUNTIME\/colors\/\" or \"$HOME\/.vim\/colors\/\", then use \":colorscheme oceandeep\". Otherwise, just \":source\" it.\r\n\r\nThe script might work fine in Vim 5.7 as well.","first_name":"Vladimir","6":"Vladimir","last_name":"Vrzic","7":"Vrzic","releases":[{"0":"698","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"vc.vim","4":"vc.vim","src_id":"2133","5":"2133","creation_date":"1057655004","6":"1057655004"}]},"697":{"script_id":"697","0":"697","script_name":"timecolor.vim","1":"timecolor.vim","script_type":"utility","2":"utility","summary":"let the time to rotate your colorschemes","3":"let the time to rotate your colorschemes","description":"vim script to associate a scheme of colors to the hours of the day  ---.\r\nused colorscheme: midnight, nightwish, coffee, morning, desert, shine, evening, night","4":"vim script to associate a scheme of colors to the hours of the day  ---.\r\nused colorscheme: midnight, nightwish, coffee, morning, desert, shine, evening, night","install_details":"copy to the $HOME\/.vim\/plugin directory","5":"copy to the $HOME\/.vim\/plugin directory","first_name":"nicolaie","6":"nicolaie","last_name":"george","7":"george","releases":[{"0":"697","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"timecolor.vim","4":"timecolor.vim","src_id":"2130","5":"2130","creation_date":"1057303072","6":"1057303072"}]},"696":{"script_id":"696","0":"696","script_name":"timecolor.vim","1":"timecolor.vim","script_type":"utility","2":"utility","summary":"let the time to rotate your colorschemes","3":"let the time to rotate your colorschemes","description":"vim script to associate a scheme of colors to the hours of the day --\r\nused colorschemes: midnight, nightwish, coffee, morning, desert, shine, evening, night","4":"vim script to associate a scheme of colors to the hours of the day --\r\nused colorschemes: midnight, nightwish, coffee, morning, desert, shine, evening, night","install_details":"copy to the $HOME\/.vim\/plugin directory","5":"copy to the $HOME\/.vim\/plugin directory","first_name":"nicolaie","6":"nicolaie","last_name":"george","7":"george","releases":[{"0":"696","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"timecolor.vim","4":"timecolor.vim","src_id":"2129","5":"2129","creation_date":"1057303000","6":"1057303000"}]},"695":{"script_id":"695","0":"695","script_name":"po.vim","1":"po.vim","script_type":"ftplugin","2":"ftplugin","summary":"ftplugin for easier editing of GNU gettext PO files","3":"ftplugin for easier editing of GNU gettext PO files","description":"This file is a Vim ftplugin for editing PO files (GNU gettext -- the GNU\r\ni18n and l10n system). It automates over a dozen frequent tasks that\r\noccur while editing files of this type.\r\n\r\n                                                                                    Key mappings\r\nAction (Insert mode)                                                GUI Vim     Vim\r\n===============================================================\r\nMove to an untransl. string forward                       <S-F1>      \\m\r\nMove to an untransl. string backward                   <S-F2>       \\p\r\nCopy the msgid string to msgstr                            <S-F3>      \\c\r\nDelete the msgstr string                                           <S-F4>      \\d\r\nMove to the next fuzzy translation                         <S-F5>       \\f\r\nMove to the previous fuzzy translation                 <S-F6>       \\b\r\nLabel the translation fuzzy                                       <S-F7>      \\z\r\nRemove the fuzzy label                                            <S-F8>      \\r\r\nShow msgfmt statistics for the file(*)                      <S-F11>     \\s\r\nBrowse through msgfmt errors for the file(*)         <S-F12>     \\e\r\nPut the translator info in the header                             \\t             \\t\r\nPut the lang. team info in the header                           \\l             \\l\r\n---------------------------------------------------------------\r\n(*) Only available on UNIX computers.\r\n\r\n\r\n                                                                                  Key mappings\r\nAction (Normal mode)                                           GUI Vim     Vim\r\n===============================================================\r\nMove to an untransl. string forward                      <S-F1>      \\m\r\nMove to an untransl. string backward                  <S-F2>      \\p\r\nMove to the next fuzzy translation                        <S-F5>      \\f\r\nMove to the previous fuzzy translation                <S-F6>      \\b\r\nLabel the translation fuzzy                                     <S-F7>      \\z\r\nRemove the fuzzy label                                          <S-F8>      \\r\r\nSplit-open the file under cursor                                  gf           gf\r\nShow msgfmt statistics for the file(*)                    <S-F11>     \\s\r\nBrowse through msgfmt errors for the file(*)       <S-F12>     \\e\r\nPut the translator info in the header                            \\t            \\t\r\nPut the lang. team info in the header                          \\l            \\l\r\n---------------------------------------------------------------\r\n(*) Only available on UNIX computers.\r\n\r\nRemarks:\r\n- \"S\" in the above key mappings stands for the <Shift> key and \"\\\" in\r\n  fact means \"<LocalLeader>\" (:help <LocalLeader>), which is \"\\\" by\r\n  Vim's default.\r\n- Information about the translator and language team is supplied by two\r\n  global variables: 'g:po_translator' and 'g:po_lang_team'. They should\r\n  be defined in the \".vimrc\" (UNIX) or \"_vimrc\" (Windows) file. If they\r\n  are not defined, the default values (descriptive strings) are put\r\n  instead.\r\n- Vim's \"gf\" Normal mode command is remapped (local to the PO buffer, of\r\n  course). It will only function on lines starting with \"#: \". Search\r\n  for the file is performed in the directories specified by the 'path'\r\n  option. The user can supply its own addition to this option via the\r\n  'g:po_path' global variable. Its default value for PO files can be\r\n  found by typing \":set path?\" from within a PO buffer. For the correct\r\n  format please see \":help 'path'\". Warning messages are printed if no\r\n  or more than one file is found.\r\n- Vim's Quickfix mode (see \":help quickfix\") is used for browsing\r\n  through msgfmt-reported errors for the file. No MO file is created\r\n  when running the msgfmt program since its output is directed to\r\n  \"\/dev\/null\". The user can supply command-line arguments to the msgfmt\r\n  program via the global variable 'g:po_msgfmt_args'. All arguments are\r\n  allowed except the \"-o\" for output file. The default value is\r\n  \"-vv -c\".\r\n\r\nBut there's even more!\r\n\r\nEvery time the PO file is saved, a PO-formatted time stamp is\r\nautomatically added to the file header.","4":"This file is a Vim ftplugin for editing PO files (GNU gettext -- the GNU\r\ni18n and l10n system). It automates over a dozen frequent tasks that\r\noccur while editing files of this type.\r\n\r\n                                                                                    Key mappings\r\nAction (Insert mode)                                                GUI Vim     Vim\r\n===============================================================\r\nMove to an untransl. string forward                       <S-F1>      \\m\r\nMove to an untransl. string backward                   <S-F2>       \\p\r\nCopy the msgid string to msgstr                            <S-F3>      \\c\r\nDelete the msgstr string                                           <S-F4>      \\d\r\nMove to the next fuzzy translation                         <S-F5>       \\f\r\nMove to the previous fuzzy translation                 <S-F6>       \\b\r\nLabel the translation fuzzy                                       <S-F7>      \\z\r\nRemove the fuzzy label                                            <S-F8>      \\r\r\nShow msgfmt statistics for the file(*)                      <S-F11>     \\s\r\nBrowse through msgfmt errors for the file(*)         <S-F12>     \\e\r\nPut the translator info in the header                             \\t             \\t\r\nPut the lang. team info in the header                           \\l             \\l\r\n---------------------------------------------------------------\r\n(*) Only available on UNIX computers.\r\n\r\n\r\n                                                                                  Key mappings\r\nAction (Normal mode)                                           GUI Vim     Vim\r\n===============================================================\r\nMove to an untransl. string forward                      <S-F1>      \\m\r\nMove to an untransl. string backward                  <S-F2>      \\p\r\nMove to the next fuzzy translation                        <S-F5>      \\f\r\nMove to the previous fuzzy translation                <S-F6>      \\b\r\nLabel the translation fuzzy                                     <S-F7>      \\z\r\nRemove the fuzzy label                                          <S-F8>      \\r\r\nSplit-open the file under cursor                                  gf           gf\r\nShow msgfmt statistics for the file(*)                    <S-F11>     \\s\r\nBrowse through msgfmt errors for the file(*)       <S-F12>     \\e\r\nPut the translator info in the header                            \\t            \\t\r\nPut the lang. team info in the header                          \\l            \\l\r\n---------------------------------------------------------------\r\n(*) Only available on UNIX computers.\r\n\r\nRemarks:\r\n- \"S\" in the above key mappings stands for the <Shift> key and \"\\\" in\r\n  fact means \"<LocalLeader>\" (:help <LocalLeader>), which is \"\\\" by\r\n  Vim's default.\r\n- Information about the translator and language team is supplied by two\r\n  global variables: 'g:po_translator' and 'g:po_lang_team'. They should\r\n  be defined in the \".vimrc\" (UNIX) or \"_vimrc\" (Windows) file. If they\r\n  are not defined, the default values (descriptive strings) are put\r\n  instead.\r\n- Vim's \"gf\" Normal mode command is remapped (local to the PO buffer, of\r\n  course). It will only function on lines starting with \"#: \". Search\r\n  for the file is performed in the directories specified by the 'path'\r\n  option. The user can supply its own addition to this option via the\r\n  'g:po_path' global variable. Its default value for PO files can be\r\n  found by typing \":set path?\" from within a PO buffer. For the correct\r\n  format please see \":help 'path'\". Warning messages are printed if no\r\n  or more than one file is found.\r\n- Vim's Quickfix mode (see \":help quickfix\") is used for browsing\r\n  through msgfmt-reported errors for the file. No MO file is created\r\n  when running the msgfmt program since its output is directed to\r\n  \"\/dev\/null\". The user can supply command-line arguments to the msgfmt\r\n  program via the global variable 'g:po_msgfmt_args'. All arguments are\r\n  allowed except the \"-o\" for output file. The default value is\r\n  \"-vv -c\".\r\n\r\nBut there's even more!\r\n\r\nEvery time the PO file is saved, a PO-formatted time stamp is\r\nautomatically added to the file header.","install_details":"    Put this file in a Vim ftplugin directory. On UNIX computers it is\r\n    usually either \"~\/.vim\/ftplugin\" or \"~\/.vim\/after\/ftplugin\". On Windows\r\n    computers, the defaults are \"$VIM\\vimfiles\\ftplugin\" or\r\n    \"$VIM\\vimfiles\\after\\ftplugin\". For more information consult the Vim\r\n    help, \":help 'ftplugin'\" and \":help 'runtimepath'\".\r\n","5":"    Put this file in a Vim ftplugin directory. On UNIX computers it is\r\n    usually either \"~\/.vim\/ftplugin\" or \"~\/.vim\/after\/ftplugin\". On Windows\r\n    computers, the defaults are \"$VIM\\vimfiles\\ftplugin\" or\r\n    \"$VIM\\vimfiles\\after\\ftplugin\". For more information consult the Vim\r\n    help, \":help 'ftplugin'\" and \":help 'runtimepath'\".\r\n","first_name":"Aleksandar","6":"Aleksandar","last_name":"Jelenak","7":"Jelenak","releases":[{"0":"695","vim_version":"6.0","1":"6.0","script_version":"1.2","2":"1.2","version_comment":"No major new features, mainly work under the hood to strengthen\r\ncurrent functionality.\r\n\r\nChanges:\r\n\r\n- Smarter handling of fuzzy translation marks\r\n- New key mappings for some commands in Normal mode\r\n- More commands available in Normal mode\r\n- gf mapping should hopefully be more useful now","3":"No major new features, mainly work under the hood to strengthen\r\ncurrent functionality.\r\n\r\nChanges:\r\n\r\n- Smarter handling of fuzzy translation marks\r\n- New key mappings for some commands in Normal mode\r\n- More commands available in Normal mode\r\n- gf mapping should hopefully be more useful now","package":"po.vim","4":"po.vim","src_id":"4159","5":"4159","creation_date":"1113381968","6":"1113381968"},{"0":"695","vim_version":"6.0","1":"6.0","script_version":"1.11","2":"1.11","version_comment":"Minor update to ver. 1.1: Running msgfmt statistics for the PO file does\r\nnot produce a 'message' output file anymore.\r\n","3":"Minor update to ver. 1.1: Running msgfmt statistics for the PO file does\r\nnot produce a 'message' output file anymore.\r\n","package":"po.vim","4":"po.vim","src_id":"2138","5":"2138","creation_date":"1057841644","6":"1057841644"}]},"694":{"script_id":"694","0":"694","script_name":"quancept.vim","1":"quancept.vim","script_type":"syntax","2":"syntax","summary":"Syntax file for SPSS Quancept scripts","3":"Syntax file for SPSS Quancept scripts","description":"Syntax file for SPSS Quancept scripts.\r\n\r\nBased on http:\/\/spss.com\/spssmr\/support\/mrinterview\/doc\/v1.2\/Scriptwriter.pdf\r\n\r\n\r\n\r\n","4":"Syntax file for SPSS Quancept scripts.\r\n\r\nBased on http:\/\/spss.com\/spssmr\/support\/mrinterview\/doc\/v1.2\/Scriptwriter.pdf\r\n\r\n\r\n\r\n","install_details":"Copy to syntax dir, modify your filetype.vim, or .vimrc.\r\n\r\nThis is created on a Windows machine, so you may want to run dos2unix on it before you use.","5":"Copy to syntax dir, modify your filetype.vim, or .vimrc.\r\n\r\nThis is created on a Windows machine, so you may want to run dos2unix on it before you use.","first_name":"Ferenc","6":"Ferenc","last_name":"Tamasi","7":"Tamasi","releases":[{"0":"694","vim_version":"6.0","1":"6.0","script_version":"0rc1b","2":"0rc1b","version_comment":"Different default question label handling by Daniel Harper. The old logic is still four comments away.","3":"Different default question label handling by Daniel Harper. The old logic is still four comments away.","package":"quancept.vim","4":"quancept.vim","src_id":"4259","5":"4259","creation_date":"1115602451","6":"1115602451"},{"0":"694","vim_version":"6.0","1":"6.0","script_version":"0rc1","2":"0rc1","version_comment":"Updated my mail address","3":"Updated my mail address","package":"quancept.vim","4":"quancept.vim","src_id":"3467","5":"3467","creation_date":"1095849613","6":"1095849613"},{"0":"694","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"quancept.vim","4":"quancept.vim","src_id":"2121","5":"2121","creation_date":"1057111482","6":"1057111482"}]},"693":{"script_id":"693","0":"693","script_name":"ample.vim","1":"ample.vim","script_type":"syntax","2":"syntax","summary":"Syntax Highlighting for MGC's AMPLE progamming language","3":"Syntax Highlighting for MGC's AMPLE progamming language","description":"This is a syntax highlight file for the AMPLE (Another Mentor Programming Language) programming language.  AMPLE is part of Mentor Graphics' Falcon Framework, a user interface framework.  Mentor Graphics Corporation is an EDA (Electronic Design Automation) company.  ","4":"This is a syntax highlight file for the AMPLE (Another Mentor Programming Language) programming language.  AMPLE is part of Mentor Graphics' Falcon Framework, a user interface framework.  Mentor Graphics Corporation is an EDA (Electronic Design Automation) company.  ","install_details":"1. place into $HOME\/.vim\/syntax \r\n\r\n2. :cal SetSyn(\"ample\") \r\nor \r\n2. put the following in $HOME\/.vimrc to autoload depending on filetype (in this case ends with .ample and .ascii) \r\n____________________________________________________________ \r\naugroup filetype \r\n    au! \r\n    au! BufRead,BufNewFile *.ample  set filetype=ample\r\n    au! BufRead,BufNewFile *.ascii     set filetype=ample\r\naugroup END \r\n____________________________________________________________ \r\n:help autocmd for more info","5":"1. place into $HOME\/.vim\/syntax \r\n\r\n2. :cal SetSyn(\"ample\") \r\nor \r\n2. put the following in $HOME\/.vimrc to autoload depending on filetype (in this case ends with .ample and .ascii) \r\n____________________________________________________________ \r\naugroup filetype \r\n    au! \r\n    au! BufRead,BufNewFile *.ample  set filetype=ample\r\n    au! BufRead,BufNewFile *.ascii     set filetype=ample\r\naugroup END \r\n____________________________________________________________ \r\n:help autocmd for more info","first_name":"Alvin","6":"Alvin","last_name":"Santos","7":"Santos","releases":[{"0":"693","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"ample.vim","4":"ample.vim","src_id":"2118","5":"2118","creation_date":"1056825939","6":"1056825939"}]},"692":{"script_id":"692","0":"692","script_name":"VimSpeak","1":"VimSpeak","script_type":"utility","2":"utility","summary":"Speak selected text with MS Agent","3":"Speak selected text with MS Agent","description":"This calls MS AGENT and speaks (range) selected text.\r\nUsage:\r\n  [range]VimSpeak\r\n","4":"This calls MS AGENT and speaks (range) selected text.\r\nUsage:\r\n  [range]VimSpeak\r\n","install_details":"copy vimspeak.dll to same directory with gvim.exe\r\ncopy vimspeak.vim to your $VIMRUNTIME\/plugin\r\n","5":"copy vimspeak.dll to same directory with gvim.exe\r\ncopy vimspeak.vim to your $VIMRUNTIME\/plugin\r\n","first_name":"Yasuhiro","6":"Yasuhiro","last_name":"Matsumoto","7":"Matsumoto","releases":[{"0":"692","vim_version":"7.0","1":"7.0","script_version":"0.3","2":"0.3","version_comment":"Rewrite.\n","3":"Rewrite.\n","package":"vimspeak-vim.zip","4":"vimspeak-vim.zip","src_id":"17890","5":"17890","creation_date":"1336379960","6":"1336379960"},{"0":"692","vim_version":"6.0","1":"6.0","script_version":"0.2","2":"0.2","version_comment":"This is un upgrade for VimSpeak. it can get langid from GetUserDefaultLCID().","3":"This is un upgrade for VimSpeak. it can get langid from GetUserDefaultLCID().","package":"VimSpeak.zip","4":"VimSpeak.zip","src_id":"2119","5":"2119","creation_date":"1056942393","6":"1056942393"},{"0":"692","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"VimSpeak.zip","4":"VimSpeak.zip","src_id":"2115","5":"2115","creation_date":"1056652943","6":"1056652943"}]},"691":{"script_id":"691","0":"691","script_name":"POD Folder","1":"POD Folder","script_type":"utility","2":"utility","summary":"Creates folds in POD files based on =head[123] sections","3":"Creates folds in POD files based on =head[123] sections","description":"I wrote this script because I've been working on a project with a lot of POD documentation, and have discovered that it's easier for me to keep track of things if I fold the document accoring to the various =head sections\n\nThis script uses manual folding, because it was quicker to figure out than syntax folding.","4":"I wrote this script because I've been working on a project with a lot of POD documentation, and have discovered that it's easier for me to keep track of things if I fold the document accoring to the various =head sections\n\nThis script uses manual folding, because it was quicker to figure out than syntax folding.","install_details":"","5":"","first_name":"Mark","6":"Mark","last_name":"Jaroski","7":"Jaroski","releases":[{"0":"691","vim_version":"6.0","1":"6.0","script_version":"0.95","2":"0.95","version_comment":"Initial upload","3":"Initial upload","package":"pod_folder.vim","4":"pod_folder.vim","src_id":"2114","5":"2114","creation_date":"1056601060","6":"1056601060"}]},"690":{"script_id":"690","0":"690","script_name":"actionscript.vim","1":"actionscript.vim","script_type":"syntax","2":"syntax","summary":"Actionscript syntax","3":"Actionscript syntax","description":"A syntax file for editing Flash actionscript with Vim.\r\n\r\nAdd this command to your vimrc file:\r\nau BufNewFile,BufRead *.as\tsetf actionscript\r\n\r\nand delete or otherwise override the default mapping of .as files to Atlas","4":"A syntax file for editing Flash actionscript with Vim.\r\n\r\nAdd this command to your vimrc file:\r\nau BufNewFile,BufRead *.as\tsetf actionscript\r\n\r\nand delete or otherwise override the default mapping of .as files to Atlas","install_details":"put this in vimfiles\/syntax","5":"put this in vimfiles\/syntax","first_name":"Adam","6":"Adam","last_name":"Wolff","7":"Wolff","releases":[{"0":"690","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"actionscript.vim","4":"actionscript.vim","src_id":"2111","5":"2111","creation_date":"1056445461","6":"1056445461"}]},"689":{"script_id":"689","0":"689","script_name":"cleanphp","1":"cleanphp","script_type":"color scheme","2":"color scheme","summary":"Highlights most php syntax with neat colour scheme","3":"Highlights most php syntax with neat colour scheme","description":"Feel free to enhance this colour scheme.","4":"Feel free to enhance this colour scheme.","install_details":"Place within your $VIM\/colors directory.","5":"Place within your $VIM\/colors directory.","first_name":"Billy","6":"Billy","last_name":"McIntosh","7":"McIntosh","releases":[{"0":"689","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"cleanphp.vim","4":"cleanphp.vim","src_id":"2109","5":"2109","creation_date":"1056423527","6":"1056423527"}]},"688":{"script_id":"688","0":"688","script_name":"calibre.vim","1":"calibre.vim","script_type":"syntax","2":"syntax","summary":"Syntax Highlight for MGC SVRF (Calibre) Standard Verification Rules Format","3":"Syntax Highlight for MGC SVRF (Calibre) Standard Verification Rules Format","description":"This is a syntax highlight file for Mentor Graphics Physical Extraction and Verification tool suite, Calibre.  It highlights Calibre's rules language SVRF - Standard Verification Rules Format.  Mentor Graphics Corporation is an Electronic Design Automation (EDA) company.\r\n\r\nI am no longer allowed to freely distribute this file as the SVRF language belongs to Mentor Graphics.  Please contact your Mentor Sales representative for further assistance.\r\n\r\nIf you are a Mentor Customer and have a support contract - the file is now available through http:\/\/supportnet.mentor.com\r\n\r\nIt will be in the Downloads tab - under related downloads - 'Calibre Utilities, Example, Scripts and Interface Software' page\r\n\r\nIt will be under the All Calibre Products","4":"This is a syntax highlight file for Mentor Graphics Physical Extraction and Verification tool suite, Calibre.  It highlights Calibre's rules language SVRF - Standard Verification Rules Format.  Mentor Graphics Corporation is an Electronic Design Automation (EDA) company.\r\n\r\nI am no longer allowed to freely distribute this file as the SVRF language belongs to Mentor Graphics.  Please contact your Mentor Sales representative for further assistance.\r\n\r\nIf you are a Mentor Customer and have a support contract - the file is now available through http:\/\/supportnet.mentor.com\r\n\r\nIt will be in the Downloads tab - under related downloads - 'Calibre Utilities, Example, Scripts and Interface Software' page\r\n\r\nIt will be under the All Calibre Products","install_details":"1. place into $HOME\/.vim\/syntax\r\n\r\n2. for gvim :cal SetSyn(\"calibre\")  for vim :set filetype=calibre\r\nor\r\n2. put the following in $HOME\/.vimrc to autoload depending on filetype (in this case ends with .rules and .rul)\r\n____________________________________________________________\r\naugroup filetype\r\n    au!\r\n    au! BufRead,BufNewFile *.rules  set filetype=calibre\r\n    au! BufRead,BufNewFile *.rul     set filetype=calibre\r\naugroup END\r\n____________________________________________________________\r\n:help autocmd for more info","5":"1. place into $HOME\/.vim\/syntax\r\n\r\n2. for gvim :cal SetSyn(\"calibre\")  for vim :set filetype=calibre\r\nor\r\n2. put the following in $HOME\/.vimrc to autoload depending on filetype (in this case ends with .rules and .rul)\r\n____________________________________________________________\r\naugroup filetype\r\n    au!\r\n    au! BufRead,BufNewFile *.rules  set filetype=calibre\r\n    au! BufRead,BufNewFile *.rul     set filetype=calibre\r\naugroup END\r\n____________________________________________________________\r\n:help autocmd for more info","first_name":"Alvin","6":"Alvin","last_name":"Santos","7":"Santos","releases":[{"0":"688","vim_version":"6.0","1":"6.0","script_version":"0.5","2":"0.5","version_comment":"No Longer allowed to distribute - please call your Mentor office","3":"No Longer allowed to distribute - please call your Mentor office","package":"calibre.vim","4":"calibre.vim","src_id":"12907","5":"12907","creation_date":"1272329088","6":"1272329088"}]},"687":{"script_id":"687","0":"687","script_name":"VimTweak","1":"VimTweak","script_type":"utility","2":"utility","summary":"The tweaking dll for GVim.exe.","3":"The tweaking dll for GVim.exe.","description":"This should work on Win2k (or WinXP maybe)\r\n\r\nAlpha Window:\r\n  200\/255 alpha\r\n  :call libcallnr(\"vimtweak.dll\", \"SetAlpha\", 200)\r\n  reset alpha\r\n  :call libcallnr(\"vimtweak.dll\", \"SetAlpha\", 255)\r\n\r\nMaximized Window:\r\n  Enable\r\n  :call libcallnr(\"vimtweak.dll\", \"EnableMaximize\", 1)\r\n  Disable\r\n  :call libcallnr(\"vimtweak.dll\", \"EnableMaximize\", 0)\r\n\r\nTopMost Window:\r\n  Enable\r\n  :call libcallnr(\"vimtweak.dll\", \"EnableTopMost\", 1)\r\n  Disable\r\n  :call libcallnr(\"vimtweak.dll\", \"EnableTopMost\", 0)\r\n","4":"This should work on Win2k (or WinXP maybe)\r\n\r\nAlpha Window:\r\n  200\/255 alpha\r\n  :call libcallnr(\"vimtweak.dll\", \"SetAlpha\", 200)\r\n  reset alpha\r\n  :call libcallnr(\"vimtweak.dll\", \"SetAlpha\", 255)\r\n\r\nMaximized Window:\r\n  Enable\r\n  :call libcallnr(\"vimtweak.dll\", \"EnableMaximize\", 1)\r\n  Disable\r\n  :call libcallnr(\"vimtweak.dll\", \"EnableMaximize\", 0)\r\n\r\nTopMost Window:\r\n  Enable\r\n  :call libcallnr(\"vimtweak.dll\", \"EnableTopMost\", 1)\r\n  Disable\r\n  :call libcallnr(\"vimtweak.dll\", \"EnableTopMost\", 0)\r\n","install_details":"copy vimtweak.dll to same directory with gvim.exe","5":"copy vimtweak.dll to same directory with gvim.exe","first_name":"Yasuhiro","6":"Yasuhiro","last_name":"Matsumoto","7":"Matsumoto","releases":[{"0":"687","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"vimtweak.zip","4":"vimtweak.zip","src_id":"2103","5":"2103","creation_date":"1056052269","6":"1056052269"}]},"686":{"script_id":"686","0":"686","script_name":"feralalign.vim","1":"feralalign.vim","script_type":"utility","2":"utility","summary":"Simple script to save you from \"ciw<tab><tab><tab>\" to align text.","3":"Simple script to save you from \"ciw<tab><tab><tab>\" to align text.","description":"Simple script that allows you to easily tab a section of spaces to a desired\r\ncolumn; I.e. if you want all your comments to line up on virt col 41 try\r\n\":FeralAlign 41\" when your cursor is in a position to \"ciw\"; I.e. saves you\r\nfrom \"ciw<tab><tab><tab>\"etc. But that is about all this does (=\r\n\r\nWorks with single lines or ranges. Ranges must be specified by a single column,\r\nblock-wise visual selection; (i.e. \"<ctrl-v>j\"). So to align 5 lines, place\r\nyour cursor in a good spot (where a \"ciw\" won\u00e2\u0080\u0099t keel something important; i.e.\r\nspaces before the comment chars) and \"<ctrl-v>4j:FeralAlign 41\"; easy as that.\r\n\r\nLimitation: Aligns to the nearest tabstop.\r\n\r\nThis script is possibly of academic value as a way to get a range command to\r\npreserve the cursor\u00e2\u0080\u0099s column.","4":"Simple script that allows you to easily tab a section of spaces to a desired\r\ncolumn; I.e. if you want all your comments to line up on virt col 41 try\r\n\":FeralAlign 41\" when your cursor is in a position to \"ciw\"; I.e. saves you\r\nfrom \"ciw<tab><tab><tab>\"etc. But that is about all this does (=\r\n\r\nWorks with single lines or ranges. Ranges must be specified by a single column,\r\nblock-wise visual selection; (i.e. \"<ctrl-v>j\"). So to align 5 lines, place\r\nyour cursor in a good spot (where a \"ciw\" won\u00e2\u0080\u0099t keel something important; i.e.\r\nspaces before the comment chars) and \"<ctrl-v>4j:FeralAlign 41\"; easy as that.\r\n\r\nLimitation: Aligns to the nearest tabstop.\r\n\r\nThis script is possibly of academic value as a way to get a range command to\r\npreserve the cursor\u00e2\u0080\u0099s column.","install_details":"This is a normal vim60 plugin.  Just drop it in \/plugin\/","5":"This is a normal vim60 plugin.  Just drop it in \/plugin\/","first_name":"Robert","6":"Robert","last_name":"KellyIV","7":"KellyIV","releases":[{"0":"686","vim_version":"6.0","1":"6.0","script_version":"0.4","2":"0.4","version_comment":"As of 0.4 you can bang :FeralAlign to use the space (\\s*) between ; and first non space (\\S) chars, i.e. C++ style end of line comments.\r\nAdded :FeralAlign2 which is basically a shortcut for :FeralAlign! virtcol(\".\")\r\nRemmed out :FeralAlignMarkedCol, etc.","3":"As of 0.4 you can bang :FeralAlign to use the space (\\s*) between ; and first non space (\\S) chars, i.e. C++ style end of line comments.\r\nAdded :FeralAlign2 which is basically a shortcut for :FeralAlign! virtcol(\".\")\r\nRemmed out :FeralAlignMarkedCol, etc.","package":"feralalign.vim","4":"feralalign.vim","src_id":"3314","5":"3314","creation_date":"1092185621","6":"1092185621"},{"0":"686","vim_version":"6.0","1":"6.0","script_version":"0.3","2":"0.3","version_comment":"Initial upload","3":"Initial upload","package":"feralalign.vim","4":"feralalign.vim","src_id":"2097","5":"2097","creation_date":"1055959207","6":"1055959207"}]},"685":{"script_id":"685","0":"685","script_name":"incbufswitch.vim","1":"incbufswitch.vim","script_type":"utility","2":"utility","summary":"Switch buffers using an incremental search","3":"Switch buffers using an incremental search","description":"Switch to a different buffer in the current window by incrementally typing the name.\r\n\r\nUsage:\r\n\r\n(1) Define a normal key mapping to :IncBufSwitch or leave the default of <C-S>\r\n(2) In normal mode, start typing the name of the buffer you want to switch to.\r\n(3) Press <BS> if make an error\r\n(4) Press <TAB> to find the next matching buffer\r\n(5) Press either <CR> or <ESC> when you are done\r\n\r\nFor example, if you have the following files in memory:\r\n\r\nfoo.c, bar.c, baz.c, structs.h\r\n\r\nand you are currently editing foo.c.\r\n\r\nExample 1: You press <C-S> and type s<CR>.  You are now editing structs.h.\r\nExample 2: You press <C-S> and type b.  Buffer switches to bar.c.  If you press <TAB> baz.c enters the window.\r\n\r\nThe project I work on has a LOT of files.  It is not uncommon to have 20-30 files in memory at any given time.  I find that this allows me to switch amongst them much faster.\r\n\r\nLet me know of any ideas or problems.","4":"Switch to a different buffer in the current window by incrementally typing the name.\r\n\r\nUsage:\r\n\r\n(1) Define a normal key mapping to :IncBufSwitch or leave the default of <C-S>\r\n(2) In normal mode, start typing the name of the buffer you want to switch to.\r\n(3) Press <BS> if make an error\r\n(4) Press <TAB> to find the next matching buffer\r\n(5) Press either <CR> or <ESC> when you are done\r\n\r\nFor example, if you have the following files in memory:\r\n\r\nfoo.c, bar.c, baz.c, structs.h\r\n\r\nand you are currently editing foo.c.\r\n\r\nExample 1: You press <C-S> and type s<CR>.  You are now editing structs.h.\r\nExample 2: You press <C-S> and type b.  Buffer switches to bar.c.  If you press <TAB> baz.c enters the window.\r\n\r\nThe project I work on has a LOT of files.  It is not uncommon to have 20-30 files in memory at any given time.  I find that this allows me to switch amongst them much faster.\r\n\r\nLet me know of any ideas or problems.","install_details":"(1) Drop in your plugin directory\r\n\r\n(2) The default key mapping of <C-S> will get you started.  If you like, define your own mapping and the script will use that.  See the script header for details.","5":"(1) Drop in your plugin directory\r\n\r\n(2) The default key mapping of <C-S> will get you started.  If you like, define your own mapping and the script will use that.  See the script header for details.","first_name":"Michael","6":"Michael","last_name":"Denio","7":"Denio","releases":[{"0":"685","vim_version":"6.0","1":"6.0","script_version":"1.1","2":"1.1","version_comment":"Added <TAB> command to find next matching buffer, <ESC> now returns to originating buffer.","3":"Added <TAB> command to find next matching buffer, <ESC> now returns to originating buffer.","package":"incbufswitch.vim","4":"incbufswitch.vim","src_id":"2110","5":"2110","creation_date":"1056435514","6":"1056435514"},{"0":"685","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"incbufswitch.vim","4":"incbufswitch.vim","src_id":"2095","5":"2095","creation_date":"1055922217","6":"1055922217"}]},"684":{"script_id":"684","0":"684","script_name":"Comment Tools","1":"Comment Tools","script_type":"utility","2":"utility","summary":"Insert or align comments (+ruby required!)","3":"Insert or align comments (+ruby required!)","description":"The Comment Tools are a set of scripts that allow you to manipulate comments (insert or align them).\r\n\r\nThey require Vim 6.x with Ruby support compiled in.","4":"The Comment Tools are a set of scripts that allow you to manipulate comments (insert or align them).\r\n\r\nThey require Vim 6.x with Ruby support compiled in.","install_details":"","5":"","first_name":"Johannes","6":"Johannes","last_name":"Tanzler","7":"Tanzler","releases":[{"0":"684","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"comment-tools.tar.bz2","4":"comment-tools.tar.bz2","src_id":"2090","5":"2090","creation_date":"1055857257","6":"1055857257"}]},"683":{"script_id":"683","0":"683","script_name":"ftplugin for Calendar","1":"ftplugin for Calendar","script_type":"ftplugin","2":"ftplugin","summary":"This is a ftplugin for Calenar.","3":"This is a ftplugin for Calenar.","description":"You can do following on diary.\r\nPutting current time with typeing <localleader>z.\r\nIf you want to customize behavior of editing diary,\r\n Please modify this file.","4":"You can do following on diary.\r\nPutting current time with typeing <localleader>z.\r\nIf you want to customize behavior of editing diary,\r\n Please modify this file.","install_details":"copy this file to your ftplugin directory.","5":"copy this file to your ftplugin directory.","first_name":"Yasuhiro","6":"Yasuhiro","last_name":"Matsumoto","7":"Matsumoto","releases":[{"0":"683","vim_version":"6.0","1":"6.0","script_version":"1.3s","2":"1.3s","version_comment":"Initial upload","3":"Initial upload","package":"calendar.vim","4":"calendar.vim","src_id":"2089","5":"2089","creation_date":"1055824102","6":"1055824102"}]},"682":{"script_id":"682","0":"682","script_name":"cschemerotate.vim","1":"cschemerotate.vim","script_type":"utility","2":"utility","summary":"Fast colorscheme switching","3":"Fast colorscheme switching","description":"Lame but fast (just ,b) switching of (now 3) different colorschemes. Useful when frequently switching between system console and transparent aterm window.","4":"Lame but fast (just ,b) switching of (now 3) different colorschemes. Useful when frequently switching between system console and transparent aterm window.","install_details":"copy to $HOME\/.vim\/plugin directory (or its equivalent under Windoze)","5":"copy to $HOME\/.vim\/plugin directory (or its equivalent under Windoze)","first_name":"Rafal","6":"Rafal","last_name":"Sulejman","7":"Sulejman","releases":[{"0":"682","vim_version":"6.0","1":"6.0","script_version":"0.2","2":"0.2","version_comment":"parametrized, commented version using user's favourite colorschema (if set) as default.","3":"parametrized, commented version using user's favourite colorschema (if set) as default.","package":"cschemerotate.vim","4":"cschemerotate.vim","src_id":"2094","5":"2094","creation_date":"1055900811","6":"1055900811"}]},"681":{"script_id":"681","0":"681","script_name":"blockhl2.vim","1":"blockhl2.vim","script_type":"syntax","2":"syntax","summary":"Improved highlighting different levels of {} in C and C++ based on blockhl.vim","3":"Improved highlighting different levels of {} in C and C++ based on blockhl.vim","description":"This took vimscript#104 blockhi.vim and modified it for highlight the curly brackets using primary colors ie green red blue cyan yellow pink and also allowed for coloring the leading spaces (ie begin of line to first non spaces) instead of the whole code block between curly brackets. \r\n\r\nI didn't like how blockhi.vim highlight the code part with background as grey.\r\nI wanted only the leading spaces hilighted.\r\nAlso added filetype and load checking just to be realy safe.\r\nAdded cpp cluster group for cpp files.\r\n\r\nIt has two main functions:\r\nHilightBrackets() truns on hilighting and hilight.\r\nNoHilightBracktes() turns off hilighting clears syntax\r\nhas two toggle function with cab to run\r\ntoghib toggles the block hilighting on or off\r\ntoghibs toggles the leading space hilighting on or off but does not toggle block hilighting it self.\r\nColors cycle over if bracket level is more then Curly region were defined.\r\n\r\nIf you what more levels (it only has 6 right now) you can change by adding more bracket and lsp matches and more cCurly regions.\r\nJust remember to have last bracket# set as hi bracket# guifg=NONE\r\nand lsp# set  hi lsp# guibg=NONE were # is the one past highest color level.\r\nThis make sure you don't have all leading spaces in file hilighted all the time.\r\n\r\nI have a way to highlight only the block your in, using a modified vimscript#626 ShowPairs.vim\r\nBut it not quite there yet.\r\nI will mostly merge it in with this script since it uses some of this scripts members.\r\nComing soon.\r\n\r\n","4":"This took vimscript#104 blockhi.vim and modified it for highlight the curly brackets using primary colors ie green red blue cyan yellow pink and also allowed for coloring the leading spaces (ie begin of line to first non spaces) instead of the whole code block between curly brackets. \r\n\r\nI didn't like how blockhi.vim highlight the code part with background as grey.\r\nI wanted only the leading spaces hilighted.\r\nAlso added filetype and load checking just to be realy safe.\r\nAdded cpp cluster group for cpp files.\r\n\r\nIt has two main functions:\r\nHilightBrackets() truns on hilighting and hilight.\r\nNoHilightBracktes() turns off hilighting clears syntax\r\nhas two toggle function with cab to run\r\ntoghib toggles the block hilighting on or off\r\ntoghibs toggles the leading space hilighting on or off but does not toggle block hilighting it self.\r\nColors cycle over if bracket level is more then Curly region were defined.\r\n\r\nIf you what more levels (it only has 6 right now) you can change by adding more bracket and lsp matches and more cCurly regions.\r\nJust remember to have last bracket# set as hi bracket# guifg=NONE\r\nand lsp# set  hi lsp# guibg=NONE were # is the one past highest color level.\r\nThis make sure you don't have all leading spaces in file hilighted all the time.\r\n\r\nI have a way to highlight only the block your in, using a modified vimscript#626 ShowPairs.vim\r\nBut it not quite there yet.\r\nI will mostly merge it in with this script since it uses some of this scripts members.\r\nComing soon.\r\n\r\n","install_details":"I created a other directory under ~\/.vim and put this there ie ~\/.vim\/other\/.\r\nthen in the ~\/.vim\/after\/syntax dir I created a c.vim that source this file.\r\nalso created a link to c.vim as cpp.vim.\r\nThis was on a unix systems.\r\nwere ~\/ is user's home dir.\r\nfile should be save in unix file format (ie no ^M's).","5":"I created a other directory under ~\/.vim and put this there ie ~\/.vim\/other\/.\r\nthen in the ~\/.vim\/after\/syntax dir I created a c.vim that source this file.\r\nalso created a link to c.vim as cpp.vim.\r\nThis was on a unix systems.\r\nwere ~\/ is user's home dir.\r\nfile should be save in unix file format (ie no ^M's).","first_name":"Lord","6":"Lord","last_name":"Bart","7":"Bart","releases":[{"0":"681","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"blockhl2.vim","4":"blockhl2.vim","src_id":"2086","5":"2086","creation_date":"1055776236","6":"1055776236"}]},"680":{"script_id":"680","0":"680","script_name":"ferallastchange.vim","1":"ferallastchange.vim","script_type":"utility","2":"utility","summary":"FORK of lastchange.vim; Automatic update of timestamp line in file.","3":"FORK of lastchange.vim; Automatic update of timestamp line in file.","description":"Update the last modification time of the file if an appropriate string is found in the first 20 lines of the file.\r\n\r\nThis is a fork of lastchange.vim and is based On Srinath Avadhanula's <email in file> work in lastchange.vim (v1.0 dated Sat Mar 30 04:00 PM 2002 PST; VIMSCRIPT #259)\r\n\r\n\r\nChanges: From lastchange.vim v1.0\r\n\r\nThis is now an almost proper vim60 plugin.\r\n\r\nTime stamp can be defined by setting g:flastchangetimeformat to the desired string for strftime().\r\n\r\nExample: (from my .vimrc)\r\n\" [Feral:166\/03@13:11] How I like ferallastchange.vim setup\r\nlet g:flastchangeleader = '\\\\date\\t\\t'\r\n\" Condense `Pacific Daylight Time` into `PDT` and tack that onto the end of our\r\n\"\ttime stamp format string\r\nlet g:flastchangetimeformat = '%a, %d %b %Y %H:%M '.substitute(strftime('%Z'), '\\<\\(\\w\\)\\(\\w*\\)\\>\\(\\W\\|$\\)', '\\1', 'g')\r\n\r\nNOTE how format %Z is special cased and replaced with a shortened string. I.e. `Pacific Daylight Time` becomes `PDT`. This is also done in the default time format string.\r\n\r\nSlightly more robust checking to see if we should operate; to speed up writing when we have nothing to do or can't do anything, etc.;\r\n\r\n\r\nSimplified and fixed, (then removed altogether) RemoveLastHistoryItem(); (could muck up search pattern)\r\n\r\nRemed out :MOD and :NOMOD commands; I have never used them; Just unrem if wanted...\r\n\r\n:sub method remed; Currently uses a setline, hopefully more efficient.\r\n\r\nLimitation:\r\nThe search to find the timestamp messes with the jumplist; I do not want it to; will fix when I know how!\r\nUpdating the timestamp is part of undo, thus you have to undo twice after a :w (Once to undo the timestamp and again to undo whatever it is you wanted to undo.)\r\n\r\nNOTE: v1.1 (initial; no longer available) had a FATAL boo boo in my attempt to\r\nget the timestamp updating out of undo. It changes undolevels to -1 (and then\r\nsets it back to what it was), this has the undesired effect of flushing your\r\nundo information for the file when ever you write. NOT at all what I had\r\nintended. If you use v1.1 now, please update to v1.2 ASAP. My sincere apologies\r\nfor any work lost as the result of this bungle.","4":"Update the last modification time of the file if an appropriate string is found in the first 20 lines of the file.\r\n\r\nThis is a fork of lastchange.vim and is based On Srinath Avadhanula's <email in file> work in lastchange.vim (v1.0 dated Sat Mar 30 04:00 PM 2002 PST; VIMSCRIPT #259)\r\n\r\n\r\nChanges: From lastchange.vim v1.0\r\n\r\nThis is now an almost proper vim60 plugin.\r\n\r\nTime stamp can be defined by setting g:flastchangetimeformat to the desired string for strftime().\r\n\r\nExample: (from my .vimrc)\r\n\" [Feral:166\/03@13:11] How I like ferallastchange.vim setup\r\nlet g:flastchangeleader = '\\\\date\\t\\t'\r\n\" Condense `Pacific Daylight Time` into `PDT` and tack that onto the end of our\r\n\"\ttime stamp format string\r\nlet g:flastchangetimeformat = '%a, %d %b %Y %H:%M '.substitute(strftime('%Z'), '\\<\\(\\w\\)\\(\\w*\\)\\>\\(\\W\\|$\\)', '\\1', 'g')\r\n\r\nNOTE how format %Z is special cased and replaced with a shortened string. I.e. `Pacific Daylight Time` becomes `PDT`. This is also done in the default time format string.\r\n\r\nSlightly more robust checking to see if we should operate; to speed up writing when we have nothing to do or can't do anything, etc.;\r\n\r\n\r\nSimplified and fixed, (then removed altogether) RemoveLastHistoryItem(); (could muck up search pattern)\r\n\r\nRemed out :MOD and :NOMOD commands; I have never used them; Just unrem if wanted...\r\n\r\n:sub method remed; Currently uses a setline, hopefully more efficient.\r\n\r\nLimitation:\r\nThe search to find the timestamp messes with the jumplist; I do not want it to; will fix when I know how!\r\nUpdating the timestamp is part of undo, thus you have to undo twice after a :w (Once to undo the timestamp and again to undo whatever it is you wanted to undo.)\r\n\r\nNOTE: v1.1 (initial; no longer available) had a FATAL boo boo in my attempt to\r\nget the timestamp updating out of undo. It changes undolevels to -1 (and then\r\nsets it back to what it was), this has the undesired effect of flushing your\r\nundo information for the file when ever you write. NOT at all what I had\r\nintended. If you use v1.1 now, please update to v1.2 ASAP. My sincere apologies\r\nfor any work lost as the result of this bungle.","install_details":"Drop in plugin directory.\r\nMake sure you are using lastchange.vim OR ferallastchange.vim but NOT BOTH.","5":"Drop in plugin directory.\r\nMake sure you are using lastchange.vim OR ferallastchange.vim but NOT BOTH.","first_name":"Robert","6":"Robert","last_name":"KellyIV","7":"KellyIV","releases":[{"0":"680","vim_version":"6.0","1":"6.0","script_version":"1.23","2":"1.23","version_comment":"Improved\/Fixed cursor restore. Screen should not jump; ever.","3":"Improved\/Fixed cursor restore. Screen should not jump; ever.","package":"ferallastchange.vim","4":"ferallastchange.vim","src_id":"4216","5":"4216","creation_date":"1114697234","6":"1114697234"},{"0":"680","vim_version":"6.0","1":"6.0","script_version":"1.2","2":"1.2","version_comment":"Thanks to Asier for pointing out messing with undolevels is not at all what I had intended.\r\nBUG FIX:\r\n    * no longer messes with undolevels.\r\nChanges:\r\n    * Changed method used to change the time stamp (now using setline() );\r\n    * removed RemoveLastHistoryItem()\r\nLimitation:\r\n    * You have to undo twice after just :w now (first time to undo the timestamp\r\n        change, the second time to undo whatever it was you wanted to undo.)","3":"Thanks to Asier for pointing out messing with undolevels is not at all what I had intended.\r\nBUG FIX:\r\n    * no longer messes with undolevels.\r\nChanges:\r\n    * Changed method used to change the time stamp (now using setline() );\r\n    * removed RemoveLastHistoryItem()\r\nLimitation:\r\n    * You have to undo twice after just :w now (first time to undo the timestamp\r\n        change, the second time to undo whatever it was you wanted to undo.)","package":"ferallastchange.vim","4":"ferallastchange.vim","src_id":"2131","5":"2131","creation_date":"1057365985","6":"1057365985"}]},"679":{"script_id":"679","0":"679","script_name":"fluxbox.vim","1":"fluxbox.vim","script_type":"syntax","2":"syntax","summary":"syntax and indent files for fluxbox wm menu file","3":"syntax and indent files for fluxbox wm menu file","description":"This includes two files, one is a syntax file for the menu file of the fluxbox (and also blackbox) window manager, and the other is an indent file for the same menu file. The indent file depends on the GenericIndent function in the genindent.vim plugin (vimscript #678).","4":"This includes two files, one is a syntax file for the menu file of the fluxbox (and also blackbox) window manager, and the other is an indent file for the same menu file. The indent file depends on the GenericIndent function in the genindent.vim plugin (vimscript #678).","install_details":"In a runtimepath directory:\r\ngunzip fluxbox.tar.gz\r\ntar xvf fluxbox.tar\r\n","5":"In a runtimepath directory:\r\ngunzip fluxbox.tar.gz\r\ntar xvf fluxbox.tar\r\n","first_name":"moshe","6":"moshe","last_name":"kamensky","7":"kamensky","releases":[{"0":"679","vim_version":"6.0","1":"6.0","script_version":"1.5","2":"1.5","version_comment":"1. Added the 'commanddialog' keyword\n\n2. Fixed icon support to allow icons for menu entries.\n\n3. Fixed folding, so that '# [end]' doesn't close a fold.","3":"1. Added the 'commanddialog' keyword\n\n2. Fixed icon support to allow icons for menu entries.\n\n3. Fixed folding, so that '# [end]' doesn't close a fold.","package":"fluxbox.tar.gz","4":"fluxbox.tar.gz","src_id":"3555","5":"3555","creation_date":"1098020630","6":"1098020630"},{"0":"679","vim_version":"6.0","1":"6.0","script_version":"1.4","2":"1.4","version_comment":"Updated for fluxbox version 0.9.10","3":"Updated for fluxbox version 0.9.10","package":"fluxbox.tar.gz","4":"fluxbox.tar.gz","src_id":"3421","5":"3421","creation_date":"1094219048","6":"1094219048"},{"0":"679","vim_version":"6.0","1":"6.0","script_version":"1.3","2":"1.3","version_comment":"Added the 'separator' keyword introduced in v0.9.7","3":"Added the 'separator' keyword introduced in v0.9.7","package":"fluxbox.tar.gz","4":"fluxbox.tar.gz","src_id":"2696","5":"2696","creation_date":"1075420791","6":"1075420791"},{"0":"679","vim_version":"6.0","1":"6.0","script_version":"1.2","2":"1.2","version_comment":"Changed comment pattern in the syntax file so that a comment that appears after a menu entry is highlighted (suggested by Eike von Seggern)","3":"Changed comment pattern in the syntax file so that a comment that appears after a menu entry is highlighted (suggested by Eike von Seggern)","package":"fluxbox.tar.gz","4":"fluxbox.tar.gz","src_id":"2360","5":"2360","creation_date":"1064838079","6":"1064838079"},{"0":"679","vim_version":"6.0","1":"6.0","script_version":"1.1","2":"1.1","version_comment":"bugfix: changed set to setlocal in the syntax file (thanks to Henry van Roessel)","3":"bugfix: changed set to setlocal in the syntax file (thanks to Henry van Roessel)","package":"fluxbox.tar.gz","4":"fluxbox.tar.gz","src_id":"2084","5":"2084","creation_date":"1055765656","6":"1055765656"},{"0":"679","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"fluxbox.tar.gz","4":"fluxbox.tar.gz","src_id":"2081","5":"2081","creation_date":"1055680337","6":"1055680337"}]},"678":{"script_id":"678","0":"678","script_name":"genindent.vim","1":"genindent.vim","script_type":"indent","2":"indent","summary":"Generic function for indentexpr","3":"Generic function for indentexpr","description":"This is a function meant to deal with a simple case of indentation:\r\nThe assumption is that you have blocks whose begining and end can be identified by a pattern. In this case, you just set b:indent_block_start and b:indent_block_end to these patterns, and the function returns the indent of a line based on the assumption that all lines within a block should be indented by one shiftwidth. It is also possible to ignore lines matching a certain pattern (e.g., comments) using a third variable b:indent_ignore. For an example, see the fluxbox indent file (vimscript #679).","4":"This is a function meant to deal with a simple case of indentation:\r\nThe assumption is that you have blocks whose begining and end can be identified by a pattern. In this case, you just set b:indent_block_start and b:indent_block_end to these patterns, and the function returns the indent of a line based on the assumption that all lines within a block should be indented by one shiftwidth. It is also possible to ignore lines matching a certain pattern (e.g., comments) using a third variable b:indent_ignore. For an example, see the fluxbox indent file (vimscript #679).","install_details":"Put this in the plugin subdir of your favorite part in the runtimepath (e.g., ~\/.vim\/plugin). Alternatively, put it somewhere else and source it from an indent file where you'd like to use it.","5":"Put this in the plugin subdir of your favorite part in the runtimepath (e.g., ~\/.vim\/plugin). Alternatively, put it somewhere else and source it from an indent file where you'd like to use it.","first_name":"moshe","6":"moshe","last_name":"kamensky","7":"kamensky","releases":[{"0":"678","vim_version":"6.0","1":"6.0","script_version":"1.1","2":"1.1","version_comment":"Fixed = to == (thanks to Kenny Root)","3":"Fixed = to == (thanks to Kenny Root)","package":"genindent.vim","4":"genindent.vim","src_id":"10915","5":"10915","creation_date":"1246413373","6":"1246413373"},{"0":"678","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"genindent.vim","4":"genindent.vim","src_id":"2080","5":"2080","creation_date":"1055679546","6":"1055679546"}]},"677":{"script_id":"677","0":"677","script_name":"pgn.vim","1":"pgn.vim","script_type":"syntax","2":"syntax","summary":"Provides syntax highlighting for .pgn (chess) files","3":"Provides syntax highlighting for .pgn (chess) files","description":"PGN, or Portable Game Notation, is the standard format for recording chess games.  All chess software that I've used can read .pgn files, most can write .pgn files.  I like to edit the files in Vim, but I couldn't find a syntax file for .pgn.  So I wrote this one.  It's quite simple, and the first syntax file I've ever written for Vim, so it may not be complete.  But it does make it easier to read \/ edit the games.","4":"PGN, or Portable Game Notation, is the standard format for recording chess games.  All chess software that I've used can read .pgn files, most can write .pgn files.  I like to edit the files in Vim, but I couldn't find a syntax file for .pgn.  So I wrote this one.  It's quite simple, and the first syntax file I've ever written for Vim, so it may not be complete.  But it does make it easier to read \/ edit the games.","install_details":"Put the file in your $VIMRUNTIME\/syntax\/ directory.\r\nThen in your $VIMRUNTIME\/filetype.vim file, add this line:\r\n\r\nau BufNewFile,BufRead *.pgn    setf pgn","5":"Put the file in your $VIMRUNTIME\/syntax\/ directory.\r\nThen in your $VIMRUNTIME\/filetype.vim file, add this line:\r\n\r\nau BufNewFile,BufRead *.pgn    setf pgn","first_name":"Charles","6":"Charles","last_name":"Ford","7":"Ford","releases":[{"0":"677","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"pgn.vim","4":"pgn.vim","src_id":"2077","5":"2077","creation_date":"1055552866","6":"1055552866"}]},"676":{"script_id":"676","0":"676","script_name":"GenerateMatlabFunctionComment","1":"GenerateMatlabFunctionComment","script_type":"utility","2":"utility","summary":"Generates documentation structure for a matlab function.","3":"Generates documentation structure for a matlab function.","description":"Generates a comment skeleton for a matlab function. \r\n\r\nFor example:\r\nfunction xs = get_slantx(x, y, angle)\r\nWhen the script (VERSION 0.3) is run on this line the output is like:\r\nfunction xs = get_slantx(x, y, angle)\r\n% get_slantx  \r\n% \r\n% Input:\r\n% ^^^^^^\r\n% . x\r\n% . y\r\n% . angle\r\n%\r\n% Output:\r\n% ^^^^^^^\r\n% . xs\r\n%% AUTHOR  Author Name\r\n\r\nThis format is compatible with Matdoc. See version comments below to know more about Matdoc.\r\n\r\nFor previous versions the output looks similar to:\r\n% get_slantx   \r\n% function xs = get_slantx(x, y, angle)\r\n% PARAM xs [OUT] \r\n% PARAM x [IN] \r\n% PARAM y [IN] \r\n% PARAM angle [IN] \r\n% AUTHOR  Author Name\r\n\r\nThis script is derived from MakeDoxygenComment by Leif Wickland.\r\n\r\nAfter the installation you can run the script simply by hitting <ALT+c> when the cursor is on function line.\r\n\r\n","4":"Generates a comment skeleton for a matlab function. \r\n\r\nFor example:\r\nfunction xs = get_slantx(x, y, angle)\r\nWhen the script (VERSION 0.3) is run on this line the output is like:\r\nfunction xs = get_slantx(x, y, angle)\r\n% get_slantx  \r\n% \r\n% Input:\r\n% ^^^^^^\r\n% . x\r\n% . y\r\n% . angle\r\n%\r\n% Output:\r\n% ^^^^^^^\r\n% . xs\r\n%% AUTHOR  Author Name\r\n\r\nThis format is compatible with Matdoc. See version comments below to know more about Matdoc.\r\n\r\nFor previous versions the output looks similar to:\r\n% get_slantx   \r\n% function xs = get_slantx(x, y, angle)\r\n% PARAM xs [OUT] \r\n% PARAM x [IN] \r\n% PARAM y [IN] \r\n% PARAM angle [IN] \r\n% AUTHOR  Author Name\r\n\r\nThis script is derived from MakeDoxygenComment by Leif Wickland.\r\n\r\nAfter the installation you can run the script simply by hitting <ALT+c> when the cursor is on function line.\r\n\r\n","install_details":"Copy the script in vim61\/macros\/ and add these lines to your _vimrc.\r\n\r\nsource $VIMRUNTIME\/macros\/MakeMatlabComment.vim\r\n \r\nmap <M-c> :call MakeMatlabComment()<CR>\r\nimap <M-c> <ESC>:call MakeMatlabComment()<CR>","5":"Copy the script in vim61\/macros\/ and add these lines to your _vimrc.\r\n\r\nsource $VIMRUNTIME\/macros\/MakeMatlabComment.vim\r\n \r\nmap <M-c> :call MakeMatlabComment()<CR>\r\nimap <M-c> <ESC>:call MakeMatlabComment()<CR>","first_name":"Vinay","6":"Vinay","last_name":"Middha","7":"Middha","releases":[{"0":"676","vim_version":"6.0","1":"6.0","script_version":"0.4","2":"0.4","version_comment":"Cleaner implementation with comments.","3":"Cleaner implementation with comments.","package":"MakeMatlabComment.vim","4":"MakeMatlabComment.vim","src_id":"2120","5":"2120","creation_date":"1056947418","6":"1056947418"},{"0":"676","vim_version":"6.0","1":"6.0","script_version":"0.3","2":"0.3","version_comment":"The comment syntax is now compatible with Matdoc. Matdoc is a program that extracts the documentation of matlab functions, and converts it to vim help files, html, latex, etc., much as doxygen does for C\/C++. Matdoc is written by Moshe Kaminsky and is available on matlabs fileexchange site.","3":"The comment syntax is now compatible with Matdoc. Matdoc is a program that extracts the documentation of matlab functions, and converts it to vim help files, html, latex, etc., much as doxygen does for C\/C++. Matdoc is written by Moshe Kaminsky and is available on matlabs fileexchange site.","package":"MakeMatlabComment.vim","4":"MakeMatlabComment.vim","src_id":"2083","5":"2083","creation_date":"1055729998","6":"1055729998"},{"0":"676","vim_version":"6.0","1":"6.0","script_version":"0.2","2":"0.2","version_comment":"Fixed error that occurs when used on matlab function without any output argument.","3":"Fixed error that occurs when used on matlab function without any output argument.","package":"MakeMatlabComment.vim","4":"MakeMatlabComment.vim","src_id":"2079","5":"2079","creation_date":"1055558055","6":"1055558055"},{"0":"676","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"MakeMatlabComment.vim","4":"MakeMatlabComment.vim","src_id":"2074","5":"2074","creation_date":"1055479319","6":"1055479319"}]},"675":{"script_id":"675","0":"675","script_name":"VS like Class Completion","1":"VS like Class Completion","script_type":"utility","2":"utility","summary":"This script can complete member of cpp or java like Visual Studio.","3":"This script can complete member of cpp or java like Visual Studio.","description":"class Test\r\n{\r\npublic:\r\n  int getValue() { return 0 };\r\n};\r\nint main( void )\r\n{\r\n  Test *test;\r\n  test->_\r\n}\r\n--------------\r\ntype <c-space> over the cursor for completing members.\r\nand, next member will be completed with typing <c-n> or <c-p>.\r\n","4":"class Test\r\n{\r\npublic:\r\n  int getValue() { return 0 };\r\n};\r\nint main( void )\r\n{\r\n  Test *test;\r\n  test->_\r\n}\r\n--------------\r\ntype <c-space> over the cursor for completing members.\r\nand, next member will be completed with typing <c-n> or <c-p>.\r\n","install_details":"cp classcmpl.vim $VIMRUNTIME\/plugin\/.","5":"cp classcmpl.vim $VIMRUNTIME\/plugin\/.","first_name":"Yasuhiro","6":"Yasuhiro","last_name":"Matsumoto","7":"Matsumoto","releases":[{"0":"675","vim_version":"6.0","1":"6.0","script_version":"0.9","2":"0.9","version_comment":"Initial upload","3":"Initial upload","package":"classcmpl.vim","4":"classcmpl.vim","src_id":"2073","5":"2073","creation_date":"1055452991","6":"1055452991"}]},"674":{"script_id":"674","0":"674","script_name":"MakeDoxygenComment","1":"MakeDoxygenComment","script_type":"ftplugin","2":"ftplugin","summary":"Generate Doxygen Comment Skeleton","3":"Generate Doxygen Comment Skeleton","description":"I haven't maintained this in a long time.  I'd suggest trying out Ryan De Boer's updated version: vimscript #4530.\r\n\r\nGenerates a doxygen comment skeleton for a C, C++,  or Java function, including @brief, @param (for each named argument), and @return.  The tag text as well as a comment block header and footer are configurable.  (Consequently, you can have \\brief, etc. if you wish, with little effort.)\r\n\r\nIt's definitely a little rough around the edges, but I hope you find it useful.\r\n\r\nTo use:  In vim with the cursor on the line of the function header that contains the parameters (if any), execute the command :Dox.  This will generate the skeleton and leave the cursor after the @brief tag.\r\n\r\nLimitations:\r\nAssumes that the function has a blank line above it and that all of the parameters are on the same line.  \r\nNot able to update a comment block after it's been written.\r\nWrites the @return tag for a void function.\r\n\r\nExample:\r\nGiven:\r\nint foo(char mychar, int yourint, double myarray[])\r\n{ \/\/...\r\n}\r\n\r\nIssuing the :Dox command with the cursor on the function declaration would generate\r\n\r\n\/**\r\n * @brief\r\n * \r\n * @param mychar\r\n * @param myint\r\n * @param myarray\r\n *\r\n * @returns\r\n **\/","4":"I haven't maintained this in a long time.  I'd suggest trying out Ryan De Boer's updated version: vimscript #4530.\r\n\r\nGenerates a doxygen comment skeleton for a C, C++,  or Java function, including @brief, @param (for each named argument), and @return.  The tag text as well as a comment block header and footer are configurable.  (Consequently, you can have \\brief, etc. if you wish, with little effort.)\r\n\r\nIt's definitely a little rough around the edges, but I hope you find it useful.\r\n\r\nTo use:  In vim with the cursor on the line of the function header that contains the parameters (if any), execute the command :Dox.  This will generate the skeleton and leave the cursor after the @brief tag.\r\n\r\nLimitations:\r\nAssumes that the function has a blank line above it and that all of the parameters are on the same line.  \r\nNot able to update a comment block after it's been written.\r\nWrites the @return tag for a void function.\r\n\r\nExample:\r\nGiven:\r\nint foo(char mychar, int yourint, double myarray[])\r\n{ \/\/...\r\n}\r\n\r\nIssuing the :Dox command with the cursor on the function declaration would generate\r\n\r\n\/**\r\n * @brief\r\n * \r\n * @param mychar\r\n * @param myint\r\n * @param myarray\r\n *\r\n * @returns\r\n **\/","install_details":"Stick MakeDoxygenComment.vim in either your plugins or ftplugins\/* directory. ","5":"Stick MakeDoxygenComment.vim in either your plugins or ftplugins\/* directory. ","first_name":"Leif","6":"Leif","last_name":"Wickland","7":"Wickland","releases":[{"0":"674","vim_version":"6.0","1":"6.0","script_version":"0.1.3","2":"0.1.3","version_comment":"Now correctly recognizes parameters which end in '[]'.","3":"Now correctly recognizes parameters which end in '[]'.","package":"MakeDoxygenComment.vim","4":"MakeDoxygenComment.vim","src_id":"2794","5":"2794","creation_date":"1078126312","6":"1078126312"},{"0":"674","vim_version":"6.0","1":"6.0","script_version":"0.1.2","2":"0.1.2","version_comment":"Fixed a problem with whitespace between the identifier and the ',' or ')'.  (Thanks to Mirko Koenig.)","3":"Fixed a problem with whitespace between the identifier and the ',' or ')'.  (Thanks to Mirko Koenig.)","package":"MakeDoxygenComment.vim","4":"MakeDoxygenComment.vim","src_id":"2773","5":"2773","creation_date":"1077551867","6":"1077551867"},{"0":"674","vim_version":"6.0","1":"6.0","script_version":"0.1.1","2":"0.1.1","version_comment":"Minor bug fix","3":"Minor bug fix","package":"MakeDoxygenComment.vim","4":"MakeDoxygenComment.vim","src_id":"2070","5":"2070","creation_date":"1055415330","6":"1055415330"},{"0":"674","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"MakeDoxygenComment.vim","4":"MakeDoxygenComment.vim","src_id":"2069","5":"2069","creation_date":"1055414285","6":"1055414285"}]},"673":{"script_id":"673","0":"673","script_name":"Maxlen.vim","1":"Maxlen.vim","script_type":"utility","2":"utility","summary":"Find the long lines and mark them.","3":"Find the long lines and mark them.","description":"When you want to know the longest line in the buffered text file, Please try this script.\r\nIt makes the cursor jumped on the longest line and also marks the top five long lines with the message like \"Marked a=lin.54(col.78), b=36(77), c=56(77), d=20(76), e=55(76)\".\r\nThis is my first vim scripting and I've enjoyed it a lot.\r\n","4":"When you want to know the longest line in the buffered text file, Please try this script.\r\nIt makes the cursor jumped on the longest line and also marks the top five long lines with the message like \"Marked a=lin.54(col.78), b=36(77), c=56(77), d=20(76), e=55(76)\".\r\nThis is my first vim scripting and I've enjoyed it a lot.\r\n","install_details":"Sorce it when you want.","5":"Sorce it when you want.","first_name":"Yasuoki","6":"Yasuoki","last_name":"Mutoh","7":"Mutoh","releases":[{"0":"673","vim_version":"6.0","1":"6.0","script_version":"0.0","2":"0.0","version_comment":"Initial upload","3":"Initial upload","package":"Maxlen.vim","4":"Maxlen.vim","src_id":"2068","5":"2068","creation_date":"1055413542","6":"1055413542"}]},"672":{"script_id":"672","0":"672","script_name":"deleted","1":"deleted","script_type":"utility","2":"utility","summary":"deleted","3":"deleted","description":"deleted","4":"deleted","install_details":"","5":"","first_name":"Antony","6":"Antony","last_name":"Scriven","7":"Scriven","releases":[{"0":"672","vim_version":"7.0","1":"7.0","script_version":"1.4","2":"1.4","version_comment":"empty","3":"empty","package":"listmaps.vim","4":"listmaps.vim","src_id":"24568","5":"24568","creation_date":"1475092733","6":"1475092733"}]},"671":{"script_id":"671","0":"671","script_name":"deleted","1":"deleted","script_type":"color scheme","2":"color scheme","summary":"deleted","3":"deleted","description":"deleted","4":"deleted","install_details":"","5":"","first_name":"Antony","6":"Antony","last_name":"Scriven","7":"Scriven","releases":[{"0":"671","vim_version":"7.0","1":"7.0","script_version":"1.1","2":"1.1","version_comment":"empty","3":"empty","package":"autumn.vim","4":"autumn.vim","src_id":"24569","5":"24569","creation_date":"1475092768","6":"1475092768"}]},"670":{"script_id":"670","0":"670","script_name":"VisIncr","1":"VisIncr","script_type":"utility","2":"utility","summary":"Produce increasing\/decreasing columns of numbers, dates, or daynames","3":"Produce increasing\/decreasing columns of numbers, dates, or daynames","description":"The visincr plugin facilitates making a column of increasing or decreasing\r\nnumbers, dates, or daynames.\r\n\r\nFirst, select a column using visual-block (ctrl-v) and move the cursor.\r\n\r\nSecond, choose what sort of incremented list you want:\r\n\r\n    :I [#]  Will use the first line's number as a starting point to build\r\n            a column of increasing numbers (or decreasing numbers if the\r\n        increment is negative).\r\n        Default increment: 1\r\n        Justification    : left (will pad on the right)\r\n\r\n    :II [# [zfill]]  Will use the first line's number as a starting point\r\n        to build a column of increasing numbers (or decreasing numbers\r\n        if the increment is negative).\r\n        Default increment: 1\r\n        Justification    : right (will pad on the left)\r\n        Zfill            : left padding will be done with the given\r\n                           character, typically a zero.\r\n\r\n    :IYMD [#]    year\/month\/day\r\n    :IMDY [#]    month\/day\/year\r\n    :IDMY [#]    day\/month\/year\r\n        Will use the starting line's date to construct an increasing\r\n        or decreasing list of dates, depending on the sign of the\r\n        number.\r\n        Default increment: 1 (in days)\r\n\r\n    :ID [#] Will produce an increasing\/decreasing list of daynames.  Three-letter\r\n            daynames will be used if the first day on the first line is a three\r\n        letter dayname; otherwise, full names will be used.\r\n\r\n    :IO [#]\r\n    :IIO [#] [zfill]\r\n        Like :I and :II, except visincr creates octal numbers.\r\n\r\n    :IR [#]\r\n    :IIR [#] [zfill]\r\n        Like :I and :II, except visincr uses Roman numerals.  Negative and\r\n        zero counts are not supported for Roman numerals.\r\n\r\n    :IX [#]\r\n    :IIX [#] [zfill]\r\n        Like :I and :II, except visincr creates hexadecimal numbers.\r\n\r\n    -------------------\r\n    EXTRA NOTES\r\n    -------------------\r\n    For :I :II :IO :IIO :IR :IIR :\r\n        If the visual block is ragged on the right-hand side (as can\r\n        easily happen when the \"$\" is used to select the\r\n        right-hand-side), the block will have spaces appended to\r\n        straighten it out.  If the string length of the count exceeds\r\n        the visual-block, then additional spaces will be inserted as\r\n        needed.  Leading tabs are handled by using virtual column\r\n        calculations.\r\n\r\n    For :IR and :IIR :\r\n        Since Roman numerals vary considerably in their lengths for\r\n        nearby numbers, an additional two spaces will be included.\r\n\r\n    For :IYMD, :IMDY, and IDMY:\r\n        You'll need the <calutil.vim> plugin, available as\r\n        \"Calendar Utilities\" under the following url:\r\n\r\n        http:\/\/mysite.verizon.net\/astronaut\/vim\/index.html#CALUTIL\r\n\r\nHelp is included, too -- check out  :he visincr-examples to see\r\neven more examples of each command in action.\r\n\r\nExamples:\r\n\r\n        :I\r\n                    Use ctrl-V to\r\n        Original    Select, :I\r\n           8            8\r\n           8            9\r\n           8            10\r\n           8            11\r\n           8            12\r\n\r\n        :I -1\r\n                    Use ctrl-V to\r\n        Original    Select, :I -1\r\n           8            8\r\n           8            7\r\n           8            6\r\n           8            5\r\n           8            4\r\n\r\n\r\n        :II\r\n                    Use ctrl-V to\r\n        Original    Select, :II\r\n           8             8\r\n           8             9\r\n           8            10\r\n           8            11\r\n           8            12\r\n\r\n        :II -1\r\n                    Use ctrl-V to\r\n        Original    Select, :II -1\r\n           8            8\r\n           8            7\r\n           8            6\r\n           8            5\r\n           8            4\r\n\r\n\r\n        :IMDY\r\n                  Use ctrl-V to\r\n        Original  Select, :IMDY\r\n        06\/10\/03     6\/10\/03\r\n        06\/10\/03     6\/11\/03\r\n        06\/10\/03     6\/12\/03\r\n        06\/10\/03     6\/13\/03\r\n        06\/10\/03     6\/14\/03\r\n\r\n\r\n        :IYMD\r\n                  Use ctrl-V to\r\n        Original  Select, :IYMD\r\n        03\/06\/10    03\/06\/10\r\n        03\/06\/10    03\/06\/11\r\n        03\/06\/10    03\/06\/12\r\n        03\/06\/10    03\/06\/13\r\n        03\/06\/10    03\/06\/14\r\n\r\n\r\n\r\n\r\n        :IDMY\r\n                  Use ctrl-V to\r\n        Original  Select, :IDMY\r\n        10\/06\/03    10\/06\/03\r\n        10\/06\/03    11\/06\/03\r\n        10\/06\/03    12\/06\/03\r\n        10\/06\/03    13\/06\/03\r\n        10\/06\/03    14\/06\/03\r\n\r\n\r\n        :ID\r\n                  Use ctrl-V to\r\n        Original  Select, :ID\r\n          Sun       Sun\r\n          Sun       Mon\r\n          Sun       Tue\r\n          Sun       Wed\r\n          Sun       Thu\r\n\r\n\r\n        :ID\r\n                  Use ctrl-V to\r\n        Original  Select, :ID\r\n         Sunday     Sunday\r\n         Sunday     Monday\r\n         Sunday     Tuesday\r\n         Sunday     Wednesday\r\n         Sunday     Thursday\r\n\r\n        :IA\r\n                  Use ctrl-V to\r\n        Original  Select, :IA\r\n           a          a\r\n           a          b\r\n           a          c\r\n           a          d\r\n           a          e\r\n\r\n        :IO\r\n                  Use ctrl-V to\r\n        Original  Select, :IO\r\n            5         5 \r\n            5         6 \r\n            5         7 \r\n            5         10\r\n            5         11\r\n\r\n        :IR\r\n                  Use ctrl-V to\r\n        Original  Select, :IR\r\n           II         II\r\n           II         III\r\n           II         IV\r\n           II         V \r\n           II         VI\r\n\r\n                  Use ctrl-V to\r\n        Original  Select, :IX\r\n            8         8\r\n            8         9\r\n            8         a\r\n            8         b\r\n            8         c\r\n\r\n\r\n-------------\r\nSEE ALSO\r\n-------------\r\nvis     : vimscript#1195 : apply any ex command (ex. :s\/..\/..\/) to a visual block\r\nvissort : vimtip#588     : how to sort a visual block (or sort based on one)\r\nvisincr : http:\/\/www.drchip.org\/astronaut\/vim\/index.html#VISINCR (for the latest, albeit experimental, release)","4":"The visincr plugin facilitates making a column of increasing or decreasing\r\nnumbers, dates, or daynames.\r\n\r\nFirst, select a column using visual-block (ctrl-v) and move the cursor.\r\n\r\nSecond, choose what sort of incremented list you want:\r\n\r\n    :I [#]  Will use the first line's number as a starting point to build\r\n            a column of increasing numbers (or decreasing numbers if the\r\n        increment is negative).\r\n        Default increment: 1\r\n        Justification    : left (will pad on the right)\r\n\r\n    :II [# [zfill]]  Will use the first line's number as a starting point\r\n        to build a column of increasing numbers (or decreasing numbers\r\n        if the increment is negative).\r\n        Default increment: 1\r\n        Justification    : right (will pad on the left)\r\n        Zfill            : left padding will be done with the given\r\n                           character, typically a zero.\r\n\r\n    :IYMD [#]    year\/month\/day\r\n    :IMDY [#]    month\/day\/year\r\n    :IDMY [#]    day\/month\/year\r\n        Will use the starting line's date to construct an increasing\r\n        or decreasing list of dates, depending on the sign of the\r\n        number.\r\n        Default increment: 1 (in days)\r\n\r\n    :ID [#] Will produce an increasing\/decreasing list of daynames.  Three-letter\r\n            daynames will be used if the first day on the first line is a three\r\n        letter dayname; otherwise, full names will be used.\r\n\r\n    :IO [#]\r\n    :IIO [#] [zfill]\r\n        Like :I and :II, except visincr creates octal numbers.\r\n\r\n    :IR [#]\r\n    :IIR [#] [zfill]\r\n        Like :I and :II, except visincr uses Roman numerals.  Negative and\r\n        zero counts are not supported for Roman numerals.\r\n\r\n    :IX [#]\r\n    :IIX [#] [zfill]\r\n        Like :I and :II, except visincr creates hexadecimal numbers.\r\n\r\n    -------------------\r\n    EXTRA NOTES\r\n    -------------------\r\n    For :I :II :IO :IIO :IR :IIR :\r\n        If the visual block is ragged on the right-hand side (as can\r\n        easily happen when the \"$\" is used to select the\r\n        right-hand-side), the block will have spaces appended to\r\n        straighten it out.  If the string length of the count exceeds\r\n        the visual-block, then additional spaces will be inserted as\r\n        needed.  Leading tabs are handled by using virtual column\r\n        calculations.\r\n\r\n    For :IR and :IIR :\r\n        Since Roman numerals vary considerably in their lengths for\r\n        nearby numbers, an additional two spaces will be included.\r\n\r\n    For :IYMD, :IMDY, and IDMY:\r\n        You'll need the <calutil.vim> plugin, available as\r\n        \"Calendar Utilities\" under the following url:\r\n\r\n        http:\/\/mysite.verizon.net\/astronaut\/vim\/index.html#CALUTIL\r\n\r\nHelp is included, too -- check out  :he visincr-examples to see\r\neven more examples of each command in action.\r\n\r\nExamples:\r\n\r\n        :I\r\n                    Use ctrl-V to\r\n        Original    Select, :I\r\n           8            8\r\n           8            9\r\n           8            10\r\n           8            11\r\n           8            12\r\n\r\n        :I -1\r\n                    Use ctrl-V to\r\n        Original    Select, :I -1\r\n           8            8\r\n           8            7\r\n           8            6\r\n           8            5\r\n           8            4\r\n\r\n\r\n        :II\r\n                    Use ctrl-V to\r\n        Original    Select, :II\r\n           8             8\r\n           8             9\r\n           8            10\r\n           8            11\r\n           8            12\r\n\r\n        :II -1\r\n                    Use ctrl-V to\r\n        Original    Select, :II -1\r\n           8            8\r\n           8            7\r\n           8            6\r\n           8            5\r\n           8            4\r\n\r\n\r\n        :IMDY\r\n                  Use ctrl-V to\r\n        Original  Select, :IMDY\r\n        06\/10\/03     6\/10\/03\r\n        06\/10\/03     6\/11\/03\r\n        06\/10\/03     6\/12\/03\r\n        06\/10\/03     6\/13\/03\r\n        06\/10\/03     6\/14\/03\r\n\r\n\r\n        :IYMD\r\n                  Use ctrl-V to\r\n        Original  Select, :IYMD\r\n        03\/06\/10    03\/06\/10\r\n        03\/06\/10    03\/06\/11\r\n        03\/06\/10    03\/06\/12\r\n        03\/06\/10    03\/06\/13\r\n        03\/06\/10    03\/06\/14\r\n\r\n\r\n\r\n\r\n        :IDMY\r\n                  Use ctrl-V to\r\n        Original  Select, :IDMY\r\n        10\/06\/03    10\/06\/03\r\n        10\/06\/03    11\/06\/03\r\n        10\/06\/03    12\/06\/03\r\n        10\/06\/03    13\/06\/03\r\n        10\/06\/03    14\/06\/03\r\n\r\n\r\n        :ID\r\n                  Use ctrl-V to\r\n        Original  Select, :ID\r\n          Sun       Sun\r\n          Sun       Mon\r\n          Sun       Tue\r\n          Sun       Wed\r\n          Sun       Thu\r\n\r\n\r\n        :ID\r\n                  Use ctrl-V to\r\n        Original  Select, :ID\r\n         Sunday     Sunday\r\n         Sunday     Monday\r\n         Sunday     Tuesday\r\n         Sunday     Wednesday\r\n         Sunday     Thursday\r\n\r\n        :IA\r\n                  Use ctrl-V to\r\n        Original  Select, :IA\r\n           a          a\r\n           a          b\r\n           a          c\r\n           a          d\r\n           a          e\r\n\r\n        :IO\r\n                  Use ctrl-V to\r\n        Original  Select, :IO\r\n            5         5 \r\n            5         6 \r\n            5         7 \r\n            5         10\r\n            5         11\r\n\r\n        :IR\r\n                  Use ctrl-V to\r\n        Original  Select, :IR\r\n           II         II\r\n           II         III\r\n           II         IV\r\n           II         V \r\n           II         VI\r\n\r\n                  Use ctrl-V to\r\n        Original  Select, :IX\r\n            8         8\r\n            8         9\r\n            8         a\r\n            8         b\r\n            8         c\r\n\r\n\r\n-------------\r\nSEE ALSO\r\n-------------\r\nvis     : vimscript#1195 : apply any ex command (ex. :s\/..\/..\/) to a visual block\r\nvissort : vimtip#588     : how to sort a visual block (or sort based on one)\r\nvisincr : http:\/\/www.drchip.org\/astronaut\/vim\/index.html#VISINCR (for the latest, albeit experimental, release)","install_details":"1. You need vimball v18 or later (vimscript#1502).  Please remove any vestiges of an older vimball first.\r\n    (if you have vim 7.1 or later, you can skip this step)\r\n2. vim visincr.vba.gz\r\n    :so %\r\n    :q","5":"1. You need vimball v18 or later (vimscript#1502).  Please remove any vestiges of an older vimball first.\r\n    (if you have vim 7.1 or later, you can skip this step)\r\n2. vim visincr.vba.gz\r\n    :so %\r\n    :q","first_name":"Charles","6":"Charles","last_name":"Campbell","7":"Campbell","releases":[{"0":"670","vim_version":"7.3","1":"7.3","script_version":"20","2":"20","version_comment":"new     : IB and IIB support binary dec\/incrementing; restricted incrementing support for :RIB, :RIIB, :RIO, :RIX, and :RIIX (ie. for binary, octal, and hexadecimal dec\/incrementing); and optional long-command names.\r\n\r\nbugfixes: two-argument IIO, IIX commands; when selection with exclusive is used.\r\n","3":"new     : IB and IIB support binary dec\/incrementing; restricted incrementing support for :RIB, :RIIB, :RIO, :RIX, and :RIIX (ie. for binary, octal, and hexadecimal dec\/incrementing); and optional long-command names.\r\n\r\nbugfixes: two-argument IIO, IIX commands; when selection with exclusive is used.\r\n","package":"visincr.vba.gz","4":"visincr.vba.gz","src_id":"16281","5":"16281","creation_date":"1313521031","6":"1313521031"},{"0":"670","vim_version":"7.0","1":"7.0","script_version":"19","2":"19","version_comment":"Forgot to include calutil with visincr (its there now!)","3":"Forgot to include calutil with visincr (its there now!)","package":"visincr.vba.gz","4":"visincr.vba.gz","src_id":"8073","5":"8073","creation_date":"1198052288","6":"1198052288"},{"0":"670","vim_version":"7.0","1":"7.0","script_version":"18","2":"18","version_comment":"* Power based incrementing: IPOW (2,4,8,16,...)\r\n* Date dividers are no longer required\r\n* Calutil is included, and they use vim 7's autoload feature (load only on demand)\r\n","3":"* Power based incrementing: IPOW (2,4,8,16,...)\r\n* Date dividers are no longer required\r\n* Calutil is included, and they use vim 7's autoload feature (load only on demand)\r\n","package":"visincr.vba.gz","4":"visincr.vba.gz","src_id":"8071","5":"8071","creation_date":"1198043618","6":"1198043618"},{"0":"670","vim_version":"7.0","1":"7.0","script_version":"17","2":"17","version_comment":"(NEW) Visincr's commands now support expression-style completion.\r\n(NEW) g:visincr_datedivset support included: date dividers are (default) assumed to from the set [-.\/]; the separator actually used is the first one found in your date column.\r\n","3":"(NEW) Visincr's commands now support expression-style completion.\r\n(NEW) g:visincr_datedivset support included: date dividers are (default) assumed to from the set [-.\/]; the separator actually used is the first one found in your date column.\r\n","package":"visincr.vba.gz","4":"visincr.vba.gz","src_id":"6208","5":"6208","creation_date":"1158669351","6":"1158669351"},{"0":"670","vim_version":"6.0","1":"6.0","script_version":"16","2":"16","version_comment":"Roman numerals (:IR and :IIR) supported!\r\n:IX, :IIX, :IO, and :IIO now support negative increments and negative counts.\r\n","3":"Roman numerals (:IR and :IIR) supported!\r\n:IX, :IIX, :IO, and :IIO now support negative increments and negative counts.\r\n","package":"visincr.vba.gz","4":"visincr.vba.gz","src_id":"5989","5":"5989","creation_date":"1153819500","6":"1153819500"},{"0":"670","vim_version":"7.0","1":"7.0","script_version":"14","2":"14","version_comment":"Visincr now supports :IX, :IIX, :IO, and :IIO for creating hexadecimal and octal incremented lists, supports autoloading for faster vim startup, and informs users about :help visincr-calutil when necessary.\r\n\r\nAutoloading by itself necessitates requiring Vim version 7.0.","3":"Visincr now supports :IX, :IIX, :IO, and :IIO for creating hexadecimal and octal incremented lists, supports autoloading for faster vim startup, and informs users about :help visincr-calutil when necessary.\r\n\r\nAutoloading by itself necessitates requiring Vim version 7.0.","package":"visincr.vba.gz","4":"visincr.vba.gz","src_id":"5825","5":"5825","creation_date":"1150104804","6":"1150104804"},{"0":"670","vim_version":"6.0","1":"6.0","script_version":"13","2":"13","version_comment":"A \"zfill\" of \"\" or '' now stands for an empty zfill.\r\nBugfix: visincr now insures that the first character of a month or day incrementing sequence is capitalized.\r\nBugfix: names embedded within lines weren't being incremented correctly; fixed!\r\n","3":"A \"zfill\" of \"\" or '' now stands for an empty zfill.\r\nBugfix: visincr now insures that the first character of a month or day incrementing sequence is capitalized.\r\nBugfix: names embedded within lines weren't being incremented correctly; fixed!\r\n","package":"visincr.vim.gz","4":"visincr.vim.gz","src_id":"5467","5":"5467","creation_date":"1142845158","6":"1142845158"},{"0":"670","vim_version":"6.0","1":"6.0","script_version":"12","2":"12","version_comment":"Zfill capability provided ( 01 02 03 ... style incrementing).  Users may now set g:visincr_dow and g:visincr_month to customize daynames and monthnames (for date incrementing).  Handles more vim option settings.\r\n","3":"Zfill capability provided ( 01 02 03 ... style incrementing).  Users may now set g:visincr_dow and g:visincr_month to customize daynames and monthnames (for date incrementing).  Handles more vim option settings.\r\n","package":"visincr.vim.gz","4":"visincr.vim.gz","src_id":"5384","5":"5384","creation_date":"1141721414","6":"1141721414"},{"0":"670","vim_version":"6.0","1":"6.0","script_version":"11","2":"11","version_comment":"g:visincr_leaddate now allows one to specify a leading character to expand single-digit days and months into two-characters\r\nThe :IM and :ID commands (increment month, increment day) now handle varying length long names\r\n","3":"g:visincr_leaddate now allows one to specify a leading character to expand single-digit days and months into two-characters\r\nThe :IM and :ID commands (increment month, increment day) now handle varying length long names\r\n","package":"visincr.vim.bz2","4":"visincr.vim.bz2","src_id":"3377","5":"3377","creation_date":"1093335388","6":"1093335388"},{"0":"670","vim_version":"6.0","1":"6.0","script_version":"9","2":"9","version_comment":"Visincr now supports incrementing\/decrementing\r\nalphabetic lists:  ie. transform a column of\r\n(a) or a) into (a) (b) (c) (or a) b) c) ). \r\n\r\nVisincr can now increment or decrement integers,\r\ndaynames, monthnames, dates, and alphabetic lists!\r\n\r\n(Help is automatically installed and made available using\r\nthe HelpExtractor)\r\n","3":"Visincr now supports incrementing\/decrementing\r\nalphabetic lists:  ie. transform a column of\r\n(a) or a) into (a) (b) (c) (or a) b) c) ). \r\n\r\nVisincr can now increment or decrement integers,\r\ndaynames, monthnames, dates, and alphabetic lists!\r\n\r\n(Help is automatically installed and made available using\r\nthe HelpExtractor)\r\n","package":"visincr.vim.bz2","4":"visincr.vim.bz2","src_id":"3024","5":"3024","creation_date":"1084519812","6":"1084519812"},{"0":"670","vim_version":"6.0","1":"6.0","script_version":"8","2":"8","version_comment":"Now has month incrementing (:IM) and restriction-pattern commands\r\n(:RI, :RID, :RYMD, etc) which restrict application of renumbering\r\nonly to those lines which have numbers\/daynames\/dates\/monthnames,\r\nas appropriate for the command.\r\n","3":"Now has month incrementing (:IM) and restriction-pattern commands\r\n(:RI, :RID, :RYMD, etc) which restrict application of renumbering\r\nonly to those lines which have numbers\/daynames\/dates\/monthnames,\r\nas appropriate for the command.\r\n","package":"visincr.vim","4":"visincr.vim","src_id":"2419","5":"2419","creation_date":"1066736705","6":"1066736705"}]},"669":{"script_id":"669","0":"669","script_name":"matrix.vim","1":"matrix.vim","script_type":"color scheme","2":"color scheme","summary":"MATRIX like colorscheme","3":"MATRIX like colorscheme","description":"I have no comment, just you know.","4":"I have no comment, just you know.","install_details":"Put it in one of your colors directories.\r\n  ex. $HOME\/.vim\/colors\/ \r\n  ex. $HOME\\vimfiles\\colors\\ \r\n  ex. $VIM\\vimfiles\\colors\\\r\nThen, just do :colorscheme matrix","5":"Put it in one of your colors directories.\r\n  ex. $HOME\/.vim\/colors\/ \r\n  ex. $HOME\\vimfiles\\colors\\ \r\n  ex. $VIM\\vimfiles\\colors\\\r\nThen, just do :colorscheme matrix","first_name":"Taro","6":"Taro","last_name":"MURAOKA","7":"MURAOKA","releases":[{"0":"669","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"matrix.vim","4":"matrix.vim","src_id":"2053","5":"2053","creation_date":"1055185753","6":"1055185753"}]},"668":{"script_id":"668","0":"668","script_name":"random.vim","1":"random.vim","script_type":"color scheme","2":"color scheme","summary":"A \"color scheme\" to pseudo-randomly load a color scheme.","3":"A \"color scheme\" to pseudo-randomly load a color scheme.","description":"This \"color scheme\" will pseudo-randomly  load a color scheme among all available color schemes. The main logic is based on vimtip #358.\r\n","4":"This \"color scheme\" will pseudo-randomly  load a color scheme among all available color schemes. The main logic is based on vimtip #358.\r\n","install_details":"Place it in the directory where you store the rest of your color schemes and use it as you would with any other color scheme.","5":"Place it in the directory where you store the rest of your color schemes and use it as you would with any other color scheme.","first_name":"Wei Huang","6":"Wei Huang","last_name":"Jou","7":"Jou","releases":[{"0":"668","vim_version":"6.0","1":"6.0","script_version":"1.3","2":"1.3","version_comment":"Updated to use \"Unix line endings, NL only\". Thanks Krzysztof Wrzalik < k w r z a l i k @ o 2 . p l >!","3":"Updated to use \"Unix line endings, NL only\". Thanks Krzysztof Wrzalik < k w r z a l i k @ o 2 . p l >!","package":"random.vim","4":"random.vim","src_id":"2335","5":"2335","creation_date":"1063571930","6":"1063571930"},{"0":"668","vim_version":"6.0","1":"6.0","script_version":"1.2","2":"1.2","version_comment":"Fixed the problem that was supposed to be addressed in v1.1. Now it should eliminate recursive calls on platforms that uses '\\' as path separators (e.g. M$ Windows and DOS) as well.","3":"Fixed the problem that was supposed to be addressed in v1.1. Now it should eliminate recursive calls on platforms that uses '\\' as path separators (e.g. M$ Windows and DOS) as well.","package":"random.vim","4":"random.vim","src_id":"2225","5":"2225","creation_date":"1060654980","6":"1060654980"},{"0":"668","vim_version":"6.0","1":"6.0","script_version":"1.1","2":"1.1","version_comment":"Fix to avoid itself from being selected resulting in recursive calls.","3":"Fix to avoid itself from being selected resulting in recursive calls.","package":"random.vim","4":"random.vim","src_id":"2107","5":"2107","creation_date":"1056405603","6":"1056405603"},{"0":"668","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"random.vim","4":"random.vim","src_id":"2052","5":"2052","creation_date":"1055155432","6":"1055155432"}]},"667":{"script_id":"667","0":"667","script_name":"Dotnet Dictionaries","1":"Dotnet Dictionaries","script_type":"utility","2":"utility","summary":"Whole .NET Framework for auto-completion and use in scripts  (C#  Vb .Net)","3":"Whole .NET Framework for auto-completion and use in scripts  (C#  Vb .Net)","description":"In the dictionary-files you find the whole .NET-Framework 4.0 for auto-completion or use in scripts. There are all namespaces, all classes and all functions - at least I hope so.\r\n\r\nThe entries are organized according to the main dlls. \r\nE.g. mscorlib.dll becomes mscorlib.dict.\r\n\r\nI hope someone invents a good possibilty to use theses entries. \r\n\r\nRegards,\r\n\r\n--Klaus Horsten","4":"In the dictionary-files you find the whole .NET-Framework 4.0 for auto-completion or use in scripts. There are all namespaces, all classes and all functions - at least I hope so.\r\n\r\nThe entries are organized according to the main dlls. \r\nE.g. mscorlib.dll becomes mscorlib.dict.\r\n\r\nI hope someone invents a good possibilty to use theses entries. \r\n\r\nRegards,\r\n\r\n--Klaus Horsten","install_details":"I use it for auto-completion.\r\n\r\nI have the line \r\n\r\nset dict+=$VIM\/vimfiles\/DotNet\/Dictionaries\/Framework\/PresentationCore.dict,$VIM\/vimfiles\/DotNet\/Dictionaries\/Framework\/PresentationFramework.dict,$VIM\/vimfiles\/DotNet\/Dictionaries\/Framework\/System.Configuration.dict,$VIM\/vimfiles\/DotNet\/Dictionaries\/Framework\/System.Core.dict,$VIM\/vimfiles\/DotNet\/Dictionaries\/Framework\/System.Data.SqlXml.dict,$VIM\/vimfiles\/DotNet\/Dictionaries\/Framework\/System.Data.dict,$VIM\/vimfiles\/DotNet\/Dictionaries\/Framework\/System.Drawing.dict,$VIM\/vimfiles\/DotNet\/Dictionaries\/Framework\/System.Numerics.dict,$VIM\/vimfiles\/DotNet\/Dictionaries\/Framework\/System.Security.dict,$VIM\/vimfiles\/DotNet\/Dictionaries\/Framework\/System.ServiceModel.dict,$VIM\/vimfiles\/DotNet\/Dictionaries\/Framework\/System.Web.dict,$VIM\/vimfiles\/DotNet\/Dictionaries\/Framework\/System.Windows.Forms.dict,$VIM\/vimfiles\/DotNet\/Dictionaries\/Framework\/System.Workflow.Activities.dict,$VIM\/vimfiles\/DotNet\/Dictionaries\/Framework\/System.Workflow.ComponentModel.dict,$VIM\/vimfiles\/DotNet\/Dictionaries\/Framework\/System.Workflow.Runtime.dict,$VIM\/vimfiles\/DotNet\/Dictionaries\/Framework\/System.Xaml.dict,$VIM\/vimfiles\/DotNet\/Dictionaries\/Framework\/System.Xml.Linq.dict,$VIM\/vimfiles\/DotNet\/Dictionaries\/Framework\/System.Xml.dict,$VIM\/vimfiles\/DotNet\/Dictionaries\/Framework\/System.dict,$VIM\/vimfiles\/DotNet\/Dictionaries\/Framework\/WindowsBase.dict,$VIM\/vimfiles\/DotNet\/Dictionaries\/Framework\/directory.txt,$VIM\/vimfiles\/DotNet\/Dictionaries\/Framework\/mscorlib.dict\r\n\r\nHelp in vim:\r\n:h ins-completion\r\n\r\n","5":"I use it for auto-completion.\r\n\r\nI have the line \r\n\r\nset dict+=$VIM\/vimfiles\/DotNet\/Dictionaries\/Framework\/PresentationCore.dict,$VIM\/vimfiles\/DotNet\/Dictionaries\/Framework\/PresentationFramework.dict,$VIM\/vimfiles\/DotNet\/Dictionaries\/Framework\/System.Configuration.dict,$VIM\/vimfiles\/DotNet\/Dictionaries\/Framework\/System.Core.dict,$VIM\/vimfiles\/DotNet\/Dictionaries\/Framework\/System.Data.SqlXml.dict,$VIM\/vimfiles\/DotNet\/Dictionaries\/Framework\/System.Data.dict,$VIM\/vimfiles\/DotNet\/Dictionaries\/Framework\/System.Drawing.dict,$VIM\/vimfiles\/DotNet\/Dictionaries\/Framework\/System.Numerics.dict,$VIM\/vimfiles\/DotNet\/Dictionaries\/Framework\/System.Security.dict,$VIM\/vimfiles\/DotNet\/Dictionaries\/Framework\/System.ServiceModel.dict,$VIM\/vimfiles\/DotNet\/Dictionaries\/Framework\/System.Web.dict,$VIM\/vimfiles\/DotNet\/Dictionaries\/Framework\/System.Windows.Forms.dict,$VIM\/vimfiles\/DotNet\/Dictionaries\/Framework\/System.Workflow.Activities.dict,$VIM\/vimfiles\/DotNet\/Dictionaries\/Framework\/System.Workflow.ComponentModel.dict,$VIM\/vimfiles\/DotNet\/Dictionaries\/Framework\/System.Workflow.Runtime.dict,$VIM\/vimfiles\/DotNet\/Dictionaries\/Framework\/System.Xaml.dict,$VIM\/vimfiles\/DotNet\/Dictionaries\/Framework\/System.Xml.Linq.dict,$VIM\/vimfiles\/DotNet\/Dictionaries\/Framework\/System.Xml.dict,$VIM\/vimfiles\/DotNet\/Dictionaries\/Framework\/System.dict,$VIM\/vimfiles\/DotNet\/Dictionaries\/Framework\/WindowsBase.dict,$VIM\/vimfiles\/DotNet\/Dictionaries\/Framework\/directory.txt,$VIM\/vimfiles\/DotNet\/Dictionaries\/Framework\/mscorlib.dict\r\n\r\nHelp in vim:\r\n:h ins-completion\r\n\r\n","first_name":"Klaus","6":"Klaus","last_name":"Horsten","7":"Horsten","releases":[{"0":"667","vim_version":"7.0","1":"7.0","script_version":"2.0","2":"2.0","version_comment":"Dotnet Framework 4.0","3":"Dotnet Framework 4.0","package":"DotnetDictionaries.zip","4":"DotnetDictionaries.zip","src_id":"14140","5":"14140","creation_date":"1288280158","6":"1288280158"},{"0":"667","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"DotnetDictionaries.zip","4":"DotnetDictionaries.zip","src_id":"2049","5":"2049","creation_date":"1055061199","6":"1055061199"}]},"666":{"script_id":"666","0":"666","script_name":"hexman.vim","1":"hexman.vim","script_type":"utility","2":"utility","summary":"Simpler Hex viewing and editing","3":"Simpler Hex viewing and editing","description":"Hexmanger provides keymapping to view quickly your file\r\nin hexmode (convertion is done over the program xxd).\r\n                                                              \r\nAdditional features:\r\n- shows in statusline the current offset (hex and dec.)\r\n- move to next\/previous hex character with <TAB> and <S-TAB>\r\n  If you don't like this mapping - please set in your vimrc:\r\n  let hex_movetab = 0\r\n- staying on a hex character it marks the related ascii column\r\n- Goto hex offset\t\r\n- Delete hex character under cursor\t\r\n- Insert ascii character before cursor\t\r\n\r\nAvailable functions:\r\n                                                                    \r\n<leader> hm\tHexManager: Call\/Leave Hexmode (using xxd)\r\n<leader> hd  \tHexDelete: delete hex character under cursor\r\n<leader> hi  \tHexInsert: Insert Ascii character before cursor\r\n<leader> hg  \tHexGoto: Goto hex offset. \r\n<leader> hn  \tHexNext: Goto next hex offset. \r\n<leader> hp  \tHexPrev: Goto previous hex offset. \r\n<leader> hs  \tHexStatus: Show \/ Hide hexoffset infos in statusline\r\n                         and related ascii column\r\n                                                                    \r\nIf you want, you can change the mapping in your vimrc:\r\nExample (call with function key F6 the Hexmode:\r\nmap <F6>  <Plug>HexManager                                          \r\n\r\n                     \r\n","4":"Hexmanger provides keymapping to view quickly your file\r\nin hexmode (convertion is done over the program xxd).\r\n                                                              \r\nAdditional features:\r\n- shows in statusline the current offset (hex and dec.)\r\n- move to next\/previous hex character with <TAB> and <S-TAB>\r\n  If you don't like this mapping - please set in your vimrc:\r\n  let hex_movetab = 0\r\n- staying on a hex character it marks the related ascii column\r\n- Goto hex offset\t\r\n- Delete hex character under cursor\t\r\n- Insert ascii character before cursor\t\r\n\r\nAvailable functions:\r\n                                                                    \r\n<leader> hm\tHexManager: Call\/Leave Hexmode (using xxd)\r\n<leader> hd  \tHexDelete: delete hex character under cursor\r\n<leader> hi  \tHexInsert: Insert Ascii character before cursor\r\n<leader> hg  \tHexGoto: Goto hex offset. \r\n<leader> hn  \tHexNext: Goto next hex offset. \r\n<leader> hp  \tHexPrev: Goto previous hex offset. \r\n<leader> hs  \tHexStatus: Show \/ Hide hexoffset infos in statusline\r\n                         and related ascii column\r\n                                                                    \r\nIf you want, you can change the mapping in your vimrc:\r\nExample (call with function key F6 the Hexmode:\r\nmap <F6>  <Plug>HexManager                                          \r\n\r\n                     \r\n","install_details":"Normally, this file should reside in the plugins\r\ndirectory and be automatically sourced. If not, you must\r\nmanually source this file using ':source hexman.vim'.\r\n                                                            \r\nIf you want to edit a file in hexmode, start vim \r\nwith the -b option - like:\r\n      vim -b <file>\r\nand then switch to hexmode with <leader>hm\r\n(see Available functions).\r\nThe program xxd is needed to convert the file in hex (and\r\nback).\r\nOnly changes in the hex part are used.  \r\nChanges in the printable text part on the right are ignored.\r\n\r\nAdditional help:\r\n:help *23.4* \r\n:help xxd                                                   \r\n","5":"Normally, this file should reside in the plugins\r\ndirectory and be automatically sourced. If not, you must\r\nmanually source this file using ':source hexman.vim'.\r\n                                                            \r\nIf you want to edit a file in hexmode, start vim \r\nwith the -b option - like:\r\n      vim -b <file>\r\nand then switch to hexmode with <leader>hm\r\n(see Available functions).\r\nThe program xxd is needed to convert the file in hex (and\r\nback).\r\nOnly changes in the hex part are used.  \r\nChanges in the printable text part on the right are ignored.\r\n\r\nAdditional help:\r\n:help *23.4* \r\n:help xxd                                                   \r\n","first_name":"Peter","6":"Peter","last_name":"Franz","7":"Franz","releases":[{"0":"666","vim_version":"7.0","1":"7.0","script_version":"0.7.3","2":"0.7.3","version_comment":"Gvim 7.4 support - xxd on Windows was not found (again).\r\nHope it works also upwards vim 7.4","3":"Gvim 7.4 support - xxd on Windows was not found (again).\r\nHope it works also upwards vim 7.4","package":"hexman.vim","4":"hexman.vim","src_id":"21365","5":"21365","creation_date":"1390497090","6":"1390497090"},{"0":"666","vim_version":"6.0","1":"6.0","script_version":"0.7.2","2":"0.7.2","version_comment":"Patch from Ingo Karkat \/ 'xxd' did not start when VIM is installed in a directory containing spaces (e.g. on an English Windows XP: \r\n\"c:\\Program Files\\vim\\vim70\\xxd.exe\").","3":"Patch from Ingo Karkat \/ 'xxd' did not start when VIM is installed in a directory containing spaces (e.g. on an English Windows XP: \r\n\"c:\\Program Files\\vim\\vim70\\xxd.exe\").","package":"hexman.vim","4":"hexman.vim","src_id":"6621","5":"6621","creation_date":"1169120138","6":"1169120138"},{"0":"666","vim_version":"6.0","1":"6.0","script_version":"0.7.1","2":"0.7.1","version_comment":"Patch from Alejandro Cornejo \/ language independent cursor offset calculation.","3":"Patch from Alejandro Cornejo \/ language independent cursor offset calculation.","package":"hexman.vim","4":"hexman.vim","src_id":"6616","5":"6616","creation_date":"1168934560","6":"1168934560"},{"0":"666","vim_version":"7.0","1":"7.0","script_version":"0.7.0","2":"0.7.0","version_comment":"Support vim7 (xxd was not found \/ fix match syntax)","3":"Support vim7 (xxd was not found \/ fix match syntax)","package":"hexman.vim","4":"hexman.vim","src_id":"5498","5":"5498","creation_date":"1143681044","6":"1143681044"},{"0":"666","vim_version":"6.0","1":"6.0","script_version":"0.6.0","2":"0.6.0","version_comment":"Search Hex Character with \\hf  \r\nWith search history eg. \/<Up> you can repeat the search.\r\nPossibility to switch off advanced ascii\/hex editing \r\n(see Additional Features in Script).\r\n","3":"Search Hex Character with \\hf  \r\nWith search history eg. \/<Up> you can repeat the search.\r\nPossibility to switch off advanced ascii\/hex editing \r\n(see Additional Features in Script).\r\n","package":"hexman.vim","4":"hexman.vim","src_id":"2501","5":"2501","creation_date":"1069310604","6":"1069310604"},{"0":"666","vim_version":"6.0","1":"6.0","script_version":"0.5.1","2":"0.5.1","version_comment":"FIX: Editing in Hex part was not possible (as of 0.5.0).","3":"FIX: Editing in Hex part was not possible (as of 0.5.0).","package":"hexman.vim","4":"hexman.vim","src_id":"2442","5":"2442","creation_date":"1067603075","6":"1067603075"},{"0":"666","vim_version":"6.0","1":"6.0","script_version":"0.5.0","2":"0.5.0","version_comment":"Changes in the printable text part (ascii area) are now supported in\r\nReplace mode (command \"R\" or Select Mode \"gh\" ) \r\nfor most characters (see Known Problems).\r\n","3":"Changes in the printable text part (ascii area) are now supported in\r\nReplace mode (command \"R\" or Select Mode \"gh\" ) \r\nfor most characters (see Known Problems).\r\n","package":"hexman.vim","4":"hexman.vim","src_id":"2439","5":"2439","creation_date":"1067559294","6":"1067559294"},{"0":"666","vim_version":"6.0","1":"6.0","script_version":"0.4.1","2":"0.4.1","version_comment":"More features: \r\n- Switch cursor between hex and ascii area with t  or  <leader>ht\r\n  (or map it to a different keymap in vimrc  e.g.: map <F7>  Plug>HexToggle)\r\n- After calling\/leaving hexman the cursor is set to current file position.","3":"More features: \r\n- Switch cursor between hex and ascii area with t  or  <leader>ht\r\n  (or map it to a different keymap in vimrc  e.g.: map <F7>  Plug>HexToggle)\r\n- After calling\/leaving hexman the cursor is set to current file position.","package":"hexman.vim","4":"hexman.vim","src_id":"2241","5":"2241","creation_date":"1061261933","6":"1061261933"},{"0":"666","vim_version":"6.0","1":"6.0","script_version":"0.2.1","2":"0.2.1","version_comment":"Bugfixes (one from Ingo karkat - thank you). New feature: Staying on a ascii character it marks the related hex column.","3":"Bugfixes (one from Ingo karkat - thank you). New feature: Staying on a ascii character it marks the related hex column.","package":"hexman.vim","4":"hexman.vim","src_id":"2216","5":"2216","creation_date":"1060309253","6":"1060309253"},{"0":"666","vim_version":"6.0","1":"6.0","script_version":"0.1.0","2":"0.1.0","version_comment":"Show own hexman menu entry with hexman commands (gui version).\r\nIf you don't like the menu - please set in your vimrc:\r\nlet hex_menu = 0","3":"Show own hexman menu entry with hexman commands (gui version).\r\nIf you don't like the menu - please set in your vimrc:\r\nlet hex_menu = 0","package":"hexman.vim","4":"hexman.vim","src_id":"2194","5":"2194","creation_date":"1059564152","6":"1059564152"},{"0":"666","vim_version":"6.0","1":"6.0","script_version":"0.0.2","2":"0.0.2","version_comment":"FIX: default moving to next hex character \r\nwith <TAB> and <S-TAB> don't work on (LINUX\/UNIX)\r\n","3":"FIX: default moving to next hex character \r\nwith <TAB> and <S-TAB> don't work on (LINUX\/UNIX)\r\n","package":"hexman.vim","4":"hexman.vim","src_id":"2078","5":"2078","creation_date":"1055557213","6":"1055557213"},{"0":"666","vim_version":"6.0","1":"6.0","script_version":"0.0.1","2":"0.0.1","version_comment":"Initial upload","3":"Initial upload","package":"hexman.vim","4":"hexman.vim","src_id":"2046","5":"2046","creation_date":"1054813088","6":"1054813088"}]},"665":{"script_id":"665","0":"665","script_name":"FeralToggleCommentify.vim","1":"FeralToggleCommentify.vim","script_type":"utility","2":"utility","summary":"My fork of ToggleCommentify.vim; comment lines in a program","3":"My fork of ToggleCommentify.vim; comment lines in a program","description":"This script offers simple, basic, line oriented commenting of files.\r\nOriginally vimscript #4 (ToggleCommentify.vim v1.2 ) by Vincent Nijs\r\nWas mutilated into what you see here, for better or worse :)\r\n\r\nFollowing list of file types are currently (v1.55) supported:\r\n    ox, cpp, php, java, bnk, cs, ftf, torquescript, fte, html, xml, c, css,\r\n    pov, vim, lisp, scheme, dosini, tex, caos, m4, config, automake, python,\r\n    perl, make, [^w]sh$, tcl, jproperties, vb, aspvbs, plsql, lua,\r\n\r\n\r\nThree commands:\r\n:CC        \" To Comment a line\/range\r\n:UC        \" To Uncomment a line\/range\r\n:TC        \" To Toggle comments on each line\/range.\r\n\r\nAll take optional arg to override default comment style\r\ni.e. \":CC --\"\r\n\r\nMaps <m-c> to :TC if no command by that name already exists. Remap <Plug>FtcTc\r\n    at will.\r\nMaps <C-c> to a duplicate and comment, line\/range; so you can easily make a\r\n    duplicate of the current line\/range and comment it; then edit it the\r\n    original. Remap <Plug>FtcDLAC at will.\r\n\r\n**********\r\nNew with v1.55:\r\nYou can customize the behavior by specifying optional option vars. Each option\r\nvar can be specified as buffer or global, with that precedence.\r\n\r\nOption: g:FTCOperateOnFirstColumnOnly\r\n    If this is 0 (false) then the comment char does not have to be at col1 to\r\n    be removed, in addition comment chars are placed just before the first word\r\n    of the line.\r\nValid Values: 0 or 1\r\nDefault: 1\r\n\r\nOption: g:FTCOperateOnlyOnNonComments\r\n    If 1 (true) a line will not be commented if it already starts with comment\r\n    chars. With this 0 (false) you can (easily) comment entire functions\r\n    without fear of messing up commenting (i.e. '<,'>CC ... '<,'>UC ...  I.e.\r\n    comment then uncomment. If this is true the above MAY not work (depending\r\n    on how the existing comments are.)\r\nValid Values: 0 or 1\r\nDefault: 0\r\n\r\nOption: g:FTCOperateOnBlankLines\r\n    If 1 (true) blank lines will be processed, else they are skipped.\r\nValid Values: 0 or 1\r\nDefault: 1\r\n\r\nOption: g:FTCBangEffectsWhat\r\n    Will toggle an option if command is banged: (i.e. :CC!)\r\n        1. OperateOnFirstColumnOnly\r\n        2. OperateOnlyOnNonComments\r\n        3. OperateOnBlankLines\r\nValid Values: 1, 2 or 3\r\nDefault: 1\r\n\r\n\r\nI.e. in .vimrc:\r\nlet g:FTCOperateOnFirstColumnOnly = 0\r\nlet g:FTCOperateOnlyOnNonComments = 1","4":"This script offers simple, basic, line oriented commenting of files.\r\nOriginally vimscript #4 (ToggleCommentify.vim v1.2 ) by Vincent Nijs\r\nWas mutilated into what you see here, for better or worse :)\r\n\r\nFollowing list of file types are currently (v1.55) supported:\r\n    ox, cpp, php, java, bnk, cs, ftf, torquescript, fte, html, xml, c, css,\r\n    pov, vim, lisp, scheme, dosini, tex, caos, m4, config, automake, python,\r\n    perl, make, [^w]sh$, tcl, jproperties, vb, aspvbs, plsql, lua,\r\n\r\n\r\nThree commands:\r\n:CC        \" To Comment a line\/range\r\n:UC        \" To Uncomment a line\/range\r\n:TC        \" To Toggle comments on each line\/range.\r\n\r\nAll take optional arg to override default comment style\r\ni.e. \":CC --\"\r\n\r\nMaps <m-c> to :TC if no command by that name already exists. Remap <Plug>FtcTc\r\n    at will.\r\nMaps <C-c> to a duplicate and comment, line\/range; so you can easily make a\r\n    duplicate of the current line\/range and comment it; then edit it the\r\n    original. Remap <Plug>FtcDLAC at will.\r\n\r\n**********\r\nNew with v1.55:\r\nYou can customize the behavior by specifying optional option vars. Each option\r\nvar can be specified as buffer or global, with that precedence.\r\n\r\nOption: g:FTCOperateOnFirstColumnOnly\r\n    If this is 0 (false) then the comment char does not have to be at col1 to\r\n    be removed, in addition comment chars are placed just before the first word\r\n    of the line.\r\nValid Values: 0 or 1\r\nDefault: 1\r\n\r\nOption: g:FTCOperateOnlyOnNonComments\r\n    If 1 (true) a line will not be commented if it already starts with comment\r\n    chars. With this 0 (false) you can (easily) comment entire functions\r\n    without fear of messing up commenting (i.e. '<,'>CC ... '<,'>UC ...  I.e.\r\n    comment then uncomment. If this is true the above MAY not work (depending\r\n    on how the existing comments are.)\r\nValid Values: 0 or 1\r\nDefault: 0\r\n\r\nOption: g:FTCOperateOnBlankLines\r\n    If 1 (true) blank lines will be processed, else they are skipped.\r\nValid Values: 0 or 1\r\nDefault: 1\r\n\r\nOption: g:FTCBangEffectsWhat\r\n    Will toggle an option if command is banged: (i.e. :CC!)\r\n        1. OperateOnFirstColumnOnly\r\n        2. OperateOnlyOnNonComments\r\n        3. OperateOnBlankLines\r\nValid Values: 1, 2 or 3\r\nDefault: 1\r\n\r\n\r\nI.e. in .vimrc:\r\nlet g:FTCOperateOnFirstColumnOnly = 0\r\nlet g:FTCOperateOnlyOnNonComments = 1","install_details":"Just drop in plugins\/","5":"Just drop in plugins\/","first_name":"Robert","6":"Robert","last_name":"KellyIV","7":"KellyIV","releases":[{"0":"665","vim_version":"6.0","1":"6.0","script_version":"1.611","2":"1.611","version_comment":"1.61 - Improved\/Fixed cursor restore. Screen should not jump; ever.\r\n1.611 - bugfix for above for column jumping about, *sigh*.","3":"1.61 - Improved\/Fixed cursor restore. Screen should not jump; ever.\r\n1.611 - bugfix for above for column jumping about, *sigh*.","package":"feraltogglecommentify.vim","4":"feraltogglecommentify.vim","src_id":"4220","5":"4220","creation_date":"1114705689","6":"1114705689"},{"0":"665","vim_version":"6.0","1":"6.0","script_version":"1.58","2":"1.58","version_comment":"Added rebol ';' comment type, contribution by Tim Johnson\r\n","3":"Added rebol ';' comment type, contribution by Tim Johnson\r\n","package":"feraltogglecommentify.vim","4":"feraltogglecommentify.vim","src_id":"2273","5":"2273","creation_date":"1062031510","6":"1062031510"},{"0":"665","vim_version":"6.0","1":"6.0","script_version":"1.57","2":"1.57","version_comment":"Added ruby \\'#\\' comment type, contribution by Brett Williams\r\nAdded sh \\'#\\' comment type.","3":"Added ruby \\'#\\' comment type, contribution by Brett Williams\r\nAdded sh \\'#\\' comment type.","package":"feraltogglecommentify.vim","4":"feraltogglecommentify.vim","src_id":"2243","5":"2243","creation_date":"1061292653","6":"1061292653"},{"0":"665","vim_version":"6.0","1":"6.0","script_version":"1.56","2":"1.56","version_comment":"BUG FIX: Fixed silly cursor restore problem, screen no longer jumps on occasion.\r\n","3":"BUG FIX: Fixed silly cursor restore problem, screen no longer jumps on occasion.\r\n","package":"feraltogglecommentify.vim","4":"feraltogglecommentify.vim","src_id":"2175","5":"2175","creation_date":"1058794466","6":"1058794466"},{"0":"665","vim_version":"6.0","1":"6.0","script_version":"1.55","2":"1.55","version_comment":"Integrating changes from J\u00c3\u00b6rn Horstmann. Changes are marked with \"JH:\".\r\nImprovement:    Added options to determine how this should react.\r\n* Optionally does not mess with blank lines.\r\n* Change by JH, comment does not have to be in first column\r\n* Change by JH, only add comment when not already commented\r\nPlease see \"Customizing:\" (in the script file) for details and usage:\r\n","3":"Integrating changes from J\u00c3\u00b6rn Horstmann. Changes are marked with \"JH:\".\r\nImprovement:    Added options to determine how this should react.\r\n* Optionally does not mess with blank lines.\r\n* Change by JH, comment does not have to be in first column\r\n* Change by JH, only add comment when not already commented\r\nPlease see \"Customizing:\" (in the script file) for details and usage:\r\n","package":"feraltogglecommentify.vim","4":"feraltogglecommentify.vim","src_id":"2152","5":"2152","creation_date":"1058377986","6":"1058377986"},{"0":"665","vim_version":"6.0","1":"6.0","script_version":"1.54","2":"1.54","version_comment":"2 BUG FIXes, 2 Improvements:\r\n* BUG FIX: (minor) no longer complains when uncommenting and there are no comment char(s). (aka middle of a range is uncommented already)\r\n* BUG FIX: Respects 'hlsearch'; won't mess with highlighting if off, etc. (Previous turned it on at end of script)\r\n* Improvement: Can now comment\/uncomment a fold without opening it.  (courtesy of normal! zn and normal! zN)\r\n* Improvement: Changed DLAC into a proper command (:DLAC) (from mapping); map <Plug>FtcDLAC as desired, defaults to <C-c>. Ranges are supported (default current line) and you can specify the comment chars just as you can with :CC, :TC, :UC.","3":"2 BUG FIXes, 2 Improvements:\r\n* BUG FIX: (minor) no longer complains when uncommenting and there are no comment char(s). (aka middle of a range is uncommented already)\r\n* BUG FIX: Respects 'hlsearch'; won't mess with highlighting if off, etc. (Previous turned it on at end of script)\r\n* Improvement: Can now comment\/uncomment a fold without opening it.  (courtesy of normal! zn and normal! zN)\r\n* Improvement: Changed DLAC into a proper command (:DLAC) (from mapping); map <Plug>FtcDLAC as desired, defaults to <C-c>. Ranges are supported (default current line) and you can specify the comment chars just as you can with :CC, :TC, :UC.","package":"feraltogglecommentify.vim","4":"feraltogglecommentify.vim","src_id":"2145","5":"2145","creation_date":"1058006781","6":"1058006781"},{"0":"665","vim_version":"6.0","1":"6.0","script_version":"1.532","2":"1.532","version_comment":"Initial upload","3":"Initial upload","package":"FeralToggleCommentify.vim","4":"FeralToggleCommentify.vim","src_id":"2043","5":"2043","creation_date":"1054714112","6":"1054714112"}]},"664":{"script_id":"664","0":"664","script_name":"scratch.vim","1":"scratch.vim","script_type":"utility","2":"utility","summary":"Plugin to create and use a scratch Vim buffer","3":"Plugin to create and use a scratch Vim buffer","description":"Overview\r\n\r\nYou can use the scratch plugin to create a temporary scratch buffer to store\r\nand edit text that will be discarded when you quit\/exit vim. The contents\r\nof the scratch buffer are not saved\/stored in a file.\r\n\r\nInstallation\r\n\r\n1. Copy the scratch.vim plugin to the $HOME\/.vim\/plugin directory. Refer to\r\n   the following Vim help topics for more information about Vim plugins:\r\n\r\n      :help add-plugin\r\n      :help add-global-plugin\r\n      :help runtimepath\r\n\r\n2. Restart Vim.\r\n\r\nUsage\r\n\r\nYou can use the following command to open\/edit the scratch buffer:\r\n\r\n      :Scratch\r\n\r\nTo open the scratch buffer in a new split window, use the following command:\r\n\r\n      :Sscratch\r\n\r\nWhen you close the scratch buffer window, the buffer will retain the\r\ncontents. You can again edit the scratch buffer by openeing it using one of\r\nthe above commands. There is no need to save the scatch buffer.\r\n\r\nWhen you quit\/exit Vim, the contents of the scratch buffer will be lost.\r\nYou will not be prompted to save the contents of the modified scratch\r\nbuffer.\r\n\r\nYou can have only one scratch buffer open in a single Vim instance. If the\r\ncurrent buffer has unsaved modifications, then the scratch buffer will be\r\nopened in a new window\r\n","4":"Overview\r\n\r\nYou can use the scratch plugin to create a temporary scratch buffer to store\r\nand edit text that will be discarded when you quit\/exit vim. The contents\r\nof the scratch buffer are not saved\/stored in a file.\r\n\r\nInstallation\r\n\r\n1. Copy the scratch.vim plugin to the $HOME\/.vim\/plugin directory. Refer to\r\n   the following Vim help topics for more information about Vim plugins:\r\n\r\n      :help add-plugin\r\n      :help add-global-plugin\r\n      :help runtimepath\r\n\r\n2. Restart Vim.\r\n\r\nUsage\r\n\r\nYou can use the following command to open\/edit the scratch buffer:\r\n\r\n      :Scratch\r\n\r\nTo open the scratch buffer in a new split window, use the following command:\r\n\r\n      :Sscratch\r\n\r\nWhen you close the scratch buffer window, the buffer will retain the\r\ncontents. You can again edit the scratch buffer by openeing it using one of\r\nthe above commands. There is no need to save the scatch buffer.\r\n\r\nWhen you quit\/exit Vim, the contents of the scratch buffer will be lost.\r\nYou will not be prompted to save the contents of the modified scratch\r\nbuffer.\r\n\r\nYou can have only one scratch buffer open in a single Vim instance. If the\r\ncurrent buffer has unsaved modifications, then the scratch buffer will be\r\nopened in a new window\r\n","install_details":"1. Copy the scratch.vim plugin to the $HOME\/.vim\/plugin directory.\r\n2. Restart Vim","5":"1. Copy the scratch.vim plugin to the $HOME\/.vim\/plugin directory.\r\n2. Restart Vim","first_name":"Yegappan","6":"Yegappan","last_name":"Lakshmanan","7":"Lakshmanan","releases":[{"0":"664","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Converted the plugin file format to unix from dos.","3":"Converted the plugin file format to unix from dos.","package":"scratch.vim","4":"scratch.vim","src_id":"2050","5":"2050","creation_date":"1055065275","6":"1055065275"}]},"663":{"script_id":"663","0":"663","script_name":"VimDebug","1":"VimDebug","script_type":"utility","2":"utility","summary":"Visual debugger for Perl, Ruby, and Python (updated 03\/2011)","3":"Visual debugger for Perl, Ruby, and Python (updated 03\/2011)","description":"VimDebug gives developers the ability to visually step through their code and set breakpoints.  Currently supported debuggers are Perl, Ruby, and Python.  \r\n\r\nThis plugin is still in beta.  Code is available on github: \r\nhttps:\/\/github.com\/kablamo\/VimDebug\r\n\r\nFor help or to report a bug, please go here:\r\nhttps:\/\/github.com\/kablamo\/VimDebug\/issues\r\n\r\n\r\n\r\nRequirements\r\n\r\nUbuntu\/OSX\/Unix\r\nPerl\r\n2 Perl modules\r\nVim with +signs compiled in.\r\n\r\n\r\nUsage\r\n\r\nSet\/reset these in your .vimrc if you want:\r\n\r\n<F12>      Start the debugger\r\n<Leader>s\/ Start the debugger with command line arguments\r\n<F10>      Restart debugger.  Break points are saved.\r\n<F11>      Exit the debugger\r\n\r\n<F2>       Show console\r\n<F6>       Next\r\n<F7>       Step\r\n<F8>       Continue\r\n\r\n<Leader>b  Set break point on the current line\r\n<Leader>c  Clear break point on the current line\r\n\r\n<Leader>v  Show the value of variable under the cursor\r\n<Leader>v\/ Show the value of any expression\r\n\r\n<Leader>\/  Enter a command for the debugger to execute, and echo the result.\r\n\r\nlet g:DBGRconsoleHeight   = 7\r\nlet g:DBGRlineNumbers      = 1","4":"VimDebug gives developers the ability to visually step through their code and set breakpoints.  Currently supported debuggers are Perl, Ruby, and Python.  \r\n\r\nThis plugin is still in beta.  Code is available on github: \r\nhttps:\/\/github.com\/kablamo\/VimDebug\r\n\r\nFor help or to report a bug, please go here:\r\nhttps:\/\/github.com\/kablamo\/VimDebug\/issues\r\n\r\n\r\n\r\nRequirements\r\n\r\nUbuntu\/OSX\/Unix\r\nPerl\r\n2 Perl modules\r\nVim with +signs compiled in.\r\n\r\n\r\nUsage\r\n\r\nSet\/reset these in your .vimrc if you want:\r\n\r\n<F12>      Start the debugger\r\n<Leader>s\/ Start the debugger with command line arguments\r\n<F10>      Restart debugger.  Break points are saved.\r\n<F11>      Exit the debugger\r\n\r\n<F2>       Show console\r\n<F6>       Next\r\n<F7>       Step\r\n<F8>       Continue\r\n\r\n<Leader>b  Set break point on the current line\r\n<Leader>c  Clear break point on the current line\r\n\r\n<Leader>v  Show the value of variable under the cursor\r\n<Leader>v\/ Show the value of any expression\r\n\r\n<Leader>\/  Enter a command for the debugger to execute, and echo the result.\r\n\r\nlet g:DBGRconsoleHeight   = 7\r\nlet g:DBGRlineNumbers      = 1","install_details":"$ tar xvzf VimDebug*tar.gz\r\n$ cd VimDebug*\r\n$ perl Makefile.PL\r\n$ make\r\n$ sudo make install\r\n$ cp -r vim\/*vim $VIMHOME\/","5":"$ tar xvzf VimDebug*tar.gz\r\n$ cd VimDebug*\r\n$ perl Makefile.PL\r\n$ make\r\n$ sudo make install\r\n$ cp -r vim\/*vim $VIMHOME\/","first_name":"eric","6":"eric","last_name":"johnson","7":"johnson","releases":[{"0":"663","vim_version":"7.0","1":"7.0","script_version":"0.5","2":"0.5","version_comment":"Warns if you don't have IO::Pty installed; fixed newline problems for a number of people; fixed tab problems for people who use SuperTab plugin","3":"Warns if you don't have IO::Pty installed; fixed newline problems for a number of people; fixed tab problems for people who use SuperTab plugin","package":"VimDebug-0.5.tar.gz","4":"VimDebug-0.5.tar.gz","src_id":"14872","5":"14872","creation_date":"1296033882","6":"1296033882"},{"0":"663","vim_version":"6.0","1":"6.0","script_version":"0.4","2":"0.4","version_comment":"Dramatically improved debug console.  New underlying API makes adding support for new languages simpler.  Added support for Gdb, but this module is not yet tested.  This project is still in beta.","3":"Dramatically improved debug console.  New underlying API makes adding support for new languages simpler.  Added support for Gdb, but this module is not yet tested.  This project is still in beta.","package":"VimDebug-0.4.tar.gz","4":"VimDebug-0.4.tar.gz","src_id":"8131","5":"8131","creation_date":"1199661240","6":"1199661240"},{"0":"663","vim_version":"6.0","1":"6.0","script_version":"0.3.5","2":"0.3.5","version_comment":"added Python, a very basic debug console, and some other gui improvements; still beta","3":"added Python, a very basic debug console, and some other gui improvements; still beta","package":"VimDebug-0.3.5.tar.gz","4":"VimDebug-0.3.5.tar.gz","src_id":"8111","5":"8111","creation_date":"1199233415","6":"1199233415"},{"0":"663","vim_version":"6.0","1":"6.0","script_version":"0.3","2":"0.3","version_comment":"complete rewrite.  much more mature.  this version only supports perl and ruby.","3":"complete rewrite.  much more mature.  this version only supports perl and ruby.","package":"VimDebug-0.3.tar.gz","4":"VimDebug-0.3.tar.gz","src_id":"8103","5":"8103","creation_date":"1198988456","6":"1198988456"},{"0":"663","vim_version":"6.0","1":"6.0","script_version":"0.2","2":"0.2","version_comment":"fixed some problems with the install process (added multvals.vim)\r\nscript now works with perl v.5.6+ (instead of v.5.8+)\r\nfixed a bug involving arrays and eval() in the perl debugger module","3":"fixed some problems with the install process (added multvals.vim)\r\nscript now works with perl v.5.6+ (instead of v.5.8+)\r\nfixed a bug involving arrays and eval() in the perl debugger module","package":"vimDebug-0.2.tar.gz","4":"vimDebug-0.2.tar.gz","src_id":"2113","5":"2113","creation_date":"1056472324","6":"1056472324"},{"0":"663","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"vimDebug-0.1.tar.gz","4":"vimDebug-0.1.tar.gz","src_id":"2041","5":"2041","creation_date":"1054660036","6":"1054660036"}]},"662":{"script_id":"662","0":"662","script_name":"xml_cbks","1":"xml_cbks","script_type":"utility","2":"utility","summary":"Extends xmledit package to provide schema-specific attribute callbacks easily","3":"Extends xmledit package to provide schema-specific attribute callbacks easily","description":"This script extends the functionality of the excellent xmledit plugin.\r\nxmledit gives you a single global callback for inserting attributes,\r\nXmlAttribCallback.  The suggestion is that this method will dispatch based\r\non which tag is received.  The script provides a hook that will set the\r\nvariable b:xml_doctype when loaded (via the function XmlFindDocType).  Then\r\nit provides a generic XmlAttribCallback which does the following:\r\n  1.  Looks for a file called $VIMXMLEDITCALLBACKS\/{b:xml_doctype}.vim\r\n  2.  If that file exists and hasn\\'t already been loaded, it is sourced\r\nThis file is expected to provide a function called\r\nXmlAttribCallback_{b:xml_doctype}.  This function is called if it exists,\r\npassing the xml_tag as the argument.\r\n\r\nThe intent is so that you can have a different callback for each doctype (schema) which will automatically be available when you edit an XML file of a\r\nspecified type.  The plugin also provides a way to provide any doctype\r\nspecific functionality automatically (you can put anything in the sourced\r\nscript).   It is almost like a secondary ftplugin for xml.\r\n\r\nNote:  This is my first vim script (I\\'ve been using vim for less than 3 weeks) so any suggestions for improvement are very welcome.","4":"This script extends the functionality of the excellent xmledit plugin.\r\nxmledit gives you a single global callback for inserting attributes,\r\nXmlAttribCallback.  The suggestion is that this method will dispatch based\r\non which tag is received.  The script provides a hook that will set the\r\nvariable b:xml_doctype when loaded (via the function XmlFindDocType).  Then\r\nit provides a generic XmlAttribCallback which does the following:\r\n  1.  Looks for a file called $VIMXMLEDITCALLBACKS\/{b:xml_doctype}.vim\r\n  2.  If that file exists and hasn\\'t already been loaded, it is sourced\r\nThis file is expected to provide a function called\r\nXmlAttribCallback_{b:xml_doctype}.  This function is called if it exists,\r\npassing the xml_tag as the argument.\r\n\r\nThe intent is so that you can have a different callback for each doctype (schema) which will automatically be available when you edit an XML file of a\r\nspecified type.  The plugin also provides a way to provide any doctype\r\nspecific functionality automatically (you can put anything in the sourced\r\nscript).   It is almost like a secondary ftplugin for xml.\r\n\r\nNote:  This is my first vim script (I\\'ve been using vim for less than 3 weeks) so any suggestions for improvement are very welcome.","install_details":"Put xml_cbks.vim in your plugin directory (personal or shared).\r\n\r\nPut xml_cbks.txt in your doc directory and then see :help add-local-help to install the help.","5":"Put xml_cbks.vim in your plugin directory (personal or shared).\r\n\r\nPut xml_cbks.txt in your doc directory and then see :help add-local-help to install the help.","first_name":"Brett","6":"Brett","last_name":"Williams","7":"Williams","releases":[{"0":"662","vim_version":"6.0","1":"6.0","script_version":"0.11","2":"0.11","version_comment":"Fixed some unlets which were out of place.","3":"Fixed some unlets which were out of place.","package":"xml_cbks.zip","4":"xml_cbks.zip","src_id":"2035","5":"2035","creation_date":"1054543832","6":"1054543832"},{"0":"662","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"xml_cbks.zip","4":"xml_cbks.zip","src_id":"2033","5":"2033","creation_date":"1054542195","6":"1054542195"}]},"661":{"script_id":"661","0":"661","script_name":"gnupg","1":"gnupg","script_type":"utility","2":"utility","summary":"Plugin for transparent editing of gpg encrypted files.","3":"Plugin for transparent editing of gpg encrypted files.","description":"Due to the lack of time I'm not able to continue the development of this script.\r\nJames McCoy took over development. New versions can be found at vimscript #3645.\r\n\r\nThis script implements transparent editing of gpg encrypted files. The filename must have a \".gpg\", \".pgp\" or \".asc\" suffix. When opening such a file the content is decrypted, when opening a new file the script will ask for the recipients of the encrypted file. The file content will be encrypted to all recipients before it is written. The script turns off viminfo and swapfile to increase security.\r\n\r\nCommands:\r\n\r\n  :GPGEditRecipients\r\n    Opens a scratch buffer to change the list of recipients. Recipients that\r\n    are unknown (not in your public key) are highlighted and have\r\n    a prepended \"!\". Closing the buffer makes the changes permanent.\r\n\r\n  :GPGViewRecipients\r\n    Prints the list of recipients.\r\n\r\n  :GPGEditOptions\r\n    Opens a scratch buffer to change the options for encryption (symmetric,\r\n    asymmetric, signing). Closing the buffer makes the changes permanent.\r\n    WARNING: There is no check of the entered options, so you need to know\r\n    what you are doing.\r\n\r\n  :GPGViewOptions\r\n    Prints the list of options.\r\n\r\nVariables:\r\n\r\n  g:GPGExecutable\r\n    If set used as gpg executable, otherwise the system chooses what is run\r\n    when \"gpg\" is called. Defaults to \"gpg\".\r\n\r\n  g:GPGUseAgent\r\n    If set to 0 a possible available gpg-agent won't be used. Defaults to 1.\r\n\r\n  g:GPGPreferSymmetric\r\n    If set to 1 symmetric encryption is preferred for new files. Defaults to 0.\r\n\r\n  g:GPGPreferArmor\r\n    If set to 1 armored data is preferred for new files. Defaults to 0.\r\n\r\n  g:GPGPreferSign\r\n    If set to 1 signed data is preferred for new files. Defaults to 0.\r\n\r\n  g:GPGDefaultRecipients\r\n    If set, these recipients are used as defaults when no other recipient is\r\n    defined. This variable is a Vim list. Default is unset.\r\n\r\nKnown Issues:\r\n\r\n  In some cases gvim can't decryt files\r\n\r\n  This is caused by the fact that a running gvim has no TTY and thus gpg is\r\n  not able to ask for the passphrase by itself. This is a problem for Windows\r\n  and Linux versions of gvim and could not be solved unless a \"terminal\r\n  emulation\" is implemented for gvim. To circumvent this you have to use any\r\n  combination of gpg-agent and a graphical pinentry program:\r\n\r\n    - gpg-agent only:\r\n        you need to provide the passphrase for the needed key to gpg-agent\r\n        in a terminal before you open files with gvim which require this key.\r\n\r\n    - pinentry only:\r\n        you will get a popup window every time you open a file that needs to\r\n        be decrypted.\r\n\r\n    - gpgagent and pinentry:\r\n        you will get a popup window the first time you open a file that\r\n        needs to be decrypted.\r\n","4":"Due to the lack of time I'm not able to continue the development of this script.\r\nJames McCoy took over development. New versions can be found at vimscript #3645.\r\n\r\nThis script implements transparent editing of gpg encrypted files. The filename must have a \".gpg\", \".pgp\" or \".asc\" suffix. When opening such a file the content is decrypted, when opening a new file the script will ask for the recipients of the encrypted file. The file content will be encrypted to all recipients before it is written. The script turns off viminfo and swapfile to increase security.\r\n\r\nCommands:\r\n\r\n  :GPGEditRecipients\r\n    Opens a scratch buffer to change the list of recipients. Recipients that\r\n    are unknown (not in your public key) are highlighted and have\r\n    a prepended \"!\". Closing the buffer makes the changes permanent.\r\n\r\n  :GPGViewRecipients\r\n    Prints the list of recipients.\r\n\r\n  :GPGEditOptions\r\n    Opens a scratch buffer to change the options for encryption (symmetric,\r\n    asymmetric, signing). Closing the buffer makes the changes permanent.\r\n    WARNING: There is no check of the entered options, so you need to know\r\n    what you are doing.\r\n\r\n  :GPGViewOptions\r\n    Prints the list of options.\r\n\r\nVariables:\r\n\r\n  g:GPGExecutable\r\n    If set used as gpg executable, otherwise the system chooses what is run\r\n    when \"gpg\" is called. Defaults to \"gpg\".\r\n\r\n  g:GPGUseAgent\r\n    If set to 0 a possible available gpg-agent won't be used. Defaults to 1.\r\n\r\n  g:GPGPreferSymmetric\r\n    If set to 1 symmetric encryption is preferred for new files. Defaults to 0.\r\n\r\n  g:GPGPreferArmor\r\n    If set to 1 armored data is preferred for new files. Defaults to 0.\r\n\r\n  g:GPGPreferSign\r\n    If set to 1 signed data is preferred for new files. Defaults to 0.\r\n\r\n  g:GPGDefaultRecipients\r\n    If set, these recipients are used as defaults when no other recipient is\r\n    defined. This variable is a Vim list. Default is unset.\r\n\r\nKnown Issues:\r\n\r\n  In some cases gvim can't decryt files\r\n\r\n  This is caused by the fact that a running gvim has no TTY and thus gpg is\r\n  not able to ask for the passphrase by itself. This is a problem for Windows\r\n  and Linux versions of gvim and could not be solved unless a \"terminal\r\n  emulation\" is implemented for gvim. To circumvent this you have to use any\r\n  combination of gpg-agent and a graphical pinentry program:\r\n\r\n    - gpg-agent only:\r\n        you need to provide the passphrase for the needed key to gpg-agent\r\n        in a terminal before you open files with gvim which require this key.\r\n\r\n    - pinentry only:\r\n        you will get a popup window every time you open a file that needs to\r\n        be decrypted.\r\n\r\n    - gpgagent and pinentry:\r\n        you will get a popup window the first time you open a file that\r\n        needs to be decrypted.\r\n","install_details":"Copy the gnupg.vim file to the $HOME\/.vim\/plugin directory. Refer to ':help add-plugin', ':help add-global-plugin' and ':help runtimepath' for more details about Vim plugins.\r\n\r\nFrom \"man 1 gpg-agent\":\r\n...\r\nYou should always add the following lines to your .bashrc or whatever initialization file is used for all shell invocations:\r\n\r\n     GPG_TTY=`tty`\r\n     export GPG_TTY\r\n\r\nIt is important that this environment variable always reflects the output of the tty command. For W32 systems this option is not required.\r\n...\r\n\r\nMost distributions provide software to ease handling of gpg and gpg-agent. Examples are keychain or seahorse.\r\n","5":"Copy the gnupg.vim file to the $HOME\/.vim\/plugin directory. Refer to ':help add-plugin', ':help add-global-plugin' and ':help runtimepath' for more details about Vim plugins.\r\n\r\nFrom \"man 1 gpg-agent\":\r\n...\r\nYou should always add the following lines to your .bashrc or whatever initialization file is used for all shell invocations:\r\n\r\n     GPG_TTY=`tty`\r\n     export GPG_TTY\r\n\r\nIt is important that this environment variable always reflects the output of the tty command. For W32 systems this option is not required.\r\n...\r\n\r\nMost distributions provide software to ease handling of gpg and gpg-agent. Examples are keychain or seahorse.\r\n","first_name":"Markus","6":"Markus","last_name":"Braun","7":"Braun","releases":[{"0":"661","vim_version":"7.0","1":"7.0","script_version":"3026","2":"3026","version_comment":"- fix a bug by using a sh compatible setting for 'shellredir' on unix systems. when 'shell' was set to csh or tcsh by the user and the system has \/bin\/sh linked to dash the plugin didn't work.\r\n","3":"- fix a bug by using a sh compatible setting for 'shellredir' on unix systems. when 'shell' was set to csh or tcsh by the user and the system has \/bin\/sh linked to dash the plugin didn't work.\r\n","package":"gnupg.vim","4":"gnupg.vim","src_id":"12200","5":"12200","creation_date":"1264592567","6":"1264592567"},{"0":"661","vim_version":"7.0","1":"7.0","script_version":"2782","2":"2782","version_comment":"- show more information (key id and creation time) of keys in GPGEditRecipients, GPGViewRecipients and during selecting in case of a ambiguous key.\r\n","3":"- show more information (key id and creation time) of keys in GPGEditRecipients, GPGViewRecipients and during selecting in case of a ambiguous key.\r\n","package":"gnupg.vim","4":"gnupg.vim","src_id":"10833","5":"10833","creation_date":"1245069312","6":"1245069312"},{"0":"661","vim_version":"7.0","1":"7.0","script_version":"2773","2":"2773","version_comment":"- fix a bug in detecting windows platforms\r\n- added g:GPGPreferSign to sign encrypted files by default (thanks to Tim Swast).\r\n","3":"- fix a bug in detecting windows platforms\r\n- added g:GPGPreferSign to sign encrypted files by default (thanks to Tim Swast).\r\n","package":"gnupg.vim","4":"gnupg.vim","src_id":"10683","5":"10683","creation_date":"1243408720","6":"1243408720"},{"0":"661","vim_version":"7.0","1":"7.0","script_version":"2276","2":"2276","version_comment":"- added support for default recipients via the variable g:GPGDefaultRecipients.\r\n- fixed an wrong error message with symmetric encryption and set recipients (thanks to Sebastian Luettich).\r\n- create a empty new buffer on leaving vim to wipe out sensitive data on console.\r\n- make sure senisitive data is never written unencrypted to disk.","3":"- added support for default recipients via the variable g:GPGDefaultRecipients.\r\n- fixed an wrong error message with symmetric encryption and set recipients (thanks to Sebastian Luettich).\r\n- create a empty new buffer on leaving vim to wipe out sensitive data on console.\r\n- make sure senisitive data is never written unencrypted to disk.","package":"gnupg.vim","4":"gnupg.vim","src_id":"9142","5":"9142","creation_date":"1219037322","6":"1219037322"},{"0":"661","vim_version":"7.0","1":"7.0","script_version":"2249","2":"2249","version_comment":"- rewritten lots of code to use lists feature of vim 7 instead of my own implementation\r\n- added a n option to change the name and location of GPG executable\r\n- try to get GPG_TTY dynamically.","3":"- rewritten lots of code to use lists feature of vim 7 instead of my own implementation\r\n- added a n option to change the name and location of GPG executable\r\n- try to get GPG_TTY dynamically.","package":"gnupg.vim","4":"gnupg.vim","src_id":"9058","5":"9058","creation_date":"1217479554","6":"1217479554"},{"0":"661","vim_version":"6.0","1":"6.0","script_version":"1933","2":"1933","version_comment":"- changed parsin to work with gpg2 correctly\r\n- save\/restore view of saved window\r\n- fix a bug when encoding and fileencoding is different\r\n- restructured autocommand triggers\r\n- added a debug command and debug messages","3":"- changed parsin to work with gpg2 correctly\r\n- save\/restore view of saved window\r\n- fix a bug when encoding and fileencoding is different\r\n- restructured autocommand triggers\r\n- added a debug command and debug messages","package":"gnupg.vim","4":"gnupg.vim","src_id":"8174","5":"8174","creation_date":"1201075426","6":"1201075426"},{"0":"661","vim_version":"6.0","1":"6.0","script_version":"1605","2":"1605","version_comment":"- new plugin options to set preferences for symmetric\/asymmetric and armor\/binary files\r\n- fix for use with gvim. !! plugin works only in gvim if gpg-agent is available !!","3":"- new plugin options to set preferences for symmetric\/asymmetric and armor\/binary files\r\n- fix for use with gvim. !! plugin works only in gvim if gpg-agent is available !!","package":"gnupg.vim","4":"gnupg.vim","src_id":"6949","5":"6949","creation_date":"1175739626","6":"1175739626"},{"0":"661","vim_version":"6.0","1":"6.0","script_version":"1472","2":"1472","version_comment":"- support for symmetric encrypted files.\r\n- detection of various encryption options.\r\n- possibility to change gpg options using new commands GPGEditOptions and GPGViewOptions commands.\r\n- support editing files with '.gpg', '.pgp' and '.asc' suffixes (tanks to Richard Bronosky).\r\n- detection of unencrypted files.\r\n- support for windows systems (thanks to Erik Remmelzwaal).","3":"- support for symmetric encrypted files.\r\n- detection of various encryption options.\r\n- possibility to change gpg options using new commands GPGEditOptions and GPGViewOptions commands.\r\n- support editing files with '.gpg', '.pgp' and '.asc' suffixes (tanks to Richard Bronosky).\r\n- detection of unencrypted files.\r\n- support for windows systems (thanks to Erik Remmelzwaal).","package":"gnupg.vim","4":"gnupg.vim","src_id":"6518","5":"6518","creation_date":"1166160155","6":"1166160155"},{"0":"661","vim_version":"6.0","1":"6.0","script_version":"1.27","2":"1.27","version_comment":"updated documentation, that gnupg.vim only works for public\/private-key encrypted files.","3":"updated documentation, that gnupg.vim only works for public\/private-key encrypted files.","package":"gnupg.vim","4":"gnupg.vim","src_id":"2108","5":"2108","creation_date":"1056416299","6":"1056416299"},{"0":"661","vim_version":"6.0","1":"6.0","script_version":"1.26","2":"1.26","version_comment":"Initial upload","3":"Initial upload","package":"gnupg.vim","4":"gnupg.vim","src_id":"2029","5":"2029","creation_date":"1054261796","6":"1054261796"}]},"660":{"script_id":"660","0":"660","script_name":"gpg.vim","1":"gpg.vim","script_type":"utility","2":"utility","summary":"it seems that this inspired another much better script: gnupg.vim","3":"it seems that this inspired another much better script: gnupg.vim","description":"As I know little about vim scripts, this was just a thought which proved convenient for me. But I just noticed there's a new plugin called 'gnupg.vim' after this which is much better. Please download that instead. I tried to delete this from the server.\r\n\r\nThis little plugin helps to edit \"gpg\" encrypted files. I use this because it's more convenient when you do not have GUI encrypt tools.\r\n\r\nHow to use:\r\njust name the file with .gpg suffix, e.g. \"something.gpg\" and \r\nvi -u ~\/.vim\/gpg.vim something.gpg","4":"As I know little about vim scripts, this was just a thought which proved convenient for me. But I just noticed there's a new plugin called 'gnupg.vim' after this which is much better. Please download that instead. I tried to delete this from the server.\r\n\r\nThis little plugin helps to edit \"gpg\" encrypted files. I use this because it's more convenient when you do not have GUI encrypt tools.\r\n\r\nHow to use:\r\njust name the file with .gpg suffix, e.g. \"something.gpg\" and \r\nvi -u ~\/.vim\/gpg.vim something.gpg","install_details":"1. download and setup \"gpg\" ( see docs for gpg )\r\n2. setup your key for gpg, get the user name for the key, e.g. \"user@domain\"\r\n2. create two little scripts called \"dgpg\" and \"egpg\" and put them in your PATH.\r\n   in \"dgpg\":\r\n    \r\n   #!\/bin\/sh\r\n   gpg -d 2>\/dev\/null\r\n\r\n   in \"egpg\":\r\n   #!\/bin\/sh\r\n   gpg -e -r user@domain\r\n   # where user@domain is the user specified when you create your gpg key\r\n\r\n 3. drop gpg.vim in your ~\/.vim\/ directory","5":"1. download and setup \"gpg\" ( see docs for gpg )\r\n2. setup your key for gpg, get the user name for the key, e.g. \"user@domain\"\r\n2. create two little scripts called \"dgpg\" and \"egpg\" and put them in your PATH.\r\n   in \"dgpg\":\r\n    \r\n   #!\/bin\/sh\r\n   gpg -d 2>\/dev\/null\r\n\r\n   in \"egpg\":\r\n   #!\/bin\/sh\r\n   gpg -e -r user@domain\r\n   # where user@domain is the user specified when you create your gpg key\r\n\r\n 3. drop gpg.vim in your ~\/.vim\/ directory","first_name":"Guang","6":"Guang","last_name":"Liu","7":"Liu","releases":[{"0":"660","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"gpg.vim","4":"gpg.vim","src_id":"2027","5":"2027","creation_date":"1054230617","6":"1054230617"}]},"659":{"script_id":"659","0":"659","script_name":"sip.vim","1":"sip.vim","script_type":"syntax","2":"syntax","summary":"sip syntax file","3":"sip syntax file","description":"This is the syntax file for sip -- a program that can convert C++ to python. See http:\/\/riverbankcomputing.co.uk\/ for more information on what sip is and what you can do with it.","4":"This is the syntax file for sip -- a program that can convert C++ to python. See http:\/\/riverbankcomputing.co.uk\/ for more information on what sip is and what you can do with it.","install_details":"Just drop the syntax file in $VIM\/syntax\/sip.vim, or ~\/.vim\/syntax\/sip.vim, and add a line to $VIM\/filetype.vim that will identify *.sip with filetype 'sip'.","5":"Just drop the syntax file in $VIM\/syntax\/sip.vim, or ~\/.vim\/syntax\/sip.vim, and add a line to $VIM\/filetype.vim that will identify *.sip with filetype 'sip'.","first_name":"Jonathan","6":"Jonathan","last_name":"Gardner","7":"Gardner","releases":[{"0":"659","vim_version":"6.0","1":"6.0","script_version":"0.2","2":"0.2","version_comment":"This one should actually work better.","3":"This one should actually work better.","package":"sip.vim","4":"sip.vim","src_id":"2026","5":"2026","creation_date":"1054139842","6":"1054139842"}]},"658":{"script_id":"658","0":"658","script_name":"headers.vim","1":"headers.vim","script_type":"syntax","2":"syntax","summary":"Syntax highlighting for SMTP\/HTTP headers","3":"Syntax highlighting for SMTP\/HTTP headers","description":"Does some basic syntax highlighting for SMTP and HTTP header information.\r\n\r\nCurrently identifies and colours:\r\n  - header names\r\n  - dates\r\n  - times\r\n  - hostnames\r\n  - IP addresses\r\n  - content-type headers\r\n  - email addresses\r\n\r\nIt's kinda kludgy; corrections and suggestions welcome.","4":"Does some basic syntax highlighting for SMTP and HTTP header information.\r\n\r\nCurrently identifies and colours:\r\n  - header names\r\n  - dates\r\n  - times\r\n  - hostnames\r\n  - IP addresses\r\n  - content-type headers\r\n  - email addresses\r\n\r\nIt's kinda kludgy; corrections and suggestions welcome.","install_details":"Drop it into $VIM\/vim61\/syntax.\r\n\r\nTo highlight a file:\r\n:set ft=headers\r\n:syn on","5":"Drop it into $VIM\/vim61\/syntax.\r\n\r\nTo highlight a file:\r\n:set ft=headers\r\n:syn on","first_name":"sim","6":"sim","last_name":"b","7":"b","releases":[{"0":"658","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"headers.vim","4":"headers.vim","src_id":"2017","5":"2017","creation_date":"1053987453","6":"1053987453"}]},"657":{"script_id":"657","0":"657","script_name":"epperl.vim","1":"epperl.vim","script_type":"syntax","2":"syntax","summary":"Syntax highlighting for EP-PERL files","3":"Syntax highlighting for EP-PERL files","description":"Allows syntax highlighting for EP-PERL scripts.\r\nSupports the <EP-PERL>, <EP-IF> and <EP-COMMENT> tags.\r\nsupport for the other tags might be enabled in later versions.","4":"Allows syntax highlighting for EP-PERL scripts.\r\nSupports the <EP-PERL>, <EP-IF> and <EP-COMMENT> tags.\r\nsupport for the other tags might be enabled in later versions.","install_details":"just copy to your syntax library, and add the following in your ~\/.vimrc file:\r\naugroup filetypedetect\r\nautocmd! BufNewFile,BufRead *.ep,*.nep setf epperl\r\naugroup END\r\n","5":"just copy to your syntax library, and add the following in your ~\/.vimrc file:\r\naugroup filetypedetect\r\nautocmd! BufNewFile,BufRead *.ep,*.nep setf epperl\r\naugroup END\r\n","first_name":"Avshalom","6":"Avshalom","last_name":"Ish-Lev","7":"Ish-Lev","releases":[{"0":"657","vim_version":"6.0","1":"6.0","script_version":"1.2","2":"1.2","version_comment":"* added support for highlighting perl vars inside the HTML section.\r\n* fixed highlighting of any text (instead of the perl greyish color, it was blue)","3":"* added support for highlighting perl vars inside the HTML section.\r\n* fixed highlighting of any text (instead of the perl greyish color, it was blue)","package":"epperl.vim","4":"epperl.vim","src_id":"2023","5":"2023","creation_date":"1054097857","6":"1054097857"},{"0":"657","vim_version":"6.0","1":"6.0","script_version":"v1.1","2":"v1.1","version_comment":"Initial upload","3":"Initial upload","package":"epperl.vim","4":"epperl.vim","src_id":"2015","5":"2015","creation_date":"1053824846","6":"1053824846"}]},"656":{"script_id":"656","0":"656","script_name":"esperanto","1":"esperanto","script_type":"utility","2":"utility","summary":"Keyboard for Esperanto \/ Klavaro por Esperanto","3":"Keyboard for Esperanto \/ Klavaro por Esperanto","description":"Simpla klavaro por la internacia lingvo Esperanto\r\n\r\n* Klavaro, post komuto al Unikodo, por Esperanto lau: cx gx hx jx sx auh\/euh\r\n* Krome, ordono por traduki el ^c ^g ^h ^j ^s ~u per: :TradukuIA5","4":"Simpla klavaro por la internacia lingvo Esperanto\r\n\r\n* Klavaro, post komuto al Unikodo, por Esperanto lau: cx gx hx jx sx auh\/euh\r\n* Krome, ordono por traduki el ^c ^g ^h ^j ^s ~u per: :TradukuIA5","install_details":"Metu la du dosierojn en vian \"keymap\" ujon, ekzemple C:\\Program Files\\vim\\vim61\\keymap.  Lanchu Vim, kaj elektu la klavaron, ekzemple per redakt->klavar->esperanto.","5":"Metu la du dosierojn en vian \"keymap\" ujon, ekzemple C:\\Program Files\\vim\\vim61\\keymap.  Lanchu Vim, kaj elektu la klavaron, ekzemple per redakt->klavar->esperanto.","first_name":"Aaron","6":"Aaron","last_name":"Irvine","7":"Irvine","releases":[{"0":"656","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"esperanto.tar.gz","4":"esperanto.tar.gz","src_id":"2014","5":"2014","creation_date":"1053679792","6":"1053679792"}]},"655":{"script_id":"655","0":"655","script_name":"proc.vim","1":"proc.vim","script_type":"syntax","2":"syntax","summary":"Oracle Pro*C\/C++ syntax file","3":"Oracle Pro*C\/C++ syntax file","description":"7-May-2004 Note:  I have recently learned that this syntax is redundant.  You can get the same functionality with esqlc.vim in the standard distribution.\r\n\r\nThis is a start towards a customization of the C++ syntax, for code that uses the Oracle Pro*C\/C++ precompiler code.  Essentially it loads up the C++ syntax file, and then does additional highlighting of text that begins with EXEC SQL.\r\n\r\n","4":"7-May-2004 Note:  I have recently learned that this syntax is redundant.  You can get the same functionality with esqlc.vim in the standard distribution.\r\n\r\nThis is a start towards a customization of the C++ syntax, for code that uses the Oracle Pro*C\/C++ precompiler code.  Essentially it loads up the C++ syntax file, and then does additional highlighting of text that begins with EXEC SQL.\r\n\r\n","install_details":"Drop this file into your $HOME\/.vim\/syntax directory, and then set up the new filetype for *.pc to load proc.vim.  What I did was create the file $HOME\/.vim\/filetype.vim with these contents:\r\n\r\nif exists(\"did_load_filetypes\")\r\n    finish\r\nendif\r\naugroup filetypedetect\r\n    au! BufRead,BufNewFile *.pc     setfiletype proc\r\naugroup END\r\n\r\nYou can execute \":help new-filetype\" for more information.\r\n","5":"Drop this file into your $HOME\/.vim\/syntax directory, and then set up the new filetype for *.pc to load proc.vim.  What I did was create the file $HOME\/.vim\/filetype.vim with these contents:\r\n\r\nif exists(\"did_load_filetypes\")\r\n    finish\r\nendif\r\naugroup filetypedetect\r\n    au! BufRead,BufNewFile *.pc     setfiletype proc\r\naugroup END\r\n\r\nYou can execute \":help new-filetype\" for more information.\r\n","first_name":"Michael","6":"Michael","last_name":"Jarvis","7":"Jarvis","releases":[{"0":"655","vim_version":"6.0","1":"6.0","script_version":"0.01","2":"0.01","version_comment":"Initial upload","3":"Initial upload","package":"proc.vim","4":"proc.vim","src_id":"2011","5":"2011","creation_date":"1053604156","6":"1053604156"}]},"654":{"script_id":"654","0":"654","script_name":"ldif.vim","1":"ldif.vim","script_type":"syntax","2":"syntax","summary":"syntax higlighting for LDIF (LDAP serialization)","3":"syntax higlighting for LDIF (LDAP serialization)","description":"Supports only the basic schemas.\r\nhttp:\/\/www.bithill.net\/software.xhtml.var","4":"Supports only the basic schemas.\r\nhttp:\/\/www.bithill.net\/software.xhtml.var","install_details":"","5":"","first_name":"binary","6":"binary","last_name":"runner","7":"runner","releases":[{"0":"654","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"ldif.vim","4":"ldif.vim","src_id":"2008","5":"2008","creation_date":"1053495892","6":"1053495892"}]},"653":{"script_id":"653","0":"653","script_name":"ldap_schema.vim","1":"ldap_schema.vim","script_type":"syntax","2":"syntax","summary":"syntax higlighting for LDAP schema definition","3":"syntax higlighting for LDAP schema definition","description":"It can be a bit outdate ut still usefull.\r\nhttp:\/\/www.bithill.net\/software.xhtml.var","4":"It can be a bit outdate ut still usefull.\r\nhttp:\/\/www.bithill.net\/software.xhtml.var","install_details":"","5":"","first_name":"binary","6":"binary","last_name":"runner","7":"runner","releases":[{"0":"653","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"ldap_schema.vim","4":"ldap_schema.vim","src_id":"2006","5":"2006","creation_date":"1053495804","6":"1053495804"}]},"652":{"script_id":"652","0":"652","script_name":"stol.vim","1":"stol.vim","script_type":"syntax","2":"syntax","summary":"syntax for STOL (Satellite Test and Operations Language)","3":"syntax for STOL (Satellite Test and Operations Language)","description":"Syntax for STOL (Satellite Test and Operations Language).\r\n\r\nThis currently contains only the base STOL language; i.e., there is no highlighting of EPOCH or other STOL extensions.\r\n","4":"Syntax for STOL (Satellite Test and Operations Language).\r\n\r\nThis currently contains only the base STOL language; i.e., there is no highlighting of EPOCH or other STOL extensions.\r\n","install_details":"Drop this in your \"$VIMRUNTIME\/syntax\" directory.","5":"Drop this in your \"$VIMRUNTIME\/syntax\" directory.","first_name":"Ed","6":"Ed","last_name":"Ralston","7":"Ralston","releases":[{"0":"652","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"stol.vim","4":"stol.vim","src_id":"2004","5":"2004","creation_date":"1053495420","6":"1053495420"}]},"651":{"script_id":"651","0":"651","script_name":"uniq.vim","1":"uniq.vim","script_type":"utility","2":"utility","summary":"Emulations of the 'uniq' utility in Vim script","3":"Emulations of the 'uniq' utility in Vim script","description":"\r\nThis script provides several examples of the Unix \"uniq\" utility emulated entirely with Vim script, found during some brief research through the Vim list archives. Like the original uniq, each requires the selected lines \"uniq-ed\" to already be sorted so that duplicates are adjacent.\r\n\r\nNote that there are generally two approches here. The first uses the getline() function to examine adjacent lines and is used by the first two examples. A second approach is illustrated by the last three examples which use a single global or substitution command to accomplish the same purpose.\r\n\r\nWe share this compilation in hopes that it might be helpful. The actual origins of each section are documented below. Use at your own risk!\r\n\r\n","4":"\r\nThis script provides several examples of the Unix \"uniq\" utility emulated entirely with Vim script, found during some brief research through the Vim list archives. Like the original uniq, each requires the selected lines \"uniq-ed\" to already be sorted so that duplicates are adjacent.\r\n\r\nNote that there are generally two approches here. The first uses the getline() function to examine adjacent lines and is used by the first two examples. A second approach is illustrated by the last three examples which use a single global or substitution command to accomplish the same purpose.\r\n\r\nWe share this compilation in hopes that it might be helpful. The actual origins of each section are documented below. Use at your own risk!\r\n\r\n","install_details":"\r\nPlease read the code to understand each example's usage. Drop into your plugin folders to have the various commands and functions available.\r\n\r\n","5":"\r\nPlease read the code to understand each example's usage. Drop into your plugin folders to have the various commands and functions available.\r\n\r\n","first_name":"Steve","6":"Steve","last_name":"Hall","7":"Hall","releases":[{"0":"651","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"uniq.vim","4":"uniq.vim","src_id":"2002","5":"2002","creation_date":"1053429433","6":"1053429433"}]},"650":{"script_id":"650","0":"650","script_name":"vectorscript.vim","1":"vectorscript.vim","script_type":"syntax","2":"syntax","summary":"Syntax file for VectorScript","3":"Syntax file for VectorScript","description":"This is a syntax file for the VectorScript\/MiniCad\/Minipascal language.  I developed it specifically for VectorWorks 10.  The syntax file does seem to work for minicad 6.0 I have not tried it in anything below that but I'm sure it will work.","4":"This is a syntax file for the VectorScript\/MiniCad\/Minipascal language.  I developed it specifically for VectorWorks 10.  The syntax file does seem to work for minicad 6.0 I have not tried it in anything below that but I'm sure it will work.","install_details":"Place this file in your \/usr\/syntax folder.  Should be placed in all vim packages in the syntax folder.","5":"Place this file in your \/usr\/syntax folder.  Should be placed in all vim packages in the syntax folder.","first_name":"Dave","6":"Dave","last_name":"Fortin","7":"Fortin","releases":[{"0":"650","vim_version":"6.0","1":"6.0","script_version":"6.1","2":"6.1","version_comment":"Initial upload","3":"Initial upload","package":"vectorscript.vim","4":"vectorscript.vim","src_id":"2001","5":"2001","creation_date":"1053418638","6":"1053418638"}]},"649":{"script_id":"649","0":"649","script_name":"chordpro.vim","1":"chordpro.vim","script_type":"syntax","2":"syntax","summary":"Syntax file for ChordPro files","3":"Syntax file for ChordPro files","description":"Note: This syntax is included in the official VIM distribution since v. 7.0\r\n\r\nchordpro.vim is a syntax file for files in the ChordPro format, a format for writing song lyrics with guitar chords.\r\n\r\nThe format was originally defined by Martin Leclerc and Mario Dorion for use with their chord utility, a program for creating nice looking lyrics\/chords in PostScript. The format has become the most popular method for exchanging chords on the Internet.\r\n\r\nChordPro files typically has the extensions .chopro or .pro.","4":"Note: This syntax is included in the official VIM distribution since v. 7.0\r\n\r\nchordpro.vim is a syntax file for files in the ChordPro format, a format for writing song lyrics with guitar chords.\r\n\r\nThe format was originally defined by Martin Leclerc and Mario Dorion for use with their chord utility, a program for creating nice looking lyrics\/chords in PostScript. The format has become the most popular method for exchanging chords on the Internet.\r\n\r\nChordPro files typically has the extensions .chopro or .pro.","install_details":"Consult your local VIM manual","5":"Consult your local VIM manual","first_name":"Niels Bo","6":"Niels Bo","last_name":"Andersen","7":"Andersen","releases":[{"0":"649","vim_version":"5.7","1":"5.7","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"chordpro.vim","4":"chordpro.vim","src_id":"2000","5":"2000","creation_date":"1053408338","6":"1053408338"}]},"648":{"script_id":"648","0":"648","script_name":"fte.vim","1":"fte.vim","script_type":"utility","2":"utility","summary":"VIM6.0+ Global plugin to expand and load templates (separate cmds). \u00c2\u00abexpression\u00c2\u00bb","3":"VIM6.0+ Global plugin to expand and load templates (separate cmds). \u00c2\u00abexpression\u00c2\u00bb","description":"This is similar in concept to Gergely Kontra's mu-template (VIMSCRIPT#222), I referenced Luc Hermitte's version mostly, fyi. Save that the loading and expanding are two SEPERATE functions. This is deliberate so that you can load how you like (or even expand how you like) Note also that it is a 3 stage process (load, modify, expand) to expand a template from start to finish. This is also deliberate please see the comments at start of the script file and the included vim style help file.\r\n\r\nNote: Bits and pieces and ideas and sniplets from templatefile.vim 1.5 and mu-template.vim 0.11, many thanks to the authors of those two scripts.\r\n\r\nThe major reasons to use this template method vs others (or in addition to others) is that you can load the template where and when and how you want, and you have FULL editing ability when editing the template. You can also use this as a sort of API assistant*(seebelow)\r\n\r\n\r\nIn short you can load a template with:\r\n:FLT ~\/codefrags\/memset.cpp\r\n\r\nmake your changes and then (with your cursor in the template)\r\n:FTE\r\n\r\nThis can be used as a sort of API assistant (when the template files have copious comments), or as a more traditional template expander.\r\n\r\nTemplate files can have comments (lines starting with FTE:), checkboxes and raido button banks. (see inclueded help file for more details).\r\n\r\nYou retain FULL VIM editing abilites (save your file and come back, compleation, etc.) while editing your templates (step#2).\r\n\r\nCurrently you can toggle a checkbox or radiobutton via <leader>f4 and expand the template via <leader>f3. Unfortunatly there is next to no grace in these mappings nor proper  cmds (yet) for toggle prompt line (<leader>f4). Also todo is <plug> stuffs.\r\n\r\nThis is a work in progress that I've run out of time with currently. It works (and works well, if a touch quirky in places) and no known bugs, though with unpatched 6.1 I had a (very) weird undo bug but that has disapeared with 6.1.200. Far as I know it was a internal VIM critter, now fixed. Gimmie feedback to encourage support\/updates for this ;) .. It currently works well enough for my uses.\r\n\r\nAlso included in zip is a codefragments menu (codefragments_menu.vim) I hacked out of Geoff Reedy's colormenu.vim. It is a method to load templates (and can be used completely separate from FTE if you so choose.).\r\n\r\n\r\nZip file made with winzip if it is of any relivance.\r\n\r\n*I define an api assistant as a dialog box that helps you fill in params for a complex (or annoying) functions (win32 messagebox for instance). With FTE it is text based but you have fake\/functional checkboxes and radio buttons.\r\n","4":"This is similar in concept to Gergely Kontra's mu-template (VIMSCRIPT#222), I referenced Luc Hermitte's version mostly, fyi. Save that the loading and expanding are two SEPERATE functions. This is deliberate so that you can load how you like (or even expand how you like) Note also that it is a 3 stage process (load, modify, expand) to expand a template from start to finish. This is also deliberate please see the comments at start of the script file and the included vim style help file.\r\n\r\nNote: Bits and pieces and ideas and sniplets from templatefile.vim 1.5 and mu-template.vim 0.11, many thanks to the authors of those two scripts.\r\n\r\nThe major reasons to use this template method vs others (or in addition to others) is that you can load the template where and when and how you want, and you have FULL editing ability when editing the template. You can also use this as a sort of API assistant*(seebelow)\r\n\r\n\r\nIn short you can load a template with:\r\n:FLT ~\/codefrags\/memset.cpp\r\n\r\nmake your changes and then (with your cursor in the template)\r\n:FTE\r\n\r\nThis can be used as a sort of API assistant (when the template files have copious comments), or as a more traditional template expander.\r\n\r\nTemplate files can have comments (lines starting with FTE:), checkboxes and raido button banks. (see inclueded help file for more details).\r\n\r\nYou retain FULL VIM editing abilites (save your file and come back, compleation, etc.) while editing your templates (step#2).\r\n\r\nCurrently you can toggle a checkbox or radiobutton via <leader>f4 and expand the template via <leader>f3. Unfortunatly there is next to no grace in these mappings nor proper  cmds (yet) for toggle prompt line (<leader>f4). Also todo is <plug> stuffs.\r\n\r\nThis is a work in progress that I've run out of time with currently. It works (and works well, if a touch quirky in places) and no known bugs, though with unpatched 6.1 I had a (very) weird undo bug but that has disapeared with 6.1.200. Far as I know it was a internal VIM critter, now fixed. Gimmie feedback to encourage support\/updates for this ;) .. It currently works well enough for my uses.\r\n\r\nAlso included in zip is a codefragments menu (codefragments_menu.vim) I hacked out of Geoff Reedy's colormenu.vim. It is a method to load templates (and can be used completely separate from FTE if you so choose.).\r\n\r\n\r\nZip file made with winzip if it is of any relivance.\r\n\r\n*I define an api assistant as a dialog box that helps you fill in params for a complex (or annoying) functions (win32 messagebox for instance). With FTE it is text based but you have fake\/functional checkboxes and radio buttons.\r\n","install_details":"place:\r\nfte.vim in plugins\/\r\nfte.txt in doc\/\r\n(optional!) codefragments_menu.vim in plugins\/","5":"place:\r\nfte.vim in plugins\/\r\nfte.txt in doc\/\r\n(optional!) codefragments_menu.vim in plugins\/","first_name":"Robert","6":"Robert","last_name":"KellyIV","7":"KellyIV","releases":[{"0":"648","vim_version":"6.0","1":"6.0","script_version":"0.42","2":"0.42","version_comment":"Initial upload","3":"Initial upload","package":"fte.zip","4":"fte.zip","src_id":"1999","5":"1999","creation_date":"1053298200","6":"1053298200"}]},"647":{"script_id":"647","0":"647","script_name":"DOS Commands","1":"DOS Commands","script_type":"utility","2":"utility","summary":"Get help for dos commands within VIM","3":"Get help for dos commands within VIM","description":"This will add all a online help for DOS commands (created from windows XP) to vim help system so you can find help for any dos commands by doing :help command\r\n\r\nExample\r\n:help FOR \r\n\r\nNote: all the dos commands are defined as uppercase, so use all uppercase when using help command.","4":"This will add all a online help for DOS commands (created from windows XP) to vim help system so you can find help for any dos commands by doing :help command\r\n\r\nExample\r\n:help FOR \r\n\r\nNote: all the dos commands are defined as uppercase, so use all uppercase when using help command.","install_details":"Just copy it to your vimfiles\/doc folder and do :helptags command\r\nsee \r\n:help :helptags \r\nor\r\n:help add-local-help \r\nfor more info","5":"Just copy it to your vimfiles\/doc folder and do :helptags command\r\nsee \r\n:help :helptags \r\nor\r\n:help add-local-help \r\nfor more info","first_name":"Rajesh","6":"Rajesh","last_name":"Kallingal","7":"Kallingal","releases":[{"0":"647","vim_version":"6.0","1":"6.0","script_version":"1.1","2":"1.1","version_comment":"BUGFIX: corrected the tag definitions (thanks to Hans-G\u00c3\u00bcnter)","3":"BUGFIX: corrected the tag definitions (thanks to Hans-G\u00c3\u00bcnter)","package":"doshelp.txt","4":"doshelp.txt","src_id":"2003","5":"2003","creation_date":"1053495145","6":"1053495145"},{"0":"647","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"doshelp.txt","4":"doshelp.txt","src_id":"1992","5":"1992","creation_date":"1053069344","6":"1053069344"}]},"646":{"script_id":"646","0":"646","script_name":"colorize","1":"colorize","script_type":"utility","2":"utility","summary":"Create colorized HTML from source code","3":"Create colorized HTML from source code","description":"A script-wrapper around modified 2html.vim.\r\n\r\nFeatures:\r\n\r\n- result caching\r\n- without surrounding html tags (html, body etc.)\r\n- striping leading\/trailing whitespace\r\n- specify language (instead of auto-detection by file extension)","4":"A script-wrapper around modified 2html.vim.\r\n\r\nFeatures:\r\n\r\n- result caching\r\n- without surrounding html tags (html, body etc.)\r\n- striping leading\/trailing whitespace\r\n- specify language (instead of auto-detection by file extension)","install_details":"requires: Ruby","5":"requires: Ruby","first_name":"Michael","6":"Michael","last_name":"Neumann","7":"Neumann","releases":[{"0":"646","vim_version":"6.0","1":"6.0","script_version":"5","2":"5","version_comment":"* added terminal option (e.g. use --terminal=xterm-color for coloring output from a CGI script)\r\n* strip-ws now strips leading _and_ trailing empty lines\r\n* beautified usage output\r\n\r\n* allow reading data from stdin","3":"* added terminal option (e.g. use --terminal=xterm-color for coloring output from a CGI script)\r\n* strip-ws now strips leading _and_ trailing empty lines\r\n* beautified usage output\r\n\r\n* allow reading data from stdin","package":"colorize","4":"colorize","src_id":"2507","5":"2507","creation_date":"1069481066","6":"1069481066"},{"0":"646","vim_version":"6.0","1":"6.0","script_version":"3","2":"3","version_comment":"result caching support","3":"result caching support","package":"colorize","4":"colorize","src_id":"1996","5":"1996","creation_date":"1053138089","6":"1053138089"},{"0":"646","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"colorize","4":"colorize","src_id":"1991","5":"1991","creation_date":"1053063210","6":"1053063210"}]},"645":{"script_id":"645","0":"645","script_name":"greyblue.vim","1":"greyblue.vim","script_type":"color scheme","2":"color scheme","summary":"soft grey and blue color scheme","3":"soft grey and blue color scheme","description":"soft grey and blue color scheme","4":"soft grey and blue color scheme","install_details":"cp to ~\/.vim\/colors\/\r\n\r\ninside vim:\r\n:color greyblue.vim","5":"cp to ~\/.vim\/colors\/\r\n\r\ninside vim:\r\n:color greyblue.vim","first_name":"eric","6":"eric","last_name":"johnson","7":"johnson","releases":[{"0":"645","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"greyblue.vim","4":"greyblue.vim","src_id":"1990","5":"1990","creation_date":"1053042866","6":"1053042866"}]},"644":{"script_id":"644","0":"644","script_name":"Color Scheme Test","1":"Color Scheme Test","script_type":"syntax","2":"syntax","summary":"Use this syntax file to display colors in color scheme files","3":"Use this syntax file to display colors in color scheme files","description":"Use this syntax file to test color schemes: edit your color scheme file, and to see what each color assignment does, set the color scheme to your color scheme then type the command ':setf cst'. As you continue to make changes, save your changes, and switch to another color scheme and back to your own to see changes. Each of the hilite group names will be colored in the color style your file defines. e.g. if your color scheme defines:\r\n\r\nhi operator\t\tguifg=DarkGreen\t\tgui=bold\r\n\r\nthen the word 'operator' will appear in bold dark green.\r\n\r\nPlace cst.vim in your syntax directory and go forth and create color :-)\r\n\r\nTom Kimpton.\r\n\r\n","4":"Use this syntax file to test color schemes: edit your color scheme file, and to see what each color assignment does, set the color scheme to your color scheme then type the command ':setf cst'. As you continue to make changes, save your changes, and switch to another color scheme and back to your own to see changes. Each of the hilite group names will be colored in the color style your file defines. e.g. if your color scheme defines:\r\n\r\nhi operator\t\tguifg=DarkGreen\t\tgui=bold\r\n\r\nthen the word 'operator' will appear in bold dark green.\r\n\r\nPlace cst.vim in your syntax directory and go forth and create color :-)\r\n\r\nTom Kimpton.\r\n\r\n","install_details":"place cst.vim in your syntax directory","5":"place cst.vim in your syntax directory","first_name":"Thomas","6":"Thomas","last_name":"Kimpton","7":"Kimpton","releases":[{"0":"644","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"cst.tar.gz","4":"cst.tar.gz","src_id":"1988","5":"1988","creation_date":"1052930876","6":"1052930876"}]},"643":{"script_id":"643","0":"643","script_name":"WML Wireless Markup Language syntax","1":"WML Wireless Markup Language syntax","script_type":"syntax","2":"syntax","summary":"The title says it all","3":"The title says it all","description":"I found no syntax script for wml so I made a simple one.\r\n\r\nIt was made for WML 1.1. Other WML versions weren't taken into account, but I believe this file is very easy to change.","4":"I found no syntax script for wml so I made a simple one.\r\n\r\nIt was made for WML 1.1. Other WML versions weren't taken into account, but I believe this file is very easy to change.","install_details":"Go to the vim syntax directory.\r\nBackup a wml.vim you might have, probably it stands for Website META Language, then put this one. Tada!\r\n\r\nBut to get things nice, edit menu.vim in vim's path, and replace:\r\nWebsite\\ MetaLanguage\r\nwith:\r\nWireless\\ Markup\\ Language\r\nOr simply, in a command:\r\n:%s\/Website\\\\ MetaLanguage\/Wireless\\\\ Markup\\\\ Language\/","5":"Go to the vim syntax directory.\r\nBackup a wml.vim you might have, probably it stands for Website META Language, then put this one. Tada!\r\n\r\nBut to get things nice, edit menu.vim in vim's path, and replace:\r\nWebsite\\ MetaLanguage\r\nwith:\r\nWireless\\ Markup\\ Language\r\nOr simply, in a command:\r\n:%s\/Website\\\\ MetaLanguage\/Wireless\\\\ Markup\\\\ Language\/","first_name":"Paulo","6":"Paulo","last_name":"Madeira","7":"Madeira","releases":[{"0":"643","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"wml.vim","4":"wml.vim","src_id":"1986","5":"1986","creation_date":"1052834618","6":"1052834618"}]},"642":{"script_id":"642","0":"642","script_name":"GetLatestVimScripts","1":"GetLatestVimScripts","script_type":"utility","2":"utility","summary":"Keep your plugins up-to-date! (semi-automatic retrieval)","3":"Keep your plugins up-to-date! (semi-automatic retrieval)","description":"GetLatestVimScripts is a plugin that automates retrieval of the latest versions of the scripts that you yourself use!\r\n\r\n   * automatic up-to-date plugins\r\n   * automatic installation for cooperating plugins\r\n   * automatic constructions of GetLatestVimScripts.dat for cooperating plugins\r\n\r\n\r\n-----\r\nUsage:\r\n-----\r\n\r\n    :GetLatestVimScripts\r\n-or-\r\n    :GLVS\r\n\r\nDownloaded files are placed in the .vim\/GetLatest directory (vimfiles\\GetLatest).  Those scripts that have an :AutoInstall: in their GetLatestVimScripts comment will be (you guessed it!) automatically installed.\r\n\r\nGetLatestVimScripts depends on a file called GetLatest\/GetLatestVimScripts.dat.  This file tells GetLatestVimScripts what plugins you're interested in and want to keep up-to-date.  Each line in the file has the form:\r\n\r\n    ScriptID SrcID ScriptName\r\n\r\nwhere\r\n\r\n    ScriptID  : you'll see it on the top of your browser in its \"Location:\" box whenever you click on the script at http:\/\/vim.sf.net\/ .\r\n    SrcID     : start it off with a \"1\"; :GetLatestVimScripts will download the file and keep this entry updated automatically\r\n    ScriptName: the name or title of the script (may have spaces, etc)\r\n\r\nIn the distribution is <GetLatestVimScripts.dist>; its an example of a <GetLatestVimScripts.dat> file.  In fact, you\r\ncan rename it to <GetLatestVimScripts.dat> and use it if you wish; it contains lines telling GetLatestVimScripts\r\nto automate retrieval of <Align.vim>, <Mines.vim>, etc.  Please feel free to edit the file as you wish.\r\n\r\nGetLatestVimScripts examines the plugins you currently have for lines that look like: (Align.vim's is shown)\r\n\r\n    \" GetLatestVimScripts: 294 1 :AutoInstall: Align.vim\r\n\r\nPlugins that have such lines enable GetLatestVimScripts to automatically build the GetLatestVimScripts.dat file\r\nfor you.  The :AutoInstall: in the comment tells GetLatestVimScripts that the plugin is safe to automatically install, too.\r\n\r\n------------\r\nHow It Works\r\n------------\r\n\r\nVim.sf.net has a separate SrcID for every script that is uploaded.  With Netscape, Mozilla, and Internet-Explorer, when you move the cursor on top of the script you'd like to download, you'll see a line resembling ...src_id=###.  As new scripts and newly uploaded scripts are placed on vim.sf.net, the src_id is incremented.  Hence the newer ones will have greater SrcIDs, so GetLatestVimScripts compares the SrcID in your <GetLatestVimScripts.dat> file with what vim.sf.net has; if there's a newer one, GetLatestVimScripts will \"wget\" it.\r\n\r\nThe GetLatestVimScripts script will modify the GetLatestVimScripts.dat file whenever it downloads a new source file to reflect the latest SrcID, too.\r\n\r\n\r\n----------------------------------------\r\nSemi-Automatic Script Dependency Support\r\n----------------------------------------\r\n\r\nGetLatestVimScripts will examine your plugins for comment lines of the form\r\n\r\n    \" GetLatestVimScripts: ScriptID SrcID ScriptName\r\n\r\nSuch lines will be appropriately appended to the GetLatest\/GetLatestVimScripts.dat file (if not already present) whenever :GetLatestVimScripts is invoked.  Thus if your newly downloaded script has such lines in it, thereby indicating that it depends upon the presence of specific scripts, GetLatestVimScripts will keep such dependent scripts up to date, too.\r\n\r\n\r\n--------\r\nRequired\r\n--------\r\n\r\n    wget\r\n\r\nie. you'll need to have wget somewhere on your path for GetLatestVimScripts to work.\r\n\r\n(alpha\/beta version available at http:\/\/www.drchip.org\/astronaut\/vim\/index.html#GETSCRIPT)\r\n","4":"GetLatestVimScripts is a plugin that automates retrieval of the latest versions of the scripts that you yourself use!\r\n\r\n   * automatic up-to-date plugins\r\n   * automatic installation for cooperating plugins\r\n   * automatic constructions of GetLatestVimScripts.dat for cooperating plugins\r\n\r\n\r\n-----\r\nUsage:\r\n-----\r\n\r\n    :GetLatestVimScripts\r\n-or-\r\n    :GLVS\r\n\r\nDownloaded files are placed in the .vim\/GetLatest directory (vimfiles\\GetLatest).  Those scripts that have an :AutoInstall: in their GetLatestVimScripts comment will be (you guessed it!) automatically installed.\r\n\r\nGetLatestVimScripts depends on a file called GetLatest\/GetLatestVimScripts.dat.  This file tells GetLatestVimScripts what plugins you're interested in and want to keep up-to-date.  Each line in the file has the form:\r\n\r\n    ScriptID SrcID ScriptName\r\n\r\nwhere\r\n\r\n    ScriptID  : you'll see it on the top of your browser in its \"Location:\" box whenever you click on the script at http:\/\/vim.sf.net\/ .\r\n    SrcID     : start it off with a \"1\"; :GetLatestVimScripts will download the file and keep this entry updated automatically\r\n    ScriptName: the name or title of the script (may have spaces, etc)\r\n\r\nIn the distribution is <GetLatestVimScripts.dist>; its an example of a <GetLatestVimScripts.dat> file.  In fact, you\r\ncan rename it to <GetLatestVimScripts.dat> and use it if you wish; it contains lines telling GetLatestVimScripts\r\nto automate retrieval of <Align.vim>, <Mines.vim>, etc.  Please feel free to edit the file as you wish.\r\n\r\nGetLatestVimScripts examines the plugins you currently have for lines that look like: (Align.vim's is shown)\r\n\r\n    \" GetLatestVimScripts: 294 1 :AutoInstall: Align.vim\r\n\r\nPlugins that have such lines enable GetLatestVimScripts to automatically build the GetLatestVimScripts.dat file\r\nfor you.  The :AutoInstall: in the comment tells GetLatestVimScripts that the plugin is safe to automatically install, too.\r\n\r\n------------\r\nHow It Works\r\n------------\r\n\r\nVim.sf.net has a separate SrcID for every script that is uploaded.  With Netscape, Mozilla, and Internet-Explorer, when you move the cursor on top of the script you'd like to download, you'll see a line resembling ...src_id=###.  As new scripts and newly uploaded scripts are placed on vim.sf.net, the src_id is incremented.  Hence the newer ones will have greater SrcIDs, so GetLatestVimScripts compares the SrcID in your <GetLatestVimScripts.dat> file with what vim.sf.net has; if there's a newer one, GetLatestVimScripts will \"wget\" it.\r\n\r\nThe GetLatestVimScripts script will modify the GetLatestVimScripts.dat file whenever it downloads a new source file to reflect the latest SrcID, too.\r\n\r\n\r\n----------------------------------------\r\nSemi-Automatic Script Dependency Support\r\n----------------------------------------\r\n\r\nGetLatestVimScripts will examine your plugins for comment lines of the form\r\n\r\n    \" GetLatestVimScripts: ScriptID SrcID ScriptName\r\n\r\nSuch lines will be appropriately appended to the GetLatest\/GetLatestVimScripts.dat file (if not already present) whenever :GetLatestVimScripts is invoked.  Thus if your newly downloaded script has such lines in it, thereby indicating that it depends upon the presence of specific scripts, GetLatestVimScripts will keep such dependent scripts up to date, too.\r\n\r\n\r\n--------\r\nRequired\r\n--------\r\n\r\n    wget\r\n\r\nie. you'll need to have wget somewhere on your path for GetLatestVimScripts to work.\r\n\r\n(alpha\/beta version available at http:\/\/www.drchip.org\/astronaut\/vim\/index.html#GETSCRIPT)\r\n","install_details":"\t(you will need an up-to-date install of vimball, vimscript#1502, although vim 7.1a or later's vimball is probably ok)\r\n\r\n1. vim getscript.vba.gz\r\n   :so %\r\n   :q\r\n2. a) Unix:\r\n      cd ~\/.vim\/GetLatest\r\n   b) Windows:\r\n      cd ..wherever..\\vimfiles\\GetLatest\r\n3. mv GetLatestVimScripts.dist GetLatestVimScripts.dat\r\n4. Edit GetLatestVimScripts.dat to install the plugins in which you're interested.  To the extent that plugin authors have included lines such as\r\n\r\n     \" GetLatestVimScripts: [scriptid] 1 [:AutoInstall:] PluginName.vim\r\n\r\n   in their plugins, GetLatestVimScripts will be able to construct the GetLatestVimScripts.dat file itself.\r\n","5":"\t(you will need an up-to-date install of vimball, vimscript#1502, although vim 7.1a or later's vimball is probably ok)\r\n\r\n1. vim getscript.vba.gz\r\n   :so %\r\n   :q\r\n2. a) Unix:\r\n      cd ~\/.vim\/GetLatest\r\n   b) Windows:\r\n      cd ..wherever..\\vimfiles\\GetLatest\r\n3. mv GetLatestVimScripts.dist GetLatestVimScripts.dat\r\n4. Edit GetLatestVimScripts.dat to install the plugins in which you're interested.  To the extent that plugin authors have included lines such as\r\n\r\n     \" GetLatestVimScripts: [scriptid] 1 [:AutoInstall:] PluginName.vim\r\n\r\n   in their plugins, GetLatestVimScripts will be able to construct the GetLatestVimScripts.dat file itself.\r\n","first_name":"Charles","6":"Charles","last_name":"Campbell","7":"Campbell","releases":[{"0":"642","vim_version":"7.3","1":"7.3","script_version":"33","2":"33","version_comment":"*.xz compression supported\r\nBug fixes: acd option bypass, fnameescape used instead of escape(), hls problem fixed\r\n","3":"*.xz compression supported\r\nBug fixes: acd option bypass, fnameescape used instead of escape(), hls problem fixed\r\n","package":"getscript.vba.gz","4":"getscript.vba.gz","src_id":"15781","5":"15781","creation_date":"1306873290","6":"1306873290"},{"0":"642","vim_version":"7.0","1":"7.0","script_version":"29","2":"29","version_comment":"Another bugfix.","3":"Another bugfix.","package":"getscript.vba.gz","4":"getscript.vba.gz","src_id":"8136","5":"8136","creation_date":"1199778504","6":"1199778504"},{"0":"642","vim_version":"7.0","1":"7.0","script_version":"28","2":"28","version_comment":"Getscript has improved shell quote handling and avoids pop-up windows under WinXP more often\r\n","3":"Getscript has improved shell quote handling and avoids pop-up windows under WinXP more often\r\n","package":"getscript.vba.gz","4":"getscript.vba.gz","src_id":"8132","5":"8132","creation_date":"1199690761","6":"1199690761"},{"0":"642","vim_version":"7.0","1":"7.0","script_version":"25","2":"25","version_comment":"removed save&restore of the fo option during script loading\r\nignores comments (#...) in GetLatestVimScripts.dat file\r\nsupports vimballs (*.vba, *.vba.gz)","3":"removed save&restore of the fo option during script loading\r\nignores comments (#...) in GetLatestVimScripts.dat file\r\nsupports vimballs (*.vba, *.vba.gz)","package":"getscript.vba.gz","4":"getscript.vba.gz","src_id":"7080","5":"7080","creation_date":"1178622320","6":"1178622320"},{"0":"642","vim_version":"7.0","1":"7.0","script_version":"23","2":"23","version_comment":"Autoinstall handles vimballs and ignores #... as comments","3":"Autoinstall handles vimballs and ignores #... as comments","package":"getscript.vba.gz","4":"getscript.vba.gz","src_id":"6945","5":"6945","creation_date":"1175680264","6":"1175680264"},{"0":"642","vim_version":"7.0","1":"7.0","script_version":"22","2":"22","version_comment":"* Now takes advantage of autoloading.\r\n* Supports automatic use of curl if wget is not available.\r\n","3":"* Now takes advantage of autoloading.\r\n* Supports automatic use of curl if wget is not available.\r\n","package":"getscript.vba.gz","4":"getscript.vba.gz","src_id":"6277","5":"6277","creation_date":"1160744070","6":"1160744070"},{"0":"642","vim_version":"6.0","1":"6.0","script_version":"20","2":"20","version_comment":"bugfix -- unzip needed the -o flag to overwrite\r\n","3":"bugfix -- unzip needed the -o flag to overwrite\r\n","package":"GetLatestVimScripts.tar.gz","4":"GetLatestVimScripts.tar.gz","src_id":"5228","5":"5228","creation_date":"1140008507","6":"1140008507"},{"0":"642","vim_version":"6.0","1":"6.0","script_version":"18","2":"18","version_comment":"Bugfix release: improvement to automatic downloading database construction; nowrapscan no longer throws an error; with bash, mv instead of ren is used; and downloading problems are handled better.\r\ng:GetLatestVimScripts_autoinstall (default=1) can be used to prevent any :AutoInstall:s.\r\n","3":"Bugfix release: improvement to automatic downloading database construction; nowrapscan no longer throws an error; with bash, mv instead of ren is used; and downloading problems are handled better.\r\ng:GetLatestVimScripts_autoinstall (default=1) can be used to prevent any :AutoInstall:s.\r\n","package":"GetLatestVimScripts.tar.gz","4":"GetLatestVimScripts.tar.gz","src_id":"4665","5":"4665","creation_date":"1129015834","6":"1129015834"},{"0":"642","vim_version":"6.0","1":"6.0","script_version":"16","2":"16","version_comment":":GLVS command made available if not already present\r\nMade execution of bunzip2\/gunzip\/tar\/zip silent.\r\nbugfix: With :AutoInstall: use of helptags.  Fixed!\r\n","3":":GLVS command made available if not already present\r\nMade execution of bunzip2\/gunzip\/tar\/zip silent.\r\nbugfix: With :AutoInstall: use of helptags.  Fixed!\r\n","package":"GetLatestVimScripts.tar.bz2","4":"GetLatestVimScripts.tar.bz2","src_id":"3382","5":"3382","creation_date":"1093419665","6":"1093419665"},{"0":"642","vim_version":"6.0","1":"6.0","script_version":"11","2":"11","version_comment":"The newest GetLatestVimScripts is a plugin!  Use :GetLatestVimScripts to get the latest versions of the scripts you're interested in.  Scriptnames and ids are now in a GetLatest\/GetLatestVimScripts.dat datafile.  GetLatestVimScripts also examines cooperating plugins for dependencies, helps build the datafile, and keeps them up-to-date too!\r\n","3":"The newest GetLatestVimScripts is a plugin!  Use :GetLatestVimScripts to get the latest versions of the scripts you're interested in.  Scriptnames and ids are now in a GetLatest\/GetLatestVimScripts.dat datafile.  GetLatestVimScripts also examines cooperating plugins for dependencies, helps build the datafile, and keeps them up-to-date too!\r\n","package":"GetLatestVimScripts.tar.bz2","4":"GetLatestVimScripts.tar.bz2","src_id":"3359","5":"3359","creation_date":"1093005850","6":"1093005850"}]},"641":{"script_id":"641","0":"641","script_name":"tcsoft.vim","1":"tcsoft.vim","script_type":"color scheme","2":"color scheme","summary":"nice light color scheme","3":"nice light color scheme","description":"My  approved coding-colorscheme :D","4":"My  approved coding-colorscheme :D","install_details":"1. copy the file to ~\/.vim\/colors directory\r\n2. Use the \":colorscheme tcsoft\" command to use the color scheme. \r\n    You can add this command to the .vimrc or .gvimrc file too. \r\n\r\ntip:\r\nif you like to have line-highlighting (vimtip #1279), copy this piece of code into your vimrc:\r\n\r\nautocmd InsertLeave * se nocul\r\nautocmd InsertEnter * se cul ","5":"1. copy the file to ~\/.vim\/colors directory\r\n2. Use the \":colorscheme tcsoft\" command to use the color scheme. \r\n    You can add this command to the .vimrc or .gvimrc file too. \r\n\r\ntip:\r\nif you like to have line-highlighting (vimtip #1279), copy this piece of code into your vimrc:\r\n\r\nautocmd InsertLeave * se nocul\r\nautocmd InsertEnter * se cul ","first_name":"Ingo","6":"Ingo","last_name":"Fabbri","7":"Fabbri","releases":[{"0":"641","vim_version":"7.0","1":"7.0","script_version":"1.1","2":"1.1","version_comment":"added some vim7.0-specific highlighting-stuff","3":"added some vim7.0-specific highlighting-stuff","package":"tcsoft.vim","4":"tcsoft.vim","src_id":"6631","5":"6631","creation_date":"1169208488","6":"1169208488"},{"0":"641","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"tcsoft.vim","4":"tcsoft.vim","src_id":"1984","5":"1984","creation_date":"1052821273","6":"1052821273"}]},"640":{"script_id":"640","0":"640","script_name":"SYN2HTML","1":"SYN2HTML","script_type":"utility","2":"utility","summary":"Syntax to HTML converter (Python)","3":"Syntax to HTML converter (Python)","description":"Yet Another Version of the 2html.vim script found in the $VIMRUNTIME\/syntax directory.\r\n\r\nThis version is written in python, making it far easier to do things like change the format of HTML created by the script (i.e. putting it in <div> tags instead of <html> tags).\r\n\r\nTo use this script, your vim must be compiled with +python.","4":"Yet Another Version of the 2html.vim script found in the $VIMRUNTIME\/syntax directory.\r\n\r\nThis version is written in python, making it far easier to do things like change the format of HTML created by the script (i.e. putting it in <div> tags instead of <html> tags).\r\n\r\nTo use this script, your vim must be compiled with +python.","install_details":"Put the script in:\r\n$HOME\/.vim\/plugin\/syn2html.vim \r\n(or your plugin directory on windows)\r\n\r\nType\r\n:python createHTML()\r\nin the buffer you want rendered to HTML, and a new pane will appear containing the source rendered as HTML. It will be given a .html extension (i.e. foo.c will become foo.c.html).","5":"Put the script in:\r\n$HOME\/.vim\/plugin\/syn2html.vim \r\n(or your plugin directory on windows)\r\n\r\nType\r\n:python createHTML()\r\nin the buffer you want rendered to HTML, and a new pane will appear containing the source rendered as HTML. It will be given a .html extension (i.e. foo.c will become foo.c.html).","first_name":"Stephen","6":"Stephen","last_name":"Thorne","7":"Thorne","releases":[{"0":"640","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"syn2html.vim.gz","4":"syn2html.vim.gz","src_id":"1983","5":"1983","creation_date":"1052798035","6":"1052798035"}]},"639":{"script_id":"639","0":"639","script_name":"gmsh.vim","1":"gmsh.vim","script_type":"syntax","2":"syntax","summary":"Syntax file for GMSH meshing facilities","3":"Syntax file for GMSH meshing facilities","description":"Gmsh (http:\/\/www.geuz.org\/gmsh) is an automatic 3D finite element mesh generator (primarily Delaunay) with build-in CAD and post-processing facilities.This simple script helps vim users in daily work providing color and syntax support.","4":"Gmsh (http:\/\/www.geuz.org\/gmsh) is an automatic 3D finite element mesh generator (primarily Delaunay) with build-in CAD and post-processing facilities.This simple script helps vim users in daily work providing color and syntax support.","install_details":"The GMSH community uses .geo files to store their problems, so adding this lines in filetype.vim will help\r\n\r\n\" GMSH (Meshing Facilities)\r\naugroup filetypedetect\r\nau BufNewFile,BufRead *.geo     setf gmsh\r\naugroup END\r\n\r\nFor other GMSH file add the following comment at the end of the file \r\n\r\n\/\/ vim: set filetype=gmsh :  \/\/\r\n","5":"The GMSH community uses .geo files to store their problems, so adding this lines in filetype.vim will help\r\n\r\n\" GMSH (Meshing Facilities)\r\naugroup filetypedetect\r\nau BufNewFile,BufRead *.geo     setf gmsh\r\naugroup END\r\n\r\nFor other GMSH file add the following comment at the end of the file \r\n\r\n\/\/ vim: set filetype=gmsh :  \/\/\r\n","first_name":"CHAMPANEY","6":"CHAMPANEY","last_name":"Laurent","7":"Laurent","releases":[{"0":"639","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"gmsh.vim","4":"gmsh.vim","src_id":"1982","5":"1982","creation_date":"1052795442","6":"1052795442"}]},"638":{"script_id":"638","0":"638","script_name":"WC.vim","1":"WC.vim","script_type":"utility","2":"utility","summary":"Count number of bytes on current line or in visual block of lines.","3":"Count number of bytes on current line or in visual block of lines.","description":"This script will count the number of bytes on the current line or a selected block of lines.","4":"This script will count the number of bytes on the current line or a selected block of lines.","install_details":"copy WC.vim to ~\/.vim\/plugin","5":"copy WC.vim to ~\/.vim\/plugin","first_name":"Jeff","6":"Jeff","last_name":"Crawford","7":"Crawford","releases":[{"0":"638","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"WC.vim","4":"WC.vim","src_id":"1981","5":"1981","creation_date":"1052599473","6":"1052599473"}]},"637":{"script_id":"637","0":"637","script_name":"COMMENT.vim","1":"COMMENT.vim","script_type":"utility","2":"utility","summary":"Comment out blocks of C\/C++ code using #if 0 #endif block","3":"Comment out blocks of C\/C++ code using #if 0 #endif block","description":"Hi All,\r\n  Here is a script I use quite often when coding\r\nand I want to temporarily comment out a chunk\r\nof C\/C++ source code.\r\n\r\nUsage:\r\nSelect the block of code you want to comment out\r\n(in visual mode) and invoke :call PComment().\r\n\r\nThis inputs\r\n#if 0\r\n<code block>\r\n#endif\r\n\r\nYou can also invoke it without the visual selection\r\nand it comments the current line.\r\n\r\nIt will also remove an #if 0 block as follows:\r\n\r\n#if 0\r\n<code block>\r\n#endif\r\n\r\nusing the above example, place the cursor anywhere\r\non the #if 0 line and invoke the function, voila \r\ncode block is restored and the #if 0 and #endif are gone.\r\n\r\nHeres a more advance example, suppose you have the\r\nfollowing:\r\n\r\n#if 0\r\n<code block>\r\n#else\r\n<code block>\r\n#endif\r\n\r\nif you invoke the command on the #if 0 the #else\r\nit will automatically be converted to #if 0 and the code \r\nblock above will be restored, like so:\r\n\r\n<code block>\r\n#if 0\r\n<code block>\r\n#endif\r\n\r\nAlso works with nested #if 0 #endif blocks:\r\n\r\nSuppose you have a large chunk of code that already\r\nhas some #if 0 blocks.  No problem, select all you want\r\nincluding the nested comment blocks and invoke the function,\r\nwhen you want to remove the comment the proper #endif\r\nis matched and removed.\r\n\r\nExample:\r\n\r\n<code block1>\r\n#if 0\r\n<code block2>\r\n#endif\r\n<code block3>\r\n<code block4>\r\n\r\nSelect all up to code block3 and invoke the function,\r\nwe get:\r\n\r\n#if 0\r\n<code block1>\r\n#if 0\r\n<code block2>\r\n#endif\r\n<code block3>\r\n#endif\r\n<code block4>\r\n\r\nMove to the first #if 0 and invoke the function, voila\r\nyou should be back to square one again.\r\n\r\nHope you all like it.\r\nHave fun.","4":"Hi All,\r\n  Here is a script I use quite often when coding\r\nand I want to temporarily comment out a chunk\r\nof C\/C++ source code.\r\n\r\nUsage:\r\nSelect the block of code you want to comment out\r\n(in visual mode) and invoke :call PComment().\r\n\r\nThis inputs\r\n#if 0\r\n<code block>\r\n#endif\r\n\r\nYou can also invoke it without the visual selection\r\nand it comments the current line.\r\n\r\nIt will also remove an #if 0 block as follows:\r\n\r\n#if 0\r\n<code block>\r\n#endif\r\n\r\nusing the above example, place the cursor anywhere\r\non the #if 0 line and invoke the function, voila \r\ncode block is restored and the #if 0 and #endif are gone.\r\n\r\nHeres a more advance example, suppose you have the\r\nfollowing:\r\n\r\n#if 0\r\n<code block>\r\n#else\r\n<code block>\r\n#endif\r\n\r\nif you invoke the command on the #if 0 the #else\r\nit will automatically be converted to #if 0 and the code \r\nblock above will be restored, like so:\r\n\r\n<code block>\r\n#if 0\r\n<code block>\r\n#endif\r\n\r\nAlso works with nested #if 0 #endif blocks:\r\n\r\nSuppose you have a large chunk of code that already\r\nhas some #if 0 blocks.  No problem, select all you want\r\nincluding the nested comment blocks and invoke the function,\r\nwhen you want to remove the comment the proper #endif\r\nis matched and removed.\r\n\r\nExample:\r\n\r\n<code block1>\r\n#if 0\r\n<code block2>\r\n#endif\r\n<code block3>\r\n<code block4>\r\n\r\nSelect all up to code block3 and invoke the function,\r\nwe get:\r\n\r\n#if 0\r\n<code block1>\r\n#if 0\r\n<code block2>\r\n#endif\r\n<code block3>\r\n#endif\r\n<code block4>\r\n\r\nMove to the first #if 0 and invoke the function, voila\r\nyou should be back to square one again.\r\n\r\nHope you all like it.\r\nHave fun.","install_details":"Copy COMMENT.vim to ~\/.vim\/plugin folder","5":"Copy COMMENT.vim to ~\/.vim\/plugin folder","first_name":"Jeff","6":"Jeff","last_name":"Crawford","7":"Crawford","releases":[{"0":"637","vim_version":"6.0","1":"6.0","script_version":"1.1","2":"1.1","version_comment":"- Pluginized the script (special thanks to Chip Campbell)\r\n- Added a help file\r\n- to install unzip in ~\/.vim and run :helptags ~\/.vim\/doc from vim\r\n- :help COMMENT for usage\r\n- no major changes; mapping is now <M-i> in visual mode.","3":"- Pluginized the script (special thanks to Chip Campbell)\r\n- Added a help file\r\n- to install unzip in ~\/.vim and run :helptags ~\/.vim\/doc from vim\r\n- :help COMMENT for usage\r\n- no major changes; mapping is now <M-i> in visual mode.","package":"COMMENT.zip","4":"COMMENT.zip","src_id":"4674","5":"4674","creation_date":"1129283912","6":"1129283912"},{"0":"637","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"COMMENT.vim","4":"COMMENT.vim","src_id":"1980","5":"1980","creation_date":"1052598862","6":"1052598862"}]},"636":{"script_id":"636","0":"636","script_name":"getdp","1":"getdp","script_type":"syntax","2":"syntax","summary":"Syntax file for GetDP Numerical Environment","3":"Syntax file for GetDP Numerical Environment","description":"GetDP is a Numerical Environment for partial diferential equations, mainly through the Finite Element method. This simple script helps vim users in daily work providing color and syntax support.","4":"GetDP is a Numerical Environment for partial diferential equations, mainly through the Finite Element method. This simple script helps vim users in daily work providing color and syntax support.","install_details":"The GetDP community uses .pro files to store their problems, so adding this lines in filetype.vim will help\n\n\" GetDP (Scientific Environment)\naugroup filetypedetect\nau BufNewFile,BufRead *.pro     setf getdp\naugroup END ","5":"The GetDP community uses .pro files to store their problems, so adding this lines in filetype.vim will help\n\n\" GetDP (Scientific Environment)\naugroup filetypedetect\nau BufNewFile,BufRead *.pro     setf getdp\naugroup END ","first_name":"Patricio","6":"Patricio","last_name":"Toledo","7":"Toledo","releases":[{"0":"636","vim_version":"6.0","1":"6.0","script_version":"0.2","2":"0.2","version_comment":"Better comments, more keywords","3":"Better comments, more keywords","package":"getdp.vim","4":"getdp.vim","src_id":"2729","5":"2729","creation_date":"1076239456","6":"1076239456"},{"0":"636","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"getdp.vim","4":"getdp.vim","src_id":"1978","5":"1978","creation_date":"1052416566","6":"1052416566"}]},"635":{"script_id":"635","0":"635","script_name":"sparc.vim","1":"sparc.vim","script_type":"syntax","2":"syntax","summary":"Syntax file for the Sparc V8 assembly language.","3":"Syntax file for the Sparc V8 assembly language.","description":"Syntax file for the Sparc V8 assembly language.\r\n","4":"Syntax file for the Sparc V8 assembly language.\r\n","install_details":"","5":"","first_name":"Nicolas","6":"Nicolas","last_name":"Herry","7":"Herry","releases":[{"0":"635","vim_version":"6.0","1":"6.0","script_version":"0.2","2":"0.2","version_comment":"Fixed a lot (actually, rewrote the whole thing). I noticed I was missing a lot of instructions in v 0.1, I hope that now they're all here in it.\r\n\r\nI still cannot get the '.' and ',a' sequences highlighted. If you can, please, help !","3":"Fixed a lot (actually, rewrote the whole thing). I noticed I was missing a lot of instructions in v 0.1, I hope that now they're all here in it.\r\n\r\nI still cannot get the '.' and ',a' sequences highlighted. If you can, please, help !","package":"sparc.vim","4":"sparc.vim","src_id":"1979","5":"1979","creation_date":"1052459452","6":"1052459452"},{"0":"635","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"sparc.vim","4":"sparc.vim","src_id":"1975","5":"1975","creation_date":"1052390628","6":"1052390628"}]},"634":{"script_id":"634","0":"634","script_name":"otf.vim","1":"otf.vim","script_type":"utility","2":"utility","summary":"On-The-Fly coloring of patterns, Inspired by MultipleSearch.vim","3":"On-The-Fly coloring of patterns, Inspired by MultipleSearch.vim","description":"Inspired by MultipleSearch.vim vimscript #479\r\n\r\nThis plugin will allow you to highlight a specific search pattern with a specific (pre made) highlight group, and allows you to easily redefine the search pattern and empty a specific pattern. There are 8 possible simultaneous highlight patterns currently available and the script should be easy to modify to add more, etc. The highlight groups are via syntax highlighting and as such your VIM needs +syntax feature.\r\n\r\n\r\nThere are 2 commands, 1 to clear all highlighting, 1 to manipulate individule color groups.\r\n:OTFReset -- to clear all highlighting done by this script. (think :noh) This can probably be shortened to :OTFR on the command line.\r\n\r\n:OTF -- takes a count (line number position) to specify the color group to use (1-8). blank string clears highlighting for the specified color group, while the bang (:OTF!) denotes that the specifed string should be treated as a keyword (think register), see below:\r\n\r\nUse Like So:\r\n    Highlight Current Word Under The Cursor:\r\n    :1OTF <c-r><c-w>\r\n    :1OTF! w\r\n    Highlight Current Search Pattern:\r\n    :1OTF <c-r>\/\r\n    :1OTF! \/\r\n    Use A Pattern From A Register:\r\n    :1OTF <c-r>\"\r\n    :1OTF! \"\r\n    Just Type The Pattern In Manually:\r\n    :1OTF \\cotf\\d\r\n    Turn Off Coloring For The First Highlight Group:\r\n    :1OTF\r\n    :1OTF!\r\n    Turn Off Coloring For The Second Highlight Group: (etc.)\r\n    :2OTF\r\n    :2OTF!\r\n    Turn Off Coloring For All Groups:\r\n    :OTFReset\r\n    Which can probably be shortened to:\r\n    :OTFR\r\n\r\nYou can override the default highlight group color definitions by simply defining your own highlight groups for feralotf# (where # is a number from 1 to 8) for example place this in your .vimrc (or color file, etc.):\r\n\" {{{ OVERRIDE On the fly highlight groups.\r\nhi feralotf1\t\tguifg=#4682B4 guibg=Linen\r\nhi feralotf2\t\tguifg=Linen\r\nhi feralotf3\t\tguifg=Linen guibg=azure4\r\nhi feralotf4\t\tguifg=Linen guibg=PaleGreen4\r\n\" }}}\r\n","4":"Inspired by MultipleSearch.vim vimscript #479\r\n\r\nThis plugin will allow you to highlight a specific search pattern with a specific (pre made) highlight group, and allows you to easily redefine the search pattern and empty a specific pattern. There are 8 possible simultaneous highlight patterns currently available and the script should be easy to modify to add more, etc. The highlight groups are via syntax highlighting and as such your VIM needs +syntax feature.\r\n\r\n\r\nThere are 2 commands, 1 to clear all highlighting, 1 to manipulate individule color groups.\r\n:OTFReset -- to clear all highlighting done by this script. (think :noh) This can probably be shortened to :OTFR on the command line.\r\n\r\n:OTF -- takes a count (line number position) to specify the color group to use (1-8). blank string clears highlighting for the specified color group, while the bang (:OTF!) denotes that the specifed string should be treated as a keyword (think register), see below:\r\n\r\nUse Like So:\r\n    Highlight Current Word Under The Cursor:\r\n    :1OTF <c-r><c-w>\r\n    :1OTF! w\r\n    Highlight Current Search Pattern:\r\n    :1OTF <c-r>\/\r\n    :1OTF! \/\r\n    Use A Pattern From A Register:\r\n    :1OTF <c-r>\"\r\n    :1OTF! \"\r\n    Just Type The Pattern In Manually:\r\n    :1OTF \\cotf\\d\r\n    Turn Off Coloring For The First Highlight Group:\r\n    :1OTF\r\n    :1OTF!\r\n    Turn Off Coloring For The Second Highlight Group: (etc.)\r\n    :2OTF\r\n    :2OTF!\r\n    Turn Off Coloring For All Groups:\r\n    :OTFReset\r\n    Which can probably be shortened to:\r\n    :OTFR\r\n\r\nYou can override the default highlight group color definitions by simply defining your own highlight groups for feralotf# (where # is a number from 1 to 8) for example place this in your .vimrc (or color file, etc.):\r\n\" {{{ OVERRIDE On the fly highlight groups.\r\nhi feralotf1\t\tguifg=#4682B4 guibg=Linen\r\nhi feralotf2\t\tguifg=Linen\r\nhi feralotf3\t\tguifg=Linen guibg=azure4\r\nhi feralotf4\t\tguifg=Linen guibg=PaleGreen4\r\n\" }}}\r\n","install_details":"To Install:\r\n    Drop into plugin directory.\r\nTo Uninstall\r\n    Remove from plugin directory\r\nTo Test Drive:\r\n    Load file into vim and source it (:source %)\r\n    :OTF \\cotf\\d\r\n    You should see all occurrences of `otf#` where # is a number as specified by \\d highlighted as white text on red background.\r\n    You can turn off the highlighting with\r\n    :OTF\r\n    If you would like to see another color, use this format: :#OTF <pattern> where # is a number between 1 and 8 and <pattern> is what you want to color.","5":"To Install:\r\n    Drop into plugin directory.\r\nTo Uninstall\r\n    Remove from plugin directory\r\nTo Test Drive:\r\n    Load file into vim and source it (:source %)\r\n    :OTF \\cotf\\d\r\n    You should see all occurrences of `otf#` where # is a number as specified by \\d highlighted as white text on red background.\r\n    You can turn off the highlighting with\r\n    :OTF\r\n    If you would like to see another color, use this format: :#OTF <pattern> where # is a number between 1 and 8 and <pattern> is what you want to color.","first_name":"Robert","6":"Robert","last_name":"KellyIV","7":"KellyIV","releases":[{"0":"634","vim_version":"6.0","1":"6.0","script_version":"0.31","2":"0.31","version_comment":"Refinement of :OTF -- just bank (with no keyword) will clear the specified group.\r\nImprovement: ':[#]OTFG[!] <register>' which will copy contents of specifed group to specified register.This means that you can \":2OTFG y\" to copy the search pattern used by highlight group 2 into register y.","3":"Refinement of :OTF -- just bank (with no keyword) will clear the specified group.\r\nImprovement: ':[#]OTFG[!] <register>' which will copy contents of specifed group to specified register.This means that you can \":2OTFG y\" to copy the search pattern used by highlight group 2 into register y.","package":"otf.vim","4":"otf.vim","src_id":"3136","5":"3136","creation_date":"1087332678","6":"1087332678"},{"0":"634","vim_version":"6.0","1":"6.0","script_version":"0.21","2":"0.21","version_comment":"Improvement: As per a suggestion from Mathieu CLABAUT the feralotf# highlight groups now use the default keyword, This allows you to override these default colors easily.","3":"Improvement: As per a suggestion from Mathieu CLABAUT the feralotf# highlight groups now use the default keyword, This allows you to override these default colors easily.","package":"otf.vim","4":"otf.vim","src_id":"1970","5":"1970","creation_date":"1052272527","6":"1052272527"},{"0":"634","vim_version":"6.0","1":"6.0","script_version":"0.2","2":"0.2","version_comment":"Small update: converted :OTF1-8 into :OTF which takes a count (line number position) and takes optional bang to specify string as a keyword (think register)\r\nKeywords are:\r\n    (w) cword,                     expand(\"<cword>\")\r\n    (W) \\<cword\\>                  \"\\\\<\".expand(\"<cword>\").\"\\\\>\"\r\n    (\") unnamed register           @@\r\n    (\/) current search string      @\/\r\ni.e. \":2OTF! \/\" (bang) will pull in the current search string and color it in color group2, while \":2OTF \/\" (no bang) will color '\/' in color group2\r\n\r\nOriginal :OTF1-8 commands updated to bang style but commented out (just in case anyone liked that method)","3":"Small update: converted :OTF1-8 into :OTF which takes a count (line number position) and takes optional bang to specify string as a keyword (think register)\r\nKeywords are:\r\n    (w) cword,                     expand(\"<cword>\")\r\n    (W) \\<cword\\>                  \"\\\\<\".expand(\"<cword>\").\"\\\\>\"\r\n    (\") unnamed register           @@\r\n    (\/) current search string      @\/\r\ni.e. \":2OTF! \/\" (bang) will pull in the current search string and color it in color group2, while \":2OTF \/\" (no bang) will color '\/' in color group2\r\n\r\nOriginal :OTF1-8 commands updated to bang style but commented out (just in case anyone liked that method)","package":"otf.vim","4":"otf.vim","src_id":"1965","5":"1965","creation_date":"1051964721","6":"1051964721"},{"0":"634","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"otf.vim","4":"otf.vim","src_id":"1963","5":"1963","creation_date":"1051915750","6":"1051915750"}]},"633":{"script_id":"633","0":"633","script_name":"Reindent","1":"Reindent","script_type":"utility","2":"utility","summary":"Reindent a complete file based on indent information taken out of indent file.","3":"Reindent a complete file based on indent information taken out of indent file.","description":"If you like well formatted files use this plugin to chage the indention of a complete file.\r\n\r\nAnnotations:\r\nThe indention information is taken out of the VIM Indent-files. This\r\nscript processes them in a little different way than vim itself, therefore\r\nit is possible that the indent-functions have to be rewritten before they \r\nwork.\r\nThis script tries to rewrite the indent functions automatically (during \r\nthis a file \"reindent.tmp\" will be created in your current working \r\ndirectory).\r\nThere may be indent functions out there that don't work with this script  because they are too complex to be rewriten automatically with my \r\ncode.\r\n                                                                                \r\nPreconditions:\r\n- A indent function has to exist for your current file (indentexpr is set)\r\n- Your current working directory has to be writable if Indent-function has to be rewritten.\r\n\r\nUsage:\r\n1. Copy this file to your plugin directory\r\n2. start vim with i.E. a HTML-File\r\n3. Hit <Lead>R (If you don't know what <Leader> is read :help leader \r\n    or press \\R to reindent).\r\n    If using menus you will find a new menu item \"Reindent\" in menu \r\n    \"Syntax\".\r\n4. Customize the Keystroke with an Entry in your .vimrc i.E.:\r\n    map ff <Plug>reindent \" call reindent by pressing ff","4":"If you like well formatted files use this plugin to chage the indention of a complete file.\r\n\r\nAnnotations:\r\nThe indention information is taken out of the VIM Indent-files. This\r\nscript processes them in a little different way than vim itself, therefore\r\nit is possible that the indent-functions have to be rewritten before they \r\nwork.\r\nThis script tries to rewrite the indent functions automatically (during \r\nthis a file \"reindent.tmp\" will be created in your current working \r\ndirectory).\r\nThere may be indent functions out there that don't work with this script  because they are too complex to be rewriten automatically with my \r\ncode.\r\n                                                                                \r\nPreconditions:\r\n- A indent function has to exist for your current file (indentexpr is set)\r\n- Your current working directory has to be writable if Indent-function has to be rewritten.\r\n\r\nUsage:\r\n1. Copy this file to your plugin directory\r\n2. start vim with i.E. a HTML-File\r\n3. Hit <Lead>R (If you don't know what <Leader> is read :help leader \r\n    or press \\R to reindent).\r\n    If using menus you will find a new menu item \"Reindent\" in menu \r\n    \"Syntax\".\r\n4. Customize the Keystroke with an Entry in your .vimrc i.E.:\r\n    map ff <Plug>reindent \" call reindent by pressing ff","install_details":"Copy this file to your plugin directory\r\n","5":"Copy this file to your plugin directory\r\n","first_name":"J\u00c3\u00b6rg","6":"J\u00c3\u00b6rg","last_name":"Tretter","7":"Tretter","releases":[{"0":"633","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"reindent.vim","4":"reindent.vim","src_id":"1962","5":"1962","creation_date":"1051895091","6":"1051895091"}]},"632":{"script_id":"632","0":"632","script_name":"make-element","1":"make-element","script_type":"utility","2":"utility","summary":"generic imap to make an xml element of any word you type","3":"generic imap to make an xml element of any word you type","description":"In insert mode, typing anyword,,, gets translated to an xml element named 'anyword'\r\n\r\nExample 1:\r\n      anyword,,,<cr><tab>xsl:if,,, ==>\r\n      <anyword>\r\n            <xsl:if>\r\n            <\/xsl:if>\r\n      <\/anyword>\r\nwith the cursor after the element open tag. \r\n\r\nIf anyword is not on a line by itself, no newline is added.\r\n\r\nExample 2:\r\nThis is a bold,,, statement ==> This is a <bold>statement<\/bold>\r\n\r\nUse it all the time myself, in docbook and with some custom dtd's.\r\n\r\nSee vimtip #465","4":"In insert mode, typing anyword,,, gets translated to an xml element named 'anyword'\r\n\r\nExample 1:\r\n      anyword,,,<cr><tab>xsl:if,,, ==>\r\n      <anyword>\r\n            <xsl:if>\r\n            <\/xsl:if>\r\n      <\/anyword>\r\nwith the cursor after the element open tag. \r\n\r\nIf anyword is not on a line by itself, no newline is added.\r\n\r\nExample 2:\r\nThis is a bold,,, statement ==> This is a <bold>statement<\/bold>\r\n\r\nUse it all the time myself, in docbook and with some custom dtd's.\r\n\r\nSee vimtip #465","install_details":"just source it from ftplugin\/xml.vim or ~\/.vimrc or _vimrc","5":"just source it from ftplugin\/xml.vim or ~\/.vimrc or _vimrc","first_name":"Bart","6":"Bart","last_name":"van Deenen","7":"van Deenen","releases":[{"0":"632","vim_version":"5.7","1":"5.7","script_version":"1.1","2":"1.1","version_comment":"This version also works with single character xml elements","3":"This version also works with single character xml elements","package":"make-element.vim","4":"make-element.vim","src_id":"3835","5":"3835","creation_date":"1107665160","6":"1107665160"},{"0":"632","vim_version":"5.7","1":"5.7","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"make-element.vim","4":"make-element.vim","src_id":"1956","5":"1956","creation_date":"1051786918","6":"1051786918"}]},"631":{"script_id":"631","0":"631","script_name":"cf.vim","1":"cf.vim","script_type":"syntax","2":"syntax","summary":"Syntax highlighting for the Confluence logic design language.","3":"Syntax highlighting for the Confluence logic design language.","description":"Syntax highlighting for Confluence.\nConfluence is a logic design language created by Launchbird Designs Systems, Inc.\n\nSee http:\/\/www.launchbird.com for more info.","4":"Syntax highlighting for Confluence.\nConfluence is a logic design language created by Launchbird Designs Systems, Inc.\n\nSee http:\/\/www.launchbird.com for more info.","install_details":"","5":"","first_name":"tom","6":"tom","last_name":"hawkins","7":"hawkins","releases":[{"0":"631","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"cf.vim","4":"cf.vim","src_id":"1955","5":"1955","creation_date":"1051769952","6":"1051769952"}]},"630":{"script_id":"630","0":"630","script_name":"resolv.conf syntax","1":"resolv.conf syntax","script_type":"syntax","2":"syntax","summary":"resolver syntax","3":"resolver syntax","description":"Resolver syntax highlighting\r\nLatest version: http:\/\/ld.yi.org\/vim\/resolv.vim","4":"Resolver syntax highlighting\r\nLatest version: http:\/\/ld.yi.org\/vim\/resolv.vim","install_details":"Place it in the syntax directory","5":"Place it in the syntax directory","first_name":"Little","6":"Little","last_name":"Dragon","7":"Dragon","releases":[{"0":"630","vim_version":"6.0","1":"6.0","script_version":"0.2","2":"0.2","version_comment":"Bug fixes","3":"Bug fixes","package":"resolv.vim","4":"resolv.vim","src_id":"6529","5":"6529","creation_date":"1166579701","6":"1166579701"},{"0":"630","vim_version":"6.0","1":"6.0","script_version":"0.1a","2":"0.1a","version_comment":"Initial upload","3":"Initial upload","package":"resolv.vim","4":"resolv.vim","src_id":"1954","5":"1954","creation_date":"1051726306","6":"1051726306"}]},"629":{"script_id":"629","0":"629","script_name":"putty","1":"putty","script_type":"color scheme","2":"color scheme","summary":"A color scheme that resembles one of Putty","3":"A color scheme that resembles one of Putty","description":"This package offers a eye-catching color scheme that resembles the default color scheme of Putty telnet terminal.","4":"This package offers a eye-catching color scheme that resembles the default color scheme of Putty telnet terminal.","install_details":"You might put this script in the '$(VIM)\/colors' directory.","5":"You might put this script in the '$(VIM)\/colors' directory.","first_name":"Prachya","6":"Prachya","last_name":"Boonkwan","7":"Boonkwan","releases":[{"0":"629","vim_version":"6.0","1":"6.0","script_version":"0.2.1","2":"0.2.1","version_comment":"This version patches a bit of color configurations","3":"This version patches a bit of color configurations","package":"putty.vim","4":"putty.vim","src_id":"1950","5":"1950","creation_date":"1051573358","6":"1051573358"},{"0":"629","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"putty.vim","4":"putty.vim","src_id":"1946","5":"1946","creation_date":"1051481505","6":"1051481505"}]},"628":{"script_id":"628","0":"628","script_name":"SeeTab","1":"SeeTab","script_type":"utility","2":"utility","summary":"Provides vertical tabbing-bars for leading tabs (or whitespace for et)","3":"Provides vertical tabbing-bars for leading tabs (or whitespace for et)","description":"Usage:  :SeeTab    -- toggles SeeTab on and off\r\n\r\nIf expandtabs is off, then leading tabs show up with one bar per tab.\r\n\r\nIf expandtabs is on, then one leading whitespace at intervals\r\nspecified by your tabstop is marked by a highlighted space.\r\n\r\nTo change the default colors of foreground as magenta and background as black,\r\njust use something like the following setting in your <.vimrc>:\r\n\r\n    let g:SeeTabCtermFG=\"black\"\r\n    let g:SeeTabCtermBG=\"red\"\r\n    let g:SeeTabGuiFG=\"black\"\r\n    let g:SeeTabGuiBG=\"orange\"\r\n\r\n(alpha\/beta version available at http:\/\/www.drchip.org\/astronaut\/vim\/index.html#SEETAB)\r\n","4":"Usage:  :SeeTab    -- toggles SeeTab on and off\r\n\r\nIf expandtabs is off, then leading tabs show up with one bar per tab.\r\n\r\nIf expandtabs is on, then one leading whitespace at intervals\r\nspecified by your tabstop is marked by a highlighted space.\r\n\r\nTo change the default colors of foreground as magenta and background as black,\r\njust use something like the following setting in your <.vimrc>:\r\n\r\n    let g:SeeTabCtermFG=\"black\"\r\n    let g:SeeTabCtermBG=\"red\"\r\n    let g:SeeTabGuiFG=\"black\"\r\n    let g:SeeTabGuiBG=\"orange\"\r\n\r\n(alpha\/beta version available at http:\/\/www.drchip.org\/astronaut\/vim\/index.html#SEETAB)\r\n","install_details":"Simply put <seetab.vim> into your plugin directory.\r\n\r\nTo initialize SeeTab on, see vimtip#411\r\n(use SeeTab in a ...\/after\/plugin\/seetab.vim\r\nfile)\r\n","5":"Simply put <seetab.vim> into your plugin directory.\r\n\r\nTo initialize SeeTab on, see vimtip#411\r\n(use SeeTab in a ...\/after\/plugin\/seetab.vim\r\nfile)\r\n","first_name":"Charles","6":"Charles","last_name":"Campbell","7":"Campbell","releases":[{"0":"628","vim_version":"6.0","1":"6.0","script_version":"3","2":"3","version_comment":"Includes GetLatestVimScripts automatic updating and installing support (see vimscript#642)","3":"Includes GetLatestVimScripts automatic updating and installing support (see vimscript#642)","package":"SeeTab.vim.gz","4":"SeeTab.vim.gz","src_id":"3593","5":"3593","creation_date":"1099290711","6":"1099290711"},{"0":"628","vim_version":"6.0","1":"6.0","script_version":"2","2":"2","version_comment":"Initial upload","3":"Initial upload","package":"SeeTab.vim","4":"SeeTab.vim","src_id":"1939","5":"1939","creation_date":"1051279619","6":"1051279619"}]},"627":{"script_id":"627","0":"627","script_name":"MarkShift","1":"MarkShift","script_type":"syntax","2":"syntax","summary":"Highlights indents when \"expandtab\" option is on.","3":"Highlights indents when \"expandtab\" option is on.","description":"Usefull for editing indented source files which have been\r\nedited with the expand tab setting. When activated the\r\nfirst space out of every N spaces is highlighted. N is\r\nworked out automaticlly from the shiftwidth setting of the\r\nbuffer.","4":"Usefull for editing indented source files which have been\r\nedited with the expand tab setting. When activated the\r\nfirst space out of every N spaces is highlighted. N is\r\nworked out automaticlly from the shiftwidth setting of the\r\nbuffer.","install_details":"Place into your plugins directory","5":"Place into your plugins directory","first_name":"brad","6":"brad","last_name":"phelan","7":"phelan","releases":[{"0":"627","vim_version":"6.0","1":"6.0","script_version":"1.2","2":"1.2","version_comment":"Changed the distance between the highlight bar to use &ts as apposed to &sw as per suggestion gowri.satyanarayana@oracle.com, April 24, 2003 22:12 ","3":"Changed the distance between the highlight bar to use &ts as apposed to &sw as per suggestion gowri.satyanarayana@oracle.com, April 24, 2003 22:12 ","package":"markshift.vim","4":"markshift.vim","src_id":"1938","5":"1938","creation_date":"1051240699","6":"1051240699"},{"0":"627","vim_version":"6.0","1":"6.0","script_version":"1.1","2":"1.1","version_comment":"Was not able to toggle the shift highlighting off due to misnaming of a variable","3":"Was not able to toggle the shift highlighting off due to misnaming of a variable","package":"markshift.vim","4":"markshift.vim","src_id":"1937","5":"1937","creation_date":"1051151875","6":"1051151875"}]},"626":{"script_id":"626","0":"626","script_name":"ShowPairs","1":"ShowPairs","script_type":"utility","2":"utility","summary":"Highlights the matching pair surrounding the current cursor location.","3":"Highlights the matching pair surrounding the current cursor location.","description":"ShowPairs highlights the matching pair surrounding the current cursor location.  The main goal of this script is to highlight matching braces and parenthesis making it easier to edit nested expressions.\r\nHowever, ShowPairs uses the 'matchpairs' global option to determine what it should highlight, so it should be generic enough for other needs.","4":"ShowPairs highlights the matching pair surrounding the current cursor location.  The main goal of this script is to highlight matching braces and parenthesis making it easier to edit nested expressions.\r\nHowever, ShowPairs uses the 'matchpairs' global option to determine what it should highlight, so it should be generic enough for other needs.","install_details":"Put showpairs.vim into your $HOME\/.vim\/plugin or $HOME\\vimfiles\\plugin folder.","5":"Put showpairs.vim into your $HOME\/.vim\/plugin or $HOME\\vimfiles\\plugin folder.","first_name":"Anthony","6":"Anthony","last_name":"Kruize","7":"Kruize","releases":[{"0":"626","vim_version":"6.0","1":"6.0","script_version":"2.1","2":"2.1","version_comment":"Fixed errors that occured when the plugin was loaded due to 'fg' and 'bg' not being defined yet, and the fact that I used an autocmd from Vim 7, oops.\r\nThanks to Alex Kunin for actually letting me know about the problem so I could fix it.","3":"Fixed errors that occured when the plugin was loaded due to 'fg' and 'bg' not being defined yet, and the fact that I used an autocmd from Vim 7, oops.\r\nThanks to Alex Kunin for actually letting me know about the problem so I could fix it.","package":"showpairs.vim","4":"showpairs.vim","src_id":"5096","5":"5096","creation_date":"1139355468","6":"1139355468"},{"0":"626","vim_version":"6.0","1":"6.0","script_version":"1.1","2":"1.1","version_comment":"Fixed the fileformat so it doesn't include ^M's everywhere.\r\nFixed the highlighting so it works when 'fg' and 'bg' aren't yet defined.","3":"Fixed the fileformat so it doesn't include ^M's everywhere.\r\nFixed the highlighting so it works when 'fg' and 'bg' aren't yet defined.","package":"showpairs.vim","4":"showpairs.vim","src_id":"1945","5":"1945","creation_date":"1051426707","6":"1051426707"},{"0":"626","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"showpairs.vim","4":"showpairs.vim","src_id":"1931","5":"1931","creation_date":"1050974219","6":"1050974219"}]},"625":{"script_id":"625","0":"625","script_name":"Colo(u)r Sampler Pack","1":"Colo(u)r Sampler Pack","script_type":"color scheme","2":"color scheme","summary":"[[[Oct 2012 Update]]] Top 100(ish) Themes, GUI Menu","3":"[[[Oct 2012 Update]]] Top 100(ish) Themes, GUI Menu","description":"This package is simply to help people who want to try out a lot of color schemes.  It is the top 100(ish) rated color schemes on vim.sf.net as of Oct 28th, 2012 that are are not \"evil\" (binding keys, changing fonts, hiding the damned cursor (!?) ) --  zipped up in a single package.  Every single theme was updated to its newest revision, and converted to unix formatted line endings. \r\n\r\nThe menu has been simplified based on feedback to simply three categories.  Dark \/ Light \/ Other. \r\n\r\nThis package was put together simply to save others time in downloading the color schemes.  If you are a scheme author and for some reason do not want your scheme included, please simply drop me a note.  robert -at- robertmelton.com\r\n\r\nNow, the pack comes with an organized GUI menu, but no tool for console users.  I recommend you pick up http:\/\/www.vim.org\/scripts\/script.php?script_id=1488 which is a colorscheme scroller \/ chooser and browser.  \r\n\r\nNow includes the very cool Mimic schemes and menu: http:\/\/www.vim.org\/scripts\/script.php?script_id=2831\r\n\r\nMany of these schemes are Gvim only, and do not support consoles well... but there is a plugin to allow Gvim only themes to work in 88\/256 color terminals -> http:\/\/www.vim.org\/scripts\/script.php?script_id=2390.\r\n\r\nLove it or Hate it -- Rate it.  :)","4":"This package is simply to help people who want to try out a lot of color schemes.  It is the top 100(ish) rated color schemes on vim.sf.net as of Oct 28th, 2012 that are are not \"evil\" (binding keys, changing fonts, hiding the damned cursor (!?) ) --  zipped up in a single package.  Every single theme was updated to its newest revision, and converted to unix formatted line endings. \r\n\r\nThe menu has been simplified based on feedback to simply three categories.  Dark \/ Light \/ Other. \r\n\r\nThis package was put together simply to save others time in downloading the color schemes.  If you are a scheme author and for some reason do not want your scheme included, please simply drop me a note.  robert -at- robertmelton.com\r\n\r\nNow, the pack comes with an organized GUI menu, but no tool for console users.  I recommend you pick up http:\/\/www.vim.org\/scripts\/script.php?script_id=1488 which is a colorscheme scroller \/ chooser and browser.  \r\n\r\nNow includes the very cool Mimic schemes and menu: http:\/\/www.vim.org\/scripts\/script.php?script_id=2831\r\n\r\nMany of these schemes are Gvim only, and do not support consoles well... but there is a plugin to allow Gvim only themes to work in 88\/256 color terminals -> http:\/\/www.vim.org\/scripts\/script.php?script_id=2390.\r\n\r\nLove it or Hate it -- Rate it.  :)","install_details":"Simply unzip, and place the files in ~\/.vim\/plugin and ~\/.vim\/colors --- it will unzip with correct dir structure, so you can just unzip to ~\/.vim\r\n\r\nHope this helps you... join #vim on irc.freenode.net for all your vim help needs :)","5":"Simply unzip, and place the files in ~\/.vim\/plugin and ~\/.vim\/colors --- it will unzip with correct dir structure, so you can just unzip to ~\/.vim\r\n\r\nHope this helps you... join #vim on irc.freenode.net for all your vim help needs :)","first_name":"Robert","6":"Robert","last_name":"Melton","7":"Melton","releases":[{"0":"625","vim_version":"7.3","1":"7.3","script_version":"2012.10.28","2":"2012.10.28","version_comment":"*** Oct 28th, 2012 *** 23 new colorschemes, 44 updated colorschemes, and the inclusion of the very cool MimicPak (http:\/\/www.vim.org\/scripts\/script.php?script_id=2831)","3":"*** Oct 28th, 2012 *** 23 new colorschemes, 44 updated colorschemes, and the inclusion of the very cool MimicPak (http:\/\/www.vim.org\/scripts\/script.php?script_id=2831)","package":"ColorSamplerPack.zip","4":"ColorSamplerPack.zip","src_id":"18915","5":"18915","creation_date":"1351428994","6":"1351428994"}]},"624":{"script_id":"624","0":"624","script_name":"nightwish.vim","1":"nightwish.vim","script_type":"color scheme","2":"color scheme","summary":"dark colorscheme","3":"dark colorscheme","description":"Yet another dark colorscheme.\r\nTried to have a decent mix of all available colors\r\nto maximize readability.\r\nShould be pretty moderate on eyes.\r\nSee http:\/\/home.arcor.de\/muhler\/vim.htm\r\nfor a screenshot.\r\n","4":"Yet another dark colorscheme.\r\nTried to have a decent mix of all available colors\r\nto maximize readability.\r\nShould be pretty moderate on eyes.\r\nSee http:\/\/home.arcor.de\/muhler\/vim.htm\r\nfor a screenshot.\r\n","install_details":"put into your ~\/.vim\/colors\r\nand put\r\n:colorscheme nightwish\r\ninto your .vimrc","5":"put into your ~\/.vim\/colors\r\nand put\r\n:colorscheme nightwish\r\ninto your .vimrc","first_name":"michael","6":"michael","last_name":"muhler","7":"muhler","releases":[{"0":"624","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"nightwish.vim","4":"nightwish.vim","src_id":"1922","5":"1922","creation_date":"1050495295","6":"1050495295"}]},"623":{"script_id":"623","0":"623","script_name":"m4pic.vim","1":"m4pic.vim","script_type":"syntax","2":"syntax","summary":"syntax file for (g)pic with m4 macros","3":"syntax file for (g)pic with m4 macros","description":"Syntax highlighting for (g)pic files.\r\nSpecial support for m4 macros.\r\n","4":"Syntax highlighting for (g)pic files.\r\nSpecial support for m4 macros.\r\n","install_details":"Put into your ~\/.vim\/syntax\r\nand associate appropriate files with this syntax file, e.g.\r\n\r\nadd the following to your filetype.vim\r\n\r\naugroup filetypedetect\r\n\tau! BufRead,BufNewfile *.m4     setfiletype m4pic\r\naugroup END","5":"Put into your ~\/.vim\/syntax\r\nand associate appropriate files with this syntax file, e.g.\r\n\r\nadd the following to your filetype.vim\r\n\r\naugroup filetypedetect\r\n\tau! BufRead,BufNewfile *.m4     setfiletype m4pic\r\naugroup END","first_name":"michael","6":"michael","last_name":"muhler","7":"muhler","releases":[{"0":"623","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"m4pic.vim","4":"m4pic.vim","src_id":"1921","5":"1921","creation_date":"1050493863","6":"1050493863"}]},"622":{"script_id":"622","0":"622","script_name":"tagsubmenu","1":"tagsubmenu","script_type":"utility","2":"utility","summary":"Add a submenu for tags commands","3":"Add a submenu for tags commands","description":"Adds a small submenu to the Tools menu of gvim. The menu options allow you to jump to tags and run the different tagselect commands without having to remember all the different key sequences. The keyboard shortcuts are shown on the menu, so this plugin is also useful while you are learning the vim tag commands.","4":"Adds a small submenu to the Tools menu of gvim. The menu options allow you to jump to tags and run the different tagselect commands without having to remember all the different key sequences. The keyboard shortcuts are shown on the menu, so this plugin is also useful while you are learning the vim tag commands.","install_details":"Copy tagsubmenu.vim into your favorite plugin directory, or source it from your .vimrc file.","5":"Copy tagsubmenu.vim into your favorite plugin directory, or source it from your .vimrc file.","first_name":"Will","6":"Will","last_name":"Smith","7":"Smith","releases":[{"0":"622","vim_version":"6.0","1":"6.0","script_version":"1.1","2":"1.1","version_comment":"Added a menu option to search for tags that match a regular expression","3":"Added a menu option to search for tags that match a regular expression","package":"tagsubmenu.vim","4":"tagsubmenu.vim","src_id":"1923","5":"1923","creation_date":"1050559723","6":"1050559723"},{"0":"622","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"tagsubmenu.vim","4":"tagsubmenu.vim","src_id":"1920","5":"1920","creation_date":"1050479018","6":"1050479018"}]},"621":{"script_id":"621","0":"621","script_name":"Conflict2Diff","1":"Conflict2Diff","script_type":"utility","2":"utility","summary":"Turns a CVS conflict file into a threeway diff","3":"Turns a CVS conflict file into a threeway diff","description":"This plugin splits a CVS conflict file into three diff windows.  The 2 conflicting versions of the file are put on the left and right.  The central window contains the file, with each conflicting area replaced by \"=======\".  Buffer specific mappings are set up to make the merging simple:\r\n\r\n<Ctrl-Down> Move to the next conflict\r\n<Ctrl-Up> Move to the previous conflict\r\n<Ctrl-Left> Use the text from the lefthand file for this conflicting area\r\n<Ctrl-Right> Use the text from the righthand file for this conflicting area\r\n<Ctrl-q> Finish by closing the left and righthand windows, turning off diff and removing the mappings\r\n","4":"This plugin splits a CVS conflict file into three diff windows.  The 2 conflicting versions of the file are put on the left and right.  The central window contains the file, with each conflicting area replaced by \"=======\".  Buffer specific mappings are set up to make the merging simple:\r\n\r\n<Ctrl-Down> Move to the next conflict\r\n<Ctrl-Up> Move to the previous conflict\r\n<Ctrl-Left> Use the text from the lefthand file for this conflicting area\r\n<Ctrl-Right> Use the text from the righthand file for this conflicting area\r\n<Ctrl-q> Finish by closing the left and righthand windows, turning off diff and removing the mappings\r\n","install_details":"Unpack the files somewhere that vim can find them.  You'll need to run the :helptags command to install the documentation.","5":"Unpack the files somewhere that vim can find them.  You'll need to run the :helptags command to install the documentation.","first_name":"Chris","6":"Chris","last_name":"Rimmer","7":"Rimmer","releases":[{"0":"621","vim_version":"6.0","1":"6.0","script_version":"1.1","2":"1.1","version_comment":"Changed so that moving up and down with <Ctrl+Up> and <Ctrl+Down> also centres the cursor vertically on the screen.","3":"Changed so that moving up and down with <Ctrl+Up> and <Ctrl+Down> also centres the cursor vertically on the screen.","package":"conf2dif.zip","4":"conf2dif.zip","src_id":"3209","5":"3209","creation_date":"1089180317","6":"1089180317"},{"0":"621","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"conf2dif.zip","4":"conf2dif.zip","src_id":"1917","5":"1917","creation_date":"1050383507","6":"1050383507"}]},"620":{"script_id":"620","0":"620","script_name":"Russian menu for gvim\/win32","1":"Russian menu for gvim\/win32","script_type":"utility","2":"utility","summary":"Russian menu for GVIM\/Windows cp1251","3":"Russian menu for GVIM\/Windows cp1251","description":"Russian menu translation especially for Windows users of GVIM 6.x. Errors not translated yet, sorry...","4":"Russian menu translation especially for Windows users of GVIM 6.x. Errors not translated yet, sorry...","install_details":"Just copy this to $VIMRUNTIME\/lang\/ where other menu lives :)","5":"Just copy this to $VIMRUNTIME\/lang\/ where other menu lives :)","first_name":"Roman","6":"Roman","last_name":"Shlum","7":"Shlum","releases":[{"0":"620","vim_version":"6.0","1":"6.0","script_version":"6.1","2":"6.1","version_comment":"Initial upload","3":"Initial upload","package":"menu_russian_russia.1251.vim","4":"menu_russian_russia.1251.vim","src_id":"1913","5":"1913","creation_date":"1050267227","6":"1050267227"}]},"619":{"script_id":"619","0":"619","script_name":"brookstream","1":"brookstream","script_type":"color scheme","2":"color scheme","summary":"A dark blue\/green colorscheme","3":"A dark blue\/green colorscheme","description":"A colorscheme based on David Lazar's dakdot scheme.\r\n\r\nFor the GUI version.\r\n\r\nScreenshot: http:\/\/www.brookstream.org\/vim_screenshot.html","4":"A colorscheme based on David Lazar's dakdot scheme.\r\n\r\nFor the GUI version.\r\n\r\nScreenshot: http:\/\/www.brookstream.org\/vim_screenshot.html","install_details":"Drop this file in your $VIMRUNTIME\/colors\/ directory.","5":"Drop this file in your $VIMRUNTIME\/colors\/ directory.","first_name":"Peter","6":"Peter","last_name":"B\u00c3\u00a4ckstr\u00c3\u00b6m","7":"B\u00c3\u00a4ckstr\u00c3\u00b6m","releases":[{"0":"619","vim_version":"6.0","1":"6.0","script_version":"1.1","2":"1.1","version_comment":"Made some small adjustments","3":"Made some small adjustments","package":"brookstream.vim","4":"brookstream.vim","src_id":"1915","5":"1915","creation_date":"1050308260","6":"1050308260"},{"0":"619","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"brookstream.vim","4":"brookstream.vim","src_id":"1910","5":"1910","creation_date":"1050159936","6":"1050159936"}]},"618":{"script_id":"618","0":"618","script_name":"BreakPts","1":"BreakPts","script_type":"utility","2":"utility","summary":"Set\/View Vim breakpoints and browse functions visually","3":"Set\/View Vim breakpoints and browse functions visually","description":"YOU NEED Vim7.0 FOR THE NEW VERSION TO WORK.\r\n\r\nNew version no longer depends on multvals.vim\r\n\r\nThe plugin provides a few features for debugging Vim scripts that are similar\r\nto what IDEs normally have, such as browing source, managing breatpoints etc.\r\nSetting breakpoints visually in functions is very important as you need to\r\nspecify the exact line number for the line you are interested in (which often\r\nis difficult to find out if you use |line-continuation| characters to format\r\ncode). This also avoids typing in the |:breakadd| command while guessing what\r\nthe scriptids for your script are. It also defines a few convenience commands\r\nthat take the place of Vim built-in commands and add Vim command-line\r\ncompletion feature.\r\n\r\nThe plugin also provided utilties to create various conditional breakpoints\r\nprogrammatically to help debug complex and iterative logic. You can set a\r\ncondition, a skip count and an expire count for your breakpoint to be valid on\r\nany particular line.\r\n\r\nYou can also simply use the plugin to browse Vim sripts and functions. It\r\nprovides a browser history type of features to drill into the code, by\r\nnavigating the function calls and return back to the previous function at any\r\ntime.\r\n\r\nHere is a list of features:\r\n    - Set\/unset breakpoints in functions and scripts visually.\r\n    - Save\/clear\/restore list of breakpoints across sessions.\r\n    - Browse functions and script by navigating through the list of functions\r\n      (and function references) and scripts.\r\n    - Reload scripts when they change externally (during development)\r\n    - Global functions to set\/unset breakpoints programmatically with optional\r\n      conditions.\r\n    - Misc. alternative commands for the built-ins that typically work better\r\n      (better completion and defaults).\r\n    - Remote debugging ability to debug scripts in one Vim session using\r\n      another Vim as the debugger.\r\n\r\n\r\n\r\nSearch_keywords: breakpoint breakpts breakadd breaklist breakdel break vim WinManager visual list Hari Krishna Dara\r\n","4":"YOU NEED Vim7.0 FOR THE NEW VERSION TO WORK.\r\n\r\nNew version no longer depends on multvals.vim\r\n\r\nThe plugin provides a few features for debugging Vim scripts that are similar\r\nto what IDEs normally have, such as browing source, managing breatpoints etc.\r\nSetting breakpoints visually in functions is very important as you need to\r\nspecify the exact line number for the line you are interested in (which often\r\nis difficult to find out if you use |line-continuation| characters to format\r\ncode). This also avoids typing in the |:breakadd| command while guessing what\r\nthe scriptids for your script are. It also defines a few convenience commands\r\nthat take the place of Vim built-in commands and add Vim command-line\r\ncompletion feature.\r\n\r\nThe plugin also provided utilties to create various conditional breakpoints\r\nprogrammatically to help debug complex and iterative logic. You can set a\r\ncondition, a skip count and an expire count for your breakpoint to be valid on\r\nany particular line.\r\n\r\nYou can also simply use the plugin to browse Vim sripts and functions. It\r\nprovides a browser history type of features to drill into the code, by\r\nnavigating the function calls and return back to the previous function at any\r\ntime.\r\n\r\nHere is a list of features:\r\n    - Set\/unset breakpoints in functions and scripts visually.\r\n    - Save\/clear\/restore list of breakpoints across sessions.\r\n    - Browse functions and script by navigating through the list of functions\r\n      (and function references) and scripts.\r\n    - Reload scripts when they change externally (during development)\r\n    - Global functions to set\/unset breakpoints programmatically with optional\r\n      conditions.\r\n    - Misc. alternative commands for the built-ins that typically work better\r\n      (better completion and defaults).\r\n    - Remote debugging ability to debug scripts in one Vim session using\r\n      another Vim as the debugger.\r\n\r\n\r\n\r\nSearch_keywords: breakpoint breakpts breakadd breaklist breakdel break vim WinManager visual list Hari Krishna Dara\r\n","install_details":"- To install, download the latest versions of these two plugins:\r\n    breakpts: http:\/\/www.vim.org\/script.php?script_id=618\r\n    genutils:  http:\/\/vim.sourceforge.net\/script.php?script_id=197\r\n- Extract the zip archives in to your runtime directory (.vim or vimfiles\r\n  under your HOME directory).\r\n- Make sure your vim has +signs feature.\r\n- Start a new instance or go to an existing instance of vim.\r\n- Execute:\r\n                                                                           \r\n    :helpt <your runtime directory>\/doc\r\n                                                                           \r\n  This should generate the help tags for the breakpts plugin help.\r\n- Take a look at the |breakpts-settings| to change any default\r\n  configuration and behavior.\r\n                                                                           \r\nOptional:\r\n- Take a look at the |breakpts-winmanager| to configure with winmanager.\r\n- Choose a hotkey as described in |breakpts-usage|.\r\n- Considier installation the following two optional plugins:\r\n  - If cmdalias plugin is installed, it will be used to create aliases for\r\n    a few commands, to make it easier to type. Download the plugin from:\r\n        http:\/\/www.vim.org\/script.php?script_id=745\r\n  - If foldutil plugin is installed, it will be used to foldaway the code\r\n    such that the breakpoints are easier to see. Download the plugin from:\r\n        http:\/\/www.vim.org\/script.php?script_id=158\r\n\r\n\r\nFor versions older than 4.0, you also need multvals.vim: vimscript#171 in addition to genutils, and you need to download the non-autoload versions of both. See their respective installation sections for more information .\r\n","5":"- To install, download the latest versions of these two plugins:\r\n    breakpts: http:\/\/www.vim.org\/script.php?script_id=618\r\n    genutils:  http:\/\/vim.sourceforge.net\/script.php?script_id=197\r\n- Extract the zip archives in to your runtime directory (.vim or vimfiles\r\n  under your HOME directory).\r\n- Make sure your vim has +signs feature.\r\n- Start a new instance or go to an existing instance of vim.\r\n- Execute:\r\n                                                                           \r\n    :helpt <your runtime directory>\/doc\r\n                                                                           \r\n  This should generate the help tags for the breakpts plugin help.\r\n- Take a look at the |breakpts-settings| to change any default\r\n  configuration and behavior.\r\n                                                                           \r\nOptional:\r\n- Take a look at the |breakpts-winmanager| to configure with winmanager.\r\n- Choose a hotkey as described in |breakpts-usage|.\r\n- Considier installation the following two optional plugins:\r\n  - If cmdalias plugin is installed, it will be used to create aliases for\r\n    a few commands, to make it easier to type. Download the plugin from:\r\n        http:\/\/www.vim.org\/script.php?script_id=745\r\n  - If foldutil plugin is installed, it will be used to foldaway the code\r\n    such that the breakpoints are easier to see. Download the plugin from:\r\n        http:\/\/www.vim.org\/script.php?script_id=158\r\n\r\n\r\nFor versions older than 4.0, you also need multvals.vim: vimscript#171 in addition to genutils, and you need to download the non-autoload versions of both. See their respective installation sections for more information .\r\n","first_name":"Hari Krishna","6":"Hari Krishna","last_name":"Dara","7":"Dara","releases":[{"0":"618","vim_version":"7.0","1":"7.0","script_version":"4.0","2":"4.0","version_comment":"- The script is now more aligned to Vim 7.0.\r\n- It is now autoloaded.\r\n- Not dependent on multvals anymore.\r\n- Comes with a Vim style help file.\r\n- Minor improvements and fixes.\r\n","3":"- The script is now more aligned to Vim 7.0.\r\n- It is now autoloaded.\r\n- Not dependent on multvals anymore.\r\n- Comes with a Vim style help file.\r\n- Minor improvements and fixes.\r\n","package":"breakpts-4.0.zip","4":"breakpts-4.0.zip","src_id":"8142","5":"8142","creation_date":"1199903669","6":"1199903669"},{"0":"618","vim_version":"6.0","1":"6.0","script_version":"3.2","2":"3.2","version_comment":"Release 3.2 for vim7 compatibility. Thanks to David Fishburn for\r\nproviding most of the patches for vim7 and testing it.\r\n","3":"Release 3.2 for vim7 compatibility. Thanks to David Fishburn for\r\nproviding most of the patches for vim7 and testing it.\r\n","package":"breakpts.vim","4":"breakpts.vim","src_id":"5661","5":"5661","creation_date":"1147108538","6":"1147108538"},{"0":"618","vim_version":"6.0","1":"6.0","script_version":"3.1","2":"3.1","version_comment":"Just trying to fix a bad upload for version 3.1\r\n\r\n- Now requires Vim 6.3 \r\n- More documentation. \r\n- The script now works perfectly well for remote debugging. All the Vim bugs\r\n  were fixed in 6.3 and I have used the plugin for some real debugging this\r\n  time, and found it to be quite usable. \r\n- You can now reload scripts from remote session. \r\n- Many new useful commands with command-completions. \r\n  - Runtime: that completes filenames from 'rtp' \r\n  - Debug: that completes command and function names (with arguments).\r\n  - Breakadd\/Breakdel: that complete function names\/script paths \r\n  - Where: to see the context at the debug prompt. \r\n- Useful BreakPtsSetupBuf command. A few other global commands. \r\n- Lots of other misc. and subtle improvements. Read the script header completely\r\n  for details (you can diff with the old version if you like :)\r\n","3":"Just trying to fix a bad upload for version 3.1\r\n\r\n- Now requires Vim 6.3 \r\n- More documentation. \r\n- The script now works perfectly well for remote debugging. All the Vim bugs\r\n  were fixed in 6.3 and I have used the plugin for some real debugging this\r\n  time, and found it to be quite usable. \r\n- You can now reload scripts from remote session. \r\n- Many new useful commands with command-completions. \r\n  - Runtime: that completes filenames from 'rtp' \r\n  - Debug: that completes command and function names (with arguments).\r\n  - Breakadd\/Breakdel: that complete function names\/script paths \r\n  - Where: to see the context at the debug prompt. \r\n- Useful BreakPtsSetupBuf command. A few other global commands. \r\n- Lots of other misc. and subtle improvements. Read the script header completely\r\n  for details (you can diff with the old version if you like :)\r\n","package":"breakpts.vim","4":"breakpts.vim","src_id":"3233","5":"3233","creation_date":"1089892331","6":"1089892331"},{"0":"618","vim_version":"6.0","1":"6.0","script_version":"3.0","2":"3.0","version_comment":"See the function header for details.\r\n- Now BreakPts command can take an option to specify the initial view.\r\n- New BPOpen command to open a script for editing from the scripts view.\r\n- Experimental features to debug scripts from a remote vim using the\r\n  |clientserver| functionality. It is now possible to view the context and execute the :debug\r\n  mode commands such as >next >cont from the browser, while debugging\r\n  remotely. CAUTION: This requires installing a patch to vim and sometimes makes Vim crash (see installation section).\r\n- Two global functions BPBreak() and BPBreakIf() to add breakpoints from\r\n  with in your script. The BPBreak() can also be used while at the\r\n  :debug prompt (>) to easily add breakpoints without needing to worry\r\n  about the function name and line number. This requires a patch to be\r\n  installed to vim (see installation section).\r\n- New setting g:brkptsModFuncHeader.\r\n- New version dependency check on dependent libraries. You now get an\r\n  error message during the Vim startup if you don't have the right\r\n  version of multvals and genutils.\r\n- Remember the line number when the browser is closed and reopened.\r\n- Fixed a bug in handling function names, such as <SID>Func.\r\n- Fixed a bug in browser name on unixy vim.\r\n- Plugin reloading now handles some non-standard naming conventions for\r\n  the loaded_ variable and works better.\r\n- Fixed other misc. bugs.\r\n- The g:loaded_breakpts variable now contains the version number for any dependency checking (see :help v:version for format information)","3":"See the function header for details.\r\n- Now BreakPts command can take an option to specify the initial view.\r\n- New BPOpen command to open a script for editing from the scripts view.\r\n- Experimental features to debug scripts from a remote vim using the\r\n  |clientserver| functionality. It is now possible to view the context and execute the :debug\r\n  mode commands such as >next >cont from the browser, while debugging\r\n  remotely. CAUTION: This requires installing a patch to vim and sometimes makes Vim crash (see installation section).\r\n- Two global functions BPBreak() and BPBreakIf() to add breakpoints from\r\n  with in your script. The BPBreak() can also be used while at the\r\n  :debug prompt (>) to easily add breakpoints without needing to worry\r\n  about the function name and line number. This requires a patch to be\r\n  installed to vim (see installation section).\r\n- New setting g:brkptsModFuncHeader.\r\n- New version dependency check on dependent libraries. You now get an\r\n  error message during the Vim startup if you don't have the right\r\n  version of multvals and genutils.\r\n- Remember the line number when the browser is closed and reopened.\r\n- Fixed a bug in handling function names, such as <SID>Func.\r\n- Fixed a bug in browser name on unixy vim.\r\n- Plugin reloading now handles some non-standard naming conventions for\r\n  the loaded_ variable and works better.\r\n- Fixed other misc. bugs.\r\n- The g:loaded_breakpts variable now contains the version number for any dependency checking (see :help v:version for format information)","package":"breakpts.vim","4":"breakpts.vim","src_id":"2612","5":"2612","creation_date":"1071688374","6":"1071688374"},{"0":"618","vim_version":"6.0","1":"6.0","script_version":"2.0","2":"2.0","version_comment":"Number of improvements, thanks to David Fishburn {fishburn at sybase dot org} for feedback\/ideas and help with identifying issues. Note: This version requires Vim 6.2. New features at a glance:\r\n\r\n    - View the list of scripts loaded.\r\n    - View the script listing and set \"file\" breakpoints.\r\n    - Reload a script after unletting the g:loaded_xxx variable.\r\n    - Mappins to goto next\/previous breakpoint.\r\n    - Fold the contents so that only breakpoints are visible (with some\r\n      context).\r\n    - A command to clear all the breakpoints.\r\n    - A new :BPBrklist command to get the list of breakpoints. You can\r\n      press <F9> on them to disable\/enable them.\r\n    - :BPSave command to save the current breakpoints in a specified global\r\n      variable. You can later exec the variable to reinstate the\r\n      breakpoints. This allows you to save\/restore breakpoints across sessions.\r\n\r\nSee description for more information. Please continue to send in your suggestions\/bug reports etc.\r\n","3":"Number of improvements, thanks to David Fishburn {fishburn at sybase dot org} for feedback\/ideas and help with identifying issues. Note: This version requires Vim 6.2. New features at a glance:\r\n\r\n    - View the list of scripts loaded.\r\n    - View the script listing and set \"file\" breakpoints.\r\n    - Reload a script after unletting the g:loaded_xxx variable.\r\n    - Mappins to goto next\/previous breakpoint.\r\n    - Fold the contents so that only breakpoints are visible (with some\r\n      context).\r\n    - A command to clear all the breakpoints.\r\n    - A new :BPBrklist command to get the list of breakpoints. You can\r\n      press <F9> on them to disable\/enable them.\r\n    - :BPSave command to save the current breakpoints in a specified global\r\n      variable. You can later exec the variable to reinstate the\r\n      breakpoints. This allows you to save\/restore breakpoints across sessions.\r\n\r\nSee description for more information. Please continue to send in your suggestions\/bug reports etc.\r\n","package":"breakpts.vim","4":"breakpts.vim","src_id":"2099","5":"2099","creation_date":"1055967910","6":"1055967910"},{"0":"618","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"breakpts.vim","4":"breakpts.vim","src_id":"1909","5":"1909","creation_date":"1050083266","6":"1050083266"}]},"617":{"script_id":"617","0":"617","script_name":"Adaryn.vim","1":"Adaryn.vim","script_type":"color scheme","2":"color scheme","summary":"A Deep, Sharp color scheme","3":"A Deep, Sharp color scheme","description":"Adaryn - A color scheme named after my daughter, Adaryn. (A-da-rin)\r\nI like deep, sharp colors and this scheme is inspired by Bohdan Vlasyuk\\\\\\'s darkblue.\r\n\r\nThe cterm background is Black since the DarkBlue was just too light.\r\nAlso the cterm colors are very close to a dark  Borland C++ color setup.","4":"Adaryn - A color scheme named after my daughter, Adaryn. (A-da-rin)\r\nI like deep, sharp colors and this scheme is inspired by Bohdan Vlasyuk\\\\\\'s darkblue.\r\n\r\nThe cterm background is Black since the DarkBlue was just too light.\r\nAlso the cterm colors are very close to a dark  Borland C++ color setup.","install_details":"Just drop into your colors folder and enter command:\r\n:colorscheme adaryn","5":"Just drop into your colors folder and enter command:\r\n:colorscheme adaryn","first_name":"Glenn","6":"Glenn","last_name":"Norton","7":"Norton","releases":[{"0":"617","vim_version":"6.0","1":"6.0","script_version":"1.1","2":"1.1","version_comment":"Same as 1.0, but with a LightBlue \"type\"","3":"Same as 1.0, but with a LightBlue \"type\"","package":"adaryn.vim","4":"adaryn.vim","src_id":"1908","5":"1908","creation_date":"1050083085","6":"1050083085"},{"0":"617","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"adaryn.vim","4":"adaryn.vim","src_id":"1907","5":"1907","creation_date":"1050081961","6":"1050081961"}]},"616":{"script_id":"616","0":"616","script_name":"Asciitable.vim","1":"Asciitable.vim","script_type":"utility","2":"utility","summary":"Create an ASCII table in a split window","3":"Create an ASCII table in a split window","description":"I don't even remember why I originally needed this, but it will open up a split and create an ASCII table in decimal, hex, or octal.  Mappings are made to:\r\n<leader>a, <leader>a8, <leader>a10, <leader>ax, and <leader>a16.\r\n\r\nNOTE:  this is only tested on Win2K, and it was not exhaustively tested for different fonts\/character sets.  I'd be curious to know how other platforms react to it.\r\n\r\nThe code to split the window is based on that found in calendar.vim by Yasuhiro Matsumoto.","4":"I don't even remember why I originally needed this, but it will open up a split and create an ASCII table in decimal, hex, or octal.  Mappings are made to:\r\n<leader>a, <leader>a8, <leader>a10, <leader>ax, and <leader>a16.\r\n\r\nNOTE:  this is only tested on Win2K, and it was not exhaustively tested for different fonts\/character sets.  I'd be curious to know how other platforms react to it.\r\n\r\nThe code to split the window is based on that found in calendar.vim by Yasuhiro Matsumoto.","install_details":"Copy asciitable.vim to your plugin directory.","5":"Copy asciitable.vim to your plugin directory.","first_name":"Jeffrey","6":"Jeffrey","last_name":"Harkavy","7":"Harkavy","releases":[{"0":"616","vim_version":"6.0","1":"6.0","script_version":"1.1","2":"1.1","version_comment":"Initial upload","3":"Initial upload","package":"asciitable.vim","4":"asciitable.vim","src_id":"1906","5":"1906","creation_date":"1050045065","6":"1050045065"}]},"615":{"script_id":"615","0":"615","script_name":"ruler.vim","1":"ruler.vim","script_type":"utility","2":"utility","summary":"Inserts a character ruler above the current line","3":"Inserts a character ruler above the current line","description":"In this world of GUI screen design a character-based ruler may not seem altogether useful.  However, when you need to create or verify flat files with fixed-width columns it's certainly helpful.  Yes, yes.  The vim ruler at the bottom will tell you where the cursor is, but that's not always what you need to know.","4":"In this world of GUI screen design a character-based ruler may not seem altogether useful.  However, when you need to create or verify flat files with fixed-width columns it's certainly helpful.  Yes, yes.  The vim ruler at the bottom will tell you where the cursor is, but that's not always what you need to know.","install_details":"Copy to the plugin directory","5":"Copy to the plugin directory","first_name":"Jeffrey","6":"Jeffrey","last_name":"Harkavy","7":"Harkavy","releases":[{"0":"615","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"ruler.vim","4":"ruler.vim","src_id":"1903","5":"1903","creation_date":"1049797571","6":"1049797571"}]},"614":{"script_id":"614","0":"614","script_name":"CRefVim","1":"CRefVim","script_type":"utility","2":"utility","summary":"a C-reference manual especially designed for Vim","3":"a C-reference manual especially designed for Vim","description":"The intention of this project is to provide a C-reference manual that can\r\nbe viewed with Vim and accessed from within Vim. \r\nThe C-reference is a reference, it is NOT a tutorial or a guide on how\r\nto write C-programs. It is a quick reference to the functions and syntax \r\nof the standard C language.\r\n\r\nThere are several ways to specify a word CRefVim should search for in order\r\nto view help:\r\n\r\n  <Leader>cr normal mode:  get help for word under cursor\r\n                           Memory aid cr: (c)-(r)eference\r\n  <Leader>cr visual mode:  get help for visually selected text\r\n                           Memory aid cr: (c)-(r)eference\r\n  <Leader>cw:              prompt for word CRefVim should search for\r\n                           Memory aid cw: (c)-reference (w)hat\r\n  <Leader>cc:              jump to table of contents of the C-reference manual\r\n                           Memory aid cc: (c)-reference (c)ontents\r\n\r\nNote: by default <Leader> is \\, e.g. press \\cr to invoke C-reference\r\n\r\nNote: The best way to search for an operator (++, --, %, ...) is to visually\r\nselect it and press <Leader>cr.\r\n\r\nTo get help do :help crefvimdoc\r\nTo show the C-reference manual do :help crefvim","4":"The intention of this project is to provide a C-reference manual that can\r\nbe viewed with Vim and accessed from within Vim. \r\nThe C-reference is a reference, it is NOT a tutorial or a guide on how\r\nto write C-programs. It is a quick reference to the functions and syntax \r\nof the standard C language.\r\n\r\nThere are several ways to specify a word CRefVim should search for in order\r\nto view help:\r\n\r\n  <Leader>cr normal mode:  get help for word under cursor\r\n                           Memory aid cr: (c)-(r)eference\r\n  <Leader>cr visual mode:  get help for visually selected text\r\n                           Memory aid cr: (c)-(r)eference\r\n  <Leader>cw:              prompt for word CRefVim should search for\r\n                           Memory aid cw: (c)-reference (w)hat\r\n  <Leader>cc:              jump to table of contents of the C-reference manual\r\n                           Memory aid cc: (c)-reference (c)ontents\r\n\r\nNote: by default <Leader> is \\, e.g. press \\cr to invoke C-reference\r\n\r\nNote: The best way to search for an operator (++, --, %, ...) is to visually\r\nselect it and press <Leader>cr.\r\n\r\nTo get help do :help crefvimdoc\r\nTo show the C-reference manual do :help crefvim","install_details":"CRefVim consists of four files, the script 'crefvim.vim', its\r\ndocumentation 'crefvimdoc.txt', the C-reference 'crefvim.txt' and a syntax\r\nfile to extend the standard syntax highlighting for help files called\r\n'help.vim'.\r\n\r\nCopy the script \"crefvim.vim\" to your local plugin-directory\r\n  Unix:    ~\/.vim\/plugin\r\n  Windows: c:\\vimfiles\\plugin\r\n\r\nYou have to add the documentation and the C-reference to Vim's help\r\nsystem. To do this, copy both 'crefvimdoc.txt' and 'crefvim.txt' to\r\nyour local doc-directory:\r\n  Unix:    ~\/.vim\/doc\r\n  Windows: c:\\vimfiles\\doc\r\n\r\nThen start Vim and do:\r\n  :helptags ~\/.vim\/doc   (or :helptags c:\\vimfiles\\doc for Windows)\r\n\r\n\r\nFinally the standard help syntax highlighting must be extended, so that\r\nthe C-reference is viewed correctly. To do so, copy the file 'help.vim' to\r\nyour local after\/syntax directory:\r\n  Unix:    ~\/.vim\/after\/syntax\r\n  Windows: c:\\vimfiles\\after\\syntax\r\n\r\nThis extention of the help syntax file is only active for the C-reference\r\nmanual.\r\n\r\n\r\nThat's all to do.","5":"CRefVim consists of four files, the script 'crefvim.vim', its\r\ndocumentation 'crefvimdoc.txt', the C-reference 'crefvim.txt' and a syntax\r\nfile to extend the standard syntax highlighting for help files called\r\n'help.vim'.\r\n\r\nCopy the script \"crefvim.vim\" to your local plugin-directory\r\n  Unix:    ~\/.vim\/plugin\r\n  Windows: c:\\vimfiles\\plugin\r\n\r\nYou have to add the documentation and the C-reference to Vim's help\r\nsystem. To do this, copy both 'crefvimdoc.txt' and 'crefvim.txt' to\r\nyour local doc-directory:\r\n  Unix:    ~\/.vim\/doc\r\n  Windows: c:\\vimfiles\\doc\r\n\r\nThen start Vim and do:\r\n  :helptags ~\/.vim\/doc   (or :helptags c:\\vimfiles\\doc for Windows)\r\n\r\n\r\nFinally the standard help syntax highlighting must be extended, so that\r\nthe C-reference is viewed correctly. To do so, copy the file 'help.vim' to\r\nyour local after\/syntax directory:\r\n  Unix:    ~\/.vim\/after\/syntax\r\n  Windows: c:\\vimfiles\\after\\syntax\r\n\r\nThis extention of the help syntax file is only active for the C-reference\r\nmanual.\r\n\r\n\r\nThat's all to do.","first_name":"Christian","6":"Christian","last_name":"Habermann","7":"Habermann","releases":[{"0":"614","vim_version":"6.0","1":"6.0","script_version":"1.0.4","2":"1.0.4","version_comment":"- example on how to assign an absolute address to a function pointer added\r\n- hint on volatile qualifier added\r\n- bad tag corrected","3":"- example on how to assign an absolute address to a function pointer added\r\n- hint on volatile qualifier added\r\n- bad tag corrected","package":"crefvim.zip","4":"crefvim.zip","src_id":"3666","5":"3666","creation_date":"1101683637","6":"1101683637"},{"0":"614","vim_version":"6.0","1":"6.0","script_version":"1.0.3","2":"1.0.3","version_comment":"- marker for syntax-highlighting changed from 0xa7 to $ \n  in order to avoid problems with fonts that use        \n  codes > 0x7f as multibyte characters (e.g. Chinese,   \n  Korean, Japanese... fonts)                            \n- two typos fixed                                       \n- three bad tags corrected                              ","3":"- marker for syntax-highlighting changed from 0xa7 to $ \n  in order to avoid problems with fonts that use        \n  codes > 0x7f as multibyte characters (e.g. Chinese,   \n  Korean, Japanese... fonts)                            \n- two typos fixed                                       \n- three bad tags corrected                              ","package":"crefvim.zip","4":"crefvim.zip","src_id":"2801","5":"2801","creation_date":"1078393700","6":"1078393700"},{"0":"614","vim_version":"6.0","1":"6.0","script_version":"1.0.2","2":"1.0.2","version_comment":"some typos fixed","3":"some typos fixed","package":"crefvim.zip","4":"crefvim.zip","src_id":"2604","5":"2604","creation_date":"1071567417","6":"1071567417"},{"0":"614","vim_version":"6.0","1":"6.0","script_version":"1.0.1","2":"1.0.1","version_comment":"- bug-fix in description of installation:\r\n  destination of help.vim is after\/syntax\r\n    Unix:    ~\/.vim\/after\/syntax\r\n    Windows: c:\\vimfiles\\after\\syntax\r\n   (not syntax\/after)\r\n   affected file: crefvimdoc.txt","3":"- bug-fix in description of installation:\r\n  destination of help.vim is after\/syntax\r\n    Unix:    ~\/.vim\/after\/syntax\r\n    Windows: c:\\vimfiles\\after\\syntax\r\n   (not syntax\/after)\r\n   affected file: crefvimdoc.txt","package":"crefvim.zip","4":"crefvim.zip","src_id":"1912","5":"1912","creation_date":"1050212480","6":"1050212480"},{"0":"614","vim_version":"6.0","1":"6.0","script_version":"1.0.0","2":"1.0.0","version_comment":"Initial upload","3":"Initial upload","package":"crefvim.zip","4":"crefvim.zip","src_id":"1899","5":"1899","creation_date":"1049588597","6":"1049588597"}]},"613":{"script_id":"613","0":"613","script_name":"gisdk","1":"gisdk","script_type":"syntax","2":"syntax","summary":"GISDK syntax files for Vim 6.0","3":"GISDK syntax files for Vim 6.0","description":"GISDK is a script language for GIS (Geographical Information Systems) software produced by Caliper. This script intends to profit from the programming editing capabilities of Vim to provide features for developing programs in GISDK, like syntax highlighting, auto completion and tagging. More information can be found in gisdk.readme.\r\n\r\nFor the more curious, some screenshots are available at:\r\nhttp:\/\/carvalho.webhop.net\/gisdk_vim1.png\r\nhttp:\/\/carvalho.webhop.net\/gisdk_vim2.png\r\nhttp:\/\/carvalho.webhop.net\/gisdk_vim3..png\r\n\r\nHave fun! :)","4":"GISDK is a script language for GIS (Geographical Information Systems) software produced by Caliper. This script intends to profit from the programming editing capabilities of Vim to provide features for developing programs in GISDK, like syntax highlighting, auto completion and tagging. More information can be found in gisdk.readme.\r\n\r\nFor the more curious, some screenshots are available at:\r\nhttp:\/\/carvalho.webhop.net\/gisdk_vim1.png\r\nhttp:\/\/carvalho.webhop.net\/gisdk_vim2.png\r\nhttp:\/\/carvalho.webhop.net\/gisdk_vim3..png\r\n\r\nHave fun! :)","install_details":"Extract the files and just copy gisdk.vim to the *syntax* folder under Vim runtime folder, and gisdk_ftp.vim and gisdk.dict to the *ftplugin* folder. Rename gisdk_ftp.vim to gisdk.vim. Edit filetype.vim in the runtime folder for the GISDK resource files to be recognized accordingly. Please see file gisdk.readme for details in the installation.","5":"Extract the files and just copy gisdk.vim to the *syntax* folder under Vim runtime folder, and gisdk_ftp.vim and gisdk.dict to the *ftplugin* folder. Rename gisdk_ftp.vim to gisdk.vim. Edit filetype.vim in the runtime folder for the GISDK resource files to be recognized accordingly. Please see file gisdk.readme for details in the installation.","first_name":"Luis","6":"Luis","last_name":"Carvalho","7":"Carvalho","releases":[{"0":"613","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"gisdk_vim.zip","4":"gisdk_vim.zip","src_id":"1898","5":"1898","creation_date":"1049574523","6":"1049574523"}]},"612":{"script_id":"612","0":"612","script_name":"cpp.vim","1":"cpp.vim","script_type":"syntax","2":"syntax","summary":"Syntaxhighlightning for Qt sources","3":"Syntaxhighlightning for Qt sources","description":"All Qt-classes are highlighted like built-in types.\r\nAlso Qt-keywords and Qt-macros are highlighted.\r\n","4":"All Qt-classes are highlighted like built-in types.\r\nAlso Qt-keywords and Qt-macros are highlighted.\r\n","install_details":"create a directory $HOME\/.vim\/after\/syntax\r\nCopy cpp.vim into that directory","5":"create a directory $HOME\/.vim\/after\/syntax\r\nCopy cpp.vim into that directory","first_name":"Dieter","6":"Dieter","last_name":"Hartmann","7":"Hartmann","releases":[{"0":"612","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"cpp.vim","4":"cpp.vim","src_id":"1896","5":"1896","creation_date":"1049437996","6":"1049437996"}]},"611":{"script_id":"611","0":"611","script_name":"dante.vim","1":"dante.vim","script_type":"color scheme","2":"color scheme","summary":"dark color scheme","3":"dark color scheme","description":"A good dark color scheme\r\n","4":"A good dark color scheme\r\n","install_details":"copy to $HOME\/.vim\/colors\r\n:colorscheme dante","5":"copy to $HOME\/.vim\/colors\r\n:colorscheme dante","first_name":"C","6":"C","last_name":"Mach","7":"Mach","releases":[{"0":"611","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"dante.vim","4":"dante.vim","src_id":"1891","5":"1891","creation_date":"1049363660","6":"1049363660"}]},"610":{"script_id":"610","0":"610","script_name":"ctags.vim","1":"ctags.vim","script_type":"utility","2":"utility","summary":"Display function name in the title bar and\/or the status line","3":"Display function name in the title bar and\/or the status line","description":"This is a new version of Alexey Marinichev\\'s ctags.vim script, vimscript #12. I have modified it with the author\\'s permission, but cannot upload it as a new version of the original script because Vim Online now allows only the original author to do that.\r\n\r\nThe original script used exuberant ctags to build a list of tags for the current file and displayed the name of the function the cursor was in (actually the name of the tag at or above the cursor\\'s line) in the title bar.\r\n\r\nThis version has been modified to display the function\/tag name in the status line instead of or in addtion to the title bar.  If multiple windows are open, the correct function\/tag name is displayed in each status line. The script has also been modified to be a plugin instead of having to be sourced. Finally, since exuberant ctags now supports Python and Vim languages as well as C, .py and .vim were added to the list of suffixes that automatically start the script.\r\n\r\nNew in Version 2.1\r\n------------------\r\n\r\n1.  Keith Reynolds contributed some changes that have made a dramatic improvement in the startup time when opening large files containing many tags.  The improvement is greatest when using a vim compiled with Perl support.  His changes also result in this version using less memory than version 2.0.\r\n\r\n2.  Keith also added automatic enabling of the status line (i.e., setting 'statusline' to 2) when entering a buffer in which the script is active.\r\n\r\n3.  The default g:ctags_args value has been changed to use C and vim type values more appropriate for this plugin.  If you prefer the previous defaults, the values are still noted in the script and can be used instead by setting them yourself in your ~\/.vimrc.\r\n\r\n4.  The default g:ctags_path value has been changed to be better for most users.  This can also be reverted to the previous default value by looking in the script for the previous setting and putting this in your ~\/.vimrc.\r\n\r\n5.  The ctags database is now regenerated every time a buffer is saved.  This keeps the database up to date as a file is changed.  If this is a performance problem for you, just add\r\n\r\n        let g:ctags_regenerate = 0\r\n\r\nto your ~\/.vimrc.\r\n\r\n6.  The behavior of the cursor when moving vertically through text has been improved.  It no longer \"forgets\" the column to which it was last set as often.  It may forget now only when the tag name changes.\r\n\r\n7.  Configuration varaibles may now be set at any time, not just at vim startup time.\r\n","4":"This is a new version of Alexey Marinichev\\'s ctags.vim script, vimscript #12. I have modified it with the author\\'s permission, but cannot upload it as a new version of the original script because Vim Online now allows only the original author to do that.\r\n\r\nThe original script used exuberant ctags to build a list of tags for the current file and displayed the name of the function the cursor was in (actually the name of the tag at or above the cursor\\'s line) in the title bar.\r\n\r\nThis version has been modified to display the function\/tag name in the status line instead of or in addtion to the title bar.  If multiple windows are open, the correct function\/tag name is displayed in each status line. The script has also been modified to be a plugin instead of having to be sourced. Finally, since exuberant ctags now supports Python and Vim languages as well as C, .py and .vim were added to the list of suffixes that automatically start the script.\r\n\r\nNew in Version 2.1\r\n------------------\r\n\r\n1.  Keith Reynolds contributed some changes that have made a dramatic improvement in the startup time when opening large files containing many tags.  The improvement is greatest when using a vim compiled with Perl support.  His changes also result in this version using less memory than version 2.0.\r\n\r\n2.  Keith also added automatic enabling of the status line (i.e., setting 'statusline' to 2) when entering a buffer in which the script is active.\r\n\r\n3.  The default g:ctags_args value has been changed to use C and vim type values more appropriate for this plugin.  If you prefer the previous defaults, the values are still noted in the script and can be used instead by setting them yourself in your ~\/.vimrc.\r\n\r\n4.  The default g:ctags_path value has been changed to be better for most users.  This can also be reverted to the previous default value by looking in the script for the previous setting and putting this in your ~\/.vimrc.\r\n\r\n5.  The ctags database is now regenerated every time a buffer is saved.  This keeps the database up to date as a file is changed.  If this is a performance problem for you, just add\r\n\r\n        let g:ctags_regenerate = 0\r\n\r\nto your ~\/.vimrc.\r\n\r\n6.  The behavior of the cursor when moving vertically through text has been improved.  It no longer \"forgets\" the column to which it was last set as often.  It may forget now only when the tag name changes.\r\n\r\n7.  Configuration varaibles may now be set at any time, not just at vim startup time.\r\n","install_details":"Copy ctags.vim to your plugin directory.\r\n\r\nIf the ctags program is not in your PATH, you will need to add the following to your vimrc:\r\n\r\n    let g:ctags_path=<path to your ctags>\r\n\r\nand to enable the display of function names in the status line, you will need to add this:\r\n\r\n    let g:ctags_statusline=1\r\n\r\nOther configuration variables you may want to change are:\r\n\r\n    g:ctags_args\r\n        Additional arguments to the ctags program.\r\n\r\n    g:ctags_title\r\n        Set to 1 if you want the function name also displayed in the title bar.\r\n        This is the default, but if g:ctags_statusline is set to 1, this must also be\r\n        set to one to show the function name in the title bar. Otherwise, the\r\n        function name appears only in the status line.\r\n\r\n    generate_tags\r\n        Set to 1 if you want the script to be started automatically for the supported\r\n        file types (actually file extensions). Otherwise the script must be started\r\n        manually with the CTAGS command.\r\n\r\n    g:ctags_regenerate\r\n        Set to 0 if you don't want the tags database rebuilt each time\r\n        the buffer is written.","5":"Copy ctags.vim to your plugin directory.\r\n\r\nIf the ctags program is not in your PATH, you will need to add the following to your vimrc:\r\n\r\n    let g:ctags_path=<path to your ctags>\r\n\r\nand to enable the display of function names in the status line, you will need to add this:\r\n\r\n    let g:ctags_statusline=1\r\n\r\nOther configuration variables you may want to change are:\r\n\r\n    g:ctags_args\r\n        Additional arguments to the ctags program.\r\n\r\n    g:ctags_title\r\n        Set to 1 if you want the function name also displayed in the title bar.\r\n        This is the default, but if g:ctags_statusline is set to 1, this must also be\r\n        set to one to show the function name in the title bar. Otherwise, the\r\n        function name appears only in the status line.\r\n\r\n    generate_tags\r\n        Set to 1 if you want the script to be started automatically for the supported\r\n        file types (actually file extensions). Otherwise the script must be started\r\n        manually with the CTAGS command.\r\n\r\n    g:ctags_regenerate\r\n        Set to 0 if you don't want the tags database rebuilt each time\r\n        the buffer is written.","first_name":"Gary","6":"Gary","last_name":"Johnson","7":"Johnson","releases":[{"0":"610","vim_version":"6.0","1":"6.0","script_version":"2.1","2":"2.1","version_comment":"Improved the startup time and memory usage.  Automatically turn the status line on when displaying the tag name in the status line.  Both of those features were contributed by Keith Reynolds.  Changed the types of tags displayed for C and vim files.  Added updating of the ctags database when a file is written.  Mostly fixed a problem where the script caused the cursor to not remember its column position as it was moved vertically.  Details on the script page.","3":"Improved the startup time and memory usage.  Automatically turn the status line on when displaying the tag name in the status line.  Both of those features were contributed by Keith Reynolds.  Changed the types of tags displayed for C and vim files.  Added updating of the ctags database when a file is written.  Mostly fixed a problem where the script caused the cursor to not remember its column position as it was moved vertically.  Details on the script page.","package":"ctags.vim","4":"ctags.vim","src_id":"2529","5":"2529","creation_date":"1070111285","6":"1070111285"},{"0":"610","vim_version":"6.0","1":"6.0","script_version":"2.0","2":"2.0","version_comment":"Initial upload","3":"Initial upload","package":"ctags.vim","4":"ctags.vim","src_id":"1888","5":"1888","creation_date":"1049318786","6":"1049318786"}]},"609":{"script_id":"609","0":"609","script_name":"Qt.vim","1":"Qt.vim","script_type":"utility","2":"utility","summary":"tiny tool for the uic used in Qt from Trolltech","3":"tiny tool for the uic used in Qt from Trolltech","description":"only for unix\/linux\r\n\r\nAnyone who uses Trolltech's fabulous Toolkit Qt is able to generate cpp\/h files using the xml Files generated by the Qt-Desginer. \r\nBy using an additional inheriting instance your can make your layout code ( the ui\/cpp\/h files in the basedir) independant from your implementation code ( the classImpl.ccp and classImpl.h in your pwd).\r\nThats what this little script does.\r\nAdditionally it makes a pro-file for qmake.\r\nThe plugin appears in your menubar as Plugin\/QT\r\n\r\n- create a new dir\r\n- start your editor : gvim myfile.ui\r\n- Plugin\/QT\/UIC subImpl -> creates a base directory with .cpp\/.h\/.ui file -> a subdeclaration with the .cpp\/.h files -> main.ccp and a pro-file. If your want it will run qmake, make and executes the resulting program.\r\n\r\n- Plugin\/QT\/UIC Impl creates only the .cpp und .h from your .ui file\r\n\r\n- Manpageview for qt classes: type for example :Man QString and see how it works. You can also type K when your coursor is over a qt class name.\r\n\r\nSuggestions are welcome.","4":"only for unix\/linux\r\n\r\nAnyone who uses Trolltech's fabulous Toolkit Qt is able to generate cpp\/h files using the xml Files generated by the Qt-Desginer. \r\nBy using an additional inheriting instance your can make your layout code ( the ui\/cpp\/h files in the basedir) independant from your implementation code ( the classImpl.ccp and classImpl.h in your pwd).\r\nThats what this little script does.\r\nAdditionally it makes a pro-file for qmake.\r\nThe plugin appears in your menubar as Plugin\/QT\r\n\r\n- create a new dir\r\n- start your editor : gvim myfile.ui\r\n- Plugin\/QT\/UIC subImpl -> creates a base directory with .cpp\/.h\/.ui file -> a subdeclaration with the .cpp\/.h files -> main.ccp and a pro-file. If your want it will run qmake, make and executes the resulting program.\r\n\r\n- Plugin\/QT\/UIC Impl creates only the .cpp und .h from your .ui file\r\n\r\n- Manpageview for qt classes: type for example :Man QString and see how it works. You can also type K when your coursor is over a qt class name.\r\n\r\nSuggestions are welcome.","install_details":"Put it into your ~\/.vim\/plugin directory. ","5":"Put it into your ~\/.vim\/plugin directory. ","first_name":"Dieter","6":"Dieter","last_name":"Hartmann","7":"Hartmann","releases":[{"0":"609","vim_version":"6.0","1":"6.0","script_version":"0.4","2":"0.4","version_comment":"- add a manpageview for qt classes in a additional buffer\r\n(thanks to Charles E. Campbell, Jr. see script manpageview.vim)\r\n- when program is compiled it starts up immediately\r\n- bug fixes","3":"- add a manpageview for qt classes in a additional buffer\r\n(thanks to Charles E. Campbell, Jr. see script manpageview.vim)\r\n- when program is compiled it starts up immediately\r\n- bug fixes","package":"Qt.vim","4":"Qt.vim","src_id":"1905","5":"1905","creation_date":"1049987576","6":"1049987576"},{"0":"609","vim_version":"6.0","1":"6.0","script_version":"0.3","2":"0.3","version_comment":"check far a valid ui-file","3":"check far a valid ui-file","package":"Qt.vim","4":"Qt.vim","src_id":"1895","5":"1895","creation_date":"1049436530","6":"1049436530"},{"0":"609","vim_version":"6.0","1":"6.0","script_version":"0.2","2":"0.2","version_comment":"a few fixes about the $QTDIR environment , the working directory and handling of existing directory\/files","3":"a few fixes about the $QTDIR environment , the working directory and handling of existing directory\/files","package":"Qt.vim","4":"Qt.vim","src_id":"1894","5":"1894","creation_date":"1049377387","6":"1049377387"},{"0":"609","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"Qt.vim","4":"Qt.vim","src_id":"1886","5":"1886","creation_date":"1049260669","6":"1049260669"}]},"608":{"script_id":"608","0":"608","script_name":"toc.vim","1":"toc.vim","script_type":"syntax","2":"syntax","summary":"Syntax file for TOC files","3":"Syntax file for TOC files","description":"Syntax file for TOC files as described in CDRDAO(1).","4":"Syntax file for TOC files as described in CDRDAO(1).","install_details":"Just copy the file into your syntax directory.","5":"Just copy the file into your syntax directory.","first_name":"Florian","6":"Florian","last_name":"Forster","7":"Forster","releases":[{"0":"608","vim_version":"6.0","1":"6.0","script_version":"0.01","2":"0.01","version_comment":"Initial upload","3":"Initial upload","package":"toc.vim","4":"toc.vim","src_id":"1885","5":"1885","creation_date":"1049243614","6":"1049243614"}]},"607":{"script_id":"607","0":"607","script_name":"valgrind.vim","1":"valgrind.vim","script_type":"utility","2":"utility","summary":"Navigate in the output of the memory checker valgrind","3":"Navigate in the output of the memory checker valgrind","description":"Valgrind (http:\/\/developer.kde.org\/~sewardj\/) is an open-source memory debugger for x86-GNU\/Linux. This script allows you to start valgrind from vim and easily jump to error it reports.\r\n\r\nThe script output is not very beautiful yet, but I find it already useful.\r\n\r\nSee the comments in the beginning of the script for some documentation.","4":"Valgrind (http:\/\/developer.kde.org\/~sewardj\/) is an open-source memory debugger for x86-GNU\/Linux. This script allows you to start valgrind from vim and easily jump to error it reports.\r\n\r\nThe script output is not very beautiful yet, but I find it already useful.\r\n\r\nSee the comments in the beginning of the script for some documentation.","install_details":"Just copy the file to ~\/.vim\/plugin and it should work.","5":"Just copy the file to ~\/.vim\/plugin and it should work.","first_name":"Rainer M.","6":"Rainer M.","last_name":"Schmid","7":"Schmid","releases":[{"0":"607","vim_version":"6.0","1":"6.0","script_version":"1.2","2":"1.2","version_comment":"Initial upload","3":"Initial upload","package":"valgrind.vim","4":"valgrind.vim","src_id":"1881","5":"1881","creation_date":"1049072676","6":"1049072676"}]},"606":{"script_id":"606","0":"606","script_name":"asmMIPS","1":"asmMIPS","script_type":"syntax","2":"syntax","summary":"MIPS specific assembly syntax (MAL)","3":"MIPS specific assembly syntax (MAL)","description":"Highlights MIPS assembly keywords, registers, labels, constants etc..","4":"Highlights MIPS assembly keywords, registers, labels, constants etc..","install_details":"copy this file into your syntax folder and add the following line in your .gvimrc\r\n\r\nautocmd BufNewFile,BufRead *.s :cal SetSyn(\"asmMIPS\") \r\n","5":"copy this file into your syntax folder and add the following line in your .gvimrc\r\n\r\nautocmd BufNewFile,BufRead *.s :cal SetSyn(\"asmMIPS\") \r\n","first_name":"Syed","6":"Syed","last_name":"Ali","7":"Ali","releases":[{"0":"606","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"asmMIPS.vim","4":"asmMIPS.vim","src_id":"1870","5":"1870","creation_date":"1048812567","6":"1048812567"}]},"605":{"script_id":"605","0":"605","script_name":"cream-numberlines","1":"cream-numberlines","script_type":"utility","2":"utility","summary":"Number lines of a selection","3":"Number lines of a selection","description":"\r\nFeatures:\r\n\r\no Dialog prompt for optional start number. (Default is actual line number.)\r\n\r\no Column of numbers is right justified.\r\n\r\n\r\nUsage:\r\n\r\no Must be called from visual mode (with a selection).\r\n\r\no Required argument indicates mode, only \"v\" (visual) allowed.\r\n\r\no Example mapping:\r\n\r\n    vmap <silent> <F12> :<C-u>call Cream_number_lines(\"v\")\r\n\r\n\r\nThis is one of many custom utilities and functions for gVim from the Cream project (http:\/\/cream.sourceforge.net), a configuration of Vim for those of us familiar with Apple and Windows software.\r\n\r\n\r\n","4":"\r\nFeatures:\r\n\r\no Dialog prompt for optional start number. (Default is actual line number.)\r\n\r\no Column of numbers is right justified.\r\n\r\n\r\nUsage:\r\n\r\no Must be called from visual mode (with a selection).\r\n\r\no Required argument indicates mode, only \"v\" (visual) allowed.\r\n\r\no Example mapping:\r\n\r\n    vmap <silent> <F12> :<C-u>call Cream_number_lines(\"v\")\r\n\r\n\r\nThis is one of many custom utilities and functions for gVim from the Cream project (http:\/\/cream.sourceforge.net), a configuration of Vim for those of us familiar with Apple and Windows software.\r\n\r\n\r\n","install_details":"\r\nDrop this file into your plugins directory and (re)start Vim.\r\n\r\n","5":"\r\nDrop this file into your plugins directory and (re)start Vim.\r\n\r\n","first_name":"Steve","6":"Steve","last_name":"Hall","7":"Hall","releases":[{"0":"605","vim_version":"6.0","1":"6.0","script_version":"0.2","2":"0.2","version_comment":"Adjusted to not include last line of selection if cursor is in column 1.","3":"Adjusted to not include last line of selection if cursor is in column 1.","package":"cream-numberlines.vim","4":"cream-numberlines.vim","src_id":"1869","5":"1869","creation_date":"1048763991","6":"1048763991"},{"0":"605","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"cream-numberlines.vim","4":"cream-numberlines.vim","src_id":"1868","5":"1868","creation_date":"1048757525","6":"1048757525"}]},"604":{"script_id":"604","0":"604","script_name":"php.vim (html enhanced)","1":"php.vim (html enhanced)","script_type":"indent","2":"indent","summary":"combination of the php indent file and the html indent file","3":"combination of the php indent file and the html indent file","description":"This is a combination of the PHP indent file by Miles Lott with the HTML indent file by Johannes Zellner. Usefull for editing php-files with html parts in it which is a typical job for webdesigners","4":"This is a combination of the PHP indent file by Miles Lott with the HTML indent file by Johannes Zellner. Usefull for editing php-files with html parts in it which is a typical job for webdesigners","install_details":"","5":"","first_name":"Pim","6":"Pim","last_name":"Snel","7":"Snel","releases":[{"0":"604","vim_version":"6.0","1":"6.0","script_version":"0.3","2":"0.3","version_comment":"Fixed wrong indention when a php-tag is opened and closed on the same line","3":"Fixed wrong indention when a php-tag is opened and closed on the same line","package":"php.vim","4":"php.vim","src_id":"2863","5":"2863","creation_date":"1080202464","6":"1080202464"},{"0":"604","vim_version":"6.0","1":"6.0","script_version":"0.2","2":"0.2","version_comment":"Changes:\n- applied patch from Holger Dzeik\n- added changelog\n- added default indention of 3 spaces after the <?php for better reading\n- replaced URL\n- reformatted the options section","3":"Changes:\n- applied patch from Holger Dzeik\n- added changelog\n- added default indention of 3 spaces after the <?php for better reading\n- replaced URL\n- reformatted the options section","package":"php.vim","4":"php.vim","src_id":"2771","5":"2771","creation_date":"1077519979","6":"1077519979"},{"0":"604","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"php.vim","4":"php.vim","src_id":"1863","5":"1863","creation_date":"1048750683","6":"1048750683"}]},"603":{"script_id":"603","0":"603","script_name":"oceanblack.vim","1":"oceanblack.vim","script_type":"color scheme","2":"color scheme","summary":"dark scheme (soft blue\/green on black), easy on the eyes","3":"dark scheme (soft blue\/green on black), easy on the eyes","description":"variation on Tom Regner's oceandeep colorfile.\r\n\r\nsee sample at https:\/\/github.com\/chrisv\/vim-chrisv\/blob\/master\/colors\/oceanblack-sample.png\r\n\r\npublic repo for this script:\r\n\r\nhttp:\/\/github.com\/chrisv\/vim-chrisv ","4":"variation on Tom Regner's oceandeep colorfile.\r\n\r\nsee sample at https:\/\/github.com\/chrisv\/vim-chrisv\/blob\/master\/colors\/oceanblack-sample.png\r\n\r\npublic repo for this script:\r\n\r\nhttp:\/\/github.com\/chrisv\/vim-chrisv ","install_details":"put in your \/colors directory, then \r\n\r\n:colorscheme oceanblack","5":"put in your \/colors directory, then \r\n\r\n:colorscheme oceanblack","first_name":"Chris","6":"Chris","last_name":"Vertonghen","7":"Vertonghen","releases":[{"0":"603","vim_version":"6.0","1":"6.0","script_version":"0.2","2":"0.2","version_comment":"cleaner colors\/bg for numbers, comments; deleted some bolding","3":"cleaner colors\/bg for numbers, comments; deleted some bolding","package":"oceanblack.vim","4":"oceanblack.vim","src_id":"1904","5":"1904","creation_date":"1049875294","6":"1049875294"},{"0":"603","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"oceanblack.vim","4":"oceanblack.vim","src_id":"1852","5":"1852","creation_date":"1048527745","6":"1048527745"}]},"602":{"script_id":"602","0":"602","script_name":"vimbadword.sh","1":"vimbadword.sh","script_type":"utility","2":"utility","summary":"outputs the first misspelled word on the status line","3":"outputs the first misspelled word on the status line","description":"This script merely outputs the first misspelled word in the current file on the status line.\r\n\r\nIt needs aspell but should work with any speller that can output a (unsorted) list of badwords.","4":"This script merely outputs the first misspelled word in the current file on the status line.\r\n\r\nIt needs aspell but should work with any speller that can output a (unsorted) list of badwords.","install_details":"Move vimspell.sh to somewhere in your PATH\r\nAdd something like this\r\n  map <F7> :so `vimbadword.sh %`<CR>\r\n  to your vimrc","5":"Move vimspell.sh to somewhere in your PATH\r\nAdd something like this\r\n  map <F7> :so `vimbadword.sh %`<CR>\r\n  to your vimrc","first_name":"Thomas","6":"Thomas","last_name":"Sutton","7":"Sutton","releases":[{"0":"602","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"vimbadword.sh","4":"vimbadword.sh","src_id":"1851","5":"1851","creation_date":"1048523853","6":"1048523853"}]},"601":{"script_id":"601","0":"601","script_name":"vimwc.sh","1":"vimwc.sh","script_type":"utility","2":"utility","summary":"a script for running wc nicely","3":"a script for running wc nicely","description":"I use this script mapped to <F12>. It outputs the current wordcount to the \\\\\\'status bar\\\\\\' thus aleviating the ever annoying \\\\\\'Press enter\\\\\\' prompt after using :!","4":"I use this script mapped to <F12>. It outputs the current wordcount to the \\\\\\'status bar\\\\\\' thus aleviating the ever annoying \\\\\\'Press enter\\\\\\' prompt after using :!","install_details":"Put vimwc.sh somewhere in your PATH\r\nEdit vimwc.sh for your configuration (use mktemp or PID)\r\nAdd something along the lines of \r\n    map <F8> :so `vimwc.sh %`<CR> ","5":"Put vimwc.sh somewhere in your PATH\r\nEdit vimwc.sh for your configuration (use mktemp or PID)\r\nAdd something along the lines of \r\n    map <F8> :so `vimwc.sh %`<CR> ","first_name":"Thomas","6":"Thomas","last_name":"Sutton","7":"Sutton","releases":[{"0":"601","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"vimwc.sh","4":"vimwc.sh","src_id":"1850","5":"1850","creation_date":"1048523429","6":"1048523429"}]},"600":{"script_id":"600","0":"600","script_name":"cmake.vim","1":"cmake.vim","script_type":"syntax","2":"syntax","summary":"CMake syntax highlighting","3":"CMake syntax highlighting","description":"A CMake (www.cmake.org) syntax highlighting mode, which understands most of commands, reports depricated commands, highlights common arguments, strings, environment variables, registry entries, variable references.","4":"A CMake (www.cmake.org) syntax highlighting mode, which understands most of commands, reports depricated commands, highlights common arguments, strings, environment variables, registry entries, variable references.","install_details":"1. Put in indent\/ subdirectory (for example: ~\/.vim\/syntax)\r\n2. load it when loading CMakeLists.txt or *.cmake:\r\n:autocmd BufRead,BufNewFile *.cmake,CMakeLists.txt setf cmake\r\n ","5":"1. Put in indent\/ subdirectory (for example: ~\/.vim\/syntax)\r\n2. load it when loading CMakeLists.txt or *.cmake:\r\n:autocmd BufRead,BufNewFile *.cmake,CMakeLists.txt setf cmake\r\n ","first_name":"Andy","6":"Andy","last_name":"Cedilnik","7":"Cedilnik","releases":[{"0":"600","vim_version":"6.0","1":"6.0","script_version":"1.4","2":"1.4","version_comment":"Cleanup before VIM 7.0. Also, make sure commands are case insensitive, add support for more commands and operators.","3":"Cleanup before VIM 7.0. Also, make sure commands are case insensitive, add support for more commands and operators.","package":"cmake-syntax.vim","4":"cmake-syntax.vim","src_id":"5584","5":"5584","creation_date":"1145449472","6":"1145449472"},{"0":"600","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"cmake.vim","4":"cmake.vim","src_id":"1849","5":"1849","creation_date":"1048503233","6":"1048503233"}]},"599":{"script_id":"599","0":"599","script_name":"cmake.vim","1":"cmake.vim","script_type":"indent","2":"indent","summary":"CMake indent file","3":"CMake indent file","description":"A CMake (www.cmake.org) indentation mode, which indents IF()\/ELSE()\/ENDIF(), FOREACH()\/ENDFOREACH(), and MACRO()\/ENDMACRO(), and it also supports multiline arguments to commands, quoted and non-quoted arguments.","4":"A CMake (www.cmake.org) indentation mode, which indents IF()\/ELSE()\/ENDIF(), FOREACH()\/ENDFOREACH(), and MACRO()\/ENDMACRO(), and it also supports multiline arguments to commands, quoted and non-quoted arguments.","install_details":"1. Put in indent\/ subdirectory (for example: ~\/.vim\/indent)\r\n2. load it when loading CMakeLists.txt or *.cmake:\r\n:autocmd BufRead,BufNewFile *.cmake,CMakeLists.txt runtime! indent\/cmake.vim\r\n","5":"1. Put in indent\/ subdirectory (for example: ~\/.vim\/indent)\r\n2. load it when loading CMakeLists.txt or *.cmake:\r\n:autocmd BufRead,BufNewFile *.cmake,CMakeLists.txt runtime! indent\/cmake.vim\r\n","first_name":"Andy","6":"Andy","last_name":"Cedilnik","7":"Cedilnik","releases":[{"0":"599","vim_version":"6.0","1":"6.0","script_version":"1.4","2":"1.4","version_comment":"More cleanups before VIM 7.0","3":"More cleanups before VIM 7.0","package":"cmake-indent.vim","4":"cmake-indent.vim","src_id":"5583","5":"5583","creation_date":"1145449327","6":"1145449327"},{"0":"599","vim_version":"6.0","1":"6.0","script_version":"0.2","2":"0.2","version_comment":"Lots of changes here. Now it can handle all CMake files I can find on my disk. This one also uses same logic as the emacs file in the CMake repository.","3":"Lots of changes here. Now it can handle all CMake files I can find on my disk. This one also uses same logic as the emacs file in the CMake repository.","package":"cmake.vim","4":"cmake.vim","src_id":"2102","5":"2102","creation_date":"1056023230","6":"1056023230"},{"0":"599","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"cmake.vim","4":"cmake.vim","src_id":"1848","5":"1848","creation_date":"1048502993","6":"1048502993"}]},"598":{"script_id":"598","0":"598","script_name":"execmap","1":"execmap","script_type":"utility","2":"utility","summary":"Lets you relax while executing long normal or visual mode maps","3":"Lets you relax while executing long normal or visual mode maps","description":"Description:\r\n  The aim of this plugin is to allow users to define lengthy normal mode\r\n  mappings (and thus increase the name-space) and still be able to type the\r\n  mappings comfortably, thus reducing the chance of making mistakes or\r\n  getting timed out. When you make mistakes in typing (resulting in an\r\n  invalid map) or pause for long enough, the control goes to the plugin\r\n  instead of getting aborted, which then prompts you to continue typing or\r\n  correct the map, without needing to start all over.\r\n                                                                             \r\n  The plugin provided a generic functions called ExecMap() and ExecMap2()\r\n  which need to be defined as the handler for the set of maps starting with\r\n  a common prefix. It by default defines this as the handler for the prefix\r\n  \"\\\" and \"_\" (without the quotes) so that for all the mappings that start\r\n  with these prefixes, the plugin provides a backup on errors and time out\r\n  cases. But you can define additional mappings for additional prefixes such\r\n  as \",\" etc.\r\n                                                                             \r\n      nnoremap , :call ExecMap(',')<CR>\r\n                                                                             \r\n  As you enter key strokes to complete a command, the plugin looks up the\r\n  partial command in the complete list of normal or visual mode mapping (as\r\n  the per the case) and rejects the key strokes if it doesn't match with\r\n  any. When the command matches an existing map with no conflicts, it gets\r\n  immediately executed. When the command matches a map, but there is a\r\n  longer map that could be matched, the plugin indicates this by displaying\r\n  a \"*\" at which point you can press <Enter> to execute the map, or continue\r\n  to type to match the longer command. Here is an example to describe it\r\n  better, say you have two maps as below:\r\n                                                                             \r\n      nnoremap \\ma :echo \"ma\"<CR>\r\n      nnoremap \\maxi :echo \"maxi\"<CR>\r\n                                                                             \r\n  Typing \"\\ma\" would match one of the mappings completely, but it would also\r\n  match \"\\maxi\" partially, so the plugin allows you to continue to type\r\n  until you press <CR>. However, whenever there is an exact match for the\r\n  current command with an existing map, the plugin indicates it by appending\r\n  a \"*\" to the prompt (pressing <CR> at that moment would execute a valid\r\n  command). I have found it working well for both normal and visual mode\r\n  mappings.\r\n                                                                             \r\n  You can use <BS> to clear the previous character and press <Esc> or <C-C>\r\n  to cancel it anytime. You can also press <Enter> to execute the command\r\n  that is typed in, but it has to match a valid map.\r\n                                                                             \r\n  Note that this functionality was originally part of genutils plugin, but\r\n  it is more appropriate for it to be a separate plugin rather than a\r\n  library function so it is no longer part of genutils.\r\n                                                                             \r\nFunction Prototypes:\r\n    \" Add a handler for all the maps that share the given prefix in\r\n    \"\t  normal mode.\r\n    void ExecMap(String prefix)\r\n                                                                             \r\n    \" Add a handler for all the maps that share the given prefix in\r\n    \"\t  the given mode. Only normal and visual modes are supported.\r\n    void ExecMap2(String prefix, String mode)\r\n                                                                             \r\n    \" Prompt user for a map with the given prefix in the given mode and\r\n    \"\t  return the map. The return value could be executed using :normal\r\n    \"\t  command. If the user cancels the operation, it returns an empty\r\n    \"\t  string. Only normal and visual modes are supported.\r\n    String ExecMapPrompt(String prefix, String mode)\r\nLimitations:\r\n  - You can only execute maps that are complete to be executable using\r\n    :normal exmode command (see help on :normal). One example map that will\r\n    not work is:\r\n                                                                             \r\n      nnoremap _ab :call input('ab command')<CR>\r\n                                                                             \r\n    If you execute the above command using \":normal _ab\", it will not run as\r\n    expected. Similarly, maps that are supposed to leave you on the : prompt\r\n    don't work as well.\r\n\r\n\r\n\r\nSearch_key_words: execmap execmap.vim normal visual mode map maps genutils relax comfort Hari Krishna Dara","4":"Description:\r\n  The aim of this plugin is to allow users to define lengthy normal mode\r\n  mappings (and thus increase the name-space) and still be able to type the\r\n  mappings comfortably, thus reducing the chance of making mistakes or\r\n  getting timed out. When you make mistakes in typing (resulting in an\r\n  invalid map) or pause for long enough, the control goes to the plugin\r\n  instead of getting aborted, which then prompts you to continue typing or\r\n  correct the map, without needing to start all over.\r\n                                                                             \r\n  The plugin provided a generic functions called ExecMap() and ExecMap2()\r\n  which need to be defined as the handler for the set of maps starting with\r\n  a common prefix. It by default defines this as the handler for the prefix\r\n  \"\\\" and \"_\" (without the quotes) so that for all the mappings that start\r\n  with these prefixes, the plugin provides a backup on errors and time out\r\n  cases. But you can define additional mappings for additional prefixes such\r\n  as \",\" etc.\r\n                                                                             \r\n      nnoremap , :call ExecMap(',')<CR>\r\n                                                                             \r\n  As you enter key strokes to complete a command, the plugin looks up the\r\n  partial command in the complete list of normal or visual mode mapping (as\r\n  the per the case) and rejects the key strokes if it doesn't match with\r\n  any. When the command matches an existing map with no conflicts, it gets\r\n  immediately executed. When the command matches a map, but there is a\r\n  longer map that could be matched, the plugin indicates this by displaying\r\n  a \"*\" at which point you can press <Enter> to execute the map, or continue\r\n  to type to match the longer command. Here is an example to describe it\r\n  better, say you have two maps as below:\r\n                                                                             \r\n      nnoremap \\ma :echo \"ma\"<CR>\r\n      nnoremap \\maxi :echo \"maxi\"<CR>\r\n                                                                             \r\n  Typing \"\\ma\" would match one of the mappings completely, but it would also\r\n  match \"\\maxi\" partially, so the plugin allows you to continue to type\r\n  until you press <CR>. However, whenever there is an exact match for the\r\n  current command with an existing map, the plugin indicates it by appending\r\n  a \"*\" to the prompt (pressing <CR> at that moment would execute a valid\r\n  command). I have found it working well for both normal and visual mode\r\n  mappings.\r\n                                                                             \r\n  You can use <BS> to clear the previous character and press <Esc> or <C-C>\r\n  to cancel it anytime. You can also press <Enter> to execute the command\r\n  that is typed in, but it has to match a valid map.\r\n                                                                             \r\n  Note that this functionality was originally part of genutils plugin, but\r\n  it is more appropriate for it to be a separate plugin rather than a\r\n  library function so it is no longer part of genutils.\r\n                                                                             \r\nFunction Prototypes:\r\n    \" Add a handler for all the maps that share the given prefix in\r\n    \"\t  normal mode.\r\n    void ExecMap(String prefix)\r\n                                                                             \r\n    \" Add a handler for all the maps that share the given prefix in\r\n    \"\t  the given mode. Only normal and visual modes are supported.\r\n    void ExecMap2(String prefix, String mode)\r\n                                                                             \r\n    \" Prompt user for a map with the given prefix in the given mode and\r\n    \"\t  return the map. The return value could be executed using :normal\r\n    \"\t  command. If the user cancels the operation, it returns an empty\r\n    \"\t  string. Only normal and visual modes are supported.\r\n    String ExecMapPrompt(String prefix, String mode)\r\nLimitations:\r\n  - You can only execute maps that are complete to be executable using\r\n    :normal exmode command (see help on :normal). One example map that will\r\n    not work is:\r\n                                                                             \r\n      nnoremap _ab :call input('ab command')<CR>\r\n                                                                             \r\n    If you execute the above command using \":normal _ab\", it will not run as\r\n    expected. Similarly, maps that are supposed to leave you on the : prompt\r\n    don't work as well.\r\n\r\n\r\n\r\nSearch_key_words: execmap execmap.vim normal visual mode map maps genutils relax comfort Hari Krishna Dara","install_details":"Just drop it in the plugin directory. Follow the procedur described above to add additional maps.\r\n\r\nRequires genutils(vimscript #197)","5":"Just drop it in the plugin directory. Follow the procedur described above to add additional maps.\r\n\r\nRequires genutils(vimscript #197)","first_name":"Hari Krishna","6":"Hari Krishna","last_name":"Dara","7":"Dara","releases":[{"0":"598","vim_version":"6.0","1":"6.0","script_version":"1.4","2":"1.4","version_comment":"Now requires Vim 6.3 for the fix in map output redirection.\r\n\r\nThis version mainly contains the new feature requested by Salman Halim to support executing maps that have conflicts (matches a map, but a longer map is also possible). Also added more documentation.","3":"Now requires Vim 6.3 for the fix in map output redirection.\r\n\r\nThis version mainly contains the new feature requested by Salman Halim to support executing maps that have conflicts (matches a map, but a longer map is also possible). Also added more documentation.","package":"execmap.vim","4":"execmap.vim","src_id":"3264","5":"3264","creation_date":"1090606154","6":"1090606154"},{"0":"598","vim_version":"6.0","1":"6.0","script_version":"1.3","2":"1.3","version_comment":"- Improved visual mode support.\r\n- Added support for executing maps when they have shorter counter parts (if both \\ab and \\abc exist, you could not execute \\abc earlier), requested by Salmon Halim (salmanhalim at yahoo dot com). Read description for usage. Needs patches for Vim 6.2 for this to work (don't know which patch, just get all the latest).","3":"- Improved visual mode support.\r\n- Added support for executing maps when they have shorter counter parts (if both \\ab and \\abc exist, you could not execute \\abc earlier), requested by Salmon Halim (salmanhalim at yahoo dot com). Read description for usage. Needs patches for Vim 6.2 for this to work (don't know which patch, just get all the latest).","package":"execmap.vim","4":"execmap.vim","src_id":"2891","5":"2891","creation_date":"1080587285","6":"1080587285"},{"0":"598","vim_version":"6.0","1":"6.0","script_version":"1.2","2":"1.2","version_comment":"Brought the changes made by Srinath Avadhanula for the script to work with visual maps also, as part of his vim-latex project. Thanks to Srinath for finishing this long pending TODO item.","3":"Brought the changes made by Srinath Avadhanula for the script to work with visual maps also, as part of his vim-latex project. Thanks to Srinath for finishing this long pending TODO item.","package":"execmap.vim","4":"execmap.vim","src_id":"2364","5":"2364","creation_date":"1065023182","6":"1065023182"},{"0":"598","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"execmap.vim","4":"execmap.vim","src_id":"1844","5":"1844","creation_date":"1048341721","6":"1048341721"}]},"597":{"script_id":"597","0":"597","script_name":"python tools","1":"python tools","script_type":"utility","2":"utility","summary":"Python production tools","3":"Python production tools","description":"Features :\r\n- HappyDoc opens the current module UML class schema : [CTRL]-h\r\n- getPythonDoc finds the current class+method name : [CTRL]-j\r\n- collapsePythonBlock folds a python block : [CTRL]-k\r\n- putEmptyFunc writes a new commented func : [CTRL]-n\r\n\r\nGoodies :\r\n- Explorer under [F9]\r\n- Terminal overflow highlighting (80columns)\r\n","4":"Features :\r\n- HappyDoc opens the current module UML class schema : [CTRL]-h\r\n- getPythonDoc finds the current class+method name : [CTRL]-j\r\n- collapsePythonBlock folds a python block : [CTRL]-k\r\n- putEmptyFunc writes a new commented func : [CTRL]-n\r\n\r\nGoodies :\r\n- Explorer under [F9]\r\n- Terminal overflow highlighting (80columns)\r\n","install_details":"Requirements :\r\n- vim with python interpreter enabled\r\n\r\nFor uml diagrams :\r\n- happydoc (currently using 2.0)\r\n- dia\r\n","5":"Requirements :\r\n- vim with python interpreter enabled\r\n\r\nFor uml diagrams :\r\n- happydoc (currently using 2.0)\r\n- dia\r\n","first_name":"S\u00c3\u00a9bastien","6":"S\u00c3\u00a9bastien","last_name":"MIGNIOT","7":"MIGNIOT","releases":[{"0":"597","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"python.vim","4":"python.vim","src_id":"1842","5":"1842","creation_date":"1048307007","6":"1048307007"}]},"596":{"script_id":"596","0":"596","script_name":"colorpalette.vim","1":"colorpalette.vim","script_type":"utility","2":"utility","summary":"vim script for color palette etc.","3":"vim script for color palette etc.","description":"A very simple range of colors to color words or line temporarily... \r\n\r\nhttp:\/\/www.intratel.es\/cubica\/dominios\/joyasur\/gtemp\/cp.jpg\r\n\r\n\"USAGE:\r\n\r\n\"To see the Palette of colors:\r\n        \"normal mode: ;p\r\n        \"command: Palette\r\n\"To select a color:\r\n        \"normal mode: <RightMouse> or <Up> <Down> arrows \r\n\"To color a word or a line:\r\n        \"normal mode for background: <Space>\r\n        \"normal mode for foreground: <M-Space>\r\n        \"visual mode for background: <RightMouse>\r\n        \"visual mode for foreground: <M-RightMouse>\r\n\"Color HEX and RGB information:\r\n        \"normal mode: i\r\n        \"popup menu: info color\r\n\r\n\"Note: To see in Status-Line the color that has been selected --don\u00c2\u00b4t forget to change the default number of \"User\".","4":"A very simple range of colors to color words or line temporarily... \r\n\r\nhttp:\/\/www.intratel.es\/cubica\/dominios\/joyasur\/gtemp\/cp.jpg\r\n\r\n\"USAGE:\r\n\r\n\"To see the Palette of colors:\r\n        \"normal mode: ;p\r\n        \"command: Palette\r\n\"To select a color:\r\n        \"normal mode: <RightMouse> or <Up> <Down> arrows \r\n\"To color a word or a line:\r\n        \"normal mode for background: <Space>\r\n        \"normal mode for foreground: <M-Space>\r\n        \"visual mode for background: <RightMouse>\r\n        \"visual mode for foreground: <M-RightMouse>\r\n\"Color HEX and RGB information:\r\n        \"normal mode: i\r\n        \"popup menu: info color\r\n\r\n\"Note: To see in Status-Line the color that has been selected --don\u00c2\u00b4t forget to change the default number of \"User\".","install_details":"","5":"","first_name":"nicolaie","6":"nicolaie","last_name":"george","7":"george","releases":[{"0":"596","vim_version":"6.0","1":"6.0","script_version":"0.2","2":"0.2","version_comment":"Added:  more colors, HEX and RGB color information, easy selection with Up and Down arrows; LeftMouse single click for selecting a color ---","3":"Added:  more colors, HEX and RGB color information, easy selection with Up and Down arrows; LeftMouse single click for selecting a color ---","package":"colorpalette.vim","4":"colorpalette.vim","src_id":"2127","5":"2127","creation_date":"1057238325","6":"1057238325"}]},"595":{"script_id":"595","0":"595","script_name":"HelpClose","1":"HelpClose","script_type":"utility","2":"utility","summary":"Close all help windows","3":"Close all help windows","description":"This plugin defines a new little command :HelpAllClose.  When execute this command, all help windows are closed.  You doesn't need to move to help window, when want to close it, any more.","4":"This plugin defines a new little command :HelpAllClose.  When execute this command, all help windows are closed.  You doesn't need to move to help window, when want to close it, any more.","install_details":"Put the file at one of your plugin directories.\r\n  ex. $HOME\/.vim\/plugin\/\r\n  ex. $HOME\\vimfiles\\plugin\\\r\n  ex. $VIM\\vimfiles\\plugin\\","5":"Put the file at one of your plugin directories.\r\n  ex. $HOME\/.vim\/plugin\/\r\n  ex. $HOME\\vimfiles\\plugin\\\r\n  ex. $VIM\\vimfiles\\plugin\\","first_name":"Taro","6":"Taro","last_name":"MURAOKA","7":"MURAOKA","releases":[{"0":"595","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"helpclose.vim","4":"helpclose.vim","src_id":"1838","5":"1838","creation_date":"1048228485","6":"1048228485"}]},"594":{"script_id":"594","0":"594","script_name":"TaQua","1":"TaQua","script_type":"color scheme","2":"color scheme","summary":"baby colors for use with aqua themes","3":"baby colors for use with aqua themes","description":"I'm using an aqua theme on GTK and Mozilla, and made this color scheme to fit the light\/baby\/soft colors of the aqua stuff.\r\nCheck a screenshot in http:\/\/eustaquiorangel.com\/images\/taqua.png","4":"I'm using an aqua theme on GTK and Mozilla, and made this color scheme to fit the light\/baby\/soft colors of the aqua stuff.\r\nCheck a screenshot in http:\/\/eustaquiorangel.com\/images\/taqua.png","install_details":"","5":"","first_name":"Eustaquio","6":"Eustaquio","last_name":"Rangel de Oliveira Jr.","7":"Rangel de Oliveira Jr.","releases":[{"0":"594","vim_version":"6.0","1":"6.0","script_version":"1.1","2":"1.1","version_comment":"Some more colors on it.","3":"Some more colors on it.","package":"taqua.vim","4":"taqua.vim","src_id":"4679","5":"4679","creation_date":"1129611354","6":"1129611354"},{"0":"594","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"taqua.vim","4":"taqua.vim","src_id":"1837","5":"1837","creation_date":"1048227127","6":"1048227127"}]},"593":{"script_id":"593","0":"593","script_name":"guifont++.vim","1":"guifont++.vim","script_type":"utility","2":"utility","summary":"Vim plugin for quickly changing GUI font size","3":"Vim plugin for quickly changing GUI font size","description":"This plugin defines key mappings to quickly make the GUI font larger or\r\nsmaller. The default mappings are \"+\" to make the font larger by 1 point\r\nand \"-\" to make the font smaller by 1 point. The original font size can\r\nbe restored with \"=\" key at any time. The mappings are user-configurable\r\n(see the installation section below).\r\n\r\nThis plugin should work on Unix and Win32 but it will work only with\r\ncertain patterns of 'guifont' option, namely:\r\n\r\n - on Unix, 'guifont' should be set to the X Logical Font Description\r\n   (XLFD) name, for example:\r\n\r\n      set guifont=-*-lucidatypewriter-bold-*-*-*-15-*-*-*-*-*-*-*\r\n\r\n - on Win32, 'guifont' should include 'hXX' font option, for example:\r\n\r\n      set guifont=Lucida_Console:h8:cANSI\r\n\r\nPlease let me know if this is not good enough for you.","4":"This plugin defines key mappings to quickly make the GUI font larger or\r\nsmaller. The default mappings are \"+\" to make the font larger by 1 point\r\nand \"-\" to make the font smaller by 1 point. The original font size can\r\nbe restored with \"=\" key at any time. The mappings are user-configurable\r\n(see the installation section below).\r\n\r\nThis plugin should work on Unix and Win32 but it will work only with\r\ncertain patterns of 'guifont' option, namely:\r\n\r\n - on Unix, 'guifont' should be set to the X Logical Font Description\r\n   (XLFD) name, for example:\r\n\r\n      set guifont=-*-lucidatypewriter-bold-*-*-*-15-*-*-*-*-*-*-*\r\n\r\n - on Win32, 'guifont' should include 'hXX' font option, for example:\r\n\r\n      set guifont=Lucida_Console:h8:cANSI\r\n\r\nPlease let me know if this is not good enough for you.","install_details":"Simply copy this plugin into your plugin directory. (See 'plugin' in the\r\nVim User Manual.) Additionally, you may choose to override one of the\r\nfollowing global variables, which are used by this plugin, in your vimrc\r\nfile:\r\n\r\n - guifontpp_size_increment         (default: 1)\r\n      The number of points by which to make the font size smaller or\r\n      larger.\r\n - guifontpp_smaller_font_map       (default: \"-\")\r\n      LHS of the key mapping to make the font size smaller.\r\n - guifontpp_larger_font_map        (default: \"+\")\r\n      LHS of the key mapping to make the font size larger.\r\n - guifontpp_original_font_map      (default: \"=\")\r\n      LHS of the key mapping to restore the original font size.\r\n\r\nFor example, you could have something like this in your vimrc file:\r\n  let guifontpp_size_increment=2\r\n  let guifontpp_smaller_font_map=\"<F10>\"\r\n  let guifontpp_larger_font_map=\"<S-F10>\"\r\n  let guifontpp_original_font_map=\"<C-F10>\"","5":"Simply copy this plugin into your plugin directory. (See 'plugin' in the\r\nVim User Manual.) Additionally, you may choose to override one of the\r\nfollowing global variables, which are used by this plugin, in your vimrc\r\nfile:\r\n\r\n - guifontpp_size_increment         (default: 1)\r\n      The number of points by which to make the font size smaller or\r\n      larger.\r\n - guifontpp_smaller_font_map       (default: \"-\")\r\n      LHS of the key mapping to make the font size smaller.\r\n - guifontpp_larger_font_map        (default: \"+\")\r\n      LHS of the key mapping to make the font size larger.\r\n - guifontpp_original_font_map      (default: \"=\")\r\n      LHS of the key mapping to restore the original font size.\r\n\r\nFor example, you could have something like this in your vimrc file:\r\n  let guifontpp_size_increment=2\r\n  let guifontpp_smaller_font_map=\"<F10>\"\r\n  let guifontpp_larger_font_map=\"<S-F10>\"\r\n  let guifontpp_original_font_map=\"<C-F10>\"","first_name":"Alexander","6":"Alexander","last_name":"Anderson","7":"Anderson","releases":[{"0":"593","vim_version":"6.0","1":"6.0","script_version":"1.6","2":"1.6","version_comment":"Initial upload","3":"Initial upload","package":"guifont++.vim","4":"guifont++.vim","src_id":"1836","5":"1836","creation_date":"1048186872","6":"1048186872"}]},"592":{"script_id":"592","0":"592","script_name":"ChocolateLiquor","1":"ChocolateLiquor","script_type":"color scheme","2":"color scheme","summary":"low-contrast dark scheme","3":"low-contrast dark scheme","description":"This started as an inverse\/opposite of PapayaWhip (vimscript #591),\r\nbut took on a life of its own. If you want a dark background that's very\r\nusable but without too much contrast, try this one.\r\n\r\nScreenshot: http:\/\/home.ptd.net\/~gwilliam\/vim\/ChocolateLiquor.png","4":"This started as an inverse\/opposite of PapayaWhip (vimscript #591),\r\nbut took on a life of its own. If you want a dark background that's very\r\nusable but without too much contrast, try this one.\r\n\r\nScreenshot: http:\/\/home.ptd.net\/~gwilliam\/vim\/ChocolateLiquor.png","install_details":"Copy to $HOME\/.vim\/colors or $VIM\/vimfiles\/colors\r\n:colorscheme ChocolateLiquor","5":"Copy to $HOME\/.vim\/colors or $VIM\/vimfiles\/colors\r\n:colorscheme ChocolateLiquor","first_name":"Gerald","6":"Gerald","last_name":"Williams","7":"Williams","releases":[{"0":"592","vim_version":"6.0","1":"6.0","script_version":"1.3","2":"1.3","version_comment":"Minor updates to FoldColumn, cterm colors (see also vimscript #1922).","3":"Minor updates to FoldColumn, cterm colors (see also vimscript #1922).","package":"ChocolateLiquor.vim","4":"ChocolateLiquor.vim","src_id":"7238","5":"7238","creation_date":"1181713959","6":"1181713959"},{"0":"592","vim_version":"7.0","1":"7.0","script_version":"1.2","2":"1.2","version_comment":"Improved visibility of folds","3":"Improved visibility of folds","package":"ChocolateLiquor.vim","4":"ChocolateLiquor.vim","src_id":"7229","5":"7229","creation_date":"1181639725","6":"1181639725"},{"0":"592","vim_version":"6.0","1":"6.0","script_version":"1.1","2":"1.1","version_comment":"Added line number coloring","3":"Added line number coloring","package":"ChocolateLiquor.vim","4":"ChocolateLiquor.vim","src_id":"1928","5":"1928","creation_date":"1050643059","6":"1050643059"},{"0":"592","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"ChocolateLiquor.vim","4":"ChocolateLiquor.vim","src_id":"1830","5":"1830","creation_date":"1048006840","6":"1048006840"}]},"591":{"script_id":"591","0":"591","script_name":"PapayaWhip","1":"PapayaWhip","script_type":"color scheme","2":"color scheme","summary":"low-contrast light scheme","3":"low-contrast light scheme","description":"This has a nice light background (PapayaWhip) that's easy on\r\nthe eyes yet very usable. Not nearly as \"puffy\" as peachpuff.\r\nCompare it to ChocolateLiquor (vimscript #592).\r\n\r\nScreenshot: http:\/\/home.ptd.net\/~gwilliam\/vim\/PapayaWhip.png","4":"This has a nice light background (PapayaWhip) that's easy on\r\nthe eyes yet very usable. Not nearly as \"puffy\" as peachpuff.\r\nCompare it to ChocolateLiquor (vimscript #592).\r\n\r\nScreenshot: http:\/\/home.ptd.net\/~gwilliam\/vim\/PapayaWhip.png","install_details":"Copy to $HOME\/.vim\/colors or $VIM\/vimfiles\/colors\r\n:colorscheme PapayaWhip","5":"Copy to $HOME\/.vim\/colors or $VIM\/vimfiles\/colors\r\n:colorscheme PapayaWhip","first_name":"Gerald","6":"Gerald","last_name":"Williams","7":"Williams","releases":[{"0":"591","vim_version":"6.0","1":"6.0","script_version":"1.1","2":"1.1","version_comment":"Added line number coloring","3":"Added line number coloring","package":"PapayaWhip.vim","4":"PapayaWhip.vim","src_id":"1927","5":"1927","creation_date":"1050643024","6":"1050643024"},{"0":"591","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"PapayaWhip.vim","4":"PapayaWhip.vim","src_id":"1829","5":"1829","creation_date":"1048006586","6":"1048006586"}]},"590":{"script_id":"590","0":"590","script_name":"BlackSea","1":"BlackSea","script_type":"color scheme","2":"color scheme","summary":"seashell-night, if you prefer","3":"seashell-night, if you prefer","description":"This is an inverse\/opposite of the \"seashell\" color scheme\r\n(vimscript #589).\r\n\r\nDark background, high contrast. The cterm version is very\r\nsimilar to \"evening\".\r\n\r\nScreenshot: http:\/\/home.ptd.net\/~gwilliam\/vim\/BlackSea.png","4":"This is an inverse\/opposite of the \"seashell\" color scheme\r\n(vimscript #589).\r\n\r\nDark background, high contrast. The cterm version is very\r\nsimilar to \"evening\".\r\n\r\nScreenshot: http:\/\/home.ptd.net\/~gwilliam\/vim\/BlackSea.png","install_details":"Copy to $HOME\/.vim\/colors or $VIM\/vimfiles\/colors\r\n:colorscheme BlackSea","5":"Copy to $HOME\/.vim\/colors or $VIM\/vimfiles\/colors\r\n:colorscheme BlackSea","first_name":"Gerald","6":"Gerald","last_name":"Williams","7":"Williams","releases":[{"0":"590","vim_version":"7.0","1":"7.0","script_version":"1.3","2":"1.3","version_comment":"Improved Fold coloring","3":"Improved Fold coloring","package":"BlackSea.vim","4":"BlackSea.vim","src_id":"7236","5":"7236","creation_date":"1181713263","6":"1181713263"},{"0":"590","vim_version":"6.0","1":"6.0","script_version":"1.2","2":"1.2","version_comment":"Improved status line visibility in GUI mode","3":"Improved status line visibility in GUI mode","package":"BlackSea.vim","4":"BlackSea.vim","src_id":"1835","5":"1835","creation_date":"1048157541","6":"1048157541"},{"0":"590","vim_version":"6.0","1":"6.0","script_version":"1.1","2":"1.1","version_comment":"Vastly improved diff coloring","3":"Vastly improved diff coloring","package":"BlackSea.vim","4":"BlackSea.vim","src_id":"1833","5":"1833","creation_date":"1048075159","6":"1048075159"},{"0":"590","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"BlackSea.vim","4":"BlackSea.vim","src_id":"1828","5":"1828","creation_date":"1048006383","6":"1048006383"}]},"589":{"script_id":"589","0":"589","script_name":"seashell","1":"seashell","script_type":"color scheme","2":"color scheme","summary":"moderate contrast scheme, light or dark","3":"moderate contrast scheme, light or dark","description":"This is very reminiscent of a seashell. It's something of a cross\r\nbetween zellner and peachpuff, if such a thing is possible. :-)\r\n\r\nSee also vimscript #590\r\n\r\nScreenshot: http:\/\/home.ptd.net\/~gwilliam\/vim\/seashell.png","4":"This is very reminiscent of a seashell. It's something of a cross\r\nbetween zellner and peachpuff, if such a thing is possible. :-)\r\n\r\nSee also vimscript #590\r\n\r\nScreenshot: http:\/\/home.ptd.net\/~gwilliam\/vim\/seashell.png","install_details":"Copy to $HOME\/.vim\/colors or $VIM\/vimfiles\/colors\r\n:colorscheme seashell","5":"Copy to $HOME\/.vim\/colors or $VIM\/vimfiles\/colors\r\n:colorscheme seashell","first_name":"Gerald","6":"Gerald","last_name":"Williams","7":"Williams","releases":[{"0":"589","vim_version":"7.0","1":"7.0","script_version":"1.2","2":"1.2","version_comment":"Combined with BlackSea into single light\/dark scheme","3":"Combined with BlackSea into single light\/dark scheme","package":"seashell.vim","4":"seashell.vim","src_id":"7235","5":"7235","creation_date":"1181713148","6":"1181713148"},{"0":"589","vim_version":"6.0","1":"6.0","script_version":"1.1","2":"1.1","version_comment":"Added line number coloring","3":"Added line number coloring","package":"seashell.vim","4":"seashell.vim","src_id":"1926","5":"1926","creation_date":"1050642950","6":"1050642950"},{"0":"589","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"seashell.vim","4":"seashell.vim","src_id":"1827","5":"1827","creation_date":"1048006125","6":"1048006125"}]},"588":{"script_id":"588","0":"588","script_name":"JavaBrowser","1":"JavaBrowser","script_type":"utility","2":"utility","summary":"Shows java file class, package in a tree as in IDEs. Java source browser.","3":"Shows java file class, package in a tree as in IDEs. Java source browser.","description":"This script is modelled on TagList vim script. Thanks to Yegappan Lakshmanan for taglist.vim\r\nHowever, this script is SPECIFICALLY tailored for Java language. So, it shows structure of the Java file\r\nstarting with classes defined within it and NOT in a general tag structure. I found it useful and hope you all\r\nfind it useful too. It also has a nice syntax to show the class members in UML format.\r\n\r\nThe \"Java Browser\" plugin provides the following features:\r\n1. Opens details of Java file types (class, package etc) in a Tree structure in a separate vim window\r\ne.g: + package\r\n            java.util\r\n       + class\r\n       +   vector\r\n       +      field\r\n                  ....\r\n       +      method\r\n                  ....\r\n2. The tree has syntax highlighting as follows:\r\n    A. public members in green, protected in orange, private in red\r\n    B. static members are underlined and abstracts are shown in italics as per UML specs in addition to above highlighting.\r\ne.g:- If you have method that public static and abstract, it will shown in green color, in italic and underlined. You can think of all possible combinations.\r\n3. When you double click (configurable for a single click) or hit enter key in the browser window when on a member, it will take you to the definition of that member in the Java file window.\r\n4. It can show an arrow (=>) or an icon (ONLY for signs enabled VIM) showing the current position of the cursor in the java file.\r\n5. The browser window is updated automatically when you open any other Java file (or switch between buffers) in the Java file window. You can manually update browser window by typing 'u' in the browser window (when u change a class for example and you need that to be reflected).\r\n6. When you put the cursor (not the mouse pointer) on a member, it shows the prototype of the member declaration in the command window (like baloon popup in IDEs!)\r\n7. It understands the inner classes and are shown like HashMap.Iterator etc.\r\n8. It understands the overridden methods.\r\n9. Browser window opening can be configured for a vertically\/horizontally split Vim window.\r\n10. Groups the tags by their type and displays them in a foldable tree.\r\n11. Automatically highlights the current tag name.\r\n12. The browser window contents can be sorted either by name or by line number.\r\n13. Runs in all the platforms where the exuberant ctags utility and Vim are\r\n     supported (this includes MS-Windows and Unix based systems).\r\n\r\n TODO:\r\n 1. To cache ctags output for a file to speed up displaying the taglist\r\n     window.\r\n \r\nThis plugin relies on the exuberant ctags utility to generate the tag\r\n listing. You can download the exuberant ctags utility from\r\n http:\/\/ctags.sourceforge.net. The exuberant ctags utility must be installed\r\n in your system to use this plugin. You should use exuberant ctags version\r\n 5.3 and above.  There is no need for you to create a tags file to use this\r\n plugin.\r\n\r\n This script relies on the Vim \"filetype\" detection mechanism to determine\r\n the type of the current file. To turn on filetype detection use\r\n\r\n               :filetype on\r\n\r\n This plugin will not work in 'compatible' mode.  Make sure the 'compatible'\r\n option is not set. This plugin will not work if you run Vim in the\r\n restricted mode (using the -Z command-line argument). This plugin also\r\n assumes that the system() Vim function is supported.","4":"This script is modelled on TagList vim script. Thanks to Yegappan Lakshmanan for taglist.vim\r\nHowever, this script is SPECIFICALLY tailored for Java language. So, it shows structure of the Java file\r\nstarting with classes defined within it and NOT in a general tag structure. I found it useful and hope you all\r\nfind it useful too. It also has a nice syntax to show the class members in UML format.\r\n\r\nThe \"Java Browser\" plugin provides the following features:\r\n1. Opens details of Java file types (class, package etc) in a Tree structure in a separate vim window\r\ne.g: + package\r\n            java.util\r\n       + class\r\n       +   vector\r\n       +      field\r\n                  ....\r\n       +      method\r\n                  ....\r\n2. The tree has syntax highlighting as follows:\r\n    A. public members in green, protected in orange, private in red\r\n    B. static members are underlined and abstracts are shown in italics as per UML specs in addition to above highlighting.\r\ne.g:- If you have method that public static and abstract, it will shown in green color, in italic and underlined. You can think of all possible combinations.\r\n3. When you double click (configurable for a single click) or hit enter key in the browser window when on a member, it will take you to the definition of that member in the Java file window.\r\n4. It can show an arrow (=>) or an icon (ONLY for signs enabled VIM) showing the current position of the cursor in the java file.\r\n5. The browser window is updated automatically when you open any other Java file (or switch between buffers) in the Java file window. You can manually update browser window by typing 'u' in the browser window (when u change a class for example and you need that to be reflected).\r\n6. When you put the cursor (not the mouse pointer) on a member, it shows the prototype of the member declaration in the command window (like baloon popup in IDEs!)\r\n7. It understands the inner classes and are shown like HashMap.Iterator etc.\r\n8. It understands the overridden methods.\r\n9. Browser window opening can be configured for a vertically\/horizontally split Vim window.\r\n10. Groups the tags by their type and displays them in a foldable tree.\r\n11. Automatically highlights the current tag name.\r\n12. The browser window contents can be sorted either by name or by line number.\r\n13. Runs in all the platforms where the exuberant ctags utility and Vim are\r\n     supported (this includes MS-Windows and Unix based systems).\r\n\r\n TODO:\r\n 1. To cache ctags output for a file to speed up displaying the taglist\r\n     window.\r\n \r\nThis plugin relies on the exuberant ctags utility to generate the tag\r\n listing. You can download the exuberant ctags utility from\r\n http:\/\/ctags.sourceforge.net. The exuberant ctags utility must be installed\r\n in your system to use this plugin. You should use exuberant ctags version\r\n 5.3 and above.  There is no need for you to create a tags file to use this\r\n plugin.\r\n\r\n This script relies on the Vim \"filetype\" detection mechanism to determine\r\n the type of the current file. To turn on filetype detection use\r\n\r\n               :filetype on\r\n\r\n This plugin will not work in 'compatible' mode.  Make sure the 'compatible'\r\n option is not set. This plugin will not work if you run Vim in the\r\n restricted mode (using the -Z command-line argument). This plugin also\r\n assumes that the system() Vim function is supported.","install_details":"1. Unzip and untar javabrowser.tgz to get javabrowser.vim and tagindicator.xpm files.\r\n2. Copy the javabrowser.vim script to the $HOME\/.vim\/plugin directory. Refer to\r\n    ':help add-plugin', ':help add-global-plugin' and ':help runtimepath' for\r\n    more details about Vim plugins.\r\n3. Copy tagindicator.xpm and tagindicator.bmp to $VIM\/pixmaps directory. NOTE: This is optional.\r\n4. Set the JavaBrowser_Ctags_Cmd variable to point to the exuberant ctags utility\r\n    path.\r\n5. Set Javabrowser_Use_Icon = 1 in your .vimrc file if you want to use icon provided with the script. Note: VIM must be compiled with \"signs\" option for this. If it is not, it will automatically be disabled and normal search highlight will be used to highlight the current tag. You can also use Javabrowser_Use_Text_Icon = 1 if you like => to indicate your current tag. Even for this, VIM needs to be compiled with \"sign\" support. You can also set JavaBrowser_Use_Highlight_Tag = 1 in your .vimrc if you want the current tag to be highlighted along with the icon (text or tagindicator.xpm). By default, it is OFF.\r\n6. If you are running a terminal\/console version of Vim and the terminal\r\n    doesn't support changing the window width then set the JavaBrowser_Inc_Winwidth\r\n    variable to 0.\r\n7. Restart Vim.\r\n8. You can use the \":JavaBrowser\" command to open\/close the taglist window.\r\n9. NOTE: This script has fileformat (ff) of DOS. UNIX users, please change it to unix before using it (Use set ff=unix and save it). Thanks to Deepak for pointing that out. That's what I do for any script I find in DOS fileformat! ","5":"1. Unzip and untar javabrowser.tgz to get javabrowser.vim and tagindicator.xpm files.\r\n2. Copy the javabrowser.vim script to the $HOME\/.vim\/plugin directory. Refer to\r\n    ':help add-plugin', ':help add-global-plugin' and ':help runtimepath' for\r\n    more details about Vim plugins.\r\n3. Copy tagindicator.xpm and tagindicator.bmp to $VIM\/pixmaps directory. NOTE: This is optional.\r\n4. Set the JavaBrowser_Ctags_Cmd variable to point to the exuberant ctags utility\r\n    path.\r\n5. Set Javabrowser_Use_Icon = 1 in your .vimrc file if you want to use icon provided with the script. Note: VIM must be compiled with \"signs\" option for this. If it is not, it will automatically be disabled and normal search highlight will be used to highlight the current tag. You can also use Javabrowser_Use_Text_Icon = 1 if you like => to indicate your current tag. Even for this, VIM needs to be compiled with \"sign\" support. You can also set JavaBrowser_Use_Highlight_Tag = 1 in your .vimrc if you want the current tag to be highlighted along with the icon (text or tagindicator.xpm). By default, it is OFF.\r\n6. If you are running a terminal\/console version of Vim and the terminal\r\n    doesn't support changing the window width then set the JavaBrowser_Inc_Winwidth\r\n    variable to 0.\r\n7. Restart Vim.\r\n8. You can use the \":JavaBrowser\" command to open\/close the taglist window.\r\n9. NOTE: This script has fileformat (ff) of DOS. UNIX users, please change it to unix before using it (Use set ff=unix and save it). Thanks to Deepak for pointing that out. That's what I do for any script I find in DOS fileformat! ","first_name":"Pradeep","6":"Pradeep","last_name":"Unde","7":"Unde","releases":[{"0":"588","vim_version":"6.0","1":"6.0","script_version":"2.03","2":"2.03","version_comment":"Two small bug fixes\r\n1. When UML visibility indicators are enabled, they were also included in syntax highlighting\r\n2. Sort by order not supported. But the window showed Sort by order at top. Changed that to Sort by name","3":"Two small bug fixes\r\n1. When UML visibility indicators are enabled, they were also included in syntax highlighting\r\n2. Sort by order not supported. But the window showed Sort by order at top. Changed that to Sort by name","package":"javabrowser.zip","4":"javabrowser.zip","src_id":"6184","5":"6184","creation_date":"1158329269","6":"1158329269"},{"0":"588","vim_version":"7.0","1":"7.0","script_version":"2.02","2":"2.02","version_comment":"The zip file had lot of spurious files. Removed them.","3":"The zip file had lot of spurious files. Removed them.","package":"javabrowser.zip","4":"javabrowser.zip","src_id":"6137","5":"6137","creation_date":"1157276996","6":"1157276996"},{"0":"588","vim_version":"7.0","1":"7.0","script_version":"2.02","2":"2.02","version_comment":"1. Added back the nice icons (tagindicator.xpm) and (tagindicator.bmp) with the script. When the zip file is unzipped in the $VIM directory (say c:\\vim), it would put the images in the $VIM\\pixmaps directory and the javabrowser.vim under $VIM\\vimfiles\\plugin directory. I like browsing the Java Tree with the image icon and I hope you would like that too.","3":"1. Added back the nice icons (tagindicator.xpm) and (tagindicator.bmp) with the script. When the zip file is unzipped in the $VIM directory (say c:\\vim), it would put the images in the $VIM\\pixmaps directory and the javabrowser.vim under $VIM\\vimfiles\\plugin directory. I like browsing the Java Tree with the image icon and I hope you would like that too.","package":"javabrowser.zip","4":"javabrowser.zip","src_id":"6131","5":"6131","creation_date":"1157120727","6":"1157120727"},{"0":"588","vim_version":"7.0","1":"7.0","script_version":"2.02","2":"2.02","version_comment":"Automatic tag highlighting supported now. Depending where the cursor is in the java file, corresponding tag is automatically hightlighed in the JavaBrowser window\r\n","3":"Automatic tag highlighting supported now. Depending where the cursor is in the java file, corresponding tag is automatically hightlighed in the JavaBrowser window\r\n","package":"javabrowser.vim","4":"javabrowser.vim","src_id":"6123","5":"6123","creation_date":"1157028315","6":"1157028315"},{"0":"588","vim_version":"7.0","1":"7.0","script_version":"2.01","2":"2.01","version_comment":"Following bog fixes and one improvement\r\n1. Fixed error showing tooltip when mouse was over \"field\" or \"method\"\r\n2. The cache was not getting set for the tooltip correctly\r\n3. The tooltip was staring with the <TAB> character picked up from the ctags output. It has been removed now","3":"Following bog fixes and one improvement\r\n1. Fixed error showing tooltip when mouse was over \"field\" or \"method\"\r\n2. The cache was not getting set for the tooltip correctly\r\n3. The tooltip was staring with the <TAB> character picked up from the ctags output. It has been removed now","package":"javabrowser.vim","4":"javabrowser.vim","src_id":"6112","5":"6112","creation_date":"1156946535","6":"1156946535"},{"0":"588","vim_version":"6.0","1":"6.0","script_version":"2.0","2":"2.0","version_comment":"1. Overhauled the code for version 7.0 and is now faster\r\n2. Does not give errors for version 7.0 now when browsing (or opening) the class tree\r\n3. Added caching for ctags output, so, buffer switching is very fast for previously viewed buffers\r\nNOTE: The sort by order and tag position auto refresh in the browser tree when navigating Java file still do not work.\r\nHopefully will make that work pretty soon :)\r\nI have not tested it extensively. I would really appreciate it if you let me know about the bugs.","3":"1. Overhauled the code for version 7.0 and is now faster\r\n2. Does not give errors for version 7.0 now when browsing (or opening) the class tree\r\n3. Added caching for ctags output, so, buffer switching is very fast for previously viewed buffers\r\nNOTE: The sort by order and tag position auto refresh in the browser tree when navigating Java file still do not work.\r\nHopefully will make that work pretty soon :)\r\nI have not tested it extensively. I would really appreciate it if you let me know about the bugs.","package":"javabrowser.vim","4":"javabrowser.vim","src_id":"6110","5":"6110","creation_date":"1156884328","6":"1156884328"},{"0":"588","vim_version":"6.0","1":"6.0","script_version":"1.22","2":"1.22","version_comment":"1. Added function JavaBrowser_Set_Syntax_Highlighting().\r\n 2. Now, the syntax highlighting for the Class tree would automatically be set\r\n when a new window is opened or at the time of tag refersh. So, the user would\r\n always see the syntax highlighting set for JavaBrowser syntax groups even if\r\n the color scheme is changed in the middle of an editing session.\r\n","3":"1. Added function JavaBrowser_Set_Syntax_Highlighting().\r\n 2. Now, the syntax highlighting for the Class tree would automatically be set\r\n when a new window is opened or at the time of tag refersh. So, the user would\r\n always see the syntax highlighting set for JavaBrowser syntax groups even if\r\n the color scheme is changed in the middle of an editing session.\r\n","package":"javabrowser.vim","4":"javabrowser.vim","src_id":"5563","5":"5563","creation_date":"1145117444","6":"1145117444"},{"0":"588","vim_version":"6.0","1":"6.0","script_version":"1.21","2":"1.21","version_comment":"Added option JavaBrowser_Show_UML_Visibility. If set, which is the default, JavaBrowser uses UML visibility indicators. + => public, - => private, # => protected in addition to the syntax highlighting.\r\n","3":"Added option JavaBrowser_Show_UML_Visibility. If set, which is the default, JavaBrowser uses UML visibility indicators. + => public, - => private, # => protected in addition to the syntax highlighting.\r\n","package":"javabrowser.vim","4":"javabrowser.vim","src_id":"5474","5":"5474","creation_date":"1142959299","6":"1142959299"},{"0":"588","vim_version":"6.0","1":"6.0","script_version":"1.20","2":"1.20","version_comment":"1. Bugfix to correct the typo for balloon_eval\r\n2. Now also checking if the version > 700 before setting the bexpr option\r\nThe script now does show an error if the verison < 7.0. However, to get the advantage of tooltip, verion >= 7.0 is needed.\r\n","3":"1. Bugfix to correct the typo for balloon_eval\r\n2. Now also checking if the version > 700 before setting the bexpr option\r\nThe script now does show an error if the verison < 7.0. However, to get the advantage of tooltip, verion >= 7.0 is needed.\r\n","package":"javabrowser.vim","4":"javabrowser.vim","src_id":"5454","5":"5454","creation_date":"1142590164","6":"1142590164"},{"0":"588","vim_version":"6.0","1":"6.0","script_version":"1.19","2":"1.19","version_comment":"Forgot to mention that the baloon_eval feature works for vim 7.0 onwards ONLY for any arbitrary tooltips. Sorry, if this caused any confusion. So, basically, to use this new feature, you need vim 7.0","3":"Forgot to mention that the baloon_eval feature works for vim 7.0 onwards ONLY for any arbitrary tooltips. Sorry, if this caused any confusion. So, basically, to use this new feature, you need vim 7.0","package":"javabrowser.vim","4":"javabrowser.vim","src_id":"5425","5":"5425","creation_date":"1142277174","6":"1142277174"},{"0":"588","vim_version":"6.0","1":"6.0","script_version":"1.19","2":"1.19","version_comment":"Added nice tool-tip when mouse is over a function\/variable name in the tag list window. Uses the ballon_eval feature for this. If this feature is not there, the tool-tip would not be shown. Shows a nice prototype for each tag in the tool-tip. An update after a loooong time.","3":"Added nice tool-tip when mouse is over a function\/variable name in the tag list window. Uses the ballon_eval feature for this. If this feature is not there, the tool-tip would not be shown. Shows a nice prototype for each tag in the tool-tip. An update after a loooong time.","package":"javabrowser.vim","4":"javabrowser.vim","src_id":"5411","5":"5411","creation_date":"1142025251","6":"1142025251"},{"0":"588","vim_version":"6.0","1":"6.0","script_version":"1.18","2":"1.18","version_comment":"Bug fix when sorted by name. Fixed the tag position. Now it shows the arrow at correct position.","3":"Bug fix when sorted by name. Fixed the tag position. Now it shows the arrow at correct position.","package":"javabrowser.tar.gz","4":"javabrowser.tar.gz","src_id":"2495","5":"2495","creation_date":"1069152520","6":"1069152520"},{"0":"588","vim_version":"6.0","1":"6.0","script_version":"1.17","2":"1.17","version_comment":"1. Optimized so that when the cursor moves within a method\/function, the tag\r\n is not rehighlighted, reducing the flicker on the screen.\r\n2. The sorting now works properly and correct tag is highlighted after the\r\n sorting.\r\n3. Set JavaBrowser_Expand_Tree_At_Startup = 1 so that the tree opens\r\n completely at :JavaBrowser command\r\n4. Bug fix: Now escaping the SPACES in $VIM so that sign will be read properly. If your $VIM looks like C:\\Program Files\\Vim, it will now work. Thanks to Doug McInns for feed back.","3":"1. Optimized so that when the cursor moves within a method\/function, the tag\r\n is not rehighlighted, reducing the flicker on the screen.\r\n2. The sorting now works properly and correct tag is highlighted after the\r\n sorting.\r\n3. Set JavaBrowser_Expand_Tree_At_Startup = 1 so that the tree opens\r\n completely at :JavaBrowser command\r\n4. Bug fix: Now escaping the SPACES in $VIM so that sign will be read properly. If your $VIM looks like C:\\Program Files\\Vim, it will now work. Thanks to Doug McInns for feed back.","package":"javabrowser.tar.gz","4":"javabrowser.tar.gz","src_id":"2340","5":"2340","creation_date":"1063965668","6":"1063965668"},{"0":"588","vim_version":"6.0","1":"6.0","script_version":"1.16","2":"1.16","version_comment":"Added tagindicator.bmp for windows. Vim on Windows does not understand the xpms. Arrgghhh! So, now Windows users can also have icon to show the current tag.\r\n","3":"Added tagindicator.bmp for windows. Vim on Windows does not understand the xpms. Arrgghhh! So, now Windows users can also have icon to show the current tag.\r\n","package":"javabrowser.tar.gz","4":"javabrowser.tar.gz","src_id":"2339","5":"2339","creation_date":"1063795434","6":"1063795434"},{"0":"588","vim_version":"6.0","1":"6.0","script_version":"1.15","2":"1.15","version_comment":"1. Added various configurable ways to highlight current tag which include\r\n A. an icon or B. an arrow(=>) with highlight of Constant and\/or C. normal\r\n search highlight\r\n 2. Added options to control all these. Added 'JavaBrowser_Use_Icon',\r\n 'JavaBrowser_Use_Text_Icon' and 'JavaBrowser_Use_Highlight_Tag'\r\n 3. All have default values","3":"1. Added various configurable ways to highlight current tag which include\r\n A. an icon or B. an arrow(=>) with highlight of Constant and\/or C. normal\r\n search highlight\r\n 2. Added options to control all these. Added 'JavaBrowser_Use_Icon',\r\n 'JavaBrowser_Use_Text_Icon' and 'JavaBrowser_Use_Highlight_Tag'\r\n 3. All have default values","package":"javabrowser.tar.gz","4":"javabrowser.tar.gz","src_id":"2311","5":"2311","creation_date":"1063004715","6":"1063004715"},{"0":"588","vim_version":"6.0","1":"6.0","script_version":"1.14","2":"1.14","version_comment":"Now automatically highlights the current tag.","3":"Now automatically highlights the current tag.","package":"javabrowser.vim","4":"javabrowser.vim","src_id":"2296","5":"2296","creation_date":"1062676255","6":"1062676255"},{"0":"588","vim_version":"6.0","1":"6.0","script_version":"1.12","2":"1.12","version_comment":"Small bug fix to remove unwanted echo for visibility.","3":"Small bug fix to remove unwanted echo for visibility.","package":"javabrowser.vim","4":"javabrowser.vim","src_id":"1918","5":"1918","creation_date":"1050413947","6":"1050413947"},{"0":"588","vim_version":"6.0","1":"6.0","script_version":"1.11","2":"1.11","version_comment":"1. Now interface methods are highlighted as public, abstract. I missed  the abstract part in  the previous version.\r\n2. The visibility modifier (public\/protected\/private) can now be anywhere in the method\/field declaration and it will be highlighted correctly.","3":"1. Now interface methods are highlighted as public, abstract. I missed  the abstract part in  the previous version.\r\n2. The visibility modifier (public\/protected\/private) can now be anywhere in the method\/field declaration and it will be highlighted correctly.","package":"javabrowser.vim","4":"javabrowser.vim","src_id":"1916","5":"1916","creation_date":"1050331598","6":"1050331598"}]},"587":{"script_id":"587","0":"587","script_name":"fgl.c","1":"fgl.c","script_type":"utility","2":"utility","summary":"Creating tags for INFORMIX 4GL\/4Js programs under UNIX environment","3":"Creating tags for INFORMIX 4GL\/4Js programs under UNIX environment","description":"The zip file contains three files - fgl.c, parsers.h, and source.mak.\r\n\r\nWhen 'fgl.c' file in fgl.zip is compiled with exuberant ctags source files, which you can download, ctags(executable) will generate tags for functions, cursor ids, prepared statements id, and global\/module level variables. I compiled exuberant ctags source in AIX and Linux without any problem. Only trouble I faced was that source codes in ctags-5.4 tar file had DOS line breaks and had to translate them to UNIX line breaks using dos2unix utility.\r\n\r\nIf you use taglist.vim, add the following lines in taglist.vim script. \r\nScroll down the script to a section where tag types are defined for different languages:\r\n- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - \r\n\" fgl language\r\nlet s:tlist_def_fgl_settings = 'fgl;f:function;c:cursor;s:prepared;v:variable'\r\n- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - \r\n","4":"The zip file contains three files - fgl.c, parsers.h, and source.mak.\r\n\r\nWhen 'fgl.c' file in fgl.zip is compiled with exuberant ctags source files, which you can download, ctags(executable) will generate tags for functions, cursor ids, prepared statements id, and global\/module level variables. I compiled exuberant ctags source in AIX and Linux without any problem. Only trouble I faced was that source codes in ctags-5.4 tar file had DOS line breaks and had to translate them to UNIX line breaks using dos2unix utility.\r\n\r\nIf you use taglist.vim, add the following lines in taglist.vim script. \r\nScroll down the script to a section where tag types are defined for different languages:\r\n- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - \r\n\" fgl language\r\nlet s:tlist_def_fgl_settings = 'fgl;f:function;c:cursor;s:prepared;v:variable'\r\n- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - \r\n","install_details":"1. Download Exuberant ctags source at \"http:\/\/sourceforge.net\/project\/showfiles.php?group_id=6556\" and decompress into a directory\r\n2. Unzip fgl.zip file to the same source directory.\r\n3. You should convert DOS line breaks to UNIX line breaks if necessary\r\n4. Type \". .\/configure\" in the directory\r\n5. Type \"make\" to compile source codes\r\n6. Copy ctags(executable) to a directory whose execution path is recognized\r\n7. Add the following line to .vimrc\/.gvimrc to set tag option in vim\/gvim\r\n    set tag=tags\r\n    This line tells vim to look for a file 'tags' in the current directory. You may want to specify the path as well (ex. set tag=~\/tmp\/tags) to put the output to another directory. Also you can set more than a tag file separated by a space. \r\n8. Type \"ctags *.4gl\" in your 4GL program directory. This will create a tag file in the current directory. Using -f option, you can put the output tag file in another directory. In this case, just make sure that vim's tag option (in .vimrc) is set to a right directory. (For more help, type 'ctags --help')\r\n9. Now you are ready to use tags in vim\/gvim\/vi.  Open a 4gl file -> place the cursor on tag(function, 4GL cursor, ..) -> press CTRL+]  to jump to its definition, or CTRL+t to jump back\r\n","5":"1. Download Exuberant ctags source at \"http:\/\/sourceforge.net\/project\/showfiles.php?group_id=6556\" and decompress into a directory\r\n2. Unzip fgl.zip file to the same source directory.\r\n3. You should convert DOS line breaks to UNIX line breaks if necessary\r\n4. Type \". .\/configure\" in the directory\r\n5. Type \"make\" to compile source codes\r\n6. Copy ctags(executable) to a directory whose execution path is recognized\r\n7. Add the following line to .vimrc\/.gvimrc to set tag option in vim\/gvim\r\n    set tag=tags\r\n    This line tells vim to look for a file 'tags' in the current directory. You may want to specify the path as well (ex. set tag=~\/tmp\/tags) to put the output to another directory. Also you can set more than a tag file separated by a space. \r\n8. Type \"ctags *.4gl\" in your 4GL program directory. This will create a tag file in the current directory. Using -f option, you can put the output tag file in another directory. In this case, just make sure that vim's tag option (in .vimrc) is set to a right directory. (For more help, type 'ctags --help')\r\n9. Now you are ready to use tags in vim\/gvim\/vi.  Open a 4gl file -> place the cursor on tag(function, 4GL cursor, ..) -> press CTRL+]  to jump to its definition, or CTRL+t to jump back\r\n","first_name":"Tim","6":"Tim","last_name":"Kim","7":"Kim","releases":[{"0":"587","vim_version":"6.0","1":"6.0","script_version":"1.7","2":"1.7","version_comment":"Added a logic to recognize report function","3":"Added a logic to recognize report function","package":"fgl.zip","4":"fgl.zip","src_id":"9619","5":"9619","creation_date":"1228535696","6":"1228535696"},{"0":"587","vim_version":"6.0","1":"6.0","script_version":"1.6","2":"1.6","version_comment":"Fix for recognizing curly brackets for comments","3":"Fix for recognizing curly brackets for comments","package":"fgl.zip","4":"fgl.zip","src_id":"9410","5":"9410","creation_date":"1225237672","6":"1225237672"},{"0":"587","vim_version":"6.0","1":"6.0","script_version":"1.5","2":"1.5","version_comment":"A bug fix when comment finishes with a curly bracket.","3":"A bug fix when comment finishes with a curly bracket.","package":"fgl.zip","4":"fgl.zip","src_id":"8974","5":"8974","creation_date":"1216480982","6":"1216480982"},{"0":"587","vim_version":"6.0","1":"6.0","script_version":"1.4","2":"1.4","version_comment":"Catches variables ending with comment\r\n(ex. define  xxx char(1)   #bla blas)\r\n","3":"Catches variables ending with comment\r\n(ex. define  xxx char(1)   #bla blas)\r\n","package":"fgl.zip","4":"fgl.zip","src_id":"8929","5":"8929","creation_date":"1215801312","6":"1215801312"},{"0":"587","vim_version":"6.0","1":"6.0","script_version":"1.3","2":"1.3","version_comment":"A few bugs fixed","3":"A few bugs fixed","package":"fgl.zip","4":"fgl.zip","src_id":"8917","5":"8917","creation_date":"1215623687","6":"1215623687"},{"0":"587","vim_version":"6.0","1":"6.0","script_version":"1.2","2":"1.2","version_comment":"Improved code efficiency -> faster to create tags","3":"Improved code efficiency -> faster to create tags","package":"fgl.zip","4":"fgl.zip","src_id":"8884","5":"8884","creation_date":"1215109701","6":"1215109701"},{"0":"587","vim_version":"6.0","1":"6.0","script_version":"1.1","2":"1.1","version_comment":"Cursor id, prepared statement id, variables are added for tag creation. (global and module scope variables are add. The names of variable should start g_xxx, m_xxx, respectively. Other naming conventions change the prefix in fgl.c)","3":"Cursor id, prepared statement id, variables are added for tag creation. (global and module scope variables are add. The names of variable should start g_xxx, m_xxx, respectively. Other naming conventions change the prefix in fgl.c)","package":"fgl.zip","4":"fgl.zip","src_id":"8864","5":"8864","creation_date":"1214645288","6":"1214645288"},{"0":"587","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"fgl.tar","4":"fgl.tar","src_id":"1825","5":"1825","creation_date":"1047990201","6":"1047990201"}]},"586":{"script_id":"586","0":"586","script_name":"northsky","1":"northsky","script_type":"color scheme","2":"color scheme","summary":"The dark soft colorsheme","3":"The dark soft colorsheme","description":"Colorsheme for programmer's inflamed eyes :)\r\nScreenshots:\r\nhttp:\/\/sites.google.com\/site\/khorser\/_\/rsrc\/1260798469256\/opensource\/vim\/northsky.png\r\nhttp:\/\/sites.google.com\/site\/khorser\/_\/rsrc\/1260798491251\/opensource\/vim\/northskydiff.png\r\n","4":"Colorsheme for programmer's inflamed eyes :)\r\nScreenshots:\r\nhttp:\/\/sites.google.com\/site\/khorser\/_\/rsrc\/1260798469256\/opensource\/vim\/northsky.png\r\nhttp:\/\/sites.google.com\/site\/khorser\/_\/rsrc\/1260798491251\/opensource\/vim\/northskydiff.png\r\n","install_details":"Copy to $VIMRUNTIME\/colors\r\n\r\nAlso available on https:\/\/bitbucket.org\/khorser\/vim-northsky and https:\/\/github.com\/khorser\/vim-northsky","5":"Copy to $VIMRUNTIME\/colors\r\n\r\nAlso available on https:\/\/bitbucket.org\/khorser\/vim-northsky and https:\/\/github.com\/khorser\/vim-northsky","first_name":"Sergey","6":"Sergey","last_name":"Khorev","7":"Khorev","releases":[{"0":"586","vim_version":"7.0","1":"7.0","script_version":"2.2","2":"2.2","version_comment":"Add some support for 256 and 88-color terminals.","3":"Add some support for 256 and 88-color terminals.","package":"northsky.vim","4":"northsky.vim","src_id":"19128","5":"19128","creation_date":"1354866628","6":"1354866628"},{"0":"586","vim_version":"6.0","1":"6.0","script_version":"2.1","2":"2.1","version_comment":"Make String and Identifier colors more distinguishable.","3":"Make String and Identifier colors more distinguishable.","package":"northsky.vim","4":"northsky.vim","src_id":"12310","5":"12310","creation_date":"1265368730","6":"1265368730"},{"0":"586","vim_version":"6.0","1":"6.0","script_version":"2.0","2":"2.0","version_comment":"Major overhaul: removed some bright colors and bold attribute from most groups, tweaked search and diff colors","3":"Major overhaul: removed some bright colors and bold attribute from most groups, tweaked search and diff colors","package":"northsky.vim","4":"northsky.vim","src_id":"12199","5":"12199","creation_date":"1264581860","6":"1264581860"},{"0":"586","vim_version":"7.0","1":"7.0","script_version":"1.1","2":"1.1","version_comment":"Changed some colors (particularly got rid of some bright ones), added new highlight groups.","3":"Changed some colors (particularly got rid of some bright ones), added new highlight groups.","package":"northsky.vim","4":"northsky.vim","src_id":"11900","5":"11900","creation_date":"1260798812","6":"1260798812"},{"0":"586","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Updated with a revision which have been in use for years now: added new highlight groups, improved terminal colors","3":"Updated with a revision which have been in use for years now: added new highlight groups, improved terminal colors","package":"northsky.vim","4":"northsky.vim","src_id":"11859","5":"11859","creation_date":"1259932067","6":"1259932067"},{"0":"586","vim_version":"6.0","1":"6.0","script_version":"0.4","2":"0.4","version_comment":"Changed fgcolor for Search group, added terminal support.","3":"Changed fgcolor for Search group, added terminal support.","package":"northsky.vim","4":"northsky.vim","src_id":"4293","5":"4293","creation_date":"1116488226","6":"1116488226"},{"0":"586","vim_version":"6.0","1":"6.0","script_version":"0.3","2":"0.3","version_comment":"Highlight for search was made softer.","3":"Highlight for search was made softer.","package":"northsky.vim","4":"northsky.vim","src_id":"3133","5":"3133","creation_date":"1087279998","6":"1087279998"}]},"585":{"script_id":"585","0":"585","script_name":"todolist.vim","1":"todolist.vim","script_type":"utility","2":"utility","summary":"Creates list of TODO, FIXME, BUG comments","3":"Creates list of TODO, FIXME, BUG comments","description":"This is my first vim script and there are plenty of bugs.  If you can help out, please do.\r\n\r\nThis script is a plugin to be used with the winmanager plugin (see vimscript #95).  The script searches all your buffers for TODO, FIXME, NOTE, BUG, XXX comments found in your code and presents them in a list.  You can sort the list by type, file, line number, date, or by the text of the todo.  You can also customize the columns in the todo list.\r\n\r\nCommands:\r\n=========\r\n\r\n<cr> : open todo under cursor\r\np : [p]review todo under cursor\r\nC-w z : close preview window\r\nx : zoom todo list window\r\ns : cycle [s]ort field\r\nc : toggle preview on [C]ursorHold\r\ny : toggle s[y]ntax\r\nr : [r]everse sort\r\n? : toggle help\r\n","4":"This is my first vim script and there are plenty of bugs.  If you can help out, please do.\r\n\r\nThis script is a plugin to be used with the winmanager plugin (see vimscript #95).  The script searches all your buffers for TODO, FIXME, NOTE, BUG, XXX comments found in your code and presents them in a list.  You can sort the list by type, file, line number, date, or by the text of the todo.  You can also customize the columns in the todo list.\r\n\r\nCommands:\r\n=========\r\n\r\n<cr> : open todo under cursor\r\np : [p]review todo under cursor\r\nC-w z : close preview window\r\nx : zoom todo list window\r\ns : cycle [s]ort field\r\nc : toggle preview on [C]ursorHold\r\ny : toggle s[y]ntax\r\nr : [r]everse sort\r\n? : toggle help\r\n","install_details":"0) Install the winmanager plugin\r\n1) copy the todolist.vim script to your .vim\/plugin directory\r\n2) Add the string \"TodoList\" to your g:winManagerWindowLayout variable, eg:\r\n    let g:winManagerWindowLayout = 'TodoList,FileExplorer|BufExplorer'\r\n3) (Re)start vim and run :WMToggle","5":"0) Install the winmanager plugin\r\n1) copy the todolist.vim script to your .vim\/plugin directory\r\n2) Add the string \"TodoList\" to your g:winManagerWindowLayout variable, eg:\r\n    let g:winManagerWindowLayout = 'TodoList,FileExplorer|BufExplorer'\r\n3) (Re)start vim and run :WMToggle","first_name":"kevin","6":"kevin","last_name":"krouse","7":"krouse","releases":[{"0":"585","vim_version":"6.0","1":"6.0","script_version":"0.0alpha","2":"0.0alpha","version_comment":"Initial upload","3":"Initial upload","package":"todolist.vim","4":"todolist.vim","src_id":"1816","5":"1816","creation_date":"1047851203","6":"1047851203"}]},"584":{"script_id":"584","0":"584","script_name":"pyljpost.vim","1":"pyljpost.vim","script_type":"utility","2":"utility","summary":"vim + python livejournal poster","3":"vim + python livejournal poster","description":"A couple of vim macro along with the simple Livejournal poster written in python. Macros include syntax\r\nfile for livejournal posts, templatabiliy, multiple journals and a couple of other minor features. Together this makes a simple vim-oriented livejournal client for those who doesn't like to leave their favourite editor.","4":"A couple of vim macro along with the simple Livejournal poster written in python. Macros include syntax\r\nfile for livejournal posts, templatabiliy, multiple journals and a couple of other minor features. Together this makes a simple vim-oriented livejournal client for those who doesn't like to leave their favourite editor.","install_details":"Installation is completely by hand now, though pretty easy, and described in included README file.","5":"Installation is completely by hand now, though pretty easy, and described in included README file.","first_name":"Wartan","6":"Wartan","last_name":"Hachaturow","7":"Hachaturow","releases":[{"0":"584","vim_version":"6.0","1":"6.0","script_version":"0.0.1","2":"0.0.1","version_comment":"Initial upload","3":"Initial upload","package":"pyljvim-0.0.1.tar.gz","4":"pyljvim-0.0.1.tar.gz","src_id":"1815","5":"1815","creation_date":"1047787195","6":"1047787195"}]},"583":{"script_id":"583","0":"583","script_name":"comment.vim","1":"comment.vim","script_type":"utility","2":"utility","summary":"Comment and uncomment selected blocks of code.","3":"Comment and uncomment selected blocks of code.","description":"This script contains two simple functions to comment and uncomment visually selected blocks of C and C++ code using \"#ifdef 0...#endif\".   If'd out sections are commented with the author's name and a timestamp.\r\n\r\nThe default mappings are .c to comment and .C to uncomment.\r\n\r\ne.x.\r\n#if 0 \/* author Tue Mar 25 19:08:09 EST 2003 *\/\r\n...\r\n#endif \/* author Tue Mar 25 19:08:09 EST 2003 *\/\r\n","4":"This script contains two simple functions to comment and uncomment visually selected blocks of C and C++ code using \"#ifdef 0...#endif\".   If'd out sections are commented with the author's name and a timestamp.\r\n\r\nThe default mappings are .c to comment and .C to uncomment.\r\n\r\ne.x.\r\n#if 0 \/* author Tue Mar 25 19:08:09 EST 2003 *\/\r\n...\r\n#endif \/* author Tue Mar 25 19:08:09 EST 2003 *\/\r\n","install_details":"Copy comment.vim to your plugin directory or source it in your .vimrc.\r\nSet the variable g:Author if you would like the  author's name to appear in the commented out block.","5":"Copy comment.vim to your plugin directory or source it in your .vimrc.\r\nSet the variable g:Author if you would like the  author's name to appear in the commented out block.","first_name":"Mike","6":"Mike","last_name":"S","7":"S","releases":[{"0":"583","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"comment.vim","4":"comment.vim","src_id":"1813","5":"1813","creation_date":"1047639344","6":"1047639344"}]},"582":{"script_id":"582","0":"582","script_name":"matlab.vim","1":"matlab.vim","script_type":"syntax","2":"syntax","summary":"Syntax highlighting for Matlab files","3":"Syntax highlighting for Matlab files","description":"Syntax highlighting for Matlab files with\r\nlist of MATLAB standard functions,\r\nControl System Toolbox","4":"Syntax highlighting for Matlab files with\r\nlist of MATLAB standard functions,\r\nControl System Toolbox","install_details":"Just decompress and\r\nput it in your ~\/.vim\/syntax directory","5":"Just decompress and\r\nput it in your ~\/.vim\/syntax directory","first_name":"Kruchy","6":"Kruchy","last_name":"","7":"","releases":[{"0":"582","vim_version":"6.0","1":"6.0","script_version":"1.2","2":"1.2","version_comment":"Added Control System Toolbox functions","3":"Added Control System Toolbox functions","package":"matlab.zip","4":"matlab.zip","src_id":"1817","5":"1817","creation_date":"1047864869","6":"1047864869"},{"0":"582","vim_version":"6.0","1":"6.0","script_version":"1.1","2":"1.1","version_comment":"Initial upload","3":"Initial upload","package":"matlab.zip","4":"matlab.zip","src_id":"1811","5":"1811","creation_date":"1047633827","6":"1047633827"}]},"581":{"script_id":"581","0":"581","script_name":"cg.vim","1":"cg.vim","script_type":"syntax","2":"syntax","summary":"Syntax for Cg and FX hardware-shading language files","3":"Syntax for Cg and FX hardware-shading language files","description":"Syntax and keyword highlighting for the Cg shader-programming language, used in game programming and plugins for 3dsMax, Maya, etc.\r\n\r\nThis file is appropriate for .cg and .fx files.\r\n\r\nDetails, see http:\/\/www.cgshaders.org\/ or http:\/\/developer.nvidia.com\/\r\n\r\nCan also be used for Microsoft HLSL files.\r\n\r\nKevin Bjorke\r\nmailto:kbjorke@nvidia.com","4":"Syntax and keyword highlighting for the Cg shader-programming language, used in game programming and plugins for 3dsMax, Maya, etc.\r\n\r\nThis file is appropriate for .cg and .fx files.\r\n\r\nDetails, see http:\/\/www.cgshaders.org\/ or http:\/\/developer.nvidia.com\/\r\n\r\nCan also be used for Microsoft HLSL files.\r\n\r\nKevin Bjorke\r\nmailto:kbjorke@nvidia.com","install_details":"Install normally: add cg.vim to $VIMRUNTIME\/syntax then add rules for .cg and .fx files to $VIMRUNTIME\/filetype.vim -- gvim users should also add a Cg item to $VIMRUNTIME\/menu.vim","5":"Install normally: add cg.vim to $VIMRUNTIME\/syntax then add rules for .cg and .fx files to $VIMRUNTIME\/filetype.vim -- gvim users should also add a Cg item to $VIMRUNTIME\/menu.vim","first_name":"Kevin","6":"Kevin","last_name":"Bjorke","7":"Bjorke","releases":[{"0":"581","vim_version":"6.0","1":"6.0","script_version":"1","2":"1","version_comment":"Initial upload","3":"Initial upload","package":"cg.vim","4":"cg.vim","src_id":"1801","5":"1801","creation_date":"1047459785","6":"1047459785"}]},"580":{"script_id":"580","0":"580","script_name":"autonumbering in vim","1":"autonumbering in vim","script_type":"utility","2":"utility","summary":"Utility script to autonumber lines while editing","3":"Utility script to autonumber lines while editing","description":"\"Description: This script auto-numbers a list.\r\n\"\r\n\"General recommended settings for editing \"*.txt\" files\r\n\"set nocp et ts=4 sw=4 tw=80 ai\r\n\"\r\n\"HOW TO INSTALL (requires vim 7.0):\r\n\" - Drop the plugin under $HOME\/.vim\/plugin or\r\n\" - :source autonum.vim\r\n\"\r\n\"HOW TO USE:\r\n\" 1. Edit a file and type \\as to activate autonumbering\r\n\" 2. Insert a number in the below-explained manner (1. )\r\n\" 3. Hit enter (A number is automatically inserted for you)\r\n\" 4. Hit ctrl-t, line is indented and numbered\r\n\" 5. If there are several levels of numbers, ctrl-d and ctrl-t could\r\n\"    be used to insert the next number in sequence at the indent level\r\n\"    your cursor is in.\r\n\" 6. Hit ctrl-g to remove the inserted number\r\n\" 7. Hit ctrl-l to forcefully autonumber\r\n\"\r\n\"Number format expected: \"\\<\\(\\d\\+\\|\\a\\)\\>\\W \"\r\n\" In words: <word-boundary><(numerals or alphabets)><non-word-char><space>\r\n\" eg: \"1. \",     \"32) \",         \"a] \",     \"D> \"\r\n\"\r\n\" keymappings: ENTER, ctrl-d, ctrl-t, ctlr-l & ctrl-g all in insert mode\r\n\"  \\as   : To start AutoNumbering\r\n\"  \\as   : To stop AutoNumbering (yeah, it toggles :)\r\n\"  ENTER : start with next number (add 1 to previous)\r\n\"  ctrl-d: indent one level back and try to autonumber\r\n\"  ctrl-t: indent one level forward and try to autonumber\r\n\"  ctrl-l: autonumber.\r\n\"  ctrl-g: remove numbering on the line\r\n","4":"\"Description: This script auto-numbers a list.\r\n\"\r\n\"General recommended settings for editing \"*.txt\" files\r\n\"set nocp et ts=4 sw=4 tw=80 ai\r\n\"\r\n\"HOW TO INSTALL (requires vim 7.0):\r\n\" - Drop the plugin under $HOME\/.vim\/plugin or\r\n\" - :source autonum.vim\r\n\"\r\n\"HOW TO USE:\r\n\" 1. Edit a file and type \\as to activate autonumbering\r\n\" 2. Insert a number in the below-explained manner (1. )\r\n\" 3. Hit enter (A number is automatically inserted for you)\r\n\" 4. Hit ctrl-t, line is indented and numbered\r\n\" 5. If there are several levels of numbers, ctrl-d and ctrl-t could\r\n\"    be used to insert the next number in sequence at the indent level\r\n\"    your cursor is in.\r\n\" 6. Hit ctrl-g to remove the inserted number\r\n\" 7. Hit ctrl-l to forcefully autonumber\r\n\"\r\n\"Number format expected: \"\\<\\(\\d\\+\\|\\a\\)\\>\\W \"\r\n\" In words: <word-boundary><(numerals or alphabets)><non-word-char><space>\r\n\" eg: \"1. \",     \"32) \",         \"a] \",     \"D> \"\r\n\"\r\n\" keymappings: ENTER, ctrl-d, ctrl-t, ctlr-l & ctrl-g all in insert mode\r\n\"  \\as   : To start AutoNumbering\r\n\"  \\as   : To stop AutoNumbering (yeah, it toggles :)\r\n\"  ENTER : start with next number (add 1 to previous)\r\n\"  ctrl-d: indent one level back and try to autonumber\r\n\"  ctrl-t: indent one level forward and try to autonumber\r\n\"  ctrl-l: autonumber.\r\n\"  ctrl-g: remove numbering on the line\r\n","install_details":"drop it under ~\/.vim\/plugin\r\nOR\r\n:source autonum.vim\r\ninside vim session","5":"drop it under ~\/.vim\/plugin\r\nOR\r\n:source autonum.vim\r\ninside vim session","first_name":"Arun","6":"Arun","last_name":"E","7":"E","releases":[{"0":"580","vim_version":"7.0","1":"7.0","script_version":"2.0","2":"2.0","version_comment":"A complete rewrite, this one supports alphabets too as numbered list!","3":"A complete rewrite, this one supports alphabets too as numbered list!","package":"autonum.vim","4":"autonum.vim","src_id":"9393","5":"9393","creation_date":"1224803203","6":"1224803203"},{"0":"580","vim_version":"6.0","1":"6.0","script_version":"1.00","2":"1.00","version_comment":"Initial upload","3":"Initial upload","package":"autonum.vim","4":"autonum.vim","src_id":"1788","5":"1788","creation_date":"1047242774","6":"1047242774"}]},"579":{"script_id":"579","0":"579","script_name":"fgl.vim","1":"fgl.vim","script_type":"indent","2":"indent","summary":"Indent script for IBM INFORMIX 4GL\/4Js programs","3":"Indent script for IBM INFORMIX 4GL\/4Js programs","description":"The script indents IBM INFORMIX 4GL\/4Js programs.\r\n\r\nAuto-indent happens when you go to the next line or next word after typing\r\n1. A whole keyword (e.g. ELSE, WHEN, ON, ...)\r\n2. A keyword phrase (e.g \"BEFORE FIELD\", \"AFTER FIELD\").\r\n","4":"The script indents IBM INFORMIX 4GL\/4Js programs.\r\n\r\nAuto-indent happens when you go to the next line or next word after typing\r\n1. A whole keyword (e.g. ELSE, WHEN, ON, ...)\r\n2. A keyword phrase (e.g \"BEFORE FIELD\", \"AFTER FIELD\").\r\n","install_details":"1. Place the script(fgl.vim) in \"indent\" directory, which is found where vim editor is installed.\r\n2. Add the following lines in .vimrc\/.gvimrc\/_vimrc\r\n- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - \r\nset et ts=3 sw=3 ai\r\nfiletype indent on\r\n- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - ","5":"1. Place the script(fgl.vim) in \"indent\" directory, which is found where vim editor is installed.\r\n2. Add the following lines in .vimrc\/.gvimrc\/_vimrc\r\n- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - \r\nset et ts=3 sw=3 ai\r\nfiletype indent on\r\n- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - ","first_name":"Tim","6":"Tim","last_name":"Kim","7":"Kim","releases":[{"0":"579","vim_version":"6.0","1":"6.0","script_version":"1.2","2":"1.2","version_comment":"Handling multi line statement\r\n","3":"Handling multi line statement\r\n","package":"fgl.vim","4":"fgl.vim","src_id":"12591","5":"12591","creation_date":"1268252114","6":"1268252114"},{"0":"579","vim_version":"6.0","1":"6.0","script_version":"1.12","2":"1.12","version_comment":"Bug fix :\r\nProblem : The ELSE statement is not unindented.\r\nIt's fixed.\r\n","3":"Bug fix :\r\nProblem : The ELSE statement is not unindented.\r\nIt's fixed.\r\n","package":"fgl.vim","4":"fgl.vim","src_id":"1795","5":"1795","creation_date":"1047302529","6":"1047302529"}]},"578":{"script_id":"578","0":"578","script_name":"allfold","1":"allfold","script_type":"utility","2":"utility","summary":"View selected lines by folding away the rest","3":"View selected lines by folding away the rest","description":"The allfold scripts implement a feature set which allows VIM users to view ALL interesting lines in a buffer and FOLD the rest away.  Lines are selected to be interesting in one of the two following ways: \r\n\r\n1. They match a regular expression pattern.\r\n2. They are in a block of lines delimited inclusively by a line that matches\r\n   a beginning RE pattern and a line that matches an ending RE pattern.\r\n\r\nSets of lines matching different selection criteria can be combined using logical \"and\" and \"or\" operations. The selections may be inverted so that lines not matching the selection criteria are actually selected.\r\n\r\nBeyond these basics other features do such things as manipulating lists of selection commands and using the raw selection \"bit-map\" directly to enhance the capabilities and ease of use of the scripts.\r\n","4":"The allfold scripts implement a feature set which allows VIM users to view ALL interesting lines in a buffer and FOLD the rest away.  Lines are selected to be interesting in one of the two following ways: \r\n\r\n1. They match a regular expression pattern.\r\n2. They are in a block of lines delimited inclusively by a line that matches\r\n   a beginning RE pattern and a line that matches an ending RE pattern.\r\n\r\nSets of lines matching different selection criteria can be combined using logical \"and\" and \"or\" operations. The selections may be inverted so that lines not matching the selection criteria are actually selected.\r\n\r\nBeyond these basics other features do such things as manipulating lists of selection commands and using the raw selection \"bit-map\" directly to enhance the capabilities and ease of use of the scripts.\r\n","install_details":"See readme.txt in the package.","5":"See readme.txt in the package.","first_name":"Marion","6":"Marion","last_name":"Berryman","7":"Berryman","releases":[{"0":"578","vim_version":"6.0","1":"6.0","script_version":"0.6","2":"0.6","version_comment":"Initial upload","3":"Initial upload","package":"allfold.tar.gz","4":"allfold.tar.gz","src_id":"1774","5":"1774","creation_date":"1046434141","6":"1046434141"}]},"577":{"script_id":"577","0":"577","script_name":"dawn","1":"dawn","script_type":"color scheme","2":"color scheme","summary":"Soft colors on a light grey background (GUI only)","3":"Soft colors on a light grey background (GUI only)","description":"Dawn is for the GUI only. It is a more muted and lower contrast version of the default and morning color schemes. \r\n\r\nA companion color scheme with a dark blue-black background is dusk (vimscript #758).","4":"Dawn is for the GUI only. It is a more muted and lower contrast version of the default and morning color schemes. \r\n\r\nA companion color scheme with a dark blue-black background is dusk (vimscript #758).","install_details":"Place dawn.vim in $HOME\/.vim\/colors (Unix) or %HOME%\\vimfiles\\colors\\ (MSWin) and add the line:\r\ncolorscheme dawn\r\nto your vimrc file.","5":"Place dawn.vim in $HOME\/.vim\/colors (Unix) or %HOME%\\vimfiles\\colors\\ (MSWin) and add the line:\r\ncolorscheme dawn\r\nto your vimrc file.","first_name":"Ajit","6":"Ajit","last_name":"Thakkar","7":"Thakkar","releases":[{"0":"577","vim_version":"6.0","1":"6.0","script_version":"1.5","2":"1.5","version_comment":"Remove bold attribute throughout. Minor tweaks.","3":"Remove bold attribute throughout. Minor tweaks.","package":"dawn.vim","4":"dawn.vim","src_id":"4807","5":"4807","creation_date":"1132833100","6":"1132833100"},{"0":"577","vim_version":"6.0","1":"6.0","script_version":"1.2","2":"1.2","version_comment":"A few changes in syntax highlighting colors to reduce contrast","3":"A few changes in syntax highlighting colors to reduce contrast","package":"dawn.vim","4":"dawn.vim","src_id":"2186","5":"2186","creation_date":"1059117567","6":"1059117567"},{"0":"577","vim_version":"6.0","1":"6.0","script_version":"1.1","2":"1.1","version_comment":"Tweaks to reduce contrast in a few places","3":"Tweaks to reduce contrast in a few places","package":"dawn.vim","4":"dawn.vim","src_id":"1794","5":"1794","creation_date":"1047297400","6":"1047297400"},{"0":"577","vim_version":"6.0","1":"6.0","script_version":"1","2":"1","version_comment":"Initial upload","3":"Initial upload","package":"dawn.vim","4":"dawn.vim","src_id":"1770","5":"1770","creation_date":"1046322198","6":"1046322198"}]},"576":{"script_id":"576","0":"576","script_name":"psp.vim","1":"psp.vim","script_type":"syntax","2":"syntax","summary":"Syntax file for Python Server Pages","3":"Syntax file for Python Server Pages","description":"Syntax for PSP used in Webware (http:\/\/webware.sf.net).  ","4":"Syntax for PSP used in Webware (http:\/\/webware.sf.net).  ","install_details":"Stick it in $VIMRUNTIME\/syntax I believe.","5":"Stick it in $VIMRUNTIME\/syntax I believe.","first_name":"Tom","6":"Tom","last_name":"von Schwerdtner","7":"von Schwerdtner","releases":[{"0":"576","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"psp.vim","4":"psp.vim","src_id":"1769","5":"1769","creation_date":"1046257979","6":"1046257979"}]},"575":{"script_id":"575","0":"575","script_name":"gnu-c","1":"gnu-c","script_type":"ftplugin","2":"ftplugin","summary":"A filetype plugin to encourage the GNU C style.","3":"A filetype plugin to encourage the GNU C style.","description":"The GNU Coding Standards encourage the use of a C style not supported by default.  This script provides convenience support when editing C sources according to the C style guidelines encouraged in the Standards by overruling the default C ftplugin, which uses a style closer to the Linux kernel style.\r\n\r\nThe GNU Coding standards are available at:\r\n\r\n\thttp:\/\/www.gnu.org\/prep\/standards.html\r\n\r\nSee |C-Indenting| and |format-comments| for an idea of what the script does.\r\n","4":"The GNU Coding Standards encourage the use of a C style not supported by default.  This script provides convenience support when editing C sources according to the C style guidelines encouraged in the Standards by overruling the default C ftplugin, which uses a style closer to the Linux kernel style.\r\n\r\nThe GNU Coding standards are available at:\r\n\r\n\thttp:\/\/www.gnu.org\/prep\/standards.html\r\n\r\nSee |C-Indenting| and |format-comments| for an idea of what the script does.\r\n","install_details":"Just extract the (gzipped) tarball to your home directory (assuming a posix environment).","5":"Just extract the (gzipped) tarball to your home directory (assuming a posix environment).","first_name":"Dean","6":"Dean","last_name":"Scarff","7":"Scarff","releases":[{"0":"575","vim_version":"6.0","1":"6.0","script_version":"0.2","2":"0.2","version_comment":"play nicer with autoindent","3":"play nicer with autoindent","package":"gnu-c.tar.gz","4":"gnu-c.tar.gz","src_id":"3843","5":"3843","creation_date":"1107891583","6":"1107891583"}]},"574":{"script_id":"574","0":"574","script_name":"TEXT - fill char","1":"TEXT - fill char","script_type":"utility","2":"utility","summary":"script for on-the-fly indenting of columns according to previous or next line","3":"script for on-the-fly indenting of columns according to previous or next line","description":"Script for on-the-fly indenting of columns according\r\nto the previous or next line (it allows for instance to easily align\r\n'=' sign in a sequence of C initializations, and much more).\r\n\r\nEXAMPLE:\r\n\r\nline 1: background-color: _#eeeeee\r\nline 2: color:|\r\n\r\nChar | is cursor, char _ is space. \r\n\r\nAfter call :FillUpSpace (you can map to TAB) is \r\nsituation this:\r\n\r\nline 1: background-color:_#eeeeee\r\nline 2: color:___________|\r\n\r\nCursor is under #. It's all.\r\n\r\nYou can use :FillUpPrevious for fill any char (by char \r\nprevious cursor) \r\n\r\nEXAMPLE:\r\n\r\nline1: Chapter1 ...................... 7\r\nline2: Chapter2 .|\r\n\r\nAfter use :FillUpPrevious is situation this:\r\n\r\nline1: Chapter1 ...................... 7\r\nline2: Chapter2 ......................|\r\n","4":"Script for on-the-fly indenting of columns according\r\nto the previous or next line (it allows for instance to easily align\r\n'=' sign in a sequence of C initializations, and much more).\r\n\r\nEXAMPLE:\r\n\r\nline 1: background-color: _#eeeeee\r\nline 2: color:|\r\n\r\nChar | is cursor, char _ is space. \r\n\r\nAfter call :FillUpSpace (you can map to TAB) is \r\nsituation this:\r\n\r\nline 1: background-color:_#eeeeee\r\nline 2: color:___________|\r\n\r\nCursor is under #. It's all.\r\n\r\nYou can use :FillUpPrevious for fill any char (by char \r\nprevious cursor) \r\n\r\nEXAMPLE:\r\n\r\nline1: Chapter1 ...................... 7\r\nline2: Chapter2 .|\r\n\r\nAfter use :FillUpPrevious is situation this:\r\n\r\nline1: Chapter1 ...................... 7\r\nline2: Chapter2 ......................|\r\n","install_details":"","5":"","first_name":"Petr","6":"Petr","last_name":"Mach","7":"Mach","releases":[{"0":"574","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"TEXT_charFill.vim","4":"TEXT_charFill.vim","src_id":"1742","5":"1742","creation_date":"1045447305","6":"1045447305"}]},"573":{"script_id":"573","0":"573","script_name":"darkdot","1":"darkdot","script_type":"color scheme","2":"color scheme","summary":"yet another dark colorscheme","3":"yet another dark colorscheme","description":"This is a dark colorscheme that uses the colors found on http:\/\/slashdot.org. By this I mean that white, black and cyan are the most common colors, not that the programs will look like Slashdot postings.\r\n\r\nIt is a colorscheme both for the GUI and the console version of vim.\r\n\r\nThe latest version and a screenshot can be found at http:\/\/www.c7obs.net\/~david\/stuff\/","4":"This is a dark colorscheme that uses the colors found on http:\/\/slashdot.org. By this I mean that white, black and cyan are the most common colors, not that the programs will look like Slashdot postings.\r\n\r\nIt is a colorscheme both for the GUI and the console version of vim.\r\n\r\nThe latest version and a screenshot can be found at http:\/\/www.c7obs.net\/~david\/stuff\/","install_details":"","5":"","first_name":"David","6":"David","last_name":"Lazar","7":"Lazar","releases":[{"0":"573","vim_version":"7.0","1":"7.0","script_version":"2.7","2":"2.7","version_comment":"Changes the color of the matching parent to match the one of the cursor.","3":"Changes the color of the matching parent to match the one of the cursor.","package":"darkdot.vim","4":"darkdot.vim","src_id":"6097","5":"6097","creation_date":"1156487483","6":"1156487483"},{"0":"573","vim_version":"7.0","1":"7.0","script_version":"2.6","2":"2.6","version_comment":"Adds support for vim 7.0 (should still work with 6.x though).","3":"Adds support for vim 7.0 (should still work with 6.x though).","package":"darkdot.vim","4":"darkdot.vim","src_id":"5988","5":"5988","creation_date":"1153811826","6":"1153811826"},{"0":"573","vim_version":"6.0","1":"6.0","script_version":"2.5","2":"2.5","version_comment":"Minor updates. (the NonText color)","3":"Minor updates. (the NonText color)","package":"darkdot.vim","4":"darkdot.vim","src_id":"5679","5":"5679","creation_date":"1147354425","6":"1147354425"},{"0":"573","vim_version":"6.0","1":"6.0","script_version":"2.2","2":"2.2","version_comment":"- changed the vimdiff colors both on the console and the GUI version\r\n- minor updates in the gvim colors","3":"- changed the vimdiff colors both on the console and the GUI version\r\n- minor updates in the gvim colors","package":"darkdot.vim","4":"darkdot.vim","src_id":"3043","5":"3043","creation_date":"1085034772","6":"1085034772"},{"0":"573","vim_version":"6.0","1":"6.0","script_version":"2.0","2":"2.0","version_comment":"It has a little less contrast to be easier on the eyes.\r\n\r\nScreenshot at http:\/\/c7.campus.utcluj.ro\/~david\/darkdot2.png\r\n","3":"It has a little less contrast to be easier on the eyes.\r\n\r\nScreenshot at http:\/\/c7.campus.utcluj.ro\/~david\/darkdot2.png\r\n","package":"darkdot.vim","4":"darkdot.vim","src_id":"1911","5":"1911","creation_date":"1050160794","6":"1050160794"},{"0":"573","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"darkdot.vim","4":"darkdot.vim","src_id":"1739","5":"1739","creation_date":"1045383489","6":"1045383489"}]},"572":{"script_id":"572","0":"572","script_name":"wintersday.vim","1":"wintersday.vim","script_type":"color scheme","2":"color scheme","summary":"Dark color scheme","3":"Dark color scheme","description":"Another dark, color scheme.","4":"Another dark, color scheme.","install_details":"Place in your vimfiles\/colors\/ directory\r\n:colo wintersday","5":"Place in your vimfiles\/colors\/ directory\r\n:colo wintersday","first_name":"Mark","6":"Mark","last_name":"Thomas","7":"Thomas","releases":[{"0":"572","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"wintersday.vim","4":"wintersday.vim","src_id":"1738","5":"1738","creation_date":"1045377849","6":"1045377849"}]},"571":{"script_id":"571","0":"571","script_name":"autolisp-help","1":"autolisp-help","script_type":"utility","2":"utility","summary":"Vim style help file of Auto\/Visual Lisp functions","3":"Vim style help file of Auto\/Visual Lisp functions","description":"This is a Vim style help file of Auto\/Visual Lisp functions. \r\nPlace it in vimfiles\/doc\/ and use :helptags {dir} to generate\r\na new tags file. I also have this mapping in my vimrc file.\r\nmap <leader>hh :he <C-R><C-W><CR>\r\nPlace your cursor on a function and type '\\hh' or what ever you have 'leader' set to. \r\nOr can simply type :he <AutoLISP function> to open the help file to a function.\r\n\r\nSee Vim help\r\n :he helptags\r\n :he leader\r\n","4":"This is a Vim style help file of Auto\/Visual Lisp functions. \r\nPlace it in vimfiles\/doc\/ and use :helptags {dir} to generate\r\na new tags file. I also have this mapping in my vimrc file.\r\nmap <leader>hh :he <C-R><C-W><CR>\r\nPlace your cursor on a function and type '\\hh' or what ever you have 'leader' set to. \r\nOr can simply type :he <AutoLISP function> to open the help file to a function.\r\n\r\nSee Vim help\r\n :he helptags\r\n :he leader\r\n","install_details":"Place autolisp-help.txt in vimfiles\/doc\/\r\nUse :helptags {dir}\r\nExample :helptags $home\/vimfiles\/doc\r\nWhere $home = C:\/Documents and Settings\/Mark\/","5":"Place autolisp-help.txt in vimfiles\/doc\/\r\nUse :helptags {dir}\r\nExample :helptags $home\/vimfiles\/doc\r\nWhere $home = C:\/Documents and Settings\/Mark\/","first_name":"Mark","6":"Mark","last_name":"Thomas","7":"Thomas","releases":[{"0":"571","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"autolisp-help.zip","4":"autolisp-help.zip","src_id":"1737","5":"1737","creation_date":"1045377367","6":"1045377367"}]},"570":{"script_id":"570","0":"570","script_name":"GTK+","1":"GTK+","script_type":"syntax","2":"syntax","summary":"GTK+-2.2 syntax highlight","3":"GTK+-2.2 syntax highlight","description":"GTK+-2.2 syntax file. This contains xlib.vim, glib.vim, \r\npango.vim, gdk.vim and gtk.vim. All deprecated methods are\r\nnot highlighted. \r\n","4":"GTK+-2.2 syntax file. This contains xlib.vim, glib.vim, \r\npango.vim, gdk.vim and gtk.vim. All deprecated methods are\r\nnot highlighted. \r\n","install_details":"Make dir $HOME\/.vim\/after\/syntax\r\nuntar this file to $HOME\/.vim\/after\/syntax\r\nIf you don't have $HOME\/.vim\/after\/syntax\/c.vim, then copy  c.vim.example to $HOME\/.vim\/after\/syntax\/c.vim\r\n\r\nsee :h mysyntaxfile-add","5":"Make dir $HOME\/.vim\/after\/syntax\r\nuntar this file to $HOME\/.vim\/after\/syntax\r\nIf you don't have $HOME\/.vim\/after\/syntax\/c.vim, then copy  c.vim.example to $HOME\/.vim\/after\/syntax\/c.vim\r\n\r\nsee :h mysyntaxfile-add","first_name":"Hwanjin","6":"Hwanjin","last_name":"Choe","7":"Choe","releases":[{"0":"570","vim_version":"6.0","1":"6.0","script_version":"20030219","2":"20030219","version_comment":"Install instruction changed. Now, you need not to change syntax to gtk\r\nIf you open c file, automatically highlighted.\r\nThanks to David Necas (Yeti) <yeti at physics.muni.cz>","3":"Install instruction changed. Now, you need not to change syntax to gtk\r\nIf you open c file, automatically highlighted.\r\nThanks to David Necas (Yeti) <yeti at physics.muni.cz>","package":"gtk-20030219.tar.bz2","4":"gtk-20030219.tar.bz2","src_id":"1753","5":"1753","creation_date":"1045629121","6":"1045629121"},{"0":"570","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"gtk.tar.bz2","4":"gtk.tar.bz2","src_id":"1735","5":"1735","creation_date":"1045269191","6":"1045269191"}]},"569":{"script_id":"569","0":"569","script_name":"caramel.vim","1":"caramel.vim","script_type":"color scheme","2":"color scheme","summary":"Low eye strain color scheme, based off of the GIMP\\'s caramel pallette for GVIM","3":"Low eye strain color scheme, based off of the GIMP\\'s caramel pallette for GVIM","description":"Just a simple, low eye strain color scheme that is based off of the GIMP\\'s caramel color pallette.\r\n\r\nSyntax hilighting is fully fleshed out, as well as most window features.  Todo list is in header comments in file.\r\n\r\nScreenshot with C, COBOL and Perl highlighting is available at: http:\/\/entropy.muc.muohio.edu\/~afterthefall\/screen.jpg","4":"Just a simple, low eye strain color scheme that is based off of the GIMP\\'s caramel color pallette.\r\n\r\nSyntax hilighting is fully fleshed out, as well as most window features.  Todo list is in header comments in file.\r\n\r\nScreenshot with C, COBOL and Perl highlighting is available at: http:\/\/entropy.muc.muohio.edu\/~afterthefall\/screen.jpg","install_details":"Same as every other color file.","5":"Same as every other color file.","first_name":"Brian","6":"Brian","last_name":"Gant","7":"Gant","releases":[{"0":"569","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"caramel.vim","4":"caramel.vim","src_id":"1734","5":"1734","creation_date":"1045260006","6":"1045260006"}]},"568":{"script_id":"568","0":"568","script_name":"ntprocesses","1":"ntprocesses","script_type":"utility","2":"utility","summary":"Kill NT processes from Vim","3":"Kill NT processes from Vim","description":"PLEASE READ THE INSTALL SECTION COMPLETELY.\r\n\r\n- This plugin generates a list of NT processes that are running on the\r\n  local NT\/W2K\/XP machine. You can kill any by processing K on the\r\n  corresponding entry.\r\n- You can open the processlist window through WinManager (as described in\r\n  the installation section below) or by assigning a hot key. You can use\r\n  the same hot key to open\/close the window. Alternatively, you can also\r\n  use the :NTProcesses command to open\/close the processes window.\r\n- You can choose which fields that you want to see by using the\r\n  NtpFields command. You can select the sort fields by pressing s\r\n  consecutively and r for reversing the sort direction.\r\n- If you have permissions, you can view the process list in a remote m\/c\r\n  by using the NtpSetHost command. With no arguments, it prints the\r\n  current remote host name. To switch back to the local m\/c, use \".\" for\r\n  the host name.\r\n- For the sake of speed, the list of processes is cached. To see the\r\n  latest set of processes and their states at any time, refresh the window\r\n  by pressing 'R'.\r\n- It requires multvals and genutils plugins to be always installed, but\r\n  others are required only depending on your usage\/setting (for a better\r\n  experience and formatting).\r\n\r\n\r\nSearch_key_words: ntprocesses ntprocess NT processes process kill multvals genutils align Hari Krishna Dara ","4":"PLEASE READ THE INSTALL SECTION COMPLETELY.\r\n\r\n- This plugin generates a list of NT processes that are running on the\r\n  local NT\/W2K\/XP machine. You can kill any by processing K on the\r\n  corresponding entry.\r\n- You can open the processlist window through WinManager (as described in\r\n  the installation section below) or by assigning a hot key. You can use\r\n  the same hot key to open\/close the window. Alternatively, you can also\r\n  use the :NTProcesses command to open\/close the processes window.\r\n- You can choose which fields that you want to see by using the\r\n  NtpFields command. You can select the sort fields by pressing s\r\n  consecutively and r for reversing the sort direction.\r\n- If you have permissions, you can view the process list in a remote m\/c\r\n  by using the NtpSetHost command. With no arguments, it prints the\r\n  current remote host name. To switch back to the local m\/c, use \".\" for\r\n  the host name.\r\n- For the sake of speed, the list of processes is cached. To see the\r\n  latest set of processes and their states at any time, refresh the window\r\n  by pressing 'R'.\r\n- It requires multvals and genutils plugins to be always installed, but\r\n  others are required only depending on your usage\/setting (for a better\r\n  experience and formatting).\r\n\r\n\r\nSearch_key_words: ntprocesses ntprocess NT processes process kill multvals genutils align Hari Krishna Dara ","install_details":"- Place the plugin in a plugin diretory under runtimepath and configure\r\n  WinManager according to your taste. E.g:\r\n                                                                           \r\n    let g:winManagerWindowLayout = 'FileExplorer,NTProcesses'\r\n                                                                           \r\n  You can then switch between FileExplorer and NTProcesses by pressing ^N\r\n  and ^P.\r\n- If you don't want to use WinManager, you can still use the :NTProcesses\r\n  comamnd or assign a hotkey by placing the following in your vimrc:\r\n                                                                           \r\n    nmap <silent> <F6> <Plug>NTProcesses\r\n                                                                           \r\n  You can substitute any key or sequnce of keys for <F6> in the above map.\r\n- Requires multvals.vim to be installed. Download from:\r\n    http:\/\/www.vim.org\/script.php?script_id=171\r\n- Requires genutils.vim to be installed. Download from:\r\n    http:\/\/www.vim.org\/script.php?script_id=197\r\n- If Align.vim is installed, it is used to format the output.\r\n- Requires cscript.exe to be in the path.\r\n- Use g:ntprocFields, g:ntprocSortFieldIndex, g:ntprocSortDirection to\r\n  specify field names, default sort field and the sort direction\r\n  respectively. Use NtpFields command to see the list of field names\r\n  possible.\r\n","5":"- Place the plugin in a plugin diretory under runtimepath and configure\r\n  WinManager according to your taste. E.g:\r\n                                                                           \r\n    let g:winManagerWindowLayout = 'FileExplorer,NTProcesses'\r\n                                                                           \r\n  You can then switch between FileExplorer and NTProcesses by pressing ^N\r\n  and ^P.\r\n- If you don't want to use WinManager, you can still use the :NTProcesses\r\n  comamnd or assign a hotkey by placing the following in your vimrc:\r\n                                                                           \r\n    nmap <silent> <F6> <Plug>NTProcesses\r\n                                                                           \r\n  You can substitute any key or sequnce of keys for <F6> in the above map.\r\n- Requires multvals.vim to be installed. Download from:\r\n    http:\/\/www.vim.org\/script.php?script_id=171\r\n- Requires genutils.vim to be installed. Download from:\r\n    http:\/\/www.vim.org\/script.php?script_id=197\r\n- If Align.vim is installed, it is used to format the output.\r\n- Requires cscript.exe to be in the path.\r\n- Use g:ntprocFields, g:ntprocSortFieldIndex, g:ntprocSortDirection to\r\n  specify field names, default sort field and the sort direction\r\n  respectively. Use NtpFields command to see the list of field names\r\n  possible.\r\n","first_name":"Hari Krishna","6":"Hari Krishna","last_name":"Dara","7":"Dara","releases":[{"0":"568","vim_version":"6.0","1":"6.0","script_version":"1.4","2":"1.4","version_comment":"Maintenance release. Fixed broken NTSsetHost and NtpKill commands.","3":"Maintenance release. Fixed broken NTSsetHost and NtpKill commands.","package":"ntprocesses.vim","4":"ntprocesses.vim","src_id":"3267","5":"3267","creation_date":"1090607671","6":"1090607671"},{"0":"568","vim_version":"6.0","1":"6.0","script_version":"1.3","2":"1.3","version_comment":"Minor updates:\r\n- Fixed the bug in connecting to a remote host, basically it wasn't working.\r\n- NtpSetHost is now global, so you don't have to open the window before\r\n  switching to a remote host.\r\n- Check and not load if it is not windows (David Fishburn).\r\n","3":"Minor updates:\r\n- Fixed the bug in connecting to a remote host, basically it wasn't working.\r\n- NtpSetHost is now global, so you don't have to open the window before\r\n  switching to a remote host.\r\n- Check and not load if it is not windows (David Fishburn).\r\n","package":"ntprocesses.vim","4":"ntprocesses.vim","src_id":"2684","5":"2684","creation_date":"1075229662","6":"1075229662"},{"0":"568","vim_version":"6.0","1":"6.0","script_version":"1.2","2":"1.2","version_comment":"- Renamed NTpFields command to NtpFields.\r\n- Now genutils.vim plugin is required. Download it from http:\/\/www.vim.org\/script.php?script_id=197\r\n- Fixed a bug with buffer name on solaris.\r\n- New feature to connect to a remote host.\r\n- q to quit window.\r\n- Version dependency check on multvals and genutils plugin. You now get an error message during the Vim startup, if you don't have minimum required versions of these two dependent plugins.\r\n","3":"- Renamed NTpFields command to NtpFields.\r\n- Now genutils.vim plugin is required. Download it from http:\/\/www.vim.org\/script.php?script_id=197\r\n- Fixed a bug with buffer name on solaris.\r\n- New feature to connect to a remote host.\r\n- q to quit window.\r\n- Version dependency check on multvals and genutils plugin. You now get an error message during the Vim startup, if you don't have minimum required versions of these two dependent plugins.\r\n","package":"ntprocesses.vim","4":"ntprocesses.vim","src_id":"2611","5":"2611","creation_date":"1071686580","6":"1071686580"},{"0":"568","vim_version":"6.0","1":"6.0","script_version":"1.1","2":"1.1","version_comment":"Initial upload","3":"Initial upload","package":"ntprocesses.vim","4":"ntprocesses.vim","src_id":"1733","5":"1733","creation_date":"1045246633","6":"1045246633"}]},"567":{"script_id":"567","0":"567","script_name":"desc.vim","1":"desc.vim","script_type":"syntax","2":"syntax","summary":"Highlinting for ROCKLinux .desc files describing software packages","3":"Highlinting for ROCKLinux .desc files describing software packages","description":"ROCKLinux uses .desc files for description of packages. It contains tags stating what the packages are, who is the author\/maintainer of the package. It also describes download locations of the source needed to build the package and the moment when the package should be built.","4":"ROCKLinux uses .desc files for description of packages. It contains tags stating what the packages are, who is the author\/maintainer of the package. It also describes download locations of the source needed to build the package and the moment when the package should be built.","install_details":"As Usual. ;-)","5":"As Usual. ;-)","first_name":"Piotr","6":"Piotr","last_name":"Esden-Tempski","7":"Esden-Tempski","releases":[{"0":"567","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"desc.vim","4":"desc.vim","src_id":"1731","5":"1731","creation_date":"1045243320","6":"1045243320"}]},"566":{"script_id":"566","0":"566","script_name":"ctrlax.vim","1":"ctrlax.vim","script_type":"utility","2":"utility","summary":"Enhancement over <C-A> and <C-X> (plugin)","3":"Enhancement over <C-A> and <C-X> (plugin)","description":"The plugin implements an enhanced version of vim's incrementing features with\r\n<C-A> and <C-X> using functions to find and replace strings according to any\r\ninline scheme.\r\n\r\nBy default vim behaviour is emulated, plus it cycles through names of months\r\nand week days (trying full name, then abbreviated).\r\n\r\nThe language for months and week days is English, but it is fairly straight\r\nforward to localise this. An example of localisation is provided in the\r\ndocumentation.\r\n\r\nExtra functions meant to assist in writing new functions are included, too.","4":"The plugin implements an enhanced version of vim's incrementing features with\r\n<C-A> and <C-X> using functions to find and replace strings according to any\r\ninline scheme.\r\n\r\nBy default vim behaviour is emulated, plus it cycles through names of months\r\nand week days (trying full name, then abbreviated).\r\n\r\nThe language for months and week days is English, but it is fairly straight\r\nforward to localise this. An example of localisation is provided in the\r\ndocumentation.\r\n\r\nExtra functions meant to assist in writing new functions are included, too.","install_details":"$ cd ~\/.vim\r\n$ gzip -cd ..\/path\/to\/ctrlax-1.1.tgz | tar xvf -\r\n$ vim -c 'helptags doc | help ctrlax.txt'","5":"$ cd ~\/.vim\r\n$ gzip -cd ..\/path\/to\/ctrlax-1.1.tgz | tar xvf -\r\n$ vim -c 'helptags doc | help ctrlax.txt'","first_name":"Preben 'Peppe'","6":"Preben 'Peppe'","last_name":"Guldberg","7":"Guldberg","releases":[{"0":"566","vim_version":"6.0","1":"6.0","script_version":"1.1","2":"1.1","version_comment":"Changes:\r\n- All bundled functions are now used by default rather\r\n  than the script only mimicking vim.\r\n\r\nFixes:\r\n- Missing number conversion that caused weird behaviour.","3":"Changes:\r\n- All bundled functions are now used by default rather\r\n  than the script only mimicking vim.\r\n\r\nFixes:\r\n- Missing number conversion that caused weird behaviour.","package":"ctrlax-1.1.tgz","4":"ctrlax-1.1.tgz","src_id":"2180","5":"2180","creation_date":"1058958399","6":"1058958399"},{"0":"566","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"File had erroneously not been gzipped (tgz was hence a bad suffix)","3":"File had erroneously not been gzipped (tgz was hence a bad suffix)","package":"ctrlax.tgz","4":"ctrlax.tgz","src_id":"1725","5":"1725","creation_date":"1045097378","6":"1045097378"}]},"565":{"script_id":"565","0":"565","script_name":"HTML - insert","1":"HTML - insert","script_type":"utility","2":"utility","summary":"Script for easy insert HTML tag A href and IMG with filled attributes.","3":"Script for easy insert HTML tag A href and IMG with filled attributes.","description":"Script add command :IMG and :HREF for easy inserting xhtml elements IMG and ANCHOR.\r\n\r\nWithout parameter call file browser dialog for select file.\r\n\r\nIf Vim is not support browse() function (non GUI Vim), you must insert path manualy.\r\n\r\n:IMG command call identify (from ImageMagic) for detect geometry of image. ","4":"Script add command :IMG and :HREF for easy inserting xhtml elements IMG and ANCHOR.\r\n\r\nWithout parameter call file browser dialog for select file.\r\n\r\nIf Vim is not support browse() function (non GUI Vim), you must insert path manualy.\r\n\r\n:IMG command call identify (from ImageMagic) for detect geometry of image. ","install_details":"Add content from script file to .vimrc or _vimrc.\r\nOr read script file with command :source .\r\nOr insert script into plugin directory.","5":"Add content from script file to .vimrc or _vimrc.\r\nOr read script file with command :source .\r\nOr insert script into plugin directory.","first_name":"Petr","6":"Petr","last_name":"Mach","7":"Mach","releases":[{"0":"565","vim_version":"6.0","1":"6.0","script_version":"1.2","2":"1.2","version_comment":" big improvements\r\n      rename HTML_loadImg() to HTML_insertImg() and fix inserted tag for XHTML compatibility\r\n      create  HTML_insertHref() width new :HREF command\r\n      create Absolute2Relative() for make inserted path relative for files in up directory","3":" big improvements\r\n      rename HTML_loadImg() to HTML_insertImg() and fix inserted tag for XHTML compatibility\r\n      create  HTML_insertHref() width new :HREF command\r\n      create Absolute2Relative() for make inserted path relative for files in up directory","package":"HTML_insert.vim","4":"HTML_insert.vim","src_id":"1736","5":"1736","creation_date":"1045362621","6":"1045362621"},{"0":"565","vim_version":"6.0","1":"6.0","script_version":"1.1","2":"1.1","version_comment":"bugfix: parsing manually added image path","3":"bugfix: parsing manually added image path","package":"HTML_loadImg.vim","4":"HTML_loadImg.vim","src_id":"1726","5":"1726","creation_date":"1045100583","6":"1045100583"},{"0":"565","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"HTML_loadImg.vim","4":"HTML_loadImg.vim","src_id":"1723","5":"1723","creation_date":"1045063239","6":"1045063239"}]},"564":{"script_id":"564","0":"564","script_name":"ASPRecolor.vim","1":"ASPRecolor.vim","script_type":"ftplugin","2":"ftplugin","summary":"In ASPVBS buffers, give JS, ASP, and HTML sections different guibg colors","3":"In ASPVBS buffers, give JS, ASP, and HTML sections different guibg colors","description":"I edit ASP code a lot.  There's usually three different langauges in the same file: HTML, Vbscript, and Javascript.  The ASPVBS filetype plugin handles this well, including the syntaxes from all three types, but it gets hard for me to distinguish them on the screen.  I wanted to assign different background colors to the different regions - but they're all highlight links, so if I change, say, Comment, then all of HTMLComment, AspVBSComment, and javascriptComment will all change too.\r\n\r\nThis plugin changes that.  After an ASPVBS buffer is loaded, it recolors every ASP and javascript syntax item with a new background color - by retrieving the underlying linked highlight definition and redefining the specific highlight item.  ASP becomes dramatically easier to read. See the included file compare.asp.html (also here: http:\/\/member.newsguy.com\/~rpresser\/compare.asp.html).\r\n\r\nRequires the MultVals plugin <http:\/\/www.vim.org\/scripts\/script.php?script_id=171> for array handling.\r\n\r\nThis technique could be applicable to other kinds of files that have multiple languages in them, like HTML\/CSS, or C++ with embedded SQL, or maybe even someday XML.\r\n","4":"I edit ASP code a lot.  There's usually three different langauges in the same file: HTML, Vbscript, and Javascript.  The ASPVBS filetype plugin handles this well, including the syntaxes from all three types, but it gets hard for me to distinguish them on the screen.  I wanted to assign different background colors to the different regions - but they're all highlight links, so if I change, say, Comment, then all of HTMLComment, AspVBSComment, and javascriptComment will all change too.\r\n\r\nThis plugin changes that.  After an ASPVBS buffer is loaded, it recolors every ASP and javascript syntax item with a new background color - by retrieving the underlying linked highlight definition and redefining the specific highlight item.  ASP becomes dramatically easier to read. See the included file compare.asp.html (also here: http:\/\/member.newsguy.com\/~rpresser\/compare.asp.html).\r\n\r\nRequires the MultVals plugin <http:\/\/www.vim.org\/scripts\/script.php?script_id=171> for array handling.\r\n\r\nThis technique could be applicable to other kinds of files that have multiple languages in them, like HTML\/CSS, or C++ with embedded SQL, or maybe even someday XML.\r\n","install_details":"Either source this from your vimrc, or just drop it in a sytem or user plugins\/ folder.\r\n","5":"Either source this from your vimrc, or just drop it in a sytem or user plugins\/ folder.\r\n","first_name":"Ross","6":"Ross","last_name":"Presser","7":"Presser","releases":[{"0":"564","vim_version":"6.0","1":"6.0","script_version":"0.95","2":"0.95","version_comment":"Vim 6.2 released different versions of the ASP\/VBS and HTML\/Javascript syntax files, and this broke the hard-coded Recolors in ASPRecolor 0.90.  This version introduces a function that walks the syntax clusters to determine what items to recolor.  It also tries a bit harder to avoid error messages.  **NOW REQUIRES MultVals.vim*** <http:\/\/www.vim.org\/scripts\/script.php?script_id=171>","3":"Vim 6.2 released different versions of the ASP\/VBS and HTML\/Javascript syntax files, and this broke the hard-coded Recolors in ASPRecolor 0.90.  This version introduces a function that walks the syntax clusters to determine what items to recolor.  It also tries a bit harder to avoid error messages.  **NOW REQUIRES MultVals.vim*** <http:\/\/www.vim.org\/scripts\/script.php?script_id=171>","package":"ASPRecolor.vim","4":"ASPRecolor.vim","src_id":"2155","5":"2155","creation_date":"1058429891","6":"1058429891"},{"0":"564","vim_version":"6.0","1":"6.0","script_version":"0.90","2":"0.90","version_comment":"Initial upload","3":"Initial upload","package":"ASPRecolor.zip","4":"ASPRecolor.zip","src_id":"1722","5":"1722","creation_date":"1045047152","6":"1045047152"}]},"563":{"script_id":"563","0":"563","script_name":"rcsvers.vim","1":"rcsvers.vim","script_type":"utility","2":"utility","summary":"Use RCS to keep a backup version whenever you save a file","3":"Use RCS to keep a backup version whenever you save a file","description":"A Vim plugin for automatically saving backup versions in RCS whenever a file is saved.  You can compare to any revision as well.\r\nkeywords: VCS, version control system, incremental saving, automatic versioning, automatic journalling or journaling, or autosave backups with versions.\r\n\r\nThe maintainer is Juan Frias (juandfrias at gmail.com)\r\n\r\nWhat's RCS? It's the Revision Control System, a set of programs used for keeping many versions of a file. See http:\/\/www.gnu.org\/software\/rcs\/rcs.html\r\n\r\nThe RCS programs are freely available at http:\/\/www.cs.purdue.edu\/homes\/trinkle\/RCS\/\r\n\r\nBe careful if you really use RCS as your production file control, it will add versions like crazy.  See the g:rvMode option to have more control over when a save is added to the revision file.\r\n\r\nrcs-menu.vim by Jeff Lanzarotta is handy to have along with this (vimscript #41).\r\n\r\nInspired by savevers.vim by Ed Ralston (vimscript #89).\r\n\r\n Mapped Keys: \r\n               <Leader>rci     This will create an initial RCS file.  Only\r\n                                      necessary when you have the script set to\r\n                                      save only when a previous RCS file exists.\r\n               <Leader>rlog    To access the saved revisions log.  This works as\r\n                                      a toggle to quit the revision windows too.\r\n\r\n               <enter>         This will compare the current file to the\r\n                                    revision under the cursor (works only in\r\n                                    the revision log window)\r\n\r\n               <Leader>older   does a diff with the previous version\r\n\r\n               <Leader>newer   does a diff with the next version\r\n\r\n You probably want to map these in your _vimrc to something easier to type, \r\n like a function key.  Do it like this:\r\n\"re-map rcsvers.vim keys\r\nmap <F9> \\rci\r\nmap <F8> \\rlog\r\nmap <F5> \\older\r\nmap <F6> \\newer\r\n\r\n You may need to set the following shell(environment) variables, you'll get a warning if so:\r\n user name:\r\n\t\tLOGNAME=myusername\r\n timezone:  \r\n\t\tTZ=EST5EDT \r\n\r\nLook here if you have problems with Daylight Saving Time (DST) with RCS after 2007 on Microsoft Windows:  http:\/\/support.microsoft.com\/kb\/932590\r\n\r\n2013-10-16: Roger says: This seems to have broken between vim 7.3 and vim 7.4, on Windows, when saving versions of files where the file is in a folder with parentheses e.g. ()\r\n \r\nBacking out to vim 7.3 fixed the problem. \r\n\r\nIf you can help figure it out, put something on the wiki page (link at the top of this page)","4":"A Vim plugin for automatically saving backup versions in RCS whenever a file is saved.  You can compare to any revision as well.\r\nkeywords: VCS, version control system, incremental saving, automatic versioning, automatic journalling or journaling, or autosave backups with versions.\r\n\r\nThe maintainer is Juan Frias (juandfrias at gmail.com)\r\n\r\nWhat's RCS? It's the Revision Control System, a set of programs used for keeping many versions of a file. See http:\/\/www.gnu.org\/software\/rcs\/rcs.html\r\n\r\nThe RCS programs are freely available at http:\/\/www.cs.purdue.edu\/homes\/trinkle\/RCS\/\r\n\r\nBe careful if you really use RCS as your production file control, it will add versions like crazy.  See the g:rvMode option to have more control over when a save is added to the revision file.\r\n\r\nrcs-menu.vim by Jeff Lanzarotta is handy to have along with this (vimscript #41).\r\n\r\nInspired by savevers.vim by Ed Ralston (vimscript #89).\r\n\r\n Mapped Keys: \r\n               <Leader>rci     This will create an initial RCS file.  Only\r\n                                      necessary when you have the script set to\r\n                                      save only when a previous RCS file exists.\r\n               <Leader>rlog    To access the saved revisions log.  This works as\r\n                                      a toggle to quit the revision windows too.\r\n\r\n               <enter>         This will compare the current file to the\r\n                                    revision under the cursor (works only in\r\n                                    the revision log window)\r\n\r\n               <Leader>older   does a diff with the previous version\r\n\r\n               <Leader>newer   does a diff with the next version\r\n\r\n You probably want to map these in your _vimrc to something easier to type, \r\n like a function key.  Do it like this:\r\n\"re-map rcsvers.vim keys\r\nmap <F9> \\rci\r\nmap <F8> \\rlog\r\nmap <F5> \\older\r\nmap <F6> \\newer\r\n\r\n You may need to set the following shell(environment) variables, you'll get a warning if so:\r\n user name:\r\n\t\tLOGNAME=myusername\r\n timezone:  \r\n\t\tTZ=EST5EDT \r\n\r\nLook here if you have problems with Daylight Saving Time (DST) with RCS after 2007 on Microsoft Windows:  http:\/\/support.microsoft.com\/kb\/932590\r\n\r\n2013-10-16: Roger says: This seems to have broken between vim 7.3 and vim 7.4, on Windows, when saving versions of files where the file is in a folder with parentheses e.g. ()\r\n \r\nBacking out to vim 7.3 fixed the problem. \r\n\r\nIf you can help figure it out, put something on the wiki page (link at the top of this page)","install_details":"Drop it in your plugin directory.  Your RCS executables must be in your path.  There are lots of options, but by default it acts exactly like RCS from the command line.\r\n","5":"Drop it in your plugin directory.  Your RCS executables must be in your path.  There are lots of options, but by default it acts exactly like RCS from the command line.\r\n","first_name":"Roger","6":"Roger","last_name":"Pilkey","7":"Pilkey","releases":[{"0":"563","vim_version":"7.0","1":"7.0","script_version":"1.28","2":"1.28","version_comment":"Adds syntax highlighting to temporary files retrieved from RCS and fix of \\rci to work with vim 7. (thanks to Sergey Khorev)\r\nAlso added Fredrik Eriksson's patch to allow editing of messages. (http:\/\/thebc.se\/patch-for-rcsversvim)\r\nAnd added the -d option to preserve original modification times. (Roger)\r\nRemoved the rvtempdir in favor of more secure tempname() call. (Roger)\r\nWe used to skip the pre-checkin, but I think we should do it, if someone or something else has modified the file since the last RCS version then we will put their version in the RCS file. (Roger)","3":"Adds syntax highlighting to temporary files retrieved from RCS and fix of \\rci to work with vim 7. (thanks to Sergey Khorev)\r\nAlso added Fredrik Eriksson's patch to allow editing of messages. (http:\/\/thebc.se\/patch-for-rcsversvim)\r\nAnd added the -d option to preserve original modification times. (Roger)\r\nRemoved the rvtempdir in favor of more secure tempname() call. (Roger)\r\nWe used to skip the pre-checkin, but I think we should do it, if someone or something else has modified the file since the last RCS version then we will put their version in the RCS file. (Roger)","package":"rcsvers.vim","4":"rcsvers.vim","src_id":"12020","5":"12020","creation_date":"1262794134","6":"1262794134"},{"0":"563","vim_version":"6.0","1":"6.0","script_version":"1.27","2":"1.27","version_comment":"Add a new mode for revising (never\/ask\/always) and fix rlog window width, both thanks to Callum Gibson.  See g:rvMode .\r\n","3":"Add a new mode for revising (never\/ask\/always) and fix rlog window width, both thanks to Callum Gibson.  See g:rvMode .\r\n","package":"rcsvers.vim","4":"rcsvers.vim","src_id":"6993","5":"6993","creation_date":"1176832062","6":"1176832062"},{"0":"563","vim_version":"6.0","1":"6.0","script_version":"1.26","2":"1.26","version_comment":"Fix for Windows for usernames with spaces (from Roger), and macosx directory separator (thanks to Jeff Fox)\r\n","3":"Fix for Windows for usernames with spaces (from Roger), and macosx directory separator (thanks to Jeff Fox)\r\n","package":"rcsvers.vim","4":"rcsvers.vim","src_id":"6607","5":"6607","creation_date":"1168520009","6":"1168520009"},{"0":"563","vim_version":"6.0","1":"6.0","script_version":"1.25","2":"1.25","version_comment":"Fix for Windows if you don't have the TZ variable set, and fix how it works when saving a file to another name.\r\n","3":"Fix for Windows if you don't have the TZ variable set, and fix how it works when saving a file to another name.\r\n","package":"rcsvers.vim","4":"rcsvers.vim","src_id":"4996","5":"4996","creation_date":"1137817321","6":"1137817321"},{"0":"563","vim_version":"6.0","1":"6.0","script_version":"1.24","2":"1.24","version_comment":"Just updating author\/maintainer email addresses.","3":"Just updating author\/maintainer email addresses.","package":"rcsvers.vim","4":"rcsvers.vim","src_id":"4681","5":"4681","creation_date":"1129660268","6":"1129660268"},{"0":"563","vim_version":"6.0","1":"6.0","script_version":"1.24","2":"1.24","version_comment":"RCS sets the executable bit on the checked-out file to be the same as the rcs archive file.  So if that property changes after you did your first checkin, your checked-out file will maintain the original setting. So now we change the executable mode of the rcs archive file to align with the current setting of the checked-out copy. Thanks to Ben Bernard.\r\n","3":"RCS sets the executable bit on the checked-out file to be the same as the rcs archive file.  So if that property changes after you did your first checkin, your checked-out file will maintain the original setting. So now we change the executable mode of the rcs archive file to align with the current setting of the checked-out copy. Thanks to Ben Bernard.\r\n","package":"rcsvers.vim","4":"rcsvers.vim","src_id":"4609","5":"4609","creation_date":"1127359594","6":"1127359594"},{"0":"563","vim_version":"6.0","1":"6.0","script_version":"1.23","2":"1.23","version_comment":"Added an option to fix the path on Cygwin systems.  \r\n See g:rvUseCygPathFiltering  \r\n Thanks to Simon Johann-G\u00c3\u00bcnter","3":"Added an option to fix the path on Cygwin systems.  \r\n See g:rvUseCygPathFiltering  \r\n Thanks to Simon Johann-G\u00c3\u00bcnter","package":"rcsvers.vim","4":"rcsvers.vim","src_id":"4129","5":"4129","creation_date":"1112810165","6":"1112810165"},{"0":"563","vim_version":"6.0","1":"6.0","script_version":"1.22","2":"1.22","version_comment":"some re-factoring, and add the option to leave RCS files unlocked when saving, which is handy for multiple users of the same RCS file.   \r\nSee g:rvLeaveRcsUnlocked. (from Roger Pilkey)\r\n","3":"some re-factoring, and add the option to leave RCS files unlocked when saving, which is handy for multiple users of the same RCS file.   \r\nSee g:rvLeaveRcsUnlocked. (from Roger Pilkey)\r\n","package":"rcsvers.vim","4":"rcsvers.vim","src_id":"4031","5":"4031","creation_date":"1110954234","6":"1110954234"},{"0":"563","vim_version":"6.0","1":"6.0","script_version":"1.21","2":"1.21","version_comment":"small update: Remember the last position in the rlog window. Rename RevisionLog window to avoid collisions\r\n","3":"small update: Remember the last position in the rlog window. Rename RevisionLog window to avoid collisions\r\n","package":"rcsvers.vim","4":"rcsvers.vim","src_id":"3268","5":"3268","creation_date":"1090641176","6":"1090641176"},{"0":"563","vim_version":"6.0","1":"6.0","script_version":"1.20","2":"1.20","version_comment":"Added a mapping to create an initial RCS file. Useful when the script \r\nis set to save only when a previous RCS file exists. see\r\nrvSaveIfPreviousRCSFileExists (thanks to Steven Michalske for the\r\n suggestion) Added <silent> to the default mappings to keep the status\r\nbar clean.","3":"Added a mapping to create an initial RCS file. Useful when the script \r\nis set to save only when a previous RCS file exists. see\r\nrvSaveIfPreviousRCSFileExists (thanks to Steven Michalske for the\r\n suggestion) Added <silent> to the default mappings to keep the status\r\nbar clean.","package":"rcsvers.vim","4":"rcsvers.vim","src_id":"3187","5":"3187","creation_date":"1088396157","6":"1088396157"},{"0":"563","vim_version":"6.0","1":"6.0","script_version":"1.19","2":"1.19","version_comment":"1.19  Added the option to prompt the user for file and check-in message on\r\n every save. See rvDescMsgPrompt option for details. Thanks to Kevin\r\n Stegemoller for the suggestion. Also \\rlog will now display the\r\n check-in message in the pick list for easier identification.\r\n","3":"1.19  Added the option to prompt the user for file and check-in message on\r\n every save. See rvDescMsgPrompt option for details. Thanks to Kevin\r\n Stegemoller for the suggestion. Also \\rlog will now display the\r\n check-in message in the pick list for easier identification.\r\n","package":"rcsvers.vim","4":"rcsvers.vim","src_id":"3110","5":"3110","creation_date":"1086890045","6":"1086890045"},{"0":"563","vim_version":"6.0","1":"6.0","script_version":"1.18","2":"1.18","version_comment":"Added the option to save an RCS version only if the RCS file already\r\n  exists (No new RCS files will be created). (from Marc Schoechlin)\r\n  See rvSaveIfPreviousRCSFileExists option.\r\n","3":"Added the option to save an RCS version only if the RCS file already\r\n  exists (No new RCS files will be created). (from Marc Schoechlin)\r\n  See rvSaveIfPreviousRCSFileExists option.\r\n","package":"rcsvers.vim","4":"rcsvers.vim","src_id":"2785","5":"2785","creation_date":"1077810410","6":"1077810410"},{"0":"563","vim_version":"6.0","1":"6.0","script_version":"1.17","2":"1.17","version_comment":"Added the option to save an RCS version only when there is an RCS\r\ndirectory in the files directory. See rvSaveIfRCSExists option.\r\n(from Camillo S\u00c3\u00a4rs)\r\n","3":"Added the option to save an RCS version only when there is an RCS\r\ndirectory in the files directory. See rvSaveIfRCSExists option.\r\n(from Camillo S\u00c3\u00a4rs)\r\n","package":"rcsvers.vim","4":"rcsvers.vim","src_id":"2687","5":"2687","creation_date":"1075280037","6":"1075280037"},{"0":"563","vim_version":"6.0","1":"6.0","script_version":"1.16","2":"1.16","version_comment":"Save some settings that \"set diff\" mangles, and different check for &cp\r\n","3":"Save some settings that \"set diff\" mangles, and different check for &cp\r\n","package":"rcsvers.vim","4":"rcsvers.vim","src_id":"2579","5":"2579","creation_date":"1070950950","6":"1070950950"},{"0":"563","vim_version":"6.0","1":"6.0","script_version":"1.15","2":"1.15","version_comment":"Add functions to go back and forth between versions (mapped to \\older and \\newer). It's kind of jerky, but comes in handy sometimes. Also fixed a few bugs with quotes.\r\n","3":"Add functions to go back and forth between versions (mapped to \\older and \\newer). It's kind of jerky, but comes in handy sometimes. Also fixed a few bugs with quotes.\r\n","package":"rcsvers.vim","4":"rcsvers.vim","src_id":"2337","5":"2337","creation_date":"1063708014","6":"1063708014"},{"0":"563","vim_version":"6.0","1":"6.0","script_version":"1.14","2":"1.14","version_comment":"Add option to set \"rlog\" command-line options.  fix rlog display,\r\nwhich would crash once in a while saying stuff like \"10,10d invalid\r\nrange\". When creating a new RCS file on an existing text file, save a\r\nversion before adding the new revision.\r\n\r\n","3":"Add option to set \"rlog\" command-line options.  fix rlog display,\r\nwhich would crash once in a while saying stuff like \"10,10d invalid\r\nrange\". When creating a new RCS file on an existing text file, save a\r\nversion before adding the new revision.\r\n\r\n","package":"rcsvers.vim","4":"rcsvers.vim","src_id":"2051","5":"2051","creation_date":"1055154943","6":"1055154943"},{"0":"563","vim_version":"6.0","1":"6.0","script_version":"1.13","2":"1.13","version_comment":"A g:rvFileQuote fix, suggested by Wiktor Niesiobedzki.  Add the ability to use the current instance of vim for the diff, which is now the default.  Change the name of the diff temp file to include the version.  Make \\rlog a toggle (on\/off)\r\n","3":"A g:rvFileQuote fix, suggested by Wiktor Niesiobedzki.  Add the ability to use the current instance of vim for the diff, which is now the default.  Change the name of the diff temp file to include the version.  Make \\rlog a toggle (on\/off)\r\n","package":"rcsvers.vim","4":"rcsvers.vim","src_id":"1973","5":"1973","creation_date":"1052374205","6":"1052374205"},{"0":"563","vim_version":"6.0","1":"6.0","script_version":"1.12","2":"1.12","version_comment":" 1.12  (From Juan Frias) Script will not load if the 'cp' flag is set. Added the option to use an exclude expression, and include expression.  Fixed yet more bugs thanks to Roger for all the beta testing.\r\n","3":" 1.12  (From Juan Frias) Script will not load if the 'cp' flag is set. Added the option to use an exclude expression, and include expression.  Fixed yet more bugs thanks to Roger for all the beta testing.\r\n","package":"rcsvers.vim","4":"rcsvers.vim","src_id":"1872","5":"1872","creation_date":"1048851754","6":"1048851754"},{"0":"563","vim_version":"6.0","1":"6.0","script_version":"1.11","2":"1.11","version_comment":"(for Juan Frias) Minor bug fix, when using spaces in the description. \r\nAlso added some error detection code to check and see that RCS \r\nand CI were successful. And removed requirements for SED and GREP, \r\nscript will no longer need these to display the log.\r\n\r\n","3":"(for Juan Frias) Minor bug fix, when using spaces in the description. \r\nAlso added some error detection code to check and see that RCS \r\nand CI were successful. And removed requirements for SED and GREP, \r\nscript will no longer need these to display the log.\r\n\r\n","package":"rcsvers.vim","4":"rcsvers.vim","src_id":"1793","5":"1793","creation_date":"1047293268","6":"1047293268"},{"0":"563","vim_version":"6.0","1":"6.0","script_version":"1.10","2":"1.10","version_comment":"Fixed some major bugs with files with long filenames and spaces Win\/Dos systems. Added a variable to pass additional options to the initial RCS check in. Fixed some documentations typos.","3":"Fixed some major bugs with files with long filenames and spaces Win\/Dos systems. Added a variable to pass additional options to the initial RCS check in. Fixed some documentations typos.","package":"rcsvers.vim","4":"rcsvers.vim","src_id":"1776","5":"1776","creation_date":"1046686656","6":"1046686656"},{"0":"563","vim_version":"6.0","1":"6.0","script_version":"1.9","2":"1.9","version_comment":"Added even more options, the ability to set your own description and pass additional options to CI command. Dos\/Win Temp directory is taken from the $TEMP environment variable, and quote filenames when using diff program to prevent errors with long filenames with spaces. Also removed confirm box from script. (Thanx Roger for all the beta testing)","3":"Added even more options, the ability to set your own description and pass additional options to CI command. Dos\/Win Temp directory is taken from the $TEMP environment variable, and quote filenames when using diff program to prevent errors with long filenames with spaces. Also removed confirm box from script. (Thanx Roger for all the beta testing)","package":"rcsvers.vim","4":"rcsvers.vim","src_id":"1775","5":"1775","creation_date":"1046443556","6":"1046443556"},{"0":"563","vim_version":"6.0","1":"6.0","script_version":"1.8","2":"1.8","version_comment":"Minor suffix bug fix. Required if you are using suffixes. ","3":"Minor suffix bug fix. Required if you are using suffixes. ","package":"rcsvers.vim","4":"rcsvers.vim","src_id":"1773","5":"1773","creation_date":"1046428146","6":"1046428146"},{"0":"563","vim_version":"6.0","1":"6.0","script_version":"1.7","2":"1.7","version_comment":"1.7   Will not alter the $xx$ tags when automaticaly checking in files.\r\n      (Thanks to Engelbert Gruber). Added option to save under the current\r\n      directory with no RCS sub directory. Also added the option to choose\r\n      your own suffixes.\r\n","3":"1.7   Will not alter the $xx$ tags when automaticaly checking in files.\r\n      (Thanks to Engelbert Gruber). Added option to save under the current\r\n      directory with no RCS sub directory. Also added the option to choose\r\n      your own suffixes.\r\n","package":"rcsvers.vim","4":"rcsvers.vim","src_id":"1771","5":"1771","creation_date":"1046339873","6":"1046339873"},{"0":"563","vim_version":"6.0","1":"6.0","script_version":"1.6","2":"1.6","version_comment":"Complete script re-write. It now allows user define options and the ability to compare to older revisions if you have SED and GREP installed. Working on a way to get rid of these external program in a later version.","3":"Complete script re-write. It now allows user define options and the ability to compare to older revisions if you have SED and GREP installed. Working on a way to get rid of these external program in a later version.","package":"rcsvers.vim","4":"rcsvers.vim","src_id":"1765","5":"1765","creation_date":"1046085426","6":"1046085426"},{"0":"563","vim_version":"6.0","1":"6.0","script_version":"1.5","2":"1.5","version_comment":"FIX files in current directory - RCS in filedirectory.\r\n+ Check for file .novimrcs in files directory to skip versioning.","3":"FIX files in current directory - RCS in filedirectory.\r\n+ Check for file .novimrcs in files directory to skip versioning.","package":"rcsvers.vim","4":"rcsvers.vim","src_id":"1758","5":"1758","creation_date":"1045712552","6":"1045712552"},{"0":"563","vim_version":"6.0","1":"6.0","script_version":"1.4","2":"1.4","version_comment":"FIX editing files not in current directory.","3":"FIX editing files not in current directory.","package":"rcsvers.vim","4":"rcsvers.vim","src_id":"1757","5":"1757","creation_date":"1045704967","6":"1045704967"},{"0":"563","vim_version":"6.0","1":"6.0","script_version":"1.3","2":"1.3","version_comment":"error in uploading","3":"error in uploading","package":"rcsvers.vim","4":"rcsvers.vim","src_id":"1755","5":"1755","creation_date":"1045637501","6":"1045637501"},{"0":"563","vim_version":"6.0","1":"6.0","script_version":"1.2","2":"1.2","version_comment":"option to select the rcs directory, and better comments thanks to Juan Frias\r\n","3":"option to select the rcs directory, and better comments thanks to Juan Frias\r\n","package":"rcsvers.vim","4":"rcsvers.vim","src_id":"1754","5":"1754","creation_date":"1045637249","6":"1045637249"},{"0":"563","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"rcsvers.vim","4":"rcsvers.vim","src_id":"1721","5":"1721","creation_date":"1045045031","6":"1045045031"}]},"562":{"script_id":"562","0":"562","script_name":"rd.vim","1":"rd.vim","script_type":"syntax","2":"syntax","summary":"Syntax highlighting for RD files.","3":"Syntax highlighting for RD files.","description":"RD is multipurpose documentation format created for documentating Ruby \r\nand output of Ruby world.\r\n\r\nabout RD: http:\/\/www.ruby-lang.org\/~rubikitch\/RDP-en.cgi?cmd=view;name=RD","4":"RD is multipurpose documentation format created for documentating Ruby \r\nand output of Ruby world.\r\n\r\nabout RD: http:\/\/www.ruby-lang.org\/~rubikitch\/RDP-en.cgi?cmd=view;name=RD","install_details":"Save in $VIMRUNTIME\/syntax\/\r\n:help new-filetype\r\n ","5":"Save in $VIMRUNTIME\/syntax\/\r\n:help new-filetype\r\n ","first_name":"Yasumasa","6":"Yasumasa","last_name":"UECHI","7":"UECHI","releases":[{"0":"562","vim_version":"6.0","1":"6.0","script_version":"1.4","2":"1.4","version_comment":"Initial upload","3":"Initial upload","package":"rd.vim","4":"rd.vim","src_id":"1720","5":"1720","creation_date":"1045024039","6":"1045024039"}]},"561":{"script_id":"561","0":"561","script_name":"help.vim","1":"help.vim","script_type":"utility","2":"utility","summary":"help subsystem (create buffer with context-dependent help page)","3":"help subsystem (create buffer with context-dependent help page)","description":"This plugin can help you call man or perldoc -f or many other help system in dependent from context.\r\n\r\nChanges:\r\n      * 1.18-1 now support perdoc in win32 OS...\r\n      * 1.18     several bugfixes, added call apropos if man page not found.\r\n      * 1.17     support fvwm, muttrc filetype, many fixes...\r\n      * 1.17g   new, extended implementation of help.vim (http:\/\/www.vim.org\/scripts\/script.php?script_id=561)\r\n      * 1.17b   forked by help.vim,v 1.16 2002\/01\/05 19:58:38 from Slava Gorbanev, added support tcl\/tk and many fixes\r\n\r\nUsage:\r\n          use <F1> by default or other key (if you remap it) to call Help(expand(\"<cword>\"))\r\n          this function creating in half window buffer with contex-dependent\r\n          manual (or other) page about word under corsor.\r\n \r\n    By default in help-buffer set key-mapping:\r\n    q           for exit (and ``Esc'' in GUI mode)\r\n    o           for command :only\r\n    D           for go to DESCRIPTION section\r\n    S           for go to SYN section\r\n    (and other --- see source code by detail)\r\n\r\nYou can mapping go to any other section:\r\nfor example for go to NAME section by N key call next command:\r\nmap N :call GoToSection('NAME')\r\n\r\nNow support: sh, vim, perl, tcl\/tk, C\/C++, fvwm, muttrc and many other.\r\n\r\n TODO nicier documentation (oh, my terrible english)...\r\n TODO support many other language","4":"This plugin can help you call man or perldoc -f or many other help system in dependent from context.\r\n\r\nChanges:\r\n      * 1.18-1 now support perdoc in win32 OS...\r\n      * 1.18     several bugfixes, added call apropos if man page not found.\r\n      * 1.17     support fvwm, muttrc filetype, many fixes...\r\n      * 1.17g   new, extended implementation of help.vim (http:\/\/www.vim.org\/scripts\/script.php?script_id=561)\r\n      * 1.17b   forked by help.vim,v 1.16 2002\/01\/05 19:58:38 from Slava Gorbanev, added support tcl\/tk and many fixes\r\n\r\nUsage:\r\n          use <F1> by default or other key (if you remap it) to call Help(expand(\"<cword>\"))\r\n          this function creating in half window buffer with contex-dependent\r\n          manual (or other) page about word under corsor.\r\n \r\n    By default in help-buffer set key-mapping:\r\n    q           for exit (and ``Esc'' in GUI mode)\r\n    o           for command :only\r\n    D           for go to DESCRIPTION section\r\n    S           for go to SYN section\r\n    (and other --- see source code by detail)\r\n\r\nYou can mapping go to any other section:\r\nfor example for go to NAME section by N key call next command:\r\nmap N :call GoToSection('NAME')\r\n\r\nNow support: sh, vim, perl, tcl\/tk, C\/C++, fvwm, muttrc and many other.\r\n\r\n TODO nicier documentation (oh, my terrible english)...\r\n TODO support many other language","install_details":"put this into your plugin directory (~\/.vim\/plugin)","5":"put this into your plugin directory (~\/.vim\/plugin)","first_name":"Nikolay","6":"Nikolay","last_name":"Panov","7":"Panov","releases":[{"0":"561","vim_version":"7.0","1":"7.0","script_version":"1.20","2":"1.20","version_comment":"Some new help systems are supported now (e.g. pydoc for python). And the plugin is tested under vim 7.","3":"Some new help systems are supported now (e.g. pydoc for python). And the plugin is tested under vim 7.","package":"help.vim","4":"help.vim","src_id":"9572","5":"9572","creation_date":"1227691081","6":"1227691081"},{"0":"561","vim_version":"6.0","1":"6.0","script_version":"1.20","2":"1.20","version_comment":"Some new help systems are supported now (e.g. pydoc for python).","3":"Some new help systems are supported now (e.g. pydoc for python).","package":"help.vim","4":"help.vim","src_id":"9571","5":"9571","creation_date":"1227691013","6":"1227691013"},{"0":"561","vim_version":"6.0","1":"6.0","script_version":"1.18-1","2":"1.18-1","version_comment":"now support perdoc in win32 OS...","3":"now support perdoc in win32 OS...","package":"help.vim","4":"help.vim","src_id":"1889","5":"1889","creation_date":"1049330752","6":"1049330752"},{"0":"561","vim_version":"6.0","1":"6.0","script_version":"1.18","2":"1.18","version_comment":"several bugfixes, added call apropos if man page not found","3":"several bugfixes, added call apropos if man page not found","package":"help.vim","4":"help.vim","src_id":"1798","5":"1798","creation_date":"1047347649","6":"1047347649"}]},"560":{"script_id":"560","0":"560","script_name":"MPD syntax highlighting","1":"MPD syntax highlighting","script_type":"syntax","2":"syntax","summary":"Syntax highlighting for MPD language","3":"Syntax highlighting for MPD language","description":"MPD language is a similar to SR. It`s used for parallel programming.","4":"MPD language is a similar to SR. It`s used for parallel programming.","install_details":"Install as usual. I recomend to switch to cindent mode and set cinkeys like that:\r\n\r\nau BufNewFile,BufRead *.mpd setlocal cinkeys+=global,resource,procedure,body\r\n\r\nEnjoy!","5":"Install as usual. I recomend to switch to cindent mode and set cinkeys like that:\r\n\r\nau BufNewFile,BufRead *.mpd setlocal cinkeys+=global,resource,procedure,body\r\n\r\nEnjoy!","first_name":"Lukas","6":"Lukas","last_name":"Zapletal","7":"Zapletal","releases":[{"0":"560","vim_version":"6.0","1":"6.0","script_version":"1.3","2":"1.3","version_comment":"New indenting, now works properly!\r\n\r\nInstallation:\r\n\r\nExtracts files to ~\/.vim directory (on windows ~\/vimfiles).\r\nThen add these lines to .vimrc (on windows _vimrc):\r\n\r\naugroup filetypedetect\r\nau! BufNewFile,BufRead *.mpd setlocal filetype=mpd\r\naugroup END\r\n\r\nIt is important to set the filetype via setlocal, because \r\nin some cases (e.g. when the file starts with several lines \r\nof comment) it can be recognized as a config file already.\r\n","3":"New indenting, now works properly!\r\n\r\nInstallation:\r\n\r\nExtracts files to ~\/.vim directory (on windows ~\/vimfiles).\r\nThen add these lines to .vimrc (on windows _vimrc):\r\n\r\naugroup filetypedetect\r\nau! BufNewFile,BufRead *.mpd setlocal filetype=mpd\r\naugroup END\r\n\r\nIt is important to set the filetype via setlocal, because \r\nin some cases (e.g. when the file starts with several lines \r\nof comment) it can be recognized as a config file already.\r\n","package":"mpd-1.3.zip","4":"mpd-1.3.zip","src_id":"1756","5":"1756","creation_date":"1045650005","6":"1045650005"},{"0":"560","vim_version":"6.0","1":"6.0","script_version":"1.1","2":"1.1","version_comment":"Update. Now includes indent script.\r\n\r\nInstall as usual using setf command.\r\nDo not set indent. VIM automatically loads indent script.","3":"Update. Now includes indent script.\r\n\r\nInstall as usual using setf command.\r\nDo not set indent. VIM automatically loads indent script.","package":"mpd.zip","4":"mpd.zip","src_id":"1719","5":"1719","creation_date":"1045016892","6":"1045016892"},{"0":"560","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"mpd.vim","4":"mpd.vim","src_id":"1715","5":"1715","creation_date":"1044953584","6":"1044953584"}]},"559":{"script_id":"559","0":"559","script_name":"BufClose.vim","1":"BufClose.vim","script_type":"utility","2":"utility","summary":"Unload a buffer without closing the window it's in","3":"Unload a buffer without closing the window it's in","description":":BufClose without an argument will close the buffer in the current window, leaving you with a blank buffer.\r\n\r\n:BufClose with an argument looks for a buffer by that name or number in a window and closes it, leaving that window with a blank buffer.","4":":BufClose without an argument will close the buffer in the current window, leaving you with a blank buffer.\r\n\r\n:BufClose with an argument looks for a buffer by that name or number in a window and closes it, leaving that window with a blank buffer.","install_details":"Either :source it or put it in your plugin directory.","5":"Either :source it or put it in your plugin directory.","first_name":"Christian J.","6":"Christian J.","last_name":"Robinson","7":"Robinson","releases":[{"0":"559","vim_version":"9.0","1":"9.0","script_version":"0.7","2":"0.7","version_comment":"- Update to Vim 9 (no functionality added)","3":"- Update to Vim 9 (no functionality added)","package":"BufClose.vim","4":"BufClose.vim","src_id":"28137","5":"28137","creation_date":"1661149213","6":"1661149213"},{"0":"559","vim_version":"6.0","1":"6.0","script_version":"0.6","2":"0.6","version_comment":"- Copyright, usage and configuration commentary added.\r\n- g:BufClose_AltBuffer can be set to load something other than a blank buffer.","3":"- Copyright, usage and configuration commentary added.\r\n- g:BufClose_AltBuffer can be set to load something other than a blank buffer.","package":"BufClose.vim","4":"BufClose.vim","src_id":"1729","5":"1729","creation_date":"1045124833","6":"1045124833"},{"0":"559","vim_version":"6.0","1":"6.0","script_version":"0.5","2":"0.5","version_comment":"Initial upload","3":"Initial upload","package":"BufClose.vim","4":"BufClose.vim","src_id":"1711","5":"1711","creation_date":"1044830490","6":"1044830490"}]},"558":{"script_id":"558","0":"558","script_name":"spreadsheet.vim","1":"spreadsheet.vim","script_type":"utility","2":"utility","summary":"SpreadSheet Functionality","3":"SpreadSheet Functionality","description":"This script lets you use vim as a spreadsheet, adding arithmetic calculations to your text files.\r\n\r\nUseful for bills, expenses, ratings and other numeric text templates.\r\n\r\nIt provides three main functions:\r\n   Get(\"cell\")\r\n   Set(\"cell\", \"value\")\r\n   Calculate(\"operation\")\r\n\r\nDetailed instructions and examples are included in the script file.\r\n\r\nIt uses 'bc'  Linux OS comand for the Calculate function.","4":"This script lets you use vim as a spreadsheet, adding arithmetic calculations to your text files.\r\n\r\nUseful for bills, expenses, ratings and other numeric text templates.\r\n\r\nIt provides three main functions:\r\n   Get(\"cell\")\r\n   Set(\"cell\", \"value\")\r\n   Calculate(\"operation\")\r\n\r\nDetailed instructions and examples are included in the script file.\r\n\r\nIt uses 'bc'  Linux OS comand for the Calculate function.","install_details":"Just copy spreadsheet.vim in your .vim\/plugin directory","5":"Just copy spreadsheet.vim in your .vim\/plugin directory","first_name":"Miguel","6":"Miguel","last_name":"Jaque Barbero","7":"Jaque Barbero","releases":[{"0":"558","vim_version":"6.0","1":"6.0","script_version":"0.1b","2":"0.1b","version_comment":"Added functions to save and recover cursor position (even between windows).","3":"Added functions to save and recover cursor position (even between windows).","package":"spreadsheet.vim","4":"spreadsheet.vim","src_id":"1743","5":"1743","creation_date":"1045452018","6":"1045452018"},{"0":"558","vim_version":"6.0","1":"6.0","script_version":"0.1a","2":"0.1a","version_comment":"Functionality added for quickly cell definition (command and key mapping)\r\nSupport for different number sintax other than bc's. By default, \",\" is used for decimal separation and \".\" for thousands.","3":"Functionality added for quickly cell definition (command and key mapping)\r\nSupport for different number sintax other than bc's. By default, \",\" is used for decimal separation and \".\" for thousands.","package":"spreadsheet.vim","4":"spreadsheet.vim","src_id":"1717","5":"1717","creation_date":"1044960718","6":"1044960718"},{"0":"558","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"spreadsheet.vim","4":"spreadsheet.vim","src_id":"1710","5":"1710","creation_date":"1044792889","6":"1044792889"}]},"557":{"script_id":"557","0":"557","script_name":"BOG","1":"BOG","script_type":"color scheme","2":"color scheme","summary":"Blue Orange Green color scheme","3":"Blue Orange Green color scheme","description":"screenshot at http:\/\/www.quantumz.net\/screen\/gvim272003.png . Suggestions are welcome :)\r\n\r\nGui only\r\n\r\n","4":"screenshot at http:\/\/www.quantumz.net\/screen\/gvim272003.png . Suggestions are welcome :)\r\n\r\nGui only\r\n\r\n","install_details":"mv to <runtimepath>\/share\/colors\r\nand then\r\n:colorscheme bog in vim\r\n","5":"mv to <runtimepath>\/share\/colors\r\nand then\r\n:colorscheme bog in vim\r\n","first_name":"blah","6":"blah","last_name":"blahd","7":"blahd","releases":[{"0":"557","vim_version":"6.0","1":"6.0","script_version":"0.0.1","2":"0.0.1","version_comment":"Initial upload","3":"Initial upload","package":"bog.vim","4":"bog.vim","src_id":"1704","5":"1704","creation_date":"1044657900","6":"1044657900"}]},"556":{"script_id":"556","0":"556","script_name":"Perl-Support","1":"Perl-Support","script_type":"utility","2":"utility","summary":"Perl IDE -- Insert code snippets, run and profile the code and look up help","3":"Perl IDE -- Insert code snippets, run and profile the code and look up help","description":"Perl-Support is written to considerably speed up writing code in a consistent\r\nstyle, as well as to help with other often performed tasks:\r\n\r\n- insert various types of comments\r\n- insert complete but empty statements (e.g. 'if {} else {}' )\r\n- insert often used code snippets (e.g. declarations, the opening of files, .. )\r\n- insert the names of file tests, character classes, special Perl-variables and POSIX-signals\r\n- read, write, maintain your own code snippets in a separate directory\r\n- ... which come in an extendible template library\r\n- run scripts or run syntax check from within the editor\r\n- show compilation errors in a quickfix window\r\n- read perldoc for functions and modules\r\n- run perltidy \/ run the profiler SmallProf\r\n- test \/ explain regular expressions (needs Vim with Perl interface)\r\n\r\nSome screen shots :  https:\/\/wolfgangmehner.github.io\/vim-plugins\/perlsupport.html\r\n\r\nFor plug-in managers :  https:\/\/github.com\/WolfgangMehner\/perl-support\r\n\r\nThe help file online :  https:\/\/wolfgangmehner.github.io\/vim-plugins\/doc\/perlsupport.html\r\n\r\nThe key mappings of this plug-in :  https:\/\/wolfgangmehner.github.io\/vim-plugins\/perlsupport\/perl-hot-keys.pdf\r\n\r\nThe installation explained :  \"Make Vim as Your Perl-IDE Using perl-support Plugin\"\r\n(http:\/\/www.thegeekstuff.com\/2009\/01\/make-vim-as-your-perl-ide-using-perl-supportvim-plugin)\r\n\r\nDOCUMENTATION\r\n--------------------------------------------------------\r\nThis plug-in comes with a help file (perlsupport.txt). Read it with\r\n\r\n    :help perlsupport\r\n\r\n** PLEASE READ THE DOCUMENTATION **\r\n\r\nEditing actions differ for different modes! There are a lot of features which\r\ncan be configured or customized to match your needs.\r\n\r\nGitHub\r\n--------------------------------------------------------\r\nPerl-Support is on GitHub:\r\n\r\n    https:\/\/github.com\/WolfgangMehner\/vim-plugins\r\n\r\n(Please help us keep track of all the issues and name your report\/request \"Perl-Support: <title>\")\r\n\r\n___________________\r\nThank you for rating perl-support !","4":"Perl-Support is written to considerably speed up writing code in a consistent\r\nstyle, as well as to help with other often performed tasks:\r\n\r\n- insert various types of comments\r\n- insert complete but empty statements (e.g. 'if {} else {}' )\r\n- insert often used code snippets (e.g. declarations, the opening of files, .. )\r\n- insert the names of file tests, character classes, special Perl-variables and POSIX-signals\r\n- read, write, maintain your own code snippets in a separate directory\r\n- ... which come in an extendible template library\r\n- run scripts or run syntax check from within the editor\r\n- show compilation errors in a quickfix window\r\n- read perldoc for functions and modules\r\n- run perltidy \/ run the profiler SmallProf\r\n- test \/ explain regular expressions (needs Vim with Perl interface)\r\n\r\nSome screen shots :  https:\/\/wolfgangmehner.github.io\/vim-plugins\/perlsupport.html\r\n\r\nFor plug-in managers :  https:\/\/github.com\/WolfgangMehner\/perl-support\r\n\r\nThe help file online :  https:\/\/wolfgangmehner.github.io\/vim-plugins\/doc\/perlsupport.html\r\n\r\nThe key mappings of this plug-in :  https:\/\/wolfgangmehner.github.io\/vim-plugins\/perlsupport\/perl-hot-keys.pdf\r\n\r\nThe installation explained :  \"Make Vim as Your Perl-IDE Using perl-support Plugin\"\r\n(http:\/\/www.thegeekstuff.com\/2009\/01\/make-vim-as-your-perl-ide-using-perl-supportvim-plugin)\r\n\r\nDOCUMENTATION\r\n--------------------------------------------------------\r\nThis plug-in comes with a help file (perlsupport.txt). Read it with\r\n\r\n    :help perlsupport\r\n\r\n** PLEASE READ THE DOCUMENTATION **\r\n\r\nEditing actions differ for different modes! There are a lot of features which\r\ncan be configured or customized to match your needs.\r\n\r\nGitHub\r\n--------------------------------------------------------\r\nPerl-Support is on GitHub:\r\n\r\n    https:\/\/github.com\/WolfgangMehner\/vim-plugins\r\n\r\n(Please help us keep track of all the issues and name your report\/request \"Perl-Support: <title>\")\r\n\r\n___________________\r\nThank you for rating perl-support !","install_details":"Copy the zip archive perl-support.zip to $HOME\/.vim\/ or $VIM\/vimfiles\r\n(on the Windows platforms) and run\r\n    unzip perl-support.zip\r\nIf you have already an older version of this plug-in and you have modified the\r\ntemplate files you may want to save your templates first or copy the files from\r\nthe archive by hand. See also the file README.md within the zip file.","5":"Copy the zip archive perl-support.zip to $HOME\/.vim\/ or $VIM\/vimfiles\r\n(on the Windows platforms) and run\r\n    unzip perl-support.zip\r\nIf you have already an older version of this plug-in and you have modified the\r\ntemplate files you may want to save your templates first or copy the files from\r\nthe archive by hand. See also the file README.md within the zip file.","first_name":"Fritz","6":"Fritz","last_name":"Mehner","7":"Mehner","releases":[{"0":"556","vim_version":"7.3","1":"7.3","script_version":"5.4","2":"5.4","version_comment":"- Add 'g:Perl_CustomTemplateFile'.\r\n- Add template personalization file and setup wizard.\r\n- Rename setting 'g:Perl_Perl' into 'g:Perl_Executable'.\r\n  ('g:Perl_Perl' still works for backwards compatibility.)\r\n- Respect 'g:Xterm_Executable' and 'g:Xterm_Options'.\r\n  ('g:Perl_XtermDefaults' still works for backwards compatibility.)\r\n- Remove unused 'g:Perl_GuiTemplateBrowser' and 'g:Perl_MenuHeader'.\r\n- New and reworked templates.\r\n- Change map \"\\vs\" -> \"\\vps\", in favor of a more consistent naming scheme.\r\n- Minor changes.","3":"- Add 'g:Perl_CustomTemplateFile'.\r\n- Add template personalization file and setup wizard.\r\n- Rename setting 'g:Perl_Perl' into 'g:Perl_Executable'.\r\n  ('g:Perl_Perl' still works for backwards compatibility.)\r\n- Respect 'g:Xterm_Executable' and 'g:Xterm_Options'.\r\n  ('g:Perl_XtermDefaults' still works for backwards compatibility.)\r\n- Remove unused 'g:Perl_GuiTemplateBrowser' and 'g:Perl_MenuHeader'.\r\n- New and reworked templates.\r\n- Change map \"\\vs\" -> \"\\vps\", in favor of a more consistent naming scheme.\r\n- Minor changes.","package":"perl-support.zip","4":"perl-support.zip","src_id":"24473","5":"24473","creation_date":"1472317384","6":"1472317384"},{"0":"556","vim_version":"7.0","1":"7.0","script_version":"5.3.2","2":"5.3.2","version_comment":"- Use Perl::Tags::Naive instead of Perl::Tags.\r\n- Minor bugfixes.\r\n- Fixed some templates.","3":"- Use Perl::Tags::Naive instead of Perl::Tags.\r\n- Minor bugfixes.\r\n- Fixed some templates.","package":"perl-support.zip","4":"perl-support.zip","src_id":"22459","5":"22459","creation_date":"1411671187","6":"1411671187"},{"0":"556","vim_version":"7.0","1":"7.0","script_version":"5.3.1","2":"5.3.1","version_comment":"- Always load the newest version of the template engine available on 'runtimepath'.","3":"- Always load the newest version of the template engine available on 'runtimepath'.","package":"perl-support.zip","4":"perl-support.zip","src_id":"21738","5":"21738","creation_date":"1396714808","6":"1396714808"},{"0":"556","vim_version":"7.0","1":"7.0","script_version":"5.3","2":"5.3","version_comment":"- Adjusting end-of-line comments improved.\r\n- Bugfix: Map and menu entry 'Snippets->edit global templates'.\r\n- 'Run -> make script executable' (\\re) is now a toggle.\r\n- Perl interpreter can be set in ~\/.vimrc.\r\n- Script can be run via shebang (new global variable g:Perl_DirectRun)\r\n- Fixed problem with system-wide installations and plug-in managers (thanks to Yegor).\r\n- Added 'Perl_SetMapLeader' and 'Perl_ResetMapLeader'.\r\n- Bugfix: Resetting maplocalleader in filetype plug-in after setting it to the value of\r\n  g:Perl_MapLeader.\r\n- Bugfix: Better compatibility with custom mappings\r\n  (use \"normal!\" and \"noremap\" consistently).","3":"- Adjusting end-of-line comments improved.\r\n- Bugfix: Map and menu entry 'Snippets->edit global templates'.\r\n- 'Run -> make script executable' (\\re) is now a toggle.\r\n- Perl interpreter can be set in ~\/.vimrc.\r\n- Script can be run via shebang (new global variable g:Perl_DirectRun)\r\n- Fixed problem with system-wide installations and plug-in managers (thanks to Yegor).\r\n- Added 'Perl_SetMapLeader' and 'Perl_ResetMapLeader'.\r\n- Bugfix: Resetting maplocalleader in filetype plug-in after setting it to the value of\r\n  g:Perl_MapLeader.\r\n- Bugfix: Better compatibility with custom mappings\r\n  (use \"normal!\" and \"noremap\" consistently).","package":"perl-support.zip","4":"perl-support.zip","src_id":"21665","5":"21665","creation_date":"1395748010","6":"1395748010"},{"0":"556","vim_version":"7.0","1":"7.0","script_version":"5.2","2":"5.2","version_comment":"- New global variable g:Perl_InsertFileHeader (suppress file description comment for new files).\r\n- Two new ex commands: PerlScriptArguments, PerlSwitches\r\n- Specifying command line arguments and Perl command line switches improved.\r\n- Bugfix: g:Perl_LoadMenus now works.\r\n- Bugfix: g:Perl_MapLeader now works.\r\n- Bugfix: syntax check under 64-Bit MS-Windows now works.\r\n- Some settings moved to the filetype plugin.\r\n- Removed superfluous settings from the filetype plugin.\r\n- Integration of Make moved into the toolbox.\r\n- Minor improvements.","3":"- New global variable g:Perl_InsertFileHeader (suppress file description comment for new files).\r\n- Two new ex commands: PerlScriptArguments, PerlSwitches\r\n- Specifying command line arguments and Perl command line switches improved.\r\n- Bugfix: g:Perl_LoadMenus now works.\r\n- Bugfix: g:Perl_MapLeader now works.\r\n- Bugfix: syntax check under 64-Bit MS-Windows now works.\r\n- Some settings moved to the filetype plugin.\r\n- Removed superfluous settings from the filetype plugin.\r\n- Integration of Make moved into the toolbox.\r\n- Minor improvements.","package":"perl-support.zip","4":"perl-support.zip","src_id":"21048","5":"21048","creation_date":"1384620710","6":"1384620710"},{"0":"556","vim_version":"7.0","1":"7.0","script_version":"5.1","2":"5.1","version_comment":"- New menu items: 'choose makefile' (\\rcm), 'make clean' (\\rmc)\r\n- Bugfix: g:Perl_LocalTemplateFile ignored if present (thanks to S\u00c3\u00a9bastien Nobili)\r\n- Bugfix: debugger do not start in console mode\r\n- Several internal improvements.","3":"- New menu items: 'choose makefile' (\\rcm), 'make clean' (\\rmc)\r\n- Bugfix: g:Perl_LocalTemplateFile ignored if present (thanks to S\u00c3\u00a9bastien Nobili)\r\n- Bugfix: debugger do not start in console mode\r\n- Several internal improvements.","package":"perl-support.zip","4":"perl-support.zip","src_id":"18073","5":"18073","creation_date":"1338544207","6":"1338544207"},{"0":"556","vim_version":"7.0","1":"7.0","script_version":"5.0.1","2":"5.0.1","version_comment":"- Bugfix: resolve home for linked home directories\r\n- Bugfix: \":make\" and \":!make\" no longer affect each other.\r\n- Bugfix: S-F1 not working for module list.\r\n- Several internal improvements.","3":"- Bugfix: resolve home for linked home directories\r\n- Bugfix: \":make\" and \":!make\" no longer affect each other.\r\n- Bugfix: S-F1 not working for module list.\r\n- Several internal improvements.","package":"perl-support.zip","4":"perl-support.zip","src_id":"17805","5":"17805","creation_date":"1335012151","6":"1335012151"},{"0":"556","vim_version":"7.0","1":"7.0","script_version":"5.0","2":"5.0","version_comment":"++ The plug-in version 5.0+ is a rewriting of version 4.15 based on a new and more powerful template system.\r\n++  The template syntax has changed!\r\n\r\n- New template system (many thanks to Wolfgang Mehner)\r\n- A few new hotkeys and menu item.\r\n- A few hotkeys and menu items renamed.","3":"++ The plug-in version 5.0+ is a rewriting of version 4.15 based on a new and more powerful template system.\r\n++  The template syntax has changed!\r\n\r\n- New template system (many thanks to Wolfgang Mehner)\r\n- A few new hotkeys and menu item.\r\n- A few hotkeys and menu items renamed.","package":"perl-support.zip","4":"perl-support.zip","src_id":"17743","5":"17743","creation_date":"1333964170","6":"1333964170"},{"0":"556","vim_version":"7.0","1":"7.0","script_version":"4.15","2":"4.15","version_comment":"- Two new plugin tags: LICENCE, ORGANIZATION.\r\n- System-wide installation: minimal Template file for a user will automatically\r\n  be added.\r\n- Hotkeys \\lcs, \\ucs removed.\r\n- Minor improvements.","3":"- Two new plugin tags: LICENCE, ORGANIZATION.\r\n- System-wide installation: minimal Template file for a user will automatically\r\n  be added.\r\n- Hotkeys \\lcs, \\ucs removed.\r\n- Minor improvements.","package":"perl-support.zip","4":"perl-support.zip","src_id":"17460","5":"17460","creation_date":"1329241824","6":"1329241824"},{"0":"556","vim_version":"7.0","1":"7.0","script_version":"4.14","2":"4.14","version_comment":"- Plugin loads faster: loading the templates is delayed until the first use.\r\n- Plugin now works with pathogen.vim.\r\n- Menus will always be generated (for the use with :emenu).\r\n- Bugfix: no local templates available with a system-wide installation (thanks to Iain Arnell).\r\n- Minor improvements.\r\n","3":"- Plugin loads faster: loading the templates is delayed until the first use.\r\n- Plugin now works with pathogen.vim.\r\n- Menus will always be generated (for the use with :emenu).\r\n- Bugfix: no local templates available with a system-wide installation (thanks to Iain Arnell).\r\n- Minor improvements.\r\n","package":"perl-support.zip","4":"perl-support.zip","src_id":"16741","5":"16741","creation_date":"1319564941","6":"1319564941"},{"0":"556","vim_version":"7.0","1":"7.0","script_version":"4.13","2":"4.13","version_comment":"- Several hotkeys allow a range, e.g. '3\\cl' (see help text and perl-hot-key.pdf).\r\n- perltidy backup files optional.\r\n- POD files have no longer filetype 'perl' (preserves proper syntyx highlighting).\r\n- Running Perl as debugger (\\rd, F9) uses Perl switches set with \\rw (thanks to S\u00c3\u00a9bastien Nobili).\r\n- Minor improvements.","3":"- Several hotkeys allow a range, e.g. '3\\cl' (see help text and perl-hot-key.pdf).\r\n- perltidy backup files optional.\r\n- POD files have no longer filetype 'perl' (preserves proper syntyx highlighting).\r\n- Running Perl as debugger (\\rd, F9) uses Perl switches set with \\rw (thanks to S\u00c3\u00a9bastien Nobili).\r\n- Minor improvements.","package":"perl-support.zip","4":"perl-support.zip","src_id":"16507","5":"16507","creation_date":"1315765226","6":"1315765226"},{"0":"556","vim_version":"7.0","1":"7.0","script_version":"4.12","2":"4.12","version_comment":"- New: folding for the plugin list.\r\n- New: hotkey \\rpnh (browse NYTProf Html files).\r\n- perltidy can be used as standard beautifier (commands \"={motion}\" ).\r\n- perltidy writes backup files.\r\n- perltidy error handling improved.\r\n- Perl::Tags is disabled by default.\r\n- Bugfix: the names of the CSV-files produced by Devel::NYTProf have changed.\r\n- Bugfix: ddd not running from Vim under a display manager.\r\n- Minor improvements.","3":"- New: folding for the plugin list.\r\n- New: hotkey \\rpnh (browse NYTProf Html files).\r\n- perltidy can be used as standard beautifier (commands \"={motion}\" ).\r\n- perltidy writes backup files.\r\n- perltidy error handling improved.\r\n- Perl::Tags is disabled by default.\r\n- Bugfix: the names of the CSV-files produced by Devel::NYTProf have changed.\r\n- Bugfix: ddd not running from Vim under a display manager.\r\n- Minor improvements.","package":"perl-support.zip","4":"perl-support.zip","src_id":"15962","5":"15962","creation_date":"1308852682","6":"1308852682"},{"0":"556","vim_version":"7.0","1":"7.0","script_version":"4.11","2":"4.11","version_comment":"- Perl::Critic integration: severity and verbosity will be taken from the\r\n\tconfiguration file if specified.\r\n- Bugfix (Windows only): wrong quoting with command line parameters.\r\n- Several minor improvements.","3":"- Perl::Critic integration: severity and verbosity will be taken from the\r\n\tconfiguration file if specified.\r\n- Bugfix (Windows only): wrong quoting with command line parameters.\r\n- Several minor improvements.","package":"perl-support.zip","4":"perl-support.zip","src_id":"15492","5":"15492","creation_date":"1303380927","6":"1303380927"},{"0":"556","vim_version":"7.0","1":"7.0","script_version":"4.10","2":"4.10","version_comment":"- Bugfix: detection of a system-wide installation can fail.\r\n- Minor improvements.","3":"- Bugfix: detection of a system-wide installation can fail.\r\n- Minor improvements.","package":"perl-support.zip","4":"perl-support.zip","src_id":"15126","5":"15126","creation_date":"1298746918","6":"1298746918"},{"0":"556","vim_version":"7.0","1":"7.0","script_version":"4.9","2":"4.9","version_comment":"- Windows: user and system installation.\r\n- Integration of Perl::Tags reworked.\r\n- Several minor bugfixes.","3":"- Windows: user and system installation.\r\n- Integration of Perl::Tags reworked.\r\n- Several minor bugfixes.","package":"perl-support.zip","4":"perl-support.zip","src_id":"14523","5":"14523","creation_date":"1292439382","6":"1292439382"},{"0":"556","vim_version":"7.0","1":"7.0","script_version":"4.8","2":"4.8","version_comment":"- Hotkeys \\$x, \\@x and \\%x renamed (to avoid conflicts when writing references).\r\n- Bugfix, Regex-Tester: colouring matches shows an error message in a few cases.","3":"- Hotkeys \\$x, \\@x and \\%x renamed (to avoid conflicts when writing references).\r\n- Bugfix, Regex-Tester: colouring matches shows an error message in a few cases.","package":"perl-support.zip","4":"perl-support.zip","src_id":"13075","5":"13075","creation_date":"1275303033","6":"1275303033"},{"0":"556","vim_version":"7.0","1":"7.0","script_version":"4.7.1","2":"4.7.1","version_comment":"- Bugfixes: insertion of Posix classes from the menu not working properly.\r\n- Bugfixes, Regex Tester: accented characters can be used.\r\n- Bugfixes, Regex Tester: embedded Perl code can be used.\r\n- Bugfixes: local installation looks like a system-wide installation in seldom cases.","3":"- Bugfixes: insertion of Posix classes from the menu not working properly.\r\n- Bugfixes, Regex Tester: accented characters can be used.\r\n- Bugfixes, Regex Tester: embedded Perl code can be used.\r\n- Bugfixes: local installation looks like a system-wide installation in seldom cases.","package":"perl-support.zip","4":"perl-support.zip","src_id":"12819","5":"12819","creation_date":"1271093693","6":"1271093693"},{"0":"556","vim_version":"7.0","1":"7.0","script_version":"4.7","2":"4.7","version_comment":"- Run make (+arguments) from the 'Run' menu; 2 additional hotkeys.\r\n- Bugfix (Windows): syntax check does not catch error message if a closing\r\n  brace is missing (thanks to Dave DelGreco for fixing this bug).\r\n","3":"- Run make (+arguments) from the 'Run' menu; 2 additional hotkeys.\r\n- Bugfix (Windows): syntax check does not catch error message if a closing\r\n  brace is missing (thanks to Dave DelGreco for fixing this bug).\r\n","package":"perl-support.zip","4":"perl-support.zip","src_id":"12539","5":"12539","creation_date":"1267537475","6":"1267537475"},{"0":"556","vim_version":"7.0","1":"7.0","script_version":"4.6.1","2":"4.6.1","version_comment":"- Bugfix (Vim, not gVim): screen isn't refreshing properly when using syntax\r\n  check and a few other commands (thanks to Iain Arnell).","3":"- Bugfix (Vim, not gVim): screen isn't refreshing properly when using syntax\r\n  check and a few other commands (thanks to Iain Arnell).","package":"perl-support.zip","4":"perl-support.zip","src_id":"12177","5":"12177","creation_date":"1264409466","6":"1264409466"},{"0":"556","vim_version":"7.0","1":"7.0","script_version":"4.6","2":"4.6","version_comment":"- The profilers Devel::SmallProf and Devel::NYTProf can now be used under Windows.\r\n- New profiler menu.\r\n- New hotkeys for calling podchecker and the pod2xxx converter.\r\n- Pathnames can contain blanks.\r\n- Template completion: behavior of Ctrl-j improved.\r\n- Template system: new attributes 'indent', 'noindent'\r\n- Comment alignment improved.\r\n- Bugfix (Windows). snippet directory unreachable.\r\n- Minor improvements.\r\n\r\n","3":"- The profilers Devel::SmallProf and Devel::NYTProf can now be used under Windows.\r\n- New profiler menu.\r\n- New hotkeys for calling podchecker and the pod2xxx converter.\r\n- Pathnames can contain blanks.\r\n- Template completion: behavior of Ctrl-j improved.\r\n- Template system: new attributes 'indent', 'noindent'\r\n- Comment alignment improved.\r\n- Bugfix (Windows). snippet directory unreachable.\r\n- Minor improvements.\r\n\r\n","package":"perl-support.zip","4":"perl-support.zip","src_id":"11969","5":"11969","creation_date":"1262004896","6":"1262004896"},{"0":"556","vim_version":"7.0","1":"7.0","script_version":"4.5","2":"4.5","version_comment":"- Profiler NYTProf: menu item and ex-command to start a html-viewer.\r\n- New conversion: Pod to Pdf (if Pod::Pdf is installed).\r\n- Perltidy,  v-mode: can be used in non-perl files (for embedded Perl).\r\n- Bugfix: hotkey \\ifu not working.\r\n- Bugfix: running and starting the debugger causes error if working directory is not\r\n  the directory of the current file.\r\n- Bugfix: missing variable Perl_TimestampFormat.\r\n- Minor improvements.","3":"- Profiler NYTProf: menu item and ex-command to start a html-viewer.\r\n- New conversion: Pod to Pdf (if Pod::Pdf is installed).\r\n- Perltidy,  v-mode: can be used in non-perl files (for embedded Perl).\r\n- Bugfix: hotkey \\ifu not working.\r\n- Bugfix: running and starting the debugger causes error if working directory is not\r\n  the directory of the current file.\r\n- Bugfix: missing variable Perl_TimestampFormat.\r\n- Minor improvements.","package":"perl-support.zip","4":"perl-support.zip","src_id":"11480","5":"11480","creation_date":"1254656493","6":"1254656493"},{"0":"556","vim_version":"7.0","1":"7.0","script_version":"4.4","2":"4.4","version_comment":"- Hotkeys are shown in the menus.\r\n- Four hotkeys renamed.\r\n- Hardcopy (run menu) can print any buffer.\r\n- Bugfix (Windows only): syntax check for files with pathnames containing blanks not working.\r\n- Minor improvements.","3":"- Hotkeys are shown in the menus.\r\n- Four hotkeys renamed.\r\n- Hardcopy (run menu) can print any buffer.\r\n- Bugfix (Windows only): syntax check for files with pathnames containing blanks not working.\r\n- Minor improvements.","package":"perl-support.zip","4":"perl-support.zip","src_id":"10934","5":"10934","creation_date":"1246609675","6":"1246609675"},{"0":"556","vim_version":"7.0","1":"7.0","script_version":"4.3","2":"4.3","version_comment":"+ File browser for code snippets and templates choosable (2 global variables).\r\n+ Comments menu: adjustment of end-of-line comments further improved.\r\n+ Bugfix: Error message when opening files and Perl::Tags is not installed.","3":"+ File browser for code snippets and templates choosable (2 global variables).\r\n+ Comments menu: adjustment of end-of-line comments further improved.\r\n+ Bugfix: Error message when opening files and Perl::Tags is not installed.","package":"perl-support.zip","4":"perl-support.zip","src_id":"10678","5":"10678","creation_date":"1243268473","6":"1243268473"},{"0":"556","vim_version":"7.0","1":"7.0","script_version":"4.2","2":"4.2","version_comment":"+ Regex Analyser extended: check several regular expressions against several targets.\r\n+ Regex Analyser extended: regular expressions with  match-time code evaluation possible.\r\n+ Regex Analyser extended: g-modifier allowed; all matches will be shown.\r\n+ Regex Analyser extended: qr\/...\/ can be picked up.\r\n+ Comments menu: adjustment of end-of-line comments improved.\r\n+ Statements menu: else block (key mapping \\se).\r\n+ Regex menu: new special variables (Perl 5.10)\r\n+ Templates: handling of <SPLIT> improved.\r\n+ Bugfix: Perl::Tags integration not working.\r\n+ Minor improvements and bugfixes.","3":"+ Regex Analyser extended: check several regular expressions against several targets.\r\n+ Regex Analyser extended: regular expressions with  match-time code evaluation possible.\r\n+ Regex Analyser extended: g-modifier allowed; all matches will be shown.\r\n+ Regex Analyser extended: qr\/...\/ can be picked up.\r\n+ Comments menu: adjustment of end-of-line comments improved.\r\n+ Statements menu: else block (key mapping \\se).\r\n+ Regex menu: new special variables (Perl 5.10)\r\n+ Templates: handling of <SPLIT> improved.\r\n+ Bugfix: Perl::Tags integration not working.\r\n+ Minor improvements and bugfixes.","package":"perl-support.zip","4":"perl-support.zip","src_id":"10560","5":"10560","creation_date":"1241774773","6":"1241774773"},{"0":"556","vim_version":"7.0","1":"7.0","script_version":"4.1.1","2":"4.1.1","version_comment":"+ Bugfix (Windows only): templates will be loaded twice, generating a long list \r\n  of error messages.\r\n","3":"+ Bugfix (Windows only): templates will be loaded twice, generating a long list \r\n  of error messages.\r\n","package":"perl-support.zip","4":"perl-support.zip","src_id":"10403","5":"10403","creation_date":"1239810573","6":"1239810573"},{"0":"556","vim_version":"7.0","1":"7.0","script_version":"4.1","2":"4.1","version_comment":"+ Additional plugin-tags (jump targets in templates): <+text+>, <-text->.\r\n+ Additional mapping Ctrl-j : jump to these new targets.\r\n+ Template-file: additional macro |STYLE| and IF-ENDIF-construct to easily\r\n  choose between sets of templates.\r\n+ SmallProf integration completely rewritten: hotspot report, report sortable.\r\n+ FastProf and NYTProf integration.\r\n+ Command completion for the command CriticSeverity.\r\n+ Minor improvements and bugfixes.","3":"+ Additional plugin-tags (jump targets in templates): <+text+>, <-text->.\r\n+ Additional mapping Ctrl-j : jump to these new targets.\r\n+ Template-file: additional macro |STYLE| and IF-ENDIF-construct to easily\r\n  choose between sets of templates.\r\n+ SmallProf integration completely rewritten: hotspot report, report sortable.\r\n+ FastProf and NYTProf integration.\r\n+ Command completion for the command CriticSeverity.\r\n+ Minor improvements and bugfixes.","package":"perl-support.zip","4":"perl-support.zip","src_id":"10227","5":"10227","creation_date":"1237237714","6":"1237237714"},{"0":"556","vim_version":"7.0","1":"7.0","script_version":"4.0.2","2":"4.0.2","version_comment":"+ Bugfix: 3 global variables without effect (format for date, time, year).","3":"+ Bugfix: 3 global variables without effect (format for date, time, year).","package":"perl-support.zip","4":"perl-support.zip","src_id":"9813","5":"9813","creation_date":"1231919802","6":"1231919802"},{"0":"556","vim_version":"7.0","1":"7.0","script_version":"4.0.1","2":"4.0.1","version_comment":"+ Bugfix: Error message in some functions that issue a prompt.","3":"+ Bugfix: Error message in some functions that issue a prompt.","package":"perl-support.zip","4":"perl-support.zip","src_id":"9746","5":"9746","creation_date":"1230892349","6":"1230892349"},{"0":"556","vim_version":"7.0","1":"7.0","script_version":"4.0","2":"4.0","version_comment":"+ Completely new template system. Most menu items now user definable.\r\n+ Plugin split into autoloadable modules (makes Vim startup faster).\r\n+ Submenus for perlcritic severity and verbosity.\r\nIn consequence there are some obsolete files and global variables, and some new\r\nfiles and hotkeys.","3":"+ Completely new template system. Most menu items now user definable.\r\n+ Plugin split into autoloadable modules (makes Vim startup faster).\r\n+ Submenus for perlcritic severity and verbosity.\r\nIn consequence there are some obsolete files and global variables, and some new\r\nfiles and hotkeys.","package":"perl-support.zip","4":"perl-support.zip","src_id":"9701","5":"9701","creation_date":"1229676262","6":"1229676262"},{"0":"556","vim_version":"7.0","1":"7.0","script_version":"3.9.1","2":"3.9.1","version_comment":"+ Bugfix: idiom 'open input file' not usable (thanks to Marcus A\u00c3\u009fhauer for\r\n  spotting and fixing it).","3":"+ Bugfix: idiom 'open input file' not usable (thanks to Marcus A\u00c3\u009fhauer for\r\n  spotting and fixing it).","package":"perl-support.zip","4":"perl-support.zip","src_id":"9578","5":"9578","creation_date":"1227773311","6":"1227773311"},{"0":"556","vim_version":"7.0","1":"7.0","script_version":"3.9","2":"3.9","version_comment":"+ New item in menu Statements: elsif (shortcut \\sei)\r\n- Map leader for hotkeys now user definable: new global variable g:BASH_MapLeader\r\n+ Specification of command line arguments (Run->cmd. line arg.): filename completion active.","3":"+ New item in menu Statements: elsif (shortcut \\sei)\r\n- Map leader for hotkeys now user definable: new global variable g:BASH_MapLeader\r\n+ Specification of command line arguments (Run->cmd. line arg.): filename completion active.","package":"perl-support.zip","4":"perl-support.zip","src_id":"9554","5":"9554","creation_date":"1227529055","6":"1227529055"},{"0":"556","vim_version":"6.0","1":"6.0","script_version":"3.8.1","2":"3.8.1","version_comment":"+ Bugfix:  In insert mode and in non-empty lines.hotkeys beginning like references (e.g. \\$ ) are now inactive.","3":"+ Bugfix:  In insert mode and in non-empty lines.hotkeys beginning like references (e.g. \\$ ) are now inactive.","package":"perl-support.zip","4":"perl-support.zip","src_id":"8855","5":"8855","creation_date":"1214458773","6":"1214458773"},{"0":"556","vim_version":"6.0","1":"6.0","script_version":"3.8","2":"3.8","version_comment":"+ New regular expression testing tool.\r\n+ 'code->comment' and 'comment->code'  are replaced by a toggle: 'toggle comment'\r\n+ 'explain regex' can use flags now.\r\n+ 'run->settings'  shows the  Perl interface version.\r\n+ Superfluous control characters for mode switching (menus, hotkeys) removed. Caused beeps.\r\n+ Some minor improvements.","3":"+ New regular expression testing tool.\r\n+ 'code->comment' and 'comment->code'  are replaced by a toggle: 'toggle comment'\r\n+ 'explain regex' can use flags now.\r\n+ 'run->settings'  shows the  Perl interface version.\r\n+ Superfluous control characters for mode switching (menus, hotkeys) removed. Caused beeps.\r\n+ Some minor improvements.","package":"perl-support.zip","4":"perl-support.zip","src_id":"8726","5":"8726","creation_date":"1211762890","6":"1211762890"},{"0":"556","vim_version":"6.0","1":"6.0","script_version":"3.7","2":"3.7","version_comment":"+ Regex analyser YAPE::Regex::Explain integrated (optional).\r\n+ Bugfix: use correct pathnames under Cygwin.\r\n+ Bugfix: always use the right perl executable to list the installed Perl modules.\r\n+ Minor changes due to ctags, version 5.7.\r\n+ Global variable g:Perl_PerlTags is no longer needed.","3":"+ Regex analyser YAPE::Regex::Explain integrated (optional).\r\n+ Bugfix: use correct pathnames under Cygwin.\r\n+ Bugfix: always use the right perl executable to list the installed Perl modules.\r\n+ Minor changes due to ctags, version 5.7.\r\n+ Global variable g:Perl_PerlTags is no longer needed.","package":"perl-support.zip","4":"perl-support.zip","src_id":"8112","5":"8112","creation_date":"1199234572","6":"1199234572"},{"0":"556","vim_version":"6.0","1":"6.0","script_version":"3.6.3","2":"3.6.3","version_comment":"+ Changes to allow a system-wide installation.","3":"+ Changes to allow a system-wide installation.","package":"perl-support.zip","4":"perl-support.zip","src_id":"7432","5":"7432","creation_date":"1185842741","6":"1185842741"},{"0":"556","vim_version":"6.0","1":"6.0","script_version":"3.6.2","2":"3.6.2","version_comment":"+ Snippets can now be managed in the console mode.\r\n+ Three new key mappings for snippets.\r\n+ Bugfix: quitting the module list buffer no longer terminates the editor.\r\n+ Documentation: section about optional dependencies added.","3":"+ Snippets can now be managed in the console mode.\r\n+ Three new key mappings for snippets.\r\n+ Bugfix: quitting the module list buffer no longer terminates the editor.\r\n+ Documentation: section about optional dependencies added.","package":"perl-support.zip","4":"perl-support.zip","src_id":"7288","5":"7288","creation_date":"1182507322","6":"1182507322"},{"0":"556","vim_version":"6.0","1":"6.0","script_version":"3.6.1","2":"3.6.1","version_comment":"+ Support for Perl::Tags added (see the help file).","3":"+ Support for Perl::Tags added (see the help file).","package":"perl-support.zip","4":"perl-support.zip","src_id":"7247","5":"7247","creation_date":"1181819891","6":"1181819891"},{"0":"556","vim_version":"6.0","1":"6.0","script_version":"3.6","2":"3.6","version_comment":"+ New command enables the alignment of line end comments (menu item, hotkey). \r\n+ Idioms hotkeys renamed (better to remember).\r\n+ Lot of new mappings for the insert mode.\r\n+ The code for opening files or pipes can surround a marked area (v-mode).\r\n+ Script pmdesc3 removes POD markup sequences now.","3":"+ New command enables the alignment of line end comments (menu item, hotkey). \r\n+ Idioms hotkeys renamed (better to remember).\r\n+ Lot of new mappings for the insert mode.\r\n+ The code for opening files or pipes can surround a marked area (v-mode).\r\n+ Script pmdesc3 removes POD markup sequences now.","package":"perl-support.zip","4":"perl-support.zip","src_id":"7178","5":"7178","creation_date":"1180496891","6":"1180496891"},{"0":"556","vim_version":"6.0","1":"6.0","script_version":"3.4","2":"3.4","version_comment":"+ Adaption for 'perlcritic', version 1.03 . Interface improved.\r\n+ Three new Ex commands to control 'perlcritic'.\r\n+ Subdirectories rearranged.\r\n+ Escaping special characters in filenames reworked (Unix,Windows).","3":"+ Adaption for 'perlcritic', version 1.03 . Interface improved.\r\n+ Three new Ex commands to control 'perlcritic'.\r\n+ Subdirectories rearranged.\r\n+ Escaping special characters in filenames reworked (Unix,Windows).","package":"perl-support.zip","4":"perl-support.zip","src_id":"6743","5":"6743","creation_date":"1171530984","6":"1171530984"},{"0":"556","vim_version":"6.0","1":"6.0","script_version":"3.3","2":"3.3","version_comment":"+ One new and two improved mappings (\\cs, \\co, \\cc). \r\n+ All command mappings can be switched off by a global variable.\r\n+ Bugfix: empty new file after removing the header template can't be closed.\r\n+ Bugfix [Windows]: perlcritic messages are sometimes garbled (Thanks to Igor Prischepoff).\r\n+ Bugfix : Tools entry missing when root menu not shown from the start.\r\n","3":"+ One new and two improved mappings (\\cs, \\co, \\cc). \r\n+ All command mappings can be switched off by a global variable.\r\n+ Bugfix: empty new file after removing the header template can't be closed.\r\n+ Bugfix [Windows]: perlcritic messages are sometimes garbled (Thanks to Igor Prischepoff).\r\n+ Bugfix : Tools entry missing when root menu not shown from the start.\r\n","package":"perl-support.zip","4":"perl-support.zip","src_id":"6570","5":"6570","creation_date":"1167727338","6":"1167727338"},{"0":"556","vim_version":"6.0","1":"6.0","script_version":"3.2.2","2":"3.2.2","version_comment":"+ Bugfix: wrong position when building regular expressions in visual mode at  the end of a line.\r\n+ Bugfix [cygwin]: unnecessary error message when starting vim not gvim).\r\n+ Perl keyword help (S-F1) improved.\r\n+ Insertion and substitution from the menus protected against  non-plugin mappings.\r\n","3":"+ Bugfix: wrong position when building regular expressions in visual mode at  the end of a line.\r\n+ Bugfix [cygwin]: unnecessary error message when starting vim not gvim).\r\n+ Perl keyword help (S-F1) improved.\r\n+ Insertion and substitution from the menus protected against  non-plugin mappings.\r\n","package":"perl-support.zip","4":"perl-support.zip","src_id":"6524","5":"6524","creation_date":"1166506006","6":"1166506006"},{"0":"556","vim_version":"6.0","1":"6.0","script_version":"3.2.1","2":"3.2.1","version_comment":"+ Better adaption for 'perlcritic', version 0.19 .\r\n+ Bugfix: key mappings \\cb and \\cn are working now.","3":"+ Better adaption for 'perlcritic', version 0.19 .\r\n+ Bugfix: key mappings \\cb and \\cn are working now.","package":"perl-support.zip","4":"perl-support.zip","src_id":"6107","5":"6107","creation_date":"1156829188","6":"1156829188"},{"0":"556","vim_version":"6.0","1":"6.0","script_version":"3.2","2":"3.2","version_comment":"+ New command and menu entry for commenting\/uncommenting larger blocks of code.\r\n+ Some POD statements now have a visual mode.\r\n+ Setting the column for the start of line-end comments improved.\r\n+ Mac OS X : circumvent a Vim bug which caused a crash when loading plugin version 3.1.\r\n+ File syntax\/perl.vim removed (but see help in perlsupport.txt).","3":"+ New command and menu entry for commenting\/uncommenting larger blocks of code.\r\n+ Some POD statements now have a visual mode.\r\n+ Setting the column for the start of line-end comments improved.\r\n+ Mac OS X : circumvent a Vim bug which caused a crash when loading plugin version 3.1.\r\n+ File syntax\/perl.vim removed (but see help in perlsupport.txt).","package":"perl-support.zip","4":"perl-support.zip","src_id":"6023","5":"6023","creation_date":"1154485062","6":"1154485062"},{"0":"556","vim_version":"7.0","1":"7.0","script_version":"3.1","2":"3.1","version_comment":"+ Adaption for 'perlcritic', version 0.16 .\r\n+ Bugfix: The profiler now gets the command line arguments of the script.\r\n+ Minor bugfixes and improvements.","3":"+ Adaption for 'perlcritic', version 0.16 .\r\n+ Bugfix: The profiler now gets the command line arguments of the script.\r\n+ Minor bugfixes and improvements.","package":"perl-support.zip","4":"perl-support.zip","src_id":"5724","5":"5724","creation_date":"1148007886","6":"1148007886"},{"0":"556","vim_version":"6.0","1":"6.0","script_version":"3.0","2":"3.0","version_comment":"+ Adaption for Vim 7.\r\n+ The hotkeys F9 and \\rd now also starts the debugger (perl -d ..) if vim is running  without GUI.\r\n+ Debugger starts correctly for scripts with command line arguments (Windows only).\r\n+ Minor improvements.","3":"+ Adaption for Vim 7.\r\n+ The hotkeys F9 and \\rd now also starts the debugger (perl -d ..) if vim is running  without GUI.\r\n+ Debugger starts correctly for scripts with command line arguments (Windows only).\r\n+ Minor improvements.","package":"perl-support.zip","4":"perl-support.zip","src_id":"5578","5":"5578","creation_date":"1145356011","6":"1145356011"},{"0":"556","vim_version":"6.0","1":"6.0","script_version":"2.9.2","2":"2.9.2","version_comment":"+ Adaption for 'perlcritic', version 0.15 .\r\n+ New template file for POD documentation files.\r\n+ Minor bugs fixed and improvements.","3":"+ Adaption for 'perlcritic', version 0.15 .\r\n+ New template file for POD documentation files.\r\n+ Minor bugs fixed and improvements.","package":"perl-support.zip","4":"perl-support.zip","src_id":"5525","5":"5525","creation_date":"1144290994","6":"1144290994"},{"0":"556","vim_version":"6.0","1":"6.0","script_version":"2.9.1","2":"2.9.1","version_comment":"+ New menu entry for setting perl command line switches (Thanks to Adam MacKinnon).\r\n+ For files with extension 't' (Perl test files) the filetype is set to 'perl'. This\r\n  allows syntax checking, reading help, and checking with perlcritic.\r\n+ There is a new comment template file 'perl-test-header' which will be\r\n  inserted at the beginning of a new test file (extension 't').\r\n+ Comment after some POD directives removed (podchecker showed errors).","3":"+ New menu entry for setting perl command line switches (Thanks to Adam MacKinnon).\r\n+ For files with extension 't' (Perl test files) the filetype is set to 'perl'. This\r\n  allows syntax checking, reading help, and checking with perlcritic.\r\n+ There is a new comment template file 'perl-test-header' which will be\r\n  inserted at the beginning of a new test file (extension 't').\r\n+ Comment after some POD directives removed (podchecker showed errors).","package":"perl-support.zip","4":"perl-support.zip","src_id":"5339","5":"5339","creation_date":"1141116098","6":"1141116098"},{"0":"556","vim_version":"6.0","1":"6.0","script_version":"2.9","2":"2.9","version_comment":"+ perlcritic integrated. Runs like a compiler. Opens a quickfix error window.<br>\r\n+ Help menu entry added (plugin help).\r\n+ A hardcopy shows date and time in the header line.\r\n+ open file\/pipe idioms according to Conway's \"Perl Best Practices\".\r\n+ POSIX class [:blank:] added.\r\n+ Bugfix: Wrong cursor positon in hash idiom.\r\n+ Plugin can be used with autocompletion for (, [, and { .","3":"+ perlcritic integrated. Runs like a compiler. Opens a quickfix error window.<br>\r\n+ Help menu entry added (plugin help).\r\n+ A hardcopy shows date and time in the header line.\r\n+ open file\/pipe idioms according to Conway's \"Perl Best Practices\".\r\n+ POSIX class [:blank:] added.\r\n+ Bugfix: Wrong cursor positon in hash idiom.\r\n+ Plugin can be used with autocompletion for (, [, and { .","package":"perl-support.zip","4":"perl-support.zip","src_id":"5014","5":"5014","creation_date":"1138674409","6":"1138674409"},{"0":"556","vim_version":"6.0","1":"6.0","script_version":"2.8.2","2":"2.8.2","version_comment":"+ Bugfix: Starting perltidy called a wrong function.","3":"+ Bugfix: Starting perltidy called a wrong function.","package":"perl-support.zip","4":"perl-support.zip","src_id":"4801","5":"4801","creation_date":"1132705385","6":"1132705385"},{"0":"556","vim_version":"6.0","1":"6.0","script_version":"2.8.1","2":"2.8.1","version_comment":"+ Bugfix: Some key mappings not working\/not properly working (Thanks to Edward Wijaya).\r\n+ Bugfix: Unnecessary message 'Made file executable' removed (Thanks to Edward Wijaya).\r\n+ Bugfix: Wrong quoting for script arguments fixed; Windows only (Thanks to Norin Raad).","3":"+ Bugfix: Some key mappings not working\/not properly working (Thanks to Edward Wijaya).\r\n+ Bugfix: Unnecessary message 'Made file executable' removed (Thanks to Edward Wijaya).\r\n+ Bugfix: Wrong quoting for script arguments fixed; Windows only (Thanks to Norin Raad).","package":"perl-support.zip","4":"perl-support.zip","src_id":"4774","5":"4774","creation_date":"1132277512","6":"1132277512"},{"0":"556","vim_version":"6.0","1":"6.0","script_version":"2.8","2":"2.8","version_comment":"+ Podchecker integrated. Runs like a compiler. Opens a quickfix error window.\r\n+ Script will be made executable before running it (e.g. after a \"Save As...\").\r\n+ Many blanks in 2 POD templates removes which garbled the resulting documents (bugfix).\r\n+ Message now visible if SmallProf is not runable (bugfix).","3":"+ Podchecker integrated. Runs like a compiler. Opens a quickfix error window.\r\n+ Script will be made executable before running it (e.g. after a \"Save As...\").\r\n+ Many blanks in 2 POD templates removes which garbled the resulting documents (bugfix).\r\n+ Message now visible if SmallProf is not runable (bugfix).","package":"perl-support.zip","4":"perl-support.zip","src_id":"4721","5":"4721","creation_date":"1131060201","6":"1131060201"},{"0":"556","vim_version":"6.0","1":"6.0","script_version":"2.7","2":"2.7","version_comment":"+ POD: \\\"invisible POD\\\" added (as suggested in Conway\\'s book \\\"Perl Best Practices\\\").<br>\r\n+ POD: sequence insertion improved; \\'<E>\\' added; \\'=for\\' added.<br>\r\n+ <S-F1> (read perldoc) now works only for filetype \\'perl\\' .<br>\r\n+ Some idioms improved (e.g. opening files, subroutine stub).<br>\r\n+ Added \\':\\' to the keyword characters; recognizes tokens like \\'Net::Cmd\\' as one keyword.<br>\r\n+ Perltidy integration made safer.<br>\r\n+ Starting an xterm was not possible with some installations (bugfix).","3":"+ POD: \\\"invisible POD\\\" added (as suggested in Conway\\'s book \\\"Perl Best Practices\\\").<br>\r\n+ POD: sequence insertion improved; \\'<E>\\' added; \\'=for\\' added.<br>\r\n+ <S-F1> (read perldoc) now works only for filetype \\'perl\\' .<br>\r\n+ Some idioms improved (e.g. opening files, subroutine stub).<br>\r\n+ Added \\':\\' to the keyword characters; recognizes tokens like \\'Net::Cmd\\' as one keyword.<br>\r\n+ Perltidy integration made safer.<br>\r\n+ Starting an xterm was not possible with some installations (bugfix).","package":"perl-support.zip","4":"perl-support.zip","src_id":"4684","5":"4684","creation_date":"1129715039","6":"1129715039"},{"0":"556","vim_version":"6.0","1":"6.0","script_version":"2.6","2":"2.6","version_comment":"+ blocks: opening brace no longer on a new line (adjustable for backward compatibility).\r\n+ Vim (without GUI): new key mappings: all entries in the run menu do have mappings now.\r\n+ Vim (without GUI): perldoc can be read with hotkeys \\h and \\rp .\r\n+ Vim (without GUI): perldoc displays docs using plain text converter.+ output into buffer: cursor goes to top of file.\r\n+ trailing ^M in perldoc window will be removed (UNIX\/Linux).\r\n+ output into buffer: cursor goes to top of file.","3":"+ blocks: opening brace no longer on a new line (adjustable for backward compatibility).\r\n+ Vim (without GUI): new key mappings: all entries in the run menu do have mappings now.\r\n+ Vim (without GUI): perldoc can be read with hotkeys \\h and \\rp .\r\n+ Vim (without GUI): perldoc displays docs using plain text converter.+ output into buffer: cursor goes to top of file.\r\n+ trailing ^M in perldoc window will be removed (UNIX\/Linux).\r\n+ output into buffer: cursor goes to top of file.","package":"perl-support.zip","4":"perl-support.zip","src_id":"4405","5":"4405","creation_date":"1120202242","6":"1120202242"},{"0":"556","vim_version":"6.0","1":"6.0","script_version":"2.5","2":"2.5","version_comment":"+ Windows support. Most features are now available under Windows.\r\n+ Spaces in path and file names are now possible (Windows and UNIX).\r\n+ Reading documentation with perldoc improved.\r\n+ Minor bugs fixed and improvements.","3":"+ Windows support. Most features are now available under Windows.\r\n+ Spaces in path and file names are now possible (Windows and UNIX).\r\n+ Reading documentation with perldoc improved.\r\n+ Minor bugs fixed and improvements.","package":"perl-support.zip","4":"perl-support.zip","src_id":"4178","5":"4178","creation_date":"1113786725","6":"1113786725"},{"0":"556","vim_version":"6.0","1":"6.0","script_version":"2.4.1","2":"2.4.1","version_comment":"+ Run the profiler SmallProf from the menu; save different results with time stamps. \r\n+ Line end comments start in a fixed column now (can be set from the menu).\r\n+ Recommended settings for ctags corrected (Thanks to William McKee).\r\n+ Perl module list generator pmdesc3 again slightly improved.","3":"+ Run the profiler SmallProf from the menu; save different results with time stamps. \r\n+ Line end comments start in a fixed column now (can be set from the menu).\r\n+ Recommended settings for ctags corrected (Thanks to William McKee).\r\n+ Perl module list generator pmdesc3 again slightly improved.","package":"perl-support.zip","4":"perl-support.zip","src_id":"3948","5":"3948","creation_date":"1109731063","6":"1109731063"},{"0":"556","vim_version":"6.0","1":"6.0","script_version":"2.4","2":"2.4","version_comment":"+ One of three debuggers can be started with the hotkey F9.\n+ Complete file or marked area can be reformatted with perltidy. \n+ Run a perl-script: \n  (1) The script can be run from the command line.\n  (2) The output can be directed into a window with name \"Perl-Output\". \n  (3) The script can be run in an xterm (adjustable).\n+ The new hotkey Shift-F9 and the menu entry \"cmd. line arg.\" set command line\n  arguments for the current buffer.\n+ A code snippet with the file name extension \"ni\" or \"noindent\" will not be\n  indented on insertion.\n+ Bug fixed (POD->Text)","3":"+ One of three debuggers can be started with the hotkey F9.\n+ Complete file or marked area can be reformatted with perltidy. \n+ Run a perl-script: \n  (1) The script can be run from the command line.\n  (2) The output can be directed into a window with name \"Perl-Output\". \n  (3) The script can be run in an xterm (adjustable).\n+ The new hotkey Shift-F9 and the menu entry \"cmd. line arg.\" set command line\n  arguments for the current buffer.\n+ A code snippet with the file name extension \"ni\" or \"noindent\" will not be\n  indented on insertion.\n+ Bug fixed (POD->Text)","package":"perl-support.zip","4":"perl-support.zip","src_id":"3696","5":"3696","creation_date":"1102849026","6":"1102849026"},{"0":"556","vim_version":"6.0","1":"6.0","script_version":"2.3.2","2":"2.3.2","version_comment":"+ Perl module list generator pmdesc3 improved (no double entries, no control\r\n   characters in version numbers, handles DOS-teminated files correctly).\r\n+ Looking up help with Shift-F1 now works also in the perldoc help buffer.\r\n+ Running a Perl-script now opens a window with name \"Perl-Output\" to display\r\n  the script output. The buffer and its content will disappear when closing\r\n  the window. \r\n\r\n","3":"+ Perl module list generator pmdesc3 improved (no double entries, no control\r\n   characters in version numbers, handles DOS-teminated files correctly).\r\n+ Looking up help with Shift-F1 now works also in the perldoc help buffer.\r\n+ Running a Perl-script now opens a window with name \"Perl-Output\" to display\r\n  the script output. The buffer and its content will disappear when closing\r\n  the window. \r\n\r\n","package":"perl-support.zip","4":"perl-support.zip","src_id":"3608","5":"3608","creation_date":"1099624740","6":"1099624740"},{"0":"556","vim_version":"6.0","1":"6.0","script_version":"2.3","2":"2.3","version_comment":"+ There is now at most one help window\/buffer.\n+ There is now at most one Perl module list window\/buffer.\n+ The perldoc help will now search in FAQs too; \n   search order :  modules - functions - FAQs. \n+ Template files and snippet files are no longer kept in the list of alternate files.\n+ A bug fixed in the Perl module list generator pmdesc3.","3":"+ There is now at most one help window\/buffer.\n+ There is now at most one Perl module list window\/buffer.\n+ The perldoc help will now search in FAQs too; \n   search order :  modules - functions - FAQs. \n+ Template files and snippet files are no longer kept in the list of alternate files.\n+ A bug fixed in the Perl module list generator pmdesc3.","package":"perl-support.zip","4":"perl-support.zip","src_id":"3544","5":"3544","creation_date":"1097744270","6":"1097744270"},{"0":"556","vim_version":"6.0","1":"6.0","script_version":"2.2","2":"2.2","version_comment":"+ Better adaption to the Windows plattforms (default directories, running scripts).\r\n+ Templates are more consistent now.\r\n+ 'Line End Comments' ignores blank lines in a marked block.","3":"+ Better adaption to the Windows plattforms (default directories, running scripts).\r\n+ Templates are more consistent now.\r\n+ 'Line End Comments' ignores blank lines in a marked block.","package":"perl-support.zip","4":"perl-support.zip","src_id":"3519","5":"3519","creation_date":"1096954500","6":"1096954500"},{"0":"556","vim_version":"6.0","1":"6.0","script_version":"2.1","2":"2.1","version_comment":"+ Installation simplified. \n+ The generation of the module list is a magnitude faster.\n+ The version of a module is now shown in the module list. \n+ The perl documentation (pod::perl*) appears in the module list.\n+ The dialog windows (GUI) have been replaced by more flexible command line inputs.\n+ User will now be asked before a snippet file will be overwritten.\n+ The undocumented and unnecessary hot key F12 has been removed.","3":"+ Installation simplified. \n+ The generation of the module list is a magnitude faster.\n+ The version of a module is now shown in the module list. \n+ The perl documentation (pod::perl*) appears in the module list.\n+ The dialog windows (GUI) have been replaced by more flexible command line inputs.\n+ User will now be asked before a snippet file will be overwritten.\n+ The undocumented and unnecessary hot key F12 has been removed.","package":"perl-support.zip","4":"perl-support.zip","src_id":"3185","5":"3185","creation_date":"1088219927","6":"1088219927"},{"0":"556","vim_version":"6.0","1":"6.0","script_version":"2.0","2":"2.0","version_comment":"+ New menu for regex-construction.\r\n+ New menu with POD commands.\r\n+ A list of all installed Perl modules can be built and read in. \r\n  The documentation for a module can be opened from this list.\r\n+ Extension to ctags + taglist shows POD table of content and enables navigation.\r\n+ Append aligned comments to all lines of a marked block.\r\n+ The root menu can be removed.\r\n+ Documentation improved.\r\n+ Bug fix (template file handling).\r\n+ Install script improved.","3":"+ New menu for regex-construction.\r\n+ New menu with POD commands.\r\n+ A list of all installed Perl modules can be built and read in. \r\n  The documentation for a module can be opened from this list.\r\n+ Extension to ctags + taglist shows POD table of content and enables navigation.\r\n+ Append aligned comments to all lines of a marked block.\r\n+ The root menu can be removed.\r\n+ Documentation improved.\r\n+ Bug fix (template file handling).\r\n+ Install script improved.","package":"perl-support.zip","4":"perl-support.zip","src_id":"3017","5":"3017","creation_date":"1084357972","6":"1084357972"},{"0":"556","vim_version":"6.0","1":"6.0","script_version":"1.9.2","2":"1.9.2","version_comment":"+ Only one entry in the gVim root menu.\n+ All hotkeys are only defined for Perl files.\n+ Install script added.\n+ Customization improved. \n+ Documentation improved.\n\n","3":"+ Only one entry in the gVim root menu.\n+ All hotkeys are only defined for Perl files.\n+ Install script added.\n+ Customization improved. \n+ Documentation improved.\n\n","package":"perl-support.zip","4":"perl-support.zip","src_id":"2202","5":"2202","creation_date":"1059967997","6":"1059967997"},{"0":"556","vim_version":"6.0","1":"6.0","script_version":"1.9","2":"1.9","version_comment":"+ 58 key mappings for Vim without GUI.  See perl-hot-keys.pdf  (reference card).\n+ A marked region can be surrounded by a for-, if-, do-while- , until-, ...   statements (with indentation).\n+ The Perl special variables have been added to the file word.list  for dictionary completion.\n+ Vim doc added (file perlsupport.txt).","3":"+ 58 key mappings for Vim without GUI.  See perl-hot-keys.pdf  (reference card).\n+ A marked region can be surrounded by a for-, if-, do-while- , until-, ...   statements (with indentation).\n+ The Perl special variables have been added to the file word.list  for dictionary completion.\n+ Vim doc added (file perlsupport.txt).","package":"perl-support.zip","4":"perl-support.zip","src_id":"2149","5":"2149","creation_date":"1058248290","6":"1058248290"},{"0":"556","vim_version":"6.0","1":"6.0","script_version":"1.8","2":"1.8","version_comment":"Tag substitution rewritten (Some characters in a substitution text for a tag \n  prevented the tag from being substituted).","3":"Tag substitution rewritten (Some characters in a substitution text for a tag \n  prevented the tag from being substituted).","package":"perl-support.zip","4":"perl-support.zip","src_id":"2030","5":"2030","creation_date":"1054373880","6":"1054373880"},{"0":"556","vim_version":"6.0","1":"6.0","script_version":"1.7","2":"1.7","version_comment":"+ Block comments are now read as templates or skeletons from files:\n      frame Comment,  function description,  file header\n+ These templates can contain tags like |FILENAME|, |AUTHOR| etc. which are replaced  after reading.\n+ indentation: multiline inserts and code snippets will be indented after insertion.\n+ Most menu entries are now also active in normal mode.\n+ Reading the templates is done in one function which can be called in an autocmd.\n+ Code cleanup: register z no longer used. Most function calls are silent now.","3":"+ Block comments are now read as templates or skeletons from files:\n      frame Comment,  function description,  file header\n+ These templates can contain tags like |FILENAME|, |AUTHOR| etc. which are replaced  after reading.\n+ indentation: multiline inserts and code snippets will be indented after insertion.\n+ Most menu entries are now also active in normal mode.\n+ Reading the templates is done in one function which can be called in an autocmd.\n+ Code cleanup: register z no longer used. Most function calls are silent now.","package":"perl-support.zip","4":"perl-support.zip","src_id":"1944","5":"1944","creation_date":"1051353684","6":"1051353684"},{"0":"556","vim_version":"6.0","1":"6.0","script_version":"1.6","2":"1.6","version_comment":"Initial upload","3":"Initial upload","package":"perl-support.vim","4":"perl-support.vim","src_id":"1702","5":"1702","creation_date":"1044608246","6":"1044608246"}]},"555":{"script_id":"555","0":"555","script_name":"HiCurLine","1":"HiCurLine","script_type":"utility","2":"utility","summary":"Highlights the current line","3":"Highlights the current line","description":"This script has a number of maps that intercept various motions and cause the current line to be highlighted.  It is a variant of <HiMtchBrkt.vim> (vimtip#177).\r\n\r\n    \\hcli : initiate HiCurLine operation\r\n    \\hcls : stop HiCurLine operation\r\n\r\n(see vimtip#411 to have HiCurLine automatically begin highlighting)\r\n\r\nHiCurLine.vim uses the HL_HiCurLine highlighting group (by default) to specify the highlighting of the current line.  One may change the highlighting group HiCurLine uses with the g:HL_HiCurLine variable.  By default,\r\n\r\n\tlet g:HL_HiCurLine= \"HL_HiCurLine\"\r\n\r\nand <HiCurLine.vim> will specify that group internally.  Otherwise, one may change the group used to whatever one wishes:\r\n\r\n\tlet g:HL_HiCurLine= \"Search\"\r\n\tlet g:HL_HiCurLine= \"Function\"\r\n\r\netc.  The default highlighting is: (background is a setting, see :he 'bg')\r\n\r\n\tbackground == dark : blue text on cyan background\r\n\tbackground == light: cyan text on blue background\r\n\r\n(alpha\/beta version available at http:\/\/www.drchip.org\/astronaut\/vim\/index.html#HICURLINE)\r\n","4":"This script has a number of maps that intercept various motions and cause the current line to be highlighted.  It is a variant of <HiMtchBrkt.vim> (vimtip#177).\r\n\r\n    \\hcli : initiate HiCurLine operation\r\n    \\hcls : stop HiCurLine operation\r\n\r\n(see vimtip#411 to have HiCurLine automatically begin highlighting)\r\n\r\nHiCurLine.vim uses the HL_HiCurLine highlighting group (by default) to specify the highlighting of the current line.  One may change the highlighting group HiCurLine uses with the g:HL_HiCurLine variable.  By default,\r\n\r\n\tlet g:HL_HiCurLine= \"HL_HiCurLine\"\r\n\r\nand <HiCurLine.vim> will specify that group internally.  Otherwise, one may change the group used to whatever one wishes:\r\n\r\n\tlet g:HL_HiCurLine= \"Search\"\r\n\tlet g:HL_HiCurLine= \"Function\"\r\n\r\netc.  The default highlighting is: (background is a setting, see :he 'bg')\r\n\r\n\tbackground == dark : blue text on cyan background\r\n\tbackground == light: cyan text on blue background\r\n\r\n(alpha\/beta version available at http:\/\/www.drchip.org\/astronaut\/vim\/index.html#HICURLINE)\r\n","install_details":"1. Put into your .vim\/plugin or\r\n   _vimfiles\\plugin directory (Unix\/Windows)\r\n2. \\hcli (actually <Leader> hcli) will\r\n   begin the highlighting.\r\n3. \\hcls will terminate HiCurLine activity, restoring any previous maps, etc. (actually <Leader>hcls)\r\n   (see :he mapleader for more on how to customize the leading characters of mappings)\r\n\r\n","5":"1. Put into your .vim\/plugin or\r\n   _vimfiles\\plugin directory (Unix\/Windows)\r\n2. \\hcli (actually <Leader> hcli) will\r\n   begin the highlighting.\r\n3. \\hcls will terminate HiCurLine activity, restoring any previous maps, etc. (actually <Leader>hcls)\r\n   (see :he mapleader for more on how to customize the leading characters of mappings)\r\n\r\n","first_name":"Charles","6":"Charles","last_name":"Campbell","7":"Campbell","releases":[{"0":"555","vim_version":"6.0","1":"6.0","script_version":"6","2":"6","version_comment":"* \\hclt and :HCL now toggles [HiCurLine] mode\r\n* Cursorhold\/FocusGained update time now set to 200ms\r\n* go =~ 'm' now used in test to see if menus are to be generated","3":"* \\hclt and :HCL now toggles [HiCurLine] mode\r\n* Cursorhold\/FocusGained update time now set to 200ms\r\n* go =~ 'm' now used in test to see if menus are to be generated","package":"HiCurLine.vim.gz","4":"HiCurLine.vim.gz","src_id":"4795","5":"4795","creation_date":"1132647610","6":"1132647610"},{"0":"555","vim_version":"6.0","1":"6.0","script_version":"5","2":"5","version_comment":"Several small improvements this time: HiCurLine now uses CursorHold to update its highlighting when the colorscheme has been changed.  More motion support: gg and G.  The highlighting group HL_HiCurLine is used, thereby permitting the user to override it.  The g:HL_HiCurLine variable is \"HL_HiCurLine\" by default, but the user may change that (ex. let g:HL_HiCurLine=\"Search\").\r\n","3":"Several small improvements this time: HiCurLine now uses CursorHold to update its highlighting when the colorscheme has been changed.  More motion support: gg and G.  The highlighting group HL_HiCurLine is used, thereby permitting the user to override it.  The g:HL_HiCurLine variable is \"HL_HiCurLine\" by default, but the user may change that (ex. let g:HL_HiCurLine=\"Search\").\r\n","package":"HiCurLine.vim.bz2","4":"HiCurLine.vim.bz2","src_id":"3240","5":"3240","creation_date":"1089960276","6":"1089960276"}]},"554":{"script_id":"554","0":"554","script_name":"mruex","1":"mruex","script_type":"utility","2":"utility","summary":"Explore your most recently used (MRU) files","3":"Explore your most recently used (MRU) files","description":"mruex.vim maintains a list (in a file called mrulist) of your most recently used files. mruex.vim presents an explorer-like interface to mrulist so that you can easily open your MRU files. Duplicates and files that are no longer readable are pruned from mrulist whenever an entry is added to mrulist. If you have several instances of Vim running simultaneously, each update to the mrulist becomes available immediately in all the Vim instances. \r\n\r\nUsage:\r\nA mrulist window is opened by the command :RSplit or <Leader>r where <Leader> is \\ by default. Five commands are available in the mrulist window:\r\nKey         Action:\r\nh              Toggle help\r\nEnter       Open file\r\no              Open file in new window\r\nd              Delete entry (not file)\r\nq              Close mrulist window\r\n\r\nCustomization is done via five Vim variables. mruex_key (default '<Leader>r')\tis the key to open the mrulist window, mruex_win_height (default 6) is the height of the mrulist window, mruex_max_entries (default 20) is the maximum number of MRU file names to keep in mrulist excluding duplicates, mruex_type (default 'w') controls the meaning of most recently used. 'w' indicates: Add file to mrulist whenever it is \twritten (saved) to disk. 'e' indicates: add file to mrulist whenever it is entered, and mruex_filter (default '') is a Vim regular expression defining files to be excluded from the mrulist. mruex_relative =1 or 0 determines  whether or not the file paths in the mrulist are relative to $HOME. \r\nThe default is mruex_relative=1 for unix systems and 0 for others.\r\nExamples:\r\n\tlet mruex_filter='d:\\\\temp\\\\'\r\nin your vimrc excludes files in the d:\\temp\\ directory from the mrulist.\r\n\tlet mruex_key='<f3>'\r\nin your vimrc sets F3 as the key that opens the mrulist window.","4":"mruex.vim maintains a list (in a file called mrulist) of your most recently used files. mruex.vim presents an explorer-like interface to mrulist so that you can easily open your MRU files. Duplicates and files that are no longer readable are pruned from mrulist whenever an entry is added to mrulist. If you have several instances of Vim running simultaneously, each update to the mrulist becomes available immediately in all the Vim instances. \r\n\r\nUsage:\r\nA mrulist window is opened by the command :RSplit or <Leader>r where <Leader> is \\ by default. Five commands are available in the mrulist window:\r\nKey         Action:\r\nh              Toggle help\r\nEnter       Open file\r\no              Open file in new window\r\nd              Delete entry (not file)\r\nq              Close mrulist window\r\n\r\nCustomization is done via five Vim variables. mruex_key (default '<Leader>r')\tis the key to open the mrulist window, mruex_win_height (default 6) is the height of the mrulist window, mruex_max_entries (default 20) is the maximum number of MRU file names to keep in mrulist excluding duplicates, mruex_type (default 'w') controls the meaning of most recently used. 'w' indicates: Add file to mrulist whenever it is \twritten (saved) to disk. 'e' indicates: add file to mrulist whenever it is entered, and mruex_filter (default '') is a Vim regular expression defining files to be excluded from the mrulist. mruex_relative =1 or 0 determines  whether or not the file paths in the mrulist are relative to $HOME. \r\nThe default is mruex_relative=1 for unix systems and 0 for others.\r\nExamples:\r\n\tlet mruex_filter='d:\\\\temp\\\\'\r\nin your vimrc excludes files in the d:\\temp\\ directory from the mrulist.\r\n\tlet mruex_key='<f3>'\r\nin your vimrc sets F3 as the key that opens the mrulist window.","install_details":"Just place this file in $HOME\\vimfiles\\plugin for MSWindows or $HOME\/.vim\/plugin for Unix. The mrulist file will be created in $HOME\\vimfiles or $HOME\/.vim respectively. mruex.vim requires Vim 6.0 (or later) run with \"set nocompatible\" in the vimrc.","5":"Just place this file in $HOME\\vimfiles\\plugin for MSWindows or $HOME\/.vim\/plugin for Unix. The mrulist file will be created in $HOME\\vimfiles or $HOME\/.vim respectively. mruex.vim requires Vim 6.0 (or later) run with \"set nocompatible\" in the vimrc.","first_name":"Ajit","6":"Ajit","last_name":"Thakkar","7":"Thakkar","releases":[{"0":"554","vim_version":"6.0","1":"6.0","script_version":"1.4","2":"1.4","version_comment":"As requested by some MSWindows users, the default behavior has been changed to use full file paths in the mrulist except for Unix systems where file paths are made relative to $HOME. A new global variable, mruex_relative, lets you modify this behavior to suit your needs. ","3":"As requested by some MSWindows users, the default behavior has been changed to use full file paths in the mrulist except for Unix systems where file paths are made relative to $HOME. A new global variable, mruex_relative, lets you modify this behavior to suit your needs. ","package":"mruex.vim","4":"mruex.vim","src_id":"1971","5":"1971","creation_date":"1052286237","6":"1052286237"},{"0":"554","vim_version":"6.0","1":"6.0","script_version":"1.3","2":"1.3","version_comment":"Restore numbered registers after MruUpdate (Ivan Tarasov). Use has(\"patch...\") etc. to automatically include enhancements that depend on patches to vim6.1","3":"Restore numbered registers after MruUpdate (Ivan Tarasov). Use has(\"patch...\") etc. to automatically include enhancements that depend on patches to vim6.1","package":"mruex.vim","4":"mruex.vim","src_id":"1890","5":"1890","creation_date":"1049354484","6":"1049354484"}]},"553":{"script_id":"553","0":"553","script_name":"adp.vim","1":"adp.vim","script_type":"syntax","2":"syntax","summary":"ADP (OpenACS\/AOLserver HTML templating format) syntax highlighting","3":"ADP (OpenACS\/AOLserver HTML templating format) syntax highlighting","description":"Syntax highlighting for ADP (OpenACS\/AOLserver templating format) files.","4":"Syntax highlighting for ADP (OpenACS\/AOLserver templating format) files.","install_details":"Single user setup: Put this file into your ~\/.vim\/syntax directory, and add filetype detection to your ~\/.vim\/filetype.vim file.\r\n\r\nHere's a skeleton filetype.vim, in case you don't have one yet:\r\n\r\n-----\r\n\" filetype detection\r\n\" sourced before $VIMRUNTIME\/filetype.vim\r\n\"\r\n\" Detects: adp\r\n\r\nif exists(\"did_load_filetypes\")\r\n  finish\r\nendif\r\n\r\naugroup filetypedetect\r\n  au! BufRead,BufNewFile *.adp   setfiletype adp\r\naugroup END\r\n-----","5":"Single user setup: Put this file into your ~\/.vim\/syntax directory, and add filetype detection to your ~\/.vim\/filetype.vim file.\r\n\r\nHere's a skeleton filetype.vim, in case you don't have one yet:\r\n\r\n-----\r\n\" filetype detection\r\n\" sourced before $VIMRUNTIME\/filetype.vim\r\n\"\r\n\" Detects: adp\r\n\r\nif exists(\"did_load_filetypes\")\r\n  finish\r\nendif\r\n\r\naugroup filetypedetect\r\n  au! BufRead,BufNewFile *.adp   setfiletype adp\r\naugroup END\r\n-----","first_name":"paul","6":"paul","last_name":"cannon","7":"cannon","releases":[{"0":"553","vim_version":"6.0","1":"6.0","script_version":"0.2","2":"0.2","version_comment":"Initial upload","3":"Initial upload","package":"adp.vim","4":"adp.vim","src_id":"1696","5":"1696","creation_date":"1044457046","6":"1044457046"}]},"552":{"script_id":"552","0":"552","script_name":"coffee.vim","1":"coffee.vim","script_type":"color scheme","2":"color scheme","summary":"a brownish colorscheme","3":"a brownish colorscheme","description":"This is a GUI-only colorscheme. It could also be called: \"cafe au lait\" or \"cafe late\", but I figured that just \"coffee\" is shorter ;-)\r\n\r\nAnyway, I hope you like it.\r\n\r\nNote: it has Unix-style LF, so you may need to convert it to use it under Windows.","4":"This is a GUI-only colorscheme. It could also be called: \"cafe au lait\" or \"cafe late\", but I figured that just \"coffee\" is shorter ;-)\r\n\r\nAnyway, I hope you like it.\r\n\r\nNote: it has Unix-style LF, so you may need to convert it to use it under Windows.","install_details":"Just copy it to $HOME\/.vim\/colors or to $VIMRUNTIME\/colors","5":"Just copy it to $HOME\/.vim\/colors or to $VIMRUNTIME\/colors","first_name":"David","6":"David","last_name":"Lazar","7":"Lazar","releases":[{"0":"552","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"coffee.vim","4":"coffee.vim","src_id":"1687","5":"1687","creation_date":"1044026954","6":"1044026954"}]},"551":{"script_id":"551","0":"551","script_name":"Mines","1":"Mines","script_type":"game","2":"game","summary":"Play Mines with vim","3":"Play Mines with vim","description":"Mines implements the popular game of Mines using Vim, retaining your best scores for each of three levels: Easy, Medium, and Hard.  Mines includes cecutil.vim and Rndm.vim (for screen restoration and for pseudo-random number generation).  The latest developments in Mines.vim will always be available at\r\n\r\n    http:\/\/www.drchip.org\/astronaut\/vim\/index.html#MINES\r\n\r\n    Games:\r\n        \\mfe : play an easy mines game\r\n        \\mfm : play a  medium-difficulty mines game\r\n        \\mfh : play a  high-difficulty mines game\r\n        \\mfr : restore a game\r\n\r\nNote that using the \\mf_ maps above will save the files showing in all windows and save your session.  Although I've used the backslash in the maps as shown here, they actually use <Leader>, so you may customize your maps using mapleader as you wish.\r\n\r\nMines.vim is a use-at-your-own-risk game.  However, an effort has been made to preserve your files.  The game does a \"windo w\" and uses mksession to both save your working files that are showing in your windows and to preserve your window layout for subsequent restoration.\r\n\r\nOn many terminals, all you need to do is to click with the left mouse (to see what's there, or maybe to go BOOM!) or to click with the rightmouse to flag what you think is a mine.\r\n\r\n    More Maps:\r\n\r\n     -Play-\r\n        x   move the cursor around the field;\r\n            pressing x is just like pressing a\r\n            <leftmouse> -- find out what's\r\n            hidden!\r\n\r\n        f   just like the <rightmouse>, flag\r\n            what's under the cursor as a mine\r\n\r\n     -Control-\r\n        s   suspend the game, restore the display\r\n            and session  (\\mfr will subsequently\r\n            restore the game)\r\n\r\n        q   quit the game, restore the display\r\n\r\n     -New Games-\r\n        E   starts up a new easy game \r\n            (only while an old game is showing)\r\n\r\n        M   starts up a new medium game\r\n            (only while an old game is showing)\r\n\r\n        H   starts up a new hard game\r\n            (only while an old game is showing)\r\n\r\nThe objective of the game is to flag all mines and to reveal all safe squares.  As soon as you click a <leftmouse> or x, the square under the cursor is revealed with either a count of the number of bombs around it or as a BOOM.\r\n\r\nIf you win Minnie will do a cartwheel for you!\r\n\r\nSigh -- there appears to be a problem with Sun Solarus dtterms -- Mines highlights several characters with the same foreground and background colors, and this action appears to turn the cursor off on dtterms.  I'm afraid I don't know how to work around this; does anyone know how to turn the cursor back on???\r\n\r\nThank you for rating Mines.vim -- and good luck!\r\n","4":"Mines implements the popular game of Mines using Vim, retaining your best scores for each of three levels: Easy, Medium, and Hard.  Mines includes cecutil.vim and Rndm.vim (for screen restoration and for pseudo-random number generation).  The latest developments in Mines.vim will always be available at\r\n\r\n    http:\/\/www.drchip.org\/astronaut\/vim\/index.html#MINES\r\n\r\n    Games:\r\n        \\mfe : play an easy mines game\r\n        \\mfm : play a  medium-difficulty mines game\r\n        \\mfh : play a  high-difficulty mines game\r\n        \\mfr : restore a game\r\n\r\nNote that using the \\mf_ maps above will save the files showing in all windows and save your session.  Although I've used the backslash in the maps as shown here, they actually use <Leader>, so you may customize your maps using mapleader as you wish.\r\n\r\nMines.vim is a use-at-your-own-risk game.  However, an effort has been made to preserve your files.  The game does a \"windo w\" and uses mksession to both save your working files that are showing in your windows and to preserve your window layout for subsequent restoration.\r\n\r\nOn many terminals, all you need to do is to click with the left mouse (to see what's there, or maybe to go BOOM!) or to click with the rightmouse to flag what you think is a mine.\r\n\r\n    More Maps:\r\n\r\n     -Play-\r\n        x   move the cursor around the field;\r\n            pressing x is just like pressing a\r\n            <leftmouse> -- find out what's\r\n            hidden!\r\n\r\n        f   just like the <rightmouse>, flag\r\n            what's under the cursor as a mine\r\n\r\n     -Control-\r\n        s   suspend the game, restore the display\r\n            and session  (\\mfr will subsequently\r\n            restore the game)\r\n\r\n        q   quit the game, restore the display\r\n\r\n     -New Games-\r\n        E   starts up a new easy game \r\n            (only while an old game is showing)\r\n\r\n        M   starts up a new medium game\r\n            (only while an old game is showing)\r\n\r\n        H   starts up a new hard game\r\n            (only while an old game is showing)\r\n\r\nThe objective of the game is to flag all mines and to reveal all safe squares.  As soon as you click a <leftmouse> or x, the square under the cursor is revealed with either a count of the number of bombs around it or as a BOOM.\r\n\r\nIf you win Minnie will do a cartwheel for you!\r\n\r\nSigh -- there appears to be a problem with Sun Solarus dtterms -- Mines highlights several characters with the same foreground and background colors, and this action appears to turn the cursor off on dtterms.  I'm afraid I don't know how to work around this; does anyone know how to turn the cursor back on???\r\n\r\nThank you for rating Mines.vim -- and good luck!\r\n","install_details":"1. Make sure you have at least v18 of vimball:\r\n   http:\/\/mysite.verizon.net\/astronaut\/vim\/index.html#VIMBALL\r\n   -or-\r\n   vimscript#1502\r\n   (if you have vim 7.1a or later, you probably can skip this step)\r\n\r\n2. vim Mines.vba.gz\r\n   :so %\r\n","5":"1. Make sure you have at least v18 of vimball:\r\n   http:\/\/mysite.verizon.net\/astronaut\/vim\/index.html#VIMBALL\r\n   -or-\r\n   vimscript#1502\r\n   (if you have vim 7.1a or later, you probably can skip this step)\r\n\r\n2. vim Mines.vba.gz\r\n   :so %\r\n","first_name":"Charles","6":"Charles","last_name":"Campbell","7":"Campbell","releases":[{"0":"551","vim_version":"7.0","1":"7.0","script_version":"19","2":"19","version_comment":"* \"nearbyflags\" counter implemented\r\n* bugfix: a \"windo\" is now protected by a noautocmd\r\n* enhancement: uses nnoremaps instead of nmaps","3":"* \"nearbyflags\" counter implemented\r\n* bugfix: a \"windo\" is now protected by a noautocmd\r\n* enhancement: uses nnoremaps instead of nmaps","package":"Mines.vba.gz","4":"Mines.vba.gz","src_id":"19632","5":"19632","creation_date":"1363124674","6":"1363124674"},{"0":"551","vim_version":"7.3","1":"7.3","script_version":"18","2":"18","version_comment":"Autoloading implemented for Mines (quicker vim startup)\r\nBug fix: an errant \"norm\" was changed to \"norm!\"\r\nImprovement: options saved-set-restored using local variants (and noswf, noet)\r\n\r\nHave fun clearing those minefields!  I'm getting about 59.8% wins on \"Easy!\"","3":"Autoloading implemented for Mines (quicker vim startup)\r\nBug fix: an errant \"norm\" was changed to \"norm!\"\r\nImprovement: options saved-set-restored using local variants (and noswf, noet)\r\n\r\nHave fun clearing those minefields!  I'm getting about 59.8% wins on \"Easy!\"","package":"Mines.vba.gz","4":"Mines.vba.gz","src_id":"15177","5":"15177","creation_date":"1299593790","6":"1299593790"},{"0":"551","vim_version":"7.0","1":"7.0","script_version":"17","2":"17","version_comment":"* Pressing \"x\" when atop an \"f\" now is a no-op; one must use an \"f\" to clear an \"f\"\r\n* Attempting to modify a completed minefield no longer produces not-modifiable error messages.\r\n* cecutil bug fix incorporated\r\n* bugfix: works with simple .vimrcs; I usually use (:set ve-all), and the lack of virtualedit was causing problems.\r\n\r\nEnjoy!  On easy mode, I win 51.7% of the time on Easy mode...","3":"* Pressing \"x\" when atop an \"f\" now is a no-op; one must use an \"f\" to clear an \"f\"\r\n* Attempting to modify a completed minefield no longer produces not-modifiable error messages.\r\n* cecutil bug fix incorporated\r\n* bugfix: works with simple .vimrcs; I usually use (:set ve-all), and the lack of virtualedit was causing problems.\r\n\r\nEnjoy!  On easy mode, I win 51.7% of the time on Easy mode...","package":"Mines.vba.gz","4":"Mines.vba.gz","src_id":"11139","5":"11139","creation_date":"1249582494","6":"1249582494"},{"0":"551","vim_version":"6.0","1":"6.0","script_version":"16","2":"16","version_comment":"On wins, percentage won now shown to 3 decimal places.\r\nWorks with Rndm.vim to save seeds in $HOME\/.seed to improve pseudo-random nature of games.\r\n","3":"On wins, percentage won now shown to 3 decimal places.\r\nWorks with Rndm.vim to save seeds in $HOME\/.seed to improve pseudo-random nature of games.\r\n","package":"Mines.vba.gz","4":"Mines.vba.gz","src_id":"6764","5":"6764","creation_date":"1172046133","6":"1172046133"},{"0":"551","vim_version":"6.0","1":"6.0","script_version":"15","2":"15","version_comment":"At end of game due to hitting a mine, empty squares mistakenly flagged as bombs are shown with a blue background\r\nNow includes cecutil to handle saving\/restoring user maps\r\nInsures that it cleans up the -Mines- file\r\nFlickering flood bug fixed\r\n","3":"At end of game due to hitting a mine, empty squares mistakenly flagged as bombs are shown with a blue background\r\nNow includes cecutil to handle saving\/restoring user maps\r\nInsures that it cleans up the -Mines- file\r\nFlickering flood bug fixed\r\n","package":"Mines.vba.gz","4":"Mines.vba.gz","src_id":"6619","5":"6619","creation_date":"1169017886","6":"1169017886"},{"0":"551","vim_version":"7.0","1":"7.0","script_version":"14","2":"14","version_comment":"Added \"Flags Used\" field while playing.\r\nNew commands for speedier play: pressing \"c\" changes corner, pressing 0,$,gg,G changes cursor position but stays inside the minefield.\r\nImproved playability: medium is now 15% mines on an 18x18 grid, hard is 18% mines.\r\n","3":"Added \"Flags Used\" field while playing.\r\nNew commands for speedier play: pressing \"c\" changes corner, pressing 0,$,gg,G changes cursor position but stays inside the minefield.\r\nImproved playability: medium is now 15% mines on an 18x18 grid, hard is 18% mines.\r\n","package":"Mines.vba.gz","4":"Mines.vba.gz","src_id":"5881","5":"5881","creation_date":"1151391771","6":"1151391771"},{"0":"551","vim_version":"6.0","1":"6.0","script_version":"13","2":"13","version_comment":"When you win, Minnie will tell you your winning percentage to the nearest 1\/10 percent.\r\nMines now uses cecutil to save\/restore user maps.\r\n","3":"When you win, Minnie will tell you your winning percentage to the nearest 1\/10 percent.\r\nMines now uses cecutil to save\/restore user maps.\r\n","package":"Mines.tar.gz","4":"Mines.tar.gz","src_id":"4950","5":"4950","creation_date":"1136554768","6":"1136554768"},{"0":"551","vim_version":"6.0","1":"6.0","script_version":"12","2":"12","version_comment":"Mines's winning banner now includes a percentage of wins.\r\nWhen Rndm.vim is missing, Mines will issue a warning about it (and where to get Rndm.vim)\r\nAny players out there?  I've now got a 47% winning rate with Easy mode...\r\n","3":"Mines's winning banner now includes a percentage of wins.\r\nWhen Rndm.vim is missing, Mines will issue a warning about it (and where to get Rndm.vim)\r\nAny players out there?  I've now got a 47% winning rate with Easy mode...\r\n","package":"Mines.vim.gz","4":"Mines.vim.gz","src_id":"4913","5":"4913","creation_date":"1135234662","6":"1135234662"},{"0":"551","vim_version":"6.0","1":"6.0","script_version":"11","2":"11","version_comment":"1: An X will now mark the bomb that went off\r\n2: Flipped the cterm=NONE and fg\/bg specs about; some machines were showing all bold which equated to one color.\r\n3: bugfix: an \"f\" on a previously determined site (whether numbered or blank) will now have no effect\r\n","3":"1: An X will now mark the bomb that went off\r\n2: Flipped the cterm=NONE and fg\/bg specs about; some machines were showing all bold which equated to one color.\r\n3: bugfix: an \"f\" on a previously determined site (whether numbered or blank) will now have no effect\r\n","package":"Mines.vim.bz2","4":"Mines.vim.bz2","src_id":"3394","5":"3394","creation_date":"1093596956","6":"1093596956"},{"0":"551","vim_version":"6.0","1":"6.0","script_version":"10","2":"10","version_comment":"Highlighting is now fixed after a colorscheme change.  The updatetime is now set to 200ms during the game (it gets restored) to facilitate the timing statistics and colorscheme handling.  Statistics are now kept separately for each size, and better streak statistics are kept, too.\r\n","3":"Highlighting is now fixed after a colorscheme change.  The updatetime is now set to 200ms during the game (it gets restored) to facilitate the timing statistics and colorscheme handling.  Statistics are now kept separately for each size, and better streak statistics are kept, too.\r\n","package":"Mines.vim.bz2","4":"Mines.vim.bz2","src_id":"3290","5":"3290","creation_date":"1091179737","6":"1091179737"},{"0":"551","vim_version":"6.0","1":"6.0","script_version":"9","2":"9","version_comment":"For some reason I didn't consider light backgrounds before -- Mines.vim now displays well on light as well as dark backgrounds.  To do so it uses the \"background\" option's setting, which colorschemes normally set (in the colorscheme sampler, only brown bw c dante delek\r\ndon't).","3":"For some reason I didn't consider light backgrounds before -- Mines.vim now displays well on light as well as dark backgrounds.  To do so it uses the \"background\" option's setting, which colorschemes normally set (in the colorscheme sampler, only brown bw c dante delek\r\ndon't).","package":"Mines.vim.bz2","4":"Mines.vim.bz2","src_id":"3188","5":"3188","creation_date":"1088403161","6":"1088403161"}]},"550":{"script_id":"550","0":"550","script_name":"ignore this","1":"ignore this","script_type":"game","2":"game","summary":"ignore this -- uploading error","3":"ignore this -- uploading error","description":"Sorry - there was an uploading error -\r\nplease see\r\n\tvimscript#551\r\nfor Mines!\r\n","4":"Sorry - there was an uploading error -\r\nplease see\r\n\tvimscript#551\r\nfor Mines!\r\n","install_details":"","5":"","first_name":"Charles","6":"Charles","last_name":"Campbell","7":"Campbell","releases":[{"0":"550","vim_version":"6.0","1":"6.0","script_version":"1","2":"1","version_comment":"Initial upload","3":"Initial upload","package":"Mines.vim","4":"Mines.vim","src_id":"1684","5":"1684","creation_date":"1044008888","6":"1044008888"}]},"549":{"script_id":"549","0":"549","script_name":"ignore this","1":"ignore this","script_type":"game","2":"game","summary":"ignore this -- uploading error","3":"ignore this -- uploading error","description":"Sorry - there was an uploading error -\r\nplease see\r\n\tvimscript#551\r\nfor Mines!\r\n","4":"Sorry - there was an uploading error -\r\nplease see\r\n\tvimscript#551\r\nfor Mines!\r\n","install_details":"","5":"","first_name":"Charles","6":"Charles","last_name":"Campbell","7":"Campbell","releases":[{"0":"549","vim_version":"6.0","1":"6.0","script_version":"1","2":"1","version_comment":"Initial upload","3":"Initial upload","package":"Mines.vim","4":"Mines.vim","src_id":"1683","5":"1683","creation_date":"1044008862","6":"1044008862"}]},"548":{"script_id":"548","0":"548","script_name":"ignore this","1":"ignore this","script_type":"game","2":"game","summary":"ignore -- uploading error","3":"ignore -- uploading error","description":"Sorry - there was an uploading error.\r\nPlease see\r\n\tvimscript#551\r\nfor Mines!\r\n","4":"Sorry - there was an uploading error.\r\nPlease see\r\n\tvimscript#551\r\nfor Mines!\r\n","install_details":"","5":"","first_name":"Charles","6":"Charles","last_name":"Campbell","7":"Campbell","releases":[{"0":"548","vim_version":"6.0","1":"6.0","script_version":"1","2":"1","version_comment":"Initial upload","3":"Initial upload","package":"Mines.vim","4":"Mines.vim","src_id":"1682","5":"1682","creation_date":"1044008781","6":"1044008781"}]},"547":{"script_id":"547","0":"547","script_name":"as.vim","1":"as.vim","script_type":"syntax","2":"syntax","summary":"FlashMX ActionScript Syntax File","3":"FlashMX ActionScript Syntax File","description":"Flash MX ActionScript Syntax file","4":"Flash MX ActionScript Syntax file","install_details":"place in $HOME\/.vim\/syntax ","5":"place in $HOME\/.vim\/syntax ","first_name":"Timothy","6":"Timothy","last_name":"Aldrich","7":"Aldrich","releases":[{"0":"547","vim_version":"6.0","1":"6.0","script_version":"0.01","2":"0.01","version_comment":"Initial upload","3":"Initial upload","package":"as.vim","4":"as.vim","src_id":"1681","5":"1681","creation_date":"1043995094","6":"1043995094"}]},"546":{"script_id":"546","0":"546","script_name":"IDL\/ATL Helper","1":"IDL\/ATL Helper","script_type":"ftplugin","2":"ftplugin","summary":"Create\/modify (win32) idl files and ATL projects","3":"Create\/modify (win32) idl files and ATL projects","description":"NB: This is designed for Microsoft idl files.  Suggestions for extending it are welcome.\r\n\r\n* Create idl files - adds guids (using guidgen)\r\n   - Add interfaces,enums (with guids)\r\n   - Coclass wizard to create cpp files for ATL  (some support for comet)\r\n* Easy Method and property creation\r\n   change  \r\n        long MyFunc( string arg1, bool *arg2)\r\n  to\r\n        HRESULT MyFunc( [in] BSTR arg1, [in,out] VARIANT_BOOL *arg2, long *ret);\r\n* Convert IDL functions to their c++ equivalents.\r\n    - Change helpstring() to comments\r\n\r\n* Modify guids quickly!\r\n* add a unique id()  to methods and properties.\r\n\r\n","4":"NB: This is designed for Microsoft idl files.  Suggestions for extending it are welcome.\r\n\r\n* Create idl files - adds guids (using guidgen)\r\n   - Add interfaces,enums (with guids)\r\n   - Coclass wizard to create cpp files for ATL  (some support for comet)\r\n* Easy Method and property creation\r\n   change  \r\n        long MyFunc( string arg1, bool *arg2)\r\n  to\r\n        HRESULT MyFunc( [in] BSTR arg1, [in,out] VARIANT_BOOL *arg2, long *ret);\r\n* Convert IDL functions to their c++ equivalents.\r\n    - Change helpstring() to comments\r\n\r\n* Modify guids quickly!\r\n* add a unique id()  to methods and properties.\r\n\r\n","install_details":"Recommend using buffermenu vimscript #246 for menus\r\nAdd as a filetype plugin for both cpp and idl files.\r\n(Source it from after\/ftplugin\/cpp.vim and after\/ftplugin\/idl.vim)","5":"Recommend using buffermenu vimscript #246 for menus\r\nAdd as a filetype plugin for both cpp and idl files.\r\n(Source it from after\/ftplugin\/cpp.vim and after\/ftplugin\/idl.vim)","first_name":"Michael","6":"Michael","last_name":"Geddes","7":"Geddes","releases":[{"0":"546","vim_version":"6.0","1":"6.0","script_version":"1.5","2":"1.5","version_comment":"Remove dependence on external function GetComment (woops)\r\nFix up some of the ATL functionality (I haven't used them for yonks)\r\nAdd maps for modify Guid, adding library definitions and addling coclasses\r\nRemove absolute dependence on SourceSafe script.","3":"Remove dependence on external function GetComment (woops)\r\nFix up some of the ATL functionality (I haven't used them for yonks)\r\nAdd maps for modify Guid, adding library definitions and addling coclasses\r\nRemove absolute dependence on SourceSafe script.","package":"idl.vim","4":"idl.vim","src_id":"1752","5":"1752","creation_date":"1045609815","6":"1045609815"},{"0":"546","vim_version":"6.0","1":"6.0","script_version":"1.4","2":"1.4","version_comment":"Fixed default MSDEV path.\r\nCleaned up handling of functions\r\nCleaned up handling of id() for 3 part properties.\r\n","3":"Fixed default MSDEV path.\r\nCleaned up handling of functions\r\nCleaned up handling of id() for 3 part properties.\r\n","package":"idl.vim","4":"idl.vim","src_id":"1750","5":"1750","creation_date":"1045585291","6":"1045585291"},{"0":"546","vim_version":"6.0","1":"6.0","script_version":"1.3","2":"1.3","version_comment":"Fixed support for adding [in] [in,out] to parameters (broken in 1.1 & 1.2)\r\n","3":"Fixed support for adding [in] [in,out] to parameters (broken in 1.1 & 1.2)\r\n","package":"idl.vim","4":"idl.vim","src_id":"1692","5":"1692","creation_date":"1044208363","6":"1044208363"},{"0":"546","vim_version":"6.0","1":"6.0","script_version":"1.2","2":"1.2","version_comment":"Fixed up adding of id() attributes.","3":"Fixed up adding of id() attributes.","package":"idl.vim","4":"idl.vim","src_id":"1691","5":"1691","creation_date":"1044202126","6":"1044202126"}]},"545":{"script_id":"545","0":"545","script_name":"ebnf.vim","1":"ebnf.vim","script_type":"syntax","2":"syntax","summary":"Extended BNF (ISO\/IEC 14977) Syntax","3":"Extended BNF (ISO\/IEC 14977) Syntax","description":"Syntax file for EBNF as specified by ISO\/IEC 14977 : 1996(E)\r\n\r\nEBNF is slightly different from most homegrown BNF.  Terminals are always quoted, non-terminals are not (and may contain spaces). Kleene closure is achieved by enclosing with braces, 0-or-1 matches with brackets, 1-or-more matches by appending \"-\" to the end of the braces (i.e. {one non-terminal, second non-terminal}- ). Atoms are separated by \",\" or \"|\". A production rule ends with \";\" or \".\". Comments are (* comment *)\r\n\r\nFor more information on EBNF see http:\/\/www.cl.cam.ac.uk\/~mgk25\/iso-ebnf.html","4":"Syntax file for EBNF as specified by ISO\/IEC 14977 : 1996(E)\r\n\r\nEBNF is slightly different from most homegrown BNF.  Terminals are always quoted, non-terminals are not (and may contain spaces). Kleene closure is achieved by enclosing with braces, 0-or-1 matches with brackets, 1-or-more matches by appending \"-\" to the end of the braces (i.e. {one non-terminal, second non-terminal}- ). Atoms are separated by \",\" or \"|\". A production rule ends with \";\" or \".\". Comments are (* comment *)\r\n\r\nFor more information on EBNF see http:\/\/www.cl.cam.ac.uk\/~mgk25\/iso-ebnf.html","install_details":"Save in $VIMRUNTIME\/syntax\/\r\n:help new-filetype","5":"Save in $VIMRUNTIME\/syntax\/\r\n:help new-filetype","first_name":"Hans","6":"Hans","last_name":"Fugal","7":"Fugal","releases":[{"0":"545","vim_version":"6.0","1":"6.0","script_version":"1.1","2":"1.1","version_comment":"Initial upload","3":"Initial upload","package":"ebnf.vim","4":"ebnf.vim","src_id":"1676","5":"1676","creation_date":"1043737202","6":"1043737202"}]},"544":{"script_id":"544","0":"544","script_name":"flyaccent.vim","1":"flyaccent.vim","script_type":"utility","2":"utility","summary":"Flying accents support","3":"Flying accents support","description":"Flying accent support for vim. When enabled (using :M command) you may type\r\na' (an 'a' letter and an apostrophe) to have an '\u00c3\u00a1' character on screen. It's a bit like dead characters, but you type the accent after the letter, which is much more intuitive in my opinion.\r\n \r\nDisabled by default, may be turned on\/off using the :M command. Currently only Hungarian characters are present, but it's easy to add new ones.\r\n","4":"Flying accent support for vim. When enabled (using :M command) you may type\r\na' (an 'a' letter and an apostrophe) to have an '\u00c3\u00a1' character on screen. It's a bit like dead characters, but you type the accent after the letter, which is much more intuitive in my opinion.\r\n \r\nDisabled by default, may be turned on\/off using the :M command. Currently only Hungarian characters are present, but it's easy to add new ones.\r\n","install_details":"Just put it in the vimfiles\/plugins directory to use it.","5":"Just put it in the vimfiles\/plugins directory to use it.","first_name":"Attila","6":"Attila","last_name":"Tajti","7":"Tajti","releases":[{"0":"544","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"flyaccent.vim","4":"flyaccent.vim","src_id":"1675","5":"1675","creation_date":"1043719122","6":"1043719122"}]},"543":{"script_id":"543","0":"543","script_name":"nuweb.vim","1":"nuweb.vim","script_type":"syntax","2":"syntax","summary":"Syntax highlight for NUWEB (Literate Programming)","3":"Syntax highlight for NUWEB (Literate Programming)","description":"NUWEB aims to provide simple features for Literate Programming with LaTeX and any other language. So implement highlight consist in TeX highlight and other simple general features. My way was to treat Scraps like Verbatim highlight more some nice features, like bold @_ grouping.\n\nIt works rasonable well with the NUWEB Docs.","4":"NUWEB aims to provide simple features for Literate Programming with LaTeX and any other language. So implement highlight consist in TeX highlight and other simple general features. My way was to treat Scraps like Verbatim highlight more some nice features, like bold @_ grouping.\n\nIt works rasonable well with the NUWEB Docs.","install_details":"As WEB\/CWEB uses *.w, i recoment use *.nw for NUWEB, so some like \n'au BufNewFile,BufRead *.nw      setf nuweb'\nin filetype.vim will do the trick.","5":"As WEB\/CWEB uses *.w, i recoment use *.nw for NUWEB, so some like \n'au BufNewFile,BufRead *.nw      setf nuweb'\nin filetype.vim will do the trick.","first_name":"Patricio","6":"Patricio","last_name":"Toledo","7":"Toledo","releases":[{"0":"543","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"nuweb.vim","4":"nuweb.vim","src_id":"1674","5":"1674","creation_date":"1043689444","6":"1043689444"}]},"542":{"script_id":"542","0":"542","script_name":"russian menu translation","1":"russian menu translation","script_type":"utility","2":"utility","summary":"russian menu translation (koi8-r encoding)","3":"russian menu translation (koi8-r encoding)","description":"Russian menu translation for GVIM. \nIncludes some dialog and toolbar captions translation.\n\nAlthough it's koi8-r you may convert it to other russian encoding,\nchange scriptencoding in file and that's it.","4":"Russian menu translation for GVIM. \nIncludes some dialog and toolbar captions translation.\n\nAlthough it's koi8-r you may convert it to other russian encoding,\nchange scriptencoding in file and that's it.","install_details":"Just download the file and put it in your \n~\/.vim\/lang\/ \n  or \n$VIMRUNTIME\/lang\/\n\nIf your system has the correct locale set (ru_RU.KOI8-R) it should work.\nIf not you should \"alias the locale\". For detailed instructions look in\n:help multilang-menus","5":"Just download the file and put it in your \n~\/.vim\/lang\/ \n  or \n$VIMRUNTIME\/lang\/\n\nIf your system has the correct locale set (ru_RU.KOI8-R) it should work.\nIf not you should \"alias the locale\". For detailed instructions look in\n:help multilang-menus","first_name":"Tim","6":"Tim","last_name":"Alexeevsky","7":"Alexeevsky","releases":[{"0":"542","vim_version":"6.0","1":"6.0","script_version":"0.2","2":"0.2","version_comment":"Some fixes in translations and new URL.","3":"Some fixes in translations and new URL.","package":"menu_ru_ru.koi8-r.vim","4":"menu_ru_ru.koi8-r.vim","src_id":"2483","5":"2483","creation_date":"1068518629","6":"1068518629"},{"0":"542","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"menu_ru_ru.koi8-r.vim","4":"menu_ru_ru.koi8-r.vim","src_id":"1668","5":"1668","creation_date":"1043406002","6":"1043406002"}]},"541":{"script_id":"541","0":"541","script_name":"velocity.vim-deprecated","1":"velocity.vim-deprecated","script_type":"syntax","2":"syntax","summary":"Syntax file for velocity templates","3":"Syntax file for velocity templates","description":"velocity.vim adds syntax highlighting for velocity templates, a template engine for Java from the Jakarta Project (http:\/\/jakarta.apache.org\/velocity).","4":"velocity.vim adds syntax highlighting for velocity templates, a template engine for Java from the Jakarta Project (http:\/\/jakarta.apache.org\/velocity).","install_details":"Copy the velocity.vim file into your ~\/.vim\/syntax\/ directory, and add the following to you ~\/.vim\/filetype.vim file, inside the \"augroup filedetect\" block:\r\n\r\nau! BufRead,BufNewFile *.vm  setfiletype velocity\r\n\r\n\r\nFor details about adding syntax highlighting support for new file types, read the help at  |:h mysyntaxfile<CR>| and |:h new-filetype<CR>| .","5":"Copy the velocity.vim file into your ~\/.vim\/syntax\/ directory, and add the following to you ~\/.vim\/filetype.vim file, inside the \"augroup filedetect\" block:\r\n\r\nau! BufRead,BufNewFile *.vm  setfiletype velocity\r\n\r\n\r\nFor details about adding syntax highlighting support for new file types, read the help at  |:h mysyntaxfile<CR>| and |:h new-filetype<CR>| .","first_name":"Antonio","6":"Antonio","last_name":"Terceiro","7":"Terceiro","releases":[{"0":"541","vim_version":"6.0","1":"6.0","script_version":"0.2.1","2":"0.2.1","version_comment":"Fixed the velocity reference syntax highlighting rule. Thanks to Philippe Paravicini <philippe.paravicini@datalex.com>.","3":"Fixed the velocity reference syntax highlighting rule. Thanks to Philippe Paravicini <philippe.paravicini@datalex.com>.","package":"velocity.vim","4":"velocity.vim","src_id":"1839","5":"1839","creation_date":"1048247062","6":"1048247062"},{"0":"541","vim_version":"6.0","1":"6.0","script_version":"0.2","2":"0.2","version_comment":"more complete version, based on the VTL Refernce guide at http:\/\/jakarta.apache.org\/velocity\/vtl-reference-guide.html","3":"more complete version, based on the VTL Refernce guide at http:\/\/jakarta.apache.org\/velocity\/vtl-reference-guide.html","package":"velocity.vim","4":"velocity.vim","src_id":"1695","5":"1695","creation_date":"1044452740","6":"1044452740"},{"0":"541","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"velocity.vim","4":"velocity.vim","src_id":"1665","5":"1665","creation_date":"1043327207","6":"1043327207"}]},"540":{"script_id":"540","0":"540","script_name":"apdl.vim","1":"apdl.vim","script_type":"syntax","2":"syntax","summary":"Syntax highlighting for ANSYS APDL files","3":"Syntax highlighting for ANSYS APDL files","description":"Syntax highlighting for ANSYS APDL files.\r\nNothing fancy, just comment, numbers and function names..","4":"Syntax highlighting for ANSYS APDL files.\r\nNothing fancy, just comment, numbers and function names..","install_details":"","5":"","first_name":"Manfred","6":"Manfred","last_name":"Spraul","7":"Spraul","releases":[{"0":"540","vim_version":"6.0","1":"6.0","script_version":"0.02","2":"0.02","version_comment":"Highlighting added for:\r\n- Invalid parameters for xSEL and CM\r\n- multiline commands\r\n- multiple commands per line","3":"Highlighting added for:\r\n- Invalid parameters for xSEL and CM\r\n- multiline commands\r\n- multiple commands per line","package":"apdl.vim","4":"apdl.vim","src_id":"1670","5":"1670","creation_date":"1043414437","6":"1043414437"},{"0":"540","vim_version":"6.0","1":"6.0","script_version":"0.01","2":"0.01","version_comment":"Initial upload","3":"Initial upload","package":"apdl.vim","4":"apdl.vim","src_id":"1664","5":"1664","creation_date":"1043326139","6":"1043326139"}]},"539":{"script_id":"539","0":"539","script_name":"FavEx","1":"FavEx","script_type":"utility","2":"utility","summary":"Favorite file and directory explorer","3":"Favorite file and directory explorer","description":"favex.vim is a plugin to update a list (favlist) of favorite files and directories, and use the list to provide easy access to the favorites. \r\n\r\nA skeletal favlist is provided. As you edit your favorites, you can add files and their directories to favlist with the :FF and :FD commands or their \\ff and \\fd key map equivalents. Once there are some entries in favlist, you can access your favorites by entering a favex window with either :FE or :FS and then pressing <Enter>, o, or O -- keys entirely analogous to those used in file-explorer. The key mappings, the favex window height, and the favex directory explore command can be customized by setting global variables in your vimrc.\r\n\r\nfavex.vim requires Vim 6.0 (or later) run with at least \"set nocompatible\" in the vimrc, and with the standard file-explorer plugin (or a suitable replacement) loaded.","4":"favex.vim is a plugin to update a list (favlist) of favorite files and directories, and use the list to provide easy access to the favorites. \r\n\r\nA skeletal favlist is provided. As you edit your favorites, you can add files and their directories to favlist with the :FF and :FD commands or their \\ff and \\fd key map equivalents. Once there are some entries in favlist, you can access your favorites by entering a favex window with either :FE or :FS and then pressing <Enter>, o, or O -- keys entirely analogous to those used in file-explorer. The key mappings, the favex window height, and the favex directory explore command can be customized by setting global variables in your vimrc.\r\n\r\nfavex.vim requires Vim 6.0 (or later) run with at least \"set nocompatible\" in the vimrc, and with the standard file-explorer plugin (or a suitable replacement) loaded.","install_details":"1. Unzip favex.zip, preserving directory structure, into either\r\n$HOME\/.vim for unix or $HOME\\vimfiles for MSWindows. \r\n2. Start Vim\r\n3. Do\r\n:helptags ~\/.vim\/doc (for unix)\r\nor\r\n:helptags ~\\vimfiles\\doc (for MSWindows)\r\n4. Do :help favex to learn about usage and customization.","5":"1. Unzip favex.zip, preserving directory structure, into either\r\n$HOME\/.vim for unix or $HOME\\vimfiles for MSWindows. \r\n2. Start Vim\r\n3. Do\r\n:helptags ~\/.vim\/doc (for unix)\r\nor\r\n:helptags ~\\vimfiles\\doc (for MSWindows)\r\n4. Do :help favex to learn about usage and customization.","first_name":"Ajit","6":"Ajit","last_name":"Thakkar","7":"Thakkar","releases":[{"0":"539","vim_version":"6.0","1":"6.0","script_version":"1.1","2":"1.1","version_comment":"Bug fix: Allow for spaces in the run-time path","3":"Bug fix: Allow for spaces in the run-time path","package":"favex11.zip","4":"favex11.zip","src_id":"1744","5":"1744","creation_date":"1045457613","6":"1045457613"}]},"538":{"script_id":"538","0":"538","script_name":"cream-email-munge","1":"cream-email-munge","script_type":"utility","2":"utility","summary":"Munge an email address","3":"Munge an email address","description":"\r\nPosted email addresses are regularly harvested and processed by automated web search tools. These addresses often end up added or sold to bulk email lists so that the unsuspecting address owner receives large quantities of unsolicited email, also known as Spam. \r\n\r\nTo avoid having one's email address harvested in this way, it can be \"munged\", or made unrecognizable to the automated system while still clearly appearing as an email address to any human reader. Examples:\r\n\r\n  unmunged:  \r\n       username@domain.com\r\n\r\n  munged, separator type:\r\n       <username>\u00c2\u00b7<domain>\u00c2\u00b7<com>\r\n       |username|at|domain|dot|com|\r\n\r\n  munged, substitution type:\r\n       useNrnaOme@SdomPainA.coMm (remove \"NOSPAM\" to email)\r\n       useSrnPamAe@MdoFmaRinE.cEom (remove \"SPAMFREE\" to email)\r\n\r\n  munged, completion type:\r\n       usernam____n.com (insert \"e@domai\" to email)\r\n\r\nThis script provides a visual mode mapping Shift+F12 which will munge any selected email address randomly per one of the examples above. The main function \"Cream_email_munge()\" will also return a munged address if passed a valid email, like:\r\n\r\n  let mymunge = Cream_email_munge(\"username@domain.com\")\r\n\r\n\r\nThis is one of many custom utilities and functions for gVim from the Cream project (http:\/\/cream.sourceforge.net), a configuration of Vim for those of us familiar with Apple and Windows software.\r\n\r\n","4":"\r\nPosted email addresses are regularly harvested and processed by automated web search tools. These addresses often end up added or sold to bulk email lists so that the unsuspecting address owner receives large quantities of unsolicited email, also known as Spam. \r\n\r\nTo avoid having one's email address harvested in this way, it can be \"munged\", or made unrecognizable to the automated system while still clearly appearing as an email address to any human reader. Examples:\r\n\r\n  unmunged:  \r\n       username@domain.com\r\n\r\n  munged, separator type:\r\n       <username>\u00c2\u00b7<domain>\u00c2\u00b7<com>\r\n       |username|at|domain|dot|com|\r\n\r\n  munged, substitution type:\r\n       useNrnaOme@SdomPainA.coMm (remove \"NOSPAM\" to email)\r\n       useSrnPamAe@MdoFmaRinE.cEom (remove \"SPAMFREE\" to email)\r\n\r\n  munged, completion type:\r\n       usernam____n.com (insert \"e@domai\" to email)\r\n\r\nThis script provides a visual mode mapping Shift+F12 which will munge any selected email address randomly per one of the examples above. The main function \"Cream_email_munge()\" will also return a munged address if passed a valid email, like:\r\n\r\n  let mymunge = Cream_email_munge(\"username@domain.com\")\r\n\r\n\r\nThis is one of many custom utilities and functions for gVim from the Cream project (http:\/\/cream.sourceforge.net), a configuration of Vim for those of us familiar with Apple and Windows software.\r\n\r\n","install_details":"\r\nDrop this file into your plugins directory and (re)start Vim.\r\n\r\n","5":"\r\nDrop this file into your plugins directory and (re)start Vim.\r\n\r\n","first_name":"Steve","6":"Steve","last_name":"Hall","7":"Hall","releases":[{"0":"538","vim_version":"6.0","1":"6.0","script_version":"0.2a","2":"0.2a","version_comment":"Fixed omission of <CR> at mapping end, sorry.","3":"Fixed omission of <CR> at mapping end, sorry.","package":"cream-email-munge.vim","4":"cream-email-munge.vim","src_id":"1661","5":"1661","creation_date":"1043270492","6":"1043270492"},{"0":"538","vim_version":"6.0","1":"6.0","script_version":"0.2","2":"0.2","version_comment":"Added both substitution type munging [useNrnaOme@SdomPainA.coMm (remove \"NOSPAM\" to email)] and completion type munging [usernam____n.com (insert \"e@domai\" to email)].\r\n\r\n","3":"Added both substitution type munging [useNrnaOme@SdomPainA.coMm (remove \"NOSPAM\" to email)] and completion type munging [usernam____n.com (insert \"e@domai\" to email)].\r\n\r\n","package":"cream-email-munge.vim","4":"cream-email-munge.vim","src_id":"1660","5":"1660","creation_date":"1043252181","6":"1043252181"},{"0":"538","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"cream-email-munge.vim","4":"cream-email-munge.vim","src_id":"1658","5":"1658","creation_date":"1043183650","6":"1043183650"}]},"537":{"script_id":"537","0":"537","script_name":"tab-syntax","1":"tab-syntax","script_type":"syntax","2":"syntax","summary":"syntax for guitar tabulatures","3":"syntax for guitar tabulatures","description":"a syntax for guitar tabulatures in format found in OLGA archives and usenet postings and generated by PowerTabEditor.\r\nWARNING: sometimes it hangs vim trying to match end of tabulature line.\r\n\r\n\r\n","4":"a syntax for guitar tabulatures in format found in OLGA archives and usenet postings and generated by PowerTabEditor.\r\nWARNING: sometimes it hangs vim trying to match end of tabulature line.\r\n\r\n\r\n","install_details":"put in ~\/.vim\/syntax\/ \r\nand define autocmd BufRead *.tab set filetype=tab","5":"put in ~\/.vim\/syntax\/ \r\nand define autocmd BufRead *.tab set filetype=tab","first_name":"Max","6":"Max","last_name":"Wasiliev","7":"Wasiliev","releases":[{"0":"537","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"tab.vim","4":"tab.vim","src_id":"1656","5":"1656","creation_date":"1043150763","6":"1043150763"}]},"536":{"script_id":"536","0":"536","script_name":"tiger.vim","1":"tiger.vim","script_type":"syntax","2":"syntax","summary":"Tiger Vim Syntax File","3":"Tiger Vim Syntax File","description":"Tiger is a language introduced by andrew Appel in his book(s) \"Modern Compiler Implementation in {ML,C,Java}.\" \r\nFor further information, go to : \"www.cs.princeton.edu\/~appel\/modern\"\r\n\r\nThis file gives you a \"correct\" syntax hightlighting when working on Tiger files.\r\nIt is to be used with the associated indentation file.\r\n\r\nLook at this screenshot to see which coding style is actually \"supported\" :\r\n\"http:\/\/www.xbsd.org\/~flz\/pics\/shot-tiger.jpg\"","4":"Tiger is a language introduced by andrew Appel in his book(s) \"Modern Compiler Implementation in {ML,C,Java}.\" \r\nFor further information, go to : \"www.cs.princeton.edu\/~appel\/modern\"\r\n\r\nThis file gives you a \"correct\" syntax hightlighting when working on Tiger files.\r\nIt is to be used with the associated indentation file.\r\n\r\nLook at this screenshot to see which coding style is actually \"supported\" :\r\n\"http:\/\/www.xbsd.org\/~flz\/pics\/shot-tiger.jpg\"","install_details":"Just source the file when opening a *.tig file.\r\nCreate an autocmd like this one :\r\nau BufNewFile,BufRead *.tig so ~\/.vim\/syntax\/tiger.vim","5":"Just source the file when opening a *.tig file.\r\nCreate an autocmd like this one :\r\nau BufNewFile,BufRead *.tig so ~\/.vim\/syntax\/tiger.vim","first_name":"Florent","6":"Florent","last_name":"Thoumie","7":"Thoumie","releases":[{"0":"536","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"tiger.vim","4":"tiger.vim","src_id":"1649","5":"1649","creation_date":"1042971725","6":"1042971725"}]},"535":{"script_id":"535","0":"535","script_name":"tiger.vim","1":"tiger.vim","script_type":"indent","2":"indent","summary":"Tiger Vim Indent File","3":"Tiger Vim Indent File","description":"Tiger is a language introduced by andrew Appel in his book(s) \"Modern Compiler Implementation in {ML,C,Java}.\" \r\nFor further information, go to : \"www.cs.princeton.edu\/~appel\/modern\"\r\n\r\nThis file gives you a \"correct\" indentation when working on Tiger files.\r\nIt is to be used with the associated syntax file.\r\n\r\nLook at this screenshot to see which coding style is actually \"supported\" :\r\n\"http:\/\/www.xbsd.org\/~flz\/pics\/shot-tiger.jpg\"","4":"Tiger is a language introduced by andrew Appel in his book(s) \"Modern Compiler Implementation in {ML,C,Java}.\" \r\nFor further information, go to : \"www.cs.princeton.edu\/~appel\/modern\"\r\n\r\nThis file gives you a \"correct\" indentation when working on Tiger files.\r\nIt is to be used with the associated syntax file.\r\n\r\nLook at this screenshot to see which coding style is actually \"supported\" :\r\n\"http:\/\/www.xbsd.org\/~flz\/pics\/shot-tiger.jpg\"","install_details":"Just source the file when opening a *.tig file.\r\nCreate an autocmd like this one :\r\nau BufNewFile,BufRead *.tig so ~\/.vim\/indent\/tiger.vim","5":"Just source the file when opening a *.tig file.\r\nCreate an autocmd like this one :\r\nau BufNewFile,BufRead *.tig so ~\/.vim\/indent\/tiger.vim","first_name":"Florent","6":"Florent","last_name":"Thoumie","7":"Thoumie","releases":[{"0":"535","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"tiger.vim","4":"tiger.vim","src_id":"1648","5":"1648","creation_date":"1042971638","6":"1042971638"}]},"534":{"script_id":"534","0":"534","script_name":"PHP-dictionary","1":"PHP-dictionary","script_type":"utility","2":"utility","summary":"A PHP-dictionary as a building stone for scripts","3":"A PHP-dictionary as a building stone for scripts","description":"PHP dictionary\r\n\r\nThis is not a script, but a building stone for a script.\r\nAlthough of minor significance, it may be useful to someone.\r\n\r\nLearn about the use of dictionaries in general and you will - as a PHP programer - be able to use this.","4":"PHP dictionary\r\n\r\nThis is not a script, but a building stone for a script.\r\nAlthough of minor significance, it may be useful to someone.\r\n\r\nLearn about the use of dictionaries in general and you will - as a PHP programer - be able to use this.","install_details":"","5":"","first_name":"Klaus","6":"Klaus","last_name":"Horsten","7":"Horsten","releases":[{"0":"534","vim_version":"6.0","1":"6.0","script_version":"0.2","2":"0.2","version_comment":"I merged my dictionary with the dictionaries of Leszek Krupinski, removed all duplicates ... So all available php-dictionaries should now be in this one.","3":"I merged my dictionary with the dictionaries of Leszek Krupinski, removed all duplicates ... So all available php-dictionaries should now be in this one.","package":"PHP.dict","4":"PHP.dict","src_id":"2367","5":"2367","creation_date":"1065089559","6":"1065089559"},{"0":"534","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"PHP.dict","4":"PHP.dict","src_id":"1647","5":"1647","creation_date":"1042941691","6":"1042941691"}]},"533":{"script_id":"533","0":"533","script_name":"ntservices","1":"ntservices","script_type":"utility","2":"utility","summary":"Control NT services from Vim.","3":"Control NT services from Vim.","description":"PLEASE READ THE INSTALL SECTION COMPLETELY.\r\n\r\n- This plugin generates a list of NT services that are installed on the\r\n  local NT\/W2K\/XP machine with the current started status. You can\r\n  start\/stop the service by pressing S or pause\/continue the service by\r\n  pressing P on the corresponding entry.\r\n- You can open the servicelist window through WinManager (as described in\r\n  the installation section below) or by assigning a hot key. You can use\r\n  the same hot key to open\/close the window. Alternatively, you can also\r\n  use the :NTServices command to open\/close the services window.\r\n- You can choose which fields that you want to see by using the\r\n  NtsFields command. You can select the sort fields by pressing s\r\n  consecutively and r for reversing the sort direction.\r\n- If you have permissions, you can view the service list in a remote m\/c\r\n  by using the NtsSetHost command. With no arguments, it prints the\r\n  current remote host name. To switch back to the local m\/c, use \".\" for\r\n  the host name.\r\n- For the sake of speed, the list of services is cached. To see the latest\r\n  set of services and their states at any time, refresh the window by\r\n  pressing 'R'.\r\n- It requires multvals and genutils plugins to be always installed, but\r\n  others are required only depending on your usage\/setting (for a better\r\n  experience and formatting).\r\n\r\nSearch_key_words: NT services ntservices ntservice service multvals genutils align Hari Krishna Dara","4":"PLEASE READ THE INSTALL SECTION COMPLETELY.\r\n\r\n- This plugin generates a list of NT services that are installed on the\r\n  local NT\/W2K\/XP machine with the current started status. You can\r\n  start\/stop the service by pressing S or pause\/continue the service by\r\n  pressing P on the corresponding entry.\r\n- You can open the servicelist window through WinManager (as described in\r\n  the installation section below) or by assigning a hot key. You can use\r\n  the same hot key to open\/close the window. Alternatively, you can also\r\n  use the :NTServices command to open\/close the services window.\r\n- You can choose which fields that you want to see by using the\r\n  NtsFields command. You can select the sort fields by pressing s\r\n  consecutively and r for reversing the sort direction.\r\n- If you have permissions, you can view the service list in a remote m\/c\r\n  by using the NtsSetHost command. With no arguments, it prints the\r\n  current remote host name. To switch back to the local m\/c, use \".\" for\r\n  the host name.\r\n- For the sake of speed, the list of services is cached. To see the latest\r\n  set of services and their states at any time, refresh the window by\r\n  pressing 'R'.\r\n- It requires multvals and genutils plugins to be always installed, but\r\n  others are required only depending on your usage\/setting (for a better\r\n  experience and formatting).\r\n\r\nSearch_key_words: NT services ntservices ntservice service multvals genutils align Hari Krishna Dara","install_details":"- Place the plugin in a plugin diretory under runtimepath and configure\r\n  WinManager according to your taste. E.g:\r\n                                                                           \r\n    let g:winManagerWindowLayout = 'FileExplorer,NTServices'\r\n                                                                           \r\n  You can then switch between FileExplorer and NTServices by pressing ^N\r\n  and ^P.\r\n- If you don't want to use WinManager, you can still use the :NTServices\r\n  comamnd or assign a hotkey by placing the following in your vimrc:\r\n                                                                           \r\n    nmap <silent> <F5> <Plug>NTServices\r\n                                                                           \r\n  You can substitute any key or sequnce of keys for <F5> in the above map.\r\n- Requires multvals.vim to be installed. Download from:\r\n    http:\/\/www.vim.org\/script.php?script_id=171\r\n- Requires genutils.vim to be installed. Download from:\r\n    http:\/\/www.vim.org\/script.php?script_id=197\r\n- If Align.vim is installed, it is used to format the output.\r\n- Requires cscript.exe and net.exe to be in the path.\r\n- Use g:ntservFields, g:ntservSortFieldIndex, g:ntservSortDirection to\r\n  specify field names, default sort field and the sort direction\r\n  respectively. Use NtsFields command to see the list of field names\r\n  possible.\r\n","5":"- Place the plugin in a plugin diretory under runtimepath and configure\r\n  WinManager according to your taste. E.g:\r\n                                                                           \r\n    let g:winManagerWindowLayout = 'FileExplorer,NTServices'\r\n                                                                           \r\n  You can then switch between FileExplorer and NTServices by pressing ^N\r\n  and ^P.\r\n- If you don't want to use WinManager, you can still use the :NTServices\r\n  comamnd or assign a hotkey by placing the following in your vimrc:\r\n                                                                           \r\n    nmap <silent> <F5> <Plug>NTServices\r\n                                                                           \r\n  You can substitute any key or sequnce of keys for <F5> in the above map.\r\n- Requires multvals.vim to be installed. Download from:\r\n    http:\/\/www.vim.org\/script.php?script_id=171\r\n- Requires genutils.vim to be installed. Download from:\r\n    http:\/\/www.vim.org\/script.php?script_id=197\r\n- If Align.vim is installed, it is used to format the output.\r\n- Requires cscript.exe and net.exe to be in the path.\r\n- Use g:ntservFields, g:ntservSortFieldIndex, g:ntservSortDirection to\r\n  specify field names, default sort field and the sort direction\r\n  respectively. Use NtsFields command to see the list of field names\r\n  possible.\r\n","first_name":"Hari Krishna","6":"Hari Krishna","last_name":"Dara","7":"Dara","releases":[{"0":"533","vim_version":"6.0","1":"6.0","script_version":"1.7","2":"1.7","version_comment":"Maintenance release. Fixed broken NTSsetHost command.\r\n","3":"Maintenance release. Fixed broken NTSsetHost command.\r\n","package":"ntservices.vim","4":"ntservices.vim","src_id":"3266","5":"3266","creation_date":"1090607499","6":"1090607499"},{"0":"533","vim_version":"6.0","1":"6.0","script_version":"1.6","2":"1.6","version_comment":"Minor updates:\r\n- Fixed the bug in connecting to a remote host, basically it wasn't working.\r\n- NtsSetHost is now global, so you don't have to open the window before\r\n  switching to a remote host.\r\n- Check and not load if it is not windows (David Fishburn).\r\n","3":"Minor updates:\r\n- Fixed the bug in connecting to a remote host, basically it wasn't working.\r\n- NtsSetHost is now global, so you don't have to open the window before\r\n  switching to a remote host.\r\n- Check and not load if it is not windows (David Fishburn).\r\n","package":"ntservices.vim","4":"ntservices.vim","src_id":"2683","5":"2683","creation_date":"1075229535","6":"1075229535"},{"0":"533","vim_version":"6.0","1":"6.0","script_version":"1.5","2":"1.5","version_comment":"- Renamed NTsFields command to NtsFields. \r\n- Now genutils.vim plugin is required. Download it from http:\/\/www.vim.org\/script.php?script_id=197 \r\n- Fixed a bug with buffer name on solaris. \r\n- New feature to connect to a remote host. \r\n- q to quit window. \r\n- Version dependency check on multvals and genutils plugin. You now get an error message during the Vim startup, if you don't have minimum required versions of these two dependent plugins. \r\n","3":"- Renamed NTsFields command to NtsFields. \r\n- Now genutils.vim plugin is required. Download it from http:\/\/www.vim.org\/script.php?script_id=197 \r\n- Fixed a bug with buffer name on solaris. \r\n- New feature to connect to a remote host. \r\n- q to quit window. \r\n- Version dependency check on multvals and genutils plugin. You now get an error message during the Vim startup, if you don't have minimum required versions of these two dependent plugins. \r\n","package":"ntservices.vim","4":"ntservices.vim","src_id":"2682","5":"2682","creation_date":"1075229490","6":"1075229490"},{"0":"533","vim_version":"6.0","1":"6.0","script_version":"1.4","2":"1.4","version_comment":"You can select the list of fields that you want to see in the services list. You can specify the field list in your vimrc, but you can always dynamically change them using NTservFields command at runtime. This new feature adds a new dependency on multvals plugin, but others are still optional.","3":"You can select the list of fields that you want to see in the services list. You can specify the field list in your vimrc, but you can always dynamically change them using NTservFields command at runtime. This new feature adds a new dependency on multvals plugin, but others are still optional.","package":"ntservices.vim","4":"ntservices.vim","src_id":"1732","5":"1732","creation_date":"1045246138","6":"1045246138"},{"0":"533","vim_version":"6.0","1":"6.0","script_version":"1.2","2":"1.2","version_comment":"With the help of David Fishburn, I was able to identify a problem and fix it. I also added a command and <Plug> mapping to activate the window without needing WinManager at all (for those who don't want to install WinManager). Thanks a lot to David for debugging the problem and providing help in other ways too.","3":"With the help of David Fishburn, I was able to identify a problem and fix it. I also added a command and <Plug> mapping to activate the window without needing WinManager at all (for those who don't want to install WinManager). Thanks a lot to David for debugging the problem and providing help in other ways too.","package":"ntservices.vim","4":"ntservices.vim","src_id":"1654","5":"1654","creation_date":"1043089739","6":"1043089739"},{"0":"533","vim_version":"6.0","1":"6.0","script_version":"1.1","2":"1.1","version_comment":"Cscript wasn't executing vbscripts on some machines unless the \/\/E:vbscript option is passed. If it still doesn't work for you, please do me a favour by running cscript manually on the temp file created with the .vbs extension in the temp directory like this:\r\n\r\ncscript \/\/E:vbscript \/\/Nologo <temp file created by plugin>\r\n\r\nand please report the error that you see. Thank you.","3":"Cscript wasn't executing vbscripts on some machines unless the \/\/E:vbscript option is passed. If it still doesn't work for you, please do me a favour by running cscript manually on the temp file created with the .vbs extension in the temp directory like this:\r\n\r\ncscript \/\/E:vbscript \/\/Nologo <temp file created by plugin>\r\n\r\nand please report the error that you see. Thank you.","package":"ntservices.vim","4":"ntservices.vim","src_id":"1644","5":"1644","creation_date":"1042893539","6":"1042893539"},{"0":"533","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"ntservices.vim","4":"ntservices.vim","src_id":"1642","5":"1642","creation_date":"1042826827","6":"1042826827"}]},"532":{"script_id":"532","0":"532","script_name":"colorer color scheme","1":"colorer color scheme","script_type":"color scheme","2":"color scheme","summary":"colorer color scheme","3":"colorer color scheme","description":"My favorite dark color scheme. Very colorful :) \r\n\r\nHere\\'s a screenshot: http:\/\/interdon.net\/~shaman\/vim\/vim-colorer.png\r\n\r\nI hope you like it! ","4":"My favorite dark color scheme. Very colorful :) \r\n\r\nHere\\'s a screenshot: http:\/\/interdon.net\/~shaman\/vim\/vim-colorer.png\r\n\r\nI hope you like it! ","install_details":"Just put in your ~\/.vim\/colors\/ directory and type \":color colorer\".","5":"Just put in your ~\/.vim\/colors\/ directory and type \":color colorer\".","first_name":"Sergey","6":"Sergey","last_name":"Beduev","7":"Beduev","releases":[{"0":"532","vim_version":"6.0","1":"6.0","script_version":"1.1","2":"1.1","version_comment":"remove bold in gui version","3":"remove bold in gui version","package":"colorer.vim","4":"colorer.vim","src_id":"2882","5":"2882","creation_date":"1080441909","6":"1080441909"},{"0":"532","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"colorer.vim","4":"colorer.vim","src_id":"1639","5":"1639","creation_date":"1042757496","6":"1042757496"}]},"531":{"script_id":"531","0":"531","script_name":"elvis c highlighting","1":"elvis c highlighting","script_type":"color scheme","2":"color scheme","summary":"Highlights C syntax like the elvis vi clone","3":"Highlights C syntax like the elvis vi clone","description":"UPDATE:  Forgot to set the String and Number options to NONE.  Have updated the script to do so.  \r\n\r\nI don't like a lot of colors.  I like how elvis highlights.  However, vim has a lot more to offer.  So this script highlights just like elvis does.  It uses white to highlight types statements and such...  It uses nothing for Normal.  If you're using Eterm, please uncomment the line to set Normal to grey since Eterm tends to have a brighter than usual Normal text.   Xterm, however, uses a lighter white so the vim \"white\" is good for highlighting.\r\n\r\nThis scheme is easy on the eyes and a bit more professional.  If you don't like a lot of colors, this one will suit you fine.\r\n","4":"UPDATE:  Forgot to set the String and Number options to NONE.  Have updated the script to do so.  \r\n\r\nI don't like a lot of colors.  I like how elvis highlights.  However, vim has a lot more to offer.  So this script highlights just like elvis does.  It uses white to highlight types statements and such...  It uses nothing for Normal.  If you're using Eterm, please uncomment the line to set Normal to grey since Eterm tends to have a brighter than usual Normal text.   Xterm, however, uses a lighter white so the vim \"white\" is good for highlighting.\r\n\r\nThis scheme is easy on the eyes and a bit more professional.  If you don't like a lot of colors, this one will suit you fine.\r\n","install_details":"Use this with the c.vim that comes with vim 6.0.   Just put this file in your ~\/.vim\/syntax directory and it will use the regex stuff that the default c.vim has, but override the color options.\r\n\r\n","5":"Use this with the c.vim that comes with vim 6.0.   Just put this file in your ~\/.vim\/syntax directory and it will use the regex stuff that the default c.vim has, but override the color options.\r\n\r\n","first_name":"Joe","6":"Joe","last_name":"Schmoe","7":"Schmoe","releases":[{"0":"531","vim_version":"6.0","1":"6.0","script_version":"1.3","2":"1.3","version_comment":"Oops!  Forgot to upload the correct script in the last version.  Sorry...","3":"Oops!  Forgot to upload the correct script in the last version.  Sorry...","package":"c.vim","4":"c.vim","src_id":"1653","5":"1653","creation_date":"1043050490","6":"1043050490"},{"0":"531","vim_version":"6.0","1":"6.0","script_version":"1.2","2":"1.2","version_comment":"set String and Number options to NONE.  ","3":"set String and Number options to NONE.  ","package":"c.vim","4":"c.vim","src_id":"1651","5":"1651","creation_date":"1043005897","6":"1043005897"}]},"530":{"script_id":"530","0":"530","script_name":"Mixed source\/assembly syntax (objdump)","1":"Mixed source\/assembly syntax (objdump)","script_type":"syntax","2":"syntax","summary":"Syntax for Mixed C source and assembly dump.","3":"Syntax for Mixed C source and assembly dump.","description":"This is a syntax file for mixed C source and assembly dump, disassembled by gnu \"objdump\" utility. It does not recognize processor instructions so, it can be used on any platform. Here are the commands to generate the mixed disassembly. Make sure the source file is in the same directory as the object file.\r\ngcc -g -c xxx.c                       \/*output is xxx.o*\/\r\nobjdump -S xxx.o > xxx.dis  \/* creates disassembly mixed with source *\/\r\n","4":"This is a syntax file for mixed C source and assembly dump, disassembled by gnu \"objdump\" utility. It does not recognize processor instructions so, it can be used on any platform. Here are the commands to generate the mixed disassembly. Make sure the source file is in the same directory as the object file.\r\ngcc -g -c xxx.c                       \/*output is xxx.o*\/\r\nobjdump -S xxx.o > xxx.dis  \/* creates disassembly mixed with source *\/\r\n","install_details":"First copy the  syntax file to your $VIM\/syntax folder. \r\n\r\nThen,\r\nIn version 7.x \r\n------------------\r\nIn your $VIM\/ftdetect folder\r\ncreate a file named cmix.vim and add   \r\n      autocmd BufRead,BufNewFile *.dis set filetype=cmix\r\n\r\n\r\nIn older versions:\r\n-----------------------\r\n1.Create a file \"myfiletypes.vim\" in your $VIM directory with the following\r\n\" myfiletypefile\r\n    augroup filetype\r\n        au! BufRead,BufNewFile *.dis\tset filetype=mixed\r\n    augroup END\r\n\r\n2.Create another file in the same directory named \"mysyntax.vim\" with\r\n\r\nau! Syntax mixed  so $vim\\syntax\\cmix.vim\r\n\" path shown above should be the directory you saved the syntax file in.\r\n\" change the direction of the slash for *nix platforms\r\n","5":"First copy the  syntax file to your $VIM\/syntax folder. \r\n\r\nThen,\r\nIn version 7.x \r\n------------------\r\nIn your $VIM\/ftdetect folder\r\ncreate a file named cmix.vim and add   \r\n      autocmd BufRead,BufNewFile *.dis set filetype=cmix\r\n\r\n\r\nIn older versions:\r\n-----------------------\r\n1.Create a file \"myfiletypes.vim\" in your $VIM directory with the following\r\n\" myfiletypefile\r\n    augroup filetype\r\n        au! BufRead,BufNewFile *.dis\tset filetype=mixed\r\n    augroup END\r\n\r\n2.Create another file in the same directory named \"mysyntax.vim\" with\r\n\r\nau! Syntax mixed  so $vim\\syntax\\cmix.vim\r\n\" path shown above should be the directory you saved the syntax file in.\r\n\" change the direction of the slash for *nix platforms\r\n","first_name":"Vihar","6":"Vihar","last_name":"Rai","7":"Rai","releases":[{"0":"530","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"cmix.vim","4":"cmix.vim","src_id":"1635","5":"1635","creation_date":"1042655893","6":"1042655893"}]},"529":{"script_id":"529","0":"529","script_name":"blockquote.vim","1":"blockquote.vim","script_type":"utility","2":"utility","summary":"insert block quotes like emacs blockquote.el","3":"insert block quotes like emacs blockquote.el","description":"Example:\r\n,----[ title ]-\r\n| some text\r\n`----\r\n\r\nWithout title:\r\n,----\r\n| some text\r\n`----\r\n\r\nUsage:\r\n  Blockquote a range (default: current line)\r\n  :<range>Bq [title]\r\n  Blockquote a file\r\n  :Bqf {filename}\r\n  Blockquote a file, starting at line {start}\r\n  :Bqf {filename} {start}\r\n  Blockquote a file, starting at line {start} and ending at {end}\r\n  :Bqf {filename} {start} {end}\r\n  Remove a blockquote, starting at <range> (default: current line)\r\n  :<range>UBq\r\n","4":"Example:\r\n,----[ title ]-\r\n| some text\r\n`----\r\n\r\nWithout title:\r\n,----\r\n| some text\r\n`----\r\n\r\nUsage:\r\n  Blockquote a range (default: current line)\r\n  :<range>Bq [title]\r\n  Blockquote a file\r\n  :Bqf {filename}\r\n  Blockquote a file, starting at line {start}\r\n  :Bqf {filename} {start}\r\n  Blockquote a file, starting at line {start} and ending at {end}\r\n  :Bqf {filename} {start} {end}\r\n  Remove a blockquote, starting at <range> (default: current line)\r\n  :<range>UBq\r\n","install_details":"Source from your .vimrc\r\n","5":"Source from your .vimrc\r\n","first_name":"Andreas","6":"Andreas","last_name":"Ferber","7":"Ferber","releases":[{"0":"529","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"blockquote.vim","4":"blockquote.vim","src_id":"1633","5":"1633","creation_date":"1042544055","6":"1042544055"}]},"528":{"script_id":"528","0":"528","script_name":"mh","1":"mh","script_type":"utility","2":"utility","summary":"display MSDN help.","3":"display MSDN help.","description":"display MSDN help in GVIM.","4":"display MSDN help in GVIM.","install_details":" usage\r\n 1. copy mh.exe to PATH directory\r\n 2. insert to _vimrc\r\n\tcom  -nargs=1 H !start mh <args>\r\n\tmap K :!start mh <cword> <CR> \r\n 3. run mh.exe and click \\'File\\' button.\r\n 4. select MSDN html help file\r\n ex)\r\n  Visual C++ 6.0: msdnvs98.col\r\n  MSDN: msdn120.col \r\n  eMbedded Visual C++ 4.0: EVC4HELP.CHM\r\n  Platform Builder 4.1: wcelib40.chm\r\n\r\n press K under the keyword. \r\n or\r\n :h keyword \r\n mh.exe will display the keyword DOCUMENT.\r\n\r\n mh.exe is not support .Net MSDN.","5":" usage\r\n 1. copy mh.exe to PATH directory\r\n 2. insert to _vimrc\r\n\tcom  -nargs=1 H !start mh <args>\r\n\tmap K :!start mh <cword> <CR> \r\n 3. run mh.exe and click \\'File\\' button.\r\n 4. select MSDN html help file\r\n ex)\r\n  Visual C++ 6.0: msdnvs98.col\r\n  MSDN: msdn120.col \r\n  eMbedded Visual C++ 4.0: EVC4HELP.CHM\r\n  Platform Builder 4.1: wcelib40.chm\r\n\r\n press K under the keyword. \r\n or\r\n :h keyword \r\n mh.exe will display the keyword DOCUMENT.\r\n\r\n mh.exe is not support .Net MSDN.","first_name":"donghyuk","6":"donghyuk","last_name":"kim","7":"kim","releases":[{"0":"528","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"click '?' button","3":"click '?' button","package":"MH.exe","4":"MH.exe","src_id":"1631","5":"1631","creation_date":"1042504060","6":"1042504060"},{"0":"528","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"MH.exe","4":"MH.exe","src_id":"1629","5":"1629","creation_date":"1042486587","6":"1042486587"}]},"527":{"script_id":"527","0":"527","script_name":"cppcomplete","1":"cppcomplete","script_type":"utility","2":"utility","summary":"C\/C++ and Java code completion","3":"C\/C++ and Java code completion","description":"This plugin helps you complete things like:\r\nvariableName.abc\r\nvariableName->abc\r\ntypeName::abc\r\nfrom the members of the struct\/class\/union that starts with abc.\r\nIf you just type abc will the script complete it with the names that \r\nstarts with abc and ignore any current scope.\r\n\r\nThe default key mapping to complete the code are:\r\nAlt+l in insert mode will try to find the possible completions and display\r\nthem in a popup menu. Also normal completions to the names in\r\ncppcomplete.tags.\r\nAlt+j in insert mode will show the popup menu with the last results.\r\nSelecting one of the  items will paste the text.\r\nF8\/F9 will work in a similar way as Ctrl+N, Ctrl+P in unextended vim so the\r\nscript can be used without the popup menu.\r\nF5 in insert mode will lookup the class and display it in a preview window\r\nThe key mapping are only tested under Windows and linux and they will not\r\nwork on all platforms. Changing the mappings is easy.\r\n\r\nThe plugin is depending on that exuberant ctags has generated a tags file\r\ncalled cppcomplete.tags with the same options as in the following example:\r\nctags -n -f cppcomplete.tags --fields=+ai --C++-types=+p *\r\nThe script has a command called GenerateTags that executes the above ctags\r\ncommand. The tag file cppcomplete.tags is local to the script so you can\r\nuse other tag files without affecting cppcomplete. \r\nJava users do not need the --C++-types flag.\r\n\r\nFor C\/C++ can the script generate the cppcomplete.tags from the included\r\nfiles for you. This is based on vims checkpath function. The path must be\r\nset correct, see the vim documentation.\r\n\r\nThis script do not requires grep anymore but it is supported. If the option\r\nis set to build an internal list with derived classes and the first\r\ncompletion takes a very long time may grep speed things up. \r\nFor Windows does the DJGPP  port of grep works. \r\nYou only need grep.exe from the grep'version'b.zip file.\r\nA good place for grep.exe could be the compilers bin directory.\r\nThe zip file is in the v2gnu directory, it can be downloaded from here:\r\nhttp:\/\/www.delorie.com\/djgpp\/getting.html\r\n\r\nIt is possible to define a set of lines from cppcomplete.tags with regular\r\nexpressions. I call the set for a block. The functions for this:\r\nBuildBlockFromRegexp the command to build the block, see below.\r\nNextInBlock jump to the line described in the block, can be called by Shift+F8 \r\nPrevInBlock same as the above but in the other direction, use Shift+F9\r\nEchoBlock shows the block itself\r\nBuildMenuFromBlock builds a menu in GUI mode from the block\r\nThe jumps are done with an internal function so the tag stack will not be\r\naffected.\r\n\r\nSome simple examples there > is the prompt:\r\n>class:l\r\nGives a block with all members that has a scope of a class beginning with l\r\n>^a.*\\ts\\t\r\nall structures beginning with an a\r\n>^\\(a\\|b\\|c)\r\nEverything that starts with a,b or c\r\nThe full vim history mechanism can be used.\r\n\r\nThe script has a number of variables that can be set from the menu in the \r\nGUI or wildmenu versions. They are at the top of the script file with descriptions if\r\nyou want to change them more permanent.\r\n\r\nFor Java do you probably want to generate a cppcomplete.tags file from the\r\nsources of the Java SDK. The use is like with C\/C++ but you will get a\r\nbetter result if you change some of the configuration variables.\r\nThe default access is treated as if it was public. \r\n\r\nIf you are new to vim and have not heard about ctags, regexp, grep are they\r\nall described in the online documentation. Just type :help followed by the word you\r\nwant more information about. They are excellent tools that can be used for\r\nmany things.\r\n\r\n\r\nBUGS\/Features\r\nThis plugin does not really understand any C\/C++ code, it is not a real parser.\r\nIt works surprisingly well but can of course give a surprising result. :)\r\nThe current scope is unknown.\r\nMultidimensional arrays should not have a space between ][, e.g.\r\nxyz[1][2].abc should be OK but not xyz[1] [2].abc\r\nThe script does not accept functions, e.g. xyc()->abc will not be completed or rather\r\nit will be completed but from all names beginning with abc.\r\n(GTK) If the mouse leaves and then reenters the popup menu is the text cursor affected.\r\n(GTK) The popup is displayed at the mouse position and not the text cursor position.\r\nFor internal use is register c used.\r\nRequires exuberant ctags.\r\nThe only tested platforms for the popup menu are GTK (linux) and Windows.\r\n+ probably a lot of other issues\r\n\r\nAnyway, I have done some testing with MFC, DX9 framework (not COM), Java SDK, STL with\r\ngood results.\r\n","4":"This plugin helps you complete things like:\r\nvariableName.abc\r\nvariableName->abc\r\ntypeName::abc\r\nfrom the members of the struct\/class\/union that starts with abc.\r\nIf you just type abc will the script complete it with the names that \r\nstarts with abc and ignore any current scope.\r\n\r\nThe default key mapping to complete the code are:\r\nAlt+l in insert mode will try to find the possible completions and display\r\nthem in a popup menu. Also normal completions to the names in\r\ncppcomplete.tags.\r\nAlt+j in insert mode will show the popup menu with the last results.\r\nSelecting one of the  items will paste the text.\r\nF8\/F9 will work in a similar way as Ctrl+N, Ctrl+P in unextended vim so the\r\nscript can be used without the popup menu.\r\nF5 in insert mode will lookup the class and display it in a preview window\r\nThe key mapping are only tested under Windows and linux and they will not\r\nwork on all platforms. Changing the mappings is easy.\r\n\r\nThe plugin is depending on that exuberant ctags has generated a tags file\r\ncalled cppcomplete.tags with the same options as in the following example:\r\nctags -n -f cppcomplete.tags --fields=+ai --C++-types=+p *\r\nThe script has a command called GenerateTags that executes the above ctags\r\ncommand. The tag file cppcomplete.tags is local to the script so you can\r\nuse other tag files without affecting cppcomplete. \r\nJava users do not need the --C++-types flag.\r\n\r\nFor C\/C++ can the script generate the cppcomplete.tags from the included\r\nfiles for you. This is based on vims checkpath function. The path must be\r\nset correct, see the vim documentation.\r\n\r\nThis script do not requires grep anymore but it is supported. If the option\r\nis set to build an internal list with derived classes and the first\r\ncompletion takes a very long time may grep speed things up. \r\nFor Windows does the DJGPP  port of grep works. \r\nYou only need grep.exe from the grep'version'b.zip file.\r\nA good place for grep.exe could be the compilers bin directory.\r\nThe zip file is in the v2gnu directory, it can be downloaded from here:\r\nhttp:\/\/www.delorie.com\/djgpp\/getting.html\r\n\r\nIt is possible to define a set of lines from cppcomplete.tags with regular\r\nexpressions. I call the set for a block. The functions for this:\r\nBuildBlockFromRegexp the command to build the block, see below.\r\nNextInBlock jump to the line described in the block, can be called by Shift+F8 \r\nPrevInBlock same as the above but in the other direction, use Shift+F9\r\nEchoBlock shows the block itself\r\nBuildMenuFromBlock builds a menu in GUI mode from the block\r\nThe jumps are done with an internal function so the tag stack will not be\r\naffected.\r\n\r\nSome simple examples there > is the prompt:\r\n>class:l\r\nGives a block with all members that has a scope of a class beginning with l\r\n>^a.*\\ts\\t\r\nall structures beginning with an a\r\n>^\\(a\\|b\\|c)\r\nEverything that starts with a,b or c\r\nThe full vim history mechanism can be used.\r\n\r\nThe script has a number of variables that can be set from the menu in the \r\nGUI or wildmenu versions. They are at the top of the script file with descriptions if\r\nyou want to change them more permanent.\r\n\r\nFor Java do you probably want to generate a cppcomplete.tags file from the\r\nsources of the Java SDK. The use is like with C\/C++ but you will get a\r\nbetter result if you change some of the configuration variables.\r\nThe default access is treated as if it was public. \r\n\r\nIf you are new to vim and have not heard about ctags, regexp, grep are they\r\nall described in the online documentation. Just type :help followed by the word you\r\nwant more information about. They are excellent tools that can be used for\r\nmany things.\r\n\r\n\r\nBUGS\/Features\r\nThis plugin does not really understand any C\/C++ code, it is not a real parser.\r\nIt works surprisingly well but can of course give a surprising result. :)\r\nThe current scope is unknown.\r\nMultidimensional arrays should not have a space between ][, e.g.\r\nxyz[1][2].abc should be OK but not xyz[1] [2].abc\r\nThe script does not accept functions, e.g. xyc()->abc will not be completed or rather\r\nit will be completed but from all names beginning with abc.\r\n(GTK) If the mouse leaves and then reenters the popup menu is the text cursor affected.\r\n(GTK) The popup is displayed at the mouse position and not the text cursor position.\r\nFor internal use is register c used.\r\nRequires exuberant ctags.\r\nThe only tested platforms for the popup menu are GTK (linux) and Windows.\r\n+ probably a lot of other issues\r\n\r\nAnyway, I have done some testing with MFC, DX9 framework (not COM), Java SDK, STL with\r\ngood results.\r\n","install_details":"I put it in .vim\/plugin for automatic loading.\r\nExuberant ctags is also needed.\r\n","5":"I put it in .vim\/plugin for automatic loading.\r\nExuberant ctags is also needed.\r\n","first_name":"Peter","6":"Peter","last_name":"Puck","7":"Puck","releases":[{"0":"527","vim_version":"6.0","1":"6.0","script_version":"6.1","2":"6.1","version_comment":"The script should not affect the search history anymore. Hopefully is it also not so easy fooled by assignments after a } on the line above. Thanks to Colin Dearing and Peter Bengtsson for pointing out the problems.","3":"The script should not affect the search history anymore. Hopefully is it also not so easy fooled by assignments after a } on the line above. Thanks to Colin Dearing and Peter Bengtsson for pointing out the problems.","package":"cppcomplete.vim","4":"cppcomplete.vim","src_id":"1831","5":"1831","creation_date":"1048012418","6":"1048012418"},{"0":"527","vim_version":"6.0","1":"6.0","script_version":"6.0","2":"6.0","version_comment":"Mostly bug fixes and an attempt to improve performance. Also some other news such as better support for console users with wildmenu.\r\nMany thanks to Colin Dearing for bug hunting and his work to improve the script  for console users. ","3":"Mostly bug fixes and an attempt to improve performance. Also some other news such as better support for console users with wildmenu.\r\nMany thanks to Colin Dearing for bug hunting and his work to improve the script  for console users. ","package":"cppcomplete.vim","4":"cppcomplete.vim","src_id":"1786","5":"1786","creation_date":"1047060341","6":"1047060341"},{"0":"527","vim_version":"6.0","1":"6.0","script_version":"5.5","2":"5.5","version_comment":"Automatic generation of the browser file for C\/C++. The script does not requires grep anymore. Completion of all names in the browser file. Nanny mode for extra help.\r\nSome bug fixes.","3":"Automatic generation of the browser file for C\/C++. The script does not requires grep anymore. Completion of all names in the browser file. Nanny mode for extra help.\r\nSome bug fixes.","package":"cppcomplete.vim","4":"cppcomplete.vim","src_id":"1751","5":"1751","creation_date":"1045595515","6":"1045595515"},{"0":"527","vim_version":"6.0","1":"6.0","script_version":"5.01","2":"5.01","version_comment":"Discovered some stupid bugs in the linux version. One other bug with templates is also fixed.","3":"Discovered some stupid bugs in the linux version. One other bug with templates is also fixed.","package":"cppcomplete.vim","4":"cppcomplete.vim","src_id":"1708","5":"1708","creation_date":"1044740542","6":"1044740542"},{"0":"527","vim_version":"6.0","1":"6.0","script_version":"5.0","2":"5.0","version_comment":"Works under Windows again also if the shell is command.com with grep from DJGPP.  Java support. Various bugfixes and some other news.","3":"Works under Windows again also if the shell is command.com with grep from DJGPP.  Java support. Various bugfixes and some other news.","package":"cppcomplete.vim","4":"cppcomplete.vim","src_id":"1706","5":"1706","creation_date":"1044699886","6":"1044699886"},{"0":"527","vim_version":"6.0","1":"6.0","script_version":"4.0","2":"4.0","version_comment":"Added GUI stuff such as a popup menu and the script is also depending on gnu grep now. It will not work with windows command.com because long command lines must be supported.\r\nVarious bugfixes and some other new stuff.","3":"Added GUI stuff such as a popup menu and the script is also depending on gnu grep now. It will not work with windows command.com because long command lines must be supported.\r\nVarious bugfixes and some other new stuff.","package":"cppcomplete.vim","4":"cppcomplete.vim","src_id":"1679","5":"1679","creation_date":"1043796028","6":"1043796028"},{"0":"527","vim_version":"6.0","1":"6.0","script_version":"3.0","2":"3.0","version_comment":"Support for inheritance and various bug fixes.","3":"Support for inheritance and various bug fixes.","package":"cppcomplete.vim","4":"cppcomplete.vim","src_id":"1655","5":"1655","creation_date":"1043094142","6":"1043094142"},{"0":"527","vim_version":"6.0","1":"6.0","script_version":"2.0","2":"2.0","version_comment":"Added a new command to reuse last search pattern\r\nChanged so that only the preview window will be closed on abort or error\r\nNow completes directly if only one match\r\n","3":"Added a new command to reuse last search pattern\r\nChanged so that only the preview window will be closed on abort or error\r\nNow completes directly if only one match\r\n","package":"cppcomplete.vim","4":"cppcomplete.vim","src_id":"1632","5":"1632","creation_date":"1042532398","6":"1042532398"},{"0":"527","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"cppcomplete.vim","4":"cppcomplete.vim","src_id":"1628","5":"1628","creation_date":"1042435194","6":"1042435194"}]},"526":{"script_id":"526","0":"526","script_name":"pdbvim","1":"pdbvim","script_type":"utility","2":"utility","summary":"Interface to pdb for debugging python scripts","3":"Interface to pdb for debugging python scripts","description":"based on the interface to gdb in vimscript#84","4":"based on the interface to gdb in vimscript#84","install_details":"put pdbvim somewhere in your path, pdbvim.vim in your plugin dir.","5":"put pdbvim somewhere in your path, pdbvim.vim in your plugin dir.","first_name":"Mathew","6":"Mathew","last_name":"Yeates","7":"Yeates","releases":[{"0":"526","vim_version":"6.0","1":"6.0","script_version":"0.3","2":"0.3","version_comment":"general cleanup. Added an Exit option to the menu","3":"general cleanup. Added an Exit option to the menu","package":"pdbvim.tar.gz","4":"pdbvim.tar.gz","src_id":"1627","5":"1627","creation_date":"1042402377","6":"1042402377"},{"0":"526","vim_version":"6.0","1":"6.0","script_version":"0.2","2":"0.2","version_comment":"forgot to include mypdb.py which contains a\r\nsubclass of Pdb for easier parsing of pdb output.\r\nMake sure to place mypdb.py in your python path.","3":"forgot to include mypdb.py which contains a\r\nsubclass of Pdb for easier parsing of pdb output.\r\nMake sure to place mypdb.py in your python path.","package":"pdbvim.tar.gz","4":"pdbvim.tar.gz","src_id":"1619","5":"1619","creation_date":"1042124220","6":"1042124220"},{"0":"526","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"pdbvim.tar.gz","4":"pdbvim.tar.gz","src_id":"1615","5":"1615","creation_date":"1042036117","6":"1042036117"}]},"525":{"script_id":"525","0":"525","script_name":"cscope menu","1":"cscope menu","script_type":"utility","2":"utility","summary":"Creates Menu for Cscope commands","3":"Creates Menu for Cscope commands","description":"This script adds commonly used cscope commands as a menu.\r\nIt works on the word that is under the cursor.\r\n","4":"This script adds commonly used cscope commands as a menu.\r\nIt works on the word that is under the cursor.\r\n","install_details":"Install the cscopemenu.vim into $VIMRUNTIME\/plugin directory and restart vim","5":"Install the cscopemenu.vim into $VIMRUNTIME\/plugin directory and restart vim","first_name":"Kdr","6":"Kdr","last_name":"Tech","7":"Tech","releases":[{"0":"525","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"cscopemenu.vim","4":"cscopemenu.vim","src_id":"1614","5":"1614","creation_date":"1042031464","6":"1042031464"}]},"524":{"script_id":"524","0":"524","script_name":"Visual Studio .NET compiler file","1":"Visual Studio .NET compiler file","script_type":"utility","2":"utility","summary":"Compiler file for visual studio .NET devenv","3":"Compiler file for visual studio .NET devenv","description":"I use big Visual Studio .NET projects at work.  With .NET microsoft no longer supports exported project make files so nmake is dead for my purpoeses and I have to call devenv ( like so set makeprg=devenv\\ project.vcproj\\ -build\\ debug). \r\n\r\nThe errorformat of devenv is a bit different from the old vc6 build tool, so here's a script with the error format in.\r\n\r\nThis could actually get more elaborate, a buildproject script that took a project name as a parameter and build the apropiate  set makeprg= command and executes it could be done, but I'm in a hurry.","4":"I use big Visual Studio .NET projects at work.  With .NET microsoft no longer supports exported project make files so nmake is dead for my purpoeses and I have to call devenv ( like so set makeprg=devenv\\ project.vcproj\\ -build\\ debug). \r\n\r\nThe errorformat of devenv is a bit different from the old vc6 build tool, so here's a script with the error format in.\r\n\r\nThis could actually get more elaborate, a buildproject script that took a project name as a parameter and build the apropiate  set makeprg= command and executes it could be done, but I'm in a hurry.","install_details":"Copy it to vim's compilers directory. Make sure you invoke devenv.com and not devenv.exe -- the latter seems to crash when invoked from the command line.","5":"Copy it to vim's compilers directory. Make sure you invoke devenv.com and not devenv.exe -- the latter seems to crash when invoked from the command line.","first_name":"John","6":"John","last_name":"Connors","7":"Connors","releases":[{"0":"524","vim_version":"6.0","1":"6.0","script_version":"1.2","2":"1.2","version_comment":"Added %t to pick up error\/warning type.","3":"Added %t to pick up error\/warning type.","package":"msvsnet.vim","4":"msvsnet.vim","src_id":"1618","5":"1618","creation_date":"1042100225","6":"1042100225"},{"0":"524","vim_version":"6.0","1":"6.0","script_version":"1.1","2":"1.1","version_comment":"Simplified, changed '*; '#' to fit errorformat wildcard rules","3":"Simplified, changed '*; '#' to fit errorformat wildcard rules","package":"msvsnet.vim","4":"msvsnet.vim","src_id":"1616","5":"1616","creation_date":"1042087973","6":"1042087973"},{"0":"524","vim_version":"6.0","1":"6.0","script_version":"1.01","2":"1.01","version_comment":"Minor typo","3":"Minor typo","package":"msvsnet.vim","4":"msvsnet.vim","src_id":"1612","5":"1612","creation_date":"1042009901","6":"1042009901"},{"0":"524","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"msvsnet.vim","4":"msvsnet.vim","src_id":"1611","5":"1611","creation_date":"1042006979","6":"1042006979"}]},"523":{"script_id":"523","0":"523","script_name":"VimITunes.vim","1":"VimITunes.vim","script_type":"utility","2":"utility","summary":"Control iTunes from within Vim","3":"Control iTunes from within Vim","description":"Allows controlling iTunes on Macintosh from within Vim.\r\n\r\nAdds a menu \"iTunes\" that contains various commands to control iTunes.\r\n\r\nAdditionally, if the global variable \"VimITunesMapPrefix\" is set when this plugin is loaded, then several useful maps are created.  For example, if in your \".vimrc\" you have\r\n\r\n   let g:VimITunesMapPrefix = \",x\"\r\n\r\nthen after this plugin is loaded, you can use the following maps:\r\n\r\n       ,xq    Quit iTunes\r\n       ,xs    Toggle Shuffle Mode\r\n       ,xp    Toggle Pause Mode\r\n       ,xl    Next Song\r\n       ,xh    Previous Song\r\n       ,xk    Volume Up\r\n       ,xj    Volume Down\r\n       ,xm    Mute\r\n       ,x?    Display Song Title\r\n       ,xd    Disable the current song\r\n       ,xe    Enable the current song\r\n","4":"Allows controlling iTunes on Macintosh from within Vim.\r\n\r\nAdds a menu \"iTunes\" that contains various commands to control iTunes.\r\n\r\nAdditionally, if the global variable \"VimITunesMapPrefix\" is set when this plugin is loaded, then several useful maps are created.  For example, if in your \".vimrc\" you have\r\n\r\n   let g:VimITunesMapPrefix = \",x\"\r\n\r\nthen after this plugin is loaded, you can use the following maps:\r\n\r\n       ,xq    Quit iTunes\r\n       ,xs    Toggle Shuffle Mode\r\n       ,xp    Toggle Pause Mode\r\n       ,xl    Next Song\r\n       ,xh    Previous Song\r\n       ,xk    Volume Up\r\n       ,xj    Volume Down\r\n       ,xm    Mute\r\n       ,x?    Display Song Title\r\n       ,xd    Disable the current song\r\n       ,xe    Enable the current song\r\n","install_details":"Put this file into your plugin directory (do \":help *add-global-plugin*\" for assistance on how to do that).\r\n\r\nIf you want to use the mappings, then in your \".vimrc\" file, add something like the following:\r\n\r\n  let g:VimITunesMapPrefix = \",x\"\r\n","5":"Put this file into your plugin directory (do \":help *add-global-plugin*\" for assistance on how to do that).\r\n\r\nIf you want to use the mappings, then in your \".vimrc\" file, add something like the following:\r\n\r\n  let g:VimITunesMapPrefix = \",x\"\r\n","first_name":"Ed","6":"Ed","last_name":"Ralston","7":"Ralston","releases":[{"0":"523","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Stable version.\r\nSilenced mappings.\r\nFree variables after script initialization.","3":"Stable version.\r\nSilenced mappings.\r\nFree variables after script initialization.","package":"VimITunes.vim","4":"VimITunes.vim","src_id":"1617","5":"1617","creation_date":"1042091082","6":"1042091082"},{"0":"523","vim_version":"6.0","1":"6.0","script_version":"0.9","2":"0.9","version_comment":"Initial upload","3":"Initial upload","package":"VimITunes.vim","4":"VimITunes.vim","src_id":"1608","5":"1608","creation_date":"1041938824","6":"1041938824"}]},"522":{"script_id":"522","0":"522","script_name":"tar.vim","1":"tar.vim","script_type":"utility","2":"utility","summary":"A vim plugin for browsing tarfiles","3":"A vim plugin for browsing tarfiles","description":"Once this script is installed, attempting to edit a tarfile will present the\r\nuser with a list of files contained in the tar archive.  By moving the cursor\r\nover a filename and pressing ENTER, the contents of a file can be viewed in\r\nread-only mode, in a new window.  Unfortunately, write support for tarfile\r\ncomponents is not currently possible.\r\n\r\nRequires GNU tar, or a tar implementation that supports the \"P\" (don't strip\r\nout leading \/'s from filenames), and \"O\" (extract files to standard output)\r\noptions.  Additionally, gzip is required for handling *.tar.Z, *.tar.gz,\r\nand *.tgz compressed tarfiles, and bzip2 is required for handling *.tar.bz2\r\ncompressed tarfiles.  A unix-like operating system is probably also required.\r\n","4":"Once this script is installed, attempting to edit a tarfile will present the\r\nuser with a list of files contained in the tar archive.  By moving the cursor\r\nover a filename and pressing ENTER, the contents of a file can be viewed in\r\nread-only mode, in a new window.  Unfortunately, write support for tarfile\r\ncomponents is not currently possible.\r\n\r\nRequires GNU tar, or a tar implementation that supports the \"P\" (don't strip\r\nout leading \/'s from filenames), and \"O\" (extract files to standard output)\r\noptions.  Additionally, gzip is required for handling *.tar.Z, *.tar.gz,\r\nand *.tgz compressed tarfiles, and bzip2 is required for handling *.tar.bz2\r\ncompressed tarfiles.  A unix-like operating system is probably also required.\r\n","install_details":"Place this file, tar.vim, in your $HOME\/.vim\/plugin directory, and\r\neither restart vim, or execute \":source $HOME\/.vim\/plugin\/tar.vim\"\r\n","5":"Place this file, tar.vim, in your $HOME\/.vim\/plugin directory, and\r\neither restart vim, or execute \":source $HOME\/.vim\/plugin\/tar.vim\"\r\n","first_name":"Michael","6":"Michael","last_name":"Toren","7":"Toren","releases":[{"0":"522","vim_version":"6.0","1":"6.0","script_version":"1.00","2":"1.00","version_comment":"Initial upload","3":"Initial upload","package":"tar-1.00.vim","4":"tar-1.00.vim","src_id":"1600","5":"1600","creation_date":"1041686618","6":"1041686618"}]},"521":{"script_id":"521","0":"521","script_name":"mru.vim","1":"mru.vim","script_type":"utility","2":"utility","summary":"Plugin to manage Most Recently Used (MRU) files","3":"Plugin to manage Most Recently Used (MRU) files","description":"Overview\r\n\r\nThe Most Recently Used (MRU) plugin provides an easy access to a list of\r\nrecently opened\/edited files in Vim. This plugin automatically stores the\r\nfile names as you open\/edit them in Vim.\r\n\r\nThis plugin will work on all the platforms where Vim is supported. This\r\nplugin will work in both console and GUI Vim. This version of the MRU\r\nplugin needs Vim 7.0 and above. If you are using an earlier version of\r\nVim, then you should use an older version of the MRU plugin.\r\n\r\nThe recently used filenames are stored in a file specified by the Vim\r\nMRU_File variable.\r\n\r\nThe Github repository for the MRU plugin is available at:\r\n\r\n      http:\/\/github.com\/yegappan\/mru\r\n\r\nUsage\r\n\r\nTo list and edit files from the MRU list, you can use the \":MRU\" command.\r\nThe \":MRU\" command displays the MRU file list in a temporary Vim window.  If\r\nthe MRU window is already opened, then the MRU list displayed in the window\r\nis refreshed.\r\n\r\nIf you are using GUI Vim, then the names of the recently edited files are\r\nadded to the \"File->Recent Files\" menu. You can select the name of a file\r\nfrom this sub-menu to edit the file.\r\n\r\nYou can use the normal Vim commands to move around in the MRU window. You\r\ncannot make changes in the MRU window.\r\n\r\nYou can select a file name to edit by pressing the <Enter> key or by double\r\nclicking the left mouse button on a file name.  The selected file will be\r\nopened. If the file is already opened in a window, the cursor will be moved\r\nto that window. Otherwise, the file is opened in the previous window. If the\r\nprevious window has a modified buffer or is the preview window or is used by\r\nsome other plugin, then the file is opened in a new window.\r\n\r\nThe user manual is available at:\r\n\r\nhttps:\/\/github.com\/yegappan\/mru\/wiki\/User-Manual\r\n","4":"Overview\r\n\r\nThe Most Recently Used (MRU) plugin provides an easy access to a list of\r\nrecently opened\/edited files in Vim. This plugin automatically stores the\r\nfile names as you open\/edit them in Vim.\r\n\r\nThis plugin will work on all the platforms where Vim is supported. This\r\nplugin will work in both console and GUI Vim. This version of the MRU\r\nplugin needs Vim 7.0 and above. If you are using an earlier version of\r\nVim, then you should use an older version of the MRU plugin.\r\n\r\nThe recently used filenames are stored in a file specified by the Vim\r\nMRU_File variable.\r\n\r\nThe Github repository for the MRU plugin is available at:\r\n\r\n      http:\/\/github.com\/yegappan\/mru\r\n\r\nUsage\r\n\r\nTo list and edit files from the MRU list, you can use the \":MRU\" command.\r\nThe \":MRU\" command displays the MRU file list in a temporary Vim window.  If\r\nthe MRU window is already opened, then the MRU list displayed in the window\r\nis refreshed.\r\n\r\nIf you are using GUI Vim, then the names of the recently edited files are\r\nadded to the \"File->Recent Files\" menu. You can select the name of a file\r\nfrom this sub-menu to edit the file.\r\n\r\nYou can use the normal Vim commands to move around in the MRU window. You\r\ncannot make changes in the MRU window.\r\n\r\nYou can select a file name to edit by pressing the <Enter> key or by double\r\nclicking the left mouse button on a file name.  The selected file will be\r\nopened. If the file is already opened in a window, the cursor will be moved\r\nto that window. Otherwise, the file is opened in the previous window. If the\r\nprevious window has a modified buffer or is the preview window or is used by\r\nsome other plugin, then the file is opened in a new window.\r\n\r\nThe user manual is available at:\r\n\r\nhttps:\/\/github.com\/yegappan\/mru\/wiki\/User-Manual\r\n","install_details":"1. Download the mru.zip file and expand the mru.zip file into the \r\n    $HOME\/.vim directory for Linux\/MacOS\/Unix systems or the\r\n    HOMEPATH\/vimfiles directory for MS-Windows.  After this\r\n    step, you should have the following files (the directory structure\r\n    should be preserved):\r\n\r\n\tplugin\/mru.vim - MRU plugin\r\n\tdoc\/mru.txt    - documentation (help) file\r\n\r\n3. Change to the $HOME\/.vim\/doc or $HOME\/vimfiles\/doc directory, start Vim and\r\n   run the \":helptags .\" command to process the help file. Without this step,\r\n   you cannot jump to the MRU help topics.\r\n4. Restart Vim.\r\n5. You can use the |:MRU| command to list and edit the recently used files.\r\n   In GUI Vim, you can use the 'File->Recent Files' menu to access the\r\n   recently used files.\r\n\r\nTo uninstall the MRU plugin, either use the uninstall command provided by the\r\nplugin manager or manually remove the plugin\/mru.vim, and doc\/mru.txt\r\nfiles from either the $HOME\/.vim or $HOME\/vimfiles directory.\r\n","5":"1. Download the mru.zip file and expand the mru.zip file into the \r\n    $HOME\/.vim directory for Linux\/MacOS\/Unix systems or the\r\n    HOMEPATH\/vimfiles directory for MS-Windows.  After this\r\n    step, you should have the following files (the directory structure\r\n    should be preserved):\r\n\r\n\tplugin\/mru.vim - MRU plugin\r\n\tdoc\/mru.txt    - documentation (help) file\r\n\r\n3. Change to the $HOME\/.vim\/doc or $HOME\/vimfiles\/doc directory, start Vim and\r\n   run the \":helptags .\" command to process the help file. Without this step,\r\n   you cannot jump to the MRU help topics.\r\n4. Restart Vim.\r\n5. You can use the |:MRU| command to list and edit the recently used files.\r\n   In GUI Vim, you can use the 'File->Recent Files' menu to access the\r\n   recently used files.\r\n\r\nTo uninstall the MRU plugin, either use the uninstall command provided by the\r\nplugin manager or manually remove the plugin\/mru.vim, and doc\/mru.txt\r\nfiles from either the $HOME\/.vim or $HOME\/vimfiles directory.\r\n","first_name":"Yegappan","6":"Yegappan","last_name":"Lakshmanan","7":"Lakshmanan","releases":[{"0":"521","vim_version":"7.0","1":"7.0","script_version":"3.11","2":"3.11","version_comment":"1. Update the MRU list every time a buffer is entered (BufEnter).\r\n2. Add the MruGetFiles() function to return the List of MRU files. Can be used to execute Ex commands on the MRU list.\r\n3. When loading a deleted buffer, make the buffer listed again.\r\n4. Support using command modifiers (e.g. topleft) with the MRU command.\r\n5. Add the :MRUToggle command to toggle the MRU window.\r\n6. When the MRU file names are displayed in the current window, keep the alternate file when opening a file.\r\n7. Add support for setting the alternate file to the first file in the MRU list (MRU_Set_Alternate_File).\r\n8. Support opening encrypted files from the MRU list.\r\n9. Search the files in the MRU list ignoring case.\r\n10. Use the MRU window height for the FZF window.\r\n11. Pass the \"--no-sort\" option to FZF to keep the MRU file order.\r\n12. Refresh the MRU list before invoking FZF.\r\n13. Use the FZF window layout for the FZFMru command.\r\n","3":"1. Update the MRU list every time a buffer is entered (BufEnter).\r\n2. Add the MruGetFiles() function to return the List of MRU files. Can be used to execute Ex commands on the MRU list.\r\n3. When loading a deleted buffer, make the buffer listed again.\r\n4. Support using command modifiers (e.g. topleft) with the MRU command.\r\n5. Add the :MRUToggle command to toggle the MRU window.\r\n6. When the MRU file names are displayed in the current window, keep the alternate file when opening a file.\r\n7. Add support for setting the alternate file to the first file in the MRU list (MRU_Set_Alternate_File).\r\n8. Support opening encrypted files from the MRU list.\r\n9. Search the files in the MRU list ignoring case.\r\n10. Use the MRU window height for the FZF window.\r\n11. Pass the \"--no-sort\" option to FZF to keep the MRU file order.\r\n12. Refresh the MRU list before invoking FZF.\r\n13. Use the FZF window layout for the FZFMru command.\r\n","package":"mru.zip","4":"mru.zip","src_id":"28131","5":"28131","creation_date":"1661041353","6":"1661041353"},{"0":"521","vim_version":"7.0","1":"7.0","script_version":"3.10","2":"3.10","version_comment":"1. Add support for fuzzy searching the MRU list (using matchfuzzy())\r\n2. Add support for FZF integration\r\n3. Add support for deleting a file from the MRU list\r\n4. Expand the environment variables in the MRU_File variable.\r\n5. When opening a file from the MRU window using 't', reuse the current tab page if it is empty.\r\n6. Change the MRU buffer name to '-RecentFiles'\r\n7. Add support for command modifiers in the :MRU command\r\n8. Add support for specifying the MRU window height.\r\n9. When opening existing buffers, use buffer commands to retain buffer-local settings.\r\n","3":"1. Add support for fuzzy searching the MRU list (using matchfuzzy())\r\n2. Add support for FZF integration\r\n3. Add support for deleting a file from the MRU list\r\n4. Expand the environment variables in the MRU_File variable.\r\n5. When opening a file from the MRU window using 't', reuse the current tab page if it is empty.\r\n6. Change the MRU buffer name to '-RecentFiles'\r\n7. Add support for command modifiers in the :MRU command\r\n8. Add support for specifying the MRU window height.\r\n9. When opening existing buffers, use buffer commands to retain buffer-local settings.\r\n","package":"mru.zip","4":"mru.zip","src_id":"27470","5":"27470","creation_date":"1612609659","6":"1612609659"},{"0":"521","vim_version":"7.0","1":"7.0","script_version":"3.9","2":"3.9","version_comment":"1. Mapping for escape key breaks special key functionality in terminal Vim\r\n2. Configurable syntax highlighting pattern (Ingo Karkat)\r\n3. To open a file in a new tab page at the end, use $ instead of 999.\r\n4. When opening a file from the MRU list, if the current buffer is modified and the 'hidden' option is set, then replace the current buffer. Otherwise open the file in a new window.\r\n5. Updated the help text.\r\n","3":"1. Mapping for escape key breaks special key functionality in terminal Vim\r\n2. Configurable syntax highlighting pattern (Ingo Karkat)\r\n3. To open a file in a new tab page at the end, use $ instead of 999.\r\n4. When opening a file from the MRU list, if the current buffer is modified and the 'hidden' option is set, then replace the current buffer. Otherwise open the file in a new window.\r\n5. Updated the help text.\r\n","package":"mru.vim","4":"mru.vim","src_id":"22864","5":"22864","creation_date":"1423021851","6":"1423021851"},{"0":"521","vim_version":"7.0","1":"7.0","script_version":"3.8","2":"3.8","version_comment":"1. Add a mapping to open a file in the preview window (By Ingo Karkat)\r\n2. Add support for changing the filename format in the MRU window (By Ingo Karkat)\r\n3. Add new key bindings (By Ingo Karkat)\r\n4. Mark the MRU buffer as modifiable always\r\n5. Add syntax highlighting for file names\r\n","3":"1. Add a mapping to open a file in the preview window (By Ingo Karkat)\r\n2. Add support for changing the filename format in the MRU window (By Ingo Karkat)\r\n3. Add new key bindings (By Ingo Karkat)\r\n4. Mark the MRU buffer as modifiable always\r\n5. Add syntax highlighting for file names\r\n","package":"mru.vim","4":"mru.vim","src_id":"21583","5":"21583","creation_date":"1394385406","6":"1394385406"},{"0":"521","vim_version":"7.0","1":"7.0","script_version":"3.7","2":"3.7","version_comment":"1. Use the fnameescape() function (if available) to escape special characters in file names.","3":"1. Use the fnameescape() function (if available) to escape special characters in file names.","package":"mru.vim","4":"mru.vim","src_id":"21224","5":"21224","creation_date":"1387738259","6":"1387738259"},{"0":"521","vim_version":"7.0","1":"7.0","script_version":"3.6","2":"3.6","version_comment":"1. When deleting the last empty line in the MRU buffer, use the black hole (_) register.\r\n2. Set the filetype option for the MRU buffer to 'mru'.\r\n3. When comparing strings, use '==#' instead of '==' to match case.\r\n","3":"1. When deleting the last empty line in the MRU buffer, use the black hole (_) register.\r\n2. Set the filetype option for the MRU buffer to 'mru'.\r\n3. When comparing strings, use '==#' instead of '==' to match case.\r\n","package":"mru.vim","4":"mru.vim","src_id":"21223","5":"21223","creation_date":"1387734971","6":"1387734971"},{"0":"521","vim_version":"7.0","1":"7.0","script_version":"3.5","2":"3.5","version_comment":"First file in the MRU list is not added to the MRU menu. Fix a off-by-one error.\r\nUsed a wrong version of the plugin in the previous upload of 3.5. Fixed the problem.","3":"First file in the MRU list is not added to the MRU menu. Fix a off-by-one error.\r\nUsed a wrong version of the plugin in the previous upload of 3.5. Fixed the problem.","package":"mru.vim","4":"mru.vim","src_id":"20075","5":"20075","creation_date":"1368051131","6":"1368051131"},{"0":"521","vim_version":"7.0","1":"7.0","script_version":"3.4","2":"3.4","version_comment":"Separate the file name and the path in the MRU window. \r\nAdded support for always opening selected files in a tab (MRU_Open_File_Use_Tabs option). \r\nAdded support for opening the MRU window even for single files (MRU_Window_Open_Always option). \r\nAdded new mapping for opening files in a vertically split window from the MRU widow (key O).\r\n","3":"Separate the file name and the path in the MRU window. \r\nAdded support for always opening selected files in a tab (MRU_Open_File_Use_Tabs option). \r\nAdded support for opening the MRU window even for single files (MRU_Window_Open_Always option). \r\nAdded new mapping for opening files in a vertically split window from the MRU widow (key O).\r\n","package":"mru.vim","4":"mru.vim","src_id":"17773","5":"17773","creation_date":"1334430827","6":"1334430827"},{"0":"521","vim_version":"7.0","1":"7.0","script_version":"3.3","2":"3.3","version_comment":"* Limit the number of file names displayed in the MRU menu. Provide a configuration variable for selecting the number of file names displayed in the MRU menu or in the sub-menu.\r\n* Add a menu accelerator for the Recent Files menu.\r\n* Add the \":Mru\" command (alias for the \":MRU\" command) for ease of use.\r\n* When a file not present in the MRU list is supplied to the \":Mru\" command, then open the file.\r\n* Add 'v' command to edit a file from the MRU list as read-only.\r\n* Increase the default MRU list size to 100 from 10.\r\n* Support for opening multiple files from the MRU list.\r\n","3":"* Limit the number of file names displayed in the MRU menu. Provide a configuration variable for selecting the number of file names displayed in the MRU menu or in the sub-menu.\r\n* Add a menu accelerator for the Recent Files menu.\r\n* Add the \":Mru\" command (alias for the \":MRU\" command) for ease of use.\r\n* When a file not present in the MRU list is supplied to the \":Mru\" command, then open the file.\r\n* Add 'v' command to edit a file from the MRU list as read-only.\r\n* Increase the default MRU list size to 100 from 10.\r\n* Support for opening multiple files from the MRU list.\r\n","package":"mru.vim","4":"mru.vim","src_id":"11919","5":"11919","creation_date":"1261159536","6":"1261159536"},{"0":"521","vim_version":"7.0","1":"7.0","script_version":"3.2","2":"3.2","version_comment":"Escape special characters in filenames for security reasons. On MS-Windows, use the _vim_mru_files file from the $USERPROFILE directory. When the ':vimgrep' command is used, don't add the files to the MRU list. When getting the files matching a pattern, first try it as a literal string. Show tooltip text for MRU menu entries.","3":"Escape special characters in filenames for security reasons. On MS-Windows, use the _vim_mru_files file from the $USERPROFILE directory. When the ':vimgrep' command is used, don't add the files to the MRU list. When getting the files matching a pattern, first try it as a literal string. Show tooltip text for MRU menu entries.","package":"mru.vim","4":"mru.vim","src_id":"9274","5":"9274","creation_date":"1222145018","6":"1222145018"},{"0":"521","vim_version":"7.0","1":"7.0","script_version":"3.1","2":"3.1","version_comment":"Support for completion of filenames from the MRU file list for the :MRU command. Split the MRU menu into submenus when a large number of filenames are present in the MRU list. Fix for the placement of the MRU menu when Vim is running in compatible mode. New option to disable the MRU menu. The :MRUedit command is replaced by the :MRU command.\r\n","3":"Support for completion of filenames from the MRU file list for the :MRU command. Split the MRU menu into submenus when a large number of filenames are present in the MRU list. Fix for the placement of the MRU menu when Vim is running in compatible mode. New option to disable the MRU menu. The :MRUedit command is replaced by the :MRU command.\r\n","package":"mru.vim","4":"mru.vim","src_id":"8292","5":"8292","creation_date":"1203257538","6":"1203257538"},{"0":"521","vim_version":"7.0","1":"7.0","script_version":"3.0","2":"3.0","version_comment":"Works only with Vim version 7.0 and above. Uses Vim 7.0 data structures and functions. Support for opening files in tabs. Support for displaying files matching a pattern in the MRU window.","3":"Works only with Vim version 7.0 and above. Uses Vim 7.0 data structures and functions. Support for opening files in tabs. Support for displaying files matching a pattern in the MRU window.","package":"mru.vim","4":"mru.vim","src_id":"8148","5":"8148","creation_date":"1200182393","6":"1200182393"},{"0":"521","vim_version":"6.0","1":"6.0","script_version":"2.5","2":"2.5","version_comment":"Use <abuf> instead of <afile> in autocmds. Escape backslash while searching for partial filenames.","3":"Use <abuf> instead of <afile> in autocmds. Escape backslash while searching for partial filenames.","package":"mru.vim","4":"mru.vim","src_id":"7851","5":"7851","creation_date":"1193828880","6":"1193828880"},{"0":"521","vim_version":"6.0","1":"6.0","script_version":"2.4","2":"2.4","version_comment":"Escape the % and # characters in the MRU filenames. Don't open a selected file in the preview window or in a window used by a Vim plugin.","3":"Escape the % and # characters in the MRU filenames. Don't open a selected file in the preview window or in a window used by a Vim plugin.","package":"mru.vim","4":"mru.vim","src_id":"6352","5":"6352","creation_date":"1162232851","6":"1162232851"},{"0":"521","vim_version":"6.0","1":"6.0","script_version":"2.3","2":"2.3","version_comment":"Escape single quote characters in filenames. Use exact match while searching for open files.","3":"Escape single quote characters in filenames. Use exact match while searching for open files.","package":"mru.vim","4":"mru.vim","src_id":"5798","5":"5798","creation_date":"1149375187","6":"1149375187"},{"0":"521","vim_version":"6.0","1":"6.0","script_version":"2.2","2":"2.2","version_comment":"1. Save the list of MRU files to the MRU db file as soon as the list is changed.\r\n2. Escape space characters in file names.\r\n3. Add the :MRUedit command to edit files from the MRU list.","3":"1. Save the list of MRU files to the MRU db file as soon as the list is changed.\r\n2. Escape space characters in file names.\r\n3. Add the :MRUedit command to edit files from the MRU list.","package":"mru.vim","4":"mru.vim","src_id":"5788","5":"5788","creation_date":"1149009390","6":"1149009390"},{"0":"521","vim_version":"6.0","1":"6.0","script_version":"2.1","2":"2.1","version_comment":"Fixed a problem with handling space characters in the name of the MRU file. Modified the plugin to work in Vi compatible mode.","3":"Fixed a problem with handling space characters in the name of the MRU file. Modified the plugin to work in Vi compatible mode.","package":"mru.vim","4":"mru.vim","src_id":"4235","5":"4235","creation_date":"1115146064","6":"1115146064"},{"0":"521","vim_version":"6.0","1":"6.0","script_version":"2.0","2":"2.0","version_comment":"Fixed the problem with one Vim session overwritting the MRU list from another Vim session. Added the MRU file list to the File menu in GUI Vim. Instead of using a Vim global variable to store the MRU list, used a separate file to store the MRU list.","3":"Fixed the problem with one Vim session overwritting the MRU list from another Vim session. Added the MRU file list to the File menu in GUI Vim. Instead of using a Vim global variable to store the MRU list, used a separate file to store the MRU list.","package":"mru.vim","4":"mru.vim","src_id":"4084","5":"4084","creation_date":"1111880956","6":"1111880956"},{"0":"521","vim_version":"6.0","1":"6.0","script_version":"1.6","2":"1.6","version_comment":"Fixed the following bugs: Some filenames are added more than once to the MRU list and the MRU window is not closed when a file which already opened in one of the windows is selected from the MRU window.","3":"Fixed the following bugs: Some filenames are added more than once to the MRU list and the MRU window is not closed when a file which already opened in one of the windows is selected from the MRU window.","package":"mru.vim","4":"mru.vim","src_id":"2172","5":"2172","creation_date":"1058609027","6":"1058609027"},{"0":"521","vim_version":"6.0","1":"6.0","script_version":"1.5","2":"1.5","version_comment":"Open the selected file from the MRU list in the window from which the MRU window was opened.","3":"Open the selected file from the MRU list in the window from which the MRU window was opened.","package":"mru.vim","4":"mru.vim","src_id":"2124","5":"2124","creation_date":"1057160347","6":"1057160347"}]},"520":{"script_id":"520","0":"520","script_name":"PHPDoc Script (PDocS)","1":"PHPDoc Script (PDocS)","script_type":"ftplugin","2":"ftplugin","summary":"PHPDoc Support in VIM while writing PHP-Source","3":"PHPDoc Support in VIM while writing PHP-Source","description":"PHPDoc Script (PDocS) supports you in writing PHPDoc like comments while creating PHP-Source code. You don't need to copy\/paste the \r\nDoc block over and over so you can create them while writing the source\r\ncode. This will result in better commets...;-)\r\nThe Script currently supports only one Styleguide.\r\n\r\nI hope it helps...\r\n\r\nI have created the script on Vim 6.1, but i think it should be running well\r\non Vim 6.0 too. I hope so...","4":"PHPDoc Script (PDocS) supports you in writing PHPDoc like comments while creating PHP-Source code. You don't need to copy\/paste the \r\nDoc block over and over so you can create them while writing the source\r\ncode. This will result in better commets...;-)\r\nThe Script currently supports only one Styleguide.\r\n\r\nI hope it helps...\r\n\r\nI have created the script on Vim 6.1, but i think it should be running well\r\non Vim 6.0 too. I hope so...","install_details":"See the Script-File inside the tar (Just put it into the plugin directory).","5":"See the Script-File inside the tar (Just put it into the plugin directory).","first_name":"Karl Heinz","6":"Karl Heinz","last_name":"Marbaise","7":"Marbaise","releases":[{"0":"520","vim_version":"6.0","1":"6.0","script_version":"0.26","2":"0.26","version_comment":"- Removed BufLeave which was not needed\r\n  and produced an Warning message in Vim\r\n- Change to Unix LF","3":"- Removed BufLeave which was not needed\r\n  and produced an Warning message in Vim\r\n- Change to Unix LF","package":"phpdocs-0.26.tar.gz","4":"phpdocs-0.26.tar.gz","src_id":"1601","5":"1601","creation_date":"1041750389","6":"1041750389"},{"0":"520","vim_version":"6.0","1":"6.0","script_version":"0.25","2":"0.25","version_comment":"Initial upload","3":"Initial upload","package":"phpdocs-0.25.tar.gz","4":"phpdocs-0.25.tar.gz","src_id":"1593","5":"1593","creation_date":"1041423566","6":"1041423566"}]},"519":{"script_id":"519","0":"519","script_name":"CVS conflict highlight","1":"CVS conflict highlight","script_type":"syntax","2":"syntax","summary":"This script highlights conflicts marked by CVS","3":"This script highlights conflicts marked by CVS","description":"I've created VIM syntax file for files where CVS\r\nfound a conflict.\r\n\r\nSuch files may be detected as containing such patterns:\r\n\r\n^<<<<<<< .*\r\n^=======$\r\n^>>>>>>> .*\r\n\r\nThis syntax file highlights areas where CVS marked a\r\nconflict, resolve conflict until no highlighting is left :)\r\n","4":"I've created VIM syntax file for files where CVS\r\nfound a conflict.\r\n\r\nSuch files may be detected as containing such patterns:\r\n\r\n^<<<<<<< .*\r\n^=======$\r\n^>>>>>>> .*\r\n\r\nThis syntax file highlights areas where CVS marked a\r\nconflict, resolve conflict until no highlighting is left :)\r\n","install_details":"Put this file into your vim syntax file directory.\r\n\r\nto activate script, use \r\n\r\n:set syntax=cvs_cnfl","5":"Put this file into your vim syntax file directory.\r\n\r\nto activate script, use \r\n\r\n:set syntax=cvs_cnfl","first_name":"Alex","6":"Alex","last_name":"Jakushev","7":"Jakushev","releases":[{"0":"519","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"cvs_cnfl.vim","4":"cvs_cnfl.vim","src_id":"1589","5":"1589","creation_date":"1041293870","6":"1041293870"}]},"518":{"script_id":"518","0":"518","script_name":"csv color","1":"csv color","script_type":"syntax","2":"syntax","summary":"syntax highlight for CSV files","3":"syntax highlight for CSV files","description":"Simple commands to highlight CSV files. At this moment it only supports tab delimited files.","4":"Simple commands to highlight CSV files. At this moment it only supports tab delimited files.","install_details":"method 1) :source csv.vim\r\nmethod 2) add to .vimrc:  autocmd BufNewFile,BufRead *.csv source csv.vim\r\n","5":"method 1) :source csv.vim\r\nmethod 2) add to .vimrc:  autocmd BufNewFile,BufRead *.csv source csv.vim\r\n","first_name":"Andre","6":"Andre","last_name":"Hentz","7":"Hentz","releases":[{"0":"518","vim_version":"6.0","1":"6.0","script_version":"1.01","2":"1.01","version_comment":"bug fixes","3":"bug fixes","package":"csv.vim","4":"csv.vim","src_id":"2357","5":"2357","creation_date":"1064589914","6":"1064589914"},{"0":"518","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"csv.vim","4":"csv.vim","src_id":"1568","5":"1568","creation_date":"1040299467","6":"1040299467"}]},"517":{"script_id":"517","0":"517","script_name":"TVO: The Vim Outliner","1":"TVO: The Vim Outliner","script_type":"ftplugin","2":"ftplugin","summary":"Turn vim into a full-featured text outliner","3":"Turn vim into a full-featured text outliner","description":"TVO (The Vim Outliner) is my solution for text outlining in Vim.\r\n\r\nIt works a lot like Word's outline support, but is much more vim-compatible.\r\nIt has syntax highlighting, embedded text blocks, shortcut mappings using both  LocalLeader and arrow keys, and works reasonably well with Vim Easy.\r\nThere is a toolbar that will be familiar to you if you've used Word's outliner.\r\n\r\nYou can extract just text, or just headings if you wish; there's also some converters (to HTML, Perl POD, and to RTF) included.\r\n\r\nPlease email me with bug reports, improvements, comments or more documentation (badly needed!).\r\n\r\nEarlier versions are available at http:\/\/bike-nomad.com\/vim\/vimoutliner.html","4":"TVO (The Vim Outliner) is my solution for text outlining in Vim.\r\n\r\nIt works a lot like Word's outline support, but is much more vim-compatible.\r\nIt has syntax highlighting, embedded text blocks, shortcut mappings using both  LocalLeader and arrow keys, and works reasonably well with Vim Easy.\r\nThere is a toolbar that will be familiar to you if you've used Word's outliner.\r\n\r\nYou can extract just text, or just headings if you wish; there's also some converters (to HTML, Perl POD, and to RTF) included.\r\n\r\nPlease email me with bug reports, improvements, comments or more documentation (badly needed!).\r\n\r\nEarlier versions are available at http:\/\/bike-nomad.com\/vim\/vimoutliner.html","install_details":"Installing in a local or global .vim directory\r\n\r\nYou will want to install TVO into a directory in your Vim\r\nruntimepath (:he 'runtimepath'). Type the command\r\n\r\n:set runtimepath\r\n\r\nTo find out what it is set to. This will display a list of\r\ndirectories separated by commas. On my Linux system, these\r\ndirectories are:\r\n\r\n~\/.vim\r\n\/usr\/local\/share\/vim\/vimfiles\r\n\/usr\/local\/share\/vim\/vim60\r\n\/usr\/local\/share\/vim\/vimfiles\/after\r\n~\/.vim\/after\r\n\r\nI installed TVO into my ~\/.vim directory.\r\n\r\nI could have also installed it so it would be available to all the\r\nusers on my system by putting it into either the\r\n\/usr\/local\/share\/vim\/vimfiles or \/usr\/local\/share\/vim\/vim60\r\ndirectories.\r\n\r\nInstalling the binaries\r\n\r\nI've included some scripts in Perl and Ruby that I use for\r\nconversion of .otl files to HTML, RTF, and Perl POD. There is also\r\na pod2otl converter.\r\nYou can move these to a directory on your path (you may also have\r\nto change the shebang (#!) lines).\r\n","5":"Installing in a local or global .vim directory\r\n\r\nYou will want to install TVO into a directory in your Vim\r\nruntimepath (:he 'runtimepath'). Type the command\r\n\r\n:set runtimepath\r\n\r\nTo find out what it is set to. This will display a list of\r\ndirectories separated by commas. On my Linux system, these\r\ndirectories are:\r\n\r\n~\/.vim\r\n\/usr\/local\/share\/vim\/vimfiles\r\n\/usr\/local\/share\/vim\/vim60\r\n\/usr\/local\/share\/vim\/vimfiles\/after\r\n~\/.vim\/after\r\n\r\nI installed TVO into my ~\/.vim directory.\r\n\r\nI could have also installed it so it would be available to all the\r\nusers on my system by putting it into either the\r\n\/usr\/local\/share\/vim\/vimfiles or \/usr\/local\/share\/vim\/vim60\r\ndirectories.\r\n\r\nInstalling the binaries\r\n\r\nI've included some scripts in Perl and Ruby that I use for\r\nconversion of .otl files to HTML, RTF, and Perl POD. There is also\r\na pod2otl converter.\r\nYou can move these to a directory on your path (you may also have\r\nto change the shebang (#!) lines).\r\n","first_name":"Ned","6":"Ned","last_name":"Konz","7":"Konz","releases":[{"0":"517","vim_version":"6.0","1":"6.0","script_version":"122","2":"122","version_comment":"    * Fixed Viki integration (with fixes from Thomas Link)\r\n    * Changed email address in ftplugin\/otl.vim\r\n    * Defaulted g:otl_use_viki\r\n    * Made double-click conditional on having a fold\r\n    * Added variable g:otl_highlight_extensions to make TODO, XXX, and NOTE highlighting configurable\r\n    * Improved installation directions in README.otl ","3":"    * Fixed Viki integration (with fixes from Thomas Link)\r\n    * Changed email address in ftplugin\/otl.vim\r\n    * Defaulted g:otl_use_viki\r\n    * Made double-click conditional on having a fold\r\n    * Added variable g:otl_highlight_extensions to make TODO, XXX, and NOTE highlighting configurable\r\n    * Improved installation directions in README.otl ","package":"vimoutliner-122.zip","4":"vimoutliner-122.zip","src_id":"5768","5":"5768","creation_date":"1148565809","6":"1148565809"},{"0":"517","vim_version":"6.0","1":"6.0","script_version":"111","2":"111","version_comment":"Made settings work right for the first file!\r\nIn my prior 2 versions (trying to get the modelines to work) I inadvertently made the settings for the first file broken.","3":"Made settings work right for the first file!\r\nIn my prior 2 versions (trying to get the modelines to work) I inadvertently made the settings for the first file broken.","package":"vimoutliner-111.zip","4":"vimoutliner-111.zip","src_id":"5461","5":"5461","creation_date":"1142789744","6":"1142789744"}]},"516":{"script_id":"516","0":"516","script_name":"sr.vim","1":"sr.vim","script_type":"syntax","2":"syntax","summary":"SR (Synchronizing Resources) syntax highlighting script","3":"SR (Synchronizing Resources) syntax highlighting script","description":"This is a syntax highlighting script for synchronizing resources.\r\nThis language is mainly intended for educational use and I doubt anyone will find it useful for writing anything meant for widespread use.\r\nYou can find the homepage here http:\/\/www.cs.arizona.edu\/sr\/\r\nand an excellent reference here http:\/\/www.mcs.drexel.edu\/~shartley\/OSusingSR\/\r\n\r\nYou could probably extend this script alot by specifying regions and clusters and stuff, but as I will probably never use the language again I didn't bother learning how to.","4":"This is a syntax highlighting script for synchronizing resources.\r\nThis language is mainly intended for educational use and I doubt anyone will find it useful for writing anything meant for widespread use.\r\nYou can find the homepage here http:\/\/www.cs.arizona.edu\/sr\/\r\nand an excellent reference here http:\/\/www.mcs.drexel.edu\/~shartley\/OSusingSR\/\r\n\r\nYou could probably extend this script alot by specifying regions and clusters and stuff, but as I will probably never use the language again I didn't bother learning how to.","install_details":"Put sr.vim in .vim\/syntax\/ and add the following lines to .vim\/filetype.vim:\r\n\r\naugroup filetypedetect\r\n\r\nau BufNewFile,BufRead *.sr setf sr\r\naugroup END","5":"Put sr.vim in .vim\/syntax\/ and add the following lines to .vim\/filetype.vim:\r\n\r\naugroup filetypedetect\r\n\r\nau BufNewFile,BufRead *.sr setf sr\r\naugroup END","first_name":"David","6":"David","last_name":"Holm","7":"Holm","releases":[{"0":"516","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"sr.vim","4":"sr.vim","src_id":"1564","5":"1564","creation_date":"1040276975","6":"1040276975"}]},"515":{"script_id":"515","0":"515","script_name":"python_fold","1":"python_fold","script_type":"utility","2":"utility","summary":"Folding expression for python","3":"Folding expression for python","description":"This script uses the expr fold-method to create folds for python source code.\r\n\r\nFolds are created for:\r\n - Class definitions\r\n - def function definitions\r\n - Blocks between {{{, }}} markers (but not yet {{{n, etc.)\r\n\r\nThe fold level for each fold is equal to the indentation divided by the value of the 'shiftwidth' option, so make sure that 'shiftwidth' is set to the right value for your code.\r\n\r\nClass and function folds show a count of the number of lines in the fold and the documentation string when closed (contributed by Max Ischenko).\r\n\r\nCaveats:\r\n- The docstring is not shown when it is enclosed in single quotes (like '''comment'''); use double quotes instead (like \"\"\"comment\"\"\")\r\n- Newest version relies on a blank line following class or function definition if the next bit of code is not a new class or function definition.  If this doesn't suit your programming style, use the _nonblank version 2.2 (nb).  That version is buggier, however.  Do not install both files.\r\n\r\nBugs:\r\n- It occasionally inserts a bogus fold at complicated structures like conditionals that are followed by a blank line.  A work-around is to remove the blank line or to replace it with a line containing a comment (a single '#' will do)","4":"This script uses the expr fold-method to create folds for python source code.\r\n\r\nFolds are created for:\r\n - Class definitions\r\n - def function definitions\r\n - Blocks between {{{, }}} markers (but not yet {{{n, etc.)\r\n\r\nThe fold level for each fold is equal to the indentation divided by the value of the 'shiftwidth' option, so make sure that 'shiftwidth' is set to the right value for your code.\r\n\r\nClass and function folds show a count of the number of lines in the fold and the documentation string when closed (contributed by Max Ischenko).\r\n\r\nCaveats:\r\n- The docstring is not shown when it is enclosed in single quotes (like '''comment'''); use double quotes instead (like \"\"\"comment\"\"\")\r\n- Newest version relies on a blank line following class or function definition if the next bit of code is not a new class or function definition.  If this doesn't suit your programming style, use the _nonblank version 2.2 (nb).  That version is buggier, however.  Do not install both files.\r\n\r\nBugs:\r\n- It occasionally inserts a bogus fold at complicated structures like conditionals that are followed by a blank line.  A work-around is to remove the blank line or to replace it with a line containing a comment (a single '#' will do)","install_details":"Choose either python_fold.vim or python_fold_nonblank.vim (do not use both at the same time!).\r\nEither save it in a file and source that file whenever you want to use the folding, or save it in your ftplugin directory (for example, ~\/.vim\/ftplugin) and it should load every time you edit python code.","5":"Choose either python_fold.vim or python_fold_nonblank.vim (do not use both at the same time!).\r\nEither save it in a file and source that file whenever you want to use the folding, or save it in your ftplugin directory (for example, ~\/.vim\/ftplugin) and it should load every time you edit python code.","first_name":"Jorrit","6":"Jorrit","last_name":"Wiersma","7":"Wiersma","releases":[{"0":"515","vim_version":"6.0","1":"6.0","script_version":"2.3","2":"2.3","version_comment":"Added line counts to the foldtext for closed folds.","3":"Added line counts to the foldtext for closed folds.","package":"python_fold.vim","4":"python_fold.vim","src_id":"4431","5":"4431","creation_date":"1121327996","6":"1121327996"},{"0":"515","vim_version":"6.0","1":"6.0","script_version":"2.2","2":"2.2","version_comment":"Fixed bug: fold text now shows \"pass\" for passed functions and classes.","3":"Fixed bug: fold text now shows \"pass\" for passed functions and classes.","package":"python_fold.vim","4":"python_fold.vim","src_id":"3193","5":"3193","creation_date":"1088575911","6":"1088575911"},{"0":"515","vim_version":"6.0","1":"6.0","script_version":"2.2 (nb)","2":"2.2 (nb)","version_comment":"Fixed bug: fold text now shows \"pass\" for passed functions and classes.  This is the version for files without blank lines: see comment on version 2.1 (nb)","3":"Fixed bug: fold text now shows \"pass\" for passed functions and classes.  This is the version for files without blank lines: see comment on version 2.1 (nb)","package":"python_fold_nonblank.vim","4":"python_fold_nonblank.vim","src_id":"3192","5":"3192","creation_date":"1088575865","6":"1088575865"},{"0":"515","vim_version":"6.0","1":"6.0","script_version":"2.1","2":"2.1","version_comment":"Fixed spurious folds problem by relying (somewhat) on blank lines following class and function definitions.  Fix contributed by Tom Schumm.","3":"Fixed spurious folds problem by relying (somewhat) on blank lines following class and function definitions.  Fix contributed by Tom Schumm.","package":"python_fold.vim","4":"python_fold.vim","src_id":"2371","5":"2371","creation_date":"1065403716","6":"1065403716"},{"0":"515","vim_version":"6.0","1":"6.0","script_version":"2.1 (nb)","2":"2.1 (nb)","version_comment":"Small bugfixes.  The next version will rely somewhat on blank lines following class or function definitions.  Try that one first: it works much better.  If that one doesn't work for you because you use absolutely no blank lines in your code then you can try this one.","3":"Small bugfixes.  The next version will rely somewhat on blank lines following class or function definitions.  Try that one first: it works much better.  If that one doesn't work for you because you use absolutely no blank lines in your code then you can try this one.","package":"python_fold_nonblank.vim","4":"python_fold_nonblank.vim","src_id":"2370","5":"2370","creation_date":"1065403624","6":"1065403624"},{"0":"515","vim_version":"6.0","1":"6.0","script_version":"2.0","2":"2.0","version_comment":"Added foldtext contributed by Max Ischenko.  Closed folds now show the documentation string of the class or function if present.","3":"Added foldtext contributed by Max Ischenko.  Closed folds now show the documentation string of the class or function if present.","package":"python_fold.vim","4":"python_fold.vim","src_id":"1974","5":"1974","creation_date":"1052377793","6":"1052377793"},{"0":"515","vim_version":"6.0","1":"6.0","script_version":"1.2","2":"1.2","version_comment":"Fixed continuation line detection","3":"Fixed continuation line detection","package":"python_fold.vim","4":"python_fold.vim","src_id":"1972","5":"1972","creation_date":"1052364130","6":"1052364130"},{"0":"515","vim_version":"6.0","1":"6.0","script_version":"1.1","2":"1.1","version_comment":"Fixed small bug (didn't look for whitespace after def or class)","3":"Fixed small bug (didn't look for whitespace after def or class)","package":"python_fold.vim","4":"python_fold.vim","src_id":"1565","5":"1565","creation_date":"1040287548","6":"1040287548"},{"0":"515","vim_version":"6.0","1":"6.0","script_version":"1","2":"1","version_comment":"Initial upload","3":"Initial upload","package":"python_fold.vim","4":"python_fold.vim","src_id":"1563","5":"1563","creation_date":"1040267332","6":"1040267332"}]},"514":{"script_id":"514","0":"514","script_name":"mrswin.vim","1":"mrswin.vim","script_type":"utility","2":"utility","summary":"Like mswin, but can be toggled off and on","3":"Like mswin, but can be toggled off and on","description":"Sourcing <mrswin.vim> toggles between <mswin.vim> and normal Vim.  You'll find <mswin.vim> distributed with Vim as\r\n\r\n   ..\\vim\\vim63\\mswin.vim\r\n\r\n(the leading path may vary).  This file needs to be executed instead of the default <mswin.vim>; every time it is sourced, it toggles between <mswin.vim> and Normal vim mappings and settings.  \r\n\r\nIt is important that you substitute using <mrswin.vim> for <mswin.vim>; <mrswin.vim> saves the settings and mappings extant prior to doing the <mswin.vim> settings and mappings.  Consequently, if you have <mswin.vim> sourced first, then its settings and mappings are what will be restored (ie., you won't be able to toggle because both sets of settings and mappings will be the same).\r\n","4":"Sourcing <mrswin.vim> toggles between <mswin.vim> and normal Vim.  You'll find <mswin.vim> distributed with Vim as\r\n\r\n   ..\\vim\\vim63\\mswin.vim\r\n\r\n(the leading path may vary).  This file needs to be executed instead of the default <mswin.vim>; every time it is sourced, it toggles between <mswin.vim> and Normal vim mappings and settings.  \r\n\r\nIt is important that you substitute using <mrswin.vim> for <mswin.vim>; <mrswin.vim> saves the settings and mappings extant prior to doing the <mswin.vim> settings and mappings.  Consequently, if you have <mswin.vim> sourced first, then its settings and mappings are what will be restored (ie., you won't be able to toggle because both sets of settings and mappings will be the same).\r\n","install_details":"Change the name of\r\n   ..\\vim\\vim63\\mswin.vim\r\nto\r\n   ..\\vim\\vim63\\old_mswin.vim.\r\n\r\nPut <mrswin.vim> wherever and have\r\n\r\n   so ...wherever\/mrswin.vim\r\n\r\nin your <_vimrc> file.\r\n","5":"Change the name of\r\n   ..\\vim\\vim63\\mswin.vim\r\nto\r\n   ..\\vim\\vim63\\old_mswin.vim.\r\n\r\nPut <mrswin.vim> wherever and have\r\n\r\n   so ...wherever\/mrswin.vim\r\n\r\nin your <_vimrc> file.\r\n","first_name":"Charles","6":"Charles","last_name":"Campbell","7":"Campbell","releases":[{"0":"514","vim_version":"6.0","1":"6.0","script_version":"4","2":"4","version_comment":"bugfix: inadvertently left debugging enabled -- now fixed!","3":"bugfix: inadvertently left debugging enabled -- now fixed!","package":"mrswin.vim.bz2","4":"mrswin.vim.bz2","src_id":"3276","5":"3276","creation_date":"1090923460","6":"1090923460"},{"0":"514","vim_version":"6.0","1":"6.0","script_version":"3","2":"3","version_comment":"MrsWin now checks for a running gui vs simply having gui capability in deciding to map meta-<space> like mswin.vim does.\r\nMrsWin updated to be based upon v6.3's mswin\r\nFolding and debugging commands were added\r\n","3":"MrsWin now checks for a running gui vs simply having gui capability in deciding to map meta-<space> like mswin.vim does.\r\nMrsWin updated to be based upon v6.3's mswin\r\nFolding and debugging commands were added\r\n","package":"mrswin.vim.bz2","4":"mrswin.vim.bz2","src_id":"3241","5":"3241","creation_date":"1089968404","6":"1089968404"},{"0":"514","vim_version":"6.0","1":"6.0","script_version":"1","2":"1","version_comment":"Initial upload","3":"Initial upload","package":"mrswin.vim","4":"mrswin.vim","src_id":"1557","5":"1557","creation_date":"1040126054","6":"1040126054"}]},"513":{"script_id":"513","0":"513","script_name":"Indent Finder","1":"Indent Finder","script_type":"indent","2":"indent","summary":"Always set the correct indentation for the file you are editing.","3":"Always set the correct indentation for the file you are editing.","description":"For each new open buffer, scans the buffer, find the indentation being used in the file and configure vim to this indentation. \r\n\r\nThis solves the problem of files with different indentations.\r\n\r\nHomepage of the project:\r\nhttp:\/\/www.freehackers.org\/Indent_Finder\r\n","4":"For each new open buffer, scans the buffer, find the indentation being used in the file and configure vim to this indentation. \r\n\r\nThis solves the problem of files with different indentations.\r\n\r\nHomepage of the project:\r\nhttp:\/\/www.freehackers.org\/Indent_Finder\r\n","install_details":"Install the python script with python setup.py install and install the vim plugin (:help plugins in vim for more information on how to install plugins)","5":"Install the python script with python setup.py install and install the vim plugin (:help plugins in vim for more information on how to install plugins)","first_name":"Philippe","6":"Philippe","last_name":"Fremy","7":"Fremy","releases":[{"0":"513","vim_version":"7.0","1":"7.0","script_version":"1.31","2":"1.31","version_comment":"Important bug fix: the vim plugin was not working.","3":"Important bug fix: the vim plugin was not working.","package":"indent_finder-1.31.zip","4":"indent_finder-1.31.zip","src_id":"9229","5":"9229","creation_date":"1220759082","6":"1220759082"},{"0":"513","vim_version":"5.7","1":"5.7","script_version":"1.3b","2":"1.3b","version_comment":"Small problem in packaging that prevented the script to work.","3":"Small problem in packaging that prevented the script to work.","package":"indent_finder-1.3b.zip","4":"indent_finder-1.3b.zip","src_id":"8998","5":"8998","creation_date":"1216721503","6":"1216721503"},{"0":"513","vim_version":"5.7","1":"5.7","script_version":"1.3","2":"1.3","version_comment":"Improved algorithm, that can also detect mixed indentation (like the one used in vim source code).","3":"Improved algorithm, that can also detect mixed indentation (like the one used in vim source code).","package":"indent_finder-1.3.zip","4":"indent_finder-1.3.zip","src_id":"8979","5":"8979","creation_date":"1216546327","6":"1216546327"},{"0":"513","vim_version":"6.0","1":"6.0","script_version":"1.01","2":"1.01","version_comment":"Act on all files, not only on files with extensions.","3":"Act on all files, not only on files with extensions.","package":"indent_finder.vim","4":"indent_finder.vim","src_id":"2100","5":"2100","creation_date":"1055982886","6":"1055982886"},{"0":"513","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"indent-finder-1.0.tgz","4":"indent-finder-1.0.tgz","src_id":"1556","5":"1556","creation_date":"1040107135","6":"1040107135"}]},"512":{"script_id":"512","0":"512","script_name":"Printer Dialog","1":"Printer Dialog","script_type":"utility","2":"utility","summary":"set print options via dialog","3":"set print options via dialog","description":"This script's intention is to simplify printing of text. It provides\r\na dialog to make many many printer settings before starting to print.\r\nE.g. select:\r\n  - printer device\r\n  - font and its size\r\n  - format of paper\r\n  - colorscheme\r\n  - line-numbering\r\n  - ....\r\n\r\nPressing <Leader>pd opens the Printer Dialog in which you can make your\r\nsettings and start\/cancel printing.\r\n\r\nYou can print either the whole contents of a buffer or a part of it.\r\nIf you want to select a whole buffer for printing, press <Leader>pd.\r\nIf you want to print only a part of a buffer, visually select this part and\r\npress <Leader>pd.\r\n","4":"This script's intention is to simplify printing of text. It provides\r\na dialog to make many many printer settings before starting to print.\r\nE.g. select:\r\n  - printer device\r\n  - font and its size\r\n  - format of paper\r\n  - colorscheme\r\n  - line-numbering\r\n  - ....\r\n\r\nPressing <Leader>pd opens the Printer Dialog in which you can make your\r\nsettings and start\/cancel printing.\r\n\r\nYou can print either the whole contents of a buffer or a part of it.\r\nIf you want to select a whole buffer for printing, press <Leader>pd.\r\nIf you want to print only a part of a buffer, visually select this part and\r\npress <Leader>pd.\r\n","install_details":"Printer Dialog consists out of two files, the script 'prtdialog.vim' and\r\nthe documentation 'prtdialog.txt'.\r\n\r\nTo use this script copy it into your local plugin-directory\r\n  Linux:   ~\/.vim\/plugin\r\n  Windows: c:\\vimfiles\\plugin\r\n\r\nIf you want to add the documentation to VIM's help system, copy\r\n'prtdialog.txt' to your local doc-directory\r\n  Linux:   ~\/.vim\/doc\r\n  Windows: c:\\vimfiles\\doc\r\n\r\nstart VIM and do:\r\n  :helptags ~\/.vim\/doc   (or :helptags c:\\vimfiles\\doc)\r\n\r\nTo view help do:\r\n  :help prtdialog","5":"Printer Dialog consists out of two files, the script 'prtdialog.vim' and\r\nthe documentation 'prtdialog.txt'.\r\n\r\nTo use this script copy it into your local plugin-directory\r\n  Linux:   ~\/.vim\/plugin\r\n  Windows: c:\\vimfiles\\plugin\r\n\r\nIf you want to add the documentation to VIM's help system, copy\r\n'prtdialog.txt' to your local doc-directory\r\n  Linux:   ~\/.vim\/doc\r\n  Windows: c:\\vimfiles\\doc\r\n\r\nstart VIM and do:\r\n  :helptags ~\/.vim\/doc   (or :helptags c:\\vimfiles\\doc)\r\n\r\nTo view help do:\r\n  :help prtdialog","first_name":"Christian","6":"Christian","last_name":"Habermann","7":"Habermann","releases":[{"0":"512","vim_version":"6.0","1":"6.0","script_version":"1.0.0","2":"1.0.0","version_comment":"Initial upload","3":"Initial upload","package":"prtdialog.zip","4":"prtdialog.zip","src_id":"1550","5":"1550","creation_date":"1039687587","6":"1039687587"}]},"511":{"script_id":"511","0":"511","script_name":"casejump.vim","1":"casejump.vim","script_type":"ftplugin","2":"ftplugin","summary":"Jump to cases in C switch statement","3":"Jump to cases in C switch statement","description":"This script allows users to jump to the next or previous case (or\r\ndefault) in a C switch statement by typing ]s or [s, respectively.\r\n","4":"This script allows users to jump to the next or previous case (or\r\ndefault) in a C switch statement by typing ]s or [s, respectively.\r\n","install_details":"Put in your ~\/.vim\/ftplugin\/c directory or rename to c_casejump.vim and\r\nput in your ~\/.vim\/ftplugin directory.\r\n","5":"Put in your ~\/.vim\/ftplugin\/c directory or rename to c_casejump.vim and\r\nput in your ~\/.vim\/ftplugin directory.\r\n","first_name":"Gary","6":"Gary","last_name":"Johnson","7":"Johnson","releases":[{"0":"511","vim_version":"6.0","1":"6.0","script_version":"1.1","2":"1.1","version_comment":"Improved the algorithm for finding the enclosing switch block, following a suggestion by Charles Campbell.","3":"Improved the algorithm for finding the enclosing switch block, following a suggestion by Charles Campbell.","package":"casejump.vim","4":"casejump.vim","src_id":"2530","5":"2530","creation_date":"1070119340","6":"1070119340"},{"0":"511","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"casejump.vim","4":"casejump.vim","src_id":"1548","5":"1548","creation_date":"1039647195","6":"1039647195"}]},"510":{"script_id":"510","0":"510","script_name":"Varrays","1":"Varrays","script_type":"utility","2":"utility","summary":"Arrays lib based on curly  braces names","3":"Arrays lib based on curly  braces names","description":"Yet another arrays lib, this one uses curly  braces names to manage differents elements ...\r\n","4":"Yet another arrays lib, this one uses curly  braces names to manage differents elements ...\r\n","install_details":"just copy it in your macros directory and call it by :\r\n\r\nruntime macros\/varray.vim","5":"just copy it in your macros directory and call it by :\r\n\r\nruntime macros\/varray.vim","first_name":"Marc","6":"Marc","last_name":"Chantreux","7":"Chantreux","releases":[{"0":"510","vim_version":"6.0","1":"6.0","script_version":"0.51","2":"0.51","version_comment":"No more length bug ( no more known bug , in fact). VARRAY_pop example added","3":"No more length bug ( no more known bug , in fact). VARRAY_pop example added","package":"varrays.zip","4":"varrays.zip","src_id":"1597","5":"1597","creation_date":"1041476522","6":"1041476522"}]},"509":{"script_id":"509","0":"509","script_name":"mailsig","1":"mailsig","script_type":"ftplugin","2":"ftplugin","summary":"Script for automatic insertion of selected mail signature","3":"Script for automatic insertion of selected mail signature","description":"This plugin provides a :Sign command which provides a list of signatures in your ~\/.sigs file, and then inserts the one you select at the bottom of your mail message, automatically word-wrapping the first line of the signature.","4":"This plugin provides a :Sign command which provides a list of signatures in your ~\/.sigs file, and then inserts the one you select at the bottom of your mail message, automatically word-wrapping the first line of the signature.","install_details":"See readme.txt.  Requires Python installed on the system (but does not require Vim Python support)","5":"See readme.txt.  Requires Python installed on the system (but does not require Vim Python support)","first_name":"Mike","6":"Mike","last_name":"Dean","7":"Dean","releases":[{"0":"509","vim_version":"6.0","1":"6.0","script_version":"0.5.1","2":"0.5.1","version_comment":"Security fix in getsig","3":"Security fix in getsig","package":"mailsig.tgz","4":"mailsig.tgz","src_id":"1543","5":"1543","creation_date":"1039513527","6":"1039513527"},{"0":"509","vim_version":"6.0","1":"6.0","script_version":"0.5","2":"0.5","version_comment":"Initial upload","3":"Initial upload","package":"mailsig.tgz","4":"mailsig.tgz","src_id":"1540","5":"1540","creation_date":"1039464498","6":"1039464498"}]},"508":{"script_id":"508","0":"508","script_name":"ZoomWin","1":"ZoomWin","script_type":"utility","2":"utility","summary":"Zoom in\/out  of windows (toggle between one window and multi-window)","3":"Zoom in\/out  of windows (toggle between one window and multi-window)","description":"Note: version 23 or later of ZoomWin requires vim 7.2 or later\r\n\r\nUsage:\r\n\r\n    Press <c-w>o : the current window zooms into a full screen\r\n    Press <c-w>o again: the previous set of windows is restored\r\n\r\nFeatures:\r\n\r\nThe idea is to make it easy to zoom into and out of a window.  ZoomWin supports normal windows, and it now also supports scratch-windows, no-name windows, and modified-buffer windows.\r\n\r\n * ZoomWin is a 7.2 plugin (as of v23)\r\n\r\n * Files are made hidden during zoom-in and restored upon zoom-out\r\n\r\n * All windows' file contents will be restored during zoomouts. \r\n\r\n * ZoomWin will clean up any temporary files it generates upon exit.\r\n \r\n * Session files are guaranteed to be unique to each vim session, so multiple vims can use zoom-in\/out without interfering with one another\r\n\r\nA later version may be available at http:\/\/www.drchip.org\/astronaut\/vim\/index.html#ZOOMWIN .\r\n\r\nWhen zooming in, ZoomWin's window is full sized, with no loss of screen space to status lines for other windows, unlike vimscript#1280 (ToggleOnly), for those vims compiled with the +mksession feature.  For those vims without that feature, v21 ZoomWin now supports partial-zoom-in (leaves a status line behind for each window).\r\n\r\nHistory:\r\n\r\nRon Aaron came up with the original ZoomWin and gave permission to have it posted.\r\n","4":"Note: version 23 or later of ZoomWin requires vim 7.2 or later\r\n\r\nUsage:\r\n\r\n    Press <c-w>o : the current window zooms into a full screen\r\n    Press <c-w>o again: the previous set of windows is restored\r\n\r\nFeatures:\r\n\r\nThe idea is to make it easy to zoom into and out of a window.  ZoomWin supports normal windows, and it now also supports scratch-windows, no-name windows, and modified-buffer windows.\r\n\r\n * ZoomWin is a 7.2 plugin (as of v23)\r\n\r\n * Files are made hidden during zoom-in and restored upon zoom-out\r\n\r\n * All windows' file contents will be restored during zoomouts. \r\n\r\n * ZoomWin will clean up any temporary files it generates upon exit.\r\n \r\n * Session files are guaranteed to be unique to each vim session, so multiple vims can use zoom-in\/out without interfering with one another\r\n\r\nA later version may be available at http:\/\/www.drchip.org\/astronaut\/vim\/index.html#ZOOMWIN .\r\n\r\nWhen zooming in, ZoomWin's window is full sized, with no loss of screen space to status lines for other windows, unlike vimscript#1280 (ToggleOnly), for those vims compiled with the +mksession feature.  For those vims without that feature, v21 ZoomWin now supports partial-zoom-in (leaves a status line behind for each window).\r\n\r\nHistory:\r\n\r\nRon Aaron came up with the original ZoomWin and gave permission to have it posted.\r\n","install_details":" The latest version of ZoomWin uses vimball, so with vim 7.1 its particularly easy to install:\r\n  vim ZoomWin.vba.gz\r\n  :so %\r\n  :q\r\nWith 7.0, you'll need to upgrade your vimball plugin first.\r\n","5":" The latest version of ZoomWin uses vimball, so with vim 7.1 its particularly easy to install:\r\n  vim ZoomWin.vba.gz\r\n  :so %\r\n  :q\r\nWith 7.0, you'll need to upgrade your vimball plugin first.\r\n","first_name":"Charles","6":"Charles","last_name":"Campbell","7":"Campbell","releases":[{"0":"508","vim_version":"7.3","1":"7.3","script_version":"24","2":"24","version_comment":"new     : g:ZoomWin_funcref (holds name of function to be called whenever ZoomWin changes state); see :help g:ZoomWin_funcref\r\nimproved: supports saving and restoring of window variables across zooms\r\nbugfix  : saves and restores local options for every window\r\n","3":"new     : g:ZoomWin_funcref (holds name of function to be called whenever ZoomWin changes state); see :help g:ZoomWin_funcref\r\nimproved: supports saving and restoring of window variables across zooms\r\nbugfix  : saves and restores local options for every window\r\n","package":"ZoomWin.vba.gz","4":"ZoomWin.vba.gz","src_id":"18151","5":"18151","creation_date":"1340047922","6":"1340047922"},{"0":"508","vim_version":"7.3","1":"7.3","script_version":"24","2":"24","version_comment":"new     : g:ZoomWin_funcref (holds name of function to be called whenever ZoomWin changes state); see :help g:ZoomWin_funcref\r\nimproved: supports saving and restoring of window variables across zooms\r\nbugfix  : saves and restores local options for every window\r\n","3":"new     : g:ZoomWin_funcref (holds name of function to be called whenever ZoomWin changes state); see :help g:ZoomWin_funcref\r\nimproved: supports saving and restoring of window variables across zooms\r\nbugfix  : saves and restores local options for every window\r\n","package":"ZoomWin.vba.gz","4":"ZoomWin.vba.gz","src_id":"18150","5":"18150","creation_date":"1340047884","6":"1340047884"},{"0":"508","vim_version":"7.0","1":"7.0","script_version":"23","2":"23","version_comment":"ZoomWin has been split into a plugin + autoload portion for faster vim startup.\r\nBug fixes (scrollbind caused the restore to have an incorrect cursor position, retains the search pattern present before zooming, more files than screen rows problem)\r\n","3":"ZoomWin has been split into a plugin + autoload portion for faster vim startup.\r\nBug fixes (scrollbind caused the restore to have an incorrect cursor position, retains the search pattern present before zooming, more files than screen rows problem)\r\n","package":"ZoomWin.vba.gz","4":"ZoomWin.vba.gz","src_id":"9865","5":"9865","creation_date":"1232989420","6":"1232989420"},{"0":"508","vim_version":"7.0","1":"7.0","script_version":"22","2":"22","version_comment":"Uploading ZoomWin in vimball format (makes it easier to install)","3":"Uploading ZoomWin in vimball format (makes it easier to install)","package":"ZoomWin.vba.gz","4":"ZoomWin.vba.gz","src_id":"8072","5":"8072","creation_date":"1198052165","6":"1198052165"},{"0":"508","vim_version":"6.0","1":"6.0","script_version":"22","2":"22","version_comment":"* The internally used \"only\" command was occasionally issuing an \"Already one window\" message, which is now prevented.\r\n* SavePosn() issued an error message when ZoomWin was handling - fixed!\r\n* Saves\/restores yank registers for every zoom\/unzoom.\r\n","3":"* The internally used \"only\" command was occasionally issuing an \"Already one window\" message, which is now prevented.\r\n* SavePosn() issued an error message when ZoomWin was handling - fixed!\r\n* Saves\/restores yank registers for every zoom\/unzoom.\r\n","package":"ZoomWin.vim.gz","4":"ZoomWin.vim.gz","src_id":"5537","5":"5537","creation_date":"1144649870","6":"1144649870"},{"0":"508","vim_version":"6.0","1":"6.0","script_version":"21","2":"21","version_comment":"* For vim version 6.3 or later, but with -mksession, ZoomWin will now do partial zooms\r\n* 6.3 or later vim users can now handle more windows\r\n* Bugfix - sometimes when zooming in, the wrong positioning was restored.  Fixed!\r\n","3":"* For vim version 6.3 or later, but with -mksession, ZoomWin will now do partial zooms\r\n* 6.3 or later vim users can now handle more windows\r\n* Bugfix - sometimes when zooming in, the wrong positioning was restored.  Fixed!\r\n","package":"ZoomWin.vim.gz","4":"ZoomWin.vim.gz","src_id":"4265","5":"4265","creation_date":"1115733503","6":"1115733503"},{"0":"508","vim_version":"6.0","1":"6.0","script_version":"19","2":"19","version_comment":"bugfix - winmanager's events, such as one to reset bufhidden to delete, caused ZoomWin to occasionally restore empty windows.  ZoomWin now works successfully with winmanager.\r\n","3":"bugfix - winmanager's events, such as one to reset bufhidden to delete, caused ZoomWin to occasionally restore empty windows.  ZoomWin now works successfully with winmanager.\r\n","package":"ZoomWin.vim.bz2","4":"ZoomWin.vim.bz2","src_id":"3063","5":"3063","creation_date":"1085564307","6":"1085564307"},{"0":"508","vim_version":"6.0","1":"6.0","script_version":"18","2":"18","version_comment":"bugfix : a Taglist+minibufexplorer+ZoomWin interaction sometimes caused minibufexplorer to create a new window while ZoomWin was busy restoring the windows.  ZoomWin then issued a complaint that it didn't know how to restore the new window.  ZoomWin now temporarily disables events while it is restoring windows.\r\n","3":"bugfix : a Taglist+minibufexplorer+ZoomWin interaction sometimes caused minibufexplorer to create a new window while ZoomWin was busy restoring the windows.  ZoomWin then issued a complaint that it didn't know how to restore the new window.  ZoomWin now temporarily disables events while it is restoring windows.\r\n","package":"ZoomWin.vim.bz2","4":"ZoomWin.vim.bz2","src_id":"3059","5":"3059","creation_date":"1085472289","6":"1085472289"},{"0":"508","vim_version":"6.0","1":"6.0","script_version":"17","2":"17","version_comment":"ZoomWin now has a command (:ZoomWin, of course!).  Works\r\nnicely with taglist:    vim +Tlist +ZoomWin filename\r\nThis cmd starts the taglist window but maximizes the filename's window\r\n","3":"ZoomWin now has a command (:ZoomWin, of course!).  Works\r\nnicely with taglist:    vim +Tlist +ZoomWin filename\r\nThis cmd starts the taglist window but maximizes the filename's window\r\n","package":"ZoomWin.vim.gz","4":"ZoomWin.vim.gz","src_id":"2904","5":"2904","creation_date":"1080897736","6":"1080897736"},{"0":"508","vim_version":"6.0","1":"6.0","script_version":"v16","2":"v16","version_comment":"ZoomWin is both faster and half the size of its v13 and earlier versions.  V16 also allows quickfix windows and handles TagList windows (bh=delete, no buffer listing).\r\n","3":"ZoomWin is both faster and half the size of its v13 and earlier versions.  V16 also allows quickfix windows and handles TagList windows (bh=delete, no buffer listing).\r\n","package":"ZoomWin.vim.gz","4":"ZoomWin.vim.gz","src_id":"2622","5":"2622","creation_date":"1072092146","6":"1072092146"}]},"507":{"script_id":"507","0":"507","script_name":"mercury-old.vim","1":"mercury-old.vim","script_type":"syntax","2":"syntax","summary":"[deprecated] A vim syntax file for the Mercury language.","3":"[deprecated] A vim syntax file for the Mercury language.","description":"------------------------------------------------------------------------\r\nDeprecated, hence renamed to mercury-old.vim from mercury.vim.\r\nPlease use Sebastian Godelet's work.\r\n------------------------------------------------------------------------\r\n\r\nA rather colorful vim syntax file for the Mercury language.","4":"------------------------------------------------------------------------\r\nDeprecated, hence renamed to mercury-old.vim from mercury.vim.\r\nPlease use Sebastian Godelet's work.\r\n------------------------------------------------------------------------\r\n\r\nA rather colorful vim syntax file for the Mercury language.","install_details":"Put it in ~\/.vim\/syntax\/.\r\n\r\nThen use \r\n:setf mercury\r\nin vim or set an autocommand\r\n\r\naugroup filetype\r\n   au BufRead *.m        set ft=mercury\r\naugroup END\r\n\r\nor add something like this to filetype.vim\r\nwhere it tries to determine the filetype of .m files(grep for matlab).\r\n\r\n    if getline(n) =~ '^:-'\r\n      setf mercury\r\n      return\r\n    endif","5":"Put it in ~\/.vim\/syntax\/.\r\n\r\nThen use \r\n:setf mercury\r\nin vim or set an autocommand\r\n\r\naugroup filetype\r\n   au BufRead *.m        set ft=mercury\r\naugroup END\r\n\r\nor add something like this to filetype.vim\r\nwhere it tries to determine the filetype of .m files(grep for matlab).\r\n\r\n    if getline(n) =~ '^:-'\r\n      setf mercury\r\n      return\r\n    endif","first_name":"Andreas","6":"Andreas","last_name":"Hauser","7":"Hauser","releases":[{"0":"507","vim_version":"6.0","1":"6.0","script_version":"0.11","2":"0.11","version_comment":"recognizes more syntax now","3":"recognizes more syntax now","package":"mercury.vim","4":"mercury.vim","src_id":"1760","5":"1760","creation_date":"1046000248","6":"1046000248"},{"0":"507","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"mercury.vim","4":"mercury.vim","src_id":"1526","5":"1526","creation_date":"1038951531","6":"1038951531"}]},"506":{"script_id":"506","0":"506","script_name":"greputil.vim","1":"greputil.vim","script_type":"utility","2":"utility","summary":"simplifies usage of 'grep'","3":"simplifies usage of 'grep'","description":"This script simplifies usage of the :grep-command and the navigation\r\nthrough search results and search history.\r\n\r\nTo start search for the word under the cursor or for the visually\r\nselected text press <Leader>gr. If there is no word under the cursor,\r\nyou will be prompted for a search-string. To be prompted for a\r\nsearch-string anyway pressing <Leader>ga will do it.\r\n\r\nFiles will be searched in the actual directory. The file pattern\r\ncan be defined by a global variable, its default is\r\n\"*.c *.h *.cpp *.hpp\" (yes, this script is primarily for\r\nprogrammers :-) )\r\n\r\nTo show search-results open quickfix-window with :copen.\r\nTo navigate through the occurrences press <F6> or <F7>.\r\nTo bring back results of older or newer search-sessions press\r\n<S-F6> or <S-F7>.","4":"This script simplifies usage of the :grep-command and the navigation\r\nthrough search results and search history.\r\n\r\nTo start search for the word under the cursor or for the visually\r\nselected text press <Leader>gr. If there is no word under the cursor,\r\nyou will be prompted for a search-string. To be prompted for a\r\nsearch-string anyway pressing <Leader>ga will do it.\r\n\r\nFiles will be searched in the actual directory. The file pattern\r\ncan be defined by a global variable, its default is\r\n\"*.c *.h *.cpp *.hpp\" (yes, this script is primarily for\r\nprogrammers :-) )\r\n\r\nTo show search-results open quickfix-window with :copen.\r\nTo navigate through the occurrences press <F6> or <F7>.\r\nTo bring back results of older or newer search-sessions press\r\n<S-F6> or <S-F7>.","install_details":"To use this script copy it into your local plugin-directory\r\n(Unix: ~\/.vim\/plugin). After starting VIM this script is sourced\r\nautomatically.","5":"To use this script copy it into your local plugin-directory\r\n(Unix: ~\/.vim\/plugin). After starting VIM this script is sourced\r\nautomatically.","first_name":"Christian","6":"Christian","last_name":"Habermann","7":"Habermann","releases":[{"0":"506","vim_version":"6.0","1":"6.0","script_version":"1.0.0","2":"1.0.0","version_comment":"Initial upload","3":"Initial upload","package":"greputil.vim","4":"greputil.vim","src_id":"1524","5":"1524","creation_date":"1038825077","6":"1038825077"}]},"505":{"script_id":"505","0":"505","script_name":"python_box.vim","1":"python_box.vim","script_type":"ftplugin","2":"ftplugin","summary":"menu and easy navigation for python files","3":"menu and easy navigation for python files","description":"Parts of this script (as indicated in the code) were taken from python.vim,\r\ncopyright 2001 Mikael Berthe <mikael.berthe@efrei.fr>.\r\n\r\nThe script brings together shortcuts and a menu to syntax check \r\nthe current file (using the compilerscript for python, python.vim),\r\nsome functionality for quickly finding one's way through classes \r\nand functions of a python file (without using exuberant ctags),\r\nsome of the nice functionality from Mikael Berthe's python.vim\r\nas well as menu access to some of Benji Fisher's python_match.vim.\r\n\r\n---------------------------------------------------------------------------\r\nSome hints on how to use\r\n---------------------------------------------------------------------------\r\nThe buffer TOC offers a outline of all Python classes and functions of the\r\ncurrent buffer in a seperate vim window. The cursor position in the TOC window\r\nindicates where you are in the original Window containing the Python code. \r\nPress <F5> again (or q) to quit that window without changing the cursor \r\nposition in the original window (containing the Python code).\r\nThat I find practical when editing a Python file and getting confused \r\nabout where I am.\r\nIf you want to change your position in the Python file:\r\nSet the cursor in the TOC window to the class\/function you want to jump to \r\nthen press <RETURN> to go there.\r\nIf the TOC windows is split pressing <SPACE> will navigate to the\r\nclass\/function but the TOC window will remain open and will keep the focus.\r\nDoubleclicking the left mousebutton will have the same effect.\r\nHowever if the window is not split left doublclicking or pressing <SPACE>\r\nwill have the same effect as pressing <RETURN>.\r\nOnce the TOC-window looses its focus it is closed immediately so to be out of\r\nthe way.\r\n","4":"Parts of this script (as indicated in the code) were taken from python.vim,\r\ncopyright 2001 Mikael Berthe <mikael.berthe@efrei.fr>.\r\n\r\nThe script brings together shortcuts and a menu to syntax check \r\nthe current file (using the compilerscript for python, python.vim),\r\nsome functionality for quickly finding one's way through classes \r\nand functions of a python file (without using exuberant ctags),\r\nsome of the nice functionality from Mikael Berthe's python.vim\r\nas well as menu access to some of Benji Fisher's python_match.vim.\r\n\r\n---------------------------------------------------------------------------\r\nSome hints on how to use\r\n---------------------------------------------------------------------------\r\nThe buffer TOC offers a outline of all Python classes and functions of the\r\ncurrent buffer in a seperate vim window. The cursor position in the TOC window\r\nindicates where you are in the original Window containing the Python code. \r\nPress <F5> again (or q) to quit that window without changing the cursor \r\nposition in the original window (containing the Python code).\r\nThat I find practical when editing a Python file and getting confused \r\nabout where I am.\r\nIf you want to change your position in the Python file:\r\nSet the cursor in the TOC window to the class\/function you want to jump to \r\nthen press <RETURN> to go there.\r\nIf the TOC windows is split pressing <SPACE> will navigate to the\r\nclass\/function but the TOC window will remain open and will keep the focus.\r\nDoubleclicking the left mousebutton will have the same effect.\r\nHowever if the window is not split left doublclicking or pressing <SPACE>\r\nwill have the same effect as pressing <RETURN>.\r\nOnce the TOC-window looses its focus it is closed immediately so to be out of\r\nthe way.\r\n","install_details":"just source or put in ftplugin directory.\r\n\r\nPlease note that this script needs the python compilerscript \"python.vim\" as well as \"python_match.vim\" by Benji Fisher. Both are to be found here among the uploaded scripts. The former should be put in the compiler script directory, the latter should be sourced or placed in the ftplugin directory. ","5":"just source or put in ftplugin directory.\r\n\r\nPlease note that this script needs the python compilerscript \"python.vim\" as well as \"python_match.vim\" by Benji Fisher. Both are to be found here among the uploaded scripts. The former should be put in the compiler script directory, the latter should be sourced or placed in the ftplugin directory. ","first_name":"Christoph","6":"Christoph","last_name":"Herzog","7":"Herzog","releases":[{"0":"505","vim_version":"6.0","1":"6.0","script_version":"0.5","2":"0.5","version_comment":"Some syntax highlighting was added for the outlinebuffer. I think it improves readability here as well.\r\n\r\nThe outlinebuffer was not always reliably removed when it lost the focus etc. Hopefully this is now fixed.","3":"Some syntax highlighting was added for the outlinebuffer. I think it improves readability here as well.\r\n\r\nThe outlinebuffer was not always reliably removed when it lost the focus etc. Hopefully this is now fixed.","package":"python_box.vim","4":"python_box.vim","src_id":"1688","5":"1688","creation_date":"1044108211","6":"1044108211"},{"0":"505","vim_version":"6.0","1":"6.0","script_version":"0.4","2":"0.4","version_comment":"Initial upload","3":"Initial upload","package":"python_box.vim","4":"python_box.vim","src_id":"1517","5":"1517","creation_date":"1038671683","6":"1038671683"}]},"504":{"script_id":"504","0":"504","script_name":"oz.vim","1":"oz.vim","script_type":"syntax","2":"syntax","summary":"Syntax file for the Mozart\/Oz language.","3":"Syntax file for the Mozart\/Oz language.","description":"Syntax file for the Mozart\/Oz language (http:\/\/www.mozart-oz.org).","4":"Syntax file for the Mozart\/Oz language (http:\/\/www.mozart-oz.org).","install_details":"","5":"","first_name":"Michael","6":"Michael","last_name":"Neumann","7":"Neumann","releases":[{"0":"504","vim_version":"6.0","1":"6.0","script_version":"1.3","2":"1.3","version_comment":"removed set oz_emacs_colors","3":"removed set oz_emacs_colors","package":"oz.vim","4":"oz.vim","src_id":"1507","5":"1507","creation_date":"1038549379","6":"1038549379"},{"0":"504","vim_version":"6.0","1":"6.0","script_version":"1.2","2":"1.2","version_comment":"Initial upload","3":"Initial upload","package":"oz.vim","4":"oz.vim","src_id":"1506","5":"1506","creation_date":"1038548611","6":"1038548611"}]},"503":{"script_id":"503","0":"503","script_name":"Macromedia Director Lingo Syntax","1":"Macromedia Director Lingo Syntax","script_type":"syntax","2":"syntax","summary":"Macromedia Director Lingo Syntax Highlighting","3":"Macromedia Director Lingo Syntax Highlighting","description":"This syntax script is for the programming language Lingo used in Macromedia's Director. The syntax highlighting colors have been changed to match those used by Director's script editor.","4":"This syntax script is for the programming language Lingo used in Macromedia's Director. The syntax highlighting colors have been changed to match those used by Director's script editor.","install_details":"","5":"","first_name":"Robert","6":"Robert","last_name":"Robbins","7":"Robbins","releases":[{"0":"503","vim_version":"5.7","1":"5.7","script_version":"1","2":"1","version_comment":"Initial upload","3":"Initial upload","package":"lingo.vim","4":"lingo.vim","src_id":"1501","5":"1501","creation_date":"1038484138","6":"1038484138"}]},"502":{"script_id":"502","0":"502","script_name":"transvim.vim","1":"transvim.vim","script_type":"utility","2":"utility","summary":"translate a phrase by looking up in a dictionary","3":"translate a phrase by looking up in a dictionary","description":"This script looks up a word\/phrase in a dictionary.\r\nUser can press key-shortcuts to translate word under cursor, visually selected \r\ntext or to be asked for a word.\r\n\r\nSearch-results are viewed in the same window in which searching\r\nwas started. To close a view, press 'q' - TransVim will then\r\nswitch back to the buffer comming from.\r\n\r\nThere are several possibilities to start a translation:\r\n  1) move cursor over word to be translated and press <Leader>tr\r\n  2) visually select word to be translated and press <Leader>tr\r\n  3) press <Leader>ta to be prompted for a word\r\nMemory aid: tr = (T)(R)anslate, ta = (T)ranslate (A)sk for word\r\n\r\nBy default <Leader> is \\, so press \\tr, \\ta to start  translation.\r\n\r\nIn order to prevent tremendous huge search-results, the search-string must be at\r\nleast 3 characters long (min. length is configurable).","4":"This script looks up a word\/phrase in a dictionary.\r\nUser can press key-shortcuts to translate word under cursor, visually selected \r\ntext or to be asked for a word.\r\n\r\nSearch-results are viewed in the same window in which searching\r\nwas started. To close a view, press 'q' - TransVim will then\r\nswitch back to the buffer comming from.\r\n\r\nThere are several possibilities to start a translation:\r\n  1) move cursor over word to be translated and press <Leader>tr\r\n  2) visually select word to be translated and press <Leader>tr\r\n  3) press <Leader>ta to be prompted for a word\r\nMemory aid: tr = (T)(R)anslate, ta = (T)ranslate (A)sk for word\r\n\r\nBy default <Leader> is \\, so press \\tr, \\ta to start  translation.\r\n\r\nIn order to prevent tremendous huge search-results, the search-string must be at\r\nleast 3 characters long (min. length is configurable).","install_details":"Copy this script into your local plugin directory (~\/.vim\/plugin\/).\r\n\r\nSet 'g:trv_dictionary' in .vimrc to a plain-ASCII dictionary of your choice \r\n(not included, see script header for further info)\r\n  e.g.: let g:trv_dictionary=\"~\/.vim\/dictionary\/ger-eng.txt\"\r\n\r\n'grep' is used for searching, so you need it too.","5":"Copy this script into your local plugin directory (~\/.vim\/plugin\/).\r\n\r\nSet 'g:trv_dictionary' in .vimrc to a plain-ASCII dictionary of your choice \r\n(not included, see script header for further info)\r\n  e.g.: let g:trv_dictionary=\"~\/.vim\/dictionary\/ger-eng.txt\"\r\n\r\n'grep' is used for searching, so you need it too.","first_name":"Christian","6":"Christian","last_name":"Habermann","7":"Habermann","releases":[{"0":"502","vim_version":"6.0","1":"6.0","script_version":"1.0.1","2":"1.0.1","version_comment":"Bug-fix: Removed mapping of <ESC> to close view of results. In\nconsole version of VIM this mapping leaded to close view\nafter pressing any cursor key - not only after <ESC>.\nNow use 'q' instead of <ESC>.","3":"Bug-fix: Removed mapping of <ESC> to close view of results. In\nconsole version of VIM this mapping leaded to close view\nafter pressing any cursor key - not only after <ESC>.\nNow use 'q' instead of <ESC>.","package":"transvim.vim","4":"transvim.vim","src_id":"1535","5":"1535","creation_date":"1039312250","6":"1039312250"},{"0":"502","vim_version":"6.0","1":"6.0","script_version":"1.0.0","2":"1.0.0","version_comment":"Initial upload","3":"Initial upload","package":"transvim.vim","4":"transvim.vim","src_id":"1499","5":"1499","creation_date":"1038478457","6":"1038478457"}]},"501":{"script_id":"501","0":"501","script_name":"OO code completion","1":"OO code completion","script_type":"utility","2":"utility","summary":"Gives list of methods for the identifier under the cursor for OO languages.","3":"Gives list of methods for the identifier under the cursor for OO languages.","description":"NOTE:as of  june 17, 2003, this script is no more developped due to lack of time\/lack of certain features i miss in ctags. i'll take patches to improve it however, and i have a much more ambitious version (with limited lex\/yacc parsing in ruby via racc) on my hard-drive, any contribution is appreciated.\r\ni don't consider it dead, but in hibernation (especially for the ctags features).\r\n\r\nREQUIRES RUBY.\r\nThis plugin will provide functions to get \"code completion\" in vim.\r\nit will list all methods for the identifier under the cursor if you call :PossibleFunctions.\r\nwhen you start typing a method, it will tell you which methods of the relevant class start by what you typed if you call :PossibleCompletions.\r\nit works by using gd and ctags to get the class of the relevant object, and ctags to get the list of functions for this object.\r\nNOTE: this includes inheritance! functions of the class and the parent classes are listed.\r\nnormally also only public member functions are listed.\r\nThis plugin requires tags to be generated with certain parameters (it\r\n needs information about inheritance and access of members).\r\n You can use the GenerateTags command to generate tags for the current directory.\r\n\r\nFor now this plugin only supports Java and C++. It should only support OO languages, though I guess it could be used for C structs maybe.","4":"NOTE:as of  june 17, 2003, this script is no more developped due to lack of time\/lack of certain features i miss in ctags. i'll take patches to improve it however, and i have a much more ambitious version (with limited lex\/yacc parsing in ruby via racc) on my hard-drive, any contribution is appreciated.\r\ni don't consider it dead, but in hibernation (especially for the ctags features).\r\n\r\nREQUIRES RUBY.\r\nThis plugin will provide functions to get \"code completion\" in vim.\r\nit will list all methods for the identifier under the cursor if you call :PossibleFunctions.\r\nwhen you start typing a method, it will tell you which methods of the relevant class start by what you typed if you call :PossibleCompletions.\r\nit works by using gd and ctags to get the class of the relevant object, and ctags to get the list of functions for this object.\r\nNOTE: this includes inheritance! functions of the class and the parent classes are listed.\r\nnormally also only public member functions are listed.\r\nThis plugin requires tags to be generated with certain parameters (it\r\n needs information about inheritance and access of members).\r\n You can use the GenerateTags command to generate tags for the current directory.\r\n\r\nFor now this plugin only supports Java and C++. It should only support OO languages, though I guess it could be used for C structs maybe.","install_details":"For now I'm not providing any key shortcuts. (Ideas?).\r\nSource this plugin or copy it to your ~\/.vim\/plugins, and you have access to the following commands:\r\n:GenerateTags\r\n:PossibleFunctions\r\n:PossibleCompletions\r\n:TypeUnderCursor\r\n\r\nplease check the documentation in the plugin file itself.","5":"For now I'm not providing any key shortcuts. (Ideas?).\r\nSource this plugin or copy it to your ~\/.vim\/plugins, and you have access to the following commands:\r\n:GenerateTags\r\n:PossibleFunctions\r\n:PossibleCompletions\r\n:TypeUnderCursor\r\n\r\nplease check the documentation in the plugin file itself.","first_name":"emmanuel","6":"emmanuel","last_name":"touzery","7":"touzery","releases":[{"0":"501","vim_version":"6.0","1":"6.0","script_version":"0.4","2":"0.4","version_comment":"* new developer: Luc Hermitte\n* support for the 'tags' variable to know where to look for tag files (if you don't have this variable there is a good default)\n* vimL cleanups (no more marks, cleaner code, ...)\n* some speedups","3":"* new developer: Luc Hermitte\n* support for the 'tags' variable to know where to look for tag files (if you don't have this variable there is a good default)\n* vimL cleanups (no more marks, cleaner code, ...)\n* some speedups","package":"oocompletion.vim","4":"oocompletion.vim","src_id":"1536","5":"1536","creation_date":"1039321920","6":"1039321920"},{"0":"501","vim_version":"6.0","1":"6.0","script_version":"0.3","2":"0.3","version_comment":"* multiple inheritance\n* java interfaces","3":"* multiple inheritance\n* java interfaces","package":"oocompletion.vim","4":"oocompletion.vim","src_id":"1493","5":"1493","creation_date":"1038354655","6":"1038354655"},{"0":"501","vim_version":"6.0","1":"6.0","script_version":"0.2","2":"0.2","version_comment":"* Fixes my speed problems with kword (keeps a cache of classes that are not found in the tags file). Now it's instaneous for even very big classes.\n* If you use the default command to generate tags, now it's recursive so that not only files from the current directory are parsed by ctags.\n\nany feedback welcome!","3":"* Fixes my speed problems with kword (keeps a cache of classes that are not found in the tags file). Now it's instaneous for even very big classes.\n* If you use the default command to generate tags, now it's recursive so that not only files from the current directory are parsed by ctags.\n\nany feedback welcome!","package":"oocompletion.vim","4":"oocompletion.vim","src_id":"1488","5":"1488","creation_date":"1038306790","6":"1038306790"},{"0":"501","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"oocompletion.vim","4":"oocompletion.vim","src_id":"1481","5":"1481","creation_date":"1038271709","6":"1038271709"}]},"500":{"script_id":"500","0":"500","script_name":"foldlist","1":"foldlist","script_type":"utility","2":"utility","summary":"Create a fold list to enable hierarchical file navigation.","3":"Create a fold list to enable hierarchical file navigation.","description":"Overview\r\n--------\r\nThis is inspired by the taglist plugin.  The \"Fold List\" plugin \r\nprovides the following features:\r\n                                                                  \r\n1. Opens a vertically split Vim window with a list of folds in \r\n   the current file.\r\n2. Moving through the fold list with the j, k, l, h, moves to the\r\n   associated fold in the file.\r\n3. <CR> jumps between file and fold list.\r\n\r\nUsage\r\n-----\r\nYou can open the foldinst window from a source window by using the \":Flist\"\r\ncommand.\r\n              nnoremap <silent> <F9> :Flist<CR>\r\n                                                                            \r\nAdd the above mapping to your ~\/.vimrc file.\r\n                                                                            \r\nYou can close the taglist window from the taglist window by pressing 'q' or\r\nusing the Vim \":q\" command. \r\n","4":"Overview\r\n--------\r\nThis is inspired by the taglist plugin.  The \"Fold List\" plugin \r\nprovides the following features:\r\n                                                                  \r\n1. Opens a vertically split Vim window with a list of folds in \r\n   the current file.\r\n2. Moving through the fold list with the j, k, l, h, moves to the\r\n   associated fold in the file.\r\n3. <CR> jumps between file and fold list.\r\n\r\nUsage\r\n-----\r\nYou can open the foldinst window from a source window by using the \":Flist\"\r\ncommand.\r\n              nnoremap <silent> <F9> :Flist<CR>\r\n                                                                            \r\nAdd the above mapping to your ~\/.vimrc file.\r\n                                                                            \r\nYou can close the taglist window from the taglist window by pressing 'q' or\r\nusing the Vim \":q\" command. \r\n","install_details":"Installation\r\n------------\r\n1. Copy the foldlist.vim script to the $HOME\/.vim\/plugin directory.  Refer to\r\n   ':help add-plugin', ':help add-global-plugin' and ':help runtimepath' for\r\n   more details about Vim plugins.\r\n2. Restart Vim.\r\n3. You can use the \":Flist\" command to open the foldlist window. \r\n","5":"Installation\r\n------------\r\n1. Copy the foldlist.vim script to the $HOME\/.vim\/plugin directory.  Refer to\r\n   ':help add-plugin', ':help add-global-plugin' and ':help runtimepath' for\r\n   more details about Vim plugins.\r\n2. Restart Vim.\r\n3. You can use the \":Flist\" command to open the foldlist window. \r\n","first_name":"Paul","6":"Paul","last_name":"Wei","7":"Wei","releases":[{"0":"500","vim_version":"6.0","1":"6.0","script_version":"1.0.5","2":"1.0.5","version_comment":"Change to use tab between levels of folds in fold list.\r\nFix to work with C commented folds","3":"Change to use tab between levels of folds in fold list.\r\nFix to work with C commented folds","package":"foldlist.vim","4":"foldlist.vim","src_id":"3689","5":"3689","creation_date":"1102426530","6":"1102426530"},{"0":"500","vim_version":"6.0","1":"6.0","script_version":"1.0.4","2":"1.0.4","version_comment":"Map <cr> in file to return to fold list.","3":"Map <cr> in file to return to fold list.","package":"foldlist.vim","4":"foldlist.vim","src_id":"1502","5":"1502","creation_date":"1038492503","6":"1038492503"},{"0":"500","vim_version":"6.0","1":"6.0","script_version":"1.0.3","2":"1.0.3","version_comment":"Fix jumping to multilevel folds.","3":"Fix jumping to multilevel folds.","package":"foldlist.vim","4":"foldlist.vim","src_id":"1498","5":"1498","creation_date":"1038454387","6":"1038454387"}]},"499":{"script_id":"499","0":"499","script_name":"SpellChecker","1":"SpellChecker","script_type":"utility","2":"utility","summary":"Spell check text including LaTeX documents","3":"Spell check text including LaTeX documents","description":"SpellChecker.vim is a plugin that uses Vim's syntax highlighting facility to help spot spelling errors. The lexicon consists of approximately 53,700 English words, including about 2,700 proper names and 50 acronyms. Three dialects are supported: American (US), British (UK), and Canadian (CA). Misspellings are highlighted as errors, and spellings corresponding to a dialect different from the selected one are highlighted as todo items.\r\n\r\nScreenshot:   http:\/\/www.unb.ca\/chem\/ajit\/macros\/spell.png\r\n\r\nCommands, key mappings and menus are provided for turning spell checking on and off, for moving through the errors with or without dialogs, changing dialects, adding and removing words to the global user and local project dictionaries, for accepting words for the current document only, for modifying all occurrences of a word, and for querying SpellChecker settings. \r\n\r\nSpellChecker was inspired by Charles Campbell's engspchk.  SpellChecker uses several ideas but very little unmodified code from engspchk. Both work with vim's syntax facility. Both highlight misspelled words as errors. Both can be used for source code in selected programming languages where only the comments will be spell-checked. The following description may help you to decide whether to use SpellChecker or engspchk.\r\n\r\nA unique feature of SpellChecker is project-specific dictionaries. These are dictionaries that are additional to all others, including the global user's dictionary. A project-specific dictionary is used only when checking documents that reside in the same directory as that dictionary. For example, such dictionaries can be useful if a document introduces acronyms or abbreviations specific to that document.\r\n\r\nOther features unique to SpellChecker include an interactive mode to step through the errors, user dictionaries that store words with an upper-case letter in a case-sensitive fashion, and a command to save all remaining errors in one step.\r\n\r\nAnother unique feature of SpellChecker is that it highlights spellings corresponding to a dialect different from the one selected. This helps to ensure that the selected dialect has been used consistently throughout a document.  \r\n\r\nSpellChecker loads faster than engspchk because a different and smaller lexicon is used by SpellChecker. The presence of fewer rare words in the lexicon means that spelling errors are less likely to be mistaken for arcane words. For example, if you type \"ort he\" instead of \"or the\", SpellChecker will flag an error whereas engspchk won't because \"ort\" is a rarely-used word (meaning morsel) that is in the engspchk  lexicon. On the other hand, this means that esoteric words may be marked as errors by SpellChecker even though they are perfectly correct. \r\n\r\nAt this time, SpellChecker does not incorporate a scheme to offer alternative spellings. It may later.\r\n","4":"SpellChecker.vim is a plugin that uses Vim's syntax highlighting facility to help spot spelling errors. The lexicon consists of approximately 53,700 English words, including about 2,700 proper names and 50 acronyms. Three dialects are supported: American (US), British (UK), and Canadian (CA). Misspellings are highlighted as errors, and spellings corresponding to a dialect different from the selected one are highlighted as todo items.\r\n\r\nScreenshot:   http:\/\/www.unb.ca\/chem\/ajit\/macros\/spell.png\r\n\r\nCommands, key mappings and menus are provided for turning spell checking on and off, for moving through the errors with or without dialogs, changing dialects, adding and removing words to the global user and local project dictionaries, for accepting words for the current document only, for modifying all occurrences of a word, and for querying SpellChecker settings. \r\n\r\nSpellChecker was inspired by Charles Campbell's engspchk.  SpellChecker uses several ideas but very little unmodified code from engspchk. Both work with vim's syntax facility. Both highlight misspelled words as errors. Both can be used for source code in selected programming languages where only the comments will be spell-checked. The following description may help you to decide whether to use SpellChecker or engspchk.\r\n\r\nA unique feature of SpellChecker is project-specific dictionaries. These are dictionaries that are additional to all others, including the global user's dictionary. A project-specific dictionary is used only when checking documents that reside in the same directory as that dictionary. For example, such dictionaries can be useful if a document introduces acronyms or abbreviations specific to that document.\r\n\r\nOther features unique to SpellChecker include an interactive mode to step through the errors, user dictionaries that store words with an upper-case letter in a case-sensitive fashion, and a command to save all remaining errors in one step.\r\n\r\nAnother unique feature of SpellChecker is that it highlights spellings corresponding to a dialect different from the one selected. This helps to ensure that the selected dialect has been used consistently throughout a document.  \r\n\r\nSpellChecker loads faster than engspchk because a different and smaller lexicon is used by SpellChecker. The presence of fewer rare words in the lexicon means that spelling errors are less likely to be mistaken for arcane words. For example, if you type \"ort he\" instead of \"or the\", SpellChecker will flag an error whereas engspchk won't because \"ort\" is a rarely-used word (meaning morsel) that is in the engspchk  lexicon. On the other hand, this means that esoteric words may be marked as errors by SpellChecker even though they are perfectly correct. \r\n\r\nAt this time, SpellChecker does not incorporate a scheme to offer alternative spellings. It may later.\r\n","install_details":"1. Unzip Spellchecker.zip, preserving directory structure, into either $HOME\/.vim for unix or $HOME\\vimfiles for MSWindows. Make sure that Spellchecker.vim is in the plugin subdirectory, the english.vim, english_dialects.vim, and english_special.vim files are in the dict subdirectory, and spellchecker.txt is in the doc subdirectory of $HOME\/.vim or $HOME\\vimfiles as the case may be. Do \":help add-plugin\", \":help add-global-plugin\" and \":help runtimepath\" for more details about Vim plugins. \r\n\r\n2. Do\r\n:helptags ~\/.vim\/doc (for unix)\r\nor\r\n:helptags ~\\vimfiles\\doc (for MSWindows)\r\nto rebuild the tags file. Do \":help add-local-help\" for more details.\r\n\r\n3. Restart vim\r\n\r\n4. Do :help SpellChecker or otherwise read spellchecker.txt to learn about usage and customization.\r\n","5":"1. Unzip Spellchecker.zip, preserving directory structure, into either $HOME\/.vim for unix or $HOME\\vimfiles for MSWindows. Make sure that Spellchecker.vim is in the plugin subdirectory, the english.vim, english_dialects.vim, and english_special.vim files are in the dict subdirectory, and spellchecker.txt is in the doc subdirectory of $HOME\/.vim or $HOME\\vimfiles as the case may be. Do \":help add-plugin\", \":help add-global-plugin\" and \":help runtimepath\" for more details about Vim plugins. \r\n\r\n2. Do\r\n:helptags ~\/.vim\/doc (for unix)\r\nor\r\n:helptags ~\\vimfiles\\doc (for MSWindows)\r\nto rebuild the tags file. Do \":help add-local-help\" for more details.\r\n\r\n3. Restart vim\r\n\r\n4. Do :help SpellChecker or otherwise read spellchecker.txt to learn about usage and customization.\r\n","first_name":"Ajit","6":"Ajit","last_name":"Thakkar","7":"Thakkar","releases":[{"0":"499","vim_version":"6.0","1":"6.0","script_version":"1.8","2":"1.8","version_comment":"Added popup menu for use with set mousemodel=popup_setpos","3":"Added popup menu for use with set mousemodel=popup_setpos","package":"spellchecker18.zip","4":"spellchecker18.zip","src_id":"1789","5":"1789","creation_date":"1047270509","6":"1047270509"},{"0":"499","vim_version":"6.0","1":"6.0","script_version":"1.7","2":"1.7","version_comment":"Added :SPM (\\sm) command to modify all occurrences of word under cursor. Bug Fix: Allow for spaces in run-time path.","3":"Added :SPM (\\sm) command to modify all occurrences of word under cursor. Bug Fix: Allow for spaces in run-time path.","package":"spellchecker17.zip","4":"spellchecker17.zip","src_id":"1746","5":"1746","creation_date":"1045457933","6":"1045457933"}]},"498":{"script_id":"498","0":"498","script_name":"sql.vim","1":"sql.vim","script_type":"syntax","2":"syntax","summary":"Syntax file for Sybase SQL Anywhere","3":"Syntax file for Sybase SQL Anywhere","description":"Syntax file for Sybase SQL Anywhere (Adaptive Server Anywhere)\r\n\r\nAttention Vim7 users\r\n----------------------------\r\nThis file has been renamed to sqlanywhere.vim and version 9.0.2 is included with Vim 7.0.\r\nA new file syntax\\sql.vim has been created which manages the appropriate loading of any sql syntax file.  See :h sql.txt for more details.\r\n\r\nSupports\r\n------------\r\n- keywords\r\n- internal functions\r\n- internal stored procedures, \r\n- TSQL compatability stored procedures\r\n- external stored procedures\/functions, \r\n- web services (HTML and XML support)\r\n- all database options\r\n- operators\r\n- datatypes\r\n- statements \r\n- comments\r\n\r\nAssuming you are editing a .sql file (Vim sets the filetype to be SQL), then by default Vim assumes Oracle syntax.\r\n\r\nThis syntax file works in conjunction with ftplugin\/sql.vim, indent\/sql.vim and syntax\/sql.vim to load the correct SQL dialect.\r\n\r\nTo change from Oracle syntax to a different SQL dialect you can initiate this by running:\r\n:SQLSetType sqlanywhere.vim\r\nor\r\n:SQLSetType <tab key> to cycle through all supported SQL dialects.\r\nor\r\n:SQLSetType sqla<tab key> to cycle through all supported SQL dialects starting with \"sqla\".\r\n\r\n\r\nOr to change Vim's default Oracle dialect to SQL Anywhere you can put the following in your .vimrc:\r\n    let g:sql_type_default = 'sqlanywhere'\r\n\r\nTo read more on these options see:\r\n:h sql.txt\r\n\r\n","4":"Syntax file for Sybase SQL Anywhere (Adaptive Server Anywhere)\r\n\r\nAttention Vim7 users\r\n----------------------------\r\nThis file has been renamed to sqlanywhere.vim and version 9.0.2 is included with Vim 7.0.\r\nA new file syntax\\sql.vim has been created which manages the appropriate loading of any sql syntax file.  See :h sql.txt for more details.\r\n\r\nSupports\r\n------------\r\n- keywords\r\n- internal functions\r\n- internal stored procedures, \r\n- TSQL compatability stored procedures\r\n- external stored procedures\/functions, \r\n- web services (HTML and XML support)\r\n- all database options\r\n- operators\r\n- datatypes\r\n- statements \r\n- comments\r\n\r\nAssuming you are editing a .sql file (Vim sets the filetype to be SQL), then by default Vim assumes Oracle syntax.\r\n\r\nThis syntax file works in conjunction with ftplugin\/sql.vim, indent\/sql.vim and syntax\/sql.vim to load the correct SQL dialect.\r\n\r\nTo change from Oracle syntax to a different SQL dialect you can initiate this by running:\r\n:SQLSetType sqlanywhere.vim\r\nor\r\n:SQLSetType <tab key> to cycle through all supported SQL dialects.\r\nor\r\n:SQLSetType sqla<tab key> to cycle through all supported SQL dialects starting with \"sqla\".\r\n\r\n\r\nOr to change Vim's default Oracle dialect to SQL Anywhere you can put the following in your .vimrc:\r\n    let g:sql_type_default = 'sqlanywhere'\r\n\r\nTo read more on these options see:\r\n:h sql.txt\r\n\r\n","install_details":"Put <sql.vim> into your .vim\/syntax or vimfiles\/syntax directory ","5":"Put <sql.vim> into your .vim\/syntax or vimfiles\/syntax directory ","first_name":"David","6":"David","last_name":"Fishburn","7":"Fishburn","releases":[{"0":"498","vim_version":"7.0","1":"7.0","script_version":"12.0.1","2":"12.0.1","version_comment":"Latest updates for SQL Anywhere version 12.0.1 including spatial data","3":"Latest updates for SQL Anywhere version 12.0.1 including spatial data","package":"sqlanywhere.vim","4":"sqlanywhere.vim","src_id":"17303","5":"17303","creation_date":"1327330098","6":"1327330098"},{"0":"498","vim_version":"7.0","1":"7.0","script_version":"11.0.1","2":"11.0.1","version_comment":"Latest updates for SQL Anywhere version 11.0.1","3":"Latest updates for SQL Anywhere version 11.0.1","package":"sqlanywhere.vim","4":"sqlanywhere.vim","src_id":"10211","5":"10211","creation_date":"1237148950","6":"1237148950"},{"0":"498","vim_version":"7.0","1":"7.0","script_version":"10.0.1","2":"10.0.1","version_comment":"Updated to 10.0.1 to keywords.  If you are using Vim 7, the file was changed to syntax\/sqlanywhere.vim.  If you are using Vim 6, you can rename the file to syntax\/sql.vim.","3":"Updated to 10.0.1 to keywords.  If you are using Vim 7, the file was changed to syntax\/sqlanywhere.vim.  If you are using Vim 6, you can rename the file to syntax\/sql.vim.","package":"sqlanywhere.vim","4":"sqlanywhere.vim","src_id":"8194","5":"8194","creation_date":"1201600842","6":"1201600842"},{"0":"498","vim_version":"6.0","1":"6.0","script_version":"9.0.2","2":"9.0.2","version_comment":"Support for Adaptive Server Anywhere 9.0.2","3":"Support for Adaptive Server Anywhere 9.0.2","package":"sql.vim","4":"sql.vim","src_id":"3780","5":"3780","creation_date":"1106074694","6":"1106074694"},{"0":"498","vim_version":"6.0","1":"6.0","script_version":"9.0.1","2":"9.0.1","version_comment":"Latest changes for the 9.0.1 release","3":"Latest changes for the 9.0.1 release","package":"sql.vim","4":"sql.vim","src_id":"2738","5":"2738","creation_date":"1076416243","6":"1076416243"}]},"497":{"script_id":"497","0":"497","script_name":"waimea.vim","1":"waimea.vim","script_type":"syntax","2":"syntax","summary":"Highlighting for Waimea config files","3":"Highlighting for Waimea config files","description":"Highlight config files for the Waimea window manager (http:\/\/www.waimea.org).  You can see a screenshot at (http:\/\/students.cs.byu.edu\/~mtb6\/waimea_config.png).  It is not finished.  I have the the menu files and style files highlighted.  They aren't that great yet, but since there is a complete lack of highlighting files for Waimea config, I thought I would release this really early.  Enjoy!  And please feel free to send me feedback.\r\n\r\nNOTE!\r\nI was contacted by the author of waimea, and he informed me that style and menu files will be changing in the near future, so I have not put any more effort into this syntax file.  If there is a demand to make it complete for waimea 0.4.0 then let me know and I will certainly do so.","4":"Highlight config files for the Waimea window manager (http:\/\/www.waimea.org).  You can see a screenshot at (http:\/\/students.cs.byu.edu\/~mtb6\/waimea_config.png).  It is not finished.  I have the the menu files and style files highlighted.  They aren't that great yet, but since there is a complete lack of highlighting files for Waimea config, I thought I would release this really early.  Enjoy!  And please feel free to send me feedback.\r\n\r\nNOTE!\r\nI was contacted by the author of waimea, and he informed me that style and menu files will be changing in the near future, so I have not put any more effort into this syntax file.  If there is a demand to make it complete for waimea 0.4.0 then let me know and I will certainly do so.","install_details":"For now, just put it in your ~\/.vim\/syntax directory.  You can then either edit ~\/.vim\/filetype.vim or add an autocommand to your .vimrc to source the file when opening a waimea config file.  Or you can type \":set ft=waimea\" manually when after you open the file.  I will make things nicer, when it is more complete.","5":"For now, just put it in your ~\/.vim\/syntax directory.  You can then either edit ~\/.vim\/filetype.vim or add an autocommand to your .vimrc to source the file when opening a waimea config file.  Or you can type \":set ft=waimea\" manually when after you open the file.  I will make things nicer, when it is more complete.","first_name":"Michael","6":"Michael","last_name":"Brailsford","7":"Brailsford","releases":[{"0":"497","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"waimea.vim","4":"waimea.vim","src_id":"1465","5":"1465","creation_date":"1038192433","6":"1038192433"}]},"496":{"script_id":"496","0":"496","script_name":"poser.vim","1":"poser.vim","script_type":"syntax","2":"syntax","summary":"A syntax file for Poser 3-D library and scene files and WaveFront OBJects","3":"A syntax file for Poser 3-D library and scene files and WaveFront OBJects","description":"This is a syntax file for use with CuriousLabs' Poser Library and Scene files, cr2, pp2, pz2, pz3, hr2, lt2, cm2, fc2 and hd2. Version 1.05 also supports Wavefront OBJect files due to added support for customGeom.","4":"This is a syntax file for use with CuriousLabs' Poser Library and Scene files, cr2, pp2, pz2, pz3, hr2, lt2, cm2, fc2 and hd2. Version 1.05 also supports Wavefront OBJect files due to added support for customGeom.","install_details":"Just add this to your gvim syntax folder. You can then activate it with :cal SetSyn(\"poser\")\r\n\r\nYou can also edit $VIMRUNTIME\/menu.vim to add it to the syntax menu, down in the P section most likely, and add a SynAu command for it in $VIMRUNTIME\/syntax\/synload.vim. You may also want to edit $VIMRUNTIME\/filetype.vim to set it to automatically load with cr2, pp2, pz2, pz3, hr2, lt2, cm2, fc2, and hd2 files. Depending on how much programming you don't do and how much manual editing of Wavefront OBJect files you do do, you could also add .obj in there.","5":"Just add this to your gvim syntax folder. You can then activate it with :cal SetSyn(\"poser\")\r\n\r\nYou can also edit $VIMRUNTIME\/menu.vim to add it to the syntax menu, down in the P section most likely, and add a SynAu command for it in $VIMRUNTIME\/syntax\/synload.vim. You may also want to edit $VIMRUNTIME\/filetype.vim to set it to automatically load with cr2, pp2, pz2, pz3, hr2, lt2, cm2, fc2, and hd2 files. Depending on how much programming you don't do and how much manual editing of Wavefront OBJect files you do do, you could also add .obj in there.","first_name":"Sean","6":"Sean","last_name":"Cannon","7":"Cannon","releases":[{"0":"496","vim_version":"7.0","1":"7.0","script_version":"2","2":"2","version_comment":"I suppose after 14 years this needs a slight update, huh?","3":"I suppose after 14 years this needs a slight update, huh?","package":"poser.vim","4":"poser.vim","src_id":"23994","5":"23994","creation_date":"1454820253","6":"1454820253"},{"0":"496","vim_version":"5.7","1":"5.7","script_version":"1.09","2":"1.09","version_comment":"conformingTarget keyword (poser) added *sigh*","3":"conformingTarget keyword (poser) added *sigh*","package":"poser.vim","4":"poser.vim","src_id":"1476","5":"1476","creation_date":"1038211551","6":"1038211551"},{"0":"496","vim_version":"5.7","1":"5.7","script_version":"1.08","2":"1.08","version_comment":"I'd missed the 's' OBJect keyword.","3":"I'd missed the 's' OBJect keyword.","package":"poser.vim","4":"poser.vim","src_id":"1475","5":"1475","creation_date":"1038210528","6":"1038210528"},{"0":"496","vim_version":"5.7","1":"5.7","script_version":"1.07","2":"1.07","version_comment":"...and the mtllib OBJect keyword...","3":"...and the mtllib OBJect keyword...","package":"poser.vim","4":"poser.vim","src_id":"1474","5":"1474","creation_date":"1038210307","6":"1038210307"},{"0":"496","vim_version":"5.7","1":"5.7","script_version":"1.06","2":"1.06","version_comment":"What the hell. Since I'm supporting Wavefront OBJects, I added the WaveFront OBJect comment highlighting.","3":"What the hell. Since I'm supporting Wavefront OBJects, I added the WaveFront OBJect comment highlighting.","package":"poser.vim","4":"poser.vim","src_id":"1473","5":"1473","creation_date":"1038209264","6":"1038209264"},{"0":"496","vim_version":"5.7","1":"5.7","script_version":"1.05","2":"1.05","version_comment":"Added support for customGeom (can't believe Imissed that)","3":"Added support for customGeom (can't believe Imissed that)","package":"poser.vim","4":"poser.vim","src_id":"1472","5":"1472","creation_date":"1038208398","6":"1038208398"},{"0":"496","vim_version":"5.7","1":"5.7","script_version":"1.04","2":"1.04","version_comment":"Added missed *Bulge functions","3":"Added missed *Bulge functions","package":"poser.vim","4":"poser.vim","src_id":"1471","5":"1471","creation_date":"1038207669","6":"1038207669"},{"0":"496","vim_version":"5.7","1":"5.7","script_version":"1.03","2":"1.03","version_comment":"Small cleanups, fixed MT stuff, changed constructor (addChild, weld, valueOpDeltaAdd, sphereMatsRaw) style to bold green since they don't have {}","3":"Small cleanups, fixed MT stuff, changed constructor (addChild, weld, valueOpDeltaAdd, sphereMatsRaw) style to bold green since they don't have {}","package":"poser.vim","4":"poser.vim","src_id":"1470","5":"1470","creation_date":"1038207362","6":"1038207362"},{"0":"496","vim_version":"5.7","1":"5.7","script_version":"1.02","2":"1.02","version_comment":"Added NULL constant, corrected -e exponents.","3":"Added NULL constant, corrected -e exponents.","package":"poser.vim","4":"poser.vim","src_id":"1468","5":"1468","creation_date":"1038194874","6":"1038194874"},{"0":"496","vim_version":"5.7","1":"5.7","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"poser.vim","4":"poser.vim","src_id":"1464","5":"1464","creation_date":"1038188992","6":"1038188992"}]},"495":{"script_id":"495","0":"495","script_name":"sql.vim","1":"sql.vim","script_type":"indent","2":"indent","summary":"SQL indent file for Sybase SQL Anywhere and Oracle","3":"SQL indent file for Sybase SQL Anywhere and Oracle","description":"This indent file was created for Sybase SQL Anywhere using the Watcom SQL syntax.\r\nIt has also been tested against Oracle packages.\r\n\r\nThis will not work for Sybase ASE and Microsoft SQL Server which use Transact-SQL syntax.\r\n\r\nindent\/sqlanywere.vim version 1.5 is included in the Vim 7.3 release.\r\nindent\/sqlanywere.vim version 3.0 is included in the Vim 7.3 patches.\r\n\r\nIn preparation for Vim 7, this file has been renamed to sqlanywhere.vim, but will continue to work with Vim 6.  Simply rename it to sql.vim to keep the default behaviour.\r\n\r\nSupports a wide variety of syntax including standard the standards: IF, LOOP, CASE.\r\nBut it will also support less used syntax like the EXCEPTION statement.\r\n\r\n\r\n","4":"This indent file was created for Sybase SQL Anywhere using the Watcom SQL syntax.\r\nIt has also been tested against Oracle packages.\r\n\r\nThis will not work for Sybase ASE and Microsoft SQL Server which use Transact-SQL syntax.\r\n\r\nindent\/sqlanywere.vim version 1.5 is included in the Vim 7.3 release.\r\nindent\/sqlanywere.vim version 3.0 is included in the Vim 7.3 patches.\r\n\r\nIn preparation for Vim 7, this file has been renamed to sqlanywhere.vim, but will continue to work with Vim 6.  Simply rename it to sql.vim to keep the default behaviour.\r\n\r\nSupports a wide variety of syntax including standard the standards: IF, LOOP, CASE.\r\nBut it will also support less used syntax like the EXCEPTION statement.\r\n\r\n\r\n","install_details":"Put <sqlanywhere.vim> into your .vim\/indent or vimfiles\/indent directory ","5":"Put <sqlanywhere.vim> into your .vim\/indent or vimfiles\/indent directory ","first_name":"David","6":"David","last_name":"Fishburn","7":"Fishburn","releases":[{"0":"495","vim_version":"7.0","1":"7.0","script_version":"4.0","2":"4.0","version_comment":"Added b:undo_indent support.","3":"Added b:undo_indent support.","package":"sqlanywhere.vim","4":"sqlanywhere.vim","src_id":"27779","5":"27779","creation_date":"1634033925","6":"1634033925"},{"0":"495","vim_version":"7.0","1":"7.0","script_version":"3.0","2":"3.0","version_comment":"Added a vim option cpo check.\r\n\r\nAdded the FOR keyword to SQLBlockStart to handle (Alec Tica):\r\n    for i in 1..100 loop\r\n      |<-- I expect to have indentation here\r\n    end loop;\r\n","3":"Added a vim option cpo check.\r\n\r\nAdded the FOR keyword to SQLBlockStart to handle (Alec Tica):\r\n    for i in 1..100 loop\r\n      |<-- I expect to have indentation here\r\n    end loop;\r\n","package":"sqlanywhere.vim","4":"sqlanywhere.vim","src_id":"19130","5":"19130","creation_date":"1354896813","6":"1354896813"},{"0":"495","vim_version":"6.0","1":"6.0","script_version":"1.5","2":"1.5","version_comment":"In Vim 7, OMNI SQL completion (:h sql-completion) allows you to complete SQL even when not editing a SQL file.  Most programming languages allow you to use SQL (.Net, Java, PHP, Ruby, Javascript, ...) you can set the filetype to SQL temporarily and flip it back (once).  After that, you can use OMNI SQL completion.  Doing this quick filetype switch while using the SQL Anywhere indent script reported an error indicating IsLineComment function already exists.  This corrects the problem by making these routines script functions instead of public.","3":"In Vim 7, OMNI SQL completion (:h sql-completion) allows you to complete SQL even when not editing a SQL file.  Most programming languages allow you to use SQL (.Net, Java, PHP, Ruby, Javascript, ...) you can set the filetype to SQL temporarily and flip it back (once).  After that, you can use OMNI SQL completion.  Doing this quick filetype switch while using the SQL Anywhere indent script reported an error indicating IsLineComment function already exists.  This corrects the problem by making these routines script functions instead of public.","package":"sqlanywhere.vim","4":"sqlanywhere.vim","src_id":"6930","5":"6930","creation_date":"1175456300","6":"1175456300"},{"0":"495","vim_version":"6.0","1":"6.0","script_version":"1.4","2":"1.4","version_comment":"Comments are handled much better in this version.  Also the indent level is determined using the shiftwidth setting.  In version 1.3, it used the indent level of the statement above which is generally not what you want.","3":"Comments are handled much better in this version.  Also the indent level is determined using the shiftwidth setting.  In version 1.3, it used the indent level of the statement above which is generally not what you want.","package":"sqlanywhere.vim","4":"sqlanywhere.vim","src_id":"4585","5":"4585","creation_date":"1126724654","6":"1126724654"},{"0":"495","vim_version":"6.0","1":"6.0","script_version":"1.3","2":"1.3","version_comment":"Extensive work has been done to make this work with Oracle PL\/SQL syntax and Sybase ASA syntax.","3":"Extensive work has been done to make this work with Oracle PL\/SQL syntax and Sybase ASA syntax.","package":"sql.vim","4":"sql.vim","src_id":"3095","5":"3095","creation_date":"1086340721","6":"1086340721"},{"0":"495","vim_version":"6.0","1":"6.0","script_version":"1.1","2":"1.1","version_comment":"Better support for closing ).\r\nCREATE TABLE T1\r\n(\r\n\tid INT\r\n)   - This is indented correctly.\r\n\r\nCREATE FUNCTION f_authenticate(\r\n     IN @user_id INTEGER\r\n    ,IN @password VARCHAR(16)\r\n)   - This is indented correctly.\r\n\r\n\r\n","3":"Better support for closing ).\r\nCREATE TABLE T1\r\n(\r\n\tid INT\r\n)   - This is indented correctly.\r\n\r\nCREATE FUNCTION f_authenticate(\r\n     IN @user_id INTEGER\r\n    ,IN @password VARCHAR(16)\r\n)   - This is indented correctly.\r\n\r\n\r\n","package":"sql.vim","4":"sql.vim","src_id":"2144","5":"2144","creation_date":"1057928960","6":"1057928960"},{"0":"495","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"sql.vim","4":"sql.vim","src_id":"1462","5":"1462","creation_date":"1038164565","6":"1038164565"}]},"494":{"script_id":"494","0":"494","script_name":"ri-browser","1":"ri-browser","script_type":"ftplugin","2":"ftplugin","summary":"Ruby Information at your fingertips","3":"Ruby Information at your fingertips","description":"Interface for browsing ri\/ruby documentation.\r\n\r\nDefines the following commands:\r\n\r\n  :Ri <arg>\r\n      Lookup the given argument.\r\n\r\n  :RiExpand <arg>\r\n      Lookup the given argument but prefix the class\/module name\r\n      when in Ri class buffer[1].\r\n\r\nand the following mappings:\r\n\r\n  <M-i>  Clean prompting for lookup word.\r\n  <M-I>  Prefix class\/module if any before prompting. (ex: Array#)\r\n\r\nLookups can also be done using the word under the cursor (WUC)\r\n\r\n  <M-]>\r\n      Gready expansion of WUC. This will work for both the\r\n      'Array.new', 'Hash#each' and 'Kernel::block_given?' way of\r\n      specifying a method.\r\n\r\n  <M-[>\r\n      Not so gready expansion of WUC but will also prefix the\r\n      class\/module when in a Ri class\/module buffer[1]. This makes\r\n      it possible to lookup 'Array#each' by invoking it with\r\n      the cursor places on 'each' in the 'Array' class buffer. \r\n\r\n[1] A Ri class\/module buffer is a buffer showing all the methods belonging\r\n    to a class or modul. Example: typing ':Ri Hash' followed by enter in\r\n    normal mode with the ri plugin loaded will open the 'Hash' class buffer.\r\n\r\nComes with syntax coloring of the Ri buffer.\r\n\r\nInspired by ri stuff at http:\/\/www.rubygarden.org\/ruby?VimExtensions\r\nCredits to vimscript #90 for much of the lovely code.","4":"Interface for browsing ri\/ruby documentation.\r\n\r\nDefines the following commands:\r\n\r\n  :Ri <arg>\r\n      Lookup the given argument.\r\n\r\n  :RiExpand <arg>\r\n      Lookup the given argument but prefix the class\/module name\r\n      when in Ri class buffer[1].\r\n\r\nand the following mappings:\r\n\r\n  <M-i>  Clean prompting for lookup word.\r\n  <M-I>  Prefix class\/module if any before prompting. (ex: Array#)\r\n\r\nLookups can also be done using the word under the cursor (WUC)\r\n\r\n  <M-]>\r\n      Gready expansion of WUC. This will work for both the\r\n      'Array.new', 'Hash#each' and 'Kernel::block_given?' way of\r\n      specifying a method.\r\n\r\n  <M-[>\r\n      Not so gready expansion of WUC but will also prefix the\r\n      class\/module when in a Ri class\/module buffer[1]. This makes\r\n      it possible to lookup 'Array#each' by invoking it with\r\n      the cursor places on 'each' in the 'Array' class buffer. \r\n\r\n[1] A Ri class\/module buffer is a buffer showing all the methods belonging\r\n    to a class or modul. Example: typing ':Ri Hash' followed by enter in\r\n    normal mode with the ri plugin loaded will open the 'Hash' class buffer.\r\n\r\nComes with syntax coloring of the Ri buffer.\r\n\r\nInspired by ri stuff at http:\/\/www.rubygarden.org\/ruby?VimExtensions\r\nCredits to vimscript #90 for much of the lovely code.","install_details":"Unzip the installation file in you vim directory and it will 'install' the files:\r\n\r\n  ftplugin\/ri.vim\r\n  syntax\/ri.vim\r\n  doc\/ri.txt\r\n\r\nThen add something like\r\n\r\n  \" Load ri interface\r\n  source path\/to\/ftplugin\/ri.vim\r\n\r\nto your ftplugin\/ruby.vim to load it when editing ruby files.\r\n\r\nFor futher documentation on installation and usage take a look at the file doc\/ri.txt","5":"Unzip the installation file in you vim directory and it will 'install' the files:\r\n\r\n  ftplugin\/ri.vim\r\n  syntax\/ri.vim\r\n  doc\/ri.txt\r\n\r\nThen add something like\r\n\r\n  \" Load ri interface\r\n  source path\/to\/ftplugin\/ri.vim\r\n\r\nto your ftplugin\/ruby.vim to load it when editing ruby files.\r\n\r\nFor futher documentation on installation and usage take a look at the file doc\/ri.txt","first_name":"Jonas","6":"Jonas","last_name":"Fonseca","7":"Fonseca","releases":[{"0":"494","vim_version":"6.0","1":"6.0","script_version":"1.2","2":"1.2","version_comment":"Better syntax highlighting and word expansion.\r\nDocs moved to doc\/ri.txt and improved.\r\nChanged some of the optionnames and default settings.","3":"Better syntax highlighting and word expansion.\r\nDocs moved to doc\/ri.txt and improved.\r\nChanged some of the optionnames and default settings.","package":"ri-browser.zip","4":"ri-browser.zip","src_id":"1503","5":"1503","creation_date":"1038499444","6":"1038499444"},{"0":"494","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"ri-browser.zip","4":"ri-browser.zip","src_id":"1461","5":"1461","creation_date":"1038163533","6":"1038163533"}]},"493":{"script_id":"493","0":"493","script_name":"C++ code template generator","1":"C++ code template generator","script_type":"ftplugin","2":"ftplugin","summary":"Generate C++ code templates based on the header file","3":"Generate C++ code templates based on the header file","description":"Opens a template file and replaces various tags with values that are parsed from the header file.  The information parsed includes data members and their types, constructors including overloaded constructors and their parameters, methods declarations and their return types and parameter lists, as well as the class name.  This is then put into the source template in the proper format.  Data members are added to the constructors to relieve typing to initialize all your class variables.  The destructor is also added.  There is a little documentation in the ftpplugin\/cpp\/tmpl_gen.vim file.  It describes what tags that are currently supported so you can customize the template file that is included.  Feedback is needed, and very welcome.  Feel free to email me with any bug reports, feature requests, or if you need help getting it set up.\r\n\r\nNOTE!   This is currently broken.  I will fix it after the semester ends, but for the time being you can edit tmpl_gen.vim and change 'require \"tmpl_gen.rb\"' to 'require \"#{ENV['HOME']}\/.vim\/ftplugin\/cpp\/tmpl_gen.rb\".\r\n\r\nI would fix this now, but I am in the middle of making some major modifications, and I have finals coming up.","4":"Opens a template file and replaces various tags with values that are parsed from the header file.  The information parsed includes data members and their types, constructors including overloaded constructors and their parameters, methods declarations and their return types and parameter lists, as well as the class name.  This is then put into the source template in the proper format.  Data members are added to the constructors to relieve typing to initialize all your class variables.  The destructor is also added.  There is a little documentation in the ftpplugin\/cpp\/tmpl_gen.vim file.  It describes what tags that are currently supported so you can customize the template file that is included.  Feedback is needed, and very welcome.  Feel free to email me with any bug reports, feature requests, or if you need help getting it set up.\r\n\r\nNOTE!   This is currently broken.  I will fix it after the semester ends, but for the time being you can edit tmpl_gen.vim and change 'require \"tmpl_gen.rb\"' to 'require \"#{ENV['HOME']}\/.vim\/ftplugin\/cpp\/tmpl_gen.rb\".\r\n\r\nI would fix this now, but I am in the middle of making some major modifications, and I have finals coming up.","install_details":"Untar the tmpl_gen.tar.gz file in your ~\/.vim directory and then edit your .vimrc and add the following autocommand:\r\nau bufnewfile *.cpp call Make_cpp_template()\r\n\r\nEnjoy!","5":"Untar the tmpl_gen.tar.gz file in your ~\/.vim directory and then edit your .vimrc and add the following autocommand:\r\nau bufnewfile *.cpp call Make_cpp_template()\r\n\r\nEnjoy!","first_name":"Michael","6":"Michael","last_name":"Brailsford","7":"Brailsford","releases":[{"0":"493","vim_version":"6.0","1":"6.0","script_version":"0.25","2":"0.25","version_comment":"Initial upload","3":"Initial upload","package":"tmpl_gen.tar.gz","4":"tmpl_gen.tar.gz","src_id":"1460","5":"1460","creation_date":"1038160165","6":"1038160165"}]},"492":{"script_id":"492","0":"492","script_name":"SQLUtilities","1":"SQLUtilities","script_type":"utility","2":"utility","summary":"SQL utilities - Formatting, generate - columns lists, procedures for databases","3":"SQL utilities - Formatting, generate - columns lists, procedures for databases","description":"Various SQL Utilities.\r\n\r\nVersion 2.0 requires Vim 7.\r\n\r\n1. A SQL formatter, to make SQL statements (select, insert, update, delete...) more readable.   \r\n2. Based on create table statements, will generate select lists for a table, as long as the definition exists in some open buffer.\r\n3. Creates a generic procedure that will perform an insert, update, delete and select based on the definition of a table (if already open in some buffer).  The format is ANSI.\r\n4.  Returns the column datatype definition for a specified column name (or supplied) based on the definition of a table (if already open in some buffer).\r\n\r\nFunctions:\r\n[range]SQLUFormatter(..list..)\r\n                                                                            \r\n     Formats SQL statements into a easily readable form.\r\n     Breaks keywords onto new lines.\r\n     Forces column lists to be split over as many lines as\r\n     necessary to fit the current textwidth of the buffer,\r\n     so that lines do not wrap.\r\n     If parentheses are unbalanced (ie a subselect) it will\r\n     indent everything within the unbalanced paranthesis.\r\n     Works for SELECT, INSERT, UPDATE, DELETE statements.\r\n\r\n     Global variables to customization some aspects of the formatting:\r\n     sqlutil_align_where - aligns the =, >=, <=, ...\r\n     sqlutil_align_comma - places the column lists in select statement on new lines\r\n     sqlutil_align_first_word - see examples\r\n\r\n     You can change the case of the keywords while formatting.\r\n\r\n                                                                            \r\nExamples (these would look much better when using a fixed font):\r\n                                                                            \r\n  Original:\r\n  SELECT m.MSG_ID, m.PRIORITY_ID, CUST.CUST_NBR, CUST.CUST_NM, \r\n  CUST.CUST_LEGAL_NM, CUST.STORE_ADDR_1, CUST.STORE_ADDR_2, \r\n  CUST.CROSS_STREET, XMLELEMENT( 'Alerts', XMLELEMENT( 'Alert_alert_id', \r\n  alert_id ), XMLELEMENT( 'Alert_agent_id', agent_id ), XMLELEMENT( \r\n  'Alert_alert_type_id', alert_type_desc), XMLELEMENT( \r\n  'Alert_alert_date', alert_date), XMLELEMENT( \r\n  'Alert_url_reference', url_reference), XMLELEMENT( \r\n  'Alert_read_status', read_status )) CUST.STORE_CITY, \r\n  CUST.STORE_ST, CUST.POST_CODE, CUST.STORE_MGR_NM, FROM MESSAGES m JOIN \r\n  PRIORITY_CD P WHERE m.to_person_id = ?  AND p.NAME = 'PRI_EMERGENCY' AND \r\n  p.JOB = 'Plumber' AND m.status_id < ( SELECT s.STATUS_ID FROM \r\n  MSG_STATUS_CD s WHERE s.NAME = 'MSG_READ') ORDER BY m.msg_id desc\r\n  \r\n                                                                            \r\n  Formatted:\r\n  SELECT m.MSG_ID, m.PRIORITY_ID, CUST.CUST_NBR, CUST.CUST_NM,\r\n         CUST.CUST_LEGAL_NM, CUST.STORE_ADDR_1, CUST.STORE_ADDR_2,\r\n         CUST.CROSS_STREET,\r\n         XMLELEMENT(\r\n             'Alerts', XMLELEMENT( 'Alert_alert_id', alert_id ),\r\n             XMLELEMENT( 'Alert_agent_id', agent_id ),\r\n             XMLELEMENT( 'Alert_alert_type_id', alert_type_desc),\r\n             XMLELEMENT( 'Alert_alert_date', alert_date),\r\n             XMLELEMENT(\r\n                 'Alert_url_reference', url_reference\r\n              ), XMLELEMENT( 'Alert_read_status', read_status )\r\n         ) CUST.STORE_CITY, CUST.STORE_ST, CUST.POST_CODE, \r\n         CUST.STORE_MGR_NM\r\n    FROM MESSAGES m\r\n    JOIN PRIORITY_CD P\r\n   WHERE m.to_person_id = ?\r\n     AND p.NAME = 'PRI_EMERGENCY'\r\n     AND p.JOB = 'Plumber'\r\n     AND m.status_id < (\r\n          SELECT s.STATUS_ID\r\n            FROM MSG_STATUS_CD s\r\n           WHERE s.NAME = 'MSG_READ'\r\n         )\r\n   ORDER BY m.msg_id desc\r\n  \r\n  \r\n                                                                            \r\n  Original:\r\n  UPDATE \"SERVICE_REQUEST\" SET \"BUILDING_ID\" = ?, \"UNIT_ID\" = ?, \r\n  \"REASON_ID\" = ?, \"PERSON_ID\" = ?, \"PRIORITY_ID\" = ?, \"STATUS_ID\" = ?, \r\n  \"CREATED\" = ?, \"REQUESTED\" = ?, \"ARRIVED\" = ?  WHERE \"REQUEST_ID\" = ?\r\n                                                                            \r\n                                                                            \r\n  Formatted:\r\n  UPDATE \"SERVICE_REQUEST\"\r\n     SET \"BUILDING_ID\" = ?,\r\n         \"UNIT_ID\" = ?,\r\n         \"REASON_ID\" = ?,\r\n         \"PERSON_ID\" = ?,\r\n         \"PRIORITY_ID\" = ?,\r\n         \"STATUS_ID\" = ?,\r\n         \"CREATED\" = ?,\r\n         \"REQUESTED\" = ?,\r\n         \"ARRIVED\" = ?,\r\n   WHERE \"REQUEST_ID\"  = ?\r\n                                                                            \r\n                                                                            \r\n                                                                            \r\n  Original:\r\n  INSERT INTO \"MESSAGES\" ( \"MSG_ID\", \"TO_PERSON_ID\", \r\n  \"FROM_PERSON_ID\", \"REQUEST_ID\", \"CREATED\", \"PRIORITY_ID\", \r\n  \"MSG_TYPE_ID\", \"STATUS_ID\", \"READ_WHEN\", \"TIMEOUT\", \r\n  \"MSG_TXT\", \"RESEND_COUNT\" ) VALUES ( ?, ?, ?, \r\n  ?, ?, ?, ?, ?, ?, ?, ?, ? )\r\n                                                                            \r\n                                                                            \r\n  Formatted:\r\n  INSERT INTO \"MESSAGES\" ( \"MSG_ID\", \"TO_PERSON_ID\",\r\n         \"FROM_PERSON_ID\", \"REQUEST_ID\", \"CREATED\",\r\n         \"PRIORITY_ID\", \"MSG_TYPE_ID\", \"STATUS_ID\",\r\n         \"READ_WHEN\", \"TIMEOUT\", \"MSG_TXT\", \"RESEND_COUNT\" )\r\n  VALUES ( ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ? )\r\n                                                                            \r\n                                                                            \r\nFunctions:\r\nSQLUCreateColumnList( optional parameter )\r\n                                                                            \r\n     Assumes either the current file, or any other open buffer, \r\n     has a CREATE TABLE statement in a format similar to this:\r\n     CREATE TABLE customer (\r\n     \tid\tINT DEFAULT AUTOINCREMENT,\r\n     \tlast_modified TIMESTAMP NULL,\r\n     \tfirst_name     \tVARCHAR(30) NOT NULL,\r\n     \tlast_name\tVARCHAR(60) NOT NULL,\r\n     \tbalance\t        NUMERIC(10,2),\r\n     \tPRIMARY KEY( id )\r\n     );\r\n     If you place the cursor on the word customer, then the \r\n     unnamed buffer (also displayed by an echo statement) will \r\n     contain:\r\n     id, last_modified, first_name, last_name, balance\r\n                                                                            \r\n     Optionally, it will replace the word with the above and place\r\n     the word in the unnamed buffer.  Calling the function with\r\n     a parameter enables this feature.\r\n                                                                            \r\n     This also uses the g:sqlutil_cmd_terminator to determine when\r\n     the create table statement ends if none of the following terms\r\n     are found before the final );\r\n            primary,reference,unique,check,foreign\r\n     sqlutil_cmd defaults to \";\"\r\n                                                                            \r\n                                                                            \r\nFunctions:\r\nSQLUGetColumnDef( optional parameter )\r\nSQLUGetColumnDataType( expand(\"<cword>\"), 1 )\r\n                                                                            \r\n     Assumes either the current file, or any other open buffer, \r\n     has a CREATE TABLE statement in a format similar to this:\r\n     CREATE TABLE customer (\r\n     \tid\tINT DEFAULT AUTOINCREMENT,\r\n     \tlast_modified TIMESTAMP NULL,\r\n     \tfirst_name     \tVARCHAR(30) NOT NULL,\r\n     \tlast_name\tVARCHAR(60) NOT NULL,\r\n     \tbalance\t        NUMERIC(10,2),\r\n     \tPRIMARY KEY( id )\r\n     );\r\n     If you place the cursor on the word first_name, then the \r\n     column definition will be placed in the unnamed buffer (and also\r\n     displayed by an echo statement).\r\n     VARCHAR(30) NOT NULL        \r\n                                                                            \r\n     If the command is called as SQLUGetColumnDef( expand(\"<cword>\"), 1 )\r\n     or using the default mapping \\scdt, just the datatype (instead\r\n     of the column definition) will be returned.  A separate command \r\n     SQLUGetColumnDataType has been created for this.\r\n     VARCHAR(30) \r\n                                                                            \r\n                                                                            \r\nFunctions:\r\nSQLUCreateProcedure()\r\n                                                                            \r\n     Assumes either the current file, or any other open buffer, \r\n     has a CREATE TABLE statement in a format similar to this:\r\n     CREATE TABLE customer (\r\n     \tid\t        INT DEFAULT AUTOINCREMENT,\r\n     \tlast_modified   TIMESTAMP NULL,\r\n     \tfirst_name     \tVARCHAR(30) NOT NULL,\r\n     \tlast_name\tVARCHAR(60) NOT NULL,\r\n     \tbalance\t        NUMERIC(10,2),\r\n     \tPRIMARY KEY( id )\r\n     );\r\n     By calling SQLUCreateProcedure while on the name of a table\r\n     the unnamed buffer will contain the create procedure statement\r\n     for insert, update, delete and select statements.\r\n     Once pasted into the buffer, unneeded functionality can be \r\n     removed.\r\n                                                                            \r\n                                                                            \r\n                                                                            \r\nCommands:\r\n[range]SQLUFormatter ..list..    \r\n                     : Reformats the SQL statements over the specified \r\n                       range.  Statement will lined up given the \r\n                       existing indent of the first word.\r\nSQLUCreateColumnList:  Creates a comma separated list of column names\r\n                       for the table name under the cursor, assuming\r\n                       the table definition exists in any open \r\n                       buffer.  The column list is placed in the unnamed\r\n                       buffer.\r\n                       This also uses the g:sqlutil_cmd_terminator.\r\n                       By default a table alias will be added to each of the columns, this is \r\n                       configurable, see documentation (new 1.3.7).\r\n                       This routine can optionally take 2 parameters\r\n                       SQLUCreateColumnList T1 \r\n                           Creates a column list for T1\r\n                       SQLUCreateColumnList T1 1\r\n                           Creates a column list for T1 but only for\r\n                           the primary keys for that table.\r\nSQLUGetColumnDef     : Displays the column definition of the column name\r\n                       under the cursor.  It assumes the CREATE TABLE\r\n                       statement is in an open buffer.\r\nSQLUGetColumnDataType\r\n                     : Displays the column datatype of the column name\r\n                       under the cursor.  It assumes the CREATE TABLE\r\n                       statement is in an open buffer.\r\nSQLUCreateProcedure  : Creates a stored procedure to perform standard\r\n                       operations against the table that the cursor\r\n                       is currently under.\r\n                       \r\n                                                                            \r\n\r\nSuggested Mappings:\r\n    vmap <silent>sf        <Plug>SQLU_Formatter<CR>\r\n    nmap <silent>scl       <Plug>SQLU_CreateColumnList<CR>\r\n    nmap <silent>scd       <Plug>SQLU_GetColumnDef<CR>\r\n    nmap <silent>scdt      <Plug>SQLU_GetColumnDataType<CR>\r\n    nmap <silent>scp       <Plug>SQLU_CreateProcedure<CR>\r\n                                                                            \r\n    mnemonic explanation\r\n    s - sql\r\n      f   - format\r\n      cl  - column list\r\n      cd  - column definition\r\n      cdt - column datatype\r\n      cp  - create procedure\r\n                                                                            \r\n    To prevent the default mappings from being created, place the \r\n    following in your _vimrc:\r\n        let g:sqlutil_load_default_maps = 0\r\n                                                                            \r\nCustomization:\r\n    By default this script assumes a command is terminated by a ;\r\n    If you are using Microsoft SQL Server a command terminator \r\n    would be \"go\", or perhaps \"\\ngo\".\r\n    To permenantly override the terminator in your _vimrc file you can add\r\n          let g:sqlutil_cmd_terminator = \"\\ngo\"\r\n                                                                            \r\n                                                                            \r\n    When building a column list from a script file (ie CREATE TABLE \r\n    statements), you can customize the script to detect when the \r\n    column list finishes by creating the following in your _vimrc:\r\n          let g:sqlutil_col_list_terminators = \r\n                       \\ 'primary,reference,unique,check,foreign'\r\n                                                                            \r\n    This can be necessary in the following example:\r\n          CREATE TABLE customer (\r\n             id         INT DEFAULT AUTOINCREMENT,\r\n             first_name VARCHAR(30) NOT NULL,\r\n             last_name  VARCHAR(60) NOT NULL,\r\n             PRIMARY KEY( id )\r\n          ); \r\n\r\nDependencies:\r\n       Align.vim - Version 15\r\n                        - Author: Charles E. Campbell, Jr.\r\n                        - http:\/\/www.vim.org\/script.php?script_id=294\r\n\r\nSuggested (Complementary) Plugins:\r\n     dbext.vim - Provides database access to many DBMS (Oracle, Sybase, Microsoft, MySQL, DBI,..)\r\n                    - Author: Peter Bagyinszki and David Fishburn\r\n                    - http:\/\/www.vim.org\/script.php?script_id=356\r\n","4":"Various SQL Utilities.\r\n\r\nVersion 2.0 requires Vim 7.\r\n\r\n1. A SQL formatter, to make SQL statements (select, insert, update, delete...) more readable.   \r\n2. Based on create table statements, will generate select lists for a table, as long as the definition exists in some open buffer.\r\n3. Creates a generic procedure that will perform an insert, update, delete and select based on the definition of a table (if already open in some buffer).  The format is ANSI.\r\n4.  Returns the column datatype definition for a specified column name (or supplied) based on the definition of a table (if already open in some buffer).\r\n\r\nFunctions:\r\n[range]SQLUFormatter(..list..)\r\n                                                                            \r\n     Formats SQL statements into a easily readable form.\r\n     Breaks keywords onto new lines.\r\n     Forces column lists to be split over as many lines as\r\n     necessary to fit the current textwidth of the buffer,\r\n     so that lines do not wrap.\r\n     If parentheses are unbalanced (ie a subselect) it will\r\n     indent everything within the unbalanced paranthesis.\r\n     Works for SELECT, INSERT, UPDATE, DELETE statements.\r\n\r\n     Global variables to customization some aspects of the formatting:\r\n     sqlutil_align_where - aligns the =, >=, <=, ...\r\n     sqlutil_align_comma - places the column lists in select statement on new lines\r\n     sqlutil_align_first_word - see examples\r\n\r\n     You can change the case of the keywords while formatting.\r\n\r\n                                                                            \r\nExamples (these would look much better when using a fixed font):\r\n                                                                            \r\n  Original:\r\n  SELECT m.MSG_ID, m.PRIORITY_ID, CUST.CUST_NBR, CUST.CUST_NM, \r\n  CUST.CUST_LEGAL_NM, CUST.STORE_ADDR_1, CUST.STORE_ADDR_2, \r\n  CUST.CROSS_STREET, XMLELEMENT( 'Alerts', XMLELEMENT( 'Alert_alert_id', \r\n  alert_id ), XMLELEMENT( 'Alert_agent_id', agent_id ), XMLELEMENT( \r\n  'Alert_alert_type_id', alert_type_desc), XMLELEMENT( \r\n  'Alert_alert_date', alert_date), XMLELEMENT( \r\n  'Alert_url_reference', url_reference), XMLELEMENT( \r\n  'Alert_read_status', read_status )) CUST.STORE_CITY, \r\n  CUST.STORE_ST, CUST.POST_CODE, CUST.STORE_MGR_NM, FROM MESSAGES m JOIN \r\n  PRIORITY_CD P WHERE m.to_person_id = ?  AND p.NAME = 'PRI_EMERGENCY' AND \r\n  p.JOB = 'Plumber' AND m.status_id < ( SELECT s.STATUS_ID FROM \r\n  MSG_STATUS_CD s WHERE s.NAME = 'MSG_READ') ORDER BY m.msg_id desc\r\n  \r\n                                                                            \r\n  Formatted:\r\n  SELECT m.MSG_ID, m.PRIORITY_ID, CUST.CUST_NBR, CUST.CUST_NM,\r\n         CUST.CUST_LEGAL_NM, CUST.STORE_ADDR_1, CUST.STORE_ADDR_2,\r\n         CUST.CROSS_STREET,\r\n         XMLELEMENT(\r\n             'Alerts', XMLELEMENT( 'Alert_alert_id', alert_id ),\r\n             XMLELEMENT( 'Alert_agent_id', agent_id ),\r\n             XMLELEMENT( 'Alert_alert_type_id', alert_type_desc),\r\n             XMLELEMENT( 'Alert_alert_date', alert_date),\r\n             XMLELEMENT(\r\n                 'Alert_url_reference', url_reference\r\n              ), XMLELEMENT( 'Alert_read_status', read_status )\r\n         ) CUST.STORE_CITY, CUST.STORE_ST, CUST.POST_CODE, \r\n         CUST.STORE_MGR_NM\r\n    FROM MESSAGES m\r\n    JOIN PRIORITY_CD P\r\n   WHERE m.to_person_id = ?\r\n     AND p.NAME = 'PRI_EMERGENCY'\r\n     AND p.JOB = 'Plumber'\r\n     AND m.status_id < (\r\n          SELECT s.STATUS_ID\r\n            FROM MSG_STATUS_CD s\r\n           WHERE s.NAME = 'MSG_READ'\r\n         )\r\n   ORDER BY m.msg_id desc\r\n  \r\n  \r\n                                                                            \r\n  Original:\r\n  UPDATE \"SERVICE_REQUEST\" SET \"BUILDING_ID\" = ?, \"UNIT_ID\" = ?, \r\n  \"REASON_ID\" = ?, \"PERSON_ID\" = ?, \"PRIORITY_ID\" = ?, \"STATUS_ID\" = ?, \r\n  \"CREATED\" = ?, \"REQUESTED\" = ?, \"ARRIVED\" = ?  WHERE \"REQUEST_ID\" = ?\r\n                                                                            \r\n                                                                            \r\n  Formatted:\r\n  UPDATE \"SERVICE_REQUEST\"\r\n     SET \"BUILDING_ID\" = ?,\r\n         \"UNIT_ID\" = ?,\r\n         \"REASON_ID\" = ?,\r\n         \"PERSON_ID\" = ?,\r\n         \"PRIORITY_ID\" = ?,\r\n         \"STATUS_ID\" = ?,\r\n         \"CREATED\" = ?,\r\n         \"REQUESTED\" = ?,\r\n         \"ARRIVED\" = ?,\r\n   WHERE \"REQUEST_ID\"  = ?\r\n                                                                            \r\n                                                                            \r\n                                                                            \r\n  Original:\r\n  INSERT INTO \"MESSAGES\" ( \"MSG_ID\", \"TO_PERSON_ID\", \r\n  \"FROM_PERSON_ID\", \"REQUEST_ID\", \"CREATED\", \"PRIORITY_ID\", \r\n  \"MSG_TYPE_ID\", \"STATUS_ID\", \"READ_WHEN\", \"TIMEOUT\", \r\n  \"MSG_TXT\", \"RESEND_COUNT\" ) VALUES ( ?, ?, ?, \r\n  ?, ?, ?, ?, ?, ?, ?, ?, ? )\r\n                                                                            \r\n                                                                            \r\n  Formatted:\r\n  INSERT INTO \"MESSAGES\" ( \"MSG_ID\", \"TO_PERSON_ID\",\r\n         \"FROM_PERSON_ID\", \"REQUEST_ID\", \"CREATED\",\r\n         \"PRIORITY_ID\", \"MSG_TYPE_ID\", \"STATUS_ID\",\r\n         \"READ_WHEN\", \"TIMEOUT\", \"MSG_TXT\", \"RESEND_COUNT\" )\r\n  VALUES ( ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ? )\r\n                                                                            \r\n                                                                            \r\nFunctions:\r\nSQLUCreateColumnList( optional parameter )\r\n                                                                            \r\n     Assumes either the current file, or any other open buffer, \r\n     has a CREATE TABLE statement in a format similar to this:\r\n     CREATE TABLE customer (\r\n     \tid\tINT DEFAULT AUTOINCREMENT,\r\n     \tlast_modified TIMESTAMP NULL,\r\n     \tfirst_name     \tVARCHAR(30) NOT NULL,\r\n     \tlast_name\tVARCHAR(60) NOT NULL,\r\n     \tbalance\t        NUMERIC(10,2),\r\n     \tPRIMARY KEY( id )\r\n     );\r\n     If you place the cursor on the word customer, then the \r\n     unnamed buffer (also displayed by an echo statement) will \r\n     contain:\r\n     id, last_modified, first_name, last_name, balance\r\n                                                                            \r\n     Optionally, it will replace the word with the above and place\r\n     the word in the unnamed buffer.  Calling the function with\r\n     a parameter enables this feature.\r\n                                                                            \r\n     This also uses the g:sqlutil_cmd_terminator to determine when\r\n     the create table statement ends if none of the following terms\r\n     are found before the final );\r\n            primary,reference,unique,check,foreign\r\n     sqlutil_cmd defaults to \";\"\r\n                                                                            \r\n                                                                            \r\nFunctions:\r\nSQLUGetColumnDef( optional parameter )\r\nSQLUGetColumnDataType( expand(\"<cword>\"), 1 )\r\n                                                                            \r\n     Assumes either the current file, or any other open buffer, \r\n     has a CREATE TABLE statement in a format similar to this:\r\n     CREATE TABLE customer (\r\n     \tid\tINT DEFAULT AUTOINCREMENT,\r\n     \tlast_modified TIMESTAMP NULL,\r\n     \tfirst_name     \tVARCHAR(30) NOT NULL,\r\n     \tlast_name\tVARCHAR(60) NOT NULL,\r\n     \tbalance\t        NUMERIC(10,2),\r\n     \tPRIMARY KEY( id )\r\n     );\r\n     If you place the cursor on the word first_name, then the \r\n     column definition will be placed in the unnamed buffer (and also\r\n     displayed by an echo statement).\r\n     VARCHAR(30) NOT NULL        \r\n                                                                            \r\n     If the command is called as SQLUGetColumnDef( expand(\"<cword>\"), 1 )\r\n     or using the default mapping \\scdt, just the datatype (instead\r\n     of the column definition) will be returned.  A separate command \r\n     SQLUGetColumnDataType has been created for this.\r\n     VARCHAR(30) \r\n                                                                            \r\n                                                                            \r\nFunctions:\r\nSQLUCreateProcedure()\r\n                                                                            \r\n     Assumes either the current file, or any other open buffer, \r\n     has a CREATE TABLE statement in a format similar to this:\r\n     CREATE TABLE customer (\r\n     \tid\t        INT DEFAULT AUTOINCREMENT,\r\n     \tlast_modified   TIMESTAMP NULL,\r\n     \tfirst_name     \tVARCHAR(30) NOT NULL,\r\n     \tlast_name\tVARCHAR(60) NOT NULL,\r\n     \tbalance\t        NUMERIC(10,2),\r\n     \tPRIMARY KEY( id )\r\n     );\r\n     By calling SQLUCreateProcedure while on the name of a table\r\n     the unnamed buffer will contain the create procedure statement\r\n     for insert, update, delete and select statements.\r\n     Once pasted into the buffer, unneeded functionality can be \r\n     removed.\r\n                                                                            \r\n                                                                            \r\n                                                                            \r\nCommands:\r\n[range]SQLUFormatter ..list..    \r\n                     : Reformats the SQL statements over the specified \r\n                       range.  Statement will lined up given the \r\n                       existing indent of the first word.\r\nSQLUCreateColumnList:  Creates a comma separated list of column names\r\n                       for the table name under the cursor, assuming\r\n                       the table definition exists in any open \r\n                       buffer.  The column list is placed in the unnamed\r\n                       buffer.\r\n                       This also uses the g:sqlutil_cmd_terminator.\r\n                       By default a table alias will be added to each of the columns, this is \r\n                       configurable, see documentation (new 1.3.7).\r\n                       This routine can optionally take 2 parameters\r\n                       SQLUCreateColumnList T1 \r\n                           Creates a column list for T1\r\n                       SQLUCreateColumnList T1 1\r\n                           Creates a column list for T1 but only for\r\n                           the primary keys for that table.\r\nSQLUGetColumnDef     : Displays the column definition of the column name\r\n                       under the cursor.  It assumes the CREATE TABLE\r\n                       statement is in an open buffer.\r\nSQLUGetColumnDataType\r\n                     : Displays the column datatype of the column name\r\n                       under the cursor.  It assumes the CREATE TABLE\r\n                       statement is in an open buffer.\r\nSQLUCreateProcedure  : Creates a stored procedure to perform standard\r\n                       operations against the table that the cursor\r\n                       is currently under.\r\n                       \r\n                                                                            \r\n\r\nSuggested Mappings:\r\n    vmap <silent>sf        <Plug>SQLU_Formatter<CR>\r\n    nmap <silent>scl       <Plug>SQLU_CreateColumnList<CR>\r\n    nmap <silent>scd       <Plug>SQLU_GetColumnDef<CR>\r\n    nmap <silent>scdt      <Plug>SQLU_GetColumnDataType<CR>\r\n    nmap <silent>scp       <Plug>SQLU_CreateProcedure<CR>\r\n                                                                            \r\n    mnemonic explanation\r\n    s - sql\r\n      f   - format\r\n      cl  - column list\r\n      cd  - column definition\r\n      cdt - column datatype\r\n      cp  - create procedure\r\n                                                                            \r\n    To prevent the default mappings from being created, place the \r\n    following in your _vimrc:\r\n        let g:sqlutil_load_default_maps = 0\r\n                                                                            \r\nCustomization:\r\n    By default this script assumes a command is terminated by a ;\r\n    If you are using Microsoft SQL Server a command terminator \r\n    would be \"go\", or perhaps \"\\ngo\".\r\n    To permenantly override the terminator in your _vimrc file you can add\r\n          let g:sqlutil_cmd_terminator = \"\\ngo\"\r\n                                                                            \r\n                                                                            \r\n    When building a column list from a script file (ie CREATE TABLE \r\n    statements), you can customize the script to detect when the \r\n    column list finishes by creating the following in your _vimrc:\r\n          let g:sqlutil_col_list_terminators = \r\n                       \\ 'primary,reference,unique,check,foreign'\r\n                                                                            \r\n    This can be necessary in the following example:\r\n          CREATE TABLE customer (\r\n             id         INT DEFAULT AUTOINCREMENT,\r\n             first_name VARCHAR(30) NOT NULL,\r\n             last_name  VARCHAR(60) NOT NULL,\r\n             PRIMARY KEY( id )\r\n          ); \r\n\r\nDependencies:\r\n       Align.vim - Version 15\r\n                        - Author: Charles E. Campbell, Jr.\r\n                        - http:\/\/www.vim.org\/script.php?script_id=294\r\n\r\nSuggested (Complementary) Plugins:\r\n     dbext.vim - Provides database access to many DBMS (Oracle, Sybase, Microsoft, MySQL, DBI,..)\r\n                    - Author: Peter Bagyinszki and David Fishburn\r\n                    - http:\/\/www.vim.org\/script.php?script_id=356\r\n","install_details":"Put <SQLUtilities.vim> into your .vim\/plugin or vimfiles\/plugin directory.\r\nPut <SQLUtilities.vim> into your .vim\/autoload or vimfiles\/autoload directory.\r\nPut <SQLUtilities.txt> into your .vim\/doc or vimfiles\/doc directory, run :helptags $VIM\/vimfiles\/doc.\r\n\r\n","5":"Put <SQLUtilities.vim> into your .vim\/plugin or vimfiles\/plugin directory.\r\nPut <SQLUtilities.vim> into your .vim\/autoload or vimfiles\/autoload directory.\r\nPut <SQLUtilities.txt> into your .vim\/doc or vimfiles\/doc directory, run :helptags $VIM\/vimfiles\/doc.\r\n\r\n","first_name":"David","6":"David","last_name":"Fishburn","7":"Fishburn","releases":[{"0":"492","vim_version":"7.0","1":"7.0","script_version":"7.0","2":"7.0","version_comment":"NF: Comments in your SQL are now allowed and will be formatted appropriately (which usually means ignored).  If you Vim does not have syntax support, all comments will be removed prior to formatting (you are asked to confirm).\r\n\r\nNF: A major overhaul to how SQL is formatted.  Fixed a few bugs which crept up while testing the new methods.  The main change was how long lines are handled.  Now, long lines are only split when a comma or open paranthesis is found.  This can still leave lines long but the previous method could leave the new SQL nearly unreadabable depending on it's content.  Thanks to Jeremey Hustman for providing the ColdFusion code samples.\r\n\r\nNF: Added new options which allow you to override which (small set of) keywords are flipped to UPPER or lower case.  This means if a few keywords are missing they can easily be added to your .vimrc while waiting for an update to the plugin.  See the option g:sqlutil_non_line_break_keywords.\r\n\r\nNF: Added new options which allows you to turn off different formatting options.  This is really only useful for debugging, but if you run into an issue you can turn off that piece of formatting.  See help for more details, the new options are: \r\n       g:sqlutil_indent_nested_blocks\r\n       g:sqlutil_wrap_long_lines\r\n       g:sqlutil_wrap_function_calls\r\n       g:sqlutil_wrap_width\r\n       g:sqlutil_split_unbalanced_paran\r\n\r\nBF: Long lines were not wrapped appropriately (Don Parker).\r\n\r\nBF: Based on certain conditions, the formatter could get into an endless loop (Don Parker).\r\n\r\nBF: ColdFusion placeholders were incorrectly formatted (Jeremy Hustman).\r\n\r\nBF: Some keywords (i.e. LIKE, AS, ASC, DESC, ...) were not UPPER cased (Jeremy Hustman).\r\n\r\nBF: Delete statements were not formatted (Jeremy Hustman).\r\n","3":"NF: Comments in your SQL are now allowed and will be formatted appropriately (which usually means ignored).  If you Vim does not have syntax support, all comments will be removed prior to formatting (you are asked to confirm).\r\n\r\nNF: A major overhaul to how SQL is formatted.  Fixed a few bugs which crept up while testing the new methods.  The main change was how long lines are handled.  Now, long lines are only split when a comma or open paranthesis is found.  This can still leave lines long but the previous method could leave the new SQL nearly unreadabable depending on it's content.  Thanks to Jeremey Hustman for providing the ColdFusion code samples.\r\n\r\nNF: Added new options which allow you to override which (small set of) keywords are flipped to UPPER or lower case.  This means if a few keywords are missing they can easily be added to your .vimrc while waiting for an update to the plugin.  See the option g:sqlutil_non_line_break_keywords.\r\n\r\nNF: Added new options which allows you to turn off different formatting options.  This is really only useful for debugging, but if you run into an issue you can turn off that piece of formatting.  See help for more details, the new options are: \r\n       g:sqlutil_indent_nested_blocks\r\n       g:sqlutil_wrap_long_lines\r\n       g:sqlutil_wrap_function_calls\r\n       g:sqlutil_wrap_width\r\n       g:sqlutil_split_unbalanced_paran\r\n\r\nBF: Long lines were not wrapped appropriately (Don Parker).\r\n\r\nBF: Based on certain conditions, the formatter could get into an endless loop (Don Parker).\r\n\r\nBF: ColdFusion placeholders were incorrectly formatted (Jeremy Hustman).\r\n\r\nBF: Some keywords (i.e. LIKE, AS, ASC, DESC, ...) were not UPPER cased (Jeremy Hustman).\r\n\r\nBF: Delete statements were not formatted (Jeremy Hustman).\r\n","package":"sqlutil_700.zip","4":"sqlutil_700.zip","src_id":"19113","5":"19113","creation_date":"1354658158","6":"1354658158"},{"0":"492","vim_version":"7.0","1":"7.0","script_version":"6.00","2":"6.00","version_comment":"NF: When formatting INSERT statements, the sqlutil_align_comma is also respected to place each column on a newline.\r\n\r\nNF: When formatting UPDATE statements and sqlutil_align_comma is set comments at the end of the line were removed (Rodrigo Laporte).\r\n","3":"NF: When formatting INSERT statements, the sqlutil_align_comma is also respected to place each column on a newline.\r\n\r\nNF: When formatting UPDATE statements and sqlutil_align_comma is set comments at the end of the line were removed (Rodrigo Laporte).\r\n","package":"sqlutil_600.zip","4":"sqlutil_600.zip","src_id":"18769","5":"18769","creation_date":"1349830532","6":"1349830532"},{"0":"492","vim_version":"7.0","1":"7.0","script_version":"5.00","2":"5.00","version_comment":"NF: Now an extra check is made for the Align plugin.  If not found when attempting to format a SQL statement a friendly message is shown (Enrico Teotti).\r\n\r\nNF: Updated documentation added the Global Options section plus updated the Customization section.\r\n\r\nNF: Problem: Keywords within strings were being formatted (Olivier Laurent).\r\n      Solution: Added an option, g:sqlutil_use_syntax_support, to determine whether or not to use Vim's syntax support to decide if the keyword is highlighted as a \"string\".  If so, leave it and move on to the next keyword.  Default value is 1 (enabled).  See |sqlutil-customization| for details on usage.\r\n\r\nNF: Added an option, g:sqlutil_syntax_elements, to allow the user to decide which syntax elements should be considered a string.  Default value is 'Constant,sqlString'.\r\n","3":"NF: Now an extra check is made for the Align plugin.  If not found when attempting to format a SQL statement a friendly message is shown (Enrico Teotti).\r\n\r\nNF: Updated documentation added the Global Options section plus updated the Customization section.\r\n\r\nNF: Problem: Keywords within strings were being formatted (Olivier Laurent).\r\n      Solution: Added an option, g:sqlutil_use_syntax_support, to determine whether or not to use Vim's syntax support to decide if the keyword is highlighted as a \"string\".  If so, leave it and move on to the next keyword.  Default value is 1 (enabled).  See |sqlutil-customization| for details on usage.\r\n\r\nNF: Added an option, g:sqlutil_syntax_elements, to allow the user to decide which syntax elements should be considered a string.  Default value is 'Constant,sqlString'.\r\n","package":"sqlutil_500.zip","4":"sqlutil_500.zip","src_id":"17536","5":"17536","creation_date":"1330398370","6":"1330398370"},{"0":"492","vim_version":"7.0","1":"7.0","script_version":"4.00","2":"4.00","version_comment":"NF: Added a tutorial to take users through the common features of the plugin.\r\n\r\nNF: Added an option, g:sqlutil_align_keyword_right, to left or right (default) align the keywords (Per Winkvist).\r\n\r\nNF: Documented and added new global variables (g:sqlutil_menu_root, g:sqlutil_menu_priority) to customize the location of the SQLUtil menu.\r\n\r\nBF: SQLite used slightly different syntax specifying UNIQUE values and would not correctly generate a column list from the CREATE TABLE statement (Oliver Peters).\r\n\r\nBF: Ensured all normal commands used ! to ensure no mappings interfered with the commands (Benoit Mortgat).\r\n","3":"NF: Added a tutorial to take users through the common features of the plugin.\r\n\r\nNF: Added an option, g:sqlutil_align_keyword_right, to left or right (default) align the keywords (Per Winkvist).\r\n\r\nNF: Documented and added new global variables (g:sqlutil_menu_root, g:sqlutil_menu_priority) to customize the location of the SQLUtil menu.\r\n\r\nBF: SQLite used slightly different syntax specifying UNIQUE values and would not correctly generate a column list from the CREATE TABLE statement (Oliver Peters).\r\n\r\nBF: Ensured all normal commands used ! to ensure no mappings interfered with the commands (Benoit Mortgat).\r\n","package":"sqlutil_400.zip","4":"sqlutil_400.zip","src_id":"13576","5":"13576","creation_date":"1281838749","6":"1281838749"},{"0":"492","vim_version":"7.0","1":"7.0","script_version":"3.00","2":"3.00","version_comment":"NF: Added new menu links so that commonly used options can be quickly and easily toggled without having to remember the global variable names or values.  For example, if you cut the menu so that it floats beside your buffer you can easily hit \"Toggle Align Where\" or \"Uppercase Keywords\".  \r\nNF: Using the menu_mode option you can control if and where the SQLUtil menu is created.  See the menu_mode option for more details.\r\nNF: Added the default maps to the menus.  If you use a floating menu, or simply view the menu you can more easily memorize your most commonly used maps.\r\nBF: UPPER and lower case of keywords did not work for multi-word keywords (ORDER BY, LEFT OUTER JOIN, ...).\r\n","3":"NF: Added new menu links so that commonly used options can be quickly and easily toggled without having to remember the global variable names or values.  For example, if you cut the menu so that it floats beside your buffer you can easily hit \"Toggle Align Where\" or \"Uppercase Keywords\".  \r\nNF: Using the menu_mode option you can control if and where the SQLUtil menu is created.  See the menu_mode option for more details.\r\nNF: Added the default maps to the menus.  If you use a floating menu, or simply view the menu you can more easily memorize your most commonly used maps.\r\nBF: UPPER and lower case of keywords did not work for multi-word keywords (ORDER BY, LEFT OUTER JOIN, ...).\r\n","package":"sqlutil_300.zip","4":"sqlutil_300.zip","src_id":"9825","5":"9825","creation_date":"1232049778","6":"1232049778"},{"0":"492","vim_version":"7.0","1":"7.0","script_version":"2.0.0","2":"2.0.0","version_comment":"NF: Added support for Vim 7's autoload functionality","3":"NF: Added support for Vim 7's autoload functionality","package":"sqlutil_200.zip","4":"sqlutil_200.zip","src_id":"7638","5":"7638","creation_date":"1189366315","6":"1189366315"},{"0":"492","vim_version":"6.0","1":"6.0","script_version":"1.4.1","2":"1.4.1","version_comment":"NF: Added additional statements to g:sqlutil_col_list_terminators\r\nBF: Forgot to increment g:loaded_sqlutilities\r\n","3":"NF: Added additional statements to g:sqlutil_col_list_terminators\r\nBF: Forgot to increment g:loaded_sqlutilities\r\n","package":"sqlutil_141.zip","4":"sqlutil_141.zip","src_id":"4655","5":"4655","creation_date":"1128665190","6":"1128665190"},{"0":"492","vim_version":"6.0","1":"6.0","script_version":"1.4.0","2":"1.4.0","version_comment":"BF: If a statement has parenthesis inside of strings, the formatter was not ignoring them.  This could result in the formatter reporting there were mismatched parenthesis.\r\n    Example: select 'string' + '(' from dummy\r\nBF: If a keyword was not followed by a space, it was not placed on a newline.  \r\n    Example:  SELECT * FROM(T1)\r\nBF: Nested function calls could potentially lead to an endless loop.  \r\n","3":"BF: If a statement has parenthesis inside of strings, the formatter was not ignoring them.  This could result in the formatter reporting there were mismatched parenthesis.\r\n    Example: select 'string' + '(' from dummy\r\nBF: If a keyword was not followed by a space, it was not placed on a newline.  \r\n    Example:  SELECT * FROM(T1)\r\nBF: Nested function calls could potentially lead to an endless loop.  \r\n","package":"sqlutil_140.zip","4":"sqlutil_140.zip","src_id":"4021","5":"4021","creation_date":"1110828184","6":"1110828184"},{"0":"492","vim_version":"6.0","1":"6.0","script_version":"1.3.9","2":"1.3.9","version_comment":"BF:  When g:sqlutil_align_comma=1 and a select list spanned more than 1 line (via functions calls and so on), it was possible the remaining comma separated list was not aligned properly.","3":"BF:  When g:sqlutil_align_comma=1 and a select list spanned more than 1 line (via functions calls and so on), it was possible the remaining comma separated list was not aligned properly.","package":"sqlutil_139.zip","4":"sqlutil_139.zip","src_id":"3847","5":"3847","creation_date":"1108021996","6":"1108021996"},{"0":"492","vim_version":"6.0","1":"6.0","script_version":"1.3.8","2":"1.3.8","version_comment":"NF: Enhanced the feature to change the case of keywords, to include the optional join words, left, right, full, inner, outer.  These words were missed prior to this change and only the JOIN word was capitalized.\r\nCH: Changed the default for sqlutil_use_tbl_alias = 'a' (ask) from being on at all times.  This can be overridden in your vimrc.\r\n","3":"NF: Enhanced the feature to change the case of keywords, to include the optional join words, left, right, full, inner, outer.  These words were missed prior to this change and only the JOIN word was capitalized.\r\nCH: Changed the default for sqlutil_use_tbl_alias = 'a' (ask) from being on at all times.  This can be overridden in your vimrc.\r\n","package":"sqlutil_138.zip","4":"sqlutil_138.zip","src_id":"3678","5":"3678","creation_date":"1102051558","6":"1102051558"},{"0":"492","vim_version":"6.0","1":"6.0","script_version":"1.3.7","2":"1.3.7","version_comment":"NF: Added new option g:sqlutil_use_tbl_alias, which is on by default.\r\n    When creating a column list for a table, it will add a table\r\n    alias to each column.  The table alias is calculated based on \r\n    rules.  This feature has 3 settings:\r\n       n - no alias\r\n       d - default calculated alias\r\n       a - ask the user using default alias\r\nNF: Updated g:sqlutil_col_list_terminators to handle some additional\r\n    cases.\r\nBF: In some cases -@- could be left in the query.  This seems to be\r\n    a bug in Vim, where the marks could move.  Unsure why, but put\r\n    a workaround in.\r\nBF: When g:sqlutil_align_comma=1, and the lines did not begin with\r\n    commas, the formatting was incorrect.\r\nBF: When searching through buffers (SQLU_CreateColumnList), the \r\n    alternate buffer could be changed.\r\n","3":"NF: Added new option g:sqlutil_use_tbl_alias, which is on by default.\r\n    When creating a column list for a table, it will add a table\r\n    alias to each column.  The table alias is calculated based on \r\n    rules.  This feature has 3 settings:\r\n       n - no alias\r\n       d - default calculated alias\r\n       a - ask the user using default alias\r\nNF: Updated g:sqlutil_col_list_terminators to handle some additional\r\n    cases.\r\nBF: In some cases -@- could be left in the query.  This seems to be\r\n    a bug in Vim, where the marks could move.  Unsure why, but put\r\n    a workaround in.\r\nBF: When g:sqlutil_align_comma=1, and the lines did not begin with\r\n    commas, the formatting was incorrect.\r\nBF: When searching through buffers (SQLU_CreateColumnList), the \r\n    alternate buffer could be changed.\r\n","package":"sqlutil_137.zip","4":"sqlutil_137.zip","src_id":"3257","5":"3257","creation_date":"1090442587","6":"1090442587"},{"0":"492","vim_version":"6.0","1":"6.0","script_version":"1.3.6","2":"1.3.6","version_comment":"NF: Added support for window functions (OVER, PARTITION BY, ROWS,     RANGE), and additional Oracle SELECT keywords (DIMENSION,     MEASURES, ITERATE, WITHIN GROUP, IGNORE, KEEP, RETURN, RULES)\r\n","3":"NF: Added support for window functions (OVER, PARTITION BY, ROWS,     RANGE), and additional Oracle SELECT keywords (DIMENSION,     MEASURES, ITERATE, WITHIN GROUP, IGNORE, KEEP, RETURN, RULES)\r\n","package":"sqlutil_136.zip","4":"sqlutil_136.zip","src_id":"3167","5":"3167","creation_date":"1087844836","6":"1087844836"},{"0":"492","vim_version":"6.0","1":"6.0","script_version":"1.3.5","2":"1.3.5","version_comment":"New features added:\r\nNew global variables to customization some aspects of the formatting:\r\nsqlutil_align_where - aligns the =, >=, <=, ...\r\nsqlutil_align_comma - places the column lists in select statement on new lines\r\nsqlutil_align_first_word - see examples\r\n\r\nYou can change the case of the keywords while formatting.\r\n\r\nA help has been created to list all the various options and examples for each of them.\r\n\r\nThanks to Ronald Speelman, for suggestions and testing.","3":"New features added:\r\nNew global variables to customization some aspects of the formatting:\r\nsqlutil_align_where - aligns the =, >=, <=, ...\r\nsqlutil_align_comma - places the column lists in select statement on new lines\r\nsqlutil_align_first_word - see examples\r\n\r\nYou can change the case of the keywords while formatting.\r\n\r\nA help has been created to list all the various options and examples for each of them.\r\n\r\nThanks to Ronald Speelman, for suggestions and testing.","package":"sqlutil_135.zip","4":"sqlutil_135.zip","src_id":"2812","5":"2812","creation_date":"1078681041","6":"1078681041"},{"0":"492","vim_version":"6.0","1":"6.0","script_version":"1.3.3","2":"1.3.3","version_comment":"NF: Added global variable sqlutil_col_list_terminators for  customization.\r\nNF: Changed all functions to be prefixed bySQLU_ for consistency.\r\nBF: Fixed SQLU_GetColumnDataType andSQLU_GetColumnDef to handle tabs.\r\nBF: -@- could be left after incorrect formatting.\r\n","3":"NF: Added global variable sqlutil_col_list_terminators for  customization.\r\nNF: Changed all functions to be prefixed bySQLU_ for consistency.\r\nBF: Fixed SQLU_GetColumnDataType andSQLU_GetColumnDef to handle tabs.\r\nBF: -@- could be left after incorrect formatting.\r\n","package":"SQLUtilities.vim","4":"SQLUtilities.vim","src_id":"2306","5":"2306","creation_date":"1062858051","6":"1062858051"},{"0":"492","vim_version":"6.0","1":"6.0","script_version":"1.3","2":"1.3","version_comment":"NF: Support the formatting of FUNCTIONS or\r\n    stored procedures used as derived tables.  This \r\n    will nest the function calls on new lines and \r\n    correctly split the paranthesis on new lines if \r\n    the function call is longer than one line.  You \r\n    would notice this mainly in the SELECT \r\n    column list.\r\nNF: Support the formatting of nested CASE\r\n    statements.\r\nNF: Added the GetColumnDataType command \r\nNF: Improved primary key determination, it no \r\n    longer requires the PRIMARY KEY statement to\r\n    be part of the CREATE TABLE statement, it can \r\n    be part of an ALTER TABLE statement.\r\nNF: Improved formatting of SQL keywords.  \r\n    INSERT INTO statement, the INTO will no longer\r\n    be split onto a new line.\r\n    Now correctly format the various JOIN keywords:\r\n    NATURAL RIGHT OUTER JOIN will be placed one\r\n    online instead of just the JOIN keyword as\r\n    before.\r\nBF: Did not properly handle the formatting of\r\n    nested open paranthesis in all cases.\r\nBF: Using new technique to determine how to change\r\n    the textwidth to utilitize more screen space\r\n    when wrapping long lines.\r\n    nested open paranthesis in all cases.\r\nNF: Create procedure uses shiftwidth for indent.\r\nBF: Save\/restore previous search.\r\n","3":"NF: Support the formatting of FUNCTIONS or\r\n    stored procedures used as derived tables.  This \r\n    will nest the function calls on new lines and \r\n    correctly split the paranthesis on new lines if \r\n    the function call is longer than one line.  You \r\n    would notice this mainly in the SELECT \r\n    column list.\r\nNF: Support the formatting of nested CASE\r\n    statements.\r\nNF: Added the GetColumnDataType command \r\nNF: Improved primary key determination, it no \r\n    longer requires the PRIMARY KEY statement to\r\n    be part of the CREATE TABLE statement, it can \r\n    be part of an ALTER TABLE statement.\r\nNF: Improved formatting of SQL keywords.  \r\n    INSERT INTO statement, the INTO will no longer\r\n    be split onto a new line.\r\n    Now correctly format the various JOIN keywords:\r\n    NATURAL RIGHT OUTER JOIN will be placed one\r\n    online instead of just the JOIN keyword as\r\n    before.\r\nBF: Did not properly handle the formatting of\r\n    nested open paranthesis in all cases.\r\nBF: Using new technique to determine how to change\r\n    the textwidth to utilitize more screen space\r\n    when wrapping long lines.\r\n    nested open paranthesis in all cases.\r\nNF: Create procedure uses shiftwidth for indent.\r\nBF: Save\/restore previous search.\r\n","package":"SQLUtilities.vim","4":"SQLUtilities.vim","src_id":"2047","5":"2047","creation_date":"1054901511","6":"1054901511"},{"0":"492","vim_version":"6.0","1":"6.0","script_version":"1.1","2":"1.1","version_comment":"Improved a number of items.\r\n\r\n1.  If a PRIMARY KEY cannot be found for a given table the WHERE clause will contain all columns.\r\n\r\n2.  Made the lookup for primary keys smarter.  Now the script will also look for ALTER TABLE ... ADD PRIMARY KEY statements instead of just the PRIMARY KEY clause as part of the CREATE TABLE statement.\r\n\r\n3.  If hidden is set, the script will cycle through the buffers looking for the table.  Now, it will leave the cursor positioned in the same location when it leaves hidden buffers.\r\n\r\n4.  You can now define g:sqlutil_cmd_terminator.  It currently defaults to \";\".  This is used when looking gathering columns lists.  \r\n","3":"Improved a number of items.\r\n\r\n1.  If a PRIMARY KEY cannot be found for a given table the WHERE clause will contain all columns.\r\n\r\n2.  Made the lookup for primary keys smarter.  Now the script will also look for ALTER TABLE ... ADD PRIMARY KEY statements instead of just the PRIMARY KEY clause as part of the CREATE TABLE statement.\r\n\r\n3.  If hidden is set, the script will cycle through the buffers looking for the table.  Now, it will leave the cursor positioned in the same location when it leaves hidden buffers.\r\n\r\n4.  You can now define g:sqlutil_cmd_terminator.  It currently defaults to \";\".  This is used when looking gathering columns lists.  \r\n","package":"SQLUtilities.vim","4":"SQLUtilities.vim","src_id":"1694","5":"1694","creation_date":"1044383479","6":"1044383479"},{"0":"492","vim_version":"6.0","1":"6.0","script_version":"1","2":"1","version_comment":"Initial upload","3":"Initial upload","package":"SQLUtilities.vim","4":"SQLUtilities.vim","src_id":"1457","5":"1457","creation_date":"1038056643","6":"1038056643"}]},"491":{"script_id":"491","0":"491","script_name":"debug.vim","1":"debug.vim","script_type":"utility","2":"utility","summary":"Simple utility to assist in debugging vim scripts","3":"Simple utility to assist in debugging vim scripts","description":"utility to help in debugging vim scripts\r\n  put this in the plugin directory\r\n  will add a new menu VIM->Debug->....\r\n    menu options \r\n      DebugOn - turns debug on - will display debug text in VIM scripts\r\n      DebugOff - turns debug off - will not display debug text in VIM scripts\r\n      Debug Status - displays debug status in status line\r\n      Insert Debug Text - insert debug text in vim scripts\r\n\r\nusage:\r\n  eg in following vim script\r\n\r\n1 fun! <SID>JavaImpGenerate()  \r\n2    let impfile = tempname()\r\n3    let currBuff = bufnr(\"%\")\r\n    \r\n  for debugging, insert debug text in above script as follows\r\n1 fun! <SID>JavaImpGenerate()  \r\n2    call Debug(\"entering JavaImpGenerate\")\r\n3    let impfile = tempname()\r\n4    call Debug(\"impfile = \" . impfile ) \r\n5    let currBuff = bufnr(\"%\")\r\n6    call Debug(\"currBuff = \" . currBuff ) \r\n\r\nThe debugging stubs in lines 2, 4, 6 will run only if Debug status is on.","4":"utility to help in debugging vim scripts\r\n  put this in the plugin directory\r\n  will add a new menu VIM->Debug->....\r\n    menu options \r\n      DebugOn - turns debug on - will display debug text in VIM scripts\r\n      DebugOff - turns debug off - will not display debug text in VIM scripts\r\n      Debug Status - displays debug status in status line\r\n      Insert Debug Text - insert debug text in vim scripts\r\n\r\nusage:\r\n  eg in following vim script\r\n\r\n1 fun! <SID>JavaImpGenerate()  \r\n2    let impfile = tempname()\r\n3    let currBuff = bufnr(\"%\")\r\n    \r\n  for debugging, insert debug text in above script as follows\r\n1 fun! <SID>JavaImpGenerate()  \r\n2    call Debug(\"entering JavaImpGenerate\")\r\n3    let impfile = tempname()\r\n4    call Debug(\"impfile = \" . impfile ) \r\n5    let currBuff = bufnr(\"%\")\r\n6    call Debug(\"currBuff = \" . currBuff ) \r\n\r\nThe debugging stubs in lines 2, 4, 6 will run only if Debug status is on.","install_details":"save debug.vim in plugin directory","5":"save debug.vim in plugin directory","first_name":"kam onn","6":"kam onn","last_name":"siew","7":"siew","releases":[{"0":"491","vim_version":"6.0","1":"6.0","script_version":"1.0.0","2":"1.0.0","version_comment":"Initial upload","3":"Initial upload","package":"debug.vim","4":"debug.vim","src_id":"1453","5":"1453","creation_date":"1037995031","6":"1037995031"}]},"490":{"script_id":"490","0":"490","script_name":"java_getset.vim","1":"java_getset.vim","script_type":"utility","2":"utility","summary":"Automatically add getter\/setters for Java properties (including array-based)","3":"Automatically add getter\/setters for Java properties (including array-based)","description":"This filetype plugin enables a user to automatically add getter\/setter\r\nmethods for Java properties.  The script will insert a getter, setter,\r\nor both depending on the command\/mapping invoked.  Users can select\r\nproperties one at a time, or in bulk (via a visual block or specifying a\r\nrange).  In either case, the selected block may include comments as they\r\nwill be ignored during the parsing.  For example, you could select all\r\nof these properties with a single visual block.\r\n\r\npublic class Test \r\n{ \r\n   \/\/ Start your selection here\r\n   private static int count;\r\n\r\n   \/** The name *\/\r\n   private String name;\r\n\r\n   \/** The array of addresses *\/\r\n   private String[] address;\r\n   \/\/ End your selection here\r\n\r\n   public static void main(String[] args)\r\n   {\r\n   }\r\n}\r\n\r\nThe script will also add the 'static' modifier to the method if the\r\nproperty was declared as 'static'.  Array-based properties will get\r\nadditional methods added to support indexing.  In addition, if a\r\nproperty is declared 'final', it will not generate a setter for it.\r\nIf a previous getter OR setter exists for a property, the script will\r\nnot add any methods (under the assumption that you've manually added\r\nyour own).\r\n\r\nThe getters\/setters that are inserted can be configured by the user.\r\nFirst, the insertion point can be selected.  It can be one of the\r\nfollowing: before the current line \/ block, after the current line \/\r\nblock, or at the end of the class (default).  Finally, the text that is\r\ninserted can be configured by defining your own templates.  This allows\r\nthe user to format for his\/her coding style.  For example, the default\r\nvalue for s:javagetset_getterTemplate is:\r\n\r\n    \/**\r\n     * Get %varname%.\r\n     * \r\n     * @return %varname% as %type%.\r\n     *\/\r\n    %modifiers% %type% %funcname%()\r\n    {   \r\n        return %varname%;\r\n    }\r\n\r\nWhere the items surrounded by % are parameters that are substituted when\r\nthe script is invoked on a particular property.  For more information on\r\nconfiguration, please see the section below on the INTERFACE.\r\n\r\nINTERFACE (commands, mappings, and variables) \r\nThe following section documents the commands, mappings, and variables\r\nused to customize the behavior of this script.\r\n\r\nCommands:\r\n  :InsertGetterSetter\r\n      Inserts a getter\/setter for the property on the current line, or\r\n      the range of properties specified via a visual block or x,y range\r\n      notation.  The user is prompted to determine what type of method\r\n      to insert.\r\n  \r\n  :InsertGetterOnly\r\n      Inserts a getter for the property on the current line, or the\r\n      range of properties specified via a visual block or x,y range\r\n      notation.  The user is not prompted.\r\n  \r\n  :InsertSetterOnly\r\n      Inserts a setter for the property on the current line, or the\r\n      range of properties specified via a visual block or x,y range\r\n      notation.  The user is not prompted.\r\n  \r\n  :InsertBothGetterSetter\r\n      Inserts a getter and setter for the property on the current line,\r\n      or the range of properties specified via a visual block or x,y\r\n      range notation.  The user is not prompted.\r\n\r\nMappings:\r\n  The following mappings are pre-defined.  You can disable the mappings\r\n  by setting a variable (see the Variables section below).  The default\r\n  key mappings use the <LocalLeader> which is the backslash key by\r\n  default '\\'.  This can also be configured via a variable (see below).\r\n  \r\n  <LocalLeader>p   (or <Plug>JavagetsetInsertGetterSetter)\r\n      Inserts a getter\/setter for the property on the current line, or\r\n      the range of properties specified via a visual block.  User is\r\n      prompted for choice.\r\n  \r\n  <LocalLeader>g   (or <Plug>JavagetsetInsertGetterOnly)\r\n      Inserts a getter for the property on the current line, or the\r\n      range of properties specified via a visual block.  User is not\r\n      prompted.\r\n  \r\n  <LocalLeader>s   (or <Plug>JavagetsetInsertSetterOnly)\r\n      Inserts a getter for the property on the current line, or the\r\n      range of properties specified via a visual block.  User is not\r\n      prompted.\r\n  \r\n  <LocalLeader>b   (or <Plug>JavagetsetInsertBothGetterSetter) \r\n      Inserts both a getter and setter for the property on the current\r\n      line, or the range of properties specified via a visual block.\r\n      User is not prompted.\r\n  \r\n  If you want to define your own mapping, you can map whatever you want\r\n  to <Plug>JavagetsetInsertGetterSetter (or any of the other <Plug>s\r\n  defined above).  For example,\r\n\r\n      map <buffer> <C-p> <Plug>JavagetsetInsertGetterSetter\r\n\r\n  When you define your own mapping, the default mapping does not get\r\n  set, only the mapping you specify.\r\n\r\nVariables:\r\n  The following variables allow you to customize the behavior of this\r\n  script so that you do not need to make changes directly to the script.\r\n  These variables can be set in your vimrc.\r\n  \r\n  no_plugin_maps \r\n    Setting this variable will disable all key mappings defined by any\r\n    of your plugins (if the plugin writer adhered to the standard\r\n    convention documented in the scripting section of the VIM manual)\r\n    including this one.\r\n  \r\n  no_java_maps\r\n    Setting this variable will disable all key mappings defined by any\r\n    java specific plugin including this one.\r\n  \r\n  maplocalleader\r\n    By default, the key mappings defined by this script use\r\n    <LocalLeader> which is the backslash character by default.  You can\r\n    change this by setting this variable to a different key.  For\r\n    example, if you want to use the comma-key, you can add this line to\r\n    your vimrc:\r\n        \r\n        let maplocalleader = ','\r\n  \r\n  b:javagetset_insertPosition\r\n    This variable determines the location where the getter and\/or setter\r\n    will be inserted.  Currently, three positions have been defined:\r\n        \r\n        0 - insert at the end of the class (default)\r\n        1 - insert before the current line \/ block\r\n        2 - insert after the current line \/ block\r\n\r\n  b:javagetset_getterTemplate\r\n  b:javagetset_setterTemplate\r\n  b:javagetset_getterArrayTemplate\r\n  b:javagetset_setterArrayTemplate\r\n    These variables determine the text that will be inserted for a\r\n    getter, setter, array-based getter, and array-based setter\r\n    respectively.  The templates may contain the following placeholders\r\n    which will be substituted by their appropriate values at insertion\r\n    time:\r\n         \r\n        %type%          Java type of the property\r\n        %varname%       The name of the property\r\n        %funcname%      The method name (\"getXzy\" or \"setXzy\")\r\n        %modifiers%     \"public\" followed by \"static\" if the property is static\r\n    \r\n    For example, if you wanted to set the default getter template so\r\n    that it would produce the following block of code for a property\r\n    defined as \"public static String name\":\r\n        \r\n        \/**\r\n         * Get name.\r\n         * @return name as String\r\n         *\/\r\n        public static String getName() { return name; }\r\n    \r\n    This block of code can be produced by adding the following variable\r\n    definition to your vimrc file.\r\n        \r\n        let b:javagetset_getterTemplate =\r\n          \\ \"\\n\" .\r\n          \\ \"\/**\\n\" .\r\n          \\ \" * Get %varname%.\\n\" .\r\n          \\ \" * @return %varname% as %type%.\\n\" .\r\n          \\ \" *\/\\n\" .\r\n          \\ \"%modifiers% %type% %funcname%() { return %varname%; }\"\r\n\r\n    The defaults for these variables are defined in the script.  For\r\n    both the getterTemplate and setterTemplate, there is a corresponding\r\n    array-baded template that is invoked if a property is array-based.\r\n    This allows you to set indexed-based getters\/setters if you desire.\r\n    This is the default behavior.\r\n","4":"This filetype plugin enables a user to automatically add getter\/setter\r\nmethods for Java properties.  The script will insert a getter, setter,\r\nor both depending on the command\/mapping invoked.  Users can select\r\nproperties one at a time, or in bulk (via a visual block or specifying a\r\nrange).  In either case, the selected block may include comments as they\r\nwill be ignored during the parsing.  For example, you could select all\r\nof these properties with a single visual block.\r\n\r\npublic class Test \r\n{ \r\n   \/\/ Start your selection here\r\n   private static int count;\r\n\r\n   \/** The name *\/\r\n   private String name;\r\n\r\n   \/** The array of addresses *\/\r\n   private String[] address;\r\n   \/\/ End your selection here\r\n\r\n   public static void main(String[] args)\r\n   {\r\n   }\r\n}\r\n\r\nThe script will also add the 'static' modifier to the method if the\r\nproperty was declared as 'static'.  Array-based properties will get\r\nadditional methods added to support indexing.  In addition, if a\r\nproperty is declared 'final', it will not generate a setter for it.\r\nIf a previous getter OR setter exists for a property, the script will\r\nnot add any methods (under the assumption that you've manually added\r\nyour own).\r\n\r\nThe getters\/setters that are inserted can be configured by the user.\r\nFirst, the insertion point can be selected.  It can be one of the\r\nfollowing: before the current line \/ block, after the current line \/\r\nblock, or at the end of the class (default).  Finally, the text that is\r\ninserted can be configured by defining your own templates.  This allows\r\nthe user to format for his\/her coding style.  For example, the default\r\nvalue for s:javagetset_getterTemplate is:\r\n\r\n    \/**\r\n     * Get %varname%.\r\n     * \r\n     * @return %varname% as %type%.\r\n     *\/\r\n    %modifiers% %type% %funcname%()\r\n    {   \r\n        return %varname%;\r\n    }\r\n\r\nWhere the items surrounded by % are parameters that are substituted when\r\nthe script is invoked on a particular property.  For more information on\r\nconfiguration, please see the section below on the INTERFACE.\r\n\r\nINTERFACE (commands, mappings, and variables) \r\nThe following section documents the commands, mappings, and variables\r\nused to customize the behavior of this script.\r\n\r\nCommands:\r\n  :InsertGetterSetter\r\n      Inserts a getter\/setter for the property on the current line, or\r\n      the range of properties specified via a visual block or x,y range\r\n      notation.  The user is prompted to determine what type of method\r\n      to insert.\r\n  \r\n  :InsertGetterOnly\r\n      Inserts a getter for the property on the current line, or the\r\n      range of properties specified via a visual block or x,y range\r\n      notation.  The user is not prompted.\r\n  \r\n  :InsertSetterOnly\r\n      Inserts a setter for the property on the current line, or the\r\n      range of properties specified via a visual block or x,y range\r\n      notation.  The user is not prompted.\r\n  \r\n  :InsertBothGetterSetter\r\n      Inserts a getter and setter for the property on the current line,\r\n      or the range of properties specified via a visual block or x,y\r\n      range notation.  The user is not prompted.\r\n\r\nMappings:\r\n  The following mappings are pre-defined.  You can disable the mappings\r\n  by setting a variable (see the Variables section below).  The default\r\n  key mappings use the <LocalLeader> which is the backslash key by\r\n  default '\\'.  This can also be configured via a variable (see below).\r\n  \r\n  <LocalLeader>p   (or <Plug>JavagetsetInsertGetterSetter)\r\n      Inserts a getter\/setter for the property on the current line, or\r\n      the range of properties specified via a visual block.  User is\r\n      prompted for choice.\r\n  \r\n  <LocalLeader>g   (or <Plug>JavagetsetInsertGetterOnly)\r\n      Inserts a getter for the property on the current line, or the\r\n      range of properties specified via a visual block.  User is not\r\n      prompted.\r\n  \r\n  <LocalLeader>s   (or <Plug>JavagetsetInsertSetterOnly)\r\n      Inserts a getter for the property on the current line, or the\r\n      range of properties specified via a visual block.  User is not\r\n      prompted.\r\n  \r\n  <LocalLeader>b   (or <Plug>JavagetsetInsertBothGetterSetter) \r\n      Inserts both a getter and setter for the property on the current\r\n      line, or the range of properties specified via a visual block.\r\n      User is not prompted.\r\n  \r\n  If you want to define your own mapping, you can map whatever you want\r\n  to <Plug>JavagetsetInsertGetterSetter (or any of the other <Plug>s\r\n  defined above).  For example,\r\n\r\n      map <buffer> <C-p> <Plug>JavagetsetInsertGetterSetter\r\n\r\n  When you define your own mapping, the default mapping does not get\r\n  set, only the mapping you specify.\r\n\r\nVariables:\r\n  The following variables allow you to customize the behavior of this\r\n  script so that you do not need to make changes directly to the script.\r\n  These variables can be set in your vimrc.\r\n  \r\n  no_plugin_maps \r\n    Setting this variable will disable all key mappings defined by any\r\n    of your plugins (if the plugin writer adhered to the standard\r\n    convention documented in the scripting section of the VIM manual)\r\n    including this one.\r\n  \r\n  no_java_maps\r\n    Setting this variable will disable all key mappings defined by any\r\n    java specific plugin including this one.\r\n  \r\n  maplocalleader\r\n    By default, the key mappings defined by this script use\r\n    <LocalLeader> which is the backslash character by default.  You can\r\n    change this by setting this variable to a different key.  For\r\n    example, if you want to use the comma-key, you can add this line to\r\n    your vimrc:\r\n        \r\n        let maplocalleader = ','\r\n  \r\n  b:javagetset_insertPosition\r\n    This variable determines the location where the getter and\/or setter\r\n    will be inserted.  Currently, three positions have been defined:\r\n        \r\n        0 - insert at the end of the class (default)\r\n        1 - insert before the current line \/ block\r\n        2 - insert after the current line \/ block\r\n\r\n  b:javagetset_getterTemplate\r\n  b:javagetset_setterTemplate\r\n  b:javagetset_getterArrayTemplate\r\n  b:javagetset_setterArrayTemplate\r\n    These variables determine the text that will be inserted for a\r\n    getter, setter, array-based getter, and array-based setter\r\n    respectively.  The templates may contain the following placeholders\r\n    which will be substituted by their appropriate values at insertion\r\n    time:\r\n         \r\n        %type%          Java type of the property\r\n        %varname%       The name of the property\r\n        %funcname%      The method name (\"getXzy\" or \"setXzy\")\r\n        %modifiers%     \"public\" followed by \"static\" if the property is static\r\n    \r\n    For example, if you wanted to set the default getter template so\r\n    that it would produce the following block of code for a property\r\n    defined as \"public static String name\":\r\n        \r\n        \/**\r\n         * Get name.\r\n         * @return name as String\r\n         *\/\r\n        public static String getName() { return name; }\r\n    \r\n    This block of code can be produced by adding the following variable\r\n    definition to your vimrc file.\r\n        \r\n        let b:javagetset_getterTemplate =\r\n          \\ \"\\n\" .\r\n          \\ \"\/**\\n\" .\r\n          \\ \" * Get %varname%.\\n\" .\r\n          \\ \" * @return %varname% as %type%.\\n\" .\r\n          \\ \" *\/\\n\" .\r\n          \\ \"%modifiers% %type% %funcname%() { return %varname%; }\"\r\n\r\n    The defaults for these variables are defined in the script.  For\r\n    both the getterTemplate and setterTemplate, there is a corresponding\r\n    array-baded template that is invoked if a property is array-based.\r\n    This allows you to set indexed-based getters\/setters if you desire.\r\n    This is the default behavior.\r\n","install_details":"1. Copy the script to your ${HOME}\/.vim\/ftplugins directory and make\r\n   sure its named \"java_getset.vim\" or \"java_something.vim\" where\r\n   \"something\" can be anything you want.\r\n\r\n2. (Optional) Customize the mapping and\/or templates.  You can create\r\n   your own filetype plugin (just make sure its loaded before this one)\r\n   and set the variables in there (i.e. ${HOME}\/.vim\/ftplugin\/java.vim)\r\n\r\n","5":"1. Copy the script to your ${HOME}\/.vim\/ftplugins directory and make\r\n   sure its named \"java_getset.vim\" or \"java_something.vim\" where\r\n   \"something\" can be anything you want.\r\n\r\n2. (Optional) Customize the mapping and\/or templates.  You can create\r\n   your own filetype plugin (just make sure its loaded before this one)\r\n   and set the variables in there (i.e. ${HOME}\/.vim\/ftplugin\/java.vim)\r\n\r\n","first_name":"Pete","6":"Pete","last_name":"Kazmier","7":"Kazmier","releases":[{"0":"490","vim_version":"6.0","1":"6.0","script_version":"1.10","2":"1.10","version_comment":"Fixed another bug, didn't properly escape the carriage return when used in the normal command.  Sorry about the numerous uploads, I'm a VIM newbie.","3":"Fixed another bug, didn't properly escape the carriage return when used in the normal command.  Sorry about the numerous uploads, I'm a VIM newbie.","package":"java_getset.vim","4":"java_getset.vim","src_id":"1523","5":"1523","creation_date":"1038813685","6":"1038813685"},{"0":"490","vim_version":"6.0","1":"6.0","script_version":"1.9","2":"1.9","version_comment":"Fixed a bug where the inserted methods were not positioned properly in some cases. ","3":"Fixed a bug where the inserted methods were not positioned properly in some cases. ","package":"java_getset.vim","4":"java_getset.vim","src_id":"1518","5":"1518","creation_date":"1038687704","6":"1038687704"},{"0":"490","vim_version":"6.0","1":"6.0","script_version":"1.6","2":"1.6","version_comment":"Corrected the way the end of the current class was determined (previously, sometimes the inserted methods would be inserted outside of the class body).  Also, I changed the test to see if the script was previously loaded as it seems that the script was not loaded as the variable b:did_ftpplugin is set by lots of scripts.","3":"Corrected the way the end of the current class was determined (previously, sometimes the inserted methods would be inserted outside of the class body).  Also, I changed the test to see if the script was previously loaded as it seems that the script was not loaded as the variable b:did_ftpplugin is set by lots of scripts.","package":"java_getset.vim","4":"java_getset.vim","src_id":"1497","5":"1497","creation_date":"1038402680","6":"1038402680"},{"0":"490","vim_version":"6.0","1":"6.0","script_version":"1.5","2":"1.5","version_comment":"User is now able to configure the position where getter\/setters are inserted.  In addition, separate commands have been defined so users do not always have to be prompted (:InsertGetterOnly, :InsertSetterOnly, :InsertBothGetterSetter).  Key mappings have also be mapped for these commands by default.  Finally, more verbose documentation has been provided.  Thanks to Dan Sharp for his comments and suggestions.","3":"User is now able to configure the position where getter\/setters are inserted.  In addition, separate commands have been defined so users do not always have to be prompted (:InsertGetterOnly, :InsertSetterOnly, :InsertBothGetterSetter).  Key mappings have also be mapped for these commands by default.  Finally, more verbose documentation has been provided.  Thanks to Dan Sharp for his comments and suggestions.","package":"java_getset.vim","4":"java_getset.vim","src_id":"1486","5":"1486","creation_date":"1038295443","6":"1038295443"}]},"489":{"script_id":"489","0":"489","script_name":"ManPageView","1":"ManPageView","script_type":"utility","2":"utility","summary":"withdrawn","3":"withdrawn","description":"withdrawn -- the search engine bots got ahold of the \"unsatisfactory\" address and within a week -810 was dumped onto manpageview's karma.  The address problem was fixed, but the karma wasn't, and so with the rating being so negative, few bother to look at manpageview here anymore.  You can still go to my website, http:\/\/www.drchip.org\/astronaut\/vim\/index.html#MANPAGEVIEW, and get a copy.","4":"withdrawn -- the search engine bots got ahold of the \"unsatisfactory\" address and within a week -810 was dumped onto manpageview's karma.  The address problem was fixed, but the karma wasn't, and so with the rating being so negative, few bother to look at manpageview here anymore.  You can still go to my website, http:\/\/www.drchip.org\/astronaut\/vim\/index.html#MANPAGEVIEW, and get a copy.","install_details":"go to http:\/\/www.drchip.org\/astronaut\/vim\/index.html#MANPAGEVIEW","5":"go to http:\/\/www.drchip.org\/astronaut\/vim\/index.html#MANPAGEVIEW","first_name":"Charles","6":"Charles","last_name":"Campbell","7":"Campbell","releases":[{"0":"489","vim_version":"7.0","1":"7.0","script_version":"W","2":"W","version_comment":"withdrawn","3":"withdrawn","package":"withdrawn.vim","4":"withdrawn.vim","src_id":"16670","5":"16670","creation_date":"1318607057","6":"1318607057"}]},"488":{"script_id":"488","0":"488","script_name":"cream-keytest","1":"cream-keytest","script_type":"utility","2":"utility","summary":"Test and interpret keyboard characters returned by your hardware\/software.","3":"Test and interpret keyboard characters returned by your hardware\/software.","description":"\r\nTest and interpret individual keyboard characters. Useful to see exactly what code your hardware and software combination returns for a given keystroke. Where our interpretation table isn't complete, the actual decimal values for the key pressed are returned.\r\n\r\nNotes:\r\n\r\n* The interpretation table is currently unfinished. There are literally between 400 and 700 possible keystroke combinations on the average keyboard. Please look at the complete Ctrl\/Shift\/Alt combination interpretations of the Ins, Del, Home, End, PgUp, PgDn keys for an example of a full test.\r\n\r\n* This has only been tested with &encoding=latin1.\r\n\r\n* If you take the time to develop the script further, please forward your explorations or improvements them back to us! (Besides, that's what the GPL is all about. ;)\r\n\r\n\r\nThis is one of many custom utilities and functions for gVim from the Cream project (http:\/\/cream.sourceforge.net), a configuration of Vim for those of us familiar with Apple and Windows software.\r\n\r\n","4":"\r\nTest and interpret individual keyboard characters. Useful to see exactly what code your hardware and software combination returns for a given keystroke. Where our interpretation table isn't complete, the actual decimal values for the key pressed are returned.\r\n\r\nNotes:\r\n\r\n* The interpretation table is currently unfinished. There are literally between 400 and 700 possible keystroke combinations on the average keyboard. Please look at the complete Ctrl\/Shift\/Alt combination interpretations of the Ins, Del, Home, End, PgUp, PgDn keys for an example of a full test.\r\n\r\n* This has only been tested with &encoding=latin1.\r\n\r\n* If you take the time to develop the script further, please forward your explorations or improvements them back to us! (Besides, that's what the GPL is all about. ;)\r\n\r\n\r\nThis is one of many custom utilities and functions for gVim from the Cream project (http:\/\/cream.sourceforge.net), a configuration of Vim for those of us familiar with Apple and Windows software.\r\n\r\n","install_details":"\r\nJust drop this file into your plugins directory, and start Vim.\r\n\r\n* Call \"Cream_keytest()\" to get feedback about each key pressed.\r\n\r\n* Call \"Cream_keyinterpret()\" to return only the interpretation. An empty return means character not yet in the table.\r\n\r\n","5":"\r\nJust drop this file into your plugins directory, and start Vim.\r\n\r\n* Call \"Cream_keytest()\" to get feedback about each key pressed.\r\n\r\n* Call \"Cream_keyinterpret()\" to return only the interpretation. An empty return means character not yet in the table.\r\n\r\n","first_name":"Steve","6":"Steve","last_name":"Hall","7":"Hall","releases":[{"0":"488","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"cream-keytest.vim","4":"cream-keytest.vim","src_id":"1431","5":"1431","creation_date":"1037633766","6":"1037633766"}]},"487":{"script_id":"487","0":"487","script_name":"Posting","1":"Posting","script_type":"utility","2":"utility","summary":"Mappings primarily intended to ease preparing of USENET\/eMail articles","3":"Mappings primarily intended to ease preparing of USENET\/eMail articles","description":"\"Posting\" provides a few mappings I once messed around with in order to ease preparing USENET\/email articles with GVim.","4":"\"Posting\" provides a few mappings I once messed around with in order to ease preparing USENET\/email articles with GVim.","install_details":":source posting.vim\r\n:Post 72\r\n","5":":source posting.vim\r\n:Post 72\r\n","first_name":"Tim","6":"Tim","last_name":"Allen","7":"Allen","releases":[{"0":"487","vim_version":"6.0","1":"6.0","script_version":"1.2","2":"1.2","version_comment":"- Added highlighting support (Vim's own syntax file mail.vim no longer necessary now - take a look at *posting-highlighting*...)\r\n- Scan mode: added commands 'k' (step up), 'd' (delete visually selected area), 'c' (chron.-check to the end), digit (take out to the end) (see also comments to shortcut <C-Space>), slightly improved stepping mechanism\r\n- \"Take out\": Added new feature (see description to shortcut \"tt\")\r\n- Improved attribution handling (attributions may span over up to 4 lines now and may contain empty lines as well)\r\n- Added shortcuts \",u\" to undo \":Post\" and \",s\" to save message as draft (see comments)\r\n- Modified \",r\" (Visual\/Normal mode) and \"r\" (Scan mode) to take indent from second line instead of first (Use this to reformat quotations with embedded lists.)\r\n- 'autoindent' works with format_flowed set to 1 too now (Sorry for inconveniences!)\r\n- Box section: New shape (see *posting-sections*)\r\n- Various minor enhancements\/fixups\r\n","3":"- Added highlighting support (Vim's own syntax file mail.vim no longer necessary now - take a look at *posting-highlighting*...)\r\n- Scan mode: added commands 'k' (step up), 'd' (delete visually selected area), 'c' (chron.-check to the end), digit (take out to the end) (see also comments to shortcut <C-Space>), slightly improved stepping mechanism\r\n- \"Take out\": Added new feature (see description to shortcut \"tt\")\r\n- Improved attribution handling (attributions may span over up to 4 lines now and may contain empty lines as well)\r\n- Added shortcuts \",u\" to undo \":Post\" and \",s\" to save message as draft (see comments)\r\n- Modified \",r\" (Visual\/Normal mode) and \"r\" (Scan mode) to take indent from second line instead of first (Use this to reformat quotations with embedded lists.)\r\n- 'autoindent' works with format_flowed set to 1 too now (Sorry for inconveniences!)\r\n- Box section: New shape (see *posting-sections*)\r\n- Various minor enhancements\/fixups\r\n","package":"posting.vim","4":"posting.vim","src_id":"2009","5":"2009","creation_date":"1053532063","6":"1053532063"},{"0":"487","vim_version":"6.0","1":"6.0","script_version":"1.1","2":"1.1","version_comment":"- Added RFC 2646 support (see comment to parameter 'format_flowed' (Settings folder))\r\n- Added support for Vim's inbuilt client-server facility (command \"Post!\", see also *posting-invocation*)\r\n- Added Scan mode feature to ease reformatting of quoted text with tables, lists or the like inside (see also comment to shortcut <C-Space>)\r\n- Added shortcut \",r\" for manual reformatting (see also comment under *posting-commands*)\r\n- Added shortcuts <Up>, <Down>, <Home>, <End> to enable navigating with line-wrap turned on (formatoption \"t\" turned off now per default, use line-wrap instead (resp. \"Split\" which turns it on automatically)) \r\n- Modified \"Paste\" to protect indented structures (tab's are replaced with spaces)\r\n- Modified quoting-markup-correction slightly to keep indented structures readable\r\n- Modified \"Undo\" to make it restore the initial state\r\n- \"Jump\" (shortcut <Space>) more intelligent now (narrowed raster)\r\n- Box sections with new shape now (flowed-friendly)\r\n","3":"- Added RFC 2646 support (see comment to parameter 'format_flowed' (Settings folder))\r\n- Added support for Vim's inbuilt client-server facility (command \"Post!\", see also *posting-invocation*)\r\n- Added Scan mode feature to ease reformatting of quoted text with tables, lists or the like inside (see also comment to shortcut <C-Space>)\r\n- Added shortcut \",r\" for manual reformatting (see also comment under *posting-commands*)\r\n- Added shortcuts <Up>, <Down>, <Home>, <End> to enable navigating with line-wrap turned on (formatoption \"t\" turned off now per default, use line-wrap instead (resp. \"Split\" which turns it on automatically)) \r\n- Modified \"Paste\" to protect indented structures (tab's are replaced with spaces)\r\n- Modified quoting-markup-correction slightly to keep indented structures readable\r\n- Modified \"Undo\" to make it restore the initial state\r\n- \"Jump\" (shortcut <Space>) more intelligent now (narrowed raster)\r\n- Box sections with new shape now (flowed-friendly)\r\n","package":"posting.vim","4":"posting.vim","src_id":"1901","5":"1901","creation_date":"1049729284","6":"1049729284"},{"0":"487","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"- Modified \"Format\" and \"final-format\" to recognize numbered lists (see also comment to shortcut \"ff\")\r\n- Added shortcut \",a\" to slot in attribution lines\r\n- Added shortcut \",p\" to help fixing up \"Plenking\" (i. e. space between word and punctuation mark)\r\n- Attribution lines: Added shortcuts <M-C-LeftMouse> (manual reformatting\/undo-mechanism) and <M-RightMouse> (cutting)\r\n- \"Take out\": changed meaning slightly (<C-t><C-t> reformats whole paragraph only in case that count is given; tables, lists etc. thus remain untouched), code partially rewritten (content check, improved performance)\r\n- Added centering support (box-directive \"\/c\" and shortcut \",c\")\r\n- Modified code for quoting-markup-check (improved performance, covered special cases)\r\n- Added shortcuts <Space> and <M-Space> to step through most recent reply text (see also comments to <S-Space> and <C-Space>)","3":"- Modified \"Format\" and \"final-format\" to recognize numbered lists (see also comment to shortcut \"ff\")\r\n- Added shortcut \",a\" to slot in attribution lines\r\n- Added shortcut \",p\" to help fixing up \"Plenking\" (i. e. space between word and punctuation mark)\r\n- Attribution lines: Added shortcuts <M-C-LeftMouse> (manual reformatting\/undo-mechanism) and <M-RightMouse> (cutting)\r\n- \"Take out\": changed meaning slightly (<C-t><C-t> reformats whole paragraph only in case that count is given; tables, lists etc. thus remain untouched), code partially rewritten (content check, improved performance)\r\n- Added centering support (box-directive \"\/c\" and shortcut \",c\")\r\n- Modified code for quoting-markup-check (improved performance, covered special cases)\r\n- Added shortcuts <Space> and <M-Space> to step through most recent reply text (see also comments to <S-Space> and <C-Space>)","package":"posting.vim","4":"posting.vim","src_id":"1797","5":"1797","creation_date":"1047310484","6":"1047310484"}]},"486":{"script_id":"486","0":"486","script_name":"SAPDB_Pascal.vim","1":"SAPDB_Pascal.vim","script_type":"syntax","2":"syntax","summary":"syntax highlighting for pascal source files from SAPDB","3":"syntax highlighting for pascal source files from SAPDB","description":"Its used to highlight syntax for pascal source files from \"http:\/\/www.sapdb.org\". Special SAPDB types and procedure calls are highlighted.","4":"Its used to highlight syntax for pascal source files from \"http:\/\/www.sapdb.org\". Special SAPDB types and procedure calls are highlighted.","install_details":"au BufRead [v|i|g|h][a-z][a-z]*[0-9][0-9]\\(_[0-9]\\)\\=      setf SAPDB_Pascal","5":"au BufRead [v|i|g|h][a-z][a-z]*[0-9][0-9]\\(_[0-9]\\)\\=      setf SAPDB_Pascal","first_name":"Gert","6":"Gert","last_name":"Gro\u00c3\u009fmann","7":"Gro\u00c3\u009fmann","releases":[{"0":"486","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"SAPDB_Pascal.vim","4":"SAPDB_Pascal.vim","src_id":"1421","5":"1421","creation_date":"1037348023","6":"1037348023"}]},"485":{"script_id":"485","0":"485","script_name":"markjump.vim","1":"markjump.vim","script_type":"ftplugin","2":"ftplugin","summary":"Code transversal functions, move to prev\/next marker, insert\/strip markers.","3":"Code transversal functions, move to prev\/next marker, insert\/strip markers.","description":"This is a normal PLUGIN not ftplugin.\r\n\r\nMarker chars are configurable.\r\nYou can define global or buffer variables to specify the marker chars for both left and right chars. Buffer vars if present are used before global chars \r\ng:L_Marker\r\nb:L_Marker\r\ng:R_Marker\r\nb:R_Marker\r\n\r\nThe default marker chars are the same as Luc Hermitte's bracketing.base.vim which is the same as Stephen Riehm's braketing macros. Which is to say \u00c2\u00ab\u00c2\u00bb\r\n\r\nIf you do not have digraphs enabled these chars are still easy to insert via \r\n<c-k><< which gives you  '\u00c2\u00ab' and <c-k>>> which is '\u00c2\u00bb' (far easier to use the included commands however)\r\n\r\n:MN        Search forward for the next occurance of marker chars\r\n:MP        Search backwards for the next occurance of marker chars\r\n:MI          Insert marker chars, usefull for <c-o>:MI text to have markers around it<cr>\r\n:MIV       Wrap the visual selection (single line) with marker chars\r\n:MA        Append marker chars (like a)\r\n:MAV     Same as :MIV\r\n:MS        Strip marker chars, positioning is a touch picky; place cursor in the markers and all is well.\r\n\r\nInsert mode mappings:\r\n<plug>MjMark         Defaults to `\u00c2\u00a1mark!`        Insert marker chars, cursor AFTER the marker chars.\r\n<plug>MjJump        Defaults to `\u00c2\u00a1jump!`        Jump to the next marker (as :MN)\r\n\r\nVISUAL mode mappings:\r\n<plug>MjMark         Defaults to `\u00c2\u00a1mark!`        Wrap marker chars around the selection. (as MIV)\r\n\r\nNOTE if you already have insert and or visual mappings for \u00c2\u00a1mark!\/\u00c2\u00a1jump! these will NOT be made.\r\n\r\nKey mappings:\r\n<plug>MjPrev           Defaults to <M-Insert> in normal, insert and visual.       Jumps to previous markers, as :MP\r\n<plug>MjNext             Defaults to <M-Del> in normal, insert and visual.        Jumps to next marker, as :MN\r\n<plug>MjInsMarker        Defaults to <M-m> in insert.       Shortcut for `<c-o>:MI ` Just hit <m-m>type your words<cr>\r\n\r\nIf there is gui and has menu adds the following plugin menu items:\r\nPlugin.markjump.Prev  Marker\r\nPlugin.markjump.Next Marker\r\nPlugin.markjump.Insert Marker\r\nPlugin.markjump.Append Marker\r\nPlugin.markjump.Strip Markers\r\n\r\nStrip markers mens to remove the marker chars from either side; cursor generally needs to be within the marker chars.\r\n\r\nThis script would not be what it is with out Luc Hermitte's input!","4":"This is a normal PLUGIN not ftplugin.\r\n\r\nMarker chars are configurable.\r\nYou can define global or buffer variables to specify the marker chars for both left and right chars. Buffer vars if present are used before global chars \r\ng:L_Marker\r\nb:L_Marker\r\ng:R_Marker\r\nb:R_Marker\r\n\r\nThe default marker chars are the same as Luc Hermitte's bracketing.base.vim which is the same as Stephen Riehm's braketing macros. Which is to say \u00c2\u00ab\u00c2\u00bb\r\n\r\nIf you do not have digraphs enabled these chars are still easy to insert via \r\n<c-k><< which gives you  '\u00c2\u00ab' and <c-k>>> which is '\u00c2\u00bb' (far easier to use the included commands however)\r\n\r\n:MN        Search forward for the next occurance of marker chars\r\n:MP        Search backwards for the next occurance of marker chars\r\n:MI          Insert marker chars, usefull for <c-o>:MI text to have markers around it<cr>\r\n:MIV       Wrap the visual selection (single line) with marker chars\r\n:MA        Append marker chars (like a)\r\n:MAV     Same as :MIV\r\n:MS        Strip marker chars, positioning is a touch picky; place cursor in the markers and all is well.\r\n\r\nInsert mode mappings:\r\n<plug>MjMark         Defaults to `\u00c2\u00a1mark!`        Insert marker chars, cursor AFTER the marker chars.\r\n<plug>MjJump        Defaults to `\u00c2\u00a1jump!`        Jump to the next marker (as :MN)\r\n\r\nVISUAL mode mappings:\r\n<plug>MjMark         Defaults to `\u00c2\u00a1mark!`        Wrap marker chars around the selection. (as MIV)\r\n\r\nNOTE if you already have insert and or visual mappings for \u00c2\u00a1mark!\/\u00c2\u00a1jump! these will NOT be made.\r\n\r\nKey mappings:\r\n<plug>MjPrev           Defaults to <M-Insert> in normal, insert and visual.       Jumps to previous markers, as :MP\r\n<plug>MjNext             Defaults to <M-Del> in normal, insert and visual.        Jumps to next marker, as :MN\r\n<plug>MjInsMarker        Defaults to <M-m> in insert.       Shortcut for `<c-o>:MI ` Just hit <m-m>type your words<cr>\r\n\r\nIf there is gui and has menu adds the following plugin menu items:\r\nPlugin.markjump.Prev  Marker\r\nPlugin.markjump.Next Marker\r\nPlugin.markjump.Insert Marker\r\nPlugin.markjump.Append Marker\r\nPlugin.markjump.Strip Markers\r\n\r\nStrip markers mens to remove the marker chars from either side; cursor generally needs to be within the marker chars.\r\n\r\nThis script would not be what it is with out Luc Hermitte's input!","install_details":"This may clash with other bracketing\/mark jump type scripts; I've tried to minimise such colisions by giving way to existing mappings\/commands. Even with existing scripts the commands defined in this script will probably be available, so you can at least take this for a test run to see if it meets your likes.\r\nInstall, drop in PLUGIN (not ftplugin) folder.\r\nUnistall, as easy as removing from your plugin folder. (and if you have made any maps to this you'll want to do something with those as well)\r\nTest drive:\r\ninstall, open a test file and :MI some text<cr>   then move cursor and play wiht :MN and :MP","5":"This may clash with other bracketing\/mark jump type scripts; I've tried to minimise such colisions by giving way to existing mappings\/commands. Even with existing scripts the commands defined in this script will probably be available, so you can at least take this for a test run to see if it meets your likes.\r\nInstall, drop in PLUGIN (not ftplugin) folder.\r\nUnistall, as easy as removing from your plugin folder. (and if you have made any maps to this you'll want to do something with those as well)\r\nTest drive:\r\ninstall, open a test file and :MI some text<cr>   then move cursor and play wiht :MN and :MP","first_name":"Robert","6":"Robert","last_name":"KellyIV","7":"KellyIV","releases":[{"0":"485","vim_version":"6.0","1":"6.0","script_version":"0.29","2":"0.29","version_comment":"Initial upload","3":"Initial upload","package":"markjump.vim","4":"markjump.vim","src_id":"1419","5":"1419","creation_date":"1037318209","6":"1037318209"}]},"484":{"script_id":"484","0":"484","script_name":"ddldbl.vim","1":"ddldbl.vim","script_type":"ftplugin","2":"ftplugin","summary":"Delete Duplicate Lines and Delete Blank Lines.","3":"Delete Duplicate Lines and Delete Blank Lines.","description":"This is just a normal ol plugin; NOT ftplugin (there really should be a plugin option in the type field when adding a new script... *hint* *hint* :) )\r\n\r\nThis is a quick\/simple implimtation to delete duplicate lines (:DDL) and delete blank lines (:DBL)\r\n\r\nBoth commands can take a range and DEFAULT TO THE ENTIRE FILE.\r\nBoth of these commands delete lines so be carefull!\r\n\r\n:DBL (delete blank lines) is little more than a command front end to a :g command.\r\n:DDL (delete duplicate lines) opens folds,  starts at th top of the range and goes down. For each duplicate line found it is :delete\r\nEnd result is you can select a portion of a file and quickily and easily delete blank lines and or delete duplicate lines.","4":"This is just a normal ol plugin; NOT ftplugin (there really should be a plugin option in the type field when adding a new script... *hint* *hint* :) )\r\n\r\nThis is a quick\/simple implimtation to delete duplicate lines (:DDL) and delete blank lines (:DBL)\r\n\r\nBoth commands can take a range and DEFAULT TO THE ENTIRE FILE.\r\nBoth of these commands delete lines so be carefull!\r\n\r\n:DBL (delete blank lines) is little more than a command front end to a :g command.\r\n:DDL (delete duplicate lines) opens folds,  starts at th top of the range and goes down. For each duplicate line found it is :delete\r\nEnd result is you can select a portion of a file and quickily and easily delete blank lines and or delete duplicate lines.","install_details":"Install:\r\nDrop the file into your PLUGIN folder (not ftplugin!)\r\n\r\nUninstall:\r\nSimply remove the file.\r\n\r\nTo Test drive:\r\nJust install and :DDL &&|| :DBL some test file. Uninstall if desired.","5":"Install:\r\nDrop the file into your PLUGIN folder (not ftplugin!)\r\n\r\nUninstall:\r\nSimply remove the file.\r\n\r\nTo Test drive:\r\nJust install and :DDL &&|| :DBL some test file. Uninstall if desired.","first_name":"Robert","6":"Robert","last_name":"KellyIV","7":"KellyIV","releases":[{"0":"484","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"ddldbl.vim","4":"ddldbl.vim","src_id":"1418","5":"1418","creation_date":"1037315897","6":"1037315897"}]},"483":{"script_id":"483","0":"483","script_name":"tagexplorer.vim","1":"tagexplorer.vim","script_type":"utility","2":"utility","summary":"Tag explorer for various programming language files","3":"Tag explorer for various programming language files","description":"Overview\r\n\r\nThe \"Tag Explorer\" plugin provides the following features:\r\n\r\n1. Opens a vertically\/horizontally split Vim window with a list of files in\r\n   a directory. You can list all the tags (functions, classes, structures,\r\n   variables, etc) defined in a file. You can jump to the location where a\r\n   tag is defined. You can edit a selected file. You can browse through the\r\n   directories.\r\n2. Groups the tags by their type and displays them in a foldable tree.\r\n3. When a tag name is selected from the explorer window, positions the cursor\r\n   at the definition of the tag in the source file\r\n4. Can display the prototype of a tag from the tag explorer window.\r\n5. Displays the scope of a tag.\r\n6. The displayed tags can be sorted either by name or by line number.\r\n7. Supports the following programming language files: Assembly, ASP, Awk, C,\r\n   C++, Cobol, Eiffel, Fortran, Java, Lisp, Make, Pascal, Perl, PHP, Python,\r\n   Rexx, Ruby, Scheme, Shell, Slang, Sql, TCL, Verilog, Vim and Yacc.\r\n8. Runs in all the platforms where the exuberant ctags utility and Vim are\r\n   supported (this includes MS-Windows and Unix based systems).\r\n9. Runs in both console\/terminal and GUI versions of Vim.\r\n\r\nThis plugin relies on the exuberant ctags utility to generate the tag\r\nlisting. You can download the exuberant ctags utility from\r\nhttp:\/\/ctags.sourceforge.net. The exuberant ctags utility must be installed\r\nin your system to use this plugin. Exuberant ctags version 5.3 and above is\r\nrecommended.  There is no need for you to create a tags file to use this\r\nplugin.\r\n\r\nInstallation\r\n\r\n1. Copy the tagexplorer.vim script to the $HOME\/.vim\/plugin directory.\r\n   Refer to ':help add-plugin', ':help add-global-plugin' and ':help\r\n   runtimepath' for more details about Vim plugins.\r\n2. Set the TE_Ctags_Path variable to point to the exuberant ctags utility\r\n   path.\r\n3. If you are running a terminal\/console version of Vim and the terminal\r\n   doesn't support changing the window width then set the TE_Adjust_Winwidth\r\n   variable to 0.\r\n4. Restart Vim.\r\n5. You can use the \":TagExplorer\" command to open\/close the tag explorer\r\n   window. \r\n\r\nUsage\r\n\r\nYou can open the tag explorer window using the \":TagExplorer\" command.\r\nInvoking this command will toggle (open or close) the tag explorer window.\r\nYou can map a key to invoke this command:\r\n\r\n              nnoremap <silent> <F8> :TagExplorer<CR>\r\n\r\nAdd the above mapping to your ~\/.vimrc file.\r\n\r\nYou can close the tag explorer window from the tag explorer window by\r\npressing 'q' or using the Vim \":q\" or using one of the Vim window CTRL-W\r\ncommands.\r\n\r\nWhen the tag explorer window is opened, the names of all the directories\r\nand files in the current directory will be displayed.\r\n\r\nWhen a directory name is selected by pressing the <Enter> key or by double\r\nclicking with the mouse, the contents of the selected directory will be\r\ndisplayed. You can go to the parent directory by selecting the \"..\" entry.\r\n\r\nWhen a file name is selected by pressing the <Enter> key or by double\r\nclicking with the mouse, the selected file will be opened in a window.\r\n\r\nYou can display all the tags (variable, function, class, etc) defined in a\r\nfile using the 'o' command.  The tag names will grouped by their type\r\n(variable, function, class, etc) and displayed as a foldable tree using the\r\nVim folding support. You can collapse the tree using the 'c' command. You\r\ncan open the tree using the 'o' command.  You can also use the mouse to\r\nopen\/close the folds. You can use the '+' and '-' keys to open and close the\r\nfolds for a tag type.\r\n\r\nYou can select a tag either by pressing the <Enter> key or by double\r\nclicking the tag name using the mouse.\r\n\r\nFor tags with scope information (like class members, structures inside\r\nstructures, etc), the scope information will be displayed in square brackets\r\n\"[]\" after the tagname.\r\n\r\nBy default, the tag list will be sorted by the order in which the tags\r\nappear in the file. You can sort the tags either by name or by order by\r\npressing the \"s\" key in the tag explorer window.\r\n\r\nYou can display the prototype of a tag by pressing <Spacebar> key when\r\nthe cursor is placed over a tag name.\r\n\r\nYou can update the tags listed for a file by pressing the 'u' key in the tag\r\nexplorer window.\r\n\r\nYou can open a different directory by using the 'g' command. You will be\r\nprompted to enter the name of the directory. You can recall the previously\r\nentered directory names by pressing the Up and Down arrow keys. The last\r\ndisplayed directory name will be the first available name in the history.\r\n\r\nTo get help on the keys, press the \"?\" key in the tag explorer window.\r\n\r\nThis script relies on the Vim \"filetype\" detection mechanism to determine\r\nthe type of the current file. To turn on filetype detection use\r\n\r\n              :filetype on\r\n\r\nThis script will not work in 'compatible' mode.  Make sure the 'compatible'\r\noption is not set.\r\n\r\nConfiguration\r\n\r\nBy changing the following variables you can configure the behavior of this\r\nplugin. Set the following variables in your .vimrc file using the 'let'\r\ncommand.\r\n\r\nThe plugin uses the TE_Ctags_Path variable to locate the ctags utility.  By\r\ndefault, this is set to ctags. Set this variable to point to the location of\r\nthe ctags utility in your system:\r\n\r\n              let TE_Ctags_Path = 'd:\\tools\\ctags.exe'\r\n\r\nBy default, the tag names will be listed in the order in which they are\r\ndefined in the file. You can alphabetically sort the tag names by pressing\r\nthe \"s\" key in the tag explorer window. You can also change the default\r\norder by setting the variable TE_Sort_Type to \"name\" or \"order\":\r\n\r\n              let TE_Sort_Type = \"name\"\r\n\r\nBy default, all the file names in a directory will be displayed in the\r\nexplorer window. If you want to display only selective filenames, you can\r\nset the 'TE_Include_File_Pattern' variable. If this variable is set to empty\r\nstring, all the files in the directory will be displayed. You have to set\r\nthis variable to a Vim regular expression pattern value. For example, to\r\ndisplay only .c and .h files, set this variable to\r\n\r\n              let TE_Include_File_Pattern = '.*\\.c$\\|.*\\.h$'\r\n\r\nYou can set the 'TE_Exclude_File_Pattern' variable to skip file names\r\nmatching a Vim regular expression pattern. For example, to skip the .o, .obj\r\n.bak, core and tags files, set this variable to\r\n\r\n              let TE_Exclude_File_Pattern = '.*\\.o$\\|.*\\.obj$\\|.*\\.bak$' .\r\n                                            '\\|.*\\.swp$\\|core\\|tags'\r\n\r\nBy default, all the sub-directory names in a directory will be displayed in\r\nthe explorer window. If you want to display only selective directories, you\r\ncan set the 'TE_Include_Dir_Pattern' variable. If this variable is set to\r\nempty string, all the sub-directories in the directory will be displayed.\r\nYou have to set this variable to a Vim regular expression pattern value.\r\nFor example, to include only those directories containing vim or unix in the\r\nname, use\r\n\r\n              let TE_Include_Dir_Pattern = '.*vim.*\\|.*unix.*'\r\n\r\nYou can set the 'TE_Exclude_Dir_Pattern' variable to skip directories\r\nmatching a Vim regular expression pattern. By default, this variable is set\r\nto empty. For example, to exclude all the directories starting with obj or\r\ncontaining test, use\r\n\r\n              let TE_Exclude_Dir_Pattern = 'obj.*\\|.*test.*'\r\n\r\nBe default, the tag names will be listed in a vertically split window.  If\r\nyou prefer a horizontally split window, then set the 'TE_Use_Horiz_Window'\r\nvariable to 1. If you are running MS-Windows version of Vim in a MS-DOS\r\ncommand window, then you should use a horizontally split window instead of a\r\nvertically split window.  Also, if you are using an older version of xterm\r\nin a Unix system that doesn't support changing the xterm window width, you\r\nshould use a horizontally split window.\r\n\r\n              let TE_Use_Horiz_Window = 1\r\n\r\nBy default, the vertically split tag explorer window will appear on the left\r\nhand side. If you prefer to open the window on the right hand side, you can\r\nset the TE_Use_Right_Window variable to one:\r\n\r\n              let TE_Use_Right_Window = 1\r\n\r\nYou can also open the tag explorer window on startup using the following\r\ncommand line:\r\n\r\n              $ vim +TagExplorer\r\n\r\nThe default width of the vertically split tag explorer window will be 30.\r\nThis can be changed by modifying the TE_WinWidth variable:\r\n\r\n              let TE_WinWidth = 20\r\n\r\nNote that the value of the 'winwidth' option setting determines the minimum\r\nwidth of the current window. If you set the 'TE_WinWidth' variable to a\r\nvalue less than that of the 'winwidth' option setting, then Vim will use the\r\nvalue of the 'winwidth' option.\r\n\r\nBy default, when the width of the window is less than 100 and a new tag\r\nexplorer window is opened vertically, then the window width will be\r\nincreased by the value set in the TE_WinWidth variable to accomodate the new\r\nwindow.  The value of this variable is used only if you are using a\r\nvertically split tag explorer window.  If your terminal doesn't support\r\nchanging the window width from Vim (older version of xterm running in a Unix\r\nsystem) or if you see any weird problems in the screen due to the change in\r\nthe window width or if you prefer not to adjust the window width then set\r\nthe 'TE_Adjust_Winwidth' variable to 0.  CAUTION: If you are using the\r\nMS-Windows version of Vim in a MS-DOS command window then you must set this\r\nvariable to 0, otherwise the system may hang due to a Vim limitation\r\n(explained in :help win32-problems)\r\n\r\n              let TE_Adjust_Winwidth = 0\r\n","4":"Overview\r\n\r\nThe \"Tag Explorer\" plugin provides the following features:\r\n\r\n1. Opens a vertically\/horizontally split Vim window with a list of files in\r\n   a directory. You can list all the tags (functions, classes, structures,\r\n   variables, etc) defined in a file. You can jump to the location where a\r\n   tag is defined. You can edit a selected file. You can browse through the\r\n   directories.\r\n2. Groups the tags by their type and displays them in a foldable tree.\r\n3. When a tag name is selected from the explorer window, positions the cursor\r\n   at the definition of the tag in the source file\r\n4. Can display the prototype of a tag from the tag explorer window.\r\n5. Displays the scope of a tag.\r\n6. The displayed tags can be sorted either by name or by line number.\r\n7. Supports the following programming language files: Assembly, ASP, Awk, C,\r\n   C++, Cobol, Eiffel, Fortran, Java, Lisp, Make, Pascal, Perl, PHP, Python,\r\n   Rexx, Ruby, Scheme, Shell, Slang, Sql, TCL, Verilog, Vim and Yacc.\r\n8. Runs in all the platforms where the exuberant ctags utility and Vim are\r\n   supported (this includes MS-Windows and Unix based systems).\r\n9. Runs in both console\/terminal and GUI versions of Vim.\r\n\r\nThis plugin relies on the exuberant ctags utility to generate the tag\r\nlisting. You can download the exuberant ctags utility from\r\nhttp:\/\/ctags.sourceforge.net. The exuberant ctags utility must be installed\r\nin your system to use this plugin. Exuberant ctags version 5.3 and above is\r\nrecommended.  There is no need for you to create a tags file to use this\r\nplugin.\r\n\r\nInstallation\r\n\r\n1. Copy the tagexplorer.vim script to the $HOME\/.vim\/plugin directory.\r\n   Refer to ':help add-plugin', ':help add-global-plugin' and ':help\r\n   runtimepath' for more details about Vim plugins.\r\n2. Set the TE_Ctags_Path variable to point to the exuberant ctags utility\r\n   path.\r\n3. If you are running a terminal\/console version of Vim and the terminal\r\n   doesn't support changing the window width then set the TE_Adjust_Winwidth\r\n   variable to 0.\r\n4. Restart Vim.\r\n5. You can use the \":TagExplorer\" command to open\/close the tag explorer\r\n   window. \r\n\r\nUsage\r\n\r\nYou can open the tag explorer window using the \":TagExplorer\" command.\r\nInvoking this command will toggle (open or close) the tag explorer window.\r\nYou can map a key to invoke this command:\r\n\r\n              nnoremap <silent> <F8> :TagExplorer<CR>\r\n\r\nAdd the above mapping to your ~\/.vimrc file.\r\n\r\nYou can close the tag explorer window from the tag explorer window by\r\npressing 'q' or using the Vim \":q\" or using one of the Vim window CTRL-W\r\ncommands.\r\n\r\nWhen the tag explorer window is opened, the names of all the directories\r\nand files in the current directory will be displayed.\r\n\r\nWhen a directory name is selected by pressing the <Enter> key or by double\r\nclicking with the mouse, the contents of the selected directory will be\r\ndisplayed. You can go to the parent directory by selecting the \"..\" entry.\r\n\r\nWhen a file name is selected by pressing the <Enter> key or by double\r\nclicking with the mouse, the selected file will be opened in a window.\r\n\r\nYou can display all the tags (variable, function, class, etc) defined in a\r\nfile using the 'o' command.  The tag names will grouped by their type\r\n(variable, function, class, etc) and displayed as a foldable tree using the\r\nVim folding support. You can collapse the tree using the 'c' command. You\r\ncan open the tree using the 'o' command.  You can also use the mouse to\r\nopen\/close the folds. You can use the '+' and '-' keys to open and close the\r\nfolds for a tag type.\r\n\r\nYou can select a tag either by pressing the <Enter> key or by double\r\nclicking the tag name using the mouse.\r\n\r\nFor tags with scope information (like class members, structures inside\r\nstructures, etc), the scope information will be displayed in square brackets\r\n\"[]\" after the tagname.\r\n\r\nBy default, the tag list will be sorted by the order in which the tags\r\nappear in the file. You can sort the tags either by name or by order by\r\npressing the \"s\" key in the tag explorer window.\r\n\r\nYou can display the prototype of a tag by pressing <Spacebar> key when\r\nthe cursor is placed over a tag name.\r\n\r\nYou can update the tags listed for a file by pressing the 'u' key in the tag\r\nexplorer window.\r\n\r\nYou can open a different directory by using the 'g' command. You will be\r\nprompted to enter the name of the directory. You can recall the previously\r\nentered directory names by pressing the Up and Down arrow keys. The last\r\ndisplayed directory name will be the first available name in the history.\r\n\r\nTo get help on the keys, press the \"?\" key in the tag explorer window.\r\n\r\nThis script relies on the Vim \"filetype\" detection mechanism to determine\r\nthe type of the current file. To turn on filetype detection use\r\n\r\n              :filetype on\r\n\r\nThis script will not work in 'compatible' mode.  Make sure the 'compatible'\r\noption is not set.\r\n\r\nConfiguration\r\n\r\nBy changing the following variables you can configure the behavior of this\r\nplugin. Set the following variables in your .vimrc file using the 'let'\r\ncommand.\r\n\r\nThe plugin uses the TE_Ctags_Path variable to locate the ctags utility.  By\r\ndefault, this is set to ctags. Set this variable to point to the location of\r\nthe ctags utility in your system:\r\n\r\n              let TE_Ctags_Path = 'd:\\tools\\ctags.exe'\r\n\r\nBy default, the tag names will be listed in the order in which they are\r\ndefined in the file. You can alphabetically sort the tag names by pressing\r\nthe \"s\" key in the tag explorer window. You can also change the default\r\norder by setting the variable TE_Sort_Type to \"name\" or \"order\":\r\n\r\n              let TE_Sort_Type = \"name\"\r\n\r\nBy default, all the file names in a directory will be displayed in the\r\nexplorer window. If you want to display only selective filenames, you can\r\nset the 'TE_Include_File_Pattern' variable. If this variable is set to empty\r\nstring, all the files in the directory will be displayed. You have to set\r\nthis variable to a Vim regular expression pattern value. For example, to\r\ndisplay only .c and .h files, set this variable to\r\n\r\n              let TE_Include_File_Pattern = '.*\\.c$\\|.*\\.h$'\r\n\r\nYou can set the 'TE_Exclude_File_Pattern' variable to skip file names\r\nmatching a Vim regular expression pattern. For example, to skip the .o, .obj\r\n.bak, core and tags files, set this variable to\r\n\r\n              let TE_Exclude_File_Pattern = '.*\\.o$\\|.*\\.obj$\\|.*\\.bak$' .\r\n                                            '\\|.*\\.swp$\\|core\\|tags'\r\n\r\nBy default, all the sub-directory names in a directory will be displayed in\r\nthe explorer window. If you want to display only selective directories, you\r\ncan set the 'TE_Include_Dir_Pattern' variable. If this variable is set to\r\nempty string, all the sub-directories in the directory will be displayed.\r\nYou have to set this variable to a Vim regular expression pattern value.\r\nFor example, to include only those directories containing vim or unix in the\r\nname, use\r\n\r\n              let TE_Include_Dir_Pattern = '.*vim.*\\|.*unix.*'\r\n\r\nYou can set the 'TE_Exclude_Dir_Pattern' variable to skip directories\r\nmatching a Vim regular expression pattern. By default, this variable is set\r\nto empty. For example, to exclude all the directories starting with obj or\r\ncontaining test, use\r\n\r\n              let TE_Exclude_Dir_Pattern = 'obj.*\\|.*test.*'\r\n\r\nBe default, the tag names will be listed in a vertically split window.  If\r\nyou prefer a horizontally split window, then set the 'TE_Use_Horiz_Window'\r\nvariable to 1. If you are running MS-Windows version of Vim in a MS-DOS\r\ncommand window, then you should use a horizontally split window instead of a\r\nvertically split window.  Also, if you are using an older version of xterm\r\nin a Unix system that doesn't support changing the xterm window width, you\r\nshould use a horizontally split window.\r\n\r\n              let TE_Use_Horiz_Window = 1\r\n\r\nBy default, the vertically split tag explorer window will appear on the left\r\nhand side. If you prefer to open the window on the right hand side, you can\r\nset the TE_Use_Right_Window variable to one:\r\n\r\n              let TE_Use_Right_Window = 1\r\n\r\nYou can also open the tag explorer window on startup using the following\r\ncommand line:\r\n\r\n              $ vim +TagExplorer\r\n\r\nThe default width of the vertically split tag explorer window will be 30.\r\nThis can be changed by modifying the TE_WinWidth variable:\r\n\r\n              let TE_WinWidth = 20\r\n\r\nNote that the value of the 'winwidth' option setting determines the minimum\r\nwidth of the current window. If you set the 'TE_WinWidth' variable to a\r\nvalue less than that of the 'winwidth' option setting, then Vim will use the\r\nvalue of the 'winwidth' option.\r\n\r\nBy default, when the width of the window is less than 100 and a new tag\r\nexplorer window is opened vertically, then the window width will be\r\nincreased by the value set in the TE_WinWidth variable to accomodate the new\r\nwindow.  The value of this variable is used only if you are using a\r\nvertically split tag explorer window.  If your terminal doesn't support\r\nchanging the window width from Vim (older version of xterm running in a Unix\r\nsystem) or if you see any weird problems in the screen due to the change in\r\nthe window width or if you prefer not to adjust the window width then set\r\nthe 'TE_Adjust_Winwidth' variable to 0.  CAUTION: If you are using the\r\nMS-Windows version of Vim in a MS-DOS command window then you must set this\r\nvariable to 0, otherwise the system may hang due to a Vim limitation\r\n(explained in :help win32-problems)\r\n\r\n              let TE_Adjust_Winwidth = 0\r\n","install_details":"1. Copy the tagexplorer.vim script to the $HOME\/.vim\/plugin directory.\r\n   Refer to ':help add-plugin', ':help add-global-plugin' and ':help\r\n   runtimepath' for more details about Vim plugins.\r\n2. Set the TE_Ctags_Path variable to point to the exuberant ctags utility\r\n   path.\r\n3. If you are running a terminal\/console version of Vim and the terminal\r\n   doesn't support changing the window width then set the TE_Adjust_Winwidth\r\n   variable to 0.\r\n4. Restart Vim.\r\n5. You can use the \":TagExplorer\" command to open\/close the tag explorer\r\n   window. \r\n","5":"1. Copy the tagexplorer.vim script to the $HOME\/.vim\/plugin directory.\r\n   Refer to ':help add-plugin', ':help add-global-plugin' and ':help\r\n   runtimepath' for more details about Vim plugins.\r\n2. Set the TE_Ctags_Path variable to point to the exuberant ctags utility\r\n   path.\r\n3. If you are running a terminal\/console version of Vim and the terminal\r\n   doesn't support changing the window width then set the TE_Adjust_Winwidth\r\n   variable to 0.\r\n4. Restart Vim.\r\n5. You can use the \":TagExplorer\" command to open\/close the tag explorer\r\n   window. \r\n","first_name":"Yegappan","6":"Yegappan","last_name":"Lakshmanan","7":"Lakshmanan","releases":[{"0":"483","vim_version":"6.0","1":"6.0","script_version":"1.2","2":"1.2","version_comment":"1, Added support for refreshing the tags listed for a file.\r\n2. Modified the plugin so that integration with the winmanager plugin will be simple.","3":"1, Added support for refreshing the tags listed for a file.\r\n2. Modified the plugin so that integration with the winmanager plugin will be simple.","package":"tagexplorer.vim","4":"tagexplorer.vim","src_id":"1584","5":"1584","creation_date":"1040922678","6":"1040922678"},{"0":"483","vim_version":"6.0","1":"6.0","script_version":"1.1","2":"1.1","version_comment":"1. Added support for opening tags in a new window.\r\n2. Added support for excluding\/including directories matching the specified pattern.","3":"1. Added support for opening tags in a new window.\r\n2. Added support for excluding\/including directories matching the specified pattern.","package":"tagexplorer.vim","4":"tagexplorer.vim","src_id":"1423","5":"1423","creation_date":"1037397613","6":"1037397613"}]},"482":{"script_id":"482","0":"482","script_name":"cuecat.vim","1":"cuecat.vim","script_type":"utility","2":"utility","summary":"Driver for CueCat barcode scanner","3":"Driver for CueCat barcode scanner","description":"This is a driver for the CueCat barcode scanner that lets you scan barcodes straight into Vim's insert mode.","4":"This is a driver for the CueCat barcode scanner that lets you scan barcodes straight into Vim's insert mode.","install_details":"Just place the downloaded file \"cuecat.vim\" in your plugin directory. To configure different sounds for successful and failed scans, edit the script where it says \"artsplay\".","5":"Just place the downloaded file \"cuecat.vim\" in your plugin directory. To configure different sounds for successful and failed scans, edit the script where it says \"artsplay\".","first_name":"Chung-chieh","6":"Chung-chieh","last_name":"Shan","7":"Shan","releases":[{"0":"482","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"cuecat.vim","4":"cuecat.vim","src_id":"1402","5":"1402","creation_date":"1037105844","6":"1037105844"}]},"481":{"script_id":"481","0":"481","script_name":"cscomment.vim","1":"cscomment.vim","script_type":"utility","2":"utility","summary":"Automates creation of \/\/\/ comments for C# methods","3":"Automates creation of \/\/\/ comments for C# methods","description":"This script will generate the \/\/\/ comment blocks for csharp for methods and constructors.  Simply place the cursor anywhere on the first line of the function prototype and hit <c-t>.  It also works on properties, constructors and classes.\r\n\r\nAdds summary, remarks, params (for all the params in the function), value (if its a property), and returns (if the function returns something.)\r\n\r\nWhile in comment mode you can tab and shift-tab through the tags, and return and backspace work as they should (enter inserts \/\/\/ on the new line and backspace erases \/\/\/ in one bs)\r\n\r\nYou can get back into comment mode by hitting <c-t> on an existing doc comment.\r\n\r\nQuestions, comments, concerns, bugs, ideas, etc, drop me an email.\r\n","4":"This script will generate the \/\/\/ comment blocks for csharp for methods and constructors.  Simply place the cursor anywhere on the first line of the function prototype and hit <c-t>.  It also works on properties, constructors and classes.\r\n\r\nAdds summary, remarks, params (for all the params in the function), value (if its a property), and returns (if the function returns something.)\r\n\r\nWhile in comment mode you can tab and shift-tab through the tags, and return and backspace work as they should (enter inserts \/\/\/ on the new line and backspace erases \/\/\/ in one bs)\r\n\r\nYou can get back into comment mode by hitting <c-t> on an existing doc comment.\r\n\r\nQuestions, comments, concerns, bugs, ideas, etc, drop me an email.\r\n","install_details":"Just drop the script in your plugin directory.  You can modify it to change the map.","5":"Just drop the script in your plugin directory.  You can modify it to change the map.","first_name":"Aaron","6":"Aaron","last_name":"Jensen","7":"Jensen","releases":[{"0":"481","vim_version":"6.0","1":"6.0","script_version":"1.3b","2":"1.3b","version_comment":"-Interfaces are no longer treated as properties\r\n-Formal ref params are now handled properly\r\n-Fixed backspace so it works on the last character.","3":"-Interfaces are no longer treated as properties\r\n-Formal ref params are now handled properly\r\n-Fixed backspace so it works on the last character.","package":"cscomment.vim","4":"cscomment.vim","src_id":"1447","5":"1447","creation_date":"1037826449","6":"1037826449"},{"0":"481","vim_version":"6.0","1":"6.0","script_version":"1.3a","2":"1.3a","version_comment":"-Fixed bug with insert point reworking\r\n-Finished backspace support, it now backspaces the \/\/\/ in one backspace\r\n\r\nAnyone have a suggestion for restoring key mappings (like when to call the restore function... and autocmd or something?  <esc> seems too unreliable.","3":"-Fixed bug with insert point reworking\r\n-Finished backspace support, it now backspaces the \/\/\/ in one backspace\r\n\r\nAnyone have a suggestion for restoring key mappings (like when to call the restore function... and autocmd or something?  <esc> seems too unreliable.","package":"cscomment.vim","4":"cscomment.vim","src_id":"1445","5":"1445","creation_date":"1037813951","6":"1037813951"},{"0":"481","vim_version":"6.0","1":"6.0","script_version":"1.3","2":"1.3","version_comment":"-Fixed bug with things not getting unmapped properly (Note that things will not get unmapped if esc isn't hit to leave insert mode, I'll tackle that tomorrow)\r\n-Made it so properties now get a value tag\r\n-Reworked the way the insert point is found after a tab\/s-tab\r\n-All tags now start out on one line per tag","3":"-Fixed bug with things not getting unmapped properly (Note that things will not get unmapped if esc isn't hit to leave insert mode, I'll tackle that tomorrow)\r\n-Made it so properties now get a value tag\r\n-Reworked the way the insert point is found after a tab\/s-tab\r\n-All tags now start out on one line per tag","package":"cscomment.vim","4":"cscomment.vim","src_id":"1440","5":"1440","creation_date":"1037759950","6":"1037759950"},{"0":"481","vim_version":"6.0","1":"6.0","script_version":"1.2","2":"1.2","version_comment":"-Commenter now allows you to edit your comments and will reshape them as necessary (add params, remove them, etc.) Just press <c-t> on an existing \/\/\/ comment or a function with a \/\/\/ comment.\r\n-Now restores previous imappings\r\n-Cleaned up a bit\r\nIf it deletes any tags you don't want it to, let me know. The only top level tags it remembers are remarks, summary, param, and returns.","3":"-Commenter now allows you to edit your comments and will reshape them as necessary (add params, remove them, etc.) Just press <c-t> on an existing \/\/\/ comment or a function with a \/\/\/ comment.\r\n-Now restores previous imappings\r\n-Cleaned up a bit\r\nIf it deletes any tags you don't want it to, let me know. The only top level tags it remembers are remarks, summary, param, and returns.","package":"cscomment.vim","4":"cscomment.vim","src_id":"1438","5":"1438","creation_date":"1037742488","6":"1037742488"},{"0":"481","vim_version":"6.0","1":"6.0","script_version":"1.1","2":"1.1","version_comment":"<cr> now adds a new line with \/\/\/, useful for long summaries.  <tab> and <s-tab> iterate through summary, params, and return tags so you can fill everything in quickly.","3":"<cr> now adds a new line with \/\/\/, useful for long summaries.  <tab> and <s-tab> iterate through summary, params, and return tags so you can fill everything in quickly.","package":"cscomment.vim","4":"cscomment.vim","src_id":"1405","5":"1405","creation_date":"1037117147","6":"1037117147"},{"0":"481","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"cscomment.vim","4":"cscomment.vim","src_id":"1401","5":"1401","creation_date":"1037103689","6":"1037103689"}]},"480":{"script_id":"480","0":"480","script_name":"toothpik.vim","1":"toothpik.vim","script_type":"color scheme","2":"color scheme","summary":"black on grey color scheme - gvim only - easy on the eyes","3":"black on grey color scheme - gvim only - easy on the eyes","description":"i can look at black on grey all with without eye-strain -- these are not fancy, but they work","4":"i can look at black on grey all with without eye-strain -- these are not fancy, but they work","install_details":"plop it in your colors path and then enter \\\\\\':colo toothpik\\\\\\'","5":"plop it in your colors path and then enter \\\\\\':colo toothpik\\\\\\'","first_name":"scott","6":"scott","last_name":"cunningham","7":"cunningham","releases":[{"0":"480","vim_version":"7.0","1":"7.0","script_version":".3","2":".3","version_comment":"white comments and fancier intro","3":"white comments and fancier intro","package":"toothpik.vim","4":"toothpik.vim","src_id":"6115","5":"6115","creation_date":"1156967118","6":"1156967118"},{"0":"480","vim_version":"6.0","1":"6.0","script_version":"0.2","2":"0.2","version_comment":"after seeing toothpik in the \\\"broken\\\" section of script_id=625 i removed the font=\\'Fixedsys\\' -- sorry about that","3":"after seeing toothpik in the \\\"broken\\\" section of script_id=625 i removed the font=\\'Fixedsys\\' -- sorry about that","package":"toothpik.vim","4":"toothpik.vim","src_id":"4410","5":"4410","creation_date":"1120564955","6":"1120564955"},{"0":"480","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"toothpik.vim","4":"toothpik.vim","src_id":"1400","5":"1400","creation_date":"1037092424","6":"1037092424"}]},"479":{"script_id":"479","0":"479","script_name":"MultipleSearch","1":"MultipleSearch","script_type":"utility","2":"utility","summary":"Highlight multiple searches at the same time, each with a different color.","3":"Highlight multiple searches at the same time, each with a different color.","description":"MultipleSearch allows you to have the results of multiple searches displayed\r\non the screen at the same time.  Each search highlights its results in a\r\ndifferent color, and all searches are displayed at once.  After the maximum\r\nnumber of colors is used, the script starts over with the first color.\r\n \r\nThe command syntax is: \r\n:Search <pattern1> \r\nwhich will highlight all occurrences of <pattern1> in the current buffer.  A\r\nsubsequent :Search <pattern2> will highlight all occurrences of <pattern2>\r\nin the current buffer, retaining the highlighting of <pattern1> as well.\r\n<pattern1> and <pattern2> are any search pattern like you would use in a\r\nnormal \/<pattern> search.\r\n\r\nThe :Search command honors Vim's 'ignorecase' and 'smartcase' settings for\r\nits own search.  You can use the \\c and \\C flags in the search pattern to\r\nforce case matching no matter the setting of 'ignorecase' and 'smartcase'.\r\n\r\nThe :SearchBuffers command works just like :Search, but the search occurs in all currently listed buffers (i.e., appear in the output of :ls).  The match in all buffers will have the same color.  This is different than  :bufdo Search <pattern> because in that case, each buffer will highlight the match in a different color.  Thanks to Jeff Mei for the suggestion!\r\n\r\nTo clear the highlighting, issue the command\r\n:SearchReset (for the current buffer) or :SearchBuffersReset (for all buffers).\r\n \r\nYou can specify the maximum number of different colors to use by setting the\r\ng:MultipleSearchMaxColors variable in your .vimrc.  The default setting is\r\nfour, but the script should handle as much as your terminal \/ GUI can\r\ndisplay.  The g:MultipleSearchColorSequence variable lets you list the\r\ncolors you want displayed, and in what order.  To make the text more\r\nreadable, you can set the g:MultipleSearchTextColorSequence variable to a\r\nlist of colors for the text, each position corresponding to the color in the\r\nsame position in g:MultipleSearchColorSequence.\r\n\r\nIf you change one of the preference variables, you can issue the command\r\n:SearchReinit\r\nto update the script with your new selections.","4":"MultipleSearch allows you to have the results of multiple searches displayed\r\non the screen at the same time.  Each search highlights its results in a\r\ndifferent color, and all searches are displayed at once.  After the maximum\r\nnumber of colors is used, the script starts over with the first color.\r\n \r\nThe command syntax is: \r\n:Search <pattern1> \r\nwhich will highlight all occurrences of <pattern1> in the current buffer.  A\r\nsubsequent :Search <pattern2> will highlight all occurrences of <pattern2>\r\nin the current buffer, retaining the highlighting of <pattern1> as well.\r\n<pattern1> and <pattern2> are any search pattern like you would use in a\r\nnormal \/<pattern> search.\r\n\r\nThe :Search command honors Vim's 'ignorecase' and 'smartcase' settings for\r\nits own search.  You can use the \\c and \\C flags in the search pattern to\r\nforce case matching no matter the setting of 'ignorecase' and 'smartcase'.\r\n\r\nThe :SearchBuffers command works just like :Search, but the search occurs in all currently listed buffers (i.e., appear in the output of :ls).  The match in all buffers will have the same color.  This is different than  :bufdo Search <pattern> because in that case, each buffer will highlight the match in a different color.  Thanks to Jeff Mei for the suggestion!\r\n\r\nTo clear the highlighting, issue the command\r\n:SearchReset (for the current buffer) or :SearchBuffersReset (for all buffers).\r\n \r\nYou can specify the maximum number of different colors to use by setting the\r\ng:MultipleSearchMaxColors variable in your .vimrc.  The default setting is\r\nfour, but the script should handle as much as your terminal \/ GUI can\r\ndisplay.  The g:MultipleSearchColorSequence variable lets you list the\r\ncolors you want displayed, and in what order.  To make the text more\r\nreadable, you can set the g:MultipleSearchTextColorSequence variable to a\r\nlist of colors for the text, each position corresponding to the color in the\r\nsame position in g:MultipleSearchColorSequence.\r\n\r\nIf you change one of the preference variables, you can issue the command\r\n:SearchReinit\r\nto update the script with your new selections.","install_details":"Copy the MultipleSearch.vim file into your local plugins directory, restart (g)vim, and you are ready to go.","5":"Copy the MultipleSearch.vim file into your local plugins directory, restart (g)vim, and you are ready to go.","first_name":"Dan","6":"Dan","last_name":"Sharp","7":"Sharp","releases":[{"0":"479","vim_version":"6.0","1":"6.0","script_version":"1.3","2":"1.3","version_comment":"New mappings:\r\nn and N : jump to next \/ previous match of current ':Search' pattern\r\n<Leader>n and <Leader>N : jump to next \/ previous ':Search'-ed pattern\r\n<Leader>* : perform a :Search of the word under the cursor \/ visually selected region\r\n\r\nOther changes:\r\nSupports Vim 7 autoload mechanism, but will still work under Vim 6\r\nBug fixes to escape characters in the search pattern\r\n","3":"New mappings:\r\nn and N : jump to next \/ previous match of current ':Search' pattern\r\n<Leader>n and <Leader>N : jump to next \/ previous ':Search'-ed pattern\r\n<Leader>* : perform a :Search of the word under the cursor \/ visually selected region\r\n\r\nOther changes:\r\nSupports Vim 7 autoload mechanism, but will still work under Vim 6\r\nBug fixes to escape characters in the search pattern\r\n","package":"MultipleSearch.zip","4":"MultipleSearch.zip","src_id":"9276","5":"9276","creation_date":"1222180336","6":"1222180336"},{"0":"479","vim_version":"6.0","1":"6.0","script_version":"1.2.1","2":"1.2.1","version_comment":"Add the :SearchBuffersReset command to clear the highlighting in all buffers from the new :SearchBuffers command.","3":"Add the :SearchBuffersReset command to clear the highlighting in all buffers from the new :SearchBuffers command.","package":"MultipleSearch.vim","4":"MultipleSearch.vim","src_id":"2395","5":"2395","creation_date":"1066114551","6":"1066114551"},{"0":"479","vim_version":"6.0","1":"6.0","script_version":"1.2","2":"1.2","version_comment":"Added the :SearchBuffers command to perform the same search in all open buffers.  This is different than ':bufdo Search' where each buffer will have the match highlighted in a different color.","3":"Added the :SearchBuffers command to perform the same search in all open buffers.  This is different than ':bufdo Search' where each buffer will have the match highlighted in a different color.","package":"MultipleSearch.vim","4":"MultipleSearch.vim","src_id":"2393","5":"2393","creation_date":"1066053901","6":"1066053901"},{"0":"479","vim_version":"6.0","1":"6.0","script_version":"1.1","2":"1.1","version_comment":"- :Search command now respects Vim's 'ignorecase' and 'smartcase' settings.\r\n- User-defined color sequence can be used for searches.\r\n- Maximum number of colors that can be used is limited only by the operating system.","3":"- :Search command now respects Vim's 'ignorecase' and 'smartcase' settings.\r\n- User-defined color sequence can be used for searches.\r\n- Maximum number of colors that can be used is limited only by the operating system.","package":"MultipleSearch.vim","4":"MultipleSearch.vim","src_id":"1435","5":"1435","creation_date":"1037690111","6":"1037690111"},{"0":"479","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"MultipleSearch.vim","4":"MultipleSearch.vim","src_id":"1394","5":"1394","creation_date":"1037002275","6":"1037002275"}]},"478":{"script_id":"478","0":"478","script_name":"aj.vim","1":"aj.vim","script_type":"syntax","2":"syntax","summary":"Syntax highlighting for AsepctJ source files","3":"Syntax highlighting for AsepctJ source files","description":"This is my first attempt to create a syntax file :).\r\nI am working with AspectJ lateley and decided to create a syntax file for the language.\r\nFor now, highliting takes care of all AspectJ keywords.\r\n\r\nAll AspectJ code should be inside a file with extension .aj\r\n\r\nTo learn more about AspectJ: http:\/\/aspectj.org","4":"This is my first attempt to create a syntax file :).\r\nI am working with AspectJ lateley and decided to create a syntax file for the language.\r\nFor now, highliting takes care of all AspectJ keywords.\r\n\r\nAll AspectJ code should be inside a file with extension .aj\r\n\r\nTo learn more about AspectJ: http:\/\/aspectj.org","install_details":"Place this file into your <HOME>\/.vim\/syntax\r\n\r\nYou can then enable syntax highliting manually \r\n: set syntax=aj.vim\r\n\r\nOr for automatic file detection add the following to your filetype.vim:\r\n\" AspectJ\r\nau BufNewFile,BufRead *.aj,     setf aj\r\n\r\n","5":"Place this file into your <HOME>\/.vim\/syntax\r\n\r\nYou can then enable syntax highliting manually \r\n: set syntax=aj.vim\r\n\r\nOr for automatic file detection add the following to your filetype.vim:\r\n\" AspectJ\r\nau BufNewFile,BufRead *.aj,     setf aj\r\n\r\n","first_name":"Therapon","6":"Therapon","last_name":"Skotiniotis","7":"Skotiniotis","releases":[{"0":"478","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"aj.vim","4":"aj.vim","src_id":"1393","5":"1393","creation_date":"1037001469","6":"1037001469"}]},"477":{"script_id":"477","0":"477","script_name":"python.vim","1":"python.vim","script_type":"ftplugin","2":"ftplugin","summary":"python compiler script","3":"python compiler script","description":"a very basic python compiler script. The last line of errorformat \r\n              \\%-G%.%#\r\nis meant to suppress all  further error messages after the traceback has been dealt with so that it will be possible to use :clast to go to the last error location which in most cases in Python is the one that has caused the error to happen. \r\nPlease note that if python is not in the path you have to edit the line \r\nsetlocal makeprg=python\r\nso that it contains the path of the python interpreter (e.g. c:\\python22\\python).\r\nAlso, if you want always to make the current file you may wish to add  a\r\n\\ %\r\nto the same line, so that:\r\nsetlocal makeprg=python\r\nshould then look like:\r\nsetlocal makeprg=python\\ %\r\n(Thanks to Guy Oliver for this tip).\r\n\r\nIf you want to syntaxcheck the current python file without executing it, you could use the following function (from python_box.vim):\r\n\r\nfunction! CheckPythonSyntax()\r\n  let curfile = bufname(\"%\")\r\n  exec \":make \" . \"-c \" . \"\\\"import py_compile; py_compile.compile(r'\" . bufname(\"%\") . \"')\\\"\"\r\nendfunction\r\n","4":"a very basic python compiler script. The last line of errorformat \r\n              \\%-G%.%#\r\nis meant to suppress all  further error messages after the traceback has been dealt with so that it will be possible to use :clast to go to the last error location which in most cases in Python is the one that has caused the error to happen. \r\nPlease note that if python is not in the path you have to edit the line \r\nsetlocal makeprg=python\r\nso that it contains the path of the python interpreter (e.g. c:\\python22\\python).\r\nAlso, if you want always to make the current file you may wish to add  a\r\n\\ %\r\nto the same line, so that:\r\nsetlocal makeprg=python\r\nshould then look like:\r\nsetlocal makeprg=python\\ %\r\n(Thanks to Guy Oliver for this tip).\r\n\r\nIf you want to syntaxcheck the current python file without executing it, you could use the following function (from python_box.vim):\r\n\r\nfunction! CheckPythonSyntax()\r\n  let curfile = bufname(\"%\")\r\n  exec \":make \" . \"-c \" . \"\\\"import py_compile; py_compile.compile(r'\" . bufname(\"%\") . \"')\\\"\"\r\nendfunction\r\n","install_details":"just add to the compiler plugin directory","5":"just add to the compiler plugin directory","first_name":"Christoph","6":"Christoph","last_name":"Herzog","7":"Herzog","releases":[{"0":"477","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"python.vim","4":"python.vim","src_id":"1392","5":"1392","creation_date":"1036939211","6":"1036939211"}]},"476":{"script_id":"476","0":"476","script_name":"Transparent","1":"Transparent","script_type":"color scheme","2":"color scheme","summary":"Nice colorscheme for both, console and gui versions of vim","3":"Nice colorscheme for both, console and gui versions of vim","description":"Yet another colorscheme for vim. It uses dark dark blue background in gui and \"transparent\" in console (looks nice when vim is started from transparent aterm).\r\n\r\nScreenshots:\r\n\r\nGVim - http:\/\/people.altlinux.ru\/~raorn\/gvim-transparent.png (25K)\r\nVim (in transparent aterm) - http:\/\/people.altlinux.ru\/~raorn\/vim-transparent.png (245K)","4":"Yet another colorscheme for vim. It uses dark dark blue background in gui and \"transparent\" in console (looks nice when vim is started from transparent aterm).\r\n\r\nScreenshots:\r\n\r\nGVim - http:\/\/people.altlinux.ru\/~raorn\/gvim-transparent.png (25K)\r\nVim (in transparent aterm) - http:\/\/people.altlinux.ru\/~raorn\/vim-transparent.png (245K)","install_details":"Put transparent.vim into \"colors\" directory in $VIMRUNTIME and run \":color transparent\" command.","5":"Put transparent.vim into \"colors\" directory in $VIMRUNTIME and run \":color transparent\" command.","first_name":"Sir","6":"Sir","last_name":"Raorn","7":"Raorn","releases":[{"0":"476","vim_version":"6.0","1":"6.0","script_version":"1.2.1","2":"1.2.1","version_comment":"DarkGreen sometimes is too dark.  Changed PreProc guifg to #00aa00.","3":"DarkGreen sometimes is too dark.  Changed PreProc guifg to #00aa00.","package":"transparent.vim","4":"transparent.vim","src_id":"5674","5":"5674","creation_date":"1147252347","6":"1147252347"},{"0":"476","vim_version":"6.0","1":"6.0","script_version":"1.2","2":"1.2","version_comment":"More updates for vim7 (still usable with 6.x).  Added Cursor* and TabLine* highlightings.","3":"More updates for vim7 (still usable with 6.x).  Added Cursor* and TabLine* highlightings.","package":"transparent.vim","4":"transparent.vim","src_id":"5655","5":"5655","creation_date":"1147063703","6":"1147063703"},{"0":"476","vim_version":"6.0","1":"6.0","script_version":"1.1","2":"1.1","version_comment":"Added Pmenu* and Spell* highlightings (vim7, if'ed)","3":"Added Pmenu* and Spell* highlightings (vim7, if'ed)","package":"transparent.vim","4":"transparent.vim","src_id":"4906","5":"4906","creation_date":"1135069950","6":"1135069950"},{"0":"476","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"transparent.vim","4":"transparent.vim","src_id":"1390","5":"1390","creation_date":"1036905075","6":"1036905075"}]},"475":{"script_id":"475","0":"475","script_name":"LaTeX-Suite (aka Vim-LaTeX)","1":"LaTeX-Suite (aka Vim-LaTeX)","script_type":"ftplugin","2":"ftplugin","summary":"A rich set of tools for editing LaTeX","3":"A rich set of tools for editing LaTeX","description":"Vim-LaTeX (aka LaTeX-suite) is a mature project which aims at bringing\r\ntogether the rich set of LaTeX tools the vim community has produced over\r\nthe years into one comprehensive package. It provides a set of tools\r\nwhich enable you to do all your LaTeX-ing without needing to quit Vim.\r\n\r\nVim-LaTeX has its own web-page at:\r\n\r\nhttp:\/\/vim-latex.sf.net\/\r\n\r\nPlease visit there to get the latest version, documentation, screen shots etc.\r\n\r\nA brief (not complete) list of the features currently supported by\r\nVim-LaTeX are as follows:\r\n\r\n* Editing:  Latex-Suite ships with a very comprehensive set of insert\r\n  mode and visual mode mappings and menu items to typeset most of the\r\n  LaTeX elements. These range from 3 letter insert mode mappings which\r\n  insert a skeleton of common typesetting elements to visual mode\r\n  mappings which enclose the selected region in braces, parentheses,\r\n  etc. The mappings can also be accessed via the menus.\r\n\r\n* Compiling: You can compile the tex file from within vim. The list of\r\n  errors is shown in a quickfix window so you can directly go to the\r\n  location of an error. The compiler plugin can be dynamically\r\n  reconfigured to show you more or less warnings.\r\n\r\n* Viewing: By pressing a key from within vim, the .dvi viewer is started\r\n  up. You can also do forward and inverse searching on your .dvi file\r\n  from within vim.\r\n\r\n* Folding: Latex-suite ships with the plugin SyntaxFolds.vim which is\r\n  a plugin for creating \"fake\" syntax folds on the fly. The fold method\r\n  is actually manual but the folding is based on LaTeX syntax. This\r\n  offers a speed increase over regular syntax folding. When you open up\r\n  a LaTeX file, all the portions will be automatically folded up.\r\n\r\n* Packages: This module provides ways of customizing the menus based on\r\n  which packages are being used in the current LaTeX file. When\r\n  latex-suite first starts up, it scans the latex-master-file for\r\n  \\usepackage{name} lines and if the corresponding package is found in\r\n  the latex-suite\/packages\/ directory, then creates a sub-menu based on\r\n  the specification found in that file. See the list of currently\r\n  supported packages.\r\n\r\n* LaTeX help file: Latex-suite ships with the standard texinfo file\r\n  translated into vim help format so that you can get help for common\r\n  latex commands from within vim. You can view the html version of this\r\n  file here.\r\n\r\n* Dictionary: Latex-suite ships with a dictionary with over 600 LaTeX\r\n  commands, which speeds up typing using the CTRL-X_d command of vim.\r\n\r\n* Customized Templates: Latex-suite ships with some commonly used latex\r\n  templates. It is trivial to add your own templates. The templates can\r\n  contain dynamic data such as time of creation etc. See list of current\r\n  templates.\r\n\r\n* Customized Macros: Latex-suite makes it easy to add custom macros,\r\n  again with the possibility of dynamic content and automatic cursor\r\n  placement.\r\n\r\n\r\nSee\r\n\r\nhttp:\/\/vim-latex.sf.net\/index.php?subject=weare\r\n\r\nfor the list of maintainers \/ how to contact us.Vim-LaTeX is currently maintained\r\nby\r\n\r\nSrinath Avadhanula\r\nMikolaj Machowski\r\nBenji Fisher\r\n\r\n","4":"Vim-LaTeX (aka LaTeX-suite) is a mature project which aims at bringing\r\ntogether the rich set of LaTeX tools the vim community has produced over\r\nthe years into one comprehensive package. It provides a set of tools\r\nwhich enable you to do all your LaTeX-ing without needing to quit Vim.\r\n\r\nVim-LaTeX has its own web-page at:\r\n\r\nhttp:\/\/vim-latex.sf.net\/\r\n\r\nPlease visit there to get the latest version, documentation, screen shots etc.\r\n\r\nA brief (not complete) list of the features currently supported by\r\nVim-LaTeX are as follows:\r\n\r\n* Editing:  Latex-Suite ships with a very comprehensive set of insert\r\n  mode and visual mode mappings and menu items to typeset most of the\r\n  LaTeX elements. These range from 3 letter insert mode mappings which\r\n  insert a skeleton of common typesetting elements to visual mode\r\n  mappings which enclose the selected region in braces, parentheses,\r\n  etc. The mappings can also be accessed via the menus.\r\n\r\n* Compiling: You can compile the tex file from within vim. The list of\r\n  errors is shown in a quickfix window so you can directly go to the\r\n  location of an error. The compiler plugin can be dynamically\r\n  reconfigured to show you more or less warnings.\r\n\r\n* Viewing: By pressing a key from within vim, the .dvi viewer is started\r\n  up. You can also do forward and inverse searching on your .dvi file\r\n  from within vim.\r\n\r\n* Folding: Latex-suite ships with the plugin SyntaxFolds.vim which is\r\n  a plugin for creating \"fake\" syntax folds on the fly. The fold method\r\n  is actually manual but the folding is based on LaTeX syntax. This\r\n  offers a speed increase over regular syntax folding. When you open up\r\n  a LaTeX file, all the portions will be automatically folded up.\r\n\r\n* Packages: This module provides ways of customizing the menus based on\r\n  which packages are being used in the current LaTeX file. When\r\n  latex-suite first starts up, it scans the latex-master-file for\r\n  \\usepackage{name} lines and if the corresponding package is found in\r\n  the latex-suite\/packages\/ directory, then creates a sub-menu based on\r\n  the specification found in that file. See the list of currently\r\n  supported packages.\r\n\r\n* LaTeX help file: Latex-suite ships with the standard texinfo file\r\n  translated into vim help format so that you can get help for common\r\n  latex commands from within vim. You can view the html version of this\r\n  file here.\r\n\r\n* Dictionary: Latex-suite ships with a dictionary with over 600 LaTeX\r\n  commands, which speeds up typing using the CTRL-X_d command of vim.\r\n\r\n* Customized Templates: Latex-suite ships with some commonly used latex\r\n  templates. It is trivial to add your own templates. The templates can\r\n  contain dynamic data such as time of creation etc. See list of current\r\n  templates.\r\n\r\n* Customized Macros: Latex-suite makes it easy to add custom macros,\r\n  again with the possibility of dynamic content and automatic cursor\r\n  placement.\r\n\r\n\r\nSee\r\n\r\nhttp:\/\/vim-latex.sf.net\/index.php?subject=weare\r\n\r\nfor the list of maintainers \/ how to contact us.Vim-LaTeX is currently maintained\r\nby\r\n\r\nSrinath Avadhanula\r\nMikolaj Machowski\r\nBenji Fisher\r\n\r\n","install_details":"The installation instructions (along with the latest stable versions of\r\nLaTeX-suite) are maintained at:\r\n\r\nhttp:\/\/vim-latex.sf.net\/index.php?subject=download\r\n\r\n","5":"The installation instructions (along with the latest stable versions of\r\nLaTeX-suite) are maintained at:\r\n\r\nhttp:\/\/vim-latex.sf.net\/index.php?subject=download\r\n\r\n","first_name":"Srinath","6":"Srinath","last_name":"Avadhanula","7":"Avadhanula","releases":[{"0":"475","vim_version":"6.0","1":"6.0","script_version":"1.5","2":"1.5","version_comment":"A vastly improved and bug-fixed version of latex-suite.\r\n\r\nSee \r\nRelease Notes: http:\/\/vim-latex.sourceforge.net\/download\/RELEASE-1.5.txt\r\nChangelog: http:\/\/vim-latex.sourceforge.net\/vimfiles\/ftplugin\/latex-suite\/ChangeLog\r\n\r\nNOTE: The Changelog at this moment suffers from excessive verbosity since it is            automatically generated.\r\n\r\nPlease note that releases are made much more regularly on the vim-latex download page at:\r\n\r\nhttp:\/\/vim-latex.sourceforge.net\/index.php?subject=download&title=Download","3":"A vastly improved and bug-fixed version of latex-suite.\r\n\r\nSee \r\nRelease Notes: http:\/\/vim-latex.sourceforge.net\/download\/RELEASE-1.5.txt\r\nChangelog: http:\/\/vim-latex.sourceforge.net\/vimfiles\/ftplugin\/latex-suite\/ChangeLog\r\n\r\nNOTE: The Changelog at this moment suffers from excessive verbosity since it is            automatically generated.\r\n\r\nPlease note that releases are made much more regularly on the vim-latex download page at:\r\n\r\nhttp:\/\/vim-latex.sourceforge.net\/index.php?subject=download&title=Download","package":"latexSuite-1.5.tar.gz","4":"latexSuite-1.5.tar.gz","src_id":"2535","5":"2535","creation_date":"1070250777","6":"1070250777"},{"0":"475","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"latexSuite.zip","4":"latexSuite.zip","src_id":"1384","5":"1384","creation_date":"1036677791","6":"1036677791"}]},"474":{"script_id":"474","0":"474","script_name":"SearchComplete","1":"SearchComplete","script_type":"utility","2":"utility","summary":"Tab completion of words inside of a search ('\/')","3":"Tab completion of words inside of a search ('\/')","description":"Call me lazy but I wanted to be able to tab-complete words while typing in a search and I have always been up to a challange.  After learning a lot more about vim and key mapping then I ever knew before, this is the result, working tab completion inside a search.","4":"Call me lazy but I wanted to be able to tab-complete words while typing in a search and I have always been up to a challange.  After learning a lot more about vim and key mapping then I ever knew before, this is the result, working tab completion inside a search.","install_details":"Simply drop this file into your plugin directory.","5":"Simply drop this file into your plugin directory.","first_name":"Chris","6":"Chris","last_name":"Russell","7":"Russell","releases":[{"0":"474","vim_version":"6.0","1":"6.0","script_version":"1.1","2":"1.1","version_comment":"Bug fix: convert file to unix eol","3":"Bug fix: convert file to unix eol","package":"SearchComplete.vim","4":"SearchComplete.vim","src_id":"1388","5":"1388","creation_date":"1036738595","6":"1036738595"},{"0":"474","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"SearchComplete.vim","4":"SearchComplete.vim","src_id":"1378","5":"1378","creation_date":"1036499497","6":"1036499497"}]},"473":{"script_id":"473","0":"473","script_name":"BlockComment.vim","1":"BlockComment.vim","script_type":"utility","2":"utility","summary":"Simple commenting and uncommenting of blocks of code","3":"Simple commenting and uncommenting of blocks of code","description":"The goal behind BlockComment was to be able to comment and uncomment blocks of code easily and to nicely format the comment block.  \r\nMy initial inspiration was EnhancedCommentify (vimscript #23) and ToggleCommentify (vimscript #4) but I have since rewritten BlockComment from the ground up to simplify the code and provide for greater ease of use and maintainability.\r\n","4":"The goal behind BlockComment was to be able to comment and uncomment blocks of code easily and to nicely format the comment block.  \r\nMy initial inspiration was EnhancedCommentify (vimscript #23) and ToggleCommentify (vimscript #4) but I have since rewritten BlockComment from the ground up to simplify the code and provide for greater ease of use and maintainability.\r\n","install_details":"Simply drop this file into your plugin directory.\r\nUse '.c' to comment code and '.C' to uncomment code.","5":"Simply drop this file into your plugin directory.\r\nUse '.c' to comment code and '.C' to uncomment code.","first_name":"Chris","6":"Chris","last_name":"Russell","7":"Russell","releases":[{"0":"473","vim_version":"6.0","1":"6.0","script_version":"1.1","2":"1.1","version_comment":"Bug fix: convert file to unix eol","3":"Bug fix: convert file to unix eol","package":"BlockComment.vim","4":"BlockComment.vim","src_id":"1387","5":"1387","creation_date":"1036738561","6":"1036738561"},{"0":"473","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"BlockComment.vim","4":"BlockComment.vim","src_id":"1377","5":"1377","creation_date":"1036498802","6":"1036498802"}]},"472":{"script_id":"472","0":"472","script_name":"mup.vim","1":"mup.vim","script_type":"syntax","2":"syntax","summary":"MUP syntax file for musical score publication and auto-MIDI generation","3":"MUP syntax file for musical score publication and auto-MIDI generation","description":"This is a first draft of syntax coloring\/highlighting for the Mup file format.\r\nMup file format is a musical publication format by Arkkra Enterprise http:\/\/www.arkkra.com\r\nThis syntax file is not created\/maintained by Arkkra Enterprise","4":"This is a first draft of syntax coloring\/highlighting for the Mup file format.\r\nMup file format is a musical publication format by Arkkra Enterprise http:\/\/www.arkkra.com\r\nThis syntax file is not created\/maintained by Arkkra Enterprise","install_details":"You can unzip those files into their respective directories under vimfiles or your .vim directory, but if you already have the syntax.vim and filetype.vim, you have to append to your own files instead of overwriting them. Or, you can place it in $VIMRUNTIME\/syntax and use :ru syntax\/mup.vim to load it.","5":"You can unzip those files into their respective directories under vimfiles or your .vim directory, but if you already have the syntax.vim and filetype.vim, you have to append to your own files instead of overwriting them. Or, you can place it in $VIMRUNTIME\/syntax and use :ru syntax\/mup.vim to load it.","first_name":"Soon Wah","6":"Soon Wah","last_name":"Chua","7":"Chua","releases":[{"0":"472","vim_version":"6.0","1":"6.0","script_version":"0.2","2":"0.2","version_comment":"Added the syntax.vim and filetype.vim files for autoloading the syntax when MUP files are used. Take note that if you have existing local copies of syntax.vim and filetype.vim files, you have to append the content of these files to your local copies instead of overwriting them, if you still want your other settings in these files.","3":"Added the syntax.vim and filetype.vim files for autoloading the syntax when MUP files are used. Take note that if you have existing local copies of syntax.vim and filetype.vim files, you have to append the content of these files to your local copies instead of overwriting them, if you still want your other settings in these files.","package":"mup-0.2.zip","4":"mup-0.2.zip","src_id":"1417","5":"1417","creation_date":"1037308681","6":"1037308681"},{"0":"472","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"mup.vim","4":"mup.vim","src_id":"1375","5":"1375","creation_date":"1036447611","6":"1036447611"}]},"471":{"script_id":"471","0":"471","script_name":"cream-vimabbrev","1":"cream-vimabbrev","script_type":"utility","2":"utility","summary":"Convert Vim script command and option names between full and abbreviated forms","3":"Convert Vim script command and option names between full and abbreviated forms","description":"\r\n*** WARNING! ***\r\nThis script is very much a work in progress and has several known bugs and likely many unknown ones. You will find little automatic success with it. It is being provided here for information only. Be hereby warned that using these functions will tear valid Vim script limb from limb leaving a trail of crying and gnashing of teeth behind.\r\n\r\nThat said, we would very much appreciate your feedback on correcting said anamolies. Feel free to forward suggestions or fixes to:\r\n  digitect (at) mindspring \u00e2\u0080\u00a2 com\r\n\r\n\r\nDescription:\r\n\r\nThis script is currently one half of a set of functions to convert Vim command and option names between short\/abbreviated and long\/full name forms. (Ex. \"fu\" => \"function\", \"e\" => \"edit\") These are sometimes indicated like \"fu[nction]\" or  \"e[dit]\".\r\n\r\nThe script currently only converts from short to long. Based on my own preferences, I am less motivated to do the other side. ;) But I conceed it would be useful to have a polished routine to help going back and forth between the two for those with preferences for either readability or bandwidth conservation.\r\n\r\nThe script contains plenty of working debris at the bottom which shouldn't impact the code above. I have tried to be as complete as possible by using Vim's own syntax and option lists to compile the substitutions from. However you may notice omissions.\r\n\r\nDependancies:\r\n\r\nmultvals.vim (http:\/\/www.vim.org\/script.php?script_id=171)\r\n  by Hari Krishna Dara, for the arrays of items to be substituted.\r\n\r\nToDo:\r\n\r\n* Avoid mapping syntaxes.\r\n* Avoid heinous \"normal af|g^\" => \"normal af|global^\" error\r\n* Avoid heinous \"normal j+r\" => \"normal j+read\" error\r\n* Add whitespace separators around evaluation operators and concatenation symbols.\r\n\r\n\r\nThis is one of many custom utilities and functions for gVim from the Cream project (http:\/\/cream.sourceforge.net), a configuration of Vim for those of us familiar with Apple and Windows software.\r\n\r\n","4":"\r\n*** WARNING! ***\r\nThis script is very much a work in progress and has several known bugs and likely many unknown ones. You will find little automatic success with it. It is being provided here for information only. Be hereby warned that using these functions will tear valid Vim script limb from limb leaving a trail of crying and gnashing of teeth behind.\r\n\r\nThat said, we would very much appreciate your feedback on correcting said anamolies. Feel free to forward suggestions or fixes to:\r\n  digitect (at) mindspring \u00e2\u0080\u00a2 com\r\n\r\n\r\nDescription:\r\n\r\nThis script is currently one half of a set of functions to convert Vim command and option names between short\/abbreviated and long\/full name forms. (Ex. \"fu\" => \"function\", \"e\" => \"edit\") These are sometimes indicated like \"fu[nction]\" or  \"e[dit]\".\r\n\r\nThe script currently only converts from short to long. Based on my own preferences, I am less motivated to do the other side. ;) But I conceed it would be useful to have a polished routine to help going back and forth between the two for those with preferences for either readability or bandwidth conservation.\r\n\r\nThe script contains plenty of working debris at the bottom which shouldn't impact the code above. I have tried to be as complete as possible by using Vim's own syntax and option lists to compile the substitutions from. However you may notice omissions.\r\n\r\nDependancies:\r\n\r\nmultvals.vim (http:\/\/www.vim.org\/script.php?script_id=171)\r\n  by Hari Krishna Dara, for the arrays of items to be substituted.\r\n\r\nToDo:\r\n\r\n* Avoid mapping syntaxes.\r\n* Avoid heinous \"normal af|g^\" => \"normal af|global^\" error\r\n* Avoid heinous \"normal j+r\" => \"normal j+read\" error\r\n* Add whitespace separators around evaluation operators and concatenation symbols.\r\n\r\n\r\nThis is one of many custom utilities and functions for gVim from the Cream project (http:\/\/cream.sourceforge.net), a configuration of Vim for those of us familiar with Apple and Windows software.\r\n\r\n","install_details":"\r\nJust drop this file into your plugins directory, make sure you have the required dependencies (multvals.vim) also there, and start Vim. Then call the functions Cream_vimshort2long() and Cream_vimlong2short() from within the file to be converted.\r\n","5":"\r\nJust drop this file into your plugins directory, make sure you have the required dependencies (multvals.vim) also there, and start Vim. Then call the functions Cream_vimshort2long() and Cream_vimlong2short() from within the file to be converted.\r\n","first_name":"Steve","6":"Steve","last_name":"Hall","7":"Hall","releases":[{"0":"471","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"cream-vimabbrev.vim","4":"cream-vimabbrev.vim","src_id":"1369","5":"1369","creation_date":"1036389724","6":"1036389724"}]},"470":{"script_id":"470","0":"470","script_name":"HTML Photo Board","1":"HTML Photo Board","script_type":"utility","2":"utility","summary":"Generate a HTML Thumbnail Photoboard using ImageMagic","3":"Generate a HTML Thumbnail Photoboard using ImageMagic","description":"Generates a table-based photoboard given either a directory of images, \nor a configuration file.  It makes use of imagemagic to resize the images \nfor both the 'expanded' and 'thumbnail' images.\n\nAt the moment, the table generated is simply a 'click to view image' type.\nThe script supports alt text, some headings, and changing of colours.\n\nDetailed description of how to use &c  is in the file itself.\nAny comments ","4":"Generates a table-based photoboard given either a directory of images, \nor a configuration file.  It makes use of imagemagic to resize the images \nfor both the 'expanded' and 'thumbnail' images.\n\nAt the moment, the table generated is simply a 'click to view image' type.\nThe script supports alt text, some headings, and changing of colours.\n\nDetailed description of how to use &c  is in the file itself.\nAny comments ","install_details":"Source, and call the appropriate functions. ","5":"Source, and call the appropriate functions. ","first_name":"Michael","6":"Michael","last_name":"Geddes","7":"Geddes","releases":[{"0":"470","vim_version":"6.0","1":"6.0","script_version":"0.2","2":"0.2","version_comment":"Initial upload","3":"Initial upload","package":"photoboard.vim","4":"photoboard.vim","src_id":"1368","5":"1368","creation_date":"1036349538","6":"1036349538"}]},"469":{"script_id":"469","0":"469","script_name":"fnaqevan","1":"fnaqevan","script_type":"color scheme","2":"color scheme","summary":"color scheme for overnight hacking","3":"color scheme for overnight hacking","description":"yet another color scheme with dark background.\r\n\r\nLinux screenshot: http:\/\/rms.republika.pl\/vim\/fnaqevan.jpg\r\nWindows screenshot: http:\/\/rms.republika.pl\/vim\/fnaqevan1.jpg","4":"yet another color scheme with dark background.\r\n\r\nLinux screenshot: http:\/\/rms.republika.pl\/vim\/fnaqevan.jpg\r\nWindows screenshot: http:\/\/rms.republika.pl\/vim\/fnaqevan1.jpg","install_details":"Drop in $VIMRUNTIME\/colors\r\n(optionally) add \":colorscheme fnaqevan\" to your .gvimrc","5":"Drop in $VIMRUNTIME\/colors\r\n(optionally) add \":colorscheme fnaqevan\" to your .gvimrc","first_name":"Rafal","6":"Rafal","last_name":"Sulejman","7":"Sulejman","releases":[{"0":"469","vim_version":"6.0","1":"6.0","script_version":"0.1a","2":"0.1a","version_comment":"ooops... typo in the filename.. :(","3":"ooops... typo in the filename.. :(","package":"fnaqevan.vim","4":"fnaqevan.vim","src_id":"1362","5":"1362","creation_date":"1036240822","6":"1036240822"}]},"468":{"script_id":"468","0":"468","script_name":"VEC","1":"VEC","script_type":"utility","2":"utility","summary":"Vim Extension Classes","3":"Vim Extension Classes","description":"The VEC package is inteneded as a way to extend the functionality of the Vim Language in order to enable people to write more complex Vim scripts in shorter times.\r\n\r\nThe package currently contains the following functions:\r\n\r\n1. Array functions\r\n\r\nArray:Contains\r\nArray:Destroy\r\nArray:Exists\r\nArray:Get\r\nArray:GetElementCount\r\nArray:New\r\nArray:Pop\r\nArray:Push\r\n\r\n2. String functions\r\n\r\nString:Dup\r\nString:Occurances\r\n\r\nIt also contains some experimental, not documented code.","4":"The VEC package is inteneded as a way to extend the functionality of the Vim Language in order to enable people to write more complex Vim scripts in shorter times.\r\n\r\nThe package currently contains the following functions:\r\n\r\n1. Array functions\r\n\r\nArray:Contains\r\nArray:Destroy\r\nArray:Exists\r\nArray:Get\r\nArray:GetElementCount\r\nArray:New\r\nArray:Pop\r\nArray:Push\r\n\r\n2. String functions\r\n\r\nString:Dup\r\nString:Occurances\r\n\r\nIt also contains some experimental, not documented code.","install_details":"Read the README and INSTALL files that come with the package.","5":"Read the README and INSTALL files that come with the package.","first_name":"Little","6":"Little","last_name":"Dragon","7":"Dragon","releases":[{"0":"468","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"vec-0.1.tar.gz","4":"vec-0.1.tar.gz","src_id":"1359","5":"1359","creation_date":"1036222175","6":"1036222175"}]},"467":{"script_id":"467","0":"467","script_name":"emodeline","1":"emodeline","script_type":"utility","2":"utility","summary":"Set the file type from emacs -*- modelines -*-","3":"Set the file type from emacs -*- modelines -*-","description":"If a file contains\r\n\r\n# -*- sh -*-\r\n[...]\r\n\r\n&filetype will be automatically set to \"sh\". This is the Emacs way of saying # vim:ft=sh :)","4":"If a file contains\r\n\r\n# -*- sh -*-\r\n[...]\r\n\r\n&filetype will be automatically set to \"sh\". This is the Emacs way of saying # vim:ft=sh :)","install_details":"Place it in the plugins directory","5":"Place it in the plugins directory","first_name":"Little","6":"Little","last_name":"Dragon","7":"Dragon","releases":[{"0":"467","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"emodeline.vim","4":"emodeline.vim","src_id":"1358","5":"1358","creation_date":"1036221910","6":"1036221910"}]},"466":{"script_id":"466","0":"466","script_name":"perl_h2xs","1":"perl_h2xs","script_type":"ftplugin","2":"ftplugin","summary":"Automate creating perl modules via h2xs","3":"Automate creating perl modules via h2xs","description":"The Perl_h2xs.vim plugin is a plugin that allows you to automate the process of perl module creation. Writing Perl modules with the recommended structure can be time consuming so this ftplugin automates the process by involking h2xs when you edit a non-existant .pm file. I.e.\r\n\r\n  vim Test::Bob.pm\r\n\r\nWill invoke h2xs -XAn Test::Bob, and if the module skeleton is created, will swap the edited file to Test\/Bob\/Bob.pm.\r\n\r\nThrough the use of variables, you can also set the plugin to create a MANIFEST.SKIP to exclude the CVS directories (and update the MANIFEST to include this new file) and to use CVS to import (or add) the newly created tree to a respository.\r\n\r\nIt works under windows and unix and you can even create .pm trees in another directory by specifying a directory name and module name in one. I.e.\r\n\r\n vim \/usr\/local\/src\/Test\/Bob.pm\r\n\r\nwould create the module:\r\n\r\n \/usr\/local\/src\/Test\/Bob\/Bob.pm\r\n\r\nSee the readme file and help docs for detalis.\r\n\r\nEnjoy, this is me being lazy :)","4":"The Perl_h2xs.vim plugin is a plugin that allows you to automate the process of perl module creation. Writing Perl modules with the recommended structure can be time consuming so this ftplugin automates the process by involking h2xs when you edit a non-existant .pm file. I.e.\r\n\r\n  vim Test::Bob.pm\r\n\r\nWill invoke h2xs -XAn Test::Bob, and if the module skeleton is created, will swap the edited file to Test\/Bob\/Bob.pm.\r\n\r\nThrough the use of variables, you can also set the plugin to create a MANIFEST.SKIP to exclude the CVS directories (and update the MANIFEST to include this new file) and to use CVS to import (or add) the newly created tree to a respository.\r\n\r\nIt works under windows and unix and you can even create .pm trees in another directory by specifying a directory name and module name in one. I.e.\r\n\r\n vim \/usr\/local\/src\/Test\/Bob.pm\r\n\r\nwould create the module:\r\n\r\n \/usr\/local\/src\/Test\/Bob\/Bob.pm\r\n\r\nSee the readme file and help docs for detalis.\r\n\r\nEnjoy, this is me being lazy :)","install_details":"The tarball contains the files:\r\n  README_perl_h2xs.txt\r\n  ftplugin\/perl_h2xs.vim\r\n  doc\/perl_h2xs.txt\r\n\r\nso you can just untar'gzip the tarball in your local vim directory. I.e. .vim or vim61\\vimfiles and all of the files will go into place. Start vim and rebuild your local help docs tags file using\r\n\r\n :helptags {docdir}\r\n\r\nI.e.\r\n\r\n :helptags ~\/.vim\/doc\r\n :helptags c:\\vim61\\vimfiles\r\n\r\nContact me if you have problems (with the module that is :-)","5":"The tarball contains the files:\r\n  README_perl_h2xs.txt\r\n  ftplugin\/perl_h2xs.vim\r\n  doc\/perl_h2xs.txt\r\n\r\nso you can just untar'gzip the tarball in your local vim directory. I.e. .vim or vim61\\vimfiles and all of the files will go into place. Start vim and rebuild your local help docs tags file using\r\n\r\n :helptags {docdir}\r\n\r\nI.e.\r\n\r\n :helptags ~\/.vim\/doc\r\n :helptags c:\\vim61\\vimfiles\r\n\r\nContact me if you have problems (with the module that is :-)","first_name":"Colin","6":"Colin","last_name":"Keith","7":"Keith","releases":[{"0":"466","vim_version":"6.0","1":"6.0","script_version":"0.51","2":"0.51","version_comment":"Regexp in  substitution when getting module filenamewasn't anchored so it was turning X::Y::Z => X\/Y\/Z\/Y\/Z.pm not X\/Y\/Z\/Z.pm\r\n\r\nIf module exists you start editing that rather than not checking if it exists and auto starting h2xs. This means you can create with vim X::Y::Z.pm then use !v to go back and you'll edit the module properly, added new var so you can be prompted before this happens if you want.","3":"Regexp in  substitution when getting module filenamewasn't anchored so it was turning X::Y::Z => X\/Y\/Z\/Y\/Z.pm not X\/Y\/Z\/Z.pm\r\n\r\nIf module exists you start editing that rather than not checking if it exists and auto starting h2xs. This means you can create with vim X::Y::Z.pm then use !v to go back and you'll edit the module properly, added new var so you can be prompted before this happens if you want.","package":"perl_h2xs_vim.tar.gz","4":"perl_h2xs_vim.tar.gz","src_id":"1363","5":"1363","creation_date":"1036246081","6":"1036246081"},{"0":"466","vim_version":"6.0","1":"6.0","script_version":"0.5","2":"0.5","version_comment":"Initial upload","3":"Initial upload","package":"perl_h2xs_vim.tar.gz","4":"perl_h2xs_vim.tar.gz","src_id":"1354","5":"1354","creation_date":"1036016879","6":"1036016879"}]},"465":{"script_id":"465","0":"465","script_name":"vimspell","1":"vimspell","script_type":"utility","2":"utility","summary":"ispell or aspell based spell checker with fly-spelling","3":"ispell or aspell based spell checker with fly-spelling","description":"***** note to VIM 7 users ! *****\r\nVersion 7 of vim integrates a native spellchecker which outperforms  vimspell script.\r\nAs such I will not maintain anymore vimspell script, and you are advised to delete all\r\nrelated files from your plugin\/ and doc\/ directory, and use the native spellchecker instead.\r\n******************************\r\n\r\nThis script is based on Claudio Fleiner's spell checker and uses ispell (or aspell) \r\nto highlight spelling errors, and provides mappings (including a popup menu opened \r\nby right clicking on a mispelled word) to correct them, with suggestions. \r\n\r\nIt is possible to set up the script to do automatic spellchecking (\u00c3\u00a0 la\r\nword --- the current visible window is checked, and errors are highlighted on the fly).\r\nFor that, just redefine the spell_auto_type variable (let spell_auto_type=\"tex,doc,mail\") in such a maner \r\nthat all the filetypes for which you want on the fly spell check are listed (\"none\", and \"all\" token are treated).\r\n     \r\nMuch more documentation on all options can be found at the beginning of the script, or \r\nafter having install it, by typing the command \":help vimspell\".\r\n\r\nFeedback (suggestions, bug report, questions,...) is welcome .... \r\n\r\nYou can subscribe to a mailing list to receive annoucement for new versions by sending a mail\r\nhere at vimspell.announce-request@ml.free.fr  with subscribe in the subject.","4":"***** note to VIM 7 users ! *****\r\nVersion 7 of vim integrates a native spellchecker which outperforms  vimspell script.\r\nAs such I will not maintain anymore vimspell script, and you are advised to delete all\r\nrelated files from your plugin\/ and doc\/ directory, and use the native spellchecker instead.\r\n******************************\r\n\r\nThis script is based on Claudio Fleiner's spell checker and uses ispell (or aspell) \r\nto highlight spelling errors, and provides mappings (including a popup menu opened \r\nby right clicking on a mispelled word) to correct them, with suggestions. \r\n\r\nIt is possible to set up the script to do automatic spellchecking (\u00c3\u00a0 la\r\nword --- the current visible window is checked, and errors are highlighted on the fly).\r\nFor that, just redefine the spell_auto_type variable (let spell_auto_type=\"tex,doc,mail\") in such a maner \r\nthat all the filetypes for which you want on the fly spell check are listed (\"none\", and \"all\" token are treated).\r\n     \r\nMuch more documentation on all options can be found at the beginning of the script, or \r\nafter having install it, by typing the command \":help vimspell\".\r\n\r\nFeedback (suggestions, bug report, questions,...) is welcome .... \r\n\r\nYou can subscribe to a mailing list to receive annoucement for new versions by sending a mail\r\nhere at vimspell.announce-request@ml.free.fr  with subscribe in the subject.","install_details":"Copy vimspell.vim into your ~\/.vim\/plugin directory\r\nThe help file shall be automagically installed when launching VIM.","5":"Copy vimspell.vim into your ~\/.vim\/plugin directory\r\nThe help file shall be automagically installed when launching VIM.","first_name":"Mathieu","6":"Mathieu","last_name":"Clabaut","7":"Clabaut","releases":[{"0":"465","vim_version":"6.0","1":"6.0","script_version":"1.100","2":"1.100","version_comment":"- UTF-8 bug workaroud (hack from Huidae Cho),\r\n- Ability to type 01 to 09 to select one of the first 9 alternatives (patch\r\n  from M.Sureshkumar),\r\n- Suppression of some debugging output,\r\n- Some corrections to better work under windows and notably, addition of   default shell handlling for windows thanks to Wojciech Pietron.\r\n- Silent some warnings.\r\n","3":"- UTF-8 bug workaroud (hack from Huidae Cho),\r\n- Ability to type 01 to 09 to select one of the first 9 alternatives (patch\r\n  from M.Sureshkumar),\r\n- Suppression of some debugging output,\r\n- Some corrections to better work under windows and notably, addition of   default shell handlling for windows thanks to Wojciech Pietron.\r\n- Silent some warnings.\r\n","package":"vimspell.vim","4":"vimspell.vim","src_id":"4580","5":"4580","creation_date":"1126674109","6":"1126674109"},{"0":"465","vim_version":"6.0","1":"6.0","script_version":"1.95","2":"1.95","version_comment":"- Correcting spell errors when typechecking lines with ` inside.\r\n- Apply patch from Olaf Conradi to manage the cases when mapping already \r\n  exists for <Space>, '.' and so one in insert mode.\r\n- Correction to use the new aspell command line interface\r\n- workaround inoremap preventing abbreviations expensions in vim 6.3 (however, \r\n  there are still some unwanted behaviour).\r\n- Better language recognition for mail filetypes.\r\n- Include some longstanding patches from Alex Efros. (Use of \\k instead of \\w \r\n  in regexp, and better usage of language specific iskeyword.)\r\n- Take csh into account. Addition of 'spell_shell' variable and associated \r\n  documentation.\r\n- Correction of line quoting bug which appeared in tex\/latex file (bug \r\n  reported by Yann  Golanski).\r\n- Add Hugo Hass patch : spell_guess_max_lines\r\n- Addition of filetype \"text\" and \"\" to spell_markup_ft option.\r\n- Add some FAQ documentation, improve the documentation about spell_markup_ft\r\n","3":"- Correcting spell errors when typechecking lines with ` inside.\r\n- Apply patch from Olaf Conradi to manage the cases when mapping already \r\n  exists for <Space>, '.' and so one in insert mode.\r\n- Correction to use the new aspell command line interface\r\n- workaround inoremap preventing abbreviations expensions in vim 6.3 (however, \r\n  there are still some unwanted behaviour).\r\n- Better language recognition for mail filetypes.\r\n- Include some longstanding patches from Alex Efros. (Use of \\k instead of \\w \r\n  in regexp, and better usage of language specific iskeyword.)\r\n- Take csh into account. Addition of 'spell_shell' variable and associated \r\n  documentation.\r\n- Correction of line quoting bug which appeared in tex\/latex file (bug \r\n  reported by Yann  Golanski).\r\n- Add Hugo Hass patch : spell_guess_max_lines\r\n- Addition of filetype \"text\" and \"\" to spell_markup_ft option.\r\n- Add some FAQ documentation, improve the documentation about spell_markup_ft\r\n","package":"vimspell.vim","4":"vimspell.vim","src_id":"3744","5":"3744","creation_date":"1104831208","6":"1104831208"},{"0":"465","vim_version":"6.0","1":"6.0","script_version":"1.84","2":"1.84","version_comment":"Add mail to the default content of 'spell_markup_ft' variable (errors where not highlighted anymore during mail composition).","3":"Add mail to the default content of 'spell_markup_ft' variable (errors where not highlighted anymore during mail composition).","package":"vimspell.vim","4":"vimspell.vim","src_id":"2966","5":"2966","creation_date":"1082615633","6":"1082615633"},{"0":"465","vim_version":"6.0","1":"6.0","script_version":"1.83","2":"1.83","version_comment":"Bug correction - highlighting inside cluster was badly set, depending on when SpellSetupBuffer was called\nAddition fo auto jump option (jump to next error after correction).\nCorrection of a bug where cursor was jumping when on the last line of a file.\nCorrection of html file highlightings.\nCorrection of spell_guess_language_ft usage (wasn't taken into account).\nPerformance issue : check of @Spell cluster existence in syntax highlightings was removed, and replaced by heuristic and manula configuration. see spell_markup_ft variable.\n\nMany thanks to  Paul Jolly, Tomas Hoger, Michaeljohn Clement, Hugo Haas and Markus Braun. ","3":"Bug correction - highlighting inside cluster was badly set, depending on when SpellSetupBuffer was called\nAddition fo auto jump option (jump to next error after correction).\nCorrection of a bug where cursor was jumping when on the last line of a file.\nCorrection of html file highlightings.\nCorrection of spell_guess_language_ft usage (wasn't taken into account).\nPerformance issue : check of @Spell cluster existence in syntax highlightings was removed, and replaced by heuristic and manula configuration. see spell_markup_ft variable.\n\nMany thanks to  Paul Jolly, Tomas Hoger, Michaeljohn Clement, Hugo Haas and Markus Braun. ","package":"vimspell.vim","4":"vimspell.vim","src_id":"2962","5":"2962","creation_date":"1082535126","6":"1082535126"},{"0":"465","vim_version":"6.0","1":"6.0","script_version":"1.78","2":"1.78","version_comment":"- Add a language auto-detection function.\n- Corrects a bug which causes delays during buffer switching (function SpellTuneCommentSyntax).\n- Correction for bug wich prevents use of alternatives number 10 and 20\n- Use of alternatives usable even when spellchecking is not automatically done\n- Samm optimization to improve buffer switching latency.","3":"- Add a language auto-detection function.\n- Corrects a bug which causes delays during buffer switching (function SpellTuneCommentSyntax).\n- Correction for bug wich prevents use of alternatives number 10 and 20\n- Use of alternatives usable even when spellchecking is not automatically done\n- Samm optimization to improve buffer switching latency.","package":"vimspell.vim","4":"vimspell.vim","src_id":"2957","5":"2957","creation_date":"1082425620","6":"1082425620"},{"0":"465","vim_version":"6.0","1":"6.0","script_version":"1.73","2":"1.73","version_comment":"- at most 20 alternatives are now proposed (was 10)\n- 'r'eplace choice was remove (was broken, and of no much use).","3":"- at most 20 alternatives are now proposed (was 10)\n- 'r'eplace choice was remove (was broken, and of no much use).","package":"vimspell.vim","4":"vimspell.vim","src_id":"2953","5":"2953","creation_date":"1082357175","6":"1082357175"},{"0":"465","vim_version":"6.0","1":"6.0","script_version":"1.72","2":"1.72","version_comment":"- Correction of a performance issue (syntax match was continuously append, which slow down vim after some times).\n- Correction of a bug, which cause unwanted behavior when the user hit another key than those proposed to correct spell errors.","3":"- Correction of a performance issue (syntax match was continuously append, which slow down vim after some times).\n- Correction of a bug, which cause unwanted behavior when the user hit another key than those proposed to correct spell errors.","package":"vimspell.vim","4":"vimspell.vim","src_id":"2951","5":"2951","creation_date":"1082354180","6":"1082354180"},{"0":"465","vim_version":"6.0","1":"6.0","script_version":"1.70","2":"1.70","version_comment":"- Spell checking in insert mode does not break undo stack anymore, thanks to\n  Hari Krishna Dara.\n- Jumping to next error now works, even if some text is not spellchecked\n  (like comments).\n- Bug with \/si and aspell corrected\n- Use @Spell cluster to spell specific region according to the highlighting\n  definitions (Idea from vim@vim.org discussion and from engspchk.vim. Thanks\n  to Mr.Campbell)\n- Suppress menu bug, when changing language by calling directly\n  :SpellChangeLanguage.\n- Some minor documentation improvement.\n","3":"- Spell checking in insert mode does not break undo stack anymore, thanks to\n  Hari Krishna Dara.\n- Jumping to next error now works, even if some text is not spellchecked\n  (like comments).\n- Bug with \/si and aspell corrected\n- Use @Spell cluster to spell specific region according to the highlighting\n  definitions (Idea from vim@vim.org discussion and from engspchk.vim. Thanks\n  to Mr.Campbell)\n- Suppress menu bug, when changing language by calling directly\n  :SpellChangeLanguage.\n- Some minor documentation improvement.\n","package":"vimspell.vim","4":"vimspell.vim","src_id":"2496","5":"2496","creation_date":"1069229937","6":"1069229937"},{"0":"465","vim_version":"6.0","1":"6.0","script_version":"1.68","2":"1.68","version_comment":"- Remove \"silent\" keyword which (for some unknown reason) prevent mapping to\n  replaceword (1,2,..) to be removed,\n- Bug workaround to prevent coma to be added to 'iskeyword' option (thanks to\n  Mark Waggoner)\n- Bug correction when line contained \\,\n- Bad filetype recognition bug correction,\n- SpellCheckLine correction. Spell checked was not done after each word,\n- aunmenu warning correction...\n- more menus,\n- more bugs to be corrected :(\n","3":"- Remove \"silent\" keyword which (for some unknown reason) prevent mapping to\n  replaceword (1,2,..) to be removed,\n- Bug workaround to prevent coma to be added to 'iskeyword' option (thanks to\n  Mark Waggoner)\n- Bug correction when line contained \\,\n- Bad filetype recognition bug correction,\n- SpellCheckLine correction. Spell checked was not done after each word,\n- aunmenu warning correction...\n- more menus,\n- more bugs to be corrected :(\n","package":"vimspell.vim","4":"vimspell.vim","src_id":"2312","5":"2312","creation_date":"1063009859","6":"1063009859"},{"0":"465","vim_version":"6.0","1":"6.0","script_version":"1.67","2":"1.67","version_comment":"previous upload failed...","3":"previous upload failed...","package":"vimspell.vim","4":"vimspell.vim","src_id":"2201","5":"2201","creation_date":"1059963782","6":"1059963782"},{"0":"465","vim_version":"6.0","1":"6.0","script_version":"1.67","2":"1.67","version_comment":"New function: popup menu with <RightMouse> to select alternative.\nMake spell_filter option working.\nEnsure usage of \/bin\/sh instead of [t]csh variants (problem with double\nquotes).\nInclude Sandra schr\u00c3\u00b6dter patch for SpellCaseAccept problem.\nAdd a map to '.' as a hook to spell check current line in insert mode.\nDocumentation update.\nCleaning of help autoinstallation functions (Guo Peng Wen).\n","3":"New function: popup menu with <RightMouse> to select alternative.\nMake spell_filter option working.\nEnsure usage of \/bin\/sh instead of [t]csh variants (problem with double\nquotes).\nInclude Sandra schr\u00c3\u00b6dter patch for SpellCaseAccept problem.\nAdd a map to '.' as a hook to spell check current line in insert mode.\nDocumentation update.\nCleaning of help autoinstallation functions (Guo Peng Wen).\n","package":"vimspell.vim","4":"vimspell.vim","src_id":"2199","5":"2199","creation_date":"1059903860","6":"1059903860"},{"0":"465","vim_version":"6.0","1":"6.0","script_version":"1.64","2":"1.64","version_comment":"- Include patch of Philippe Sum to make vimspell work with windows (untested).\n- Disable hlsearch when doing <leader>sp and <leader>sn.\n- Save and restore backspace option when spell_insert_mode is set.\n- Do not check current window if spell_auto_enable is not set or set to 0.\n- In insert mode, do not check current line when no new words were inserted (fastest operation when typing several spaces).\n- Correct bug where error highlighting vanished when reentering a buffer already checked (as a result, less computation are done when switching).\nAdd Markus Braun patch to remove SpellProposeAlternatives mapping when hitting ESC key.\n","3":"- Include patch of Philippe Sum to make vimspell work with windows (untested).\n- Disable hlsearch when doing <leader>sp and <leader>sn.\n- Save and restore backspace option when spell_insert_mode is set.\n- Do not check current window if spell_auto_enable is not set or set to 0.\n- In insert mode, do not check current line when no new words were inserted (fastest operation when typing several spaces).\n- Correct bug where error highlighting vanished when reentering a buffer already checked (as a result, less computation are done when switching).\nAdd Markus Braun patch to remove SpellProposeAlternatives mapping when hitting ESC key.\n","package":"vimspell.vim","4":"vimspell.vim","src_id":"2190","5":"2190","creation_date":"1059376229","6":"1059376229"},{"0":"465","vim_version":"6.0","1":"6.0","script_version":"1.61","2":"1.61","version_comment":"Include Guopeng Wen to \n - fix error in SpellCheckLanguage when there is no menu.\n - fix SpellSetupBuffer behaviuor when autocommand are enables.\n","3":"Include Guopeng Wen to \n - fix error in SpellCheckLanguage when there is no menu.\n - fix SpellSetupBuffer behaviuor when autocommand are enables.\n","package":"vimspell.vim","4":"vimspell.vim","src_id":"2176","5":"2176","creation_date":"1058831570","6":"1058831570"},{"0":"465","vim_version":"6.0","1":"6.0","script_version":"1.60","2":"1.60","version_comment":"Some escaping bug corrections.\nDocumentation updated.\nEscape Space in filename.\nCursor position restoring in SpellCheckWindow.\nIskeyword is now set globally. \nLoadIsKeyword function is suppress. SpellSaveIskeyword is only call when setting up buffer.\nInclusion of Guopeng Wen  patch to minimize overhead\nof vimspell use when no menu are used and when no autospell is done.\nAdd faq about minimizing vimspell overhead.\nInclusion of Markus Braun patch:\n- s:SpellSetupBuffer() call s:SpellSetSpellchecker() only when it was not called before\n- Right calculation of the window top and bottom position, even if fold are  present (idea from Mark Hillebrand, who used this in his FirstWinLine() and  LastWinLine())\nVerify that mapleader is defined before being used.\nAdd language and filetype dependant 'iskeyword' options...\nMinor menu enhancment.\nBug ands todolist update.\n","3":"Some escaping bug corrections.\nDocumentation updated.\nEscape Space in filename.\nCursor position restoring in SpellCheckWindow.\nIskeyword is now set globally. \nLoadIsKeyword function is suppress. SpellSaveIskeyword is only call when setting up buffer.\nInclusion of Guopeng Wen  patch to minimize overhead\nof vimspell use when no menu are used and when no autospell is done.\nAdd faq about minimizing vimspell overhead.\nInclusion of Markus Braun patch:\n- s:SpellSetupBuffer() call s:SpellSetSpellchecker() only when it was not called before\n- Right calculation of the window top and bottom position, even if fold are  present (idea from Mark Hillebrand, who used this in his FirstWinLine() and  LastWinLine())\nVerify that mapleader is defined before being used.\nAdd language and filetype dependant 'iskeyword' options...\nMinor menu enhancment.\nBug ands todolist update.\n","package":"vimspell.vim","4":"vimspell.vim","src_id":"2174","5":"2174","creation_date":"1058750250","6":"1058750250"},{"0":"465","vim_version":"6.0","1":"6.0","script_version":"1.49","2":"1.49","version_comment":"Bug correction: SpellCheckLine didn't work when the line contained quotes.","3":"Bug correction: SpellCheckLine didn't work when the line contained quotes.","package":"vimspell.vim","4":"vimspell.vim","src_id":"1969","5":"1969","creation_date":"1052190384","6":"1052190384"},{"0":"465","vim_version":"6.0","1":"6.0","script_version":"1.48","2":"1.48","version_comment":"  - Experimental on the fly spell checking in insert mode. Thanks to Mikolaj Machowski\n   (new options spell_insert_mode).\n  - Addition of \"none\" and \"all\" token for the spell_auto_type\n    variable.\n  - FAQ section in documentation.\n  - Beginning of a solution for auto help installation bug (the help\n    file was not installed when vimspell was not in a user writeable\n    directory. Thanks to Peter Kaagman\n  - Some documentation addition and correction.\n  - Some code cleaning and ordering.\n","3":"  - Experimental on the fly spell checking in insert mode. Thanks to Mikolaj Machowski\n   (new options spell_insert_mode).\n  - Addition of \"none\" and \"all\" token for the spell_auto_type\n    variable.\n  - FAQ section in documentation.\n  - Beginning of a solution for auto help installation bug (the help\n    file was not installed when vimspell was not in a user writeable\n    directory. Thanks to Peter Kaagman\n  - Some documentation addition and correction.\n  - Some code cleaning and ordering.\n","package":"vimspell.vim","4":"vimspell.vim","src_id":"1967","5":"1967","creation_date":"1052094605","6":"1052094605"},{"0":"465","vim_version":"6.0","1":"6.0","script_version":"1.46","2":"1.46","version_comment":"Apply patches from Markus Braun (many thanks to him):\n - removed the need of sed, sort, awk external tools\n - removed the spell_fly_error variables\n - fixed small bug when proposing alternatives.\nFix small bug when manually calling SpellSetLanguage. Kindly reported by JF L.\nRemove highlighting when changing language or spell checker.\nMinor cosmetic changes.\nAdd Markus Braun Patch which display spell check stats.\nDo not load vimspell when 'compatible' is set.\nSmall bug when unletting undefined variable.\nLanguage menu initialization is now correct.\nUpdate TODO list.","3":"Apply patches from Markus Braun (many thanks to him):\n - removed the need of sed, sort, awk external tools\n - removed the spell_fly_error variables\n - fixed small bug when proposing alternatives.\nFix small bug when manually calling SpellSetLanguage. Kindly reported by JF L.\nRemove highlighting when changing language or spell checker.\nMinor cosmetic changes.\nAdd Markus Braun Patch which display spell check stats.\nDo not load vimspell when 'compatible' is set.\nSmall bug when unletting undefined variable.\nLanguage menu initialization is now correct.\nUpdate TODO list.","package":"vimspell.vim","4":"vimspell.vim","src_id":"1818","5":"1818","creation_date":"1047887102","6":"1047887102"},{"0":"465","vim_version":"6.0","1":"6.0","script_version":"1.40","2":"1.40","version_comment":"New feature : auto-installation of vimspell help file \nDocumentation correction and polishing (it now follows the help format).\nAdd <Leader>sA map for SpellAutoDisable\nRework of vimspell option documentation.\nCorrect Spellexit function.\n<Leader>sq now call SpellAutoDisable instead of SpellExit.\nSpellChecker is call in auto mode when window loose focus.\n","3":"New feature : auto-installation of vimspell help file \nDocumentation correction and polishing (it now follows the help format).\nAdd <Leader>sA map for SpellAutoDisable\nRework of vimspell option documentation.\nCorrect Spellexit function.\n<Leader>sq now call SpellAutoDisable instead of SpellExit.\nSpellChecker is call in auto mode when window loose focus.\n","package":"vimspell.vim","4":"vimspell.vim","src_id":"1782","5":"1782","creation_date":"1046928731","6":"1046928731"},{"0":"465","vim_version":"6.0","1":"6.0","script_version":"1.33","2":"1.33","version_comment":"Add preliminary support of spell errors highlighting in comments.\nCorrect nasty bug, which causes lost of data when auto spell check was\nselected and the number of lines of the text was less than the window height.\nCorrect bug when serching for next or previous errors.\nCursor position is now restored after a spell check.\nThanks to Markus Braun <Markus.Braun@krawel.de> and Igor Goldenberg\n<igold@igold.pp.ru>.","3":"Add preliminary support of spell errors highlighting in comments.\nCorrect nasty bug, which causes lost of data when auto spell check was\nselected and the number of lines of the text was less than the window height.\nCorrect bug when serching for next or previous errors.\nCursor position is now restored after a spell check.\nThanks to Markus Braun <Markus.Braun@krawel.de> and Igor Goldenberg\n<igold@igold.pp.ru>.","package":"vimspell.vim","4":"vimspell.vim","src_id":"1604","5":"1604","creation_date":"1041823344","6":"1041823344"},{"0":"465","vim_version":"6.0","1":"6.0","script_version":"1.30","2":"1.30","version_comment":"Add parameters to tune vimspell menu position.\nCorrect bug, which prevents user defined spell_language_list to be used.\nCorrect a bug, which reactivate auto-spell when entering a buffer, even if it\nwas previously disable.\n","3":"Add parameters to tune vimspell menu position.\nCorrect bug, which prevents user defined spell_language_list to be used.\nCorrect a bug, which reactivate auto-spell when entering a buffer, even if it\nwas previously disable.\n","package":"vimspell.vim","4":"vimspell.vim","src_id":"1552","5":"1552","creation_date":"1040002533","6":"1040002533"},{"0":"465","vim_version":"6.0","1":"6.0","script_version":"1.28","2":"1.28","version_comment":"Small patch to 'spell_auto_type' usage (all buffer with no filetype were spell\nchecked by default).\nAdd credits.","3":"Small patch to 'spell_auto_type' usage (all buffer with no filetype were spell\nchecked by default).\nAdd credits.","package":"vimspell.vim","4":"vimspell.vim","src_id":"1546","5":"1546","creation_date":"1039590915","6":"1039590915"},{"0":"465","vim_version":"6.0","1":"6.0","script_version":"1.26","2":"1.26","version_comment":"Correct spell_auto_type behaviour. There was a bug which made AutoSpell enable for all file types.","3":"Correct spell_auto_type behaviour. There was a bug which made AutoSpell enable for all file types.","package":"vimspell.vim","4":"vimspell.vim","src_id":"1545","5":"1545","creation_date":"1039587650","6":"1039587650"},{"0":"465","vim_version":"6.0","1":"6.0","script_version":"1.25","2":"1.25","version_comment":"Correct bug with aspell (add word to local dictionary didn't work), kindly reported by Andrew McCarthy <andrewmc-vim@celt.dias.ie> and Alberto Ornaghi <alor@sikurezza.org>","3":"Correct bug with aspell (add word to local dictionary didn't work), kindly reported by Andrew McCarthy <andrewmc-vim@celt.dias.ie> and Alberto Ornaghi <alor@sikurezza.org>","package":"vimspell.vim","4":"vimspell.vim","src_id":"1544","5":"1544","creation_date":"1039584426","6":"1039584426"},{"0":"465","vim_version":"6.0","1":"6.0","script_version":"1.23","2":"1.23","version_comment":"Add (requested) documentation about setting up on-the-fly spell check,\nadd spell_auto_type and spell_no_readonly variables to tune when on-the-fly\nspell checking is done.\nStill on bug about highlighting (see TODO list in documentation section), if someone wants to tackle it....","3":"Add (requested) documentation about setting up on-the-fly spell check,\nadd spell_auto_type and spell_no_readonly variables to tune when on-the-fly\nspell checking is done.\nStill on bug about highlighting (see TODO list in documentation section), if someone wants to tackle it....","package":"vimspell.vim","4":"vimspell.vim","src_id":"1542","5":"1542","creation_date":"1039513362","6":"1039513362"},{"0":"465","vim_version":"6.0","1":"6.0","script_version":"1.22","2":"1.22","version_comment":"Bug correction : Spellcheck on the fly for the visible window now preserve\ninformations from previous global spellcheck (<Leader>ss).\nDictionnaries are rescan whenever the spellchecker is changed.","3":"Bug correction : Spellcheck on the fly for the visible window now preserve\ninformations from previous global spellcheck (<Leader>ss).\nDictionnaries are rescan whenever the spellchecker is changed.","package":"vimspell.vim","4":"vimspell.vim","src_id":"1538","5":"1538","creation_date":"1039396950","6":"1039396950"},{"0":"465","vim_version":"6.0","1":"6.0","script_version":"1.20","2":"1.20","version_comment":"Documentation and minor modifications.\nAdd  filetype and spell checker dependant options (support by default tex,html,sgml, and nroff or email modes).\nEnglish corrections.\nMake several variables bufferwise (language, spell_executable,...)\nAdd functions and menu to change spellchecker\nCorrect bugs.\nAdd a better dictionaries detection for aspell.\n","3":"Documentation and minor modifications.\nAdd  filetype and spell checker dependant options (support by default tex,html,sgml, and nroff or email modes).\nEnglish corrections.\nMake several variables bufferwise (language, spell_executable,...)\nAdd functions and menu to change spellchecker\nCorrect bugs.\nAdd a better dictionaries detection for aspell.\n","package":"vimspell.vim","4":"vimspell.vim","src_id":"1525","5":"1525","creation_date":"1038870642","6":"1038870642"},{"0":"465","vim_version":"6.0","1":"6.0","script_version":"1.17","2":"1.17","version_comment":"Correct a bug when applying suggestion on a word at the beginning of the buffer.\nThanks to Markus Braun.","3":"Correct a bug when applying suggestion on a word at the beginning of the buffer.\nThanks to Markus Braun.","package":"vimspell.vim","4":"vimspell.vim","src_id":"1496","5":"1496","creation_date":"1038385673","6":"1038385673"},{"0":"465","vim_version":"6.0","1":"6.0","script_version":"1.16","2":"1.16","version_comment":"Add credits,\nUse update instead of write,\nReplace <ESC> default mapping by <Leader>\nCorrect nasty bug (SpellIgnore)\nImprove menus.\nImprove dictionnaries auto-detection.","3":"Add credits,\nUse update instead of write,\nReplace <ESC> default mapping by <Leader>\nCorrect nasty bug (SpellIgnore)\nImprove menus.\nImprove dictionnaries auto-detection.","package":"vimspell.vim","4":"vimspell.vim","src_id":"1494","5":"1494","creation_date":"1038363132","6":"1038363132"},{"0":"465","vim_version":"6.0","1":"6.0","script_version":"1.14","2":"1.14","version_comment":"Much more parametrization (see documentation at the beginning of the script).\nUse aspell or ispell.\nUse as many language as available. Auto detect availables dictionnaries.\nMore functionnal menu.\nBug correction.","3":"Much more parametrization (see documentation at the beginning of the script).\nUse aspell or ispell.\nUse as many language as available. Auto detect availables dictionnaries.\nMore functionnal menu.\nBug correction.","package":"vimspell.vim","4":"vimspell.vim","src_id":"1463","5":"1463","creation_date":"1038188358","6":"1038188358"},{"0":"465","vim_version":"6.0","1":"6.0","script_version":"1.13","2":"1.13","version_comment":"Comments and a bit of documentation.\nSome cleaning.\n\nneed some more parametrization and cleaning.","3":"Comments and a bit of documentation.\nSome cleaning.\n\nneed some more parametrization and cleaning.","package":"vimspell.vim","4":"vimspell.vim","src_id":"1382","5":"1382","creation_date":"1036636909","6":"1036636909"},{"0":"465","vim_version":"6.0","1":"6.0","script_version":"1.12","2":"1.12","version_comment":"Initial upload","3":"Initial upload","package":"vimspell.vim","4":"vimspell.vim","src_id":"1350","5":"1350","creation_date":"1035946907","6":"1035946907"}]},"464":{"script_id":"464","0":"464","script_name":"VB Line-Number","1":"VB Line-Number","script_type":"ftplugin","2":"ftplugin","summary":"Translate Line #'s reported by vb command line to source code line","3":"Translate Line #'s reported by vb command line to source code line","description":"When the VB command-line compiler reports errors, the line #s are as if you were editing in the VB editor.\r\n\r\nThis script translate Line #'s reported by vb command line to the actual source code line.\r\n\r\nSimply type  <VBline#>gvb  or  :VGO <VBLine#>  \r\nand you go to the corresponding line in the VB code.\r\n","4":"When the VB command-line compiler reports errors, the line #s are as if you were editing in the VB editor.\r\n\r\nThis script translate Line #'s reported by vb command line to the actual source code line.\r\n\r\nSimply type  <VBline#>gvb  or  :VGO <VBLine#>  \r\nand you go to the corresponding line in the VB code.\r\n","install_details":"Install as a filetype plugin for all VB files.","5":"Install as a filetype plugin for all VB files.","first_name":"Michael","6":"Michael","last_name":"Geddes","7":"Geddes","releases":[{"0":"464","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"vblinenr.vim","4":"vblinenr.vim","src_id":"1349","5":"1349","creation_date":"1035905658","6":"1035905658"}]},"463":{"script_id":"463","0":"463","script_name":"rainbow.zip","1":"rainbow.zip","script_type":"color scheme","2":"color scheme","summary":"color scheme package","3":"color scheme package","description":"This is color scheme package including 7 files.","4":"This is color scheme package including 7 files.","install_details":"Please copy colorscheme files to your colors directory.","5":"Please copy colorscheme files to your colors directory.","first_name":"Takeshi","6":"Takeshi","last_name":"Zeniya","7":"Zeniya","releases":[{"0":"463","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"rainbow.ZIP","4":"rainbow.ZIP","src_id":"1347","5":"1347","creation_date":"1035876514","6":"1035876514"}]},"462":{"script_id":"462","0":"462","script_name":"nw.vim","1":"nw.vim","script_type":"syntax","2":"syntax","summary":"Simple syntax highlighting for NOWEB files.","3":"Simple syntax highlighting for NOWEB files.","description":"\"nw.vim\" provides a simple syntax highlighting for NOWEB source files.\r\n\r\nNOWEB is a collection of tools for \"Literate Programming\". Unlike WEB or CWEB it is not bound to a specific programming language like PASCAL or C.\r\n\r\nFor more informations about NOWEB, the sources or binary distributions\r\nhave a look at\r\n\r\nhttp:\/\/www.eecs.harvard.edu\/~nr\/noweb\r\n\r\nFor informations about \"Literate Programming\" in general\r\n\r\nhttp:\/\/www.literateprogramming.com\r\n\r\ncould be a place to start.\r\n","4":"\"nw.vim\" provides a simple syntax highlighting for NOWEB source files.\r\n\r\nNOWEB is a collection of tools for \"Literate Programming\". Unlike WEB or CWEB it is not bound to a specific programming language like PASCAL or C.\r\n\r\nFor more informations about NOWEB, the sources or binary distributions\r\nhave a look at\r\n\r\nhttp:\/\/www.eecs.harvard.edu\/~nr\/noweb\r\n\r\nFor informations about \"Literate Programming\" in general\r\n\r\nhttp:\/\/www.literateprogramming.com\r\n\r\ncould be a place to start.\r\n","install_details":"Follow the instructions of \"new-filetype\" in the\r\nVIM manual, to edit\/create your local version of\r\n`filetype.vim'. The line for NOWEB files should\r\nread\r\n\r\n  au! BufRead,BufNewFile *.nw   setfiletype nw\r\n\r\nCopy `nw.vim' to your local syntax file directory\r\n(see \"mysyntaxfile\" in the VIM manual) and add\r\na copy of `tex.vim' from your VIM installation,\r\nsuch that `nw.vim' can find it.\r\n\r\nThat's it! (Remember to restart VIM...)\r\n","5":"Follow the instructions of \"new-filetype\" in the\r\nVIM manual, to edit\/create your local version of\r\n`filetype.vim'. The line for NOWEB files should\r\nread\r\n\r\n  au! BufRead,BufNewFile *.nw   setfiletype nw\r\n\r\nCopy `nw.vim' to your local syntax file directory\r\n(see \"mysyntaxfile\" in the VIM manual) and add\r\na copy of `tex.vim' from your VIM installation,\r\nsuch that `nw.vim' can find it.\r\n\r\nThat's it! (Remember to restart VIM...)\r\n","first_name":"Dirk","6":"Dirk","last_name":"B\u00c3\u00a4chle","7":"B\u00c3\u00a4chle","releases":[{"0":"462","vim_version":"6.0","1":"6.0","script_version":"1.1","2":"1.1","version_comment":"Bug fixed: Corrected `current_syntax = \"noweb\"' to `current_syntax = \"nw\"'","3":"Bug fixed: Corrected `current_syntax = \"noweb\"' to `current_syntax = \"nw\"'","package":"nw.vim","4":"nw.vim","src_id":"1355","5":"1355","creation_date":"1036041397","6":"1036041397"},{"0":"462","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"nw.vim","4":"nw.vim","src_id":"1346","5":"1346","creation_date":"1035866290","6":"1035866290"}]},"461":{"script_id":"461","0":"461","script_name":"TTCoach","1":"TTCoach","script_type":"utility","2":"utility","summary":"Utility to train touch typing skills","3":"Utility to train touch typing skills","description":"Detailed help in ttcoach.txt.\r\nInstall :help add-local-help\r\n\r\nThis plugin is very similar to to other touch type training programs and provide simple statistics (chars per minute, time, faults, faults per key and finger)","4":"Detailed help in ttcoach.txt.\r\nInstall :help add-local-help\r\n\r\nThis plugin is very similar to to other touch type training programs and provide simple statistics (chars per minute, time, faults, faults per key and finger)","install_details":"       Unpack ttcoach.zip file in your .vim or vimfiles directory. It will create\r\n       ttcoach directory with some files in it.\r\n       They should be:\r\n           macros\/ttcoach.vim - this file\r\n           files for training in macros\/ttcoach directory\r\n           doc\/ttcoach.txt\r\n           plugin\/ttcplug.vim\r\n","5":"       Unpack ttcoach.zip file in your .vim or vimfiles directory. It will create\r\n       ttcoach directory with some files in it.\r\n       They should be:\r\n           macros\/ttcoach.vim - this file\r\n           files for training in macros\/ttcoach directory\r\n           doc\/ttcoach.txt\r\n           plugin\/ttcplug.vim\r\n","first_name":"Mikolaj","6":"Mikolaj","last_name":"Machowski","7":"Machowski","releases":[{"0":"461","vim_version":"6.0","1":"6.0","script_version":"1.2","2":"1.2","version_comment":"Basic support for utf-8 &encoding - en and de work, pl and fr are broken.","3":"Basic support for utf-8 &encoding - en and de work, pl and fr are broken.","package":"ttcoach.zip","4":"ttcoach.zip","src_id":"2733","5":"2733","creation_date":"1076308605","6":"1076308605"},{"0":"461","vim_version":"6.0","1":"6.0","script_version":"1.1","2":"1.1","version_comment":"Major bugfixes (especially for Windows).","3":"Major bugfixes (especially for Windows).","package":"ttcoach.zip","4":"ttcoach.zip","src_id":"2703","5":"2703","creation_date":"1075611044","6":"1075611044"},{"0":"461","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":" - highlight bugs, not \":sleep\"\n - goals system\n - two new exercise files with Vim exercises: colon and sqbrackets\n - fixed bug with multiple keyboards attached \n - many small bugfixes \n - Show only ttc files in Explorer commands\n - Save statistics always with generation - it will free one F-key\n - Add ! to all :normal commands\n - TTCustom works on copies, not original files. Shi^W:wq happens\n - improvements in editing custom files\n - Menus\n - Give possibility to save Custom files in separate dir\n","3":" - highlight bugs, not \":sleep\"\n - goals system\n - two new exercise files with Vim exercises: colon and sqbrackets\n - fixed bug with multiple keyboards attached \n - many small bugfixes \n - Show only ttc files in Explorer commands\n - Save statistics always with generation - it will free one F-key\n - Add ! to all :normal commands\n - TTCustom works on copies, not original files. Shi^W:wq happens\n - improvements in editing custom files\n - Menus\n - Give possibility to save Custom files in separate dir\n","package":"ttcoach.zip","4":"ttcoach.zip","src_id":"2701","5":"2701","creation_date":"1075549387","6":"1075549387"},{"0":"461","vim_version":"6.0","1":"6.0","script_version":"0.9","2":"0.9","version_comment":"- drill: new exercise for Vim Normal mode commands\n- name of layout, exercise and accuracy in statusline\n- most important Fx shortcuts in statusline\n- add words per minute statistics\n- improved handling of small_help window\n- automatic highlighting with i,I commands (no need for F4)\n- remove blank lines in TTCustom files\n- silencing of preparation commands\n","3":"- drill: new exercise for Vim Normal mode commands\n- name of layout, exercise and accuracy in statusline\n- most important Fx shortcuts in statusline\n- add words per minute statistics\n- improved handling of small_help window\n- automatic highlighting with i,I commands (no need for F4)\n- remove blank lines in TTCustom files\n- silencing of preparation commands\n","package":"ttcoach.zip","4":"ttcoach.zip","src_id":"2379","5":"2379","creation_date":"1065582659","6":"1065582659"},{"0":"461","vim_version":"6.0","1":"6.0","script_version":"0.8","2":"0.8","version_comment":"Vim TTCoach v. 0.8\n\nNew exercises:\n    Slovak\n\nNew command:\n    TTCustom - more in help file\n\nNew shortcut:\n    F1 - short help\n\nRemoved few bugs and moved ttcoach.vim to macros\/ttcoach. Now only two\nplaces to remove if you don't want to use TTCoach any longer :(\nPlease remove old version of TTCoach before installing this one.","3":"Vim TTCoach v. 0.8\n\nNew exercises:\n    Slovak\n\nNew command:\n    TTCustom - more in help file\n\nNew shortcut:\n    F1 - short help\n\nRemoved few bugs and moved ttcoach.vim to macros\/ttcoach. Now only two\nplaces to remove if you don't want to use TTCoach any longer :(\nPlease remove old version of TTCoach before installing this one.","package":"ttcoach.zip","4":"ttcoach.zip","src_id":"2328","5":"2328","creation_date":"1063337597","6":"1063337597"},{"0":"461","vim_version":"6.0","1":"6.0","script_version":"0.7.1","2":"0.7.1","version_comment":"bug fix release: incorrect variables in ttc_plug_en.vim","3":"bug fix release: incorrect variables in ttc_plug_en.vim","package":"ttcoach.zip","4":"ttcoach.zip","src_id":"1398","5":"1398","creation_date":"1037074907","6":"1037074907"},{"0":"461","vim_version":"6.0","1":"6.0","script_version":"0.7","2":"0.7","version_comment":"- ttcoach.vim is now layout independent; really improved F3 mapping; better use of :TTexplore command","3":"- ttcoach.vim is now layout independent; really improved F3 mapping; better use of :TTexplore command","package":"ttcoach.zip","4":"ttcoach.zip","src_id":"1397","5":"1397","creation_date":"1037067209","6":"1037067209"}]},"460":{"script_id":"460","0":"460","script_name":"rrd.vim","1":"rrd.vim","script_type":"ftplugin","2":"ftplugin","summary":"Edit RRD data with Vim.","3":"Edit RRD data with Vim.","description":"The RRD.vim package is a vim module that acts as a frontend to manipulating the data from a round-robin database created by Tobi Oetiker's excellent  RRDTool program. It uses rrdtool to export the data into XML which it syntax highlights, and to re-import it again once you have made your changes. For a full description see the README_rrdplugin.txt file.","4":"The RRD.vim package is a vim module that acts as a frontend to manipulating the data from a round-robin database created by Tobi Oetiker's excellent  RRDTool program. It uses rrdtool to export the data into XML which it syntax highlights, and to re-import it again once you have made your changes. For a full description see the README_rrdplugin.txt file.","install_details":"To install untar-gzip this package in your local vim directory (I.e. $HOME\/.vim or $VIM\/vimfiles) it will drop all of the files into place. Then read the readme file for details on adding the help docs to your own local help docs. You can then read the helpdocs for details on the program.","5":"To install untar-gzip this package in your local vim directory (I.e. $HOME\/.vim or $VIM\/vimfiles) it will drop all of the files into place. Then read the readme file for details on adding the help docs to your own local help docs. You can then read the helpdocs for details on the program.","first_name":"Colin","6":"Colin","last_name":"Keith","7":"Keith","releases":[{"0":"460","vim_version":"6.0","1":"6.0","script_version":"1.1","2":"1.1","version_comment":"Added support for adding\/removing entire RRD datasets.\r\nFold text printed (more) prettily","3":"Added support for adding\/removing entire RRD datasets.\r\nFold text printed (more) prettily","package":"rrd.tar.gz","4":"rrd.tar.gz","src_id":"1373","5":"1373","creation_date":"1036404311","6":"1036404311"}]},"459":{"script_id":"459","0":"459","script_name":"vim-templates","1":"vim-templates","script_type":"ftplugin","2":"ftplugin","summary":"Handling of templates and Pre\/Post editing commands","3":"Handling of templates and Pre\/Post editing commands","description":"This package can read\/generate templates throught functions defined in ftplugins for that filetype.\r\n\r\nAlso here is functions which throught autocommands performs actions from that ftplugin.\r\n\r\nDocumentation and some examples are in package archive.","4":"This package can read\/generate templates throught functions defined in ftplugins for that filetype.\r\n\r\nAlso here is functions which throught autocommands performs actions from that ftplugin.\r\n\r\nDocumentation and some examples are in package archive.","install_details":"Look at documentation in package.","5":"Look at documentation in package.","first_name":"Karel","6":"Karel","last_name":"Vaigl","7":"Vaigl","releases":[{"0":"459","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"vim-templates-0.1.tar.bz2","4":"vim-templates-0.1.tar.bz2","src_id":"1340","5":"1340","creation_date":"1035692485","6":"1035692485"}]},"458":{"script_id":"458","0":"458","script_name":"PCP header","1":"PCP header","script_type":"utility","2":"utility","summary":"Templating\/Header updating automation","3":"Templating\/Header updating automation","description":"This plugin provides templating and automatic header updating capabilities to Vim. Header writing enables Vim to automatically write and update headers to arbitrary filetypes.  It works by a templating method, where the user provides standardized templates and when editing a new file Vim will check if a template exists for the 'filetype' and use it.  The user will then be asked to fill in some information before starting to edit the file and Vim will then use this information to generate a new file from the template. Blah, blah, ...simply download, install, run :helptags and read the provided documentation with\r\n             :help header-qstart\r\n","4":"This plugin provides templating and automatic header updating capabilities to Vim. Header writing enables Vim to automatically write and update headers to arbitrary filetypes.  It works by a templating method, where the user provides standardized templates and when editing a new file Vim will check if a template exists for the 'filetype' and use it.  The user will then be asked to fill in some information before starting to edit the file and Vim will then use this information to generate a new file from the template. Blah, blah, ...simply download, install, run :helptags and read the provided documentation with\r\n             :help header-qstart\r\n","install_details":"save\/copy the file to your ~\/.vim directory, cd to ~\/.vim if not there. next run 'tar zxvf pcpheader-1.0.0.tar.gz' or appropriate version string. finally start up vim and run :helptags ~\/.vim\/doc to regenerate the tags table. and you are set!","5":"save\/copy the file to your ~\/.vim directory, cd to ~\/.vim if not there. next run 'tar zxvf pcpheader-1.0.0.tar.gz' or appropriate version string. finally start up vim and run :helptags ~\/.vim\/doc to regenerate the tags table. and you are set!","first_name":"Nikolai","6":"Nikolai","last_name":"Weibull","7":"Weibull","releases":[{"0":"458","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"pcpheader-1.0.0.tar.gz","4":"pcpheader-1.0.0.tar.gz","src_id":"1335","5":"1335","creation_date":"1035466780","6":"1035466780"}]},"457":{"script_id":"457","0":"457","script_name":"noweb.vim","1":"noweb.vim","script_type":"syntax","2":"syntax","summary":"folding noweb documents.","3":"folding noweb documents.","description":"Folds noweb code chunks.","4":"Folds noweb code chunks.","install_details":"Move into vim\/syntax.","5":"Move into vim\/syntax.","first_name":"engelbert","6":"engelbert","last_name":"gruber","7":"gruber","releases":[{"0":"457","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"noweb.vim","4":"noweb.vim","src_id":"1333","5":"1333","creation_date":"1035429956","6":"1035429956"}]},"456":{"script_id":"456","0":"456","script_name":"xgen.vim","1":"xgen.vim","script_type":"utility","2":"utility","summary":"XML-Element generator for HTML, DTD, SVG, XSLFO, XSLT and XML-Schema","3":"XML-Element generator for HTML, DTD, SVG, XSLFO, XSLT and XML-Schema","description":"\" Overview\r\n\" --------\r\n\"\r\n\" xgen.vim generates a menu for GENeration Xml-Element templates\r\n\" for different W3C-Recommondations.\r\n\"\r\n\" In addition to generation you can browse through the\r\n\" recommendation structure and have some simple but useful commands.\r\n\"\r\n\" You can find the following recommondations in the xGen-menu\r\n\" if they are enabled. Each one can be enable and disabled in\r\n\" this menu. If all an enable, the performance might be influenced.\r\n\" \r\n\" dtd:  Document Type Definitions for XML 1.0\r\n\"\r\n\" fo:   Extensible Stylesheet Language (XSL) Version 1.0\r\n\"       Recommendation 15 October 2001\r\n\"\r\n\" html: Extensible HTML version 1.0 Strict DTD\r\n\"\r\n\" svg:  SVG 1.0 2001 September 04\r\n\"\r\n\" xsd : XML Schema \r\n\"       Recommendation, 2 May 2001 \r\n\"\r\n\" xsl : XSL Transformations (XSLT) Version 1.0\r\n\"       Recommendation 16 November 1999\r\n\"\r\n\"\r\n\"\r\n\"\r\n\" XML-menu structure\r\n\" --------------\r\n\"\r\n\" TEMPLATES  : to generate some of my favourite templates\r\n\" MIN        : to generate the element with all required attributes\r\n\" MAX        : to generate the element with all attributes\r\n\" ------------\r\n\" ROOTS      : shows all root-elements and generates them, including\r\n\"              the <?xml ... and the xmlns\r\n\" BROWSE     : shows all possible child element for all elements,\r\n\"              so you can analyse the structure\r\n\" ------------\r\n\" FILL       : after creation, the elements are empty with a \r\n\"              closing \/>. Use FILL to splitt the element\r\n\" >>         : the creation in done in the next line. Often\r\n\"              it is useful to shift the new element to the right\r\n\" <<         : to correct a shift to the left\r\n\" AUTOINDENT : normaly generation is most efficient with autoindent\r\n\"\r\n\"\r\n\" DTD-menu structure\r\n\" ------------------\r\n\"\r\n\" For DTD, only MIN, AUTOINDENT, >> and << are suported.\r\n\"\r\n\" The MIN-Structure inside the dtd.MIN, can be used in a\r\n\" comparable way. The items sould be \"self explaining\". Some\r\n\" specials are:\r\n\" \r\n\" ATTRIBUTE-FIXED    : CDATA FIXED\r\n\" ATTRIBUTE-IMPLIED  : CDATA IMPLIED\r\n\" ATTRIBUTE-REQUIRED : CDATA REQUIRED\r\n\" ATTRIBUTE-VALUE    : CDATA VALUE\r\n\" ATTRIBUTE-VALUE-*  : replaces \" CDATA \" in the for about cases\r\n\"\r\n\" DOCTYPE-EXTERNAL   : external SYSTEM DOCTYPE\r\n\" DOCTYPE-MIXED      : mixed SYSTEM DOCTYPE\r\n\" DOCTYPE-PUBLIC     : replaces \" SYSTEM \" to PUBLIC in the two\r\n\"                      above cases\r\n\"","4":"\" Overview\r\n\" --------\r\n\"\r\n\" xgen.vim generates a menu for GENeration Xml-Element templates\r\n\" for different W3C-Recommondations.\r\n\"\r\n\" In addition to generation you can browse through the\r\n\" recommendation structure and have some simple but useful commands.\r\n\"\r\n\" You can find the following recommondations in the xGen-menu\r\n\" if they are enabled. Each one can be enable and disabled in\r\n\" this menu. If all an enable, the performance might be influenced.\r\n\" \r\n\" dtd:  Document Type Definitions for XML 1.0\r\n\"\r\n\" fo:   Extensible Stylesheet Language (XSL) Version 1.0\r\n\"       Recommendation 15 October 2001\r\n\"\r\n\" html: Extensible HTML version 1.0 Strict DTD\r\n\"\r\n\" svg:  SVG 1.0 2001 September 04\r\n\"\r\n\" xsd : XML Schema \r\n\"       Recommendation, 2 May 2001 \r\n\"\r\n\" xsl : XSL Transformations (XSLT) Version 1.0\r\n\"       Recommendation 16 November 1999\r\n\"\r\n\"\r\n\"\r\n\"\r\n\" XML-menu structure\r\n\" --------------\r\n\"\r\n\" TEMPLATES  : to generate some of my favourite templates\r\n\" MIN        : to generate the element with all required attributes\r\n\" MAX        : to generate the element with all attributes\r\n\" ------------\r\n\" ROOTS      : shows all root-elements and generates them, including\r\n\"              the <?xml ... and the xmlns\r\n\" BROWSE     : shows all possible child element for all elements,\r\n\"              so you can analyse the structure\r\n\" ------------\r\n\" FILL       : after creation, the elements are empty with a \r\n\"              closing \/>. Use FILL to splitt the element\r\n\" >>         : the creation in done in the next line. Often\r\n\"              it is useful to shift the new element to the right\r\n\" <<         : to correct a shift to the left\r\n\" AUTOINDENT : normaly generation is most efficient with autoindent\r\n\"\r\n\"\r\n\" DTD-menu structure\r\n\" ------------------\r\n\"\r\n\" For DTD, only MIN, AUTOINDENT, >> and << are suported.\r\n\"\r\n\" The MIN-Structure inside the dtd.MIN, can be used in a\r\n\" comparable way. The items sould be \"self explaining\". Some\r\n\" specials are:\r\n\" \r\n\" ATTRIBUTE-FIXED    : CDATA FIXED\r\n\" ATTRIBUTE-IMPLIED  : CDATA IMPLIED\r\n\" ATTRIBUTE-REQUIRED : CDATA REQUIRED\r\n\" ATTRIBUTE-VALUE    : CDATA VALUE\r\n\" ATTRIBUTE-VALUE-*  : replaces \" CDATA \" in the for about cases\r\n\"\r\n\" DOCTYPE-EXTERNAL   : external SYSTEM DOCTYPE\r\n\" DOCTYPE-MIXED      : mixed SYSTEM DOCTYPE\r\n\" DOCTYPE-PUBLIC     : replaces \" SYSTEM \" to PUBLIC in the two\r\n\"                      above cases\r\n\"","install_details":"Just :source xgen.vim an you'll receive the xGen Menu.","5":"Just :source xgen.vim an you'll receive the xGen Menu.","first_name":"Wolf","6":"Wolf","last_name":"Sluyterman van Langeweyde","7":"Sluyterman van Langeweyde","releases":[{"0":"456","vim_version":"6.0","1":"6.0","script_version":"2.0.1","2":"2.0.1","version_comment":"Bugfix for DTD EMPTY","3":"Bugfix for DTD EMPTY","package":"xgen.zip","4":"xgen.zip","src_id":"2096","5":"2096","creation_date":"1055944837","6":"1055944837"},{"0":"456","vim_version":"6.0","1":"6.0","script_version":"2.0","2":"2.0","version_comment":"New featues\r\nHTML\r\nSVG\r\nDTD\r\nUser controled disable and enable to increase performance.","3":"New featues\r\nHTML\r\nSVG\r\nDTD\r\nUser controled disable and enable to increase performance.","package":"xgen.zip","4":"xgen.zip","src_id":"1997","5":"1997","creation_date":"1053259908","6":"1053259908"},{"0":"456","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"xgen.zip","4":"xgen.zip","src_id":"1330","5":"1330","creation_date":"1035292276","6":"1035292276"}]},"455":{"script_id":"455","0":"455","script_name":"php_abb","1":"php_abb","script_type":"ftplugin","2":"ftplugin","summary":"abbreviations for php functions","3":"abbreviations for php functions","description":"php_abb is a ftplugin for php, mostly providing insert mode abbreviations\r\nfor php builtin functions and control structures.  These abbreviations\r\nexpand to function stubs and should help you remember the syntax in\r\naddition to speeding typing.  A map-like function that does a number of\r\npossibly obtuse things is also included.\r\n\r\nThe insert mode abbreviations come in two falvors: those using the raw\r\nphp function name (these can be disabled) and those prefixed with g:phpLeader.  \r\nSee the help file for details.\r\n\r\nThe phpActOnVariable function performs a number of activities on the php\r\nvariable under your cursor at the time the function is executed.  You should\r\ncreate a map to this function.  As an example of how you would use this, say you\r\nhave mapped it to <leader>m and you have your cursor on any letter in the word\r\ntest in the following code:\r\n\r\n     $test = \"FooBaR\";\r\n\r\nIf you then type <leader>m and strtl<cr> a new line will be opened underneath\r\nand the following code will be inserted:\r\n\r\n     $test = strtolower($test);\r\n\r\nYou can see a list of all the mappings for this function by executing the\r\nfunction and entering '?' when prompted.","4":"php_abb is a ftplugin for php, mostly providing insert mode abbreviations\r\nfor php builtin functions and control structures.  These abbreviations\r\nexpand to function stubs and should help you remember the syntax in\r\naddition to speeding typing.  A map-like function that does a number of\r\npossibly obtuse things is also included.\r\n\r\nThe insert mode abbreviations come in two falvors: those using the raw\r\nphp function name (these can be disabled) and those prefixed with g:phpLeader.  \r\nSee the help file for details.\r\n\r\nThe phpActOnVariable function performs a number of activities on the php\r\nvariable under your cursor at the time the function is executed.  You should\r\ncreate a map to this function.  As an example of how you would use this, say you\r\nhave mapped it to <leader>m and you have your cursor on any letter in the word\r\ntest in the following code:\r\n\r\n     $test = \"FooBaR\";\r\n\r\nIf you then type <leader>m and strtl<cr> a new line will be opened underneath\r\nand the following code will be inserted:\r\n\r\n     $test = strtolower($test);\r\n\r\nYou can see a list of all the mappings for this function by executing the\r\nfunction and entering '?' when prompted.","install_details":"Untar in your ~\/.vim directory (or equivalent).  Inside Vim, enter this:\r\n   :helptags ~\/.vim\/doc\r\n(or equivalent directory)\r\n\r\nThen enter\r\n  :help php_abb\r\nfor information \r\n\r\nYou should create a few maps similar to:\r\n\r\nimap <F7>  <esc>:call ReplacePlaceHolder()<cr>a\r\nnmap <F7>  :call ReplacePlaceHolder()<cr>\r\nnmap <leader>m <esc>:call PhpActOnVariable()<cr>\r\n\r\nin the main script or in another php ftplugin file.  Something like:\r\n\r\n~\/.vim\/ftplugin\/php_settings.vim","5":"Untar in your ~\/.vim directory (or equivalent).  Inside Vim, enter this:\r\n   :helptags ~\/.vim\/doc\r\n(or equivalent directory)\r\n\r\nThen enter\r\n  :help php_abb\r\nfor information \r\n\r\nYou should create a few maps similar to:\r\n\r\nimap <F7>  <esc>:call ReplacePlaceHolder()<cr>a\r\nnmap <F7>  :call ReplacePlaceHolder()<cr>\r\nnmap <leader>m <esc>:call PhpActOnVariable()<cr>\r\n\r\nin the main script or in another php ftplugin file.  Something like:\r\n\r\n~\/.vim\/ftplugin\/php_settings.vim","first_name":"culley","6":"culley","last_name":"harrelson","7":"harrelson","releases":[{"0":"455","vim_version":"6.0","1":"6.0","script_version":"1.1","2":"1.1","version_comment":"Added 3 new settings: g:phpNewlineBeforeBrace, g:phpFoldMarkerFunctions, g:phpRequireIncludeParens.  I also added support for the following php functions: is_null, is_numeric, empty","3":"Added 3 new settings: g:phpNewlineBeforeBrace, g:phpFoldMarkerFunctions, g:phpRequireIncludeParens.  I also added support for the following php functions: is_null, is_numeric, empty","package":"php_abb.tar","4":"php_abb.tar","src_id":"2024","5":"2024","creation_date":"1054107325","6":"1054107325"},{"0":"455","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Complete rewrite.  The theme of this rewrite was: quit polluting the mapping namespace, allow for most everything to be customized, remove all personal stuff from the script and write documentation.  All maps have been wrapped into a function and all abbreviations are now prefixed with g:phpLeader so you can change this variable and change the prefix for every abbreviation.  Abbreviations are now created in a more modular fashion so it should be much easier to maintain the script.  I have bumped the version to 1.0-- the structure should *finally* be mostly set so I can now focus on extending the script to cover additional php functions.","3":"Complete rewrite.  The theme of this rewrite was: quit polluting the mapping namespace, allow for most everything to be customized, remove all personal stuff from the script and write documentation.  All maps have been wrapped into a function and all abbreviations are now prefixed with g:phpLeader so you can change this variable and change the prefix for every abbreviation.  Abbreviations are now created in a more modular fashion so it should be much easier to maintain the script.  I have bumped the version to 1.0-- the structure should *finally* be mostly set so I can now focus on extending the script to cover additional php functions.","package":"php_abb.tar","4":"php_abb.tar","src_id":"2016","5":"2016","creation_date":"1053900143","6":"1053900143"},{"0":"455","vim_version":"6.0","1":"6.0","script_version":".4","2":".4","version_comment":"++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++\r\nscript version .4\r\nUloaded to vim.org 2003-05-03\r\n++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++\r\n\r\n--------------------------------------------------------------\r\nphp functions added\r\n--------------------------------------------------------------\r\nbool array_key_exists ( mixed key, array search)\r\nint count ( mixed var)\r\nstring htmlspecialchars ( string string [, int quote_style [, string charset]])\r\nstring strstr ( string haystack, string needle)\r\nint strcasecmp ( string str1, string str2)\r\nstring substr ( string string, int start [, int length])\r\nvoid trigger_error ( string error_msg [, int error_type])\r\n\r\n--------------------------------------------------------------\r\nnew PEAR DB stuff\r\n--------------------------------------------------------------\r\nphpgr -- $data = $dbh->getRow($sql);<cursor>\r\nphpgcol -- $dbh->getCol($sql);<cursor>\r\nphpni -- $<cursor> = $dbh->nextId('php~x', false);\r\n\r\n--------------------------------------------------------------\r\nmisc new stuff\r\n--------------------------------------------------------------\r\nphptodo -- \/\/TODO:\r\n","3":"++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++\r\nscript version .4\r\nUloaded to vim.org 2003-05-03\r\n++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++\r\n\r\n--------------------------------------------------------------\r\nphp functions added\r\n--------------------------------------------------------------\r\nbool array_key_exists ( mixed key, array search)\r\nint count ( mixed var)\r\nstring htmlspecialchars ( string string [, int quote_style [, string charset]])\r\nstring strstr ( string haystack, string needle)\r\nint strcasecmp ( string str1, string str2)\r\nstring substr ( string string, int start [, int length])\r\nvoid trigger_error ( string error_msg [, int error_type])\r\n\r\n--------------------------------------------------------------\r\nnew PEAR DB stuff\r\n--------------------------------------------------------------\r\nphpgr -- $data = $dbh->getRow($sql);<cursor>\r\nphpgcol -- $dbh->getCol($sql);<cursor>\r\nphpni -- $<cursor> = $dbh->nextId('php~x', false);\r\n\r\n--------------------------------------------------------------\r\nmisc new stuff\r\n--------------------------------------------------------------\r\nphptodo -- \/\/TODO:\r\n","package":"php.tar","4":"php.tar","src_id":"1964","5":"1964","creation_date":"1051946195","6":"1051946195"},{"0":"455","vim_version":"6.0","1":"6.0","script_version":".3","2":".3","version_comment":"Complete rewrite.  The new format should allow me to continue through the built in php functions till I die.  See the script header for details.\r\n\r\nNew items:\r\n\r\necho\r\nexplode\r\nrequire_once()\r\nstrlen\r\nstrcmp\r\nstr_replace\r\nstrtolower\r\nstrtoupper\r\nunset\r\nwordwrap\r\n\r\nThere are about 6 or 7 other new things that I can't remember...\r\n\r\n","3":"Complete rewrite.  The new format should allow me to continue through the built in php functions till I die.  See the script header for details.\r\n\r\nNew items:\r\n\r\necho\r\nexplode\r\nrequire_once()\r\nstrlen\r\nstrcmp\r\nstr_replace\r\nstrtolower\r\nstrtoupper\r\nunset\r\nwordwrap\r\n\r\nThere are about 6 or 7 other new things that I can't remember...\r\n\r\n","package":"php.tar","4":"php.tar","src_id":"1425","5":"1425","creation_date":"1037431288","6":"1037431288"},{"0":"455","vim_version":"6.0","1":"6.0","script_version":".2","2":".2","version_comment":"new abbreviations:\r\n\r\nphplv     - look up the last value from a postgresql sequence\r\nphpserver - output $_SERVER['<cursor']\r\nphpgassoc - output $data = $dbh->getAssoc($sql);\r\nphpwhile  - output while structure\r\n\r\nnew maps:\r\n\r\n<leader>ap  - when on an array variable open a line under cursor and output an array_push function\r\n<leader>ae  - when on an array variable open a line under cursor and output the extract function\r\n<leader>apr - when on an array variable open a line under cursor and output the print_r function\r\n\r\n\r\n","3":"new abbreviations:\r\n\r\nphplv     - look up the last value from a postgresql sequence\r\nphpserver - output $_SERVER['<cursor']\r\nphpgassoc - output $data = $dbh->getAssoc($sql);\r\nphpwhile  - output while structure\r\n\r\nnew maps:\r\n\r\n<leader>ap  - when on an array variable open a line under cursor and output an array_push function\r\n<leader>ae  - when on an array variable open a line under cursor and output the extract function\r\n<leader>apr - when on an array variable open a line under cursor and output the print_r function\r\n\r\n\r\n","package":"php.vim","4":"php.vim","src_id":"1356","5":"1356","creation_date":"1036080887","6":"1036080887"},{"0":"455","vim_version":"6.0","1":"6.0","script_version":".1","2":".1","version_comment":"Initial upload","3":"Initial upload","package":"php.vim","4":"php.vim","src_id":"1328","5":"1328","creation_date":"1035238243","6":"1035238243"}]},"454":{"script_id":"454","0":"454","script_name":"sql.vim","1":"sql.vim","script_type":"ftplugin","2":"ftplugin","summary":"ftplugin for SQL (Common for Oracle, Microsoft SQL Server, Sybase, ...)","3":"ftplugin for SQL (Common for Oracle, Microsoft SQL Server, Sybase, ...)","description":"This file should only contain values that are common to all SQL languages Oracle, Microsoft SQL Server, Sybase ASA\/ASE, MySQL, and so on.\r\n\r\nAttention Vim7 users\r\n-----------------------------\r\nftplugin\/sql.vim version 10.0 is included in the Vim 7.3 patches. \r\nftplugin\/sql.vim previous versions have been sent to Bram when updates are made and they are always part of the Vim release.  Runtime updates can be pulled from the Vim website or through Vim patches.\r\n\r\nftplugin\/sql.vim version 1.0 is included in the Vim 7.0 release. \r\nVersion 0.04 is included with Vim 6.3.\r\n\r\nThis is the main file for supporting different SQL dialects (Oracle, DB2, Sybase, MySQL, Postgres, SQLite and so on) in Vim.  There are many features within which allow you to default your buffer to specific database dialects as well as change each buffer (at any time) to a different SQL dialect.\r\n\r\nSee :h sql.txt for more details.\r\n\r\nPatterns have been defined for the matchit plugin, to use the % command to match statements.  Supported patterns are:\r\n        begin\r\n        end\r\n                                   \r\n        if\r\n        elseif | elsif\r\n        else [if]\r\n        end if\r\n                                   \r\n        [while condition] loop\r\n            leave\r\n            break\r\n            continue\r\n            exit\r\n        end loop\r\n                                   \r\n        for\r\n            leave\r\n            break\r\n            continue\r\n            exit\r\n        end loop\r\n                                   \r\n        case\r\n        when \r\n        when\r\n        end case\r\n                                   \r\n        merge\r\n        when not matched\r\n        when matched\r\n                                   \r\n        EXCEPTION\r\n        WHEN column_not_found THEN\r\n        WHEN OTHERS THEN\r\n\r\nDefine how to find the macro definition of a variable using the various\r\n[d, [D, [_CTRL_D and so on features ( see :h [d )\r\n\r\nMatch these values ignoring case:\r\ni.e.  DECLARE varname INTEGER\r\n\r\nAdded additional buffer mappings which work in both normal and visual mode:\r\n        ]] - next BEGIN\r\n        [[ - previous BEGIN\r\n        ][ - next END\r\n        [] - previous END\r\n\r\nThe following mappings also work in normal and visual mode.\r\nA global variable has been defined to control the behaviour of these maps.  You can override this variable in your vimrc file if it is not complete, or as new objects are added to other databases.\r\n    let g:ftplugin_sql_objects = 'function,procedure,event,' .\r\n                \\ '\\(existing\\\\|global\\s\\+temporary\\s\\+\\)\\?table,trigger' .\r\n                \\ ',schema,service,publication,database,datatype,domain' .\r\n                \\ ',index,subscription,synchronization,view,variable'\r\n\r\n        ]} - Next CREATE statement (of the above types)\r\n        [{ - Previous CREATE statement (of the above types)\r\n\r\nThese mappings also work in both normal and visual mode.\r\n        ]\" - Next comment\r\n        [\" - End of previous comment \r\n\r\nIt also sets up Vim's OMNI SQL completion which calls into autoload\/SQLComplete.vim  (this file is also automatically included in the Vim distribution).  SQLComplete (http:\/\/www.vim.org\/scripts\/script.php?script_id=1572) is also updated on the website and can be downloaded separately.  A raft of insert mode mappings have been created to allow you to write your SQL more efficiently.\r\n\r\nThere is a user defined keyboard shortcut (i.e. <CTRL-C>) followed by a single letter to initiate the imaps.\r\n\r\nIf you are using a syntax enabled Vim:\r\n    a - Complete based on current syntax\r\n    k - Complete based on sqlKeywords\r\n    f - Complete based on sqlFunctions\r\n    o - Complete based on sqlOptions\r\n    T - Complete based on sqlTypes\r\n    s - Complete based on sqlStatements\r\n\r\nIf the dbext plugin (http:\/\/www.vim.org\/scripts\/script.php?script_id=356) is installed and can connect to your database:\r\n    t - Complete based on tables\r\n    p - Complete based on procedures\r\n    v - Complete based on views\r\n    c - Complete based on columns\r\n    l - Return a comma separated list of columns for a table\r\n    L - Return a comma separated list of columns for a table when a list of tables is shown\r\n    R - Complete based on resetCaches\r\n    Right Arrow - Drill into table to show columns\r\n    Left Arrow  - Back to table list\r\n\r\n","4":"This file should only contain values that are common to all SQL languages Oracle, Microsoft SQL Server, Sybase ASA\/ASE, MySQL, and so on.\r\n\r\nAttention Vim7 users\r\n-----------------------------\r\nftplugin\/sql.vim version 10.0 is included in the Vim 7.3 patches. \r\nftplugin\/sql.vim previous versions have been sent to Bram when updates are made and they are always part of the Vim release.  Runtime updates can be pulled from the Vim website or through Vim patches.\r\n\r\nftplugin\/sql.vim version 1.0 is included in the Vim 7.0 release. \r\nVersion 0.04 is included with Vim 6.3.\r\n\r\nThis is the main file for supporting different SQL dialects (Oracle, DB2, Sybase, MySQL, Postgres, SQLite and so on) in Vim.  There are many features within which allow you to default your buffer to specific database dialects as well as change each buffer (at any time) to a different SQL dialect.\r\n\r\nSee :h sql.txt for more details.\r\n\r\nPatterns have been defined for the matchit plugin, to use the % command to match statements.  Supported patterns are:\r\n        begin\r\n        end\r\n                                   \r\n        if\r\n        elseif | elsif\r\n        else [if]\r\n        end if\r\n                                   \r\n        [while condition] loop\r\n            leave\r\n            break\r\n            continue\r\n            exit\r\n        end loop\r\n                                   \r\n        for\r\n            leave\r\n            break\r\n            continue\r\n            exit\r\n        end loop\r\n                                   \r\n        case\r\n        when \r\n        when\r\n        end case\r\n                                   \r\n        merge\r\n        when not matched\r\n        when matched\r\n                                   \r\n        EXCEPTION\r\n        WHEN column_not_found THEN\r\n        WHEN OTHERS THEN\r\n\r\nDefine how to find the macro definition of a variable using the various\r\n[d, [D, [_CTRL_D and so on features ( see :h [d )\r\n\r\nMatch these values ignoring case:\r\ni.e.  DECLARE varname INTEGER\r\n\r\nAdded additional buffer mappings which work in both normal and visual mode:\r\n        ]] - next BEGIN\r\n        [[ - previous BEGIN\r\n        ][ - next END\r\n        [] - previous END\r\n\r\nThe following mappings also work in normal and visual mode.\r\nA global variable has been defined to control the behaviour of these maps.  You can override this variable in your vimrc file if it is not complete, or as new objects are added to other databases.\r\n    let g:ftplugin_sql_objects = 'function,procedure,event,' .\r\n                \\ '\\(existing\\\\|global\\s\\+temporary\\s\\+\\)\\?table,trigger' .\r\n                \\ ',schema,service,publication,database,datatype,domain' .\r\n                \\ ',index,subscription,synchronization,view,variable'\r\n\r\n        ]} - Next CREATE statement (of the above types)\r\n        [{ - Previous CREATE statement (of the above types)\r\n\r\nThese mappings also work in both normal and visual mode.\r\n        ]\" - Next comment\r\n        [\" - End of previous comment \r\n\r\nIt also sets up Vim's OMNI SQL completion which calls into autoload\/SQLComplete.vim  (this file is also automatically included in the Vim distribution).  SQLComplete (http:\/\/www.vim.org\/scripts\/script.php?script_id=1572) is also updated on the website and can be downloaded separately.  A raft of insert mode mappings have been created to allow you to write your SQL more efficiently.\r\n\r\nThere is a user defined keyboard shortcut (i.e. <CTRL-C>) followed by a single letter to initiate the imaps.\r\n\r\nIf you are using a syntax enabled Vim:\r\n    a - Complete based on current syntax\r\n    k - Complete based on sqlKeywords\r\n    f - Complete based on sqlFunctions\r\n    o - Complete based on sqlOptions\r\n    T - Complete based on sqlTypes\r\n    s - Complete based on sqlStatements\r\n\r\nIf the dbext plugin (http:\/\/www.vim.org\/scripts\/script.php?script_id=356) is installed and can connect to your database:\r\n    t - Complete based on tables\r\n    p - Complete based on procedures\r\n    v - Complete based on views\r\n    c - Complete based on columns\r\n    l - Return a comma separated list of columns for a table\r\n    L - Return a comma separated list of columns for a table when a list of tables is shown\r\n    R - Complete based on resetCaches\r\n    Right Arrow - Drill into table to show columns\r\n    Left Arrow  - Back to table list\r\n\r\n","install_details":"Copy into your .vim\/ftplugin or vimfiles\/ftplugin directory.","5":"Copy into your .vim\/ftplugin or vimfiles\/ftplugin directory.","first_name":"David","6":"David","last_name":"Fishburn","7":"Fishburn","releases":[{"0":"454","vim_version":"7.0","1":"7.0","script_version":"10.0","2":"10.0","version_comment":"Version 10.0 (Dec 2012)\r\n                                                                            \r\nNF: Changed all maps to use noremap instead of must map\r\n\r\nNF: Changed all visual maps to use xnoremap instead of vnoremap as they should only be used in visual mode and not select mode.\r\n\r\nBF: Most of the maps were using doubled up backslashes before they were changed to using the search() function, which meant they no longer worked.\r\n                                                                            \r\nVersion 9.0\r\n                                                                            \r\nNF: Completes 'b:undo_ftplugin'\r\nBF: Correctly set cpoptions when creating script\r\n                                                                            \r\nVersion 8.0\r\n                                                                            \r\nNF: Improved the matchit plugin regex (Talek)\r\n                                                                            \r\nVersion 7.0\r\n                                                                            \r\nNF: Calls the sqlcomplete#ResetCacheSyntax() function when calling SQLSetType.\r\n                                                                            \r\nVersion 6.0\r\n                                                                            \r\nNF: Adds the command SQLGetType\r\n                                                                            \r\nVersion 5.0\r\n                                                                            \r\nNF: Adds the ability to choose the keys to control SQL completion, just add the following to your .vimrc:\r\n   let g:ftplugin_sql_omni_key       = '<C-C>'\r\n   let g:ftplugin_sql_omni_key_right = '<Right>'\r\n   let g:ftplugin_sql_omni_key_left  = '<Left>'\r\n                                                                            \r\nBF: format-options - Auto-wrap comments using textwidth was turned off by mistake.\r\n","3":"Version 10.0 (Dec 2012)\r\n                                                                            \r\nNF: Changed all maps to use noremap instead of must map\r\n\r\nNF: Changed all visual maps to use xnoremap instead of vnoremap as they should only be used in visual mode and not select mode.\r\n\r\nBF: Most of the maps were using doubled up backslashes before they were changed to using the search() function, which meant they no longer worked.\r\n                                                                            \r\nVersion 9.0\r\n                                                                            \r\nNF: Completes 'b:undo_ftplugin'\r\nBF: Correctly set cpoptions when creating script\r\n                                                                            \r\nVersion 8.0\r\n                                                                            \r\nNF: Improved the matchit plugin regex (Talek)\r\n                                                                            \r\nVersion 7.0\r\n                                                                            \r\nNF: Calls the sqlcomplete#ResetCacheSyntax() function when calling SQLSetType.\r\n                                                                            \r\nVersion 6.0\r\n                                                                            \r\nNF: Adds the command SQLGetType\r\n                                                                            \r\nVersion 5.0\r\n                                                                            \r\nNF: Adds the ability to choose the keys to control SQL completion, just add the following to your .vimrc:\r\n   let g:ftplugin_sql_omni_key       = '<C-C>'\r\n   let g:ftplugin_sql_omni_key_right = '<Right>'\r\n   let g:ftplugin_sql_omni_key_left  = '<Left>'\r\n                                                                            \r\nBF: format-options - Auto-wrap comments using textwidth was turned off by mistake.\r\n","package":"sql.vim","4":"sql.vim","src_id":"19131","5":"19131","creation_date":"1354897192","6":"1354897192"},{"0":"454","vim_version":"6.0","1":"6.0","script_version":"0.08","2":"0.08","version_comment":"Missed an = sign, <sigh>","3":"Missed an = sign, <sigh>","package":"sql.vim","4":"sql.vim","src_id":"3888","5":"3888","creation_date":"1108966358","6":"1108966358"},{"0":"454","vim_version":"6.0","1":"6.0","script_version":"0.07","2":"0.07","version_comment":"Very minor update.\r\n\r\nChanged this line:\r\nsetlocal cpo&vim\r\n\r\nTo:\r\nset cpo ","3":"Very minor update.\r\n\r\nChanged this line:\r\nsetlocal cpo&vim\r\n\r\nTo:\r\nset cpo ","package":"sql.vim","4":"sql.vim","src_id":"3886","5":"3886","creation_date":"1108923308","6":"1108923308"},{"0":"454","vim_version":"6.0","1":"6.0","script_version":"0.06","2":"0.06","version_comment":"Added some additional visual maps, and now allow the user to customize part of the search strings with this global variable: g:ftplugin_sql_objects\r\n","3":"Added some additional visual maps, and now allow the user to customize part of the search strings with this global variable: g:ftplugin_sql_objects\r\n","package":"sql.vim","4":"sql.vim","src_id":"3883","5":"3883","creation_date":"1108838715","6":"1108838715"},{"0":"454","vim_version":"6.0","1":"6.0","script_version":"0.05","2":"0.05","version_comment":"Added additional matchit.vim features.\r\nCreated additional buffer maps to assist in navigation:\r\n]] - next BEGIN\r\n[[ - previous BEGIN\r\n][ - next END\r\n[] - previous END\r\n\r\n]} - Next CREATE statement\r\n[{ - Previous CREATE statement\r\n\r\n]\" - Next comment\r\n[\" - End of previous comment\r\n","3":"Added additional matchit.vim features.\r\nCreated additional buffer maps to assist in navigation:\r\n]] - next BEGIN\r\n[[ - previous BEGIN\r\n][ - next END\r\n[] - previous END\r\n\r\n]} - Next CREATE statement\r\n[{ - Previous CREATE statement\r\n\r\n]\" - Next comment\r\n[\" - End of previous comment\r\n","package":"sql.vim","4":"sql.vim","src_id":"3659","5":"3659","creation_date":"1101368191","6":"1101368191"},{"0":"454","vim_version":"6.0","1":"6.0","script_version":"0.04","2":"0.04","version_comment":"Updated the IF...ELSE...END IF block to correct an error.","3":"Updated the IF...ELSE...END IF block to correct an error.","package":"sql.vim","4":"sql.vim","src_id":"2796","5":"2796","creation_date":"1078299689","6":"1078299689"}]},"453":{"script_id":"453","0":"453","script_name":"HTML\/XHTML Macros","1":"HTML\/XHTML Macros","script_type":"utility","2":"utility","summary":"HTML\/XHTML editing macros and menus","3":"HTML\/XHTML editing macros and menus","description":"This is a set of HTML\/XHTML mappings and menus for Vim 9 or later. The mappings will be local to the buffer so they won't interfere if you edit other files in the same Vim session.\r\n\r\nThe macros automatically insert a tag and position the cursor at the logical insert point.  For example, in insert the mapping \";ah\" inserts <A HREF=\"\"><\/A> and leaves the cursor between the double quotes.  If you were to visually highlight some text then type \";ah\" it would wrap the tag around the text.  For example:\r\n        some text\r\nBecomes:\r\n        <A HREF=\"\">some text<\/A>\r\nWith the cursor positioned between the double quotes in insert mode. Or if you used \";aH\" instead:\r\n        <A HREF=\"some text\"><\/A>\r\nWith the cursor positioned between the > and the < in insert mode.\r\n\r\nThere are many other features, such as a configurable template inserted with the \";html\" normal mode macro, browser remote control mappings, etc.\r\n\r\nSee https:\/\/christianrobinson.name\/assets\/programming\/faq.html for frequently asked questions.\r\n\r\nSee https:\/\/christianrobinson.name\/assets\/programming\/HTML.html to preview the help file.","4":"This is a set of HTML\/XHTML mappings and menus for Vim 9 or later. The mappings will be local to the buffer so they won't interfere if you edit other files in the same Vim session.\r\n\r\nThe macros automatically insert a tag and position the cursor at the logical insert point.  For example, in insert the mapping \";ah\" inserts <A HREF=\"\"><\/A> and leaves the cursor between the double quotes.  If you were to visually highlight some text then type \";ah\" it would wrap the tag around the text.  For example:\r\n        some text\r\nBecomes:\r\n        <A HREF=\"\">some text<\/A>\r\nWith the cursor positioned between the double quotes in insert mode. Or if you used \";aH\" instead:\r\n        <A HREF=\"some text\"><\/A>\r\nWith the cursor positioned between the > and the < in insert mode.\r\n\r\nThere are many other features, such as a configurable template inserted with the \";html\" normal mode macro, browser remote control mappings, etc.\r\n\r\nSee https:\/\/christianrobinson.name\/assets\/programming\/faq.html for frequently asked questions.\r\n\r\nSee https:\/\/christianrobinson.name\/assets\/programming\/HTML.html to preview the help file.","install_details":"Note: If you have an old installation of this plugin, you need to remove its files first or they may prevent the packed version from loading.\r\n\r\nPut \":filetype plugin on\" in your vimrc, then extract HTML.zip in your runtime directory (~\/.vim for Unix, %USERPROFILE%\\vimfiles for Windows; see \":help 'runtimepath'\").\r\n\r\nAlternatively you may use git. See: https:\/\/github.com\/Heptite\/HTML\r\n\r\nSee https:\/\/christianrobinson.name\/HTML for more information, newer versions, and extra files.","5":"Note: If you have an old installation of this plugin, you need to remove its files first or they may prevent the packed version from loading.\r\n\r\nPut \":filetype plugin on\" in your vimrc, then extract HTML.zip in your runtime directory (~\/.vim for Unix, %USERPROFILE%\\vimfiles for Windows; see \":help 'runtimepath'\").\r\n\r\nAlternatively you may use git. See: https:\/\/github.com\/Heptite\/HTML\r\n\r\nSee https:\/\/christianrobinson.name\/HTML for more information, newer versions, and extra files.","first_name":"Christian J.","6":"Christian J.","last_name":"Robinson","7":"Robinson","releases":[{"0":"453","vim_version":"9.0","1":"9.0","script_version":"1.3.6","2":"1.3.6","version_comment":"- File missing from zip archive","3":"- File missing from zip archive","package":"HTML.zip","4":"HTML.zip","src_id":"28545","5":"28545","creation_date":"1694426951","6":"1694426951"},{"0":"453","vim_version":"9.0","1":"9.0","script_version":"1.3.5","2":"1.3.5","version_comment":"- ;sN mapping for a <span> tag without attributes\r\n- Several internal changes, tweaks, bug fixes","3":"- ;sN mapping for a <span> tag without attributes\r\n- Several internal changes, tweaks, bug fixes","package":"HTML.zip","4":"HTML.zip","src_id":"28458","5":"28458","creation_date":"1683515040","6":"1683515040"},{"0":"453","vim_version":"9.0","1":"9.0","script_version":"1.3.0","2":"1.3.0","version_comment":"- Refactoring\r\n- Change logic for handling visual mappings","3":"- Refactoring\r\n- Change logic for handling visual mappings","package":"HTML.zip","4":"HTML.zip","src_id":"28112","5":"28112","creation_date":"1658904060","6":"1658904060"},{"0":"453","vim_version":"9.0","1":"9.0","script_version":"1.2.5","2":"1.2.5","version_comment":"- Fix :HTMLabout, plus documentation fixes (Ivan Pe\u00c5\u00a1ić)\r\n- Try catching some errors to prevent aborting of mappings which could cause options to be unset","3":"- Fix :HTMLabout, plus documentation fixes (Ivan Pe\u00c5\u00a1ić)\r\n- Try catching some errors to prevent aborting of mappings which could cause options to be unset","package":"HTML.zip","4":"HTML.zip","src_id":"28085","5":"28085","creation_date":"1657153614","6":"1657153614"},{"0":"453","vim_version":"9.0","1":"9.0","script_version":"1.2.4","2":"1.2.4","version_comment":"- Update minimum Vim version requirement to 9.0 now that Vim9 has been released","3":"- Update minimum Vim version requirement to 9.0 now that Vim9 has been released","package":"HTML.zip","4":"HTML.zip","src_id":"28082","5":"28082","creation_date":"1656463479","6":"1656463479"},{"0":"453","vim_version":"9.0","1":"9.0","script_version":"1.2.3","2":"1.2.3","version_comment":"- Fix character entity conversion mappings","3":"- Fix character entity conversion mappings","package":"HTML.zip","4":"HTML.zip","src_id":"27955","5":"27955","creation_date":"1646015838","6":"1646015838"},{"0":"453","vim_version":"9.0","1":"9.0","script_version":"1.2.2","2":"1.2.2","version_comment":"- Update to latest Vim9 syntax\r\n- Try to fix visual mapping issues","3":"- Update to latest Vim9 syntax\r\n- Try to fix visual mapping issues","package":"HTML.zip","4":"HTML.zip","src_id":"27940","5":"27940","creation_date":"1643887636","6":"1643887636"},{"0":"453","vim_version":"9.0","1":"9.0","script_version":"1.2.1","2":"1.2.1","version_comment":"- Small update with tweaks and to reflect the new vim9script syntax","3":"- Small update with tweaks and to reflect the new vim9script syntax","package":"HTML.zip","4":"HTML.zip","src_id":"27913","5":"27913","creation_date":"1642557322","6":"1642557322"},{"0":"453","vim_version":"9.0","1":"9.0","script_version":"1.2.0","2":"1.2.0","version_comment":"- More refactoring\r\n- Under the hood optimizations","3":"- More refactoring\r\n- Under the hood optimizations","package":"HTML.zip","4":"HTML.zip","src_id":"27911","5":"27911","creation_date":"1642339463","6":"1642339463"},{"0":"453","vim_version":"9.0","1":"9.0","script_version":"1.1.16","2":"1.1.16","version_comment":"- Update to use Vim9\\'s revised import syntax","3":"- Update to use Vim9\\'s revised import syntax","package":"HTML.zip","4":"HTML.zip","src_id":"27893","5":"27893","creation_date":"1641540596","6":"1641540596"},{"0":"453","vim_version":"9.0","1":"9.0","script_version":"1.1.15","2":"1.1.15","version_comment":"- Tweaks, and speed improvements\r\n- Some plugin commands are now local to the buffer","3":"- Tweaks, and speed improvements\r\n- Some plugin commands are now local to the buffer","package":"HTML.zip","4":"HTML.zip","src_id":"27749","5":"27749","creation_date":"1632630957","6":"1632630957"},{"0":"453","vim_version":"9.0","1":"9.0","script_version":"1.1.14","2":"1.1.14","version_comment":"- Support Brave browser\r\n- Image tag WIDTHxHEIGHT updater now supports a couple more image types ","3":"- Support Brave browser\r\n- Image tag WIDTHxHEIGHT updater now supports a couple more image types ","package":"HTML.zip","4":"HTML.zip","src_id":"27728","5":"27728","creation_date":"1630675614","6":"1630675614"},{"0":"453","vim_version":"9.0","1":"9.0","script_version":"1.1.13","2":"1.1.13","version_comment":"- Some bugs fixed\r\n- Some refactoring\r\n- Minor feature additions","3":"- Some bugs fixed\r\n- Some refactoring\r\n- Minor feature additions","package":"HTML.zip","4":"HTML.zip","src_id":"27723","5":"27723","creation_date":"1630300181","6":"1630300181"},{"0":"453","vim_version":"9.0","1":"9.0","script_version":"1.1.11","2":"1.1.11","version_comment":"- Fixed a bug that crept in while trying to fix other bugs.\r\n- Code tweaks.","3":"- Fixed a bug that crept in while trying to fix other bugs.\r\n- Code tweaks.","package":"HTML.zip","4":"HTML.zip","src_id":"27712","5":"27712","creation_date":"1629592931","6":"1629592931"},{"0":"453","vim_version":"9.0","1":"9.0","script_version":"1.1.10","2":"1.1.10","version_comment":"- Fix more bugs.\r\n- Simplify some code.","3":"- Fix more bugs.\r\n- Simplify some code.","package":"HTML.zip","4":"HTML.zip","src_id":"27711","5":"27711","creation_date":"1629292391","6":"1629292391"},{"0":"453","vim_version":"9.0","1":"9.0","script_version":"1.1.9","2":"1.1.9","version_comment":"- Loading bug fixed.\r\n- More entities.\r\n- Moved config variables to a unified dictionary.","3":"- Loading bug fixed.\r\n- More entities.\r\n- Moved config variables to a unified dictionary.","package":"HTML.zip","4":"HTML.zip","src_id":"27710","5":"27710","creation_date":"1629121065","6":"1629121065"},{"0":"453","vim_version":"9.0","1":"9.0","script_version":"1.1.8","2":"1.1.8","version_comment":"- More bugs were found and squashed.\r\n- Moved more data to json.","3":"- More bugs were found and squashed.\r\n- Moved more data to json.","package":"HTML.zip","4":"HTML.zip","src_id":"27708","5":"27708","creation_date":"1628951204","6":"1628951204"},{"0":"453","vim_version":"9.0","1":"9.0","script_version":"1.1.7","2":"1.1.7","version_comment":"- Some bugs crept in during the change over to json.\r\n- Code improvements.","3":"- Some bugs crept in during the change over to json.\r\n- Code improvements.","package":"HTML.zip","4":"HTML.zip","src_id":"27707","5":"27707","creation_date":"1628851047","6":"1628851047"},{"0":"453","vim_version":"9.0","1":"9.0","script_version":"1.1.6","2":"1.1.6","version_comment":"- Fixed a serious bug loading the entities.\r\n- Also load the tag mappings and menus via json.","3":"- Fixed a serious bug loading the entities.\r\n- Also load the tag mappings and menus via json.","package":"HTML.zip","4":"HTML.zip","src_id":"27706","5":"27706","creation_date":"1628775254","6":"1628775254"},{"0":"453","vim_version":"9.0","1":"9.0","script_version":"1.1.5","2":"1.1.5","version_comment":"- Remove unused code.\r\n- Make defining HTML entities with menus easier.\r\n- Add an about command.","3":"- Remove unused code.\r\n- Make defining HTML entities with menus easier.\r\n- Add an about command.","package":"HTML.zip","4":"HTML.zip","src_id":"27705","5":"27705","creation_date":"1628697385","6":"1628697385"},{"0":"453","vim_version":"9.0","1":"9.0","script_version":"1.1.4","2":"1.1.4","version_comment":"- Separate constants to another file\r\n- Rewrote the color selector code to use Vim's popups\r\n- Other small changes","3":"- Separate constants to another file\r\n- Rewrote the color selector code to use Vim's popups\r\n- Other small changes","package":"HTML.zip","4":"HTML.zip","src_id":"27702","5":"27702","creation_date":"1628602063","6":"1628602063"},{"0":"453","vim_version":"9.0","1":"9.0","script_version":"1.1.3","2":"1.1.3","version_comment":"- Allow switching between upper and lowercase tags.\r\n- Fix menu handling bug.","3":"- Allow switching between upper and lowercase tags.\r\n- Fix menu handling bug.","package":"HTML.zip","4":"HTML.zip","src_id":"27701","5":"27701","creation_date":"1628349667","6":"1628349667"},{"0":"453","vim_version":"9.0","1":"9.0","script_version":"1.1.2","2":"1.1.2","version_comment":"- Config option to allow the menu to be placed in another menu.\r\n- Add more documentation tags.\r\n","3":"- Config option to allow the menu to be placed in another menu.\r\n- Add more documentation tags.\r\n","package":"HTML.zip","4":"HTML.zip","src_id":"27696","5":"27696","creation_date":"1628231209","6":"1628231209"},{"0":"453","vim_version":"9.0","1":"9.0","script_version":"1.1.1","2":"1.1.1","version_comment":"- More smart tags\r\n- More bug fixes\r\n- Overhaul some more code","3":"- More smart tags\r\n- More bug fixes\r\n- Overhaul some more code","package":"HTML.zip","4":"HTML.zip","src_id":"27692","5":"27692","creation_date":"1628090530","6":"1628090530"},{"0":"453","vim_version":"9.0","1":"9.0","script_version":"1.1.0","2":"1.1.0","version_comment":"- Overhaul smart tag code, allowing many more tags to be \"smart\"\r\n- Optimizations\r\n- Documentation updates","3":"- Overhaul smart tag code, allowing many more tags to be \"smart\"\r\n- Optimizations\r\n- Documentation updates","package":"HTML.zip","4":"HTML.zip","src_id":"27688","5":"27688","creation_date":"1627821258","6":"1627821258"},{"0":"453","vim_version":"9.0","1":"9.0","script_version":"1.0.18","2":"1.0.18","version_comment":"- Bug fixes\r\n- Improve code for flexibility\r\n- ;mi mapping now works in more contexts","3":"- Bug fixes\r\n- Improve code for flexibility\r\n- ;mi mapping now works in more contexts","package":"HTML.zip","4":"HTML.zip","src_id":"27687","5":"27687","creation_date":"1627660673","6":"1627660673"},{"0":"453","vim_version":"9.0","1":"9.0","script_version":"1.0.17","2":"1.0.17","version_comment":"- Bug fixes and many code improvements","3":"- Bug fixes and many code improvements","package":"HTML.zip","4":"HTML.zip","src_id":"27677","5":"27677","creation_date":"1627468431","6":"1627468431"},{"0":"453","vim_version":"9.0","1":"9.0","script_version":"1.0.16","2":"1.0.16","version_comment":"- Better character entity conversion.\r\n- Bug fixes.","3":"- Better character entity conversion.\r\n- Bug fixes.","package":"HTML.zip","4":"HTML.zip","src_id":"27675","5":"27675","creation_date":"1627374529","6":"1627374529"},{"0":"453","vim_version":"9.0","1":"9.0","script_version":"1.0.14","2":"1.0.14","version_comment":"- Add \"links\" to available textmode browsers\r\n- Use system menu.vim ToolBar items where applicable\r\n- More refactoring and internal code improvements\r\n- Bug fixes","3":"- Add \"links\" to available textmode browsers\r\n- Use system menu.vim ToolBar items where applicable\r\n- More refactoring and internal code improvements\r\n- Bug fixes","package":"HTML.zip","4":"HTML.zip","src_id":"27674","5":"27674","creation_date":"1627110488","6":"1627110488"},{"0":"453","vim_version":"9.0","1":"9.0","script_version":"1.0.11","2":"1.0.11","version_comment":"- Allow lynx and w3m to be opened in a :terminal\r\n- Now available on github","3":"- Allow lynx and w3m to be opened in a :terminal\r\n- Now available on github","package":"HTML.zip","4":"HTML.zip","src_id":"27661","5":"27661","creation_date":"1626829151","6":"1626829151"},{"0":"453","vim_version":"9.0","1":"9.0","script_version":"1.0.8","2":"1.0.8","version_comment":"Some refactoring and logic changes, very little in the way of feature additions","3":"Some refactoring and logic changes, very little in the way of feature additions","package":"HTML.zip","4":"HTML.zip","src_id":"27657","5":"27657","creation_date":"1626579018","6":"1626579018"},{"0":"453","vim_version":"9.0","1":"9.0","script_version":"1.0.5","2":"1.0.5","version_comment":"- Support more tags, including Server-Side Includes\r\n- Many tweaks and bug fixes","3":"- Support more tags, including Server-Side Includes\r\n- Many tweaks and bug fixes","package":"HTML.zip","4":"HTML.zip","src_id":"27356","5":"27356","creation_date":"1604916370","6":"1604916370"},{"0":"453","vim_version":"9.0","1":"9.0","script_version":"1.0.0","2":"1.0.0","version_comment":"- Major refactor, now only supports Vim 9 (or a very recently patched version of Vim 8 if you have it)","3":"- Major refactor, now only supports Vim 9 (or a very recently patched version of Vim 8 if you have it)","package":"HTML.zip","4":"HTML.zip","src_id":"27345","5":"27345","creation_date":"1603355062","6":"1603355062"},{"0":"453","vim_version":"8.2","1":"8.2","script_version":"0.44.4","2":"0.44.4","version_comment":"- Bug fixes","3":"- Bug fixes","package":"HTML.zip","4":"HTML.zip","src_id":"27333","5":"27333","creation_date":"1602663589","6":"1602663589"},{"0":"453","vim_version":"8.2","1":"8.2","script_version":"0.44.3","2":"0.44.3","version_comment":"- Transition to Vim 8.2 and begin transition to the upcoming Vim 9.0","3":"- Transition to Vim 8.2 and begin transition to the upcoming Vim 9.0","package":"HTML.zip","4":"HTML.zip","src_id":"27328","5":"27328","creation_date":"1602382111","6":"1602382111"},{"0":"453","vim_version":"7.2","1":"7.2","script_version":"0.42.6","2":"0.42.6","version_comment":"- Add <button> (;bn) tag, which is used by some frameworks","3":"- Add <button> (;bn) tag, which is used by some frameworks","package":"HTML.zip","4":"HTML.zip","src_id":"27022","5":"27022","creation_date":"1582270251","6":"1582270251"},{"0":"453","vim_version":"7.2","1":"7.2","script_version":"0.42.5","2":"0.42.5","version_comment":"- A few more HTML 5 tag mappings\r\n- Housekeeping and bug fixes","3":"- A few more HTML 5 tag mappings\r\n- Housekeeping and bug fixes","package":"HTML.zip","4":"HTML.zip","src_id":"26953","5":"26953","creation_date":"1580730144","6":"1580730144"},{"0":"453","vim_version":"7.2","1":"7.2","script_version":"0.42.4","2":"0.42.4","version_comment":"- Added super- and sub-script character entities\r\n- Documented tags that are not HTML 5 compatible\r\n- Internal housekeeping","3":"- Added super- and sub-script character entities\r\n- Documented tags that are not HTML 5 compatible\r\n- Internal housekeeping","package":"HTML.zip","4":"HTML.zip","src_id":"26951","5":"26951","creation_date":"1580649247","6":"1580649247"},{"0":"453","vim_version":"7.2","1":"7.2","script_version":"0.42.2","2":"0.42.2","version_comment":"- More HTML 5 tag mappings\r\n- Various tweaks and fixes","3":"- More HTML 5 tag mappings\r\n- Various tweaks and fixes","package":"HTML.zip","4":"HTML.zip","src_id":"26949","5":"26949","creation_date":"1580477441","6":"1580477441"},{"0":"453","vim_version":"7.2","1":"7.2","script_version":"0.42.1","2":"0.42.1","version_comment":"- Default browser mapping for Unix wasn't working","3":"- Default browser mapping for Unix wasn't working","package":"HTML.zip","4":"HTML.zip","src_id":"26947","5":"26947","creation_date":"1580354795","6":"1580354795"},{"0":"453","vim_version":"7.2","1":"7.2","script_version":"0.42.0","2":"0.42.0","version_comment":"- Add support for specific browsers under Windows\r\n- Several tweaks and fixes","3":"- Add support for specific browsers under Windows\r\n- Several tweaks and fixes","package":"HTML.zip","4":"HTML.zip","src_id":"26942","5":"26942","creation_date":"1580210601","6":"1580210601"},{"0":"453","vim_version":"7.2","1":"7.2","script_version":"0.41.2","2":"0.41.2","version_comment":"- Drop support for obsolete browsers\r\n- More HTML 5 mappings","3":"- Drop support for obsolete browsers\r\n- More HTML 5 mappings","package":"HTML.zip","4":"HTML.zip","src_id":"26941","5":"26941","creation_date":"1580115560","6":"1580115560"},{"0":"453","vim_version":"7.2","1":"7.2","script_version":"0.41.1","2":"0.41.1","version_comment":"- Add a few HTML 5 mappings -- more on request\r\n- Make certain tags and the default template valid HTML for modern browsers (using CSS)","3":"- Add a few HTML 5 mappings -- more on request\r\n- Make certain tags and the default template valid HTML for modern browsers (using CSS)","package":"HTML.zip","4":"HTML.zip","src_id":"26939","5":"26939","creation_date":"1580022893","6":"1580022893"},{"0":"453","vim_version":"7.2","1":"7.2","script_version":"0.40.2","2":"0.40.2","version_comment":"- Add left\/right single and double quote character entities\r\n- Add mapping for HTML 5 doctype","3":"- Add left\/right single and double quote character entities\r\n- Add mapping for HTML 5 doctype","package":"HTML.zip","4":"HTML.zip","src_id":"26936","5":"26936","creation_date":"1580007282","6":"1580007282"},{"0":"453","vim_version":"7.2","1":"7.2","script_version":"0.40.1","2":"0.40.1","version_comment":"- More fraction entities added\r\n- globpath() → findfile() for compatibility with Vundle (Leif Arne Storset)","3":"- More fraction entities added\r\n- globpath() → findfile() for compatibility with Vundle (Leif Arne Storset)","package":"HTML.zip","4":"HTML.zip","src_id":"19034","5":"19034","creation_date":"1353914287","6":"1353914287"},{"0":"453","vim_version":"7.2","1":"7.2","script_version":"0.39.4","2":"0.39.4","version_comment":"- Added:\r\n  + <param> (;pm) mapping\r\n  + • (&*) mapping\r\n- Fixed:\r\n  + Slight problem with the <noscript> (;ns) mapping\r\n  + HTMLnextInsertPoint() (tab mapping) might not properly jump to the end of a closing comment dilimeter. (Samuel Ferencik)","3":"- Added:\r\n  + <param> (;pm) mapping\r\n  + • (&*) mapping\r\n- Fixed:\r\n  + Slight problem with the <noscript> (;ns) mapping\r\n  + HTMLnextInsertPoint() (tab mapping) might not properly jump to the end of a closing comment dilimeter. (Samuel Ferencik)","package":"HTML.zip","4":"HTML.zip","src_id":"16609","5":"16609","creation_date":"1317446102","6":"1317446102"},{"0":"453","vim_version":"7.2","1":"7.2","script_version":"0.39.1","2":"0.39.1","version_comment":"- Character entity conversion mappings can now encode to &#x..; hexadecimal strings, and decode them as well (Samuel Ferencik)\r\n- Roman numeral character entity mappings added (Samuel Ferencik)","3":"- Character entity conversion mappings can now encode to &#x..; hexadecimal strings, and decode them as well (Samuel Ferencik)\r\n- Roman numeral character entity mappings added (Samuel Ferencik)","package":"HTML.zip","4":"HTML.zip","src_id":"16196","5":"16196","creation_date":"1312489627","6":"1312489627"},{"0":"453","vim_version":"7.2","1":"7.2","script_version":"0.38.1","2":"0.38.1","version_comment":"- Euro entity mapping and menu (Samuel Ferencik)\r\n- HTMLnextInsertPoint() sometimes didn't restore options (Samuel Ferencik)\r\n- Entire scriptencoding has been changed to utf8 instead of partially latin1","3":"- Euro entity mapping and menu (Samuel Ferencik)\r\n- HTMLnextInsertPoint() sometimes didn't restore options (Samuel Ferencik)\r\n- Entire scriptencoding has been changed to utf8 instead of partially latin1","package":"HTML.zip","4":"HTML.zip","src_id":"15795","5":"15795","creation_date":"1307043055","6":"1307043055"},{"0":"453","vim_version":"7.2","1":"7.2","script_version":"0.37.1","2":"0.37.1","version_comment":"- Determining the Firefox remote command wasn't working properly (Fr. Robert Bower)\r\n- Fr. Robert Bower added support for Google Chrome on Unix\/Linux\r\n\r\n(This script _might_ run okay on Vim 7.0\/7.1, but it has not been tested -- 7.3 is preferred.)","3":"- Determining the Firefox remote command wasn't working properly (Fr. Robert Bower)\r\n- Fr. Robert Bower added support for Google Chrome on Unix\/Linux\r\n\r\n(This script _might_ run okay on Vim 7.0\/7.1, but it has not been tested -- 7.3 is preferred.)","package":"HTML.zip","4":"HTML.zip","src_id":"15498","5":"15498","creation_date":"1303423347","6":"1303423347"},{"0":"453","vim_version":"7.0","1":"7.0","script_version":"0.36.4","2":"0.36.4","version_comment":"- More character entity mappings\r\n- Minor changes","3":"- More character entity mappings\r\n- Minor changes","package":"HTML.zip","4":"HTML.zip","src_id":"13517","5":"13517","creation_date":"1281204482","6":"1281204482"},{"0":"453","vim_version":"7.0","1":"7.0","script_version":"0.36.3","2":"0.36.3","version_comment":"- Various minor fixes","3":"- Various minor fixes","package":"HTML.zip","4":"HTML.zip","src_id":"13274","5":"13274","creation_date":"1277971348","6":"1277971348"},{"0":"453","vim_version":"7.0","1":"7.0","script_version":"0.36.1","2":"0.36.1","version_comment":"- b:no_html_maps can be set like g:no_html_maps\r\n- Israel Chauca Fuentes provided MacOS browser control code\r\n- minor fixes and changes","3":"- b:no_html_maps can be set like g:no_html_maps\r\n- Israel Chauca Fuentes provided MacOS browser control code\r\n- minor fixes and changes","package":"HTML.zip","4":"HTML.zip","src_id":"11606","5":"11606","creation_date":"1256704537","6":"1256704537"},{"0":"453","vim_version":"7.0","1":"7.0","script_version":"0.35.1","2":"0.35.1","version_comment":"- Try to safely escape shell commands","3":"- Try to safely escape shell commands","package":"HTML.zip","4":"HTML.zip","src_id":"8808","5":"8808","creation_date":"1213568695","6":"1213568695"},{"0":"453","vim_version":"7.0","1":"7.0","script_version":"0.35","2":"0.35","version_comment":"- Added:\r\n  + The colors in the color menu can be displayed in a split window under the GUI, and colors can be selected from the display (;# mapping and :ColorSelect command)\r\n  + g:no_html_map_override can be set to prevent the plugin from overriding already existing mappings, and now warning messages are printed when overriding takes place\r\n  + g:no_html_maps can be set to a regular expression to tell the plugin not to define matching mappings\r\n  + g:html_map_entity_leader can be used to define the character entity mapping leader--works like g:html_map_leader\r\n  + MangleImageTag.vim (used by the ;mi mapping) no longer moves the cursor\r\n  + Miscellaneous minor additions\r\n- Miscellaneous fixes \r\n- Significant refactoring to make maintaining the plugin easier","3":"- Added:\r\n  + The colors in the color menu can be displayed in a split window under the GUI, and colors can be selected from the display (;# mapping and :ColorSelect command)\r\n  + g:no_html_map_override can be set to prevent the plugin from overriding already existing mappings, and now warning messages are printed when overriding takes place\r\n  + g:no_html_maps can be set to a regular expression to tell the plugin not to define matching mappings\r\n  + g:html_map_entity_leader can be used to define the character entity mapping leader--works like g:html_map_leader\r\n  + MangleImageTag.vim (used by the ;mi mapping) no longer moves the cursor\r\n  + Miscellaneous minor additions\r\n- Miscellaneous fixes \r\n- Significant refactoring to make maintaining the plugin easier","package":"HTML.zip","4":"HTML.zip","src_id":"8783","5":"8783","creation_date":"1213124677","6":"1213124677"},{"0":"453","vim_version":"7.0","1":"7.0","script_version":"0.34","2":"0.34","version_comment":"- Removed code that was supporting Vim 6, thus:\r\n  + MangleImageTag() used by ;mi mapping should now always compute correct size\r\n  + Various code was simplified","3":"- Removed code that was supporting Vim 6, thus:\r\n  + MangleImageTag() used by ;mi mapping should now always compute correct size\r\n  + Various code was simplified","package":"HTML.zip","4":"HTML.zip","src_id":"8654","5":"8654","creation_date":"1210140767","6":"1210140767"},{"0":"453","vim_version":"6.0","1":"6.0","script_version":"0.33.1","2":"0.33.1","version_comment":"- Character entities for arrows and the Greek alphabet added\r\n- This is the last version that will support Vim 6","3":"- Character entities for arrows and the Greek alphabet added\r\n- This is the last version that will support Vim 6","package":"HTML.zip","4":"HTML.zip","src_id":"8620","5":"8620","creation_date":"1209480341","6":"1209480341"},{"0":"453","vim_version":"6.0","1":"6.0","script_version":"0.32.2","2":"0.32.2","version_comment":"- Fixed:\r\n  + Some of the \"boolean\" configuration variables weren't being tested right (Keith Lancaster)\r\n  + Could get an error when (re-)initializing the menus\r\n- Changed:\r\n  + The ;& and ;% normal mode mappings now behave as operator (motion) mappings--use ;&l or ;%l to emulate the old behavior\r\n- Added:\r\n  + :HTMLmappings reload\/html\/xhtml can force reloading of the entire script, or switch the mappings into html\/xhtml mode\r\n- misc. minor fixes","3":"- Fixed:\r\n  + Some of the \"boolean\" configuration variables weren't being tested right (Keith Lancaster)\r\n  + Could get an error when (re-)initializing the menus\r\n- Changed:\r\n  + The ;& and ;% normal mode mappings now behave as operator (motion) mappings--use ;&l or ;%l to emulate the old behavior\r\n- Added:\r\n  + :HTMLmappings reload\/html\/xhtml can force reloading of the entire script, or switch the mappings into html\/xhtml mode\r\n- misc. minor fixes","package":"HTML.zip","4":"HTML.zip","src_id":"8556","5":"8556","creation_date":"1208110410","6":"1208110410"},{"0":"453","vim_version":"6.0","1":"6.0","script_version":"0.30","2":"0.30","version_comment":"- Fixed:\r\n  + Exclude leading indent from the start tag for visual mappings when in visual-line mode\r\n- Added:\r\n  + ;tH (<THEAD>), ;tf (<TFOOT>), and ;tb (<TBODY>) mappings added","3":"- Fixed:\r\n  + Exclude leading indent from the start tag for visual mappings when in visual-line mode\r\n- Added:\r\n  + ;tH (<THEAD>), ;tf (<TFOOT>), and ;tb (<TBODY>) mappings added","package":"HTML.zip","4":"HTML.zip","src_id":"8422","5":"8422","creation_date":"1204932414","6":"1204932414"},{"0":"453","vim_version":"6.0","1":"6.0","script_version":"0.29.2","2":"0.29.2","version_comment":"- Fixed:\r\n  + Tab mapping wasn't positioning the cursor right when there were multiple spaces between a opening and closing tag\r\n- Added:\r\n  + Make the <html> tag include an xmlns attribute for XHTML","3":"- Fixed:\r\n  + Tab mapping wasn't positioning the cursor right when there were multiple spaces between a opening and closing tag\r\n- Added:\r\n  + Make the <html> tag include an xmlns attribute for XHTML","package":"HTML.zip","4":"HTML.zip","src_id":"7639","5":"7639","creation_date":"1189387535","6":"1189387535"},{"0":"453","vim_version":"6.0","1":"6.0","script_version":"0.29","2":"0.29","version_comment":"- Added:\r\n  + g:html_tag_case_autodetect configuration variable\r\n- Fixed:\r\n  + The HTMLnextInsertPoint() function was causing a press enter prompt\r\n  + 'formatoptions' could make visual mappings behave wrong\r\n- Other minor additions and fixes","3":"- Added:\r\n  + g:html_tag_case_autodetect configuration variable\r\n- Fixed:\r\n  + The HTMLnextInsertPoint() function was causing a press enter prompt\r\n  + 'formatoptions' could make visual mappings behave wrong\r\n- Other minor additions and fixes","package":"HTML.zip","4":"HTML.zip","src_id":"7441","5":"7441","creation_date":"1186087554","6":"1186087554"},{"0":"453","vim_version":"6.0","1":"6.0","script_version":"0.28.2","2":"0.28.2","version_comment":"- Fixed:\r\n  + Defining the menus failed entirely if g:no_html_toolbar was set\r\n- Changes:\r\n  + Add \"Select Tag\" and \"Select Inner Tag\" to the PopUp menu\r\n  + Minor tweaks","3":"- Fixed:\r\n  + Defining the menus failed entirely if g:no_html_toolbar was set\r\n- Changes:\r\n  + Add \"Select Tag\" and \"Select Inner Tag\" to the PopUp menu\r\n  + Minor tweaks","package":"HTML.zip","4":"HTML.zip","src_id":"7310","5":"7310","creation_date":"1183133674","6":"1183133674"},{"0":"453","vim_version":"6.0","1":"6.0","script_version":"0.28","2":"0.28","version_comment":"- Fixed:\r\n  + Visual mode mappings weren't operating properly when 'selection' was set to \"exclusive\"\r\n- Added:\r\n  + ;db -- default browser mapping for Windows","3":"- Fixed:\r\n  + Visual mode mappings weren't operating properly when 'selection' was set to \"exclusive\"\r\n- Added:\r\n  + ;db -- default browser mapping for Windows","package":"HTML.zip","4":"HTML.zip","src_id":"7297","5":"7297","creation_date":"1182662667","6":"1182662667"},{"0":"453","vim_version":"6.0","1":"6.0","script_version":"0.27.6","2":"0.27.6","version_comment":"- Fixed:\r\n  + Menus weren't getting disabled\/enabled properly\r\n- Changed:\r\n  + <DT> and <DD> tags now have closing tags and visual mappings\r\n  + ;;-style mapping for whatever g:html_map_leader is set to\r\n  + Internal code changes","3":"- Fixed:\r\n  + Menus weren't getting disabled\/enabled properly\r\n- Changed:\r\n  + <DT> and <DD> tags now have closing tags and visual mappings\r\n  + ;;-style mapping for whatever g:html_map_leader is set to\r\n  + Internal code changes","package":"HTML.zip","4":"HTML.zip","src_id":"7233","5":"7233","creation_date":"1181676519","6":"1181676519"},{"0":"453","vim_version":"6.0","1":"6.0","script_version":"0.27.4","2":"0.27.4","version_comment":"- Added:\r\n  + Smart handling of <EM><\/EM> tags\r\n  + ;% mapping added -- like ;& but convert to %XX hex strings for URIs\r\n- Changed:\r\n  + Moved ;ns \/ ;nns mappings to ;ne \/ ;nne, and moved ;nj mappings to ;ns","3":"- Added:\r\n  + Smart handling of <EM><\/EM> tags\r\n  + ;% mapping added -- like ;& but convert to %XX hex strings for URIs\r\n- Changed:\r\n  + Moved ;ns \/ ;nns mappings to ;ne \/ ;nne, and moved ;nj mappings to ;ns","package":"HTML.zip","4":"HTML.zip","src_id":"7211","5":"7211","creation_date":"1181114477","6":"1181114477"},{"0":"453","vim_version":"6.0","1":"6.0","script_version":"0.27.1","2":"0.27.1","version_comment":"- Added:\r\n  + g:force_html_menu can be set to force the HTML menus to be defined in the console\r\n  + g:no_html_menu can be set to stop the menu and toolbar items from being defined\r\n  + w3m browser preview under *nix\r\n- Minor changes and fixes","3":"- Added:\r\n  + g:force_html_menu can be set to force the HTML menus to be defined in the console\r\n  + g:no_html_menu can be set to stop the menu and toolbar items from being defined\r\n  + w3m browser preview under *nix\r\n- Minor changes and fixes","package":"HTML.zip","4":"HTML.zip","src_id":"7184","5":"7184","creation_date":"1180647500","6":"1180647500"},{"0":"453","vim_version":"6.0","1":"6.0","script_version":"0.26.8","2":"0.26.8","version_comment":"- Fixed:\r\n  + MangleImageTag() used by ;mi mapping was missing some quotes and computing the wrong sizes when 'encoding' was UTF8 or similar\r\n  + Tab on the end of a line in insert mode moved the cursor a character left\r\n  + Temporarily clear the 'comments' option for the ;js mapping so extraneous \/\/ comments weren't inserted\r\n- Various minor changes","3":"- Fixed:\r\n  + MangleImageTag() used by ;mi mapping was missing some quotes and computing the wrong sizes when 'encoding' was UTF8 or similar\r\n  + Tab on the end of a line in insert mode moved the cursor a character left\r\n  + Temporarily clear the 'comments' option for the ;js mapping so extraneous \/\/ comments weren't inserted\r\n- Various minor changes","package":"HTML.zip","4":"HTML.zip","src_id":"7143","5":"7143","creation_date":"1179484468","6":"1179484468"},{"0":"453","vim_version":"6.0","1":"6.0","script_version":"0.26.5","2":"0.26.5","version_comment":"- Fixed:\r\n  + When 'filetype' was set in a modeline \":HTMLmappings disable\" didn't work\r\n  + Mappings defined with HTMLmap()\/HTMLmapo() outside the script weren't redefined when :HTMLmappings disable then enable was run\r\n- Added:\r\n  + ;aH, ;aT, ;aN, etc. now work in insert mode -- they get data from the clipboard\r\n  + ;nj mapping for <NOSCRIPT><CR><\/NOSCRIPT> added\r\n  + visual and normal mode mappings for ;ob\r\n- Various minor changes and fixes","3":"- Fixed:\r\n  + When 'filetype' was set in a modeline \":HTMLmappings disable\" didn't work\r\n  + Mappings defined with HTMLmap()\/HTMLmapo() outside the script weren't redefined when :HTMLmappings disable then enable was run\r\n- Added:\r\n  + ;aH, ;aT, ;aN, etc. now work in insert mode -- they get data from the clipboard\r\n  + ;nj mapping for <NOSCRIPT><CR><\/NOSCRIPT> added\r\n  + visual and normal mode mappings for ;ob\r\n- Various minor changes and fixes","package":"HTML.zip","4":"HTML.zip","src_id":"7019","5":"7019","creation_date":"1177316876","6":"1177316876"},{"0":"453","vim_version":"6.0","1":"6.0","script_version":"0.26","2":"0.26","version_comment":"- Added:\r\n  + \":HTMLmappings disable\/enable\" command\r\n  + %vimversion% template token\r\n- Fixed:\r\n  + Some recently added mappings weren't in the menu\r\n  + Inserting the HTML template could trigger the \"Press ENTER\" prompt","3":"- Added:\r\n  + \":HTMLmappings disable\/enable\" command\r\n  + %vimversion% template token\r\n- Fixed:\r\n  + Some recently added mappings weren't in the menu\r\n  + Inserting the HTML template could trigger the \"Press ENTER\" prompt","package":"HTML.zip","4":"HTML.zip","src_id":"6967","5":"6967","creation_date":"1176211370","6":"1176211370"},{"0":"453","vim_version":"6.0","1":"6.0","script_version":"0.25.5","2":"0.25.5","version_comment":"- New mappings:\r\n  + ;sj mapping -- like ;js but for sourced JavaScript\r\n  + ;^ mapping to decode &#...; encoded strings\r\n  + ;& in insert mode inserts a literal &\r\n- Minor changes","3":"- New mappings:\r\n  + ;sj mapping -- like ;js but for sourced JavaScript\r\n  + ;^ mapping to decode &#...; encoded strings\r\n  + ;& in insert mode inserts a literal &\r\n- Minor changes","package":"HTML.zip","4":"HTML.zip","src_id":"6926","5":"6926","creation_date":"1175296036","6":"1175296036"},{"0":"453","vim_version":"6.0","1":"6.0","script_version":"0.25.1","2":"0.25.1","version_comment":"- Allow b:html_template to be set in addition to g:html_template\r\n- HTMLnextInsertPoint() used by the <tab> mapping now handles comments, and no longer requires an argument\r\n- ;s4 mapping added -- Same as ;4 only strict rather than transitional\r\n- %time%, %time12%, and %time24% template tokens added, and %date% token is now customizable\r\n- b:do_xhtml_mappings was being ignored","3":"- Allow b:html_template to be set in addition to g:html_template\r\n- HTMLnextInsertPoint() used by the <tab> mapping now handles comments, and no longer requires an argument\r\n- ;s4 mapping added -- Same as ;4 only strict rather than transitional\r\n- %time%, %time12%, and %time24% template tokens added, and %date% token is now customizable\r\n- b:do_xhtml_mappings was being ignored","package":"HTML.zip","4":"HTML.zip","src_id":"6857","5":"6857","creation_date":"1173643933","6":"1173643933"},{"0":"453","vim_version":"6.0","1":"6.0","script_version":"0.24","2":"0.24","version_comment":"- In rare cases the script tried to re-enable the ToolBar buttons when they didn't exist\r\n- g:no_html_tab_mapping can be defined to 'move' the <tab> mappings to ;<tab>\r\n- misc. fixes and additions","3":"- In rare cases the script tried to re-enable the ToolBar buttons when they didn't exist\r\n- g:no_html_tab_mapping can be defined to 'move' the <tab> mappings to ;<tab>\r\n- misc. fixes and additions","package":"HTML.zip","4":"HTML.zip","src_id":"6766","5":"6766","creation_date":"1172143783","6":"1172143783"},{"0":"453","vim_version":"6.0","1":"6.0","script_version":"0.23.2","2":"0.23.2","version_comment":"- Bug when testing for g:html_charset\r\n- Fix a couple of the forms mappings\r\n- Documentation updates and fixes","3":"- Bug when testing for g:html_charset\r\n- Fix a couple of the forms mappings\r\n- Documentation updates and fixes","package":"HTML.zip","4":"HTML.zip","src_id":"6510","5":"6510","creation_date":"1165957179","6":"1165957179"},{"0":"453","vim_version":"6.0","1":"6.0","script_version":"0.23.1","2":"0.23.1","version_comment":"- Dynamic charset support for the template and the ;ct mapping, based on the 'fileencoding', and 'encoding' options (but the conversion table is limited, see \":help html-author-notes\")\r\n- <option> tag wasn't properly closed","3":"- Dynamic charset support for the template and the ;ct mapping, based on the 'fileencoding', and 'encoding' options (but the conversion table is limited, see \":help html-author-notes\")\r\n- <option> tag wasn't properly closed","package":"HTML.zip","4":"HTML.zip","src_id":"6506","5":"6506","creation_date":"1165869218","6":"1165869218"},{"0":"453","vim_version":"6.0","1":"6.0","script_version":"0.22.2","2":"0.22.2","version_comment":"- browser_launcher.vim: Bug in detecting the remote command\r\n- ;me mapping wasn't properly positioning the cursor\r\n- Minor documentation fixes","3":"- browser_launcher.vim: Bug in detecting the remote command\r\n- ;me mapping wasn't properly positioning the cursor\r\n- Minor documentation fixes","package":"HTML.zip","4":"HTML.zip","src_id":"6497","5":"6497","creation_date":"1165256956","6":"1165256956"},{"0":"453","vim_version":"6.0","1":"6.0","script_version":"0.22.1","2":"0.22.1","version_comment":"- Make the leader of the ;-mappings configurable with g:html_map_leader\r\n- Fix error when g:no_html_toolbar is set","3":"- Make the leader of the ;-mappings configurable with g:html_map_leader\r\n- Fix error when g:no_html_toolbar is set","package":"HTML.zip","4":"HTML.zip","src_id":"6414","5":"6414","creation_date":"1163512925","6":"1163512925"},{"0":"453","vim_version":"6.0","1":"6.0","script_version":"0.21.2","2":"0.21.2","version_comment":"- ;im mapping wasn't properly positioning the cursor\r\n- Minor improvement to the HTMLnextInsertPoint function used by the tab mapping","3":"- ;im mapping wasn't properly positioning the cursor\r\n- Minor improvement to the HTMLnextInsertPoint function used by the tab mapping","package":"HTML.zip","4":"HTML.zip","src_id":"6279","5":"6279","creation_date":"1160763882","6":"1160763882"},{"0":"453","vim_version":"6.0","1":"6.0","script_version":"0.21","2":"0.21","version_comment":"- Basic support for XHTML added--see \":help g:do_xhtml_mappings\"\r\n- Misc. minor fixes","3":"- Basic support for XHTML added--see \":help g:do_xhtml_mappings\"\r\n- Misc. minor fixes","package":"HTML.zip","4":"HTML.zip","src_id":"6253","5":"6253","creation_date":"1159999751","6":"1159999751"},{"0":"453","vim_version":"6.0","1":"6.0","script_version":"0.20.4","2":"0.20.4","version_comment":"- ;h1 - ;h6 and mappings no longer create center aligned tags, ;hr no longer has a default width. Use ;H1 - ;H6 \/ ;Hr if you still want the old default behavior.\r\n- Don't display menu\/toolbar entries for browsers that don't exist. (Unix only)\r\n- Allow .-repeating of operator mappings to work properly.\r\n- Code improvements and bug fixes.","3":"- ;h1 - ;h6 and mappings no longer create center aligned tags, ;hr no longer has a default width. Use ;H1 - ;H6 \/ ;Hr if you still want the old default behavior.\r\n- Don't display menu\/toolbar entries for browsers that don't exist. (Unix only)\r\n- Allow .-repeating of operator mappings to work properly.\r\n- Code improvements and bug fixes.","package":"HTML.zip","4":"HTML.zip","src_id":"5785","5":"5785","creation_date":"1148830312","6":"1148830312"},{"0":"453","vim_version":"6.0","1":"6.0","script_version":"0.19","2":"0.19","version_comment":"- Smart-handling of certain tags (bold, italic, underline, comments) if syntax highlighting is on.","3":"- Smart-handling of certain tags (bold, italic, underline, comments) if syntax highlighting is on.","package":"HTML.zip","4":"HTML.zip","src_id":"4991","5":"4991","creation_date":"1137576583","6":"1137576583"},{"0":"453","vim_version":"6.0","1":"6.0","script_version":"0.18","2":"0.18","version_comment":"- Implemented normal mode mappings that take an operator (motion) for Vim 7.","3":"- Implemented normal mode mappings that take an operator (motion) for Vim 7.","package":"HTML.zip","4":"HTML.zip","src_id":"4921","5":"4921","creation_date":"1135565946","6":"1135565946"},{"0":"453","vim_version":"6.0","1":"6.0","script_version":"0.17.1","2":"0.17.1","version_comment":"- Some visual mappings had insert offset problems when 'indentexpr' was set.\r\n- Author email in templates wasn't being encoded (bug since the template became configurable).","3":"- Some visual mappings had insert offset problems when 'indentexpr' was set.\r\n- Author email in templates wasn't being encoded (bug since the template became configurable).","package":"HTML.zip","4":"HTML.zip","src_id":"4694","5":"4694","creation_date":"1129967663","6":"1129967663"},{"0":"453","vim_version":"6.0","1":"6.0","script_version":"0.16.2","2":"0.16.2","version_comment":"Some visual mappings didn't work with the extra code used to prevent a (visual)bell.","3":"Some visual mappings didn't work with the extra code used to prevent a (visual)bell.","package":"HTML.zip","4":"HTML.zip","src_id":"4657","5":"4657","creation_date":"1128767212","6":"1128767212"},{"0":"453","vim_version":"6.0","1":"6.0","script_version":"0.16","2":"0.16","version_comment":"- Fixed some of the forms visual mappings.\r\n- Added code to prevent a (visual)bell with some of the visual mappings when 'showmatch' was enabled.","3":"- Fixed some of the forms visual mappings.\r\n- Added code to prevent a (visual)bell with some of the visual mappings when 'showmatch' was enabled.","package":"HTML.zip","4":"HTML.zip","src_id":"4427","5":"4427","creation_date":"1121235073","6":"1121235073"},{"0":"453","vim_version":"6.0","1":"6.0","script_version":"0.15.1","2":"0.15.1","version_comment":"- MangleImageTag was getting the width and height of gifs reversed.\r\n- Other minor bugs fixed.","3":"- MangleImageTag was getting the width and height of gifs reversed.\r\n- Other minor bugs fixed.","package":"HTML.zip","4":"HTML.zip","src_id":"4299","5":"4299","creation_date":"1116502614","6":"1116502614"},{"0":"453","vim_version":"6.0","1":"6.0","script_version":"0.15","2":"0.15","version_comment":"- A bug crept in that prevented the work-around for the GTK2 toolbar pixmap bug from working.","3":"- A bug crept in that prevented the work-around for the GTK2 toolbar pixmap bug from working.","package":"HTML.zip","4":"HTML.zip","src_id":"3109","5":"3109","creation_date":"1086821955","6":"1086821955"},{"0":"453","vim_version":"6.0","1":"6.0","script_version":"0.14","2":"0.14","version_comment":"- ;& mapping to change the visual selection or character under the cursor to its &#...; equivalent.\r\n- ;mi mapping to automatically update the WIDTH\/HEIGHT attributes in an IMG tag. (MangleImageTag.vim included. -- Experimental! See \":help ;mi\".)\r\n- Misc. bug fixes and tweaks.","3":"- ;& mapping to change the visual selection or character under the cursor to its &#...; equivalent.\r\n- ;mi mapping to automatically update the WIDTH\/HEIGHT attributes in an IMG tag. (MangleImageTag.vim included. -- Experimental! See \":help ;mi\".)\r\n- Misc. bug fixes and tweaks.","package":"HTML.zip","4":"HTML.zip","src_id":"2965","5":"2965","creation_date":"1082597541","6":"1082597541"},{"0":"453","vim_version":"6.0","1":"6.0","script_version":"0.13","2":"0.13","version_comment":"- The template used by ;html is now configurable.\r\n- Colors menu changed from a cascading menu to an alphabetic menu.\r\n- Misc. tweaks.","3":"- The template used by ;html is now configurable.\r\n- Colors menu changed from a cascading menu to an alphabetic menu.\r\n- Misc. tweaks.","package":"HTML.zip","4":"HTML.zip","src_id":"2838","5":"2838","creation_date":"1079463449","6":"1079463449"},{"0":"453","vim_version":"6.0","1":"6.0","script_version":"0.12","2":"0.12","version_comment":"- Insert mode mappings weren't buffer-local. (Error when removing Vim5 support.)","3":"- Insert mode mappings weren't buffer-local. (Error when removing Vim5 support.)","package":"HTML.zip","4":"HTML.zip","src_id":"2459","5":"2459","creation_date":"1067989730","6":"1067989730"},{"0":"453","vim_version":"6.0","1":"6.0","script_version":"0.11","2":"0.11","version_comment":"- HTML menu and ToolBar weren't being enabled sometimes when the script was loaded again.\r\n- Abandoned support for vim versions prior to 6.\r\n- More minor changes.","3":"- HTML menu and ToolBar weren't being enabled sometimes when the script was loaded again.\r\n- Abandoned support for vim versions prior to 6.\r\n- More minor changes.","package":"HTML.zip","4":"HTML.zip","src_id":"2426","5":"2426","creation_date":"1067263515","6":"1067263515"},{"0":"453","vim_version":"5.7","1":"5.7","script_version":"0.10","2":"0.10","version_comment":"- Mozilla mappings added.\r\n- HTML encode author email (to prevent spam harvesters).\r\n- Work-around for a bug in the Vim GTK2 toolbar interface that doesn't properly find icons.\r\n- Other minor changes.","3":"- Mozilla mappings added.\r\n- HTML encode author email (to prevent spam harvesters).\r\n- Work-around for a bug in the Vim GTK2 toolbar interface that doesn't properly find icons.\r\n- Other minor changes.","package":"HTML.zip","4":"HTML.zip","src_id":"2333","5":"2333","creation_date":"1063488175","6":"1063488175"}]},"452":{"script_id":"452","0":"452","script_name":"draw.vim","1":"draw.vim","script_type":"utility","2":"utility","summary":"Draw rectangles and lines using blockwise Visual selection.","3":"Draw rectangles and lines using blockwise Visual selection.","description":"This plugin allows you to draw rectangles and lines using blockwise Visual mode, which makes it ideal for drawing tables and such. Simply move the cursor to the start position, hit CTRL-V to enter blockwise Visual mode and move the cursor to define the rectangle or line. Finally, type <leader>d to draw the rectangle or line. If you don't know what <leader> is, \\d should do the trick. This script supports UTF-8 as well as PC-8 boxdrawing characters, and checks the value of 'encoding' to determine which it should use. If you use a single byte character set other than ECS\/PC-8 which includes boxdrawing characters, please notify me so I can add support for it.\r\n\r\nNote: I strongly recommend \":set virtualedit+=block\" when using this script, so you can define rectangles beyond the end of the line.","4":"This plugin allows you to draw rectangles and lines using blockwise Visual mode, which makes it ideal for drawing tables and such. Simply move the cursor to the start position, hit CTRL-V to enter blockwise Visual mode and move the cursor to define the rectangle or line. Finally, type <leader>d to draw the rectangle or line. If you don't know what <leader> is, \\d should do the trick. This script supports UTF-8 as well as PC-8 boxdrawing characters, and checks the value of 'encoding' to determine which it should use. If you use a single byte character set other than ECS\/PC-8 which includes boxdrawing characters, please notify me so I can add support for it.\r\n\r\nNote: I strongly recommend \":set virtualedit+=block\" when using this script, so you can define rectangles beyond the end of the line.","install_details":"Just put it in your plugin directory, or :source it when you want to use it.\r\n\r\nTested under Windows 2000 with UTF-8 and PC-8 in GVim, and PC-8 in console mode Vim, both version 6.1 without patches.","5":"Just put it in your plugin directory, or :source it when you want to use it.\r\n\r\nTested under Windows 2000 with UTF-8 and PC-8 in GVim, and PC-8 in console mode Vim, both version 6.1 without patches.","first_name":"Timo","6":"Timo","last_name":"Frenay","7":"Frenay","releases":[{"0":"452","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"draw.vim","4":"draw.vim","src_id":"1322","5":"1322","creation_date":"1035050089","6":"1035050089"}]},"451":{"script_id":"451","0":"451","script_name":"EasyAccents","1":"EasyAccents","script_type":"utility","2":"utility","summary":"Easy accents while you type: a' a` c, etc.","3":"Easy accents while you type: a' a` c, etc.","description":"EasyAccents makes entering accented characters easy in insert mode.  Of course there are many European keyboards that have accented characters on keys, but US-style keyboards don't.  During insert mode,  a' becomes an accented a, etc.  It works with utf8 encoding.\r\n\r\nEasyAccents may be toggled on and off with:\r\n  :EZA\r\n\r\nYou can get just the two characters o', for example, by simply escaping the ':  o\\' -> o'\r\n\r\nHistory\/Features:\r\n\r\nv5: included g:EasyAccents_VowelFirst option\r\n    fixed insert vs append bug\r\n\r\nv4: EasyAccents handles a' a` A' o: etc : during insert mode, these pairs of\r\ncharacters become the associated accented characters.  Use <Leader>ea (\\ea) to\r\ntoggle EasyAccents on and off.  Especially helpful for US style keyboards.\r\n\r\n(alpha\/beta version available at http:\/\/www.drchip.org\/astronaut\/vim\/index.html#EASYACCENTS)\r\n","4":"EasyAccents makes entering accented characters easy in insert mode.  Of course there are many European keyboards that have accented characters on keys, but US-style keyboards don't.  During insert mode,  a' becomes an accented a, etc.  It works with utf8 encoding.\r\n\r\nEasyAccents may be toggled on and off with:\r\n  :EZA\r\n\r\nYou can get just the two characters o', for example, by simply escaping the ':  o\\' -> o'\r\n\r\nHistory\/Features:\r\n\r\nv5: included g:EasyAccents_VowelFirst option\r\n    fixed insert vs append bug\r\n\r\nv4: EasyAccents handles a' a` A' o: etc : during insert mode, these pairs of\r\ncharacters become the associated accented characters.  Use <Leader>ea (\\ea) to\r\ntoggle EasyAccents on and off.  Especially helpful for US style keyboards.\r\n\r\n(alpha\/beta version available at http:\/\/www.drchip.org\/astronaut\/vim\/index.html#EASYACCENTS)\r\n","install_details":"1. vim EasyAccents.vba.gz\r\n2. :so %\r\n\r\n ","5":"1. vim EasyAccents.vba.gz\r\n2. :so %\r\n\r\n ","first_name":"Charles","6":"Charles","last_name":"Campbell","7":"Campbell","releases":[{"0":"451","vim_version":"7.0","1":"7.0","script_version":"9","2":"9","version_comment":"Improved help and more easy-accents!  o' o` o~ etc.  Start it with :EZA, stop it with :EZA .\r\n","3":"Improved help and more easy-accents!  o' o` o~ etc.  Start it with :EZA, stop it with :EZA .\r\n","package":"EasyAccents.vba.gz","4":"EasyAccents.vba.gz","src_id":"9231","5":"9231","creation_date":"1220867868","6":"1220867868"},{"0":"451","vim_version":"6.0","1":"6.0","script_version":"6","2":"6","version_comment":"Normally EasyAccents supports 'a `a ~a :a etc to produce accented characters.\r\nNow, putting g:EasyAccents_VowelFirst=0 makes EasyAccents handle a' a` a~ a: .\r\nV6 supports even more accents: a@ A@ D@ e@ E@ N~ p@ u@ x@\r\n","3":"Normally EasyAccents supports 'a `a ~a :a etc to produce accented characters.\r\nNow, putting g:EasyAccents_VowelFirst=0 makes EasyAccents handle a' a` a~ a: .\r\nV6 supports even more accents: a@ A@ D@ e@ E@ N~ p@ u@ x@\r\n","package":"EasyAccents.vim.gz","4":"EasyAccents.vim.gz","src_id":"2905","5":"2905","creation_date":"1080899699","6":"1080899699"}]},"450":{"script_id":"450","0":"450","script_name":"xhtml.vim","1":"xhtml.vim","script_type":"ftplugin","2":"ftplugin","summary":"keyboard shortcuts and GUI menu for xhtml tags","3":"keyboard shortcuts and GUI menu for xhtml tags","description":"This script creates shortcuts for most xhtml tags, and in gvim it adds a menu for the various tags.  Shortcuts are triggered by the semicolon.  For example ;li will create open and close \"list item\" tags and leave the cursor between them.  Similarly ;im creates an image tag and leaves the cursor in the first field.\r\n\r\nCtrl-J is bound to a kind of \"jump\" and will generally place the cursor at the next place you would want to type (the next field or the place just before the next tag starts).\r\n\r\nThere are bindings for the 3 modes; command mode, insert mode, and visual mode; as well as some special characters like ;cp (copyright symbol) and ;< (less than symbol).","4":"This script creates shortcuts for most xhtml tags, and in gvim it adds a menu for the various tags.  Shortcuts are triggered by the semicolon.  For example ;li will create open and close \"list item\" tags and leave the cursor between them.  Similarly ;im creates an image tag and leaves the cursor in the first field.\r\n\r\nCtrl-J is bound to a kind of \"jump\" and will generally place the cursor at the next place you would want to type (the next field or the place just before the next tag starts).\r\n\r\nThere are bindings for the 3 modes; command mode, insert mode, and visual mode; as well as some special characters like ;cp (copyright symbol) and ;< (less than symbol).","install_details":"","5":"","first_name":"Donald","6":"Donald","last_name":"Bindner","7":"Bindner","releases":[{"0":"450","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"xhtml.vim","4":"xhtml.vim","src_id":"1308","5":"1308","creation_date":"1034709513","6":"1034709513"}]},"449":{"script_id":"449","0":"449","script_name":"gmt.vim","1":"gmt.vim","script_type":"syntax","2":"syntax","summary":"GMT (Generic Mapping Tools)","3":"GMT (Generic Mapping Tools)","description":"gmt.vim provides basic support for Generic Mapping Tools (GMT) shell scripts. As those scripts have no standard name y propose '.gmt' as a way to identify them. Indeed it is the only way to detect them.\t\t ","4":"gmt.vim provides basic support for Generic Mapping Tools (GMT) shell scripts. As those scripts have no standard name y propose '.gmt' as a way to identify them. Indeed it is the only way to detect them.\t\t ","install_details":"Put the script in $VIMRUNTIME\/syntax. Remember to call it '.gmt' and to modify the filetype.vim file.","5":"Put the script in $VIMRUNTIME\/syntax. Remember to call it '.gmt' and to modify the filetype.vim file.","first_name":"Patricio","6":"Patricio","last_name":"Toledo","7":"Toledo","releases":[{"0":"449","vim_version":"6.0","1":"6.0","script_version":"0.4","2":"0.4","version_comment":"no comments, enjoy","3":"no comments, enjoy","package":"gmt.vim","4":"gmt.vim","src_id":"1976","5":"1976","creation_date":"1052416098","6":"1052416098"},{"0":"449","vim_version":"6.0","1":"6.0","script_version":"0.3","2":"0.3","version_comment":"Initial upload","3":"Initial upload","package":"gmt.vim","4":"gmt.vim","src_id":"1305","5":"1305","creation_date":"1034704303","6":"1034704303"}]},"448":{"script_id":"448","0":"448","script_name":"java_checkstyle.vim","1":"java_checkstyle.vim","script_type":"ftplugin","2":"ftplugin","summary":"Integrates Checkstyle with Vim","3":"Integrates Checkstyle with Vim","description":"The java_checkstyle.vim filetype plugin script integrates Checkstyle\r\nhttp:\/\/checkstyle.sourceforge.net\/ with Vim.  \"Checkstyle is a\r\ndevelopment tool to help programmers write Java code that adheres to a\r\ncoding standard\" (from the Checkstyle home page).  This plugin allows a\r\nuser to run Checkstyle on the current Java file, putting the results in an\r\nerrorfile and jumping to the first Checkstyle error.\r\n","4":"The java_checkstyle.vim filetype plugin script integrates Checkstyle\r\nhttp:\/\/checkstyle.sourceforge.net\/ with Vim.  \"Checkstyle is a\r\ndevelopment tool to help programmers write Java code that adheres to a\r\ncoding standard\" (from the Checkstyle home page).  This plugin allows a\r\nuser to run Checkstyle on the current Java file, putting the results in an\r\nerrorfile and jumping to the first Checkstyle error.\r\n","install_details":"The java_checkstyle.vim script should be copied to the right directory.\r\nOn UNIX, this is ~\/.vim\/ftplugin; see ':help ftplugins' and ':help\r\nadd-global-plugin' for more information.  You will likely need to specify\r\nthe location of the checkstyle-all jar file and your desired Checkstyle\r\nconfiguration file, which can be done either by editing the script itself\r\nor by adding the settings to your vimrc file (see the section in the\r\nscript called \"Configuration\").  If you have not already done so, you will\r\nalso need to turn on filetype plugin usage in Vim using the following\r\ncommand (you will probably want to put this in your vimrc file):\r\n\r\n    :filetype plugin on","5":"The java_checkstyle.vim script should be copied to the right directory.\r\nOn UNIX, this is ~\/.vim\/ftplugin; see ':help ftplugins' and ':help\r\nadd-global-plugin' for more information.  You will likely need to specify\r\nthe location of the checkstyle-all jar file and your desired Checkstyle\r\nconfiguration file, which can be done either by editing the script itself\r\nor by adding the settings to your vimrc file (see the section in the\r\nscript called \"Configuration\").  If you have not already done so, you will\r\nalso need to turn on filetype plugin usage in Vim using the following\r\ncommand (you will probably want to put this in your vimrc file):\r\n\r\n    :filetype plugin on","first_name":"Xandy","6":"Xandy","last_name":"Johnson","7":"Johnson","releases":[{"0":"448","vim_version":"6.0","1":"6.0","script_version":"0.5","2":"0.5","version_comment":"Incorporated a fix from David McReynolds to correct handling of spaces in the Checkstyle command-line arguments.","3":"Incorporated a fix from David McReynolds to correct handling of spaces in the Checkstyle command-line arguments.","package":"java_checkstyle.tar.gz","4":"java_checkstyle.tar.gz","src_id":"2147","5":"2147","creation_date":"1058183195","6":"1058183195"},{"0":"448","vim_version":"6.0","1":"6.0","script_version":"0.4","2":"0.4","version_comment":"Updated to Checkstyle 3.1 based on the contribution of Minto Tsai.","3":"Updated to Checkstyle 3.1 based on the contribution of Minto Tsai.","package":"java_checkstyle.tar.gz","4":"java_checkstyle.tar.gz","src_id":"2140","5":"2140","creation_date":"1057876514","6":"1057876514"},{"0":"448","vim_version":"6.0","1":"6.0","script_version":"0.3","2":"0.3","version_comment":"Adding support for specifying the Checkstyle properties file (patch from Thomas Regner).","3":"Adding support for specifying the Checkstyle properties file (patch from Thomas Regner).","package":"java_checkstyle.tar.gz","4":"java_checkstyle.tar.gz","src_id":"1334","5":"1334","creation_date":"1035457232","6":"1035457232"},{"0":"448","vim_version":"6.0","1":"6.0","script_version":"0.2","2":"0.2","version_comment":"Dramatic simplification and elimination of dependencies.   The changes in\r\nthis version are based on the work of Doug Kearns (see the README for more\r\ndetails).","3":"Dramatic simplification and elimination of dependencies.   The changes in\r\nthis version are based on the work of Doug Kearns (see the README for more\r\ndetails).","package":"java_checkstyle.tar.gz","4":"java_checkstyle.tar.gz","src_id":"1327","5":"1327","creation_date":"1035236419","6":"1035236419"},{"0":"448","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"java_checkstyle.tar.gz","4":"java_checkstyle.tar.gz","src_id":"1304","5":"1304","creation_date":"1034683093","6":"1034683093"}]},"447":{"script_id":"447","0":"447","script_name":"exim.vim","1":"exim.vim","script_type":"syntax","2":"syntax","summary":"syntax highlighting for exim.conf","3":"syntax highlighting for exim.conf","description":"Syntax highlighting for Exim configuration file exim.conf.","4":"Syntax highlighting for Exim configuration file exim.conf.","install_details":"","5":"","first_name":"David","6":"David","last_name":"Necas","7":"Necas","releases":[{"0":"447","vim_version":"6.0","1":"6.0","script_version":"20040206","2":"20040206","version_comment":"Updated for Exim 4.30, a few missing keywords fixed.","3":"Updated for Exim 4.30, a few missing keywords fixed.","package":"exim.vim","4":"exim.vim","src_id":"2724","5":"2724","creation_date":"1075995971","6":"1075995971"},{"0":"447","vim_version":"6.0","1":"6.0","script_version":"20030518","2":"20030518","version_comment":"In fact, this is not an update at all. The previous version was (and still is) for Exim 3, while this one is for Exim 4 (only). I renamed the old one to exim3.vim on http:\/\/trific.ath.cx\/resources\/vim\/syntax\/ but in Vim 6.2 it's called exim.vim.","3":"In fact, this is not an update at all. The previous version was (and still is) for Exim 3, while this one is for Exim 4 (only). I renamed the old one to exim3.vim on http:\/\/trific.ath.cx\/resources\/vim\/syntax\/ but in Vim 6.2 it's called exim.vim.","package":"exim.vim","4":"exim.vim","src_id":"1998","5":"1998","creation_date":"1053266061","6":"1053266061"},{"0":"447","vim_version":"5.7","1":"5.7","script_version":"20021015","2":"20021015","version_comment":"Initial upload","3":"Initial upload","package":"exim.vim","4":"exim.vim","src_id":"1300","5":"1300","creation_date":"1034615651","6":"1034615651"}]},"446":{"script_id":"446","0":"446","script_name":"JavaDecompiler.vim","1":"JavaDecompiler.vim","script_type":"utility","2":"utility","summary":"Automatically decompiles java class files and displays java code.","3":"Automatically decompiles java class files and displays java code.","description":"When you edit a .class file using vim, this plugin will decompile the class file for you and display it in the current buffer.\r\n\r\nAdmittedly, the buffer management is not very robust, but it's a very handy plugin nonetheless.  How much cooler is it to view decompiled code using your favorite editor than to download a new UI to view Java code in?!","4":"When you edit a .class file using vim, this plugin will decompile the class file for you and display it in the current buffer.\r\n\r\nAdmittedly, the buffer management is not very robust, but it's a very handy plugin nonetheless.  How much cooler is it to view decompiled code using your favorite editor than to download a new UI to view Java code in?!","install_details":"Put jad.vim in your plugins directory.  \r\nDownload jad for your operating system (http:\/\/kpdus.tripod.com\/jad.html) and make sure it is in your system path.\r\n","5":"Put jad.vim in your plugins directory.  \r\nDownload jad for your operating system (http:\/\/kpdus.tripod.com\/jad.html) and make sure it is in your system path.\r\n","first_name":"David","6":"David","last_name":"Bowers","7":"Bowers","releases":[{"0":"446","vim_version":"6.0","1":"6.0","script_version":"1.3","2":"1.3","version_comment":"Delete not needed code.\r\nDetach buffer from 'class'-file and attach it to 'jad'-file.","3":"Delete not needed code.\r\nDetach buffer from 'class'-file and attach it to 'jad'-file.","package":"jad.vim","4":"jad.vim","src_id":"1329","5":"1329","creation_date":"1035272220","6":"1035272220"},{"0":"446","vim_version":"6.0","1":"6.0","script_version":"1.2","2":"1.2","version_comment":"Remove some gzip dependencies :)","3":"Remove some gzip dependencies :)","package":"jad.vim","4":"jad.vim","src_id":"1319","5":"1319","creation_date":"1034924107","6":"1034924107"},{"0":"446","vim_version":"6.0","1":"6.0","script_version":"1.1","2":"1.1","version_comment":"Initial upload","3":"Initial upload","package":"jad.vim","4":"jad.vim","src_id":"1299","5":"1299","creation_date":"1034581774","6":"1034581774"}]},"445":{"script_id":"445","0":"445","script_name":"Syntax for the BETA programming language","1":"Syntax for the BETA programming language","script_type":"syntax","2":"syntax","summary":"Syntax file for BETA","3":"Syntax file for BETA","description":"Syntax file for the BETA programming language. You can find a free compiler at www.mjolner.com.","4":"Syntax file for the BETA programming language. You can find a free compiler at www.mjolner.com.","install_details":"","5":"","first_name":"Janus","6":"Janus","last_name":"T\u00c3\u00b8ndering","7":"T\u00c3\u00b8ndering","releases":[{"0":"445","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"beta.vim","4":"beta.vim","src_id":"1295","5":"1295","creation_date":"1034430287","6":"1034430287"}]},"444":{"script_id":"444","0":"444","script_name":"deldiff.vim","1":"deldiff.vim","script_type":"utility","2":"utility","summary":"Delete blocks out of unified diffs","3":"Delete blocks out of unified diffs","description":"This script provides \"did\" and \"dad\" which work like \r\n\"dib\" or \"dip\" but for unified diffs.\r\n\"did\" deletes \"@@  ..\" surrounded blocks from a diff file.\r\n\"dad\" deletes the complete diff for one file.\r\nSee the script for more detailed behaviour.\r\nThey have proved to be invaluable for me as I often have to deal with unfied diffs.","4":"This script provides \"did\" and \"dad\" which work like \r\n\"dib\" or \"dip\" but for unified diffs.\r\n\"did\" deletes \"@@  ..\" surrounded blocks from a diff file.\r\n\"dad\" deletes the complete diff for one file.\r\nSee the script for more detailed behaviour.\r\nThey have proved to be invaluable for me as I often have to deal with unfied diffs.","install_details":"Drop into your plugindir or source them from your .vimrc","5":"Drop into your plugindir or source them from your .vimrc","first_name":"Tilmann","6":"Tilmann","last_name":"Bitterberg","7":"Bitterberg","releases":[{"0":"444","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"deldiff.vim","4":"deldiff.vim","src_id":"1293","5":"1293","creation_date":"1034414013","6":"1034414013"}]},"443":{"script_id":"443","0":"443","script_name":"spacehi.vim","1":"spacehi.vim","script_type":"utility","2":"utility","summary":"Togglable syntax highlighting of tabs and trailing spaces.","3":"Togglable syntax highlighting of tabs and trailing spaces.","description":"This plugin will highlight tabs and trailing spaces on a line, with the ability to toggle the highlighting on and off. Using highlighting to illuminate these characters is preferrable to using listchars and \"set list\" because it allows you to copy from the vim window without getting listchars shrapnel in your buffer.\r\n\r\nThe highlighting is done on a per buffer basis, and can be toggled on and off easily (the default binds to F3 if it\\'s unbound).\r\n","4":"This plugin will highlight tabs and trailing spaces on a line, with the ability to toggle the highlighting on and off. Using highlighting to illuminate these characters is preferrable to using listchars and \"set list\" because it allows you to copy from the vim window without getting listchars shrapnel in your buffer.\r\n\r\nThe highlighting is done on a per buffer basis, and can be toggled on and off easily (the default binds to F3 if it\\'s unbound).\r\n","install_details":"Drop in your plugins directory and you\\'re all set. Customization stuff can be found in the Documentation section of the script file.","5":"Drop in your plugins directory and you\\'re all set. Customization stuff can be found in the Documentation section of the script file.","first_name":"Adam","6":"Adam","last_name":"Lazur","7":"Lazur","releases":[{"0":"443","vim_version":"6.0","1":"6.0","script_version":"1.3","2":"1.3","version_comment":"Initial upload","3":"Initial upload","package":"spacehi.vim","4":"spacehi.vim","src_id":"1292","5":"1292","creation_date":"1034352672","6":"1034352672"}]},"442":{"script_id":"442","0":"442","script_name":"lilac.vim","1":"lilac.vim","script_type":"color scheme","2":"color scheme","summary":"A mixture of navajo-night.vim and xian.vim (GUI only)","3":"A mixture of navajo-night.vim and xian.vim (GUI only)","description":"A mixture of navajo-night.vim and xian.vim (my previous post, too *pastel*).\r\nNo support for cterm (GUI only).\r\n\r\nTested on:\r\n * LCD (advisable Contrast & Brightness @ ~25%)\r\n * CRT (advisable Contrast & Brightness @ ~75%)\r\n\r\nAims at:\r\n * minimized colors allocation (12 colors only )\r\n * reduced eye impact and save energy (no #FF, #F0 is the max authorized)\r\n * better looking folding and diff mode than xian.vim (tastes may vary)\r\n * while keeping most good looking colors from navajo-night (mostly the bg is different)\r\n\r\nPlease feedback to christian_michon@yahoo.fr for color tweaking and suggestions for\r\nenhancements.\r\n\r\nThanks to the authors of navajo-night.vim and Shantonu for his background color ;)\r\n\r\nChristian\r\nZZ","4":"A mixture of navajo-night.vim and xian.vim (my previous post, too *pastel*).\r\nNo support for cterm (GUI only).\r\n\r\nTested on:\r\n * LCD (advisable Contrast & Brightness @ ~25%)\r\n * CRT (advisable Contrast & Brightness @ ~75%)\r\n\r\nAims at:\r\n * minimized colors allocation (12 colors only )\r\n * reduced eye impact and save energy (no #FF, #F0 is the max authorized)\r\n * better looking folding and diff mode than xian.vim (tastes may vary)\r\n * while keeping most good looking colors from navajo-night (mostly the bg is different)\r\n\r\nPlease feedback to christian_michon@yahoo.fr for color tweaking and suggestions for\r\nenhancements.\r\n\r\nThanks to the authors of navajo-night.vim and Shantonu for his background color ;)\r\n\r\nChristian\r\nZZ","install_details":"Drop as usual in $VIMRUNTIME\/colors...\r\n\r\nAdd \":color lilac\" to your .gvimrc","5":"Drop as usual in $VIMRUNTIME\/colors...\r\n\r\nAdd \":color lilac\" to your .gvimrc","first_name":"Christian","6":"Christian","last_name":"MICHON","7":"MICHON","releases":[{"0":"442","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"lilac.vim","4":"lilac.vim","src_id":"1290","5":"1290","creation_date":"1034215244","6":"1034215244"}]},"441":{"script_id":"441","0":"441","script_name":"localvimrc","1":"localvimrc","script_type":"utility","2":"utility","summary":"load subdirectory specific vimrc files","3":"load subdirectory specific vimrc files","description":"Sometimes, when you work on different projects, you have the problem, that they use different indentation, tab expansion and so on. You need vimrc for each project that overrides your prefered settings from ~\/.vimrc\r\n\r\nThis plugin searches for local vimrc files in the file system tree of the currently opened file. By default it searches for all \".lvimrc\" files from the file's directory up to the root directory and loads them in reverse order. The filename and amount of loaded files are customizable through global variables.\r\n\r\nFor security reasons it the plugin asks for confirmation before loading a local vimrc file and loads it using :sandbox command. The plugin asks once per session and local vimrc before loading it, if the file didn't change since previous loading.\r\n\r\nIt is possible to define a whitelist and a blacklist of local vimrc files that are loaded or ignored unconditionally.\r\n\r\nIf you think this plugin could be improved, fork on GitHub and send a pull request or just tell me your ideas.\r\n\r\nGitHub: https:\/\/github.com\/embear\/vim-localvimrc","4":"Sometimes, when you work on different projects, you have the problem, that they use different indentation, tab expansion and so on. You need vimrc for each project that overrides your prefered settings from ~\/.vimrc\r\n\r\nThis plugin searches for local vimrc files in the file system tree of the currently opened file. By default it searches for all \".lvimrc\" files from the file's directory up to the root directory and loads them in reverse order. The filename and amount of loaded files are customizable through global variables.\r\n\r\nFor security reasons it the plugin asks for confirmation before loading a local vimrc file and loads it using :sandbox command. The plugin asks once per session and local vimrc before loading it, if the file didn't change since previous loading.\r\n\r\nIt is possible to define a whitelist and a blacklist of local vimrc files that are loaded or ignored unconditionally.\r\n\r\nIf you think this plugin could be improved, fork on GitHub and send a pull request or just tell me your ideas.\r\n\r\nGitHub: https:\/\/github.com\/embear\/vim-localvimrc","install_details":"localvimrc is now distributed as a vimball (see :help vimball)\r\n\r\nvim localvimrc.vmb\r\n:so %\r\n:q\r\n\r\nand that's all! ","5":"localvimrc is now distributed as a vimball (see :help vimball)\r\n\r\nvim localvimrc.vmb\r\n:so %\r\n:q\r\n\r\nand that's all! ","first_name":"Markus","6":"Markus","last_name":"Braun","7":"Braun","releases":[{"0":"441","vim_version":"7.4","1":"7.4","script_version":"3.1.0","2":"3.1.0","version_comment":"- add option to disable probing of Python versions\r\n- prevent recursive sourcing of local vimrc files\r\n- better handling of syntax errors in sourced local vimrc files\r\n- compatibility with current development versions of Vim","3":"- add option to disable probing of Python versions\r\n- prevent recursive sourcing of local vimrc files\r\n- better handling of syntax errors in sourced local vimrc files\r\n- compatibility with current development versions of Vim","package":"localvimrc.vmb","4":"localvimrc.vmb","src_id":"27167","5":"27167","creation_date":"1590007935","6":"1590007935"},{"0":"441","vim_version":"7.4","1":"7.4","script_version":"3.0.1","2":"3.0.1","version_comment":"- fix a compatibility issue with unavailable |v:true| and |v:false| in Vim version 7.4","3":"- fix a compatibility issue with unavailable |v:true| and |v:false| in Vim version 7.4","package":"localvimrc.vmb","4":"localvimrc.vmb","src_id":"26187","5":"26187","creation_date":"1534891186","6":"1534891186"},{"0":"441","vim_version":"7.4","1":"7.4","script_version":"3.0.0","2":"3.0.0","version_comment":"IMPORTANT NOTICE: The checksum algorithm was changed since last release thus all persistent answers are invalid and asked again on loading a local vimrc file for the first time after updateing the plugin.\r\n\r\n- use SHA256 as for calculating checksums and use FNV-1 as fallback.\r\n- add command |LocalVimRCCleanup| to remove all unusable persistence data.\r\n- add command |LocalVimRCForget| to remove persistence data for given files.\r\n- add command |LocalVimRCDebugShow| to show debug messages.\r\n- add setting |g:localvimrc_debug_lines| to limit the number of stored debug messages.","3":"IMPORTANT NOTICE: The checksum algorithm was changed since last release thus all persistent answers are invalid and asked again on loading a local vimrc file for the first time after updateing the plugin.\r\n\r\n- use SHA256 as for calculating checksums and use FNV-1 as fallback.\r\n- add command |LocalVimRCCleanup| to remove all unusable persistence data.\r\n- add command |LocalVimRCForget| to remove persistence data for given files.\r\n- add command |LocalVimRCDebugShow| to show debug messages.\r\n- add setting |g:localvimrc_debug_lines| to limit the number of stored debug messages.","package":"localvimrc.vmb","4":"localvimrc.vmb","src_id":"26182","5":"26182","creation_date":"1534472601","6":"1534472601"},{"0":"441","vim_version":"7.4","1":"7.4","script_version":"2.7.0","2":"2.7.0","version_comment":"- add setting |g:localvimrc_enable| and commands |LocalVimRCEnable| and |LocalVimRCDisable| to globally disable processing of local vimrc files.\r\n- add setting |g:localvimrc_event_pattern| to change the pattern for which the autocommand is executed.","3":"- add setting |g:localvimrc_enable| and commands |LocalVimRCEnable| and |LocalVimRCDisable| to globally disable processing of local vimrc files.\r\n- add setting |g:localvimrc_event_pattern| to change the pattern for which the autocommand is executed.","package":"localvimrc.vmb","4":"localvimrc.vmb","src_id":"25891","5":"25891","creation_date":"1521438540","6":"1521438540"},{"0":"441","vim_version":"7.4","1":"7.4","script_version":"2.6.1","2":"2.6.1","version_comment":"- fix a bug with missing uniq() in Vim version 7.4","3":"- fix a bug with missing uniq() in Vim version 7.4","package":"localvimrc.vmb","4":"localvimrc.vmb","src_id":"25833","5":"25833","creation_date":"1519110840","6":"1519110840"},{"0":"441","vim_version":"7.4","1":"7.4","script_version":"2.6.0","2":"2.6.0","version_comment":"- add command LocalVimRCEdit to edit sourced local vimrc files for the current buffer.\r\n- bug fixes","3":"- add command LocalVimRCEdit to edit sourced local vimrc files for the current buffer.\r\n- bug fixes","package":"localvimrc.vmb","4":"localvimrc.vmb","src_id":"25796","5":"25796","creation_date":"1516613031","6":"1516613031"},{"0":"441","vim_version":"7.2","1":"7.2","script_version":"2.5.0","2":"2.5.0","version_comment":"- g:localvimrc_whitelist and g:localvimrc_blacklist now takes optionally a list of regular expressions.\r\n- add convenience variables g:localvimrc_script_unresolved and g:localvimrc_script_dir_unresolved.\r\n- add ability to view local vimrc before sourcing when g:localvimrc_ask is enabled.\r\n- emit autocommands before and after sourcing files.\r\n- add g:localvimrc_file_directory_only to limit sourcing to local vimrc files in the same directory as the edited file.\r\n- add LocalVimRCFinish function to stop loading of remaining local vimrc files from within a local vimrc file.\r\n- add unit tests.","3":"- g:localvimrc_whitelist and g:localvimrc_blacklist now takes optionally a list of regular expressions.\r\n- add convenience variables g:localvimrc_script_unresolved and g:localvimrc_script_dir_unresolved.\r\n- add ability to view local vimrc before sourcing when g:localvimrc_ask is enabled.\r\n- emit autocommands before and after sourcing files.\r\n- add g:localvimrc_file_directory_only to limit sourcing to local vimrc files in the same directory as the edited file.\r\n- add LocalVimRCFinish function to stop loading of remaining local vimrc files from within a local vimrc file.\r\n- add unit tests.","package":"localvimrc.vmb","4":"localvimrc.vmb","src_id":"25017","5":"25017","creation_date":"1489041497","6":"1489041497"},{"0":"441","vim_version":"7.2","1":"7.2","script_version":"2.4.0","2":"2.4.0","version_comment":"- add setting g:localvimrc_event which defines the autocommand events that trigger local vimrc file loading.\r\n- make it possible to supply a list of local vimrc filenames in g:localvimrc_name\r\n- ask user when sourcing local vimrc fails and g:localvimrc_sandbox and g:localvimrc_ask is set whether the file should be sourced without sandbox.\r\n- don't lose persistence file on full partitions.\r\n- fix a bug where local vimrc files are sourced in wrong order when some of them are symlinks to a different directory.","3":"- add setting g:localvimrc_event which defines the autocommand events that trigger local vimrc file loading.\r\n- make it possible to supply a list of local vimrc filenames in g:localvimrc_name\r\n- ask user when sourcing local vimrc fails and g:localvimrc_sandbox and g:localvimrc_ask is set whether the file should be sourced without sandbox.\r\n- don't lose persistence file on full partitions.\r\n- fix a bug where local vimrc files are sourced in wrong order when some of them are symlinks to a different directory.","package":"localvimrc.vmb","4":"localvimrc.vmb","src_id":"23988","5":"23988","creation_date":"1454673155","6":"1454673155"},{"0":"441","vim_version":"7.2","1":"7.2","script_version":"2.3.0","2":"2.3.0","version_comment":"- private persistence file to enable persistence over concurrent vim instances.\r\n- add convenience variables g:localvimrc_sourced_once and g:localvimrc_sourced_once_for_file.","3":"- private persistence file to enable persistence over concurrent vim instances.\r\n- add convenience variables g:localvimrc_sourced_once and g:localvimrc_sourced_once_for_file.","package":"localvimrc.vba","4":"localvimrc.vba","src_id":"21434","5":"21434","creation_date":"1391719513","6":"1391719513"},{"0":"441","vim_version":"7.2","1":"7.2","script_version":"2.2.0","2":"2.2.0","version_comment":"- remove redraw calls for better performance and fixing a bug on windows.\r\n- load local vimrc on event BufWinEnter to fix a bug with window local\r\n  settings.\r\n- add g:localvimrc_reverse to change order of sourcing local vimrc files.\r\n- add convenience variables g:localvimrc_file, g:localvimrc_file_dir,\r\n  g:localvimrc_script and g:localvimrc_script_dir.\r\n","3":"- remove redraw calls for better performance and fixing a bug on windows.\r\n- load local vimrc on event BufWinEnter to fix a bug with window local\r\n  settings.\r\n- add g:localvimrc_reverse to change order of sourcing local vimrc files.\r\n- add convenience variables g:localvimrc_file, g:localvimrc_file_dir,\r\n  g:localvimrc_script and g:localvimrc_script_dir.\r\n","package":"localvimrc.vba","4":"localvimrc.vba","src_id":"21019","5":"21019","creation_date":"1383988127","6":"1383988127"},{"0":"441","vim_version":"7.2","1":"7.2","script_version":"2.1.0","2":"2.1.0","version_comment":"- add possibility to make decisions persistent\r\n- use full file path when storing decisions","3":"- add possibility to make decisions persistent\r\n- use full file path when storing decisions","package":"localvimrc.vba","4":"localvimrc.vba","src_id":"18689","5":"18689","creation_date":"1348604416","6":"1348604416"},{"0":"441","vim_version":"7.2","1":"7.2","script_version":"2.0.0","2":"2.0.0","version_comment":"- added g:localvimrc_whitelist and g:localvimrc_blacklist settings.\r\n- ask only once per session and local vimrc before loading it, if it didn't change.","3":"- added g:localvimrc_whitelist and g:localvimrc_blacklist settings.\r\n- ask only once per session and local vimrc before loading it, if it didn't change.","package":"localvimrc.vba","4":"localvimrc.vba","src_id":"17725","5":"17725","creation_date":"1333632263","6":"1333632263"},{"0":"441","vim_version":"7.0","1":"7.0","script_version":"2758","2":"2758","version_comment":"- source .lvimrc in a sandbox to better maintain security, configurable using g:localvimrc_sandbox \r\n- ask user before sourcing any local vimrc file, configurable using g:localvimrc_ask  \r\n","3":"- source .lvimrc in a sandbox to better maintain security, configurable using g:localvimrc_sandbox \r\n- ask user before sourcing any local vimrc file, configurable using g:localvimrc_ask  \r\n","package":"localvimrc.vim","4":"localvimrc.vim","src_id":"10578","5":"10578","creation_date":"1242056047","6":"1242056047"},{"0":"441","vim_version":"7.0","1":"7.0","script_version":"1870","2":"1870","version_comment":"- new configuration variable g:localvimrc_name to change filename\r\n- new configuration variable g:localvimrc_count to limit number of loaded files","3":"- new configuration variable g:localvimrc_name to change filename\r\n- new configuration variable g:localvimrc_count to limit number of loaded files","package":"localvimrc.vim","4":"localvimrc.vim","src_id":"7726","5":"7726","creation_date":"1190946202","6":"1190946202"},{"0":"441","vim_version":"7.0","1":"7.0","script_version":"1613","2":"1613","version_comment":"- switched to arrays in vim 7\r\n- escape file\/path names correctly","3":"- switched to arrays in vim 7\r\n- escape file\/path names correctly","package":"localvimrc.vim","4":"localvimrc.vim","src_id":"6948","5":"6948","creation_date":"1175739079","6":"1175739079"},{"0":"441","vim_version":"6.0","1":"6.0","script_version":"1.2","2":"1.2","version_comment":"Initial upload","3":"Initial upload","package":"localvimrc.vim","4":"localvimrc.vim","src_id":"1288","5":"1288","creation_date":"1034137331","6":"1034137331"}]},"440":{"script_id":"440","0":"440","script_name":"stata.vim","1":"stata.vim","script_type":"syntax","2":"syntax","summary":"vim syntax file for Stata programs","3":"vim syntax file for Stata programs","description":"stata.vim is a syntax file for Stata do and ado programs.\r\n\r\nThis syntax file will help identify:\r\n\r\n* some common Stata programming commands\r\n* Stata functions\r\n* local and global macro expansions\r\n* regular (\"\") and compound (`\"\"') double quotes\r\n* numeric and string formats \r\n* Stata comments\r\n* errors in parens, brackets, ...\r\n","4":"stata.vim is a syntax file for Stata do and ado programs.\r\n\r\nThis syntax file will help identify:\r\n\r\n* some common Stata programming commands\r\n* Stata functions\r\n* local and global macro expansions\r\n* regular (\"\") and compound (`\"\"') double quotes\r\n* numeric and string formats \r\n* Stata comments\r\n* errors in parens, brackets, ...\r\n","install_details":"I keep stata.vim in $HOME\/.vim\/syntax\/ and associate Stata programs in\r\n$HOME\/.vim\/filetypes.vim using the following: \r\n\r\naugroup filetypedetect\r\n        autocmd! BufRead,BufNewFile *.ado       set filetype=stata\r\n        autocmd! BufRead,BufNewFile *.class    set filetype=stata\r\n        autocmd! BufRead,BufNewFile *.do         set filetype=stata\r\naugrougp END\r\n","5":"I keep stata.vim in $HOME\/.vim\/syntax\/ and associate Stata programs in\r\n$HOME\/.vim\/filetypes.vim using the following: \r\n\r\naugroup filetypedetect\r\n        autocmd! BufRead,BufNewFile *.ado       set filetype=stata\r\n        autocmd! BufRead,BufNewFile *.class    set filetype=stata\r\n        autocmd! BufRead,BufNewFile *.do         set filetype=stata\r\naugrougp END\r\n","first_name":"Jeffrey","6":"Jeffrey","last_name":"Pitblado","7":"Pitblado","releases":[{"0":"440","vim_version":"6.0","1":"6.0","script_version":"1.1.2","2":"1.1.2","version_comment":"* fixed 'start' expression for stataFunc matches","3":"* fixed 'start' expression for stataFunc matches","package":"stata.vim","4":"stata.vim","src_id":"5571","5":"5571","creation_date":"1145261940","6":"1145261940"},{"0":"440","vim_version":"6.0","1":"6.0","script_version":"1.1.1","2":"1.1.1","version_comment":"renamed syntax groups st* to stata*\r\n'syntax clear' only under version control\r\ncheck for 'b:current_syntax', removed 'did_stata_syntax_inits'","3":"renamed syntax groups st* to stata*\r\n'syntax clear' only under version control\r\ncheck for 'b:current_syntax', removed 'did_stata_syntax_inits'","package":"stata.vim","4":"stata.vim","src_id":"5560","5":"5560","creation_date":"1145108639","6":"1145108639"},{"0":"440","vim_version":"6.0","1":"6.0","script_version":"1.1.0","2":"1.1.0","version_comment":"* updated for Stata 9\r\n* improved function coverage\r\n* trimmed most Stata commands out, leaving only common programming commands\r\n","3":"* updated for Stata 9\r\n* improved function coverage\r\n* trimmed most Stata commands out, leaving only common programming commands\r\n","package":"stata.vim","4":"stata.vim","src_id":"5552","5":"5552","creation_date":"1144968948","6":"1144968948"},{"0":"440","vim_version":"6.0","1":"6.0","script_version":"1.0.5","2":"1.0.5","version_comment":"Initial upload","3":"Initial upload","package":"stata.vim","4":"stata.vim","src_id":"1286","5":"1286","creation_date":"1034077448","6":"1034077448"}]},"439":{"script_id":"439","0":"439","script_name":"titlecase.vim","1":"titlecase.vim","script_type":"utility","2":"utility","summary":"Convert range or visual to titlecase.","3":"Convert range or visual to titlecase.","description":"Sample:\r\nGiven:\r\nChange a range or visual to title case, i.e.\r\n\":TitleCase<CR>\" results in:\r\nChange A Range Or Visual To Title Case, I.E.\r\n\r\nThis simple changes (via :s) \\<\\l (start of word, lowercase a-z) to uppercase. Probably not perfect Titlecase but works good enough for a quickie!\r\n\r\nRemaps (with no elegance) <F5> to FeralTitleCase_Visual, change as desired.\r\n\r\nVisual method works for single line visuals only, multi line it tries to be clever and makes a mess.. use with caution, single (part of) line works fine though. (needs to have a check that say I don't do multi line visuals!; or only char wise visuals or something).\r\nRange Command (defaults to current line) is:TitleCase\r\nIts small, crude and dirty. But it works :)\r\n\r\nHappy VIMing!","4":"Sample:\r\nGiven:\r\nChange a range or visual to title case, i.e.\r\n\":TitleCase<CR>\" results in:\r\nChange A Range Or Visual To Title Case, I.E.\r\n\r\nThis simple changes (via :s) \\<\\l (start of word, lowercase a-z) to uppercase. Probably not perfect Titlecase but works good enough for a quickie!\r\n\r\nRemaps (with no elegance) <F5> to FeralTitleCase_Visual, change as desired.\r\n\r\nVisual method works for single line visuals only, multi line it tries to be clever and makes a mess.. use with caution, single (part of) line works fine though. (needs to have a check that say I don't do multi line visuals!; or only char wise visuals or something).\r\nRange Command (defaults to current line) is:TitleCase\r\nIts small, crude and dirty. But it works :)\r\n\r\nHappy VIMing!","install_details":"Place in plugin folder\r\n\r\nUninstall remove or rename script file.","5":"Place in plugin folder\r\n\r\nUninstall remove or rename script file.","first_name":"Robert","6":"Robert","last_name":"KellyIV","7":"KellyIV","releases":[{"0":"439","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"titlecase.vim","4":"titlecase.vim","src_id":"1284","5":"1284","creation_date":"1034022287","6":"1034022287"}]},"438":{"script_id":"438","0":"438","script_name":"cppgetset.vim","1":"cppgetset.vim","script_type":"ftplugin","2":"ftplugin","summary":"Convert a data type definition into get\/set data members.","3":"Convert a data type definition into get\/set data members.","description":"Ment for c++ class data members; modify for others...\r\nDoes not work with static data members. (see comment in script, easy enough to rem out the check if you like)\r\n\r\nThe Although inserting both get and set member functions is currently hard coded the format (brace format and some buityfication of the var name) is handled by optional global option vars. NOTE you do not have to define anything unless you want different ouput from the default.\r\n\r\nNOTE this sniplet is in the .vim file\r\n\"Place something like the below in your .vimrc or where ever you like to keep\r\n\"    your global option vars and change as desired.\r\n\"\"\r\n\"\"*****************************************************************\r\n\"\" GETSET Options: {{{\r\n\"\"*****************************************************************\r\n\"\" You are welcomed to email me if there is another format you would like for\r\n\"\"    this, please include example code!\r\n\"\" See cppgetset.vim for more documtation.\r\n\"\" Member Function Name Prefix:\r\n\"\"        0 for (default)\r\n\"\"            \"Get_\"\r\n\"\"            \"Set_\"\r\n\"\"        else\r\n\"\"            \"get\"\r\n\"\"            \"set\"\r\n\"let g:getset_StyleOfGetSetMethod                 = 1\r\n\"\" Brace Style:\r\n\"\"        0 for (default)\r\n\"\"            func()\r\n\"\"            {\r\n\"\"            }\r\n\"\"        else\r\n\"\"            func() {\r\n\"\"            }\r\n\"let g:getset_StyleOfBraces                       = 1\r\n\"\" HowTo Trim Var Prefix:\r\n\"\"        1 for (default)\r\n\"\"            if Var prefix is m_ remove the m so the prefix is _\r\n\"\"            else prepend _\r\n\"\"        2 for\r\n\"\"            Prepend _\r\n\"\"        else\r\n\"\"            do not modify Var\r\n\"\"    I.e.\r\n\"\"        0 = m_lFlags    ->    m_lFlags\r\n\"\"            mlFlags     ->    mlFlags\r\n\"\"        1 = m_lFlags    ->    _lFlags\r\n\"\"            mlFlags     ->    _mlFlags\r\n\"\"        2 = m_lFlags    ->    __lFlags\r\n\"\"            mlFlags     ->    _mlFlags\r\n\"let g:getset_Trim_VarPrefix                      = 2\r\n\"\" Howto Trim Member Function Name Var Prefix:\r\n\"\"        1 for (default)\r\n\"\"            Remove m_\r\n\"\"        2 for\r\n\"\"            Remove m\r\n\"\"        else\r\n\"\"            do not modify Var\r\n\"let g:getset_Trim_MemberFunctionNameVarPrefix    = 2\r\n\"\" }}}\r\n\"\"\r\n\r\n\r\n\r\n\r\n\r\nExample:\r\nclass CTester\r\n{\r\n    char    m_caBuffer[_MAX_PATH];\r\n    int        m_iLenBuffer; \/\/ 2\r\n    long    m_lFlags;\r\n    \/\/ Static member declaration.\r\n    \/\/ [Feral:275\/02@15:02] this SHOULD abort out;\r\n    static long m_bytecount;\r\n}\r\nPlace cursor on line with m_caBuffer and :GETSET\r\nPlace cursor in .cpp file where you want the get\/set member function implimentations and :GETSET gives you:\r\n\r\n\r\n\/\/ {{{\r\n\/*!\r\n * \\brief    Get m_caBuffer.\r\n *\r\n * \\return    m_caBuffer as a char.\r\n *\/ \/\/ }}}\r\nchar CTester::Get_caBuffer()\r\n{\r\n    return(m_caBuffer);\r\n}\r\n\r\n\/\/ {{{\r\n\/*!\r\n * \\brief    Set m_caBuffer.\r\n *\r\n * \\param    _caBuffer    The new value for m_caBuffer (as a char).\r\n *\/ \/\/ }}}\r\nvoid CTester::Set_caBuffer(char _caBuffer)\r\n{\r\n    m_caBuffer = _caBuffer;\r\n    return;\r\n}\r\n\r\n\r\nNote in this example in particular you'll probably need to edit the actual code to get\/set but this is a nice fast starting spot...\r\nNote the comment method used is suitable for Doxygen (I think!) easy enough to change though, email me and I'll add support for others... provide examples though!\r\n\r\nNote that you call :GETSET twice (I was playing with this idea--one less thing to remember) The function decides what to do based on the file extension. If :GETSET's attempt at being clever is incorect, or you want to place inline member functions you can easily overide what :GETSET does with the optional params g (get), p (put), i (inline), thus to place inline memberfunctions you :GETSET i\r\n\r\nInspired by javaGetSet.vim by Tom Bast See: http:\/\/vim.sourceforge.net\/script.php?script_id=436\r\nRegister pasting origial idea from one of them scripts at vim.sf.net :)\r\n\r\nAlso be sure to look at Luc Hermitte's cpp_InsertAccessors.vim (See: http:\/\/hermitte.free.fr\/vim) it is basicaly superior (but a bit larger)\r\n\r\nHappy VIMing!","4":"Ment for c++ class data members; modify for others...\r\nDoes not work with static data members. (see comment in script, easy enough to rem out the check if you like)\r\n\r\nThe Although inserting both get and set member functions is currently hard coded the format (brace format and some buityfication of the var name) is handled by optional global option vars. NOTE you do not have to define anything unless you want different ouput from the default.\r\n\r\nNOTE this sniplet is in the .vim file\r\n\"Place something like the below in your .vimrc or where ever you like to keep\r\n\"    your global option vars and change as desired.\r\n\"\"\r\n\"\"*****************************************************************\r\n\"\" GETSET Options: {{{\r\n\"\"*****************************************************************\r\n\"\" You are welcomed to email me if there is another format you would like for\r\n\"\"    this, please include example code!\r\n\"\" See cppgetset.vim for more documtation.\r\n\"\" Member Function Name Prefix:\r\n\"\"        0 for (default)\r\n\"\"            \"Get_\"\r\n\"\"            \"Set_\"\r\n\"\"        else\r\n\"\"            \"get\"\r\n\"\"            \"set\"\r\n\"let g:getset_StyleOfGetSetMethod                 = 1\r\n\"\" Brace Style:\r\n\"\"        0 for (default)\r\n\"\"            func()\r\n\"\"            {\r\n\"\"            }\r\n\"\"        else\r\n\"\"            func() {\r\n\"\"            }\r\n\"let g:getset_StyleOfBraces                       = 1\r\n\"\" HowTo Trim Var Prefix:\r\n\"\"        1 for (default)\r\n\"\"            if Var prefix is m_ remove the m so the prefix is _\r\n\"\"            else prepend _\r\n\"\"        2 for\r\n\"\"            Prepend _\r\n\"\"        else\r\n\"\"            do not modify Var\r\n\"\"    I.e.\r\n\"\"        0 = m_lFlags    ->    m_lFlags\r\n\"\"            mlFlags     ->    mlFlags\r\n\"\"        1 = m_lFlags    ->    _lFlags\r\n\"\"            mlFlags     ->    _mlFlags\r\n\"\"        2 = m_lFlags    ->    __lFlags\r\n\"\"            mlFlags     ->    _mlFlags\r\n\"let g:getset_Trim_VarPrefix                      = 2\r\n\"\" Howto Trim Member Function Name Var Prefix:\r\n\"\"        1 for (default)\r\n\"\"            Remove m_\r\n\"\"        2 for\r\n\"\"            Remove m\r\n\"\"        else\r\n\"\"            do not modify Var\r\n\"let g:getset_Trim_MemberFunctionNameVarPrefix    = 2\r\n\"\" }}}\r\n\"\"\r\n\r\n\r\n\r\n\r\n\r\nExample:\r\nclass CTester\r\n{\r\n    char    m_caBuffer[_MAX_PATH];\r\n    int        m_iLenBuffer; \/\/ 2\r\n    long    m_lFlags;\r\n    \/\/ Static member declaration.\r\n    \/\/ [Feral:275\/02@15:02] this SHOULD abort out;\r\n    static long m_bytecount;\r\n}\r\nPlace cursor on line with m_caBuffer and :GETSET\r\nPlace cursor in .cpp file where you want the get\/set member function implimentations and :GETSET gives you:\r\n\r\n\r\n\/\/ {{{\r\n\/*!\r\n * \\brief    Get m_caBuffer.\r\n *\r\n * \\return    m_caBuffer as a char.\r\n *\/ \/\/ }}}\r\nchar CTester::Get_caBuffer()\r\n{\r\n    return(m_caBuffer);\r\n}\r\n\r\n\/\/ {{{\r\n\/*!\r\n * \\brief    Set m_caBuffer.\r\n *\r\n * \\param    _caBuffer    The new value for m_caBuffer (as a char).\r\n *\/ \/\/ }}}\r\nvoid CTester::Set_caBuffer(char _caBuffer)\r\n{\r\n    m_caBuffer = _caBuffer;\r\n    return;\r\n}\r\n\r\n\r\nNote in this example in particular you'll probably need to edit the actual code to get\/set but this is a nice fast starting spot...\r\nNote the comment method used is suitable for Doxygen (I think!) easy enough to change though, email me and I'll add support for others... provide examples though!\r\n\r\nNote that you call :GETSET twice (I was playing with this idea--one less thing to remember) The function decides what to do based on the file extension. If :GETSET's attempt at being clever is incorect, or you want to place inline member functions you can easily overide what :GETSET does with the optional params g (get), p (put), i (inline), thus to place inline memberfunctions you :GETSET i\r\n\r\nInspired by javaGetSet.vim by Tom Bast See: http:\/\/vim.sourceforge.net\/script.php?script_id=436\r\nRegister pasting origial idea from one of them scripts at vim.sf.net :)\r\n\r\nAlso be sure to look at Luc Hermitte's cpp_InsertAccessors.vim (See: http:\/\/hermitte.free.fr\/vim) it is basicaly superior (but a bit larger)\r\n\r\nHappy VIMing!","install_details":"Drop in ftplugin\/cpp or the like.\r\n\r\nUninstall is simply remove the script file.\r\n\r\nTo TRY this drop it in your ftplugin\/cpp then open a header file, locate a class data member, :GETSET on it, then move where you want inline get set methods and :GETSET i ... if you don't like it, just remove it else look at the options :)","5":"Drop in ftplugin\/cpp or the like.\r\n\r\nUninstall is simply remove the script file.\r\n\r\nTo TRY this drop it in your ftplugin\/cpp then open a header file, locate a class data member, :GETSET on it, then move where you want inline get set methods and :GETSET i ... if you don't like it, just remove it else look at the options :)","first_name":"Robert","6":"Robert","last_name":"KellyIV","7":"KellyIV","releases":[{"0":"438","vim_version":"6.0","1":"6.0","script_version":"0.2","2":"0.2","version_comment":"* More robust class\/struct handling\r\n* Global vars for options to determin how the get set methods look.\r\n* Proper ftplugin, MUST be placed in ftplugin\/cpp or the like.\r\n","3":"* More robust class\/struct handling\r\n* Global vars for options to determin how the get set methods look.\r\n* Proper ftplugin, MUST be placed in ftplugin\/cpp or the like.\r\n","package":"cppgetset.vim","4":"cppgetset.vim","src_id":"1317","5":"1317","creation_date":"1034893683","6":"1034893683"},{"0":"438","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"cppgetset.vim","4":"cppgetset.vim","src_id":"1283","5":"1283","creation_date":"1034021568","6":"1034021568"}]},"437":{"script_id":"437","0":"437","script_name":"copycppdectoimp.vim","1":"copycppdectoimp.vim","script_type":"ftplugin","2":"ftplugin","summary":"Expanded version of VIM-TIP#335 - Copy C++ function declaration into implementat","3":"Expanded version of VIM-TIP#335 - Copy C++ function declaration into implementat","description":"Ment for cpp class member functions, also works for normal c functions; modify for others...\r\nThis is not perfect, but works pretty good. -- Works out of the box, however you may want to customize it some. Customization is as easy as defining some global vars...\r\n\r\n\" OPTIOINAL: Place something like the below in your .vimrc or where ever you like to keep your global option vars and change as desired.\r\n\" Note, these are the defaults.\r\n\"*****************************************************************\r\n\" GHPH Options: {{{\r\n\"*****************************************************************\r\n\" See copycppdectoimp.vim for more documtation.\r\n\" Virtual: 1 for commented, else removed.\r\nlet g:ghph_ShowVirtual                    = 0\r\n\" Static:  1 for commented, else removed.\r\nlet g:ghph_ShowStatic                     = 0\r\n\" Default Params: 3 for \/*5*\/, 2 for \/* = 5*\/, else removed.\r\nlet g:ghph_ShowDefaultParams     = 3\r\n\" Command: 1 to define :GHPH (default if nothing defined), 0 to NOT define.\r\nlet g:ghph_useGHPH                       = 1\r\n\" Command: 1 to define :GH and :PH, 0 to NOT define.\r\n\"let g:ghph_useGHandPH               = 1\r\n\" }}}\r\n\r\n\r\n:GHPH when in a header file (.h) and on a member function decloration.\r\nThen :GHPH when in a source file (.cpp or the like) where you want the properly expanded implimentation of the member function.\r\n(There is also :GH and :PH or :GHPH g :GHPH p as alternitive methods of using this, see below.)\r\n\r\nPlease see the comments in the file for more info.\r\n\r\nExample:\r\nclass CTest\r\n{\r\n    void Test_Member_Function_G(\r\n        int        _iSomeNumber,                \/\/!< doxy comment\r\n        char    * _cpSomeString,            \/\/!< Same\r\n        float    \/*_fNotused*\/,        \/\/!< not used param. Heh aka error stress test.\r\n        int        _iFlags = 0            \/*!< I think *\/\r\n        );    \/\/ yea whatever.\r\n}\r\n\/\/ nested classes\/structs and inlined functions supported.\r\n\/\/ If you have something you want to work but doesnt email me an I'll see if I can get it to.\r\n\r\nPlace cursor on line with 'Test_Member_Function_G' and :GHPH\r\nPlace cursor in .cpp file where you want function and :GHPH gives you:\r\nvoid CTest::Test_Member_Function_G(int _iSomeNumber, char * _cpSomeString, float \/*_fNotused*\/, int _iFlags\/*0*\/)\r\n{\r\n}\r\nWith your cursor on the opening brace ready for a o\r\n\r\nHow static, virtual and default params are comented in the function are configurable (can totally remove them if you like), See the file for more info.\r\n\r\nNote that you call :GHPH twice (I was playing with this idea--one less thing to remember) The function decides what to do based on the file extension (only .h at the moment but easy to change\/add more). If you like it is as easy as unreming the command definitions to get :GH and :PH.\r\n\r\nYou can overide :GHPH's attempt to be clever and force getting the definition or putting the implimentation via :GHPH g and :GHPH p respectivly.\r\n\r\nAlthough still a work in progress it both functions and behaves well.\r\n\r\n\r\nTo TRY this all you need to is place this in your ftplugin\/cpp directory and then :GHPH on a member function and :GHPH in the source file. Don't like it? remove the file from ftplugin\/cpp\r\n\r\n\r\nThanks to Leif Wickland for VIM-Tip#335 from which this file derived.\r\nSee: http:\/\/vim.sourceforge.net\/tip_view.php?tip_id=335\r\n\r\nWhat YOU would like to see in this script wanted, drop me an email.\r\nHappy VIMing!","4":"Ment for cpp class member functions, also works for normal c functions; modify for others...\r\nThis is not perfect, but works pretty good. -- Works out of the box, however you may want to customize it some. Customization is as easy as defining some global vars...\r\n\r\n\" OPTIOINAL: Place something like the below in your .vimrc or where ever you like to keep your global option vars and change as desired.\r\n\" Note, these are the defaults.\r\n\"*****************************************************************\r\n\" GHPH Options: {{{\r\n\"*****************************************************************\r\n\" See copycppdectoimp.vim for more documtation.\r\n\" Virtual: 1 for commented, else removed.\r\nlet g:ghph_ShowVirtual                    = 0\r\n\" Static:  1 for commented, else removed.\r\nlet g:ghph_ShowStatic                     = 0\r\n\" Default Params: 3 for \/*5*\/, 2 for \/* = 5*\/, else removed.\r\nlet g:ghph_ShowDefaultParams     = 3\r\n\" Command: 1 to define :GHPH (default if nothing defined), 0 to NOT define.\r\nlet g:ghph_useGHPH                       = 1\r\n\" Command: 1 to define :GH and :PH, 0 to NOT define.\r\n\"let g:ghph_useGHandPH               = 1\r\n\" }}}\r\n\r\n\r\n:GHPH when in a header file (.h) and on a member function decloration.\r\nThen :GHPH when in a source file (.cpp or the like) where you want the properly expanded implimentation of the member function.\r\n(There is also :GH and :PH or :GHPH g :GHPH p as alternitive methods of using this, see below.)\r\n\r\nPlease see the comments in the file for more info.\r\n\r\nExample:\r\nclass CTest\r\n{\r\n    void Test_Member_Function_G(\r\n        int        _iSomeNumber,                \/\/!< doxy comment\r\n        char    * _cpSomeString,            \/\/!< Same\r\n        float    \/*_fNotused*\/,        \/\/!< not used param. Heh aka error stress test.\r\n        int        _iFlags = 0            \/*!< I think *\/\r\n        );    \/\/ yea whatever.\r\n}\r\n\/\/ nested classes\/structs and inlined functions supported.\r\n\/\/ If you have something you want to work but doesnt email me an I'll see if I can get it to.\r\n\r\nPlace cursor on line with 'Test_Member_Function_G' and :GHPH\r\nPlace cursor in .cpp file where you want function and :GHPH gives you:\r\nvoid CTest::Test_Member_Function_G(int _iSomeNumber, char * _cpSomeString, float \/*_fNotused*\/, int _iFlags\/*0*\/)\r\n{\r\n}\r\nWith your cursor on the opening brace ready for a o\r\n\r\nHow static, virtual and default params are comented in the function are configurable (can totally remove them if you like), See the file for more info.\r\n\r\nNote that you call :GHPH twice (I was playing with this idea--one less thing to remember) The function decides what to do based on the file extension (only .h at the moment but easy to change\/add more). If you like it is as easy as unreming the command definitions to get :GH and :PH.\r\n\r\nYou can overide :GHPH's attempt to be clever and force getting the definition or putting the implimentation via :GHPH g and :GHPH p respectivly.\r\n\r\nAlthough still a work in progress it both functions and behaves well.\r\n\r\n\r\nTo TRY this all you need to is place this in your ftplugin\/cpp directory and then :GHPH on a member function and :GHPH in the source file. Don't like it? remove the file from ftplugin\/cpp\r\n\r\n\r\nThanks to Leif Wickland for VIM-Tip#335 from which this file derived.\r\nSee: http:\/\/vim.sourceforge.net\/tip_view.php?tip_id=335\r\n\r\nWhat YOU would like to see in this script wanted, drop me an email.\r\nHappy VIMing!","install_details":"Drop in your ftplugin\/cpp directory.\r\n\r\nUninstall is just remove the script file and any vars\/mappings you have made.","5":"Drop in your ftplugin\/cpp directory.\r\n\r\nUninstall is just remove the script file and any vars\/mappings you have made.","first_name":"Robert","6":"Robert","last_name":"KellyIV","7":"KellyIV","releases":[{"0":"437","vim_version":"6.0","1":"6.0","script_version":"0.46","2":"0.46","version_comment":"Refined matching declaration prens; should be more resistant to mismatched prens outside of the function declaration. Mismatched prens inside the function declaration (i.e. in comments) will confuse this still.\r\nNOTE that I goofed the previous version's number, it was 0.45 NOT 0.55. Oopsie!","3":"Refined matching declaration prens; should be more resistant to mismatched prens outside of the function declaration. Mismatched prens inside the function declaration (i.e. in comments) will confuse this still.\r\nNOTE that I goofed the previous version's number, it was 0.45 NOT 0.55. Oopsie!","package":"copycppdectoimp.vim","4":"copycppdectoimp.vim","src_id":"2040","5":"2040","creation_date":"1054607090","6":"1054607090"},{"0":"437","vim_version":"6.0","1":"6.0","script_version":"0.55","2":"0.55","version_comment":"* Bug fix: more robust handling of comments and prens and things in multi line function declorations.\r\n* Small fix to take into account non blank equalprg; thanks to Nathan Dunn for help tracking this down.","3":"* Bug fix: more robust handling of comments and prens and things in multi line function declorations.\r\n* Small fix to take into account non blank equalprg; thanks to Nathan Dunn for help tracking this down.","package":"copycppdectoimp.vim","4":"copycppdectoimp.vim","src_id":"1966","5":"1966","creation_date":"1052015354","6":"1052015354"},{"0":"437","vim_version":"6.0","1":"6.0","script_version":"0.43","2":"0.43","version_comment":"Bugfix, The case of filename extension no loger matters during the check for header\/source.\r\n","3":"Bugfix, The case of filename extension no loger matters during the check for header\/source.\r\n","package":"copycppdectoimp.vim","4":"copycppdectoimp.vim","src_id":"1316","5":"1316","creation_date":"1034893571","6":"1034893571"},{"0":"437","vim_version":"6.0","1":"6.0","script_version":"0.32","2":"0.32","version_comment":"* More intelligent\/robust checking\/finding the class.\r\n* Nested classes are now supported.\r\n* Normal functions now work.\r\n","3":"* More intelligent\/robust checking\/finding the class.\r\n* Nested classes are now supported.\r\n* Normal functions now work.\r\n","package":"copycppdectoimp.vim","4":"copycppdectoimp.vim","src_id":"1289","5":"1289","creation_date":"1034186797","6":"1034186797"},{"0":"437","vim_version":"6.0","1":"6.0","script_version":"0.3","2":"0.3","version_comment":"Initial upload","3":"Initial upload","package":"copycppdectoimp.vim","4":"copycppdectoimp.vim","src_id":"1282","5":"1282","creation_date":"1034019918","6":"1034019918"}]},"436":{"script_id":"436","0":"436","script_name":"javaGetSet.vim","1":"javaGetSet.vim","script_type":"utility","2":"utility","summary":"This will createGet\/set methods automatically for a Java class.","3":"This will createGet\/set methods automatically for a Java class.","description":"This will create Java Get\/set methods for a bean.  \r\nThe motivation was a fellow who told me Rational Rose was superior to vim because it could automatically create get\/set methods for a bean given properties. So I cranked this out.\r\n\r\nThis requires Java Syntax be on and works with 6.1\r\nThe process is to first create your properties (for example: int id; String userName;) and  let this make the methods. It requires some manual work, but not much.  You need to put the datatype in buffer 'a' and the property in buffer 'b'  For example, say you have this:\r\n\r\npublic String foo, bar, baz;\r\n\r\nYank word \"String\" into buffer 'a' and if you want to make get\/set for foo,\r\nyank word \"foo\" into buffer 'b'.  Then go to where you want the get\/set\r\nmethods and type <ctl>gs and the methods with Javadoc are created. \r\nTo do \"bar\" next, just replace buffer 'b' with \"bar\".  So, with \"String\" in buffer 'a' and 'foo' in buffer 'b' Doing this: <ctl>gs  will give you this:\r\n\r\n\r\n   \/**\r\n    * Get foo.\r\n    *\r\n    * @return foo as a String \r\n    *\/\r\n   public String  getFoo()\r\n   {\r\n      return(foo);\r\n   }\r\n\r\n   \/**\r\n    * Set foo.\r\n    *\r\n    * @param The foo as a String \r\n    *\/\r\n   public void setFoo(String  foo)\r\n   {\r\n      this.foo = foo;\r\n      return;\r\n   }\r\n\r\n\r\nPretty cool, huh?","4":"This will create Java Get\/set methods for a bean.  \r\nThe motivation was a fellow who told me Rational Rose was superior to vim because it could automatically create get\/set methods for a bean given properties. So I cranked this out.\r\n\r\nThis requires Java Syntax be on and works with 6.1\r\nThe process is to first create your properties (for example: int id; String userName;) and  let this make the methods. It requires some manual work, but not much.  You need to put the datatype in buffer 'a' and the property in buffer 'b'  For example, say you have this:\r\n\r\npublic String foo, bar, baz;\r\n\r\nYank word \"String\" into buffer 'a' and if you want to make get\/set for foo,\r\nyank word \"foo\" into buffer 'b'.  Then go to where you want the get\/set\r\nmethods and type <ctl>gs and the methods with Javadoc are created. \r\nTo do \"bar\" next, just replace buffer 'b' with \"bar\".  So, with \"String\" in buffer 'a' and 'foo' in buffer 'b' Doing this: <ctl>gs  will give you this:\r\n\r\n\r\n   \/**\r\n    * Get foo.\r\n    *\r\n    * @return foo as a String \r\n    *\/\r\n   public String  getFoo()\r\n   {\r\n      return(foo);\r\n   }\r\n\r\n   \/**\r\n    * Set foo.\r\n    *\r\n    * @param The foo as a String \r\n    *\/\r\n   public void setFoo(String  foo)\r\n   {\r\n      this.foo = foo;\r\n      return;\r\n   }\r\n\r\n\r\nPretty cool, huh?","install_details":"source it.","5":"source it.","first_name":"Tom","6":"Tom","last_name":"Bast","7":"Bast","releases":[{"0":"436","vim_version":"6.0","1":"6.0","script_version":"1.3","2":"1.3","version_comment":"Initial upload","3":"Initial upload","package":"javaGetSet.vim","4":"javaGetSet.vim","src_id":"1275","5":"1275","creation_date":"1033547601","6":"1033547601"}]},"435":{"script_id":"435","0":"435","script_name":"pythonhelper","1":"pythonhelper","script_type":"utility","2":"utility","summary":"Displays Python class, method or function the cursor is in on the status line","3":"Displays Python class, method or function the cursor is in on the status line","description":"Vim script to help moving around in larger Python source files. It displays current class, method or function the cursor is placed in in the status line for every python file. It's more clever than Yegappan Lakshmanan's taglist.vim because it takes into account indetation and comments to determine what tag the cursor is placed in and from version 0.80 doesn't need exuberant ctags utility.\r\n\r\nNote: The script displays current tag on the status line only in NORMAL mode. This is because CursorHold event in VIM is fired up only in this mode. However if you'd like to know what tag you are in even in INSERT or VISUAL mode, contact me (email specified in the script) and I'll send you a patch that enables firing up CursorHold event in those modes as well.","4":"Vim script to help moving around in larger Python source files. It displays current class, method or function the cursor is placed in in the status line for every python file. It's more clever than Yegappan Lakshmanan's taglist.vim because it takes into account indetation and comments to determine what tag the cursor is placed in and from version 0.80 doesn't need exuberant ctags utility.\r\n\r\nNote: The script displays current tag on the status line only in NORMAL mode. This is because CursorHold event in VIM is fired up only in this mode. However if you'd like to know what tag you are in even in INSERT or VISUAL mode, contact me (email specified in the script) and I'll send you a patch that enables firing up CursorHold event in those modes as well.","install_details":"1. Make sure your Vim has python feature on (+python). If not, you will need to recompile it with --with-pythoninterp option to the configure script\r\n2. Copy script pythonhelper.vim to the $HOME\/.vim\/plugin directory\r\n3. Run Vim and open any python file.","5":"1. Make sure your Vim has python feature on (+python). If not, you will need to recompile it with --with-pythoninterp option to the configure script\r\n2. Copy script pythonhelper.vim to the $HOME\/.vim\/plugin directory\r\n3. Run Vim and open any python file.","first_name":"Michal","6":"Michal","last_name":"Vitecek","7":"Vitecek","releases":[{"0":"435","vim_version":"7.0","1":"7.0","script_version":"0.83","2":"0.83","version_comment":"Added support for the CursorHoldI event so that the class\/method\/function is recognized also in Insert mode.","3":"Added support for the CursorHoldI event so that the class\/method\/function is recognized also in Insert mode.","package":"pythonhelper.vim","4":"pythonhelper.vim","src_id":"12010","5":"12010","creation_date":"1262621325","6":"1262621325"},{"0":"435","vim_version":"6.0","1":"6.0","script_version":"0.82","2":"0.82","version_comment":"- fixed a bug when nested functions\/classes were not properly detected","3":"- fixed a bug when nested functions\/classes were not properly detected","package":"pythonhelper.vim","4":"pythonhelper.vim","src_id":"10987","5":"10987","creation_date":"1247242272","6":"1247242272"},{"0":"435","vim_version":"6.0","1":"6.0","script_version":"0.81","2":"0.81","version_comment":"- fixed a small bug in indent level recognition","3":"- fixed a small bug in indent level recognition","package":"pythonhelper.vim","4":"pythonhelper.vim","src_id":"1807","5":"1807","creation_date":"1047538073","6":"1047538073"},{"0":"435","vim_version":"6.0","1":"6.0","script_version":"0.80","2":"0.80","version_comment":"- removed the dependency on exuberant ctags which parsed the python source code wrongly anyways. From now on only VIM with python support is needed. This might greatly help windoze users.","3":"- removed the dependency on exuberant ctags which parsed the python source code wrongly anyways. From now on only VIM with python support is needed. This might greatly help windoze users.","package":"pythonhelper.vim","4":"pythonhelper.vim","src_id":"1321","5":"1321","creation_date":"1034928723","6":"1034928723"},{"0":"435","vim_version":"6.0","1":"6.0","script_version":"0.72","2":"0.72","version_comment":"- fixed problem with parsing ctags output on python files that use tabs\r\n- when there is a syntax error in the file and ctags parses it incorrectly a warning is displayed in the command line","3":"- fixed problem with parsing ctags output on python files that use tabs\r\n- when there is a syntax error in the file and ctags parses it incorrectly a warning is displayed in the command line","package":"pythonhelper.vim","4":"pythonhelper.vim","src_id":"1277","5":"1277","creation_date":"1033620467","6":"1033620467"},{"0":"435","vim_version":"6.0","1":"6.0","script_version":"0.71","2":"0.71","version_comment":"- fixed problem with undefined window-bound variable w:PHStatusLine when a window has been split into two.\r\n- unbound event BufWinEnter because it's not needed because of the above change now","3":"- fixed problem with undefined window-bound variable w:PHStatusLine when a window has been split into two.\r\n- unbound event BufWinEnter because it's not needed because of the above change now","package":"pythonhelper.vim","4":"pythonhelper.vim","src_id":"1274","5":"1274","creation_date":"1033539172","6":"1033539172"},{"0":"435","vim_version":"6.0","1":"6.0","script_version":"0.7","2":"0.7","version_comment":"Initial upload","3":"Initial upload","package":"pythonhelper.vim","4":"pythonhelper.vim","src_id":"1273","5":"1273","creation_date":"1033532873","6":"1033532873"}]},"434":{"script_id":"434","0":"434","script_name":"Get UNC Path (Win32)","1":"Get UNC Path (Win32)","script_type":"utility","2":"utility","summary":"Get\/Yank a UNC pathname using 'net share'","3":"Get\/Yank a UNC pathname using 'net share'","description":"The function GetUNCPathOf  tries to find a UNC pathname for a given file by searching the 'net share' list.\r\nIf it fails, it returns the filename it was passed.\r\n\r\nThe map <localleader>yf  yanks the filename into \"*  - the clipboard, for use in emails or browsers.\r\n\r\nUseful for placing filenames into intranet emails.\r\n\r\n\/\/.ichael G.","4":"The function GetUNCPathOf  tries to find a UNC pathname for a given file by searching the 'net share' list.\r\nIf it fails, it returns the filename it was passed.\r\n\r\nThe map <localleader>yf  yanks the filename into \"*  - the clipboard, for use in emails or browsers.\r\n\r\nUseful for placing filenames into intranet emails.\r\n\r\n\/\/.ichael G.","install_details":"Install as a plugin - or source as required","5":"Install as a plugin - or source as required","first_name":"Michael","6":"Michael","last_name":"Geddes","7":"Geddes","releases":[{"0":"434","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"uncpath.vim","4":"uncpath.vim","src_id":"1271","5":"1271","creation_date":"1033522016","6":"1033522016"}]},"433":{"script_id":"433","0":"433","script_name":"Get Win32 Short Name","1":"Get Win32 Short Name","script_type":"utility","2":"utility","summary":"Works out the 8.3 short-name of an existing file","3":"Works out the 8.3 short-name of an existing file","description":"Since writing this, I've discovered heaps about short names.  There are many caveats, but the biggest 3 are:\r\n1) After the first 4 similar names, windows uses a hash algorithm to work out the 3rd-6th letters of the name.\r\n2) Samba uses a different hash algorithm to work out the short name\r\n3) There is a Win32 API function call to set the short name of a file.\r\n\r\nThis script contains a function that works out only simple win32 8.3 short versions of a filename.  It will\r\nwork unless there are more than 4 files with the same name.\r\n\r\nI have since written a patch for Vim6.1 which will allow windows users acces to the short-filename via the api call... expect it soon.. (via fnamemodify and probably using the modifier :8 )\r\n\r\nNOTE: This is part of Vim 6.1 - \r\n     echo fnamemodify( 'c:\\vim\\plugins\\shortname.vim', ':8') \r\n\r\nEg\r\necho GetWin32ShortName('c:\\vim\\plugins\\shortname.vim')\r\n\r\nshould produce:  c:\\vim\\plugins\\shortn~1.vim\r\nor something like that.\r\n\r\n","4":"Since writing this, I've discovered heaps about short names.  There are many caveats, but the biggest 3 are:\r\n1) After the first 4 similar names, windows uses a hash algorithm to work out the 3rd-6th letters of the name.\r\n2) Samba uses a different hash algorithm to work out the short name\r\n3) There is a Win32 API function call to set the short name of a file.\r\n\r\nThis script contains a function that works out only simple win32 8.3 short versions of a filename.  It will\r\nwork unless there are more than 4 files with the same name.\r\n\r\nI have since written a patch for Vim6.1 which will allow windows users acces to the short-filename via the api call... expect it soon.. (via fnamemodify and probably using the modifier :8 )\r\n\r\nNOTE: This is part of Vim 6.1 - \r\n     echo fnamemodify( 'c:\\vim\\plugins\\shortname.vim', ':8') \r\n\r\nEg\r\necho GetWin32ShortName('c:\\vim\\plugins\\shortname.vim')\r\n\r\nshould produce:  c:\\vim\\plugins\\shortn~1.vim\r\nor something like that.\r\n\r\n","install_details":"","5":"","first_name":"Michael","6":"Michael","last_name":"Geddes","7":"Geddes","releases":[{"0":"433","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"shortname.vim","4":"shortname.vim","src_id":"1258","5":"1258","creation_date":"1033332363","6":"1033332363"}]},"432":{"script_id":"432","0":"432","script_name":"biogoo.vim","1":"biogoo.vim","script_type":"color scheme","2":"color scheme","summary":"Colorful text on a light gray background (GUI only)","3":"Colorful text on a light gray background (GUI only)","description":"This script's homepage is https:\/\/github.com\/bdesham\/biogoo. Go there for a full README and a screenshot.\r\n\r\nThis is a bunch of colors that I thought were visually appealing and looked good together.  The background is light shades of gray, and the text is all dark colors.  Note that this color scheme only works in GUI mode (i.e., gvim and not \"terminal vim\").\r\n\r\nI don't really test with syntax files that I don't use.  If you find a situation that looks crappy in biogoo, or if you find something lacking in general, please e-mail me with details and I'll fix the problem :-)","4":"This script's homepage is https:\/\/github.com\/bdesham\/biogoo. Go there for a full README and a screenshot.\r\n\r\nThis is a bunch of colors that I thought were visually appealing and looked good together.  The background is light shades of gray, and the text is all dark colors.  Note that this color scheme only works in GUI mode (i.e., gvim and not \"terminal vim\").\r\n\r\nI don't really test with syntax files that I don't use.  If you find a situation that looks crappy in biogoo, or if you find something lacking in general, please e-mail me with details and I'll fix the problem :-)","install_details":"1.    copy to ~\/.vim\/colors\r\n2.    :color biogoo","5":"1.    copy to ~\/.vim\/colors\r\n2.    :color biogoo","first_name":"Benjamin","6":"Benjamin","last_name":"Esham","7":"Esham","releases":[{"0":"432","vim_version":"6.0","1":"6.0","script_version":"1.6.2","2":"1.6.2","version_comment":"Put the README-type content into a separate file and put everything into a GitHub repository.  (No changes to the color scheme itself.)","3":"Put the README-type content into a separate file and put everything into a GitHub repository.  (No changes to the color scheme itself.)","package":"biogoo.vim","4":"biogoo.vim","src_id":"15137","5":"15137","creation_date":"1298929064","6":"1298929064"},{"0":"432","vim_version":"6.0","1":"6.0","script_version":"1.6.1","2":"1.6.1","version_comment":"Fixed some oversights in 1.6. Version 1.6 swapped the spelling-error color so that setting 'cursorline' or 'cursorcolumn' doesn't make words invisible and added \"ColorColumn\" to support 'colorcolumn' in Vim 7.3.","3":"Fixed some oversights in 1.6. Version 1.6 swapped the spelling-error color so that setting 'cursorline' or 'cursorcolumn' doesn't make words invisible and added \"ColorColumn\" to support 'colorcolumn' in Vim 7.3.","package":"biogoo.vim","4":"biogoo.vim","src_id":"13596","5":"13596","creation_date":"1282000262","6":"1282000262"},{"0":"432","vim_version":"6.0","1":"6.0","script_version":"1.5","2":"1.5","version_comment":"completed support for Vim 7's new highlighting groups","3":"completed support for Vim 7's new highlighting groups","package":"biogoo.vim","4":"biogoo.vim","src_id":"6458","5":"6458","creation_date":"1164106185","6":"1164106185"},{"0":"432","vim_version":"6.0","1":"6.0","script_version":"0.95","2":"0.95","version_comment":"Initial upload","3":"Initial upload","package":"biogoo.vim","4":"biogoo.vim","src_id":"1254","5":"1254","creation_date":"1033245768","6":"1033245768"}]},"431":{"script_id":"431","0":"431","script_name":"VimFootnotes","1":"VimFootnotes","script_type":"utility","2":"utility","summary":"Insert various types of footnotes with Vim.","3":"Insert various types of footnotes with Vim.","description":"Inspired by Emmanuel Touzery tip:\r\n\" http:\/\/vim.sourceforge.net\/tip_view.php?tip_id=332 \r\n\" and discussion below (thanks to Luc for pluginization hints) \r\n\" I added functions and turned it into vim script.\r\n\r\n\r\n\" Commands:\r\n\" <Leader>f (in insert mode) - inserts footnotemark, opens at bottom window where\r\n\"     footnotemark is also inserted and you are ready to type in your\r\n\"     footnotetext.\r\n\" <Leader>r (in insert mode) - closes footnote window and returns to the text in\r\n\"     proper place. \r\n\"\r\n\" You can change them by placing in your vimrc:\r\n\"  imap your_map <Plug>AddVimFootnote\r\n\"  imap your_map <Plug>ReturnFromFootnote\r\n\"\r\n\"\r\n\"    Footnotes are placed at the end of the file but above signature delimiter\r\n\"    (is one exists). \r\n\"\r\n\" Settings:\r\n\" g:vimfootnotetype - possible values:\r\n\" \tarabic (default) - [1] [2] [3] ...\r\n\" \talpha  - [a] [b] ... [z] [aa] [bb] ... [zz] [a] ...\r\n\"   Alpha  - as above but uppercase [A] ...\r\n\"   star   - [*] [**] [***] ...\t\r\n\"\r\n\" Additional commands:\r\n\" FootnoteNumber:\r\n\" \tYou can change current footnote number (one obligatory argument)\r\n\"   :FootnoteNumber 5\t\r\n\" FootnoteNumberRestore:\r\n\"\tYou can restore old footnote number  \r\n\"\t:FootnoteNumberRestore\t\r\n\" FootnoteUndo: \r\n\"\tDecrease footnote counter by 1\r\n\"\t:FootnoteUndo\t \r\n\" FootnoteMeta:\r\n\" \tChange type of the footnotes and restart counter (1, a, A, *)\r\n\" \t:FootnoteMeta\r\n\" \t\tIf your previous footnote type was alpha, Alpha or star new type will\r\n\" \t\tbe arabic.\r\n\" \t\tIf your previous footnote type was arabic new type will be alpha.\r\n\" \t:FootnoteMeta name_of_the_type\r\n\" \t\tChange footnote type to name_of_the_type. If name_of_the_type is the\r\n\" \t\tsame as\tyour current footnote type nothing would be changed.\r\n\" FootnoteRestore:\r\n\" \tRestore previous footnote type and counter. Unfortunately there is no easy\r\n\" \tway to sort footnotes at the end of file without handmade :!sort on marked\r\n\" \tlines (it doesn't work for 'star' type).\r\n\" \t:FootnoteRestore\t\r\n\"\r\n\" For easier work with this commands I would suggest place this lines in your\r\n\" vimrc (they offer very nice competion of Vim commands):\t\r\n\"\tset laststatus=2\r\n\"\tset wildmode=longest,list\r\n\"\tset wildmenu\r\n\"\r\n\" And\/or map :FootnoteComs for something you like.\r\n\"\r\n\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\r\n","4":"Inspired by Emmanuel Touzery tip:\r\n\" http:\/\/vim.sourceforge.net\/tip_view.php?tip_id=332 \r\n\" and discussion below (thanks to Luc for pluginization hints) \r\n\" I added functions and turned it into vim script.\r\n\r\n\r\n\" Commands:\r\n\" <Leader>f (in insert mode) - inserts footnotemark, opens at bottom window where\r\n\"     footnotemark is also inserted and you are ready to type in your\r\n\"     footnotetext.\r\n\" <Leader>r (in insert mode) - closes footnote window and returns to the text in\r\n\"     proper place. \r\n\"\r\n\" You can change them by placing in your vimrc:\r\n\"  imap your_map <Plug>AddVimFootnote\r\n\"  imap your_map <Plug>ReturnFromFootnote\r\n\"\r\n\"\r\n\"    Footnotes are placed at the end of the file but above signature delimiter\r\n\"    (is one exists). \r\n\"\r\n\" Settings:\r\n\" g:vimfootnotetype - possible values:\r\n\" \tarabic (default) - [1] [2] [3] ...\r\n\" \talpha  - [a] [b] ... [z] [aa] [bb] ... [zz] [a] ...\r\n\"   Alpha  - as above but uppercase [A] ...\r\n\"   star   - [*] [**] [***] ...\t\r\n\"\r\n\" Additional commands:\r\n\" FootnoteNumber:\r\n\" \tYou can change current footnote number (one obligatory argument)\r\n\"   :FootnoteNumber 5\t\r\n\" FootnoteNumberRestore:\r\n\"\tYou can restore old footnote number  \r\n\"\t:FootnoteNumberRestore\t\r\n\" FootnoteUndo: \r\n\"\tDecrease footnote counter by 1\r\n\"\t:FootnoteUndo\t \r\n\" FootnoteMeta:\r\n\" \tChange type of the footnotes and restart counter (1, a, A, *)\r\n\" \t:FootnoteMeta\r\n\" \t\tIf your previous footnote type was alpha, Alpha or star new type will\r\n\" \t\tbe arabic.\r\n\" \t\tIf your previous footnote type was arabic new type will be alpha.\r\n\" \t:FootnoteMeta name_of_the_type\r\n\" \t\tChange footnote type to name_of_the_type. If name_of_the_type is the\r\n\" \t\tsame as\tyour current footnote type nothing would be changed.\r\n\" FootnoteRestore:\r\n\" \tRestore previous footnote type and counter. Unfortunately there is no easy\r\n\" \tway to sort footnotes at the end of file without handmade :!sort on marked\r\n\" \tlines (it doesn't work for 'star' type).\r\n\" \t:FootnoteRestore\t\r\n\"\r\n\" For easier work with this commands I would suggest place this lines in your\r\n\" vimrc (they offer very nice competion of Vim commands):\t\r\n\"\tset laststatus=2\r\n\"\tset wildmode=longest,list\r\n\"\tset wildmenu\r\n\"\r\n\" And\/or map :FootnoteComs for something you like.\r\n\"\r\n\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\r\n","install_details":"Installation: Drop it to your plugin directory but you can declare your\r\n\"      favorite types of footnotes in your ftplugins.\r\n","5":"Installation: Drop it to your plugin directory but you can declare your\r\n\"      favorite types of footnotes in your ftplugins.\r\n","first_name":"Mikolaj","6":"Mikolaj","last_name":"Machowski","7":"Machowski","releases":[{"0":"431","vim_version":"6.0","1":"6.0","script_version":"0.5","2":"0.5","version_comment":"Added: roman and Roman counters\r\nFixed: various bugs with :FootnoteCommands","3":"Added: roman and Roman counters\r\nFixed: various bugs with :FootnoteCommands","package":"vimfootnotes.vim","4":"vimfootnotes.vim","src_id":"1263","5":"1263","creation_date":"1033390009","6":"1033390009"},{"0":"431","vim_version":"6.0","1":"6.0","script_version":"0.3","2":"0.3","version_comment":"Initial upload","3":"Initial upload","package":"vimfootnotes.vim","4":"vimfootnotes.vim","src_id":"1251","5":"1251","creation_date":"1033042815","6":"1033042815"}]},"430":{"script_id":"430","0":"430","script_name":"lustre syntax","1":"lustre syntax","script_type":"syntax","2":"syntax","summary":"syntax file for lustre language","3":"syntax file for lustre language","description":"it's very basic but helps!!!","4":"it's very basic but helps!!!","install_details":"","5":"","first_name":"odyss","6":"odyss","last_name":"sofronis","7":"sofronis","releases":[{"0":"430","vim_version":"6.0","1":"6.0","script_version":"0.83","2":"0.83","version_comment":"some more matchings , in comments and tel (with out \".\" in the end)","3":"some more matchings , in comments and tel (with out \".\" in the end)","package":"lustre.vim","4":"lustre.vim","src_id":"1337","5":"1337","creation_date":"1035537745","6":"1035537745"},{"0":"430","vim_version":"6.0","1":"6.0","script_version":"0.82","2":"0.82","version_comment":"a bit better...","3":"a bit better...","package":"lustre.vim","4":"lustre.vim","src_id":"1259","5":"1259","creation_date":"1033352032","6":"1033352032"},{"0":"430","vim_version":"6.0","1":"6.0","script_version":"0.81","2":"0.81","version_comment":"added some statement recognition","3":"added some statement recognition","package":"lustre.vim","4":"lustre.vim","src_id":"1247","5":"1247","creation_date":"1032938054","6":"1032938054"},{"0":"430","vim_version":"5.7","1":"5.7","script_version":"0.8","2":"0.8","version_comment":"Initial upload","3":"Initial upload","package":"lustre.vim","4":"lustre.vim","src_id":"1246","5":"1246","creation_date":"1032935925","6":"1032935925"}]},"429":{"script_id":"429","0":"429","script_name":"lustre","1":"lustre","script_type":"ftplugin","2":"ftplugin","summary":"compiles and runs a lustre program","3":"compiles and runs a lustre program","description":"this script compiles and runs a lustre program \r\nthere are 2 maps that hace been;\r\n<m-c>    compile \r\n<m-r>     run\r\nto run it u must first compile it succesfully...run does not make compilation\r\n\r\nfor each case the action is for the current node and for that the file must be of the format \r\nnode nodename","4":"this script compiles and runs a lustre program \r\nthere are 2 maps that hace been;\r\n<m-c>    compile \r\n<m-r>     run\r\nto run it u must first compile it succesfully...run does not make compilation\r\n\r\nfor each case the action is for the current node and for that the file must be of the format \r\nnode nodename","install_details":"put it in the ftplugins directory...\r\n\r\nprobably u'll need a file \"filetype.vim\"\r\ncontaining the below (for the recognision of the lustre file type)\r\n\r\nfiletype.vim:\r\n\r\n\" Lustre file\r\naugroup filetypedetect\r\n  au! BufRead,BufNewFile *.lus  setfiletype lustre\r\naugroup END\r\n\r\n\r\n\r\n","5":"put it in the ftplugins directory...\r\n\r\nprobably u'll need a file \"filetype.vim\"\r\ncontaining the below (for the recognision of the lustre file type)\r\n\r\nfiletype.vim:\r\n\r\n\" Lustre file\r\naugroup filetypedetect\r\n  au! BufRead,BufNewFile *.lus  setfiletype lustre\r\naugroup END\r\n\r\n\r\n\r\n","first_name":"odyss","6":"odyss","last_name":"sofronis","7":"sofronis","releases":[{"0":"429","vim_version":"6.0","1":"6.0","script_version":"0.41","2":"0.41","version_comment":"     ","3":"     ","package":"lustre.vim","4":"lustre.vim","src_id":"1272","5":"1272","creation_date":"1033526137","6":"1033526137"},{"0":"429","vim_version":"5.7","1":"5.7","script_version":"0.3","2":"0.3","version_comment":"Initial upload","3":"Initial upload","package":"Lustre.vim","4":"Lustre.vim","src_id":"1245","5":"1245","creation_date":"1032935756","6":"1032935756"}]},"428":{"script_id":"428","0":"428","script_name":"smlisp.vim","1":"smlisp.vim","script_type":"syntax","2":"syntax","summary":"syntax file for Small Lisp","3":"syntax file for Small Lisp","description":"smlisp.vim provides syntax highlighting and paranthesis\/bracket matching for the Small Lisp languague. The main web site is http:\/\/www.cs.sfu.ca\/~cameron\/smlisp\/\r\n(which provides the original MSDOS binaries).\r\n\r\nFor the Linux distribution check the primary location\r\nhttp:\/\/www.uv.es\/~tung\/smlisp\/.","4":"smlisp.vim provides syntax highlighting and paranthesis\/bracket matching for the Small Lisp languague. The main web site is http:\/\/www.cs.sfu.ca\/~cameron\/smlisp\/\r\n(which provides the original MSDOS binaries).\r\n\r\nFor the Linux distribution check the primary location\r\nhttp:\/\/www.uv.es\/~tung\/smlisp\/.","install_details":"Load smlisp.vim with \":source smlisp.vim\". Be sure to start with syntax off as there might be a conflict with the Slang syntax. (Once smlisp.vim is incorporated in the main Vim distribution, there will hopefully be an automatic file type detection.)","5":"Load smlisp.vim with \":source smlisp.vim\". Be sure to start with syntax off as there might be a conflict with the Slang syntax. (Once smlisp.vim is incorporated in the main Vim distribution, there will hopefully be an automatic file type detection.)","first_name":"Michael M.","6":"Michael M.","last_name":"Tung","7":"Tung","releases":[{"0":"428","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"smlisp.vim","4":"smlisp.vim","src_id":"1244","5":"1244","creation_date":"1032874228","6":"1032874228"}]},"424":{"script_id":"424","0":"424","script_name":"midnight2.vim","1":"midnight2.vim","script_type":"color scheme","2":"color scheme","summary":"Dark blue, low contrast colorscheme.","3":"Dark blue, low contrast colorscheme.","description":"Midnight is a colorscheme with a dark blue background and light blue foreground.  It is designed to keep contrast at a minimum.  It is the same as midnight.vim (vimscript #253).  I will attempt to keep both up to date with the same version of the colorscheme.","4":"Midnight is a colorscheme with a dark blue background and light blue foreground.  It is designed to keep contrast at a minimum.  It is the same as midnight.vim (vimscript #253).  I will attempt to keep both up to date with the same version of the colorscheme.","install_details":"Download and place in ~\/.vim\/colors.  Then type \":color midnight2\".  I also highly recommend you place \"color midnight2\" in your ~\/.vimrc.  :)","5":"Download and place in ~\/.vim\/colors.  Then type \":color midnight2\".  I also highly recommend you place \"color midnight2\" in your ~\/.vimrc.  :)","first_name":"Michael","6":"Michael","last_name":"Brailsford","7":"Brailsford","releases":[{"0":"424","vim_version":"6.0","1":"6.0","script_version":"2.5","2":"2.5","version_comment":"Added vimdiff coloring.  The previous vimdiff coloring was hideous.","3":"Added vimdiff coloring.  The previous vimdiff coloring was hideous.","package":"midnight2.vim","4":"midnight2.vim","src_id":"6500","5":"6500","creation_date":"1165302742","6":"1165302742"},{"0":"424","vim_version":"7.0","1":"7.0","script_version":"2.0","2":"2.0","version_comment":"This includes some modifications suggested by Mark Lodato.  This is an update for vim7.  Thanks Mark! ","3":"This includes some modifications suggested by Mark Lodato.  This is an update for vim7.  Thanks Mark! ","package":"midnight2.vim","4":"midnight2.vim","src_id":"5943","5":"5943","creation_date":"1152689527","6":"1152689527"},{"0":"424","vim_version":"6.0","1":"6.0","script_version":"0.8","2":"0.8","version_comment":"Initial upload","3":"Initial upload","package":"midnight2.vim","4":"midnight2.vim","src_id":"1238","5":"1238","creation_date":"1032808198","6":"1032808198"}]},"423":{"script_id":"423","0":"423","script_name":"jcl.vim","1":"jcl.vim","script_type":"utility","2":"utility","summary":"IBM Mainframe JCL language syntax","3":"IBM Mainframe JCL language syntax","description":"Mainframe JCL language.\r\nEnphasize Conditional parts of jcl\r\nImplements common used keywords and commands.\r\n\r\n","4":"Mainframe JCL language.\r\nEnphasize Conditional parts of jcl\r\nImplements common used keywords and commands.\r\n\r\n","install_details":"","5":"","first_name":"zanotti","6":"zanotti","last_name":"fiorenzo","7":"fiorenzo","releases":[{"0":"423","vim_version":"6.0","1":"6.0","script_version":"2.0","2":"2.0","version_comment":"More keyword handled; improved conditional highligthning.\r\n","3":"More keyword handled; improved conditional highligthning.\r\n","package":"jcl.vim","4":"jcl.vim","src_id":"2500","5":"2500","creation_date":"1069297436","6":"1069297436"}]},"422":{"script_id":"422","0":"422","script_name":"eukleides.vim","1":"eukleides.vim","script_type":"syntax","2":"syntax","summary":"Syntax file for eukleides language","3":"Syntax file for eukleides language","description":"This is a syntax file for the eukleides language.  Eukleides is a language for drawing Euclidean geometrical diagrams.  It is available at http:\/\/perso.wanadoo.fr\/obrecht\/index.html","4":"This is a syntax file for the eukleides language.  Eukleides is a language for drawing Euclidean geometrical diagrams.  It is available at http:\/\/perso.wanadoo.fr\/obrecht\/index.html","install_details":"Just drop into your syntax directory, and associate files with extension .euk.","5":"Just drop into your syntax directory, and associate files with extension .euk.","first_name":"Robert","6":"Robert","last_name":"Goulding","7":"Goulding","releases":[{"0":"422","vim_version":"6.0","1":"6.0","script_version":"0.3","2":"0.3","version_comment":"Initial upload","3":"Initial upload","package":"eukleides.vim","4":"eukleides.vim","src_id":"1227","5":"1227","creation_date":"1032594501","6":"1032594501"}]},"421":{"script_id":"421","0":"421","script_name":"elinks.vim","1":"elinks.vim","script_type":"syntax","2":"syntax","summary":"Syntax file for elinks.conf","3":"Syntax file for elinks.conf","description":"Syntax highlighting of elinks' configuration file. Covers elink version 0.4pre15 or later.\r\nThe elinks project homepage: http:\/\/elinks.or.cz","4":"Syntax highlighting of elinks' configuration file. Covers elink version 0.4pre15 or later.\r\nThe elinks project homepage: http:\/\/elinks.or.cz","install_details":"Put it in the syntax folder of either ~\/.vim or $VIMRUNTIME and add:\r\n        au! BufNewFile,BufRead elinks.conf setfiletype elinks\r\nto filetype.vim the same place.","5":"Put it in the syntax folder of either ~\/.vim or $VIMRUNTIME and add:\r\n        au! BufNewFile,BufRead elinks.conf setfiletype elinks\r\nto filetype.vim the same place.","first_name":"Jonas","6":"Jonas","last_name":"Fonseca","7":"Fonseca","releases":[{"0":"421","vim_version":"6.0","1":"6.0","script_version":"1.1","2":"1.1","version_comment":"Keywords updated for version 0.4.1 and 0.5pre0","3":"Keywords updated for version 0.4.1 and 0.5pre0","package":"elinks.vim","4":"elinks.vim","src_id":"1645","5":"1645","creation_date":"1042904766","6":"1042904766"},{"0":"421","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"elinks.vim","4":"elinks.vim","src_id":"1226","5":"1226","creation_date":"1032514038","6":"1032514038"}]},"420":{"script_id":"420","0":"420","script_name":"MySQL script runner","1":"MySQL script runner","script_type":"utility","2":"utility","summary":"MySQL scripts that allows you to run SQL scripts in mysql console by pressing F9","3":"MySQL scripts that allows you to run SQL scripts in mysql console by pressing F9","description":"MySQL scripts that allows you to run SQL scripts in mysql console by pressing F9.\r\n\r\nYou can add this plugin to handle *.SQL file type.","4":"MySQL scripts that allows you to run SQL scripts in mysql console by pressing F9.\r\n\r\nYou can add this plugin to handle *.SQL file type.","install_details":"autocmd! BufRead,BufNewFile *.sql ru macros\/mysql.vim","5":"autocmd! BufRead,BufNewFile *.sql ru macros\/mysql.vim","first_name":"Lukas","6":"Lukas","last_name":"Zapletal","7":"Zapletal","releases":[{"0":"420","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"mysql.vim","4":"mysql.vim","src_id":"1220","5":"1220","creation_date":"1032316505","6":"1032316505"}]},"419":{"script_id":"419","0":"419","script_name":"syslog syntax file","1":"syslog syntax file","script_type":"syntax","2":"syntax","summary":"Adds syntax color to log files created by sysklogd.","3":"Adds syntax color to log files created by sysklogd.","description":"Adds syntax color to log files created by sysklogd.  ","4":"Adds syntax color to log files created by sysklogd.  ","install_details":"You probably want to add a line to your filetype.vim to automatically recognize files as being generated by syslog:\r\n\r\naugroup filetypedetect\r\n  au! BufRead,BufNewFile \/var\/log\/syslog\/*\tset filetype=syslog\r\naugroup END\r\n\r\nOf course, your log directory will vary.","5":"You probably want to add a line to your filetype.vim to automatically recognize files as being generated by syslog:\r\n\r\naugroup filetypedetect\r\n  au! BufRead,BufNewFile \/var\/log\/syslog\/*\tset filetype=syslog\r\naugroup END\r\n\r\nOf course, your log directory will vary.","first_name":"Bob","6":"Bob","last_name":"Hiestand","7":"Hiestand","releases":[{"0":"419","vim_version":"6.0","1":"6.0","script_version":"1.1","2":"1.1","version_comment":"Initial upload","3":"Initial upload","package":"syslog.vim","4":"syslog.vim","src_id":"1215","5":"1215","creation_date":"1032253951","6":"1032253951"}]},"418":{"script_id":"418","0":"418","script_name":"Registryedit (win32)","1":"Registryedit (win32)","script_type":"ftplugin","2":"ftplugin","summary":"Edit the win32 registry through vim.","3":"Edit the win32 registry through vim.","description":"This plugin allows you to edit the Win32 registry through Vim.\r\n\r\nIt was originally conceived after someone on the Vim Mailing list wanted to know how to extend Vim with Perl. Being the bright spark that I am I helpfully pointed out that it wasn't a case of learning how to extend Vim, but knowing how to use Perl to do something that Vim could not. This rules out many uses of Perl - you wouldn't process a CGI request or a log file within Vim. To balance the things you wouldn't do I came up with some suggestions as to things you might want to do. One of those was to make use of Vim's autocmds so you could access the Win32 registry. The original poster then said they'd like to see it done - out of curiousity than out of a challenge, but ever one to open my mouth wide I decided to put my money where my mouth was and this script was born.\r\n\r\nQuite simply this plugin extends Vim via Perl to enable Vim access to the data in the Win32 registry. You access it using the ever popular URL notation of protocol:\/\/file\r\n\r\n  registry:\/\/HKEY_CLASSES_ROOT\/.vim\r\n\r\nFrom there on autocmds catch the request and hand it onto the functions RegistryRead() and RegistryWrite(). Inside both of these its all Perl work using the Win32::TieRegistry module by Tye McQueen to read and write (yes, write) to the registry.\r\n\r\nIt is not a full implementation of Win32::TieRegistry. It just extracts the data, places it in Vim and then updates the registry when you save. It is intended for demonstration purposes (and my own learning) so it is not a stateful reflection of the registry. For example to add a line you just add it and hit save. To delete an entry, you don't just delete the line, you need to mark it with XX. This was intentional to prevent anyone from saving a blank file and then wondering why its all broken. I may change this in a future release if anyone *really* wants me to.\r\n\r\nHowever its mainly for learning purposes and since this is getting long already, please see the readme file for details.","4":"This plugin allows you to edit the Win32 registry through Vim.\r\n\r\nIt was originally conceived after someone on the Vim Mailing list wanted to know how to extend Vim with Perl. Being the bright spark that I am I helpfully pointed out that it wasn't a case of learning how to extend Vim, but knowing how to use Perl to do something that Vim could not. This rules out many uses of Perl - you wouldn't process a CGI request or a log file within Vim. To balance the things you wouldn't do I came up with some suggestions as to things you might want to do. One of those was to make use of Vim's autocmds so you could access the Win32 registry. The original poster then said they'd like to see it done - out of curiousity than out of a challenge, but ever one to open my mouth wide I decided to put my money where my mouth was and this script was born.\r\n\r\nQuite simply this plugin extends Vim via Perl to enable Vim access to the data in the Win32 registry. You access it using the ever popular URL notation of protocol:\/\/file\r\n\r\n  registry:\/\/HKEY_CLASSES_ROOT\/.vim\r\n\r\nFrom there on autocmds catch the request and hand it onto the functions RegistryRead() and RegistryWrite(). Inside both of these its all Perl work using the Win32::TieRegistry module by Tye McQueen to read and write (yes, write) to the registry.\r\n\r\nIt is not a full implementation of Win32::TieRegistry. It just extracts the data, places it in Vim and then updates the registry when you save. It is intended for demonstration purposes (and my own learning) so it is not a stateful reflection of the registry. For example to add a line you just add it and hit save. To delete an entry, you don't just delete the line, you need to mark it with XX. This was intentional to prevent anyone from saving a blank file and then wondering why its all broken. I may change this in a future release if anyone *really* wants me to.\r\n\r\nHowever its mainly for learning purposes and since this is getting long already, please see the readme file for details.","install_details":"Copy the registryedit.vim to the ftplugins directory and update your filetypes.vim as detailed in the readme file.","5":"Copy the registryedit.vim to the ftplugins directory and update your filetypes.vim as detailed in the readme file.","first_name":"Colin","6":"Colin","last_name":"Keith","7":"Keith","releases":[{"0":"418","vim_version":"6.0","1":"6.0","script_version":"1","2":"1","version_comment":"Initial upload","3":"Initial upload","package":"registryedit.zip","4":"registryedit.zip","src_id":"1213","5":"1213","creation_date":"1032212610","6":"1032212610"}]},"417":{"script_id":"417","0":"417","script_name":"plsql.vim","1":"plsql.vim","script_type":"syntax","2":"syntax","summary":"PL\/SQL syntax file","3":"PL\/SQL syntax file","description":"Extension of Austin Ziegler's PL\/SQL syntax file, created primarily to incorporate some of the new Oracle9i keywords.","4":"Extension of Austin Ziegler's PL\/SQL syntax file, created primarily to incorporate some of the new Oracle9i keywords.","install_details":"Put in the \"syntax\" subdirectory.","5":"Put in the \"syntax\" subdirectory.","first_name":"b","6":"b","last_name":"pribyl","7":"pribyl","releases":[{"0":"417","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"plsql.vim","4":"plsql.vim","src_id":"1212","5":"1212","creation_date":"1032186294","6":"1032186294"}]},"416":{"script_id":"416","0":"416","script_name":"Kent Vim Extensions","1":"Kent Vim Extensions","script_type":"utility","2":"utility","summary":"Entering folds and other stuff","3":"Entering folds and other stuff","description":"The purpose of these extensions is to make the use of Vim easier, especially for programming tasks, while preserving the extraordinary features of Vim, which make\r\nit (imho) one of the best editors available.\r\n\r\nThe main part, and probably of most interest for you, is the possibility to enter folds. Entering a fold means to hide everything apart from the fold, so that only the fold you have entered is visible. Thus, you will be able to organise your files much better, and to find and edit certain parts of your files much easier and faster. Especially for long source code files, this is very useful.\r\n\r\nThere are also a lot of other features, please check out the help on that by typing\r\n\r\n:help kent\r\n\r\nafter installation.\r\n\r\nNote: These extensions are tested for Vim version 6.1 onwards. No guarantees for lower versions!\r\n\r\nThere are the following parts:\r\n\r\nKent Folding Extensions:\r\nExtensions to improve the look and feel of folds.\r\nEspecially the possibility to enter folds, inspired by the old origami editor, is very useful.\r\n\r\nImprovements to the Look and Feel of Vim and GVim:\r\nThe purpose is to make it easier to use Vim, especially for users without a lot of Vim experience.\r\n\r\nKent Programming Extensions:\r\nExtensions useful for programming tasks.\r\nFor example commenting out parts of the code depending on the language.\r\n\r\nKent occam Extensions:\r\nExtensions related to the occam language.\r\nContains syntax and indent files for occam, as well as an easy way to compile, debug and run occam programs.","4":"The purpose of these extensions is to make the use of Vim easier, especially for programming tasks, while preserving the extraordinary features of Vim, which make\r\nit (imho) one of the best editors available.\r\n\r\nThe main part, and probably of most interest for you, is the possibility to enter folds. Entering a fold means to hide everything apart from the fold, so that only the fold you have entered is visible. Thus, you will be able to organise your files much better, and to find and edit certain parts of your files much easier and faster. Especially for long source code files, this is very useful.\r\n\r\nThere are also a lot of other features, please check out the help on that by typing\r\n\r\n:help kent\r\n\r\nafter installation.\r\n\r\nNote: These extensions are tested for Vim version 6.1 onwards. No guarantees for lower versions!\r\n\r\nThere are the following parts:\r\n\r\nKent Folding Extensions:\r\nExtensions to improve the look and feel of folds.\r\nEspecially the possibility to enter folds, inspired by the old origami editor, is very useful.\r\n\r\nImprovements to the Look and Feel of Vim and GVim:\r\nThe purpose is to make it easier to use Vim, especially for users without a lot of Vim experience.\r\n\r\nKent Programming Extensions:\r\nExtensions useful for programming tasks.\r\nFor example commenting out parts of the code depending on the language.\r\n\r\nKent occam Extensions:\r\nExtensions related to the occam language.\r\nContains syntax and indent files for occam, as well as an easy way to compile, debug and run occam programs.","install_details":"Please go to the Kent Vim Extensions website and follow the instructions.","5":"Please go to the Kent Vim Extensions website and follow the instructions.","first_name":"Mario","6":"Mario","last_name":"Schweigler","7":"Schweigler","releases":[{"0":"416","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"See file for details.","3":"See file for details.","package":"install.txt","4":"install.txt","src_id":"3005","5":"3005","creation_date":"1084018879","6":"1084018879"}]},"415":{"script_id":"415","0":"415","script_name":"Zenburn","1":"Zenburn","script_type":"color scheme","2":"color scheme","summary":"Low contrast colour scheme for low light conditions","3":"Low contrast colour scheme for low light conditions","description":"This colour scheme is intended to be pleasant for the eyes when working in low-light conditions. The low contrast will reduce eyestrain.\r\n\r\nIf you like to work in a darkened room with a fullscreen Vim, this is for you! Even if you don't, try this one out :-)\r\n\r\nThere is now a higher-contrast mode (with darker background) which is enabled via \":let g:zenburn_high_Contrast=1\" then \":colors zenburn\". See the syntax file itself for further options.\r\n\r\nZenburn official site: http:\/\/slinky.imukuppi.org\/zenburnpage\/\r\nZenburn screenshot: http:\/\/slinky.imukuppi.org\/zenburn\/","4":"This colour scheme is intended to be pleasant for the eyes when working in low-light conditions. The low contrast will reduce eyestrain.\r\n\r\nIf you like to work in a darkened room with a fullscreen Vim, this is for you! Even if you don't, try this one out :-)\r\n\r\nThere is now a higher-contrast mode (with darker background) which is enabled via \":let g:zenburn_high_Contrast=1\" then \":colors zenburn\". See the syntax file itself for further options.\r\n\r\nZenburn official site: http:\/\/slinky.imukuppi.org\/zenburnpage\/\r\nZenburn screenshot: http:\/\/slinky.imukuppi.org\/zenburn\/","install_details":"Copy the file to ~\/.vim\/colors and :colorscheme zenburn.","5":"Copy the file to ~\/.vim\/colors and :colorscheme zenburn.","first_name":"Jani","6":"Jani","last_name":"Nurminen","7":"Nurminen","releases":[{"0":"415","vim_version":"7.0","1":"7.0","script_version":"2.21","2":"2.21","version_comment":"Vimball version of v2.21","3":"Vimball version of v2.21","package":"zenburn.vba","4":"zenburn.vba","src_id":"15531","5":"15531","creation_date":"1303820713","6":"1303820713"},{"0":"415","vim_version":"7.0","1":"7.0","script_version":"2.21","2":"2.21","version_comment":"Folded, FoldColumn and TabLine color fixes by Pawel Piekarski.","3":"Folded, FoldColumn and TabLine color fixes by Pawel Piekarski.","package":"zenburn.vim","4":"zenburn.vim","src_id":"15530","5":"15530","creation_date":"1303820694","6":"1303820694"},{"0":"415","vim_version":"7.0","1":"7.0","script_version":"2.19","2":"2.19","version_comment":"Vimball version","3":"Vimball version","package":"zenburn.vba","4":"zenburn.vba","src_id":"15463","5":"15463","creation_date":"1303035490","6":"1303035490"},{"0":"415","vim_version":"7.0","1":"7.0","script_version":"2.19","2":"2.19","version_comment":"Changes:\r\n* Clayton Parker: LineNr bugfix, fix directory styles\r\n* Christophe-Marie Duquesne: suggested support for ctags_highlighting by Al Budden (http:\/\/sites.google.com\/site\/abudden\/contents\/Vim-Scripts\/ctags-highlighting). Experimental support is now in and will be enabled if you have the plugin. If you want to disable it manually, let g:zenburn_disable_ctags_highlighting_support = 1. More help is needed with the ctags_highlighting.\r\n* New darker Visual is now the default. It doesn't stick out now and fits the overall colourscheme better, including with LineNr. Using the old-style Visual is still possible: let g:zenburn_old_Visual = 1.\r\n\r\nAs usual, please see the Zenburn.vim for more details!","3":"Changes:\r\n* Clayton Parker: LineNr bugfix, fix directory styles\r\n* Christophe-Marie Duquesne: suggested support for ctags_highlighting by Al Budden (http:\/\/sites.google.com\/site\/abudden\/contents\/Vim-Scripts\/ctags-highlighting). Experimental support is now in and will be enabled if you have the plugin. If you want to disable it manually, let g:zenburn_disable_ctags_highlighting_support = 1. More help is needed with the ctags_highlighting.\r\n* New darker Visual is now the default. It doesn't stick out now and fits the overall colourscheme better, including with LineNr. Using the old-style Visual is still possible: let g:zenburn_old_Visual = 1.\r\n\r\nAs usual, please see the Zenburn.vim for more details!","package":"zenburn.vim","4":"zenburn.vim","src_id":"15462","5":"15462","creation_date":"1303035461","6":"1303035461"},{"0":"415","vim_version":"7.0","1":"7.0","script_version":"2.16","2":"2.16","version_comment":"Vimball version of v2.16","3":"Vimball version of v2.16","package":"zenburn.vba","4":"zenburn.vba","src_id":"14111","5":"14111","creation_date":"1287944258","6":"1287944258"},{"0":"415","vim_version":"7.0","1":"7.0","script_version":"2.16","2":"2.16","version_comment":"* The licensing is clarified: latest GPL applies. Thanks to Martin Langasek.\r\n* Support for autocompletion of configuration parameters, thanks to Marcin Szamotulski.\r\n* CursorColumn and CursorLine colour improvements. A new configuration parameter has been added for this, please see the Zenburn.vim file. Thanks to Andrew Wagner.","3":"* The licensing is clarified: latest GPL applies. Thanks to Martin Langasek.\r\n* Support for autocompletion of configuration parameters, thanks to Marcin Szamotulski.\r\n* CursorColumn and CursorLine colour improvements. A new configuration parameter has been added for this, please see the Zenburn.vim file. Thanks to Andrew Wagner.","package":"zenburn.vim","4":"zenburn.vim","src_id":"14110","5":"14110","creation_date":"1287944227","6":"1287944227"},{"0":"415","vim_version":"7.0","1":"7.0","script_version":"v2.14","2":"v2.14","version_comment":"Vimball version of v2.14","3":"Vimball version of v2.14","package":"zenburn.vba","4":"zenburn.vba","src_id":"14053","5":"14053","creation_date":"1287002347","6":"1287002347"},{"0":"415","vim_version":"7.0","1":"7.0","script_version":"2.14","2":"2.14","version_comment":"CursorColumn guifg was unintentionally set, colourizing all columns with same foreground. Thanks to Drew.","3":"CursorColumn guifg was unintentionally set, colourizing all columns with same foreground. Thanks to Drew.","package":"zenburn.vim","4":"zenburn.vim","src_id":"14052","5":"14052","creation_date":"1287001929","6":"1287001929"},{"0":"415","vim_version":"7.0","1":"7.0","script_version":"2.13","2":"2.13","version_comment":"Vimball version of v2.13","3":"Vimball version of v2.13","package":"zenburn.vba","4":"zenburn.vba","src_id":"11578","5":"11578","creation_date":"1256379953","6":"1256379953"},{"0":"415","vim_version":"7.0","1":"7.0","script_version":"2.13","2":"2.13","version_comment":"Terminal fixes (Ignore-group, NonText-group, Error-group)\r\nUI fixes (Ignore-group, Error-group)\r\nFix for invisible NonText-group\r\n","3":"Terminal fixes (Ignore-group, NonText-group, Error-group)\r\nUI fixes (Ignore-group, Error-group)\r\nFix for invisible NonText-group\r\n","package":"zenburn.vim","4":"zenburn.vim","src_id":"11576","5":"11576","creation_date":"1256379681","6":"1256379681"},{"0":"415","vim_version":"7.0","1":"7.0","script_version":"2.5","2":"2.5","version_comment":"Toggleable colorize for Ignore-groups. Makes Vim help files look nicer.","3":"Toggleable colorize for Ignore-groups. Makes Vim help files look nicer.","package":"zenburn.vim","4":"zenburn.vim","src_id":"11332","5":"11332","creation_date":"1252228357","6":"1252228357"},{"0":"415","vim_version":"7.0","1":"7.0","script_version":"2.4","2":"2.4","version_comment":"256-color syntax fixes (Spellchecker, PMenu). Toggle for forcing dark background (Tim Smith).","3":"256-color syntax fixes (Spellchecker, PMenu). Toggle for forcing dark background (Tim Smith).","package":"zenburn.vim","4":"zenburn.vim","src_id":"9518","5":"9518","creation_date":"1227041201","6":"1227041201"},{"0":"415","vim_version":"7.0","1":"7.0","script_version":"2.3","2":"2.3","version_comment":"CursorLine fix for 256-color mode by Pablo Castellazzi","3":"CursorLine fix for 256-color mode by Pablo Castellazzi","package":"zenburn.vim","4":"zenburn.vim","src_id":"9046","5":"9046","creation_date":"1217414119","6":"1217414119"},{"0":"415","vim_version":"7.0","1":"7.0","script_version":"2.2","2":"2.2","version_comment":"Many fixes and enhancements.","3":"Many fixes and enhancements.","package":"zenburn.vim","4":"zenburn.vim","src_id":"8921","5":"8921","creation_date":"1215695345","6":"1215695345"},{"0":"415","vim_version":"6.0","1":"6.0","script_version":"1.15","2":"1.15","version_comment":"High\/low contrast toggle, 256-color terminal support by Kurt Maier. Other minor coloring fixes.","3":"High\/low contrast toggle, 256-color terminal support by Kurt Maier. Other minor coloring fixes.","package":"zenburn.vim","4":"zenburn.vim","src_id":"6149","5":"6149","creation_date":"1157622038","6":"1157622038"},{"0":"415","vim_version":"6.0","1":"6.0","script_version":"1.13","2":"1.13","version_comment":"Some fixes: Duller colouring of Include (configurable). Wildmenu is now consistent with the overall colour scheme. More contrasted Visual (configurable), as proposed by the Cream people. Now there are also a couple configuration parameters (e.g. to use the old brighter orange with Include syntax group). Also, the script is now \"officially\" GPL ..it sort of always has been anyway without explicitly mentioning it :-).\r\n\r\nPlease look at inside the file for the configuration parameters.","3":"Some fixes: Duller colouring of Include (configurable). Wildmenu is now consistent with the overall colour scheme. More contrasted Visual (configurable), as proposed by the Cream people. Now there are also a couple configuration parameters (e.g. to use the old brighter orange with Include syntax group). Also, the script is now \"officially\" GPL ..it sort of always has been anyway without explicitly mentioning it :-).\r\n\r\nPlease look at inside the file for the configuration parameters.","package":"zenburn.vim","4":"zenburn.vim","src_id":"1211","5":"1211","creation_date":"1032174410","6":"1032174410"},{"0":"415","vim_version":"6.0","1":"6.0","script_version":"1.11","2":"1.11","version_comment":"Some fixes and fine-tuning. Exceptions and Perl code now looks more consistent.","3":"Some fixes and fine-tuning. Exceptions and Perl code now looks more consistent.","package":"zenburn.vim","4":"zenburn.vim","src_id":"1210","5":"1210","creation_date":"1032099238","6":"1032099238"},{"0":"415","vim_version":"6.0","1":"6.0","script_version":"1.10","2":"1.10","version_comment":"Initial upload","3":"Initial upload","package":"zenburn.vim","4":"zenburn.vim","src_id":"1208","5":"1208","creation_date":"1031998743","6":"1031998743"}]},"414":{"script_id":"414","0":"414","script_name":"plsql.vim","1":"plsql.vim","script_type":"indent","2":"indent","summary":"PL\/SQL indent file","3":"PL\/SQL indent file","description":"An Oracle PL\/SQL indent file that indents after BEGIN IF AS IS THEN WHEN LOOP ELSE ELSIF CASE EXCEPTION and DECLARE, and unindents after the corresponding end of these statements\/sections.","4":"An Oracle PL\/SQL indent file that indents after BEGIN IF AS IS THEN WHEN LOOP ELSE ELSIF CASE EXCEPTION and DECLARE, and unindents after the corresponding end of these statements\/sections.","install_details":"1. Put in indent\/ subdirectory.\r\n2. You may want \"runtime! indent.vim\" in .vimrc.","5":"1. Put in indent\/ subdirectory.\r\n2. You may want \"runtime! indent.vim\" in .vimrc.","first_name":"b","6":"b","last_name":"pribyl","7":"pribyl","releases":[{"0":"414","vim_version":"6.0","1":"6.0","script_version":"1.3.1.1","2":"1.3.1.1","version_comment":"quick fix to problem of IS in SQL statements; fixed unindent of inline subprograms; identified new TODO regarding nested blocks in exception handlers","3":"quick fix to problem of IS in SQL statements; fixed unindent of inline subprograms; identified new TODO regarding nested blocks in exception handlers","package":"plsql.vim","4":"plsql.vim","src_id":"1235","5":"1235","creation_date":"1032771498","6":"1032771498"},{"0":"414","vim_version":"6.0","1":"6.0","script_version":"1.2","2":"1.2","version_comment":"Corrected a problem with WHEN clauses in exception handlers.  Also added support for CASE statements.  Changed version # here to match my RCS version #. Added TODO section.","3":"Corrected a problem with WHEN clauses in exception handlers.  Also added support for CASE statements.  Changed version # here to match my RCS version #. Added TODO section.","package":"plsql.vim","4":"plsql.vim","src_id":"1216","5":"1216","creation_date":"1032259717","6":"1032259717"},{"0":"414","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"plsql.vim","4":"plsql.vim","src_id":"1207","5":"1207","creation_date":"1031822101","6":"1031822101"}]},"413":{"script_id":"413","0":"413","script_name":"ActionScript","1":"ActionScript","script_type":"syntax","2":"syntax","summary":"ActionScript syntax highligting","3":"ActionScript syntax highligting","description":"what to say?","4":"what to say?","install_details":"ActionScript files usually end with \".as\" but it is associated with Atlas in filetype.vim. You should remove this association and create a new one for ActionScript ... ","5":"ActionScript files usually end with \".as\" but it is associated with Atlas in filetype.vim. You should remove this association and create a new one for ActionScript ... ","first_name":"Igor","6":"Igor","last_name":"Dvorsky","7":"Dvorsky","releases":[{"0":"413","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"actionscript.vim","4":"actionscript.vim","src_id":"1205","5":"1205","creation_date":"1031817453","6":"1031817453"}]},"412":{"script_id":"412","0":"412","script_name":"cvopsefsa.vim","1":"cvopsefsa.vim","script_type":"syntax","2":"syntax","summary":"CVOPS EFSA language syntax file","3":"CVOPS EFSA language syntax file","description":"Syntax highlighting for the state automaton language files (.aut) used inside Celtius CVOPS.","4":"Syntax highlighting for the state automaton language files (.aut) used inside Celtius CVOPS.","install_details":"Copy the cvopsefsa.vim to ~\/.vim\/syntax directory. To enable, put something like \nthis e.g. in ~\/.vimrc\n \nautocmd BufNewFile,BufRead *.aut    set syntax=cvopsefsa\n\nSee also :help new-filetype.\n","5":"Copy the cvopsefsa.vim to ~\/.vim\/syntax directory. To enable, put something like \nthis e.g. in ~\/.vimrc\n \nautocmd BufNewFile,BufRead *.aut    set syntax=cvopsefsa\n\nSee also :help new-filetype.\n","first_name":"Jani","6":"Jani","last_name":"Nurminen","7":"Nurminen","releases":[{"0":"412","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"cvopsefsa.vim","4":"cvopsefsa.vim","src_id":"1204","5":"1204","creation_date":"1031796746","6":"1031796746"}]},"411":{"script_id":"411","0":"411","script_name":"tex.vim","1":"tex.vim","script_type":"ftplugin","2":"ftplugin","summary":"an updated version of the standard ftplugin\/tex.vim","3":"an updated version of the standard ftplugin\/tex.vim","description":"     This is an updated version of the file ftplugin\/tex.vim included in the\r\nstandard vim distribution.  It sets options appropriately for editing TeX\r\n(especially LaTeX) files.  It is fairly conservative:  it may not do everything\r\nyou want, but it will probably not do anything to annoy you.\r\n\r\n     This will set the buffer-local variable b:tex_flavor to \"tex\" (for plain TeX)\r\n or \"latex\".  Other mappings, plugins, etc. may use this variable to modify\r\ntheir behavior.","4":"     This is an updated version of the file ftplugin\/tex.vim included in the\r\nstandard vim distribution.  It sets options appropriately for editing TeX\r\n(especially LaTeX) files.  It is fairly conservative:  it may not do everything\r\nyou want, but it will probably not do anything to annoy you.\r\n\r\n     This will set the buffer-local variable b:tex_flavor to \"tex\" (for plain TeX)\r\n or \"latex\".  Other mappings, plugins, etc. may use this variable to modify\r\ntheir behavior.","install_details":"Copy the file to $VIMRUNTIME\/ftplugin\/tex.vim .\r\nYou probably do not want to have this in your local ftplugin\/ directory,\r\nsince you may get an even more recent version when you upgrade to\r\na new version of vim.","5":"Copy the file to $VIMRUNTIME\/ftplugin\/tex.vim .\r\nYou probably do not want to have this in your local ftplugin\/ directory,\r\nsince you may get an even more recent version when you upgrade to\r\na new version of vim.","first_name":"Benji","6":"Benji","last_name":"Fisher","7":"Fisher","releases":[{"0":"411","vim_version":"6.0","1":"6.0","script_version":"1.2","2":"1.2","version_comment":"Improve the 'includeexpr' option setting for systems where \"{\" and \"}\" are included in 'isfname'.  (Ajit Thakkar)\r\n\r\nThis version should be included in the vim 6.3 distribution.","3":"Improve the 'includeexpr' option setting for systems where \"{\" and \"}\" are included in 'isfname'.  (Ajit Thakkar)\r\n\r\nThis version should be included in the vim 6.3 distribution.","package":"tex.vim","4":"tex.vim","src_id":"3016","5":"3016","creation_date":"1084350288","6":"1084350288"},{"0":"411","vim_version":"6.0","1":"6.0","script_version":"1.1.1","2":"1.1.1","version_comment":"Oops.  I commented out the \"finish\" line for testing, then forgot to un-comment it.","3":"Oops.  I commented out the \"finish\" line for testing, then forgot to un-comment it.","package":"tex.vim","4":"tex.vim","src_id":"2637","5":"2637","creation_date":"1072796622","6":"1072796622"},{"0":"411","vim_version":"6.0","1":"6.0","script_version":"1.1","2":"1.1","version_comment":"I fixed some typos so that the 'define' option works better with plain TeX.","3":"I fixed some typos so that the 'define' option works better with plain TeX.","package":"tex.vim","4":"tex.vim","src_id":"2636","5":"2636","creation_date":"1072791973","6":"1072791973"},{"0":"411","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"tex.vim","4":"tex.vim","src_id":"1198","5":"1198","creation_date":"1031489163","6":"1031489163"}]},"410":{"script_id":"410","0":"410","script_name":"muf.vim","1":"muf.vim","script_type":"syntax","2":"syntax","summary":"Syntax hilites and indenting for the MUF language","3":"Syntax hilites and indenting for the MUF language","description":"This contains both syntax hiliting and smart indent scripts for the MUF programming language.  MUF is the Multi-User Forth language used with several Muck server variations.","4":"This contains both syntax hiliting and smart indent scripts for the MUF programming language.  MUF is the Multi-User Forth language used with several Muck server variations.","install_details":"Unpack in your \/usr\/share\/vim directory, and apply the filetype.vim.diff patch.","5":"Unpack in your \/usr\/share\/vim directory, and apply the filetype.vim.diff patch.","first_name":"Revar","6":"Revar","last_name":"Desmera","7":"Desmera","releases":[{"0":"410","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"mufvim.tar.gz","4":"mufvim.tar.gz","src_id":"1196","5":"1196","creation_date":"1031367168","6":"1031367168"}]},"409":{"script_id":"409","0":"409","script_name":"svn.vim","1":"svn.vim","script_type":"syntax","2":"syntax","summary":"Subversion commits syntax highlight (like CVS)","3":"Subversion commits syntax highlight (like CVS)","description":"Simple syntax highlight when commiting a file with Subversion (SVN). \r\nThis is based on CVS version.","4":"Simple syntax highlight when commiting a file with Subversion (SVN). \r\nThis is based on CVS version.","install_details":"Just copy it to syntax directory (home or system wide).","5":"Just copy it to syntax directory (home or system wide).","first_name":"Leandro","6":"Leandro","last_name":"Lucarella","7":"Lucarella","releases":[{"0":"409","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"svn.vim","4":"svn.vim","src_id":"1192","5":"1192","creation_date":"1031296594","6":"1031296594"}]},"408":{"script_id":"408","0":"408","script_name":"beanshell.vim","1":"beanshell.vim","script_type":"utility","2":"utility","summary":"Runs the current buffer using BeanShell.","3":"Runs the current buffer using BeanShell.","description":"This script invokes BeanShell ( see http:\/\/www.beanshell.org ) on the contents of the current buffer.\r\n\r\nThe script depends on java (needed to run BeanShell) as well as BeanShell itself.  The java executable should be in your PATH and the BeanShell jar should be in your CLASSPATH in order to use this script in its default configuration.\r\n\r\nPress \"<Leader>br\" and BeanShell will be invoked on the contents of the current buffer (the current buffer will not be written out).  The output from BeanShell will appear in a new window.\r\n\r\nBeanShell may also be invoked by entering the command \":BeanShell\" or by selecting the \"Invoke BeanShell\" item from the \"Plugin\" menu.\r\n\r\nStarting with version 1.2, a range may be supplied to the \"BeanShell\" command and the key command may be activated within a visual block.  Invoking BeanShell this way will cause it to act upon the specified lines rather than the entire buffer.","4":"This script invokes BeanShell ( see http:\/\/www.beanshell.org ) on the contents of the current buffer.\r\n\r\nThe script depends on java (needed to run BeanShell) as well as BeanShell itself.  The java executable should be in your PATH and the BeanShell jar should be in your CLASSPATH in order to use this script in its default configuration.\r\n\r\nPress \"<Leader>br\" and BeanShell will be invoked on the contents of the current buffer (the current buffer will not be written out).  The output from BeanShell will appear in a new window.\r\n\r\nBeanShell may also be invoked by entering the command \":BeanShell\" or by selecting the \"Invoke BeanShell\" item from the \"Plugin\" menu.\r\n\r\nStarting with version 1.2, a range may be supplied to the \"BeanShell\" command and the key command may be activated within a visual block.  Invoking BeanShell this way will cause it to act upon the specified lines rather than the entire buffer.","install_details":"Either drop beanshell.vim into your plugins directory or :source it as needed.\r\n\r\nThe command to execute BeanShell may be configured by setting the variable \"BeanShell_Cmd\".  This defaults to \"java bsh.Interpreter\", but may be set to anything so you can (for example) forego having java in your path and specify it in this variable.\r\n\r\nThe key command to invoke BeanShell may be configured by mapping some key to <Plug>BeanShell.  For example, to have Shift-F3 invoke BeanShell, enter the command \":map <S-F3> <Plug>BeanShell\" (or place this command in your vimrc).","5":"Either drop beanshell.vim into your plugins directory or :source it as needed.\r\n\r\nThe command to execute BeanShell may be configured by setting the variable \"BeanShell_Cmd\".  This defaults to \"java bsh.Interpreter\", but may be set to anything so you can (for example) forego having java in your path and specify it in this variable.\r\n\r\nThe key command to invoke BeanShell may be configured by mapping some key to <Plug>BeanShell.  For example, to have Shift-F3 invoke BeanShell, enter the command \":map <S-F3> <Plug>BeanShell\" (or place this command in your vimrc).","first_name":"Henry","6":"Henry","last_name":"So, Jr.","7":"So, Jr.","releases":[{"0":"408","vim_version":"6.0","1":"6.0","script_version":"1.2","2":"1.2","version_comment":"Added support for a range on the \"BeanShell\" command and for a visual block on the key command.","3":"Added support for a range on the \"BeanShell\" command and for a visual block on the key command.","package":"beanshell.vim","4":"beanshell.vim","src_id":"5740","5":"5740","creation_date":"1148222908","6":"1148222908"},{"0":"408","vim_version":"6.0","1":"6.0","script_version":"1.1","2":"1.1","version_comment":"Brought the script more in-line with the suggestions in section 41.9 of the VIM User Manual (:help write-plugin).","3":"Brought the script more in-line with the suggestions in section 41.9 of the VIM User Manual (:help write-plugin).","package":"beanshell.vim","4":"beanshell.vim","src_id":"1195","5":"1195","creation_date":"1031342496","6":"1031342496"},{"0":"408","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"beanshell.vim","4":"beanshell.vim","src_id":"1191","5":"1191","creation_date":"1031257401","6":"1031257401"}]},"407":{"script_id":"407","0":"407","script_name":"CVSAnnotate.vim","1":"CVSAnnotate.vim","script_type":"syntax","2":"syntax","summary":"Simple syntax file for use with the cvscommand.vim plugin.","3":"Simple syntax file for use with the cvscommand.vim plugin.","description":"This syntax file provides syntax definitions for buffers created by the cvscommand.vim plugin (version 1.10 and above).","4":"This syntax file provides syntax definitions for buffers created by the cvscommand.vim plugin (version 1.10 and above).","install_details":"Just place in your syntax directory.","5":"Just place in your syntax directory.","first_name":"Bob","6":"Bob","last_name":"Hiestand","7":"Hiestand","releases":[{"0":"407","vim_version":"6.0","1":"6.0","script_version":"1.3","2":"1.3","version_comment":"Initial upload","3":"Initial upload","package":"CVSAnnotate.vim","4":"CVSAnnotate.vim","src_id":"1189","5":"1189","creation_date":"1031147255","6":"1031147255"}]},"406":{"script_id":"406","0":"406","script_name":"blackdust.vim","1":"blackdust.vim","script_type":"color scheme","2":"color scheme","summary":"darkish colour scheme, inverse of whitedust","3":"darkish colour scheme, inverse of whitedust","description":"I inverted whitedust.vim (vimscript #348) by hand, then decided that was a complete waste of time, and wrote vimscript #405 to do automatic inversions for me :)\r\nIn any case, here is blackdust, the inverse of whitedust.","4":"I inverted whitedust.vim (vimscript #348) by hand, then decided that was a complete waste of time, and wrote vimscript #405 to do automatic inversions for me :)\r\nIn any case, here is blackdust, the inverse of whitedust.","install_details":"drop it into your ~\/.vim\/colors\/ directory, complain to Bram that he can't spell \"colour\" in english ;)","5":"drop it into your ~\/.vim\/colors\/ directory, complain to Bram that he can't spell \"colour\" in english ;)","first_name":"Matthew","6":"Matthew","last_name":"Hawkins","7":"Hawkins","releases":[{"0":"406","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"blackdust.vim","4":"blackdust.vim","src_id":"1186","5":"1186","creation_date":"1031055923","6":"1031055923"}]},"405":{"script_id":"405","0":"405","script_name":"colour_flip.pl","1":"colour_flip.pl","script_type":"utility","2":"utility","summary":"perl script to inverse colourscheme colours","3":"perl script to inverse colourscheme colours","description":"Ever held visual bell on and thought \"gee, that doesn't look too bad?\" then spent hours inverting your colourscheme by hand to make a new one?\r\nWell, stop wasting time.  Just pipe the colourscheme through this here funky perl script, and save the output as your new scheme.  It takes a whole 0.035 seconds to run on a 433Mhz Celeron.  This amounts to a considerable (~102857) amount of time saving!\r\nIt will recognise both RGB and system colour names and do its best to invert them.\r\nNOTE: it will break on colourscheme files where the highlight commands span multiple lines.  Maybe I'll fix that someday, but then again maybe not.  Feel free to upload a new version which does that.","4":"Ever held visual bell on and thought \"gee, that doesn't look too bad?\" then spent hours inverting your colourscheme by hand to make a new one?\r\nWell, stop wasting time.  Just pipe the colourscheme through this here funky perl script, and save the output as your new scheme.  It takes a whole 0.035 seconds to run on a 433Mhz Celeron.  This amounts to a considerable (~102857) amount of time saving!\r\nIt will recognise both RGB and system colour names and do its best to invert them.\r\nNOTE: it will break on colourscheme files where the highlight commands span multiple lines.  Maybe I'll fix that someday, but then again maybe not.  Feel free to upload a new version which does that.","install_details":"save it, edit it to your liking, run it through your perl interpreter.  I don't use any weird-arse CPAN modules so you don't need anything else.","5":"save it, edit it to your liking, run it through your perl interpreter.  I don't use any weird-arse CPAN modules so you don't need anything else.","first_name":"Matthew","6":"Matthew","last_name":"Hawkins","7":"Hawkins","releases":[{"0":"405","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"colour_flip.pl","4":"colour_flip.pl","src_id":"1185","5":"1185","creation_date":"1031054849","6":"1031054849"}]},"404":{"script_id":"404","0":"404","script_name":"getmail.vim","1":"getmail.vim","script_type":"syntax","2":"syntax","summary":"Syntax file for getmailrc","3":"Syntax file for getmailrc","description":"A syntax file for getmail (a fetchmail replacement written in Python). Based on samba.vim.\r\n\r\ngetmail homepage: http:\/\/pyropus.ca\/software\/getmail\/","4":"A syntax file for getmail (a fetchmail replacement written in Python). Based on samba.vim.\r\n\r\ngetmail homepage: http:\/\/pyropus.ca\/software\/getmail\/","install_details":"drop it in your $HOME\/.vim\/syntax directory","5":"drop it in your $HOME\/.vim\/syntax directory","first_name":"Nikolai","6":"Nikolai","last_name":"Nespor","7":"Nespor","releases":[{"0":"404","vim_version":"6.0","1":"6.0","script_version":"0.4","2":"0.4","version_comment":"Update syntax to getmail version 4.x.","3":"Update syntax to getmail version 4.x.","package":"getmailrc.vim","4":"getmailrc.vim","src_id":"3894","5":"3894","creation_date":"1109050709","6":"1109050709"},{"0":"404","vim_version":"6.0","1":"6.0","script_version":"0.3.1","2":"0.3.1","version_comment":"Added new config option \"command_add_fromline\". Exists in getmail from version 3.1.8 onwards.","3":"Added new config option \"command_add_fromline\". Exists in getmail from version 3.1.8 onwards.","package":"getmail.vim","4":"getmail.vim","src_id":"2295","5":"2295","creation_date":"1062643339","6":"1062643339"},{"0":"404","vim_version":"6.0","1":"6.0","script_version":"0.3","2":"0.3","version_comment":"Updated syntax for getmail version 3.1.0","3":"Updated syntax for getmail version 3.1.0","package":"getmail.vim","4":"getmail.vim","src_id":"1761","5":"1761","creation_date":"1046001499","6":"1046001499"},{"0":"404","vim_version":"6.0","1":"6.0","script_version":"0.2","2":"0.2","version_comment":"Fixed a typo","3":"Fixed a typo","package":"getmail.vim","4":"getmail.vim","src_id":"1231","5":"1231","creation_date":"1032738346","6":"1032738346"},{"0":"404","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"getmail.vim","4":"getmail.vim","src_id":"1184","5":"1184","creation_date":"1031044943","6":"1031044943"}]},"403":{"script_id":"403","0":"403","script_name":"eruby.vim","1":"eruby.vim","script_type":"syntax","2":"syntax","summary":"Highlight eruby code blocks within html.","3":"Highlight eruby code blocks within html.","description":"This script properly highlights <% ... %>, <%=...%>, and <%#...%> as ruby code within html.","4":"This script properly highlights <% ... %>, <%=...%>, and <%#...%> as ruby code within html.","install_details":"Save the file eruby.vim to your ~\/.vim\/syntax directory and add a line in your ~\/.vimrc or in ~\/.vim\/filetype.vim to load this syntax file for all *.rhtm and *.rhtml files.","5":"Save the file eruby.vim to your ~\/.vim\/syntax directory and add a line in your ~\/.vimrc or in ~\/.vim\/filetype.vim to load this syntax file for all *.rhtm and *.rhtml files.","first_name":"Michael","6":"Michael","last_name":"Brailsford","7":"Brailsford","releases":[{"0":"403","vim_version":"6.0","1":"6.0","script_version":"2.0","2":"2.0","version_comment":"Fix to correctly highlight eruby tags within html tags.  Also added comments with instructions to install .rhtml as a new filetype.  Removed the ~\/.vim\/filetype.vim file from the package.","3":"Fix to correctly highlight eruby tags within html tags.  Also added comments with instructions to install .rhtml as a new filetype.  Removed the ~\/.vim\/filetype.vim file from the package.","package":"eruby.vim","4":"eruby.vim","src_id":"1505","5":"1505","creation_date":"1038532707","6":"1038532707"},{"0":"403","vim_version":"6.0","1":"6.0","script_version":"1.5","2":"1.5","version_comment":"Fixed the highlighting of blocks that are broken up by html.  Fixed the highlighting of case \r\nstatements.   Included the html ftplugins, so that indenting and all the other nice html ftplugins\r\nwork.  Thanks to Tim Bates for pointing these out.\r\n","3":"Fixed the highlighting of blocks that are broken up by html.  Fixed the highlighting of case \r\nstatements.   Included the html ftplugins, so that indenting and all the other nice html ftplugins\r\nwork.  Thanks to Tim Bates for pointing these out.\r\n","package":"eruby.tar.gz","4":"eruby.tar.gz","src_id":"1456","5":"1456","creation_date":"1037998247","6":"1037998247"},{"0":"403","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"eruby_vim.tar.gz","4":"eruby_vim.tar.gz","src_id":"1180","5":"1180","creation_date":"1030865822","6":"1030865822"}]},"402":{"script_id":"402","0":"402","script_name":"colormenu.vim","1":"colormenu.vim","script_type":"utility","2":"utility","summary":"Menu showing all available color schemes","3":"Menu showing all available color schemes","description":"A simple plugin that adds a menu with all color schemes in the runtime path.  Selecting an item from the menu activates that color scheme.","4":"A simple plugin that adds a menu with all color schemes in the runtime path.  Selecting an item from the menu activates that color scheme.","install_details":"Drop the file in the plugins directory somwhere in the runtime path","5":"Drop the file in the plugins directory somwhere in the runtime path","first_name":"Geoff","6":"Geoff","last_name":"Reedy","7":"Reedy","releases":[{"0":"402","vim_version":"6.0","1":"6.0","script_version":"20020829","2":"20020829","version_comment":"Initial upload","3":"Initial upload","package":"colormenu.vim","4":"colormenu.vim","src_id":"1177","5":"1177","creation_date":"1030635897","6":"1030635897"}]},"401":{"script_id":"401","0":"401","script_name":"regRedir.vim","1":"regRedir.vim","script_type":"utility","2":"utility","summary":"Vim plugin to redirect command output into a register","3":"Vim plugin to redirect command output into a register","description":"\" Description: This plugin defines a 'Redir' command that takes a register\r\n\" and one or more {bar} separated commands. This command will execute \r\n\" these commands and collect their output into the specified register.\r\n\" The resulting register could than be inserted anywhere with a :put\r\n\" The register must always be specified, and is the first character \r\n\" of the command argument. The remainder of the argument is the command\r\n\" to be captured. This command may be separated from the register with \r\n\" a space. Several commands can be specified, but have to be separated\r\n\" with a bar:\r\n\"\r\n\" :Redir {reg} {cmd} [ | {cmd} [ | {cmd} ... ] ]\r\n\" \r\n\" Examples:\r\n\" 1) Simple case of one command (e.g. :version) to be captured into \r\n\"    register v\r\n\"\t    :Redir vversion\r\n\"\t or\r\n\"\t    :Redir v version\r\n\" 2) Example of two commands (ls and set) to be collected into \r\n\"\t register p\r\n\"\t    :Redir p ls | set\r\n\"\t or\r\n\"\t    :Redir pls|set\r\n\" 3) Example of a command (g\/exe) to be appended to register x\r\n\"\t    :Redir Xg\/exe\r\n\"\t or\r\n\"\t    :Redir X g\/exe\r\n\"\r\n","4":"\" Description: This plugin defines a 'Redir' command that takes a register\r\n\" and one or more {bar} separated commands. This command will execute \r\n\" these commands and collect their output into the specified register.\r\n\" The resulting register could than be inserted anywhere with a :put\r\n\" The register must always be specified, and is the first character \r\n\" of the command argument. The remainder of the argument is the command\r\n\" to be captured. This command may be separated from the register with \r\n\" a space. Several commands can be specified, but have to be separated\r\n\" with a bar:\r\n\"\r\n\" :Redir {reg} {cmd} [ | {cmd} [ | {cmd} ... ] ]\r\n\" \r\n\" Examples:\r\n\" 1) Simple case of one command (e.g. :version) to be captured into \r\n\"    register v\r\n\"\t    :Redir vversion\r\n\"\t or\r\n\"\t    :Redir v version\r\n\" 2) Example of two commands (ls and set) to be collected into \r\n\"\t register p\r\n\"\t    :Redir p ls | set\r\n\"\t or\r\n\"\t    :Redir pls|set\r\n\" 3) Example of a command (g\/exe) to be appended to register x\r\n\"\t    :Redir Xg\/exe\r\n\"\t or\r\n\"\t    :Redir X g\/exe\r\n\"\r\n","install_details":"\" Installation: Just unzip and copy this file into your ~\/vim\/plugin \r\n\"\t\tor corresponding directory\r\n","5":"\" Installation: Just unzip and copy this file into your ~\/vim\/plugin \r\n\"\t\tor corresponding directory\r\n","first_name":"Guido","6":"Guido","last_name":"Van Hoecke","7":"Van Hoecke","releases":[{"0":"401","vim_version":"6.0","1":"6.0","script_version":"1","2":"1","version_comment":"Initial upload","3":"Initial upload","package":"regRedir.zip","4":"regRedir.zip","src_id":"1176","5":"1176","creation_date":"1030634427","6":"1030634427"}]},"400":{"script_id":"400","0":"400","script_name":"sean.vim","1":"sean.vim","script_type":"color scheme","2":"color scheme","summary":"dark color scheme","3":"dark color scheme","description":"Nice colours on a black background, mainly set up for C++ but seem sto be OK on most file types.","4":"Nice colours on a black background, mainly set up for C++ but seem sto be OK on most file types.","install_details":"Drop it in $vim\/vimfiles\/colors and add \"colorscheme sean.vim\" to your vimrc","5":"Drop it in $vim\/vimfiles\/colors and add \"colorscheme sean.vim\" to your vimrc","first_name":"Sean","6":"Sean","last_name":"Richards","7":"Richards","releases":[{"0":"400","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"sean.vim","4":"sean.vim","src_id":"1175","5":"1175","creation_date":"1030629650","6":"1030629650"}]},"399":{"script_id":"399","0":"399","script_name":"ironman.vim","1":"ironman.vim","script_type":"color scheme","2":"color scheme","summary":"Color scheme with bright background","3":"Color scheme with bright background","description":"Color scheme with bright background to work hours and hours in front of the monitor.\r\nHow it looks? http:\/\/1drv.ms\/1GttLx3\r\n\r\nFor GUI only.","4":"Color scheme with bright background to work hours and hours in front of the monitor.\r\nHow it looks? http:\/\/1drv.ms\/1GttLx3\r\n\r\nFor GUI only.","install_details":"Drop it in $vim\/vimfiles\/colors and add \"colorscheme ironman.vim\" to your vimrc","5":"Drop it in $vim\/vimfiles\/colors and add \"colorscheme ironman.vim\" to your vimrc","first_name":"Michael","6":"Michael","last_name":"Boehler","7":"Boehler","releases":[{"0":"399","vim_version":"7.0","1":"7.0","script_version":"3.3","2":"3.3","version_comment":"some small modifications","3":"some small modifications","package":"ironman.vim","4":"ironman.vim","src_id":"22951","5":"22951","creation_date":"1424865350","6":"1424865350"},{"0":"399","vim_version":"7.0","1":"7.0","script_version":"3.2","2":"3.2","version_comment":"some small modifications (inspired by colorsheme PYTE thanks Henning)","3":"some small modifications (inspired by colorsheme PYTE thanks Henning)","package":"ironman.vim","4":"ironman.vim","src_id":"8317","5":"8317","creation_date":"1203559971","6":"1203559971"}]},"398":{"script_id":"398","0":"398","script_name":"maxima.vim","1":"maxima.vim","script_type":"syntax","2":"syntax","summary":"syntax file for the Maxima language","3":"syntax file for the Maxima language","description":"This is a vim syntax file for the Maxima programming language. Maxima (based on GNU Common Lisp) is a GNU licensed system for doing computer algebra. It is an outgrowth of MIT's original Macsyma implementation.","4":"This is a vim syntax file for the Maxima programming language. Maxima (based on GNU Common Lisp) is a GNU licensed system for doing computer algebra. It is an outgrowth of MIT's original Macsyma implementation.","install_details":"","5":"","first_name":"Michael M.","6":"Michael M.","last_name":"Tung","7":"Tung","releases":[{"0":"398","vim_version":"6.0","1":"6.0","script_version":"0.2","2":"0.2","version_comment":"now includes coloring for float decimals in scientific notation","3":"now includes coloring for float decimals in scientific notation","package":"maxima.vim","4":"maxima.vim","src_id":"1179","5":"1179","creation_date":"1030681040","6":"1030681040"},{"0":"398","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"maxima.vim","4":"maxima.vim","src_id":"1163","5":"1163","creation_date":"1030339948","6":"1030339948"}]},"397":{"script_id":"397","0":"397","script_name":"ShowFunc.vim","1":"ShowFunc.vim","script_type":"utility","2":"utility","summary":"Creates a list of all tags \/ functions from a window, all windows or buffers.","3":"Creates a list of all tags \/ functions from a window, all windows or buffers.","description":"This script creates a hyperlink list of all the tags (i.e. functions, subroutines, classes, macros or procedures) from a single buffer, all open windows or buffers and displays them in a dynamically sized cwindow.\r\n\r\nSupported File types with Exuberant Ctags version 5.5.4 (and newer):  Asm, Asp, Awk, Beta, C, C++, c#, Cobol, Eiffel, Erlang, Fortran, Java, Javascript, Lisp, Lua, Make, Pascal, Perl, PHP, Python, PL\/SQL,  REXX, Ruby, Scheme, Shell, SLang, SML, SQL, Tcl, Vera, Verilog, Vim, YACC......and any user defined (i.e. --regex-lang=) types. \r\n\r\nDefault Key Mappings:\r\n<F1>    Run scan and open cwindow.\r\n              \r\nTo reassign add the following to your .vimrc:\r\n      map  NewKey   <Plug>ShowFunc\r\n      map! NewKey   <Plug>ShowFunc\r\nFor example to change the <F1> mapping to <F7>\r\n      map  <F7>   <Plug>ShowFunc\r\n      map! <F7>   <Plug>ShowFunc\r\n\r\nShowFunc Window commands:\r\nc       Close cwindow.\r\nh       Display help dialog.\r\nr        Refresh.\r\ns       Change file sort, results will appear in either alphabetical or file order.  (Default: file order)\r\nt       Change scan type, results will be from either the current file, all open windows or all open buffers.  (Default: all open buffers)","4":"This script creates a hyperlink list of all the tags (i.e. functions, subroutines, classes, macros or procedures) from a single buffer, all open windows or buffers and displays them in a dynamically sized cwindow.\r\n\r\nSupported File types with Exuberant Ctags version 5.5.4 (and newer):  Asm, Asp, Awk, Beta, C, C++, c#, Cobol, Eiffel, Erlang, Fortran, Java, Javascript, Lisp, Lua, Make, Pascal, Perl, PHP, Python, PL\/SQL,  REXX, Ruby, Scheme, Shell, SLang, SML, SQL, Tcl, Vera, Verilog, Vim, YACC......and any user defined (i.e. --regex-lang=) types. \r\n\r\nDefault Key Mappings:\r\n<F1>    Run scan and open cwindow.\r\n              \r\nTo reassign add the following to your .vimrc:\r\n      map  NewKey   <Plug>ShowFunc\r\n      map! NewKey   <Plug>ShowFunc\r\nFor example to change the <F1> mapping to <F7>\r\n      map  <F7>   <Plug>ShowFunc\r\n      map! <F7>   <Plug>ShowFunc\r\n\r\nShowFunc Window commands:\r\nc       Close cwindow.\r\nh       Display help dialog.\r\nr        Refresh.\r\ns       Change file sort, results will appear in either alphabetical or file order.  (Default: file order)\r\nt       Change scan type, results will be from either the current file, all open windows or all open buffers.  (Default: all open buffers)","install_details":"Put this file in the vim plugins directory (~\/.vim\/plugin\/) to load it automatically, or load it with :so ShowFunc.vim.\r\n\r\nYou need Exuberant CTags installed for this function to work.\r\nWebsite: http:\/\/ctags.sourceforge.net\/\r\nDebian: apt-get install exuberant-ctags\r\n\r\nHistory:\r\nThis script grew from an idea posted by Flemming Madsen on vimtip #79.","5":"Put this file in the vim plugins directory (~\/.vim\/plugin\/) to load it automatically, or load it with :so ShowFunc.vim.\r\n\r\nYou need Exuberant CTags installed for this function to work.\r\nWebsite: http:\/\/ctags.sourceforge.net\/\r\nDebian: apt-get install exuberant-ctags\r\n\r\nHistory:\r\nThis script grew from an idea posted by Flemming Madsen on vimtip #79.","first_name":"Dave","6":"Dave","last_name":"Vehrs","7":"Vehrs","releases":[{"0":"397","vim_version":"7.0","1":"7.0","script_version":"1.5.9","2":"1.5.9","version_comment":"Improved grepformat string.  Set so that F1 toggles the ShowFunc cwindow as suggested by Halkeye on the Vim Tips  Wiki.  Tested bug reported by Dtyall, unable to replicate in the version I use, which already has the fixes suggested.  Sorry I didn't release those sooner.","3":"Improved grepformat string.  Set so that F1 toggles the ShowFunc cwindow as suggested by Halkeye on the Vim Tips  Wiki.  Tested bug reported by Dtyall, unable to replicate in the version I use, which already has the fixes suggested.  Sorry I didn't release those sooner.","package":"ShowFunc.vim","4":"ShowFunc.vim","src_id":"19558","5":"19558","creation_date":"1361469591","6":"1361469591"},{"0":"397","vim_version":"7.0","1":"7.0","script_version":"1.5.8","2":"1.5.8","version_comment":"Fixed a C++ file type error thanks to a report from Gynvael Coldwind.","3":"Fixed a C++ file type error thanks to a report from Gynvael Coldwind.","package":"ShowFunc.vim","4":"ShowFunc.vim","src_id":"11071","5":"11071","creation_date":"1248723748","6":"1248723748"},{"0":"397","vim_version":"6.0","1":"6.0","script_version":"1.5.7","2":"1.5.7","version_comment":"Per request by Diederik Van der Boor, added ability to filter the variables kinds that ctags outputs (ver 5.5 or newer).","3":"Per request by Diederik Van der Boor, added ability to filter the variables kinds that ctags outputs (ver 5.5 or newer).","package":"ShowFunc.vim","4":"ShowFunc.vim","src_id":"5491","5":"5491","creation_date":"1143558165","6":"1143558165"},{"0":"397","vim_version":"6.0","1":"6.0","script_version":"1.5.6","2":"1.5.6","version_comment":"First Vim 7 patches.  Added setlocal statusline support to update the cwindow name.","3":"First Vim 7 patches.  Added setlocal statusline support to update the cwindow name.","package":"ShowFunc.vim","4":"ShowFunc.vim","src_id":"5341","5":"5341","creation_date":"1141123907","6":"1141123907"},{"0":"397","vim_version":"6.0","1":"6.0","script_version":"1.5.5","2":"1.5.5","version_comment":"Patches from two Windows users (David Rennalls and Bill McCarthy).  Fixes in cleanup, documentaion, and autocmds.","3":"Patches from two Windows users (David Rennalls and Bill McCarthy).  Fixes in cleanup, documentaion, and autocmds.","package":"ShowFunc.vim","4":"ShowFunc.vim","src_id":"4440","5":"4440","creation_date":"1121861295","6":"1121861295"},{"0":"397","vim_version":"6.0","1":"6.0","script_version":"1.5.4","2":"1.5.4","version_comment":"Script cleanup.  Added MyLastWindow function (when closing windows, tests last window to see if its a Cwindow, if it is then close vim session). ","3":"Script cleanup.  Added MyLastWindow function (when closing windows, tests last window to see if its a Cwindow, if it is then close vim session). ","package":"ShowFunc.vim","4":"ShowFunc.vim","src_id":"3762","5":"3762","creation_date":"1105615982","6":"1105615982"},{"0":"397","vim_version":"6.0","1":"6.0","script_version":"1.5.3","2":"1.5.3","version_comment":"Fixed custom fold text for cwindow.","3":"Fixed custom fold text for cwindow.","package":"ShowFunc.vim","4":"ShowFunc.vim","src_id":"3548","5":"3548","creation_date":"1097852103","6":"1097852103"},{"0":"397","vim_version":"6.0","1":"6.0","script_version":"1.5.2","2":"1.5.2","version_comment":"Improved Exuberant Ctags version checking.","3":"Improved Exuberant Ctags version checking.","package":"ShowFunc.vim","4":"ShowFunc.vim","src_id":"2376","5":"2376","creation_date":"1065476142","6":"1065476142"},{"0":"397","vim_version":"6.0","1":"6.0","script_version":"1.5.1","2":"1.5.1","version_comment":"Bug fixes","3":"Bug fixes","package":"ShowFunc.vim","4":"ShowFunc.vim","src_id":"2352","5":"2352","creation_date":"1064425365","6":"1064425365"},{"0":"397","vim_version":"6.0","1":"6.0","script_version":"1.5","2":"1.5","version_comment":"Created a more generic grep format so that explicit type definitions are no longer necessary (eliminating the SetGrepFormat function).  Modified the SetGrepPrg function to detect Ctags versions earlier than 5.5.  Supportted filetypes for Ctags versions 5.4 are statically assigned.  With Ctags versions 5.5 (and later) supported filetypes are detected dynamically (including those defined by regular expressions (--regex-<LANG>).\r\n","3":"Created a more generic grep format so that explicit type definitions are no longer necessary (eliminating the SetGrepFormat function).  Modified the SetGrepPrg function to detect Ctags versions earlier than 5.5.  Supportted filetypes for Ctags versions 5.4 are statically assigned.  With Ctags versions 5.5 (and later) supported filetypes are detected dynamically (including those defined by regular expressions (--regex-<LANG>).\r\n","package":"ShowFunc.vim","4":"ShowFunc.vim","src_id":"2343","5":"2343","creation_date":"1064141740","6":"1064141740"},{"0":"397","vim_version":"6.0","1":"6.0","script_version":"1.4.5","2":"1.4.5","version_comment":"More error handling improvements, including tests for the correct version of ctags, and keymap assignment.  Thanks to Mark Thomas for his assistance in finding and fixing a bug in the executable detection on Windows.  ","3":"More error handling improvements, including tests for the correct version of ctags, and keymap assignment.  Thanks to Mark Thomas for his assistance in finding and fixing a bug in the executable detection on Windows.  ","package":"ShowFunc.vim","4":"ShowFunc.vim","src_id":"1883","5":"1883","creation_date":"1049204133","6":"1049204133"},{"0":"397","vim_version":"6.0","1":"6.0","script_version":"1.4.4","2":"1.4.4","version_comment":"Improved error handling.  Improved SetFoldText().","3":"Improved error handling.  Improved SetFoldText().","package":"ShowFunc.vim","4":"ShowFunc.vim","src_id":"1819","5":"1819","creation_date":"1047933401","6":"1047933401"},{"0":"397","vim_version":"6.0","1":"6.0","script_version":"1.4.3","2":"1.4.3","version_comment":"Automatically fold output on filename for multiple file scans (all buffers or windows).   \n","3":"Automatically fold output on filename for multiple file scans (all buffers or windows).   \n","package":"ShowFunc.vim","4":"ShowFunc.vim","src_id":"1814","5":"1814","creation_date":"1047757196","6":"1047757196"},{"0":"397","vim_version":"6.0","1":"6.0","script_version":"1.4.2","2":"1.4.2","version_comment":"Rewrote the SetGrepFormat and SetGrepPrg functions.  Added support for all tags for all languages (28) that exuberant ctags supports. ","3":"Rewrote the SetGrepFormat and SetGrepPrg functions.  Added support for all tags for all languages (28) that exuberant ctags supports. ","package":"ShowFunc.vim","4":"ShowFunc.vim","src_id":"1809","5":"1809","creation_date":"1047579984","6":"1047579984"},{"0":"397","vim_version":"6.0","1":"6.0","script_version":"1.4.1","2":"1.4.1","version_comment":"Fixed multi-window scan display issue. Improved dynamic cwindow sizing.  Added basic help dialog.    ","3":"Fixed multi-window scan display issue. Improved dynamic cwindow sizing.  Added basic help dialog.    ","package":"ShowFunc.vim","4":"ShowFunc.vim","src_id":"1650","5":"1650","creation_date":"1042999278","6":"1042999278"},{"0":"397","vim_version":"6.0","1":"6.0","script_version":"1.4","2":"1.4","version_comment":"Changed user interface. Eliminated multiple key-mappings.  Pressing F1 runs the default scan, and opens the cwindow.  Scan sort and type can be changed by pressing the s and t keys respectively.  Combined scan type functions into one (ShowFuncOpen) and bought back the all open windows scan.","3":"Changed user interface. Eliminated multiple key-mappings.  Pressing F1 runs the default scan, and opens the cwindow.  Scan sort and type can be changed by pressing the s and t keys respectively.  Combined scan type functions into one (ShowFuncOpen) and bought back the all open windows scan.","package":"ShowFunc.vim","4":"ShowFunc.vim","src_id":"1574","5":"1574","creation_date":"1040489034","6":"1040489034"},{"0":"397","vim_version":"6.0","1":"6.0","script_version":"1.3","2":"1.3","version_comment":"Fixed buffer display issue (Thanks to vimtip#133). Fixed window height test for TestWinH and OpenCWin.  Changed MultiWin (scans all open windows) to MultiBuf (scans all open buffers). Basic multiple file handling is complete.","3":"Fixed buffer display issue (Thanks to vimtip#133). Fixed window height test for TestWinH and OpenCWin.  Changed MultiWin (scans all open windows) to MultiBuf (scans all open buffers). Basic multiple file handling is complete.","package":"ShowFunc.vim","4":"ShowFunc.vim","src_id":"1521","5":"1521","creation_date":"1038733469","6":"1038733469"},{"0":"397","vim_version":"6.0","1":"6.0","script_version":"1.3Beta3","2":"1.3Beta3","version_comment":"Split SetFileType into two ( SetGrepFormat, and SetGrepPrg ). Set &...&vim to insure proper '\\ multiline translation. Added keymapping testing to protect against conflicting with existing user configurations and to make it easy to remap when necessary. Thanks to Luc Hermitte \r\n","3":"Split SetFileType into two ( SetGrepFormat, and SetGrepPrg ). Set &...&vim to insure proper '\\ multiline translation. Added keymapping testing to protect against conflicting with existing user configurations and to make it easy to remap when necessary. Thanks to Luc Hermitte \r\n","package":"ShowFunc.vim","4":"ShowFunc.vim","src_id":"1514","5":"1514","creation_date":"1038571696","6":"1038571696"},{"0":"397","vim_version":"6.0","1":"6.0","script_version":"1.3Beta2","2":"1.3Beta2","version_comment":"Fixed multiple file cwindow refresh issue (grep vs. grepa).  General clean up.\r\n","3":"Fixed multiple file cwindow refresh issue (grep vs. grepa).  General clean up.\r\n","package":"ShowFunc.vim","4":"ShowFunc.vim","src_id":"1442","5":"1442","creation_date":"1037787548","6":"1037787548"},{"0":"397","vim_version":"6.0","1":"6.0","script_version":"1.3Beta","2":"1.3Beta","version_comment":"Added multiple file support.  Restructured script.  ","3":"Added multiple file support.  Restructured script.  ","package":"ShowFunc.vim","4":"ShowFunc.vim","src_id":"1427","5":"1427","creation_date":"1037447212","6":"1037447212"},{"0":"397","vim_version":"6.0","1":"6.0","script_version":"1.2.1","2":"1.2.1","version_comment":"Added unknown filetype handling.  Added status messages('ShowFunc:').  Fixed key-mappings .  ","3":"Added unknown filetype handling.  Added status messages('ShowFunc:').  Fixed key-mappings .  ","package":"ShowFunc.vim","4":"ShowFunc.vim","src_id":"1314","5":"1314","creation_date":"1034875121","6":"1034875121"},{"0":"397","vim_version":"6.0","1":"6.0","script_version":"1.2","2":"1.2","version_comment":"Fixed redraw bug so that it works with the winmanager plugin (vimscript#95).  ","3":"Fixed redraw bug so that it works with the winmanager plugin (vimscript#95).  ","package":"ShowFunc.vim","4":"ShowFunc.vim","src_id":"1228","5":"1228","creation_date":"1032732050","6":"1032732050"},{"0":"397","vim_version":"6.0","1":"6.0","script_version":"1.1.3","2":"1.1.3","version_comment":"Fixed Fortran and Pascal patches, Thanks the Ajit Thakkar, and Engelbert Gruber.","3":"Fixed Fortran and Pascal patches, Thanks the Ajit Thakkar, and Engelbert Gruber.","package":"ShowFunc.vim","4":"ShowFunc.vim","src_id":"1182","5":"1182","creation_date":"1030967120","6":"1030967120"},{"0":"397","vim_version":"6.0","1":"6.0","script_version":"1.1.1","2":"1.1.1","version_comment":"ooops.","3":"ooops.","package":"ShowFunc.vim","4":"ShowFunc.vim","src_id":"1167","5":"1167","creation_date":"1030397327","6":"1030397327"},{"0":"397","vim_version":"6.0","1":"6.0","script_version":"1.1","2":"1.1","version_comment":"Patches to Fortran (thanks to Ajit Thakkar), Pascal, and Python support.  ","3":"Patches to Fortran (thanks to Ajit Thakkar), Pascal, and Python support.  ","package":"ShowFunc.vim","4":"ShowFunc.vim","src_id":"1166","5":"1166","creation_date":"1030396769","6":"1030396769"},{"0":"397","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"ShowFunc.vim","4":"ShowFunc.vim","src_id":"1161","5":"1161","creation_date":"1030207413","6":"1030207413"}]},"396":{"script_id":"396","0":"396","script_name":"scilab.vim","1":"scilab.vim","script_type":"syntax","2":"syntax","summary":"Vim syntax file for Scilab","3":"Vim syntax file for Scilab","description":"scilab.vim provides basic syntax support for Scilab, it is based on matlab.vim, because Scilab it is a Matlab like languaje.","4":"scilab.vim provides basic syntax support for Scilab, it is based on matlab.vim, because Scilab it is a Matlab like languaje.","install_details":"just put scilab.vim where Vim could see it","5":"just put scilab.vim where Vim could see it","first_name":"Patricio","6":"Patricio","last_name":"Toledo","7":"Toledo","releases":[{"0":"396","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"scilab.vim","4":"scilab.vim","src_id":"1160","5":"1160","creation_date":"1030205957","6":"1030205957"}]},"395":{"script_id":"395","0":"395","script_name":"gri.vim","1":"gri.vim","script_type":"syntax","2":"syntax","summary":"Vim syntax file for Gri","3":"Vim syntax file for Gri","description":"gri.vim provides basic syntax support for Gri, it is based mainly in gnuplot.vim, as it is a scripting language for scientific plots. ","4":"gri.vim provides basic syntax support for Gri, it is based mainly in gnuplot.vim, as it is a scripting language for scientific plots. ","install_details":"just put gri.vim where vim could see it.","5":"just put gri.vim where vim could see it.","first_name":"Patricio","6":"Patricio","last_name":"Toledo","7":"Toledo","releases":[{"0":"395","vim_version":"6.0","1":"6.0","script_version":"0.3","2":"0.3","version_comment":"mismatch }, better colors and other kind stuff","3":"mismatch }, better colors and other kind stuff","package":"gri.vim","4":"gri.vim","src_id":"1977","5":"1977","creation_date":"1052416210","6":"1052416210"},{"0":"395","vim_version":"6.0","1":"6.0","script_version":"0.1.9","2":"0.1.9","version_comment":"Just optimization.","3":"Just optimization.","package":"gri.vim","4":"gri.vim","src_id":"1306","5":"1306","creation_date":"1034704758","6":"1034704758"},{"0":"395","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"gri.vim","4":"gri.vim","src_id":"1159","5":"1159","creation_date":"1030205416","6":"1030205416"}]},"394":{"script_id":"394","0":"394","script_name":"bugfixes to vim indent for verilog","1":"bugfixes to vim indent for verilog","script_type":"indent","2":"indent","summary":"bugfixes: previous version was evaluating expressions inside comments","3":"bugfixes: previous version was evaluating expressions inside comments","description":"The current version of verilog.vim used for indentation evaluates expressions inside '\/\/' comments leading to a grossly misindented code fixed the same","4":"The current version of verilog.vim used for indentation evaluates expressions inside '\/\/' comments leading to a grossly misindented code fixed the same","install_details":"put this in your \r\n$install_DIr\/share\/vim\/vim60\/indent\/verilog.vim","5":"put this in your \r\n$install_DIr\/share\/vim\/vim60\/indent\/verilog.vim","first_name":"vijayvithal","6":"vijayvithal","last_name":"jahagirdar","7":"jahagirdar","releases":[{"0":"394","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"added details of what was changed in the file header","3":"added details of what was changed in the file header","package":"verilog.vim","4":"verilog.vim","src_id":"9712","5":"9712","creation_date":"1229808495","6":"1229808495"},{"0":"394","vim_version":"6.0","1":"6.0","script_version":"1","2":"1","version_comment":"Initial upload","3":"Initial upload","package":"verilog.vim","4":"verilog.vim","src_id":"1155","5":"1155","creation_date":"1029918574","6":"1029918574"}]},"393":{"script_id":"393","0":"393","script_name":"spectre.vim","1":"spectre.vim","script_type":"syntax","2":"syntax","summary":"Syntax hilighting for Spectre circuit simulator input netlist","3":"Syntax hilighting for Spectre circuit simulator input netlist","description":"Spectre is an advanced circuit simulator from Cadence Design Systems that simulates analog and digital circuits at the differential equation level.","4":"Spectre is an advanced circuit simulator from Cadence Design Systems that simulates analog and digital circuits at the differential equation level.","install_details":"1. Place in the vim syntax directory.\r\n2. :cal SetSyn(\"spectre\")","5":"1. Place in the vim syntax directory.\r\n2. :cal SetSyn(\"spectre\")","first_name":"Ahmed","6":"Ahmed","last_name":"Elzeftawi","7":"Elzeftawi","releases":[{"0":"393","vim_version":"7.0","1":"7.0","script_version":"0.2","2":"0.2","version_comment":"Added support for line folding in Spectre netlist contributed by Ignacio Martinez","3":"Added support for line folding in Spectre netlist contributed by Ignacio Martinez","package":"spectre.vim","4":"spectre.vim","src_id":"26370","5":"26370","creation_date":"1549686987","6":"1549686987"},{"0":"393","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"spectre.vim","4":"spectre.vim","src_id":"1154","5":"1154","creation_date":"1029905486","6":"1029905486"}]},"392":{"script_id":"392","0":"392","script_name":"ocean.vim","1":"ocean.vim","script_type":"syntax","2":"syntax","summary":"Syntax hilighting for Open Command Environment for Analysis (OCEAN)","3":"Syntax hilighting for Open Command Environment for Analysis (OCEAN)","description":"This file provides syntax hilighting for Open Command Environment for Analysis(OCEAN). OCEAN is a scripting language used in EDA tools from Cadence Design Systems that simulates analog and digital circuits at the differential equation level.","4":"This file provides syntax hilighting for Open Command Environment for Analysis(OCEAN). OCEAN is a scripting language used in EDA tools from Cadence Design Systems that simulates analog and digital circuits at the differential equation level.","install_details":"1. Place in the vim syntax directory.\r\n2. :cal SetSyn(\"ocean\")\r\n","5":"1. Place in the vim syntax directory.\r\n2. :cal SetSyn(\"ocean\")\r\n","first_name":"Ahmed","6":"Ahmed","last_name":"Elzeftawi","7":"Elzeftawi","releases":[{"0":"392","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"ocean.vim","4":"ocean.vim","src_id":"1153","5":"1153","creation_date":"1029905323","6":"1029905323"}]},"391":{"script_id":"391","0":"391","script_name":"LaTeX functions","1":"LaTeX functions","script_type":"ftplugin","2":"ftplugin","summary":"Functions and mappings for editing LaTeX documents.","3":"Functions and mappings for editing LaTeX documents.","description":"This package has functions for inserting various LaTeX commands. Has ability to insert, delete, change enviroment. Has macros for operating on commands with two or more argument, etc.\r\n\r\nAlso there is functions for operating with citations and references. Mainly it's insertion into document, with quite user-friendly selection.\r\n\r\nNow it has documentation, in style of VIM help files.\r\n\r\nSo if you have any wishes, ideas, etc. feel free to contact me.","4":"This package has functions for inserting various LaTeX commands. Has ability to insert, delete, change enviroment. Has macros for operating on commands with two or more argument, etc.\r\n\r\nAlso there is functions for operating with citations and references. Mainly it's insertion into document, with quite user-friendly selection.\r\n\r\nNow it has documentation, in style of VIM help files.\r\n\r\nSo if you have any wishes, ideas, etc. feel free to contact me.","install_details":"See installation section in tex.txt file in package archive.","5":"See installation section in tex.txt file in package archive.","first_name":"Karel","6":"Karel","last_name":"Vaigl","7":"Vaigl","releases":[{"0":"391","vim_version":"6.0","1":"6.0","script_version":"0.2","2":"0.2","version_comment":"added documentation + some functions + improved key-mappings","3":"added documentation + some functions + improved key-mappings","package":"latex-0.2.tar.bz2","4":"latex-0.2.tar.bz2","src_id":"1339","5":"1339","creation_date":"1035689729","6":"1035689729"},{"0":"391","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"latex.tar.gz","4":"latex.tar.gz","src_id":"1152","5":"1152","creation_date":"1029852120","6":"1029852120"}]},"390":{"script_id":"390","0":"390","script_name":"plp.vim","1":"plp.vim","script_type":"syntax","2":"syntax","summary":"Syntax file for PLP code, which is HTML + Perl","3":"Syntax file for PLP code, which is HTML + Perl","description":"PLP is yet another Perl embedder, primarily for HTML documents. Unlike with other Perl embedders, there is no need to learn a meta-syntax or object model: one can just use the normal Perl constructs. PLP runs under mod_perl for speeds comparable to those of PHP, but can also be run as a CGI script. \r\n\r\nThis syntax file adds proper PLP highlighting to vim.","4":"PLP is yet another Perl embedder, primarily for HTML documents. Unlike with other Perl embedders, there is no need to learn a meta-syntax or object model: one can just use the normal Perl constructs. PLP runs under mod_perl for speeds comparable to those of PHP, but can also be run as a CGI script. \r\n\r\nThis syntax file adds proper PLP highlighting to vim.","install_details":"","5":"","first_name":"Juerd","6":"Juerd","last_name":"Waalboer","7":"Waalboer","releases":[{"0":"390","vim_version":"6.0","1":"6.0","script_version":"1.00","2":"1.00","version_comment":"Initial upload","3":"Initial upload","package":"plp.vim","4":"plp.vim","src_id":"1145","5":"1145","creation_date":"1029725833","6":"1029725833"}]},"389":{"script_id":"389","0":"389","script_name":"scratch utility","1":"scratch utility","script_type":"utility","2":"utility","summary":"A simple utility to create scratch buffers","3":"A simple utility to create scratch buffers","description":"This is a simple plugin that creates a scratch buffer for your\r\nvim session and helps to access it when you need it.  \r\n                                                                 \r\nIf you like the custom mapping provided in the script - hitting\r\n<F8> should create a new scratch buffer. You can do your scribes\r\nhere and if you want to get rid of it, hit <F8> again. If you want to \r\nget back to the scratch buffer hit <F8> again.\r\n","4":"This is a simple plugin that creates a scratch buffer for your\r\nvim session and helps to access it when you need it.  \r\n                                                                 \r\nIf you like the custom mapping provided in the script - hitting\r\n<F8> should create a new scratch buffer. You can do your scribes\r\nhere and if you want to get rid of it, hit <F8> again. If you want to \r\nget back to the scratch buffer hit <F8> again.\r\n","install_details":"This script will only work on Vim 6.0 and higher. Just dump the script in your plugin directory and let vim do the rest!\r\n","5":"This script will only work on Vim 6.0 and higher. Just dump the script in your plugin directory and let vim do the rest!\r\n","first_name":"Abhilash","6":"Abhilash","last_name":"Koneri","7":"Koneri","releases":[{"0":"389","vim_version":"6.0","1":"6.0","script_version":"0.7","2":"0.7","version_comment":"Includes VimLeavePre hook to dump the contents of the scratch buffer to a file before exiting.  Set the global variable g:scratchBackupFile to a file path to enable the feature. See comments in the plugin file.\r\n \r\n(Once again , Thanks to Hari Krishna Dara (hari_vim at yahoo dot com) for the useful enhancement!)\r\n ","3":"Includes VimLeavePre hook to dump the contents of the scratch buffer to a file before exiting.  Set the global variable g:scratchBackupFile to a file path to enable the feature. See comments in the plugin file.\r\n \r\n(Once again , Thanks to Hari Krishna Dara (hari_vim at yahoo dot com) for the useful enhancement!)\r\n ","package":"scratch.vim","4":"scratch.vim","src_id":"4652","5":"4652","creation_date":"1128547911","6":"1128547911"},{"0":"389","vim_version":"6.0","1":"6.0","script_version":"0.6","2":"0.6","version_comment":"Fixes a bug in the script that does not handle the scratch buffer deleted using :bwipeout!  This version simply re-creates the an empty buffer.","3":"Fixes a bug in the script that does not handle the scratch buffer deleted using :bwipeout!  This version simply re-creates the an empty buffer.","package":"scratch.vim","4":"scratch.vim","src_id":"4437","5":"4437","creation_date":"1121631846","6":"1121631846"},{"0":"389","vim_version":"6.0","1":"6.0","script_version":"0.5","2":"0.5","version_comment":"Included the (yet another) patch sent by Hari Krishna Dara. This patch adds extra escapes when shellslash is set (Unix shells).\r\n\r\nThanks Hari!\r\n","3":"Included the (yet another) patch sent by Hari Krishna Dara. This patch adds extra escapes when shellslash is set (Unix shells).\r\n\r\nThanks Hari!\r\n","package":"scratch.vim","4":"scratch.vim","src_id":"2445","5":"2445","creation_date":"1067889561","6":"1067889561"},{"0":"389","vim_version":"6.0","1":"6.0","script_version":"0.4","2":"0.4","version_comment":"Changed the scratch buffer name to [scratch] (from the ghastly -scratch-). Thanks to Hari Krishna Dara once again!","3":"Changed the scratch buffer name to [scratch] (from the ghastly -scratch-). Thanks to Hari Krishna Dara once again!","package":"scratch.vim","4":"scratch.vim","src_id":"1749","5":"1749","creation_date":"1045506230","6":"1045506230"},{"0":"389","vim_version":"6.0","1":"6.0","script_version":"0.3","2":"0.3","version_comment":"Friendlier key mappings. Hitting F8 should create , hide and navigate to the scratch buffer during a vim session. Thanks to Hari Krishna Dara for enhancing the script.","3":"Friendlier key mappings. Hitting F8 should create , hide and navigate to the scratch buffer during a vim session. Thanks to Hari Krishna Dara for enhancing the script.","package":"scratch.vim","4":"scratch.vim","src_id":"1621","5":"1621","creation_date":"1042146414","6":"1042146414"},{"0":"389","vim_version":"6.0","1":"6.0","script_version":"0.2","2":"0.2","version_comment":"Add more friendly mappings. Thanks to Charles E. Campbell for his suggestions. The old mappings were removed. The defaults now use <F8> to open the scratch buffer and <s-F8> to close the buffer","3":"Add more friendly mappings. Thanks to Charles E. Campbell for his suggestions. The old mappings were removed. The defaults now use <F8> to open the scratch buffer and <s-F8> to close the buffer","package":"scratch.vim","4":"scratch.vim","src_id":"1446","5":"1446","creation_date":"1037823958","6":"1037823958"},{"0":"389","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Fixed the problem with opening scratch buffer -- Thanks to Thomas Regner <regner@dievision.de> for spotting the problem ","3":"Fixed the problem with opening scratch buffer -- Thanks to Thomas Regner <regner@dievision.de> for spotting the problem ","package":"scratch.vim","4":"scratch.vim","src_id":"1352","5":"1352","creation_date":"1036010194","6":"1036010194"},{"0":"389","vim_version":"6.0","1":"6.0","script_version":"0.0","2":"0.0","version_comment":"Initial upload","3":"Initial upload","package":"scratch.vim","4":"scratch.vim","src_id":"1144","5":"1144","creation_date":"1029572888","6":"1029572888"}]},"388":{"script_id":"388","0":"388","script_name":"LbdbQuery.vim","1":"LbdbQuery.vim","script_type":"utility","2":"utility","summary":"Look up email addresses with lbdbq.","3":"Look up email addresses with lbdbq.","description":"This script invokes lbdbq to look up the email address. mutt-heads that edit headers with vim might find this one useful. The results are displayed in a split window. The window is closed when the key 'q' is hit. Hit the \"+\" key to select the email id of interest and insert it into the file.\r\n","4":"This script invokes lbdbq to look up the email address. mutt-heads that edit headers with vim might find this one useful. The results are displayed in a split window. The window is closed when the key 'q' is hit. Hit the \"+\" key to select the email id of interest and insert it into the file.\r\n","install_details":"Save thie file somwhere and source it.","5":"Save thie file somwhere and source it.","first_name":"Janakiraman","6":"Janakiraman","last_name":"","7":"","releases":[{"0":"388","vim_version":"5.7","1":"5.7","script_version":"0.2","2":"0.2","version_comment":"Fixed a problem with names of the form \"Lastname, Firstname\".","3":"Fixed a problem with names of the form \"Lastname, Firstname\".","package":"LbdbQuery.vim","4":"LbdbQuery.vim","src_id":"2430","5":"2430","creation_date":"1067368788","6":"1067368788"},{"0":"388","vim_version":"5.7","1":"5.7","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"LbdbQuery.vim","4":"LbdbQuery.vim","src_id":"1143","5":"1143","creation_date":"1029534265","6":"1029534265"}]},"387":{"script_id":"387","0":"387","script_name":"rnc.vim","1":"rnc.vim","script_type":"syntax","2":"syntax","summary":"RELAX NG Compact Syntax","3":"RELAX NG Compact Syntax","description":"Syntax highlighting for RELAX NG Compact Syntax: http:\/\/www.oasis-open.org\/committees\/relax-ng\/compact-20020607.html\r\n\r\nThis is currently very helpful (a little color goes a long way), but not quite fully mature. I am happy to add the feature you want most, and incrementally it will grow into a mature syntax file.","4":"Syntax highlighting for RELAX NG Compact Syntax: http:\/\/www.oasis-open.org\/committees\/relax-ng\/compact-20020607.html\r\n\r\nThis is currently very helpful (a little color goes a long way), but not quite fully mature. I am happy to add the feature you want most, and incrementally it will grow into a mature syntax file.","install_details":"1. Save rnc.vim in ~\/.vim\/syntax (create the directories if necessary)\r\n2. Edit ~\/.vim\/filetype.vim, and put the following line in it:\r\n\r\n\" RELAX NG Compact Syntax\r\naugroup filetypedetect\r\n  au! BufRead,BufNewFile *.rnc\tsetfiletype rnc\r\naugroup END\r\n\r\nOn windows systems, use your vimfiles directory instead of ~\/.vim","5":"1. Save rnc.vim in ~\/.vim\/syntax (create the directories if necessary)\r\n2. Edit ~\/.vim\/filetype.vim, and put the following line in it:\r\n\r\n\" RELAX NG Compact Syntax\r\naugroup filetypedetect\r\n  au! BufRead,BufNewFile *.rnc\tsetfiletype rnc\r\naugroup END\r\n\r\nOn windows systems, use your vimfiles directory instead of ~\/.vim","first_name":"Hans","6":"Hans","last_name":"Fugal","7":"Fugal","releases":[{"0":"387","vim_version":"6.0","1":"6.0","script_version":"1.7","2":"1.7","version_comment":"Some context sensitivity in response to feature requests. (hint, hint) This version now handles named parameters, element and attribute names, and better handles assignmentMethod operators. Annotations have their own highlight group although currently it's not highlight-linked to anything.","3":"Some context sensitivity in response to feature requests. (hint, hint) This version now handles named parameters, element and attribute names, and better handles assignmentMethod operators. Annotations have their own highlight group although currently it's not highlight-linked to anything.","package":"rnc.vim","4":"rnc.vim","src_id":"2105","5":"2105","creation_date":"1056227650","6":"1056227650"},{"0":"387","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"rnc.vim","4":"rnc.vim","src_id":"1142","5":"1142","creation_date":"1029496501","6":"1029496501"}]},"386":{"script_id":"386","0":"386","script_name":"python_match.vim","1":"python_match.vim","script_type":"ftplugin","2":"ftplugin","summary":"Extend the % motion and define g%, [%, and ]% motions for Python files","3":"Extend the % motion and define g%, [%, and ]% motions for Python files","description":"This script redefines the % motion so that (in addition to its usual behavior)\r\nit cycles through if\/elif\/else, try\/except\/catch, for\/continue\/break, and\r\nwhile\/continue\/break structures.  The script also\r\ndefines g% to cycle in the opposite direction.  Two other motions, [% and ]%,\r\ngo to the start and end of the current block, respectively.\r\n\r\nAll of these motions should work in Normal, Visual, and Operator-pending\r\nmodes.  For example, d]% should delete (characterwise) until the end of the\r\ncurrent block; v]%d should do the same, going through Visual mode so that\r\nyou can see what is being deleted; and V]%d makes it linewise.","4":"This script redefines the % motion so that (in addition to its usual behavior)\r\nit cycles through if\/elif\/else, try\/except\/catch, for\/continue\/break, and\r\nwhile\/continue\/break structures.  The script also\r\ndefines g% to cycle in the opposite direction.  Two other motions, [% and ]%,\r\ngo to the start and end of the current block, respectively.\r\n\r\nAll of these motions should work in Normal, Visual, and Operator-pending\r\nmodes.  For example, d]% should delete (characterwise) until the end of the\r\ncurrent block; v]%d should do the same, going through Visual mode so that\r\nyou can see what is being deleted; and V]%d makes it linewise.","install_details":"Copy the file to your ftplugin\/ directory.  If, for some reason, you want to\r\nchange the name of the file, copy it to ftplugin\/python\/ or :source it from\r\nftplugin\/python.vim .","5":"Copy the file to your ftplugin\/ directory.  If, for some reason, you want to\r\nchange the name of the file, copy it to ftplugin\/python\/ or :source it from\r\nftplugin\/python.vim .","first_name":"Benji","6":"Benji","last_name":"Fisher","7":"Fisher","releases":[{"0":"386","vim_version":"6.0","1":"6.0","script_version":"0.5","2":"0.5","version_comment":"I added support for for and while loops:  % and g% go between the start of the block and either break or continue lines.\r\n\r\nI reorganized the code and made several minor improvements.  For example, [% and ]% now accept a count,  `` goes back to where you started, and g% does nothing (insteadof acting like the default %) if the cursor starts on a line that does not begin with a recognized key word.","3":"I added support for for and while loops:  % and g% go between the start of the block and either break or continue lines.\r\n\r\nI reorganized the code and made several minor improvements.  For example, [% and ]% now accept a count,  `` goes back to where you started, and g% does nothing (insteadof acting like the default %) if the cursor starts on a line that does not begin with a recognized key word.","package":"python_match.vim","4":"python_match.vim","src_id":"2366","5":"2366","creation_date":"1065086069","6":"1065086069"},{"0":"386","vim_version":"6.0","1":"6.0","script_version":"0.4","2":"0.4","version_comment":"Initial upload","3":"Initial upload","package":"python_match.vim","4":"python_match.vim","src_id":"1138","5":"1138","creation_date":"1029478690","6":"1029478690"}]},"385":{"script_id":"385","0":"385","script_name":"ibmedit.vim","1":"ibmedit.vim","script_type":"color scheme","2":"color scheme","summary":"Color scheme similar to IBM Edit from MS-DOS. Also looks a bit like Borland IDE.","3":"Color scheme similar to IBM Edit from MS-DOS. Also looks a bit like Borland IDE.","description":"DarkBlue background. easy on the eyes. best used in gui.","4":"DarkBlue background. easy on the eyes. best used in gui.","install_details":"1\/ copy into ~\/.vim\/colors\r\n2\/ in vim:\r\n:colo ibmedit","5":"1\/ copy into ~\/.vim\/colors\r\n2\/ in vim:\r\n:colo ibmedit","first_name":"maarten","6":"maarten","last_name":"s","7":"s","releases":[{"0":"385","vim_version":"6.0","1":"6.0","script_version":"1.1","2":"1.1","version_comment":"colors for color term are in line with gui colors now.","3":"colors for color term are in line with gui colors now.","package":"ibmedit.vim","4":"ibmedit.vim","src_id":"1149","5":"1149","creation_date":"1029831464","6":"1029831464"},{"0":"385","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"ibmedit.vim","4":"ibmedit.vim","src_id":"1137","5":"1137","creation_date":"1029470022","6":"1029470022"}]},"384":{"script_id":"384","0":"384","script_name":"DarkOcean.vim","1":"DarkOcean.vim","script_type":"color scheme","2":"color scheme","summary":"Its really dark","3":"Its really dark","description":"dark colorscheme. snapshot available at\r\nhttp:\/\/www.geocities.com\/ncr_10\/snapshot.html \r\ninspired by Tom Regner's oceandeep colorscheme (vimscript #368)\r\n\r\n\r\n-ncr","4":"dark colorscheme. snapshot available at\r\nhttp:\/\/www.geocities.com\/ncr_10\/snapshot.html \r\ninspired by Tom Regner's oceandeep colorscheme (vimscript #368)\r\n\r\n\r\n-ncr","install_details":"Drop this in your $VIMRUNTIME\/colors\/ directory\r\nor manually source it \":so darkocean.vim\".","5":"Drop this in your $VIMRUNTIME\/colors\/ directory\r\nor manually source it \":so darkocean.vim\".","first_name":"Naveen","6":"Naveen","last_name":"Chandra","7":"Chandra","releases":[{"0":"384","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"darkocean.vim","4":"darkocean.vim","src_id":"1136","5":"1136","creation_date":"1029469119","6":"1029469119"}]},"383":{"script_id":"383","0":"383","script_name":"SyntaxAttr.vim","1":"SyntaxAttr.vim","script_type":"utility","2":"utility","summary":"Show syntax highlighting attributes of character under cursor.","3":"Show syntax highlighting attributes of character under cursor.","description":"Displays the syntax highlighting attributes of the character under the cursor; including syntax group (and what it's linked to, if linked), foreground\/background colors (name and numeric equivallent), bold, underline, etc.\r\n\r\nExample output:\r\n\r\n[WIth cursor on a function name in a vim script]\r\n     group: vimUserFuncName guifg=DarkCyan(#008b8b) gui=bold\r\n\r\n[With cursor on \"function\" keyword in vim script]\r\n     group: vimFuncKey->Statement guifg=Brown(#a52a2a) gui=bold\r\n\r\n[WIth cursor on \"let\" keyword in vim script]\r\n     group: vimLet->Statement guifg=Brown(#a52a2a) gui=bold\r\n\r\nThis can be helpfull both developing syntax files, and for determining what something is (according to the syntax rules), since the group names used in syntax files are usually well-named.\r\n\r\nRecommended use with a mapping such as:\r\n\r\n  map -a\t:call SyntaxAttr()<CR>","4":"Displays the syntax highlighting attributes of the character under the cursor; including syntax group (and what it's linked to, if linked), foreground\/background colors (name and numeric equivallent), bold, underline, etc.\r\n\r\nExample output:\r\n\r\n[WIth cursor on a function name in a vim script]\r\n     group: vimUserFuncName guifg=DarkCyan(#008b8b) gui=bold\r\n\r\n[With cursor on \"function\" keyword in vim script]\r\n     group: vimFuncKey->Statement guifg=Brown(#a52a2a) gui=bold\r\n\r\n[WIth cursor on \"let\" keyword in vim script]\r\n     group: vimLet->Statement guifg=Brown(#a52a2a) gui=bold\r\n\r\nThis can be helpfull both developing syntax files, and for determining what something is (according to the syntax rules), since the group names used in syntax files are usually well-named.\r\n\r\nRecommended use with a mapping such as:\r\n\r\n  map -a\t:call SyntaxAttr()<CR>","install_details":"I put it in my autoload directory (~\/vim\/autoload), so the function is automagically loaded as needed via an autocommand: \r\n\r\nautocmd FuncUndefined * exe 'runtime autoload\/' . expand('<afile>') . '.vim'","5":"I put it in my autoload directory (~\/vim\/autoload), so the function is automagically loaded as needed via an autocommand: \r\n\r\nautocmd FuncUndefined * exe 'runtime autoload\/' . expand('<afile>') . '.vim'","first_name":"Gary","6":"Gary","last_name":"Holloway","7":"Holloway","releases":[{"0":"383","vim_version":"6.0","1":"6.0","script_version":"1.1","2":"1.1","version_comment":"Initial upload","3":"Initial upload","package":"SyntaxAttr.vim","4":"SyntaxAttr.vim","src_id":"1135","5":"1135","creation_date":"1029427767","6":"1029427767"}]},"382":{"script_id":"382","0":"382","script_name":"ShowBlockName.vim","1":"ShowBlockName.vim","script_type":"utility","2":"utility","summary":"Show the name of the code-block (e.g. function) the cursor is in on the cmd line","3":"Show the name of the code-block (e.g. function) the cursor is in on the cmd line","description":"Display the name of the current \"block\" the cursor is in in the command-line\r\narea (i.e., with vim's echo).\r\n\r\nA \"block\" is context-sensitive, (e.g., function name, variable name if in an\r\ninitialization, type name if in a typedef, etc.)\r\n\r\nNOTE: The only languages with specific support as-is are vim scripts, Perl, and C.  Support for other languages can be added by modifying the script with appropriate search patterns.\r\n\r\nTypical use (.vimrc):\r\n  au CursorHold *\tcall ShowBlockName('quiet')\r\n\r\n  \" Show the name of the function we're in on the message line; pnuemonic [[\r\n  map <silent> g[[\t:call ShowBlockName()<CR>\r\n\r\n  \" Disable ShowBlockName (once); to prevent the CursorHold autocommand from\r\n  \" overwriting something in the command window (e.g., SyntaxAttr() output).\r\n  map <silent> g]] :call ShowBlockName('OFF')<CR>\r\n\r\n\r\n  \" Tweak commands like [d so that they disable ShowBlockName so\r\n  \" it doesn't obliterate the output of this command.\r\n  nnoremap [d :call ShowBlockName('[d')<CR>\r\n  nnoremap [i :call ShowBlockName('[i')<CR>\r\n\r\nNOTE:\r\n\tThis will NOT work if the start-of-block is the first line in a file.\r\n\r\nTHIS SCRIPT USES ShowLine ( vimscript #381 )","4":"Display the name of the current \"block\" the cursor is in in the command-line\r\narea (i.e., with vim's echo).\r\n\r\nA \"block\" is context-sensitive, (e.g., function name, variable name if in an\r\ninitialization, type name if in a typedef, etc.)\r\n\r\nNOTE: The only languages with specific support as-is are vim scripts, Perl, and C.  Support for other languages can be added by modifying the script with appropriate search patterns.\r\n\r\nTypical use (.vimrc):\r\n  au CursorHold *\tcall ShowBlockName('quiet')\r\n\r\n  \" Show the name of the function we're in on the message line; pnuemonic [[\r\n  map <silent> g[[\t:call ShowBlockName()<CR>\r\n\r\n  \" Disable ShowBlockName (once); to prevent the CursorHold autocommand from\r\n  \" overwriting something in the command window (e.g., SyntaxAttr() output).\r\n  map <silent> g]] :call ShowBlockName('OFF')<CR>\r\n\r\n\r\n  \" Tweak commands like [d so that they disable ShowBlockName so\r\n  \" it doesn't obliterate the output of this command.\r\n  nnoremap [d :call ShowBlockName('[d')<CR>\r\n  nnoremap [i :call ShowBlockName('[i')<CR>\r\n\r\nNOTE:\r\n\tThis will NOT work if the start-of-block is the first line in a file.\r\n\r\nTHIS SCRIPT USES ShowLine ( vimscript #381 )","install_details":"I put it in my autoload directory (~\/vim\/autoload), so the function is automagically loaded as needed via an autocommand: \r\n\r\nautocmd FuncUndefined * exe 'runtime autoload\/' . expand('<afile>') . '.vim'","5":"I put it in my autoload directory (~\/vim\/autoload), so the function is automagically loaded as needed via an autocommand: \r\n\r\nautocmd FuncUndefined * exe 'runtime autoload\/' . expand('<afile>') . '.vim'","first_name":"Gary","6":"Gary","last_name":"Holloway","7":"Holloway","releases":[{"0":"382","vim_version":"6.0","1":"6.0","script_version":"1.6.1","2":"1.6.1","version_comment":"Fixed typo.","3":"Fixed typo.","package":"ShowBlockName.vim","4":"ShowBlockName.vim","src_id":"1634","5":"1634","creation_date":"1042569494","6":"1042569494"},{"0":"382","vim_version":"6.0","1":"6.0","script_version":"1.6","2":"1.6","version_comment":"Removed extraneous '#' from perl function-matching pattern (thanks Christian ).","3":"Removed extraneous '#' from perl function-matching pattern (thanks Christian ).","package":"ShowBlockName.vim","4":"ShowBlockName.vim","src_id":"1134","5":"1134","creation_date":"1029426697","6":"1029426697"},{"0":"382","vim_version":"6.0","1":"6.0","script_version":"1.5","2":"1.5","version_comment":"Initial upload","3":"Initial upload","package":"ShowBlockName.vim","4":"ShowBlockName.vim","src_id":"1132","5":"1132","creation_date":"1029418932","6":"1029418932"}]},"381":{"script_id":"381","0":"381","script_name":"ShowLine.vim","1":"ShowLine.vim","script_type":"utility","2":"utility","summary":"Display line(s) in the command area (like echo), but syntax highlighted.","3":"Display line(s) in the command area (like echo), but syntax highlighted.","description":"Display a line or lines in the command area, like the builtin echo, but using the original lines' syntax highlighting.\r\n\r\nUseful to other scripts for displaying lines of text, highlighted as they appear in the editor window (e.g., see ShowBlockName.vim -- vimscript #382)","4":"Display a line or lines in the command area, like the builtin echo, but using the original lines' syntax highlighting.\r\n\r\nUseful to other scripts for displaying lines of text, highlighted as they appear in the editor window (e.g., see ShowBlockName.vim -- vimscript #382)","install_details":"I put it in my autoload directory (~\/vim\/autoload), so the function is automagically loaded as needed via an autocommand:\r\n\r\nautocmd FuncUndefined *\texe 'runtime autoload\/' . expand('<afile>') . '.vim'","5":"I put it in my autoload directory (~\/vim\/autoload), so the function is automagically loaded as needed via an autocommand:\r\n\r\nautocmd FuncUndefined *\texe 'runtime autoload\/' . expand('<afile>') . '.vim'","first_name":"Gary","6":"Gary","last_name":"Holloway","7":"Holloway","releases":[{"0":"381","vim_version":"6.0","1":"6.0","script_version":"1.1","2":"1.1","version_comment":"Initial upload","3":"Initial upload","package":"ShowLine.vim","4":"ShowLine.vim","src_id":"1131","5":"1131","creation_date":"1029417246","6":"1029417246"}]},"380":{"script_id":"380","0":"380","script_name":"PreviewTag.vim","1":"PreviewTag.vim","script_type":"utility","2":"utility","summary":"Resize preview window hieght to show \"entire\" tag (if a recognized type of tag)","3":"Resize preview window hieght to show \"entire\" tag (if a recognized type of tag)","description":"Basically, does a  g}  command to bring up the tag in the preview window.  \r\nNext, it looks at the located tag, and based on what it looks like adjusts the preview window height and posistions the file in the preview window so that the \"entire\" tag is shown -- in the case of a structure, the \"entire\" tag includes the opening brace through the closing brace.  That's where the style used can have an effect.  We use the style:                                            \r\n                                                                              \r\n     typedef struct foo {                                                     \r\n          int   member1;                                                      \r\n          long  member2;                                                      \r\n     } FooType;                                                               \r\n                                                                              \r\nSo, including the line having the opening brace through the line having the   \r\nclosing brace shows the entire type.                                          \r\n                                                                              \r\nIf it doesn't work with your style, it should only take some minor tweaks to  \r\nthe patterns used to identify different tags to treat specially.\r\n\r\nIf the tag isn't recognized as \"special\", the tag is previewed \"normally\" (i.e., whatever g} does normally, based on your vim settings.","4":"Basically, does a  g}  command to bring up the tag in the preview window.  \r\nNext, it looks at the located tag, and based on what it looks like adjusts the preview window height and posistions the file in the preview window so that the \"entire\" tag is shown -- in the case of a structure, the \"entire\" tag includes the opening brace through the closing brace.  That's where the style used can have an effect.  We use the style:                                            \r\n                                                                              \r\n     typedef struct foo {                                                     \r\n          int   member1;                                                      \r\n          long  member2;                                                      \r\n     } FooType;                                                               \r\n                                                                              \r\nSo, including the line having the opening brace through the line having the   \r\nclosing brace shows the entire type.                                          \r\n                                                                              \r\nIf it doesn't work with your style, it should only take some minor tweaks to  \r\nthe patterns used to identify different tags to treat specially.\r\n\r\nIf the tag isn't recognized as \"special\", the tag is previewed \"normally\" (i.e., whatever g} does normally, based on your vim settings.","install_details":"Personally, I put it into an \"autoload\" directory (e.g., ~\/vim\/autoload), and have it sourced automagically via an autocommand:\r\n\r\n\" Auto-load functions on an as-needed basis.\r\nautocmd FuncUndefined *\texe 'runtime autoload\/' . expand('<afile>') . '.vim'\r\n","5":"Personally, I put it into an \"autoload\" directory (e.g., ~\/vim\/autoload), and have it sourced automagically via an autocommand:\r\n\r\n\" Auto-load functions on an as-needed basis.\r\nautocmd FuncUndefined *\texe 'runtime autoload\/' . expand('<afile>') . '.vim'\r\n","first_name":"Gary","6":"Gary","last_name":"Holloway","7":"Holloway","releases":[{"0":"380","vim_version":"6.0","1":"6.0","script_version":"1","2":"1","version_comment":"Initial upload","3":"Initial upload","package":"PreviewTag.vim","4":"PreviewTag.vim","src_id":"1130","5":"1130","creation_date":"1029412672","6":"1029412672"}]},"379":{"script_id":"379","0":"379","script_name":"d.vim","1":"d.vim","script_type":"syntax","2":"syntax","summary":"Syntax file for the D programming language.","3":"Syntax file for the D programming language.","description":"Syntax file for the D programming language.\r\n\r\nThe new maintainer for versions > 0.18 is Jesse Phillips. Released versions will still be published to this page, but development now occurs at https:\/\/github.com\/JesseKPhillips\/d.vim.","4":"Syntax file for the D programming language.\r\n\r\nThe new maintainer for versions > 0.18 is Jesse Phillips. Released versions will still be published to this page, but development now occurs at https:\/\/github.com\/JesseKPhillips\/d.vim.","install_details":"d.vim is now included in the official vim distribution, v6.3 and later, although it may not always be up to date. To override the default version included in the distribution, place the downloaded d.vim in your syntax directory. On windows, copy to $VIM\/vimfiles\/syntax or $HOME\/vimfiles\/syntax. On Linux copy to $HOME\/.vim\/syntax or $VIM\/vimfiles\/syntax.\r\n\r\nIn older versions of vim (< v6.3), add\r\n  autocmd! BufRead,BufNewFile *.d setfiletype d\r\nto your .vimrc or filetype.vim file. See :help filetype and :help new-filetype.\r\n\r\nSome customizations can be made by manipulating the options ``d_comment_strings``, ``d_hl_operator_overload``, and ``d_hl_object_types``. See the \"Options\" section in d.vim for details.","5":"d.vim is now included in the official vim distribution, v6.3 and later, although it may not always be up to date. To override the default version included in the distribution, place the downloaded d.vim in your syntax directory. On windows, copy to $VIM\/vimfiles\/syntax or $HOME\/vimfiles\/syntax. On Linux copy to $HOME\/.vim\/syntax or $VIM\/vimfiles\/syntax.\r\n\r\nIn older versions of vim (< v6.3), add\r\n  autocmd! BufRead,BufNewFile *.d setfiletype d\r\nto your .vimrc or filetype.vim file. See :help filetype and :help new-filetype.\r\n\r\nSome customizations can be made by manipulating the options ``d_comment_strings``, ``d_hl_operator_overload``, and ``d_hl_object_types``. See the \"Options\" section in d.vim for details.","first_name":"Jason","6":"Jason","last_name":"Mills","7":"Mills","releases":[{"0":"379","vim_version":"7.0","1":"7.0","script_version":"0.26","2":"0.26","version_comment":"* Addressed variable names with \\\"import\\\" or \\\"module\\\" breaking highlighting.\r\n* Fixed Heredoc not being highlighted in function call\r\n* Closing comments without opening are highlighted as error\r\n(By Jesse Phillips)","3":"* Addressed variable names with \\\"import\\\" or \\\"module\\\" breaking highlighting.\r\n* Fixed Heredoc not being highlighted in function call\r\n* Closing comments without opening are highlighted as error\r\n(By Jesse Phillips)","package":"d.vim","4":"d.vim","src_id":"20982","5":"20982","creation_date":"1383148679","6":"1383148679"},{"0":"379","vim_version":"7.0","1":"7.0","script_version":"0.25","2":"0.25","version_comment":"* ASM blocks highlight comments.\r\n* in\/out contracts no longer highlighted as storage class.\r\n* If a module name is the same as a keyword it will not be\r\nhighlighted on module declaration or import.\r\n* scope highlights as a statement, but as a storage class in\r\nparameter list.\r\n* pragma will highlight known commands (lib,msg).\r\n* Keyword updates.","3":"* ASM blocks highlight comments.\r\n* in\/out contracts no longer highlighted as storage class.\r\n* If a module name is the same as a keyword it will not be\r\nhighlighted on module declaration or import.\r\n* scope highlights as a statement, but as a storage class in\r\nparameter list.\r\n* pragma will highlight known commands (lib,msg).\r\n* Keyword updates.","package":"d.vim","4":"d.vim","src_id":"20297","5":"20297","creation_date":"1370446627","6":"1370446627"},{"0":"379","vim_version":"7.0","1":"7.0","script_version":"0.24","2":"0.24","version_comment":"- Added syntax based folding for comments and { } blocks (``set foldmethod=syntax`` to enable).\r\n- Added some missing keywords, such as __vector, __ctfe, __simd, and lots of asm op codes.\r\n- Support for ``coptions``.\r\n- Optional highlighting of some common types from object.di (set variable ``d_hl_object_types``).\r\n- Fixed a few minor keyword matching issues.\r\n- Tidy the code.\r\n\r\nNote: This was done through the efforts of Jesse Phillips.","3":"- Added syntax based folding for comments and { } blocks (``set foldmethod=syntax`` to enable).\r\n- Added some missing keywords, such as __vector, __ctfe, __simd, and lots of asm op codes.\r\n- Support for ``coptions``.\r\n- Optional highlighting of some common types from object.di (set variable ``d_hl_object_types``).\r\n- Fixed a few minor keyword matching issues.\r\n- Tidy the code.\r\n\r\nNote: This was done through the efforts of Jesse Phillips.","package":"d.vim","4":"d.vim","src_id":"19069","5":"19069","creation_date":"1354285336","6":"1354285336"},{"0":"379","vim_version":"7.0","1":"7.0","script_version":"0.22","2":"0.22","version_comment":"* Fixed issue with highlighting version statement inside block.\r\n\r\nNote: Jesse Phillips is the new maintainer and is responsible for this version.","3":"* Fixed issue with highlighting version statement inside block.\r\n\r\nNote: Jesse Phillips is the new maintainer and is responsible for this version.","package":"d.vim","4":"d.vim","src_id":"13889","5":"13889","creation_date":"1285201794","6":"1285201794"},{"0":"379","vim_version":"6.0","1":"6.0","script_version":"0.21","2":"0.21","version_comment":"* Fixed some highlighting bugs (Ellery Newcomer).\r\n* #! highlighting (Steven N. Oliver).\r\n\r\nNote: Jesse Phillips is the new maintainer and is responsible for this version.","3":"* Fixed some highlighting bugs (Ellery Newcomer).\r\n* #! highlighting (Steven N. Oliver).\r\n\r\nNote: Jesse Phillips is the new maintainer and is responsible for this version.","package":"d.vim","4":"d.vim","src_id":"13812","5":"13812","creation_date":"1284244435","6":"1284244435"},{"0":"379","vim_version":"6.0","1":"6.0","script_version":"0.20","2":"0.20","version_comment":"* Added missing keywords for D 2.0 compiler 2.047\r\n* Added special highlighting of known versions\/scopes\/annotations (thanks to Shougo Matsushita)\r\n* Added highlighting of ASM Op Codes in asm blocks.\r\n\r\nNote: Jesse Phillips is the new maintainer and is responsible for this version.","3":"* Added missing keywords for D 2.0 compiler 2.047\r\n* Added special highlighting of known versions\/scopes\/annotations (thanks to Shougo Matsushita)\r\n* Added highlighting of ASM Op Codes in asm blocks.\r\n\r\nNote: Jesse Phillips is the new maintainer and is responsible for this version.","package":"d.vim","4":"d.vim","src_id":"13674","5":"13674","creation_date":"1282766154","6":"1282766154"},{"0":"379","vim_version":"6.0","1":"6.0","script_version":"0.18","2":"0.18","version_comment":"Updated to D versions 1.053 and 2.039.\r\n+ Merged Kirk McDonald version 0.17 updates (http:\/\/paste.dprogramming.com\/dplmb7qx?view=hidelines), including\r\ndelimited strings, token strings, here strings, and some new keywords.\r\n+ Merged Jesse K. Phillips patch for some keywords and attributes (annotations).\r\n+ Added some missing keywords.\r\n","3":"Updated to D versions 1.053 and 2.039.\r\n+ Merged Kirk McDonald version 0.17 updates (http:\/\/paste.dprogramming.com\/dplmb7qx?view=hidelines), including\r\ndelimited strings, token strings, here strings, and some new keywords.\r\n+ Merged Jesse K. Phillips patch for some keywords and attributes (annotations).\r\n+ Added some missing keywords.\r\n","package":"d.vim","4":"d.vim","src_id":"12074","5":"12074","creation_date":"1263258630","6":"1263258630"},{"0":"379","vim_version":"6.0","1":"6.0","script_version":"0.16","2":"0.16","version_comment":"Updated for D version 0.178.\r\n+ Applied a patch (Tim Keating) to fix a bug in highlighting the `\\` literal.\r\n+ Added new keyword: foreach_reverse, lazy\r\n+ Added missing operator overloads: opAssign, opIn, opIn_r.\r\n+ Removed iftype keyword.","3":"Updated for D version 0.178.\r\n+ Applied a patch (Tim Keating) to fix a bug in highlighting the `\\` literal.\r\n+ Added new keyword: foreach_reverse, lazy\r\n+ Added missing operator overloads: opAssign, opIn, opIn_r.\r\n+ Removed iftype keyword.","package":"d.vim","4":"d.vim","src_id":"6563","5":"6563","creation_date":"1167386884","6":"1167386884"},{"0":"379","vim_version":"6.0","1":"6.0","script_version":"0.15","2":"0.15","version_comment":"+ Improved syntax synchronization, especially for \/* *\/ style comments.\r\n+ Fixed a bug that caused some identifiers and numbers to highlight as octal number errors (thanks to Frank Benoit).\r\n+ Added new scope keyword.\r\n+ Strings now know about and highlight the modifiers r, d, c, and w.\r\n+ Changed hexadecimal floating point definitions to match current D spec: _ is a valid digit, i is a valid suffix, and only decimal digits are allowed after the hex exponent p.\r\n+ Changed binary number definitions so integer suffixes are allowed.\r\n","3":"+ Improved syntax synchronization, especially for \/* *\/ style comments.\r\n+ Fixed a bug that caused some identifiers and numbers to highlight as octal number errors (thanks to Frank Benoit).\r\n+ Added new scope keyword.\r\n+ Strings now know about and highlight the modifiers r, d, c, and w.\r\n+ Changed hexadecimal floating point definitions to match current D spec: _ is a valid digit, i is a valid suffix, and only decimal digits are allowed after the hex exponent p.\r\n+ Changed binary number definitions so integer suffixes are allowed.\r\n","package":"d.vim","4":"d.vim","src_id":"5419","5":"5419","creation_date":"1142150700","6":"1142150700"},{"0":"379","vim_version":"6.0","1":"6.0","script_version":"0.14","2":"0.14","version_comment":"Added missing operator overload. Removed highlighting of string prefixes (because string postfixes are not highlighted! Later I hope to highlight both in prefix\/postfix characters).","3":"Added missing operator overload. Removed highlighting of string prefixes (because string postfixes are not highlighted! Later I hope to highlight both in prefix\/postfix characters).","package":"d.vim","4":"d.vim","src_id":"4707","5":"4707","creation_date":"1130606591","6":"1130606591"},{"0":"379","vim_version":"6.0","1":"6.0","script_version":"0.13","2":"0.13","version_comment":"Added new keyword introduced in D version 0.123.","3":"Added new keyword introduced in D version 0.123.","package":"d.vim","4":"d.vim","src_id":"4332","5":"4332","creation_date":"1117693333","6":"1117693333"},{"0":"379","vim_version":"6.0","1":"6.0","script_version":"0.12","2":"0.12","version_comment":"Updated for D version 0.116.\r\n+ Added support for __LINE__, __FILE__ etc.\r\n+ Added support for character entities.","3":"Updated for D version 0.116.\r\n+ Added support for __LINE__, __FILE__ etc.\r\n+ Added support for character entities.","package":"d.vim","4":"d.vim","src_id":"3989","5":"3989","creation_date":"1110384925","6":"1110384925"},{"0":"379","vim_version":"6.0","1":"6.0","script_version":"0.10","2":"0.10","version_comment":"Updated for version 0.95 of the D language spec.","3":"Updated for version 0.95 of the D language spec.","package":"d.vim","4":"d.vim","src_id":"3231","5":"3231","creation_date":"1089872407","6":"1089872407"},{"0":"379","vim_version":"6.0","1":"6.0","script_version":"0.8","2":"0.8","version_comment":"Updated for version 0.90 of the D language spec. Removed unnecessary use of 'main_syntax'.","3":"Updated for version 0.90 of the D language spec. Removed unnecessary use of 'main_syntax'.","package":"d.vim","4":"d.vim","src_id":"3057","5":"3057","creation_date":"1085461203","6":"1085461203"},{"0":"379","vim_version":"6.0","1":"6.0","script_version":"0.6","2":"0.6","version_comment":"Fixed problem with highlighting certain styles of floating point numbers.","3":"Fixed problem with highlighting certain styles of floating point numbers.","package":"d.vim","4":"d.vim","src_id":"2921","5":"2921","creation_date":"1081404535","6":"1081404535"},{"0":"379","vim_version":"6.0","1":"6.0","script_version":"0.5","2":"0.5","version_comment":"Updated keywords to match version 0.79 of the D spec.","3":"Updated keywords to match version 0.79 of the D spec.","package":"d.vim","4":"d.vim","src_id":"2737","5":"2737","creation_date":"1076414077","6":"1076414077"},{"0":"379","vim_version":"6.0","1":"6.0","script_version":"0.4","2":"0.4","version_comment":"Updated for 0.76 of the D spec. In a nutshell, add the keyword 'is' and updated operator overload names.","3":"Updated for 0.76 of the D spec. In a nutshell, add the keyword 'is' and updated operator overload names.","package":"d.vim","4":"d.vim","src_id":"2514","5":"2514","creation_date":"1069749936","6":"1069749936"},{"0":"379","vim_version":"6.0","1":"6.0","script_version":"0.3","2":"0.3","version_comment":"Updated for version 0.75 of the D spec.  Highlights: new keywords, new configuration option, and better highlighting of numbers and strings.","3":"Updated for version 0.75 of the D spec.  Highlights: new keywords, new configuration option, and better highlighting of numbers and strings.","package":"d.vim","4":"d.vim","src_id":"2505","5":"2505","creation_date":"1069409464","6":"1069409464"},{"0":"379","vim_version":"6.0","1":"6.0","script_version":"0.2","2":"0.2","version_comment":"Added new keywords: template, instance, auto; Added option to (not) highlight strings and numbers in comments; Fixed floating point numbers to recognize floats without decimal points.","3":"Added new keywords: template, instance, auto; Added option to (not) highlight strings and numbers in comments; Fixed floating point numbers to recognize floats without decimal points.","package":"d.vim","4":"d.vim","src_id":"1265","5":"1265","creation_date":"1033453861","6":"1033453861"},{"0":"379","vim_version":"6.0","1":"6.0","script_version":"0.1.1","2":"0.1.1","version_comment":"Fixed a few problems: added interface keyword; differentiated public: (and other scope decls) from user labels.","3":"Fixed a few problems: added interface keyword; differentiated public: (and other scope decls) from user labels.","package":"d.vim","4":"d.vim","src_id":"1141","5":"1141","creation_date":"1029490282","6":"1029490282"},{"0":"379","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"d.vim","4":"d.vim","src_id":"1128","5":"1128","creation_date":"1029400789","6":"1029400789"}]},"378":{"script_id":"378","0":"378","script_name":"ia64.vim","1":"ia64.vim","script_type":"syntax","2":"syntax","summary":"Syntax highlight file for Intel IA64 Itanium processor","3":"Syntax highlight file for Intel IA64 Itanium processor","description":"This version (0.7) of ia64.vim scripts fixes the highlighting problem with (tbit.z.*) instructions as pointed out by a user. Version (0.6) which comes with vim 6.1 does not highlight these instructions correctly.\r\n","4":"This version (0.7) of ia64.vim scripts fixes the highlighting problem with (tbit.z.*) instructions as pointed out by a user. Version (0.6) which comes with vim 6.1 does not highlight these instructions correctly.\r\n","install_details":"Copy the file ia64.vim into your <vim install directory>\\vim61\\syntax folder","5":"Copy the file ia64.vim into your <vim install directory>\\vim61\\syntax folder","first_name":"Parth","6":"Parth","last_name":"Malwankar","7":"Malwankar","releases":[{"0":"378","vim_version":"6.0","1":"6.0","script_version":"0.7","2":"0.7","version_comment":"Initial upload","3":"Initial upload","package":"ia64.vim","4":"ia64.vim","src_id":"1120","5":"1120","creation_date":"1029273429","6":"1029273429"}]},"377":{"script_id":"377","0":"377","script_name":"vim game of life","1":"vim game of life","script_type":"game","2":"game","summary":"Game of Life in VIM.","3":"Game of Life in VIM.","description":"A totally useless and not interactive vim script showing an implementation of the famous game of life.\r\n","4":"A totally useless and not interactive vim script showing an implementation of the famous game of life.\r\n","install_details":"source gol.vim\r\n:Gol\r\nsit down and relax\r\nq when you fully satisfied.","5":"source gol.vim\r\n:Gol\r\nsit down and relax\r\nq when you fully satisfied.","first_name":"Arnaud","6":"Arnaud","last_name":"Cornet","7":"Cornet","releases":[{"0":"377","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"gol.vim","4":"gol.vim","src_id":"1119","5":"1119","creation_date":"1029239639","6":"1029239639"}]},"376":{"script_id":"376","0":"376","script_name":"mof.vim","1":"mof.vim","script_type":"syntax","2":"syntax","summary":"Syntax file for CIM Managed Object Format (MOF) files","3":"Syntax file for CIM Managed Object Format (MOF) files","description":"Syntax highlighting for CIM Managed Object Format (MOF) files.  See http:\/\/www.dmtf.org for details on CIM.","4":"Syntax highlighting for CIM Managed Object Format (MOF) files.  See http:\/\/www.dmtf.org for details on CIM.","install_details":"Place in syntax directory and set filetype=mof.","5":"Place in syntax directory and set filetype=mof.","first_name":"Mike","6":"Mike","last_name":"Martin","7":"Martin","releases":[{"0":"376","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"mof.vim","4":"mof.vim","src_id":"1118","5":"1118","creation_date":"1029232854","6":"1029232854"}]},"375":{"script_id":"375","0":"375","script_name":"Denim","1":"Denim","script_type":"color scheme","2":"color scheme","summary":"Dark Color Scheme with lots of blue","3":"Dark Color Scheme with lots of blue","description":"see a screen shot here\r\nhttp:\/\/www.geocities.com\/aldy0169\/images\/denim.jpg","4":"see a screen shot here\r\nhttp:\/\/www.geocities.com\/aldy0169\/images\/denim.jpg","install_details":"drop it in your ~\/.vim\/colors directory\r\n:colorscheme denim","5":"drop it in your ~\/.vim\/colors directory\r\n:colorscheme denim","first_name":"Timothy","6":"Timothy","last_name":"Aldrich","7":"Aldrich","releases":[{"0":"375","vim_version":"6.0","1":"6.0","script_version":"1","2":"1","version_comment":"Initial upload","3":"Initial upload","package":"denim.vim","4":"denim.vim","src_id":"1117","5":"1117","creation_date":"1029229974","6":"1029229974"}]},"374":{"script_id":"374","0":"374","script_name":"indent\/ruby.vim","1":"indent\/ruby.vim","script_type":"indent","2":"indent","summary":"The official indent\/ruby.vim","3":"The official indent\/ruby.vim","description":"This is the official ftplugin intended for installation in the *global* indent directory. \r\n\r\nIt fixes a bug in the version included with Vim 6.1.  (Comment ending in [,.*(] screws\r\nup the indenting for the next line(s).) \r\n","4":"This is the official ftplugin intended for installation in the *global* indent directory. \r\n\r\nIt fixes a bug in the version included with Vim 6.1.  (Comment ending in [,.*(] screws\r\nup the indenting for the next line(s).) \r\n","install_details":"This is a global ftplugin.  Overwrite your $VIMRUNTIME\/indent\/ruby.vim with this one.","5":"This is a global ftplugin.  Overwrite your $VIMRUNTIME\/indent\/ruby.vim with this one.","first_name":"Gavin","6":"Gavin","last_name":"Sinclair","7":"Sinclair","releases":[{"0":"374","vim_version":"6.0","1":"6.0","script_version":"1.1","2":"1.1","version_comment":"Initial upload","3":"Initial upload","package":"ruby.vim","4":"ruby.vim","src_id":"1116","5":"1116","creation_date":"1029228919","6":"1029228919"}]},"373":{"script_id":"373","0":"373","script_name":"ftplugin\/ruby.vim","1":"ftplugin\/ruby.vim","script_type":"ftplugin","2":"ftplugin","summary":"The official ftplugin\/ruby.vim","3":"The official ftplugin\/ruby.vim","description":"This is the official ftplugin intended for installation in the *global* ftplugin directory.\r\n\r\nIt contains *no* settings, as no settings\/mappings are known that transcend personal taste\r\nto become globally useful Ruby settings.\r\n\r\nThe version included in Vim 6.1 sets shiftwidth and formatoptions, which is inappropriate.","4":"This is the official ftplugin intended for installation in the *global* ftplugin directory.\r\n\r\nIt contains *no* settings, as no settings\/mappings are known that transcend personal taste\r\nto become globally useful Ruby settings.\r\n\r\nThe version included in Vim 6.1 sets shiftwidth and formatoptions, which is inappropriate.","install_details":"This is a global ftplugin.  Overwrite your $VIMRUNTIME\/ftplugin\/ruby.vim with this one.","5":"This is a global ftplugin.  Overwrite your $VIMRUNTIME\/ftplugin\/ruby.vim with this one.","first_name":"Gavin","6":"Gavin","last_name":"Sinclair","7":"Sinclair","releases":[{"0":"373","vim_version":"6.0","1":"6.0","script_version":"1.1","2":"1.1","version_comment":"Initial upload","3":"Initial upload","package":"ruby.vim","4":"ruby.vim","src_id":"1115","5":"1115","creation_date":"1029228587","6":"1029228587"}]},"372":{"script_id":"372","0":"372","script_name":"Red Black","1":"Red Black","script_type":"color scheme","2":"color scheme","summary":"A red and black color scheme","3":"A red and black color scheme","description":"A red and black color scheme.","4":"A red and black color scheme.","install_details":"Place it in the colors directory","5":"Place it in the colors directory","first_name":"Little","6":"Little","last_name":"Dragon","7":"Dragon","releases":[{"0":"372","vim_version":"6.0","1":"6.0","script_version":"1","2":"1","version_comment":"Initial upload","3":"Initial upload","package":"redblack.vim","4":"redblack.vim","src_id":"1113","5":"1113","creation_date":"1029197237","6":"1029197237"}]},"371":{"script_id":"371","0":"371","script_name":"timstamp.vim","1":"timstamp.vim","script_type":"utility","2":"utility","summary":"Global plugin for automated time stamping","3":"Global plugin for automated time stamping","description":"Content of the help document:\r\n\r\n*timstamp.txt*  Global plugin for automated time stamping - v0.95\r\n\r\nThe timstamp general plugin provides automated time-stamping functionality.\r\n\r\n1. General\t\t    |timstamp_general|\r\n2. Specification format\t    |timstamp_specformat|\r\n3. Default specs\t    |timstamp_default_specs|\r\n4. Control variables\t    |timstamp_control|\r\n\r\n==============================================================================\r\n\r\n1. General\t\t\t\t\t\t*timstamp_general*\r\n\r\nWhenever a file is written, this plugin will look for 'Time-stamp lines'\r\namongst the first and last lines of the file to be written. If any of these\r\nlines contain e.g. ' Time stamp:' or 'Last change:', the plugin will update\r\nthese lines before writing the file.\r\n\r\nThe plugin is fully controlled by the user. It does provide two standard\r\n'Time-stamp line' specifications as well as their replacement spec. The user\r\ncan add additional values as well as remove the default values.\r\n\r\nThe plugin and its documentation file can be installed as described under\r\n|add-global-plugin| and |add-local-help|. Do not forget to run |:helptags|.\r\n\r\n==============================================================================\r\n\r\n2. Specification format\t\t\t\t\t*timstamp_specformat*\r\n\r\nThe specification format for a time-stamp line consists of the {pat} and {sub}\r\nparts required to build the desired substitute command. These {pat} and {sub} \r\nparts must be separated by a \"!\" character.\r\n\r\nAn examplespec may clarify this: \"( Last changed:\\).*$!\\1 %Y %b %d\".\r\nThe {pat} part instructs the plugin to look for any line that ends on\r\n' Last changed: ...'.\r\n\r\nThe {sub} part is passed on to |strftime()|, which (at least at the time I am\r\nwriting this) translates \"%Y %b %d\" into \"2002 Aug 11\". Of course, these would\r\nbe the values at the time of the plugin execution, which is the moment before\r\nwriting the file. Any % tokens known by your version of |strftime()| can be \r\nused.\r\n    \r\nAdditionally, some # tokens have been defined by the plugin. These are\r\nreplaced by their corresponding value after |strftime()| processing and \r\nbefore performing the actual substitutions:\r\n\r\n    #f\tfilename    |timstamp_filename|\r\n    #h  hostname    |timstamp_hostname|\r\n    #H  Hostname    |timstamp_Hostname|\r\n    #n  username    |timstamp_username|\r\n    #u  userid\t    |timstamp_userid|\r\n\r\n#f  filename\t\t\t\t\t\t*timstamp_filename*\r\n\r\n    The #f token is replaced by the filename of the current buffer. This is a\r\n    name without any path components.\r\n\r\n#h  hostname\t\t\t\t\t\t*timstamp_hostname*\r\n\r\n    The #h token is replaced by the hostname of the current vim process. \r\n   \r\n    The user can specify the desired value with the glabal variable\r\n    g:timstamp_hostname. If that variable does not exist, the value of the\r\n    $HOSTNAME environment variable will be used. If there is no $HOSTNAME, the\r\n    output of the hostname() function is used. However, only the last word\r\n    returned by that function is preserved. The platform type of qualifier\r\n    (e.g. PC) is not kept.\r\n\r\n#H  Hostname\t\t\t\t\t\t*timstamp_Hostname*\r\n\r\n    The #H token is also replaced by the hostname. However, the platform\r\n    qualifier is not removed.\r\n\r\n#n  username\t\t\t\t\t\t*timstamp_username*\r\n\r\n    The #n token will be replaced by the user name. This will be obtained from\r\n    the g:timstamp_username variable if it exists. Otherwise, it is\r\n    initialised from the $USERNAME environment variable.    \r\n\r\n#u  userid\t\t\t\t\t\t*timstamp_userid*\r\n\r\n    The #u token will be replaced by the userid. This will be obtained from\r\n    the g:timstamp_userid variable if it exists. Otherwise, it is\r\n    initialised from the $LOGNAME environment variable. \r\n    \r\n==============================================================================\r\n\r\n3. Default specs\t\t\t\t    *timstamp_default_specs*\r\n\r\nThe plugin defines two default specs, which can be overwritten by the user:\r\n\r\n    Last Change Spec   |timstamp_last_change_spec|\r\n    Time Stamp spec    |timstamp_time_stamp_spec|\r\n    \r\n3.1. Last Change Spec\t\t\t\t*timstamp_last_change_spec*\r\n\t\r\n    The last change spec has following default value:\r\n\r\n    '\\( Last \\?\\(changed\\?\\|modified\\):\\).*$!\\1 %Y %b %d' \r\n\t\r\n    which can be overruled by providing a different value in the \r\n    g:timstamp_1 variable.\r\n\r\n    The {pat} part is '\\( Last \\?\\(changed\\?\\|modified\\):\\).*$'. This will \r\n    process lines containing ' Last changed', ' Last modified' or its \r\n    variations.\r\n\r\n    The {sub} part is '\\1 %Y %b %d'. This will preserve the ' Last ...:' \r\n    string and replace the remainder with the current 4 digit year, \r\n    the short month name and the day of month. \r\n\r\n    This file contains a 'Last Change' line at |timstamp_examples|.\r\n\t\r\n3.2. Time Stamp spec\t\t\t\t    *timstamp_time_stamp_spec*\r\n\r\n    The time stamp spec is a bit more complex:\r\n\r\n\t'\\( Time[- ]\\?stamp:\\).*$!\\1 <#f %a %Y\/%m\/%d %H:%M:%S #u #h>'\r\n\r\n    and can be overruled by defining the global g:timstamp_2 variable.\r\n\r\n    The {pat} part is shorter: '\\( Time[- ]\\?stamp: \\)<.*>$'. It will trigger \r\n    on lines containing ' Time-stamp', ' Time stamp' or ' Timestamp'\r\n    immediately followed by a ':'.\r\n\r\n    The {sub} part is '\\1 <#f %a %Y\/%m\/%d %H:%M:%S #u #h>'. This will \r\n    preserve the ' Time...:' string, and replace the remainder of the line \r\n    with e.g. ' <timstamp.txt Sun 2002\/08\/11 13:03:01 guivho BTM4BZ>'. Please\r\n    refer to the |timstamp_specformat| above for the # tokens.\r\n\r\n    This file contains a 'Time stamp' line at |timstamp_examples|.\r\n\r\n==============================================================================\r\n\r\n4. Control variables\t\t\t\t\t*timstamp_control*\r\n\r\nThe plugin can be fully controlled by the user. Each of the internal variables\r\nthat control the operation, can be overruled by providing a corresponding\r\nglobal value.\r\n\r\n    g:timstamp_1, \r\n    g:timstamp_2, \r\n    g:timstamp_...\t    |timstamp_specs|\r\n    g:timstamp_automask\t    |timstamp_automask|\r\n    g:timstamp_hostname\t    |timstamp_hostname|\r\n    g:timstamp_Hostname\t    |timstamp_Hostname|\r\n    g:timstamp_ignorecase   |timstamp_ignorecase|\r\n    g:timstamp_language\t    |timstamp_language|\r\n    g:timstamp_modelines    |timstamp_modelines|\r\n    g:timstamp_userid\t    |timstamp_userid|\r\n    g:timstamp_username\t    |timstamp_username|\r\n\r\n4.1. g:timstamp_1, g:timstamp_2, g:timstamp_...\t\t    *timstamp_specs*\r\n\r\nThe |timstamp_default_specs| section has described the two default specs\r\nprovided by the plugin. If the user is happy with those two specs, no entry is\r\nrequired in the .vimrc file.\r\n\r\nHowever the user may overrule these default values by defining a g:timstamp_1\r\nand \/ or a g:timstamp_2 variable, e.g:\r\n\r\n    :let g:timstamp_1='\\( Last change:\\).*$!\\1 %A %Y %b %d'\r\n    \r\nif the user would always want to include the day of the week as in\r\n\r\n    ' Last Change: Wednesday 2002 Aug 14'  \r\n\r\nThe user can add additional specs, e.g. a g:timstamp_3 etc... :\r\n\r\n    :let g:timstamp_3='\\( Last messed up at:\\).*$\\1 %Y %b %d'\r\n\r\nfor those files that are still in early development? :-)\r\n    \r\n\r\nNote that the first empty or not existing spec will terminate processing.\r\n\r\nIf e.g. a g:timstamp_3 has been defined, but g:timstamp_2 has been set to \"\" \r\nprocessing will not continue beyond g:timstamp_2. On the other hand, if the\r\nfirst two specs are non empty (either while they have not been overruled, or \r\nas they have been replaced by a non empty value), processing will continue \r\nwith g:timstamp_3, g:timstamp_4, g:timstamp_5 ... as long as each consecutive \r\nvariable exists and has a non empty value.\r\n\r\n4.2. g:timstamp_automask\t\t\t\t*timstamp_automask*\r\n\r\nBy default, the plugin installs an \"autocommand BufWrite\" for all files. So it\r\nuses '*' as {pat} (cfr |:autocmd|). The user can overrule this behaviour by\r\ndefining g:timstamp_automask with the desired value, e.g.:\r\n\r\n    :let g:timstamp_automask = \"*.html\"\r\n>\r\nto limit timestamping to html files.\r\n\r\n4.3. g:timstamp_hostname\t\t\t    Cfr |timstamp_hostname|.\r\n\r\n4.4. g:timstamp_Hostname\t\t\t    Cfr |timstamp_Hostname|.\r\n\r\n4.5. g:timstamp_ignorecase\t\t\t\t*timstamp_ignorecase*\r\n\r\nThe plugin ignores case when performing the eventual substitution. \r\nSo ' lAsT cHanGe:' is as valid as ' Last Change:'. The user can prevent this\r\nby defining global variable g:timstamp_ignorecase to an empty value: <\r\n\r\n    :let g:timstamp_ignorecase = \"\"\r\n>\r\n\r\n4.6. g:timstamp_language\t\t\t\t*timstamp_language*\r\n\r\nThe plugin assumes that one usually wants english timestamps. By default it\r\nexecutes a ':language time en' to achieve this. The user can specify a\r\ndifferent language to be used by means of the g:timstamp_language variable.\r\n\r\n\r\n4.7. g:timstamp_modelines\t\t\t\t*timstamp_modelines*\r\n\r\nThe plugin uses the value of the |'modelines'| option to define the number of\r\nhead or tail lines to be taken into account. The user can specify a different\r\nvalue by means of the g:timstamp_modelines variable. \r\n\r\nThis can even be set to '$' if all file lines have to be taken into account.\r\nBe aware that this would change any line that matches any of your\r\n|timspec_specs|. This may be more than you would expect.\r\n\r\n4.8. g:timstamp_userid\t\t\t\t    Cfr |timstamp_userid|\r\n\r\n4.9. g:timstamp_username\t\t\t    Cfr |timstamp_username|\r\n\r\n==============================================================================\r\n\r\n\t\t\t\t\t\t\t*timstamp_examples*\r\n Version: 0.95\r\n Last change: 2003 Feb 13\r\n Timestamp: <timstamp.txt Thu 2003\/02\/13 22:58:16  MSDOG>\r\n Maintainer: Guido Van Hoecke <Guido@VanHoecke.org>\r\n vim:tw=78:sw=4:ts=8:ft=help:norl:\r\n","4":"Content of the help document:\r\n\r\n*timstamp.txt*  Global plugin for automated time stamping - v0.95\r\n\r\nThe timstamp general plugin provides automated time-stamping functionality.\r\n\r\n1. General\t\t    |timstamp_general|\r\n2. Specification format\t    |timstamp_specformat|\r\n3. Default specs\t    |timstamp_default_specs|\r\n4. Control variables\t    |timstamp_control|\r\n\r\n==============================================================================\r\n\r\n1. General\t\t\t\t\t\t*timstamp_general*\r\n\r\nWhenever a file is written, this plugin will look for 'Time-stamp lines'\r\namongst the first and last lines of the file to be written. If any of these\r\nlines contain e.g. ' Time stamp:' or 'Last change:', the plugin will update\r\nthese lines before writing the file.\r\n\r\nThe plugin is fully controlled by the user. It does provide two standard\r\n'Time-stamp line' specifications as well as their replacement spec. The user\r\ncan add additional values as well as remove the default values.\r\n\r\nThe plugin and its documentation file can be installed as described under\r\n|add-global-plugin| and |add-local-help|. Do not forget to run |:helptags|.\r\n\r\n==============================================================================\r\n\r\n2. Specification format\t\t\t\t\t*timstamp_specformat*\r\n\r\nThe specification format for a time-stamp line consists of the {pat} and {sub}\r\nparts required to build the desired substitute command. These {pat} and {sub} \r\nparts must be separated by a \"!\" character.\r\n\r\nAn examplespec may clarify this: \"( Last changed:\\).*$!\\1 %Y %b %d\".\r\nThe {pat} part instructs the plugin to look for any line that ends on\r\n' Last changed: ...'.\r\n\r\nThe {sub} part is passed on to |strftime()|, which (at least at the time I am\r\nwriting this) translates \"%Y %b %d\" into \"2002 Aug 11\". Of course, these would\r\nbe the values at the time of the plugin execution, which is the moment before\r\nwriting the file. Any % tokens known by your version of |strftime()| can be \r\nused.\r\n    \r\nAdditionally, some # tokens have been defined by the plugin. These are\r\nreplaced by their corresponding value after |strftime()| processing and \r\nbefore performing the actual substitutions:\r\n\r\n    #f\tfilename    |timstamp_filename|\r\n    #h  hostname    |timstamp_hostname|\r\n    #H  Hostname    |timstamp_Hostname|\r\n    #n  username    |timstamp_username|\r\n    #u  userid\t    |timstamp_userid|\r\n\r\n#f  filename\t\t\t\t\t\t*timstamp_filename*\r\n\r\n    The #f token is replaced by the filename of the current buffer. This is a\r\n    name without any path components.\r\n\r\n#h  hostname\t\t\t\t\t\t*timstamp_hostname*\r\n\r\n    The #h token is replaced by the hostname of the current vim process. \r\n   \r\n    The user can specify the desired value with the glabal variable\r\n    g:timstamp_hostname. If that variable does not exist, the value of the\r\n    $HOSTNAME environment variable will be used. If there is no $HOSTNAME, the\r\n    output of the hostname() function is used. However, only the last word\r\n    returned by that function is preserved. The platform type of qualifier\r\n    (e.g. PC) is not kept.\r\n\r\n#H  Hostname\t\t\t\t\t\t*timstamp_Hostname*\r\n\r\n    The #H token is also replaced by the hostname. However, the platform\r\n    qualifier is not removed.\r\n\r\n#n  username\t\t\t\t\t\t*timstamp_username*\r\n\r\n    The #n token will be replaced by the user name. This will be obtained from\r\n    the g:timstamp_username variable if it exists. Otherwise, it is\r\n    initialised from the $USERNAME environment variable.    \r\n\r\n#u  userid\t\t\t\t\t\t*timstamp_userid*\r\n\r\n    The #u token will be replaced by the userid. This will be obtained from\r\n    the g:timstamp_userid variable if it exists. Otherwise, it is\r\n    initialised from the $LOGNAME environment variable. \r\n    \r\n==============================================================================\r\n\r\n3. Default specs\t\t\t\t    *timstamp_default_specs*\r\n\r\nThe plugin defines two default specs, which can be overwritten by the user:\r\n\r\n    Last Change Spec   |timstamp_last_change_spec|\r\n    Time Stamp spec    |timstamp_time_stamp_spec|\r\n    \r\n3.1. Last Change Spec\t\t\t\t*timstamp_last_change_spec*\r\n\t\r\n    The last change spec has following default value:\r\n\r\n    '\\( Last \\?\\(changed\\?\\|modified\\):\\).*$!\\1 %Y %b %d' \r\n\t\r\n    which can be overruled by providing a different value in the \r\n    g:timstamp_1 variable.\r\n\r\n    The {pat} part is '\\( Last \\?\\(changed\\?\\|modified\\):\\).*$'. This will \r\n    process lines containing ' Last changed', ' Last modified' or its \r\n    variations.\r\n\r\n    The {sub} part is '\\1 %Y %b %d'. This will preserve the ' Last ...:' \r\n    string and replace the remainder with the current 4 digit year, \r\n    the short month name and the day of month. \r\n\r\n    This file contains a 'Last Change' line at |timstamp_examples|.\r\n\t\r\n3.2. Time Stamp spec\t\t\t\t    *timstamp_time_stamp_spec*\r\n\r\n    The time stamp spec is a bit more complex:\r\n\r\n\t'\\( Time[- ]\\?stamp:\\).*$!\\1 <#f %a %Y\/%m\/%d %H:%M:%S #u #h>'\r\n\r\n    and can be overruled by defining the global g:timstamp_2 variable.\r\n\r\n    The {pat} part is shorter: '\\( Time[- ]\\?stamp: \\)<.*>$'. It will trigger \r\n    on lines containing ' Time-stamp', ' Time stamp' or ' Timestamp'\r\n    immediately followed by a ':'.\r\n\r\n    The {sub} part is '\\1 <#f %a %Y\/%m\/%d %H:%M:%S #u #h>'. This will \r\n    preserve the ' Time...:' string, and replace the remainder of the line \r\n    with e.g. ' <timstamp.txt Sun 2002\/08\/11 13:03:01 guivho BTM4BZ>'. Please\r\n    refer to the |timstamp_specformat| above for the # tokens.\r\n\r\n    This file contains a 'Time stamp' line at |timstamp_examples|.\r\n\r\n==============================================================================\r\n\r\n4. Control variables\t\t\t\t\t*timstamp_control*\r\n\r\nThe plugin can be fully controlled by the user. Each of the internal variables\r\nthat control the operation, can be overruled by providing a corresponding\r\nglobal value.\r\n\r\n    g:timstamp_1, \r\n    g:timstamp_2, \r\n    g:timstamp_...\t    |timstamp_specs|\r\n    g:timstamp_automask\t    |timstamp_automask|\r\n    g:timstamp_hostname\t    |timstamp_hostname|\r\n    g:timstamp_Hostname\t    |timstamp_Hostname|\r\n    g:timstamp_ignorecase   |timstamp_ignorecase|\r\n    g:timstamp_language\t    |timstamp_language|\r\n    g:timstamp_modelines    |timstamp_modelines|\r\n    g:timstamp_userid\t    |timstamp_userid|\r\n    g:timstamp_username\t    |timstamp_username|\r\n\r\n4.1. g:timstamp_1, g:timstamp_2, g:timstamp_...\t\t    *timstamp_specs*\r\n\r\nThe |timstamp_default_specs| section has described the two default specs\r\nprovided by the plugin. If the user is happy with those two specs, no entry is\r\nrequired in the .vimrc file.\r\n\r\nHowever the user may overrule these default values by defining a g:timstamp_1\r\nand \/ or a g:timstamp_2 variable, e.g:\r\n\r\n    :let g:timstamp_1='\\( Last change:\\).*$!\\1 %A %Y %b %d'\r\n    \r\nif the user would always want to include the day of the week as in\r\n\r\n    ' Last Change: Wednesday 2002 Aug 14'  \r\n\r\nThe user can add additional specs, e.g. a g:timstamp_3 etc... :\r\n\r\n    :let g:timstamp_3='\\( Last messed up at:\\).*$\\1 %Y %b %d'\r\n\r\nfor those files that are still in early development? :-)\r\n    \r\n\r\nNote that the first empty or not existing spec will terminate processing.\r\n\r\nIf e.g. a g:timstamp_3 has been defined, but g:timstamp_2 has been set to \"\" \r\nprocessing will not continue beyond g:timstamp_2. On the other hand, if the\r\nfirst two specs are non empty (either while they have not been overruled, or \r\nas they have been replaced by a non empty value), processing will continue \r\nwith g:timstamp_3, g:timstamp_4, g:timstamp_5 ... as long as each consecutive \r\nvariable exists and has a non empty value.\r\n\r\n4.2. g:timstamp_automask\t\t\t\t*timstamp_automask*\r\n\r\nBy default, the plugin installs an \"autocommand BufWrite\" for all files. So it\r\nuses '*' as {pat} (cfr |:autocmd|). The user can overrule this behaviour by\r\ndefining g:timstamp_automask with the desired value, e.g.:\r\n\r\n    :let g:timstamp_automask = \"*.html\"\r\n>\r\nto limit timestamping to html files.\r\n\r\n4.3. g:timstamp_hostname\t\t\t    Cfr |timstamp_hostname|.\r\n\r\n4.4. g:timstamp_Hostname\t\t\t    Cfr |timstamp_Hostname|.\r\n\r\n4.5. g:timstamp_ignorecase\t\t\t\t*timstamp_ignorecase*\r\n\r\nThe plugin ignores case when performing the eventual substitution. \r\nSo ' lAsT cHanGe:' is as valid as ' Last Change:'. The user can prevent this\r\nby defining global variable g:timstamp_ignorecase to an empty value: <\r\n\r\n    :let g:timstamp_ignorecase = \"\"\r\n>\r\n\r\n4.6. g:timstamp_language\t\t\t\t*timstamp_language*\r\n\r\nThe plugin assumes that one usually wants english timestamps. By default it\r\nexecutes a ':language time en' to achieve this. The user can specify a\r\ndifferent language to be used by means of the g:timstamp_language variable.\r\n\r\n\r\n4.7. g:timstamp_modelines\t\t\t\t*timstamp_modelines*\r\n\r\nThe plugin uses the value of the |'modelines'| option to define the number of\r\nhead or tail lines to be taken into account. The user can specify a different\r\nvalue by means of the g:timstamp_modelines variable. \r\n\r\nThis can even be set to '$' if all file lines have to be taken into account.\r\nBe aware that this would change any line that matches any of your\r\n|timspec_specs|. This may be more than you would expect.\r\n\r\n4.8. g:timstamp_userid\t\t\t\t    Cfr |timstamp_userid|\r\n\r\n4.9. g:timstamp_username\t\t\t    Cfr |timstamp_username|\r\n\r\n==============================================================================\r\n\r\n\t\t\t\t\t\t\t*timstamp_examples*\r\n Version: 0.95\r\n Last change: 2003 Feb 13\r\n Timestamp: <timstamp.txt Thu 2003\/02\/13 22:58:16  MSDOG>\r\n Maintainer: Guido Van Hoecke <Guido@VanHoecke.org>\r\n vim:tw=78:sw=4:ts=8:ft=help:norl:\r\n","install_details":"The plugin and its documentation file can be installed as described under |add-global-plugin| and |add-local-help|. Do not forget to run |:helptags|.\r\n\r\nNote: the 'detailed description' above is a copy of the accompanying timstamp.txt help file. \r\n","5":"The plugin and its documentation file can be installed as described under |add-global-plugin| and |add-local-help|. Do not forget to run |:helptags|.\r\n\r\nNote: the 'detailed description' above is a copy of the accompanying timstamp.txt help file. \r\n","first_name":"Guido","6":"Guido","last_name":"Van Hoecke","7":"Van Hoecke","releases":[{"0":"371","vim_version":"6.0","1":"6.0","script_version":"0.95","2":"0.95","version_comment":"1) Replaced s:filename() by call to builtin fnamemodify()\r\n2) Added license statement\r\n3) Now processes g:timstamp_3 etc by copying them into \r\n    s:timestamp_3 at the beginning of the script\r\n    (Thanks to Norihiko Murase)\r\n4) Fixed two documentation typos (Thanks to Norihiko Murase)\r\n","3":"1) Replaced s:filename() by call to builtin fnamemodify()\r\n2) Added license statement\r\n3) Now processes g:timstamp_3 etc by copying them into \r\n    s:timestamp_3 at the beginning of the script\r\n    (Thanks to Norihiko Murase)\r\n4) Fixed two documentation typos (Thanks to Norihiko Murase)\r\n","package":"timstamp.zip","4":"timstamp.zip","src_id":"1730","5":"1730","creation_date":"1045145224","6":"1045145224"},{"0":"371","vim_version":"6.0","1":"6.0","script_version":"0.94","2":"0.94","version_comment":"1) Added a missing 'let' in an assignment statement. (reported by Luis Jure)\r\n2) Added additional warning in the help file about  '$' value for g:timstamp_modelines.  \r\nCfr :h timstamp_modelines\r\n3) Corrected s:filename() to also work with dos slashes. (thanks to Richard Bair)\r\n","3":"1) Added a missing 'let' in an assignment statement. (reported by Luis Jure)\r\n2) Added additional warning in the help file about  '$' value for g:timstamp_modelines.  \r\nCfr :h timstamp_modelines\r\n3) Corrected s:filename() to also work with dos slashes. (thanks to Richard Bair)\r\n","package":"timstamp.zip","4":"timstamp.zip","src_id":"1129","5":"1129","creation_date":"1029403047","6":"1029403047"},{"0":"371","vim_version":"6.0","1":"6.0","script_version":"0.93","2":"0.93","version_comment":"Now only presents the %token part of the spec to strftime(): this seems to provide correct results, even when using %Z to add the timezone followed by '>'\r\nThe helpfile has been extended with some example specs.\r\n(error and help reported\/requested by Adrian Nagle)\r\n","3":"Now only presents the %token part of the spec to strftime(): this seems to provide correct results, even when using %Z to add the timezone followed by '>'\r\nThe helpfile has been extended with some example specs.\r\n(error and help reported\/requested by Adrian Nagle)\r\n","package":"timstamp.zip","4":"timstamp.zip","src_id":"1125","5":"1125","creation_date":"1029337991","6":"1029337991"},{"0":"371","vim_version":"6.0","1":"6.0","script_version":"0.92","2":"0.92","version_comment":"Now uses the line(\"$\") function to test for short files and limits the modifications to the specified nr of modelines rather than that number plus one extra line (Thanks to Piet Delport and Rimon Barr)\r\n","3":"Now uses the line(\"$\") function to test for short files and limits the modifications to the specified nr of modelines rather than that number plus one extra line (Thanks to Piet Delport and Rimon Barr)\r\n","package":"timstamp.zip","4":"timstamp.zip","src_id":"1111","5":"1111","creation_date":"1029144528","6":"1029144528"},{"0":"371","vim_version":"6.0","1":"6.0","script_version":"0.91","2":"0.91","version_comment":"version 0.91 now preserves the cursor location, is silent! about language setting, and does no longer choke on short files \r\n\r\n","3":"version 0.91 now preserves the cursor location, is silent! about language setting, and does no longer choke on short files \r\n\r\n","package":"timstamp.zip","4":"timstamp.zip","src_id":"1110","5":"1110","creation_date":"1029066796","6":"1029066796"},{"0":"371","vim_version":"6.0","1":"6.0","script_version":"0.9","2":"0.9","version_comment":"Initial upload","3":"Initial upload","package":"timstamp.zip","4":"timstamp.zip","src_id":"1109","5":"1109","creation_date":"1029046126","6":"1029046126"}]},"370":{"script_id":"370","0":"370","script_name":"Expmod","1":"Expmod","script_type":"utility","2":"utility","summary":"explorer.vim modification for viewing files and relative path","3":"explorer.vim modification for viewing files and relative path","description":"expatch adds 2 new commands to explorer.vim: v and g\r\nv - view graphic file\r\ng - get full file name and store it in global variable\r\n\r\nIt works also with mouse and <Enter>:\r\nv == <2-LeftMouse> == <Enter> (if file is graphic file)\r\ng == <2-S-LeftMouse>\r\n\r\nexpmod.vim takes care about global variable. Behaviour of <F8> depends\r\non file name and file type of current buffer. The most dramatic effects\r\nare if ft=html.\r\nFor graphic files it _o_pens new line and inserts:\r\n<img src=\"relative_path\" width=\"100\" height=\"100\" alt=\"short_file_name\"\r\nborder=\"0\">\r\n\r\nrelative_path is a relative path from edited file to graphic file. E.g.\r\n\"..\/images\/alpha.gif\"\r\ndimensions are given by identify\r\nshort_file_name is short file name ;)\r\nborder is default value.\r\n\r\nFor all other files it inserts:\r\n<a href=\"relative_path\" class=\"\">\r\n\r\n<F8> works also for other 'ft' values:\r\nFor php: include(\"relative_path\");\r\nFor c: #include <relative_path>\r\n","4":"expatch adds 2 new commands to explorer.vim: v and g\r\nv - view graphic file\r\ng - get full file name and store it in global variable\r\n\r\nIt works also with mouse and <Enter>:\r\nv == <2-LeftMouse> == <Enter> (if file is graphic file)\r\ng == <2-S-LeftMouse>\r\n\r\nexpmod.vim takes care about global variable. Behaviour of <F8> depends\r\non file name and file type of current buffer. The most dramatic effects\r\nare if ft=html.\r\nFor graphic files it _o_pens new line and inserts:\r\n<img src=\"relative_path\" width=\"100\" height=\"100\" alt=\"short_file_name\"\r\nborder=\"0\">\r\n\r\nrelative_path is a relative path from edited file to graphic file. E.g.\r\n\"..\/images\/alpha.gif\"\r\ndimensions are given by identify\r\nshort_file_name is short file name ;)\r\nborder is default value.\r\n\r\nFor all other files it inserts:\r\n<a href=\"relative_path\" class=\"\">\r\n\r\n<F8> works also for other 'ft' values:\r\nFor php: include(\"relative_path\");\r\nFor c: #include <relative_path>\r\n","install_details":"This is version for *nix systems. It can be easily modified for other\r\nsystems. Alas, it is rather impossible to create one cross-system\r\nversion since this plugin depends on external tools:\r\n- xli for viewing graphic files (I believe it is in all systems with\r\n  XFree)  \r\n- identify from ImageMagick package for image dimensions\r\n\r\nexpatch is a patch for regular explorer.vim\r\npatch explorer.vim < expatch\r\n\r\nexpmod.vim is a plugin file. \r\nDrop it into your plugin directory.\r\n","5":"This is version for *nix systems. It can be easily modified for other\r\nsystems. Alas, it is rather impossible to create one cross-system\r\nversion since this plugin depends on external tools:\r\n- xli for viewing graphic files (I believe it is in all systems with\r\n  XFree)  \r\n- identify from ImageMagick package for image dimensions\r\n\r\nexpatch is a patch for regular explorer.vim\r\npatch explorer.vim < expatch\r\n\r\nexpmod.vim is a plugin file. \r\nDrop it into your plugin directory.\r\n","first_name":"Mikolaj","6":"Mikolaj","last_name":"Machowski","7":"Machowski","releases":[{"0":"370","vim_version":"6.0","1":"6.0","script_version":"0.3","2":"0.3","version_comment":"Initial upload","3":"Initial upload","package":"expmod.zip","4":"expmod.zip","src_id":"1108","5":"1108","creation_date":"1028994719","6":"1028994719"}]},"369":{"script_id":"369","0":"369","script_name":"atomcoder","1":"atomcoder","script_type":"utility","2":"utility","summary":"Atomcoder Development Environment","3":"Atomcoder Development Environment","description":"Atomcoder Vim Scripts \r\n\r\nProblem: \r\n- with Vim map we cannot map \"ab\" if \"a\" is already mapped.\r\n- with Vim map there is no chance for correction if we made a typo.\r\n- with Vim map we need to prefix with Vim mapleader key as a lot of single characters are already mapped by default.\r\n\r\nSolution:\r\n- rename the mappings using underscore \"_\" as prefix and suffix.\r\n- call a Vim command using argument like \"java\" or \"javac\" which in turns call a Vim function which calls the respective mapping.\r\n- map the Vim command to a special key like Enter key <CR>\r\n- after entering the argument like \"java\", press Enter key <CR> again to execute it\r\n- we may be able extend this to allow passing parameters like \"build\" to execute an external \"ant build\" command instead of mapping each Ant target.\r\n\r\nEnter Vim commands like game cheat codes, press Enter then type command. Commands are entered in command line and not as maps. This means you could correct typing mistakes before invoking the command.\r\n\r\nJust my various Vim settings, mappings, functions for Java Programming.\r\n\r\nPress Enter (<CR>) invokes \":Vim\" prompt in command line. \":Vim\" calls the \"Vim\" function. Then type \"lc<CR>\" to line comment the current line (or highlighted lines) of Java, Vim, XML code. \"<CR>nlc<CR>\" will uncomment it.\r\n\r\nSome \":Vim\" commands:\r\n- tt - toggle tomcat\r\n- tr - tomcat shutdown tomcat startup\r\n- te - tomcat shutdown\r\n- cvsd - cvs diff on current file\r\n- cvsci - cvs ci\r\n- cvsru - :del % then cvs up\r\n- cvstF - cvs tag -F with hardcoded tag\r\n- cvsup - cvs up\r\n- cvsv - cvs up -p\r\n- cvslga - cvs log\r\n- cd - cd to directory containing current file\r\n\r\nSome maps:\r\n- <F8> - :!ant work-webapp\r\n- <F9> - :!ant work-compile\r\n- p - works more like mswin <C-V> when text is highlighted\r\n- g\/ - put current word in the \"\/ register so that a substring that matches it gets highligthed\r\n- g? - put current word in the \"\/ register so that a word that matches it gets highligthed\r\n- ZR :e!<CR>\r\n- ZU :up<CR>\r\n- ZZ <Nop>\r\n- ZD :bd!<CR>\r\n- ZC :bd<CR>\r\n\r\nJava\r\n- typing \"sout\" in insert mode will expand to \"System.out.println();\" with cursor put in between \"()\"\r\n- \"vmain\" -> \"public static void main(String[] args)\"\r\n- \"pst\" -> \"printStackTrace()\"\r\n\r\n","4":"Atomcoder Vim Scripts \r\n\r\nProblem: \r\n- with Vim map we cannot map \"ab\" if \"a\" is already mapped.\r\n- with Vim map there is no chance for correction if we made a typo.\r\n- with Vim map we need to prefix with Vim mapleader key as a lot of single characters are already mapped by default.\r\n\r\nSolution:\r\n- rename the mappings using underscore \"_\" as prefix and suffix.\r\n- call a Vim command using argument like \"java\" or \"javac\" which in turns call a Vim function which calls the respective mapping.\r\n- map the Vim command to a special key like Enter key <CR>\r\n- after entering the argument like \"java\", press Enter key <CR> again to execute it\r\n- we may be able extend this to allow passing parameters like \"build\" to execute an external \"ant build\" command instead of mapping each Ant target.\r\n\r\nEnter Vim commands like game cheat codes, press Enter then type command. Commands are entered in command line and not as maps. This means you could correct typing mistakes before invoking the command.\r\n\r\nJust my various Vim settings, mappings, functions for Java Programming.\r\n\r\nPress Enter (<CR>) invokes \":Vim\" prompt in command line. \":Vim\" calls the \"Vim\" function. Then type \"lc<CR>\" to line comment the current line (or highlighted lines) of Java, Vim, XML code. \"<CR>nlc<CR>\" will uncomment it.\r\n\r\nSome \":Vim\" commands:\r\n- tt - toggle tomcat\r\n- tr - tomcat shutdown tomcat startup\r\n- te - tomcat shutdown\r\n- cvsd - cvs diff on current file\r\n- cvsci - cvs ci\r\n- cvsru - :del % then cvs up\r\n- cvstF - cvs tag -F with hardcoded tag\r\n- cvsup - cvs up\r\n- cvsv - cvs up -p\r\n- cvslga - cvs log\r\n- cd - cd to directory containing current file\r\n\r\nSome maps:\r\n- <F8> - :!ant work-webapp\r\n- <F9> - :!ant work-compile\r\n- p - works more like mswin <C-V> when text is highlighted\r\n- g\/ - put current word in the \"\/ register so that a substring that matches it gets highligthed\r\n- g? - put current word in the \"\/ register so that a word that matches it gets highligthed\r\n- ZR :e!<CR>\r\n- ZU :up<CR>\r\n- ZZ <Nop>\r\n- ZD :bd!<CR>\r\n- ZC :bd<CR>\r\n\r\nJava\r\n- typing \"sout\" in insert mode will expand to \"System.out.println();\" with cursor put in between \"()\"\r\n- \"vmain\" -> \"public static void main(String[] args)\"\r\n- \"pst\" -> \"printStackTrace()\"\r\n\r\n","install_details":"CVS commands requires Cygwin.\r\nTo Install: Put all .vim files into  $VIM\/vimfiles\/plugin directory like \"C:\\Program Files (x86)\\vim\\vimfiles\\plugin\". Try not to delete this folder when upgrading to newer Vim version.","5":"CVS commands requires Cygwin.\r\nTo Install: Put all .vim files into  $VIM\/vimfiles\/plugin directory like \"C:\\Program Files (x86)\\vim\\vimfiles\\plugin\". Try not to delete this folder when upgrading to newer Vim version.","first_name":"Simon","6":"Simon","last_name":"Chiu","7":"Chiu","releases":[{"0":"369","vim_version":"8.0","1":"8.0","script_version":"4","2":"4","version_comment":"Added Run function mapped to F5. If filetype is vim, will source %. else execute a run.bat file in windows shell.\r\nCode for run.bat: ..\\\\maven\\\\bin\\\\mvn clean package &  choice \/T 60 \/D Y \/M \"Close (60s)\" & if errorlevel 2 pause\r\n","3":"Added Run function mapped to F5. If filetype is vim, will source %. else execute a run.bat file in windows shell.\r\nCode for run.bat: ..\\\\maven\\\\bin\\\\mvn clean package &  choice \/T 60 \/D Y \/M \"Close (60s)\" & if errorlevel 2 pause\r\n","package":"atomcoder.zip","4":"atomcoder.zip","src_id":"25448","5":"25448","creation_date":"1501089869","6":"1501089869"},{"0":"369","vim_version":"8.0","1":"8.0","script_version":"3","2":"3","version_comment":"merge gui_mswin.vim with environment.vim, rename environment.vim to atomcoder.vim, other files with atomcoder prefix\r\n","3":"merge gui_mswin.vim with environment.vim, rename environment.vim to atomcoder.vim, other files with atomcoder prefix\r\n","package":"atomcoder.zip","4":"atomcoder.zip","src_id":"25332","5":"25332","creation_date":"1498092505","6":"1498092505"},{"0":"369","vim_version":"6.0","1":"6.0","script_version":"2","2":"2","version_comment":"Fix color for Windows Terminal Client.","3":"Fix color for Windows Terminal Client.","package":"atomcoder-vim-2.zip","4":"atomcoder-vim-2.zip","src_id":"2408","5":"2408","creation_date":"1066329743","6":"1066329743"},{"0":"369","vim_version":"6.0","1":"6.0","script_version":"1","2":"1","version_comment":"environment, java, cvs, local_mswin, gui_mswin","3":"environment, java, cvs, local_mswin, gui_mswin","package":"atomcoder-1.zip","4":"atomcoder-1.zip","src_id":"1100","5":"1100","creation_date":"1028861589","6":"1028861589"}]},"368":{"script_id":"368","0":"368","script_name":"oceandeep","1":"oceandeep","script_type":"color scheme","2":"color scheme","summary":"dark colorscheme, pleasant, mainly blue and blueish-green","3":"dark colorscheme, pleasant, mainly blue and blueish-green","description":"dark colorscheme, pleasant, mainly blue and blueish-green,\r\nbased on Nightshimmer (vimscript #328) by Niklas Lindstr\u00c3\u00b6m (http:\/\/vim.sourceforge.net\/profile.php?user_id=577);\r\n\r\nYou'll find a screenshot at my place over here:\r\nhttp:\/\/www.tomsdiner.org\/vim\/oceandeep\/index.html\r\n\r\nThanks for voting this up, I'm surprised and delighted that you like this scheme as much as I do :-)","4":"dark colorscheme, pleasant, mainly blue and blueish-green,\r\nbased on Nightshimmer (vimscript #328) by Niklas Lindstr\u00c3\u00b6m (http:\/\/vim.sourceforge.net\/profile.php?user_id=577);\r\n\r\nYou'll find a screenshot at my place over here:\r\nhttp:\/\/www.tomsdiner.org\/vim\/oceandeep\/index.html\r\n\r\nThanks for voting this up, I'm surprised and delighted that you like this scheme as much as I do :-)","install_details":"In Vim 6 upwards, simply drop this into your \"$VIMRUNTIME\/colors\/\" or \"$HOME\/.vim\/colors\/\", then use \":colorscheme oceandeep\". Otherwise, just \":source\" it. \r\n","5":"In Vim 6 upwards, simply drop this into your \"$VIMRUNTIME\/colors\/\" or \"$HOME\/.vim\/colors\/\", then use \":colorscheme oceandeep\". Otherwise, just \":source\" it. \r\n","first_name":"Tom","6":"Tom","last_name":"Regner","7":"Regner","releases":[{"0":"368","vim_version":"6.0","1":"6.0","script_version":"1.2.5","2":"1.2.5","version_comment":"change by Alexei Alexandrov\r\n- highlight CursorColumn\r\n","3":"change by Alexei Alexandrov\r\n- highlight CursorColumn\r\n","package":"oceandeep.vim","4":"oceandeep.vim","src_id":"7799","5":"7799","creation_date":"1192484428","6":"1192484428"}]},"367":{"script_id":"367","0":"367","script_name":"DirDo.vim","1":"DirDo.vim","script_type":"utility","2":"utility","summary":"Performs Vim commands over files recursively under multiple directories.","3":"Performs Vim commands over files recursively under multiple directories.","description":"This plugin is like :argdo but it works recursively under a directory (or\r\nmultiple directories).  The limitation for :argdo is that it does not glob\r\nthe files inside the subdirectories.  DirDo works in a similar manner but\r\nyou're allowed to specify multiple directories (good for refactoring code\r\nand modifying files in a deep hierarchy).  DirDo also globs the files in\r\nthe subdirectories so you can make sure an operation is performed\r\nconsistantly.","4":"This plugin is like :argdo but it works recursively under a directory (or\r\nmultiple directories).  The limitation for :argdo is that it does not glob\r\nthe files inside the subdirectories.  DirDo works in a similar manner but\r\nyou're allowed to specify multiple directories (good for refactoring code\r\nand modifying files in a deep hierarchy).  DirDo also globs the files in\r\nthe subdirectories so you can make sure an operation is performed\r\nconsistantly.","install_details":"REQUIREMENTS:\r\n  - The :argdo command in Vim 6.0\r\nPut this file in your ~\/.vim\/plugin directory.\r\n\r\nThe syntax of the commands:\r\n\r\nFirst we need to set what directory we would like to perform this\r\ncommand on\r\n\r\n    :DirDoDir [\/my\/directory1] [\/my\/directory2] [\/my\/directory3]\r\n\r\n    or\r\n\r\n    :DDD [\/my\/directory1] [\/my\/directory2] [\/my\/directory3]\r\n\r\nIf no argument is given, then it'll display the directories that you're\r\ngoing to work on and let you edit them by separating them with commas\r\n(',')\r\n\r\nYou can also use the following command to add a directory to the DirDoDir\r\nvariable:\r\n\r\n    :DirDoAdd [\/my\/dir]\r\n\r\n    or\r\n\r\n    :DDA [\/my\/dir]\r\n\r\nIf you do not give an argument to DDA, it'll add the current working\r\ndirectory to the DirDoDir variable.\r\n\r\nThen we set the file glob pattern\r\n\r\n    :DirDoPattern [file glob pattern1] [file glob pattern2] ...\r\n\r\n    or\r\n\r\n    :DDP [file glob pattern1] [file glob pattern2] ...\r\n\r\nIf no argument is given, then it'll display the patterns and let you\r\nedit them (separate each pattern with spaces).\r\n\r\nThen, you can do:\r\n\r\n    :DirDo [commands]\r\n\r\n    or\r\n\r\n    :DDO [commands]\r\n\r\nto executes the commands on each file that matches the glob pattern\r\nrecursively under the directories that you have specified.  The format of\r\n[commands] is just like what you do on :argdo. See :help argdo for\r\ndetails.\r\n\r\nIf no argument is given, then it'll reuse the last command.\r\n\r\nExamples:\r\n\r\nReplace all the instaces of \"Foo\" to \"Bar\" in all the Java or C files under\r\nthe directory \/my\/directory and its subdirectories, confirming each match:\r\n\r\n    :DDD \/my\/directory (or just :DDD<CR> and type it in)\r\n    :DDP *.java *.c (or just :DDP<CR> and type it in)\r\n    :DDO %s\/Foo\/Bar\/gce | update\r\n\r\n(See :h argdo for the commands after DDO.)\r\n\r\nSame scenario but replacing \"Bar\" with \"Baz\" without confirmation for each\r\nmatch (note the directory and patterns are saved):\r\n\r\n    :DDO %s\/Bar\/Baz\/ge | update\r\n\r\n(Since 1.2) There is a command called DirDoFast where you can set the\r\ndirectory, pattern, and command at once.  Note that your arguments need to\r\nbe escaped if there is an space to it, otherwise Vim will break up the\r\narguments incorrectly.  The syntax is:\r\n\r\n    :DirDoFast [directories] [patterns] command\r\n\r\n    or\r\n\r\n    :DDF [directories] [patterns] command\r\n\r\nMultiple directories need to be separated by comma.  Patterns need to be\r\nseparated by spaces.  Since space is used by Vim to separate the command\r\narguments, ALL spaces in the directory, pattern, or command need to be\r\nescaped.  For example, the last command using DDF would look like:\r\n\r\n:DDF \/my\/directory *.java\\ *.c %s\/Foo\/Bar\/gce\\ |\\ update\r\n\r\nIf you only give 2 arguments to :DDF, you assume the directory is set to\r\n\".\".\r\n\r\nIf you only give 1 argument to :DDF, you assume the directory is set to\r\n\".\" and the pattern is set to \"*\".\r\n\r\n(Since 1.3) There is a command called DirReplace that simplifies the\r\nmulti-directory string replace procedure.  Essentially, it is the same\r\nas executing DirDoFast with a directory, pattern, and command (as \r\ns\/[regex_pattern]\/[replacement\/gce | update).\r\n\r\n    :DirReplace\r\n\r\n    or\r\n\r\n    :DR\r\n\r\nYou will be asked for the directories, glob patterns, regex string, and\r\nthe replacement.\r\n\r\nThere is an option to run DirDo with less verbosity, to toggle the\r\nsetting, run:\r\n\r\n    :DirDoVerbose\r\n\r\n    or\r\n\r\n    :DDV\r\n\r\nYou can also set the following variables in your .vimrc to set the default\r\ndirectory and pattern.  This is good for pointing to the directories for\r\ncode refactoring:\r\n\r\nlet g:DirDoPattern = \"...\"\r\n\r\nlet g:DirDoDir = \"...\"\r\n\r\nFor example, if you want by default have the command apply on all your C,\r\nC++, and Java source, you can set the DirDoPattern to:\r\n\r\nlet g:DirDoPattern = \"*.c *.cpp *.java\"\r\n\r\nIf you want to apply your changes to \/dir1, \/dir2, and \/dir3, you can do:\r\n\r\nlet g:DirDoDir = \"\/dir1,\/dir2,\/dir3\"\r\n","5":"REQUIREMENTS:\r\n  - The :argdo command in Vim 6.0\r\nPut this file in your ~\/.vim\/plugin directory.\r\n\r\nThe syntax of the commands:\r\n\r\nFirst we need to set what directory we would like to perform this\r\ncommand on\r\n\r\n    :DirDoDir [\/my\/directory1] [\/my\/directory2] [\/my\/directory3]\r\n\r\n    or\r\n\r\n    :DDD [\/my\/directory1] [\/my\/directory2] [\/my\/directory3]\r\n\r\nIf no argument is given, then it'll display the directories that you're\r\ngoing to work on and let you edit them by separating them with commas\r\n(',')\r\n\r\nYou can also use the following command to add a directory to the DirDoDir\r\nvariable:\r\n\r\n    :DirDoAdd [\/my\/dir]\r\n\r\n    or\r\n\r\n    :DDA [\/my\/dir]\r\n\r\nIf you do not give an argument to DDA, it'll add the current working\r\ndirectory to the DirDoDir variable.\r\n\r\nThen we set the file glob pattern\r\n\r\n    :DirDoPattern [file glob pattern1] [file glob pattern2] ...\r\n\r\n    or\r\n\r\n    :DDP [file glob pattern1] [file glob pattern2] ...\r\n\r\nIf no argument is given, then it'll display the patterns and let you\r\nedit them (separate each pattern with spaces).\r\n\r\nThen, you can do:\r\n\r\n    :DirDo [commands]\r\n\r\n    or\r\n\r\n    :DDO [commands]\r\n\r\nto executes the commands on each file that matches the glob pattern\r\nrecursively under the directories that you have specified.  The format of\r\n[commands] is just like what you do on :argdo. See :help argdo for\r\ndetails.\r\n\r\nIf no argument is given, then it'll reuse the last command.\r\n\r\nExamples:\r\n\r\nReplace all the instaces of \"Foo\" to \"Bar\" in all the Java or C files under\r\nthe directory \/my\/directory and its subdirectories, confirming each match:\r\n\r\n    :DDD \/my\/directory (or just :DDD<CR> and type it in)\r\n    :DDP *.java *.c (or just :DDP<CR> and type it in)\r\n    :DDO %s\/Foo\/Bar\/gce | update\r\n\r\n(See :h argdo for the commands after DDO.)\r\n\r\nSame scenario but replacing \"Bar\" with \"Baz\" without confirmation for each\r\nmatch (note the directory and patterns are saved):\r\n\r\n    :DDO %s\/Bar\/Baz\/ge | update\r\n\r\n(Since 1.2) There is a command called DirDoFast where you can set the\r\ndirectory, pattern, and command at once.  Note that your arguments need to\r\nbe escaped if there is an space to it, otherwise Vim will break up the\r\narguments incorrectly.  The syntax is:\r\n\r\n    :DirDoFast [directories] [patterns] command\r\n\r\n    or\r\n\r\n    :DDF [directories] [patterns] command\r\n\r\nMultiple directories need to be separated by comma.  Patterns need to be\r\nseparated by spaces.  Since space is used by Vim to separate the command\r\narguments, ALL spaces in the directory, pattern, or command need to be\r\nescaped.  For example, the last command using DDF would look like:\r\n\r\n:DDF \/my\/directory *.java\\ *.c %s\/Foo\/Bar\/gce\\ |\\ update\r\n\r\nIf you only give 2 arguments to :DDF, you assume the directory is set to\r\n\".\".\r\n\r\nIf you only give 1 argument to :DDF, you assume the directory is set to\r\n\".\" and the pattern is set to \"*\".\r\n\r\n(Since 1.3) There is a command called DirReplace that simplifies the\r\nmulti-directory string replace procedure.  Essentially, it is the same\r\nas executing DirDoFast with a directory, pattern, and command (as \r\ns\/[regex_pattern]\/[replacement\/gce | update).\r\n\r\n    :DirReplace\r\n\r\n    or\r\n\r\n    :DR\r\n\r\nYou will be asked for the directories, glob patterns, regex string, and\r\nthe replacement.\r\n\r\nThere is an option to run DirDo with less verbosity, to toggle the\r\nsetting, run:\r\n\r\n    :DirDoVerbose\r\n\r\n    or\r\n\r\n    :DDV\r\n\r\nYou can also set the following variables in your .vimrc to set the default\r\ndirectory and pattern.  This is good for pointing to the directories for\r\ncode refactoring:\r\n\r\nlet g:DirDoPattern = \"...\"\r\n\r\nlet g:DirDoDir = \"...\"\r\n\r\nFor example, if you want by default have the command apply on all your C,\r\nC++, and Java source, you can set the DirDoPattern to:\r\n\r\nlet g:DirDoPattern = \"*.c *.cpp *.java\"\r\n\r\nIf you want to apply your changes to \/dir1, \/dir2, and \/dir3, you can do:\r\n\r\nlet g:DirDoDir = \"\/dir1,\/dir2,\/dir3\"\r\n","first_name":"William","6":"William","last_name":"Lee","7":"Lee","releases":[{"0":"367","vim_version":"6.0","1":"6.0","script_version":"1.3","2":"1.3","version_comment":"Added the DirReplace command.  Fixed a bug on the directory listing that prevents DirDo from functioning properly.","3":"Added the DirReplace command.  Fixed a bug on the directory listing that prevents DirDo from functioning properly.","package":"DirDo.vim","4":"DirDo.vim","src_id":"4583","5":"4583","creation_date":"1126701837","6":"1126701837"},{"0":"367","vim_version":"6.0","1":"6.0","script_version":"1.2","2":"1.2","version_comment":"Added the DirDoFast command so you can set directory, pattern, and command at once.  Fixed bug where the unix hidden file will not show up in the file list.  Fixed bug where ~ in the path does not work.","3":"Added the DirDoFast command so you can set directory, pattern, and command at once.  Fixed bug where the unix hidden file will not show up in the file list.  Fixed bug where ~ in the path does not work.","package":"DirDo.vim","4":"DirDo.vim","src_id":"2072","5":"2072","creation_date":"1055434912","6":"1055434912"},{"0":"367","vim_version":"6.0","1":"6.0","script_version":"1.1","2":"1.1","version_comment":"Added the option :DirDoAdd (:DDA) to add the current directory (getcwd()) to the list of directories that you want to apply DirDo on.  This is useful if you want to construct your list of DirDo directories quickly.","3":"Added the option :DirDoAdd (:DDA) to add the current directory (getcwd()) to the list of directories that you want to apply DirDo on.  This is useful if you want to construct your list of DirDo directories quickly.","package":"DirDo.vim","4":"DirDo.vim","src_id":"1151","5":"1151","creation_date":"1029846675","6":"1029846675"},{"0":"367","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"DirDo.vim","4":"DirDo.vim","src_id":"1089","5":"1089","creation_date":"1028738927","6":"1028738927"}]},"366":{"script_id":"366","0":"366","script_name":"ldraw.vim","1":"ldraw.vim","script_type":"syntax","2":"syntax","summary":"Syntax file for LDraw (LEGO Draw) models files.","3":"Syntax file for LDraw (LEGO Draw) models files.","description":"See http:\/\/www.ldraw.org\/ for more information about LDraw and other related applications.","4":"See http:\/\/www.ldraw.org\/ for more information about LDraw and other related applications.","install_details":"","5":"","first_name":"Jack","6":"Jack","last_name":"Hawk","7":"Hawk","releases":[{"0":"366","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"ldraw.vim","4":"ldraw.vim","src_id":"1088","5":"1088","creation_date":"1028729420","6":"1028729420"}]},"365":{"script_id":"365","0":"365","script_name":"bash-support.vim","1":"bash-support.vim","script_type":"utility","2":"utility","summary":"Bash IDE -- Insert code snippets, run, check and debug the code and look up help","3":"Bash IDE -- Insert code snippets, run, check and debug the code and look up help","description":"Write Bash-scripts by inserting comments, statements, tests, variables, built-ins, etc..\r\nSpeed up writing new scripts considerably.\r\nWrite code und comments with a professional appearance from the beginning.\r\n\r\nSome screen shots :  https:\/\/wolfgangmehner.github.io\/vim-plugins\/bashsupport.html\r\n\r\nFor plug-in managers :  https:\/\/github.com\/WolfgangMehner\/bash-support\r\n\r\nThe help file online :  https:\/\/wolfgangmehner.github.io\/vim-plugins\/doc\/bashsupport.html\r\n\r\nThe key mappings of this plug-in :  https:\/\/wolfgangmehner.github.io\/vim-plugins\/bashsupport\/bash-hotkeys.pdf\r\n\r\nThe installation explained :  \"Make Vim as Your Bash-IDE Using bash-support Plugin\"\r\n(http:\/\/www.thegeekstuff.com\/2009\/02\/make-vim-as-your-bash-ide-using-bash-support-plugin)\r\n\r\nPlug-in featured in the linux.com article 'Turn Vim into a bash IDE' :  http:\/\/www.linux.com\/articles\/114359\r\n\r\nDOCUMENTATION\r\n--------------------------------------------------------\r\nThis plug-in comes with a help file (bashsupport.txt). Read it with\r\n\r\n    :help bashsupport\r\n\r\n** PLEASE READ THE DOCUMENTATION **\r\n\r\nEditing actions differ for different modes! There are a lot of features which\r\ncan be configured or customized to match your needs.\r\n\r\nGitHub\r\n--------------------------------------------------------\r\nBash-Support is on GitHub:\r\n\r\n    https:\/\/github.com\/WolfgangMehner\/vim-plugins\r\n\r\n(Please help us keep track of all the issues and name your report\/request \"Bash-Support: <title>\")\r\n\r\n","4":"Write Bash-scripts by inserting comments, statements, tests, variables, built-ins, etc..\r\nSpeed up writing new scripts considerably.\r\nWrite code und comments with a professional appearance from the beginning.\r\n\r\nSome screen shots :  https:\/\/wolfgangmehner.github.io\/vim-plugins\/bashsupport.html\r\n\r\nFor plug-in managers :  https:\/\/github.com\/WolfgangMehner\/bash-support\r\n\r\nThe help file online :  https:\/\/wolfgangmehner.github.io\/vim-plugins\/doc\/bashsupport.html\r\n\r\nThe key mappings of this plug-in :  https:\/\/wolfgangmehner.github.io\/vim-plugins\/bashsupport\/bash-hotkeys.pdf\r\n\r\nThe installation explained :  \"Make Vim as Your Bash-IDE Using bash-support Plugin\"\r\n(http:\/\/www.thegeekstuff.com\/2009\/02\/make-vim-as-your-bash-ide-using-bash-support-plugin)\r\n\r\nPlug-in featured in the linux.com article 'Turn Vim into a bash IDE' :  http:\/\/www.linux.com\/articles\/114359\r\n\r\nDOCUMENTATION\r\n--------------------------------------------------------\r\nThis plug-in comes with a help file (bashsupport.txt). Read it with\r\n\r\n    :help bashsupport\r\n\r\n** PLEASE READ THE DOCUMENTATION **\r\n\r\nEditing actions differ for different modes! There are a lot of features which\r\ncan be configured or customized to match your needs.\r\n\r\nGitHub\r\n--------------------------------------------------------\r\nBash-Support is on GitHub:\r\n\r\n    https:\/\/github.com\/WolfgangMehner\/vim-plugins\r\n\r\n(Please help us keep track of all the issues and name your report\/request \"Bash-Support: <title>\")\r\n\r\n","install_details":"Copy the zip archive bash-support.zip to $HOME\/.vim\/ or $VIM\/vimfiles\r\n(on the Windows platforms) and run\r\n    unzip bash-support.zip\r\nIf you have already an older version of this plugin and you have modified the\r\ntemplate files you may want to save your templates first or copy the files from\r\nthe archive by hand. See also the file README.md within the zip file.","5":"Copy the zip archive bash-support.zip to $HOME\/.vim\/ or $VIM\/vimfiles\r\n(on the Windows platforms) and run\r\n    unzip bash-support.zip\r\nIf you have already an older version of this plugin and you have modified the\r\ntemplate files you may want to save your templates first or copy the files from\r\nthe archive by hand. See also the file README.md within the zip file.","first_name":"Fritz","6":"Fritz","last_name":"Mehner","7":"Mehner","releases":[{"0":"365","vim_version":"7.3","1":"7.3","script_version":"4.3","2":"4.3","version_comment":"- Add 'g:BASH_CustomTemplateFile'.\r\n- Add template personalization file and setup wizard.\r\n- Change the way lines of code are turned into comments\r\n  (insert no space after the hash).\r\n- Change the map for 'comment -> code' to '\\co' for consistency with the other\r\n  plug-ins. The old map '\\cu' still works, however.\r\n- Minor corrections and improvements.","3":"- Add 'g:BASH_CustomTemplateFile'.\r\n- Add template personalization file and setup wizard.\r\n- Change the way lines of code are turned into comments\r\n  (insert no space after the hash).\r\n- Change the map for 'comment -> code' to '\\co' for consistency with the other\r\n  plug-ins. The old map '\\cu' still works, however.\r\n- Minor corrections and improvements.","package":"bash-support.zip","4":"bash-support.zip","src_id":"24452","5":"24452","creation_date":"1471360903","6":"1471360903"},{"0":"365","vim_version":"7.0","1":"7.0","script_version":"4.2.1","2":"4.2.1","version_comment":"- Bugfix: Setup of local templates in case of global installation.\r\n- Help: Bash and utility manuals wrapped on window width.\r\n- Bugfix: \\hm and \\hh work wrong in insert mode.\r\n- Bugfix: Better compatibility with custom mappings\r\n  (use \"normal!\" and \"noremap\" consistently).\r\n- Added 'Bash_SetMapLeader' and 'Bash_ResetMapLeader'.\r\n- Minor corrections and improvements.","3":"- Bugfix: Setup of local templates in case of global installation.\r\n- Help: Bash and utility manuals wrapped on window width.\r\n- Bugfix: \\hm and \\hh work wrong in insert mode.\r\n- Bugfix: Better compatibility with custom mappings\r\n  (use \"normal!\" and \"noremap\" consistently).\r\n- Added 'Bash_SetMapLeader' and 'Bash_ResetMapLeader'.\r\n- Minor corrections and improvements.","package":"bash-support.zip","4":"bash-support.zip","src_id":"21804","5":"21804","creation_date":"1398096915","6":"1398096915"},{"0":"365","vim_version":"7.0","1":"7.0","script_version":"4.2","2":"4.2","version_comment":"- Default shell can be set in ~\/.vimrc via g:BASH_Executable.\r\n- Errors can be parsed for bash, dash, ksh, zsh.\r\n- Bugfix: QuickFix list doesn't work properly (thanks to @PengZheng)\r\n- 'Run -> make script executable' (\\re) is now a toggle.\r\n- Minor corrections and improvements.","3":"- Default shell can be set in ~\/.vimrc via g:BASH_Executable.\r\n- Errors can be parsed for bash, dash, ksh, zsh.\r\n- Bugfix: QuickFix list doesn't work properly (thanks to @PengZheng)\r\n- 'Run -> make script executable' (\\re) is now a toggle.\r\n- Minor corrections and improvements.","package":"bash-support.zip","4":"bash-support.zip","src_id":"21272","5":"21272","creation_date":"1388839672","6":"1388839672"},{"0":"365","vim_version":"7.0","1":"7.0","script_version":"4.1","2":"4.1","version_comment":"- Filetype plugin added.\r\n- Bugfix: Setup of local templates in case of global installation.\r\n- Adjusting end-of-line comments improved.\r\n- Submenu 'Regexp' renamed to 'PatternMatching'. Appropriate hotkeys renamed.\r\n- Minor bugfixes.\r\n- Documentation updated.","3":"- Filetype plugin added.\r\n- Bugfix: Setup of local templates in case of global installation.\r\n- Adjusting end-of-line comments improved.\r\n- Submenu 'Regexp' renamed to 'PatternMatching'. Appropriate hotkeys renamed.\r\n- Minor bugfixes.\r\n- Documentation updated.","package":"bash-support.zip","4":"bash-support.zip","src_id":"21180","5":"21180","creation_date":"1386607760","6":"1386607760"},{"0":"365","vim_version":"7.0","1":"7.0","script_version":"4.0","2":"4.0","version_comment":"++  The plug-in version 4.0 is a rewriting of version 3.12.1 .\r\n++  The template syntax has changed!\r\n\r\n- New template system (many thanks to Wolfgang Mehner)\r\n- A few new hotkeys and menu item.\r\n- A few hotkeys and menu items renamed. ","3":"++  The plug-in version 4.0 is a rewriting of version 3.12.1 .\r\n++  The template syntax has changed!\r\n\r\n- New template system (many thanks to Wolfgang Mehner)\r\n- A few new hotkeys and menu item.\r\n- A few hotkeys and menu items renamed. ","package":"bash-support.zip","4":"bash-support.zip","src_id":"20562","5":"20562","creation_date":"1374664785","6":"1374664785"},{"0":"365","vim_version":"7.0","1":"7.0","script_version":"3.12.1","2":"3.12.1","version_comment":"- Minor additions and bugfixes in 2 menus.\r\n- Test -v added.","3":"- Minor additions and bugfixes in 2 menus.\r\n- Test -v added.","package":"bash-support.zip","4":"bash-support.zip","src_id":"19532","5":"19532","creation_date":"1361103523","6":"1361103523"},{"0":"365","vim_version":"7.0","1":"7.0","script_version":"3.12","2":"3.12","version_comment":"- New global variable g:BASH_InsertFileHeader (suppress file description comment for new files)\r\n- New menu item 'view code snippet' (\\nv).\r\n- New ex command BASH_ScriptCmdLineArguments.\r\n- 3 ex commands renamed.\r\n- Minor internal improvements.","3":"- New global variable g:BASH_InsertFileHeader (suppress file description comment for new files)\r\n- New menu item 'view code snippet' (\\nv).\r\n- New ex command BASH_ScriptCmdLineArguments.\r\n- 3 ex commands renamed.\r\n- Minor internal improvements.","package":"bash-support.zip","4":"bash-support.zip","src_id":"19313","5":"19313","creation_date":"1357379201","6":"1357379201"},{"0":"365","vim_version":"7.0","1":"7.0","script_version":"3.11","2":"3.11","version_comment":"- Rendering of manuals (\\hm) and Bash help (\\hh).\r\n- Bugfix: \\hb, \\hm, \\hh not working.\r\n- Minor internal improvements.","3":"- Rendering of manuals (\\hm) and Bash help (\\hh).\r\n- Bugfix: \\hb, \\hm, \\hh not working.\r\n- Minor internal improvements.","package":"bash-support.zip","4":"bash-support.zip","src_id":"19103","5":"19103","creation_date":"1354621457","6":"1354621457"},{"0":"365","vim_version":"7.0","1":"7.0","script_version":"3.10","2":"3.10","version_comment":"- Resolve $HOME for linked home directories.\r\n- Wrong insertion for parameter substitution \"match beginning; del longest\r\n  part\" (thanks to John Orr).\r\n- Other minor bugs fixed.","3":"- Resolve $HOME for linked home directories.\r\n- Wrong insertion for parameter substitution \"match beginning; del longest\r\n  part\" (thanks to John Orr).\r\n- Other minor bugs fixed.","package":"bash-support.zip","4":"bash-support.zip","src_id":"18071","5":"18071","creation_date":"1338537241","6":"1338537241"},{"0":"365","vim_version":"7.0","1":"7.0","script_version":"3.9","2":"3.9","version_comment":"- Hotkey renamed: \\st -> \\su\r\n- New global variable allows loading menus only with filetype 'sh'.\r\n- Comments: echo \"<line>\" escapes double quotes in original text.\r\n- Other minor bugs fixed.","3":"- Hotkey renamed: \\st -> \\su\r\n- New global variable allows loading menus only with filetype 'sh'.\r\n- Comments: echo \"<line>\" escapes double quotes in original text.\r\n- Other minor bugs fixed.","package":"bash-support.zip","4":"bash-support.zip","src_id":"17122","5":"17122","creation_date":"1324989052","6":"1324989052"},{"0":"365","vim_version":"7.0","1":"7.0","script_version":"3.8","2":"3.8","version_comment":"- New comment submenu 'script sections'.\r\n- Two new hotkeys \\css, \\ckc for commenting.\r\n- Two new plugin tags: LICENSE,ORGANIZATION\r\n- Run menu: new item 'Bash cmd. line arg.' (\\rba).  \r\n- I\/O-Redir-menu: additional item'>&2'\r\n- System-wide installation: minimal Template file for a user will automatically\r\n  be added.\r\n- Hotkey renamed: \\t -> \\t1\r\n- A few code snippets for debugging added.\r\n- Bugfix: \\cl did not work in insert mode.\r\n- Other minor bugs fixed.","3":"- New comment submenu 'script sections'.\r\n- Two new hotkeys \\css, \\ckc for commenting.\r\n- Two new plugin tags: LICENSE,ORGANIZATION\r\n- Run menu: new item 'Bash cmd. line arg.' (\\rba).  \r\n- I\/O-Redir-menu: additional item'>&2'\r\n- System-wide installation: minimal Template file for a user will automatically\r\n  be added.\r\n- Hotkey renamed: \\t -> \\t1\r\n- A few code snippets for debugging added.\r\n- Bugfix: \\cl did not work in insert mode.\r\n- Other minor bugs fixed.","package":"bash-support.zip","4":"bash-support.zip","src_id":"16898","5":"16898","creation_date":"1321616653","6":"1321616653"},{"0":"365","vim_version":"7.0","1":"7.0","script_version":"3.7","2":"3.7","version_comment":"- The three hotkeys \\cl, \\cj, \\cc allow a range, e.g. '3\\cl' (see help text and\r\n\tbash-hot-key.pdf).\r\n- Plugin loads faster: loading the templates is delayed until the first use.\r\n- Plugin now works with pathogen.vim.\r\n- Menus will always be generated (for the use with :emenu).\r\n- Bugfix: no local templates available with a system-wide installation (thanks to Iain Arnell).\r\n- Several improvements.","3":"- The three hotkeys \\cl, \\cj, \\cc allow a range, e.g. '3\\cl' (see help text and\r\n\tbash-hot-key.pdf).\r\n- Plugin loads faster: loading the templates is delayed until the first use.\r\n- Plugin now works with pathogen.vim.\r\n- Menus will always be generated (for the use with :emenu).\r\n- Bugfix: no local templates available with a system-wide installation (thanks to Iain Arnell).\r\n- Several improvements.","package":"bash-support.zip","4":"bash-support.zip","src_id":"16694","5":"16694","creation_date":"1318939989","6":"1318939989"},{"0":"365","vim_version":"7.0","1":"7.0","script_version":"3.6","2":"3.6","version_comment":"- New hotkey \\ssa and menu entry for the selection of a subarray.\r\n- Bugfix: detection of a system-wide installation can fail.\r\n- Minor improvements.","3":"- New hotkey \\ssa and menu entry for the selection of a subarray.\r\n- Bugfix: detection of a system-wide installation can fail.\r\n- Minor improvements.","package":"bash-support.zip","4":"bash-support.zip","src_id":"16019","5":"16019","creation_date":"1309629244","6":"1309629244"},{"0":"365","vim_version":"7.0","1":"7.0","script_version":"3.5","2":"3.5","version_comment":"- Bugfix: detection of a system-wide installation can fail.\r\n- Minor improvements.\r\n","3":"- Bugfix: detection of a system-wide installation can fail.\r\n- Minor improvements.\r\n","package":"bash-support.zip","4":"bash-support.zip","src_id":"15125","5":"15125","creation_date":"1298746757","6":"1298746757"},{"0":"365","vim_version":"7.0","1":"7.0","script_version":"3.4","2":"3.4","version_comment":"- 2 new hotkeys: \\t, \\t2 (empty tests)\r\n- Windows: user and system installation.\r\n- Syntax check under Windows.\r\n- Several minor bugs fixed.","3":"- 2 new hotkeys: \\t, \\t2 (empty tests)\r\n- Windows: user and system installation.\r\n- Syntax check under Windows.\r\n- Several minor bugs fixed.","package":"bash-support.zip","4":"bash-support.zip","src_id":"14460","5":"14460","creation_date":"1291838138","6":"1291838138"},{"0":"365","vim_version":"7.0","1":"7.0","script_version":"3.3","2":"3.3","version_comment":"- 3 hotkeys renamed: \\sl -> \\sei (elif), \\sas -> \\saa ( ${.[@]} ) , \\hp -> \\hbs.\r\n- 3 new hotkeys: \\sa1 ( ${.[*]} ), \\san ( ${#.[@]} ), \\sai ( ${!.[@]} ).\r\n- 1 new menu entry (Tests)\r\n- Minor improvements.","3":"- 3 hotkeys renamed: \\sl -> \\sei (elif), \\sas -> \\saa ( ${.[@]} ) , \\hp -> \\hbs.\r\n- 3 new hotkeys: \\sa1 ( ${.[*]} ), \\san ( ${#.[@]} ), \\sai ( ${!.[@]} ).\r\n- 1 new menu entry (Tests)\r\n- Minor improvements.","package":"bash-support.zip","4":"bash-support.zip","src_id":"14185","5":"14185","creation_date":"1288958243","6":"1288958243"},{"0":"365","vim_version":"7.0","1":"7.0","script_version":"3.2","2":"3.2","version_comment":"- New hotkey and menu entry for [[ =~ ]]\r\n- New for Bash 4.1: shopt 'compat40', variables '$BASHOPTS', '$BASH_XTRACEFD'.\r\n- Bugfixes: local installation looks like a system-wide installation in seldom cases.\r\n- Bugfixes: typo in 4 menu entries.","3":"- New hotkey and menu entry for [[ =~ ]]\r\n- New for Bash 4.1: shopt 'compat40', variables '$BASHOPTS', '$BASH_XTRACEFD'.\r\n- Bugfixes: local installation looks like a system-wide installation in seldom cases.\r\n- Bugfixes: typo in 4 menu entries.","package":"bash-support.zip","4":"bash-support.zip","src_id":"13525","5":"13525","creation_date":"1281303885","6":"1281303885"},{"0":"365","vim_version":"7.0","1":"7.0","script_version":"3.1.1","2":"3.1.1","version_comment":"- Bugfixes: code snippets will not be found if plugin not installed beyond '$HOME\/.vim'.\r\n- Bugfixes: undocumented global variable used in above non-standard installation.","3":"- Bugfixes: code snippets will not be found if plugin not installed beyond '$HOME\/.vim'.\r\n- Bugfixes: undocumented global variable used in above non-standard installation.","package":"bash-support.zip","4":"bash-support.zip","src_id":"12381","5":"12381","creation_date":"1266083432","6":"1266083432"},{"0":"365","vim_version":"7.0","1":"7.0","script_version":"3.1","2":"3.1","version_comment":"- The plugin now handles different template styles without editing and reloading the main template file.\r\n- New hotkey and ex-command to switch template styles.\r\n- New global List\/Dictionnary g:BASH_AlsoBash: add filename pattern (and styles) for files not named *.sh .\r\n- Minor improvements.\r\n- Bugfixes: missing redraws in some cases. ","3":"- The plugin now handles different template styles without editing and reloading the main template file.\r\n- New hotkey and ex-command to switch template styles.\r\n- New global List\/Dictionnary g:BASH_AlsoBash: add filename pattern (and styles) for files not named *.sh .\r\n- Minor improvements.\r\n- Bugfixes: missing redraws in some cases. ","package":"bash-support.zip","4":"bash-support.zip","src_id":"12267","5":"12267","creation_date":"1265047655","6":"1265047655"},{"0":"365","vim_version":"7.0","1":"7.0","script_version":"3.0.1","2":"3.0.1","version_comment":"- New global variable g:BASH_Errorformat: adapt the error format used to parse\r\n  runtime messages to your locale setting.\r\n- Bugfix (Windows only): missing internal variable prevents proper initialization.","3":"- New global variable g:BASH_Errorformat: adapt the error format used to parse\r\n  runtime messages to your locale setting.\r\n- Bugfix (Windows only): missing internal variable prevents proper initialization.","package":"bash-support.zip","4":"bash-support.zip","src_id":"11913","5":"11913","creation_date":"1261068837","6":"1261068837"},{"0":"365","vim_version":"7.0","1":"7.0","script_version":"3.0","2":"3.0","version_comment":"+ Completely new template system. User can change templates on the fly.\r\n+ Additional mapping Ctrl-j : jump behind parenthesis or strings in the current line.\r\n+ A few Posix character classes have better shortcuts.\r\n+ Bugfix: insert mode for Posix character classes.","3":"+ Completely new template system. User can change templates on the fly.\r\n+ Additional mapping Ctrl-j : jump behind parenthesis or strings in the current line.\r\n+ A few Posix character classes have better shortcuts.\r\n+ Bugfix: insert mode for Posix character classes.","package":"bash-support.zip","4":"bash-support.zip","src_id":"11829","5":"11829","creation_date":"1259515648","6":"1259515648"},{"0":"365","vim_version":"7.0","1":"7.0","script_version":"2.14","2":"2.14","version_comment":"+ Debugging: ddd always called with bashdb(1)  (may cause trouble otherwise).\r\n+ More complete adaption to Bash 4.0: options, builtins, environment variables.\r\n+ Bugfix: running and starting the debugger causes error if working directory is not\r\n  the directory of the current file.\r\n+ Minor improvements.","3":"+ Debugging: ddd always called with bashdb(1)  (may cause trouble otherwise).\r\n+ More complete adaption to Bash 4.0: options, builtins, environment variables.\r\n+ Bugfix: running and starting the debugger causes error if working directory is not\r\n  the directory of the current file.\r\n+ Minor improvements.","package":"bash-support.zip","4":"bash-support.zip","src_id":"11394","5":"11394","creation_date":"1253196102","6":"1253196102"},{"0":"365","vim_version":"7.0","1":"7.0","script_version":"2.13","2":"2.13","version_comment":"+ New menu item 'array element'.\r\n+ New hotkeys \\sa, \\sas.\r\n+ New submenu 'Snippets'.\r\n+ Hotkeys for the POSIX character classes.\r\n+ Hardcopy (run menu) can print any buffer.\r\n+ Bugfix: 'Run->save + run script' (\\rr, <C-F9>) : visual mode broken. \r\n+ Minor improvements.","3":"+ New menu item 'array element'.\r\n+ New hotkeys \\sa, \\sas.\r\n+ New submenu 'Snippets'.\r\n+ Hotkeys for the POSIX character classes.\r\n+ Hardcopy (run menu) can print any buffer.\r\n+ Bugfix: 'Run->save + run script' (\\rr, <C-F9>) : visual mode broken. \r\n+ Minor improvements.","package":"bash-support.zip","4":"bash-support.zip","src_id":"11059","5":"11059","creation_date":"1248431127","6":"1248431127"},{"0":"365","vim_version":"7.0","1":"7.0","script_version":"2.12","2":"2.12","version_comment":"+ Hotkeys are shown in the menus.\r\n+ New menu item and hotkey \\hb : open the Bash manual.\r\n+ New hotkey \\rco : syntax check options.\r\n+ File browser for code snippets choosable (new global variable).\r\n+ Bugfix: wrapper script for use of a xterm could not handle parameters containing blanks.\r\n+ Minor improvements.","3":"+ Hotkeys are shown in the menus.\r\n+ New menu item and hotkey \\hb : open the Bash manual.\r\n+ New hotkey \\rco : syntax check options.\r\n+ File browser for code snippets choosable (new global variable).\r\n+ Bugfix: wrapper script for use of a xterm could not handle parameters containing blanks.\r\n+ Minor improvements.","package":"bash-support.zip","4":"bash-support.zip","src_id":"10918","5":"10918","creation_date":"1246461340","6":"1246461340"},{"0":"365","vim_version":"7.0","1":"7.0","script_version":"2.11","2":"2.11","version_comment":"+ Additions for Bash version 4.0.\r\n+ Comments menu (\\cj): adjustment of end-of-line comments improved.\r\n+ Two submenus rearranged.","3":"+ Additions for Bash version 4.0.\r\n+ Comments menu (\\cj): adjustment of end-of-line comments improved.\r\n+ Two submenus rearranged.","package":"bash-support.zip","4":"bash-support.zip","src_id":"10628","5":"10628","creation_date":"1242663475","6":"1242663475"},{"0":"365","vim_version":"7.0","1":"7.0","script_version":"2.10","2":"2.10","version_comment":"- new item in the Statements-menu: 'for ((...)) do done'.\r\n- new item in the Statements-menu: 'printf \"%s\"'.\r\n- new item in the Statements-menu: indirect parameter expansion ${!name}\r\n- Bugfix: unnecessary submenu beyond 'Environ'.\r\n- Bugfix: shopt menu had no insert mode.","3":"- new item in the Statements-menu: 'for ((...)) do done'.\r\n- new item in the Statements-menu: 'printf \"%s\"'.\r\n- new item in the Statements-menu: indirect parameter expansion ${!name}\r\n- Bugfix: unnecessary submenu beyond 'Environ'.\r\n- Bugfix: shopt menu had no insert mode.","package":"bash-support.zip","4":"bash-support.zip","src_id":"9890","5":"9890","creation_date":"1233325819","6":"1233325819"},{"0":"365","vim_version":"7.0","1":"7.0","script_version":"2.9.1","2":"2.9.1","version_comment":"- Map leader for hotkeys now user definable: new global variable g:BASH_MapLeader.\r\n- Bugfix: 'Statements->no. of elem.s' inserts wrong text.","3":"- Map leader for hotkeys now user definable: new global variable g:BASH_MapLeader.\r\n- Bugfix: 'Statements->no. of elem.s' inserts wrong text.","package":"bash-support.zip","4":"bash-support.zip","src_id":"9776","5":"9776","creation_date":"1231432198","6":"1231432198"},{"0":"365","vim_version":"7.0","1":"7.0","script_version":"2.9","2":"2.9","version_comment":"+ Can now be used under Windows, e.g. with win-bash (few restrictions).\r\n+ Name completion when entering a builtin name.\r\n+ Bugfix: help shows no selection when just 2 manuals are available.","3":"+ Can now be used under Windows, e.g. with win-bash (few restrictions).\r\n+ Name completion when entering a builtin name.\r\n+ Bugfix: help shows no selection when just 2 manuals are available.","package":"bash-support.zip","4":"bash-support.zip","src_id":"9425","5":"9425","creation_date":"1225715375","6":"1225715375"},{"0":"365","vim_version":"7.0","1":"7.0","script_version":"2.8","2":"2.8","version_comment":"+ New help menu: help reorganized, 3 new help hotkeys.\r\n+ The help hotkeys now also work when Vim is run on the console.","3":"+ New help menu: help reorganized, 3 new help hotkeys.\r\n+ The help hotkeys now also work when Vim is run on the console.","package":"bash-support.zip","4":"bash-support.zip","src_id":"9378","5":"9378","creation_date":"1224619884","6":"1224619884"},{"0":"365","vim_version":"7.0","1":"7.0","script_version":"2.7.1","2":"2.7.1","version_comment":"+ Minor bugfix in the I\/O-Redir-menu.\r\n+ I\/O-Redir-menu shows redirectors (sort of help).\r\n+ I\/O-Redir-menu: here-document item has a vmode.\r\n+ File name expansion for the first command line argument entered with <S-F9>.","3":"+ Minor bugfix in the I\/O-Redir-menu.\r\n+ I\/O-Redir-menu shows redirectors (sort of help).\r\n+ I\/O-Redir-menu: here-document item has a vmode.\r\n+ File name expansion for the first command line argument entered with <S-F9>.","package":"bash-support.zip","4":"bash-support.zip","src_id":"9304","5":"9304","creation_date":"1223046294","6":"1223046294"},{"0":"365","vim_version":"7.0","1":"7.0","script_version":"2.7","2":"2.7","version_comment":"+ When a Bash script is started from the Vim command line errors and warnings (if any)\r\n  are caught in an error window allowing quickfix commands to be used.\r\n+ Scripts which are not set executable can be run under Vim.\r\n+ One new hotkey.","3":"+ When a Bash script is started from the Vim command line errors and warnings (if any)\r\n  are caught in an error window allowing quickfix commands to be used.\r\n+ Scripts which are not set executable can be run under Vim.\r\n+ One new hotkey.","package":"bash-support.zip","4":"bash-support.zip","src_id":"9123","5":"9123","creation_date":"1218675197","6":"1218675197"},{"0":"365","vim_version":"7.0","1":"7.0","script_version":"2.6","2":"2.6","version_comment":"+ Superfluous control characters for mode switching (menus, hotkeys) removed. Caused beeps.\r\n+ Most hotkeys now work in insert mode.","3":"+ Superfluous control characters for mode switching (menus, hotkeys) removed. Caused beeps.\r\n+ Most hotkeys now work in insert mode.","package":"bash-support.zip","4":"bash-support.zip","src_id":"9015","5":"9015","creation_date":"1216888004","6":"1216888004"},{"0":"365","vim_version":"7.0","1":"7.0","script_version":"2.5","2":"2.5","version_comment":"+ Menu item 'toggle comment' replaces 'code->comment' and 'comment->code'\r\n+ Hotkey \\co removed,  \\cc is now a toggle.\r\n+ Bugfix. Adjusting comments (\\cj): # in '$#' and '${#...}' is no longer\r\n  regarded as a start of a comment.\r\n+ Bugfix. \\cl in insert mode called function for visual mode.","3":"+ Menu item 'toggle comment' replaces 'code->comment' and 'comment->code'\r\n+ Hotkey \\co removed,  \\cc is now a toggle.\r\n+ Bugfix. Adjusting comments (\\cj): # in '$#' and '${#...}' is no longer\r\n  regarded as a start of a comment.\r\n+ Bugfix. \\cl in insert mode called function for visual mode.","package":"bash-support.zip","4":"bash-support.zip","src_id":"8740","5":"8740","creation_date":"1212031259","6":"1212031259"},{"0":"365","vim_version":"7.0","1":"7.0","script_version":"2.4","2":"2.4","version_comment":"+ Format for the macros |DATE|, |TIME|, and |YEAR| can be defined by the user.\r\n+ Option 'nocasematch' added.\r\n+ Additional menu entries: 1 parameter substitution, 1 special variable, array index list.\r\n+ Help text improved.","3":"+ Format for the macros |DATE|, |TIME|, and |YEAR| can be defined by the user.\r\n+ Option 'nocasematch' added.\r\n+ Additional menu entries: 1 parameter substitution, 1 special variable, array index list.\r\n+ Help text improved.","package":"bash-support.zip","4":"bash-support.zip","src_id":"8157","5":"8157","creation_date":"1200530959","6":"1200530959"},{"0":"365","vim_version":"6.0","1":"6.0","script_version":"2.3","2":"2.3","version_comment":"+ Changes to allow a system-wide installation (please see the help file 'doc\/bashsupport.txt').","3":"+ Changes to allow a system-wide installation (please see the help file 'doc\/bashsupport.txt').","package":"bash-support.zip","4":"bash-support.zip","src_id":"7552","5":"7552","creation_date":"1188012092","6":"1188012092"},{"0":"365","vim_version":"6.0","1":"6.0","script_version":"2.2","2":"2.2","version_comment":"+ Snippets can now be managed in the console mode.\r\n+ Three new key mappings for snippet handling.\r\n+ Three items from the statements menu removed (quoting; but see file customization.vimrc).","3":"+ Snippets can now be managed in the console mode.\r\n+ Three new key mappings for snippet handling.\r\n+ Three items from the statements menu removed (quoting; but see file customization.vimrc).","package":"bash-support.zip","4":"bash-support.zip","src_id":"7302","5":"7302","creation_date":"1182736690","6":"1182736690"},{"0":"365","vim_version":"6.0","1":"6.0","script_version":"2.1","2":"2.1","version_comment":"+ New menu item and key mapping to adjust end-of-line comments.\r\n+ New insert mode mappings.\r\n+ A few mappings have been renamed (to bring them into line with my C\/C++ and Perl plugin).","3":"+ New menu item and key mapping to adjust end-of-line comments.\r\n+ New insert mode mappings.\r\n+ A few mappings have been renamed (to bring them into line with my C\/C++ and Perl plugin).","package":"bash-support.zip","4":"bash-support.zip","src_id":"7156","5":"7156","creation_date":"1179903245","6":"1179903245"},{"0":"365","vim_version":"6.0","1":"6.0","script_version":"2.0.1","2":"2.0.1","version_comment":"+ Bugfix: missing hotkey \\ch added (Thanks to Ian Tegebo).\r\n+ File wrapper.sh moved to the new directory 'bash-support\/scripts'.","3":"+ Bugfix: missing hotkey \\ch added (Thanks to Ian Tegebo).\r\n+ File wrapper.sh moved to the new directory 'bash-support\/scripts'.","package":"bash-support.zip","4":"bash-support.zip","src_id":"6859","5":"6859","creation_date":"1173692175","6":"1173692175"},{"0":"365","vim_version":"6.0","1":"6.0","script_version":"2.0","2":"2.0","version_comment":"+ PLUGIN DIRECTORIES REARRANGED.\r\n+ One new mapping (\\cs). \r\n+ Statement menu extended.\r\n+ Bash keyword help (S-F1) improved.\r\n+ Bugfix: empty new file after removing the header template can't be closed.\r\n+ Bugfix : Tools entry missing when root menu not shown from the start.","3":"+ PLUGIN DIRECTORIES REARRANGED.\r\n+ One new mapping (\\cs). \r\n+ Statement menu extended.\r\n+ Bash keyword help (S-F1) improved.\r\n+ Bugfix: empty new file after removing the header template can't be closed.\r\n+ Bugfix : Tools entry missing when root menu not shown from the start.","package":"bash-support.zip","4":"bash-support.zip","src_id":"6646","5":"6646","creation_date":"1169511437","6":"1169511437"},{"0":"365","vim_version":"6.0","1":"6.0","script_version":"1.15","2":"1.15","version_comment":"+ Inserting a function can be used in visual mode (+ new key mapping).\r\n+ Bugfix: cursor misplaced after some visual mode operations.\r\n+ Needs Vim version 7.0+.\r\n","3":"+ Inserting a function can be used in visual mode (+ new key mapping).\r\n+ Bugfix: cursor misplaced after some visual mode operations.\r\n+ Needs Vim version 7.0+.\r\n","package":"bash-support.zip","4":"bash-support.zip","src_id":"6515","5":"6515","creation_date":"1166017134","6":"1166017134"},{"0":"365","vim_version":"6.0","1":"6.0","script_version":"1.14","2":"1.14","version_comment":"+ Setting the column for the start of line-end comments improved.\r\n+ Mac OS X : circumvent a Vim bug which caused a crash when loading plugin version 1.13.","3":"+ Setting the column for the start of line-end comments improved.\r\n+ Mac OS X : circumvent a Vim bug which caused a crash when loading plugin version 1.13.","package":"bash-support.zip","4":"bash-support.zip","src_id":"6027","5":"6027","creation_date":"1154560485","6":"1154560485"},{"0":"365","vim_version":"6.0","1":"6.0","script_version":"1.13","2":"1.13","version_comment":"+ The hotkeys F9 and \\rd now also starts the debugger if vim is running without GUI.\r\n+ The debugger frontend ddd can be started as preferred debugger.\r\n+ New help entry in the main menu of this plugin (shows the plugin documentation).\r\n+ A hardcopy shows the localized date and time in the header line.","3":"+ The hotkeys F9 and \\rd now also starts the debugger if vim is running without GUI.\r\n+ The debugger frontend ddd can be started as preferred debugger.\r\n+ New help entry in the main menu of this plugin (shows the plugin documentation).\r\n+ A hardcopy shows the localized date and time in the header line.","package":"bash-support.zip","4":"bash-support.zip","src_id":"5593","5":"5593","creation_date":"1145849289","6":"1145849289"},{"0":"365","vim_version":"6.0","1":"6.0","script_version":"1.12","2":"1.12","version_comment":"+ Bugfix: hotkey <S-F9> now working again.\r\n+ Syntax check recognizes shopt options.\r\n+ New regex menu: compose regular expressions with a few keystrokes from the menu.\r\n","3":"+ Bugfix: hotkey <S-F9> now working again.\r\n+ Syntax check recognizes shopt options.\r\n+ New regex menu: compose regular expressions with a few keystrokes from the menu.\r\n","package":"bash-support.zip","4":"bash-support.zip","src_id":"4756","5":"4756","creation_date":"1131935949","6":"1131935949"},{"0":"365","vim_version":"6.0","1":"6.0","script_version":"1.11","2":"1.11","version_comment":"+ Start debugger bashdb with a keystroke.\r\n+ Parameter, environmnent variables, builtins completed.\r\n+ Code <-> comment working in all modes.\r\n+ Insert\/remove echo for commenting\/uncommenting statements.\r\n+ Script will be made executable before running it (e.g. after a \"Save As...\").","3":"+ Start debugger bashdb with a keystroke.\r\n+ Parameter, environmnent variables, builtins completed.\r\n+ Code <-> comment working in all modes.\r\n+ Insert\/remove echo for commenting\/uncommenting statements.\r\n+ Script will be made executable before running it (e.g. after a \"Save As...\").","package":"bash-support.zip","4":"bash-support.zip","src_id":"4712","5":"4712","creation_date":"1130815812","6":"1130815812"},{"0":"365","vim_version":"6.0","1":"6.0","script_version":"1.10.1","2":"1.10.1","version_comment":"+ Starting an xterm was not possible for some Linux\/Unix installations (bugfix).\r\n","3":"+ Starting an xterm was not possible for some Linux\/Unix installations (bugfix).\r\n","package":"bash-support.zip","4":"bash-support.zip","src_id":"4644","5":"4644","creation_date":"1128308358","6":"1128308358"},{"0":"365","vim_version":"6.0","1":"6.0","script_version":"1.10","2":"1.10","version_comment":"+ Shopt-menu added.\r\n+ New Bash 3.0 set options added.\r\n+ More builtins.\r\n+ <S-F1> or \\h displays help for the Bash builtin command under the cursor.\r\n+ Key mappings for all run menu entries.\r\n+ Line end comments start in a fixed column now (can be set from the menu).\r\n+ Spaces in path names and file names are now possible.\r\n+ Template files and snippet files are no longer kept in the list of alternate files.","3":"+ Shopt-menu added.\r\n+ New Bash 3.0 set options added.\r\n+ More builtins.\r\n+ <S-F1> or \\h displays help for the Bash builtin command under the cursor.\r\n+ Key mappings for all run menu entries.\r\n+ Line end comments start in a fixed column now (can be set from the menu).\r\n+ Spaces in path names and file names are now possible.\r\n+ Template files and snippet files are no longer kept in the list of alternate files.","package":"bash-support.zip","4":"bash-support.zip","src_id":"4513","5":"4513","creation_date":"1124760002","6":"1124760002"},{"0":"365","vim_version":"6.0","1":"6.0","script_version":"1.9","2":"1.9","version_comment":"+ Running a Bash-script \n  (1) The script can be run from the command line as usual.\n  (2) The output can be directed into a window with name \"Bash-Output\". \n  (3) The script can be run in a xterm.\n+ The new hotkey Shift-F9 or the \"cmd. line arg.\" sets command line arguments for the\n  current buffer (that is, each buffer can have its own arguments).\n+ A code snippet with the file name extension \"ni\" or \"noindent\" will not be\n  indented on insertion.\n+ 'Line End Comments' ignores blank lines in a marked block.\n+ Calling a set-command (submenu \"Set\") for a marked block will set this option above\n  this block and unset it below.","3":"+ Running a Bash-script \n  (1) The script can be run from the command line as usual.\n  (2) The output can be directed into a window with name \"Bash-Output\". \n  (3) The script can be run in a xterm.\n+ The new hotkey Shift-F9 or the \"cmd. line arg.\" sets command line arguments for the\n  current buffer (that is, each buffer can have its own arguments).\n+ A code snippet with the file name extension \"ni\" or \"noindent\" will not be\n  indented on insertion.\n+ 'Line End Comments' ignores blank lines in a marked block.\n+ Calling a set-command (submenu \"Set\") for a marked block will set this option above\n  this block and unset it below.","package":"bash-support.zip","4":"bash-support.zip","src_id":"3687","5":"3687","creation_date":"1102329903","6":"1102329903"},{"0":"365","vim_version":"6.0","1":"6.0","script_version":"1.8","2":"1.8","version_comment":"+ Installation simplified.\n+ Run syntax check \/ list errors in an error window.\n+ Append aligned comments to all lines of a marked block.\n+ The root menu can be removed.\n+ The dialog windows (GUI) have been replaced by more flexible command line inputs.\n+ The undocumented and unnecessary hot key F12 has been removed.","3":"+ Installation simplified.\n+ Run syntax check \/ list errors in an error window.\n+ Append aligned comments to all lines of a marked block.\n+ The root menu can be removed.\n+ The dialog windows (GUI) have been replaced by more flexible command line inputs.\n+ The undocumented and unnecessary hot key F12 has been removed.","package":"bash-support.zip","4":"bash-support.zip","src_id":"3217","5":"3217","creation_date":"1089363230","6":"1089363230"},{"0":"365","vim_version":"6.0","1":"6.0","script_version":"1.7","2":"1.7","version_comment":"+ Only one entry in the gVim root menu.\n+ 28 key mappings for Vim without GUI. See bash-hot-keys.pdf (reference card).\n+ All hotkeys are only defined for bash files.\n+ Install script added.\n+ Customization improved. \n+ Vim doc added (file bashsupport.txt).\n+ Documentation improved.\n+ Bug fix (template file handling)","3":"+ Only one entry in the gVim root menu.\n+ 28 key mappings for Vim without GUI. See bash-hot-keys.pdf (reference card).\n+ All hotkeys are only defined for bash files.\n+ Install script added.\n+ Customization improved. \n+ Vim doc added (file bashsupport.txt).\n+ Documentation improved.\n+ Bug fix (template file handling)","package":"bash-support.zip","4":"bash-support.zip","src_id":"2221","5":"2221","creation_date":"1060576637","6":"1060576637"},{"0":"365","vim_version":"6.0","1":"6.0","script_version":"1.5","2":"1.5","version_comment":"+ Tag substitution rewritten (Some characters in a substitution text for a tag  prevented the tag from being substituted).\n+ All bash variables can now be inserted from the menus.\n+ A marked region can be surrounded by a for-, if, select- while- or until   statement (with indentation).\n+ A marked text can be surrounded with quotes.\n+ A marked region or a complete line can be surrounded with echo \" \".\n+ The echo \" \" can be removed from a line.","3":"+ Tag substitution rewritten (Some characters in a substitution text for a tag  prevented the tag from being substituted).\n+ All bash variables can now be inserted from the menus.\n+ A marked region can be surrounded by a for-, if, select- while- or until   statement (with indentation).\n+ A marked text can be surrounded with quotes.\n+ A marked region or a complete line can be surrounded with echo \" \".\n+ The echo \" \" can be removed from a line.","package":"bash-support.zip","4":"bash-support.zip","src_id":"2031","5":"2031","creation_date":"1054376513","6":"1054376513"},{"0":"365","vim_version":"6.0","1":"6.0","script_version":"1.4","2":"1.4","version_comment":"+ Block comments are now read as templates or skeletons from files: \n    frame Comment,  function description,  file header\n+ These templates can contain tags like |FILENAME|, |AUTHOR| etc. which are replaced   after reading.\n+ indentation: multiline inserts and code snippets will be indented after insertion.\n+ Most menu entries are now also active in normal mode.\n+ Reading the templates is done in one function which can be called in an autocmd.\n+ Code cleanup: register z no longer used. Most function calls are silent now.","3":"+ Block comments are now read as templates or skeletons from files: \n    frame Comment,  function description,  file header\n+ These templates can contain tags like |FILENAME|, |AUTHOR| etc. which are replaced   after reading.\n+ indentation: multiline inserts and code snippets will be indented after insertion.\n+ Most menu entries are now also active in normal mode.\n+ Reading the templates is done in one function which can be called in an autocmd.\n+ Code cleanup: register z no longer used. Most function calls are silent now.","package":"bash-support.zip","4":"bash-support.zip","src_id":"1943","5":"1943","creation_date":"1051353546","6":"1051353546"},{"0":"365","vim_version":"6.0","1":"6.0","script_version":"1.3","2":"1.3","version_comment":"Initial upload","3":"Initial upload","package":"bash-support.vim","4":"bash-support.vim","src_id":"1087","5":"1087","creation_date":"1028722569","6":"1028722569"}]},"364":{"script_id":"364","0":"364","script_name":"withdrawn","1":"withdrawn","script_type":"syntax","2":"syntax","summary":"-","3":"-","description":"withdrawn","4":"withdrawn","install_details":"Don't","5":"Don't","first_name":"Charles","6":"Charles","last_name":"Campbell","7":"Campbell","releases":[{"0":"364","vim_version":"6.0","1":"6.0","script_version":"W","2":"W","version_comment":"Withdrawn","3":"Withdrawn","package":"Withdrawn.vim","4":"Withdrawn.vim","src_id":"1413","5":"1413","creation_date":"1037193194","6":"1037193194"}]},"363":{"script_id":"363","0":"363","script_name":"cream-showinvisibles","1":"cream-showinvisibles","script_type":"utility","2":"utility","summary":"Toggle view of invisible tabs, returns, trailing spaces","3":"Toggle view of invisible tabs, returns, trailing spaces","description":"\r\nToggle view of invisible characters such as tabs, trailing spaces and hard returns. The script includes intuitive presets for these characters, a global environmental variable (g:LIST) that is retained and initialized across sessions if you use a viminfo, and a familiar (to some of us) keyboard shortcut mapping to F4.\r\n\r\nThis configuration includes characters as nice looking as your specific setup will allow, determined by hardware, operating system and Vim version. (Vim version 6.1.469 supports multi-byte characters, used with UTF-8 encoding.)\r\n\r\nThis is one of the many custom utilities and functions for gVim from the Cream project (http:\/\/cream.sourceforge.net), a configuration of Vim for those of us familiar with Apple and Windows software. \r\n\r\n","4":"\r\nToggle view of invisible characters such as tabs, trailing spaces and hard returns. The script includes intuitive presets for these characters, a global environmental variable (g:LIST) that is retained and initialized across sessions if you use a viminfo, and a familiar (to some of us) keyboard shortcut mapping to F4.\r\n\r\nThis configuration includes characters as nice looking as your specific setup will allow, determined by hardware, operating system and Vim version. (Vim version 6.1.469 supports multi-byte characters, used with UTF-8 encoding.)\r\n\r\nThis is one of the many custom utilities and functions for gVim from the Cream project (http:\/\/cream.sourceforge.net), a configuration of Vim for those of us familiar with Apple and Windows software. \r\n\r\n","install_details":"\r\nJust drop this file into your plugins directory and start Vim. Then use F4 to toggle invisibles!\r\n\r\n","5":"\r\nJust drop this file into your plugins directory and start Vim. Then use F4 to toggle invisibles!\r\n\r\n","first_name":"Steve","6":"Steve","last_name":"Hall","7":"Hall","releases":[{"0":"363","vim_version":"6.0","1":"6.0","script_version":"3.01","2":"3.01","version_comment":"Fixed typos in trail multi-byte test and extends definitions.","3":"Fixed typos in trail multi-byte test and extends definitions.","package":"cream-showinvisibles.vim","4":"cream-showinvisibles.vim","src_id":"2847","5":"2847","creation_date":"1079804155","6":"1079804155"},{"0":"363","vim_version":"6.0","1":"6.0","script_version":"3.0","2":"3.0","version_comment":"Characters are now selected by their display printability, not encoding. Better looking extended range chars are tried first, the 128 7-bit ASCII set last.","3":"Characters are now selected by their display printability, not encoding. Better looking extended range chars are tried first, the 128 7-bit ASCII set last.","package":"cream-showinvisibles.vim","4":"cream-showinvisibles.vim","src_id":"2845","5":"2845","creation_date":"1079783841","6":"1079783841"},{"0":"363","vim_version":"6.0","1":"6.0","script_version":"2.1","2":"2.1","version_comment":"o Enabled utf-8 chars for Vim v6.2+.    \r\no Added mappings, autocmds for non-Cream.    \r\no Renamed functions.    \r\n(See ChangeLog within file.)\r\n","3":"o Enabled utf-8 chars for Vim v6.2+.    \r\no Added mappings, autocmds for non-Cream.    \r\no Renamed functions.    \r\n(See ChangeLog within file.)\r\n","package":"cream-showinvisibles.vim","4":"cream-showinvisibles.vim","src_id":"2593","5":"2593","creation_date":"1071418459","6":"1071418459"},{"0":"363","vim_version":"6.0","1":"6.0","script_version":"2.0","2":"2.0","version_comment":"New multi-byte sets now available, contingent upon Vim version 6.1.469 and above. Multi-byte characters have also been abstracted to decimal values so the current editing session doesn't affect them.\r\n","3":"New multi-byte sets now available, contingent upon Vim version 6.1.469 and above. Multi-byte characters have also been abstracted to decimal values so the current editing session doesn't affect them.\r\n","package":"cream-showinvisibles.vim","4":"cream-showinvisibles.vim","src_id":"1925","5":"1925","creation_date":"1050589816","6":"1050589816"},{"0":"363","vim_version":"6.0","1":"6.0","script_version":"1.1","2":"1.1","version_comment":"New normal mode mapping and slightly saner visual and insert mode mappings.\r\n","3":"New normal mode mapping and slightly saner visual and insert mode mappings.\r\n","package":"cream-showinvisibles.vim","4":"cream-showinvisibles.vim","src_id":"1077","5":"1077","creation_date":"1028400231","6":"1028400231"},{"0":"363","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"cream-showinvisibles.vim","4":"cream-showinvisibles.vim","src_id":"1075","5":"1075","creation_date":"1028362333","6":"1028362333"}]},"362":{"script_id":"362","0":"362","script_name":"opsplorer","1":"opsplorer","script_type":"utility","2":"utility","summary":"tree file explorer","3":"tree file explorer","description":"The opsplorer script is intended to be an alternative to the file-explorer\r\nplugin that comes with the vim package. It's got a tree structure (you can\r\nalso quickly change the tree root path) and is designed to be as compact as\r\npossible.\r\n\r\nFor detailed description, see :help opsplorer.txt\r\n\r\nHave fun :-)","4":"The opsplorer script is intended to be an alternative to the file-explorer\r\nplugin that comes with the vim package. It's got a tree structure (you can\r\nalso quickly change the tree root path) and is designed to be as compact as\r\npossible.\r\n\r\nFor detailed description, see :help opsplorer.txt\r\n\r\nHave fun :-)","install_details":"- unpack\r\n- drop opsplorer.vim in ~\/.vim\/plugin\r\n- drop opsplorer.txt in ~\/.vim\/doc\r\n- create helpfile tags with :helptags ~\/.vim\/doc","5":"- unpack\r\n- drop opsplorer.vim in ~\/.vim\/plugin\r\n- drop opsplorer.txt in ~\/.vim\/doc\r\n- create helpfile tags with :helptags ~\/.vim\/doc","first_name":"Patrick","6":"Patrick","last_name":"Schiel","7":"Schiel","releases":[{"0":"362","vim_version":"7.0","1":"7.0","script_version":"1.2","2":"1.2","version_comment":"fixed 2 bugs","3":"fixed 2 bugs","package":"opsplorer.zip","4":"opsplorer.zip","src_id":"10271","5":"10271","creation_date":"1237824226","6":"1237824226"},{"0":"362","vim_version":"6.0","1":"6.0","script_version":"1.1","2":"1.1","version_comment":"Added some mappings, added helpfile, changed \"set\" to \"setlocal\" where appropriate, redraw after file operation","3":"Added some mappings, added helpfile, changed \"set\" to \"setlocal\" where appropriate, redraw after file operation","package":"opsplorer.zip","4":"opsplorer.zip","src_id":"1107","5":"1107","creation_date":"1028904618","6":"1028904618"},{"0":"362","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"opsplorer.vim","4":"opsplorer.vim","src_id":"1073","5":"1073","creation_date":"1028208776","6":"1028208776"}]},"361":{"script_id":"361","0":"361","script_name":"snippet.vim","1":"snippet.vim","script_type":"utility","2":"utility","summary":"Replace a word with any text","3":"Replace a word with any text","description":"Snippets are fragments of code, usually related to keywords . \r\nFor example the C language defines \"for\" and \"do\" as keywords, \r\namong others.  Since \"for\" is usually written\r\n    as : \r\n         for (...;...;...) {\r\n                 \/\/code here\r\n         }\r\nMost users will create an abbreviation for the keyword \"for\" to add the\r\nparenthesis and curly-braces such as : \r\n         iabb xFor for<space>(<space>;<space>;<space>)<space>{<cr><cr>}\r\n\r\nTo accomplish this using snippets, create a file with these lines :\r\n\r\n for ( <#cursor#>; ; ) {\r\n\r\n }\r\n\r\nNow when editing a 'c' file, when you type 'for<C-S>' ,for is replaced by the\r\nsnippet of code you placed in the file.  Additionally the cursor is placed \r\nbetween the opening ( and the first ; ... ready for you to begin typing.\r\n","4":"Snippets are fragments of code, usually related to keywords . \r\nFor example the C language defines \"for\" and \"do\" as keywords, \r\namong others.  Since \"for\" is usually written\r\n    as : \r\n         for (...;...;...) {\r\n                 \/\/code here\r\n         }\r\nMost users will create an abbreviation for the keyword \"for\" to add the\r\nparenthesis and curly-braces such as : \r\n         iabb xFor for<space>(<space>;<space>;<space>)<space>{<cr><cr>}\r\n\r\nTo accomplish this using snippets, create a file with these lines :\r\n\r\n for ( <#cursor#>; ; ) {\r\n\r\n }\r\n\r\nNow when editing a 'c' file, when you type 'for<C-S>' ,for is replaced by the\r\nsnippet of code you placed in the file.  Additionally the cursor is placed \r\nbetween the opening ( and the first ; ... ready for you to begin typing.\r\n","install_details":"place plugin\/snippet.vim in your ~\/.vim\/plugin directory\r\nplace syntax\/snippet.vim in your ~\/.vim\/syntax directory\r\nplace doc\/snippet.txt in your ~\/.vim\/doc \r\nsee :he add-local-help for details on adding plugin help.\r\nmkdir ~\/.vim\/snippets ( read help for alternatives )\r\nmkdir ~\/.vim\/snippets\/<syntax>\r\n\r\nto use the snippet syntax file, add : \r\n\r\naugroup filetypedetect \r\n  au! BufRead,BufNewFile *.spt setfiletype snippet \r\naugroup END \r\n\r\nto your filetype.vim \r\n\r\n","5":"place plugin\/snippet.vim in your ~\/.vim\/plugin directory\r\nplace syntax\/snippet.vim in your ~\/.vim\/syntax directory\r\nplace doc\/snippet.txt in your ~\/.vim\/doc \r\nsee :he add-local-help for details on adding plugin help.\r\nmkdir ~\/.vim\/snippets ( read help for alternatives )\r\nmkdir ~\/.vim\/snippets\/<syntax>\r\n\r\nto use the snippet syntax file, add : \r\n\r\naugroup filetypedetect \r\n  au! BufRead,BufNewFile *.spt setfiletype snippet \r\naugroup END \r\n\r\nto your filetype.vim \r\n\r\n","first_name":"Timothy","6":"Timothy","last_name":"Aldrich","7":"Aldrich","releases":[{"0":"361","vim_version":"6.0","1":"6.0","script_version":"1.5","2":"1.5","version_comment":"Minor fix in the include functionality.","3":"Minor fix in the include functionality.","package":"snippet.zip","4":"snippet.zip","src_id":"2620","5":"2620","creation_date":"1071831702","6":"1071831702"},{"0":"361","vim_version":"6.0","1":"6.0","script_version":"1.4","2":"1.4","version_comment":"another Vikas improvement :\r\nchanged visual selection from character wise 'v' to line wise 'V'\r\nincorporates all previous fixes see changelog for list","3":"another Vikas improvement :\r\nchanged visual selection from character wise 'v' to line wise 'V'\r\nincorporates all previous fixes see changelog for list","package":"snippet.zip","4":"snippet.zip","src_id":"1106","5":"1106","creation_date":"1028892055","6":"1028892055"}]},"360":{"script_id":"360","0":"360","script_name":"rcsdiff.vim","1":"rcsdiff.vim","script_type":"utility","2":"utility","summary":"Visual rcsdiff","3":"Visual rcsdiff","description":"This script will create a new command, 'Rcsdiff'.\r\n\r\nNAME\r\n        Rcsdiff - Compare RCS revisions to current working file.\r\n\r\nSYNOPSIS\r\n        :Rcsdiff [rev]\r\n\r\nARGUMENT\r\n        rev - Revision number. [Optional]\r\n \r\nDESCRIPTION\r\n        Display a diff comparison of the current working file and its\r\n        RCS (Revision Control System) revision.\r\n\r\n        An optional argument is provided to compare a specific revision.\r\n        If omitted, the latest revision will be used. This is useful for\r\n        determining changes since the last checkin.\r\n\r\nNOTES\r\n        See the rcsdiff script for more documentation and mappings.","4":"This script will create a new command, 'Rcsdiff'.\r\n\r\nNAME\r\n        Rcsdiff - Compare RCS revisions to current working file.\r\n\r\nSYNOPSIS\r\n        :Rcsdiff [rev]\r\n\r\nARGUMENT\r\n        rev - Revision number. [Optional]\r\n \r\nDESCRIPTION\r\n        Display a diff comparison of the current working file and its\r\n        RCS (Revision Control System) revision.\r\n\r\n        An optional argument is provided to compare a specific revision.\r\n        If omitted, the latest revision will be used. This is useful for\r\n        determining changes since the last checkin.\r\n\r\nNOTES\r\n        See the rcsdiff script for more documentation and mappings.","install_details":"~\/.vim\/plugin\/rcsdiff.vim\r\n\r\n* The RCS checkout utility, 'co', must be on your path.","5":"~\/.vim\/plugin\/rcsdiff.vim\r\n\r\n* The RCS checkout utility, 'co', must be on your path.","first_name":"Brian","6":"Brian","last_name":"Nelson","7":"Nelson","releases":[{"0":"360","vim_version":"6.0","1":"6.0","script_version":"1.2","2":"1.2","version_comment":"* remove <leader> mapping \r\n* update error message handling","3":"* remove <leader> mapping \r\n* update error message handling","package":"rcsdiff.vim","4":"rcsdiff.vim","src_id":"4638","5":"4638","creation_date":"1128075872","6":"1128075872"},{"0":"360","vim_version":"6.0","1":"6.0","script_version":"1.1","2":"1.1","version_comment":"upate email address","3":"upate email address","package":"rcsdiff.vim","4":"rcsdiff.vim","src_id":"3716","5":"3716","creation_date":"1103552498","6":"1103552498"},{"0":"360","vim_version":"6.0","1":"6.0","script_version":"1.1","2":"1.1","version_comment":"Update documentation.","3":"Update documentation.","package":"rcsdiff.vim","4":"rcsdiff.vim","src_id":"2649","5":"2649","creation_date":"1073386664","6":"1073386664"},{"0":"360","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"rcsdiff.vim","4":"rcsdiff.vim","src_id":"1068","5":"1068","creation_date":"1028132837","6":"1028132837"}]},"359":{"script_id":"359","0":"359","script_name":"ABAP.vim","1":"ABAP.vim","script_type":"syntax","2":"syntax","summary":"Syntax highlighting for SAP\/ABAP files","3":"Syntax highlighting for SAP\/ABAP files","description":"It is used to highlight the structure of a ABAP\/4 programs. It is a very early version and only some of the keywords have been highlighted. Send comments to swapan@yahoo.com","4":"It is used to highlight the structure of a ABAP\/4 programs. It is a very early version and only some of the keywords have been highlighted. Send comments to swapan@yahoo.com","install_details":"","5":"","first_name":"Swapan","6":"Swapan","last_name":"Sarkar","7":"Sarkar","releases":[{"0":"359","vim_version":"6.0","1":"6.0","script_version":"0.3","2":"0.3","version_comment":"\" Change Log:\r\n\" 2003 June 16    Jeff Woehler <jrwoehler@softhome.net>\r\n\"  - Numeric values highlighted as constants\r\n\"  - Added many ABAP keywords\/statements.\r\n\"  - Changed 'syn keyword' to 'syn match' on all words with '-' (word barier).","3":"\" Change Log:\r\n\" 2003 June 16    Jeff Woehler <jrwoehler@softhome.net>\r\n\"  - Numeric values highlighted as constants\r\n\"  - Added many ABAP keywords\/statements.\r\n\"  - Changed 'syn keyword' to 'syn match' on all words with '-' (word barier).","package":"abap.vim","4":"abap.vim","src_id":"2085","5":"2085","creation_date":"1055774662","6":"1055774662"},{"0":"359","vim_version":"6.0","1":"6.0","script_version":"0.2","2":"0.2","version_comment":"Bad syntax for line comments fixed (in the 0.1 version clause\r\n\\'select * from mara\\' \r\nwas recognized as comment)","3":"Bad syntax for line comments fixed (in the 0.1 version clause\r\n\\'select * from mara\\' \r\nwas recognized as comment)","package":"abap.vim","4":"abap.vim","src_id":"1420","5":"1420","creation_date":"1037334073","6":"1037334073"},{"0":"359","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"abap.vim","4":"abap.vim","src_id":"1063","5":"1063","creation_date":"1027949466","6":"1027949466"}]},"358":{"script_id":"358","0":"358","script_name":"java_apidoc.vim","1":"java_apidoc.vim","script_type":"ftplugin","2":"ftplugin","summary":"Java API documentation viewer (JavaDoc)","3":"Java API documentation viewer (JavaDoc)","description":"When viewing\/editing a Java source file, put the cursor on an 'import...' line, or on a class name such as 'String', and then press F2. A browser opens showing the API (generated JavaDoc HTML pages) for the imported package or class. The mechanism can be extended to include your own generated JavaDocs.","4":"When viewing\/editing a Java source file, put the cursor on an 'import...' line, or on a class name such as 'String', and then press F2. A browser opens showing the API (generated JavaDoc HTML pages) for the imported package or class. The mechanism can be extended to include your own generated JavaDocs.","install_details":"Put this file in ~\/.vim\/ftplugin (or wherever Vim looks for plugins), then edit the code following the three lines marked in the script with CONFIGURATION to your taste.\r\n\r\nCONFIGURATION - BROWSER\r\nOn a recent RedHat distribution, this should work (as will 'dillo', 'opera', 'ygti'), Windows users will probably want to set this to \"explorer\":\r\n-----------------------------------------------------------------------------\r\nau FileType java let browser=\"htmlview\"\r\n-----------------------------------------------------------------------------\r\n\r\nCONFIGURATION - JAVA API PATH\r\nSet the javadoc_path variable to a comma separated list of paths to  the tops of the Javadoc trees. Change these to match your api locations. Windows users: You should use double backslashes when specifying path names, e.g. C:\\\\jdk\\\\doc\\\\api\r\n-----------------------------------------------------------------------------\r\nlet javadoc_path=\"\/home\/etch\/www\/dox\/java\/j2se1.4.2\/api\"\r\n-----------------------------------------------------------------------------\r\n\r\nCONFIGURATION - KEY ASSIGNMENT\r\nThis is where you, er, assign the key you want to use.\r\n-----------------------------------------------------------------------------\r\nnmap <F2> :call OpenJavadoc()<CR><CR>\r\n-----------------------------------------------------------------------------","5":"Put this file in ~\/.vim\/ftplugin (or wherever Vim looks for plugins), then edit the code following the three lines marked in the script with CONFIGURATION to your taste.\r\n\r\nCONFIGURATION - BROWSER\r\nOn a recent RedHat distribution, this should work (as will 'dillo', 'opera', 'ygti'), Windows users will probably want to set this to \"explorer\":\r\n-----------------------------------------------------------------------------\r\nau FileType java let browser=\"htmlview\"\r\n-----------------------------------------------------------------------------\r\n\r\nCONFIGURATION - JAVA API PATH\r\nSet the javadoc_path variable to a comma separated list of paths to  the tops of the Javadoc trees. Change these to match your api locations. Windows users: You should use double backslashes when specifying path names, e.g. C:\\\\jdk\\\\doc\\\\api\r\n-----------------------------------------------------------------------------\r\nlet javadoc_path=\"\/home\/etch\/www\/dox\/java\/j2se1.4.2\/api\"\r\n-----------------------------------------------------------------------------\r\n\r\nCONFIGURATION - KEY ASSIGNMENT\r\nThis is where you, er, assign the key you want to use.\r\n-----------------------------------------------------------------------------\r\nnmap <F2> :call OpenJavadoc()<CR><CR>\r\n-----------------------------------------------------------------------------","first_name":"Paul","6":"Paul","last_name":"Etchells","7":"Etchells","releases":[{"0":"358","vim_version":"6.0","1":"6.0","script_version":"3.1.1","2":"3.1.1","version_comment":"Version number in the comment was wrong - otherwise identical to the last version. Thanks to eagle-eyed Mike Arms for spotting that.","3":"Version number in the comment was wrong - otherwise identical to the last version. Thanks to eagle-eyed Mike Arms for spotting that.","package":"java_apidoc.vim","4":"java_apidoc.vim","src_id":"3152","5":"3152","creation_date":"1087584660","6":"1087584660"},{"0":"358","vim_version":"6.0","1":"6.0","script_version":"3.1","2":"3.1","version_comment":"Improved Win32 compatability.  Thanks to W. H. Jou for the patch.","3":"Improved Win32 compatability.  Thanks to W. H. Jou for the patch.","package":"java_apidoc.vim","4":"java_apidoc.vim","src_id":"3140","5":"3140","creation_date":"1087392582","6":"1087392582"},{"0":"358","vim_version":"6.0","1":"6.0","script_version":"3.0","2":"3.0","version_comment":"Now same script works on 'nix and win32.","3":"Now same script works on 'nix and win32.","package":"java_apidoc.vim","4":"java_apidoc.vim","src_id":"2885","5":"2885","creation_date":"1080473097","6":"1080473097"},{"0":"358","vim_version":"6.0","1":"6.0","script_version":"1.2","2":"1.2","version_comment":"Now features fast file indexing by using the allclasses-noframe.html or allclasses-frame.html generated during a javadoc pass - well worth having!","3":"Now features fast file indexing by using the allclasses-noframe.html or allclasses-frame.html generated during a javadoc pass - well worth having!","package":"java_apidoc.vim","4":"java_apidoc.vim","src_id":"2798","5":"2798","creation_date":"1078316534","6":"1078316534"},{"0":"358","vim_version":"6.0","1":"6.0","script_version":"1.1","2":"1.1","version_comment":"Skips 'class-use' folders by default, but these can be searched by setting let s:skip_class_use = 1 at the top of the script.","3":"Skips 'class-use' folders by default, but these can be searched by setting let s:skip_class_use = 1 at the top of the script.","package":"java_apidoc.vim","4":"java_apidoc.vim","src_id":"2603","5":"2603","creation_date":"1071556400","6":"1071556400"},{"0":"358","vim_version":"6.0","1":"6.0","script_version":"2.0","2":"2.0","version_comment":"13-Nov-02 Wed 08:18:11 PM \r\nmodified to work in Windows environment\r\n","3":"13-Nov-02 Wed 08:18:11 PM \r\nmodified to work in Windows environment\r\n","package":"java_apidoc.vim","4":"java_apidoc.vim","src_id":"1407","5":"1407","creation_date":"1037161267","6":"1037161267"},{"0":"358","vim_version":"6.0","1":"6.0","script_version":"1.0.1","2":"1.0.1","version_comment":"Some minor errors in the comments, viz: java_api_path should be javadoc_path","3":"Some minor errors in the comments, viz: java_api_path should be javadoc_path","package":"java_apidoc.vim","4":"java_apidoc.vim","src_id":"1062","5":"1062","creation_date":"1027934028","6":"1027934028"},{"0":"358","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"java_apidoc.vim","4":"java_apidoc.vim","src_id":"1061","5":"1061","creation_date":"1027933459","6":"1027933459"}]},"357":{"script_id":"357","0":"357","script_name":"openroad.vim","1":"openroad.vim","script_type":"utility","2":"utility","summary":"Goodies for OpenROAD users","3":"Goodies for OpenROAD users","description":"Some useful mappings & functions for OpenROAD programmers\r\n\r\n1) Shortcut menus for methods, procedures & event blocks  - click on a method\/procedure\/event name & vim jumps to that section of code.\r\nThese functions were based on \"incfiles.vim\" by Thomas Ramming (much changed, I hasten to add - I have actually done some work here!)\r\n\r\n2) Folding - text folds at BEGIN\/END blocks - makes long files easier to navigate\r\n  <F3> opens folds, <F4> closes. To turn off this feature, comment out the line \"set foldmethod=marker\"\r\n\r\n3) Help on keywords - place cursor on an openroad keyword then shift-K opens the appropriate part of the openroad help file (need to use pre-4.1 MR help file)\r\n\r\n4) command completion - type part of a word, press CTRL-space & Vim will guess the rest. I've taken this from \"_vim_wok_visualcpp01.zip\" by Wolfram Esser.\r\n\r\nIt's my first vim script, so I apologise if it seems crude\r\n\r\nPaul Humphrey","4":"Some useful mappings & functions for OpenROAD programmers\r\n\r\n1) Shortcut menus for methods, procedures & event blocks  - click on a method\/procedure\/event name & vim jumps to that section of code.\r\nThese functions were based on \"incfiles.vim\" by Thomas Ramming (much changed, I hasten to add - I have actually done some work here!)\r\n\r\n2) Folding - text folds at BEGIN\/END blocks - makes long files easier to navigate\r\n  <F3> opens folds, <F4> closes. To turn off this feature, comment out the line \"set foldmethod=marker\"\r\n\r\n3) Help on keywords - place cursor on an openroad keyword then shift-K opens the appropriate part of the openroad help file (need to use pre-4.1 MR help file)\r\n\r\n4) command completion - type part of a word, press CTRL-space & Vim will guess the rest. I've taken this from \"_vim_wok_visualcpp01.zip\" by Wolfram Esser.\r\n\r\nIt's my first vim script, so I apologise if it seems crude\r\n\r\nPaul Humphrey","install_details":"Place file in plugins directory","5":"Place file in plugins directory","first_name":"Paul","6":"Paul","last_name":"Humphrey","7":"Humphrey","releases":[{"0":"357","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"openroad.vim","4":"openroad.vim","src_id":"1060","5":"1060","creation_date":"1027930578","6":"1027930578"}]},"356":{"script_id":"356","0":"356","script_name":"dbext.vim","1":"dbext.vim","script_type":"utility","2":"utility","summary":"Provides database access to many DBMS (Oracle, Sybase, Microsoft, MySQL, DBI,..)","3":"Provides database access to many DBMS (Oracle, Sybase, Microsoft, MySQL, DBI,..)","description":"This plugin contains functions\/mappings\/commands to enable Vim to access several databases. \r\n\r\nCurrent databases supported are: \r\nODBC \/ Perl DBI (Any database with a Perl DBI driver)\r\nMySQL\r\nOracle \r\nOracle Rdb (VMS)\r\nSAP HANA\r\nSAP Sybase SQL Anywhere (SA\/ASA)\r\nSAP Sybase IQ (ASA)\r\nSAP Sybase Adaptive Server Enterprise (ASE)\r\nSAP Sybase UltraLite (UL)\r\nMicrosoft SQL Server\r\nIBM DB2\r\nInterbase \r\nSQLite\r\nPostgreSQL\r\nIngres\r\nFirebird\r\nCrate.IO\r\n\r\nFor Perl's DBI layer if the database you are using is not *natively* supported by dbext, but has a DBI interface, dbext's standard feature set is available.  For those already using dbext, the DBI interface should provide a performance boost when running statements against your database.  DBI also provides an ODBC bridge, therefore any ODBC compliant database is also accessible.\r\n\r\nNOTE: As of version 4.0 this plugin requires Vim 7.\r\nVersion 5.0 supports Vim 7's autoload feature.\r\nVersion 25.0 supports Vim 8's Job \/ Channel asynchronous feature.\r\n\r\ndbext provides a common interface between your editor and a database.  If your company\/project moves onto a new database platform, there is no need to learn the new databases tools.  While editing your SQL (and without leaving Vim) you can execute database commands, run queries, display results, and view database objects.  dbext understands various programming languages, and can parse and prompt the user for [host] variables and execute the resulting statement.  See below for more details.\r\n\r\nAdds a menu for the common commands for gvim users.\r\n\r\nSome of the features that are supported:\r\n\r\nTutorial\r\n-----------\r\nA tutorial has been added to help you become familiar with the features of the plugin, :h dbext-tutorial.\r\nIf you dislike reading docs, then at a minimum follow the tutorial.  It will give you the basics of the features and introduce some \"best\" practices, like creating connection profiles.\r\n\r\nConnection Profiles\r\n-----------------------------\r\nYou can create as many profiles as you like in your vimrc.  Each profile specifies various connection information.  Each buffer can be connected to a different database.   The plugin will automatically prompt the user for connection information.  If you have defined profiles in your vimrc, for ease of use,  you can choose from a numbered list.\r\n\r\nAdding connection profiles is the best way to use dbext, :h dbext.txt has lots of examples of different profiles for different databases.\r\n     let g:dbext_default_profile_myASA = 'type=ASA:user=DBA:passwd=SQL'\r\n     let g:dbext_default_profile_mySQLServer = 'type=SQLSRV:integratedlogin=1:srvname=mySrv:dbname=myDB'\r\n     let g:dbext_default_profile_mySQL = 'type=MYSQL:user=root:passwd=whatever:dbname=mysql'\r\n     let g:dbext_default_profile_mySQL_DBI = 'type=DBI:user=root:passwd=whatever:driver=mysql:conn_parms=database=mysql;host=localhost'\r\n     let g:dbext_default_profile_myORA = 'type=ORA:srvname=zzz42ga:user=john:passwd=whatever'\r\n\r\nAssuming you work on many different projects, you can automatically have dbext choose the correct database connection profile by adding autocmds that use the filesystem path to choose the correct profile:\r\n\r\n     augroup project1\r\n         au!\r\n         \" Automatically choose the correct dbext profile\r\n         autocmd BufRead *\/projectX\/sql\/* DBSetOption profile=myASA\r\n     augroup end\r\n\r\n     augroup project2\r\n         au!\r\n         \" Automatically choose the correct dbext profile\r\n         autocmd BufRead *\/projectY\/* DBSetOption profile=myORA\r\n     augroup end\r\n\r\nOr from the menu or the maps created you can choose a profile at any time.\r\n\r\nSQL History\r\n-----------\r\nAs of version 3.0, dbext maintains a history file which is shared between multiple instances of Vim.  A statement added in one instance of Vim will be immediately available in a different instance of Vim on the same computer.  To re-run a statement you can either press <enter> on the line, or if you prefer the mouse you can double click on the statement.\r\n\r\nModeline Support\r\n---------------------------\r\nSimilar to Vim modelines, you can specify connection information as comments within your buffers.  To prevent sensitive information (i.e. passwords) from being visible, you can specify a connection profile as part of your modeline.  \r\n\r\nObject Completion\r\n----------------------------\r\ndbext ties into Vim dictionary feature.  You can complete table names, procedure names and view names using the i_CTRL-X_CTRL-K feature.\r\n\r\nViewing Lists of Objects\r\n------------------------------------\r\nYou can browse through the various objects in the database you are connected to and specify wildcard information.  For example you can say, \"Show me all tables beginning with 'ml_' \".  These objects are currently supported: Tables, Procedures, Views,  Columns (for a table).\r\n\r\nResult Buffer\r\n-------------------\r\nThe output from any of the commands is placed into a new buffer called Result.  In the event of an error, both the error and the command line is included for inspection.\r\n\r\nMappings\r\n----------------\r\nThere are many maps created for convenience.  They exist for most modes (command, visual and insert).\r\n\r\nPlace the cursor on a word, and invoke the default mapping (or menu) and a Result buffer will open with the contents of the table displayed (i.e. select * from <word>.  Optionally you can be prompted for the table name, and a WHERE clause.\r\n\r\nDescribe a table (see column names and datatypes).\r\n\r\nDescribe a stored procedure (see input and output datatypes).\r\n\r\nVisually highlight statements and execute them against the database.\r\n\r\nParsing Statements\r\n-----------------------------\r\nBy default any statement will be parsed looking for input parameters (host variables), if any are found you are prompted to enter a suitable value for the parameter.  This option can be turned off either globally or on a per\r\nbuffer basis.\r\n        SELECT first_name, city\r\n          FROM customer\r\n         WHERE last_name    = @name\r\nIn the case you will be asked for a value for @name.  The rules for defining input parameters are customizable either globally or on a per buffer basis.  The rules for finding these variables can be setup as standard Vim regular expressions.  So if you can find the variables using \/, you can easily customize your own settings using your own naming conventions.  See help file for more details.\r\n\r\nFileType Support\r\n--------------------------\r\nSQL can be used from a variety of languages.  Each development language (PHP, Perl, Java, ...) language has different syntax for creating SQL statements that are sent to the database.  dbext has support for several\r\ndifferent filetypes, so that it can understand and correctly parse a SQL statement.\r\n\r\nThe current supported languages are:\r\n        PHP, Java, JSP, JavaScript, JProperties, Perl, SQL, Vim\r\n\r\nFor example assume you had the following Java code:\r\nString mySQL = \r\n    \"SELECT s.script, ts.event, t.name                  \" +\r\n    \"     , s.script_language, sv.name                  \" +\r\n    \"  FROM ml_script s, ml_table_script ts, ml_table t \" +\r\n                \"     , ml_script_version sv                        \" +\r\n    \" WHERE s.script_id   = \" + script_version +\r\n    \"   AND ts.version_id = \"+obj.method() +\r\n    \"   AND ts.table_id   = t.table_id                  \";\r\n\r\nIf you visually select from the \"SELECT ... to the \"; and ran \r\n :'<,'>DBExecSQL    (or used the default map <Leader>se)\r\n\r\nThe Java filetype support would concatenate each individual string into one\r\nsingle string.  In this case it removed the \" + \" and concatenated  the\r\nlines to result in the following (assuming this is on one line): \r\n       SELECT s.script, ts.event, t.name , s.script_language, sv.name\r\n       FROM ml_script s, ml_table_script ts, ml_table t \r\n                  , ml_script_version sv\r\n      WHERE s.script_id   = \" + script_version + \"\r\n        AND ts.version_id = \"+obj.method() +\"\r\n        AND ts.table_id   = t.table_id \r\n\r\nNext, it will prompt you for replacement values for the various variables or  objects you used in the string.\r\nAssuming you had the default behaviour turned on, you would be prompted  to supply a value for: \r\n                \" + script_version + \"\r\n                \"+obj.method() +\"\r\n\r\nSo assuming you entered: \r\n                100\r\n                'Project_Yahoo'\r\n\r\nThen the resulting string sent to your database would be (again, this would technically be on one line): \r\n       SELECT s.script, ts.event, t.name , s.script_language, sv.name\r\n       FROM ml_script s, ml_table_script ts, ml_table t \r\n                  , ml_script_version sv\r\n      WHERE s.script_id   = 100\r\n        AND ts.version_id = 'Project_Yahoo'\r\n        AND ts.table_id   = t.table_id \r\n\r\nBenefit:  \r\nYou did not have to test your SQL by cutting and pasting it into a separate tool and replacing all the object and host variables yourself.  Just by visually selecting the string and running the command DBExecSQL (or the default mapping <Leader>se) the SQL statement was executed against the database and allowed to you enter host variables.\r\n\r\nAdditional Commands\r\n---------------------------------\r\nDBExecSQL - Enter any command you want sent to the database\r\nDBExecRangeSQL - Enter any range of statements you want executed\r\nSelect  - Enter the remainder of a select (ie :Select * from customer)\r\nCall  - Call a stored procedure\r\nUpdate  - Enter the remainder of an update\r\nInsert  - Enter the remainder of an insert\r\nDelete  - Enter the remainder of an delete\r\nDrop    - Enter the remainder of a drop\r\nAlter   - Enter the remainder of an alter\r\nCreate  - Enter the remainder of a create","4":"This plugin contains functions\/mappings\/commands to enable Vim to access several databases. \r\n\r\nCurrent databases supported are: \r\nODBC \/ Perl DBI (Any database with a Perl DBI driver)\r\nMySQL\r\nOracle \r\nOracle Rdb (VMS)\r\nSAP HANA\r\nSAP Sybase SQL Anywhere (SA\/ASA)\r\nSAP Sybase IQ (ASA)\r\nSAP Sybase Adaptive Server Enterprise (ASE)\r\nSAP Sybase UltraLite (UL)\r\nMicrosoft SQL Server\r\nIBM DB2\r\nInterbase \r\nSQLite\r\nPostgreSQL\r\nIngres\r\nFirebird\r\nCrate.IO\r\n\r\nFor Perl's DBI layer if the database you are using is not *natively* supported by dbext, but has a DBI interface, dbext's standard feature set is available.  For those already using dbext, the DBI interface should provide a performance boost when running statements against your database.  DBI also provides an ODBC bridge, therefore any ODBC compliant database is also accessible.\r\n\r\nNOTE: As of version 4.0 this plugin requires Vim 7.\r\nVersion 5.0 supports Vim 7's autoload feature.\r\nVersion 25.0 supports Vim 8's Job \/ Channel asynchronous feature.\r\n\r\ndbext provides a common interface between your editor and a database.  If your company\/project moves onto a new database platform, there is no need to learn the new databases tools.  While editing your SQL (and without leaving Vim) you can execute database commands, run queries, display results, and view database objects.  dbext understands various programming languages, and can parse and prompt the user for [host] variables and execute the resulting statement.  See below for more details.\r\n\r\nAdds a menu for the common commands for gvim users.\r\n\r\nSome of the features that are supported:\r\n\r\nTutorial\r\n-----------\r\nA tutorial has been added to help you become familiar with the features of the plugin, :h dbext-tutorial.\r\nIf you dislike reading docs, then at a minimum follow the tutorial.  It will give you the basics of the features and introduce some \"best\" practices, like creating connection profiles.\r\n\r\nConnection Profiles\r\n-----------------------------\r\nYou can create as many profiles as you like in your vimrc.  Each profile specifies various connection information.  Each buffer can be connected to a different database.   The plugin will automatically prompt the user for connection information.  If you have defined profiles in your vimrc, for ease of use,  you can choose from a numbered list.\r\n\r\nAdding connection profiles is the best way to use dbext, :h dbext.txt has lots of examples of different profiles for different databases.\r\n     let g:dbext_default_profile_myASA = 'type=ASA:user=DBA:passwd=SQL'\r\n     let g:dbext_default_profile_mySQLServer = 'type=SQLSRV:integratedlogin=1:srvname=mySrv:dbname=myDB'\r\n     let g:dbext_default_profile_mySQL = 'type=MYSQL:user=root:passwd=whatever:dbname=mysql'\r\n     let g:dbext_default_profile_mySQL_DBI = 'type=DBI:user=root:passwd=whatever:driver=mysql:conn_parms=database=mysql;host=localhost'\r\n     let g:dbext_default_profile_myORA = 'type=ORA:srvname=zzz42ga:user=john:passwd=whatever'\r\n\r\nAssuming you work on many different projects, you can automatically have dbext choose the correct database connection profile by adding autocmds that use the filesystem path to choose the correct profile:\r\n\r\n     augroup project1\r\n         au!\r\n         \" Automatically choose the correct dbext profile\r\n         autocmd BufRead *\/projectX\/sql\/* DBSetOption profile=myASA\r\n     augroup end\r\n\r\n     augroup project2\r\n         au!\r\n         \" Automatically choose the correct dbext profile\r\n         autocmd BufRead *\/projectY\/* DBSetOption profile=myORA\r\n     augroup end\r\n\r\nOr from the menu or the maps created you can choose a profile at any time.\r\n\r\nSQL History\r\n-----------\r\nAs of version 3.0, dbext maintains a history file which is shared between multiple instances of Vim.  A statement added in one instance of Vim will be immediately available in a different instance of Vim on the same computer.  To re-run a statement you can either press <enter> on the line, or if you prefer the mouse you can double click on the statement.\r\n\r\nModeline Support\r\n---------------------------\r\nSimilar to Vim modelines, you can specify connection information as comments within your buffers.  To prevent sensitive information (i.e. passwords) from being visible, you can specify a connection profile as part of your modeline.  \r\n\r\nObject Completion\r\n----------------------------\r\ndbext ties into Vim dictionary feature.  You can complete table names, procedure names and view names using the i_CTRL-X_CTRL-K feature.\r\n\r\nViewing Lists of Objects\r\n------------------------------------\r\nYou can browse through the various objects in the database you are connected to and specify wildcard information.  For example you can say, \"Show me all tables beginning with 'ml_' \".  These objects are currently supported: Tables, Procedures, Views,  Columns (for a table).\r\n\r\nResult Buffer\r\n-------------------\r\nThe output from any of the commands is placed into a new buffer called Result.  In the event of an error, both the error and the command line is included for inspection.\r\n\r\nMappings\r\n----------------\r\nThere are many maps created for convenience.  They exist for most modes (command, visual and insert).\r\n\r\nPlace the cursor on a word, and invoke the default mapping (or menu) and a Result buffer will open with the contents of the table displayed (i.e. select * from <word>.  Optionally you can be prompted for the table name, and a WHERE clause.\r\n\r\nDescribe a table (see column names and datatypes).\r\n\r\nDescribe a stored procedure (see input and output datatypes).\r\n\r\nVisually highlight statements and execute them against the database.\r\n\r\nParsing Statements\r\n-----------------------------\r\nBy default any statement will be parsed looking for input parameters (host variables), if any are found you are prompted to enter a suitable value for the parameter.  This option can be turned off either globally or on a per\r\nbuffer basis.\r\n        SELECT first_name, city\r\n          FROM customer\r\n         WHERE last_name    = @name\r\nIn the case you will be asked for a value for @name.  The rules for defining input parameters are customizable either globally or on a per buffer basis.  The rules for finding these variables can be setup as standard Vim regular expressions.  So if you can find the variables using \/, you can easily customize your own settings using your own naming conventions.  See help file for more details.\r\n\r\nFileType Support\r\n--------------------------\r\nSQL can be used from a variety of languages.  Each development language (PHP, Perl, Java, ...) language has different syntax for creating SQL statements that are sent to the database.  dbext has support for several\r\ndifferent filetypes, so that it can understand and correctly parse a SQL statement.\r\n\r\nThe current supported languages are:\r\n        PHP, Java, JSP, JavaScript, JProperties, Perl, SQL, Vim\r\n\r\nFor example assume you had the following Java code:\r\nString mySQL = \r\n    \"SELECT s.script, ts.event, t.name                  \" +\r\n    \"     , s.script_language, sv.name                  \" +\r\n    \"  FROM ml_script s, ml_table_script ts, ml_table t \" +\r\n                \"     , ml_script_version sv                        \" +\r\n    \" WHERE s.script_id   = \" + script_version +\r\n    \"   AND ts.version_id = \"+obj.method() +\r\n    \"   AND ts.table_id   = t.table_id                  \";\r\n\r\nIf you visually select from the \"SELECT ... to the \"; and ran \r\n :'<,'>DBExecSQL    (or used the default map <Leader>se)\r\n\r\nThe Java filetype support would concatenate each individual string into one\r\nsingle string.  In this case it removed the \" + \" and concatenated  the\r\nlines to result in the following (assuming this is on one line): \r\n       SELECT s.script, ts.event, t.name , s.script_language, sv.name\r\n       FROM ml_script s, ml_table_script ts, ml_table t \r\n                  , ml_script_version sv\r\n      WHERE s.script_id   = \" + script_version + \"\r\n        AND ts.version_id = \"+obj.method() +\"\r\n        AND ts.table_id   = t.table_id \r\n\r\nNext, it will prompt you for replacement values for the various variables or  objects you used in the string.\r\nAssuming you had the default behaviour turned on, you would be prompted  to supply a value for: \r\n                \" + script_version + \"\r\n                \"+obj.method() +\"\r\n\r\nSo assuming you entered: \r\n                100\r\n                'Project_Yahoo'\r\n\r\nThen the resulting string sent to your database would be (again, this would technically be on one line): \r\n       SELECT s.script, ts.event, t.name , s.script_language, sv.name\r\n       FROM ml_script s, ml_table_script ts, ml_table t \r\n                  , ml_script_version sv\r\n      WHERE s.script_id   = 100\r\n        AND ts.version_id = 'Project_Yahoo'\r\n        AND ts.table_id   = t.table_id \r\n\r\nBenefit:  \r\nYou did not have to test your SQL by cutting and pasting it into a separate tool and replacing all the object and host variables yourself.  Just by visually selecting the string and running the command DBExecSQL (or the default mapping <Leader>se) the SQL statement was executed against the database and allowed to you enter host variables.\r\n\r\nAdditional Commands\r\n---------------------------------\r\nDBExecSQL - Enter any command you want sent to the database\r\nDBExecRangeSQL - Enter any range of statements you want executed\r\nSelect  - Enter the remainder of a select (ie :Select * from customer)\r\nCall  - Call a stored procedure\r\nUpdate  - Enter the remainder of an update\r\nInsert  - Enter the remainder of an insert\r\nDelete  - Enter the remainder of an delete\r\nDrop    - Enter the remainder of a drop\r\nAlter   - Enter the remainder of an alter\r\nCreate  - Enter the remainder of a create","install_details":"The zip file contains the necessary path structure.\r\n\r\nOn *nix, unzip into:\r\n$HOME\/.vim\/\r\n\r\nOn Windows unzip into:\r\nvim\/vimfiles\/\r\n\r\nFiles:\r\nplugin\/dbext.vim \r\nautoload\/dbext.vim\r\nautoload\/dbext_dbi.vim\r\ndoc\/dbext.txt\r\n\r\nTo update the Vim Help, run:\r\n:helptags $HOME\/.vim\/doc  (Unix)\r\n:helptags $VIM\/vimfiles\/doc  (Windows)\r\n\r\nDependencies\r\n----------------------\r\nThe autoload\/SQLComplete.vim file uses dbext.vim for dynamic code completion.  This file has been included with dbext.vim but it is normally included with the standard Vim runtime.  David Fishburn is also the author of this plugin.  It was enhanced to support SQL objects with spaces.  It can also be downloaded separately from here: http:\/\/www.vim.org\/scripts\/script.php?script_id=1572\r\n\r\nMaintainer\r\n--------------\r\nDavid Fishburn, for issues please post to the Vim mailing list, or to David directly.  \r\n:h dbext.txt has contact details.\r\n","5":"The zip file contains the necessary path structure.\r\n\r\nOn *nix, unzip into:\r\n$HOME\/.vim\/\r\n\r\nOn Windows unzip into:\r\nvim\/vimfiles\/\r\n\r\nFiles:\r\nplugin\/dbext.vim \r\nautoload\/dbext.vim\r\nautoload\/dbext_dbi.vim\r\ndoc\/dbext.txt\r\n\r\nTo update the Vim Help, run:\r\n:helptags $HOME\/.vim\/doc  (Unix)\r\n:helptags $VIM\/vimfiles\/doc  (Windows)\r\n\r\nDependencies\r\n----------------------\r\nThe autoload\/SQLComplete.vim file uses dbext.vim for dynamic code completion.  This file has been included with dbext.vim but it is normally included with the standard Vim runtime.  David Fishburn is also the author of this plugin.  It was enhanced to support SQL objects with spaces.  It can also be downloaded separately from here: http:\/\/www.vim.org\/scripts\/script.php?script_id=1572\r\n\r\nMaintainer\r\n--------------\r\nDavid Fishburn, for issues please post to the Vim mailing list, or to David directly.  \r\n:h dbext.txt has contact details.\r\n","first_name":"Peter","6":"Peter","last_name":"Bagyinszki","7":"Bagyinszki","releases":[{"0":"356","vim_version":"8.0","1":"8.0","script_version":"26.00","2":"26.00","version_comment":"New Features\r\n------------\r\n- New option g:dbext_default_job_show_msgs to control whether information messages are displayed when starting and stop jobs.  Regular status messages continue to display.\r\n- New option g:dbext_default_job_pipe_regex to control how to identify and strip piped in files and specify it separately via job options.\r\n- Renamed option g:dbext_default_use_jobs to g:dbext_default_job_enable to better support tab completion for the DBSetOption command.\r\n                                                                          \r\nBug Fixes\r\n---------\r\n- Also check for 'timers' when checking for job support.\r\n- Revamped job support.  Tested on Windows, Linux and OSX.  Works on long running and very short jobs where it was erratic on first release.\r\n","3":"New Features\r\n------------\r\n- New option g:dbext_default_job_show_msgs to control whether information messages are displayed when starting and stop jobs.  Regular status messages continue to display.\r\n- New option g:dbext_default_job_pipe_regex to control how to identify and strip piped in files and specify it separately via job options.\r\n- Renamed option g:dbext_default_use_jobs to g:dbext_default_job_enable to better support tab completion for the DBSetOption command.\r\n                                                                          \r\nBug Fixes\r\n---------\r\n- Also check for 'timers' when checking for job support.\r\n- Revamped job support.  Tested on Windows, Linux and OSX.  Works on long running and very short jobs where it was erratic on first release.\r\n","package":"dbext_2600.zip","4":"dbext_2600.zip","src_id":"25648","5":"25648","creation_date":"1510943534","6":"1510943534"},{"0":"356","vim_version":"7.2","1":"7.2","script_version":"25.00","2":"25.00","version_comment":"Posted by David Fishburn\r\n\r\nNew Features\r\n------------\r\n- Added support for using Vim's Job \/ Channel feature for asynchronous execution.  If the job fails to start, the usual synchronous way of launching the process happens (after displaying a message).  The main purpose for this feature is to allow you to continue editing your files while waiting for the results from SQL statements to complete.  Prior to Vim's Job feature, this was a synchronous process which could interrupt your development needlessly.\r\n\r\n- New commands DBJobStatus, DBJobStop, DBJobTimerStart, DBJobTimerStop.\r\n\r\n- New options g:dbext_default_use_jobs defaults to 1 (enabled),  g:dbext_default_job_status_update_ms defaults to 2000.\r\n                                                                        \r\nBug Fixes\r\n---------\r\n- None\r\n","3":"Posted by David Fishburn\r\n\r\nNew Features\r\n------------\r\n- Added support for using Vim's Job \/ Channel feature for asynchronous execution.  If the job fails to start, the usual synchronous way of launching the process happens (after displaying a message).  The main purpose for this feature is to allow you to continue editing your files while waiting for the results from SQL statements to complete.  Prior to Vim's Job feature, this was a synchronous process which could interrupt your development needlessly.\r\n\r\n- New commands DBJobStatus, DBJobStop, DBJobTimerStart, DBJobTimerStop.\r\n\r\n- New options g:dbext_default_use_jobs defaults to 1 (enabled),  g:dbext_default_job_status_update_ms defaults to 2000.\r\n                                                                        \r\nBug Fixes\r\n---------\r\n- None\r\n","package":"dbext_2500.zip","4":"dbext_2500.zip","src_id":"24935","5":"24935","creation_date":"1485829645","6":"1485829645"},{"0":"356","vim_version":"7.2","1":"7.2","script_version":"24.00","2":"24.00","version_comment":"Posted by David Fishburn\r\n\r\n New Features\r\n ------------\r\n - Added missing menu items for Execute All (sea), Execute Line (sel), Execute Previous Visual Selection (sep) (pull #18) (Rapha\u00c3\u00abl Bade)\r\n\r\n - When using ?s as input parameters, these can now be remembered and used when saving previous values when executing the query.\r\n\r\n - Additional examples of connecting to Oracle using DBI\/ODBC without a TNSNAMES entry.\r\n\r\n - Strip off ending cmd terminators for the DBI database type as some databases (Oracle) complain about them (Bruce Hunsaker).\r\n\r\n - For native Oracle connections, when retrieving database objects (tables, procedures, columns, ...) ignore case (Dimitri Belov).\r\n\r\n Bug Fixes\r\n ---------\r\n - For Java, CSharp, JSP, HTML and JavaScript files, remove line continuation (backslash) characters before sending request to database.\r\n\r\n - Better error handling for the DBI \/ ODBC databases (Michael Graham, Bruce Hunsaker, Dimitri Belov, Will Wyatt).\r\n\r\n - The @ask[bg] parameter was not supported properly in later releases (Richard Tsai, Nan Jia).\r\n\r\n - Vim error - Invalid range reported for the SQL history (Bruce Hunsaker).\r\n\r\n - DBI \/ ODBC CommitOnDisconnect driver parameter is not supported by all drivers, handle cleanly (Dimitri Belov).\r\n\r\n - DBI \/ ODBC Disconnect reported a Vim error (Dimitri Belov).\r\n","3":"Posted by David Fishburn\r\n\r\n New Features\r\n ------------\r\n - Added missing menu items for Execute All (sea), Execute Line (sel), Execute Previous Visual Selection (sep) (pull #18) (Rapha\u00c3\u00abl Bade)\r\n\r\n - When using ?s as input parameters, these can now be remembered and used when saving previous values when executing the query.\r\n\r\n - Additional examples of connecting to Oracle using DBI\/ODBC without a TNSNAMES entry.\r\n\r\n - Strip off ending cmd terminators for the DBI database type as some databases (Oracle) complain about them (Bruce Hunsaker).\r\n\r\n - For native Oracle connections, when retrieving database objects (tables, procedures, columns, ...) ignore case (Dimitri Belov).\r\n\r\n Bug Fixes\r\n ---------\r\n - For Java, CSharp, JSP, HTML and JavaScript files, remove line continuation (backslash) characters before sending request to database.\r\n\r\n - Better error handling for the DBI \/ ODBC databases (Michael Graham, Bruce Hunsaker, Dimitri Belov, Will Wyatt).\r\n\r\n - The @ask[bg] parameter was not supported properly in later releases (Richard Tsai, Nan Jia).\r\n\r\n - Vim error - Invalid range reported for the SQL history (Bruce Hunsaker).\r\n\r\n - DBI \/ ODBC CommitOnDisconnect driver parameter is not supported by all drivers, handle cleanly (Dimitri Belov).\r\n\r\n - DBI \/ ODBC Disconnect reported a Vim error (Dimitri Belov).\r\n","package":"dbext_2400.zip","4":"dbext_2400.zip","src_id":"24519","5":"24519","creation_date":"1473636283","6":"1473636283"},{"0":"356","vim_version":"7.2","1":"7.2","script_version":"23.00","2":"23.00","version_comment":"Posted by David Fishburn\r\n\r\nNew Features\r\n------------\r\n- Added a new database, CrateIO (Mathias Fussenegger)\r\n- CRATE native database type and Crate via DBI are supported\r\n- Updated the DBI SQLAnywhere procedure list to respect the option of whether to include the object owner names\r\n- Added a new public function, DB_DictionaryDelete, to be used by the OMNI SQL Completion plugin (autoload\/sqlcomplete.vim, which is part of Vim)\r\n                                                                               \r\nBug Fixes\r\n---------\r\n- helptags reported duplicate tag MyProjectDir, updated documentation as a work around as there is no way to escape the real syntax (pull #3) (mexpolk)\r\n- For PGSQL, use the \"schemaname\" column rather than \"tableowner\" (pull #15) (Stefan Litsche)\r\n","3":"Posted by David Fishburn\r\n\r\nNew Features\r\n------------\r\n- Added a new database, CrateIO (Mathias Fussenegger)\r\n- CRATE native database type and Crate via DBI are supported\r\n- Updated the DBI SQLAnywhere procedure list to respect the option of whether to include the object owner names\r\n- Added a new public function, DB_DictionaryDelete, to be used by the OMNI SQL Completion plugin (autoload\/sqlcomplete.vim, which is part of Vim)\r\n                                                                               \r\nBug Fixes\r\n---------\r\n- helptags reported duplicate tag MyProjectDir, updated documentation as a work around as there is no way to escape the real syntax (pull #3) (mexpolk)\r\n- For PGSQL, use the \"schemaname\" column rather than \"tableowner\" (pull #15) (Stefan Litsche)\r\n","package":"dbext_2300.zip","4":"dbext_2300.zip","src_id":"23862","5":"23862","creation_date":"1451866087","6":"1451866087"},{"0":"356","vim_version":"7.2","1":"7.2","script_version":"22.00","2":"22.00","version_comment":"Posted by David Fishburn\r\n\r\nNew Features\r\n------------\r\n- Overhauled the prompting for SQL statement variable substitution (i.e. host variables, named parameters, question marks, ...).  The actions and user interface are hopefully more clear, useful and efficient.  For a full updated tutorial on how it works see :h dbext-tutorial-variables\r\n\r\n- Saved variables can now hold multiple values for the same parameter, see :h dbext-tutorial-variables for how it works.\r\n\r\n- Added C++ language support for variables (pull #12) (Anatolii Sakhnik).\r\n\r\n- Added the ability to specify special characters (i.e. \"\\t\") for column delimiters when using ODBC or DBI database types (Michael Krnac).\r\n\r\n- Added new option, \"passwd_use_secret\", which is used when entering a password, if the value should be masked.  When using a GUI version of Vim, the prompt is not displayed in a dialog unlike the other parameters.  This option is OFF (0) by default. (pull #13) (petteja)\r\n\r\n- Added new option, \"strip_into\", which is used when executing statements which have variable assignments using the INTO clause.  To test these queries, you need to remove the INTO clause so that when they execute the query you can see the result set returned.  This was on for all databases, but for TransactSQL or TSQL databases like SQLSRV and ASE, stripping the INTO clause may be the wrong action.  Now it can be controlled using this setting.  This can also be set \/ overridden using DBSetOption strip_into=1 or as part of a dbext profile.\r\n\r\n- Added new option, \"strip_at_variables\", which is executing statements which have variable assignments in the SELECT list instead of the INTO clause.  To test these queries, you need to remove the assignments when they execute to see the result set returned.  This was on for all databases, but for TransactSQL or TSQL databases like SQLSRV and ASE, stripping the variable assignments in the SELECT list is required. This can be controlled via this setting.  This can also be set \/ overridden using DBSetOption strip_at_variables=1 or as part of a dbext profile.\r\n                                                                                 \r\nBug Fixes\r\n---------\r\n- Minor correction to DBSetVar example (Cedric Simon).\r\n\r\n- When deleting a buffer, all syntax highlighting of your existing buffer is sometimes lost, which was a problem with one of the\r\n  dbext autocmds (Anatolii Sakhnik).\r\n\r\n- Update Postgres get column list join conditions (pull #9) (Dickson S. Guedes).\r\n\r\n- dbext autocmd for checking for modelines messed up the jumplist (Justin M. Keyes)\r\n","3":"Posted by David Fishburn\r\n\r\nNew Features\r\n------------\r\n- Overhauled the prompting for SQL statement variable substitution (i.e. host variables, named parameters, question marks, ...).  The actions and user interface are hopefully more clear, useful and efficient.  For a full updated tutorial on how it works see :h dbext-tutorial-variables\r\n\r\n- Saved variables can now hold multiple values for the same parameter, see :h dbext-tutorial-variables for how it works.\r\n\r\n- Added C++ language support for variables (pull #12) (Anatolii Sakhnik).\r\n\r\n- Added the ability to specify special characters (i.e. \"\\t\") for column delimiters when using ODBC or DBI database types (Michael Krnac).\r\n\r\n- Added new option, \"passwd_use_secret\", which is used when entering a password, if the value should be masked.  When using a GUI version of Vim, the prompt is not displayed in a dialog unlike the other parameters.  This option is OFF (0) by default. (pull #13) (petteja)\r\n\r\n- Added new option, \"strip_into\", which is used when executing statements which have variable assignments using the INTO clause.  To test these queries, you need to remove the INTO clause so that when they execute the query you can see the result set returned.  This was on for all databases, but for TransactSQL or TSQL databases like SQLSRV and ASE, stripping the INTO clause may be the wrong action.  Now it can be controlled using this setting.  This can also be set \/ overridden using DBSetOption strip_into=1 or as part of a dbext profile.\r\n\r\n- Added new option, \"strip_at_variables\", which is executing statements which have variable assignments in the SELECT list instead of the INTO clause.  To test these queries, you need to remove the assignments when they execute to see the result set returned.  This was on for all databases, but for TransactSQL or TSQL databases like SQLSRV and ASE, stripping the variable assignments in the SELECT list is required. This can be controlled via this setting.  This can also be set \/ overridden using DBSetOption strip_at_variables=1 or as part of a dbext profile.\r\n                                                                                 \r\nBug Fixes\r\n---------\r\n- Minor correction to DBSetVar example (Cedric Simon).\r\n\r\n- When deleting a buffer, all syntax highlighting of your existing buffer is sometimes lost, which was a problem with one of the\r\n  dbext autocmds (Anatolii Sakhnik).\r\n\r\n- Update Postgres get column list join conditions (pull #9) (Dickson S. Guedes).\r\n\r\n- dbext autocmd for checking for modelines messed up the jumplist (Justin M. Keyes)\r\n","package":"dbext_2200.zip","4":"dbext_2200.zip","src_id":"23512","5":"23512","creation_date":"1439244416","6":"1439244416"},{"0":"356","vim_version":"7.0","1":"7.0","script_version":"21.00","2":"21.00","version_comment":"Posted by David Fishburn (maintainer) \r\n\r\nNew Features\r\n------------\r\n- Added new database, SAP Sybase IQ.\r\n\r\n- Added ability to describe SAP HANA stored procedures using DBI\/ODBC.\r\n\r\n- Added new command, DBProfilesRefresh, which will repopulate the profile list from your global variables without having to restart Vim.\r\n\r\n- Updated dbext profiles and modelines to accept special characters (\\t) as the column delimiter for DBI connections (Josef Fortier).\r\n                                                                              \r\nBug Fixes\r\n---------\r\n- Sometimes after setting a connection profile would still prompt you the first time you attempted to use the connection.\r\n\r\n- For PostgreSQL, check for .pgpass on *nix variants and pgpass.conf on windows (Collin Peters).\r\n\r\n- Some connection parameters were overridden incorrectly when first applying the dbext_default_profile (Lyude, Martin Chabot, Will Wyatt, Bruno Sutic).\r\n\r\n- Worked around an issue with the vim-gitgutter dbext plugin (airblade).\r\n\r\n- There were 3 places where we fetch Vim's variables to check for dbext profiles and other dbext settings.  These have changed these to fetch only Vim's global variables to reduce the amount returned and hopefully increase the response time (Michael Jansen).\r\n","3":"Posted by David Fishburn (maintainer) \r\n\r\nNew Features\r\n------------\r\n- Added new database, SAP Sybase IQ.\r\n\r\n- Added ability to describe SAP HANA stored procedures using DBI\/ODBC.\r\n\r\n- Added new command, DBProfilesRefresh, which will repopulate the profile list from your global variables without having to restart Vim.\r\n\r\n- Updated dbext profiles and modelines to accept special characters (\\t) as the column delimiter for DBI connections (Josef Fortier).\r\n                                                                              \r\nBug Fixes\r\n---------\r\n- Sometimes after setting a connection profile would still prompt you the first time you attempted to use the connection.\r\n\r\n- For PostgreSQL, check for .pgpass on *nix variants and pgpass.conf on windows (Collin Peters).\r\n\r\n- Some connection parameters were overridden incorrectly when first applying the dbext_default_profile (Lyude, Martin Chabot, Will Wyatt, Bruno Sutic).\r\n\r\n- Worked around an issue with the vim-gitgutter dbext plugin (airblade).\r\n\r\n- There were 3 places where we fetch Vim's variables to check for dbext profiles and other dbext settings.  These have changed these to fetch only Vim's global variables to reduce the amount returned and hopefully increase the response time (Michael Jansen).\r\n","package":"dbext_2100.zip","4":"dbext_2100.zip","src_id":"22865","5":"22865","creation_date":"1423057100","6":"1423057100"},{"0":"356","vim_version":"7.0","1":"7.0","script_version":"20.00","2":"20.00","version_comment":"Posted by David Fishburn (maintainer)\r\n\r\nNew Features\r\n------------\r\n- Added new DBI\/ODBC option DBI_max_column_width to restrict the width displayed in the DBI result window (Luke Mauldin).\r\n\r\n- Improved the pattern used to find the query under the cursor.  Besides finding the command terminator, it will also look for the first blank line or the end of the file (Jason Quirk).\r\n\r\n- The dbext menu now uses the maps rather than calls to the commands. A new option will control this behaviour, g:dbext_map_or_cmd.\r\n\r\n- Changed the default SQLite binary to be sqlite3 instead of sqlite (Greg Kapfhammer).\r\n\r\n- Added a profile example for using the \"sqsh\" binary to connect to SQL Server instead of \"osql\" (Brian Iv\u00c3\u00a1n Mart\u00c3\u00adnez).\r\n\r\n- The cmd_terminator displayed under Connection Options in the DBGetOption output was always blank.\r\n\r\n- Improved support for SAP HANA database, pulling objects from the system catalogue.\r\n         \r\n                                                                  \r\nBug Fixes\r\n---------\r\n- Controlling the DBI max rows (:DBSetOption DBI_max_rows=100) and DBI column separator did not work on a per buffer basis.\r\n\r\n- Undefined variable, s:dbext_prev_winnr, was reported when using DBI\/ODBC connections through the sqlComplete plugin and completing objects which require an active database connection (i.e. Tables,  Procedures, ...) which had failed to connect to the database.\r\n\r\n- dbext was not prompting for ? parameters in PHP files.  This also affected all languages (J\u00c3\u00a9r\u00c3\u00a9mie).\r\n\r\n- Changing a database's global cmd terminator was not necessarily picked up when using that database type (Jason Quirk).\r\n\r\n- ODBC or DBI could report an error about using length() instead of scalar() (Micah Duke).\r\n\r\n- Various errors on Linux with DBI (Micah Duke).\r\n\r\n- Using the console version of Vim displayed a number of \"debug\" messages during initialization.\r\n\r\n","3":"Posted by David Fishburn (maintainer)\r\n\r\nNew Features\r\n------------\r\n- Added new DBI\/ODBC option DBI_max_column_width to restrict the width displayed in the DBI result window (Luke Mauldin).\r\n\r\n- Improved the pattern used to find the query under the cursor.  Besides finding the command terminator, it will also look for the first blank line or the end of the file (Jason Quirk).\r\n\r\n- The dbext menu now uses the maps rather than calls to the commands. A new option will control this behaviour, g:dbext_map_or_cmd.\r\n\r\n- Changed the default SQLite binary to be sqlite3 instead of sqlite (Greg Kapfhammer).\r\n\r\n- Added a profile example for using the \"sqsh\" binary to connect to SQL Server instead of \"osql\" (Brian Iv\u00c3\u00a1n Mart\u00c3\u00adnez).\r\n\r\n- The cmd_terminator displayed under Connection Options in the DBGetOption output was always blank.\r\n\r\n- Improved support for SAP HANA database, pulling objects from the system catalogue.\r\n         \r\n                                                                  \r\nBug Fixes\r\n---------\r\n- Controlling the DBI max rows (:DBSetOption DBI_max_rows=100) and DBI column separator did not work on a per buffer basis.\r\n\r\n- Undefined variable, s:dbext_prev_winnr, was reported when using DBI\/ODBC connections through the sqlComplete plugin and completing objects which require an active database connection (i.e. Tables,  Procedures, ...) which had failed to connect to the database.\r\n\r\n- dbext was not prompting for ? parameters in PHP files.  This also affected all languages (J\u00c3\u00a9r\u00c3\u00a9mie).\r\n\r\n- Changing a database's global cmd terminator was not necessarily picked up when using that database type (Jason Quirk).\r\n\r\n- ODBC or DBI could report an error about using length() instead of scalar() (Micah Duke).\r\n\r\n- Various errors on Linux with DBI (Micah Duke).\r\n\r\n- Using the console version of Vim displayed a number of \"debug\" messages during initialization.\r\n\r\n","package":"dbext_2000.zip","4":"dbext_2000.zip","src_id":"20843","5":"20843","creation_date":"1380069136","6":"1380069136"},{"0":"356","vim_version":"7.0","1":"7.0","script_version":"19.0","2":"19.0","version_comment":"Posted by David Fishburn\r\n\r\nNew Features\r\n------------\r\n- Added support for parsing C# files (Raul Segura Acevedo).\r\n- Updated the PostgreSQL message when the .pgpass file is missing (Dav Clark).\r\n                                                                                                     \r\nBug Fixes\r\n---------\r\n- When prompting for connection parameters a second time, the previously chosen profile number was not defaulted.\r\n- If a dbext login script was stored in the $HOME directory it would never be found (Tim Teufel).\r\n- The first host variable was prompted for replacement, but the second one was not (Stanimir Mladenov).\r\n- Selecting a visual region with leading and ending double quotes (like a table name) could report invalid arguments for the following commands: DBSelectFromTable, DBSelectFromTableTopX, DBDescribeTable, DBDescribeProcedure, DBListColumn\r\n- For DB2 on the mainframe the command line utilities do not support the -t switch.  If you override the buffer specific cmd_terminator setting and set this value to an empty string the -t will be left off.  This can be most easily specified in a dbext connection profile (Michael McDermott):\r\n     let g:dbext_default_profile_MyDB2 = 'type=DB2:user=me:passwd=mypass:dbname=SSD:cmd_terminator='\r\n  Or while within a buffer:\r\n     DBSetOption cmd_terminator=\r\n     DBSetOption cmd_terminator=;\r\n","3":"Posted by David Fishburn\r\n\r\nNew Features\r\n------------\r\n- Added support for parsing C# files (Raul Segura Acevedo).\r\n- Updated the PostgreSQL message when the .pgpass file is missing (Dav Clark).\r\n                                                                                                     \r\nBug Fixes\r\n---------\r\n- When prompting for connection parameters a second time, the previously chosen profile number was not defaulted.\r\n- If a dbext login script was stored in the $HOME directory it would never be found (Tim Teufel).\r\n- The first host variable was prompted for replacement, but the second one was not (Stanimir Mladenov).\r\n- Selecting a visual region with leading and ending double quotes (like a table name) could report invalid arguments for the following commands: DBSelectFromTable, DBSelectFromTableTopX, DBDescribeTable, DBDescribeProcedure, DBListColumn\r\n- For DB2 on the mainframe the command line utilities do not support the -t switch.  If you override the buffer specific cmd_terminator setting and set this value to an empty string the -t will be left off.  This can be most easily specified in a dbext connection profile (Michael McDermott):\r\n     let g:dbext_default_profile_MyDB2 = 'type=DB2:user=me:passwd=mypass:dbname=SSD:cmd_terminator='\r\n  Or while within a buffer:\r\n     DBSetOption cmd_terminator=\r\n     DBSetOption cmd_terminator=;\r\n","package":"dbext_1900.zip","4":"dbext_1900.zip","src_id":"19989","5":"19989","creation_date":"1367370761","6":"1367370761"},{"0":"356","vim_version":"7.0","1":"7.0","script_version":"18.0","2":"18.0","version_comment":"Posted by David Fishburn\r\n\r\nNew Features\r\n------------\r\n- Added support for parsing C# files (Raul Segura Acevedo).\r\n                                                                             \r\nBug Fixes\r\n---------\r\n- Changed the Oracle calls to SQLPlus from using single quotes to using double quotes (David Sweeney).\r\n- The <Leader>sbp and <Leader>tcl mapping were missing with version 17.00.\r\n- The DBI interface could report: \"E15: Invalid expression\" when retrieving table lists from DB2, but this could also affect other SQL commands that returned strings surrounded in double quotes (Charles McGarvey).\r\n","3":"Posted by David Fishburn\r\n\r\nNew Features\r\n------------\r\n- Added support for parsing C# files (Raul Segura Acevedo).\r\n                                                                             \r\nBug Fixes\r\n---------\r\n- Changed the Oracle calls to SQLPlus from using single quotes to using double quotes (David Sweeney).\r\n- The <Leader>sbp and <Leader>tcl mapping were missing with version 17.00.\r\n- The DBI interface could report: \"E15: Invalid expression\" when retrieving table lists from DB2, but this could also affect other SQL commands that returned strings surrounded in double quotes (Charles McGarvey).\r\n","package":"dbext_1800.zip","4":"dbext_1800.zip","src_id":"19052","5":"19052","creation_date":"1354064331","6":"1354064331"},{"0":"356","vim_version":"7.0","1":"7.0","script_version":"17.0","2":"17.0","version_comment":"Posted by David Fishburn\r\n\r\nNew Features\r\n------------\r\n- Added new database type, the SAP HANA in memory database.\r\n\r\n- Added new option, ignore_variable_regex, which is used when parsing your statement for replacable input parameters (i.e. placeholders for prepared statements).  Certain variables need to be skipped (for example when running a CREATE PROCEDURE statement) to leave the logic inside the stored procedure intact.  This option allows the user finer control over the regex used to decide which SQL syntax should be skipped.\r\n\r\n- Added new option, statement_starts_line, which is used when deciding if the query should be parsed for input parameters.  Certain filetypes assume the statements can be embedded within strings (like in Java, PHP, Perl and so on).\r\n\r\n- When parsing PHP and Java files, leading and trailing quotes are stripped automatically when executing the query, which could lead to incorrect results.  First check if there is a leading quote.  If so, then only strip the corresponding closing quote.\r\n\r\n- Updated documentation describing the default regex for variable_def_regex.\r\n- Added new option g:dbext_map_prefix which defaults to <Leader>s, this allows you to customize the start of all the default maps (Daniel Hahler).\r\n                                                                                \r\nBug Fixes\r\n---------\r\n- The default value for variable_def_regex, did not properly escape the $, which lead to some query parameters being skipped when executing SQL.\r\n\r\n- It was impossible to search and replace input parameters within a query if the parameter was enclosed in single quotes.  The above new features were required to make this possible (Joshua Dennis).\r\n\r\n- DBCompleteTable, DBCompleteProcedure, DBCompleteView would always recreate the object list.  If it has already been created, it should simply reuse what was available.  To force the recreation you add the bang to the command: DBCompleteTable!, DBCompleteProcedure!, DBCompleteView!.\r\n\r\n- Even with the checks it was possible for dbext to report:  E227: mapping already exists for ... when creating maps where the mapping already exists (Daniel Hahler).\r\n","3":"Posted by David Fishburn\r\n\r\nNew Features\r\n------------\r\n- Added new database type, the SAP HANA in memory database.\r\n\r\n- Added new option, ignore_variable_regex, which is used when parsing your statement for replacable input parameters (i.e. placeholders for prepared statements).  Certain variables need to be skipped (for example when running a CREATE PROCEDURE statement) to leave the logic inside the stored procedure intact.  This option allows the user finer control over the regex used to decide which SQL syntax should be skipped.\r\n\r\n- Added new option, statement_starts_line, which is used when deciding if the query should be parsed for input parameters.  Certain filetypes assume the statements can be embedded within strings (like in Java, PHP, Perl and so on).\r\n\r\n- When parsing PHP and Java files, leading and trailing quotes are stripped automatically when executing the query, which could lead to incorrect results.  First check if there is a leading quote.  If so, then only strip the corresponding closing quote.\r\n\r\n- Updated documentation describing the default regex for variable_def_regex.\r\n- Added new option g:dbext_map_prefix which defaults to <Leader>s, this allows you to customize the start of all the default maps (Daniel Hahler).\r\n                                                                                \r\nBug Fixes\r\n---------\r\n- The default value for variable_def_regex, did not properly escape the $, which lead to some query parameters being skipped when executing SQL.\r\n\r\n- It was impossible to search and replace input parameters within a query if the parameter was enclosed in single quotes.  The above new features were required to make this possible (Joshua Dennis).\r\n\r\n- DBCompleteTable, DBCompleteProcedure, DBCompleteView would always recreate the object list.  If it has already been created, it should simply reuse what was available.  To force the recreation you add the bang to the command: DBCompleteTable!, DBCompleteProcedure!, DBCompleteView!.\r\n\r\n- Even with the checks it was possible for dbext to report:  E227: mapping already exists for ... when creating maps where the mapping already exists (Daniel Hahler).\r\n","package":"dbext_1700.zip","4":"dbext_1700.zip","src_id":"18770","5":"18770","creation_date":"1349833110","6":"1349833110"},{"0":"356","vim_version":"7.0","1":"7.0","script_version":"16.0","2":"16.0","version_comment":"Posted by David Fishburn\r\n\r\nBug Fixes\r\n---------\r\n- For Oracle databases, the SQLPlus command had unmatched quotation marks which could lead to errors displayed by dbext indicating it could not open the file to execute the SQL (JustinF Zhang).\r\n","3":"Posted by David Fishburn\r\n\r\nBug Fixes\r\n---------\r\n- For Oracle databases, the SQLPlus command had unmatched quotation marks which could lead to errors displayed by dbext indicating it could not open the file to execute the SQL (JustinF Zhang).\r\n","package":"dbext_1600.zip","4":"dbext_1600.zip","src_id":"18117","5":"18117","creation_date":"1339468200","6":"1339468200"},{"0":"356","vim_version":"7.0","1":"7.0","script_version":"15.0","2":"15.0","version_comment":"Posted by David Fishburn\r\n\r\nNew Features\r\n---------\r\n- A new database confirguration parameter, g:dbext_default_DBTYPE_extra, is available to allow the user to customize command line parameters passed to the database binary used to execute the statement.  This can be overriden affecting all new connections via your .vimr.  Or for a specific buffer via connection profile or :DBPromptForBufferParameters (Ken Inglis, Michael Berkowski).\r\n                                                                                                                                                               \r\nBug Fixes\r\n---------\r\n- The dbext menu for List Variables displayed the wrong mapping.\r\n- For SQLite databases, if no database is specified now a warning message is displayed instead of an error message.\r\n","3":"Posted by David Fishburn\r\n\r\nNew Features\r\n---------\r\n- A new database confirguration parameter, g:dbext_default_DBTYPE_extra, is available to allow the user to customize command line parameters passed to the database binary used to execute the statement.  This can be overriden affecting all new connections via your .vimr.  Or for a specific buffer via connection profile or :DBPromptForBufferParameters (Ken Inglis, Michael Berkowski).\r\n                                                                                                                                                               \r\nBug Fixes\r\n---------\r\n- The dbext menu for List Variables displayed the wrong mapping.\r\n- For SQLite databases, if no database is specified now a warning message is displayed instead of an error message.\r\n","package":"dbext_1500.zip","4":"dbext_1500.zip","src_id":"17851","5":"17851","creation_date":"1335923020","6":"1335923020"},{"0":"356","vim_version":"7.0","1":"7.0","script_version":"14.0","2":"14.0","version_comment":"Posted by David Fishburn\r\n\r\nNew Features\r\n---------\r\n- Added support for using extended connection strings with Oracle and SQLPlus Fredrik Acosta).\r\n\r\n- Added a new buffer option to specify which filetype dbext should use when parsing the query.  If an existing language already works as you need you can tell dbext to use it via the modeline or DBSetOption (Albie Janse van Rensburg).\r\n\r\n- Added an example of a function I use to execute blocks of stored procedures using dbext's commands.\r\n\r\n- For PostgreSQL, dbext will check for the existance of a .pgpass file.  If not found, execution will abort and a warning message will be displayed.  By default $HOME\/.pgpass will be validated (Frank Schwach).\r\n                                                                               \r\nBug Fixes\r\n---------\r\n- When closing or deleting buffers it was possible to loose syntax, filetype and hidden settings (Alexey Radkov).\r\n\r\n- Parsing VisualBasic and Basic variables let to errors in DB_parseVB (Albie Janse van Rensburg).\r\n\r\n- Generating a column list for an ASA database left an extra , at the end of the list.  This also affected the SQLComplete plugin.\r\n","3":"Posted by David Fishburn\r\n\r\nNew Features\r\n---------\r\n- Added support for using extended connection strings with Oracle and SQLPlus Fredrik Acosta).\r\n\r\n- Added a new buffer option to specify which filetype dbext should use when parsing the query.  If an existing language already works as you need you can tell dbext to use it via the modeline or DBSetOption (Albie Janse van Rensburg).\r\n\r\n- Added an example of a function I use to execute blocks of stored procedures using dbext's commands.\r\n\r\n- For PostgreSQL, dbext will check for the existance of a .pgpass file.  If not found, execution will abort and a warning message will be displayed.  By default $HOME\/.pgpass will be validated (Frank Schwach).\r\n                                                                               \r\nBug Fixes\r\n---------\r\n- When closing or deleting buffers it was possible to loose syntax, filetype and hidden settings (Alexey Radkov).\r\n\r\n- Parsing VisualBasic and Basic variables let to errors in DB_parseVB (Albie Janse van Rensburg).\r\n\r\n- Generating a column list for an ASA database left an extra , at the end of the list.  This also affected the SQLComplete plugin.\r\n","package":"dbext_1400.zip","4":"dbext_1400.zip","src_id":"17722","5":"17722","creation_date":"1333595279","6":"1333595279"},{"0":"356","vim_version":"7.0","1":"7.0","script_version":"13.0","2":"13.0","version_comment":"Posted by David Fishburn\r\n\r\nNew Features\r\n---------\r\n- Added new command, DBDisconnectAll, for DBI\/ODBC.\r\n- DBDisconnect for DBI\/ODBC now can accept an optional parameter for the buffer you wish disconnected.\r\n- DBListConnections also includes the buffer filename in it's output to help associate the two more easily.\r\n- Updated the default variable_def_regex to include an alphabetic character after a \":\" for host variables to avoid false matches with time formats \"10:20\".\r\n- Improved the variable substitution to also check if a variable is preceeded by a single line comment character.  If so, ignore the match.\r\n        CALL myProc( sl_var1  -- p_var1\r\n                   , sl_var2  -- p_var2\r\n                   );   \r\n                                                                          \r\nBug Fixes\r\n---------\r\n- When clearing the results buffer the default register was updated.\r\n- Duplicate tag on MyProjectDir when running helptags (Simon Dambe).\r\n- Some of the variable substitution options Skip, Use Blank had off by one errors.\r\n","3":"Posted by David Fishburn\r\n\r\nNew Features\r\n---------\r\n- Added new command, DBDisconnectAll, for DBI\/ODBC.\r\n- DBDisconnect for DBI\/ODBC now can accept an optional parameter for the buffer you wish disconnected.\r\n- DBListConnections also includes the buffer filename in it's output to help associate the two more easily.\r\n- Updated the default variable_def_regex to include an alphabetic character after a \":\" for host variables to avoid false matches with time formats \"10:20\".\r\n- Improved the variable substitution to also check if a variable is preceeded by a single line comment character.  If so, ignore the match.\r\n        CALL myProc( sl_var1  -- p_var1\r\n                   , sl_var2  -- p_var2\r\n                   );   \r\n                                                                          \r\nBug Fixes\r\n---------\r\n- When clearing the results buffer the default register was updated.\r\n- Duplicate tag on MyProjectDir when running helptags (Simon Dambe).\r\n- Some of the variable substitution options Skip, Use Blank had off by one errors.\r\n","package":"dbext_1300.zip","4":"dbext_1300.zip","src_id":"15864","5":"15864","creation_date":"1307934490","6":"1307934490"},{"0":"356","vim_version":"7.0","1":"7.0","script_version":"12.00","2":"12.00","version_comment":"Posted by David Fishburn\r\n\r\nNew Features \r\n--------- \r\n- A number of changes around the Oracle formating instructions.  Support for packages when describing certain objects.  These changes were provided by Sergey Khorev. \r\n- Improved the parsing of Perl strings when prompting for variables. \r\n- Made some additional changes to the variable_def_regex for how you can specify it from Vim modelines and DBSetOption.  This makes it much more flexible. \r\n                                                                             \r\nBug Fixes \r\n--------- \r\n- If the word \"profile\" was used in a dbext profile name dbext would report the error: \"dbext: Profiles cannot be nested\" (Chris Cierpisz). \r\n- Corrected the regex used to find object owner names (Sergey Khorev). ","3":"Posted by David Fishburn\r\n\r\nNew Features \r\n--------- \r\n- A number of changes around the Oracle formating instructions.  Support for packages when describing certain objects.  These changes were provided by Sergey Khorev. \r\n- Improved the parsing of Perl strings when prompting for variables. \r\n- Made some additional changes to the variable_def_regex for how you can specify it from Vim modelines and DBSetOption.  This makes it much more flexible. \r\n                                                                             \r\nBug Fixes \r\n--------- \r\n- If the word \"profile\" was used in a dbext profile name dbext would report the error: \"dbext: Profiles cannot be nested\" (Chris Cierpisz). \r\n- Corrected the regex used to find object owner names (Sergey Khorev). ","package":"dbext_1200.zip","4":"dbext_1200.zip","src_id":"13339","5":"13339","creation_date":"1279222232","6":"1279222232"},{"0":"356","vim_version":"7.0","1":"7.0","script_version":"11.01","2":"11.01","version_comment":"Post by David Fishburn\r\nBug Fixes\r\n---------\r\n- If a large result set is retrieved, there is a significant performance delay which was introduced in 11.00.  This was related to the new g:dbext_rows_affected feature (Tocer).\r\n- Error E15: Invalid expression: b:dbext_sqlvar_mv[var] is reported if you are using saved variables and then modified the query with a new variable.  Now the saved variables are used for the known variables and you are prompted for the unknown.\r\n","3":"Post by David Fishburn\r\nBug Fixes\r\n---------\r\n- If a large result set is retrieved, there is a significant performance delay which was introduced in 11.00.  This was related to the new g:dbext_rows_affected feature (Tocer).\r\n- Error E15: Invalid expression: b:dbext_sqlvar_mv[var] is reported if you are using saved variables and then modified the query with a new variable.  Now the saved variables are used for the known variables and you are prompted for the unknown.\r\n","package":"dbext_1101.zip","4":"dbext_1101.zip","src_id":"11341","5":"11341","creation_date":"1252372347","6":"1252372347"},{"0":"356","vim_version":"7.0","1":"7.0","script_version":"11.00","2":"11.00","version_comment":"Posted by David Fishburn\r\n\r\nNew Features\r\n------------\r\n- When autoclose is enabled, a message is displayed indicating autoclose is enabled.  This message will now also include the number of rows affected by the last statement (if applicable).  This is available for all database interfaces which can provide this information.  Vim scripts or mappings have access to this value by referencing the g:dbext_rows_affected variable (Philippe Moravie).\r\n- The Select, Update, Delete, Alter and Drop commands will now complete table names.\r\n- Revamped the saved variables (see |dbext-tutorial-variables|).  dbext checks your queries and will prompt for variables (see |dbext-prompting|).  dbext uses regular expressions to determine which variables should be prompted.  To see how you can easily extend the regular expressions follow the tutorial.  This replaces the previous method which was too limiting.  The new technique uses Vim's standard regular expressions.  This introduces the variable_def_regex dbext option and deprecates the variable_def dbext option.\r\n- With the introduction of saved variables, you are now prompted during SQL execution to determine whether the previously saved variables should be substituted.\r\n                                                                              \r\nBug Fixes\r\n---------\r\n- If you re-sourced plugin\/dbext.vim you would receive the following error: E227: mapping already exists for <Leader>sas\r\n- Errors were reported about undefined variable, dbext_sqlvar_temp_mv,  if executing a SQL statement directly from a filetype which was not SQL (i.e. PHP, Java, csharp, ...).\r\n- If saved variables were in use, it was possible for dbext to used the replaced variables without the user knowing.  For example stored procedures could be created with the replaced strings instead of the variables.\r\n","3":"Posted by David Fishburn\r\n\r\nNew Features\r\n------------\r\n- When autoclose is enabled, a message is displayed indicating autoclose is enabled.  This message will now also include the number of rows affected by the last statement (if applicable).  This is available for all database interfaces which can provide this information.  Vim scripts or mappings have access to this value by referencing the g:dbext_rows_affected variable (Philippe Moravie).\r\n- The Select, Update, Delete, Alter and Drop commands will now complete table names.\r\n- Revamped the saved variables (see |dbext-tutorial-variables|).  dbext checks your queries and will prompt for variables (see |dbext-prompting|).  dbext uses regular expressions to determine which variables should be prompted.  To see how you can easily extend the regular expressions follow the tutorial.  This replaces the previous method which was too limiting.  The new technique uses Vim's standard regular expressions.  This introduces the variable_def_regex dbext option and deprecates the variable_def dbext option.\r\n- With the introduction of saved variables, you are now prompted during SQL execution to determine whether the previously saved variables should be substituted.\r\n                                                                              \r\nBug Fixes\r\n---------\r\n- If you re-sourced plugin\/dbext.vim you would receive the following error: E227: mapping already exists for <Leader>sas\r\n- Errors were reported about undefined variable, dbext_sqlvar_temp_mv,  if executing a SQL statement directly from a filetype which was not SQL (i.e. PHP, Java, csharp, ...).\r\n- If saved variables were in use, it was possible for dbext to used the replaced variables without the user knowing.  For example stored procedures could be created with the replaced strings instead of the variables.\r\n","package":"dbext_1100.zip","4":"dbext_1100.zip","src_id":"11239","5":"11239","creation_date":"1251056157","6":"1251056157"},{"0":"356","vim_version":"7.0","1":"7.0","script_version":"10.00","2":"10.00","version_comment":"Posted by David Fishburn\r\n\r\nNew Features\r\n------------\r\n- Added new database support for SQL Anywhere UltraLite (11.x).\r\n- Added new database support for Firebird (2.x).\r\n- Added \"@@variable\" style to the list of bypassed variable names along with IN, OUT, INOUT and DECLARE.\r\n- When listing stored variables, you can now remove multiple lines using visual mode.\r\n- When closing the result window (using \"q\" or DBResultsClose) you are intentionally returned to the buffer which opened the window instead of allowing Vim to choose which window.\r\n                                                                            \r\nBug Fixes\r\n---------\r\n- The version 9.00 release of dbext broke modeline support.\r\n- When listing variables the following error could be reported: E121: Undefined variable\r\n- It was not possible to retrieve more than 500 characters from a character or binary column in the database when using DBI or ODBC.  Adding driver_parms=LongReadLen=4096 now works correctly.  You can also change this after you are connected to the database using DBSetOption LongReadLen=4096.  Running DBListConnections will display the current setting for each database connection currently open.\r\n","3":"Posted by David Fishburn\r\n\r\nNew Features\r\n------------\r\n- Added new database support for SQL Anywhere UltraLite (11.x).\r\n- Added new database support for Firebird (2.x).\r\n- Added \"@@variable\" style to the list of bypassed variable names along with IN, OUT, INOUT and DECLARE.\r\n- When listing stored variables, you can now remove multiple lines using visual mode.\r\n- When closing the result window (using \"q\" or DBResultsClose) you are intentionally returned to the buffer which opened the window instead of allowing Vim to choose which window.\r\n                                                                            \r\nBug Fixes\r\n---------\r\n- The version 9.00 release of dbext broke modeline support.\r\n- When listing variables the following error could be reported: E121: Undefined variable\r\n- It was not possible to retrieve more than 500 characters from a character or binary column in the database when using DBI or ODBC.  Adding driver_parms=LongReadLen=4096 now works correctly.  You can also change this after you are connected to the database using DBSetOption LongReadLen=4096.  Running DBListConnections will display the current setting for each database connection currently open.\r\n","package":"dbext_1000.zip","4":"dbext_1000.zip","src_id":"10209","5":"10209","creation_date":"1237069070","6":"1237069070"},{"0":"356","vim_version":"7.0","1":"7.0","script_version":"9.0","2":"9.0","version_comment":"Posted by David Fishburn\r\nNew Features\r\n------------\r\n- Added the ability to set and store SQL variables for each buffer.  This will reduce prompting for statements which are often re-used.  Added support for listing and deleting SQL variables.   Initial prototype by Garrison Yu.\r\n- Added option, g:dbext_default_variable_remember, to control whether SQL variables should be stored when prompted.\r\n- Improved the parsing of SQL statements to account for procedural language.  If a IN, OUT, INOUT or DECLARE statement is found prior to the use of the variable, it is stored for later use.  When the variable is encountered, if the declaration was found we skip prompting for it's value.  This should reduce the number of prompts you receive when executing SQL (i.e. Functions, Procedures, Events, Packages and so on depending on the naming convention you use for your variables.\r\n- Updated the tutorial and added more links to different sections see |dbext-tutorial-variable|\r\n- Added VB filetype support (Garrison Yu).\r\n- Added escaping to allow specifying an new Oracle URL syntax for server connection parameters (Anton Sharonov).\r\n- Renamed DBCloseResults, DBOpenResults, DBRefreshResult, DBToggleResultsResize to DBResultsClose, DBResultsOpen, DBResultsRefresh, DBResultsToggleResize to be more consistent.\r\n                                                                          \r\nBug Fixes\r\n---------\r\n- You are often repeatedly prompted for connection information.  This change reduces the number and allows you to cancel out of the prompt dialogs.\r\n- Added an unconditional quit command to exit out of Oracle's SQLPlus (Anton Sharonov).\r\n","3":"Posted by David Fishburn\r\nNew Features\r\n------------\r\n- Added the ability to set and store SQL variables for each buffer.  This will reduce prompting for statements which are often re-used.  Added support for listing and deleting SQL variables.   Initial prototype by Garrison Yu.\r\n- Added option, g:dbext_default_variable_remember, to control whether SQL variables should be stored when prompted.\r\n- Improved the parsing of SQL statements to account for procedural language.  If a IN, OUT, INOUT or DECLARE statement is found prior to the use of the variable, it is stored for later use.  When the variable is encountered, if the declaration was found we skip prompting for it's value.  This should reduce the number of prompts you receive when executing SQL (i.e. Functions, Procedures, Events, Packages and so on depending on the naming convention you use for your variables.\r\n- Updated the tutorial and added more links to different sections see |dbext-tutorial-variable|\r\n- Added VB filetype support (Garrison Yu).\r\n- Added escaping to allow specifying an new Oracle URL syntax for server connection parameters (Anton Sharonov).\r\n- Renamed DBCloseResults, DBOpenResults, DBRefreshResult, DBToggleResultsResize to DBResultsClose, DBResultsOpen, DBResultsRefresh, DBResultsToggleResize to be more consistent.\r\n                                                                          \r\nBug Fixes\r\n---------\r\n- You are often repeatedly prompted for connection information.  This change reduces the number and allows you to cancel out of the prompt dialogs.\r\n- Added an unconditional quit command to exit out of Oracle's SQLPlus (Anton Sharonov).\r\n","package":"dbext_900.zip","4":"dbext_900.zip","src_id":"9794","5":"9794","creation_date":"1231617857","6":"1231617857"},{"0":"356","vim_version":"7.0","1":"7.0","script_version":"8.00","2":"8.00","version_comment":"Posted by David Fishburn\r\nNew Features\r\n------------\r\n- When defining a profile or running DBPromptForBufferParameters, you can now optionally specify a file containing commands you want to execute against the database when you first connect (James Horine).\r\n- A new global variable, g:dbext_default_login_script_dir allows you to override the 2 default directories which are searched for these files.\r\n- The dbext tutorial has been updated to demonstrate the login_script.\r\n- Doc update demonstrating the use of integrated logins (Daren Thomas).\r\n- Added a new user defined autocommand dbextPreConnection which is triggered prior to dbext connecting to the database.  This allows you to customize settings based on your buffer and environment (Tim Pope).\r\n                                                                         \r\nBug Fixes\r\n---------\r\n- Setting LongReadLen for DBI and ODBC connections did not work.\r\n","3":"Posted by David Fishburn\r\nNew Features\r\n------------\r\n- When defining a profile or running DBPromptForBufferParameters, you can now optionally specify a file containing commands you want to execute against the database when you first connect (James Horine).\r\n- A new global variable, g:dbext_default_login_script_dir allows you to override the 2 default directories which are searched for these files.\r\n- The dbext tutorial has been updated to demonstrate the login_script.\r\n- Doc update demonstrating the use of integrated logins (Daren Thomas).\r\n- Added a new user defined autocommand dbextPreConnection which is triggered prior to dbext connecting to the database.  This allows you to customize settings based on your buffer and environment (Tim Pope).\r\n                                                                         \r\nBug Fixes\r\n---------\r\n- Setting LongReadLen for DBI and ODBC connections did not work.\r\n","package":"dbext_800.zip","4":"dbext_800.zip","src_id":"9416","5":"9416","creation_date":"1225333479","6":"1225333479"},{"0":"356","vim_version":"7.0","1":"7.0","script_version":"7.00","2":"7.00","version_comment":"Posted by David Fishburn.\r\nNew Features\r\n------------\r\n- Large change between how the error handling between DBI and ODBC  connections were reported and displayed.\r\n- Non-printable characters are now dealt with for DBI and ODBC connections.\r\n                                                                      \r\nBug Fixes\r\n---------\r\n- Using ODBC to connect to SQL Server, dbext did not handle informational messages appropriately leading to \"not connected\" messages (Albie Janse van Rensburg).\r\n- When executing SQL if you were prompted for a variable replacement and cancelled the query the dbext history window was displayed instead of returning to the buffer.\r\n","3":"Posted by David Fishburn.\r\nNew Features\r\n------------\r\n- Large change between how the error handling between DBI and ODBC  connections were reported and displayed.\r\n- Non-printable characters are now dealt with for DBI and ODBC connections.\r\n                                                                      \r\nBug Fixes\r\n---------\r\n- Using ODBC to connect to SQL Server, dbext did not handle informational messages appropriately leading to \"not connected\" messages (Albie Janse van Rensburg).\r\n- When executing SQL if you were prompted for a variable replacement and cancelled the query the dbext history window was displayed instead of returning to the buffer.\r\n","package":"dbext_700.zip","4":"dbext_700.zip","src_id":"9261","5":"9261","creation_date":"1222007518","6":"1222007518"},{"0":"356","vim_version":"7.0","1":"7.0","script_version":"6.20","2":"6.20","version_comment":"Posted by David Fishburn\r\nBug Fixes\r\n---------\r\n- Changed the DB2 TOP X syntax (DBExecSQLTopX).\r\n- Changed the query used to retrieve the current line for DBExecSQLUnderCursor when no text is selected (Sergey Alekhin).\r\n- When parsing a SQL statement for host variables it was possible to miss excluding the INTO clause correctly (Sergey Alekhin).\r\n","3":"Posted by David Fishburn\r\nBug Fixes\r\n---------\r\n- Changed the DB2 TOP X syntax (DBExecSQLTopX).\r\n- Changed the query used to retrieve the current line for DBExecSQLUnderCursor when no text is selected (Sergey Alekhin).\r\n- When parsing a SQL statement for host variables it was possible to miss excluding the INTO clause correctly (Sergey Alekhin).\r\n","package":"dbext_620.zip","4":"dbext_620.zip","src_id":"9099","5":"9099","creation_date":"1218313754","6":"1218313754"},{"0":"356","vim_version":"7.0","1":"7.0","script_version":"6.10","2":"6.10","version_comment":"Posted by David Fishburn\r\nNew Features\r\n------------\r\n- The result window inherits the connection parameters of the buffer which last executed SQL (Antony Scriven).  For example, if you retrieve a list of tables, you may want to describe a table or generate a list of columns for one of the tables.  Using the usual maps will generate the result you need without prompting for connection parameters.  This is especially useful if you have more than 1 buffer and each buffer connects to different databases.\r\n- Added the ability to choose where to put the Result window.  When the window is split you can choose vertical or horizontal, bottom or top, and choose the the width of the window for horizontal switches (Clinton Jones).\r\n- Modified DBExecSQLUnderCursor to select all text until end of line if no valid command terminator is found rather than just one letter (David Venus).\r\n- DBGetOption displays the output from :ver for debugging.\r\n                                                                 \r\nBug Fixes\r\n---------\r\n- Tutorial update (Nico Coetzee).\r\n- Tutorial update (Clinton Jones).\r\n- DBGetOption reported an exception E730: using List as a String.\r\n","3":"Posted by David Fishburn\r\nNew Features\r\n------------\r\n- The result window inherits the connection parameters of the buffer which last executed SQL (Antony Scriven).  For example, if you retrieve a list of tables, you may want to describe a table or generate a list of columns for one of the tables.  Using the usual maps will generate the result you need without prompting for connection parameters.  This is especially useful if you have more than 1 buffer and each buffer connects to different databases.\r\n- Added the ability to choose where to put the Result window.  When the window is split you can choose vertical or horizontal, bottom or top, and choose the the width of the window for horizontal switches (Clinton Jones).\r\n- Modified DBExecSQLUnderCursor to select all text until end of line if no valid command terminator is found rather than just one letter (David Venus).\r\n- DBGetOption displays the output from :ver for debugging.\r\n                                                                 \r\nBug Fixes\r\n---------\r\n- Tutorial update (Nico Coetzee).\r\n- Tutorial update (Clinton Jones).\r\n- DBGetOption reported an exception E730: using List as a String.\r\n","package":"dbext_610.zip","4":"dbext_610.zip","src_id":"8782","5":"8782","creation_date":"1213119232","6":"1213119232"},{"0":"356","vim_version":"7.0","1":"7.0","script_version":"6.01","2":"6.01","version_comment":"Posted by David Fishburn\r\nBug Fixes\r\n---------\r\n- On dbext startup an error was reported indicating mapleader was not defined (Matt).\r\n","3":"Posted by David Fishburn\r\nBug Fixes\r\n---------\r\n- On dbext startup an error was reported indicating mapleader was not defined (Matt).\r\n","package":"dbext_601.zip","4":"dbext_601.zip","src_id":"8621","5":"8621","creation_date":"1209500252","6":"1209500252"},{"0":"356","vim_version":"6.0","1":"6.0","script_version":"6.00","2":"6.00","version_comment":"Posted by David Fishburn\r\n\r\nNew Features\r\n------------\r\n- dbext now supports table and column names which can contain spaces (Antony Scriven).  There is a corresponding change to sqlcomplete.vim to support this.\r\n- Added an autoclose option.  If you execute SQL which does not return a result set you can choose to have the dbext results window automatically close (unless of course there was an error).  See the autoclose option for more details.\r\n- Added the map shortcuts to each of menu items under the dbext menu so that users can learn them more easily (Alexander Langer).\r\n- Using the menu_mode option you can control if and where the dbext menu is created (Marty Grenfell).  See the menu_mode option for more details.\r\n- For MySQL, added -t as part of the default command line parameters setting.  This will properly format the data into tabs or spaces to make it more readable (Luke Cordingley).\r\n- A message is displayed indicating the time a SQL command began executing.  The result window also contains the time the SQL finished executing.\r\n- DBI or ODBC can now fetch BLOB columns from the database.  By default these are truncated at 500 characters, but that can be changed by issuing: DBSetOption driver_parms=LongReadLen=4096\r\n\r\nBug Fixes\r\n---------\r\n- If a database column had an emdedded double quote this would be displayed as \\\" in the dbext result window (Jean-Christophe Clavier).\r\n- When loading the plugin, it will now check to ensure the map does not already exist before attempting to create it.  This will prevent errors when mappings clash (Antony Scriven).\r\n- If you prompt for connection parameters using the DBI or ODBC types we need to disconnect any existing connections or the existing connection will continue to be used.\r\n- In some cases when using DBI or ODBC an error was not reported and only a blank result set was returned.  Now the database error is reported back to the user.\r\n- Data retrieved via DBI or ODBC which contained a backslash were not escaped properly and could disappear.\r\n","3":"Posted by David Fishburn\r\n\r\nNew Features\r\n------------\r\n- dbext now supports table and column names which can contain spaces (Antony Scriven).  There is a corresponding change to sqlcomplete.vim to support this.\r\n- Added an autoclose option.  If you execute SQL which does not return a result set you can choose to have the dbext results window automatically close (unless of course there was an error).  See the autoclose option for more details.\r\n- Added the map shortcuts to each of menu items under the dbext menu so that users can learn them more easily (Alexander Langer).\r\n- Using the menu_mode option you can control if and where the dbext menu is created (Marty Grenfell).  See the menu_mode option for more details.\r\n- For MySQL, added -t as part of the default command line parameters setting.  This will properly format the data into tabs or spaces to make it more readable (Luke Cordingley).\r\n- A message is displayed indicating the time a SQL command began executing.  The result window also contains the time the SQL finished executing.\r\n- DBI or ODBC can now fetch BLOB columns from the database.  By default these are truncated at 500 characters, but that can be changed by issuing: DBSetOption driver_parms=LongReadLen=4096\r\n\r\nBug Fixes\r\n---------\r\n- If a database column had an emdedded double quote this would be displayed as \\\" in the dbext result window (Jean-Christophe Clavier).\r\n- When loading the plugin, it will now check to ensure the map does not already exist before attempting to create it.  This will prevent errors when mappings clash (Antony Scriven).\r\n- If you prompt for connection parameters using the DBI or ODBC types we need to disconnect any existing connections or the existing connection will continue to be used.\r\n- In some cases when using DBI or ODBC an error was not reported and only a blank result set was returned.  Now the database error is reported back to the user.\r\n- Data retrieved via DBI or ODBC which contained a backslash were not escaped properly and could disappear.\r\n","package":"dbext_600.zip","4":"dbext_600.zip","src_id":"8615","5":"8615","creation_date":"1209400566","6":"1209400566"},{"0":"356","vim_version":"7.0","1":"7.0","script_version":"5.20","2":"5.20","version_comment":"Posted by David Fishburn.\r\nNew Features\r\n------------\r\n- When using DBI or DBI::ODBC null fields are now displayed as NULL instead of empty spaces (now you can distinguish between them).\r\n- When using DBI or DBI::ODBC you can specify the column separator \r\n:let g:dbext_default_dbi_column_delimiter=\"\\t\" (Jean-Christophe Clavier)\r\n- When using DBI or DBI::ODBC and you use a vertical orientation for the result set, if there are any embedded newline characters in your data this will be displayed and shifted to align with the column above.  Prior to this all newlines were stripped from the output when printing to preserve standard horizontal output (Jean-Christophe Clavier).\r\n","3":"Posted by David Fishburn.\r\nNew Features\r\n------------\r\n- When using DBI or DBI::ODBC null fields are now displayed as NULL instead of empty spaces (now you can distinguish between them).\r\n- When using DBI or DBI::ODBC you can specify the column separator \r\n:let g:dbext_default_dbi_column_delimiter=\"\\t\" (Jean-Christophe Clavier)\r\n- When using DBI or DBI::ODBC and you use a vertical orientation for the result set, if there are any embedded newline characters in your data this will be displayed and shifted to align with the column above.  Prior to this all newlines were stripped from the output when printing to preserve standard horizontal output (Jean-Christophe Clavier).\r\n","package":"dbext_520.zip","4":"dbext_520.zip","src_id":"7678","5":"7678","creation_date":"1189887238","6":"1189887238"},{"0":"356","vim_version":"7.0","1":"7.0","script_version":"5.11","2":"5.11","version_comment":"Posted by David Fishburn. \r\nNew Features ------------ \r\n- Added support for Oracle Rdb on an Open VMS Node.  \r\nFor vim on Open VMS look at http:\/\/www.polarhome.com\/vim\/.\r\nFor Open VMS http:\/\/h71000.www7.hp.com\/openvms\/. \r\nDevelopment of Rdb support by Andi Stern\r\n","3":"Posted by David Fishburn. \r\nNew Features ------------ \r\n- Added support for Oracle Rdb on an Open VMS Node.  \r\nFor vim on Open VMS look at http:\/\/www.polarhome.com\/vim\/.\r\nFor Open VMS http:\/\/h71000.www7.hp.com\/openvms\/. \r\nDevelopment of Rdb support by Andi Stern\r\n","package":"dbext_511.zip","4":"dbext_511.zip","src_id":"7643","5":"7643","creation_date":"1189406344","6":"1189406344"},{"0":"356","vim_version":"7.0","1":"7.0","script_version":"5.06","2":"5.06","version_comment":"Posted by David Fishburn. \r\nNew Features\r\n------------\r\n- Added Perl's DBI and DBI::ODBC support.  This opens additional database support without having to adjust scripts.  You must have a Perl enabled Vim (:echo has('perl')).  Using the DBI layer offers some advantages over using the native binary tools:\r\n       - Transaction support which allows you to maintain a transaction during your editing session and either commit or rollback and changes.  This is not possible without using the DBI layer.\r\n       - Speed improvements, since the database connection is maintained, the there is less overhead per command.\r\nHuge thanks to Jean-Christophe Clavier and Albie Janse van Rensburg for their beta testing and suggestions.\r\n\r\n- New commands are available to select only a few rows instead of an entire result set.  In most databases this is referred to as TOP X.  DBExecSQLTopX, DBExecVisualSQLTopX, DBExecSQLUnderCursorTopX have been added plus associated mappings (Albie Janse van Rensburg).\r\n- Made Cygwin detection a bit easier using the shellslash option (Steve Gibson)\r\n                                                                                \r\nBug Fixes\r\n------------\r\n- SQL Server support had issues with the queries when running DBCompleteTable, DBCompleteProcedure, DBCompleteView which also affected the sqlcomplete.vim plugin included with Vim7 (Albie Janse van Rensburg).\r\n- Oracle reported \"rows will be truncated\", added \"set linesize 10000\" to the Oracle headers (Stuart Brock)\r\n- When prompting for connection parameters if you choose a profile of \"0\" which is no profile, you had to re-run the wizard to prompt for the rest of the parameters, now the wizard continues as expected.\r\n","3":"Posted by David Fishburn. \r\nNew Features\r\n------------\r\n- Added Perl's DBI and DBI::ODBC support.  This opens additional database support without having to adjust scripts.  You must have a Perl enabled Vim (:echo has('perl')).  Using the DBI layer offers some advantages over using the native binary tools:\r\n       - Transaction support which allows you to maintain a transaction during your editing session and either commit or rollback and changes.  This is not possible without using the DBI layer.\r\n       - Speed improvements, since the database connection is maintained, the there is less overhead per command.\r\nHuge thanks to Jean-Christophe Clavier and Albie Janse van Rensburg for their beta testing and suggestions.\r\n\r\n- New commands are available to select only a few rows instead of an entire result set.  In most databases this is referred to as TOP X.  DBExecSQLTopX, DBExecVisualSQLTopX, DBExecSQLUnderCursorTopX have been added plus associated mappings (Albie Janse van Rensburg).\r\n- Made Cygwin detection a bit easier using the shellslash option (Steve Gibson)\r\n                                                                                \r\nBug Fixes\r\n------------\r\n- SQL Server support had issues with the queries when running DBCompleteTable, DBCompleteProcedure, DBCompleteView which also affected the sqlcomplete.vim plugin included with Vim7 (Albie Janse van Rensburg).\r\n- Oracle reported \"rows will be truncated\", added \"set linesize 10000\" to the Oracle headers (Stuart Brock)\r\n- When prompting for connection parameters if you choose a profile of \"0\" which is no profile, you had to re-run the wizard to prompt for the rest of the parameters, now the wizard continues as expected.\r\n","package":"dbext_506.zip","4":"dbext_506.zip","src_id":"7615","5":"7615","creation_date":"1188801330","6":"1188801330"},{"0":"356","vim_version":"7.0","1":"7.0","script_version":"4.20","2":"4.20","version_comment":"Posted by David Fishburn.\r\nNew Features\r\n- Improved support for Cygwin.  If you are using a Cygwin compiled Vim (on   Windows) and are accessing Windows compiled binaries (i.e. sqlplus.exe) the binary will complain since it does not understand Unix path names.  Added the option g:dbext_default_use_win32_filenames which allows you to indicate the binaries must use translated Windows paths instead. (Richard)\r\n- DBGetOption displays more information.\r\n                                                                               \r\nBug Fixes\r\n- SQL Server support had issues with the queries when running DBCompleteTable, DBCompleteProcedure, DBCompleteView which also affected the sqlcomplete.vim plugin included with Vim7 (Albie Janse van Rensburg).\r\n","3":"Posted by David Fishburn.\r\nNew Features\r\n- Improved support for Cygwin.  If you are using a Cygwin compiled Vim (on   Windows) and are accessing Windows compiled binaries (i.e. sqlplus.exe) the binary will complain since it does not understand Unix path names.  Added the option g:dbext_default_use_win32_filenames which allows you to indicate the binaries must use translated Windows paths instead. (Richard)\r\n- DBGetOption displays more information.\r\n                                                                               \r\nBug Fixes\r\n- SQL Server support had issues with the queries when running DBCompleteTable, DBCompleteProcedure, DBCompleteView which also affected the sqlcomplete.vim plugin included with Vim7 (Albie Janse van Rensburg).\r\n","package":"dbext_420.zip","4":"dbext_420.zip","src_id":"6527","5":"6527","creation_date":"1166557547","6":"1166557547"},{"0":"356","vim_version":"7.0","1":"7.0","script_version":"4.10","2":"4.10","version_comment":"Posted by David Fishburn.\r\nNew Features\r\n------------\r\n- Updated DBGetOption to additionally display a list of all database profiles and their types.  All dbext options that have been overriden via the vimrc are also displayed.\r\n                                                                          \r\nBug Fixes\r\n------------\r\n- db2 support had issues with the queries when running DBCompleteTable, DBCompleteProcedure, DBCompleteView which also affected the sqlcomplete.vim plugin included with Vim7 (Peter Princz).\r\n- The documentation was still indicating there was a plugin dependency which has been removed with Vim7.\r\n","3":"Posted by David Fishburn.\r\nNew Features\r\n------------\r\n- Updated DBGetOption to additionally display a list of all database profiles and their types.  All dbext options that have been overriden via the vimrc are also displayed.\r\n                                                                          \r\nBug Fixes\r\n------------\r\n- db2 support had issues with the queries when running DBCompleteTable, DBCompleteProcedure, DBCompleteView which also affected the sqlcomplete.vim plugin included with Vim7 (Peter Princz).\r\n- The documentation was still indicating there was a plugin dependency which has been removed with Vim7.\r\n","package":"dbext_410.zip","4":"dbext_410.zip","src_id":"6499","5":"6499","creation_date":"1165297231","6":"1165297231"},{"0":"356","vim_version":"7.0","1":"7.0","script_version":"4.03","2":"4.03","version_comment":"Posted by David Fishburn.\r\nNew Features\r\n------------\r\n- dbext.vim now requires Vim7.\r\n- dbext.vim no longer has dependencies on other plugins by utilizing the new Vim7 features (Lists and Dictionaries).\r\n- When using the DBCompleteTable, DBCompleteProcedure, DBCompleteView commands errors are displayed instead of silently ignored.  This makes them more useful with the sqlComplete plugin (see |sql.txt|).\r\n- Added new option, dbext_default_MYSQL_version, for MySQL to indicate the version you using.\r\n- You can optionally define a function, DBextPostResult, in your .vimrc, this function will be called each time the result window is updated.  This function can be used to do anything, for example, syntax highlighting the result set in the result window.\r\n\r\nBug Fixes\r\n------------\r\n- Added version support with MySQL to control what SQL is sent for version 4 and 5 servers.\r\n","3":"Posted by David Fishburn.\r\nNew Features\r\n------------\r\n- dbext.vim now requires Vim7.\r\n- dbext.vim no longer has dependencies on other plugins by utilizing the new Vim7 features (Lists and Dictionaries).\r\n- When using the DBCompleteTable, DBCompleteProcedure, DBCompleteView commands errors are displayed instead of silently ignored.  This makes them more useful with the sqlComplete plugin (see |sql.txt|).\r\n- Added new option, dbext_default_MYSQL_version, for MySQL to indicate the version you using.\r\n- You can optionally define a function, DBextPostResult, in your .vimrc, this function will be called each time the result window is updated.  This function can be used to do anything, for example, syntax highlighting the result set in the result window.\r\n\r\nBug Fixes\r\n------------\r\n- Added version support with MySQL to control what SQL is sent for version 4 and 5 servers.\r\n","package":"dbext_400.zip","4":"dbext_400.zip","src_id":"6221","5":"6221","creation_date":"1159009571","6":"1159009571"},{"0":"356","vim_version":"6.0","1":"6.0","script_version":"3.50","2":"3.50","version_comment":"New Features\r\n------------\r\n - g:dbext_default_inputdialog_cancel_support = 0 will prevent inputdialog from providing a cancel option.  This works around a Vim7 bug.  dbext will automatically detect this and set the option the first time it is encountered.\r\n - Changed the order of some of the text in the dialog boxes to make them more readable when using the console version of Vim.\r\n - dbext can parse SQL statements and prompt the user to replace variables with values prior to sending the statement to the database to be executed.  This is useful for testing SQL which is embedded in your code without having to manually replace variables and string concatentation.  A new identifier (the until flag) allows you to specify the beginning of a string and what to prompt for until a finishing string.  This makes it more flexible for you to configure what you would like prompting for when looking for variables.\r\n\r\nBug Fixes\r\n------------\r\n - DBPromptForBufferParameters can report \"E180: Invalid complete value: -1\" if running the console version of Vim.  dbext will detect this problem and automatically set g:dbext_default_inputdialog_cancel_support = 0 to work around this Vim7 bug.\r\n\r\n","3":"New Features\r\n------------\r\n - g:dbext_default_inputdialog_cancel_support = 0 will prevent inputdialog from providing a cancel option.  This works around a Vim7 bug.  dbext will automatically detect this and set the option the first time it is encountered.\r\n - Changed the order of some of the text in the dialog boxes to make them more readable when using the console version of Vim.\r\n - dbext can parse SQL statements and prompt the user to replace variables with values prior to sending the statement to the database to be executed.  This is useful for testing SQL which is embedded in your code without having to manually replace variables and string concatentation.  A new identifier (the until flag) allows you to specify the beginning of a string and what to prompt for until a finishing string.  This makes it more flexible for you to configure what you would like prompting for when looking for variables.\r\n\r\nBug Fixes\r\n------------\r\n - DBPromptForBufferParameters can report \"E180: Invalid complete value: -1\" if running the console version of Vim.  dbext will detect this problem and automatically set g:dbext_default_inputdialog_cancel_support = 0 to work around this Vim7 bug.\r\n\r\n","package":"dbext_350.zip","4":"dbext_350.zip","src_id":"5843","5":"5843","creation_date":"1150779505","6":"1150779505"},{"0":"356","vim_version":"6.0","1":"6.0","script_version":"3.00","2":"3.00","version_comment":"New Features\r\n------------\r\n- dbext supports a history of previous commands.  The DBHistory command will display a numbered list of previous SQL statements.  Pressing <enter> or double clicking on one of the items will execute the statement.  The number of items in the list is configurable via your vimrc.  The history items are stored in a file, dbext_sql_history.txt.  The location of the file can also be controlled.\r\n- The 'refresh' feature added in version 2.30 has been updated to take advantage of the history feature.\r\n- The PHP parser has improved and can handle single or double quoted strings, string concatenation and host variables.  It will correctly strip the quotes, join the concatenated strings and prompt the user for host variables before executing the SQL statement.\r\n- Updated documentation for Vim 7 SQL code completion.\r\n- Table, procedure and view dictionaries include the owner name of the object.  This is on by default, but can be controlled via a new global option, dbext_default_dict_show_owner.  This has not been enabled for all databases it depends on whether the database supports this feature.  The autoload\\sqlcomplete.vim plugin takes advantage of this feature.\r\n- Added support for stored procedures \/ functions in MySQL 5.\r\n                                                                            \r\nBug Fixes\r\n------------\r\n- Updated the PHP parser to work with a more varied string quotes and string concatenation.\r\n- The \"extra\" feature did not add a leading space for MySQL.  Using the tabbed output required updates to the parsing of the output generated by MySQL.\r\n- Miscellaneous documentation updates.","3":"New Features\r\n------------\r\n- dbext supports a history of previous commands.  The DBHistory command will display a numbered list of previous SQL statements.  Pressing <enter> or double clicking on one of the items will execute the statement.  The number of items in the list is configurable via your vimrc.  The history items are stored in a file, dbext_sql_history.txt.  The location of the file can also be controlled.\r\n- The 'refresh' feature added in version 2.30 has been updated to take advantage of the history feature.\r\n- The PHP parser has improved and can handle single or double quoted strings, string concatenation and host variables.  It will correctly strip the quotes, join the concatenated strings and prompt the user for host variables before executing the SQL statement.\r\n- Updated documentation for Vim 7 SQL code completion.\r\n- Table, procedure and view dictionaries include the owner name of the object.  This is on by default, but can be controlled via a new global option, dbext_default_dict_show_owner.  This has not been enabled for all databases it depends on whether the database supports this feature.  The autoload\\sqlcomplete.vim plugin takes advantage of this feature.\r\n- Added support for stored procedures \/ functions in MySQL 5.\r\n                                                                            \r\nBug Fixes\r\n------------\r\n- Updated the PHP parser to work with a more varied string quotes and string concatenation.\r\n- The \"extra\" feature did not add a leading space for MySQL.  Using the tabbed output required updates to the parsing of the output generated by MySQL.\r\n- Miscellaneous documentation updates.","package":"dbext_300.zip","4":"dbext_300.zip","src_id":"5702","5":"5702","creation_date":"1147700006","6":"1147700006"},{"0":"356","vim_version":"6.0","1":"6.0","script_version":"2.30","2":"2.30","version_comment":"New Features\r\n ------------\r\n - The result window has a local buffer mapping 'R', which will 'refresh' the window.  This means it will re-run the previous statement which is useful if you are repeatedly checking something in the database.\r\n - SQL Anywhere (ASA) no longer relies on the jcatalogue tables to be installed in the database.  System views are used instead.\r\n - Support for MySQL 5.0 has been added, which includes stored procedures and views (as much as the beta allowed).\r\n - For Postgress SQL you can now optionally enter an owner name to filter by when showing list of objects (tables, procedures, views).\r\n\r\n Bug Fixes\r\n ------------\r\n - The alternate-file is no longer changed the first time the result buffer is opened.\r\n - Using DB2 with db2cmd incorrectly specified the command terminator with td, instead of -t.\r\n - On win32 platforms, if the bin_path has been specified for DB2, then add this to the system path since db2cmd relies on other batch files to operate correctly.\r\n - The connection string is displayed by both the Result buffer (first line) and the titlestring to the buffer (if enabled).  This was not correctly appending the user used to connect to the database.\r\n - When parsing Vim scripts we did not correctly remove a leading line continuation slash from the from of a query.","3":"New Features\r\n ------------\r\n - The result window has a local buffer mapping 'R', which will 'refresh' the window.  This means it will re-run the previous statement which is useful if you are repeatedly checking something in the database.\r\n - SQL Anywhere (ASA) no longer relies on the jcatalogue tables to be installed in the database.  System views are used instead.\r\n - Support for MySQL 5.0 has been added, which includes stored procedures and views (as much as the beta allowed).\r\n - For Postgress SQL you can now optionally enter an owner name to filter by when showing list of objects (tables, procedures, views).\r\n\r\n Bug Fixes\r\n ------------\r\n - The alternate-file is no longer changed the first time the result buffer is opened.\r\n - Using DB2 with db2cmd incorrectly specified the command terminator with td, instead of -t.\r\n - On win32 platforms, if the bin_path has been specified for DB2, then add this to the system path since db2cmd relies on other batch files to operate correctly.\r\n - The connection string is displayed by both the Result buffer (first line) and the titlestring to the buffer (if enabled).  This was not correctly appending the user used to connect to the database.\r\n - When parsing Vim scripts we did not correctly remove a leading line continuation slash from the from of a query.","package":"dbext_230.zip","4":"dbext_230.zip","src_id":"4576","5":"4576","creation_date":"1126619006","6":"1126619006"},{"0":"356","vim_version":"6.0","1":"6.0","script_version":"2.20","2":"2.20","version_comment":" New Features\r\n ------------\r\n - Added new connection parameter called \"extra\", you can place any\r\nadditional command line parameters in this option.\r\n - DBGetOption displays all options including the dbext version.\r\n - Better support for command terminators that have newline or special\r\ncharacters in them.  For example ASE\/SQLSRV use \"\\ngo\\n\", now the command\r\nDBExecSQLUnderCursor will correctly find the statement.\r\n - Use_tbl_alias defaults to \"ask\", instead of \"default on\".\r\n - For most supported databases, when displaying the Table \/ Procedure \/\r\nView List, you can now enter a partial string \"DBA.\", and if a . is included\r\nit will only display objects created \/ owned by that userid.\r\n - DBExecSQLUnderCursor would sometimes stop in the middle of a query if the\r\ncommand terminator was included (inside a quoted string), now it ensures\r\nthere is no text following the terminator.\r\n - The result window also includes the error code returned by the binary\r\nused to execute the command.  This can be useful for debugging.\r\n - The first line of the result window includes a line showing the\r\nconnection information, if you have many buffers open, it can be difficult\r\nto determine which database you are executing commands against.  A glance at\r\nthis line will tell you immediately.\r\n - g:dbext_default_always_prompt_for_variables = 0 will prevent you from\r\nbeing prompted for substitution parameters.  Setting this value to 1 will\r\nalways prompt the user.\r\n - You can now abort the execution of a statement if you are prompted for\r\nsubstitution parameters.\r\n - If you are prompted for parameters, if you choose \"Stop Prompting\" the\r\ncommand will be executed immediate.  If \"Never Prompt\" is chosen, no further\r\nprompting will occur for this buffer.\r\n\r\n Bug Fixes\r\n ---------\r\n - SQLSRV did not have a default command terminator, now it is \"\\ngo\\n\".\r\n - Changed the Oracle command terminator to \";\", and the routine that\r\nexecutes the statements automatically adds the \"\\nquit;\\n\" so that   sqlplus\r\nwill complete.\r\n - Spaces were not correctly removed from column lists in all cases, this\r\nshowed up as an issue with the SQL Intellisense plugin.\r\n - When executing SELECT statements the INTO clause (if present) is removed\r\nso the results are displayed in the result window.  Refined the removal of\r\nthe INTO clause to ensure it does not interfer with an INSERT or MERGE\r\nstatement.","3":" New Features\r\n ------------\r\n - Added new connection parameter called \"extra\", you can place any\r\nadditional command line parameters in this option.\r\n - DBGetOption displays all options including the dbext version.\r\n - Better support for command terminators that have newline or special\r\ncharacters in them.  For example ASE\/SQLSRV use \"\\ngo\\n\", now the command\r\nDBExecSQLUnderCursor will correctly find the statement.\r\n - Use_tbl_alias defaults to \"ask\", instead of \"default on\".\r\n - For most supported databases, when displaying the Table \/ Procedure \/\r\nView List, you can now enter a partial string \"DBA.\", and if a . is included\r\nit will only display objects created \/ owned by that userid.\r\n - DBExecSQLUnderCursor would sometimes stop in the middle of a query if the\r\ncommand terminator was included (inside a quoted string), now it ensures\r\nthere is no text following the terminator.\r\n - The result window also includes the error code returned by the binary\r\nused to execute the command.  This can be useful for debugging.\r\n - The first line of the result window includes a line showing the\r\nconnection information, if you have many buffers open, it can be difficult\r\nto determine which database you are executing commands against.  A glance at\r\nthis line will tell you immediately.\r\n - g:dbext_default_always_prompt_for_variables = 0 will prevent you from\r\nbeing prompted for substitution parameters.  Setting this value to 1 will\r\nalways prompt the user.\r\n - You can now abort the execution of a statement if you are prompted for\r\nsubstitution parameters.\r\n - If you are prompted for parameters, if you choose \"Stop Prompting\" the\r\ncommand will be executed immediate.  If \"Never Prompt\" is chosen, no further\r\nprompting will occur for this buffer.\r\n\r\n Bug Fixes\r\n ---------\r\n - SQLSRV did not have a default command terminator, now it is \"\\ngo\\n\".\r\n - Changed the Oracle command terminator to \";\", and the routine that\r\nexecutes the statements automatically adds the \"\\nquit;\\n\" so that   sqlplus\r\nwill complete.\r\n - Spaces were not correctly removed from column lists in all cases, this\r\nshowed up as an issue with the SQL Intellisense plugin.\r\n - When executing SELECT statements the INTO clause (if present) is removed\r\nso the results are displayed in the result window.  Refined the removal of\r\nthe INTO clause to ensure it does not interfer with an INSERT or MERGE\r\nstatement.","package":"dbext_220.zip","4":"dbext_220.zip","src_id":"3999","5":"3999","creation_date":"1110496830","6":"1110496830"},{"0":"356","vim_version":"6.0","1":"6.0","script_version":"2.11","2":"2.11","version_comment":"Bug fix: On some platforms the temporary file created to execute SQL\r\nstatements must end in \".sql\".  Corrected this for all databases.","3":"Bug fix: On some platforms the temporary file created to execute SQL\r\nstatements must end in \".sql\".  Corrected this for all databases.","package":"dbext_211.zip","4":"dbext_211.zip","src_id":"3483","5":"3483","creation_date":"1096025400","6":"1096025400"},{"0":"356","vim_version":"6.0","1":"6.0","script_version":"2.10","2":"2.10","version_comment":"New Features\r\n- Support for the SQLite database has been added (thanks to Ron Aaron).","3":"New Features\r\n- Support for the SQLite database has been added (thanks to Ron Aaron).","package":"dbext_210.zip","4":"dbext_210.zip","src_id":"3454","5":"3454","creation_date":"1095243144","6":"1095243144"},{"0":"356","vim_version":"6.0","1":"6.0","script_version":"2.01","2":"2.01","version_comment":"New Features\r\n- Tutorial - Based on feedback from users, created a step by step tutorial.\r\nAll users should try the tutorial to learn how to use the various features\r\nof the plugin.\r\n- DBGetOption - without parameters populates the Result window with all\r\noptions.\r\n- DBGetOption and DBSetOption support command line completion for the\r\nvarious options (DBGetOption d<tab>, will cycle through all options\r\nbeginning with \"d\").\r\n- New option, replace_title, changes the title of the buffer to show\r\nconnection information which is useful if you are using  a scratch buffer to\r\ntest SQL.\r\n- IntegratedLogin support for Windows users.\r\n- DBExecRangeSQL - useful for custom mappings, and executing commands\r\nwithout visual mode.\r\n- New maps <Leader>sea - sql - execute - all (lines in the file),\r\n<Leader>sel - sql - execute - line (the current line)\r\n- New filetype support - jproperties\r\n\r\n\r\nBug Fixes\r\n- dbname was not defaulting correctly.\r\n- bin_path did not work correctly on windows platforms.\r\n- Updated the connection text in the Result buffer.\r\n- Overhauled the DB2 support.\r\n","3":"New Features\r\n- Tutorial - Based on feedback from users, created a step by step tutorial.\r\nAll users should try the tutorial to learn how to use the various features\r\nof the plugin.\r\n- DBGetOption - without parameters populates the Result window with all\r\noptions.\r\n- DBGetOption and DBSetOption support command line completion for the\r\nvarious options (DBGetOption d<tab>, will cycle through all options\r\nbeginning with \"d\").\r\n- New option, replace_title, changes the title of the buffer to show\r\nconnection information which is useful if you are using  a scratch buffer to\r\ntest SQL.\r\n- IntegratedLogin support for Windows users.\r\n- DBExecRangeSQL - useful for custom mappings, and executing commands\r\nwithout visual mode.\r\n- New maps <Leader>sea - sql - execute - all (lines in the file),\r\n<Leader>sel - sql - execute - line (the current line)\r\n- New filetype support - jproperties\r\n\r\n\r\nBug Fixes\r\n- dbname was not defaulting correctly.\r\n- bin_path did not work correctly on windows platforms.\r\n- Updated the connection text in the Result buffer.\r\n- Overhauled the DB2 support.\r\n","package":"dbext-2.01.zip","4":"dbext-2.01.zip","src_id":"3259","5":"3259","creation_date":"1090454552","6":"1090454552"},{"0":"356","vim_version":"6.0","1":"6.0","script_version":"2.00","2":"2.00","version_comment":"dbext.vim has been greatly enhanced for version 2.00.\r\n\r\nAdditional features include:\r\n\r\nConnection Profiles\r\nYou can create as many profiles as you like in your vimrc.  Each profile specifies various connection information.  When you are prompted for connection information, for ease of use,  you can choose from a numbered list.\r\n\r\nModeline Support\r\nSimilar to Vim modelines, you can specify connection information as comments within your buffers.  To prevent sensitive information (ie passwords) from being visible, you can specify a connection profile as part of your modeline.  \r\n\r\nObject Completion\r\ndbext ties into Vim dictionary feature.  You can complete table names, procedure names and view names.\r\n\r\nViewing Lists of Objects\r\nYou can browse through the various objects in the database you are connected\r\nto and specify wildcard information.  For example you can say, \"Show me all\r\ntables beginning with 'ml_' \".  These objects are currently supported:\r\nTables, Procedures, Views,  Columns (for a table).\r\n\r\nFileType Support Added\r\ndbext has support for various filetypes.  For example, assume you dynamically build a SQL statement by joining strings together, using calls to functions, host parameters.  By visually selecting the code and executing it dbext will parse the statement, strip out the various string joining commands (+, ||,  .) and prompt you for host values before sending the string to be executed against the database.  This way it is very easy to test your SQL statements without having to cut and paste the commands into a SQL tool.  Currently supported filetypes are: PHP, Java, JSP, JavaScript, Perl, SQL, Vim.\r\n\r\nIntellisense Addin Support\r\nThe Intellisense  plugin now has SQL supported.  To enable greater functionality (table, procedure, view lists), it uses dbext.vim to retrieve this information.","3":"dbext.vim has been greatly enhanced for version 2.00.\r\n\r\nAdditional features include:\r\n\r\nConnection Profiles\r\nYou can create as many profiles as you like in your vimrc.  Each profile specifies various connection information.  When you are prompted for connection information, for ease of use,  you can choose from a numbered list.\r\n\r\nModeline Support\r\nSimilar to Vim modelines, you can specify connection information as comments within your buffers.  To prevent sensitive information (ie passwords) from being visible, you can specify a connection profile as part of your modeline.  \r\n\r\nObject Completion\r\ndbext ties into Vim dictionary feature.  You can complete table names, procedure names and view names.\r\n\r\nViewing Lists of Objects\r\nYou can browse through the various objects in the database you are connected\r\nto and specify wildcard information.  For example you can say, \"Show me all\r\ntables beginning with 'ml_' \".  These objects are currently supported:\r\nTables, Procedures, Views,  Columns (for a table).\r\n\r\nFileType Support Added\r\ndbext has support for various filetypes.  For example, assume you dynamically build a SQL statement by joining strings together, using calls to functions, host parameters.  By visually selecting the code and executing it dbext will parse the statement, strip out the various string joining commands (+, ||,  .) and prompt you for host values before sending the string to be executed against the database.  This way it is very easy to test your SQL statements without having to cut and paste the commands into a SQL tool.  Currently supported filetypes are: PHP, Java, JSP, JavaScript, Perl, SQL, Vim.\r\n\r\nIntellisense Addin Support\r\nThe Intellisense  plugin now has SQL supported.  To enable greater functionality (table, procedure, view lists), it uses dbext.vim to retrieve this information.","package":"dbext-2.0.zip","4":"dbext-2.0.zip","src_id":"3220","5":"3220","creation_date":"1089545200","6":"1089545200"}]},"355":{"script_id":"355","0":"355","script_name":"vimrc_nopik","1":"vimrc_nopik","script_type":"utility","2":"utility","summary":"Customized vimrc by Nopik","3":"Customized vimrc by Nopik","description":"After quite long usage of vim I\\'ve got quite useful vimrc file. Its newest version can be found at http:\/\/www.nopik.of.pl\nRight now it uses all of function keys for easy buffer browsing and compilation (it is tailored for C\/C++). There is also few other nice features and keybindings.","4":"After quite long usage of vim I\\'ve got quite useful vimrc file. Its newest version can be found at http:\/\/www.nopik.of.pl\nRight now it uses all of function keys for easy buffer browsing and compilation (it is tailored for C\/C++). There is also few other nice features and keybindings.","install_details":"","5":"","first_name":"Kamil","6":"Kamil","last_name":"Burzynski","7":"Burzynski","releases":[{"0":"355","vim_version":"6.0","1":"6.0","script_version":"1.9","2":"1.9","version_comment":"This upload didn't change since last time, but now comes with short keybinding description on homepage and fixes a number in script version ;)","3":"This upload didn't change since last time, but now comes with short keybinding description on homepage and fixes a number in script version ;)","package":"vimrc","4":"vimrc","src_id":"1057","5":"1057","creation_date":"1027779303","6":"1027779303"},{"0":"355","vim_version":"6.0","1":"6.0","script_version":"6.1","2":"6.1","version_comment":"Initial upload","3":"Initial upload","package":"vimrc","4":"vimrc","src_id":"1054","5":"1054","creation_date":"1027683905","6":"1027683905"}]},"354":{"script_id":"354","0":"354","script_name":"variableSort.vim","1":"variableSort.vim","script_type":"utility","2":"utility","summary":"Function to sort a simulated array variable set.","3":"Function to sort a simulated array variable set.","description":"This is  a sorting function which  takes the name of  an array-like variable\r\nwhich ends  in numerical  subscripts along  the lines  of var0,  var1, var2.\r\nThese can be created quite easily with the var{i} notation of Vim 6.\r\n\r\nOther parameters are the starting  and ending subscripts (inclusive) and the\r\ndirection of the sort (1 or 'a' for ascending, otherwise descending).\r\n\r\nThe array is sorted in place; there is no return value from the function.\r\n\r\nOptional  argument  is the  name  of  a swap  function  that  takes the  two\r\nsubscripts  and  swaps the  variable  (there  is  one provided  that  should\r\nactually be good enough for most  cases; however, if something special needs\r\nto be  done for the swap  -- such as  multiple records, then this  should be\r\nused.  In this  case, it  is  assumed the  swap function  already knows  the\r\nvariables it's going to swap and thus aren't passed in.)\r\n\r\nSample custom swap function:\r\nfunction! MultipleRangeSwap( sub1, sub2 )\r\n  let temp = b:rangeS{a:sub1}\r\n  let b:rangeS{a:sub1} = b:rangeS{a:sub2}\r\n  let b:rangeS{a:sub2} = temp\r\n\r\n  let temp = b:rangeE{a:sub1}\r\n  let b:rangeE{a:sub1} = b:rangeE{a:sub2}\r\n  let b:rangeE{a:sub2} = temp\r\nendfunction\r\n\r\nSample call:\r\ncall SortArray( \"b:rangeS\", 0, b:numRanges - 1, 1, \"MultipleRangeSwap\" )\r\n\r\nThis will perform an ascending sort  on a variable sequence named b:rangeS0,\r\nb:rangeS1 etc.,  using the MultipleRangeSwap  function for the  actual swap.\r\nThis function  was needed here  because two  variables needed to  be swapped\r\ntogether  even though  only  one was  used  in the  sort.  The default  swap\r\nwould've only swapped b:rangeS variables, leaving the b:rangeE variables out\r\nof sync.","4":"This is  a sorting function which  takes the name of  an array-like variable\r\nwhich ends  in numerical  subscripts along  the lines  of var0,  var1, var2.\r\nThese can be created quite easily with the var{i} notation of Vim 6.\r\n\r\nOther parameters are the starting  and ending subscripts (inclusive) and the\r\ndirection of the sort (1 or 'a' for ascending, otherwise descending).\r\n\r\nThe array is sorted in place; there is no return value from the function.\r\n\r\nOptional  argument  is the  name  of  a swap  function  that  takes the  two\r\nsubscripts  and  swaps the  variable  (there  is  one provided  that  should\r\nactually be good enough for most  cases; however, if something special needs\r\nto be  done for the swap  -- such as  multiple records, then this  should be\r\nused.  In this  case, it  is  assumed the  swap function  already knows  the\r\nvariables it's going to swap and thus aren't passed in.)\r\n\r\nSample custom swap function:\r\nfunction! MultipleRangeSwap( sub1, sub2 )\r\n  let temp = b:rangeS{a:sub1}\r\n  let b:rangeS{a:sub1} = b:rangeS{a:sub2}\r\n  let b:rangeS{a:sub2} = temp\r\n\r\n  let temp = b:rangeE{a:sub1}\r\n  let b:rangeE{a:sub1} = b:rangeE{a:sub2}\r\n  let b:rangeE{a:sub2} = temp\r\nendfunction\r\n\r\nSample call:\r\ncall SortArray( \"b:rangeS\", 0, b:numRanges - 1, 1, \"MultipleRangeSwap\" )\r\n\r\nThis will perform an ascending sort  on a variable sequence named b:rangeS0,\r\nb:rangeS1 etc.,  using the MultipleRangeSwap  function for the  actual swap.\r\nThis function  was needed here  because two  variables needed to  be swapped\r\ntogether  even though  only  one was  used  in the  sort.  The default  swap\r\nwould've only swapped b:rangeS variables, leaving the b:rangeE variables out\r\nof sync.","install_details":"Pop into your plugin directory.","5":"Pop into your plugin directory.","first_name":"Salman","6":"Salman","last_name":"Halim","7":"Halim","releases":[{"0":"354","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"variableSort.vim","4":"variableSort.vim","src_id":"1050","5":"1050","creation_date":"1027665877","6":"1027665877"}]},"353":{"script_id":"353","0":"353","script_name":"getVar.vim","1":"getVar.vim","script_type":"utility","2":"utility","summary":"Convenient retrieval of buffer or global script options.","3":"Convenient retrieval of buffer or global script options.","description":"These are just a few convenience functions that are useful for retrieval of plugin options that can be set globally as well as having buffer-specific over-rides.\r\n\r\nExample:  I have a global variable called \"g:sortOrder\" which is set to \"a\".  In the test.java buffer, I create a buffer variable called \"b:sortOrder\" which is set to \"d\".  Now, GetVar#GetVar( \"sortOrder\" ) will return \"d\" when I'm in test.java and \"a\" everywhere else.  My plugin code doesn't need to actually check for buffer or global variables; I can just call GetVar#GetVar and be done with it.\r\n\r\nWhy is this useful?  It mimics the behaviour of options.  For example, :set grepprg? will return the value of 'grepprg'; if a local version has been set (:setlocal grepprg=<something>), it will quietly return that.  Otherwise, it will return the global value.  GetVar#GetVar allows the same behaviour for variables.\r\n\r\nGetVar#GetVar will take an optional second parameter which will be the default value to return if neither a buffer nor a global variable by the specified name is found (the default default :) is -1).\r\n\r\nExample:  GetVar#GetVar( \"userID\", \"NONE\" ) will take either a userID or the string \"NONE\" if there isn't one.  This can be useful where a script should just use an assumed default if the user hasn't specified an override (global or otherwise).\r\n\r\nGetVar#VarExists simply returns true if any of the scopes used by GetVar#GetVar exist (in the same order of checking as GetVar#GetVar).\r\n","4":"These are just a few convenience functions that are useful for retrieval of plugin options that can be set globally as well as having buffer-specific over-rides.\r\n\r\nExample:  I have a global variable called \"g:sortOrder\" which is set to \"a\".  In the test.java buffer, I create a buffer variable called \"b:sortOrder\" which is set to \"d\".  Now, GetVar#GetVar( \"sortOrder\" ) will return \"d\" when I'm in test.java and \"a\" everywhere else.  My plugin code doesn't need to actually check for buffer or global variables; I can just call GetVar#GetVar and be done with it.\r\n\r\nWhy is this useful?  It mimics the behaviour of options.  For example, :set grepprg? will return the value of 'grepprg'; if a local version has been set (:setlocal grepprg=<something>), it will quietly return that.  Otherwise, it will return the global value.  GetVar#GetVar allows the same behaviour for variables.\r\n\r\nGetVar#GetVar will take an optional second parameter which will be the default value to return if neither a buffer nor a global variable by the specified name is found (the default default :) is -1).\r\n\r\nExample:  GetVar#GetVar( \"userID\", \"NONE\" ) will take either a userID or the string \"NONE\" if there isn't one.  This can be useful where a script should just use an assumed default if the user hasn't specified an override (global or otherwise).\r\n\r\nGetVar#VarExists simply returns true if any of the scopes used by GetVar#GetVar exist (in the same order of checking as GetVar#GetVar).\r\n","install_details":"Pop it into the autload directory and use in your plugins -- just make sure to add this as a dependence when you submit your plugin to this site.","5":"Pop it into the autload directory and use in your plugins -- just make sure to add this as a dependence when you submit your plugin to this site.","first_name":"Salman","6":"Salman","last_name":"Halim","7":"Halim","releases":[{"0":"353","vim_version":"7.0","1":"7.0","script_version":"2.0","2":"2.0","version_comment":"Made the whole thing into an autoload script, prefixing the names of all the functions with GetVar (the name of the script); so, the new function names are:\r\n\r\nGetVar#GetVar\r\nGetVar#VarExists\r\nGetVar#GetSafe\r\nGetVar#Allocate\r\n","3":"Made the whole thing into an autoload script, prefixing the names of all the functions with GetVar (the name of the script); so, the new function names are:\r\n\r\nGetVar#GetVar\r\nGetVar#VarExists\r\nGetVar#GetSafe\r\nGetVar#Allocate\r\n","package":"GetVar.vim","4":"GetVar.vim","src_id":"15512","5":"15512","creation_date":"1303600690","6":"1303600690"},{"0":"353","vim_version":"6.0","1":"6.0","script_version":"1.4","2":"1.4","version_comment":"Added two new functions: GetSafe and Allocate.","3":"Added two new functions: GetSafe and Allocate.","package":"GetVar.vim","4":"GetVar.vim","src_id":"12655","5":"12655","creation_date":"1268928019","6":"1268928019"},{"0":"353","vim_version":"6.0","1":"6.0","script_version":"1.3","2":"1.3","version_comment":"Changed the plugin slightly to allow for a default value to continue working if the regular return value is a list (or dictionary; basically, not a simple\r\nscalar value). Then change, while bringing the plugin up to scratch with Vim 7.x, doesn't break Vim 6.x compatibility.\r\n","3":"Changed the plugin slightly to allow for a default value to continue working if the regular return value is a list (or dictionary; basically, not a simple\r\nscalar value). Then change, while bringing the plugin up to scratch with Vim 7.x, doesn't break Vim 6.x compatibility.\r\n","package":"GetVar.vim","4":"GetVar.vim","src_id":"10132","5":"10132","creation_date":"1236350229","6":"1236350229"},{"0":"353","vim_version":"7.0","1":"7.0","script_version":"1.2","2":"1.2","version_comment":"Updated to use Vim 7's t: (tab-specific) variables once buffer-specific variables aren't found.\r\nThe new sequence is window -> buffer -> tab -> global.  (Just stick with 1.1 if not using Vim 7.)\r\n","3":"Updated to use Vim 7's t: (tab-specific) variables once buffer-specific variables aren't found.\r\nThe new sequence is window -> buffer -> tab -> global.  (Just stick with 1.1 if not using Vim 7.)\r\n","package":"getVar.vim","4":"getVar.vim","src_id":"5504","5":"5504","creation_date":"1143815173","6":"1143815173"},{"0":"353","vim_version":"6.0","1":"6.0","script_version":"1.1","2":"1.1","version_comment":"Updated to return window-specific variables, THEN buffer and then global variables.","3":"Updated to return window-specific variables, THEN buffer and then global variables.","package":"getVar.vim","4":"getVar.vim","src_id":"2345","5":"2345","creation_date":"1064210479","6":"1064210479"},{"0":"353","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"getVar.vim","4":"getVar.vim","src_id":"1049","5":"1049","creation_date":"1027665363","6":"1027665363"}]},"352":{"script_id":"352","0":"352","script_name":"multipleRanges.vim","1":"multipleRanges.vim","script_type":"utility","2":"utility","summary":"Selecting different ranges of lines","3":"Selecting different ranges of lines","description":"This script lets you choose multiple non-consecutive ranges and then execute commands on them all at the same time.  Just visually select a range of lines and hit the mapping sequence.  Repeat until all the ranges have been selected (they will be highlighted).  Then, execute the script-defined command Rangecommand with the actual command (and arguments) as arguments to Rangecommand and it'll do it.  The ranges will remain selected until you execute the reset mapping allowing you to execute more commands on the ranges.\r\n\r\nNOTE:  VERSION 1.2 AND ABOVE DEPEND ON MY getVar.vim vimscript#353 AND variableSort.vim vimscript#354.  Sorry I neglected to mention that before.\r\n\r\nVersion 1.8: No new functionality; brought the plugin up to Vim version 7.2, using Lists and removing the dependence on variableSort.vim (getVar.vim is still required).","4":"This script lets you choose multiple non-consecutive ranges and then execute commands on them all at the same time.  Just visually select a range of lines and hit the mapping sequence.  Repeat until all the ranges have been selected (they will be highlighted).  Then, execute the script-defined command Rangecommand with the actual command (and arguments) as arguments to Rangecommand and it'll do it.  The ranges will remain selected until you execute the reset mapping allowing you to execute more commands on the ranges.\r\n\r\nNOTE:  VERSION 1.2 AND ABOVE DEPEND ON MY getVar.vim vimscript#353 AND variableSort.vim vimscript#354.  Sorry I neglected to mention that before.\r\n\r\nVersion 1.8: No new functionality; brought the plugin up to Vim version 7.2, using Lists and removing the dependence on variableSort.vim (getVar.vim is still required).","install_details":"Pop it into the plugin directory.  Read the usage comments in the plugin for, well, usage directions.","5":"Pop it into the plugin directory.  Read the usage comments in the plugin for, well, usage directions.","first_name":"Salman","6":"Salman","last_name":"Halim","7":"Halim","releases":[{"0":"352","vim_version":"7.2","1":"7.2","script_version":"1.8","2":"1.8","version_comment":"No new functionality; brought the plugin up to version 7.2, using Lists and removing the dependence on variableSort.vim (getVar.vim is still required).","3":"No new functionality; brought the plugin up to version 7.2, using Lists and removing the dependence on variableSort.vim (getVar.vim is still required).","package":"multipleRanges.vim","4":"multipleRanges.vim","src_id":"15431","5":"15431","creation_date":"1302565202","6":"1302565202"},{"0":"352","vim_version":"6.0","1":"6.0","script_version":"1.7","2":"1.7","version_comment":"Added a new command (Rangecommandnormal) which allows for a normal-mode command to be executed on the ranges. Also added mappings to quickly enter the Rangecommand and Rangecommandnormal command-lines. Added error-checking in case there are no ranges currently selected when the commands are executed.","3":"Added a new command (Rangecommandnormal) which allows for a normal-mode command to be executed on the ranges. Also added mappings to quickly enter the Rangecommand and Rangecommandnormal command-lines. Added error-checking in case there are no ranges currently selected when the commands are executed.","package":"multipleRanges.vim","4":"multipleRanges.vim","src_id":"1150","5":"1150","creation_date":"1029831575","6":"1029831575"},{"0":"352","vim_version":"6.0","1":"6.0","script_version":"1.65","2":"1.65","version_comment":"Removed the unique keyword from the internal script mappings as Vikas Agnihotri pointed out that this was causing a problem with potential reloading of the script while not adding anything to the ease of use.","3":"Removed the unique keyword from the internal script mappings as Vikas Agnihotri pointed out that this was causing a problem with potential reloading of the script while not adding anything to the ease of use.","package":"multipleRanges.vim","4":"multipleRanges.vim","src_id":"1058","5":"1058","creation_date":"1027793042","6":"1027793042"},{"0":"352","vim_version":"6.0","1":"6.0","script_version":"1.6","2":"1.6","version_comment":"Added  support for  user-defined highlights for  the ranges  (GUI only; will do cterm if asked).","3":"Added  support for  user-defined highlights for  the ranges  (GUI only; will do cterm if asked).","package":"multipleRanges.vim","4":"multipleRanges.vim","src_id":"1055","5":"1055","creation_date":"1027684365","6":"1027684365"},{"0":"352","vim_version":"6.0","1":"6.0","script_version":"1.5","2":"1.5","version_comment":"Depends on getVar.vim vimscript 353 and variableSort.vim vimscript 354.  Added the ability to invert range.  Ranges are now on a per-buffer basis instead of a per-window (was causing problems where a new buffer in the same window would act up).","3":"Depends on getVar.vim vimscript 353 and variableSort.vim vimscript 354.  Added the ability to invert range.  Ranges are now on a per-buffer basis instead of a per-window (was causing problems where a new buffer in the same window would act up).","package":"multipleRanges.vim","4":"multipleRanges.vim","src_id":"1051","5":"1051","creation_date":"1027669954","6":"1027669954"},{"0":"352","vim_version":"6.0","1":"6.0","script_version":"1.2","2":"1.2","version_comment":"Cleans  up better once  a set of ranges  is cleared (the  variables are unlet).\r\nAdded  an  option (buffer  or  global  variable called  'consolidateRanges') which,  if  set  to 1,  will  cause  Rangecommand  to  first sort  and  then consolidate  overlapping ranges  into a  single range  before executing  the command. The ranges will remain consolidated once the command is done.","3":"Cleans  up better once  a set of ranges  is cleared (the  variables are unlet).\r\nAdded  an  option (buffer  or  global  variable called  'consolidateRanges') which,  if  set  to 1,  will  cause  Rangecommand  to  first sort  and  then consolidate  overlapping ranges  into a  single range  before executing  the command. The ranges will remain consolidated once the command is done.","package":"multipleRanges.vim","4":"multipleRanges.vim","src_id":"1048","5":"1048","creation_date":"1027606369","6":"1027606369"},{"0":"352","vim_version":"6.0","1":"6.0","script_version":"1.1","2":"1.1","version_comment":"Added a new command to show the current list of ranges (ugly output), made the script more plugin-like and updated usage comments slightly.","3":"Added a new command to show the current list of ranges (ugly output), made the script more plugin-like and updated usage comments slightly.","package":"multipleRanges.vim","4":"multipleRanges.vim","src_id":"1047","5":"1047","creation_date":"1027581665","6":"1027581665"},{"0":"352","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"multipleRanges.vim","4":"multipleRanges.vim","src_id":"1046","5":"1046","creation_date":"1027580210","6":"1027580210"}]},"351":{"script_id":"351","0":"351","script_name":"localColorSchemes.vim","1":"localColorSchemes.vim","script_type":"utility","2":"utility","summary":"Local color schemes","3":"Local color schemes","description":"This allows the use of buffer-specific color schemes.  Every time one moves from one buffer to another, the color scheme will change to the specified one; setting the variable b:colorscheme inside an ftplugin will allow for all files of a particular type to have that scheme (such as morning for vim files, peachpuff for Java files etc.).\r\n\r\nTo use, there are three mappings, all starting with <Leader>:  sl prompts and sets a local color scheme, sg does the same for a global color scheme and rl removes any locally set color schemes.  There is also a convenience command called Colorscheme which behaves just like the regular colorscheme command (except for the command-line completion); it also modifies the global colorscheme name.\r\n\r\nI have placed the value of the colorscheme names my 'statusline' option so I can tell which colors are being used -- and I stick either a g: or b: before the name so I know if it's a local or global setting.  (Hint:  use a non <SID> version of GetVar -- included within).\r\n\r\nThe only problem I know of is that syntax settings set by plugins (such as the excellent ShowMarks) get reset every time a color scheme is changed (since they start with a syntax clear).","4":"This allows the use of buffer-specific color schemes.  Every time one moves from one buffer to another, the color scheme will change to the specified one; setting the variable b:colorscheme inside an ftplugin will allow for all files of a particular type to have that scheme (such as morning for vim files, peachpuff for Java files etc.).\r\n\r\nTo use, there are three mappings, all starting with <Leader>:  sl prompts and sets a local color scheme, sg does the same for a global color scheme and rl removes any locally set color schemes.  There is also a convenience command called Colorscheme which behaves just like the regular colorscheme command (except for the command-line completion); it also modifies the global colorscheme name.\r\n\r\nI have placed the value of the colorscheme names my 'statusline' option so I can tell which colors are being used -- and I stick either a g: or b: before the name so I know if it's a local or global setting.  (Hint:  use a non <SID> version of GetVar -- included within).\r\n\r\nThe only problem I know of is that syntax settings set by plugins (such as the excellent ShowMarks) get reset every time a color scheme is changed (since they start with a syntax clear).","install_details":"Pop it into your plugin directory.","5":"Pop it into your plugin directory.","first_name":"Salman","6":"Salman","last_name":"Halim","7":"Halim","releases":[{"0":"351","vim_version":"6.0","1":"6.0","script_version":"1.2","2":"1.2","version_comment":"Added Removewindowcolors  and Setwindowcolors to set  window-specific colors (along with mappings).","3":"Added Removewindowcolors  and Setwindowcolors to set  window-specific colors (along with mappings).","package":"localColorSchemes.vim","4":"localColorSchemes.vim","src_id":"2347","5":"2347","creation_date":"1064215545","6":"1064215545"},{"0":"351","vim_version":"6.0","1":"6.0","script_version":"1.1","2":"1.1","version_comment":"Removed internal GetVar; now has a dependence on getVar.vim (http:\/\/www.vim.org\/scripts\/script.php?script_id=353).","3":"Removed internal GetVar; now has a dependence on getVar.vim (http:\/\/www.vim.org\/scripts\/script.php?script_id=353).","package":"localColorSchemes.vim","4":"localColorSchemes.vim","src_id":"2346","5":"2346","creation_date":"1064210641","6":"1064210641"},{"0":"351","vim_version":"6.0","1":"6.0","script_version":"1","2":"1","version_comment":"Initial upload","3":"Initial upload","package":"localColorSchemes.vim","4":"localColorSchemes.vim","src_id":"1045","5":"1045","creation_date":"1027492049","6":"1027492049"}]},"350":{"script_id":"350","0":"350","script_name":"Highlight UnMatched Brackets","1":"Highlight UnMatched Brackets","script_type":"utility","2":"utility","summary":"Capture those unmatched brackets while u r still in insert-mode","3":"Capture those unmatched brackets while u r still in insert-mode","description":"Its really irksome when your compiler\r\ncomplains for any unmatched \"{\" or \"(\" or \"[\".\r\nWith this plugin you can highlight all\r\nthose unmatched \"{\" or \"(\"  or  \"[\" as you type.\r\nThis helps you to keep track of where\r\nthe exact closing bracket should come.\r\n\r\nThis plugin also warns you of any extra \"}\" or \")\" or \"]\" you typed.\r\n\r\nCustomization:   \r\n\t\t   - Specifying Additional Bracket-pairs.\r\n         \t\t   \t  User can specify additional matching pairs in\r\n                     the global option 'matchpairs', see :help 'matchpairs'\r\n                     For eg: set mps+=<:> (to include <> pair)\r\n                     put the above setting in .vimrc file and restart vim.\r\n                  - To get rid of highlighting when you quit insert\r\n                     mode, add this mapping in your vimrc\r\n                           noremap! <Esc> <Esc>:match NONE<CR>\r\n\r\nTo test how this plugin works type something like\r\n{\r\n  (     ) [ ]\r\n  ( ( ( ) ) )\r\n}\r\n\r\nHappy vimming.\r\n\r\n-ncr","4":"Its really irksome when your compiler\r\ncomplains for any unmatched \"{\" or \"(\" or \"[\".\r\nWith this plugin you can highlight all\r\nthose unmatched \"{\" or \"(\"  or  \"[\" as you type.\r\nThis helps you to keep track of where\r\nthe exact closing bracket should come.\r\n\r\nThis plugin also warns you of any extra \"}\" or \")\" or \"]\" you typed.\r\n\r\nCustomization:   \r\n\t\t   - Specifying Additional Bracket-pairs.\r\n         \t\t   \t  User can specify additional matching pairs in\r\n                     the global option 'matchpairs', see :help 'matchpairs'\r\n                     For eg: set mps+=<:> (to include <> pair)\r\n                     put the above setting in .vimrc file and restart vim.\r\n                  - To get rid of highlighting when you quit insert\r\n                     mode, add this mapping in your vimrc\r\n                           noremap! <Esc> <Esc>:match NONE<CR>\r\n\r\nTo test how this plugin works type something like\r\n{\r\n  (     ) [ ]\r\n  ( ( ( ) ) )\r\n}\r\n\r\nHappy vimming.\r\n\r\n-ncr","install_details":"Drop this in your plugins directory or\r\nmanually source this file using \r\n :so UnMtchBracket.vim","5":"Drop this in your plugins directory or\r\nmanually source this file using \r\n :so UnMtchBracket.vim","first_name":"Naveen","6":"Naveen","last_name":"Chandra","7":"Chandra","releases":[{"0":"350","vim_version":"6.0","1":"6.0","script_version":"2.0","2":"2.0","version_comment":"- Added support for defining additional bracket \r\npairs through matchpairs.\r\n- Elliminated those irksome errorbells by silent!\r\n- Added support for highlighting brackets within the\r\ndisplayed lines i.e. highlighting the brackets is \r\ndone only in the currently displayed lines \r\neventhough the matching bracket is outside the \r\ncurrently displayed lines.\r\n- Elliminated those visual jerks or shifting of \r\nediting line.","3":"- Added support for defining additional bracket \r\npairs through matchpairs.\r\n- Elliminated those irksome errorbells by silent!\r\n- Added support for highlighting brackets within the\r\ndisplayed lines i.e. highlighting the brackets is \r\ndone only in the currently displayed lines \r\neventhough the matching bracket is outside the \r\ncurrently displayed lines.\r\n- Elliminated those visual jerks or shifting of \r\nediting line.","package":"UnMtchBracket.vim","4":"UnMtchBracket.vim","src_id":"1303","5":"1303","creation_date":"1034669219","6":"1034669219"},{"0":"350","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"UnMtchBracket.vim","4":"UnMtchBracket.vim","src_id":"1042","5":"1042","creation_date":"1027391666","6":"1027391666"}]},"349":{"script_id":"349","0":"349","script_name":"ruby.vim","1":"ruby.vim","script_type":"utility","2":"utility","summary":"Ruby language compiler plugin","3":"Ruby language compiler plugin","description":"NB: The ruby compiler plugin is now part of the vim-ruby project at rubyforge.org.  Please visit the vim-ruby project page for the latest information about this plugin and the vim-ruby project.  This page no longer contains the most recent version of the plugin.\r\n\r\nhttp:\/\/vim-ruby.rubyforge.org\r\nhttp:\/\/rubyforge.org\r\n\r\nThis is a compiler plugin for the Ruby language.  Not terribly glamorous, but it does take advantage of multi-line errorformats, and it's a little more graceful than the errorformats I've seen so far.","4":"NB: The ruby compiler plugin is now part of the vim-ruby project at rubyforge.org.  Please visit the vim-ruby project page for the latest information about this plugin and the vim-ruby project.  This page no longer contains the most recent version of the plugin.\r\n\r\nhttp:\/\/vim-ruby.rubyforge.org\r\nhttp:\/\/rubyforge.org\r\n\r\nThis is a compiler plugin for the Ruby language.  Not terribly glamorous, but it does take advantage of multi-line errorformats, and it's a little more graceful than the errorformats I've seen so far.","install_details":"First, make sure it's not already installed.  I've been told it will be included in future releases of Vim (> 601), so check that $VIMRUNTIME\/compiler\/ruby.vim doesn't already exist before attempting to install it.\r\n\r\n...unless of course, it's a newer revision.  =)\r\n\r\nSimply place the ruby.vim file in your compiler plugin subdirectory and either source it by hand or enable filetype plugins (':filetype plugin on').","5":"First, make sure it's not already installed.  I've been told it will be included in future releases of Vim (> 601), so check that $VIMRUNTIME\/compiler\/ruby.vim doesn't already exist before attempting to install it.\r\n\r\n...unless of course, it's a newer revision.  =)\r\n\r\nSimply place the ruby.vim file in your compiler plugin subdirectory and either source it by hand or enable filetype plugins (':filetype plugin on').","first_name":"Tim","6":"Tim","last_name":"Hammerquist","7":"Hammerquist","releases":[{"0":"349","vim_version":"6.0","1":"6.0","script_version":"0.2","2":"0.2","version_comment":"Initial upload","3":"Initial upload","package":"ruby-0.2.tar.gz","4":"ruby-0.2.tar.gz","src_id":"1040","5":"1040","creation_date":"1027375810","6":"1027375810"}]},"348":{"script_id":"348","0":"348","script_name":"White Dust","1":"White Dust","script_type":"color scheme","2":"color scheme","summary":"A light color scheme for GUI","3":"A light color scheme for GUI","description":"A light color scheme for GUI","4":"A light color scheme for GUI","install_details":"Place it in the colors directory","5":"Place it in the colors directory","first_name":"Little","6":"Little","last_name":"Dragon","7":"Dragon","releases":[{"0":"348","vim_version":"6.0","1":"6.0","script_version":"1","2":"1","version_comment":"Initial upload","3":"Initial upload","package":"whitedust.vim","4":"whitedust.vim","src_id":"1038","5":"1038","creation_date":"1027353950","6":"1027353950"}]},"347":{"script_id":"347","0":"347","script_name":"textlink.vim","1":"textlink.vim","script_type":"utility","2":"utility","summary":"Another way to hyperlink plain text files. |FileName|@|SearchString| notation...","3":"Another way to hyperlink plain text files. |FileName|@|SearchString| notation...","description":"This is (yet?) another way to implement hypertext styling linking in plain text files (a.k.a. source code).\r\n\r\nThe notation is extremely simple and easy to type (and comprehend at a glance): |FileName|@|SearchString| (even easier to understand at a glance with highlighting: see the Colors section of textlink.vim for details)\r\n\r\nThe format of a textlink is | filename to load_fullpath |@| text to search for |\r\n\r\n\r\nBasically this is just :split FileName, gg, \/SearchString. (ok very basically). You can omit loading of the file or searching for the SearchString if you like via the provided commands. You may also :vsplit if you like.\r\n\r\n\r\nCOMMANDS:\r\n:TTL\r\n    Mnemonic: test text link\r\n    Test text link. (echos the found FileName and SearchString)\r\n\r\n:TL\r\n    Mnemonic: text link\r\n    :split, :edit FileName, gg, \/SearchString (basically). This is to say splits the current window and loads the specified file name then searches for the specified SearchString from the top of the file.\r\n\r\n:TLF\r\n    Mnemonic: text link file\r\n    Like :TL save ignores the SearchString... basically a short cut to :split and gf\r\n\r\n:TLS\r\n    Mnemonic: text link string (or search)\r\n    Like :TL save ignores the FileName... useful when FileName is |T|\r\n    (this file) and you do not want to split the window.\r\n\r\n\r\n:TTL\r\n    Mnemonic: test text link\r\n    Test text link. (echos the found FileName and SearchString)\r\n\r\n:VTL\r\n:VTLF\r\n:VTLS\r\n    Same as the above commands save :vsplit vs :split.\r\n\r\n\r\nEXAMPLES:\r\n|T|@|Examples:|\r\n    This will search for 'Examples:' in this file (T for this). useful with either :TL or :TLS\r\n\r\n|A|@|Examples:|\r\n    This will search for 'Examples:' in the AlternateFile (A for alternate) from a.vim, see NOTE below. ? Wonderful for leaving notes about a function in a header file for instance.\r\n\r\n|$VIM\/vimfiles\/plugin\/textlink.vim|@|\" Examples:|\r\n    Environmental variables are expanded in the FileName portion, thanks to VIM :) In fact any(?) valid vim filename will work for FileName, I believe.\r\n\r\nSee: |~\\cvs.html|@|if(somenum < 25 || somenum > 15)|, pretty cool eh?\r\n    Although there can only be a single TextLink on any given line, it can appear anywhere in that line. (this is due to the greedy matching of the searchstring bars... to allow such a search string as this example..\r\n\r\n\r\nNOTE\r\nPlease see the comments in the file for more information and stuffs.\r\n\r\nAlso this can (and is setup to) use a.vim by Mike Sharpe (http:\/\/vim.sourceforge.net\/scripts\/script.php?script_id=31)\r\n\r\nThis works well enough to use everyday (I do) however there are probably a few quirks in it yet. (we all know how that goes ;) )\r\n\r\nI hope this is as useful to you as it is to me :)\r\n\r\n\r\nAlso of note (text hyperlinking) see  Stefan Bittner's http:\/\/vim.sourceforge.net\/scripts\/script.php?script_id=293\r\n\r\n\r\nHappy VIMing!\r\n\r\nRemoved buggy\/broken versions below, as there was no reason to use them (they were buggy!). I believe 1.32 is (finaly stable, sorry for all the bugs in the first place!)","4":"This is (yet?) another way to implement hypertext styling linking in plain text files (a.k.a. source code).\r\n\r\nThe notation is extremely simple and easy to type (and comprehend at a glance): |FileName|@|SearchString| (even easier to understand at a glance with highlighting: see the Colors section of textlink.vim for details)\r\n\r\nThe format of a textlink is | filename to load_fullpath |@| text to search for |\r\n\r\n\r\nBasically this is just :split FileName, gg, \/SearchString. (ok very basically). You can omit loading of the file or searching for the SearchString if you like via the provided commands. You may also :vsplit if you like.\r\n\r\n\r\nCOMMANDS:\r\n:TTL\r\n    Mnemonic: test text link\r\n    Test text link. (echos the found FileName and SearchString)\r\n\r\n:TL\r\n    Mnemonic: text link\r\n    :split, :edit FileName, gg, \/SearchString (basically). This is to say splits the current window and loads the specified file name then searches for the specified SearchString from the top of the file.\r\n\r\n:TLF\r\n    Mnemonic: text link file\r\n    Like :TL save ignores the SearchString... basically a short cut to :split and gf\r\n\r\n:TLS\r\n    Mnemonic: text link string (or search)\r\n    Like :TL save ignores the FileName... useful when FileName is |T|\r\n    (this file) and you do not want to split the window.\r\n\r\n\r\n:TTL\r\n    Mnemonic: test text link\r\n    Test text link. (echos the found FileName and SearchString)\r\n\r\n:VTL\r\n:VTLF\r\n:VTLS\r\n    Same as the above commands save :vsplit vs :split.\r\n\r\n\r\nEXAMPLES:\r\n|T|@|Examples:|\r\n    This will search for 'Examples:' in this file (T for this). useful with either :TL or :TLS\r\n\r\n|A|@|Examples:|\r\n    This will search for 'Examples:' in the AlternateFile (A for alternate) from a.vim, see NOTE below. ? Wonderful for leaving notes about a function in a header file for instance.\r\n\r\n|$VIM\/vimfiles\/plugin\/textlink.vim|@|\" Examples:|\r\n    Environmental variables are expanded in the FileName portion, thanks to VIM :) In fact any(?) valid vim filename will work for FileName, I believe.\r\n\r\nSee: |~\\cvs.html|@|if(somenum < 25 || somenum > 15)|, pretty cool eh?\r\n    Although there can only be a single TextLink on any given line, it can appear anywhere in that line. (this is due to the greedy matching of the searchstring bars... to allow such a search string as this example..\r\n\r\n\r\nNOTE\r\nPlease see the comments in the file for more information and stuffs.\r\n\r\nAlso this can (and is setup to) use a.vim by Mike Sharpe (http:\/\/vim.sourceforge.net\/scripts\/script.php?script_id=31)\r\n\r\nThis works well enough to use everyday (I do) however there are probably a few quirks in it yet. (we all know how that goes ;) )\r\n\r\nI hope this is as useful to you as it is to me :)\r\n\r\n\r\nAlso of note (text hyperlinking) see  Stefan Bittner's http:\/\/vim.sourceforge.net\/scripts\/script.php?script_id=293\r\n\r\n\r\nHappy VIMing!\r\n\r\nRemoved buggy\/broken versions below, as there was no reason to use them (they were buggy!). I believe 1.32 is (finaly stable, sorry for all the bugs in the first place!)","install_details":"To install simply drop into your plug in directory.\r\nLoad VIM and add text links (|Filename|@|searchstring|) to your files...\r\nThen place your cursoe on the line (anywhere on the line) and :TL (or one of the other commands) when you want to transverse the textlink.\r\n\r\nTo remove, simple delete or rename textlink.vim from ye plugin directory.","5":"To install simply drop into your plug in directory.\r\nLoad VIM and add text links (|Filename|@|searchstring|) to your files...\r\nThen place your cursoe on the line (anywhere on the line) and :TL (or one of the other commands) when you want to transverse the textlink.\r\n\r\nTo remove, simple delete or rename textlink.vim from ye plugin directory.","first_name":"Robert","6":"Robert","last_name":"KellyIV","7":"KellyIV","releases":[{"0":"347","vim_version":"6.0","1":"6.0","script_version":"1.4","2":"1.4","version_comment":"Should now accept absolute or full paths\r\nYou can now omit the T of for this file, i.e. || is valid and is the same as |T|.\r\nFixed one or two typos.\r\n","3":"Should now accept absolute or full paths\r\nYou can now omit the T of for this file, i.e. || is valid and is the same as |T|.\r\nFixed one or two typos.\r\n","package":"textlink.vim","4":"textlink.vim","src_id":"1285","5":"1285","creation_date":"1034023037","6":"1034023037"},{"0":"347","vim_version":"6.0","1":"6.0","script_version":"1.32","2":"1.32","version_comment":"Added documentation on what to do with the color definitions and the like, small bug fix in the textlink-fragment.vim file. (embeded in textlink.vim)","3":"Added documentation on what to do with the color definitions and the like, small bug fix in the textlink-fragment.vim file. (embeded in textlink.vim)","package":"textlink.vim","4":"textlink.vim","src_id":"1067","5":"1067","creation_date":"1028124720","6":"1028124720"},{"0":"347","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"textlink.vim","4":"textlink.vim","src_id":"1034","5":"1034","creation_date":"1027250420","6":"1027250420"}]},"346":{"script_id":"346","0":"346","script_name":"php.vim","1":"php.vim","script_type":"indent","2":"indent","summary":"THE Original indent for php","3":"THE Original indent for php","description":"This was the original vim php indent file written in 2002 and included in Vim 6.X releases.  It still works with the latest 9.X release.\r\n\r\nIndents after <?php tag, <? tag (optional), ( )or { }.  The script can also format switch\/case statements and more recently will automatically format \/* comment sections *\/\r\n\r\nIt likes the following format:\r\n<pre>\r\n    if($something)\r\n    {\r\n         dothis();\r\n    }\r\n\r\nOR\r\n    if($thisone) {\r\n        dothis();\r\n    }\r\n<\/pre>\r\n\r\nComment sections are automatically formatted, adding the * on a new line until closure by *\/ :\r\n\r\n\/* Comment line 1\r\n * Line 2\r\n *\/\r\n\r\nComments done using # also receive a new line with the # prepended.  But, you will have to end it manually since there is no difference between lines and the end of such sections.\r\nComments done using \/\/ also receive a new line with the \/\/ prepended.  But, you will have to end it manually since there is no difference between lines and the end of such sections.\r\n\r\nIt was not designed to and will not handle if blocks etc. without brackets and also does not format html.  Please use braces and separate display logic for more readable code.\r\n","4":"This was the original vim php indent file written in 2002 and included in Vim 6.X releases.  It still works with the latest 9.X release.\r\n\r\nIndents after <?php tag, <? tag (optional), ( )or { }.  The script can also format switch\/case statements and more recently will automatically format \/* comment sections *\/\r\n\r\nIt likes the following format:\r\n<pre>\r\n    if($something)\r\n    {\r\n         dothis();\r\n    }\r\n\r\nOR\r\n    if($thisone) {\r\n        dothis();\r\n    }\r\n<\/pre>\r\n\r\nComment sections are automatically formatted, adding the * on a new line until closure by *\/ :\r\n\r\n\/* Comment line 1\r\n * Line 2\r\n *\/\r\n\r\nComments done using # also receive a new line with the # prepended.  But, you will have to end it manually since there is no difference between lines and the end of such sections.\r\nComments done using \/\/ also receive a new line with the \/\/ prepended.  But, you will have to end it manually since there is no difference between lines and the end of such sections.\r\n\r\nIt was not designed to and will not handle if blocks etc. without brackets and also does not format html.  Please use braces and separate display logic for more readable code.\r\n","install_details":"Place in your \/usr\/share\/vim\/vim8X\/indent directory (e.g. \/usr\/share\/vim\/vim81\/indent), replacing the version which is installed by default.  NOTE: This script is no longer included in Vim as of 7.0, yet was replaced by another script.  After many years I still use this one with Vim 7.X and 8.X because it handles tab indentation correctly without adding spaces, etc.  The current official script seems to favor the use of spaces and if you want to always start with a tab you will have to enter that yourself on a new line after a closing bracket.  You're welcome to submit ideas for improvement.\r\n\r\nConfiguration\r\n  These can optionally be added to your vimrc:\r\n\r\n    php_noindent_switch -- do not try to indent switch\/case statements or comments (version 0.1 behavior)\r\n    php_indent_shortopentags -- indent after short php open tags, too\r\n    php_no_autocomment  -- do not automatically format comment sections\r\n    php_indent_space -- Use spaces instead of tabs [ This may work already if you have expandtab set in your config. ]\r\n","5":"Place in your \/usr\/share\/vim\/vim8X\/indent directory (e.g. \/usr\/share\/vim\/vim81\/indent), replacing the version which is installed by default.  NOTE: This script is no longer included in Vim as of 7.0, yet was replaced by another script.  After many years I still use this one with Vim 7.X and 8.X because it handles tab indentation correctly without adding spaces, etc.  The current official script seems to favor the use of spaces and if you want to always start with a tab you will have to enter that yourself on a new line after a closing bracket.  You're welcome to submit ideas for improvement.\r\n\r\nConfiguration\r\n  These can optionally be added to your vimrc:\r\n\r\n    php_noindent_switch -- do not try to indent switch\/case statements or comments (version 0.1 behavior)\r\n    php_indent_shortopentags -- indent after short php open tags, too\r\n    php_no_autocomment  -- do not automatically format comment sections\r\n    php_indent_space -- Use spaces instead of tabs [ This may work already if you have expandtab set in your config. ]\r\n","first_name":"Miles","6":"Miles","last_name":"Lott","7":"Lott","releases":[{"0":"346","vim_version":"7.0","1":"7.0","script_version":"1.4","2":"1.4","version_comment":"Add formatting of heredoc instances in code\r\nFix indentation of lines following a \/\/ or # comment line","3":"Add formatting of heredoc instances in code\r\nFix indentation of lines following a \/\/ or # comment line","package":"php.vim","4":"php.vim","src_id":"28659","5":"28659","creation_date":"1712528197","6":"1712528197"},{"0":"346","vim_version":"6.0","1":"6.0","script_version":"1.3","2":"1.3","version_comment":"Added the ability to configure use of spaces instead of tabs for indenting.  FWIW, this script is still working for me on the latest version of vim, even after 12 years.","3":"Added the ability to configure use of spaces instead of tabs for indenting.  FWIW, this script is still working for me on the latest version of vim, even after 12 years.","package":"php.vim","4":"php.vim","src_id":"26563","5":"26563","creation_date":"1561364165","6":"1561364165"},{"0":"346","vim_version":"7.0","1":"7.0","script_version":"1.2","2":"1.2","version_comment":"Versions 0.8 - 1.1 have a switch\/case formatting bug caused by an incomplete variable renaming.  1.2 should fix this.","3":"Versions 0.8 - 1.1 have a switch\/case formatting bug caused by an incomplete variable renaming.  1.2 should fix this.","package":"php.vim","4":"php.vim","src_id":"6758","5":"6758","creation_date":"1171826668","6":"1171826668"},{"0":"346","vim_version":"7.0","1":"7.0","script_version":"1.1","2":"1.1","version_comment":"Same as the last version, adding #-commented lines","3":"Same as the last version, adding #-commented lines","package":"php.vim","4":"php.vim","src_id":"6756","5":"6756","creation_date":"1171809370","6":"1171809370"},{"0":"346","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Decided to skip lines commented using \/\/ except for the initial tab","3":"Decided to skip lines commented using \/\/ except for the initial tab","package":"php.vim","4":"php.vim","src_id":"6754","5":"6754","creation_date":"1171808957","6":"1171808957"},{"0":"346","vim_version":"7.0","1":"7.0","script_version":"0.9","2":"0.9","version_comment":"Sameday bugfix for certain commenting styles, e.g. closing with \/**\/","3":"Sameday bugfix for certain commenting styles, e.g. closing with \/**\/","package":"php.vim","4":"php.vim","src_id":"6752","5":"6752","creation_date":"1171787719","6":"1171787719"},{"0":"346","vim_version":"7.0","1":"7.0","script_version":"0.8","2":"0.8","version_comment":"Borrowed methods from current dist of php.vim for automatic formatting of comments (http:\/\/www.2072productions.com\/?to=phpindent.txt).  Otherwise, the function of the file is largely unchanged, i.e. it STILL works.\r\n","3":"Borrowed methods from current dist of php.vim for automatic formatting of comments (http:\/\/www.2072productions.com\/?to=phpindent.txt).  Otherwise, the function of the file is largely unchanged, i.e. it STILL works.\r\n","package":"php.vim","4":"php.vim","src_id":"6751","5":"6751","creation_date":"1171778016","6":"1171778016"},{"0":"346","vim_version":"6.0","1":"6.0","script_version":"0.7","2":"0.7","version_comment":"Fixed \/* comment *\/ indentation with patch from devin@tritarget.com.","3":"Fixed \/* comment *\/ indentation with patch from devin@tritarget.com.","package":"php.vim","4":"php.vim","src_id":"6021","5":"6021","creation_date":"1154462445","6":"1154462445"},{"0":"346","vim_version":"6.0","1":"6.0","script_version":"0.6","2":"0.6","version_comment":"Fix indentation for closing bracket (patch from ITLab at MUSC - http:\/\/www.itlab.musc.edu\/).  Problem reported by various users.  The fix came via the debian vim maintainers (bug 282135).","3":"Fix indentation for closing bracket (patch from ITLab at MUSC - http:\/\/www.itlab.musc.edu\/).  Problem reported by various users.  The fix came via the debian vim maintainers (bug 282135).","package":"php.vim","4":"php.vim","src_id":"4049","5":"4049","creation_date":"1111385913","6":"1111385913"},{"0":"346","vim_version":"6.0","1":"6.0","script_version":"0.5","2":"0.5","version_comment":"Bug fix for open tag and empty statements.","3":"Bug fix for open tag and empty statements.","package":"php.vim","4":"php.vim","src_id":"3032","5":"3032","creation_date":"1084861463","6":"1084861463"},{"0":"346","vim_version":"6.0","1":"6.0","script_version":"0.4","2":"0.4","version_comment":"Fixes for closing php tag, switch statement closure, and php_indent_shortopentags option from Steffen Bruentjen <vim@kontraphon.de>\r\n","3":"Fixes for closing php tag, switch statement closure, and php_indent_shortopentags option from Steffen Bruentjen <vim@kontraphon.de>\r\n","package":"php.vim","4":"php.vim","src_id":"3031","5":"3031","creation_date":"1084857066","6":"1084857066"},{"0":"346","vim_version":"6.0","1":"6.0","script_version":"0.3","2":"0.3","version_comment":"This adds an option to turn off the formatting of switch\/case statements.  This combines versions 0.1 and 0.2.","3":"This adds an option to turn off the formatting of switch\/case statements.  This combines versions 0.1 and 0.2.","package":"php.vim","4":"php.vim","src_id":"1555","5":"1555","creation_date":"1040066138","6":"1040066138"},{"0":"346","vim_version":"6.0","1":"6.0","script_version":"0.2","2":"0.2","version_comment":"This adds formatting of switch\/case\/default, but with some strict requirements for preformatting.\r\nPlease read the file to see what I mean.","3":"This adds formatting of switch\/case\/default, but with some strict requirements for preformatting.\r\nPlease read the file to see what I mean.","package":"php.vim","4":"php.vim","src_id":"1036","5":"1036","creation_date":"1027281974","6":"1027281974"},{"0":"346","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"php.vim","4":"php.vim","src_id":"1032","5":"1032","creation_date":"1027168350","6":"1027168350"}]},"345":{"script_id":"345","0":"345","script_name":"lcscheck.vim","1":"lcscheck.vim","script_type":"utility","2":"utility","summary":"check 'listchars' for valid eol byte for utf-8. (Not needed for Vim 6.2)","3":"check 'listchars' for valid eol byte for utf-8. (Not needed for Vim 6.2)","description":"Under utf-8, characters 128 and over become multi-byte. Therefore, under  Vim 6.1 or earlier, they should not be used for the option values in 'listchars'. This script takes care of the \"eol:\" sub-option, the only one which gave me problems. If you use characters >= 128 for other sub-options, similar scripts can easily be written (based on this one) to take care of them.\r\n\r\nThis script has intentionally been abundantly commented to make it understandable.\r\n\r\nSee vimtip#246 for a related tip.","4":"Under utf-8, characters 128 and over become multi-byte. Therefore, under  Vim 6.1 or earlier, they should not be used for the option values in 'listchars'. This script takes care of the \"eol:\" sub-option, the only one which gave me problems. If you use characters >= 128 for other sub-options, similar scripts can easily be written (based on this one) to take care of them.\r\n\r\nThis script has intentionally been abundantly commented to make it understandable.\r\n\r\nSee vimtip#246 for a related tip.","install_details":"Paste or source this script text immediately before switching over to unicode, inside the statement\r\n\r\nif has(\"multi_byte\")\r\n\r\nif you use it, but otherwise before setting 'tenc' 'enc' 'fencs' etc. to the values used for Unicode editing.","5":"Paste or source this script text immediately before switching over to unicode, inside the statement\r\n\r\nif has(\"multi_byte\")\r\n\r\nif you use it, but otherwise before setting 'tenc' 'enc' 'fencs' etc. to the values used for Unicode editing.","first_name":"Antoine","6":"Antoine","last_name":"Mechelynck","7":"Mechelynck","releases":[{"0":"345","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"lcscheck.vim","4":"lcscheck.vim","src_id":"1029","5":"1029","creation_date":"1027089697","6":"1027089697"}]},"344":{"script_id":"344","0":"344","script_name":"MqlMenu.vim","1":"MqlMenu.vim","script_type":"utility","2":"utility","summary":"menus for eMatrix users","3":"menus for eMatrix users","description":"Creates a menu of Matrix mql commands\r\nMatrix is a Product Data Management system from MatrixOne http:\/\/www.matrixone.com \r\nIt has an SQL-like command language called mql . \r\nWhen you run the menu items, it runs\/imports\/etc with mql using the current file as input\r\n","4":"Creates a menu of Matrix mql commands\r\nMatrix is a Product Data Management system from MatrixOne http:\/\/www.matrixone.com \r\nIt has an SQL-like command language called mql . \r\nWhen you run the menu items, it runs\/imports\/etc with mql using the current file as input\r\n","install_details":"Just drop this file in your plugin folder\/directory.\r\n","5":"Just drop this file in your plugin folder\/directory.\r\n","first_name":"Roger","6":"Roger","last_name":"Pilkey","7":"Pilkey","releases":[{"0":"344","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"mqlmenu.vim","4":"mqlmenu.vim","src_id":"1028","5":"1028","creation_date":"1027072148","6":"1027072148"}]},"343":{"script_id":"343","0":"343","script_name":"fstab syntax","1":"fstab syntax","script_type":"syntax","2":"syntax","summary":"fstab syntax","3":"fstab syntax","description":"fstab syntax highlighting\r\nLatest version: http:\/\/ld.yi.org\/vim\/fstab.vim\r\n\r\nFeatures:\r\n- You can place let fstab_unknown_fs_errors = 0 in your .vimrc to instruct the highlighter to not show unknown filesystems as errors","4":"fstab syntax highlighting\r\nLatest version: http:\/\/ld.yi.org\/vim\/fstab.vim\r\n\r\nFeatures:\r\n- You can place let fstab_unknown_fs_errors = 0 in your .vimrc to instruct the highlighter to not show unknown filesystems as errors","install_details":"Place it in the syntax directory","5":"Place it in the syntax directory","first_name":"Little","6":"Little","last_name":"Dragon","7":"Dragon","releases":[{"0":"343","vim_version":"6.0","1":"6.0","script_version":"0.9","2":"0.9","version_comment":"Bug fixes","3":"Bug fixes","package":"fstab.vim","4":"fstab.vim","src_id":"6633","5":"6633","creation_date":"1169349614","6":"1169349614"},{"0":"343","vim_version":"6.0","1":"6.0","script_version":"0.8","2":"0.8","version_comment":"Bug fixes and additions","3":"Bug fixes and additions","package":"fstab.vim","4":"fstab.vim","src_id":"6530","5":"6530","creation_date":"1166579801","6":"1166579801"}]},"342":{"script_id":"342","0":"342","script_name":"sand","1":"sand","script_type":"color scheme","2":"color scheme","summary":"Light sand-like background color scheme with miscellaneous dark grains","3":"Light sand-like background color scheme with miscellaneous dark grains","description":"GUI only colorscheme.\r\nI created it some time ago when I found no light colorscheme that I like at vim.sf.net\r\nNow there are some, but I still like this one. So I decided to put it here.\r\n\r\nLook at http:\/\/sunsite.cs.msu.su\/~tim\/vim\/index.html It shows this scheme in work :) \r\nThis page was generated with syntax\/2html.vim script.","4":"GUI only colorscheme.\r\nI created it some time ago when I found no light colorscheme that I like at vim.sf.net\r\nNow there are some, but I still like this one. So I decided to put it here.\r\n\r\nLook at http:\/\/sunsite.cs.msu.su\/~tim\/vim\/index.html It shows this scheme in work :) \r\nThis page was generated with syntax\/2html.vim script.","install_details":"Save the file as \"colors\/sand.vim\" under 'runtimepath'. I.e. as ~\/.vim\/colors\/sand.vim under Unix.\r\nAnd use it with  :color sand. Change color to sand in your .vimrc\/.gvimrc if you like it.","5":"Save the file as \"colors\/sand.vim\" under 'runtimepath'. I.e. as ~\/.vim\/colors\/sand.vim under Unix.\r\nAnd use it with  :color sand. Change color to sand in your .vimrc\/.gvimrc if you like it.","first_name":"Tim","6":"Tim","last_name":"Alexeevsky","7":"Alexeevsky","releases":[{"0":"342","vim_version":"6.0","1":"6.0","script_version":"0.5","2":"0.5","version_comment":"Initial upload","3":"Initial upload","package":"sand.vim","4":"sand.vim","src_id":"1017","5":"1017","creation_date":"1026705103","6":"1026705103"}]},"341":{"script_id":"341","0":"341","script_name":"pf.vim","1":"pf.vim","script_type":"syntax","2":"syntax","summary":"OpenBSD pf.conf (packet filter configuration)","3":"OpenBSD pf.conf (packet filter configuration)","description":"\r\n!!! NOTE: since Apr-2013 this script has a new maintainer, and it is now hosted on Github: https:\/\/github.com\/lotheac\/pf.vim !!!\r\n\r\n\r\nSyntax file for OpenBSD's packet-filter (pf) configuration file: pf.conf.\r\n\r\nPreview \"screenshot\" here: http:\/\/www.sentia.org\/downloads\/pf.conf.html","4":"\r\n!!! NOTE: since Apr-2013 this script has a new maintainer, and it is now hosted on Github: https:\/\/github.com\/lotheac\/pf.vim !!!\r\n\r\n\r\nSyntax file for OpenBSD's packet-filter (pf) configuration file: pf.conf.\r\n\r\nPreview \"screenshot\" here: http:\/\/www.sentia.org\/downloads\/pf.conf.html","install_details":"Drop it in your syntax directory.  Type ':setf pf'.\r\n\r\nOr make vim autodetect it by having this in ~\/.vim\/filetypes.vim:\r\naugroup filetypedetect\r\nau BufNewFile,BufRead pf.conf   setf pf\r\nau BufNewFile,BufRead pf.conf.* setf pf\r\naugroup END\r\n\r\n","5":"Drop it in your syntax directory.  Type ':setf pf'.\r\n\r\nOr make vim autodetect it by having this in ~\/.vim\/filetypes.vim:\r\naugroup filetypedetect\r\nau BufNewFile,BufRead pf.conf   setf pf\r\nau BufNewFile,BufRead pf.conf.* setf pf\r\naugroup END\r\n\r\n","first_name":"Camiel","6":"Camiel","last_name":"Dobbelaar","7":"Dobbelaar","releases":[{"0":"341","vim_version":"6.0","1":"6.0","script_version":"1.3","2":"1.3","version_comment":"- altq and table statements\r\n- shorthands: 10\/8, 172.16\/12\r\n- folding (use ###> for sections and ##> for subsections)","3":"- altq and table statements\r\n- shorthands: 10\/8, 172.16\/12\r\n- folding (use ###> for sections and ##> for subsections)","package":"pf.vim","4":"pf.vim","src_id":"1762","5":"1762","creation_date":"1046067889","6":"1046067889"},{"0":"341","vim_version":"6.0","1":"6.0","script_version":"1.2","2":"1.2","version_comment":"Remove highlighting of erroneous {, it is too error-prone.","3":"Remove highlighting of erroneous {, it is too error-prone.","package":"pf.vim","4":"pf.vim","src_id":"1399","5":"1399","creation_date":"1037078288","6":"1037078288"},{"0":"341","vim_version":"6.0","1":"6.0","script_version":"1.1","2":"1.1","version_comment":"Supports IPv6 now.  Plus most-well-known services.  Strings can now be single quoted too.  Improved matching of assignment.","3":"Supports IPv6 now.  Plus most-well-known services.  Strings can now be single quoted too.  Improved matching of assignment.","package":"pf.vim","4":"pf.vim","src_id":"1371","5":"1371","creation_date":"1036402752","6":"1036402752"},{"0":"341","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"pf.vim","4":"pf.vim","src_id":"1015","5":"1015","creation_date":"1026471832","6":"1026471832"}]},"340":{"script_id":"340","0":"340","script_name":"tforge.vim","1":"tforge.vim","script_type":"syntax","2":"syntax","summary":"Text::Forge syntax file","3":"Text::Forge syntax file","description":"This is the syntax file for Text::Forge templates. See http:\/\/text-forge.sf.net\/ for more info on what Text::Forge is. This depends on a good html and perl syntax file, which comes with the default vim distribution.","4":"This is the syntax file for Text::Forge templates. See http:\/\/text-forge.sf.net\/ for more info on what Text::Forge is. This depends on a good html and perl syntax file, which comes with the default vim distribution.","install_details":"1) Move tforge.vim to your syntax directory (usually at $VIMRUNTIME\/syntax\/).\r\n\r\n2) Add a few line to your filetype.vim script (usually at $VIMRUNTIME\/filetype.vim):\r\n\\\" Text::Forge\r\nau BufNewFile,BufRead *.tf setf tforge\r\n\r\nIf you are editing a file that doesn\\'t have \\\".tf\\\" on the end, then you can just do this to get the highlighting:\r\n:setf tforge\r\n","5":"1) Move tforge.vim to your syntax directory (usually at $VIMRUNTIME\/syntax\/).\r\n\r\n2) Add a few line to your filetype.vim script (usually at $VIMRUNTIME\/filetype.vim):\r\n\\\" Text::Forge\r\nau BufNewFile,BufRead *.tf setf tforge\r\n\r\nIf you are editing a file that doesn\\'t have \\\".tf\\\" on the end, then you can just do this to get the highlighting:\r\n:setf tforge\r\n","first_name":"Jonathan","6":"Jonathan","last_name":"Gardner","7":"Gardner","releases":[{"0":"340","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"tforge.vim","4":"tforge.vim","src_id":"1013","5":"1013","creation_date":"1026390467","6":"1026390467"}]},"339":{"script_id":"339","0":"339","script_name":"ASP maps","1":"ASP maps","script_type":"ftplugin","2":"ftplugin","summary":"Maps to facilitate coding in ASP","3":"Maps to facilitate coding in ASP","description":"Based intially on Gavin Sinclair's Java script (vimscript #266), these are mappings to facilitate coding in VBScript ASP.\r\n\r\nExamples of use:\r\n\r\nTo get:\r\n<%\r\nResponse.Write \"SomeText\"\r\n%>\r\nIn insert mode you type:\r\n,%,r,wSomeText\r\n\r\nTo get:\r\nIf Trim(Request.QueryString(\"option\")) then\r\nEnd If\r\nIn insert mode you type:\r\n:i<Ctrl+f>t,R,qoption\r\n\r\nYou have:\r\nstrOption = Request(\"option\")\r\nAnd you want:\r\nstrOption = Trim(Request(\"option\"))\r\nYou mark Request(\"option\") in visual mode and press <Ctrl+f>t\r\n\r\n\r\n\r\nI will be adding more soon.","4":"Based intially on Gavin Sinclair's Java script (vimscript #266), these are mappings to facilitate coding in VBScript ASP.\r\n\r\nExamples of use:\r\n\r\nTo get:\r\n<%\r\nResponse.Write \"SomeText\"\r\n%>\r\nIn insert mode you type:\r\n,%,r,wSomeText\r\n\r\nTo get:\r\nIf Trim(Request.QueryString(\"option\")) then\r\nEnd If\r\nIn insert mode you type:\r\n:i<Ctrl+f>t,R,qoption\r\n\r\nYou have:\r\nstrOption = Request(\"option\")\r\nAnd you want:\r\nstrOption = Trim(Request(\"option\"))\r\nYou mark Request(\"option\") in visual mode and press <Ctrl+f>t\r\n\r\n\r\n\r\nI will be adding more soon.","install_details":"just drop the file in your ftplugin dir.","5":"just drop the file in your ftplugin dir.","first_name":"Ariel","6":"Ariel","last_name":"Arjona","7":"Arjona","releases":[{"0":"339","vim_version":"6.0","1":"6.0","script_version":"0.3","2":"0.3","version_comment":"* Added more flow control statements\r\n* Added more visual selection wrapping of VBScript functions","3":"* Added more flow control statements\r\n* Added more visual selection wrapping of VBScript functions","package":"aspvbs.vim","4":"aspvbs.vim","src_id":"1024","5":"1024","creation_date":"1026894370","6":"1026894370"},{"0":"339","vim_version":"6.0","1":"6.0","script_version":"0.2","2":"0.2","version_comment":"Added wrapping of VBScript functions such as Trim() around visually selected text.","3":"Added wrapping of VBScript functions such as Trim() around visually selected text.","package":"aspvbs.vim","4":"aspvbs.vim","src_id":"1018","5":"1018","creation_date":"1026719340","6":"1026719340"},{"0":"339","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"aspvbs.vim","4":"aspvbs.vim","src_id":"1011","5":"1011","creation_date":"1026374349","6":"1026374349"}]},"338":{"script_id":"338","0":"338","script_name":"vtags_def","1":"vtags_def","script_type":"utility","2":"utility","summary":"vtags language definitions","3":"vtags language definitions","description":"VTags language definitions script.\r\nGet vtags.vim and this script.\r\n\r\nThis script does not do anything on it's own.\r\nRequired by: vimscript #337 (vtags)","4":"VTags language definitions script.\r\nGet vtags.vim and this script.\r\n\r\nThis script does not do anything on it's own.\r\nRequired by: vimscript #337 (vtags)","install_details":":source vtags_def.vim\r\n:source vtags.vim","5":":source vtags_def.vim\r\n:source vtags.vim","first_name":"Little","6":"Little","last_name":"Dragon","7":"Dragon","releases":[{"0":"338","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"vtags_def.vim","4":"vtags_def.vim","src_id":"1010","5":"1010","creation_date":"1026357098","6":"1026357098"}]},"337":{"script_id":"337","0":"337","script_name":"vtags","1":"vtags","script_type":"utility","2":"utility","summary":"tags file generator","3":"tags file generator","description":"VTags is a tags file generator, written entirely in Vim.\r\n\r\nIt currently supports only the PHP and Vim languages, but adding a new\r\nlanguage should be trivial. \r\n\r\nThe speed is not one of the best around yet, but I'm working on this.\r\n\r\nThis one being the first release, it's quite in alpha stage. The\r\nlanguage definitions are experimental, to verify that the parsing engine\r\nworks. The parser only works on full lines, so if a line contains more,\r\nsay, function definitions, only the first one will be taken. I will be\r\nworking on supporting multiple definitions in one line, but _after_\r\nI get the speed fixed :)\r\nIt's the first unstable slow alpha testing thing. Be kind with me ;)\r\n\r\nAny feedback would be very much appreciated.\r\n\r\nRequires: vimscript #338 (vtags_def)","4":"VTags is a tags file generator, written entirely in Vim.\r\n\r\nIt currently supports only the PHP and Vim languages, but adding a new\r\nlanguage should be trivial. \r\n\r\nThe speed is not one of the best around yet, but I'm working on this.\r\n\r\nThis one being the first release, it's quite in alpha stage. The\r\nlanguage definitions are experimental, to verify that the parsing engine\r\nworks. The parser only works on full lines, so if a line contains more,\r\nsay, function definitions, only the first one will be taken. I will be\r\nworking on supporting multiple definitions in one line, but _after_\r\nI get the speed fixed :)\r\nIt's the first unstable slow alpha testing thing. Be kind with me ;)\r\n\r\nAny feedback would be very much appreciated.\r\n\r\nRequires: vimscript #338 (vtags_def)","install_details":"1. Get the vtags_def.vim script, containing language definitions.\r\n2. Get this script.\r\n3. Source them both, in the following order:\r\n   :source vtags_def.vim\r\n   :source vtags.vim\r\n","5":"1. Get the vtags_def.vim script, containing language definitions.\r\n2. Get this script.\r\n3. Source them both, in the following order:\r\n   :source vtags_def.vim\r\n   :source vtags.vim\r\n","first_name":"Little","6":"Little","last_name":"Dragon","7":"Dragon","releases":[{"0":"337","vim_version":"6.0","1":"6.0","script_version":"0.1.1","2":"0.1.1","version_comment":"Fixed some Windows bugs.","3":"Fixed some Windows bugs.","package":"vtags.vim","4":"vtags.vim","src_id":"1014","5":"1014","creation_date":"1026397442","6":"1026397442"}]},"336":{"script_id":"336","0":"336","script_name":"lh-cpp","1":"lh-cpp","script_type":"ftplugin","2":"ftplugin","summary":"C++ (and C) ftplugins","3":"C++ (and C) ftplugins","description":"This package contains several ftplugins addressed at the edition of C and C++ files.\r\n\r\nThe (ft)plugins suite is maintained on google-code: https:\/\/github.com\/LucHermitte\/lh-cpp","4":"This package contains several ftplugins addressed at the edition of C and C++ files.\r\n\r\nThe (ft)plugins suite is maintained on google-code: https:\/\/github.com\/LucHermitte\/lh-cpp","install_details":"As the plugin have many dependencies, use vim-addon-manager to install it\r\n   :UpdateAddons lh-cpp\r\n\r\nFor other methods, check https:\/\/github.com\/LucHermitte\/lh-cpp#installation","5":"As the plugin have many dependencies, use vim-addon-manager to install it\r\n   :UpdateAddons lh-cpp\r\n\r\nFor other methods, check https:\/\/github.com\/LucHermitte\/lh-cpp#installation","first_name":"Luc","6":"Luc","last_name":"Hermitte","7":"Hermitte","releases":[{"0":"336","vim_version":"6.0","1":"6.0","script_version":"20040316","2":"20040316","version_comment":"Many things have been enhanced. Several more options to tune the mappings. More complete documentation. Check the changelog for more info.","3":"Many things have been enhanced. Several more options to tune the mappings. More complete documentation. Check the changelog for more info.","package":"lh-cpp.tar.gz","4":"lh-cpp.tar.gz","src_id":"2848","5":"2848","creation_date":"1079808668","6":"1079808668"},{"0":"336","vim_version":"6.0","1":"6.0","script_version":"1.3","2":"1.3","version_comment":"Some annoying bugs fixed regarding Triggers.vim and pathnames ; folding enhanced ; documentation updated ; facilities to jump to functions (member or not) implementations, if the implementation does not exist yet, a default one is provided -- cf VIM TIP#135 ; plus some other minor bonuses.","3":"Some annoying bugs fixed regarding Triggers.vim and pathnames ; folding enhanced ; documentation updated ; facilities to jump to functions (member or not) implementations, if the implementation does not exist yet, a default one is provided -- cf VIM TIP#135 ; plus some other minor bonuses.","package":"lh-cpp.tar.gz","4":"lh-cpp.tar.gz","src_id":"1287","5":"1287","creation_date":"1034108505","6":"1034108505"},{"0":"336","vim_version":"6.0","1":"6.0","script_version":"1.2","2":"1.2","version_comment":"Documentation added ; dependencies simplified : it will be easier to use only some scripts and not others.","3":"Documentation added ; dependencies simplified : it will be easier to use only some scripts and not others.","package":"lh-cpp.tar.gz","4":"lh-cpp.tar.gz","src_id":"1012","5":"1012","creation_date":"1026376004","6":"1026376004"},{"0":"336","vim_version":"6.0","1":"6.0","script_version":"1.1","2":"1.1","version_comment":"Triggers.vim has been fixed and should not cause troubles anymore.","3":"Triggers.vim has been fixed and should not cause troubles anymore.","package":"lh-cpp.tar.gz","4":"lh-cpp.tar.gz","src_id":"1008","5":"1008","creation_date":"1026286645","6":"1026286645"},{"0":"336","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"lh-cpp.tar.gz","4":"lh-cpp.tar.gz","src_id":"1004","5":"1004","creation_date":"1026235694","6":"1026235694"}]},"335":{"script_id":"335","0":"335","script_name":"bw.vim","1":"bw.vim","script_type":"color scheme","2":"color scheme","summary":"Black and White cterm color scheme","3":"Black and White cterm color scheme","description":"This color scheme mimics vim's default behavior on a non-color terminal (like vt100), in a color terminal (like xterm, rxvt, etc.) Great for if you have a complex colorful background image and transparent terminals.\r\n\r\nScreenshot: http:\/\/hans.fugal.net\/vim\/colors\/bw.vim.html","4":"This color scheme mimics vim's default behavior on a non-color terminal (like vt100), in a color terminal (like xterm, rxvt, etc.) Great for if you have a complex colorful background image and transparent terminals.\r\n\r\nScreenshot: http:\/\/hans.fugal.net\/vim\/colors\/bw.vim.html","install_details":"put in vim colors directory (~\/.vim\/colors | <your-vim-dir>\\vimfiles\\colors)","5":"put in vim colors directory (~\/.vim\/colors | <your-vim-dir>\\vimfiles\\colors)","first_name":"Hans","6":"Hans","last_name":"Fugal","7":"Fugal","releases":[{"0":"335","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"bw.vim","4":"bw.vim","src_id":"1003","5":"1003","creation_date":"1026234283","6":"1026234283"}]},"334":{"script_id":"334","0":"334","script_name":"QuickAscii","1":"QuickAscii","script_type":"utility","2":"utility","summary":"Quick adding of characters not on your keyboard.","3":"Quick adding of characters not on your keyboard.","description":"Yet another ASCII table plugin :). I often need to insert some high-ASCII character that my keymap doesn't allow to write and none of the *ASCII plugins I saw was so easy and quick to use, so I wrote my own. It's my first plugin for VIM and I welcome any bug reports, ideas and suggestions.\r\n\r\nSince version 2.0 it has ability to use any number of intervals to display and  to use any file for character input. UTF8 is supported as well.","4":"Yet another ASCII table plugin :). I often need to insert some high-ASCII character that my keymap doesn't allow to write and none of the *ASCII plugins I saw was so easy and quick to use, so I wrote my own. It's my first plugin for VIM and I welcome any bug reports, ideas and suggestions.\r\n\r\nSince version 2.0 it has ability to use any number of intervals to display and  to use any file for character input. UTF8 is supported as well.","install_details":"Just put this file (qascii.vim) into your plugin directory or put it anywhere and source it (replace {YOUR-PATH} with real path, of course :)\r\n:source {YOUR-PATH}\/qascii.vim\r\n\r\nIt's highly recommended to create a mapping afterwards (see Usage in comments of script itself).\r\n","5":"Just put this file (qascii.vim) into your plugin directory or put it anywhere and source it (replace {YOUR-PATH} with real path, of course :)\r\n:source {YOUR-PATH}\/qascii.vim\r\n\r\nIt's highly recommended to create a mapping afterwards (see Usage in comments of script itself).\r\n","first_name":"Peter","6":"Peter","last_name":"Valach","7":"Valach","releases":[{"0":"334","vim_version":"6.0","1":"6.0","script_version":"2.0","2":"2.0","version_comment":"- Any file can be used as input (new function).\r\n- Any number of intervals can now be used (in the old function :).\r\n- Lots of internal changes.","3":"- Any file can be used as input (new function).\r\n- Any number of intervals can now be used (in the old function :).\r\n- Lots of internal changes.","package":"qascii.vim","4":"qascii.vim","src_id":"1448","5":"1448","creation_date":"1037848815","6":"1037848815"},{"0":"334","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"qascii.vim","4":"qascii.vim","src_id":"999","5":"999","creation_date":"1026194614","6":"1026194614"}]},"333":{"script_id":"333","0":"333","script_name":"cream-progressbar","1":"cream-progressbar","script_type":"utility","2":"utility","summary":"draw a progress bar in the command line","3":"draw a progress bar in the command line","description":"\r\nA function that, when called, draws a progress bar in the command line:\r\n\r\n    Loading file... [####################             ] 65%\r\n\r\nDisplays and allows options to:\r\n  1. Display the progress through RPM-like characters\r\n  2. Display an initial description string\r\n  3. Allows selection of the character used for the bar\r\n  4. Optionally, allows any bar length (default is window width)\r\n\r\nJust use a call such as:\r\n  call ProgressBar( 65, \"Loading file...\", \"#\", 0 )\r\n\r\n\r\nThis is one of many custom utilities and functions for gVim from the Cream project (http:\/\/cream.sourceforge.net), a configuration of Vim for those of us familiar with Apple and Windows software. \r\n\r\n","4":"\r\nA function that, when called, draws a progress bar in the command line:\r\n\r\n    Loading file... [####################             ] 65%\r\n\r\nDisplays and allows options to:\r\n  1. Display the progress through RPM-like characters\r\n  2. Display an initial description string\r\n  3. Allows selection of the character used for the bar\r\n  4. Optionally, allows any bar length (default is window width)\r\n\r\nJust use a call such as:\r\n  call ProgressBar( 65, \"Loading file...\", \"#\", 0 )\r\n\r\n\r\nThis is one of many custom utilities and functions for gVim from the Cream project (http:\/\/cream.sourceforge.net), a configuration of Vim for those of us familiar with Apple and Windows software. \r\n\r\n","install_details":"\r\nSimply copy this file and paste it into your vimrc. Or you can drop the entire file into your plugins directory. Or you can place it into another vim file you intend on loading before calling it.\r\n\r\n","5":"\r\nSimply copy this file and paste it into your vimrc. Or you can drop the entire file into your plugins directory. Or you can place it into another vim file you intend on loading before calling it.\r\n\r\n","first_name":"Steve","6":"Steve","last_name":"Hall","7":"Hall","releases":[{"0":"333","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"cream-progressbar.vim","4":"cream-progressbar.vim","src_id":"993","5":"993","creation_date":"1026074467","6":"1026074467"}]},"332":{"script_id":"332","0":"332","script_name":"prt_hdr","1":"prt_hdr","script_type":"utility","2":"utility","summary":"Alternate page header printing when PostScript printing.","3":"Alternate page header printing when PostScript printing.","description":"These files enable you to have page headers printed differently. Styles available include underlined, gray background, and in a box.\r\n\r\nTo select the style you want you will need to edit the file and comment out 1 line and uncomment another. See comments in the file (lines beginning with %).  There is no control from within VIM short of editing this file.\r\n\r\nThis file will only work if you are printing headers (i.e. header in printoptions has a value of 1 or more) and that the header fits on a single line. Otherwise the header style will be applied to the first line of text on each page.","4":"These files enable you to have page headers printed differently. Styles available include underlined, gray background, and in a box.\r\n\r\nTo select the style you want you will need to edit the file and comment out 1 line and uncomment another. See comments in the file (lines beginning with %).  There is no control from within VIM short of editing this file.\r\n\r\nThis file will only work if you are printing headers (i.e. header in printoptions has a value of 1 or more) and that the header fits on a single line. Otherwise the header style will be applied to the first line of text on each page.","install_details":"For VIM 6.2 - download prolog.ps into a directory called print in your runtimepath.\r\n\r\nFor VIM 6.0 and 6.1 - download procset.ps, then backup $VIMRUNTIME\/procset.ps in case you have problems and want to get back to a known good version.\r\n\r\nThen copy the downloaded file to $VIMRUNTIME.  It will be used the next time you use the :hardcopy command.\r\n","5":"For VIM 6.2 - download prolog.ps into a directory called print in your runtimepath.\r\n\r\nFor VIM 6.0 and 6.1 - download procset.ps, then backup $VIMRUNTIME\/procset.ps in case you have problems and want to get back to a known good version.\r\n\r\nThen copy the downloaded file to $VIMRUNTIME.  It will be used the next time you use the :hardcopy command.\r\n","first_name":"Mike","6":"Mike","last_name":"Williams","7":"Williams","releases":[{"0":"332","vim_version":"6.0","1":"6.0","script_version":"2.0","2":"2.0","version_comment":"New version of file for alternate page header printing for VIM 6.2. This version needs to exist in a directory called print in your runtimepath. Otherwise, instructions for use are as before.","3":"New version of file for alternate page header printing for VIM 6.2. This version needs to exist in a directory called print in your runtimepath. Otherwise, instructions for use are as before.","package":"prolog.ps","4":"prolog.ps","src_id":"2036","5":"2036","creation_date":"1054547025","6":"1054547025"},{"0":"332","vim_version":"6.0","1":"6.0","script_version":"1.1","2":"1.1","version_comment":"Whoops, finger trouble. Fix PS error with default page header code. Sorry.","3":"Whoops, finger trouble. Fix PS error with default page header code. Sorry.","package":"procset.ps","4":"procset.ps","src_id":"991","5":"991","creation_date":"1025762910","6":"1025762910"}]},"330":{"script_id":"330","0":"330","script_name":"code2html","1":"code2html","script_type":"utility","2":"utility","summary":"Generate HTML or XHTML+CSS from a Vim buffer using the syntax-hili colorscheme","3":"Generate HTML or XHTML+CSS from a Vim buffer using the syntax-hili colorscheme","description":"WHAT:\r\nThis is a substantially modified rewrite of the \"2html.vim\" script that's found in the Vim runtime \"syntax\" directory, and used exactly as that file is used (i.e.): \r\n\r\n  :so[urce] ~\/scripts\/code2html.vim\r\n\r\nRECENT:\r\n24 Sep 2008 - ATTENTION PLEASE! There will be no more revisions to this script under *this* name.  Because there is a collision between the name \"code2html[.vim]\" and another F\/LOSS software project by that name, I am renaming this script to \"buf2html[.vim]\".  THE NEW SCRIPT IS LOCATED AT http:\/\/www.vim.org\/scripts\/script.php?script_id=2384.\r\n\r\nWHO:\r\nBased on work by Bram Moolenaar and David Nečas (\"Yeti\"), now maintained by Soren Andersen.  Past contributions by Christian Hujer.       \r\n\r\nWHY:\r\nThe main thing this module changes is the automatic addition of some simple css code to specify the fixed-width (monospace) font you want the HTML-ized syntax-colored code to be rendered in -- IF any of those fonts are findable by the reader's WWW browser. This provides an HTML rendering in modern browsers that can surprisingly closely replicate the appearance in the GVIM editor.\r\n\r\nINSTALL:\r\nSave this vim file to a directory convenient for you. Do *not* place it in a runtime plugin directory; you do not want it to be evaluated when opening any file for editing.  This is a script but not a plugin.  The author tends to have a ~\/scripts dir on his accounts, and places this file there, alongside awk, sed, perl and other such script\/programs.\r\n\r\nFEATURES:\r\nThe code will find out what \"guifont\" value the user is using, and convert that specification (usually set in \".gvimrc\") to a css font spec. There are also changes to output an up-to-date xml -type header (DTD) by Christian Hujer.\r\n\r\nIt will also create a \"<DIV>\" section containing the main \"<PRE>\" block. To understand why this is good, running a test example shows better than a thousand words. It allows specification of the font in css, as well as some other things, like padding of the contents of the \"<PRE>\" and some differing bgcolor for the document as a whole vs the \"code\" content. This is all primarily a matter of personal preference of course.\r\n\r\nExamples of source highlighted with this script can be found at my home page at http:\/\/intrepid.perlmonk.org\r\n\r\nIf you view the output of this script -- run on your GVIM on one of your own source code documents, and viewed in a competent css-supporting browser -- you may find that the document looks so identical to your GVIM display that you'll be tempted to start sending vim commands to your browser ;-). \r\n\r\nUPDATE: 22 Oct 2002\r\nIn a little while a new version will be uploaded (presently I am having Christian check our merged changes before we commit to releasing this major update).\r\n  * Made output of DTD not dependant on whether user has html_use_css=1.\r\n  * Made significant changes to program flow, fixed a problem with output of the style definitions in the header STYLE block.\r\n  * Added several new variables that the user can set to change the behavior of the script.\r\n\r\nAll in all, the program is more robust, outputs more correct (according to latest W3C standards) HTML, script has more configurability, and the output is prettier (as source).\r\n\r\nUPDATE: Aug 08 2002 20:32:28 EDT\r\nSorry -- did not have time right now to properly document ALL the changes in v1.1, but these include:\r\n  * fixed the stupid \".main_code\" bug (should have written to the head style block \"#main-code\" instead of \".main-code\"). aargh.\r\n  * added a new function to create the CSS font specifier, it is doing a much better job than the previous code\r\n  * the output is much more cosmetically proper.\r\nThank you very much to all the people who downloaded version 1.0. Please give the update a try -- it is much improved.\r\n","4":"WHAT:\r\nThis is a substantially modified rewrite of the \"2html.vim\" script that's found in the Vim runtime \"syntax\" directory, and used exactly as that file is used (i.e.): \r\n\r\n  :so[urce] ~\/scripts\/code2html.vim\r\n\r\nRECENT:\r\n24 Sep 2008 - ATTENTION PLEASE! There will be no more revisions to this script under *this* name.  Because there is a collision between the name \"code2html[.vim]\" and another F\/LOSS software project by that name, I am renaming this script to \"buf2html[.vim]\".  THE NEW SCRIPT IS LOCATED AT http:\/\/www.vim.org\/scripts\/script.php?script_id=2384.\r\n\r\nWHO:\r\nBased on work by Bram Moolenaar and David Nečas (\"Yeti\"), now maintained by Soren Andersen.  Past contributions by Christian Hujer.       \r\n\r\nWHY:\r\nThe main thing this module changes is the automatic addition of some simple css code to specify the fixed-width (monospace) font you want the HTML-ized syntax-colored code to be rendered in -- IF any of those fonts are findable by the reader's WWW browser. This provides an HTML rendering in modern browsers that can surprisingly closely replicate the appearance in the GVIM editor.\r\n\r\nINSTALL:\r\nSave this vim file to a directory convenient for you. Do *not* place it in a runtime plugin directory; you do not want it to be evaluated when opening any file for editing.  This is a script but not a plugin.  The author tends to have a ~\/scripts dir on his accounts, and places this file there, alongside awk, sed, perl and other such script\/programs.\r\n\r\nFEATURES:\r\nThe code will find out what \"guifont\" value the user is using, and convert that specification (usually set in \".gvimrc\") to a css font spec. There are also changes to output an up-to-date xml -type header (DTD) by Christian Hujer.\r\n\r\nIt will also create a \"<DIV>\" section containing the main \"<PRE>\" block. To understand why this is good, running a test example shows better than a thousand words. It allows specification of the font in css, as well as some other things, like padding of the contents of the \"<PRE>\" and some differing bgcolor for the document as a whole vs the \"code\" content. This is all primarily a matter of personal preference of course.\r\n\r\nExamples of source highlighted with this script can be found at my home page at http:\/\/intrepid.perlmonk.org\r\n\r\nIf you view the output of this script -- run on your GVIM on one of your own source code documents, and viewed in a competent css-supporting browser -- you may find that the document looks so identical to your GVIM display that you'll be tempted to start sending vim commands to your browser ;-). \r\n\r\nUPDATE: 22 Oct 2002\r\nIn a little while a new version will be uploaded (presently I am having Christian check our merged changes before we commit to releasing this major update).\r\n  * Made output of DTD not dependant on whether user has html_use_css=1.\r\n  * Made significant changes to program flow, fixed a problem with output of the style definitions in the header STYLE block.\r\n  * Added several new variables that the user can set to change the behavior of the script.\r\n\r\nAll in all, the program is more robust, outputs more correct (according to latest W3C standards) HTML, script has more configurability, and the output is prettier (as source).\r\n\r\nUPDATE: Aug 08 2002 20:32:28 EDT\r\nSorry -- did not have time right now to properly document ALL the changes in v1.1, but these include:\r\n  * fixed the stupid \".main_code\" bug (should have written to the head style block \"#main-code\" instead of \".main-code\"). aargh.\r\n  * added a new function to create the CSS font specifier, it is doing a much better job than the previous code\r\n  * the output is much more cosmetically proper.\r\nThank you very much to all the people who downloaded version 1.0. Please give the update a try -- it is much improved.\r\n","install_details":"There is no name-clash at present with any syntax file shipped in the VIM distro, so it could be placed in $VIMRUNTIME\/syntax. But I prefer and recommend that you place it in an easy-to-remember location such as ~\/scripts\/.\r\n\r\nYou will also most likely want to \":let html_use_css = 1\" before :source'ing this module, or there will be little point in it at all, because most of the changes go into action in the doc head '<STYLE ...' block.  Set that in your ~\/.vimrc, -or- do :let g:html_use_css=1 | source ~\/scripts\/code2html.vim\r\n\r\nA few notes on system fixed-width fonts, ADDED 06 Jul 2002:\r\nWell, about fonts, not much can be said that isn't prefaced with the acknowledgement that the bottom line is personal taste. I am sure that fonts have been discussed by VIMmers many times before.\r\n\r\nAnyway I wanted to note that the choices I make in my \"_vimrc\" reflect my personal tastes and knowledge, YMMV. However as it may be helpful for some readers I want to show what my _vimrc contains now:\r\n\r\n  :set guifont=anonymous:h8,lucida_console:h9,andale_mono:h10,lucida_sans_typewriter:h9,\r\n  :set guifont+=onuava:h9,crystal:h9,monospace_821_bt:h9,courier_new:h9\r\n\r\nThe first entry, \"Anonymous\", is a new discovery that I am excited about. It is a monospaced (fixed-width) font that looks very good and is unbelievably readable in my Win32-GVIM display at a 8-pixel height setting (\":h8\") whereas I dare not go lower than \":h9\" with my second fav, Lucida Console (which is a very good font and slightly nudges out the popular \"Andale Mono\" at lowest point sizes, in my preference).\r\n\r\nThe Windows version of \"Anonymous\" is presently at\r\n http:\/\/www.ms-studio.com\/FontSales\/Resources\/AnonymousTT.zip\r\n linked to from  http:\/\/www.ms-studio.com\/FontSales\/anonymous.html\r\n\r\n\"Anonymous\" is released as Copyrighted freeware (I didn't read any detailed licensing terms but the sense one gets from that terminology is that it's likely to be pretty much compatible with the intent of most Open Source software licensing philosophies). I can definitely recommend that readers give this font a try.\r\n\r\nIn any case, the point of setting as many possible alternates in _gvimrc (or wherever you find it convenient to do so) is to hit as many target systems as possible without having the browser default to it's unqualified default monospace font. Of course for *serious* Web users that setting may already be those users' strong personal preference, but this is likely to be true in only a small minority of cases (any anyway such users will also often be using WWW clients that can override our specification with a user setting, such as Opera, if they object to our choice).\r\n\r\nPlease read the comments in the script source code for a more detailed explanation of Usage.","5":"There is no name-clash at present with any syntax file shipped in the VIM distro, so it could be placed in $VIMRUNTIME\/syntax. But I prefer and recommend that you place it in an easy-to-remember location such as ~\/scripts\/.\r\n\r\nYou will also most likely want to \":let html_use_css = 1\" before :source'ing this module, or there will be little point in it at all, because most of the changes go into action in the doc head '<STYLE ...' block.  Set that in your ~\/.vimrc, -or- do :let g:html_use_css=1 | source ~\/scripts\/code2html.vim\r\n\r\nA few notes on system fixed-width fonts, ADDED 06 Jul 2002:\r\nWell, about fonts, not much can be said that isn't prefaced with the acknowledgement that the bottom line is personal taste. I am sure that fonts have been discussed by VIMmers many times before.\r\n\r\nAnyway I wanted to note that the choices I make in my \"_vimrc\" reflect my personal tastes and knowledge, YMMV. However as it may be helpful for some readers I want to show what my _vimrc contains now:\r\n\r\n  :set guifont=anonymous:h8,lucida_console:h9,andale_mono:h10,lucida_sans_typewriter:h9,\r\n  :set guifont+=onuava:h9,crystal:h9,monospace_821_bt:h9,courier_new:h9\r\n\r\nThe first entry, \"Anonymous\", is a new discovery that I am excited about. It is a monospaced (fixed-width) font that looks very good and is unbelievably readable in my Win32-GVIM display at a 8-pixel height setting (\":h8\") whereas I dare not go lower than \":h9\" with my second fav, Lucida Console (which is a very good font and slightly nudges out the popular \"Andale Mono\" at lowest point sizes, in my preference).\r\n\r\nThe Windows version of \"Anonymous\" is presently at\r\n http:\/\/www.ms-studio.com\/FontSales\/Resources\/AnonymousTT.zip\r\n linked to from  http:\/\/www.ms-studio.com\/FontSales\/anonymous.html\r\n\r\n\"Anonymous\" is released as Copyrighted freeware (I didn't read any detailed licensing terms but the sense one gets from that terminology is that it's likely to be pretty much compatible with the intent of most Open Source software licensing philosophies). I can definitely recommend that readers give this font a try.\r\n\r\nIn any case, the point of setting as many possible alternates in _gvimrc (or wherever you find it convenient to do so) is to hit as many target systems as possible without having the browser default to it's unqualified default monospace font. Of course for *serious* Web users that setting may already be those users' strong personal preference, but this is likely to be true in only a small minority of cases (any anyway such users will also often be using WWW clients that can override our specification with a user setting, such as Opera, if they object to our choice).\r\n\r\nPlease read the comments in the script source code for a more detailed explanation of Usage.","first_name":"S\u00c3\u00b6ren","6":"S\u00c3\u00b6ren","last_name":"Andersen","7":"Andersen","releases":[{"0":"330","vim_version":"6.0","1":"6.0","script_version":"1.51","2":"1.51","version_comment":"The .tar file contains code2html-1_51_vim.gz and code2html-1_51_vim.gz.asc (a PGP\/GnuPG signature for verifying the gzipped-script). I jumped version numbers, sorry.","3":"The .tar file contains code2html-1_51_vim.gz and code2html-1_51_vim.gz.asc (a PGP\/GnuPG signature for verifying the gzipped-script). I jumped version numbers, sorry.","package":"code2html-1_51_vim.tar","4":"code2html-1_51_vim.tar","src_id":"2227","5":"2227","creation_date":"1060670668","6":"1060670668"},{"0":"330","vim_version":"6.0","1":"6.0","script_version":"1.2","2":"1.2","version_comment":"More small bug-stomping + now adds a little note at page bottom -- \"made with VIM\" sort of thing.","3":"More small bug-stomping + now adds a little note at page bottom -- \"made with VIM\" sort of thing.","package":"code2html_vim.gz","4":"code2html_vim.gz","src_id":"1105","5":"1105","creation_date":"1028891572","6":"1028891572"},{"0":"330","vim_version":"6.0","1":"6.0","script_version":"1.1","2":"1.1","version_comment":"many \"robustifications\" and bug fixes.","3":"many \"robustifications\" and bug fixes.","package":"code2html_vim.gz","4":"code2html_vim.gz","src_id":"1093","5":"1093","creation_date":"1028827853","6":"1028827853"},{"0":"330","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"code2html.vim.gz","4":"code2html.vim.gz","src_id":"987","5":"987","creation_date":"1025716839","6":"1025716839"}]},"329":{"script_id":"329","0":"329","script_name":"cfengine syntax file","1":"cfengine syntax file","script_type":"syntax","2":"syntax","summary":"Syntax file for cfengine configuration files","3":"Syntax file for cfengine configuration files","description":"See http:\/\/www.cfengine.org for more information about cfengine","4":"See http:\/\/www.cfengine.org for more information about cfengine","install_details":"","5":"","first_name":"Marcus","6":"Marcus","last_name":"Spading","7":"Spading","releases":[{"0":"329","vim_version":"6.0","1":"6.0","script_version":"0.3","2":"0.3","version_comment":"Minor update:\r\n- added keywords\r\n- fixed some typos\r\n- thanks go to Brian Youngstrom for the patch","3":"Minor update:\r\n- added keywords\r\n- fixed some typos\r\n- thanks go to Brian Youngstrom for the patch","package":"cfengine.vim","4":"cfengine.vim","src_id":"2693","5":"2693","creation_date":"1075361397","6":"1075361397"},{"0":"329","vim_version":"6.0","1":"6.0","script_version":"0.2","2":"0.2","version_comment":"- cfservd keywords added\n- ip-addresses are recognized\n- fixed some typos","3":"- cfservd keywords added\n- ip-addresses are recognized\n- fixed some typos","package":"cfengine.vim","4":"cfengine.vim","src_id":"992","5":"992","creation_date":"1025962483","6":"1025962483"},{"0":"329","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"cfengine.vim","4":"cfengine.vim","src_id":"979","5":"979","creation_date":"1025640976","6":"1025640976"}]},"328":{"script_id":"328","0":"328","script_name":"Nightshimmer","1":"Nightshimmer","script_type":"color scheme","2":"color scheme","summary":"a darkblue scheme with shimmering colors","3":"a darkblue scheme with shimmering colors","description":"A calm, soothing color scheme for silent nights and other moments of magic. It reminds me a little of Monkey Island, or Sandman. Or something.\r\n\r\nHere's a screenshot: https:\/\/github.com\/niklasl\/vimheap\/wiki\/images\/nightshimmer.png\r\n\r\nEnjoy!\r\n","4":"A calm, soothing color scheme for silent nights and other moments of magic. It reminds me a little of Monkey Island, or Sandman. Or something.\r\n\r\nHere's a screenshot: https:\/\/github.com\/niklasl\/vimheap\/wiki\/images\/nightshimmer.png\r\n\r\nEnjoy!\r\n","install_details":"Simply drop this into your \"$HOME\/.vim\/colors\/\" and use \":colorscheme nightshimmer\". (Or just \":source\" it.)","5":"Simply drop this into your \"$HOME\/.vim\/colors\/\" and use \":colorscheme nightshimmer\". (Or just \":source\" it.)","first_name":"Niklas","6":"Niklas","last_name":"Lindstr\u00c3\u00b6m","7":"Lindstr\u00c3\u00b6m","releases":[{"0":"328","vim_version":"7.0","1":"7.0","script_version":"1.1","2":"1.1","version_comment":"Long overdue: generic improvements and highlights of new groups (for folds etc.).","3":"Long overdue: generic improvements and highlights of new groups (for folds etc.).","package":"nightshimmer.vim","4":"nightshimmer.vim","src_id":"14836","5":"14836","creation_date":"1295815651","6":"1295815651"},{"0":"328","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"nightshimmer-theme.vim","4":"nightshimmer-theme.vim","src_id":"978","5":"978","creation_date":"1025621016","6":"1025621016"}]},"327":{"script_id":"327","0":"327","script_name":"JHTML syntax file","1":"JHTML syntax file","script_type":"syntax","2":"syntax","summary":"Syntax file for ATG Dynamo's jhtml markup.","3":"Syntax file for ATG Dynamo's jhtml markup.","description":"Syntax file for the jhtml markup language created by ATG for their Java-based Dynamo Application Server. ","4":"Syntax file for the jhtml markup language created by ATG for their Java-based Dynamo Application Server. ","install_details":"","5":"","first_name":"Jon","6":"Jon","last_name":"Gubman","7":"Gubman","releases":[{"0":"327","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Fixed a few mixed case matches, provided a few more syntaxes","3":"Fixed a few mixed case matches, provided a few more syntaxes","package":"jhtml.vim","4":"jhtml.vim","src_id":"995","5":"995","creation_date":"1026123783","6":"1026123783"}]},"326":{"script_id":"326","0":"326","script_name":"PHPcollection","1":"PHPcollection","script_type":"utility","2":"utility","summary":"PHP Collection contains: compiler, ftplugin, script for K key, dicts","3":"PHP Collection contains: compiler, ftplugin, script for K key, dicts","description":"PHP Collection contains 3 files and 2 links:\r\ncompiler, ftplugin, script for use with 'keywordprg' and PHP\r\nmanual, links to vim dictionaries of PHP functions and prototypes.\r\n\r\nI. PHP compiler (cphp.vim)\r\nRequirements:\r\n1. PHP compiled as cgi\r\n2. bash\r\n3. grep compatible tool :help grep\r\n4. standard message error from PHP (it doesn't use debugger) :help\r\ncompiler\r\nHelp:\r\n:make <file_name> <QUERY_STRING>\r\n\r\nII. PHP ftplugin (php.vim)\r\nInspired by Christopher Swingley I add some things and put it in\r\nftplugin file.\r\nFirst part is ``objective'' and contains only important(?) settings. In\r\nsecond are some useful options commented by default.\r\n\r\nIII. Bash script for 'keywordprg' option. (phpmanual.sh)\r\nWritten by Leszek Krupinski <leszek@php.net> for use with K.\r\nDefault settings points to lynx and directory where Mkd8.2 puts\r\nphp-manual rpm.\r\n\r\nIV. Links. Both dictionaries where created by Leszek Krupinski\r\nDictionary of PHP functions:\r\nhttp:\/\/www.leon.w-wa.pl\/texts\/phpfunclist\r\nDictionary of PHP prototypes:\r\nhttp:\/\/www.leon.w-wa.pl\/texts\/phpproto\r\n\r\nThanks for Doug Kearns, Leszek Krupinski and Christopher Swingley\r\n\r\nAll faults are only mine.\r\n\r\nMikolaj Machowski\r\n<mikmach@wp.pl>\r\n","4":"PHP Collection contains 3 files and 2 links:\r\ncompiler, ftplugin, script for use with 'keywordprg' and PHP\r\nmanual, links to vim dictionaries of PHP functions and prototypes.\r\n\r\nI. PHP compiler (cphp.vim)\r\nRequirements:\r\n1. PHP compiled as cgi\r\n2. bash\r\n3. grep compatible tool :help grep\r\n4. standard message error from PHP (it doesn't use debugger) :help\r\ncompiler\r\nHelp:\r\n:make <file_name> <QUERY_STRING>\r\n\r\nII. PHP ftplugin (php.vim)\r\nInspired by Christopher Swingley I add some things and put it in\r\nftplugin file.\r\nFirst part is ``objective'' and contains only important(?) settings. In\r\nsecond are some useful options commented by default.\r\n\r\nIII. Bash script for 'keywordprg' option. (phpmanual.sh)\r\nWritten by Leszek Krupinski <leszek@php.net> for use with K.\r\nDefault settings points to lynx and directory where Mkd8.2 puts\r\nphp-manual rpm.\r\n\r\nIV. Links. Both dictionaries where created by Leszek Krupinski\r\nDictionary of PHP functions:\r\nhttp:\/\/www.leon.w-wa.pl\/texts\/phpfunclist\r\nDictionary of PHP prototypes:\r\nhttp:\/\/www.leon.w-wa.pl\/texts\/phpproto\r\n\r\nThanks for Doug Kearns, Leszek Krupinski and Christopher Swingley\r\n\r\nAll faults are only mine.\r\n\r\nMikolaj Machowski\r\n<mikmach@wp.pl>\r\n","install_details":"1. Rename cphp.vim as php.vim and place it in\r\n.vim\/compiler\/\r\n2. Place it in\r\n.vim\/ftplugin\/\r\n3. Make script executable and place it in eg.\r\n.vim\/external\/         (suggested in php.vim)\r\n4. You could place dictionaries in eg.\r\n.vim\/dictionaries\/     (suggested in php.vim)\r\n","5":"1. Rename cphp.vim as php.vim and place it in\r\n.vim\/compiler\/\r\n2. Place it in\r\n.vim\/ftplugin\/\r\n3. Make script executable and place it in eg.\r\n.vim\/external\/         (suggested in php.vim)\r\n4. You could place dictionaries in eg.\r\n.vim\/dictionaries\/     (suggested in php.vim)\r\n","first_name":"Mikolaj","6":"Mikolaj","last_name":"Machowski","7":"Machowski","releases":[{"0":"326","vim_version":"6.0","1":"6.0","script_version":"0.2","2":"0.2","version_comment":"Updated 2003-01-06 by Stephen Thorne <stephen@mu.com.au> to use php4's 'lint' filter, instead of executing a php file with a query string. The format of errors had changed since the original version too, so the error string was modified.\r\n","3":"Updated 2003-01-06 by Stephen Thorne <stephen@mu.com.au> to use php4's 'lint' filter, instead of executing a php file with a query string. The format of errors had changed since the original version too, so the error string was modified.\r\n","package":"phpcollection.zip","4":"phpcollection.zip","src_id":"1602","5":"1602","creation_date":"1041793590","6":"1041793590"},{"0":"326","vim_version":"6.0","1":"6.0","script_version":"0.1.1","2":"0.1.1","version_comment":"Small changes in README file:\r\nadded manual to compiler.","3":"Small changes in README file:\r\nadded manual to compiler.","package":"php.zip","4":"php.zip","src_id":"977","5":"977","creation_date":"1025611814","6":"1025611814"},{"0":"326","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"php.zip","4":"php.zip","src_id":"970","5":"970","creation_date":"1025536111","6":"1025536111"}]},"325":{"script_id":"325","0":"325","script_name":"JavaImp.vim","1":"JavaImp.vim","script_type":"utility","2":"utility","summary":"Insert and sort Java import statements, view JavaDoc from class name, and more.","3":"Insert and sort Java import statements, view JavaDoc from class name, and more.","description":"This script can generate a Java class name to package mapping file from multiple source paths.  Once you have create the mapping file,  you can use this file to insert import statements in your .java file using a simple key mapping.  It can also sort your imports too!  \r\n\r\nJavaImp can also be integrated with JavaDoc, where you can lookup APIs very quickly by just hitting a hot key on a class name.  This script can save the time you spent looking up docs and typing in routine import package names.  Give it a try!","4":"This script can generate a Java class name to package mapping file from multiple source paths.  Once you have create the mapping file,  you can use this file to insert import statements in your .java file using a simple key mapping.  It can also sort your imports too!  \r\n\r\nJavaImp can also be integrated with JavaDoc, where you can lookup APIs very quickly by just hitting a hot key on a class name.  This script can save the time you spent looking up docs and typing in routine import package names.  Give it a try!","install_details":"REQUIREMENTS:\r\n  - It's recommended that you have the Unix \"sort\" binary (or the Windows's\r\n  \"sort\" or cygwin's \"sort\" will do) in your path.   For the jar support you\r\n  also need to have the\r\n  \"jar\" binary in your path.\r\n  - To use JavaDoc viewing, you probably need to have a pager like \"w3m\" or\r\n  \"lynx\".  You can also use your usual web browser for this.  You do not\r\n  really need this if you do not use the JavaDoc viewing feature.\r\n\r\nUSAGE:\r\n  Put this file in your ~\/.vim\/plugin directory.\r\n\r\n  You need to set two global variables in your .vimrc in order for this to\r\n  work:\r\n\r\n      let g:JavaImpPaths = \"...\"\r\n      let g:JavaImpDataDir = \"...\"\r\n\r\n  The g:JavaImpPaths is a comma separated list of paths that point to the\r\n  roots of the 'com' or 'org' etc.\r\n\r\n  For example: if you have your Java source files in\r\n  \/project\/src\/java\/com\/blah and \/project2\/javasrc\/org\/blah...., you'll put\r\n  this in your .vimrc file:\r\n\r\n      let g:JavaImpPaths = \"\/project\/src\/java,\/project2\/javasrc\"\r\n\r\n  If there are too many paths, you can split them into separate lines:\r\n\r\n      let g:JavaImpPaths = \"\/project\/src\/java,\" .\r\n         \\ \"\/project2\/javasrc,\" .\r\n         \\ \"\/project3\/javasrc\"\r\n\r\n  Note: Don't forget the ',' to separate the paths.\r\n\r\n  If ',' is not convenient for you, set g:JavaImpPathSep to the\r\n  (single-character) separator you would like to use:\r\n\r\n      let g:JavaImpPathSep = ':'\r\n\r\n  The g:JavaImpDataDir is a directory that you use to store JavaImp\r\n  settings and cache files. Default is:\r\n\r\n      let g:JavaImpDataDir = $HOME . \"\/vim\/JavaImp\"\r\n\r\n  Note: Since version 2.1, the \"g:JavaImpDataDir\" variable replaces\r\n  \"g:JavaImpClassList\" and \"g:JavaImpJarCache\".  If \"g:JavaImpClassList\" and\r\n  \"g:JavaImpJarCache\" are not set, then they default to\r\n  \"g:JavaImpDataDir\/JavaImp.txt\" and \"g:JavaImpDataDir\/cache\/\" accordingly.\r\n  The files and directory will be created automatically when you generate\r\n  the JavaImp.txt file.  It's recommended that you to use the\r\n  g:JavaImpDataDir variable instead.\r\n\r\n  Now you are ready for some actions.  You can now do a:\r\n\r\n      :JavaImpGenerate or :JIG\r\n\r\n  If you have not created the directory for g:JavaImpDataDir yet, this will\r\n  create the appropriate paths.  JIG will go through your JavaImpPaths and\r\n  search for anything that ends with .java, .class, or .jar.  It'll then\r\n  write the mappings to the JavaImp.txt and\/or the cache files.\r\n  \r\n  After you've generated your JavaImp.txt file, move your cursor to a class name\r\n  in a Java file and do a:\r\n\r\n      :JavaImp or :JI\r\n\r\n  And the magic happens!  You'll realize that you have an extra import\r\n  statement inserted after the last import statement in the file.  It'll\r\n  also prompts you with duplicate class names and insert what you have\r\n  selected.  If the class name is already imported, it'll do nothing.  \r\n\r\n  Doing a:\r\n\r\n      :JavaImpSilent\r\n\r\n  will do a similar thing with less verbosity.  This is useful to be used in\r\n  another script.\r\n\r\n  You can also sort the import statements in the file by doing:\r\n\r\n      :JavaImpSort or :JIS\r\n\r\n  Source Viewing\r\n  --------------\r\n\r\n  JavaImp will try to find the source file of the class under your cursor\r\n  by:\r\n\r\n      :JavaImpFile or :JIF\r\n      \r\n  Doing a :JavaImpFileSplit or :JIFS will open a splitted window on the\r\n  file.\r\n\r\n  JavaDoc Viewing\r\n  ---------------\r\n  If you want to use the JavaDoc viewing feature for JavaImp, you should set\r\n  g:JavaImpDocPaths.  Similar to how you set the g:JavaImpPaths,\r\n  g:JavaImpDocPaths contains a list of root level directories that contains\r\n  your java docs.  This, together with a HTML pager (like w3m or lynx on\r\n  Unix), let you view the JavaDocs very quickly by just hitting :JID on a\r\n  class name.  For example, you can set:\r\n\r\n      let g:JavaImpDocPaths = \"\/usr\/java\/docs\/api,\" .\r\n         \\ \"\/project\/docs\/api\"\r\n\r\n  The default pager is set to:\r\n\r\n      let g:JavaImpDocViewer = \"w3m\"\r\n  \r\n  On windows, you can put iexplore.exe or mozilla.exe in your path and set\r\n  the g:JavaImpDocViewer to \"iexplore.exe\" or \"mozilla.exe\".  Note that\r\n  windows' shell and spaces in the path don't mix. Thus, given an absolute\r\n  path of the HTML viewer to g:JavaImpDocViewer may not work.\r\n\r\n  If you have your g:JavaImpDocPaths and g:JavaImpDocViewer set correctly\r\n  You can then do this with your cursor on a classname:\r\n\r\n      :JavaImpDoc or :JID \r\n\r\n  JavaImp will find your class accordingly and open the viewer to the\r\n  class based on the import list that you've generated by :JIG.  You can\r\n  also set in your java.vim  filetype plugin to get a similar man page\r\n  behavior by press \"K\":\r\n\r\n      nmap <buffer> K :JID<CR>\r\n\r\n  Other Settings\r\n  --------------\r\n  You can make the following settings in your .vimrc file:\r\n\r\n  (Deprecated in 2.1) The g:JavaImpClassList is a file you specify to store\r\n  the class mappings.  The default is set to:\r\n  \r\n      let g:JavaImpClassList = g:JavaImpDataDir . \"\/JavaImp.txt\"\r\n\r\n  (Deprecated in 2.1, enabled by default and set relative to the\r\n  g:JavaImpDataDir) It's recommended that you set a directory for the\r\n  caching result for your jar files.  JavaImp saves the result from each\r\n  \"jar\" command in this directory. The default is set to:\r\n\r\n      let g:JavaImpJarCache = g:JavaImpDataDir . \"\/cache\"\r\n\r\n  (In in 2.1, g:JavaImpSortBin is set to \"sort\", so this is disabled by\r\n  default) The sorting algorithm gives preferences to the java.* classes.\r\n  You can turn this behavior off by putting this in your .vimrc file.\r\n\r\n      let g:JavaImpSortJavaFirst = 0\r\n\r\n  NOTE: If you do not have a sort binary, set the following to \"\", and\r\n  JavaImp will use the pure Vim implementation.  However, if\r\n  JavaImpClassList gets too huge, the sorting might choke. If you\r\n  are on a unix machine or you have the sort binary in your path, it's\r\n  recommended that you set (or leave it as default):\r\n\r\n      let g:JavaImpSortBin = \"sort\" \r\n\r\n  By default, the sort algorithm will insert a blank line among package\r\n  group with package root for 2 similar levels.  For example, the import of\r\n  the following:\r\n\r\n      import java.util.List;\r\n      import org.apache.tools.zip.ZipEntry;\r\n      import javax.mail.search.MessageNumberTerm;\r\n      import java.util.Vector;\r\n      import javax.mail.Message;\r\n      import org.apache.tools.ant.types.ZipFileSet;\r\n\r\n  will become:\r\n\r\n      import java.util.List;\r\n      import java.util.Vector;\r\n\r\n      import javax.mail.Message;\r\n      import javax.mail.search.MessageNumberTerm;\r\n\r\n      import org.apache.tools.ant.types.ZipFileSet;\r\n      import org.apache.tools.zip.ZipEntry;\r\n\r\n  Note the classes that begins similar package root with two beginning\r\n  levels of package hierarchy are stuck together.  You can set the\r\n  g:JavaImpSortPkgSep to change this behavior.  The default\r\n  g:JavaImpSortPkgSep is set to 2.  Do not set it too high though for you'll\r\n  insert a blank line after each import.  If you do not want to insert blank\r\n  lines among the imports, set:\r\n\r\n      let g:JavaImpSortPkgSep = 0\r\n\r\n  Be warned that g:JavaImpSortRemoveEmpty has no effect if\r\n  g:JavaImpSortPkgSep is set.\r\n\r\n  Extras\r\n  ------\r\n  After you have generated the JavaImp.txt file by using :JIG, you can use\r\n  it as your dictionary for autocompletion.  For example, you can put the\r\n  following in your java.vim ftplugin (note here g:JavaImpDataDir is set\r\n  before running this):\r\n\r\n  exe \"setlocal dict=\" . g:JavaImpDataDir . \"\/JavaImp.txt\"\r\n  setlocal complete-=k\r\n  setlocal complete+=k\r\n  \r\n  or put this in your .vimrc\r\n  \r\n  exe \"set dict=\" . g:JavaImpDataDir . \"\/JavaImp.txt\"\r\n  set complete-=k\r\n  set complete+=k\r\n\r\n  After you have done so, you can open a .java file and use ^P and ^N to\r\n  autocomplete your Java class names.\r\n\r\n  Importing your JDK Classes\r\n  --------------------------\r\n  JavaImp also support a file type called \"jmplst\".  A jmplst file\r\n  essentially contains the output of a \"jar tf\" command.  It is mainly use\r\n  in the case where you want to import some external classes in JavaImp but\r\n  you do not have the source directory nor the jar file.  For example, you\r\n  can import the JDK classes, which can be located in $JAVA_HOME\/src.jar\r\n  (different in different distributions) with your JDK distribution,\r\n  by using the jmplst file:\r\n\r\n  To expose the standard JDK classes to JavaImp:\r\n\r\n  1. If you have \"sed\":\r\n     > jar tf $JAVA_HOME\/src.jar | sed -e 's#^src\/##' > jdk.jmplst\r\n\r\n     If you do not have \"sed\":\r\n     > jar tf $JAVA_HOME\/src.jar > jdk.jmplst\r\n     > vim jdk.jmplst\r\n     [Execute the following vim commands:]\r\n\r\n     1G0<C-v>Gllld:w\r\n\r\n     [ This will select vertically the all the \"src\/\" prefixes and delete\r\n     them, then save the file. Essentially, we want to get rid of the src\r\n     directory otherwise it'll screw up the import statements. ]\r\n\r\n  2. Put the jdk.jmplst in a directory that you've added in your\r\n     g:JavaImpPaths.  For example, I put my jdk.jmplst in\r\n     $HOME\/vim\/JavaImp\/jmplst directory, and add $HOME\/vim\/JavaImp\/jmplst to\r\n     g:JavaImpPaths.\r\n\r\n  3. Open vim with the JavaImp.vim loaded and Do a :JIG.  You should see\r\n     that JavaImp will pick up many more classes.\r\n\r\n  4. Try to do a :JI on a \"Vector\" class, for example, to see whether you\r\n     can add the import statement from the JDK.\r\n\r\n\r\n\r\n  Enjoy!\r\n\r\n","5":"REQUIREMENTS:\r\n  - It's recommended that you have the Unix \"sort\" binary (or the Windows's\r\n  \"sort\" or cygwin's \"sort\" will do) in your path.   For the jar support you\r\n  also need to have the\r\n  \"jar\" binary in your path.\r\n  - To use JavaDoc viewing, you probably need to have a pager like \"w3m\" or\r\n  \"lynx\".  You can also use your usual web browser for this.  You do not\r\n  really need this if you do not use the JavaDoc viewing feature.\r\n\r\nUSAGE:\r\n  Put this file in your ~\/.vim\/plugin directory.\r\n\r\n  You need to set two global variables in your .vimrc in order for this to\r\n  work:\r\n\r\n      let g:JavaImpPaths = \"...\"\r\n      let g:JavaImpDataDir = \"...\"\r\n\r\n  The g:JavaImpPaths is a comma separated list of paths that point to the\r\n  roots of the 'com' or 'org' etc.\r\n\r\n  For example: if you have your Java source files in\r\n  \/project\/src\/java\/com\/blah and \/project2\/javasrc\/org\/blah...., you'll put\r\n  this in your .vimrc file:\r\n\r\n      let g:JavaImpPaths = \"\/project\/src\/java,\/project2\/javasrc\"\r\n\r\n  If there are too many paths, you can split them into separate lines:\r\n\r\n      let g:JavaImpPaths = \"\/project\/src\/java,\" .\r\n         \\ \"\/project2\/javasrc,\" .\r\n         \\ \"\/project3\/javasrc\"\r\n\r\n  Note: Don't forget the ',' to separate the paths.\r\n\r\n  If ',' is not convenient for you, set g:JavaImpPathSep to the\r\n  (single-character) separator you would like to use:\r\n\r\n      let g:JavaImpPathSep = ':'\r\n\r\n  The g:JavaImpDataDir is a directory that you use to store JavaImp\r\n  settings and cache files. Default is:\r\n\r\n      let g:JavaImpDataDir = $HOME . \"\/vim\/JavaImp\"\r\n\r\n  Note: Since version 2.1, the \"g:JavaImpDataDir\" variable replaces\r\n  \"g:JavaImpClassList\" and \"g:JavaImpJarCache\".  If \"g:JavaImpClassList\" and\r\n  \"g:JavaImpJarCache\" are not set, then they default to\r\n  \"g:JavaImpDataDir\/JavaImp.txt\" and \"g:JavaImpDataDir\/cache\/\" accordingly.\r\n  The files and directory will be created automatically when you generate\r\n  the JavaImp.txt file.  It's recommended that you to use the\r\n  g:JavaImpDataDir variable instead.\r\n\r\n  Now you are ready for some actions.  You can now do a:\r\n\r\n      :JavaImpGenerate or :JIG\r\n\r\n  If you have not created the directory for g:JavaImpDataDir yet, this will\r\n  create the appropriate paths.  JIG will go through your JavaImpPaths and\r\n  search for anything that ends with .java, .class, or .jar.  It'll then\r\n  write the mappings to the JavaImp.txt and\/or the cache files.\r\n  \r\n  After you've generated your JavaImp.txt file, move your cursor to a class name\r\n  in a Java file and do a:\r\n\r\n      :JavaImp or :JI\r\n\r\n  And the magic happens!  You'll realize that you have an extra import\r\n  statement inserted after the last import statement in the file.  It'll\r\n  also prompts you with duplicate class names and insert what you have\r\n  selected.  If the class name is already imported, it'll do nothing.  \r\n\r\n  Doing a:\r\n\r\n      :JavaImpSilent\r\n\r\n  will do a similar thing with less verbosity.  This is useful to be used in\r\n  another script.\r\n\r\n  You can also sort the import statements in the file by doing:\r\n\r\n      :JavaImpSort or :JIS\r\n\r\n  Source Viewing\r\n  --------------\r\n\r\n  JavaImp will try to find the source file of the class under your cursor\r\n  by:\r\n\r\n      :JavaImpFile or :JIF\r\n      \r\n  Doing a :JavaImpFileSplit or :JIFS will open a splitted window on the\r\n  file.\r\n\r\n  JavaDoc Viewing\r\n  ---------------\r\n  If you want to use the JavaDoc viewing feature for JavaImp, you should set\r\n  g:JavaImpDocPaths.  Similar to how you set the g:JavaImpPaths,\r\n  g:JavaImpDocPaths contains a list of root level directories that contains\r\n  your java docs.  This, together with a HTML pager (like w3m or lynx on\r\n  Unix), let you view the JavaDocs very quickly by just hitting :JID on a\r\n  class name.  For example, you can set:\r\n\r\n      let g:JavaImpDocPaths = \"\/usr\/java\/docs\/api,\" .\r\n         \\ \"\/project\/docs\/api\"\r\n\r\n  The default pager is set to:\r\n\r\n      let g:JavaImpDocViewer = \"w3m\"\r\n  \r\n  On windows, you can put iexplore.exe or mozilla.exe in your path and set\r\n  the g:JavaImpDocViewer to \"iexplore.exe\" or \"mozilla.exe\".  Note that\r\n  windows' shell and spaces in the path don't mix. Thus, given an absolute\r\n  path of the HTML viewer to g:JavaImpDocViewer may not work.\r\n\r\n  If you have your g:JavaImpDocPaths and g:JavaImpDocViewer set correctly\r\n  You can then do this with your cursor on a classname:\r\n\r\n      :JavaImpDoc or :JID \r\n\r\n  JavaImp will find your class accordingly and open the viewer to the\r\n  class based on the import list that you've generated by :JIG.  You can\r\n  also set in your java.vim  filetype plugin to get a similar man page\r\n  behavior by press \"K\":\r\n\r\n      nmap <buffer> K :JID<CR>\r\n\r\n  Other Settings\r\n  --------------\r\n  You can make the following settings in your .vimrc file:\r\n\r\n  (Deprecated in 2.1) The g:JavaImpClassList is a file you specify to store\r\n  the class mappings.  The default is set to:\r\n  \r\n      let g:JavaImpClassList = g:JavaImpDataDir . \"\/JavaImp.txt\"\r\n\r\n  (Deprecated in 2.1, enabled by default and set relative to the\r\n  g:JavaImpDataDir) It's recommended that you set a directory for the\r\n  caching result for your jar files.  JavaImp saves the result from each\r\n  \"jar\" command in this directory. The default is set to:\r\n\r\n      let g:JavaImpJarCache = g:JavaImpDataDir . \"\/cache\"\r\n\r\n  (In in 2.1, g:JavaImpSortBin is set to \"sort\", so this is disabled by\r\n  default) The sorting algorithm gives preferences to the java.* classes.\r\n  You can turn this behavior off by putting this in your .vimrc file.\r\n\r\n      let g:JavaImpSortJavaFirst = 0\r\n\r\n  NOTE: If you do not have a sort binary, set the following to \"\", and\r\n  JavaImp will use the pure Vim implementation.  However, if\r\n  JavaImpClassList gets too huge, the sorting might choke. If you\r\n  are on a unix machine or you have the sort binary in your path, it's\r\n  recommended that you set (or leave it as default):\r\n\r\n      let g:JavaImpSortBin = \"sort\" \r\n\r\n  By default, the sort algorithm will insert a blank line among package\r\n  group with package root for 2 similar levels.  For example, the import of\r\n  the following:\r\n\r\n      import java.util.List;\r\n      import org.apache.tools.zip.ZipEntry;\r\n      import javax.mail.search.MessageNumberTerm;\r\n      import java.util.Vector;\r\n      import javax.mail.Message;\r\n      import org.apache.tools.ant.types.ZipFileSet;\r\n\r\n  will become:\r\n\r\n      import java.util.List;\r\n      import java.util.Vector;\r\n\r\n      import javax.mail.Message;\r\n      import javax.mail.search.MessageNumberTerm;\r\n\r\n      import org.apache.tools.ant.types.ZipFileSet;\r\n      import org.apache.tools.zip.ZipEntry;\r\n\r\n  Note the classes that begins similar package root with two beginning\r\n  levels of package hierarchy are stuck together.  You can set the\r\n  g:JavaImpSortPkgSep to change this behavior.  The default\r\n  g:JavaImpSortPkgSep is set to 2.  Do not set it too high though for you'll\r\n  insert a blank line after each import.  If you do not want to insert blank\r\n  lines among the imports, set:\r\n\r\n      let g:JavaImpSortPkgSep = 0\r\n\r\n  Be warned that g:JavaImpSortRemoveEmpty has no effect if\r\n  g:JavaImpSortPkgSep is set.\r\n\r\n  Extras\r\n  ------\r\n  After you have generated the JavaImp.txt file by using :JIG, you can use\r\n  it as your dictionary for autocompletion.  For example, you can put the\r\n  following in your java.vim ftplugin (note here g:JavaImpDataDir is set\r\n  before running this):\r\n\r\n  exe \"setlocal dict=\" . g:JavaImpDataDir . \"\/JavaImp.txt\"\r\n  setlocal complete-=k\r\n  setlocal complete+=k\r\n  \r\n  or put this in your .vimrc\r\n  \r\n  exe \"set dict=\" . g:JavaImpDataDir . \"\/JavaImp.txt\"\r\n  set complete-=k\r\n  set complete+=k\r\n\r\n  After you have done so, you can open a .java file and use ^P and ^N to\r\n  autocomplete your Java class names.\r\n\r\n  Importing your JDK Classes\r\n  --------------------------\r\n  JavaImp also support a file type called \"jmplst\".  A jmplst file\r\n  essentially contains the output of a \"jar tf\" command.  It is mainly use\r\n  in the case where you want to import some external classes in JavaImp but\r\n  you do not have the source directory nor the jar file.  For example, you\r\n  can import the JDK classes, which can be located in $JAVA_HOME\/src.jar\r\n  (different in different distributions) with your JDK distribution,\r\n  by using the jmplst file:\r\n\r\n  To expose the standard JDK classes to JavaImp:\r\n\r\n  1. If you have \"sed\":\r\n     > jar tf $JAVA_HOME\/src.jar | sed -e 's#^src\/##' > jdk.jmplst\r\n\r\n     If you do not have \"sed\":\r\n     > jar tf $JAVA_HOME\/src.jar > jdk.jmplst\r\n     > vim jdk.jmplst\r\n     [Execute the following vim commands:]\r\n\r\n     1G0<C-v>Gllld:w\r\n\r\n     [ This will select vertically the all the \"src\/\" prefixes and delete\r\n     them, then save the file. Essentially, we want to get rid of the src\r\n     directory otherwise it'll screw up the import statements. ]\r\n\r\n  2. Put the jdk.jmplst in a directory that you've added in your\r\n     g:JavaImpPaths.  For example, I put my jdk.jmplst in\r\n     $HOME\/vim\/JavaImp\/jmplst directory, and add $HOME\/vim\/JavaImp\/jmplst to\r\n     g:JavaImpPaths.\r\n\r\n  3. Open vim with the JavaImp.vim loaded and Do a :JIG.  You should see\r\n     that JavaImp will pick up many more classes.\r\n\r\n  4. Try to do a :JI on a \"Vector\" class, for example, to see whether you\r\n     can add the import statement from the JDK.\r\n\r\n\r\n\r\n  Enjoy!\r\n\r\n","first_name":"William","6":"William","last_name":"Lee","7":"Lee","releases":[{"0":"325","vim_version":"6.0","1":"6.0","script_version":"2.2.3","2":"2.2.3","version_comment":"Fixes a bug where JavaImp ignores files that start with 0.","3":"Fixes a bug where JavaImp ignores files that start with 0.","package":"JavaImp.vim","4":"JavaImp.vim","src_id":"3094","5":"3094","creation_date":"1086332620","6":"1086332620"},{"0":"325","vim_version":"6.0","1":"6.0","script_version":"2.2.2","2":"2.2.2","version_comment":"Do not insert the import if the class you want to insert is in the same package of the current source file.  (Thanks to Adam Hawthorne)\r\n","3":"Do not insert the import if the class you want to insert is in the same package of the current source file.  (Thanks to Adam Hawthorne)\r\n","package":"JavaImp.vim","4":"JavaImp.vim","src_id":"3000","5":"3000","creation_date":"1083918702","6":"1083918702"},{"0":"325","vim_version":"6.0","1":"6.0","script_version":"2.2.1","2":"2.2.1","version_comment":"Minor bug fixes.","3":"Minor bug fixes.","package":"JavaImp.vim","4":"JavaImp.vim","src_id":"2431","5":"2431","creation_date":"1067408667","6":"1067408667"},{"0":"325","vim_version":"6.0","1":"6.0","script_version":"2.2.0","2":"2.2.0","version_comment":"Added the JavaDoc viewing and source viewing capabilities.  You can now view API calls through an HTML viewer or load up a source file from your paths.\r\n","3":"Added the JavaDoc viewing and source viewing capabilities.  You can now view API calls through an HTML viewer or load up a source file from your paths.\r\n","package":"JavaImp.vim","4":"JavaImp.vim","src_id":"1857","5":"1857","creation_date":"1048699429","6":"1048699429"},{"0":"325","vim_version":"6.0","1":"6.0","script_version":"2.1.3","2":"2.1.3","version_comment":"Added an option to override the default JavaImpPaths separator.  Fixes an error when trying to do :JI over an unamed buffer.\r\n","3":"Added an option to override the default JavaImpPaths separator.  Fixes an error when trying to do :JI over an unamed buffer.\r\n","package":"JavaImp.vim","4":"JavaImp.vim","src_id":"1847","5":"1847","creation_date":"1048496955","6":"1048496955"},{"0":"325","vim_version":"6.0","1":"6.0","script_version":"2.1.2","2":"2.1.2","version_comment":"Fixes a critical bug in where a single import match would put in a \"0\" as its name.  Users of 2.1.1 should update to this immediately.  Thanks Matt Paduano for pointing this out.\r\n","3":"Fixes a critical bug in where a single import match would put in a \"0\" as its name.  Users of 2.1.1 should update to this immediately.  Thanks Matt Paduano for pointing this out.\r\n","package":"JavaImp.vim","4":"JavaImp.vim","src_id":"1812","5":"1812","creation_date":"1047636813","6":"1047636813"}]},"324":{"script_id":"324","0":"324","script_name":"multivim","1":"multivim","script_type":"utility","2":"utility","summary":"Integrate multiple vim windows","3":"Integrate multiple vim windows","description":"Based on bcbuf.vim (vimscript #201), this script allows the user to open a new vim window from within vim, and manage the buffers in all open vim sessions (windows) in a centralized manner. One can:\r\r\r\r\r\n\r\r\r\r\r\n0. Open a new vim window from within vim by the command \":nf\"\r\r\r\r\r\n\r\r\r\r\r\n1. Yank and Put across multiple sessions using the usual mappings.\r\r\r\r\r\n\r\r\r\r\r\n2. Edit a file, first in one session, then in another, using :edit, :split, :vsplit, etc.\r\r\r\r\r\n\r\r\r\r\r\n3. Look at all buffers in all sessions using :files, :buffers, etc.\r\r\r\r\r\n\r\r\r\r\r\n4. Push a command from one session's history and pop it in another.\r\r\r\r\r\n\r\r\r\r\r\nFor more details look at the comments at the start of the script. ","4":"Based on bcbuf.vim (vimscript #201), this script allows the user to open a new vim window from within vim, and manage the buffers in all open vim sessions (windows) in a centralized manner. One can:\r\r\r\r\r\n\r\r\r\r\r\n0. Open a new vim window from within vim by the command \":nf\"\r\r\r\r\r\n\r\r\r\r\r\n1. Yank and Put across multiple sessions using the usual mappings.\r\r\r\r\r\n\r\r\r\r\r\n2. Edit a file, first in one session, then in another, using :edit, :split, :vsplit, etc.\r\r\r\r\r\n\r\r\r\r\r\n3. Look at all buffers in all sessions using :files, :buffers, etc.\r\r\r\r\r\n\r\r\r\r\r\n4. Push a command from one session's history and pop it in another.\r\r\r\r\r\n\r\r\r\r\r\nFor more details look at the comments at the start of the script. ","install_details":"UNIX or related OS required, along with bash and Eterm. Minor modifications required if you want to change these requirements.\r\n\r\nThe tarball contains 2 files: \r\r\r\r\r\n\r\r\r\r\r\nmultivim.vim is the vim plugin and should go into the usual plugins directory.\r\r\r\r\r\n\r\r\r\r\r\nvim_stub is a bash shell script that should go somewhere in your $PATH. vim should always be invoked through it. You might want to\r\r\r\r\r\n\r\r\r\r\r\nalias vim='vim_stub'\r\r\r\r\r\n\r\r\r\r\r\nFor more help,\r\r\r\r\r\n:help add-plugin","5":"UNIX or related OS required, along with bash and Eterm. Minor modifications required if you want to change these requirements.\r\n\r\nThe tarball contains 2 files: \r\r\r\r\r\n\r\r\r\r\r\nmultivim.vim is the vim plugin and should go into the usual plugins directory.\r\r\r\r\r\n\r\r\r\r\r\nvim_stub is a bash shell script that should go somewhere in your $PATH. vim should always be invoked through it. You might want to\r\r\r\r\r\n\r\r\r\r\r\nalias vim='vim_stub'\r\r\r\r\r\n\r\r\r\r\r\nFor more help,\r\r\r\r\r\n:help add-plugin","first_name":"Kartik","6":"Kartik","last_name":"Agaram","7":"Agaram","releases":[{"0":"324","vim_version":"6.0","1":"6.0","script_version":"1.2","2":"1.2","version_comment":"Major bugfix - :files was going into an infinite loop. Now fixed.","3":"Major bugfix - :files was going into an infinite loop. Now fixed.","package":"multivim.tgz","4":"multivim.tgz","src_id":"974","5":"974","creation_date":"1025566807","6":"1025566807"}]},"323":{"script_id":"323","0":"323","script_name":"reformat.vim","1":"reformat.vim","script_type":"utility","2":"utility","summary":"Reformat paragraphs according to file type","3":"Reformat paragraphs according to file type","description":"This script defines the common <C-J> key binding to reformat paragraphs, but also takes cares of properly reformatting paragraphs having no blank lines around them, but delimited by specific markup like <p> ... <\/p>, <para> ... <\/para>, \/* ... *\/ or any other constructs: it can be easily extended for about any syntax.","4":"This script defines the common <C-J> key binding to reformat paragraphs, but also takes cares of properly reformatting paragraphs having no blank lines around them, but delimited by specific markup like <p> ... <\/p>, <para> ... <\/para>, \/* ... *\/ or any other constructs: it can be easily extended for about any syntax.","install_details":"Source that file from your init file.","5":"Source that file from your init file.","first_name":"Jean-Baptiste","6":"Jean-Baptiste","last_name":"Quenot","7":"Quenot","releases":[{"0":"323","vim_version":"6.0","1":"6.0","script_version":"1.3","2":"1.3","version_comment":"Added support for Python and C.","3":"Added support for Python and C.","package":"reformat.vim","4":"reformat.vim","src_id":"1006","5":"1006","creation_date":"1026273920","6":"1026273920"},{"0":"323","vim_version":"6.0","1":"6.0","script_version":"1.2","2":"1.2","version_comment":"Support for HTML paragraphs.","3":"Support for HTML paragraphs.","package":"reformat.vim","4":"reformat.vim","src_id":"996","5":"996","creation_date":"1026141171","6":"1026141171"},{"0":"323","vim_version":"6.0","1":"6.0","script_version":"1.1","2":"1.1","version_comment":"Fixed commands quoting.","3":"Fixed commands quoting.","package":"reformat.vim","4":"reformat.vim","src_id":"985","5":"985","creation_date":"1025697974","6":"1025697974"},{"0":"323","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"reformat.vim","4":"reformat.vim","src_id":"960","5":"960","creation_date":"1025238508","6":"1025238508"}]},"322":{"script_id":"322","0":"322","script_name":"srecord.vim","1":"srecord.vim","script_type":"syntax","2":"syntax","summary":"Syntax highlights S-Record files.","3":"Syntax highlights S-Record files.","description":"Syntax highlights S-Record files.","4":"Syntax highlights S-Record files.","install_details":"Create a filetype for your srecords. For example in my filetype.vim page I\\\\\\'ve entered\r\n\r\n \\\\\\\"Srecord Files\r\n\r\nau! BufRead,BufNewFile *.s19 setfiletype srecord \r\n\r\nNow place the script in your syntax plugin in directory.","5":"Create a filetype for your srecords. For example in my filetype.vim page I\\\\\\'ve entered\r\n\r\n \\\\\\\"Srecord Files\r\n\r\nau! BufRead,BufNewFile *.s19 setfiletype srecord \r\n\r\nNow place the script in your syntax plugin in directory.","first_name":"brad","6":"brad","last_name":"phelan","7":"phelan","releases":[{"0":"322","vim_version":"6.0","1":"6.0","script_version":"2.0","2":"2.0","version_comment":"Added support for other S-Record line types. Previously only S3 type lines were supported.","3":"Added support for other S-Record line types. Previously only S3 type lines were supported.","package":"srecord.vim","4":"srecord.vim","src_id":"1079","5":"1079","creation_date":"1028510955","6":"1028510955"},{"0":"322","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"srecord.vim","4":"srecord.vim","src_id":"949","5":"949","creation_date":"1025085109","6":"1025085109"}]},"321":{"script_id":"321","0":"321","script_name":"Buffer Search","1":"Buffer Search","script_type":"utility","2":"utility","summary":"Different search patterns across Multiple Windows.","3":"Different search patterns across Multiple Windows.","description":"This plugin lets your search pattern be specific to \r\nthat buffer. This is especially handy when one \r\nworks with multiple windows and wants different\r\nsearch pattern highlighted in different windows.\r\n\r\nNormally  if you do :\/abc in one window, all other\r\nwindows will also highlight \"abc\".\r\nNow by using this plugin you can do\r\n:Bs abc    which will highlight \"abc\" only in that\r\nwindow.  Likewise you can have multiple search\r\npattern highlighted in different windows.\r\n\r\nSide Effects: This plugin will unset hlsearch option\r\n\r\n-ncr","4":"This plugin lets your search pattern be specific to \r\nthat buffer. This is especially handy when one \r\nworks with multiple windows and wants different\r\nsearch pattern highlighted in different windows.\r\n\r\nNormally  if you do :\/abc in one window, all other\r\nwindows will also highlight \"abc\".\r\nNow by using this plugin you can do\r\n:Bs abc    which will highlight \"abc\" only in that\r\nwindow.  Likewise you can have multiple search\r\npattern highlighted in different windows.\r\n\r\nSide Effects: This plugin will unset hlsearch option\r\n\r\n-ncr","install_details":"Place this script in your plugin directory, then use\r\n\":Bs <search-pattern>\" to invoke buffer search.","5":"Place this script in your plugin directory, then use\r\n\":Bs <search-pattern>\" to invoke buffer search.","first_name":"Naveen","6":"Naveen","last_name":"Chandra","7":"Chandra","releases":[{"0":"321","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"bufsearch.vim","4":"bufsearch.vim","src_id":"948","5":"948","creation_date":"1025065085","6":"1025065085"}]},"320":{"script_id":"320","0":"320","script_name":"hungarian_to_english","1":"hungarian_to_english","script_type":"utility","2":"utility","summary":"Strips Hungarian notation from C and C++ identifiers.","3":"Strips Hungarian notation from C and C++ identifiers.","description":"A function to strip Hungarian decorations from C and C++ \r\nidentifier names.  In some cases, this can make code \r\neasier to read.  It might also change how your program \r\nruns or make it not compile, so use with caution!\r\n","4":"A function to strip Hungarian decorations from C and C++ \r\nidentifier names.  In some cases, this can make code \r\neasier to read.  It might also change how your program \r\nruns or make it not compile, so use with caution!\r\n","install_details":"Put hungarian_to_english.vim in $VIM\/vimfiles\/plugin directory and change the key mapping from <F8> to \r\nwhichever key combination you prefer.\r\n","5":"Put hungarian_to_english.vim in $VIM\/vimfiles\/plugin directory and change the key mapping from <F8> to \r\nwhichever key combination you prefer.\r\n","first_name":"Issac","6":"Issac","last_name":"Trotts","7":"Trotts","releases":[{"0":"320","vim_version":"6.0","1":"6.0","script_version":"1.0.3","2":"1.0.3","version_comment":"- removal of fBlah \r\n- no more spurious error messages from patterns not found","3":"- removal of fBlah \r\n- no more spurious error messages from patterns not found","package":"hungarian_to_english.vim","4":"hungarian_to_english.vim","src_id":"961","5":"961","creation_date":"1025277736","6":"1025277736"},{"0":"320","vim_version":"6.0","1":"6.0","script_version":"1.0.2","2":"1.0.2","version_comment":"- removal of aBlah, eBlah, _blah, chBlah\r\n- better handling of m_bBlah and its friends\r\n- fixed it so it works not just on the first offending instance\r\n  of each line\r\n- corrected incorrectly changing identifiers like PRINTF when\r\n  ignorecase is turned on\r\n\r\n","3":"- removal of aBlah, eBlah, _blah, chBlah\r\n- better handling of m_bBlah and its friends\r\n- fixed it so it works not just on the first offending instance\r\n  of each line\r\n- corrected incorrectly changing identifiers like PRINTF when\r\n  ignorecase is turned on\r\n\r\n","package":"hungarian_to_english.vim","4":"hungarian_to_english.vim","src_id":"958","5":"958","creation_date":"1025125888","6":"1025125888"},{"0":"320","vim_version":"6.0","1":"6.0","script_version":"1.0.1","2":"1.0.1","version_comment":"- fixed a bug with capitalization\r\n- added removal of the m_blah notation\r\n- changed to only operate on the selected range\r\n","3":"- fixed a bug with capitalization\r\n- added removal of the m_blah notation\r\n- changed to only operate on the selected range\r\n","package":"hungarian_to_english.vim","4":"hungarian_to_english.vim","src_id":"957","5":"957","creation_date":"1025104224","6":"1025104224"},{"0":"320","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"hungarian_to_english.vim","4":"hungarian_to_english.vim","src_id":"945","5":"945","creation_date":"1025012935","6":"1025012935"}]},"319":{"script_id":"319","0":"319","script_name":"highlightline.vim","1":"highlightline.vim","script_type":"utility","2":"utility","summary":"This script allows you to highlight lines.","3":"This script allows you to highlight lines.","description":"This is a highlight current line script.\r\n\r\npress F2 to highlight the current line\r\npress F2 again to unhighlight the current highlighted line","4":"This is a highlight current line script.\r\n\r\npress F2 to highlight the current line\r\npress F2 again to unhighlight the current highlighted line","install_details":"Just put this in your plugin directory or source it in your vimrc.","5":"Just put this in your plugin directory or source it in your vimrc.","first_name":"Torrin","6":"Torrin","last_name":"","7":"","releases":[{"0":"319","vim_version":"6.0","1":"6.0","script_version":"5","2":"5","version_comment":"Improved version, same as version 4, just forgot to turn off the echo highlightedline.","3":"Improved version, same as version 4, just forgot to turn off the echo highlightedline.","package":"highlightline.vim","4":"highlightline.vim","src_id":"2136","5":"2136","creation_date":"1057742363","6":"1057742363"},{"0":"319","vim_version":"6.0","1":"6.0","script_version":"4","2":"4","version_comment":"This is a much improved version of the script.  It doesn't handle everything correctly yet, but I'm working on it.  Enjoy.","3":"This is a much improved version of the script.  It doesn't handle everything correctly yet, but I'm working on it.  Enjoy.","package":"highlightline.vim","4":"highlightline.vim","src_id":"2135","5":"2135","creation_date":"1057737753","6":"1057737753"},{"0":"319","vim_version":"6.0","1":"6.0","script_version":"2.01","2":"2.01","version_comment":"On line 41, change    getline(\".\")    to      substitute(getline(\".\"),\"[+\\\"]\",\".\",\"g\")    \r\nThis fixes the delimiter problem. mentioned in version 2.","3":"On line 41, change    getline(\".\")    to      substitute(getline(\".\"),\"[+\\\"]\",\".\",\"g\")    \r\nThis fixes the delimiter problem. mentioned in version 2.","package":"highlightline.vim","4":"highlightline.vim","src_id":"983","5":"983","creation_date":"1025692176","6":"1025692176"},{"0":"319","vim_version":"6.0","1":"6.0","script_version":"2","2":"2","version_comment":"Initial upload","3":"Initial upload","package":"highlightline.vim","4":"highlightline.vim","src_id":"938","5":"938","creation_date":"1024654413","6":"1024654413"}]},"318":{"script_id":"318","0":"318","script_name":"f.vim","1":"f.vim","script_type":"utility","2":"utility","summary":"Function that shows lines that do contain a given regexp. The rest is folded.","3":"Function that shows lines that do contain a given regexp. The rest is folded.","description":":call F()\r\nThis function lets you see all the lines in a file\r\nthat contain a given regular-expression.\r\n\r\nThe remaining lines are folded with the manual method,\r\nand can be opened to see some 'nearby' line.\r\n\r\nIf no regular expression is specified, the last regular expression\r\nspecified for search is utilized.\r\n\r\nThe idea comes from the mainframe ISPF editor.\r\n\r\nAfter you get your folds, you can give commands affecting only the folded lines\r\nusing:\r\n\r\n:folddoclosed\r\n\r\nor use:\r\n\r\n:folddoopen\r\n\r\nto operate only on the visible lines.\r\n\r\nzo   to open a fold a bit\r\nzozj to open a fold a bit and leave the cursor on the fold line\r\nzO   to open a fold completely \r\nzE   to open all folds\r\n\r\nzf{motion} to close folders 'a bit more' (or to create folders)\r\nIf you have 2 adjacent folders, zf<ENTER> will 'merge' them.\r\nIn the same way a visible line can be 'added' to a nearby folder.\r\n\r\n:call FA()\r\nThis function is similar to F() above, except instead of typing in\r\na regular expression, the current word the cursor is over is used as\r\nthe regular expression.\r\n\r\nThe function FA() has been prepared and added by:\r\nKen Huisman - ken.huisman@gmail.com\r\n\r\nSuggested mappings:\r\n:map <F5> :call F()<CR>\r\n:map <F6> :normal zozj<CR>\r\n\r\n:<Up> to recall the macro after having executed it once\r\n\r\nediting the \"f.vim\" file itself:\r\n\r\ntry giving as an expression  nfold\r\ntry giving as an expression  as\r\ntry giving as an expression   as     [that is: ' as' ]\r\ntry giving as an expression  let\r\ntry giving as an expression  ^\":\r\ntry giving as an expression  :fun\\|:endf\r\ntry giving as an expression  :endf\r\ntry giving as an expression  ^:endf\r\n\r\nfor remarks, complaints, etc. write to: azc100@gmail.com\r\nversion 05042001","4":":call F()\r\nThis function lets you see all the lines in a file\r\nthat contain a given regular-expression.\r\n\r\nThe remaining lines are folded with the manual method,\r\nand can be opened to see some 'nearby' line.\r\n\r\nIf no regular expression is specified, the last regular expression\r\nspecified for search is utilized.\r\n\r\nThe idea comes from the mainframe ISPF editor.\r\n\r\nAfter you get your folds, you can give commands affecting only the folded lines\r\nusing:\r\n\r\n:folddoclosed\r\n\r\nor use:\r\n\r\n:folddoopen\r\n\r\nto operate only on the visible lines.\r\n\r\nzo   to open a fold a bit\r\nzozj to open a fold a bit and leave the cursor on the fold line\r\nzO   to open a fold completely \r\nzE   to open all folds\r\n\r\nzf{motion} to close folders 'a bit more' (or to create folders)\r\nIf you have 2 adjacent folders, zf<ENTER> will 'merge' them.\r\nIn the same way a visible line can be 'added' to a nearby folder.\r\n\r\n:call FA()\r\nThis function is similar to F() above, except instead of typing in\r\na regular expression, the current word the cursor is over is used as\r\nthe regular expression.\r\n\r\nThe function FA() has been prepared and added by:\r\nKen Huisman - ken.huisman@gmail.com\r\n\r\nSuggested mappings:\r\n:map <F5> :call F()<CR>\r\n:map <F6> :normal zozj<CR>\r\n\r\n:<Up> to recall the macro after having executed it once\r\n\r\nediting the \"f.vim\" file itself:\r\n\r\ntry giving as an expression  nfold\r\ntry giving as an expression  as\r\ntry giving as an expression   as     [that is: ' as' ]\r\ntry giving as an expression  let\r\ntry giving as an expression  ^\":\r\ntry giving as an expression  :fun\\|:endf\r\ntry giving as an expression  :endf\r\ntry giving as an expression  ^:endf\r\n\r\nfor remarks, complaints, etc. write to: azc100@gmail.com\r\nversion 05042001","install_details":"source the file \r\n:so f.vim\r\n\r\n:call F()\r\n\r\n:call FA()\r\n\r\n\"f.vim\" can also be added to the .vimrc file\r\nThere are a few suggested mappings, but they are commented.\r\nIf you wish to use them, put them (uncommented :-) in your .vimrc file.","5":"source the file \r\n:so f.vim\r\n\r\n:call F()\r\n\r\n:call FA()\r\n\r\n\"f.vim\" can also be added to the .vimrc file\r\nThere are a few suggested mappings, but they are commented.\r\nIf you wish to use them, put them (uncommented :-) in your .vimrc file.","first_name":"Antonio","6":"Antonio","last_name":"Colombo","7":"Colombo","releases":[{"0":"318","vim_version":"6.0","1":"6.0","script_version":"05051001","2":"05051001","version_comment":"Added a modification introduced by Paul Wei. When no search string is specified, the one remembered from the last search command is used instead.","3":"Added a modification introduced by Paul Wei. When no search string is specified, the one remembered from the last search command is used instead.","package":"f.vim","4":"f.vim","src_id":"4264","5":"4264","creation_date":"1115712932","6":"1115712932"},{"0":"318","vim_version":"6.0","1":"6.0","script_version":"05042001","2":"05042001","version_comment":"Comments modification, thanks to Alexander Langer","3":"Comments modification, thanks to Alexander Langer","package":"f.vim","4":"f.vim","src_id":"4186","5":"4186","creation_date":"1113961019","6":"1113961019"},{"0":"318","vim_version":"6.0","1":"6.0","script_version":"05011901","2":"05011901","version_comment":"Added new function FA() written and contributed by \r\nKen Huisman [ken.huisman@gmail.com]. The current word the cursor is over is used as the regular expression to search.","3":"Added new function FA() written and contributed by \r\nKen Huisman [ken.huisman@gmail.com]. The current word the cursor is over is used as the regular expression to search.","package":"f.vim","4":"f.vim","src_id":"3783","5":"3783","creation_date":"1106097587","6":"1106097587"},{"0":"318","vim_version":"6.0","1":"6.0","script_version":"03121201","2":"03121201","version_comment":"Modified as per suggestions\/corrections from Michael Fitz and Jean-Marc Frigerio. Mainly diagnostics and highlighting.","3":"Modified as per suggestions\/corrections from Michael Fitz and Jean-Marc Frigerio. Mainly diagnostics and highlighting.","package":"f.vim","4":"f.vim","src_id":"2585","5":"2585","creation_date":"1071202035","6":"1071202035"},{"0":"318","vim_version":"6.0","1":"6.0","script_version":"02070801","2":"02070801","version_comment":"Added :foldenable to be able to use the function also while inside :help","3":"Added :foldenable to be able to use the function also while inside :help","package":"f.vim","4":"f.vim","src_id":"994","5":"994","creation_date":"1026097324","6":"1026097324"},{"0":"318","vim_version":"6.0","1":"6.0","script_version":"02062101","2":"02062101","version_comment":"Initial upload","3":"Initial upload","package":"f.vim","4":"f.vim","src_id":"937","5":"937","creation_date":"1024638360","6":"1024638360"}]},"317":{"script_id":"317","0":"317","script_name":"vera.vim","1":"vera.vim","script_type":"syntax","2":"syntax","summary":"Syntax file for the Vera language","3":"Syntax file for the Vera language","description":"This is a vera.vim syntax file.  It\r\nhas been updated to reflect Vera 5.0.\r\nDeprecated tasks in the language are\r\nnow linked to \"Error\" in order to\r\nhighlight them in the code.","4":"This is a vera.vim syntax file.  It\r\nhas been updated to reflect Vera 5.0.\r\nDeprecated tasks in the language are\r\nnow linked to \"Error\" in order to\r\nhighlight them in the code.","install_details":":so vera.vim","5":":so vera.vim","first_name":"Beth","6":"Beth","last_name":"Leonard","7":"Leonard","releases":[{"0":"317","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"vera.vim","4":"vera.vim","src_id":"924","5":"924","creation_date":"1024066607","6":"1024066607"}]},"316":{"script_id":"316","0":"316","script_name":"broadcast.vim","1":"broadcast.vim","script_type":"utility","2":"utility","summary":"Send keystrokes to all VIM windows","3":"Send keystrokes to all VIM windows","description":"This plugin lets you broadcast to all GVIM windows (or all other windows except current).  Especially handy for someone who prefers to open each file in a separate window instead of a separate buffer.  Lots of things possible, for example:\r\n\r\nGlobally replace text across all GVIM windows:\r\n   :Bcast :%s\/oldtext\/newtext\/g<CR>\r\n\r\nExit all other opened GVIM windows:\r\n   :Bcast0 :q<CR>\r\n","4":"This plugin lets you broadcast to all GVIM windows (or all other windows except current).  Especially handy for someone who prefers to open each file in a separate window instead of a separate buffer.  Lots of things possible, for example:\r\n\r\nGlobally replace text across all GVIM windows:\r\n   :Bcast :%s\/oldtext\/newtext\/g<CR>\r\n\r\nExit all other opened GVIM windows:\r\n   :Bcast0 :q<CR>\r\n","install_details":"Place script in your plugin directory, then use \":Bcast <keys>\" or \":Bcast0 <keys>\" to invoke.\r\nVIM needs to be compiled with +clientserver.","5":"Place script in your plugin directory, then use \":Bcast <keys>\" or \":Bcast0 <keys>\" to invoke.\r\nVIM needs to be compiled with +clientserver.","first_name":"Don","6":"Don","last_name":"Yang","7":"Yang","releases":[{"0":"316","vim_version":"6.0","1":"6.0","script_version":"0.9","2":"0.9","version_comment":"Initial upload","3":"Initial upload","package":"broadcast.vim","4":"broadcast.vim","src_id":"920","5":"920","creation_date":"1023869364","6":"1023869364"}]},"315":{"script_id":"315","0":"315","script_name":"xchat log syntax","1":"xchat log syntax","script_type":"syntax","2":"syntax","summary":"a syntax file for xchat log files","3":"a syntax file for xchat log files","description":"this is a syntax file for xchat log files so those that look at them alot\r\ncan read them easier than pure flat uncolored text\r\n\r\nthe syntax is setup just like what xchat outputs minus the colored nicks option\r\ni hope to add that sometime but it could be a while if at all\r\n","4":"this is a syntax file for xchat log files so those that look at them alot\r\ncan read them easier than pure flat uncolored text\r\n\r\nthe syntax is setup just like what xchat outputs minus the colored nicks option\r\ni hope to add that sometime but it could be a while if at all\r\n","install_details":"to install just copy to your local syntax directory ~\/.vim\/syntax for most","5":"to install just copy to your local syntax directory ~\/.vim\/syntax for most","first_name":"Bret","6":"Bret","last_name":"Towe","7":"Towe","releases":[{"0":"315","vim_version":"6.0","1":"6.0","script_version":"0.2","2":"0.2","version_comment":"Initial upload","3":"Initial upload","package":"xchatlog.vim","4":"xchatlog.vim","src_id":"918","5":"918","creation_date":"1023843250","6":"1023843250"}]},"314":{"script_id":"314","0":"314","script_name":"tomatosoup.vim","1":"tomatosoup.vim","script_type":"color scheme","2":"color scheme","summary":"A humorous colorscheme based on tomato soup and grilled cheese sandwiches!","3":"A humorous colorscheme based on tomato soup and grilled cheese sandwiches!","description":"Download this, look at it, go make some tomato soup and grilled cheese sandwiches and enjoy them.  Then when you are done eating, use a serious colorscheme.  You could possibly set some useful commands to change the colorscheme to tomatosoup.vim around lunch and dinner time.  :)  Have fun, and happy vimming!","4":"Download this, look at it, go make some tomato soup and grilled cheese sandwiches and enjoy them.  Then when you are done eating, use a serious colorscheme.  You could possibly set some useful commands to change the colorscheme to tomatosoup.vim around lunch and dinner time.  :)  Have fun, and happy vimming!","install_details":"Just put in your ~\/.vim\/colors\/ directory and type \":color tomatosoup\".","5":"Just put in your ~\/.vim\/colors\/ directory and type \":color tomatosoup\".","first_name":"Michael","6":"Michael","last_name":"Brailsford","7":"Brailsford","releases":[{"0":"314","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"tomatosoup.vim","4":"tomatosoup.vim","src_id":"917","5":"917","creation_date":"1023805879","6":"1023805879"}]},"313":{"script_id":"313","0":"313","script_name":"EDIFACT position in a segment","1":"EDIFACT position in a segment","script_type":"utility","2":"utility","summary":"works out the position of the cursor in an EDIFACT segment","3":"works out the position of the cursor in an EDIFACT segment","description":"i spend quite a lot of time reading, editing, and translating EDIFACT messages.  so i have produced this to help me work out where i am in the file.\r\n\r\nthe EDIFACT position dscription\r\nSG2.PNA.C816.3836\r\nisnt that helpful without a spec for reference.  the first two parts (segment group 2, segment PNA) are quite clear, but the last two arent very useful.\r\n\r\nfor an example segment\r\nPNA+PAT+NHS_NUM1:OPI+++SU:SURNAME1+FO:FORENAME1A+TI:TITLE1+MI:FORENAME1B+FS:FORENAME1C'\r\n\r\nthat is the fragment \"SURNAME1\"\r\n\r\nso instead i use numbers for the element and fragment positions, both numbered from zero.  \"PNA\" is element zero, \"PAT\" element one, etc.\r\n\r\nusing this function, place your cursor in the \"SURNAME1\" fragment, and it will return the info:\r\nelement = 5 , fragment = 1\r\n\r\nwhen using this, make sure that every segment starts on a new line in your file (search for ' and replace with '\\r will do this nicely).  trying to read EDIFACT when it is all one line is just to painful, so i dont recorment it.\r\n\r\nthis function has the seperators \"+\" and \":\" hard coded at the moment, and doesnt handle escaped seperators.","4":"i spend quite a lot of time reading, editing, and translating EDIFACT messages.  so i have produced this to help me work out where i am in the file.\r\n\r\nthe EDIFACT position dscription\r\nSG2.PNA.C816.3836\r\nisnt that helpful without a spec for reference.  the first two parts (segment group 2, segment PNA) are quite clear, but the last two arent very useful.\r\n\r\nfor an example segment\r\nPNA+PAT+NHS_NUM1:OPI+++SU:SURNAME1+FO:FORENAME1A+TI:TITLE1+MI:FORENAME1B+FS:FORENAME1C'\r\n\r\nthat is the fragment \"SURNAME1\"\r\n\r\nso instead i use numbers for the element and fragment positions, both numbered from zero.  \"PNA\" is element zero, \"PAT\" element one, etc.\r\n\r\nusing this function, place your cursor in the \"SURNAME1\" fragment, and it will return the info:\r\nelement = 5 , fragment = 1\r\n\r\nwhen using this, make sure that every segment starts on a new line in your file (search for ' and replace with '\\r will do this nicely).  trying to read EDIFACT when it is all one line is just to painful, so i dont recorment it.\r\n\r\nthis function has the seperators \"+\" and \":\" hard coded at the moment, and doesnt handle escaped seperators.","install_details":"append the file to your .vimrc\r\nthe default mapping is _=","5":"append the file to your .vimrc\r\nthe default mapping is _=","first_name":"colin","6":"colin","last_name":"dearing","7":"dearing","releases":[{"0":"313","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"get_edi_pos.vim","4":"get_edi_pos.vim","src_id":"909","5":"909","creation_date":"1023688027","6":"1023688027"}]},"312":{"script_id":"312","0":"312","script_name":"ipsec_conf.vim","1":"ipsec_conf.vim","script_type":"syntax","2":"syntax","summary":"Syntax highlighting for FreeS\/WAN ipsec.conf","3":"Syntax highlighting for FreeS\/WAN ipsec.conf","description":"Highlights keywords, IP addresses, numbers, and strings in FreeS\/WAN's (http:\/\/www.freeswan.org\/) ipsec.conf configuration file.\r\n\r\nSomewhat validating: it flags unknown constructs as errors in red.","4":"Highlights keywords, IP addresses, numbers, and strings in FreeS\/WAN's (http:\/\/www.freeswan.org\/) ipsec.conf configuration file.\r\n\r\nSomewhat validating: it flags unknown constructs as errors in red.","install_details":"Copy to ~\/.vim\/syntax and add the following to ~\/.vim\/filetype.vim:\r\n\r\n    au! BufRead,BufNewFile ipsec.conf\tsetfiletype ipsec_conf","5":"Copy to ~\/.vim\/syntax and add the following to ~\/.vim\/filetype.vim:\r\n\r\n    au! BufRead,BufNewFile ipsec.conf\tsetfiletype ipsec_conf","first_name":"Bruce","6":"Bruce","last_name":"Christensen","7":"Christensen","releases":[{"0":"312","vim_version":"6.0","1":"6.0","script_version":"0.1.1","2":"0.1.1","version_comment":"Changes:\r\n\r\n- Added support for X.509 keywords\r\n- Fixed a bug that caused Vim 6 to eat 100% CPU (thanks to Christian Gall <cg@cgall.de> for reporting the bug)\r\n","3":"Changes:\r\n\r\n- Added support for X.509 keywords\r\n- Fixed a bug that caused Vim 6 to eat 100% CPU (thanks to Christian Gall <cg@cgall.de> for reporting the bug)\r\n","package":"ipsec_conf.vim","4":"ipsec_conf.vim","src_id":"912","5":"912","creation_date":"1023704853","6":"1023704853"},{"0":"312","vim_version":"5.7","1":"5.7","script_version":"0.1.0","2":"0.1.0","version_comment":"Initial upload","3":"Initial upload","package":"ipsec_conf.vim","4":"ipsec_conf.vim","src_id":"908","5":"908","creation_date":"1023543465","6":"1023543465"}]},"311":{"script_id":"311","0":"311","script_name":"grep.vim","1":"grep.vim","script_type":"utility","2":"utility","summary":"Search tools (grep, ripgrep, ack, ag, findstr, git grep) integration with Vim","3":"Search tools (grep, ripgrep, ack, ag, findstr, git grep) integration with Vim","description":"The grep plugin integrates grep like utilities (grep, fgrep, egrep, agrep, findstr, silver searcher, ack, ripgrep, git grep, sift, platinum searcher and universal code grep) with Vim and allows you to search for a pattern in one or more files and jump to them.\r\n\r\nTo use this plugin, you will need the grep like utilities in your system.  If a particular utility is not present, then you cannot use the corresponding features, but you can still use the rest of the features supported by the plugin.  For information about where to download these utilities, refer to the help file.\r\n\r\nThe github repository for this plugin is at https:\/\/github.com\/yegappan\/grep\r\n\r\nThe grep.vim plugin introduce the following Vim commands - :Grep, :Rgrep, :GrepBuffer, :GrepArgs, :Fgrep, :Egrep, :Findstr, :Agrep, :Ag, :Ack, :Rg, :GitGrep, :Sift, :Ptgrep, :Ucgrep, etc.  You can use these commands to search for patterns.\r\n\r\nFor more information about the commands and how to configure this plugin, refer to the help file.\r\n","4":"The grep plugin integrates grep like utilities (grep, fgrep, egrep, agrep, findstr, silver searcher, ack, ripgrep, git grep, sift, platinum searcher and universal code grep) with Vim and allows you to search for a pattern in one or more files and jump to them.\r\n\r\nTo use this plugin, you will need the grep like utilities in your system.  If a particular utility is not present, then you cannot use the corresponding features, but you can still use the rest of the features supported by the plugin.  For information about where to download these utilities, refer to the help file.\r\n\r\nThe github repository for this plugin is at https:\/\/github.com\/yegappan\/grep\r\n\r\nThe grep.vim plugin introduce the following Vim commands - :Grep, :Rgrep, :GrepBuffer, :GrepArgs, :Fgrep, :Egrep, :Findstr, :Agrep, :Ag, :Ack, :Rg, :GitGrep, :Sift, :Ptgrep, :Ucgrep, etc.  You can use these commands to search for patterns.\r\n\r\nFor more information about the commands and how to configure this plugin, refer to the help file.\r\n","install_details":"You can use any one of the Vim plugin managers (dein.vim, pathogen, vam, vim-plug, volt, Vundle, etc.) to install and manage this plugin.\r\n\r\nAlternatively, you can also manually download and install the plugin using the following steps. \r\n\r\n1. Download the grep.zip file from the https:\/\/vim.sourceforge.io site. \r\n2. Expand the grep.zip file to the $HOME\/.vim\/plugin or $HOME\/vimfiles\/plugin or $VIM\/vimfiles\/plugin directory.\r\n3. If the grep executables are not already present in one of the directories in the PATH environment variable, then set the Grep_Path and other _Path variables to point to the location of the grep utilities in the .vimrc file.\r\n4. Restart Vim.\r\n5. You can now use the \":Grep\" and other commands to search for patterns in files.\r\n","5":"You can use any one of the Vim plugin managers (dein.vim, pathogen, vam, vim-plug, volt, Vundle, etc.) to install and manage this plugin.\r\n\r\nAlternatively, you can also manually download and install the plugin using the following steps. \r\n\r\n1. Download the grep.zip file from the https:\/\/vim.sourceforge.io site. \r\n2. Expand the grep.zip file to the $HOME\/.vim\/plugin or $HOME\/vimfiles\/plugin or $VIM\/vimfiles\/plugin directory.\r\n3. If the grep executables are not already present in one of the directories in the PATH environment variable, then set the Grep_Path and other _Path variables to point to the location of the grep utilities in the .vimrc file.\r\n4. Restart Vim.\r\n5. You can now use the \":Grep\" and other commands to search for patterns in files.\r\n","first_name":"Yegappan","6":"Yegappan","last_name":"Lakshmanan","7":"Lakshmanan","releases":[{"0":"311","vim_version":"7.0","1":"7.0","script_version":"2.2","2":"2.2","version_comment":"Added support for Universal Code Grep (UCG).","3":"Added support for Universal Code Grep (UCG).","package":"grep.zip","4":"grep.zip","src_id":"25998","5":"25998","creation_date":"1527576211","6":"1527576211"},{"0":"311","vim_version":"7.0","1":"7.0","script_version":"2.1","2":"2.1","version_comment":"1. Added support for git grep, sift, platinum searcher and findstr. \r\n2. Removed Grep_Default_Options and added support for search command specific option variables. \r\n3. Use 'shell' and 'shellcmdflag' options for running the search command. \r\n4. Redirect the search command input to null. \r\n5. On MS-Windows, convert the command path, search directory path, and temporary file path to 8.3 format. \r\n6. Support for running commands like ag, ack, ripgrep, git and platinum searcher without any file names to support recursive searches. \r\n7. Move all the commands and their options into a separate table for simplified lookup. \r\n8. On MS-Windows, use findstr instead of grep for buffer list and argument list search commands. \r\n9. Refactor the code and simplify long functions. \r\n10. Changed the license to MIT license. \r\n","3":"1. Added support for git grep, sift, platinum searcher and findstr. \r\n2. Removed Grep_Default_Options and added support for search command specific option variables. \r\n3. Use 'shell' and 'shellcmdflag' options for running the search command. \r\n4. Redirect the search command input to null. \r\n5. On MS-Windows, convert the command path, search directory path, and temporary file path to 8.3 format. \r\n6. Support for running commands like ag, ack, ripgrep, git and platinum searcher without any file names to support recursive searches. \r\n7. Move all the commands and their options into a separate table for simplified lookup. \r\n8. On MS-Windows, use findstr instead of grep for buffer list and argument list search commands. \r\n9. Refactor the code and simplify long functions. \r\n10. Changed the license to MIT license. \r\n","package":"grep.zip","4":"grep.zip","src_id":"25938","5":"25938","creation_date":"1524333129","6":"1524333129"},{"0":"311","vim_version":"7.0","1":"7.0","script_version":"2.0","2":"2.0","version_comment":"1. Added support for running the grep commands asynchronously (needs Vim version 8.0 and above).\r\n2. Added support for the silver searcher (ag), ripgrep and ack tools.\r\n3. Support for updating the correct quickfix list (if the quickfix identifier support is present).\r\n4. Escape the program path to handle space characters in program name.\r\n5. Convert the plugin into an autoloaded plugin.\r\n6. Move the documentation to a help file.","3":"1. Added support for running the grep commands asynchronously (needs Vim version 8.0 and above).\r\n2. Added support for the silver searcher (ag), ripgrep and ack tools.\r\n3. Support for updating the correct quickfix list (if the quickfix identifier support is present).\r\n4. Escape the program path to handle space characters in program name.\r\n5. Convert the plugin into an autoloaded plugin.\r\n6. Move the documentation to a help file.","package":"grep.zip","4":"grep.zip","src_id":"25816","5":"25816","creation_date":"1517797792","6":"1517797792"},{"0":"311","vim_version":"6.0","1":"6.0","script_version":"1.11","2":"1.11","version_comment":"Fixed a problem in using the \"Rgrep <pattern> <filenames>\" command.","3":"Fixed a problem in using the \"Rgrep <pattern> <filenames>\" command.","package":"grep.vim","4":"grep.vim","src_id":"19966","5":"19966","creation_date":"1367166972","6":"1367166972"},{"0":"311","vim_version":"6.0","1":"6.0","script_version":"1.10","2":"1.10","version_comment":"Fix the problem in running the grep command in MS-Windows because of command-line\r\nquoting issues.","3":"Fix the problem in running the grep command in MS-Windows because of command-line\r\nquoting issues.","package":"grep.vim","4":"grep.vim","src_id":"19921","5":"19921","creation_date":"1366780926","6":"1366780926"},{"0":"311","vim_version":"6.0","1":"6.0","script_version":"1.9","2":"1.9","version_comment":"New commands to add search results to the existing results.  New\r\nGrep_Xargs_Options variable to control the options passed to xargs.\r\nDon't echo newlines before running the commands.","3":"New commands to add search results to the existing results.  New\r\nGrep_Xargs_Options variable to control the options passed to xargs.\r\nDon't echo newlines before running the commands.","package":"grep.vim","4":"grep.vim","src_id":"7645","5":"7645","creation_date":"1189447987","6":"1189447987"},{"0":"311","vim_version":"6.0","1":"6.0","script_version":"1.8","2":"1.8","version_comment":"Support for expanding file and directory names in the search prompt. Fix for recursively searching for filenames with space characters in the name using find and xargs.","3":"Support for expanding file and directory names in the search prompt. Fix for recursively searching for filenames with space characters in the name using find and xargs.","package":"grep.vim","4":"grep.vim","src_id":"6868","5":"6868","creation_date":"1173767803","6":"1173767803"},{"0":"311","vim_version":"6.0","1":"6.0","script_version":"1.7","2":"1.7","version_comment":"Added filename completion support for grep commands. In GUI Vim, added Tools->Search menu item for using the Grep commands.","3":"Added filename completion support for grep commands. In GUI Vim, added Tools->Search menu item for using the Grep commands.","package":"grep.vim","4":"grep.vim","src_id":"5838","5":"5838","creation_date":"1150476759","6":"1150476759"},{"0":"311","vim_version":"6.0","1":"6.0","script_version":"1.6","2":"1.6","version_comment":"1. Add the search pattern to the search results.\r\n2. Support for the -h argument to the commands.\r\n3. Make the plugin work in Vi-compatible mode.\r\n4. Updated documentation.","3":"1. Add the search pattern to the search results.\r\n2. Support for the -h argument to the commands.\r\n3. Make the plugin work in Vi-compatible mode.\r\n4. Updated documentation.","package":"grep.vim","4":"grep.vim","src_id":"4484","5":"4484","creation_date":"1123684782","6":"1123684782"},{"0":"311","vim_version":"6.0","1":"6.0","script_version":"1.5","2":"1.5","version_comment":"Don't automatically jump to the first match in the grep output.","3":"Don't automatically jump to the first match in the grep output.","package":"grep.vim","4":"grep.vim","src_id":"4219","5":"4219","creation_date":"1114704604","6":"1114704604"},{"0":"311","vim_version":"6.0","1":"6.0","script_version":"1.4","2":"1.4","version_comment":"Support for specifying the grep flags, search pattern and filenames as argument to commands and other minor improvements.","3":"Support for specifying the grep flags, search pattern and filenames as argument to commands and other minor improvements.","package":"grep.vim","4":"grep.vim","src_id":"3579","5":"3579","creation_date":"1098876291","6":"1098876291"},{"0":"311","vim_version":"6.0","1":"6.0","script_version":"1.3","2":"1.3","version_comment":"Fixed file pattern quoting and special character escaping for MS-Windows.","3":"Fixed file pattern quoting and special character escaping for MS-Windows.","package":"grep.vim","4":"grep.vim","src_id":"916","5":"916","creation_date":"1023788171","6":"1023788171"}]},"310":{"script_id":"310","0":"310","script_name":"cream-sort","1":"cream-sort","script_type":"utility","2":"utility","summary":"sort a file by lines","3":"sort a file by lines","description":"\r\n:call Cream_sortfile() will sort the current file alphabetically by line. User is prompted to choose the column of the sort. The function uses the operating system's sort command (both Windows or Unix) for speed since our original use was for 7mb dictionary wordlists(!). (cream-sort actually creates and sorts a temp file copied from the current to preserve the original file since it would be destroyed by the OS during the process.) \r\n\r\nPlease notice three other sort libraries included within the script below the advertised first one. They were \"research\" during the project and may serve certain users better than ours!\r\n\r\nThis is one of the many custom utilities and functions for gVim from the Cream project (http:\/\/cream.sourceforge.net), a configuration of Vim in the vein of Apple and Windows software you already know.\r\n\r\n","4":"\r\n:call Cream_sortfile() will sort the current file alphabetically by line. User is prompted to choose the column of the sort. The function uses the operating system's sort command (both Windows or Unix) for speed since our original use was for 7mb dictionary wordlists(!). (cream-sort actually creates and sorts a temp file copied from the current to preserve the original file since it would be destroyed by the OS during the process.) \r\n\r\nPlease notice three other sort libraries included within the script below the advertised first one. They were \"research\" during the project and may serve certain users better than ours!\r\n\r\nThis is one of the many custom utilities and functions for gVim from the Cream project (http:\/\/cream.sourceforge.net), a configuration of Vim in the vein of Apple and Windows software you already know.\r\n\r\n","install_details":"\r\nJust copy this file and paste it into your vimrc. Or you can drop the entire file into your plugins directory.\r\n\r\n","5":"\r\nJust copy this file and paste it into your vimrc. Or you can drop the entire file into your plugins directory.\r\n\r\n","first_name":"Steve","6":"Steve","last_name":"Hall","7":"Hall","releases":[{"0":"310","vim_version":"6.0","1":"6.0","script_version":"1.3","2":"1.3","version_comment":"* Quote path\/filenames on Windows to handle spaces\r\n* Added requirement that file be named (external redirection methods\r\n  require it)\r\n* Added prompt to save modified file before proceeding\r\n","3":"* Quote path\/filenames on Windows to handle spaces\r\n* Added requirement that file be named (external redirection methods\r\n  require it)\r\n* Added prompt to save modified file before proceeding\r\n","package":"cream-sort.vim","4":"cream-sort.vim","src_id":"1201","5":"1201","creation_date":"1031648159","6":"1031648159"}]},"309":{"script_id":"309","0":"309","script_name":"CSV delimited field jumper","1":"CSV delimited field jumper","script_type":"utility","2":"utility","summary":"Map keys to easily jump to fields in CSV files","3":"Map keys to easily jump to fields in CSV files","description":"I wrote these simple functions to easily jump to specific fields in CSV (and tildle delimited) data\/text files.  There are two functions: one tells you the current field number the cursor is on, and the other prompts you for the field number to move to on the current line.\r\n\r\nAt work, all of our data files are CSV, so this has saved me countless hours verifying data.\r\n\r\nAt the bottom of mmfield.vim, you can specify which keys to map to the functions.","4":"I wrote these simple functions to easily jump to specific fields in CSV (and tildle delimited) data\/text files.  There are two functions: one tells you the current field number the cursor is on, and the other prompts you for the field number to move to on the current line.\r\n\r\nAt work, all of our data files are CSV, so this has saved me countless hours verifying data.\r\n\r\nAt the bottom of mmfield.vim, you can specify which keys to map to the functions.","install_details":"In your .vimrc file, add a line:\r\nautocmd BufRead *.dat,*.dme source mmfield.vim\r\n\r\nThis will source the mmfield.vim functions for when you edit files with extensions of .dat or .dme.","5":"In your .vimrc file, add a line:\r\nautocmd BufRead *.dat,*.dme source mmfield.vim\r\n\r\nThis will source the mmfield.vim functions for when you edit files with extensions of .dat or .dme.","first_name":"J","6":"J","last_name":"Robertson","7":"Robertson","releases":[{"0":"309","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"mmfield.vim","4":"mmfield.vim","src_id":"905","5":"905","creation_date":"1023440076","6":"1023440076"}]},"308":{"script_id":"308","0":"308","script_name":"fog colorscheme","1":"fog colorscheme","script_type":"color scheme","2":"color scheme","summary":"A gentle colorscheme for code editing.","3":"A gentle colorscheme for code editing.","description":"This color scheme is meant for the person that spends hours and hours and hours and... in vim and wants some contrast to help pick things out in the files they edit, but doesn't want **C**O**N**T**R**A**S**T**!\r\n","4":"This color scheme is meant for the person that spends hours and hours and hours and... in vim and wants some contrast to help pick things out in the files they edit, but doesn't want **C**O**N**T**R**A**S**T**!\r\n","install_details":"Put this script in your 'colors' folder.\r\n","5":"Put this script in your 'colors' folder.\r\n","first_name":"Thomas","6":"Thomas","last_name":"Kimpton","7":"Kimpton","releases":[{"0":"308","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"fog.vim","4":"fog.vim","src_id":"904","5":"904","creation_date":"1023375890","6":"1023375890"}]},"307":{"script_id":"307","0":"307","script_name":"xemacs colorscheme","1":"xemacs colorscheme","script_type":"color scheme","2":"color scheme","summary":"Vim with xemacs-like colors","3":"Vim with xemacs-like colors","description":"Copy it to your $HOME\/.vim\/colors and do a :colorscheme xemacs from within vim. I've tried to mimic xemacs\r\ncolors as best as I could, but suggestions would be very much welcome.","4":"Copy it to your $HOME\/.vim\/colors and do a :colorscheme xemacs from within vim. I've tried to mimic xemacs\r\ncolors as best as I could, but suggestions would be very much welcome.","install_details":"","5":"","first_name":"Joao","6":"Joao","last_name":"Estevao","7":"Estevao","releases":[{"0":"307","vim_version":"6.0","1":"6.0","script_version":"0.2","2":"0.2","version_comment":"Special now renders in navyblue so it can be easily seen.","3":"Special now renders in navyblue so it can be easily seen.","package":"xemacs.vim","4":"xemacs.vim","src_id":"2240","5":"2240","creation_date":"1061220692","6":"1061220692"},{"0":"307","vim_version":"6.0","1":"6.0","script_version":"0.1.1","2":"0.1.1","version_comment":"Forgot to change some hilights. Duh","3":"Forgot to change some hilights. Duh","package":"xemacs.vim","4":"xemacs.vim","src_id":"901","5":"901","creation_date":"1023259729","6":"1023259729"},{"0":"307","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"xemacs.vim","4":"xemacs.vim","src_id":"900","5":"900","creation_date":"1023258473","6":"1023258473"}]},"306":{"script_id":"306","0":"306","script_name":"gnome-doc.vim","1":"gnome-doc.vim","script_type":"utility","2":"utility","summary":"auto-generate C document headers for GTK+\/GNOME functions","3":"auto-generate C document headers for GTK+\/GNOME functions","description":"Add a document header to your function. The headers can be parsed and converted into documentation by the gtk-doc tools.","4":"Add a document header to your function. The headers can be parsed and converted into documentation by the gtk-doc tools.","install_details":"","5":"","first_name":"Arjan","6":"Arjan","last_name":"Molenaar","7":"Molenaar","releases":[{"0":"306","vim_version":"5.7","1":"5.7","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"gnome-doc.vim","4":"gnome-doc.vim","src_id":"896","5":"896","creation_date":"1022719575","6":"1022719575"}]},"305":{"script_id":"305","0":"305","script_name":"sql_iabbr.vim","1":"sql_iabbr.vim","script_type":"ftplugin","2":"ftplugin","summary":"Makes all your favorite SQL keywords uppercase automatically.","3":"Makes all your favorite SQL keywords uppercase automatically.","description":"With this ftplugin you can type \"create table foo (foo_id int);\" and get \"CREATE TABLE foo (foo_id INT);\".  It is based on both sql.vim and the output from postgresql's \\dT command while in psql.  That makes it a tad bit tailored to postgresql, but it will work with any SQL compliant dbms.  Please note that I am not an SQL wizard.  I just know how to copy and paste and use \":%s\/\/\/\".  :)  Enjoy!  Comments are welcome.  Many thanks to Hari Krishna Dara for improving this plugin and making it generally more useful.","4":"With this ftplugin you can type \"create table foo (foo_id int);\" and get \"CREATE TABLE foo (foo_id INT);\".  It is based on both sql.vim and the output from postgresql's \\dT command while in psql.  That makes it a tad bit tailored to postgresql, but it will work with any SQL compliant dbms.  Please note that I am not an SQL wizard.  I just know how to copy and paste and use \":%s\/\/\/\".  :)  Enjoy!  Comments are welcome.  Many thanks to Hari Krishna Dara for improving this plugin and making it generally more useful.","install_details":"Just stick in ~\/.vim\/ftplugin\/sql, and you're good to go.  ","5":"Just stick in ~\/.vim\/ftplugin\/sql, and you're good to go.  ","first_name":"Michael","6":"Michael","last_name":"Brailsford","7":"Brailsford","releases":[{"0":"305","vim_version":"6.0","1":"6.0","script_version":"1.5","2":"1.5","version_comment":"I added ^Xu map to undo the previous immediate capitalization. This will work\r\ncorrectly only when you are still next to the word for which you want to\r\nundo capitaliation and you have not left the insert mode since the\r\ncapitaliation was done.\r\n","3":"I added ^Xu map to undo the previous immediate capitalization. This will work\r\ncorrectly only when you are still next to the word for which you want to\r\nundo capitaliation and you have not left the insert mode since the\r\ncapitaliation was done.\r\n","package":"sql_iabbr.vim","4":"sql_iabbr.vim","src_id":"1414","5":"1414","creation_date":"1037203561","6":"1037203561"},{"0":"305","vim_version":"6.0","1":"6.0","script_version":"1.4","2":"1.4","version_comment":"- Added Zak Beck's contribution to ignore the words inside constants too.\r\n- Also for Vikas Agnihothri, exposed the function that expands the abbreviations conditionally as a global function. You can now use SqlIab_ReplaceConditionally() function anywhere in your scripts to add new abbreviations for sql files.","3":"- Added Zak Beck's contribution to ignore the words inside constants too.\r\n- Also for Vikas Agnihothri, exposed the function that expands the abbreviations conditionally as a global function. You can now use SqlIab_ReplaceConditionally() function anywhere in your scripts to add new abbreviations for sql files.","package":"sql_iabbr.vim","4":"sql_iabbr.vim","src_id":"1357","5":"1357","creation_date":"1036162129","6":"1036162129"},{"0":"305","vim_version":"6.0","1":"6.0","script_version":"1.3","2":"1.3","version_comment":"I have modified Michael's script to ignore the abbreviations if the same words are used inside comments. Since there is no other difference, you can even download the 1.2 version if you don't like this. Thanks to Michael for allowing me to upload into his space.","3":"I have modified Michael's script to ignore the abbreviations if the same words are used inside comments. Since there is no other difference, you can even download the 1.2 version if you don't like this. Thanks to Michael for allowing me to upload into his space.","package":"sql_iabbr.vim","4":"sql_iabbr.vim","src_id":"1224","5":"1224","creation_date":"1032450176","6":"1032450176"},{"0":"305","vim_version":"6.0","1":"6.0","script_version":"1.2","2":"1.2","version_comment":"Made all the abbreviations local to the buffer.  Now when editing sql and some other language in the same vim instance, typing \"create\" in the non-sql window will not be changed to \"CREATE\".","3":"Made all the abbreviations local to the buffer.  Now when editing sql and some other language in the same vim instance, typing \"create\" in the non-sql window will not be changed to \"CREATE\".","package":"sql_iabbr.vim","4":"sql_iabbr.vim","src_id":"984","5":"984","creation_date":"1025693666","6":"1025693666"},{"0":"305","vim_version":"6.0","1":"6.0","script_version":"1.1","2":"1.1","version_comment":"Added a few keywords that I found missing as I used the script.","3":"Added a few keywords that I found missing as I used the script.","package":"sql_iabbr.vim","4":"sql_iabbr.vim","src_id":"913","5":"913","creation_date":"1023712160","6":"1023712160"},{"0":"305","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"sql_iabbr.vim","4":"sql_iabbr.vim","src_id":"895","5":"895","creation_date":"1022711831","6":"1022711831"}]},"304":{"script_id":"304","0":"304","script_name":"pyimp.vim","1":"pyimp.vim","script_type":"utility","2":"utility","summary":"load python file from import statement","3":"load python file from import statement","description":"Set of functions to open a Python import statement as a file.\r\nThis is a modification of javaimp.vim by Darren Greaves <darren@krapplets.org> http:\/\/boncey.org\/vim.shtml\r\nSuggested stuff to add to your ~.vimrc:\r\nlet $PYTHONSOURCEPATH=\"\/usr\/lib\/python2.2\/,\/usr\/lib\/python2.2\/lib,\/usr\/lib\/python2.2\/site-packages,~\/python\"\r\nmap H :call OpenPythonImport($PYTHONSOURCEPATH)<CR>\r\nThen press H while on a import line and the file should open (you'll need the\r\nsource files and the path to have been set already.\r\n\r\nThe paths in $PYTHONSOURCEPATH should have the source packages directly\r\nunderneath each path.  The script needs to be able to add the package to the\r\npath element and open a file.\r\n\r\nI still need to figure out how to load the \"from blah.bleh.blih import yada\" type of imports","4":"Set of functions to open a Python import statement as a file.\r\nThis is a modification of javaimp.vim by Darren Greaves <darren@krapplets.org> http:\/\/boncey.org\/vim.shtml\r\nSuggested stuff to add to your ~.vimrc:\r\nlet $PYTHONSOURCEPATH=\"\/usr\/lib\/python2.2\/,\/usr\/lib\/python2.2\/lib,\/usr\/lib\/python2.2\/site-packages,~\/python\"\r\nmap H :call OpenPythonImport($PYTHONSOURCEPATH)<CR>\r\nThen press H while on a import line and the file should open (you'll need the\r\nsource files and the path to have been set already.\r\n\r\nThe paths in $PYTHONSOURCEPATH should have the source packages directly\r\nunderneath each path.  The script needs to be able to add the package to the\r\npath element and open a file.\r\n\r\nI still need to figure out how to load the \"from blah.bleh.blih import yada\" type of imports","install_details":"Vim 6:  Copy to ~\/.vim\/plugin or $VIM\/plugin directory\r\n","5":"Vim 6:  Copy to ~\/.vim\/plugin or $VIM\/plugin directory\r\n","first_name":"Tom","6":"Tom","last_name":"Jenkins","7":"Jenkins","releases":[{"0":"304","vim_version":"6.0","1":"6.0","script_version":"0.2","2":"0.2","version_comment":"Now has rudimentary loading for \"from\" type imports. ","3":"Now has rudimentary loading for \"from\" type imports. ","package":"pyimp.vim","4":"pyimp.vim","src_id":"899","5":"899","creation_date":"1023116987","6":"1023116987"},{"0":"304","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"pyimp.vim","4":"pyimp.vim","src_id":"893","5":"893","creation_date":"1022703864","6":"1022703864"}]},"303":{"script_id":"303","0":"303","script_name":"ftplugin\/ruby.vim","1":"ftplugin\/ruby.vim","script_type":"ftplugin","2":"ftplugin","summary":"Ruby filetype plugin with matchit, lots more","3":"Ruby filetype plugin with matchit, lots more","description":"This is a pretty complete Ruby filetype script.\r\nIt provides for the use of matchit.vim, as well as setting the include path correctly (by calling ruby if you have it). It also deals with the possibility of :: in identifiers, both for tags and for finding keywords.","4":"This is a pretty complete Ruby filetype script.\r\nIt provides for the use of matchit.vim, as well as setting the include path correctly (by calling ruby if you have it). It also deals with the possibility of :: in identifiers, both for tags and for finding keywords.","install_details":"Copy the script to your local (or global) ftplugin directory. This should be on your 'runtimepath'. On Unix systems, this could be in your ~\/.vim\/ftplugin directory.\r\nThe current stock ruby.vim shouldn't get in the way.\r\n\r\nTo get matchit.vim to work, you have to move it from the stock $VIMRUNTIME\/macros to the $VIMRUNTIME\/plugin directory. Or at least you have to have matchit.vim in a plugin directory on your runtimepath.\r\n\r\nIf you want to tweak the settings any, just make another ruby.vim in an ftplugin directory at the end of the runtimepath. On Unix systems, this would ordinarily be ~\/.vim\/after\/ftplugin","5":"Copy the script to your local (or global) ftplugin directory. This should be on your 'runtimepath'. On Unix systems, this could be in your ~\/.vim\/ftplugin directory.\r\nThe current stock ruby.vim shouldn't get in the way.\r\n\r\nTo get matchit.vim to work, you have to move it from the stock $VIMRUNTIME\/macros to the $VIMRUNTIME\/plugin directory. Or at least you have to have matchit.vim in a plugin directory on your runtimepath.\r\n\r\nIf you want to tweak the settings any, just make another ruby.vim in an ftplugin directory at the end of the runtimepath. On Unix systems, this would ordinarily be ~\/.vim\/after\/ftplugin","first_name":"Ned","6":"Ned","last_name":"Konz","7":"Konz","releases":[{"0":"303","vim_version":"6.0","1":"6.0","script_version":"1.8","2":"1.8","version_comment":"changed shellquote logic for compatibility with *csh.","3":"changed shellquote logic for compatibility with *csh.","package":"ruby.vim","4":"ruby.vim","src_id":"1071","5":"1071","creation_date":"1028200427","6":"1028200427"},{"0":"303","vim_version":"6.0","1":"6.0","script_version":"1.7","2":"1.7","version_comment":"Fixed end at beginning of line","3":"Fixed end at beginning of line","package":"ruby.vim","4":"ruby.vim","src_id":"941","5":"941","creation_date":"1024698606","6":"1024698606"}]},"302":{"script_id":"302","0":"302","script_name":"AnsiEsc.vim","1":"AnsiEsc.vim","script_type":"syntax","2":"syntax","summary":"ansi escape sequences concealed, but highlighted as specified (conceal)","3":"ansi escape sequences concealed, but highlighted as specified (conceal)","description":"Files with ANSI escape sequences look good when dumped onto a terminal that accepts them, but heretofore have been a distracting clutter when edited via vim.  The AnsiEsc.vim file, when sourced with vim 7.3 or later, will conceal Ansi escape sequences but will cause subsequent text to be colored as the escape sequence specifies.\r\n\r\nYou need to have a vim with conceal mode enabled; use has(\"conceal\") to find out if the vim you're using has that feature.\r\n\r\nWithout that conceal feature or with vim versions earlier than 7.3, the best that can be done is to suppress Ansi escape sequences with \"Ignore\" highlighting.  AnsiEsc.vim v2 does that.\r\n\r\nCutting edge versions are available at http:\/\/www.drchip.org\/astronaut\/vim\/index.html#ANSIESC .\r\n\r\nUsage:  edit a file containing escape sequences, then type :AnsiEsc\r\n","4":"Files with ANSI escape sequences look good when dumped onto a terminal that accepts them, but heretofore have been a distracting clutter when edited via vim.  The AnsiEsc.vim file, when sourced with vim 7.3 or later, will conceal Ansi escape sequences but will cause subsequent text to be colored as the escape sequence specifies.\r\n\r\nYou need to have a vim with conceal mode enabled; use has(\"conceal\") to find out if the vim you're using has that feature.\r\n\r\nWithout that conceal feature or with vim versions earlier than 7.3, the best that can be done is to suppress Ansi escape sequences with \"Ignore\" highlighting.  AnsiEsc.vim v2 does that.\r\n\r\nCutting edge versions are available at http:\/\/www.drchip.org\/astronaut\/vim\/index.html#ANSIESC .\r\n\r\nUsage:  edit a file containing escape sequences, then type :AnsiEsc\r\n","install_details":"vim AnsiEsc.vba.gz\r\n:so %\r\n:q\r\n","5":"vim AnsiEsc.vba.gz\r\n:so %\r\n:q\r\n","first_name":"Charles","6":"Charles","last_name":"Campbell","7":"Campbell","releases":[{"0":"302","vim_version":"7.0","1":"7.0","script_version":"12","2":"12","version_comment":"* changed conc -> cole for vim 7.3's built-in conceal mode\r\n* included some additional escape sequences","3":"* changed conc -> cole for vim 7.3's built-in conceal mode\r\n* included some additional escape sequences","package":"AnsiEsc.vba.gz","4":"AnsiEsc.vba.gz","src_id":"14498","5":"14498","creation_date":"1292273107","6":"1292273107"},{"0":"302","vim_version":"7.0","1":"7.0","script_version":"11","2":"11","version_comment":"supports several escape sequences such as <esc>[m , <esc>[2J, and <esc>[H.","3":"supports several escape sequences such as <esc>[m , <esc>[2J, and <esc>[H.","package":"AnsiEsc.vba.gz","4":"AnsiEsc.vba.gz","src_id":"13236","5":"13236","creation_date":"1277235111","6":"1277235111"},{"0":"302","vim_version":"7.0","1":"7.0","script_version":"10","2":"10","version_comment":"AnsiEsc has 1 and 2 Ansi escape code sequences supported by fixed syntax highlighting rules; it now also builds custom syntax highlighting to support 3 and 4 Ansi Escape code sequences based on your current document.  So  \\e[48;5;16m will now cause correct highlighting to follow, for example.\r\n","3":"AnsiEsc has 1 and 2 Ansi escape code sequences supported by fixed syntax highlighting rules; it now also builds custom syntax highlighting to support 3 and 4 Ansi Escape code sequences based on your current document.  So  \\e[48;5;16m will now cause correct highlighting to follow, for example.\r\n","package":"AnsiEsc.vba.gz","4":"AnsiEsc.vba.gz","src_id":"12795","5":"12795","creation_date":"1270671403","6":"1270671403"},{"0":"302","vim_version":"7.0","1":"7.0","script_version":"9","2":"9","version_comment":"* AnsiEsc comes in plugin + autoload format: faster vim startup, and AnsiEsc only when you want it.\r\n* Now provides a :AnsiEsc command totoggle ANSI escape sequence processing.\r\n\r\nWorks with Vince Negri's conceal patch (if your vim supports VN's conceal, then the ansi-escape sequences are suppressed except on the line you're editing).","3":"* AnsiEsc comes in plugin + autoload format: faster vim startup, and AnsiEsc only when you want it.\r\n* Now provides a :AnsiEsc command totoggle ANSI escape sequence processing.\r\n\r\nWorks with Vince Negri's conceal patch (if your vim supports VN's conceal, then the ansi-escape sequences are suppressed except on the line you're editing).","package":"AnsiEsc.vba.gz","4":"AnsiEsc.vba.gz","src_id":"10244","5":"10244","creation_date":"1237392426","6":"1237392426"},{"0":"302","vim_version":"7.0","1":"7.0","script_version":"8","2":"8","version_comment":"Uses vim7.0's undercurl as a substitute for blinking (which Vim doesn't support), contains a small helpfile, and contains directions for getting Vince Negri's conceal patch for vim 7.0.","3":"Uses vim7.0's undercurl as a substitute for blinking (which Vim doesn't support), contains a small helpfile, and contains directions for getting Vince Negri's conceal patch for vim 7.0.","package":"AnsiEsc.vba.gz","4":"AnsiEsc.vba.gz","src_id":"6072","5":"6072","creation_date":"1155714012","6":"1155714012"},{"0":"302","vim_version":"6.0","1":"6.0","script_version":"2","2":"2","version_comment":"I mistakenly removed AnsiEsc v2 (which is the version which doesn't use Vince Negri's conceal).  This update restores it!\r\n","3":"I mistakenly removed AnsiEsc v2 (which is the version which doesn't use Vince Negri's conceal).  This update restores it!\r\n","package":"AnsiEsc_v2.vim","4":"AnsiEsc_v2.vim","src_id":"3653","5":"3653","creation_date":"1101276934","6":"1101276934"}]},"301":{"script_id":"301","0":"301","script_name":"xmledit","1":"xmledit","script_type":"ftplugin","2":"ftplugin","summary":"A filetype plugin to help edit XML, HTML, and SGML documents","3":"A filetype plugin to help edit XML, HTML, and SGML documents","description":"This script provides some convenience when editing XML (and some SGML including\r\nHTML) formated documents. It allows you to jump to the beginning or end of the\r\ntag block your cursor is in. '%' will jump between '<' and '>' within the tag\r\nyour cursor is in. When in insert mode and you finish a tag (pressing '>') the\r\ntag will be completed. If you press '>' twice it will complete the tag and\r\nplace the cursor in the middle of the tags on it's own line.\r\n\r\nFor the latest development snapshot visit\r\n    http:\/\/github.com\/sukima\/xmledit\/\r\n\r\nPlease fork this project. We need help making this better.","4":"This script provides some convenience when editing XML (and some SGML including\r\nHTML) formated documents. It allows you to jump to the beginning or end of the\r\ntag block your cursor is in. '%' will jump between '<' and '>' within the tag\r\nyour cursor is in. When in insert mode and you finish a tag (pressing '>') the\r\ntag will be completed. If you press '>' twice it will complete the tag and\r\nplace the cursor in the middle of the tags on it's own line.\r\n\r\nFor the latest development snapshot visit\r\n    http:\/\/github.com\/sukima\/xmledit\/\r\n\r\nPlease fork this project. We need help making this better.","install_details":"This new version has the documentation coupled with the script. You only need one file xml.vim.\r\n\r\nPlace this file in your ftplugin directory (i.e. '~\/.vim\/ftplugin\/xml.vim) Type :help ftplugins for more information on installation.\r\n\r\nThe documentation will install automatically the first time the plugin is ran. *NOTE* the first time the plugin is ran is NOT the first time VIM is ran. Because this is a file plugin you have to open an XML document to execute the script. So open a new test.xml file at first.\r\n\r\nThe html.vim script that came with the old tarball is now in the documentation as an example. to use it just copy\/paste it into the file html.vim. See :help xml-plugin-html after the documentation installs.\r\n\r\nChangeLog and older versions availiable on request.","5":"This new version has the documentation coupled with the script. You only need one file xml.vim.\r\n\r\nPlace this file in your ftplugin directory (i.e. '~\/.vim\/ftplugin\/xml.vim) Type :help ftplugins for more information on installation.\r\n\r\nThe documentation will install automatically the first time the plugin is ran. *NOTE* the first time the plugin is ran is NOT the first time VIM is ran. Because this is a file plugin you have to open an XML document to execute the script. So open a new test.xml file at first.\r\n\r\nThe html.vim script that came with the old tarball is now in the documentation as an example. to use it just copy\/paste it into the file html.vim. See :help xml-plugin-html after the documentation installs.\r\n\r\nChangeLog and older versions availiable on request.","first_name":"Devin","6":"Devin","last_name":"Weaver","7":"Weaver","releases":[{"0":"301","vim_version":"7.0","1":"7.0","script_version":"1.9.1","2":"1.9.1","version_comment":"Adds a global disable switch\r\n\r\nUpdated to vimball packaging (compatible with pathogeon)","3":"Adds a global disable switch\r\n\r\nUpdated to vimball packaging (compatible with pathogeon)","package":"xmledit-1.9.1.vba","4":"xmledit-1.9.1.vba","src_id":"13387","5":"13387","creation_date":"1279831521","6":"1279831521"},{"0":"301","vim_version":"7.0","1":"7.0","script_version":"1.84","2":"1.84","version_comment":"Latest development build after move to Git repository. No new features.","3":"Latest development build after move to Git repository. No new features.","package":"xml.vim","4":"xml.vim","src_id":"10362","5":"10362","creation_date":"1239119151","6":"1239119151"},{"0":"301","vim_version":"6.0","1":"6.0","script_version":"1.29","2":"1.29","version_comment":"Fixed some documentation. Added <a> tag to html example.\r\nAdded Visual select tag mapping. Cosmetics","3":"Fixed some documentation. Added <a> tag to html example.\r\nAdded Visual select tag mapping. Cosmetics","package":"xml.vim","4":"xml.vim","src_id":"4280","5":"4280","creation_date":"1116084389","6":"1116084389"}]},"300":{"script_id":"300","0":"300","script_name":"Vimacs","1":"Vimacs","script_type":"utility","2":"utility","summary":"Vim-Improved eMACS: Emacs emulation for Vim","3":"Vim-Improved eMACS: Emacs emulation for Vim","description":"Vimacs (Vim-Improved eMACS) brings Emacs's extensive key bindings and modeless editing features to the Vim world, while completely retaining Vim's powerful moded editing style.\r\n\r\nVimacs is based on the keymaps of GNU Emacs 21 and XEmacs, so if you are familiar with them, you'll feel right at home in Vimacs.  For Emacs users, most (if not all) of the common key maps in Emacs are present in Vimacs, such as <C-Space>, <C-w> and <C-y> to mark, kill and yank regions, <C-x><C-f> to find a file, and <C-x>2 to vertically split a window.  However, you can now take advantage of the incredible power of Vim's Normal and Command modes with a touch of the <Esc> key.\r\n\r\nIf you're a long-time Vim user, you retain vi's powerful moded editing paradigm while gaining all the benefits of Emacs' modeless editing.  After a while, the <C-a> and <C-e> keys will become second nature to you, just as you're used to the h, j, k, and l keys for movement.  Some of the keys familiar to you in Insert mode have been changed, but you won't take long to get used to Emacs's keys: just like Vim, Emacs's key layout has been designed so that commonly used keys are quick to access.\r\n\r\nSee the homepage at http:\/\/www.algorithm.com.au\/code\/vimacs\/ for more information.","4":"Vimacs (Vim-Improved eMACS) brings Emacs's extensive key bindings and modeless editing features to the Vim world, while completely retaining Vim's powerful moded editing style.\r\n\r\nVimacs is based on the keymaps of GNU Emacs 21 and XEmacs, so if you are familiar with them, you'll feel right at home in Vimacs.  For Emacs users, most (if not all) of the common key maps in Emacs are present in Vimacs, such as <C-Space>, <C-w> and <C-y> to mark, kill and yank regions, <C-x><C-f> to find a file, and <C-x>2 to vertically split a window.  However, you can now take advantage of the incredible power of Vim's Normal and Command modes with a touch of the <Esc> key.\r\n\r\nIf you're a long-time Vim user, you retain vi's powerful moded editing paradigm while gaining all the benefits of Emacs' modeless editing.  After a while, the <C-a> and <C-e> keys will become second nature to you, just as you're used to the h, j, k, and l keys for movement.  Some of the keys familiar to you in Insert mode have been changed, but you won't take long to get used to Emacs's keys: just like Vim, Emacs's key layout has been designed so that commonly used keys are quick to access.\r\n\r\nSee the homepage at http:\/\/www.algorithm.com.au\/code\/vimacs\/ for more information.","install_details":"Grab the .tar.gz if you're using Unix, and the .zip file if you're using Windows (or any other platform, like MacOS).\r\n\r\nVimacs is a standard Vim plugin, so just put the vimacs.vim file in your plugin directory, and put vimacs.txt in your documentation directory.  That's it!  If you're using Unix, you should also read the INSTALL text file that comes with Vimacs for notes on how to run Vim with or without Vimacs.","5":"Grab the .tar.gz if you're using Unix, and the .zip file if you're using Windows (or any other platform, like MacOS).\r\n\r\nVimacs is a standard Vim plugin, so just put the vimacs.vim file in your plugin directory, and put vimacs.txt in your documentation directory.  That's it!  If you're using Unix, you should also read the INSTALL text file that comes with Vimacs for notes on how to run Vim with or without Vimacs.","first_name":"Andre","6":"Andre","last_name":"Pang","7":"Pang","releases":[{"0":"300","vim_version":"6.0","1":"6.0","script_version":"0.93","2":"0.93","version_comment":"For Windows and other (non-Unix) platforms.","3":"For Windows and other (non-Unix) platforms.","package":"vimacs-0.93.zip","4":"vimacs-0.93.zip","src_id":"878","5":"878","creation_date":"1021722855","6":"1021722855"},{"0":"300","vim_version":"6.0","1":"6.0","script_version":"0.93","2":"0.93","version_comment":"Initial upload","3":"Initial upload","package":"vimacs-0.93.tar.gz","4":"vimacs-0.93.tar.gz","src_id":"877","5":"877","creation_date":"1021722807","6":"1021722807"}]},"299":{"script_id":"299","0":"299","script_name":"TabIndent","1":"TabIndent","script_type":"utility","2":"utility","summary":"Overload the <Tab> key to either insert a tab, or indent the current line","3":"Overload the <Tab> key to either insert a tab, or indent the current line","description":"The TabIndent plugin allows you use the <Tab> key in Insert mode to indent the current line, as well as retain its usual task of inserting a real <Tab> character.  TabIndent exhibits a bit of intelligence by making sure that the current line is only indented if you're editing source code, by checking the 'cindent' and 'indentexpr' options.  Editing text files will never cause the <Tab> key to perform indentation.\r\n\r\nYou can also change the behaviour of when indentation is performed; some people prefer <Tab> to always perform indentation, and others may want to indent only if the cursor is at the start of the line.  TabIndent is designed to make every user work the way they want to.","4":"The TabIndent plugin allows you use the <Tab> key in Insert mode to indent the current line, as well as retain its usual task of inserting a real <Tab> character.  TabIndent exhibits a bit of intelligence by making sure that the current line is only indented if you're editing source code, by checking the 'cindent' and 'indentexpr' options.  Editing text files will never cause the <Tab> key to perform indentation.\r\n\r\nYou can also change the behaviour of when indentation is performed; some people prefer <Tab> to always perform indentation, and others may want to indent only if the cursor is at the start of the line.  TabIndent is designed to make every user work the way they want to.","install_details":"Standard Vim plugin.  Unzip file, place tab-indent.vim file in your plugin directory, place tab-indent.txt file in your doc directory.  Have fun!","5":"Standard Vim plugin.  Unzip file, place tab-indent.vim file in your plugin directory, place tab-indent.txt file in your doc directory.  Have fun!","first_name":"Andre","6":"Andre","last_name":"Pang","7":"Pang","releases":[{"0":"299","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"tabindent-1.0.zip","4":"tabindent-1.0.zip","src_id":"876","5":"876","creation_date":"1021720915","6":"1021720915"}]},"298":{"script_id":"298","0":"298","script_name":"vimfortune","1":"vimfortune","script_type":"utility","2":"utility","summary":"Show random tips when launching VIM","3":"Show random tips when launching VIM","description":"This simple script shows you a random tip using 'fortune' program when launching VIM\r\nwithout specifying filename(s) to edit(ie. '%vim' and not '%vim foobar.c').\r\nYou can also explicitly view a tip by typing\r\n:TIPS\r\nor\r\n:!fortune vimtips\r\n\r\nIncluded are pre-formatted datafiles converted from the vim tips available from:\r\nhttp:\/\/vim.sourceforge.net\/tips\/download.php","4":"This simple script shows you a random tip using 'fortune' program when launching VIM\r\nwithout specifying filename(s) to edit(ie. '%vim' and not '%vim foobar.c').\r\nYou can also explicitly view a tip by typing\r\n:TIPS\r\nor\r\n:!fortune vimtips\r\n\r\nIncluded are pre-formatted datafiles converted from the vim tips available from:\r\nhttp:\/\/vim.sourceforge.net\/tips\/download.php","install_details":"You should have 'fortune' installed (normally, you already have one if using un*x-like OS).\r\nCopy the datafiles to the data directory of fortune, and the script to the script directory of VIM. \r\nExample:\r\n% cp vimtips vimtips.dat \/usr\/share\/games\/fortune\r\n% cp vimfortune.vim ~\/.vim\/plugin","5":"You should have 'fortune' installed (normally, you already have one if using un*x-like OS).\r\nCopy the datafiles to the data directory of fortune, and the script to the script directory of VIM. \r\nExample:\r\n% cp vimtips vimtips.dat \/usr\/share\/games\/fortune\r\n% cp vimfortune.vim ~\/.vim\/plugin","first_name":"key","6":"key","last_name":"","7":"","releases":[{"0":"298","vim_version":"6.0","1":"6.0","script_version":"0.1.1","2":"0.1.1","version_comment":"Initial upload","3":"Initial upload","package":"vimfortune-011.tgz","4":"vimfortune-011.tgz","src_id":"871","5":"871","creation_date":"1021361433","6":"1021361433"}]},"297":{"script_id":"297","0":"297","script_name":"latextags","1":"latextags","script_type":"utility","2":"utility","summary":"Perl script to generate tags for LaTeX files.","3":"Perl script to generate tags for LaTeX files.","description":"This is a perl script to generate tags\r\nfor Latex files. The script generates\r\ntags for labels, newcommands and bibliography\r\nitems. \r\nThis is script was derived from Michael Schaap's\r\npltags.pl script.\r\nThe format of the tags file is usable from VIM.","4":"This is a perl script to generate tags\r\nfor Latex files. The script generates\r\ntags for labels, newcommands and bibliography\r\nitems. \r\nThis is script was derived from Michael Schaap's\r\npltags.pl script.\r\nThe format of the tags file is usable from VIM.","install_details":"","5":"","first_name":"michael","6":"michael","last_name":"muhler","7":"muhler","releases":[{"0":"297","vim_version":"6.0","1":"6.0","script_version":"1.5","2":"1.5","version_comment":"fixed multiple braces bug, fix by Manoj, thanks!\r\nAdded some thoughts on how to integrate\r\ninto Vim.\r\n","3":"fixed multiple braces bug, fix by Manoj, thanks!\r\nAdded some thoughts on how to integrate\r\ninto Vim.\r\n","package":"latextags.pl","4":"latextags.pl","src_id":"1892","5":"1892","creation_date":"1049369710","6":"1049369710"},{"0":"297","vim_version":"6.0","1":"6.0","script_version":"1.4","2":"1.4","version_comment":"Initial upload","3":"Initial upload","package":"latextags.pl","4":"latextags.pl","src_id":"870","5":"870","creation_date":"1021348698","6":"1021348698"}]},"296":{"script_id":"296","0":"296","script_name":"showbrace","1":"showbrace","script_type":"ftplugin","2":"ftplugin","summary":"Shows line that matches the entered curlybrace","3":"Shows line that matches the entered curlybrace","description":"\r\nA simple script I made for editing Java source. When an ending curly-brace } is inserted the script\r\nshows the line with the opening brace on the statusline.\r\n\r\nOnly works when noshowmode is set.","4":"\r\nA simple script I made for editing Java source. When an ending curly-brace } is inserted the script\r\nshows the line with the opening brace on the statusline.\r\n\r\nOnly works when noshowmode is set.","install_details":"","5":"","first_name":"Tatu","6":"Tatu","last_name":"Tarvainen","7":"Tarvainen","releases":[{"0":"296","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"showbrace.vim","4":"showbrace.vim","src_id":"868","5":"868","creation_date":"1021103774","6":"1021103774"}]},"295":{"script_id":"295","0":"295","script_name":"bluegreen","1":"bluegreen","script_type":"color scheme","2":"color scheme","summary":"dark green and blue colorscheme","3":"dark green and blue colorscheme","description":"this is another colorscheme by me, featuring a dark blue and green motif.","4":"this is another colorscheme by me, featuring a dark blue and green motif.","install_details":"just drop it in $HOME\/.vim\/colors\/ and do a :colorscheme bluegreen","5":"just drop it in $HOME\/.vim\/colors\/ and do a :colorscheme bluegreen","first_name":"Joao","6":"Joao","last_name":"Estevao","7":"Estevao","releases":[{"0":"295","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"bluegreen.vim","4":"bluegreen.vim","src_id":"863","5":"863","creation_date":"1021017913","6":"1021017913"}]},"294":{"script_id":"294","0":"294","script_name":"Align","1":"Align","script_type":"utility","2":"utility","summary":"Help folks to align text, eqns, declarations, tables, etc","3":"Help folks to align text, eqns, declarations, tables, etc","description":"                                                    [ALIGN\/ALIGNMAPS NEEDS VIM 7.0 AS OF V29\/34]\r\n\r\nAlign and AlignMaps lets you align statements on their equal signs, make comment boxes, align comments, align declarations, etc.\r\n\r\nNote: this plugin is not a left&right margin justification tool!  See vimscript#177, vimscript#2324, or vimscript#3728 for that.\r\nNote: if you have vim 7.1 or later, your vimball should unpack just fine without having to update it.\r\n\r\nThere are two basic commands provided by this package:\r\n\r\n        AlignCtrl options sep1 sep2 sep3 ...\r\n        [range]Align sep1 sep2 sep3 ...\r\n\r\nThe \"sep#\" are regular expressions which describe separators that delineate fields; Align will line up the separators. The range may be any Vim range, _including_ visual-blocks.  Align works on lines of the form:\r\n(ws==whitespace, sep==separator, field==text)\r\n\r\n    ws-field-ws-sep-ws-field-ws-sep-ws-field-...\r\n    ws-field-ws-sep-ws-field-ws-sep-ws-field-...\r\n\r\nNote that white-space (ws) surrounding separators is ignored.\r\n\r\nThe Align package includes:\r\n\r\n  Align : the basic alignment command\r\n  AlignCtrl : provides options for the next call to :Align\r\n  AlignMaps : many three or four key maps which support aligning C\/C++ style declarations, ()?..:.., expressions, C\/C++ comments, numbers, C preprocessor definitions, tables based on tabs or spaces, and more.\r\n\r\nIn addition, AutoAlign (vimscript#884) uses the Align function to align =s as you type.\r\n\r\nAlign handles alignment on multiple separators, not just the first one, and the separators may be the same across the line or different.  With AlignCtrl one may specify that separators are cyclic (re-used sequentially) or equivalent (all separators are simultaneously active).\r\n\r\nThere are several options to help with deciding what to do with initial white space.   By default Align re-uses the first line's initial white space, but one may use AlignCtrl to retain or remove each line's initial white space.\r\n\r\nThe <Align.vim> and <AlignMaps.vim> files are plugins and require vim 6.1 or higher.\r\n\r\n\r\nEXAMPLES:\r\n\r\n:5,10Align =\r\n    Align on '=' signs\r\n\r\n:'<,'>Align = + - \\* \/\r\n    Align on any of the five separator characters shown.\r\n    Note that visual block mode was used to fire off Align.\r\n\r\n:AlignCtrl =lp1P1I\r\n    which means:\r\n    = all separators are equivalent\r\n    l fields will be left-justified\r\n    p1 pad one space before each separator\r\n    P1 pad one space after each separator\r\n    I  preserve and apply the first line's leading white space to all\r\n       Align'd lines\r\n\r\n:help align\r\n    Gives help for Align\r\n\r\n\r\nALIGNMENT CONTROL\r\n\r\nAlignment control allows for left or right justification or centering of fields, cyclic (sequentially active) or equivalent (simultaneously active) regular expressions to specify field separators, initial white space control, optional visual-block use (ie. apply Alignment only within a block), user-specified white-space padding about separators, and multiple separators.\r\n\r\nMANY ALIGNMENT MAPS\r\n\r\nAlignMaps.vim provides a number of maps which make using this package easy.  They typically either apply to the range 'a,. (from mark a to current line) or use the visual-selection (V, v, or ctrl-v selected):\r\n\r\n\t\\t=  : align assignments (don't count logic, like == or !=)\r\n\t\\t,  : align on commas\r\n\t\\t|  : align on vertical bars (|)\r\n\t\\tsp : align on whitespace\r\n\t\\tt  : align LaTeX tabular tables\r\n\r\nAlignMaps also provides some internally complex maps for aligning C declarations, Ansi C function arguments, html tables, LaTeX tabulars, and trailing comments:\r\n\r\n\t\\acom : align comments\r\n\t\\adec : align C declarations (one variable per line)\r\n\t\\afnc : align ansi-style C function input arguments\r\n\t\\Htd  : align html tables\r\n\t\r\nTo see some examples of this, check out\r\n\r\n    http:\/\/www.drchip.org\/astronaut\/vim\/align.html#Examples\r\n\r\n(the proportional fonts used by most browsers in showing you this page preclude showing the examples here). The help for Align and AlignCtrl also contains many examples.\r\n(for those of you who prefer not to have the maps that AlignMaps.vim provides, simply remove the AlignMapsPlugin.vim from .vim\/plugin and AlignMaps.vim from .vim\/autoload - that's why AlignMaps is separate from Align)\r\n\r\nALIGNMENT ON VISUAL BLOCKS AND g,v-LIKE CONTROL\r\n\r\nSometimes one wants to align only a subset of text in a range, based on patterns or column extents.  Align supports both types of restrictions!\r\n    \r\n    Visual-block selection may be used to restrict Align to operate only\r\n    within that visual block.\r\n    \r\n    AlignCtrl supports \"g\" and \"v\" patterns that restrict Align to\r\n\r\n    operate on lines which match (or don't match, respectively) those\r\n    patterns.\r\n\r\nNEW STUFF:\r\n\r\nThere's a number of new AlignCtrl options:\r\n    \r\n    - allows one to skip a separator (treat it as part of a field)\r\n    + repeat the last lrc justification (ex. lr+ == lrrrrrr... )\r\n    : treat the rest of the line as a field; acts as a modifier\r\n      to the last lrc. \r\n    < left-justify the separator\r\n    > right-justify the separator\r\n    | center the separator\r\n\r\nThese are, except for the \":\", cyclic parameters.  In other words, >< is equivalent to ><><><><... .  Thus separators can be of differing lengths (ex.  -\\+ as a separator pattern can match -, --, ---, etc and the separators will be left\/right\/center justified as you wish).\r\n\r\nTo get automatic, as-you-type, aligning of = in the C, vimL, and other languages, check out vimscript#884 for several ftplugins (which use Align).\r\n\r\n\r\nAlternative Aligners:\r\n    Gergely Kontra's vimscript#176\r\n\r\nThank you for rating Align!\r\n\r\n---------------------------------------\r\nDISCUSSION and COMMENTS:\r\n---------------------------------------\r\n\r\nPlease use email for bugs.  Enjoy!\r\n\r\n(alpha\/beta version available at http:\/\/mysite.verizon.net\/astronaut\/vim\/index.html#ALIGN)\r\n","4":"                                                    [ALIGN\/ALIGNMAPS NEEDS VIM 7.0 AS OF V29\/34]\r\n\r\nAlign and AlignMaps lets you align statements on their equal signs, make comment boxes, align comments, align declarations, etc.\r\n\r\nNote: this plugin is not a left&right margin justification tool!  See vimscript#177, vimscript#2324, or vimscript#3728 for that.\r\nNote: if you have vim 7.1 or later, your vimball should unpack just fine without having to update it.\r\n\r\nThere are two basic commands provided by this package:\r\n\r\n        AlignCtrl options sep1 sep2 sep3 ...\r\n        [range]Align sep1 sep2 sep3 ...\r\n\r\nThe \"sep#\" are regular expressions which describe separators that delineate fields; Align will line up the separators. The range may be any Vim range, _including_ visual-blocks.  Align works on lines of the form:\r\n(ws==whitespace, sep==separator, field==text)\r\n\r\n    ws-field-ws-sep-ws-field-ws-sep-ws-field-...\r\n    ws-field-ws-sep-ws-field-ws-sep-ws-field-...\r\n\r\nNote that white-space (ws) surrounding separators is ignored.\r\n\r\nThe Align package includes:\r\n\r\n  Align : the basic alignment command\r\n  AlignCtrl : provides options for the next call to :Align\r\n  AlignMaps : many three or four key maps which support aligning C\/C++ style declarations, ()?..:.., expressions, C\/C++ comments, numbers, C preprocessor definitions, tables based on tabs or spaces, and more.\r\n\r\nIn addition, AutoAlign (vimscript#884) uses the Align function to align =s as you type.\r\n\r\nAlign handles alignment on multiple separators, not just the first one, and the separators may be the same across the line or different.  With AlignCtrl one may specify that separators are cyclic (re-used sequentially) or equivalent (all separators are simultaneously active).\r\n\r\nThere are several options to help with deciding what to do with initial white space.   By default Align re-uses the first line's initial white space, but one may use AlignCtrl to retain or remove each line's initial white space.\r\n\r\nThe <Align.vim> and <AlignMaps.vim> files are plugins and require vim 6.1 or higher.\r\n\r\n\r\nEXAMPLES:\r\n\r\n:5,10Align =\r\n    Align on '=' signs\r\n\r\n:'<,'>Align = + - \\* \/\r\n    Align on any of the five separator characters shown.\r\n    Note that visual block mode was used to fire off Align.\r\n\r\n:AlignCtrl =lp1P1I\r\n    which means:\r\n    = all separators are equivalent\r\n    l fields will be left-justified\r\n    p1 pad one space before each separator\r\n    P1 pad one space after each separator\r\n    I  preserve and apply the first line's leading white space to all\r\n       Align'd lines\r\n\r\n:help align\r\n    Gives help for Align\r\n\r\n\r\nALIGNMENT CONTROL\r\n\r\nAlignment control allows for left or right justification or centering of fields, cyclic (sequentially active) or equivalent (simultaneously active) regular expressions to specify field separators, initial white space control, optional visual-block use (ie. apply Alignment only within a block), user-specified white-space padding about separators, and multiple separators.\r\n\r\nMANY ALIGNMENT MAPS\r\n\r\nAlignMaps.vim provides a number of maps which make using this package easy.  They typically either apply to the range 'a,. (from mark a to current line) or use the visual-selection (V, v, or ctrl-v selected):\r\n\r\n\t\\t=  : align assignments (don't count logic, like == or !=)\r\n\t\\t,  : align on commas\r\n\t\\t|  : align on vertical bars (|)\r\n\t\\tsp : align on whitespace\r\n\t\\tt  : align LaTeX tabular tables\r\n\r\nAlignMaps also provides some internally complex maps for aligning C declarations, Ansi C function arguments, html tables, LaTeX tabulars, and trailing comments:\r\n\r\n\t\\acom : align comments\r\n\t\\adec : align C declarations (one variable per line)\r\n\t\\afnc : align ansi-style C function input arguments\r\n\t\\Htd  : align html tables\r\n\t\r\nTo see some examples of this, check out\r\n\r\n    http:\/\/www.drchip.org\/astronaut\/vim\/align.html#Examples\r\n\r\n(the proportional fonts used by most browsers in showing you this page preclude showing the examples here). The help for Align and AlignCtrl also contains many examples.\r\n(for those of you who prefer not to have the maps that AlignMaps.vim provides, simply remove the AlignMapsPlugin.vim from .vim\/plugin and AlignMaps.vim from .vim\/autoload - that's why AlignMaps is separate from Align)\r\n\r\nALIGNMENT ON VISUAL BLOCKS AND g,v-LIKE CONTROL\r\n\r\nSometimes one wants to align only a subset of text in a range, based on patterns or column extents.  Align supports both types of restrictions!\r\n    \r\n    Visual-block selection may be used to restrict Align to operate only\r\n    within that visual block.\r\n    \r\n    AlignCtrl supports \"g\" and \"v\" patterns that restrict Align to\r\n\r\n    operate on lines which match (or don't match, respectively) those\r\n    patterns.\r\n\r\nNEW STUFF:\r\n\r\nThere's a number of new AlignCtrl options:\r\n    \r\n    - allows one to skip a separator (treat it as part of a field)\r\n    + repeat the last lrc justification (ex. lr+ == lrrrrrr... )\r\n    : treat the rest of the line as a field; acts as a modifier\r\n      to the last lrc. \r\n    < left-justify the separator\r\n    > right-justify the separator\r\n    | center the separator\r\n\r\nThese are, except for the \":\", cyclic parameters.  In other words, >< is equivalent to ><><><><... .  Thus separators can be of differing lengths (ex.  -\\+ as a separator pattern can match -, --, ---, etc and the separators will be left\/right\/center justified as you wish).\r\n\r\nTo get automatic, as-you-type, aligning of = in the C, vimL, and other languages, check out vimscript#884 for several ftplugins (which use Align).\r\n\r\n\r\nAlternative Aligners:\r\n    Gergely Kontra's vimscript#176\r\n\r\nThank you for rating Align!\r\n\r\n---------------------------------------\r\nDISCUSSION and COMMENTS:\r\n---------------------------------------\r\n\r\nPlease use email for bugs.  Enjoy!\r\n\r\n(alpha\/beta version available at http:\/\/mysite.verizon.net\/astronaut\/vim\/index.html#ALIGN)\r\n","install_details":"1. You'll need to have plugins enabled: in your home directory, have at least the following two lines in your .vimrc file:\r\n   set nocp\r\n   filetype plugin on\r\n\r\n2. Using vim 7.1 or later:\r\n  vim Align.vba.gz\r\n   :so %\r\n   :q\r\n\r\n3. Using vim 7.0: see http:\/\/mysite.verizon.net\/astronaut\/vim\/index.html#VIMBALL to get and install an up-to-date version of vimball.  Then follow the simple directions for installation of Align\/AlignMaps above!  Or, preferably: upgrade your copy of vim.\r\n\r\n(this version of Align\/AlignMaps requires vim 7.0)\r\n","5":"1. You'll need to have plugins enabled: in your home directory, have at least the following two lines in your .vimrc file:\r\n   set nocp\r\n   filetype plugin on\r\n\r\n2. Using vim 7.1 or later:\r\n  vim Align.vba.gz\r\n   :so %\r\n   :q\r\n\r\n3. Using vim 7.0: see http:\/\/mysite.verizon.net\/astronaut\/vim\/index.html#VIMBALL to get and install an up-to-date version of vimball.  Then follow the simple directions for installation of Align\/AlignMaps above!  Or, preferably: upgrade your copy of vim.\r\n\r\n(this version of Align\/AlignMaps requires vim 7.0)\r\n","first_name":"Charles","6":"Charles","last_name":"Campbell","7":"Campbell","releases":[{"0":"294","vim_version":"7.0","1":"7.0","script_version":"37\/43","2":"37\/43","version_comment":"(Align) has visual maps to accompany all normal mode mappings (use V to invoke them)\r\n(Align) a bugfix (cursor moved when g:Align_xstrlen=3)\r\n(AlignMaps) use nnoremaps instead of nmaps","3":"(Align) has visual maps to accompany all normal mode mappings (use V to invoke them)\r\n(Align) a bugfix (cursor moved when g:Align_xstrlen=3)\r\n(AlignMaps) use nnoremaps instead of nmaps","package":"Align.vba.gz","4":"Align.vba.gz","src_id":"19633","5":"19633","creation_date":"1363124907","6":"1363124907"},{"0":"294","vim_version":"7.3","1":"7.3","script_version":"36\/42","2":"36\/42","version_comment":"new     : users may specify a function to decide whether or not a character should be skipped with the AlignCtrl \\\"*\\\" character\r\nnew     : Align will automatically grow the range if the given range is only one line to accommodate all lines which match the first separator pattern\r\nimproved: AlignMaps\\' \\\\anum, \\\\aenum, \\\\aunum and \\\\t=, \\\\T=\r\nbugfixes: various; see :help align-history\r\n","3":"new     : users may specify a function to decide whether or not a character should be skipped with the AlignCtrl \\\"*\\\" character\r\nnew     : Align will automatically grow the range if the given range is only one line to accommodate all lines which match the first separator pattern\r\nimproved: AlignMaps\\' \\\\anum, \\\\aenum, \\\\aunum and \\\\t=, \\\\T=\r\nbugfixes: various; see :help align-history\r\n","package":"Align.vba.gz","4":"Align.vba.gz","src_id":"18148","5":"18148","creation_date":"1340047312","6":"1340047312"},{"0":"294","vim_version":"7.0","1":"7.0","script_version":"35\/41","2":"35\/41","version_comment":"Align: save and restore of mod now done with the local version of the option\r\nAlign: new sanity check for an AlignStyle of just \":\"\r\nAlignMaps: new maps: \\ts; ts: \\ts< \\ts= \\a(\r\nAlignMaps: default g:Align_xstrlen often is now 1 for multi-byte support\r\nAlignMaps: bug fixed for \\ts,\r\n","3":"Align: save and restore of mod now done with the local version of the option\r\nAlign: new sanity check for an AlignStyle of just \":\"\r\nAlignMaps: new maps: \\ts; ts: \\ts< \\ts= \\a(\r\nAlignMaps: default g:Align_xstrlen often is now 1 for multi-byte support\r\nAlignMaps: bug fixed for \\ts,\r\n","package":"Align.vba.gz","4":"Align.vba.gz","src_id":"10110","5":"10110","creation_date":"1236175367","6":"1236175367"},{"0":"294","vim_version":"7.0","1":"7.0","script_version":"34\/40","2":"34\/40","version_comment":"(AlignMaps) split into plugin\/ and autoload\/ sections (faster [g]vim startup)\r\n(AlignMaps) maps use <Plug>s and <script>s: allowing users to invoke the maps how they wish, and preventing user maps from interfering with the internal workings of the maps.\r\n(Align)     bugfix - using :AlignCtrl before entering any alignment ctrl cmds was causing an error\r\n","3":"(AlignMaps) split into plugin\/ and autoload\/ sections (faster [g]vim startup)\r\n(AlignMaps) maps use <Plug>s and <script>s: allowing users to invoke the maps how they wish, and preventing user maps from interfering with the internal workings of the maps.\r\n(Align)     bugfix - using :AlignCtrl before entering any alignment ctrl cmds was causing an error\r\n","package":"Align.vba.gz","4":"Align.vba.gz","src_id":"9414","5":"9414","creation_date":"1225313151","6":"1225313151"},{"0":"294","vim_version":"6.0","1":"6.0","script_version":"33\/39","2":"33\/39","version_comment":"* Align now aligns multi-byte characters correctly (see :help align-strlen) -- choose g:Align_xstrlen for the type of codepoint you want handled.\r\n\r\n* Align now accepts \\\"...\\\" arguments, so one can pass whitespace to Align as a separator\r\n\r\n* AlignMaps\\' \\\\t= map now avoids comment aligning when the filetype is not *.c or *.cpp","3":"* Align now aligns multi-byte characters correctly (see :help align-strlen) -- choose g:Align_xstrlen for the type of codepoint you want handled.\r\n\r\n* Align now accepts \\\"...\\\" arguments, so one can pass whitespace to Align as a separator\r\n\r\n* AlignMaps\\' \\\\t= map now avoids comment aligning when the filetype is not *.c or *.cpp","package":"Align.vba.gz","4":"Align.vba.gz","src_id":"8407","5":"8407","creation_date":"1204827574","6":"1204827574"},{"0":"294","vim_version":"7.0","1":"7.0","script_version":"32\/38","2":"32\/38","version_comment":"The <leader>tt map wasn't working right; Align now uses <q-args> instead of <f-args>, so it does the argument splitting itself, thus allowing patterns containing backslashes to be used without lots of backslash-duplication.  This allows the \\tt map in AlignMaps to work, and to work without a lot of extra backslashes.","3":"The <leader>tt map wasn't working right; Align now uses <q-args> instead of <f-args>, so it does the argument splitting itself, thus allowing patterns containing backslashes to be used without lots of backslash-duplication.  This allows the \\tt map in AlignMaps to work, and to work without a lot of extra backslashes.","package":"Align.vba.gz","4":"Align.vba.gz","src_id":"7531","5":"7531","creation_date":"1187604557","6":"1187604557"},{"0":"294","vim_version":"7.0","1":"7.0","script_version":"31\/36","2":"31\/36","version_comment":"New feature -- one can embed AlignCtrl settings into Align (as a one-shot):\r\n\r\n   [range]Align! [AlignCtrl settings] pattern(s)\r\n\r\nPlus some small improvements to some of the AlignMaps.","3":"New feature -- one can embed AlignCtrl settings into Align (as a one-shot):\r\n\r\n   [range]Align! [AlignCtrl settings] pattern(s)\r\n\r\nPlus some small improvements to some of the AlignMaps.","package":"Align.vba.gz","4":"Align.vba.gz","src_id":"7511","5":"7511","creation_date":"1187272421","6":"1187272421"},{"0":"294","vim_version":"7.0","1":"7.0","script_version":"30\/35","2":"30\/35","version_comment":"* \\acom can now work with doxygen style \/\/\/ comments\r\n* \\t= and cousins used \"`\"s.  They now use \\xff characters.\r\n* <char-0xff> used in \\t= \\T= \\w= and \\m= instead of backquotes.\r\n","3":"* \\acom can now work with doxygen style \/\/\/ comments\r\n* \\t= and cousins used \"`\"s.  They now use \\xff characters.\r\n* <char-0xff> used in \\t= \\T= \\w= and \\m= instead of backquotes.\r\n","package":"Align.vba.gz","4":"Align.vba.gz","src_id":"6210","5":"6210","creation_date":"1158738746","6":"1158738746"},{"0":"294","vim_version":"7.0","1":"7.0","script_version":"29\/34","2":"29\/34","version_comment":"Align and AlignMaps now use vim 7.0 style autoloading (quicker startup, loads only when used)\r\ncecutil updated to use keepjumps\r\nNow being distributed as a vimball - simply :so % it after decompressing it to install\r\n","3":"Align and AlignMaps now use vim 7.0 style autoloading (quicker startup, loads only when used)\r\ncecutil updated to use keepjumps\r\nNow being distributed as a vimball - simply :so % it after decompressing it to install\r\n","package":"Align.vba.gz","4":"Align.vba.gz","src_id":"5608","5":"5608","creation_date":"1145948850","6":"1145948850"},{"0":"294","vim_version":"6.0","1":"6.0","script_version":"28\/33","2":"28\/33","version_comment":"bugfix: (Align) Align now works around the report option setting.\r\nbugfix: (Align) AlignCtrl l: wasn't behaving as expected; fixed!\r\nbugfix: (AlignMap) \\ts, now uses P1 in its AlignCtrl call\r\n","3":"bugfix: (Align) Align now works around the report option setting.\r\nbugfix: (Align) AlignCtrl l: wasn't behaving as expected; fixed!\r\nbugfix: (AlignMap) \\ts, now uses P1 in its AlignCtrl call\r\n","package":"Align.tar.gz","4":"Align.tar.gz","src_id":"4788","5":"4788","creation_date":"1132559038","6":"1132559038"},{"0":"294","vim_version":"6.0","1":"6.0","script_version":"27\/32","2":"27\/32","version_comment":"Align v27 : cpo and ignorecase workarounds\r\nAlignMaps v32: s:WrapperStart() -> AlignWrapperStart(), s:WrapperEnd() -> AlignWrapperEnd()\r\n These changes let the wrappers be used outside of AlignMaps.vim (customized map support)\r\n","3":"Align v27 : cpo and ignorecase workarounds\r\nAlignMaps v32: s:WrapperStart() -> AlignWrapperStart(), s:WrapperEnd() -> AlignWrapperEnd()\r\n These changes let the wrappers be used outside of AlignMaps.vim (customized map support)\r\n","package":"Align.tar.gz","4":"Align.tar.gz","src_id":"4421","5":"4421","creation_date":"1121147801","6":"1121147801"},{"0":"294","vim_version":"6.0","1":"6.0","script_version":"27\/31","2":"27\/31","version_comment":"Align: GetLatestVimScripts\/AutoInstall supported\r\nAlignMaps: new map: \\\\adcom (align declaration-style comments), \\\\a, now wors across multiple lines with different types, cecutil.vim now used, more number alignment maps (\\\\aenum, \\\\aunum)\r\n","3":"Align: GetLatestVimScripts\/AutoInstall supported\r\nAlignMaps: new map: \\\\adcom (align declaration-style comments), \\\\a, now wors across multiple lines with different types, cecutil.vim now used, more number alignment maps (\\\\aenum, \\\\aunum)\r\n","package":"Align.tar.gz","4":"Align.tar.gz","src_id":"4167","5":"4167","creation_date":"1113564092","6":"1113564092"}]},"293":{"script_id":"293","0":"293","script_name":"utl.vim","1":"utl.vim","script_type":"utility","2":"utility","summary":"Univeral Text Linking - Execute URLs, footnotes, open emails, organize ideas","3":"Univeral Text Linking - Execute URLs, footnotes, open emails, organize ideas","description":"--- WHAT IS UTL.VIM?\r\n\r\nIt brings the benefits of URL-based hyperlinking to plain text, extending the\r\nURL syntax for plain text needs, in accordance with the RFC 2396 (towards\r\ncurrent RFC 3986) URL specification.\r\n\r\nUtl is very easy to start. Just  :so %  the .vba file and dive into the live examples\r\nof the doc.\r\n\r\n--- USAGES\r\n\r\n- Open any URLs found in text with appropriate handler\r\n- Open files of any media type from within Vim (.pdf, .jpg, etc)\r\n- Small helper utilities via embedded Vimscript\r\n- Project management\r\n- Organizing ideas\r\n- Commenting source code\r\n- Personal Wiki\r\n- Editing HTML\r\n- Bookmark files, directories, URLs\r\n\r\n--- CHARACTERISTICS\r\n\r\n- Well documented and helpful verbose mode\r\n- Is easy to get started\r\n- Stays out of the way, no side effects\r\n- Extensible\r\n\r\n--- KEYWORDS\r\nHypertext, URL, URI, email, footnotes, Wiki, bookmarks\r\n\r\n--- CHANGES SINCE UTL V2.0\r\n\r\nThe most important changes are:\r\n\r\n- Added generic media type handler: open .pdf, .doc,\r\n  .jpg etc without the need to define handler variables.\r\n- Added support for footnote references: make \"[1]\"\r\n  executable.\r\n- Added scheme to open emails, e.g.\r\n  <mail:\/\/\/Inbox?26.07.2008 16:01>\r\n- Added verbose mode: Better figure out what's going on\r\n- Added 'copy link\/filename to clipboard' function\r\n- Changed user interface: Basic Command :Utl instead\r\n  only mapping \\gu\r\n- Alternate http access method: open web documents\r\n  directly in Vim\r\n- Support network files (shares, NFS), e.g.\r\n  <file:\/\/127.0.0.1\/path\/to\/file>\r\n- Improved jumping back and forth\r\n- More versatile scheme handler interface\r\n- Fixed Bugs\r\n\r\n--- EXAMPLES\r\n\r\nFor live examples and tutorial you can have a look into the docs\r\nwithout installing by opening the download link below and search\r\nfor \"getStarted\"","4":"--- WHAT IS UTL.VIM?\r\n\r\nIt brings the benefits of URL-based hyperlinking to plain text, extending the\r\nURL syntax for plain text needs, in accordance with the RFC 2396 (towards\r\ncurrent RFC 3986) URL specification.\r\n\r\nUtl is very easy to start. Just  :so %  the .vba file and dive into the live examples\r\nof the doc.\r\n\r\n--- USAGES\r\n\r\n- Open any URLs found in text with appropriate handler\r\n- Open files of any media type from within Vim (.pdf, .jpg, etc)\r\n- Small helper utilities via embedded Vimscript\r\n- Project management\r\n- Organizing ideas\r\n- Commenting source code\r\n- Personal Wiki\r\n- Editing HTML\r\n- Bookmark files, directories, URLs\r\n\r\n--- CHARACTERISTICS\r\n\r\n- Well documented and helpful verbose mode\r\n- Is easy to get started\r\n- Stays out of the way, no side effects\r\n- Extensible\r\n\r\n--- KEYWORDS\r\nHypertext, URL, URI, email, footnotes, Wiki, bookmarks\r\n\r\n--- CHANGES SINCE UTL V2.0\r\n\r\nThe most important changes are:\r\n\r\n- Added generic media type handler: open .pdf, .doc,\r\n  .jpg etc without the need to define handler variables.\r\n- Added support for footnote references: make \"[1]\"\r\n  executable.\r\n- Added scheme to open emails, e.g.\r\n  <mail:\/\/\/Inbox?26.07.2008 16:01>\r\n- Added verbose mode: Better figure out what's going on\r\n- Added 'copy link\/filename to clipboard' function\r\n- Changed user interface: Basic Command :Utl instead\r\n  only mapping \\gu\r\n- Alternate http access method: open web documents\r\n  directly in Vim\r\n- Support network files (shares, NFS), e.g.\r\n  <file:\/\/127.0.0.1\/path\/to\/file>\r\n- Improved jumping back and forth\r\n- More versatile scheme handler interface\r\n- Fixed Bugs\r\n\r\n--- EXAMPLES\r\n\r\nFor live examples and tutorial you can have a look into the docs\r\nwithout installing by opening the download link below and search\r\nfor \"getStarted\"","install_details":"Download the utl_3_0a.vba file and open it in a Vim. Then follow\r\nthe instructions (:so %).\r\n    ","5":"Download the utl_3_0a.vba file and open it in a Vim. Then follow\r\nthe instructions (:so %).\r\n    ","first_name":"Stefan","6":"Stefan","last_name":"Bittner","7":"Bittner","releases":[{"0":"293","vim_version":"7.0","1":"7.0","script_version":"3.0a ALPHA","2":"3.0a ALPHA","version_comment":"The most important changes are:\r\n- Added generic media type handler: open .pdf, .doc,\r\n  .jpg etc without the need to define handler variables.\r\n- Added support for footnote references: make \"[1]\"\r\n  executable.\r\n- Added scheme to open emails, e.g.\r\n  <mail:\/\/\/Inbox?26.07.2008 16:01>\r\n- Added verbose mode: Better figure out what's going\r\n- Added 'copy link\/filename to clipboard' function\r\n- Changed user interface: Basic Command :Utl instead\r\n  only mapping \\gu\r\n- Alternate http access method: open web documents\r\n  directly in Vim\r\n- Support network files (shares, NFS), e.g.\r\n  <file:\/\/127.0.0.1\/path\/to\/file>\r\n- Improved jumping back and forth\r\n- More versatile scheme handler interface\r\n- Fixed Bugs","3":"The most important changes are:\r\n- Added generic media type handler: open .pdf, .doc,\r\n  .jpg etc without the need to define handler variables.\r\n- Added support for footnote references: make \"[1]\"\r\n  executable.\r\n- Added scheme to open emails, e.g.\r\n  <mail:\/\/\/Inbox?26.07.2008 16:01>\r\n- Added verbose mode: Better figure out what's going\r\n- Added 'copy link\/filename to clipboard' function\r\n- Changed user interface: Basic Command :Utl instead\r\n  only mapping \\gu\r\n- Alternate http access method: open web documents\r\n  directly in Vim\r\n- Support network files (shares, NFS), e.g.\r\n  <file:\/\/127.0.0.1\/path\/to\/file>\r\n- Improved jumping back and forth\r\n- More versatile scheme handler interface\r\n- Fixed Bugs","package":"utl_3_0a.vba","4":"utl_3_0a.vba","src_id":"9060","5":"9060","creation_date":"1217517576","6":"1217517576"},{"0":"293","vim_version":"6.0","1":"6.0","script_version":"2.0","2":"2.0","version_comment":"Successor of Thlnk.vim with many new features:\r\n* Call web browser and email client on URLs (configurable scheme handlers),\r\n* Call MS-Word on .doc files, Acrobat Reader on .pdf, IrfanView on .jpg etc.\r\n  (configurable media type handlers)\r\n* New vimscript: protocol for embedding vim commands into text files and source code.\r\n* Syntax highlighting of URLs\r\n* Support for URL heuristics, e.g. allow www.vim.org, not only http:\/\/www.vim.org\r\n* Support exeuction of URLs without <URL:...> embedding, e.g. \"see www.vim.org\"\r\n* Support multiline URLs, Smart setup and customization facility, bugs fixed.\r\n","3":"Successor of Thlnk.vim with many new features:\r\n* Call web browser and email client on URLs (configurable scheme handlers),\r\n* Call MS-Word on .doc files, Acrobat Reader on .pdf, IrfanView on .jpg etc.\r\n  (configurable media type handlers)\r\n* New vimscript: protocol for embedding vim commands into text files and source code.\r\n* Syntax highlighting of URLs\r\n* Support for URL heuristics, e.g. allow www.vim.org, not only http:\/\/www.vim.org\r\n* Support exeuction of URLs without <URL:...> embedding, e.g. \"see www.vim.org\"\r\n* Support multiline URLs, Smart setup and customization facility, bugs fixed.\r\n","package":"utl-2_0_0.zip","4":"utl-2_0_0.zip","src_id":"4085","5":"4085","creation_date":"1111910979","6":"1111910979"},{"0":"293","vim_version":"6.0","1":"6.0","script_version":"1.2.1","2":"1.2.1","version_comment":"Please see release notes for version 1.2. The reason for this version 1.2.1 is, that I\r\npacked the .vim files with the wrong 'fileformats' setting into the .zip file. Sorry!","3":"Please see release notes for version 1.2. The reason for this version 1.2.1 is, that I\r\npacked the .vim files with the wrong 'fileformats' setting into the .zip file. Sorry!","package":"thlnk-1.2.1.zip","4":"thlnk-1.2.1.zip","src_id":"927","5":"927","creation_date":"1024131850","6":"1024131850"},{"0":"293","vim_version":"6.0","1":"6.0","script_version":"1.2","2":"1.2","version_comment":"- New section \"Tips and Common Pitfails\" added to the docs. Enhanced Documentation.\r\n- Enhanced warning and error messages.\r\n- Bug fixes:\r\n  * {Visual}\\gu didn't work on Windows gVim without guioptions+=a set.\r\n  * Klaus Horsten <horsten@gmx.at>: With 'wrapscan' unset, fragment addressing could fail.\r\n  * Patrik Nyman <patrik.nyman@orient.su.se>: Non existing http: or rcp: URLs made thlnk\r\n    list the current buffer.","3":"- New section \"Tips and Common Pitfails\" added to the docs. Enhanced Documentation.\r\n- Enhanced warning and error messages.\r\n- Bug fixes:\r\n  * {Visual}\\gu didn't work on Windows gVim without guioptions+=a set.\r\n  * Klaus Horsten <horsten@gmx.at>: With 'wrapscan' unset, fragment addressing could fail.\r\n  * Patrik Nyman <patrik.nyman@orient.su.se>: Non existing http: or rcp: URLs made thlnk\r\n    list the current buffer.","package":"thlnk-1.2.zip","4":"thlnk-1.2.zip","src_id":"926","5":"926","creation_date":"1024125634","6":"1024125634"}]},"292":{"script_id":"292","0":"292","script_name":"xian.vim","1":"xian.vim","script_type":"color scheme","2":"color scheme","summary":"kind'a pastel colorscheme (dark bg, GUI only)","3":"kind'a pastel colorscheme (dark bg, GUI only)","description":"based on a dark background color I saw\r\non a web page some time back.\r\n\r\nComments are welcome.\r\nChristian","4":"based on a dark background color I saw\r\non a web page some time back.\r\n\r\nComments are welcome.\r\nChristian","install_details":"Just upload in $VIM\/vim61\/colors","5":"Just upload in $VIM\/vim61\/colors","first_name":"Christian","6":"Christian","last_name":"MICHON","7":"MICHON","releases":[{"0":"292","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"xian.vim","4":"xian.vim","src_id":"850","5":"850","creation_date":"1020802942","6":"1020802942"}]},"291":{"script_id":"291","0":"291","script_name":"autodate.vim","1":"autodate.vim","script_type":"utility","2":"utility","summary":"A customizable plugin to update time stamps automatically.","3":"A customizable plugin to update time stamps automatically.","description":"This plugin inserts and updates a time stamp automatically.\r\n\r\nUsers can specify a format and position of the time stamp by options.\r\nBy default, autodate.vim searches a keyword \"Last Change:.\"\r\nin the first 50 lines of the buffer, and inserts a time stamp.  Example: \r\n    Last Change: 24-Jun-2003. \r\n\r\nSetting Example:\r\n    :let b:autodate_keyword_pre = '<!--DATE-->'\r\n    :let b:autodate_keyword_post = '<!--DATE-->'\r\n    :let b:autodate_format = '%Y\/%m\/%d'\r\nThe Result:\r\n    <!--DATE-->2003\/06\/24<!--DATE-->\r\n\r\nSee comments in autodate.vim for more details.","4":"This plugin inserts and updates a time stamp automatically.\r\n\r\nUsers can specify a format and position of the time stamp by options.\r\nBy default, autodate.vim searches a keyword \"Last Change:.\"\r\nin the first 50 lines of the buffer, and inserts a time stamp.  Example: \r\n    Last Change: 24-Jun-2003. \r\n\r\nSetting Example:\r\n    :let b:autodate_keyword_pre = '<!--DATE-->'\r\n    :let b:autodate_keyword_post = '<!--DATE-->'\r\n    :let b:autodate_format = '%Y\/%m\/%d'\r\nThe Result:\r\n    <!--DATE-->2003\/06\/24<!--DATE-->\r\n\r\nSee comments in autodate.vim for more details.","install_details":"Put the file in ~\/.vim\/plugin\/ directory.","5":"Put the file in ~\/.vim\/plugin\/ directory.","first_name":"Taro","6":"Taro","last_name":"MURAOKA","7":"MURAOKA","releases":[{"0":"291","vim_version":"6.0","1":"6.0","script_version":"1.0.2","2":"1.0.2","version_comment":"Add \"%[0-9]a\" format, which is replaced with locale independed English day name string.","3":"Add \"%[0-9]a\" format, which is replaced with locale independed English day name string.","package":"autodate.vim","4":"autodate.vim","src_id":"2106","5":"2106","creation_date":"1056392807","6":"1056392807"}]},"290":{"script_id":"290","0":"290","script_name":"ruby-matchit","1":"ruby-matchit","script_type":"utility","2":"utility","summary":"'Matchit' for Ruby.","3":"'Matchit' for Ruby.","description":"Map '%' to jump from one keyword to its corresponding 'end' in Ruby files. Inspired by 'matchit.vim' that comes with Vim.\r\n\r\n","4":"Map '%' to jump from one keyword to its corresponding 'end' in Ruby files. Inspired by 'matchit.vim' that comes with Vim.\r\n\r\n","install_details":"Put the file in ~\/.vim\/ftplugin\/ruby\/ directory or copy its contents to ~\/.vim\/ftplugin\/ruby.vim","5":"Put the file in ~\/.vim\/ftplugin\/ruby\/ directory or copy its contents to ~\/.vim\/ftplugin\/ruby.vim","first_name":"Johannes","6":"Johannes","last_name":"Tanzler","7":"Tanzler","releases":[{"0":"290","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"ruby-matchit.vim","4":"ruby-matchit.vim","src_id":"848","5":"848","creation_date":"1020697349","6":"1020697349"}]},"289":{"script_id":"289","0":"289","script_name":"serverlist.vim","1":"serverlist.vim","script_type":"utility","2":"utility","summary":"Switch between VIM windows quickly","3":"Switch between VIM windows quickly","description":"Script creates key mappings for each existing VIM window.  After sourcing the script, you can press \\a in normal mode to switch to window 1, \\b for window 2, etc.  The keys are broadcasted to each window, such that the same key always map to the same window.  \\. will show mapping for current window.","4":"Script creates key mappings for each existing VIM window.  After sourcing the script, you can press \\a in normal mode to switch to window 1, \\b for window 2, etc.  The keys are broadcasted to each window, such that the same key always map to the same window.  \\. will show mapping for current window.","install_details":"to run, :source serverlist.vim\r\nVIM needs to be compiled with +clientserver\r\n\r\nyou can also place script in plugins directory to create shortcut keys automatically, but that will increase VIM startup time considerably (quadratic to number of windows), so be careful.","5":"to run, :source serverlist.vim\r\nVIM needs to be compiled with +clientserver\r\n\r\nyou can also place script in plugins directory to create shortcut keys automatically, but that will increase VIM startup time considerably (quadratic to number of windows), so be careful.","first_name":"Don","6":"Don","last_name":"Yang","7":"Yang","releases":[{"0":"289","vim_version":"6.0","1":"6.0","script_version":"1.31","2":"1.31","version_comment":"always delay mapping windows until buffer is available (bugfix)","3":"always delay mapping windows until buffer is available (bugfix)","package":"serverlist.vim","4":"serverlist.vim","src_id":"2805","5":"2805","creation_date":"1078440102","6":"1078440102"},{"0":"289","vim_version":"6.0","1":"6.0","script_version":"1.3","2":"1.3","version_comment":"compatibility fixes for 6.2","3":"compatibility fixes for 6.2","package":"serverlist.vim","4":"serverlist.vim","src_id":"2039","5":"2039","creation_date":"1054559341","6":"1054559341"},{"0":"289","vim_version":"6.0","1":"6.0","script_version":"1.22","2":"1.22","version_comment":"window cycling now works in both directions.","3":"window cycling now works in both directions.","package":"serverlist.vim","4":"serverlist.vim","src_id":"1489","5":"1489","creation_date":"1038309384","6":"1038309384"},{"0":"289","vim_version":"6.0","1":"6.0","script_version":"1.21","2":"1.21","version_comment":"Fix to get around cmap <C-V> issue (for mswin.vim users)","3":"Fix to get around cmap <C-V> issue (for mswin.vim users)","package":"serverlist.vim","4":"serverlist.vim","src_id":"1264","5":"1264","creation_date":"1033398583","6":"1033398583"},{"0":"289","vim_version":"6.0","1":"6.0","script_version":"1.2","2":"1.2","version_comment":"Add key mapping to cycle windows.","3":"Add key mapping to cycle windows.","package":"serverlist.vim","4":"serverlist.vim","src_id":"1253","5":"1253","creation_date":"1033236675","6":"1033236675"},{"0":"289","vim_version":"6.0","1":"6.0","script_version":"1.1","2":"1.1","version_comment":"Preserve existing keymappings.","3":"Preserve existing keymappings.","package":"serverlist.vim","4":"serverlist.vim","src_id":"959","5":"959","creation_date":"1025169540","6":"1025169540"},{"0":"289","vim_version":"6.0","1":"6.0","script_version":"1.01","2":"1.01","version_comment":"bugfix for insert mode","3":"bugfix for insert mode","package":"serverlist.vim","4":"serverlist.vim","src_id":"956","5":"956","creation_date":"1025102914","6":"1025102914"},{"0":"289","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Added key mapping to show shortcut for current window.","3":"Added key mapping to show shortcut for current window.","package":"serverlist.vim","4":"serverlist.vim","src_id":"955","5":"955","creation_date":"1025091131","6":"1025091131"},{"0":"289","vim_version":"6.0","1":"6.0","script_version":"0.9","2":"0.9","version_comment":".","3":".","package":"serverlist.vim","4":"serverlist.vim","src_id":"845","5":"845","creation_date":"1020678439","6":"1020678439"}]},"288":{"script_id":"288","0":"288","script_name":"aqua","1":"aqua","script_type":"color scheme","2":"color scheme","summary":"An aqua like color scheme","3":"An aqua like color scheme","description":"This is just an blueish aqua color scheme.","4":"This is just an blueish aqua color scheme.","install_details":"Just drop it in you $HOME\/.vim\/colors\/ or $VIMRUNTIME\/colors\/ (I think...) and do :colorscheme aqua from vim.","5":"Just drop it in you $HOME\/.vim\/colors\/ or $VIMRUNTIME\/colors\/ (I think...) and do :colorscheme aqua from vim.","first_name":"Joao","6":"Joao","last_name":"Estevao","7":"Estevao","releases":[{"0":"288","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"aqua.vim","4":"aqua.vim","src_id":"842","5":"842","creation_date":"1020667420","6":"1020667420"}]},"287":{"script_id":"287","0":"287","script_name":"outlineMode.vim","1":"outlineMode.vim","script_type":"utility","2":"utility","summary":"Create an outline view for source files in various programming languages.","3":"Create an outline view for source files in various programming languages.","description":"This script is now retired, as it is superceded by vimscript #273","4":"This script is now retired, as it is superceded by vimscript #273","install_details":"","5":"","first_name":"Kartik","6":"Kartik","last_name":"Agaram","7":"Agaram","releases":[{"0":"287","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"This script has been retired. You should use #273","3":"This script has been retired. You should use #273","package":"null.vim","4":"null.vim","src_id":"861","5":"861","creation_date":"1020953443","6":"1020953443"}]},"286":{"script_id":"286","0":"286","script_name":"sessmgr","1":"sessmgr","script_type":"utility","2":"utility","summary":"Manage session and viminfo like CodeWrite","3":"Manage session and viminfo like CodeWrite","description":"Manages sessions and viminfo so that when you start vim in a particular directory (e.g. a \"project\"), then vim starts up with all the files and windows set the way they were last, including history and other settings.  Allows multiple named sessions in each project, including the ability to quickly and easily switch between them.","4":"Manages sessions and viminfo so that when you start vim in a particular directory (e.g. a \"project\"), then vim starts up with all the files and windows set the way they were last, including history and other settings.  Allows multiple named sessions in each project, including the ability to quickly and easily switch between them.","install_details":"Put the file in your ..plugin.. directory.  Also, read the documentation at the end of the file.","5":"Put the file in your ..plugin.. directory.  Also, read the documentation at the end of the file.","first_name":"Ron","6":"Ron","last_name":"Aaron","7":"Aaron","releases":[{"0":"286","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"sessmgr.vim","4":"sessmgr.vim","src_id":"831","5":"831","creation_date":"1020243424","6":"1020243424"}]},"285":{"script_id":"285","0":"285","script_name":"potts.vim","1":"potts.vim","script_type":"color scheme","2":"color scheme","summary":"Doug's Colorscheme","3":"Doug's Colorscheme","description":"This is the colorscheme I've come up with \"over the years\".  It assumes for console that\r\nyou have the term set for a black background and gray text.  If you switch to a lighter\r\nscheme, it may not be very visible. \r\n\r\nIt works pretty well on transparent term windows, better if you can partially shade them.\r\n\r\nSorry it doesn't have a flashy name, but it doesn't seem to have any theme to it.\r\nScreen shots at http:\/\/pottsdl.github.com\/colors.html\r\nScreen shot of console vim and GUI (Motif) vim.","4":"This is the colorscheme I've come up with \"over the years\".  It assumes for console that\r\nyou have the term set for a black background and gray text.  If you switch to a lighter\r\nscheme, it may not be very visible. \r\n\r\nIt works pretty well on transparent term windows, better if you can partially shade them.\r\n\r\nSorry it doesn't have a flashy name, but it doesn't seem to have any theme to it.\r\nScreen shots at http:\/\/pottsdl.github.com\/colors.html\r\nScreen shot of console vim and GUI (Motif) vim.","install_details":"Put into your vimfiles colors\/ directory.  And :colorscheme potts","5":"Put into your vimfiles colors\/ directory.  And :colorscheme potts","first_name":"Douglas","6":"Douglas","last_name":"Potts","7":"Potts","releases":[{"0":"285","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"potts.vim","4":"potts.vim","src_id":"823","5":"823","creation_date":"1020142060","6":"1020142060"}]},"284":{"script_id":"284","0":"284","script_name":"unilatex.vim","1":"unilatex.vim","script_type":"ftplugin","2":"ftplugin","summary":"display LaTeX symbols as unicode while editing","3":"display LaTeX symbols as unicode while editing","description":"Vim supports unicode since version 6. This means it's possible to display many mathmatical symbols in vim. Writing LaTeX texts can now be much easier. To display unicode symbols while editing LaTeX documents, I've written a plugin for vim.\r\n\r\nScreenshot:\r\nhttp:\/\/www.fenk.wau.nl\/~oever\/software\/vim\/\r\n\r\nWhat does the plugin do?\r\n\r\n- Convert all symbols like \\alpha to the unicode symbol α when reading a LaTeX file.\r\n- Convert these commands when typing them.\r\n- Convert the unicode symbols back to LaTeX when saving the document.","4":"Vim supports unicode since version 6. This means it's possible to display many mathmatical symbols in vim. Writing LaTeX texts can now be much easier. To display unicode symbols while editing LaTeX documents, I've written a plugin for vim.\r\n\r\nScreenshot:\r\nhttp:\/\/www.fenk.wau.nl\/~oever\/software\/vim\/\r\n\r\nWhat does the plugin do?\r\n\r\n- Convert all symbols like \\alpha to the unicode symbol α when reading a LaTeX file.\r\n- Convert these commands when typing them.\r\n- Convert the unicode symbols back to LaTeX when saving the document.","install_details":"You can download it an save it in ~\/.vim\/ftplugin\/tex\/ to use it. \r\nFiletype plugin must be turned on. Just add the next line to your .vimrc or .gvimrc file:\r\n    filetype plugin on\r\nThe encoding must be set to utf-8:\r\n    set encoding=utf-8\r\n\r\nAlso, you must use gvim with a font that support unicode. Just add something like this to your file .gvimrc:\r\n    set guifont=-misc-fixed-medium-r-normal-*-*-120-*-*-c-*-iso10646-1\r\nAlternatively, you can use vim in a unicode terminal.\r\n","5":"You can download it an save it in ~\/.vim\/ftplugin\/tex\/ to use it. \r\nFiletype plugin must be turned on. Just add the next line to your .vimrc or .gvimrc file:\r\n    filetype plugin on\r\nThe encoding must be set to utf-8:\r\n    set encoding=utf-8\r\n\r\nAlso, you must use gvim with a font that support unicode. Just add something like this to your file .gvimrc:\r\n    set guifont=-misc-fixed-medium-r-normal-*-*-120-*-*-c-*-iso10646-1\r\nAlternatively, you can use vim in a unicode terminal.\r\n","first_name":"Jos","6":"Jos","last_name":"van den Oever","7":"van den Oever","releases":[{"0":"284","vim_version":"6.0","1":"6.0","script_version":"1.2","2":"1.2","version_comment":"The code \\int (222B) was associated with the symbol for \\vee (2228). This has been fixed.","3":"The code \\int (222B) was associated with the symbol for \\vee (2228). This has been fixed.","package":"unilatex.vim","4":"unilatex.vim","src_id":"1000","5":"1000","creation_date":"1026199918","6":"1026199918"},{"0":"284","vim_version":"6.0","1":"6.0","script_version":"1.1","2":"1.1","version_comment":"The cursur position is stored. This means that saving a file does not move the cursor to the position of the last replacement.\n\n","3":"The cursur position is stored. This means that saving a file does not move the cursor to the position of the last replacement.\n\n","package":"unilatex.vim","4":"unilatex.vim","src_id":"821","5":"821","creation_date":"1020068143","6":"1020068143"},{"0":"284","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"unilatex.vim","4":"unilatex.vim","src_id":"820","5":"820","creation_date":"1020046855","6":"1020046855"}]},"283":{"script_id":"283","0":"283","script_name":"txt2pdf.vim","1":"txt2pdf.vim","script_type":"utility","2":"utility","summary":"Script to save the current file and convert it to PDF using txt2pdf","3":"Script to save the current file and convert it to PDF using txt2pdf","description":"Script to save the current file and convert it to PDF using txt2pdf. You need to install txt2pdf http:\/\/www.sanface.com\/txt2pdf.html\r\n\r\nYou can also use txt2pdf PRO http:\/\/www.sanface.com\/txt2pdfPRO.html and txt2pdf PRO + crypt http:\/\/www.sanface.com\/txt2pdfPROcrypt.html to\r\nmake more complex PDFs like\r\nhttp:\/\/www.sanface.com\/pdf\/Purchase_Order.pdf\r\nhttp:\/\/www.sanface.com\/pdf\/invoice.pdf\r\nhttp:\/\/www.sanface.com\/pdf\/hfmus.pdf\r\nhttp:\/\/www.sanface.com\/pdf\/heraldbill.pdf\r\n","4":"Script to save the current file and convert it to PDF using txt2pdf. You need to install txt2pdf http:\/\/www.sanface.com\/txt2pdf.html\r\n\r\nYou can also use txt2pdf PRO http:\/\/www.sanface.com\/txt2pdfPRO.html and txt2pdf PRO + crypt http:\/\/www.sanface.com\/txt2pdfPROcrypt.html to\r\nmake more complex PDFs like\r\nhttp:\/\/www.sanface.com\/pdf\/Purchase_Order.pdf\r\nhttp:\/\/www.sanface.com\/pdf\/invoice.pdf\r\nhttp:\/\/www.sanface.com\/pdf\/hfmus.pdf\r\nhttp:\/\/www.sanface.com\/pdf\/heraldbill.pdf\r\n","install_details":"Inside the distribution three files: txt2pdf.vim the VIM plugin, txt2pdf.txt the plugin documentation, txt2pdf.vim the syntax for txt2pdf.cfg.\r\nPut the plugin inside your VIM plugin directory.\r\nPut the doc inside your VIM doc directory (generate the local tags file with the |:helptags| command).\r\nPut the syntax plugin inside your VIM syntax directory and configure filetype.vim (au BufNewFile,BufRead txt2pdf.cfg                setf txt2pdf) .\r\nRemember to set global variables:\r\n\ttxt2pdf_path\t: the path of txt2pdf executable\r\n\ttxt2pdfcfg_path\t: the path of your configuration file (usually txt2pdf.cfg)\r\n\ttxt2pdf_key\t: the key to start the command (deafult <F2>)\r\n\ttxt2pdfconf_key\t: the key to start an input dialog to enter the txt2pdf configuration file path (deafult <F3>)\r\nin vimrc file.\r\nYou can find more information in the ReadMe file inside the distribution.","5":"Inside the distribution three files: txt2pdf.vim the VIM plugin, txt2pdf.txt the plugin documentation, txt2pdf.vim the syntax for txt2pdf.cfg.\r\nPut the plugin inside your VIM plugin directory.\r\nPut the doc inside your VIM doc directory (generate the local tags file with the |:helptags| command).\r\nPut the syntax plugin inside your VIM syntax directory and configure filetype.vim (au BufNewFile,BufRead txt2pdf.cfg                setf txt2pdf) .\r\nRemember to set global variables:\r\n\ttxt2pdf_path\t: the path of txt2pdf executable\r\n\ttxt2pdfcfg_path\t: the path of your configuration file (usually txt2pdf.cfg)\r\n\ttxt2pdf_key\t: the key to start the command (deafult <F2>)\r\n\ttxt2pdfconf_key\t: the key to start an input dialog to enter the txt2pdf configuration file path (deafult <F3>)\r\nin vimrc file.\r\nYou can find more information in the ReadMe file inside the distribution.","first_name":"SANFACE","6":"SANFACE","last_name":"Software","7":"Software","releases":[{"0":"283","vim_version":"6.0","1":"6.0","script_version":"2.15","2":"2.15","version_comment":"Update to support txt2pdf PRO + crypt 7.5, txt2pdf PRO 7.5 and txt2pdf 7.6","3":"Update to support txt2pdf PRO + crypt 7.5, txt2pdf PRO 7.5 and txt2pdf 7.6","package":"txt2pdfvim.zip","4":"txt2pdfvim.zip","src_id":"3737","5":"3737","creation_date":"1104380080","6":"1104380080"}]},"282":{"script_id":"282","0":"282","script_name":"candy.vim","1":"candy.vim","script_type":"color scheme","2":"color scheme","summary":"color scheme ( background is black )","3":"color scheme ( background is black )","description":"If you want to update this file, please download rainbow.zip.\r\nhttp:\/\/www.vim.org\/script.php?script_id=463\r\ncandy.vim is renamed to neon.vim.\r\n\r\nThis is color scheme.","4":"If you want to update this file, please download rainbow.zip.\r\nhttp:\/\/www.vim.org\/script.php?script_id=463\r\ncandy.vim is renamed to neon.vim.\r\n\r\nThis is color scheme.","install_details":"Save as colors\/candy.vim under runtimepath.\r\nthen\r\n:colo candy","5":"Save as colors\/candy.vim under runtimepath.\r\nthen\r\n:colo candy","first_name":"Takeshi","6":"Takeshi","last_name":"Zeniya","7":"Zeniya","releases":[{"0":"282","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"candy.vim","4":"candy.vim","src_id":"817","5":"817","creation_date":"1019965376","6":"1019965376"}]},"281":{"script_id":"281","0":"281","script_name":"ExecPerl","1":"ExecPerl","script_type":"utility","2":"utility","summary":"Utilities for executing perl scripts","3":"Utilities for executing perl scripts","description":"Provides the following commands:\r\n\r\n:ExecPerl script_name\r\n\tThis will execute script_name using the perl\r\n\tinterpreter.\r\n\r\n:ExecPerlMore\r\n\tThis will execute script_name using the perl\r\n\tinterpreter.  If the output would scroll past the end\r\n\tof the screen, execution pauses and waits for a\r\n\tkeystroke before continuing.\r\n\r\n:ExecPerlDump\r\n\tThis will ask you for an output file and then\r\n\texecute script_name using the perl interpreter.  The\r\n\toutput from the script is dumped to the file that you\r\n\tentered when you were prompted.  You may press enter\r\n\tinstead of entering a file name to accept the default\r\n\tfilename.\r\n\r\nAlso, The following keys are mapped by default.  You'll have to\r\ncomment them if you don't want this behavior:\r\n\r\n\t<F5>:    ExecPerl the current file being edited\r\n\t<C-F5>:  ExecPerlMore the current file being edited\r\n\t<S-F5>:  ExecPerlDump the current file being edited\r\n\r\n","4":"Provides the following commands:\r\n\r\n:ExecPerl script_name\r\n\tThis will execute script_name using the perl\r\n\tinterpreter.\r\n\r\n:ExecPerlMore\r\n\tThis will execute script_name using the perl\r\n\tinterpreter.  If the output would scroll past the end\r\n\tof the screen, execution pauses and waits for a\r\n\tkeystroke before continuing.\r\n\r\n:ExecPerlDump\r\n\tThis will ask you for an output file and then\r\n\texecute script_name using the perl interpreter.  The\r\n\toutput from the script is dumped to the file that you\r\n\tentered when you were prompted.  You may press enter\r\n\tinstead of entering a file name to accept the default\r\n\tfilename.\r\n\r\nAlso, The following keys are mapped by default.  You'll have to\r\ncomment them if you don't want this behavior:\r\n\r\n\t<F5>:    ExecPerl the current file being edited\r\n\t<C-F5>:  ExecPerlMore the current file being edited\r\n\t<S-F5>:  ExecPerlDump the current file being edited\r\n\r\n","install_details":"Place it in your plugin\/ directory or source it at runtime.","5":"Place it in your plugin\/ directory or source it at runtime.","first_name":"Scott","6":"Scott","last_name":"Barker","7":"Barker","releases":[{"0":"281","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"ExecPerl.vim","4":"ExecPerl.vim","src_id":"814","5":"814","creation_date":"1019854330","6":"1019854330"}]},"280":{"script_id":"280","0":"280","script_name":"netdict","1":"netdict","script_type":"ftplugin","2":"ftplugin","summary":"A frontend to the Unix dict protocol command-line client.","3":"A frontend to the Unix dict protocol command-line client.","description":"Netdict is a plugin to lookup definitions via the Internet with a dict command-line client. It has the following features:\r\n\r\n    - specifying an alternate database and search strategy\r\n    - term matching\r\n    - syntax highlighting\r\n    - customizable settings\r\n    - GUI when available","4":"Netdict is a plugin to lookup definitions via the Internet with a dict command-line client. It has the following features:\r\n\r\n    - specifying an alternate database and search strategy\r\n    - term matching\r\n    - syntax highlighting\r\n    - customizable settings\r\n    - GUI when available","install_details":"Extract the archive and then `make install'. Then run \":helptags ~\/.vim\/doc\" then \":h netdict\" for more info.","5":"Extract the archive and then `make install'. Then run \":helptags ~\/.vim\/doc\" then \":h netdict\" for more info.","first_name":"Ben","6":"Ben","last_name":"Kibbey","7":"Kibbey","releases":[{"0":"280","vim_version":"6.0","1":"6.0","script_version":"20060805","2":"20060805","version_comment":"Added a GUI input dialog. Read ChangeLog for more.","3":"Added a GUI input dialog. Read ChangeLog for more.","package":"netdict.tgz","4":"netdict.tgz","src_id":"6148","5":"6148","creation_date":"1157610853","6":"1157610853"},{"0":"280","vim_version":"6.0","1":"6.0","script_version":"20030823","2":"20030823","version_comment":"Fix for database expression.","3":"Fix for database expression.","package":"netdict.tgz","4":"netdict.tgz","src_id":"2257","5":"2257","creation_date":"1061642276","6":"1061642276"}]},"279":{"script_id":"279","0":"279","script_name":"Projmgr","1":"Projmgr","script_type":"utility","2":"utility","summary":"A fancy way of using 'session'","3":"A fancy way of using 'session'","description":"This plugin provides a more easy to use interface for the Vim session\r\nfeature.\r\n\r\nI wrote it first only for my own needs. I have a bunch of small\r\nprojects lying around on my hard disk. I would like to load a whole\r\nproject, play around with it, switch to another if I like, or simply\r\nunload it.\r\n\r\nThis plugin provide a menu system for 'Load', 'Unload' 'Switch to' a\r\nproject(session). None-menu-driven version is not available at the\r\nmoment.\r\n\r\nThis version is for Linux only. I am still struggling to get a Win32 version done.\r\n\r\nA screenshot (333879 in size) at:\r\nhttp:\/\/www.geocities.com\/wzhliang\/vim\/image\/fullscreen1.png\r\n\r\n","4":"This plugin provides a more easy to use interface for the Vim session\r\nfeature.\r\n\r\nI wrote it first only for my own needs. I have a bunch of small\r\nprojects lying around on my hard disk. I would like to load a whole\r\nproject, play around with it, switch to another if I like, or simply\r\nunload it.\r\n\r\nThis plugin provide a menu system for 'Load', 'Unload' 'Switch to' a\r\nproject(session). None-menu-driven version is not available at the\r\nmoment.\r\n\r\nThis version is for Linux only. I am still struggling to get a Win32 version done.\r\n\r\nA screenshot (333879 in size) at:\r\nhttp:\/\/www.geocities.com\/wzhliang\/vim\/image\/fullscreen1.png\r\n\r\n","install_details":"1. Automatic: \r\n   Simply use the install.sh script and following the instruction. \r\n   Requires:\r\n   bash, Perl.\r\n2. Manual:\r\n   You don't need to do this ideally. But if for whatever reason the \r\n   install shell script is not working for you, try to following these\r\n   steps:\r\n   a) Copy the projmgr.vim into your plugin directory or\r\n      $HOME\/.vim\/plugin.\r\n   b) Copy the Perl script to somewhere. E.g plugin\/perl.\r\n   c) Copy this documentation into the corresponding doc directory.\r\n   d) Make a directory: $HOME\/.vim\/projects. This where the vim session\r\n      files will be stored.\r\n   e) Modify the script and change the s:projmgr_dir to the plugin\r\n      directory where you installed projmgr.vim.\r\n   f) Copy all (if you have any) your session files into the directory\r\n      mentioned in d).","5":"1. Automatic: \r\n   Simply use the install.sh script and following the instruction. \r\n   Requires:\r\n   bash, Perl.\r\n2. Manual:\r\n   You don't need to do this ideally. But if for whatever reason the \r\n   install shell script is not working for you, try to following these\r\n   steps:\r\n   a) Copy the projmgr.vim into your plugin directory or\r\n      $HOME\/.vim\/plugin.\r\n   b) Copy the Perl script to somewhere. E.g plugin\/perl.\r\n   c) Copy this documentation into the corresponding doc directory.\r\n   d) Make a directory: $HOME\/.vim\/projects. This where the vim session\r\n      files will be stored.\r\n   e) Modify the script and change the s:projmgr_dir to the plugin\r\n      directory where you installed projmgr.vim.\r\n   f) Copy all (if you have any) your session files into the directory\r\n      mentioned in d).","first_name":"Wenzhi","6":"Wenzhi","last_name":"Liang","7":"Liang","releases":[{"0":"279","vim_version":"6.0","1":"6.0","script_version":"0.2","2":"0.2","version_comment":"A few bug fix. Cleaned some output to achieve a much neater feeling. Improved a install shell script to make manual installation unnecessary.","3":"A few bug fix. Cleaned some output to achieve a much neater feeling. Improved a install shell script to make manual installation unnecessary.","package":"projmgr-0.2.tar.gz","4":"projmgr-0.2.tar.gz","src_id":"819","5":"819","creation_date":"1020046737","6":"1020046737"},{"0":"279","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"projmgr.tar.gz","4":"projmgr.tar.gz","src_id":"811","5":"811","creation_date":"1019626187","6":"1019626187"}]},"278":{"script_id":"278","0":"278","script_name":"sybase.vim","1":"sybase.vim","script_type":"utility","2":"utility","summary":"Connect to a sybase database from within VIM","3":"Connect to a sybase database from within VIM","description":"Follows is an adaption of sqlplus.vim written by Jamis Buck see http:\/\/vim.sourceforge.net\/scripts\/script.php?script_id=97\r\nfor the original. \r\n\r\nThis script contains code required to execute SQL queries from withing VIM.  It uses sqsh (http:\/\/www.sqsh.org\/) however it could trivially be adapted to use isql.  It is very ruff and ready but seems to offer required functionality.\r\n\r\nThanks to Jamis Buck for creating sqlplus.vim I am sure if you compair the code you will see how little I have had to do to get this code to work ;-) \r\n\r\nINSTRUCTIONS\r\n============\r\n\r\nEdit ~\/.sqshrc and add the line \\set semicolon_hack=1 \r\n\r\nSave the code into a file and source from your .vimrc or use your favourate autoload system.\r\n\r\nEdit the code to add the credentials for the databases you would like to connect to.\r\n\r\nIn highlight mode hit F8 to execute the hightlighed SQL.  It will cope with broken lines.\r\n\r\nHit F8 with no highlighted selection and VIM will prompt you for a database to connect to.\r\n\r\n","4":"Follows is an adaption of sqlplus.vim written by Jamis Buck see http:\/\/vim.sourceforge.net\/scripts\/script.php?script_id=97\r\nfor the original. \r\n\r\nThis script contains code required to execute SQL queries from withing VIM.  It uses sqsh (http:\/\/www.sqsh.org\/) however it could trivially be adapted to use isql.  It is very ruff and ready but seems to offer required functionality.\r\n\r\nThanks to Jamis Buck for creating sqlplus.vim I am sure if you compair the code you will see how little I have had to do to get this code to work ;-) \r\n\r\nINSTRUCTIONS\r\n============\r\n\r\nEdit ~\/.sqshrc and add the line \\set semicolon_hack=1 \r\n\r\nSave the code into a file and source from your .vimrc or use your favourate autoload system.\r\n\r\nEdit the code to add the credentials for the databases you would like to connect to.\r\n\r\nIn highlight mode hit F8 to execute the hightlighed SQL.  It will cope with broken lines.\r\n\r\nHit F8 with no highlighted selection and VIM will prompt you for a database to connect to.\r\n\r\n","install_details":"","5":"","first_name":"Scott","6":"Scott","last_name":"James","7":"James","releases":[{"0":"278","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"sybase.vim","4":"sybase.vim","src_id":"810","5":"810","creation_date":"1019620801","6":"1019620801"}]},"277":{"script_id":"277","0":"277","script_name":"PrintWithLNum","1":"PrintWithLNum","script_type":"utility","2":"utility","summary":"Prepend line numbers to each line for printing","3":"Prepend line numbers to each line for printing","description":"In response to a query on the vim mailing list I developed this quick function which prepends the line number to the beginning of each line. The line numbers are left justified and formatted with a 1 character white space on either side of the number.\r\n\r\nThere are two methods of operation. The first prepends the line numbers to each line and is activated with :Printwln    (or \":Printwln(0)\" ). The second method of calling causes the program to prepend the line number and then go on to print the file using \":hardcopy\", and then undo the changes it just made. This allows you to print off the contents of a file without changing it.\r\n\r\nHope it helps someone.\r\n\r\nColin.","4":"In response to a query on the vim mailing list I developed this quick function which prepends the line number to the beginning of each line. The line numbers are left justified and formatted with a 1 character white space on either side of the number.\r\n\r\nThere are two methods of operation. The first prepends the line numbers to each line and is activated with :Printwln    (or \":Printwln(0)\" ). The second method of calling causes the program to prepend the line number and then go on to print the file using \":hardcopy\", and then undo the changes it just made. This allows you to print off the contents of a file without changing it.\r\n\r\nHope it helps someone.\r\n\r\nColin.","install_details":"Place where appropriate, source printwln.vim","5":"Place where appropriate, source printwln.vim","first_name":"Colin","6":"Colin","last_name":"Keith","7":"Keith","releases":[{"0":"277","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"printwln.vim","4":"printwln.vim","src_id":"809","5":"809","creation_date":"1019554334","6":"1019554334"}]},"276":{"script_id":"276","0":"276","script_name":"adrian.vim","1":"adrian.vim","script_type":"color scheme","2":"color scheme","summary":"A dark background color scheme, with light color for text comments","3":"A dark background color scheme, with light color for text comments","description":"This colorscheme is a dark background colorscheme.  Comments are in light grey and other text is highlighted to aid me in thermal analysis syntax highlighting.\r\n\r\nThe latest version should always be found at: http:\/\/www.naglenet.org\/vim\/vimfiles\/colors\/adrian.vim\r\n\r\nSample screen shot:\r\nsmall> http:\/\/www.naglenet.org\/images\/vim\/tak_scrnsht-s.jpg\r\noriginal> http:\/\/www.naglenet.org\/vim\/tak_screenshot.html\r\n\r\nComments are always welcome.","4":"This colorscheme is a dark background colorscheme.  Comments are in light grey and other text is highlighted to aid me in thermal analysis syntax highlighting.\r\n\r\nThe latest version should always be found at: http:\/\/www.naglenet.org\/vim\/vimfiles\/colors\/adrian.vim\r\n\r\nSample screen shot:\r\nsmall> http:\/\/www.naglenet.org\/images\/vim\/tak_scrnsht-s.jpg\r\noriginal> http:\/\/www.naglenet.org\/vim\/tak_screenshot.html\r\n\r\nComments are always welcome.","install_details":"Install two options:\r\n\r\nA) Current session:\r\n1> Copy or move the file into the \"colors\/\" directory in the runtimepath.\r\n2> In command mode, type\r\n:colo adrian\r\n\r\nB) Permanent\r\n1> Enter the following line in you vimrc file:\r\ncolorscheme adrian\r\n","5":"Install two options:\r\n\r\nA) Current session:\r\n1> Copy or move the file into the \"colors\/\" directory in the runtimepath.\r\n2> In command mode, type\r\n:colo adrian\r\n\r\nB) Permanent\r\n1> Enter the following line in you vimrc file:\r\ncolorscheme adrian\r\n","first_name":"Adrian","6":"Adrian","last_name":"Nagle","7":"Nagle","releases":[{"0":"276","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"adrian.vim","4":"adrian.vim","src_id":"808","5":"808","creation_date":"1019538382","6":"1019538382"}]},"275":{"script_id":"275","0":"275","script_name":"camo.vim","1":"camo.vim","script_type":"color scheme","2":"color scheme","summary":"Dark Color Scheme","3":"Dark Color Scheme","description":"For a screenshot goto http:\/\/www.geocities.com\/aldy0169\/images\/camo.jpg\r\n","4":"For a screenshot goto http:\/\/www.geocities.com\/aldy0169\/images\/camo.jpg\r\n","install_details":"place in your $VIMRUNTIME\/colors\r\n:colorscheme camo","5":"place in your $VIMRUNTIME\/colors\r\n:colorscheme camo","first_name":"Timothy","6":"Timothy","last_name":"Aldrich","7":"Aldrich","releases":[{"0":"275","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"camo.vim","4":"camo.vim","src_id":"807","5":"807","creation_date":"1019511722","6":"1019511722"}]},"274":{"script_id":"274","0":"274","script_name":"User Defined Type Highlighter","1":"User Defined Type Highlighter","script_type":"utility","2":"utility","summary":"Generate vim highlighting groups from C++ typedefs, structs, and classes.","3":"Generate vim highlighting groups from C++ typedefs, structs, and classes.","description":"Generates vim highlighting groups for typedefs, classes, and structs that you have defined in your C++ header files.  There are a few options that you can set to control its behavior, so read the included help file so you can know what options you can change in your .vimrc if you want.","4":"Generates vim highlighting groups for typedefs, classes, and structs that you have defined in your C++ header files.  There are a few options that you can set to control its behavior, so read the included help file so you can know what options you can change in your .vimrc if you want.","install_details":"Thanks to Gavin Sinclair for suggesting that I package this differently.  You should unpackage udt.tar.gz in your ~\/.vim directory.  This will add the usr_include.vim file to your ftplugin\/cpp directory.  There is no longer a need to source the file in your .vimrc, it will be sourced whenever you load up a C++ file.  You should move the udt.rb file to wherever you keep your scripts (ie. ~\/bin).","5":"Thanks to Gavin Sinclair for suggesting that I package this differently.  You should unpackage udt.tar.gz in your ~\/.vim directory.  This will add the usr_include.vim file to your ftplugin\/cpp directory.  There is no longer a need to source the file in your .vimrc, it will be sourced whenever you load up a C++ file.  You should move the udt.rb file to wherever you keep your scripts (ie. ~\/bin).","first_name":"Michael","6":"Michael","last_name":"Brailsford","7":"Brailsford","releases":[{"0":"274","vim_version":"6.0","1":"6.0","script_version":"1.1","2":"1.1","version_comment":"Changed a few things and fixed some bugs.  Mainly, I made it so you do not have to move any files to make the plugin work, if you don't want to.  It is still *highly* recommend that you do move the files as suggested in the help file, but you now have the option to not move anything.  Updated the help files, and fixed some typos and other minor things.","3":"Changed a few things and fixed some bugs.  Mainly, I made it so you do not have to move any files to make the plugin work, if you don't want to.  It is still *highly* recommend that you do move the files as suggested in the help file, but you now have the option to not move anything.  Updated the help files, and fixed some typos and other minor things.","package":"udt.tar.gz","4":"udt.tar.gz","src_id":"1030","5":"1030","creation_date":"1027122417","6":"1027122417"},{"0":"274","vim_version":"6.0","1":"6.0","script_version":"1.01","2":"1.01","version_comment":"Very minor bug fix.","3":"Very minor bug fix.","package":"udt_highlight.tar","4":"udt_highlight.tar","src_id":"816","5":"816","creation_date":"1019864712","6":"1019864712"},{"0":"274","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Improved the handling of typedefs.  Now it properly handles something like \"typedef long long int llint;\".  Added support for user configurable colors, also added documentation.  Anyway, this is a major overhaul of the script.  Install the doc, and you can read all about it.  You should still untar the archive in ~\/.vim.  When you start up vim type \":helptags ~\/.vim\/doc\" then \":he udt\".","3":"Improved the handling of typedefs.  Now it properly handles something like \"typedef long long int llint;\".  Added support for user configurable colors, also added documentation.  Anyway, this is a major overhaul of the script.  Install the doc, and you can read all about it.  You should still untar the archive in ~\/.vim.  When you start up vim type \":helptags ~\/.vim\/doc\" then \":he udt\".","package":"udt_highlight.tar","4":"udt_highlight.tar","src_id":"815","5":"815","creation_date":"1019855927","6":"1019855927"},{"0":"274","vim_version":"6.0","1":"6.0","script_version":"0.92","2":"0.92","version_comment":"Well, just polishing things up.  I am now very confident that it will work.  I ran the command line version on \/usr\/include and got a syntax highlighting file of 7000 lines.  I included that file in the tar.  I also added some things to aid in expanding this to work with other languages.  For now though it is for C++ only.","3":"Well, just polishing things up.  I am now very confident that it will work.  I ran the command line version on \/usr\/include and got a syntax highlighting file of 7000 lines.  I included that file in the tar.  I also added some things to aid in expanding this to work with other languages.  For now though it is for C++ only.","package":"syntax_expander.tar","4":"syntax_expander.tar","src_id":"804","5":"804","creation_date":"1019423014","6":"1019423014"},{"0":"274","vim_version":"6.0","1":"6.0","script_version":"0.91","2":"0.91","version_comment":"Thanks to Gavin Sinclair for suggesting better packaging.  Now you should untar the file in your ~\/.vim directory and it will add the syn_expand.vim to the ftplugins\/cpp\/ directory.  You should then move the csyntax_expander.rb to whereever you keep scripts.","3":"Thanks to Gavin Sinclair for suggesting better packaging.  Now you should untar the file in your ~\/.vim directory and it will add the syn_expand.vim to the ftplugins\/cpp\/ directory.  You should then move the csyntax_expander.rb to whereever you keep scripts.","package":"syntax_expander.tar","4":"syntax_expander.tar","src_id":"803","5":"803","creation_date":"1019414228","6":"1019414228"},{"0":"274","vim_version":"6.0","1":"6.0","script_version":"0.9","2":"0.9","version_comment":"Initial upload","3":"Initial upload","package":"syntax_expander.tar","4":"syntax_expander.tar","src_id":"802","5":"802","creation_date":"1019410535","6":"1019410535"}]},"273":{"script_id":"273","0":"273","script_name":"taglist.vim","1":"taglist.vim","script_type":"utility","2":"utility","summary":"Source code browser (supports C\/C++, java, perl, python, tcl, sql, php, etc)","3":"Source code browser (supports C\/C++, java, perl, python, tcl, sql, php, etc)","description":"The \"Tag List\" plugin is a source code browser plugin for Vim and\r\nprovides an overview of the structure of source code files and allows\r\nyou to efficiently browse through source code files for different\r\nprogramming languages.\r\n\r\nThe Github repository for the taglist plugin is available at:\r\n\r\n    https:\/\/github.com\/yegappan\/taglist\r\n\r\nYou can visit the taglist plugin home page for more information:\r\n\r\n      http:\/\/vim-taglist.sourceforge.net\r\n\r\nYou can subscribe to the taglist mailing list to post your questions\r\nor suggestions for improvement or to report bugs. Visit the following\r\npage for subscribing to the mailing list:\r\n\r\n      http:\/\/groups.yahoo.com\/group\/taglist\/\r\n\r\nFor more information about using this plugin, after installing the\r\ntaglist plugin, use the \":help taglist\" command.","4":"The \"Tag List\" plugin is a source code browser plugin for Vim and\r\nprovides an overview of the structure of source code files and allows\r\nyou to efficiently browse through source code files for different\r\nprogramming languages.\r\n\r\nThe Github repository for the taglist plugin is available at:\r\n\r\n    https:\/\/github.com\/yegappan\/taglist\r\n\r\nYou can visit the taglist plugin home page for more information:\r\n\r\n      http:\/\/vim-taglist.sourceforge.net\r\n\r\nYou can subscribe to the taglist mailing list to post your questions\r\nor suggestions for improvement or to report bugs. Visit the following\r\npage for subscribing to the mailing list:\r\n\r\n      http:\/\/groups.yahoo.com\/group\/taglist\/\r\n\r\nFor more information about using this plugin, after installing the\r\ntaglist plugin, use the \":help taglist\" command.","install_details":"1. Download the taglist.zip file and unzip the files to the $HOME\/.vim or the\r\n    $HOME\/vimfiles or the $VIM\/vimfiles directory. After this step, you should\r\n    have the following two files (the directory structure should be preserved):\r\n\r\n         plugin\/taglist.vim - main taglist plugin file\r\n         doc\/taglist.txt    - documentation (help) file\r\n\r\n   Refer to the |add-plugin|, |add-global-plugin| and |runtimepath| Vim\r\n   help pages for more details about installing Vim plugins.\r\n2. Change to the $HOME\/.vim\/doc or $HOME\/vimfiles\/doc or $VIM\/vimfiles\/doc\r\n    directory, start Vim and run the \":helptags .\" command to process the\r\n    taglist help file. Without this step, you cannot jump to the taglist help\r\n    topics.\r\n3. If the exuberant ctags utility is not present in your PATH, then set the\r\n    Tlist_Ctags_Cmd variable to point to the location of the exuberant ctags\r\n    utility (not to the directory) in the .vimrc file.\r\n4. If you are running a terminal\/console version of Vim and the terminal\r\n    doesn't support changing the window width then set the\r\n    'Tlist_Inc_Winwidth' variable to 0 in the .vimrc file.\r\n5. Restart Vim.\r\n6. You can now use the \":TlistToggle\" command to open\/close the taglist\r\n    window. You can use the \":help taglist\" command to get more information\r\n    about using the taglist plugin.\r\n","5":"1. Download the taglist.zip file and unzip the files to the $HOME\/.vim or the\r\n    $HOME\/vimfiles or the $VIM\/vimfiles directory. After this step, you should\r\n    have the following two files (the directory structure should be preserved):\r\n\r\n         plugin\/taglist.vim - main taglist plugin file\r\n         doc\/taglist.txt    - documentation (help) file\r\n\r\n   Refer to the |add-plugin|, |add-global-plugin| and |runtimepath| Vim\r\n   help pages for more details about installing Vim plugins.\r\n2. Change to the $HOME\/.vim\/doc or $HOME\/vimfiles\/doc or $VIM\/vimfiles\/doc\r\n    directory, start Vim and run the \":helptags .\" command to process the\r\n    taglist help file. Without this step, you cannot jump to the taglist help\r\n    topics.\r\n3. If the exuberant ctags utility is not present in your PATH, then set the\r\n    Tlist_Ctags_Cmd variable to point to the location of the exuberant ctags\r\n    utility (not to the directory) in the .vimrc file.\r\n4. If you are running a terminal\/console version of Vim and the terminal\r\n    doesn't support changing the window width then set the\r\n    'Tlist_Inc_Winwidth' variable to 0 in the .vimrc file.\r\n5. Restart Vim.\r\n6. You can now use the \":TlistToggle\" command to open\/close the taglist\r\n    window. You can use the \":help taglist\" command to get more information\r\n    about using the taglist plugin.\r\n","first_name":"Yegappan","6":"Yegappan","last_name":"Lakshmanan","7":"Lakshmanan","releases":[{"0":"273","vim_version":"6.0","1":"6.0","script_version":"4.6","2":"4.6","version_comment":"1. Fixed a bug in refreshing the folds in the taglist window when switching between Vim tabs with Tlist_Show_One_File enabled.\r\n2. Update the TlistShowTag command output to display the tag scope.\r\n3. Preserve the alternate file when opening the taglist window.\r\n4. Restore the 'cpo' option value properly when the loading of the plugin is stopped.\r\n5. When the plugin is recursively sourced, don't change the 'cpo' setting to the default value.\r\n6. If a filetype contains multiple file types separated by a dot, then use the first file type.\r\n7. When displaying tag prototypes, trim the output to fit the window width.\r\n8. Add support for some more languages.\r\n9. Disable the 'relativenumber' option for the taglist window.\r\n10. On MS-Windows, use writefile() to generate the temporary batch file instead of the redir command. This fixes a problem in using the generated batch file in multi-byte encoding environments.\r\n","3":"1. Fixed a bug in refreshing the folds in the taglist window when switching between Vim tabs with Tlist_Show_One_File enabled.\r\n2. Update the TlistShowTag command output to display the tag scope.\r\n3. Preserve the alternate file when opening the taglist window.\r\n4. Restore the 'cpo' option value properly when the loading of the plugin is stopped.\r\n5. When the plugin is recursively sourced, don't change the 'cpo' setting to the default value.\r\n6. If a filetype contains multiple file types separated by a dot, then use the first file type.\r\n7. When displaying tag prototypes, trim the output to fit the window width.\r\n8. Add support for some more languages.\r\n9. Disable the 'relativenumber' option for the taglist window.\r\n10. On MS-Windows, use writefile() to generate the temporary batch file instead of the redir command. This fixes a problem in using the generated batch file in multi-byte encoding environments.\r\n","package":"taglist_46.zip","4":"taglist_46.zip","src_id":"19574","5":"19574","creation_date":"1361941702","6":"1361941702"},{"0":"273","vim_version":"6.0","1":"6.0","script_version":"4.5","2":"4.5","version_comment":"Fix an extra space in the check for exctags. Refresh the taglist window\r\nfolds after entering a tab. Escape special characters like backslash in\r\nthe tag name when saving a session file. Add an internal function to get\r\nand detect file types.\r\n","3":"Fix an extra space in the check for exctags. Refresh the taglist window\r\nfolds after entering a tab. Escape special characters like backslash in\r\nthe tag name when saving a session file. Add an internal function to get\r\nand detect file types.\r\n","package":"taglist_45.zip","4":"taglist_45.zip","src_id":"7701","5":"7701","creation_date":"1190398429","6":"1190398429"},{"0":"273","vim_version":"6.0","1":"6.0","script_version":"4.4","2":"4.4","version_comment":"The following fixes are made in this release:\r\n1. If multiple Vim plugins register for the BufEnter autocmd, then sometimes\r\n    the buffer name supplied to the autocmd is incorrect. Use the buffer number\r\n    instead of buffer name in the BufEnter autocmd.\r\n2. Add the filename to the tags menu only for valid file names.\r\n","3":"The following fixes are made in this release:\r\n1. If multiple Vim plugins register for the BufEnter autocmd, then sometimes\r\n    the buffer name supplied to the autocmd is incorrect. Use the buffer number\r\n    instead of buffer name in the BufEnter autocmd.\r\n2. Add the filename to the tags menu only for valid file names.\r\n","package":"taglist_44.zip","4":"taglist_44.zip","src_id":"7169","5":"7169","creation_date":"1180129776","6":"1180129776"},{"0":"273","vim_version":"6.0","1":"6.0","script_version":"4.3","2":"4.3","version_comment":"1. Added support for jumping to a tag\/file in a new or existing tab\r\n   from the taglist window (works only with Vim7 and above).\r\n2. Added support for opening a tag in the previous window.\r\n3. With the Tlist_File_Fold_Auto_Close variable set, when opening a\r\n   file from the file explorer window, the folds in the taglist window\r\n   are not closed correctly.  Fixed this problem.\r\n","3":"1. Added support for jumping to a tag\/file in a new or existing tab\r\n   from the taglist window (works only with Vim7 and above).\r\n2. Added support for opening a tag in the previous window.\r\n3. With the Tlist_File_Fold_Auto_Close variable set, when opening a\r\n   file from the file explorer window, the folds in the taglist window\r\n   are not closed correctly.  Fixed this problem.\r\n","package":"taglist_43.zip","4":"taglist_43.zip","src_id":"6769","5":"6769","creation_date":"1172164345","6":"1172164345"},{"0":"273","vim_version":"6.0","1":"6.0","script_version":"4.2","2":"4.2","version_comment":"1. After opening a file with no tags defined in it with the\r\n   Tlist_Compact_Format option set, if the tags are updated, the folds\r\n   used for the files following the empty tags file are affected.\r\n2. On MS-Windows, use a \"taglist.cmd\" temporary file to run exuberant\r\n   ctags. This is to handle space characters in the file names and\r\n   in the exuberant ctags path name.\r\n3. In the taglist window, when a file is re-sorted or updated open the\r\n   fold for the file.\r\n4. When the 'shellxquote' option is set to double quotes, escape\r\n   double quotes in the command executed for exuberant ctags.\r\n5. On FreeBSD, exuberant ctags is installed as exctags, look for\r\n   exctags in the PATH.\r\n6. If two taglist plugins are present (one in the system Vim directory\r\n   and another in the user's .vim\/plugin directory), then the plugin\r\n   in the users's .vim directory overrides the version in the system\r\n   vim directory.\r\n7. When the :TlistMessages command is issued display the debug\r\n   messages in a taglist.txt buffer.\r\n8. Clear the readonly option for the taglist buffer\r\n9. When opening a selected file, don't use the preview window, if\r\n   present.\r\n","3":"1. After opening a file with no tags defined in it with the\r\n   Tlist_Compact_Format option set, if the tags are updated, the folds\r\n   used for the files following the empty tags file are affected.\r\n2. On MS-Windows, use a \"taglist.cmd\" temporary file to run exuberant\r\n   ctags. This is to handle space characters in the file names and\r\n   in the exuberant ctags path name.\r\n3. In the taglist window, when a file is re-sorted or updated open the\r\n   fold for the file.\r\n4. When the 'shellxquote' option is set to double quotes, escape\r\n   double quotes in the command executed for exuberant ctags.\r\n5. On FreeBSD, exuberant ctags is installed as exctags, look for\r\n   exctags in the PATH.\r\n6. If two taglist plugins are present (one in the system Vim directory\r\n   and another in the user's .vim\/plugin directory), then the plugin\r\n   in the users's .vim directory overrides the version in the system\r\n   vim directory.\r\n7. When the :TlistMessages command is issued display the debug\r\n   messages in a taglist.txt buffer.\r\n8. Clear the readonly option for the taglist buffer\r\n9. When opening a selected file, don't use the preview window, if\r\n   present.\r\n","package":"taglist_42.zip","4":"taglist_42.zip","src_id":"6416","5":"6416","creation_date":"1163526299","6":"1163526299"},{"0":"273","vim_version":"6.0","1":"6.0","script_version":"4.1","2":"4.1","version_comment":"When the Tlist_File_Fold_Auto_Close variable is set to 1, jumping to the taglist window closes all the folds. Modified the plugin to not close the fold for the currently active file. When the TlistLock and TlistUnlock commands are invoked, an error message is displayed. This problem is fixed.","3":"When the Tlist_File_Fold_Auto_Close variable is set to 1, jumping to the taglist window closes all the folds. Modified the plugin to not close the fold for the currently active file. When the TlistLock and TlistUnlock commands are invoked, an error message is displayed. This problem is fixed.","package":"taglist_41.zip","4":"taglist_41.zip","src_id":"6158","5":"6158","creation_date":"1157918390","6":"1157918390"},{"0":"273","vim_version":"6.0","1":"6.0","script_version":"4.0","2":"4.0","version_comment":"Fixes:\r\nFix the problems in using the taglist plugin with Vim7 tabs. When\r\nTlist_File_Fold_Auto_Close is set, close the tag fold when leaving a\r\nbuffer.  When jumping to a selected tag, if the file is opened in more\r\nthan one window, use the previous window from which the user entered\r\nthe taglist window.\r\nNew features:\r\nSupport for displaying the tag prototype as a tooltip.  Support for\r\nspecifying additional commands after the taglist commands using the\r\nbar separator.\r\n","3":"Fixes:\r\nFix the problems in using the taglist plugin with Vim7 tabs. When\r\nTlist_File_Fold_Auto_Close is set, close the tag fold when leaving a\r\nbuffer.  When jumping to a selected tag, if the file is opened in more\r\nthan one window, use the previous window from which the user entered\r\nthe taglist window.\r\nNew features:\r\nSupport for displaying the tag prototype as a tooltip.  Support for\r\nspecifying additional commands after the taglist commands using the\r\nbar separator.\r\n","package":"taglist_40.zip","4":"taglist_40.zip","src_id":"6147","5":"6147","creation_date":"1157580180","6":"1157580180"},{"0":"273","vim_version":"6.0","1":"6.0","script_version":"4.0b4","2":"4.0b4","version_comment":"Fixes:\r\n1. When 'Tlist_Show_One_File' is set, after few files are opened,\r\n   unable to select tags from the taglist window.\r\n2. When the taglist plugin is stored in a directory with space characters\r\n   in the name, the autoloading of taglist plugin fails.\r\nNew features:\r\n1. Support for moving cursor to the taglist window when using the\r\n   \":TlistToggle\" command.\r\n2. When all the tags in a file are of the same type, in the taglist\r\n   menu, don't display the tag type.\r\n3. Changed the '?' help key to 'F1' in the taglist window.\r\n4. Set the filetype for the taglist buffer to 'taglist'\r\n5. In Vim7, set the 'winfixwidth' option for the taglist window.\r\n6. When jumping between files using the ]] or <Tab> and [[ or <Backspace>\r\n   keys, wrap around at the first and last file.\r\n","3":"Fixes:\r\n1. When 'Tlist_Show_One_File' is set, after few files are opened,\r\n   unable to select tags from the taglist window.\r\n2. When the taglist plugin is stored in a directory with space characters\r\n   in the name, the autoloading of taglist plugin fails.\r\nNew features:\r\n1. Support for moving cursor to the taglist window when using the\r\n   \":TlistToggle\" command.\r\n2. When all the tags in a file are of the same type, in the taglist\r\n   menu, don't display the tag type.\r\n3. Changed the '?' help key to 'F1' in the taglist window.\r\n4. Set the filetype for the taglist buffer to 'taglist'\r\n5. In Vim7, set the 'winfixwidth' option for the taglist window.\r\n6. When jumping between files using the ]] or <Tab> and [[ or <Backspace>\r\n   keys, wrap around at the first and last file.\r\n","package":"taglist_40b4.zip","4":"taglist_40b4.zip","src_id":"5548","5":"5548","creation_date":"1144880228","6":"1144880228"},{"0":"273","vim_version":"6.0","1":"6.0","script_version":"4.0b3","2":"4.0b3","version_comment":"The following changes are made in this version:\r\n\r\n1. Delay loading of the taglist plugin to reduce the Vim startup time.\r\n2. Support for recursively adding multiples files to the taglist using the\r\n   ':TlistAddFilesRecursive' command.\r\n3. New ':TlistOpen' command to open and jump to the taglist window.\r\n4. New ':TlistToggle' command to supersede the ':Tlist' command.\r\n5. New 'Tlist_Close_On_Select' option for closing the taglist window\r\n   when a file is selected.\r\n6. New 'Tlist_Auto_Update' option to enable\/disable processing of newly\r\n   edited files.\r\n7. New ':TlistLock' and ':TlistUnlock' commands to lock and unlock the\r\n   taglist.\r\n8. New 'Tlist_Highlight_Tag_On_BufEnter' option to enable\/disable\r\n   highlighting of the current tag on entering a buffer.\r\n9. When the taglist buffer is created from a Vim session file, update\r\n   the taglist with the files from the session file.\r\n10. Change the background color used for highlighting file names in the\r\n    taglist window.\r\n11. When <Space> is pressed on a file name or a tag type name in the\r\n    taglist window, display information about the number of tags.\r\n12. Set the 'foldlevel' option to a high value in the taglist window.\r\n13. When refreshing the taglist window, process all the opened buffers.\r\n14. When moving between windows, disable and enable autocommands.\r\n15. When a file is selected from the taglist window, use a non-plugin\r\n    window to edit the file.\r\n16. If 'Tlist_Exit_OnlyWindow' is set and when exiting Vim, make sure\r\n    the '0 mark is set to the previous buffer.\r\n17. When using the taglist plugin with the winmanager plugin and\r\n    'Tlist_Process_File_Always' is set or the taglist menu is enabled,\r\n    sometimes, it is not possible to jump to other windows from the\r\n    taglist window using the keyboard. Fixed this problem.\r\n18. While opening files in a new window, use filenames instead of buffer\r\n    numbers.\r\n","3":"The following changes are made in this version:\r\n\r\n1. Delay loading of the taglist plugin to reduce the Vim startup time.\r\n2. Support for recursively adding multiples files to the taglist using the\r\n   ':TlistAddFilesRecursive' command.\r\n3. New ':TlistOpen' command to open and jump to the taglist window.\r\n4. New ':TlistToggle' command to supersede the ':Tlist' command.\r\n5. New 'Tlist_Close_On_Select' option for closing the taglist window\r\n   when a file is selected.\r\n6. New 'Tlist_Auto_Update' option to enable\/disable processing of newly\r\n   edited files.\r\n7. New ':TlistLock' and ':TlistUnlock' commands to lock and unlock the\r\n   taglist.\r\n8. New 'Tlist_Highlight_Tag_On_BufEnter' option to enable\/disable\r\n   highlighting of the current tag on entering a buffer.\r\n9. When the taglist buffer is created from a Vim session file, update\r\n   the taglist with the files from the session file.\r\n10. Change the background color used for highlighting file names in the\r\n    taglist window.\r\n11. When <Space> is pressed on a file name or a tag type name in the\r\n    taglist window, display information about the number of tags.\r\n12. Set the 'foldlevel' option to a high value in the taglist window.\r\n13. When refreshing the taglist window, process all the opened buffers.\r\n14. When moving between windows, disable and enable autocommands.\r\n15. When a file is selected from the taglist window, use a non-plugin\r\n    window to edit the file.\r\n16. If 'Tlist_Exit_OnlyWindow' is set and when exiting Vim, make sure\r\n    the '0 mark is set to the previous buffer.\r\n17. When using the taglist plugin with the winmanager plugin and\r\n    'Tlist_Process_File_Always' is set or the taglist menu is enabled,\r\n    sometimes, it is not possible to jump to other windows from the\r\n    taglist window using the keyboard. Fixed this problem.\r\n18. While opening files in a new window, use filenames instead of buffer\r\n    numbers.\r\n","package":"taglist_40b3.zip","4":"taglist_40b3.zip","src_id":"4924","5":"4924","creation_date":"1135792886","6":"1135792886"},{"0":"273","vim_version":"6.0","1":"6.0","script_version":"4.0b2","2":"4.0b2","version_comment":"1. Added the TlistAddFiles command to add multiple files to the taglist window without opening them.\r\n2. Maintain the taglist window width and height across Vim window layout changes.\r\n3. Restore the Vim window location after the taglist window is closed.\r\n4. Use a simpler regular expression for parsing tags output.\r\n5. When a closed fold is selected in the taglist window, open the fold and jump to the file.\r\n6. When the Tlist_Auto_Open variable is set, open the taglist window only when a supported type of file is opened.\r\n7. When displaying tags for a single file, center the current tag line when opening a file.\r\n8. When jumping to a tag, add the previous location to the jump list.\r\n9. Fixed a problem with recording timestamps in the debug messages on MS-Windows.\r\n10. Set the ' mark when jumping to a selected tag.\r\n","3":"1. Added the TlistAddFiles command to add multiple files to the taglist window without opening them.\r\n2. Maintain the taglist window width and height across Vim window layout changes.\r\n3. Restore the Vim window location after the taglist window is closed.\r\n4. Use a simpler regular expression for parsing tags output.\r\n5. When a closed fold is selected in the taglist window, open the fold and jump to the file.\r\n6. When the Tlist_Auto_Open variable is set, open the taglist window only when a supported type of file is opened.\r\n7. When displaying tags for a single file, center the current tag line when opening a file.\r\n8. When jumping to a tag, add the previous location to the jump list.\r\n9. Fixed a problem with recording timestamps in the debug messages on MS-Windows.\r\n10. Set the ' mark when jumping to a selected tag.\r\n","package":"taglist_40b2.zip","4":"taglist_40b2.zip","src_id":"4455","5":"4455","creation_date":"1122911431","6":"1122911431"},{"0":"273","vim_version":"6.0","1":"6.0","script_version":"4.0b1","2":"4.0b1","version_comment":"Added support for optionally displaying the tags in the drop-down\/popup menu. Performance enhancments, various bug fixes and debug support.","3":"Added support for optionally displaying the tags in the drop-down\/popup menu. Performance enhancments, various bug fixes and debug support.","package":"taglist_40b1.zip","4":"taglist_40b1.zip","src_id":"4124","5":"4124","creation_date":"1112738535","6":"1112738535"},{"0":"273","vim_version":"6.0","1":"6.0","script_version":"3.4","2":"3.4","version_comment":"1. Introduced a new option 'Tlist_Show_One_File\" to display the tags for only the current buffer in the taglist window.\r\n2. Support for not displaying the tags for a user-deleted file in the taglist window.\r\n3. Fix for sharing the mouse single click map with other plugins","3":"1. Introduced a new option 'Tlist_Show_One_File\" to display the tags for only the current buffer in the taglist window.\r\n2. Support for not displaying the tags for a user-deleted file in the taglist window.\r\n3. Fix for sharing the mouse single click map with other plugins","package":"taglist.zip","4":"taglist.zip","src_id":"3340","5":"3340","creation_date":"1092660977","6":"1092660977"},{"0":"273","vim_version":"6.0","1":"6.0","script_version":"3.3","2":"3.3","version_comment":"1. If Tlist_Ctags_Cmd variable is not set, on startup, check for the\r\n   presence of exuberant-ctags or ctags or tags in the PATH and set\r\n   Tlist_Ctags_Cmd variable accordingly. If none of the executable is\r\n   found, then the taglist plugin will not be not loaded.\r\n2. Added a new configuration variable Tlist_Enable_Fold_Column to\r\n   enable or disable fold columns in the taglist window.\r\n3. Added support for setting the taglist application name used by the\r\n   winmanager plugin and the cream package.\r\n4. Two new key mappings ([[ and ]]) are added to the taglist window to\r\n   move between files.\r\n5. When a file is modified, the taglist window will be automatically\r\n   updated (after going to some other window or buffer and then coming\r\n   to the modified buffer).\r\n6. Made the Tlist_Update_File_Tags() function as a global function.\r\n   This function can be used to add or update the tags for a new file.\r\n7. Updated the Tlist_Get_Tag_Prototype_By_Line() and the \r\n   Tlist_Get_Tagname_By_Line() functions to get the tag name and tag\r\n   prototype for the specified line in a file.\r\n","3":"1. If Tlist_Ctags_Cmd variable is not set, on startup, check for the\r\n   presence of exuberant-ctags or ctags or tags in the PATH and set\r\n   Tlist_Ctags_Cmd variable accordingly. If none of the executable is\r\n   found, then the taglist plugin will not be not loaded.\r\n2. Added a new configuration variable Tlist_Enable_Fold_Column to\r\n   enable or disable fold columns in the taglist window.\r\n3. Added support for setting the taglist application name used by the\r\n   winmanager plugin and the cream package.\r\n4. Two new key mappings ([[ and ]]) are added to the taglist window to\r\n   move between files.\r\n5. When a file is modified, the taglist window will be automatically\r\n   updated (after going to some other window or buffer and then coming\r\n   to the modified buffer).\r\n6. Made the Tlist_Update_File_Tags() function as a global function.\r\n   This function can be used to add or update the tags for a new file.\r\n7. Updated the Tlist_Get_Tag_Prototype_By_Line() and the \r\n   Tlist_Get_Tagname_By_Line() functions to get the tag name and tag\r\n   prototype for the specified line in a file.\r\n","package":"taglist.zip","4":"taglist.zip","src_id":"3091","5":"3091","creation_date":"1086132887","6":"1086132887"},{"0":"273","vim_version":"6.0","1":"6.0","script_version":"3.2","2":"3.2","version_comment":"Added support for closing the tags tree for inactive files, removing the tags tree for deleted buffers, processing the tags when the taglist window is not opened, disabling the automatic highlighting of the current tag, displaying name of the current tag.","3":"Added support for closing the tags tree for inactive files, removing the tags tree for deleted buffers, processing the tags when the taglist window is not opened, disabling the automatic highlighting of the current tag, displaying name of the current tag.","package":"taglist.zip","4":"taglist.zip","src_id":"2978","5":"2978","creation_date":"1082902190","6":"1082902190"},{"0":"273","vim_version":"6.0","1":"6.0","script_version":"3.1","2":"3.1","version_comment":"Added support for saving and restoring taglist sessions. Separated the taglist documentation into a separate file in Vim help format.","3":"Added support for saving and restoring taglist sessions. Separated the taglist documentation into a separate file in Vim help format.","package":"taglist.zip","4":"taglist.zip","src_id":"2444","5":"2444","creation_date":"1067769250","6":"1067769250"},{"0":"273","vim_version":"6.0","1":"6.0","script_version":"3.0","2":"3.0","version_comment":"Added support for displaying tags defined in multiple files.","3":"Added support for displaying tags defined in multiple files.","package":"taglist.vim","4":"taglist.vim","src_id":"2353","5":"2353","creation_date":"1064430824","6":"1064430824"},{"0":"273","vim_version":"6.0","1":"6.0","script_version":"2.8","2":"2.8","version_comment":"Added information about the taglist mailing list.","3":"Added information about the taglist mailing list.","package":"taglist.vim","4":"taglist.vim","src_id":"2334","5":"2334","creation_date":"1063541000","6":"1063541000"},{"0":"273","vim_version":"6.0","1":"6.0","script_version":"2.7","2":"2.7","version_comment":"1. Added TlistUpdate command to update the taglist window.\r\n2. Made the taglist highlight groups user configurable.\r\n3. Fixed a problem in the taglist integration with the winmanager plugin","3":"1. Added TlistUpdate command to update the taglist window.\r\n2. Made the taglist highlight groups user configurable.\r\n3. Fixed a problem in the taglist integration with the winmanager plugin","package":"taglist.vim","4":"taglist.vim","src_id":"2250","5":"2250","creation_date":"1061466037","6":"1061466037"},{"0":"273","vim_version":"6.0","1":"6.0","script_version":"2.6","2":"2.6","version_comment":"1. Added support for previewing a tag.\r\n2. Added the TlistClose command to close the taglist window\r\n3. Added the Tlist_Exit_OnlyWindow option to close the taglist window if only that window is open.","3":"1. Added support for previewing a tag.\r\n2. Added the TlistClose command to close the taglist window\r\n3. Added the Tlist_Exit_OnlyWindow option to close the taglist window if only that window is open.","package":"taglist.vim","4":"taglist.vim","src_id":"2054","5":"2054","creation_date":"1055189710","6":"1055189710"},{"0":"273","vim_version":"6.0","1":"6.0","script_version":"2.5","2":"2.5","version_comment":"Added support for highlighting the tag scope. Added support for displaying namespaces in C++ files. Updated the comments.","3":"Added support for highlighting the tag scope. Added support for displaying namespaces in C++ files. Updated the comments.","package":"taglist.vim","4":"taglist.vim","src_id":"1941","5":"1941","creation_date":"1051301389","6":"1051301389"}]},"272":{"script_id":"272","0":"272","script_name":"multi.vim","1":"multi.vim","script_type":"utility","2":"utility","summary":"using Greenhills Multi as C\/C++ compiler for quickfix","3":"using Greenhills Multi as C\/C++ compiler for quickfix","description":"Script to use Greenhills Multi as C\/C++ compiler from vim with ':make <project_build_file>'.\r\nSets compiler and errorformat for use with quickfix commands.\r\nNeeds a tool ('catch', not supported) on NT4 to catch stderr and stdout in my environment.\r\n(Probably not necessary under Unix).\r\n\r\nDoes not catch all error and warning formats (especially. no linker problems).","4":"Script to use Greenhills Multi as C\/C++ compiler from vim with ':make <project_build_file>'.\r\nSets compiler and errorformat for use with quickfix commands.\r\nNeeds a tool ('catch', not supported) on NT4 to catch stderr and stdout in my environment.\r\n(Probably not necessary under Unix).\r\n\r\nDoes not catch all error and warning formats (especially. no linker problems).","install_details":"Drop multi.vim in c:\\vim\\vimfiles\\compiler and add the following autocommand to your _vimrc: \r\nau BufNewFile,BufRead *.c  compiler multi\r\n","5":"Drop multi.vim in c:\\vim\\vimfiles\\compiler and add the following autocommand to your _vimrc: \r\nau BufNewFile,BufRead *.c  compiler multi\r\n","first_name":"thomas","6":"thomas","last_name":"ramming","7":"ramming","releases":[{"0":"272","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"multi.vim","4":"multi.vim","src_id":"795","5":"795","creation_date":"1019000548","6":"1019000548"}]},"271":{"script_id":"271","0":"271","script_name":"navajo-night","1":"navajo-night","script_type":"color scheme","2":"color scheme","summary":"A blue scheme, inverse of navajo","3":"A blue scheme, inverse of navajo","description":"This is simply the inverse of the navajo colour scheme.\r\nI was using navajo, and hit visual bell enough times to go \"hey, that looks cool\" ;-)\r\n\r\nSo here it is.  Also includes the statusbar colours  and assistance for spell checking from the Cream version of the navajo scheme.\r\n\r\nThanks to R. Edward Ralston for navajo, Steve Hall for Cream, and Srinath Avadhanula for misc bug fixes.\r\n","4":"This is simply the inverse of the navajo colour scheme.\r\nI was using navajo, and hit visual bell enough times to go \"hey, that looks cool\" ;-)\r\n\r\nSo here it is.  Also includes the statusbar colours  and assistance for spell checking from the Cream version of the navajo scheme.\r\n\r\nThanks to R. Edward Ralston for navajo, Steve Hall for Cream, and Srinath Avadhanula for misc bug fixes.\r\n","install_details":"Drop it in your colors directory with the rest of the nice colour schemes you've made for vim and forgotten to upload here :) and from command mode, :colo navajo-night\r\nor add \"colorscheme navajo-night\" to your vimrc","5":"Drop it in your colors directory with the rest of the nice colour schemes you've made for vim and forgotten to upload here :) and from command mode, :colo navajo-night\r\nor add \"colorscheme navajo-night\" to your vimrc","first_name":"Matthew","6":"Matthew","last_name":"Hawkins","7":"Hawkins","releases":[{"0":"271","vim_version":"6.0","1":"6.0","script_version":"1.1","2":"1.1","version_comment":"Merged in changes from Srinath Avadhanula and Steve Hall.\r\nThis version will be distributed with a future version of Cream.\r\nTODO: (note to self) download this from home and merge in the cterm fixes.","3":"Merged in changes from Srinath Avadhanula and Steve Hall.\r\nThis version will be distributed with a future version of Cream.\r\nTODO: (note to self) download this from home and merge in the cterm fixes.","package":"navajo-night.vim","4":"navajo-night.vim","src_id":"805","5":"805","creation_date":"1019428941","6":"1019428941"},{"0":"271","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"fixed cterm colours, now the script doesn't whine when its loaded.\r\nnot 100% happy with the colours, but its better than errors ;)\r\n","3":"fixed cterm colours, now the script doesn't whine when its loaded.\r\nnot 100% happy with the colours, but its better than errors ;)\r\n","package":"navajo-night.vim","4":"navajo-night.vim","src_id":"790","5":"790","creation_date":"1018560209","6":"1018560209"}]},"270":{"script_id":"270","0":"270","script_name":"Cool colors","1":"Cool colors","script_type":"color scheme","2":"color scheme","summary":"Colors based on inverted SciTE colors (GUI only)","3":"Colors based on inverted SciTE colors (GUI only)","description":"Dark background.\r\nHere is a screenshot:\r\nhttp:\/\/www.mcl.hu\/~kgergely\/cool.png","4":"Dark background.\r\nHere is a screenshot:\r\nhttp:\/\/www.mcl.hu\/~kgergely\/cool.png","install_details":"","5":"","first_name":"Gergely","6":"Gergely","last_name":"Kontra","7":"Kontra","releases":[{"0":"270","vim_version":"6.0","1":"6.0","script_version":"0.11","2":"0.11","version_comment":"Slightly better colors. I hope","3":"Slightly better colors. I hope","package":"cool.vim","4":"cool.vim","src_id":"981","5":"981","creation_date":"1025663889","6":"1025663889"},{"0":"270","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"cool.vim","4":"cool.vim","src_id":"777","5":"777","creation_date":"1018433035","6":"1018433035"}]},"269":{"script_id":"269","0":"269","script_name":"scite colors","1":"scite colors","script_type":"color scheme","2":"color scheme","summary":"Scite-like colors (GUI only)","3":"Scite-like colors (GUI only)","description":"Color scheme based on the SciTE editor's colors.\r\nHere is a snapshot:\r\nhttp:\/\/www.mcl.hu\/~kgergely\/scite.png","4":"Color scheme based on the SciTE editor's colors.\r\nHere is a snapshot:\r\nhttp:\/\/www.mcl.hu\/~kgergely\/scite.png","install_details":"","5":"","first_name":"Gergely","6":"Gergely","last_name":"Kontra","7":"Kontra","releases":[{"0":"269","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"scite.vim","4":"scite.vim","src_id":"776","5":"776","creation_date":"1018432913","6":"1018432913"}]},"268":{"script_id":"268","0":"268","script_name":"byteme.vim","1":"byteme.vim","script_type":"utility","2":"utility","summary":"Goto Hex Offset","3":"Goto Hex Offset","description":"A few years ago I had to write a streaming single-page to multi-page TIFF converter.  Doing so required that I spend a lot of time wondering around in a HEX editor looking at the bytes that made up the TIFF headers.  The biggest part to tweaking the image files was getting all of the offsets calculated correctly.\r\n\r\nI was using MultiEdit for an editor at the time and needed \"Goto Hex Offset\" functionality that ME didn't have so I wrote a cmac function to do it for me.  It's purpose was to take me to a specified _byte_ in _me_ (MultiEdit) hence I named the function \"ByteMe\".\r\n\r\nA few months ago, I started using VIM.  Once again I needed \"Goto Hex Offset\" functionality which VIM did not have.  So, I rewrote my cmac ByteMe functionality in VIM and the result was this byteme.vim plugin.\r\n\r\nI'm fairly new to VIM so I expect my code could be much, much simpler, but this at least works for now.\r\n\r\nI wrote this on a Win2000 box using GVim 6.0 and have since upgraded to GVim 6.1 with no effect to byteme.vim.  I also tested it in gvim 6.0 running in Red Hat Linux 7.2 and it appeared to work ok (after passing it through dos2unix).  I even tested it in vim 6.0 on Red Hat Linux 7.2 and the byteme.vim functionality works but I have not figured out how to make the key mapping work.  I could only fire off the function using \":call ByteMe()\".\r\n\r\nI am using the xxd utility to generate the hex.  For anyone who might not have xxd on your Windows box, I got mine by downloading and installing Cygwin and then adding c:\\cygwin\\bin to my path. (Little warning about installing cygwin and then putting it at the beginning of your windows path. At least for me, this breaks my vim ftp functionality every time.  I keep getting this 'bad port' error.  To fix it, I just go to ...\\cygwin\\bin\\ftp.exe and rename it to ...\\cygwin_ftp.exe.  That forces vim to use the default Windows ftp and fixes the 'bad port' error. If I want to use the cygwin ftp, I just type cygwin_ftp.)\r\n\r\nbyteme.vim is written to use the format returned by the generic xxd hex dump.  If you use any switches to get xxd to change the format, or use some other utility to generate the hex, you'll probably have to rewrite byteme.vim.\r\n\r\nTo use: Once you have installed the plugin, reopen VIM, open the file you plan to view, convert to hex, hit <M-g> (Alt-g on a Windows style keyboard), enter the new offset in hex (e.g. fe09), hit enter, and you should be there.  An entry containing non-valid hex chars (e.g. fgtr) should take you to byte 0.  If the offset you enter is past then end of your file, you should end up at the end of the file but without any major error\/warning so pay attention.","4":"A few years ago I had to write a streaming single-page to multi-page TIFF converter.  Doing so required that I spend a lot of time wondering around in a HEX editor looking at the bytes that made up the TIFF headers.  The biggest part to tweaking the image files was getting all of the offsets calculated correctly.\r\n\r\nI was using MultiEdit for an editor at the time and needed \"Goto Hex Offset\" functionality that ME didn't have so I wrote a cmac function to do it for me.  It's purpose was to take me to a specified _byte_ in _me_ (MultiEdit) hence I named the function \"ByteMe\".\r\n\r\nA few months ago, I started using VIM.  Once again I needed \"Goto Hex Offset\" functionality which VIM did not have.  So, I rewrote my cmac ByteMe functionality in VIM and the result was this byteme.vim plugin.\r\n\r\nI'm fairly new to VIM so I expect my code could be much, much simpler, but this at least works for now.\r\n\r\nI wrote this on a Win2000 box using GVim 6.0 and have since upgraded to GVim 6.1 with no effect to byteme.vim.  I also tested it in gvim 6.0 running in Red Hat Linux 7.2 and it appeared to work ok (after passing it through dos2unix).  I even tested it in vim 6.0 on Red Hat Linux 7.2 and the byteme.vim functionality works but I have not figured out how to make the key mapping work.  I could only fire off the function using \":call ByteMe()\".\r\n\r\nI am using the xxd utility to generate the hex.  For anyone who might not have xxd on your Windows box, I got mine by downloading and installing Cygwin and then adding c:\\cygwin\\bin to my path. (Little warning about installing cygwin and then putting it at the beginning of your windows path. At least for me, this breaks my vim ftp functionality every time.  I keep getting this 'bad port' error.  To fix it, I just go to ...\\cygwin\\bin\\ftp.exe and rename it to ...\\cygwin_ftp.exe.  That forces vim to use the default Windows ftp and fixes the 'bad port' error. If I want to use the cygwin ftp, I just type cygwin_ftp.)\r\n\r\nbyteme.vim is written to use the format returned by the generic xxd hex dump.  If you use any switches to get xxd to change the format, or use some other utility to generate the hex, you'll probably have to rewrite byteme.vim.\r\n\r\nTo use: Once you have installed the plugin, reopen VIM, open the file you plan to view, convert to hex, hit <M-g> (Alt-g on a Windows style keyboard), enter the new offset in hex (e.g. fe09), hit enter, and you should be there.  An entry containing non-valid hex chars (e.g. fgtr) should take you to byte 0.  If the offset you enter is past then end of your file, you should end up at the end of the file but without any major error\/warning so pay attention.","install_details":"Just drop byteme.vim in your plugin directory.  If you do NOT want the default keymap to use <M-g> (Alt-g on a Windows style keyboard), edit byteme.vim.","5":"Just drop byteme.vim in your plugin directory.  If you do NOT want the default keymap to use <M-g> (Alt-g on a Windows style keyboard), edit byteme.vim.","first_name":"Robert","6":"Robert","last_name":"Roberts","7":"Roberts","releases":[{"0":"268","vim_version":"6.0","1":"6.0","script_version":"0.0.2","2":"0.0.2","version_comment":"Nothing is different from version 0.0.1 except that I added some 'How-To-Use\" type verbiage as comments internal to the actual byteme.vim file.","3":"Nothing is different from version 0.0.1 except that I added some 'How-To-Use\" type verbiage as comments internal to the actual byteme.vim file.","package":"byteme.vim","4":"byteme.vim","src_id":"775","5":"775","creation_date":"1018348272","6":"1018348272"},{"0":"268","vim_version":"6.0","1":"6.0","script_version":"0.0.1","2":"0.0.1","version_comment":"Initial upload","3":"Initial upload","package":"byteme.vim","4":"byteme.vim","src_id":"774","5":"774","creation_date":"1018345902","6":"1018345902"}]},"267":{"script_id":"267","0":"267","script_name":"Nsis color","1":"Nsis color","script_type":"syntax","2":"syntax","summary":"Nullsoft install system scripts syntax highlight","3":"Nullsoft install system scripts syntax highlight","description":"Nullsoft install system (NSIS) scripts syntax highlight. NSIS is free and produce vary small and pretty installers. Look http:\/\/www.nullsoft.com\/free\/nsis\/ for details.","4":"Nullsoft install system (NSIS) scripts syntax highlight. NSIS is free and produce vary small and pretty installers. Look http:\/\/www.nullsoft.com\/free\/nsis\/ for details.","install_details":"","5":"","first_name":"Artem","6":"Artem","last_name":"Zankovich","7":"Zankovich","releases":[{"0":"267","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"nsis.zip","4":"nsis.zip","src_id":"772","5":"772","creation_date":"1018161231","6":"1018161231"}]},"266":{"script_id":"266","0":"266","script_name":"java.vim","1":"java.vim","script_type":"ftplugin","2":"ftplugin","summary":"Convenience mappings for Java programming","3":"Convenience mappings for Java programming","description":"Contains several mappings (about 30) to save typing when Java programming.  Most are short for keywords, types, etc.  (e.g. ,p ,s ,f ^Ts  -->  public static final String).  Some are more complex, like inserting a javadoc comment or expanding a constructor.\r\n\r\nThe script is commented sufficiently.\r\n\r\nI haven't added anything to this for ages, but there is no limit to how useful this can be, so please feel free to add updates.","4":"Contains several mappings (about 30) to save typing when Java programming.  Most are short for keywords, types, etc.  (e.g. ,p ,s ,f ^Ts  -->  public static final String).  Some are more complex, like inserting a javadoc comment or expanding a constructor.\r\n\r\nThe script is commented sufficiently.\r\n\r\nI haven't added anything to this for ages, but there is no limit to how useful this can be, so please feel free to add updates.","install_details":"Drop it in your ~\/.vim\/ftplugin or .\/vimfiles\/ftplugin directory.\r\nIf you already have a java ftplugin, create a subdirectory \"java\" and drop them both in.  Or rename this to java_maps.vim.","5":"Drop it in your ~\/.vim\/ftplugin or .\/vimfiles\/ftplugin directory.\r\nIf you already have a java ftplugin, create a subdirectory \"java\" and drop them both in.  Or rename this to java_maps.vim.","first_name":"Gavin","6":"Gavin","last_name":"Sinclair","7":"Sinclair","releases":[{"0":"266","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"java.vim","4":"java.vim","src_id":"768","5":"768","creation_date":"1018049879","6":"1018049879"}]},"265":{"script_id":"265","0":"265","script_name":"brief.vim","1":"brief.vim","script_type":"utility","2":"utility","summary":"Brief editor key binding emulation in Vim","3":"Brief editor key binding emulation in Vim","description":"The brief.vim Vim plugin emulates the brief editor key bindings and behavior\r\nin Vim.\r\n\r\nThe brief editor has only one mode - insert-mode. This plugin uses the Vim\r\n\"insertmode\" option to emulate the brief insert mode. This plugin will automatically\r\nstart the insert mode.  To properly use this plugin, you have to be in\r\ninsertmode always.  If you press escape, Vim will not go to the normal mode.\r\nIf you want to use any of the normal commands, press <C-o> and then the normal\r\nmode command. \r\n\r\nThis plugin uses the CTRL and ALT keys for the mappings. Before\r\nusing this plugin, make sure that the ALT and CTRL keys work in your Vim\r\ninstallation.\r\n\r\nThe following list of brief like key-mappings are provided:\r\n\r\nCursor Movement Keys:\r\n\r\n<Up>         - Move cursor up one line\r\n<Down>       - Move cursor down one line\r\n<C-Left>     - Goto beginning of previous word\r\n<C-Right>    - Goto beginning of next word\r\n<Home>       - Home key.  If you press once, cursor will move to the first\r\n               column in the current line.  If you press twice, cursor will\r\n               move to the first column in the first line in the current\r\n               page.  If you press thrice, cursor will be positioned at the\r\n               top of the file.\r\n<End>        - End key. If you press once, cursor will move to the last\r\n               column in the current line.  If you press twice, cursor will\r\n               move to the last column in the last line in the current page.\r\n               If you press thrice, cursor will be positioned at the end of\r\n               the file.\r\n<C-PageUp>   - Goto-beginning of file\r\n<C-PageDown> - goto-end of file\r\n<C-Home>     - Beginning-of-window\r\n<C-End>      - End-of-window\r\n<C-d>        - Scroll line down\r\n<C-e>        - Scroll line up\r\n<A-Home>     - Move the cursor to the first character on screen\r\n<A-End>      - Move the cursor to the last character on screen\r\n<C-b>        - Move the current line to the bottom of the window\r\n<C-c>        - Move the current line to the center of the window\r\n<C-t>        - Move the current line to the top of the window\r\n\r\nEditing Keys:\r\n\r\n<C-CR>       - Open a new line below the current line and goto that line\r\n<S-CR>       - open a new line below the current line, cursor stays in the\r\n               current line\r\n<A-i>        - Toggle insert mode\r\n<A-k>        - Delete from the cursor position to the end of line\r\n<C-k>        - Delete from the cursor position to the start of line\r\n<A-d>        - Delete the current line\r\n<kPlus>      - Copy line or mark to scrap buffer.  Vim register 'a' is used\r\n               as the scrap  buffer.\r\n<kMinus>     - Cut line or mark to scrap buffer.  Vim register 'a' is used\r\n               as the scrap buffer.\r\n<Ins>        - Paste scrab buffer contents to current cursor position.  Vim\r\n               register 'a' is used as the scrap buffer\r\n<C-Ins>      - Copy marked text to system clipboard.  If no mark, copy\r\n               current line\r\n<S-Ins>      - Paste the system clipboard contents to current cursor\r\n<S-Del>      - Cut the marked text to system clipboard. If no mark, cut the\r\n               current line\r\n<C-Del>      - Remove the marked text\r\n<C-v>        - Clipboard paste\r\n<A-g>        - Goto line\r\n<C-BS>       - Delete the previous word\r\n<A-BS>       - Delete the next word\r\n<A-\/>        - Complete a partially typed word\r\n<A-q>        - Quote the next character\r\n\r\nDelete Keys:\r\n\r\n<A-u>          :\r\n<kMultiply>  : Undo last operation.  Either keypad * key or <A-u> can be used.\r\n<A-y>          : Restore line\r\n<C-y>          : Redo the previously undid commands\r\n\r\nSearch and Replace Commands:\r\n\r\n<C-f>          :\r\n<F5>          :\r\n<A-s>         : String search\r\n<S-F5>       : search again\r\n<A-F5>       : Reverse search\r\n<F6>          : Search and replace from the current cursor position\r\n<A-t>         : Search and replace the current word from the current cursor position\r\n<S-F6>       : Repeat last search and replace\r\n<C-F5>       : toggle case sensitivity of search commands.\r\n\r\nBuffer Commands:\r\n\r\n<A-e>        - Open file\r\n<A-x>        - Exit\r\n<A-r>        - Read file\r\n<A-w>        - Save the current file\r\n<A-o>        - Save the current file in a different file name\r\n<A-n>        - Select next buffer from the buffer list\r\n<A-->        -\r\n<A-p>        - Select previous buffer from the buffer list\r\n<C-->        -\r\n<C-kMinus>   - Delete current buffer from buffer list\r\n<A-b>        - Display buffer list\r\n<A-f>        - Display buffer information\r\n\r\nCompiler related commands:\r\n\r\n<A-F10>      - Compile current buffer\r\n<C-n>        - Jump to the next error\r\n<C-l>        - pJump to the next previous error\r\n<C-p>        - View compiler output\r\n\r\nMark commands:\r\n\r\n<A-m>        - Toggle standard text marking mode\r\n<A-l>        - Toggle line marking mode\r\n<A-c>        - \r\n<A-a>        - Toggle column marking mode\r\n<A-h>        - Mark current word\r\n\r\nMisc commands:\r\n\r\n<A-v>        - Show version\r\n<C-Up>\r\n<C-Down>     - Goto next\/previous function\r\n<A-z>        - Start a shell\r\n<A-F1>       - Search for a keyword in online help\r\n\r\nBookmark:\r\n\r\n<A-0>        - Mark bookmark 0\r\n<A-1>        - Mark bookmark 1\r\n<A-2>        - Mark bookmark 2\r\n<A-3>        - Mark bookmark 3\r\n<A-4>        - Mark bookmark 4\r\n<A-5>        - Mark bookmark 5\r\n<A-6>        - Mark bookmark 6\r\n<A-7>        - Mark bookmark 7\r\n<A-8>        - Mark bookmark 8\r\n<A-9>        - Mark bookmark 9\r\n<A-j>        - Jump to a bookmark\r\n\r\nWindows Commands:\r\n\r\n<F3>         - Split window\r\n<F4>         - Delete window\r\n<A-F2>       - Zoom window\r\n<A-Down>     - Goto the window below the current window\r\n<A-Up>       - Goto the window above the current window\r\n\r\n","4":"The brief.vim Vim plugin emulates the brief editor key bindings and behavior\r\nin Vim.\r\n\r\nThe brief editor has only one mode - insert-mode. This plugin uses the Vim\r\n\"insertmode\" option to emulate the brief insert mode. This plugin will automatically\r\nstart the insert mode.  To properly use this plugin, you have to be in\r\ninsertmode always.  If you press escape, Vim will not go to the normal mode.\r\nIf you want to use any of the normal commands, press <C-o> and then the normal\r\nmode command. \r\n\r\nThis plugin uses the CTRL and ALT keys for the mappings. Before\r\nusing this plugin, make sure that the ALT and CTRL keys work in your Vim\r\ninstallation.\r\n\r\nThe following list of brief like key-mappings are provided:\r\n\r\nCursor Movement Keys:\r\n\r\n<Up>         - Move cursor up one line\r\n<Down>       - Move cursor down one line\r\n<C-Left>     - Goto beginning of previous word\r\n<C-Right>    - Goto beginning of next word\r\n<Home>       - Home key.  If you press once, cursor will move to the first\r\n               column in the current line.  If you press twice, cursor will\r\n               move to the first column in the first line in the current\r\n               page.  If you press thrice, cursor will be positioned at the\r\n               top of the file.\r\n<End>        - End key. If you press once, cursor will move to the last\r\n               column in the current line.  If you press twice, cursor will\r\n               move to the last column in the last line in the current page.\r\n               If you press thrice, cursor will be positioned at the end of\r\n               the file.\r\n<C-PageUp>   - Goto-beginning of file\r\n<C-PageDown> - goto-end of file\r\n<C-Home>     - Beginning-of-window\r\n<C-End>      - End-of-window\r\n<C-d>        - Scroll line down\r\n<C-e>        - Scroll line up\r\n<A-Home>     - Move the cursor to the first character on screen\r\n<A-End>      - Move the cursor to the last character on screen\r\n<C-b>        - Move the current line to the bottom of the window\r\n<C-c>        - Move the current line to the center of the window\r\n<C-t>        - Move the current line to the top of the window\r\n\r\nEditing Keys:\r\n\r\n<C-CR>       - Open a new line below the current line and goto that line\r\n<S-CR>       - open a new line below the current line, cursor stays in the\r\n               current line\r\n<A-i>        - Toggle insert mode\r\n<A-k>        - Delete from the cursor position to the end of line\r\n<C-k>        - Delete from the cursor position to the start of line\r\n<A-d>        - Delete the current line\r\n<kPlus>      - Copy line or mark to scrap buffer.  Vim register 'a' is used\r\n               as the scrap  buffer.\r\n<kMinus>     - Cut line or mark to scrap buffer.  Vim register 'a' is used\r\n               as the scrap buffer.\r\n<Ins>        - Paste scrab buffer contents to current cursor position.  Vim\r\n               register 'a' is used as the scrap buffer\r\n<C-Ins>      - Copy marked text to system clipboard.  If no mark, copy\r\n               current line\r\n<S-Ins>      - Paste the system clipboard contents to current cursor\r\n<S-Del>      - Cut the marked text to system clipboard. If no mark, cut the\r\n               current line\r\n<C-Del>      - Remove the marked text\r\n<C-v>        - Clipboard paste\r\n<A-g>        - Goto line\r\n<C-BS>       - Delete the previous word\r\n<A-BS>       - Delete the next word\r\n<A-\/>        - Complete a partially typed word\r\n<A-q>        - Quote the next character\r\n\r\nDelete Keys:\r\n\r\n<A-u>          :\r\n<kMultiply>  : Undo last operation.  Either keypad * key or <A-u> can be used.\r\n<A-y>          : Restore line\r\n<C-y>          : Redo the previously undid commands\r\n\r\nSearch and Replace Commands:\r\n\r\n<C-f>          :\r\n<F5>          :\r\n<A-s>         : String search\r\n<S-F5>       : search again\r\n<A-F5>       : Reverse search\r\n<F6>          : Search and replace from the current cursor position\r\n<A-t>         : Search and replace the current word from the current cursor position\r\n<S-F6>       : Repeat last search and replace\r\n<C-F5>       : toggle case sensitivity of search commands.\r\n\r\nBuffer Commands:\r\n\r\n<A-e>        - Open file\r\n<A-x>        - Exit\r\n<A-r>        - Read file\r\n<A-w>        - Save the current file\r\n<A-o>        - Save the current file in a different file name\r\n<A-n>        - Select next buffer from the buffer list\r\n<A-->        -\r\n<A-p>        - Select previous buffer from the buffer list\r\n<C-->        -\r\n<C-kMinus>   - Delete current buffer from buffer list\r\n<A-b>        - Display buffer list\r\n<A-f>        - Display buffer information\r\n\r\nCompiler related commands:\r\n\r\n<A-F10>      - Compile current buffer\r\n<C-n>        - Jump to the next error\r\n<C-l>        - pJump to the next previous error\r\n<C-p>        - View compiler output\r\n\r\nMark commands:\r\n\r\n<A-m>        - Toggle standard text marking mode\r\n<A-l>        - Toggle line marking mode\r\n<A-c>        - \r\n<A-a>        - Toggle column marking mode\r\n<A-h>        - Mark current word\r\n\r\nMisc commands:\r\n\r\n<A-v>        - Show version\r\n<C-Up>\r\n<C-Down>     - Goto next\/previous function\r\n<A-z>        - Start a shell\r\n<A-F1>       - Search for a keyword in online help\r\n\r\nBookmark:\r\n\r\n<A-0>        - Mark bookmark 0\r\n<A-1>        - Mark bookmark 1\r\n<A-2>        - Mark bookmark 2\r\n<A-3>        - Mark bookmark 3\r\n<A-4>        - Mark bookmark 4\r\n<A-5>        - Mark bookmark 5\r\n<A-6>        - Mark bookmark 6\r\n<A-7>        - Mark bookmark 7\r\n<A-8>        - Mark bookmark 8\r\n<A-9>        - Mark bookmark 9\r\n<A-j>        - Jump to a bookmark\r\n\r\nWindows Commands:\r\n\r\n<F3>         - Split window\r\n<F4>         - Delete window\r\n<A-F2>       - Zoom window\r\n<A-Down>     - Goto the window below the current window\r\n<A-Up>       - Goto the window above the current window\r\n\r\n","install_details":"To install the brief.vim plugin, follow these steps:\r\n\r\nStep1: Copy the brief.vim plugin to the ~\/.vim\/plugin directory\r\nStep2. Restart Vim\r\n","5":"To install the brief.vim plugin, follow these steps:\r\n\r\nStep1: Copy the brief.vim plugin to the ~\/.vim\/plugin directory\r\nStep2. Restart Vim\r\n","first_name":"Yegappan","6":"Yegappan","last_name":"Lakshmanan","7":"Lakshmanan","releases":[{"0":"265","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"brief.vim","4":"brief.vim","src_id":"767","5":"767","creation_date":"1018035256","6":"1018035256"}]},"264":{"script_id":"264","0":"264","script_name":"aspnet.vim","1":"aspnet.vim","script_type":"syntax","2":"syntax","summary":"ASP.NET syntax highlighting","3":"ASP.NET syntax highlighting","description":"Provide syntax highlighting for C# code withing <script runat=\"server\"> ... <\/script> blocks as well as @ directives in *.(aspx|ascx|asmx) files.\r\n\r\nThis is a work in progress.  It's not perfect by any means, but it's quite usable.","4":"Provide syntax highlighting for C# code withing <script runat=\"server\"> ... <\/script> blocks as well as @ directives in *.(aspx|ascx|asmx) files.\r\n\r\nThis is a work in progress.  It's not perfect by any means, but it's quite usable.","install_details":"Note that this really requires vim 6.1, or at least a C# syntax file called \"cs.vim\" in the $VIMRUNTIME\/syntax\/ directory.","5":"Note that this really requires vim 6.1, or at least a C# syntax file called \"cs.vim\" in the $VIMRUNTIME\/syntax\/ directory.","first_name":"Mark","6":"Mark","last_name":"Feeney","7":"Feeney","releases":[{"0":"264","vim_version":"6.0","1":"6.0","script_version":"1.3","2":"1.3","version_comment":"Initial upload","3":"Initial upload","package":"aspnet.vim","4":"aspnet.vim","src_id":"763","5":"763","creation_date":"1018010774","6":"1018010774"}]},"263":{"script_id":"263","0":"263","script_name":"csc.vim","1":"csc.vim","script_type":"utility","2":"utility","summary":"Compiler file for MS C#.  (csc, csc.exe)","3":"Compiler file for MS C#.  (csc, csc.exe)","description":"Use the Microsoft C# compiler from within Vim.  Parses error output from the compiler and populates the quickfix window.","4":"Use the Microsoft C# compiler from within Vim.  Parses error output from the compiler and populates the quickfix window.","install_details":"Drop csc.vim in c:\\vim\\vimfiles\\compiler and add the following autocommand to your _vimrc:\r\nau BufNewFile,BufRead *.cs compiler csc\r\n","5":"Drop csc.vim in c:\\vim\\vimfiles\\compiler and add the following autocommand to your _vimrc:\r\nau BufNewFile,BufRead *.cs compiler csc\r\n","first_name":"Mark","6":"Mark","last_name":"Feeney","7":"Feeney","releases":[{"0":"263","vim_version":"6.0","1":"6.0","script_version":"1.3","2":"1.3","version_comment":"Initial upload","3":"Initial upload","package":"csc.vim","4":"csc.vim","src_id":"762","5":"762","creation_date":"1018010559","6":"1018010559"}]},"262":{"script_id":"262","0":"262","script_name":"doc.vim","1":"doc.vim","script_type":"syntax","2":"syntax","summary":"Syntax colouring for ASCII documentation","3":"Syntax colouring for ASCII documentation","description":"Gives you syntax coloring for ASCII-documentation files.\r\nNot perfect, but may be a base for your own.\r\n\r\nDetects headlines (underlined with '-' or '='),\r\nenumerations, lists (starting with '-' or '*')\r\nsome simple time, date formats \r\nsome simple email addresses, web addresses.","4":"Gives you syntax coloring for ASCII-documentation files.\r\nNot perfect, but may be a base for your own.\r\n\r\nDetects headlines (underlined with '-' or '='),\r\nenumerations, lists (starting with '-' or '*')\r\nsome simple time, date formats \r\nsome simple email addresses, web addresses.","install_details":"copy file to vim\/syntax directory,\r\nenter ':so $VIM\/syntax\/doc.vim' in .txt or .doc files\r\nor edit some installation files to add it in the syntax menu.","5":"copy file to vim\/syntax directory,\r\nenter ':so $VIM\/syntax\/doc.vim' in .txt or .doc files\r\nor edit some installation files to add it in the syntax menu.","first_name":"thomas","6":"thomas","last_name":"ramming","7":"ramming","releases":[{"0":"262","vim_version":"6.0","1":"6.0","script_version":"0.3","2":"0.3","version_comment":"added red for german\/English Achtung\/attention Hinweis\/remark lines.","3":"added red for german\/English Achtung\/attention Hinweis\/remark lines.","package":"syncol_doc.zip","4":"syncol_doc.zip","src_id":"3338","5":"3338","creation_date":"1092631809","6":"1092631809"},{"0":"262","vim_version":"6.0","1":"6.0","script_version":"0.2","2":"0.2","version_comment":"some new matches for headlines, german quotes and a \r\ntextline sourrounded by underscore\/'abovescore' (called it cBlock).\r\nUsing extended ascii characters (see script printascii.vim).\r\n\r\nPacked with a sample ascii file and the same as html that you can see what my gvim does.","3":"some new matches for headlines, german quotes and a \r\ntextline sourrounded by underscore\/'abovescore' (called it cBlock).\r\nUsing extended ascii characters (see script printascii.vim).\r\n\r\nPacked with a sample ascii file and the same as html that you can see what my gvim does.","package":"syncol_doc.zip","4":"syncol_doc.zip","src_id":"797","5":"797","creation_date":"1019197152","6":"1019197152"},{"0":"262","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"doc.vim","4":"doc.vim","src_id":"760","5":"760","creation_date":"1017972596","6":"1017972596"}]},"261":{"script_id":"261","0":"261","script_name":"vimdoc","1":"vimdoc","script_type":"utility","2":"utility","summary":"produce vim documentation in man, html and LaTeX(PostScript) format","3":"produce vim documentation in man, html and LaTeX(PostScript) format","description":"This project is far from perfect, but it already works.\r\n\r\nUse this to produce vim documentation in html, man and LaTeX(PostScript) format.","4":"This project is far from perfect, but it already works.\r\n\r\nUse this to produce vim documentation in html, man and LaTeX(PostScript) format.","install_details":"Unpack this archive (tar xzf vimdoc-1.0.tar.gz), copy some (or all) vim help files to vimdoc-1.0\/txt directory and type 'make'.","5":"Unpack this archive (tar xzf vimdoc-1.0.tar.gz), copy some (or all) vim help files to vimdoc-1.0\/txt directory and type 'make'.","first_name":"\u013dubom\u00c3\u00adr","6":"Ľubom\u00c3\u00adr","last_name":"Host","7":"Host","releases":[{"0":"261","vim_version":"6.0","1":"6.0","script_version":"1.3","2":"1.3","version_comment":"Version 1.3 is usuable for usr_0*.txt files from user manual. Need more testing, product(vimmanual.ps) is already readable.\r\n","3":"Version 1.3 is usuable for usr_0*.txt files from user manual. Need more testing, product(vimmanual.ps) is already readable.\r\n","package":"vimdoc-1.3.tar.gz","4":"vimdoc-1.3.tar.gz","src_id":"788","5":"788","creation_date":"1018557972","6":"1018557972"},{"0":"261","vim_version":"6.0","1":"6.0","script_version":"1.2","2":"1.2","version_comment":"* Fixed problem with 'example' in fold.txt:425.\r\n* Fixed problem with vim modeline at end of fold.txt. It was considered as 'subsection'.","3":"* Fixed problem with 'example' in fold.txt:425.\r\n* Fixed problem with vim modeline at end of fold.txt. It was considered as 'subsection'.","package":"vimdoc-1.2.tar.gz","4":"vimdoc-1.2.tar.gz","src_id":"785","5":"785","creation_date":"1018541247","6":"1018541247"},{"0":"261","vim_version":"6.0","1":"6.0","script_version":"1.1","2":"1.1","version_comment":"Added support for index, subsubsection, $VIM, $VIMRUNTIME,  $VAR, special chars.\r\nTested for fold.txt tips.txt.\r\n","3":"Added support for index, subsubsection, $VIM, $VIMRUNTIME,  $VAR, special chars.\r\nTested for fold.txt tips.txt.\r\n","package":"vimdoc-1.1.tar.gz","4":"vimdoc-1.1.tar.gz","src_id":"766","5":"766","creation_date":"1018027305","6":"1018027305"},{"0":"261","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"vimdoc-1.0.tar.gz","4":"vimdoc-1.0.tar.gz","src_id":"751","5":"751","creation_date":"1017833758","6":"1017833758"}]},"260":{"script_id":"260","0":"260","script_name":"manxome foes colorscheme","1":"manxome foes colorscheme","script_type":"color scheme","2":"color scheme","summary":"a pleasant scheme for long vimming sessions","3":"a pleasant scheme for long vimming sessions","description":"The colorschemes that ship with vim all made me wince, and after several hours of editing, even the most innocuous of them would become unpleasant.  I designed this scheme to be both clearly marked up and easy on my eyes.  It reminds me of the default colorscheme of the Telegard BBS.","4":"The colorschemes that ship with vim all made me wince, and after several hours of editing, even the most innocuous of them would become unpleasant.  I designed this scheme to be both clearly marked up and easy on my eyes.  It reminds me of the default colorscheme of the Telegard BBS.","install_details":"Drop it in ~\/.vim\/colors and add \"colorscheme manxome\" to your vimrc, and you\\'re done!  See |:help colo| for more information.","5":"Drop it in ~\/.vim\/colors and add \"colorscheme manxome\" to your vimrc, and you\\'re done!  See |:help colo| for more information.","first_name":"Ricardo","6":"Ricardo","last_name":"Signes","7":"Signes","releases":[{"0":"260","vim_version":"6.0","1":"6.0","script_version":"R2v2","2":"R2v2","version_comment":"I've changed the fileformat to unix to prevent ^M errors.","3":"I've changed the fileformat to unix to prevent ^M errors.","package":"manxome.vim","4":"manxome.vim","src_id":"2151","5":"2151","creation_date":"1058346394","6":"1058346394"},{"0":"260","vim_version":"6.0","1":"6.0","script_version":"R2","2":"R2","version_comment":"Some colors have been tweaked for more pleasant vimming on LCD screens and dark CRTs.  I've added a few highlight types to pick up some syntax types I hadn't used before.","3":"Some colors have been tweaked for more pleasant vimming on LCD screens and dark CRTs.  I've added a few highlight types to pick up some syntax types I hadn't used before.","package":"manxome.vim","4":"manxome.vim","src_id":"1214","5":"1214","creation_date":"1032240370","6":"1032240370"},{"0":"260","vim_version":"6.0","1":"6.0","script_version":"R1","2":"R1","version_comment":"Initial upload","3":"Initial upload","package":"manxome.vim","4":"manxome.vim","src_id":"736","5":"736","creation_date":"1017505050","6":"1017505050"}]},"259":{"script_id":"259","0":"259","script_name":"lastchange.vim","1":"lastchange.vim","script_type":"utility","2":"utility","summary":"automatically set time-stamp on modification","3":"automatically set time-stamp on modification","description":"this (very) lightweight script automatically updates the time-stamp on a file when you :write it out.\r\nthe time-stamp is of the form:\r\n     Last Change: Sat Mar 30 04:00 PM 2002 PST\r\n\r\nThe script is similar to the example given in :help autocmd, the difference being that the time-stamp already\r\nthere is checked. If it is identical to the one being added, then nothing is done. Since the time-stamp\r\nis truncated to the last hour, this ensures that the undo buffer is changed only for :write's every hour.\r\n\r\nSet g:timeStampLeader in your ~\/.vimrc to change 'Last Change: ' \r\n(to 'Last modified: ' for instance)\r\n\r\nUse :NOMOD to force the time-stamp to be not updated.\r\nUse :MOD to change it back.\r\n\r\nPS: The update only works if the string 'Last Change: ' is found somewhere\r\nin the first 20 lines of the file. Only the first found occurence is processed.\r\n","4":"this (very) lightweight script automatically updates the time-stamp on a file when you :write it out.\r\nthe time-stamp is of the form:\r\n     Last Change: Sat Mar 30 04:00 PM 2002 PST\r\n\r\nThe script is similar to the example given in :help autocmd, the difference being that the time-stamp already\r\nthere is checked. If it is identical to the one being added, then nothing is done. Since the time-stamp\r\nis truncated to the last hour, this ensures that the undo buffer is changed only for :write's every hour.\r\n\r\nSet g:timeStampLeader in your ~\/.vimrc to change 'Last Change: ' \r\n(to 'Last modified: ' for instance)\r\n\r\nUse :NOMOD to force the time-stamp to be not updated.\r\nUse :MOD to change it back.\r\n\r\nPS: The update only works if the string 'Last Change: ' is found somewhere\r\nin the first 20 lines of the file. Only the first found occurence is processed.\r\n","install_details":"drop in ~\/vimfiles\/plugin (DOS) or ~\/.vim\/plugin (UNIX)\r\n","5":"drop in ~\/vimfiles\/plugin (DOS) or ~\/.vim\/plugin (UNIX)\r\n","first_name":"Srinath","6":"Srinath","last_name":"Avadhanula","7":"Avadhanula","releases":[{"0":"259","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"lastchange.vim","4":"lastchange.vim","src_id":"735","5":"735","creation_date":"1017505008","6":"1017505008"}]},"258":{"script_id":"258","0":"258","script_name":"htmlmap","1":"htmlmap","script_type":"utility","2":"utility","summary":"macros to help type HTML entities","3":"macros to help type HTML entities","description":"This script defines a number of macros, all for insert mode in HTML files. Once installed, it will automatically \"translate\" characters into their &...; strings: so for instance if you type \"\u00c3\u00a4\" the characters \" & a u m l ; \" will be inserted (without the intervening spaces). A mechanism similar to Vim's \"digraphs\" is also supported but with another key (F12, but you can replace it with something else if it doesn't suit you), so that e.g. \"<F12>oe\" inserts the numeric code for the oe ligature (above 255, some browsers know the numeric codes but not the symbolic entities such as &oelig;).\r\n\r\nThe script contains a lot of comments to make it largely self-explanatory.","4":"This script defines a number of macros, all for insert mode in HTML files. Once installed, it will automatically \"translate\" characters into their &...; strings: so for instance if you type \"\u00c3\u00a4\" the characters \" & a u m l ; \" will be inserted (without the intervening spaces). A mechanism similar to Vim's \"digraphs\" is also supported but with another key (F12, but you can replace it with something else if it doesn't suit you), so that e.g. \"<F12>oe\" inserts the numeric code for the oe ligature (above 255, some browsers know the numeric codes but not the symbolic entities such as &oelig;).\r\n\r\nThe script contains a lot of comments to make it largely self-explanatory.","install_details":"Add the line\r\n\r\n    source <path>\/htmlmap.vim\r\n\r\n(where <path> is the directory where you downloaded this script) to the file ~\/.vim\/ftplugin\/after\/html.vim (for Unix) or ~\/vimfiles\/ftplugin\/after\/html.vim (for Windows). Create the file and the directories if they don't yet exist.\r\n\r\nOptionally, add\r\n\r\n    imap <F12> <C-K>\r\n\r\nto your vimrc if you want to use the same key as a digraph prefix for entities in HTML and for characters in other files.\r\n\r\nNote that if your vim does not support autocommands you can still make this script work by sourcing it manually in the buffer(s) where you need it.","5":"Add the line\r\n\r\n    source <path>\/htmlmap.vim\r\n\r\n(where <path> is the directory where you downloaded this script) to the file ~\/.vim\/ftplugin\/after\/html.vim (for Unix) or ~\/vimfiles\/ftplugin\/after\/html.vim (for Windows). Create the file and the directories if they don't yet exist.\r\n\r\nOptionally, add\r\n\r\n    imap <F12> <C-K>\r\n\r\nto your vimrc if you want to use the same key as a digraph prefix for entities in HTML and for characters in other files.\r\n\r\nNote that if your vim does not support autocommands you can still make this script work by sourcing it manually in the buffer(s) where you need it.","first_name":"Antoine","6":"Antoine","last_name":"Mechelynck","7":"Mechelynck","releases":[{"0":"258","vim_version":"6.0","1":"6.0","script_version":"1.01pl4","2":"1.01pl4","version_comment":"Euro-Sign added.","3":"Euro-Sign added.","package":"htmlmap.vim","4":"htmlmap.vim","src_id":"1689","5":"1689","creation_date":"1044189284","6":"1044189284"},{"0":"258","vim_version":"6.0","1":"6.0","script_version":"1.01pl3","2":"1.01pl3","version_comment":" - Bugfix for some rare Cyrillic characters\r\n - Bugfix for circumflex-accented o and O\r\n - Improvement: Added map for non-breaking space (but commented-out by default)\r\n - Cosmetic improvement: Release history added.","3":" - Bugfix for some rare Cyrillic characters\r\n - Bugfix for circumflex-accented o and O\r\n - Improvement: Added map for non-breaking space (but commented-out by default)\r\n - Cosmetic improvement: Release history added.","package":"htmlmap.vim","4":"htmlmap.vim","src_id":"1336","5":"1336","creation_date":"1035469521","6":"1035469521"},{"0":"258","vim_version":"6.0","1":"6.0","script_version":"1.01pl1","2":"1.01pl1","version_comment":"Bugfix for Cyrillic uppercase  io, dje, gje and Ukrainian ie (was 1024-1027, should be 1025-1028)","3":"Bugfix for Cyrillic uppercase  io, dje, gje and Ukrainian ie (was 1024-1027, should be 1025-1028)","package":"htmlmap.vim","4":"htmlmap.vim","src_id":"737","5":"737","creation_date":"1017537654","6":"1017537654"},{"0":"258","vim_version":"6.0","1":"6.0","script_version":"1.01","2":"1.01","version_comment":"bugfix = incorrect output for <F12>B= ; <F12>V= not recognized (Cyrillic uppercase B and V)","3":"bugfix = incorrect output for <F12>B= ; <F12>V= not recognized (Cyrillic uppercase B and V)","package":"htmlmap.vim","4":"htmlmap.vim","src_id":"734","5":"734","creation_date":"1017497216","6":"1017497216"},{"0":"258","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"htmlmap.vim","4":"htmlmap.vim","src_id":"727","5":"727","creation_date":"1017372063","6":"1017372063"}]},"257":{"script_id":"257","0":"257","script_name":"XSLT syntax","1":"XSLT syntax","script_type":"syntax","2":"syntax","summary":"Syntax for XSLT (with HTML and others)","3":"Syntax for XSLT (with HTML and others)","description":"Syntax highlighting for XSLT with HTML keywords.\r\n                                               \r\ncontaining keywords\r\n- HTML\r\n- CSS (use syntax\/css.vim)\r\n- JavaScript (use syntax\/javascript.vim)\r\n- VBScript (use syntax\/vb.vim)\r\n- PerlScript (use syntax\/perl.vim)","4":"Syntax highlighting for XSLT with HTML keywords.\r\n                                               \r\ncontaining keywords\r\n- HTML\r\n- CSS (use syntax\/css.vim)\r\n- JavaScript (use syntax\/javascript.vim)\r\n- VBScript (use syntax\/vb.vim)\r\n- PerlScript (use syntax\/perl.vim)","install_details":"","5":"","first_name":"atsushi","6":"atsushi","last_name":"moriki","7":"moriki","releases":[{"0":"257","vim_version":"6.0","1":"6.0","script_version":"0.3.11","2":"0.3.11","version_comment":"Bug fix (CSS keyword)","3":"Bug fix (CSS keyword)","package":"xsl.vim","4":"xsl.vim","src_id":"2092","5":"2092","creation_date":"1055882867","6":"1055882867"},{"0":"257","vim_version":"6.0","1":"6.0","script_version":"0.3.10","2":"0.3.10","version_comment":"Keywords other than XSLT were chosen.","3":"Keywords other than XSLT were chosen.","package":"xsl.vim","4":"xsl.vim","src_id":"897","5":"897","creation_date":"1022720849","6":"1022720849"},{"0":"257","vim_version":"6.0","1":"6.0","script_version":"0.3.04","2":"0.3.04","version_comment":"Initial upload","3":"Initial upload","package":"xsl.vim","4":"xsl.vim","src_id":"726","5":"726","creation_date":"1017365854","6":"1017365854"}]},"256":{"script_id":"256","0":"256","script_name":"pascii","1":"pascii","script_type":"utility","2":"utility","summary":"Ascii table printing","3":"Ascii table printing","description":"This package prints ascii table into a new buffer. ","4":"This package prints ascii table into a new buffer. ","install_details":"","5":"","first_name":"Lubos","6":"Lubos","last_name":"Celko","7":"Celko","releases":[{"0":"256","vim_version":"6.0","1":"6.0","script_version":"1.3","2":"1.3","version_comment":"Updated by Bill McCarthy","3":"Updated by Bill McCarthy","package":"pascii.vim","4":"pascii.vim","src_id":"4501","5":"4501","creation_date":"1124408760","6":"1124408760"},{"0":"256","vim_version":"6.0","1":"6.0","script_version":"1.2","2":"1.2","version_comment":"Initial upload","3":"Initial upload","package":"pascii.vim","4":"pascii.vim","src_id":"723","5":"723","creation_date":"1017269133","6":"1017269133"}]},"255":{"script_id":"255","0":"255","script_name":"ihtml.vim","1":"ihtml.vim","script_type":"syntax","2":"syntax","summary":"iHTML syntax highlighting","3":"iHTML syntax highlighting","description":"Does \"smart\" highlighting of all iHTML syntax.  Handles up to iHTML Enterprise Edition 2.20.  Also highlights SQL within SQL= attributes (which you can turn off if you'd like).  If you're using foldmethod=syntax, there are some nice folds setup by this syntax file.\r\n\r\nLatest version always available here:\r\nhttp:\/\/www.markfeeney.com\/resources\/ihtml.vim","4":"Does \"smart\" highlighting of all iHTML syntax.  Handles up to iHTML Enterprise Edition 2.20.  Also highlights SQL within SQL= attributes (which you can turn off if you'd like).  If you're using foldmethod=syntax, there are some nice folds setup by this syntax file.\r\n\r\nLatest version always available here:\r\nhttp:\/\/www.markfeeney.com\/resources\/ihtml.vim","install_details":"Drop the file in ~\/.vim\/syntax or on win32 in c:\\vim\\vimfiles\\syntax (assuming you're using drive c).  Setup some autocommands to load ihtml.vim for files ending with ihtml or iht.  Another better strategy is to load the syntax file for any files containing <!iHTML> in the first 2 or three lines of the file.","5":"Drop the file in ~\/.vim\/syntax or on win32 in c:\\vim\\vimfiles\\syntax (assuming you're using drive c).  Setup some autocommands to load ihtml.vim for files ending with ihtml or iht.  Another better strategy is to load the syntax file for any files containing <!iHTML> in the first 2 or three lines of the file.","first_name":"Mark","6":"Mark","last_name":"Feeney","7":"Feeney","releases":[{"0":"255","vim_version":"6.0","1":"6.0","script_version":"1.4","2":"1.4","version_comment":"Was missing a few end tags in the last veresion.  Also, a few environment variables were messed up and\/or missing.","3":"Was missing a few end tags in the last veresion.  Also, a few environment variables were messed up and\/or missing.","package":"ihtml.vim","4":"ihtml.vim","src_id":"764","5":"764","creation_date":"1018010877","6":"1018010877"},{"0":"255","vim_version":"6.0","1":"6.0","script_version":"1.2","2":"1.2","version_comment":"Initial upload","3":"Initial upload","package":"ihtml.vim","4":"ihtml.vim","src_id":"721","5":"721","creation_date":"1017218344","6":"1017218344"}]},"254":{"script_id":"254","0":"254","script_name":"tmpl.vim","1":"tmpl.vim","script_type":"syntax","2":"syntax","summary":"Syntax for HTML-Template","3":"Syntax for HTML-Template","description":"Syntax highlignting for HTML containing HTML-Template tag(<TMPL_XXX .. >).\r\nIt uses $VIMRUNTIME\/syntax\/html.vim.\r\n","4":"Syntax highlignting for HTML containing HTML-Template tag(<TMPL_XXX .. >).\r\nIt uses $VIMRUNTIME\/syntax\/html.vim.\r\n","install_details":"","5":"","first_name":"atsushi","6":"atsushi","last_name":"moriki","7":"moriki","releases":[{"0":"254","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"tmpl.vim","4":"tmpl.vim","src_id":"714","5":"714","creation_date":"1017105771","6":"1017105771"}]},"253":{"script_id":"253","0":"253","script_name":"midnight.vim","1":"midnight.vim","script_type":"color scheme","2":"color scheme","summary":"Dark blue, low contrast colorscheme.","3":"Dark blue, low contrast colorscheme.","description":"Midnight is a colorscheme with a dark blue background and light blue foreground.  It is designed to keep contrast at a minimum.  It is the same as midnight2.vim (vimscript #424).  I will attempt to keep both up to date with the same version of the colorscheme.","4":"Midnight is a colorscheme with a dark blue background and light blue foreground.  It is designed to keep contrast at a minimum.  It is the same as midnight2.vim (vimscript #424).  I will attempt to keep both up to date with the same version of the colorscheme.","install_details":"Download and place in ~\/.vim\/colors.  Then type \":color midnight\".  I also highly recommend you place \"color midnight\" in your ~\/.vimrc.  :)","5":"Download and place in ~\/.vim\/colors.  Then type \":color midnight\".  I also highly recommend you place \"color midnight\" in your ~\/.vimrc.  :)","first_name":"Michael","6":"Michael","last_name":"Brailsford","7":"Brailsford","releases":[{"0":"253","vim_version":"7.0","1":"7.0","script_version":"2.5","2":"2.5","version_comment":"Major update to the midnight colorscheme.  This version features much subdued colors.  The background is much darker.  The contrast has been dialed way back.  This version adds updates for vim7 and vimdiff.  This is the same as version 2.5 of midnight2.","3":"Major update to the midnight colorscheme.  This version features much subdued colors.  The background is much darker.  The contrast has been dialed way back.  This version adds updates for vim7 and vimdiff.  This is the same as version 2.5 of midnight2.","package":"midnight.vim","4":"midnight.vim","src_id":"6503","5":"6503","creation_date":"1165303739","6":"1165303739"},{"0":"253","vim_version":"6.0","1":"6.0","script_version":"1.4","2":"1.4","version_comment":"Made the semicolon toggle mapping more intuitive.  Now it is mapped to <leader>;, instead of <leader>sc.\r\n","3":"Made the semicolon toggle mapping more intuitive.  Now it is mapped to <leader>;, instead of <leader>sc.\r\n","package":"midnight.vim","4":"midnight.vim","src_id":"780","5":"780","creation_date":"1018470882","6":"1018470882"},{"0":"253","vim_version":"6.0","1":"6.0","script_version":"1.3","2":"1.3","version_comment":"Made the colorscheme more complete.  Now the status line is highlighted differently for the current buffer, and I changed a few other highlighting this to round out the colorscheme.  Also added a function to toggle the semicolon highlighting feature off and on with an nmap.  Very handy for c\/c++, java, etc...","3":"Made the colorscheme more complete.  Now the status line is highlighted differently for the current buffer, and I changed a few other highlighting this to round out the colorscheme.  Also added a function to toggle the semicolon highlighting feature off and on with an nmap.  Very handy for c\/c++, java, etc...","package":"midnight.vim","4":"midnight.vim","src_id":"770","5":"770","creation_date":"1018123739","6":"1018123739"},{"0":"253","vim_version":"6.0","1":"6.0","script_version":"1.2","2":"1.2","version_comment":"Removed the semicolon highlighting at the end of lines.  It didn't work right anyway.","3":"Removed the semicolon highlighting at the end of lines.  It didn't work right anyway.","package":"midnight.vim","4":"midnight.vim","src_id":"739","5":"739","creation_date":"1017609369","6":"1017609369"},{"0":"253","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"midnight.vim","4":"midnight.vim","src_id":"713","5":"713","creation_date":"1017086271","6":"1017086271"}]},"252":{"script_id":"252","0":"252","script_name":"UserMenu.vim","1":"UserMenu.vim","script_type":"utility","2":"utility","summary":"(gvim) Menu for inserting longer pieces of text","3":"(gvim) Menu for inserting longer pieces of text","description":"\" For gvim.\r\n\" Registers are good for executing vim commands but not perfect for inserting\r\n\" longer parts of normal text. This menu for gvim help you easy creating,\r\n\" saving end editing eg. headers for various .tex and .html files.","4":"\" For gvim.\r\n\" Registers are good for executing vim commands but not perfect for inserting\r\n\" longer parts of normal text. This menu for gvim help you easy creating,\r\n\" saving end editing eg. headers for various .tex and .html files.","install_details":"\" Installation:\r\n\" NOTE: libList.vim is necessary. It is great library for handling lists.\r\n\" http:\/\/vim.sourceforge.net\/scripts\/script.php?script_id=166\r\n\"\r\n\" 1. Simplest way is to put this file into your plugin directory or source it\r\n\" from vimrc (or gvimrc) file.\r\n\" 2. Also you need create special directories where\r\n\" your texts will be stored. In default configuration it is:\r\n\" $HOME\/.vim\/usermenu\/ (for unices).\r\n\" 3. Configuration:\r\n\" Path to libList.vim . It isn't necessary when libList.vim is in your plugin\r\n\" directory.\r\nsource $HOME\/.vim\/scripts\/libList.vim\r\n\r\n\" Path to usermenu (for unices)\r\nlet s:path = \"$HOME\/.vim\/usermenu\/\"\r\n\r\n\" Name of the folder with `macros'\r\nlet s:localpath = \"usermenu\"\r\n\r\n\" Action. Default is read, but maybe you want to change that (eg. source).\r\nlet s:action = \"read\"","5":"\" Installation:\r\n\" NOTE: libList.vim is necessary. It is great library for handling lists.\r\n\" http:\/\/vim.sourceforge.net\/scripts\/script.php?script_id=166\r\n\"\r\n\" 1. Simplest way is to put this file into your plugin directory or source it\r\n\" from vimrc (or gvimrc) file.\r\n\" 2. Also you need create special directories where\r\n\" your texts will be stored. In default configuration it is:\r\n\" $HOME\/.vim\/usermenu\/ (for unices).\r\n\" 3. Configuration:\r\n\" Path to libList.vim . It isn't necessary when libList.vim is in your plugin\r\n\" directory.\r\nsource $HOME\/.vim\/scripts\/libList.vim\r\n\r\n\" Path to usermenu (for unices)\r\nlet s:path = \"$HOME\/.vim\/usermenu\/\"\r\n\r\n\" Name of the folder with `macros'\r\nlet s:localpath = \"usermenu\"\r\n\r\n\" Action. Default is read, but maybe you want to change that (eg. source).\r\nlet s:action = \"read\"","first_name":"Mikolaj","6":"Mikolaj","last_name":"Machowski","7":"Machowski","releases":[{"0":"252","vim_version":"6.0","1":"6.0","script_version":"0.5","2":"0.5","version_comment":"Cleaning of the code, better cross-system behaviour.","3":"Cleaning of the code, better cross-system behaviour.","package":"usermenu.vim","4":"usermenu.vim","src_id":"1252","5":"1252","creation_date":"1033134197","6":"1033134197"},{"0":"252","vim_version":"6.0","1":"6.0","script_version":"0.2","2":"0.2","version_comment":"MSWindows compability added","3":"MSWindows compability added","package":"usermenu.vim","4":"usermenu.vim","src_id":"846","5":"846","creation_date":"1020679157","6":"1020679157"},{"0":"252","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"usermenu.vim","4":"usermenu.vim","src_id":"711","5":"711","creation_date":"1017057574","6":"1017057574"}]},"251":{"script_id":"251","0":"251","script_name":"lid.vim","1":"lid.vim","script_type":"utility","2":"utility","summary":"Plugin to integrate GNU id-utils tool with Vim","3":"Plugin to integrate GNU id-utils tool with Vim","description":"Overview\r\n\r\nThe lid plugin integrates the GNU id-utils lid tool with Vim to lookup\r\nkeywords in the ID database.\r\n\r\nFor more information about id utilities (lid, aid, etc), visit the \r\nfollowing pages: \r\n\r\n    http:\/\/www.gnu.org\/software\/idutils\/idutils.html \r\n    http:\/\/www.delorie.com\/gnu\/docs\/id-utils\/id-utils_toc.html \r\n\r\nYou can download the id-utils binaries for MS-Windows from: \r\n\r\n    http:\/\/gnuwin32.sourceforge.net\/packages\/id-utils.htm\r\n\r\nThe github repository for this plugin is at http:\/\/github.com\/yegappan\/lid\r\n\r\nUsage\r\n\r\nThe lid plugin introduces two Vim commands to lookup keywords in the ID\r\ndatabase.\r\n\r\n      :Lid [ <keyword> ]\r\n      :Aid [ <keyword> ]\r\n\r\nYou can lookup keywords in the ID database using the 'Lid' command. For\r\nexample,\r\n\r\n      :Lid<Enter> \r\n\r\nThis command will prompt you for the keyword to lookup.  The default is the\r\ncurrent keyword under the cursor.  You can retrieve previously entered\r\nkeywords using the up and down arrow keys. You can cancel the lookup by\r\npressing the escape key.\r\n\r\nYou can map a key to invoke the Lid command:\r\n\r\n      nnoremap <silent> <F4> :Lid <C-R><C-W><CR>\r\n\r\nAdd the above mapping to your ~\/.vimrc file.\r\n\r\nYou can also specify the keyword to the Lid command like this:\r\n\r\n      :Lid <keyword>\r\n\r\nIn the above command format, you can press the <Tab> key to expand\r\nkeywords from a tags file.\r\n\r\nYou can use the \"-g\" and \"-x\" option to the 'Lid' command to selectively\r\ndisplay lines from the lid output. You can use the \"-g\" option to the 'Lid'\r\ncommand to list only those lid matches that contain a Vim pattern. You can\r\nuse the \"-x\" option to the 'Lid' command to list only those lid matches that\r\ndoes not contain a Vim pattern.\r\n\r\n       :Lid -g\r\n       :Lid -x\r\n\r\nIf you use the any one of the above options, you will prompted to enter the\r\npattern you are interested in.\r\n\r\nYou can specify additional command-line options accepted by the lid utility\r\nto the above commands.  For example, to perform a case-insensitive search,\r\nyou can use the following command:\r\n\r\n      :Lid -i\r\n\r\nYou can use the \":Aid\" command to list all the matching keywords in the\r\nID database that has the specified literal pattern:\r\n\r\n      :Aid <keyword>\r\n\r\nAll the above description about the :Lid command also applies to the\r\n:Aid command.\r\n\r\nThe output of the lid command will be listed in the Vim quickfix window.\r\n1. You can select a line in the quickfix window and press <Enter> or double\r\n   click on a match to jump to that line.\r\n2. You can use the \":cnext\" and \":cprev\" commands to the jump to the next or\r\n   previous output line.\r\n3. You can use the \":colder\" and \":cnewer\" commands to go between multiple\r\n   Lid quickfix output windows.\r\n4. The quickfix window need not be opened always to use the lid output.\r\n   You can close the quickfix window and use the quickfix commands to jump\r\n   to the lid matches.  Use the \":copen\" command to open the quickfix\r\n   window again.\r\n\r\nFor more information about other quickfix commands read \":help quickfix\"\r\n\r\nConfiguration\r\n\r\nBy changing the following variables you can configure the behavior of this\r\nplugin. Set the following variables in your .vimrc file using the 'let'\r\ncommand.\r\n\r\nThe path to the lid executable is specified by the 'LID_Cmd' variable.  By\r\ndefault, this variable is set to lid. You can change the lid executable path\r\nby setting the 'LID_Cmd' variable:\r\n\r\n      let LID_Cmd = '\/my\/path\/lid'\r\n\r\nBy default, this plugin uses 'ID' as the name of the database.  This is\r\ndefined by the 'LID_File' variable.  You can change the name\/location of the\r\nID database by setting the 'LID_File' variable:\r\n\r\n      let LID_File = '\/my\/path\/ID'\r\n\r\nYou can also specify more than one ID file names in the LID_File variable.\r\nThe ID file names should be separated by a ',' character.\r\n\r\n      let LID_File = '\/my\/path1\/ID,\/my\/path2\/ID,\/my\/path3\/ID'\r\n\r\nThe plugin will use the first ID file name and run lid using that filename.\r\nIf a match is found, it will return the results. If a match is not found,\r\nthen the second ID file name will be used and this will be repeated till\r\neither a match is found or all the specified ID file names are processed.\r\n\r\nIf more than one ID file is specified using the 'LID_File' variable, you can\r\nset the 'LID_Search_Multiple_ID_Files' variable to 1 to always search for a\r\nkeyword in all the specified ID files. By default,\r\n'LID_Search_Multiple_ID_Files' variable is set to one. All the specified ID\r\nfiles are searched for the keyword. \r\n\r\n      let LID_Search_Multiple_ID_Files = 0\r\n\r\nBy default, when you invoke the :Lid command the quickfix window will be\r\nopened with the lid output.  You can disable opening the quickfix window,\r\nby setting the 'LID_OpenQuickfixWindow' variable to 1:\r\n\r\n      let LID_OpenQuickfixWindow = 1\r\n\r\nYou can manually open the quickfix window using the :cwindow command.\r\n\r\nThe 'LID_Shell_Quote_Char' variable specifies the character to use to\r\nescape the keyword before passing it to the lid command.  By default,\r\nfor MS-Windows systems, no shell quote character is set.  For other\r\nsystems, \"'\" is used as the the shell quote character.  You can change\r\nthis by setting the 'LID_Shell_Quote_Char' variable:\r\n\r\n      let LID_Shell_Quote_Char = '\"'\r\n\r\nBy default, the ID file specified by the LID_File variable will be used.  If\r\nyou set the 'LID_Prompt_ID_Filename' variable to 1, then every time the LID\r\ncommand will prompt for the location of the ID file.  The default ID file\r\nlocation displayed will be the last used value.  You can again set the\r\n'LID_Prompt_ID_Filename' variable back to 0, to turn off this prompt.  The\r\nlast supplied ID file will be used for further Lid invocations.\r\n\r\n      let LID_Prompt_ID_Filename = 1\r\n\r\nBy default, when the lid output is displayed, the cursor will be\r\nautomatically positioned at the first matching line.  You can set the\r\nLID_Jump_To_Match variable to 0 to prevent this.  In this case, only the\r\noutput from LID will be displayed.\r\n\r\n      let LID_Jump_To_Match = 0\r\n\r\nBy default, the lid search results are added to the global quickfix list.\r\nIf you like to use the per-window location list for the results, then you\r\ncan set the LID_Use_Location_List variable to 1:\r\n\r\n      let LID_Use_Location_List = 1\r\n\r\nThe location list feature is supported only in Vim version 7.0 and later\r\nversions. If the location list is used, then you have to use the location\r\nlist commands to browse the results.","4":"Overview\r\n\r\nThe lid plugin integrates the GNU id-utils lid tool with Vim to lookup\r\nkeywords in the ID database.\r\n\r\nFor more information about id utilities (lid, aid, etc), visit the \r\nfollowing pages: \r\n\r\n    http:\/\/www.gnu.org\/software\/idutils\/idutils.html \r\n    http:\/\/www.delorie.com\/gnu\/docs\/id-utils\/id-utils_toc.html \r\n\r\nYou can download the id-utils binaries for MS-Windows from: \r\n\r\n    http:\/\/gnuwin32.sourceforge.net\/packages\/id-utils.htm\r\n\r\nThe github repository for this plugin is at http:\/\/github.com\/yegappan\/lid\r\n\r\nUsage\r\n\r\nThe lid plugin introduces two Vim commands to lookup keywords in the ID\r\ndatabase.\r\n\r\n      :Lid [ <keyword> ]\r\n      :Aid [ <keyword> ]\r\n\r\nYou can lookup keywords in the ID database using the 'Lid' command. For\r\nexample,\r\n\r\n      :Lid<Enter> \r\n\r\nThis command will prompt you for the keyword to lookup.  The default is the\r\ncurrent keyword under the cursor.  You can retrieve previously entered\r\nkeywords using the up and down arrow keys. You can cancel the lookup by\r\npressing the escape key.\r\n\r\nYou can map a key to invoke the Lid command:\r\n\r\n      nnoremap <silent> <F4> :Lid <C-R><C-W><CR>\r\n\r\nAdd the above mapping to your ~\/.vimrc file.\r\n\r\nYou can also specify the keyword to the Lid command like this:\r\n\r\n      :Lid <keyword>\r\n\r\nIn the above command format, you can press the <Tab> key to expand\r\nkeywords from a tags file.\r\n\r\nYou can use the \"-g\" and \"-x\" option to the 'Lid' command to selectively\r\ndisplay lines from the lid output. You can use the \"-g\" option to the 'Lid'\r\ncommand to list only those lid matches that contain a Vim pattern. You can\r\nuse the \"-x\" option to the 'Lid' command to list only those lid matches that\r\ndoes not contain a Vim pattern.\r\n\r\n       :Lid -g\r\n       :Lid -x\r\n\r\nIf you use the any one of the above options, you will prompted to enter the\r\npattern you are interested in.\r\n\r\nYou can specify additional command-line options accepted by the lid utility\r\nto the above commands.  For example, to perform a case-insensitive search,\r\nyou can use the following command:\r\n\r\n      :Lid -i\r\n\r\nYou can use the \":Aid\" command to list all the matching keywords in the\r\nID database that has the specified literal pattern:\r\n\r\n      :Aid <keyword>\r\n\r\nAll the above description about the :Lid command also applies to the\r\n:Aid command.\r\n\r\nThe output of the lid command will be listed in the Vim quickfix window.\r\n1. You can select a line in the quickfix window and press <Enter> or double\r\n   click on a match to jump to that line.\r\n2. You can use the \":cnext\" and \":cprev\" commands to the jump to the next or\r\n   previous output line.\r\n3. You can use the \":colder\" and \":cnewer\" commands to go between multiple\r\n   Lid quickfix output windows.\r\n4. The quickfix window need not be opened always to use the lid output.\r\n   You can close the quickfix window and use the quickfix commands to jump\r\n   to the lid matches.  Use the \":copen\" command to open the quickfix\r\n   window again.\r\n\r\nFor more information about other quickfix commands read \":help quickfix\"\r\n\r\nConfiguration\r\n\r\nBy changing the following variables you can configure the behavior of this\r\nplugin. Set the following variables in your .vimrc file using the 'let'\r\ncommand.\r\n\r\nThe path to the lid executable is specified by the 'LID_Cmd' variable.  By\r\ndefault, this variable is set to lid. You can change the lid executable path\r\nby setting the 'LID_Cmd' variable:\r\n\r\n      let LID_Cmd = '\/my\/path\/lid'\r\n\r\nBy default, this plugin uses 'ID' as the name of the database.  This is\r\ndefined by the 'LID_File' variable.  You can change the name\/location of the\r\nID database by setting the 'LID_File' variable:\r\n\r\n      let LID_File = '\/my\/path\/ID'\r\n\r\nYou can also specify more than one ID file names in the LID_File variable.\r\nThe ID file names should be separated by a ',' character.\r\n\r\n      let LID_File = '\/my\/path1\/ID,\/my\/path2\/ID,\/my\/path3\/ID'\r\n\r\nThe plugin will use the first ID file name and run lid using that filename.\r\nIf a match is found, it will return the results. If a match is not found,\r\nthen the second ID file name will be used and this will be repeated till\r\neither a match is found or all the specified ID file names are processed.\r\n\r\nIf more than one ID file is specified using the 'LID_File' variable, you can\r\nset the 'LID_Search_Multiple_ID_Files' variable to 1 to always search for a\r\nkeyword in all the specified ID files. By default,\r\n'LID_Search_Multiple_ID_Files' variable is set to one. All the specified ID\r\nfiles are searched for the keyword. \r\n\r\n      let LID_Search_Multiple_ID_Files = 0\r\n\r\nBy default, when you invoke the :Lid command the quickfix window will be\r\nopened with the lid output.  You can disable opening the quickfix window,\r\nby setting the 'LID_OpenQuickfixWindow' variable to 1:\r\n\r\n      let LID_OpenQuickfixWindow = 1\r\n\r\nYou can manually open the quickfix window using the :cwindow command.\r\n\r\nThe 'LID_Shell_Quote_Char' variable specifies the character to use to\r\nescape the keyword before passing it to the lid command.  By default,\r\nfor MS-Windows systems, no shell quote character is set.  For other\r\nsystems, \"'\" is used as the the shell quote character.  You can change\r\nthis by setting the 'LID_Shell_Quote_Char' variable:\r\n\r\n      let LID_Shell_Quote_Char = '\"'\r\n\r\nBy default, the ID file specified by the LID_File variable will be used.  If\r\nyou set the 'LID_Prompt_ID_Filename' variable to 1, then every time the LID\r\ncommand will prompt for the location of the ID file.  The default ID file\r\nlocation displayed will be the last used value.  You can again set the\r\n'LID_Prompt_ID_Filename' variable back to 0, to turn off this prompt.  The\r\nlast supplied ID file will be used for further Lid invocations.\r\n\r\n      let LID_Prompt_ID_Filename = 1\r\n\r\nBy default, when the lid output is displayed, the cursor will be\r\nautomatically positioned at the first matching line.  You can set the\r\nLID_Jump_To_Match variable to 0 to prevent this.  In this case, only the\r\noutput from LID will be displayed.\r\n\r\n      let LID_Jump_To_Match = 0\r\n\r\nBy default, the lid search results are added to the global quickfix list.\r\nIf you like to use the per-window location list for the results, then you\r\ncan set the LID_Use_Location_List variable to 1:\r\n\r\n      let LID_Use_Location_List = 1\r\n\r\nThe location list feature is supported only in Vim version 7.0 and later\r\nversions. If the location list is used, then you have to use the location\r\nlist commands to browse the results.","install_details":"1. Copy the lid.vim file to the $HOME\/.vim\/plugin or $HOME\/vimfiles\/plugin\r\n   or $VIM\/vimfiles\/plugin directory.\r\n   Refer to the following Vim help topics for more information about Vim\r\n   plugins:\r\n      :help add-plugin\r\n      :help add-global-plugin\r\n      :help runtimepath\r\n2. If the GNU lid utility is not already present in one of the directories\r\n   in the PATH environment variable, then set the LID_Cmd variable in the\r\n   .vimrc file to point to the GNU lid utility path.\r\n3. Restart Vim.\r\n4. You can now use the \":Lid\" command to search for a keyword.\r\n","5":"1. Copy the lid.vim file to the $HOME\/.vim\/plugin or $HOME\/vimfiles\/plugin\r\n   or $VIM\/vimfiles\/plugin directory.\r\n   Refer to the following Vim help topics for more information about Vim\r\n   plugins:\r\n      :help add-plugin\r\n      :help add-global-plugin\r\n      :help runtimepath\r\n2. If the GNU lid utility is not already present in one of the directories\r\n   in the PATH environment variable, then set the LID_Cmd variable in the\r\n   .vimrc file to point to the GNU lid utility path.\r\n3. Restart Vim.\r\n4. You can now use the \":Lid\" command to search for a keyword.\r\n","first_name":"Yegappan","6":"Yegappan","last_name":"Lakshmanan","7":"Lakshmanan","releases":[{"0":"251","vim_version":"6.0","1":"6.0","script_version":"2.5","2":"2.5","version_comment":"1. Introduced the Aid command to perform an approximate search for an identifier.\r\n2. Changed the -p option to -g and -v option to -x. These options are used to include and exclude lines matching a patttern from the output.\r\n3. Added option for using the location list instead of the quickfix list for the output.\r\n4. Optimized the functions that filter the output for a pattern.\r\n","3":"1. Introduced the Aid command to perform an approximate search for an identifier.\r\n2. Changed the -p option to -g and -v option to -x. These options are used to include and exclude lines matching a patttern from the output.\r\n3. Added option for using the location list instead of the quickfix list for the output.\r\n4. Optimized the functions that filter the output for a pattern.\r\n","package":"lid.vim","4":"lid.vim","src_id":"19685","5":"19685","creation_date":"1364002527","6":"1364002527"},{"0":"251","vim_version":"6.0","1":"6.0","script_version":"2.4","2":"2.4","version_comment":"Fixed a problem in searching multiple ID files when some of the ID files are not present.","3":"Fixed a problem in searching multiple ID files when some of the ID files are not present.","package":"lid.vim","4":"lid.vim","src_id":"2028","5":"2028","creation_date":"1054251232","6":"1054251232"},{"0":"251","vim_version":"6.0","1":"6.0","script_version":"2.3","2":"2.3","version_comment":"Added optional support for searching a keyword always in more than one ID file.","3":"Added optional support for searching a keyword always in more than one ID file.","package":"lid.vim","4":"lid.vim","src_id":"1221","5":"1221","creation_date":"1032375551","6":"1032375551"},{"0":"251","vim_version":"6.0","1":"6.0","script_version":"1.1","2":"1.1","version_comment":"Updated script comments.","3":"Updated script comments.","package":"gid.vim","4":"gid.vim","src_id":"733","5":"733","creation_date":"1017487559","6":"1017487559"}]},"250":{"script_id":"250","0":"250","script_name":"bnf.vim","1":"bnf.vim","script_type":"syntax","2":"syntax","summary":"Highlight BNFs","3":"Highlight BNFs","description":"Pretty straight forward.  It highlights a BNF grammar definition.  Not too fancy, but it makes writing a BNF more pleasant.  You can see a screenshot of bnf.vim at http:\/\/students.cs.byu.edu\/~mtb6\/bnf_vim.png .  For more complex BNF grammar definitions, you may want to check out http:\/\/vim.sourceforge.net\/script.php?script_id=545 which is an EBNF syntax file by Hans Fugal.","4":"Pretty straight forward.  It highlights a BNF grammar definition.  Not too fancy, but it makes writing a BNF more pleasant.  You can see a screenshot of bnf.vim at http:\/\/students.cs.byu.edu\/~mtb6\/bnf_vim.png .  For more complex BNF grammar definitions, you may want to check out http:\/\/vim.sourceforge.net\/script.php?script_id=545 which is an EBNF syntax file by Hans Fugal.","install_details":"Just put it in your ~\/.vim\/syntax directory and add an autocommand to load it up on all files ending with .bnf.  Something like \"au bufreadpre,bufnewfile *.bnf set ft=bnf\" will do nicely.","5":"Just put it in your ~\/.vim\/syntax directory and add an autocommand to load it up on all files ending with .bnf.  Something like \"au bufreadpre,bufnewfile *.bnf set ft=bnf\" will do nicely.","first_name":"Michael","6":"Michael","last_name":"Brailsford","7":"Brailsford","releases":[{"0":"250","vim_version":"6.0","1":"6.0","script_version":"1.2","2":"1.2","version_comment":"I forgot to add the proper syntax file starting stuff.  This adds it.","3":"I forgot to add the proper syntax file starting stuff.  This adds it.","package":"bnf.vim","4":"bnf.vim","src_id":"712","5":"712","creation_date":"1017085851","6":"1017085851"},{"0":"250","vim_version":"6.0","1":"6.0","script_version":"1.1","2":"1.1","version_comment":"fixed a bug that did not quote string properly if they had the comment char '#' in the quoted string.","3":"fixed a bug that did not quote string properly if they had the comment char '#' in the quoted string.","package":"bnf.vim","4":"bnf.vim","src_id":"707","5":"707","creation_date":"1016828034","6":"1016828034"},{"0":"250","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"bnf.vim","4":"bnf.vim","src_id":"706","5":"706","creation_date":"1016820678","6":"1016820678"}]},"249":{"script_id":"249","0":"249","script_name":"update_vim","1":"update_vim","script_type":"utility","2":"utility","summary":"Shell script for updating(patching) vim 6.1","3":"Shell script for updating(patching) vim 6.1","description":"This script download all new patches for vim (currently 6.1.x), patch sources, recompile it and install new version of vim.","4":"This script download all new patches for vim (currently 6.1.x), patch sources, recompile it and install new version of vim.","install_details":"Please check my homepage \r\nhttp:\/\/pauli.fmph.uniba.sk\/~8host\/vim\/scripts\/zshrc for actual version.\r\n\r\nSource this script with your shell ( I'm using zsh but bash may be also good). Call function update-vim-zsh() and your vim will be updated.\r\n\r\nYou need unpacked sources and directory with patches.\r\n\r\nYou must customize this script for you. Vim sources must be already unpacked. You need also vim-6.1-extra.tar.gz and vim-6.1-lang.tar.gz package.\r\n","5":"Please check my homepage \r\nhttp:\/\/pauli.fmph.uniba.sk\/~8host\/vim\/scripts\/zshrc for actual version.\r\n\r\nSource this script with your shell ( I'm using zsh but bash may be also good). Call function update-vim-zsh() and your vim will be updated.\r\n\r\nYou need unpacked sources and directory with patches.\r\n\r\nYou must customize this script for you. Vim sources must be already unpacked. You need also vim-6.1-extra.tar.gz and vim-6.1-lang.tar.gz package.\r\n","first_name":"\u013dubom\u00c3\u00adr","6":"Ľubom\u00c3\u00adr","last_name":"Host","7":"Host","releases":[{"0":"249","vim_version":"6.0","1":"6.0","script_version":"1.3","2":"1.3","version_comment":"Improvements for vim version 6.1.","3":"Improvements for vim version 6.1.","package":"zshrc","4":"zshrc","src_id":"750","5":"750","creation_date":"1017830776","6":"1017830776"},{"0":"249","vim_version":"6.0","1":"6.0","script_version":"1.2","2":"1.2","version_comment":"Initial upload","3":"Initial upload","package":"zshrc","4":"zshrc","src_id":"697","5":"697","creation_date":"1016536414","6":"1016536414"}]},"248":{"script_id":"248","0":"248","script_name":"vimRubyX","1":"vimRubyX","script_type":"utility","2":"utility","summary":"enhancements to vim ruby interface","3":"enhancements to vim ruby interface","description":"Enhancements to the VIM-Ruby interface.\r\nThis allows you to easily define and call vim functions from ruby.\r\nCalling is done as if all the vim user defined and built in functions were\r\nmethods on the VIM module\r\nDefining is done by adding a new method to the VIM module.","4":"Enhancements to the VIM-Ruby interface.\r\nThis allows you to easily define and call vim functions from ruby.\r\nCalling is done as if all the vim user defined and built in functions were\r\nmethods on the VIM module\r\nDefining is done by adding a new method to the VIM module.","install_details":"The vimRubyX plugin is actually a ruby module. But since it is only usefull\r\nfrom vim and for more convenience it is packaged as a vim plugin. To install\r\nit just unzip the package in a directory in your runtime view and run\r\n|:helptags| on the appropriate doc directory.","5":"The vimRubyX plugin is actually a ruby module. But since it is only usefull\r\nfrom vim and for more convenience it is packaged as a vim plugin. To install\r\nit just unzip the package in a directory in your runtime view and run\r\n|:helptags| on the appropriate doc directory.","first_name":"Benoit","6":"Benoit","last_name":"Cerrina","7":"Cerrina","releases":[{"0":"248","vim_version":"6.0","1":"6.0","script_version":"1.3","2":"1.3","version_comment":"exit more graciously if vim is not ruby enabled (no ruby support compiled in or dynamic ruby and ruby lib not found)","3":"exit more graciously if vim is not ruby enabled (no ruby support compiled in or dynamic ruby and ruby lib not found)","package":"vimRubyX.zip","4":"vimRubyX.zip","src_id":"2813","5":"2813","creation_date":"1078696657","6":"1078696657"},{"0":"248","vim_version":"6.0","1":"6.0","script_version":"1.2","2":"1.2","version_comment":"better exception handling in EvalRb","3":"better exception handling in EvalRb","package":"Vimrubyx.zip","4":"Vimrubyx.zip","src_id":"778","5":"778","creation_date":"1018435297","6":"1018435297"},{"0":"248","vim_version":"6.0","1":"6.0","script_version":"1.1","2":"1.1","version_comment":"added interactive ruby evaluation and enhanced vim ex-command support from within ruby","3":"added interactive ruby evaluation and enhanced vim ex-command support from within ruby","package":"vimRubyX.zip","4":"vimRubyX.zip","src_id":"771","5":"771","creation_date":"1018143869","6":"1018143869"},{"0":"248","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"vimRubyX.zip","4":"vimRubyX.zip","src_id":"692","5":"692","creation_date":"1016461399","6":"1016461399"}]},"247":{"script_id":"247","0":"247","script_name":"cream-ascii","1":"cream-ascii","script_type":"utility","2":"utility","summary":"Insert an ASCII character from a dialog box","3":"Insert an ASCII character from a dialog box","description":"\r\nInsert an ASCII character from a dialog box. See the screenshot at http:\/\/cream.sourceforge.net\/screenshot-ascii.png.\r\n\r\nThis is one of many custom utilities and functions for gVim from the Cream project (http:\/\/cream.sourceforge.net), a configuration of Vim for those of us familiar with Apple and Windows software. \r\n\r\n","4":"\r\nInsert an ASCII character from a dialog box. See the screenshot at http:\/\/cream.sourceforge.net\/screenshot-ascii.png.\r\n\r\nThis is one of many custom utilities and functions for gVim from the Cream project (http:\/\/cream.sourceforge.net), a configuration of Vim for those of us familiar with Apple and Windows software. \r\n\r\n","install_details":"Just copy this file and paste it into your vimrc. Or you can drop the entire file into your plugins directory.\r\n\r\nTwo cream ASCII menu items attempt to load into the bottom of the default Tools menu. (If you have customized your menus and Tools has been removed or altered, this could fail, obviously.)\r\n\r\nIf you choose not to use the menus, you can also call the Cream_ascii() function directly from the command line. Options are as follows:\r\n\r\n  :call Cream_ascii()  -- No argument inserts a complete ASCII table into the current document\r\n\r\n  :call Cream_ascii(\"dialog\")  -- The argument \"dialog\" calls the dialog version of the program\r\n\r\n  :call Cream_ascii([32-255])  -- You can also use a number 32-255 to insert that decimal character with Vim's nr2char()\r\n\r\n","5":"Just copy this file and paste it into your vimrc. Or you can drop the entire file into your plugins directory.\r\n\r\nTwo cream ASCII menu items attempt to load into the bottom of the default Tools menu. (If you have customized your menus and Tools has been removed or altered, this could fail, obviously.)\r\n\r\nIf you choose not to use the menus, you can also call the Cream_ascii() function directly from the command line. Options are as follows:\r\n\r\n  :call Cream_ascii()  -- No argument inserts a complete ASCII table into the current document\r\n\r\n  :call Cream_ascii(\"dialog\")  -- The argument \"dialog\" calls the dialog version of the program\r\n\r\n  :call Cream_ascii([32-255])  -- You can also use a number 32-255 to insert that decimal character with Vim's nr2char()\r\n\r\n","first_name":"Steve","6":"Steve","last_name":"Hall","7":"Hall","releases":[{"0":"247","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"cream-ascii.vim","4":"cream-ascii.vim","src_id":"686","5":"686","creation_date":"1016287909","6":"1016287909"}]},"246":{"script_id":"246","0":"246","script_name":"Buffer Menus","1":"Buffer Menus","script_type":"utility","2":"utility","summary":"Add menus for the current buffer only.","3":"Add menus for the current buffer only.","description":"Adds menus for the current buffer.   When you leave the buffer, they get removed, and when you go back in, they are added again.\r\nIt cannot be used effectively to replace a menu as it is not possible to find out what the mapping used to be (as for map commands), and therefore not possible to restore it (*sigh*)\r\n\r\nThis is taken from my 'buffoptions' script, and should be useful in enabling menus to be added to ftplugin scripts.\r\n\r\nNOTE: When adding to ftplugin scripts make VERY sure that the menus only get added ONCE (reinclude protection is good here).\r\n\r\nTODO: (Please email me to add to this list)\r\n- Allow 'Unmenu' of individual menus\r\n\r\n\r\nUsage -\r\n:Bmenu[!] [\"<silent>\"] [\"<unmenu>\"|\"<disable>\"] [<modes>] [<priority>] <Menuname> <Mapping>\r\n \t\tAdd menus to different modes for the current buffer.  (Bang is used to\r\n        specify 'noremenu')\r\n:B[ivacn]menu[!][\"<silent>\"] [\"<unmenu>\"|\"<disable>\"]  [<priority>] <Menuname> <Mapping>\r\n\t    Add menu for one mode (or 'a' for all modes) for the current buffer.\r\n      (Bang is used to specify 'noremenu')\r\n\r\nB[ivacn]noremenu [\"<silent>\"] [\"<unmenu>\"|\"<disable>\"] [<modes>] [<priority>] <Menuname> <Mapping>\r\n      Adds a 'norecursive' menu.\r\n\r\nThe above commands accept '<silent>' as a flag to do a silent mapping.\r\nThey also allow <SID> (providing you have done the \"exe FindBufferSID()\"\r\nat the beginning of the script), and will expand <leader> and <localleader>\r\nin menu names.\r\n\r\nIf g:buffermenu_use_disable is set to 1 then all buffermenus use\r\nenable\/disable to update the menus.  Otherwise, they will use menu\/unmenu.\r\nTo override for one menu only, use <unmenu> or <disable>\r\n\r\n\r\n:Bunmenuall\r\n      Remove all menus for the current buffer\r\n\r\nBufferOneShot( <ident> )\r\n \t\tUse this to make sure Bmenus only get added ONCE per buffer.\r\n \t\teg:\r\n \t\tif BufferOneShot('MyProgram')\r\n \t\t\tBmenu 10.20 Test.Test iHello<esc>\r\n \t\tendif\r\n \t\tA buffer local-variable called b:buffer_oneshot_MyProgram will be\r\n \t\tcreated (just in case you want to unlet it when testing).\r\n\r\nexe FindBufferSID() \r\n\t\t:exe the result of this function when using <SID> in menu commands so that the correct\r\n\t\tfunction gets called.\r\n\r\n","4":"Adds menus for the current buffer.   When you leave the buffer, they get removed, and when you go back in, they are added again.\r\nIt cannot be used effectively to replace a menu as it is not possible to find out what the mapping used to be (as for map commands), and therefore not possible to restore it (*sigh*)\r\n\r\nThis is taken from my 'buffoptions' script, and should be useful in enabling menus to be added to ftplugin scripts.\r\n\r\nNOTE: When adding to ftplugin scripts make VERY sure that the menus only get added ONCE (reinclude protection is good here).\r\n\r\nTODO: (Please email me to add to this list)\r\n- Allow 'Unmenu' of individual menus\r\n\r\n\r\nUsage -\r\n:Bmenu[!] [\"<silent>\"] [\"<unmenu>\"|\"<disable>\"] [<modes>] [<priority>] <Menuname> <Mapping>\r\n \t\tAdd menus to different modes for the current buffer.  (Bang is used to\r\n        specify 'noremenu')\r\n:B[ivacn]menu[!][\"<silent>\"] [\"<unmenu>\"|\"<disable>\"]  [<priority>] <Menuname> <Mapping>\r\n\t    Add menu for one mode (or 'a' for all modes) for the current buffer.\r\n      (Bang is used to specify 'noremenu')\r\n\r\nB[ivacn]noremenu [\"<silent>\"] [\"<unmenu>\"|\"<disable>\"] [<modes>] [<priority>] <Menuname> <Mapping>\r\n      Adds a 'norecursive' menu.\r\n\r\nThe above commands accept '<silent>' as a flag to do a silent mapping.\r\nThey also allow <SID> (providing you have done the \"exe FindBufferSID()\"\r\nat the beginning of the script), and will expand <leader> and <localleader>\r\nin menu names.\r\n\r\nIf g:buffermenu_use_disable is set to 1 then all buffermenus use\r\nenable\/disable to update the menus.  Otherwise, they will use menu\/unmenu.\r\nTo override for one menu only, use <unmenu> or <disable>\r\n\r\n\r\n:Bunmenuall\r\n      Remove all menus for the current buffer\r\n\r\nBufferOneShot( <ident> )\r\n \t\tUse this to make sure Bmenus only get added ONCE per buffer.\r\n \t\teg:\r\n \t\tif BufferOneShot('MyProgram')\r\n \t\t\tBmenu 10.20 Test.Test iHello<esc>\r\n \t\tendif\r\n \t\tA buffer local-variable called b:buffer_oneshot_MyProgram will be\r\n \t\tcreated (just in case you want to unlet it when testing).\r\n\r\nexe FindBufferSID() \r\n\t\t:exe the result of this function when using <SID> in menu commands so that the correct\r\n\t\tfunction gets called.\r\n\r\n","install_details":"This should be used as a general plugin - dump it into the plugin directory.\r\n\r\n(Without the s: and <SID> it should work for 5.6, 5.7 as well, sourced from your vimrc )","5":"This should be used as a general plugin - dump it into the plugin directory.\r\n\r\n(Without the s: and <SID> it should work for 5.6, 5.7 as well, sourced from your vimrc )","first_name":"Michael","6":"Michael","last_name":"Geddes","7":"Geddes","releases":[{"0":"246","vim_version":"6.0","1":"6.0","script_version":"1.9","2":"1.9","version_comment":"Added noremenu mappings and <silent> support (thanks Luc).  \r\nUpdated the documentation. \r\nMade provision for using <SID> in a mapping  - careful you'll need to read the docs on this one.\r\nAdded a global option to use menu enable menu disable instead of unmenu.\r\nAdded <unmenu> and <disable> options to specify explicitly whether to disable or unmenu the mapping.\r\n\r\n","3":"Added noremenu mappings and <silent> support (thanks Luc).  \r\nUpdated the documentation. \r\nMade provision for using <SID> in a mapping  - careful you'll need to read the docs on this one.\r\nAdded a global option to use menu enable menu disable instead of unmenu.\r\nAdded <unmenu> and <disable> options to specify explicitly whether to disable or unmenu the mapping.\r\n\r\n","package":"buffermenu.vim","4":"buffermenu.vim","src_id":"779","5":"779","creation_date":"1018456944","6":"1018456944"},{"0":"246","vim_version":"6.0","1":"6.0","script_version":"1.6","2":"1.6","version_comment":"Fix up a bug where spaces are used in the mapping part were causing an error to be reported.\r\n","3":"Fix up a bug where spaces are used in the mapping part were causing an error to be reported.\r\n","package":"buffermenu.vim","4":"buffermenu.vim","src_id":"753","5":"753","creation_date":"1017855621","6":"1017855621"},{"0":"246","vim_version":"6.0","1":"6.0","script_version":"1.5","2":"1.5","version_comment":"For some reason when pressing ctrl+^  I was getting two buffer unloads - this was causing menus to be undone twice and lots of errors.  I have now fixed it to make sure it only undoes the menus once.\r\n","3":"For some reason when pressing ctrl+^  I was getting two buffer unloads - this was causing menus to be undone twice and lots of errors.  I have now fixed it to make sure it only undoes the menus once.\r\n","package":"buffermenu.vim","4":"buffermenu.vim","src_id":"749","5":"749","creation_date":"1017777555","6":"1017777555"},{"0":"246","vim_version":"6.0","1":"6.0","script_version":"1.3","2":"1.3","version_comment":"Allow menus with spaces to work.\r\nEcho errors using echoerr so that they are reported properly","3":"Allow menus with spaces to work.\r\nEcho errors using echoerr so that they are reported properly","package":"buffermenu.vim","4":"buffermenu.vim","src_id":"747","5":"747","creation_date":"1017764122","6":"1017764122"},{"0":"246","vim_version":"6.0","1":"6.0","script_version":"1.2","2":"1.2","version_comment":"Don't add menus to the buffer-list that produce an error when first adding.","3":"Don't add menus to the buffer-list that produce an error when first adding.","package":"buffermenu.vim","4":"buffermenu.vim","src_id":"704","5":"704","creation_date":"1016726906","6":"1016726906"},{"0":"246","vim_version":"6.0","1":"6.0","script_version":"1.1","2":"1.1","version_comment":"Enhancements:\r\n- <maplocalleader> and <mapleader> now get expanded when adding - this means you can do: \r\n    Bamenu Test.Test<tab><maplocalleader>aa <maplocalleader>aa\r\n  And get a menu with the 'help' showing the actual localleader\/leader\r\n\r\nBugfixes:\r\n- Bamenu Bcmenu Bnmenu  now pass the correct parameters and won't give an error\r\n- Bunmenuall now works.","3":"Enhancements:\r\n- <maplocalleader> and <mapleader> now get expanded when adding - this means you can do: \r\n    Bamenu Test.Test<tab><maplocalleader>aa <maplocalleader>aa\r\n  And get a menu with the 'help' showing the actual localleader\/leader\r\n\r\nBugfixes:\r\n- Bamenu Bcmenu Bnmenu  now pass the correct parameters and won't give an error\r\n- Bunmenuall now works.","package":"buffermenu.vim","4":"buffermenu.vim","src_id":"703","5":"703","creation_date":"1016725875","6":"1016725875"},{"0":"246","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"buffermenu.vim","4":"buffermenu.vim","src_id":"683","5":"683","creation_date":"1016033218","6":"1016033218"}]},"245":{"script_id":"245","0":"245","script_name":"JavaRun","1":"JavaRun","script_type":"utility","2":"utility","summary":"Compile and run Java program","3":"Compile and run Java program","description":"Save\/compile (if necessary) and run the Java, Python, Perl, Ruby, Tcltk or CLisp source program in the current buffer.\r\n\r\nSome useful abbreviations for Java programming, e.g. psvm for \"public static void main(String[] args) { }\", cl for class, etc.","4":"Save\/compile (if necessary) and run the Java, Python, Perl, Ruby, Tcltk or CLisp source program in the current buffer.\r\n\r\nSome useful abbreviations for Java programming, e.g. psvm for \"public static void main(String[] args) { }\", cl for class, etc.","install_details":"Source this .vim file or put it in the plugin directory.\r\nOn editing a Java or other program, execute :Run [args...]<CR>\r\nwhere args are optional command line arguments to the program.\r\n\r\nAlternatively, just press <F5> to run the program without arguments.\r\n\r\nThis script use the jikes compiler for Java program by default. You may change to javac by modifying the makeprg and errorformat options inside the script.","5":"Source this .vim file or put it in the plugin directory.\r\nOn editing a Java or other program, execute :Run [args...]<CR>\r\nwhere args are optional command line arguments to the program.\r\n\r\nAlternatively, just press <F5> to run the program without arguments.\r\n\r\nThis script use the jikes compiler for Java program by default. You may change to javac by modifying the makeprg and errorformat options inside the script.","first_name":"Kendrew","6":"Kendrew","last_name":"Lau","7":"Lau","releases":[{"0":"245","vim_version":"6.0","1":"6.0","script_version":"0.2","2":"0.2","version_comment":"Added useful abbreviations for Java programming, e.g. psvm for \"public static void main(String[] args) { }\", cl for class, etc.\n\nAdded key mapping for <F5> to run the program.\n\nAdded support for running Python, Perl, Tcltk, Ruby, CLisp programs (according to file extension).\n","3":"Added useful abbreviations for Java programming, e.g. psvm for \"public static void main(String[] args) { }\", cl for class, etc.\n\nAdded key mapping for <F5> to run the program.\n\nAdded support for running Python, Perl, Tcltk, Ruby, CLisp programs (according to file extension).\n","package":"JavaRun.vim","4":"JavaRun.vim","src_id":"1432","5":"1432","creation_date":"1037648171","6":"1037648171"},{"0":"245","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"JavaRun.vim","4":"JavaRun.vim","src_id":"682","5":"682","creation_date":"1015984848","6":"1015984848"}]},"244":{"script_id":"244","0":"244","script_name":"imaps.vim","1":"imaps.vim","script_type":"utility","2":"utility","summary":"another template or stub expander","3":"another template or stub expander","description":"imaps.vim is yet another template expander or Stubs expander like several\r\nothers out there.\r\n\r\nThe expander works by the user pressing '\\\\' (or whatever the leader\r\ncharacter is), after a \"keyword\". the keywords are filetype specific. to\r\ngive an example, suppose you press '\\\\' after the word 'bfg' in a latex file\r\n(filetype = tex), then the word 'bfg' will expand to:\r\n\r\n\\begin{figure}[h]\r\n\\centerline{\\psfig{figure=*.eps}}\r\n\\caption{}\r\n\\label{fig:}\r\n\\end{figure}\r\n\r\nand the cursor will be placed where '*' is shown. vim remains in insert\r\nmode so that you can continue typing. if you type '\\\\' after something which\r\nis not defined as a keyword for the current filetype, then you will simply\r\nget a '\\\\'.\r\n\r\nthe file already contains several mappings mainly for latex and some for\r\nhtml. however it should be very easy to extend it to your liking. it should\r\nbe fairly obvious how to extend it if you look at the file, but here's the\r\nlittle description:\r\n\r\nsuppose you want the keyword 'bit' to expand to \r\n\r\n\\begin{itemize}\r\n\\item * \r\n\\end{itemize}\r\n\r\nand have the cursor be positioned where '*' is shown, add the following\r\nline to imaps.vim (actually, this line is already there, but it makes for\r\na good example)\r\n\r\nlet s:tex_bit       = \"\\\\begin{itemize}\\<cr>\\\\item \u00c3\u00a4\\<cr>\\\\end{itemize}\"\r\n\r\nexplanation:\r\n1. the suffix 's:' is to make it script specific.\r\n2. then 'tex' makes imaps.vim treat 'deg' as a keyword only for latex\r\n   files.\r\n3. 'bit' is the keyword itself.\r\n4. the rhs is what you want to have 'bit' expand to. if you want the cursor\r\n   not to be positioned anywhere special, then nothing needs to be done.\r\n   the cursor will be placed at the end. However, if like in this example,\r\n   you want it to be at a specific place, put a \"\u00c3\u00a4\" (the a-double-dot\r\n   character) where you want the cursor to be. (the \u00c3\u00a4 character is obtained\r\n   by typing control-k-a-colon <C-k> + a + : ). \r\n\r\nNOTE: \r\n\r\n1. if you want a \"dynamic\" rhs, i.e you want the keyword 'date' to expand\r\n   to the present date, then you can have the rhs begin with the string\r\n   \"<C-r>=\". for example, the following line does the date thingie:\r\n\r\n   let s:_date = \"\\<c-r>=strftime('%b %d %Y')\\<cr>\"\r\n    \r\n   (\":help i_CTRL-R\" for how this works).\r\n\r\n2. if you want a keyword to be filetype insensetive (i.e to work across all\r\n   files) like the date thing above, then like the example above, do not\r\n   prepend any file type, just use \r\n\r\n   let s:_keyword = expansion\r\n\r\n   (note the leading underscore after s:)\r\n\r\n","4":"imaps.vim is yet another template expander or Stubs expander like several\r\nothers out there.\r\n\r\nThe expander works by the user pressing '\\\\' (or whatever the leader\r\ncharacter is), after a \"keyword\". the keywords are filetype specific. to\r\ngive an example, suppose you press '\\\\' after the word 'bfg' in a latex file\r\n(filetype = tex), then the word 'bfg' will expand to:\r\n\r\n\\begin{figure}[h]\r\n\\centerline{\\psfig{figure=*.eps}}\r\n\\caption{}\r\n\\label{fig:}\r\n\\end{figure}\r\n\r\nand the cursor will be placed where '*' is shown. vim remains in insert\r\nmode so that you can continue typing. if you type '\\\\' after something which\r\nis not defined as a keyword for the current filetype, then you will simply\r\nget a '\\\\'.\r\n\r\nthe file already contains several mappings mainly for latex and some for\r\nhtml. however it should be very easy to extend it to your liking. it should\r\nbe fairly obvious how to extend it if you look at the file, but here's the\r\nlittle description:\r\n\r\nsuppose you want the keyword 'bit' to expand to \r\n\r\n\\begin{itemize}\r\n\\item * \r\n\\end{itemize}\r\n\r\nand have the cursor be positioned where '*' is shown, add the following\r\nline to imaps.vim (actually, this line is already there, but it makes for\r\na good example)\r\n\r\nlet s:tex_bit       = \"\\\\begin{itemize}\\<cr>\\\\item \u00c3\u00a4\\<cr>\\\\end{itemize}\"\r\n\r\nexplanation:\r\n1. the suffix 's:' is to make it script specific.\r\n2. then 'tex' makes imaps.vim treat 'deg' as a keyword only for latex\r\n   files.\r\n3. 'bit' is the keyword itself.\r\n4. the rhs is what you want to have 'bit' expand to. if you want the cursor\r\n   not to be positioned anywhere special, then nothing needs to be done.\r\n   the cursor will be placed at the end. However, if like in this example,\r\n   you want it to be at a specific place, put a \"\u00c3\u00a4\" (the a-double-dot\r\n   character) where you want the cursor to be. (the \u00c3\u00a4 character is obtained\r\n   by typing control-k-a-colon <C-k> + a + : ). \r\n\r\nNOTE: \r\n\r\n1. if you want a \"dynamic\" rhs, i.e you want the keyword 'date' to expand\r\n   to the present date, then you can have the rhs begin with the string\r\n   \"<C-r>=\". for example, the following line does the date thingie:\r\n\r\n   let s:_date = \"\\<c-r>=strftime('%b %d %Y')\\<cr>\"\r\n    \r\n   (\":help i_CTRL-R\" for how this works).\r\n\r\n2. if you want a keyword to be filetype insensetive (i.e to work across all\r\n   files) like the date thing above, then like the example above, do not\r\n   prepend any file type, just use \r\n\r\n   let s:_keyword = expansion\r\n\r\n   (note the leading underscore after s:)\r\n\r\n","install_details":"drop in your plugin directory or (not recommended) source it from your .vimrc","5":"drop in your plugin directory or (not recommended) source it from your .vimrc","first_name":"Srinath","6":"Srinath","last_name":"Avadhanula","7":"Avadhanula","releases":[{"0":"244","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"imaps.vim","4":"imaps.vim","src_id":"681","5":"681","creation_date":"1015972691","6":"1015972691"}]},"243":{"script_id":"243","0":"243","script_name":"mu-marks","1":"mu-marks","script_type":"utility","2":"utility","summary":"Script inspired by AlphaTk & Stephen Riemhm's bracketing function","3":"Script inspired by AlphaTk & Stephen Riemhm's bracketing function","description":"Template expander.\r\nUnique feature: one command for insert and visual-mode expansion.\r\n\r\nThe MarkMap and MarkMapB commands allows you to make global and filetype-specific mappings. MarkMapB commands can be in your ftplugin dir in the appropiate file. The only weirdness is the typing of the command. Well, these weird characters should be configurable. (But I think they're at least readable, and look good)\r\nOne example mapping (in my vim.vim)\r\nMarkMapB wh wh \u00c2\u00ab\u00c2\u00bb<CR>\u00c2\u00b6endw\u00c2\u00ab\u00c2\u00a1\u00c2\u00bb\r\nAfter typing wh, and pressing <C-Space> (you can change it) in insert mode, you will get\r\nwh |\r\nendw\u00c2\u00ab\u00c2\u00bb\r\n| symbols the cursor.\r\nSo the \u00c2\u00ab\u00c2\u00bb characters are the cursor positions, and the furthers are the jump-points. There can be an explanation text between these 2 chars, so \u00c2\u00abexplanation\u00c2\u00bb is allowed.\r\nIf you have a line\r\necho 'Hello world'\r\nand you select it visually, press <C-Space> and type wh<CR>, you will get\r\nwh |\r\n  echo 'Hello world'\r\nendw\r\nSo the \u00c2\u00b6 sign is replaced by the visually selected text (adding an extra newline if needed).\r\nIf you want to remove the trailing newline (if any) you can use the \u00c2\u00b7 symbol.\r\nNotice, that there is no mark after the endw.\r\nMarks, that begin with \u00c2\u00ab\u00c2\u00a1 are not used in visual mappings.","4":"Template expander.\r\nUnique feature: one command for insert and visual-mode expansion.\r\n\r\nThe MarkMap and MarkMapB commands allows you to make global and filetype-specific mappings. MarkMapB commands can be in your ftplugin dir in the appropiate file. The only weirdness is the typing of the command. Well, these weird characters should be configurable. (But I think they're at least readable, and look good)\r\nOne example mapping (in my vim.vim)\r\nMarkMapB wh wh \u00c2\u00ab\u00c2\u00bb<CR>\u00c2\u00b6endw\u00c2\u00ab\u00c2\u00a1\u00c2\u00bb\r\nAfter typing wh, and pressing <C-Space> (you can change it) in insert mode, you will get\r\nwh |\r\nendw\u00c2\u00ab\u00c2\u00bb\r\n| symbols the cursor.\r\nSo the \u00c2\u00ab\u00c2\u00bb characters are the cursor positions, and the furthers are the jump-points. There can be an explanation text between these 2 chars, so \u00c2\u00abexplanation\u00c2\u00bb is allowed.\r\nIf you have a line\r\necho 'Hello world'\r\nand you select it visually, press <C-Space> and type wh<CR>, you will get\r\nwh |\r\n  echo 'Hello world'\r\nendw\r\nSo the \u00c2\u00b6 sign is replaced by the visually selected text (adding an extra newline if needed).\r\nIf you want to remove the trailing newline (if any) you can use the \u00c2\u00b7 symbol.\r\nNotice, that there is no mark after the endw.\r\nMarks, that begin with \u00c2\u00ab\u00c2\u00a1 are not used in visual mappings.","install_details":"Drop into your plugin dir.\r\nA little usage comment inside.\r\nAsk me, if something isn't clear!","5":"Drop into your plugin dir.\r\nA little usage comment inside.\r\nAsk me, if something isn't clear!","first_name":"Gergely","6":"Gergely","last_name":"Kontra","7":"Kontra","releases":[{"0":"243","vim_version":"6.0","1":"6.0","script_version":"0.12","2":"0.12","version_comment":"Bugfixes","3":"Bugfixes","package":"mu-marks.vim","4":"mu-marks.vim","src_id":"680","5":"680","creation_date":"1015935163","6":"1015935163"},{"0":"243","vim_version":"6.0","1":"6.0","script_version":"0.11","2":"0.11","version_comment":"Bugfixes","3":"Bugfixes","package":"mu-marks.vim","4":"mu-marks.vim","src_id":"677","5":"677","creation_date":"1015915968","6":"1015915968"},{"0":"243","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"MicroMarks.vim","4":"MicroMarks.vim","src_id":"674","5":"674","creation_date":"1015837661","6":"1015837661"}]},"242":{"script_id":"242","0":"242","script_name":"cream-capitalization","1":"cream-capitalization","script_type":"utility","2":"utility","summary":"Capitalize a selection in one of four ways","3":"Capitalize a selection in one of four ways","description":"\r\nA simple collection of functions (and mappings) to capitalize a selection in one of four ways:\r\n  UPPERCASE, lowercase, Title Case and rEVERSE cASE.\r\n\r\ncream-capitalize makes these F5 combination keyboard shortcuts available:\r\n\r\n  F5           Capitalize selection, title case\r\n  Shift+F5     Uppercase selection\r\n  Alt+F5       Lowercase selection\r\n  Ctrl+F5      Reverse case of selection\r\n\r\nThis is one of many custom utilities and functions for gVim from the Cream project ( http:\/\/cream.sourceforge.net ), a configuration of Vim for those of us familiar with Apple and Windows software. \r\n\r\n","4":"\r\nA simple collection of functions (and mappings) to capitalize a selection in one of four ways:\r\n  UPPERCASE, lowercase, Title Case and rEVERSE cASE.\r\n\r\ncream-capitalize makes these F5 combination keyboard shortcuts available:\r\n\r\n  F5           Capitalize selection, title case\r\n  Shift+F5     Uppercase selection\r\n  Alt+F5       Lowercase selection\r\n  Ctrl+F5      Reverse case of selection\r\n\r\nThis is one of many custom utilities and functions for gVim from the Cream project ( http:\/\/cream.sourceforge.net ), a configuration of Vim for those of us familiar with Apple and Windows software. \r\n\r\n","install_details":"Simply copy this file and paste it into your vimrc. Or you can drop the entire file into your plugins directory.\r\n\r\n","5":"Simply copy this file and paste it into your vimrc. Or you can drop the entire file into your plugins directory.\r\n\r\n","first_name":"Steve","6":"Steve","last_name":"Hall","7":"Hall","releases":[{"0":"242","vim_version":"7.0","1":"7.0","script_version":"2.5","2":"2.5","version_comment":"Correct apostrophe \"s\" being capitalized. [Adam Lehigh]","3":"Correct apostrophe \"s\" being capitalized. [Adam Lehigh]","package":"cream-capitalization.vim","4":"cream-capitalization.vim","src_id":"21945","5":"21945","creation_date":"1401116308","6":"1401116308"},{"0":"242","vim_version":"6.0","1":"6.0","script_version":"2.4","2":"2.4","version_comment":"Title case keeps select articles lower case, added localized cursor positioning function call.","3":"Title case keeps select articles lower case, added localized cursor positioning function call.","package":"cream-capitalization.vim","4":"cream-capitalization.vim","src_id":"8195","5":"8195","creation_date":"1201605769","6":"1201605769"},{"0":"242","vim_version":"6.0","1":"6.0","script_version":"2.3","2":"2.3","version_comment":"Fixed function name inconsistency. (Sorry. ;)","3":"Fixed function name inconsistency. (Sorry. ;)","package":"cream-capitalization.vim","4":"cream-capitalization.vim","src_id":"2560","5":"2560","creation_date":"1070741822","6":"1070741822"},{"0":"242","vim_version":"6.0","1":"6.0","script_version":"2.2","2":"2.2","version_comment":"Cleaner, faster. First update released here since v1.3. Matches current Cream. (See internal ChangeLog.)","3":"Cleaner, faster. First update released here since v1.3. Matches current Cream. (See internal ChangeLog.)","package":"cream-capitalization.vim","4":"cream-capitalization.vim","src_id":"2557","5":"2557","creation_date":"1070696455","6":"1070696455"},{"0":"242","vim_version":"6.0","1":"6.0","script_version":"1.3","2":"1.3","version_comment":"Fixed positioning \"anomalies\" for title case. (Hopefully for good!)","3":"Fixed positioning \"anomalies\" for title case. (Hopefully for good!)","package":"cream-capitalization.vim","4":"cream-capitalization.vim","src_id":"875","5":"875","creation_date":"1021677820","6":"1021677820"}]},"241":{"script_id":"241","0":"241","script_name":"xul.vim","1":"xul.vim","script_type":"syntax","2":"syntax","summary":"Syntax for the eXtensible User interface Language","3":"Syntax for the eXtensible User interface Language","description":"Syntax highlighting for XUL based on the DocBook highlighting by Devin Weaver. Optional attribute highlighting for common XUL attributes is included.","4":"Syntax highlighting for XUL based on the DocBook highlighting by Devin Weaver. Optional attribute highlighting for common XUL attributes is included.","install_details":"Place file in your syntax directory. The files should have the extension .xul.\r\nFor attribute-highlighting put hl_xul_atts = 1 in your .(g)vimrc.","5":"Place file in your syntax directory. The files should have the extension .xul.\r\nFor attribute-highlighting put hl_xul_atts = 1 in your .(g)vimrc.","first_name":"Nikolai","6":"Nikolai","last_name":"Nespor","7":"Nespor","releases":[{"0":"241","vim_version":"6.0","1":"6.0","script_version":"0.5","2":"0.5","version_comment":"Bring keyword and attribute list up-to-date.","3":"Bring keyword and attribute list up-to-date.","package":"xul.vim","4":"xul.vim","src_id":"3892","5":"3892","creation_date":"1109046054","6":"1109046054"},{"0":"241","vim_version":"6.0","1":"6.0","script_version":"0.4","2":"0.4","version_comment":"Bring keywords and attributes up to date. Both are taken from http:\/\/www.xulplanet.com\/.","3":"Bring keywords and attributes up to date. Both are taken from http:\/\/www.xulplanet.com\/.","package":"xul.vim","4":"xul.vim","src_id":"3272","5":"3272","creation_date":"1090667979","6":"1090667979"},{"0":"241","vim_version":"6.0","1":"6.0","script_version":"0.3","2":"0.3","version_comment":"Cleand up keyword list. Only common XUL attributes are now highlighted.","3":"Cleand up keyword list. Only common XUL attributes are now highlighted.","package":"xul.vim","4":"xul.vim","src_id":"1232","5":"1232","creation_date":"1032738770","6":"1032738770"},{"0":"241","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"xul.vim","4":"xul.vim","src_id":"669","5":"669","creation_date":"1015657868","6":"1015657868"}]},"240":{"script_id":"240","0":"240","script_name":"perforce","1":"perforce","script_type":"utility","2":"utility","summary":"Feature Rich Perforce SCM Integration.","3":"Feature Rich Perforce SCM Integration.","description":"PLEASE READ THE INSTALL SECTION COMPLETELY.\r\n\r\nThis is a fairly complete integration with the perforce version control system for the most commanly used operations, including many administrative commands. It includes a great menu that is modelled very close to the p4win (the perforce GUI client) and is quite extensive.\r\n\r\n---------------------------------------------------------------------------------------------------------------------------------------------------\r\nLately, I am not finding enough time to add features to this, so if anybody is interested to help me add new features or even take over the responsibility, you are very much welcome.\r\n---------------------------------------------------------------------------------------------------------------------------------------------------\r\n\r\nInstall the files as described in the installation section below and read and type \":h perforce.txt\" for help on using the plugin.\r\n\r\nIf you find any problems please report them to me. If you happen to add new features or fix any problems, I would appreciate if you send me in the diff. This will speed up the future enhancements (there is a lot more that can be done) and also benefit all the script users.\r\n\r\nSearch_key_words: perforce scm source control interface p4 p4d p4win multvals genutils Hari Krishna Dara","4":"PLEASE READ THE INSTALL SECTION COMPLETELY.\r\n\r\nThis is a fairly complete integration with the perforce version control system for the most commanly used operations, including many administrative commands. It includes a great menu that is modelled very close to the p4win (the perforce GUI client) and is quite extensive.\r\n\r\n---------------------------------------------------------------------------------------------------------------------------------------------------\r\nLately, I am not finding enough time to add features to this, so if anybody is interested to help me add new features or even take over the responsibility, you are very much welcome.\r\n---------------------------------------------------------------------------------------------------------------------------------------------------\r\n\r\nInstall the files as described in the installation section below and read and type \":h perforce.txt\" for help on using the plugin.\r\n\r\nIf you find any problems please report them to me. If you happen to add new features or fix any problems, I would appreciate if you send me in the diff. This will speed up the future enhancements (there is a lot more that can be done) and also benefit all the script users.\r\n\r\nSearch_key_words: perforce scm source control interface p4 p4d p4win multvals genutils Hari Krishna Dara","install_details":"- Extract the zip file into your runtime directory (~\/.vim or %HOME%\/vimfiles).\r\n- Download the latest versions of the below scripts and place them in your runtime plugin directory (see end for instructions specific to older version):\r\n    genutils.vim: vimscript#197\r\n- Start Vim and regenerate help tags on your runtime doc directory. Ex:\r\n    :helpt ~\/.vim\/doc\r\n    :helpt ~\\vimfiles\\doc\r\n- Type the following command and read the installation section to complete the installation:\r\n    :help perforce-installation\r\n\r\nFor versions prior to 4.0, you need to download multvals.vim (vimscript#171) in addition to genutils, but make sure you download only the non-autoload versions of both genutils and multvals plugins (see their download page for details, and a trick to have both coexists).\r\n","5":"- Extract the zip file into your runtime directory (~\/.vim or %HOME%\/vimfiles).\r\n- Download the latest versions of the below scripts and place them in your runtime plugin directory (see end for instructions specific to older version):\r\n    genutils.vim: vimscript#197\r\n- Start Vim and regenerate help tags on your runtime doc directory. Ex:\r\n    :helpt ~\/.vim\/doc\r\n    :helpt ~\\vimfiles\\doc\r\n- Type the following command and read the installation section to complete the installation:\r\n    :help perforce-installation\r\n\r\nFor versions prior to 4.0, you need to download multvals.vim (vimscript#171) in addition to genutils, but make sure you download only the non-autoload versions of both genutils and multvals plugins (see their download page for details, and a trick to have both coexists).\r\n","first_name":"Hari Krishna","6":"Hari Krishna","last_name":"Dara","7":"Dara","releases":[{"0":"240","vim_version":"7.0","1":"7.0","script_version":"4.1","2":"4.1","version_comment":"There were a few issues with the 4.0 version, and this version tries to resolve them, and adds a few features.\r\n\r\n- Fixed broken handling of <SHOW DIFF> in describe windows. But it is\r\n  better than before, as you can now describe multiple changelists and\r\n  show diffs selectively.\r\n- For newer perforce servers, <Enter> on a pending change (in\r\n  changelist) showed the file list twice. Removed special handling for\r\n  this, which means for older perforce servers, you will see no file\r\n  list.\r\n- Force a file status update on auto checkout.\r\n- File status handling has in general been improved.\r\n- Now executing command on multiple files that result in changing the\r\n  file statuses (such as add, edit, revert etc.) will correctly result\r\n  in their file statuses getting reset.\r\n- While create a new changelist or submitting a change, the Files:\r\n  section is examined and the file statuses for all of them will be\r\n  reset. This also works for most of the cases of modifying a changelist\r\n  to remove\/add files.\r\n- This will also solve a long standing issue that reload during submit\r\n  doesn't update its file status.\r\n- All windows are getting navigatation commands mapped (like in help\r\n  window)\r\n- Workaround for one of the E788 errors (originating from the plugin)\r\n  during the auto-checkout. This part of the code has been cleaned up\r\n  and simplified. During the auto-checkout, if there are other users\r\n  editing the same file, it now results in the plugin echoing the output\r\n  as a |WarningMsg|. If you missed to read the output (because you\r\n  pressed <Enter> in advance), you can see it again using the\r\n  |PFLastMessage| command. The other E788 originating from Vim code\r\n  can't be fixed\/workedaround, it has to be fixed by Bram.\r\n- Fixed broken submit from changelist.\r\n- When you create changelists, you can now safely undo to make any\r\n  further changes, and save them. This also works for submissions (to\r\n  edit description only), though you may have to remove the Files\r\n  section before saving the change description.\r\n","3":"There were a few issues with the 4.0 version, and this version tries to resolve them, and adds a few features.\r\n\r\n- Fixed broken handling of <SHOW DIFF> in describe windows. But it is\r\n  better than before, as you can now describe multiple changelists and\r\n  show diffs selectively.\r\n- For newer perforce servers, <Enter> on a pending change (in\r\n  changelist) showed the file list twice. Removed special handling for\r\n  this, which means for older perforce servers, you will see no file\r\n  list.\r\n- Force a file status update on auto checkout.\r\n- File status handling has in general been improved.\r\n- Now executing command on multiple files that result in changing the\r\n  file statuses (such as add, edit, revert etc.) will correctly result\r\n  in their file statuses getting reset.\r\n- While create a new changelist or submitting a change, the Files:\r\n  section is examined and the file statuses for all of them will be\r\n  reset. This also works for most of the cases of modifying a changelist\r\n  to remove\/add files.\r\n- This will also solve a long standing issue that reload during submit\r\n  doesn't update its file status.\r\n- All windows are getting navigatation commands mapped (like in help\r\n  window)\r\n- Workaround for one of the E788 errors (originating from the plugin)\r\n  during the auto-checkout. This part of the code has been cleaned up\r\n  and simplified. During the auto-checkout, if there are other users\r\n  editing the same file, it now results in the plugin echoing the output\r\n  as a |WarningMsg|. If you missed to read the output (because you\r\n  pressed <Enter> in advance), you can see it again using the\r\n  |PFLastMessage| command. The other E788 originating from Vim code\r\n  can't be fixed\/workedaround, it has to be fixed by Bram.\r\n- Fixed broken submit from changelist.\r\n- When you create changelists, you can now safely undo to make any\r\n  further changes, and save them. This also works for submissions (to\r\n  edit description only), though you may have to remove the Files\r\n  section before saving the change description.\r\n","package":"perforce-4.1.zip","4":"perforce-4.1.zip","src_id":"6139","5":"6139","creation_date":"1157278579","6":"1157278579"},{"0":"240","vim_version":"7.0","1":"7.0","script_version":"4.0","2":"4.0","version_comment":"Uploading again, the previous attempt had a a file missing in the zip.\r\n\r\n- Using Vim7 features, so it is no longer backwards compatible with\r\n  older Vim releases. All the logic using multvals has been changed to\r\n  take advantage of the Vim7 Lists, so it should be a lot more cleaner\r\n  and flexible.\r\n- No longer depends on multvals plugin.\r\n- It is now autoloaded on demand, which means it will help your vim\r\n  session load faster. Read the impact on the installation due to this\r\n  change, |perforce-installation|.\r\n- A new Cancel option for checkout prompt, see\r\n  |perforce-automatic-checkout|. The default for checkout prompt is now\r\n  \"Cancel\".\r\n- The perforce\/perforcemenu.vim needs to be loaded from your vimrc if\r\n  you want menu to be enabled. See |perforce-installation|.\r\n- The plugin no longer removes the global user setting variables but you\r\n  still need to call |:PFInitialize| for effect of some settings to\r\n  propogate further. This should have no user visible impact (except in\r\n  rare cases).  This will only make it easier to deal with settings. You\r\n  can still use |:PFSettings| command conveniently for its prompting or\r\n  completion features.\r\n- Setting a preset to the g:p4DefaultPreset directly now works fine.\r\n- Most settings can now be overridden at the buffer\/window\/tab level.\r\n- Bug: PFRefreshActivePane doesn't work well on the diff windows (especially\r\n  when the ++c option is used). ","3":"Uploading again, the previous attempt had a a file missing in the zip.\r\n\r\n- Using Vim7 features, so it is no longer backwards compatible with\r\n  older Vim releases. All the logic using multvals has been changed to\r\n  take advantage of the Vim7 Lists, so it should be a lot more cleaner\r\n  and flexible.\r\n- No longer depends on multvals plugin.\r\n- It is now autoloaded on demand, which means it will help your vim\r\n  session load faster. Read the impact on the installation due to this\r\n  change, |perforce-installation|.\r\n- A new Cancel option for checkout prompt, see\r\n  |perforce-automatic-checkout|. The default for checkout prompt is now\r\n  \"Cancel\".\r\n- The perforce\/perforcemenu.vim needs to be loaded from your vimrc if\r\n  you want menu to be enabled. See |perforce-installation|.\r\n- The plugin no longer removes the global user setting variables but you\r\n  still need to call |:PFInitialize| for effect of some settings to\r\n  propogate further. This should have no user visible impact (except in\r\n  rare cases).  This will only make it easier to deal with settings. You\r\n  can still use |:PFSettings| command conveniently for its prompting or\r\n  completion features.\r\n- Setting a preset to the g:p4DefaultPreset directly now works fine.\r\n- Most settings can now be overridden at the buffer\/window\/tab level.\r\n- Bug: PFRefreshActivePane doesn't work well on the diff windows (especially\r\n  when the ++c option is used). ","package":"perforce-4.0.zip","4":"perforce-4.0.zip","src_id":"6129","5":"6129","creation_date":"1157115530","6":"1157115530"},{"0":"240","vim_version":"6.0","1":"6.0","script_version":"3.2","2":"3.2","version_comment":"Release 3.2 for vim7 compatibility. There are a few enhancements too. This is probably the last version that will work in Vim 6.3\/6.4.\r\n- Fixed PVDiff to work with two filenames. The problem was only with\r\n  PVDiff command, as \"PF vdiff\" worked fine.\r\n- PFDiffOff command is a lot more flexible now, see |PFDiffOff|.\r\n- New command PPasswd for changing passwords.\r\n- Don't confirm revert if -a or -n option is passed.\r\n- Avoid accidentally loosing existing buffers while opening new ones\r\n  from diff and other windows.\r\n- Recognize additional p4 commands as valid.\r\n- You can now pass multiple codeline modifiers, see\r\n  |perforce-alternative-codeline-modifier|.\r\n- Misc. tuneups for peforce diff hyperlinking feature.\r\n- Misc. bugfixes in the menu.\r\n","3":"Release 3.2 for vim7 compatibility. There are a few enhancements too. This is probably the last version that will work in Vim 6.3\/6.4.\r\n- Fixed PVDiff to work with two filenames. The problem was only with\r\n  PVDiff command, as \"PF vdiff\" worked fine.\r\n- PFDiffOff command is a lot more flexible now, see |PFDiffOff|.\r\n- New command PPasswd for changing passwords.\r\n- Don't confirm revert if -a or -n option is passed.\r\n- Avoid accidentally loosing existing buffers while opening new ones\r\n  from diff and other windows.\r\n- Recognize additional p4 commands as valid.\r\n- You can now pass multiple codeline modifiers, see\r\n  |perforce-alternative-codeline-modifier|.\r\n- Misc. tuneups for peforce diff hyperlinking feature.\r\n- Misc. bugfixes in the menu.\r\n","package":"perforce-3.2.zip","4":"perforce-3.2.zip","src_id":"5660","5":"5660","creation_date":"1147108166","6":"1147108166"},{"0":"240","vim_version":"6.0","1":"6.0","script_version":"3.1","2":"3.1","version_comment":"- This version introduces the concept of overriding settints at the\r\n  buffer\/window level (an extension of the existing support for\r\n  b:p4Options). Makes it easier to work with multiple clients from a single\r\n  vim instance. Currently only the p4Client\/p4Port\/p4User\/clientRoot can be\r\n  set at buffer\/window level.\r\n- Now view mappings are maintained separately for each client. This allows\r\n  us to easily work with multiple clients at once. Also see\r\n  |perforce-buffer-local-options|.\r\n- For diff hyperlinking, avoid refreshing the depot file if it already\r\n  visible.\r\n- Now supports <pfitem> tag to mean the current list item. See |:<pfite>|\r\n- New :PExec command to make it easier to execute exeternal perforce\r\n  commands directly, when plugin can't do what you want. See |PExec|.\r\n- PFDiffLink and PFDiffVLink commands couldn't handle \"diff -r\" output.\r\n- If the current directory is not same as the directory of file being\r\n  resolved PFShowConflicts didn't work.\r\n- PItemOpen in describe window now opens the local file, as PItemDescribe\r\n  can be used to open the depot file.\r\n- Misc. bug fixes:\r\n    - Negative revisions are not working any more. E.g., PP #-1\r\n    - PW is not using the custom completion, so revision specifier (#1)\r\n      still needs to be escaped.\r\n    - While rerunning a command that opens up a new buffer (such as PD),\r\n      unexpected warning messages about matching an existing buffer.\r\n      Instead, it should silently refresh the output.\r\n    - Diff hyperlinking, prints the depot file everytime, this causes\r\n      unnecessary delays.\r\n    - PFRefreshActivePane would fail if there are filename special\r\n      characters in the command.\r\n","3":"- This version introduces the concept of overriding settints at the\r\n  buffer\/window level (an extension of the existing support for\r\n  b:p4Options). Makes it easier to work with multiple clients from a single\r\n  vim instance. Currently only the p4Client\/p4Port\/p4User\/clientRoot can be\r\n  set at buffer\/window level.\r\n- Now view mappings are maintained separately for each client. This allows\r\n  us to easily work with multiple clients at once. Also see\r\n  |perforce-buffer-local-options|.\r\n- For diff hyperlinking, avoid refreshing the depot file if it already\r\n  visible.\r\n- Now supports <pfitem> tag to mean the current list item. See |:<pfite>|\r\n- New :PExec command to make it easier to execute exeternal perforce\r\n  commands directly, when plugin can't do what you want. See |PExec|.\r\n- PFDiffLink and PFDiffVLink commands couldn't handle \"diff -r\" output.\r\n- If the current directory is not same as the directory of file being\r\n  resolved PFShowConflicts didn't work.\r\n- PItemOpen in describe window now opens the local file, as PItemDescribe\r\n  can be used to open the depot file.\r\n- Misc. bug fixes:\r\n    - Negative revisions are not working any more. E.g., PP #-1\r\n    - PW is not using the custom completion, so revision specifier (#1)\r\n      still needs to be escaped.\r\n    - While rerunning a command that opens up a new buffer (such as PD),\r\n      unexpected warning messages about matching an existing buffer.\r\n      Instead, it should silently refresh the output.\r\n    - Diff hyperlinking, prints the depot file everytime, this causes\r\n      unnecessary delays.\r\n    - PFRefreshActivePane would fail if there are filename special\r\n      characters in the command.\r\n","package":"perforce-3.1.zip","4":"perforce-3.1.zip","src_id":"3587","5":"3587","creation_date":"1098992802","6":"1098992802"},{"0":"240","vim_version":"6.0","1":"6.0","script_version":"3.0","2":"3.0","version_comment":"Now requires Vim 6.3 and the latest versions of genutils and multvals plugins.\r\n\r\nToo many changes to be listed here, read the |perforce-version-changes| section for details.\r\n\r\nTakes advantage of some of the new Vim 6.3 features.\r\n\r\nI recommend reading |perforce-troubleshooting|, |perforce-known-issues|, |perforce-tips| sections. Many of the other sections also have been updated, which are cross referenced from the version changes section.\r\n\r\nPlease report issues using the new PFBugReport command.","3":"Now requires Vim 6.3 and the latest versions of genutils and multvals plugins.\r\n\r\nToo many changes to be listed here, read the |perforce-version-changes| section for details.\r\n\r\nTakes advantage of some of the new Vim 6.3 features.\r\n\r\nI recommend reading |perforce-troubleshooting|, |perforce-known-issues|, |perforce-tips| sections. Many of the other sections also have been updated, which are cross referenced from the version changes section.\r\n\r\nPlease report issues using the new PFBugReport command.","package":"perforce-3.0.zip","4":"perforce-3.0.zip","src_id":"3318","5":"3318","creation_date":"1092244666","6":"1092244666"},{"0":"240","vim_version":"6.0","1":"6.0","script_version":"2.0","2":"2.0","version_comment":"There are too many changes to mention here. Most notable ones being, the new online help for the plugin and the perforce ruler feature from Tom's perforce plugin which is now integrated into this with some improvements. Regenerate help tags after extracting the zip. I highly recommend reading through at least the installation, changes, troubleshooting and tips sections of the help. I also recommend at least glancing through the rest of the help to have an idea of what the plugin is capable of doing. I appreciate feedback.\r\n\r\nDownload the new versions of multvals.vim and genutils.vim.","3":"There are too many changes to mention here. Most notable ones being, the new online help for the plugin and the perforce ruler feature from Tom's perforce plugin which is now integrated into this with some improvements. Regenerate help tags after extracting the zip. I highly recommend reading through at least the installation, changes, troubleshooting and tips sections of the help. I also recommend at least glancing through the rest of the help to have an idea of what the plugin is capable of doing. I appreciate feedback.\r\n\r\nDownload the new versions of multvals.vim and genutils.vim.","package":"perforce-2.0.zip","4":"perforce-2.0.zip","src_id":"2437","5":"2437","creation_date":"1067523464","6":"1067523464"},{"0":"240","vim_version":"6.0","1":"6.0","script_version":"1.3","2":"1.3","version_comment":"- You need genutils.vim version (1.0.24)\r\n- Now the PSubmit and PDiff2 commands are enhanced. PSubmit can now take arguments that are directly passed to POpened to generate the list of files to submit. So it is possible to say \"PSubmit % #\" to open the template with only the current and alternate files or \"PSubmit \/\/depot\/branch\/...\" to open the template with all the opened files under the given branch. \r\n- You can now pass in filters at the end of the commands. Just make sure you have a white space before the pipe. Ex: \r\n\r\n  PChanges -s pending | grep hari \r\n\r\n- I added ^X^P command line mapping which works like the \"E\" command but provides more flexibility. I also added ^X^I command line mapping for list windows (such as PF changes), which inserts the current item name on to the command line. Try them, they are very useful. \r\n- New commands for clients, labels windows to create a new item from the current item as a template (type P). \r\n- In the filelist windows, you can now press p to print the current file and S to sync to the current file. \r\n- Another major change is improved command line parsing. \r\n- Also the syntax highlighting has been improved to cover more cases.","3":"- You need genutils.vim version (1.0.24)\r\n- Now the PSubmit and PDiff2 commands are enhanced. PSubmit can now take arguments that are directly passed to POpened to generate the list of files to submit. So it is possible to say \"PSubmit % #\" to open the template with only the current and alternate files or \"PSubmit \/\/depot\/branch\/...\" to open the template with all the opened files under the given branch. \r\n- You can now pass in filters at the end of the commands. Just make sure you have a white space before the pipe. Ex: \r\n\r\n  PChanges -s pending | grep hari \r\n\r\n- I added ^X^P command line mapping which works like the \"E\" command but provides more flexibility. I also added ^X^I command line mapping for list windows (such as PF changes), which inserts the current item name on to the command line. Try them, they are very useful. \r\n- New commands for clients, labels windows to create a new item from the current item as a template (type P). \r\n- In the filelist windows, you can now press p to print the current file and S to sync to the current file. \r\n- Another major change is improved command line parsing. \r\n- Also the syntax highlighting has been improved to cover more cases.","package":"perforce-1.3.zip","4":"perforce-1.3.zip","src_id":"793","5":"793","creation_date":"1018640981","6":"1018640981"},{"0":"240","vim_version":"6.0","1":"6.0","script_version":"1.2.2","2":"1.2.2","version_comment":"Earlier, I have uploaded a wrong file as a zip file, I apologize for the mistake. I have deleted the old upload and am trying again.\r\n\r\nThis is just a minor patch release. Added useful WQ command which is same as the W command but will also quit the window if there is no error. Speeds up making changes to labels, jobs etc. You might still want to use W for submits, as you can copy the output into your integration plans or something like that. Also I made a typo in my previous release notes about the variable name for passing default diff options. The correct name is g:p4DefaultDiffOptions. Please use the latest version of genutils.vim which fixes a typo resulting in an error message while quitting help windows.","3":"Earlier, I have uploaded a wrong file as a zip file, I apologize for the mistake. I have deleted the old upload and am trying again.\r\n\r\nThis is just a minor patch release. Added useful WQ command which is same as the W command but will also quit the window if there is no error. Speeds up making changes to labels, jobs etc. You might still want to use W for submits, as you can copy the output into your integration plans or something like that. Also I made a typo in my previous release notes about the variable name for passing default diff options. The correct name is g:p4DefaultDiffOptions. Please use the latest version of genutils.vim which fixes a typo resulting in an error message while quitting help windows.","package":"perforce-1.2.2.zip","4":"perforce-1.2.2.zip","src_id":"746","5":"746","creation_date":"1017741911","6":"1017741911"},{"0":"240","vim_version":"6.0","1":"6.0","script_version":"1.2.0","2":"1.2.0","version_comment":"- Perforce help window is now much better. It reuses the same window for all the help commands and maximizes too like the vim built-in window. It even restores the windows when you quit the help. Also navigating in the help window is much better as the cursor positions are remembered.\r\n- New command: PJobspec\r\n- g:p4DefaultChangesSize to pass in default diff options to all the diff operations. Set it to '-dc' to get diff with context.\r\n- Renamed g:p4DefaultChangesSize to g:p4DefaultListSize. This is now used even for jobs command.\r\n- g:p4MaxLinesInDialog to limit the number of lines that should be shown in the dialogs. Commands that normally show dialogs (such as PE) open a new window if this limit is exceeded. This avoids showing too many lines in the dialogs (such as PF edit ...)\r\n- Fixed labelsync command.\r\n- Fixed the delete in the list view. Now pressing D in the labels, changes etc. works.\r\n- <SHOW DIFFS> option on the describe window. Pressing <Enter> on this line expands it to show diff.\r\n- Some basic formatting options in the edit windows.\r\n- You need the 1.0.19 version of genutils.vim","3":"- Perforce help window is now much better. It reuses the same window for all the help commands and maximizes too like the vim built-in window. It even restores the windows when you quit the help. Also navigating in the help window is much better as the cursor positions are remembered.\r\n- New command: PJobspec\r\n- g:p4DefaultChangesSize to pass in default diff options to all the diff operations. Set it to '-dc' to get diff with context.\r\n- Renamed g:p4DefaultChangesSize to g:p4DefaultListSize. This is now used even for jobs command.\r\n- g:p4MaxLinesInDialog to limit the number of lines that should be shown in the dialogs. Commands that normally show dialogs (such as PE) open a new window if this limit is exceeded. This avoids showing too many lines in the dialogs (such as PF edit ...)\r\n- Fixed labelsync command.\r\n- Fixed the delete in the list view. Now pressing D in the labels, changes etc. works.\r\n- <SHOW DIFFS> option on the describe window. Pressing <Enter> on this line expands it to show diff.\r\n- Some basic formatting options in the edit windows.\r\n- You need the 1.0.19 version of genutils.vim","package":"perforce-1.2.0.zip","4":"perforce-1.2.0.zip","src_id":"719","5":"719","creation_date":"1017171951","6":"1017171951"},{"0":"240","vim_version":"6.0","1":"6.0","script_version":"1.1.17","2":"1.1.17","version_comment":"Fixed it to work on Unix, thanks to Kevin McCarthy for reporting the problem and a solution. I also added a basic syntax highlighting for the perforce windows (not complete yet). Extract the perforce.zip in your runtime directory.","3":"Fixed it to work on Unix, thanks to Kevin McCarthy for reporting the problem and a solution. I also added a basic syntax highlighting for the perforce windows (not complete yet). Extract the perforce.zip in your runtime directory.","package":"perforce-1.1.17.zip","4":"perforce-1.1.17.zip","src_id":"702","5":"702","creation_date":"1016650631","6":"1016650631"},{"0":"240","vim_version":"6.0","1":"6.0","script_version":"1.1.15","2":"1.1.15","version_comment":"Minor patch release. Fixed PLabels command. Now O in PChanges correctly edits the current change instead of showing the opened list. The opened list can be viewed by using the o (small case) command. Updated the usage header in the file.","3":"Minor patch release. Fixed PLabels command. Now O in PChanges correctly edits the current change instead of showing the opened list. The opened list can be viewed by using the o (small case) command. Updated the usage header in the file.","package":"perforce.vim","4":"perforce.vim","src_id":"696","5":"696","creation_date":"1016531323","6":"1016531323"},{"0":"240","vim_version":"6.0","1":"6.0","script_version":"1.1.14","2":"1.1.14","version_comment":"More featured, more robust, with more predictable results. Lots of bugs have been fixed. Now, a command executed through PF or its shortcut are identical, so no more surprises (PF change and PChange are same). Thanks for the suggestion, Man. The code is also much more cleaner now. I have also improved the help header in the file, so read the first few lines for a good overview of the script's capabilities.","3":"More featured, more robust, with more predictable results. Lots of bugs have been fixed. Now, a command executed through PF or its shortcut are identical, so no more surprises (PF change and PChange are same). Thanks for the suggestion, Man. The code is also much more cleaner now. I have also improved the help header in the file, so read the first few lines for a good overview of the script's capabilities.","package":"perforce.vim","4":"perforce.vim","src_id":"690","5":"690","creation_date":"1016405124","6":"1016405124"},{"0":"240","vim_version":"6.0","1":"6.0","script_version":"1.1.8","2":"1.1.8","version_comment":"Initial upload","3":"Initial upload","package":"perforce.vim","4":"perforce.vim","src_id":"667","5":"667","creation_date":"1015605333","6":"1015605333"}]},"239":{"script_id":"239","0":"239","script_name":"Visual Mapping Maker","1":"Visual Mapping Maker","script_type":"utility","2":"utility","summary":"Create a mapping for the visual selected block","3":"Create a mapping for the visual selected block","description":"well ... write something like that :\r\n\r\nif(|)\r\n{\r\n\r\n}\r\n\r\nSelect it in visual mode, type ',t' and it will replace the block by the equivalent mapping (placing the cursor at the place of the underscore)\r\n\r\nfeedbacks and bug reports would be very nice","4":"well ... write something like that :\r\n\r\nif(|)\r\n{\r\n\r\n}\r\n\r\nSelect it in visual mode, type ',t' and it will replace the block by the equivalent mapping (placing the cursor at the place of the underscore)\r\n\r\nfeedbacks and bug reports would be very nice","install_details":"- copy the file in plugin directory.\r\n- be sure 'nocompatible' is set\r\n-  You can define :\r\n--> g:VMM_directory (directory where the macros are stored)\r\n--> g:VMM_file (file where the macros are stored)\r\n--> g:VMM_cursor (default cursor symbol)","5":"- copy the file in plugin directory.\r\n- be sure 'nocompatible' is set\r\n-  You can define :\r\n--> g:VMM_directory (directory where the macros are stored)\r\n--> g:VMM_file (file where the macros are stored)\r\n--> g:VMM_cursor (default cursor symbol)","first_name":"Marc","6":"Marc","last_name":"Chantreux","7":"Chantreux","releases":[{"0":"239","vim_version":"6.0","1":"6.0","script_version":"0.0.1","2":"0.0.1","version_comment":"Initial upload","3":"Initial upload","package":"vmm.vim","4":"vmm.vim","src_id":"662","5":"662","creation_date":"1015549717","6":"1015549717"}]},"238":{"script_id":"238","0":"238","script_name":"Hex Output","1":"Hex Output","script_type":"utility","2":"utility","summary":"Output a number as HEX","3":"Output a number as HEX","description":"Function to output a number as HEX\r\n\r\necho HexOut( 255)\r\n should output 'ff'","4":"Function to output a number as HEX\r\n\r\necho HexOut( 255)\r\n should output 'ff'","install_details":"Source it\r\n","5":"Source it\r\n","first_name":"Michael","6":"Michael","last_name":"Geddes","7":"Geddes","releases":[{"0":"238","vim_version":"5.7","1":"5.7","script_version":"0.0.1","2":"0.0.1","version_comment":"Initial upload","3":"Initial upload","package":"hex.vim","4":"hex.vim","src_id":"661","5":"661","creation_date":"1015539582","6":"1015539582"}]},"237":{"script_id":"237","0":"237","script_name":"Michael's Standard Settings","1":"Michael's Standard Settings","script_type":"utility","2":"utility","summary":"Some standard 'vimrc' settings & mappings that I use","3":"Some standard 'vimrc' settings & mappings that I use","description":"Here are some standard vimrc settings that I use.  Mostly they are pretty well commented.\r\nThey are intended as a springboard - most serious users will be beyond this. ","4":"Here are some standard vimrc settings that I use.  Mostly they are pretty well commented.\r\nThey are intended as a springboard - most serious users will be beyond this. ","install_details":"source from _vimrc \/ use parts to form your _vimrc","5":"source from _vimrc \/ use parts to form your _vimrc","first_name":"Michael","6":"Michael","last_name":"Geddes","7":"Geddes","releases":[{"0":"237","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"standard.vim","4":"standard.vim","src_id":"660","5":"660","creation_date":"1015518959","6":"1015518959"}]},"236":{"script_id":"236","0":"236","script_name":"SourceSafe Integration","1":"SourceSafe Integration","script_type":"utility","2":"utility","summary":"Fairly complete file-based SourceSafe Integration","3":"Fairly complete file-based SourceSafe Integration","description":"This package is now deprecated.  Use Source Control  ( vimscript #770 ) instead.\r\n","4":"This package is now deprecated.  Use Source Control  ( vimscript #770 ) instead.\r\n","install_details":"Use as Plugin or source from _vimrc.\r\nDon't forget to add a '.project' file containing the sourcesafe project you are working with in the physical directory where your project is.","5":"Use as Plugin or source from _vimrc.\r\nDon't forget to add a '.project' file containing the sourcesafe project you are working with in the physical directory where your project is.","first_name":"Michael","6":"Michael","last_name":"Geddes","7":"Geddes","releases":[{"0":"236","vim_version":"6.0","1":"6.0","script_version":"1.16","2":"1.16","version_comment":"- Use 'cat' if &shell contains 'sh'\r\n- Explain $SSDIR & #include in doco.\r\nFixes for William D. Bartholomew\r\n- Add ssDeployFile for the ability to deploy a file by default instead of a directory\r\n- Fix space in historybuffer temp name.\r\n","3":"- Use 'cat' if &shell contains 'sh'\r\n- Explain $SSDIR & #include in doco.\r\nFixes for William D. Bartholomew\r\n- Add ssDeployFile for the ability to deploy a file by default instead of a directory\r\n- Fix space in historybuffer temp name.\r\n","package":"srcsafe.vim","4":"srcsafe.vim","src_id":"2195","5":"2195","creation_date":"1059605209","6":"1059605209"},{"0":"236","vim_version":"6.0","1":"6.0","script_version":"1.14","2":"1.14","version_comment":" - Fix up system call with $VIMRUNTIME containing spaces. -Zak Beck\r\n - Make Get prompt to overwrite a read-only file.\r\n - Remove calls to ShortName where possible. (VSS shortname is not\r\n   always the same as M$oft shortname anyway!)\r\n - Prevent Diff against project - causes wacky behaviour.\r\n","3":" - Fix up system call with $VIMRUNTIME containing spaces. -Zak Beck\r\n - Make Get prompt to overwrite a read-only file.\r\n - Remove calls to ShortName where possible. (VSS shortname is not\r\n   always the same as M$oft shortname anyway!)\r\n - Prevent Diff against project - causes wacky behaviour.\r\n","package":"srcsafe.vim","4":"srcsafe.vim","src_id":"1595","5":"1595","creation_date":"1041437234","6":"1041437234"},{"0":"236","vim_version":"6.0","1":"6.0","script_version":"1.13","2":"1.13","version_comment":"Add interactive mode for answering multiple questions.\r\nFix up checking of modified status & automatic reloading of status's\r\n","3":"Add interactive mode for answering multiple questions.\r\nFix up checking of modified status & automatic reloading of status's\r\n","package":"srcsafe.vim","4":"srcsafe.vim","src_id":"1367","5":"1367","creation_date":"1036348777","6":"1036348777"}]},"235":{"script_id":"235","0":"235","script_name":"Naught 'n' crosses","1":"Naught 'n' crosses","script_type":"game","2":"game","summary":"Dumb Naught and crosses games","3":"Dumb Naught and crosses games","description":"Naught and Crosses game inside VIM against the (dumb) computer.\r\nIf you like games, see also the Tetris vimscript#172 and the Sokoban vimscript#211","4":"Naught and Crosses game inside VIM against the (dumb) computer.\r\nIf you like games, see also the Tetris vimscript#172 and the Sokoban vimscript#211","install_details":"Drop it into your plugin dir, and press\r\n<Leader>xo (if you don't know, what is leader, press \\xo)\r\nPress cursor keys or hjkl to move around, Space to put your sign!","5":"Drop it into your plugin dir, and press\r\n<Leader>xo (if you don't know, what is leader, press \\xo)\r\nPress cursor keys or hjkl to move around, Space to put your sign!","first_name":"Gergely","6":"Gergely","last_name":"Kontra","7":"Kontra","releases":[{"0":"235","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"X-and-O.vim","4":"X-and-O.vim","src_id":"652","5":"652","creation_date":"1015416264","6":"1015416264"}]},"234":{"script_id":"234","0":"234","script_name":"std_c.zip","1":"std_c.zip","script_type":"syntax","2":"syntax","summary":"A Standard C syntax file.","3":"A Standard C syntax file.","description":"This C syntax file is to help developing portable Standard C code.  That is C code that has to be able to compile on many different compilers.  The default is to highlight C89 C code, but it can be configured to allow or flag as an error C94 and C99 language features (types, constants, etc.)\r\n\r\nAdditional non-standard C features can be allowed - C++ comments, GNU C keywords, $ in identitfiers for VMS C, etc.\r\n\r\nThe syntax file also has the following benefits:\r\n\r\no more language elements highlighted (e.g. function and identifier names)\r\no more syntax errors highlighted, and\r\no better highlighting of macros.\r\n\r\nDetails of all configuration options are documented in the supplied help file.\r\n\r\nMore detail can be found at http:\/\/www.eandem.co.uk\/mrw\/vim\/syntax\/index.html#ansic","4":"This C syntax file is to help developing portable Standard C code.  That is C code that has to be able to compile on many different compilers.  The default is to highlight C89 C code, but it can be configured to allow or flag as an error C94 and C99 language features (types, constants, etc.)\r\n\r\nAdditional non-standard C features can be allowed - C++ comments, GNU C keywords, $ in identitfiers for VMS C, etc.\r\n\r\nThe syntax file also has the following benefits:\r\n\r\no more language elements highlighted (e.g. function and identifier names)\r\no more syntax errors highlighted, and\r\no better highlighting of macros.\r\n\r\nDetails of all configuration options are documented in the supplied help file.\r\n\r\nMore detail can be found at http:\/\/www.eandem.co.uk\/mrw\/vim\/syntax\/index.html#ansic","install_details":"Download the zip file and expand into your runtime path using the directory paths included.","5":"Download the zip file and expand into your runtime path using the directory paths included.","first_name":"Mike","6":"Mike","last_name":"Williams","7":"Williams","releases":[{"0":"234","vim_version":"7.0","1":"7.0","script_version":"12.5","2":"12.5","version_comment":"Misc updates:\r\no Add support for syntax based folding.\r\no Add VIM7 spell group to comments and strings.\r\no Braces within parentheses no longer highlighted as an error (controllable).\r\no Add missing C99 printf float format specifier F.\r\no Doc updated for new configuration options.","3":"Misc updates:\r\no Add support for syntax based folding.\r\no Add VIM7 spell group to comments and strings.\r\no Braces within parentheses no longer highlighted as an error (controllable).\r\no Add missing C99 printf float format specifier F.\r\no Doc updated for new configuration options.","package":"std_c.zip","4":"std_c.zip","src_id":"5856","5":"5856","creation_date":"1151119175","6":"1151119175"},{"0":"234","vim_version":"6.0","1":"6.0","script_version":"11.2","2":"11.2","version_comment":"Bug fixes for nested comments and system header include statements.","3":"Bug fixes for nested comments and system header include statements.","package":"std_c.zip","4":"std_c.zip","src_id":"3307","5":"3307","creation_date":"1091928301","6":"1091928301"},{"0":"234","vim_version":"6.0","1":"6.0","script_version":"10.8","2":"10.8","version_comment":"Correct highlighting of #pragma and #warn[ing] pp directives. Minor fix to correct handling of '-' in sscanf() scanlists when there are the last character.","3":"Correct highlighting of #pragma and #warn[ing] pp directives. Minor fix to correct handling of '-' in sscanf() scanlists when there are the last character.","package":"std_c.zip","4":"std_c.zip","src_id":"2293","5":"2293","creation_date":"1062567162","6":"1062567162"},{"0":"234","vim_version":"6.0","1":"6.0","script_version":"10.5","2":"10.5","version_comment":"Added following:\r\no correct highlighting of digraphs in tokens if enabled\r\no C++ comments can have the line continuation character - \\ !!!\r\no Fixed bug in highlighting nested array bracketing, and\r\no Change invalid token ~= from operator highlight to an error.","3":"Added following:\r\no correct highlighting of digraphs in tokens if enabled\r\no C++ comments can have the line continuation character - \\ !!!\r\no Fixed bug in highlighting nested array bracketing, and\r\no Change invalid token ~= from operator highlight to an error.","package":"std_c.zip","4":"std_c.zip","src_id":"2045","5":"2045","creation_date":"1054791209","6":"1054791209"}]},"233":{"script_id":"233","0":"233","script_name":"print_bw.zip","1":"print_bw.zip","script_type":"color scheme","2":"color scheme","summary":"Highlight scheme for black and white only printing.","3":"Highlight scheme for black and white only printing.","description":"This colorscheme is just black and white but uses the font attributes bold, italic, and underline.  This allows printing of highlighted files on black and white printers where shades of gray can be hard to read.  On color printers it also means you don't use up the more expensive colored inks.\r\n\r\nThe colorscheme is meant to be used just when printing.  Change colorscheme to print_bw, print, and then change back to your prefered scheme.  This could be done via a map or a script I guess.\r\n\r\nThe most recent version is available from the Bitbucket repo: https:\/\/bitbucket.org\/MrDubya\/print_bw","4":"This colorscheme is just black and white but uses the font attributes bold, italic, and underline.  This allows printing of highlighted files on black and white printers where shades of gray can be hard to read.  On color printers it also means you don't use up the more expensive colored inks.\r\n\r\nThe colorscheme is meant to be used just when printing.  Change colorscheme to print_bw, print, and then change back to your prefered scheme.  This could be done via a map or a script I guess.\r\n\r\nThe most recent version is available from the Bitbucket repo: https:\/\/bitbucket.org\/MrDubya\/print_bw","install_details":"Either Download file into your colors directory or use a VIM plugin manager and clone the Bitbucket repo.","5":"Either Download file into your colors directory or use a VIM plugin manager and clone the Bitbucket repo.","first_name":"Mike","6":"Mike","last_name":"Williams","7":"Williams","releases":[{"0":"233","vim_version":"6.0","1":"6.0","script_version":"1.1a","2":"1.1a","version_comment":"Added License and white space clean up.","3":"Added License and white space clean up.","package":"print_bw.vim","4":"print_bw.vim","src_id":"23102","5":"23102","creation_date":"1427624117","6":"1427624117"}]},"232":{"script_id":"232","0":"232","script_name":"spell.vim","1":"spell.vim","script_type":"utility","2":"utility","summary":"Vim 'spell' utility plugin","3":"Vim 'spell' utility plugin","description":"\r\nVim plugin for using the 'spell' Unix utility.  Provides commands to spell\r\ncheck the current buffer, or a range of lines in the current buffer, current\r\nword or a supplied string and to highlight misspelled words.  This plugin\r\nprovides the functionality similar to that provided by the emacs spell.el\r\nscript.\r\n\r\nThis plugin provides the following commands: \r\n\r\n   1. Spell\r\n      Spell check lines in the current buffer.  The default behavior is to\r\n      spell check the entire buffer. You can specify an ex command-line\r\n      range to spell check only lines in that range. If a word is\r\n      misspelled, you will be prompted to enter the correct spelling for the\r\n      word.  If you enter the correct spelling, then you will be prompted\r\n      for replacing every occurrence of that word in the current buffer.  If\r\n      you press just enter, then the word will be skipped.  If you press\r\n      <Esc>, the spell check will be stopped. \r\n\r\n   2. SpellWord \r\n      Check the spelling of the current word under the cursor. If the word\r\n      is misspelled, you will be prompted for the correct spelling.  If you\r\n      enter the correct spelling, you will be prompted for replacing every\r\n      occurrence of that word in the current buffer.  If you press just\r\n      enter, then the word will be skipped. \r\n\r\n   3. SpellString <string> \r\n      Check the spelling of the supplied string.  All the misspelled words\r\n      in the string will be displayed. \r\n\r\n   4. SpellHighlight\r\n      Highlight all the misspelled words in the current buffer. This command\r\n      also takes a range of lines.\r\n\r\n   5. SpellHighlightClear\r\n      Clear the highlighting for the misspelled words.\r\n\r\nThe 'spell' utility only checks the spelling and will not provide the \r\nalternatives (correct spelling) for a word.  As this plugin depends on the \r\n'spell' utility, you will not get the correct spelling for a word.  You will \r\nonly know whether a word is spelled correctly or not.","4":"\r\nVim plugin for using the 'spell' Unix utility.  Provides commands to spell\r\ncheck the current buffer, or a range of lines in the current buffer, current\r\nword or a supplied string and to highlight misspelled words.  This plugin\r\nprovides the functionality similar to that provided by the emacs spell.el\r\nscript.\r\n\r\nThis plugin provides the following commands: \r\n\r\n   1. Spell\r\n      Spell check lines in the current buffer.  The default behavior is to\r\n      spell check the entire buffer. You can specify an ex command-line\r\n      range to spell check only lines in that range. If a word is\r\n      misspelled, you will be prompted to enter the correct spelling for the\r\n      word.  If you enter the correct spelling, then you will be prompted\r\n      for replacing every occurrence of that word in the current buffer.  If\r\n      you press just enter, then the word will be skipped.  If you press\r\n      <Esc>, the spell check will be stopped. \r\n\r\n   2. SpellWord \r\n      Check the spelling of the current word under the cursor. If the word\r\n      is misspelled, you will be prompted for the correct spelling.  If you\r\n      enter the correct spelling, you will be prompted for replacing every\r\n      occurrence of that word in the current buffer.  If you press just\r\n      enter, then the word will be skipped. \r\n\r\n   3. SpellString <string> \r\n      Check the spelling of the supplied string.  All the misspelled words\r\n      in the string will be displayed. \r\n\r\n   4. SpellHighlight\r\n      Highlight all the misspelled words in the current buffer. This command\r\n      also takes a range of lines.\r\n\r\n   5. SpellHighlightClear\r\n      Clear the highlighting for the misspelled words.\r\n\r\nThe 'spell' utility only checks the spelling and will not provide the \r\nalternatives (correct spelling) for a word.  As this plugin depends on the \r\n'spell' utility, you will not get the correct spelling for a word.  You will \r\nonly know whether a word is spelled correctly or not.","install_details":"1. Copy the spell.vim script to the .vim\/plugin directory.  Refer to \r\n   'help add-plugin', 'help add-global-plugin' and 'help runtimepath' for \r\n   more details. \r\n2. Modify the s:SpellPath variable, defined at the top of the script,\r\n   to point to the spell utility path. \r\n3. Restart Vim.\r\n\r\n","5":"1. Copy the spell.vim script to the .vim\/plugin directory.  Refer to \r\n   'help add-plugin', 'help add-global-plugin' and 'help runtimepath' for \r\n   more details. \r\n2. Modify the s:SpellPath variable, defined at the top of the script,\r\n   to point to the spell utility path. \r\n3. Restart Vim.\r\n\r\n","first_name":"Yegappan","6":"Yegappan","last_name":"Lakshmanan","7":"Lakshmanan","releases":[{"0":"232","vim_version":"6.0","1":"6.0","script_version":"1.2","2":"1.2","version_comment":"Updated the range (of lines) handling. Removed the dependancy on the echo and cat commands.","3":"Updated the range (of lines) handling. Removed the dependancy on the echo and cat commands.","package":"spell.vim","4":"spell.vim","src_id":"4163","5":"4163","creation_date":"1113421125","6":"1113421125"},{"0":"232","vim_version":"6.0","1":"6.0","script_version":"1.1","2":"1.1","version_comment":"Added script command description in the comments.","3":"Added script command description in the comments.","package":"spell.vim","4":"spell.vim","src_id":"645","5":"645","creation_date":"1014733247","6":"1014733247"}]},"231":{"script_id":"231","0":"231","script_name":"Smart Tabs","1":"Smart Tabs","script_type":"utility","2":"utility","summary":"Use tabs for indent, spaces for alignment","3":"Use tabs for indent, spaces for alignment","description":"There are many different arguments about tabs and stuff.  My current personal preference is a choice of tabbing that is independent of anybody\\'s viewing settings.  \r\n\r\nFor the beginning of the line, this means we can use <tabs> which will expand whatever the reader wants it to.  Trying to line up tabs at the end of the line is a little trickier, and making a few assumptions, my preference is to use spaces there.\r\n\r\nThis script allows you to use your normal tab settings for the beginning of the line, and have tabs expanded as spaces anywhere else.  This effectively distinguishes 'indent' from 'alignment'.  \r\n\r\n<tab>  Uses editor tab settings to insert a tab at the beginning of the line (before the first non-space character), and inserts spaces otherwise.\r\n<BS>  Uses editor tab settings to delete tabs or 'expanded' tabs ala smarttab\r\n\r\n :RetabIndent[!] [tabstop]\r\n    This is similar to the :retab command, with the exception that it  affects all and only whitespace at the start of the line, changing it to suit your current (or new) tabstop and expandtab setting.  With the bang (!) at the end, the command also strips trailing  whitespace.\r\n\r\nCAUTION: After 1.1, this is no longer a filetype plugin by default ( set g:ctab_filetype_maps=1 to override)\r\n\r\nUsing spaces for alignment of code under unmatched brackets is now supported.","4":"There are many different arguments about tabs and stuff.  My current personal preference is a choice of tabbing that is independent of anybody\\'s viewing settings.  \r\n\r\nFor the beginning of the line, this means we can use <tabs> which will expand whatever the reader wants it to.  Trying to line up tabs at the end of the line is a little trickier, and making a few assumptions, my preference is to use spaces there.\r\n\r\nThis script allows you to use your normal tab settings for the beginning of the line, and have tabs expanded as spaces anywhere else.  This effectively distinguishes 'indent' from 'alignment'.  \r\n\r\n<tab>  Uses editor tab settings to insert a tab at the beginning of the line (before the first non-space character), and inserts spaces otherwise.\r\n<BS>  Uses editor tab settings to delete tabs or 'expanded' tabs ala smarttab\r\n\r\n :RetabIndent[!] [tabstop]\r\n    This is similar to the :retab command, with the exception that it  affects all and only whitespace at the start of the line, changing it to suit your current (or new) tabstop and expandtab setting.  With the bang (!) at the end, the command also strips trailing  whitespace.\r\n\r\nCAUTION: After 1.1, this is no longer a filetype plugin by default ( set g:ctab_filetype_maps=1 to override)\r\n\r\nUsing spaces for alignment of code under unmatched brackets is now supported.","install_details":"Pre 1.1:  Use as an ftplugin, especially for c, cpp, idl files.  By this, I mean place the script in (say) the macros directory, and then source it from a ftplugin for c, cpp or idl (~\/.vim\/ftplugin\/c.vim).\r\n>= 1.1 :  Use as a general plugin.  (Doesn't include <m-;> mappings)","5":"Pre 1.1:  Use as an ftplugin, especially for c, cpp, idl files.  By this, I mean place the script in (say) the macros directory, and then source it from a ftplugin for c, cpp or idl (~\/.vim\/ftplugin\/c.vim).\r\n>= 1.1 :  Use as a general plugin.  (Doesn't include <m-;> mappings)","first_name":"Michael","6":"Michael","last_name":"Geddes","7":"Geddes","releases":[{"0":"231","vim_version":"7.0","1":"7.0","script_version":"2.6","2":"2.6","version_comment":"Fix issue with alignment not disappearing","3":"Fix issue with alignment not disappearing","package":"ctab.vim","4":"ctab.vim","src_id":"14989","5":"14989","creation_date":"1297204836","6":"1297204836"},{"0":"231","vim_version":"7.0","1":"7.0","script_version":"2.5","2":"2.5","version_comment":"Fixes an issue with aligning when pressing <CR>","3":"Fixes an issue with aligning when pressing <CR>","package":"ctab.vim","4":"ctab.vim","src_id":"14152","5":"14152","creation_date":"1288480583","6":"1288480583"},{"0":"231","vim_version":"7.0","1":"7.0","script_version":"2.4","2":"2.4","version_comment":"Bugfix","3":"Bugfix","package":"ctab.vim","4":"ctab.vim","src_id":"13650","5":"13650","creation_date":"1282556733","6":"1282556733"},{"0":"231","vim_version":"6.0","1":"6.0","script_version":"2.3","2":"2.3","version_comment":"- Fix (Gene Smith) for error with non C files\r\n- Add option for filetype maps\r\n- Allow for lisp indentation\r\n","3":"- Fix (Gene Smith) for error with non C files\r\n- Add option for filetype maps\r\n- Allow for lisp indentation\r\n","package":"ctab.vim","4":"ctab.vim","src_id":"12546","5":"12546","creation_date":"1267587601","6":"1267587601"},{"0":"231","vim_version":"6.0","1":"6.0","script_version":"2.1","2":"2.1","version_comment":"Small fix to equal operation","3":"Small fix to equal operation","package":"ctab.vim","4":"ctab.vim","src_id":"10726","5":"10726","creation_date":"1244073754","6":"1244073754"},{"0":"231","vim_version":"6.0","1":"6.0","script_version":"2.0","2":"2.0","version_comment":"Added support (after many requests) for using tabs to expand alignment for mismatched brackets etc.","3":"Added support (after many requests) for using tabs to expand alignment for mismatched brackets etc.","package":"ctab.vim","4":"ctab.vim","src_id":"10725","5":"10725","creation_date":"1244071175","6":"1244071175"},{"0":"231","vim_version":"6.0","1":"6.0","script_version":"1.4.1","2":"1.4.1","version_comment":"Changed to unix fileformat (thanks Peter)","3":"Changed to unix fileformat (thanks Peter)","package":"ctab.vim","4":"ctab.vim","src_id":"4664","5":"4664","creation_date":"1129008535","6":"1129008535"},{"0":"231","vim_version":"6.0","1":"6.0","script_version":"1.4","2":"1.4","version_comment":"Fixed Backspace tab being off by 1","3":"Fixed Backspace tab being off by 1","package":"ctab.vim","4":"ctab.vim","src_id":"2599","5":"2599","creation_date":"1071502096","6":"1071502096"},{"0":"231","vim_version":"6.0","1":"6.0","script_version":"1.3","2":"1.3","version_comment":"1.1: - Added support for backspacing over spaced tabs \\\\\\'smarttab\\\\\\' style\r\n     - Clean up the look of it by blanking the :call\r\n     - No longer a \\\\\\'filetype\\\\\\' plugin by default.\r\n1.2: - Interactions with \\\\\\'smarttab\\\\\\' were causing problems. Now fall back to\r\n       vim\\\\\\'s \\\\\\'smarttab\\\\\\' setting when inserting \\\\\\'indent\\\\\\' tabs.\r\n     - Fixed compat with digraphs (which were getting swallowed)\r\n     - Made <BS> mapping work with the \\\\\\'filetype\\\\\\' plugin mode.\r\n     - Make CTabAlignTo() public.\r\n1.3: - Fix removing trailing spaces with RetabIndent! which was causing\r\n       initial indents to disappear.\r\n\r\n","3":"1.1: - Added support for backspacing over spaced tabs \\\\\\'smarttab\\\\\\' style\r\n     - Clean up the look of it by blanking the :call\r\n     - No longer a \\\\\\'filetype\\\\\\' plugin by default.\r\n1.2: - Interactions with \\\\\\'smarttab\\\\\\' were causing problems. Now fall back to\r\n       vim\\\\\\'s \\\\\\'smarttab\\\\\\' setting when inserting \\\\\\'indent\\\\\\' tabs.\r\n     - Fixed compat with digraphs (which were getting swallowed)\r\n     - Made <BS> mapping work with the \\\\\\'filetype\\\\\\' plugin mode.\r\n     - Make CTabAlignTo() public.\r\n1.3: - Fix removing trailing spaces with RetabIndent! which was causing\r\n       initial indents to disappear.\r\n\r\n","package":"ctab.vim","4":"ctab.vim","src_id":"2582","5":"2582","creation_date":"1070983767","6":"1070983767"},{"0":"231","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Added RetabIndent command - similar to :retab, but doesn't cause internal tabs to be modified. ","3":"Added RetabIndent command - similar to :retab, but doesn't cause internal tabs to be modified. ","package":"ctab.vim","4":"ctab.vim","src_id":"2567","5":"2567","creation_date":"1070809075","6":"1070809075"},{"0":"231","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"ctab.vim","4":"ctab.vim","src_id":"640","5":"640","creation_date":"1014662517","6":"1014662517"}]},"230":{"script_id":"230","0":"230","script_name":"Brace Complete for C\/C++","1":"Brace Complete for C\/C++","script_type":"ftplugin","2":"ftplugin","summary":"Adds braces after if, else, while","3":"Adds braces after if, else, while","description":"This is for use with the style of C\/C++ coding that says ALWAYS have braces after an if, and always start braces on a new line: \r\n\r\nif(a ==1 )\r\n{\r\n}\r\nelse\r\n{\r\n}\r\nit also changes\r\nelse{\r\nto \r\nelse\r\n{\r\n\r\nFor those whoe get lazy :) ","4":"This is for use with the style of C\/C++ coding that says ALWAYS have braces after an if, and always start braces on a new line: \r\n\r\nif(a ==1 )\r\n{\r\n}\r\nelse\r\n{\r\n}\r\nit also changes\r\nelse{\r\nto \r\nelse\r\n{\r\n\r\nFor those whoe get lazy :) ","install_details":"Add as ftplugin for cpp.","5":"Add as ftplugin for cpp.","first_name":"Michael","6":"Michael","last_name":"Geddes","7":"Geddes","releases":[{"0":"230","vim_version":"6.0","1":"6.0","script_version":"0.2","2":"0.2","version_comment":"Add <buffer> to maps","3":"Add <buffer> to maps","package":"complete.vim","4":"complete.vim","src_id":"639","5":"639","creation_date":"1014660708","6":"1014660708"},{"0":"230","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"complete.vim","4":"complete.vim","src_id":"638","5":"638","creation_date":"1014660425","6":"1014660425"}]},"229":{"script_id":"229","0":"229","script_name":"search-in-runtime","1":"search-in-runtime","script_type":"utility","2":"utility","summary":"Search files through the paths lists, and execute any command on them","3":"Search files through the paths lists, and execute any command on them","description":"This plugin extends the command 'runtime' (:h runtime) to execute any command (not only 'source') on files found in the '&runtimepath' option.\r\n\r\nIt defines the command \":SearchInRuntime\" which takes as a first parameter the command to execute and then the search patterns used to search files in the 'runtimepath' directories list.\r\n\r\nE.g. 1:\r\n     :SearchInRuntime! source here\/foo*.vim \r\nis equivalent to :\r\n     :runtime! here\/foo*.vim\r\n\r\nE.g. 2:\r\n     :silent exe 'SearchInRuntime 0r there\/that.'.&ft\r\nwill search 'runtimepath' list for the first file named \"that.<filetype>\" present in the directory \"there\", and inserts it in the current buffer. If no file is found, nothing is done.\r\n\r\nN.B.: The [!] (bang) character can be used to apply the command to all found files. Otherwise, 'SearchInRuntime' stops after the first file.\r\n\r\nSince the version 1.1 : \r\n(*) the 'verbose' option is supported :\r\n    >= 0 -> display when no file is found\r\n    >= 1 -> display the list of file found\r\n    >= 3 -> display the list of directories searched\r\n(*) ':SearchInPATH' : like ':SearchInRuntime', but with $PATH\r\n(*) ':SearchInVar' : works on any list of directories defined in a variable.\r\n(*) Contrary to ':runtime', the search can accept absolute paths, for instance :\r\n     :runtime! \/usr\/local\/share\/vim\/*.vim                           is not valid while\r\n     :SearchInRuntime source \/usr\/local\/share\/vim\/*.vim   is accepted.\r\n\r\nSince the version 1.5.:\r\n(*) The commands passed to the different :SearchIn* commands can accept any number of arguments before the names of the files found.To use them, add at the end of the :SearchIn* command: a pipe (' |0 ') and then the list of the other parameters. For instance:\r\n      :SearchInRuntime! grep plugin\/*foo*.vim |0 text\r\n    For every file name plugin\/*foo*.vim in the 'runtimepath', this will execute:\r\n      :grep text {path-to-the-file}\r\n\r\n(*) The commands passed to the different :SearchIn* commands can accept any number of arguments after the names of the files found. To use them, add at the end of the :SearchIn* command: a pipe (' | ') and then the list of the other parameters\r\n\r\n        :SearchInRuntime! Echo plugin\/*foo*.vim | final arguments\r\n    For every file name plugin\/*foo*.vim in the 'runtimepath', this will execute:\r\n        :Echo {path-to-the-file} final arguments\r\n\r\nSince Version 2.0.x:\r\n- Custom auto-completion added -- if vim supports it\r\n- New commands: :Split and :Vsplit to split open files found into &path\r\n\r\nSince Version 2.1.0:\r\n- new commands for vim7+ only: :GSplit and :GVSplit\r\n- overloaded mapping for vim7+ only: gf and CTRL-W_f\r\n- new mapping: glf that echoes the files in 'path' that match the pattern under the cursor\r\n\r\nGSplit, GVSplit, gf and CTRL-W_f permit to help the end-user to select a file among those matching a file-pattern (either given as parameter to the commands, or written under the cursor). If the selected file is already opened in a window, then that window is made the new active window -- this avoid to split-open the same file again and again.\r\n\r\nFull documentation available on:\r\n    https:\/\/github.com\/LucHermitte\/SearchInRuntime\r\nor within the vimball archive.","4":"This plugin extends the command 'runtime' (:h runtime) to execute any command (not only 'source') on files found in the '&runtimepath' option.\r\n\r\nIt defines the command \":SearchInRuntime\" which takes as a first parameter the command to execute and then the search patterns used to search files in the 'runtimepath' directories list.\r\n\r\nE.g. 1:\r\n     :SearchInRuntime! source here\/foo*.vim \r\nis equivalent to :\r\n     :runtime! here\/foo*.vim\r\n\r\nE.g. 2:\r\n     :silent exe 'SearchInRuntime 0r there\/that.'.&ft\r\nwill search 'runtimepath' list for the first file named \"that.<filetype>\" present in the directory \"there\", and inserts it in the current buffer. If no file is found, nothing is done.\r\n\r\nN.B.: The [!] (bang) character can be used to apply the command to all found files. Otherwise, 'SearchInRuntime' stops after the first file.\r\n\r\nSince the version 1.1 : \r\n(*) the 'verbose' option is supported :\r\n    >= 0 -> display when no file is found\r\n    >= 1 -> display the list of file found\r\n    >= 3 -> display the list of directories searched\r\n(*) ':SearchInPATH' : like ':SearchInRuntime', but with $PATH\r\n(*) ':SearchInVar' : works on any list of directories defined in a variable.\r\n(*) Contrary to ':runtime', the search can accept absolute paths, for instance :\r\n     :runtime! \/usr\/local\/share\/vim\/*.vim                           is not valid while\r\n     :SearchInRuntime source \/usr\/local\/share\/vim\/*.vim   is accepted.\r\n\r\nSince the version 1.5.:\r\n(*) The commands passed to the different :SearchIn* commands can accept any number of arguments before the names of the files found.To use them, add at the end of the :SearchIn* command: a pipe (' |0 ') and then the list of the other parameters. For instance:\r\n      :SearchInRuntime! grep plugin\/*foo*.vim |0 text\r\n    For every file name plugin\/*foo*.vim in the 'runtimepath', this will execute:\r\n      :grep text {path-to-the-file}\r\n\r\n(*) The commands passed to the different :SearchIn* commands can accept any number of arguments after the names of the files found. To use them, add at the end of the :SearchIn* command: a pipe (' | ') and then the list of the other parameters\r\n\r\n        :SearchInRuntime! Echo plugin\/*foo*.vim | final arguments\r\n    For every file name plugin\/*foo*.vim in the 'runtimepath', this will execute:\r\n        :Echo {path-to-the-file} final arguments\r\n\r\nSince Version 2.0.x:\r\n- Custom auto-completion added -- if vim supports it\r\n- New commands: :Split and :Vsplit to split open files found into &path\r\n\r\nSince Version 2.1.0:\r\n- new commands for vim7+ only: :GSplit and :GVSplit\r\n- overloaded mapping for vim7+ only: gf and CTRL-W_f\r\n- new mapping: glf that echoes the files in 'path' that match the pattern under the cursor\r\n\r\nGSplit, GVSplit, gf and CTRL-W_f permit to help the end-user to select a file among those matching a file-pattern (either given as parameter to the commands, or written under the cursor). If the selected file is already opened in a window, then that window is made the new active window -- this avoid to split-open the same file again and again.\r\n\r\nFull documentation available on:\r\n    https:\/\/github.com\/LucHermitte\/SearchInRuntime\r\nor within the vimball archive.","install_details":"Install search-in-runtime with vim-addon-manager, or get the latest release from https:\/\/github.com\/LucHermitte\/SearchInRuntime#2-installation","5":"Install search-in-runtime with vim-addon-manager, or get the latest release from https:\/\/github.com\/LucHermitte\/SearchInRuntime#2-installation","first_name":"Luc","6":"Luc","last_name":"Hermitte","7":"Hermitte","releases":[{"0":"229","vim_version":"6.0","1":"6.0","script_version":"2.1.3","2":"2.1.3","version_comment":"Bug fix: regression introduced on gf and <c-w>f","3":"Bug fix: regression introduced on gf and <c-w>f","package":"searchInRuntime.tar.gz","4":"searchInRuntime.tar.gz","src_id":"4988","5":"4988","creation_date":"1137501660","6":"1137501660"},{"0":"229","vim_version":"6.0","1":"6.0","script_version":"2.1.2","2":"2.1.2","version_comment":"* Various bug fixes for :G*split (paths withs spaces, UNC paths, URLs, absolute paths, ... ; factorisation of paths). \r\n* Possibility to choose the names of the \"Goto-Or-Split\" commands (:G*split).\r\n* New behavior for :G*split: we jump to the first matching window unless the command in banged ; in that latter case, the user is asked to choose the matching file to open\/jump-to.\r\n* All these modifications concern only Vim7+ as the corresponding feature is not supported on 6.x versions of Vim.","3":"* Various bug fixes for :G*split (paths withs spaces, UNC paths, URLs, absolute paths, ... ; factorisation of paths). \r\n* Possibility to choose the names of the \"Goto-Or-Split\" commands (:G*split).\r\n* New behavior for :G*split: we jump to the first matching window unless the command in banged ; in that latter case, the user is asked to choose the matching file to open\/jump-to.\r\n* All these modifications concern only Vim7+ as the corresponding feature is not supported on 6.x versions of Vim.","package":"searchInRuntime.tar.gz","4":"searchInRuntime.tar.gz","src_id":"4963","5":"4963","creation_date":"1137084781","6":"1137084781"},{"0":"229","vim_version":"6.0","1":"6.0","script_version":"2.1.0","2":"2.1.0","version_comment":"Two minor bugfixes. New commands and overridden mappings for vim7+: :GSplit, :GVSplit, gf, CTRL-W_f and glf. When several matching files can be found in 'path', the user is asked which one to open. If it is already opened in a window, that window becomes active.","3":"Two minor bugfixes. New commands and overridden mappings for vim7+: :GSplit, :GVSplit, gf, CTRL-W_f and glf. When several matching files can be found in 'path', the user is asked which one to open. If it is already opened in a window, that window becomes active.","package":"searchInRuntime.tar.gz","4":"searchInRuntime.tar.gz","src_id":"4891","5":"4891","creation_date":"1134404914","6":"1134404914"},{"0":"229","vim_version":"6.0","1":"6.0","script_version":"2.0.3","2":"2.0.3","version_comment":"Support for \"smart\" auto-completion added for each command from the plugin -- \"smart\" means: \"respect the parameter position\". New commands: :Sp and :Vsp that split open files found into &path ; and :Runtime, another wrapper for :runtime with auto-completion.","3":"Support for \"smart\" auto-completion added for each command from the plugin -- \"smart\" means: \"respect the parameter position\". New commands: :Sp and :Vsp that split open files found into &path ; and :Runtime, another wrapper for :runtime with auto-completion.","package":"searchInRuntime.tar.gz","4":"searchInRuntime.tar.gz","src_id":"4218","5":"4218","creation_date":"1114700158","6":"1114700158"},{"0":"229","vim_version":"6.0","1":"6.0","script_version":"1.6c","2":"1.6c","version_comment":"Bug fix for non-Windows users.","3":"Bug fix for non-Windows users.","package":"searchInRuntime.tar.gz","4":"searchInRuntime.tar.gz","src_id":"1875","5":"1875","creation_date":"1048961437","6":"1048961437"},{"0":"229","vim_version":"6.0","1":"6.0","script_version":"1.6","2":"1.6","version_comment":"Tarball containing the plugin and its documentation.","3":"Tarball containing the plugin and its documentation.","package":"searchInRuntime.tar.gz","4":"searchInRuntime.tar.gz","src_id":"1403","5":"1403","creation_date":"1037112091","6":"1037112091"},{"0":"229","vim_version":"6.0","1":"6.0","script_version":"1.6","2":"1.6","version_comment":"The :SearchIn* commands can pass any number of additional arguments to the \"inner\" command. SearchInENV changed in SearchInVar.","3":"The :SearchIn* commands can pass any number of additional arguments to the \"inner\" command. SearchInENV changed in SearchInVar.","package":"searchInRuntime.vim","4":"searchInRuntime.vim","src_id":"1383","5":"1383","creation_date":"1036654812","6":"1036654812"},{"0":"229","vim_version":"6.0","1":"6.0","script_version":"1.1","2":"1.1","version_comment":"Two more commands : ':SearchInENV' and ':SearchInPATH' ; '&verbose' is supported like with ':runtime'.","3":"Two more commands : ':SearchInENV' and ':SearchInPATH' ; '&verbose' is supported like with ':runtime'.","package":"searchInRuntime.vim","4":"searchInRuntime.vim","src_id":"757","5":"757","creation_date":"1017909316","6":"1017909316"},{"0":"229","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"searchInRuntime.vim","4":"searchInRuntime.vim","src_id":"637","5":"637","creation_date":"1014630715","6":"1014630715"}]},"228":{"script_id":"228","0":"228","script_name":"Expand Template","1":"Expand Template","script_type":"utility","2":"utility","summary":"Template expander.","3":"Template expander.","description":"This script is no longer supported. Use vimscript #1733 (aedit) instead.","4":"This script is no longer supported. Use vimscript #1733 (aedit) instead.","install_details":"","5":"","first_name":"Little","6":"Little","last_name":"Dragon","7":"Dragon","releases":[{"0":"228","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"expand_template.vim","4":"expand_template.vim","src_id":"635","5":"635","creation_date":"1014552977","6":"1014552977"}]},"227":{"script_id":"227","0":"227","script_name":"Brown","1":"Brown","script_type":"color scheme","2":"color scheme","summary":"Brown GUI color scheme.","3":"Brown GUI color scheme.","description":"A light brown colorscheme for GVIM.","4":"A light brown colorscheme for GVIM.","install_details":":so brown.vim or copy it in the vim runtime colors directory and use :colorscheme brown","5":":so brown.vim or copy it in the vim runtime colors directory and use :colorscheme brown","first_name":"Little","6":"Little","last_name":"Dragon","7":"Dragon","releases":[{"0":"227","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"brown.vim","4":"brown.vim","src_id":"633","5":"633","creation_date":"1014530848","6":"1014530848"}]},"226":{"script_id":"226","0":"226","script_name":"closeb","1":"closeb","script_type":"utility","2":"utility","summary":"Close complex brackets or tags","3":"Close complex brackets or tags","description":"This plugin closes complex brackets \/ tags.\r\nIt is an extended version of closetag, (http:\/\/vim.sourceforge.net\/scripts\/script.php?script_id=13)\r\n\r\nIt comes with configuration for closing XML\/SGML tags and LaTeX environments but is easily configured for other filetypes.\r\n\r\nClosing a bracket \/ tag also (optionally) inserts a newline and \/ or indentation, but only if the matching bracket \/ tag stood on a line of its own.\r\n\r\nIf, during scanning for the bracket \/ tag to close, mismatching brackets are found, they are optionally highlighted.\r\n\r\nA path function is provided, which displays all open tags. For example, this function may be used in the status line for a constant display of location in an XML file.\r\n","4":"This plugin closes complex brackets \/ tags.\r\nIt is an extended version of closetag, (http:\/\/vim.sourceforge.net\/scripts\/script.php?script_id=13)\r\n\r\nIt comes with configuration for closing XML\/SGML tags and LaTeX environments but is easily configured for other filetypes.\r\n\r\nClosing a bracket \/ tag also (optionally) inserts a newline and \/ or indentation, but only if the matching bracket \/ tag stood on a line of its own.\r\n\r\nIf, during scanning for the bracket \/ tag to close, mismatching brackets are found, they are optionally highlighted.\r\n\r\nA path function is provided, which displays all open tags. For example, this function may be used in the status line for a constant display of location in an XML file.\r\n","install_details":"Put this into your plugin directory ~\/.vim\/plugin.\r\nIt will map CTRL-_ to closing a tag in insert mode (as closetag.vim did). The :Path command displays the \"path\".\r\n","5":"Put this into your plugin directory ~\/.vim\/plugin.\r\nIt will map CTRL-_ to closing a tag in insert mode (as closetag.vim did). The :Path command displays the \"path\".\r\n","first_name":"Mark A.","6":"Mark A.","last_name":"Hillebrand","7":"Hillebrand","releases":[{"0":"226","vim_version":"6.0","1":"6.0","script_version":"0.2a","2":"0.2a","version_comment":"Commented out some debug code...","3":"Commented out some debug code...","package":"closeb.vim","4":"closeb.vim","src_id":"646","5":"646","creation_date":"1014768597","6":"1014768597"},{"0":"226","vim_version":"6.0","1":"6.0","script_version":"0.2","2":"0.2","version_comment":"This version now supports a new type of close, the \"middle close\". For XML\/SGML, it will close the tag and reopen the same tag (useful for list of tags); for LaTeX, it will insert \\item inside of {itemize}, {enumerate}, .. environments, just close otherwise.\r\n\r\nMiddle closes are invoke by the two-key sequence CTRL-\\ =\r\n","3":"This version now supports a new type of close, the \"middle close\". For XML\/SGML, it will close the tag and reopen the same tag (useful for list of tags); for LaTeX, it will insert \\item inside of {itemize}, {enumerate}, .. environments, just close otherwise.\r\n\r\nMiddle closes are invoke by the two-key sequence CTRL-\\ =\r\n","package":"closeb.vim","4":"closeb.vim","src_id":"630","5":"630","creation_date":"1014378967","6":"1014378967"},{"0":"226","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"closeb.vim","4":"closeb.vim","src_id":"629","5":"629","creation_date":"1014364606","6":"1014364606"}]},"225":{"script_id":"225","0":"225","script_name":"einstimer.vim","1":"einstimer.vim","script_type":"syntax","2":"syntax","summary":"Syntax file for IBM Einstimer tcl","3":"Syntax file for IBM Einstimer tcl","description":"This is a syntax file for IBM's Einstimer tcl language\r\n\r\nThe syntaxing can handle optional arguments and all their legal abbreviations.\r\nThe command names themselves, however, have to be spelled out completely.\r\nI haven't figured out a clean way of doing the command abbreviations.\r\n\r\nThis syntax file sources the standard tcl syntax file from the vim\r\nrelease to do most of the tcl stuff.  I have just added the language-specific\r\nextensions.  I'm not an expert in vim syntaxing, but they seem to work\r\nreasonably well.  Send comments and suggestions to:\r\n\r\npaulzimmer@zimmerdesignservices.com","4":"This is a syntax file for IBM's Einstimer tcl language\r\n\r\nThe syntaxing can handle optional arguments and all their legal abbreviations.\r\nThe command names themselves, however, have to be spelled out completely.\r\nI haven't figured out a clean way of doing the command abbreviations.\r\n\r\nThis syntax file sources the standard tcl syntax file from the vim\r\nrelease to do most of the tcl stuff.  I have just added the language-specific\r\nextensions.  I'm not an expert in vim syntaxing, but they seem to work\r\nreasonably well.  Send comments and suggestions to:\r\n\r\npaulzimmer@zimmerdesignservices.com","install_details":"see instructions for pt.vim","5":"see instructions for pt.vim","first_name":"Paul","6":"Paul","last_name":"Zimmer","7":"Zimmer","releases":[{"0":"225","vim_version":"6.0","1":"6.0","script_version":"6.2","2":"6.2","version_comment":"For ibm 11.1 tools!  Many other improvements as well.","3":"For ibm 11.1 tools!  Many other improvements as well.","package":"einsstd_abridged.tgz","4":"einsstd_abridged.tgz","src_id":"5926","5":"5926","creation_date":"1152194159","6":"1152194159"},{"0":"225","vim_version":"6.0","1":"6.0","script_version":"6.1","2":"6.1","version_comment":"Added README file to show different ways of hooking the script in.  I no longer have access to the Einstimer tool, so I can't do updates...","3":"Added README file to show different ways of hooking the script in.  I no longer have access to the Einstimer tool, so I can't do updates...","package":"eins.vim.tgz","4":"eins.vim.tgz","src_id":"3003","5":"3003","creation_date":"1083953911","6":"1083953911"},{"0":"225","vim_version":"6.0","1":"6.0","script_version":"6.1","2":"6.1","version_comment":"Compatible with vim 6.1","3":"Compatible with vim 6.1","package":"einstimer.vim.gz","4":"einstimer.vim.gz","src_id":"828","5":"828","creation_date":"1020182045","6":"1020182045"},{"0":"225","vim_version":"5.7","1":"5.7","script_version":"5.8","2":"5.8","version_comment":"Initial upload","3":"Initial upload","package":"einstimer.vim.gz","4":"einstimer.vim.gz","src_id":"627","5":"627","creation_date":"1014306209","6":"1014306209"}]},"224":{"script_id":"224","0":"224","script_name":"night.vim","1":"night.vim","script_type":"color scheme","2":"color scheme","summary":"Colorscheme with dark background.","3":"Colorscheme with dark background.","description":"If you want to update this file, please download rainbow.zip.\r\nhttp:\/\/www.vim.org\/script.php?script_id=463\r\n\r\nThis is colorscheme(GUI only).","4":"If you want to update this file, please download rainbow.zip.\r\nhttp:\/\/www.vim.org\/script.php?script_id=463\r\n\r\nThis is colorscheme(GUI only).","install_details":"Save as colos\/night.vim under 'runtimepath'","5":"Save as colos\/night.vim under 'runtimepath'","first_name":"Takeshi","6":"Takeshi","last_name":"Zeniya","7":"Zeniya","releases":[{"0":"224","vim_version":"6.0","1":"6.0","script_version":"2.0","2":"2.0","version_comment":"Change \"Statusline\" \"Folded\" ... etc","3":"Change \"Statusline\" \"Folded\" ... etc","package":"night.vim","4":"night.vim","src_id":"663","5":"663","creation_date":"1015567024","6":"1015567024"},{"0":"224","vim_version":"6.0","1":"6.0","script_version":"1.1","2":"1.1","version_comment":"Small changes.","3":"Small changes.","package":"night.vim","4":"night.vim","src_id":"628","5":"628","creation_date":"1014349642","6":"1014349642"},{"0":"224","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"night.vim","4":"night.vim","src_id":"624","5":"624","creation_date":"1014301808","6":"1014301808"}]},"223":{"script_id":"223","0":"223","script_name":"xl_tiv.vim","1":"xl_tiv.vim","script_type":"utility","2":"utility","summary":"Translate sequences of ampersand-pound-digits-semicolon in html source","3":"Translate sequences of ampersand-pound-digits-semicolon in html source","description":"Source for vimtip #217.\r\n\r\nI found a website *cough*Tivoli.com*cough* that likes to obfuscate some of its help file web pages using ampersand-pound-digits-semicolon instead of normal ascii.\u00c2\u00a0\u00c2\u00a0If you load the source with Vim (in Opera you can just designate Vim as your source viewing program), you can :so xl_tiv.vim to make it readable.\r\n","4":"Source for vimtip #217.\r\n\r\nI found a website *cough*Tivoli.com*cough* that likes to obfuscate some of its help file web pages using ampersand-pound-digits-semicolon instead of normal ascii.\u00c2\u00a0\u00c2\u00a0If you load the source with Vim (in Opera you can just designate Vim as your source viewing program), you can :so xl_tiv.vim to make it readable.\r\n","install_details":"Open an html file in Vim.  Source xl_tiv.vim.","5":"Open an html file in Vim.  Source xl_tiv.vim.","first_name":"Larry","6":"Larry","last_name":"Clapp","7":"Clapp","releases":[{"0":"223","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload.","3":"Initial upload.","package":"xl_tiv.vim","4":"xl_tiv.vim","src_id":"623","5":"623","creation_date":"1014296359","6":"1014296359"}]},"222":{"script_id":"222","0":"222","script_name":"mu-template","1":"mu-template","script_type":"utility","2":"utility","summary":"Mu template (fill-out forms, expression substitution)","3":"Mu template (fill-out forms, expression substitution)","description":"This is a micro-template file.\r\nTemplates should be in $VIMTEMPLATES directory.\r\nThe default is $VIM\/vimfiles\/template.\r\nTemplate files should be named template.&ft (&ft is the filetype)\r\nIf filetype is not known, template.unknown will be read.\r\nYou shouldn't modify the script (unless you have <C-J> mapped..). All customizing is inside the templates.\r\nYou can insert 'fields' to the template. With the chars '<<' and '>>'.\r\nEditing will be started at the first field in selectmode.\r\nYou can jump to the next field by pressing <C-J>\r\n(sorry <C-J> is remapped in normal, insert (and visual) mode)\r\nExpression evaluation:\r\nUse the \u00c2\u00a1 (press <m-!>) symbol to surround your expression.\r\nEg.: Creation date: \u00c2\u00a1strftime('%c')\u00c2\u00a1 \r\nThe template set is very limited, but you will get the idea, I hope.\r\n(At least I hope you can learn some programming tricks)\r\nFEEDBACK PLEASE!","4":"This is a micro-template file.\r\nTemplates should be in $VIMTEMPLATES directory.\r\nThe default is $VIM\/vimfiles\/template.\r\nTemplate files should be named template.&ft (&ft is the filetype)\r\nIf filetype is not known, template.unknown will be read.\r\nYou shouldn't modify the script (unless you have <C-J> mapped..). All customizing is inside the templates.\r\nYou can insert 'fields' to the template. With the chars '<<' and '>>'.\r\nEditing will be started at the first field in selectmode.\r\nYou can jump to the next field by pressing <C-J>\r\n(sorry <C-J> is remapped in normal, insert (and visual) mode)\r\nExpression evaluation:\r\nUse the \u00c2\u00a1 (press <m-!>) symbol to surround your expression.\r\nEg.: Creation date: \u00c2\u00a1strftime('%c')\u00c2\u00a1 \r\nThe template set is very limited, but you will get the idea, I hope.\r\n(At least I hope you can learn some programming tricks)\r\nFEEDBACK PLEASE!","install_details":"Unzip, copy to the right directory ($VIM\/vimfiles\/), customize templates.","5":"Unzip, copy to the right directory ($VIM\/vimfiles\/), customize templates.","first_name":"Gergely","6":"Gergely","last_name":"Kontra","7":"Kontra","releases":[{"0":"222","vim_version":"6.0","1":"6.0","script_version":"0.11","2":"0.11","version_comment":"Fixes, Luc Herminettes improvements:\r\nupside down ? for vim execution.\r\nHarmony with other mark-jump implementation :-)","3":"Fixes, Luc Herminettes improvements:\r\nupside down ? for vim execution.\r\nHarmony with other mark-jump implementation :-)","package":"mu-template.zip","4":"mu-template.zip","src_id":"649","5":"649","creation_date":"1014803275","6":"1014803275"},{"0":"222","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"mu-template.zip","4":"mu-template.zip","src_id":"618","5":"618","creation_date":"1014198616","6":"1014198616"}]},"221":{"script_id":"221","0":"221","script_name":"VIlisp.vim","1":"VIlisp.vim","script_type":"utility","2":"utility","summary":"Send Lisp code to a running Lisp interpreter","3":"Send Lisp code to a running Lisp interpreter","description":"New: 19 May 2008: See also http:\/\/theclapp.org\/blog\/posts\/intro_to_lw-vim-mode\/ about a partial vi-mode for Lispworks.\r\n\r\nNew: 1 May 2008: Interested users should check out LIMP at http:\/\/mikael.jansson.be\/hacking\/limp\/docs\/ and\/or vimscript#2219.  Among other improvements, it replaces funnel.pl with screen, which I've thought would be a good idea for a while now but never got around to implementing.\r\n\r\n---\r\n\r\nVIlisp.vim defines functions and key mappings to send Lisp code to a CMU Common Lisp process running in a separate terminal window.  VIlisp basically automates cut-and-paste from Vim to Lisp.  Vim writes to a FIFO created by a Perl script, funnel.pl.  Funnel takes input from Vim and the keyboard and sends it to Lisp.\r\n\r\nI use: Vim v6.3.71, CMU CL 19a-release-20040728 + minimal debian patches, and Perl 5.8.4.  funnel.pl requires the GNU Readline library (4.2 or higher), and Perl modules IO::Pty, Term::ReadLine, and Term::ReadLine::Gnu.  Developed on Debian \"sarge\" GNU\/Linux, kernel 2.6.6.  YMMV.\r\n\r\nfunnel.pl would probably work with any Lisp that will run in an xterm; just change how it exits Lisp; CMU CL uses \"(ext:quit)\".  With other minor alterations, it'd probably work with other scrolled-from-the-bottom interpreters (e.g. I've received reports of it working with Octave and R).\r\n\r\nInterested users should also see vimscript #165.  I haven't tried it, but from the description, it looks like it might fit the bill.\r\n\r\nAs of June 2002:\r\n\r\nVIlisp.vim also interfaces to your local copy of the Common Lisp HyperSpec (e.g. lookup \"defun\"), and does Lisp keyword lookups via an included Vim thesaurus file (e.g. expand \"with-\" into with-accessors, then with-compilation-unit, then with-condition-restarts, etc).\r\n\r\nSee the README for documentation.","4":"New: 19 May 2008: See also http:\/\/theclapp.org\/blog\/posts\/intro_to_lw-vim-mode\/ about a partial vi-mode for Lispworks.\r\n\r\nNew: 1 May 2008: Interested users should check out LIMP at http:\/\/mikael.jansson.be\/hacking\/limp\/docs\/ and\/or vimscript#2219.  Among other improvements, it replaces funnel.pl with screen, which I've thought would be a good idea for a while now but never got around to implementing.\r\n\r\n---\r\n\r\nVIlisp.vim defines functions and key mappings to send Lisp code to a CMU Common Lisp process running in a separate terminal window.  VIlisp basically automates cut-and-paste from Vim to Lisp.  Vim writes to a FIFO created by a Perl script, funnel.pl.  Funnel takes input from Vim and the keyboard and sends it to Lisp.\r\n\r\nI use: Vim v6.3.71, CMU CL 19a-release-20040728 + minimal debian patches, and Perl 5.8.4.  funnel.pl requires the GNU Readline library (4.2 or higher), and Perl modules IO::Pty, Term::ReadLine, and Term::ReadLine::Gnu.  Developed on Debian \"sarge\" GNU\/Linux, kernel 2.6.6.  YMMV.\r\n\r\nfunnel.pl would probably work with any Lisp that will run in an xterm; just change how it exits Lisp; CMU CL uses \"(ext:quit)\".  With other minor alterations, it'd probably work with other scrolled-from-the-bottom interpreters (e.g. I've received reports of it working with Octave and R).\r\n\r\nInterested users should also see vimscript #165.  I haven't tried it, but from the description, it looks like it might fit the bill.\r\n\r\nAs of June 2002:\r\n\r\nVIlisp.vim also interfaces to your local copy of the Common Lisp HyperSpec (e.g. lookup \"defun\"), and does Lisp keyword lookups via an included Vim thesaurus file (e.g. expand \"with-\" into with-accessors, then with-compilation-unit, then with-condition-restarts, etc).\r\n\r\nSee the README for documentation.","install_details":"Make sure you have GNU Readline (version 4.2 or higher) installed, Perl (at least version 5; I use 5.8.4), and the Perl GNU Readline module installed.\r\n\r\nPut this at an appropriate place in your ~\/.vimrc:\r\n\r\n    autocmd BufRead,BufNewFile *.lsp,*.lisp so ~\/path\/to\/VIlisp.vim\r\n\r\nThe VIlisp package includes a file called lisp-thesaurus.  Put it in the same directory as VIlisp.vim, and VIlisp.vim will find it.\r\n\r\nIn an Xterm, run\r\n\r\n    export PERL_RL=gnu                  # use GNU readline in funnel\r\n    perl funnel.pl $HOME\/.lisp-pipe lisp\r\n\r\nIn a different xterm, run e.g.\r\n\r\n    vim test.lisp\r\n\r\nSee the README for more extensive configuration information, and for how to configure VIlisp to use your browser to access your local copy of the Common Lisp HyperSpec.","5":"Make sure you have GNU Readline (version 4.2 or higher) installed, Perl (at least version 5; I use 5.8.4), and the Perl GNU Readline module installed.\r\n\r\nPut this at an appropriate place in your ~\/.vimrc:\r\n\r\n    autocmd BufRead,BufNewFile *.lsp,*.lisp so ~\/path\/to\/VIlisp.vim\r\n\r\nThe VIlisp package includes a file called lisp-thesaurus.  Put it in the same directory as VIlisp.vim, and VIlisp.vim will find it.\r\n\r\nIn an Xterm, run\r\n\r\n    export PERL_RL=gnu                  # use GNU readline in funnel\r\n    perl funnel.pl $HOME\/.lisp-pipe lisp\r\n\r\nIn a different xterm, run e.g.\r\n\r\n    vim test.lisp\r\n\r\nSee the README for more extensive configuration information, and for how to configure VIlisp to use your browser to access your local copy of the Common Lisp HyperSpec.","first_name":"Larry","6":"Larry","last_name":"Clapp","7":"Clapp","releases":[{"0":"221","vim_version":"6.0","1":"6.0","script_version":"2.3","2":"2.3","version_comment":"Fixed funnel.pl crashing when you resize its window.  Changed some mappings (from 'map' to 'nmap' where needed.)","3":"Fixed funnel.pl crashing when you resize its window.  Changed some mappings (from 'map' to 'nmap' where needed.)","package":"VIlisp.2.3.tgz","4":"VIlisp.2.3.tgz","src_id":"4722","5":"4722","creation_date":"1131392329","6":"1131392329"},{"0":"221","vim_version":"6.0","1":"6.0","script_version":"2.2","2":"2.2","version_comment":"Fixed a minor bug in funnel.pl that kept it from detecting EOF on the tty in some situations.","3":"Fixed a minor bug in funnel.pl that kept it from detecting EOF on the tty in some situations.","package":"VIlisp.2.2.tgz","4":"VIlisp.2.2.tgz","src_id":"4532","5":"4532","creation_date":"1125247428","6":"1125247428"},{"0":"221","vim_version":"6.0","1":"6.0","script_version":"2.1","2":"2.1","version_comment":"Fixed problem where if you don't have &hidden or &autowrite, and you have a modified file, and you \\es, it deletes most of your buffer.\r\nFixed some problems with funnel.pl not closing correctly.","3":"Fixed problem where if you don't have &hidden or &autowrite, and you have a modified file, and you \\es, it deletes most of your buffer.\r\nFixed some problems with funnel.pl not closing correctly.","package":"VIlisp.2.1.tgz","4":"VIlisp.2.1.tgz","src_id":"4505","5":"4505","creation_date":"1124545898","6":"1124545898"},{"0":"221","vim_version":"6.0","1":"6.0","script_version":"2.0","2":"2.0","version_comment":"- Updated the README.  Added lots of documentation.\r\n- Added looking up keywords in the HyperSpec\r\n- Added a Lisp keyword thesaurus\r\n- changed VIlisp.vim to check for the existence of a BufRead\/*.lsp event","3":"- Updated the README.  Added lots of documentation.\r\n- Added looking up keywords in the HyperSpec\r\n- Added a Lisp keyword thesaurus\r\n- changed VIlisp.vim to check for the existence of a BufRead\/*.lsp event","package":"VIlisp.2.0.tgz","4":"VIlisp.2.0.tgz","src_id":"915","5":"915","creation_date":"1023745760","6":"1023745760"},{"0":"221","vim_version":"6.0","1":"6.0","script_version":"1.1","2":"1.1","version_comment":"- added ^C processing to funnel.pl\r\n- added use of <Leader> in VIlisp.vim mappings\r\n- added a few mappings\r\n    - ,qi -- quit interpreter\r\n    - ,ci -- send ^C to interpreter\r\n- changed wincol() to vircol().  Allows use of \"set number\"\r\n- use \"normal!\" instead of \"normal\" everywhere, so as to avoid clashes with user-defined mappings\r\n- added \"stty sane\" on exit of funnel.pl.  cmu lisp doesn't need it, but at least one Octave or R user does.\r\n","3":"- added ^C processing to funnel.pl\r\n- added use of <Leader> in VIlisp.vim mappings\r\n- added a few mappings\r\n    - ,qi -- quit interpreter\r\n    - ,ci -- send ^C to interpreter\r\n- changed wincol() to vircol().  Allows use of \"set number\"\r\n- use \"normal!\" instead of \"normal\" everywhere, so as to avoid clashes with user-defined mappings\r\n- added \"stty sane\" on exit of funnel.pl.  cmu lisp doesn't need it, but at least one Octave or R user does.\r\n","package":"VIlisp.1.1.tgz","4":"VIlisp.1.1.tgz","src_id":"829","5":"829","creation_date":"1020188899","6":"1020188899"},{"0":"221","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"VIlisp.tgz","4":"VIlisp.tgz","src_id":"610","5":"610","creation_date":"1014060284","6":"1014060284"}]},"220":{"script_id":"220","0":"220","script_name":"mkview.vim","1":"mkview.vim","script_type":"utility","2":"utility","summary":"implementation of mkview without requiring a view file","3":"implementation of mkview without requiring a view file","description":"This module provides functions which emulate the |mkview| function of vim\r\nwithout requiring the creation of |view-file|s. This is useful when you\r\nhave an explorer type window with some arbitrary level of folding which\r\nneeds to be remembered. This module is therefore of interest to script\r\nwriters and not to the casual vim user.\r\n\r\nSynopsis:\r\n\r\n1. let viewInfo = MkView()\r\n   This returns a formatted string viewInfo (see file for the format) which\r\n   contains the minimal information needed to\r\n   . Restore manually folds. Restore manually opened and closed folds.\r\n     (this is the behavior of |mkview| when 'viewoptions' contains\r\n     \"folds\".\r\n   . Restore the cursor row and column position.\r\n   The file is allowed to have arbitrarily nested folds.\r\n   If there is prior information about the folds, then the following\r\n   variants described below can be used.\r\n\r\n2. let viewInfo  = MkViewNoFolds()\r\n   When it is known that there are no folds in the file, then use this\r\n   function. It will contain just the information needed to restore the\r\n   cursor row and column positions.\r\n\r\n3. let viewInfo = MkViewNoNestedFolds()\r\n   When it is known apriori that there are no folds with |foldlevel|\r\n   greater than 1, i.e, there are no nested folds, then use this function\r\n   which takes advantage of the fact to be faster than MkView(). Nested\r\n   folds, if they exist will be silently ignored if this function is used.\r\n\r\n4. call LoadView(viewInfo)\r\n   This function restores the fold state of the file as described in\r\n   MkView(). It eliminates the folds already in the file before restoring\r\n   the original fold state so that additional nestedness is not introduced.\r\n","4":"This module provides functions which emulate the |mkview| function of vim\r\nwithout requiring the creation of |view-file|s. This is useful when you\r\nhave an explorer type window with some arbitrary level of folding which\r\nneeds to be remembered. This module is therefore of interest to script\r\nwriters and not to the casual vim user.\r\n\r\nSynopsis:\r\n\r\n1. let viewInfo = MkView()\r\n   This returns a formatted string viewInfo (see file for the format) which\r\n   contains the minimal information needed to\r\n   . Restore manually folds. Restore manually opened and closed folds.\r\n     (this is the behavior of |mkview| when 'viewoptions' contains\r\n     \"folds\".\r\n   . Restore the cursor row and column position.\r\n   The file is allowed to have arbitrarily nested folds.\r\n   If there is prior information about the folds, then the following\r\n   variants described below can be used.\r\n\r\n2. let viewInfo  = MkViewNoFolds()\r\n   When it is known that there are no folds in the file, then use this\r\n   function. It will contain just the information needed to restore the\r\n   cursor row and column positions.\r\n\r\n3. let viewInfo = MkViewNoNestedFolds()\r\n   When it is known apriori that there are no folds with |foldlevel|\r\n   greater than 1, i.e, there are no nested folds, then use this function\r\n   which takes advantage of the fact to be faster than MkView(). Nested\r\n   folds, if they exist will be silently ignored if this function is used.\r\n\r\n4. call LoadView(viewInfo)\r\n   This function restores the fold state of the file as described in\r\n   MkView(). It eliminates the folds already in the file before restoring\r\n   the original fold state so that additional nestedness is not introduced.\r\n","install_details":"drop in your ~\/.vim\/plugin directory","5":"drop in your ~\/.vim\/plugin directory","first_name":"Srinath","6":"Srinath","last_name":"Avadhanula","7":"Avadhanula","releases":[{"0":"220","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"mkview.vim","4":"mkview.vim","src_id":"605","5":"605","creation_date":"1013967011","6":"1013967011"}]},"219":{"script_id":"219","0":"219","script_name":"bccalc.vim","1":"bccalc.vim","script_type":"utility","2":"utility","summary":"evaluate equations within vim","3":"evaluate equations within vim","description":"This scirpt calculates equations using the program 'bc' (found on most linux systems, available for most systems).  Visually select the equation you want to calculate, then hit ;bc - if the selection ends with an '=' sign, the answer will be appended after the equal, otherwise, the answer is echoed as a message. Equations can span multiple lines, and the full bc syntax is probably supported.  Additionally, sin (), cos (), etc, are transformed into the names used by bc (s () c (), etc).\r\n\r\nThis script was first entered as a tip, but someone pointed out that functions are hard to use when posted as tips, so this makes it easier to download and use.\r\n\r\nHere are some example lines:\r\n\r\n2 * sqrt (2) =\r\n\r\n3 * (2 - 1) + 4.0 ^ 6 =\r\n\r\n4 \/ 3 =\r\n\r\n3 +\r\n   4 -\r\n      2 * (1 \/ (3 + 2)) =\r\n\r\ndefine rad (x) {\r\n  return (x \/ 180) * 4 * atan (1)\r\n}\r\ncos (rad (45)) =\r\n\r\nibase = 2; obase = 2;\r\n0100 * 0101 = \r\n\r\nSelect each of these in turn (continguous non-blank lines, and hit ;bc for each), and this is what you get:\r\n2 * sqrt (2) = 2.82842712474619009760\r\n\r\n3 * (2 - 1) + 4.0 ^ 6 = 4099.000000\r\n\r\n4 \/ 3 = 1.33333333333333333333\r\n\r\n3 +\r\n   4 -\r\n      2 * (1 \/ (3 + 2)) = 6.60000000000000000000\r\n\r\ndefine rad (x) {\r\n  return (x \/ 180) * 4 * atan (1)\r\n}\r\ncos (rad (45)) = .70710678118654752440 \r\n\r\nibase = 2; obase = 2;\r\n0100 * 0101 = 10100\r\n\r\nChaining is now allowed:\r\n\r\nstart with this\r\n\r\n2 + 3 = \r\n;bc\r\n2 + 3 = 5\r\nadd some more stuff:\r\n2 + 3 = 5 * 2 = \r\n;bc\r\n2  + 3 = 5 * 2 = 10","4":"This scirpt calculates equations using the program 'bc' (found on most linux systems, available for most systems).  Visually select the equation you want to calculate, then hit ;bc - if the selection ends with an '=' sign, the answer will be appended after the equal, otherwise, the answer is echoed as a message. Equations can span multiple lines, and the full bc syntax is probably supported.  Additionally, sin (), cos (), etc, are transformed into the names used by bc (s () c (), etc).\r\n\r\nThis script was first entered as a tip, but someone pointed out that functions are hard to use when posted as tips, so this makes it easier to download and use.\r\n\r\nHere are some example lines:\r\n\r\n2 * sqrt (2) =\r\n\r\n3 * (2 - 1) + 4.0 ^ 6 =\r\n\r\n4 \/ 3 =\r\n\r\n3 +\r\n   4 -\r\n      2 * (1 \/ (3 + 2)) =\r\n\r\ndefine rad (x) {\r\n  return (x \/ 180) * 4 * atan (1)\r\n}\r\ncos (rad (45)) =\r\n\r\nibase = 2; obase = 2;\r\n0100 * 0101 = \r\n\r\nSelect each of these in turn (continguous non-blank lines, and hit ;bc for each), and this is what you get:\r\n2 * sqrt (2) = 2.82842712474619009760\r\n\r\n3 * (2 - 1) + 4.0 ^ 6 = 4099.000000\r\n\r\n4 \/ 3 = 1.33333333333333333333\r\n\r\n3 +\r\n   4 -\r\n      2 * (1 \/ (3 + 2)) = 6.60000000000000000000\r\n\r\ndefine rad (x) {\r\n  return (x \/ 180) * 4 * atan (1)\r\n}\r\ncos (rad (45)) = .70710678118654752440 \r\n\r\nibase = 2; obase = 2;\r\n0100 * 0101 = 10100\r\n\r\nChaining is now allowed:\r\n\r\nstart with this\r\n\r\n2 + 3 = \r\n;bc\r\n2 + 3 = 5\r\nadd some more stuff:\r\n2 + 3 = 5 * 2 = \r\n;bc\r\n2  + 3 = 5 * 2 = 10","install_details":"Download, place in plugin directory, or copy and paste function and mapping into your vimrc.","5":"Download, place in plugin directory, or copy and paste function and mapping into your vimrc.","first_name":"scott","6":"scott","last_name":"urban","7":"urban","releases":[{"0":"219","vim_version":"7.0","1":"7.0","script_version":"1.9","2":"1.9","version_comment":"Fix map clobbering bug - now puts answer at end in multi line selection.","3":"Fix map clobbering bug - now puts answer at end in multi line selection.","package":"bccalc.vim","4":"bccalc.vim","src_id":"25077","5":"25077","creation_date":"1492435067","6":"1492435067"},{"0":"219","vim_version":"6.0","1":"6.0","script_version":"1.8","2":"1.8","version_comment":"Change to allow chaining of equations, 3 + 4 = <7> - 4 = <3> - see summary","3":"Change to allow chaining of equations, 3 + 4 = <7> - 4 = <3> - see summary","package":"bccalc.vim","4":"bccalc.vim","src_id":"4706","5":"4706","creation_date":"1130522717","6":"1130522717"},{"0":"219","vim_version":"6.0","1":"6.0","script_version":"1.7","2":"1.7","version_comment":"Typo\r\n","3":"Typo\r\n","package":"bccalc.vim","4":"bccalc.vim","src_id":"2971","5":"2971","creation_date":"1082715171","6":"1082715171"},{"0":"219","vim_version":"6.0","1":"6.0","script_version":"1.6","2":"1.6","version_comment":"Fixes for sin, cos, etc, function substitutions, thanks to C. Campbell.\r\nFixes for multiple substitutions.\r\nFix for :Calculate command","3":"Fixes for sin, cos, etc, function substitutions, thanks to C. Campbell.\r\nFixes for multiple substitutions.\r\nFix for :Calculate command","package":"bccalc.vim","4":"bccalc.vim","src_id":"2968","5":"2968","creation_date":"1082711258","6":"1082711258"},{"0":"219","vim_version":"6.0","1":"6.0","script_version":"1.5","2":"1.5","version_comment":"Added a normal mode mapping for equation on lines by themselves - visual mode mapping can be tedious.  Added a command version, you can do\r\n:Calculate 2 + 5 \/ 2 + 4\r\nand 8 will be echoed","3":"Added a normal mode mapping for equation on lines by themselves - visual mode mapping can be tedious.  Added a command version, you can do\r\n:Calculate 2 + 5 \/ 2 + 4\r\nand 8 will be echoed","package":"bccalc.vim","4":"bccalc.vim","src_id":"2967","5":"2967","creation_date":"1082634281","6":"1082634281"},{"0":"219","vim_version":"6.0","1":"6.0","script_version":"1.2","2":"1.2","version_comment":"added bccalc_preload global variable - allows specifying file(s) with functions\/variables to load  before doing calculations","3":"added bccalc_preload global variable - allows specifying file(s) with functions\/variables to load  before doing calculations","package":"bccalc.vim","4":"bccalc.vim","src_id":"606","5":"606","creation_date":"1014023796","6":"1014023796"},{"0":"219","vim_version":"6.0","1":"6.0","script_version":"1.1","2":"1.1","version_comment":"Added \"&\", \"<\", \">\", and \"|\" to escape characters that mess up when passed to shell.","3":"Added \"&\", \"<\", \">\", and \"|\" to escape characters that mess up when passed to shell.","package":"bccalc.vim","4":"bccalc.vim","src_id":"597","5":"597","creation_date":"1013875123","6":"1013875123"},{"0":"219","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"bccalc.vim","4":"bccalc.vim","src_id":"596","5":"596","creation_date":"1013874859","6":"1013874859"}]},"218":{"script_id":"218","0":"218","script_name":"tex.vim","1":"tex.vim","script_type":"indent","2":"indent","summary":"Indent file for TeX","3":"Indent file for TeX","description":"This is an indent file for LaTeX.\r\n\r\nIt emulates Emacs' way of indenting item-environments, i.e., continuation lines of '\\item', '\\item[]', and '\\bibitem' will be indented separately.\r\n\r\nNOTE: I searched for an indent file for TeX and didn't found one -- so I wrote this script. Right now I've noticed that Johannes Zellner has already created an indent file for TeX (you can find his version at http:\/\/www.zellner.org\/vim\/indent\/tex.vim). I think that's the official version.\r\nNevertheless, since his version doesn't indent \\items the way I want them to be, I decided to release my version, too. Try both of them, use the one you like most.","4":"This is an indent file for LaTeX.\r\n\r\nIt emulates Emacs' way of indenting item-environments, i.e., continuation lines of '\\item', '\\item[]', and '\\bibitem' will be indented separately.\r\n\r\nNOTE: I searched for an indent file for TeX and didn't found one -- so I wrote this script. Right now I've noticed that Johannes Zellner has already created an indent file for TeX (you can find his version at http:\/\/www.zellner.org\/vim\/indent\/tex.vim). I think that's the official version.\r\nNevertheless, since his version doesn't indent \\items the way I want them to be, I decided to release my version, too. Try both of them, use the one you like most.","install_details":"Copy the file to your ~\/.vim\/indent\/ directory","5":"Copy the file to your ~\/.vim\/indent\/ directory","first_name":"Johannes","6":"Johannes","last_name":"Tanzler","7":"Tanzler","releases":[{"0":"218","vim_version":"7.0","1":"7.0","script_version":"0.5","2":"0.5","version_comment":"2005\/06\/15, Moshe Kaminsky <kaminsky@math.huji.ac.il>\r\n(*) New variables: g:tex_items, g:tex_itemize_env, g:tex_noindent_env\r\n\r\n2011\/3\/6, by Zhou Yi Chao <broken.zhou@gmail.com>\r\n(*) Don't change indentation of lines starting with '%'\r\n(*) New features: Add smartindent-like indent for \"{}\" and  \"[]\".\r\n(*) New variables: g:tex_indent_brace\r\n\r\n+ License","3":"2005\/06\/15, Moshe Kaminsky <kaminsky@math.huji.ac.il>\r\n(*) New variables: g:tex_items, g:tex_itemize_env, g:tex_noindent_env\r\n\r\n2011\/3\/6, by Zhou Yi Chao <broken.zhou@gmail.com>\r\n(*) Don't change indentation of lines starting with '%'\r\n(*) New features: Add smartindent-like indent for \"{}\" and  \"[]\".\r\n(*) New variables: g:tex_indent_brace\r\n\r\n+ License","package":"tex.vim","4":"tex.vim","src_id":"16497","5":"16497","creation_date":"1315611878","6":"1315611878"},{"0":"218","vim_version":"6.0","1":"6.0","script_version":"0.4","2":"0.4","version_comment":"New variables: g:tex_items, g:tex_itemize_env, g:tex_noindent_env (Moshe Kaminsky)\r\n","3":"New variables: g:tex_items, g:tex_itemize_env, g:tex_noindent_env (Moshe Kaminsky)\r\n","package":"tex.vim","4":"tex.vim","src_id":"4363","5":"4363","creation_date":"1118765128","6":"1118765128"},{"0":"218","vim_version":"6.0","1":"6.0","script_version":"0.02","2":"0.02","version_comment":"Better support for the option, uses some regex instead of several '||'. (Thanks to Luc Hermitte!)","3":"Better support for the option, uses some regex instead of several '||'. (Thanks to Luc Hermitte!)","package":"tex-indent-0.02.vim","4":"tex-indent-0.02.vim","src_id":"609","5":"609","creation_date":"1014044139","6":"1014044139"},{"0":"218","vim_version":"6.0","1":"6.0","script_version":"0.01","2":"0.01","version_comment":"Initial upload","3":"Initial upload","package":"tex.vim","4":"tex.vim","src_id":"595","5":"595","creation_date":"1013872681","6":"1013872681"}]},"217":{"script_id":"217","0":"217","script_name":"cmvc.vim","1":"cmvc.vim","script_type":"utility","2":"utility","summary":"Menu \/ Mappings for CMVC version control application","3":"Menu \/ Mappings for CMVC version control application","description":"This script integrates using the IBM Configuration Management Version Control (CMVC) application from within Vim.  It provides keyboard shortcuts as well as a menu to access common functions such as checking files in and out, viewing and responding to defects, etc.\r\n\r\nCurrently, only the functions I use regularly (Defect, File, Track, and VerifyCm) are implemented.  If you want to add others, the API should be fairly straightforward to do so.  Of course, I would appreciate receiving any changes you make, so that I can incorporate it into the next version (and avoid duplicating the work myself).\r\n\r\nNOTE:  This script currently requires Vim 6.  If there is interest in making it 5.x compatible, let me know and I will see what I can do.\r\n\r\nTODO:\t    Here are some other things I want to add when I get around to it:\r\n    -\tImplement more functions, like Report, to get a list of available defects \/ files \/ etc., which you can then view or\r\n\tcheckout.\r\n    -\tMake the script more \"plugin-ized\", like allowing users to override the default mappings and use their own.\r\n    -\tKeep a history of releases, components, and families used, then present them in a \"confirm\" dialog so the user\r\n\tcan just pick one instead of retyping it.  Inlcude an \"other\" button to bring up an \"inputdialog\" so the user can still\r\n\tenter an unlisted \/ new value.\r\n    -\tAdd commands to let the functions be used in Command mode.","4":"This script integrates using the IBM Configuration Management Version Control (CMVC) application from within Vim.  It provides keyboard shortcuts as well as a menu to access common functions such as checking files in and out, viewing and responding to defects, etc.\r\n\r\nCurrently, only the functions I use regularly (Defect, File, Track, and VerifyCm) are implemented.  If you want to add others, the API should be fairly straightforward to do so.  Of course, I would appreciate receiving any changes you make, so that I can incorporate it into the next version (and avoid duplicating the work myself).\r\n\r\nNOTE:  This script currently requires Vim 6.  If there is interest in making it 5.x compatible, let me know and I will see what I can do.\r\n\r\nTODO:\t    Here are some other things I want to add when I get around to it:\r\n    -\tImplement more functions, like Report, to get a list of available defects \/ files \/ etc., which you can then view or\r\n\tcheckout.\r\n    -\tMake the script more \"plugin-ized\", like allowing users to override the default mappings and use their own.\r\n    -\tKeep a history of releases, components, and families used, then present them in a \"confirm\" dialog so the user\r\n\tcan just pick one instead of retyping it.  Inlcude an \"other\" button to bring up an \"inputdialog\" so the user can still\r\n\tenter an unlisted \/ new value.\r\n    -\tAdd commands to let the functions be used in Command mode.","install_details":"Just drop this file into your plugin directory, and it will automatically be loaded when you start Vim.  Otherwise, just put it in a directory of your choice and :source it as needed.  The syntax file should go into your syntax directory.\r\n","5":"Just drop this file into your plugin directory, and it will automatically be loaded when you start Vim.  Otherwise, just put it in a directory of your choice and :source it as needed.  The syntax file should go into your syntax directory.\r\n","first_name":"Dan","6":"Dan","last_name":"Sharp","7":"Sharp","releases":[{"0":"217","vim_version":"6.0","1":"6.0","script_version":"1.4","2":"1.4","version_comment":"- Make Defect List View prettier.\t\r\n- Fix diff function\t\r\n- If set to use password authentication, prompt user to log in on first command if necessary.\r\n- Misc. bug fixes","3":"- Make Defect List View prettier.\t\r\n- Fix diff function\t\r\n- If set to use password authentication, prompt user to log in on first command if necessary.\r\n- Misc. bug fixes","package":"CMVC.tar.gz","4":"CMVC.tar.gz","src_id":"2215","5":"2215","creation_date":"1060265580","6":"1060265580"},{"0":"217","vim_version":"6.0","1":"6.0","script_version":"1.3","2":"1.3","version_comment":"Fixed some glaring bugs and added:\r\n   - Check out \/ extract a particular version of a file.\r\n   - Diff two versions of a file with vim's builtin diff support.\r\n   - Login and Logout commands for in case your server requires it.\r\n   - Support more optional attributes of Defect and File commands","3":"Fixed some glaring bugs and added:\r\n   - Check out \/ extract a particular version of a file.\r\n   - Diff two versions of a file with vim's builtin diff support.\r\n   - Login and Logout commands for in case your server requires it.\r\n   - Support more optional attributes of Defect and File commands","package":"CMVC.tar.gz","4":"CMVC.tar.gz","src_id":"743","5":"743","creation_date":"1017666436","6":"1017666436"},{"0":"217","vim_version":"6.0","1":"6.0","script_version":"1.2","2":"1.2","version_comment":"--  Now uses full path name when extracting \/ checking out files.\r\n    Instead of putting the file in the current directory and\r\n    editing it there (preventing the concurrent editing of files \r\n    with the same name in two different releases), use the -top\r\n    option to put the files in the appropriate subdirectory of \r\n    the current directory and edit the file there.\r\n--  Add a help file.\r\n--  Enhance highlighting of -view output.\r\n--  Make script compatible with Johannes Zellner's AutoLoadGen.vim\r\n--  Only load menus when the gui is running.\r\n--  Allow a customizable top-level menu.\r\n","3":"--  Now uses full path name when extracting \/ checking out files.\r\n    Instead of putting the file in the current directory and\r\n    editing it there (preventing the concurrent editing of files \r\n    with the same name in two different releases), use the -top\r\n    option to put the files in the appropriate subdirectory of \r\n    the current directory and edit the file there.\r\n--  Add a help file.\r\n--  Enhance highlighting of -view output.\r\n--  Make script compatible with Johannes Zellner's AutoLoadGen.vim\r\n--  Only load menus when the gui is running.\r\n--  Allow a customizable top-level menu.\r\n","package":"CMVC.tar.gz","4":"CMVC.tar.gz","src_id":"679","5":"679","creation_date":"1015920681","6":"1015920681"},{"0":"217","vim_version":"6.0","1":"6.0","script_version":"1.1","2":"1.1","version_comment":"-   Added syntax file for to highlight -view output.\r\n-   Added extra map command for closing -view buffer\r\n-   Bug fixes\r\n","3":"-   Added syntax file for to highlight -view output.\r\n-   Added extra map command for closing -view buffer\r\n-   Bug fixes\r\n","package":"cmvc.tar.gz","4":"cmvc.tar.gz","src_id":"592","5":"592","creation_date":"1013721727","6":"1013721727"},{"0":"217","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"cmvc.vim","4":"cmvc.vim","src_id":"590","5":"590","creation_date":"1013677646","6":"1013677646"}]},"216":{"script_id":"216","0":"216","script_name":"xmms play and enqueue","1":"xmms play and enqueue","script_type":"utility","2":"utility","summary":"This snippet plays a file or enqueues it using xmms.","3":"This snippet plays a file or enqueues it using xmms.","description":"If a file contains filenames, each in a separate line,\nthen a filename can be played or enqueued into xmms\nby pressing Shift+F3 and F3 respectively.\n\nThis script requires no external dependencies except \nxmms.","4":"If a file contains filenames, each in a separate line,\nthen a filename can be played or enqueued into xmms\nby pressing Shift+F3 and F3 respectively.\n\nThis script requires no external dependencies except \nxmms.","install_details":"source the file from your .vimrc","5":"source the file from your .vimrc","first_name":"Shlomi","6":"Shlomi","last_name":"Fish","7":"Fish","releases":[{"0":"216","vim_version":"6.0","1":"6.0","script_version":"0.4.0","2":"0.4.0","version_comment":"Changed to a Vim-script function, so the file is not modified.","3":"Changed to a Vim-script function, so the file is not modified.","package":"xmms.vim","4":"xmms.vim","src_id":"1709","5":"1709","creation_date":"1044761238","6":"1044761238"},{"0":"216","vim_version":"5.7","1":"5.7","script_version":"0.2.0","2":"0.2.0","version_comment":"Initial upload","3":"Initial upload","package":"xmms.vim","4":"xmms.vim","src_id":"588","5":"588","creation_date":"1013650694","6":"1013650694"}]},"215":{"script_id":"215","0":"215","script_name":"tagmenu.vim","1":"tagmenu.vim","script_type":"utility","2":"utility","summary":"Tags menu for various programming language source files","3":"Tags menu for various programming language source files","description":"The taglist plugin supersedes the tags menu plugin. The taglist plugin\r\nintegrates the functionality of the tagsmenu plugin.\r\n\r\n The taglist plugin displays the list of tags defined in the current file in the\r\n\"Tags\" menu (in GUI Vim). The taglist plugin provides much more\r\nfunctionality than the tagsmenu plugin. You can download it from:\r\n\r\nhttp:\/\/vim.sourceforge.net\/scripts\/script.php?script_id=273\r\n\r\nYou can get more information about the taglist plugin from the\r\nfollowing page:\r\n\r\n    http:\/\/vim-taglist.sourceforge.net\r\n\r\nThe tags menu plugin is no longer maintained.\r\n\r\nOverview\r\n\r\nThe \"Tags Menu\" plugin provides the following features:\r\n\r\n1. Creates a \"Tags\" menu containing all the tags (variables, functions,\r\n   classes, methods, macros, etc) defined in the current file.\r\n2. Creates a popup menu with the contents of the \"Tags\" menu. This popup\r\n   menu can be accessed  by right clicking the mouse.\r\n3. Groups the tags by their type and displays them in separate submenus.\r\n4. The \"Tags\" menu can be sorted either by name or by line number.\r\n5. When a tag name is selected from the \"Tags\" menu, positions the cursor\r\n   at the definition of the tag.\r\n6. Automatically updates the \"Tags\" menu as you switch between\r\n   files\/buffers.\r\n7. If the number of tags in a particular type exceeds a configurable limit,\r\n   splits the menu for that tag type into one or more submenus.\r\n8. Supports the following language files: Assembly, ASP, Awk, C, C++,\r\n   Cobol, Eiffel, Fortran, Java, Lisp, Make, Pascal, Perl, PHP, Python,\r\n   Rexx, Ruby, Scheme, Shell, Slang, TCL, Verilog, Vim and Yacc.\r\n9. Runs in all the platforms where the exuberant ctags utility and Vim are\r\n   supported (this includes MS-Windows and Unix based systems).\r\n10. Will run only in the GUI version of Vim.\r\n11. The ctags output for a file is cached to speed up updating the \"Tags\"\r\n    menu.\r\n\r\nThis script relies on the exuberant ctags utility to get the tags defined in\r\na file. You can download the exuberant ctags utility from\r\nhttp:\/\/ctags.sourceforge.net. The exuberant ctags utility must be installed\r\nin your system to use this plugin. You should use exuberant ctags version\r\n5.3 and above.  There is no need for you to create a tags file to use this\r\nplugin.\r\n\r\nConfiguration\r\n\r\nBy changing the following variables you can configure the behavior of this\r\nscript. Set the following variables in your .vimrc file using the 'let'\r\ncommand.\r\n\r\nThe script uses the Tmenu_ctags_cmd variable to locate the ctags utility.\r\nBy default, this is set to ctags. Set this variable to point to the\r\nlocation of the ctags utility in your system:\r\n\r\n          let Tmenu_ctags_cmd = 'd:\\tools\\ctags.exe'\r\n\r\nIf a file contains too many tags of a particular type (function, variable,\r\netc), greater than a configurable limit, then the tags menu for that tag\r\ntype will be split into sub-menus.  The default limit is 25.  This can be\r\nchanged by setting the Tmenu_max_submenu_items variable:\r\n\r\n          let Tmenu_max_submenu_items = 20\r\n\r\nIf the number of tags of a particular tag type is more than that specified\r\nby Tmenu_max_submenu_items setting, then the tags menu for that tag type\r\nwill be split into sub-menus. The name of the submenu is formed using the\r\nnames of the first and the last tag entries in that submenu. Only the first\r\nTmenu_max_tag_length characters from these names will be used to form the\r\nsubmenu name. Change the Tmenu_max_tag_length setting if you want to include\r\nmore or less characters:\r\n\r\n          let Tmenu_max_tag_length = 10\r\n\r\nBy default, the tag names will be added to the menu in the order in which\r\nthey are defined in the file. You can alphabetically sort the tag names\r\nin the menu by selecting the \"Sort menu by->Name\" menu item. You can also\r\nchange the default order by setting the variable Tmenu_sort_type to\r\n\"name\" or \"order\":\r\n\r\n          let Tmenu_sort_type = \"name\"\r\n\r\nThis script will not work in 'compatible' mode.  Make sure the 'compatible'\r\noption is not set. This script depends on the file type detected by Vim.\r\nMake sure the Vim file type detection (:filetype on) is turned on.","4":"The taglist plugin supersedes the tags menu plugin. The taglist plugin\r\nintegrates the functionality of the tagsmenu plugin.\r\n\r\n The taglist plugin displays the list of tags defined in the current file in the\r\n\"Tags\" menu (in GUI Vim). The taglist plugin provides much more\r\nfunctionality than the tagsmenu plugin. You can download it from:\r\n\r\nhttp:\/\/vim.sourceforge.net\/scripts\/script.php?script_id=273\r\n\r\nYou can get more information about the taglist plugin from the\r\nfollowing page:\r\n\r\n    http:\/\/vim-taglist.sourceforge.net\r\n\r\nThe tags menu plugin is no longer maintained.\r\n\r\nOverview\r\n\r\nThe \"Tags Menu\" plugin provides the following features:\r\n\r\n1. Creates a \"Tags\" menu containing all the tags (variables, functions,\r\n   classes, methods, macros, etc) defined in the current file.\r\n2. Creates a popup menu with the contents of the \"Tags\" menu. This popup\r\n   menu can be accessed  by right clicking the mouse.\r\n3. Groups the tags by their type and displays them in separate submenus.\r\n4. The \"Tags\" menu can be sorted either by name or by line number.\r\n5. When a tag name is selected from the \"Tags\" menu, positions the cursor\r\n   at the definition of the tag.\r\n6. Automatically updates the \"Tags\" menu as you switch between\r\n   files\/buffers.\r\n7. If the number of tags in a particular type exceeds a configurable limit,\r\n   splits the menu for that tag type into one or more submenus.\r\n8. Supports the following language files: Assembly, ASP, Awk, C, C++,\r\n   Cobol, Eiffel, Fortran, Java, Lisp, Make, Pascal, Perl, PHP, Python,\r\n   Rexx, Ruby, Scheme, Shell, Slang, TCL, Verilog, Vim and Yacc.\r\n9. Runs in all the platforms where the exuberant ctags utility and Vim are\r\n   supported (this includes MS-Windows and Unix based systems).\r\n10. Will run only in the GUI version of Vim.\r\n11. The ctags output for a file is cached to speed up updating the \"Tags\"\r\n    menu.\r\n\r\nThis script relies on the exuberant ctags utility to get the tags defined in\r\na file. You can download the exuberant ctags utility from\r\nhttp:\/\/ctags.sourceforge.net. The exuberant ctags utility must be installed\r\nin your system to use this plugin. You should use exuberant ctags version\r\n5.3 and above.  There is no need for you to create a tags file to use this\r\nplugin.\r\n\r\nConfiguration\r\n\r\nBy changing the following variables you can configure the behavior of this\r\nscript. Set the following variables in your .vimrc file using the 'let'\r\ncommand.\r\n\r\nThe script uses the Tmenu_ctags_cmd variable to locate the ctags utility.\r\nBy default, this is set to ctags. Set this variable to point to the\r\nlocation of the ctags utility in your system:\r\n\r\n          let Tmenu_ctags_cmd = 'd:\\tools\\ctags.exe'\r\n\r\nIf a file contains too many tags of a particular type (function, variable,\r\netc), greater than a configurable limit, then the tags menu for that tag\r\ntype will be split into sub-menus.  The default limit is 25.  This can be\r\nchanged by setting the Tmenu_max_submenu_items variable:\r\n\r\n          let Tmenu_max_submenu_items = 20\r\n\r\nIf the number of tags of a particular tag type is more than that specified\r\nby Tmenu_max_submenu_items setting, then the tags menu for that tag type\r\nwill be split into sub-menus. The name of the submenu is formed using the\r\nnames of the first and the last tag entries in that submenu. Only the first\r\nTmenu_max_tag_length characters from these names will be used to form the\r\nsubmenu name. Change the Tmenu_max_tag_length setting if you want to include\r\nmore or less characters:\r\n\r\n          let Tmenu_max_tag_length = 10\r\n\r\nBy default, the tag names will be added to the menu in the order in which\r\nthey are defined in the file. You can alphabetically sort the tag names\r\nin the menu by selecting the \"Sort menu by->Name\" menu item. You can also\r\nchange the default order by setting the variable Tmenu_sort_type to\r\n\"name\" or \"order\":\r\n\r\n          let Tmenu_sort_type = \"name\"\r\n\r\nThis script will not work in 'compatible' mode.  Make sure the 'compatible'\r\noption is not set. This script depends on the file type detected by Vim.\r\nMake sure the Vim file type detection (:filetype on) is turned on.","install_details":"1. Copy the tagmenu.vim script to the .vim\/plugin directory.  Refer to\r\n    'help add-plugin', 'help add-global-plugin' and 'help runtimepath' for \r\n    more details.\r\n2. Set the Tmenu_ctags_cmd variable to point to the exuberant ctags \r\n    utility path.\r\n3. If you have previously used the funcmenu.vim plugin script, remove it\r\n    from your ~\/.vim\/plugin directory.\r\n4. Restart GVim.\r\n","5":"1. Copy the tagmenu.vim script to the .vim\/plugin directory.  Refer to\r\n    'help add-plugin', 'help add-global-plugin' and 'help runtimepath' for \r\n    more details.\r\n2. Set the Tmenu_ctags_cmd variable to point to the exuberant ctags \r\n    utility path.\r\n3. If you have previously used the funcmenu.vim plugin script, remove it\r\n    from your ~\/.vim\/plugin directory.\r\n4. Restart GVim.\r\n","first_name":"Yegappan","6":"Yegappan","last_name":"Lakshmanan","7":"Lakshmanan","releases":[{"0":"215","vim_version":"6.0","1":"6.0","script_version":"1.31","2":"1.31","version_comment":"Fixed a problem with processing tags with \"|\" in the search pattern.","3":"Fixed a problem with processing tags with \"|\" in the search pattern.","package":"tagmenu.vim","4":"tagmenu.vim","src_id":"1396","5":"1396","creation_date":"1037009728","6":"1037009728"},{"0":"215","vim_version":"6.0","1":"6.0","script_version":"1.3","2":"1.3","version_comment":"Added support for popup menus (Thomas Kimpton), verilog language and updated comments.","3":"Added support for popup menus (Thomas Kimpton), verilog language and updated comments.","package":"tagmenu.vim","4":"tagmenu.vim","src_id":"1250","5":"1250","creation_date":"1032982138","6":"1032982138"},{"0":"215","vim_version":"6.0","1":"6.0","script_version":"1.2","2":"1.2","version_comment":"Handle multiple tags with same name. Center the selected tag line. Rename the menu names to be consistent with other menus.","3":"Handle multiple tags with same name. Center the selected tag line. Rename the menu names to be consistent with other menus.","package":"tagmenu.vim","4":"tagmenu.vim","src_id":"962","5":"962","creation_date":"1025278726","6":"1025278726"},{"0":"215","vim_version":"6.0","1":"6.0","script_version":"1.4","2":"1.4","version_comment":"Fix for handling long filenames.\r\nPass the Vim filetype to ctags.","3":"Fix for handling long filenames.\r\nPass the Vim filetype to ctags.","package":"funcmenu.vim","4":"funcmenu.vim","src_id":"783","5":"783","creation_date":"1018524034","6":"1018524034"}]},"214":{"script_id":"214","0":"214","script_name":"lh-vim-lib","1":"lh-vim-lib","script_type":"utility","2":"utility","summary":"a library plugin for script writers","3":"a library plugin for script writers","description":"lh-vim-lib is a collection of miscellanous VimL functions. \r\nAn exhaustive list of the functions provided can be found at: https:\/\/github.com\/LucHermitte\/lh-vim-lib where the library is hosted.\r\n\r\nIt can be installed with VAM (or vim-pi compatible plugin managers) under the name \"lh-vim-lib\".\r\n\r\nRequirements: Vim 7+ (this plugin is actually exclusivelly made of autoload plugins)\r\n\r\nNote: vimscript # 214 used to be menu-map which is now part of lh-vim-lib.","4":"lh-vim-lib is a collection of miscellanous VimL functions. \r\nAn exhaustive list of the functions provided can be found at: https:\/\/github.com\/LucHermitte\/lh-vim-lib where the library is hosted.\r\n\r\nIt can be installed with VAM (or vim-pi compatible plugin managers) under the name \"lh-vim-lib\".\r\n\r\nRequirements: Vim 7+ (this plugin is actually exclusivelly made of autoload plugins)\r\n\r\nNote: vimscript # 214 used to be menu-map which is now part of lh-vim-lib.","install_details":"See: https:\/\/github.com\/LucHermitte\/lh-vim-lib#installation\r\n\r\nOr source this old vimball archive.","5":"See: https:\/\/github.com\/LucHermitte\/lh-vim-lib#installation\r\n\r\nOr source this old vimball archive.","first_name":"Luc","6":"Luc","last_name":"Hermitte","7":"Hermitte","releases":[{"0":"214","vim_version":"7.4","1":"7.4","script_version":"3.2.5","2":"3.2.5","version_comment":"(*) new functions lh#path#munge(), and lh#list#push_if_new()\r\n(*) new RAII-tool: lh#on#exit() that will register cleanup action to be executed at the end on a\r\nscope, and more precisally in a :finally section.","3":"(*) new functions lh#path#munge(), and lh#list#push_if_new()\r\n(*) new RAII-tool: lh#on#exit() that will register cleanup action to be executed at the end on a\r\nscope, and more precisally in a :finally section.","package":"lh-vim-lib-3.2.5.vmb","4":"lh-vim-lib-3.2.5.vmb","src_id":"22976","5":"22976","creation_date":"1425393731","6":"1425393731"},{"0":"214","vim_version":"7.2","1":"7.2","script_version":"3.2.2","2":"3.2.2","version_comment":"Mainly bug fixes for local_vimrc","3":"Mainly bug fixes for local_vimrc","package":"lh-vim-lib-3.2.2.vmb","4":"lh-vim-lib-3.2.2.vmb","src_id":"22416","5":"22416","creation_date":"1410523553","6":"1410523553"},{"0":"214","vim_version":"7.2","1":"7.2","script_version":"3.2.1","2":"3.2.1","version_comment":"Latest snapshot of the library....","3":"Latest snapshot of the library....","package":"lh-vim-lib-3.2.1.vmb","4":"lh-vim-lib-3.2.1.vmb","src_id":"22369","5":"22369","creation_date":"1409154713","6":"1409154713"},{"0":"214","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"menu-map.vim","4":"menu-map.vim","src_id":"584","5":"584","creation_date":"1013598782","6":"1013598782"}]},"213":{"script_id":"213","0":"213","script_name":"c.vim","1":"c.vim","script_type":"utility","2":"utility","summary":"C\/C++ IDE -- Write and run programs. Insert statements, idioms, comments etc.","3":"C\/C++ IDE -- Write and run programs. Insert statements, idioms, comments etc.","description":"**   Statement oriented editing of  C \/ C++ programs\r\n**   Speed up writing new code considerably\r\n**   Write code and comments with a professional appearance from the beginning\r\n**   Use code snippets\r\n**   Toolbox for cmake(1), doxygen(1), and make(1)\r\n\r\n- insertion of various types of comments   (file prologue, function descriptions, file section headers\r\n    keyword comments, date, time, ...  )\r\n- insertion of empty control statements   (if-else, while, do-while, switch, ... )\r\n- insertion of various preprocessor directives\r\n- insertion of C-idioms   (enum+typedef, loops, complete main, empty function, file open dialogs, ... )\r\n- insertion of C++ -idioms   ( frames for simple classes and template classes, try-catch blocks,\r\n    file open dialogs, output manipulators, ios flags, ... )\r\n- use and organize your own collection of code snippets\r\n- compile \/ link \/ run support for one-file projects   (without a makefile)\r\n- run buffer through splint\r\n- personalization of comments   (name, email, ... )\r\n- menus can be switched on and off   (via the Tools menu)\r\n\r\nSome screen shots :  https:\/\/wolfgangmehner.github.io\/vim-plugins\/csupport.html\r\n\r\nFor plug-in managers :  https:\/\/github.com\/WolfgangMehner\/c-support\r\n\r\nThe help file online :  https:\/\/wolfgangmehner.github.io\/vim-plugins\/doc\/csupport.html\r\n\r\nThe key mappings of this plug-in :  https:\/\/wolfgangmehner.github.io\/vim-plugins\/csupport\/c-hotkeys.pdf\r\n\r\nThe installation explained :  \"Make Vim as Your C\/C++ IDE Using c.vim Plugin\"\r\n(http:\/\/www.thegeekstuff.com\/2009\/01\/tutorial-make-vim-as-your-cc-ide-using-cvim-plugin\/)\r\n\r\nDOCUMENTATION\r\n--------------------------------------------------------\r\nThis plug-in comes with a help file (csupport.txt). Read it with\r\n\r\n    :help csupport\r\n\r\n** PLEASE READ THE DOCUMENTATION **\r\n\r\nEditing actions differ for different modes! There are a lot of features which\r\ncan be configured or customized to match your needs.\r\n\r\nGitHub\r\n--------------------------------------------------------\r\nC-Support is on GitHub:\r\n\r\n    https:\/\/github.com\/WolfgangMehner\/vim-plugins\r\n\r\n(Please help us keep track of all the issues and name your report\/request \"C-Support: <title>\")\r\n\r\n","4":"**   Statement oriented editing of  C \/ C++ programs\r\n**   Speed up writing new code considerably\r\n**   Write code and comments with a professional appearance from the beginning\r\n**   Use code snippets\r\n**   Toolbox for cmake(1), doxygen(1), and make(1)\r\n\r\n- insertion of various types of comments   (file prologue, function descriptions, file section headers\r\n    keyword comments, date, time, ...  )\r\n- insertion of empty control statements   (if-else, while, do-while, switch, ... )\r\n- insertion of various preprocessor directives\r\n- insertion of C-idioms   (enum+typedef, loops, complete main, empty function, file open dialogs, ... )\r\n- insertion of C++ -idioms   ( frames for simple classes and template classes, try-catch blocks,\r\n    file open dialogs, output manipulators, ios flags, ... )\r\n- use and organize your own collection of code snippets\r\n- compile \/ link \/ run support for one-file projects   (without a makefile)\r\n- run buffer through splint\r\n- personalization of comments   (name, email, ... )\r\n- menus can be switched on and off   (via the Tools menu)\r\n\r\nSome screen shots :  https:\/\/wolfgangmehner.github.io\/vim-plugins\/csupport.html\r\n\r\nFor plug-in managers :  https:\/\/github.com\/WolfgangMehner\/c-support\r\n\r\nThe help file online :  https:\/\/wolfgangmehner.github.io\/vim-plugins\/doc\/csupport.html\r\n\r\nThe key mappings of this plug-in :  https:\/\/wolfgangmehner.github.io\/vim-plugins\/csupport\/c-hotkeys.pdf\r\n\r\nThe installation explained :  \"Make Vim as Your C\/C++ IDE Using c.vim Plugin\"\r\n(http:\/\/www.thegeekstuff.com\/2009\/01\/tutorial-make-vim-as-your-cc-ide-using-cvim-plugin\/)\r\n\r\nDOCUMENTATION\r\n--------------------------------------------------------\r\nThis plug-in comes with a help file (csupport.txt). Read it with\r\n\r\n    :help csupport\r\n\r\n** PLEASE READ THE DOCUMENTATION **\r\n\r\nEditing actions differ for different modes! There are a lot of features which\r\ncan be configured or customized to match your needs.\r\n\r\nGitHub\r\n--------------------------------------------------------\r\nC-Support is on GitHub:\r\n\r\n    https:\/\/github.com\/WolfgangMehner\/vim-plugins\r\n\r\n(Please help us keep track of all the issues and name your report\/request \"C-Support: <title>\")\r\n\r\n","install_details":"Copy the zip archive cvim.zip to $HOME\/.vim\/ (Linux\/Unix) or $HOME\/vimfiles\r\n(on the Windows platforms) and run\r\n    unzip cvim.zip\r\nIf you have already an older version of this plug-in and you have modified the\r\ntemplate files you may want to save your templates first or copy the files from\r\nthe archive by hand. See also the file README.md within the zip file.\r\n\r\nTo enable the tools for cmake or doxygen, add these lines to ~\/.vimrc :\r\n\r\n    let  g:C_UseTool_cmake    = 'yes'\r\n    let  g:C_UseTool_doxygen = 'yes'\r\n\r\nFor how to enable the Doxygen templates, see Chapter 1.10.1 of the documentation:\r\n\r\n    :help csupport-doxygen-enable","5":"Copy the zip archive cvim.zip to $HOME\/.vim\/ (Linux\/Unix) or $HOME\/vimfiles\r\n(on the Windows platforms) and run\r\n    unzip cvim.zip\r\nIf you have already an older version of this plug-in and you have modified the\r\ntemplate files you may want to save your templates first or copy the files from\r\nthe archive by hand. See also the file README.md within the zip file.\r\n\r\nTo enable the tools for cmake or doxygen, add these lines to ~\/.vimrc :\r\n\r\n    let  g:C_UseTool_cmake    = 'yes'\r\n    let  g:C_UseTool_doxygen = 'yes'\r\n\r\nFor how to enable the Doxygen templates, see Chapter 1.10.1 of the documentation:\r\n\r\n    :help csupport-doxygen-enable","first_name":"Fritz","6":"Fritz","last_name":"Mehner","7":"Mehner","releases":[{"0":"213","vim_version":"7.3","1":"7.3","script_version":"6.2","2":"6.2","version_comment":"- Add 'g:C_CustomTemplateFile'.\r\n- Add template personalization file and setup wizard.\r\n- Respect 'g:Xterm_Executable' and 'g:Xterm_Options'.\r\n  ('g:C_XtermDefaults' still works for backwards compatibility.)\r\n- Remove unused 'g:C_GuiTemplateBrowser'.\r\n- Change 'Run -> link' and 'Run -> run', do not produce object file anymore.\r\n- Add submenu 'Comments -> all sections'.\r\n- Add submenu 'Preprocessor -> include POSIX header'.\r\n- New and reworked templates.\r\n- Minor changes and bugfixes.","3":"- Add 'g:C_CustomTemplateFile'.\r\n- Add template personalization file and setup wizard.\r\n- Respect 'g:Xterm_Executable' and 'g:Xterm_Options'.\r\n  ('g:C_XtermDefaults' still works for backwards compatibility.)\r\n- Remove unused 'g:C_GuiTemplateBrowser'.\r\n- Change 'Run -> link' and 'Run -> run', do not produce object file anymore.\r\n- Add submenu 'Comments -> all sections'.\r\n- Add submenu 'Preprocessor -> include POSIX header'.\r\n- New and reworked templates.\r\n- Minor changes and bugfixes.","package":"c-support.zip","4":"c-support.zip","src_id":"24474","5":"24474","creation_date":"1472317446","6":"1472317446"},{"0":"213","vim_version":"7.0","1":"7.0","script_version":"6.1.1","2":"6.1.1","version_comment":"- Added 'C_SetMapLeader' and 'C_ResetMapLeader'.\r\n- Bugfix: Resetting maplocalleader in filetype plug-in after setting it to the\r\n  value of g:C_MapLeader.\r\n- Bugfix: Setup of local templates in case of global installation.\r\n- Bugfix: Better compatibility with custom mappings\r\n  (use \"normal!\" and \"noremap\" consistently).\r\n- 'Help->show manual' shows man page text with appropriate width (UNIX only).\r\n- Extended the documentation.","3":"- Added 'C_SetMapLeader' and 'C_ResetMapLeader'.\r\n- Bugfix: Resetting maplocalleader in filetype plug-in after setting it to the\r\n  value of g:C_MapLeader.\r\n- Bugfix: Setup of local templates in case of global installation.\r\n- Bugfix: Better compatibility with custom mappings\r\n  (use \"normal!\" and \"noremap\" consistently).\r\n- 'Help->show manual' shows man page text with appropriate width (UNIX only).\r\n- Extended the documentation.","package":"cvim.zip","4":"cvim.zip","src_id":"21803","5":"21803","creation_date":"1398096831","6":"1398096831"},{"0":"213","vim_version":"7.0","1":"7.0","script_version":"6.1","2":"6.1","version_comment":"- Map renamed: \\rme -> \\re.\r\n- New global variable g:C_InsertFileHeader (suppress file description comment for new files).\r\n- Two new ex commands: CCmdlineArgs, CMakeCmdlineArgs.\r\n- 'Run->cmd. line arg.' : tab expansion (files\/directories)for all arguments.\r\n- Bugfix: template 'file description header' not loading (thanks to Marco Lasczok).\r\n- Bugfix: unnecessary characters in one template.\r\n- Prototype picker improved.\r\n- Toggle non-C-comments.\r\n- Run debugger.\r\n- Some global variables now changeable on the fly.\r\n- Menus now show the correct mapleader.\r\n- Bugfix: g:C_LoadMenus now works.\r\n- Bugfix: Prevent unnecessary rereading of the template library.\r\n- Added Doxygen templates and 'Doxygen->brief, after member'.\r\n- Added help menu entries: help English, help Doxygen\r\n- Improved \"adjust end-of-line comment\".\r\n- Bugfix: Setup of local templates in case of global installation.\r\n- Bugfix: Map and menu entry 'Snippets->edit global templates'.\r\n- Several internal improvements.","3":"- Map renamed: \\rme -> \\re.\r\n- New global variable g:C_InsertFileHeader (suppress file description comment for new files).\r\n- Two new ex commands: CCmdlineArgs, CMakeCmdlineArgs.\r\n- 'Run->cmd. line arg.' : tab expansion (files\/directories)for all arguments.\r\n- Bugfix: template 'file description header' not loading (thanks to Marco Lasczok).\r\n- Bugfix: unnecessary characters in one template.\r\n- Prototype picker improved.\r\n- Toggle non-C-comments.\r\n- Run debugger.\r\n- Some global variables now changeable on the fly.\r\n- Menus now show the correct mapleader.\r\n- Bugfix: g:C_LoadMenus now works.\r\n- Bugfix: Prevent unnecessary rereading of the template library.\r\n- Added Doxygen templates and 'Doxygen->brief, after member'.\r\n- Added help menu entries: help English, help Doxygen\r\n- Improved \"adjust end-of-line comment\".\r\n- Bugfix: Setup of local templates in case of global installation.\r\n- Bugfix: Map and menu entry 'Snippets->edit global templates'.\r\n- Several internal improvements.","package":"cvim.zip","4":"cvim.zip","src_id":"21251","5":"21251","creation_date":"1388254156","6":"1388254156"},{"0":"213","vim_version":"7.0","1":"7.0","script_version":"6.0","2":"6.0","version_comment":" ++  The plug-in version 6.0+ is a rewriting of version 5.19. \r\n ++  The template syntax has changed! \r\n\r\n- New template system (many thanks to Wolfgang Mehner)\r\n- A few new hotkeys and menu item.\r\n- A few hotkeys and menu items renamed.\r\n\r\n","3":" ++  The plug-in version 6.0+ is a rewriting of version 5.19. \r\n ++  The template syntax has changed! \r\n\r\n- New template system (many thanks to Wolfgang Mehner)\r\n- A few new hotkeys and menu item.\r\n- A few hotkeys and menu items renamed.\r\n\r\n","package":"cvim.zip","4":"cvim.zip","src_id":"18444","5":"18444","creation_date":"1345490546","6":"1345490546"},{"0":"213","vim_version":"7.0","1":"7.0","script_version":"5.19","2":"5.19","version_comment":"- Resolve home for linked home directories.\r\n- Three C++-items removed (see file 'customization.cpp.vim').\r\n- Bugfix: global options changed unintentionally.\r\n- Minor improvements and bugfixes.","3":"- Resolve home for linked home directories.\r\n- Three C++-items removed (see file 'customization.cpp.vim').\r\n- Bugfix: global options changed unintentionally.\r\n- Minor improvements and bugfixes.","package":"cvim.zip","4":"cvim.zip","src_id":"17992","5":"17992","creation_date":"1337361929","6":"1337361929"},{"0":"213","vim_version":"7.0","1":"7.0","script_version":"5.18","2":"5.18","version_comment":"- Hotkeys \\lcs, \\ucs removed.\r\n- Bugfix: delayed template initialization missing correct style.\r\n- Wrong cursor position when inserting some templates at the end of a line.","3":"- Hotkeys \\lcs, \\ucs removed.\r\n- Bugfix: delayed template initialization missing correct style.\r\n- Wrong cursor position when inserting some templates at the end of a line.","package":"cvim.zip","4":"cvim.zip","src_id":"17559","5":"17559","creation_date":"1330802603","6":"1330802603"},{"0":"213","vim_version":"7.0","1":"7.0","script_version":"5.17","2":"5.17","version_comment":"- Two new plugin tags: LICENSE,ORGANIZATION\r\n- System-wide installation: minimal Template file for a user will automatically be added.\r\n- New menu item and hotkey: choose a makefile.\r\n- New idiom: realloc.\r\n- New preprocessor item: #if #endif.\r\n- New hotkeys: \\ire, \\ifs, \\ifp, \\pif.","3":"- Two new plugin tags: LICENSE,ORGANIZATION\r\n- System-wide installation: minimal Template file for a user will automatically be added.\r\n- New menu item and hotkey: choose a makefile.\r\n- New idiom: realloc.\r\n- New preprocessor item: #if #endif.\r\n- New hotkeys: \\ire, \\ifs, \\ifp, \\pif.","package":"cvim.zip","4":"cvim.zip","src_id":"17127","5":"17127","creation_date":"1325161670","6":"1325161670"},{"0":"213","vim_version":"7.0","1":"7.0","script_version":"5.16.1","2":"5.16.1","version_comment":"- Bugfix: problem with a system-wide installation under Windows (thanks to Ricardo Vrech).","3":"- Bugfix: problem with a system-wide installation under Windows (thanks to Ricardo Vrech).","package":"cvim.zip","4":"cvim.zip","src_id":"16847","5":"16847","creation_date":"1320958582","6":"1320958582"},{"0":"213","vim_version":"7.0","1":"7.0","script_version":"5.16","2":"5.16","version_comment":"- Plugin loads faster: loading the templates is delayed until the first use.\r\n- Plugin now works with pathogen.vim.\r\n- Menus will always be generated (for the use with :emenu).\r\n- Bugfix: no local templates available with a system-wide installation (thanks to Iain Arnell).\r\n- Several improvements.","3":"- Plugin loads faster: loading the templates is delayed until the first use.\r\n- Plugin now works with pathogen.vim.\r\n- Menus will always be generated (for the use with :emenu).\r\n- Bugfix: no local templates available with a system-wide installation (thanks to Iain Arnell).\r\n- Several improvements.","package":"cvim.zip","4":"cvim.zip","src_id":"16809","5":"16809","creation_date":"1320505833","6":"1320505833"},{"0":"213","vim_version":"7.0","1":"7.0","script_version":"5.15.1","2":"5.15.1","version_comment":"This is the correct version 5.15.\r\nThe version 5.15 just published) contains a wrong archive. Sorry.","3":"This is the correct version 5.15.\r\nThe version 5.15 just published) contains a wrong archive. Sorry.","package":"cvim.zip","4":"cvim.zip","src_id":"16506","5":"16506","creation_date":"1315764812","6":"1315764812"},{"0":"213","vim_version":"7.0","1":"7.0","script_version":"5.15","2":"5.15","version_comment":"- New hotkey \\cx C to C++ comments and vice versa.\r\n- Several hotkeys allow a range, e.g. '3\\cl' (see help text and c-hotkey.pdf).\r\n- Improved prototype picking: \\nf, \\np picks up a function prototype, \r\n  \\nm picks up a method prototype (see documentation for more).\r\n- include-statements will now be inserted in the actual line (before: new line\r\n  below the actual line).\r\n- Several minor improvements.","3":"- New hotkey \\cx C to C++ comments and vice versa.\r\n- Several hotkeys allow a range, e.g. '3\\cl' (see help text and c-hotkey.pdf).\r\n- Improved prototype picking: \\nf, \\np picks up a function prototype, \r\n  \\nm picks up a method prototype (see documentation for more).\r\n- include-statements will now be inserted in the actual line (before: new line\r\n  below the actual line).\r\n- Several minor improvements.","package":"cvim.zip","4":"cvim.zip","src_id":"16505","5":"16505","creation_date":"1315762293","6":"1315762293"},{"0":"213","vim_version":"7.0","1":"7.0","script_version":"5.14","2":"5.14","version_comment":"- A makefile can be run with C-F9\r\n- Linking ( Run menu, \\rl, \\rr ) will be suppressed if buffer contains no main function.\r\n- Bugfix: correctly deactivate unwanted compiler messages in a quickfix buffer.\r\n- Several minor improvements.","3":"- A makefile can be run with C-F9\r\n- Linking ( Run menu, \\rl, \\rr ) will be suppressed if buffer contains no main function.\r\n- Bugfix: correctly deactivate unwanted compiler messages in a quickfix buffer.\r\n- Several minor improvements.","package":"cvim.zip","4":"cvim.zip","src_id":"16018","5":"16018","creation_date":"1309604854","6":"1309604854"},{"0":"213","vim_version":"7.0","1":"7.0","script_version":"5.13","2":"5.13","version_comment":"- New hotkeys \\rmc (run 'make clean') and \\rme (executable to run).\r\n- Hotkeys for make are working when in a makefile.\r\n- Linker errors and errors during a make will be shown in a quickfix buffer.\r\n- Bugfix: detection of a systemwide installation can fail.\r\n- Bugfix: preprocessor directive '#if 0 #endif' not working.","3":"- New hotkeys \\rmc (run 'make clean') and \\rme (executable to run).\r\n- Hotkeys for make are working when in a makefile.\r\n- Linker errors and errors during a make will be shown in a quickfix buffer.\r\n- Bugfix: detection of a systemwide installation can fail.\r\n- Bugfix: preprocessor directive '#if 0 #endif' not working.","package":"cvim.zip","4":"cvim.zip","src_id":"14859","5":"14859","creation_date":"1295990269","6":"1295990269"},{"0":"213","vim_version":"7.0","1":"7.0","script_version":"5.12","2":"5.12","version_comment":"- New hotkeys \\+\" .\r\n- Windows: user installation now possible.\r\n- Bugfixe: for-idiom shows part of type definition as variable name in some cases.\r\n- Bugfixe: wrong cursor position for some templates.","3":"- New hotkeys \\+\" .\r\n- Windows: user installation now possible.\r\n- Bugfixe: for-idiom shows part of type definition as variable name in some cases.\r\n- Bugfixe: wrong cursor position for some templates.","package":"cvim.zip","4":"cvim.zip","src_id":"14305","5":"14305","creation_date":"1290182545","6":"1290182545"},{"0":"213","vim_version":"5.7","1":"5.7","script_version":"5.11","2":"5.11","version_comment":"- New tag {CURSOR} to avoid indent problems in a few cases.\r\n- Three hotkeys renamed \\rg -> \\rma , \\ri -> \\rpa ,  \\re -> \\rka (better to remember).\r\n- 'long long' added to the for-idioms.\r\n- Bugfixes: for-idiom shows type as variable name if no variable name was given.\r\n- Bugfixes: for-idiom inserts standard types with 2+ words wrong.\r\n- Bugfixes: multiline end-of-line comments have wrong position in some cases.\r\n- Bugfixes: local installation looks like a system-wide installation in seldom cases.","3":"- New tag {CURSOR} to avoid indent problems in a few cases.\r\n- Three hotkeys renamed \\rg -> \\rma , \\ri -> \\rpa ,  \\re -> \\rka (better to remember).\r\n- 'long long' added to the for-idioms.\r\n- Bugfixes: for-idiom shows type as variable name if no variable name was given.\r\n- Bugfixes: for-idiom inserts standard types with 2+ words wrong.\r\n- Bugfixes: multiline end-of-line comments have wrong position in some cases.\r\n- Bugfixes: local installation looks like a system-wide installation in seldom cases.","package":"cvim.zip","4":"cvim.zip","src_id":"13077","5":"13077","creation_date":"1275304530","6":"1275304530"},{"0":"213","vim_version":"7.0","1":"7.0","script_version":"5.10","2":"5.10","version_comment":"- The plugin now handles different template styles without editing and reloading the main template file.\r\n- The number of template styles is not limited. \r\n- New hotkey and ex-command to switch template styles.\r\n- Template styles can automatically be related to file extensions.\r\n- indent(1) errors will be presented in a quickfix error window.\r\n- Comment alignment improved.\r\n- Minor improvements.","3":"- The plugin now handles different template styles without editing and reloading the main template file.\r\n- The number of template styles is not limited. \r\n- New hotkey and ex-command to switch template styles.\r\n- Template styles can automatically be related to file extensions.\r\n- indent(1) errors will be presented in a quickfix error window.\r\n- Comment alignment improved.\r\n- Minor improvements.","package":"cvim.zip","4":"cvim.zip","src_id":"12311","5":"12311","creation_date":"1265378125","6":"1265378125"},{"0":"213","vim_version":"7.0","1":"7.0","script_version":"5.9","2":"5.9","version_comment":"+ Two additional hotkeys (+ ex commands) for preprocessor statements.\r\n+ Compile-link-run: improved error detection.\r\n+ Menu Run: hardcopy can print any buffer.\r\n+ Several minor improvements and bugfixes.","3":"+ Two additional hotkeys (+ ex commands) for preprocessor statements.\r\n+ Compile-link-run: improved error detection.\r\n+ Menu Run: hardcopy can print any buffer.\r\n+ Several minor improvements and bugfixes.","package":"cvim.zip","4":"cvim.zip","src_id":"11557","5":"11557","creation_date":"1256149396","6":"1256149396"},{"0":"213","vim_version":"7.0","1":"7.0","script_version":"5.8","2":"5.8","version_comment":"+ Hotkeys are shown in the menus.\r\n+ File browser for code snippets and templates choosable (2 global variables).\r\n+ Two new hotkeys: include file description (implementation, header).\r\n+ New menu item: namespace alias\r\n+ Bugfix: wrapper script for use of a xterm could not handle parameters containing blanks.\r\n+ Several minor improvements.","3":"+ Hotkeys are shown in the menus.\r\n+ File browser for code snippets and templates choosable (2 global variables).\r\n+ Two new hotkeys: include file description (implementation, header).\r\n+ New menu item: namespace alias\r\n+ Bugfix: wrapper script for use of a xterm could not handle parameters containing blanks.\r\n+ Several minor improvements.","package":"cvim.zip","4":"cvim.zip","src_id":"10910","5":"10910","creation_date":"1246343408","6":"1246343408"},{"0":"213","vim_version":"7.0","1":"7.0","script_version":"5.7","2":"5.7","version_comment":"+ 4 new hotkeys : insert file section comments (C\/C++\/H), special comments,\r\n  keyword comments.\r\n+ End-of-line comment adjustment improved.","3":"+ 4 new hotkeys : insert file section comments (C\/C++\/H), special comments,\r\n  keyword comments.\r\n+ End-of-line comment adjustment improved.","package":"cvim.zip","4":"cvim.zip","src_id":"10498","5":"10498","creation_date":"1241103985","6":"1241103985"},{"0":"213","vim_version":"7.0","1":"7.0","script_version":"5.6","2":"5.6","version_comment":"+ Jump targets (templates) and mapping Ctrl-j can be switched off.\r\n+ Yet unused jump targets will be highlighted after a file is opened.\r\n+ Statements menu: else block (key mapping \\se).\r\n+ Handling of <SPLIT> improved (templates).\r\n+ Minor improvements.","3":"+ Jump targets (templates) and mapping Ctrl-j can be switched off.\r\n+ Yet unused jump targets will be highlighted after a file is opened.\r\n+ Statements menu: else block (key mapping \\se).\r\n+ Handling of <SPLIT> improved (templates).\r\n+ Minor improvements.","package":"cvim.zip","4":"cvim.zip","src_id":"10354","5":"10354","creation_date":"1239039861","6":"1239039861"},{"0":"213","vim_version":"7.0","1":"7.0","script_version":"5.5","2":"5.5","version_comment":"+ Additional plugin-tags (jump targets in templates): <+text+>, <-text->.\r\n+ Additional mapping Ctrl-j : jump to these new targets.\r\n+ Template-file: additional macro |STYLE| and IF-ENDIF-construct to easily\r\n  choose between sets of templates.\r\n+ Additional mapping: auto-complete classical C comment (also multi-line).\r\n+ Additional mapping: auto-complete open block starting with {<CR> .\r\n+ Visual mode for date and time insertion (menu 'Comments').\r\n+ Visual mode for tags (submenu 'Comments->tags (plugin)').\r\n+ Bugfix: hotkey \\ica not working\r\n+ Bugfix: hotkey Shift-F2 for the alternate-plugin disappeared. ","3":"+ Additional plugin-tags (jump targets in templates): <+text+>, <-text->.\r\n+ Additional mapping Ctrl-j : jump to these new targets.\r\n+ Template-file: additional macro |STYLE| and IF-ENDIF-construct to easily\r\n  choose between sets of templates.\r\n+ Additional mapping: auto-complete classical C comment (also multi-line).\r\n+ Additional mapping: auto-complete open block starting with {<CR> .\r\n+ Visual mode for date and time insertion (menu 'Comments').\r\n+ Visual mode for tags (submenu 'Comments->tags (plugin)').\r\n+ Bugfix: hotkey \\ica not working\r\n+ Bugfix: hotkey Shift-F2 for the alternate-plugin disappeared. ","package":"cvim.zip","4":"cvim.zip","src_id":"9990","5":"9990","creation_date":"1234897841","6":"1234897841"},{"0":"213","vim_version":"7.0","1":"7.0","script_version":"5.4","2":"5.4","version_comment":"+ New hotkey \\+co inserts ' cout <<  << endl;'\r\n+ New menu item C++-menu: 'cout' replaces 'cout variable' and 'cout string'.\r\n+ Hotkey \\c\/ removed ( \\cc does the same).\r\n+ Bugfix: after an unsuccessful compilation screen sometimes garbled.","3":"+ New hotkey \\+co inserts ' cout <<  << endl;'\r\n+ New menu item C++-menu: 'cout' replaces 'cout variable' and 'cout string'.\r\n+ Hotkey \\c\/ removed ( \\cc does the same).\r\n+ Bugfix: after an unsuccessful compilation screen sometimes garbled.","package":"cvim.zip","4":"cvim.zip","src_id":"9679","5":"9679","creation_date":"1229346517","6":"1229346517"},{"0":"213","vim_version":"7.0","1":"7.0","script_version":"5.3","2":"5.3","version_comment":"+ Insertions work properly when folding is used.\r\n+ Menu items Idioms->for(...) : type declaration for loop variable possible (tab completion).\r\n+ Specification of command line arguments (Run->cmd. line arg.): filename completion active.\r\n+ New main menu item 'show manual' (hotkey \\hm): read manual for word under cursor. \r\n+ One hotkey renamed: \\h -> \\hp (help plugin)","3":"+ Insertions work properly when folding is used.\r\n+ Menu items Idioms->for(...) : type declaration for loop variable possible (tab completion).\r\n+ Specification of command line arguments (Run->cmd. line arg.): filename completion active.\r\n+ New main menu item 'show manual' (hotkey \\hm): read manual for word under cursor. \r\n+ One hotkey renamed: \\h -> \\hp (help plugin)","package":"cvim.zip","4":"cvim.zip","src_id":"9602","5":"9602","creation_date":"1228292805","6":"1228292805"},{"0":"213","vim_version":"7.0","1":"7.0","script_version":"5.2.1","2":"5.2.1","version_comment":"+ Bugfix: stray characters whith three dialogs\r\n+ Bugfix: Missing parameter in 2 internal function calls\r\n+ Menu items 'Snippets->edit local\/global templates' start an file browser (convenience).","3":"+ Bugfix: stray characters whith three dialogs\r\n+ Bugfix: Missing parameter in 2 internal function calls\r\n+ Menu items 'Snippets->edit local\/global templates' start an file browser (convenience).","package":"cvim.zip","4":"cvim.zip","src_id":"9146","5":"9146","creation_date":"1219061334","6":"1219061334"},{"0":"213","vim_version":"7.0","1":"7.0","script_version":"5.2","2":"5.2","version_comment":"+ Superfluous control characters for mode switching (menus, hotkeys) removed. Caused beeps.\r\n+ Template files (local\/global) can be opened from the snippet menu.\r\n+ Three new preprocessor statements.\r\n+ v-mode for RTTI-entries.","3":"+ Superfluous control characters for mode switching (menus, hotkeys) removed. Caused beeps.\r\n+ Template files (local\/global) can be opened from the snippet menu.\r\n+ Three new preprocessor statements.\r\n+ v-mode for RTTI-entries.","package":"cvim.zip","4":"cvim.zip","src_id":"9070","5":"9070","creation_date":"1217814575","6":"1217814575"},{"0":"213","vim_version":"7.0","1":"7.0","script_version":"5.1","2":"5.1","version_comment":"+ Definition and implementation of classes have now different templates and menu entries.\r\n+ Accessor methods (get\/set) can be generated.\r\n+ New templates: everything other than language keywords comes from a template (and is user changeable).","3":"+ Definition and implementation of classes have now different templates and menu entries.\r\n+ Accessor methods (get\/set) can be generated.\r\n+ New templates: everything other than language keywords comes from a template (and is user changeable).","package":"cvim.zip","4":"cvim.zip","src_id":"8437","5":"8437","creation_date":"1205323106","6":"1205323106"},{"0":"213","vim_version":"7.0","1":"7.0","script_version":"5.0.5","2":"5.0.5","version_comment":"+ Bugfix: on a few systems doubling of path components in the run command (F9).\r\n  Skip this upgrade if you do not have this problem.","3":"+ Bugfix: on a few systems doubling of path components in the run command (F9).\r\n  Skip this upgrade if you do not have this problem.","package":"cvim.zip","4":"cvim.zip","src_id":"7975","5":"7975","creation_date":"1195608918","6":"1195608918"},{"0":"213","vim_version":"7.0","1":"7.0","script_version":"5.0.4","2":"5.0.4","version_comment":"+ Format for the macros |DATE|, |TIME|, and |YEAR| can be defined by the user.\r\n+ Help text improved.","3":"+ Format for the macros |DATE|, |TIME|, and |YEAR| can be defined by the user.\r\n+ Help text improved.","package":"cvim.zip","4":"cvim.zip","src_id":"7949","5":"7949","creation_date":"1195197511","6":"1195197511"},{"0":"213","vim_version":"7.0","1":"7.0","script_version":"5.0.3","2":"5.0.3","version_comment":"+ Code snippets can now be used in the console mode (Vim without GUI).\r\n+ Bugfix: Possible conflict with 'indent' removed when inserting templates.","3":"+ Code snippets can now be used in the console mode (Vim without GUI).\r\n+ Bugfix: Possible conflict with 'indent' removed when inserting templates.","package":"cvim.zip","4":"cvim.zip","src_id":"7802","5":"7802","creation_date":"1192529408","6":"1192529408"},{"0":"213","vim_version":"7.0","1":"7.0","script_version":"5.0.2","2":"5.0.2","version_comment":"+ Bugfix: Prototype picker did not alway delete no longer used prototypes.\r\n+ Bugfix: Prototype picker removed template specializations from parameter lists.","3":"+ Bugfix: Prototype picker did not alway delete no longer used prototypes.\r\n+ Bugfix: Prototype picker removed template specializations from parameter lists.","package":"cvim.zip","4":"cvim.zip","src_id":"7740","5":"7740","creation_date":"1191381095","6":"1191381095"},{"0":"213","vim_version":"7.0","1":"7.0","script_version":"5.0.1","2":"5.0.1","version_comment":"+ Bugfix: autocmd setting can influence autocmd settings of OTHER plugins.","3":"+ Bugfix: autocmd setting can influence autocmd settings of OTHER plugins.","package":"cvim.zip","4":"cvim.zip","src_id":"7717","5":"7717","creation_date":"1190772710","6":"1190772710"},{"0":"213","vim_version":"7.0","1":"7.0","script_version":"5.0","2":"5.0","version_comment":"+ New template system. Now every menu item is user definable.\r\n+ Changes to allow a system-wide installation.\r\n+ A few hotkeys added and renamed.\r\n\r\n","3":"+ New template system. Now every menu item is user definable.\r\n+ Changes to allow a system-wide installation.\r\n+ A few hotkeys added and renamed.\r\n\r\n","package":"cvim.zip","4":"cvim.zip","src_id":"7682","5":"7682","creation_date":"1189990362","6":"1189990362"},{"0":"213","vim_version":"6.0","1":"6.0","script_version":"4.6.1","2":"4.6.1","version_comment":"+ New global variable to control the filetype of *.h header files (default is now 'cpp').\r\n+ Bugfix: properly resetting 'compiler' after using make, splint, and CodeCheck.","3":"+ New global variable to control the filetype of *.h header files (default is now 'cpp').\r\n+ Bugfix: properly resetting 'compiler' after using make, splint, and CodeCheck.","package":"cvim.zip","4":"cvim.zip","src_id":"7494","5":"7494","creation_date":"1186983656","6":"1186983656"},{"0":"213","vim_version":"6.0","1":"6.0","script_version":"4.6","2":"4.6","version_comment":"+ New insert mode mappings (comments, statements, preprocessing, idioms, C++).\r\n+ Some mappings renamed (easier to remember). \r\n+ New tag (basename of a file reduced to characters allowed in names).","3":"+ New insert mode mappings (comments, statements, preprocessing, idioms, C++).\r\n+ Some mappings renamed (easier to remember). \r\n+ New tag (basename of a file reduced to characters allowed in names).","package":"cvim.zip","4":"cvim.zip","src_id":"7168","5":"7168","creation_date":"1180086118","6":"1180086118"},{"0":"213","vim_version":"6.0","1":"6.0","script_version":"4.5","2":"4.5","version_comment":"+ New menu item and hotkey for the (re)alignement of end-of-line comments.\r\n+ Hotkey \\cn removed. Only one menu item for end-of-line comments left.\r\n+ Changed hotkeys: \\ce -> \\cl and \\cl -> \\cs .\r\n+ Three new tags (giving the basename of a file) for writing template files.\r\n+ Prototype picker handles template methods.\r\n+ Bugfix: splint works now under Windows.\r\n+ Minor improvements.","3":"+ New menu item and hotkey for the (re)alignement of end-of-line comments.\r\n+ Hotkey \\cn removed. Only one menu item for end-of-line comments left.\r\n+ Changed hotkeys: \\ce -> \\cl and \\cl -> \\cs .\r\n+ Three new tags (giving the basename of a file) for writing template files.\r\n+ Prototype picker handles template methods.\r\n+ Bugfix: splint works now under Windows.\r\n+ Minor improvements.","package":"cvim.zip","4":"cvim.zip","src_id":"7020","5":"7020","creation_date":"1177388784","6":"1177388784"},{"0":"213","vim_version":"6.0","1":"6.0","script_version":"4.4","2":"4.4","version_comment":"+ PLUGIN DIRECTORIES REARRANGED.\r\n+ main- and for-idiom have a visual mode now.\r\n+ Four new commands (command line) to control the comment style.\r\n+ Comment style (C\/C++) can automatically follow the filetype.\r\n+ Bugfix: empty new file after removing the header template can't be closed.\r\n+ Bugfix : Tools entry missing when root menu not shown from the start.\r\n+ Minor improvements.","3":"+ PLUGIN DIRECTORIES REARRANGED.\r\n+ main- and for-idiom have a visual mode now.\r\n+ Four new commands (command line) to control the comment style.\r\n+ Comment style (C\/C++) can automatically follow the filetype.\r\n+ Bugfix: empty new file after removing the header template can't be closed.\r\n+ Bugfix : Tools entry missing when root menu not shown from the start.\r\n+ Minor improvements.","package":"cvim.zip","4":"cvim.zip","src_id":"6765","5":"6765","creation_date":"1172048377","6":"1172048377"},{"0":"213","vim_version":"6.0","1":"6.0","script_version":"4.3","2":"4.3","version_comment":"+ New key mappings for preprocessor statements. \r\n+ Source code analysing tool CodeCheck (Trademark) integrated\r\n+ New preprocessor menu.\r\n+ Bugfix: indent under Windows.\r\n+ Minor improvements.\r\n","3":"+ New key mappings for preprocessor statements. \r\n+ Source code analysing tool CodeCheck (Trademark) integrated\r\n+ New preprocessor menu.\r\n+ Bugfix: indent under Windows.\r\n+ Minor improvements.\r\n","package":"cvim.zip","4":"cvim.zip","src_id":"6430","5":"6430","creation_date":"1163727610","6":"1163727610"},{"0":"213","vim_version":"6.0","1":"6.0","script_version":"4.2.1","2":"4.2.1","version_comment":"+ Bugfix: change needed for some menu names after patch 7.0.054 .","3":"+ Bugfix: change needed for some menu names after patch 7.0.054 .","package":"cvim.zip","4":"cvim.zip","src_id":"6100","5":"6100","creation_date":"1156559962","6":"1156559962"},{"0":"213","vim_version":"6.0","1":"6.0","script_version":"4.2","2":"4.2","version_comment":"+ Setting the starting column for trailing comments improved.\r\n+ Small bug in block uncommenting fixed.\r\n+ Mac OS X : circumvent a Vim bug which caused a crash when loading plugin version 4.1\r\n+ File syntax\/c.vim removed (but see help in csupport.txt).","3":"+ Setting the starting column for trailing comments improved.\r\n+ Small bug in block uncommenting fixed.\r\n+ Mac OS X : circumvent a Vim bug which caused a crash when loading plugin version 4.1\r\n+ File syntax\/c.vim removed (but see help in csupport.txt).","package":"cvim.zip","4":"cvim.zip","src_id":"6029","5":"6029","creation_date":"1154567247","6":"1154567247"},{"0":"213","vim_version":"6.0","1":"6.0","script_version":"4.1","2":"4.1","version_comment":"+ A complete switch statement can be made from a list of labels.\r\n+ Additional cases can be made from a list of labels.\r\n+ Small bug in line end commenting fixed.\r\n+ Minor improvements.","3":"+ A complete switch statement can be made from a list of labels.\r\n+ Additional cases can be made from a list of labels.\r\n+ Small bug in line end commenting fixed.\r\n+ Minor improvements.","package":"cvim.zip","4":"cvim.zip","src_id":"5895","5":"5895","creation_date":"1151569399","6":"1151569399"},{"0":"213","vim_version":"6.0","1":"6.0","script_version":"4.0","2":"4.0","version_comment":"+ Kernighan & Ritchie style for block statements can be enabled.\r\n+ Changes to make plugin compatible with Vim 7.\r\n+ Set C\/C++ file type for source files which should not be preprocessed (*.i, *.ii).\r\n+ Some minor improvements.","3":"+ Kernighan & Ritchie style for block statements can be enabled.\r\n+ Changes to make plugin compatible with Vim 7.\r\n+ Set C\/C++ file type for source files which should not be preprocessed (*.i, *.ii).\r\n+ Some minor improvements.","package":"cvim.zip","4":"cvim.zip","src_id":"5549","5":"5549","creation_date":"1144894808","6":"1144894808"},{"0":"213","vim_version":"6.0","1":"6.0","script_version":"3.11","2":"3.11","version_comment":"+ Hotkeys and an accompanying reference card added.\r\n+ Preparation for syntax based folding.\r\n+ Some minor improvements.","3":"+ Hotkeys and an accompanying reference card added.\r\n+ Preparation for syntax based folding.\r\n+ Some minor improvements.","package":"cvim.zip","4":"cvim.zip","src_id":"5462","5":"5462","creation_date":"1142817127","6":"1142817127"},{"0":"213","vim_version":"6.0","1":"6.0","script_version":"3.10","2":"3.10","version_comment":"+ Remove \"#if 0 ... #endif\" from the inside. \r\n+ Change C comments to C++ comments and vice versa.\r\n+ try..catch \/ catch \/ catch(...)  now can be set surround a marked area.\r\n+ Prototype picking improved (for C++).\r\n+ A hardcopy shows the localized date and time in the header line.\r\n+ New help menu entry in the main menu of this plugin (shows the plugin documentation).\r\n+ Switch between corresponding source and header files with <S-F2> if the plugin a.vim\r\n  is present.\r\n+ Plugin can be used with autocompletion for (, [, and { .","3":"+ Remove \"#if 0 ... #endif\" from the inside. \r\n+ Change C comments to C++ comments and vice versa.\r\n+ try..catch \/ catch \/ catch(...)  now can be set surround a marked area.\r\n+ Prototype picking improved (for C++).\r\n+ A hardcopy shows the localized date and time in the header line.\r\n+ New help menu entry in the main menu of this plugin (shows the plugin documentation).\r\n+ Switch between corresponding source and header files with <S-F2> if the plugin a.vim\r\n  is present.\r\n+ Plugin can be used with autocompletion for (, [, and { .","package":"cvim.zip","4":"cvim.zip","src_id":"5003","5":"5003","creation_date":"1138247014","6":"1138247014"},{"0":"213","vim_version":"6.0","1":"6.0","script_version":"3.9.1","2":"3.9.1","version_comment":"+ Doubling of file header for new c- and h-files under Windows fixed (Thanks to Fabricio C A Oliveira).\r\n+ Tiny bug in the file open idioms fixed.","3":"+ Doubling of file header for new c- and h-files under Windows fixed (Thanks to Fabricio C A Oliveira).\r\n+ Tiny bug in the file open idioms fixed.","package":"cvim.zip","4":"cvim.zip","src_id":"4860","5":"4860","creation_date":"1133664987","6":"1133664987"},{"0":"213","vim_version":"6.0","1":"6.0","script_version":"3.9","2":"3.9","version_comment":"+ Formatter 'indent' integrated.\r\n+ Bugfix in the automatic header insertion.\r\n+ Assert idiom added.\r\n+ #if 0 ... #endif statement for blocking out code added.\r\n+ Minor stylistic improvements in some idioms.","3":"+ Formatter 'indent' integrated.\r\n+ Bugfix in the automatic header insertion.\r\n+ Assert idiom added.\r\n+ #if 0 ... #endif statement for blocking out code added.\r\n+ Minor stylistic improvements in some idioms.","package":"cvim.zip","4":"cvim.zip","src_id":"4714","5":"4714","creation_date":"1130839203","6":"1130839203"},{"0":"213","vim_version":"6.0","1":"6.0","script_version":"3.8.2","2":"3.8.2","version_comment":"+ Screen update problem solved: color inversion under FC4 (Thanks to Bernie Barton).\r\n+ RTTI menu : additional v-mode.\r\n+ Statement menu and C++ menu rearranged.\r\n+ Include guard : name generation improved.\r\n+ File header templates will be included for additional file extensions (cp, cxx, c++, ...).","3":"+ Screen update problem solved: color inversion under FC4 (Thanks to Bernie Barton).\r\n+ RTTI menu : additional v-mode.\r\n+ Statement menu and C++ menu rearranged.\r\n+ Include guard : name generation improved.\r\n+ File header templates will be included for additional file extensions (cp, cxx, c++, ...).","package":"cvim.zip","4":"cvim.zip","src_id":"4553","5":"4553","creation_date":"1125905178","6":"1125905178"},{"0":"213","vim_version":"6.0","1":"6.0","script_version":"3.8.1","2":"3.8.1","version_comment":"+ More C++ output manipulators; manipulator insertion more intuitive.\r\n+ Output into buffer: cursor goes to top of file.\r\n+ Makefile template improved (code snippet).\r\n+ Some minor improvements.","3":"+ More C++ output manipulators; manipulator insertion more intuitive.\r\n+ Output into buffer: cursor goes to top of file.\r\n+ Makefile template improved (code snippet).\r\n+ Some minor improvements.","package":"cvim.zip","4":"cvim.zip","src_id":"4472","5":"4472","creation_date":"1123482919","6":"1123482919"},{"0":"213","vim_version":"6.0","1":"6.0","script_version":"3.8","2":"3.8","version_comment":"+ Windows support. Most features are available under Windows now.","3":"+ Windows support. Most features are available under Windows now.","package":"cvim.zip","4":"cvim.zip","src_id":"4329","5":"4329","creation_date":"1117522515","6":"1117522515"},{"0":"213","vim_version":"6.0","1":"6.0","script_version":"3.7.2","2":"3.7.2","version_comment":"+ Run buffer through splint (A tool for statically checking C programs; see\r\n  http:\/\/www.splint.org). An error window will be opened; quickfix commands can be used.\r\n+ Set buffer related command line arguments for splint.\r\n+ Line end comments start in a fixed column (can be set from the menu).\r\n+ Spaces in path names and file names are now possible.\r\n+ Template files and snippet files are no longer kept in the list of alternate files.\r\n+ Some minor improvements.","3":"+ Run buffer through splint (A tool for statically checking C programs; see\r\n  http:\/\/www.splint.org). An error window will be opened; quickfix commands can be used.\r\n+ Set buffer related command line arguments for splint.\r\n+ Line end comments start in a fixed column (can be set from the menu).\r\n+ Spaces in path names and file names are now possible.\r\n+ Template files and snippet files are no longer kept in the list of alternate files.\r\n+ Some minor improvements.","package":"cvim.zip","4":"cvim.zip","src_id":"4244","5":"4244","creation_date":"1115260693","6":"1115260693"},{"0":"213","vim_version":"6.0","1":"6.0","script_version":"3.7.1","2":"3.7.1","version_comment":"+ Bug fixed (comand line arguments not passed to the executable).\r\n+ File extension for executables can be set.\r\n+ Minor improvements.","3":"+ Bug fixed (comand line arguments not passed to the executable).\r\n+ File extension for executables can be set.\r\n+ Minor improvements.","package":"cvim.zip","4":"cvim.zip","src_id":"3719","5":"3719","creation_date":"1103590629","6":"1103590629"},{"0":"213","vim_version":"6.0","1":"6.0","script_version":"3.7","2":"3.7","version_comment":"+ Running a program:\r\n  (1) Run program from the gVim command line.\r\n  (2) Run program and direct the output into a window with name \"C-Output\". \r\n  (3) Run program in an xterm.\r\n+ Command line arguments are now buffer related (each buffer can have its own arguments).\r\n+ Code snippets can be protected from being indented during insertion. \r\n+ Picked up prototypes will be deleted after insertion.\r\n+ A code snippet with the file name extension \"ni\" or \"noindent\" will not be\r\n  indented on insertion.\r\n+ for- and calloc-\/malloc-idioms improved.\r\n+ Bug fixed (word list handling).","3":"+ Running a program:\r\n  (1) Run program from the gVim command line.\r\n  (2) Run program and direct the output into a window with name \"C-Output\". \r\n  (3) Run program in an xterm.\r\n+ Command line arguments are now buffer related (each buffer can have its own arguments).\r\n+ Code snippets can be protected from being indented during insertion. \r\n+ Picked up prototypes will be deleted after insertion.\r\n+ A code snippet with the file name extension \"ni\" or \"noindent\" will not be\r\n  indented on insertion.\r\n+ for- and calloc-\/malloc-idioms improved.\r\n+ Bug fixed (word list handling).","package":"cvim.zip","4":"cvim.zip","src_id":"3711","5":"3711","creation_date":"1103250543","6":"1103250543"},{"0":"213","vim_version":"6.0","1":"6.0","script_version":"3.6","2":"3.6","version_comment":"+ Installation simplified. \n+ for-loop-idiom asks for control variable, initial value, ...\n+ malloc-idiom asks for pointer variable and size.\n+ Toggling the comment style works correct again.\n+ Empty error windows will be closed.\n+ Prototype picker removes trailing parts of the function body if marked.\n+ The dialog windows (GUI) have been replaced by more flexible command line inputs.\n+ The undocumented and unnecessary hot key F12 has been removed.\n+ Extension to ctags + taglist shows makefile targets and qmake targets.","3":"+ Installation simplified. \n+ for-loop-idiom asks for control variable, initial value, ...\n+ malloc-idiom asks for pointer variable and size.\n+ Toggling the comment style works correct again.\n+ Empty error windows will be closed.\n+ Prototype picker removes trailing parts of the function body if marked.\n+ The dialog windows (GUI) have been replaced by more flexible command line inputs.\n+ The undocumented and unnecessary hot key F12 has been removed.\n+ Extension to ctags + taglist shows makefile targets and qmake targets.","package":"cvim.zip","4":"cvim.zip","src_id":"3205","5":"3205","creation_date":"1089102591","6":"1089102591"},{"0":"213","vim_version":"6.0","1":"6.0","script_version":"3.5","2":"3.5","version_comment":"+ Aligned line end comments for consecutive lines.\r\n+ Improved prototype picker removes comments.\r\n+ Picked up prototypes can be shown.\r\n+ Uncomment more than one block at once.\r\n+ 3 new idioms.\r\n+ Help file improved .","3":"+ Aligned line end comments for consecutive lines.\r\n+ Improved prototype picker removes comments.\r\n+ Picked up prototypes can be shown.\r\n+ Uncomment more than one block at once.\r\n+ 3 new idioms.\r\n+ Help file improved .","package":"cvim.zip","4":"cvim.zip","src_id":"2902","5":"2902","creation_date":"1080891779","6":"1080891779"},{"0":"213","vim_version":"6.0","1":"6.0","script_version":"3.4","2":"3.4","version_comment":"+ The following constructs are now read as templates from files: \n   class, class using new, template class, template class using new, error class\n+ The preprocessor statements #if... and the function idiom include marked lines when invoked in visual mode.\n+ All hotkeys are only defined for C\/C++ files (file type plugin added).\n+ Only one C\/C++ entry in the gVim root menu (can be disabled).\n+ Two new global variables: C_Dictionary_File, C_MenuHeader .\n+ Install script added.\n+ Customization improved. \n+ Documentation improved (help file added).\n+ Bug fix (template file handling)","3":"+ The following constructs are now read as templates from files: \n   class, class using new, template class, template class using new, error class\n+ The preprocessor statements #if... and the function idiom include marked lines when invoked in visual mode.\n+ All hotkeys are only defined for C\/C++ files (file type plugin added).\n+ Only one C\/C++ entry in the gVim root menu (can be disabled).\n+ Two new global variables: C_Dictionary_File, C_MenuHeader .\n+ Install script added.\n+ Customization improved. \n+ Documentation improved (help file added).\n+ Bug fix (template file handling)","package":"cvim.zip","4":"cvim.zip","src_id":"2628","5":"2628","creation_date":"1072415743","6":"1072415743"},{"0":"213","vim_version":"6.0","1":"6.0","script_version":"3.1","2":"3.1","version_comment":"+ When the comment style \"C\" is active the menu entry \"Comments.code->comment\" \n  turns a marked region in one multiline C-comment.\n+ The menu entry \"Comments.comment->code\"  turns marked multiline C-comment   back into code.\n+ A marked region can be surrounded by a for-, if, if-else, while-, do-while-statement  (with indentation).\n+ The menu entry \"Snippets.make prototype\" makes a C- or C++-prototype from \n  the current line or marked region and puts it in an internal buffer.\n+ The menu entry \"Snippets.add prototype\" also makes a C- or C++-prototype from \n  the current line or a marked region and adds it to the internal buffer.\n+ The menu entry \"Snippets.put prototype\" inserts all gathered prototypes    below the current line. \n+ Tag substitution rewritten (Some characters in a substitution text for a tag \n  prevented the tag from being substituted).","3":"+ When the comment style \"C\" is active the menu entry \"Comments.code->comment\" \n  turns a marked region in one multiline C-comment.\n+ The menu entry \"Comments.comment->code\"  turns marked multiline C-comment   back into code.\n+ A marked region can be surrounded by a for-, if, if-else, while-, do-while-statement  (with indentation).\n+ The menu entry \"Snippets.make prototype\" makes a C- or C++-prototype from \n  the current line or marked region and puts it in an internal buffer.\n+ The menu entry \"Snippets.add prototype\" also makes a C- or C++-prototype from \n  the current line or a marked region and adds it to the internal buffer.\n+ The menu entry \"Snippets.put prototype\" inserts all gathered prototypes    below the current line. \n+ Tag substitution rewritten (Some characters in a substitution text for a tag \n  prevented the tag from being substituted).","package":"cvim.zip","4":"cvim.zip","src_id":"2032","5":"2032","creation_date":"1054380012","6":"1054380012"},{"0":"213","vim_version":"6.0","1":"6.0","script_version":"3.0","2":"3.0","version_comment":"+ C-style comments AND C++-style comments are supported now.\n+ The menu entry 'Comments->Comment style ..' switches the styles (toggle).\n+ Block comments are now read as templates or skeletons from files:\n    Frame Block,        Function Description,  Method Description,\n    Class Description,  H+file header,         C\/C++-file header\n+ These templates can contain tags like |FILENAME|, |AUTHOR| etc. which are replaced\n  after reading (KDevelop templates can be used without any change).\n+ indentation: multiline inserts and code snippets will be indented after insertion.\n+ Most menu entries are now also active in normal mode.\n+ new menu items:  includes for the C99 header, \n  includes for the standard C++ header, \n  includes for the C++ version of the Standard C Library header,\n  multiline C comment,  vim modeline\n+ Reading the templates is done in one function which can be called in an autocmd.\n+ Code cleanup: register z no longer used. Most function calls are silent now.","3":"+ C-style comments AND C++-style comments are supported now.\n+ The menu entry 'Comments->Comment style ..' switches the styles (toggle).\n+ Block comments are now read as templates or skeletons from files:\n    Frame Block,        Function Description,  Method Description,\n    Class Description,  H+file header,         C\/C++-file header\n+ These templates can contain tags like |FILENAME|, |AUTHOR| etc. which are replaced\n  after reading (KDevelop templates can be used without any change).\n+ indentation: multiline inserts and code snippets will be indented after insertion.\n+ Most menu entries are now also active in normal mode.\n+ new menu items:  includes for the C99 header, \n  includes for the standard C++ header, \n  includes for the C++ version of the Standard C Library header,\n  multiline C comment,  vim modeline\n+ Reading the templates is done in one function which can be called in an autocmd.\n+ Code cleanup: register z no longer used. Most function calls are silent now.","package":"cvim.zip","4":"cvim.zip","src_id":"1947","5":"1947","creation_date":"1051517110","6":"1051517110"},{"0":"213","vim_version":"6.0","1":"6.0","script_version":"2.8.1","2":"2.8.1","version_comment":"- menus appear immediately after loading the plugin\n- additional word lists for keyword completion (optional):\n    C\/C++ -keywords\n    German words (for commenting sources)\n    K&R-Book: Words from the table of content (for commenting sources)\n    Standard Template Library (STL):  method names and type names\n    XFORMS library: macro and function names\n- additional settings for .vimrc and .gvimrc (optional)","3":"- menus appear immediately after loading the plugin\n- additional word lists for keyword completion (optional):\n    C\/C++ -keywords\n    German words (for commenting sources)\n    K&R-Book: Words from the table of content (for commenting sources)\n    Standard Template Library (STL):  method names and type names\n    XFORMS library: macro and function names\n- additional settings for .vimrc and .gvimrc (optional)","package":"cvim.zip","4":"cvim.zip","src_id":"1781","5":"1781","creation_date":"1046928013","6":"1046928013"},{"0":"213","vim_version":"6.0","1":"6.0","script_version":"2.8","2":"2.8","version_comment":"- code snippet support: read, write, edit code snippets in a separate directory\n- specify command line arguments for make\n- hardcopy: print whole buffer or a highlighted part of it into a file (Postscript)\n- new menu entry  \"fscanf( infile, \"\", & );\"  after code for opening a file with pointer \"infile\" is inserted\n- new menu entry  \"fprintf( outfile, \"\\n\",  );\"  after code for opening a file with pointer \"outfile\" is inserted\n","3":"- code snippet support: read, write, edit code snippets in a separate directory\n- specify command line arguments for make\n- hardcopy: print whole buffer or a highlighted part of it into a file (Postscript)\n- new menu entry  \"fscanf( infile, \"\", & );\"  after code for opening a file with pointer \"infile\" is inserted\n- new menu entry  \"fprintf( outfile, \"\\n\",  );\"  after code for opening a file with pointer \"outfile\" is inserted\n","package":"c.vim","4":"c.vim","src_id":"1748","5":"1748","creation_date":"1045478699","6":"1045478699"},{"0":"213","vim_version":"6.0","1":"6.0","script_version":"2.6","2":"2.6","version_comment":"- separation of file section comments in 2 new submenus\n   'C-File-Sections' and 'H-File-Sections'\n- class comment\n- method comment\n- keyword comments and special comments are now in submenus\n- new hot key to run make\n- word list for C\/C++ word completion (optional)\n- some optional vimrc- and gvimrc-entries in two files (optional)\n- minor improvements and corrections","3":"- separation of file section comments in 2 new submenus\n   'C-File-Sections' and 'H-File-Sections'\n- class comment\n- method comment\n- keyword comments and special comments are now in submenus\n- new hot key to run make\n- word list for C\/C++ word completion (optional)\n- some optional vimrc- and gvimrc-entries in two files (optional)\n- minor improvements and corrections","package":"cvim.zip","4":"cvim.zip","src_id":"988","5":"988","creation_date":"1025746250","6":"1025746250"},{"0":"213","vim_version":"6.0","1":"6.0","script_version":"2.1","2":"2.1","version_comment":"- include all file section headers at once\n- insert empty block\n- 2 additional loops\n- includes for all Standard C Library header files\n- minor internal improvements\n","3":"- include all file section headers at once\n- insert empty block\n- 2 additional loops\n- includes for all Standard C Library header files\n- minor internal improvements\n","package":"c.vim","4":"c.vim","src_id":"758","5":"758","creation_date":"1017913010","6":"1017913010"},{"0":"213","vim_version":"6.0","1":"6.0","script_version":"2.0.3","2":"2.0.3","version_comment":"(1) 4 new keyword comments\r\n(2) code->comments does no longer mark  the first character in all lines","3":"(1) 4 new keyword comments\r\n(2) code->comments does no longer mark  the first character in all lines","package":"c.vim","4":"c.vim","src_id":"658","5":"658","creation_date":"1015469074","6":"1015469074"},{"0":"213","vim_version":"6.0","1":"6.0","script_version":"2.0","2":"2.0","version_comment":"Initial upload","3":"Initial upload","package":"c.vim","4":"c.vim","src_id":"579","5":"579","creation_date":"1013564701","6":"1013564701"}]},"212":{"script_id":"212","0":"212","script_name":"linuxmag.vim","1":"linuxmag.vim","script_type":"syntax","2":"syntax","summary":"linuxmag.vim is a syntax highlighting file for Linux Magazine articles","3":"linuxmag.vim is a syntax highlighting file for Linux Magazine articles","description":"\r\nIf you ever find yourself writing an article for Linux Magazine,\r\ntry this syntax highlighting file out.  It understands the mark-up\r\nconventions used by the editors there.  A short overview of the\r\nmark-up format is included in the archive.\r\n\r\n\r\n","4":"\r\nIf you ever find yourself writing an article for Linux Magazine,\r\ntry this syntax highlighting file out.  It understands the mark-up\r\nconventions used by the editors there.  A short overview of the\r\nmark-up format is included in the archive.\r\n\r\n\r\n","install_details":"Copy linuxmag.vim to ~\/.vim\/syntax and whenever you're editing\r\nan article for Linux Magazine, do the following in vim:\r\n\r\n    :setf linuxmag\r\n\r\n","5":"Copy linuxmag.vim to ~\/.vim\/syntax and whenever you're editing\r\nan article for Linux Magazine, do the following in vim:\r\n\r\n    :setf linuxmag\r\n\r\n","first_name":"John","6":"John","last_name":"Beppu","7":"Beppu","releases":[{"0":"212","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"linuxmag-1.0.tar.gz","4":"linuxmag-1.0.tar.gz","src_id":"578","5":"578","creation_date":"1013481759","6":"1013481759"}]},"211":{"script_id":"211","0":"211","script_name":"sokoban.vim","1":"sokoban.vim","script_type":"game","2":"game","summary":"Sokoban Game for Vim!","3":"Sokoban Game for Vim!","description":"The goal of VimSokoban is to push all the packages ($) into the  home area (.) of each level using hjkl keys or the arrow keys. \r\nThe arrow keys move the player (X) in the  corresponding direction, pushing a package if it is in the way and there is a clear \r\nspace on the other side.\r\n\r\nUse the \r\n:Sokoban       - or -    :Sokoban <level num>     (no split window)\r\n:SokobanH     - or -    :SokobanH <level num>   (horizontal split window)\r\n:SokobanV     - or -    :SokobanV <level num>   (vertical split window)\r\ncommands to start the game\r\n\r\nh or <Left> - move the man left\r\nj or <Down> - move the man down\r\nk or <Up> - move the man up\r\nl or <Right> - move the man right\r\nr - restart level\r\nn - next level\r\np - previous level\r\nu - undo move\r\n\r\nLevels came from the xsokoban distribution which is in the public domain.\r\n http:\/\/www.cs.cornell.edu\/andru\/xsokoban.html\r\n\r\nTake a look at VIM Tetris (vimscript#172) too....the game which started the VIM Game revolution :) ","4":"The goal of VimSokoban is to push all the packages ($) into the  home area (.) of each level using hjkl keys or the arrow keys. \r\nThe arrow keys move the player (X) in the  corresponding direction, pushing a package if it is in the way and there is a clear \r\nspace on the other side.\r\n\r\nUse the \r\n:Sokoban       - or -    :Sokoban <level num>     (no split window)\r\n:SokobanH     - or -    :SokobanH <level num>   (horizontal split window)\r\n:SokobanV     - or -    :SokobanV <level num>   (vertical split window)\r\ncommands to start the game\r\n\r\nh or <Left> - move the man left\r\nj or <Down> - move the man down\r\nk or <Up> - move the man up\r\nl or <Right> - move the man right\r\nr - restart level\r\nn - next level\r\np - previous level\r\nu - undo move\r\n\r\nLevels came from the xsokoban distribution which is in the public domain.\r\n http:\/\/www.cs.cornell.edu\/andru\/xsokoban.html\r\n\r\nTake a look at VIM Tetris (vimscript#172) too....the game which started the VIM Game revolution :) ","install_details":"Run `tar -zxf VimSokoban.tar.gz`, this will unpack the installation into the VimSokoban directory. Contained in that directory \r\nare the levels and the sokoban.vim script. Simply add sokoban.vim to your favorite vim plugin directory or source it directly.  \r\nThe directory containing the levels is found as follows, \r\n1) if g:SokobanLevelDirectory is set that directory is used\r\n2) if $VIMSOKOBANDIR is set that directory is used\r\n3) if $HOME\/VimSokoban exists it is used\r\n4) on WINDOWS, if c:\\\\VimSokoban exists it is used\r\n5) if a VimSokoban directory exists below the directory where the script lives exists it is used. (this means that if sokoban.vim \r\n    is in your plugin directory you can put the levels into a directory called VimSokoban in your plugin directory)\r\n6) Finally, the directory where the script lives is considered. (this means that if you have the levels and the sokoban.vim \r\n    script in the same directory it should be able to find the levels)\r\n\r\n(when setting g:SokobanLevelDirectory or $VIMSOKOBANDIR make sure that it contains a trailing \/ or \\ (unix\/windows). \r\n\r\nYou will need a VIM window which is 80 characters wide and about 35 lines. ","5":"Run `tar -zxf VimSokoban.tar.gz`, this will unpack the installation into the VimSokoban directory. Contained in that directory \r\nare the levels and the sokoban.vim script. Simply add sokoban.vim to your favorite vim plugin directory or source it directly.  \r\nThe directory containing the levels is found as follows, \r\n1) if g:SokobanLevelDirectory is set that directory is used\r\n2) if $VIMSOKOBANDIR is set that directory is used\r\n3) if $HOME\/VimSokoban exists it is used\r\n4) on WINDOWS, if c:\\\\VimSokoban exists it is used\r\n5) if a VimSokoban directory exists below the directory where the script lives exists it is used. (this means that if sokoban.vim \r\n    is in your plugin directory you can put the levels into a directory called VimSokoban in your plugin directory)\r\n6) Finally, the directory where the script lives is considered. (this means that if you have the levels and the sokoban.vim \r\n    script in the same directory it should be able to find the levels)\r\n\r\n(when setting g:SokobanLevelDirectory or $VIMSOKOBANDIR make sure that it contains a trailing \/ or \\ (unix\/windows). \r\n\r\nYou will need a VIM window which is 80 characters wide and about 35 lines. ","first_name":"Mike","6":"Mike","last_name":"Sharpe","7":"Sharpe","releases":[{"0":"211","vim_version":"6.0","1":"6.0","script_version":"1.3","2":"1.3","version_comment":"set buftype and nomodifiable, remeber progress though levels, record high scores for each level.","3":"set buftype and nomodifiable, remeber progress though levels, record high scores for each level.","package":"VimSokoban.tar.gz","4":"VimSokoban.tar.gz","src_id":"656","5":"656","creation_date":"1015435442","6":"1015435442"},{"0":"211","vim_version":"6.0","1":"6.0","script_version":"1.2","2":"1.2","version_comment":"fix bug in routine which detected when a level was complete. This meant some levels were not detected as complete e.g. level 11.","3":"fix bug in routine which detected when a level was complete. This meant some levels were not detected as complete e.g. level 11.","package":"VimSokoban.tar.gz","4":"VimSokoban.tar.gz","src_id":"620","5":"620","creation_date":"1014249900","6":"1014249900"},{"0":"211","vim_version":"6.0","1":"6.0","script_version":"1.1b","2":"1.1b","version_comment":"Use the <sfile> expansion to try to locate the level directory.","3":"Use the <sfile> expansion to try to locate the level directory.","package":"VimSokoban.tar.gz","4":"VimSokoban.tar.gz","src_id":"615","5":"615","creation_date":"1014144705","6":"1014144705"},{"0":"211","vim_version":"6.0","1":"6.0","script_version":"1.1a","2":"1.1a","version_comment":"Minor tweaks to help windows find the level\r\ndirectory a little more smoothly. I hope this works.","3":"Minor tweaks to help windows find the level\r\ndirectory a little more smoothly. I hope this works.","package":"VimSokoban.tar.gz","4":"VimSokoban.tar.gz","src_id":"594","5":"594","creation_date":"1013799547","6":"1013799547"},{"0":"211","vim_version":"6.0","1":"6.0","script_version":"1.1","2":"1.1","version_comment":"Map the j\/k keys correctly.\r\nAdded SokobanH and SokobanV commands which control how the screen is split","3":"Map the j\/k keys correctly.\r\nAdded SokobanH and SokobanV commands which control how the screen is split","package":"VimSokoban.tar.gz","4":"VimSokoban.tar.gz","src_id":"586","5":"586","creation_date":"1013635578","6":"1013635578"},{"0":"211","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"VimSokoban.tar.gz","4":"VimSokoban.tar.gz","src_id":"577","5":"577","creation_date":"1013466335","6":"1013466335"}]},"210":{"script_id":"210","0":"210","script_name":"fine_blue.vim","1":"fine_blue.vim","script_type":"color scheme","2":"color scheme","summary":"Colorscheme with light background.","3":"Colorscheme with light background.","description":"If you want to update this file, please download rainbow.zip.\r\nhttp:\/\/www.vim.org\/script.php?script_id=463\r\n\r\nIf you edit this like\r\n:%s\/#\\(\\x\\x\\)\\(\\x\\x\\)\\(\\x\\x\\)\/#\\3\\2\\1\/g | %s\/blue\/red\/ | w fine_red.vim\r\nyou can get fine_red.vim!\r\n\r\nNOTE:This colorscheme is GUI only.","4":"If you want to update this file, please download rainbow.zip.\r\nhttp:\/\/www.vim.org\/script.php?script_id=463\r\n\r\nIf you edit this like\r\n:%s\/#\\(\\x\\x\\)\\(\\x\\x\\)\\(\\x\\x\\)\/#\\3\\2\\1\/g | %s\/blue\/red\/ | w fine_red.vim\r\nyou can get fine_red.vim!\r\n\r\nNOTE:This colorscheme is GUI only.","install_details":"Save as colos\/fine_blue.vim under 'runtimepath'","5":"Save as colos\/fine_blue.vim under 'runtimepath'","first_name":"Takeshi","6":"Takeshi","last_name":"Zeniya","7":"Zeniya","releases":[{"0":"210","vim_version":"6.0","1":"6.0","script_version":"1.2","2":"1.2","version_comment":"Add \"Underlined\", Change \"WarningMsg\" \"ErrorMsg\" ... etc","3":"Add \"Underlined\", Change \"WarningMsg\" \"ErrorMsg\" ... etc","package":"fine_blue.vim","4":"fine_blue.vim","src_id":"664","5":"664","creation_date":"1015567154","6":"1015567154"},{"0":"210","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"fine_blue.vim","4":"fine_blue.vim","src_id":"574","5":"574","creation_date":"1013323843","6":"1013323843"}]},"209":{"script_id":"209","0":"209","script_name":"Perldoc.vim","1":"Perldoc.vim","script_type":"ftplugin","2":"ftplugin","summary":"perldoc command from vim","3":"perldoc command from vim","description":"The Perldoc.vim plugin is a command + function that enables the perldoc command to be used from within the Vim text editor.  When activated the Perldoc command opens a new window at the top of the screen and places the output of the perldoc command into that window. This read-only window is just a Vim window, so you can perform all of the normal commands that you can in Vim - such as searching for a word or expression, yanking examples and code snippets.","4":"The Perldoc.vim plugin is a command + function that enables the perldoc command to be used from within the Vim text editor.  When activated the Perldoc command opens a new window at the top of the screen and places the output of the perldoc command into that window. This read-only window is just a Vim window, so you can perform all of the normal commands that you can in Vim - such as searching for a word or expression, yanking examples and code snippets.","install_details":"See the README.txt file.\r\n\r\nFor fastest installation save the zip file in your personal vim directory (eg $HOME\/.vim,   or $VIM\\vimfiles\\) and unzip, it will place the 3 vim files in the correct locations. Details are in the README file. Please read it before e-mailing, but do e-mail if you have questions.","5":"See the README.txt file.\r\n\r\nFor fastest installation save the zip file in your personal vim directory (eg $HOME\/.vim,   or $VIM\\vimfiles\\) and unzip, it will place the 3 vim files in the correct locations. Details are in the README file. Please read it before e-mailing, but do e-mail if you have questions.","first_name":"Colin","6":"Colin","last_name":"Keith","7":"Keith","releases":[{"0":"209","vim_version":"6.0","1":"6.0","script_version":"1.1.1","2":"1.1.1","version_comment":"Support for su'ing to non-root user when executing the perldoc command as root. Perl below v5.6x do not support the -U flag to enable \"unsecure\" mode. See README.txt \/ vim docs for details.","3":"Support for su'ing to non-root user when executing the perldoc command as root. Perl below v5.6x do not support the -U flag to enable \"unsecure\" mode. See README.txt \/ vim docs for details.","package":"perldoc.zip","4":"perldoc.zip","src_id":"1002","5":"1002","creation_date":"1026228570","6":"1026228570"}]},"208":{"script_id":"208","0":"208","script_name":"ctx","1":"ctx","script_type":"utility","2":"utility","summary":"Describes your cursor's current scope or context when editing a C file.","3":"Describes your cursor's current scope or context when editing a C file.","description":"CTX is an attempt to help Vim users navigate in C\r\nprogram files with very large function definitions. Such\r\nfiles should generally not exist, but alas they do, and\r\nsometimes we need to make changes to them.\r\n\r\nThis script helps by opening a small window in your Vim\r\nsession and keeping up-to-date with a few lines of text\r\ndescribing your cursor's current scope or context in a C\r\nfile.\r\n\r\nhttp:\/\/www.bluweb.com\/us\/chouser\/proj\/ctx\/","4":"CTX is an attempt to help Vim users navigate in C\r\nprogram files with very large function definitions. Such\r\nfiles should generally not exist, but alas they do, and\r\nsometimes we need to make changes to them.\r\n\r\nThis script helps by opening a small window in your Vim\r\nsession and keeping up-to-date with a few lines of text\r\ndescribing your cursor's current scope or context in a C\r\nfile.\r\n\r\nhttp:\/\/www.bluweb.com\/us\/chouser\/proj\/ctx\/","install_details":"To use, source the ctx.vim file in your ~\/.vimrc.  You may also\r\nwant to reduce your updatetime to 1000 or so.","5":"To use, source the ctx.vim file in your ~\/.vimrc.  You may also\r\nwant to reduce your updatetime to 1000 or so.","first_name":"Chris","6":"Chris","last_name":"Houser","7":"Houser","releases":[{"0":"208","vim_version":"6.0","1":"6.0","script_version":"1.17","2":"1.17","version_comment":"- Added support for last switch case or label; less consistant than other structures.\r\n- Added autoupdate setting and \"\\c\" toggle key mapping\r\n- Revamped context window finding\/hiding\/auto-closing\r\n- Added support for line continuations\r\n- Properly ignore strings\r\n- Automatically skip reloads to avoid error messages\r\n","3":"- Added support for last switch case or label; less consistant than other structures.\r\n- Added autoupdate setting and \"\\c\" toggle key mapping\r\n- Revamped context window finding\/hiding\/auto-closing\r\n- Added support for line continuations\r\n- Properly ignore strings\r\n- Automatically skip reloads to avoid error messages\r\n","package":"ctx-1.17.vim","4":"ctx-1.17.vim","src_id":"933","5":"933","creation_date":"1024321494","6":"1024321494"},{"0":"208","vim_version":"6.0","1":"6.0","script_version":"1.16","2":"1.16","version_comment":"Initial upload","3":"Initial upload","package":"ctx-1.16.vim","4":"ctx-1.16.vim","src_id":"569","5":"569","creation_date":"1013159311","6":"1013159311"}]},"207":{"script_id":"207","0":"207","script_name":"MRU Menu","1":"MRU Menu","script_type":"utility","2":"utility","summary":"Plugin to manage a MRU (Most Recently Used) menu","3":"Plugin to manage a MRU (Most Recently Used) menu","description":"Description:\r\n\tThis plugin will create a MRU menu to keep track of most recently visited\r\n\tbuffers. You can customize Menu Label, menu size and whether to show\r\n\tnumbered or non-numbered menu\r\n                                                                            \r\n  Global Variables Used:\r\n  \tMRU_BUFFERS - keeps the lsit of recent buffers, usedto build the menu\r\n  \tMRU_MENUSIZE - maximum entries to keep in the list\r\n  \tMRU_HOTKEYS - whether to have a hot key of 0-9, A-Z in the menu\r\n  \tMRU_LABEL - menu name to use, default is 'M&RU'\r\n                                                                            \r\nScreen Shots: \r\n  \thttp:\/\/www.geocities.com\/rajesh_kallingal\/vim\/vimmru01.jpg \r\n  \thttp:\/\/www.geocities.com\/rajesh_kallingal\/vim\/vimmru02.jpg \r\n\r\n  \tIf the above links don't work try this http:\/\/www.geocities.com\/rajesh_kallingal\/vim\r\n     \r\nTODO:\r\n\t- handle menu size of more than 35\r\n\t- help document\r\n","4":"Description:\r\n\tThis plugin will create a MRU menu to keep track of most recently visited\r\n\tbuffers. You can customize Menu Label, menu size and whether to show\r\n\tnumbered or non-numbered menu\r\n                                                                            \r\n  Global Variables Used:\r\n  \tMRU_BUFFERS - keeps the lsit of recent buffers, usedto build the menu\r\n  \tMRU_MENUSIZE - maximum entries to keep in the list\r\n  \tMRU_HOTKEYS - whether to have a hot key of 0-9, A-Z in the menu\r\n  \tMRU_LABEL - menu name to use, default is 'M&RU'\r\n                                                                            \r\nScreen Shots: \r\n  \thttp:\/\/www.geocities.com\/rajesh_kallingal\/vim\/vimmru01.jpg \r\n  \thttp:\/\/www.geocities.com\/rajesh_kallingal\/vim\/vimmru02.jpg \r\n\r\n  \tIf the above links don't work try this http:\/\/www.geocities.com\/rajesh_kallingal\/vim\r\n     \r\nTODO:\r\n\t- handle menu size of more than 35\r\n\t- help document\r\n","install_details":"Just drop it this file in your plugin folder\/directory.\r\nMake sure you have included '!' in 'viminfo' option to save global valiables. (e.g :set viminfo += !)\r\nsee :help 'viminfo' for more info.\r\n","5":"Just drop it this file in your plugin folder\/directory.\r\nMake sure you have included '!' in 'viminfo' option to save global valiables. (e.g :set viminfo += !)\r\nsee :help 'viminfo' for more info.\r\n","first_name":"Rajesh","6":"Rajesh","last_name":"Kallingal","7":"Kallingal","releases":[{"0":"207","vim_version":"6.0","1":"6.0","script_version":"6.0.4","2":"6.0.4","version_comment":"MRU was not working while writing a new file. Added back the autocmd for BufWritePost and FileWritePost (Thanks to Edward J. Krall for reporting)","3":"MRU was not working while writing a new file. Added back the autocmd for BufWritePost and FileWritePost (Thanks to Edward J. Krall for reporting)","package":"MruMenu.vim","4":"MruMenu.vim","src_id":"2012","5":"2012","creation_date":"1053676541","6":"1053676541"},{"0":"207","vim_version":"6.0","1":"6.0","script_version":"6.0.3","2":"6.0.3","version_comment":"Speeded up the menu creation by moving the check for loaded buffers to run time rather than menu build time.\r\n\r\nHandles help files correctly, thanks to Steve Hall.","3":"Speeded up the menu creation by moving the check for loaded buffers to run time rather than menu build time.\r\n\r\nHandles help files correctly, thanks to Steve Hall.","package":"MruMenu.vim","4":"MruMenu.vim","src_id":"1989","5":"1989","creation_date":"1053006116","6":"1053006116"},{"0":"207","vim_version":"6.0","1":"6.0","script_version":"6.0.2","2":"6.0.2","version_comment":"BugFix: MRU wasn't working when vim is started by dragging a file on to the shortcut or the executable.","3":"BugFix: MRU wasn't working when vim is started by dragging a file on to the shortcut or the executable.","package":"MruMenu.vim","4":"MruMenu.vim","src_id":"570","5":"570","creation_date":"1013162453","6":"1013162453"},{"0":"207","vim_version":"6.0","1":"6.0","script_version":"6.0.1","2":"6.0.1","version_comment":"Initial upload","3":"Initial upload","package":"MruMenu.vim","4":"MruMenu.vim","src_id":"562","5":"562","creation_date":"1013001647","6":"1013001647"}]},"206":{"script_id":"206","0":"206","script_name":"LaTeX Help","1":"LaTeX Help","script_type":"utility","2":"utility","summary":"Help for LaTeX in vim.help format","3":"Help for LaTeX in vim.help format","description":"This is LaTeX Help info files `translated' as vim help file.\r\nYou can add this file to your help system and then type\r\n\r\n:help kill\r\n\r\nor\r\n\r\n:help \\kill\r\n\r\nto read something about this command.","4":"This is LaTeX Help info files `translated' as vim help file.\r\nYou can add this file to your help system and then type\r\n\r\n:help kill\r\n\r\nor\r\n\r\n:help \\kill\r\n\r\nto read something about this command.","install_details":":help add-local-help","5":":help add-local-help","first_name":"Mikolaj","6":"Mikolaj","last_name":"Machowski","7":"Machowski","releases":[{"0":"206","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"latexhelp.zip","4":"latexhelp.zip","src_id":"561","5":"561","creation_date":"1012987111","6":"1012987111"}]},"205":{"script_id":"205","0":"205","script_name":"morse.vim","1":"morse.vim","script_type":"utility","2":"utility","summary":"Script for writing morse code in vim","3":"Script for writing morse code in vim","description":"When we relax on trips in the country, we probably value script for communication in morse code (notebook and vim are necessary, of course :) What is in the vim's window, we can blink by flash-lamp :)\r\n\r\nAfter sourcing morse.vim, type <F5> to start 'morse' in normal or insert mode and type <F5> again to stop it. (This is default map, remaping this keystroke is on lines 33-34) \r\n\r\nFeature 1:\r\nIs possible switch on some 'special' characters like ,;\/?.: 'to morse'. If you want this feature, please, uncomment  line \"let g:var_morse_ext = 1\"\r\n\r\nFeature 2:\r\nMaybe is good (?) to treble spaces between words for better reading;  If you want this, please, uncomment line \"let g:var_morse_3spc = 1\"\r\n\r\nEnjoy","4":"When we relax on trips in the country, we probably value script for communication in morse code (notebook and vim are necessary, of course :) What is in the vim's window, we can blink by flash-lamp :)\r\n\r\nAfter sourcing morse.vim, type <F5> to start 'morse' in normal or insert mode and type <F5> again to stop it. (This is default map, remaping this keystroke is on lines 33-34) \r\n\r\nFeature 1:\r\nIs possible switch on some 'special' characters like ,;\/?.: 'to morse'. If you want this feature, please, uncomment  line \"let g:var_morse_ext = 1\"\r\n\r\nFeature 2:\r\nMaybe is good (?) to treble spaces between words for better reading;  If you want this, please, uncomment line \"let g:var_morse_3spc = 1\"\r\n\r\nEnjoy","install_details":"Just put this file into your $VIMRUNTIME\/plugin\/ directory, or source it directly by command \":so .\/path\/to\/file\/morse.vim\"","5":"Just put this file into your $VIMRUNTIME\/plugin\/ directory, or source it directly by command \":so .\/path\/to\/file\/morse.vim\"","first_name":"jiri","6":"jiri","last_name":"brezina","7":"brezina","releases":[{"0":"205","vim_version":"5.7","1":"5.7","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"morse.vim","4":"morse.vim","src_id":"560","5":"560","creation_date":"1012948670","6":"1012948670"}]},"204":{"script_id":"204","0":"204","script_name":"vimconfig","1":"vimconfig","script_type":"utility","2":"utility","summary":"Vim 6.3 configuration files: vimrc, ftplugins, plugins","3":"Vim 6.3 configuration files: vimrc, ftplugins, plugins","description":"Vim 6.3 configuration files.\r\n\r\nThis package include vimrc file, filetype plugins (mail, perl, TeX) and some plugins from another projects.\r\n\r\nUseful functions (e.g. for folding, autoreload of ~\/.vimrc ...)\r\n\r\nThe LATEST version of project can be downloaded from:\r\n\r\nhttp:\/\/platon.sk\/projects\/vimconfig\/\r\n\r\n\r\nYou can submit bugs, feature requests etc. at\r\nhttp:\/\/platon.sk\/projects\/vimconfig\/\r\n","4":"Vim 6.3 configuration files.\r\n\r\nThis package include vimrc file, filetype plugins (mail, perl, TeX) and some plugins from another projects.\r\n\r\nUseful functions (e.g. for folding, autoreload of ~\/.vimrc ...)\r\n\r\nThe LATEST version of project can be downloaded from:\r\n\r\nhttp:\/\/platon.sk\/projects\/vimconfig\/\r\n\r\n\r\nYou can submit bugs, feature requests etc. at\r\nhttp:\/\/platon.sk\/projects\/vimconfig\/\r\n","install_details":"SAVE this file AS vimconfig-1.10.tar.gz\r\nExtract files from an archive:\r\n\r\ntar xvzf vimconfig-1.10.tar.gz\r\n\r\nCreate symlinks:  -- simply type 'make install'\r\n\r\ncd vimconfig-1.10\r\nmake install\r\n\r\nEnjoy! :-)\r\n\r\nMakefile included - you may use it for creating your own distribution.\r\n","5":"SAVE this file AS vimconfig-1.10.tar.gz\r\nExtract files from an archive:\r\n\r\ntar xvzf vimconfig-1.10.tar.gz\r\n\r\nCreate symlinks:  -- simply type 'make install'\r\n\r\ncd vimconfig-1.10\r\nmake install\r\n\r\nEnjoy! :-)\r\n\r\nMakefile included - you may use it for creating your own distribution.\r\n","first_name":"\u013dubom\u00c3\u00adr","6":"Ľubom\u00c3\u00adr","last_name":"Host","7":"Host","releases":[{"0":"204","vim_version":"6.0","1":"6.0","script_version":"1.11","2":"1.11","version_comment":"Added support for UTF-8 diacritics input method.","3":"Added support for UTF-8 diacritics input method.","package":"vimconfig-1.11.tar.gz","4":"vimconfig-1.11.tar.gz","src_id":"4189","5":"4189","creation_date":"1114045598","6":"1114045598"},{"0":"204","vim_version":"6.0","1":"6.0","script_version":"1.10","2":"1.10","version_comment":"* New features in templating system:\r\n        - load templates from upper directory\r\n        - autogenerate Java package name\r\n* Added templates for Perl, PHP, Java, Lisp, TeX, XML, C, H, Template-Toolkit\r\n* Added filetype plugins Template-Toolkit (http:\/\/template-toolkit.org)\r\n* Added database client for ViM (beta version)\r\n* Documentation update\r\n* Diacritics input method can be changed more friendly\r\n* Added windows-1250 and \"HTML unicode\" mappings\r\n* Added autocommads for GnuPG (http:\/\/gnupg.org)\r\n","3":"* New features in templating system:\r\n        - load templates from upper directory\r\n        - autogenerate Java package name\r\n* Added templates for Perl, PHP, Java, Lisp, TeX, XML, C, H, Template-Toolkit\r\n* Added filetype plugins Template-Toolkit (http:\/\/template-toolkit.org)\r\n* Added database client for ViM (beta version)\r\n* Documentation update\r\n* Diacritics input method can be changed more friendly\r\n* Added windows-1250 and \"HTML unicode\" mappings\r\n* Added autocommads for GnuPG (http:\/\/gnupg.org)\r\n","package":"vimconfig-1.10.tar.gz","4":"vimconfig-1.10.tar.gz","src_id":"3988","5":"3988","creation_date":"1110380565","6":"1110380565"},{"0":"204","vim_version":"6.0","1":"6.0","script_version":"1.8","2":"1.8","version_comment":"Fixed many many bugs. Added many features. Added script for update Vim6.1 sources.","3":"Fixed many many bugs. Added many features. Added script for update Vim6.1 sources.","package":"vimconfig-1.8.tar.gz","4":"vimconfig-1.8.tar.gz","src_id":"1919","5":"1919","creation_date":"1050432753","6":"1050432753"},{"0":"204","vim_version":"6.0","1":"6.0","script_version":"1.7","2":"1.7","version_comment":"* Fixed some misbehaviours.\r\n* Added many files (ftplugins: html, sgml, vim; indent: php, tex; plugins: impas, increment, syntaxFolds; documentation)\r\n* Other undocumented changes :-)","3":"* Fixed some misbehaviours.\r\n* Added many files (ftplugins: html, sgml, vim; indent: php, tex; plugins: impas, increment, syntaxFolds; documentation)\r\n* Other undocumented changes :-)","package":"vimconfig-1.7.tar.gz","4":"vimconfig-1.7.tar.gz","src_id":"1092","5":"1092","creation_date":"1028827240","6":"1028827240"},{"0":"204","vim_version":"6.0","1":"6.0","script_version":"1.6","2":"1.6","version_comment":"Improvements in function LastMod() - update date\/time on line which contain g:autolastmodtext=\"^\\([ <Tab>]*Last modified: \\)\".\r\nVariable g:autolastmodtext is regular expression.\r\nAdded autocommands for *.php *.php3 files - call function AutoLastMod() when writing file.\r\n","3":"Improvements in function LastMod() - update date\/time on line which contain g:autolastmodtext=\"^\\([ <Tab>]*Last modified: \\)\".\r\nVariable g:autolastmodtext is regular expression.\r\nAdded autocommands for *.php *.php3 files - call function AutoLastMod() when writing file.\r\n","package":"vimconfig-1.6.tar.gz","4":"vimconfig-1.6.tar.gz","src_id":"634","5":"634","creation_date":"1014547717","6":"1014547717"},{"0":"204","vim_version":"6.0","1":"6.0","script_version":"1.5","2":"1.5","version_comment":"Patched little bug in Makefiil(es).","3":"Patched little bug in Makefiil(es).","package":"vimconfig-1.5.tar.gz","4":"vimconfig-1.5.tar.gz","src_id":"631","5":"631","creation_date":"1014501427","6":"1014501427"},{"0":"204","vim_version":"6.0","1":"6.0","script_version":"1.4","2":"1.4","version_comment":"Patched function SmartBS()","3":"Patched function SmartBS()","package":"vimconfig-1.4.tar.gz","4":"vimconfig-1.4.tar.gz","src_id":"608","5":"608","creation_date":"1014033458","6":"1014033458"}]},"203":{"script_id":"203","0":"203","script_name":"DSP Make","1":"DSP Make","script_type":"utility","2":"utility","summary":"Set Makeprg for MSDEV DSP","3":"Set Makeprg for MSDEV DSP","description":"This is a Vim 6 Plugin that is invoked by menu (Code.Set DSP Make) and a map  <leader>dsp, that sets makeprg to the desired msdev project.\r\n\r\nIt is useful for those using MSDEV projects and want to make from within VIM, and allows choosing a specific target from within a project.\r\n\r\nIt scans the current directory, and the directory of the current file, and presents a dialog with a choice of all the dsp projects present (assuming there is more than one) and when you choose one, displays a choice of the targets available in that DSP.\r\n'makeprg' is then modified to build that target within the desired project.\r\n\r\nNow type :make to make the project!\r\n\r\n(It does rely on &grepprg being set to a valid program -either grep or findstr work fine).\r\n","4":"This is a Vim 6 Plugin that is invoked by menu (Code.Set DSP Make) and a map  <leader>dsp, that sets makeprg to the desired msdev project.\r\n\r\nIt is useful for those using MSDEV projects and want to make from within VIM, and allows choosing a specific target from within a project.\r\n\r\nIt scans the current directory, and the directory of the current file, and presents a dialog with a choice of all the dsp projects present (assuming there is more than one) and when you choose one, displays a choice of the targets available in that DSP.\r\n'makeprg' is then modified to build that target within the desired project.\r\n\r\nNow type :make to make the project!\r\n\r\n(It does rely on &grepprg being set to a valid program -either grep or findstr work fine).\r\n","install_details":"Put into the plugin directory.","5":"Put into the plugin directory.","first_name":"Michael","6":"Michael","last_name":"Geddes","7":"Geddes","releases":[{"0":"203","vim_version":"6.0","1":"6.0","script_version":"0.5","2":"0.5","version_comment":"Go up directories to find a .dsp","3":"Go up directories to find a .dsp","package":"dspmake.vim","4":"dspmake.vim","src_id":"2695","5":"2695","creation_date":"1075401882","6":"1075401882"},{"0":"203","vim_version":"6.0","1":"6.0","script_version":"0.3","2":"0.3","version_comment":"Allow for spaces in filenames","3":"Allow for spaces in filenames","package":"dspmake.vim","4":"dspmake.vim","src_id":"717","5":"717","creation_date":"1017156506","6":"1017156506"},{"0":"203","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"dspmake.vim","4":"dspmake.vim","src_id":"555","5":"555","creation_date":"1012928081","6":"1012928081"}]},"202":{"script_id":"202","0":"202","script_name":"quickfonts.vim","1":"quickfonts.vim","script_type":"utility","2":"utility","summary":"quickly switch between a list of favorite fonts, manage list of favorite fonts","3":"quickly switch between a list of favorite fonts, manage list of favorite fonts","description":"UPDATES \r\n - allow specification of base menu in which to put quickfonts menu (e.g. 'Plugin')\r\n - bug fixes and handling of gtk2 style fonts\r\n\r\n\r\nThis plugin manages a list of favorite fonts, and allows you to swich quickly between those fonts.  This is useful if you normally like to use several fonts, for example, if your eyes get tired looking at a small font, or someone comes to look at code on your monitor, or your vision is blurry from a night of heavy drinking, you can quickly switch to a larger font, and the go back to a smaller font when the conditions allow it.\r\n\r\nAll functionality is available through an optional menu or through custom vim commands.\r\n\r\nFonts are read from a file specified with the global variable g:quickFontsFile or the default file $HOME\/.vimquickfonts if that variable doesn't eists.  At vim start up, the file is read, if it doesn't exist your list will be empty. If the 'quickFontsAutoLoad' global variable is set (i.e. in your .vimrc), the script will load the last used font upon gvim start-up. On vim quit, your list of favorites is written to the file as well as the quickfont used last.\r\n\r\nYou can switch between the fonts with the mappings Alt-< and Alt->, which I find useful because they also work in some terminal programs (rxvt\/xterm on some systems). You can change the mappings in the plugin if those don't suit you or disable them and add your own if you want (see help file).  The same functionality is available with the commands :QuickFontBigger and :QuickFontSmaller.\r\n\r\nYou can add a font to your favorites list with the command \r\n:QuickFontAdd\r\nwhich either takes no argument, in which case the value of 'guifont' will be added if available, or if an argument of '*' is given, the guifont selector is called, if you select a font from that (with no errors) that font will be added to the list.  A full font specification string can also be given as an argument. Duplicate fonts are eliminated, and new fonts are inserted sorted by pixel size in the list. UPDATE - sorting is done on font width * height rather than just width (for unix\/Xwindows).  You  can disable this with: \r\n\"let quickFontsNoXwininfo = 1\" in your vimrc.\r\n\r\nYou can remove a favorite font with the command\r\n:QuickFontDel\r\nwhich with no argument deletes the current selected font from the list, or if you give it a number, it will delete the font at that index in the list.\r\n\r\nYou can get info on your favorite font list and the currenlty selected font with the command\r\n:QuickFontInfo\r\n\r\nYou can reload your font list from your config file (abandoning any changes to the list) with the command\r\n:QuickFontReload\r\n\r\nFinally, you can always edit the config file by hand, in which case, an autocommand will re-read your changes when you write the file.\r\n\r\nCaveats: should work with non-X style fonts, except the font sorting.  There are stubs for sorting fonts for other systems - just not filled out - let me know if want to help with that.\r\n\r\n","4":"UPDATES \r\n - allow specification of base menu in which to put quickfonts menu (e.g. 'Plugin')\r\n - bug fixes and handling of gtk2 style fonts\r\n\r\n\r\nThis plugin manages a list of favorite fonts, and allows you to swich quickly between those fonts.  This is useful if you normally like to use several fonts, for example, if your eyes get tired looking at a small font, or someone comes to look at code on your monitor, or your vision is blurry from a night of heavy drinking, you can quickly switch to a larger font, and the go back to a smaller font when the conditions allow it.\r\n\r\nAll functionality is available through an optional menu or through custom vim commands.\r\n\r\nFonts are read from a file specified with the global variable g:quickFontsFile or the default file $HOME\/.vimquickfonts if that variable doesn't eists.  At vim start up, the file is read, if it doesn't exist your list will be empty. If the 'quickFontsAutoLoad' global variable is set (i.e. in your .vimrc), the script will load the last used font upon gvim start-up. On vim quit, your list of favorites is written to the file as well as the quickfont used last.\r\n\r\nYou can switch between the fonts with the mappings Alt-< and Alt->, which I find useful because they also work in some terminal programs (rxvt\/xterm on some systems). You can change the mappings in the plugin if those don't suit you or disable them and add your own if you want (see help file).  The same functionality is available with the commands :QuickFontBigger and :QuickFontSmaller.\r\n\r\nYou can add a font to your favorites list with the command \r\n:QuickFontAdd\r\nwhich either takes no argument, in which case the value of 'guifont' will be added if available, or if an argument of '*' is given, the guifont selector is called, if you select a font from that (with no errors) that font will be added to the list.  A full font specification string can also be given as an argument. Duplicate fonts are eliminated, and new fonts are inserted sorted by pixel size in the list. UPDATE - sorting is done on font width * height rather than just width (for unix\/Xwindows).  You  can disable this with: \r\n\"let quickFontsNoXwininfo = 1\" in your vimrc.\r\n\r\nYou can remove a favorite font with the command\r\n:QuickFontDel\r\nwhich with no argument deletes the current selected font from the list, or if you give it a number, it will delete the font at that index in the list.\r\n\r\nYou can get info on your favorite font list and the currenlty selected font with the command\r\n:QuickFontInfo\r\n\r\nYou can reload your font list from your config file (abandoning any changes to the list) with the command\r\n:QuickFontReload\r\n\r\nFinally, you can always edit the config file by hand, in which case, an autocommand will re-read your changes when you write the file.\r\n\r\nCaveats: should work with non-X style fonts, except the font sorting.  There are stubs for sorting fonts for other systems - just not filled out - let me know if want to help with that.\r\n\r\n","install_details":"1 - un-gzip, untar in your ~\/.vim direcory, or your vimfiles directory, or in $VIMRUNTIME\r\n2 - (optional) build local help files (:help helptags)\r\n3 - (optional) define plugin options in your vimrc - see ':help quickfonts'","5":"1 - un-gzip, untar in your ~\/.vim direcory, or your vimfiles directory, or in $VIMRUNTIME\r\n2 - (optional) build local help files (:help helptags)\r\n3 - (optional) define plugin options in your vimrc - see ':help quickfonts'","first_name":"scott","6":"scott","last_name":"urban","7":"urban","releases":[{"0":"202","vim_version":"6.0","1":"6.0","script_version":"1.29","2":"1.29","version_comment":"email updated","3":"email updated","package":"quickfonts-1.29.tar.gz","4":"quickfonts-1.29.tar.gz","src_id":"4103","5":"4103","creation_date":"1112185040","6":"1112185040"},{"0":"202","vim_version":"6.0","1":"6.0","script_version":"1.27","2":"1.27","version_comment":"fix for geometry bug when 'ignorecase' is set - thanks to Stephan  Hegel","3":"fix for geometry bug when 'ignorecase' is set - thanks to Stephan  Hegel","package":"quickfonts.tar.gz","4":"quickfonts.tar.gz","src_id":"2718","5":"2718","creation_date":"1075804902","6":"1075804902"},{"0":"202","vim_version":"6.0","1":"6.0","script_version":"1.26","2":"1.26","version_comment":"Shell and documentation fixes from Stephan Hegel","3":"Shell and documentation fixes from Stephan Hegel","package":"quickfonts.tar.gz","4":"quickfonts.tar.gz","src_id":"2711","5":"2711","creation_date":"1075714546","6":"1075714546"},{"0":"202","vim_version":"6.0","1":"6.0","script_version":"1.25","2":"1.25","version_comment":"- allow specification of base menu in which to put quickfonts menu (e.g. 'Plugin')\r\n- fix for error when menus don't exist\r\n- fix for new font style used by GTK\r\n- fix for xwinfo name error - needed redraw!\r\n- other minor fixes","3":"- allow specification of base menu in which to put quickfonts menu (e.g. 'Plugin')\r\n- fix for error when menus don't exist\r\n- fix for new font style used by GTK\r\n- fix for xwinfo name error - needed redraw!\r\n- other minor fixes","package":"quickfonts.1.25.tar.gz","4":"quickfonts.1.25.tar.gz","src_id":"2477","5":"2477","creation_date":"1068302117","6":"1068302117"},{"0":"202","vim_version":"6.0","1":"6.0","script_version":"1.21","2":"1.21","version_comment":"Menus added for most functionality - can be disabled - see help document.","3":"Menus added for most functionality - can be disabled - see help document.","package":"quickfonts-1.21.tar.gz","4":"quickfonts-1.21.tar.gz","src_id":"1671","5":"1671","creation_date":"1043493981","6":"1043493981"},{"0":"202","vim_version":"6.0","1":"6.0","script_version":"1.20","2":"1.20","version_comment":"Made start-up smoother - window no longer does a size jump when using the auto-load-last-used font feature. ","3":"Made start-up smoother - window no longer does a size jump when using the auto-load-last-used font feature. ","package":"quickfonts-1.20.tar.gz","4":"quickfonts-1.20.tar.gz","src_id":"1669","5":"1669","creation_date":"1043407029","6":"1043407029"},{"0":"202","vim_version":"6.0","1":"6.0","script_version":"1.19","2":"1.19","version_comment":"Added feature to load last font used (from quickfont list) when gvim starts up.  Added flag to disable default mapping creation.  Code clean-up, doc updates, etc.","3":"Added feature to load last font used (from quickfont list) when gvim starts up.  Added flag to disable default mapping creation.  Code clean-up, doc updates, etc.","package":"quickfonts-1.19.tar.gz","4":"quickfonts-1.19.tar.gz","src_id":"1666","5":"1666","creation_date":"1043331931","6":"1043331931"},{"0":"202","vim_version":"6.0","1":"6.0","script_version":"1.18","2":"1.18","version_comment":":QuickFontAdd funtion can now take a font name - useful for a motif version I use (no GUI font selector)","3":":QuickFontAdd funtion can now take a font name - useful for a motif version I use (no GUI font selector)","package":"quickfonts-1.18.tar.gz","4":"quickfonts-1.18.tar.gz","src_id":"892","5":"892","creation_date":"1022585125","6":"1022585125"},{"0":"202","vim_version":"6.0","1":"6.0","script_version":"1.16","2":"1.16","version_comment":"Added QuickFontSet command that allows jumping to font by index number.  Use :QuickFontInfo and :QuickFontSet x in succession.","3":"Added QuickFontSet command that allows jumping to font by index number.  Use :QuickFontInfo and :QuickFontSet x in succession.","package":"quickfont-1.16.tar.gz","4":"quickfont-1.16.tar.gz","src_id":"798","5":"798","creation_date":"1019218326","6":"1019218326"},{"0":"202","vim_version":"6.0","1":"6.0","script_version":"1.14","2":"1.14","version_comment":"Added documentation (run :helptags ~\/.vim\/doc); Fixed numeric sorting bug; Default config file for Windows changed to $HOME\/_vimquickfonts; Fall through when xwininfo fails.","3":"Added documentation (run :helptags ~\/.vim\/doc); Fixed numeric sorting bug; Default config file for Windows changed to $HOME\/_vimquickfonts; Fall through when xwininfo fails.","package":"quickfonts.tar.gz","4":"quickfonts.tar.gz","src_id":"566","5":"566","creation_date":"1013103975","6":"1013103975"},{"0":"202","vim_version":"6.0","1":"6.0","script_version":"1.13","2":"1.13","version_comment":"Fonts can be sorted on area (char width * height) instead of just on width - this gives a bit smoother transition as you go bigger and smaller. Uses xwininfo to do this (X systems only) - you can turn it off by letting the var quickFontsNoXwininfo in your vimrc.\r\nFont sorting separated into different gui systems - only X is implemented now - if you want to help with windows or others, let me know.\r\nQuickFontReload command added - re-reads your font list file - effectively abandoning changes.\r\nEscaping of spaces in font names.\r\nGeneral improvements","3":"Fonts can be sorted on area (char width * height) instead of just on width - this gives a bit smoother transition as you go bigger and smaller. Uses xwininfo to do this (X systems only) - you can turn it off by letting the var quickFontsNoXwininfo in your vimrc.\r\nFont sorting separated into different gui systems - only X is implemented now - if you want to help with windows or others, let me know.\r\nQuickFontReload command added - re-reads your font list file - effectively abandoning changes.\r\nEscaping of spaces in font names.\r\nGeneral improvements","package":"quickfonts.vim","4":"quickfonts.vim","src_id":"564","5":"564","creation_date":"1013098043","6":"1013098043"},{"0":"202","vim_version":"6.0","1":"6.0","script_version":"1.6","2":"1.6","version_comment":"Initial upload","3":"Initial upload","package":"quickfonts.vim","4":"quickfonts.vim","src_id":"544","5":"544","creation_date":"1012828403","6":"1012828403"}]},"201":{"script_id":"201","0":"201","script_name":"bcbuf.vim","1":"bcbuf.vim","script_type":"utility","2":"utility","summary":"Broadcast commands for buffers","3":"Broadcast commands for buffers","description":"This scripts allows to use \/ share buffers over multiple, clientserver-enabled vims.\r\nEspecially, the :BCbuffer command allows to \"steal\" a buffer which is opened in another vim.\r\n\r\nThe file bcbuf.vim provides further documentation.\r\n ","4":"This scripts allows to use \/ share buffers over multiple, clientserver-enabled vims.\r\nEspecially, the :BCbuffer command allows to \"steal\" a buffer which is opened in another vim.\r\n\r\nThe file bcbuf.vim provides further documentation.\r\n ","install_details":"Drop this script in ~\/.vim\/plugin\/","5":"Drop this script in ~\/.vim\/plugin\/","first_name":"Mark A.","6":"Mark A.","last_name":"Hillebrand","7":"Hillebrand","releases":[{"0":"201","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"bcbuf-0.1.vim","4":"bcbuf-0.1.vim","src_id":"541","5":"541","creation_date":"1012819547","6":"1012819547"}]},"200":{"script_id":"200","0":"200","script_name":"ComplMenu.vim","1":"ComplMenu.vim","script_type":"utility","2":"utility","summary":"A completion menu (shows all possibilities as you type)","3":"A completion menu (shows all possibilities as you type)","description":"Features:\r\nobsolate. Just use vim7 instead","4":"Features:\r\nobsolate. Just use vim7 instead","install_details":"","5":"","first_name":"Gergely","6":"Gergely","last_name":"Kontra","7":"Kontra","releases":[{"0":"200","vim_version":"6.0","1":"6.0","script_version":"0.01","2":"0.01","version_comment":"Initial upload","3":"Initial upload","package":"ComplMenu.vim","4":"ComplMenu.vim","src_id":"535","5":"535","creation_date":"1012805006","6":"1012805006"}]},"199":{"script_id":"199","0":"199","script_name":"charset.vim","1":"charset.vim","script_type":"utility","2":"utility","summary":"Read file in proper encoding (xml, html...)","3":"Read file in proper encoding (xml, html...)","description":"Some types of documents have their encoding written in them. This plugin makes this information accessible to vim and ensures that they are read in proper encoding.\r\n\r\nAlso can be used for plain files in modeline-like way.\r\n\r\nCurrently, xml and html files are recognized and the last line of .txt files is checked to find out encoding.","4":"Some types of documents have their encoding written in them. This plugin makes this information accessible to vim and ensures that they are read in proper encoding.\r\n\r\nAlso can be used for plain files in modeline-like way.\r\n\r\nCurrently, xml and html files are recognized and the last line of .txt files is checked to find out encoding.","install_details":"Unpack in .vim directory. Contains the plugin itself and documentation.","5":"Unpack in .vim directory. Contains the plugin itself and documentation.","first_name":"Tomas","6":"Tomas","last_name":"Zellerin","7":"Zellerin","releases":[{"0":"199","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"charset.tar.gz","4":"charset.tar.gz","src_id":"532","5":"532","creation_date":"1012792009","6":"1012792009"}]},"198":{"script_id":"198","0":"198","script_name":"template file loader","1":"template file loader","script_type":"utility","2":"utility","summary":"Loads a template file and does customizable processing when editing a new file.","3":"Loads a template file and does customizable processing when editing a new file.","description":"This plugin is for loading template files when editing new files.  A template file will be loaded if found, keywords in that template are expanded, and\/or a customized function for that type of files is called.\r\n\r\nFor all new files, the script checks to see if you have a skeleton (template) file for the extension of that file.  For example, \":new temp.c\"  would check for the existence of \"skel.c\".  Files without extensions are handled also - if you did \":new makefile\", the script checks for the existence of \"skel.noext.makefile\".\r\n\r\nskel.* files are looked for in a directory specified with the environment variable $VIMTEMPLATE or in your ~\/.vim directory if that env var doesn't exist.  This allows you to use mutliple sets of template files - some for work files and some for personal files, for example.\r\n\r\nThis plugin is meant to be customized - add your own keywords for expansion or your own file specific template functions (example provided in script).\r\n\r\nThe script includes many example skel.* files - some are links to others.\r\n\r\n\r\n","4":"This plugin is for loading template files when editing new files.  A template file will be loaded if found, keywords in that template are expanded, and\/or a customized function for that type of files is called.\r\n\r\nFor all new files, the script checks to see if you have a skeleton (template) file for the extension of that file.  For example, \":new temp.c\"  would check for the existence of \"skel.c\".  Files without extensions are handled also - if you did \":new makefile\", the script checks for the existence of \"skel.noext.makefile\".\r\n\r\nskel.* files are looked for in a directory specified with the environment variable $VIMTEMPLATE or in your ~\/.vim directory if that env var doesn't exist.  This allows you to use mutliple sets of template files - some for work files and some for personal files, for example.\r\n\r\nThis plugin is meant to be customized - add your own keywords for expansion or your own file specific template functions (example provided in script).\r\n\r\nThe script includes many example skel.* files - some are links to others.\r\n\r\n\r\n","install_details":"1 - Un-gzip\r\n2 - Un-tar in $HOME\/.vim or equivalent.\r\n3 - Plugins must be turned on.\r\n4 - Customize as you see fit","5":"1 - Un-gzip\r\n2 - Un-tar in $HOME\/.vim or equivalent.\r\n3 - Plugins must be turned on.\r\n4 - Customize as you see fit","first_name":"scott","6":"scott","last_name":"urban","7":"urban","releases":[{"0":"198","vim_version":"6.0","1":"6.0","script_version":"1.5","2":"1.5","version_comment":"Patched little bug in Makefile.","3":"Patched little bug in Makefile.","package":"templatefile-1.5.tar.gz","4":"templatefile-1.5.tar.gz","src_id":"632","5":"632","creation_date":"1014501728","6":"1014501728"},{"0":"198","vim_version":"6.0","1":"6.0","script_version":"1.2","2":"1.2","version_comment":"Completely rewrited. I include this plugin to my vimconfig project:\nhttp:\/\/vim.sourceforge.net\/scripts\/script.php?script_id=204","3":"Completely rewrited. I include this plugin to my vimconfig project:\nhttp:\/\/vim.sourceforge.net\/scripts\/script.php?script_id=204","package":"template.gz","4":"template.gz","src_id":"558","5":"558","creation_date":"1012935740","6":"1012935740"},{"0":"198","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"templatefile.tar.gz","4":"templatefile.tar.gz","src_id":"530","5":"530","creation_date":"1012644332","6":"1012644332"}]},"197":{"script_id":"197","0":"197","script_name":"genutils","1":"genutils","script_type":"utility","2":"utility","summary":"General utility functions","3":"General utility functions","description":"The new version requires Vim 7.0 and it employs the new autoload mechanism. If you have plugins that use both the new version and previous non-autoloaded version, then see the installation instructions for both to coexist.\r\n\r\nThis script provides functions that are mostly useful to script developers, but some of the functions can be easily converted to good utilities.\r\n\r\nSee script header for documented public functions with help and usage information along with the function prototypes.\r\n\r\nThis script provides many useful utility functions for buffers, windows and other misc things. I needed a place to share all the misc. utility functions so I renamed bufNwinUtils.vim and started adding these additional functions. I intend to create\/collect many more useful functions and add to this script.\r\n\r\n- Read the \"Documentation With Function Prototypes\" section below.\r\n- Misc. window\/buffer related functions, genutils#NumberOfWindows(),\r\n  genutils#FindBufferForName(), genutils#MoveCursorToWindow(),\r\n  genutils#MoveCurLineToWinLine(), genutils#SetupScratchBuffer(),\r\n  genutils#MapAppendCascaded()\r\n- Save\/Restore all the window height\/width settings to be restored later.\r\n- Save\/Restore position in the buffer to be restored later. Works like the\r\n  built-in marks feature, but has more to it.\r\n- genutils#AddNotifyWindowClose() to get notifications *after* a window\r\n  with the specified buffer has been closed or the buffer is unloaded. The\r\n  built-in autocommands can only notify you *before* the window is closed.\r\n  You can use this with the Save\/Restore window settings feature to\r\n  restore the dimensions of existing windows, after your window is closed\r\n  (just like how Vim does while closing help windows). See selectbuf.vim\r\n  or perforce.vim for examples.\r\n  There is also a test function called RunNotifyWindowCloseTest() that\r\n  demos the usage (you need to uncomment RunNotifyWindowCloseTest and\r\n  NotifyWindowCloseF functions).\r\n- genutils#ShowLinesWithSyntax() function to echo lines with syntax coloring.\r\n- genutils#ShiftWordInSpace(), genutils#CenterWordInSpace() and\r\n  genutils#AlignWordWithWordInPreviousLine() utility functions to move\r\n  words in the space without changing the width of the field. A\r\n  genutils#GetSpacer() function to return a spacer of specified width.\r\n- Binary search function genutils#BinSearchList() for sorted lists, to\r\n  find the index after which a given item can be inserted to keep the list\r\n  in sorted order. You can also use these functions to just search for\r\n  boundaries.\r\n  There are also a couple of functions genutils#BinSearchForInsert() and\r\n  genutils#BinSearchForInsert2() to find the location for a newline to be\r\n  inserted in an already sorted buffer or arbitrary data.\r\n  There are also a few comparison functions that can be used with sort() or\r\n  the above functions.\r\n- ExecMap function has now been separated as a plugin called execmap.vim.\r\n- New genutils#CommonPath() function to extract the common part of two\r\n  paths, and genutils#RelPathFromFile() and genutils#RelPathFromDir() to\r\n  find relative paths (useful HTML href's). A side effect is the\r\n  genutils#CommonString() function to find the common string of two\r\n  strings.\r\n- genutils#UnEscape() and genutils#DeEscape() functions to reverse and\r\n  genutils#Escape() to compliment what built-in escape() does. There is\r\n  also an genutils#EscapeCommand() function to escape external command\r\n  strings.\r\n- Utility functions genutils#CurLineHasSign() and genutils#ClearAllSigns()\r\n  to fill in the gaps left by Vim.\r\n- genutils#GetVimCmdOutput() function to capture the output of Vim built-in\r\n  commands, in a safe manner.\r\n- genutils#OptClearBuffer() function to clear the contents and undo\r\n  history of the current buffer in an optimal manner. Ideal to be used\r\n  when plugins need to refresh their windows and don't care about\r\n  preserving the current contents (which is the most usual case).\r\n- genutils#GetPreviewWinnr() function.\r\n- Functions to have persistent data, genutils#PutPersistentVar() and\r\n  genutils#GetPersistentVar(). You don't need to worry about saving in\r\n  files and reading them back. To disable, set g:genutilsNoPersist in your\r\n  vimrc.\r\n- A function to emulate the default Vim behavior for |timestamp| changes.\r\n  It also provides hooks to get call backs before and after handling the\r\n  default FileChangedShell autocommand (effectively splitting it into a\r\n  Pre and a Post event). Suggested usage is to use\r\n  genutils#AddToFCShellPre() and either install a default event handling\r\n  mechanism for all files by calling genutils#DefFCShellInstall() or\r\n  create your own autocommand on a matching pattern to call\r\n  genutils#DefFileChangedShell() function. Most useful for the source\r\n  control plugins to conditionally reload a file, while being able to\r\n  default to the Vim's standard behavior of asking the user. See\r\n  perforce.vim for usage examples.\r\n- Utility function genutils#ExtractFuncListing() that is useful to to\r\n  create snippets (see breakpts.vim, ntservices.vim and ntprocesses.vim\r\n  for interesting ideas on how to use this function).\r\n                                                                                   \r\nFunction Prototypes:\r\n    The types in prototypes of the functions mimic Java.\r\n    This is just a full list for a quick reference, see\r\n      \"Documentation With Function Prototypes\" for more information on the\r\n      functions.\r\n                                                                                   \r\nvoid    genutils#DebugShowArgs(...)\r\nString  genutils#ExtractFuncListing(String funcName, String hLines, String tLines)\r\nint     genutils#NumberOfWindows()\r\nint     genutils#FindBufferForName(String fileName)\r\nString  genutils#GetBufNameForAu(String bufName)\r\nvoid    genutils#MoveCursorToWindow(int winno)\r\nvoid    genutils#MoveCurLineToWinLine(int winLine)\r\nvoid    genutils#CloseWindow(int winnr, boolean force)\r\nvoid    genutils#MarkActiveWindow()\r\nvoid    genutils#RestoreActiveWindow()\r\nvoid    genutils#IsOnlyVerticalWindow()\r\nvoid    genutils#IsOnlyHorizontalWindow()\r\nint     genutils#GetNextWinnrInStack(char dir)\r\nint     genutils#GetLastWinnrInStack(char dir)\r\nvoid    genutils#MoveCursorToNextInWinStack(char dir)\r\nvoid    genutils#MoveCursorToLastInWinStack(char dir)\r\nvoid    genutils#OpenWinNoEa(String openWinCmd)\r\nvoid    genutils#CloseWinNoEa(int winnr, boolean force)\r\nvoid    genutils#SetupScratchBuffer()\r\nvoid    genutils#CleanDiffOptions()\r\nboolean genutils#ArrayVarExists(String varName, int index)\r\nvoid    genutils#MapAppendCascaded(String lhs, String rhs, String mapMode)\r\nvoid    genutils#SaveWindowSettings()\r\nvoid    genutils#RestoreWindowSettings()\r\nvoid    genutils#ResetWindowSettings()\r\nvoid    genutils#SaveWindowSettings2(String id, boolean overwrite)\r\nvoid    genutils#RestoreWindowSettings2(String id)\r\nvoid    genutils#ResetWindowSettings2(String id)\r\nvoid    genutils#SaveVisualSelection(String id)\r\nvoid    genutils#RestoreVisualSelection(String id)\r\nvoid    genutils#SaveSoftPosition(String id)\r\nvoid    genutils#RestoreSoftPosition(String id)\r\nvoid    genutils#ResetSoftPosition(String id)\r\nvoid    genutils#SaveHardPosition(String id)\r\nvoid    genutils#RestoreHardPosition(String id)\r\nvoid    genutils#ResetHardPosition(String id)\r\nint     genutils#GetLinePosition(String id)\r\nint     genutils#GetColPosition(String id)\r\nboolean genutils#IsPositionSet(String id)\r\nString  genutils#CleanupFileName(String fileName)\r\nString  genutils#CleanupFileName2(String fileName, String win32ProtectedChars)\r\nboolean genutils#OnMS()\r\nboolean genutils#PathIsAbsolute(String path)\r\nboolean genutils#PathIsFileNameOnly(String path)\r\nvoid    genutils#AddNotifyWindowClose(String windowTitle, String functionName)\r\nvoid    genutils#RemoveNotifyWindowClose(String windowTitle)\r\nvoid    genutils#CheckWindowClose()\r\nvoid    genutils#ShowLinesWithSyntax() range\r\nvoid    genutils#ShiftWordInSpace(int direction)\r\nvoid    genutils#CenterWordInSpace()\r\nint     genutils#BinSearchList(List list, int start, int end, Object item,\r\n                           [Funcref|String] cmp, int direction)\r\nint     genutils#BinSearchForInsert(int start, int end, String line,\r\n                           String cmp, int direction)\r\nint     genutils#BinSearchForInsert2(int start, int end, line, String cmp,\r\n                            int direction, String accessor, String context)\r\nString  genutils#CommonPath(String path1, String path2)\r\nString  genutils#CommonString(String str1, String str2)\r\nString  genutils#RelPathFromFile(String srcFile, String tgtFile)\r\nString  genutils#RelPathFromDir(String srcDir, String tgtFile)\r\nString  genutils#Roman2Decimal(String str)\r\nString  genutils#Escape(String str, String chars)\r\nString  genutils#UnEscape(String str, String chars)\r\nString  genutils#DeEscape(String str)\r\nString  genutils#CrUnProtectedCharsPattern(String chars)\r\nString  genutils#EscapeCommand(String cmd, List\/String args, List\/String pipe)\r\nint     genutils#GetShellEnvType()\r\nString  genutils#ExpandStr(String str)\r\nString  genutils#QuoteStr(String str)\r\nboolean genutils#CurLineHasSign()\r\nvoid    genutils#ClearAllSigns()\r\nString  genutils#UserFileComplete(String ArgLead, String CmdLine,\r\n               String CursorPos, String smartSlash, String searchPath)\r\nString  genutils#UserFileComplete2(String ArgLead, String CmdLine,\r\n               String CursorPos, [Map params])\r\nString  genutils#UserDirComplete2(String ArgLead, String CmdLine,\r\n               String CursorPos, [Map params])\r\nString  genutils#UserFileExpand(String fileArgs)\r\nString  genutils#GetVimCmdOutput(String cmd)\r\nvoid    genutils#OptClearBuffer()\r\nint     genutils#GetPreviewWinnr()\r\nvoid    genutils#PutPersistentVar(String pluginName, String persistentVar,\r\n               String value)\r\nvoid    genutils#GetPersistentVar(String pluginName, String persistentVar,\r\n               String default)\r\nvoid    genutils#AddToFCShellPre(String funcName)\r\nvoid    genutils#RemoveFromFCShellPre(String funcName)\r\nvoid    genutils#DefFCShellInstall()\r\nvoid    genutils#DefFCShellUninstall()\r\nboolean genutils#DefFileChangedShell()\r\nvoid    genutils#SilentSubstitute(String pat, String cmd)\r\nvoid    genutils#SilentDelete(String pat)\r\nvoid    genutils#SilentDelete(String range, String pat)\r\nString  genutils#GetSpacer(int width)\r\nString  genutils#PromptForElement(List array,\r\n    \t   [String defaultValue | int defaultIndex], String msg,\r\n    \t   String skip, boolean useDialog, int nCols)\r\nint     genutils#GetSelectedIndex()\r\n\r\nDeprecations:\r\n  - UserFileComplete() is now deprecated, use UserFileComplete2().\r\n  - CleanDiffOptions() is deprecated as Vim now has the :diffoff command.\r\n  - MakeArgumentString, MakeArgumentList and CreateArgString are deprecated.\r\n    Vim7 now includes call() function to receive and pass argument lists\r\n    around.\r\n  - The g:makeArgumentString and g:makeArgumentList are obsolete and are\r\n    deprecated, please use MakeArgumentString() and MakeArgumentList()\r\n    instead.\r\n  - FindWindowForBuffer() function is now deprecated, as the corresponding\r\n    Vim bugs are fixed. Use the below expr instead:\r\n      bufwinnr(genutils#FindBufferForName(fileName))\r\n  - QSort(), QSort2(), BinInsertSort() and BinInsertSort2() functions are\r\n    now deprecated in favor of sort() function.\r\n\r\n\r\n\r\n\r\nSearch_key_words: genutils variable arguments window buffer windows buffers preview save restore cursor position notify close echo syntax shift sort library typing error errors scriptid clean reset diff eatchar align word words space file filename binary search multvals Hari Krishna Dara","4":"The new version requires Vim 7.0 and it employs the new autoload mechanism. If you have plugins that use both the new version and previous non-autoloaded version, then see the installation instructions for both to coexist.\r\n\r\nThis script provides functions that are mostly useful to script developers, but some of the functions can be easily converted to good utilities.\r\n\r\nSee script header for documented public functions with help and usage information along with the function prototypes.\r\n\r\nThis script provides many useful utility functions for buffers, windows and other misc things. I needed a place to share all the misc. utility functions so I renamed bufNwinUtils.vim and started adding these additional functions. I intend to create\/collect many more useful functions and add to this script.\r\n\r\n- Read the \"Documentation With Function Prototypes\" section below.\r\n- Misc. window\/buffer related functions, genutils#NumberOfWindows(),\r\n  genutils#FindBufferForName(), genutils#MoveCursorToWindow(),\r\n  genutils#MoveCurLineToWinLine(), genutils#SetupScratchBuffer(),\r\n  genutils#MapAppendCascaded()\r\n- Save\/Restore all the window height\/width settings to be restored later.\r\n- Save\/Restore position in the buffer to be restored later. Works like the\r\n  built-in marks feature, but has more to it.\r\n- genutils#AddNotifyWindowClose() to get notifications *after* a window\r\n  with the specified buffer has been closed or the buffer is unloaded. The\r\n  built-in autocommands can only notify you *before* the window is closed.\r\n  You can use this with the Save\/Restore window settings feature to\r\n  restore the dimensions of existing windows, after your window is closed\r\n  (just like how Vim does while closing help windows). See selectbuf.vim\r\n  or perforce.vim for examples.\r\n  There is also a test function called RunNotifyWindowCloseTest() that\r\n  demos the usage (you need to uncomment RunNotifyWindowCloseTest and\r\n  NotifyWindowCloseF functions).\r\n- genutils#ShowLinesWithSyntax() function to echo lines with syntax coloring.\r\n- genutils#ShiftWordInSpace(), genutils#CenterWordInSpace() and\r\n  genutils#AlignWordWithWordInPreviousLine() utility functions to move\r\n  words in the space without changing the width of the field. A\r\n  genutils#GetSpacer() function to return a spacer of specified width.\r\n- Binary search function genutils#BinSearchList() for sorted lists, to\r\n  find the index after which a given item can be inserted to keep the list\r\n  in sorted order. You can also use these functions to just search for\r\n  boundaries.\r\n  There are also a couple of functions genutils#BinSearchForInsert() and\r\n  genutils#BinSearchForInsert2() to find the location for a newline to be\r\n  inserted in an already sorted buffer or arbitrary data.\r\n  There are also a few comparison functions that can be used with sort() or\r\n  the above functions.\r\n- ExecMap function has now been separated as a plugin called execmap.vim.\r\n- New genutils#CommonPath() function to extract the common part of two\r\n  paths, and genutils#RelPathFromFile() and genutils#RelPathFromDir() to\r\n  find relative paths (useful HTML href's). A side effect is the\r\n  genutils#CommonString() function to find the common string of two\r\n  strings.\r\n- genutils#UnEscape() and genutils#DeEscape() functions to reverse and\r\n  genutils#Escape() to compliment what built-in escape() does. There is\r\n  also an genutils#EscapeCommand() function to escape external command\r\n  strings.\r\n- Utility functions genutils#CurLineHasSign() and genutils#ClearAllSigns()\r\n  to fill in the gaps left by Vim.\r\n- genutils#GetVimCmdOutput() function to capture the output of Vim built-in\r\n  commands, in a safe manner.\r\n- genutils#OptClearBuffer() function to clear the contents and undo\r\n  history of the current buffer in an optimal manner. Ideal to be used\r\n  when plugins need to refresh their windows and don't care about\r\n  preserving the current contents (which is the most usual case).\r\n- genutils#GetPreviewWinnr() function.\r\n- Functions to have persistent data, genutils#PutPersistentVar() and\r\n  genutils#GetPersistentVar(). You don't need to worry about saving in\r\n  files and reading them back. To disable, set g:genutilsNoPersist in your\r\n  vimrc.\r\n- A function to emulate the default Vim behavior for |timestamp| changes.\r\n  It also provides hooks to get call backs before and after handling the\r\n  default FileChangedShell autocommand (effectively splitting it into a\r\n  Pre and a Post event). Suggested usage is to use\r\n  genutils#AddToFCShellPre() and either install a default event handling\r\n  mechanism for all files by calling genutils#DefFCShellInstall() or\r\n  create your own autocommand on a matching pattern to call\r\n  genutils#DefFileChangedShell() function. Most useful for the source\r\n  control plugins to conditionally reload a file, while being able to\r\n  default to the Vim's standard behavior of asking the user. See\r\n  perforce.vim for usage examples.\r\n- Utility function genutils#ExtractFuncListing() that is useful to to\r\n  create snippets (see breakpts.vim, ntservices.vim and ntprocesses.vim\r\n  for interesting ideas on how to use this function).\r\n                                                                                   \r\nFunction Prototypes:\r\n    The types in prototypes of the functions mimic Java.\r\n    This is just a full list for a quick reference, see\r\n      \"Documentation With Function Prototypes\" for more information on the\r\n      functions.\r\n                                                                                   \r\nvoid    genutils#DebugShowArgs(...)\r\nString  genutils#ExtractFuncListing(String funcName, String hLines, String tLines)\r\nint     genutils#NumberOfWindows()\r\nint     genutils#FindBufferForName(String fileName)\r\nString  genutils#GetBufNameForAu(String bufName)\r\nvoid    genutils#MoveCursorToWindow(int winno)\r\nvoid    genutils#MoveCurLineToWinLine(int winLine)\r\nvoid    genutils#CloseWindow(int winnr, boolean force)\r\nvoid    genutils#MarkActiveWindow()\r\nvoid    genutils#RestoreActiveWindow()\r\nvoid    genutils#IsOnlyVerticalWindow()\r\nvoid    genutils#IsOnlyHorizontalWindow()\r\nint     genutils#GetNextWinnrInStack(char dir)\r\nint     genutils#GetLastWinnrInStack(char dir)\r\nvoid    genutils#MoveCursorToNextInWinStack(char dir)\r\nvoid    genutils#MoveCursorToLastInWinStack(char dir)\r\nvoid    genutils#OpenWinNoEa(String openWinCmd)\r\nvoid    genutils#CloseWinNoEa(int winnr, boolean force)\r\nvoid    genutils#SetupScratchBuffer()\r\nvoid    genutils#CleanDiffOptions()\r\nboolean genutils#ArrayVarExists(String varName, int index)\r\nvoid    genutils#MapAppendCascaded(String lhs, String rhs, String mapMode)\r\nvoid    genutils#SaveWindowSettings()\r\nvoid    genutils#RestoreWindowSettings()\r\nvoid    genutils#ResetWindowSettings()\r\nvoid    genutils#SaveWindowSettings2(String id, boolean overwrite)\r\nvoid    genutils#RestoreWindowSettings2(String id)\r\nvoid    genutils#ResetWindowSettings2(String id)\r\nvoid    genutils#SaveVisualSelection(String id)\r\nvoid    genutils#RestoreVisualSelection(String id)\r\nvoid    genutils#SaveSoftPosition(String id)\r\nvoid    genutils#RestoreSoftPosition(String id)\r\nvoid    genutils#ResetSoftPosition(String id)\r\nvoid    genutils#SaveHardPosition(String id)\r\nvoid    genutils#RestoreHardPosition(String id)\r\nvoid    genutils#ResetHardPosition(String id)\r\nint     genutils#GetLinePosition(String id)\r\nint     genutils#GetColPosition(String id)\r\nboolean genutils#IsPositionSet(String id)\r\nString  genutils#CleanupFileName(String fileName)\r\nString  genutils#CleanupFileName2(String fileName, String win32ProtectedChars)\r\nboolean genutils#OnMS()\r\nboolean genutils#PathIsAbsolute(String path)\r\nboolean genutils#PathIsFileNameOnly(String path)\r\nvoid    genutils#AddNotifyWindowClose(String windowTitle, String functionName)\r\nvoid    genutils#RemoveNotifyWindowClose(String windowTitle)\r\nvoid    genutils#CheckWindowClose()\r\nvoid    genutils#ShowLinesWithSyntax() range\r\nvoid    genutils#ShiftWordInSpace(int direction)\r\nvoid    genutils#CenterWordInSpace()\r\nint     genutils#BinSearchList(List list, int start, int end, Object item,\r\n                           [Funcref|String] cmp, int direction)\r\nint     genutils#BinSearchForInsert(int start, int end, String line,\r\n                           String cmp, int direction)\r\nint     genutils#BinSearchForInsert2(int start, int end, line, String cmp,\r\n                            int direction, String accessor, String context)\r\nString  genutils#CommonPath(String path1, String path2)\r\nString  genutils#CommonString(String str1, String str2)\r\nString  genutils#RelPathFromFile(String srcFile, String tgtFile)\r\nString  genutils#RelPathFromDir(String srcDir, String tgtFile)\r\nString  genutils#Roman2Decimal(String str)\r\nString  genutils#Escape(String str, String chars)\r\nString  genutils#UnEscape(String str, String chars)\r\nString  genutils#DeEscape(String str)\r\nString  genutils#CrUnProtectedCharsPattern(String chars)\r\nString  genutils#EscapeCommand(String cmd, List\/String args, List\/String pipe)\r\nint     genutils#GetShellEnvType()\r\nString  genutils#ExpandStr(String str)\r\nString  genutils#QuoteStr(String str)\r\nboolean genutils#CurLineHasSign()\r\nvoid    genutils#ClearAllSigns()\r\nString  genutils#UserFileComplete(String ArgLead, String CmdLine,\r\n               String CursorPos, String smartSlash, String searchPath)\r\nString  genutils#UserFileComplete2(String ArgLead, String CmdLine,\r\n               String CursorPos, [Map params])\r\nString  genutils#UserDirComplete2(String ArgLead, String CmdLine,\r\n               String CursorPos, [Map params])\r\nString  genutils#UserFileExpand(String fileArgs)\r\nString  genutils#GetVimCmdOutput(String cmd)\r\nvoid    genutils#OptClearBuffer()\r\nint     genutils#GetPreviewWinnr()\r\nvoid    genutils#PutPersistentVar(String pluginName, String persistentVar,\r\n               String value)\r\nvoid    genutils#GetPersistentVar(String pluginName, String persistentVar,\r\n               String default)\r\nvoid    genutils#AddToFCShellPre(String funcName)\r\nvoid    genutils#RemoveFromFCShellPre(String funcName)\r\nvoid    genutils#DefFCShellInstall()\r\nvoid    genutils#DefFCShellUninstall()\r\nboolean genutils#DefFileChangedShell()\r\nvoid    genutils#SilentSubstitute(String pat, String cmd)\r\nvoid    genutils#SilentDelete(String pat)\r\nvoid    genutils#SilentDelete(String range, String pat)\r\nString  genutils#GetSpacer(int width)\r\nString  genutils#PromptForElement(List array,\r\n    \t   [String defaultValue | int defaultIndex], String msg,\r\n    \t   String skip, boolean useDialog, int nCols)\r\nint     genutils#GetSelectedIndex()\r\n\r\nDeprecations:\r\n  - UserFileComplete() is now deprecated, use UserFileComplete2().\r\n  - CleanDiffOptions() is deprecated as Vim now has the :diffoff command.\r\n  - MakeArgumentString, MakeArgumentList and CreateArgString are deprecated.\r\n    Vim7 now includes call() function to receive and pass argument lists\r\n    around.\r\n  - The g:makeArgumentString and g:makeArgumentList are obsolete and are\r\n    deprecated, please use MakeArgumentString() and MakeArgumentList()\r\n    instead.\r\n  - FindWindowForBuffer() function is now deprecated, as the corresponding\r\n    Vim bugs are fixed. Use the below expr instead:\r\n      bufwinnr(genutils#FindBufferForName(fileName))\r\n  - QSort(), QSort2(), BinInsertSort() and BinInsertSort2() functions are\r\n    now deprecated in favor of sort() function.\r\n\r\n\r\n\r\n\r\nSearch_key_words: genutils variable arguments window buffer windows buffers preview save restore cursor position notify close echo syntax shift sort library typing error errors scriptid clean reset diff eatchar align word words space file filename binary search multvals Hari Krishna Dara","install_details":"Expand in your runtime (vimfiles\/.vim directory).\r\n\r\nPlace the following in your vimrc if you find them useful:\r\n\r\n- Add the following commands to create simple sort commands.\r\n    command! -nargs=0 -range=% SortByLength <line1>,<line2>call QSort(\r\n        \\ 'CmpByLineLengthNname', 1)\r\n    command! -nargs=0 -range=% RSortByLength <line1>,<line2>call QSort(\r\n        \\ 'CmpByLineLengthNname', -1)\r\n    command! -nargs=0 -range=% SortJavaImports <line1>,<line2>call QSort(\r\n        \\ 'CmpJavaImports', 1)\r\n                                                                           \r\n- You might like the following mappings to adjust spacing:\r\n    nnoremap <silent> <C-Space> :call ShiftWordInSpace(1)<CR>\r\n    nnoremap <silent> <C-BS> :call ShiftWordInSpace(-1)<CR>\r\n    nnoremap <silent> \\cw :call CenterWordInSpace()<CR>\r\n    nnoremap <silent> \\va :call AlignWordWithWordInPreviousLine()<CR>\r\n                                                                           \r\n- The :find command is very useful to search for a file in path, but it\r\n  doesn't support file completion. Add the following command in your vimrc\r\n  to add this functionality:\r\n      command! -nargs=1 -bang -complete=customlist,genutils#UserFileComplete2\r\n            \\ FindInPath :find<bang> <args>\r\n                                                                           \r\n- If you are running commands that generate multiple pages of output, you\r\n  might find it useful to redirect the output to a new buffer. Put the\r\n  following command in your vimrc:\r\n    command! -nargs=* -complete=command Redir\r\n          \\ :new | put! =GetVimCmdOutput('<args>') | setl bufhidden=wipe |\r\n          \\ setl nomodified\r\n\r\n\r\nFor version prior to 2.0:\r\nDrop it in the plugin directory or source it from vimrc.\r\nAlso install multvals.vim: vimscript #171\r\n\r\nSpecial instructions for the coexistence of autoload (version since 2.0) and non-autoload (prior to 2.0) versions of genutils:\r\n- Install the latest version of genutils first. Overwriting all existing\r\n  files.\r\n- Open the plugin\/genutils.vim file and note the value set to\r\n  loaded_genutils variable.\r\n- Install the older version of genutils (non autoload version) in to\r\n  plugin directory, overwriting the existing file.\r\n- Open the plugin\/genutils.vim again and change the value of\r\n  loaded_genutils variable to the value you noted before and save it.\r\n\r\n","5":"Expand in your runtime (vimfiles\/.vim directory).\r\n\r\nPlace the following in your vimrc if you find them useful:\r\n\r\n- Add the following commands to create simple sort commands.\r\n    command! -nargs=0 -range=% SortByLength <line1>,<line2>call QSort(\r\n        \\ 'CmpByLineLengthNname', 1)\r\n    command! -nargs=0 -range=% RSortByLength <line1>,<line2>call QSort(\r\n        \\ 'CmpByLineLengthNname', -1)\r\n    command! -nargs=0 -range=% SortJavaImports <line1>,<line2>call QSort(\r\n        \\ 'CmpJavaImports', 1)\r\n                                                                           \r\n- You might like the following mappings to adjust spacing:\r\n    nnoremap <silent> <C-Space> :call ShiftWordInSpace(1)<CR>\r\n    nnoremap <silent> <C-BS> :call ShiftWordInSpace(-1)<CR>\r\n    nnoremap <silent> \\cw :call CenterWordInSpace()<CR>\r\n    nnoremap <silent> \\va :call AlignWordWithWordInPreviousLine()<CR>\r\n                                                                           \r\n- The :find command is very useful to search for a file in path, but it\r\n  doesn't support file completion. Add the following command in your vimrc\r\n  to add this functionality:\r\n      command! -nargs=1 -bang -complete=customlist,genutils#UserFileComplete2\r\n            \\ FindInPath :find<bang> <args>\r\n                                                                           \r\n- If you are running commands that generate multiple pages of output, you\r\n  might find it useful to redirect the output to a new buffer. Put the\r\n  following command in your vimrc:\r\n    command! -nargs=* -complete=command Redir\r\n          \\ :new | put! =GetVimCmdOutput('<args>') | setl bufhidden=wipe |\r\n          \\ setl nomodified\r\n\r\n\r\nFor version prior to 2.0:\r\nDrop it in the plugin directory or source it from vimrc.\r\nAlso install multvals.vim: vimscript #171\r\n\r\nSpecial instructions for the coexistence of autoload (version since 2.0) and non-autoload (prior to 2.0) versions of genutils:\r\n- Install the latest version of genutils first. Overwriting all existing\r\n  files.\r\n- Open the plugin\/genutils.vim file and note the value set to\r\n  loaded_genutils variable.\r\n- Install the older version of genutils (non autoload version) in to\r\n  plugin directory, overwriting the existing file.\r\n- Open the plugin\/genutils.vim again and change the value of\r\n  loaded_genutils variable to the value you noted before and save it.\r\n\r\n","first_name":"Hari Krishna","6":"Hari Krishna","last_name":"Dara","7":"Dara","releases":[{"0":"197","vim_version":"7.0","1":"7.0","script_version":"2.5","2":"2.5","version_comment":"Re-uploading the zip file with the correct name.\r\n- Improved genutils#CleanupFileName() to expand \"~\" and environment\r\n  variables. It also works more reliably now.\r\n- More user friendly version of genutils#UserFileComplete() function\r\n  added as genutils#UserFileComplete2(). It can now be used directly as\r\n  the custom or customlist function in commands (so saves trouble for\r\n  users, as no wrapper needs be written), and also offer various\r\n  customizations via passing params.\r\n- New function genutils#UserDirComplete2(), which is a customization on\r\n  top of genutils#UserFileComplete2() for the sake of restricting the\r\n  completions to directories only.\r\n- Minor improvements in genutils#PathIsAbsolute() and\r\n  genutils#GetVimCmdOutput() ","3":"Re-uploading the zip file with the correct name.\r\n- Improved genutils#CleanupFileName() to expand \"~\" and environment\r\n  variables. It also works more reliably now.\r\n- More user friendly version of genutils#UserFileComplete() function\r\n  added as genutils#UserFileComplete2(). It can now be used directly as\r\n  the custom or customlist function in commands (so saves trouble for\r\n  users, as no wrapper needs be written), and also offer various\r\n  customizations via passing params.\r\n- New function genutils#UserDirComplete2(), which is a customization on\r\n  top of genutils#UserFileComplete2() for the sake of restricting the\r\n  completions to directories only.\r\n- Minor improvements in genutils#PathIsAbsolute() and\r\n  genutils#GetVimCmdOutput() ","package":"genutils-2.5.zip","4":"genutils-2.5.zip","src_id":"11399","5":"11399","creation_date":"1253228255","6":"1253228255"},{"0":"197","vim_version":"7.0","1":"7.0","script_version":"2.4","2":"2.4","version_comment":"- Fixed some corner cases in RelPathFromDir()\/RelPathFromFile().\r\n- Made the default comparators sort() function friendly.\r\n","3":"- Fixed some corner cases in RelPathFromDir()\/RelPathFromFile().\r\n- Made the default comparators sort() function friendly.\r\n","package":"genutils-2.4.zip","4":"genutils-2.4.zip","src_id":"7231","5":"7231","creation_date":"1181659519","6":"1181659519"},{"0":"197","vim_version":"7.0","1":"7.0","script_version":"2.3","2":"2.3","version_comment":"- SilentSubstitute() and SilentDelete() should preserve cursor position.\r\n- CleanupFileName() should also remove any leading or trailing\r\n  whitespace.\r\n","3":"- SilentSubstitute() and SilentDelete() should preserve cursor position.\r\n- CleanupFileName() should also remove any leading or trailing\r\n  whitespace.\r\n","package":"genutils-2.3.zip","4":"genutils-2.3.zip","src_id":"6138","5":"6138","creation_date":"1157277996","6":"1157277996"},{"0":"197","vim_version":"7.0","1":"7.0","script_version":"2.2","2":"2.2","version_comment":"- EscapeCommand() now supports Lists as arguments.\r\n- CrUnProtectedCharsPattern() now accepts an optional \"capture\"\r\n  argument.\r\n- Renamed PromptForElement2 to PromptForElement. It was a typo.\r\n","3":"- EscapeCommand() now supports Lists as arguments.\r\n- CrUnProtectedCharsPattern() now accepts an optional \"capture\"\r\n  argument.\r\n- Renamed PromptForElement2 to PromptForElement. It was a typo.\r\n","package":"genutils-2.2.zip","4":"genutils-2.2.zip","src_id":"6121","5":"6121","creation_date":"1157026962","6":"1157026962"},{"0":"197","vim_version":"7.0","1":"7.0","script_version":"2.1","2":"2.1","version_comment":"- Fixed a typo in AddNotifyWindowClose() in the previous release.\r\n- Added BinSearchList() function. \r\n(uploading again to correct the Vim compatibility information, sorry to bump up)","3":"- Fixed a typo in AddNotifyWindowClose() in the previous release.\r\n- Added BinSearchList() function. \r\n(uploading again to correct the Vim compatibility information, sorry to bump up)","package":"genutils-2.1.zip","4":"genutils-2.1.zip","src_id":"6053","5":"6053","creation_date":"1155133650","6":"1155133650"},{"0":"197","vim_version":"7.0","1":"7.0","script_version":"2.0","2":"2.0","version_comment":"genutils 2.0 release for Vim7.0.\r\nThis release is not backwards compatible with previous genutils or Vim\r\nversions, so download this version only when a plugin explicitly\r\ndepends on this version. If you want to use plugins that use both the\r\nold and new version of genutils, then you need to follow the below\r\nprocedure so that both can co-exist:\r\n- Install the latest version of genutils first. Overwriting all existing\r\n  files.\r\n- Open the plugin\/genutils.vim file and note the value set to\r\n  loaded_genutils variable.\r\n- Install the older version of genutils (non autoload version) in to\r\n  plugin directory, overwriting the existing file.\r\n- Open the plugin\/genutils.vim again and change the value of\r\n  loaded_genutils variable to the value you noted before and save it.\r\n\r\nThis version has the following changes:\r\n- No longer depends on multvals plugin. Inherits some useful functions\r\n  from multvals to make way for it to be retired (in favor of Vim7\r\n  arrays). New functions are:\r\n  CrUnProtectedCharsPattern\r\n  PromptForElement\/GetSelectedIndex\r\n- Fix for Save\/RestoreHardPosition() not working right when there are\r\n  wrapped lines in the window.\r\n- Dropped the AddToFCShell and RemoveFromFCShell functions as these\r\n  can't be implemented in Vim7 because of new restrictions on\r\n  FileChangedShell autocommand. Use AddToFcShellPre and\r\n  RemoveFromFCShellPre functions instead.\r\n","3":"genutils 2.0 release for Vim7.0.\r\nThis release is not backwards compatible with previous genutils or Vim\r\nversions, so download this version only when a plugin explicitly\r\ndepends on this version. If you want to use plugins that use both the\r\nold and new version of genutils, then you need to follow the below\r\nprocedure so that both can co-exist:\r\n- Install the latest version of genutils first. Overwriting all existing\r\n  files.\r\n- Open the plugin\/genutils.vim file and note the value set to\r\n  loaded_genutils variable.\r\n- Install the older version of genutils (non autoload version) in to\r\n  plugin directory, overwriting the existing file.\r\n- Open the plugin\/genutils.vim again and change the value of\r\n  loaded_genutils variable to the value you noted before and save it.\r\n\r\nThis version has the following changes:\r\n- No longer depends on multvals plugin. Inherits some useful functions\r\n  from multvals to make way for it to be retired (in favor of Vim7\r\n  arrays). New functions are:\r\n  CrUnProtectedCharsPattern\r\n  PromptForElement\/GetSelectedIndex\r\n- Fix for Save\/RestoreHardPosition() not working right when there are\r\n  wrapped lines in the window.\r\n- Dropped the AddToFCShell and RemoveFromFCShell functions as these\r\n  can't be implemented in Vim7 because of new restrictions on\r\n  FileChangedShell autocommand. Use AddToFcShellPre and\r\n  RemoveFromFCShellPre functions instead.\r\n","package":"genutils-2.0.zip","4":"genutils-2.0.zip","src_id":"5853","5":"5853","creation_date":"1151071894","6":"1151071894"},{"0":"197","vim_version":"6.0","1":"6.0","script_version":"1.20","2":"1.20","version_comment":"Release 1.20 for fixing an issue with my previous release. Thanks to\r\nNiels, Delphin and Craig for reporting the problem. If you downloaded the latest selectbuf, please download this version of genutils.\r\n","3":"Release 1.20 for fixing an issue with my previous release. Thanks to\r\nNiels, Delphin and Craig for reporting the problem. If you downloaded the latest selectbuf, please download this version of genutils.\r\n","package":"genutils.vim","4":"genutils.vim","src_id":"5663","5":"5663","creation_date":"1147172213","6":"1147172213"},{"0":"197","vim_version":"6.0","1":"6.0","script_version":"1.19","2":"1.19","version_comment":"Now Vim7 compatible, no functionality change.","3":"Now Vim7 compatible, no functionality change.","package":"genutils.vim","4":"genutils.vim","src_id":"5658","5":"5658","creation_date":"1147100954","6":"1147100954"},{"0":"197","vim_version":"6.0","1":"6.0","script_version":"1.18","2":"1.18","version_comment":"- New functions OpenWinNoEa() and CloseWinNoEa() which open and close\r\n  windows with minimal side effects (such as minimizing the impact on\r\n  the current window sizes, restoring the cursor to the original window\r\n  and even restoring the current-previous-window). This is a good\r\n  alternative to using the existing Save\/RestoreWindowSettings()\r\n  method.\r\n- GetShellEnvType() is now public. Useful in conjunction with the\r\n  EscapeCommand() function.\r\n","3":"- New functions OpenWinNoEa() and CloseWinNoEa() which open and close\r\n  windows with minimal side effects (such as minimizing the impact on\r\n  the current window sizes, restoring the cursor to the original window\r\n  and even restoring the current-previous-window). This is a good\r\n  alternative to using the existing Save\/RestoreWindowSettings()\r\n  method.\r\n- GetShellEnvType() is now public. Useful in conjunction with the\r\n  EscapeCommand() function.\r\n","package":"genutils.vim","4":"genutils.vim","src_id":"4033","5":"4033","creation_date":"1110978481","6":"1110978481"},{"0":"197","vim_version":"6.0","1":"6.0","script_version":"1.17","2":"1.17","version_comment":"- Minor corrections to the FindBufferForName() function to work well\r\n  with filenames containing backslashes (see doc).","3":"- Minor corrections to the FindBufferForName() function to work well\r\n  with filenames containing backslashes (see doc).","package":"genutils.vim","4":"genutils.vim","src_id":"3583","5":"3583","creation_date":"1098991013","6":"1098991013"},{"0":"197","vim_version":"6.0","1":"6.0","script_version":"1.16","2":"1.16","version_comment":"- Fast BinInsertSort() based on the BISort() by Peit Delport's.\r\n- Slightly improved QSort().\r\n","3":"- Fast BinInsertSort() based on the BISort() by Peit Delport's.\r\n- Slightly improved QSort().\r\n","package":"genutils.vim","4":"genutils.vim","src_id":"3565","5":"3565","creation_date":"1098292251","6":"1098292251"},{"0":"197","vim_version":"6.0","1":"6.0","script_version":"1.15","2":"1.15","version_comment":"New functions:\r\n- CloseWindow()\r\n- MarkActiveWindow()\r\n- RestoreActiveWindow()\r\nNew overloaded function for:\r\n- SilentDelete()\r\n\r\n- Fixed IsOnlyVerticalWindow() and IsOnlyHorizontalWindow() to use\r\n  MarkActiveWindow() and RestoreActiveWindow() to avoid corrupting the\r\n  \"previous-window\".\r\n","3":"New functions:\r\n- CloseWindow()\r\n- MarkActiveWindow()\r\n- RestoreActiveWindow()\r\nNew overloaded function for:\r\n- SilentDelete()\r\n\r\n- Fixed IsOnlyVerticalWindow() and IsOnlyHorizontalWindow() to use\r\n  MarkActiveWindow() and RestoreActiveWindow() to avoid corrupting the\r\n  \"previous-window\".\r\n","package":"genutils.vim","4":"genutils.vim","src_id":"3559","5":"3559","creation_date":"1098123651","6":"1098123651"},{"0":"197","vim_version":"6.0","1":"6.0","script_version":"1.14","2":"1.14","version_comment":"- New functions: GetNextWinnrInStack, GetLastWinnrInStack, MoveCursorToNextInWinStack, MoveCursorToLastInWinStack based on Dr. Chip's WinStackMv() function.\r\n- New functions: SaveVisualSelection, RestoreVisualSelection.\r\n- FIxed a possible issue with my earlier change. You can't add to 'eventignore'  if its current value is \"all\".\r\n- Some improvement to RestoreWindowSettings(). It is still not working perfectly. Actually, there are no commands available in Vim to accurately resize windows in all circumstances.\r\n- Save\/Restore functions for cursor positions now create marks in the buffer context. This means, you can use the same name to create marks in different buffers, without overwriting each other. This is how Vim works for lowercase marks anyway.\r\n- Misc. other improvements\/bugfixes.","3":"- New functions: GetNextWinnrInStack, GetLastWinnrInStack, MoveCursorToNextInWinStack, MoveCursorToLastInWinStack based on Dr. Chip's WinStackMv() function.\r\n- New functions: SaveVisualSelection, RestoreVisualSelection.\r\n- FIxed a possible issue with my earlier change. You can't add to 'eventignore'  if its current value is \"all\".\r\n- Some improvement to RestoreWindowSettings(). It is still not working perfectly. Actually, there are no commands available in Vim to accurately resize windows in all circumstances.\r\n- Save\/Restore functions for cursor positions now create marks in the buffer context. This means, you can use the same name to create marks in different buffers, without overwriting each other. This is how Vim works for lowercase marks anyway.\r\n- Misc. other improvements\/bugfixes.","package":"genutils.vim","4":"genutils.vim","src_id":"3317","5":"3317","creation_date":"1092243152","6":"1092243152"},{"0":"197","vim_version":"6.0","1":"6.0","script_version":"1.13","2":"1.13","version_comment":"Now requires Vim 6.3\r\n\r\n- More documentation. I now added a section with all the supported functions at one place so it is easy to lookup.\r\n- New function GetBufNameForAU().\r\n- New functions to help write custom completion functions, UserFileComplete() and UserFileExpand()\r\n- Some clarifications on EscapeCommand().\r\n- Improved CleanFileName() to work with Windows UNC paths.","3":"Now requires Vim 6.3\r\n\r\n- More documentation. I now added a section with all the supported functions at one place so it is easy to lookup.\r\n- New function GetBufNameForAU().\r\n- New functions to help write custom completion functions, UserFileComplete() and UserFileExpand()\r\n- Some clarifications on EscapeCommand().\r\n- Improved CleanFileName() to work with Windows UNC paths.","package":"genutils.vim","4":"genutils.vim","src_id":"3211","5":"3211","creation_date":"1089204026","6":"1089204026"},{"0":"197","vim_version":"6.0","1":"6.0","script_version":"1.12","2":"1.12","version_comment":"- New function EscapeCommand() extracted from my perforce.vim plugin. This\r\n  makes it simpler for plugins to execute external commands passing\r\n  arguments literally.\r\n- New functions IsOnlyHorizontalWindow(), IsOnlyVerticalWindow(),\r\n  QuoteStr(), SilentSubstitute(), SilentDelete()\r\n- More documentation on GetPreviewWinnr(), DefFileChangedShell(),\r\n  MakeArgumentString(), MakeArgumentList(), UnEscape(), GetSpacer()\r\n","3":"- New function EscapeCommand() extracted from my perforce.vim plugin. This\r\n  makes it simpler for plugins to execute external commands passing\r\n  arguments literally.\r\n- New functions IsOnlyHorizontalWindow(), IsOnlyVerticalWindow(),\r\n  QuoteStr(), SilentSubstitute(), SilentDelete()\r\n- More documentation on GetPreviewWinnr(), DefFileChangedShell(),\r\n  MakeArgumentString(), MakeArgumentList(), UnEscape(), GetSpacer()\r\n","package":"genutils.vim","4":"genutils.vim","src_id":"3148","5":"3148","creation_date":"1087568083","6":"1087568083"},{"0":"197","vim_version":"6.0","1":"6.0","script_version":"1.11","2":"1.11","version_comment":"- Most important change is a lot of documentation with function prototypes. Now it is not necessary to look into the code to see the help and usage information. I also documented a lot of functions that lacked documentation earlier.\r\n- A few minor fixes to bugs\/inconsistencies and other improvements in Escape(), RestoreSoftPosition, Notify window close related functionality. Also added a patch from Bram for persistence related funcationality.","3":"- Most important change is a lot of documentation with function prototypes. Now it is not necessary to look into the code to see the help and usage information. I also documented a lot of functions that lacked documentation earlier.\r\n- A few minor fixes to bugs\/inconsistencies and other improvements in Escape(), RestoreSoftPosition, Notify window close related functionality. Also added a patch from Bram for persistence related funcationality.","package":"genutils.vim","4":"genutils.vim","src_id":"2890","5":"2890","creation_date":"1080586082","6":"1080586082"},{"0":"197","vim_version":"6.0","1":"6.0","script_version":"1.10","2":"1.10","version_comment":"- Fixed bugs in the RelPathFromFile and RelPathFromDir functions.\r\n- The g:loaded_genutils variable now contains the version number for dependency checking (see \":help v:version\" for format). If your plugin depends on genutils.vim, it is now easy and safe to check if the user has at least the minimum base version.","3":"- Fixed bugs in the RelPathFromFile and RelPathFromDir functions.\r\n- The g:loaded_genutils variable now contains the version number for dependency checking (see \":help v:version\" for format). If your plugin depends on genutils.vim, it is now easy and safe to check if the user has at least the minimum base version.","package":"genutils.vim","4":"genutils.vim","src_id":"2608","5":"2608","creation_date":"1071685724","6":"1071685724"},{"0":"197","vim_version":"6.0","1":"6.0","script_version":"1.9","2":"1.9","version_comment":"Misc. functions added: GetSpacer, GetPreviewWinnr, ExtractFuncListing, UnEscape, GetLine\/ColPosition. Removed undocumented IsPreviewWindowOpen function. See description for more details.","3":"Misc. functions added: GetSpacer, GetPreviewWinnr, ExtractFuncListing, UnEscape, GetLine\/ColPosition. Removed undocumented IsPreviewWindowOpen function. See description for more details.","package":"genutils.vim","4":"genutils.vim","src_id":"2436","5":"2436","creation_date":"1067517974","6":"1067517974"},{"0":"197","vim_version":"6.0","1":"6.0","script_version":"1.8","2":"1.8","version_comment":"When disabling persistence feature using g:genutilsNoPersist, it is possible for the plugins that depend on it to fail. Fixed it.","3":"When disabling persistence feature using g:genutilsNoPersist, it is possible for the plugins that depend on it to fail. Fixed it.","package":"genutils.vim","4":"genutils.vim","src_id":"2276","5":"2276","creation_date":"1062094946","6":"1062094946"},{"0":"197","vim_version":"6.0","1":"6.0","script_version":"1.7","2":"1.7","version_comment":"Misc. changes, see script for more details.\r\n- The scriptlets g:makeArgumentString g:makeArgumentList have been replaced with new function MakeArgumentString() and MakeArgumentList() and the usage now is more concise. The old usage is now deprecated.\r\n- New functions Escape(), GetVimCmdOutput() and OptClearBuffer()\r\n- New utility functions for signs, CurLineHasSign() and ClearAllSigns().\r\n- Fixed bugs in FindWindowForName().\r\n- The FindWindowForBuffer() function is now redundant and is deprecated, use bufwinnr(FindBufferForName(fileName)) for the same purpose.\r\n- Some improvements for Vim6.2, but it should still work with Vim6.0.\r\n- Fixed a few bugs.","3":"Misc. changes, see script for more details.\r\n- The scriptlets g:makeArgumentString g:makeArgumentList have been replaced with new function MakeArgumentString() and MakeArgumentList() and the usage now is more concise. The old usage is now deprecated.\r\n- New functions Escape(), GetVimCmdOutput() and OptClearBuffer()\r\n- New utility functions for signs, CurLineHasSign() and ClearAllSigns().\r\n- Fixed bugs in FindWindowForName().\r\n- The FindWindowForBuffer() function is now redundant and is deprecated, use bufwinnr(FindBufferForName(fileName)) for the same purpose.\r\n- Some improvements for Vim6.2, but it should still work with Vim6.0.\r\n- Fixed a few bugs.","package":"genutils.vim","4":"genutils.vim","src_id":"2263","5":"2263","creation_date":"1061823987","6":"1061823987"},{"0":"197","vim_version":"6.0","1":"6.0","script_version":"1.6","2":"1.6","version_comment":"Minor fixes\/updates. Fixed a bug in restoring line position with respect to window. Users of FileChangedShell functionality provided by the plugin (and thus the perforce plugin), should download this version only if the 6.1.220 patch is installed.","3":"Minor fixes\/updates. Fixed a bug in restoring line position with respect to window. Users of FileChangedShell functionality provided by the plugin (and thus the perforce plugin), should download this version only if the 6.1.220 patch is installed.","package":"genutils.vim","4":"genutils.vim","src_id":"1959","5":"1959","creation_date":"1051894477","6":"1051894477"},{"0":"197","vim_version":"6.0","1":"6.0","script_version":"1.5","2":"1.5","version_comment":"My earlier version was using :normal instead of :normal! command, so user's mapping will interfere with it. If you have downloaded 1.4 earlier, please download it again. Thanks to David Rennalls for reporting the problem.","3":"My earlier version was using :normal instead of :normal! command, so user's mapping will interfere with it. If you have downloaded 1.4 earlier, please download it again. Thanks to David Rennalls for reporting the problem.","package":"genutils.vim","4":"genutils.vim","src_id":"1878","5":"1878","creation_date":"1049036968","6":"1049036968"},{"0":"197","vim_version":"6.0","1":"6.0","script_version":"1.4","2":"1.4","version_comment":"Some bugfixes and improvements.\r\n- New UnEscape() which is more close to escape() than the old DeEscape().\r\n- ExecMap() is separated as a new plugin. That is the better place for it as it is not really useful as a library function.\r\n- The sort compare methods were made public as they are very useful in writing new compares.\r\n- Some update on doc.\r\n- Now CreateArgString() can be used with an arbitrary pattern.\r\n- Fixed some bugs in MoveCurLineToWinLine(). It works better now.\r\n- Added a functions to handle FileChangedShell autocommand and emulate the default vim behavior.","3":"Some bugfixes and improvements.\r\n- New UnEscape() which is more close to escape() than the old DeEscape().\r\n- ExecMap() is separated as a new plugin. That is the better place for it as it is not really useful as a library function.\r\n- The sort compare methods were made public as they are very useful in writing new compares.\r\n- Some update on doc.\r\n- Now CreateArgString() can be used with an arbitrary pattern.\r\n- Fixed some bugs in MoveCurLineToWinLine(). It works better now.\r\n- Added a functions to handle FileChangedShell autocommand and emulate the default vim behavior.","package":"genutils.vim","4":"genutils.vim","src_id":"1845","5":"1845","creation_date":"1048434475","6":"1048434475"},{"0":"197","vim_version":"6.0","1":"6.0","script_version":"1.3","2":"1.3","version_comment":"GPLed it for the use by Cream project. See http:\/\/cream.sf.net for information on Cream for Vim.","3":"GPLed it for the use by Cream project. See http:\/\/cream.sf.net for information on Cream for Vim.","package":"genutils.vim","4":"genutils.vim","src_id":"1530","5":"1530","creation_date":"1039093524","6":"1039093524"},{"0":"197","vim_version":"6.0","1":"6.0","script_version":"1.2","2":"1.2","version_comment":"- Generalized Quick sort function. The sort routine is no longer tied to the\r\n  buffer contents (multvals.vim uses this function to sort arrays).\r\n- A binary search function that can be used to incrementally update sorted\r\n  buffer contents (like buffer lists, tag lists etc), and a generalized variant\r\n  of this function which is no tied to the buffer contents.\r\n- A new comparator to sort Java imports first by name and then by their length.\r\n  This groups the imports from the same package pretty well together.\r\n- Minor fixes in FindWindowForBuffer() and FindBufferForWindow()\r\n","3":"- Generalized Quick sort function. The sort routine is no longer tied to the\r\n  buffer contents (multvals.vim uses this function to sort arrays).\r\n- A binary search function that can be used to incrementally update sorted\r\n  buffer contents (like buffer lists, tag lists etc), and a generalized variant\r\n  of this function which is no tied to the buffer contents.\r\n- A new comparator to sort Java imports first by name and then by their length.\r\n  This groups the imports from the same package pretty well together.\r\n- Minor fixes in FindWindowForBuffer() and FindBufferForWindow()\r\n","package":"genutils.vim","4":"genutils.vim","src_id":"1491","5":"1491","creation_date":"1038317800","6":"1038317800"},{"0":"197","vim_version":"6.0","1":"6.0","script_version":"1.1","2":"1.1","version_comment":"New functions \r\n  - CenterWordInSpace(), useful if you use Align.vim and want to center the text horizontally in the boxes.\r\n  - Improved ShiftWordInSpace().\r\n  - New collection from list, CommonPath() with minor improvements. Added RelPathFromFile() and RelPathFromDir() functions.\r\n  - New persistence functions, PutPersistenceVar() and GetPersistenceVar() functions to save and retrieve your script variables across vim sessions without stepping on another script's name space.\r\n  -- Minor fixes in CleanupFileName() function.","3":"New functions \r\n  - CenterWordInSpace(), useful if you use Align.vim and want to center the text horizontally in the boxes.\r\n  - Improved ShiftWordInSpace().\r\n  - New collection from list, CommonPath() with minor improvements. Added RelPathFromFile() and RelPathFromDir() functions.\r\n  - New persistence functions, PutPersistenceVar() and GetPersistenceVar() functions to save and retrieve your script variables across vim sessions without stepping on another script's name space.\r\n  -- Minor fixes in CleanupFileName() function.","package":"genutils.vim","4":"genutils.vim","src_id":"1121","5":"1121","creation_date":"1029282658","6":"1029282658"},{"0":"197","vim_version":"6.0","1":"6.0","script_version":"1.0.24","2":"1.0.24","version_comment":"New function, AlignWordWithWordInPreviousLine(). Improved ExecMap(), it is now much more useful. Added new scriptlet, g:makeArgumentList and its companion function, CreateArgString().","3":"New function, AlignWordWithWordInPreviousLine(). Improved ExecMap(), it is now much more useful. Added new scriptlet, g:makeArgumentList and its companion function, CreateArgString().","package":"genutils.vim","4":"genutils.vim","src_id":"791","5":"791","creation_date":"1018638290","6":"1018638290"},{"0":"197","vim_version":"6.0","1":"6.0","script_version":"1.0.20","2":"1.0.20","version_comment":"Fixed a typo in ResetWindowSettings(). Update the previous version to fix an error while quitting selectbuf or perforce help window.","3":"Fixed a typo in ResetWindowSettings(). Update the previous version to fix an error while quitting selectbuf or perforce help window.","package":"genutils.vim","4":"genutils.vim","src_id":"731","5":"731","creation_date":"1017427042","6":"1017427042"},{"0":"197","vim_version":"6.0","1":"6.0","script_version":"1.0.19","2":"1.0.19","version_comment":"Minor changes. Fixed FindWindowForBuffer and other functions to take care of the extra backslashes in the filenames protecting the spaces etc. Save\/RestoreWindowSettings functions now have a variant that takes in a key. This key can be used to call these function from multiple scripts at the same time without overwriting each other's settings. Some new functions.","3":"Minor changes. Fixed FindWindowForBuffer and other functions to take care of the extra backslashes in the filenames protecting the spaces etc. Save\/RestoreWindowSettings functions now have a variant that takes in a key. This key can be used to call these function from multiple scripts at the same time without overwriting each other's settings. Some new functions.","package":"genutils.vim","4":"genutils.vim","src_id":"718","5":"718","creation_date":"1017170308","6":"1017170308"},{"0":"197","vim_version":"6.0","1":"6.0","script_version":"1.0.15","2":"1.0.15","version_comment":"- Fixed minor issues with makeArgumentString.\r\n- New functions to do quick sort on the current window contents. A command to sort lines by their length.\r\n- A Basic help\/description is added at the start of the script.","3":"- Fixed minor issues with makeArgumentString.\r\n- New functions to do quick sort on the current window contents. A command to sort lines by their length.\r\n- A Basic help\/description is added at the start of the script.","package":"genutils.vim","4":"genutils.vim","src_id":"666","5":"666","creation_date":"1015603937","6":"1015603937"},{"0":"197","vim_version":"6.0","1":"6.0","script_version":"1.0.11","2":"1.0.11","version_comment":"New utility to pass variable number of arugments to other functions. Ex usage:\r\n   fu! s:IF(...)\r\n     exec g:makeArgumentString\r\n     exec \"call Impl(\" . argumentString . \")\"\r\n   endfu\r\n\r\nNew OnMS() function to check for any windoze OS. New utility ShiftWordInSpace() and SetupScratchBuffer() functions. Add the following mappings to move words in the white space:\r\n\r\nnoremap <silent> <C-Space> :call ShiftWordInSpace(1)<CR>\r\nnoremap <silent> <C-BS> :call ShiftWordInSpace(-1)<CR>\r\n","3":"New utility to pass variable number of arugments to other functions. Ex usage:\r\n   fu! s:IF(...)\r\n     exec g:makeArgumentString\r\n     exec \"call Impl(\" . argumentString . \")\"\r\n   endfu\r\n\r\nNew OnMS() function to check for any windoze OS. New utility ShiftWordInSpace() and SetupScratchBuffer() functions. Add the following mappings to move words in the white space:\r\n\r\nnoremap <silent> <C-Space> :call ShiftWordInSpace(1)<CR>\r\nnoremap <silent> <C-BS> :call ShiftWordInSpace(-1)<CR>\r\n","package":"genutils.vim","4":"genutils.vim","src_id":"643","5":"643","creation_date":"1014674179","6":"1014674179"},{"0":"197","vim_version":"6.0","1":"6.0","script_version":"1.0.8","2":"1.0.8","version_comment":"Improved the save\/restore position to even save\/restore the line position in the window. Take a look at the set of Save\/Restore\/ResetSoft\/HardPosition() functions.","3":"Improved the save\/restore position to even save\/restore the line position in the window. Take a look at the set of Save\/Restore\/ResetSoft\/HardPosition() functions.","package":"genutils.vim","4":"genutils.vim","src_id":"549","5":"549","creation_date":"1012849927","6":"1012849927"},{"0":"197","vim_version":"6.0","1":"6.0","script_version":"1.0.7","2":"1.0.7","version_comment":"Initial upload","3":"Initial upload","package":"genutils.vim","4":"genutils.vim","src_id":"526","5":"526","creation_date":"1012591383","6":"1012591383"}]},"196":{"script_id":"196","0":"196","script_name":"vcal.vim","1":"vcal.vim","script_type":"utility","2":"utility","summary":"Vcal.vim is a simple scheduling calendar script.","3":"Vcal.vim is a simple scheduling calendar script.","description":"Vcal.vim is a calendar plugin that can read vcard files.  Appointments can be set and it can handle simple recurring dates.  This currently only works on Linux.","4":"Vcal.vim is a calendar plugin that can read vcard files.  Appointments can be set and it can handle simple recurring dates.  This currently only works on Linux.","install_details":"Untar the vcal archive.  The README file contains installation instructions.","5":"Untar the vcal archive.  The README file contains installation instructions.","first_name":"Ken","6":"Ken","last_name":"Steen","7":"Steen","releases":[{"0":"196","vim_version":"6.0","1":"6.0","script_version":"0.2","2":"0.2","version_comment":"This version contains some fixes for repeating dates.","3":"This version contains some fixes for repeating dates.","package":"vcal-0.2.tar.gz","4":"vcal-0.2.tar.gz","src_id":"1127","5":"1127","creation_date":"1029357995","6":"1029357995"},{"0":"196","vim_version":"6.0","1":"6.0","script_version":".1","2":".1","version_comment":"Initial upload","3":"Initial upload","package":"vcal-0.1.tar.gz","4":"vcal-0.1.tar.gz","src_id":"524","5":"524","creation_date":"1012558490","6":"1012558490"}]},"195":{"script_id":"195","0":"195","script_name":"Engspchk","1":"Engspchk","script_type":"syntax","2":"syntax","summary":"Spelling checker: On-the-fly spell checking, multi-language, alternate spellings","3":"Spelling checker: On-the-fly spell checking, multi-language, alternate spellings","description":"There are a fair number of ispell\/aspell based spelling checkers out there -- but engspchk isn't one of them.  The engspchk source uses Vim's native syntax highlighting to catch spelling errors, so you get quick on-the-fly spellchecking!  An optional external program, agrep, may be used to suggest alternative spellings. With the optional <engspchk.rare> dictionary, <engspchk.vim> now provides over 186730 words (over 189000 when including proper names)!\r\n\r\nEngspchk flags rare\/unusual words and allows the user to specify his\/her preferred dialect (let g:spchkdialect=\"usa\", \"uk\", or \"can\").  Click-N-Fix by enabling the mouse (example: :set mouse=n) and a leftmouse click in the document will advance the cursor to the next spelling error; a leftmouse click in the alternative spellings window will substitute the selected word for the misspelled word.  A rightmouse click will do that substitute for all such misspellings in your file.\r\n\r\nEngspchk is no longer English-only: it supports multiple languages.  You can tell it what language (dictionary) to use by either renaming it (ex.  engspchk.vim -> frspchk.vim for French) or by specifying the variable g:spchklang (ex. let g:spchklang=\"ger\" for German).  See http:\/\/www.drchip.org\/astronaut\/vim\/index.html#vimlinks_scripts for some dictionaries: currently, that includes Dutch, French, Galician, German, Hungarian, Italian, Polish, Russian, Spanish, and Yiddish.\r\n\r\nThe engspchk s\/w includes maps for jumping to the next and preceding spelling errors, alternative spellings, and for saving words either permanently in a custom dictionary or just for the current session.\r\n\r\nEngspchk's dictionaries are optional.  SpellChecker, for example, claims to load faster because it doesn't handle unusual words.  Merely deleting <CVIMSYN\/engspchk.rare> will speed up loading (which is pretty fast anyway).  Both support flagging dialect-sensitive words, but only Engspchk has Click-N-Fix and rare word support.  Telling the difference between \"or the\" and \"ort he\" is easy -- the \"ort\" will show up with RareWord highlighting (default: black on cyan).\r\n\r\nTo begin checking your spelling with engspchk, and assuming that <engspchk.vim> has been put into your .vim\/plugin directory, simply start up engspchk by applying the English Check map:\r\n\r\n    \\ec\r\n\r\nand your spelling errors will show up highlighted in white-on-red.  Alternatively, if you're using gvim, select DrChip:Load Spelling Checker from the menu.\r\n\r\nIf you want to change languages, engspchk provides a lot of ways to help you:\r\n\r\n  * set g:spchklang appropriately and \\ec will load that language's dictionary.  The backslash is actually using <mapleader>, so you can customize the backslash to whatever you want.\r\n  * you may embed a modeline at the beginning or at the end of the file:  ex. spchk: lang=nl.\r\n  * using gvim, there's a \"Load AltLang Spelling Checker\" submenu for choosing whatever language(s) for which you have dictionaries!\r\n  * engspchk looks over your dictionaries and constructs simple commands: :Engspchk  :Frspchk  :Gerspchk  :Nlspchk  :Spanspchk  etc,\r\n\r\nIt will work with some cooperating syntax files to check out spelling in comments, including:\r\n\r\namiga, bib, c, cpp, csh, d, dcl, dtml, elmfilt, exports, fortran, html, java, lex, lisp, mail, maple, sh, sm, smarty, tcsh, tex, vim, and xmath\r\n\r\nIf your favorite computer language isn't on that list, perhaps you can talk that language's maintainer into making it engspchk compatible.\r\n\r\nMore Features:\r\n\r\nVersion 42-45:\r\n  click'n'fix button support improved: with a click, one can re-try alternates, accept misspellings (skip by them), and apply corrected spelling to entire document.  (see :he engspchk-clicknfix)\r\n\r\n  The alternative spellings window can now be either on the bottom or on the right hand side. (see :he engspchk-variables)\r\n\r\n  PreProc highlighting used to emphasize word selected for alternate spellings\r\n\r\n  A number of bug fixes -- see   :help |engspchk-history| (after downloading, of course!)\r\n\r\nVersion 41:\r\n    Engspchk can be loaded into multiple windows concurrently; one can force spell checking of non-highlighted text with the g:spchknonhl variable; RareWord and Dialect added to the @Spell cluster; and the 'hidden' option is set to allow preserve engspchk highlighting (\\ee will restore the user's hidden setting).\r\n\r\nVersion 40:\r\n    *@Spell cluster utilized.\r\n    *Allow two or more sequential capitalized\r\n     letters to be ignored (English only, acronym support).\r\n    *Yura Kloubakov's inclusion of the user's\r\n     mapleader in the DrChip menu and removal\r\n     of \\ec after use\r\n    *Entered dozens of city names into <engspchk.proper>\r\n\r\nVersion 34:\r\n    The latest engspchk includes:\r\n    differentiating between common, dialect, and rare words, saving\/restoring gdefault option maps to make a word a temporary\/permanent BadWord\r\n    Click-N-Fix\r\n\r\nVersion 32:\r\n    English dialects supported (usa can uk); bug fixes (ending engspchk, alternatives, etc)\r\n\r\n\r\nVersion 30:\r\n    Engspchk, the native Vim spelling checker, is better than ever!\r\n\r\n    * Click'n'Fix:\r\n      - leftmouse to move to the next error\r\n      - leftmouse to select correctly spelled word\r\n      - rightmouse to fix all instances of\r\n        misspelled word\r\n      Makes spell-checking a document Fast and Easy!\r\n\r\n    * New maps:\r\n      - \\eS, \\eT to take a word under the cursor\r\n        out of the user dictionary (permanently\r\n        or just this session)\r\n      - \\ee to end engspchk; restores prior maps\r\n        and restores normal highlighting\r\n      - <tab> in alternative-word window does\r\n        a global replace of the misspelled word\r\n        with the user-selected correctly spelled\r\n        word\r\n\r\n    * optional auto-jump to next spelling error\r\n      for \\es, \\et, and \\ea.\r\n    * will signal if syntax highlighting is off.\r\n    * Plus a bugfix for Mac users\r\n\r\n    Plus engspchk supports a non-English languages,\r\n    checks for spelling inside comments for C, C++,\r\n    Fortran, DCL (VMS), csh\/sh\/ksh\/bash, tex, and\r\n    more.\r\n\r\nVersion 27: New features for the Vim-based spelling checker!\r\n\r\n    * Maps to remove words from the user dictionary\r\n      (\\eT, \\eS).\r\n\r\n    * If g:spchk_autonext exists, then \\et, \\es, and\r\n      \\ea (if a word is selected) will automatically\r\n      do a \\en jump to the next spelling error.\r\n\r\n    * \\en and \\ep will now examine words inside folds,\r\n      opening the fold as necessary to display spelling\r\n      errors.\r\n\r\nVersion 23:\r\n    Can handle English, French, German, Spanish, Dutch,\r\n    Hungarian -- just set up a dictionary and set a\r\n    g:spchklang variable!  Native vim code, no external\r\n    programs necessary\r\n\r\nVersion 19:\r\n    Now contains: engspchk.vim engspchk.dict\r\n    engspchk.wb engspchk.txt Over 187192 words!\r\n    non-English support menus, documentation, English\r\n    punctuation checking (g:spchkpunc)\r\n\r\n\r\nAlternative Spelling Checkers\r\n    SpellChecker - Ajit Thakkar                   - syntax     - vimscript#499\r\n    vimspell          - Mathieu Clabaut            - [ia]spell   - vimscript#465\r\n    spellcheck      - Matthias Veit                 - ispell       - vimscript#131\r\n    spell                - Yegappan Lakshmanan - spell        - vimscript#232\r\n    vim-spell         - Luc Hermite                    - [ia]spell  - vimscript#135\r\n\r\n\r\nThank you for ranking engspchk!\r\n\r\n(alpha\/beta version available at http:\/\/mysite.verizon.net\/astronaut\/vim\/index.html#ENGSPCHK)\r\n","4":"There are a fair number of ispell\/aspell based spelling checkers out there -- but engspchk isn't one of them.  The engspchk source uses Vim's native syntax highlighting to catch spelling errors, so you get quick on-the-fly spellchecking!  An optional external program, agrep, may be used to suggest alternative spellings. With the optional <engspchk.rare> dictionary, <engspchk.vim> now provides over 186730 words (over 189000 when including proper names)!\r\n\r\nEngspchk flags rare\/unusual words and allows the user to specify his\/her preferred dialect (let g:spchkdialect=\"usa\", \"uk\", or \"can\").  Click-N-Fix by enabling the mouse (example: :set mouse=n) and a leftmouse click in the document will advance the cursor to the next spelling error; a leftmouse click in the alternative spellings window will substitute the selected word for the misspelled word.  A rightmouse click will do that substitute for all such misspellings in your file.\r\n\r\nEngspchk is no longer English-only: it supports multiple languages.  You can tell it what language (dictionary) to use by either renaming it (ex.  engspchk.vim -> frspchk.vim for French) or by specifying the variable g:spchklang (ex. let g:spchklang=\"ger\" for German).  See http:\/\/www.drchip.org\/astronaut\/vim\/index.html#vimlinks_scripts for some dictionaries: currently, that includes Dutch, French, Galician, German, Hungarian, Italian, Polish, Russian, Spanish, and Yiddish.\r\n\r\nThe engspchk s\/w includes maps for jumping to the next and preceding spelling errors, alternative spellings, and for saving words either permanently in a custom dictionary or just for the current session.\r\n\r\nEngspchk's dictionaries are optional.  SpellChecker, for example, claims to load faster because it doesn't handle unusual words.  Merely deleting <CVIMSYN\/engspchk.rare> will speed up loading (which is pretty fast anyway).  Both support flagging dialect-sensitive words, but only Engspchk has Click-N-Fix and rare word support.  Telling the difference between \"or the\" and \"ort he\" is easy -- the \"ort\" will show up with RareWord highlighting (default: black on cyan).\r\n\r\nTo begin checking your spelling with engspchk, and assuming that <engspchk.vim> has been put into your .vim\/plugin directory, simply start up engspchk by applying the English Check map:\r\n\r\n    \\ec\r\n\r\nand your spelling errors will show up highlighted in white-on-red.  Alternatively, if you're using gvim, select DrChip:Load Spelling Checker from the menu.\r\n\r\nIf you want to change languages, engspchk provides a lot of ways to help you:\r\n\r\n  * set g:spchklang appropriately and \\ec will load that language's dictionary.  The backslash is actually using <mapleader>, so you can customize the backslash to whatever you want.\r\n  * you may embed a modeline at the beginning or at the end of the file:  ex. spchk: lang=nl.\r\n  * using gvim, there's a \"Load AltLang Spelling Checker\" submenu for choosing whatever language(s) for which you have dictionaries!\r\n  * engspchk looks over your dictionaries and constructs simple commands: :Engspchk  :Frspchk  :Gerspchk  :Nlspchk  :Spanspchk  etc,\r\n\r\nIt will work with some cooperating syntax files to check out spelling in comments, including:\r\n\r\namiga, bib, c, cpp, csh, d, dcl, dtml, elmfilt, exports, fortran, html, java, lex, lisp, mail, maple, sh, sm, smarty, tcsh, tex, vim, and xmath\r\n\r\nIf your favorite computer language isn't on that list, perhaps you can talk that language's maintainer into making it engspchk compatible.\r\n\r\nMore Features:\r\n\r\nVersion 42-45:\r\n  click'n'fix button support improved: with a click, one can re-try alternates, accept misspellings (skip by them), and apply corrected spelling to entire document.  (see :he engspchk-clicknfix)\r\n\r\n  The alternative spellings window can now be either on the bottom or on the right hand side. (see :he engspchk-variables)\r\n\r\n  PreProc highlighting used to emphasize word selected for alternate spellings\r\n\r\n  A number of bug fixes -- see   :help |engspchk-history| (after downloading, of course!)\r\n\r\nVersion 41:\r\n    Engspchk can be loaded into multiple windows concurrently; one can force spell checking of non-highlighted text with the g:spchknonhl variable; RareWord and Dialect added to the @Spell cluster; and the 'hidden' option is set to allow preserve engspchk highlighting (\\ee will restore the user's hidden setting).\r\n\r\nVersion 40:\r\n    *@Spell cluster utilized.\r\n    *Allow two or more sequential capitalized\r\n     letters to be ignored (English only, acronym support).\r\n    *Yura Kloubakov's inclusion of the user's\r\n     mapleader in the DrChip menu and removal\r\n     of \\ec after use\r\n    *Entered dozens of city names into <engspchk.proper>\r\n\r\nVersion 34:\r\n    The latest engspchk includes:\r\n    differentiating between common, dialect, and rare words, saving\/restoring gdefault option maps to make a word a temporary\/permanent BadWord\r\n    Click-N-Fix\r\n\r\nVersion 32:\r\n    English dialects supported (usa can uk); bug fixes (ending engspchk, alternatives, etc)\r\n\r\n\r\nVersion 30:\r\n    Engspchk, the native Vim spelling checker, is better than ever!\r\n\r\n    * Click'n'Fix:\r\n      - leftmouse to move to the next error\r\n      - leftmouse to select correctly spelled word\r\n      - rightmouse to fix all instances of\r\n        misspelled word\r\n      Makes spell-checking a document Fast and Easy!\r\n\r\n    * New maps:\r\n      - \\eS, \\eT to take a word under the cursor\r\n        out of the user dictionary (permanently\r\n        or just this session)\r\n      - \\ee to end engspchk; restores prior maps\r\n        and restores normal highlighting\r\n      - <tab> in alternative-word window does\r\n        a global replace of the misspelled word\r\n        with the user-selected correctly spelled\r\n        word\r\n\r\n    * optional auto-jump to next spelling error\r\n      for \\es, \\et, and \\ea.\r\n    * will signal if syntax highlighting is off.\r\n    * Plus a bugfix for Mac users\r\n\r\n    Plus engspchk supports a non-English languages,\r\n    checks for spelling inside comments for C, C++,\r\n    Fortran, DCL (VMS), csh\/sh\/ksh\/bash, tex, and\r\n    more.\r\n\r\nVersion 27: New features for the Vim-based spelling checker!\r\n\r\n    * Maps to remove words from the user dictionary\r\n      (\\eT, \\eS).\r\n\r\n    * If g:spchk_autonext exists, then \\et, \\es, and\r\n      \\ea (if a word is selected) will automatically\r\n      do a \\en jump to the next spelling error.\r\n\r\n    * \\en and \\ep will now examine words inside folds,\r\n      opening the fold as necessary to display spelling\r\n      errors.\r\n\r\nVersion 23:\r\n    Can handle English, French, German, Spanish, Dutch,\r\n    Hungarian -- just set up a dictionary and set a\r\n    g:spchklang variable!  Native vim code, no external\r\n    programs necessary\r\n\r\nVersion 19:\r\n    Now contains: engspchk.vim engspchk.dict\r\n    engspchk.wb engspchk.txt Over 187192 words!\r\n    non-English support menus, documentation, English\r\n    punctuation checking (g:spchkpunc)\r\n\r\n\r\nAlternative Spelling Checkers\r\n    SpellChecker - Ajit Thakkar                   - syntax     - vimscript#499\r\n    vimspell          - Mathieu Clabaut            - [ia]spell   - vimscript#465\r\n    spellcheck      - Matthias Veit                 - ispell       - vimscript#131\r\n    spell                - Yegappan Lakshmanan - spell        - vimscript#232\r\n    vim-spell         - Luc Hermite                    - [ia]spell  - vimscript#135\r\n\r\n\r\nThank you for ranking engspchk!\r\n\r\n(alpha\/beta version available at http:\/\/mysite.verizon.net\/astronaut\/vim\/index.html#ENGSPCHK)\r\n","install_details":"1) put engspchk.tar.gz into your .vim directory\r\n2) gunzip engspchk.tar.gz\r\n3) tar -xvf engspchk.tar\r\n4) vim\r\n   :helptags ..wherever..\/.vim\/doc\r\n   :help engspchk-start  <-- startup directions for Unix\/Linux\/Cygwin\r\n   :help engspchk-win32  <-- startup directions for Windows\r\n\r\nFrom there the directions explain how to set up CVIMSYN, an environment\r\nvariable; how to set up Click-N-Fix; how to enable plugins; how to\r\nchoose a bottom-of-screen or right-side alternative-spellings window;\r\nand how to choose your preferred dialect.  Your choice!\r\n","5":"1) put engspchk.tar.gz into your .vim directory\r\n2) gunzip engspchk.tar.gz\r\n3) tar -xvf engspchk.tar\r\n4) vim\r\n   :helptags ..wherever..\/.vim\/doc\r\n   :help engspchk-start  <-- startup directions for Unix\/Linux\/Cygwin\r\n   :help engspchk-win32  <-- startup directions for Windows\r\n\r\nFrom there the directions explain how to set up CVIMSYN, an environment\r\nvariable; how to set up Click-N-Fix; how to enable plugins; how to\r\nchoose a bottom-of-screen or right-side alternative-spellings window;\r\nand how to choose your preferred dialect.  Your choice!\r\n","first_name":"Charles","6":"Charles","last_name":"Campbell","7":"Campbell","releases":[{"0":"195","vim_version":"6.0","1":"6.0","script_version":"64","2":"64","version_comment":"When filetype is mail, spell checking no longer takes place in initial lines\r\n","3":"When filetype is mail, spell checking no longer takes place in initial lines\r\n","package":"engspchk.tar.gz","4":"engspchk.tar.gz","src_id":"6351","5":"6351","creation_date":"1162207037","6":"1162207037"},{"0":"195","vim_version":"6.0","1":"6.0","script_version":"63","2":"63","version_comment":"Small things: includes CVIMSYN\/engspchk.match, uses cecutil, and CVIMSYN can now have spaces in its path\r\n","3":"Small things: includes CVIMSYN\/engspchk.match, uses cecutil, and CVIMSYN can now have spaces in its path\r\n","package":"engspchk.tar.gz","4":"engspchk.tar.gz","src_id":"5227","5":"5227","creation_date":"1140008338","6":"1140008338"},{"0":"195","vim_version":"6.0","1":"6.0","script_version":"62","2":"62","version_comment":"cpo workaround and improved visual-block only spellchecking\r\n","3":"cpo workaround and improved visual-block only spellchecking\r\n","package":"engspchk.tar.gz","4":"engspchk.tar.gz","src_id":"4422","5":"4422","creation_date":"1121148191","6":"1121148191"},{"0":"195","vim_version":"6.0","1":"6.0","script_version":"61","2":"61","version_comment":"A check is made for +clipboard before attempting to clear it\r\n","3":"A check is made for +clipboard before attempting to clear it\r\n","package":"engspchk.tar.gz","4":"engspchk.tar.gz","src_id":"4018","5":"4018","creation_date":"1110801290","6":"1110801290"},{"0":"195","vim_version":"6.0","1":"6.0","script_version":"60","2":"60","version_comment":"Engspchk now has improved operation with html.\r\nEngspchk checks if \"m\" is part of guioptions before doing (un)menu operations.\r\nContractions have now been moved to [lang]spchk.contraction; hopefully, some\r\nfolks will step up and make some contraction dictionaries for their native\r\nlanguages (I know that French, for example, needs such support!).\r\n","3":"Engspchk now has improved operation with html.\r\nEngspchk checks if \"m\" is part of guioptions before doing (un)menu operations.\r\nContractions have now been moved to [lang]spchk.contraction; hopefully, some\r\nfolks will step up and make some contraction dictionaries for their native\r\nlanguages (I know that French, for example, needs such support!).\r\n","package":"engspchk.tar.gz","4":"engspchk.tar.gz","src_id":"3851","5":"3851","creation_date":"1108110107","6":"1108110107"},{"0":"195","vim_version":"6.0","1":"6.0","script_version":"59","2":"59","version_comment":"Silenced all \"unmenu\" operations; included more tests to see if the gui is actually running before attempting to (un)install menus\r\n","3":"Silenced all \"unmenu\" operations; included more tests to see if the gui is actually running before attempting to (un)install menus\r\n","package":"engspchk.tar.gz","4":"engspchk.tar.gz","src_id":"3707","5":"3707","creation_date":"1103100517","6":"1103100517"},{"0":"195","vim_version":"6.0","1":"6.0","script_version":"58","2":"58","version_comment":"Engspchk now has language-specific starting commands: :Engspchk :Nlspchk :Spanspchk etc (which are based on the dictionaries you have available in $CVIMSYN)\r\nError messages now have a \"press <cr> to continue\" message so that one can see them.\r\nBugfixes: modeline priority, modeline highlighting, incomplete saving\/restoration of user maps\r\n","3":"Engspchk now has language-specific starting commands: :Engspchk :Nlspchk :Spanspchk etc (which are based on the dictionaries you have available in $CVIMSYN)\r\nError messages now have a \"press <cr> to continue\" message so that one can see them.\r\nBugfixes: modeline priority, modeline highlighting, incomplete saving\/restoration of user maps\r\n","package":"engspchk.tar.gz","4":"engspchk.tar.gz","src_id":"3615","5":"3615","creation_date":"1099994928","6":"1099994928"},{"0":"195","vim_version":"6.0","1":"6.0","script_version":"57","2":"57","version_comment":"New Feature: \\ev enables spell checking on just a visual-block (ie. ctrl-v, v, or V), and \\eV removes the block restriction\r\nNew utf8 German (with two dialects) and Russian dictionaries (tnx, Sergey Markelov!)\r\nbugfix: when mapleader wasn't explicitly set, a variable-not-found message resulted.  Fixed (tnx, Sergey Markelov!)\r\n","3":"New Feature: \\ev enables spell checking on just a visual-block (ie. ctrl-v, v, or V), and \\eV removes the block restriction\r\nNew utf8 German (with two dialects) and Russian dictionaries (tnx, Sergey Markelov!)\r\nbugfix: when mapleader wasn't explicitly set, a variable-not-found message resulted.  Fixed (tnx, Sergey Markelov!)\r\n","package":"engspchk.tar.bz2","4":"engspchk.tar.bz2","src_id":"3144","5":"3144","creation_date":"1087455162","6":"1087455162"},{"0":"195","vim_version":"6.0","1":"6.0","script_version":"56","2":"56","version_comment":"\\ej, \\eJ: enables saving words to and from *spchk.proj, engspchk's project support.\r\nbugfix: the loading of colorschemes usually wiped out RareWord and Dialect highlighting.  A CursorHold is now used to restore such highlighting.\r\nbugfix: usually languages (C Vim Mail etc) want to confine spellchecking to certain regions (ie. comments).  The latest engspchk does that, but the dictionaries needed to be changed.  engspchk.dict is changed for you, but new non-English dictionaries also need to be obtained.\r\n","3":"\\ej, \\eJ: enables saving words to and from *spchk.proj, engspchk's project support.\r\nbugfix: the loading of colorschemes usually wiped out RareWord and Dialect highlighting.  A CursorHold is now used to restore such highlighting.\r\nbugfix: usually languages (C Vim Mail etc) want to confine spellchecking to certain regions (ie. comments).  The latest engspchk does that, but the dictionaries needed to be changed.  engspchk.dict is changed for you, but new non-English dictionaries also need to be obtained.\r\n","package":"engspchk.tar.bz2","4":"engspchk.tar.bz2","src_id":"3127","5":"3127","creation_date":"1087203629","6":"1087203629"},{"0":"195","vim_version":"6.0","1":"6.0","script_version":"55","2":"55","version_comment":"Bugfixes: now uses finish instead of exit for certain errors, an exception has been made for mail for extensive spell checking, the \"-\" has been removed from iskeyword for French (please let me know if other languages need it removed, too!), an improved search method for dictionaries (often won't need CVIMSYN set anymore!).  Most important, a bug with wordlist generation caused some words to be dropped that should not have been.  Pls wipe out your old engspchk.wordlist and let engspchk v55 re-generate it!\r\n\r\n","3":"Bugfixes: now uses finish instead of exit for certain errors, an exception has been made for mail for extensive spell checking, the \"-\" has been removed from iskeyword for French (please let me know if other languages need it removed, too!), an improved search method for dictionaries (often won't need CVIMSYN set anymore!).  Most important, a bug with wordlist generation caused some words to be dropped that should not have been.  Pls wipe out your old engspchk.wordlist and let engspchk v55 re-generate it!\r\n\r\n","package":"engspchk-v55.tar.bz2","4":"engspchk-v55.tar.bz2","src_id":"3101","5":"3101","creation_date":"1086591721","6":"1086591721"},{"0":"195","vim_version":"6.0","1":"6.0","script_version":"50","2":"50","version_comment":"\\er and \\ed now cycle through three states:\r\n  \"RareWord\/Dialect : Error : no\" highlighting\r\n\r\nEngspchk now supports modelines (spchk: ...)\r\nwhere one may set options such as acronym,\r\naltright, autonext, cvimsyn, dialect, DrChipTopLvlMenu,\r\nmouse, nonhl, proj, punc, silent, and lang.\r\n\r\nEngspchk has dictionaries for: Dutch, Galician, German,\r\nHungarian, Italian, Russian, Spanish, Polish.  A Yiddish\r\nvariant has also been made available.  See\r\nhttp:\/\/www.erols.com\/astronaut\/index.html#vimlinks_scripts\r\nEngspchk supports selecting from multiple languages by mouse.\r\n","3":"\\er and \\ed now cycle through three states:\r\n  \"RareWord\/Dialect : Error : no\" highlighting\r\n\r\nEngspchk now supports modelines (spchk: ...)\r\nwhere one may set options such as acronym,\r\naltright, autonext, cvimsyn, dialect, DrChipTopLvlMenu,\r\nmouse, nonhl, proj, punc, silent, and lang.\r\n\r\nEngspchk has dictionaries for: Dutch, Galician, German,\r\nHungarian, Italian, Russian, Spanish, Polish.  A Yiddish\r\nvariant has also been made available.  See\r\nhttp:\/\/www.erols.com\/astronaut\/index.html#vimlinks_scripts\r\nEngspchk supports selecting from multiple languages by mouse.\r\n","package":"engspchk-v50.tar.bz2","4":"engspchk-v50.tar.bz2","src_id":"3013","5":"3013","creation_date":"1084283676","6":"1084283676"},{"0":"195","vim_version":"5.7","1":"5.7","script_version":"2.09","2":"2.09","version_comment":"Initial upload","3":"Initial upload","package":"engspchk.tar.gz","4":"engspchk.tar.gz","src_id":"522","5":"522","creation_date":"1012380442","6":"1012380442"}]},"194":{"script_id":"194","0":"194","script_name":"MRU","1":"MRU","script_type":"utility","2":"utility","summary":"Most recently used files in your file menu","3":"Most recently used files in your file menu","description":"It stores data in the file called $MRU.\r\nSee also vimscript#161\r\n\r\nHint: If you want a lightweight solution, you can use marks 0..9","4":"It stores data in the file called $MRU.\r\nSee also vimscript#161\r\n\r\nHint: If you want a lightweight solution, you can use marks 0..9","install_details":"When $MRU is not set, it will store data in you $HOME dir on unix, and in $VIM dir on windows. You can customize what to do with the file with defining OPEN_FUNC variable. The number of items can be changed by defining MRU_num. (default is 4).","5":"When $MRU is not set, it will store data in you $HOME dir on unix, and in $VIM dir on windows. You can customize what to do with the file with defining OPEN_FUNC variable. The number of items can be changed by defining MRU_num. (default is 4).","first_name":"Gergely","6":"Gergely","last_name":"Kontra","7":"Kontra","releases":[{"0":"194","vim_version":"6.0","1":"6.0","script_version":"0.32","2":"0.32","version_comment":"Fixed filename escaping (Thx to Fritz Mehner for the patch)\r\n","3":"Fixed filename escaping (Thx to Fritz Mehner for the patch)\r\n","package":"MRU.vim","4":"MRU.vim","src_id":"4144","5":"4144","creation_date":"1113115287","6":"1113115287"},{"0":"194","vim_version":"6.0","1":"6.0","script_version":"0.31","2":"0.31","version_comment":"Shutup clienserver stuff","3":"Shutup clienserver stuff","package":"MRU.vim","4":"MRU.vim","src_id":"673","5":"673","creation_date":"1015837534","6":"1015837534"},{"0":"194","vim_version":"6.0","1":"6.0","script_version":"0.3","2":"0.3","version_comment":"Most recently used files in your file menu\r\nNew features: * Limited path size (set PATHSIZELIMIT) * It closes the file even when 'hidden' is set * Synchronize if +clientserver is available","3":"Most recently used files in your file menu\r\nNew features: * Limited path size (set PATHSIZELIMIT) * It closes the file even when 'hidden' is set * Synchronize if +clientserver is available","package":"MRU.vim","4":"MRU.vim","src_id":"537","5":"537","creation_date":"1012806850","6":"1012806850"},{"0":"194","vim_version":"6.0","1":"6.0","script_version":"0.2","2":"0.2","version_comment":"Initial upload","3":"Initial upload","package":"MRU.vim","4":"MRU.vim","src_id":"520","5":"520","creation_date":"1012372591","6":"1012372591"}]},"193":{"script_id":"193","0":"193","script_name":"fortune.vim","1":"fortune.vim","script_type":"utility","2":"utility","summary":"Adding fortunes to your e-mails and fancy mail quoting","3":"Adding fortunes to your e-mails and fancy mail quoting","description":"This script provides a way to have vim put a fortune at the end of your mail messages. Most unix mail clients automatically handle the capability of having a program output as the signature file, but most windows mail clients, (at least PC-pine) do not (yet) provide a way to do this. This script provides a vim way to do the equivalent, if your mail client is capable of using external editors to compose mails. \r\n\r\nIn addition, this script also provides a way to change the style in which you quote the reply to your mails. by default, PC-pine quotes messages with the header:\r\n   On Sat 12 Jun 2001, John Doe wrote:\r\ntoo boring? \r\nThis script will change this to:\r\n   In our last exciting episode on Sat 12 Jun 2001, John Doe said:\r\nYou can ofcourse customize this to your special whackiness by changing the function ReplaceQuote().\r\n","4":"This script provides a way to have vim put a fortune at the end of your mail messages. Most unix mail clients automatically handle the capability of having a program output as the signature file, but most windows mail clients, (at least PC-pine) do not (yet) provide a way to do this. This script provides a vim way to do the equivalent, if your mail client is capable of using external editors to compose mails. \r\n\r\nIn addition, this script also provides a way to change the style in which you quote the reply to your mails. by default, PC-pine quotes messages with the header:\r\n   On Sat 12 Jun 2001, John Doe wrote:\r\ntoo boring? \r\nThis script will change this to:\r\n   In our last exciting episode on Sat 12 Jun 2001, John Doe said:\r\nYou can ofcourse customize this to your special whackiness by changing the function ReplaceQuote().\r\n","install_details":"1. download the file into your ~\/.vim\/plugin directory.\r\n2. create a signature file which looks like:\r\n    -----%<-----\r\n    -- \r\n    Srinath Avadhanula\r\n    _REPLACE_WITH_FORTUNE_\r\n    -----%<-----\r\n   (only the last line is necessary).\r\n3. in your mail client configuration, set this as your signature file. \r\n   (for pine, this is in the configuration screen).\r\n4. download and install the fortune program somewhere so that its in your\r\n   path and vim can source its output with a simple \". ! fortune\" command.\r\n   if you have cygwin installed, then running a google search for \"fortune\r\n   cygwin\" turns up many relevant hits. just download the relevant .tar.gz\r\n   file and untar it into cygwin's root directory.\r\n\r\nYou will need to use a mail client which is capable of using external\r\neditors to compose mails. (Outlook readily dissapears from my mind).\r\nSome mail clients on windows platforms having this feature:\r\n\r\n   PC-pine: http:\/\/www.washington.edu\/pine\/pc-pine\/\r\n  Mahogany: http:\/\/mahogany.sourceforge.net\/\r\n\r\n(I've been using PC-pine exclusively for many moons now).\r\n\r\nNOTE:\r\nIf the fancy mail quoting does not seem to be working for you check that\r\nyour mail client quotes replies either with the header:\r\n   On Sat 12 Jun 2001, John Doe wrote:\r\nor\r\n   On 12 Jun 2001, John Doe wrote:\r\nIf its some other format, you will need to tweak the function\r\nReplaceQuote() (please consider sending me a patch if you do this). \r\n","5":"1. download the file into your ~\/.vim\/plugin directory.\r\n2. create a signature file which looks like:\r\n    -----%<-----\r\n    -- \r\n    Srinath Avadhanula\r\n    _REPLACE_WITH_FORTUNE_\r\n    -----%<-----\r\n   (only the last line is necessary).\r\n3. in your mail client configuration, set this as your signature file. \r\n   (for pine, this is in the configuration screen).\r\n4. download and install the fortune program somewhere so that its in your\r\n   path and vim can source its output with a simple \". ! fortune\" command.\r\n   if you have cygwin installed, then running a google search for \"fortune\r\n   cygwin\" turns up many relevant hits. just download the relevant .tar.gz\r\n   file and untar it into cygwin's root directory.\r\n\r\nYou will need to use a mail client which is capable of using external\r\neditors to compose mails. (Outlook readily dissapears from my mind).\r\nSome mail clients on windows platforms having this feature:\r\n\r\n   PC-pine: http:\/\/www.washington.edu\/pine\/pc-pine\/\r\n  Mahogany: http:\/\/mahogany.sourceforge.net\/\r\n\r\n(I've been using PC-pine exclusively for many moons now).\r\n\r\nNOTE:\r\nIf the fancy mail quoting does not seem to be working for you check that\r\nyour mail client quotes replies either with the header:\r\n   On Sat 12 Jun 2001, John Doe wrote:\r\nor\r\n   On 12 Jun 2001, John Doe wrote:\r\nIf its some other format, you will need to tweak the function\r\nReplaceQuote() (please consider sending me a patch if you do this). \r\n","first_name":"Srinath","6":"Srinath","last_name":"Avadhanula","7":"Avadhanula","releases":[{"0":"193","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"fortune.vim","4":"fortune.vim","src_id":"519","5":"519","creation_date":"1012356401","6":"1012356401"}]},"192":{"script_id":"192","0":"192","script_name":"RExplorer","1":"RExplorer","script_type":"utility","2":"utility","summary":"Tree explorer with color","3":"Tree explorer with color","description":"This is an attempt to implement a tree explorer purely using vim 6.0 language. I have tried it on a unix and windows system and runs without any problem. Not sure about the behaviour in a different OS.\r\n\r\nIn the current version, the explorer window opens always on the left hand side.\r\n-Arun\r\n\r\nAscii snapshot:\r\n----------------------\r\n[+] \/\r\n[-] \/home\/user\r\n | [+] install\r\n | [+] mail\r\n | [+] misc\r\n | [+] src\r\n | [+] tmp\r\n |  |- README.txt\r\n |  |- hello.c  \r\n |","4":"This is an attempt to implement a tree explorer purely using vim 6.0 language. I have tried it on a unix and windows system and runs without any problem. Not sure about the behaviour in a different OS.\r\n\r\nIn the current version, the explorer window opens always on the left hand side.\r\n-Arun\r\n\r\nAscii snapshot:\r\n----------------------\r\n[+] \/\r\n[-] \/home\/user\r\n | [+] install\r\n | [+] mail\r\n | [+] misc\r\n | [+] src\r\n | [+] tmp\r\n |  |- README.txt\r\n |  |- hello.c  \r\n |","install_details":"1. unzip the files \r\n    in unix, gzip -dc RExplorer.tgz |tar vxf -\r\n    in win, use winzip or equivalent\r\n2. store the files RExplorer.vim and RECfg.txt in the same directory.\r\n3. source RExplorer.vim in a gvim session\r\n4. Be sure to read RECfg.txt for your customizations (for file associations and initial trees)","5":"1. unzip the files \r\n    in unix, gzip -dc RExplorer.tgz |tar vxf -\r\n    in win, use winzip or equivalent\r\n2. store the files RExplorer.vim and RECfg.txt in the same directory.\r\n3. source RExplorer.vim in a gvim session\r\n4. Be sure to read RECfg.txt for your customizations (for file associations and initial trees)","first_name":"Arun","6":"Arun","last_name":"E","7":"E","releases":[{"0":"192","vim_version":"6.0","1":"6.0","script_version":"1.05","2":"1.05","version_comment":"Enabled for vim7","3":"Enabled for vim7","package":"RExplorer.tgz","4":"RExplorer.tgz","src_id":"6426","5":"6426","creation_date":"1163682795","6":"1163682795"},{"0":"192","vim_version":"6.0","1":"6.0","script_version":"1.00","2":"1.00","version_comment":"Initial upload","3":"Initial upload","package":"RExplorer.tgz","4":"RExplorer.tgz","src_id":"512","5":"512","creation_date":"1012017791","6":"1012017791"}]},"191":{"script_id":"191","0":"191","script_name":"wcd.vim","1":"wcd.vim","script_type":"utility","2":"utility","summary":"Wherever Change Directory in vim","3":"Wherever Change Directory in vim","description":"wcd.vim plugin adds the :Wcd command, which allows to quickly\r\naccess any directory - same way as with wcd under the shell.\r\nwcd.vim requires wcd.exe to be installed on your system.\r\n\r\nFor more information on wcd, see:\r\n  http:\/\/www.xs4all.nl\/~waterlan\/\r\n","4":"wcd.vim plugin adds the :Wcd command, which allows to quickly\r\naccess any directory - same way as with wcd under the shell.\r\nwcd.vim requires wcd.exe to be installed on your system.\r\n\r\nFor more information on wcd, see:\r\n  http:\/\/www.xs4all.nl\/~waterlan\/\r\n","install_details":"Just drop the file into your plugin directory.  If Wcd does\r\nnot work right away to your satisfaction, try to adjust the\r\nSettings section.","5":"Just drop the file into your plugin directory.  If Wcd does\r\nnot work right away to your satisfaction, try to adjust the\r\nSettings section.","first_name":"Pavol","6":"Pavol","last_name":"Juhas","7":"Juhas","releases":[{"0":"191","vim_version":"6.0","1":"6.0","script_version":"1.13","2":"1.13","version_comment":"Small fixes, wcd should work better with unix gvim.  Settings can now be adjusted via global variables in .vimrc.","3":"Small fixes, wcd should work better with unix gvim.  Settings can now be adjusted via global variables in .vimrc.","package":"wcd.vim","4":"wcd.vim","src_id":"2550","5":"2550","creation_date":"1070644159","6":"1070644159"},{"0":"191","vim_version":"6.0","1":"6.0","script_version":"1.10","2":"1.10","version_comment":"New: OS sensitive defaults.  Now it should work under *nix\r\ngvim.  Added settings for easier setup.","3":"New: OS sensitive defaults.  Now it should work under *nix\r\ngvim.  Added settings for easier setup.","package":"wcd.vim","4":"wcd.vim","src_id":"688","5":"688","creation_date":"1016315156","6":"1016315156"},{"0":"191","vim_version":"6.0","1":"6.0","script_version":"1.02","2":"1.02","version_comment":"now executed through :silent !wcd.exe\r\n:Wcd -g mydir should work nicely","3":"now executed through :silent !wcd.exe\r\n:Wcd -g mydir should work nicely","package":"wcd.vim","4":"wcd.vim","src_id":"670","5":"670","creation_date":"1015694530","6":"1015694530"},{"0":"191","vim_version":"6.0","1":"6.0","script_version":"1","2":"1","version_comment":"Initial upload","3":"Initial upload","package":"wcd.vim","4":"wcd.vim","src_id":"509","5":"509","creation_date":"1011910933","6":"1011910933"}]},"190":{"script_id":"190","0":"190","script_name":"navajo.vim","1":"navajo.vim","script_type":"color scheme","2":"color scheme","summary":"Colorscheme with light background.","3":"Colorscheme with light background.","description":"The colorschemes I've seen on vim.sf.net seem to all have dark\r\nbackgrounds, but the dark backgrounds really bother my eyes.\r\nAlso, the default white background of gvim is too bright for me.\r\nPerhaps I'm alone, but a nice off-white background allows me to\r\nmerrily spend all day long staring at screen after screen after\r\nscreen of code, day after day, week after week, year after\r\nyear...  Editing code, reviewing code, documenting code,\r\ndebugging code, dreaming code in the nightmare that has become my\r\nlife... Oh, well -- at least this pleasant little colorscheme helps me\r\nget through the day.\r\nThe screen capture at http:\/\/vim.eralston.net\/?id=navajo should help you\r\ndecide whether this colorscheme is right for you.\r\n\r\nYour first impression may be that the background is kinda ugly,\r\nand I guess that's probably true.  But hey, I find it much more\r\nreadable, and it sure beats a poke in the eye with a sharp stick.\r\nIt works well in the gui, and to get a similar background\r\nin a color xterm, start your xterm with\r\n\"xterm -bg NavajoWhite3 -fg black\"\r\n\r\nIf you have any questions, feel free to ask; but to save you the\r\ntime and effort, the answer will invariably be 42.","4":"The colorschemes I've seen on vim.sf.net seem to all have dark\r\nbackgrounds, but the dark backgrounds really bother my eyes.\r\nAlso, the default white background of gvim is too bright for me.\r\nPerhaps I'm alone, but a nice off-white background allows me to\r\nmerrily spend all day long staring at screen after screen after\r\nscreen of code, day after day, week after week, year after\r\nyear...  Editing code, reviewing code, documenting code,\r\ndebugging code, dreaming code in the nightmare that has become my\r\nlife... Oh, well -- at least this pleasant little colorscheme helps me\r\nget through the day.\r\nThe screen capture at http:\/\/vim.eralston.net\/?id=navajo should help you\r\ndecide whether this colorscheme is right for you.\r\n\r\nYour first impression may be that the background is kinda ugly,\r\nand I guess that's probably true.  But hey, I find it much more\r\nreadable, and it sure beats a poke in the eye with a sharp stick.\r\nIt works well in the gui, and to get a similar background\r\nin a color xterm, start your xterm with\r\n\"xterm -bg NavajoWhite3 -fg black\"\r\n\r\nIf you have any questions, feel free to ask; but to save you the\r\ntime and effort, the answer will invariably be 42.","install_details":"Save as $VIMRUNTIME\/colors\/navajo.vim.\r\nThe colorscheme can then be loaded into vim with the command\r\n:colorscheme navajo","5":"Save as $VIMRUNTIME\/colors\/navajo.vim.\r\nThe colorscheme can then be loaded into vim with the command\r\n:colorscheme navajo","first_name":"Ed","6":"Ed","last_name":"Ralston","7":"Ralston","releases":[{"0":"190","vim_version":"6.0","1":"6.0","script_version":"0.2","2":"0.2","version_comment":"Slightly brighter background to accomodate w32.","3":"Slightly brighter background to accomodate w32.","package":"navajo.vim","4":"navajo.vim","src_id":"510","5":"510","creation_date":"1011930948","6":"1011930948"},{"0":"190","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"navajo.vim","4":"navajo.vim","src_id":"507","5":"507","creation_date":"1011857308","6":"1011857308"}]},"189":{"script_id":"189","0":"189","script_name":"renumber.vim","1":"renumber.vim","script_type":"utility","2":"utility","summary":"Egads! It's *another* renumber utility :-)","3":"Egads! It's *another* renumber utility :-)","description":"This would seem to be very similar in function to Inc (vimscript #156) - I put it here mainly for posterity.\r\n\r\nThe main differences are that it will honour preceeding zeros (without assuming octal ... plus, 0 in hex numbers are honoured: \"0x0001\"), and it will 'tidy up' misaligned numbers, to a degree (only right-aligns ATM). It uses the location of the first number to determine the alignment location.\r\n\r\nYou may now renumber starting at the \/bottom\/ of a block with the 'r' (reverse) option.  Note that you still have a default increment of +1, so to renumber a block ending at '10' you need to change the last number in the file to \"10\", make your selection and \"Renumber r s-1\".\r\n\r\nRenumber will also renumber days & months (e.g., Jan,Feb.Mar, etc.).  To renumber days, use the 'd' argument - for months, it's 'm'.\r\n\r\nUse by selecting the block of text (visually, linewise or blockwise, etc.), then issuing:\r\n\r\n:'<,'>Renumber\r\n\r\n.. or some other range indicator.\r\n\r\nRenumber will search the selection for a number (left -> right), and use that (hence use blockwise selection (<Ctrl-V>) to specify a column).  It will only edit numbers it finds in subsequent lines that have approximately the same position within each line.\r\n\r\nYou may pass in any arguments in any order:\r\n\r\na  - consider whole of line when searching for next number (even blockwise).\r\nd - renumber with day names\r\nm - renumber with month names\r\nr - reverse block order: start renumbering from bottom of block upwards\r\nsN  - [no space] use increment N (may be negative).\r\n\r\nEg.,\r\n\r\n:'<,'>Renumber a\r\n:'<,'>Renumber s4\r\n:'<,'>Renumber a s-2\r\n:'<,'>Renumber m s3\r\n:'<,'>Renumber r s-1\r\n\r\n\r\nTodo - add a left-justify option (probably '-').\r\n","4":"This would seem to be very similar in function to Inc (vimscript #156) - I put it here mainly for posterity.\r\n\r\nThe main differences are that it will honour preceeding zeros (without assuming octal ... plus, 0 in hex numbers are honoured: \"0x0001\"), and it will 'tidy up' misaligned numbers, to a degree (only right-aligns ATM). It uses the location of the first number to determine the alignment location.\r\n\r\nYou may now renumber starting at the \/bottom\/ of a block with the 'r' (reverse) option.  Note that you still have a default increment of +1, so to renumber a block ending at '10' you need to change the last number in the file to \"10\", make your selection and \"Renumber r s-1\".\r\n\r\nRenumber will also renumber days & months (e.g., Jan,Feb.Mar, etc.).  To renumber days, use the 'd' argument - for months, it's 'm'.\r\n\r\nUse by selecting the block of text (visually, linewise or blockwise, etc.), then issuing:\r\n\r\n:'<,'>Renumber\r\n\r\n.. or some other range indicator.\r\n\r\nRenumber will search the selection for a number (left -> right), and use that (hence use blockwise selection (<Ctrl-V>) to specify a column).  It will only edit numbers it finds in subsequent lines that have approximately the same position within each line.\r\n\r\nYou may pass in any arguments in any order:\r\n\r\na  - consider whole of line when searching for next number (even blockwise).\r\nd - renumber with day names\r\nm - renumber with month names\r\nr - reverse block order: start renumbering from bottom of block upwards\r\nsN  - [no space] use increment N (may be negative).\r\n\r\nEg.,\r\n\r\n:'<,'>Renumber a\r\n:'<,'>Renumber s4\r\n:'<,'>Renumber a s-2\r\n:'<,'>Renumber m s3\r\n:'<,'>Renumber r s-1\r\n\r\n\r\nTodo - add a left-justify option (probably '-').\r\n","install_details":"Put into a vim plugin directory somewhere.\r\n","5":"Put into a vim plugin directory somewhere.\r\n","first_name":"Neil","6":"Neil","last_name":"Bird","7":"Bird","releases":[{"0":"189","vim_version":"6.0","1":"6.0","script_version":"1.16","2":"1.16","version_comment":"A number of padding-related bug-fixes.","3":"A number of padding-related bug-fixes.","package":"renumber.vim","4":"renumber.vim","src_id":"4430","5":"4430","creation_date":"1121316756","6":"1121316756"},{"0":"189","vim_version":"6.0","1":"6.0","script_version":"1.13","2":"1.13","version_comment":"Fix bug when visual selection doesn't cover start of initial number (e.g., '456' of \"123456\".","3":"Fix bug when visual selection doesn't cover start of initial number (e.g., '456' of \"123456\".","package":"renumber.vim","4":"renumber.vim","src_id":"2952","5":"2952","creation_date":"1082355582","6":"1082355582"},{"0":"189","vim_version":"6.0","1":"6.0","script_version":"1.12","2":"1.12","version_comment":"Add support for renumbering hex values (0x1, 0x001, etc.).\r\nSome more 'nasty' stuff, as vim can't convert dec->hex, so, unfortunately, this will only work with a perl-capable vim (you won't get any errors without perl, it just won't cope with it, as it didn't before).\r\nYou get a free global 'Dec2Hex' function, though :-)\r\n","3":"Add support for renumbering hex values (0x1, 0x001, etc.).\r\nSome more 'nasty' stuff, as vim can't convert dec->hex, so, unfortunately, this will only work with a perl-capable vim (you won't get any errors without perl, it just won't cope with it, as it didn't before).\r\nYou get a free global 'Dec2Hex' function, though :-)\r\n","package":"renumber.vim","4":"renumber.vim","src_id":"2949","5":"2949","creation_date":"1082339685","6":"1082339685"},{"0":"189","vim_version":"6.0","1":"6.0","script_version":"1.11","2":"1.11","version_comment":"Fixed bug - now correctly skips lines with no matching nos. to renumber\r\nAlso hopefully copes with lines containing mixtures of tabs\/spaces, which cause havoc with visual-block column numbers.\r\nI'm doing some quite dodgy stuff to fix that, so please let me know if it misbehaves.","3":"Fixed bug - now correctly skips lines with no matching nos. to renumber\r\nAlso hopefully copes with lines containing mixtures of tabs\/spaces, which cause havoc with visual-block column numbers.\r\nI'm doing some quite dodgy stuff to fix that, so please let me know if it misbehaves.","package":"renumber.vim","4":"renumber.vim","src_id":"2539","5":"2539","creation_date":"1070501527","6":"1070501527"},{"0":"189","vim_version":"6.0","1":"6.0","script_version":"1.10","2":"1.10","version_comment":"- Wasn't matching preceeding '-'s as part of a number to replace.\r\n- Added r[everse] option, to start renumbering from the end of the block.","3":"- Wasn't matching preceeding '-'s as part of a number to replace.\r\n- Added r[everse] option, to start renumbering from the end of the block.","package":"renumber.vim","4":"renumber.vim","src_id":"2007","5":"2007","creation_date":"1053495877","6":"1053495877"},{"0":"189","vim_version":"6.0","1":"6.0","script_version":"1.9","2":"1.9","version_comment":"Bug fix arg. parsing for negative renumbering (John Sumsion)","3":"Bug fix arg. parsing for negative renumbering (John Sumsion)","package":"renumber.vim","4":"renumber.vim","src_id":"1880","5":"1880","creation_date":"1049072236","6":"1049072236"},{"0":"189","vim_version":"6.0","1":"6.0","script_version":"1.8","2":"1.8","version_comment":"Bugfix the month\/day stuff, plus a little speed optimisation.","3":"Bugfix the month\/day stuff, plus a little speed optimisation.","package":"renumber.vim","4":"renumber.vim","src_id":"1860","5":"1860","creation_date":"1048731790","6":"1048731790"},{"0":"189","vim_version":"6.0","1":"6.0","script_version":"1.7","2":"1.7","version_comment":"Add 'renumber' of days-of-week and months-of-year (English only)!","3":"Add 'renumber' of days-of-week and months-of-year (English only)!","package":"renumber.vim","4":"renumber.vim","src_id":"1855","5":"1855","creation_date":"1048650311","6":"1048650311"},{"0":"189","vim_version":"6.0","1":"6.0","script_version":"1.4","2":"1.4","version_comment":"Use col() instead of virtcol(), thus letting it work on lines containing <Tabs>!","3":"Use col() instead of virtcol(), thus letting it work on lines containing <Tabs>!","package":"renumber.vim","4":"renumber.vim","src_id":"675","5":"675","creation_date":"1015908470","6":"1015908470"},{"0":"189","vim_version":"6.0","1":"6.0","script_version":"1.3","2":"1.3","version_comment":"Initial upload","3":"Initial upload","package":"renumber.vim","4":"renumber.vim","src_id":"506","5":"506","creation_date":"1011769604","6":"1011769604"}]},"188":{"script_id":"188","0":"188","script_name":"ruby-menu.vim","1":"ruby-menu.vim","script_type":"utility","2":"utility","summary":"Adds a Ruby menu and some functions under that.","3":"Adds a Ruby menu and some functions under that.","description":"Currently does the following:\r\n\r\nRun the script out of the buffer\r\nRuns RI on a word under cursor\r\nRuns the script using the word under the cursor as an argument\r\nComment lines\r\nUncomment lines\r\n\r\nPlease e-mail with contributions or desires. I will add the appropriate \"who did what\" to the script\r\nif you contribute.","4":"Currently does the following:\r\n\r\nRun the script out of the buffer\r\nRuns RI on a word under cursor\r\nRuns the script using the word under the cursor as an argument\r\nComment lines\r\nUncomment lines\r\n\r\nPlease e-mail with contributions or desires. I will add the appropriate \"who did what\" to the script\r\nif you contribute.","install_details":"Read the file...it's in there","5":"Read the file...it's in there","first_name":"Robert","6":"Robert","last_name":"Hicks","7":"Hicks","releases":[{"0":"188","vim_version":"6.0","1":"6.0","script_version":"0.5","2":"0.5","version_comment":"Initial upload","3":"Initial upload","package":"ruby-menu.vim","4":"ruby-menu.vim","src_id":"502","5":"502","creation_date":"1011689482","6":"1011689482"}]},"187":{"script_id":"187","0":"187","script_name":"win manager Improved","1":"win manager Improved","script_type":"utility","2":"utility","summary":"Adds directory shortcuts to winmanager for faster traversal across file system","3":"Adds directory shortcuts to winmanager for faster traversal across file system","description":"Introduction:\r\n-----------------\r\n  This plugin will help user in quick traversal between various directories in a project, across the filesystems. This allows user to create shortcuts to directories. All shortcuts created by user are persistent across sessions and are available through the menu. Users who don't have a graphical interface can access menu through wild menu options.\r\n   All shortcuts created are stored in a text file which user can modify, if he has confidence. \r\n                  Support for adding current directory to shortcuts and direct access to shortcuts file has been given.(v 1.01)\r\n\r\n\r\nUsage:\r\n---------\r\n   Use Dir-shortcut menu to add shortcuts and traverse to them.\r\n   All commands of winmanager can be used as earlier. A summary of what might be needed by you follows:\r\n   :WManager\tto start Windows manager\r\n   :WMClose\tto close it\r\n   :WMtoggle\tto toggle between visible and hidden modes of winmanager.\r\n\r\n Testing:\r\n ----------\r\n \tI'm using these scripts from about a month now and feel they work good enough to be released to users.\r\n\r\n Thanks :\r\n ----------\r\n    Srinath for the wonderful script he has written.\r\n    To the vim-community, who encourage people even like me to contribute to make vim the best editor. \r\n    To my team mates for valuable support and suggestions I get from them.\r\n\r\n\r\nSuggestions and Bugs:\r\n---------------------------------\r\n    Report suggestion and bugs directly to me at anubhav47@hotmail.com. \r\n","4":"Introduction:\r\n-----------------\r\n  This plugin will help user in quick traversal between various directories in a project, across the filesystems. This allows user to create shortcuts to directories. All shortcuts created by user are persistent across sessions and are available through the menu. Users who don't have a graphical interface can access menu through wild menu options.\r\n   All shortcuts created are stored in a text file which user can modify, if he has confidence. \r\n                  Support for adding current directory to shortcuts and direct access to shortcuts file has been given.(v 1.01)\r\n\r\n\r\nUsage:\r\n---------\r\n   Use Dir-shortcut menu to add shortcuts and traverse to them.\r\n   All commands of winmanager can be used as earlier. A summary of what might be needed by you follows:\r\n   :WManager\tto start Windows manager\r\n   :WMClose\tto close it\r\n   :WMtoggle\tto toggle between visible and hidden modes of winmanager.\r\n\r\n Testing:\r\n ----------\r\n \tI'm using these scripts from about a month now and feel they work good enough to be released to users.\r\n\r\n Thanks :\r\n ----------\r\n    Srinath for the wonderful script he has written.\r\n    To the vim-community, who encourage people even like me to contribute to make vim the best editor. \r\n    To my team mates for valuable support and suggestions I get from them.\r\n\r\n\r\nSuggestions and Bugs:\r\n---------------------------------\r\n    Report suggestion and bugs directly to me at anubhav47@hotmail.com. \r\n","install_details":"For Version 1.01 onwards\r\n-------------------------------------\r\n    Place file addToWinManager.vim inot the  plugin directory. (Upzipping it in $VIMRUNTIME will do the same thing).\r\n\r\n\r\n\r\nFor Version 1.0\r\n----------------------\r\nPlace file        addToWinManager.vim in your home directory\r\n\t      winmanager.vim in your plugin directory(done automatically if you unzip the files in your $VIMRUNTIME dir).\r\n\t      winmanager.doc in your doc directory (done automatically if you unzip the files in your $VIMRUNTIME directory).\r\n\r\nAdd following line to your .vimrc (or whatever is your startup file)\r\n\r\nso $HOME\/addToWinManager.vim\r\n\r\nand you are through with it. Just start your gvim\/vim\r\n","5":"For Version 1.01 onwards\r\n-------------------------------------\r\n    Place file addToWinManager.vim inot the  plugin directory. (Upzipping it in $VIMRUNTIME will do the same thing).\r\n\r\n\r\n\r\nFor Version 1.0\r\n----------------------\r\nPlace file        addToWinManager.vim in your home directory\r\n\t      winmanager.vim in your plugin directory(done automatically if you unzip the files in your $VIMRUNTIME dir).\r\n\t      winmanager.doc in your doc directory (done automatically if you unzip the files in your $VIMRUNTIME directory).\r\n\r\nAdd following line to your .vimrc (or whatever is your startup file)\r\n\r\nso $HOME\/addToWinManager.vim\r\n\r\nand you are through with it. Just start your gvim\/vim\r\n","first_name":"Anubhav","6":"Anubhav","last_name":"Srivastava","7":"Srivastava","releases":[{"0":"187","vim_version":"6.0","1":"6.0","script_version":"1.01","2":"1.01","version_comment":"New in Version:\r\n          1). Upgraded to work with winmanager 2.0  \r\n          2). Easier installation: just upzip in your $VIMRUNTIME, or place file addToWinManager in your plugin directory.\r\n          3). Removed bug for windows platform (was not escaping \/ earlier) .\r\n          4). A new command to add current directory to Dir-shortcut menu is added.\r\n          5). A direct access to .menu1.vim is provided through the Dir-shortcut menu.\r\n\r\nThanks yet again for the suggestions. These are  what makes VIM community great. \r\n\r\nAnubhav","3":"New in Version:\r\n          1). Upgraded to work with winmanager 2.0  \r\n          2). Easier installation: just upzip in your $VIMRUNTIME, or place file addToWinManager in your plugin directory.\r\n          3). Removed bug for windows platform (was not escaping \/ earlier) .\r\n          4). A new command to add current directory to Dir-shortcut menu is added.\r\n          5). A direct access to .menu1.vim is provided through the Dir-shortcut menu.\r\n\r\nThanks yet again for the suggestions. These are  what makes VIM community great. \r\n\r\nAnubhav","package":"winmanager Improved.zip","4":"winmanager Improved.zip","src_id":"498","5":"498","creation_date":"1011409283","6":"1011409283"},{"0":"187","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"winmanager Improved.zip","4":"winmanager Improved.zip","src_id":"492","5":"492","creation_date":"1011343695","6":"1011343695"}]},"186":{"script_id":"186","0":"186","script_name":"glib.vim","1":"glib.vim","script_type":"syntax","2":"syntax","summary":"syntax highlighting for additional glib types","3":"syntax highlighting for additional glib types","description":"This syntax file, written by my friend Jason Thomas, adds to your existing C syntax file many of the extra types and so forth given to you by the excellent glib library from http:\/\/www.gtk.org\/\r\n\r\nIt is believed to be complete (at least for 1.2.x), though feel free to submit patches if you find something missing.\r\n","4":"This syntax file, written by my friend Jason Thomas, adds to your existing C syntax file many of the extra types and so forth given to you by the excellent glib library from http:\/\/www.gtk.org\/\r\n\r\nIt is believed to be complete (at least for 1.2.x), though feel free to submit patches if you find something missing.\r\n","install_details":"*** General Vim ***\r\n  - Add to your ~\/.vim\/syntax directory and\r\n    :set syntax=glib\r\n    when you want it.\r\n\r\n*** Utilising Vim6 ***\r\n - add to your ~\/.vim\/after\/syntax\/ directory and rename it \"c.vim\".  \r\n - edit the script, comment out all the lines before the \r\n\r\n   \" Now setup the glib specific stuff\r\n\r\n    comment (the ones to do with clearing out syntax items in vim5 and 6), and\r\n    also comment out the second-last line of the file (the let b:current_syntax .. line).\r\n    All that should be left is the \"syn\" related commands in-between.\r\n - Load your favourite C or C++ file to get the glib highlighting automagically!\r\n","5":"*** General Vim ***\r\n  - Add to your ~\/.vim\/syntax directory and\r\n    :set syntax=glib\r\n    when you want it.\r\n\r\n*** Utilising Vim6 ***\r\n - add to your ~\/.vim\/after\/syntax\/ directory and rename it \"c.vim\".  \r\n - edit the script, comment out all the lines before the \r\n\r\n   \" Now setup the glib specific stuff\r\n\r\n    comment (the ones to do with clearing out syntax items in vim5 and 6), and\r\n    also comment out the second-last line of the file (the let b:current_syntax .. line).\r\n    All that should be left is the \"syn\" related commands in-between.\r\n - Load your favourite C or C++ file to get the glib highlighting automagically!\r\n","first_name":"Matthew","6":"Matthew","last_name":"Hawkins","7":"Hawkins","releases":[{"0":"186","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"glib.vim","4":"glib.vim","src_id":"485","5":"485","creation_date":"1011233576","6":"1011233576"}]},"185":{"script_id":"185","0":"185","script_name":"bk-menu.vim","1":"bk-menu.vim","script_type":"utility","2":"utility","summary":"Integration of Bitkeeper with Vim","3":"Integration of Bitkeeper with Vim","description":"This is a hack of the sccs-menu.vim plugin to work with Bitkeeper instead.  At this stage things are likely to be broken but feedback (and patches?) are most welcome.\r\n\r\nThanks to Pradeep Unde for the SCCS plugin.\r\n","4":"This is a hack of the sccs-menu.vim plugin to work with Bitkeeper instead.  At this stage things are likely to be broken but feedback (and patches?) are most welcome.\r\n\r\nThanks to Pradeep Unde for the SCCS plugin.\r\n","install_details":"drop it into your plugins directory.\r\n","5":"drop it into your plugins directory.\r\n","first_name":"Matthew","6":"Matthew","last_name":"Hawkins","7":"Hawkins","releases":[{"0":"185","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"bk-menu.vim","4":"bk-menu.vim","src_id":"482","5":"482","creation_date":"1011212944","6":"1011212944"}]},"184":{"script_id":"184","0":"184","script_name":"vtreeexplorer","1":"vtreeexplorer","script_type":"utility","2":"utility","summary":"tree based file explorer - the original","3":"tree based file explorer - the original","description":"Creates a tree based file explorer within vim.\r\n\r\nThis is like the directory explorer plugin that ships with vim, but instead of presenting just one directory at a time, this plugin present portions of the filesystem hierarch in a tree view.  This type of view should be familiar from modern graphical file managers.  This explorer persents navigation, exploration, and opening of files only -  unlike the standard directory explorer that allow you to delete and rename files.   This a handy tool for becoming familiar with source trees.\r\n\r\n\r\nFeature summary:\r\n- directories are foldable (fold markers are highlighted invisible)\r\n- directories and links are syntax highlighted\r\n- open a file in a new window\r\n- mappings for naviagation (keyboard and mouse) - goto parent, change dir, go up, cd to home, refesh, etc\r\n- lazy loading of directory structure - one directory at a time.  Recursive expansion also available.\r\n\r\nCaveats:\r\nMay not work well for obscure systems - unix and windows work well.  Please send bugs or patches.\r\n\r\nThis is a reimplementation of the treeexplorerer (see http:\/\/vim.sourceforge.net\/scripts\/script.php?script_id=183 ) that doesn't require perl or the tree command - it's pure vim.\r\n\r\nScott","4":"Creates a tree based file explorer within vim.\r\n\r\nThis is like the directory explorer plugin that ships with vim, but instead of presenting just one directory at a time, this plugin present portions of the filesystem hierarch in a tree view.  This type of view should be familiar from modern graphical file managers.  This explorer persents navigation, exploration, and opening of files only -  unlike the standard directory explorer that allow you to delete and rename files.   This a handy tool for becoming familiar with source trees.\r\n\r\n\r\nFeature summary:\r\n- directories are foldable (fold markers are highlighted invisible)\r\n- directories and links are syntax highlighted\r\n- open a file in a new window\r\n- mappings for naviagation (keyboard and mouse) - goto parent, change dir, go up, cd to home, refesh, etc\r\n- lazy loading of directory structure - one directory at a time.  Recursive expansion also available.\r\n\r\nCaveats:\r\nMay not work well for obscure systems - unix and windows work well.  Please send bugs or patches.\r\n\r\nThis is a reimplementation of the treeexplorerer (see http:\/\/vim.sourceforge.net\/scripts\/script.php?script_id=183 ) that doesn't require perl or the tree command - it's pure vim.\r\n\r\nScott","install_details":"1. un-gzip, untar in your $HOME\/.vim, $VIMRUNTIME, or equivalent directories.  Or un-gzip and un-tar and source the vtreeexplorer.vim file to test.\r\n\r\n2. you can add the help to your help index with :helptags ~\/.vim\/doc (if you put the files there).\r\n\r\n :VTreeExplore\r\n   or\r\n :VSTreeExplore\r\n\r\nquick help is at top of window\r\n\r\nSee vtreeexplorer.txt of :help vtreeexplorer (if you did :helptags above) for more detailed help.\r\n","5":"1. un-gzip, untar in your $HOME\/.vim, $VIMRUNTIME, or equivalent directories.  Or un-gzip and un-tar and source the vtreeexplorer.vim file to test.\r\n\r\n2. you can add the help to your help index with :helptags ~\/.vim\/doc (if you put the files there).\r\n\r\n :VTreeExplore\r\n   or\r\n :VSTreeExplore\r\n\r\nquick help is at top of window\r\n\r\nSee vtreeexplorer.txt of :help vtreeexplorer (if you did :helptags above) for more detailed help.\r\n","first_name":"scott","6":"scott","last_name":"urban","7":"urban","releases":[{"0":"184","vim_version":"7.0","1":"7.0","script_version":"1.28","2":"1.28","version_comment":"Added 'O' command which replaces explorer window with editing of file when activated on file in tree - idea from Brian Doyle.","3":"Added 'O' command which replaces explorer window with editing of file when activated on file in tree - idea from Brian Doyle.","package":"vtreeexplorer-1.28.tar.gz","4":"vtreeexplorer-1.28.tar.gz","src_id":"8097","5":"8097","creation_date":"1198879584","6":"1198879584"},{"0":"184","vim_version":"7.0","1":"7.0","script_version":"1.27","2":"1.27","version_comment":"Add feature where files and directories matching global variable g:treeExplHidePattern will be not shown.  Can be updated at anytime.  Hiding toggled with the existing mechanism. Thanks to Vaclav Kulakovsky for the idea and patch.","3":"Add feature where files and directories matching global variable g:treeExplHidePattern will be not shown.  Can be updated at anytime.  Hiding toggled with the existing mechanism. Thanks to Vaclav Kulakovsky for the idea and patch.","package":"vtreeexplorer-1.27.tar.gz","4":"vtreeexplorer-1.27.tar.gz","src_id":"7928","5":"7928","creation_date":"1194732901","6":"1194732901"},{"0":"184","vim_version":"7.0","1":"7.0","script_version":"1.26","2":"1.26","version_comment":"Fix for bug that occurs when opening a file after splitting the vtree window. Thanks to genelisp\/isaac","3":"Fix for bug that occurs when opening a file after splitting the vtree window. Thanks to genelisp\/isaac","package":"vtreeexplorer-1.26.tar.gz","4":"vtreeexplorer-1.26.tar.gz","src_id":"7927","5":"7927","creation_date":"1194731404","6":"1194731404"},{"0":"184","vim_version":"7.0","1":"7.0","script_version":"1.25","2":"1.25","version_comment":"Added support for tabs with the 'e' shortcut - thanks to Krzysztof Kościuszkiewicz","3":"Added support for tabs with the 'e' shortcut - thanks to Krzysztof Kościuszkiewicz","package":"vtreeexplorer-1.25.tar.gz","4":"vtreeexplorer-1.25.tar.gz","src_id":"7926","5":"7926","creation_date":"1194730111","6":"1194730111"},{"0":"184","vim_version":"7.0","1":"7.0","script_version":"1.24","2":"1.24","version_comment":"Don't clobber yank register, fixes for vim 7, misc fixes.  Thanks to A. Kruize, D. Mayle, M. Grentel","3":"Don't clobber yank register, fixes for vim 7, misc fixes.  Thanks to A. Kruize, D. Mayle, M. Grentel","package":"vtreeexplorer-1.24.tar.gz","4":"vtreeexplorer-1.24.tar.gz","src_id":"6086","5":"6086","creation_date":"1156144118","6":"1156144118"},{"0":"184","vim_version":"6.0","1":"6.0","script_version":"1.23","2":"1.23","version_comment":"Fixes for functionality on windows.","3":"Fixes for functionality on windows.","package":"vtreeexplorer-1.23.tar.gz","4":"vtreeexplorer-1.23.tar.gz","src_id":"4709","5":"4709","creation_date":"1130707041","6":"1130707041"},{"0":"184","vim_version":"6.0","1":"6.0","script_version":"1.22","2":"1.22","version_comment":"- bug fix for vim6 - thanks to Steve Hall\r\n- avoid register clobbering - thanks to Bindu Wavell","3":"- bug fix for vim6 - thanks to Steve Hall\r\n- avoid register clobbering - thanks to Bindu Wavell","package":"vtreeexplorer-1.22.tar.gz","4":"vtreeexplorer-1.22.tar.gz","src_id":"4705","5":"4705","creation_date":"1130483230","6":"1130483230"},{"0":"184","vim_version":"6.0","1":"6.0","script_version":"1.21","2":"1.21","version_comment":"- more compact default layout (width of tree layout is customizable)\r\n- updated contact info","3":"- more compact default layout (width of tree layout is customizable)\r\n- updated contact info","package":"vtreeexplorer-1.21.tar.gz","4":"vtreeexplorer-1.21.tar.gz","src_id":"4704","5":"4704","creation_date":"1130454380","6":"1130454380"},{"0":"184","vim_version":"6.0","1":"6.0","script_version":"1.20","2":"1.20","version_comment":"Auto-loading for TreeExplorer buffer type - useful if you save and restore a session with the explorer in it. Updated email address.","3":"Auto-loading for TreeExplorer buffer type - useful if you save and restore a session with the explorer in it. Updated email address.","package":"vtreeexplorer-1.20.tar.gz","4":"vtreeexplorer-1.20.tar.gz","src_id":"3740","5":"3740","creation_date":"1104402320","6":"1104402320"},{"0":"184","vim_version":"6.0","1":"6.0","script_version":"1.19","2":"1.19","version_comment":"Fix for filenames that contain '#' - thanks to Klaus Fabritius.","3":"Fix for filenames that contain '#' - thanks to Klaus Fabritius.","package":"vtreeexplorer-1.19.tar.gz","4":"vtreeexplorer-1.19.tar.gz","src_id":"1672","5":"1672","creation_date":"1043571809","6":"1043571809"},{"0":"184","vim_version":"6.0","1":"6.0","script_version":"1.16","2":"1.16","version_comment":"Minor fix when opening modified buffer that is  already open in more than 1 window - Yegappan Lakshman","3":"Minor fix when opening modified buffer that is  already open in more than 1 window - Yegappan Lakshman","package":"vtreeexplorer.tar.gz","4":"vtreeexplorer.tar.gz","src_id":"1223","5":"1223","creation_date":"1032446034","6":"1032446034"},{"0":"184","vim_version":"6.0","1":"6.0","script_version":"1.15","2":"1.15","version_comment":"Syntax bug - must have hit  'J' instead of 'j' at some point.","3":"Syntax bug - must have hit  'J' instead of 'j' at some point.","package":"vtreeexplorer.tar.gz","4":"vtreeexplorer.tar.gz","src_id":"1043","5":"1043","creation_date":"1027458151","6":"1027458151"},{"0":"184","vim_version":"6.0","1":"6.0","script_version":"1.14","2":"1.14","version_comment":"Add mapping for mouse button on tree - like 'open' (thanks to Douglas Potts).","3":"Add mapping for mouse button on tree - like 'open' (thanks to Douglas Potts).","package":"vtreeexplorer.tar.gz","4":"vtreeexplorer.tar.gz","src_id":"1041","5":"1041","creation_date":"1027378547","6":"1027378547"},{"0":"184","vim_version":"6.0","1":"6.0","script_version":"1.13","2":"1.13","version_comment":"Bugfix for VSTreeExplore - thanks to Benoit Cerrina\r\nAdded help documenation.","3":"Bugfix for VSTreeExplore - thanks to Benoit Cerrina\r\nAdded help documenation.","package":"vtreeexplorer.tar.gz","4":"vtreeexplorer.tar.gz","src_id":"604","5":"604","creation_date":"1013954846","6":"1013954846"},{"0":"184","vim_version":"6.0","1":"6.0","script_version":"1.10","2":"1.10","version_comment":"Added directory sorting and D mapping to toggle between 3 modes. Highlighting change for links. Support for opening more than one tree explorer at once.  Code cleanups and factoring.","3":"Added directory sorting and D mapping to toggle between 3 modes. Highlighting change for links. Support for opening more than one tree explorer at once.  Code cleanups and factoring.","package":"vtreeexplorer.vim","4":"vtreeexplorer.vim","src_id":"493","5":"493","creation_date":"1011346728","6":"1011346728"},{"0":"184","vim_version":"6.0","1":"6.0","script_version":"1.9","2":"1.9","version_comment":"Added ~ to chars escaped in file names. Suppressed message output. Handle when top dir is of the form C:\\ for dos\/win systems.","3":"Added ~ to chars escaped in file names. Suppressed message output. Handle when top dir is of the form C:\\ for dos\/win systems.","package":"vtreeexplorer.vim","4":"vtreeexplorer.vim","src_id":"489","5":"489","creation_date":"1011280240","6":"1011280240"},{"0":"184","vim_version":"6.0","1":"6.0","script_version":"1.8","2":"1.8","version_comment":"Changed recursive expand from E to X mapping. Added E mapping to open regular file explorer on cursor dir.  Added :CD command to switch to direcotry (useful maybe to CD: D: on windows?) - still some escaping bugs on that one.  Fixed bug for dirs\/files that start with tree parts. Better escaping of file\/dir names. Other minor fixes and clean ups.","3":"Changed recursive expand from E to X mapping. Added E mapping to open regular file explorer on cursor dir.  Added :CD command to switch to direcotry (useful maybe to CD: D: on windows?) - still some escaping bugs on that one.  Fixed bug for dirs\/files that start with tree parts. Better escaping of file\/dir names. Other minor fixes and clean ups.","package":"vtreeexplorer.vim","4":"vtreeexplorer.vim","src_id":"488","5":"488","creation_date":"1011273886","6":"1011273886"},{"0":"184","vim_version":"6.0","1":"6.0","script_version":"1.7","2":"1.7","version_comment":"Added command to refresh cursor dir.  Added command to recursively expand subdirs of cursor dir (caution: this could take a long time for big subdir trees).  Changed the hidded files toggle to refresh current dir after. Fixes for windows. Other minor fixes. Using CVS version numbers now, sorry for the jump.","3":"Added command to refresh cursor dir.  Added command to recursively expand subdirs of cursor dir (caution: this could take a long time for big subdir trees).  Changed the hidded files toggle to refresh current dir after. Fixes for windows. Other minor fixes. Using CVS version numbers now, sorry for the jump.","package":"vtreeexplorer.vim","4":"vtreeexplorer.vim","src_id":"486","5":"486","creation_date":"1011266124","6":"1011266124"},{"0":"184","vim_version":"6.0","1":"6.0","script_version":"1.01","2":"1.01","version_comment":"Fixed problem with esaping dir names with spaces - still some issues with using it in windows.","3":"Fixed problem with esaping dir names with spaces - still some issues with using it in windows.","package":"vtreeexplorer.vim","4":"vtreeexplorer.vim","src_id":"481","5":"481","creation_date":"1011201161","6":"1011201161"},{"0":"184","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"vtreeexplorer.vim","4":"vtreeexplorer.vim","src_id":"480","5":"480","creation_date":"1011189396","6":"1011189396"}]},"183":{"script_id":"183","0":"183","script_name":"treeexplorer","1":"treeexplorer","script_type":"utility","2":"utility","summary":"uses perl and tree to create a tree file explorer","3":"uses perl and tree to create a tree file explorer","description":"IMPORTANT: See UPDATES below - this script is now an orphan\r\n\r\nUses perl and the unix tree command (available on linux, or find sources on freshmeat.net) to create a tree based explorer for your directory structure.   Features:\r\n\r\n- directories are foldable\r\n- different filetypes are highlighed\r\n- open a file in a new window\r\n- mappings for naviagation,\r\n- lazy loading of directory structure\r\n\r\nCaveats:\r\nProbably doesn't work right for non-unix systems, I'm working on this, but help is welcome\r\n\r\nUPDATES: \r\n- I have reimplemented this script using only vim.  The new implementation can be found at http:\/\/vim.sourceforge.net\/scripts\/script.php?script_id=184 - vimtreeexplorer.vim.  That approach is faster as well as requiring no external programs.  I have now abandoned the original implementation because the new implementation can do recursive expansion if you want it to.\r\n\r\n\r\n\r\nScott","4":"IMPORTANT: See UPDATES below - this script is now an orphan\r\n\r\nUses perl and the unix tree command (available on linux, or find sources on freshmeat.net) to create a tree based explorer for your directory structure.   Features:\r\n\r\n- directories are foldable\r\n- different filetypes are highlighed\r\n- open a file in a new window\r\n- mappings for naviagation,\r\n- lazy loading of directory structure\r\n\r\nCaveats:\r\nProbably doesn't work right for non-unix systems, I'm working on this, but help is welcome\r\n\r\nUPDATES: \r\n- I have reimplemented this script using only vim.  The new implementation can be found at http:\/\/vim.sourceforge.net\/scripts\/script.php?script_id=184 - vimtreeexplorer.vim.  That approach is faster as well as requiring no external programs.  I have now abandoned the original implementation because the new implementation can do recursive expansion if you want it to.\r\n\r\n\r\n\r\nScott","install_details":"Instructions:\r\n- make sure you have perl\r\n- make sure you have 'tree' command\r\n- download, gunzip, untar package\r\n- make vimtreeexpl.pl executable, put in your path (e.g. $HOME\/bin)\r\n- put treeexpl.vim in your plugin dir (e.g. $HOME\/.vim\/plugin)\r\n\r\n:TreeExplore\r\n\r\nor\r\n\r\n:STreeExplore\r\n\r\nhelp at top of screen","5":"Instructions:\r\n- make sure you have perl\r\n- make sure you have 'tree' command\r\n- download, gunzip, untar package\r\n- make vimtreeexpl.pl executable, put in your path (e.g. $HOME\/bin)\r\n- put treeexpl.vim in your plugin dir (e.g. $HOME\/.vim\/plugin)\r\n\r\n:TreeExplore\r\n\r\nor\r\n\r\n:STreeExplore\r\n\r\nhelp at top of screen","first_name":"scott","6":"scott","last_name":"urban","7":"urban","releases":[{"0":"183","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"treeexplorer.tar.gz","4":"treeexplorer.tar.gz","src_id":"478","5":"478","creation_date":"1011110977","6":"1011110977"}]},"182":{"script_id":"182","0":"182","script_name":"SuperTab","1":"SuperTab","script_type":"utility","2":"utility","summary":"Do all your insert-mode completion with Tab!","3":"Do all your insert-mode completion with Tab!","description":"The script has MOVED (since Eric Van Dewoestine is the new maintainer).\r\n\r\nSo go to vimscript#1643 for the new version.\r\n\r\nThank Eric to taking over the maintainership!","4":"The script has MOVED (since Eric Van Dewoestine is the new maintainer).\r\n\r\nSo go to vimscript#1643 for the new version.\r\n\r\nThank Eric to taking over the maintainership!","install_details":"","5":"","first_name":"Gergely","6":"Gergely","last_name":"Kontra","7":"Kontra","releases":[{"0":"182","vim_version":"6.0","1":"6.0","script_version":"0.41","2":"0.41","version_comment":"Fixed couple bugs introduced in last version\r\nEric Van Dewoestine","3":"Fixed couple bugs introduced in last version\r\nEric Van Dewoestine","package":"supertab.vim","4":"supertab.vim","src_id":"5938","5":"5938","creation_date":"1152579677","6":"1152579677"},{"0":"182","vim_version":"7.0","1":"7.0","script_version":"0.4","2":"0.4","version_comment":"Upgrade by Eric Van Dewoestine","3":"Upgrade by Eric Van Dewoestine","package":"supertab.vim","4":"supertab.vim","src_id":"5699","5":"5699","creation_date":"1147672132","6":"1147672132"},{"0":"182","vim_version":"6.0","1":"6.0","script_version":"0.32","2":"0.32","version_comment":"Bugfix: tab insertion\/completion decidion correction. SuperTab now inserts <Tab>, if the preceding character is whitespace\r\nThx to  Lorenz Wegener","3":"Bugfix: tab insertion\/completion decidion correction. SuperTab now inserts <Tab>, if the preceding character is whitespace\r\nThx to  Lorenz Wegener","package":"SuperTab.vim","4":"SuperTab.vim","src_id":"2481","5":"2481","creation_date":"1068426121","6":"1068426121"},{"0":"182","vim_version":"6.0","1":"6.0","script_version":"0.31","2":"0.31","version_comment":"Now SuperTab allow cycling back with <S-Tab>\r\nLimitations: You must cycle forward before and it works in the GUI version only","3":"Now SuperTab allow cycling back with <S-Tab>\r\nLimitations: You must cycle forward before and it works in the GUI version only","package":"SuperTab.vim","4":"SuperTab.vim","src_id":"1225","5":"1225","creation_date":"1032505052","6":"1032505052"},{"0":"182","vim_version":"6.0","1":"6.0","script_version":"0.3","2":"0.3","version_comment":"Back to the roots.\r\n* Bugfix\r\n* Autocompletion removed","3":"Back to the roots.\r\n* Bugfix\r\n* Autocompletion removed","package":"SuperTab.vim","4":"SuperTab.vim","src_id":"695","5":"695","creation_date":"1016524398","6":"1016524398"},{"0":"182","vim_version":"6.0","1":"6.0","script_version":"0.2afix","2":"0.2afix","version_comment":"Fixed bug with <C-X>p and <C-x>n.\r\n<C-E> and <C-Y> modes are not remembered now.","3":"Fixed bug with <C-X>p and <C-x>n.\r\n<C-E> and <C-Y> modes are not remembered now.","package":"SuperTab.vim","4":"SuperTab.vim","src_id":"612","5":"612","creation_date":"1014097711","6":"1014097711"},{"0":"182","vim_version":"6.0","1":"6.0","script_version":"0.2alpha","2":"0.2alpha","version_comment":"Experimental autocompletion mode.\r\nIt can be turned on and off with \\ac.\r\nIn this mode <CR> accept autocompletion, <Del> clears the current autocomplete <Esc> goes back to normal mode without applying the offered autocompletion, and <Tab> allows another completion (from this point, you cannot undo the completion you made)\r\nThe script uses Charles E. Campbell, Jr.'s SaveMap function.\r\nThe script is bigger and bigger. Help me to simplify it.","3":"Experimental autocompletion mode.\r\nIt can be turned on and off with \\ac.\r\nIn this mode <CR> accept autocompletion, <Del> clears the current autocomplete <Esc> goes back to normal mode without applying the offered autocompletion, and <Tab> allows another completion (from this point, you cannot undo the completion you made)\r\nThe script uses Charles E. Campbell, Jr.'s SaveMap function.\r\nThe script is bigger and bigger. Help me to simplify it.","package":"SuperTab.vim","4":"SuperTab.vim","src_id":"491","5":"491","creation_date":"1011339378","6":"1011339378"},{"0":"182","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"SuperTab.vim","4":"SuperTab.vim","src_id":"473","5":"473","creation_date":"1011066736","6":"1011066736"}]},"181":{"script_id":"181","0":"181","script_name":"prt_mgr.zip","1":"prt_mgr.zip","script_type":"utility","2":"utility","summary":"VIM Print Manager providing N-up and manual duplex printing.","3":"VIM Print Manager providing N-up and manual duplex printing.","description":"This plugin extends the flexibility of printing from VIM using PSUtils - http:\/\/www.tardis.ed.ac.uk\/~ajcd\/psutils\/. The plugin supports:\r\n\r\no N-up printing,\r\no Manual duplex printing (feeding printed pages back into the printer to print the reverse sides)\r\no Reverse page order printing.\r\no Print to file.\r\n\r\nThere are also VIM functions to allow the Print Manager to be called from other scripts, as well as being hooked to the :hardcopy command using the printexpr option.\r\n\r\nSee included help file for details on setting up and using the Print Manager plugin.\r\n\r\nNOTE: This replaces the dup_prt.zip Duplex Printing plugin - if you had previously installed this plugin then please remove this from your runtime directories.","4":"This plugin extends the flexibility of printing from VIM using PSUtils - http:\/\/www.tardis.ed.ac.uk\/~ajcd\/psutils\/. The plugin supports:\r\n\r\no N-up printing,\r\no Manual duplex printing (feeding printed pages back into the printer to print the reverse sides)\r\no Reverse page order printing.\r\no Print to file.\r\n\r\nThere are also VIM functions to allow the Print Manager to be called from other scripts, as well as being hooked to the :hardcopy command using the printexpr option.\r\n\r\nSee included help file for details on setting up and using the Print Manager plugin.\r\n\r\nNOTE: This replaces the dup_prt.zip Duplex Printing plugin - if you had previously installed this plugin then please remove this from your runtime directories.","install_details":"Unzip the file into your local VIM runtime directory, restart VIM, and run helptags on your local doc directory.","5":"Unzip the file into your local VIM runtime directory, restart VIM, and run helptags on your local doc directory.","first_name":"Mike","6":"Mike","last_name":"Williams","7":"Williams","releases":[{"0":"181","vim_version":"6.0","1":"6.0","script_version":"2.2","2":"2.2","version_comment":"Fix bug when doing Nup printing to A or B series paper sizes (other than default of A4).","3":"Fix bug when doing Nup printing to A or B series paper sizes (other than default of A4).","package":"prt_mgr.zip","4":"prt_mgr.zip","src_id":"2686","5":"2686","creation_date":"1075279206","6":"1075279206"}]},"180":{"script_id":"180","0":"180","script_name":"remcmd.vim","1":"remcmd.vim","script_type":"utility","2":"utility","summary":"Send commands to remote Vim sessions","3":"Send commands to remote Vim sessions","description":"This script came out of my misc utility functions to send some useful commands to a remote Vim session. It basically adds four commands as follows (assuming that your <Leader> is set to \\):\r\n\r\n    \\ro - Opens the current file in a remote Vim session.\r\n    \\re - Executes a command in the remote Vim session.\r\n    \\ta - Opens the current tag in the remote Vim session.\r\n    \\ts - Selects the current tag in the remote Vim session.\r\n\r\nEach one of the above commands prompts the user to select the name of a remote Vim and executes the command. To make your life easier, it even remembers your previous selection, so repeated execution of remote commands in the same remote Vim session is easy.\r\n\r\nThough it adds only 4, it is because I don't know what commans other might like to add. But it is easy enough for you to add your favourite commands this way. It exposes the basic functions necessary to do it yourself from your own script or .vimrc:\r\n\r\n       RemCmdServerList(), RemCmdSelectServer(), RemCmdSendRemoteCommand()\r\n\r\nTake a look at the script on how to use these functions. For convenience, you can add regular and\/or popup menu group for this with the name \"Remcmd\" by setting some global variables in your .vimrc. Take a look at the script header for details.\r\n","4":"This script came out of my misc utility functions to send some useful commands to a remote Vim session. It basically adds four commands as follows (assuming that your <Leader> is set to \\):\r\n\r\n    \\ro - Opens the current file in a remote Vim session.\r\n    \\re - Executes a command in the remote Vim session.\r\n    \\ta - Opens the current tag in the remote Vim session.\r\n    \\ts - Selects the current tag in the remote Vim session.\r\n\r\nEach one of the above commands prompts the user to select the name of a remote Vim and executes the command. To make your life easier, it even remembers your previous selection, so repeated execution of remote commands in the same remote Vim session is easy.\r\n\r\nThough it adds only 4, it is because I don't know what commans other might like to add. But it is easy enough for you to add your favourite commands this way. It exposes the basic functions necessary to do it yourself from your own script or .vimrc:\r\n\r\n       RemCmdServerList(), RemCmdSelectServer(), RemCmdSendRemoteCommand()\r\n\r\nTake a look at the script on how to use these functions. For convenience, you can add regular and\/or popup menu group for this with the name \"Remcmd\" by setting some global variables in your .vimrc. Take a look at the script header for details.\r\n","install_details":"Just drop it in your plugin directory or source it from your .vimrc.\r\n\r\nYou need multvals.vim (2.0.4) for this to work, download from:\r\nhttp:\/\/vim.sourceforge.net\/scripts\/script.php?script_id=171","5":"Just drop it in your plugin directory or source it from your .vimrc.\r\n\r\nYou need multvals.vim (2.0.4) for this to work, download from:\r\nhttp:\/\/vim.sourceforge.net\/scripts\/script.php?script_id=171","first_name":"Hari Krishna","6":"Hari Krishna","last_name":"Dara","7":"Dara","releases":[{"0":"180","vim_version":"6.0","1":"6.0","script_version":"1.0.7","2":"1.0.7","version_comment":"Added register sharing capability with some limitations. You can specify a list of comma separated local registers to be synced to remote registers. You can even specify a different remote register than the local one. The following is very useful:\r\n\r\n  let g:remcmdRegisters='\"'\r\n  let g:remcmdRemoteRegisters='r'\r\n\r\nThis makes whatever you copy in whichever Vim window always available in the r (for remote) register of other vim windows. However there are some limitations, it doesn't automatically sync when the yank (or delete) command starts with y (or d), such as y'a. Use RCmdSyncRegisters or the SyncRegisters menu (if menu is enabled) to force a sync. You can enable the main menu or popup menu by setting the following variables:\r\n\r\n    let g:remcmdAddToMenu=1\r\n    let g:remcmdAddToPopupMenu=1\r\n\r\nPlease see the script for more features, sorry I don't have time to write a help page. Please send in your feedback.","3":"Added register sharing capability with some limitations. You can specify a list of comma separated local registers to be synced to remote registers. You can even specify a different remote register than the local one. The following is very useful:\r\n\r\n  let g:remcmdRegisters='\"'\r\n  let g:remcmdRemoteRegisters='r'\r\n\r\nThis makes whatever you copy in whichever Vim window always available in the r (for remote) register of other vim windows. However there are some limitations, it doesn't automatically sync when the yank (or delete) command starts with y (or d), such as y'a. Use RCmdSyncRegisters or the SyncRegisters menu (if menu is enabled) to force a sync. You can enable the main menu or popup menu by setting the following variables:\r\n\r\n    let g:remcmdAddToMenu=1\r\n    let g:remcmdAddToPopupMenu=1\r\n\r\nPlease see the script for more features, sorry I don't have time to write a help page. Please send in your feedback.","package":"remcmd.vim","4":"remcmd.vim","src_id":"616","5":"616","creation_date":"1014163370","6":"1014163370"},{"0":"180","vim_version":"6.0","1":"6.0","script_version":"1.0.3","2":"1.0.3","version_comment":"Added RCmdPresetServer command that takes in a server name to be used for all the operations. Until you call the same command passing an empty string \"\", you will not prompted to select the server, which makes it easy to execute repeated remote commands in the same remote session.\r\n\r\nAlso added two new commands \\sf and \\sb to search forward and backward for the current word in the remote session.","3":"Added RCmdPresetServer command that takes in a server name to be used for all the operations. Until you call the same command passing an empty string \"\", you will not prompted to select the server, which makes it easy to execute repeated remote commands in the same remote session.\r\n\r\nAlso added two new commands \\sf and \\sb to search forward and backward for the current word in the remote session.","package":"remcmd.vim","4":"remcmd.vim","src_id":"550","5":"550","creation_date":"1012850177","6":"1012850177"},{"0":"180","vim_version":"6.0","1":"6.0","script_version":"1.0.1","2":"1.0.1","version_comment":"Initial upload","3":"Initial upload","package":"remcmd.vim","4":"remcmd.vim","src_id":"468","5":"468","creation_date":"1010780293","6":"1010780293"}]},"179":{"script_id":"179","0":"179","script_name":"ViMail","1":"ViMail","script_type":"utility","2":"utility","summary":"Compose and send mail from vim.","3":"Compose and send mail from vim.","description":"This script is intended to provide an easy and quick way of sending e-mail messages from within vim.","4":"This script is intended to provide an easy and quick way of sending e-mail messages from within vim.","install_details":":source vimail.vim","5":":source vimail.vim","first_name":"Little","6":"Little","last_name":"Dragon","7":"Dragon","releases":[{"0":"179","vim_version":"6.0","1":"6.0","script_version":"0.1.5","2":"0.1.5","version_comment":"Created global variables, added alias completion and modified the :SendMail function to send even if the current buffer doesn't contain headers (experimental).","3":"Created global variables, added alias completion and modified the :SendMail function to send even if the current buffer doesn't contain headers (experimental).","package":"vimail-0.1.5.vim","4":"vimail-0.1.5.vim","src_id":"581","5":"581","creation_date":"1013595388","6":"1013595388"}]},"178":{"script_id":"178","0":"178","script_name":"A better tcl indent","1":"A better tcl indent","script_type":"indent","2":"indent","summary":"A better tcl indent (for me:)","3":"A better tcl indent (for me:)","description":"I noticed some bugs (maybe vim's bug) when reindenting lines in a tcl code, write my own indent file, which works well for me.","4":"I noticed some bugs (maybe vim's bug) when reindenting lines in a tcl code, write my own indent file, which works well for me.","install_details":"","5":"","first_name":"Gergely","6":"Gergely","last_name":"Kontra","7":"Kontra","releases":[{"0":"178","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"tcl.vim","4":"tcl.vim","src_id":"458","5":"458","creation_date":"1010669522","6":"1010669522"}]},"177":{"script_id":"177","0":"177","script_name":"Justify","1":"Justify","script_type":"utility","2":"utility","summary":"Simple text justifier inspired by Kartik Murari's format.vim (vimscript#27)","3":"Simple text justifier inspired by Kartik Murari's format.vim (vimscript#27)","description":"This script defines a new Justify command.\r\nYou can define ranges with the script, and optionally you can define the text width.\r\n\r\nI am happy to link to other similar programs, just drop me a mail!","4":"This script defines a new Justify command.\r\nYou can define ranges with the script, and optionally you can define the text width.\r\n\r\nI am happy to link to other similar programs, just drop me a mail!","install_details":"Drop it into your plugin directory!","5":"Drop it into your plugin directory!","first_name":"Gergely","6":"Gergely","last_name":"Kontra","7":"Kontra","releases":[{"0":"177","vim_version":"6.0","1":"6.0","script_version":"0.3","2":"0.3","version_comment":"- Multibyte patch by Teemu Likonen\r\n- Makes substitute silent","3":"- Multibyte patch by Teemu Likonen\r\n- Makes substitute silent","package":"MyJustify.vim","4":"MyJustify.vim","src_id":"9032","5":"9032","creation_date":"1217133452","6":"1217133452"},{"0":"177","vim_version":"6.0","1":"6.0","script_version":"0.2","2":"0.2","version_comment":"avoids a small annoying beep on some lines (and prevents user map interference). ","3":"avoids a small annoying beep on some lines (and prevents user map interference). ","package":"MyJustify.vim","4":"MyJustify.vim","src_id":"4230","5":"4230","creation_date":"1115036630","6":"1115036630"},{"0":"177","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"MyJustify.vim","4":"MyJustify.vim","src_id":"456","5":"456","creation_date":"1010653324","6":"1010653324"}]},"176":{"script_id":"176","0":"176","script_name":"Lineup - A simple text aligner","1":"Lineup - A simple text aligner","script_type":"utility","2":"utility","summary":"Aligns the Nth occurence of a string or RE","3":"Aligns the Nth occurence of a string or RE","description":"Use Align.vim vimscript#294, it knows a lot more!\r\n\r\nIt is a simple text aligner\r\n:'<,'>Lineup = to align your visually selected equations.\r\n","4":"Use Align.vim vimscript#294, it knows a lot more!\r\n\r\nIt is a simple text aligner\r\n:'<,'>Lineup = to align your visually selected equations.\r\n","install_details":"Drop it into your plugin directory","5":"Drop it into your plugin directory","first_name":"Gergely","6":"Gergely","last_name":"Kontra","7":"Kontra","releases":[{"0":"176","vim_version":"6.0","1":"6.0","script_version":"0.13","2":"0.13","version_comment":"* Bugfixes\r\n* Allows to lineup Nth occurence","3":"* Bugfixes\r\n* Allows to lineup Nth occurence","package":"Lineup.vim","4":"Lineup.vim","src_id":"865","5":"865","creation_date":"1021026790","6":"1021026790"}]},"175":{"script_id":"175","0":"175","script_name":"CreateMenuPath.vim","1":"CreateMenuPath.vim","script_type":"utility","2":"utility","summary":"Create a menu that mirrors a directory tree","3":"Create a menu that mirrors a directory tree","description":"This file provides a function to create a menu that mirrors a directory tree.\r\n\r\nUsage:\r\nCreateMenuPath({path} [, {menu name} [, {menu priority} [, {filename ignore pattern1} [, {filename ignore pattern2} ...]]]])\r\n\r\nExamples:\r\n:call CreateMenuPath('~')   \" Creates a menu of your home directory.\r\n\r\n:call CreateMenuPath('~\/public_html', 'Files.Web\\ Page', '600.100', '\\c.\\(gif\\|jpe\\=g\\|png\\|ico\\|bmp\\|tiff\\=\\)$')  \" Files.Web Page menu, priority 600.100, ignoring some image files.\r\n\r\nA default filename ignore pattern is provided which ignores a number of image, audio and archive files, but it's incomplete.\r\n\r\nThe global variable \"CMP_Recurse_Limit\" can be set to specify the maximum sub-directory depth to scan.  Set it to 0 (the default) for infinite recursion.  Set it to 1 to scan only the specified directory.\r\n","4":"This file provides a function to create a menu that mirrors a directory tree.\r\n\r\nUsage:\r\nCreateMenuPath({path} [, {menu name} [, {menu priority} [, {filename ignore pattern1} [, {filename ignore pattern2} ...]]]])\r\n\r\nExamples:\r\n:call CreateMenuPath('~')   \" Creates a menu of your home directory.\r\n\r\n:call CreateMenuPath('~\/public_html', 'Files.Web\\ Page', '600.100', '\\c.\\(gif\\|jpe\\=g\\|png\\|ico\\|bmp\\|tiff\\=\\)$')  \" Files.Web Page menu, priority 600.100, ignoring some image files.\r\n\r\nA default filename ignore pattern is provided which ignores a number of image, audio and archive files, but it's incomplete.\r\n\r\nThe global variable \"CMP_Recurse_Limit\" can be set to specify the maximum sub-directory depth to scan.  Set it to 0 (the default) for infinite recursion.  Set it to 1 to scan only the specified directory.\r\n","install_details":"Either :source it or put it in your plugin directory.","5":"Either :source it or put it in your plugin directory.","first_name":"Christian J.","6":"Christian J.","last_name":"Robinson","7":"Robinson","releases":[{"0":"175","vim_version":"9.0","1":"9.0","script_version":"3.0","2":"3.0","version_comment":"- Update for Vim 9 (no new features)","3":"- Update for Vim 9 (no new features)","package":"CreateMenuPath.vim","4":"CreateMenuPath.vim","src_id":"28142","5":"28142","creation_date":"1661156238","6":"1661156238"},{"0":"175","vim_version":"7.0","1":"7.0","script_version":"2.0","2":"2.0","version_comment":"Update for Vim7:\r\n  - Allow more than one ignore pattern argument\r\n  - Looping over the found files is simpler","3":"Update for Vim7:\r\n  - Allow more than one ignore pattern argument\r\n  - Looping over the found files is simpler","package":"CreateMenuPath.vim","4":"CreateMenuPath.vim","src_id":"8713","5":"8713","creation_date":"1211517714","6":"1211517714"},{"0":"175","vim_version":"6.0","1":"6.0","script_version":"1.5","2":"1.5","version_comment":"- Don't add a \/ or \\ before the glob pattern if it's already there. (Fixes that a path of 'c:\\' wouldn't work.)","3":"- Don't add a \/ or \\ before the glob pattern if it's already there. (Fixes that a path of 'c:\\' wouldn't work.)","package":"CreateMenuPath.vim","4":"CreateMenuPath.vim","src_id":"685","5":"685","creation_date":"1016224924","6":"1016224924"},{"0":"175","vim_version":"6.0","1":"6.0","script_version":"1.4","2":"1.4","version_comment":"CMP_Recurse_Limit global variable added.","3":"CMP_Recurse_Limit global variable added.","package":"CreateMenuPath.vim","4":"CreateMenuPath.vim","src_id":"508","5":"508","creation_date":"1011906170","6":"1011906170"},{"0":"175","vim_version":"6.0","1":"6.0","script_version":"1.3","2":"1.3","version_comment":"- Use a dummy menu item to prevent a torn off menu from disappearing. (Does not work in the PopUp menu.)","3":"- Use a dummy menu item to prevent a torn off menu from disappearing. (Does not work in the PopUp menu.)","package":"CreateMenuPath.vim","4":"CreateMenuPath.vim","src_id":"496","5":"496","creation_date":"1011375140","6":"1011375140"},{"0":"175","vim_version":"6.0","1":"6.0","script_version":"1.2","2":"1.2","version_comment":"- Rescan menu item didn't work.\r\n- Escape some characters in CD Here menu item.\r\n- Create a ...More menu when the number of menu items exceeds 30, and add shortcut keys.","3":"- Rescan menu item didn't work.\r\n- Escape some characters in CD Here menu item.\r\n- Create a ...More menu when the number of menu items exceeds 30, and add shortcut keys.","package":"CreateMenuPath.vim","4":"CreateMenuPath.vim","src_id":"459","5":"459","creation_date":"1010682002","6":"1010682002"},{"0":"175","vim_version":"6.0","1":"6.0","script_version":"1.1","2":"1.1","version_comment":"- Two menu items added:  \"CD Here\" and \"Rescan\"\r\n- Clear the menu out before building it.  (Marcin Juszkiewicz)","3":"- Two menu items added:  \"CD Here\" and \"Rescan\"\r\n- Clear the menu out before building it.  (Marcin Juszkiewicz)","package":"CreateMenuPath.vim","4":"CreateMenuPath.vim","src_id":"453","5":"453","creation_date":"1010635142","6":"1010635142"}]},"174":{"script_id":"174","0":"174","script_name":"tf.vim","1":"tf.vim","script_type":"indent","2":"indent","summary":"tf (TinyFugue) indent file","3":"tf (TinyFugue) indent file","description":"Provides indent rules for tf (TinyFugue).","4":"Provides indent rules for tf (TinyFugue).","install_details":"Put it in <runtimepath>\/indent\/","5":"Put it in <runtimepath>\/indent\/","first_name":"Christian J.","6":"Christian J.","last_name":"Robinson","7":"Robinson","releases":[{"0":"174","vim_version":"7.0","1":"7.0","script_version":"0.11","2":"0.11","version_comment":"Set b:undo_indent (Doug Kearns)","3":"Set b:undo_indent (Doug Kearns)","package":"tf.vim","4":"tf.vim","src_id":"28016","5":"28016","creation_date":"1650939665","6":"1650939665"},{"0":"174","vim_version":"7.4","1":"7.4","script_version":"0.10","2":"0.10","version_comment":"Use shiftwidth() instead of &shiftwidth","3":"Use shiftwidth() instead of &shiftwidth","package":"tf.vim","4":"tf.vim","src_id":"24999","5":"24999","creation_date":"1488044936","6":"1488044936"},{"0":"174","vim_version":"6.0","1":"6.0","script_version":"0.9","2":"0.9","version_comment":"No indentation if the previous line didn't end with \"\\\".\r\nThis could be annoying, but it lets you know if you made a mistake.","3":"No indentation if the previous line didn't end with \"\\\".\r\nThis could be annoying, but it lets you know if you made a mistake.","package":"tf.vim","4":"tf.vim","src_id":"922","5":"922","creation_date":"1023938163","6":"1023938163"},{"0":"174","vim_version":"6.0","1":"6.0","script_version":"0.8","2":"0.8","version_comment":"Initial upload","3":"Initial upload","package":"tf.vim","4":"tf.vim","src_id":"451","5":"451","creation_date":"1010586209","6":"1010586209"}]},"173":{"script_id":"173","0":"173","script_name":"boxdraw","1":"boxdraw","script_type":"utility","2":"utility","summary":"Draw diagrams and tables using boxdrawing characters","3":"Draw diagrams and tables using boxdrawing characters","description":"Summary\r\n-------\r\n * Draw diagrams and tables using \"real box drawing characters\" (AKA ANSI\r\nart).\r\n * Move rectangular\/linear blocks of text around.\r\n * Trace box-drawing typeset diagrams -- follow the lines, etc.\r\n\r\nDetailed description\r\n--------------------\r\nThese scripts facilitate drawing simple 'ANSI' graphic containing box\r\ndrawing characters (not just '+', '-' and '|', but REAL box drawing\r\ncharacters).  It can be useful to draw diagrams and fancy tables (at\r\nleast, I use it this way).\r\n\r\nUpon sourcing the script defines several macros:\r\n\r\n<shift+arrow> -- moves cursor in specified direction leaving trail of\r\nbox drawing characters, making all joins and crossings.\r\ng+<arrow> -- follow line of boxdrawing characters until it reaches\r\nintersection or ends.\r\n<shift+arrow> in visual mode -- move selected rectangular block in\r\nspecified direction.\r\n\\e -- ends box drawing mode (unmap shift+arrows macros and restore\r\nvirtualedit value)\r\n\\b -- restarts box drawing (map shift+arrows macros and set virtual\r\n      edit=all)\r\n\\s -- selects 'single-line' boxdrawing characters\r\n\\d -- selects 'double-line' boxdrawing characters\r\n\\a -- convert all characters in selection into ascii '+', '-', '|' (utf8\r\n      only, not implemented)\r\n(\"\\\" prefix may be changed by changing mapleader variable, see :h mapleader)\r\n\r\nWhen rectangular block is selected, it can be moved around using\r\n<shift-arrow> keys. Unfortunately, as of version 6.1 multibyte\r\ncharacters and rectangular blocks do not live together too good, so this\r\nfeature is experimental.\r\n\r\nWhen line block is selected, <shift-up> and <shift-down> moves it up or down\r\nnondestructively, <shift-left> decreases indent and <shift-up> increases\r\nindent.\r\n\r\nCurrently box drawing is supported for utf8 and cp437 (DOS) encodings.\r\n\r\nScript does not use any \"weird\" box drawing characters from unicode set\r\nthat are not present in, say, cp437. So, it is safe to save utf-8 file\r\nin any single byte encoding that contains regular single box drawing\r\ncharacters.\r\nThis script also contains mapping that converts all boxdrawing\r\ncharacters in current selection into ascii '+', '-', '|'.\r\n\r\nIf vim encoding is single byte, this script assumes cp437 (DOS). Most\r\nencodings have boxdrawing characters at the same place, however, some\r\n(notably, koi8-r) have them in different code postions.\r\nIf you want to use it with encoding that contains such\r\ncharacters in diferent place, please drop me a note -- I will be happy\r\nto add support for that codepage too.\r\n\r\nTo help you determine which boxdrawing characters are suppored by your\r\nterminal I have included file sampler.txt. Just type it (or cat it) on\r\nthe termianal and encoding that labels the block that looks \"right\" will\r\nbe your supported encoding.\r\n\r\nNote for PuTTY users\r\n--------------------\r\n\r\nIt turns out that PuTTY does not translate Shift+Arrow combination into\r\nX key code (like xterm does), so mappings will not work for this\r\nterminal. I have modified initialization script to use <arrows> instead\r\nof <shift>+<arrows> in Unix environment.\r\n\r\nPerl scripts\r\n------------\r\n\r\nSome box-drawing related procedures are more naturally done with\r\nexternal scripts. These scripts take ascii standard input and produce\r\nutf8 encoded standard output.\r\n\r\nbdua2b.pl -- converts regular '+-|'-style drawing into single-line utf8\r\n  boxdrawing. This script has does not just blindly replace characters,\r\n  but instead looks to the neighbourhood and chooses boxdrawing\r\n  character that fits best. Use this script as a filter to convert\r\n  existing ascii drawings.\r\n  Option -ss selects single border characters, -sd -- double border,\r\n  -sh -- single vertical double horizontal, -sv single horizontal double\r\n  vertical.\r\n\r\noutline.pl -- outlines groups of similar characters in the input with\r\n  boxdrawing characters. Option -d makes output twice as wide, options\r\n  -s* select boxdrawing flavor as in previous script.\r\n  For example,\r\n\r\n  aaaacc\r\n  abbcc\r\n  ccbbc\r\n  cccb\r\n\r\nwill be converted into\r\n\r\n  ┌───┬─┐\r\n  │┌─┬┘┌┘\r\n  ├┴┐└┐│\r\n  │ └┐├┘\r\n  └──┴┘\r\n\r\nor\r\n\r\n  ┌───────┬───┐\r\n  │ ┌───┬─┘ ┌─┘\r\n  ├─┴─┐ └─┐ │\r\n  │   └─┐ ├─┘\r\n  └─────┴─┘\r\n\r\n\r\nBoth scripts were tested with ActivePerl 5.6.1.\r\n\r\nPlans:\r\n------\r\n* Support double boxes in a cleaner way.\r\n\r\nInstallation\r\n------------\r\nCopy boxdraw.vim to the place where you normally keep vim scripts (e.g. ~\/.vim\r\nor c:\\vim\\vimfiles) and source it every time you want to draw a diagram or nice\r\ntable.\r\n\r\nYou may wish also to add this to your menu by adding a line to your .gvimrc\r\n(_gvimrc) file (use actual path to boxdraw.vim):\r\n:menu Tools.Bo&x\\ Draw :so ~\/.vim\/boxdraw.vim<CR>\r\n\r\nEnvironment\r\n-----------\r\nI run Windows and use boxdraw.vim in gvim (it supports utf-8 very\r\nnicely) and bd-single in vim (its support of utf-8 is kind of unclear\r\nfor me). Both major Windows monospaced fonts (Courier New and Lucida\r\nConsole) support wide range of Unicode characters, including box\r\ndrawing.\r\n\r\nWhy use box drawing characters?\r\n-------------------------------\r\nThese characters are in Unicode standard for compatibility with wide\r\nrange of existing 8-bit encodings that have them. The wording of Unicode\r\nstandard discourages usage of such characters, other than for the\r\npurpose of converting between encodigns and storage of legacy data.\r\nHaving said all that I found that sometimes a picture, even crude and\r\nprimitive, is worth pages of explanations. Just about the only way to\r\ninclude picture in source code is to use ascii or \"ansi\" art. Ascii is\r\nmore compatible, but \"ansi\" looks way better. Since I have to use\r\nUnicode to include cyrillic characters in comments anyway, I decided to\r\nstop on \"ansi\" art as a format of choice for in-source drawings.\r\n\r\nAuthor\r\n------\r\nAndrew Nikitin <nsg21@hotmail.com>\r\n","4":"Summary\r\n-------\r\n * Draw diagrams and tables using \"real box drawing characters\" (AKA ANSI\r\nart).\r\n * Move rectangular\/linear blocks of text around.\r\n * Trace box-drawing typeset diagrams -- follow the lines, etc.\r\n\r\nDetailed description\r\n--------------------\r\nThese scripts facilitate drawing simple 'ANSI' graphic containing box\r\ndrawing characters (not just '+', '-' and '|', but REAL box drawing\r\ncharacters).  It can be useful to draw diagrams and fancy tables (at\r\nleast, I use it this way).\r\n\r\nUpon sourcing the script defines several macros:\r\n\r\n<shift+arrow> -- moves cursor in specified direction leaving trail of\r\nbox drawing characters, making all joins and crossings.\r\ng+<arrow> -- follow line of boxdrawing characters until it reaches\r\nintersection or ends.\r\n<shift+arrow> in visual mode -- move selected rectangular block in\r\nspecified direction.\r\n\\e -- ends box drawing mode (unmap shift+arrows macros and restore\r\nvirtualedit value)\r\n\\b -- restarts box drawing (map shift+arrows macros and set virtual\r\n      edit=all)\r\n\\s -- selects 'single-line' boxdrawing characters\r\n\\d -- selects 'double-line' boxdrawing characters\r\n\\a -- convert all characters in selection into ascii '+', '-', '|' (utf8\r\n      only, not implemented)\r\n(\"\\\" prefix may be changed by changing mapleader variable, see :h mapleader)\r\n\r\nWhen rectangular block is selected, it can be moved around using\r\n<shift-arrow> keys. Unfortunately, as of version 6.1 multibyte\r\ncharacters and rectangular blocks do not live together too good, so this\r\nfeature is experimental.\r\n\r\nWhen line block is selected, <shift-up> and <shift-down> moves it up or down\r\nnondestructively, <shift-left> decreases indent and <shift-up> increases\r\nindent.\r\n\r\nCurrently box drawing is supported for utf8 and cp437 (DOS) encodings.\r\n\r\nScript does not use any \"weird\" box drawing characters from unicode set\r\nthat are not present in, say, cp437. So, it is safe to save utf-8 file\r\nin any single byte encoding that contains regular single box drawing\r\ncharacters.\r\nThis script also contains mapping that converts all boxdrawing\r\ncharacters in current selection into ascii '+', '-', '|'.\r\n\r\nIf vim encoding is single byte, this script assumes cp437 (DOS). Most\r\nencodings have boxdrawing characters at the same place, however, some\r\n(notably, koi8-r) have them in different code postions.\r\nIf you want to use it with encoding that contains such\r\ncharacters in diferent place, please drop me a note -- I will be happy\r\nto add support for that codepage too.\r\n\r\nTo help you determine which boxdrawing characters are suppored by your\r\nterminal I have included file sampler.txt. Just type it (or cat it) on\r\nthe termianal and encoding that labels the block that looks \"right\" will\r\nbe your supported encoding.\r\n\r\nNote for PuTTY users\r\n--------------------\r\n\r\nIt turns out that PuTTY does not translate Shift+Arrow combination into\r\nX key code (like xterm does), so mappings will not work for this\r\nterminal. I have modified initialization script to use <arrows> instead\r\nof <shift>+<arrows> in Unix environment.\r\n\r\nPerl scripts\r\n------------\r\n\r\nSome box-drawing related procedures are more naturally done with\r\nexternal scripts. These scripts take ascii standard input and produce\r\nutf8 encoded standard output.\r\n\r\nbdua2b.pl -- converts regular '+-|'-style drawing into single-line utf8\r\n  boxdrawing. This script has does not just blindly replace characters,\r\n  but instead looks to the neighbourhood and chooses boxdrawing\r\n  character that fits best. Use this script as a filter to convert\r\n  existing ascii drawings.\r\n  Option -ss selects single border characters, -sd -- double border,\r\n  -sh -- single vertical double horizontal, -sv single horizontal double\r\n  vertical.\r\n\r\noutline.pl -- outlines groups of similar characters in the input with\r\n  boxdrawing characters. Option -d makes output twice as wide, options\r\n  -s* select boxdrawing flavor as in previous script.\r\n  For example,\r\n\r\n  aaaacc\r\n  abbcc\r\n  ccbbc\r\n  cccb\r\n\r\nwill be converted into\r\n\r\n  ┌───┬─┐\r\n  │┌─┬┘┌┘\r\n  ├┴┐└┐│\r\n  │ └┐├┘\r\n  └──┴┘\r\n\r\nor\r\n\r\n  ┌───────┬───┐\r\n  │ ┌───┬─┘ ┌─┘\r\n  ├─┴─┐ └─┐ │\r\n  │   └─┐ ├─┘\r\n  └─────┴─┘\r\n\r\n\r\nBoth scripts were tested with ActivePerl 5.6.1.\r\n\r\nPlans:\r\n------\r\n* Support double boxes in a cleaner way.\r\n\r\nInstallation\r\n------------\r\nCopy boxdraw.vim to the place where you normally keep vim scripts (e.g. ~\/.vim\r\nor c:\\vim\\vimfiles) and source it every time you want to draw a diagram or nice\r\ntable.\r\n\r\nYou may wish also to add this to your menu by adding a line to your .gvimrc\r\n(_gvimrc) file (use actual path to boxdraw.vim):\r\n:menu Tools.Bo&x\\ Draw :so ~\/.vim\/boxdraw.vim<CR>\r\n\r\nEnvironment\r\n-----------\r\nI run Windows and use boxdraw.vim in gvim (it supports utf-8 very\r\nnicely) and bd-single in vim (its support of utf-8 is kind of unclear\r\nfor me). Both major Windows monospaced fonts (Courier New and Lucida\r\nConsole) support wide range of Unicode characters, including box\r\ndrawing.\r\n\r\nWhy use box drawing characters?\r\n-------------------------------\r\nThese characters are in Unicode standard for compatibility with wide\r\nrange of existing 8-bit encodings that have them. The wording of Unicode\r\nstandard discourages usage of such characters, other than for the\r\npurpose of converting between encodigns and storage of legacy data.\r\nHaving said all that I found that sometimes a picture, even crude and\r\nprimitive, is worth pages of explanations. Just about the only way to\r\ninclude picture in source code is to use ascii or \"ansi\" art. Ascii is\r\nmore compatible, but \"ansi\" looks way better. Since I have to use\r\nUnicode to include cyrillic characters in comments anyway, I decided to\r\nstop on \"ansi\" art as a format of choice for in-source drawings.\r\n\r\nAuthor\r\n------\r\nAndrew Nikitin <nsg21@hotmail.com>\r\n","install_details":"Copy boxdraw.vim to the place where you normally keep vim scripts (e.g. ~\/.vim\r\nor c:\\vim\\vimfiles) and source it every time you want to draw a diagram or nice\r\ntable.\r\n\r\nYou may wish also to add this to your menu by adding a line to your .gvimrc\r\n(_gvimrc) file (use actual path to boxdraw.vim):\r\n:menu Tools.Bo&x\\ Draw :so ~\/.vim\/boxdraw.vim<CR>\r\n\r\nI run Windows and use boxdraw.vim in gvim (it supports utf-8 very\r\nnicely) and bd-single in vim (its support for utf-8 is kind of unclear\r\nto me).\r\n","5":"Copy boxdraw.vim to the place where you normally keep vim scripts (e.g. ~\/.vim\r\nor c:\\vim\\vimfiles) and source it every time you want to draw a diagram or nice\r\ntable.\r\n\r\nYou may wish also to add this to your menu by adding a line to your .gvimrc\r\n(_gvimrc) file (use actual path to boxdraw.vim):\r\n:menu Tools.Bo&x\\ Draw :so ~\/.vim\/boxdraw.vim<CR>\r\n\r\nI run Windows and use boxdraw.vim in gvim (it supports utf-8 very\r\nnicely) and bd-single in vim (its support for utf-8 is kind of unclear\r\nto me).\r\n","first_name":"Andrew","6":"Andrew","last_name":"Nikitin","7":"Nikitin","releases":[{"0":"173","vim_version":"6.0","1":"6.0","script_version":"1.1","2":"1.1","version_comment":"special processing for line-block movements, changed cabbr for perl\r\n","3":"special processing for line-block movements, changed cabbr for perl\r\n","package":"boxdraw.zip","4":"boxdraw.zip","src_id":"9687","5":"9687","creation_date":"1229543032","6":"1229543032"},{"0":"173","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"combined single-byte and utf8 versions, included sampler.txt to help determine encoding","3":"combined single-byte and utf8 versions, included sampler.txt to help determine encoding","package":"boxdraw.zip","4":"boxdraw.zip","src_id":"3665","5":"3665","creation_date":"1101486472","6":"1101486472"},{"0":"173","vim_version":"6.0","1":"6.0","script_version":"0.4","2":"0.4","version_comment":"following the lines, updated perl scripts","3":"following the lines, updated perl scripts","package":"boxdraw.zip","4":"boxdraw.zip","src_id":"3154","5":"3154","creation_date":"1087588870","6":"1087588870"},{"0":"173","vim_version":"6.0","1":"6.0","script_version":"0.3","2":"0.3","version_comment":"perl scripts + some rectangular block movements","3":"perl scripts + some rectangular block movements","package":"boxdraw.zip","4":"boxdraw.zip","src_id":"2513","5":"2513","creation_date":"1069731785","6":"1069731785"},{"0":"173","vim_version":"6.0","1":"6.0","script_version":"0.2","2":"0.2","version_comment":"support for single-byte encoding, box->ascii conversion","3":"support for single-byte encoding, box->ascii conversion","package":"boxdraw.zip","4":"boxdraw.zip","src_id":"523","5":"523","creation_date":"1012420865","6":"1012420865"},{"0":"173","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Double boxeswere added. Still only utf-8.","3":"Double boxeswere added. Still only utf-8.","package":"boxdraw.zip","4":"boxdraw.zip","src_id":"460","5":"460","creation_date":"1010687250","6":"1010687250"},{"0":"173","vim_version":"6.0","1":"6.0","script_version":"0.0","2":"0.0","version_comment":"Initial upload","3":"Initial upload","package":"boxdraw.vim","4":"boxdraw.vim","src_id":"450","5":"450","creation_date":"1010567010","6":"1010567010"}]},"172":{"script_id":"172","0":"172","script_name":"TeTrIs.vim","1":"TeTrIs.vim","script_type":"game","2":"game","summary":"A tetris game in pure vim","3":"A tetris game in pure vim","description":"A funny way to get used to VIM's h k l and <Space> key.\r\nThe first (I hope) interactive game inside pure VIM!\r\nIt's a work-in-progress version.\r\n\r\nTodo:\r\n- better random\r\n- better timing\r\n- shorter code\r\n\r\nIf you like games, also see Sokoban vimscript#211!","4":"A funny way to get used to VIM's h k l and <Space> key.\r\nThe first (I hope) interactive game inside pure VIM!\r\nIt's a work-in-progress version.\r\n\r\nTodo:\r\n- better random\r\n- better timing\r\n- shorter code\r\n\r\nIf you like games, also see Sokoban vimscript#211!","install_details":"Source it! Press :source TeTrIs.vim<Enter>\r\n\r\nTo start the game, press <Leader>te.\r\n(If you don't know what is <Leader>, you should press \\te, and type :help Leader<Enter> to learn about what the heck leader is)\r\nControls:\r\nh: left\r\nl: right\r\nj: down\r\ni,k: rotate\r\n<Space>: drop\r\n<Esc> or q: quit\r\n(if you have more or other keys, which help you to learn VIM, please send me the mail)\r\np: pause game To restore, press <Leader>te in any window!\r\n\r\n*** Save everything, before you begin to play ***","5":"Source it! Press :source TeTrIs.vim<Enter>\r\n\r\nTo start the game, press <Leader>te.\r\n(If you don't know what is <Leader>, you should press \\te, and type :help Leader<Enter> to learn about what the heck leader is)\r\nControls:\r\nh: left\r\nl: right\r\nj: down\r\ni,k: rotate\r\n<Space>: drop\r\n<Esc> or q: quit\r\n(if you have more or other keys, which help you to learn VIM, please send me the mail)\r\np: pause game To restore, press <Leader>te in any window!\r\n\r\n*** Save everything, before you begin to play ***","first_name":"Gergely","6":"Gergely","last_name":"Kontra","7":"Kontra","releases":[{"0":"172","vim_version":"7.0","1":"7.0","script_version":"0.53","2":"0.53","version_comment":"This version is written by Felix Leger\r\n\r\nChangelog:\r\n- Shape rotations now match official Super Rotation System (SRS)\r\n- High scores don\\'t wrap around when displayed\r\n- First shape is now always random (instead of always being a bar)\r\n- Shapes\\' color scheme now matches official Tetris colors as closely as possible (since default terminal ANSI doesn\\'t support orange for L shape, that one is white instead\r\n- Since v0.5, colors are randomly attributed. Now each shape has its own color, like in official Tetris\r\n- Shapes now are homogeneously colored, we see MM, {}, $$, etc. only if colors are disabled (note: can be reverted if dark foreground colors are switched to light foreground colors, see comment in code)\r\n- Wall and \\\"next piece\\\" frame now have texture (i.e. light color foreground), helps not confusing the J piece (same color)\r\n- Made default speed slower, closer to official (similar to v0.4)\r\n- Can\\'t acheive infinite speed (i.e. break game) by holding +. Also, speeds grows 10 times faster when + is held (otherwise almost unnoticeable)","3":"This version is written by Felix Leger\r\n\r\nChangelog:\r\n- Shape rotations now match official Super Rotation System (SRS)\r\n- High scores don\\'t wrap around when displayed\r\n- First shape is now always random (instead of always being a bar)\r\n- Shapes\\' color scheme now matches official Tetris colors as closely as possible (since default terminal ANSI doesn\\'t support orange for L shape, that one is white instead\r\n- Since v0.5, colors are randomly attributed. Now each shape has its own color, like in official Tetris\r\n- Shapes now are homogeneously colored, we see MM, {}, $$, etc. only if colors are disabled (note: can be reverted if dark foreground colors are switched to light foreground colors, see comment in code)\r\n- Wall and \\\"next piece\\\" frame now have texture (i.e. light color foreground), helps not confusing the J piece (same color)\r\n- Made default speed slower, closer to official (similar to v0.4)\r\n- Can\\'t acheive infinite speed (i.e. break game) by holding +. Also, speeds grows 10 times faster when + is held (otherwise almost unnoticeable)","package":"TeTrIs.vim","4":"TeTrIs.vim","src_id":"24952","5":"24952","creation_date":"1486487346","6":"1486487346"},{"0":"172","vim_version":"6.0","1":"6.0","script_version":"0.52fix","2":"0.52fix","version_comment":"norm -> norm! to protect from M$-win's remappings","3":"norm -> norm! to protect from M$-win's remappings","package":"tetris.vim","4":"tetris.vim","src_id":"650","5":"650","creation_date":"1014804074","6":"1014804074"},{"0":"172","vim_version":"6.0","1":"6.0","script_version":"0.52","2":"0.52","version_comment":"Fixed massive slowdown when key pressed.\r\nFix up window positioning when ending and showing highscore.","3":"Fixed massive slowdown when key pressed.\r\nFix up window positioning when ending and showing highscore.","package":"tetris.vim","4":"tetris.vim","src_id":"619","5":"619","creation_date":"1014245689","6":"1014245689"},{"0":"172","vim_version":"6.0","1":"6.0","script_version":"0.51","2":"0.51","version_comment":"New timing, bug fixes, Name is stored in script-variable.","3":"New timing, bug fixes, Name is stored in script-variable.","package":"TeTrIs.vim","4":"TeTrIs.vim","src_id":"613","5":"613","creation_date":"1014101934","6":"1014101934"},{"0":"172","vim_version":"6.0","1":"6.0","script_version":"0.5","2":"0.5","version_comment":"New mode, top10, better colors, improved rotation, new timing, speedup, animations","3":"New mode, top10, better colors, improved rotation, new timing, speedup, animations","package":"TeTrIs.vim","4":"TeTrIs.vim","src_id":"589","5":"589","creation_date":"1013677433","6":"1013677433"},{"0":"172","vim_version":"6.0","1":"6.0","script_version":"0.4","2":"0.4","version_comment":"Colour, speeds, extra keys, the missing piece. Lotsa stuff.\r\n","3":"Colour, speeds, extra keys, the missing piece. Lotsa stuff.\r\n","package":"TeTrIs.vim","4":"TeTrIs.vim","src_id":"552","5":"552","creation_date":"1012860735","6":"1012860735"},{"0":"172","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"TeTrIs.vim","4":"TeTrIs.vim","src_id":"444","5":"444","creation_date":"1010049667","6":"1010049667"}]},"171":{"script_id":"171","0":"171","script_name":"multvals.vim","1":"multvals.vim","script_type":"utility","2":"utility","summary":"Array library that uses patterns as separators","3":"Array library that uses patterns as separators","description":"The new version requires Vim 6.3.\r\n\r\nThis is an array library useful for script developers.\r\n\r\nI started off from the lightWeightArray.vim script as a basis and created this\r\nmore complete script to call it an array. You can now manipulate the Vim's\r\nmulti-valued variables or create your own using this script. This makes it easy\r\nfor you to support variables having multiple values and familiar for the users\r\nof your script.\r\n\r\nSee file header for function prototypes.\r\n\r\n- An array is nothing but a string of multiple values separated by a\r\n  pattern.  The simplest example being Vim's multi-value variables such as\r\n  tags. You can use the MvAddElement() function to create an array.\r\n  However, there is nothing special about this function, you can as well\r\n  make up the string by simply concatinating elements with the chosen\r\n  pattern as a separator.\r\n- The separator can be any regular expression (which means that if you\r\n  want to use regex metacharacters in a non-regex pattern, then you need\r\n  to protect the metacharacters with backslashes). However, if a regular\r\n  expression is used as a separtor, you need to pass in a second separator,\r\n  which is a plain string that guarantees to match the separator regular\r\n  expression, as an additional argument (which was not the case with\r\n  earlier versions). When the array needs to be modified (which is\r\n  internally done by some of the reader functions also) this sample\r\n  separator is used to preserve the integrity of the array.\r\n- If you for example want to go over the words in a sentence, then an easy\r\n  way would be to treat the sentence as an array with '\\s\\+' as a\r\n  separator pattern. Be sure not to have zero-width expressions in the\r\n  pattern as these would otherwise confuse the plugin.\r\n- Suggested usage to go over the elements is to use the iterater functions\r\n  as shows in the below example\r\n  Ex Usage:\r\n    \" The below pattern avoids protected comma's from getting treated as\r\n    \"   separators.\r\n    call MvIterCreate(&tags, '\\\\\\@<!\\(\\\\\\\\\\)*\\zs,', 'Tags', ',')\r\n    while MvIterHasNext('Tags')\r\n      call input('Next element: ' . MvIterNext('Tags'))\r\n    endwhile\r\n    call MvIterDestroy('Tags')\r\n                                                                            \r\nALMOST ALL OPERATIONS TAKE THE ARRAY AND THE SEPARATOR AS THE FIRST TWO\r\n  ARGUMENTS.\r\nAll element-indexes start from 0 (like in C++ or Java).\r\nAll string-indexes start from 0 (as it is for Vim built-in functions).\r\n\r\n\r\n\r\nPlease let me know of any bugs and problems that you face.\r\n\r\n\r\nSearch_key_words: array arrays multvals sort multiple values multivals Hari Krishna Dara","4":"The new version requires Vim 6.3.\r\n\r\nThis is an array library useful for script developers.\r\n\r\nI started off from the lightWeightArray.vim script as a basis and created this\r\nmore complete script to call it an array. You can now manipulate the Vim's\r\nmulti-valued variables or create your own using this script. This makes it easy\r\nfor you to support variables having multiple values and familiar for the users\r\nof your script.\r\n\r\nSee file header for function prototypes.\r\n\r\n- An array is nothing but a string of multiple values separated by a\r\n  pattern.  The simplest example being Vim's multi-value variables such as\r\n  tags. You can use the MvAddElement() function to create an array.\r\n  However, there is nothing special about this function, you can as well\r\n  make up the string by simply concatinating elements with the chosen\r\n  pattern as a separator.\r\n- The separator can be any regular expression (which means that if you\r\n  want to use regex metacharacters in a non-regex pattern, then you need\r\n  to protect the metacharacters with backslashes). However, if a regular\r\n  expression is used as a separtor, you need to pass in a second separator,\r\n  which is a plain string that guarantees to match the separator regular\r\n  expression, as an additional argument (which was not the case with\r\n  earlier versions). When the array needs to be modified (which is\r\n  internally done by some of the reader functions also) this sample\r\n  separator is used to preserve the integrity of the array.\r\n- If you for example want to go over the words in a sentence, then an easy\r\n  way would be to treat the sentence as an array with '\\s\\+' as a\r\n  separator pattern. Be sure not to have zero-width expressions in the\r\n  pattern as these would otherwise confuse the plugin.\r\n- Suggested usage to go over the elements is to use the iterater functions\r\n  as shows in the below example\r\n  Ex Usage:\r\n    \" The below pattern avoids protected comma's from getting treated as\r\n    \"   separators.\r\n    call MvIterCreate(&tags, '\\\\\\@<!\\(\\\\\\\\\\)*\\zs,', 'Tags', ',')\r\n    while MvIterHasNext('Tags')\r\n      call input('Next element: ' . MvIterNext('Tags'))\r\n    endwhile\r\n    call MvIterDestroy('Tags')\r\n                                                                            \r\nALMOST ALL OPERATIONS TAKE THE ARRAY AND THE SEPARATOR AS THE FIRST TWO\r\n  ARGUMENTS.\r\nAll element-indexes start from 0 (like in C++ or Java).\r\nAll string-indexes start from 0 (as it is for Vim built-in functions).\r\n\r\n\r\n\r\nPlease let me know of any bugs and problems that you face.\r\n\r\n\r\nSearch_key_words: array arrays multvals sort multiple values multivals Hari Krishna Dara","install_details":"Source it from your .vimrc or just drop it in your plugin directory. \r\nSince version 2.1.1, you require Vim 6.0, for older versions you require Vim 5.6.\r\n\r\nSort functionality from version 2.4 requires genutils.vim: vimscript #197","5":"Source it from your .vimrc or just drop it in your plugin directory. \r\nSince version 2.1.1, you require Vim 6.0, for older versions you require Vim 5.6.\r\n\r\nSort functionality from version 2.4 requires genutils.vim: vimscript #197","first_name":"Hari Krishna","6":"Hari Krishna","last_name":"Dara","7":"Dara","releases":[{"0":"171","vim_version":"6.0","1":"6.0","script_version":"3.10","2":"3.10","version_comment":"- New MvBISortElements() that uses the faster BinInsertSort2() function\r\n  from genutils.vim plugin.\r\n","3":"- New MvBISortElements() that uses the faster BinInsertSort2() function\r\n  from genutils.vim plugin.\r\n","package":"multvals.vim","4":"multvals.vim","src_id":"3582","5":"3582","creation_date":"1098990862","6":"1098990862"},{"0":"171","vim_version":"6.0","1":"6.0","script_version":"3.9","2":"3.9","version_comment":"- MvIterPeek made public. This was left private by accident.","3":"- MvIterPeek made public. This was left private by accident.","package":"multvals.vim","4":"multvals.vim","src_id":"3566","5":"3566","creation_date":"1098292712","6":"1098292712"},{"0":"171","vim_version":"6.0","1":"6.0","script_version":"3.8","2":"3.8","version_comment":"Fixed bugs in the *StrIndex* functions, such that when the element is\r\nnot found, they always return the contracted -1 (instead of any -ve\r\nvalue). This will fix problems with a number of other functions that\r\ndepend on them (such as MvPushToFront reported by Thomas Link).\r\n","3":"Fixed bugs in the *StrIndex* functions, such that when the element is\r\nnot found, they always return the contracted -1 (instead of any -ve\r\nvalue). This will fix problems with a number of other functions that\r\ndepend on them (such as MvPushToFront reported by Thomas Link).\r\n","package":"multvals.vim","4":"multvals.vim","src_id":"3482","5":"3482","creation_date":"1096021587","6":"1096021587"},{"0":"171","vim_version":"6.0","1":"6.0","script_version":"3.6","2":"3.6","version_comment":"Maintenance release.\r\n- Work-around for a bug in MvNumberOfElements().\r\n- New utility function MvCrUnProtectedCharsPattern()\r\n","3":"Maintenance release.\r\n- Work-around for a bug in MvNumberOfElements().\r\n- New utility function MvCrUnProtectedCharsPattern()\r\n","package":"multvals.vim","4":"multvals.vim","src_id":"3147","5":"3147","creation_date":"1087567985","6":"1087567985"},{"0":"171","vim_version":"6.0","1":"6.0","script_version":"3.5","2":"3.5","version_comment":"CAUTION: This version potentially introduces an incompatibility with that of\r\nolder versions because of the below change. If your plugin depended on this\r\nundocumented behavior you will have to update your plugin immediately to work\r\nwith the new plugin. Even if you didn't know about behavior, it is still better\r\nto check if your plugin accidentally depended on this. If you need further\r\nclarifications, please email me with your questions and I will try to answer.\r\n\r\n- Now the plugin ignores the 'ignorecase' and 'smartcase' settings, so the\r\n  results are more consistent. This I think is the right thing to do for a\r\n  library.\r\n- Also added a new function MvIterPeek.\r\n","3":"CAUTION: This version potentially introduces an incompatibility with that of\r\nolder versions because of the below change. If your plugin depended on this\r\nundocumented behavior you will have to update your plugin immediately to work\r\nwith the new plugin. Even if you didn't know about behavior, it is still better\r\nto check if your plugin accidentally depended on this. If you need further\r\nclarifications, please email me with your questions and I will try to answer.\r\n\r\n- Now the plugin ignores the 'ignorecase' and 'smartcase' settings, so the\r\n  results are more consistent. This I think is the right thing to do for a\r\n  library.\r\n- Also added a new function MvIterPeek.\r\n","package":"multvals.vim","4":"multvals.vim","src_id":"2852","5":"2852","creation_date":"1079982824","6":"1079982824"},{"0":"171","vim_version":"6.0","1":"6.0","script_version":"3.4","2":"3.4","version_comment":"- The plugin was not working correctly when there are *'s in the array.\r\n- New function MvRemovePatternAll\r\n- g:loaded_multvals now contains the version number for dependency cheking.\r\n  (see \":help v:version\" for format)\r\n- Added prototypes for the functions in the header as per the suggestion\r\n  of Naveen Chandra.","3":"- The plugin was not working correctly when there are *'s in the array.\r\n- New function MvRemovePatternAll\r\n- g:loaded_multvals now contains the version number for dependency cheking.\r\n  (see \":help v:version\" for format)\r\n- Added prototypes for the functions in the header as per the suggestion\r\n  of Naveen Chandra.","package":"multvals.vim","4":"multvals.vim","src_id":"2607","5":"2607","creation_date":"1071684899","6":"1071684899"},{"0":"171","vim_version":"6.0","1":"6.0","script_version":"3.3","2":"3.3","version_comment":"Minor changes, added a new function MvElementLike and improved MvPromptForElement by adding a new companion function MvGetSelectedIndex, to be used when the array can contain empty elements.","3":"Minor changes, added a new function MvElementLike and improved MvPromptForElement by adding a new companion function MvGetSelectedIndex, to be used when the array can contain empty elements.","package":"multvals.vim","4":"multvals.vim","src_id":"2262","5":"2262","creation_date":"1061821467","6":"1061821467"},{"0":"171","vim_version":"6.0","1":"6.0","script_version":"3.2","2":"3.2","version_comment":"New function MvNumSearchNext. See the function header for details.\r\n","3":"New function MvNumSearchNext. See the function header for details.\r\n","package":"multvals.vim","4":"multvals.vim","src_id":"2063","5":"2063","creation_date":"1055353605","6":"1055353605"},{"0":"171","vim_version":"6.0","1":"6.0","script_version":"3.1","2":"3.1","version_comment":"Minor changes. Now the MvCreateIter() also accepts sample separator as the last argument when a regular expression is used as a separator. This is consistent with the rest of the functions and makes it easy to iterate over settings like 'tags'.\r\n\r\ncall MvIterCreate(&tags, \"\\\\\\@<!\\(\\\\\\\\\\)*\\zs,\", \"Tags\", ',')\r\n\r\n","3":"Minor changes. Now the MvCreateIter() also accepts sample separator as the last argument when a regular expression is used as a separator. This is consistent with the rest of the functions and makes it easy to iterate over settings like 'tags'.\r\n\r\ncall MvIterCreate(&tags, \"\\\\\\@<!\\(\\\\\\\\\\)*\\zs,\", \"Tags\", ',')\r\n\r\n","package":"multvals.vim","4":"multvals.vim","src_id":"1873","5":"1873","creation_date":"1048875616","6":"1048875616"},{"0":"171","vim_version":"6.0","1":"6.0","script_version":"3.0","2":"3.0","version_comment":"- All functions can now be used with regular expressions as separators. Most of the functions now accept an optional extra argument as the last argument, which needs to be a plain separator as a sample that matches the regular expression of the separator. If the separator is not a regular expressions, this can be ignored, making it backwardly compatible change.\r\n- Added new functions MvRemovePattern, MvStrIndexOfPattern, MvStrIndexAfterPattern, MvIndexOfPattern, MvContainsPattern.\r\n- Fixed a bug in the new implementation of MvPromptForElement. This function now accepts only element index as selection. This makes it cleaner to implement and also makes it possible to have even numbers as values in the array.\r\n","3":"- All functions can now be used with regular expressions as separators. Most of the functions now accept an optional extra argument as the last argument, which needs to be a plain separator as a sample that matches the regular expression of the separator. If the separator is not a regular expressions, this can be ignored, making it backwardly compatible change.\r\n- Added new functions MvRemovePattern, MvStrIndexOfPattern, MvStrIndexAfterPattern, MvIndexOfPattern, MvContainsPattern.\r\n- Fixed a bug in the new implementation of MvPromptForElement. This function now accepts only element index as selection. This makes it cleaner to implement and also makes it possible to have even numbers as values in the array.\r\n","package":"multvals.vim","4":"multvals.vim","src_id":"1582","5":"1582","creation_date":"1040921218","6":"1040921218"},{"0":"171","vim_version":"6.0","1":"6.0","script_version":"2.5","2":"2.5","version_comment":"Just removed some debug echomsg which I forgot to remove. Sorry about it. I also added some more information on how to use MvQSortElements() method.","3":"Just removed some debug echomsg which I forgot to remove. Sorry about it. I also added some more information on how to use MvQSortElements() method.","package":"multvals.vim","4":"multvals.vim","src_id":"1532","5":"1532","creation_date":"1039105349","6":"1039105349"},{"0":"171","vim_version":"6.0","1":"6.0","script_version":"2.4","2":"2.4","version_comment":"- New functions MvQSortElements() and MvSwapElementsAt(). Requires genutils.vim\r\n  for sorting support.\r\n- Worked-around a bug in vim that effects MvElementAt() for last element in a\r\n  large array. \r\n- A variant of MvPromptForElement to specify the number of columns that you\r\n  want the elements to be formatted in. The formatting is very nice now.\r\n","3":"- New functions MvQSortElements() and MvSwapElementsAt(). Requires genutils.vim\r\n  for sorting support.\r\n- Worked-around a bug in vim that effects MvElementAt() for last element in a\r\n  large array. \r\n- A variant of MvPromptForElement to specify the number of columns that you\r\n  want the elements to be formatted in. The formatting is very nice now.\r\n","package":"multvals.vim","4":"multvals.vim","src_id":"1492","5":"1492","creation_date":"1038317880","6":"1038317880"},{"0":"171","vim_version":"6.0","1":"6.0","script_version":"2.3","2":"2.3","version_comment":"GPL'ed it mainly for the use by Creme project (http:\/\/cream.sf.net). Added MvRemoveElementAll and MvReplaceElementAt, contributed by Steve Hall <digitect at mindspring.com>","3":"GPL'ed it mainly for the use by Creme project (http:\/\/cream.sf.net). Added MvRemoveElementAll and MvReplaceElementAt, contributed by Steve Hall <digitect at mindspring.com>","package":"multvals.vim","4":"multvals.vim","src_id":"939","5":"939","creation_date":"1024656068","6":"1024656068"},{"0":"171","vim_version":"6.0","1":"6.0","script_version":"2.1.2","2":"2.1.2","version_comment":"More robust iterator, now checks for maximum count. Reimplemented it to use the ElementAt() function and removed NextElement and NextIndex() functions that are not needed.","3":"More robust iterator, now checks for maximum count. Reimplemented it to use the ElementAt() function and removed NextElement and NextIndex() functions that are not needed.","package":"multvals.vim","4":"multvals.vim","src_id":"642","5":"642","creation_date":"1014673645","6":"1014673645"},{"0":"171","vim_version":"6.0","1":"6.0","script_version":"2.1.1","2":"2.1.1","version_comment":"New functions MvRotateLeftAt() and MvRotateRight() to be used by the PushPop.vim script.","3":"New functions MvRotateLeftAt() and MvRotateRight() to be used by the PushPop.vim script.","package":"multvals.vim","4":"multvals.vim","src_id":"575","5":"575","creation_date":"1013378961","6":"1013378961"},{"0":"171","vim_version":"6.0","1":"6.0","script_version":"2.1.1","2":"2.1.1","version_comment":"Enhanced the script to accept any regular expression as a separator pattern, but it works only for read-only operations. Now you can treat the following as an array:\r\n\r\naxxbxxxxcxdxxxxxe\r\n\r\nand access a, b, c, d and e as array elements.\r\n\r\nNow the element is escaped before using in the matches, so you shouldn't have any problem using any random strings to store in to the array.\r\n\r\nAlso the script is now made as a plugin, so it works only 6.0","3":"Enhanced the script to accept any regular expression as a separator pattern, but it works only for read-only operations. Now you can treat the following as an array:\r\n\r\naxxbxxxxcxdxxxxxe\r\n\r\nand access a, b, c, d and e as array elements.\r\n\r\nNow the element is escaped before using in the matches, so you shouldn't have any problem using any random strings to store in to the array.\r\n\r\nAlso the script is now made as a plugin, so it works only 6.0","package":"multvals.vim","4":"multvals.vim","src_id":"571","5":"571","creation_date":"1013178479","6":"1013178479"},{"0":"171","vim_version":"6.0","1":"6.0","script_version":"2.0.5","2":"2.0.5","version_comment":"Fixed bugs in MvStrIndexOfElement(), MvIterHasNext() and MvCmpByPosition(). Now I have been using the script for quite some time and fixed all the bugs that I discovered. It should be quite robust and usable now. I have used the functions from here in selectbuf.vim for implementing MRU listing and also in the remcmd.vim for list selection, so check these scripts for a good usage. Also see the end of the script for test code that gives example usage of the script.","3":"Fixed bugs in MvStrIndexOfElement(), MvIterHasNext() and MvCmpByPosition(). Now I have been using the script for quite some time and fixed all the bugs that I discovered. It should be quite robust and usable now. I have used the functions from here in selectbuf.vim for implementing MRU listing and also in the remcmd.vim for list selection, so check these scripts for a good usage. Also see the end of the script for test code that gives example usage of the script.","package":"multvals.vim","4":"multvals.vim","src_id":"525","5":"525","creation_date":"1012588334","6":"1012588334"},{"0":"171","vim_version":"6.0","1":"6.0","script_version":"2.0.4","2":"2.0.4","version_comment":"Lots of new functions are added and they are documented well. Now the script has functions to access the elements by element index, just like a real array. Much more usable as an array than previously it was.\r\n\r\n However, it is incompatible with the previous version for the following reasons:\r\n   - Prefixed all the global functions with \"Mv\" to avoid global name\r\n       conflicts.\r\n   - The order of arguments for MvIterCreate has been changed for the sake of\r\n       consistency.\r\n\r\nHere is a list of all the functions:\r\n       MvAddElement\r\n       MvInsertElementAt\r\n       MvRemoveElement\r\n       MvRemoveElementAt\r\n       MvNumberOfElements\r\n       MvStrIndexOfElement\r\n       MvStrIndexOfElementAt\r\n       MvIndexOfElement\r\n       MvContainsElement\r\n       MvElementAt\r\n       MvLastElement\r\n       MvPushToFront\r\n       MvPushToFrontElementAt\r\n       MvPullToBack\r\n       MvPullToBackElementAt\r\n       MvIterCreate\r\n       MvIterDestroy\r\n       MvIterHasNext\r\n       MvIterNext\r\n       MvCmpByPosition\r\n       MvPromptForElement\r\n","3":"Lots of new functions are added and they are documented well. Now the script has functions to access the elements by element index, just like a real array. Much more usable as an array than previously it was.\r\n\r\n However, it is incompatible with the previous version for the following reasons:\r\n   - Prefixed all the global functions with \"Mv\" to avoid global name\r\n       conflicts.\r\n   - The order of arguments for MvIterCreate has been changed for the sake of\r\n       consistency.\r\n\r\nHere is a list of all the functions:\r\n       MvAddElement\r\n       MvInsertElementAt\r\n       MvRemoveElement\r\n       MvRemoveElementAt\r\n       MvNumberOfElements\r\n       MvStrIndexOfElement\r\n       MvStrIndexOfElementAt\r\n       MvIndexOfElement\r\n       MvContainsElement\r\n       MvElementAt\r\n       MvLastElement\r\n       MvPushToFront\r\n       MvPushToFrontElementAt\r\n       MvPullToBack\r\n       MvPullToBackElementAt\r\n       MvIterCreate\r\n       MvIterDestroy\r\n       MvIterHasNext\r\n       MvIterNext\r\n       MvCmpByPosition\r\n       MvPromptForElement\r\n","package":"multvals.vim","4":"multvals.vim","src_id":"467","5":"467","creation_date":"1010779665","6":"1010779665"},{"0":"171","vim_version":"5.7","1":"5.7","script_version":"2.0.2","2":"2.0.2","version_comment":"Initial upload","3":"Initial upload","package":"multvals.vim","4":"multvals.vim","src_id":"443","5":"443","creation_date":"1009982336","6":"1009982336"}]},"170":{"script_id":"170","0":"170","script_name":"mcant.vim","1":"mcant.vim","script_type":"ftplugin","2":"ftplugin","summary":"a minimalist vim+ant configuration","3":"a minimalist vim+ant configuration","description":"Submitted in response to ant.vim, this 1 liner is all I've ever needed to be completely happy and efficient with ant and vim. All the benefits of vim error parsing, with no configuration or other fiddling required.\n\nIf you don't feel like downloading the script, just put this in your .vimrc file:\n\nset makeprg=ant\\ -quiet\\ -emacs\\ -find\\ build.xml ","4":"Submitted in response to ant.vim, this 1 liner is all I've ever needed to be completely happy and efficient with ant and vim. All the benefits of vim error parsing, with no configuration or other fiddling required.\n\nIf you don't feel like downloading the script, just put this in your .vimrc file:\n\nset makeprg=ant\\ -quiet\\ -emacs\\ -find\\ build.xml ","install_details":"Drop into your plugin directory (~\/.vim\/plugin)\n\n","5":"Drop into your plugin directory (~\/.vim\/plugin)\n\n","first_name":"mcclain","6":"mcclain","last_name":"looney","7":"looney","releases":[{"0":"170","vim_version":"6.0","1":"6.0","script_version":"1","2":"1","version_comment":"Initial upload","3":"Initial upload","package":"mcant.vim","4":"mcant.vim","src_id":"442","5":"442","creation_date":"1009968379","6":"1009968379"}]},"169":{"script_id":"169","0":"169","script_name":"email.vim","1":"email.vim","script_type":"utility","2":"utility","summary":"Email auto-completion for vim. It\\'s simple, clean and useful :)","3":"Email auto-completion for vim. It\\'s simple, clean and useful :)","description":"Just as the name implies, this script will add auto-complete functionality for email addresses in vim. This is very handy for those who use vim with mutt. Enjoy.\r\n\r\nFor those of you who would rather just look at the code through your browser:\r\nhttp:\/\/www.itodd.org\/~itodd\/email.vim\r\n\r\nThanks to Luc Hermitte for writing a much more advanced autocomplete script [ vimscript #46 ] which helped me create this one.\r\n\r\n-- \r\nTodd Boland\r\nhttp:\/\/www.itodd.org\/\r\n\r\n:wq","4":"Just as the name implies, this script will add auto-complete functionality for email addresses in vim. This is very handy for those who use vim with mutt. Enjoy.\r\n\r\nFor those of you who would rather just look at the code through your browser:\r\nhttp:\/\/www.itodd.org\/~itodd\/email.vim\r\n\r\nThanks to Luc Hermitte for writing a much more advanced autocomplete script [ vimscript #46 ] which helped me create this one.\r\n\r\n-- \r\nTodd Boland\r\nhttp:\/\/www.itodd.org\/\r\n\r\n:wq","install_details":"Note: This script depends on the following basic unix tools: grep, sort, uniq, wc and xargs. Feel free to hack it up for other OSs\r\n\r\nFirst create a ~\/.addresses file. In this file put a list of addresses separated by new lines. Duplicates will be automatically ignored.\r\n\r\nLoad the script:\r\n:source \/path\/to\/email.vim\r\n\r\nIf you'd like the script to automatically load when editing a mutt email, add the following line to your ~\/vimrc:\r\nau BufRead \/tmp\/mutt* source \/path\/to\/email.vim\r\n\r\nThen on a new line type:\r\nTo: start_of_emai<tab>\r\n\r\nwhere \"start_of_emai\" is the begining of an email address listed in ~\/.addresses","5":"Note: This script depends on the following basic unix tools: grep, sort, uniq, wc and xargs. Feel free to hack it up for other OSs\r\n\r\nFirst create a ~\/.addresses file. In this file put a list of addresses separated by new lines. Duplicates will be automatically ignored.\r\n\r\nLoad the script:\r\n:source \/path\/to\/email.vim\r\n\r\nIf you'd like the script to automatically load when editing a mutt email, add the following line to your ~\/vimrc:\r\nau BufRead \/tmp\/mutt* source \/path\/to\/email.vim\r\n\r\nThen on a new line type:\r\nTo: start_of_emai<tab>\r\n\r\nwhere \"start_of_emai\" is the begining of an email address listed in ~\/.addresses","first_name":"Todd","6":"Todd","last_name":"Boland","7":"Boland","releases":[{"0":"169","vim_version":"6.0","1":"6.0","script_version":"1.02","2":"1.02","version_comment":"Small update to add support for Reply-To: and From: lines.","3":"Small update to add support for Reply-To: and From: lines.","package":"email.vim","4":"email.vim","src_id":"437","5":"437","creation_date":"1009193052","6":"1009193052"},{"0":"169","vim_version":"6.0","1":"6.0","script_version":"1.01","2":"1.01","version_comment":"Never release code at 3am. Fixed some bugs and optimized.","3":"Never release code at 3am. Fixed some bugs and optimized.","package":"email.vim","4":"email.vim","src_id":"435","5":"435","creation_date":"1008941601","6":"1008941601"},{"0":"169","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"email.vim","4":"email.vim","src_id":"432","5":"432","creation_date":"1008891241","6":"1008891241"}]},"168":{"script_id":"168","0":"168","script_name":"idevim.tgz","1":"idevim.tgz","script_type":"utility","2":"utility","summary":"Control Gdb from inside Vim","3":"Control Gdb from inside Vim","description":" Vim is the best editor in the world, and gdb the best debugger. Try to imagine the integration of both. Well, let me just say that if God had this tool when he wrote the world, this would have been a better place.\r\n\r\n Idevim also features an Assembley debugger, and other features like Automatic Core Dump detection etc. All in all, it is the best IDE for a Vim fan.","4":" Vim is the best editor in the world, and gdb the best debugger. Try to imagine the integration of both. Well, let me just say that if God had this tool when he wrote the world, this would have been a better place.\r\n\r\n Idevim also features an Assembley debugger, and other features like Automatic Core Dump detection etc. All in all, it is the best IDE for a Vim fan.","install_details":"untar and do a make install.","5":"untar and do a make install.","first_name":"K T","6":"K T","last_name":"ligesh","7":"ligesh","releases":[{"0":"168","vim_version":"6.0","1":"6.0","script_version":"0.8","2":"0.8","version_comment":"Initial upload","3":"Initial upload","package":"idevim.tgz","4":"idevim.tgz","src_id":"428","5":"428","creation_date":"1008617614","6":"1008617614"}]},"167":{"script_id":"167","0":"167","script_name":"perforce.vim","1":"perforce.vim","script_type":"utility","2":"utility","summary":"Perforce source control features","3":"Perforce source control features","description":"Perforce is a source control system from http:\/\/www.perforce.com\r\n\r\nFeatures:\r\n- menu and keyboard shortcuts to open (checkout), revert, and sync files.\r\n- prompts to open a file for editing when you attempt to change a checked-in file.\r\n- perforce status displayed on the ruler.\r\n- tested on Windows operating systems only.\r\n\r\nThis plugin provides a relatively few commonly used commands. If you are looking for the ability to carry out many perforce commands from within vim, you may wish to look at  Hari Krishna Dara's plugin (script 240)  at http:\/\/vim.sourceforge.net\/scripts\/script.php?script_id=240.","4":"Perforce is a source control system from http:\/\/www.perforce.com\r\n\r\nFeatures:\r\n- menu and keyboard shortcuts to open (checkout), revert, and sync files.\r\n- prompts to open a file for editing when you attempt to change a checked-in file.\r\n- perforce status displayed on the ruler.\r\n- tested on Windows operating systems only.\r\n\r\nThis plugin provides a relatively few commonly used commands. If you are looking for the ability to carry out many perforce commands from within vim, you may wish to look at  Hari Krishna Dara's plugin (script 240)  at http:\/\/vim.sourceforge.net\/scripts\/script.php?script_id=240.","install_details":"Place in your vimfiles\\plugin directory.\r\nSet p4editor=vim -c PerforceLaunch for use as p4 forms editor.","5":"Place in your vimfiles\\plugin directory.\r\nSet p4editor=vim -c PerforceLaunch for use as p4 forms editor.","first_name":"Tom","6":"Tom","last_name":"Slee","7":"Slee","releases":[{"0":"167","vim_version":"7.0","1":"7.0","script_version":"0.5","2":"0.5","version_comment":"Extensive enhancements by Suresh Srinivasan:\r\n\r\nAdded a set of changelist commands ('\\' indicates the leader character):\r\n \r\n    \\v - Show list of versions of the file.\r\n    \\u - Show unified diff of the file.\r\n    \\z - Show diff between specific versions of the file.\r\n    \\p - Show depot version of file.\r\n    \\a - Show depot version of file with annotations (revision# for each line).\r\n    \\x - Mark file for delete.\r\n \r\n    \\C - Create new changelist.\r\n    \\D - Show diff of all files in a changelist.\r\n    \\F - Show list of files in a changelist.\r\n    \\L - Show list of pending changelists.\r\n    \\X - Delete a changelist.\r\n    \\S - Submit current changelist.\r\n    \\I - Show changelist info.\r\n \r\n    \\h - Show Help message.\r\n    \\l - Login into perforce.\r\n    \\\\ - Show general perforce info (license, location, etc.).\r\n \r\nStatus line message now includes the changelist number.","3":"Extensive enhancements by Suresh Srinivasan:\r\n\r\nAdded a set of changelist commands ('\\' indicates the leader character):\r\n \r\n    \\v - Show list of versions of the file.\r\n    \\u - Show unified diff of the file.\r\n    \\z - Show diff between specific versions of the file.\r\n    \\p - Show depot version of file.\r\n    \\a - Show depot version of file with annotations (revision# for each line).\r\n    \\x - Mark file for delete.\r\n \r\n    \\C - Create new changelist.\r\n    \\D - Show diff of all files in a changelist.\r\n    \\F - Show list of files in a changelist.\r\n    \\L - Show list of pending changelists.\r\n    \\X - Delete a changelist.\r\n    \\S - Submit current changelist.\r\n    \\I - Show changelist info.\r\n \r\n    \\h - Show Help message.\r\n    \\l - Login into perforce.\r\n    \\\\ - Show general perforce info (license, location, etc.).\r\n \r\nStatus line message now includes the changelist number.","package":"perforce.vim","4":"perforce.vim","src_id":"7283","5":"7283","creation_date":"1182428272","6":"1182428272"},{"0":"167","vim_version":"6.0","1":"6.0","script_version":"0.4","2":"0.4","version_comment":"Useful enhancements made by Terrance Cohen:\r\n\r\n- Added P4DiffFile() option\r\n- \"[Not in p4]\" appears on ruler instead of \"0\"\r\n- Added defaults to confirmation dialogs so user can just hit enter or \r\nescape... no need to find a hotkey. Revert defaults to 'No', others \r\ndefault to 'Yes'.\r\n- Changed icons in confirmation dialogs to question\r\n- Rephrased confirmation texts to make them easier to parse quickly","3":"Useful enhancements made by Terrance Cohen:\r\n\r\n- Added P4DiffFile() option\r\n- \"[Not in p4]\" appears on ruler instead of \"0\"\r\n- Added defaults to confirmation dialogs so user can just hit enter or \r\nescape... no need to find a hotkey. Revert defaults to 'No', others \r\ndefault to 'Yes'.\r\n- Changed icons in confirmation dialogs to question\r\n- Rephrased confirmation texts to make them easier to parse quickly","package":"perforce.vim","4":"perforce.vim","src_id":"2325","5":"2325","creation_date":"1063289493","6":"1063289493"},{"0":"167","vim_version":"6.0","1":"6.0","script_version":"0.3","2":"0.3","version_comment":"- fixed bug where cursor position within a line was not always maintained across p4 operations on the file.\r\n- sped up \"p4 edit\" operation -- it now uses two shell commands instead of three.","3":"- fixed bug where cursor position within a line was not always maintained across p4 operations on the file.\r\n- sped up \"p4 edit\" operation -- it now uses two shell commands instead of three.","package":"perforce.vim","4":"perforce.vim","src_id":"475","5":"475","creation_date":"1011075695","6":"1011075695"},{"0":"167","vim_version":"6.0","1":"6.0","script_version":"0.2","2":"0.2","version_comment":"Initial upload","3":"Initial upload","package":"perforce.vim","4":"perforce.vim","src_id":"422","5":"422","creation_date":"1008242722","6":"1008242722"}]},"166":{"script_id":"166","0":"166","script_name":"libList.vim","1":"libList.vim","script_type":"utility","2":"utility","summary":"Library of functions to work with lists\/arrays","3":"Library of functions to work with lists\/arrays","description":"libList.vim is a set of functions to work with lists or one level arrays.\r\r\n\r\r\nLists are strings variables with values separated by g:listSep character (comma by default). You may redefine g:listSep variable as you wish.\r\r\n\r\r\nHere are available functions :\r\r\n\r\r\n- AddListItem( array, newItem, index ) : Add item \"newItem\" to array \"array\" at \"index\" position\r\r\n- GetListItem( array, index ) : Return item at \"index\" position in array \"array\"\r\r\n- GetListMatchItem( array, pattern ) : Return item matching \"pattern\" in array \"array\"\r\r\n- GetListCount( array ) : Return the number of items in array \"array\"\r\r\n- RemoveListItem( array, index ) : Remove item at \"index\" position from array \"array\"\r\r\n- ReplaceListItem( array, index, item ) : Remove item at \"index\" position by \"item\" in array \"array\"\r\r\n- ExchangeListItems( array, item1Index, item2Index ) : Exchange item \"item1Index\" with item \"item2Index\" in array \"array\"\r\r\n- QuickSortList( array, beg, end ) : Return array \"array\" with items between \"beg\" and \"end\" sorted\r\r\n\r\r\nExample:\r\r\nlet mylist=\"\"\r\r\necho GetListCount( mylist ) \" --> 0\r\r\nlet mylist = AddListItem( mylist, \"One\", 0 ) \" mylist == \"One\"\r\r\nlet mylist = AddListItem( mylist, \"Three\", 1 ) \" mylist == \"One,Three\"\r\r\nlet mylist = AddListItem( mylist, \"Two\", 1 ) \" mylist == \"One,Two,Three\"\r\r\necho GetListCount( mylist ) \" --> 3\r\r\necho GetListItem( mylist, 2 ) \" --> Three\r\r\necho GetListMatchItem( mylist, \"w\" ) \" --> two\r\r\necho GetListMatchItem( mylist, \"e\" ) \" --> One\r\r\nlet mylist = RemoveListItem( mylist, 2 ) \" mylist == \"One,Two\"\r\r\necho GetListCount( mylist ) \" --> 2\r\r\nlet mylist = ReplaceListItem( mylist, 0, \"Three\" ) \" mylist == \"Three,Two\"\r\r\nlet mylist = ExchangeListItems( mylist, 0, 1 ) \" mylist == \"Two,Three\"\r\r\nlet mylist = AddListItem( mylist, \"One\", 0 ) \" mylist == \"One,Two,Three\"\r\r\nlet mylist = QuickSortList( mylist, 0, GetListCount(mylist)-1 ) \" mylist == \"One,Three,Two\"","4":"libList.vim is a set of functions to work with lists or one level arrays.\r\r\n\r\r\nLists are strings variables with values separated by g:listSep character (comma by default). You may redefine g:listSep variable as you wish.\r\r\n\r\r\nHere are available functions :\r\r\n\r\r\n- AddListItem( array, newItem, index ) : Add item \"newItem\" to array \"array\" at \"index\" position\r\r\n- GetListItem( array, index ) : Return item at \"index\" position in array \"array\"\r\r\n- GetListMatchItem( array, pattern ) : Return item matching \"pattern\" in array \"array\"\r\r\n- GetListCount( array ) : Return the number of items in array \"array\"\r\r\n- RemoveListItem( array, index ) : Remove item at \"index\" position from array \"array\"\r\r\n- ReplaceListItem( array, index, item ) : Remove item at \"index\" position by \"item\" in array \"array\"\r\r\n- ExchangeListItems( array, item1Index, item2Index ) : Exchange item \"item1Index\" with item \"item2Index\" in array \"array\"\r\r\n- QuickSortList( array, beg, end ) : Return array \"array\" with items between \"beg\" and \"end\" sorted\r\r\n\r\r\nExample:\r\r\nlet mylist=\"\"\r\r\necho GetListCount( mylist ) \" --> 0\r\r\nlet mylist = AddListItem( mylist, \"One\", 0 ) \" mylist == \"One\"\r\r\nlet mylist = AddListItem( mylist, \"Three\", 1 ) \" mylist == \"One,Three\"\r\r\nlet mylist = AddListItem( mylist, \"Two\", 1 ) \" mylist == \"One,Two,Three\"\r\r\necho GetListCount( mylist ) \" --> 3\r\r\necho GetListItem( mylist, 2 ) \" --> Three\r\r\necho GetListMatchItem( mylist, \"w\" ) \" --> two\r\r\necho GetListMatchItem( mylist, \"e\" ) \" --> One\r\r\nlet mylist = RemoveListItem( mylist, 2 ) \" mylist == \"One,Two\"\r\r\necho GetListCount( mylist ) \" --> 2\r\r\nlet mylist = ReplaceListItem( mylist, 0, \"Three\" ) \" mylist == \"Three,Two\"\r\r\nlet mylist = ExchangeListItems( mylist, 0, 1 ) \" mylist == \"Two,Three\"\r\r\nlet mylist = AddListItem( mylist, \"One\", 0 ) \" mylist == \"One,Two,Three\"\r\r\nlet mylist = QuickSortList( mylist, 0, GetListCount(mylist)-1 ) \" mylist == \"One,Three,Two\"","install_details":"Put this file in your plugins directory, and all functions will be available for other scripts.","5":"Put this file in your plugins directory, and all functions will be available for other scripts.","first_name":"Gontran","6":"Gontran","last_name":"BAERTS","7":"BAERTS","releases":[{"0":"166","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"libList.vim","4":"libList.vim","src_id":"421","5":"421","creation_date":"1008234626","6":"1008234626"}]},"165":{"script_id":"165","0":"165","script_name":"vimsh.tar.gz","1":"vimsh.tar.gz","script_type":"utility","2":"utility","summary":"terminal\/shell buffer script for python enabled [g]vim","3":"terminal\/shell buffer script for python enabled [g]vim","description":"A terminal\/shell buffer script for python enabled [g]vim (+python).  Allows execution of shell commands in a vim buffer.\r\nIt does not use r! <cmd>.  \r\n\r\nSome of it's features:\r\n\r\n* It retains state because it's interactive.  Set an environment variable and it \"stays\" because the shell process is the same through the whole session.\r\n* It can run interactive line based programs like ftp\/telnet\/python\/ssh\/etc including masked password input (pty supported platform only).\r\n* Since it's a vim buffer you can go into normal mode and move around the buffer, yank, paste, use word completion, etc.\r\n* Runs on Linux, OS X, Windows, and other UNIX platforms.  Primary development and testing is done on Linux.  Windows has limitations (no interactive programs or Ctrl-C) due to lack of pty support.\r\n       \r\nRequirements:\r\nTo use it you must have a python enabled [g]vim and run on a platform that supports pty (i.e. Linux, OS X),\r\nor pipes (Windows). The pty version has much better formatted output than the pipes\r\nversion and supports running interactive programs.  Please read the README for other installation\r\nand configuration details.  Tested on vim 6.0\/7.x using Slackware, Ubuntu, and Gentoo Linux, FreeBSD, Mac OS X, and Windows XP\/Vista.  \r\n\r\nI'd also like to hear from users running other operating systems, i.e. QNX\/Solaris\/other BSDs.\r\n\r\n!!!!! WINDOWS USERS !!!!!, there is a zip file available at the below link. The version\r\nkept here on vimonline is a tarred, gzipped file ( tar.gz ). If you are going to use\r\nWinzip with the .tar.gz file be sure to turn off the \"Tar file smart CR\/LF handling\". It doesn't work\r\nwell.\r\n\r\nPlease send me bug reports and suggestions if you use it.  I appreciate all the patches\r\nI've been getting lately!\r\n\r\nVisit:\r\n\r\n    http:\/\/www.briansturk.com\/vim.html\r\n\r\nSee \"terminal buffer\" for more information.  There is also a (old) screenshot\r\nof it running on Slackware Linux and Vim 6.0.","4":"A terminal\/shell buffer script for python enabled [g]vim (+python).  Allows execution of shell commands in a vim buffer.\r\nIt does not use r! <cmd>.  \r\n\r\nSome of it's features:\r\n\r\n* It retains state because it's interactive.  Set an environment variable and it \"stays\" because the shell process is the same through the whole session.\r\n* It can run interactive line based programs like ftp\/telnet\/python\/ssh\/etc including masked password input (pty supported platform only).\r\n* Since it's a vim buffer you can go into normal mode and move around the buffer, yank, paste, use word completion, etc.\r\n* Runs on Linux, OS X, Windows, and other UNIX platforms.  Primary development and testing is done on Linux.  Windows has limitations (no interactive programs or Ctrl-C) due to lack of pty support.\r\n       \r\nRequirements:\r\nTo use it you must have a python enabled [g]vim and run on a platform that supports pty (i.e. Linux, OS X),\r\nor pipes (Windows). The pty version has much better formatted output than the pipes\r\nversion and supports running interactive programs.  Please read the README for other installation\r\nand configuration details.  Tested on vim 6.0\/7.x using Slackware, Ubuntu, and Gentoo Linux, FreeBSD, Mac OS X, and Windows XP\/Vista.  \r\n\r\nI'd also like to hear from users running other operating systems, i.e. QNX\/Solaris\/other BSDs.\r\n\r\n!!!!! WINDOWS USERS !!!!!, there is a zip file available at the below link. The version\r\nkept here on vimonline is a tarred, gzipped file ( tar.gz ). If you are going to use\r\nWinzip with the .tar.gz file be sure to turn off the \"Tar file smart CR\/LF handling\". It doesn't work\r\nwell.\r\n\r\nPlease send me bug reports and suggestions if you use it.  I appreciate all the patches\r\nI've been getting lately!\r\n\r\nVisit:\r\n\r\n    http:\/\/www.briansturk.com\/vim.html\r\n\r\nSee \"terminal buffer\" for more information.  There is also a (old) screenshot\r\nof it running on Slackware Linux and Vim 6.0.","install_details":"run via:\r\n:source vimsh.vim\r\n\r\nor map to a key, something like this\r\nnmap <leader>sh           :runtime after\/usr\/macros\/vimsh\/vimsh.vim<CR>","5":"run via:\r\n:source vimsh.vim\r\n\r\nor map to a key, something like this\r\nnmap <leader>sh           :runtime after\/usr\/macros\/vimsh\/vimsh.vim<CR>","first_name":"brian","6":"brian","last_name":"sturk","7":"sturk","releases":[{"0":"165","vim_version":"6.0","1":"6.0","script_version":"0.22","2":"0.22","version_comment":"* Fixed reverse logic for sending EOF.\r\n* Fixed logic bug w\/ setting IGNBRK.\r\n* Added new keymaping for 'Enter' in normal mode.  This also pages output ala F5 does by default.\r\n* Added <silent> to all mappings to surpress echo'ing of execution of map in ex window.\r\n* Changed tabstop to 8 which seems to be the default for bash.\r\n* Cleaned up Win32 ^M handling.\r\n* Correctly handle output from programs ending with multiple ^M.  On Windows > 1 is ignored, pty all are honored.\r\n* Fixed the handling of the sometimes echo'ed executed command on Win32.\r\n* Workaround warning now shows actual mapped keys for page_output and new_prompt.","3":"* Fixed reverse logic for sending EOF.\r\n* Fixed logic bug w\/ setting IGNBRK.\r\n* Added new keymaping for 'Enter' in normal mode.  This also pages output ala F5 does by default.\r\n* Added <silent> to all mappings to surpress echo'ing of execution of map in ex window.\r\n* Changed tabstop to 8 which seems to be the default for bash.\r\n* Cleaned up Win32 ^M handling.\r\n* Correctly handle output from programs ending with multiple ^M.  On Windows > 1 is ignored, pty all are honored.\r\n* Fixed the handling of the sometimes echo'ed executed command on Win32.\r\n* Workaround warning now shows actual mapped keys for page_output and new_prompt.","package":"vimsh.tar.gz","4":"vimsh.tar.gz","src_id":"18977","5":"18977","creation_date":"1353019116","6":"1353019116"},{"0":"165","vim_version":"6.0","1":"6.0","script_version":"0.21","2":"0.21","version_comment":"Back from the dead.  Windows is working again, and a few bugs fixed.","3":"Back from the dead.  Windows is working again, and a few bugs fixed.","package":"vimsh.tar.gz","4":"vimsh.tar.gz","src_id":"12376","5":"12376","creation_date":"1266032614","6":"1266032614"},{"0":"165","vim_version":"6.0","1":"6.0","script_version":".20","2":".20","version_comment":"This version has gone through more testing now that I am using Linux all day @ work on my desktop.  I also did some decent testing on Windows.  Please let me know if you find any bugs...\r\n\r\n============================\r\n\r\n* Leading space in output issue now works 100%, even when doing\r\n  wacky stuff like 'sleep 10', then 'ls', without waiting for the prompt to return.\r\n* Typing 'exit' now works as expected when running ssh, telnet,\r\n  etc.  This fix also doesn't need the procs_in_pty hack I had previously used.\r\n* exit'ing the initially spawned shell correctly deletes the buffer.\r\n* Fixed race conditions w\/ SIGCHLD (async) setting flag and bdelete\r\n  path not always seeing flag toggle.\r\n* Fixed bug where exiting vimsh buffer kept vim in insert mode.\r\n* Ctrl-D (EOF) now closes buffer only when sent to initial spawned shell.\r\n* Fixed bug on Windows (pipes) for multiple line command or leading space in command.","3":"This version has gone through more testing now that I am using Linux all day @ work on my desktop.  I also did some decent testing on Windows.  Please let me know if you find any bugs...\r\n\r\n============================\r\n\r\n* Leading space in output issue now works 100%, even when doing\r\n  wacky stuff like 'sleep 10', then 'ls', without waiting for the prompt to return.\r\n* Typing 'exit' now works as expected when running ssh, telnet,\r\n  etc.  This fix also doesn't need the procs_in_pty hack I had previously used.\r\n* exit'ing the initially spawned shell correctly deletes the buffer.\r\n* Fixed race conditions w\/ SIGCHLD (async) setting flag and bdelete\r\n  path not always seeing flag toggle.\r\n* Fixed bug where exiting vimsh buffer kept vim in insert mode.\r\n* Ctrl-D (EOF) now closes buffer only when sent to initial spawned shell.\r\n* Fixed bug on Windows (pipes) for multiple line command or leading space in command.","package":"vimsh.tar","4":"vimsh.tar","src_id":"2877","5":"2877","creation_date":"1080327740","6":"1080327740"},{"0":"165","vim_version":"6.0","1":"6.0","script_version":"0.19","2":"0.19","version_comment":"* Fixed clear_screen call.\r\n* Changed default mapping for clearing screen to ^L.\r\n* Preserve mode (insert\/normal) when clearing screen.\r\n* Fix leading space in output when paging commands like ping(8).\r\n* Added some tips for [t]csh users to the readme.","3":"* Fixed clear_screen call.\r\n* Changed default mapping for clearing screen to ^L.\r\n* Preserve mode (insert\/normal) when clearing screen.\r\n* Fix leading space in output when paging commands like ping(8).\r\n* Added some tips for [t]csh users to the readme.","package":"vimsh.tar.gz","4":"vimsh.tar.gz","src_id":"2846","5":"2846","creation_date":"1079802561","6":"1079802561"},{"0":"165","vim_version":"6.0","1":"6.0","script_version":"0.18","2":"0.18","version_comment":"* Use waitpid rather than wait, now correctly handles :!cmd <mbays@sdf.lonestar.org>\r\n* Run pyfile command once when sourcing vimsh.vim <mbays@sdf.lonestar.org>\r\n* Handle programs that do not have a prompt <mbays@sdf.lonestar.org>\r\n* Moved invocation of startup shell in vimsh.vim to outside of pyfile sourcing conditional.\r\n* Fixed case where buffer deleted through autocommand and same \r\n  buffer name used again would cause an error (multiple buf fix).\r\n* Fixed multiple au BufDelete commands being invoked for same vimsh buffer name\r\n  (multiple buf fix).\r\n* Fixed password regex for ssh, now handles leading spaces if present within vimsh.","3":"* Use waitpid rather than wait, now correctly handles :!cmd <mbays@sdf.lonestar.org>\r\n* Run pyfile command once when sourcing vimsh.vim <mbays@sdf.lonestar.org>\r\n* Handle programs that do not have a prompt <mbays@sdf.lonestar.org>\r\n* Moved invocation of startup shell in vimsh.vim to outside of pyfile sourcing conditional.\r\n* Fixed case where buffer deleted through autocommand and same \r\n  buffer name used again would cause an error (multiple buf fix).\r\n* Fixed multiple au BufDelete commands being invoked for same vimsh buffer name\r\n  (multiple buf fix).\r\n* Fixed password regex for ssh, now handles leading spaces if present within vimsh.","package":"vimsh.tar.gz","4":"vimsh.tar.gz","src_id":"2702","5":"2702","creation_date":"1075586728","6":"1075586728"},{"0":"165","vim_version":"6.0","1":"6.0","script_version":"0.17","2":"0.17","version_comment":"* Multiple buffer support <ddarius@hotpop.com>.\r\n  i.e. :VimShNewBuf foo\r\n* Default behavior of creating a single vimsh buffer\r\n  when sourced added to multiple buffer patch.\r\n* Multi-line command support <ddarius@hotpop.com>\r\n* made a clear screen routine honoring g:vimsh_clear_all\r\n* clear screen key mapping g:vimsh_clear_key (default F9) <ddarius@hotpop.com>\r\n* use startinsert! <ddarius@hotpop.com>","3":"* Multiple buffer support <ddarius@hotpop.com>.\r\n  i.e. :VimShNewBuf foo\r\n* Default behavior of creating a single vimsh buffer\r\n  when sourced added to multiple buffer patch.\r\n* Multi-line command support <ddarius@hotpop.com>\r\n* made a clear screen routine honoring g:vimsh_clear_all\r\n* clear screen key mapping g:vimsh_clear_key (default F9) <ddarius@hotpop.com>\r\n* use startinsert! <ddarius@hotpop.com>","package":"vimsh.tar.gz","4":"vimsh.tar.gz","src_id":"2527","5":"2527","creation_date":"1070103499","6":"1070103499"},{"0":"165","vim_version":"6.0","1":"6.0","script_version":"0.16","2":"0.16","version_comment":"* Changed '^M' to '\\n' for python 2.3.  Vimsh would not\r\n  run w\/ python 2.3. Backwards compatible change.\r\n","3":"* Changed '^M' to '\\n' for python 2.3.  Vimsh would not\r\n  run w\/ python 2.3. Backwards compatible change.\r\n","package":"vimsh.tar.gz","4":"vimsh.tar.gz","src_id":"2342","5":"2342","creation_date":"1064002990","6":"1064002990"},{"0":"165","vim_version":"6.0","1":"6.0","script_version":"0.15","2":"0.15","version_comment":"Too many changes\/bugfixes to list here, please see changelog for this version.\r\n","3":"Too many changes\/bugfixes to list here, please see changelog for this version.\r\n","package":"vimsh.tar.gz","4":"vimsh.tar.gz","src_id":"1261","5":"1261","creation_date":"1033382738","6":"1033382738"},{"0":"165","vim_version":"6.0","1":"6.0","script_version":"0.14","2":"0.14","version_comment":"* Changed name of buffer name from vimsh to _vimsh_ since this\r\n  script is usually placed in a directory called vimsh.\r\n  If vimsh was a directory in vim's cwd it would edit\r\n  the directory using the explorer plugin.\r\n* Fixed procs_in_pty to return full name of command last executed.\r\n* Fixed not going back to insert mode after changing timeout.\r\n* Added current timeout to timeout prompt.\r\n* Correctly handle bogus entered timeout values, like 'ls'.\r\n* Added support routine to return the current mode.\r\n* Added a support routine to determine if last command\r\n  executed is still running.","3":"* Changed name of buffer name from vimsh to _vimsh_ since this\r\n  script is usually placed in a directory called vimsh.\r\n  If vimsh was a directory in vim's cwd it would edit\r\n  the directory using the explorer plugin.\r\n* Fixed procs_in_pty to return full name of command last executed.\r\n* Fixed not going back to insert mode after changing timeout.\r\n* Added current timeout to timeout prompt.\r\n* Correctly handle bogus entered timeout values, like 'ls'.\r\n* Added support routine to return the current mode.\r\n* Added a support routine to determine if last command\r\n  executed is still running.","package":"vimsh.tar.gz","4":"vimsh.tar.gz","src_id":"862","5":"862","creation_date":"1020976249","6":"1020976249"},{"0":"165","vim_version":"6.0","1":"6.0","script_version":"0.13","2":"0.13","version_comment":"* Figured out the line break always creeping in to\r\n  files for some users.  Winzip has feature under\r\n    Options->Configuration->Miscellaneous\r\n  called \"Tar file smart CF\/LF conversion\".  \r\n  It's not so smart... Turn it off if you want\r\n  to unpack the tarball using Winzip.  Better yet\r\nuse the vimsh.zip file available at my website.\r\n* Fixed 'exit' of shell killing entire vim session rather\r\nthan just the vimsh buffer.\r\n* Fixed empty line being added after paging output (F5)\r\n* Now check for password prompt when paging slow output(F5).\r\n* Cleanup of filename handling\r\n* Removed some un-needed ';' characters at the end of\r\nlines ( this is what happens when you do C all day )\r\n* Removed duplicate sending of EOF in send_eof.\r\n* Fixed pty\/# of proc detection","3":"* Figured out the line break always creeping in to\r\n  files for some users.  Winzip has feature under\r\n    Options->Configuration->Miscellaneous\r\n  called \"Tar file smart CF\/LF conversion\".  \r\n  It's not so smart... Turn it off if you want\r\n  to unpack the tarball using Winzip.  Better yet\r\nuse the vimsh.zip file available at my website.\r\n* Fixed 'exit' of shell killing entire vim session rather\r\nthan just the vimsh buffer.\r\n* Fixed empty line being added after paging output (F5)\r\n* Now check for password prompt when paging slow output(F5).\r\n* Cleanup of filename handling\r\n* Removed some un-needed ';' characters at the end of\r\nlines ( this is what happens when you do C all day )\r\n* Removed duplicate sending of EOF in send_eof.\r\n* Fixed pty\/# of proc detection","package":"vimsh.tar.gz","4":"vimsh.tar.gz","src_id":"782","5":"782","creation_date":"1018475832","6":"1018475832"},{"0":"165","vim_version":"6.0","1":"6.0","script_version":"0.12","2":"0.12","version_comment":"* Fix for Solaris pty detection.\r\n* EOF and SIGINT now query termios settings so\r\n  the 'right thing' happens.  Users can still map\r\n  whatever vim key sequence they want for these\r\n  operations.  Support for more of these coming\r\n  in future versions.\r\n* Removed now unused vimsh.signal function.\r\n* Output of slower commands after refresh give\r\n  better but still not perfect output.\r\n* For pty, SIGINT now flushes remaining data which will\r\n  work for some commands, i.e. ping.  Some apps still\r\n  will not flush correctly, find(1) for example.\r\n* Added a help message for SIGINT handler which can be\r\n  disabled by setting vimsh_show_workaround_msgs\r\n  to 0 in your .vimrc.  It just explains how to get\r\n  around not seeing the prompt for commands that don't\r\n  flush correctly after SIGINT.\r\n* Go back to insert mode after paging output.\r\n* Fixes and speed ups for Windows\r\n      - BufWipeout wasn't being hit so lots of cmd.exe\r\n        instances being left around, changed to\r\n        BufDelete.\r\n      - \r\n wasn't being removed from end of lines that\r\n        had it, i.e. ping.exe.\r\n      - Buffer size for reading from pipe has been\r\n        optimized somewhat.\r\n      - Return to insert mode after trying to execute\r\n        unsupported command.\r\n      - Changed redraw frequency for better interactive\r\n        response.","3":"* Fix for Solaris pty detection.\r\n* EOF and SIGINT now query termios settings so\r\n  the 'right thing' happens.  Users can still map\r\n  whatever vim key sequence they want for these\r\n  operations.  Support for more of these coming\r\n  in future versions.\r\n* Removed now unused vimsh.signal function.\r\n* Output of slower commands after refresh give\r\n  better but still not perfect output.\r\n* For pty, SIGINT now flushes remaining data which will\r\n  work for some commands, i.e. ping.  Some apps still\r\n  will not flush correctly, find(1) for example.\r\n* Added a help message for SIGINT handler which can be\r\n  disabled by setting vimsh_show_workaround_msgs\r\n  to 0 in your .vimrc.  It just explains how to get\r\n  around not seeing the prompt for commands that don't\r\n  flush correctly after SIGINT.\r\n* Go back to insert mode after paging output.\r\n* Fixes and speed ups for Windows\r\n      - BufWipeout wasn't being hit so lots of cmd.exe\r\n        instances being left around, changed to\r\n        BufDelete.\r\n      - \r\n wasn't being removed from end of lines that\r\n        had it, i.e. ping.exe.\r\n      - Buffer size for reading from pipe has been\r\n        optimized somewhat.\r\n      - Return to insert mode after trying to execute\r\n        unsupported command.\r\n      - Changed redraw frequency for better interactive\r\n        response.","package":"vimsh.tar.gz","4":"vimsh.tar.gz","src_id":"759","5":"759","creation_date":"1017935904","6":"1017935904"},{"0":"165","vim_version":"6.0","1":"6.0","script_version":"0.11","2":"0.11","version_comment":"* Added support for sending EOF. Default\r\n   mapping is Ctrl-D <C-d>.  Now you can run python\r\n   for example in a buffer and quit it by typing\r\n   Ctrl-D.\r\n* Fixed snafu of line split in the middle of python\r\n   statement which kept script from loading.  WHOOPS.\r\n* Made the signalling mechanism more generic so I can\r\n   add more handlers in the future.","3":"* Added support for sending EOF. Default\r\n   mapping is Ctrl-D <C-d>.  Now you can run python\r\n   for example in a buffer and quit it by typing\r\n   Ctrl-D.\r\n* Fixed snafu of line split in the middle of python\r\n   statement which kept script from loading.  WHOOPS.\r\n* Made the signalling mechanism more generic so I can\r\n   add more handlers in the future.","package":"vimsh.tar.gz","4":"vimsh.tar.gz","src_id":"665","5":"665","creation_date":"1015597601","6":"1015597601"},{"0":"165","vim_version":"6.0","1":"6.0","script_version":".10","2":".10","version_comment":"* !! NOTE !!: new way to run is to \"source\" vimsh.vim, see vimsh.readme in tarball\r\n   Windows users need to use the link in the description to get a .zip file.\r\n* \/bin\/sh is symlinked to csh on *bsd, added csh prompt.\r\n* Fixed mappings\r\n* Added check for buffer's existence before writing prompt\r\n  and jump to prompt if it already exists.\r\n* Ctrl-c ( SIGINT ) for interrupting continuous cmds, prompts\r\n  if multiple processes besides shell running.\r\n* Cleaned up exit handling\r\n* Added function and mapping for refreshing\/paging\r\n  output when timeout is too short.\r\n* Added vim function to redraw periodically during long\r\n  operations or continuous operations ( ie ping <host> or \r\n  find \/.","3":"* !! NOTE !!: new way to run is to \"source\" vimsh.vim, see vimsh.readme in tarball\r\n   Windows users need to use the link in the description to get a .zip file.\r\n* \/bin\/sh is symlinked to csh on *bsd, added csh prompt.\r\n* Fixed mappings\r\n* Added check for buffer's existence before writing prompt\r\n  and jump to prompt if it already exists.\r\n* Ctrl-c ( SIGINT ) for interrupting continuous cmds, prompts\r\n  if multiple processes besides shell running.\r\n* Cleaned up exit handling\r\n* Added function and mapping for refreshing\/paging\r\n  output when timeout is too short.\r\n* Added vim function to redraw periodically during long\r\n  operations or continuous operations ( ie ping <host> or \r\n  find \/.","package":"vimsh.tar.gz","4":"vimsh.tar.gz","src_id":"436","5":"436","creation_date":"1008946068","6":"1008946068"},{"0":"165","vim_version":"6.0","1":"6.0","script_version":"0.9","2":"0.9","version_comment":"Set buftype=nofile <b.cerrina@wanadoo.fr>\r\nOption to use current buffer if non-modified\r\nUse vim variables for options so this file doesn\\'t need\r\nto be modified to allow customization.  See script for info.\r\nHandle cancelling of input dialogs\r\nFlag unsupported windows console commands\r\n( partial list see:unsupp_regex )\r\nSee NOTE for this version in script for more Windows specific information.\r\n","3":"Set buftype=nofile <b.cerrina@wanadoo.fr>\r\nOption to use current buffer if non-modified\r\nUse vim variables for options so this file doesn\\'t need\r\nto be modified to allow customization.  See script for info.\r\nHandle cancelling of input dialogs\r\nFlag unsupported windows console commands\r\n( partial list see:unsupp_regex )\r\nSee NOTE for this version in script for more Windows specific information.\r\n","package":"vimsh.tar.gz","4":"vimsh.tar.gz","src_id":"424","5":"424","creation_date":"1008278434","6":"1008278434"},{"0":"165","vim_version":"6.0","1":"6.0","script_version":"0.8","2":"0.8","version_comment":"- Windows support, tested on NT4 w\/ ActiveState Python 2.2\r\n    Should also work on 2K\/XP. Caveat hacktor  :).  Non interactive\r\n    programs dir, findstr, attrib etc work fine, no ftp, telnet, etc yet.\r\n- Made clear check more explicit, cleartool was triggering it\r\n- Fixed the mysterious missing single char issue.\r\n\r\nI'm getting some good feedback from Windows users, are there any Unix\r\nvim people using it?\r\n","3":"- Windows support, tested on NT4 w\/ ActiveState Python 2.2\r\n    Should also work on 2K\/XP. Caveat hacktor  :).  Non interactive\r\n    programs dir, findstr, attrib etc work fine, no ftp, telnet, etc yet.\r\n- Made clear check more explicit, cleartool was triggering it\r\n- Fixed the mysterious missing single char issue.\r\n\r\nI'm getting some good feedback from Windows users, are there any Unix\r\nvim people using it?\r\n","package":"vimsh.tar.gz","4":"vimsh.tar.gz","src_id":"420","5":"420","creation_date":"1008114314","6":"1008114314"},{"0":"165","vim_version":"6.0","1":"6.0","script_version":"0.7","2":"0.7","version_comment":"Made import\/usage of tty, pty conditional on not being windows\r\nRemoved popen buffer size\r\nIncreased timeout if using popen3\r\nFixed output for lines crossing consecutive reads for pty\r\nAdded map for starting a new prompt at bottom of buffer\r\n","3":"Made import\/usage of tty, pty conditional on not being windows\r\nRemoved popen buffer size\r\nIncreased timeout if using popen3\r\nFixed output for lines crossing consecutive reads for pty\r\nAdded map for starting a new prompt at bottom of buffer\r\n","package":"vimsh.tar.gz","4":"vimsh.tar.gz","src_id":"417","5":"417","creation_date":"1007936079","6":"1007936079"},{"0":"165","vim_version":"6.0","1":"6.0","script_version":"0.6","2":"0.6","version_comment":"NOTE: the python module select doesn't seem to be available except for sockets on Windows so I need to investigate this more\r\n- Removed the <Delete><BS> hooks.  They just weren't working as I thought they would.  Now just check for cursor to not be in prompt. \r\n- Figured out the ftp issue see \"notes\". \r\n- Added a mapping & func to set timeouts.\r\n- Changed pty prompt to something useful \r\n- fixed clear\r\n","3":"NOTE: the python module select doesn't seem to be available except for sockets on Windows so I need to investigate this more\r\n- Removed the <Delete><BS> hooks.  They just weren't working as I thought they would.  Now just check for cursor to not be in prompt. \r\n- Figured out the ftp issue see \"notes\". \r\n- Added a mapping & func to set timeouts.\r\n- Changed pty prompt to something useful \r\n- fixed clear\r\n","package":"vimsh.tar.gz","4":"vimsh.tar.gz","src_id":"414","5":"414","creation_date":"1007774147","6":"1007774147"},{"0":"165","vim_version":"6.0","1":"6.0","script_version":"0.5","2":"0.5","version_comment":"Implemented secure input of passwords,\r\nExit cmd works as expected, for subprocesses it\r\nexits to parent, initial shell exit will delete buffer,\r\nKeep <Delete> from overwriting prompt\r\n","3":"Implemented secure input of passwords,\r\nExit cmd works as expected, for subprocesses it\r\nexits to parent, initial shell exit will delete buffer,\r\nKeep <Delete> from overwriting prompt\r\n","package":"vimsh.tar.gz","4":"vimsh.tar.gz","src_id":"411","5":"411","creation_date":"1007751710","6":"1007751710"},{"0":"165","vim_version":"6.0","1":"6.0","script_version":"0.4a","2":"0.4a","version_comment":"implemented alternate subprocess control ( popen ) so it should *in theory* work on any platform that supports\r\npipes, i.e. WinXX, albiet the output isn't as pretty-formatted as with pty.  I cannot at the moment test on Windows\r\nand would like some feedback.  Shell commands clear and exit are also implemented.","3":"implemented alternate subprocess control ( popen ) so it should *in theory* work on any platform that supports\r\npipes, i.e. WinXX, albiet the output isn't as pretty-formatted as with pty.  I cannot at the moment test on Windows\r\nand would like some feedback.  Shell commands clear and exit are also implemented.","package":"vimsh.tar.gz","4":"vimsh.tar.gz","src_id":"410","5":"410","creation_date":"1007685758","6":"1007685758"},{"0":"165","vim_version":"6.0","1":"6.0","script_version":"0.3a","2":"0.3a","version_comment":"Fixed up the 1st line issue, and ^M printing.  The script is starting to firm up so I'm\r\ngoing to next try to get it to work on windows.  Please send any feedback\/issues not listed\r\nin the script.","3":"Fixed up the 1st line issue, and ^M printing.  The script is starting to firm up so I'm\r\ngoing to next try to get it to work on windows.  Please send any feedback\/issues not listed\r\nin the script.","package":"vimsh.tar.gz","4":"vimsh.tar.gz","src_id":"408","5":"408","creation_date":"1007597169","6":"1007597169"},{"0":"165","vim_version":"6.0","1":"6.0","script_version":"0.2a","2":"0.2a","version_comment":"Fixed tabwidth, not on prompt message, handling of user input execution rm -i works, and shells now die via autocommand","3":"Fixed tabwidth, not on prompt message, handling of user input execution rm -i works, and shells now die via autocommand","package":"vimsh.tar.gz","4":"vimsh.tar.gz","src_id":"406","5":"406","creation_date":"1007568355","6":"1007568355"},{"0":"165","vim_version":"6.0","1":"6.0","script_version":"0.1a","2":"0.1a","version_comment":"Initial upload","3":"Initial upload","package":"vimsh.tar.gz","4":"vimsh.tar.gz","src_id":"404","5":"404","creation_date":"1007501780","6":"1007501780"}]},"164":{"script_id":"164","0":"164","script_name":"html-macros.vim","1":"html-macros.vim","script_type":"utility","2":"utility","summary":"macros for html","3":"macros for html","description":"Here are some macros for html.\r\n\r\nIn normal mode, the function key F1 will insert an html skeleton.\r\nIn insert mode, F1 will complete the previous uncompleted tag.\r\nTyping \"<\" will result in a pair \"<>\", with the cursor in between.\r\nThere are a number of macros beginning with \";\".  For instance,\r\n;1 will result in <h1><\/h1>, with the cursor in the middle.\r\nTyping ;1 in visual mode will embrace the region with the tags <h1><\/h1>.","4":"Here are some macros for html.\r\n\r\nIn normal mode, the function key F1 will insert an html skeleton.\r\nIn insert mode, F1 will complete the previous uncompleted tag.\r\nTyping \"<\" will result in a pair \"<>\", with the cursor in between.\r\nThere are a number of macros beginning with \";\".  For instance,\r\n;1 will result in <h1><\/h1>, with the cursor in the middle.\r\nTyping ;1 in visual mode will embrace the region with the tags <h1><\/h1>.","install_details":"Put it in an ftplugin directory in your runtime path, \r\nor add the following line to your .vimrc file.\r\n\r\nautocmd Filetype html source ~\/.Vim\/html-macros.vim\r\n\r\nwith the appropriate directories.","5":"Put it in an ftplugin directory in your runtime path, \r\nor add the following line to your .vimrc file.\r\n\r\nautocmd Filetype html source ~\/.Vim\/html-macros.vim\r\n\r\nwith the appropriate directories.","first_name":"Carl","6":"Carl","last_name":"Mueller","7":"Mueller","releases":[{"0":"164","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"a","3":"a","package":"html-macros.vim","4":"html-macros.vim","src_id":"1294","5":"1294","creation_date":"1034416194","6":"1034416194"},{"0":"164","vim_version":"6.0","1":"6.0","script_version":"1.1","2":"1.1","version_comment":"Fixed problems with indentation","3":"Fixed problems with indentation","package":"html.vim","4":"html.vim","src_id":"1291","5":"1291","creation_date":"1034245755","6":"1034245755"},{"0":"164","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Changed the name, so it doesn't conflict\r\nwith the html.vim syntax file.","3":"Changed the name, so it doesn't conflict\r\nwith the html.vim syntax file.","package":"html-macros.vim","4":"html-macros.vim","src_id":"434","5":"434","creation_date":"1008920515","6":"1008920515"},{"0":"164","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"html-macros.vim","4":"html-macros.vim","src_id":"398","5":"398","creation_date":"1007365039","6":"1007365039"}]},"163":{"script_id":"163","0":"163","script_name":"ruby-macros.vim","1":"ruby-macros.vim","script_type":"ftplugin","2":"ftplugin","summary":"macros for the ruby language","3":"macros for the ruby language","description":"This plugin is for editing ruby files.\r\n\r\nTyping \"for\" on a blank line will result in\r\n\r\nfor  in  \r\nend\r\n\r\nwith the cursor positioned before the \"in\".  \r\nThe same will happen with \"while\", \"until\", \r\nand so on.  But if the line is not blank,\r\n\"for\" will just insert itself.\r\n\r\nAlso, symbols like \" are inserted in matching\r\npairs, with the cursor in between.\r\n\r\n\"K\" runs ruby on the current buffer, and \r\nthe \"F1\" function key puts a line\r\n#!\/usr\/math\/bin\/ruby\r\non the first line.  (You will have to edit \r\nthis part).\r\n","4":"This plugin is for editing ruby files.\r\n\r\nTyping \"for\" on a blank line will result in\r\n\r\nfor  in  \r\nend\r\n\r\nwith the cursor positioned before the \"in\".  \r\nThe same will happen with \"while\", \"until\", \r\nand so on.  But if the line is not blank,\r\n\"for\" will just insert itself.\r\n\r\nAlso, symbols like \" are inserted in matching\r\npairs, with the cursor in between.\r\n\r\n\"K\" runs ruby on the current buffer, and \r\nthe \"F1\" function key puts a line\r\n#!\/usr\/math\/bin\/ruby\r\non the first line.  (You will have to edit \r\nthis part).\r\n","install_details":"Put something like the following line in your .vimrc file:\r\n\r\nautocmd Filetype ruby source ~\/.Vim\/ruby-macros.vim\r\n\r\nor put this in an ftplugin directory in your runtime path.","5":"Put something like the following line in your .vimrc file:\r\n\r\nautocmd Filetype ruby source ~\/.Vim\/ruby-macros.vim\r\n\r\nor put this in an ftplugin directory in your runtime path.","first_name":"Carl","6":"Carl","last_name":"Mueller","7":"Mueller","releases":[{"0":"163","vim_version":"6.0","1":"6.0","script_version":"1.2","2":"1.2","version_comment":"Fixed a mistake with the matched \r\ninsertion of brackets.","3":"Fixed a mistake with the matched \r\ninsertion of brackets.","package":"ruby-macros.vim","4":"ruby-macros.vim","src_id":"1053","5":"1053","creation_date":"1027680479","6":"1027680479"},{"0":"163","vim_version":"6.0","1":"6.0","script_version":"1.01","2":"1.01","version_comment":"Renamed file, so it doesn't conflict\r\nwith the ruby.vim syntax file.","3":"Renamed file, so it doesn't conflict\r\nwith the ruby.vim syntax file.","package":"ruby-macros.vim","4":"ruby-macros.vim","src_id":"429","5":"429","creation_date":"1008660107","6":"1008660107"},{"0":"163","vim_version":"6.0","1":"6.0","script_version":"1.01","2":"1.01","version_comment":"Fixed the macros for automatically \r\ncompleting constructions like \r\n\\\\\\\"if .. end\\\\\\\".","3":"Fixed the macros for automatically \r\ncompleting constructions like \r\n\\\\\\\"if .. end\\\\\\\".","package":"ruby-macros.vim","4":"ruby-macros.vim","src_id":"426","5":"426","creation_date":"1008571487","6":"1008571487"},{"0":"163","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"ruby-macros.vim","4":"ruby-macros.vim","src_id":"397","5":"397","creation_date":"1007364309","6":"1007364309"}]},"162":{"script_id":"162","0":"162","script_name":"auctex.vim","1":"auctex.vim","script_type":"ftplugin","2":"ftplugin","summary":"macros for latex","3":"macros for latex","description":"This is a large collection of Latex macros, with inspiration\r\nfrom the emacs package \"auctex\", among other places.  \r\nRead the file for details;  I have written many comments.\r\n\r\nYou should freely modify these macros.  Most of them are  \r\nindepent, so nothing will break.  In some places I've provided\r\nalternate versions which are commented out.  If you have good \r\nideas, contact me and I'll incorporate them.\r\n\r\nBy popular demand, here is a more extensive description of\r\nthe key bindings:\r\nhttp:\/\/www.math.rochester.edu\/people\/faculty\/cmlr\/Latex\/auctex-vim-keybindings\r\n\r\nThere is also Vim-LaTeX,\r\nhttp:\/\/vim-latex.sourceforge.net \r\nIt is a more extensive package, developed by a group, and I have \r\ncontributed most of my ideas to this project.  You might prefer \r\nmy script if you like something smaller, with parts that are (mostly) \r\nindependent and easy to modify.\r\n\r\nBriefly,\r\n\r\nIn normal mode, F1 - F4 will insert latex templates, unless they are\r\nalready there in the file.  You have to provide these templates yourself.\r\n\r\nIn insert mode, F1 - F5 will insert environments such as \\begin{..} \\end{..}.\r\n\r\nC-S-F1 through C-S-F5 will alter existing environments.\r\n\r\n(), $$, [], \\[\\], {}, \\{\\}, && are inserted in matching pairs.\r\n\r\nOutside of a math environment, tab does word completion, \r\nor gives a tab if the previous character is a space or \r\na line beginning.  Within a math environment, \r\ntab moves you between parentheses or to the end of the \r\nenvironment.\r\n\r\nMany Latex commands are bound to the ` key.  (This comes from auctex).\r\nFor instance, \\alpha is bound to `a, and \\infty is bound to `8.\r\n\\frac{}{} is bound to `\/  .\r\n\r\nMenu items allow you to change or delete matching pairs of brackets,\r\nas well as insert \\left..\\right automatically.  \r\n\r\nNow pressing <Insert> twice will also allow modification of brackets, according \r\nto a menu that appears at the bottom.\r\n\r\nIn normal mode, K runs latex, takes you to the position of the first error (if any),\r\nand displays the error message with highlighting.\r\n\r\nTo get \\mathbf{R}, type r<Insert>b.  To get \\mathcal{R}, type r<Insert>c. \r\n<Insert>s produces \\sqrt{}.  Capital letters are more common, but you can\r\nstill get \\mathbf{x} by typing X<Insert>b.  Same for \\mathcal.\r\n\r\nSome macros are polymorphic.  For instance, when preceded by bracket, \r\n<Insert>l will insert \\left..\\right around the brackets.  Otherwise it \r\nwill insert \\label{} and position the cursor in between the {}.\r\nLikewise, <Insert>c will produce \\cite{} when preceded by a blank or at \r\nthe beginning of the line;  but, for example, b<Insert>b will produce \\mathbf{B}.\r\n\r\nThere are \"smart quotes\".  That is, typing \" will produce a `` if there is\r\na space before the \", and will produce '' otherwise.\r\n\r\nYou can embrace the visual region with () by typing `(.  This works \r\nfor other kinds of parentheses, too, as well as $$ and &&.\r\n\r\nLong lines are automatically split up to keep $..$ (math expressions)\r\non the same line.\r\n\r\nThere are several abbreviations, such as \\b for \\bigskip.\r\n\r\nYou can add your own macros, the macro key is ;\r\n\r\nInspired by LaTeX-Suite, the tab key has some new uses.  Inside \\ref{}, it opens \r\na subwindow with the reference keys.  Pressing enter will insert that reference.  \r\nDitto for \\cite{}, the subwindow will show either your bibitem entries (if any) or \r\nyour bibtex file.  Pressing enter within the bibtex reference will insert the proper \r\ncitation key.","4":"This is a large collection of Latex macros, with inspiration\r\nfrom the emacs package \"auctex\", among other places.  \r\nRead the file for details;  I have written many comments.\r\n\r\nYou should freely modify these macros.  Most of them are  \r\nindepent, so nothing will break.  In some places I've provided\r\nalternate versions which are commented out.  If you have good \r\nideas, contact me and I'll incorporate them.\r\n\r\nBy popular demand, here is a more extensive description of\r\nthe key bindings:\r\nhttp:\/\/www.math.rochester.edu\/people\/faculty\/cmlr\/Latex\/auctex-vim-keybindings\r\n\r\nThere is also Vim-LaTeX,\r\nhttp:\/\/vim-latex.sourceforge.net \r\nIt is a more extensive package, developed by a group, and I have \r\ncontributed most of my ideas to this project.  You might prefer \r\nmy script if you like something smaller, with parts that are (mostly) \r\nindependent and easy to modify.\r\n\r\nBriefly,\r\n\r\nIn normal mode, F1 - F4 will insert latex templates, unless they are\r\nalready there in the file.  You have to provide these templates yourself.\r\n\r\nIn insert mode, F1 - F5 will insert environments such as \\begin{..} \\end{..}.\r\n\r\nC-S-F1 through C-S-F5 will alter existing environments.\r\n\r\n(), $$, [], \\[\\], {}, \\{\\}, && are inserted in matching pairs.\r\n\r\nOutside of a math environment, tab does word completion, \r\nor gives a tab if the previous character is a space or \r\na line beginning.  Within a math environment, \r\ntab moves you between parentheses or to the end of the \r\nenvironment.\r\n\r\nMany Latex commands are bound to the ` key.  (This comes from auctex).\r\nFor instance, \\alpha is bound to `a, and \\infty is bound to `8.\r\n\\frac{}{} is bound to `\/  .\r\n\r\nMenu items allow you to change or delete matching pairs of brackets,\r\nas well as insert \\left..\\right automatically.  \r\n\r\nNow pressing <Insert> twice will also allow modification of brackets, according \r\nto a menu that appears at the bottom.\r\n\r\nIn normal mode, K runs latex, takes you to the position of the first error (if any),\r\nand displays the error message with highlighting.\r\n\r\nTo get \\mathbf{R}, type r<Insert>b.  To get \\mathcal{R}, type r<Insert>c. \r\n<Insert>s produces \\sqrt{}.  Capital letters are more common, but you can\r\nstill get \\mathbf{x} by typing X<Insert>b.  Same for \\mathcal.\r\n\r\nSome macros are polymorphic.  For instance, when preceded by bracket, \r\n<Insert>l will insert \\left..\\right around the brackets.  Otherwise it \r\nwill insert \\label{} and position the cursor in between the {}.\r\nLikewise, <Insert>c will produce \\cite{} when preceded by a blank or at \r\nthe beginning of the line;  but, for example, b<Insert>b will produce \\mathbf{B}.\r\n\r\nThere are \"smart quotes\".  That is, typing \" will produce a `` if there is\r\na space before the \", and will produce '' otherwise.\r\n\r\nYou can embrace the visual region with () by typing `(.  This works \r\nfor other kinds of parentheses, too, as well as $$ and &&.\r\n\r\nLong lines are automatically split up to keep $..$ (math expressions)\r\non the same line.\r\n\r\nThere are several abbreviations, such as \\b for \\bigskip.\r\n\r\nYou can add your own macros, the macro key is ;\r\n\r\nInspired by LaTeX-Suite, the tab key has some new uses.  Inside \\ref{}, it opens \r\na subwindow with the reference keys.  Pressing enter will insert that reference.  \r\nDitto for \\cite{}, the subwindow will show either your bibitem entries (if any) or \r\nyour bibtex file.  Pressing enter within the bibtex reference will insert the proper \r\ncitation key.","install_details":"Put the file in the directory ~\/.Vim, and include the following line in your .vimrc file:\r\n\r\nautocmd Filetype tex source ~\/.Vim\/auctex.vim","5":"Put the file in the directory ~\/.Vim, and include the following line in your .vimrc file:\r\n\r\nautocmd Filetype tex source ~\/.Vim\/auctex.vim","first_name":"Carl","6":"Carl","last_name":"Mueller","7":"Mueller","releases":[{"0":"162","vim_version":"8.0","1":"8.0","script_version":"2.2.18","2":"2.2.18","version_comment":"Running latex no longer pollutes the screen with output.","3":"Running latex no longer pollutes the screen with output.","package":"auctex.vim","4":"auctex.vim","src_id":"24799","5":"24799","creation_date":"1481506982","6":"1481506982"},{"0":"162","vim_version":"7.4","1":"7.4","script_version":"2.2.17","2":"2.2.17","version_comment":"Fixed a bug in the reference insertion feature.","3":"Fixed a bug in the reference insertion feature.","package":"auctex.vim","4":"auctex.vim","src_id":"23660","5":"23660","creation_date":"1444409598","6":"1444409598"},{"0":"162","vim_version":"7.0","1":"7.0","script_version":"2.2.16","2":"2.2.16","version_comment":"When you make a tex error, the cursor automatically goes to the position of the error.  This feature didn't work with long lines, now it's corrected.","3":"When you make a tex error, the cursor automatically goes to the position of the error.  This feature didn't work with long lines, now it's corrected.","package":"auctex.vim","4":"auctex.vim","src_id":"23602","5":"23602","creation_date":"1442596137","6":"1442596137"},{"0":"162","vim_version":"7.4","1":"7.4","script_version":"2.2.15","2":"2.2.15","version_comment":"Now reference and citation insertion works correctly.","3":"Now reference and citation insertion works correctly.","package":"auctex.vim","4":"auctex.vim","src_id":"21996","5":"21996","creation_date":"1402151703","6":"1402151703"},{"0":"162","vim_version":"7.4","1":"7.4","script_version":"2.2.14","2":"2.2.14","version_comment":"Now the page is centered after reference or citation insertion.","3":"Now the page is centered after reference or citation insertion.","package":"auctex.vim","4":"auctex.vim","src_id":"21993","5":"21993","creation_date":"1402085758","6":"1402085758"},{"0":"162","vim_version":"7.4","1":"7.4","script_version":"2.2.13","2":"2.2.13","version_comment":"Improved <F7> proof macro.  Also, <Insert>i now puts in a <CR> before \\item, so you can use it at the end of the previous \\item.","3":"Improved <F7> proof macro.  Also, <Insert>i now puts in a <CR> before \\item, so you can use it at the end of the previous \\item.","package":"auctex.vim","4":"auctex.vim","src_id":"21991","5":"21991","creation_date":"1402075442","6":"1402075442"},{"0":"162","vim_version":"7.4","1":"7.4","script_version":"2.2.12","2":"2.2.12","version_comment":"Now after a successful latex compilation, the cursor is centered in the window.","3":"Now after a successful latex compilation, the cursor is centered in the window.","package":"auctex.vim","4":"auctex.vim","src_id":"21981","5":"21981","creation_date":"1401747550","6":"1401747550"},{"0":"162","vim_version":"7.3","1":"7.3","script_version":"2.2.11","2":"2.2.11","version_comment":"Inserting environments \"description\", \"enumerate\", and \"itemize\" now results in \"\\item\" appearing on the first line of the environment, and the cursor placed correctly.  Removed redundant key bindings <M-Space>, <C-Space>, <C-Tab>, <S-Tab>.","3":"Inserting environments \"description\", \"enumerate\", and \"itemize\" now results in \"\\item\" appearing on the first line of the environment, and the cursor placed correctly.  Removed redundant key bindings <M-Space>, <C-Space>, <C-Tab>, <S-Tab>.","package":"auctex.vim","4":"auctex.vim","src_id":"18225","5":"18225","creation_date":"1341585715","6":"1341585715"},{"0":"162","vim_version":"7.3","1":"7.3","script_version":"2.2.10","2":"2.2.10","version_comment":"Now within \\cite{}, the tab key only opens the bibtex or reference window when the cursor is just to the right of the left bracket.  Otherwise the cursor is placed to the right outside the brackets.","3":"Now within \\cite{}, the tab key only opens the bibtex or reference window when the cursor is just to the right of the left bracket.  Otherwise the cursor is placed to the right outside the brackets.","package":"auctex.vim","4":"auctex.vim","src_id":"18031","5":"18031","creation_date":"1337867409","6":"1337867409"},{"0":"162","vim_version":"7.3","1":"7.3","script_version":"2.2.9","2":"2.2.9","version_comment":"Now it is possible to add multiple reference within a \\cite{} while in citation mode.  Just go the citation in the lower window and press comma or right click.","3":"Now it is possible to add multiple reference within a \\cite{} while in citation mode.  Just go the citation in the lower window and press comma or right click.","package":"auctex.vim","4":"auctex.vim","src_id":"18015","5":"18015","creation_date":"1337611076","6":"1337611076"},{"0":"162","vim_version":"7.3","1":"7.3","script_version":"2.2.8","2":"2.2.8","version_comment":"Vim no longer recognizes <S-F1>, <S-F2>, etc.  I'm changing these bindings to <C-S-F1> and so on.  They are used to change environments.","3":"Vim no longer recognizes <S-F1>, <S-F2>, etc.  I'm changing these bindings to <C-S-F1> and so on.  They are used to change environments.","package":"auctex.vim","4":"auctex.vim","src_id":"16680","5":"16680","creation_date":"1318774828","6":"1318774828"},{"0":"162","vim_version":"7.0","1":"7.0","script_version":"2.2.7","2":"2.2.7","version_comment":"Changed mathbf and mathcal macros to switch the capitalization of the letter.  This is because capital letters are more common with these commands, so it saves a keystroke.  But if you want  a small letter, you can still get it.","3":"Changed mathbf and mathcal macros to switch the capitalization of the letter.  This is because capital letters are more common with these commands, so it saves a keystroke.  But if you want  a small letter, you can still get it.","package":"auctex.vim","4":"auctex.vim","src_id":"16634","5":"16634","creation_date":"1318037856","6":"1318037856"},{"0":"162","vim_version":"7.0","1":"7.0","script_version":"2.2.6","2":"2.2.6","version_comment":"Fixed bug for changing environments with <S-F5>.","3":"Fixed bug for changing environments with <S-F5>.","package":"auctex.vim","4":"auctex.vim","src_id":"13443","5":"13443","creation_date":"1280538532","6":"1280538532"},{"0":"162","vim_version":"7.0","1":"7.0","script_version":"2.2.5","2":"2.2.5","version_comment":"Some further cleanup","3":"Some further cleanup","package":"auctex.vim","4":"auctex.vim","src_id":"13062","5":"13062","creation_date":"1274970587","6":"1274970587"},{"0":"162","vim_version":"7.0","1":"7.0","script_version":"2.2.4","2":"2.2.4","version_comment":"Slight improvement of the double insert macro of 2.2.3.  Removed corresponding <Tab> key bindings.","3":"Slight improvement of the double insert macro of 2.2.3.  Removed corresponding <Tab> key bindings.","package":"auctex.vim","4":"auctex.vim","src_id":"13058","5":"13058","creation_date":"1274886328","6":"1274886328"},{"0":"162","vim_version":"7.0","1":"7.0","script_version":"2.2.3","2":"2.2.3","version_comment":"Pressing <Insert> twice now changes brackets in various ways, according to a menu that appears at the bottom.","3":"Pressing <Insert> twice now changes brackets in various ways, according to a menu that appears at the bottom.","package":"auctex.vim","4":"auctex.vim","src_id":"13056","5":"13056","creation_date":"1274814082","6":"1274814082"},{"0":"162","vim_version":"7.0","1":"7.0","script_version":"2.2.2","2":"2.2.2","version_comment":"Fixed bug in changing environments (perhaps due to changes in vim scripting).","3":"Fixed bug in changing environments (perhaps due to changes in vim scripting).","package":"auctex.vim","4":"auctex.vim","src_id":"13021","5":"13021","creation_date":"1274100037","6":"1274100037"},{"0":"162","vim_version":"7.0","1":"7.0","script_version":"2.2.1","2":"2.2.1","version_comment":"Fixed small bug when searching for \"bibliography\".","3":"Fixed small bug when searching for \"bibliography\".","package":"auctex.vim","4":"auctex.vim","src_id":"10437","5":"10437","creation_date":"1240404968","6":"1240404968"},{"0":"162","vim_version":"7.0","1":"7.0","script_version":"2.2","2":"2.2","version_comment":"Some bug fixes, especially in breaking lines.","3":"Some bug fixes, especially in breaking lines.","package":"auctex.vim","4":"auctex.vim","src_id":"8380","5":"8380","creation_date":"1204457621","6":"1204457621"},{"0":"162","vim_version":"7.0","1":"7.0","script_version":"2.1.4","2":"2.1.4","version_comment":"Various features are faster and better.  For example, ending the line in a period now splits the line if it is too long.","3":"Various features are faster and better.  For example, ending the line in a period now splits the line if it is too long.","package":"auctex.vim","4":"auctex.vim","src_id":"8270","5":"8270","creation_date":"1202904538","6":"1202904538"},{"0":"162","vim_version":"7.0","1":"7.0","script_version":"2.1.3","2":"2.1.3","version_comment":"Speeded up the macro where \"..\" results in \"\\ldots\" or \"\\cdots\", or just \"\\dots\".","3":"Speeded up the macro where \"..\" results in \"\\ldots\" or \"\\cdots\", or just \"\\dots\".","package":"auctex.vim","4":"auctex.vim","src_id":"8237","5":"8237","creation_date":"1202142423","6":"1202142423"},{"0":"162","vim_version":"7.0","1":"7.0","script_version":"2.1.2","2":"2.1.2","version_comment":"Suppressed search highlighting that came on in one of the macros, and made another small fix.","3":"Suppressed search highlighting that came on in one of the macros, and made another small fix.","package":"auctex.vim","4":"auctex.vim","src_id":"8188","5":"8188","creation_date":"1201545086","6":"1201545086"},{"0":"162","vim_version":"6.0","1":"6.0","script_version":"2.1.1","2":"2.1.1","version_comment":"Another improvement to \\ref and \\cite macros, in line with the Reftex emacs package.","3":"Another improvement to \\ref and \\cite macros, in line with the Reftex emacs package.","package":"auctex.vim","4":"auctex.vim","src_id":"8106","5":"8106","creation_date":"1199096898","6":"1199096898"},{"0":"162","vim_version":"7.0","1":"7.0","script_version":"2.1","2":"2.1","version_comment":"Improved citation lookup.  Now pressing tab while in \\cite{} will split the window and either view your bibitem entries (if any) or load your bibtex file.  Then you can go to the entry you want, press Enter, and the citation will be copied into \\cite{}.  This was inspired by reftex, an emacs package.","3":"Improved citation lookup.  Now pressing tab while in \\cite{} will split the window and either view your bibitem entries (if any) or load your bibtex file.  Then you can go to the entry you want, press Enter, and the citation will be copied into \\cite{}.  This was inspired by reftex, an emacs package.","package":"auctex.vim","4":"auctex.vim","src_id":"7944","5":"7944","creation_date":"1195051472","6":"1195051472"},{"0":"162","vim_version":"7.0","1":"7.0","script_version":"2.0011","2":"2.0011","version_comment":"Yet another small improvement in the tab map.","3":"Yet another small improvement in the tab map.","package":"auctex.vim","4":"auctex.vim","src_id":"7795","5":"7795","creation_date":"1192406812","6":"1192406812"},{"0":"162","vim_version":"6.0","1":"6.0","script_version":"2.0010","2":"2.0010","version_comment":"Made a small improvement in the tab key map.","3":"Made a small improvement in the tab key map.","package":"auctex.vim","4":"auctex.vim","src_id":"7747","5":"7747","creation_date":"1191489561","6":"1191489561"},{"0":"162","vim_version":"7.0","1":"7.0","script_version":"2.0009","2":"2.0009","version_comment":"One small change.  To change an environment, type S-F1 through S-F5.  This replaces the control key, which is used for other things in KDE.  Otherwise, there seems to be no reason to change the script, please send suggestions if you think otherwise.","3":"One small change.  To change an environment, type S-F1 through S-F5.  This replaces the control key, which is used for other things in KDE.  Otherwise, there seems to be no reason to change the script, please send suggestions if you think otherwise.","package":"auctex.vim","4":"auctex.vim","src_id":"7627","5":"7627","creation_date":"1189153292","6":"1189153292"},{"0":"162","vim_version":"6.0","1":"6.0","script_version":"2.0008","2":"2.0008","version_comment":"Inspired by LaTeX-Suite, the tab key has some new uses.  Inside \\ref{}, it opens a subwindow with the reference keys.  Pressing enter will insert that reference.\r\nDitto for \\cite{}.  Pressing enter within the bibtex reference will insert the proper \r\ncitation key.","3":"Inspired by LaTeX-Suite, the tab key has some new uses.  Inside \\ref{}, it opens a subwindow with the reference keys.  Pressing enter will insert that reference.\r\nDitto for \\cite{}.  Pressing enter within the bibtex reference will insert the proper \r\ncitation key.","package":"auctex.vim","4":"auctex.vim","src_id":"3291","5":"3291","creation_date":"1091191728","6":"1091191728"},{"0":"162","vim_version":"6.0","1":"6.0","script_version":"2.0007","2":"2.0007","version_comment":"Fixed a bug involving changes of environment.  (Control-F5)","3":"Fixed a bug involving changes of environment.  (Control-F5)","package":"auctex.vim","4":"auctex.vim","src_id":"2843","5":"2843","creation_date":"1079589249","6":"1079589249"},{"0":"162","vim_version":"6.0","1":"6.0","script_version":"2.0006","2":"2.0006","version_comment":"The tab key now does word completion \r\noutside of a math environment, or \r\nproduces a tab at the beginning of the \r\nline or if the previous character is a \r\nspace.  Within a math environment, it takes you to the next set of \r\nparentheses, or to the end of the \r\nenvironment.  Other small fixes.","3":"The tab key now does word completion \r\noutside of a math environment, or \r\nproduces a tab at the beginning of the \r\nline or if the previous character is a \r\nspace.  Within a math environment, it takes you to the next set of \r\nparentheses, or to the end of the \r\nenvironment.  Other small fixes.","package":"auctex.vim","4":"auctex.vim","src_id":"2141","5":"2141","creation_date":"1057913802","6":"1057913802"},{"0":"162","vim_version":"6.0","1":"6.0","script_version":"2.0005","2":"2.0005","version_comment":"Fixed the last bug in this version\r\n(I hope).","3":"Fixed the last bug in this version\r\n(I hope).","package":"auctex.vim","4":"auctex.vim","src_id":"1533","5":"1533","creation_date":"1039156418","6":"1039156418"},{"0":"162","vim_version":"6.0","1":"6.0","script_version":"2.0004","2":"2.0004","version_comment":"Now running latex automatically\r\ntakes you to the error (if any).\r\nAlso, corrected a bug.","3":"Now running latex automatically\r\ntakes you to the error (if any).\r\nAlso, corrected a bug.","package":"auctex.vim","4":"auctex.vim","src_id":"1522","5":"1522","creation_date":"1038810958","6":"1038810958"},{"0":"162","vim_version":"6.0","1":"6.0","script_version":"2.0003","2":"2.0003","version_comment":"Fixed a bug in the automatic line\r\nbreaking.  Also, the script is now\r\neasier to read and customize.","3":"Fixed a bug in the automatic line\r\nbreaking.  Also, the script is now\r\neasier to read and customize.","package":"auctex.vim","4":"auctex.vim","src_id":"1395","5":"1395","creation_date":"1037008160","6":"1037008160"},{"0":"162","vim_version":"6.0","1":"6.0","script_version":"2.0002","2":"2.0002","version_comment":"Fixed a bug","3":"Fixed a bug","package":"auctex.vim","4":"auctex.vim","src_id":"1342","5":"1342","creation_date":"1035787701","6":"1035787701"},{"0":"162","vim_version":"6.0","1":"6.0","script_version":"2.0001","2":"2.0001","version_comment":"Used the \"mapleader\" variable to make\r\nit easier to customize some macros.","3":"Used the \"mapleader\" variable to make\r\nit easier to customize some macros.","package":"auctex.vim","4":"auctex.vim","src_id":"1332","5":"1332","creation_date":"1035363188","6":"1035363188"},{"0":"162","vim_version":"6.0","1":"6.0","script_version":"2.0","2":"2.0","version_comment":"auctex.vim is now compatible with both\r\nlatex and amslatex.  See the file for \r\ndetails.  This mostly affects the function keys, which are used to enter the most common environments.","3":"auctex.vim is now compatible with both\r\nlatex and amslatex.  See the file for \r\ndetails.  This mostly affects the function keys, which are used to enter the most common environments.","package":"auctex.vim","4":"auctex.vim","src_id":"1279","5":"1279","creation_date":"1033716752","6":"1033716752"},{"0":"162","vim_version":"6.0","1":"6.0","script_version":"1.6.1","2":"1.6.1","version_comment":"Added support for the ampersand macro\r\nin the tabular environment.  Suggested\r\nby Johannes Ranke.","3":"Added support for the ampersand macro\r\nin the tabular environment.  Suggested\r\nby Johannes Ranke.","package":"auctex.vim","4":"auctex.vim","src_id":"1183","5":"1183","creation_date":"1031032789","6":"1031032789"},{"0":"162","vim_version":"6.0","1":"6.0","script_version":"1.6","2":"1.6","version_comment":"Extensive code clean-up, with many \r\nsuggestions by Peppe Guldberg.  Various \r\nimprovements and fixes.  Some emacs \r\nbindings included for convenience.  \r\nVi purists can delete these!","3":"Extensive code clean-up, with many \r\nsuggestions by Peppe Guldberg.  Various \r\nimprovements and fixes.  Some emacs \r\nbindings included for convenience.  \r\nVi purists can delete these!","package":"auctex.vim","4":"auctex.vim","src_id":"1052","5":"1052","creation_date":"1027679837","6":"1027679837"},{"0":"162","vim_version":"6.0","1":"6.0","script_version":"1.5","2":"1.5","version_comment":"Fixed the <F5> macro for the entering\r\nenvironments (thanks to Peppe Guldberg and Torsten Wolf).  Improved the macros\r\nfor modifying brackets.  A few other \r\nsmall changes, too.","3":"Fixed the <F5> macro for the entering\r\nenvironments (thanks to Peppe Guldberg and Torsten Wolf).  Improved the macros\r\nfor modifying brackets.  A few other \r\nsmall changes, too.","package":"auctex.vim","4":"auctex.vim","src_id":"943","5":"943","creation_date":"1024746029","6":"1024746029"},{"0":"162","vim_version":"6.0","1":"6.0","script_version":"1.01","2":"1.01","version_comment":"Corrected a bug in the bracket macros.","3":"Corrected a bug in the bracket macros.","package":"auctex.vim","4":"auctex.vim","src_id":"416","5":"416","creation_date":"1007902546","6":"1007902546"},{"0":"162","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"auctex.vim","4":"auctex.vim","src_id":"395","5":"395","creation_date":"1007360882","6":"1007360882"}]},"161":{"script_id":"161","0":"161","script_name":"FavMenu.vim","1":"FavMenu.vim","script_type":"utility","2":"utility","summary":"A new menu, like IE's Favourites, or Netscape's Bookmark","3":"A new menu, like IE's Favourites, or Netscape's Bookmark","description":"Adds a new menu to vim\r\nYou can add your favourite files (and dirs) into it, and open them later by clicking on the corresponding menu item.\r\nThe file list is persistent, data is stored in a file, which is the value of the $FAVOURITES\r\nThis variable should hold the name of your favourites files with full path.\r\nSo it must look like \"~\/.vim_favourites\" or 'c:\\program files\\vim\\_favourites'.\r\n","4":"Adds a new menu to vim\r\nYou can add your favourite files (and dirs) into it, and open them later by clicking on the corresponding menu item.\r\nThe file list is persistent, data is stored in a file, which is the value of the $FAVOURITES\r\nThis variable should hold the name of your favourites files with full path.\r\nSo it must look like \"~\/.vim_favourites\" or 'c:\\program files\\vim\\_favourites'.\r\n","install_details":"Drop it into your plugin directory.","5":"Drop it into your plugin directory.","first_name":"Gergely","6":"Gergely","last_name":"Kontra","7":"Kontra","releases":[{"0":"161","vim_version":"7.0","1":"7.0","script_version":"0.34","2":"0.34","version_comment":"Thank this bugfix release to Zhen-Huan Hu\r\n\r\n* Fixed bug when $LANG is empty\r\n* Use _vimfavourites as default file name for Windows\r\n\r\n!!! New version of script follows vim filename conventions, which means prior windows users should rename their .vimfavourites files to _vimfavourites !!!\r\n","3":"Thank this bugfix release to Zhen-Huan Hu\r\n\r\n* Fixed bug when $LANG is empty\r\n* Use _vimfavourites as default file name for Windows\r\n\r\n!!! New version of script follows vim filename conventions, which means prior windows users should rename their .vimfavourites files to _vimfavourites !!!\r\n","package":"FavMenu.vim","4":"FavMenu.vim","src_id":"24440","5":"24440","creation_date":"1470987396","6":"1470987396"},{"0":"161","vim_version":"7.0","1":"7.0","script_version":"0.33","2":"0.33","version_comment":"* Spanish translation (thanks to Switcher)\r\n* bugfix","3":"* Spanish translation (thanks to Switcher)\r\n* bugfix","package":"FavMenu.vim","4":"FavMenu.vim","src_id":"19452","5":"19452","creation_date":"1359541189","6":"1359541189"},{"0":"161","vim_version":"6.0","1":"6.0","script_version":"0.32","2":"0.32","version_comment":"Added Hungarian translation","3":"Added Hungarian translation","package":"FavMenu.vim","4":"FavMenu.vim","src_id":"672","5":"672","creation_date":"1015837496","6":"1015837496"},{"0":"161","vim_version":"6.0","1":"6.0","script_version":"0.3","2":"0.3","version_comment":"New features:\r\n* Limited path size (set PATHSIZELIMIT)\r\n* It closes the file even when 'hidden' is set\r\n* Synchronize if +clientserver is available","3":"New features:\r\n* Limited path size (set PATHSIZELIMIT)\r\n* It closes the file even when 'hidden' is set\r\n* Synchronize if +clientserver is available","package":"FavMenu.vim","4":"FavMenu.vim","src_id":"538","5":"538","creation_date":"1012806942","6":"1012806942"},{"0":"161","vim_version":"6.0","1":"6.0","script_version":"0.22","2":"0.22","version_comment":"* Nice fallbacks to the vars.\r\n* fav_menu is renamed to OPEN_FUNC Sorry for the inconvinience.\r\n* Menu shortcuts","3":"* Nice fallbacks to the vars.\r\n* fav_menu is renamed to OPEN_FUNC Sorry for the inconvinience.\r\n* Menu shortcuts","package":"FavMenu.vim","4":"FavMenu.vim","src_id":"521","5":"521","creation_date":"1012372708","6":"1012372708"},{"0":"161","vim_version":"6.0","1":"6.0","script_version":"0.21","2":"0.21","version_comment":"Bug fixes","3":"Bug fixes","package":"FavMenu.vim","4":"FavMenu.vim","src_id":"474","5":"474","creation_date":"1011072730","6":"1011072730"},{"0":"161","vim_version":"6.0","1":"6.0","script_version":"0.2","2":"0.2","version_comment":"* Fixed bug, which caused same files to hide each other\r\n* Your favourite files must be located at $FAVOURITES\r\n* You can Edit the favourites. Menus will updated, when you save\r\n* When you click on the menu, it invokes the fav_fun function\r\n* You can choose cascade delete menu by defining fav_cascade_del (at startup!)\r\n* You can add directories to your favourites. Thanks to the_intellectual_person <arun_kumar_ks@hotmail.com>, who gave me a patch for this","3":"* Fixed bug, which caused same files to hide each other\r\n* Your favourite files must be located at $FAVOURITES\r\n* You can Edit the favourites. Menus will updated, when you save\r\n* When you click on the menu, it invokes the fav_fun function\r\n* You can choose cascade delete menu by defining fav_cascade_del (at startup!)\r\n* You can add directories to your favourites. Thanks to the_intellectual_person <arun_kumar_ks@hotmail.com>, who gave me a patch for this","package":"FavMenu.vim","4":"FavMenu.vim","src_id":"454","5":"454","creation_date":"1010644174","6":"1010644174"},{"0":"161","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"FavMenu.vim","4":"FavMenu.vim","src_id":"394","5":"394","creation_date":"1007359397","6":"1007359397"}]},"160":{"script_id":"160","0":"160","script_name":"gtkvim.tgz","1":"gtkvim.tgz","script_type":"utility","2":"utility","summary":"GTK+ widget interface to gvim","3":"GTK+ widget interface to gvim","description":"C source to 'GtkVim' widget, which embeds a gvim into your application as if it were a normal widget (actually runs a gvim as another process, displaying in your widget via a GtkSocket).\r\n\r\nThe current version is for GTK2, and unfortunately requires a pached vim.  This is pending, should make it into vim 7.0 in some fashion, and may even make it into 6.4.  I'll update this note as and when a decision is made.\r\n\r\nNext step I guess is to extend GtkVim to be a full Bonobo (?) widget to allow more flexible use in applications which support that (like evolution, I think).\r\n\r\n==== Old GTK1 notes ====\r\n\r\nVersions 1.x require a GTK+ gvim 6.0 and probably GTK+ 1.2.8 or later.\r\n\r\nIf you have focusing problems, you may also require the following patch to your GTK libraries (inc. the latest [at time of writing] 1.2.10) for automatic focusing (e.g., upon <Tab>) to work correctly.  Point-and-click activation will still work OK without this patch.\r\n\r\nCurrently still \/not\/ working is the ability to set the GtkVim widget's focus at startup (gtk_widget_grab_focus() or gtk_window_set_focus()).\r\n\r\n--- gtk\/gtkwindow.c.focus\tFri Mar  9 18:39:16 2001\r\n+++ gtk\/gtkwindow.c\tThu Jul  5 10:34:00 2001\r\n@@ -985,7 +985,13 @@\r\n       break;\r\n     case EnterNotify:\r\n     case LeaveNotify:\r\n-      if (xev->xcrossing.detail != NotifyInferior &&\r\n+      \/* We only track the actual destination of keyboard events for real\r\n+       * toplevels, not for embedded toplevels such as GtkPlug. The reason for\r\n+       * this is that GtkPlug redirects events so the widget may effectively not\r\n+       * have the focus even if it actually has the focus.\r\n+       *\/\r\n+      if (gdk_window_get_parent (GTK_WIDGET (window)->window) == GDK_ROOT_PARENT () &&\r\n+\t  xev->xcrossing.detail != NotifyInferior &&\r\n \t  xev->xcrossing.focus && !window->window_has_focus)\r\n \t{\r\n \t  window->window_has_pointer_focus = (xev->xany.type == EnterNotify) ? TRUE : FALSE;\r\n","4":"C source to 'GtkVim' widget, which embeds a gvim into your application as if it were a normal widget (actually runs a gvim as another process, displaying in your widget via a GtkSocket).\r\n\r\nThe current version is for GTK2, and unfortunately requires a pached vim.  This is pending, should make it into vim 7.0 in some fashion, and may even make it into 6.4.  I'll update this note as and when a decision is made.\r\n\r\nNext step I guess is to extend GtkVim to be a full Bonobo (?) widget to allow more flexible use in applications which support that (like evolution, I think).\r\n\r\n==== Old GTK1 notes ====\r\n\r\nVersions 1.x require a GTK+ gvim 6.0 and probably GTK+ 1.2.8 or later.\r\n\r\nIf you have focusing problems, you may also require the following patch to your GTK libraries (inc. the latest [at time of writing] 1.2.10) for automatic focusing (e.g., upon <Tab>) to work correctly.  Point-and-click activation will still work OK without this patch.\r\n\r\nCurrently still \/not\/ working is the ability to set the GtkVim widget's focus at startup (gtk_widget_grab_focus() or gtk_window_set_focus()).\r\n\r\n--- gtk\/gtkwindow.c.focus\tFri Mar  9 18:39:16 2001\r\n+++ gtk\/gtkwindow.c\tThu Jul  5 10:34:00 2001\r\n@@ -985,7 +985,13 @@\r\n       break;\r\n     case EnterNotify:\r\n     case LeaveNotify:\r\n-      if (xev->xcrossing.detail != NotifyInferior &&\r\n+      \/* We only track the actual destination of keyboard events for real\r\n+       * toplevels, not for embedded toplevels such as GtkPlug. The reason for\r\n+       * this is that GtkPlug redirects events so the widget may effectively not\r\n+       * have the focus even if it actually has the focus.\r\n+       *\/\r\n+      if (gdk_window_get_parent (GTK_WIDGET (window)->window) == GDK_ROOT_PARENT () &&\r\n+\t  xev->xcrossing.detail != NotifyInferior &&\r\n \t  xev->xcrossing.focus && !window->window_has_focus)\r\n \t{\r\n \t  window->window_has_pointer_focus = (xev->xany.type == EnterNotify) ? TRUE : FALSE;\r\n","install_details":"Unpack the tgz file ('tar zxf gtkvim.tgz') somewhere and 'make' in the new directory it creates.  Sorry, no configure or anything, but it's pretty minimalist so shouldn't cause any problems.\r\n\r\nLink the gtkvim.o with your app.  See included example cadged from the GTK+ release ('rangewidgets').","5":"Unpack the tgz file ('tar zxf gtkvim.tgz') somewhere and 'make' in the new directory it creates.  Sorry, no configure or anything, but it's pretty minimalist so shouldn't cause any problems.\r\n\r\nLink the gtkvim.o with your app.  See included example cadged from the GTK+ release ('rangewidgets').","first_name":"Neil","6":"Neil","last_name":"Bird","7":"Bird","releases":[{"0":"160","vim_version":"6.0","1":"6.0","script_version":"2.0","2":"2.0","version_comment":"Updated to build against GTK2 by default.","3":"Updated to build against GTK2 by default.","package":"gtkvim.tgz","4":"gtkvim.tgz","src_id":"5452","5":"5452","creation_date":"1142569889","6":"1142569889"},{"0":"160","vim_version":"6.0","1":"6.0","script_version":"1.7","2":"1.7","version_comment":"Fixed coredump due to incorrectly initialised string (Evan Martin).\r\n\r\n","3":"Fixed coredump due to incorrectly initialised string (Evan Martin).\r\n\r\n","package":"gtkvim.tgz","4":"gtkvim.tgz","src_id":"568","5":"568","creation_date":"1013128562","6":"1013128562"},{"0":"160","vim_version":"6.0","1":"6.0","script_version":"1.6","2":"1.6","version_comment":"Initial upload","3":"Initial upload","package":"gtkvim.tgz","4":"gtkvim.tgz","src_id":"391","5":"391","creation_date":"1007351725","6":"1007351725"}]},"159":{"script_id":"159","0":"159","script_name":"minibufexpl.vim","1":"minibufexpl.vim","script_type":"utility","2":"utility","summary":"Elegant buffer explorer - takes very little screen space","3":"Elegant buffer explorer - takes very little screen space","description":"Several modern GUI editors list your open buffers as tabs along the top or bottom of your screen (VisualStudio, DreamWeaver, EditPlus and UltraEdit come to mind), now we have this feature in VIM! You can checkout a screenshot here: http:\/\/www.wavell.net\/vim\/vim_screenshot.gif.\r\n\r\nYou can quickly switch buffers by double-clicking the appropriate \"tab\" (if you don't want to use the mouse just put the cursor on the \"tab\" and press enter). As you open and close buffers the tabs get updated. Buffers that are modified get visually marked and buffers that are open in a window get visually marked. The -MiniBufferExplorer- opens automatically when you open more than one eligible buffer (no need to open the explorer if you\u00e2\u0080\u0099re only editing one file.) -MiniBufExplorer- doesn't bother showing non-modifiable or hidden buffers. You can delete buffers by selecting them and pressing d on the keyboard. \r\n\r\nWhen you are in the -MiniBufExplorer- window, Tab and Shift-Tab move forward and backward respectively through the buffer list. \r\n\r\nThere are a growing number of optional features in this script that are enabled by letting variables in your .vimrc:\r\n\r\n  control + the vim direction keys [hjkl] can be made to move you between windows. \r\n  control + arrow keys can be made to do the same thing\r\n  control + tab & shift + control + tab can be setup to switch through your open windows (like in MS Windows)\r\n  control + tab & shift + control + tab can alternatively be setup to cycle forwards and backwards through your modifiable buffers in the current window\r\n\r\nNOTE: Some versions of vim don't support all of the key mappings that this script uses so you may experience degraded functionality. For example on Solaris SHIFT-TAB appears to fire the regular TAB mappings (same for console and gvim.) Also CONTROL+ARROWS appears to work in gvim on Solaris, but not in my xterm. All of the key bindings appear to work in Windows.\r\n\r\n[Thanks to Jeff Lanzarotta for his BufExplorer plugin (http:\/\/vim.sourceforge.net\/scripts\/script.php?script_id=42) that got me started down this slippery slope.]\r\n\r\n[While I still use vim to edit the odd file, I spend most of my time in one flavor or the other of eclipse (with the vim plugin of course.) As such this plugin has not seen any love from me in a very long time. Recently I've been contacted by several folks who have made significant progress on this script. As I'm not able to validate their work I'm currently not up for posting their changes. However, I'm very happy to provide a pointer to their work: Checkout https:\/\/github.com\/fholgado\/minibufexpl.vim ]\r\n\r\n[Also, it appears that the TabBar plugin is a variant on MBE, you can read about what they have done here: http:\/\/www.vim.org\/scripts\/script.php?script_id=1338 ]","4":"Several modern GUI editors list your open buffers as tabs along the top or bottom of your screen (VisualStudio, DreamWeaver, EditPlus and UltraEdit come to mind), now we have this feature in VIM! You can checkout a screenshot here: http:\/\/www.wavell.net\/vim\/vim_screenshot.gif.\r\n\r\nYou can quickly switch buffers by double-clicking the appropriate \"tab\" (if you don't want to use the mouse just put the cursor on the \"tab\" and press enter). As you open and close buffers the tabs get updated. Buffers that are modified get visually marked and buffers that are open in a window get visually marked. The -MiniBufferExplorer- opens automatically when you open more than one eligible buffer (no need to open the explorer if you\u00e2\u0080\u0099re only editing one file.) -MiniBufExplorer- doesn't bother showing non-modifiable or hidden buffers. You can delete buffers by selecting them and pressing d on the keyboard. \r\n\r\nWhen you are in the -MiniBufExplorer- window, Tab and Shift-Tab move forward and backward respectively through the buffer list. \r\n\r\nThere are a growing number of optional features in this script that are enabled by letting variables in your .vimrc:\r\n\r\n  control + the vim direction keys [hjkl] can be made to move you between windows. \r\n  control + arrow keys can be made to do the same thing\r\n  control + tab & shift + control + tab can be setup to switch through your open windows (like in MS Windows)\r\n  control + tab & shift + control + tab can alternatively be setup to cycle forwards and backwards through your modifiable buffers in the current window\r\n\r\nNOTE: Some versions of vim don't support all of the key mappings that this script uses so you may experience degraded functionality. For example on Solaris SHIFT-TAB appears to fire the regular TAB mappings (same for console and gvim.) Also CONTROL+ARROWS appears to work in gvim on Solaris, but not in my xterm. All of the key bindings appear to work in Windows.\r\n\r\n[Thanks to Jeff Lanzarotta for his BufExplorer plugin (http:\/\/vim.sourceforge.net\/scripts\/script.php?script_id=42) that got me started down this slippery slope.]\r\n\r\n[While I still use vim to edit the odd file, I spend most of my time in one flavor or the other of eclipse (with the vim plugin of course.) As such this plugin has not seen any love from me in a very long time. Recently I've been contacted by several folks who have made significant progress on this script. As I'm not able to validate their work I'm currently not up for posting their changes. However, I'm very happy to provide a pointer to their work: Checkout https:\/\/github.com\/fholgado\/minibufexpl.vim ]\r\n\r\n[Also, it appears that the TabBar plugin is a variant on MBE, you can read about what they have done here: http:\/\/www.vim.org\/scripts\/script.php?script_id=1338 ]","install_details":"Copy minibufexpl.vim into your plugin directory. Or :source minibufexpl.vim. That is all you need to get started.\r\n\r\nIf you want to enable extra functionality (documented in the source) you might want to add the following to your .vimrc:\r\n\r\n  let g:miniBufExplMapWindowNavVim = 1\r\n  let g:miniBufExplMapWindowNavArrows = 1\r\n  let g:miniBufExplMapCTabSwitchBufs = 1\r\n  let g:miniBufExplModSelTarget = 1\r\n\r\nThese are options that I expect most user will enjoy. \r\n\r\nYou can configure things like how tabs wrap, how big or small the explorer window is, if the explorer window is horizonal or vertical, the use of single or double click for buffer selection, what colors are used for the tabs in different states, how many buffers need to be open before the explorer window opens, etc. There are also some commands that you can use in your own key bindings for simple buffer manipulation. All of these options and more are documented at the top of the source file.","5":"Copy minibufexpl.vim into your plugin directory. Or :source minibufexpl.vim. That is all you need to get started.\r\n\r\nIf you want to enable extra functionality (documented in the source) you might want to add the following to your .vimrc:\r\n\r\n  let g:miniBufExplMapWindowNavVim = 1\r\n  let g:miniBufExplMapWindowNavArrows = 1\r\n  let g:miniBufExplMapCTabSwitchBufs = 1\r\n  let g:miniBufExplModSelTarget = 1\r\n\r\nThese are options that I expect most user will enjoy. \r\n\r\nYou can configure things like how tabs wrap, how big or small the explorer window is, if the explorer window is horizonal or vertical, the use of single or double click for buffer selection, what colors are used for the tabs in different states, how many buffers need to be open before the explorer window opens, etc. There are also some commands that you can use in your own key bindings for simple buffer manipulation. All of these options and more are documented at the top of the source file.","first_name":"bindu","6":"bindu","last_name":"wavell","7":"wavell","releases":[{"0":"159","vim_version":"6.0","1":"6.0","script_version":"6.3.2","2":"6.3.2","version_comment":"For some reason there was still a call to StopExplorer with 2 params. Many thanks to Jason Mills for reporting this!\r\n","3":"For some reason there was still a call to StopExplorer with 2 params. Many thanks to Jason Mills for reporting this!\r\n","package":"minibufexpl.vim","4":"minibufexpl.vim","src_id":"3640","5":"3640","creation_date":"1100766890","6":"1100766890"},{"0":"159","vim_version":"6.0","1":"6.0","script_version":"6.3.1","2":"6.3.1","version_comment":"Added g:miniBufExplForceSyntaxEnable option for folks that are experiencing the vim bug where buffers show up without highlighting when another buffer has been closed, quit, wiped or deleted. This resolves all known issues with buffers loosing their highlighting. If you find a case that is not resolved, please report it :)\r\n\r\nFolded source so that it's easier to navigate","3":"Added g:miniBufExplForceSyntaxEnable option for folks that are experiencing the vim bug where buffers show up without highlighting when another buffer has been closed, quit, wiped or deleted. This resolves all known issues with buffers loosing their highlighting. If you find a case that is not resolved, please report it :)\r\n\r\nFolded source so that it's easier to navigate","package":"minibufexpl.vim","4":"minibufexpl.vim","src_id":"3195","5":"3195","creation_date":"1088593708","6":"1088593708"},{"0":"159","vim_version":"6.0","1":"6.0","script_version":"6.3.0","2":"6.3.0","version_comment":"FEATURE RELEASE:\r\no Added optional single click to select buffers in the MBE window\r\no MBE is no longer included in :ls output\r\no Added the ability to have your tabs show up in a vertical window\r\no Autosize vertical explorer window\r\n\r\nNOTE: Folks who use the single click feature in TagList should wait to use the MBE single click feature until the next release of TagList (~2 weeks) which includes a patch to allow both explorers to utilize single click.\r\n\r\nCHANGE\r\no g:miniBufExplMaxHeight was renamed g:miniBufExplMaxSize \r\no g:miniBufExplMinHeight was renamed g:miniBufExplMinSize \r\n\r\nThe old settings are backwards compatible if you don't use the new settings. The old settings are depreciated.\r\n","3":"FEATURE RELEASE:\r\no Added optional single click to select buffers in the MBE window\r\no MBE is no longer included in :ls output\r\no Added the ability to have your tabs show up in a vertical window\r\no Autosize vertical explorer window\r\n\r\nNOTE: Folks who use the single click feature in TagList should wait to use the MBE single click feature until the next release of TagList (~2 weeks) which includes a patch to allow both explorers to utilize single click.\r\n\r\nCHANGE\r\no g:miniBufExplMaxHeight was renamed g:miniBufExplMaxSize \r\no g:miniBufExplMinHeight was renamed g:miniBufExplMinSize \r\n\r\nThe old settings are backwards compatible if you don't use the new settings. The old settings are depreciated.\r\n","package":"minibufexpl.vim","4":"minibufexpl.vim","src_id":"3179","5":"3179","creation_date":"1088062051","6":"1088062051"},{"0":"159","vim_version":"6.0","1":"6.0","script_version":"6.2.8","2":"6.2.8","version_comment":"Added an option to stop MBE from targeting non-modifiable buffers when switching buffers. Those of you who use buffer explorers like taglist, project, etc and would like MBE to try not to place selected buffers into explorer windows will like this one :) To get this working download the latest version of minibufexpl.vim and put \"let g:miniBufExplModSelTarget = 1\" into your .vimrc. This is not a 100% guarantee, but it does a good job of trying to avoice explorer windows. Thanks to A.W. Law for the inspiration for this.\r\n","3":"Added an option to stop MBE from targeting non-modifiable buffers when switching buffers. Those of you who use buffer explorers like taglist, project, etc and would like MBE to try not to place selected buffers into explorer windows will like this one :) To get this working download the latest version of minibufexpl.vim and put \"let g:miniBufExplModSelTarget = 1\" into your .vimrc. This is not a 100% guarantee, but it does a good job of trying to avoice explorer windows. Thanks to A.W. Law for the inspiration for this.\r\n","package":"minibufexpl.vim","4":"minibufexpl.vim","src_id":"3103","5":"3103","creation_date":"1086600178","6":"1086600178"},{"0":"159","vim_version":"6.0","1":"6.0","script_version":"6.2.7","2":"6.2.7","version_comment":"Very minor bug fix for people who want to set loaded_minibufexplorer in their .vimrc in order to stop MBE from loading. 99.99% of users do not need this update. Thanks to bash for finding this.\r\n","3":"Very minor bug fix for people who want to set loaded_minibufexplorer in their .vimrc in order to stop MBE from loading. 99.99% of users do not need this update. Thanks to bash for finding this.\r\n","package":"minibufexpl.vim","4":"minibufexpl.vim","src_id":"3056","5":"3056","creation_date":"1085406091","6":"1085406091"},{"0":"159","vim_version":"6.0","1":"6.0","script_version":"6.2.6","2":"6.2.6","version_comment":"Very minor update: Moved history to end of source file. Updated highlighting documentation. Created global commands MBEbn and MBEbp that can be used in mappings if folks want to cycle buffers while skipping non-eligible buffers.","3":"Very minor update: Moved history to end of source file. Updated highlighting documentation. Created global commands MBEbn and MBEbp that can be used in mappings if folks want to cycle buffers while skipping non-eligible buffers.","package":"minibufexpl.vim","4":"minibufexpl.vim","src_id":"1951","5":"1951","creation_date":"1051691851","6":"1051691851"},{"0":"159","vim_version":"6.0","1":"6.0","script_version":"6.2.5","2":"6.2.5","version_comment":"Added a ToggleExplorer option and updated the documentation.","3":"Added a ToggleExplorer option and updated the documentation.","package":"minibufexpl.vim","4":"minibufexpl.vim","src_id":"1914","5":"1914","creation_date":"1050271464","6":"1050271464"},{"0":"159","vim_version":"6.0","1":"6.0","script_version":"6.2.4","2":"6.2.4","version_comment":"MiniBufExplorer is now compatible with :set hidden.","3":"MiniBufExplorer is now compatible with :set hidden.","package":"minibufexpl.vim","4":"minibufexpl.vim","src_id":"1877","5":"1877","creation_date":"1048984525","6":"1048984525"},{"0":"159","vim_version":"6.0","1":"6.0","script_version":"6.2.3","2":"6.2.3","version_comment":"Added an optional feature to cause tabs to wrap. i.e. you should never get a tab name split across two lines (there is a potential issue if you have filenames with spaces, but otherwise this works.)","3":"Added an optional feature to cause tabs to wrap. i.e. you should never get a tab name split across two lines (there is a potential issue if you have filenames with spaces, but otherwise this works.)","package":"minibufexpl.vim","4":"minibufexpl.vim","src_id":"1858","5":"1858","creation_date":"1048722968","6":"1048722968"},{"0":"159","vim_version":"6.0","1":"6.0","script_version":"6.2.2","2":"6.2.2","version_comment":"Changed the way the g:miniBufExplorerMoreThanOne\r\nglobal is handled. You can set this to the number\r\nof eligible buffers you want to be loaded before\r\nthe MBE window is loaded. Setting it to 0 causes\r\nthe MBE window to be opened even if there are no\r\nbuffers. Setting it to 4 causes the window to stay\r\nclosed until the 4th eligible buffer is loaded.\r\n\r\nAdded a MinHeight option. This is nice if you want\r\nthe MBE window to always take the same amount of\r\nspace. For example set MaxHeight and MinHeight to 2\r\nand set MoreThanOne to 0 and you will always have\r\na 2 row (plus the ruler :) MBE window.\r\n\r\nI now setlocal foldcomun=0 and nonumber in the MBE \r\nwindow. This is for those of you that like to have\r\nthese options turned on locally. I'm assuming noone\r\noutthere wants foldcolumns and line numbers in the\r\nMBE window? :)\r\n\r\nFixed a bug where an empty MBE window was taking half\r\nof the screen (partly why the MinHeight option was \r\nadded.)","3":"Changed the way the g:miniBufExplorerMoreThanOne\r\nglobal is handled. You can set this to the number\r\nof eligible buffers you want to be loaded before\r\nthe MBE window is loaded. Setting it to 0 causes\r\nthe MBE window to be opened even if there are no\r\nbuffers. Setting it to 4 causes the window to stay\r\nclosed until the 4th eligible buffer is loaded.\r\n\r\nAdded a MinHeight option. This is nice if you want\r\nthe MBE window to always take the same amount of\r\nspace. For example set MaxHeight and MinHeight to 2\r\nand set MoreThanOne to 0 and you will always have\r\na 2 row (plus the ruler :) MBE window.\r\n\r\nI now setlocal foldcomun=0 and nonumber in the MBE \r\nwindow. This is for those of you that like to have\r\nthese options turned on locally. I'm assuming noone\r\noutthere wants foldcolumns and line numbers in the\r\nMBE window? :)\r\n\r\nFixed a bug where an empty MBE window was taking half\r\nof the screen (partly why the MinHeight option was \r\nadded.)","package":"minibufexpl.vim","4":"minibufexpl.vim","src_id":"1853","5":"1853","creation_date":"1048554818","6":"1048554818"},{"0":"159","vim_version":"6.0","1":"6.0","script_version":"6.2.1","2":"6.2.1","version_comment":"If MBE is the only window (because of :bd for example) and there are still eligible buffers then one of them will be displayed.\r\n\r\nThe <Leader>mbe mapping now highlights the buffer from the current window.\r\n\r\nThe delete ('d') binding in the MBE window now restors the cursor position, which can help if you want to delete several buffers in a row that are not at the beginning of the buffer list.\r\n\r\nAdded a new key binding ('p') in the MBE window to switch to the previous window (last edit window)","3":"If MBE is the only window (because of :bd for example) and there are still eligible buffers then one of them will be displayed.\r\n\r\nThe <Leader>mbe mapping now highlights the buffer from the current window.\r\n\r\nThe delete ('d') binding in the MBE window now restors the cursor position, which can help if you want to delete several buffers in a row that are not at the beginning of the buffer list.\r\n\r\nAdded a new key binding ('p') in the MBE window to switch to the previous window (last edit window)","package":"minibufexpl.vim","4":"minibufexpl.vim","src_id":"1841","5":"1841","creation_date":"1048282229","6":"1048282229"},{"0":"159","vim_version":"6.0","1":"6.0","script_version":"6.2.0","2":"6.2.0","version_comment":"Major overhaul of autocommand and list updating code, we now have much better handling of :bd (which is the most requested feature.) As well as resolving other issues where the buffer list would not be updated automatically. The old version tried to trap specific events, this one just updates frequently, but it keeps track and only changes the screen if there has been a change.\r\n\r\nAdded g:miniBufExplMaxHeight variable so you can keep the -MiniBufExplorer- window small when you have lots of buffers (or buffers with long names :)\r\n\r\nImprovement to internal syntax highlighting code I renamed the syntax group names. Anyone who has figured out how to use them already shouldn't have any trouble with the new Nameing :)\r\n\r\nAdded debug mode 3 which writes to a global variable this is fast and doesn't mess with the buffer\/window lists.","3":"Major overhaul of autocommand and list updating code, we now have much better handling of :bd (which is the most requested feature.) As well as resolving other issues where the buffer list would not be updated automatically. The old version tried to trap specific events, this one just updates frequently, but it keeps track and only changes the screen if there has been a change.\r\n\r\nAdded g:miniBufExplMaxHeight variable so you can keep the -MiniBufExplorer- window small when you have lots of buffers (or buffers with long names :)\r\n\r\nImprovement to internal syntax highlighting code I renamed the syntax group names. Anyone who has figured out how to use them already shouldn't have any trouble with the new Nameing :)\r\n\r\nAdded debug mode 3 which writes to a global variable this is fast and doesn't mess with the buffer\/window lists.","package":"minibufexpl.vim","4":"minibufexpl.vim","src_id":"1834","5":"1834","creation_date":"1048134216","6":"1048134216"},{"0":"159","vim_version":"6.0","1":"6.0","script_version":"6.1.0","2":"6.1.0","version_comment":"<Leader>mbc was failing because I was calling one of my own functions with the wrong number of args. Thanks to Gerry Patterson and others for finding this!\r\n","3":"<Leader>mbc was failing because I was calling one of my own functions with the wrong number of args. Thanks to Gerry Patterson and others for finding this!\r\n","package":"minibufexpl.vim","4":"minibufexpl.vim","src_id":"1810","5":"1810","creation_date":"1047608806","6":"1047608806"},{"0":"159","vim_version":"6.0","1":"6.0","script_version":"6.0.9","2":"6.0.9","version_comment":"Double clicking tabs was overwriting the clipboard register on MS Windows but not elsewhere... go figure :). This has now been fixed. Thanks to Shoeb Bhinderwala for reporting this one.","3":"Double clicking tabs was overwriting the clipboard register on MS Windows but not elsewhere... go figure :). This has now been fixed. Thanks to Shoeb Bhinderwala for reporting this one.","package":"minibufexpl.vim","4":"minibufexpl.vim","src_id":"1219","5":"1219","creation_date":"1032297891","6":"1032297891"},{"0":"159","vim_version":"6.0","1":"6.0","script_version":"6.0.8","2":"6.0.8","version_comment":"Apparently some VIM builds are having a hard time with line continuation in scripts so the few that were here have been removed.\r\n\r\n\r\nUpdated debugging code so that debug output is put into a buffer which can then be written to disk or emailed to me when someone is having a major issue. Can also write directly to a file (VERY SLOWLY) on UNIX or Win32 (not 95 or 98 at the moment) or use VIM's echo function to display the output to the screen.\r\n\r\nSeveral people have had issues when the hidden option is turned on. So I have put in several checks to make sure folks know this if they try to use MBE with the option set.","3":"Apparently some VIM builds are having a hard time with line continuation in scripts so the few that were here have been removed.\r\n\r\n\r\nUpdated debugging code so that debug output is put into a buffer which can then be written to disk or emailed to me when someone is having a major issue. Can also write directly to a file (VERY SLOWLY) on UNIX or Win32 (not 95 or 98 at the moment) or use VIM's echo function to display the output to the screen.\r\n\r\nSeveral people have had issues when the hidden option is turned on. So I have put in several checks to make sure folks know this if they try to use MBE with the option set.","package":"minibufexpl.vim","4":"minibufexpl.vim","src_id":"1084","5":"1084","creation_date":"1028657130","6":"1028657130"},{"0":"159","vim_version":"6.0","1":"6.0","script_version":"6.0.7","2":"6.0.7","version_comment":"Major update to how MBE handles buffer deletes. Now deletes are handled through an autocmd so you can now use :bd to delete buffers and the UI keeps in sync. Also made the MBE window go away when there is only one eligible buffer left to edit.","3":"Major update to how MBE handles buffer deletes. Now deletes are handled through an autocmd so you can now use :bd to delete buffers and the UI keeps in sync. Also made the MBE window go away when there is only one eligible buffer left to edit.","package":"minibufexpl.vim","4":"minibufexpl.vim","src_id":"551","5":"551","creation_date":"1012854825","6":"1012854825"},{"0":"159","vim_version":"6.0","1":"6.0","script_version":"6.0.6","2":"6.0.6","version_comment":"Fixed register overwrite bug found by S\u00c3\u00a9bastien Pierre. The @\" register was being overwritten with the selected buffer name when switching buffers, the @\" register is now preserved.","3":"Fixed register overwrite bug found by S\u00c3\u00a9bastien Pierre. The @\" register was being overwritten with the selected buffer name when switching buffers, the @\" register is now preserved.","package":"minibufexpl.vim","4":"minibufexpl.vim","src_id":"515","5":"515","creation_date":"1012209587","6":"1012209587"},{"0":"159","vim_version":"6.0","1":"6.0","script_version":"6.0.5","2":"6.0.5","version_comment":"Added more optional fancy window\/buffer navigation:\r\n\r\nYou can turn on the ability to use control and the arrow keys to move between windows.\r\nYou can turn on the ability to use <C-TAB> and <C-S-TAB> to open the next and previous (respectively) buffer in the current window.\r\nYou can turn on the ability to use <C-TAB> and <C-S-TAB> to switch windows (forward and backwards respectively.)\r\n\r\nFixed an issue with window sizing when we run out of buffers.","3":"Added more optional fancy window\/buffer navigation:\r\n\r\nYou can turn on the ability to use control and the arrow keys to move between windows.\r\nYou can turn on the ability to use <C-TAB> and <C-S-TAB> to open the next and previous (respectively) buffer in the current window.\r\nYou can turn on the ability to use <C-TAB> and <C-S-TAB> to switch windows (forward and backwards respectively.)\r\n\r\nFixed an issue with window sizing when we run out of buffers.","package":"minibufexpl.vim","4":"minibufexpl.vim","src_id":"505","5":"505","creation_date":"1011731470","6":"1011731470"},{"0":"159","vim_version":"6.0","1":"6.0","script_version":"6.0.4","2":"6.0.4","version_comment":"After reading 'Tip #173: Switch between splits very fast (for multi-file editing)' I decided to optionally add control+direction [hjkl] mappings to switch between windows. If you want to enable this feature just put 'let g:miniBufExplMapWindowNav=1\" into your .vimrc.","3":"After reading 'Tip #173: Switch between splits very fast (for multi-file editing)' I decided to optionally add control+direction [hjkl] mappings to switch between windows. If you want to enable this feature just put 'let g:miniBufExplMapWindowNav=1\" into your .vimrc.","package":"minibufexpl.vim","4":"minibufexpl.vim","src_id":"431","5":"431","creation_date":"1008723017","6":"1008723017"},{"0":"159","vim_version":"6.0","1":"6.0","script_version":"6.0.3","2":"6.0.3","version_comment":"Our buffername [MiniBufExplorer] was being treated as a regular expression in some instances and matching several single character file names. Since escaping the '[' and ']' doesn't work on the windows version of vim 6.0 yet, I renamed the buffer -MiniBufExplorer-. This appears to have resolved the issue.","3":"Our buffername [MiniBufExplorer] was being treated as a regular expression in some instances and matching several single character file names. Since escaping the '[' and ']' doesn't work on the windows version of vim 6.0 yet, I renamed the buffer -MiniBufExplorer-. This appears to have resolved the issue.","package":"minibufexpl.vim","4":"minibufexpl.vim","src_id":"430","5":"430","creation_date":"1008720182","6":"1008720182"},{"0":"159","vim_version":"6.0","1":"6.0","script_version":"6.0.2","2":"6.0.2","version_comment":"2 Changes requested by Suresh Govindachar\r\nAdded SplitToEdge option and set it on by default\r\nAdded tab and shift-tab mappings in [MBE] window","3":"2 Changes requested by Suresh Govindachar\r\nAdded SplitToEdge option and set it on by default\r\nAdded tab and shift-tab mappings in [MBE] window","package":"minibufexpl.vim","4":"minibufexpl.vim","src_id":"400","5":"400","creation_date":"1007455937","6":"1007455937"},{"0":"159","vim_version":"6.0","1":"6.0","script_version":"6.0.0","2":"6.0.0","version_comment":"Initial upload","3":"Initial upload","package":"minibufexpl.vim","4":"minibufexpl.vim","src_id":"390","5":"390","creation_date":"1007242548","6":"1007242548"}]},"158":{"script_id":"158","0":"158","script_name":"foldutil.vim","1":"foldutil.vim","script_type":"utility","2":"utility","summary":"Utility for creating folds (using specified match criteria)","3":"Utility for creating folds (using specified match criteria)","description":"  The plugins provides useful commands for the ease of creating folds using\r\n  different match-criteria. They support creating folds in three different\r\n  modes, in the whole buffer, or only in the selected range:\r\n      - block mode\r\n        You give a starting and ending pattern for the blocks.\r\n      - outline mode\r\n        You give a pattern that determines the start of the block. A new\r\n        block automatically starts whenever the pattern is found.\r\n      - non-block mode\r\n        You give a pattern which determines the set of lines that should be\r\n        included in the folds. Useful to see only the matching\/non-matching\r\n        lines with or without context.\r\n                                                                               \r\n  The first set of commands use pattern matching criteria (using the\r\n  built-in =~ operator, see help on |expr-=~|).\r\n  \r\n    FoldMatching - All arguments are optional. The first argument specifies\r\n                   the begin pattern and an optional second argument can be\r\n                   passed to specify an end pattern (for block mode) and\r\n                   additionally the number of context lines to be shown\r\n                   (which defaults to 1 if not specified). To specify an\r\n                   outline mode, a special value of -1 should be specified\r\n                   as context.\r\n        Syntax:\r\n          [range]FoldMatching[!] [pattern] [endPattern] [context]\r\n\r\n        Ex:\r\n          FoldMatching\r\n            Uses current search pattern and creates folds in non-block mode\r\n            with the default context of 1.\r\n          FoldMatching! ^\\s*\/\/ 0\r\n            This potentially folds away all the lines that are not in\r\n            C++\/Java single-line comments such that you can see only those\r\n            comments.\r\n          FoldMatching public -1\r\n            Uses \"public\" as the pattern and creates folds in outline mode.\r\n          FoldMatching \/\\* \\*\/ 0\r\n            Creates folds for all the C++\/Java style block comments with no\r\n            context.\r\n                                                                               \r\n    FoldNonMatching - This is just an alias for \"FoldMatching\" with a bang.\r\n                                                                               \r\n  The following commands use line number as match criteria\r\n  \r\n    FoldShowLines - Pass a comma-separated list of line numbers and an\r\n                    optional number of context lines to show\/hide. All the\r\n                    rest of the lines (excluding those in context) will be\r\n                    folded away. You can also create blocks by specifying an\r\n                    optional list of line numbers as a second argument. You\r\n                    can give a range too.\r\n        Syntax:\r\n          [range]FoldShowLines[!] {lineNumbers} [endLineNumbers] [context]\r\n  \r\n        Ex:\r\n          FoldShowLines 10,50,100 3\r\n            Creates four folds exposing the lines 10, 50 and 100 with a\r\n            context of 3 lines.\r\n          FoldShowLines! 5,15,25 10,20,30 0\r\n            Creates three folds with 5 to 10, 15 to 20 and 25 to 30 as blocks.\r\n                                                                               \r\n    FoldShowMarks - Shows all the lines that have a mark defined in the\r\n                    current buffer, by folding away all the rest of the\r\n                    lines. Only the marks from a-z and A-Z are considered\r\n                    for match criteria.\r\n        Syntax:\r\n          [range]FoldShowMarks [context]\r\n                                                                               \r\n  The following command takes a highlight group as a match criteria, and\r\n    uses it to show\/hide lines.\r\n  \r\n    FoldShowHiGroup - Pass a highlight group name and an optional number of\r\n                    context lines to be shown. All the rest of the lines\r\n                    (excluding those in context) will be folded away. You\r\n                    can also create blocks by specifying an optional end\r\n                    highligh group as a second argument. You can give a\r\n                    range too.\r\n        Syntax:\r\n          [range]FoldShowHiGroup[!] {HiGroup} [endHiGroup] [context]\r\n  \r\n        Ex:\r\n          FoldShowHiGroup Todo\r\n            Folds away all the lines except those that have a TODO item\r\n            mentioned (in Java, this is all the comments containing the\r\n            words TODO or FIXME, by default) with a context of 1 line.\r\n          FoldShowHiGroup Special 0\r\n            In HTML this reveals just the lines containing special characters.\r\n          FoldShowHiGroup! Comment 0\r\n            This will fold away all the comment lines in any language.\r\n  \r\n  The following is purely for convenience to reduce the number of commands\r\n  to be executed (you need to create separate folds).\r\n                                                                               \r\n    FoldShowRange - All the lines are folded except for the lines in the range\r\n                    given. Helps to search only in a range of lines, as it is\r\n                    easy to identify when the cursor goes out of the range.\r\n                    Also consider removing \"search\" and \"jump\" from\r\n                    'foldopen' setting.\r\n        Syntax:\r\n          [range]FoldShowRange\r\n  \r\n        Ex:\r\n          50,500FoldShowRange\r\n  \r\n      The defaults for pattern and context are current search pattern\r\n        (extracted from \/ register) and 1 respectively.\r\n      The outline mode additionally modifies the 'foldtext' such that the\r\n        starting line shows up as the summary line for the fold (without the\r\n        usual dashes and number of lines in the prefix). This allows you to\r\n        view the matched lines more clearly and also follow the same\r\n        indentation as the original (nice when folding code). You can\r\n        however set g:foldutilFoldText to any value that is acceptable for\r\n        'foldtext' and customize this behavior (e.g., to view the number of\r\n        lines in addition to the matched line, set it to something like:\r\n            \"getline(v:foldstart).' <'.(v:foldend-v:foldstart+1).' lines>'\").\r\n                                                                               \r\n      Ex: \r\n        - Open a vim script and try: \r\n            FoldNonMatching \\<function\\> -1\r\n        - Open a java class and try: \r\n            FoldNonMatching public\\|private\\|protected -1\r\n        - Open files with diff\/patch output for several files and try:\r\n            FoldMatching diff -1\r\n                                                                               \r\n        Please send me other uses that you found for the \"-1\" context and I\r\n        will add it to the above list.\r\n                                                                               \r\n  Notes:\r\n  - The plugin provides several ways to specify the fold blocks, but not all\r\n    of them might make sense to you, especially when used with the *bang*\r\n    option to invert the match.\r\n                                                                               \r\n  - For :FoldMatching command, the pattern is searched using the built-in\r\n    search() function, so any limitations application to this function apply\r\n    to the patterns passed to the command as well.\r\n                                                                               \r\n  - You can change the default for context by setting g:foldutilDefContext.\r\n                                                                               \r\n  - The arguments are separated by spaces, so to include spaces in the\r\n    patterns, you need to protect them with a back-slash. Specifying a bang\r\n    makes the match inverse, so it allows you to show matching lines,\r\n    instead of folding them away.\r\n                                                                               \r\n  - You can change the context alone by using :FoldSetContext command or\r\n    completely end folding and revert the settings modified by the plugin by\r\n    using the :FoldEndFolding command.\r\n                                                                               \r\n  - When the commands are executed, if the current 'foldmethod' is not\r\n    \"manual\", it is switched to \"manual\" temporarily and restored when the\r\n    folding is ended using the :FoldEndFolding command. It also remembers\r\n    other fold related settings (such as the existing folds and\r\n    'foldminlines') and restores them as much as possible. For help on\r\n    working with folds, see help on |folding|.\r\n                                                                               \r\n  - The plugin by default, first clears the existing folds before creating the\r\n    new folds. But you can change this by setting g:foldutilClearFolds to 0,\r\n    in which case the new folds are added to the existing folds, so you can\r\n    create folds incrementally.\r\n                                                                               \r\n  - The plugin provides a function to return a string with Vim commands to\r\n    recreate the folds in the current window. Executing the string later\r\n    results in the folds getting recreated as they were before (so you can\r\n    use it to save the folds). You need to make sure that 'fdm' is either in\r\n    \"manual\" or \"marker\" mode to be able to execute the return value (though\r\n    lline is an int, you can pass in the string '$' as a shortcut to mean\r\n    the last line).\r\n                                                                               \r\n      String  FoldCreateFoldsStr(int fline, int lline)\r\n                                                                               \r\n  - You can create your own match criteria and extend the functionality of\r\n    the plugin by using the b:fuSearchFn variable. If you set the name of\r\n    your search function with custom match criteria to this variable, before\r\n    calling the :FoldMatching or :FoldNonMatching commands, the plugin uses\r\n    the custom function instead of one of the standard search functions that\r\n    comes with the plugin. The prototype of the function is:\r\n                                                                               \r\n      int Search(pattern, negate)\r\n                                                                               \r\n    The function should behave very much like the built-in search()\r\n    function, ie., it should search for the next line matching the give\r\n    pattern (using your custom match criteria), position the cursor at the\r\n    matched line and return the line number. When the match fails, it\r\n    should return 0 and shouldn't change the cursor position\r\n    (see :help search()).\r\n                                                                               \r\n    See one of the existing functions, s:SearchForPattern(),\r\n    s:PositionAtNextLine() and s:PositionAtNextHiGroup() for examples.\r\n                                                                               \r\nSummary Of Features:\r\n  Command Line:\r\n    FoldMatching (or FoldNonMatching), FoldShowLines, FoldShowMarks,\r\n    FoldShowHiGroup, FoldShowRange, FoldEndFolding\r\n                                                                               \r\n  Functions:\r\n    FoldCreateFoldsStr\r\n                                                                               \r\n  Settings:\r\n      g:foldutilDefContext, g:foldutilClearFolds, g:foldutilFoldText\r\n\r\n\r\n\r\nSearch_Key_Words: foldutil foldutils fold util folds Hari Krishna Dara","4":"  The plugins provides useful commands for the ease of creating folds using\r\n  different match-criteria. They support creating folds in three different\r\n  modes, in the whole buffer, or only in the selected range:\r\n      - block mode\r\n        You give a starting and ending pattern for the blocks.\r\n      - outline mode\r\n        You give a pattern that determines the start of the block. A new\r\n        block automatically starts whenever the pattern is found.\r\n      - non-block mode\r\n        You give a pattern which determines the set of lines that should be\r\n        included in the folds. Useful to see only the matching\/non-matching\r\n        lines with or without context.\r\n                                                                               \r\n  The first set of commands use pattern matching criteria (using the\r\n  built-in =~ operator, see help on |expr-=~|).\r\n  \r\n    FoldMatching - All arguments are optional. The first argument specifies\r\n                   the begin pattern and an optional second argument can be\r\n                   passed to specify an end pattern (for block mode) and\r\n                   additionally the number of context lines to be shown\r\n                   (which defaults to 1 if not specified). To specify an\r\n                   outline mode, a special value of -1 should be specified\r\n                   as context.\r\n        Syntax:\r\n          [range]FoldMatching[!] [pattern] [endPattern] [context]\r\n\r\n        Ex:\r\n          FoldMatching\r\n            Uses current search pattern and creates folds in non-block mode\r\n            with the default context of 1.\r\n          FoldMatching! ^\\s*\/\/ 0\r\n            This potentially folds away all the lines that are not in\r\n            C++\/Java single-line comments such that you can see only those\r\n            comments.\r\n          FoldMatching public -1\r\n            Uses \"public\" as the pattern and creates folds in outline mode.\r\n          FoldMatching \/\\* \\*\/ 0\r\n            Creates folds for all the C++\/Java style block comments with no\r\n            context.\r\n                                                                               \r\n    FoldNonMatching - This is just an alias for \"FoldMatching\" with a bang.\r\n                                                                               \r\n  The following commands use line number as match criteria\r\n  \r\n    FoldShowLines - Pass a comma-separated list of line numbers and an\r\n                    optional number of context lines to show\/hide. All the\r\n                    rest of the lines (excluding those in context) will be\r\n                    folded away. You can also create blocks by specifying an\r\n                    optional list of line numbers as a second argument. You\r\n                    can give a range too.\r\n        Syntax:\r\n          [range]FoldShowLines[!] {lineNumbers} [endLineNumbers] [context]\r\n  \r\n        Ex:\r\n          FoldShowLines 10,50,100 3\r\n            Creates four folds exposing the lines 10, 50 and 100 with a\r\n            context of 3 lines.\r\n          FoldShowLines! 5,15,25 10,20,30 0\r\n            Creates three folds with 5 to 10, 15 to 20 and 25 to 30 as blocks.\r\n                                                                               \r\n    FoldShowMarks - Shows all the lines that have a mark defined in the\r\n                    current buffer, by folding away all the rest of the\r\n                    lines. Only the marks from a-z and A-Z are considered\r\n                    for match criteria.\r\n        Syntax:\r\n          [range]FoldShowMarks [context]\r\n                                                                               \r\n  The following command takes a highlight group as a match criteria, and\r\n    uses it to show\/hide lines.\r\n  \r\n    FoldShowHiGroup - Pass a highlight group name and an optional number of\r\n                    context lines to be shown. All the rest of the lines\r\n                    (excluding those in context) will be folded away. You\r\n                    can also create blocks by specifying an optional end\r\n                    highligh group as a second argument. You can give a\r\n                    range too.\r\n        Syntax:\r\n          [range]FoldShowHiGroup[!] {HiGroup} [endHiGroup] [context]\r\n  \r\n        Ex:\r\n          FoldShowHiGroup Todo\r\n            Folds away all the lines except those that have a TODO item\r\n            mentioned (in Java, this is all the comments containing the\r\n            words TODO or FIXME, by default) with a context of 1 line.\r\n          FoldShowHiGroup Special 0\r\n            In HTML this reveals just the lines containing special characters.\r\n          FoldShowHiGroup! Comment 0\r\n            This will fold away all the comment lines in any language.\r\n  \r\n  The following is purely for convenience to reduce the number of commands\r\n  to be executed (you need to create separate folds).\r\n                                                                               \r\n    FoldShowRange - All the lines are folded except for the lines in the range\r\n                    given. Helps to search only in a range of lines, as it is\r\n                    easy to identify when the cursor goes out of the range.\r\n                    Also consider removing \"search\" and \"jump\" from\r\n                    'foldopen' setting.\r\n        Syntax:\r\n          [range]FoldShowRange\r\n  \r\n        Ex:\r\n          50,500FoldShowRange\r\n  \r\n      The defaults for pattern and context are current search pattern\r\n        (extracted from \/ register) and 1 respectively.\r\n      The outline mode additionally modifies the 'foldtext' such that the\r\n        starting line shows up as the summary line for the fold (without the\r\n        usual dashes and number of lines in the prefix). This allows you to\r\n        view the matched lines more clearly and also follow the same\r\n        indentation as the original (nice when folding code). You can\r\n        however set g:foldutilFoldText to any value that is acceptable for\r\n        'foldtext' and customize this behavior (e.g., to view the number of\r\n        lines in addition to the matched line, set it to something like:\r\n            \"getline(v:foldstart).' <'.(v:foldend-v:foldstart+1).' lines>'\").\r\n                                                                               \r\n      Ex: \r\n        - Open a vim script and try: \r\n            FoldNonMatching \\<function\\> -1\r\n        - Open a java class and try: \r\n            FoldNonMatching public\\|private\\|protected -1\r\n        - Open files with diff\/patch output for several files and try:\r\n            FoldMatching diff -1\r\n                                                                               \r\n        Please send me other uses that you found for the \"-1\" context and I\r\n        will add it to the above list.\r\n                                                                               \r\n  Notes:\r\n  - The plugin provides several ways to specify the fold blocks, but not all\r\n    of them might make sense to you, especially when used with the *bang*\r\n    option to invert the match.\r\n                                                                               \r\n  - For :FoldMatching command, the pattern is searched using the built-in\r\n    search() function, so any limitations application to this function apply\r\n    to the patterns passed to the command as well.\r\n                                                                               \r\n  - You can change the default for context by setting g:foldutilDefContext.\r\n                                                                               \r\n  - The arguments are separated by spaces, so to include spaces in the\r\n    patterns, you need to protect them with a back-slash. Specifying a bang\r\n    makes the match inverse, so it allows you to show matching lines,\r\n    instead of folding them away.\r\n                                                                               \r\n  - You can change the context alone by using :FoldSetContext command or\r\n    completely end folding and revert the settings modified by the plugin by\r\n    using the :FoldEndFolding command.\r\n                                                                               \r\n  - When the commands are executed, if the current 'foldmethod' is not\r\n    \"manual\", it is switched to \"manual\" temporarily and restored when the\r\n    folding is ended using the :FoldEndFolding command. It also remembers\r\n    other fold related settings (such as the existing folds and\r\n    'foldminlines') and restores them as much as possible. For help on\r\n    working with folds, see help on |folding|.\r\n                                                                               \r\n  - The plugin by default, first clears the existing folds before creating the\r\n    new folds. But you can change this by setting g:foldutilClearFolds to 0,\r\n    in which case the new folds are added to the existing folds, so you can\r\n    create folds incrementally.\r\n                                                                               \r\n  - The plugin provides a function to return a string with Vim commands to\r\n    recreate the folds in the current window. Executing the string later\r\n    results in the folds getting recreated as they were before (so you can\r\n    use it to save the folds). You need to make sure that 'fdm' is either in\r\n    \"manual\" or \"marker\" mode to be able to execute the return value (though\r\n    lline is an int, you can pass in the string '$' as a shortcut to mean\r\n    the last line).\r\n                                                                               \r\n      String  FoldCreateFoldsStr(int fline, int lline)\r\n                                                                               \r\n  - You can create your own match criteria and extend the functionality of\r\n    the plugin by using the b:fuSearchFn variable. If you set the name of\r\n    your search function with custom match criteria to this variable, before\r\n    calling the :FoldMatching or :FoldNonMatching commands, the plugin uses\r\n    the custom function instead of one of the standard search functions that\r\n    comes with the plugin. The prototype of the function is:\r\n                                                                               \r\n      int Search(pattern, negate)\r\n                                                                               \r\n    The function should behave very much like the built-in search()\r\n    function, ie., it should search for the next line matching the give\r\n    pattern (using your custom match criteria), position the cursor at the\r\n    matched line and return the line number. When the match fails, it\r\n    should return 0 and shouldn't change the cursor position\r\n    (see :help search()).\r\n                                                                               \r\n    See one of the existing functions, s:SearchForPattern(),\r\n    s:PositionAtNextLine() and s:PositionAtNextHiGroup() for examples.\r\n                                                                               \r\nSummary Of Features:\r\n  Command Line:\r\n    FoldMatching (or FoldNonMatching), FoldShowLines, FoldShowMarks,\r\n    FoldShowHiGroup, FoldShowRange, FoldEndFolding\r\n                                                                               \r\n  Functions:\r\n    FoldCreateFoldsStr\r\n                                                                               \r\n  Settings:\r\n      g:foldutilDefContext, g:foldutilClearFolds, g:foldutilFoldText\r\n\r\n\r\n\r\nSearch_Key_Words: foldutil foldutils fold util folds Hari Krishna Dara","install_details":"Drop it in your plugin directory.\r\n\r\nRequires Vim6.3\r\nRequires multvals.vim (vimscript #171)\r\nRequires genutils.vim (vimscript #197)","5":"Drop it in your plugin directory.\r\n\r\nRequires Vim6.3\r\nRequires multvals.vim (vimscript #171)\r\nRequires genutils.vim (vimscript #197)","first_name":"Hari Krishna","6":"Hari Krishna","last_name":"Dara","7":"Dara","releases":[{"0":"158","vim_version":"7.0","1":"7.0","script_version":"3.0","2":"3.0","version_comment":"- No longer depends on multvals.\r\n- Works with the new autoload version of genutils.\r\n","3":"- No longer depends on multvals.\r\n- Works with the new autoload version of genutils.\r\n","package":"foldutil.vim","4":"foldutil.vim","src_id":"6267","5":"6267","creation_date":"1160481327","6":"1160481327"},{"0":"158","vim_version":"6.0","1":"6.0","script_version":"2.0","2":"2.0","version_comment":"- Now you can pass separate begin and end patterns to specify the fold\r\n  blocks.\r\n- FoldShowMatching has been renamed to FoldMatching.\r\n- You can also invert the pattern easily by passing a *bang* to the\r\n  FoldMatching and other commands.\r\n- There are now multiple ways to specify the match criteria\r\n  - Search pattern (existing): FoldMatching, FoldNonMatching\r\n  - Line numbers (existing): FoldShowLines\r\n  - Vim marks (new): FoldShowMarks\r\n  - Highlight group names (new): FoldShowHiGroup\r\n- Easy way to create custom match criteria if the above doesn't suite\r\n  your needs. This provides a lot of extensibility.\r\n- The logic has been rewritten for the ease of maintenance and\r\n  extensibility. The plugin also runs much faster now (makes difference\r\n  on huge log files).\r\n\r\nThere is a new dependency on the genutils.vim plugin.\r\n","3":"- Now you can pass separate begin and end patterns to specify the fold\r\n  blocks.\r\n- FoldShowMatching has been renamed to FoldMatching.\r\n- You can also invert the pattern easily by passing a *bang* to the\r\n  FoldMatching and other commands.\r\n- There are now multiple ways to specify the match criteria\r\n  - Search pattern (existing): FoldMatching, FoldNonMatching\r\n  - Line numbers (existing): FoldShowLines\r\n  - Vim marks (new): FoldShowMarks\r\n  - Highlight group names (new): FoldShowHiGroup\r\n- Easy way to create custom match criteria if the above doesn't suite\r\n  your needs. This provides a lot of extensibility.\r\n- The logic has been rewritten for the ease of maintenance and\r\n  extensibility. The plugin also runs much faster now (makes difference\r\n  on huge log files).\r\n\r\nThere is a new dependency on the genutils.vim plugin.\r\n","package":"foldutil.vim","4":"foldutil.vim","src_id":"4278","5":"4278","creation_date":"1116007742","6":"1116007742"},{"0":"158","vim_version":"6.0","1":"6.0","script_version":"1.7","2":"1.7","version_comment":"- New FoldShowRange command to fold all lines except the selected range.\r\n  See doc for usage.\r\n","3":"- New FoldShowRange command to fold all lines except the selected range.\r\n  See doc for usage.\r\n","package":"foldutil.vim","4":"foldutil.vim","src_id":"3586","5":"3586","creation_date":"1098991925","6":"1098991925"},{"0":"158","vim_version":"6.0","1":"6.0","script_version":"1.6","2":"1.6","version_comment":"- Now requires Vim6.2\r\n- Now requires multvals.vim\r\n- The plugin now remembers \"manual\" folds and restores with :FoldEndFolding. Defines a useful global function FoldCreateFoldsStr() for this purpose.\r\n- A new :FoldSetContext to conveniently change only the context of the current match.\r\n- Also fixed an error with non-existing w:settStr.","3":"- Now requires Vim6.2\r\n- Now requires multvals.vim\r\n- The plugin now remembers \"manual\" folds and restores with :FoldEndFolding. Defines a useful global function FoldCreateFoldsStr() for this purpose.\r\n- A new :FoldSetContext to conveniently change only the context of the current match.\r\n- Also fixed an error with non-existing w:settStr.","package":"foldutil.vim","4":"foldutil.vim","src_id":"3223","5":"3223","creation_date":"1089746273","6":"1089746273"},{"0":"158","vim_version":"6.0","1":"6.0","script_version":"1.5","2":"1.5","version_comment":"A very useful \"-1\" context is now supported. Thanks to John A. Peters for the idea. Read the description for details.","3":"A very useful \"-1\" context is now supported. Thanks to John A. Peters for the idea. Read the description for details.","package":"foldutil.vim","4":"foldutil.vim","src_id":"2678","5":"2678","creation_date":"1075142836","6":"1075142836"},{"0":"158","vim_version":"6.0","1":"6.0","script_version":"1.4","2":"1.4","version_comment":"Thanks to Tom Regner {tomte at tomsdiner dot org} for the enhancement to work even when foldmethod is not 'manual'. See description for a new command and more information.\r\n","3":"Thanks to Tom Regner {tomte at tomsdiner dot org} for the enhancement to work even when foldmethod is not 'manual'. See description for a new command and more information.\r\n","package":"foldutil.vim","4":"foldutil.vim","src_id":"2098","5":"2098","creation_date":"1055966133","6":"1055966133"},{"0":"158","vim_version":"6.0","1":"6.0","script_version":"1.3","2":"1.3","version_comment":"Fixed a couple of bugs and added a new command \":FoldShowLines\" to fold away all the lines that are not part of the comma separated list of lines specified on the command-line. See description for usage.\r\n","3":"Fixed a couple of bugs and added a new command \":FoldShowLines\" to fold away all the lines that are not part of the comma separated list of lines specified on the command-line. See description for usage.\r\n","package":"foldutil.vim","4":"foldutil.vim","src_id":"2064","5":"2064","creation_date":"1055354358","6":"1055354358"},{"0":"158","vim_version":"6.0","1":"6.0","script_version":"1.1","2":"1.1","version_comment":"Fixed a couple of bugs reported by Gergely Kontra and better error messages (missing search pattern etc.)","3":"Fixed a couple of bugs reported by Gergely Kontra and better error messages (missing search pattern etc.)","package":"foldutil.vim","4":"foldutil.vim","src_id":"1237","5":"1237","creation_date":"1032794857","6":"1032794857"},{"0":"158","vim_version":"6.0","1":"6.0","script_version":"1.0.0","2":"1.0.0","version_comment":"Initial upload","3":"Initial upload","package":"foldutil.vim","4":"foldutil.vim","src_id":"388","5":"388","creation_date":"1007140102","6":"1007140102"}]},"157":{"script_id":"157","0":"157","script_name":"autoload_cscope.vim","1":"autoload_cscope.vim","script_type":"utility","2":"utility","summary":"Script that will search for and load cscope.out databases automatically","3":"Script that will search for and load cscope.out databases automatically","description":"This plugin will automatically load cscope.out databases into vim when you open a C file. (headers included)\r\n\r\nIt does a search starting at the directory that the file is in, and checking the parent directories until it find the cscope.out file.  The idea being that you can start editing a source file deep in a project dir, and it will find the correct cscope database a couple dirs up.\r\n\r\nThis version also creates some macros and a menu that can be useful.  If you don't like them, you can set g:autocscope_menus to 0 and they won't load.\r\n\r\n","4":"This plugin will automatically load cscope.out databases into vim when you open a C file. (headers included)\r\n\r\nIt does a search starting at the directory that the file is in, and checking the parent directories until it find the cscope.out file.  The idea being that you can start editing a source file deep in a project dir, and it will find the correct cscope database a couple dirs up.\r\n\r\nThis version also creates some macros and a menu that can be useful.  If you don't like them, you can set g:autocscope_menus to 0 and they won't load.\r\n\r\n","install_details":"Just drop it into your plugin directory.","5":"Just drop it into your plugin directory.","first_name":"michael","6":"michael","last_name":"tilstra","7":"tilstra","releases":[{"0":"157","vim_version":"7.0","1":"7.0","script_version":"0.5","2":"0.5","version_comment":"Dotan Halevi fixed the path handling when used on Windows systems.","3":"Dotan Halevi fixed the path handling when used on Windows systems.","package":"autoload_cscope.vim","4":"autoload_cscope.vim","src_id":"14884","5":"14884","creation_date":"1296158362","6":"1296158362"},{"0":"157","vim_version":"6.0","1":"6.0","script_version":"0.4","2":"0.4","version_comment":"Fixed a handful of typos. Including one pointed out by Prasun Ratn.","3":"Fixed a handful of typos. Including one pointed out by Prasun Ratn.","package":"autoload_cscope.vim","4":"autoload_cscope.vim","src_id":"14269","5":"14269","creation_date":"1289831206","6":"1289831206"},{"0":"157","vim_version":"6.0","1":"6.0","script_version":"0.3","2":"0.3","version_comment":"fixed the issue where it wasn't always finding the right place to start looking.\r\nusnig the nifty fnamemodify() function saves a lot of crude I was trying to do by hand.","3":"fixed the issue where it wasn't always finding the right place to start looking.\r\nusnig the nifty fnamemodify() function saves a lot of crude I was trying to do by hand.","package":"autoload_cscope.vim","4":"autoload_cscope.vim","src_id":"516","5":"516","creation_date":"1012212736","6":"1012212736"},{"0":"157","vim_version":"6.0","1":"6.0","script_version":"0.2","2":"0.2","version_comment":"fixed up the Cycle_csdb function a bit.  still has a few little bugs.  but they don't seem to be life threatening.  (scan the file for FIXME to see them)","3":"fixed up the Cycle_csdb function a bit.  still has a few little bugs.  but they don't seem to be life threatening.  (scan the file for FIXME to see them)","package":"autoload_cscope.vim","4":"autoload_cscope.vim","src_id":"471","5":"471","creation_date":"1010997893","6":"1010997893"},{"0":"157","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"autoload_cscope.vim","4":"autoload_cscope.vim","src_id":"387","5":"387","creation_date":"1007135248","6":"1007135248"}]},"156":{"script_id":"156","0":"156","script_name":"increment.vim","1":"increment.vim","script_type":"utility","2":"utility","summary":"yet another script for incrementing numbers.","3":"yet another script for incrementing numbers.","description":"This script provides a way to quickly create incremented lists (either\r\nincreasing or decreasing) using the visual block mode. \r\n\r\nSynopsis:\r\n=========\r\n1. Suppose you have a column of the following form:\r\n    array(1) = 3;\r\n    array(1) = 3;\r\n    array(1) = 3;\r\n    array(1) = 3;\r\n    array(1) = 3;\r\n2. Choose the column of '1's using Ctrl-V and then run the command Inc (you\r\n   should see \"'<,'>Inc\" on the command line at this point)(if you do not\r\n   have any other user commands starting with 'I', just I will suffice).\r\n   This will tranform the text as:\r\n    array(1) = 3;       array(1) = 3;\r\n    array(1) = 3;       array(2) = 3;\r\n    array(1) = 3;  --> array(3) = 3;\r\n    array(1) = 3;       array(4) = 3;\r\n    array(1) = 3;       array(5) = 3;\r\n3. You can then choose the column of '3's (again using Ctrl-V) and run the\r\n   command \"Inc 3\" to generate another incremented list. This will\r\n   generate:\r\n    array(1) = 3;        array(1) =  3;\r\n    array(2) = 3;        array(2) =  6;\r\n    array(3) = 3;  -->  array(3) =  9;\r\n    array(4) = 3;        array(4) = 12;\r\n    array(5) = 3;        array(5) = 15;\r\n    \r\n    Note: increment.vim automatically pads the numbers in the the column\r\n    with spaces in order to get them right aligned. This is useful in most\r\n    cases, but for cases when this might be bad, use IncN which doesnt do\r\n    any alignment. \r\n\r\nCommands provided:\r\n==================\r\n1. Inc : generates a column of increasing numbers with RIGHT  alignment.\r\n2. IncN: generates a column of increasing numbers with NO     alignment.\r\n3. IncL: generates a column of increasing numbers with LEFT   alignment\r\n\r\nTip:\r\nA mapping which goes well with this command is the following:\r\n\r\nvnoremap <c-a> :Inc<CR>\r\n\r\nWith this mapping, select a column of numbers and press Ctrl-A, which will\r\nget them in increasing order. I use <c-a> because its similar to the <c-a>\r\ncommand in normal mode which increments the number under the cursor.\r\n\r\nAcknowledgements:\r\n===============\r\nThere are other scripts which have been made to do almost the same thing.\r\nCharles E Campbell's vimtip #150         uses a similar visual block strategy\r\nStanislav Sitar's         vimscript #145     uses a searc\/replace strategy\r\n\r\n","4":"This script provides a way to quickly create incremented lists (either\r\nincreasing or decreasing) using the visual block mode. \r\n\r\nSynopsis:\r\n=========\r\n1. Suppose you have a column of the following form:\r\n    array(1) = 3;\r\n    array(1) = 3;\r\n    array(1) = 3;\r\n    array(1) = 3;\r\n    array(1) = 3;\r\n2. Choose the column of '1's using Ctrl-V and then run the command Inc (you\r\n   should see \"'<,'>Inc\" on the command line at this point)(if you do not\r\n   have any other user commands starting with 'I', just I will suffice).\r\n   This will tranform the text as:\r\n    array(1) = 3;       array(1) = 3;\r\n    array(1) = 3;       array(2) = 3;\r\n    array(1) = 3;  --> array(3) = 3;\r\n    array(1) = 3;       array(4) = 3;\r\n    array(1) = 3;       array(5) = 3;\r\n3. You can then choose the column of '3's (again using Ctrl-V) and run the\r\n   command \"Inc 3\" to generate another incremented list. This will\r\n   generate:\r\n    array(1) = 3;        array(1) =  3;\r\n    array(2) = 3;        array(2) =  6;\r\n    array(3) = 3;  -->  array(3) =  9;\r\n    array(4) = 3;        array(4) = 12;\r\n    array(5) = 3;        array(5) = 15;\r\n    \r\n    Note: increment.vim automatically pads the numbers in the the column\r\n    with spaces in order to get them right aligned. This is useful in most\r\n    cases, but for cases when this might be bad, use IncN which doesnt do\r\n    any alignment. \r\n\r\nCommands provided:\r\n==================\r\n1. Inc : generates a column of increasing numbers with RIGHT  alignment.\r\n2. IncN: generates a column of increasing numbers with NO     alignment.\r\n3. IncL: generates a column of increasing numbers with LEFT   alignment\r\n\r\nTip:\r\nA mapping which goes well with this command is the following:\r\n\r\nvnoremap <c-a> :Inc<CR>\r\n\r\nWith this mapping, select a column of numbers and press Ctrl-A, which will\r\nget them in increasing order. I use <c-a> because its similar to the <c-a>\r\ncommand in normal mode which increments the number under the cursor.\r\n\r\nAcknowledgements:\r\n===============\r\nThere are other scripts which have been made to do almost the same thing.\r\nCharles E Campbell's vimtip #150         uses a similar visual block strategy\r\nStanislav Sitar's         vimscript #145     uses a searc\/replace strategy\r\n\r\n","install_details":"drop the file in the vim plugins directory.","5":"drop the file in the vim plugins directory.","first_name":"Srinath","6":"Srinath","last_name":"Avadhanula","7":"Avadhanula","releases":[{"0":"156","vim_version":"6.0","1":"6.0","script_version":"1.3","2":"1.3","version_comment":"removed the leading tabs bug yet again. the last was not handling properly a combination of leading tabs and whitespaces.","3":"removed the leading tabs bug yet again. the last was not handling properly a combination of leading tabs and whitespaces.","package":"increment.vim","4":"increment.vim","src_id":"469","5":"469","creation_date":"1010839647","6":"1010839647"},{"0":"156","vim_version":"6.0","1":"6.0","script_version":"1.1","2":"1.1","version_comment":"fixed a bug where leading tabs were causing problems. added another command IncL which causes left aligned columns.","3":"fixed a bug where leading tabs were causing problems. added another command IncL which causes left aligned columns.","package":"increment.vim","4":"increment.vim","src_id":"389","5":"389","creation_date":"1007232154","6":"1007232154"},{"0":"156","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"increment.vim","4":"increment.vim","src_id":"368","5":"368","creation_date":"1006406222","6":"1006406222"}]},"155":{"script_id":"155","0":"155","script_name":"ant_menu.vim","1":"ant_menu.vim","script_type":"utility","2":"utility","summary":"plugin for ant","3":"plugin for ant","description":"A simple script that provides a pull-down menu and keyboard shortcuts for calling ant, a java build \r\nutility.  By default, ant.vim assumes that the build.xml file is in the current directory.  The user can \r\nset the build file in another directory by selecting the \"Set build file\" option or by using \",s\" in \r\ncommand mode. \r\n\r\nGlobal options can be set in your .vimrc file.      For example:\r\n\r\nlet g:buildFile = 'foo.xml'\r\nlet g:antOption = '-debug'\r\nlet g:logFile = 'foo.log'\r\n\r\nIf you are on a windows box and you cannot see compilation errors in your quickfix window,\r\ntry setting the shellpipe to \"2>\" in your _vimrc.","4":"A simple script that provides a pull-down menu and keyboard shortcuts for calling ant, a java build \r\nutility.  By default, ant.vim assumes that the build.xml file is in the current directory.  The user can \r\nset the build file in another directory by selecting the \"Set build file\" option or by using \",s\" in \r\ncommand mode. \r\n\r\nGlobal options can be set in your .vimrc file.      For example:\r\n\r\nlet g:buildFile = 'foo.xml'\r\nlet g:antOption = '-debug'\r\nlet g:logFile = 'foo.log'\r\n\r\nIf you are on a windows box and you cannot see compilation errors in your quickfix window,\r\ntry setting the shellpipe to \"2>\" in your _vimrc.","install_details":"For vim 6, just drop ant_menu.vim into your plugin directory.","5":"For vim 6, just drop ant_menu.vim into your plugin directory.","first_name":"Shad","6":"Shad","last_name":"Gregory","7":"Gregory","releases":[{"0":"155","vim_version":"6.0","1":"6.0","script_version":"0.5.7.1","2":"0.5.7.1","version_comment":"*Moved ANT menu under Plugin\r\n*Updated to toggle menu options upon load","3":"*Moved ANT menu under Plugin\r\n*Updated to toggle menu options upon load","package":"ant_menu.vim","4":"ant_menu.vim","src_id":"10729","5":"10729","creation_date":"1244088007","6":"1244088007"},{"0":"155","vim_version":"6.0","1":"6.0","script_version":"0.5.7","2":"0.5.7","version_comment":"Selected options will now be marked with an '*' in the ant menu.","3":"Selected options will now be marked with an '*' in the ant menu.","package":"ant_menu.vim","4":"ant_menu.vim","src_id":"10723","5":"10723","creation_date":"1244063491","6":"1244063491"},{"0":"155","vim_version":"6.0","1":"6.0","script_version":"0.5.6","2":"0.5.6","version_comment":"Bug fix for default buffer problems that occurs when the user switches between buffers.\r\nThanks to David Fishburn for the fix.","3":"Bug fix for default buffer problems that occurs when the user switches between buffers.\r\nThanks to David Fishburn for the fix.","package":"ant_menu.vim","4":"ant_menu.vim","src_id":"10642","5":"10642","creation_date":"1242836825","6":"1242836825"},{"0":"155","vim_version":"6.0","1":"6.0","script_version":"0.5.5","2":"0.5.5","version_comment":"Amit Jain's cleaner output changes","3":"Amit Jain's cleaner output changes","package":"ant_menu.vim","4":"ant_menu.vim","src_id":"6445","5":"6445","creation_date":"1163964865","6":"1163964865"},{"0":"155","vim_version":"6.0","1":"6.0","script_version":"0.5.4","2":"0.5.4","version_comment":"*Changed name to ant_menu.vim to avoid confusion with the numerous other ant.vim's.\r\n*Includes Derek Pomery's code to dynamically load build.xml upon buffer switch.\r\n*Includes David's <dakATdotech.com > code to specify a target on find.","3":"*Changed name to ant_menu.vim to avoid confusion with the numerous other ant.vim's.\r\n*Includes Derek Pomery's code to dynamically load build.xml upon buffer switch.\r\n*Includes David's <dakATdotech.com > code to specify a target on find.","package":"ant_menu.vim","4":"ant_menu.vim","src_id":"2956","5":"2956","creation_date":"1082377216","6":"1082377216"},{"0":"155","vim_version":"6.0","1":"6.0","script_version":"0.5.3","2":"0.5.3","version_comment":"*Merged in javac 1.4 code for GetProbFile() from 'Michael Scheper <ant.vim@michaelscheper.com>'\r\n*added code for kjc (only works with -emacs)\r\n*clean up","3":"*Merged in javac 1.4 code for GetProbFile() from 'Michael Scheper <ant.vim@michaelscheper.com>'\r\n*added code for kjc (only works with -emacs)\r\n*clean up","package":"ant.vim","4":"ant.vim","src_id":"2634","5":"2634","creation_date":"1072610787","6":"1072610787"},{"0":"155","vim_version":"6.0","1":"6.0","script_version":"0.5.2","2":"0.5.2","version_comment":"*Incorporated Phil McCarthy's fix that starts ant -find from the file's current directory.\r\n*Incorporated bug fix from Michael Scheper.","3":"*Incorporated Phil McCarthy's fix that starts ant -find from the file's current directory.\r\n*Incorporated bug fix from Michael Scheper.","package":"ant.vim","4":"ant.vim","src_id":"2592","5":"2592","creation_date":"1071402274","6":"1071402274"},{"0":"155","vim_version":"6.0","1":"6.0","script_version":"0.5.1","2":"0.5.1","version_comment":"*merged in Jou Wei Huang's fix for multiline targets\r\n*fixed bug that prevented '-find' from working when another option is set","3":"*merged in Jou Wei Huang's fix for multiline targets\r\n*fixed bug that prevented '-find' from working when another option is set","package":"ant.vim","4":"ant.vim","src_id":"1785","5":"1785","creation_date":"1047037733","6":"1047037733"},{"0":"155","vim_version":"6.0","1":"6.0","script_version":"0.5","2":"0.5","version_comment":"*Incorporated David Fishburn's quickfix code.\r\n*Minor tweaks to target menu functionality.\r\n","3":"*Incorporated David Fishburn's quickfix code.\r\n*Minor tweaks to target menu functionality.\r\n","package":"ant.vim","4":"ant.vim","src_id":"1643","5":"1643","creation_date":"1042891241","6":"1042891241"},{"0":"155","vim_version":"6.0","1":"6.0","script_version":"0.4.3","2":"0.4.3","version_comment":"*target menu fix for multi-line targets and\r\n  target lines in which \"name\" is not the\r\n  first attribute (thanks to Ronny Wilms for \r\n  the fix)\r\n*,g should have better support for jikes\r\n  (thanks to Mark Healy for the code)\r\n*,g will open a new gvim only if the file is\r\n  in an existing buffer","3":"*target menu fix for multi-line targets and\r\n  target lines in which \"name\" is not the\r\n  first attribute (thanks to Ronny Wilms for \r\n  the fix)\r\n*,g should have better support for jikes\r\n  (thanks to Mark Healy for the code)\r\n*,g will open a new gvim only if the file is\r\n  in an existing buffer","package":"ant.vim","4":"ant.vim","src_id":"1389","5":"1389","creation_date":"1036857356","6":"1036857356"},{"0":"155","vim_version":"6.0","1":"6.0","script_version":"0.4.2","2":"0.4.2","version_comment":"*',g' now spawns new gvim window\r\n  (thanks to Nathan for the suggestion)\r\n*cleaned up target menu code\r\n*added ',t' binding for selecting build\r\n targets (thanks goes out to Anton Straka\r\n for the code snippet)","3":"*',g' now spawns new gvim window\r\n  (thanks to Nathan for the suggestion)\r\n*cleaned up target menu code\r\n*added ',t' binding for selecting build\r\n targets (thanks goes out to Anton Straka\r\n for the code snippet)","package":"ant.vim","4":"ant.vim","src_id":"1112","5":"1112","creation_date":"1029146759","6":"1029146759"},{"0":"155","vim_version":"6.0","1":"6.0","script_version":"0.4.1","2":"0.4.1","version_comment":"updated to allow multiple ant options","3":"updated to allow multiple ant options","package":"ant.vim","4":"ant.vim","src_id":"448","5":"448","creation_date":"1010488501","6":"1010488501"},{"0":"155","vim_version":"6.0","1":"6.0","script_version":"0.4","2":"0.4","version_comment":"Added ',g' keyboard shortcut.  When in the ant error buffer, this\r\nwill attempt to parse out the file in error and open it in a new\r\nbuffer with the cursor at the line flagged in error.  The user must\r\nexecute the shortcut at the line that identifies the file in error.","3":"Added ',g' keyboard shortcut.  When in the ant error buffer, this\r\nwill attempt to parse out the file in error and open it in a new\r\nbuffer with the cursor at the line flagged in error.  The user must\r\nexecute the shortcut at the line that identifies the file in error.","package":"ant.vim","4":"ant.vim","src_id":"441","5":"441","creation_date":"1009961651","6":"1009961651"},{"0":"155","vim_version":"6.0","1":"6.0","script_version":"0.31","2":"0.31","version_comment":"Added new options to specify a log file.  Once this has\r\nbeen done, ant output will be piped to the log file.  You\r\nmust select the 'no log file' option to return  to dumping\r\nthe output to a buffer.  Alsoadded menu option for \r\n'-projecthelp'.","3":"Added new options to specify a log file.  Once this has\r\nbeen done, ant output will be piped to the log file.  You\r\nmust select the 'no log file' option to return  to dumping\r\nthe output to a buffer.  Alsoadded menu option for \r\n'-projecthelp'.","package":"ant.vim","4":"ant.vim","src_id":"423","5":"423","creation_date":"1008254057","6":"1008254057"},{"0":"155","vim_version":"6.0","1":"6.0","script_version":"0.3","2":"0.3","version_comment":"Fixed bug in which ant.vim chokes on periods in target \r\nnames (thanks to Keith Corwin for pointing it out).\r\nAdded descriptions of keyboard shortcuts in comments.\r\n\r\n","3":"Fixed bug in which ant.vim chokes on periods in target \r\nnames (thanks to Keith Corwin for pointing it out).\r\nAdded descriptions of keyboard shortcuts in comments.\r\n\r\n","package":"ant.vim","4":"ant.vim","src_id":"412","5":"412","creation_date":"1007754025","6":"1007754025"},{"0":"155","vim_version":"6.0","1":"6.0","script_version":"0.21","2":"0.21","version_comment":"ant.vim now builds the target entry on startup if a build.xml exists in the current\r\ndirectory.  The user can now set options seperate from the build, hopefully this\r\nwill provide greater flexibility (as well as one less step to the build option :-)).\r\nIf you forget which option is set, \"ANT->Set Option->Show Current\" will display\r\nthe current option.","3":"ant.vim now builds the target entry on startup if a build.xml exists in the current\r\ndirectory.  The user can now set options seperate from the build, hopefully this\r\nwill provide greater flexibility (as well as one less step to the build option :-)).\r\nIf you forget which option is set, \"ANT->Set Option->Show Current\" will display\r\nthe current option.","package":"ant.vim","4":"ant.vim","src_id":"401","5":"401","creation_date":"1007466911","6":"1007466911"},{"0":"155","vim_version":"6.0","1":"6.0","script_version":"0.2","2":"0.2","version_comment":"ant.vim will now add a 'Target' menu when the user manually sets the location of \r\nthe build file with ',s' or by selecting the build option.  So, for example, selecting\r\nANT->Target->clean from the menu will execute 'ant clean.'  I'm not all that confident \r\nin my regex skills, so I can't guarantee that it will work in all (or even most!) circumstances.  \r\nAny help or bug reports will be appreciated.","3":"ant.vim will now add a 'Target' menu when the user manually sets the location of \r\nthe build file with ',s' or by selecting the build option.  So, for example, selecting\r\nANT->Target->clean from the menu will execute 'ant clean.'  I'm not all that confident \r\nin my regex skills, so I can't guarantee that it will work in all (or even most!) circumstances.  \r\nAny help or bug reports will be appreciated.","package":"ant.vim","4":"ant.vim","src_id":"396","5":"396","creation_date":"1007362078","6":"1007362078"},{"0":"155","vim_version":"6.0","1":"6.0","script_version":"0.13","2":"0.13","version_comment":"Fixed problem with find option.  Added keyboard shortcut for 'ant -find'.","3":"Fixed problem with find option.  Added keyboard shortcut for 'ant -find'.","package":"ant.vim","4":"ant.vim","src_id":"376","5":"376","creation_date":"1006764020","6":"1006764020"},{"0":"155","vim_version":"6.0","1":"6.0","script_version":"0.12","2":"0.12","version_comment":"*Rearranged the menu selections\r\n*Added quiet build\r\n*Added keyboard shortcuts for \"default build\" and \"build.xml set\"","3":"*Rearranged the menu selections\r\n*Added quiet build\r\n*Added keyboard shortcuts for \"default build\" and \"build.xml set\"","package":"ant.vim","4":"ant.vim","src_id":"370","5":"370","creation_date":"1006491496","6":"1006491496"},{"0":"155","vim_version":"6.0","1":"6.0","script_version":"0.11","2":"0.11","version_comment":"Added test for the existence of build.xml.","3":"Added test for the existence of build.xml.","package":"ant.vim","4":"ant.vim","src_id":"366","5":"366","creation_date":"1006328596","6":"1006328596"},{"0":"155","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"ant.vim","4":"ant.vim","src_id":"365","5":"365","creation_date":"1006324340","6":"1006324340"}]},"154":{"script_id":"154","0":"154","script_name":"ctags.vim","1":"ctags.vim","script_type":"utility","2":"utility","summary":"add to or replace your tags file from vim","3":"add to or replace your tags file from vim","description":"Plugin that allows you to add to or replace your tags file from the menu.\r\n\r\nThe script takes the current working directory and finds C\/C++ source to be added to your tags file.\r\nUnix only; requires ctags, find and egrep. The default tag file is $HOME\/.tags\r\n\r\n\r\n","4":"Plugin that allows you to add to or replace your tags file from the menu.\r\n\r\nThe script takes the current working directory and finds C\/C++ source to be added to your tags file.\r\nUnix only; requires ctags, find and egrep. The default tag file is $HOME\/.tags\r\n\r\n\r\n","install_details":"Add to your plugin directory","5":"Add to your plugin directory","first_name":"Daniel","6":"Daniel","last_name":"Shields","7":"Shields","releases":[{"0":"154","vim_version":"6.0","1":"6.0","script_version":"0.3","2":"0.3","version_comment":"Now allows removal of tags from tagfile. Tidy up menu.","3":"Now allows removal of tags from tagfile. Tidy up menu.","package":"ctags.vim","4":"ctags.vim","src_id":"373","5":"373","creation_date":"1006743174","6":"1006743174"},{"0":"154","vim_version":"6.0","1":"6.0","script_version":"0.2","2":"0.2","version_comment":"Script prompts for change of root diectory. Use <Leader> for key mappings.","3":"Script prompts for change of root diectory. Use <Leader> for key mappings.","package":"ctags.vim","4":"ctags.vim","src_id":"367","5":"367","creation_date":"1006395800","6":"1006395800"},{"0":"154","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"ctags.vim","4":"ctags.vim","src_id":"364","5":"364","creation_date":"1006319379","6":"1006319379"}]},"153":{"script_id":"153","0":"153","script_name":"EasyHtml.vim","1":"EasyHtml.vim","script_type":"utility","2":"utility","summary":"Allows to add attributs\/values\/CSSProperties to HTML tags\/attributs very easily.","3":"Allows to add attributs\/values\/CSSProperties to HTML tags\/attributs very easily.","description":"With EasyHtml, you no longer need to look for tags attributes, attributes values or CSS properties values while editing HTML files. EasyHtml let you select the right attribute or value by showing you an attributes\/values list for the tag\/attribute\/CSS property under the cursor.\r\n\r\nMove the text cursor on the tag, attribute, or CSS property word then :\r\n\r\n- Press <F2> key to display attributes for the tag before\/under the cursor\r\n- Press <F3> key to display values for the attribute before\/under the cursor\r\n- Press <F4> ket to display values for the CSS Property befor\/under the cursor\r\n\r\nIn the EasyHtml buffer, use :\r\n\r\n       - h,j,k,l or <Left>,<Down>,<Up>,<Right> keys to change selected item.\r\n       - <PageUp>\/<PageDown> or <C-F>,<C-B> keys to scroll list one page downward\/forward.\r\n       - <Home> or <C-Home> to select the first item.\r\n       - <End> or <C-End> to select the last item.\r\n       - <ENTER> to add selected item WITHOUT exiting from items list.\r\n       - <S-ENTER> to add selected item AND exit from items list.\r\n       - q or <ESC> to exit without adding selected item.\r\n\r\nDeprecated attributes as declared by W3C are red highlighted, while right attributes are blue highlighted.\r\n\r\nSet g:easyHtmlSplitRight variable to 0 or 1 to open items list at left or right of current window. By default, use splitright setting.\r\n\r\nSet g:eh_singlequote variable to 0 (default) or 1 to use double or single quote when adding attributes (For example id=\"\" or id='')\r\n\r\nSet g:eh_incsearch variable to 0 (default) or 1 to dis- or en-able incremental list search. This feature allows to select an item by typing its beginning. When this is enable, 'q', 'h', 'j', 'k' and 'l' keys aren't used to exit from list and to move highlighting. Use 'Q', '<Left>', '<Down>', '<Up>' and '<Right>' instead.\r\n\r\nSet g:eh_atfirstplace to 0 (default) or 1 to indicate if attributes must be added at the end or at the beginning of the tag.\r\n\r\n+ Useful mappings :\r\n  . d<F2> : delete tag before\/under cursor\r\n  . d<F3> : delete attribute before\/under cursor\r\n","4":"With EasyHtml, you no longer need to look for tags attributes, attributes values or CSS properties values while editing HTML files. EasyHtml let you select the right attribute or value by showing you an attributes\/values list for the tag\/attribute\/CSS property under the cursor.\r\n\r\nMove the text cursor on the tag, attribute, or CSS property word then :\r\n\r\n- Press <F2> key to display attributes for the tag before\/under the cursor\r\n- Press <F3> key to display values for the attribute before\/under the cursor\r\n- Press <F4> ket to display values for the CSS Property befor\/under the cursor\r\n\r\nIn the EasyHtml buffer, use :\r\n\r\n       - h,j,k,l or <Left>,<Down>,<Up>,<Right> keys to change selected item.\r\n       - <PageUp>\/<PageDown> or <C-F>,<C-B> keys to scroll list one page downward\/forward.\r\n       - <Home> or <C-Home> to select the first item.\r\n       - <End> or <C-End> to select the last item.\r\n       - <ENTER> to add selected item WITHOUT exiting from items list.\r\n       - <S-ENTER> to add selected item AND exit from items list.\r\n       - q or <ESC> to exit without adding selected item.\r\n\r\nDeprecated attributes as declared by W3C are red highlighted, while right attributes are blue highlighted.\r\n\r\nSet g:easyHtmlSplitRight variable to 0 or 1 to open items list at left or right of current window. By default, use splitright setting.\r\n\r\nSet g:eh_singlequote variable to 0 (default) or 1 to use double or single quote when adding attributes (For example id=\"\" or id='')\r\n\r\nSet g:eh_incsearch variable to 0 (default) or 1 to dis- or en-able incremental list search. This feature allows to select an item by typing its beginning. When this is enable, 'q', 'h', 'j', 'k' and 'l' keys aren't used to exit from list and to move highlighting. Use 'Q', '<Left>', '<Down>', '<Up>' and '<Right>' instead.\r\n\r\nSet g:eh_atfirstplace to 0 (default) or 1 to indicate if attributes must be added at the end or at the beginning of the tag.\r\n\r\n+ Useful mappings :\r\n  . d<F2> : delete tag before\/under cursor\r\n  . d<F3> : delete attribute before\/under cursor\r\n","install_details":"Put this file in your plugin directory.\r\nRequires liblist.vim and genutils.vim scripts.\r\nDownload them at\r\n  http:\/\/vim.sourceforge.net\/scripts\/script.php?script_id=166\r\nand\r\n  http:\/\/vim.sourceforge.net\/scripts\/script.php?script_id=197\r\n","5":"Put this file in your plugin directory.\r\nRequires liblist.vim and genutils.vim scripts.\r\nDownload them at\r\n  http:\/\/vim.sourceforge.net\/scripts\/script.php?script_id=166\r\nand\r\n  http:\/\/vim.sourceforge.net\/scripts\/script.php?script_id=197\r\n","first_name":"Gontran","6":"Gontran","last_name":"BAERTS","7":"BAERTS","releases":[{"0":"153","vim_version":"6.0","1":"6.0","script_version":"0.5.1","2":"0.5.1","version_comment":"- No longer use of the modifiable option.","3":"- No longer use of the modifiable option.","package":"EasyHtml.vim","4":"EasyHtml.vim","src_id":"705","5":"705","creation_date":"1016757985","6":"1016757985"},{"0":"153","vim_version":"6.0","1":"6.0","script_version":"0.5","2":"0.5","version_comment":"- Now use liblist.vim script to handle lists and genutils.vim script to handle windows (Thanks to Hari Krishna Dara for this script).\r\nDownload them at\r\n  http:\/\/vim.sourceforge.net\/scripts\/script.php?script_id=166\r\nand\r\n  http:\/\/vim.sourceforge.net\/scripts\/script.php?script_id=197\r\nMake script smaller.\r\n- Mapping changed !\r\n  <F2> displays tag attributes\r\n  <F3> displays attributes values\r\n  <F4> displays CSS Properties values\r\n  <ENTER> no longer close list after item addition. Use <S-ENTER> to add and exit from list.\r\n- More user friendly : you no longer need to move cursor exactly on the keyword. Cursor may stay on '=', ':' or '\"' signs just after keyword while hitting <F2>, <F3> or <F4> keys.\r\nFor example,\r\n. Tags : <img\r\n  Hitting <F2> key works while cursor is at '<' sign.\r\n. Attributes : style=\"\"\r\n  Hitting <F3> key works while cursor is at '=' or '\"' signs.\r\n. CSS properties : background-color:;\r\n  Hitting <F4> key works while cursor is at ':' or ';' signs.\r\n- New g:eh_atfirstplace variable. See Usage section above.\r\n- Fix modifiable setting again\r\n- Fix syntax error for the \"frame\" attribute of <table> tag which causes \"border\" attribute to not been seen in attributes list.\r\n","3":"- Now use liblist.vim script to handle lists and genutils.vim script to handle windows (Thanks to Hari Krishna Dara for this script).\r\nDownload them at\r\n  http:\/\/vim.sourceforge.net\/scripts\/script.php?script_id=166\r\nand\r\n  http:\/\/vim.sourceforge.net\/scripts\/script.php?script_id=197\r\nMake script smaller.\r\n- Mapping changed !\r\n  <F2> displays tag attributes\r\n  <F3> displays attributes values\r\n  <F4> displays CSS Properties values\r\n  <ENTER> no longer close list after item addition. Use <S-ENTER> to add and exit from list.\r\n- More user friendly : you no longer need to move cursor exactly on the keyword. Cursor may stay on '=', ':' or '\"' signs just after keyword while hitting <F2>, <F3> or <F4> keys.\r\nFor example,\r\n. Tags : <img\r\n  Hitting <F2> key works while cursor is at '<' sign.\r\n. Attributes : style=\"\"\r\n  Hitting <F3> key works while cursor is at '=' or '\"' signs.\r\n. CSS properties : background-color:;\r\n  Hitting <F4> key works while cursor is at ':' or ';' signs.\r\n- New g:eh_atfirstplace variable. See Usage section above.\r\n- Fix modifiable setting again\r\n- Fix syntax error for the \"frame\" attribute of <table> tag which causes \"border\" attribute to not been seen in attributes list.\r\n","package":"EasyHtml.vim","4":"EasyHtml.vim","src_id":"691","5":"691","creation_date":"1016439049","6":"1016439049"},{"0":"153","vim_version":"6.0","1":"6.0","script_version":"0.4.1","2":"0.4.1","version_comment":"- Fix infinite loop to find window when easyhtml buffer is hidden. Thanks to Jonathon Merz who pointed out the bug and send me the patch.\r\n'The drawback to this fix is that it will reinitialize all the buffer\r\nmappings and such for the EasyHtml buffer every time the buffer is opened but\r\nis not in a window already', he says. Hari Krishna Dara has made a great script named bufNwinUtils.vim which contains useful functions to handle buffers and windows. It will allow me to avoid the drawback. I'm interesting to use his script with mine, but it requires to load entire bufNwinUtils.vim for only  two or three functions used. What do you think about that ? give me feedback, thanks.","3":"- Fix infinite loop to find window when easyhtml buffer is hidden. Thanks to Jonathon Merz who pointed out the bug and send me the patch.\r\n'The drawback to this fix is that it will reinitialize all the buffer\r\nmappings and such for the EasyHtml buffer every time the buffer is opened but\r\nis not in a window already', he says. Hari Krishna Dara has made a great script named bufNwinUtils.vim which contains useful functions to handle buffers and windows. It will allow me to avoid the drawback. I'm interesting to use his script with mine, but it requires to load entire bufNwinUtils.vim for only  two or three functions used. What do you think about that ? give me feedback, thanks.","package":"EasyHtml.vim","4":"EasyHtml.vim","src_id":"405","5":"405","creation_date":"1007515935","6":"1007515935"},{"0":"153","vim_version":"6.0","1":"6.0","script_version":"0.4","2":"0.4","version_comment":"- Added values for the \"style\" attribute (CSS2 properties)\r\n- Added values for CSS2 properties\r\n- <PageUp> and <PageDown> are now usable to move highlight through the list\r\n- When adding a value for an attribute, current attribute value (if exists) is replaced by the selected one, except for \"style\" attribute for which values are append\r\n- Set g:eh_singlequote variable to 0 or 1 to use double or single quote when adding attributes (For example id=\"\" or id='')","3":"- Added values for the \"style\" attribute (CSS2 properties)\r\n- Added values for CSS2 properties\r\n- <PageUp> and <PageDown> are now usable to move highlight through the list\r\n- When adding a value for an attribute, current attribute value (if exists) is replaced by the selected one, except for \"style\" attribute for which values are append\r\n- Set g:eh_singlequote variable to 0 or 1 to use double or single quote when adding attributes (For example id=\"\" or id='')","package":"EasyHtml.vim","4":"EasyHtml.vim","src_id":"392","5":"392","creation_date":"1007354510","6":"1007354510"},{"0":"153","vim_version":"6.0","1":"6.0","script_version":"0.3","2":"0.3","version_comment":"- Attributes list updated\r\n- Don't display attributes list for closing tags\r\n- Now, display values list when hitting <F3> with cursor on attribute word (for some attributes only).","3":"- Attributes list updated\r\n- Don't display attributes list for closing tags\r\n- Now, display values list when hitting <F3> with cursor on attribute word (for some attributes only).","package":"EasyHtml.vim","4":"EasyHtml.vim","src_id":"383","5":"383","creation_date":"1006940166","6":"1006940166"},{"0":"153","vim_version":"6.0","1":"6.0","script_version":"0.2.1","2":"0.2.1","version_comment":"- Fix global modifiable setting instead of local","3":"- Fix global modifiable setting instead of local","package":"EasyHtml.vim","4":"EasyHtml.vim","src_id":"378","5":"378","creation_date":"1006839727","6":"1006839727"},{"0":"153","vim_version":"6.0","1":"6.0","script_version":"0.2","2":"0.2","version_comment":"- Attributs list is now alphabetically sorted\r\n- Hitting <F3> allows to display attributs list in Insert mode too\r\n- Allows to select an attribut by incremental search :-)\r\nFor example, with <body> tag, typing \"onk\" (normal mode) in the attributs list buffer automatically select \"onkeydown\" attribut. Use backspace (<BS>) to remove characters. This behavior is enable by setting g:eh_incsearch variable to 1. Warning : when incremental attribut search is on, 'q', 'h', 'j', 'k' and 'l' keys aren't used to exit from list and to move highlighting. Use 'Q', '<Left>', '<Down>', '<Up>' and '<Right>' instead.\r\n- Check for attributs list already opened, and reuse it","3":"- Attributs list is now alphabetically sorted\r\n- Hitting <F3> allows to display attributs list in Insert mode too\r\n- Allows to select an attribut by incremental search :-)\r\nFor example, with <body> tag, typing \"onk\" (normal mode) in the attributs list buffer automatically select \"onkeydown\" attribut. Use backspace (<BS>) to remove characters. This behavior is enable by setting g:eh_incsearch variable to 1. Warning : when incremental attribut search is on, 'q', 'h', 'j', 'k' and 'l' keys aren't used to exit from list and to move highlighting. Use 'Q', '<Left>', '<Down>', '<Up>' and '<Right>' instead.\r\n- Check for attributs list already opened, and reuse it","package":"EasyHtml.vim","4":"EasyHtml.vim","src_id":"377","5":"377","creation_date":"1006769725","6":"1006769725"},{"0":"153","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"EasyHtml.vim","4":"EasyHtml.vim","src_id":"363","5":"363","creation_date":"1006317326","6":"1006317326"}]},"152":{"script_id":"152","0":"152","script_name":"ShowMarks","1":"ShowMarks","script_type":"utility","2":"utility","summary":"Visually shows the location of marks.","3":"Visually shows the location of marks.","description":"ShowMarks provides a visual representation of the location marks.\r\nMarks are useful for jumping back and forth between interesting points in a buffer, but can be hard to keep track of without any way to see where you have placed them.  ShowMarks hopefully makes life easier by placing a sign in the leftmost column of the buffer.  The sign indicates the label of the mark and its location.\r\nIt can be toggled on and off and individual marks can be hidden(effectively removing them).\r\n\r\nBy default the following keymappings are defined:\r\n   \\mt : Toggles ShowMarks on and off.\r\n   \\mh : Hides an individual mark.\r\n   \\ma : Hides all marks in the current buffer.\r\n   \\mm : Places the next available mark.\r\n\r\nShowMarks requires that Vim is compiled with the +signs feature.\r\n","4":"ShowMarks provides a visual representation of the location marks.\r\nMarks are useful for jumping back and forth between interesting points in a buffer, but can be hard to keep track of without any way to see where you have placed them.  ShowMarks hopefully makes life easier by placing a sign in the leftmost column of the buffer.  The sign indicates the label of the mark and its location.\r\nIt can be toggled on and off and individual marks can be hidden(effectively removing them).\r\n\r\nBy default the following keymappings are defined:\r\n   \\mt : Toggles ShowMarks on and off.\r\n   \\mh : Hides an individual mark.\r\n   \\ma : Hides all marks in the current buffer.\r\n   \\mm : Places the next available mark.\r\n\r\nShowMarks requires that Vim is compiled with the +signs feature.\r\n","install_details":"Simply unzip showmarks.zip into you $HOME\/.vim or $HOME\\vimfiles folder.","5":"Simply unzip showmarks.zip into you $HOME\/.vim or $HOME\\vimfiles folder.","first_name":"Anthony","6":"Anthony","last_name":"Kruize","7":"Kruize","releases":[{"0":"152","vim_version":"6.0","1":"6.0","script_version":"2.2","2":"2.2","version_comment":"Fixed the highlighting of the A-Z marks when 'ignorecase' is on.(Mike Kelly)  Showmarks now triggers immediately when entering a buffer for the first time.(Mikolaj Machowski) Added support for highlighting the entire line a mark is placed on.  Now uses HelpExtractor to install the help file.","3":"Fixed the highlighting of the A-Z marks when 'ignorecase' is on.(Mike Kelly)  Showmarks now triggers immediately when entering a buffer for the first time.(Mikolaj Machowski) Added support for highlighting the entire line a mark is placed on.  Now uses HelpExtractor to install the help file.","package":"showmarks.vim","4":"showmarks.vim","src_id":"3342","5":"3342","creation_date":"1092691709","6":"1092691709"},{"0":"152","vim_version":"6.0","1":"6.0","script_version":"2.1","2":"2.1","version_comment":"Marks are now shown with an order of precedence and can be highlighted a different colour when multiple marks are placed on the same line. Included marks can now be specified per buffer. Thanks to Gary Holloway for these changes.","3":"Marks are now shown with an order of precedence and can be highlighted a different colour when multiple marks are placed on the same line. Included marks can now be specified per buffer. Thanks to Gary Holloway for these changes.","package":"showmarks.zip","4":"showmarks.zip","src_id":"2800","5":"2800","creation_date":"1078358229","6":"1078358229"},{"0":"152","vim_version":"6.0","1":"6.0","script_version":"2.0","2":"2.0","version_comment":"This version adds support for all other marks, enhanced customization of how marks are displayed and a few bug fixes.  Special thanks to everyone who contributed to this release.","3":"This version adds support for all other marks, enhanced customization of how marks are displayed and a few bug fixes.  Special thanks to everyone who contributed to this release.","package":"showmarks.zip","4":"showmarks.zip","src_id":"2220","5":"2220","creation_date":"1060576601","6":"1060576601"},{"0":"152","vim_version":"6.0","1":"6.0","script_version":"1.5","2":"1.5","version_comment":"Added the ability to customize how the marks are displayed.","3":"Added the ability to customize how the marks are displayed.","package":"showmarks.zip","4":"showmarks.zip","src_id":"1020","5":"1020","creation_date":"1026782212","6":"1026782212"},{"0":"152","vim_version":"6.0","1":"6.0","script_version":"1.4","2":"1.4","version_comment":"This version has support for placing the next available mark, support for hiding all marks in the current buffer, marks on line 1 are no longer shown, and includes a help file.\r\nIt is now packaged as a Zip archive.","3":"This version has support for placing the next available mark, support for hiding all marks in the current buffer, marks on line 1 are no longer shown, and includes a help file.\r\nIt is now packaged as a Zip archive.","package":"showmarks.zip","4":"showmarks.zip","src_id":"894","5":"894","creation_date":"1022709336","6":"1022709336"},{"0":"152","vim_version":"6.0","1":"6.0","script_version":"1.3","2":"1.3","version_comment":"Fixed toggling ShowMarks not responding immediately. Added user commands for toggling\/hiding marks. Added ability to disable ShowMarks by default.","3":"Fixed toggling ShowMarks not responding immediately. Added user commands for toggling\/hiding marks. Added ability to disable ShowMarks by default.","package":"showmarks.vim","4":"showmarks.vim","src_id":"881","5":"881","creation_date":"1021859813","6":"1021859813"},{"0":"152","vim_version":"6.0","1":"6.0","script_version":"1.2","2":"1.2","version_comment":"Added the ability to define which marks are shown\/ignored, added a check to make sure Vim has signs support, and removed some debugging code I accidently left in.","3":"Added the ability to define which marks are shown\/ignored, added a check to make sure Vim has signs support, and removed some debugging code I accidently left in.","package":"showmarks.vim","4":"showmarks.vim","src_id":"655","5":"655","creation_date":"1015434580","6":"1015434580"},{"0":"152","vim_version":"6.0","1":"6.0","script_version":"1.1","2":"1.1","version_comment":"Added support for the A-Z marks and fixed the sign staying placed if the line it is on was deleted.","3":"Added support for the A-Z marks and fixed the sign staying placed if the line it is on was deleted.","package":"showmarks.vim","4":"showmarks.vim","src_id":"559","5":"559","creation_date":"1012936002","6":"1012936002"},{"0":"152","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"showmarks.vim","4":"showmarks.vim","src_id":"361","5":"361","creation_date":"1006287079","6":"1006287079"}]},"151":{"script_id":"151","0":"151","script_name":"cisco-syntax.tar.gz","1":"cisco-syntax.tar.gz","script_type":"syntax","2":"syntax","summary":"Cisco config syntax file","3":"Cisco config syntax file","description":"first pass at a syntax for cisco router configs. Comments suggestion are most welcome.\r\n","4":"first pass at a syntax for cisco router configs. Comments suggestion are most welcome.\r\n","install_details":"copy to syntax directory, load config and set filetype=cisco\r\n","5":"copy to syntax directory, load config and set filetype=cisco\r\n","first_name":"Harry","6":"Harry","last_name":"Schroeder","7":"Schroeder","releases":[{"0":"151","vim_version":"6.0","1":"6.0","script_version":"1.2","2":"1.2","version_comment":"Completely rewrited. I include this plugin to my vimconfig project:\nhttp:\/\/vim.sourceforge.net\/scripts\/script.php?script_id=204\n","3":"Completely rewrited. I include this plugin to my vimconfig project:\nhttp:\/\/vim.sourceforge.net\/scripts\/script.php?script_id=204\n","package":"template.gz","4":"template.gz","src_id":"557","5":"557","creation_date":"1012934716","6":"1012934716"},{"0":"151","vim_version":"6.0","1":"6.0","script_version":"1.1","2":"1.1","version_comment":"Additions thanks to matt okeson-harlow to help with cmts or ubr configs\r\n\r\n","3":"Additions thanks to matt okeson-harlow to help with cmts or ubr configs\r\n\r\n","package":"cisco-syntax.tar.gz","4":"cisco-syntax.tar.gz","src_id":"446","5":"446","creation_date":"1010087166","6":"1010087166"},{"0":"151","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"cisco-syntax.tar.gz","4":"cisco-syntax.tar.gz","src_id":"358","5":"358","creation_date":"1006010675","6":"1006010675"}]},"150":{"script_id":"150","0":"150","script_name":"undoins.vim","1":"undoins.vim","script_type":"utility","2":"utility","summary":"Undeleted the immediate previous <C-W> or <C-U> action.","3":"Undeleted the immediate previous <C-W> or <C-U> action.","description":"- Vim provides a number or ways to recover some text that you have deleted\r\n  (multiple undos, numbered registers, unnamed register etc.), however,\r\n  there is no way to recover a line or word that you killed either\r\n  accidentally (e.g., pressing <C-W> one extra time) or deliberately if you\r\n  are already in insert mode.\r\n- This little script tries to compensate for this missing functionality for\r\n  the most commonly used two commands, <C-W> and <C-U> such that the text\r\n  that is going to be killed is first backed up in an internal script\r\n  variable before letting Vim continue to do what you asked it to do.\r\n- The script also provides a mapping (by default <C-X><C-U> which you can\r\n  customize by using the <Plug>UndoInInsModeUndoKey mapping) that you can\r\n  execute to put back the text at the current cursor position. A <C-X><C-U>\r\n  immediately followed by a <C-U> or <C-W> is effectively works like an undo\r\n  of the previous action.\r\n- The script is only going to \"estimate\" what is going to be deleted by ^W,\r\n  but for certain filetypes it may not exactly match the word that Vim is\r\n  going to delete, in which case the undo might undo too much or too little.\r\n\r\n\r\nThis is essentially a 6.0 version of my previous undoInInsertMode.vim script,\r\n  except that the script works much better now for ^W, thanks to Luc Hermitte\r\n  (hermitte at laas dot fr) for helping me get this done.\r\n\r\n\r\nSearch_key_words: undo insert mode undoins undoins.vim Hari Krishna Dara","4":"- Vim provides a number or ways to recover some text that you have deleted\r\n  (multiple undos, numbered registers, unnamed register etc.), however,\r\n  there is no way to recover a line or word that you killed either\r\n  accidentally (e.g., pressing <C-W> one extra time) or deliberately if you\r\n  are already in insert mode.\r\n- This little script tries to compensate for this missing functionality for\r\n  the most commonly used two commands, <C-W> and <C-U> such that the text\r\n  that is going to be killed is first backed up in an internal script\r\n  variable before letting Vim continue to do what you asked it to do.\r\n- The script also provides a mapping (by default <C-X><C-U> which you can\r\n  customize by using the <Plug>UndoInInsModeUndoKey mapping) that you can\r\n  execute to put back the text at the current cursor position. A <C-X><C-U>\r\n  immediately followed by a <C-U> or <C-W> is effectively works like an undo\r\n  of the previous action.\r\n- The script is only going to \"estimate\" what is going to be deleted by ^W,\r\n  but for certain filetypes it may not exactly match the word that Vim is\r\n  going to delete, in which case the undo might undo too much or too little.\r\n\r\n\r\nThis is essentially a 6.0 version of my previous undoInInsertMode.vim script,\r\n  except that the script works much better now for ^W, thanks to Luc Hermitte\r\n  (hermitte at laas dot fr) for helping me get this done.\r\n\r\n\r\nSearch_key_words: undo insert mode undoins undoins.vim Hari Krishna Dara","install_details":"Source it from .vimrc or drop it in the plugin directory.","5":"Source it from .vimrc or drop it in the plugin directory.","first_name":"Hari Krishna","6":"Hari Krishna","last_name":"Dara","7":"Dara","releases":[{"0":"150","vim_version":"6.0","1":"6.0","script_version":"1.1","2":"1.1","version_comment":"Now the script keeps track of the column where the editing started (through the '^ marker) to undo more precisely.","3":"Now the script keeps track of the column where the editing started (through the '^ marker) to undo more precisely.","package":"undoins.vim","4":"undoins.vim","src_id":"2779","5":"2779","creation_date":"1077651199","6":"1077651199"},{"0":"150","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"undoins.vim","4":"undoins.vim","src_id":"357","5":"357","creation_date":"1005928539","6":"1005928539"}]},"149":{"script_id":"149","0":"149","script_name":"darkslategray.vim","1":"darkslategray.vim","script_type":"color scheme","2":"color scheme","summary":"Dark slate gray background, pastel colored text","3":"Dark slate gray background, pastel colored text","description":"Emacs in RedHat Linux used to have (still does?) a kind of 'Wheat on DarkSlateGray' color scheme by default. This color scheme is created in the same spirit.\r\n\r\nDarkslategray is intended to be nice to your eyes (low contrast) and to take advantage of syntax hilighting as much as possible.\r\n\r\nscreenshot (rather old):\r\nhttp:\/\/www.hut.fi\/~tsusi\/vim\/darkslategray.png","4":"Emacs in RedHat Linux used to have (still does?) a kind of 'Wheat on DarkSlateGray' color scheme by default. This color scheme is created in the same spirit.\r\n\r\nDarkslategray is intended to be nice to your eyes (low contrast) and to take advantage of syntax hilighting as much as possible.\r\n\r\nscreenshot (rather old):\r\nhttp:\/\/www.hut.fi\/~tsusi\/vim\/darkslategray.png","install_details":"Copy to $VIM\/colors or .vim\/colors directory.\r\nRestart vim.\r\n:colorscheme darkslategray\r\nor\r\nchoose Edit\/Color Scheme\/darkslategray from the GUI menu.","5":"Copy to $VIM\/colors or .vim\/colors directory.\r\nRestart vim.\r\n:colorscheme darkslategray\r\nor\r\nchoose Edit\/Color Scheme\/darkslategray from the GUI menu.","first_name":"Tuomas","6":"Tuomas","last_name":"Susi","7":"Susi","releases":[{"0":"149","vim_version":"6.0","1":"6.0","script_version":"1.7","2":"1.7","version_comment":"More small tweaks for consistency in C\/C++\/Java code syntax highlighting and good looks with file-explorer and windmanager-type plugins.","3":"More small tweaks for consistency in C\/C++\/Java code syntax highlighting and good looks with file-explorer and windmanager-type plugins.","package":"darkslategray.vim","4":"darkslategray.vim","src_id":"3523","5":"3523","creation_date":"1097103762","6":"1097103762"},{"0":"149","vim_version":"6.0","1":"6.0","script_version":"1.6","2":"1.6","version_comment":"A number of small tweaks for consistency. Fileformat is now unix and color definitions are raw RGB, so this should now work in all systems.","3":"A number of small tweaks for consistency. Fileformat is now unix and color definitions are raw RGB, so this should now work in all systems.","package":"darkslategray.vim","4":"darkslategray.vim","src_id":"3506","5":"3506","creation_date":"1096515225","6":"1096515225"},{"0":"149","vim_version":"6.0","1":"6.0","script_version":"1.4","2":"1.4","version_comment":"Better preprocessor and tag colors.","3":"Better preprocessor and tag colors.","package":"darkslategray.vim","4":"darkslategray.vim","src_id":"2093","5":"2093","creation_date":"1055899009","6":"1055899009"},{"0":"149","vim_version":"6.0","1":"6.0","script_version":"1.3","2":"1.3","version_comment":"Search highlighting and TODO items now look different. Small fixes.","3":"Search highlighting and TODO items now look different. Small fixes.","package":"darkslategray.vim","4":"darkslategray.vim","src_id":"644","5":"644","creation_date":"1014720754","6":"1014720754"},{"0":"149","vim_version":"6.0","1":"6.0","script_version":"1.2","2":"1.2","version_comment":"Preprocessor colors are now more consistent. (By Srinath Avadhanula)","3":"Preprocessor colors are now more consistent. (By Srinath Avadhanula)","package":"darkslategray.vim","4":"darkslategray.vim","src_id":"514","5":"514","creation_date":"1012102549","6":"1012102549"},{"0":"149","vim_version":"6.0","1":"6.0","script_version":"1.1","2":"1.1","version_comment":"Small changes to line numbers etc.","3":"Small changes to line numbers etc.","package":"darkslategray.vim","4":"darkslategray.vim","src_id":"511","5":"511","creation_date":"1011964157","6":"1011964157"},{"0":"149","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"darkslategray.vim","4":"darkslategray.vim","src_id":"355","5":"355","creation_date":"1005888655","6":"1005888655"}]},"148":{"script_id":"148","0":"148","script_name":"perl_io.vim","1":"perl_io.vim","script_type":"utility","2":"utility","summary":"Perl : using 'print' and 'printf' instead of 'VIM::Msg'","3":"Perl : using 'print' and 'printf' instead of 'VIM::Msg'","description":"This plugin uses 'Tie::Handle' mechanism to create two output handles: VIMOUT and VIMERR. Then standard output is\r\nassociated with VIMOUT. This allows normal use of 'print' and 'printf' operators:\r\n\r\n\t:perl << EOP\r\n\t\tprint 'Line:', $curwin->(Cursor())[0];\r\n\t\tprintf '%d:%d\", $curwin->Cursor();\r\n\t\tprint VIMERR \"Error: $!\";\r\n\tEOP\r\n\r\nValue in $, is handled correctly:\r\n\t\r\n\t:perl $, = '; ';\r\n\t:perl print 'a' .. 'e'; # prints 'a; b; c; d; e'\r\n\r\nValue in $\\ is ignored and  there is no buffering, so it works as if $\\ was set to \"\\n\":\r\n\r\n\t:perl print 'one'; print 'two' \r\n\t\r\nprints same as \r\n\t\r\n\t:perl print \"one\\ntwo\"\r\n","4":"This plugin uses 'Tie::Handle' mechanism to create two output handles: VIMOUT and VIMERR. Then standard output is\r\nassociated with VIMOUT. This allows normal use of 'print' and 'printf' operators:\r\n\r\n\t:perl << EOP\r\n\t\tprint 'Line:', $curwin->(Cursor())[0];\r\n\t\tprintf '%d:%d\", $curwin->Cursor();\r\n\t\tprint VIMERR \"Error: $!\";\r\n\tEOP\r\n\r\nValue in $, is handled correctly:\r\n\t\r\n\t:perl $, = '; ';\r\n\t:perl print 'a' .. 'e'; # prints 'a; b; c; d; e'\r\n\r\nValue in $\\ is ignored and  there is no buffering, so it works as if $\\ was set to \"\\n\":\r\n\r\n\t:perl print 'one'; print 'two' \r\n\t\r\nprints same as \r\n\t\r\n\t:perl print \"one\\ntwo\"\r\n","install_details":"Drop in your plugin directory.","5":"Drop in your plugin directory.","first_name":"Serguei","6":"Serguei","last_name":"Jidkov","7":"Jidkov","releases":[{"0":"148","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"perl_io.vim","4":"perl_io.vim","src_id":"352","5":"352","creation_date":"1005819772","6":"1005819772"}]},"147":{"script_id":"147","0":"147","script_name":"SearchCompl.vim","1":"SearchCompl.vim","script_type":"utility","2":"utility","summary":"Completion on the '\/' search line.","3":"Completion on the '\/' search line.","description":"Similar to CmdlineCompl that it does the\r\ncompletion in-line, and without the use of cedit.  (Also originally by Stefan Roemer, thanks Stefan!).","4":"Similar to CmdlineCompl that it does the\r\ncompletion in-line, and without the use of cedit.  (Also originally by Stefan Roemer, thanks Stefan!).","install_details":"Drop in your plugin directory.","5":"Drop in your plugin directory.","first_name":"Douglas","6":"Douglas","last_name":"Potts","7":"Potts","releases":[{"0":"147","vim_version":"6.0","1":"6.0","script_version":"1.1","2":"1.1","version_comment":"Initial upload","3":"Initial upload","package":"SearchCompl.vim","4":"SearchCompl.vim","src_id":"351","5":"351","creation_date":"1005818903","6":"1005818903"}]},"146":{"script_id":"146","0":"146","script_name":"CmdlineCompl.vim","1":"CmdlineCompl.vim","script_type":"utility","2":"utility","summary":"Completion behavior on the command line. Without cedit.","3":"Completion behavior on the command line. Without cedit.","description":"Script for getting regular insert mode type completion, while on the command line.\r\nOriginally posted by Stefan Roemer, allows completion without needing the commandline edit window.","4":"Script for getting regular insert mode type completion, while on the command line.\r\nOriginally posted by Stefan Roemer, allows completion without needing the commandline edit window.","install_details":"drop in your plugin directory.","5":"drop in your plugin directory.","first_name":"Douglas","6":"Douglas","last_name":"Potts","7":"Potts","releases":[{"0":"146","vim_version":"6.0","1":"6.0","script_version":"1.1","2":"1.1","version_comment":"Initial upload","3":"Initial upload","package":"CmdlineCompl.vim","4":"CmdlineCompl.vim","src_id":"350","5":"350","creation_date":"1005818772","6":"1005818772"}]},"145":{"script_id":"145","0":"145","script_name":"increment.vim","1":"increment.vim","script_type":"utility","2":"utility","summary":"quickly create incremented lists","3":"quickly create incremented lists","description":"Sometimes you want to search for a string in the text \r\nand add an auto incremented number to each occurence of the string. \r\nLet's say, you want to make a numbered list. \r\nYou write something like:\r\nqwerty: The first line\r\nqwerty: the second one\r\nqwerty: and so on ...\r\nThen you type a command\r\n:let I=0\r\nfollowed by a replace command\r\n:%s\/qwerty\/\\=INC(1)\/\r\nThe first 'qwerty' is replaced by number 1, \r\nthe second by number 2, and so on... .\r\nSometimes you might want to generate numbers with a leadimg zeroes. \r\nYou simply initialize global variable I to value like \r\n:let I=99890000\r\nthen you make the replacement \r\n:%s\/my_token_word\/\\=INC(1)\/g\r\nfollowed by\r\n:%s\/9989\/\/g\r\n\r\nYou have to initialize a global variable I \r\nbefore the first use of INC() function,\r\nothervise the numbering will continue where it stopped \r\nduring the last replace.\r\n\r\nText Pad has a very similar metacharacter for replacement - \\i.","4":"Sometimes you want to search for a string in the text \r\nand add an auto incremented number to each occurence of the string. \r\nLet's say, you want to make a numbered list. \r\nYou write something like:\r\nqwerty: The first line\r\nqwerty: the second one\r\nqwerty: and so on ...\r\nThen you type a command\r\n:let I=0\r\nfollowed by a replace command\r\n:%s\/qwerty\/\\=INC(1)\/\r\nThe first 'qwerty' is replaced by number 1, \r\nthe second by number 2, and so on... .\r\nSometimes you might want to generate numbers with a leadimg zeroes. \r\nYou simply initialize global variable I to value like \r\n:let I=99890000\r\nthen you make the replacement \r\n:%s\/my_token_word\/\\=INC(1)\/g\r\nfollowed by\r\n:%s\/9989\/\/g\r\n\r\nYou have to initialize a global variable I \r\nbefore the first use of INC() function,\r\nothervise the numbering will continue where it stopped \r\nduring the last replace.\r\n\r\nText Pad has a very similar metacharacter for replacement - \\i.","install_details":"Put increment.vim into a plugin directory.\r\nUse in replacement strings\r\n:%s\/my_token_word_to_be_replaced_by_the_auto_incremented_numbers\/\\=INC(1)\/g","5":"Put increment.vim into a plugin directory.\r\nUse in replacement strings\r\n:%s\/my_token_word_to_be_replaced_by_the_auto_incremented_numbers\/\\=INC(1)\/g","first_name":"stanislav","6":"stanislav","last_name":"sitar","7":"sitar","releases":[{"0":"145","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"increment.vim","4":"increment.vim","src_id":"349","5":"349","creation_date":"1005801973","6":"1005801973"}]},"144":{"script_id":"144","0":"144","script_name":"chcmdmod.vim","1":"chcmdmod.vim","script_type":"utility","2":"utility","summary":"Misc. commands for search and colon mode","3":"Misc. commands for search and colon mode","description":"This script evolved from a mistake that I used to sometimes make. To start a search, instead of using \"\/\", I would sometimes start with \":\" and after typing some text realize I am in the wrong mode, so I wrote this plugin to be able to switch between modes without loosing the text that you already typed, but I added more features to it later.\r\n\r\n- When you are in one of the :, \/ or ? modes, switch to a different mode\r\n  by typing ^X\/ or ^X: or ^X?.\r\n- While searching you can press ^S to find the next hit, without needing to\r\n  first press <Enter> followed by n or N. You need to have 'incsearch'\r\n  option turned on for this to work. You can mix this with the ^X\/ and ^X?\r\n  to reverse the search without needing to press enter and start over.\r\n- While searching using 'incsearch', you can use ^Xw to complete the\r\n  current word (or ^XW for WORD), <S-Right> to fetch one extra character\r\n  from the end of current match position (or <S-Left> from the beginning).\r\n\r\n\r\n\r\n\r\nSearch_key_words: command chcmdmod change search Hari Krishna Dara","4":"This script evolved from a mistake that I used to sometimes make. To start a search, instead of using \"\/\", I would sometimes start with \":\" and after typing some text realize I am in the wrong mode, so I wrote this plugin to be able to switch between modes without loosing the text that you already typed, but I added more features to it later.\r\n\r\n- When you are in one of the :, \/ or ? modes, switch to a different mode\r\n  by typing ^X\/ or ^X: or ^X?.\r\n- While searching you can press ^S to find the next hit, without needing to\r\n  first press <Enter> followed by n or N. You need to have 'incsearch'\r\n  option turned on for this to work. You can mix this with the ^X\/ and ^X?\r\n  to reverse the search without needing to press enter and start over.\r\n- While searching using 'incsearch', you can use ^Xw to complete the\r\n  current word (or ^XW for WORD), <S-Right> to fetch one extra character\r\n  from the end of current match position (or <S-Left> from the beginning).\r\n\r\n\r\n\r\n\r\nSearch_key_words: command chcmdmod change search Hari Krishna Dara","install_details":"Source this file from your .vimrc or just drop it in your plugin directory.\r\n\r\nFor versions prior to 2.0:\r\nRequires curcmdmode.vim(1.0) (vimscript #745).","5":"Source this file from your .vimrc or just drop it in your plugin directory.\r\n\r\nFor versions prior to 2.0:\r\nRequires curcmdmode.vim(1.0) (vimscript #745).","first_name":"Hari Krishna","6":"Hari Krishna","last_name":"Dara","7":"Dara","releases":[{"0":"144","vim_version":"7.0","1":"7.0","script_version":"2.0","2":"2.0","version_comment":"Release 2.0 for Vim7. A lot of it is rewritten to use the new Vim7\r\nfeatures and it is much cleaner and safer now (thanks to the new\r\ngetcmdtype() function). Also, it no longer depends on any other plugins.\r\nNow includes commands to retrieve characters from the search location.\r\n","3":"Release 2.0 for Vim7. A lot of it is rewritten to use the new Vim7\r\nfeatures and it is much cleaner and safer now (thanks to the new\r\ngetcmdtype() function). Also, it no longer depends on any other plugins.\r\nNow includes commands to retrieve characters from the search location.\r\n","package":"chcmdmod.vim","4":"chcmdmod.vim","src_id":"5665","5":"5665","creation_date":"1147199485","6":"1147199485"},{"0":"144","vim_version":"6.0","1":"6.0","script_version":"1.0.3","2":"1.0.3","version_comment":"Added an experimental emacs-like feature. Vim already has a nice feature called 'incsearch' which is pretty useful. I have added a ^S command to the search prompt to take you to next search without having to press Enter and type n command. This is how you use it:\r\n\r\n- open a file and make sure you have 'incsearch' on.\r\n- start typing a search pattern, say \/public\r\n- without pressing Enter, Type ^S. You can see that you are taken to the next hit. Keep going.\r\n- when you want to do a reverse search, just type ^X? and observe that you are now in ? prompt.\r\n- you can start typing ^S again to go to the previous hits.\r\n- when you want the cursor to move to a hit, just press enter as you would normally.\r\n- if you want to cancel the search you can do so, but the original cursor position is restored only if you use ^U or Esc.\r\n\r\nAlso cleaned up the script a lot and fixed some misc. bugs. But before you start using the script, please be advised that it maps the ? \/ and : keys in normal mode. It tried to preserve your existing mapping for these keys (I have the \/ and ? mapped to turn on hlsearch and it continues to work even with the script), but I can't gaurantee that it will always work, so try the script and if you don't face any problems, you can start using it regularly. If you face any problems, please report it to me and I will try to solve it.\r\n\r\nPlease send in your comments.","3":"Added an experimental emacs-like feature. Vim already has a nice feature called 'incsearch' which is pretty useful. I have added a ^S command to the search prompt to take you to next search without having to press Enter and type n command. This is how you use it:\r\n\r\n- open a file and make sure you have 'incsearch' on.\r\n- start typing a search pattern, say \/public\r\n- without pressing Enter, Type ^S. You can see that you are taken to the next hit. Keep going.\r\n- when you want to do a reverse search, just type ^X? and observe that you are now in ? prompt.\r\n- you can start typing ^S again to go to the previous hits.\r\n- when you want the cursor to move to a hit, just press enter as you would normally.\r\n- if you want to cancel the search you can do so, but the original cursor position is restored only if you use ^U or Esc.\r\n\r\nAlso cleaned up the script a lot and fixed some misc. bugs. But before you start using the script, please be advised that it maps the ? \/ and : keys in normal mode. It tried to preserve your existing mapping for these keys (I have the \/ and ? mapped to turn on hlsearch and it continues to work even with the script), but I can't gaurantee that it will always work, so try the script and if you don't face any problems, you can start using it regularly. If you face any problems, please report it to me and I will try to solve it.\r\n\r\nPlease send in your comments.","package":"chcmdmod.vim","4":"chcmdmod.vim","src_id":"567","5":"567","creation_date":"1013107462","6":"1013107462"},{"0":"144","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"chcmdmod.vim","4":"chcmdmod.vim","src_id":"348","5":"348","creation_date":"1005757868","6":"1005757868"}]},"143":{"script_id":"143","0":"143","script_name":"words_tools.vim","1":"words_tools.vim","script_type":"utility","2":"utility","summary":"Alternatives to expand(","3":"Alternatives to expand(","description":"A tip would have been more accurate regarding what I am presenting here. But as some functions proposed are needed by another script of mine, here is a script file containing the definitions of three functions that can be used instead of expand(\"<cword>\").\r\n\r\nexpand(\"<cword>\") is a nice feature in VIM, but it is not very helpful when we have to deal with automatic completion -- you know : when you hit <tab> within VIM's command line or your favourite shell. Indeed, \"<cword>\" refers to the word under\/after the cursor, while we need the word under\/before the cursor.\r\n\r\nSo, here is three functions :\r\n* GetPreviousWord() that returns the word preceding the cursor ; the word is either truncated at the cursor's position or completed by as many spaces as needed to reach this position. I call a word, a sequence of keyword characters ('\\k', see :h isk).\r\n  It is handy, in C programming, to test what precedes the cursor when we hit '(', and then expand C control-structures (for, if, else, elif, switch, etc.) to anything desired.\r\n\r\n* GetCurrentWord() returns the word which is either stricly under the cursor or just before -- if the cursor is preceded by a space, an empty string is returned. Here, a word is a sequence of non white space characters : '\\S' -- in order to expand regular expressions. \r\n  Cf. http:\/\/vim.sourceforge.net\/scripts\/script.php?script_id=46 v2.2\r\n\r\n* GetNearestWord() returns the word ('\\S') either under, just before or just after the cursor.\r\n\r\nYou can take a look at a table showing the different returned values by this functions in equivalent contexts : http:\/\/hermitte.free.fr\/vim\/general.php3#expl_words_tools\r\n\r\nAs I said before, a tip would have been more appropriate. These functions are just examples of want could be done on this topic. They fulfill some specific needs I had. ","4":"A tip would have been more accurate regarding what I am presenting here. But as some functions proposed are needed by another script of mine, here is a script file containing the definitions of three functions that can be used instead of expand(\"<cword>\").\r\n\r\nexpand(\"<cword>\") is a nice feature in VIM, but it is not very helpful when we have to deal with automatic completion -- you know : when you hit <tab> within VIM's command line or your favourite shell. Indeed, \"<cword>\" refers to the word under\/after the cursor, while we need the word under\/before the cursor.\r\n\r\nSo, here is three functions :\r\n* GetPreviousWord() that returns the word preceding the cursor ; the word is either truncated at the cursor's position or completed by as many spaces as needed to reach this position. I call a word, a sequence of keyword characters ('\\k', see :h isk).\r\n  It is handy, in C programming, to test what precedes the cursor when we hit '(', and then expand C control-structures (for, if, else, elif, switch, etc.) to anything desired.\r\n\r\n* GetCurrentWord() returns the word which is either stricly under the cursor or just before -- if the cursor is preceded by a space, an empty string is returned. Here, a word is a sequence of non white space characters : '\\S' -- in order to expand regular expressions. \r\n  Cf. http:\/\/vim.sourceforge.net\/scripts\/script.php?script_id=46 v2.2\r\n\r\n* GetNearestWord() returns the word ('\\S') either under, just before or just after the cursor.\r\n\r\nYou can take a look at a table showing the different returned values by this functions in equivalent contexts : http:\/\/hermitte.free.fr\/vim\/general.php3#expl_words_tools\r\n\r\nAs I said before, a tip would have been more appropriate. These functions are just examples of want could be done on this topic. They fulfill some specific needs I had. ","install_details":"Drop it in your macros folder and source it when needed.\r\n\r\nNB: this \"library\" is now distributed as part of lh-vim-lib: http:\/\/www.vim.org\/scripts\/script.php?script_id=214","5":"Drop it in your macros folder and source it when needed.\r\n\r\nNB: this \"library\" is now distributed as part of lh-vim-lib: http:\/\/www.vim.org\/scripts\/script.php?script_id=214","first_name":"Luc","6":"Luc","last_name":"Hermitte","7":"Hermitte","releases":[{"0":"143","vim_version":"5.7","1":"5.7","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"words_tools.vim","4":"words_tools.vim","src_id":"344","5":"344","creation_date":"1005642400","6":"1005642400"}]},"142":{"script_id":"142","0":"142","script_name":"sql.vim","1":"sql.vim","script_type":"ftplugin","2":"ftplugin","summary":"This is a file type plugin for Oracle SQL files.","3":"This is a file type plugin for Oracle SQL files.","description":"This is a file type plugin for Oracle SQL files. This is a companion file\r\nfor oracle.vim script -Oracle IDE (http:\/\/vim.sourceforge.net\/scripts\/script.php?script_id=141) \r\n                                                                          \r\nThis has a lot of abbreviations, some mappings, few settings and syntax.\r\n","4":"This is a file type plugin for Oracle SQL files. This is a companion file\r\nfor oracle.vim script -Oracle IDE (http:\/\/vim.sourceforge.net\/scripts\/script.php?script_id=141) \r\n                                                                          \r\nThis has a lot of abbreviations, some mappings, few settings and syntax.\r\n","install_details":"Just drop it in your ftplugin folder\/directory\r\n","5":"Just drop it in your ftplugin folder\/directory\r\n","first_name":"Rajesh","6":"Rajesh","last_name":"Kallingal","7":"Kallingal","releases":[{"0":"142","vim_version":"6.0","1":"6.0","script_version":"6.0.4","2":"6.0.4","version_comment":"Replaced ^R ,^H,^M with <C-R>,<C-H>,<C-M>","3":"Replaced ^R ,^H,^M with <C-R>,<C-H>,<C-M>","package":"sql.vim","4":"sql.vim","src_id":"476","5":"476","creation_date":"1011084006","6":"1011084006"},{"0":"142","vim_version":"6.0","1":"6.0","script_version":"6.0.3","2":"6.0.3","version_comment":"Changed the Ctrl+D mapping to call the new function DescribeObject() in oracle.vim","3":"Changed the Ctrl+D mapping to call the new function DescribeObject() in oracle.vim","package":"sql.vim","4":"sql.vim","src_id":"464","5":"464","creation_date":"1010754864","6":"1010754864"},{"0":"142","vim_version":"6.0","1":"6.0","script_version":"6.0.2","2":"6.0.2","version_comment":"Fixed some intentation issues with some of the mappings","3":"Fixed some intentation issues with some of the mappings","package":"sql.vim","4":"sql.vim","src_id":"374","5":"374","creation_date":"1006761180","6":"1006761180"},{"0":"142","vim_version":"6.0","1":"6.0","script_version":"6.0.1","2":"6.0.1","version_comment":"Initial upload","3":"Initial upload","package":"sql.vim","4":"sql.vim","src_id":"339","5":"339","creation_date":"1005500475","6":"1005500475"}]},"141":{"script_id":"141","0":"141","script_name":"oracle.vim","1":"oracle.vim","script_type":"utility","2":"utility","summary":"Oracle SQL*Plus IDE","3":"Oracle SQL*Plus IDE","description":"Description:\r\nThis file contains functions\/menus\/commands\/abbreviations to make Vim an\r\nOracle SQL*Plus IDE.\r\nHere are the main highlights of this script:\r\n\r\n- SqlMake(): lets you open any stored procedure and compile from within vim.\r\n\t Will display and optionally highlight the errors, navigate\r\n\t thru errors in the quickfix mode.\r\n\t\r\n- Adds a SQL*Plus menu\r\n\r\n- SqlPlus(): lets you start an external SQL*Plus, execute the whole file\r\n\t contents in SQL*Plus and return the results back in the same\r\n\t buffer, or select a portion of the buffer, execute it and\r\n\t display the results in a new buffer.\r\n\r\n- GetSource(): get the stored procedure code from the database\r\n\r\n- Abbreviations: lot of abbreviations to make coding in PL\/SQL a breeze,\r\n\t all accessible thru menu as well\r\n\r\nMappings:\r\n\r\n  <Leader>c\tSelect Database dialog\r\n  <Leader>C\tGet column names for the tablename under cursor\r\n  <Leader>F\tStored procedure code from DB for the function\/procedure name\r\n  \t\tunder cursor\r\n  <Leader>i\tFind Invalid Objects\r\n  CTRL+S \t\tStart SQL*Plus window (external)\r\n  <Leader>r\tExecute current file in SQL*Plus window (external)\r\n  <Leader>s\tExecute current file in SQL*Plus and get the result to same\r\n  \t\tbuffer\r\n  <Leader>s\tExecute current selection in SQL*Plus and get the result to a\r\n  \t\tnew window\r\n\r\n  Following mappings from ftplugin sql.vim\r\n  <C-D>\t\tDescribe the object under cursor\r\n  <LocalLeader>d\tmake a dbms_output.put_line statement for word\/selection\r\n  \t\tbelow current line\r\n  <LocalLeader>D\tmake a dbms_output.put_line statement for word\/selection\r\n  \t\tabove current line\r\n\r\n\r\nOptional files:\r\n  sql.vim\t- sql filetype plugin load to your ftplugin folders. This file is\r\n  \t\t  needed for Abbreviations and some mappings\r\n\r\nNote:\r\n\tI have tested this only under gvim6.0 on Win2000 and Oracle 8.1.5. I do\r\n\tnot have any other platform to test these.\r\n\r\nScreen Shots:\r\nhttp:\/\/www.geocities.com\/rajesh_kallingal\/vim\/vimsql01.jpg\r\nhttp:\/\/www.geocities.com\/rajesh_kallingal\/vim\/vimsql02.jpg\r\nIf the above links don't work try this one.\r\nhttp:\/\/www.geocities.com\/rajesh_kallingal\/vim","4":"Description:\r\nThis file contains functions\/menus\/commands\/abbreviations to make Vim an\r\nOracle SQL*Plus IDE.\r\nHere are the main highlights of this script:\r\n\r\n- SqlMake(): lets you open any stored procedure and compile from within vim.\r\n\t Will display and optionally highlight the errors, navigate\r\n\t thru errors in the quickfix mode.\r\n\t\r\n- Adds a SQL*Plus menu\r\n\r\n- SqlPlus(): lets you start an external SQL*Plus, execute the whole file\r\n\t contents in SQL*Plus and return the results back in the same\r\n\t buffer, or select a portion of the buffer, execute it and\r\n\t display the results in a new buffer.\r\n\r\n- GetSource(): get the stored procedure code from the database\r\n\r\n- Abbreviations: lot of abbreviations to make coding in PL\/SQL a breeze,\r\n\t all accessible thru menu as well\r\n\r\nMappings:\r\n\r\n  <Leader>c\tSelect Database dialog\r\n  <Leader>C\tGet column names for the tablename under cursor\r\n  <Leader>F\tStored procedure code from DB for the function\/procedure name\r\n  \t\tunder cursor\r\n  <Leader>i\tFind Invalid Objects\r\n  CTRL+S \t\tStart SQL*Plus window (external)\r\n  <Leader>r\tExecute current file in SQL*Plus window (external)\r\n  <Leader>s\tExecute current file in SQL*Plus and get the result to same\r\n  \t\tbuffer\r\n  <Leader>s\tExecute current selection in SQL*Plus and get the result to a\r\n  \t\tnew window\r\n\r\n  Following mappings from ftplugin sql.vim\r\n  <C-D>\t\tDescribe the object under cursor\r\n  <LocalLeader>d\tmake a dbms_output.put_line statement for word\/selection\r\n  \t\tbelow current line\r\n  <LocalLeader>D\tmake a dbms_output.put_line statement for word\/selection\r\n  \t\tabove current line\r\n\r\n\r\nOptional files:\r\n  sql.vim\t- sql filetype plugin load to your ftplugin folders. This file is\r\n  \t\t  needed for Abbreviations and some mappings\r\n\r\nNote:\r\n\tI have tested this only under gvim6.0 on Win2000 and Oracle 8.1.5. I do\r\n\tnot have any other platform to test these.\r\n\r\nScreen Shots:\r\nhttp:\/\/www.geocities.com\/rajesh_kallingal\/vim\/vimsql01.jpg\r\nhttp:\/\/www.geocities.com\/rajesh_kallingal\/vim\/vimsql02.jpg\r\nIf the above links don't work try this one.\r\nhttp:\/\/www.geocities.com\/rajesh_kallingal\/vim","install_details":"Just drop it this file in your plugin folder\/directory.\r\n\r\nIf you are downloading 6.0.3 or prior version, to get some of the additional features you have to download the ftplugin sql.vim (http:\/\/vim.sourceforge.net\/scripts\/script.php?script_id=142) and put that\r\nin the ftplugin folder\/directory. This script is included in the zip file from 6.0.4 onwards\r\n","5":"Just drop it this file in your plugin folder\/directory.\r\n\r\nIf you are downloading 6.0.3 or prior version, to get some of the additional features you have to download the ftplugin sql.vim (http:\/\/vim.sourceforge.net\/scripts\/script.php?script_id=142) and put that\r\nin the ftplugin folder\/directory. This script is included in the zip file from 6.0.4 onwards\r\n","first_name":"Rajesh","6":"Rajesh","last_name":"Kallingal","7":"Kallingal","releases":[{"0":"141","vim_version":"6.0","1":"6.0","script_version":"6.0.4","2":"6.0.4","version_comment":"Changes:\r\n- Added online help (oracle.txt)\r\n- Save and retrieve connection info between sessions\r\n- created new function GetColumn() to handle inserting column names for the table.\r\n- redefined most of the connection variables.\r\n\r\nNow its a zip file with online document as well as the ftplugin sql.vim (script# 141)","3":"Changes:\r\n- Added online help (oracle.txt)\r\n- Save and retrieve connection info between sessions\r\n- created new function GetColumn() to handle inserting column names for the table.\r\n- redefined most of the connection variables.\r\n\r\nNow its a zip file with online document as well as the ftplugin sql.vim (script# 141)","package":"oracle.zip","4":"oracle.zip","src_id":"554","5":"554","creation_date":"1012905539","6":"1012905539"},{"0":"141","vim_version":"6.0","1":"6.0","script_version":"6.0.3","2":"6.0.3","version_comment":"Added DescribeObject function to fix the Ctrl+D mapping issue in sql.vim ftplugin","3":"Added DescribeObject function to fix the Ctrl+D mapping issue in sql.vim ftplugin","package":"oracle.vim","4":"oracle.vim","src_id":"463","5":"463","creation_date":"1010754746","6":"1010754746"},{"0":"141","vim_version":"6.0","1":"6.0","script_version":"6.0.2","2":"6.0.2","version_comment":"Changed the error highlighting method to use +signs if available","3":"Changed the error highlighting method to use +signs if available","package":"oracle.vim","4":"oracle.vim","src_id":"375","5":"375","creation_date":"1006761911","6":"1006761911"},{"0":"141","vim_version":"6.0","1":"6.0","script_version":"6.0.1","2":"6.0.1","version_comment":"Initial upload","3":"Initial upload","package":"oracle.vim","4":"oracle.vim","src_id":"338","5":"338","creation_date":"1005500095","6":"1005500095"}]},"140":{"script_id":"140","0":"140","script_name":"VirMark.vim","1":"VirMark.vim","script_type":"utility","2":"utility","summary":"Ability to create virtual marks.","3":"Ability to create virtual marks.","description":"Based on some advice given by Benji Fisher on utilizing a buffer local variable to store the current position.  It becomes a virtual mark as it doesn't take up one of the normal vim 'marks' a-zA-Z, instead it uses a variable.  They are local to a buffer, just like normal marks.  Useful for scripts that need to keep position, but don't want to change the user's mark setting.","4":"Based on some advice given by Benji Fisher on utilizing a buffer local variable to store the current position.  It becomes a virtual mark as it doesn't take up one of the normal vim 'marks' a-zA-Z, instead it uses a variable.  They are local to a buffer, just like normal marks.  Useful for scripts that need to keep position, but don't want to change the user's mark setting.","install_details":"Put in your plugin directory.  Can be used either from a Script or the command line.  Two user commands SetMark and GoMark.  Argument is just like normal mark  command a a-z character.","5":"Put in your plugin directory.  Can be used either from a Script or the command line.  Two user commands SetMark and GoMark.  Argument is just like normal mark  command a a-z character.","first_name":"Douglas","6":"Douglas","last_name":"Potts","7":"Potts","releases":[{"0":"140","vim_version":"6.0","1":"6.0","script_version":"1.1","2":"1.1","version_comment":"Initial upload","3":"Initial upload","package":"VirMark.vim","4":"VirMark.vim","src_id":"328","5":"328","creation_date":"1005228270","6":"1005228270"}]},"139":{"script_id":"139","0":"139","script_name":"which.vim","1":"which.vim","script_type":"utility","2":"utility","summary":"This is a unix like \"Which\" function.","3":"This is a unix like \"Which\" function.","description":"This is a unix like \"Which\" function.\r\nWe can check whether program was installed in script.\r\n:echo Which('wget')\r\n","4":"This is a unix like \"Which\" function.\r\nWe can check whether program was installed in script.\r\n:echo Which('wget')\r\n","install_details":"","5":"","first_name":"Yasuhiro","6":"Yasuhiro","last_name":"Matsumoto","7":"Matsumoto","releases":[{"0":"139","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"which.vim","4":"which.vim","src_id":"327","5":"327","creation_date":"1005189775","6":"1005189775"}]},"137":{"script_id":"137","0":"137","script_name":"ada.vim","1":"ada.vim","script_type":"indent","2":"indent","summary":"Ada language auto-indent settings","3":"Ada language auto-indent settings","description":"Sets indentexpr for Ada langauge; fairly comprehensive indent calculations, but don't expect 1G=G to work very well!  As it happens, it now seems to fare fairly well ...\r\n\r\nLet me know if you find a situation you'd like fixed.\r\n\r\nSee also Ada ftplugin, vimscript #136.","4":"Sets indentexpr for Ada langauge; fairly comprehensive indent calculations, but don't expect 1G=G to work very well!  As it happens, it now seems to fare fairly well ...\r\n\r\nLet me know if you find a situation you'd like fixed.\r\n\r\nSee also Ada ftplugin, vimscript #136.","install_details":"Replace delivered $VIMRUNTIME\/indent\/ada.vim with newer version.\r\n","5":"Replace delivered $VIMRUNTIME\/indent\/ada.vim with newer version.\r\n","first_name":"Neil","6":"Neil","last_name":"Bird","7":"Bird","releases":[{"0":"137","vim_version":"6.0","1":"6.0","script_version":"1.28","2":"1.28","version_comment":"A number of block-matching related bug fixes.\r\n","3":"A number of block-matching related bug fixes.\r\n","package":"ada.vim","4":"ada.vim","src_id":"3648","5":"3648","creation_date":"1101174040","6":"1101174040"},{"0":"137","vim_version":"6.0","1":"6.0","script_version":"1.27","2":"1.27","version_comment":"A couple of block indent recoveries (patch by Robert Nowotniak)","3":"A couple of block indent recoveries (patch by Robert Nowotniak)","package":"ada.vim","4":"ada.vim","src_id":"2777","5":"2777","creation_date":"1077598855","6":"1077598855"},{"0":"137","vim_version":"6.0","1":"6.0","script_version":"1.26","2":"1.26","version_comment":"Fix indent \/ block-matching after forward procedure specifications (Meikel Brandmeyer).","3":"Fix indent \/ block-matching after forward procedure specifications (Meikel Brandmeyer).","package":"ada.vim","4":"ada.vim","src_id":"2005","5":"2005","creation_date":"1053495780","6":"1053495780"},{"0":"137","vim_version":"6.0","1":"6.0","script_version":"1.25","2":"1.25","version_comment":"Fix 'end' after 'exception' mis-alignment.\r\nCope (hopefully) with multil-line 'thing is new other' declaration.","3":"Fix 'end' after 'exception' mis-alignment.\r\nCope (hopefully) with multil-line 'thing is new other' declaration.","package":"ada.vim","4":"ada.vim","src_id":"1902","5":"1902","creation_date":"1049784105","6":"1049784105"},{"0":"137","vim_version":"6.0","1":"6.0","script_version":"1.24","2":"1.24","version_comment":"Allow a procecure call's arg. list's leading \"(\" to be on next line (Serge Robyns).\r\nFix bug whilst checking for indent of previous multi-line statement after a \";\".","3":"Allow a procecure call's arg. list's leading \"(\" to be on next line (Serge Robyns).\r\nFix bug whilst checking for indent of previous multi-line statement after a \";\".","package":"ada.vim","4":"ada.vim","src_id":"1082","5":"1082","creation_date":"1028526509","6":"1028526509"},{"0":"137","vim_version":"6.0","1":"6.0","script_version":"1.22","2":"1.22","version_comment":"Cope correctly with generic package instances ('package is new' - Thomas Maier-Komor).","3":"Cope correctly with generic package instances ('package is new' - Thomas Maier-Komor).","package":"ada.vim","4":"ada.vim","src_id":"884","5":"884","creation_date":"1021962603","6":"1021962603"},{"0":"137","vim_version":"6.0","1":"6.0","script_version":"1.20","2":"1.20","version_comment":"Fix & enhance indent during\/after record definitions (Donald Bindner). \r\n","3":"Fix & enhance indent during\/after record definitions (Donald Bindner). \r\n","package":"ada.vim","4":"ada.vim","src_id":"761","5":"761","creation_date":"1017975733","6":"1017975733"},{"0":"137","vim_version":"6.0","1":"6.0","script_version":"1.19","2":"1.19","version_comment":"Stop 'beeping' bug when matching indent back to start of parenthesis pair.","3":"Stop 'beeping' bug when matching indent back to start of parenthesis pair.","package":"ada.vim","4":"ada.vim","src_id":"419","5":"419","creation_date":"1007955803","6":"1007955803"},{"0":"137","vim_version":"6.0","1":"6.0","script_version":"1.18","2":"1.18","version_comment":"Initial upload","3":"Initial upload","package":"ada.vim","4":"ada.vim","src_id":"324","5":"324","creation_date":"1005181396","6":"1005181396"}]},"136":{"script_id":"136","0":"136","script_name":"ada.vim","1":"ada.vim","script_type":"ftplugin","2":"ftplugin","summary":"Ada language default plugin","3":"Ada language default plugin","description":"Perform Ada specific completion & tagging.\r\n\r\nProvides mapping overrides for tag jumping that figure out the current Ada object and tag jump to that, not the 'simple' vim word.\r\n\r\nSimilarly allows <Ctrl-N> matching of full-length ada entities from tags.\r\n\r\nExports 'AdaWord()' function to return full name of Ada entity under the cursor (or at given line\/column), stripping whitespace\/newlines as necessary.\r\n\r\nSee also Ada indent script, vimscript #137.\r\n\r\n","4":"Perform Ada specific completion & tagging.\r\n\r\nProvides mapping overrides for tag jumping that figure out the current Ada object and tag jump to that, not the 'simple' vim word.\r\n\r\nSimilarly allows <Ctrl-N> matching of full-length ada entities from tags.\r\n\r\nExports 'AdaWord()' function to return full name of Ada entity under the cursor (or at given line\/column), stripping whitespace\/newlines as necessary.\r\n\r\nSee also Ada indent script, vimscript #137.\r\n\r\n","install_details":"Replace delivered $VIMRUNTIME\/ftplugin\/ada.vim with newer version.\r\n","5":"Replace delivered $VIMRUNTIME\/ftplugin\/ada.vim with newer version.\r\n","first_name":"Neil","6":"Neil","last_name":"Bird","7":"Bird","releases":[{"0":"136","vim_version":"6.0","1":"6.0","script_version":"1.7","2":"1.7","version_comment":"Initial upload","3":"Initial upload","package":"ada.vim","4":"ada.vim","src_id":"323","5":"323","creation_date":"1005180885","6":"1005180885"}]},"135":{"script_id":"135","0":"135","script_name":"vim-spell.tar.gz","1":"vim-spell.tar.gz","script_type":"utility","2":"utility","summary":"Another spell-checker plugin","3":"Another spell-checker plugin","description":"VIM-Spell is a spell-checker plugin for VIM based on Ispell or Aspell.\r\n\r\nThis plugin can parse a file and look for misspellings, highlight them, jump from one to another, choose the language, add new words to the dictionary, ignore some, and so on. \r\n\r\nThe main feature is probably the split window used to propose alternatives for a misspelling and to correct it. To give an idea, here is a little screenshot :\r\n    http:\/\/hermitte.free.fr\/vim\/ressources\/VS-capture.gif\r\n\r\nMore over, in order to speed up the processing, the calls to ispell\/aspell are regrouped. All the alternatives for every misspelling in the current document are cached in a local file. Then, obtaining the alternatives for a given misspelling is an instantaneous operation.\r\n\r\nFor more information, you can take a look at the help file archived in the\r\ntarball or look at :\r\n    http:\/\/hermitte.free.fr\/vim\/ressources\/vimfiles\/doc\/VS_help.html\r\nRem.: the site is quite slow.\r\n\r\nThe latest version have been tested with VIM 6.1 under a PC\/WindowsXP\/cmd.exe and PC\/WindowsXP\/Cygwin-bash.\r\n\r\nChangelog available at:\r\n http:\/\/hermitte.free.fr\/vim\/ressources\/vimfiles\/macros\/vim-spell\/ChangeLog\r\nBTW, you may find a more up-to-date version of the plugin at:\r\n http:\/\/hermitte.free.fr\/vim\/ressources\/\r\nNote: the latest versions are no longer compatible with Vim 5.x.\r\n","4":"VIM-Spell is a spell-checker plugin for VIM based on Ispell or Aspell.\r\n\r\nThis plugin can parse a file and look for misspellings, highlight them, jump from one to another, choose the language, add new words to the dictionary, ignore some, and so on. \r\n\r\nThe main feature is probably the split window used to propose alternatives for a misspelling and to correct it. To give an idea, here is a little screenshot :\r\n    http:\/\/hermitte.free.fr\/vim\/ressources\/VS-capture.gif\r\n\r\nMore over, in order to speed up the processing, the calls to ispell\/aspell are regrouped. All the alternatives for every misspelling in the current document are cached in a local file. Then, obtaining the alternatives for a given misspelling is an instantaneous operation.\r\n\r\nFor more information, you can take a look at the help file archived in the\r\ntarball or look at :\r\n    http:\/\/hermitte.free.fr\/vim\/ressources\/vimfiles\/doc\/VS_help.html\r\nRem.: the site is quite slow.\r\n\r\nThe latest version have been tested with VIM 6.1 under a PC\/WindowsXP\/cmd.exe and PC\/WindowsXP\/Cygwin-bash.\r\n\r\nChangelog available at:\r\n http:\/\/hermitte.free.fr\/vim\/ressources\/vimfiles\/macros\/vim-spell\/ChangeLog\r\nBTW, you may find a more up-to-date version of the plugin at:\r\n http:\/\/hermitte.free.fr\/vim\/ressources\/\r\nNote: the latest versions are no longer compatible with Vim 5.x.\r\n","install_details":"Uncompress the tarball archive into one of your paths from 'runtimepath'.\r\n\r\nThen, load lhVimSpell.vim from the ftplugin you want or drop the file into your plugins folder. Check the documentation for more explanations.\r\n\r\nIn order to work correctly, several things are required:\r\n- aspell or ispell : external spell-checkers ; required,\r\n- sort : *NIX external text tools -- be sure, they have priority over DOS tools ; optional since version 0.5,\r\n- a.vim, an old version is joined in the archive ; \r\n  http:\/\/vim.sf.net\/scripts\/script.php?script_id=31 ,\r\n  the latest is of no use for my plugin;\r\n- Triggers.vim http:\/\/vim.sourceforge.net\/scripts\/script.php?script_id=48 (optional since version 0.2b),\r\n\r\nN.B.: if you want to hack the plugin, you should download the \"developper version\"\r\n    http:\/\/hermitte.free.fr\/vim\/ressources\/vimfiles\/macros\/vim-spell-dev.tar.gz\r\n","5":"Uncompress the tarball archive into one of your paths from 'runtimepath'.\r\n\r\nThen, load lhVimSpell.vim from the ftplugin you want or drop the file into your plugins folder. Check the documentation for more explanations.\r\n\r\nIn order to work correctly, several things are required:\r\n- aspell or ispell : external spell-checkers ; required,\r\n- sort : *NIX external text tools -- be sure, they have priority over DOS tools ; optional since version 0.5,\r\n- a.vim, an old version is joined in the archive ; \r\n  http:\/\/vim.sf.net\/scripts\/script.php?script_id=31 ,\r\n  the latest is of no use for my plugin;\r\n- Triggers.vim http:\/\/vim.sourceforge.net\/scripts\/script.php?script_id=48 (optional since version 0.2b),\r\n\r\nN.B.: if you want to hack the plugin, you should download the \"developper version\"\r\n    http:\/\/hermitte.free.fr\/vim\/ressources\/vimfiles\/macros\/vim-spell-dev.tar.gz\r\n","first_name":"Luc","6":"Luc","last_name":"Hermitte","7":"Hermitte","releases":[{"0":"135","vim_version":"6.0","1":"6.0","script_version":"0.5","2":"0.5","version_comment":"Many changes, fixes, ... Now definitively working on MsWindows boxes; cf Changelog for more details","3":"Many changes, fixes, ... Now definitively working on MsWindows boxes; cf Changelog for more details","package":"vim-spell.tar.gz","4":"vim-spell.tar.gz","src_id":"1716","5":"1716","creation_date":"1044957629","6":"1044957629"},{"0":"135","vim_version":"5.7","1":"5.7","script_version":"0.3c","2":"0.3c","version_comment":"Bug fixes : (*) words can be added directly into local dictionary ; (*) mappings will works for several buffers (used to be a problem when calling vim with for instance 'vim *.tex').","3":"Bug fixes : (*) words can be added directly into local dictionary ; (*) mappings will works for several buffers (used to be a problem when calling vim with for instance 'vim *.tex').","package":"vim-spell.tar.gz","4":"vim-spell.tar.gz","src_id":"1039","5":"1039","creation_date":"1027360684","6":"1027360684"},{"0":"135","vim_version":"5.7","1":"5.7","script_version":"0.3b","2":"0.3b","version_comment":"No more error message when there is no misspelling. The syntax highlighting rules have been extended to support HTML files and some others filetypes ; the rules for TeX files have been enhanced.","3":"No more error message when there is no misspelling. The syntax highlighting rules have been extended to support HTML files and some others filetypes ; the rules for TeX files have been enhanced.","package":"vim-spell.tar.gz","4":"vim-spell.tar.gz","src_id":"1025","5":"1025","creation_date":"1026979864","6":"1026979864"},{"0":"135","vim_version":"5.7","1":"5.7","script_version":"0.3","2":"0.3","version_comment":"The plugin has been simplified. The number of files has been reduced to 3 ; it should be easier to install. ","3":"The plugin has been simplified. The number of files has been reduced to 3 ; it should be easier to install. ","package":"vim-spell.tar.gz","4":"vim-spell.tar.gz","src_id":"986","5":"986","creation_date":"1025715401","6":"1025715401"},{"0":"135","vim_version":"6.0","1":"6.0","script_version":"0.2d","2":"0.2d","version_comment":"The capitalization problem with the archive has been fixed. + some minor changes","3":"The capitalization problem with the archive has been fixed. + some minor changes","package":"vim-spell.tar.gz","4":"vim-spell.tar.gz","src_id":"976","5":"976","creation_date":"1025584874","6":"1025584874"},{"0":"135","vim_version":"5.7","1":"5.7","script_version":"0.2c","2":"0.2c","version_comment":"The list of words to be ignored is no more reset after every parsing. A dependency has been \"eased\". Some bugs fixed.","3":"The list of words to be ignored is no more reset after every parsing. A dependency has been \"eased\". Some bugs fixed.","package":"vim-spell.tar.gz","4":"vim-spell.tar.gz","src_id":"636","5":"636","creation_date":"1014628926","6":"1014628926"},{"0":"135","vim_version":"5.7","1":"5.7","script_version":"0.2b","2":"0.2b","version_comment":"There is no important improvments in this version. Only the dependancies have been reduced (help.vim is no more required, while triggers.vim has become optional)","3":"There is no important improvments in this version. Only the dependancies have been reduced (help.vim is no more required, while triggers.vim has become optional)","package":"vim-spell.tar.gz","4":"vim-spell.tar.gz","src_id":"583","5":"583","creation_date":"1013597128","6":"1013597128"},{"0":"135","vim_version":"5.7","1":"5.7","script_version":"0.2","2":"0.2","version_comment":"Some bugs have been fixed (accentuated characters can be inserted into personal dictionaries, ...); the color highlighting scheme with LaTeX is now correct; the dependancies have been reduced for VIM 6.","3":"Some bugs have been fixed (accentuated characters can be inserted into personal dictionaries, ...); the color highlighting scheme with LaTeX is now correct; the dependancies have been reduced for VIM 6.","package":"vim-spell.tar.gz","4":"vim-spell.tar.gz","src_id":"517","5":"517","creation_date":"1012302664","6":"1012302664"}]},"134":{"script_id":"134","0":"134","script_name":"djgpp.vim","1":"djgpp.vim","script_type":"utility","2":"utility","summary":"Compiler file for DJGPP","3":"Compiler file for DJGPP","description":"Compiler file to use QuickFix features with DJGPP compiler.","4":"Compiler file to use QuickFix features with DJGPP compiler.","install_details":"Simply copy in you \\vim60\\compiler \r\nThen you can use it with \r\ncompiler djgpp","5":"Simply copy in you \\vim60\\compiler \r\nThen you can use it with \r\ncompiler djgpp","first_name":"Vadim","6":"Vadim","last_name":"Volkov","7":"Volkov","releases":[{"0":"134","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"djgpp.vim","4":"djgpp.vim","src_id":"320","5":"320","creation_date":"1005024553","6":"1005024553"}]},"133":{"script_id":"133","0":"133","script_name":"TableTab.vim","1":"TableTab.vim","script_type":"utility","2":"utility","summary":"global plugin for variable-width tab stops","3":"global plugin for variable-width tab stops","description":"When active, TableTab.vim remaps the <Tab> key in insert mode, to\r\nthe function, which adjusts the tab stops according to the previous\r\nline.  If this line matches \/^\\s*[_=*\\-]\\+ *$\/  (it is only of ===,\r\n--- etc.) the line before is checked.\r\n\r\nShould be useful for editing tables.\r\n","4":"When active, TableTab.vim remaps the <Tab> key in insert mode, to\r\nthe function, which adjusts the tab stops according to the previous\r\nline.  If this line matches \/^\\s*[_=*\\-]\\+ *$\/  (it is only of ===,\r\n--- etc.) the line before is checked.\r\n\r\nShould be useful for editing tables.\r\n","install_details":"Just drop TableTab.vim into your plugin directory or source it from your vimrc.\r\nAfter sourcing, <Leader><Tab> will toggle between tab stops\r\nlookup and a normal function of the <Tab> key.\r\n","5":"Just drop TableTab.vim into your plugin directory or source it from your vimrc.\r\nAfter sourcing, <Leader><Tab> will toggle between tab stops\r\nlookup and a normal function of the <Tab> key.\r\n","first_name":"Pavol","6":"Pavol","last_name":"Juhas","7":"Juhas","releases":[{"0":"133","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"TableTab.vim","4":"TableTab.vim","src_id":"315","5":"315","creation_date":"1004887152","6":"1004887152"}]},"132":{"script_id":"132","0":"132","script_name":"PopupBuffer.vim","1":"PopupBuffer.vim","script_type":"utility","2":"utility","summary":"Vim global plugin for selecting buffer from PopUp menu","3":"Vim global plugin for selecting buffer from PopUp menu","description":"This script is an adaptation of the default list buffer menu from menu.vim file. With mousefocus on and horizontally splited windows, it's very difficult to select an other buffer for the bottom window from the Buffer menu :). With the PopupBuffer script, right-click on the bottom window and select an other buffer from the Buffers submenu.","4":"This script is an adaptation of the default list buffer menu from menu.vim file. With mousefocus on and horizontally splited windows, it's very difficult to select an other buffer for the bottom window from the Buffer menu :). With the PopupBuffer script, right-click on the bottom window and select an other buffer from the Buffers submenu.","install_details":"Requires to launch Vim with GUI mode. Put setmousemodel=popup or set mousemodel=popup_setpos to your .vimrc file. Copy this script to your ~\/.vim\/plugin directory, et voil\u00c3\u00a0 !","5":"Requires to launch Vim with GUI mode. Put setmousemodel=popup or set mousemodel=popup_setpos to your .vimrc file. Copy this script to your ~\/.vim\/plugin directory, et voil\u00c3\u00a0 !","first_name":"Gontran","6":"Gontran","last_name":"BAERTS","7":"BAERTS","releases":[{"0":"132","vim_version":"6.0","1":"6.0","script_version":"1.1.1","2":"1.1.1","version_comment":"- Fix stupid bug in PBAdd() function. Directories were added to popup buffers menu and never removed.","3":"- Fix stupid bug in PBAdd() function. Directories were added to popup buffers menu and never removed.","package":"PopupBuffer.vim","4":"PopupBuffer.vim","src_id":"347","5":"347","creation_date":"1005714485","6":"1005714485"},{"0":"132","vim_version":"6.0","1":"6.0","script_version":"1.1","2":"1.1","version_comment":"Vim global plugin for selecting buffer from PopUp menu.\r\nUpdates in version 1.1 :\r\n- Allow to control the menu item format with popupBufferPattern global variable. Use %F for full file path, %f for file name, %p for file path, and %n for buffer number.\r\nFor example:\r\nlet g:popupBufferPattern = \"Select %f (%n) from %p directory\"\r\n- Fix unremoved deleted buffers from menu\r\n- Improve addition of new item to menu. Don't add all buffers each time.\r\n","3":"Vim global plugin for selecting buffer from PopUp menu.\r\nUpdates in version 1.1 :\r\n- Allow to control the menu item format with popupBufferPattern global variable. Use %F for full file path, %f for file name, %p for file path, and %n for buffer number.\r\nFor example:\r\nlet g:popupBufferPattern = \"Select %f (%n) from %p directory\"\r\n- Fix unremoved deleted buffers from menu\r\n- Improve addition of new item to menu. Don't add all buffers each time.\r\n","package":"PopupBuffer.vim","4":"PopupBuffer.vim","src_id":"343","5":"343","creation_date":"1005630641","6":"1005630641"},{"0":"132","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"PopupBuffer.vim","4":"PopupBuffer.vim","src_id":"314","5":"314","creation_date":"1004690246","6":"1004690246"}]},"131":{"script_id":"131","0":"131","script_name":"spellcheck.vim","1":"spellcheck.vim","script_type":"utility","2":"utility","summary":"spell checker  for vim","3":"spell checker  for vim","description":"This script enables spell checking capabilities known from text \r\nprocessors:\r\n\r\n*SpellCheck: highlights all misspelled words\r\n*Propose: checks word under cursor - giving proposals for correcting\r\n*AddToDictionary: adds word under cursor to dictionary\r\n*SpchkNxt: jumps to next error\r\n*SpchkPrv: jumps to previous error\r\n*SetLanguageTag: which language to use (uk_UK | de_DE ...)\r\n*SpellAutoEnable: enables automatic higlighting of misspelled words\r\n  (this is done via CursorHold)\r\n*SpellAutoDisable: disables automatic check\r\n\r\nproblems:\r\n-syntax highlighting does not work correctly in every syntax-mode\r\n solution: set syntax=off and then do the spellcheck\r\n-to add a word to the list of known words, the skript has to know \r\n which private dictionary aspell is using (something like \r\n $HOME\/.aspell.xxx.pws where xxx depends on the language tag)\r\n the current relation is: \r\n   uk_UK|us_US -> english (.aspell.english.pws)\r\n   de_DE -> de (.aspell.de.pws)\r\n to add entries or change existing ones, there is a little adjustment table.\r\n","4":"This script enables spell checking capabilities known from text \r\nprocessors:\r\n\r\n*SpellCheck: highlights all misspelled words\r\n*Propose: checks word under cursor - giving proposals for correcting\r\n*AddToDictionary: adds word under cursor to dictionary\r\n*SpchkNxt: jumps to next error\r\n*SpchkPrv: jumps to previous error\r\n*SetLanguageTag: which language to use (uk_UK | de_DE ...)\r\n*SpellAutoEnable: enables automatic higlighting of misspelled words\r\n  (this is done via CursorHold)\r\n*SpellAutoDisable: disables automatic check\r\n\r\nproblems:\r\n-syntax highlighting does not work correctly in every syntax-mode\r\n solution: set syntax=off and then do the spellcheck\r\n-to add a word to the list of known words, the skript has to know \r\n which private dictionary aspell is using (something like \r\n $HOME\/.aspell.xxx.pws where xxx depends on the language tag)\r\n the current relation is: \r\n   uk_UK|us_US -> english (.aspell.english.pws)\r\n   de_DE -> de (.aspell.de.pws)\r\n to add entries or change existing ones, there is a little adjustment table.\r\n","install_details":"*you need aspell (plus dictionary ofcourse)\r\n*you need a ruby interpreter enabled\r\n*$LANG should be defined (echo $LANG on CLI prompt)\r\n\r\nSimply move the skript to your plugin directory. ","5":"*you need aspell (plus dictionary ofcourse)\r\n*you need a ruby interpreter enabled\r\n*$LANG should be defined (echo $LANG on CLI prompt)\r\n\r\nSimply move the skript to your plugin directory. ","first_name":"matthias","6":"matthias","last_name":"veit","7":"veit","releases":[{"0":"131","vim_version":"6.0","1":"6.0","script_version":"2.1","2":"2.1","version_comment":"After a replacement of a misspelled word jump to the next error (tend to be usefule while in correction mode). \r\n","3":"After a replacement of a misspelled word jump to the next error (tend to be usefule while in correction mode). \r\n","package":"spell.zip","4":"spell.zip","src_id":"980","5":"980","creation_date":"1025654826","6":"1025654826"},{"0":"131","vim_version":"6.0","1":"6.0","script_version":"2.0","2":"2.0","version_comment":"replacement of misspelled words via proposals (thanks to Patrick Sundberg), \r\nthe language to check can be selected via SetLanguageTag (which takes the\r\ncommon language tags like uk_UK, de_DE etc) - default is taken from $LANG","3":"replacement of misspelled words via proposals (thanks to Patrick Sundberg), \r\nthe language to check can be selected via SetLanguageTag (which takes the\r\ncommon language tags like uk_UK, de_DE etc) - default is taken from $LANG","package":"spell.zip","4":"spell.zip","src_id":"975","5":"975","creation_date":"1025576337","6":"1025576337"},{"0":"131","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"spellcheck.vim","4":"spellcheck.vim","src_id":"313","5":"313","creation_date":"1004629501","6":"1004629501"}]},"130":{"script_id":"130","0":"130","script_name":"usr2latex.pl","1":"usr2latex.pl","script_type":"utility","2":"utility","summary":"Convert vim usrguide txt files to latex","3":"Convert vim usrguide txt files to latex","description":"This script can be very useful to produce a readable book version of your usr_*.txt files.\r\nIt generates on its standard output a latex file from all the usr_*.txt.\r\n\r\nI know, it's far from perfect but it produced a quite good latex file for me.\r\nEmail me if you want to get latex, dvi or pdf generated output.","4":"This script can be very useful to produce a readable book version of your usr_*.txt files.\r\nIt generates on its standard output a latex file from all the usr_*.txt.\r\n\r\nI know, it's far from perfect but it produced a quite good latex file for me.\r\nEmail me if you want to get latex, dvi or pdf generated output.","install_details":"Install notes are included in the script:\r\nUsage:\r\n1)Copy this script to your vim doc directory(where files usr_*.txt are located).\r\n2)Launch it. The latex file is generated on its standard output.\r\n3)Don't forget to run latex three times on the generated file to get a valid toc.","5":"Install notes are included in the script:\r\nUsage:\r\n1)Copy this script to your vim doc directory(where files usr_*.txt are located).\r\n2)Launch it. The latex file is generated on its standard output.\r\n3)Don't forget to run latex three times on the generated file to get a valid toc.","first_name":"Christophe","6":"Christophe","last_name":"Gouiran","7":"Gouiran","releases":[{"0":"130","vim_version":"6.0","1":"6.0","script_version":"","2":"","version_comment":"Initial upload","3":"Initial upload","package":"usr2latex.pl","4":"usr2latex.pl","src_id":"299","5":"299","creation_date":"1003823044","6":"1003823044"}]},"129":{"script_id":"129","0":"129","script_name":"PushPop.vim","1":"PushPop.vim","script_type":"utility","2":"utility","summary":"Pushd\/Popd implementation for vim command-line","3":"Pushd\/Popd implementation for vim command-line","description":"PLEASE READ THE INSTALL SECTION.\r\n\r\n- The script provides a pushd\/popd functionality for Vim taking Bash as a\r\n  reference. It defines new commands called Pushd, Popd and Cd and Dirs.\r\n  It also defines abbreviations pushd and popd (the lower case versions)\r\n  to make it easier to type and get used to, but if it causes any\r\n  trouble for your regular command line typing (as the abbreviations are\r\n  expanded anywhere you type), just set the g:pushpopNoAbbrev variable in\r\n  your .vimrc, or install cmdalias.vim also along with PushPop.vim (in\r\n  which case additional abbreviations are defined for dirs and cdp as\r\n  well). The cmdalias.vim plugin provides support for defining\r\n  abbreviations that expand only at the start of the command-line, which\r\n  make the abbreviations behave just like bash aliases, or like the Vim\r\n  built-in commands (read the plugin's description for more information).\r\n- Most of the Bash pushd\/popd syntax is supported.\r\n- The plugin integrates seamlessly with the vim features such as 'cdpath'.\r\n  It handles the protected command and space chars correctly as expected,\r\n  however, unprotected spaces are not treated as separators (which is the\r\n  case with 'cdpath' for the sake of backward compatibility with age old\r\n  vim 3.0).\r\n- Vim provides a \"cd -\" command to quickly jump back to the previous\r\n  directory on the lines of bash, to make it complete, the script\r\n  sets the g:OLDPWD variable to mimic the $OLDPWD variable of bash.\r\n- The Cdp command will push the directory of the current file on to the\r\n  stack and cd into it.\r\n- It provides commands to make it easy to manipulate the \"cdpath\" and save\r\n  and restore it (unless the persistence feature of genutils.vim is\r\n  disabled), without needing to manually edit the vimrc. The \"PPAddDir\"\r\n  command will allow you to add the specified directory or the current\r\n  directory (with no arguments) to 'cdpath'. The \"PPRemoveDir\" command can\r\n  be used to remove a directory by its name or index, or just the current\r\n  directory (whith no arguments). Both commands accept \"-l\" as an option\r\n  to specify the directory argument literally (the directory name is then\r\n  not modified). The \"-l\" option with no arguments can also be used to\r\n  add\/remove \"empty\" directory entry (represented as ^, or ,, or ,$ in the\r\n  'cdpath'). If you need to add entried that have wild-cards in them (such\r\n  as \"src\/**\", the above commands can't be used as Vim will try to expand\r\n  the wildcards before the plugin can see them, so in this case use\r\n  \"PPAddPat\" and \"PPRemovePat\" commands. Pass \"-l\" option to avoid\r\n  modification.\r\n- To view the list of directories in your 'cdpath', use the regular \"set\r\n  cdpath?\" command or just \"Cdpath\". In addition, the \"Cd\" command accepts\r\n  \"-i\" option to cd directly into one of the directories in 'cdpath'. With\r\n  no arguments, you will be prompted with the list of directories to\r\n  select from, and with an index as the argument (starting from 0), you\r\n  can directly cd into the directory at that index.\r\n- If g:pushpopCdable_vars is set, the plugin emulates the bash\r\n  'cdable_vars' feature. When the built-in \":cd\" fails, the argument is\r\n  assumed to be the name of a global variable whose value is the directory\r\n  to change to. Normally, you don't necessarily need to use the :Cd\r\n  command instead of :cd command, but in this particular case, the feature\r\n  will not work unless you use the :Cd command. Consider aliasing :cd to\r\n  :Cd as described in Deprecations section below.\r\n- The main functions are also exposed as global functions, which can be used\r\n  by the script writers to recursively traverse directories and finally\r\n  return back to the original directory.\r\n\r\nPlease see the script header for more information such as deprecations etc.\r\n\r\nPlease send in your comments\/feedback\/suggestions\/contributions for improving the script.\r\n\r\n=================================================\r\nYou can refer to the bash manual page for more information on how to use Pushd, Popd and Dirs commands. In case you don't have access to it, here is an extract from bash man page (on cygwin):\r\n\r\n       pushd [-n] [dir]\r\n       pushd [-n] [+n] [-n]\r\n              Adds a directory to the top of the directory stack,\r\n              or  rotates  the  stack,  making the new top of the\r\n              stack the current working directory.  With no argu-\r\n              ments,   exchanges  the  top  two  directories  and\r\n              returns 0, unless the  directory  stack  is  empty.\r\n              Arguments,  if  supplied,  have the following mean-\r\n              ings:\r\n              +n     Rotates the stack so that the nth  directory\r\n                     (counting from the left of the list shown by\r\n                     dirs, starting with zero) is at the top.\r\n              -n     Rotates the stack so that the nth  directory\r\n                     (counting  from  the right of the list shown\r\n                     by dirs, starting with zero) is at the  top.\r\n              -n     Suppresses  the  normal  change of directory\r\n                     when adding directories  to  the  stack,  so\r\n                     that only the stack is manipulated.\r\n              dir    Adds  dir to the directory stack at the top,\r\n                     making it the new current working directory.\r\n\r\n              If  the pushd command is successful, a dirs is per-\r\n              formed as well.  If the first form is  used,  pushd\r\n              returns  0  unless  the  cd to dir fails.  With the\r\n              second form, pushd returns 0 unless  the  directory\r\n       popd [-n] [+n] [-n]\r\n              Removes  entries from the directory stack.  With no\r\n              arguments,  removes  the  top  directory  from  the\r\n              stack,  and performs a cd to the new top directory.\r\n              Arguments, if supplied, have  the  following  mean-\r\n              ings:\r\n              +n     Removes the nth entry counting from the left\r\n                     of the list shown  by  dirs,  starting  with\r\n                     zero.   For example: ``popd +0'' removes the\r\n                     first directory, ``popd +1'' the second.\r\n              -n     Removes the  nth  entry  counting  from  the\r\n                     right  of  the  list shown by dirs, starting\r\n                     with zero.  For example: ``popd -0'' removes\r\n                     the  last directory, ``popd -1'' the next to\r\n                     last.\r\n              -n     Suppresses the normal  change  of  directory\r\n                     when removing directories from the stack, so\r\n                     that only the stack is manipulated.\r\n\r\n              If the popd command is successful, a dirs  is  per-\r\n              formed  as  well, and the return status is 0.  popd\r\n              returns false if an invalid option is  encountered,\r\n              the directory stack is empty, a non-existent direc-\r\n              stack is empty, a non-existent directory stack ele-\r\n              ment is specified, or the directory change  to  the\r\n              specified new current directory fails.\r\n              tory stack entry is  specified,  or  the  directory\r\n              change fails.\r\n       dirs [-clpv] [+n] [-n]\r\n              Without  options,  displays  the  list of currently\r\n              remembered directories.  The default display is  on\r\n              a  single  line  with  directory names separated by\r\n              spaces.  Directories are added to the list with the\r\n              pushd  command;  the  popd  command removes entries\r\n              from the list.\r\n              +n     Displays the nth  entry  counting  from  the\r\n                     left  of the list shown by dirs when invoked\r\n                     without options, starting with zero.\r\n              -n     Displays the nth  entry  counting  from  the\r\n                     right of the list shown by dirs when invoked\r\n                     without options, starting with zero.\r\n              -c     Clears the directory stack by  deleting  all\r\n                     of the entries.\r\n              -l     Produces a longer listing; the default list-\r\n                     ing format uses a tilde to denote  the  home\r\n                     directory.\r\n              -p     Print the directory stack with one entry per\r\n                     line.\r\n              -v     Print the directory stack with one entry per\r\n                     line, prefixing each entry with its index in\r\n                     the stack.\r\n\r\n              The return value is 0 unless an invalid  option  is\r\n              supplied  or n indexes beyond the end of the direc-\r\n              tory stack.\r\n=================================================\r\n\r\nSearch_key_words: push pop directory cd change bash csh dirs pushpop genutils Hari Krishna Dara","4":"PLEASE READ THE INSTALL SECTION.\r\n\r\n- The script provides a pushd\/popd functionality for Vim taking Bash as a\r\n  reference. It defines new commands called Pushd, Popd and Cd and Dirs.\r\n  It also defines abbreviations pushd and popd (the lower case versions)\r\n  to make it easier to type and get used to, but if it causes any\r\n  trouble for your regular command line typing (as the abbreviations are\r\n  expanded anywhere you type), just set the g:pushpopNoAbbrev variable in\r\n  your .vimrc, or install cmdalias.vim also along with PushPop.vim (in\r\n  which case additional abbreviations are defined for dirs and cdp as\r\n  well). The cmdalias.vim plugin provides support for defining\r\n  abbreviations that expand only at the start of the command-line, which\r\n  make the abbreviations behave just like bash aliases, or like the Vim\r\n  built-in commands (read the plugin's description for more information).\r\n- Most of the Bash pushd\/popd syntax is supported.\r\n- The plugin integrates seamlessly with the vim features such as 'cdpath'.\r\n  It handles the protected command and space chars correctly as expected,\r\n  however, unprotected spaces are not treated as separators (which is the\r\n  case with 'cdpath' for the sake of backward compatibility with age old\r\n  vim 3.0).\r\n- Vim provides a \"cd -\" command to quickly jump back to the previous\r\n  directory on the lines of bash, to make it complete, the script\r\n  sets the g:OLDPWD variable to mimic the $OLDPWD variable of bash.\r\n- The Cdp command will push the directory of the current file on to the\r\n  stack and cd into it.\r\n- It provides commands to make it easy to manipulate the \"cdpath\" and save\r\n  and restore it (unless the persistence feature of genutils.vim is\r\n  disabled), without needing to manually edit the vimrc. The \"PPAddDir\"\r\n  command will allow you to add the specified directory or the current\r\n  directory (with no arguments) to 'cdpath'. The \"PPRemoveDir\" command can\r\n  be used to remove a directory by its name or index, or just the current\r\n  directory (whith no arguments). Both commands accept \"-l\" as an option\r\n  to specify the directory argument literally (the directory name is then\r\n  not modified). The \"-l\" option with no arguments can also be used to\r\n  add\/remove \"empty\" directory entry (represented as ^, or ,, or ,$ in the\r\n  'cdpath'). If you need to add entried that have wild-cards in them (such\r\n  as \"src\/**\", the above commands can't be used as Vim will try to expand\r\n  the wildcards before the plugin can see them, so in this case use\r\n  \"PPAddPat\" and \"PPRemovePat\" commands. Pass \"-l\" option to avoid\r\n  modification.\r\n- To view the list of directories in your 'cdpath', use the regular \"set\r\n  cdpath?\" command or just \"Cdpath\". In addition, the \"Cd\" command accepts\r\n  \"-i\" option to cd directly into one of the directories in 'cdpath'. With\r\n  no arguments, you will be prompted with the list of directories to\r\n  select from, and with an index as the argument (starting from 0), you\r\n  can directly cd into the directory at that index.\r\n- If g:pushpopCdable_vars is set, the plugin emulates the bash\r\n  'cdable_vars' feature. When the built-in \":cd\" fails, the argument is\r\n  assumed to be the name of a global variable whose value is the directory\r\n  to change to. Normally, you don't necessarily need to use the :Cd\r\n  command instead of :cd command, but in this particular case, the feature\r\n  will not work unless you use the :Cd command. Consider aliasing :cd to\r\n  :Cd as described in Deprecations section below.\r\n- The main functions are also exposed as global functions, which can be used\r\n  by the script writers to recursively traverse directories and finally\r\n  return back to the original directory.\r\n\r\nPlease see the script header for more information such as deprecations etc.\r\n\r\nPlease send in your comments\/feedback\/suggestions\/contributions for improving the script.\r\n\r\n=================================================\r\nYou can refer to the bash manual page for more information on how to use Pushd, Popd and Dirs commands. In case you don't have access to it, here is an extract from bash man page (on cygwin):\r\n\r\n       pushd [-n] [dir]\r\n       pushd [-n] [+n] [-n]\r\n              Adds a directory to the top of the directory stack,\r\n              or  rotates  the  stack,  making the new top of the\r\n              stack the current working directory.  With no argu-\r\n              ments,   exchanges  the  top  two  directories  and\r\n              returns 0, unless the  directory  stack  is  empty.\r\n              Arguments,  if  supplied,  have the following mean-\r\n              ings:\r\n              +n     Rotates the stack so that the nth  directory\r\n                     (counting from the left of the list shown by\r\n                     dirs, starting with zero) is at the top.\r\n              -n     Rotates the stack so that the nth  directory\r\n                     (counting  from  the right of the list shown\r\n                     by dirs, starting with zero) is at the  top.\r\n              -n     Suppresses  the  normal  change of directory\r\n                     when adding directories  to  the  stack,  so\r\n                     that only the stack is manipulated.\r\n              dir    Adds  dir to the directory stack at the top,\r\n                     making it the new current working directory.\r\n\r\n              If  the pushd command is successful, a dirs is per-\r\n              formed as well.  If the first form is  used,  pushd\r\n              returns  0  unless  the  cd to dir fails.  With the\r\n              second form, pushd returns 0 unless  the  directory\r\n       popd [-n] [+n] [-n]\r\n              Removes  entries from the directory stack.  With no\r\n              arguments,  removes  the  top  directory  from  the\r\n              stack,  and performs a cd to the new top directory.\r\n              Arguments, if supplied, have  the  following  mean-\r\n              ings:\r\n              +n     Removes the nth entry counting from the left\r\n                     of the list shown  by  dirs,  starting  with\r\n                     zero.   For example: ``popd +0'' removes the\r\n                     first directory, ``popd +1'' the second.\r\n              -n     Removes the  nth  entry  counting  from  the\r\n                     right  of  the  list shown by dirs, starting\r\n                     with zero.  For example: ``popd -0'' removes\r\n                     the  last directory, ``popd -1'' the next to\r\n                     last.\r\n              -n     Suppresses the normal  change  of  directory\r\n                     when removing directories from the stack, so\r\n                     that only the stack is manipulated.\r\n\r\n              If the popd command is successful, a dirs  is  per-\r\n              formed  as  well, and the return status is 0.  popd\r\n              returns false if an invalid option is  encountered,\r\n              the directory stack is empty, a non-existent direc-\r\n              stack is empty, a non-existent directory stack ele-\r\n              ment is specified, or the directory change  to  the\r\n              specified new current directory fails.\r\n              tory stack entry is  specified,  or  the  directory\r\n              change fails.\r\n       dirs [-clpv] [+n] [-n]\r\n              Without  options,  displays  the  list of currently\r\n              remembered directories.  The default display is  on\r\n              a  single  line  with  directory names separated by\r\n              spaces.  Directories are added to the list with the\r\n              pushd  command;  the  popd  command removes entries\r\n              from the list.\r\n              +n     Displays the nth  entry  counting  from  the\r\n                     left  of the list shown by dirs when invoked\r\n                     without options, starting with zero.\r\n              -n     Displays the nth  entry  counting  from  the\r\n                     right of the list shown by dirs when invoked\r\n                     without options, starting with zero.\r\n              -c     Clears the directory stack by  deleting  all\r\n                     of the entries.\r\n              -l     Produces a longer listing; the default list-\r\n                     ing format uses a tilde to denote  the  home\r\n                     directory.\r\n              -p     Print the directory stack with one entry per\r\n                     line.\r\n              -v     Print the directory stack with one entry per\r\n                     line, prefixing each entry with its index in\r\n                     the stack.\r\n\r\n              The return value is 0 unless an invalid  option  is\r\n              supplied  or n indexes beyond the end of the direc-\r\n              tory stack.\r\n=================================================\r\n\r\nSearch_key_words: push pop directory cd change bash csh dirs pushpop genutils Hari Krishna Dara","install_details":"Just drop it in your plugin directory. \r\n\r\nRequires:\r\ngenutils.vim (2.0): vimscript #197 \r\nDepends on (Not required):\r\ncmdalias.vim (1.0): vimscript #745\r\n\r\nPlease note that prior to 4.0 version, the plugin depended on the older versions of genutils and multvals\r\ngenutils.vim (1.1): vimscript #197 \r\nmultvals.vim (3.0): vimscript #171\r\n","5":"Just drop it in your plugin directory. \r\n\r\nRequires:\r\ngenutils.vim (2.0): vimscript #197 \r\nDepends on (Not required):\r\ncmdalias.vim (1.0): vimscript #745\r\n\r\nPlease note that prior to 4.0 version, the plugin depended on the older versions of genutils and multvals\r\ngenutils.vim (1.1): vimscript #197 \r\nmultvals.vim (3.0): vimscript #171\r\n","first_name":"Hari Krishna","6":"Hari Krishna","last_name":"Dara","7":"Dara","releases":[{"0":"129","vim_version":"7.0","1":"7.0","script_version":"4.0","2":"4.0","version_comment":"Made to work with Vim7. Also, it uses the Vim7 Lists instead of\r\nmultvals, so it no longer depends on multvals and it is a lot cleaner.\r\n","3":"Made to work with Vim7. Also, it uses the Vim7 Lists instead of\r\nmultvals, so it no longer depends on multvals and it is a lot cleaner.\r\n","package":"PushPop.vim","4":"PushPop.vim","src_id":"6710","5":"6710","creation_date":"1170424281","6":"1170424281"},{"0":"129","vim_version":"6.0","1":"6.0","script_version":"2.4","2":"2.4","version_comment":"- Refined the handling of 'cdpath'. It works better now.\r\n- Subtle improvements in the Pushd\/Popd command usage.\r\n- Delayed syncing is used to sync the top level directory in the stack with the current directory. You don't have to use the custom Cd command anymore, which means one less abbreviation to deal with. This also means that it will work seamlessly with other plugins that change directory as well (like fileexplorer).\r\n- The script now takes advantage of cmdalias.vim when available for creating aliases to the capitalized commands. This is better than the plain cabbr's.\r\n- There is a new 'cdable_vars' feature on the lines of bash.\r\n- Fixed some misc. minor issues.\r\n\r\nPlease read the complete header in the script for changes and new usage.","3":"- Refined the handling of 'cdpath'. It works better now.\r\n- Subtle improvements in the Pushd\/Popd command usage.\r\n- Delayed syncing is used to sync the top level directory in the stack with the current directory. You don't have to use the custom Cd command anymore, which means one less abbreviation to deal with. This also means that it will work seamlessly with other plugins that change directory as well (like fileexplorer).\r\n- The script now takes advantage of cmdalias.vim when available for creating aliases to the capitalized commands. This is better than the plain cabbr's.\r\n- There is a new 'cdable_vars' feature on the lines of bash.\r\n- Fixed some misc. minor issues.\r\n\r\nPlease read the complete header in the script for changes and new usage.","package":"PushPop.vim","4":"PushPop.vim","src_id":"2277","5":"2277","creation_date":"1062095501","6":"1062095501"},{"0":"129","vim_version":"6.0","1":"6.0","script_version":"2.3","2":"2.3","version_comment":"- Fixed bugs. \r\n- Respect protected commas in cdpath and directory names. \r\n- Minor improvements: Pushd also now takes -i argument. AddDir and RemoveDir take -l argument. Use g:pushpopPersistCdpath to control the persistnce of cdpath.\r\n- Requires the new version of multvals.vim\r\n","3":"- Fixed bugs. \r\n- Respect protected commas in cdpath and directory names. \r\n- Minor improvements: Pushd also now takes -i argument. AddDir and RemoveDir take -l argument. Use g:pushpopPersistCdpath to control the persistnce of cdpath.\r\n- Requires the new version of multvals.vim\r\n","package":"PushPop.vim","4":"PushPop.vim","src_id":"1583","5":"1583","creation_date":"1040921311","6":"1040921311"},{"0":"129","vim_version":"6.0","1":"6.0","script_version":"2.2","2":"2.2","version_comment":"I missed to do an integration, so ended up with a wrong file here. I apologize, please update your version with this.","3":"I missed to do an integration, so ended up with a wrong file here. I apologize, please update your version with this.","package":"PushPop.vim","4":"PushPop.vim","src_id":"1126","5":"1126","creation_date":"1029349366","6":"1029349366"},{"0":"129","vim_version":"6.0","1":"6.0","script_version":"2.1","2":"2.1","version_comment":"I have totally redesigned it to work seamlessly with vim's cd and cdpath features. You can now pushd into a diretory that is in the cdpath. Also added new commands to manage the cdpath itself, without needing to change the .vimrc. Removed unnecessary command-line abbreviations. Removed Cdp command as it is a duplicate of \"cd -\" command and renamed Cdc command as Cdp. The script now requires genutils.vim for storing and retrieving cdpath.","3":"I have totally redesigned it to work seamlessly with vim's cd and cdpath features. You can now pushd into a diretory that is in the cdpath. Also added new commands to manage the cdpath itself, without needing to change the .vimrc. Removed unnecessary command-line abbreviations. Removed Cdp command as it is a duplicate of \"cd -\" command and renamed Cdc command as Cdp. The script now requires genutils.vim for storing and retrieving cdpath.","package":"PushPop.vim","4":"PushPop.vim","src_id":"1122","5":"1122","creation_date":"1029283325","6":"1029283325"},{"0":"129","vim_version":"6.0","1":"6.0","script_version":"2.0.5","2":"2.0.5","version_comment":"Fixed pushd with no-arg to switch between the top two dirs, instead of rotating (like with an index). Fixed cd to not to do a dirs. Added new commands cdp to quickly go back to the previous directory and cdc to pushd in to the directory of the currently open file.","3":"Fixed pushd with no-arg to switch between the top two dirs, instead of rotating (like with an index). Fixed cd to not to do a dirs. Added new commands cdp to quickly go back to the previous directory and cdc to pushd in to the directory of the currently open file.","package":"PushPop.vim","4":"PushPop.vim","src_id":"699","5":"699","creation_date":"1016578456","6":"1016578456"},{"0":"129","vim_version":"6.0","1":"6.0","script_version":"2.0.2","2":"2.0.2","version_comment":"I finally made the script complete and plugin compatible. It now supports most of the bash pushd\/popd syntax and is very compliant with it in the functionality and messages. Give it a shot, I am sure you will like it.\r\n\r\nIt also provided an commandline abbreviation for cd command to adjust the top most directory. You can set the global variable pushpopNoAbbrev to disable the commandline abbreviations such as cd, dirs, pushd etc., if they interfere with your regular usage.","3":"I finally made the script complete and plugin compatible. It now supports most of the bash pushd\/popd syntax and is very compliant with it in the functionality and messages. Give it a shot, I am sure you will like it.\r\n\r\nIt also provided an commandline abbreviation for cd command to adjust the top most directory. You can set the global variable pushpopNoAbbrev to disable the commandline abbreviations such as cd, dirs, pushd etc., if they interfere with your regular usage.","package":"PushPop.vim","4":"PushPop.vim","src_id":"576","5":"576","creation_date":"1013379540","6":"1013379540"},{"0":"129","vim_version":"5.7","1":"5.7","script_version":"1.0beta5","2":"1.0beta5","version_comment":"Initial upload","3":"Initial upload","package":"PushPop.vim","4":"PushPop.vim","src_id":"298","5":"298","creation_date":"1003775045","6":"1003775045"}]},"128":{"script_id":"128","0":"128","script_name":"random_vim_tip.tar.gz","1":"random_vim_tip.tar.gz","script_type":"utility","2":"utility","summary":"Python script - not vim - displays random vim command or tip.","3":"Python script - not vim - displays random vim command or tip.","description":"Displays random vim command (with explanation) or tip, then starts vim. Can be set to show tip once per X launches. ","4":"Displays random vim command (with explanation) or tip, then starts vim. Can be set to show tip once per X launches. ","install_details":"Read the README.","5":"Read the README.","first_name":"A","6":"A","last_name":"K","7":"K","releases":[{"0":"128","vim_version":"6.0","1":"6.0","script_version":"","2":"","version_comment":"Initial upload","3":"Initial upload","package":"random_vim_tip.tar.gz","4":"random_vim_tip.tar.gz","src_id":"296","5":"296","creation_date":"1003679543","6":"1003679543"}]},"127":{"script_id":"127","0":"127","script_name":"runscript.vim","1":"runscript.vim","script_type":"utility","2":"utility","summary":"Plugin for running Python scripts.","3":"Plugin for running Python scripts.","description":"Vim global plugin for running Python scripts\r\nVersion: 1.1\r\nMaintainer: Frederick Young <lordfyb@hotmail.com>\r\nLast change: 2001 Oct 30 \r\n--Pressing the \"F12\" key will run the Python script in the current buffer\r\n \r\n--Pressing the \"F11\" key will designate the Python script in the current\r\n  buffer as the script to run when pressing F12\"\r\n   \r\n--Pressing \"Shift-F11\" will remove the designation performed by pressing \"F11\"\r\n  and will allow pressing \"F12\" to run the script in the current buffer\r\n   \r\n--Typing the Ex command \"Rs\" will also allow you to run a Python script but\r\n  with the benefit of allowing you to pass up to 20 parameters to the script.\r\n   \r\n   Sample syntax...\r\n\r\n   \t:rs -xy 800 600\r\n\r\n  The above will run the script in the current buffer or the one designated\r\n  to run when pressing \"F11\" and pass to it the parameters \"-xy 800 600\"\r\n\r\n--Pressing \"F9\" will toggle the display of a buffer containing the output\r\n  produced when running the Ex command \"Rs\" or pressing \"F12\".\r\n\r\nAlso, the value of the variable s:PathToExecutable in the script may need to be changed to reflect the location of Python on your system.\r\n\r\n  With some minor modifications, it should be possible to run other scripts\r\n  like perl, vbscript, or even executables compiled with the Ex command\r\n  \"make\".","4":"Vim global plugin for running Python scripts\r\nVersion: 1.1\r\nMaintainer: Frederick Young <lordfyb@hotmail.com>\r\nLast change: 2001 Oct 30 \r\n--Pressing the \"F12\" key will run the Python script in the current buffer\r\n \r\n--Pressing the \"F11\" key will designate the Python script in the current\r\n  buffer as the script to run when pressing F12\"\r\n   \r\n--Pressing \"Shift-F11\" will remove the designation performed by pressing \"F11\"\r\n  and will allow pressing \"F12\" to run the script in the current buffer\r\n   \r\n--Typing the Ex command \"Rs\" will also allow you to run a Python script but\r\n  with the benefit of allowing you to pass up to 20 parameters to the script.\r\n   \r\n   Sample syntax...\r\n\r\n   \t:rs -xy 800 600\r\n\r\n  The above will run the script in the current buffer or the one designated\r\n  to run when pressing \"F11\" and pass to it the parameters \"-xy 800 600\"\r\n\r\n--Pressing \"F9\" will toggle the display of a buffer containing the output\r\n  produced when running the Ex command \"Rs\" or pressing \"F12\".\r\n\r\nAlso, the value of the variable s:PathToExecutable in the script may need to be changed to reflect the location of Python on your system.\r\n\r\n  With some minor modifications, it should be possible to run other scripts\r\n  like perl, vbscript, or even executables compiled with the Ex command\r\n  \"make\".","install_details":"Just copy into the plugin folder","5":"Just copy into the plugin folder","first_name":"Frederick","6":"Frederick","last_name":"Young","7":"Young","releases":[{"0":"127","vim_version":"6.0","1":"6.0","script_version":"1.1","2":"1.1","version_comment":"New in this release...\r\nNew in this release...\r\n*   The function key \"F9\" is now used as a toggle for the output window.\r\n    Because of this, the Ex command \"Sb\" has been removed\r\n\r\n*   Minor bug fixes","3":"New in this release...\r\nNew in this release...\r\n*   The function key \"F9\" is now used as a toggle for the output window.\r\n    Because of this, the Ex command \"Sb\" has been removed\r\n\r\n*   Minor bug fixes","package":"runscript.vim","4":"runscript.vim","src_id":"310","5":"310","creation_date":"1004591326","6":"1004591326"},{"0":"127","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"runscript.vim","4":"runscript.vim","src_id":"295","5":"295","creation_date":"1003645453","6":"1003645453"}]},"126":{"script_id":"126","0":"126","script_name":"ctx-1.15.vim","1":"ctx-1.15.vim","script_type":"utility","2":"utility","summary":"Describes your cursor\\'s current scope or context when editing a C file.","3":"Describes your cursor\\'s current scope or context when editing a C file.","description":"CTX is an attempt to help Vim users navigate in C\r\nprogram files with very large function definitions. Such\r\nfiles should generally not exist, but alas they do, and\r\nsometimes we need to make changes to them.\r\n\r\nThis script helps by opening a small window in your Vim\r\nsession and keeping up-to-date with a few lines of text\r\ndescribing your cursor\\'s current scope or context in a C\r\nfile.\r\n\r\nhttp:\/\/www.bluweb.com\/us\/chouser\/proj\/ctx\/\r\n","4":"CTX is an attempt to help Vim users navigate in C\r\nprogram files with very large function definitions. Such\r\nfiles should generally not exist, but alas they do, and\r\nsometimes we need to make changes to them.\r\n\r\nThis script helps by opening a small window in your Vim\r\nsession and keeping up-to-date with a few lines of text\r\ndescribing your cursor\\'s current scope or context in a C\r\nfile.\r\n\r\nhttp:\/\/www.bluweb.com\/us\/chouser\/proj\/ctx\/\r\n","install_details":"To use, source the ctx.vim file in your ~\/.vimrc.  You may also \r\nwant to reduce your updatetime to 1000 or so.\r\n","5":"To use, source the ctx.vim file in your ~\/.vimrc.  You may also \r\nwant to reduce your updatetime to 1000 or so.\r\n","first_name":"Chris","6":"Chris","last_name":"Houser","7":"Houser","releases":[{"0":"126","vim_version":"6.0","1":"6.0","script_version":"1.15","2":"1.15","version_comment":"Initial upload","3":"Initial upload","package":"ctx-1.15.vim","4":"ctx-1.15.vim","src_id":"290","5":"290","creation_date":"1003496500","6":"1003496500"}]},"125":{"script_id":"125","0":"125","script_name":"selbuff.vim","1":"selbuff.vim","script_type":"utility","2":"utility","summary":"Another buffer select script","3":"Another buffer select script","description":"selbuff.vim is an easy way to select a buffer, very similar to bufexplorer.  It works by creating a window (n < (&lines\/2) ? n : (&lines\/2)) lines high listing all buffers (except the selection temp buffer) at the bottom of the vim frame.  Moving the cursor to a line and pressing <CR> shows the selected buffer in the window you were in when you pressed <Leader>bl. Moving the cursor to a line and pressing 'd' delete's the buffer.  Moving the cursor to a line and pressing 'w' will write the file.  Pressing 'q' within the select buffer window closes the window.","4":"selbuff.vim is an easy way to select a buffer, very similar to bufexplorer.  It works by creating a window (n < (&lines\/2) ? n : (&lines\/2)) lines high listing all buffers (except the selection temp buffer) at the bottom of the vim frame.  Moving the cursor to a line and pressing <CR> shows the selected buffer in the window you were in when you pressed <Leader>bl. Moving the cursor to a line and pressing 'd' delete's the buffer.  Moving the cursor to a line and pressing 'w' will write the file.  Pressing 'q' within the select buffer window closes the window.","install_details":"Just put the script in your plugin directory.  Read the script for usage information.","5":"Just put the script in your plugin directory.  Read the script for usage information.","first_name":"Todd","6":"Todd","last_name":"Cosgrove","7":"Cosgrove","releases":[{"0":"125","vim_version":"6.0","1":"6.0","script_version":"1.6","2":"1.6","version_comment":"Fixed the 'w' functionality that I broke when making changes for vim60.\r\n","3":"Fixed the 'w' functionality that I broke when making changes for vim60.\r\n","package":"selbuff.vim","4":"selbuff.vim","src_id":"297","5":"297","creation_date":"1003730730","6":"1003730730"},{"0":"125","vim_version":"6.0","1":"6.0","script_version":"1.5","2":"1.5","version_comment":"Initial upload","3":"Initial upload","package":"selbuff.vim","4":"selbuff.vim","src_id":"286","5":"286","creation_date":"1003411876","6":"1003411876"}]},"124":{"script_id":"124","0":"124","script_name":"quickhigh.tgz","1":"quickhigh.tgz","script_type":"utility","2":"utility","summary":"Highlight quickfix erros","3":"Highlight quickfix erros","description":"This is a plugin for highlighting quickfix errors.\n\nIt provides mappings for manualy adding the highlights and commands to automatically add the highlights.\nIt has the ability to work with both the :make and :grep commands.\nIt also has the ability to distinguish between warning and error compiler messages.  \n\nPlease see the documenation for configuration (help quickhigh.txt after installation).","4":"This is a plugin for highlighting quickfix errors.\n\nIt provides mappings for manualy adding the highlights and commands to automatically add the highlights.\nIt has the ability to work with both the :make and :grep commands.\nIt also has the ability to distinguish between warning and error compiler messages.  \n\nPlease see the documenation for configuration (help quickhigh.txt after installation).","install_details":"cd ~\/.vim\ngzip -dc ~\/dl\/quickhigh.tgz | tar -xf -\nvim -c \":helptags ~\/.vim\/doc\" -c :q","5":"cd ~\/.vim\ngzip -dc ~\/dl\/quickhigh.tgz | tar -xf -\nvim -c \":helptags ~\/.vim\/doc\" -c :q","first_name":"brian","6":"brian","last_name":"medley","7":"medley","releases":[{"0":"124","vim_version":"6.0","1":"6.0","script_version":"1.15","2":"1.15","version_comment":"Fixup for when there is col information in the line output.","3":"Fixup for when there is col information in the line output.","package":"quickhigh.tgz","4":"quickhigh.tgz","src_id":"440","5":"440","creation_date":"1009906851","6":"1009906851"},{"0":"124","vim_version":"6.0","1":"6.0","script_version":"1.14","2":"1.14","version_comment":"Modify to work better if ':' is part of a filename.\nUpdate to perl embedded file layout suggested by Benoit.\n","3":"Modify to work better if ':' is part of a filename.\nUpdate to perl embedded file layout suggested by Benoit.\n","package":"quickhigh.tgz","4":"quickhigh.tgz","src_id":"337","5":"337","creation_date":"1005487884","6":"1005487884"},{"0":"124","vim_version":"6.0","1":"6.0","script_version":"1.12","2":"1.12","version_comment":"let users define their own signs\nadded perl code for speed\nmore error checking\nmisc bugs fixed","3":"let users define their own signs\nadded perl code for speed\nmore error checking\nmisc bugs fixed","package":"quickhigh.tgz","4":"quickhigh.tgz","src_id":"308","5":"308","creation_date":"1004192667","6":"1004192667"}]},"123":{"script_id":"123","0":"123","script_name":"sum.vim","1":"sum.vim","script_type":"utility","2":"utility","summary":"sum the values of a range of rows","3":"sum the values of a range of rows","description":"A little script that sum some values of a range of rows. That's all :)\r\nSum.vim use the powerfull bc utility (you must install it!).\r\nThe script work also with older version of vim... i tested it also under win32 and it work (of course you must install the porting of bc)","4":"A little script that sum some values of a range of rows. That's all :)\r\nSum.vim use the powerfull bc utility (you must install it!).\r\nThe script work also with older version of vim... i tested it also under win32 and it work (of course you must install the porting of bc)","install_details":"just put sum.vim in the plugin directory :)","5":"just put sum.vim in the plugin directory :)","first_name":"Vanni","6":"Vanni","last_name":"Brutto","7":"Brutto","releases":[{"0":"123","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"sum.vim","4":"sum.vim","src_id":"279","5":"279","creation_date":"1003232483","6":"1003232483"}]},"122":{"script_id":"122","0":"122","script_name":"Astronaut","1":"Astronaut","script_type":"color scheme","2":"color scheme","summary":"withdrawn","3":"withdrawn","description":"withdrawn -- the search engine bots got ahold of the \"unsatisfactory\" address and within a day -134 was dumped onto the astronaut colorscheme's karma.  I am now removing any plugins of mine from vim.sf.net that have this problem, as the poor karma ratings deter new downloaders.  You may still go to my website, http:\/\/www.drchip.org\/astronaut\/vim\/index.html#ASTRONAUT to get a copy.\r\n","4":"withdrawn -- the search engine bots got ahold of the \"unsatisfactory\" address and within a day -134 was dumped onto the astronaut colorscheme's karma.  I am now removing any plugins of mine from vim.sf.net that have this problem, as the poor karma ratings deter new downloaders.  You may still go to my website, http:\/\/www.drchip.org\/astronaut\/vim\/index.html#ASTRONAUT to get a copy.\r\n","install_details":"go to http:\/\/drchip.0sites.net\/astronaut\/vim\/index.html#ASTRONAUT","5":"go to http:\/\/drchip.0sites.net\/astronaut\/vim\/index.html#ASTRONAUT","first_name":"Charles","6":"Charles","last_name":"Campbell","7":"Campbell","releases":[{"0":"122","vim_version":"7.0","1":"7.0","script_version":"W","2":"W","version_comment":"withdrawn due to search bot problem","3":"withdrawn due to search bot problem","package":"withdrawn.vim","4":"withdrawn.vim","src_id":"16752","5":"16752","creation_date":"1319727026","6":"1319727026"}]},"121":{"script_id":"121","0":"121","script_name":"asu1dark.vim","1":"asu1dark.vim","script_type":"color scheme","2":"color scheme","summary":"Color scheme with dark background.","3":"Color scheme with dark background.","description":"My favorite dark color scheme. Very colorful :) Tried only in Win32 gvim, and DOS vim.","4":"My favorite dark color scheme. Very colorful :) Tried only in Win32 gvim, and DOS vim.","install_details":"Put the file in your ~\/vimfiles\/colors directory and use colorscheme asu1dark in your .vimrc to activate the color scheme.","5":"Put the file in your ~\/vimfiles\/colors directory and use colorscheme asu1dark in your .vimrc to activate the color scheme.","first_name":"A. Sinan","6":"A. Sinan","last_name":"Unur","7":"Unur","releases":[{"0":"121","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"asu1dark.vim","4":"asu1dark.vim","src_id":"271","5":"271","creation_date":"1003124955","6":"1003124955"}]},"120":{"script_id":"120","0":"120","script_name":"Decho","1":"Decho","script_type":"utility","2":"utility","summary":"Vim script internal debugger (output in separate window, tab, or remote vim)","3":"Vim script internal debugger (output in separate window, tab, or remote vim)","description":"The Decho.vim plugin provides debugging messages in a separate window.  One puts\r\n\r\n    Decho \"some message here\"\r\n-or-\r\n    call Decho(\"another message\")\r\n\r\nand Decho will split the screen with a five line debugging window on the bottom of the display where the messages will appear.  Allows one to inspect multiple error messages with the usual vim editing commands!\r\n\r\nTo better support the debugging of scripts, Decho.vim also provides:\r\n\r\n    call Dfunc(\"YourFunctionName([arg1<\".a:arg1.\"> arg2<\".a:arg2.\">])\")\r\n    call Dret(\"YourFunctionName [returnvalue]\")\r\n\r\nThese two functions use Decho(), but also provide function tracking.  The .vim\/syntax\/Decho.vim provides special highlighting for the DBG buffer, too.  See the example below!\r\n\r\nOne may redirect the output of arbitrary vim commands to the DBG buffer with the following function:\r\n\r\n    call Dredir(\"command\")\r\n\r\nFor example, consider\r\n\r\n\tcall Dredir(\"ls\")\r\n\r\nDecho.vim makes it easy to turn debugging on and off in your scripts:\r\n\r\n    Turning Debugging On:\r\n        vim yourscript.vim\r\n        :DechoOn\r\n        :wq\r\n\r\n    Turning Debugging Off:\r\n        vim yourscript.vim\r\n        :DechoOff\r\n        :wq\r\n\r\nSome plugins use events such as WinEnter and others attempt to control window layout.  Decho supports these plugins with four methods to avoid disturbing the display:\r\n\r\n\tDechoMsgOn  -- subsequent debugging output uses :echomsg\r\n\tDechoRemOn  -- subsequent debugging output goes to a remote gvim which DechoRemOn will set up itself\r\n        DechoTabOn  -- subsequent debugging output goes to a separate debugging tab\/window\r\n\tDechoVarOn  -- subsequent debugging output goes to a variable (default value: g:dechovar)\r\n\r\nWith any of these enabled, subsequent Dfunc, Dret, Decho, and Dredir output will be directed as indicated.\r\n\r\n ---------------------------------------------------------------------\r\nExample:\r\n\r\n    LocalBrowse(dirname<.>) {\r\n    |NetGetcwd() {\r\n    ||return NetGetcwd \/home\/cec\/.vim\/VIMSCRIPT\/ }\r\n    |dirname<\/home>\r\n    |Perform directory listing...\r\n    |bufnr(dirname<\/home>)=1\r\n    |dirnamenr=1 dirname<\/home> pre-exists\r\n    |changed directory to<\/home>\r\n    |buffer already exists, but needs listing (buf#1)\r\n    |Setting up local browser maps\r\n    |NetGetcwd() {\r\n    ||return NetGetcwd \/home\/cec\/.vim\/VIMSCRIPT\/ }\r\n    |NetGetcwd() {\r\n    ||return NetGetcwd \/home\/cec\/.vim\/VIMSCRIPT\/ }\r\n    |NetGetcwd() {\r\n    ||return NetGetcwd \/home\/cec\/.vim\/VIMSCRIPT\/ }\r\n    |NetGetcwd() {\r\n    ||return NetGetcwd \/home\/cec\/.vim\/VIMSCRIPT\/ }\r\n    |NetGetcwd() {\r\n    ||return NetGetcwd \/home\/cec\/.vim\/VIMSCRIPT\/ }\r\n    |NetGetcwd() {\r\n    ||return NetGetcwd \/home\/cec\/.vim\/VIMSCRIPT\/ }\r\n    |set up banner\r\n    |directories will be sorted by name\r\n    |LocalBrowseList(dirname<\/home>) {\r\n    |(elided for brevity)\r\n    ||return LocalBrowseList }\r\n    |SetSort() bannercnt=8 {\r\n    |(elided for brevity)\r\n    ||return SetSort }\r\n    |NetSort() {\r\n    ||return NetSort }\r\n    |return LocalBrowse : file<\/home> }\r\n\r\n(alpha\/beta version available at http:\/\/mysite.verizon.net\/astronaut\/vim\/index.html#DECHO)","4":"The Decho.vim plugin provides debugging messages in a separate window.  One puts\r\n\r\n    Decho \"some message here\"\r\n-or-\r\n    call Decho(\"another message\")\r\n\r\nand Decho will split the screen with a five line debugging window on the bottom of the display where the messages will appear.  Allows one to inspect multiple error messages with the usual vim editing commands!\r\n\r\nTo better support the debugging of scripts, Decho.vim also provides:\r\n\r\n    call Dfunc(\"YourFunctionName([arg1<\".a:arg1.\"> arg2<\".a:arg2.\">])\")\r\n    call Dret(\"YourFunctionName [returnvalue]\")\r\n\r\nThese two functions use Decho(), but also provide function tracking.  The .vim\/syntax\/Decho.vim provides special highlighting for the DBG buffer, too.  See the example below!\r\n\r\nOne may redirect the output of arbitrary vim commands to the DBG buffer with the following function:\r\n\r\n    call Dredir(\"command\")\r\n\r\nFor example, consider\r\n\r\n\tcall Dredir(\"ls\")\r\n\r\nDecho.vim makes it easy to turn debugging on and off in your scripts:\r\n\r\n    Turning Debugging On:\r\n        vim yourscript.vim\r\n        :DechoOn\r\n        :wq\r\n\r\n    Turning Debugging Off:\r\n        vim yourscript.vim\r\n        :DechoOff\r\n        :wq\r\n\r\nSome plugins use events such as WinEnter and others attempt to control window layout.  Decho supports these plugins with four methods to avoid disturbing the display:\r\n\r\n\tDechoMsgOn  -- subsequent debugging output uses :echomsg\r\n\tDechoRemOn  -- subsequent debugging output goes to a remote gvim which DechoRemOn will set up itself\r\n        DechoTabOn  -- subsequent debugging output goes to a separate debugging tab\/window\r\n\tDechoVarOn  -- subsequent debugging output goes to a variable (default value: g:dechovar)\r\n\r\nWith any of these enabled, subsequent Dfunc, Dret, Decho, and Dredir output will be directed as indicated.\r\n\r\n ---------------------------------------------------------------------\r\nExample:\r\n\r\n    LocalBrowse(dirname<.>) {\r\n    |NetGetcwd() {\r\n    ||return NetGetcwd \/home\/cec\/.vim\/VIMSCRIPT\/ }\r\n    |dirname<\/home>\r\n    |Perform directory listing...\r\n    |bufnr(dirname<\/home>)=1\r\n    |dirnamenr=1 dirname<\/home> pre-exists\r\n    |changed directory to<\/home>\r\n    |buffer already exists, but needs listing (buf#1)\r\n    |Setting up local browser maps\r\n    |NetGetcwd() {\r\n    ||return NetGetcwd \/home\/cec\/.vim\/VIMSCRIPT\/ }\r\n    |NetGetcwd() {\r\n    ||return NetGetcwd \/home\/cec\/.vim\/VIMSCRIPT\/ }\r\n    |NetGetcwd() {\r\n    ||return NetGetcwd \/home\/cec\/.vim\/VIMSCRIPT\/ }\r\n    |NetGetcwd() {\r\n    ||return NetGetcwd \/home\/cec\/.vim\/VIMSCRIPT\/ }\r\n    |NetGetcwd() {\r\n    ||return NetGetcwd \/home\/cec\/.vim\/VIMSCRIPT\/ }\r\n    |NetGetcwd() {\r\n    ||return NetGetcwd \/home\/cec\/.vim\/VIMSCRIPT\/ }\r\n    |set up banner\r\n    |directories will be sorted by name\r\n    |LocalBrowseList(dirname<\/home>) {\r\n    |(elided for brevity)\r\n    ||return LocalBrowseList }\r\n    |SetSort() bannercnt=8 {\r\n    |(elided for brevity)\r\n    ||return SetSort }\r\n    |NetSort() {\r\n    ||return NetSort }\r\n    |return LocalBrowse : file<\/home> }\r\n\r\n(alpha\/beta version available at http:\/\/mysite.verizon.net\/astronaut\/vim\/index.html#DECHO)","install_details":"1. vim Decho.vba.gz\r\n    :so %\r\n    :q\r\n\r\n2. This will create the following files:\r\n  plugin\/Decho.vim\r\n  plugin\/cecutil.vim\r\n  syntax\/Decho.vim\r\n  doc\/Decho.txt\r\n\r\n(you may want the latest vimball handling script for this: vimscript#1502)","5":"1. vim Decho.vba.gz\r\n    :so %\r\n    :q\r\n\r\n2. This will create the following files:\r\n  plugin\/Decho.vim\r\n  plugin\/cecutil.vim\r\n  syntax\/Decho.vim\r\n  doc\/Decho.txt\r\n\r\n(you may want the latest vimball handling script for this: vimscript#1502)","first_name":"Charles","6":"Charles","last_name":"Campbell","7":"Campbell","releases":[{"0":"120","vim_version":"7.0","1":"7.0","script_version":"20","2":"20","version_comment":"* DechoSep() can now be externally called (and :Dsep  makes it easy to use).  Creates an easy-to-find separator in the debugging output.\r\n* bug fixes (Cyan, Magenta highlighting; improved DechoTab's tab search, unwanted DechoRemOn staircasing)\r\n","3":"* DechoSep() can now be externally called (and :Dsep  makes it easy to use).  Creates an easy-to-find separator in the debugging output.\r\n* bug fixes (Cyan, Magenta highlighting; improved DechoTab's tab search, unwanted DechoRemOn staircasing)\r\n","package":"Decho.vba.gz","4":"Decho.vba.gz","src_id":"9388","5":"9388","creation_date":"1224776334","6":"1224776334"},{"0":"120","vim_version":"7.0","1":"7.0","script_version":"19","2":"19","version_comment":"Various bugfixes and improvements...\r\nDredir now takes optional strings first instead of last.\r\nThe :Decho and :Dredir commands now take <args> instead of <q-args>, which allows them to act more like the function calls do.\r\nDechoRemOn's remote vim no longer will have formatoptions' a or t suboptions set even if the user has specified something like fo+=at in his\/her .vimrc.\r\nIf the user interposes a new tab (or deletes the \"Decho Tab\"), Decho finds the \"Decho Tab\" tab or creates a new one when called.\r\n","3":"Various bugfixes and improvements...\r\nDredir now takes optional strings first instead of last.\r\nThe :Decho and :Dredir commands now take <args> instead of <q-args>, which allows them to act more like the function calls do.\r\nDechoRemOn's remote vim no longer will have formatoptions' a or t suboptions set even if the user has specified something like fo+=at in his\/her .vimrc.\r\nIf the user interposes a new tab (or deletes the \"Decho Tab\"), Decho finds the \"Decho Tab\" tab or creates a new one when called.\r\n","package":"Decho.vba.gz","4":"Decho.vba.gz","src_id":"7092","5":"7092","creation_date":"1178802324","6":"1178802324"},{"0":"120","vim_version":"7.0","1":"7.0","script_version":"18","2":"18","version_comment":"Decho now handles list arguments, works around ignorecase setting, and no longer uses bt=nofile (makes it easier to save).","3":"Decho now handles list arguments, works around ignorecase setting, and no longer uses bt=nofile (makes it easier to save).","package":"Decho.vba.gz","4":"Decho.vba.gz","src_id":"6144","5":"6144","creation_date":"1157458692","6":"1157458692"},{"0":"120","vim_version":"6.0","1":"6.0","script_version":"17","2":"17","version_comment":"The \"Decho Tab\" buffer now is syntax highlighted, plus bugfixes.\r\n","3":"The \"Decho Tab\" buffer now is syntax highlighted, plus bugfixes.\r\n","package":"Decho.tar.gz","4":"Decho.tar.gz","src_id":"5374","5":"5374","creation_date":"1141646344","6":"1141646344"},{"0":"120","vim_version":"6.0","1":"6.0","script_version":"16","2":"16","version_comment":"For vim 7.0 users: DechoTabOn\/Off changed to reflect changes in vim 7.0's :tab, :tabn, :tabnew commands.  (Decho still works fine for vim 6.0, BTW)","3":"For vim 7.0 users: DechoTabOn\/Off changed to reflect changes in vim 7.0's :tab, :tabn, :tabnew commands.  (Decho still works fine for vim 6.0, BTW)","package":"Decho.tar.gz","4":"Decho.tar.gz","src_id":"5333","5":"5333","creation_date":"1141023253","6":"1141023253"},{"0":"120","vim_version":"6.0","1":"6.0","script_version":"15","2":"15","version_comment":"Decho now supports use of vim7.0aa's \"tab\" feature -- with :DechoTabOn, subsequent debugging output goes to its own tab.","3":"Decho now supports use of vim7.0aa's \"tab\" feature -- with :DechoTabOn, subsequent debugging output goes to its own tab.","package":"Decho.tar.gz","4":"Decho.tar.gz","src_id":"5297","5":"5297","creation_date":"1140530330","6":"1140530330"},{"0":"120","vim_version":"6.0","1":"6.0","script_version":"14","2":"14","version_comment":"Decho has a new pair of commands: DechoRemOn and DechoRemOff.  With these, debugging output can be sent to a remote gvim.  Really helps with debugging plugins that use events and control window layout.\r\n","3":"Decho has a new pair of commands: DechoRemOn and DechoRemOff.  With these, debugging output can be sent to a remote gvim.  Really helps with debugging plugins that use events and control window layout.\r\n","package":"Decho.tar.gz","4":"Decho.tar.gz","src_id":"5225","5":"5225","creation_date":"1139996742","6":"1139996742"},{"0":"120","vim_version":"6.0","1":"6.0","script_version":"12","2":"12","version_comment":"* DechoOn\/Off now also turns on\/off DechoVarOn\/Off\r\n* DechoMsgOn and DechoMsgOff installed; debugging messages will use the |echomsg| command.\r\n* DechoVarOn and DechoVarOff installed; debugging messages will be appended to the variable specified by g:dechovarname, which by default is \"g:dechovar\".  These two commands toggle the variable \"g:dechovar_enabled\".\r\n* Now includes a GetLatestVimScripts line for cecutil.vim\r\n* Decho now does \"runtime plugin\/cecutil.vim\" if that plugin hasn't been loaded yet.  It will also try the AsNeeded subdirectory if g:loaded_asneeded exists.\r\n* with DechoMsgOn, Decho(\"doesn't\") now works\r\n* Dredir() now accepts multiple arguments (cmd and output)\r\n","3":"* DechoOn\/Off now also turns on\/off DechoVarOn\/Off\r\n* DechoMsgOn and DechoMsgOff installed; debugging messages will use the |echomsg| command.\r\n* DechoVarOn and DechoVarOff installed; debugging messages will be appended to the variable specified by g:dechovarname, which by default is \"g:dechovar\".  These two commands toggle the variable \"g:dechovar_enabled\".\r\n* Now includes a GetLatestVimScripts line for cecutil.vim\r\n* Decho now does \"runtime plugin\/cecutil.vim\" if that plugin hasn't been loaded yet.  It will also try the AsNeeded subdirectory if g:loaded_asneeded exists.\r\n* with DechoMsgOn, Decho(\"doesn't\") now works\r\n* Dredir() now accepts multiple arguments (cmd and output)\r\n","package":"Decho.tar.gz","4":"Decho.tar.gz","src_id":"4796","5":"4796","creation_date":"1132647950","6":"1132647950"},{"0":"120","vim_version":"6.0","1":"6.0","script_version":"10","2":"10","version_comment":"* New function: call Dredir(\"command\") will redirect the command's output to the DBG buffer.\r\n* Decho now uses keepjumps to avoid altering the jumplist table (requires vim6.3)\r\n* Decho's appending to the DBG buffer no longer flags it as modified.\r\n* One may have Decho ignore BufEnter events if g:decho_bufenter exists.\r\n","3":"* New function: call Dredir(\"command\") will redirect the command's output to the DBG buffer.\r\n* Decho now uses keepjumps to avoid altering the jumplist table (requires vim6.3)\r\n* Decho's appending to the DBG buffer no longer flags it as modified.\r\n* One may have Decho ignore BufEnter events if g:decho_bufenter exists.\r\n","package":"Decho.tar.bz2","4":"Decho.tar.bz2","src_id":"3297","5":"3297","creation_date":"1091516553","6":"1091516553"},{"0":"120","vim_version":"6.0","1":"6.0","script_version":"8","2":"8","version_comment":"Decho now has :Dhide and :Dshow commands for toggling the visibility of the DBG buffer\r\n","3":"Decho now has :Dhide and :Dshow commands for toggling the visibility of the DBG buffer\r\n","package":"Decho.tar.bz2","4":"Decho.tar.bz2","src_id":"3102","5":"3102","creation_date":"1086593523","6":"1086593523"},{"0":"120","vim_version":"6.0","1":"6.0","script_version":"7","2":"7","version_comment":"With g:decho_hide=1, Decho will keep its DBG buffer hidden, thereby allowing window-manipulating scripts their natural behavior.  Use :ls! to see the DBG buffer, and you may use :b [nmbr] to see it.\r\nIn additon, Decho's DBG window's is silently created, and Dfunc\/Decho\/Dret will always resize the DBG window to the number of lines specified by g:decho_winheight.\r\n","3":"With g:decho_hide=1, Decho will keep its DBG buffer hidden, thereby allowing window-manipulating scripts their natural behavior.  Use :ls! to see the DBG buffer, and you may use :b [nmbr] to see it.\r\nIn additon, Decho's DBG window's is silently created, and Dfunc\/Decho\/Dret will always resize the DBG window to the number of lines specified by g:decho_winheight.\r\n","package":"Decho.tar.bz2","4":"Decho.tar.bz2","src_id":"3092","5":"3092","creation_date":"1086173712","6":"1086173712"},{"0":"120","vim_version":"6.0","1":"6.0","script_version":"6","2":"6","version_comment":"Now, along with Decho(), is\r\n  Dfunc(\"funcname(...)\") -- for tracking entry to function funcname\r\n  Dret(\"funcname ...\") -- for tracking return from function funcname\r\nIncludes special syntax highlighting for Dfunc\/Decho\/Dret files, too.\r\n","3":"Now, along with Decho(), is\r\n  Dfunc(\"funcname(...)\") -- for tracking entry to function funcname\r\n  Dret(\"funcname ...\") -- for tracking return from function funcname\r\nIncludes special syntax highlighting for Dfunc\/Decho\/Dret files, too.\r\n","package":"Decho.tar.bz2","4":"Decho.tar.bz2","src_id":"3012","5":"3012","creation_date":"1084283041","6":"1084283041"}]},"119":{"script_id":"119","0":"119","script_name":"vim.vim","1":"vim.vim","script_type":"indent","2":"indent","summary":"indentation for vim script with support for embedded scripting language","3":"indentation for vim script with support for embedded scripting language","description":"This script is for those of us who uses embedded scripting language in the here document form.\r\nsee :help perl, :help ruby, :help python, :help tcl\r\nif you embed a script in vim using the \r\nperl<<EOF\r\n#some perl code\r\nEOF\r\nor equivalent for other script languages, the scripts won't be correctly indented.\r\nWorse, if you write some python this way and reindent your file the whole script is trashed since\r\nthe indentation was meaningfull and it is lost.\r\n\r\nThis scripts add support for indenting the embedded script.\r\nPlease mail me any problems you encounter with this script","4":"This script is for those of us who uses embedded scripting language in the here document form.\r\nsee :help perl, :help ruby, :help python, :help tcl\r\nif you embed a script in vim using the \r\nperl<<EOF\r\n#some perl code\r\nEOF\r\nor equivalent for other script languages, the scripts won't be correctly indented.\r\nWorse, if you write some python this way and reindent your file the whole script is trashed since\r\nthe indentation was meaningfull and it is lost.\r\n\r\nThis scripts add support for indenting the embedded script.\r\nPlease mail me any problems you encounter with this script","install_details":"just put this script in an indent subdirectory somewhere in the runtimepath (:help runtimepath).\r\nThe runtime directory where you put it must be BEFORE the standard vim runtime directory, this\r\nallows this script to use the regular indent\/vim.vim script for the non embedded part.\r\ne.g:\r\ndefault runtimepath on unix:\r\n$HOME\/.vim,$VIM\/vimfiles,$VIMRUNTIME,$VIM\/vimfiles\/after,$HOME\/.vim\/after\r\nthe script must be copied in $HOME\/.vim\/indent\r\nor in $VIM\/vimfiles","5":"just put this script in an indent subdirectory somewhere in the runtimepath (:help runtimepath).\r\nThe runtime directory where you put it must be BEFORE the standard vim runtime directory, this\r\nallows this script to use the regular indent\/vim.vim script for the non embedded part.\r\ne.g:\r\ndefault runtimepath on unix:\r\n$HOME\/.vim,$VIM\/vimfiles,$VIMRUNTIME,$VIM\/vimfiles\/after,$HOME\/.vim\/after\r\nthe script must be copied in $HOME\/.vim\/indent\r\nor in $VIM\/vimfiles","first_name":"Benoit","6":"Benoit","last_name":"Cerrina","7":"Cerrina","releases":[{"0":"119","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"vim.vim","4":"vim.vim","src_id":"266","5":"266","creation_date":"1002846615","6":"1002846615"}]},"118":{"script_id":"118","0":"118","script_name":"Shell.vim","1":"Shell.vim","script_type":"utility","2":"utility","summary":"A shell buffer in vim.","3":"A shell buffer in vim.","description":"Many a time I find myself missing the power of\r\n*the* editor while typing shell commands. This\r\nscript opens a new buffer which can be used to\r\nenter shell commands. Commands will be\r\nexecuted when you type <Enter>. Simply put, it\r\ndoes a :r!command<cr> and a little more.\r\n\r\nThe global variable g:PROMPT wil be used as\r\nthe prompt string.","4":"Many a time I find myself missing the power of\r\n*the* editor while typing shell commands. This\r\nscript opens a new buffer which can be used to\r\nenter shell commands. Commands will be\r\nexecuted when you type <Enter>. Simply put, it\r\ndoes a :r!command<cr> and a little more.\r\n\r\nThe global variable g:PROMPT wil be used as\r\nthe prompt string.","install_details":"Save it somwhere and add a line to your .vimrc \r\nthat will source the file.","5":"Save it somwhere and add a line to your .vimrc \r\nthat will source the file.","first_name":"Janakiraman","6":"Janakiraman","last_name":"","7":"","releases":[{"0":"118","vim_version":"5.7","1":"5.7","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"Shell.vim","4":"Shell.vim","src_id":"265","5":"265","creation_date":"1002829316","6":"1002829316"}]},"117":{"script_id":"117","0":"117","script_name":"cs.vim","1":"cs.vim","script_type":"syntax","2":"syntax","summary":"Another C# Syntax Colorizer File","3":"Another C# Syntax Colorizer File","description":"Another C# syntax colorizer, this one made by a friend and I over the course of Beta 2. Some things don't work correctly, or aren't done yet (#region folding, stuff like that), but it's fairly generic enough to have a nice base for adding things.\r\n\r\nTo add:\r\n- error classes\r\n- directionals (and call them that)\r\n- operators\r\n- #region folding\r\n\r\nI'll copy the contents of the System classes and integrate coloring for that (probably by copying wholesale from vimscript #116) if someone really wants me to do so. Ain't Open Source great? =P","4":"Another C# syntax colorizer, this one made by a friend and I over the course of Beta 2. Some things don't work correctly, or aren't done yet (#region folding, stuff like that), but it's fairly generic enough to have a nice base for adding things.\r\n\r\nTo add:\r\n- error classes\r\n- directionals (and call them that)\r\n- operators\r\n- #region folding\r\n\r\nI'll copy the contents of the System classes and integrate coloring for that (probably by copying wholesale from vimscript #116) if someone really wants me to do so. Ain't Open Source great? =P","install_details":"Copy to the usual place. Email me if you want some support filetypes.vim and whatnot to work it into vim proper without touching anything in your vim60 directory. This part gave me a lot of guff when I was just starting out with it on Windows...","5":"Copy to the usual place. Email me if you want some support filetypes.vim and whatnot to work it into vim proper without touching anything in your vim60 directory. This part gave me a lot of guff when I was just starting out with it on Windows...","first_name":"Nathan","6":"Nathan","last_name":"Sharfi","7":"Sharfi","releases":[{"0":"117","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"cs.vim","4":"cs.vim","src_id":"259","5":"259","creation_date":"1002674697","6":"1002674697"}]},"116":{"script_id":"116","0":"116","script_name":"csharp.vim","1":"csharp.vim","script_type":"syntax","2":"syntax","summary":"C# Syntax file","3":"C# Syntax file","description":"This is off of the comp.editors newsgroup. I wanted to make sure it wasn't \"lost\" so I am uploading it to here. I have tweaked it slightly. I am not a syntax guru so please someone take it...modify it...love it! I do not know who the original author is otherwise I would give him credit in the file.","4":"This is off of the comp.editors newsgroup. I wanted to make sure it wasn't \"lost\" so I am uploading it to here. I have tweaked it slightly. I am not a syntax guru so please someone take it...modify it...love it! I do not know who the original author is otherwise I would give him credit in the file.","install_details":"Just put it in the normal place...","5":"Just put it in the normal place...","first_name":"Robert","6":"Robert","last_name":"Hicks","7":"Hicks","releases":[{"0":"116","vim_version":"6.0","1":"6.0","script_version":"1.1","2":"1.1","version_comment":"A few syntax statements were updated and folding was added for #region...#endregion regions in C# files.","3":"A few syntax statements were updated and folding was added for #region...#endregion regions in C# files.","package":"csharp.vim","4":"csharp.vim","src_id":"1021","5":"1021","creation_date":"1026834302","6":"1026834302"},{"0":"116","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"csharp.vim","4":"csharp.vim","src_id":"257","5":"257","creation_date":"1002648826","6":"1002648826"}]},"115":{"script_id":"115","0":"115","script_name":"blue.vim","1":"blue.vim","script_type":"color scheme","2":"color scheme","summary":"a blue theme for vim","3":"a blue theme for vim","description":"I just wanted a blue theme for use with vim ... and I did this one. I looks better on gvim, because of the hexa color values there. but works good on the console too. some things need to fix, but by now its working good for me. ;-)","4":"I just wanted a blue theme for use with vim ... and I did this one. I looks better on gvim, because of the hexa color values there. but works good on the console too. some things need to fix, but by now its working good for me. ;-)","install_details":"just copy to your vimfiles\\colors directory","5":"just copy to your vimfiles\\colors directory","first_name":"Eustaquio","6":"Eustaquio","last_name":"Rangel de Oliveira Jr.","7":"Rangel de Oliveira Jr.","releases":[{"0":"115","vim_version":"6.0","1":"6.0","script_version":"0.3","2":"0.3","version_comment":"Just change some blue colors and add some other colors (to be honest, just green eheh)","3":"Just change some blue colors and add some other colors (to be honest, just green eheh)","package":"blue.vim","4":"blue.vim","src_id":"1590","5":"1590","creation_date":"1041306951","6":"1041306951"},{"0":"115","vim_version":"6.0","1":"6.0","script_version":"0.2","2":"0.2","version_comment":"just fixed some things like visual mode selection,  error & warning msg, vertical split and directory colors. have fun ;-)","3":"just fixed some things like visual mode selection,  error & warning msg, vertical split and directory colors. have fun ;-)","package":"blue.vim","4":"blue.vim","src_id":"260","5":"260","creation_date":"1002702831","6":"1002702831"},{"0":"115","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"blue.vim","4":"blue.vim","src_id":"252","5":"252","creation_date":"1002624788","6":"1002624788"}]},"114":{"script_id":"114","0":"114","script_name":"MultiPrompt.vim","1":"MultiPrompt.vim","script_type":"utility","2":"utility","summary":"\"Emulates\" a multifield prompt dialog even in console mode!","3":"\"Emulates\" a multifield prompt dialog even in console mode!","description":"\"Emulates\" a multifield prompt dialog in console mode!\r\nIdeal tool for speeding up your typing. Good for constructs, which contains constant text with a few small variable texts.\r\nSee the examples in the script!\r\nWARNING: Don't use with a beta version! It will crash vim. (due to a bug in vim)","4":"\"Emulates\" a multifield prompt dialog in console mode!\r\nIdeal tool for speeding up your typing. Good for constructs, which contains constant text with a few small variable texts.\r\nSee the examples in the script!\r\nWARNING: Don't use with a beta version! It will crash vim. (due to a bug in vim)","install_details":"Source it, learn the examples (comment them out) and define your own mappings!\r\nImprove it, comment it!\r\nFeedback is extremely granted","5":"Source it, learn the examples (comment them out) and define your own mappings!\r\nImprove it, comment it!\r\nFeedback is extremely granted","first_name":"Gergely","6":"Gergely","last_name":"Kontra","7":"Kontra","releases":[{"0":"114","vim_version":"6.0","1":"6.0","script_version":"0.51","2":"0.51","version_comment":"Use curly-brace variables","3":"Use curly-brace variables","package":"MultiPrompt.vim","4":"MultiPrompt.vim","src_id":"653","5":"653","creation_date":"1015416369","6":"1015416369"}]},"113":{"script_id":"113","0":"113","script_name":"idutils","1":"idutils","script_type":"utility","2":"utility","summary":"Simple interface with GNU id-utils (deprecated)","3":"Simple interface with GNU id-utils (deprecated)","description":"This script has been superceded by vimscript #1062 with many enhancements.\r\n\r\nThis script provides a simple interface with GNU id-utils.\r\n\r\nSummary Of Features:\r\n  Command Line:\r\n      IGInitialize, IDGrep, IDGrepAdd\r\n                                                                              \r\n  Settings:\r\n      g:IGlidcmd, g:IGfiltercmd, g:IGautoCopen\r\n                                                                              \r\nHelp:\r\n      IDGrep    <keyword>\r\n      IDGrep    [<lid argument> ...] <lid keyword pattern> \r\n      IDGrep    <lid options> [+f <filter arguments> ...]\r\n      IDGrepAdd <keyword>\r\n      IDGrepAdd [<lid options> ...] <lid keyword pattern> \r\n      IDGrepAdd <lid arguments> [+f <filter arguments> ...]\r\n                                                                              \r\n  You can use all the regular quickfix commands to traverse from one hit to\r\n    another.\r\n                                                                              \r\n      :h quickfix \r\n                                                                              \r\n  Each time you run IDGrepAdd, the new list of matches are added to the\r\n    existing list. This works the same as 'grepadd' command. If you can't\r\n    use a single filter to get all the matches then this command helps you to\r\n    still work with a single list instead of generating multiple lists.\r\n                                                                              \r\n  Use the g:IGlidcmd, g:IGfiltercmd, g:IGautoCopen global variables to set\r\n    the path to 'lid' command, filter command name\/path (defaults to 'grep')\r\n    and if the error list window should automatically be opened (runs\r\n    |:cwindow| at the end).\r\n                                                                              \r\n  You can pass as many filters as you want, each prefixed with +f option.\r\n    The filter arguments are escaped such a way that the arguments are\r\n    passed through the shell, unmodified to the filter.\r\n                                                                              \r\nExamples: \r\n  - Filter the lines that don't contain src.\r\n      IDGrep main +f src\r\n                                                                              \r\n  - Filter the lines that contain src.\r\n      IDGrep main +f -v src\r\n                                                                              \r\n  - To search for the current word in all the files and filter the results\r\n    not containing \\.java in the grepped output. This will potentially\r\n    return all the occurences in the java files only. \r\n      IDGrep <cword> +f \\.java \r\n                                                                              \r\n  - If any argument contains spaces, then you need to protect them by\r\n    prefixing them with a backslash.  The following will filter those lines\r\n    that don't contain \"ABC XYZ\".\r\n      IDGrep <cword> +f ABC\\ XYZ \r\n\r\n\r\nSearch_key_words: idutils id-utils gnu id grep gid mkid lid Hari Krishna Dara","4":"This script has been superceded by vimscript #1062 with many enhancements.\r\n\r\nThis script provides a simple interface with GNU id-utils.\r\n\r\nSummary Of Features:\r\n  Command Line:\r\n      IGInitialize, IDGrep, IDGrepAdd\r\n                                                                              \r\n  Settings:\r\n      g:IGlidcmd, g:IGfiltercmd, g:IGautoCopen\r\n                                                                              \r\nHelp:\r\n      IDGrep    <keyword>\r\n      IDGrep    [<lid argument> ...] <lid keyword pattern> \r\n      IDGrep    <lid options> [+f <filter arguments> ...]\r\n      IDGrepAdd <keyword>\r\n      IDGrepAdd [<lid options> ...] <lid keyword pattern> \r\n      IDGrepAdd <lid arguments> [+f <filter arguments> ...]\r\n                                                                              \r\n  You can use all the regular quickfix commands to traverse from one hit to\r\n    another.\r\n                                                                              \r\n      :h quickfix \r\n                                                                              \r\n  Each time you run IDGrepAdd, the new list of matches are added to the\r\n    existing list. This works the same as 'grepadd' command. If you can't\r\n    use a single filter to get all the matches then this command helps you to\r\n    still work with a single list instead of generating multiple lists.\r\n                                                                              \r\n  Use the g:IGlidcmd, g:IGfiltercmd, g:IGautoCopen global variables to set\r\n    the path to 'lid' command, filter command name\/path (defaults to 'grep')\r\n    and if the error list window should automatically be opened (runs\r\n    |:cwindow| at the end).\r\n                                                                              \r\n  You can pass as many filters as you want, each prefixed with +f option.\r\n    The filter arguments are escaped such a way that the arguments are\r\n    passed through the shell, unmodified to the filter.\r\n                                                                              \r\nExamples: \r\n  - Filter the lines that don't contain src.\r\n      IDGrep main +f src\r\n                                                                              \r\n  - Filter the lines that contain src.\r\n      IDGrep main +f -v src\r\n                                                                              \r\n  - To search for the current word in all the files and filter the results\r\n    not containing \\.java in the grepped output. This will potentially\r\n    return all the occurences in the java files only. \r\n      IDGrep <cword> +f \\.java \r\n                                                                              \r\n  - If any argument contains spaces, then you need to protect them by\r\n    prefixing them with a backslash.  The following will filter those lines\r\n    that don't contain \"ABC XYZ\".\r\n      IDGrep <cword> +f ABC\\ XYZ \r\n\r\n\r\nSearch_key_words: idutils id-utils gnu id grep gid mkid lid Hari Krishna Dara","install_details":"Drop the file in your plugin directory or source it from your vimrc.\r\nRequires Vim-6.2 or higher.\r\nRequires genutils (vimscript#197) and multvals (vimscript #171)","5":"Drop the file in your plugin directory or source it from your vimrc.\r\nRequires Vim-6.2 or higher.\r\nRequires genutils (vimscript#197) and multvals (vimscript #171)","first_name":"Hari Krishna","6":"Hari Krishna","last_name":"Dara","7":"Dara","releases":[{"0":"113","vim_version":"6.0","1":"6.0","script_version":"1.3","2":"1.3","version_comment":"Changed -f option to +f since that is used by lid itself. Removed the debug messages.","3":"Changed -f option to +f since that is used by lid itself. Removed the debug messages.","package":"idutils.vim","4":"idutils.vim","src_id":"1171","5":"1171","creation_date":"1030539704","6":"1030539704"},{"0":"113","vim_version":"6.0","1":"6.0","script_version":"1.1","2":"1.1","version_comment":"Improved the command-line syntax. It is now much easier to pass in multiple arguments to both lid and the filter command (grep).","3":"Improved the command-line syntax. It is now much easier to pass in multiple arguments to both lid and the filter command (grep).","package":"idutils.vim","4":"idutils.vim","src_id":"1158","5":"1158","creation_date":"1030042154","6":"1030042154"},{"0":"113","vim_version":"6.0","1":"6.0","script_version":"1.0.2","2":"1.0.2","version_comment":"Minor changes. Lets you define your own \"lid\" command interface. Fixes an extra message coming up when IDGrep is run.","3":"Minor changes. Lets you define your own \"lid\" command interface. Fixes an extra message coming up when IDGrep is run.","package":"idutils.vim","4":"idutils.vim","src_id":"253","5":"253","creation_date":"1002629178","6":"1002629178"},{"0":"113","vim_version":"6.0","1":"6.0","script_version":"1.0.1","2":"1.0.1","version_comment":"Initial upload","3":"Initial upload","package":"idutils.vim","4":"idutils.vim","src_id":"247","5":"247","creation_date":"1002553786","6":"1002553786"}]},"112":{"script_id":"112","0":"112","script_name":"borland.vim","1":"borland.vim","script_type":"utility","2":"utility","summary":"compiler plugin for some Borland compilers","3":"compiler plugin for some Borland compilers","description":"Contains a single errorformat for all supported compilers, as well as detailed settings\/comments for each.\nSupported\/tested compilers : \n- Turbo C 2.0; Borland C 3.1, 5.2; CBuilder 4, 5;\n- Turbo Pascal 7.0; Delphi 5, 6; Kylix 1.0;\n- Free pascal 1.0 (GNU)","4":"Contains a single errorformat for all supported compilers, as well as detailed settings\/comments for each.\nSupported\/tested compilers : \n- Turbo C 2.0; Borland C 3.1, 5.2; CBuilder 4, 5;\n- Turbo Pascal 7.0; Delphi 5, 6; Kylix 1.0;\n- Free pascal 1.0 (GNU)","install_details":"Copy to $VIMRUNTIME\/compiler, restart Vim.","5":"Copy to $VIMRUNTIME\/compiler, restart Vim.","first_name":"Thorsten","6":"Thorsten","last_name":"Maerz","7":"Maerz","releases":[{"0":"112","vim_version":"6.0","1":"6.0","script_version":"1.1","2":"1.1","version_comment":"Initial upload","3":"Initial upload","package":"borland.vim","4":"borland.vim","src_id":"246","5":"246","creation_date":"1002431474","6":"1002431474"}]},"111":{"script_id":"111","0":"111","script_name":"torte.vim","1":"torte.vim","script_type":"color scheme","2":"color scheme","summary":"Grey on black, slighter contrasts (for TFT)","3":"Grey on black, slighter contrasts (for TFT)","description":"Dark colorscheme, uses grey\/green\/yellow text on black.\nNo bold chars (better for small fonts).","4":"Dark colorscheme, uses grey\/green\/yellow text on black.\nNo bold chars (better for small fonts).","install_details":"Copy to $VIMRUNTIME\/colors directory, restart Vim.","5":"Copy to $VIMRUNTIME\/colors directory, restart Vim.","first_name":"Thorsten","6":"Thorsten","last_name":"Maerz","7":"Maerz","releases":[{"0":"111","vim_version":"6.0","1":"6.0","script_version":"1.1","2":"1.1","version_comment":"Initial upload","3":"Initial upload","package":"torte.vim","4":"torte.vim","src_id":"245","5":"245","creation_date":"1002430976","6":"1002430976"}]},"110":{"script_id":"110","0":"110","script_name":"golden.vim","1":"golden.vim","script_type":"color scheme","2":"color scheme","summary":"Gold based color scheme","3":"Gold based color scheme","description":"A dark colorscheme that encorporates a gold theme.  Supports folds, and splitbuffers.  examples can be found at http:\/\/www.trolocsis.com\/vim\/goldencpp.html and http:\/\/www.trolocsis.com\/vim\/pythontest.html","4":"A dark colorscheme that encorporates a gold theme.  Supports folds, and splitbuffers.  examples can be found at http:\/\/www.trolocsis.com\/vim\/goldencpp.html and http:\/\/www.trolocsis.com\/vim\/pythontest.html","install_details":"","5":"","first_name":"Ryan","6":"Ryan","last_name":"Phillips","7":"Phillips","releases":[{"0":"110","vim_version":"6.0","1":"6.0","script_version":"0.0.2","2":"0.0.2","version_comment":"Initial upload","3":"Initial upload","package":"golden.vim","4":"golden.vim","src_id":"244","5":"244","creation_date":"1002417839","6":"1002417839"}]},"109":{"script_id":"109","0":"109","script_name":"lightWeightArray.vim","1":"lightWeightArray.vim","script_type":"utility","2":"utility","summary":"*obsolete* Small utility to work with vim multivalues variables","3":"*obsolete* Small utility to work with vim multivalues variables","description":"I have improved this script and uploaded as a new script called multvals.vim. Please download it from here:\r\n\r\nhttp:\/\/vim.sourceforge.net\/scripts\/script.php?script_id=171\r\n\r\nThis defines two readonly functions to work with ',' separated multivalues such as \"tags\". You can also use it as a light-weight array operations. You can make up an array by concatenating a set of values with a ',' in between them and later use these functions to extract the individual values. ","4":"I have improved this script and uploaded as a new script called multvals.vim. Please download it from here:\r\n\r\nhttp:\/\/vim.sourceforge.net\/scripts\/script.php?script_id=171\r\n\r\nThis defines two readonly functions to work with ',' separated multivalues such as \"tags\". You can also use it as a light-weight array operations. You can make up an array by concatenating a set of values with a ',' in between them and later use these functions to extract the individual values. ","install_details":"Source it or drop it in your plugin directory.","5":"Source it or drop it in your plugin directory.","first_name":"Hari Krishna","6":"Hari Krishna","last_name":"Dara","7":"Dara","releases":[{"0":"109","vim_version":"6.0","1":"6.0","script_version":"","2":"","version_comment":"Initial upload","3":"Initial upload","package":"lightWeightArray.vim","4":"lightWeightArray.vim","src_id":"243","5":"243","creation_date":"1002371561","6":"1002371561"}]},"108":{"script_id":"108","0":"108","script_name":"bufNwinUtils.vim","1":"bufNwinUtils.vim","script_type":"utility","2":"utility","summary":"*obsolete* A nice set of useful functions","3":"*obsolete* A nice set of useful functions","description":"This script is not maintained any more. I have renamed it to genutils.vim and added many more functions. Unless you are using a very old version of one of my other scripts, that require this, you should download the new script, genutils.vim\r\n\r\n(http:\/\/vim.sourceforge.net\/scripts\/script.php?script_id=197\r\n\r\n-----------\r\n\r\nDefines the following functions:\r\n\r\n- NumberOfWindows\r\n- FindWindowForBuffer\r\n- FindBufferForName\r\n- SaveWindowSettings\r\n- RestoreWindowSettings\r\n\r\nAnd other misc. functions.","4":"This script is not maintained any more. I have renamed it to genutils.vim and added many more functions. Unless you are using a very old version of one of my other scripts, that require this, you should download the new script, genutils.vim\r\n\r\n(http:\/\/vim.sourceforge.net\/scripts\/script.php?script_id=197\r\n\r\n-----------\r\n\r\nDefines the following functions:\r\n\r\n- NumberOfWindows\r\n- FindWindowForBuffer\r\n- FindBufferForName\r\n- SaveWindowSettings\r\n- RestoreWindowSettings\r\n\r\nAnd other misc. functions.","install_details":"Source it or drop it in plugin directory.","5":"Source it or drop it in plugin directory.","first_name":"Hari Krishna","6":"Hari Krishna","last_name":"Dara","7":"Dara","releases":[{"0":"108","vim_version":"6.0","1":"6.0","script_version":"1.0.3","2":"1.0.3","version_comment":"New functions to store and restore virtual intelligent positions. This is like having additional markers over the builtin a-z makers. I have extracted the idea from explorer.vim","3":"New functions to store and restore virtual intelligent positions. This is like having additional markers over the builtin a-z makers. I have extracted the idea from explorer.vim","package":"bufNwinUtils.vim","4":"bufNwinUtils.vim","src_id":"330","5":"330","creation_date":"1005259963","6":"1005259963"}]},"107":{"script_id":"107","0":"107","script_name":"SelectBuf","1":"SelectBuf","script_type":"utility","2":"utility","summary":"A fast and extensible buffer explorer.","3":"A fast and extensible buffer explorer.","description":"PLEASE READ THE INSTALL SECTION COMPLETELY.\r\n\r\nSelectBuf is a buffer explorer similar to the file explorer plugin that comes\r\nwith Vim, the difference being that file explorer allows you to view the files\r\non the file system, where as buffer explorer limits the view to only the files\r\nthat are already opened in the current Vim session. It is even possible and \r\neasy to extend the plugin with new commands.\r\n\r\nSince the first time I released it in Jul '99 (try sending an email to \r\nvim-thread.1235@vim.org), the script has gone many\r\nrevisions and enhancements both in technology and features, taking advantage of all the niceties that the new versions of Vim has to offer.\r\n\r\nFor detailed help, see \":help selectbuf\" or read doc\/selectbuf.txt. \r\n\r\n- Install the plugin, restart vim and press <F3> (the default key binding) to\r\n  get the list of buffers.\r\n- Move the cursor on to the buffer that you need to select and press <CR> or\r\n  double click with the left-mouse button.\r\n- If you want to close the window without making a selection, press <F3>\r\n  again.\r\n- You can also press ^W<CR> or O to open the file in a new or previous window.\r\n  You can use d to delete or D to wipeout the buffer. Use d again to\r\n  undelete a previously deleted buffer (you need to first view the deleted\r\n  buffers using u command).\r\n\r\nYou can change the default key mapping to open browser window by setting \r\n\r\n      nmap <unique> <silent> <YourKey> <Plug>SelectBuf\r\n\r\nAlmost everything is configurable, including all the key mappings that are\r\navailable. E.g., you can change the help key to <C-H> instead of the default ?,\r\nso you can free it to do backward searches in the file list, using the\r\nfollowing mapping:\r\n\r\n      noremap <silent> <Plug>SelBufHelpKey <C-H> \r\n\r\nSome highlights of the features are:\r\n\r\n- It is super fast as the buffer list is cached and incrementally built as new\r\n  files are added and the old ones are deleted.\r\n- Hide buffer numbers to save on real estate (goes well with \"Always On\" mode\r\n  or when used with WinManager).\r\n- Opens a new window to avoid disturbing your existing windows. But you can\r\n  change the behavior to reuse the current window or even to permanently keep\r\n  it open.\r\n- You can select block of buffers and delete or wipeout all the buffers at once.\r\n- You can toggle various settings on and off while you are in the browser. You\r\n  can e.g., toggle showing the buffer indicators by pressing i.\r\n- Goes very well with WinManager.\r\n- There are different sorting keys available. You can sort by buffer number,\r\n  name, type (extension), path, indicators and MRU order. You can even select a\r\n  default sort order\r\n- If you use multiple windows, then the browser restores the window sizes after\r\n  closing it.\r\n- Syntax coloring makes it easy to find the buffer you are looking to switch to.\r\n- Full configurability.\r\n- Extensibility.\r\n- Support for WinManager and multiselect plugins.\r\n- and many more.\r\n\r\nFor more information, read the vim help on seletbuf.\r\n\r\n\r\nSearch_key_words: buffer selectbuf bufexplorer explorer list select multvals genutils multiselect Hari Krishna Dara\r\n","4":"PLEASE READ THE INSTALL SECTION COMPLETELY.\r\n\r\nSelectBuf is a buffer explorer similar to the file explorer plugin that comes\r\nwith Vim, the difference being that file explorer allows you to view the files\r\non the file system, where as buffer explorer limits the view to only the files\r\nthat are already opened in the current Vim session. It is even possible and \r\neasy to extend the plugin with new commands.\r\n\r\nSince the first time I released it in Jul '99 (try sending an email to \r\nvim-thread.1235@vim.org), the script has gone many\r\nrevisions and enhancements both in technology and features, taking advantage of all the niceties that the new versions of Vim has to offer.\r\n\r\nFor detailed help, see \":help selectbuf\" or read doc\/selectbuf.txt. \r\n\r\n- Install the plugin, restart vim and press <F3> (the default key binding) to\r\n  get the list of buffers.\r\n- Move the cursor on to the buffer that you need to select and press <CR> or\r\n  double click with the left-mouse button.\r\n- If you want to close the window without making a selection, press <F3>\r\n  again.\r\n- You can also press ^W<CR> or O to open the file in a new or previous window.\r\n  You can use d to delete or D to wipeout the buffer. Use d again to\r\n  undelete a previously deleted buffer (you need to first view the deleted\r\n  buffers using u command).\r\n\r\nYou can change the default key mapping to open browser window by setting \r\n\r\n      nmap <unique> <silent> <YourKey> <Plug>SelectBuf\r\n\r\nAlmost everything is configurable, including all the key mappings that are\r\navailable. E.g., you can change the help key to <C-H> instead of the default ?,\r\nso you can free it to do backward searches in the file list, using the\r\nfollowing mapping:\r\n\r\n      noremap <silent> <Plug>SelBufHelpKey <C-H> \r\n\r\nSome highlights of the features are:\r\n\r\n- It is super fast as the buffer list is cached and incrementally built as new\r\n  files are added and the old ones are deleted.\r\n- Hide buffer numbers to save on real estate (goes well with \"Always On\" mode\r\n  or when used with WinManager).\r\n- Opens a new window to avoid disturbing your existing windows. But you can\r\n  change the behavior to reuse the current window or even to permanently keep\r\n  it open.\r\n- You can select block of buffers and delete or wipeout all the buffers at once.\r\n- You can toggle various settings on and off while you are in the browser. You\r\n  can e.g., toggle showing the buffer indicators by pressing i.\r\n- Goes very well with WinManager.\r\n- There are different sorting keys available. You can sort by buffer number,\r\n  name, type (extension), path, indicators and MRU order. You can even select a\r\n  default sort order\r\n- If you use multiple windows, then the browser restores the window sizes after\r\n  closing it.\r\n- Syntax coloring makes it easy to find the buffer you are looking to switch to.\r\n- Full configurability.\r\n- Extensibility.\r\n- Support for WinManager and multiselect plugins.\r\n- and many more.\r\n\r\nFor more information, read the vim help on seletbuf.\r\n\r\n\r\nSearch_key_words: buffer selectbuf bufexplorer explorer list select multvals genutils multiselect Hari Krishna Dara\r\n","install_details":"For complete installation instructions, read the help on\r\nselectbuf-installation. To get started on the help, expand the zip file in your\r\nruntime directory and run :helpt on your doc directory or just read through the\r\ndoc\/selectbuf.txt file.\r\n\r\nRequires, \r\ngenutils.vim: vimscript#197\r\n\r\nDepends on (optional),\r\nmultiselect.vim: vimscript#953\r\n\r\nWinManager version 2.3 has some bugs because of which selectbuf may not work\r\ncorrectly with it. I am working with Srinath to have a new version with fixes\r\nuntil then, a version with fixes can be downloaded from: \r\n\r\nhttp:\/\/mywebpage.netscape.com\/haridara\/vim\/winmanager.vim \r\n\r\nFor versions older than 4.0, you also need multvals.vim: vimscript#171 in addition to genutils, and you need to download the non-autoload versions of both. See their respective installation sections for more information .\r\n\r\nFor versions older than 2.2.2,\r\nbufNwinUtils.vim: http:\/\/vim.sourceforge.net\/scripts\/script.php?script_id=108\r\nlightWeightArray.vim: http:\/\/vim.sourceforge.net\/scripts\/script.php?script_id=109\r\n\r\n","5":"For complete installation instructions, read the help on\r\nselectbuf-installation. To get started on the help, expand the zip file in your\r\nruntime directory and run :helpt on your doc directory or just read through the\r\ndoc\/selectbuf.txt file.\r\n\r\nRequires, \r\ngenutils.vim: vimscript#197\r\n\r\nDepends on (optional),\r\nmultiselect.vim: vimscript#953\r\n\r\nWinManager version 2.3 has some bugs because of which selectbuf may not work\r\ncorrectly with it. I am working with Srinath to have a new version with fixes\r\nuntil then, a version with fixes can be downloaded from: \r\n\r\nhttp:\/\/mywebpage.netscape.com\/haridara\/vim\/winmanager.vim \r\n\r\nFor versions older than 4.0, you also need multvals.vim: vimscript#171 in addition to genutils, and you need to download the non-autoload versions of both. See their respective installation sections for more information .\r\n\r\nFor versions older than 2.2.2,\r\nbufNwinUtils.vim: http:\/\/vim.sourceforge.net\/scripts\/script.php?script_id=108\r\nlightWeightArray.vim: http:\/\/vim.sourceforge.net\/scripts\/script.php?script_id=109\r\n\r\n","first_name":"Hari Krishna","6":"Hari Krishna","last_name":"Dara","7":"Dara","releases":[{"0":"107","vim_version":"7.0","1":"7.0","script_version":"4.3","2":"4.3","version_comment":"- New setting selBufShowRelativePath (Nathan Huizinga\r\n  (nathan dot huizinga at gmail dot com)).\r\n- Bug fix: |:SBSettings| is still broken.\r\nRequires at least version 2.4 of genutils.\r\n","3":"- New setting selBufShowRelativePath (Nathan Huizinga\r\n  (nathan dot huizinga at gmail dot com)).\r\n- Bug fix: |:SBSettings| is still broken.\r\nRequires at least version 2.4 of genutils.\r\n","package":"selectbuf-4.3.zip","4":"selectbuf-4.3.zip","src_id":"7232","5":"7232","creation_date":"1181660704","6":"1181660704"},{"0":"107","vim_version":"7.0","1":"7.0","script_version":"4.2","2":"4.2","version_comment":"- Bug fix: |:SBSettings| is broken.\r\n- Bug fix: syntax highlighting is sometimes broken the first time browser\r\n  window is open.\r\n- Bug fix: formatting is sometimes broken with incremental update, when\r\n  browser is open after certain sequence of buffer changes.\r\n","3":"- Bug fix: |:SBSettings| is broken.\r\n- Bug fix: syntax highlighting is sometimes broken the first time browser\r\n  window is open.\r\n- Bug fix: formatting is sometimes broken with incremental update, when\r\n  browser is open after certain sequence of buffer changes.\r\n","package":"selectbuf-4.2.zip","4":"selectbuf-4.2.zip","src_id":"7205","5":"7205","creation_date":"1181032262","6":"1181032262"},{"0":"107","vim_version":"7.0","1":"7.0","script_version":"4.1","2":"4.1","version_comment":"- Bug fix: multiselect usage is not conditional in some places.\r\n- Bug fix: Syntax may not be setup correctly when the first time browser window\r\n  is opened.\r\n","3":"- Bug fix: multiselect usage is not conditional in some places.\r\n- Bug fix: Syntax may not be setup correctly when the first time browser window\r\n  is opened.\r\n","package":"selectbuf-4.1.zip","4":"selectbuf-4.1.zip","src_id":"6173","5":"6173","creation_date":"1158079655","6":"1158079655"},{"0":"107","vim_version":"7.0","1":"7.0","script_version":"4.0","2":"4.0","version_comment":"- Started using vim7 features, so it is no longer backwards compatible.\r\n- No longer depends on multvals. The plugin has been reworked to use Vim7 arrays\r\n  and sort(), so there should be significant improvement in performance\r\n  everywhere.\r\n- It is now autoloaded on demand, which means it will help your vim session\r\n  load faster.\r\n- Support for multiselect has been enhanced. The selections are a lot more\r\n  meaningful now, as they move along with the buffers. You can even sort the\r\n  contents and still not loose your selections.\r\n- |:SBSettings| is now more flexible and easier to use as it supports arguments\r\n  and command-line completion.\r\n- The global variables for the settings are no longer removed, but you should\r\n  still run |:SBInitialize| for any side effects to take place. Use\r\n  |:SBSettings| to make this easier.\r\nIf you want to use multiselect with this plugin, make sure you download the latest version of it.","3":"- Started using vim7 features, so it is no longer backwards compatible.\r\n- No longer depends on multvals. The plugin has been reworked to use Vim7 arrays\r\n  and sort(), so there should be significant improvement in performance\r\n  everywhere.\r\n- It is now autoloaded on demand, which means it will help your vim session\r\n  load faster.\r\n- Support for multiselect has been enhanced. The selections are a lot more\r\n  meaningful now, as they move along with the buffers. You can even sort the\r\n  contents and still not loose your selections.\r\n- |:SBSettings| is now more flexible and easier to use as it supports arguments\r\n  and command-line completion.\r\n- The global variables for the settings are no longer removed, but you should\r\n  still run |:SBInitialize| for any side effects to take place. Use\r\n  |:SBSettings| to make this easier.\r\nIf you want to use multiselect with this plugin, make sure you download the latest version of it.","package":"selectbuf-4.0.zip","4":"selectbuf-4.0.zip","src_id":"6163","5":"6163","creation_date":"1157995651","6":"1157995651"},{"0":"107","vim_version":"6.0","1":"6.0","script_version":"3.6","2":"3.6","version_comment":"Release 3.6 for vim7 compatibility. Also includes minor changes. This\r\nwill probably the last release that will work in Vim 6.3\/6.4 version.\r\n- Restoring search string works again. New setting\r\n  |selBufRestoreSearchString|.\r\n- New mark d, see |selectbuf-marks|.\r\n","3":"Release 3.6 for vim7 compatibility. Also includes minor changes. This\r\nwill probably the last release that will work in Vim 6.3\/6.4 version.\r\n- Restoring search string works again. New setting\r\n  |selBufRestoreSearchString|.\r\n- New mark d, see |selectbuf-marks|.\r\n","package":"selectbuf-3.6.zip","4":"selectbuf-3.6.zip","src_id":"5659","5":"5659","creation_date":"1147105629","6":"1147105629"},{"0":"107","vim_version":"6.0","1":"6.0","script_version":"3.5","2":"3.5","version_comment":"Bug fixes.\r\n- Refresh now updates the MRU list.\r\n- Fixed broken \"toggle details\" functionality.\r\n- \"SBLaunch .\" now correctly launches windows explorer on the current\r\n  directory as expected.\r\n- Entering buffer number directly in the browser window now works much\r\n  better.\r\n- Misc. bug fixes.\r\n","3":"Bug fixes.\r\n- Refresh now updates the MRU list.\r\n- Fixed broken \"toggle details\" functionality.\r\n- \"SBLaunch .\" now correctly launches windows explorer on the current\r\n  directory as expected.\r\n- Entering buffer number directly in the browser window now works much\r\n  better.\r\n- Misc. bug fixes.\r\n","package":"selectbuf-3.5.zip","4":"selectbuf-3.5.zip","src_id":"4034","5":"4034","creation_date":"1110979923","6":"1110979923"},{"0":"107","vim_version":"6.0","1":"6.0","script_version":"3.4","2":"3.4","version_comment":"- Faster sorting of buffer list.\r\n- If multiselect is installed, you can use spacebar to toggle selection. See\r\n  |selectbuf-multiselect|.\r\n- Fixed a bug in case-insensitive sorting of buffer names.\r\n- Number keys are now mapped to jump to a buffer by its number. See\r\n  |selectbuf-buffer-search|.\r\n- Bug fixes.\r\n    - If SBExec created a new window, it results in a Vim error.\r\n    - Toggle buffer numbers is broken.\r\n    - Other misc. bug fixes.\r\n\r\nGet the latest multvals (vimscript #171) and genutils (vimscript #197) plugins.","3":"- Faster sorting of buffer list.\r\n- If multiselect is installed, you can use spacebar to toggle selection. See\r\n  |selectbuf-multiselect|.\r\n- Fixed a bug in case-insensitive sorting of buffer names.\r\n- Number keys are now mapped to jump to a buffer by its number. See\r\n  |selectbuf-buffer-search|.\r\n- Bug fixes.\r\n    - If SBExec created a new window, it results in a Vim error.\r\n    - Toggle buffer numbers is broken.\r\n    - Other misc. bug fixes.\r\n\r\nGet the latest multvals (vimscript #171) and genutils (vimscript #197) plugins.","package":"selectbuf-3.4.zip","4":"selectbuf-3.4.zip","src_id":"3585","5":"3585","creation_date":"1098991753","6":"1098991753"},{"0":"107","vim_version":"6.0","1":"6.0","script_version":"3.3","2":"3.3","version_comment":"Now requires Vim 6.3.\r\n\r\nMostly a maintenance release.\r\n\t- Better launcher command for windows. You can now launch applications\r\n\t  with arguments, and handles spaces well.\r\n\t- Improved the performance of delete\/wipeout when the list of files is\r\n\t  huge.\r\n\t- Better performance for toggling indicators,paths etc.\r\n\t- A fix for incremental update in split paths.\r\n","3":"Now requires Vim 6.3.\r\n\r\nMostly a maintenance release.\r\n\t- Better launcher command for windows. You can now launch applications\r\n\t  with arguments, and handles spaces well.\r\n\t- Improved the performance of delete\/wipeout when the list of files is\r\n\t  huge.\r\n\t- Better performance for toggling indicators,paths etc.\r\n\t- A fix for incremental update in split paths.\r\n","package":"selectbuf-3.3.zip","4":"selectbuf-3.3.zip","src_id":"3265","5":"3265","creation_date":"1090607005","6":"1090607005"},{"0":"107","vim_version":"6.0","1":"6.0","script_version":"3.2","2":"3.2","version_comment":":help selectbuf-changes-3.2\r\n\r\n- Added a feature to split file paths, instead of the setting\r\n  selBufHighlightOnlyFilename. See help on |selBufAlwaysShowPaths|. The browser\r\n  by default now starts with this mode.\r\n- The display is now more compact by the use of only required number of spaces\r\n  than using hard tabs.\r\n- A setting to ignore case while sorting, see |selBufIgnoreCaseInSort|.\r\n- A new \"selectbuf\" filetype to further customize the syntax highlighting and\r\n  extend the functionality, see |selectbuf-filetype|. There is now an API\r\n  available, see |selectbuf-extend|.\r\n- New command SBExec for selections, see |SBExec|. Extremely useful to execute\r\n  external commands.\r\n- Support for multiple selections through multiselect.vim plugin, see\r\n  |selectbuf-multiselect|.\r\n- New command (very useful, at least on MS Windows), |SBLaunch|.\r\n- Improved |SelBufTHiddenKey| and |SelBufTDetailsKey| to avoid doing a full\r\n  refresh. It should work much faster now.\r\n","3":":help selectbuf-changes-3.2\r\n\r\n- Added a feature to split file paths, instead of the setting\r\n  selBufHighlightOnlyFilename. See help on |selBufAlwaysShowPaths|. The browser\r\n  by default now starts with this mode.\r\n- The display is now more compact by the use of only required number of spaces\r\n  than using hard tabs.\r\n- A setting to ignore case while sorting, see |selBufIgnoreCaseInSort|.\r\n- A new \"selectbuf\" filetype to further customize the syntax highlighting and\r\n  extend the functionality, see |selectbuf-filetype|. There is now an API\r\n  available, see |selectbuf-extend|.\r\n- New command SBExec for selections, see |SBExec|. Extremely useful to execute\r\n  external commands.\r\n- Support for multiple selections through multiselect.vim plugin, see\r\n  |selectbuf-multiselect|.\r\n- New command (very useful, at least on MS Windows), |SBLaunch|.\r\n- Improved |SelBufTHiddenKey| and |SelBufTDetailsKey| to avoid doing a full\r\n  refresh. It should work much faster now.\r\n","package":"selectbuf-3.2.zip","4":"selectbuf-3.2.zip","src_id":"2919","5":"2919","creation_date":"1081362275","6":"1081362275"},{"0":"107","vim_version":"6.0","1":"6.0","script_version":"3.1","2":"3.1","version_comment":"Fixed many bugs found\/reported in version 3.0. The plugin is also much more responsive under WinManager. See :h |selectbuf-changes| for information on what is fixed. Thanks a lot to David Fishburn (fishburn at sybase dot com) for reporting many issues. I also had to fix some more of the WinManager issues, so please download the latest version (with my patches) from the URL mentioned in the installation section. Also download version 1.6 of genutils plugin.\r\n","3":"Fixed many bugs found\/reported in version 3.0. The plugin is also much more responsive under WinManager. See :h |selectbuf-changes| for information on what is fixed. Thanks a lot to David Fishburn (fishburn at sybase dot com) for reporting many issues. I also had to fix some more of the WinManager issues, so please download the latest version (with my patches) from the URL mentioned in the installation section. Also download version 1.6 of genutils plugin.\r\n","package":"selectbuf-3.1.zip","4":"selectbuf-3.1.zip","src_id":"1961","5":"1961","creation_date":"1051894838","6":"1051894838"},{"0":"107","vim_version":"6.0","1":"6.0","script_version":"3.0","2":"3.0","version_comment":"This is a major improvement over the previous version. One feature for\r\nwhich I worked very hard is the incremental update of the buffer list.\r\nThe buffer opens very quickly now irrespective of how many files you\r\nhave currently open in your current session.  Here is a brief list of\r\nnew features. For a complete list and their description see the :help\r\nselectbuf-features\r\n\r\n    - Incremental update of the browser for speed. The browser caches the\r\n      the list of buffers and incrementally changes it as you open new\r\n      files and delete them.\r\n    - Hide buffer numbers to save real estate (useful with \"Always on\"\r\n      mode or with WinManager).\r\n    - New vim help file with detailed description of features and configuration.\r\n    - Block operations for buffer deletes now works well.\r\n    - \"Always On\" mode is now much better.\r\n    - Marks for a quick access to the next, previous and current buffers\r\n      has a better meaning.\r\n    - WinManager integration. This requires patches to WinManager\r\n      though. Until Srinath is out of his hibernation to validate my\r\n      patches and make the next release, it can be downloaded from:\r\n\r\n\thttp:\/\/mywebpage.netscape.com\/haridara\/vim\/winmanager.vim\r\n\r\n      With incremental update feature, opening files from WinManager now\r\n      literally flies. Get the latest versions of multvals and genutils plugins\r\n      along with this. I would very much appreciate any feedback.\r\n","3":"This is a major improvement over the previous version. One feature for\r\nwhich I worked very hard is the incremental update of the buffer list.\r\nThe buffer opens very quickly now irrespective of how many files you\r\nhave currently open in your current session.  Here is a brief list of\r\nnew features. For a complete list and their description see the :help\r\nselectbuf-features\r\n\r\n    - Incremental update of the browser for speed. The browser caches the\r\n      the list of buffers and incrementally changes it as you open new\r\n      files and delete them.\r\n    - Hide buffer numbers to save real estate (useful with \"Always on\"\r\n      mode or with WinManager).\r\n    - New vim help file with detailed description of features and configuration.\r\n    - Block operations for buffer deletes now works well.\r\n    - \"Always On\" mode is now much better.\r\n    - Marks for a quick access to the next, previous and current buffers\r\n      has a better meaning.\r\n    - WinManager integration. This requires patches to WinManager\r\n      though. Until Srinath is out of his hibernation to validate my\r\n      patches and make the next release, it can be downloaded from:\r\n\r\n\thttp:\/\/mywebpage.netscape.com\/haridara\/vim\/winmanager.vim\r\n\r\n      With incremental update feature, opening files from WinManager now\r\n      literally flies. Get the latest versions of multvals and genutils plugins\r\n      along with this. I would very much appreciate any feedback.\r\n","package":"selectbuf-3.0.zip","4":"selectbuf-3.0.zip","src_id":"1876","5":"1876","creation_date":"1048967764","6":"1048967764"},{"0":"107","vim_version":"6.0","1":"6.0","script_version":"2.2.4","2":"2.2.4","version_comment":"- Main improvement is the faster sorting algorithm. The browser sorts much quickly and works flawlessly when there are a lot of files open (order of 200), especially when the MRU is selected. Still more can be done to imrove the sorting speed.\r\n- When the browser window is opened, a message is generated with the total number of buffers and number of buffers shown.\r\n- Cleaned up a lot of stuff. Now the impact of the browser on the user environment is much less as it avoids cluttering search history and restores the unnamed register.","3":"- Main improvement is the faster sorting algorithm. The browser sorts much quickly and works flawlessly when there are a lot of files open (order of 200), especially when the MRU is selected. Still more can be done to imrove the sorting speed.\r\n- When the browser window is opened, a message is generated with the total number of buffers and number of buffers shown.\r\n- Cleaned up a lot of stuff. Now the impact of the browser on the user environment is much less as it avoids cluttering search history and restores the unnamed register.","package":"selectbuf.vim","4":"selectbuf.vim","src_id":"611","5":"611","creation_date":"1014078442","6":"1014078442"},{"0":"107","vim_version":"6.0","1":"6.0","script_version":"2.2.3","2":"2.2.3","version_comment":"Fixed the \"myBufNr\" not defined error reported by Halim Salman.\r\n","3":"Fixed the \"myBufNr\" not defined error reported by Halim Salman.\r\n","package":"selectbuf.vim","4":"selectbuf.vim","src_id":"542","5":"542","creation_date":"1012821235","6":"1012821235"},{"0":"107","vim_version":"6.0","1":"6.0","script_version":"2.2.2","2":"2.2.2","version_comment":"I have finally added MRU soring support with the popular demand :) \r\n\r\n- Now you can specify the sorting method to be by MRU files. To make mru the default order, place this line in your vimrc: \r\n\r\nlet g:selBufDefaultSortOrder = \"mru\" \r\n\r\nYou can also use SBBufToHead and SBBufToTail commands with a buffer number argument to move the specified buffer to the starting and ending of the MRU list. \r\n\r\n- If you make any changes to the configuration, you can use the new command SBInitialize to reconfigure the internal data of selectbuf.vim. \r\n\r\n- Fixed some misc. bugs. \r\n- FIxed the broken save\/restore window settings (after converting to 6.0). Now even the vertically split windows are restored correctly. \r\n\r\nNote that you need the new improved script genutils.vim instead of the older bufNwinUtils.vim. Download it from \r\n\r\nhttp:\/\/vim.sourceforge.net\/scripts\/script.php?script_id=197 \r\n\r\nAlso you need the new improved multvals.vim instead of the older lightWeightArray.vim. Download it from:\r\n\r\nhttp:\/\/vim.sourceforge.net\/scripts\/script.php?script_id=171","3":"I have finally added MRU soring support with the popular demand :) \r\n\r\n- Now you can specify the sorting method to be by MRU files. To make mru the default order, place this line in your vimrc: \r\n\r\nlet g:selBufDefaultSortOrder = \"mru\" \r\n\r\nYou can also use SBBufToHead and SBBufToTail commands with a buffer number argument to move the specified buffer to the starting and ending of the MRU list. \r\n\r\n- If you make any changes to the configuration, you can use the new command SBInitialize to reconfigure the internal data of selectbuf.vim. \r\n\r\n- Fixed some misc. bugs. \r\n- FIxed the broken save\/restore window settings (after converting to 6.0). Now even the vertically split windows are restored correctly. \r\n\r\nNote that you need the new improved script genutils.vim instead of the older bufNwinUtils.vim. Download it from \r\n\r\nhttp:\/\/vim.sourceforge.net\/scripts\/script.php?script_id=197 \r\n\r\nAlso you need the new improved multvals.vim instead of the older lightWeightArray.vim. Download it from:\r\n\r\nhttp:\/\/vim.sourceforge.net\/scripts\/script.php?script_id=171","package":"selectbuf.vim","4":"selectbuf.vim","src_id":"528","5":"528","creation_date":"1012592030","6":"1012592030"},{"0":"107","vim_version":"6.0","1":"6.0","script_version":"2.1.11","2":"2.1.11","version_comment":"- New feature to bulk delete\/wipeout multiple buffers by selecting the rows.\r\n  Very useful when you load a bunch of files by mistake and you just want to\r\n  delete all the buffers at once. You can also sort by type and select all the\r\n  buffers of a particular type and delete\/wipeout at once.\r\n- Complete configurability of the key mappings for all the commands. You can\r\n  define your own key mappings for all the actions, or just for those that you\r\n  don't like the default key assignment. E.g., I don't like to use \"?\" for\r\n  showing the help (though it is more intuitive), as it disables my ability to\r\n  search backwards in the browser window. So I changed the assignment by\r\n  putting the following line in .vimrc\r\n\r\n        noremap <silent> <Plug>SelBufHelpKey <C-H>\r\n\r\n  The ? key is now freed and I can use ^H instead to toggle help header.\r\n","3":"- New feature to bulk delete\/wipeout multiple buffers by selecting the rows.\r\n  Very useful when you load a bunch of files by mistake and you just want to\r\n  delete all the buffers at once. You can also sort by type and select all the\r\n  buffers of a particular type and delete\/wipeout at once.\r\n- Complete configurability of the key mappings for all the commands. You can\r\n  define your own key mappings for all the actions, or just for those that you\r\n  don't like the default key assignment. E.g., I don't like to use \"?\" for\r\n  showing the help (though it is more intuitive), as it disables my ability to\r\n  search backwards in the browser window. So I changed the assignment by\r\n  putting the following line in .vimrc\r\n\r\n        noremap <silent> <Plug>SelBufHelpKey <C-H>\r\n\r\n  The ? key is now freed and I can use ^H instead to toggle help header.\r\n","package":"selectbuf.vim","4":"selectbuf.vim","src_id":"353","5":"353","creation_date":"1005847929","6":"1005847929"},{"0":"107","vim_version":"6.0","1":"6.0","script_version":"2.1.10","2":"2.1.10","version_comment":"I am making this a 2.1 release version after a good amount of usage for the past\r\nfew weeks. Here is a final summary of all the new features in this release:\r\n\r\n    - help header with a status line\r\n    - open\/close browser using the same key (to get a quick glance of the files)\r\n    - optionally show buffer indicators\r\n    - show\/hide hidden buffers\r\n    - separate delete and wipeout functionality\r\n    - refresh browser\r\n    - show\/hide path info\r\n    - buffer markers for easy navigation\r\n    - most of the features are configurable\r\n    - avoid cluttering the global name space with the config variables\r\n    - sort\/reverse sort by \"buffer nubmer\", \"name\", \"path\", \"type\", \"indicators\"\r\n    - must better syntax highlighting (configurable)\r\n    - optionally open a vertical window for the browser\r\n    - three operating modes for the browser\r\n        - split: standard style, split opens the browser window\r\n        - switch: reuse the current window (bufexplorer style)\r\n        - keep: keep browser always open. Very useful when used with the\r\n                previous option to open a vertically split window.\r\n\r\n    Requires 1.0.3 bufNwinUtils.vim.\r\n\r\nPlease keep sending bug reports\/suggestions\/comments etc.\r\n","3":"I am making this a 2.1 release version after a good amount of usage for the past\r\nfew weeks. Here is a final summary of all the new features in this release:\r\n\r\n    - help header with a status line\r\n    - open\/close browser using the same key (to get a quick glance of the files)\r\n    - optionally show buffer indicators\r\n    - show\/hide hidden buffers\r\n    - separate delete and wipeout functionality\r\n    - refresh browser\r\n    - show\/hide path info\r\n    - buffer markers for easy navigation\r\n    - most of the features are configurable\r\n    - avoid cluttering the global name space with the config variables\r\n    - sort\/reverse sort by \"buffer nubmer\", \"name\", \"path\", \"type\", \"indicators\"\r\n    - must better syntax highlighting (configurable)\r\n    - optionally open a vertical window for the browser\r\n    - three operating modes for the browser\r\n        - split: standard style, split opens the browser window\r\n        - switch: reuse the current window (bufexplorer style)\r\n        - keep: keep browser always open. Very useful when used with the\r\n                previous option to open a vertically split window.\r\n\r\n    Requires 1.0.3 bufNwinUtils.vim.\r\n\r\nPlease keep sending bug reports\/suggestions\/comments etc.\r\n","package":"selectbuf.vim","4":"selectbuf.vim","src_id":"329","5":"329","creation_date":"1005259832","6":"1005259832"},{"0":"107","vim_version":"6.0","1":"6.0","script_version":"2.1beta9","2":"2.1beta9","version_comment":"Forgot to mention that you require the latest bufNwinUtils.vim. Download it: http:\/\/vim.sourceforge.net\/scripts\/script.php?script_id=108 \r\n","3":"Forgot to mention that you require the latest bufNwinUtils.vim. Download it: http:\/\/vim.sourceforge.net\/scripts\/script.php?script_id=108 \r\n","package":"selectbuf.vim","4":"selectbuf.vim","src_id":"318","5":"318","creation_date":"1004964965","6":"1004964965"},{"0":"107","vim_version":"6.0","1":"6.0","script_version":"2.1beta9","2":"2.1beta9","version_comment":"I have added most of the features that I wanted to, and also fixed all the FIXME's. So the script is now mostly clean and very stable.\r\n\r\n- Now sort by name and sort by path are separate.\r\n- Fixed the bug in remembering the cursor position.\r\n- More configurability of the script. Fix for avoiding the global config params from cluttering the global namespace.\r\n- You can specify a default sort order.\r\n- Syntax coloring in the browser window is much better now.\r\n- Added P command to show\/hide paths.\r\n- Improved stability.\r\n\r\nIt is very close to a release version now.","3":"I have added most of the features that I wanted to, and also fixed all the FIXME's. So the script is now mostly clean and very stable.\r\n\r\n- Now sort by name and sort by path are separate.\r\n- Fixed the bug in remembering the cursor position.\r\n- More configurability of the script. Fix for avoiding the global config params from cluttering the global namespace.\r\n- You can specify a default sort order.\r\n- Syntax coloring in the browser window is much better now.\r\n- Added P command to show\/hide paths.\r\n- Improved stability.\r\n\r\nIt is very close to a release version now.","package":"selectbuf.vim","4":"selectbuf.vim","src_id":"317","5":"317","creation_date":"1004964774","6":"1004964774"},{"0":"107","vim_version":"6.0","1":"6.0","script_version":"2.1beta6","2":"2.1beta6","version_comment":"Added some cool new features and fixed some problems.\r\n\r\n- Added sorting. You can now sort by \"buffer number\", \"name\", \"type\" or by \"indicators\".\r\n  - Use s to select the sort type forward.\r\n  - Use S to select the sort type backward.\r\n  - Use r to sort in the reverse order.\r\n  - Since r is more appropriate (and familiar) for reverse sorting, I used R to refresh the browser.\r\n- I got the solution for the toggling the meaning of activation key, so now you can use the same key that activates the browser to even close it. So provided you have <F3> mapped, you can have a quick look at the browser by pressing <F3> twice in quick succession.\r\n- I also used some nice 6.0 features to make the browser buffer more friendly.\r\n- Fixed the spurious nomodifiable problem (happens occassionally). Thanks for reporting this problem.\r\n","3":"Added some cool new features and fixed some problems.\r\n\r\n- Added sorting. You can now sort by \"buffer number\", \"name\", \"type\" or by \"indicators\".\r\n  - Use s to select the sort type forward.\r\n  - Use S to select the sort type backward.\r\n  - Use r to sort in the reverse order.\r\n  - Since r is more appropriate (and familiar) for reverse sorting, I used R to refresh the browser.\r\n- I got the solution for the toggling the meaning of activation key, so now you can use the same key that activates the browser to even close it. So provided you have <F3> mapped, you can have a quick look at the browser by pressing <F3> twice in quick succession.\r\n- I also used some nice 6.0 features to make the browser buffer more friendly.\r\n- Fixed the spurious nomodifiable problem (happens occassionally). Thanks for reporting this problem.\r\n","package":"selectbuf.vim","4":"selectbuf.vim","src_id":"307","5":"307","creation_date":"1004121472","6":"1004121472"},{"0":"107","vim_version":"6.0","1":"6.0","script_version":"2.1beta3","2":"2.1beta3","version_comment":"Added the following useful features:\r\n\r\n- Optionally hide fileexplorer buffers.\r\n- Undelete (relist) buffers.\r\n- show status line with the current settings.\r\n","3":"Added the following useful features:\r\n\r\n- Optionally hide fileexplorer buffers.\r\n- Undelete (relist) buffers.\r\n- show status line with the current settings.\r\n","package":"selectbuf.vim","4":"selectbuf.vim","src_id":"300","5":"300","creation_date":"1003849479","6":"1003849479"},{"0":"107","vim_version":"6.0","1":"6.0","script_version":"2.1beta2","2":"2.1beta2","version_comment":"I got a nice feedback from a few people that mapping cursor movement commands for functionality is asking for trouble. Since w, W, h and H are cursor movement commands, before it is too late, I changed the key mappings as follows:\r\n\r\nDelete buffer: d from D\r\nWipeout buffer: D from W \r\nToggle hidden: u from H (u for unlisted)\r\nToggle wrap: p from w\r\nToggle help: ? from h\r\n\r\nNow you shouldn't see many surprises when you follow your natural instincts to move cursor :)\r\nPlease continue to give feedback. Thank you.\r\n","3":"I got a nice feedback from a few people that mapping cursor movement commands for functionality is asking for trouble. Since w, W, h and H are cursor movement commands, before it is too late, I changed the key mappings as follows:\r\n\r\nDelete buffer: d from D\r\nWipeout buffer: D from W \r\nToggle hidden: u from H (u for unlisted)\r\nToggle wrap: p from w\r\nToggle help: ? from h\r\n\r\nNow you shouldn't see many surprises when you follow your natural instincts to move cursor :)\r\nPlease continue to give feedback. Thank you.\r\n","package":"selectbuf.vim","4":"selectbuf.vim","src_id":"292","5":"292","creation_date":"1003514031","6":"1003514031"},{"0":"107","vim_version":"6.0","1":"6.0","script_version":"2.1beta1","2":"2.1beta1","version_comment":"Some nice improvements.\r\n- help header (can be toggled)\r\n- buffer indicators on the lines of :ls (can be toggled)\r\n- show hidden buffers (can be toggled)\r\n- Separate delete and wipeout functionality for buffers\r\n- refresh browser (without reopening) .\r\n- buffer markers to easily navigate.\r\n- more robust.\r\n- more configurability.\r\n\r\nIt is still beta, but I have done quite a lot of testing and it seems to be stable. I would appreciate any bug reports and feedback. I have more ideas for some good features to come soon, but if you would like to see any features yourself, please let me know.\r\n\r\nYou need the 1.0.1 version of bufNwinUtils.vim","3":"Some nice improvements.\r\n- help header (can be toggled)\r\n- buffer indicators on the lines of :ls (can be toggled)\r\n- show hidden buffers (can be toggled)\r\n- Separate delete and wipeout functionality for buffers\r\n- refresh browser (without reopening) .\r\n- buffer markers to easily navigate.\r\n- more robust.\r\n- more configurability.\r\n\r\nIt is still beta, but I have done quite a lot of testing and it seems to be stable. I would appreciate any bug reports and feedback. I have more ideas for some good features to come soon, but if you would like to see any features yourself, please let me know.\r\n\r\nYou need the 1.0.1 version of bufNwinUtils.vim","package":"selectbuf.vim","4":"selectbuf.vim","src_id":"289","5":"289","creation_date":"1003425198","6":"1003425198"},{"0":"107","vim_version":"6.0","1":"6.0","script_version":"2.0.3","2":"2.0.3","version_comment":"Removed the ^M's.","3":"Removed the ^M's.","package":"selectbuf.vim","4":"selectbuf.vim","src_id":"262","5":"262","creation_date":"1002721285","6":"1002721285"},{"0":"107","vim_version":"6.0","1":"6.0","script_version":"2.0.2","2":"2.0.2","version_comment":"While converting the script to 6.0, lost the hack that restores search history when the browser is closed. ","3":"While converting the script to 6.0, lost the hack that restores search history when the browser is closed. ","package":"selectbuf.vim","4":"selectbuf.vim","src_id":"248","5":"248","creation_date":"1002563058","6":"1002563058"},{"0":"107","vim_version":"6.0","1":"6.0","script_version":"","2":"","version_comment":"Initial upload","3":"Initial upload","package":"selectbuf.vim","4":"selectbuf.vim","src_id":"240","5":"240","creation_date":"1002307747","6":"1002307747"}]},"106":{"script_id":"106","0":"106","script_name":"colorscheme_template.vim","1":"colorscheme_template.vim","script_type":"color scheme","2":"color scheme","summary":"A template to make coming up with your own color scheme a bit easier.","3":"A template to make coming up with your own color scheme a bit easier.","description":"The philosophy here is to provide a ready-to-uncomment list of highlight commands for all the important groups.  Then you can deviate from the default until you come up with one you like.","4":"The philosophy here is to provide a ready-to-uncomment list of highlight commands for all the important groups.  Then you can deviate from the default until you come up with one you like.","install_details":"Copy to ~\/.vim\/colors\/<myscheme>.vim where <myscheme> is the name of your color scheme.  Edit to your heart's content.","5":"Copy to ~\/.vim\/colors\/<myscheme>.vim where <myscheme> is the name of your color scheme.  Edit to your heart's content.","first_name":"Hans","6":"Hans","last_name":"Fugal","7":"Fugal","releases":[{"0":"106","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"colorscheme_template.vim","4":"colorscheme_template.vim","src_id":"239","5":"239","creation_date":"1002304518","6":"1002304518"}]},"105":{"script_id":"105","0":"105","script_name":"desert.vim","1":"desert.vim","script_type":"color scheme","2":"color scheme","summary":"A dark-background color scheme inspired by my hometown of Santa Fe, New Mexico","3":"A dark-background color scheme inspired by my hometown of Santa Fe, New Mexico","description":"I started with the evening colorscheme included in the distro, and tweaked a few colors to my liking.  Then I decided to do a major overhaul and give the whole thing a desert evening sort of feel.  I find it a very pleasing, easy-on-the-eyes theme.  \r\n\r\nScreenshot: http:\/\/hans.fugal.net\/vim\/colors\/desert.html\r\n\r\nUpdate: now on github for your forking pleasure. The version I uploaded there is probably slightly different than the version I last uploaded here.","4":"I started with the evening colorscheme included in the distro, and tweaked a few colors to my liking.  Then I decided to do a major overhaul and give the whole thing a desert evening sort of feel.  I find it a very pleasing, easy-on-the-eyes theme.  \r\n\r\nScreenshot: http:\/\/hans.fugal.net\/vim\/colors\/desert.html\r\n\r\nUpdate: now on github for your forking pleasure. The version I uploaded there is probably slightly different than the version I last uploaded here.","install_details":"Get the latest version at https:\/\/github.com\/fugalh\/desert.vim\r\nPut in ~\/.vim\/colors or (<your-vim-dir>\\vimfiles\\colors on Windows) and do \r\n:colorscheme desert\r\n\r\nYou can probably use it with vim 5.x if you want to try sourcing it from your .vimrc and perhaps debugging\/deleting some stuff (non-essential for this kind of usage)","5":"Get the latest version at https:\/\/github.com\/fugalh\/desert.vim\r\nPut in ~\/.vim\/colors or (<your-vim-dir>\\vimfiles\\colors on Windows) and do \r\n:colorscheme desert\r\n\r\nYou can probably use it with vim 5.x if you want to try sourcing it from your .vimrc and perhaps debugging\/deleting some stuff (non-essential for this kind of usage)","first_name":"Hans","6":"Hans","last_name":"Fugal","7":"Fugal","releases":[{"0":"105","vim_version":"6.0","1":"6.0","script_version":"1.2","2":"1.2","version_comment":"Minor cterm changes. (folding and Ignore)","3":"Minor cterm changes. (folding and Ignore)","package":"desert.vim","4":"desert.vim","src_id":"2038","5":"2038","creation_date":"1054557392","6":"1054557392"},{"0":"105","vim_version":"6.0","1":"6.0","script_version":"1.1","2":"1.1","version_comment":"Overhauled the cterm colors. No gui changes.","3":"Overhauled the cterm colors. No gui changes.","package":"desert.vim","4":"desert.vim","src_id":"1005","5":"1005","creation_date":"1026236805","6":"1026236805"},{"0":"105","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"desert.vim","4":"desert.vim","src_id":"238","5":"238","creation_date":"1002302688","6":"1002302688"}]},"104":{"script_id":"104","0":"104","script_name":"BlockHL","1":"BlockHL","script_type":"syntax","2":"syntax","summary":"highlighting different levels of {} in C","3":"highlighting different levels of {} in C","description":"Blockhl.vim supports block-oriented highlighting of leading white space for C\/C++.\r\n\r\nFor dark backgrounds, as one gets deeper into curly braces, the leading indentation will change to ever lighter colors (up to 7 such levels, then it cycles).\r\n\r\nFor light backgrounds, increasing curly brace depths will cause ever darker colors to be used (again, 7 levels).\r\n\r\nYou will need to source the <blockhl.vim> file in if you change colorschemes.\r\n\r\n\tRequired: gvim\r\n\r\n(alpha\/beta version available at http:\/\/www.drchip.org\/astronaut\/vim\/index.html#BLOCKHL)\r\n","4":"Blockhl.vim supports block-oriented highlighting of leading white space for C\/C++.\r\n\r\nFor dark backgrounds, as one gets deeper into curly braces, the leading indentation will change to ever lighter colors (up to 7 such levels, then it cycles).\r\n\r\nFor light backgrounds, increasing curly brace depths will cause ever darker colors to be used (again, 7 levels).\r\n\r\nYou will need to source the <blockhl.vim> file in if you change colorschemes.\r\n\r\n\tRequired: gvim\r\n\r\n(alpha\/beta version available at http:\/\/www.drchip.org\/astronaut\/vim\/index.html#BLOCKHL)\r\n","install_details":"1. In your <.vimrc> you'll need\r\n   filetype plugin on\r\n\r\n2. Put the <blockhl.vim> file into:\r\n    .vim\/after\/syntax\/c.vim\r\n-or-\r\n2. put the <blockhl.vim> file into\r\n   .vim\/after\/syntax\/c\/\r\n   and use vimscript#1023\r\n\r\nvimscript#1023 also contains some help for non-Unix users\r\n\r\n\r\n","5":"1. In your <.vimrc> you'll need\r\n   filetype plugin on\r\n\r\n2. Put the <blockhl.vim> file into:\r\n    .vim\/after\/syntax\/c.vim\r\n-or-\r\n2. put the <blockhl.vim> file into\r\n   .vim\/after\/syntax\/c\/\r\n   and use vimscript#1023\r\n\r\nvimscript#1023 also contains some help for non-Unix users\r\n\r\n\r\n","first_name":"Charles","6":"Charles","last_name":"Campbell","7":"Campbell","releases":[{"0":"104","vim_version":"6.0","1":"6.0","script_version":"4","2":"4","version_comment":"optionally supports entire-line rather than just leading whitespace\r\nuses cursorhold to restore highlighting after a colorscheme change\r\nbugfix: an ALLBUT in cParen caused cCurly7 to do inside-() highlighting.\r\n","3":"optionally supports entire-line rather than just leading whitespace\r\nuses cursorhold to restore highlighting after a colorscheme change\r\nbugfix: an ALLBUT in cParen caused cCurly7 to do inside-() highlighting.\r\n","package":"blockhl.vim.bz2","4":"blockhl.vim.bz2","src_id":"3201","5":"3201","creation_date":"1088693010","6":"1088693010"},{"0":"104","vim_version":"6.0","1":"6.0","script_version":"3","2":"3","version_comment":"Blockhl now tailors its C block-highlighting based on the user's background setting (light versus dark).","3":"Blockhl now tailors its C block-highlighting based on the user's background setting (light versus dark).","package":"blockhl.vim.bz2","4":"blockhl.vim.bz2","src_id":"3197","5":"3197","creation_date":"1088594387","6":"1088594387"}]},"103":{"script_id":"103","0":"103","script_name":"regview.vim","1":"regview.vim","script_type":"utility","2":"utility","summary":"Interactively browse register contents","3":"Interactively browse register contents","description":"This global plugin allows interactive browsing of register\r\ncontents.  It also allows pasting or executing the contents of\r\nthe currently viewed register. ","4":"This global plugin allows interactive browsing of register\r\ncontents.  It also allows pasting or executing the contents of\r\nthe currently viewed register. ","install_details":"Just drop into your plugin directory.\r\n\r\nAlso requires Johannes Zellner's ScratchBuffer.vim plugin, which is\r\navailable from http:\/\/www.zellner.org\/vim\/plugin\/ScratchBuffer.vim\r\n","5":"Just drop into your plugin directory.\r\n\r\nAlso requires Johannes Zellner's ScratchBuffer.vim plugin, which is\r\navailable from http:\/\/www.zellner.org\/vim\/plugin\/ScratchBuffer.vim\r\n","first_name":"Cory","6":"Cory","last_name":"Echols","7":"Echols","releases":[{"0":"103","vim_version":"6.0","1":"6.0","script_version":"0.9","2":"0.9","version_comment":"Initial upload","3":"Initial upload","package":"regview.vim","4":"regview.vim","src_id":"230","5":"230","creation_date":"1002092669","6":"1002092669"}]},"102":{"script_id":"102","0":"102","script_name":"DirDiff.vim","1":"DirDiff.vim","script_type":"utility","2":"utility","summary":"A plugin to diff and merge two directories recursively.","3":"A plugin to diff and merge two directories recursively.","description":"This is a utility that performs a recursive diff on two directories and generate a diff \"window\".  Based on that window you can perform various diff operations such as opening two files in Vim's diff mode, copy the file or directory recursively to the other, or remove the directory tree from the source directory.","4":"This is a utility that performs a recursive diff on two directories and generate a diff \"window\".  Based on that window you can perform various diff operations such as opening two files in Vim's diff mode, copy the file or directory recursively to the other, or remove the directory tree from the source directory.","install_details":"  The preferred way now to install DirDiff is to use a pathogen like tools.  The GitHub repo is at:\r\n  \r\n  https:\/\/github.com\/will133\/vim-dirdiff.\r\n\r\n  Alternatively, you can unzip the .zip file in your ~\/.vim\/ directory and run :helptags to generate your documentation.\r\n\r\n  Doing the following will generate a diff window.\r\n\r\n      :DirDiff <A:Src Directory> <B:Src Directory>\r\n  e.g.\r\n      :DirDiff ..\/something\/dir1 \/usr\/bin\/somethingelse\/dir2\r\n\r\n  The following commands can be used inside the diff window:\r\n  'Enter','o' - Diff open: open the diff file(s) where your cursor is at\r\n  's' - Synchronize the current diff.  You can also select\r\n        a range (through visual) and press 's' to synchronize differences\r\n        across a range.\r\n\r\n        - There are 6 Options you can choose when you hit 's':\r\n          1. A -> B\r\n             Copy A to overwrite B\r\n             If A's file actually points to a directory, it'll copy it to B\r\n             recursively.\r\n          2. B -> A\r\n             Copy B to overwrite A\r\n             If B's file actually points to a directory, it'll copy it to A\r\n             recursively.\r\n          3. Always A\r\n             For the rest of the items that you've selected,\r\n             synchronize like (1).\r\n          4. Always B\r\n             For the rest of the items that you've selected,\r\n             synchronize like (2).\r\n          5. Skip\r\n             Skip this diff entry.\r\n          6. Cancel\r\n             Quit the loop and exit.\r\n\r\n  'u' - Diff update: update the diff window\r\n  'x' - Sets the exclude pattern, separated by ','\r\n  'i' - Sets the ignore pattern, separated by ','\r\n  'a' - Sets additional arguments for diff, eg. -w to ignore white space,\r\n        etc.\r\n  'q' - Quit DirDiff\r\n   \r\n  The following comamnds can be used in the Vim diff mode\r\n  \\dg - Diff get: maps to :diffget<CR>\r\n  \\dp - Diff put: maps to :diffput<CR>\r\n  \\dj - Diff next: (think j for down) \r\n  \\dk - Diff previous: (think k for up)\r\n\r\n  You can set the following DirDiff variables.  You can add the following\r\n  \"let\" lines in your .vimrc file.\r\n\r\n  Sets default exclude pattern:\r\n      let g:DirDiffExcludes = \"CVS,*.class,*.exe,.*.swp\"\r\n\r\n  Sets default ignore pattern:\r\n      let g:DirDiffIgnore = \"Id:,Revision:,Date:\"\r\n\r\n  If DirDiffSort is set to 1, sorts the diff lines.\r\n      let g:DirDiffSort = 1\r\n\r\n  Sets the diff window (bottom window) height (rows)\r\n      let g:DirDiffWindowSize = 14\r\n\r\n  Ignore case during diff\r\n      let g:DirDiffIgnoreCase = 0\r\n\r\n  Dynamically figure out the diff text.  If you are using and i18n version\r\n  of diff, this will try to get the specific diff text during runtime.  It's\r\n  turned off by default.  If you are always targetting a specific version of\r\n  diff, you can turn this off and set the DirDiffText* variables\r\n  accordingly.\r\n      let g:DirDiffDynamicDiffText = 0\r\n\r\n  String used for the English equivalent \"Files \"\r\n      let g:DirDiffTextFiles = \"Files \"\r\n\r\n  String used for the English equivalent \" and \"\r\n      let g:DirDiffTextAnd = \" and \"\r\n\r\n  String used for the English equivalent \" differ\")\r\n      let g:DirDiffTextDiffer = \" differ\"\r\n\r\n  String used for the English equivalent \"Only in \")\r\n      let g:DirDiffTextOnlyIn = \"Only in \"\r\n\r\n","5":"  The preferred way now to install DirDiff is to use a pathogen like tools.  The GitHub repo is at:\r\n  \r\n  https:\/\/github.com\/will133\/vim-dirdiff.\r\n\r\n  Alternatively, you can unzip the .zip file in your ~\/.vim\/ directory and run :helptags to generate your documentation.\r\n\r\n  Doing the following will generate a diff window.\r\n\r\n      :DirDiff <A:Src Directory> <B:Src Directory>\r\n  e.g.\r\n      :DirDiff ..\/something\/dir1 \/usr\/bin\/somethingelse\/dir2\r\n\r\n  The following commands can be used inside the diff window:\r\n  'Enter','o' - Diff open: open the diff file(s) where your cursor is at\r\n  's' - Synchronize the current diff.  You can also select\r\n        a range (through visual) and press 's' to synchronize differences\r\n        across a range.\r\n\r\n        - There are 6 Options you can choose when you hit 's':\r\n          1. A -> B\r\n             Copy A to overwrite B\r\n             If A's file actually points to a directory, it'll copy it to B\r\n             recursively.\r\n          2. B -> A\r\n             Copy B to overwrite A\r\n             If B's file actually points to a directory, it'll copy it to A\r\n             recursively.\r\n          3. Always A\r\n             For the rest of the items that you've selected,\r\n             synchronize like (1).\r\n          4. Always B\r\n             For the rest of the items that you've selected,\r\n             synchronize like (2).\r\n          5. Skip\r\n             Skip this diff entry.\r\n          6. Cancel\r\n             Quit the loop and exit.\r\n\r\n  'u' - Diff update: update the diff window\r\n  'x' - Sets the exclude pattern, separated by ','\r\n  'i' - Sets the ignore pattern, separated by ','\r\n  'a' - Sets additional arguments for diff, eg. -w to ignore white space,\r\n        etc.\r\n  'q' - Quit DirDiff\r\n   \r\n  The following comamnds can be used in the Vim diff mode\r\n  \\dg - Diff get: maps to :diffget<CR>\r\n  \\dp - Diff put: maps to :diffput<CR>\r\n  \\dj - Diff next: (think j for down) \r\n  \\dk - Diff previous: (think k for up)\r\n\r\n  You can set the following DirDiff variables.  You can add the following\r\n  \"let\" lines in your .vimrc file.\r\n\r\n  Sets default exclude pattern:\r\n      let g:DirDiffExcludes = \"CVS,*.class,*.exe,.*.swp\"\r\n\r\n  Sets default ignore pattern:\r\n      let g:DirDiffIgnore = \"Id:,Revision:,Date:\"\r\n\r\n  If DirDiffSort is set to 1, sorts the diff lines.\r\n      let g:DirDiffSort = 1\r\n\r\n  Sets the diff window (bottom window) height (rows)\r\n      let g:DirDiffWindowSize = 14\r\n\r\n  Ignore case during diff\r\n      let g:DirDiffIgnoreCase = 0\r\n\r\n  Dynamically figure out the diff text.  If you are using and i18n version\r\n  of diff, this will try to get the specific diff text during runtime.  It's\r\n  turned off by default.  If you are always targetting a specific version of\r\n  diff, you can turn this off and set the DirDiffText* variables\r\n  accordingly.\r\n      let g:DirDiffDynamicDiffText = 0\r\n\r\n  String used for the English equivalent \"Files \"\r\n      let g:DirDiffTextFiles = \"Files \"\r\n\r\n  String used for the English equivalent \" and \"\r\n      let g:DirDiffTextAnd = \" and \"\r\n\r\n  String used for the English equivalent \" differ\")\r\n      let g:DirDiffTextDiffer = \" differ\"\r\n\r\n  String used for the English equivalent \"Only in \")\r\n      let g:DirDiffTextOnlyIn = \"Only in \"\r\n\r\n","first_name":"William","6":"William","last_name":"Lee","7":"Lee","releases":[{"0":"102","vim_version":"7.0","1":"7.0","script_version":"1.1.5","2":"1.1.5","version_comment":"Added pathogen support.  Disable the default <Leader> mapping.  You can turn those mappings on if you set g:DirDiffEnableMappings = 1.  Fixed couple of screen refresh bugs and remove bogus error messages.","3":"Added pathogen support.  Disable the default <Leader> mapping.  You can turn those mappings on if you set g:DirDiffEnableMappings = 1.  Fixed couple of screen refresh bugs and remove bogus error messages.","package":"dirdiff.zip","4":"dirdiff.zip","src_id":"22871","5":"22871","creation_date":"1423112953","6":"1423112953"},{"0":"102","vim_version":"7.0","1":"7.0","script_version":"1.1.4","2":"1.1.4","version_comment":"Minor fix for failing to split open the diff buffers for certain .vimrc settings","3":"Minor fix for failing to split open the diff buffers for certain .vimrc settings","package":"DirDiff.vim","4":"DirDiff.vim","src_id":"16171","5":"16171","creation_date":"1311946296","6":"1311946296"},{"0":"102","vim_version":"7.0","1":"7.0","script_version":"1.1.3","2":"1.1.3","version_comment":"Added Wu WeiWei patch for making DirDiff work for Chinese diff.","3":"Added Wu WeiWei patch for making DirDiff work for Chinese diff.","package":"DirDiff.vim","4":"DirDiff.vim","src_id":"13435","5":"13435","creation_date":"1280462200","6":"1280462200"},{"0":"102","vim_version":"7.0","1":"7.0","script_version":"1.1.2","2":"1.1.2","version_comment":"The last version was a bad release.  This contains the right patch instead.","3":"The last version was a bad release.  This contains the right patch instead.","package":"DirDiff.vim","4":"DirDiff.vim","src_id":"9375","5":"9375","creation_date":"1224511514","6":"1224511514"},{"0":"102","vim_version":"7.0","1":"7.0","script_version":"1.1.1","2":"1.1.1","version_comment":"Note that this version requires vim 7.2.  This fixed a bug where spaces in the filename is not handled correctly.","3":"Note that this version requires vim 7.2.  This fixed a bug where spaces in the filename is not handled correctly.","package":"DirDiff.vim","4":"DirDiff.vim","src_id":"9364","5":"9364","creation_date":"1224257573","6":"1224257573"},{"0":"102","vim_version":"6.0","1":"6.0","script_version":"1.1.0","2":"1.1.0","version_comment":"Added support for non-English version of diff.  Thanks to Florian Delizy.  Release under a FreeBSD-like license.  ","3":"Added support for non-English version of diff.  Thanks to Florian Delizy.  Release under a FreeBSD-like license.  ","package":"DirDiff.vim","4":"DirDiff.vim","src_id":"5306","5":"5306","creation_date":"1140640423","6":"1140640423"},{"0":"102","vim_version":"6.0","1":"6.0","script_version":"1.0.2","2":"1.0.2","version_comment":"Fixed a small bug in the quit routine.","3":"Fixed a small bug in the quit routine.","package":"DirDiff.vim","4":"DirDiff.vim","src_id":"2440","5":"2440","creation_date":"1067579696","6":"1067579696"},{"0":"102","vim_version":"6.0","1":"6.0","script_version":"1.0.1","2":"1.0.1","version_comment":"Fixed a reported path separator problem in W2K.","3":"Fixed a reported path separator problem in W2K.","package":"DirDiff.vim","4":"DirDiff.vim","src_id":"2432","5":"2432","creation_date":"1067409040","6":"1067409040"},{"0":"102","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Latest stable version.  Fixed a bug where error message may appear if you set the nowrapscan option.  Add a quit option to close the diff windows.","3":"Latest stable version.  Fixed a bug where error message may appear if you set the nowrapscan option.  Add a quit option to close the diff windows.","package":"DirDiff.vim","4":"DirDiff.vim","src_id":"322","5":"322","creation_date":"1005120872","6":"1005120872"}]},"101":{"script_id":"101","0":"101","script_name":"nlist.vim","1":"nlist.vim","script_type":"utility","2":"utility","summary":"Vim global plugin for adding line numbers","3":"Vim global plugin for adding line numbers","description":"Description:\nThis provides a command and a function.  They both can be called with or\nwithout a range.  In addition, they can be called with or without arguments.\nWithout a range they operate on the current line.  The arguments are described\nbelow:\n\n    arg1 -> the number to start at.  The default is one.  This will\n            number your selected lines sequentially.  The start can be a\n            number, ., $, or, 'x (like getline).\n    arg2 -> Text to append after numbers.  The default is a space.\n    arg3 -> Controls formatting.  Can be \"left\", \"right\", or \"none\".  The\n            default is \"right\".\n\nExamples:\n    To make a list start at 1:\n        :'<,'>Nlist\n        :'<,'>call Nlist()\n    To number the whole buffer (with it's actual line number):\n        :%Nlist\n        :%call Nlist()\n    To number a subset of lines with their line number (and put a '] ' in\n    front of every number):\n        :'<,'>Nlist . ]\\\n        :'<,'>call Nlist(\".\", \"] \")\n    To number the whole buffer (with it's actual line number) without\n    justification:\n        :%Nlist 1 \\ left\n        :%call Nlist(\"1\", \" \", \"none\")\n\nExample mappings that a user can define:\nnnoremap <unique> <Leader>N :%Nlist<cr>\nvnoremap <unique> <Leader>N :Nlist<cr>","4":"Description:\nThis provides a command and a function.  They both can be called with or\nwithout a range.  In addition, they can be called with or without arguments.\nWithout a range they operate on the current line.  The arguments are described\nbelow:\n\n    arg1 -> the number to start at.  The default is one.  This will\n            number your selected lines sequentially.  The start can be a\n            number, ., $, or, 'x (like getline).\n    arg2 -> Text to append after numbers.  The default is a space.\n    arg3 -> Controls formatting.  Can be \"left\", \"right\", or \"none\".  The\n            default is \"right\".\n\nExamples:\n    To make a list start at 1:\n        :'<,'>Nlist\n        :'<,'>call Nlist()\n    To number the whole buffer (with it's actual line number):\n        :%Nlist\n        :%call Nlist()\n    To number a subset of lines with their line number (and put a '] ' in\n    front of every number):\n        :'<,'>Nlist . ]\\\n        :'<,'>call Nlist(\".\", \"] \")\n    To number the whole buffer (with it's actual line number) without\n    justification:\n        :%Nlist 1 \\ left\n        :%call Nlist(\"1\", \" \", \"none\")\n\nExample mappings that a user can define:\nnnoremap <unique> <Leader>N :%Nlist<cr>\nvnoremap <unique> <Leader>N :Nlist<cr>","install_details":"cp ~\/.vim\/plugin","5":"cp ~\/.vim\/plugin","first_name":"brian","6":"brian","last_name":"medley","7":"medley","releases":[{"0":"101","vim_version":"6.0","1":"6.0","script_version":"2.0","2":"2.0","version_comment":"Alphabetic numbering like a b c .... y z aa ab ac added by Seib.","3":"Alphabetic numbering like a b c .... y z aa ab ac added by Seib.","package":"nlist.vim","4":"nlist.vim","src_id":"2125","5":"2125","creation_date":"1057169084","6":"1057169084"},{"0":"101","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"nlist.vim","4":"nlist.vim","src_id":"218","5":"218","creation_date":"1001974939","6":"1001974939"}]},"100":{"script_id":"100","0":"100","script_name":"TagsBase.zip","1":"TagsBase.zip","script_type":"utility","2":"utility","summary":"Creates a menu of tags (functions, fields...) keep track of the current function","3":"Creates a menu of tags (functions, fields...) keep track of the current function","description":"Tags Base started as the merge and enhancements of the scripts:\r\n *TagsMenu (http:\/\/members.home.net\/jayglanville\/tagsmenu\/TagsMenu.html) script\r\n \t\t    Jay Dickon Glanville  dickon@nortelnetworks.com\r\n\r\n *ctags.vim (http:\/\/vim.sourceforge.net\/scripts\/script.php?script_id=12) script\r\n \t\t\tAlexey Marinichev   lyosha@lyosha.2y.net\r\n see |TagsBase-Credits|\r\nIt now is a complete rewrite of those scripts plus additional functionality in embedded\r\nperl as well as some of the original vim code which is used to provide the same functionality\r\nwhen you are unlucky enough not to have access to the +perl or +perl\/dyn feature in\r\nyour vim build.\r\n\r\nTags Base automatically uses |ctags| to generate a |tag| file for the currently\r\nedited file, refreshes it if the file is newer than the tags file and uses it\r\nto provide a set of advanced feature to vim.\r\n\r\nBeware that this means that some tag files are left behind on your computer,\r\n\tthey may end up in the same directory as your files or in a temporary\r\n\tdirectory depending on the rights of the file directory. You can specify the\r\n\tprefixe and suffix used to compute those temporary files.  There is also\r\n                some options to cleanup those file, the default being of only cleaning up\r\n                the temp directory.\r\n\r\nRight now the feature provided are:\r\n    *Detection of the currently edited tag and its type and presentation of this information in the\r\n     title bar. Most of the time when editing a C\/C++\/java... file this means you have on the \r\n     title bar the name of the current function.     *Creation of a menu of tags in the file this \r\n     contains things such as method, function, class... the type of tags supported depends on \r\n     the current language and on the implementation of the |ctags| program\r\n\r\n    TagsBase manipulates all tags supported by |ctags|. (For the full list of\r\n    supported tags and attributes, see \"http:\/\/ctags.sourceforge.net\/\"\r\n\r\n\r\nAdditional description can be found in the included help file. This script requires a version 5.0 of ctags.\r\n\r\nThis script has also been used by me as a test bed for embedding perl in vim scripts specifically for\r\nperformance reasons since parsing a large set of tags can take a fair amount of time.\r\nFor this reason you'll find a couple fo files (TagsBase.pl and VIM.pm) which I use in the development\r\nprocess, to find out about this see vimtip #140","4":"Tags Base started as the merge and enhancements of the scripts:\r\n *TagsMenu (http:\/\/members.home.net\/jayglanville\/tagsmenu\/TagsMenu.html) script\r\n \t\t    Jay Dickon Glanville  dickon@nortelnetworks.com\r\n\r\n *ctags.vim (http:\/\/vim.sourceforge.net\/scripts\/script.php?script_id=12) script\r\n \t\t\tAlexey Marinichev   lyosha@lyosha.2y.net\r\n see |TagsBase-Credits|\r\nIt now is a complete rewrite of those scripts plus additional functionality in embedded\r\nperl as well as some of the original vim code which is used to provide the same functionality\r\nwhen you are unlucky enough not to have access to the +perl or +perl\/dyn feature in\r\nyour vim build.\r\n\r\nTags Base automatically uses |ctags| to generate a |tag| file for the currently\r\nedited file, refreshes it if the file is newer than the tags file and uses it\r\nto provide a set of advanced feature to vim.\r\n\r\nBeware that this means that some tag files are left behind on your computer,\r\n\tthey may end up in the same directory as your files or in a temporary\r\n\tdirectory depending on the rights of the file directory. You can specify the\r\n\tprefixe and suffix used to compute those temporary files.  There is also\r\n                some options to cleanup those file, the default being of only cleaning up\r\n                the temp directory.\r\n\r\nRight now the feature provided are:\r\n    *Detection of the currently edited tag and its type and presentation of this information in the\r\n     title bar. Most of the time when editing a C\/C++\/java... file this means you have on the \r\n     title bar the name of the current function.     *Creation of a menu of tags in the file this \r\n     contains things such as method, function, class... the type of tags supported depends on \r\n     the current language and on the implementation of the |ctags| program\r\n\r\n    TagsBase manipulates all tags supported by |ctags|. (For the full list of\r\n    supported tags and attributes, see \"http:\/\/ctags.sourceforge.net\/\"\r\n\r\n\r\nAdditional description can be found in the included help file. This script requires a version 5.0 of ctags.\r\n\r\nThis script has also been used by me as a test bed for embedding perl in vim scripts specifically for\r\nperformance reasons since parsing a large set of tags can take a fair amount of time.\r\nFor this reason you'll find a couple fo files (TagsBase.pl and VIM.pm) which I use in the development\r\nprocess, to find out about this see vimtip #140","install_details":"download the zip file, uncompress it in your runtimepath and run :helptags DirectoryWhereYouUncompressed\/doc","5":"download the zip file, uncompress it in your runtimepath and run :helptags DirectoryWhereYouUncompressed\/doc","first_name":"Benoit","6":"Benoit","last_name":"Cerrina","7":"Cerrina","releases":[{"0":"100","vim_version":"6.0","1":"6.0","script_version":"0.9.2","2":"0.9.2","version_comment":"corrected several bugs when the file path contains some spaces\r\ncorrected a bug with the TagsWindow","3":"corrected several bugs when the file path contains some spaces\r\ncorrected a bug with the TagsWindow","package":"TagsBase.zip","4":"TagsBase.zip","src_id":"382","5":"382","creation_date":"1006931499","6":"1006931499"},{"0":"100","vim_version":"6.0","1":"6.0","script_version":"0.9.1","2":"0.9.1","version_comment":"corrected a bug in the current tag lookup when perl is not available","3":"corrected a bug in the current tag lookup when perl is not available","package":"TagsBase.zip","4":"TagsBase.zip","src_id":"340","5":"340","creation_date":"1005548726","6":"1005548726"},{"0":"100","vim_version":"6.0","1":"6.0","script_version":"0.9","2":"0.9","version_comment":"added the TagsWindow command to visualize tags in a buffer. \r\nadded a menu entry to opent the Tags Buffer.\r\nadded a toc to the help.\r\ncorrected the NT ACL bug.","3":"added the TagsWindow command to visualize tags in a buffer. \r\nadded a menu entry to opent the Tags Buffer.\r\nadded a toc to the help.\r\ncorrected the NT ACL bug.","package":"TagsBase.zip","4":"TagsBase.zip","src_id":"336","5":"336","creation_date":"1005468141","6":"1005468141"},{"0":"100","vim_version":"6.0","1":"6.0","script_version":"0.8.3","2":"0.8.3","version_comment":"greatly enhanced the win32 cascading menus (when perl is available)","3":"greatly enhanced the win32 cascading menus (when perl is available)","package":"TagsBase.zip","4":"TagsBase.zip","src_id":"305","5":"305","creation_date":"1003969442","6":"1003969442"},{"0":"100","vim_version":"6.0","1":"6.0","script_version":"0.8.2","2":"0.8.2","version_comment":"bugfix removed some stray timing statements from the perl scripts","3":"bugfix removed some stray timing statements from the perl scripts","package":"TagsBase.zip","4":"TagsBase.zip","src_id":"294","5":"294","creation_date":"1003643367","6":"1003643367"},{"0":"100","vim_version":"6.0","1":"6.0","script_version":"0.8.1","2":"0.8.1","version_comment":"small correction for bug resulting in error message:\r\nUncaught exception from user code:\r\n^ICan't call method \"Type\" on unblessed reference at perl\/TagsBase.vim line 376.\r\n\r\n^ITagsBase::GetTagType(391) called at (eval 14) line 1\r\n^Ieval 'TagsBase::GetTagType 391\r\n;' called at (eval 14) line 0\r\nUncaught exception from user code:\r\n^ICan't call method \"Name\" on unblessed reference at perl\/TagsBase.vim line 389.\r\n\r\n^ITagsBase::GetTagName(391) called at (eval 15) line 1\r\n^Ieval 'TagsBase::GetTagName 391\r\n","3":"small correction for bug resulting in error message:\r\nUncaught exception from user code:\r\n^ICan't call method \"Type\" on unblessed reference at perl\/TagsBase.vim line 376.\r\n\r\n^ITagsBase::GetTagType(391) called at (eval 14) line 1\r\n^Ieval 'TagsBase::GetTagType 391\r\n;' called at (eval 14) line 0\r\nUncaught exception from user code:\r\n^ICan't call method \"Name\" on unblessed reference at perl\/TagsBase.vim line 389.\r\n\r\n^ITagsBase::GetTagName(391) called at (eval 15) line 1\r\n^Ieval 'TagsBase::GetTagName 391\r\n","package":"TagsBase.zip","4":"TagsBase.zip","src_id":"293","5":"293","creation_date":"1003540689","6":"1003540689"},{"0":"100","vim_version":"6.0","1":"6.0","script_version":"0.8","2":"0.8","version_comment":"Greatly improved the speed when perl is available.  Now almost everything happens in\r\nthe perl interpreter.   Speed improvement example: on a file with 5408 tags: \r\n645 second --> 72 second.  Limited the number of menu items to\r\nconfigurable size both for time reasons and because gtk doesn't like menus which are\r\nlonger than the screen.\r\nAdded the TagsBase.pl and VIM.pm file to the distribution, those are not needed for \r\nrunning the scripts but are usefull for debuging the perl parts.","3":"Greatly improved the speed when perl is available.  Now almost everything happens in\r\nthe perl interpreter.   Speed improvement example: on a file with 5408 tags: \r\n645 second --> 72 second.  Limited the number of menu items to\r\nconfigurable size both for time reasons and because gtk doesn't like menus which are\r\nlonger than the screen.\r\nAdded the TagsBase.pl and VIM.pm file to the distribution, those are not needed for \r\nrunning the scripts but are usefull for debuging the perl parts.","package":"TagsBase.zip","4":"TagsBase.zip","src_id":"291","5":"291","creation_date":"1003501484","6":"1003501484"},{"0":"100","vim_version":"6.0","1":"6.0","script_version":"0.7.1","2":"0.7.1","version_comment":" \"Corrected some bugs regarding the situation when perl is not builtin.\r\n  Corrected a bug when there is only one tag in the file repeated tag generation would interpret it as being overloaded.","3":" \"Corrected some bugs regarding the situation when perl is not builtin.\r\n  Corrected a bug when there is only one tag in the file repeated tag generation would interpret it as being overloaded.","package":"TagsBase.zip","4":"TagsBase.zip","src_id":"258","5":"258","creation_date":"1002670762","6":"1002670762"},{"0":"100","vim_version":"6.0","1":"6.0","script_version":"0.7","2":"0.7","version_comment":"Corrected some bugs regarding paths with spaces. \r\nreplaced the script local function s:GetTagName by a global function TagsBase_GetTagName. \r\nModified the doc to suggest using this function for displaying the tag name someplace else than the title bar.\r\nCorrected a bug regarding the cleanup code and editing read only files.","3":"Corrected some bugs regarding paths with spaces. \r\nreplaced the script local function s:GetTagName by a global function TagsBase_GetTagName. \r\nModified the doc to suggest using this function for displaying the tag name someplace else than the title bar.\r\nCorrected a bug regarding the cleanup code and editing read only files.","package":"TagsBase.zip","4":"TagsBase.zip","src_id":"255","5":"255","creation_date":"1002633195","6":"1002633195"},{"0":"100","vim_version":"6.0","1":"6.0","script_version":"0.6.1","2":"0.6.1","version_comment":"Uses the BufEnter autocmd to refresh the menu, this makes the menu work with split windows.\r\nKeeps the menu generating command in a buffer variable to avoid the extra work of reparsing if it is not needed.  \r\nUses the perl interpreter if available to speed up the tags parsing.","3":"Uses the BufEnter autocmd to refresh the menu, this makes the menu work with split windows.\r\nKeeps the menu generating command in a buffer variable to avoid the extra work of reparsing if it is not needed.  \r\nUses the perl interpreter if available to speed up the tags parsing.","package":"TagsBase.zip","4":"TagsBase.zip","src_id":"242","5":"242","creation_date":"1002326049","6":"1002326049"},{"0":"100","vim_version":"6.0","1":"6.0","script_version":"0.6","2":"0.6","version_comment":"avoids opening a buffer on the tags file, optionnally destroy the created tags files,  \r\nchanged the name of the g:CatProg variable to g:TagsBase_CatProg.\r\nSee :help TagsBase for a descriptions of the new options\r\n","3":"avoids opening a buffer on the tags file, optionnally destroy the created tags files,  \r\nchanged the name of the g:CatProg variable to g:TagsBase_CatProg.\r\nSee :help TagsBase for a descriptions of the new options\r\n","package":"TagsBase.zip","4":"TagsBase.zip","src_id":"228","5":"228","creation_date":"1002034250","6":"1002034250"},{"0":"100","vim_version":"6.0","1":"6.0","script_version":"0.5.3","2":"0.5.3","version_comment":"added new options to select the name of the tags\r\nfiles. Removed the html files. Changed the      \r\nlicense to public domain added the              \r\n|TagsBase-ChangeLog| and the |TagsBase-Credits| \r\nsection to the help. Added a warning about the  \r\nexistence of the tags files\"                    \r\n","3":"added new options to select the name of the tags\r\nfiles. Removed the html files. Changed the      \r\nlicense to public domain added the              \r\n|TagsBase-ChangeLog| and the |TagsBase-Credits| \r\nsection to the help. Added a warning about the  \r\nexistence of the tags files\"                    \r\n","package":"TagsBase.zip","4":"TagsBase.zip","src_id":"226","5":"226","creation_date":"1002019790","6":"1002019790"},{"0":"100","vim_version":"6.0","1":"6.0","script_version":"0.5.2","2":"0.5.2","version_comment":"bug fixes in the sorting of the lines array","3":"bug fixes in the sorting of the lines array","package":"TagsBase.zip","4":"TagsBase.zip","src_id":"224","5":"224","creation_date":"1002009304","6":"1002009304"},{"0":"100","vim_version":"6.0","1":"6.0","script_version":"0.5.1","2":"0.5.1","version_comment":"bug correction\r\n","3":"bug correction\r\n","package":"TagsBase.zip","4":"TagsBase.zip","src_id":"222","5":"222","creation_date":"1001993701","6":"1001993701"},{"0":"100","vim_version":"6.0","1":"6.0","script_version":"0.5","2":"0.5","version_comment":"I'm having a problem with the vim online interface, the version 0.5 script is a zip file not a vim file.\r\nOnce you download it it should be renamed as TagsBase.zip and unpacked in your runtimepath.\r\n","3":"I'm having a problem with the vim online interface, the version 0.5 script is a zip file not a vim file.\r\nOnce you download it it should be renamed as TagsBase.zip and unpacked in your runtimepath.\r\n","package":"TagsBase.zip","4":"TagsBase.zip","src_id":"221","5":"221","creation_date":"1001986911","6":"1001986911"},{"0":"100","vim_version":"6.0","1":"6.0","script_version":"0.5","2":"0.5","version_comment":"Added help, made customization easier, packaged into a zip file.\r\nTo install unpack in a directory in your runtimepath (see :help runtimepath) and run\r\n:helptags $dirUnpacked\/doc\r\n","3":"Added help, made customization easier, packaged into a zip file.\r\nTo install unpack in a directory in your runtimepath (see :help runtimepath) and run\r\n:helptags $dirUnpacked\/doc\r\n","package":"TagsBase.zip","4":"TagsBase.zip","src_id":"220","5":"220","creation_date":"1001984548","6":"1001984548"},{"0":"100","vim_version":"6.0","1":"6.0","script_version":"0.4","2":"0.4","version_comment":"reorganized and commented the script, support for the builtin tags stack, support for ordered tag file generation, some bugs corrected.","3":"reorganized and commented the script, support for the builtin tags stack, support for ordered tag file generation, some bugs corrected.","package":"TagsBase.zip","4":"TagsBase.zip","src_id":"217","5":"217","creation_date":"1001957323","6":"1001957323"},{"0":"100","vim_version":"6.0","1":"6.0","script_version":"0.3","2":"0.3","version_comment":"added a menu entry to toggle on and off the title string functionality","3":"added a menu entry to toggle on and off the title string functionality","package":"TagsBase.zip","4":"TagsBase.zip","src_id":"210","5":"210","creation_date":"1001907034","6":"1001907034"},{"0":"100","vim_version":"6.0","1":"6.0","script_version":"0.2","2":"0.2","version_comment":"Corrected dependency on a $TMP variable\r\ncorrected bug when on an ms system the shell used was a unix type shell, this generated problems due to the shell misinterpreting the '\\' in a path.\r\nIf you find any other bugs, please report it by mail to me (benoit.cerrina@writeme.com","3":"Corrected dependency on a $TMP variable\r\ncorrected bug when on an ms system the shell used was a unix type shell, this generated problems due to the shell misinterpreting the '\\' in a path.\r\nIf you find any other bugs, please report it by mail to me (benoit.cerrina@writeme.com","package":"TagsBase.zip","4":"TagsBase.zip","src_id":"209","5":"209","creation_date":"1001902232","6":"1001902232"},{"0":"100","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"TagsBase.zip","4":"TagsBase.zip","src_id":"208","5":"208","creation_date":"1001858001","6":"1001858001"}]},"99":{"script_id":"99","0":"99","script_name":"mail.tgz","1":"mail.tgz","script_type":"ftplugin","2":"ftplugin","summary":"mail plugin for vim","3":"mail plugin for vim","description":"This plugin's purpose is helping with mail editing.  It has two major roles.\r\nThe first is email address retrievel and the second is added functionality\r\nwhile editing.\r\n\r\nBelow is a description of the user callable functions in this plugin.\r\n\r\nEmail address retrieval\r\n=================\r\n\r\nMailAliasList\r\n------------------\r\n\r\nThis routine is designed to run an external program, allow the user to select\r\na bunch of emails, and then these emails are returned in a comma seperated\r\nlist.  For example, suppose the following line exists (the cursor is at the\r\ncaret):\r\n\r\n    To:\r\n          ^\r\n\r\nIf the user hits '\\al' then the currently configured program launches and the\r\nplugin will wait for the email list to be retrieved.  At present, only Abook\r\nis supported in this manner.  Patches are welcome.\r\n        \r\nMailAliasQuery\r\n---------------------\r\n\r\nThis routine is designed to take the <cword> under the cursor and do a lookup\r\non it.  This lookup should return a mutt email query, for example, given the\r\nfollowing:\r\n\r\n    To: john\r\n          ^\r\n\r\nIf the user hits \\aq, then the plugin will go out and attempt to lookup \"john\"\r\nin the current alias source.  Currently, all sources work with this mode.\r\n\r\nFormatting\r\n========\r\n\r\nMailFormatQuote\r\n-------------------------\r\n\r\nFormat a quote segment using QuoteMotion1.\r\n\r\nMailFormatLine\r\n----------------------\r\n\r\nFormats the current line.\r\n\r\nMailFormatMerge\r\n-------------------------\r\n\r\nConjoins the current line with the previous line.\r\n\r\nMailFormatParagraph\r\n-------------------------------\r\n\r\nFormats the current paragraph.\r\n\r\nQuote Manipulation\r\n==============\r\n\r\nMailQuoteEraseSig\r\n----------------------------\r\n\r\nThis routine will remove quoted signatures.  It always operates over the\r\nentire email.\r\n\r\n% | No, I don't agree with you.\r\n%\r\n% Nonsense.  You are wrong.  Grow up.\r\n%\r\n% | I can't believe I'm even replying to this.\r\n% | --\r\n% | Some power user\r\n%\r\n% Yeah, believe it, brother.\r\n% --\r\n% Some other user\r\n\r\nwill become:\r\n\r\n% | No, I don't agree with you.\r\n%\r\n% Nonsense.  You are wrong.  Grow up.\r\n%\r\n% | I can't believe I'm even replying to this.\r\n%\r\n% Yeah, believe it, brother.\r\n\r\nMailQuoteFixupSpaces\r\n---------------------------------\r\n\r\nThis will take a quote segment and try to put spaces in quote blocks where\r\nthey don't currently exist.  For example,\r\n    \r\n    >>% hello\r\n    >> bob\r\n\r\nwould turn into:\r\n\r\n    > > % hello\r\n    > > bob\r\n\r\nIn normal mode the ranger to operate over comes from mail_quote_motion1.\r\n\r\nMailQuoteMangledMerge\r\n------------------------------------\r\n\r\nThis routine will try and make sense out of 'Mangled' quoted paragraph.\r\nFor example, it will try and turn\r\n\r\n> > starting to look like a distro problem... Anyone\r\n> else\r\n> > having this problem running a different distro\r\n> besides\r\n> > LinuxBlast 8? Anyone tried 8.1 yet?\r\n\r\ninto:\r\n\r\n> > starting to look like a distro problem... Anyone else\r\n> > having this problem running a different distro besides\r\n> > LinuxBlast 8? Anyone tried 8.1 yet?\r\n\r\nIn normal mode this routine will operate over the current and next line.\r\n\r\nMailQuoteDelEmpty\r\n-----------------------------\r\n\r\nThis will search through the given range and attempt to delete all\r\nlines consisting of a quote block and optional white space.\r\n\r\nFor example,\r\n\r\n% > yellow\r\n% > blue\r\n% > \r\n% yes\r\n\r\nwill become:\r\n\r\n% > yellow\r\n% > blue\r\n\r\n% yes\r\n\r\nIn normal mode this routine will operate over the entire email.\r\n\r\nMailQuoteRemoveDpth\r\n----------------------------------\r\n\r\nThis routine will try and decrease the quote depth of a quote segment by one.\r\nHowever, it will remove the last layer of quoting.  This is because it is\r\nassumed that the user wants the oldest quote to be gone.\r\n\r\nFor example,\r\n\r\nab> % > I really\r\nab> % > like\r\nab> % > apples\r\n\r\nwill become:\r\n\r\nab> % I really\r\nab> % like\r\nab> % apples\r\n\r\nIn normal mode the ranger to operate over comes from mail_quote_motion1.\r\n\r\nQuote Motions\r\n===========\r\n\r\nA quote motion is a vim linewise motion that operates over quotes.  The\r\ndefault motion character is 'q'.  These motions are analogous to '$', 'E', and\r\nothers.  They allow the user to use operator commands over a quote range.  For\r\nexample, dq would allow the user to delete the current quote.  This means that\r\n\r\ngiven:\r\n\r\n> % Hi                                  <<< cursor on this line,\r\n> % How are you doing?\r\n> % How are things?\r\n> Fine.\r\n\r\nAnd the user hits dq, the text will be transformed into:\r\n\r\n> Yeah, It only took a few months.\r\n\r\nOr if the user were to hit, dqq, the text would be transformed into:\r\n\r\n> % Hi How are you doing?  How are things?\r\n> Yeah, fine.\r\n\r\nTo re-define the first or define the other two, use something like this:\r\n\r\n    omap <silent> <unique> q <Plug>MailQuoteMotion1\r\n    omap <silent> <unique> Q <Plug>MailQuoteMotion2\r\n    omap <silent> <unique> x <Plug>MailQuoteMotion3","4":"This plugin's purpose is helping with mail editing.  It has two major roles.\r\nThe first is email address retrievel and the second is added functionality\r\nwhile editing.\r\n\r\nBelow is a description of the user callable functions in this plugin.\r\n\r\nEmail address retrieval\r\n=================\r\n\r\nMailAliasList\r\n------------------\r\n\r\nThis routine is designed to run an external program, allow the user to select\r\na bunch of emails, and then these emails are returned in a comma seperated\r\nlist.  For example, suppose the following line exists (the cursor is at the\r\ncaret):\r\n\r\n    To:\r\n          ^\r\n\r\nIf the user hits '\\al' then the currently configured program launches and the\r\nplugin will wait for the email list to be retrieved.  At present, only Abook\r\nis supported in this manner.  Patches are welcome.\r\n        \r\nMailAliasQuery\r\n---------------------\r\n\r\nThis routine is designed to take the <cword> under the cursor and do a lookup\r\non it.  This lookup should return a mutt email query, for example, given the\r\nfollowing:\r\n\r\n    To: john\r\n          ^\r\n\r\nIf the user hits \\aq, then the plugin will go out and attempt to lookup \"john\"\r\nin the current alias source.  Currently, all sources work with this mode.\r\n\r\nFormatting\r\n========\r\n\r\nMailFormatQuote\r\n-------------------------\r\n\r\nFormat a quote segment using QuoteMotion1.\r\n\r\nMailFormatLine\r\n----------------------\r\n\r\nFormats the current line.\r\n\r\nMailFormatMerge\r\n-------------------------\r\n\r\nConjoins the current line with the previous line.\r\n\r\nMailFormatParagraph\r\n-------------------------------\r\n\r\nFormats the current paragraph.\r\n\r\nQuote Manipulation\r\n==============\r\n\r\nMailQuoteEraseSig\r\n----------------------------\r\n\r\nThis routine will remove quoted signatures.  It always operates over the\r\nentire email.\r\n\r\n% | No, I don't agree with you.\r\n%\r\n% Nonsense.  You are wrong.  Grow up.\r\n%\r\n% | I can't believe I'm even replying to this.\r\n% | --\r\n% | Some power user\r\n%\r\n% Yeah, believe it, brother.\r\n% --\r\n% Some other user\r\n\r\nwill become:\r\n\r\n% | No, I don't agree with you.\r\n%\r\n% Nonsense.  You are wrong.  Grow up.\r\n%\r\n% | I can't believe I'm even replying to this.\r\n%\r\n% Yeah, believe it, brother.\r\n\r\nMailQuoteFixupSpaces\r\n---------------------------------\r\n\r\nThis will take a quote segment and try to put spaces in quote blocks where\r\nthey don't currently exist.  For example,\r\n    \r\n    >>% hello\r\n    >> bob\r\n\r\nwould turn into:\r\n\r\n    > > % hello\r\n    > > bob\r\n\r\nIn normal mode the ranger to operate over comes from mail_quote_motion1.\r\n\r\nMailQuoteMangledMerge\r\n------------------------------------\r\n\r\nThis routine will try and make sense out of 'Mangled' quoted paragraph.\r\nFor example, it will try and turn\r\n\r\n> > starting to look like a distro problem... Anyone\r\n> else\r\n> > having this problem running a different distro\r\n> besides\r\n> > LinuxBlast 8? Anyone tried 8.1 yet?\r\n\r\ninto:\r\n\r\n> > starting to look like a distro problem... Anyone else\r\n> > having this problem running a different distro besides\r\n> > LinuxBlast 8? Anyone tried 8.1 yet?\r\n\r\nIn normal mode this routine will operate over the current and next line.\r\n\r\nMailQuoteDelEmpty\r\n-----------------------------\r\n\r\nThis will search through the given range and attempt to delete all\r\nlines consisting of a quote block and optional white space.\r\n\r\nFor example,\r\n\r\n% > yellow\r\n% > blue\r\n% > \r\n% yes\r\n\r\nwill become:\r\n\r\n% > yellow\r\n% > blue\r\n\r\n% yes\r\n\r\nIn normal mode this routine will operate over the entire email.\r\n\r\nMailQuoteRemoveDpth\r\n----------------------------------\r\n\r\nThis routine will try and decrease the quote depth of a quote segment by one.\r\nHowever, it will remove the last layer of quoting.  This is because it is\r\nassumed that the user wants the oldest quote to be gone.\r\n\r\nFor example,\r\n\r\nab> % > I really\r\nab> % > like\r\nab> % > apples\r\n\r\nwill become:\r\n\r\nab> % I really\r\nab> % like\r\nab> % apples\r\n\r\nIn normal mode the ranger to operate over comes from mail_quote_motion1.\r\n\r\nQuote Motions\r\n===========\r\n\r\nA quote motion is a vim linewise motion that operates over quotes.  The\r\ndefault motion character is 'q'.  These motions are analogous to '$', 'E', and\r\nothers.  They allow the user to use operator commands over a quote range.  For\r\nexample, dq would allow the user to delete the current quote.  This means that\r\n\r\ngiven:\r\n\r\n> % Hi                                  <<< cursor on this line,\r\n> % How are you doing?\r\n> % How are things?\r\n> Fine.\r\n\r\nAnd the user hits dq, the text will be transformed into:\r\n\r\n> Yeah, It only took a few months.\r\n\r\nOr if the user were to hit, dqq, the text would be transformed into:\r\n\r\n> % Hi How are you doing?  How are things?\r\n> Yeah, fine.\r\n\r\nTo re-define the first or define the other two, use something like this:\r\n\r\n    omap <silent> <unique> q <Plug>MailQuoteMotion1\r\n    omap <silent> <unique> Q <Plug>MailQuoteMotion2\r\n    omap <silent> <unique> x <Plug>MailQuoteMotion3","install_details":"cd ~\/.vim\r\ngzip -dc ~\/dl\/mail.tgz | tar -xf -\r\nvim -c \":helptags ~\/.vim\/doc\" -c :q","5":"cd ~\/.vim\r\ngzip -dc ~\/dl\/mail.tgz | tar -xf -\r\nvim -c \":helptags ~\/.vim\/doc\" -c :q","first_name":"brian","6":"brian","last_name":"medley","7":"medley","releases":[{"0":"99","vim_version":"6.0","1":"6.0","script_version":"1.9","2":"1.9","version_comment":"No longer map the first four function keys by default.\r\n\r\nCouple other bugfixes.","3":"No longer map the first four function keys by default.\r\n\r\nCouple other bugfixes.","package":"mail.tgz","4":"mail.tgz","src_id":"2461","5":"2461","creation_date":"1068063721","6":"1068063721"}]},"98":{"script_id":"98","0":"98","script_name":"spec.vim","1":"spec.vim","script_type":"ftplugin","2":"ftplugin","summary":"spec file plugin","3":"spec file plugin","description":"This is a spec file for creating\/editing rpm spec files. It supports internal and external macros.\nThere are currently two commands:\n\\ch creates a new changelog entry\n\\CH creates a new single change","4":"This is a spec file for creating\/editing rpm spec files. It supports internal and external macros.\nThere are currently two commands:\n\\ch creates a new changelog entry\n\\CH creates a new single change","install_details":"Just put in your .vim\/ftplugin dir","5":"Just put in your .vim\/ftplugin dir","first_name":"Guillaume","6":"Guillaume","last_name":"Rousse","7":"Rousse","releases":[{"0":"98","vim_version":"7.0","1":"7.0","script_version":"3.0","2":"3.0","version_comment":" - support epoch in revision informations\r\n - use rpm to evaluate external macros\r\n - add customization options (Gustavo Niemeyer <niemeyer@conectiva.com>)\r\n - large code  cleanup","3":" - support epoch in revision informations\r\n - use rpm to evaluate external macros\r\n - add customization options (Gustavo Niemeyer <niemeyer@conectiva.com>)\r\n - large code  cleanup","package":"spec-3.0.zip","4":"spec-3.0.zip","src_id":"7519","5":"7519","creation_date":"1187365510","6":"1187365510"},{"0":"98","vim_version":"6.0","1":"6.0","script_version":"0.2.1","2":"0.2.1","version_comment":"fix archive","3":"fix archive","package":"spec.zip","4":"spec.zip","src_id":"2665","5":"2665","creation_date":"1074403912","6":"1074403912"},{"0":"98","vim_version":"6.0","1":"6.0","script_version":"0.2","2":"0.2","version_comment":"- removed line width limit\n- support for %name style macros\n- quote patten when calling grep (Luca Berra <bluca@comedia.it>)\n- navigation through sections (Max Ischenko)\n- doc file","3":"- removed line width limit\n- support for %name style macros\n- quote patten when calling grep (Luca Berra <bluca@comedia.it>)\n- navigation through sections (Max Ischenko)\n- doc file","package":"spec.zip","4":"spec.zip","src_id":"2655","5":"2655","creation_date":"1073720588","6":"1073720588"},{"0":"98","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"spec.vim","4":"spec.vim","src_id":"205","5":"205","creation_date":"1001756217","6":"1001756217"}]},"97":{"script_id":"97","0":"97","script_name":"sqlplus.vim","1":"sqlplus.vim","script_type":"utility","2":"utility","summary":"Execute SQL queries and commands from within VIM (using Oracle's SQL*Plus)","3":"Execute SQL queries and commands from within VIM (using Oracle's SQL*Plus)","description":"Jamis Buck no longer maintains this script. Dani Rey is the new maintainer. Alas, the vim.org system is not configured to allow project owners to change, and the vim.org maintainers are silent when help requests are sent, so we're doing this the hard way.\r\n\r\nIf you want to use sqlplus.vim, please go grab Dani Rey's version, here:\r\n\r\n  http:\/\/www.vim.org\/scripts\/script.php?script_id=2821\r\n\r\nEnjoy!","4":"Jamis Buck no longer maintains this script. Dani Rey is the new maintainer. Alas, the vim.org system is not configured to allow project owners to change, and the vim.org maintainers are silent when help requests are sent, so we're doing this the hard way.\r\n\r\nIf you want to use sqlplus.vim, please go grab Dani Rey's version, here:\r\n\r\n  http:\/\/www.vim.org\/scripts\/script.php?script_id=2821\r\n\r\nEnjoy!","install_details":"THE SCRIPTS BELOW ARE OLD AND UNMAINTAINED.\r\n\r\nGo grab Dani Rey's newer, actively maintained version, here:\r\n\r\n  http:\/\/www.vim.org\/scripts\/script.php?script_id=2821","5":"THE SCRIPTS BELOW ARE OLD AND UNMAINTAINED.\r\n\r\nGo grab Dani Rey's newer, actively maintained version, here:\r\n\r\n  http:\/\/www.vim.org\/scripts\/script.php?script_id=2821","first_name":"Jamis","6":"Jamis","last_name":"Buck","7":"Buck","releases":[{"0":"97","vim_version":"6.0","1":"6.0","script_version":"1.2.3","2":"1.2.3","version_comment":"Now works under Windows!  (Thanks to Matt Kunze for his work in that area).","3":"Now works under Windows!  (Thanks to Matt Kunze for his work in that area).","package":"sqlplus.vim","4":"sqlplus.vim","src_id":"304","5":"304","creation_date":"1003935050","6":"1003935050"},{"0":"97","vim_version":"6.0","1":"6.0","script_version":"1.2.2","2":"1.2.2","version_comment":"Added \"cabbrev\" abbreviations so that :Select, :Update, :DB, and :SQL can be typed all lowercase.","3":"Added \"cabbrev\" abbreviations so that :Select, :Update, :DB, and :SQL can be typed all lowercase.","package":"sqlplus.vim","4":"sqlplus.vim","src_id":"301","5":"301","creation_date":"1003849727","6":"1003849727"},{"0":"97","vim_version":"6.0","1":"6.0","script_version":"1.2.1","2":"1.2.1","version_comment":"Fixed bug where multiline queries would fail if any lines after the first did not begin with whitespace.","3":"Fixed bug where multiline queries would fail if any lines after the first did not begin with whitespace.","package":"sqlplus.vim","4":"sqlplus.vim","src_id":"232","5":"232","creation_date":"1002099271","6":"1002099271"},{"0":"97","vim_version":"6.0","1":"6.0","script_version":"1.2","2":"1.2","version_comment":"added support for executing update and delete statements under cursor, fixed broken AE_execQueryUnderCursor, added :Update and :Delete commands, added :SQL command, added \\s* commands for quicker access to SQL commands, made variables global so they can be set in vimrc\r\n","3":"added support for executing update and delete statements under cursor, fixed broken AE_execQueryUnderCursor, added :Update and :Delete commands, added :SQL command, added \\s* commands for quicker access to SQL commands, made variables global so they can be set in vimrc\r\n","package":"sqlplus.vim","4":"sqlplus.vim","src_id":"225","5":"225","creation_date":"1002015195","6":"1002015195"},{"0":"97","vim_version":"6.0","1":"6.0","script_version":"0.1.1","2":"0.1.1","version_comment":"Added SQL*Plus commands to ensure that data is not truncated or wrapped, and that headers are not shown but once.","3":"Added SQL*Plus commands to ensure that data is not truncated or wrapped, and that headers are not shown but once.","package":"sqlplus.vim","4":"sqlplus.vim","src_id":"204","5":"204","creation_date":"1001675895","6":"1001675895"},{"0":"97","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"sqlplus.vim","4":"sqlplus.vim","src_id":"203","5":"203","creation_date":"1001675461","6":"1001675461"}]},"96":{"script_id":"96","0":"96","script_name":"methods.vim","1":"methods.vim","script_type":"utility","2":"utility","summary":"java, c++ menu classbrowser","3":"java, c++ menu classbrowser","description":"This little script offers an Class- and Sessionmenue for all languages\r\nctags understand (java,c++,c,eiffel,fortran). \r\n - ClassMembers: all attributes\/methods of actual class\r\n - SessionClasses: all Classes in the current session\r\nBy clicking on the entries, vim jumps to the specified location.The menue is updated via autocommands.","4":"This little script offers an Class- and Sessionmenue for all languages\r\nctags understand (java,c++,c,eiffel,fortran). \r\n - ClassMembers: all attributes\/methods of actual class\r\n - SessionClasses: all Classes in the current session\r\nBy clicking on the entries, vim jumps to the specified location.The menue is updated via autocommands.","install_details":"You NEED a ruby-interpreter compiled to vim, because this is a ruby script.\r\nAlso ctags is needed. \r\nJust put methods.vim into your vim-plugin directory - thats it.\r\n ","5":"You NEED a ruby-interpreter compiled to vim, because this is a ruby script.\r\nAlso ctags is needed. \r\nJust put methods.vim into your vim-plugin directory - thats it.\r\n ","first_name":"matthias","6":"matthias","last_name":"veit","7":"veit","releases":[{"0":"96","vim_version":"6.0","1":"6.0","script_version":"1.13","2":"1.13","version_comment":"-check for valid environment\r\n","3":"-check for valid environment\r\n","package":"methods.zip","4":"methods.zip","src_id":"563","5":"563","creation_date":"1013060672","6":"1013060672"},{"0":"96","vim_version":"6.0","1":"6.0","script_version":"1.13","2":"1.13","version_comment":"Complete redraw of this script. Featuring:\r\n-menudrawing works correctly:\r\n now it is possible to tearOff the ClassMenue and jump from\r\n buffer to buffer, while the open menu is updated dynamically.\r\n-all properties are dynamically changeable\r\n-extension points added: multiple parsers and sorters featured\r\n-ctags runs in filter mode\r\n","3":"Complete redraw of this script. Featuring:\r\n-menudrawing works correctly:\r\n now it is possible to tearOff the ClassMenue and jump from\r\n buffer to buffer, while the open menu is updated dynamically.\r\n-all properties are dynamically changeable\r\n-extension points added: multiple parsers and sorters featured\r\n-ctags runs in filter mode\r\n","package":"vimmethods.zip","4":"vimmethods.zip","src_id":"540","5":"540","creation_date":"1012815247","6":"1012815247"},{"0":"96","vim_version":"6.0","1":"6.0","script_version":"1.11","2":"1.11","version_comment":"-fixed the filenameexpansion failure\r\n-buffer deletion now works correctly\r\n","3":"-fixed the filenameexpansion failure\r\n-buffer deletion now works correctly\r\n","package":"methods.zip","4":"methods.zip","src_id":"447","5":"447","creation_date":"1010117088","6":"1010117088"},{"0":"96","vim_version":"6.0","1":"6.0","script_version":"1.10","2":"1.10","version_comment":"-fixed the \"new file\" problem (use only valid files)\r\n-using currentfile instead of <afile> can make trouble (fixed)\r\n  ","3":"-fixed the \"new file\" problem (use only valid files)\r\n-using currentfile instead of <afile> can make trouble (fixed)\r\n  ","package":"methods.vim","4":"methods.vim","src_id":"331","5":"331","creation_date":"1005289136","6":"1005289136"},{"0":"96","vim_version":"6.0","1":"6.0","script_version":"1.9.1","2":"1.9.1","version_comment":"-changed autocommands behaviour (try to read tags for every file type)\r\n-changed visibility and names of functions for better readability","3":"-changed autocommands behaviour (try to read tags for every file type)\r\n-changed visibility and names of functions for better readability","package":"methods.vim","4":"methods.vim","src_id":"316","5":"316","creation_date":"1004932805","6":"1004932805"},{"0":"96","vim_version":"6.0","1":"6.0","script_version":"1.9","2":"1.9","version_comment":"-display method-name in statusline\r\n-multisessions enabled\r\n-attributes are shown in submenu","3":"-display method-name in statusline\r\n-multisessions enabled\r\n-attributes are shown in submenu","package":"methods.vim","4":"methods.vim","src_id":"312","5":"312","creation_date":"1004627447","6":"1004627447"}]},"95":{"script_id":"95","0":"95","script_name":"winmanager","1":"winmanager","script_type":"utility","2":"utility","summary":"A windows style IDE for Vim 6.0","3":"A windows style IDE for Vim 6.0","description":"winmanager: A classical windows type environment for vim6.0 \r\n\r\nSnapshot                 : http:\/\/robotics.eecs.berkeley.edu\/~srinath\/vim\/snapshot2.JPG \r\nDetailed Instructions : http:\/\/robotics.eecs.berkeley.edu\/~srinath\/vim\/winmanager.htm \r\nUpates                    : http:\/\/robotics.eecs.berkeley.edu\/~srinath\/vim\/winmanager-2.0.htm \r\n\r\nwinmanager is a plugin which implements a classical windows type IDE in Vim-6.0. Basically, you have the directory tree\r\nand the buffer list as 2 windows which stay on the left and the editing is done in a seperate area on the left. People\r\nhave already made excellent File and Buffer explorers seperately and I thought that it might be a cool idea to combine\r\nthem both.  winmanager.vim combines the standard File Explorer which ships with Vim6.0 and a Buffer Explorer written by\r\nJeff Lanzarotta into one package.  It has the following features: \r\n\r\n1. the buffer listing is dynamic: i.e as you keep changing windows, editing new files, etc, the buffer list changes\r\ndynamically. the window also resizes dynamically, i.e it tries to occupy the minimum possible space to display all the\r\ncurrently listed windows. also, only the filename (i.e without path) is displayed in this window. however, the full path\r\nname is echoed on the command line as one moves around. \r\n\r\n2. the file explorer window doesn't actually edit a directory. Its a new empty file with modifiable off, etc. so that it\r\ndoesnt eat up buffer numbers as you roam around the directory tree. I found the original behaviour slightly annoying...\r\nAlso, I didnt find a way to change drives i.e go from c:\/ to h:\/ in the original explorer.vim. therefore i have added a\r\ntiny new mapping 'C' which changes the currently displayed directory to pwd. \r\n\r\nThanks! \r\n\r\n","4":"winmanager: A classical windows type environment for vim6.0 \r\n\r\nSnapshot                 : http:\/\/robotics.eecs.berkeley.edu\/~srinath\/vim\/snapshot2.JPG \r\nDetailed Instructions : http:\/\/robotics.eecs.berkeley.edu\/~srinath\/vim\/winmanager.htm \r\nUpates                    : http:\/\/robotics.eecs.berkeley.edu\/~srinath\/vim\/winmanager-2.0.htm \r\n\r\nwinmanager is a plugin which implements a classical windows type IDE in Vim-6.0. Basically, you have the directory tree\r\nand the buffer list as 2 windows which stay on the left and the editing is done in a seperate area on the left. People\r\nhave already made excellent File and Buffer explorers seperately and I thought that it might be a cool idea to combine\r\nthem both.  winmanager.vim combines the standard File Explorer which ships with Vim6.0 and a Buffer Explorer written by\r\nJeff Lanzarotta into one package.  It has the following features: \r\n\r\n1. the buffer listing is dynamic: i.e as you keep changing windows, editing new files, etc, the buffer list changes\r\ndynamically. the window also resizes dynamically, i.e it tries to occupy the minimum possible space to display all the\r\ncurrently listed windows. also, only the filename (i.e without path) is displayed in this window. however, the full path\r\nname is echoed on the command line as one moves around. \r\n\r\n2. the file explorer window doesn't actually edit a directory. Its a new empty file with modifiable off, etc. so that it\r\ndoesnt eat up buffer numbers as you roam around the directory tree. I found the original behaviour slightly annoying...\r\nAlso, I didnt find a way to change drives i.e go from c:\/ to h:\/ in the original explorer.vim. therefore i have added a\r\ntiny new mapping 'C' which changes the currently displayed directory to pwd. \r\n\r\nThanks! \r\n\r\n","install_details":"For version >= 2.0\r\n=============\r\n1. copy the file to your $HOME\/.vim or $HOME\\vimfiles directory\r\n\r\n2. unzip it (its a zip file) at that location. this should create the files\r\n   - plugin\/\r\n       winmanager.vim\r\n       winfileexplorer.vim\r\n       wintagexplorer.vim\r\n   - doc\/\r\n       winmanager.txt\r\n\r\n   IMPORTANT NOTE:\r\n   \r\n   i  . This version of winmanager ONLY works if you have the latest version\r\n        bufexplorer.vim. (vimscript #42).\r\n        The idea is that winmanager will no longer contain a duplicate copy\r\n        of bufexplorer.vim. This reduces script bloat, makes updates easier\r\n        and in genral makes the world a better place.\r\n   \r\n3. vim -c \"helptags ~\/.vim\/doc\" -c \"q\"  (unix)\r\n   or\r\n   vim -c \"helptags ~\/vimfiles\/doc\" -c \"q\"  (windows)\r\n   (this step should install winmanager.txt as a local help file on your\r\n   system. if this doesnt work, see \":he add-local-help\" to see how to do\r\n   it).\r\n\r\nYou will also need to change the mappings you might have used with\r\nwinmanager-1.x to\r\n\r\n    map <c-w><c-f> :FirstExplorerWindow<cr>\r\n    map <c-w><c-b> :BottomExplorerWindow<cr>\r\n    map <c-w><c-t> :WMToggle<cr>\r\n\r\nand the variable name g:bufExplorerWidth has been changed to\r\ng:winManagerWidth just to be more consistent.\r\n","5":"For version >= 2.0\r\n=============\r\n1. copy the file to your $HOME\/.vim or $HOME\\vimfiles directory\r\n\r\n2. unzip it (its a zip file) at that location. this should create the files\r\n   - plugin\/\r\n       winmanager.vim\r\n       winfileexplorer.vim\r\n       wintagexplorer.vim\r\n   - doc\/\r\n       winmanager.txt\r\n\r\n   IMPORTANT NOTE:\r\n   \r\n   i  . This version of winmanager ONLY works if you have the latest version\r\n        bufexplorer.vim. (vimscript #42).\r\n        The idea is that winmanager will no longer contain a duplicate copy\r\n        of bufexplorer.vim. This reduces script bloat, makes updates easier\r\n        and in genral makes the world a better place.\r\n   \r\n3. vim -c \"helptags ~\/.vim\/doc\" -c \"q\"  (unix)\r\n   or\r\n   vim -c \"helptags ~\/vimfiles\/doc\" -c \"q\"  (windows)\r\n   (this step should install winmanager.txt as a local help file on your\r\n   system. if this doesnt work, see \":he add-local-help\" to see how to do\r\n   it).\r\n\r\nYou will also need to change the mappings you might have used with\r\nwinmanager-1.x to\r\n\r\n    map <c-w><c-f> :FirstExplorerWindow<cr>\r\n    map <c-w><c-b> :BottomExplorerWindow<cr>\r\n    map <c-w><c-t> :WMToggle<cr>\r\n\r\nand the variable name g:bufExplorerWidth has been changed to\r\ng:winManagerWidth just to be more consistent.\r\n","first_name":"Srinath","6":"Srinath","last_name":"Avadhanula","7":"Avadhanula","releases":[{"0":"95","vim_version":"6.0","1":"6.0","script_version":"2.3","2":"2.3","version_comment":"Sorry, but I just found out that I had uploaded a week old version last time which didnt have any of the promised new features, namely favorite dirs, improved wintagexplorer etc. Its a huge surprise that I didnt get flooded with complaints! oh well.. also fixed a few minor bugs with both winmanager.vim and wintagexplorer.vim, so this is not a completely wasted upload.\r\n\r\nPlease see release notes for version 2.2 for changes.\r\nOnce again, you need vimscript #42 (bufexplorer.vim) for this to work.","3":"Sorry, but I just found out that I had uploaded a week old version last time which didnt have any of the promised new features, namely favorite dirs, improved wintagexplorer etc. Its a huge surprise that I didnt get flooded with complaints! oh well.. also fixed a few minor bugs with both winmanager.vim and wintagexplorer.vim, so this is not a completely wasted upload.\r\n\r\nPlease see release notes for version 2.2 for changes.\r\nOnce again, you need vimscript #42 (bufexplorer.vim) for this to work.","package":"winmanager.zip","4":"winmanager.zip","src_id":"754","5":"754","creation_date":"1017855839","6":"1017855839"},{"0":"95","vim_version":"6.0","1":"6.0","script_version":"2.2","2":"2.2","version_comment":"New Features:\r\n1. The file explorer now has a favorite directories option. The list of\r\n   favourite directories is shown above the current listing with '+'\r\n   signs prefixed to each fav dir. In order to change to a favorite\r\n   directory, you just go to that dir and press <enter>. Set g:favDirs\r\n   in your ~\/.vimrc to use set a default list of favorite directories.\r\n   This is a new-line seperated list of directories. For example:\r\n        let g:favDirs = \r\n            \\'e:\/srinath\/testing\/vim\/vimfiles\/plugin\/'.\"\\n\".\r\n            \\'e:\/srinath\/testing\/vim\/vimfiles\/ftplugin\/'.\"\\n\".\r\n            \\'e:\/srinath\/testing\/vim\/vimfiles\/compiler\/'\r\n   After startup, you can use 'f' to add the currently displayed\r\n   directory to the favourites.\r\n   NOTE: Use full path names. Use a trailing back-slash is safe.\r\n   NOTE: Use double quotes to enter a new-line.\r\n   NOTE: By default, $HOME is always included in the list. Do *not*\r\n         include it in g:favDirs.\r\n\r\n2. wintagexplorer.vim now has a feature where it saves its display in a\r\n   file .vimtagsdisplay in the tags directory. This speeds up display\r\n   next time you use wintagexplorer. useful if you work with large tags\r\n   files.\r\n   Put\r\n      let g:saveTagsDisplay = 0\r\n   in your ~\/.vimrc to disable this feature.\r\n\r\n3. There are a couple of more functions which winmanager exposes.\r\n   1. WinManagerGetLastEditedFile(n)\r\n      returns the n^th last file being edited.\r\n   2. IsWinManagerVisible()\r\n      returns 1 or 0 depending on whether explorer windows are visible.\r\n   These functions are internally necessary for adding on\r\n   FlistTree.vim to winmanager.vim. This is a new addon to winmanager\r\n   based on Dr. Charles E. Campbell's flisttree utility which\r\n   graphically shows the function dependency within C files.\r\n   FlistTree.vim is expected to be released shortly.\r\n\r\nug Fixes:\r\n1. When a file is chosen from the bufexplorer list and its not currently\r\n   visible, then the cursor jumps back to the first row.\r\n\r\n2. Sometimes the <C-N> and <C-p> mappings would be lost, when an\r\n   explorer didnt display properly.\r\n\r\n3. Several bugs in wintagexplorer.vim have been resolved.\r\n   (Thanks to Madoka Machitani and Mike Williams for valuable help).\r\n   wintagexplorer.vim is also more intelligent about remembering its\r\n   display.\r\n","3":"New Features:\r\n1. The file explorer now has a favorite directories option. The list of\r\n   favourite directories is shown above the current listing with '+'\r\n   signs prefixed to each fav dir. In order to change to a favorite\r\n   directory, you just go to that dir and press <enter>. Set g:favDirs\r\n   in your ~\/.vimrc to use set a default list of favorite directories.\r\n   This is a new-line seperated list of directories. For example:\r\n        let g:favDirs = \r\n            \\'e:\/srinath\/testing\/vim\/vimfiles\/plugin\/'.\"\\n\".\r\n            \\'e:\/srinath\/testing\/vim\/vimfiles\/ftplugin\/'.\"\\n\".\r\n            \\'e:\/srinath\/testing\/vim\/vimfiles\/compiler\/'\r\n   After startup, you can use 'f' to add the currently displayed\r\n   directory to the favourites.\r\n   NOTE: Use full path names. Use a trailing back-slash is safe.\r\n   NOTE: Use double quotes to enter a new-line.\r\n   NOTE: By default, $HOME is always included in the list. Do *not*\r\n         include it in g:favDirs.\r\n\r\n2. wintagexplorer.vim now has a feature where it saves its display in a\r\n   file .vimtagsdisplay in the tags directory. This speeds up display\r\n   next time you use wintagexplorer. useful if you work with large tags\r\n   files.\r\n   Put\r\n      let g:saveTagsDisplay = 0\r\n   in your ~\/.vimrc to disable this feature.\r\n\r\n3. There are a couple of more functions which winmanager exposes.\r\n   1. WinManagerGetLastEditedFile(n)\r\n      returns the n^th last file being edited.\r\n   2. IsWinManagerVisible()\r\n      returns 1 or 0 depending on whether explorer windows are visible.\r\n   These functions are internally necessary for adding on\r\n   FlistTree.vim to winmanager.vim. This is a new addon to winmanager\r\n   based on Dr. Charles E. Campbell's flisttree utility which\r\n   graphically shows the function dependency within C files.\r\n   FlistTree.vim is expected to be released shortly.\r\n\r\nug Fixes:\r\n1. When a file is chosen from the bufexplorer list and its not currently\r\n   visible, then the cursor jumps back to the first row.\r\n\r\n2. Sometimes the <C-N> and <C-p> mappings would be lost, when an\r\n   explorer didnt display properly.\r\n\r\n3. Several bugs in wintagexplorer.vim have been resolved.\r\n   (Thanks to Madoka Machitani and Mike Williams for valuable help).\r\n   wintagexplorer.vim is also more intelligent about remembering its\r\n   display.\r\n","package":"winmanager.zip","4":"winmanager.zip","src_id":"740","5":"740","creation_date":"1017619305","6":"1017619305"},{"0":"95","vim_version":"6.0","1":"6.0","script_version":"2.1","2":"2.1","version_comment":"    1. worked on improving the speed of wintagexplorer.vim \r\n       (the latest version is almost 3 times faster than the previous\r\n       version and faster for larger files).\r\n    2. removed some bugs from wintagexplorer.vim where the mappings would\r\n       dissapear because of caching.\r\n    3. fixed some important documentation bugs (thanks to Madoka\r\n       Machitani.)\r\n    4. also used an augroup for the autocommands used in winmanager to\r\n       better handle cases where the autcommands are deleted. (thanks to\r\n       Madoka again)\r\n    5. made fileexplorer.vim not screw up the search history. this was\r\n       caused because of ^\"= getting into the search history.\r\n       (thanks to Jeff Lanzarotta and Xiangjiang Ma).\r\n\r\n     NOTE: I frequently get asked the following question:\r\n     Q. From version 2.0, the command :GotoBufExplorerWindow does not work.\r\n        Whats wrong?\r\n     A. Starting from 2.0, the commands have been changed as follows:\r\n                 old                           new\r\n           GotoFileExplorerWindow  -----> FirstExplorerWindow\r\n           GotoBufExplorerWindow   -----> BottomExplorerWindow\r\n","3":"    1. worked on improving the speed of wintagexplorer.vim \r\n       (the latest version is almost 3 times faster than the previous\r\n       version and faster for larger files).\r\n    2. removed some bugs from wintagexplorer.vim where the mappings would\r\n       dissapear because of caching.\r\n    3. fixed some important documentation bugs (thanks to Madoka\r\n       Machitani.)\r\n    4. also used an augroup for the autocommands used in winmanager to\r\n       better handle cases where the autcommands are deleted. (thanks to\r\n       Madoka again)\r\n    5. made fileexplorer.vim not screw up the search history. this was\r\n       caused because of ^\"= getting into the search history.\r\n       (thanks to Jeff Lanzarotta and Xiangjiang Ma).\r\n\r\n     NOTE: I frequently get asked the following question:\r\n     Q. From version 2.0, the command :GotoBufExplorerWindow does not work.\r\n        Whats wrong?\r\n     A. Starting from 2.0, the commands have been changed as follows:\r\n                 old                           new\r\n           GotoFileExplorerWindow  -----> FirstExplorerWindow\r\n           GotoBufExplorerWindow   -----> BottomExplorerWindow\r\n","package":"winmanager.zip","4":"winmanager.zip","src_id":"587","5":"587","creation_date":"1013638411","6":"1013638411"},{"0":"95","vim_version":"6.0","1":"6.0","script_version":"2.0","2":"2.0","version_comment":"This is a major revision of winmanager with lots of new features, improved\r\nstability, etc.\r\n\r\nIMPORTANT: you need to download and install the latest version of\r\nbufexplorer (vimscript #42) to make this version of winmanager work.\r\n\r\n1. One of the major new features of this version is (hopefully, touch wood,\r\netc) its stability. It has undergone extensive QA by Xiangjiang Ma (and\r\nother users of the 2.0 beta version have also been using it for a couple of\r\nweeks and have reported a few bugs). A big thanks to him (and others) for\r\nall the valuable help. Infact a lot of the new features and the\r\nimplementation methods owe their style\/origin to his ideas.\r\n\r\n2. This version of winmanager no longer ships with a duplicate of\r\nbufexplorer.vim. This has many advantages such as a reduction in script\r\nbloat and in general promotes the idea of modularity. The latest version of\r\nbufexplorer.vim (see above) provides hooks so that winmanager can\r\ncommunicate with it. (thanks to Jeff Lanzarotta for making the necessary\r\nchanges).\r\n\r\n3. Becuase of some new features of bufexplorer.vim, winmanager is able to\r\noffer better dynamic behavior. For example, when you open up winmanager\r\nwhen your editing only a single buffer, bufexplorer will not be shown. As\r\nsoon as at least 2 buffers are opened, bufexplorer is automatically opened.\r\n\r\n4. This version provides an easy way to customize the window layout of\r\nwinmanager using non-default values of the global variable,\r\ng:winManagerWindowLayout. (see \":he winmanager-customizing\" for details).\r\n\r\n5. This version also provides a way to use winmanager.vim to \"edit\"\r\ndirectories instead of the standard exploerer.vim. To do this, you will\r\nneed to disable the standard explorer.vim (either by renaming it to\r\nexplorer.txt or putting \":let loaded_explorer = 1\" in your .vimrc). You\r\nthen need to put\r\n   :let g:defaultExplorer = 0 \r\nin your .vimrc to let winmanager know that its supposed to take over. \r\n\r\n6. I have tried to set-up a framework wherby it is very easy to add other\r\nIDE type plugins to winmanager. By this I mean that a plugin author\r\ncould, with the minimum of effort make a plugin which can be integrated\r\ninto winmanager. \r\n\r\n7. For the purpose of demonstrating the first feature, in this new version,\r\nwinmanager also ships with another lightweight plugin called\r\ntagsexplorer.vim. This is an elementary plugin which shows the tags in the\r\npresent directory in a fancy manner and offers some simple ways of\r\nnavigating between them.\r\nTo see this in action [File List] window and press CTRL-N. \r\n","3":"This is a major revision of winmanager with lots of new features, improved\r\nstability, etc.\r\n\r\nIMPORTANT: you need to download and install the latest version of\r\nbufexplorer (vimscript #42) to make this version of winmanager work.\r\n\r\n1. One of the major new features of this version is (hopefully, touch wood,\r\netc) its stability. It has undergone extensive QA by Xiangjiang Ma (and\r\nother users of the 2.0 beta version have also been using it for a couple of\r\nweeks and have reported a few bugs). A big thanks to him (and others) for\r\nall the valuable help. Infact a lot of the new features and the\r\nimplementation methods owe their style\/origin to his ideas.\r\n\r\n2. This version of winmanager no longer ships with a duplicate of\r\nbufexplorer.vim. This has many advantages such as a reduction in script\r\nbloat and in general promotes the idea of modularity. The latest version of\r\nbufexplorer.vim (see above) provides hooks so that winmanager can\r\ncommunicate with it. (thanks to Jeff Lanzarotta for making the necessary\r\nchanges).\r\n\r\n3. Becuase of some new features of bufexplorer.vim, winmanager is able to\r\noffer better dynamic behavior. For example, when you open up winmanager\r\nwhen your editing only a single buffer, bufexplorer will not be shown. As\r\nsoon as at least 2 buffers are opened, bufexplorer is automatically opened.\r\n\r\n4. This version provides an easy way to customize the window layout of\r\nwinmanager using non-default values of the global variable,\r\ng:winManagerWindowLayout. (see \":he winmanager-customizing\" for details).\r\n\r\n5. This version also provides a way to use winmanager.vim to \"edit\"\r\ndirectories instead of the standard exploerer.vim. To do this, you will\r\nneed to disable the standard explorer.vim (either by renaming it to\r\nexplorer.txt or putting \":let loaded_explorer = 1\" in your .vimrc). You\r\nthen need to put\r\n   :let g:defaultExplorer = 0 \r\nin your .vimrc to let winmanager know that its supposed to take over. \r\n\r\n6. I have tried to set-up a framework wherby it is very easy to add other\r\nIDE type plugins to winmanager. By this I mean that a plugin author\r\ncould, with the minimum of effort make a plugin which can be integrated\r\ninto winmanager. \r\n\r\n7. For the purpose of demonstrating the first feature, in this new version,\r\nwinmanager also ships with another lightweight plugin called\r\ntagsexplorer.vim. This is an elementary plugin which shows the tags in the\r\npresent directory in a fancy manner and offers some simple ways of\r\nnavigating between them.\r\nTo see this in action [File List] window and press CTRL-N. \r\n","package":"winmanager.zip","4":"winmanager.zip","src_id":"495","5":"495","creation_date":"1011372930","6":"1011372930"}]},"94":{"script_id":"94","0":"94","script_name":"express.vim","1":"express.vim","script_type":"syntax","2":"syntax","summary":"syntax file for Step21 express schema","3":"syntax file for Step21 express schema","description":"this is a syntax file for coloring the data structure description language EXPRESS as defined in the STEP (Standard for the Exchgange of Product Model) standard formarly\r\nISO-10303.  Express is describe in the part 11 of this standard","4":"this is a syntax file for coloring the data structure description language EXPRESS as defined in the STEP (Standard for the Exchgange of Product Model) standard formarly\r\nISO-10303.  Express is describe in the part 11 of this standard","install_details":"just drop it in a syntax directory in your runtime path\r\nyou'll also need to add \r\n\t  au! BufRead,BufNewFile *.express\tsetfiletype express\r\nto the filetype detect augroup","5":"just drop it in a syntax directory in your runtime path\r\nyou'll also need to add \r\n\t  au! BufRead,BufNewFile *.express\tsetfiletype express\r\nto the filetype detect augroup","first_name":"Benoit","6":"Benoit","last_name":"Cerrina","7":"Cerrina","releases":[{"0":"94","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"express.vim","4":"express.vim","src_id":"190","5":"190","creation_date":"1001379711","6":"1001379711"}]},"93":{"script_id":"93","0":"93","script_name":"tex.vim","1":"tex.vim","script_type":"utility","2":"utility","summary":"LaTeX macros in Vim (which emulate operator-pending mode operations)","3":"LaTeX macros in Vim (which emulate operator-pending mode operations)","description":"This file type plugin intended provides some insert mode macros for the\r\nLaTeX typesetting language. The nice thing about these mappings is that\r\nthey emulate the operator pending mode in the insert mode.  i.e, the user\r\ndoes NOT have to type the LHS in a hurry or without making mistakes. This\r\nfacilitates using the macros greatly.\r\n\r\nSee below for the detailed list of macros provided or just browe the file after downloading it.\r\nIn brief, this file provides stubs for the most commonly used typsetting\r\ncommands such as figures, matrices etc. As an example, the commonly used\r\nmatrix element is provided. Typing\r\n\r\nmat<tab>\r\n\r\nin the insert mode will expand to the following familiar matrix element:\r\n\r\n\\left[\r\n\\begin{array}{_}\r\n\\end{array}\r\n\\right]\r\n\r\nwith the cursor placed where the underscore is shown (note the underscore is\r\nnot part of the macro, it just shows the cursor placement)\r\nNOTE: <tab> is part of the LHS of the mapping. however, the characters need\r\n      NOT be typed in quick succession as in most insert mode commands.\r\n\r\nSee the section \"ADDING\" in the file in order to modify\/add new mappings.\r\n\r\nA quick way to enter greek symbols is also provided. For example, typing\r\n'\\q<tab>' will expand to \\theta. (NOTE: quotes are not part of the LHS).\r\nSee the section \"SYMBOLS\" in the file for adding\/modifying the way the\r\ngreek alphabet is mapped into the english alphabet. Again <tab> can be \r\nconviniently pressed after a long time or after moving around and coming back.\r\n\r\na few other shortcuts: \r\n== expands to &=& (useful while writing eqnarrays) \r\n$$ expands to $$ but the cursor is repositioned before the last $ (so you dont have to go back) \r\n_ expands to _{} \r\n^ expands to ^{} \r\n\r\n============================================================================\r\nLIST OF AVAILABLE MACROS\r\n============================================================================\r\n\r\n1. TABLE: tab<tab>\r\n\\begin{table}\r\n\\centering\r\n\\begin{tabular}{-}\r\n\r\n\\end{tabular}\r\n\\label{tab:}\r\n\\caption{}\r\n\\end{table}\r\n\r\n2. ARRAY: bar<tab>\r\n\\left\r\n\\begin{array}{-}\r\n\r\n\\end{array}\r\n\\right\r\n\r\n3. ENUMERATE: ben<tab>\r\n\\begin{enumerate}\r\n\\item -\r\n\\end{enumerate}\r\n\r\n4. ITEMIZE:\tbit<tab>\r\n\\begin{itemize}\r\n\\item -\r\n\\end{itemize}\r\n\r\n\r\n5. EQUATION: beq<tab> \r\n\\begin{equation}\r\n-\r\n\\end{equation}\r\n\r\n6. EQUATION ARRAY: bqn<tab> \r\n\\begin{eqnarray}\r\n-\r\n\\end{eqnarray}\r\n\r\n6. EPS FIGURE: bfg<tab> \r\n\\begin{figure}[h]\r\n\\centerline{\\psfig{figure=-.eps}}\r\n\\caption{}\r\n\\label{fig:}\r\n\\end{figure}\r\n\r\n7. EMPTY FIGURE: bfe<tab> \r\n\\begin{figure}\r\n\\vspace{-}\r\n\\caption{}\r\n\\end{figure}\r\n\r\n8. TABULAR: btb<tab> \r\n\\begin{tabular}{-}\r\n\r\n\\end{tabular}\r\n\r\n9. TABLE: bta<tab> \r\n\\begin{table}\r\n\\centering\r\n\\begin{tabular}{-}\r\n\r\n\\end{tabular}\r\n\\label{tab:}\r\n\\caption{}\r\n\\end{table}\r\n\r\n10. PICTURE: pic<tab> \r\n\\begin{picture}(4,4)\r\n\\put(0.5,0){\\framebox(4,4){-}}\r\n\\end{picture}\r\n\r\n11. MATRIX: mat<tab> \r\n\\left[\r\n\\begin{array}{-}\r\n\\end{array}\r\n\\right]\r\n\r\n12. FRAC: frac<tab> \r\n\\frac{-}{}\r\n\r\n13. DOT: dot<tab> \r\n\\dot{-}\r\n\r\n14. DOUBLE DOT: ddot<tab> \r\n\\ddot{-}\r\n","4":"This file type plugin intended provides some insert mode macros for the\r\nLaTeX typesetting language. The nice thing about these mappings is that\r\nthey emulate the operator pending mode in the insert mode.  i.e, the user\r\ndoes NOT have to type the LHS in a hurry or without making mistakes. This\r\nfacilitates using the macros greatly.\r\n\r\nSee below for the detailed list of macros provided or just browe the file after downloading it.\r\nIn brief, this file provides stubs for the most commonly used typsetting\r\ncommands such as figures, matrices etc. As an example, the commonly used\r\nmatrix element is provided. Typing\r\n\r\nmat<tab>\r\n\r\nin the insert mode will expand to the following familiar matrix element:\r\n\r\n\\left[\r\n\\begin{array}{_}\r\n\\end{array}\r\n\\right]\r\n\r\nwith the cursor placed where the underscore is shown (note the underscore is\r\nnot part of the macro, it just shows the cursor placement)\r\nNOTE: <tab> is part of the LHS of the mapping. however, the characters need\r\n      NOT be typed in quick succession as in most insert mode commands.\r\n\r\nSee the section \"ADDING\" in the file in order to modify\/add new mappings.\r\n\r\nA quick way to enter greek symbols is also provided. For example, typing\r\n'\\q<tab>' will expand to \\theta. (NOTE: quotes are not part of the LHS).\r\nSee the section \"SYMBOLS\" in the file for adding\/modifying the way the\r\ngreek alphabet is mapped into the english alphabet. Again <tab> can be \r\nconviniently pressed after a long time or after moving around and coming back.\r\n\r\na few other shortcuts: \r\n== expands to &=& (useful while writing eqnarrays) \r\n$$ expands to $$ but the cursor is repositioned before the last $ (so you dont have to go back) \r\n_ expands to _{} \r\n^ expands to ^{} \r\n\r\n============================================================================\r\nLIST OF AVAILABLE MACROS\r\n============================================================================\r\n\r\n1. TABLE: tab<tab>\r\n\\begin{table}\r\n\\centering\r\n\\begin{tabular}{-}\r\n\r\n\\end{tabular}\r\n\\label{tab:}\r\n\\caption{}\r\n\\end{table}\r\n\r\n2. ARRAY: bar<tab>\r\n\\left\r\n\\begin{array}{-}\r\n\r\n\\end{array}\r\n\\right\r\n\r\n3. ENUMERATE: ben<tab>\r\n\\begin{enumerate}\r\n\\item -\r\n\\end{enumerate}\r\n\r\n4. ITEMIZE:\tbit<tab>\r\n\\begin{itemize}\r\n\\item -\r\n\\end{itemize}\r\n\r\n\r\n5. EQUATION: beq<tab> \r\n\\begin{equation}\r\n-\r\n\\end{equation}\r\n\r\n6. EQUATION ARRAY: bqn<tab> \r\n\\begin{eqnarray}\r\n-\r\n\\end{eqnarray}\r\n\r\n6. EPS FIGURE: bfg<tab> \r\n\\begin{figure}[h]\r\n\\centerline{\\psfig{figure=-.eps}}\r\n\\caption{}\r\n\\label{fig:}\r\n\\end{figure}\r\n\r\n7. EMPTY FIGURE: bfe<tab> \r\n\\begin{figure}\r\n\\vspace{-}\r\n\\caption{}\r\n\\end{figure}\r\n\r\n8. TABULAR: btb<tab> \r\n\\begin{tabular}{-}\r\n\r\n\\end{tabular}\r\n\r\n9. TABLE: bta<tab> \r\n\\begin{table}\r\n\\centering\r\n\\begin{tabular}{-}\r\n\r\n\\end{tabular}\r\n\\label{tab:}\r\n\\caption{}\r\n\\end{table}\r\n\r\n10. PICTURE: pic<tab> \r\n\\begin{picture}(4,4)\r\n\\put(0.5,0){\\framebox(4,4){-}}\r\n\\end{picture}\r\n\r\n11. MATRIX: mat<tab> \r\n\\left[\r\n\\begin{array}{-}\r\n\\end{array}\r\n\\right]\r\n\r\n12. FRAC: frac<tab> \r\n\\frac{-}{}\r\n\r\n13. DOT: dot<tab> \r\n\\dot{-}\r\n\r\n14. DOUBLE DOT: ddot<tab> \r\n\\ddot{-}\r\n","install_details":"For Vim-6.0, drop the file in the $VIMRUNTIME\\ftplugin directory, where it will be sourced automatically at startup.\r\nFor previous versions, source it using the .vimrc file.","5":"For Vim-6.0, drop the file in the $VIMRUNTIME\\ftplugin directory, where it will be sourced automatically at startup.\r\nFor previous versions, source it using the .vimrc file.","first_name":"Srinath","6":"Srinath","last_name":"Avadhanula","7":"Avadhanula","releases":[{"0":"93","vim_version":"6.0","1":"6.0","script_version":"1.2","2":"1.2","version_comment":"removed a bug which was causing nested environments to be entered incorrectly. \r\nadded a few more commands. removed some debugging statements.\r\nadded a function RunLaTeX() which runs latex on the current file or a master file \r\nif one exists. see the file for additional details.","3":"removed a bug which was causing nested environments to be entered incorrectly. \r\nadded a few more commands. removed some debugging statements.\r\nadded a function RunLaTeX() which runs latex on the current file or a master file \r\nif one exists. see the file for additional details.","package":"tex.vim","4":"tex.vim","src_id":"418","5":"418","creation_date":"1007944172","6":"1007944172"},{"0":"93","vim_version":"6.0","1":"6.0","script_version":"1.1","2":"1.1","version_comment":"added a wrapper function which makes the insert mode mappings emulate the operator pending mode. i.e, the user does not have to type the LHS fast. Even making mistakes and moving around in the file is allowed before coming back and typing the last character (in this case its chosen to be the tab) expands nicely to the RHS.","3":"added a wrapper function which makes the insert mode mappings emulate the operator pending mode. i.e, the user does not have to type the LHS fast. Even making mistakes and moving around in the file is allowed before coming back and typing the last character (in this case its chosen to be the tab) expands nicely to the RHS.","package":"tex.vim","4":"tex.vim","src_id":"413","5":"413","creation_date":"1007760152","6":"1007760152"},{"0":"93","vim_version":"6.0","1":"6.0","script_version":"","2":"","version_comment":"Initial upload","3":"Initial upload","package":"tex.vim","4":"tex.vim","src_id":"189","5":"189","creation_date":"1001352283","6":"1001352283"}]},"92":{"script_id":"92","0":"92","script_name":"borland.vim","1":"borland.vim","script_type":"color scheme","2":"color scheme","summary":"Classic borland IDE like Vim color scheme","3":"Classic borland IDE like Vim color scheme","description":"\r\n","4":"\r\n","install_details":"\r\n1. Copy the borland.vim script to the .vim\/colors directory. Refer to\r\n   ':help colorscheme', ':help syn-default-override' and ':help runtimepath'\r\n   for more details\r\n2. Use the \":colorscheme borland\" command to use the color scheme.  You\r\n   can add this command to the .vimrc or .gvimrc file also.\r\n","5":"\r\n1. Copy the borland.vim script to the .vim\/colors directory. Refer to\r\n   ':help colorscheme', ':help syn-default-override' and ':help runtimepath'\r\n   for more details\r\n2. Use the \":colorscheme borland\" command to use the color scheme.  You\r\n   can add this command to the .vimrc or .gvimrc file also.\r\n","first_name":"Yegappan","6":"Yegappan","last_name":"Lakshmanan","7":"Lakshmanan","releases":[{"0":"92","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"borland.vim","4":"borland.vim","src_id":"188","5":"188","creation_date":"1001183753","6":"1001183753"}]},"91":{"script_id":"91","0":"91","script_name":"nsis.vim","1":"nsis.vim","script_type":"syntax","2":"syntax","summary":"This is a vim syntax file for NSIS script.","3":"This is a vim syntax file for NSIS script.","description":"NSIS stands for 'NullSoft Installation System' and is a handy free scriptable installation system made by NullSoft ( the \r\nguys who made Winamp). For more information on this, see http:\/\/www.nullsoft.com\/free\/nsis\/\r\nThis syntax is very straight forward as the syntax of the scripting language is simple. \r\n\r\nIf you use NSIS, please give it a try and tell me what you think as this is the first I actually write and vim syntax file.\r\nThanks,","4":"NSIS stands for 'NullSoft Installation System' and is a handy free scriptable installation system made by NullSoft ( the \r\nguys who made Winamp). For more information on this, see http:\/\/www.nullsoft.com\/free\/nsis\/\r\nThis syntax is very straight forward as the syntax of the scripting language is simple. \r\n\r\nIf you use NSIS, please give it a try and tell me what you think as this is the first I actually write and vim syntax file.\r\nThanks,","install_details":"Just put the .vim file into your syntax directory. The most easy(?) way to use it to do 'so .....\/nsis.vim'. But you can \r\nmodify your filetypes.vim in the runtime directory and add the following:\r\nau BufNewFile,BufRead *.nsi\t\tsetf nsis\r\nAnd then anytime you open a .nsi file, the syntax will be turned on automatically.\r\n","5":"Just put the .vim file into your syntax directory. The most easy(?) way to use it to do 'so .....\/nsis.vim'. But you can \r\nmodify your filetypes.vim in the runtime directory and add the following:\r\nau BufNewFile,BufRead *.nsi\t\tsetf nsis\r\nAnd then anytime you open a .nsi file, the syntax will be turned on automatically.\r\n","first_name":"Wenzhi","6":"Wenzhi","last_name":"Liang","7":"Liang","releases":[{"0":"91","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"nsis.vim","4":"nsis.vim","src_id":"184","5":"184","creation_date":"1001059360","6":"1001059360"}]},"90":{"script_id":"90","0":"90","script_name":"vcscommand.vim","1":"vcscommand.vim","script_type":"utility","2":"utility","summary":"CVS\/SVN\/SVK\/git\/hg\/bzr integration plugin","3":"CVS\/SVN\/SVK\/git\/hg\/bzr integration plugin","description":"VIM 7 plugin useful for manipulating files controlled by CVS, SVN, SVK, git, bzr, and hg within VIM, including committing changes and performing diffs using the vimdiff system.  Keywords:  bazaar bzr cvs CVS cvscommand git mercurial hg subversion SVN svk vcscommand\r\n\r\nThe source for this plugin is available in git at git:\/\/repo.or.cz\/vcscommand .  A web front end is available at http:\/\/repo.or.cz\/w\/vcscommand.git .\r\n\r\nPlease submit any issues at http:\/\/code.google.com\/p\/vcscommand\/\r\n","4":"VIM 7 plugin useful for manipulating files controlled by CVS, SVN, SVK, git, bzr, and hg within VIM, including committing changes and performing diffs using the vimdiff system.  Keywords:  bazaar bzr cvs CVS cvscommand git mercurial hg subversion SVN svk vcscommand\r\n\r\nThe source for this plugin is available in git at git:\/\/repo.or.cz\/vcscommand .  A web front end is available at http:\/\/repo.or.cz\/w\/vcscommand.git .\r\n\r\nPlease submit any issues at http:\/\/code.google.com\/p\/vcscommand\/\r\n","install_details":"If you are upgrading from the cvscommand.vim script, remove the cvscommand.vim plugin and the cvscommand.txt help file from your system before installing this version.  Also, read the CHANGES.txt file to learn about changes since cvscommand.vim.\r\n\r\nFor Vim 7:\r\n\r\n  Unzip the installation file.\r\n  Move the vcscommand.vim, vcscvs.vim, vcssvn.vim, vcssvk.vim, and vcsgit.vim scripts into your plugin directory.\r\n  Move the vcscommand.txt file into your doc directory and use the ':helptags' command to add it to your help directory (:help add-local-help).\r\n\r\nOptionally, you can move the syntax scripts into your syntax directory to get syntax highlighting of annotate result buffers.\r\n\r\nFor vim 6.x:\r\n\r\nUse a previous version of the script (1.76 of cvscommand.zip).  This only supports CVS.","5":"If you are upgrading from the cvscommand.vim script, remove the cvscommand.vim plugin and the cvscommand.txt help file from your system before installing this version.  Also, read the CHANGES.txt file to learn about changes since cvscommand.vim.\r\n\r\nFor Vim 7:\r\n\r\n  Unzip the installation file.\r\n  Move the vcscommand.vim, vcscvs.vim, vcssvn.vim, vcssvk.vim, and vcsgit.vim scripts into your plugin directory.\r\n  Move the vcscommand.txt file into your doc directory and use the ':helptags' command to add it to your help directory (:help add-local-help).\r\n\r\nOptionally, you can move the syntax scripts into your syntax directory to get syntax highlighting of annotate result buffers.\r\n\r\nFor vim 6.x:\r\n\r\nUse a previous version of the script (1.76 of cvscommand.zip).  This only supports CVS.","first_name":"Bob","6":"Bob","last_name":"Hiestand","7":"Hiestand","releases":[{"0":"90","vim_version":"7.0","1":"7.0","script_version":"1.99.47","2":"1.99.47","version_comment":"Re-enable the executable name quoting previously disabled in 1.99.43.  Please let me know if this causes problems.\r\n\r\nHandle ignored files in SVN to avoid errors in GetBufferInfo.\r\n\r\nRespect VCSCommandEdit setting of 'edit' in 2-argument VCSVimDiff.","3":"Re-enable the executable name quoting previously disabled in 1.99.43.  Please let me know if this causes problems.\r\n\r\nHandle ignored files in SVN to avoid errors in GetBufferInfo.\r\n\r\nRespect VCSCommandEdit setting of 'edit' in 2-argument VCSVimDiff.","package":"vcscommand-1.99.47.zip","4":"vcscommand-1.99.47.zip","src_id":"19809","5":"19809","creation_date":"1365799988","6":"1365799988"},{"0":"90","vim_version":"7.0","1":"7.0","script_version":"1.99.46","2":"1.99.46","version_comment":"Fix VCSVimDiff to work with 7.2 and lower again.\r\n\r\nAlways start a new row of windows when executing a split annotate.","3":"Fix VCSVimDiff to work with 7.2 and lower again.\r\n\r\nAlways start a new row of windows when executing a split annotate.","package":"vcscommand-1.99.46.zip","4":"vcscommand-1.99.46.zip","src_id":"17031","5":"17031","creation_date":"1323193056","6":"1323193056"},{"0":"90","vim_version":"7.0","1":"7.0","script_version":"1.99.45","2":"1.99.45","version_comment":"Identify files under svn 1.7.\r\nDon\\'t check repo status for svn buffer info.\r\nFix HG :VCSAnnotate in VCSAnnotate buffer.\r\nHandle &sel of \\'exclusive\\' in split annotation.\r\nUse case-insensitive tests for VCS file types.\r\n","3":"Identify files under svn 1.7.\r\nDon\\'t check repo status for svn buffer info.\r\nFix HG :VCSAnnotate in VCSAnnotate buffer.\r\nHandle &sel of \\'exclusive\\' in split annotation.\r\nUse case-insensitive tests for VCS file types.\r\n","package":"vcscommand-1.99.45.zip","4":"vcscommand-1.99.45.zip","src_id":"16705","5":"16705","creation_date":"1319038464","6":"1319038464"},{"0":"90","vim_version":"7.0","1":"7.0","script_version":"1.99.44","2":"1.99.44","version_comment":"Protect against versions of VIM that don't have fnameescape().\r\nAdded option 'VCSCommandVCSTypeOveride'\r\nAdded option 'VCSCommandVCSTypePreference'\r\nProtect against systems without +mbyte.\r\nRespect fenc when reviewing, annotating, or diffing.\r\nEncode commit messages as &tenc.\r\n","3":"Protect against versions of VIM that don't have fnameescape().\r\nAdded option 'VCSCommandVCSTypeOveride'\r\nAdded option 'VCSCommandVCSTypePreference'\r\nProtect against systems without +mbyte.\r\nRespect fenc when reviewing, annotating, or diffing.\r\nEncode commit messages as &tenc.\r\n","package":"vcscommand-1.99.44.zip","4":"vcscommand-1.99.44.zip","src_id":"16616","5":"16616","creation_date":"1317662461","6":"1317662461"},{"0":"90","vim_version":"7.0","1":"7.0","script_version":"1.99.43","2":"1.99.43","version_comment":"Important:  Don't try to escape executable names for shell execution. This means you'll need to make sure you've escaped special executable names for your particular system correctly.\r\nRespect 'no_plugin_maps'.\r\nfix escaping in VCSCommandChdir\r\nAccount for space used by 'number' option when performing split annotate.\r\nRestore cursorbind as part of vimdiff restore.\r\nHandle a difference between &enc and &tenc\r\nAlways use [bang] after :normal to avoid user remaps.\r\nAdded VCSCommandSetVCSType()\r\n\r\n","3":"Important:  Don't try to escape executable names for shell execution. This means you'll need to make sure you've escaped special executable names for your particular system correctly.\r\nRespect 'no_plugin_maps'.\r\nfix escaping in VCSCommandChdir\r\nAccount for space used by 'number' option when performing split annotate.\r\nRestore cursorbind as part of vimdiff restore.\r\nHandle a difference between &enc and &tenc\r\nAlways use [bang] after :normal to avoid user remaps.\r\nAdded VCSCommandSetVCSType()\r\n\r\n","package":"vcscommand-1.99.43.zip","4":"vcscommand-1.99.43.zip","src_id":"15797","5":"15797","creation_date":"1307054825","6":"1307054825"},{"0":"90","vim_version":"7.0","1":"7.0","script_version":"1.99.42","2":"1.99.42","version_comment":"svnannotate:  handle longer revision numbers\r\n\r\nVCSVimDiff:  handle 1 vimdiff session per tab\r\n\r\nmenu:  Add VCSCommandDisableMenu, VCSCommandMenuRoot, and VCSCommandMenuPriority variables to customize the GUI menu.\r\n\r\nvcshg:  correct message for empty commit\r\n","3":"svnannotate:  handle longer revision numbers\r\n\r\nVCSVimDiff:  handle 1 vimdiff session per tab\r\n\r\nmenu:  Add VCSCommandDisableMenu, VCSCommandMenuRoot, and VCSCommandMenuPriority variables to customize the GUI menu.\r\n\r\nvcshg:  correct message for empty commit\r\n","package":"vcscommand-1.99.42.zip","4":"vcscommand-1.99.42.zip","src_id":"13751","5":"13751","creation_date":"1283530589","6":"1283530589"},{"0":"90","vim_version":"7.0","1":"7.0","script_version":"1.99.41","2":"1.99.41","version_comment":"VCSStatus:  fix option pass-through\r\n\r\ngit:  show correct message for empty commit\r\n\r\nall:  fixed scratch buffer naming when buffers are not listed\r\n\r\nhg:  Provide a more useful commit info buffer\r\n\r\nhg:  show feedback on vcsadd via verbose option\r\n","3":"VCSStatus:  fix option pass-through\r\n\r\ngit:  show correct message for empty commit\r\n\r\nall:  fixed scratch buffer naming when buffers are not listed\r\n\r\nhg:  Provide a more useful commit info buffer\r\n\r\nhg:  show feedback on vcsadd via verbose option\r\n","package":"vcscommand-1.99.41.zip","4":"vcscommand-1.99.41.zip","src_id":"13632","5":"13632","creation_date":"1282318900","6":"1282318900"},{"0":"90","vim_version":"7.0","1":"7.0","script_version":"1.99.40","2":"1.99.40","version_comment":"*  Do not write to bzr log when identifying\r\n\r\n*  vcssvn:  Handle newer SVN 'status -vu' format.","3":"*  Do not write to bzr log when identifying\r\n\r\n*  vcssvn:  Handle newer SVN 'status -vu' format.","package":"vcscommand-1.99.40.zip","4":"vcscommand-1.99.40.zip","src_id":"12743","5":"12743","creation_date":"1269977142","6":"1269977142"},{"0":"90","vim_version":"7.0","1":"7.0","script_version":"1.99.39","2":"1.99.39","version_comment":"*IMPORTANT for Windows Users*  Please let me know if this change breaks your commit functionality.\r\n\r\n*  Removes use of 'shellslash' from the commit process.\r\n\r\n* Adds a call to user-defined autocommand VCSBufferCreated after the commit log message buffer is created.\r\n","3":"*IMPORTANT for Windows Users*  Please let me know if this change breaks your commit functionality.\r\n\r\n*  Removes use of 'shellslash' from the commit process.\r\n\r\n* Adds a call to user-defined autocommand VCSBufferCreated after the commit log message buffer is created.\r\n","package":"vcscommand-1.99.39.zip","4":"vcscommand-1.99.39.zip","src_id":"12736","5":"12736","creation_date":"1269891009","6":"1269891009"},{"0":"90","vim_version":"7.0","1":"7.0","script_version":"1.99.38","2":"1.99.38","version_comment":"VCSVimDiff:  Preserve filetype in review buffers.\r\n\r\nThis fixes a feature broken in 1.99.36.","3":"VCSVimDiff:  Preserve filetype in review buffers.\r\n\r\nThis fixes a feature broken in 1.99.36.","package":"vcscommand-1.99.38.zip","4":"vcscommand-1.99.38.zip","src_id":"12440","5":"12440","creation_date":"1266619342","6":"1266619342"},{"0":"90","vim_version":"7.0","1":"7.0","script_version":"1.99.37","2":"1.99.37","version_comment":"filetype of scratch buffers changed to lowercase for consistency.\r\n\r\nSyntax files renamed to lowercase.  You will probably want to remove existing syntax files from this plugin before installing this version.","3":"filetype of scratch buffers changed to lowercase for consistency.\r\n\r\nSyntax files renamed to lowercase.  You will probably want to remove existing syntax files from this plugin before installing this version.","package":"vcscommand-1.99.37.zip","4":"vcscommand-1.99.37.zip","src_id":"12274","5":"12274","creation_date":"1265131607","6":"1265131607"},{"0":"90","vim_version":"7.0","1":"7.0","script_version":"1.99.36","2":"1.99.36","version_comment":"VCSAnnotate now jumps to the current line in the annotated buffer (if annotating the current revision).\r\n\r\nVCSLog for CVS no longer sets the file type to 'rcslog'.  If you use that for syntax coloring, you may want to add something like the following to your vimrc:\r\n\r\nau FileType CVSlog set syntax=rcslog","3":"VCSAnnotate now jumps to the current line in the annotated buffer (if annotating the current revision).\r\n\r\nVCSLog for CVS no longer sets the file type to 'rcslog'.  If you use that for syntax coloring, you may want to add something like the following to your vimrc:\r\n\r\nau FileType CVSlog set syntax=rcslog","package":"vcscommand-1.99.36.zip","4":"vcscommand-1.99.36.zip","src_id":"12230","5":"12230","creation_date":"1264783450","6":"1264783450"},{"0":"90","vim_version":"7.0","1":"7.0","script_version":"1.99.35","2":"1.99.35","version_comment":"Fixed hang in MacVim on Snow Leopard (thanks to Adam Lickel).","3":"Fixed hang in MacVim on Snow Leopard (thanks to Adam Lickel).","package":"vcscommand-1.99.35.zip","4":"vcscommand-1.99.35.zip","src_id":"12191","5":"12191","creation_date":"1264535083","6":"1264535083"},{"0":"90","vim_version":"7.0","1":"7.0","script_version":"1.99.34","2":"1.99.34","version_comment":"vcshg:  Added annotate syntax.","3":"vcshg:  Added annotate syntax.","package":"vcscommand-1.99.34.zip","4":"vcscommand-1.99.34.zip","src_id":"12073","5":"12073","creation_date":"1263238496","6":"1263238496"},{"0":"90","vim_version":"7.0","1":"7.0","script_version":"1.99.33","2":"1.99.33","version_comment":"HG improvements:\r\n\r\nFixed variable assignment bug in GetBufferInfo.\r\nAdd username to blame output.\r\nAdded split annotate view.\r\n","3":"HG improvements:\r\n\r\nFixed variable assignment bug in GetBufferInfo.\r\nAdd username to blame output.\r\nAdded split annotate view.\r\n","package":"vcscommand.zip","4":"vcscommand.zip","src_id":"12031","5":"12031","creation_date":"1262968731","6":"1262968731"},{"0":"90","vim_version":"7.0","1":"7.0","script_version":"1.99.32","2":"1.99.32","version_comment":"* Resolve ambiguous file\/branch names.\r\n* Work correctly with blanks in 'VCSCommandXXXExec' variable.\r\n\r\nvcsbzr:  Add VCSCommandDisableAll kill switch.\r\nvcsbzr:  use annotate split mode.\r\nvcscvs:  Made GetRevision() script-local.\r\nvcshg: Identify hg version control when not in the root of a repository.\r\ngitAnnotate.vim:  match original commits in blame\r\n","3":"* Resolve ambiguous file\/branch names.\r\n* Work correctly with blanks in 'VCSCommandXXXExec' variable.\r\n\r\nvcsbzr:  Add VCSCommandDisableAll kill switch.\r\nvcsbzr:  use annotate split mode.\r\nvcscvs:  Made GetRevision() script-local.\r\nvcshg: Identify hg version control when not in the root of a repository.\r\ngitAnnotate.vim:  match original commits in blame\r\n","package":"vcscommand.zip","4":"vcscommand.zip","src_id":"12026","5":"12026","creation_date":"1262888213","6":"1262888213"},{"0":"90","vim_version":"7.0","1":"7.0","script_version":"1.99.31","2":"1.99.31","version_comment":"Added VCSAnnotate! (and VCSBlame!) (default keybinding <leader>cN) to split the resulting buffer into separate header and content windows.\r\n\r\nIncluded support for bzr and hg (as generously provided by others).\r\n\r\nAdded syntax file for git annotate buffers.\r\n","3":"Added VCSAnnotate! (and VCSBlame!) (default keybinding <leader>cN) to split the resulting buffer into separate header and content windows.\r\n\r\nIncluded support for bzr and hg (as generously provided by others).\r\n\r\nAdded syntax file for git annotate buffers.\r\n","package":"vcscommand.zip","4":"vcscommand.zip","src_id":"11049","5":"11049","creation_date":"1248209020","6":"1248209020"},{"0":"90","vim_version":"7.0","1":"7.0","script_version":"beta30","2":"beta30","version_comment":"vcscvs:  Removed useless (and bug-inspiring) aunmenu.\r\n\r\nvcscvs:  Remove extraneous debug message issued by recent cvs.\r\n\r\nFixed typo in sample macro documentation.","3":"vcscvs:  Removed useless (and bug-inspiring) aunmenu.\r\n\r\nvcscvs:  Remove extraneous debug message issued by recent cvs.\r\n\r\nFixed typo in sample macro documentation.","package":"vcscommand.zip","4":"vcscommand.zip","src_id":"11044","5":"11044","creation_date":"1248123721","6":"1248123721"},{"0":"90","vim_version":"7.0","1":"7.0","script_version":"beta29","2":"beta29","version_comment":"Added 'VCSCommandVCSTypeOverride' variable for explicitly overriding VCS type detection for specific directories.","3":"Added 'VCSCommandVCSTypeOverride' variable for explicitly overriding VCS type detection for specific directories.","package":"vcscommand.zip","4":"vcscommand.zip","src_id":"9965","5":"9965","creation_date":"1234554748","6":"1234554748"},{"0":"90","vim_version":"7.0","1":"7.0","script_version":"beta28","2":"beta28","version_comment":"Add 'VCSCommandDisableAll' variable to prevent the plugin or any extensions from loading.\r\n\r\nvcssvn:  prevent hangs caused by querying the user for input by specifying '--non-interactive' on the appropriate commands.\r\n\r\nUse &diffopt to seed the default DiffSplit orientation. (James Vega)\r\n","3":"Add 'VCSCommandDisableAll' variable to prevent the plugin or any extensions from loading.\r\n\r\nvcssvn:  prevent hangs caused by querying the user for input by specifying '--non-interactive' on the appropriate commands.\r\n\r\nUse &diffopt to seed the default DiffSplit orientation. (James Vega)\r\n","package":"vcscommand.zip","4":"vcscommand.zip","src_id":"9279","5":"9279","creation_date":"1222268067","6":"1222268067"},{"0":"90","vim_version":"7.0","1":"7.0","script_version":"beta28","2":"beta28","version_comment":"Add 'VCSCommandDisableAll' variable to prevent the plugin or any extensions from loading.\r\n\r\nvcssvn:  prevent hangs caused by querying the user for input by specifying '--non-interactive' on the appropriate commands.\r\n\r\nUse &diffopt to seed the default DiffSplit orientation. (James Vega)\r\n","3":"Add 'VCSCommandDisableAll' variable to prevent the plugin or any extensions from loading.\r\n\r\nvcssvn:  prevent hangs caused by querying the user for input by specifying '--non-interactive' on the appropriate commands.\r\n\r\nUse &diffopt to seed the default DiffSplit orientation. (James Vega)\r\n","package":"vcscommand.zip","4":"vcscommand.zip","src_id":"9278","5":"9278","creation_date":"1222268019","6":"1222268019"},{"0":"90","vim_version":"7.0","1":"7.0","script_version":"beta27","2":"beta27","version_comment":"Shortcut \/ mapping configuration changes:\r\n\r\nDo not fail out of plugin at first failed mapping.  Indicate mapping conflicts only if 'verbose' is set.\r\n    \r\nAdd new option 'VCSCommandMapPrefix' for overriding the default prefix '<Leader>c' in mappings.\r\n    \r\nAdd new option 'VCSCommandMappings' to completely override all default mappings.\r\n","3":"Shortcut \/ mapping configuration changes:\r\n\r\nDo not fail out of plugin at first failed mapping.  Indicate mapping conflicts only if 'verbose' is set.\r\n    \r\nAdd new option 'VCSCommandMapPrefix' for overriding the default prefix '<Leader>c' in mappings.\r\n    \r\nAdd new option 'VCSCommandMappings' to completely override all default mappings.\r\n","package":"vcscommand.zip","4":"vcscommand.zip","src_id":"9188","5":"9188","creation_date":"1219910893","6":"1219910893"},{"0":"90","vim_version":"7.0","1":"7.0","script_version":"beta 26","2":"beta 26","version_comment":"vcsgit:  Set &ft correctly for VCSStatus buffers.\r\n\r\nvcsgit:  Quote the blob name for VCSReview to handle paths with spaces.","3":"vcsgit:  Set &ft correctly for VCSStatus buffers.\r\n\r\nvcsgit:  Quote the blob name for VCSReview to handle paths with spaces.","package":"vcscommand.zip","4":"vcscommand.zip","src_id":"8827","5":"8827","creation_date":"1213895945","6":"1213895945"},{"0":"90","vim_version":"7.0","1":"7.0","script_version":"beta25","2":"beta25","version_comment":"This fixes the  'cdpath' error in git VCSReview and (2 argument) VCSVimDiff.\r\n","3":"This fixes the  'cdpath' error in git VCSReview and (2 argument) VCSVimDiff.\r\n","package":"vcscommand.zip","4":"vcscommand.zip","src_id":"8747","5":"8747","creation_date":"1212486365","6":"1212486365"},{"0":"90","vim_version":"7.0","1":"7.0","script_version":"beta24","2":"beta24","version_comment":"      Revert \"Call subversion with the '--non-interactive' switch to avoid locking up when authentication can't be prompted.\"\r\n      Use 'setlocal' instead of 'set' for all buffer option changes.\r\n      Use 'enew' followed by 'file' instead of 'edit' when creating output buffers.\r\n      Don't execute autocommands when naming VCS command output buffers.\r\n\r\nThis set of changes may avoid issues related to autocommands that execute when the command result buffer is opened.","3":"      Revert \"Call subversion with the '--non-interactive' switch to avoid locking up when authentication can't be prompted.\"\r\n      Use 'setlocal' instead of 'set' for all buffer option changes.\r\n      Use 'enew' followed by 'file' instead of 'edit' when creating output buffers.\r\n      Don't execute autocommands when naming VCS command output buffers.\r\n\r\nThis set of changes may avoid issues related to autocommands that execute when the command result buffer is opened.","package":"vcscommand.zip","4":"vcscommand.zip","src_id":"8709","5":"8709","creation_date":"1211283927","6":"1211283927"},{"0":"90","vim_version":"7.0","1":"7.0","script_version":"beta22","2":"beta22","version_comment":"Added VCSCommandGitDescribeArgList option to control allowed modes of 'git describe' used in GetBufferInfo for git.  This is a comma-separated list of arguments to try against git-describe.  This is an attempt to have prioritized fallbacks of descriptions, and runs in order until it finds a valid description.  This value defaults to ',tags,all,always', and so first searches annotated tags, then tags, then all references, then a commit description.","3":"Added VCSCommandGitDescribeArgList option to control allowed modes of 'git describe' used in GetBufferInfo for git.  This is a comma-separated list of arguments to try against git-describe.  This is an attempt to have prioritized fallbacks of descriptions, and runs in order until it finds a valid description.  This value defaults to ',tags,all,always', and so first searches annotated tags, then tags, then all references, then a commit description.","package":"vcscommand.zip","4":"vcscommand.zip","src_id":"8459","5":"8459","creation_date":"1205751889","6":"1205751889"},{"0":"90","vim_version":"7.0","1":"7.0","script_version":"beta21","2":"beta21","version_comment":"Tweaked buffer info for git buffers.\r\n\r\nDon't clobber &cp when testing for a vcs command.\r\n\r\nAdded 'options' Dict to VCSCommandDoCommand for tweaking framework behavior.\r\n\r\nAllow non-zero vcs command exit status when 'allowNonZeroExit' option is passed to VCSCommandDoCommand.\r\n\r\nImplemented VCSStatus for git as (repository-wide) 'git status'.\r\n\r\nConverted to leading tab style.\r\n\r\nDistinguish between exact and inexact identifications by extensions.\r\n\r\nMark git identification as inexact, so that using another VCS to control directories somewhere under a git-controlled directory does not identify the files incorrectly as git.\r\n\r\nMoved CHANGES.txt content into help file.\r\n","3":"Tweaked buffer info for git buffers.\r\n\r\nDon't clobber &cp when testing for a vcs command.\r\n\r\nAdded 'options' Dict to VCSCommandDoCommand for tweaking framework behavior.\r\n\r\nAllow non-zero vcs command exit status when 'allowNonZeroExit' option is passed to VCSCommandDoCommand.\r\n\r\nImplemented VCSStatus for git as (repository-wide) 'git status'.\r\n\r\nConverted to leading tab style.\r\n\r\nDistinguish between exact and inexact identifications by extensions.\r\n\r\nMark git identification as inexact, so that using another VCS to control directories somewhere under a git-controlled directory does not identify the files incorrectly as git.\r\n\r\nMoved CHANGES.txt content into help file.\r\n","package":"vcscommand.zip","4":"vcscommand.zip","src_id":"8435","5":"8435","creation_date":"1205237138","6":"1205237138"},{"0":"90","vim_version":"7.0","1":"7.0","script_version":"beta20","2":"beta20","version_comment":"Implemented (first pass of) git support.\r\n\r\nTemporarily removed buffer status\/command verification scheme.\r\n\r\nSave and restore 'foldlevel' with VCSVimDiff.\r\n\r\nAdded VCSRemove as alias for VCSDelete.\r\nAdded VCSBlame as alias for VCSAnnotate.\r\n","3":"Implemented (first pass of) git support.\r\n\r\nTemporarily removed buffer status\/command verification scheme.\r\n\r\nSave and restore 'foldlevel' with VCSVimDiff.\r\n\r\nAdded VCSRemove as alias for VCSDelete.\r\nAdded VCSBlame as alias for VCSAnnotate.\r\n","package":"vcscommand.zip","4":"vcscommand.zip","src_id":"8210","5":"8210","creation_date":"1201883140","6":"1201883140"},{"0":"90","vim_version":"7.0","1":"7.0","script_version":"beta19","2":"beta19","version_comment":"Load the plugin with nocompatible set, as it should have been done a few years ago.","3":"Load the plugin with nocompatible set, as it should have been done a few years ago.","package":"vcscommand.zip","4":"vcscommand.zip","src_id":"7435","5":"7435","creation_date":"1185896411","6":"1185896411"},{"0":"90","vim_version":"7.0","1":"7.0","script_version":"beta18","2":"beta18","version_comment":"Added 'VCSCommandDisableMappings' and 'VCSCommandDisableExtensionMappings' options.  If set, these variables prevent creation of the default command key mappings.","3":"Added 'VCSCommandDisableMappings' and 'VCSCommandDisableExtensionMappings' options.  If set, these variables prevent creation of the default command key mappings.","package":"vcscommand.zip","4":"vcscommand.zip","src_id":"7119","5":"7119","creation_date":"1179238893","6":"1179238893"},{"0":"90","vim_version":"7.0","1":"7.0","script_version":"beta17","2":"beta17","version_comment":"Use 'executable()' to test for VCS tools (to avoid potentially slow operation at plugin load time).\r\n\r\nAlways pass current revision to VCSAnnotate when using CVS with no arguments.","3":"Use 'executable()' to test for VCS tools (to avoid potentially slow operation at plugin load time).\r\n\r\nAlways pass current revision to VCSAnnotate when using CVS with no arguments.","package":"vcscommand.zip","4":"vcscommand.zip","src_id":"7112","5":"7112","creation_date":"1179214659","6":"1179214659"},{"0":"90","vim_version":"7.0","1":"7.0","script_version":"beta16","2":"beta16","version_comment":"VCSLog accepts passthrough options.\r\nVCSDiff correctly checks whether second argument starts with hyphen when deciding whether to pass-through.\r\n","3":"VCSLog accepts passthrough options.\r\nVCSDiff correctly checks whether second argument starts with hyphen when deciding whether to pass-through.\r\n","package":"vcscommand.zip","4":"vcscommand.zip","src_id":"7044","5":"7044","creation_date":"1177931197","6":"1177931197"},{"0":"90","vim_version":"7.0","1":"7.0","script_version":"beta15","2":"beta15","version_comment":"Use 'haslocaldir()' if available to correctly handle windows that used :lcd.\r\n\r\nMade VCSDiff pass-through.\r\n\r\nFixed SVK VCSDiff implementation.\r\n\r\nMade VCSCommands work a bit better on directory buffers (netrw).\r\n\r\nReplaced delayed extension registration to directly loading the main plugin from\r\nextension plugins.  This allows base functions declared in the main plugin to\r\nbe used in the extensions.\r\n\r\nFixed SVN diff to actually use 'VCSCommandSVNDiffOpt' option.","3":"Use 'haslocaldir()' if available to correctly handle windows that used :lcd.\r\n\r\nMade VCSDiff pass-through.\r\n\r\nFixed SVK VCSDiff implementation.\r\n\r\nMade VCSCommands work a bit better on directory buffers (netrw).\r\n\r\nReplaced delayed extension registration to directly loading the main plugin from\r\nextension plugins.  This allows base functions declared in the main plugin to\r\nbe used in the extensions.\r\n\r\nFixed SVN diff to actually use 'VCSCommandSVNDiffOpt' option.","package":"vcscommand.zip","4":"vcscommand.zip","src_id":"7025","5":"7025","creation_date":"1177422154","6":"1177422154"},{"0":"90","vim_version":"7.0","1":"7.0","script_version":"beta14","2":"beta14","version_comment":"Reincarnated 'CVSAnnotateParent' option for CVS as 'VCSCommandCVSAnnotateParent'.\r\n\r\nClose all vcscommand result buffers when vim exits to prevent them from being written to the viminfo file.","3":"Reincarnated 'CVSAnnotateParent' option for CVS as 'VCSCommandCVSAnnotateParent'.\r\n\r\nClose all vcscommand result buffers when vim exits to prevent them from being written to the viminfo file.","package":"vcscommand.zip","4":"vcscommand.zip","src_id":"6975","5":"6975","creation_date":"1176370272","6":"1176370272"},{"0":"90","vim_version":"7.0","1":"7.0","script_version":"beta13","2":"beta13","version_comment":"Fixed following commands (broken in Beta 12):\r\n  VCSLock\r\n  VCSRevert\r\n  VCSUnlock\r\n  VCSUpdate","3":"Fixed following commands (broken in Beta 12):\r\n  VCSLock\r\n  VCSRevert\r\n  VCSUnlock\r\n  VCSUpdate","package":"vcscommand.zip","4":"vcscommand.zip","src_id":"6858","5":"6858","creation_date":"1173686073","6":"1173686073"},{"0":"90","vim_version":"7.0","1":"7.0","script_version":"beta12","2":"beta12","version_comment":"Added SVK support.\r\n\r\nReplaced SVN-specific command SVNInfo with VCSInfo, which is defined for SVK\r\nand SVN.  This is mapped to '<leader>ci' by default; as a consequence, the\r\ndefault mapping for the CVS-specific CVSEditors command was changed to\r\n'<leader>cE'.\r\n\r\nMade VCSAnnotate accept parameters to pass to the underlying VCS.\r\n\r\nMade error messages for operations on non-versioned files more consistent.\r\n\r\nAdded check to disable individual VCS extension plugins.","3":"Added SVK support.\r\n\r\nReplaced SVN-specific command SVNInfo with VCSInfo, which is defined for SVK\r\nand SVN.  This is mapped to '<leader>ci' by default; as a consequence, the\r\ndefault mapping for the CVS-specific CVSEditors command was changed to\r\n'<leader>cE'.\r\n\r\nMade VCSAnnotate accept parameters to pass to the underlying VCS.\r\n\r\nMade error messages for operations on non-versioned files more consistent.\r\n\r\nAdded check to disable individual VCS extension plugins.","package":"vcscommand.zip","4":"vcscommand.zip","src_id":"6814","5":"6814","creation_date":"1172660172","6":"1172660172"},{"0":"90","vim_version":"7.0","1":"7.0","script_version":"beta11","2":"beta11","version_comment":"Added VCSCommandSVNDiffExt option to allow external diff applications.\r\nAdded VCSDelete command.\r\nAdded pass-through parameters to VCS Add, Delete, Log, Status, Lock, and Unlock commands (extra parameters to the command are given to the underlying VCS command).","3":"Added VCSCommandSVNDiffExt option to allow external diff applications.\r\nAdded VCSDelete command.\r\nAdded pass-through parameters to VCS Add, Delete, Log, Status, Lock, and Unlock commands (extra parameters to the command are given to the underlying VCS command).","package":"vcscommand.zip","4":"vcscommand.zip","src_id":"6761","5":"6761","creation_date":"1171958911","6":"1171958911"},{"0":"90","vim_version":"7.0","1":"7.0","script_version":"Beta10","2":"Beta10","version_comment":"Changed file type of commit log buffers to 'commitlog' (from 'commit log') to avoid FileType errors.\r\n\r\nAdded 'VCSCommandSVNDiffOpt' to pass options to the svn diff -x parameter.","3":"Changed file type of commit log buffers to 'commitlog' (from 'commit log') to avoid FileType errors.\r\n\r\nAdded 'VCSCommandSVNDiffOpt' to pass options to the svn diff -x parameter.","package":"vcscommand.zip","4":"vcscommand.zip","src_id":"6368","5":"6368","creation_date":"1162481486","6":"1162481486"},{"0":"90","vim_version":"7.0","1":"7.0","script_version":"Beta9","2":"Beta9","version_comment":"Added 'VCSCommandResultBufferNameExtension' option for adding a custom extension to the VCS output buffer names.  This is intended to help users experiencing issues due to autocommands and other settings that depend on buffer name.\r\n\r\nAdded 'VCSCommandResultBufferNameFunction' option for completely over-riding the procedure for generating the result buffer names.","3":"Added 'VCSCommandResultBufferNameExtension' option for adding a custom extension to the VCS output buffer names.  This is intended to help users experiencing issues due to autocommands and other settings that depend on buffer name.\r\n\r\nAdded 'VCSCommandResultBufferNameFunction' option for completely over-riding the procedure for generating the result buffer names.","package":"vcscommand.zip","4":"vcscommand.zip","src_id":"6160","5":"6160","creation_date":"1157975792","6":"1157975792"},{"0":"90","vim_version":"7.0","1":"7.0","script_version":"Beta8","2":"Beta8","version_comment":"Changed behavior of plugin within Explorer\/netrw -style directory buffers.  Commands within such a buffer now act as though invoked on that directory, and so affect all files (and subdirectories), regardless of where the cursor is within the directory buffer.","3":"Changed behavior of plugin within Explorer\/netrw -style directory buffers.  Commands within such a buffer now act as though invoked on that directory, and so affect all files (and subdirectories), regardless of where the cursor is within the directory buffer.","package":"vcscommand.zip","4":"vcscommand.zip","src_id":"6070","5":"6070","creation_date":"1155565796","6":"1155565796"},{"0":"90","vim_version":"7.0","1":"7.0","script_version":"Beta5","2":"Beta5","version_comment":"Corrected shortcut help text in commit message buffer.","3":"Corrected shortcut help text in commit message buffer.","package":"vcscommand.zip","4":"vcscommand.zip","src_id":"6055","5":"6055","creation_date":"1155142051","6":"1155142051"},{"0":"90","vim_version":"7.0","1":"7.0","script_version":"Beta4","2":"Beta4","version_comment":"Changed default mappings back to those from cvscommand (starting with\r\n'<Leader>c' instead of '<Leader>v'.  This is to avoid conflict with existing plugins using the '<Leader>v' prefix.  Please note that the mappings can still be overridden by the user using <Plug> mappings.  Please consult the documentation for more information.\r\n\r\nRemoved special characters other than parentheses from output buffer names.  This is to address buffer name problems on Windows.\r\n","3":"Changed default mappings back to those from cvscommand (starting with\r\n'<Leader>c' instead of '<Leader>v'.  This is to avoid conflict with existing plugins using the '<Leader>v' prefix.  Please note that the mappings can still be overridden by the user using <Plug> mappings.  Please consult the documentation for more information.\r\n\r\nRemoved special characters other than parentheses from output buffer names.  This is to address buffer name problems on Windows.\r\n","package":"vcscommand.zip","4":"vcscommand.zip","src_id":"6054","5":"6054","creation_date":"1155141491","6":"1155141491"},{"0":"90","vim_version":"7.0","1":"7.0","script_version":"Beta3","2":"Beta3","version_comment":"Initial public release of vcscommand (based on cvscommand) to integrate subversion (SVN) and utilize VIM 7.0 features.","3":"Initial public release of vcscommand (based on cvscommand) to integrate subversion (SVN) and utilize VIM 7.0 features.","package":"vcscommand.zip","4":"vcscommand.zip","src_id":"6040","5":"6040","creation_date":"1154682744","6":"1154682744"},{"0":"90","vim_version":"6.0","1":"6.0","script_version":"1.76","2":"1.76","version_comment":"Added optional direct specification of log message on :CVSCommit command (to avoid using the log message buffer).  Usage:\r\n\r\n:CVSCommit <log message text here>","3":"Added optional direct specification of log message on :CVSCommit command (to avoid using the log message buffer).  Usage:\r\n\r\n:CVSCommit <log message text here>","package":"cvscommand.zip","4":"cvscommand.zip","src_id":"5302","5":"5302","creation_date":"1140620646","6":"1140620646"},{"0":"90","vim_version":"6.0","1":"6.0","script_version":"1.75","2":"1.75","version_comment":"Forced file changed check whenever the original CVS file could have changed, even in split window environments (per Luca Gerli).","3":"Forced file changed check whenever the original CVS file could have changed, even in split window environments (per Luca Gerli).","package":"cvscommand.zip","4":"cvscommand.zip","src_id":"5208","5":"5208","creation_date":"1139840652","6":"1139840652"},{"0":"90","vim_version":"6.0","1":"6.0","script_version":"1.74","2":"1.74","version_comment":"* Added ability to use CVSCommand functions \/ hotkeys on directory listing buffers, specifically the file explorer.\r\n* CVSAnnotate:  Previously, if CVSAnnotate was invoked on a CVSAnnotate buffer, the new annotate buffer would go to the version just prior to the one on the current line.  Now, the new buffer uses the version on the current line.  To obtain the old behavior, set CVSCommandAnnotateParent to a non-zero value.  The header lines resulting from the cvs annotate command are now trimmed.  No attempt is made to jump to the 'correct' line in a CVSAnnotate buffer, as it is unlikely to be the correct line anyway.\r\n","3":"* Added ability to use CVSCommand functions \/ hotkeys on directory listing buffers, specifically the file explorer.\r\n* CVSAnnotate:  Previously, if CVSAnnotate was invoked on a CVSAnnotate buffer, the new annotate buffer would go to the version just prior to the one on the current line.  Now, the new buffer uses the version on the current line.  To obtain the old behavior, set CVSCommandAnnotateParent to a non-zero value.  The header lines resulting from the cvs annotate command are now trimmed.  No attempt is made to jump to the 'correct' line in a CVSAnnotate buffer, as it is unlikely to be the correct line anyway.\r\n","package":"cvscommand.zip","4":"cvscommand.zip","src_id":"5069","5":"5069","creation_date":"1139235622","6":"1139235622"},{"0":"90","vim_version":"6.0","1":"6.0","script_version":"1.73","2":"1.73","version_comment":"Fixed typo in sample map in documentation per Luca Gerli.","3":"Fixed typo in sample map in documentation per Luca Gerli.","package":"cvscommand.zip","4":"cvscommand.zip","src_id":"4999","5":"4999","creation_date":"1138004528","6":"1138004528"},{"0":"90","vim_version":"6.0","1":"6.0","script_version":"1.72","2":"1.72","version_comment":"Moved version check to after the loaded_cvscommand check.","3":"Moved version check to after the loaded_cvscommand check.","package":"cvscommand.zip","4":"cvscommand.zip","src_id":"4987","5":"4987","creation_date":"1137483934","6":"1137483934"},{"0":"90","vim_version":"6.0","1":"6.0","script_version":"1.71","2":"1.71","version_comment":"Restored CVSVimDiffFinish user autocommand which executes after a CVSVimDiff\r\n(in order to allow customization of window placement, etc).\r\n","3":"Restored CVSVimDiffFinish user autocommand which executes after a CVSVimDiff\r\n(in order to allow customization of window placement, etc).\r\n","package":"cvscommand.zip","4":"cvscommand.zip","src_id":"4798","5":"4798","creation_date":"1132649461","6":"1132649461"},{"0":"90","vim_version":"6.0","1":"6.0","script_version":"1.70","2":"1.70","version_comment":"Fixes bug that resulted in working directory change.\r\n\r\nDisplays warning to user and will not load if running on VIM earlier than 6.2.","3":"Fixes bug that resulted in working directory change.\r\n\r\nDisplays warning to user and will not load if running on VIM earlier than 6.2.","package":"cvscommand.zip","4":"cvscommand.zip","src_id":"4728","5":"4728","creation_date":"1131629755","6":"1131629755"},{"0":"90","vim_version":"6.0","1":"6.0","script_version":"1.68","2":"1.68","version_comment":"Fixed bug with autochdir and CVSCommit.\r\n(Repackaged from previous upload, which had new script in wrong place and old script in right place).du","3":"Fixed bug with autochdir and CVSCommit.\r\n(Repackaged from previous upload, which had new script in wrong place and old script in right place).du","package":"cvscommand.zip","4":"cvscommand.zip","src_id":"4403","5":"4403","creation_date":"1120140813","6":"1120140813"},{"0":"90","vim_version":"6.0","1":"6.0","script_version":"1.67","2":"1.67","version_comment":"Corrected b:CVSRepository variable for CVSAdd'd files.  This will fix status line display for these files, if the default (cvs) status line is used.","3":"Corrected b:CVSRepository variable for CVSAdd'd files.  This will fix status line display for these files, if the default (cvs) status line is used.","package":"cvscommand.zip","4":"cvscommand.zip","src_id":"3491","5":"3491","creation_date":"1096276528","6":"1096276528"},{"0":"90","vim_version":"6.0","1":"6.0","script_version":"1.66","2":"1.66","version_comment":"Changed maintainer email address.","3":"Changed maintainer email address.","package":"cvscommand.zip","4":"cvscommand.zip","src_id":"3450","5":"3450","creation_date":"1095147351","6":"1095147351"},{"0":"90","vim_version":"6.0","1":"6.0","script_version":"1.65","2":"1.65","version_comment":"Added instructions for integrating with SSH.\r\n\r\nAdded CVSCommandCVSExec option to specify cvs executable path.\r\n\r\nAdded CVSBufferSetup user event.\r\n","3":"Added instructions for integrating with SSH.\r\n\r\nAdded CVSCommandCVSExec option to specify cvs executable path.\r\n\r\nAdded CVSBufferSetup user event.\r\n","package":"cvscommand.zip","4":"cvscommand.zip","src_id":"3294","5":"3294","creation_date":"1091452558","6":"1091452558"},{"0":"90","vim_version":"6.0","1":"6.0","script_version":"1.64","2":"1.64","version_comment":"Delete folds created by vimdiff mode in CVSVimDiff if the original window used manual folds, when it is restored.\r\n\r\nAlways set scrollbind in the result window of a CVSVimDiff in order to combat the effects of splitting windows resetting scrollbind.  Please let me know if this causes anyone trouble.","3":"Delete folds created by vimdiff mode in CVSVimDiff if the original window used manual folds, when it is restored.\r\n\r\nAlways set scrollbind in the result window of a CVSVimDiff in order to combat the effects of splitting windows resetting scrollbind.  Please let me know if this causes anyone trouble.","package":"cvscommand.zip","4":"cvscommand.zip","src_id":"3018","5":"3018","creation_date":"1084370820","6":"1084370820"},{"0":"90","vim_version":"6.0","1":"6.0","script_version":"1.63","2":"1.63","version_comment":"Bugfix release.  Buffers start with 1, not 0.  Switch to the original buffer first before destorying CVS buffers in\r\nCVSGotoOriginal! in order to preserve window layout.\r\n","3":"Bugfix release.  Buffers start with 1, not 0.  Switch to the original buffer first before destorying CVS buffers in\r\nCVSGotoOriginal! in order to preserve window layout.\r\n","package":"cvscommand.zip","4":"cvscommand.zip","src_id":"2126","5":"2126","creation_date":"1057214550","6":"1057214550"},{"0":"90","vim_version":"6.0","1":"6.0","script_version":"1.62","2":"1.62","version_comment":"Added b:CVSRepository as a standard variable if buffer setup is enabled.\r\n\r\nChanged sample status line to display the repository version number if it differs from\r\nthe working version number.\r\n\r\nAdded recursive annotation functionality.\r\n\r\nSilenced text puts to set up the CVSCommit buffer.\r\n\r\nAdded CVSVimDiffFinish event for window placement customization.\r\n\r\nImplemented the remove-all-CVS-buffers aspect of CVSGotoOriginal! in a slightly\r\nmore sane way.\r\n\r\nAdded 'foldenable' to the list of restored options for\r\nCVSVimDiff.\r\n","3":"Added b:CVSRepository as a standard variable if buffer setup is enabled.\r\n\r\nChanged sample status line to display the repository version number if it differs from\r\nthe working version number.\r\n\r\nAdded recursive annotation functionality.\r\n\r\nSilenced text puts to set up the CVSCommit buffer.\r\n\r\nAdded CVSVimDiffFinish event for window placement customization.\r\n\r\nImplemented the remove-all-CVS-buffers aspect of CVSGotoOriginal! in a slightly\r\nmore sane way.\r\n\r\nAdded 'foldenable' to the list of restored options for\r\nCVSVimDiff.\r\n","package":"cvscommand.zip","4":"cvscommand.zip","src_id":"2123","5":"2123","creation_date":"1057141542","6":"1057141542"},{"0":"90","vim_version":"6.0","1":"6.0","script_version":"1.54","2":"1.54","version_comment":"Added recognition of numerical tags for use as sticky tags.","3":"Added recognition of numerical tags for use as sticky tags.","package":"cvscommand.zip","4":"cvscommand.zip","src_id":"1949","5":"1949","creation_date":"1051525467","6":"1051525467"},{"0":"90","vim_version":"6.0","1":"6.0","script_version":"1.52","2":"1.52","version_comment":"Added the CVSGotoOriginal[!] command and mappings (<Leader>cg and <Leader> cG for with and without '!', respectively).  This command jumps to the source buffer if the current buffer is a CVS output buffer.  The '!' also closes all CVS output buffer for the given source buffer.","3":"Added the CVSGotoOriginal[!] command and mappings (<Leader>cg and <Leader> cG for with and without '!', respectively).  This command jumps to the source buffer if the current buffer is a CVS output buffer.  The '!' also closes all CVS output buffer for the given source buffer.","package":"cvscommand.zip","4":"cvscommand.zip","src_id":"1929","5":"1929","creation_date":"1050652360","6":"1050652360"}]},"89":{"script_id":"89","0":"89","script_name":"savevers.vim","1":"savevers.vim","script_type":"utility","2":"utility","summary":"Automatically save and diff multiple, sequentially numbered revisions (like VMS)","3":"Automatically save and diff multiple, sequentially numbered revisions (like VMS)","description":"Automatically saves and compares multiple, sequentially numbered\r\nold revisions of files (like in VMS)\r\n\r\nIf the 'patchmode' option is non-empty, then whenever a file\r\nis saved, a version of the previously saved version is kept,\r\nbut renamed to {file}.{number}.{patchext}, where:\r\n    {file}     is the filename of the file being saved\r\n    {number}   is a number between 0001 and 9999\r\n    {patchext} is the value of the 'patchmode' option.\r\n\r\nOptionally, the saved versions can be placed in a subdirectory.\r\n\r\nNote that this plugin is DISABLED if 'patchmode' is empty.\r\nAlso, this plugin won't work if 'backupdir' is empty or if\r\n'backup' is unset, so to get started, put the following in\r\nyour \".vimrc\"\r\n\r\n    set backup\r\n    set patchmode=.clean\r\n\r\nSo, for example, if 'patchmode' is '.clean' and we save a\r\nfile named \"test.txt\" we'll have the following files:\r\n\r\n-rw-r----- 1 eralston admin  106 Sep 20 11:14 test.txt\r\n-rw-r----- 1 eralston admin  102 Sep 20 11:12 test.txt.0001.clean\r\n\r\nIf we make subsequent changes to \"test.txt\" and save it a\r\nfew more times, we'll end up with something like:\r\n\r\n-rw-r----- 1 eralston admin  226 Sep 20 11:43 test.txt\r\n-rw-r----- 1 eralston admin  102 Sep 20 11:12 test.txt.0001.clean\r\n-rw-r----- 1 eralston admin  106 Sep 20 11:14 test.txt.0002.clean\r\n-rw-r----- 1 eralston admin  132 Sep 20 11:22 test.txt.0003.clean\r\n-rw-r----- 1 eralston admin  148 Sep 20 11:34 test.txt.0004.clean\r\n\r\nCOMMANDS:\r\n   :Purge [-a] [-v] [N]\r\n      Removes all but the patchmode files numbered N and below.\r\n      The [N] is optional, and defaults to 1.\r\n      Normally, this operates only on the patchmode files associated\r\n      with the current buffer, but if the [-a] flag is given, then\r\n      it operates on all patchmode files in the directory of the\r\n      current file.\r\n      If the optional [-v] (verbose) flag is given, then the filename\r\n      of each deleted patchmode file is printed.\r\n\r\n      Use \":Purge 0\" to delete all of the patchmode files for the\r\n      current file.\r\n\r\n      Use \":Purge -a 0\" to delete all of the patchmode files in\r\n      the directory of the current file.\r\n\r\n   :VersDiff [arg]\r\n      Does a \"diffsplit\" on the current file with the version\r\n      indicated by [arg].  So, for example, if the current\r\n      file is \"test.txt\" then the \":VersDiff 5\" command will\r\n      do a \"diffsplit\" with \"test.txt.0005.clean\", assuming\r\n      &patchmode is \".clean\"\r\n\r\n      If [arg] is zero (the default), then the diff is done with\r\n      the current saved version of the file.\r\n\r\n      If [arg] is negative, then the diff is done with the\r\n      [arg]th oldest file; e.g., if [arg] is \"-5\" and there are\r\n      versions 0001-0023 saved on disk, then the version that\r\n      is diffed will be (23-5+1)=19, i.e, \"test.txt.0019\" will\r\n      be diffed.\r\n\r\n      If [arg] is \"-cvs\", then the diff is done with the most recently\r\n      checked-in version of the file.\r\n\r\n      If [arg] is \"-\", then the current VersDiff window is decremented.\r\n      If [arg] is \"+\", then the current VersDiff window is incremented.\r\n          (Note that if VersDiff is currently doing a cvs diff, then\r\n          the cvs revision is incremented\/decremented)\r\n\r\n      If [arg] is \"-c\", then any current VersDiff window is closed.\r\n\r\nHINTS:\r\n   If you use GNU 'ls', then try adding \"-I'*.clean'\" (without the\r\n   double quotes) to your 'ls' alias (assuming &patchmode==.clean)\r\n\r\n   It's also helpful to have the patchmode value in the backupskip,\r\n   suffixes, and wildignore vim options:\r\n\r\n      :exe \"set backupskip+=*\" . &patchmode\r\n      :exe \"set suffixes+=\" . &patchmode\r\n      :exe \"set wildignore+=*\" . &patchmode\r\n\r\n   Also, here are some nice mappings that allow quick comparison\r\n   of the current file with previous versions.  Pressing <F5>\r\n   successively shows the diff with older versions.\r\n\r\n      \" <F5> decrease version viewed in VersDiff window\r\n      \" <F6> increase version viewed in VersDiff window\r\n      \" <F7> do VersDiff with cvs version of current file\r\n      \" <F8> cancel VersDiff window\r\n      nmap <silent> <F5> :VersDiff -<cr>\r\n      nmap <silent> <F6> :VersDiff +<cr>\r\n      nmap <silent> <F7> :VersDiff -cvs<cr>\r\n      nmap <silent> <F8> :VersDiff -c<cr>","4":"Automatically saves and compares multiple, sequentially numbered\r\nold revisions of files (like in VMS)\r\n\r\nIf the 'patchmode' option is non-empty, then whenever a file\r\nis saved, a version of the previously saved version is kept,\r\nbut renamed to {file}.{number}.{patchext}, where:\r\n    {file}     is the filename of the file being saved\r\n    {number}   is a number between 0001 and 9999\r\n    {patchext} is the value of the 'patchmode' option.\r\n\r\nOptionally, the saved versions can be placed in a subdirectory.\r\n\r\nNote that this plugin is DISABLED if 'patchmode' is empty.\r\nAlso, this plugin won't work if 'backupdir' is empty or if\r\n'backup' is unset, so to get started, put the following in\r\nyour \".vimrc\"\r\n\r\n    set backup\r\n    set patchmode=.clean\r\n\r\nSo, for example, if 'patchmode' is '.clean' and we save a\r\nfile named \"test.txt\" we'll have the following files:\r\n\r\n-rw-r----- 1 eralston admin  106 Sep 20 11:14 test.txt\r\n-rw-r----- 1 eralston admin  102 Sep 20 11:12 test.txt.0001.clean\r\n\r\nIf we make subsequent changes to \"test.txt\" and save it a\r\nfew more times, we'll end up with something like:\r\n\r\n-rw-r----- 1 eralston admin  226 Sep 20 11:43 test.txt\r\n-rw-r----- 1 eralston admin  102 Sep 20 11:12 test.txt.0001.clean\r\n-rw-r----- 1 eralston admin  106 Sep 20 11:14 test.txt.0002.clean\r\n-rw-r----- 1 eralston admin  132 Sep 20 11:22 test.txt.0003.clean\r\n-rw-r----- 1 eralston admin  148 Sep 20 11:34 test.txt.0004.clean\r\n\r\nCOMMANDS:\r\n   :Purge [-a] [-v] [N]\r\n      Removes all but the patchmode files numbered N and below.\r\n      The [N] is optional, and defaults to 1.\r\n      Normally, this operates only on the patchmode files associated\r\n      with the current buffer, but if the [-a] flag is given, then\r\n      it operates on all patchmode files in the directory of the\r\n      current file.\r\n      If the optional [-v] (verbose) flag is given, then the filename\r\n      of each deleted patchmode file is printed.\r\n\r\n      Use \":Purge 0\" to delete all of the patchmode files for the\r\n      current file.\r\n\r\n      Use \":Purge -a 0\" to delete all of the patchmode files in\r\n      the directory of the current file.\r\n\r\n   :VersDiff [arg]\r\n      Does a \"diffsplit\" on the current file with the version\r\n      indicated by [arg].  So, for example, if the current\r\n      file is \"test.txt\" then the \":VersDiff 5\" command will\r\n      do a \"diffsplit\" with \"test.txt.0005.clean\", assuming\r\n      &patchmode is \".clean\"\r\n\r\n      If [arg] is zero (the default), then the diff is done with\r\n      the current saved version of the file.\r\n\r\n      If [arg] is negative, then the diff is done with the\r\n      [arg]th oldest file; e.g., if [arg] is \"-5\" and there are\r\n      versions 0001-0023 saved on disk, then the version that\r\n      is diffed will be (23-5+1)=19, i.e, \"test.txt.0019\" will\r\n      be diffed.\r\n\r\n      If [arg] is \"-cvs\", then the diff is done with the most recently\r\n      checked-in version of the file.\r\n\r\n      If [arg] is \"-\", then the current VersDiff window is decremented.\r\n      If [arg] is \"+\", then the current VersDiff window is incremented.\r\n          (Note that if VersDiff is currently doing a cvs diff, then\r\n          the cvs revision is incremented\/decremented)\r\n\r\n      If [arg] is \"-c\", then any current VersDiff window is closed.\r\n\r\nHINTS:\r\n   If you use GNU 'ls', then try adding \"-I'*.clean'\" (without the\r\n   double quotes) to your 'ls' alias (assuming &patchmode==.clean)\r\n\r\n   It's also helpful to have the patchmode value in the backupskip,\r\n   suffixes, and wildignore vim options:\r\n\r\n      :exe \"set backupskip+=*\" . &patchmode\r\n      :exe \"set suffixes+=\" . &patchmode\r\n      :exe \"set wildignore+=*\" . &patchmode\r\n\r\n   Also, here are some nice mappings that allow quick comparison\r\n   of the current file with previous versions.  Pressing <F5>\r\n   successively shows the diff with older versions.\r\n\r\n      \" <F5> decrease version viewed in VersDiff window\r\n      \" <F6> increase version viewed in VersDiff window\r\n      \" <F7> do VersDiff with cvs version of current file\r\n      \" <F8> cancel VersDiff window\r\n      nmap <silent> <F5> :VersDiff -<cr>\r\n      nmap <silent> <F6> :VersDiff +<cr>\r\n      nmap <silent> <F7> :VersDiff -cvs<cr>\r\n      nmap <silent> <F8> :VersDiff -c<cr>","install_details":"Save the plugin as $VIMRUNTIME\/plugin\/savevers.vim\r\nand you're good to go.  The default settings should\r\nwork fine for most people, but to enable it, the following\r\nsettings (put in .vimrc) should get you started:\r\n\r\n       set backup\r\n       set patchmode=.clean\r\n\r\nThis plugin can be configured by setting the following\r\nvariables in \".vimrc\"\r\n\r\n   savevers_types     - This is a comma-separated list of filename\r\n                        patterns.  Sets the types of files that\r\n                        will have numbered versions.\r\n                        Defaults to \"*\" (all files).\r\n\r\n   savevers_max       - Sets the maximum patchmode version.\r\n                        Defaults to \"9999\".\r\n\r\n   savevers_purge     - Sets default value of [N] for the :Purge command\r\n                        Defaults to \"1\".\r\n\r\n   savevers_dirs      - This is a comma-separated list of directories\r\n                        that will be tried to store the patchmode files.\r\n                        The first writable directory in this list is used.\r\n                        This works much like the vim 'backupdir' option.\r\n                        To set this to the same as 'backupdir', do\r\n                           :let savevers_dirs = &backupdir\r\n                        Defaults to '.', which puts all patchmode files\r\n                        in the same directory as the original file.\r\n\r\n   versdiff_no_resize - Disables window resizing during \":VersDiff\"\r\n\r\n   versdiff_max_cols  - Limits window resizing during \":VersDiff\"\r\n\r\nSo, for example, if the user has in ~\/.vimrc:\r\n   let savevers_types = \"*.c,*.h,*.vim\"\r\n   let savevers_max = 99\r\n   let savevers_purge = 0\r\nthen only \"*.c\", \"*.h\", and \"*.vim\" files will be numbered,\r\nand there will be a maximum of 99 versions saved.\r\nAlso, the \":Purge\" command will purge all numbered versions\r\n(instead of the default, which is to delete all but the oldest).\r\n","5":"Save the plugin as $VIMRUNTIME\/plugin\/savevers.vim\r\nand you're good to go.  The default settings should\r\nwork fine for most people, but to enable it, the following\r\nsettings (put in .vimrc) should get you started:\r\n\r\n       set backup\r\n       set patchmode=.clean\r\n\r\nThis plugin can be configured by setting the following\r\nvariables in \".vimrc\"\r\n\r\n   savevers_types     - This is a comma-separated list of filename\r\n                        patterns.  Sets the types of files that\r\n                        will have numbered versions.\r\n                        Defaults to \"*\" (all files).\r\n\r\n   savevers_max       - Sets the maximum patchmode version.\r\n                        Defaults to \"9999\".\r\n\r\n   savevers_purge     - Sets default value of [N] for the :Purge command\r\n                        Defaults to \"1\".\r\n\r\n   savevers_dirs      - This is a comma-separated list of directories\r\n                        that will be tried to store the patchmode files.\r\n                        The first writable directory in this list is used.\r\n                        This works much like the vim 'backupdir' option.\r\n                        To set this to the same as 'backupdir', do\r\n                           :let savevers_dirs = &backupdir\r\n                        Defaults to '.', which puts all patchmode files\r\n                        in the same directory as the original file.\r\n\r\n   versdiff_no_resize - Disables window resizing during \":VersDiff\"\r\n\r\n   versdiff_max_cols  - Limits window resizing during \":VersDiff\"\r\n\r\nSo, for example, if the user has in ~\/.vimrc:\r\n   let savevers_types = \"*.c,*.h,*.vim\"\r\n   let savevers_max = 99\r\n   let savevers_purge = 0\r\nthen only \"*.c\", \"*.h\", and \"*.vim\" files will be numbered,\r\nand there will be a maximum of 99 versions saved.\r\nAlso, the \":Purge\" command will purge all numbered versions\r\n(instead of the default, which is to delete all but the oldest).\r\n","first_name":"Ed","6":"Ed","last_name":"Ralston","7":"Ralston","releases":[{"0":"89","vim_version":"6.0","1":"6.0","script_version":"0.8","2":"0.8","version_comment":"Corrected some obscure documentation.  Allow cvs revisions to be incremented\/decremented.","3":"Corrected some obscure documentation.  Allow cvs revisions to be incremented\/decremented.","package":"savevers.vim","4":"savevers.vim","src_id":"261","5":"261","creation_date":"1002717972","6":"1002717972"},{"0":"89","vim_version":"6.0","1":"6.0","script_version":"0.7","2":"0.7","version_comment":"Added option to specify directory for patchmode files","3":"Added option to specify directory for patchmode files","package":"savevers.vim","4":"savevers.vim","src_id":"227","5":"227","creation_date":"1002028083","6":"1002028083"},{"0":"89","vim_version":"6.0","1":"6.0","script_version":"0.6","2":"0.6","version_comment":"\":VersDiff\" command improvements","3":"\":VersDiff\" command improvements","package":"savevers.vim","4":"savevers.vim","src_id":"212","5":"212","creation_date":"1001923586","6":"1001923586"},{"0":"89","vim_version":"6.0","1":"6.0","script_version":"0.5","2":"0.5","version_comment":"Added \":VersDiff\" command.","3":"Added \":VersDiff\" command.","package":"savevers.vim","4":"savevers.vim","src_id":"211","5":"211","creation_date":"1001922280","6":"1001922280"},{"0":"89","vim_version":"6.0","1":"6.0","script_version":"0.4","2":"0.4","version_comment":"Added \"-a\" and \"-v\" flags to the \":Purge\" command.","3":"Added \"-a\" and \"-v\" flags to the \":Purge\" command.","package":"savevers.vim","4":"savevers.vim","src_id":"196","5":"196","creation_date":"1001495881","6":"1001495881"},{"0":"89","vim_version":"6.0","1":"6.0","script_version":"0.3","2":"0.3","version_comment":"Added configuration options","3":"Added configuration options","package":"savevers.vim","4":"savevers.vim","src_id":"192","5":"192","creation_date":"1001419308","6":"1001419308"},{"0":"89","vim_version":"6.0","1":"6.0","script_version":"0.2","2":"0.2","version_comment":"allow up to 9999 numbered versions\r\n","3":"allow up to 9999 numbered versions\r\n","package":"savevers.vim","4":"savevers.vim","src_id":"191","5":"191","creation_date":"1001397561","6":"1001397561"},{"0":"89","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"savevers.vim","4":"savevers.vim","src_id":"178","5":"178","creation_date":"1000986955","6":"1000986955"}]},"88":{"script_id":"88","0":"88","script_name":"vimtips.zip","1":"vimtips.zip","script_type":"utility","2":"utility","summary":"Display a helpful tip the first time you start Vim each day.","3":"Display a helpful tip the first time you start Vim each day.","description":"     Whenever you start Vim (but no more than daily) the script will open a\r\nhelp window with a Vim tip. You must download the tips separately, from\r\nhttp:\/\/vim.sourceforge.net\/tips\/tip_download.php\r\n\r\n    After installation, you can get the next tip with\r\n\r\n:TipOfTheDay\r\n\r\n(usual abbreviation rules apply) or go to the top of the tips file with\r\n\r\n:help vimtips.txt","4":"     Whenever you start Vim (but no more than daily) the script will open a\r\nhelp window with a Vim tip. You must download the tips separately, from\r\nhttp:\/\/vim.sourceforge.net\/tips\/tip_download.php\r\n\r\n    After installation, you can get the next tip with\r\n\r\n:TipOfTheDay\r\n\r\n(usual abbreviation rules apply) or go to the top of the tips file with\r\n\r\n:help vimtips.txt","install_details":"1. Unpack totd.zip into a directory in your |runtimepath|.  For most users,\r\nthis typically means ~\/.vim or $HOME\/vimfiles or $VIM\/vimfiles .  This will\r\ncreate files\r\n\tplugin\/totd.vim\t(the plugin)\r\n\tdoc\/totd.txt\t(the docs)\r\n\tplugin\/vimtips\/vimtips.txt\t(skeleton tips file)\r\n\r\n2a. The easiest thing may be to restart vim, either right now or whenever you\r\nget around to it.  Then totd.vim will automatically run |:helptags|, edit the\r\ntags file, and open the skeleton vimtips file.\r\n\r\n2b. If you want to finish the installation right now, without restarting vim,\r\nsimply source the totd.vim file and get a tip:\r\n\r\n\t:source path\/to\/totd.vim\r\n\t:TipOfTheDay\r\n\r\n3. The totd.vim plugin will open the skeleton vimtips file in a help window.\r\nFollow the URL there to download a real vimtips file.\r\n\r\n4. As with any plugin that comes with documentation, you should run\r\n\r\n\t:helptags path\/to\/doc\r\n\r\nso that you can read the documentation with\r\n\r\n\t:help totd\r\n\t:help Tip","5":"1. Unpack totd.zip into a directory in your |runtimepath|.  For most users,\r\nthis typically means ~\/.vim or $HOME\/vimfiles or $VIM\/vimfiles .  This will\r\ncreate files\r\n\tplugin\/totd.vim\t(the plugin)\r\n\tdoc\/totd.txt\t(the docs)\r\n\tplugin\/vimtips\/vimtips.txt\t(skeleton tips file)\r\n\r\n2a. The easiest thing may be to restart vim, either right now or whenever you\r\nget around to it.  Then totd.vim will automatically run |:helptags|, edit the\r\ntags file, and open the skeleton vimtips file.\r\n\r\n2b. If you want to finish the installation right now, without restarting vim,\r\nsimply source the totd.vim file and get a tip:\r\n\r\n\t:source path\/to\/totd.vim\r\n\t:TipOfTheDay\r\n\r\n3. The totd.vim plugin will open the skeleton vimtips file in a help window.\r\nFollow the URL there to download a real vimtips file.\r\n\r\n4. As with any plugin that comes with documentation, you should run\r\n\r\n\t:helptags path\/to\/doc\r\n\r\nso that you can read the documentation with\r\n\r\n\t:help totd\r\n\t:help Tip","first_name":"Benji","6":"Benji","last_name":"Fisher","7":"Fisher","releases":[{"0":"88","vim_version":"6.0","1":"6.0","script_version":"2.2.2","2":"2.2.2","version_comment":"I applied a patch from Bill McCarthy:  set the 'linebreak' option in the help window in case there are tips with long lines, and add :silent when updating the line number.","3":"I applied a patch from Bill McCarthy:  set the 'linebreak' option in the help window in case there are tips with long lines, and add :silent when updating the line number.","package":"vimtips.zip","4":"vimtips.zip","src_id":"5969","5":"5969","creation_date":"1153292170","6":"1153292170"},{"0":"88","vim_version":"5.7","1":"5.7","script_version":"2.2.1","2":"2.2.1","version_comment":"No new functionality:  I just updated the URL for getting a tips archive.","3":"No new functionality:  I just updated the URL for getting a tips archive.","package":"vimtips.zip","4":"vimtips.zip","src_id":"5526","5":"5526","creation_date":"1144300221","6":"1144300221"},{"0":"88","vim_version":"6.0","1":"6.0","script_version":"2.2","2":"2.2","version_comment":"     I changed the way that the script edits files.  Installation should be slightly smoother, and in rare cases opening the tips should be better.\r\n     In previous versions, I accidentally included a moderately large, very old, tips file instead of a skeleton vimtips.txt.  This version contains a small skeleton file.","3":"     I changed the way that the script edits files.  Installation should be slightly smoother, and in rare cases opening the tips should be better.\r\n     In previous versions, I accidentally included a moderately large, very old, tips file instead of a skeleton vimtips.txt.  This version contains a small skeleton file.","package":"vimtips.zip","4":"vimtips.zip","src_id":"1452","5":"1452","creation_date":"1037953297","6":"1037953297"},{"0":"88","vim_version":"6.0","1":"6.0","script_version":"2.1.1","2":"2.1.1","version_comment":"I fixed a tiny, silly bug that probably would never cause a problem anyway.  (OK, if \"vimtips.txs\" is in your tags file, the binary search would screw up.)","3":"I fixed a tiny, silly bug that probably would never cause a problem anyway.  (OK, if \"vimtips.txs\" is in your tags file, the binary search would screw up.)","package":"vimtips.zip","4":"vimtips.zip","src_id":"1439","5":"1439","creation_date":"1037759403","6":"1037759403"},{"0":"88","vim_version":"6.0","1":"6.0","script_version":"2.1","2":"2.1","version_comment":"Do not run :helptags automatically.  The user should install the docs (totd.txt) himself.  The tag for vimtips.txt is still inserted automatically.\r\nReason:  as long as this is the only script that automatically edits the tags file, there is no problem, but what if someone else tries the same trick?  Each script runs :helptags, wiping out the other's customization, ...","3":"Do not run :helptags automatically.  The user should install the docs (totd.txt) himself.  The tag for vimtips.txt is still inserted automatically.\r\nReason:  as long as this is the only script that automatically edits the tags file, there is no problem, but what if someone else tries the same trick?  Each script runs :helptags, wiping out the other's customization, ...","package":"vimtips.zip","4":"vimtips.zip","src_id":"1436","5":"1436","creation_date":"1037712768","6":"1037712768"},{"0":"88","vim_version":"6.0","1":"6.0","script_version":"2.0","2":"2.0","version_comment":"This is almost a total rewrite.  Installation is simpler, start-up is faster,\r\nand I added a command\r\n\r\n:TipOfTheDay\r\n\r\n(or :Tip if that does not conflict with anything else, thanks to usual\r\nabbreviation rules) to get a tip on demand.","3":"This is almost a total rewrite.  Installation is simpler, start-up is faster,\r\nand I added a command\r\n\r\n:TipOfTheDay\r\n\r\n(or :Tip if that does not conflict with anything else, thanks to usual\r\nabbreviation rules) to get a tip on demand.","package":"vimtips.zip","4":"vimtips.zip","src_id":"1434","5":"1434","creation_date":"1037679074","6":"1037679074"},{"0":"88","vim_version":"6.0","1":"6.0","script_version":"1.1","2":"1.1","version_comment":"Bug fix:  Be more graceful if :helptag has not yet been used.  (See the\r\ninstallation intructions!)","3":"Bug fix:  Be more graceful if :helptag has not yet been used.  (See the\r\ninstallation intructions!)","package":"vimtips.zip","4":"vimtips.zip","src_id":"177","5":"177","creation_date":"1000974874","6":"1000974874"},{"0":"88","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"vimtips.zip","4":"vimtips.zip","src_id":"176","5":"176","creation_date":"1000973416","6":"1000973416"}]},"87":{"script_id":"87","0":"87","script_name":"plkeyb.vim","1":"plkeyb.vim","script_type":"utility","2":"utility","summary":"Polish dead-key keyboard emulation","3":"Polish dead-key keyboard emulation","description":"Polish letters in iso-8859-2 encoding. \r\nPress \"~\" (tilde), then [ACELNOSZXacelnoszx] to insert polish equiv.\r\nNEW :\r\n'keymap' version. Unzip the file in your $VIMRUNTIME\/keymap or $HOME\/.vim\/keymap directory.\r\nYou'll be able to select the new 'polish' keymap from Edit\/Keymap menu.\r\nActivate with Edit\/Keymap\/polish or :set keymap=polish.\r\n","4":"Polish letters in iso-8859-2 encoding. \r\nPress \"~\" (tilde), then [ACELNOSZXacelnoszx] to insert polish equiv.\r\nNEW :\r\n'keymap' version. Unzip the file in your $VIMRUNTIME\/keymap or $HOME\/.vim\/keymap directory.\r\nYou'll be able to select the new 'polish' keymap from Edit\/Keymap menu.\r\nActivate with Edit\/Keymap\/polish or :set keymap=polish.\r\n","install_details":"copy this into your ~\/.vim\/keymap directory  (or use system-wide keymap dir).\r\nOf course you'll have to set the proper screen font (supporting iso8859-2 or UTF-8 encoding)","5":"copy this into your ~\/.vim\/keymap directory  (or use system-wide keymap dir).\r\nOf course you'll have to set the proper screen font (supporting iso8859-2 or UTF-8 encoding)","first_name":"Rafal","6":"Rafal","last_name":"Sulejman","7":"Sulejman","releases":[{"0":"87","vim_version":"6.0","1":"6.0","script_version":"2.10","2":"2.10","version_comment":"Hopefully a bit better version. I can edit (ON MY SYSTEM -- YMMV -- pls report) utf-8 and iso-8859-2 files now. Check your *encodings...","3":"Hopefully a bit better version. I can edit (ON MY SYSTEM -- YMMV -- pls report) utf-8 and iso-8859-2 files now. Check your *encodings...","package":"polish_keymap.zip","4":"polish_keymap.zip","src_id":"2022","5":"2022","creation_date":"1054026495","6":"1054026495"}]},"86":{"script_id":"86","0":"86","script_name":"brief.vim","1":"brief.vim","script_type":"utility","2":"utility","summary":"Plugin for Brief-style Home and End","3":"Plugin for Brief-style Home and End","description":"Pressing \"Home\" successively puts you at the beginning of the current line, beginning of the screen, and the beginning of the file.  \r\nSimilarly, for \"End\".\r\n","4":"Pressing \"Home\" successively puts you at the beginning of the current line, beginning of the screen, and the beginning of the file.  \r\nSimilarly, for \"End\".\r\n","install_details":"drop into your vim plugin directory","5":"drop into your vim plugin directory","first_name":"Ed","6":"Ed","last_name":"Ralston","7":"Ralston","releases":[{"0":"86","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"brief.vim","4":"brief.vim","src_id":"173","5":"173","creation_date":"1000886895","6":"1000886895"}]},"85":{"script_id":"85","0":"85","script_name":"Mkcolorscheme.vim","1":"Mkcolorscheme.vim","script_type":"utility","2":"utility","summary":"Help write colorscheme files from existing settings","3":"Help write colorscheme files from existing settings","description":"This is a simple script to help turn your existing highlight settings into a vim colorscheme file.","4":"This is a simple script to help turn your existing highlight settings into a vim colorscheme file.","install_details":"1. drop into your plugin directory\r\n2. set up your colorscheme they way you want\r\n3. :Mkcolorscheme [scheme-name]  (If you don't supply a scheme-name you will be prompted for one)\r\n4. review and save to colors\/<name>.vim\r\n","5":"1. drop into your plugin directory\r\n2. set up your colorscheme they way you want\r\n3. :Mkcolorscheme [scheme-name]  (If you don't supply a scheme-name you will be prompted for one)\r\n4. review and save to colors\/<name>.vim\r\n","first_name":"Travis","6":"Travis","last_name":"Hume","7":"Hume","releases":[{"0":"85","vim_version":"6.0","1":"6.0","script_version":"0.06","2":"0.06","version_comment":"New command signature\r\n     Mkcolorscheme[!] [scheme-name]\r\n\r\nIf invoked with a ! then the generated colorscheme file is automatically written to ~\/.vim\/colors\/<scheme-name>.vim if possible.  Only works with has(\"unix\") for now, feel free to fix this.\r\n\r\nThe included :command is no longer commented out and properly invokes the Mkcolorscheme() function with the <bang> syntax.","3":"New command signature\r\n     Mkcolorscheme[!] [scheme-name]\r\n\r\nIf invoked with a ! then the generated colorscheme file is automatically written to ~\/.vim\/colors\/<scheme-name>.vim if possible.  Only works with has(\"unix\") for now, feel free to fix this.\r\n\r\nThe included :command is no longer commented out and properly invokes the Mkcolorscheme() function with the <bang> syntax.","package":"Mkcolorscheme.vim","4":"Mkcolorscheme.vim","src_id":"748","5":"748","creation_date":"1017769056","6":"1017769056"},{"0":"85","vim_version":"6.0","1":"6.0","script_version":"0.05","2":"0.05","version_comment":"No functionality changes.  Just some documentation, including some very helpful :commands to help with modifying or creating colorschemes.","3":"No functionality changes.  Just some documentation, including some very helpful :commands to help with modifying or creating colorschemes.","package":"Mkcolorscheme.vim","4":"Mkcolorscheme.vim","src_id":"728","5":"728","creation_date":"1017393216","6":"1017393216"}]},"84":{"script_id":"84","0":"84","script_name":"gdbvim.tar.gz","1":"gdbvim.tar.gz","script_type":"utility","2":"utility","summary":"Watch in vim what you debug in gdb. And more.","3":"Watch in vim what you debug in gdb. And more.","description":"You have one window with (g)vim open, other window with gdb running. When you reach source line in your code, it appears in the vim window. In the opposite direction, you can send commands from vim to gdb (e.g., set breakpoints on given line).\r\n\r\nYou  may want to look at vimtip #357. I did not test that, but it may ease your work with this script.\r\n\r\nIt is possible that slightly fixed version and more on-line information is at http:\/\/www.volny.cz\/zellerin\/gdbvim\/ .","4":"You have one window with (g)vim open, other window with gdb running. When you reach source line in your code, it appears in the vim window. In the opposite direction, you can send commands from vim to gdb (e.g., set breakpoints on given line).\r\n\r\nYou  may want to look at vimtip #357. I did not test that, but it may ease your work with this script.\r\n\r\nIt is possible that slightly fixed version and more on-line information is at http:\/\/www.volny.cz\/zellerin\/gdbvim\/ .","install_details":"You need X running and recent version of vim with +signs and +clientserver\r\n\r\nExtract files from archiv; gdbvim is executable, gdbvim.vim should go to your plugin directory and gdbvim.txt to your local help directory. See :he add-plugin and :he add-local-help.","5":"You need X running and recent version of vim with +signs and +clientserver\r\n\r\nExtract files from archiv; gdbvim is executable, gdbvim.vim should go to your plugin directory and gdbvim.txt to your local help directory. See :he add-plugin and :he add-local-help.","first_name":"Tomas","6":"Tomas","last_name":"Zellerin","7":"Zellerin","releases":[{"0":"84","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"gdbvim.tar.gz","4":"gdbvim.tar.gz","src_id":"167","5":"167","creation_date":"1000363857","6":"1000363857"}]},"83":{"script_id":"83","0":"83","script_name":"let-modeline.vim","1":"let-modeline.vim","script_type":"utility","2":"utility","summary":"Extends the modeline feature to the assignment of variables","3":"Extends the modeline feature to the assignment of variables","description":"The file defines the function FirstModeLine().\r\n\r\nIts purpose is very simple. It consists in extending VIM modelines (:h modeline for more info) to custom variables -- these variables can then be used to customize other VIM scripts.\r\n\r\nFor instance, if your file foo.vim has as one of its first or last lines:\r\n   \" VIM: let b:toto=\"foo\" g:tata=4 g:egal=\"t=y\".&tw $CPPFLAG='-I..\/..\/libs'\r\nThen, once the buffer is (re)loaded, one buffer relative variable (b:toto) and two global variables (g:tata and g:egal) are defined to the value specified after the equal sign.\r\n\r\nPersonnaly, I use it in conjunction with tex-tools.vim in order to know the name of the main file of the current document and then call latex on the main file and not on the currently edited file -- I use intensively \\\\include{} and \\\\includeonly{}.\r\n\r\nRegarding the security issue, the script forbids calls to functions in the right hand operand -- it prevents from trojans. Nevertheless, it is possible to call functions thanks to a buffer relative callback feature. This time, only one function could be called. Trojans are still possible if the callback functions (that you have accepted in your configuration) want it to be possible -- like calling a function named after the value passed in parameter... \r\nThe callback feature has been implemented to be used in conjunction with ftplugins ; cf. tex-maps.vim and tex-tools.vim on my Web site:\r\n    http:\/\/hermitte.free.fr\/vim\/tex.php\r\n\r\nNote: The version 1.5 is the last one which can be used with Vim 5.x.","4":"The file defines the function FirstModeLine().\r\n\r\nIts purpose is very simple. It consists in extending VIM modelines (:h modeline for more info) to custom variables -- these variables can then be used to customize other VIM scripts.\r\n\r\nFor instance, if your file foo.vim has as one of its first or last lines:\r\n   \" VIM: let b:toto=\"foo\" g:tata=4 g:egal=\"t=y\".&tw $CPPFLAG='-I..\/..\/libs'\r\nThen, once the buffer is (re)loaded, one buffer relative variable (b:toto) and two global variables (g:tata and g:egal) are defined to the value specified after the equal sign.\r\n\r\nPersonnaly, I use it in conjunction with tex-tools.vim in order to know the name of the main file of the current document and then call latex on the main file and not on the currently edited file -- I use intensively \\\\include{} and \\\\includeonly{}.\r\n\r\nRegarding the security issue, the script forbids calls to functions in the right hand operand -- it prevents from trojans. Nevertheless, it is possible to call functions thanks to a buffer relative callback feature. This time, only one function could be called. Trojans are still possible if the callback functions (that you have accepted in your configuration) want it to be possible -- like calling a function named after the value passed in parameter... \r\nThe callback feature has been implemented to be used in conjunction with ftplugins ; cf. tex-maps.vim and tex-tools.vim on my Web site:\r\n    http:\/\/hermitte.free.fr\/vim\/tex.php\r\n\r\nNote: The version 1.5 is the last one which can be used with Vim 5.x.","install_details":"Drop this file into your {rtp}\/plugin\/ directory. let-modeline is also shipped with lh-misc.\r\n\r\nIn any case prefer to install the version from https:\/\/github.com\/LucHermitte\/lh-misc\/blob\/master\/plugin\/let-modeline.vim","5":"Drop this file into your {rtp}\/plugin\/ directory. let-modeline is also shipped with lh-misc.\r\n\r\nIn any case prefer to install the version from https:\/\/github.com\/LucHermitte\/lh-misc\/blob\/master\/plugin\/let-modeline.vim","first_name":"Luc","6":"Luc","last_name":"Hermitte","7":"Hermitte","releases":[{"0":"83","vim_version":"6.0","1":"6.0","script_version":"1.9","2":"1.9","version_comment":"The latest version.","3":"The latest version.","package":"let-modeline.vim","4":"let-modeline.vim","src_id":"23079","5":"23079","creation_date":"1426976330","6":"1426976330"}]},"82":{"script_id":"82","0":"82","script_name":"AppendComment.vim","1":"AppendComment.vim","script_type":"utility","2":"utility","summary":"Append comment at end of line","3":"Append comment at end of line","description":"One thing I liked in Emacs is the ability to insert comments\r\nat the end of line using <M-;>. \r\nThis script tries to achieve the same for Vim.\r\nIf there's already a comment, it's aligned.\r\n\r\nMaybe, your language is supported. \r\nIf not, it's easy to add new ones.\r\n\r\nThis script was inspired by Meikel Brandmeyers EnhCommentify.vim: vimscript#23","4":"One thing I liked in Emacs is the ability to insert comments\r\nat the end of line using <M-;>. \r\nThis script tries to achieve the same for Vim.\r\nIf there's already a comment, it's aligned.\r\n\r\nMaybe, your language is supported. \r\nIf not, it's easy to add new ones.\r\n\r\nThis script was inspired by Meikel Brandmeyers EnhCommentify.vim: vimscript#23","install_details":"Put it in your ~\/.vim\/plugin","5":"Put it in your ~\/.vim\/plugin","first_name":"Johannes","6":"Johannes","last_name":"Tanzler","7":"Tanzler","releases":[{"0":"82","vim_version":"6.0","1":"6.0","script_version":"0.02","2":"0.02","version_comment":"Bugfixing\r\nIf line is empty, the comment is\r\ninserted according to current\r\nindentation.","3":"Bugfixing\r\nIf line is empty, the comment is\r\ninserted according to current\r\nindentation.","package":"AppendComment.vim","4":"AppendComment.vim","src_id":"174","5":"174","creation_date":"1000907854","6":"1000907854"},{"0":"82","vim_version":"6.0","1":"6.0","script_version":"0.01","2":"0.01","version_comment":"Initial upload","3":"Initial upload","package":"AppendComment.vim","4":"AppendComment.vim","src_id":"164","5":"164","creation_date":"1000307631","6":"1000307631"}]},"81":{"script_id":"81","0":"81","script_name":"translate.vim","1":"translate.vim","script_type":"utility","2":"utility","summary":"Look up a word in a dictionary file","3":"Look up a word in a dictionary file","description":"This script looks up a word in a\r\ndictionary file using egrep (you can change this to grep, of course).\r\nWhen the word was found, a new window with the search results is opened at the bottom of the screen.\r\n\r\nThis script was inspired by Emacs' translate.el.","4":"This script looks up a word in a\r\ndictionary file using egrep (you can change this to grep, of course).\r\nWhen the word was found, a new window with the search results is opened at the bottom of the screen.\r\n\r\nThis script was inspired by Emacs' translate.el.","install_details":"Put this script in your ~\/.vim\/plugin directory","5":"Put this script in your ~\/.vim\/plugin directory","first_name":"Johannes","6":"Johannes","last_name":"Tanzler","7":"Tanzler","releases":[{"0":"81","vim_version":"6.0","1":"6.0","script_version":"0.01","2":"0.01","version_comment":"Initial upload","3":"Initial upload","package":"translate.vim","4":"translate.vim","src_id":"162","5":"162","creation_date":"1000200485","6":"1000200485"}]},"80":{"script_id":"80","0":"80","script_name":"files2menu.pm","1":"files2menu.pm","script_type":"utility","2":"utility","summary":"add all files recursively as menu entry","3":"add all files recursively as menu entry","description":"DESCR     finds files according to predefined file masks in all subdirs starting in parent dir (default).\r\n\tcreates menu commands for gvim for each file found (creates submenues automatically after 40 menu entries).\r\n\tfilemasks and other settings may be easily changed within the perl script for your needs.\r\n\r\n\tUsage: \tfiles2menu.pm <options>\r\n\toptions:\r\n\t                    \tgenerate file list on stdout (default)\r\n\t -o <filelist>      \tgenerate filelist in file <filelist>\r\n\t -v                 \tgenerate VIM scriptfile\r\n\t -v <scriptfile>    \tgenerate VIM Scriptfile <scriptfile>\r\n\t -f <patternlist>   \tuse search pattern <patternlist>\r\n\t\t                predefined pattern lists:   CPP, EXE, MAK, GL, DOC, VIM\r\n\t -m                 \tcreate menu entry <menuEntry> for each found file  (blanks allowed in name)\r\n\t -c                 \tcreate submenu after <n> entries\r\n\t -d                 \tdebug mode\r\n\t -s <startdir>      \tstart in CWD (default) or parent dir ('..') or <startdir>\r\n\r\n\r\nI used 'ls' because any other tools had trouble with that genious system of long file names under Windows and Novell.","4":"DESCR     finds files according to predefined file masks in all subdirs starting in parent dir (default).\r\n\tcreates menu commands for gvim for each file found (creates submenues automatically after 40 menu entries).\r\n\tfilemasks and other settings may be easily changed within the perl script for your needs.\r\n\r\n\tUsage: \tfiles2menu.pm <options>\r\n\toptions:\r\n\t                    \tgenerate file list on stdout (default)\r\n\t -o <filelist>      \tgenerate filelist in file <filelist>\r\n\t -v                 \tgenerate VIM scriptfile\r\n\t -v <scriptfile>    \tgenerate VIM Scriptfile <scriptfile>\r\n\t -f <patternlist>   \tuse search pattern <patternlist>\r\n\t\t                predefined pattern lists:   CPP, EXE, MAK, GL, DOC, VIM\r\n\t -m                 \tcreate menu entry <menuEntry> for each found file  (blanks allowed in name)\r\n\t -c                 \tcreate submenu after <n> entries\r\n\t -d                 \tdebug mode\r\n\t -s <startdir>      \tstart in CWD (default) or parent dir ('..') or <startdir>\r\n\r\n\r\nI used 'ls' because any other tools had trouble with that genious system of long file names under Windows and Novell.","install_details":"Add a line like the following to your _gvimrc. You will get a menu entry which creates new submenues\r\nwith an entry for each C\/C++ file found in all paralell directories and below.\r\n\r\n'menu 12.10 Proj.Add\\ source\\ files\\ recursiv\t\t:exec(\"!perl \".$VIMRUNTIME.\"\/syntax\/files2Menu.pm -f CPP\")<CR>:so! files.vim<CR>'\r\n\r\nIt works fine with Perl (Version 5005_3), ls (GNU fileutils) 3.16 and gvim 5.8\r\n\r\n","5":"Add a line like the following to your _gvimrc. You will get a menu entry which creates new submenues\r\nwith an entry for each C\/C++ file found in all paralell directories and below.\r\n\r\n'menu 12.10 Proj.Add\\ source\\ files\\ recursiv\t\t:exec(\"!perl \".$VIMRUNTIME.\"\/syntax\/files2Menu.pm -f CPP\")<CR>:so! files.vim<CR>'\r\n\r\nIt works fine with Perl (Version 5005_3), ls (GNU fileutils) 3.16 and gvim 5.8\r\n\r\n","first_name":"thomas","6":"thomas","last_name":"ramming","7":"ramming","releases":[{"0":"80","vim_version":"5.7","1":"5.7","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"files2menu.pm","4":"files2menu.pm","src_id":"156","5":"156","creation_date":"999732752","6":"999732752"}]},"79":{"script_id":"79","0":"79","script_name":"wordlist.vim","1":"wordlist.vim","script_type":"utility","2":"utility","summary":"Autocorrect wordlist from Office XP","3":"Autocorrect wordlist from Office XP","description":"When Vim parses this file it will give you autocorrection of words (\"andthe\" becomes \"and the\").","4":"When Vim parses this file it will give you autocorrection of words (\"andthe\" becomes \"and the\").","install_details":"I just put a line in my _vimrc file like so: source $VIMRUNTIME\/plugin\/wordlist.vim\r\n","5":"I just put a line in my _vimrc file like so: source $VIMRUNTIME\/plugin\/wordlist.vim\r\n","first_name":"Robert","6":"Robert","last_name":"Hicks","7":"Hicks","releases":[{"0":"79","vim_version":"6.0","1":"6.0","script_version":"1.01","2":"1.01","version_comment":"Just changed some comments to give the person who did the actual \r\nconversion due credit. There is also a website that you can check\r\nfor updated wordlist.vim files.","3":"Just changed some comments to give the person who did the actual \r\nconversion due credit. There is also a website that you can check\r\nfor updated wordlist.vim files.","package":"wordlist.vim","4":"wordlist.vim","src_id":"158","5":"158","creation_date":"999774864","6":"999774864"},{"0":"79","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"wordlist.vim","4":"wordlist.vim","src_id":"153","5":"153","creation_date":"999666194","6":"999666194"}]},"78":{"script_id":"78","0":"78","script_name":"functags.vim","1":"functags.vim","script_type":"utility","2":"utility","summary":"create menu entries for each function definition in a C\/C++ file","3":"create menu entries for each function definition in a C\/C++ file","description":"This script generates menu entries for each C\/C++ function definition within the actual edited C\/C++ file.\r\nAfter executing it, you can move to any of the functions by selecting them via menu.\r\n\r\n- adds a menu entry under a main menu 'Proj'\r\n- creates a file cfunctags.vim as script for generating the menu entries\r\n\r\nBUGS: does not handle references ('&') and destructors (~) correctly.\r\n           If anyone would add these, please let me know.\r\n\r\nThe script is just quick and (hope not very) dirty written, but working (only short tests up to now)\r\nunder GVIM 5.8, NT4.0, Novell network\r\n\r\n","4":"This script generates menu entries for each C\/C++ function definition within the actual edited C\/C++ file.\r\nAfter executing it, you can move to any of the functions by selecting them via menu.\r\n\r\n- adds a menu entry under a main menu 'Proj'\r\n- creates a file cfunctags.vim as script for generating the menu entries\r\n\r\nBUGS: does not handle references ('&') and destructors (~) correctly.\r\n           If anyone would add these, please let me know.\r\n\r\nThe script is just quick and (hope not very) dirty written, but working (only short tests up to now)\r\nunder GVIM 5.8, NT4.0, Novell network\r\n\r\n","install_details":"Create a menu entry in your _gvimrc to source in and call this script:\r\n\"($VIM_SYNTAX must contain the path to this script file)\r\n'menu 12.10 Proj.Add\\ local\\ functions\t:so $VIM_SYNTAX\/functags.vim<CR>'\r\n","5":"Create a menu entry in your _gvimrc to source in and call this script:\r\n\"($VIM_SYNTAX must contain the path to this script file)\r\n'menu 12.10 Proj.Add\\ local\\ functions\t:so $VIM_SYNTAX\/functags.vim<CR>'\r\n","first_name":"thomas","6":"thomas","last_name":"ramming","7":"ramming","releases":[{"0":"78","vim_version":"5.7","1":"5.7","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"functags.vim","4":"functags.vim","src_id":"152","5":"152","creation_date":"999646839","6":"999646839"}]},"77":{"script_id":"77","0":"77","script_name":"incfiles.vim","1":"incfiles.vim","script_type":"utility","2":"utility","summary":"create menu entries for each include file in a C\/C++ file","3":"create menu entries for each include file in a C\/C++ file","description":"This script generates menu entries for each include file within the actual edited C\/C++ file.\r\nAfter executing it, you can enter any of the include files by selecting them via menu.\r\n\r\nThe script is just quick and (hope not very) dirty written, but working (only short tests up to now)\r\nunder GVIM 5.8, NT4.0, Novell network\r\n","4":"This script generates menu entries for each include file within the actual edited C\/C++ file.\r\nAfter executing it, you can enter any of the include files by selecting them via menu.\r\n\r\nThe script is just quick and (hope not very) dirty written, but working (only short tests up to now)\r\nunder GVIM 5.8, NT4.0, Novell network\r\n","install_details":"- create menu entry for include file (to enter it) within C\/C++ files\r\n- adds menu entries under main menu 'Proj'\r\ne.g. enter ':% call CreateIncFileMenu()' within your C\/C++ file.\r\nThen you can enter any include file by selecting it in the menu.\r\nCreate a menu entry in your _gvimrc to source in and call this script:\r\n($VIM_SYNTAX must contain the path to this script file)\r\n'menu 12.10 Proj.Add\\ include\\ files\t\t:so $VIM_SYNTAX\/incfiles.vim<CR>:% call CreateIncFileMenu()<CR>'\r\n","5":"- create menu entry for include file (to enter it) within C\/C++ files\r\n- adds menu entries under main menu 'Proj'\r\ne.g. enter ':% call CreateIncFileMenu()' within your C\/C++ file.\r\nThen you can enter any include file by selecting it in the menu.\r\nCreate a menu entry in your _gvimrc to source in and call this script:\r\n($VIM_SYNTAX must contain the path to this script file)\r\n'menu 12.10 Proj.Add\\ include\\ files\t\t:so $VIM_SYNTAX\/incfiles.vim<CR>:% call CreateIncFileMenu()<CR>'\r\n","first_name":"thomas","6":"thomas","last_name":"ramming","7":"ramming","releases":[{"0":"77","vim_version":"5.7","1":"5.7","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"incfiles.vim","4":"incfiles.vim","src_id":"151","5":"151","creation_date":"999646492","6":"999646492"}]},"76":{"script_id":"76","0":"76","script_name":"uri-ref","1":"uri-ref","script_type":"utility","2":"utility","summary":"Easily insert references to URLs in emails","3":"Easily insert references to URLs in emails","description":"Inline URIs in emails make the text around them obscure. This is why I put references to URIs at the bottom of the email.\r\n\r\nThis script provides a prompt to do so in a painless way.\r\n\r\nExamples and documentation are at: http:\/\/larve.net\/people\/hugo\/2001\/02\/email-uri-refs\/","4":"Inline URIs in emails make the text around them obscure. This is why I put references to URIs at the bottom of the email.\r\n\r\nThis script provides a prompt to do so in a painless way.\r\n\r\nExamples and documentation are at: http:\/\/larve.net\/people\/hugo\/2001\/02\/email-uri-refs\/","install_details":"Just stick the script into your plugins directory or your vimrc.\r\n\r\nWhile writing an email, in insert mode, press F5 and follow the instructions.\r\n\r\nNote that your mail has to have a valid signature for the script to work as it's currently written.","5":"Just stick the script into your plugins directory or your vimrc.\r\n\r\nWhile writing an email, in insert mode, press F5 and follow the instructions.\r\n\r\nNote that your mail has to have a valid signature for the script to work as it's currently written.","first_name":"Hugo","6":"Hugo","last_name":"Haas","7":"Haas","releases":[{"0":"76","vim_version":"6.0","1":"6.0","script_version":"20061101","2":"20061101","version_comment":"Fixed typo that triggered a warning in VIM 7 (Dave Roe)","3":"Fixed typo that triggered a warning in VIM 7 (Dave Roe)","package":"uri-ref-20061101.vim","4":"uri-ref-20061101.vim","src_id":"6358","5":"6358","creation_date":"1162340720","6":"1162340720"},{"0":"76","vim_version":"6.0","1":"6.0","script_version":"20040601","2":"20040601","version_comment":"Removed some forgotten debugging code.","3":"Removed some forgotten debugging code.","package":"uri-ref-20040601.vim","4":"uri-ref-20040601.vim","src_id":"3085","5":"3085","creation_date":"1086081034","6":"1086081034"},{"0":"76","vim_version":"6.0","1":"6.0","script_version":"20040528","2":"20040528","version_comment":"Fixed some numbering bugs.","3":"Fixed some numbering bugs.","package":"uri-ref-20040528.vim","4":"uri-ref-20040528.vim","src_id":"3067","5":"3067","creation_date":"1085750755","6":"1085750755"},{"0":"76","vim_version":"5.7","1":"5.7","script_version":"20010910","2":"20010910","version_comment":"InsertRef() and ConvertToRef() were behaving differently with a shiftwidth different from 2.\r\nThis has been fixed","3":"InsertRef() and ConvertToRef() were behaving differently with a shiftwidth different from 2.\r\nThis has been fixed","package":"uri-ref-20010223.vim","4":"uri-ref-20010223.vim","src_id":"161","5":"161","creation_date":"1000152702","6":"1000152702"},{"0":"76","vim_version":"5.7","1":"5.7","script_version":"20010223","2":"20010223","version_comment":"Included URL for documentation.","3":"Included URL for documentation.","package":"uri-ref-20010223.vim","4":"uri-ref-20010223.vim","src_id":"149","5":"149","creation_date":"999531346","6":"999531346"},{"0":"76","vim_version":"5.7","1":"5.7","script_version":"20010223","2":"20010223","version_comment":"Initial upload","3":"Initial upload","package":"uri-ref-20010223.vim","4":"uri-ref-20010223.vim","src_id":"148","5":"148","creation_date":"999530389","6":"999530389"}]},"75":{"script_id":"75","0":"75","script_name":"javaimp.vim","1":"javaimp.vim","script_type":"utility","2":"utility","summary":"Open a Java source file from its import statement","3":"Open a Java source file from its import statement","description":"Set of functions to open a Java import statement as a file.\r\nMaintained by Darren Greaves http:\/\/boncey.org\/showBlog.go?id=138\r\nSuggested stuff to add to your ~.vimrc:\r\nlet $JAVASOURCEPATH=\"$SERVLET_HOME\/src\/share,$JAVA_HOME\/src,$XML_HOME\/src\"\r\nmap H :call OpenJavaImport($JAVASOURCEPATH)<CR>\r\nThen press H while on a import line and the file should open (you'll need the\r\nsource files and the path to have been set already.\r\n\r\nThe paths in $JAVASOURCEPATH should have the source packages directly\r\nunderneath each path.  The script needs to be able to add the package to the\r\npath element and open a file.\r\n","4":"Set of functions to open a Java import statement as a file.\r\nMaintained by Darren Greaves http:\/\/boncey.org\/showBlog.go?id=138\r\nSuggested stuff to add to your ~.vimrc:\r\nlet $JAVASOURCEPATH=\"$SERVLET_HOME\/src\/share,$JAVA_HOME\/src,$XML_HOME\/src\"\r\nmap H :call OpenJavaImport($JAVASOURCEPATH)<CR>\r\nThen press H while on a import line and the file should open (you'll need the\r\nsource files and the path to have been set already.\r\n\r\nThe paths in $JAVASOURCEPATH should have the source packages directly\r\nunderneath each path.  The script needs to be able to add the package to the\r\npath element and open a file.\r\n","install_details":"Vim 6:  Copy to ~\/.vim\/plugin or $VIM\/plugin directory\r\nVim 5 : Copy to $VIM and\r\n- Add \"source $VIM\/javaimp.vim\" to your vimrc ","5":"Vim 6:  Copy to ~\/.vim\/plugin or $VIM\/plugin directory\r\nVim 5 : Copy to $VIM and\r\n- Add \"source $VIM\/javaimp.vim\" to your vimrc ","first_name":"Darren","6":"Darren","last_name":"Greaves","7":"Greaves","releases":[{"0":"75","vim_version":"6.0","1":"6.0","script_version":"0.2","2":"0.2","version_comment":"Fixed broken regex that expected one space between import and package name.\r\nChanged has(\"GUI\") to has(\"gui_running\") as I had this wrong.\r\nUpdated URL for new Web site for downloading.","3":"Fixed broken regex that expected one space between import and package name.\r\nChanged has(\"GUI\") to has(\"gui_running\") as I had this wrong.\r\nUpdated URL for new Web site for downloading.","package":"javaimp.vim","4":"javaimp.vim","src_id":"709","5":"709","creation_date":"1016982784","6":"1016982784"},{"0":"75","vim_version":"5.7","1":"5.7","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"javaimp.vim","4":"javaimp.vim","src_id":"146","5":"146","creation_date":"999439009","6":"999439009"}]},"74":{"script_id":"74","0":"74","script_name":"aux2tags.vim","1":"aux2tags.vim","script_type":"utility","2":"utility","summary":"Generate a tags file from a LaTeX .aux file","3":"Generate a tags file from a LaTeX .aux file","description":"     This script provide a command, :TeXtags, that will generate a tags\r\nfile in the current directory based on a LaTeX .aux file.  If you are editing\r\nthe file foo.tex in the current directory, just type :TeXtags.  You can then\r\nuse Vim's tag functions to display, or jump to, labels in foo.tex.\r\n\r\n     At the moment, this only works for \\label{} commands, not bibliographic\r\ncitations.  TODO:  handle \\bibcite; handle multiple files with \\input lines;\r\nbe more intelligent about directories; escape problematic characters in tags;\r\nuse :silent and <buffer> for Vim 6.0; etc.","4":"     This script provide a command, :TeXtags, that will generate a tags\r\nfile in the current directory based on a LaTeX .aux file.  If you are editing\r\nthe file foo.tex in the current directory, just type :TeXtags.  You can then\r\nuse Vim's tag functions to display, or jump to, labels in foo.tex.\r\n\r\n     At the moment, this only works for \\label{} commands, not bibliographic\r\ncitations.  TODO:  handle \\bibcite; handle multiple files with \\input lines;\r\nbe more intelligent about directories; escape problematic characters in tags;\r\nuse :silent and <buffer> for Vim 6.0; etc.","install_details":"Add \":source aux2tags.vim\" to your vimrc file, or (Vim 6.0) drop in your\r\nplugin directory.  Invoke with\r\n:TeXtags\r\nor\r\n:TeXtags foo.tex","5":"Add \":source aux2tags.vim\" to your vimrc file, or (Vim 6.0) drop in your\r\nplugin directory.  Invoke with\r\n:TeXtags\r\nor\r\n:TeXtags foo.tex","first_name":"Benji","6":"Benji","last_name":"Fisher","7":"Fisher","releases":[{"0":"74","vim_version":"5.7","1":"5.7","script_version":"0.2","2":"0.2","version_comment":"Version 0.2 adds support for multiple LaTeX files using \\include\r\n(but not \\input).  Minor changes:  simplify tag format, add some usage\r\nnotes, warn Vim that the tags are not sorted.","3":"Version 0.2 adds support for multiple LaTeX files using \\include\r\n(but not \\input).  Minor changes:  simplify tag format, add some usage\r\nnotes, warn Vim that the tags are not sorted.","package":"aux2tags.vim","4":"aux2tags.vim","src_id":"157","5":"157","creation_date":"999766562","6":"999766562"},{"0":"74","vim_version":"5.7","1":"5.7","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"aux2tags.vim","4":"aux2tags.vim","src_id":"144","5":"144","creation_date":"999160783","6":"999160783"}]},"73":{"script_id":"73","0":"73","script_name":"word_complete.vim","1":"word_complete.vim","script_type":"utility","2":"utility","summary":"automatically offers word completion as you type","3":"automatically offers word completion as you type","description":"Each time you type an alphabetic character, the script attempts\r\nto complete the current word.  The suggested completion is selected\r\nin Select mode, so you can just type another character to keep going.\r\nOther options:  <Tab> to accept, <BS> to get rid of the completion,\r\n<Esc> to leave Insert mode without accepting the completion, <C-N>\r\nor <C-P> to cycle through choices, <C-X> to enter <C-X> mode.\r\n\r\nLimitations:\r\nThe script works by :imap'ping each alphabetic character, and uses\r\nInsert-mode completion (:help i_ctrl-p).  It is far from perfect.  For example, the :imap's mean that you are constantly switching out of Insert mode, which means that undo only works a few characters at a time.  This also messes up any abbreviations you may have defined.  Since Select mode uses the same mappings as Visual mode, the special keys mentioned above may conflict with what you are used to in Visual mode.  I have received one report that mswin.vim interferes with this script.\r\n\r\nEvery second character you type is in Select mode, so with versions of vim before 6.2, completions are offered only half the time.","4":"Each time you type an alphabetic character, the script attempts\r\nto complete the current word.  The suggested completion is selected\r\nin Select mode, so you can just type another character to keep going.\r\nOther options:  <Tab> to accept, <BS> to get rid of the completion,\r\n<Esc> to leave Insert mode without accepting the completion, <C-N>\r\nor <C-P> to cycle through choices, <C-X> to enter <C-X> mode.\r\n\r\nLimitations:\r\nThe script works by :imap'ping each alphabetic character, and uses\r\nInsert-mode completion (:help i_ctrl-p).  It is far from perfect.  For example, the :imap's mean that you are constantly switching out of Insert mode, which means that undo only works a few characters at a time.  This also messes up any abbreviations you may have defined.  Since Select mode uses the same mappings as Visual mode, the special keys mentioned above may conflict with what you are used to in Visual mode.  I have received one report that mswin.vim interferes with this script.\r\n\r\nEvery second character you type is in Select mode, so with versions of vim before 6.2, completions are offered only half the time.","install_details":":source it from your vimrc file or drop it in your plugin directory.\r\nTo activate, choose \"Word Completion\" from the Tools menu, or type\r\n  :call DoWordComplete()\r\nTo make it stop, choose \"Tools\/Stop Completion,\" or type\r\n  :call EndWordComplete()\r\nIf you want to activate word completion for every buffer, add the line\r\n  :autocmd BufEnter * call DoWordComplete()\r\nto your vimrc file.","5":":source it from your vimrc file or drop it in your plugin directory.\r\nTo activate, choose \"Word Completion\" from the Tools menu, or type\r\n  :call DoWordComplete()\r\nTo make it stop, choose \"Tools\/Stop Completion,\" or type\r\n  :call EndWordComplete()\r\nIf you want to activate word completion for every buffer, add the line\r\n  :autocmd BufEnter * call DoWordComplete()\r\nto your vimrc file.","first_name":"Benji","6":"Benji","last_name":"Fisher","7":"Fisher","releases":[{"0":"73","vim_version":"7.0","1":"7.0","script_version":"1.1","2":"1.1","version_comment":"Minor change:  I replaced\r\n  while letter <= \"z\"\r\nwith\r\n  while letter <=# \"z\"\r\n(case-sensitive comparison, regardless of 'ignorecase' option) so that if someone decides to add a loop for \"A\" to \"Z\" using the same model, (s)he does not get odd results.","3":"Minor change:  I replaced\r\n  while letter <= \"z\"\r\nwith\r\n  while letter <=# \"z\"\r\n(case-sensitive comparison, regardless of 'ignorecase' option) so that if someone decides to add a loop for \"A\" to \"Z\" using the same model, (s)he does not get odd results.","package":"word_complete.vim","4":"word_complete.vim","src_id":"6504","5":"6504","creation_date":"1165385141","6":"1165385141"},{"0":"73","vim_version":"7.0","1":"7.0","script_version":"1.0","2":"1.0","version_comment":"Since vim 7.0 supports :smap (mappings that apply only to Select mode) I updated the script to use these.  Now the maps defined by the script for when completion is active will not do anything unexpected in Visual mode.\r\n\r\nI also updated the installation instructions in the comments at the top of the file.","3":"Since vim 7.0 supports :smap (mappings that apply only to Select mode) I updated the script to use these.  Now the maps defined by the script for when completion is active will not do anything unexpected in Visual mode.\r\n\r\nI also updated the installation instructions in the comments at the top of the file.","package":"word_complete.vim","4":"word_complete.vim","src_id":"5704","5":"5704","creation_date":"1147718891","6":"1147718891"},{"0":"73","vim_version":"6.0","1":"6.0","script_version":"0.6","2":"0.6","version_comment":"I added a configuration section.  You can now change\r\n(1) a minimum length of word to be completed\r\n(2) the character (default <Tab>) used to accept the completion.\r\n\r\nI also added some comments and separated a StartAppend() function (which is called twice).","3":"I added a configuration section.  You can now change\r\n(1) a minimum length of word to be completed\r\n(2) the character (default <Tab>) used to accept the completion.\r\n\r\nI also added some comments and separated a StartAppend() function (which is called twice).","package":"word_complete.vim","4":"word_complete.vim","src_id":"2218","5":"2218","creation_date":"1060414377","6":"1060414377"},{"0":"73","vim_version":"6.0","1":"6.0","script_version":"0.5","2":"0.5","version_comment":"better support for keymaps","3":"better support for keymaps","package":"word_complete.vim","4":"word_complete.vim","src_id":"2048","5":"2048","creation_date":"1054903431","6":"1054903431"},{"0":"73","vim_version":"6.0","1":"6.0","script_version":"0.4","2":"0.4","version_comment":"This version tries to treat :lmap's (and keymaps) properly.\r\n\r\nMinor improvement:  completion is attempted before \r\npunctuation, as well as at the end of a line or before white space.\r\n\r\nThis version will probably no longer work with vim 5.x.","3":"This version tries to treat :lmap's (and keymaps) properly.\r\n\r\nMinor improvement:  completion is attempted before \r\npunctuation, as well as at the end of a line or before white space.\r\n\r\nThis version will probably no longer work with vim 5.x.","package":"word_complete.vim","4":"word_complete.vim","src_id":"1882","5":"1882","creation_date":"1049107880","6":"1049107880"},{"0":"73","vim_version":"5.7","1":"5.7","script_version":"0.3","2":"0.3","version_comment":"Initial upload","3":"Initial upload","package":"word_complete.vim","4":"word_complete.vim","src_id":"143","5":"143","creation_date":"999110663","6":"999110663"}]},"72":{"script_id":"72","0":"72","script_name":"foo.vim","1":"foo.vim","script_type":"utility","2":"utility","summary":"examples of Vim functions (and a few commands, etc.)","3":"examples of Vim functions (and a few commands, etc.)","description":"This file is a collection of Vim functions I have written, many of them in\r\nresponse to questions posted on the vim users' list.  They are all reasonably\r\nshort, so I hope they will be good examples if you are trying to learn how to\r\nwrite your own Vim functions.  You may even find some of the functions\r\nuseful, such as the :Range command and the Mark(), Common(), Count(),\r\nGetModelines(), VarTab(), and SmartBS() functions.","4":"This file is a collection of Vim functions I have written, many of them in\r\nresponse to questions posted on the vim users' list.  They are all reasonably\r\nshort, so I hope they will be good examples if you are trying to learn how to\r\nwrite your own Vim functions.  You may even find some of the functions\r\nuseful, such as the :Range command and the Mark(), Common(), Count(),\r\nGetModelines(), VarTab(), and SmartBS() functions.","install_details":"","5":"","first_name":"Benji","6":"Benji","last_name":"Fisher","7":"Fisher","releases":[{"0":"72","vim_version":"6.0","1":"6.0","script_version":"2.1.1","2":"2.1.1","version_comment":"improved \"text object\" :vmap's for i\", i', a\", a' (will be obsolete in vim 7) and some tweaks to the comments","3":"improved \"text object\" :vmap's for i\", i', a\", a' (will be obsolete in vim 7) and some tweaks to the comments","package":"foo.vim","4":"foo.vim","src_id":"4837","5":"4837","creation_date":"1133376832","6":"1133376832"},{"0":"72","vim_version":"6.0","1":"6.0","script_version":"2.1","2":"2.1","version_comment":"New functions:\r\n\r\nGCD():  an example of recursion\r\nRepeatString():  Generate \"ababababababababab\"\r\nInvertString():  by Preben \"Peppe\" Guldberg\r\nMyMarks():  save file positions to a file and read them\r\nFooSID():  expose the script ID so you can call script-local functions","3":"New functions:\r\n\r\nGCD():  an example of recursion\r\nRepeatString():  Generate \"ababababababababab\"\r\nInvertString():  by Preben \"Peppe\" Guldberg\r\nMyMarks():  save file positions to a file and read them\r\nFooSID():  expose the script ID so you can call script-local functions","package":"foo.vim","4":"foo.vim","src_id":"2657","5":"2657","creation_date":"1073892452","6":"1073892452"},{"0":"72","vim_version":"6.0","1":"6.0","script_version":"2.0.3","2":"2.0.3","version_comment":"I changed :map to :imap for the VarTab() function.","3":"I changed :map to :imap for the VarTab() function.","package":"foo.vim","4":"foo.vim","src_id":"2116","5":"2116","creation_date":"1056694480","6":"1056694480"},{"0":"72","vim_version":"6.0","1":"6.0","script_version":"2.0.2","2":"2.0.2","version_comment":"Oops, I uploaded the wrong file!","3":"Oops, I uploaded the wrong file!","package":"foo.vim","4":"foo.vim","src_id":"2061","5":"2061","creation_date":"1055341087","6":"1055341087"},{"0":"72","vim_version":"6.0","1":"6.0","script_version":"2.0.2","2":"2.0.2","version_comment":"improvements to the EditFun command and function","3":"improvements to the EditFun command and function","package":"matchit.vim","4":"matchit.vim","src_id":"2060","5":"2060","creation_date":"1055333498","6":"1055333498"},{"0":"72","vim_version":"6.0","1":"6.0","script_version":"2.0.1","2":"2.0.1","version_comment":"Oops:  make sure script variables are defined before used.","3":"Oops:  make sure script variables are defined before used.","package":"foo.vim","4":"foo.vim","src_id":"1433","5":"1433","creation_date":"1037678700","6":"1037678700"},{"0":"72","vim_version":"6.0","1":"6.0","script_version":"2.0","2":"2.0","version_comment":"I added a user configuration section, as discussed on the vim-dev\r\nmailing list.  With the defaults, most :imap's are not defined, so it\r\nis safer to include this in your plugin directory, if you like using any\r\nof the commands or functions it defines.  Like the rest of the file,\r\nthe configuration section is meant as an example to be followed.\r\nThe user should copy this section to a separate file, foo.vimrc .\r\n\r\nI also added functions to save script-local variables in the script\r\nfile, so they are made persistent.","3":"I added a user configuration section, as discussed on the vim-dev\r\nmailing list.  With the defaults, most :imap's are not defined, so it\r\nis safer to include this in your plugin directory, if you like using any\r\nof the commands or functions it defines.  Like the rest of the file,\r\nthe configuration section is meant as an example to be followed.\r\nThe user should copy this section to a separate file, foo.vimrc .\r\n\r\nI also added functions to save script-local variables in the script\r\nfile, so they are made persistent.","package":"foo.vim","4":"foo.vim","src_id":"1422","5":"1422","creation_date":"1037361395","6":"1037361395"},{"0":"72","vim_version":"5.7","1":"5.7","script_version":"1.4","2":"1.4","version_comment":"Just a format change:  This version has unix-style line endings, and I\r\nupdated the modelines to keep it that way.","3":"Just a format change:  This version has unix-style line endings, and I\r\nupdated the modelines to keep it that way.","package":"foo.vim","4":"foo.vim","src_id":"1083","5":"1083","creation_date":"1028616044","6":"1028616044"},{"0":"72","vim_version":"5.7","1":"5.7","script_version":"1.4","2":"1.4","version_comment":"I added Common(str1, str2), which returns the initial matching part (if any)\r\nof two input strings.\r\nI also added TWIN() (The Weather Is Nice):  an example of how to prompt\r\nthe user for input and add some text based on that input.","3":"I added Common(str1, str2), which returns the initial matching part (if any)\r\nof two input strings.\r\nI also added TWIN() (The Weather Is Nice):  an example of how to prompt\r\nthe user for input and add some text based on that input.","package":"foo.vim","4":"foo.vim","src_id":"1078","5":"1078","creation_date":"1028493181","6":"1028493181"},{"0":"72","vim_version":"5.7","1":"5.7","script_version":"1.3","2":"1.3","version_comment":"I added the :Iabbr command, which allows you to define abbreviations like\r\n\r\n:Iabbr foo foo()<Left>\r\n\r\nthat can be triggered by a space without inserting that space.  Several contributors to the vim users' list suggested improvements to this command.","3":"I added the :Iabbr command, which allows you to define abbreviations like\r\n\r\n:Iabbr foo foo()<Left>\r\n\r\nthat can be triggered by a space without inserting that space.  Several contributors to the vim users' list suggested improvements to this command.","package":"foo.vim","4":"foo.vim","src_id":"738","5":"738","creation_date":"1017567546","6":"1017567546"},{"0":"72","vim_version":"5.7","1":"5.7","script_version":"1.2","2":"1.2","version_comment":"I added a table of contents, with a one-line description of the purpose\r\nand a one-line description of the techniques used by each example.\r\nI also trimmed a few of the less interesting examples and made a\r\ncouple of corrections, added a few comments, etc.","3":"I added a table of contents, with a one-line description of the purpose\r\nand a one-line description of the techniques used by each example.\r\nI also trimmed a few of the less interesting examples and made a\r\ncouple of corrections, added a few comments, etc.","package":"foo.vim","4":"foo.vim","src_id":"409","5":"409","creation_date":"1007629013","6":"1007629013"},{"0":"72","vim_version":"6.0","1":"6.0","script_version":"1.1","2":"1.1","version_comment":"I improved the GetModelines() function.\r\nMaybe something else is new, too...","3":"I improved the GetModelines() function.\r\nMaybe something else is new, too...","package":"foo.vim","4":"foo.vim","src_id":"369","5":"369","creation_date":"1006458830","6":"1006458830"},{"0":"72","vim_version":"5.7","1":"5.7","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"foo.vim","4":"foo.vim","src_id":"139","5":"139","creation_date":"998990280","6":"998990280"}]},"71":{"script_id":"71","0":"71","script_name":"dctl.vim.gz","1":"dctl.vim.gz","script_type":"utility","2":"utility","summary":"Syntax file for Synopsys DesignCompiler tcl","3":"Syntax file for Synopsys DesignCompiler tcl","description":" This is a syntax file for Synopsys' DesignCompiler tcl language \r\n\r\n ** These files are no longer being maintained here **  \r\n\r\nGo to my website www.zimmerdesignservices.com for the latest versions.","4":" This is a syntax file for Synopsys' DesignCompiler tcl language \r\n\r\n ** These files are no longer being maintained here **  \r\n\r\nGo to my website www.zimmerdesignservices.com for the latest versions.","install_details":"Nothing special.  Just download and unzip\/untar.  There's a README file that shows various ways of hooking it in.","5":"Nothing special.  Just download and unzip\/untar.  There's a README file that shows various ways of hooking it in.","first_name":"Paul","6":"Paul","last_name":"Zimmer","7":"Zimmer","releases":[{"0":"71","vim_version":"6.0","1":"6.0","script_version":"2005.09a","2":"2005.09a","version_comment":"Fixed a bug in previous version caused by some random unprintable characters in Synopsys' html help pages.","3":"Fixed a bug in previous version caused by some random unprintable characters in Synopsys' html help pages.","package":"dctl_2005.09.vim.tgz","4":"dctl_2005.09.vim.tgz","src_id":"6012","5":"6012","creation_date":"1154287286","6":"1154287286"},{"0":"71","vim_version":"6.0","1":"6.0","script_version":"2005.09","2":"2005.09","version_comment":"Updated for 2005.09.  Several other small enhancements as well.  Dictionary files now included.  I don't always remember to update on this site, so check my website www.zimmerdesignservices.com for latest.","3":"Updated for 2005.09.  Several other small enhancements as well.  Dictionary files now included.  I don't always remember to update on this site, so check my website www.zimmerdesignservices.com for latest.","package":"dctl_2005.09.vim.tgz","4":"dctl_2005.09.vim.tgz","src_id":"5928","5":"5928","creation_date":"1152196645","6":"1152196645"},{"0":"71","vim_version":"6.0","1":"6.0","script_version":"2004.06","2":"2004.06","version_comment":"Updated for 2004.06.  Changed the script version to match the target dc version (2004.06)","3":"Updated for 2004.06.  Changed the script version to match the target dc version (2004.06)","package":"dctlstd_200406.vim.tgz","4":"dctlstd_200406.vim.tgz","src_id":"3302","5":"3302","creation_date":"1091616691","6":"1091616691"},{"0":"71","vim_version":"6.0","1":"6.0","script_version":"6.14","2":"6.14","version_comment":"For DC 2003.12 release.  Now also includes a README that show various ways to hook in the file.","3":"For DC 2003.12 release.  Now also includes a README that show various ways to hook in the file.","package":"dctl_200312.vim.tgz","4":"dctl_200312.vim.tgz","src_id":"3002","5":"3002","creation_date":"1083951986","6":"1083951986"},{"0":"71","vim_version":"6.0","1":"6.0","script_version":"6.12","2":"6.12","version_comment":"Updated for DC2003.06\r\nAlso, removed some incorrect syntax matches that occurred when Synopsys added package \r\nsupport.  Haven't tackled the problem of actually parsing the package commands, but I \r\nat least removed the incorrect keywords that had resulted from this change","3":"Updated for DC2003.06\r\nAlso, removed some incorrect syntax matches that occurred when Synopsys added package \r\nsupport.  Haven't tackled the problem of actually parsing the package commands, but I \r\nat least removed the incorrect keywords that had resulted from this change","package":"dctl.vim.gz","4":"dctl.vim.gz","src_id":"2564","5":"2564","creation_date":"1070807836","6":"1070807836"},{"0":"71","vim_version":"6.0","1":"6.0","script_version":"6.11","2":"6.11","version_comment":"Updated for dc 2002.05","3":"Updated for dc 2002.05","package":"dctl.vim.gz","4":"dctl.vim.gz","src_id":"1066","5":"1066","creation_date":"1028040673","6":"1028040673"},{"0":"71","vim_version":"6.0","1":"6.0","script_version":"6.1","2":"6.1","version_comment":"Compatible with vi 6.1","3":"Compatible with vi 6.1","package":"dctl.vim.gz","4":"dctl.vim.gz","src_id":"827","5":"827","creation_date":"1020181989","6":"1020181989"},{"0":"71","vim_version":"5.7","1":"5.7","script_version":"5.8","2":"5.8","version_comment":"Fixed problems with 5.8 inter-operation, hilink, etc\r\nWorks much better now.  Doesn't get \"lost\" much anymore.","3":"Fixed problems with 5.8 inter-operation, hilink, etc\r\nWorks much better now.  Doesn't get \"lost\" much anymore.","package":"dctl.vim.gz","4":"dctl.vim.gz","src_id":"626","5":"626","creation_date":"1014305946","6":"1014305946"},{"0":"71","vim_version":"5.7","1":"5.7","script_version":"5.7","2":"5.7","version_comment":"Initial upload","3":"Initial upload","package":"dctl.vim.gz","4":"dctl.vim.gz","src_id":"136","5":"136","creation_date":"998907117","6":"998907117"}]},"70":{"script_id":"70","0":"70","script_name":"pt.vim.gz","1":"pt.vim.gz","script_type":"syntax","2":"syntax","summary":"Syntax file for Synopsys PrimeTime tcl","3":"Syntax file for Synopsys PrimeTime tcl","description":"This is a syntax file for Synopsys' PrimeTime tcl language\r\n\r\n ** These files are no longer being maintained here **  \r\n\r\nGo to my website www.zimmerdesignservices.com for the latest versions.","4":"This is a syntax file for Synopsys' PrimeTime tcl language\r\n\r\n ** These files are no longer being maintained here **  \r\n\r\nGo to my website www.zimmerdesignservices.com for the latest versions.","install_details":"Nothing special.  Just download and unzip\/untar.  There's a README file that shows various ways of hooking it in.","5":"Nothing special.  Just download and unzip\/untar.  There's a README file that shows various ways of hooking it in.","first_name":"Paul","6":"Paul","last_name":"Zimmer","7":"Zimmer","releases":[{"0":"70","vim_version":"6.0","1":"6.0","script_version":"2005.06","2":"2005.06","version_comment":"Updated for 2005.06.  Several other small enhancements as well.  Dictionary files now included.  I don't always remember to update on this site, so check my website www.zimmerdesignservices.com for latest.","3":"Updated for 2005.06.  Several other small enhancements as well.  Dictionary files now included.  I don't always remember to update on this site, so check my website www.zimmerdesignservices.com for latest.","package":"pt_2005.06.vim.tgz","4":"pt_2005.06.vim.tgz","src_id":"5927","5":"5927","creation_date":"1152196596","6":"1152196596"},{"0":"70","vim_version":"6.0","1":"6.0","script_version":"2004.06","2":"2004.06","version_comment":"Updated for 2004.06.  Changed script numbering version to match target pt version (so script version is now \"2004.06\".","3":"Updated for 2004.06.  Changed script numbering version to match target pt version (so script version is now \"2004.06\".","package":"ptstd_200406.vim.tgz","4":"ptstd_200406.vim.tgz","src_id":"3301","5":"3301","creation_date":"1091616509","6":"1091616509"},{"0":"70","vim_version":"6.0","1":"6.0","script_version":"6.14","2":"6.14","version_comment":"For PrimeTime 2003.12 release.  Now also includes a README that show various ways to hook in the file.","3":"For PrimeTime 2003.12 release.  Now also includes a README that show various ways to hook in the file.","package":"pt_200312.vim.tgz","4":"pt_200312.vim.tgz","src_id":"3001","5":"3001","creation_date":"1083951926","6":"1083951926"},{"0":"70","vim_version":"6.0","1":"6.0","script_version":"6.12","2":"6.12","version_comment":"Updated for PT2003.03\r\nAlso, removed some incorrect syntax matches that occurred when Synopsys added package\r\nsupport.  Haven't tackled the problem of actually parsing the package commands, but I\r\nat least removed the incorrect keywords that had resulted from this change.","3":"Updated for PT2003.03\r\nAlso, removed some incorrect syntax matches that occurred when Synopsys added package\r\nsupport.  Haven't tackled the problem of actually parsing the package commands, but I\r\nat least removed the incorrect keywords that had resulted from this change.","package":"pt.vim.gz","4":"pt.vim.gz","src_id":"2563","5":"2563","creation_date":"1070807743","6":"1070807743"},{"0":"70","vim_version":"6.0","1":"6.0","script_version":"6.11","2":"6.11","version_comment":"Updated for pt 2002.03","3":"Updated for pt 2002.03","package":"pt.vim.gz","4":"pt.vim.gz","src_id":"1065","5":"1065","creation_date":"1028040615","6":"1028040615"},{"0":"70","vim_version":"6.0","1":"6.0","script_version":"6.1","2":"6.1","version_comment":"Compatible with vim 6.1","3":"Compatible with vim 6.1","package":"pt.vim.gz","4":"pt.vim.gz","src_id":"826","5":"826","creation_date":"1020181918","6":"1020181918"},{"0":"70","vim_version":"5.7","1":"5.7","script_version":"5.8","2":"5.8","version_comment":"Fixed problems with 5.8 inter-operation, hilink, etc\r\nWorks much better now.  Doesn't get \"lost\" much anymore.","3":"Fixed problems with 5.8 inter-operation, hilink, etc\r\nWorks much better now.  Doesn't get \"lost\" much anymore.","package":"pt.vim.gz","4":"pt.vim.gz","src_id":"625","5":"625","creation_date":"1014305863","6":"1014305863"},{"0":"70","vim_version":"5.7","1":"5.7","script_version":"5.7","2":"5.7","version_comment":"Initial upload","3":"Initial upload","package":"pt.vim.gz","4":"pt.vim.gz","src_id":"134","5":"134","creation_date":"998905598","6":"998905598"}]},"69":{"script_id":"69","0":"69","script_name":"project.tar.gz","1":"project.tar.gz","script_type":"utility","2":"utility","summary":"Organize\/Navigate projects of files (like IDE\/buffer explorer)","3":"Organize\/Navigate projects of files (like IDE\/buffer explorer)","description":"You can use this plugin's basic functionality to set up a list of\r\nfrequently-accessed files for easy navigation. The list of files\r\nwill be displayed in a window on the left side of the Vim\r\nwindow, and you can press <Return> or double-click on\r\nfilenames in the list to open the files. This is similar to how\r\nsome IDEs I've used work. I find this easier to use than\r\nhaving to navigate a directory hierarchy with the file-explorer.\r\nIt also obviates the need for a buffer explorer because you\r\nhave your list of files on the left of the Vim Window.\r\n\r\n\r\nBut there's much, much more . . . .\r\n\r\nYou can also instruct the Plugin to change to a directory and\r\nto run scripts when you select a file. These scripts can, for\r\nexample, modify the environment to include compilers in\r\n$PATH. This makes it very easy to use quickfix with multiple\r\nprojects that use different environments. I give examples in\r\nthe documentation.\r\n\r\nOther features include:\r\n\to Loading\/Unloading all the files in a Project (\\l, \\L, \\w, and \\W)\r\n\to Grepping all the files in a Project (\\g and \\G)\r\n\to Running a user-specified script on a file (can be used\r\n\t  to launch an external program on the file) (\\1 through \\9)\r\n\to Running a user-specified script on all the files in a Project\r\n\t  (\\f1-\\f9 and \\F1-\\F9)\r\n\to Also works with the netrw plugin using directory\r\n\t  names like ftp:\/\/remotehost\r\n             (Good for webpage maintenance.)\r\n\to Support for custom mappings for version control\r\n\t  integration (example of perforce in the documentation).\r\n\to I also give an example in the documentation on how to \r\n\t  set up a custom launcher based on extension. The\r\n\t  example launches *.jpg files in a viewer. I have also set\r\n\t  up viewers for PDF (acroread) and HTML files (mozilla)\r\n\t  for my own use.\r\n\r\nThis plugin is known to work on Linux, Solaris, and Windows.\r\nI cannot test it on Windows, though, so please let me know if\r\nyou run into any problems. If you use it on other platforms,\r\nlet me know.\r\n\r\n(Let me know if you need a .zip file)\r\n","4":"You can use this plugin's basic functionality to set up a list of\r\nfrequently-accessed files for easy navigation. The list of files\r\nwill be displayed in a window on the left side of the Vim\r\nwindow, and you can press <Return> or double-click on\r\nfilenames in the list to open the files. This is similar to how\r\nsome IDEs I've used work. I find this easier to use than\r\nhaving to navigate a directory hierarchy with the file-explorer.\r\nIt also obviates the need for a buffer explorer because you\r\nhave your list of files on the left of the Vim Window.\r\n\r\n\r\nBut there's much, much more . . . .\r\n\r\nYou can also instruct the Plugin to change to a directory and\r\nto run scripts when you select a file. These scripts can, for\r\nexample, modify the environment to include compilers in\r\n$PATH. This makes it very easy to use quickfix with multiple\r\nprojects that use different environments. I give examples in\r\nthe documentation.\r\n\r\nOther features include:\r\n\to Loading\/Unloading all the files in a Project (\\l, \\L, \\w, and \\W)\r\n\to Grepping all the files in a Project (\\g and \\G)\r\n\to Running a user-specified script on a file (can be used\r\n\t  to launch an external program on the file) (\\1 through \\9)\r\n\to Running a user-specified script on all the files in a Project\r\n\t  (\\f1-\\f9 and \\F1-\\F9)\r\n\to Also works with the netrw plugin using directory\r\n\t  names like ftp:\/\/remotehost\r\n             (Good for webpage maintenance.)\r\n\to Support for custom mappings for version control\r\n\t  integration (example of perforce in the documentation).\r\n\to I also give an example in the documentation on how to \r\n\t  set up a custom launcher based on extension. The\r\n\t  example launches *.jpg files in a viewer. I have also set\r\n\t  up viewers for PDF (acroread) and HTML files (mozilla)\r\n\t  for my own use.\r\n\r\nThis plugin is known to work on Linux, Solaris, and Windows.\r\nI cannot test it on Windows, though, so please let me know if\r\nyou run into any problems. If you use it on other platforms,\r\nlet me know.\r\n\r\n(Let me know if you need a .zip file)\r\n","install_details":"Decompress and untar in your ~\/.vim directory (or\r\nequivalent).  Inside Vim, enter this:\r\n   :helptags ~\/.vim\/doc\r\n(or equivalent directory)\r\n(Enter \":help add-global-plugin\" to determine the directory to\r\nuntar it into.)\r\n\r\nThen enter\r\n  :help project\r\nfor information\r\n","5":"Decompress and untar in your ~\/.vim directory (or\r\nequivalent).  Inside Vim, enter this:\r\n   :helptags ~\/.vim\/doc\r\n(or equivalent directory)\r\n(Enter \":help add-global-plugin\" to determine the directory to\r\nuntar it into.)\r\n\r\nThen enter\r\n  :help project\r\nfor information\r\n","first_name":"Aric","6":"Aric","last_name":"Blumer","7":"Blumer","releases":[{"0":"69","vim_version":"7.0","1":"7.0","script_version":"1.4.1","2":"1.4.1","version_comment":"- Bug fixes\r\n- Optional use of vimgrep instead of grep\r\n- Line numbers in the project window\r\n- Window not bound to left side (experimental)","3":"- Bug fixes\r\n- Optional use of vimgrep instead of grep\r\n- Line numbers in the project window\r\n- Window not bound to left side (experimental)","package":"project-1.4.1.tar.gz","4":"project-1.4.1.tar.gz","src_id":"6273","5":"6273","creation_date":"1160724310","6":"1160724310"},{"0":"69","vim_version":"7.0","1":"7.0","script_version":"1.4","2":"1.4","version_comment":"After about 2.5 years here is a slightly updated version.\r\n\r\n-Updated to support 7.0.  The previous version works in 7.0, but there was an annoying redraw when you move into\/out of the project window.\r\n-Also, 7.0 treats modelines a little bit differently than 6.x. Version 7.0 re-evaluates window-local modelines if you hide and show the project window, and this messes up folds if you have a foldlevel in your project file's modelines.  Modelines are now turned off after the project file is first loaded.\r\n-Added \\S (Split-load all files at the cursor level) contributed by A. Harrison.\r\n-Bug fix with misuse of winnr() when winbufnr() should have been used.","3":"After about 2.5 years here is a slightly updated version.\r\n\r\n-Updated to support 7.0.  The previous version works in 7.0, but there was an annoying redraw when you move into\/out of the project window.\r\n-Also, 7.0 treats modelines a little bit differently than 6.x. Version 7.0 re-evaluates window-local modelines if you hide and show the project window, and this messes up folds if you have a foldlevel in your project file's modelines.  Modelines are now turned off after the project file is first loaded.\r\n-Added \\S (Split-load all files at the cursor level) contributed by A. Harrison.\r\n-Bug fix with misuse of winnr() when winbufnr() should have been used.","package":"project-1.4.tar.gz","4":"project-1.4.tar.gz","src_id":"5600","5":"5600","creation_date":"1145873435","6":"1145873435"},{"0":"69","vim_version":"6.0","1":"6.0","script_version":"1.3","2":"1.3","version_comment":"-Bug Fixes (thanks Xiangjiang Ma)\r\n-Completed suite of % expansions in proj_run\r\n-Added mapping to toggle Project Window open\/closed.\r\n-Added <F5> mapping equivalent to \\R","3":"-Bug Fixes (thanks Xiangjiang Ma)\r\n-Completed suite of % expansions in proj_run\r\n-Added mapping to toggle Project Window open\/closed.\r\n-Added <F5> mapping equivalent to \\R","package":"project-1.3.tar.gz","4":"project-1.3.tar.gz","src_id":"1338","5":"1338","creation_date":"1035552386","6":"1035552386"},{"0":"69","vim_version":"6.0","1":"6.0","script_version":"1.2.1","2":"1.2.1","version_comment":"--Identical to 1.2 but fixed functionality with netrw","3":"--Identical to 1.2 but fixed functionality with netrw","package":"project-1.2.1.tar.gz","4":"project-1.2.1.tar.gz","src_id":"1266","5":"1266","creation_date":"1033463126","6":"1033463126"},{"0":"69","vim_version":"6.0","1":"6.0","script_version":"1.2","2":"1.2","version_comment":"-Environment variables now expanded in paths.\r\n-Added 'b' flag to use the browse() function. (Off for Windows--it can't browse for directories.)\r\n-Added keep pragma to keep lines when refreshing.\r\n-Small tweaks.\r\n-Doc: example of using perforce with the plugin.\r\n-Doc: example of adding custom launchers.\r\n-Can't test on Windows, please let me know of problems.","3":"-Environment variables now expanded in paths.\r\n-Added 'b' flag to use the browse() function. (Off for Windows--it can't browse for directories.)\r\n-Added keep pragma to keep lines when refreshing.\r\n-Small tweaks.\r\n-Doc: example of using perforce with the plugin.\r\n-Doc: example of adding custom launchers.\r\n-Can't test on Windows, please let me know of problems.","package":"project-1.2.tar.gz","4":"project-1.2.tar.gz","src_id":"1262","5":"1262","creation_date":"1033382743","6":"1033382743"},{"0":"69","vim_version":"6.0","1":"6.0","script_version":"1.1","2":"1.1","version_comment":"Now accepts spaces in directories. Some bug fixes, too. Added Project_GetFname() for user scripts.","3":"Now accepts spaces in directories. Some bug fixes, too. Added Project_GetFname() for user scripts.","package":"project-1.1.tar.gz","4":"project-1.1.tar.gz","src_id":"741","5":"741","creation_date":"1017662927","6":"1017662927"},{"0":"69","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Some Bugfixes, improvements in performance. Added recursive create, explore, filenames with spaces, etc.","3":"Some Bugfixes, improvements in performance. Added recursive create, explore, filenames with spaces, etc.","package":"project.tar.gz","4":"project.tar.gz","src_id":"385","5":"385","creation_date":"1007116153","6":"1007116153"},{"0":"69","vim_version":"6.0","1":"6.0","script_version":"1.0pre4","2":"1.0pre4","version_comment":"Last pre before 1.0, so please test!\r\n- Added project grep, project load, project wipe\r\n- Can run commands on all files in a project.\r\n- Now supports netrw plugin","3":"Last pre before 1.0, so please test!\r\n- Added project grep, project load, project wipe\r\n- Can run commands on all files in a project.\r\n- Now supports netrw plugin","package":"project.tar.gz","4":"project.tar.gz","src_id":"285","5":"285","creation_date":"1003399508","6":"1003399508"},{"0":"69","vim_version":"6.0","1":"6.0","script_version":"1.0pre3","2":"1.0pre3","version_comment":"Added flags for sorting of filenames.\r\nAdded mappings to run external program or Vim script on a file.\r\nFixed a small bug (\"internal error\").","3":"Added flags for sorting of filenames.\r\nAdded mappings to run external program or Vim script on a file.\r\nFixed a small bug (\"internal error\").","package":"project.tar.gz","4":"project.tar.gz","src_id":"254","5":"254","creation_date":"1002630522","6":"1002630522"},{"0":"69","vim_version":"6.0","1":"6.0","script_version":"1.0pre2","2":"1.0pre2","version_comment":"Fixed absolute path detection for Win32. (Thanks Lawrence!) Fixed small documentation error.","3":"Fixed absolute path detection for Win32. (Thanks Lawrence!) Fixed small documentation error.","package":"project.tar.gz","4":"project.tar.gz","src_id":"236","5":"236","creation_date":"1002264518","6":"1002264518"},{"0":"69","vim_version":"6.0","1":"6.0","script_version":"1.0pre1","2":"1.0pre1","version_comment":"Several new features, most notably: Paths can now be relative in subprojects. Subprojects inherit parameters from parent. New in= and out= directives to run Vim scripts to modify the environment. Added T flag. Added per-fold flags. CTRL-W_o keeps Project Window visible. etc.","3":"Several new features, most notably: Paths can now be relative in subprojects. Subprojects inherit parameters from parent. New in= and out= directives to run Vim scripts to modify the environment. Added T flag. Added per-fold flags. CTRL-W_o keeps Project Window visible. etc.","package":"project.tar.gz","4":"project.tar.gz","src_id":"233","5":"233","creation_date":"1002103425","6":"1002103425"}]},"68":{"script_id":"68","0":"68","script_name":"vfp.vim","1":"vfp.vim","script_type":"syntax","2":"syntax","summary":"Visual FoxPro 3.0, 5.0, and 6.0 syntax file","3":"Visual FoxPro 3.0, 5.0, and 6.0 syntax file","description":"\r\n     This file builds on the FoxPro for DOS v2.x syntax file maintained by Powing Tse <powing@mcmug.org> and the Clipper 5.2 & FlagShip syntax file maintained by C R Zamana <zamana@zip.net>.\r\n\r\n     This syntax file should work with Visual Foxpro versions 3.0 - 6.0 and OS platforms Windows, Mac, and Unix.  The best fit will be VFP 6 (which is Windows only).  Older versions may have things highlighted that aren't actually available in that version.  For example, GETHOST() is new in VFP 6, but would show up in a VFP 3 program as a reserved word.  Consider this as a future-proofing feature and not a bug.  ;-)\r\n\r\n     Because of the messy nature of the Visual FoxPro documentation *and* the language itself, I've had to combine reserved word lists from several, slightly different, sources.  This means I might have missed a reserved word here or there.  If you find one, please let me know so I can add it to this file.\r\n\r\n","4":"\r\n     This file builds on the FoxPro for DOS v2.x syntax file maintained by Powing Tse <powing@mcmug.org> and the Clipper 5.2 & FlagShip syntax file maintained by C R Zamana <zamana@zip.net>.\r\n\r\n     This syntax file should work with Visual Foxpro versions 3.0 - 6.0 and OS platforms Windows, Mac, and Unix.  The best fit will be VFP 6 (which is Windows only).  Older versions may have things highlighted that aren't actually available in that version.  For example, GETHOST() is new in VFP 6, but would show up in a VFP 3 program as a reserved word.  Consider this as a future-proofing feature and not a bug.  ;-)\r\n\r\n     Because of the messy nature of the Visual FoxPro documentation *and* the language itself, I've had to combine reserved word lists from several, slightly different, sources.  This means I might have missed a reserved word here or there.  If you find one, please let me know so I can add it to this file.\r\n\r\n","install_details":"\r\n     1)  Copy the vfp.vim file to your syntax directory.\r\n\r\n     2)  Add the line \"SynAu vfp\" to your synload.vim file.\r\n\r\n     3)  If you are using gvim and want to have this syntax file to show up in the menus, add the line \"am 50.80.395 &Syntax.TUV.Visual\\ Foxpro :cal SetSyn(\"vfp\")<CR>\" to your menu.vim file.\r\n\r\n     4)  Optionally, if you are using the myfiletypes.vim file you can add the following 2 lines to make all prg files and fpw files automatically use the VFP syntax file:\r\n\tau! BufRead,BufNewFile *.prg    set filetype=vfp\r\n\tau! BufRead,BufNewFile *.fpw    set filetype=vfp\r\n\r\n","5":"\r\n     1)  Copy the vfp.vim file to your syntax directory.\r\n\r\n     2)  Add the line \"SynAu vfp\" to your synload.vim file.\r\n\r\n     3)  If you are using gvim and want to have this syntax file to show up in the menus, add the line \"am 50.80.395 &Syntax.TUV.Visual\\ Foxpro :cal SetSyn(\"vfp\")<CR>\" to your menu.vim file.\r\n\r\n     4)  Optionally, if you are using the myfiletypes.vim file you can add the following 2 lines to make all prg files and fpw files automatically use the VFP syntax file:\r\n\tau! BufRead,BufNewFile *.prg    set filetype=vfp\r\n\tau! BufRead,BufNewFile *.fpw    set filetype=vfp\r\n\r\n","first_name":"Edward","6":"Edward","last_name":"Franks","7":"Franks","releases":[{"0":"68","vim_version":"5.7","1":"5.7","script_version":"1.1","2":"1.1","version_comment":"Somehow I missed the keyword \"tag\".  :-\/\r\n","3":"Somehow I missed the keyword \"tag\".  :-\/\r\n","package":"vfp.vim","4":"vfp.vim","src_id":"186","5":"186","creation_date":"1001061939","6":"1001061939"},{"0":"68","vim_version":"5.7","1":"5.7","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"vfp.vim","4":"vfp.vim","src_id":"125","5":"125","creation_date":"998381225","6":"998381225"}]},"67":{"script_id":"67","0":"67","script_name":"nqc.vim","1":"nqc.vim","script_type":"utility","2":"utility","summary":"NQC programming support (for the LEGO MINDSTORMS RCX-Controller)","3":"NQC programming support (for the LEGO MINDSTORMS RCX-Controller)","description":"gvim-menus for NQC (Not Quite C),  Version 2.3r1  (and newer).\r\nNQC is a C-like language for programmimg the LEGO MINDSTORMS RCX-Controller.\r\nThese menus turn gvim into an IDE for the RCX-programming:\r\n - insertion of NQC statements, function calls, comments, RCX constants\r\n - download programs and firmware to RCX\r\n - upload the datalog from RCX\r\n - erase programs and datalogs in RCX\r\n\r\n\r\nHere are some screen shots : http:\/\/lug.fh-swf.de\/vim\/vim-nqc\/screenshots-en.html","4":"gvim-menus for NQC (Not Quite C),  Version 2.3r1  (and newer).\r\nNQC is a C-like language for programmimg the LEGO MINDSTORMS RCX-Controller.\r\nThese menus turn gvim into an IDE for the RCX-programming:\r\n - insertion of NQC statements, function calls, comments, RCX constants\r\n - download programs and firmware to RCX\r\n - upload the datalog from RCX\r\n - erase programs and datalogs in RCX\r\n\r\n\r\nHere are some screen shots : http:\/\/lug.fh-swf.de\/vim\/vim-nqc\/screenshots-en.html","install_details":"Copy the zip archive  nqcvim.zip to $HOME\/.vim\/ and run \r\n      unzip nqcvim.zip \r\nIf you have already an older version of this plugin and you have modified the \r\ntemplate files you may want to save your templates first or copy the files from the \r\narchive by hand. See also the file README.nqc within the zip file.","5":"Copy the zip archive  nqcvim.zip to $HOME\/.vim\/ and run \r\n      unzip nqcvim.zip \r\nIf you have already an older version of this plugin and you have modified the \r\ntemplate files you may want to save your templates first or copy the files from the \r\narchive by hand. See also the file README.nqc within the zip file.","first_name":"Fritz","6":"Fritz","last_name":"Mehner","7":"Mehner","releases":[{"0":"67","vim_version":"6.0","1":"6.0","script_version":"3.1","2":"3.1","version_comment":"+ Aligned line end comments for consecutive lines.\n+ Uncomment more than one block at once.\n+ The dialog windows (GUI) have been replaced by more flexible command line inputs.\n+ Online documentation improved.\n","3":"+ Aligned line end comments for consecutive lines.\n+ Uncomment more than one block at once.\n+ The dialog windows (GUI) have been replaced by more flexible command line inputs.\n+ Online documentation improved.\n","package":"nqcvim.zip","4":"nqcvim.zip","src_id":"3739","5":"3739","creation_date":"1104387481","6":"1104387481"},{"0":"67","vim_version":"6.0","1":"6.0","script_version":"3.0","2":"3.0","version_comment":" + Only one NQC root menu entry in the gVim root menu.\n + A marked region can be surrounded by a for-, if, if-else, while-,\n   do-while-statement (with indentation).\n + 3 block comments are now read as templates or skeletons from files\n + The NQC root menu can be changed or disabled.\n + All hotkeys are only defined for NQC files (file type plugin added).\n + Install script added.\n + Customization improved.\n + Documentation improved (help file added).","3":" + Only one NQC root menu entry in the gVim root menu.\n + A marked region can be surrounded by a for-, if, if-else, while-,\n   do-while-statement (with indentation).\n + 3 block comments are now read as templates or skeletons from files\n + The NQC root menu can be changed or disabled.\n + All hotkeys are only defined for NQC files (file type plugin added).\n + Install script added.\n + Customization improved.\n + Documentation improved (help file added).","package":"nqcvim.zip","4":"nqcvim.zip","src_id":"2633","5":"2633","creation_date":"1072525855","6":"1072525855"},{"0":"67","vim_version":"6.0","1":"6.0","script_version":"2.0","2":"2.0","version_comment":"+ indentation: multiline inserts and code snippets will be indented after insertion.\n+ Most menu entries are now also active in normal mode.\n+ Code cleanup: register z no longer used. Most function calls are silent now.\n\n","3":"+ indentation: multiline inserts and code snippets will be indented after insertion.\n+ Most menu entries are now also active in normal mode.\n+ Code cleanup: register z no longer used. Most function calls are silent now.\n\n","package":"nqc.vim","4":"nqc.vim","src_id":"1942","5":"1942","creation_date":"1051350712","6":"1051350712"},{"0":"67","vim_version":"6.0","1":"6.0","script_version":"1.9","2":"1.9","version_comment":"- maintain your own code snippets in a separate directory\n- additional for- and if-statements\n- new hotkey (save, open file, save buffer and compile)\n- analyse datalog with GNUPLOT\n  + upload datalog in a separate buffer\n  + show x- or x-y-plot \n  + configure plot (type: impulses, lines, lines+points, points, steps)\n  + set plot title\n  + save plot (Postscript) or print plot\n- make hardcopy of buffer or of a highlighted part (Postscript)\n- show settings (target, serial port, firmware, hotkeys) \n","3":"- maintain your own code snippets in a separate directory\n- additional for- and if-statements\n- new hotkey (save, open file, save buffer and compile)\n- analyse datalog with GNUPLOT\n  + upload datalog in a separate buffer\n  + show x- or x-y-plot \n  + configure plot (type: impulses, lines, lines+points, points, steps)\n  + set plot title\n  + save plot (Postscript) or print plot\n- make hardcopy of buffer or of a highlighted part (Postscript)\n- show settings (target, serial port, firmware, hotkeys) \n","package":"nqc.vim","4":"nqc.vim","src_id":"1701","5":"1701","creation_date":"1044604487","6":"1044604487"},{"0":"67","vim_version":"6.0","1":"6.0","script_version":"1.6.3","2":"1.6.3","version_comment":"- menus can now be toggled (look for an entry in the Tools menu)\n- additional NQC-statements:  break unti continue start","3":"- menus can now be toggled (look for an entry in the Tools menu)\n- additional NQC-statements:  break unti continue start","package":"nqc.vim","4":"nqc.vim","src_id":"529","5":"529","creation_date":"1012619073","6":"1012619073"},{"0":"67","vim_version":"6.0","1":"6.0","script_version":"1.5","2":"1.5","version_comment":"- API for NQC Vers. 2.3r1 complete\r\n- configurability improved\r\n- minor bugfixes and improvements\r\n","3":"- API for NQC Vers. 2.3r1 complete\r\n- configurability improved\r\n- minor bugfixes and improvements\r\n","package":"nqc.vim","4":"nqc.vim","src_id":"160","5":"160","creation_date":"1000098652","6":"1000098652"},{"0":"67","vim_version":"5.7","1":"5.7","script_version":"1.4","2":"1.4","version_comment":"support for RCX, RCX2, CyberMaster, Scout","3":"support for RCX, RCX2, CyberMaster, Scout","package":"nqc.vim","4":"nqc.vim","src_id":"150","5":"150","creation_date":"999608892","6":"999608892"},{"0":"67","vim_version":"5.7","1":"5.7","script_version":"1.3.1","2":"1.3.1","version_comment":"bug fix:\r\n- datalog upload\r\n ","3":"bug fix:\r\n- datalog upload\r\n ","package":"nqc.vim","4":"nqc.vim","src_id":"147","5":"147","creation_date":"999485168","6":"999485168"},{"0":"67","vim_version":"5.7","1":"5.7","script_version":"1.3","2":"1.3","version_comment":"Initial upload","3":"Initial upload","package":"nqc.vim","4":"nqc.vim","src_id":"124","5":"124","creation_date":"998364977","6":"998364977"}]},"66":{"script_id":"66","0":"66","script_name":"_vim_wok_visualcpp01.zip","1":"_vim_wok_visualcpp01.zip","script_type":"utility","2":"utility","summary":"Simulating some cool features of MS Visual Studio C++ (TM) by Microsoft Corp.","3":"Simulating some cool features of MS Visual Studio C++ (TM) by Microsoft Corp.","description":"Some key extensions, which simulate MS Visual Studio C++ behaviour under VIM. E.g. CTRL-F2 sets\/unsets anonymous marks on current line, F2 jumps to next mark. HOME toggles cursorpos between first column of line and first non-white-char on current line. TAB indents all currently selected lines by one shiftwidth (SHIFT-TAB unindents). CTRL-SPACE does keyword completion.\r\nEven people who never used (or will use) the MS IDE, these key bindings make some tasks quicker\/simpler... Just try the CTRL-F2 \/ F2 feature and you'll love it. Same for the new HOME behaviour.\r\nThis is my first VIM script, so don't blame me, if things work in even more simple ways... just drop me an email - and tell me how!","4":"Some key extensions, which simulate MS Visual Studio C++ behaviour under VIM. E.g. CTRL-F2 sets\/unsets anonymous marks on current line, F2 jumps to next mark. HOME toggles cursorpos between first column of line and first non-white-char on current line. TAB indents all currently selected lines by one shiftwidth (SHIFT-TAB unindents). CTRL-SPACE does keyword completion.\r\nEven people who never used (or will use) the MS IDE, these key bindings make some tasks quicker\/simpler... Just try the CTRL-F2 \/ F2 feature and you'll love it. Same for the new HOME behaviour.\r\nThis is my first VIM script, so don't blame me, if things work in even more simple ways... just drop me an email - and tell me how!","install_details":"Just append the content of the vim file to you _vimrc \/ .vimrc file","5":"Just append the content of the vim file to you _vimrc \/ .vimrc file","first_name":"Wolfram","6":"Wolfram","last_name":"Esser","7":"Esser","releases":[{"0":"66","vim_version":"5.7","1":"5.7","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"_vim_wok_visualcpp01.zip","4":"_vim_wok_visualcpp01.zip","src_id":"123","5":"123","creation_date":"998362584","6":"998362584"}]},"65":{"script_id":"65","0":"65","script_name":"CD.vim","1":"CD.vim","script_type":"utility","2":"utility","summary":"CD to whatever directory the current buffer is using.","3":"CD to whatever directory the current buffer is using.","description":"This is a tiny little script to allow the VIM user to CD to whatever directory your buffer currently is in.  So, if you \"vim my\/dir\/deeply\/in\/src\/file.txt\" a lot then \":CD\" will move VIM into my\/dir\/deeply\/in\/src so that you can edit other files easily within the same directory.\r\n","4":"This is a tiny little script to allow the VIM user to CD to whatever directory your buffer currently is in.  So, if you \"vim my\/dir\/deeply\/in\/src\/file.txt\" a lot then \":CD\" will move VIM into my\/dir\/deeply\/in\/src so that you can edit other files easily within the same directory.\r\n","install_details":"Either copy the guts of the file into your .vimrc or source it.\r\n\r\nShare and enjoy!\r\n","5":"Either copy the guts of the file into your .vimrc or source it.\r\n\r\nShare and enjoy!\r\n","first_name":"Rich","6":"Rich","last_name":"Harkins","7":"Harkins","releases":[{"0":"65","vim_version":"6.0","1":"6.0","script_version":"2.1","2":"2.1","version_comment":"useful when changing directories when buffers are switched.","3":"useful when changing directories when buffers are switched.","package":"cd.vim","4":"cd.vim","src_id":"928","5":"928","creation_date":"1024281877","6":"1024281877"},{"0":"65","vim_version":"5.7","1":"5.7","script_version":"2.0","2":"2.0","version_comment":"Simplified. I'm not sure it works under vim 5.7","3":"Simplified. I'm not sure it works under vim 5.7","package":"CD.vim","4":"CD.vim","src_id":"445","5":"445","creation_date":"1010052323","6":"1010052323"},{"0":"65","vim_version":"5.7","1":"5.7","script_version":"1.1","2":"1.1","version_comment":"Added support for backslash separated filenames.  Thanks to Kontra Gergely for pointing this flaw out.","3":"Added support for backslash separated filenames.  Thanks to Kontra Gergely for pointing this flaw out.","package":"CD.vim","4":"CD.vim","src_id":"234","5":"234","creation_date":"1002113118","6":"1002113118"},{"0":"65","vim_version":"5.7","1":"5.7","script_version":"1.000001:)","2":"1.000001:)","version_comment":"Sorry - missed the com command off my posting!!!\r\n:)\r\n","3":"Sorry - missed the com command off my posting!!!\r\n:)\r\n","package":"CD.vim","4":"CD.vim","src_id":"121","5":"121","creation_date":"998312285","6":"998312285"},{"0":"65","vim_version":"5.7","1":"5.7","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"CD.vim","4":"CD.vim","src_id":"120","5":"120","creation_date":"998312147","6":"998312147"}]},"64":{"script_id":"64","0":"64","script_name":"po.vim","1":"po.vim","script_type":"utility","2":"utility","summary":"PO (portable object) helper functions","3":"PO (portable object) helper functions","description":"  PO files are textfiles which contains translations. These are used by localized programs using gettext.\r\n  Ever saw the Emacs PO mode? It's great. This little filetype plugin tries to at least give you some help editing those PO files, and while it's certainly not (yet?) as good as the Emacs PO mode, it's good enough to get the work done.\r\n  This script adds some menu entries. No keystrokes defined. There are search functions for the next untranslated entry, the next fuzzy entry, or both; there's a \"remove fuzzy\" entry. To edit longer entries use \"remove quotes\"; you then can edit the entry as you like (using \"gq\", for instance); afterwards add the quotes again with \"add quotes\". When you're finished, send your file to the translation project (but take care that you filename must be the name the TP Robot requires - use a symlink, for instance).","4":"  PO files are textfiles which contains translations. These are used by localized programs using gettext.\r\n  Ever saw the Emacs PO mode? It's great. This little filetype plugin tries to at least give you some help editing those PO files, and while it's certainly not (yet?) as good as the Emacs PO mode, it's good enough to get the work done.\r\n  This script adds some menu entries. No keystrokes defined. There are search functions for the next untranslated entry, the next fuzzy entry, or both; there's a \"remove fuzzy\" entry. To edit longer entries use \"remove quotes\"; you then can edit the entry as you like (using \"gq\", for instance); afterwards add the quotes again with \"add quotes\". When you're finished, send your file to the translation project (but take care that you filename must be the name the TP Robot requires - use a symlink, for instance).","install_details":"  You can just source it, but it's better to put it into a filetype plugin directory, such as .vim\/ftplugin. Vim will then load it automatically.","5":"  You can just source it, but it's better to put it into a filetype plugin directory, such as .vim\/ftplugin. Vim will then load it automatically.","first_name":"Michael","6":"Michael","last_name":"Piefel","7":"Piefel","releases":[{"0":"64","vim_version":"6.0","1":"6.0","script_version":"20011221","2":"20011221","version_comment":"This Christmas release features an improved \"Send to Translation Project\" function. The plugin can now figure out the correct subject to use for the robot. Core functionality is unchanged.","3":"This Christmas release features an improved \"Send to Translation Project\" function. The plugin can now figure out the correct subject to use for the robot. Core functionality is unchanged.","package":"po.vim","4":"po.vim","src_id":"433","5":"433","creation_date":"1008910011","6":"1008910011"},{"0":"64","vim_version":"6.0","1":"6.0","script_version":"20010530","2":"20010530","version_comment":"Initial upload","3":"Initial upload","package":"po.vim","4":"po.vim","src_id":"118","5":"118","creation_date":"998292844","6":"998292844"}]},"63":{"script_id":"63","0":"63","script_name":"emacs.vim","1":"emacs.vim","script_type":"color scheme","2":"color scheme","summary":"Emacs like colors","3":"Emacs like colors","description":"  This colorscheme implements colors that let Vim look just a little like Emacs.\r\n  It is not perfect in several respects: For one Emacs has very different categories for its syntax highlighting. Many more, often, which tends to let your screen light up like a christmas tree sometimes. I can't reproduce that without changing the syntax files, and I don't want that. The scheme tries to look like Emacs, but I only really checked for C++. The most important thing is the color of comments, and these are right. The other aspect is the suitability of the script for terminal based Vims - I didn't check, it's for GVim.\r\n","4":"  This colorscheme implements colors that let Vim look just a little like Emacs.\r\n  It is not perfect in several respects: For one Emacs has very different categories for its syntax highlighting. Many more, often, which tends to let your screen light up like a christmas tree sometimes. I can't reproduce that without changing the syntax files, and I don't want that. The scheme tries to look like Emacs, but I only really checked for C++. The most important thing is the color of comments, and these are right. The other aspect is the suitability of the script for terminal based Vims - I didn't check, it's for GVim.\r\n","install_details":"  You can just source the script whenever you want. That way it even works in older Vims, but with warnings - ignore them.\r\n  If you put it in a color directory, for instance .vim\/colors, the color scheme will pop up in the menu, where you can choose it, or you can use  the \":colorscheme emacs\" command.","5":"  You can just source the script whenever you want. That way it even works in older Vims, but with warnings - ignore them.\r\n  If you put it in a color directory, for instance .vim\/colors, the color scheme will pop up in the menu, where you can choose it, or you can use  the \":colorscheme emacs\" command.","first_name":"Michael","6":"Michael","last_name":"Piefel","7":"Piefel","releases":[{"0":"63","vim_version":"6.0","1":"6.0","script_version":"20010816","2":"20010816","version_comment":"Initial upload","3":"Initial upload","package":"emacs.vim","4":"emacs.vim","src_id":"117","5":"117","creation_date":"998290983","6":"998290983"}]},"62":{"script_id":"62","0":"62","script_name":"whatdomain.vim","1":"whatdomain.vim","script_type":"utility","2":"utility","summary":"Find out meaning of Top Level Domain","3":"Find out meaning of Top Level Domain","description":"If you ever wondered what country the domain .tv belonged to, you had to look it up in some database - you had to leave Vim. No More!\r\nThis plugin offers you a simple function which will identify the domain and print it out. You can call the function WhatDomain directly (with one string argument, the TLD), ot even better, use the following command on the Vim command line:\r\n    :WhatDomain\r\nIt will ask you for the domain you want to have identified and subsequently prints out which country or category this domain belongs to. You can also pass the domain you ask for as a parameter (:WhatDomain de) or use the function call syntax (:call WhatDomain).","4":"If you ever wondered what country the domain .tv belonged to, you had to look it up in some database - you had to leave Vim. No More!\r\nThis plugin offers you a simple function which will identify the domain and print it out. You can call the function WhatDomain directly (with one string argument, the TLD), ot even better, use the following command on the Vim command line:\r\n    :WhatDomain\r\nIt will ask you for the domain you want to have identified and subsequently prints out which country or category this domain belongs to. You can also pass the domain you ask for as a parameter (:WhatDomain de) or use the function call syntax (:call WhatDomain).","install_details":"Just source this file at any point. To have it always available, simply put it in you .vim\/plugin directory.","5":"Just source this file at any point. To have it always available, simply put it in you .vim\/plugin directory.","first_name":"Michael","6":"Michael","last_name":"Piefel","7":"Piefel","releases":[{"0":"62","vim_version":"6.0","1":"6.0","script_version":"20010919","2":"20010919","version_comment":"Thanks to a patch by Salman Halim you can now also call the routine with the domain as a parameter.","3":"Thanks to a patch by Salman Halim you can now also call the routine with the domain as a parameter.","package":"whatdomain.vim","4":"whatdomain.vim","src_id":"172","5":"172","creation_date":"1000880172","6":"1000880172"},{"0":"62","vim_version":"6.0","1":"6.0","script_version":"20010820","2":"20010820","version_comment":"Initial upload","3":"Initial upload","package":"whatdomain.vim","4":"whatdomain.vim","src_id":"116","5":"116","creation_date":"998289811","6":"998289811"}]},"61":{"script_id":"61","0":"61","script_name":"Embperl_Syntax.zip","1":"Embperl_Syntax.zip","script_type":"syntax","2":"syntax","summary":"Syntax for Embperl","3":"Syntax for Embperl","description":"Rewrite of the official embperl syntax file. There is a color scheme for setting GUI like Interdev (yellow perl code).\r\n\r\nThis is \"beta\" version of the script. It needs more testing (in vim < 6.0).","4":"Rewrite of the official embperl syntax file. There is a color scheme for setting GUI like Interdev (yellow perl code).\r\n\r\nThis is \"beta\" version of the script. It needs more testing (in vim < 6.0).","install_details":"Just unpack and see the config example at the begining in syntax\/embperl.vim.","5":"Just unpack and see the config example at the begining in syntax\/embperl.vim.","first_name":"Lukas","6":"Lukas","last_name":"Zapletal","7":"Zapletal","releases":[{"0":"61","vim_version":"6.0","1":"6.0","script_version":"1.2","2":"1.2","version_comment":"Minor bugfixes","3":"Minor bugfixes","package":"Embperl_Syntax.zip","4":"Embperl_Syntax.zip","src_id":"182","5":"182","creation_date":"1001026259","6":"1001026259"},{"0":"61","vim_version":"6.0","1":"6.0","script_version":"1.1","2":"1.1","version_comment":"Fixes [$ $] errors, yellow (interdev) coloring and documentation.","3":"Fixes [$ $] errors, yellow (interdev) coloring and documentation.","package":"Embperl_Syntax.zip","4":"Embperl_Syntax.zip","src_id":"115","5":"115","creation_date":"998271402","6":"998271402"},{"0":"61","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"Embperl_Syntax.zip","4":"Embperl_Syntax.zip","src_id":"107","5":"107","creation_date":"997847251","6":"997847251"}]},"60":{"script_id":"60","0":"60","script_name":"delphi.vim","1":"delphi.vim","script_type":"syntax","2":"syntax","summary":"Syntax file for Borlands Delphi\/Kylix","3":"Syntax file for Borlands Delphi\/Kylix","description":"This syntax file for Borlands ObjectPascal (Delphi,Kylix) is derived from the original pascal.vim.\r\nSome basic VCL-Classes are added and some keywords have new meanings (e.g. read\/write, assign).\r\nIt also includes a different color scheme.\r\n","4":"This syntax file for Borlands ObjectPascal (Delphi,Kylix) is derived from the original pascal.vim.\r\nSome basic VCL-Classes are added and some keywords have new meanings (e.g. read\/write, assign).\r\nIt also includes a different color scheme.\r\n","install_details":"1. Copy the file to $VIM\/sytax.\r\n2. Add to $VIM\/filetype.vim :\r\nCUT FROM HERE-->\r\n\" Pascal \/ Delphi\r\nif (1==1)\t\"change to \"1==0\" to use original syntax\r\n  au BufNewFile,BufRead *.pas,*.PAS\t\tset ft=delphi\r\nelse\r\n  au BufNewFile,BufRead *.pas,*.PAS\t\tset ft=pascal\r\nendif\r\n\" Delphi project file\r\nau BufNewFile,BufRead *.dpr,*.DPR\t\tset ft=delphi\r\n\" Delphi form file\r\nau BufNewFile,BufRead *.dfm,*.DFM\t\tset ft=delphi\r\nau BufNewFile,BufRead *.xfm,*.XFM\t\tset ft=delphi\r\n\" Delphi package file\r\nau BufNewFile,BufRead *.dpk,*.DPK\t\tset ft=delphi\r\n\" Delphi .DOF file = INI file for MSDOS\r\nau BufNewFile,BufRead *.dof,*.DOF\t\tset ft=dosini\r\nau BufNewFile,BufRead *.kof,*.KOF\t\tset ft=dosini\r\nau BufNewFile,BufRead *.dsk,*.DSK\t\tset ft=dosini\r\nau BufNewFile,BufRead *.desk,*.DESK\t\tset ft=dosini\r\nau BufNewFile,BufRead *.dti,*.DTI\t\tset ft=dosini\r\n\" Delphi .BPG = Makefile\r\nau BufNewFile,BufRead *.bpg,*.BPG\t\tset ft=make|setlocal makeprg=make\\ -f\\ %\r\n<--CUT UNTIL HERE\r\n","5":"1. Copy the file to $VIM\/sytax.\r\n2. Add to $VIM\/filetype.vim :\r\nCUT FROM HERE-->\r\n\" Pascal \/ Delphi\r\nif (1==1)\t\"change to \"1==0\" to use original syntax\r\n  au BufNewFile,BufRead *.pas,*.PAS\t\tset ft=delphi\r\nelse\r\n  au BufNewFile,BufRead *.pas,*.PAS\t\tset ft=pascal\r\nendif\r\n\" Delphi project file\r\nau BufNewFile,BufRead *.dpr,*.DPR\t\tset ft=delphi\r\n\" Delphi form file\r\nau BufNewFile,BufRead *.dfm,*.DFM\t\tset ft=delphi\r\nau BufNewFile,BufRead *.xfm,*.XFM\t\tset ft=delphi\r\n\" Delphi package file\r\nau BufNewFile,BufRead *.dpk,*.DPK\t\tset ft=delphi\r\n\" Delphi .DOF file = INI file for MSDOS\r\nau BufNewFile,BufRead *.dof,*.DOF\t\tset ft=dosini\r\nau BufNewFile,BufRead *.kof,*.KOF\t\tset ft=dosini\r\nau BufNewFile,BufRead *.dsk,*.DSK\t\tset ft=dosini\r\nau BufNewFile,BufRead *.desk,*.DESK\t\tset ft=dosini\r\nau BufNewFile,BufRead *.dti,*.DTI\t\tset ft=dosini\r\n\" Delphi .BPG = Makefile\r\nau BufNewFile,BufRead *.bpg,*.BPG\t\tset ft=make|setlocal makeprg=make\\ -f\\ %\r\n<--CUT UNTIL HERE\r\n","first_name":"Thorsten","6":"Thorsten","last_name":"Maerz","7":"Maerz","releases":[{"0":"60","vim_version":"6.0","1":"6.0","script_version":"1.1","2":"1.1","version_comment":"Initial upload","3":"Initial upload","package":"delphi.vim","4":"delphi.vim","src_id":"100","5":"100","creation_date":"997611100","6":"997611100"}]},"59":{"script_id":"59","0":"59","script_name":"dtags","1":"dtags","script_type":"utility","2":"utility","summary":"Create tag files for Borland Delphi\/Kylix","3":"Create tag files for Borland Delphi\/Kylix","description":"This Perl script scans (a given or local) directory tree for Delphi\/Kylix files and prints a tag-file to stdout.\r\n","4":"This Perl script scans (a given or local) directory tree for Delphi\/Kylix files and prints a tag-file to stdout.\r\n","install_details":"- install perl\r\n- execute \"perl dtags \/mysrc\/test\/ > tags\" to create a tagfile from directory \"\/mysrc\/test\"\r\n- use \":set tags\" to set the location of your tagfiles","5":"- install perl\r\n- execute \"perl dtags \/mysrc\/test\/ > tags\" to create a tagfile from directory \"\/mysrc\/test\"\r\n- use \":set tags\" to set the location of your tagfiles","first_name":"Thorsten","6":"Thorsten","last_name":"Maerz","7":"Maerz","releases":[{"0":"59","vim_version":"6.0","1":"6.0","script_version":"1.2","2":"1.2","version_comment":"Initial upload","3":"Initial upload","package":"dtags","4":"dtags","src_id":"99","5":"99","creation_date":"997609597","6":"997609597"}]},"58":{"script_id":"58","0":"58","script_name":"cvsmenu.vim","1":"cvsmenu.vim","script_type":"utility","2":"utility","summary":"Menu for CVS-Versioncontrol","3":"Menu for CVS-Versioncontrol","description":"Supports most cvs commands and adds som extended functions, e.g. \r\n- Query update (like WinCVS\/gCVS)\r\n- Local Status (offline: displays status and version info)\r\n- Clickable\/sorted output : easily open conflicting files, etc.\r\nWorks on single files as well as on whole directories, when called from fileexplorer.\r\nIncludes highlighting \/ mappings to navigate through cvs output or show conflicts.","4":"Supports most cvs commands and adds som extended functions, e.g. \r\n- Query update (like WinCVS\/gCVS)\r\n- Local Status (offline: displays status and version info)\r\n- Clickable\/sorted output : easily open conflicting files, etc.\r\nWorks on single files as well as on whole directories, when called from fileexplorer.\r\nIncludes highlighting \/ mappings to navigate through cvs output or show conflicts.","install_details":"Copy to $VIM\/plugin directory.\r\nUse \"CVS\/Settings\/Install\/Install updates\" to checkout and install latest script and documentation","5":"Copy to $VIM\/plugin directory.\r\nUse \"CVS\/Settings\/Install\/Install updates\" to checkout and install latest script and documentation","first_name":"Thorsten","6":"Thorsten","last_name":"Maerz","7":"Maerz","releases":[{"0":"58","vim_version":"6.0","1":"6.0","script_version":"1.77","2":"1.77","version_comment":"some bugfixes, new keymappings in output window","3":"some bugfixes, new keymappings in output window","package":"cvsmenu.vim","4":"cvsmenu.vim","src_id":"342","5":"342","creation_date":"1005581696","6":"1005581696"},{"0":"58","vim_version":"6.0","1":"6.0","script_version":"1.72","2":"1.72","version_comment":":CVS command for direct access\r\nCreate patchfiles\r\nJoinIn (add & commit with default message)\r\nimproved output handling","3":":CVS command for direct access\r\nCreate patchfiles\r\nJoinIn (add & commit with default message)\r\nimproved output handling","package":"cvsmenu.vim","4":"cvsmenu.vim","src_id":"223","5":"223","creation_date":"1002000778","6":"1002000778"},{"0":"58","vim_version":"6.0","1":"6.0","script_version":"1.58","2":"1.58","version_comment":"cvs output displayed\/remembered in titlebar\nshow local status (revision, etc.) when opening a file (offline)\ndiff : restore settings when finished","3":"cvs output displayed\/remembered in titlebar\nshow local status (revision, etc.) when opening a file (offline)\ndiff : restore settings when finished","package":"cvsmenu.vim","4":"cvsmenu.vim","src_id":"159","5":"159","creation_date":"999948109","6":"999948109"},{"0":"58","vim_version":"6.0","1":"6.0","script_version":"1.42","2":"1.42","version_comment":"improvements:\n- local status (works offline)\n- less output, (fits in statusline, if success)\n- unknown files shown\n- revised settings menu\nfixes:\n- conflict syntax","3":"improvements:\n- local status (works offline)\n- less output, (fits in statusline, if success)\n- unknown files shown\n- revised settings menu\nfixes:\n- conflict syntax","package":"cvsmenu.vim","4":"cvsmenu.vim","src_id":"145","5":"145","creation_date":"999357845","6":"999357845"},{"0":"58","vim_version":"6.0","1":"6.0","script_version":"1.37","2":"1.37","version_comment":"less \"AnyKey\"-prompts\nsorted output (conflicts moved to top,etc.)\n","3":"less \"AnyKey\"-prompts\nsorted output (conflicts moved to top,etc.)\n","package":"cvsmenu.vim","4":"cvsmenu.vim","src_id":"140","5":"140","creation_date":"999001668","6":"999001668"},{"0":"58","vim_version":"6.0","1":"6.0","script_version":"1.31","2":"1.31","version_comment":"Bugfix:Install updates","3":"Bugfix:Install updates","package":"cvsmenu.vim","4":"cvsmenu.vim","src_id":"138","5":"138","creation_date":"998929863","6":"998929863"},{"0":"58","vim_version":"6.0","1":"6.0","script_version":"1.30","2":"1.30","version_comment":"output to statusline (optional)\nCVS based installer\/updater\nconflict highlighting by default","3":"output to statusline (optional)\nCVS based installer\/updater\nconflict highlighting by default","package":"cvsmenu.vim","4":"cvsmenu.vim","src_id":"137","5":"137","creation_date":"998927151","6":"998927151"},{"0":"58","vim_version":"6.0","1":"6.0","script_version":"1.22","2":"1.22","version_comment":"- added keymappings (there are so little:)\r\n- added LGPL note","3":"- added keymappings (there are so little:)\r\n- added LGPL note","package":"cvsmenu.vim","4":"cvsmenu.vim","src_id":"130","5":"130","creation_date":"998478744","6":"998478744"},{"0":"58","vim_version":"6.0","1":"6.0","script_version":"1.19","2":"1.19","version_comment":"added menus: update to rev, merge changes from branch\/between 2 branches\r\nlink to online doku\/latest rev.,\r\nsettings, conflict highlighting","3":"added menus: update to rev, merge changes from branch\/between 2 branches\r\nlink to online doku\/latest rev.,\r\nsettings, conflict highlighting","package":"cvsmenu.vim","4":"cvsmenu.vim","src_id":"122","5":"122","creation_date":"998318602","6":"998318602"},{"0":"58","vim_version":"6.0","1":"6.0","script_version":"1.16","2":"1.16","version_comment":"added \"tagging\/branching\",\"import\",\"watch\",\"edit\",\"revert changes\"\nFeel free to send comments, tips, help requests, etc. to info@netztorte.de","3":"added \"tagging\/branching\",\"import\",\"watch\",\"edit\",\"revert changes\"\nFeel free to send comments, tips, help requests, etc. to info@netztorte.de","package":"cvsmenu.vim","4":"cvsmenu.vim","src_id":"114","5":"114","creation_date":"998225665","6":"998225665"},{"0":"58","vim_version":"6.0","1":"6.0","script_version":"1.14","2":"1.14","version_comment":"better support for directories\/single files\ninsert CVS keywords","3":"better support for directories\/single files\ninsert CVS keywords","package":"cvsmenu.vim","4":"cvsmenu.vim","src_id":"113","5":"113","creation_date":"998077500","6":"998077500"},{"0":"58","vim_version":"6.0","1":"6.0","script_version":"1.10","2":"1.10","version_comment":"added \"release\", \"remove\", \"short status\" (list files sorted by status)\r\nmajor fixes : tempfiles deleted, jump to file ([shift-cr],dblclick) from every output\r\n","3":"added \"release\", \"remove\", \"short status\" (list files sorted by status)\r\nmajor fixes : tempfiles deleted, jump to file ([shift-cr],dblclick) from every output\r\n","package":"cvsmenu.vim","4":"cvsmenu.vim","src_id":"112","5":"112","creation_date":"997950402","6":"997950402"},{"0":"58","vim_version":"6.0","1":"6.0","script_version":"1.7","2":"1.7","version_comment":"added login\/out,add,history,global options,new menu structure,...\r\nhttp:\/\/ezytools.sf.net\/VimTools\/\r\nto get the latest version and documentation","3":"added login\/out,add,history,global options,new menu structure,...\r\nhttp:\/\/ezytools.sf.net\/VimTools\/\r\nto get the latest version and documentation","package":"cvsmenu.vim","4":"cvsmenu.vim","src_id":"104","5":"104","creation_date":"997712432","6":"997712432"},{"0":"58","vim_version":"6.0","1":"6.0","script_version":"1.4","2":"1.4","version_comment":"- Fixes for \"checkout\" and \"queryupdate\"\r\n- Continued at CVS repository : (VimTools section)\r\nhttp:\/\/ezytools.sourceforge.net\/\r\n","3":"- Fixes for \"checkout\" and \"queryupdate\"\r\n- Continued at CVS repository : (VimTools section)\r\nhttp:\/\/ezytools.sourceforge.net\/\r\n","package":"cvsmenu.vim","4":"cvsmenu.vim","src_id":"103","5":"103","creation_date":"997667174","6":"997667174"},{"0":"58","vim_version":"6.0","1":"6.0","script_version":"1.2","2":"1.2","version_comment":"Added \"commit\", \"checkout\" and \"update\"\nAdded settings\/info menu\nMinor fixes","3":"Added \"commit\", \"checkout\" and \"update\"\nAdded settings\/info menu\nMinor fixes","package":"cvsmenu.vim","4":"cvsmenu.vim","src_id":"102","5":"102","creation_date":"997631560","6":"997631560"},{"0":"58","vim_version":"6.0","1":"6.0","script_version":"1.1","2":"1.1","version_comment":"Initial upload","3":"Initial upload","package":"cvsmenu.vim","4":"cvsmenu.vim","src_id":"98","5":"98","creation_date":"997608234","6":"997608234"}]},"57":{"script_id":"57","0":"57","script_name":"oberon.vim","1":"oberon.vim","script_type":"syntax","2":"syntax","summary":"simple Oberon syntax file","3":"simple Oberon syntax file","description":"oberon.vim is a very simple syntax file to get a colored view of Oberon modules (*.Mod files)...","4":"oberon.vim is a very simple syntax file to get a colored view of Oberon modules (*.Mod files)...","install_details":"See syntax.txt within you VIM distribution or look at http:\/\/www.copyleft.de\/pub\/author\/sbeyer\/junk\/oberon.vim-help ...","5":"See syntax.txt within you VIM distribution or look at http:\/\/www.copyleft.de\/pub\/author\/sbeyer\/junk\/oberon.vim-help ...","first_name":"Stephan","6":"Stephan","last_name":"Beyer","7":"Beyer","releases":[{"0":"57","vim_version":"6.0","1":"6.0","script_version":"20010808","2":"20010808","version_comment":"Initial upload","3":"Initial upload","package":"oberon.vim","4":"oberon.vim","src_id":"88","5":"88","creation_date":"997251269","6":"997251269"}]},"56":{"script_id":"56","0":"56","script_name":"perl.vim","1":"perl.vim","script_type":"utility","2":"utility","summary":"Perl compiler script","3":"Perl compiler script","description":"This is compiler script that runs perl -Wc and parses all error and warnings. For more information how to use compilers in VIM read help.\r\n\r\nThis version has workaround with redirecting stderr on windows platform so it can run either on unixes or windows.\r\n\r\nEnjoy. Lukas","4":"This is compiler script that runs perl -Wc and parses all error and warnings. For more information how to use compilers in VIM read help.\r\n\r\nThis version has workaround with redirecting stderr on windows platform so it can run either on unixes or windows.\r\n\r\nEnjoy. Lukas","install_details":"Just put in the $VIMRUNTIME\/compiler directory and run :make.","5":"Just put in the $VIMRUNTIME\/compiler directory and run :make.","first_name":"Lukas","6":"Lukas","last_name":"Zapletal","7":"Zapletal","releases":[{"0":"56","vim_version":"6.0","1":"6.0","script_version":"1.1","2":"1.1","version_comment":"I made a mistake so the script didn`t manage errors ending ', near \"...\"' correctly. Now it is fixed.\r\n\r\nI know VIM 6.0 has tools\/efm_perl.pl - but this is not working under Windows and it is slower (because perl is called twice).","3":"I made a mistake so the script didn`t manage errors ending ', near \"...\"' correctly. Now it is fixed.\r\n\r\nI know VIM 6.0 has tools\/efm_perl.pl - but this is not working under Windows and it is slower (because perl is called twice).","package":"perl.vim","4":"perl.vim","src_id":"91","5":"91","creation_date":"997332284","6":"997332284"},{"0":"56","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"perl.vim","4":"perl.vim","src_id":"87","5":"87","creation_date":"997247871","6":"997247871"}]},"55":{"script_id":"55","0":"55","script_name":"TagsMenu.zip","1":"TagsMenu.zip","script_type":"utility","2":"utility","summary":"Creates a menu of all the tags in the current file.","3":"Creates a menu of all the tags in the current file.","description":"*TagsMenu.txt*   Plugin to add all known tags to a menu.\r\n\r\n--------------------------------------------------------------------------\r\nThe following is a cut-and-paste of the TagsMenu help file that is packaged in the attached zip file.\r\n--------------------------------------------------------------------------\r\n\r\nPURPOSE                                             *TagsMenu-purpose*\r\n\r\nThis plugin will find all the tags in the current file, and make a menu of these tags.  Each menu item is a move command to that tag (not actually a :tag command, but a \/unique search pattern\/ to that tag).\r\n\r\n\r\nREQUIREMENTS                                        *TagsMenu-requirements*\r\n\r\nThe only requirement for this plugin to work is that Exuberant Ctags (see |ctags|) version 5.x is installed somewhere in your path.  If you do have it installed but not in your path, you could also set the |TagsMenu_ctagsCommand| to explicitly point to your ctags installation.  No other external requirements are necessary.\r\n\r\n\r\nINSTALLATION                                        *TagsMenu-installation*\r\n\r\nTo add the plugin, see the vim help on the subject |add-global-plugin| (:h add-global-plugin).  To add the accompanying help file, see the vim help on the subject |add-local-help|.\r\n\r\n\r\nEXECUTION                                           *TagsMenu-execution*\r\n\r\nAutomatic execution:  the plugin will automaticly execute (depending on the value of the |TagsMenu_useAutoCommand| option) when a buffer is entered of a recognized filetype (see |TagsMenu-filetypes|).\r\n\r\nManual execution:  there are two ways to manually force the recalculation of the menu: \r\n    <leader>t\r\n        - this mapping depends on the value of <leader> for your configuration.  By default it is '\\'.  See |mapleader|.\r\n    menu Tags -> Rebuild Tags Menu \r\n        - this will only appear if the tags menu has already been created.\r\n\r\n\r\nREGOGNIZED FILETYPES                                *TagsMenu-filetypes*\r\n\r\nThe current list of recognized |filetypes| is limited to the list of types recognized by ctags.  These include: asm, awk, c, cpp, cxx, sh, cobol, eiffel, fortran, java, lisp, make, pascal, perl, php, python, rexx, ruby, scheme, tcl, and vim.\r\n\r\n\r\n\r\nVersion: 0.93\r\nAuthor: Jay Dickon Glanville (plus others) <jayglanville at rogers.com>\r\nLocation: http:\/\/members.rogers.com\/jayglanville\/tagsmenu\r\nLast Modified: 4 Dec 2001\r\n","4":"*TagsMenu.txt*   Plugin to add all known tags to a menu.\r\n\r\n--------------------------------------------------------------------------\r\nThe following is a cut-and-paste of the TagsMenu help file that is packaged in the attached zip file.\r\n--------------------------------------------------------------------------\r\n\r\nPURPOSE                                             *TagsMenu-purpose*\r\n\r\nThis plugin will find all the tags in the current file, and make a menu of these tags.  Each menu item is a move command to that tag (not actually a :tag command, but a \/unique search pattern\/ to that tag).\r\n\r\n\r\nREQUIREMENTS                                        *TagsMenu-requirements*\r\n\r\nThe only requirement for this plugin to work is that Exuberant Ctags (see |ctags|) version 5.x is installed somewhere in your path.  If you do have it installed but not in your path, you could also set the |TagsMenu_ctagsCommand| to explicitly point to your ctags installation.  No other external requirements are necessary.\r\n\r\n\r\nINSTALLATION                                        *TagsMenu-installation*\r\n\r\nTo add the plugin, see the vim help on the subject |add-global-plugin| (:h add-global-plugin).  To add the accompanying help file, see the vim help on the subject |add-local-help|.\r\n\r\n\r\nEXECUTION                                           *TagsMenu-execution*\r\n\r\nAutomatic execution:  the plugin will automaticly execute (depending on the value of the |TagsMenu_useAutoCommand| option) when a buffer is entered of a recognized filetype (see |TagsMenu-filetypes|).\r\n\r\nManual execution:  there are two ways to manually force the recalculation of the menu: \r\n    <leader>t\r\n        - this mapping depends on the value of <leader> for your configuration.  By default it is '\\'.  See |mapleader|.\r\n    menu Tags -> Rebuild Tags Menu \r\n        - this will only appear if the tags menu has already been created.\r\n\r\n\r\nREGOGNIZED FILETYPES                                *TagsMenu-filetypes*\r\n\r\nThe current list of recognized |filetypes| is limited to the list of types recognized by ctags.  These include: asm, awk, c, cpp, cxx, sh, cobol, eiffel, fortran, java, lisp, make, pascal, perl, php, python, rexx, ruby, scheme, tcl, and vim.\r\n\r\n\r\n\r\nVersion: 0.93\r\nAuthor: Jay Dickon Glanville (plus others) <jayglanville at rogers.com>\r\nLocation: http:\/\/members.rogers.com\/jayglanville\/tagsmenu\r\nLast Modified: 4 Dec 2001\r\n","install_details":"This is a Vim 6.0 plugin.  Therefore, it is only available to version 6.0 vim.  As a plugin, drop the TagsMenu.vim file into your personal plugin directory, and the TagsMenu.txt help file into your personal doc directory.","5":"This is a Vim 6.0 plugin.  Therefore, it is only available to version 6.0 vim.  As a plugin, drop the TagsMenu.vim file into your personal plugin directory, and the TagsMenu.txt help file into your personal doc directory.","first_name":"Jay Dickon","6":"Jay Dickon","last_name":"Glanville","7":"Glanville","releases":[{"0":"55","vim_version":"6.0","1":"6.0","script_version":"0.93","2":"0.93","version_comment":"- added ability to toggle options from the menu\r\n- added ability to group by first character (this helps shorten long menu lists)\r\n- minor internal changes that help solve some bugs\r\n\r\nFor full information, goto http:\/\/members.rogers.com\/jayglanville\/tagsmenu","3":"- added ability to toggle options from the menu\r\n- added ability to group by first character (this helps shorten long menu lists)\r\n- minor internal changes that help solve some bugs\r\n\r\nFor full information, goto http:\/\/members.rogers.com\/jayglanville\/tagsmenu","package":"TagsMenu.zip","4":"TagsMenu.zip","src_id":"402","5":"402","creation_date":"1007467539","6":"1007467539"},{"0":"55","vim_version":"6.0","1":"6.0","script_version":"0.91","2":"0.91","version_comment":"Initial upload","3":"Initial upload","package":"TagsMenu.zip","4":"TagsMenu.zip","src_id":"86","5":"86","creation_date":"997178668","6":"997178668"}]},"54":{"script_id":"54","0":"54","script_name":"ConvertBase.vim","1":"ConvertBase.vim","script_type":"utility","2":"utility","summary":"Convert to\/from various numeric bases","3":"Convert to\/from various numeric bases","description":"This script is basically just three functions:\r\n  ConvertToBase(int, base)\r\n  ConvertFromBase(str, base)\r\n  ConvertBases(str, base1, base2)\r\n\r\nAnd two example functions that are commented out.\r\n\r\nThe following mappings may also be useful:\r\n\" Translate the character under the cursor to a decimal value:\r\nnmap <M-a>d i<C-R>=char2nr(getline(line(\".\"))[col(\".\") - 1])<CR><ESC>lx\r\n\" ... hexadecimal value:\r\nnmap <M-a>h ix<C-R>=ConvertToBase(char2nr(getline(line(\".\"))[col(\".\") - 1]),16)<CR><ESC>lx\r\n\" ... octal value:\r\nnmap <M-a>o i<C-R>=ConvertToBase(char2nr(getline(line(\".\"))[col(\".\") - 1]),8)<CR><ESC>lx","4":"This script is basically just three functions:\r\n  ConvertToBase(int, base)\r\n  ConvertFromBase(str, base)\r\n  ConvertBases(str, base1, base2)\r\n\r\nAnd two example functions that are commented out.\r\n\r\nThe following mappings may also be useful:\r\n\" Translate the character under the cursor to a decimal value:\r\nnmap <M-a>d i<C-R>=char2nr(getline(line(\".\"))[col(\".\") - 1])<CR><ESC>lx\r\n\" ... hexadecimal value:\r\nnmap <M-a>h ix<C-R>=ConvertToBase(char2nr(getline(line(\".\"))[col(\".\") - 1]),16)<CR><ESC>lx\r\n\" ... octal value:\r\nnmap <M-a>o i<C-R>=ConvertToBase(char2nr(getline(line(\".\"))[col(\".\") - 1]),8)<CR><ESC>lx","install_details":"Source the script or place it in your plugin directory.","5":"Source the script or place it in your plugin directory.","first_name":"Christian J.","6":"Christian J.","last_name":"Robinson","7":"Robinson","releases":[{"0":"54","vim_version":"9.0","1":"9.0","script_version":"2.0","2":"2.0","version_comment":"- Update for Vim 9 (no features added)","3":"- Update for Vim 9 (no features added)","package":"ConvertBase.vim","4":"ConvertBase.vim","src_id":"28141","5":"28141","creation_date":"1661153976","6":"1661153976"},{"0":"54","vim_version":"5.7","1":"5.7","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"ConvertBase.vim","4":"ConvertBase.vim","src_id":"84","5":"84","creation_date":"997102431","6":"997102431"}]},"53":{"script_id":"53","0":"53","script_name":"colorize.vim","1":"colorize.vim","script_type":"utility","2":"utility","summary":"Change background color when in insert mode","3":"Change background color when in insert mode","description":"It is hard to adjust to command\/insert mode.  \r\nIf you don't pay attention, all that typing is lost, etc.\r\nThese lines are added to your resource file _gvimrc\r\nand will change the background color when you\r\ngo into insert mode (not every key, but the main\r\nones i,s,a,and o.)  The color changes back when\r\nyou press escape.\r\nVery helpful for newbies!\r\n","4":"It is hard to adjust to command\/insert mode.  \r\nIf you don't pay attention, all that typing is lost, etc.\r\nThese lines are added to your resource file _gvimrc\r\nand will change the background color when you\r\ngo into insert mode (not every key, but the main\r\nones i,s,a,and o.)  The color changes back when\r\nyou press escape.\r\nVery helpful for newbies!\r\n","install_details":"Open the _gvimrc file, copy\/paste the lines\r\nnear the bottom of the file into it.\r\n","5":"Open the _gvimrc file, copy\/paste the lines\r\nnear the bottom of the file into it.\r\n","first_name":"doug","6":"doug","last_name":"edmunds","7":"edmunds","releases":[{"0":"53","vim_version":"5.7","1":"5.7","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"colorize.vim","4":"colorize.vim","src_id":"79","5":"79","creation_date":"996689321","6":"996689321"}]},"52":{"script_id":"52","0":"52","script_name":"calendar.vim","1":"calendar.vim","script_type":"utility","2":"utility","summary":"Calendar","3":"Calendar","description":"This script create calender window. \nThis don't use the external program(cal).\n","4":"This script create calender window. \nThis don't use the external program(cal).\n","install_details":"Copy calendar.vim to your plugin directory.\n","5":"Copy calendar.vim to your plugin directory.\n","first_name":"Yasuhiro","6":"Yasuhiro","last_name":"Matsumoto","7":"Matsumoto","releases":[{"0":"52","vim_version":"7.2","1":"7.2","script_version":"2.9","2":"2.9","version_comment":"[fix] missing file\n","3":"[fix] missing file\n","package":"calendar-vim.zip","4":"calendar-vim.zip","src_id":"19707","5":"19707","creation_date":"1364296525","6":"1364296525"},{"0":"52","vim_version":"6.0","1":"6.0","script_version":"2.8","2":"2.8","version_comment":"[fix] fix keymap\n","3":"[fix] fix keymap\n","package":"calendar.vim","4":"calendar.vim","src_id":"19661","5":"19661","creation_date":"1363656033","6":"1363656033"},{"0":"52","vim_version":"6.0","1":"6.0","script_version":"2.7","2":"2.7","version_comment":"vim7ish, customizable key bindings\n","3":"vim7ish, customizable key bindings\n","package":"calendar.vim","4":"calendar.vim","src_id":"19660","5":"19660","creation_date":"1363655412","6":"1363655412"},{"0":"52","vim_version":"6.0","1":"6.0","script_version":"2.5","2":"2.5","version_comment":"[fix] 7.2 don't have relativenumber.\n","3":"[fix] 7.2 don't have relativenumber.\n","package":"calendar.vim","4":"calendar.vim","src_id":"14880","5":"14880","creation_date":"1296125854","6":"1296125854"},{"0":"52","vim_version":"6.0","1":"6.0","script_version":"2.4","2":"2.4","version_comment":"Applied patch from SethMilliken: added g:calendar_options . default is 'fdc=0 nonu nornu' . you can overwrite default behavior of calendar window.\n","3":"Applied patch from SethMilliken: added g:calendar_options . default is 'fdc=0 nonu nornu' . you can overwrite default behavior of calendar window.\n","package":"calendar.vim","4":"calendar.vim","src_id":"14879","5":"14879","creation_date":"1296108960","6":"1296108960"},{"0":"52","vim_version":"6.0","1":"6.0","script_version":"2.3","2":"2.3","version_comment":"Applied patch from bw1: fixed weeknum function.\n","3":"Applied patch from bw1: fixed weeknum function.\n","package":"calendar.vim","4":"calendar.vim","src_id":"14707","5":"14707","creation_date":"1294502491","6":"1294502491"},{"0":"52","vim_version":"6.0","1":"6.0","script_version":"2.2","2":"2.2","version_comment":"Applied patch:\n  http:\/\/gist.github.com\/355513#file_customizable_keymap.diff\n  http:\/\/gist.github.com\/355513#file_winfixwidth.diff\n","3":"Applied patch:\n  http:\/\/gist.github.com\/355513#file_customizable_keymap.diff\n  http:\/\/gist.github.com\/355513#file_winfixwidth.diff\n","package":"calendar.vim","4":"calendar.vim","src_id":"12959","5":"12959","creation_date":"1273105391","6":"1273105391"},{"0":"52","vim_version":"6.0","1":"6.0","script_version":"2.1","2":"2.1","version_comment":"Applied patch from thinca. Thanks.\n","3":"Applied patch from thinca. Thanks.\n","package":"calendar.vim","4":"calendar.vim","src_id":"12699","5":"12699","creation_date":"1269450262","6":"1269450262"},{"0":"52","vim_version":"6.0","1":"6.0","script_version":"2.0","2":"2.0","version_comment":"Applied patch from Ingo Karkat. Thanks.\n\n- ENH: Added a config setting g:calendar_datetime. This allows to remove the\ndisplay of the current date\/time in the title (I don't like it), and offers the\nwindow's statusline as an alternative.\n\n- BUG: The checks for g:calendar_action and g:calendar_sign should also check\nfor an existing, but empty variable. Otherwise, it is not possible to disable it\nin a .vimrc, because the sourcing of calendar.vim would initialize the variables.\n\n- BUG: In s:CalendarDoAction(), the check for g:calendar_action must come after\nthe \"navi\" handling; otherwise \"navi\" breaks if g:calendar_action is disabled\n(see above).\n\n- ENH: The :set wrapscan is ugly, because it is a global setting. The search()\ncommands already pass the 'w' flag, so the only remaining issue were the\nsearches via \/. I modified the 'G0\/...' search to 'G$?' (i.e. backward from end\nof buffer), so that 'wrapscan' isn't required any more. (Even better would be to\nuse search() for these jumps, too.) With this, I can also completely get rid of\nthe autocmds in case one does not want the date\/time in the title, neither (see\nabove).\n\n- Using :setlocal buftype=nofile instead of =nowrite; this is more suitable for\nthis kind of scratch buffer, and avoids that the path may be shown in the title\n\/ statusline (depending on the customization).\n\n- BUG: Replaced :setlocal nowrap with 'wrap'. Without this, the 'sidescrolloff'\nsetting may cause the left side of the calendar to disappear if the last\ninserted element is near the right window border. 'wrap' shouldn't matter,\nanyway, and 'sidescrolloff' is a global setting, unfortunately.\nTry :set sidescrolloff=3 in combination with :let g:calendar_navi = 'bottom' to\nreproduce.\n\n- BUG: The :normal i... for the navi rendering causes a trailing space after the\n\"Next>\" button. This way, I cannot quickly type \"G$<CR>\" to activate the next\nbutton. Now using :normal a... to append. This causes the entire navi to shift\none character to the right, but you could fix this by decreasing the column\ncounter.\n\n- ENH: Use :stopinsert in case we've gotten here from insert mode (via\n<C-O>:Calendar<CR>)...\n\n- Using :wincmd w instead of :normal <C-w>; it's simpler. (And you should always\nuse :normal! (with a bang) to avoid interference with user remappings!)\n\n- ENH: I noticed that <left> and <s-left> do the same thing, but in different\nways (one uses the navi and the latter is called by the former). I dropped the\nunintuitive shift mappings and instead do the jumps consistently in the navi,\nusing the b:Calendar... variables instead of that ugly maparg() stuff.\n\n- ENH: I noticed that <left> and <up> do the same thing. I changed <up>\/<down>\nto move an entire year, so one can quickly let the years pass...\n\n- ENH: the 'q' mapping now returns to the previous window, not the first one.\n","3":"Applied patch from Ingo Karkat. Thanks.\n\n- ENH: Added a config setting g:calendar_datetime. This allows to remove the\ndisplay of the current date\/time in the title (I don't like it), and offers the\nwindow's statusline as an alternative.\n\n- BUG: The checks for g:calendar_action and g:calendar_sign should also check\nfor an existing, but empty variable. Otherwise, it is not possible to disable it\nin a .vimrc, because the sourcing of calendar.vim would initialize the variables.\n\n- BUG: In s:CalendarDoAction(), the check for g:calendar_action must come after\nthe \"navi\" handling; otherwise \"navi\" breaks if g:calendar_action is disabled\n(see above).\n\n- ENH: The :set wrapscan is ugly, because it is a global setting. The search()\ncommands already pass the 'w' flag, so the only remaining issue were the\nsearches via \/. I modified the 'G0\/...' search to 'G$?' (i.e. backward from end\nof buffer), so that 'wrapscan' isn't required any more. (Even better would be to\nuse search() for these jumps, too.) With this, I can also completely get rid of\nthe autocmds in case one does not want the date\/time in the title, neither (see\nabove).\n\n- Using :setlocal buftype=nofile instead of =nowrite; this is more suitable for\nthis kind of scratch buffer, and avoids that the path may be shown in the title\n\/ statusline (depending on the customization).\n\n- BUG: Replaced :setlocal nowrap with 'wrap'. Without this, the 'sidescrolloff'\nsetting may cause the left side of the calendar to disappear if the last\ninserted element is near the right window border. 'wrap' shouldn't matter,\nanyway, and 'sidescrolloff' is a global setting, unfortunately.\nTry :set sidescrolloff=3 in combination with :let g:calendar_navi = 'bottom' to\nreproduce.\n\n- BUG: The :normal i... for the navi rendering causes a trailing space after the\n\"Next>\" button. This way, I cannot quickly type \"G$<CR>\" to activate the next\nbutton. Now using :normal a... to append. This causes the entire navi to shift\none character to the right, but you could fix this by decreasing the column\ncounter.\n\n- ENH: Use :stopinsert in case we've gotten here from insert mode (via\n<C-O>:Calendar<CR>)...\n\n- Using :wincmd w instead of :normal <C-w>; it's simpler. (And you should always\nuse :normal! (with a bang) to avoid interference with user remappings!)\n\n- ENH: I noticed that <left> and <s-left> do the same thing, but in different\nways (one uses the navi and the latter is called by the former). I dropped the\nunintuitive shift mappings and instead do the jumps consistently in the navi,\nusing the b:Calendar... variables instead of that ugly maparg() stuff.\n\n- ENH: I noticed that <left> and <up> do the same thing. I changed <up>\/<down>\nto move an entire year, so one can quickly let the years pass...\n\n- ENH: the 'q' mapping now returns to the previous window, not the first one.\n","package":"calendar.vim","4":"calendar.vim","src_id":"11795","5":"11795","creation_date":"1259070460","6":"1259070460"},{"0":"52","vim_version":"6.0","1":"6.0","script_version":"1.9","2":"1.9","version_comment":"This is an upgrade for calendar.vim. use nnoremap.\n","3":"This is an upgrade for calendar.vim. use nnoremap.\n","package":"calendar.vim","4":"calendar.vim","src_id":"11771","5":"11771","creation_date":"1258729981","6":"1258729981"},{"0":"52","vim_version":"6.0","1":"6.0","script_version":"1.8","2":"1.8","version_comment":"This is an upgrade for calendar.vim. fixed E382 while closing diary.\n","3":"This is an upgrade for calendar.vim. fixed E382 while closing diary.\n","package":"calendar.vim","4":"calendar.vim","src_id":"11496","5":"11496","creation_date":"1255007904","6":"1255007904"},{"0":"52","vim_version":"6.0","1":"6.0","script_version":"1.7","2":"1.7","version_comment":"This is a fixed version of calendar.vim. fixed problem of week number on 03\/01\/2008.","3":"This is a fixed version of calendar.vim. fixed problem of week number on 03\/01\/2008.","package":"calendar.vim","4":"calendar.vim","src_id":"8279","5":"8279","creation_date":"1203039142","6":"1203039142"},{"0":"52","vim_version":"6.0","1":"6.0","script_version":"1.6","2":"1.6","version_comment":"Added new actions 'calendar_begin' and 'calenader_end'.","3":"Added new actions 'calendar_begin' and 'calenader_end'.","package":"calendar.vim","4":"calendar.vim","src_id":"7409","5":"7409","creation_date":"1185303755","6":"1185303755"},{"0":"52","vim_version":"6.0","1":"6.0","script_version":"1.5","2":"1.5","version_comment":"This is an upgrade for calendar.vim. this include some bug fix.","3":"This is an upgrade for calendar.vim. this include some bug fix.","package":"calendar.vim","4":"calendar.vim","src_id":"7047","5":"7047","creation_date":"1178055275","6":"1178055275"},{"0":"52","vim_version":"6.0","1":"6.0","script_version":"1.4a","2":"1.4a","version_comment":"This is an upgrade for calendar.vim. this include some bug fix and calendar_today action.\r\n","3":"This is an upgrade for calendar.vim. this include some bug fix and calendar_today action.\r\n","package":"calendar.vim","4":"calendar.vim","src_id":"4984","5":"4984","creation_date":"1137449393","6":"1137449393"},{"0":"52","vim_version":"6.0","1":"6.0","script_version":"1.4","2":"1.4","version_comment":"This is an upgrade for Calendar.vim. this include 2 bug fixs and 1 improvement.","3":"This is an upgrade for Calendar.vim. this include 2 bug fixs and 1 improvement.","package":"calendar.vim","4":"calendar.vim","src_id":"3599","5":"3599","creation_date":"1099500066","6":"1099500066"}]},"51":{"script_id":"51","0":"51","script_name":"cscope_macros.vim","1":"cscope_macros.vim","script_type":"utility","2":"utility","summary":"basic cscope settings and key mappings","3":"basic cscope settings and key mappings","description":"This script implements the recommended settings for vim's cscope interface, and also provides a set of key mappings I've found useful.  If you don't know what cscope is, go to http:\/\/cscope.sourceforge.net and check it out--it's more powerful than ctags, though it works with fewer languages (primarily C\/C++\/Java).\r\n\r\nThe script takes care of automatically loading any cscope database you have in the current directory, or that you have set the $CSCOPE_DB environment variable to point to.  It also tells vim to allow cscope to share the CTRL-]  (goto tag) command with ctags.  Finally, it creates a set of keyboard maps (all starting with CTRL-spacebar) that perform the various types of cscope search, and which can either display cscope's results in a new vim window or in the current window.\r\n\r\n--------------------------------------------------\r\nA quick vim\/cscope tutorial:\r\n--------------------------------------------------\r\n\r\n0) Get and install cscope if you don't have it already on your machine.\r\n\r\n1) Install this plugin (see instructions below).\r\n\r\n2) Go into a directory with some C code in it, and enter 'cscope -r'.  Check out the native cscope interface program (which will call vim to edit files if you set your EDITOR variable to 'vim').  The native cscope interface is very nice, but has the problem that you need to exit vim each time you want to do a new search.   Hit CTRL-D to exit cscope.\r\n\r\n3) Start up vim.  If you want, you can start it with a C symbol (ex: 'vim -t  main'), and you should hop right to the definition of that symbol in your code.\r\n\r\n4) Put the cursor over a C symbol that is used in several places in your program.  Type \"CTRL-spacebar s\" in quick succession, and you should see a menu showing you all the uses of the symbol in the program.  Select one of them and hit enter, and you'll jump to that use.  As with ctags, you can hit CTRL-T to jump back to your original location before the search (and you can nest searches and CTRL-T will unwind them one at a time).\r\n\r\n5) Try the same search, but this time via \"CTRL-spacebar h s\".  This time, the window will split in two horizontally, and the cscope search result will be put in the new window. [If you have trouble hitting the keys fast enough for this to work, go into the cscope_macro.vim script and change vim's timeout settings as described in the comments.]  \r\n\r\n6) Try splitting the window vertically, by using 'v' instead of 'h' in the above search.\r\n\r\n7) Explore some of the other cscope search types, like 'find file' and 'find functions that call the function under the cursor'.  These are all described in the comments in cscope_macros.vim.\r\n\r\n8) Try using cscope with another language, like Java or C++.  The best way to do this is by doing \"ls *.java > cscope.files\"  (or \"find -name '*.java' > cscope.files\" if you've got a directory tree of Java files), then running cscope.\r\n\r\n9) Try setting the $CSCOPE_DB environment variable to point to a cscope database you create, so you won't need to lauch vim in the same directory as the database. This is particularly useful for projects where code is split into multiple subdirectories.  (Note: for this to work, you should build the database with absolute pathnames: cd to \/, and do \"find \/my\/fancy\/project -name '*.c' -o -name '*.h' > \/my\/cscope.files\", then run cscope in the same directory as the cscope.files file, then set and export the $CSCOPE_DB variable, pointing it to the cscope.out file that results).\r\n\r\n10) Use \":help cscope\" within vim, and\/or \"man cscope\" from your shell to answer any questions you have.  I.e., RTFM.","4":"This script implements the recommended settings for vim's cscope interface, and also provides a set of key mappings I've found useful.  If you don't know what cscope is, go to http:\/\/cscope.sourceforge.net and check it out--it's more powerful than ctags, though it works with fewer languages (primarily C\/C++\/Java).\r\n\r\nThe script takes care of automatically loading any cscope database you have in the current directory, or that you have set the $CSCOPE_DB environment variable to point to.  It also tells vim to allow cscope to share the CTRL-]  (goto tag) command with ctags.  Finally, it creates a set of keyboard maps (all starting with CTRL-spacebar) that perform the various types of cscope search, and which can either display cscope's results in a new vim window or in the current window.\r\n\r\n--------------------------------------------------\r\nA quick vim\/cscope tutorial:\r\n--------------------------------------------------\r\n\r\n0) Get and install cscope if you don't have it already on your machine.\r\n\r\n1) Install this plugin (see instructions below).\r\n\r\n2) Go into a directory with some C code in it, and enter 'cscope -r'.  Check out the native cscope interface program (which will call vim to edit files if you set your EDITOR variable to 'vim').  The native cscope interface is very nice, but has the problem that you need to exit vim each time you want to do a new search.   Hit CTRL-D to exit cscope.\r\n\r\n3) Start up vim.  If you want, you can start it with a C symbol (ex: 'vim -t  main'), and you should hop right to the definition of that symbol in your code.\r\n\r\n4) Put the cursor over a C symbol that is used in several places in your program.  Type \"CTRL-spacebar s\" in quick succession, and you should see a menu showing you all the uses of the symbol in the program.  Select one of them and hit enter, and you'll jump to that use.  As with ctags, you can hit CTRL-T to jump back to your original location before the search (and you can nest searches and CTRL-T will unwind them one at a time).\r\n\r\n5) Try the same search, but this time via \"CTRL-spacebar h s\".  This time, the window will split in two horizontally, and the cscope search result will be put in the new window. [If you have trouble hitting the keys fast enough for this to work, go into the cscope_macro.vim script and change vim's timeout settings as described in the comments.]  \r\n\r\n6) Try splitting the window vertically, by using 'v' instead of 'h' in the above search.\r\n\r\n7) Explore some of the other cscope search types, like 'find file' and 'find functions that call the function under the cursor'.  These are all described in the comments in cscope_macros.vim.\r\n\r\n8) Try using cscope with another language, like Java or C++.  The best way to do this is by doing \"ls *.java > cscope.files\"  (or \"find -name '*.java' > cscope.files\" if you've got a directory tree of Java files), then running cscope.\r\n\r\n9) Try setting the $CSCOPE_DB environment variable to point to a cscope database you create, so you won't need to lauch vim in the same directory as the database. This is particularly useful for projects where code is split into multiple subdirectories.  (Note: for this to work, you should build the database with absolute pathnames: cd to \/, and do \"find \/my\/fancy\/project -name '*.c' -o -name '*.h' > \/my\/cscope.files\", then run cscope in the same directory as the cscope.files file, then set and export the $CSCOPE_DB variable, pointing it to the cscope.out file that results).\r\n\r\n10) Use \":help cscope\" within vim, and\/or \"man cscope\" from your shell to answer any questions you have.  I.e., RTFM.","install_details":"vim 6:     Stick this file in your ~\/.vim\/plugin directory (or in a\r\n              'plugin' directory in some other directory that is in your\r\n              'runtimepath'.\r\n\r\nvim 5:     Stick this file somewhere and call 'source cscope_macros.vim' from\r\n              your ~\/.vimrc file (or cut and paste cscope_macros.vim into your .vimrc).\r\n","5":"vim 6:     Stick this file in your ~\/.vim\/plugin directory (or in a\r\n              'plugin' directory in some other directory that is in your\r\n              'runtimepath'.\r\n\r\nvim 5:     Stick this file somewhere and call 'source cscope_macros.vim' from\r\n              your ~\/.vimrc file (or cut and paste cscope_macros.vim into your .vimrc).\r\n","first_name":"Jason","6":"Jason","last_name":"Duell","7":"Duell","releases":[{"0":"51","vim_version":"6.0","1":"6.0","script_version":"2.0.0","2":"2.0.0","version_comment":"Hmm, backslashes don't seem to show up when I type them on the upload form.  What I meant to write in that last post was that the new default mapping for regular cscope searches is 'CTRL-\\\\'  (Control-backslash).","3":"Hmm, backslashes don't seem to show up when I type them on the upload form.  What I meant to write in that last post was that the new default mapping for regular cscope searches is 'CTRL-\\\\'  (Control-backslash).","package":"cscope_macros.vim","4":"cscope_macros.vim","src_id":"171","5":"171","creation_date":"1000507924","6":"1000507924"},{"0":"51","vim_version":"6.0","1":"6.0","script_version":"2.0","2":"2.0","version_comment":"I've changed the default mappings in the script, to avoid 3-key maps.  Now it uses 'CTRL-\\' to do basic (no window split) cscope searches, 'CTRL-spacebar' to do searches that display results in a new, horizontally split window, and 'CTRL-spacebar CTRL-spacebar' to do searches with a vertical split.  I've also trimmed my overly verbose comments in the file.\r\n\r\nSince I can't update the description text on this site, I'm going to be keeping the latest tutorial on vim-cscope usage at http:\/\/cscope.sourceforge.net from now on.  I'll be posting a new version of the tutorial there soon.","3":"I've changed the default mappings in the script, to avoid 3-key maps.  Now it uses 'CTRL-\\' to do basic (no window split) cscope searches, 'CTRL-spacebar' to do searches that display results in a new, horizontally split window, and 'CTRL-spacebar CTRL-spacebar' to do searches with a vertical split.  I've also trimmed my overly verbose comments in the file.\r\n\r\nSince I can't update the description text on this site, I'm going to be keeping the latest tutorial on vim-cscope usage at http:\/\/cscope.sourceforge.net from now on.  I'll be posting a new version of the tutorial there soon.","package":"cscope_macros.vim","4":"cscope_macros.vim","src_id":"170","5":"170","creation_date":"1000507765","6":"1000507765"},{"0":"51","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"cscope_macros.vim","4":"cscope_macros.vim","src_id":"73","5":"73","creation_date":"996529713","6":"996529713"}]},"50":{"script_id":"50","0":"50","script_name":"lh-brackets","1":"lh-brackets","script_type":"utility","2":"utility","summary":"Bracketing system + Tools for programming mappings","3":"Bracketing system + Tools for programming mappings","description":"The latest version of this plugin is maintained at https:\/\/github.com\/LucHermitte\/lh-brackets\r\n\r\n\r\nHere is an archive containing different functions and commands aimed at (ft)plugins\r\ndeveloppers.\r\n\r\nYou fill find :\r\n- functions to define context dependent mappings : i.e. mappings that won't expand\r\n  within comment or string context -> MapNoContext() & MapNoContext2()\r\n- a function that insert a pair of tokens around a visual area -> MapAroundVisualLine()\r\n- a function that expands mappings contained into strings -> BuildMapSeq()\r\n- commands that eats the <spaces> you hit at the end of abbreviations\r\n\r\n- a set of definitions to insert markers and jump to them (derived from Stephen \r\n  Riehm bracketing system) ; the markers can be customized, erased or deleted, \r\n  etc.\r\n\r\n- my bracketing system : through a set of buffer-relative options, we can activate \r\n  (and tune) the insertion of pairs of brackets when we hit the opening bracket. It \r\n  works in insert, normal and visual modes. If markers are available and wanted, \r\n  they will be inserted in insert-mode.\r\n  It also proposes functions (from auctex.vim) that delete pairs of brackets, \r\n  change them (to '{}', '()', or '[]'), toogle backslashes, etc.\r\n\r\nYou fill found a much more complete documentation and examples within the archive, and there:\r\nhttps:\/\/github.com\/LucHermitte\/lh-brackets","4":"The latest version of this plugin is maintained at https:\/\/github.com\/LucHermitte\/lh-brackets\r\n\r\n\r\nHere is an archive containing different functions and commands aimed at (ft)plugins\r\ndeveloppers.\r\n\r\nYou fill find :\r\n- functions to define context dependent mappings : i.e. mappings that won't expand\r\n  within comment or string context -> MapNoContext() & MapNoContext2()\r\n- a function that insert a pair of tokens around a visual area -> MapAroundVisualLine()\r\n- a function that expands mappings contained into strings -> BuildMapSeq()\r\n- commands that eats the <spaces> you hit at the end of abbreviations\r\n\r\n- a set of definitions to insert markers and jump to them (derived from Stephen \r\n  Riehm bracketing system) ; the markers can be customized, erased or deleted, \r\n  etc.\r\n\r\n- my bracketing system : through a set of buffer-relative options, we can activate \r\n  (and tune) the insertion of pairs of brackets when we hit the opening bracket. It \r\n  works in insert, normal and visual modes. If markers are available and wanted, \r\n  they will be inserted in insert-mode.\r\n  It also proposes functions (from auctex.vim) that delete pairs of brackets, \r\n  change them (to '{}', '()', or '[]'), toogle backslashes, etc.\r\n\r\nYou fill found a much more complete documentation and examples within the archive, and there:\r\nhttps:\/\/github.com\/LucHermitte\/lh-brackets","install_details":"The easiest way to install this plugin, is to install lh-brackets thanks vim-addon-manager (as VAM hadles dependencies).\r\n\r\nCheck https:\/\/github.com\/LucHermitte\/lh-brackets otherwise.","5":"The easiest way to install this plugin, is to install lh-brackets thanks vim-addon-manager (as VAM hadles dependencies).\r\n\r\nCheck https:\/\/github.com\/LucHermitte\/lh-brackets otherwise.","first_name":"Luc","6":"Luc","last_name":"Hermitte","7":"Hermitte","releases":[{"0":"50","vim_version":"6.0","1":"6.0","script_version":"0.6.1","2":"0.6.1","version_comment":"A lot of changes and improvments have been made since the last release 6 years ago: folding friendly, doesn't mess with history and registers, utf-8 friendly, new mapping to replace a placeholder with its contents, options to select (or not) the current marker on a jump ; Surround() recognizes placeholders from other selections, support for angle brackets ; new context sensitive text inserters ; etc.","3":"A lot of changes and improvments have been made since the last release 6 years ago: folding friendly, doesn't mess with history and registers, utf-8 friendly, new mapping to replace a placeholder with its contents, options to select (or not) the current marker on a jump ; Surround() recognizes placeholders from other selections, support for angle brackets ; new context sensitive text inserters ; etc.","package":"lh-map-tools-0.6.1.vba","4":"lh-map-tools-0.6.1.vba","src_id":"8321","5":"8321","creation_date":"1203611973","6":"1203611973"},{"0":"50","vim_version":"6.0","1":"6.0","script_version":"2002-11-08","2":"2002-11-08","version_comment":"(*) Misc_maps: Some minor problems fixed. \r\n(*) Markers: Names of options and functions changed ; Closing markers can be of any length ; Possibility to jump backward and forward from markers to markers + the associated commands.\r\n(*) Mappings can be customized outside the plugins.\r\n(*) Doc updated","3":"(*) Misc_maps: Some minor problems fixed. \r\n(*) Markers: Names of options and functions changed ; Closing markers can be of any length ; Possibility to jump backward and forward from markers to markers + the associated commands.\r\n(*) Mappings can be customized outside the plugins.\r\n(*) Doc updated","package":"lh-map-tools.tar.gz","4":"lh-map-tools.tar.gz","src_id":"1386","5":"1386","creation_date":"1036726317","6":"1036726317"},{"0":"50","vim_version":"6.0","1":"6.0","script_version":"2002-04-04","2":"2002-04-04","version_comment":"Bugs fixed, plus other functions and a bracketing system.","3":"Bugs fixed, plus other functions and a bracketing system.","package":"lh-map-tools.tar.gz","4":"lh-map-tools.tar.gz","src_id":"756","5":"756","creation_date":"1017907176","6":"1017907176"}]},"49":{"script_id":"49","0":"49","script_name":"Mail_cc.set","1":"Mail_cc.set","script_type":"utility","2":"utility","summary":"Function that deletes one's e-mail address from the Cc: list","3":"Function that deletes one's e-mail address from the Cc: list","description":"Bothered of receiving a copy of all your messages when you reply to a group of people ? Well, this file is for you ! \r\n\r\nIn order to use it, source this file or delete its last line and call DelFromCC() by yourself.\r\n\r\nIt works fine with MUTT and ELM ; I haven't test any other MUA. MUTT defines the option metoo that should handle this... I've never successed to make it work properly :-((","4":"Bothered of receiving a copy of all your messages when you reply to a group of people ? Well, this file is for you ! \r\n\r\nIn order to use it, source this file or delete its last line and call DelFromCC() by yourself.\r\n\r\nIt works fine with MUTT and ELM ; I haven't test any other MUA. MUTT defines the option metoo that should handle this... I've never successed to make it work properly :-((","install_details":"Once again, copy the file to wherever you are inspired and source it from your e-mail plugins.\r\n\r\nAll you have to do is to change my e-mail address to yours. This have to be done within the variables 'user' and 'domain'.\r\n","5":"Once again, copy the file to wherever you are inspired and source it from your e-mail plugins.\r\n\r\nAll you have to do is to change my e-mail address to yours. This have to be done within the variables 'user' and 'domain'.\r\n","first_name":"Luc","6":"Luc","last_name":"Hermitte","7":"Hermitte","releases":[{"0":"49","vim_version":"5.7","1":"5.7","script_version":"1.3","2":"1.3","version_comment":"Initial upload","3":"Initial upload","package":"Mail_cc.set","4":"Mail_cc.set","src_id":"69","5":"69","creation_date":"996311054","6":"996311054"}]},"48":{"script_id":"48","0":"48","script_name":"Triggers.vim","1":"Triggers.vim","script_type":"utility","2":"utility","summary":"Helps to toggle definitions (maps, sets, abbr)","3":"Helps to toggle definitions (maps, sets, abbr)","description":"This script defines functions that help to toggle the definitions of many things -- like mappings, settings \r\nor abbreviations. The very simple application is to map (\/ unmap) a macro when we hit (\/rehit) the trigger. \r\nA much more useful application is to map all the definitions from a function when hitting the trigger and \r\nunload them on a second hit and reload on a third, etc..\r\n\r\nFor examples of use, cf. the header part of the file, or  <http:\/\/hermitte.free.fr\/vim\/general.php >.\r\n","4":"This script defines functions that help to toggle the definitions of many things -- like mappings, settings \r\nor abbreviations. The very simple application is to map (\/ unmap) a macro when we hit (\/rehit) the trigger. \r\nA much more useful application is to map all the definitions from a function when hitting the trigger and \r\nunload them on a second hit and reload on a third, etc..\r\n\r\nFor examples of use, cf. the header part of the file, or  <http:\/\/hermitte.free.fr\/vim\/general.php >.\r\n","install_details":"Copy the file into {rtp}\/plugin, and prefer the latest version from: https:\/\/github.com\/LucHermitte\/lh-misc\/blob\/master\/plugin\/Triggers.vim\r\n\r\nIt can also be installed with lh-misc. ","5":"Copy the file into {rtp}\/plugin, and prefer the latest version from: https:\/\/github.com\/LucHermitte\/lh-misc\/blob\/master\/plugin\/Triggers.vim\r\n\r\nIt can also be installed with lh-misc. ","first_name":"Luc","6":"Luc","last_name":"Hermitte","7":"Hermitte","releases":[{"0":"48","vim_version":"5.7","1":"5.7","script_version":"1.05","2":"1.05","version_comment":"The placement of the memorized undo files has changed to suit VIM6\r\nsystems, and older ones where we can't write files into $VIMRUNTIME.\r\nThe creation of the undo files is smoother ; vim should not insult us\r\nanymore.","3":"The placement of the memorized undo files has changed to suit VIM6\r\nsystems, and older ones where we can't write files into $VIMRUNTIME.\r\nThe creation of the undo files is smoother ; vim should not insult us\r\nanymore.","package":"trigger.tar.gz","4":"trigger.tar.gz","src_id":"1007","5":"1007","creation_date":"1026286407","6":"1026286407"},{"0":"48","vim_version":"5.7","1":"5.7","script_version":"1.04","2":"1.04","version_comment":"Bufferized maps and abbreviations (<buffer> for VIM6) are now valid and correctly handled.\r\nAnd the two files required are now part of the archive.","3":"Bufferized maps and abbreviations (<buffer> for VIM6) are now valid and correctly handled.\r\nAnd the two files required are now part of the archive.","package":"triggers.tar.gz","4":"triggers.tar.gz","src_id":"582","5":"582","creation_date":"1013596666","6":"1013596666"},{"0":"48","vim_version":"5.7","1":"5.7","script_version":"1.03","2":"1.03","version_comment":"Fix a little synchronisation problem between files thanks to an external script attached to the tarball archive.","3":"Fix a little synchronisation problem between files thanks to an external script attached to the tarball archive.","package":"Triggers.vim","4":"Triggers.vim","src_id":"215","5":"215","creation_date":"1001940044","6":"1001940044"},{"0":"48","vim_version":"5.7","1":"5.7","script_version":"1.02","2":"1.02","version_comment":"Initial upload","3":"Initial upload","package":"Triggers.vim","4":"Triggers.vim","src_id":"67","5":"67","creation_date":"996223322","6":"996223322"}]},"47":{"script_id":"47","0":"47","script_name":"Mail_Re.set","1":"Mail_Re.set","script_type":"utility","2":"utility","summary":"Merge the all the \"Re: Re:\" in e-mail subjects in only one.","3":"Merge the all the \"Re: Re:\" in e-mail subjects in only one.","description":"May be, you have allready noticed and used the two macros : ,re that merges all the \"[Rr][Ee]:\" in the subject in only one \"Re:\" and ,Re that merges \"[Rr][Re]: Re[n]\" in \"Re[n+1]\". \r\nThis file combines the features from both macros without any visual bell or incremention of the first number in the subject. \r\n","4":"May be, you have allready noticed and used the two macros : ,re that merges all the \"[Rr][Ee]:\" in the subject in only one \"Re:\" and ,Re that merges \"[Rr][Re]: Re[n]\" in \"Re[n+1]\". \r\nThis file combines the features from both macros without any visual bell or incremention of the first number in the subject. \r\n","install_details":"Copy the file anywhere you want. Source it from your e-mail pluggins file and then call the function Mail_Re() or map it to anything you want.","5":"Copy the file anywhere you want. Source it from your e-mail pluggins file and then call the function Mail_Re() or map it to anything you want.","first_name":"Luc","6":"Luc","last_name":"Hermitte","7":"Hermitte","releases":[{"0":"47","vim_version":"5.7","1":"5.7","script_version":"1.2","2":"1.2","version_comment":"Comments translated to English","3":"Comments translated to English","package":"Mail_Re.set","4":"Mail_Re.set","src_id":"68","5":"68","creation_date":"996309820","6":"996309820"},{"0":"47","vim_version":"5.7","1":"5.7","script_version":"1.1","2":"1.1","version_comment":"Initial upload","3":"Initial upload","package":"Mail_Re.set","4":"Mail_Re.set","src_id":"66","5":"66","creation_date":"996222797","6":"996222797"}]},"46":{"script_id":"46","0":"46","script_name":"Mail_mutt_alias.set","1":"Mail_mutt_alias.set","script_type":"utility","2":"utility","summary":"Extract an e-mail address from the mutt aliases file.","3":"Extract an e-mail address from the mutt aliases file.","description":"This script permit to insert an alias from the mutt aliases file while editing an\r\ne-mail within vim.\r\n\r\nSince the version 2.0, we can hit <tab> (in INSERT-mode) within an address \r\nfield (To:, Cc:, Bcc:, Reply-To) to expand an alias. \r\nIf several contacts match the to-be-expanded pattern, a menu is proposed in a \r\nsplitted window in order to choose the addresses. \r\n\r\nDependencies :\r\nv2.x+ : a.vim                http:\/\/vim.sourceforge.net\/scripts\/script.php?script_id=31\r\n          Actually, you should download an old version of a.vim that still exports its functions\r\n\r\nv2.2+ : words_tools.vim http:\/\/vim.sourceforge.net\/scripts\/script.php?script_id=143\r\n\r\n\r\nN.B.: The command (:Ca) and the macro (,Ca) have been abandonned since version 2.3.","4":"This script permit to insert an alias from the mutt aliases file while editing an\r\ne-mail within vim.\r\n\r\nSince the version 2.0, we can hit <tab> (in INSERT-mode) within an address \r\nfield (To:, Cc:, Bcc:, Reply-To) to expand an alias. \r\nIf several contacts match the to-be-expanded pattern, a menu is proposed in a \r\nsplitted window in order to choose the addresses. \r\n\r\nDependencies :\r\nv2.x+ : a.vim                http:\/\/vim.sourceforge.net\/scripts\/script.php?script_id=31\r\n          Actually, you should download an old version of a.vim that still exports its functions\r\n\r\nv2.2+ : words_tools.vim http:\/\/vim.sourceforge.net\/scripts\/script.php?script_id=143\r\n\r\n\r\nN.B.: The command (:Ca) and the macro (,Ca) have been abandonned since version 2.3.","install_details":"Update the path to your mutt aliases file, and put the file anywhere you want -- N.B.: $$\/ftplugin\/mail\/ is certainly the best place you could find.","5":"Update the path to your mutt aliases file, and put the file anywhere you want -- N.B.: $$\/ftplugin\/mail\/ is certainly the best place you could find.","first_name":"Luc","6":"Luc","last_name":"Hermitte","7":"Hermitte","releases":[{"0":"46","vim_version":"6.0","1":"6.0","script_version":"2.3","2":"2.3","version_comment":"Some minor enhancements and several bugs fixed.","3":"Some minor enhancements and several bugs fixed.","package":"Mail_mutt_alias_set.vim","4":"Mail_mutt_alias_set.vim","src_id":"968","5":"968","creation_date":"1025503032","6":"1025503032"},{"0":"46","vim_version":"5.7","1":"5.7","script_version":"2.2","2":"2.2","version_comment":"Many bugs have been corrected, now the script runs under VIM 5.6-Solaris. A tagging feature has been added in order to select several e-mail addresses in the list. And <tab> can now expand aliases\/names expressed as regular expressions.","3":"Many bugs have been corrected, now the script runs under VIM 5.6-Solaris. A tagging feature has been added in order to select several e-mail addresses in the list. And <tab> can now expand aliases\/names expressed as regular expressions.","package":"Mail_mutt_alias.set","4":"Mail_mutt_alias.set","src_id":"345","5":"345","creation_date":"1005642604","6":"1005642604"},{"0":"46","vim_version":"5.7","1":"5.7","script_version":"2.1","2":"2.1","version_comment":"Correction of some regexps + definition of a syntax highlighting scheme for the menu.","3":"Correction of some regexps + definition of a syntax highlighting scheme for the menu.","package":"Mail_mutt_alias.set","4":"Mail_mutt_alias.set","src_id":"219","5":"219","creation_date":"1001977016","6":"1001977016"},{"0":"46","vim_version":"5.7","1":"5.7","script_version":"2.0","2":"2.0","version_comment":"Fix some problems when several aliases match a pattern through a menu to choose from.\r\nMap tabulation as an expand character for aliases ; only within the address lines of e-messages headers.","3":"Fix some problems when several aliases match a pattern through a menu to choose from.\r\nMap tabulation as an expand character for aliases ; only within the address lines of e-messages headers.","package":"Mail_mutt_alias.set","4":"Mail_mutt_alias.set","src_id":"214","5":"214","creation_date":"1001939833","6":"1001939833"},{"0":"46","vim_version":"5.7","1":"5.7","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"Mail_mutt_alias.set","4":"Mail_mutt_alias.set","src_id":"65","5":"65","creation_date":"996222308","6":"996222308"}]},"45":{"script_id":"45","0":"45","script_name":"Mail_Sig.set","1":"Mail_Sig.set","script_type":"utility","2":"utility","summary":"Erase signatures at the end of your replies","3":"Erase signatures at the end of your replies","description":"This file defines an alternative to the macro :\r\n\r\n                          map ,kqs G?^> *-- $dG \r\n\r\n\r\nIt comes as a command. This time, VIM won't complains about not found ^> *-- $ pattern. BTW, It also deletes all the empty lines (quoted or not) just above the signature to delete.\r\n\r\nOlder versions (for VIM 5.7) of the file define the function Erase_Sig(). \r\nThe latest version (for VIM 6.x) defines the command :EraseSignature. \r\n\r\nIt can also delete up to two signatures -- some mailing lists add another dashes-delimited\r\nsignature. And it keeps our signature that may be automatically inserted by some MUAs \r\nlike Mutt.\r\n\r\n\r\nSince v1.4: the operator-pending mode mapping '--' is defined. Hitting d--, c-- or y--\r\nwill delete, change or yank lines until our own signature (if present) or the end of the file.\r\n","4":"This file defines an alternative to the macro :\r\n\r\n                          map ,kqs G?^> *-- $dG \r\n\r\n\r\nIt comes as a command. This time, VIM won't complains about not found ^> *-- $ pattern. BTW, It also deletes all the empty lines (quoted or not) just above the signature to delete.\r\n\r\nOlder versions (for VIM 5.7) of the file define the function Erase_Sig(). \r\nThe latest version (for VIM 6.x) defines the command :EraseSignature. \r\n\r\nIt can also delete up to two signatures -- some mailing lists add another dashes-delimited\r\nsignature. And it keeps our signature that may be automatically inserted by some MUAs \r\nlike Mutt.\r\n\r\n\r\nSince v1.4: the operator-pending mode mapping '--' is defined. Hitting d--, c-- or y--\r\nwill delete, change or yank lines until our own signature (if present) or the end of the file.\r\n","install_details":"Drop the file wherever you want ; {rtp}\/ftplugin\/mail beeing, IMO, the best place. \r\n\r\nAnd uncomment the call to the command at the end of the file if you don't want the \r\noperation to be automatic ; you may want define a mapping (like ,kqs for instance) \r\nthat will invoke :EraseSignature.\r\n","5":"Drop the file wherever you want ; {rtp}\/ftplugin\/mail beeing, IMO, the best place. \r\n\r\nAnd uncomment the call to the command at the end of the file if you don't want the \r\noperation to be automatic ; you may want define a mapping (like ,kqs for instance) \r\nthat will invoke :EraseSignature.\r\n","first_name":"Luc","6":"Luc","last_name":"Hermitte","7":"Hermitte","releases":[{"0":"45","vim_version":"6.0","1":"6.0","script_version":"1.4","2":"1.4","version_comment":"New operator-pending mode mapping : --. It matches lines until our own signature or the end of the file.","3":"New operator-pending mode mapping : --. It matches lines until our own signature or the end of the file.","package":"Mail_Sig_set.vim","4":"Mail_Sig_set.vim","src_id":"982","5":"982","creation_date":"1025666180","6":"1025666180"},{"0":"45","vim_version":"6.0","1":"6.0","script_version":"1.3","2":"1.3","version_comment":"Now, the script can erase up to two previous signatures (inserted by some mailing lists), and more important, it doesn't delete our signature when automatically inserted by the MUA. ","3":"Now, the script can erase up to two previous signatures (inserted by some mailing lists), and more important, it doesn't delete our signature when automatically inserted by the MUA. ","package":"Mail_Sig_set.vim","4":"Mail_Sig_set.vim","src_id":"969","5":"969","creation_date":"1025504547","6":"1025504547"},{"0":"45","vim_version":"5.7","1":"5.7","script_version":"1.2","2":"1.2","version_comment":"Initial upload","3":"Initial upload","package":"Mail_Sig.set","4":"Mail_Sig.set","src_id":"64","5":"64","creation_date":"996222192","6":"996222192"}]},"44":{"script_id":"44","0":"44","script_name":"completeWord.py","1":"completeWord.py","script_type":"utility","2":"utility","summary":"Complete word from Python src files.","3":"Complete word from Python src files.","description":"Completes the word under the cursor by scanning the current file and any imported Python modules that have source available.","4":"Completes the word under the cursor by scanning the current file and any imported Python modules that have source available.","install_details":"Requires Vim to be compiled with the Python interpreter.  Change the mapping at the bottom of the file and 'pyfile completeWord.py'","5":"Requires Vim to be compiled with the Python interpreter.  Change the mapping at the bottom of the file and 'pyfile completeWord.py'","first_name":"Kevin","6":"Kevin","last_name":"Dahlhausen","7":"Dahlhausen","releases":[{"0":"44","vim_version":"5.7","1":"5.7","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"completeWord.py","4":"completeWord.py","src_id":"63","5":"63","creation_date":"996180221","6":"996180221"}]},"43":{"script_id":"43","0":"43","script_name":"sccs-menu.vim","1":"sccs-menu.vim","script_type":"utility","2":"utility","summary":"Adds a SCCS menu in GVim to acces SCCS functions.","3":"Adds a SCCS menu in GVim to acces SCCS functions.","description":"Script to access most commonly used SCCS functions thr' vim. Allows to get the latest version, any required version of a file. You can check in\/out the file, add the file in sccs, unedit the file, revert back the changes made. You can view diff of any 2 versions of the file, see the change log etc.","4":"Script to access most commonly used SCCS functions thr' vim. Allows to get the latest version, any required version of a file. You can check in\/out the file, add the file in sccs, unedit the file, revert back the changes made. You can view diff of any 2 versions of the file, see the change log etc.","install_details":"Put the script in the plugin directory and that's all. Make sure that the \"sccs\" executable is in the PATH.","5":"Put the script in the plugin directory and that's all. Make sure that the \"sccs\" executable is in the PATH.","first_name":"Pradeep","6":"Pradeep","last_name":"Unde","7":"Unde","releases":[{"0":"43","vim_version":"6.0","1":"6.0","script_version":"1.11","2":"1.11","version_comment":"Fixed SCCS status of files beginning with the same name.\r\nex: 'foo' and 'foo.c': Status of 'foo' was set to status of 'foo.c' if 'foo.c' was checked out (i.e. 'foo' was set to checked out).","3":"Fixed SCCS status of files beginning with the same name.\r\nex: 'foo' and 'foo.c': Status of 'foo' was set to status of 'foo.c' if 'foo.c' was checked out (i.e. 'foo' was set to checked out).","package":"sccs-menu.vim","4":"sccs-menu.vim","src_id":"1157","5":"1157","creation_date":"1029977494","6":"1029977494"},{"0":"43","vim_version":"6.0","1":"6.0","script_version":"1.10","2":"1.10","version_comment":"Now manu items are file state sensitive. That means they are enabled\/disabled according to whether the file is checked in\/out. Also added SCCS menu to the popup menu.","3":"Now manu items are file state sensitive. That means they are enabled\/disabled according to whether the file is checked in\/out. Also added SCCS menu to the popup menu.","package":"sccs-menu.vim","4":"sccs-menu.vim","src_id":"487","5":"487","creation_date":"1011269804","6":"1011269804"},{"0":"43","vim_version":"6.0","1":"6.0","script_version":"1.9","2":"1.9","version_comment":"1. Now using :t for the file name\r\n2. A small bug fix for Revert back menu item as suggested by Peter\r\n3. Added \"unedit\" menu item","3":"1. Now using :t for the file name\r\n2. A small bug fix for Revert back menu item as suggested by Peter\r\n3. Added \"unedit\" menu item","package":"sccs-menu.vim","4":"sccs-menu.vim","src_id":"477","5":"477","creation_date":"1011092755","6":"1011092755"},{"0":"43","vim_version":"6.0","1":"6.0","script_version":"1.8","2":"1.8","version_comment":"1. Now the script does not produce any temp files for diff.\r\n2. Now using \"sccs prt -y | awk\" to get the SCCS version. Thanks to Will Fiveash.\r\n3. Also added the script version in the header. (Again thanks to Will !)","3":"1. Now the script does not produce any temp files for diff.\r\n2. Now using \"sccs prt -y | awk\" to get the SCCS version. Thanks to Will Fiveash.\r\n3. Also added the script version in the header. (Again thanks to Will !)","package":"sccs-menu.vim","4":"sccs-menu.vim","src_id":"132","5":"132","creation_date":"998564650","6":"998564650"},{"0":"43","vim_version":"6.0","1":"6.0","script_version":"1.7","2":"1.7","version_comment":"Fixed SCCS quirks white getting version of a file using \"sccs what\". Hopefully now we get the right text in the status line.","3":"Fixed SCCS quirks white getting version of a file using \"sccs what\". Hopefully now we get the right text in the status line.","package":"sccs-menu.vim","4":"sccs-menu.vim","src_id":"111","5":"111","creation_date":"997945303","6":"997945303"},{"0":"43","vim_version":"6.0","1":"6.0","script_version":"1.6","2":"1.6","version_comment":"Added diff for any 2 SCCS versions of the opened file. If u diff with current version, it splits the screen vertically with the opened file to show the diff.If u diff with 2 versions that are different from opened file, it splits the screen horizontally and show vertically split diff in upper window. Added better way to get the SCCS version to show in status line. Added silent execute wherever possible.","3":"Added diff for any 2 SCCS versions of the opened file. If u diff with current version, it splits the screen vertically with the opened file to show the diff.If u diff with 2 versions that are different from opened file, it splits the screen horizontally and show vertically split diff in upper window. Added better way to get the SCCS version to show in status line. Added silent execute wherever possible.","package":"sccs-menu.vim","4":"sccs-menu.vim","src_id":"108","5":"108","creation_date":"997859806","6":"997859806"},{"0":"43","vim_version":"6.0","1":"6.0","script_version":"1.5","2":"1.5","version_comment":"Couple of fixes...\r\n1. If no file opened....SCCS status was SCCS-SCCS-. Corrected this.\r\n2. Shortcut <F6> for the sccs log did not work properly although the menu item was working properly.","3":"Couple of fixes...\r\n1. If no file opened....SCCS status was SCCS-SCCS-. Corrected this.\r\n2. Shortcut <F6> for the sccs log did not work properly although the menu item was working properly.","package":"sccs-menu.vim","4":"sccs-menu.vim","src_id":"94","5":"94","creation_date":"997427206","6":"997427206"},{"0":"43","vim_version":"6.0","1":"6.0","script_version":"1.4","2":"1.4","version_comment":"Updated the SCCSUpdateVersion function to use \"sccs prt -y\" to get the latest version of the opened file. This fixes a bug in the script. Also, this enables the script to find whether the file is there in SCCS or not. If the file in not in SCCS, now you will see \"SCCS-Not in SCCS\" entry in the statusline.","3":"Updated the SCCSUpdateVersion function to use \"sccs prt -y\" to get the latest version of the opened file. This fixes a bug in the script. Also, this enables the script to find whether the file is there in SCCS or not. If the file in not in SCCS, now you will see \"SCCS-Not in SCCS\" entry in the statusline.","package":"sccs-menu.vim","4":"sccs-menu.vim","src_id":"92","5":"92","creation_date":"997360772","6":"997360772"},{"0":"43","vim_version":"6.0","1":"6.0","script_version":"1.3","2":"1.3","version_comment":"1. Added set laststatus=2 so that the user will always have a status line ro see the SCCS status (or version).\r\n2. A small bug fix to get the SCCS version of the file.","3":"1. Added set laststatus=2 so that the user will always have a status line ro see the SCCS status (or version).\r\n2. A small bug fix to get the SCCS version of the file.","package":"sccs-menu.vim","4":"sccs-menu.vim","src_id":"90","5":"90","creation_date":"997259296","6":"997259296"},{"0":"43","vim_version":"6.0","1":"6.0","script_version":"1.2","2":"1.2","version_comment":"Added item in status line indicating the status of the file in SCCS.\r\n1. If the file is checked in in SCCS, it shows the sccs-version of the file. It shows the version in the form SCCS-(version-no)\r\n2. If the file has been checked out, it shows like SCCS-Checked out(Locked)\r\n3. If the file does not exist in SCCS, it shows empty version like SCCS-","3":"Added item in status line indicating the status of the file in SCCS.\r\n1. If the file is checked in in SCCS, it shows the sccs-version of the file. It shows the version in the form SCCS-(version-no)\r\n2. If the file has been checked out, it shows like SCCS-Checked out(Locked)\r\n3. If the file does not exist in SCCS, it shows empty version like SCCS-","package":"sccs-menu.vim","4":"sccs-menu.vim","src_id":"89","5":"89","creation_date":"997256589","6":"997256589"},{"0":"43","vim_version":"6.0","1":"6.0","script_version":"1.1","2":"1.1","version_comment":"Added (copied!) a function to load the log (or edit) history in a separate buffer so that it is convenient to read all the history in one shot.","3":"Added (copied!) a function to load the log (or edit) history in a separate buffer so that it is convenient to read all the history in one shot.","package":"sccs-menu.vim","4":"sccs-menu.vim","src_id":"81","5":"81","creation_date":"996762179","6":"996762179"},{"0":"43","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"sccs-menu.vim","4":"sccs-menu.vim","src_id":"61","5":"61","creation_date":"996057907","6":"996057907"}]},"42":{"script_id":"42","0":"42","script_name":"bufexplorer.zip","1":"bufexplorer.zip","script_type":"utility","2":"utility","summary":"Buffer Explorer \/ Browser","3":"Buffer Explorer \/ Browser","description":"With bufexplorer, you can quickly and easily switch between buffers by using the one of the default public interfaces:\r\n\r\n  '\\be' (normal open)  or\r\n  '\\bs' (force horizontal split open)  or\r\n  '\\bv' (force vertical split open)\r\n\r\nOnce the bufexplorer window is open you can use the normal movement keys (hjkl) to move around and then use <Enter> or <Left-Mouse-Click> to select the buffer you would like to open. If you would like to have the selected buffer opened in a new tab, simply press either <Shift-Enter> or 't'. Please note that when opening a buffer in a tab, that if the buffer is already in another tab, bufexplorer can switch to that tab automatically for you if you would like. More about that in the supplied VIM help.\r\n\r\nBufexplorer also offers various options including:\r\n- Display the list of buffers in various sort orders including:\r\n    - Most Recently Used (MRU) which is the default\r\n    - Buffer number\r\n    - File name\r\n    - File extension\r\n    - Full file path name\r\n- Delete buffer from list \r\n\r\nFor more about options, sort orders, configuration options, etc. please see the supplied VIM help.\r\n\r\nNOTE: I try and update this version as soon as a fix comes out... However, all version are located on GitHub https:\/\/github.com\/jlanzarotta\/bufexplorer","4":"With bufexplorer, you can quickly and easily switch between buffers by using the one of the default public interfaces:\r\n\r\n  '\\be' (normal open)  or\r\n  '\\bs' (force horizontal split open)  or\r\n  '\\bv' (force vertical split open)\r\n\r\nOnce the bufexplorer window is open you can use the normal movement keys (hjkl) to move around and then use <Enter> or <Left-Mouse-Click> to select the buffer you would like to open. If you would like to have the selected buffer opened in a new tab, simply press either <Shift-Enter> or 't'. Please note that when opening a buffer in a tab, that if the buffer is already in another tab, bufexplorer can switch to that tab automatically for you if you would like. More about that in the supplied VIM help.\r\n\r\nBufexplorer also offers various options including:\r\n- Display the list of buffers in various sort orders including:\r\n    - Most Recently Used (MRU) which is the default\r\n    - Buffer number\r\n    - File name\r\n    - File extension\r\n    - Full file path name\r\n- Delete buffer from list \r\n\r\nFor more about options, sort orders, configuration options, etc. please see the supplied VIM help.\r\n\r\nNOTE: I try and update this version as soon as a fix comes out... However, all version are located on GitHub https:\/\/github.com\/jlanzarotta\/bufexplorer","install_details":"Simply unzip bufexplorer.zip into a directory in your 'runtimepath', usually ~\/.vim or c:\\vimfiles, and restart Vim. This zip file contains plugin\\bufexplorer.vim, and doc\\bufexplorer.txt.  See ':help add-local-help' on how to add bufexplorer.txt to vim's help system.\r\n\r\nNOTE: Version 7.0.12 and above will ONLY work with 7.0 and above of Vim.\r\nNOTE NOTE NOTE: If you have a version prior to 7.1.2 that contains an autoload\\bufexplorer.vim file, please REMOVE the autoload\\bufexlorer.vim AND the plugin\\bufexplorer.vim files before installing a new version.","5":"Simply unzip bufexplorer.zip into a directory in your 'runtimepath', usually ~\/.vim or c:\\vimfiles, and restart Vim. This zip file contains plugin\\bufexplorer.vim, and doc\\bufexplorer.txt.  See ':help add-local-help' on how to add bufexplorer.txt to vim's help system.\r\n\r\nNOTE: Version 7.0.12 and above will ONLY work with 7.0 and above of Vim.\r\nNOTE NOTE NOTE: If you have a version prior to 7.1.2 that contains an autoload\\bufexplorer.vim file, please REMOVE the autoload\\bufexlorer.vim AND the plugin\\bufexplorer.vim files before installing a new version.","first_name":"jeff","6":"jeff","last_name":"lanzarotta","7":"lanzarotta","releases":[{"0":"42","vim_version":"7.4","1":"7.4","script_version":"7.4.26","2":"7.4.26","version_comment":"- Merged in changes from Bashar Harfoush that fixes a severe error where the bufexplorer buffer was not being removed from the buffer list when bufexplorer was closed.","3":"- Merged in changes from Bashar Harfoush that fixes a severe error where the bufexplorer buffer was not being removed from the buffer list when bufexplorer was closed.","package":"bufexplorer-7.4.26.zip","4":"bufexplorer-7.4.26.zip","src_id":"28441","5":"28441","creation_date":"1683029401","6":"1683029401"},{"0":"42","vim_version":"7.4","1":"7.4","script_version":"7.4.23","2":"7.4.23","version_comment":"- Merged in changes from benoit-pierre that fixes an error thrown when vim is in read-only mode.\r\n- Merged in changes from tartansandal that implements the use of an independent variable to track window splitting since s:splitMode != '' no longer implies that a split was triggered.","3":"- Merged in changes from benoit-pierre that fixes an error thrown when vim is in read-only mode.\r\n- Merged in changes from tartansandal that implements the use of an independent variable to track window splitting since s:splitMode != '' no longer implies that a split was triggered.","package":"bufexplorer-7.4.23.zip","4":"bufexplorer-7.4.23.zip","src_id":"27929","5":"27929","creation_date":"1643362948","6":"1643362948"},{"0":"42","vim_version":"7.4","1":"7.4","script_version":"7.4.21","2":"7.4.21","version_comment":"Merged in changes from adelarsq, which was the added support for ryanoasis\/vim-devicons.","3":"Merged in changes from adelarsq, which was the added support for ryanoasis\/vim-devicons.","package":"bufexplorer-7.4.21.zip","4":"bufexplorer-7.4.21.zip","src_id":"26416","5":"26416","creation_date":"1551999408","6":"1551999408"},{"0":"42","vim_version":"7.4","1":"7.4","script_version":"7.4.19","2":"7.4.19","version_comment":"Merged in changes from github.  Changes include but not limited to:\r\n- Thanks to Yubo Su for the patch that adds 'f, F, V, and v' commands.  With this change, the original 'f' command was remapped to 'a'.\r\n\r\n  The set of commands that can be used during exploring are:\r\n    F - Open selected buffer in another window above the current.\r\n    f - Open selected buffer in another window below the current.\r\n    V - Open the selected buffer in another window on the left of the current.\r\n    v - Open the selected buffer in another window on the right of the current.","3":"Merged in changes from github.  Changes include but not limited to:\r\n- Thanks to Yubo Su for the patch that adds 'f, F, V, and v' commands.  With this change, the original 'f' command was remapped to 'a'.\r\n\r\n  The set of commands that can be used during exploring are:\r\n    F - Open selected buffer in another window above the current.\r\n    f - Open selected buffer in another window below the current.\r\n    V - Open the selected buffer in another window on the left of the current.\r\n    v - Open the selected buffer in another window on the right of the current.","package":"bufexplorer-7.4.19.zip","4":"bufexplorer-7.4.19.zip","src_id":"25593","5":"25593","creation_date":"1506695134","6":"1506695134"},{"0":"42","vim_version":"7.4","1":"7.4","script_version":"7.4.15","2":"7.4.15","version_comment":"- As suggested by adelarsq way back on January 5th, 2016, a filetype has been added.  There is now 'filetype=bufexplorer'.\r\n- Finally applied the patch submitted by justfalter.  This patch is a backward-compatible fix for the \"invalid tab range\" bug.","3":"- As suggested by adelarsq way back on January 5th, 2016, a filetype has been added.  There is now 'filetype=bufexplorer'.\r\n- Finally applied the patch submitted by justfalter.  This patch is a backward-compatible fix for the \"invalid tab range\" bug.","package":"bufexplorer-7.4.15.zip","4":"bufexplorer-7.4.15.zip","src_id":"25120","5":"25120","creation_date":"1493819649","6":"1493819649"},{"0":"42","vim_version":"7.4","1":"7.4","script_version":"7.4.13","2":"7.4.13","version_comment":"Thanks to devakivamsi for pointing out that even though bufexplorer turns off line numbers by default within its own window, this did not work correctly when using WinManager.  This has now been corrected.","3":"Thanks to devakivamsi for pointing out that even though bufexplorer turns off line numbers by default within its own window, this did not work correctly when using WinManager.  This has now been corrected.","package":"bufexplorer-7.4.13.zip","4":"bufexplorer-7.4.13.zip","src_id":"25062","5":"25062","creation_date":"1490963959","6":"1490963959"},{"0":"42","vim_version":"7.4","1":"7.4","script_version":"7.4.12","2":"7.4.12","version_comment":"Forgot to update vim.org with the version on github!  Opps...\r\nChanges include:\r\n    - Thanks again to Martin Vuille for several more fixes related to making bufexplorer more tab-friendly.\r\n    - Thanks to Martin Vuille for reworking the per-tab buffer listing code.  Fix for g:bufExplorerShowTabBuffer is not working correctly and other \"glitches\" when the ShotTabBuffer option is enabled.  For example old code would not correctly handle adding\/deleting a tab that wasn't the highest-numbered tab.\r\n    - Thanks to buddylindsey for fixing a misspelling in the docs.","3":"Forgot to update vim.org with the version on github!  Opps...\r\nChanges include:\r\n    - Thanks again to Martin Vuille for several more fixes related to making bufexplorer more tab-friendly.\r\n    - Thanks to Martin Vuille for reworking the per-tab buffer listing code.  Fix for g:bufExplorerShowTabBuffer is not working correctly and other \"glitches\" when the ShotTabBuffer option is enabled.  For example old code would not correctly handle adding\/deleting a tab that wasn't the highest-numbered tab.\r\n    - Thanks to buddylindsey for fixing a misspelling in the docs.","package":"bufexplorer-7.4.12.zip","4":"bufexplorer-7.4.12.zip","src_id":"24742","5":"24742","creation_date":"1479408896","6":"1479408896"},{"0":"42","vim_version":"7.4","1":"7.4","script_version":"7.4.9","2":"7.4.9","version_comment":"- Thanks to ivegotasthma for supplying a patch to fix a major issue with plugin performance when lots of buffers are open.\r\n- Thanks to ershov for the patch to fix grouping of files in ambiguous sort modes.\r\n- Thanks to PhilRunninger for changing documentation to use <Leader>, in place of ''.\r\n- Converted files to Unix format.","3":"- Thanks to ivegotasthma for supplying a patch to fix a major issue with plugin performance when lots of buffers are open.\r\n- Thanks to ershov for the patch to fix grouping of files in ambiguous sort modes.\r\n- Thanks to PhilRunninger for changing documentation to use <Leader>, in place of ''.\r\n- Converted files to Unix format.","package":"bufexplorer-7.4.9.zip","4":"bufexplorer-7.4.9.zip","src_id":"24205","5":"24205","creation_date":"1461764816","6":"1461764816"},{"0":"42","vim_version":"7.4","1":"7.4","script_version":"v7.4.6","2":"v7.4.6","version_comment":"Converted files back to Unix format.  It looks like I had git setup incorrectly and the files got converted to Dos format...","3":"Converted files back to Unix format.  It looks like I had git setup incorrectly and the files got converted to Dos format...","package":"bufexplorer-7.4.6.zip","4":"bufexplorer-7.4.6.zip","src_id":"22601","5":"22601","creation_date":"1415073666","6":"1415073666"},{"0":"42","vim_version":"7.3","1":"7.3","script_version":"7.4.5","2":"7.4.5","version_comment":"- Dr Michael Henry suggested to change all noremap commands to nnoremap.  Using noremap is unnecessarily broad and can cause problems, especially for select mode.\r\n- Revert change where bufexplorer windows was closed even if the target buffer has not been loaded yet.\r\n- Ivan Ukhov fixed issue with deleting the last window.  This update also fixes as well as another.  If you have say, NERDtree open on the left side and bufexplorer on the right, that bufexplorer would close NERDtree erroneously thinking that it is closing itself.\r\n- Radoslaw Burny fixed a few bugs that surfaced when bufexplorer is used within winmanager.","3":"- Dr Michael Henry suggested to change all noremap commands to nnoremap.  Using noremap is unnecessarily broad and can cause problems, especially for select mode.\r\n- Revert change where bufexplorer windows was closed even if the target buffer has not been loaded yet.\r\n- Ivan Ukhov fixed issue with deleting the last window.  This update also fixes as well as another.  If you have say, NERDtree open on the left side and bufexplorer on the right, that bufexplorer would close NERDtree erroneously thinking that it is closing itself.\r\n- Radoslaw Burny fixed a few bugs that surfaced when bufexplorer is used within winmanager.","package":"bufexplorer-7.4.5.zip","4":"bufexplorer-7.4.5.zip","src_id":"22563","5":"22563","creation_date":"1414207819","6":"1414207819"},{"0":"42","vim_version":"7.0","1":"7.0","script_version":"7.4.2","2":"7.4.2","version_comment":"Added global option g:bufExplorerDisableDefaultKeyMapping.  This option controls weather the default key mappings (\\be, \\bs, and \\bv) are enabled or not.  See documentation for more information.","3":"Added global option g:bufExplorerDisableDefaultKeyMapping.  This option controls weather the default key mappings (\\be, \\bs, and \\bv) are enabled or not.  See documentation for more information.","package":"bufexplorer-7.4.2.zip","4":"bufexplorer-7.4.2.zip","src_id":"20953","5":"20953","creation_date":"1382705955","6":"1382705955"},{"0":"42","vim_version":"7.3","1":"7.3","script_version":"7.4.1","2":"7.4.1","version_comment":"- First update related to Vim 7.4.\r\n- I have been asked by several bufexplorer users to put the code on github so that the Vundle plugin could be used to make updates easier.  The code can now be found on github at https:\/\/github.com\/jlanzarotta\/bufexplorer.  For those that use the Vundle plugin, you can add 'Bundle 'jlanzarotta\/bufexplorer' to your _vimrc or .vimrc file to get the latest version.\r\n- Changed license text.\r\n- Fixed issue with 'hidden'.  If 'hidden' is set, make sure that g:bufExplorerFindActive is set to 0.  Otherwise, when using \/bs or \/bv, and selecting a buffer, the original buffer will be switched to instead of being opened in the newly created windows.\r\n- Added new 'b' mapping when the bufExplorer window is opened.  When 'b' is pressed, the user is prompted for the buffer number to switch to, and is is then switched to when <CR> is pressed.  This allows for somewhat faster buffer switching instead of using the j and k keys or the mouse to select the buffer to switch to.\r\n- Removed 'set nolist' from the Initialize() function as well as the restore of the 'list' setting in the CleanUp() function.  These were causing issues when multiple new files were opened from the command line.  Furthermore, there was really no reason, that I can remember, to why the 'list' setting was saved, modified, and restored anyways.\r\n- Fixed issue with WinManager integration code not working correctly anymore.\r\n- Brought back the xnoremap setup for the 'd' and 'D' keys.  These were removed for some reason after version 7.2.8.\r\n- Thanks to all the contributors and testers.\r\n- If there are any issues you find or enhancements you would like, let me know. ","3":"- First update related to Vim 7.4.\r\n- I have been asked by several bufexplorer users to put the code on github so that the Vundle plugin could be used to make updates easier.  The code can now be found on github at https:\/\/github.com\/jlanzarotta\/bufexplorer.  For those that use the Vundle plugin, you can add 'Bundle 'jlanzarotta\/bufexplorer' to your _vimrc or .vimrc file to get the latest version.\r\n- Changed license text.\r\n- Fixed issue with 'hidden'.  If 'hidden' is set, make sure that g:bufExplorerFindActive is set to 0.  Otherwise, when using \/bs or \/bv, and selecting a buffer, the original buffer will be switched to instead of being opened in the newly created windows.\r\n- Added new 'b' mapping when the bufExplorer window is opened.  When 'b' is pressed, the user is prompted for the buffer number to switch to, and is is then switched to when <CR> is pressed.  This allows for somewhat faster buffer switching instead of using the j and k keys or the mouse to select the buffer to switch to.\r\n- Removed 'set nolist' from the Initialize() function as well as the restore of the 'list' setting in the CleanUp() function.  These were causing issues when multiple new files were opened from the command line.  Furthermore, there was really no reason, that I can remember, to why the 'list' setting was saved, modified, and restored anyways.\r\n- Fixed issue with WinManager integration code not working correctly anymore.\r\n- Brought back the xnoremap setup for the 'd' and 'D' keys.  These were removed for some reason after version 7.2.8.\r\n- Thanks to all the contributors and testers.\r\n- If there are any issues you find or enhancements you would like, let me know. ","package":"bufexplorer-7.4.1.zip","4":"bufexplorer-7.4.1.zip","src_id":"20925","5":"20925","creation_date":"1381931393","6":"1381931393"},{"0":"42","vim_version":"7.0","1":"7.0","script_version":"7.3.6","2":"7.3.6","version_comment":"Removed the 'drop' window command that was causing issue with the argument-list being modified after the BufExplorer windows was displayed.\r\n","3":"Removed the 'drop' window command that was causing issue with the argument-list being modified after the BufExplorer windows was displayed.\r\n","package":"bufexplorer-7.3.6.zip","4":"bufexplorer-7.3.6.zip","src_id":"20031","5":"20031","creation_date":"1367857524","6":"1367857524"},{"0":"42","vim_version":"7.0","1":"7.0","script_version":"7.3.5","2":"7.3.5","version_comment":"Michael Henry added the ability to view \"No Name\" buffers.  This functionality was lost since version 7.3.0.  He also did some removal of \"dead\" code and cleaned up the code to handle filenames with embedded '\"'.","3":"Michael Henry added the ability to view \"No Name\" buffers.  This functionality was lost since version 7.3.0.  He also did some removal of \"dead\" code and cleaned up the code to handle filenames with embedded '\"'.","package":"bufexplorer-7.3.5.zip","4":"bufexplorer-7.3.5.zip","src_id":"19481","5":"19481","creation_date":"1360337722","6":"1360337722"},{"0":"42","vim_version":"7.0","1":"7.0","script_version":"7.3.4","2":"7.3.4","version_comment":"Thanks go out to John Szakmeister for finding and fixing a bug in the RebuildBufferList method.  The keepjumps line that clears the list could potentially reference a backwards range.","3":"Thanks go out to John Szakmeister for finding and fixing a bug in the RebuildBufferList method.  The keepjumps line that clears the list could potentially reference a backwards range.","package":"bufexplorer-7.3.4.zip","4":"bufexplorer-7.3.4.zip","src_id":"19446","5":"19446","creation_date":"1359397083","6":"1359397083"},{"0":"42","vim_version":"7.0","1":"7.0","script_version":"7.3.3","2":"7.3.3","version_comment":"* Major cleanup and reorganization of the change log.\r\n* We welcome the return of g:bufExplorerSplitHorzSize and g:bufExplorerSplitVertSize.  When setting these values, anything less than or equal to 0 causes the split windows size to be determined by Vim.  If for example you want your new horizontal split window 10 rows high, set g:bufExplorerSplitHorzSize = 10 in your .vimrc.  Similar would be done if wanting a vertical split except you would use the g:bufExplorerSplitVertSize variable instead.","3":"* Major cleanup and reorganization of the change log.\r\n* We welcome the return of g:bufExplorerSplitHorzSize and g:bufExplorerSplitVertSize.  When setting these values, anything less than or equal to 0 causes the split windows size to be determined by Vim.  If for example you want your new horizontal split window 10 rows high, set g:bufExplorerSplitHorzSize = 10 in your .vimrc.  Similar would be done if wanting a vertical split except you would use the g:bufExplorerSplitVertSize variable instead.","package":"bufexplorer-7.3.3.zip","4":"bufexplorer-7.3.3.zip","src_id":"19370","5":"19370","creation_date":"1358170988","6":"1358170988"},{"0":"42","vim_version":"7.0","1":"7.0","script_version":"7.2.3","2":"7.2.3","version_comment":"Thanks go out to Michael Henry for pointing out that I completely missed yet another function, ReverseSortSelect(), during the refactoring.  This function has now returned.\r\n","3":"Thanks go out to Michael Henry for pointing out that I completely missed yet another function, ReverseSortSelect(), during the refactoring.  This function has now returned.\r\n","package":"bufexplorer-7.3.2.zip","4":"bufexplorer-7.3.2.zip","src_id":"19234","5":"19234","creation_date":"1356316581","6":"1356316581"},{"0":"42","vim_version":"7.0","1":"7.0","script_version":"7.3.1","2":"7.3.1","version_comment":"Thanks go out to Brett Rasmussen for pointing out that the feature added way back in version 7.2.3 by Yuriy Ershov to automatically reposition the cursor to the line containing the active buffer, was no longer in the plugin.  That bit of code has been re-added and all is well.\r\n","3":"Thanks go out to Brett Rasmussen for pointing out that the feature added way back in version 7.2.3 by Yuriy Ershov to automatically reposition the cursor to the line containing the active buffer, was no longer in the plugin.  That bit of code has been re-added and all is well.\r\n","package":"bufexplorer-7.3.1.zip","4":"bufexplorer-7.3.1.zip","src_id":"19122","5":"19122","creation_date":"1354802432","6":"1354802432"},{"0":"42","vim_version":"7.0","1":"7.0","script_version":"7.3.0","2":"7.3.0","version_comment":"It has been quite a while since I published a new version and this is the first version since Vim 7.3 was released.\r\n    * Thanks to Tim Johnson for testing out this new version.\r\n    * I have put some time into reworking and cleaning up the code as\r\n    * well as various bug fixes.\r\n    * I have hopefully allowed for better mapping of the main public methods as is explained in the \r\n      bufexplorer-  customization section of the documentation.\r\n    * Add new 'B', 'o', and 'S' key mappings.\r\n    * Overall, I am hopeful that I not forgotten or lost a feature :)","3":"It has been quite a while since I published a new version and this is the first version since Vim 7.3 was released.\r\n    * Thanks to Tim Johnson for testing out this new version.\r\n    * I have put some time into reworking and cleaning up the code as\r\n    * well as various bug fixes.\r\n    * I have hopefully allowed for better mapping of the main public methods as is explained in the \r\n      bufexplorer-  customization section of the documentation.\r\n    * Add new 'B', 'o', and 'S' key mappings.\r\n    * Overall, I am hopeful that I not forgotten or lost a feature :)","package":"bufexplorer-7.3.0.zip","4":"bufexplorer-7.3.0.zip","src_id":"18766","5":"18766","creation_date":"1349785843","6":"1349785843"},{"0":"42","vim_version":"7.0","1":"7.0","script_version":"7.2.8","2":"7.2.8","version_comment":"Thanks to Charles Campbell for integrating bufexplorer with GDBMGR.\r\n(http:\/\/mysite.verizon.net\/astronaut\/vim\/index.html#GDBMGR)\r\n* Fixed update date.","3":"Thanks to Charles Campbell for integrating bufexplorer with GDBMGR.\r\n(http:\/\/mysite.verizon.net\/astronaut\/vim\/index.html#GDBMGR)\r\n* Fixed update date.","package":"bufexplorer.zip","4":"bufexplorer.zip","src_id":"14208","5":"14208","creation_date":"1289242967","6":"1289242967"},{"0":"42","vim_version":"7.0","1":"7.0","script_version":"7.2.7","2":"7.2.7","version_comment":"This is my first attempt to fix the \"cache\" issue where buffer information has changed but the cache\/display does not reflect those changes. More work still needs to be done. More or less the cache has been disabled.","3":"This is my first attempt to fix the \"cache\" issue where buffer information has changed but the cache\/display does not reflect those changes. More work still needs to be done. More or less the cache has been disabled.","package":"bufexplorer.zip","4":"bufexplorer.zip","src_id":"12904","5":"12904","creation_date":"1272317510","6":"1272317510"},{"0":"42","vim_version":"7.0","1":"7.0","script_version":"7.2.6","2":"7.2.6","version_comment":"Thanks to Michael Henry for pointing out that I totally forgot to update the inline help to reflect the previous change to the 'd' and 'D' keys. Opps!","3":"Thanks to Michael Henry for pointing out that I totally forgot to update the inline help to reflect the previous change to the 'd' and 'D' keys. Opps!","package":"bufexplorer.zip","4":"bufexplorer.zip","src_id":"12363","5":"12363","creation_date":"1265985139","6":"1265985139"},{"0":"42","vim_version":"6.0","1":"6.0","script_version":"7.2.5","2":"7.2.5","version_comment":"Philip Morant suggested switching the command (bwipe) associated with the 'd' key with the command (bdelete) associated with the 'D' key. This made sense since the 'd' key is more likely to be used compared to the 'D' key.","3":"Philip Morant suggested switching the command (bwipe) associated with the 'd' key with the command (bdelete) associated with the 'D' key. This made sense since the 'd' key is more likely to be used compared to the 'D' key.","package":"bufexplorer.zip","4":"bufexplorer.zip","src_id":"12354","5":"12354","creation_date":"1265818392","6":"1265818392"},{"0":"42","vim_version":"7.0","1":"7.0","script_version":"7.2.4","2":"7.2.4","version_comment":"Fix: I did not implement the patch provided by Godefroid Chapelle correctly. I missed one line which happened to be the most important one :)","3":"Fix: I did not implement the patch provided by Godefroid Chapelle correctly. I missed one line which happened to be the most important one :)","package":"bufexplorer.zip","4":"bufexplorer.zip","src_id":"12104","5":"12104","creation_date":"1263487279","6":"1263487279"},{"0":"42","vim_version":"7.0","1":"7.0","script_version":"7.2.3","2":"7.2.3","version_comment":"Hopefully I have not let anyone or anything out :)\r\n- Enhancements:\r\n    * Thanks to David Fishburn for helping me out with a much needed\r\n       code overhaul as well as some awesome performance enhancements.\r\n       He also reworked the handling of tabs.\r\n    * Thanks to Vladimir Dobriakov for making the suggestions on\r\n       enhancing the documentation to include a better explaination of\r\n       what is contained in the main bufexplorer window.\r\n    * Thanks to Yuriy Ershov for added code that when the bufexplorer\r\n       window is opened, the cursor is now positioned at the line with the\r\n       active buffer (useful in non-MRU sort modes).\r\n    * Yuriy also added the abiltiy to cycle through the sort fields in\r\n       reverse order.\r\n- Fixes:\r\n    * Thanks to Michael Henry for supplying a patch that allows\r\n       bufexplorer to be opened even when there is one buffer or less.\r\n    * Thanks to Godefroid Chapelle for supplying a patch that fixed\r\n       MRU sort order after loading a session.","3":"Hopefully I have not let anyone or anything out :)\r\n- Enhancements:\r\n    * Thanks to David Fishburn for helping me out with a much needed\r\n       code overhaul as well as some awesome performance enhancements.\r\n       He also reworked the handling of tabs.\r\n    * Thanks to Vladimir Dobriakov for making the suggestions on\r\n       enhancing the documentation to include a better explaination of\r\n       what is contained in the main bufexplorer window.\r\n    * Thanks to Yuriy Ershov for added code that when the bufexplorer\r\n       window is opened, the cursor is now positioned at the line with the\r\n       active buffer (useful in non-MRU sort modes).\r\n    * Yuriy also added the abiltiy to cycle through the sort fields in\r\n       reverse order.\r\n- Fixes:\r\n    * Thanks to Michael Henry for supplying a patch that allows\r\n       bufexplorer to be opened even when there is one buffer or less.\r\n    * Thanks to Godefroid Chapelle for supplying a patch that fixed\r\n       MRU sort order after loading a session.","package":"bufexplorer.zip","4":"bufexplorer.zip","src_id":"11905","5":"11905","creation_date":"1260903301","6":"1260903301"},{"0":"42","vim_version":"7.0","1":"7.0","script_version":"7.2.2","2":"7.2.2","version_comment":"Thanks to David L. Dight for spotting and fixing an issue when using ctrl^. bufexplorer would incorrectly handle the previous buffer so that when ctrl^ was pressed the incorrect file was opened.\r\n","3":"Thanks to David L. Dight for spotting and fixing an issue when using ctrl^. bufexplorer would incorrectly handle the previous buffer so that when ctrl^ was pressed the incorrect file was opened.\r\n","package":"bufexplorer.zip","4":"bufexplorer.zip","src_id":"9524","5":"9524","creation_date":"1227116826","6":"1227116826"},{"0":"42","vim_version":"7.0","1":"7.0","script_version":"7.2.1","2":"7.2.1","version_comment":"7.2.1  - Fix: * Thanks to Dimitar for spotting and fixing a feature that was inadvertently left out of the previous version. The feature was when bufexplorer was used together with WinManager, you could use the tab key to open a buffer in a split window.","3":"7.2.1  - Fix: * Thanks to Dimitar for spotting and fixing a feature that was inadvertently left out of the previous version. The feature was when bufexplorer was used together with WinManager, you could use the tab key to open a buffer in a split window.","package":"bufexplorer.zip","4":"bufexplorer.zip","src_id":"9220","5":"9220","creation_date":"1220420584","6":"1220420584"},{"0":"42","vim_version":"6.0","1":"6.0","script_version":"7.2.0","2":"7.2.0","version_comment":"- Enhancements:\r\n  * For all those missing the \\bs and \\bv commands, these have now returned. Thanks to Phil O'Connell for asking for the return of these missing features and helping test out this version.\r\n- Fixes:\r\n  * Fixed problem with the bufExplorerFindActive code not working correctly.\r\n  * Fixed an incompatibility between bufexplorer and netrw that caused buffers to be incorrectly removed from the MRU list.","3":"- Enhancements:\r\n  * For all those missing the \\bs and \\bv commands, these have now returned. Thanks to Phil O'Connell for asking for the return of these missing features and helping test out this version.\r\n- Fixes:\r\n  * Fixed problem with the bufExplorerFindActive code not working correctly.\r\n  * Fixed an incompatibility between bufexplorer and netrw that caused buffers to be incorrectly removed from the MRU list.","package":"bufexplorer.zip","4":"bufexplorer.zip","src_id":"9128","5":"9128","creation_date":"1218787734","6":"1218787734"},{"0":"42","vim_version":"6.0","1":"6.0","script_version":"7.1.7","2":"7.1.7","version_comment":"TaCahiroy fixed several issues related to opening a buffer in a tab.\r\n","3":"TaCahiroy fixed several issues related to opening a buffer in a tab.\r\n","package":"bufexplorer.zip","4":"bufexplorer.zip","src_id":"8079","5":"8079","creation_date":"1198233376","6":"1198233376"},{"0":"42","vim_version":"6.0","1":"6.0","script_version":"7.1.6","2":"7.1.6","version_comment":"Fixes:\r\n  * Removed ff=unix from modeline in bufexplorer.txt. Found by Bill McCarthy.","3":"Fixes:\r\n  * Removed ff=unix from modeline in bufexplorer.txt. Found by Bill McCarthy.","package":"bufexplorer.zip","4":"bufexplorer.zip","src_id":"8015","5":"8015","creation_date":"1196549065","6":"1196549065"},{"0":"42","vim_version":"6.0","1":"6.0","script_version":"7.1.5","2":"7.1.5","version_comment":"Fixed: Could not open unnamed buffers. Fixed by TaCahiroy.","3":"Fixed: Could not open unnamed buffers. Fixed by TaCahiroy.","package":"bufexplorer.zip","4":"bufexplorer.zip","src_id":"8008","5":"8008","creation_date":"1196405132","6":"1196405132"},{"0":"42","vim_version":"6.0","1":"6.0","script_version":"7.1.4","2":"7.1.4","version_comment":"Fixes:\r\n  * Sometimes when a file's path has 'white space' in it, extra buffers would be created containing each piece of the path. i.e: opening c:\\document and settings\\test.txt would create a buffer named \"and\" and a buffer named \"Documents\". This was reported and fixed by TaCa Yoss. ","3":"Fixes:\r\n  * Sometimes when a file's path has 'white space' in it, extra buffers would be created containing each piece of the path. i.e: opening c:\\document and settings\\test.txt would create a buffer named \"and\" and a buffer named \"Documents\". This was reported and fixed by TaCa Yoss. ","package":"bufexplorer.zip","4":"bufexplorer.zip","src_id":"7953","5":"7953","creation_date":"1195216395","6":"1195216395"},{"0":"42","vim_version":"6.0","1":"6.0","script_version":"7.1.3","2":"7.1.3","version_comment":"Added code to allow only one instance of the plugin to run at a time. Thanks Dennis Hostetler.","3":"Added code to allow only one instance of the plugin to run at a time. Thanks Dennis Hostetler.","package":"bufexplorer.zip","4":"bufexplorer.zip","src_id":"7946","5":"7946","creation_date":"1195127489","6":"1195127489"},{"0":"42","vim_version":"6.0","1":"6.0","script_version":"7.1.2","2":"7.1.2","version_comment":"This is a MAJOR update.\r\n* Added handling of tabs. (Dave Larson)\r\n* Removed \\bs and \\bv commands because these are easier for the user to create horizontal and vertical windows. (Dave Larson)\r\n* Fixed jumplist issue spotted by JiangJun.\r\n* Went back to using just a plugin file, instead of both an autoload and plugin file. The splitting of the file caused issues with other plugins. So if you have a prior version of bufexplorer that has an autoload file, please remove autoload\\bufexplorer and plugin\\bufexplorer before installing this new version.\r\n* Fixed E493 error spotted by Thomas Arendsen Hein.\r\n* Minor cosmetic changes.\r\n* Minor help file changes.","3":"This is a MAJOR update.\r\n* Added handling of tabs. (Dave Larson)\r\n* Removed \\bs and \\bv commands because these are easier for the user to create horizontal and vertical windows. (Dave Larson)\r\n* Fixed jumplist issue spotted by JiangJun.\r\n* Went back to using just a plugin file, instead of both an autoload and plugin file. The splitting of the file caused issues with other plugins. So if you have a prior version of bufexplorer that has an autoload file, please remove autoload\\bufexplorer and plugin\\bufexplorer before installing this new version.\r\n* Fixed E493 error spotted by Thomas Arendsen Hein.\r\n* Minor cosmetic changes.\r\n* Minor help file changes.","package":"bufexplorer.zip","4":"bufexplorer.zip","src_id":"7893","5":"7893","creation_date":"1194424427","6":"1194424427"},{"0":"42","vim_version":"7.0","1":"7.0","script_version":"7.0.17","2":"7.0.17","version_comment":"Fixed issue with 'drop' command. Various enhancements and improvements. ","3":"Fixed issue with 'drop' command. Various enhancements and improvements. ","package":"bufexplorer.zip","4":"bufexplorer.zip","src_id":"7406","5":"7406","creation_date":"1185258634","6":"1185258634"},{"0":"42","vim_version":"7.0","1":"7.0","script_version":"7.0.15","2":"7.0.15","version_comment":"Thanks to Mark Smithfield for suggesting bufexplorer needed to handle the ':args' command.\r\nFixed issue reported by Liu Jiaping on non Windows systems, which was\r\n  ...\r\nOpen file1, open file2, modify file1, open bufexplorer, you get the following error:\r\n--------8<--------\r\nError detected while processing function\r\n<SNR>14_StartBufExplorer..<SNR>14_SplitOpen:\r\nline    4:\r\nE37: No write since last change (add ! to override)\r\n--------8<--------\r\n\r\nBut the worse thing is, when I want to save the current buffer and type ':w', I get another error message:\r\n\r\n--------8<--------\r\nE382: Cannot write, 'buftype' option is set \r\n--------8<--------","3":"Thanks to Mark Smithfield for suggesting bufexplorer needed to handle the ':args' command.\r\nFixed issue reported by Liu Jiaping on non Windows systems, which was\r\n  ...\r\nOpen file1, open file2, modify file1, open bufexplorer, you get the following error:\r\n--------8<--------\r\nError detected while processing function\r\n<SNR>14_StartBufExplorer..<SNR>14_SplitOpen:\r\nline    4:\r\nE37: No write since last change (add ! to override)\r\n--------8<--------\r\n\r\nBut the worse thing is, when I want to save the current buffer and type ':w', I get another error message:\r\n\r\n--------8<--------\r\nE382: Cannot write, 'buftype' option is set \r\n--------8<--------","package":"bufexplorer.zip","4":"bufexplorer.zip","src_id":"7032","5":"7032","creation_date":"1177651459","6":"1177651459"},{"0":"42","vim_version":"7.0","1":"7.0","script_version":"7.0.14","2":"7.0.14","version_comment":"Thanks to Randall Hansen for removing the requirement of terminal versions to be recompiled with 'gui' support so the 'drop' command would work. The 'drop' command is really not needed in terminal versions.","3":"Thanks to Randall Hansen for removing the requirement of terminal versions to be recompiled with 'gui' support so the 'drop' command would work. The 'drop' command is really not needed in terminal versions.","package":"bufexplorer.zip","4":"bufexplorer.zip","src_id":"6897","5":"6897","creation_date":"1174628106","6":"1174628106"},{"0":"42","vim_version":"7.0","1":"7.0","script_version":"7.0.13","2":"7.0.13","version_comment":"Fixed Winmanager integration. Thanks to Dave Eggum for another major update. Most notable changes are, improved speed and code clean up. Please see the bufexplorer help for a full list of changes and updates.","3":"Fixed Winmanager integration. Thanks to Dave Eggum for another major update. Most notable changes are, improved speed and code clean up. Please see the bufexplorer help for a full list of changes and updates.","package":"bufexplorer.zip","4":"bufexplorer.zip","src_id":"6773","5":"6773","creation_date":"1172208728","6":"1172208728"},{"0":"42","vim_version":"7.0","1":"7.0","script_version":"7.0.12","2":"7.0.12","version_comment":"MAJOR Update. Please Note that this version will ONLY run with Vim version 7.0 or greater.\r\n\r\nDave Eggum has made some 'significant' updates to this latest version:\r\n  - Added BufExplorerGetAltBuf() global function to be used in the user\u00e2\u0080\u0099s rulerformat.\r\n  - Added g:bufExplorerSplitRight option.\r\n  - Added g:bufExplorerShowRelativePath option with mapping.\r\n  - Added current line highlighting.\r\n  - The split type can now be changed whether bufexplorer is opened in split mode or not.\r\n  - Various major and minor bug fixes and speed improvements.\r\n  - Sort by extension.\r\n  Other improvements\/changes:\r\n  - Changed the help key from '?' to <F1> to be more 'standard'.\r\n  - Fixed splitting of vertical bufexplorer window.","3":"MAJOR Update. Please Note that this version will ONLY run with Vim version 7.0 or greater.\r\n\r\nDave Eggum has made some 'significant' updates to this latest version:\r\n  - Added BufExplorerGetAltBuf() global function to be used in the user\u00e2\u0080\u0099s rulerformat.\r\n  - Added g:bufExplorerSplitRight option.\r\n  - Added g:bufExplorerShowRelativePath option with mapping.\r\n  - Added current line highlighting.\r\n  - The split type can now be changed whether bufexplorer is opened in split mode or not.\r\n  - Various major and minor bug fixes and speed improvements.\r\n  - Sort by extension.\r\n  Other improvements\/changes:\r\n  - Changed the help key from '?' to <F1> to be more 'standard'.\r\n  - Fixed splitting of vertical bufexplorer window.","package":"bufexplorer.zip","4":"bufexplorer.zip","src_id":"6484","5":"6484","creation_date":"1164877661","6":"1164877661"},{"0":"42","vim_version":"6.0","1":"6.0","script_version":"7.0.11","2":"7.0.11","version_comment":"Fixed a couple of highlighting bugs, reported by David Eggum. He also changed passive voice to active on a couple of warning messages.","3":"Fixed a couple of highlighting bugs, reported by David Eggum. He also changed passive voice to active on a couple of warning messages.","package":"bufexplorer.zip","4":"bufexplorer.zip","src_id":"5409","5":"5409","creation_date":"1141995262","6":"1141995262"},{"0":"42","vim_version":"6.0","1":"6.0","script_version":"7.0.10","2":"7.0.10","version_comment":"Fixed bug report by Xiangjiang Ma. If the 'ssl' option is set, the slash character used when displaying the path was incorrect. Thanks Xiangjiang!\r\n","3":"Fixed bug report by Xiangjiang Ma. If the 'ssl' option is set, the slash character used when displaying the path was incorrect. Thanks Xiangjiang!\r\n","package":"bufexplorer.zip","4":"bufexplorer.zip","src_id":"5353","5":"5353","creation_date":"1141307886","6":"1141307886"},{"0":"42","vim_version":"6.0","1":"6.0","script_version":"7.0.9","2":"7.0.9","version_comment":"Martin Grenfell found and eliminated an annoying bug in the bufexplorer\/winmanager integration. The bug was were an annoying message would be displayed when a window was split or a new file was opened in a new window. Thanks Martin!","3":"Martin Grenfell found and eliminated an annoying bug in the bufexplorer\/winmanager integration. The bug was were an annoying message would be displayed when a window was split or a new file was opened in a new window. Thanks Martin!","package":"bufexplorer.zip","4":"bufexplorer.zip","src_id":"5337","5":"5337","creation_date":"1141105021","6":"1141105021"},{"0":"42","vim_version":"6.0","1":"6.0","script_version":"7.0.8","2":"7.0.8","version_comment":"Thanks to Mike Li for catching a bug in the WinManager integration. The bug was related to the incorrect displaying of the buffer explorer's window title.","3":"Thanks to Mike Li for catching a bug in the WinManager integration. The bug was related to the incorrect displaying of the buffer explorer's window title.","package":"bufexplorer.zip","4":"bufexplorer.zip","src_id":"4993","5":"4993","creation_date":"1137581537","6":"1137581537"},{"0":"42","vim_version":"6.0","1":"6.0","script_version":"7.0.7","2":"7.0.7","version_comment":"Thanks to Jeremy Cowgar for adding a new enhancement. This enhancement allows the user to press 'S', that is capital S, which will open the buffer under the cursor in a newly created split window.","3":"Thanks to Jeremy Cowgar for adding a new enhancement. This enhancement allows the user to press 'S', that is capital S, which will open the buffer under the cursor in a newly created split window.","package":"bufexplorer.zip","4":"bufexplorer.zip","src_id":"4904","5":"4904","creation_date":"1134985372","6":"1134985372"},{"0":"42","vim_version":"6.0","1":"6.0","script_version":"7.0.6","2":"7.0.6","version_comment":"Thanks to Larry Zhang for finding a bug in the \"split\" buffer code. If you force set g:bufExplorerSplitType='v' in your vimrc, and if you tried to do a \\bs to split the bufexplorer window, it would always split horizontal, not vertical. He also found that I had a typeo in that the variable g:bufExplorerSplitVertSize was all lower case in the documentation which was incorrect.","3":"Thanks to Larry Zhang for finding a bug in the \"split\" buffer code. If you force set g:bufExplorerSplitType='v' in your vimrc, and if you tried to do a \\bs to split the bufexplorer window, it would always split horizontal, not vertical. He also found that I had a typeo in that the variable g:bufExplorerSplitVertSize was all lower case in the documentation which was incorrect.","package":"bufexplorer.zip","4":"bufexplorer.zip","src_id":"4775","5":"4775","creation_date":"1132296508","6":"1132296508"},{"0":"42","vim_version":"6.0","1":"6.0","script_version":"7.0.5","2":"7.0.5","version_comment":"Thanks to Mun Johl for pointing out a bug that if a buffer was modified, the '+' was not showing up correctly.","3":"Thanks to Mun Johl for pointing out a bug that if a buffer was modified, the '+' was not showing up correctly.","package":"bufexplorer.zip","4":"bufexplorer.zip","src_id":"4680","5":"4680","creation_date":"1129616706","6":"1129616706"},{"0":"42","vim_version":"6.0","1":"6.0","script_version":"7.0.4","2":"7.0.4","version_comment":"Fixed a problem discovered first by Xiangjiang Ma. Well since I've been using vim 7.0 and not 6.3, I started using a function (getftype) that is not in 6.3. So for backward compatibility, I conditionaly use this function now.  Thus, the g:bufExplorerShowDirectories feature is only available when using vim 7.0 and above.","3":"Fixed a problem discovered first by Xiangjiang Ma. Well since I've been using vim 7.0 and not 6.3, I started using a function (getftype) that is not in 6.3. So for backward compatibility, I conditionaly use this function now.  Thus, the g:bufExplorerShowDirectories feature is only available when using vim 7.0 and above.","package":"bufexplorer.zip","4":"bufexplorer.zip","src_id":"4645","5":"4645","creation_date":"1128319804","6":"1128319804"},{"0":"42","vim_version":"6.0","1":"6.0","script_version":"7.0.3","2":"7.0.3","version_comment":"Thanks to Erwin Waterlander for finding a problem when the last buffer was deleted. This issue got me to rewrite the buffer display logic (which I've wanted to do for sometime now).\r\nAlso great thanks to Dave Eggum for coming up with idea for g:bufExplorerShowDirectories. Directories usually show up in the list from using a command like \":e .\", this controls how those are displayed.","3":"Thanks to Erwin Waterlander for finding a problem when the last buffer was deleted. This issue got me to rewrite the buffer display logic (which I've wanted to do for sometime now).\r\nAlso great thanks to Dave Eggum for coming up with idea for g:bufExplorerShowDirectories. Directories usually show up in the list from using a command like \":e .\", this controls how those are displayed.","package":"bufexplorer.zip","4":"bufexplorer.zip","src_id":"4636","5":"4636","creation_date":"1128063808","6":"1128063808"},{"0":"42","vim_version":"6.0","1":"6.0","script_version":"7.0.2","2":"7.0.2","version_comment":"Thanks to Thomas Arendsen Hein for finding a problem when a user has the default help turned off and then brought up the explorer. An E493 would be displayed.\r\n","3":"Thanks to Thomas Arendsen Hein for finding a problem when a user has the default help turned off and then brought up the explorer. An E493 would be displayed.\r\n","package":"bufexplorer.zip","4":"bufexplorer.zip","src_id":"4072","5":"4072","creation_date":"1111745610","6":"1111745610"},{"0":"42","vim_version":"6.0","1":"6.0","script_version":"7.0.1","2":"7.0.1","version_comment":"Thanks to Erwin Waterlander for finding a couple problems. The first problem allowed a modified buffer to be deleted.  Opps! The second problem occured when several files were opened, BufExplorer was started, the current buffer was deleted using the 'd' option, and then BufExplorer was exited. The deleted buffer was still visible while it is not in the buffers list. Opps again!","3":"Thanks to Erwin Waterlander for finding a couple problems. The first problem allowed a modified buffer to be deleted.  Opps! The second problem occured when several files were opened, BufExplorer was started, the current buffer was deleted using the 'd' option, and then BufExplorer was exited. The deleted buffer was still visible while it is not in the buffers list. Opps again!","package":"bufexplorer.zip","4":"bufexplorer.zip","src_id":"3994","5":"3994","creation_date":"1110441671","6":"1110441671"},{"0":"42","vim_version":"6.0","1":"6.0","script_version":"7.0.0","2":"7.0.0","version_comment":"Thanks to Shankar R. for suggesting to add the ability to set the fixed width (g:bufExplorerSplitVertSize) of a new window when opening bufexplorer vertically and fixed height (g:bufExplorerSplitHorzSize) of a new window when opening bufexplorer horizontally. By default, the windows are normally split to use half the existing width or height.","3":"Thanks to Shankar R. for suggesting to add the ability to set the fixed width (g:bufExplorerSplitVertSize) of a new window when opening bufexplorer vertically and fixed height (g:bufExplorerSplitHorzSize) of a new window when opening bufexplorer horizontally. By default, the windows are normally split to use half the existing width or height.","package":"bufexplorer.zip","4":"bufexplorer.zip","src_id":"3932","5":"3932","creation_date":"1109569202","6":"1109569202"},{"0":"42","vim_version":"6.0","1":"6.0","script_version":"6.3.0","2":"6.3.0","version_comment":"Added keepjumps so that the jumps list would not get clutered with bufexplorer related stuff.","3":"Added keepjumps so that the jumps list would not get clutered with bufexplorer related stuff.","package":"bufexplorer.zip","4":"bufexplorer.zip","src_id":"3262","5":"3262","creation_date":"1090571554","6":"1090571554"},{"0":"42","vim_version":"6.0","1":"6.0","script_version":"6.2.3","2":"6.2.3","version_comment":"Thanks to Jay Logan for finding  a bug in the vertical split postion of the code. When selecting that the window was to be split vertically by doing a '\\bv', from then on, all splits, i.e. '\\bs', were split vertically, even though g:bufExplorerSplitType was not set to 'v'.","3":"Thanks to Jay Logan for finding  a bug in the vertical split postion of the code. When selecting that the window was to be split vertically by doing a '\\bv', from then on, all splits, i.e. '\\bs', were split vertically, even though g:bufExplorerSplitType was not set to 'v'.","package":"bufexplorer.zip","4":"bufexplorer.zip","src_id":"2937","5":"2937","creation_date":"1082015512","6":"1082015512"},{"0":"42","vim_version":"6.0","1":"6.0","script_version":"6.2.2","2":"6.2.2","version_comment":"Thanks to Patrik Modesto for adding a small improvement. For some reason his bufexplorer window was always showing up folded. He added 'setlocal nofoldenable' and it was fixed. If you are having the same problem, this version is for you...\r\n","3":"Thanks to Patrik Modesto for adding a small improvement. For some reason his bufexplorer window was always showing up folded. He added 'setlocal nofoldenable' and it was fixed. If you are having the same problem, this version is for you...\r\n","package":"bufexplorer.zip","4":"bufexplorer.zip","src_id":"2652","5":"2652","creation_date":"1073624377","6":"1073624377"},{"0":"42","vim_version":"6.0","1":"6.0","script_version":"6.2.1","2":"6.2.1","version_comment":"Thanks goes out to Takashi Matsuo for added the 'fullPath' sorting logic and option.","3":"Thanks goes out to Takashi Matsuo for added the 'fullPath' sorting logic and option.","package":"bufexplorer.zip","4":"bufexplorer.zip","src_id":"2383","5":"2383","creation_date":"1065678735","6":"1065678735"},{"0":"42","vim_version":"6.0","1":"6.0","script_version":"6.2.0","2":"6.2.0","version_comment":"Thanks goes out to Simon Johann-G\u00c3\u00bcnter for spotting and fixing a problem in that the last search pattern is overriden by the search pattern for blank lines.","3":"Thanks goes out to Simon Johann-G\u00c3\u00bcnter for spotting and fixing a problem in that the last search pattern is overriden by the search pattern for blank lines.","package":"bufexplorer.zip","4":"bufexplorer.zip","src_id":"2075","5":"2075","creation_date":"1055486899","6":"1055486899"},{"0":"42","vim_version":"6.0","1":"6.0","script_version":"6.1.6","2":"6.1.6","version_comment":"Thanks to Artem Chuprina for finding a pesky bug that has been around for sometime now. The <esc> key mapping was causing the buffer explored to close prematurely when vim was run in an xterm. The <esc> key mapping is now removed.","3":"Thanks to Artem Chuprina for finding a pesky bug that has been around for sometime now. The <esc> key mapping was causing the buffer explored to close prematurely when vim was run in an xterm. The <esc> key mapping is now removed.","package":"bufexplorer.zip","4":"bufexplorer.zip","src_id":"1968","5":"1968","creation_date":"1052135330","6":"1052135330"},{"0":"42","vim_version":"6.0","1":"6.0","script_version":"6.1.5","2":"6.1.5","version_comment":"Thanks to Khorev Sergey. Added option to show default help or not.","3":"Thanks to Khorev Sergey. Added option to show default help or not.","package":"bufexplorer.zip","4":"bufexplorer.zip","src_id":"1948","5":"1948","creation_date":"1051524704","6":"1051524704"},{"0":"42","vim_version":"6.0","1":"6.0","script_version":"6.1.4","2":"6.1.4","version_comment":"Thanks goes out to Valery Kondakoff for suggesting the addition of setlocal nonumber and foldcolumn=0. This allows for line numbering and folding to be turned off temporarily while in the explorer.","3":"Thanks goes out to Valery Kondakoff for suggesting the addition of setlocal nonumber and foldcolumn=0. This allows for line numbering and folding to be turned off temporarily while in the explorer.","package":"bufexplorer.zip","4":"bufexplorer.zip","src_id":"1822","5":"1822","creation_date":"1047968745","6":"1047968745"},{"0":"42","vim_version":"6.0","1":"6.0","script_version":"6.1.3","2":"6.1.3","version_comment":"Added the ability to force the newly split window to be temporarily vertical, which was suggested by Thomas Glanzmann. Added folding. Did some code cleanup.","3":"Added the ability to force the newly split window to be temporarily vertical, which was suggested by Thomas Glanzmann. Added folding. Did some code cleanup.","package":"bufexplorer.zip","4":"bufexplorer.zip","src_id":"1799","5":"1799","creation_date":"1047377515","6":"1047377515"},{"0":"42","vim_version":"6.0","1":"6.0","script_version":"6.1.2","2":"6.1.2","version_comment":"Now pressing the <esc> key will quit, just like 'q'. Added folds to hide winmanager configuration. If anyone had the 'C' option in their cpoptions they would receive a E10 error on startup of BufExplorer. cpo is now saved, updated and restored. Thanks to Charles E Campbell, Jr. Attempted to make sure there can only be one BufExplorer window open at a time.","3":"Now pressing the <esc> key will quit, just like 'q'. Added folds to hide winmanager configuration. If anyone had the 'C' option in their cpoptions they would receive a E10 error on startup of BufExplorer. cpo is now saved, updated and restored. Thanks to Charles E Campbell, Jr. Attempted to make sure there can only be one BufExplorer window open at a time.","package":"bufexplorer.zip","4":"bufexplorer.zip","src_id":"1376","5":"1376","creation_date":"1036478110","6":"1036478110"},{"0":"42","vim_version":"6.0","1":"6.0","script_version":"6.1.1","2":"6.1.1","version_comment":"Thanks to Brian D. Goodwin for adding toupper to FileNameCmp. This way buffers sorted by name will be in the correct order regardless of case.\r\n","3":"Thanks to Brian D. Goodwin for adding toupper to FileNameCmp. This way buffers sorted by name will be in the correct order regardless of case.\r\n","package":"bufexplorer.zip","4":"bufexplorer.zip","src_id":"724","5":"724","creation_date":"1017306422","6":"1017306422"},{"0":"42","vim_version":"6.0","1":"6.0","script_version":"6.0.16","2":"6.0.16","version_comment":"Thanks to Andre Pang for the original patch\/idea to get bufexplorer to work in insertmode\/modeless mode (evim). Added Initialize and Cleanup autocommands to handle commands that need to be performed when starting or leaving bufexplorer.\r\n","3":"Thanks to Andre Pang for the original patch\/idea to get bufexplorer to work in insertmode\/modeless mode (evim). Added Initialize and Cleanup autocommands to handle commands that need to be performed when starting or leaving bufexplorer.\r\n","package":"bufexplorer.zip","4":"bufexplorer.zip","src_id":"684","5":"684","creation_date":"1016096256","6":"1016096256"},{"0":"42","vim_version":"6.0","1":"6.0","script_version":"6.0.15","2":"6.0.15","version_comment":"Srinath Avadhanulax added a patch for winmanager.vim.","3":"Srinath Avadhanulax added a patch for winmanager.vim.","package":"bufexplorer.zip","4":"bufexplorer.zip","src_id":"617","5":"617","creation_date":"1014183781","6":"1014183781"},{"0":"42","vim_version":"6.0","1":"6.0","script_version":"6.0.14","2":"6.0.14","version_comment":"Fix a yew more bug that I thought I already had fixed. Thanks to Eric Bloodworth for adding 'Open Mode\/Edit in Place'. Added vertical splitting.","3":"Fix a yew more bug that I thought I already had fixed. Thanks to Eric Bloodworth for adding 'Open Mode\/Edit in Place'. Added vertical splitting.","package":"bufexplorer.zip","4":"bufexplorer.zip","src_id":"614","5":"614","creation_date":"1014108186","6":"1014108186"},{"0":"42","vim_version":"6.0","1":"6.0","script_version":"6.0.13","2":"6.0.13","version_comment":"Thanks to Charles E Campbell, Jr. for pointing out some embarrassing typos that I had in the documentation. I guess I need to run the spell checker more :o)","3":"Thanks to Charles E Campbell, Jr. for pointing out some embarrassing typos that I had in the documentation. I guess I need to run the spell checker more :o)","package":"bufexplorer.zip","4":"bufexplorer.zip","src_id":"553","5":"553","creation_date":"1012897683","6":"1012897683"},{"0":"42","vim_version":"6.0","1":"6.0","script_version":"6.0.12","2":"6.0.12","version_comment":"Thanks to Madoka Machitani, for the tip on adding the augroup command around the MRUList autocommands.","3":"Thanks to Madoka Machitani, for the tip on adding the augroup command around the MRUList autocommands.","package":"bufexplorer.zip","4":"bufexplorer.zip","src_id":"543","5":"543","creation_date":"1012822592","6":"1012822592"},{"0":"42","vim_version":"6.0","1":"6.0","script_version":"6.0.11","2":"6.0.11","version_comment":"Fixed bug report by Xiangjiang Ma. '\"=' was being added to the search history which messed up hlsearch.\r\n","3":"Fixed bug report by Xiangjiang Ma. '\"=' was being added to the search history which messed up hlsearch.\r\n","package":"bufexplorer.zip","4":"bufexplorer.zip","src_id":"513","5":"513","creation_date":"1012033807","6":"1012033807"},{"0":"42","vim_version":"6.0","1":"6.0","script_version":"6.0.10","2":"6.0.10","version_comment":"Added the necessary hooks so that the winmanager.vim script could more easily integrate with this script. Now the winmanager.vim script should not have to have it's own version of bufexplorer.vim.\r\nTried to improve performance.\r\nRemember to look at 'help: add-local-help' on how to add the help file into the vim help system.","3":"Added the necessary hooks so that the winmanager.vim script could more easily integrate with this script. Now the winmanager.vim script should not have to have it's own version of bufexplorer.vim.\r\nTried to improve performance.\r\nRemember to look at 'help: add-local-help' on how to add the help file into the vim help system.","package":"bufexplorer.zip","4":"bufexplorer.zip","src_id":"472","5":"472","creation_date":"1011006405","6":"1011006405"},{"0":"42","vim_version":"6.0","1":"6.0","script_version":"6.0.9","2":"6.0.9","version_comment":"Now you can sort the buffer list by most recently used (MRU). Please note that this is now a .zip file. Please unzip in your vimfiles, ~\/.vim or whatever directory you store your vim stuff in. This file contains \\plugin\\bufexplorer.vim and \\doc\\bufexplorer.txt. To add the nifty help to vim look under ':help add-local-help' for more information.","3":"Now you can sort the buffer list by most recently used (MRU). Please note that this is now a .zip file. Please unzip in your vimfiles, ~\/.vim or whatever directory you store your vim stuff in. This file contains \\plugin\\bufexplorer.vim and \\doc\\bufexplorer.txt. To add the nifty help to vim look under ':help add-local-help' for more information.","package":"bufexplorer.zip","4":"bufexplorer.zip","src_id":"427","5":"427","creation_date":"1008572421","6":"1008572421"},{"0":"42","vim_version":"6.0","1":"6.0","script_version":"6.0.8","2":"6.0.8","version_comment":"Was not resetting the showcmd command correctly.\r\nAdded nifty help file.","3":"Was not resetting the showcmd command correctly.\r\nAdded nifty help file.","package":"bufexplorer.zip","4":"bufexplorer.zip","src_id":"393","5":"393","creation_date":"1007358639","6":"1007358639"},{"0":"42","vim_version":"6.0","1":"6.0","script_version":"6.0.7","2":"6.0.7","version_comment":"Thanks to Brett Carlane for some great enhancements. Some are added, some are not, yet. Added highlighting of current and alternate filenames. Added spliting of path\/filename toggle. Reworked ShowBuffers(). Changed my email address.\r\n","3":"Thanks to Brett Carlane for some great enhancements. Some are added, some are not, yet. Added highlighting of current and alternate filenames. Added spliting of path\/filename toggle. Reworked ShowBuffers(). Changed my email address.\r\n","package":"bufexplorer.zip","4":"bufexplorer.zip","src_id":"360","5":"360","creation_date":"1006155072","6":"1006155072"},{"0":"42","vim_version":"6.0","1":"6.0","script_version":"6.0.6","2":"6.0.6","version_comment":"Fixed problem with the SortListing() function failing when there was only one buffer to display.\r\n","3":"Fixed problem with the SortListing() function failing when there was only one buffer to display.\r\n","package":"bufexplorer.zip","4":"bufexplorer.zip","src_id":"154","5":"154","creation_date":"999667909","6":"999667909"},{"0":"42","vim_version":"6.0","1":"6.0","script_version":"6.0.5","2":"6.0.5","version_comment":"Fixed problems reported by David Pascoe, in that you where unable to hit 'd' on a buffer that belonged to a files that nolonger existed and that the 'yank' buffer was being overridden by the help text when the bufexplorer was opened.","3":"Fixed problems reported by David Pascoe, in that you where unable to hit 'd' on a buffer that belonged to a files that nolonger existed and that the 'yank' buffer was being overridden by the help text when the bufexplorer was opened.","package":"bufexplorer.zip","4":"bufexplorer.zip","src_id":"93","5":"93","creation_date":"997422375","6":"997422375"},{"0":"42","vim_version":"6.0","1":"6.0","script_version":"6.0.4","2":"6.0.4","version_comment":"Thanks to Charles Campbell for making this plugin more plugin *compliant*, adding default keymappings of <Leader>be and <Leader>bs as well as fixing the 'w:sortDirLabel not being defined' bug.\r\n","3":"Thanks to Charles Campbell for making this plugin more plugin *compliant*, adding default keymappings of <Leader>be and <Leader>bs as well as fixing the 'w:sortDirLabel not being defined' bug.\r\n","package":"bufexplorer.zip","4":"bufexplorer.zip","src_id":"77","5":"77","creation_date":"996580813","6":"996580813"},{"0":"42","vim_version":"6.0","1":"6.0","script_version":"6.0.3","2":"6.0.3","version_comment":"Added ability to sort buffers by 'buffer number' or 'name' in forward and reverse order.","3":"Added ability to sort buffers by 'buffer number' or 'name' in forward and reverse order.","package":"bufexplorer.zip","4":"bufexplorer.zip","src_id":"72","5":"72","creation_date":"996491223","6":"996491223"},{"0":"42","vim_version":"6.0","1":"6.0","script_version":"6.0.2","2":"6.0.2","version_comment":"Initial upload","3":"Initial upload","package":"bufexplorer.zip","4":"bufexplorer.zip","src_id":"60","5":"60","creation_date":"996054304","6":"996054304"}]},"41":{"script_id":"41","0":"41","script_name":"rcs-menu.vim","1":"rcs-menu.vim","script_type":"utility","2":"utility","summary":"Interface to RCS (Revision Control System)","3":"Interface to RCS (Revision Control System)","description":"rcs-menu.vim is a plugin which allows you to easily interace with the command line versions of rcs, ci, co, rlog and rcsdiff.  If you are running a GUI version of Vim, you will get a new menu in the menu bar for RCS.  This plugin can also be found at http:\/\/lanzarotta.tripod.com\/vim.html.","4":"rcs-menu.vim is a plugin which allows you to easily interace with the command line versions of rcs, ci, co, rlog and rcsdiff.  If you are running a GUI version of Vim, you will get a new menu in the menu bar for RCS.  This plugin can also be found at http:\/\/lanzarotta.tripod.com\/vim.html.","install_details":"Simply put rcs-menu.vim in your plugin directory and restart Vim.","5":"Simply put rcs-menu.vim in your plugin directory and restart Vim.","first_name":"jeff","6":"jeff","last_name":"lanzarotta","7":"lanzarotta","releases":[{"0":"41","vim_version":"6.0","1":"6.0","script_version":"6.0.2","2":"6.0.2","version_comment":"Initial upload","3":"Initial upload","package":"rcs-menu.vim","4":"rcs-menu.vim","src_id":"59","5":"59","creation_date":"996054069","6":"996054069"}]},"40":{"script_id":"40","0":"40","script_name":"DrawIt!","1":"DrawIt!","script_type":"utility","2":"utility","summary":"Ascii drawing plugin: lines, ellipses, arrows, fills, and more!","3":"Ascii drawing plugin: lines, ellipses, arrows, fills, and more!","description":"DrawIt is a plugin which allows one to draw lines left, right, up, down, and along both slants. Optionally one may \"cap\" the lines with arrowheads.  One may change the horizontal, vertical, slant, and crossing characters to whichever characters one wishes.\r\n\r\nIts easy to start and stop DrawIt: use\r\n\r\n   \\di to start DrawIt and\r\n   \\ds to stop  DrawIt.\r\n\r\nThe alpha\/beta version is available at  http:\/\/www.drchip.org\/astronaut\/vim\/index.html#DRAWIT.\r\n\r\nWhen DrawIt has been started you may use the number pad to leave a trail of dashes, vertical bars, etc.  The lines will be expanded as needed to accomodate your drawing.  DrawIt can also draw boxes and ellipses on a blank-filled area (DrawIt can produce these) which can be useful for drawing boxes around comments.\r\n\r\nViart's <drawing.vim> has been merged with the original DrawIt (vimscript#11) (by permission).  Use visual-block selection to specify starting and ending positions and a Bresenham line drawing algorithm will be used to connect the two.  DrC has written an ellipse-drawing Bresenham-style procedure: again, use the visual block selection to specify a box to contain the ellipse and \\e to trigger the ellipse drawing.\r\n\r\nDrawIt incorporates an \"erase\" mode, toggled by the <space> key, that will leave a trail of blanks behind and under the cursor as it is moved by the number pad.  Using the shift-arrow keys, DrawIt will move the cursor, expanding lines and inserting spaces as needed, without changing underlying text.\r\n\r\nDrawIt is now in the vimball format, which is understood by the new Vim 7.0 release.  After decompressing the DrawIt.vba.gz file, edit it with Vim, and then source it (:so %).  The components of DrawIt will then be placed where they belong, based on your Vim's runtimepath.\r\n\r\nDrawIt records many user options that affect DrawIt and all maps that starting DrawIt creates.  When DrawIt is terminated it restores the user's maps and options.  DrawIt's number pad maps will expand the file as necessary to accomodate the drawing, automatically.\r\n\r\nSupported Features\r\n   <left>       move and draw left\r\n   <right>      move and draw right, inserting lines\/space as needed\r\n   <up>         move and draw up, inserting lines\/space as needed\r\n   <down>       move and draw down, inserting lines\/space as needed\r\n   <s-left>     move left\r\n   <s-right>    move right, inserting lines\/space as needed\r\n   <s-up>       move up, inserting lines\/space as needed\r\n   <s-down>     move down, inserting lines\/space as needed\r\n   <space>      toggle into and out of erase mode\r\n   >            draw -> arrow\r\n   <            draw <- arrow\r\n   ^            draw ^  arrow\r\n   v            draw v  arrow\r\n   <pgdn>       replace with a \\, move down and right, and insert a \\\r\n   <end>        replace with a \/, move down and left,  and insert a \/\r\n   <pgup>       replace with a \/, move up   and right, and insert a \/\r\n   <home>       replace with a \\, move up   and left,  and insert a \\\r\n   \\>           draw fat -> arrow\r\n   \\<           draw fat <- arrow\r\n   \\^           draw fat ^  arrow\r\n   \\v           draw fat v  arrow\r\n   \\a           draw arrow based on corners of visual-block\r\n   \\b           draw box using visual-block selected region\r\n   \\e           draw an ellipse inside visual-block\r\n   \\f           fill a figure with some character\r\n   \\h           create a canvas for \\a \\b \\e \\l\r\n   \\l           draw line based on corners of visual block\r\n   \\s           adds spaces to canvas\r\n   <leftmouse>  select visual block\r\n <s-leftmouse>  drag and draw with current brush (register)\r\n   \\ra ... \\rz  replace text with given brush\/register\r\n   \\pa ...      like \\ra ... \\rz, except that blanks are considered\r\n                to be transparent\r\n\r\nThank you for ranking DrawIt!\r\n","4":"DrawIt is a plugin which allows one to draw lines left, right, up, down, and along both slants. Optionally one may \"cap\" the lines with arrowheads.  One may change the horizontal, vertical, slant, and crossing characters to whichever characters one wishes.\r\n\r\nIts easy to start and stop DrawIt: use\r\n\r\n   \\di to start DrawIt and\r\n   \\ds to stop  DrawIt.\r\n\r\nThe alpha\/beta version is available at  http:\/\/www.drchip.org\/astronaut\/vim\/index.html#DRAWIT.\r\n\r\nWhen DrawIt has been started you may use the number pad to leave a trail of dashes, vertical bars, etc.  The lines will be expanded as needed to accomodate your drawing.  DrawIt can also draw boxes and ellipses on a blank-filled area (DrawIt can produce these) which can be useful for drawing boxes around comments.\r\n\r\nViart's <drawing.vim> has been merged with the original DrawIt (vimscript#11) (by permission).  Use visual-block selection to specify starting and ending positions and a Bresenham line drawing algorithm will be used to connect the two.  DrC has written an ellipse-drawing Bresenham-style procedure: again, use the visual block selection to specify a box to contain the ellipse and \\e to trigger the ellipse drawing.\r\n\r\nDrawIt incorporates an \"erase\" mode, toggled by the <space> key, that will leave a trail of blanks behind and under the cursor as it is moved by the number pad.  Using the shift-arrow keys, DrawIt will move the cursor, expanding lines and inserting spaces as needed, without changing underlying text.\r\n\r\nDrawIt is now in the vimball format, which is understood by the new Vim 7.0 release.  After decompressing the DrawIt.vba.gz file, edit it with Vim, and then source it (:so %).  The components of DrawIt will then be placed where they belong, based on your Vim's runtimepath.\r\n\r\nDrawIt records many user options that affect DrawIt and all maps that starting DrawIt creates.  When DrawIt is terminated it restores the user's maps and options.  DrawIt's number pad maps will expand the file as necessary to accomodate the drawing, automatically.\r\n\r\nSupported Features\r\n   <left>       move and draw left\r\n   <right>      move and draw right, inserting lines\/space as needed\r\n   <up>         move and draw up, inserting lines\/space as needed\r\n   <down>       move and draw down, inserting lines\/space as needed\r\n   <s-left>     move left\r\n   <s-right>    move right, inserting lines\/space as needed\r\n   <s-up>       move up, inserting lines\/space as needed\r\n   <s-down>     move down, inserting lines\/space as needed\r\n   <space>      toggle into and out of erase mode\r\n   >            draw -> arrow\r\n   <            draw <- arrow\r\n   ^            draw ^  arrow\r\n   v            draw v  arrow\r\n   <pgdn>       replace with a \\, move down and right, and insert a \\\r\n   <end>        replace with a \/, move down and left,  and insert a \/\r\n   <pgup>       replace with a \/, move up   and right, and insert a \/\r\n   <home>       replace with a \\, move up   and left,  and insert a \\\r\n   \\>           draw fat -> arrow\r\n   \\<           draw fat <- arrow\r\n   \\^           draw fat ^  arrow\r\n   \\v           draw fat v  arrow\r\n   \\a           draw arrow based on corners of visual-block\r\n   \\b           draw box using visual-block selected region\r\n   \\e           draw an ellipse inside visual-block\r\n   \\f           fill a figure with some character\r\n   \\h           create a canvas for \\a \\b \\e \\l\r\n   \\l           draw line based on corners of visual block\r\n   \\s           adds spaces to canvas\r\n   <leftmouse>  select visual block\r\n <s-leftmouse>  drag and draw with current brush (register)\r\n   \\ra ... \\rz  replace text with given brush\/register\r\n   \\pa ...      like \\ra ... \\rz, except that blanks are considered\r\n                to be transparent\r\n\r\nThank you for ranking DrawIt!\r\n","install_details":"DrawIt! is now distributed as a vimball (see :help vimball)\r\n\r\nvim DrawIt.vba.gz\r\n:so %\r\n:q\r\n\r\nand that's all!\r\n\r\n","5":"DrawIt! is now distributed as a vimball (see :help vimball)\r\n\r\nvim DrawIt.vba.gz\r\n:so %\r\n:q\r\n\r\nand that's all!\r\n\r\n","first_name":"Charles","6":"Charles","last_name":"Campbell","7":"Campbell","releases":[{"0":"40","vim_version":"7.3","1":"7.3","script_version":"13","2":"13","version_comment":"improved string length handling for multi-character characters\r\nvarious bug fixes","3":"improved string length handling for multi-character characters\r\nvarious bug fixes","package":"DrawIt.vba.gz","4":"DrawIt.vba.gz","src_id":"21108","5":"21108","creation_date":"1385414918","6":"1385414918"},{"0":"40","vim_version":"7.0","1":"7.0","script_version":"12","2":"12","version_comment":"A few bug fixes","3":"A few bug fixes","package":"DrawIt.vba.gz","4":"DrawIt.vba.gz","src_id":"19631","5":"19631","creation_date":"1363124436","6":"1363124436"},{"0":"40","vim_version":"7.3","1":"7.3","script_version":"11","2":"11","version_comment":"New: utf-8 and cp437 box drawing characters\r\nNew: \"fat\" arrows use utf-8 characters when available\r\nVarious bugfixes\r\n","3":"New: utf-8 and cp437 box drawing characters\r\nNew: \"fat\" arrows use utf-8 characters when available\r\nVarious bugfixes\r\n","package":"DrawIt.vba.gz","4":"DrawIt.vba.gz","src_id":"18154","5":"18154","creation_date":"1340050600","6":"1340050600"},{"0":"40","vim_version":"7.0","1":"7.0","script_version":"10","2":"10","version_comment":"Fixed a bug with text brushes and ctrl-leftmouse.","3":"Fixed a bug with text brushes and ctrl-leftmouse.","package":"DrawIt.vba.gz","4":"DrawIt.vba.gz","src_id":"8798","5":"8798","creation_date":"1213273906","6":"1213273906"},{"0":"40","vim_version":"7.0","1":"7.0","script_version":"9","2":"9","version_comment":"Bugfix: Johann-Guenter Simon fixed a bug with s:DrawErase()","3":"Bugfix: Johann-Guenter Simon fixed a bug with s:DrawErase()","package":"DrawIt.vba.gz","4":"DrawIt.vba.gz","src_id":"7777","5":"7777","creation_date":"1192026407","6":"1192026407"},{"0":"40","vim_version":"7.0","1":"7.0","script_version":"8","2":"8","version_comment":"* Changed \"Holer\" to \"Canvas\" and implemented AutoCanvas (which works real well with set ve=all)\r\n* use ctrl-leftmouse to select visual-blocks\r\n* floods can now be done inside an ellipse\r\n* Extended DrawIt to allow users to specify their ellipse drawing with b:di_ellipse\r\n* DrawIt's maps are now all <buffer> (local) instead of global\r\n* Bug fixe fixed multi-character user map restoration\r\n","3":"* Changed \"Holer\" to \"Canvas\" and implemented AutoCanvas (which works real well with set ve=all)\r\n* use ctrl-leftmouse to select visual-blocks\r\n* floods can now be done inside an ellipse\r\n* Extended DrawIt to allow users to specify their ellipse drawing with b:di_ellipse\r\n* DrawIt's maps are now all <buffer> (local) instead of global\r\n* Bug fixe fixed multi-character user map restoration\r\n","package":"DrawIt.vba.gz","4":"DrawIt.vba.gz","src_id":"7419","5":"7419","creation_date":"1185473782","6":"1185473782"},{"0":"40","vim_version":"7.0","1":"7.0","script_version":"7","2":"7","version_comment":"DrawIt now uses autoload feature of vim 7.0 , so vim7.0 is required!\r\nDrawIt now supports brushes: use visual block to select a brush, then use :SetBrush a (for example).  Blanks are transparent.  Use shift-leftmouse to draw with the current brush.\r\nVarious bugfixes.\r\n","3":"DrawIt now uses autoload feature of vim 7.0 , so vim7.0 is required!\r\nDrawIt now supports brushes: use visual block to select a brush, then use :SetBrush a (for example).  Blanks are transparent.  Use shift-leftmouse to draw with the current brush.\r\nVarious bugfixes.\r\n","package":"DrawIt.vba.gz","4":"DrawIt.vba.gz","src_id":"5550","5":"5550","creation_date":"1144916209","6":"1144916209"},{"0":"40","vim_version":"6.0","1":"6.0","script_version":"02242003","2":"02242003","version_comment":"The latest DrawIt now provides a fill function.\r\n\\f will ask for a character to fill the figure\r\nsurrounding the current cursor location.  Plus\r\nI suggest reading :he drawit-tip for those whose\r\nhome\/pageup\/pagedown\/end keys aren't all working\r\nproperly with DrawIt.\r\n","3":"The latest DrawIt now provides a fill function.\r\n\\f will ask for a character to fill the figure\r\nsurrounding the current cursor location.  Plus\r\nI suggest reading :he drawit-tip for those whose\r\nhome\/pageup\/pagedown\/end keys aren't all working\r\nproperly with DrawIt.\r\n","package":"DrawIt.tar.gz","4":"DrawIt.tar.gz","src_id":"1764","5":"1764","creation_date":"1046072791","6":"1046072791"}]},"39":{"script_id":"39","0":"39","script_name":"matchit.zip","1":"matchit.zip","script_type":"utility","2":"utility","summary":"extended % matching for HTML, LaTeX, and many other languages","3":"extended % matching for HTML, LaTeX, and many other languages","description":"The matchit.vim script allows you to configure % to match more than just\r\nsingle characters.  You can match words and even regular expressions.\r\nAlso, matching treats strings and comments (as recognized by the\r\nsyntax highlighting mechanism) intelligently.\r\nThe default ftplugins include settings for several languages:\r\nAda, ASP with VBS, Csh, DTD, Essbase, Fortran, HTML, JSP\r\n(same as HTML), LaTeX, Lua, Pascal, SGML, Shell, Tcsh, Vim, XML.\r\n(I no longer keep track, so there may be others.)\r\nThe documentation (included in the zip file) explains how to configure\r\nthe script for a new language and how to modify the defaults.\r\n\r\nSince vim 6.0, matchit.vim has been included in the standard vim distribution,\r\nunder the macros\/ directory; the version here may be more recent.\r\n","4":"The matchit.vim script allows you to configure % to match more than just\r\nsingle characters.  You can match words and even regular expressions.\r\nAlso, matching treats strings and comments (as recognized by the\r\nsyntax highlighting mechanism) intelligently.\r\nThe default ftplugins include settings for several languages:\r\nAda, ASP with VBS, Csh, DTD, Essbase, Fortran, HTML, JSP\r\n(same as HTML), LaTeX, Lua, Pascal, SGML, Shell, Tcsh, Vim, XML.\r\n(I no longer keep track, so there may be others.)\r\nThe documentation (included in the zip file) explains how to configure\r\nthe script for a new language and how to modify the defaults.\r\n\r\nSince vim 6.0, matchit.vim has been included in the standard vim distribution,\r\nunder the macros\/ directory; the version here may be more recent.\r\n","install_details":"Vim 5.x:  Make sure to download the correct version (1.0).  Add a line like\r\n\r\n:source path\/to\/matchit.vim\r\n\r\nto your vimrc file.  More details are in matchit.html (included).\r\n\r\nVim 6.x, 7.x:  Download the most recent version.\r\nUnpack the zip file in your personal vim directory (e.g. ~\/.vim on *NIX):\r\nthis will put matchit.vim in your plugin\/ directory and put matchit.txt into\r\nyour doc\/ directory.  Then do\r\n\r\n:helptags ~\/.vim\/doc\r\n\r\nto rebuild the tags file.  For details, read\r\n\r\n:help add-local-help\r\n\r\nMake sure you have a line like\r\n\r\n:filetype plugin on\r\n\r\nin your vimrc file.  This enables filetype plugins, many of which tell\r\nmatchit.vim which matching pairs to use.","5":"Vim 5.x:  Make sure to download the correct version (1.0).  Add a line like\r\n\r\n:source path\/to\/matchit.vim\r\n\r\nto your vimrc file.  More details are in matchit.html (included).\r\n\r\nVim 6.x, 7.x:  Download the most recent version.\r\nUnpack the zip file in your personal vim directory (e.g. ~\/.vim on *NIX):\r\nthis will put matchit.vim in your plugin\/ directory and put matchit.txt into\r\nyour doc\/ directory.  Then do\r\n\r\n:helptags ~\/.vim\/doc\r\n\r\nto rebuild the tags file.  For details, read\r\n\r\n:help add-local-help\r\n\r\nMake sure you have a line like\r\n\r\n:filetype plugin on\r\n\r\nin your vimrc file.  This enables filetype plugins, many of which tell\r\nmatchit.vim which matching pairs to use.","first_name":"Benji","6":"Benji","last_name":"Fisher","7":"Fisher","releases":[{"0":"39","vim_version":"6.0","1":"6.0","script_version":"1.13.2","2":"1.13.2","version_comment":"Another bug fix:  either 1.13 or 1.13.1 broke the behavior of finding a matching construct that starts after the cursor.","3":"Another bug fix:  either 1.13 or 1.13.1 broke the behavior of finding a matching construct that starts after the cursor.","package":"matchit.zip","4":"matchit.zip","src_id":"8196","5":"8196","creation_date":"1201613387","6":"1201613387"},{"0":"39","vim_version":"6.0","1":"6.0","script_version":"1.13.1","2":"1.13.1","version_comment":"bug fix","3":"bug fix","package":"matchit.zip","4":"matchit.zip","src_id":"7637","5":"7637","creation_date":"1189319375","6":"1189319375"},{"0":"39","vim_version":"6.0","1":"6.0","script_version":"1.13","2":"1.13","version_comment":"The script uses its own logic, instead of the default % behavior, if the match comes from the 'matchpairs' option rather than from the b:match_words variable.  This implies that you can get the matchit behavior for strings and comments just by loading the script; you need not define b:match_words at all.","3":"The script uses its own logic, instead of the default % behavior, if the match comes from the 'matchpairs' option rather than from the b:match_words variable.  This implies that you can get the matchit behavior for strings and comments just by loading the script; you need not define b:match_words at all.","package":"matchit.zip","4":"matchit.zip","src_id":"7582","5":"7582","creation_date":"1188400115","6":"1188400115"},{"0":"39","vim_version":"6.0","1":"6.0","script_version":"1.12","2":"1.12","version_comment":"I fixed a bug in the [% and ]% motions:  if b:match_words contained escaped colons or commas ('\\:' or '\\,') then they would be treated incorrectly.","3":"I fixed a bug in the [% and ]% motions:  if b:match_words contained escaped colons or commas ('\\:' or '\\,') then they would be treated incorrectly.","package":"matchit.zip","4":"matchit.zip","src_id":"6332","5":"6332","creation_date":"1161680415","6":"1161680415"},{"0":"39","vim_version":"6.0","1":"6.0","script_version":"1.11","2":"1.11","version_comment":"improved support for multi-byte characters (thanks to Yuheng Xie)","3":"improved support for multi-byte characters (thanks to Yuheng Xie)","package":"matchit.zip","4":"matchit.zip","src_id":"5705","5":"5705","creation_date":"1147720749","6":"1147720749"},{"0":"39","vim_version":"6.0","1":"6.0","script_version":"1.10","2":"1.10","version_comment":"Allow escaped commas and colons to be included in matching patterns.\r\nExample:  to match \"foo:\" with \"foo,\" and \"bar,\" with \"bar:\", try\r\n:let b:match_words = 'foo\\::foo\\,,bar\\,:bar\\:'","3":"Allow escaped commas and colons to be included in matching patterns.\r\nExample:  to match \"foo:\" with \"foo,\" and \"bar,\" with \"bar:\", try\r\n:let b:match_words = 'foo\\::foo\\,,bar\\,:bar\\:'","package":"matchit.zip","4":"matchit.zip","src_id":"5330","5":"5330","creation_date":"1140941190","6":"1140941190"},{"0":"39","vim_version":"6.0","1":"6.0","script_version":"1.9","2":"1.9","version_comment":"improved fix for the [% bug (see previous version comment)\r\nAvoid screen jumps when 'nowrap' is set (reported by Charles Campbell).","3":"improved fix for the [% bug (see previous version comment)\r\nAvoid screen jumps when 'nowrap' is set (reported by Charles Campbell).","package":"matchit.zip","4":"matchit.zip","src_id":"3026","5":"3026","creation_date":"1084609001","6":"1084609001"},{"0":"39","vim_version":"6.0","1":"6.0","script_version":"1.8","2":"1.8","version_comment":"Bug fix for [% and ]% (Dany St-Amant)\r\nMinor change in :vmap for a%\r\nUpdated documentation\r\n\r\nThis version should be included with the standard distribution of vim 6.3 (in $VIMRUNTIME\/macros)","3":"Bug fix for [% and ]% (Dany St-Amant)\r\nMinor change in :vmap for a%\r\nUpdated documentation\r\n\r\nThis version should be included with the standard distribution of vim 6.3 (in $VIMRUNTIME\/macros)","package":"matchit.zip","4":"matchit.zip","src_id":"3015","5":"3015","creation_date":"1084349516","6":"1084349516"},{"0":"39","vim_version":"6.0","1":"6.0","script_version":"1.7","2":"1.7","version_comment":"This version of matchit.vim requires vim 6.x (maybe 6.1 or later).\r\nThis may be more recent than the version in the standard vim\r\ndistribution, under $VIMRUNTIME\/macros\/matchit.vim .\r\nThe zip file contains matchit.vim (the script) and matchit.txt\r\n(the documentation).","3":"This version of matchit.vim requires vim 6.x (maybe 6.1 or later).\r\nThis may be more recent than the version in the standard vim\r\ndistribution, under $VIMRUNTIME\/macros\/matchit.vim .\r\nThe zip file contains matchit.vim (the script) and matchit.txt\r\n(the documentation).","package":"matchit.zip","4":"matchit.zip","src_id":"1197","5":"1197","creation_date":"1031487870","6":"1031487870"},{"0":"39","vim_version":"5.7","1":"5.7","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"matchit.zip","4":"matchit.zip","src_id":"56","5":"56","creation_date":"995892386","6":"995892386"}]},"38":{"script_id":"38","0":"38","script_name":"dbhelper.tgz","1":"dbhelper.tgz","script_type":"utility","2":"utility","summary":"Helper for Writing DocBook Documents","3":"Helper for Writing DocBook Documents","description":"This script is an adaption of Dan York's (dyork at lodestar2.com) VIMRC file that acts as a helper in making docbook documents.  This script uses abbreviations in the form of \",<chracter>\" to trigger automatic insertion of docbook tags.  I have added a few new abbreviations to the original exhaustive list from Dan York's original list.  I have further extended it to add compilation of the document from within VIM itself to generate the output in your most favourite format by using VIM's inbuilt \"make\" facility.    Please send your inputs and comments to vivekv at users.sourceforge.net\t","4":"This script is an adaption of Dan York's (dyork at lodestar2.com) VIMRC file that acts as a helper in making docbook documents.  This script uses abbreviations in the form of \",<chracter>\" to trigger automatic insertion of docbook tags.  I have added a few new abbreviations to the original exhaustive list from Dan York's original list.  I have further extended it to add compilation of the document from within VIM itself to generate the output in your most favourite format by using VIM's inbuilt \"make\" facility.    Please send your inputs and comments to vivekv at users.sourceforge.net\t","install_details":"Copy dbhelper.vim to the directory where you store all your VIM scripts.  Then in the .vimrc file, include the line source <directory>\/dbhelper.vim.  Then edit the file mkrtf.ksh and edit the line which invokes openjade, configuring it to compile according to your preferences and your system paths.  Thats it!  \r\nIn VIM, type :make to compile.  VIM will automatically highlight errors in the document after compilation.","5":"Copy dbhelper.vim to the directory where you store all your VIM scripts.  Then in the .vimrc file, include the line source <directory>\/dbhelper.vim.  Then edit the file mkrtf.ksh and edit the line which invokes openjade, configuring it to compile according to your preferences and your system paths.  Thats it!  \r\nIn VIM, type :make to compile.  VIM will automatically highlight errors in the document after compilation.","first_name":"vivek","6":"vivek","last_name":"Venugopalan","7":"Venugopalan","releases":[{"0":"38","vim_version":"5.7","1":"5.7","script_version":"0.2","2":"0.2","version_comment":"Uploaded the proper file.  Last version was bogus.  Sorry","3":"Uploaded the proper file.  Last version was bogus.  Sorry","package":"dbhelper.tgz","4":"dbhelper.tgz","src_id":"110","5":"110","creation_date":"997926059","6":"997926059"},{"0":"38","vim_version":"5.7","1":"5.7","script_version":"0.1","2":"0.1","version_comment":"Added support for Article and FAQs","3":"Added support for Article and FAQs","package":"dbhelper.tgz","4":"dbhelper.tgz","src_id":"55","5":"55","creation_date":"995826698","6":"995826698"},{"0":"38","vim_version":"6.0","1":"6.0","script_version":"0.0","2":"0.0","version_comment":"Initial upload","3":"Initial upload","package":"dbhelper.tgz","4":"dbhelper.tgz","src_id":"54","5":"54","creation_date":"995599991","6":"995599991"}]},"37":{"script_id":"37","0":"37","script_name":"vimvccmd.zip","1":"vimvccmd.zip","script_type":"utility","2":"utility","summary":"patch for vim to ","3":"patch for vim to ","description":"I know that this isn't a macro and I haven't used it in a while but I always have people emailing me about it so I figured I'd try putting it up here.\r\nThe header file has instructions for adding it to the vim project.  Anyone is more than welcome to pick\/clean this up.  Usage is\r\nstraight forward and there is latent ( read: not working ) support for setting breakpoints from vim.  \r\nI wrote this a while ago so it's not a stellar example of using ATL etc.\r\n\r\nUsage:  :vc <cmd>\r\nwhere <cmd> is any exported command in Visual Studio.  See the keybindings to see all of the different commands.\r\n\r\nIt's also available at my web page as well as other vim stuff\r\nhttp:\/\/www.briansturk.com\/vim.html\r\n\r\n","4":"I know that this isn't a macro and I haven't used it in a while but I always have people emailing me about it so I figured I'd try putting it up here.\r\nThe header file has instructions for adding it to the vim project.  Anyone is more than welcome to pick\/clean this up.  Usage is\r\nstraight forward and there is latent ( read: not working ) support for setting breakpoints from vim.  \r\nI wrote this a while ago so it's not a stellar example of using ATL etc.\r\n\r\nUsage:  :vc <cmd>\r\nwhere <cmd> is any exported command in Visual Studio.  See the keybindings to see all of the different commands.\r\n\r\nIt's also available at my web page as well as other vim stuff\r\nhttp:\/\/www.briansturk.com\/vim.html\r\n\r\n","install_details":"See the header file","5":"See the header file","first_name":"brian","6":"brian","last_name":"sturk","7":"sturk","releases":[{"0":"37","vim_version":"5.7","1":"5.7","script_version":"","2":"","version_comment":"Initial upload","3":"Initial upload","package":"vimvccmd.zip","4":"vimvccmd.zip","src_id":"53","5":"53","creation_date":"995499451","6":"995499451"}]},"36":{"script_id":"36","0":"36","script_name":"jbean.vim","1":"jbean.vim","script_type":"utility","2":"utility","summary":"Completion of Get\/Set method","3":"Completion of Get\/Set method","description":"This is result of this script.\r\nIf you modified _vimrc, you'll get this with ALT-B.\r\n\r\n\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\r\n\r\nprivate String name;\r\n\r\npublic String getName()\r\n{\r\nreturn this.name;\r\n}\r\npublic void setName(String name)\r\n{\r\nthis.name = name;\r\n}","4":"This is result of this script.\r\nIf you modified _vimrc, you'll get this with ALT-B.\r\n\r\n\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\r\n\r\nprivate String name;\r\n\r\npublic String getName()\r\n{\r\nreturn this.name;\r\n}\r\npublic void setName(String name)\r\n{\r\nthis.name = name;\r\n}","install_details":"put this in macros directory. and modify _vimrc to load this command\r\n\r\nin _vimrc\r\n\r\nautocmd FileType java source $VIM\/macros\/jbean.vim\r\nautocmd FileType java map <M-b> :call MakeBeanFramework()<CR>","5":"put this in macros directory. and modify _vimrc to load this command\r\n\r\nin _vimrc\r\n\r\nautocmd FileType java source $VIM\/macros\/jbean.vim\r\nautocmd FileType java map <M-b> :call MakeBeanFramework()<CR>","first_name":"sunghyun","6":"sunghyun","last_name":"kim","7":"kim","releases":[{"0":"36","vim_version":"5.7","1":"5.7","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"jbean.vim","4":"jbean.vim","src_id":"52","5":"52","creation_date":"995466652","6":"995466652"}]},"35":{"script_id":"35","0":"35","script_name":"javabean.vim","1":"javabean.vim","script_type":"utility","2":"utility","summary":"Adds property getters and setters","3":"Adds property getters and setters","description":"Given a number of Java properties in a basic format, this will generate the getters and setters for them; for example, given:\r\n\r\nString myString\r\nint myInt\r\n\r\nyou will get:\r\n\r\nprotected String m_myString;\r\nprotected int m_myInt;\r\n\r\npublic void setMyString( String val )\r\n{\r\n  m_myString = val;\r\n}\r\n\r\npublic String getMyString()\r\n{\r\n  return m_myString;\r\n}\r\n\r\npublic void setMyInt( int val )\r\n{\r\n  m_myInt = val;\r\n}\r\n\r\npublic int getMyInt()\r\n{\r\n  return m_myInt;\r\n}\r\n\r\nVersion 2.0:\r\n\r\nAdded getters and setters for array variables; for example:\r\n\r\nString[] names\r\n\r\nresults in:\r\n\r\nprotected String[] m_names;\r\n\r\npublic void setNames( String[] val )\r\n{\r\n    m_names = val;\r\n}\r\n\r\npublic String[] getNames()\r\n{\r\n    return m_names;\r\n}\r\n\r\npublic void setNames( String val, int index )\r\n{\r\n    m_names[ index ] = val;\r\n}\r\n\r\npublic String getNames( int index )\r\n{\r\n    return m_names[ index ];\r\n}\r\n\r\nVersion 2.5:\r\n\r\nAdded a new variable (g:javabean_generateArrayAccessors--defaults to 1) to control whether or not to generate array index-based getters and setters.\r\n\r\nAllowed the specification of the three configuration variables in the Vimrc instead of having to modify this file; the variables and their default values, again, are:\r\n\r\ng:javabean_scope = \"protected\"\r\n\r\ng:javabean_beanPrefix = \"m_\"\r\n\r\ng:javabean_generateArrayAccessors = 1\r\n","4":"Given a number of Java properties in a basic format, this will generate the getters and setters for them; for example, given:\r\n\r\nString myString\r\nint myInt\r\n\r\nyou will get:\r\n\r\nprotected String m_myString;\r\nprotected int m_myInt;\r\n\r\npublic void setMyString( String val )\r\n{\r\n  m_myString = val;\r\n}\r\n\r\npublic String getMyString()\r\n{\r\n  return m_myString;\r\n}\r\n\r\npublic void setMyInt( int val )\r\n{\r\n  m_myInt = val;\r\n}\r\n\r\npublic int getMyInt()\r\n{\r\n  return m_myInt;\r\n}\r\n\r\nVersion 2.0:\r\n\r\nAdded getters and setters for array variables; for example:\r\n\r\nString[] names\r\n\r\nresults in:\r\n\r\nprotected String[] m_names;\r\n\r\npublic void setNames( String[] val )\r\n{\r\n    m_names = val;\r\n}\r\n\r\npublic String[] getNames()\r\n{\r\n    return m_names;\r\n}\r\n\r\npublic void setNames( String val, int index )\r\n{\r\n    m_names[ index ] = val;\r\n}\r\n\r\npublic String getNames( int index )\r\n{\r\n    return m_names[ index ];\r\n}\r\n\r\nVersion 2.5:\r\n\r\nAdded a new variable (g:javabean_generateArrayAccessors--defaults to 1) to control whether or not to generate array index-based getters and setters.\r\n\r\nAllowed the specification of the three configuration variables in the Vimrc instead of having to modify this file; the variables and their default values, again, are:\r\n\r\ng:javabean_scope = \"protected\"\r\n\r\ng:javabean_beanPrefix = \"m_\"\r\n\r\ng:javabean_generateArrayAccessors = 1\r\n","install_details":"Just pop it into your plugin directory.  Can set g:javabean_scope or b:javabean_scope if \\\\\\'protected\\\\\\' isn\\\\\\'t what you use.","5":"Just pop it into your plugin directory.  Can set g:javabean_scope or b:javabean_scope if \\\\\\'protected\\\\\\' isn\\\\\\'t what you use.","first_name":"Salman","6":"Salman","last_name":"Halim","7":"Halim","releases":[{"0":"35","vim_version":"7.0","1":"7.0","script_version":"2.5","2":"2.5","version_comment":"Added a new variable (g:javabean_generateArrayAccessors--defaults to 1) to control whether or not to generate array index-based getters and setters.\r\n\r\nAllowed the specification of the three configuration variables in the Vimrc instead of having to modify this file.","3":"Added a new variable (g:javabean_generateArrayAccessors--defaults to 1) to control whether or not to generate array index-based getters and setters.\r\n\r\nAllowed the specification of the three configuration variables in the Vimrc instead of having to modify this file.","package":"javabean.vim","4":"javabean.vim","src_id":"15474","5":"15474","creation_date":"1303153217","6":"1303153217"},{"0":"35","vim_version":"7.0","1":"7.0","script_version":"2.0","2":"2.0","version_comment":"Added support for array variables to get them by index.","3":"Added support for array variables to get them by index.","package":"javabean.vim","4":"javabean.vim","src_id":"15460","5":"15460","creation_date":"1302985795","6":"1302985795"},{"0":"35","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"javabean.vim","4":"javabean.vim","src_id":"51","5":"51","creation_date":"995465568","6":"995465568"}]},"34":{"script_id":"34","0":"34","script_name":"oravim.txt","1":"oravim.txt","script_type":"utility","2":"utility","summary":"SQL*Plus without SQL*Plus","3":"SQL*Plus without SQL*Plus","description":"This script allows you to have a SQLWorksheet-type interface to Oracle. Similar to Jeremy Collins\\' script (vimtip #33), and actually the idea was based on his. It, too, requires that TCL is built in to Vim, and also has a few other requirements: links and a version of SQL*Plus that supports HTML output. \r\n\r\n     The usage is quite a bit different, though. \r\n\r\n     Start by simply editing a file in vim, and move your cursor to a SQL statement. You can visually select it or not, it doesn\\'t matter as long as there is a blank line before and after. Then, based on these keybindings, hit <C-k> and your statement will be executed, formatted, and popped up in a split     window below. To run another statement, move to another one and hit <C-k> again. It will replace the bottom window with the new results. \r\n\r\nMore detail (and latest versions) at http:\/\/oravim.dashf.com\/","4":"This script allows you to have a SQLWorksheet-type interface to Oracle. Similar to Jeremy Collins\\' script (vimtip #33), and actually the idea was based on his. It, too, requires that TCL is built in to Vim, and also has a few other requirements: links and a version of SQL*Plus that supports HTML output. \r\n\r\n     The usage is quite a bit different, though. \r\n\r\n     Start by simply editing a file in vim, and move your cursor to a SQL statement. You can visually select it or not, it doesn\\'t matter as long as there is a blank line before and after. Then, based on these keybindings, hit <C-k> and your statement will be executed, formatted, and popped up in a split     window below. To run another statement, move to another one and hit <C-k> again. It will replace the bottom window with the new results. \r\n\r\nMore detail (and latest versions) at http:\/\/oravim.dashf.com\/","install_details":"see oravim.txt for install details","5":"see oravim.txt for install details","first_name":"Lee","6":"Lee","last_name":"Teague","7":"Teague","releases":[{"0":"34","vim_version":"6.0","1":"6.0","script_version":"0.0.0.1","2":"0.0.0.1","version_comment":"Initial upload","3":"Initial upload","package":"oravim.txt","4":"oravim.txt","src_id":"48","5":"48","creation_date":"995288728","6":"995288728"}]},"33":{"script_id":"33","0":"33","script_name":"vimrc.tcl","1":"vimrc.tcl","script_type":"utility","2":"utility","summary":"Adds a SQLWorksheet type interface to Oracle SQL*Plus","3":"Adds a SQLWorksheet type interface to Oracle SQL*Plus","description":"This small hack requires Tcl to be compiled into your\r\ncopy of Vim.\r\n\r\nThe default settings will allow this hack to work on\r\nthe default SQL*Plus temp file, afiedt.buf, only.\r\n\r\nTo use simply highlight the query you would like to\r\nrun and press Enter.  You should drop back down to\r\nSQL*Plus.  Do the usual '\/' and your good to go.\r\n\r\nHave not tried this hack with PL\/SQL or multiple\r\nQuery's but I cannot see why it won't work, or why it\r\nwould for that matter.\r\n\r\nBUGS\r\n----\r\n1) :wq causes an error message about writing the file.\r\n   Safe to ignore but would be nice to get rid of this.\r\n\r\n2) No checks to make sure you have highlighted a valid\r\n   Query.  Hence all hell breaks loose if you don't.\r\n\r\n3) You *HAVE* to have a trailing ';' on your Query for\r\n   this hack to work.  Would be nice if you didn't have\r\n   to have that.  Would also be nice if you could run\r\n   a group of statements.\r\n","4":"This small hack requires Tcl to be compiled into your\r\ncopy of Vim.\r\n\r\nThe default settings will allow this hack to work on\r\nthe default SQL*Plus temp file, afiedt.buf, only.\r\n\r\nTo use simply highlight the query you would like to\r\nrun and press Enter.  You should drop back down to\r\nSQL*Plus.  Do the usual '\/' and your good to go.\r\n\r\nHave not tried this hack with PL\/SQL or multiple\r\nQuery's but I cannot see why it won't work, or why it\r\nwould for that matter.\r\n\r\nBUGS\r\n----\r\n1) :wq causes an error message about writing the file.\r\n   Safe to ignore but would be nice to get rid of this.\r\n\r\n2) No checks to make sure you have highlighted a valid\r\n   Query.  Hence all hell breaks loose if you don't.\r\n\r\n3) You *HAVE* to have a trailing ';' on your Query for\r\n   this hack to work.  Would be nice if you didn't have\r\n   to have that.  Would also be nice if you could run\r\n   a group of statements.\r\n","install_details":"Copy the script to ~\/.vimrc.tcl then add this to your ~\/.vimrc\r\n\r\nau BufNewFile,BufRead afiedt.buf tc sqlplus_reload\r\nau BufNewFile,BufRead afiedt.buf set ft=sql\r\nau VimLeave           afiedt.buf tc sqlplus_force_save\r\nmap  <F11> :tc sqlplus_force_save<cr>\r\nvmap ^M    :tc sqlplus<cr>\r\n\r\nif has(\"tcl\")\r\n  tclfile ~\/.vimrc.tcl\r\nendif\r\n","5":"Copy the script to ~\/.vimrc.tcl then add this to your ~\/.vimrc\r\n\r\nau BufNewFile,BufRead afiedt.buf tc sqlplus_reload\r\nau BufNewFile,BufRead afiedt.buf set ft=sql\r\nau VimLeave           afiedt.buf tc sqlplus_force_save\r\nmap  <F11> :tc sqlplus_force_save<cr>\r\nvmap ^M    :tc sqlplus<cr>\r\n\r\nif has(\"tcl\")\r\n  tclfile ~\/.vimrc.tcl\r\nendif\r\n","first_name":"Jeremy","6":"Jeremy","last_name":"Collins","7":"Collins","releases":[{"0":"33","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"vimrc.tcl","4":"vimrc.tcl","src_id":"46","5":"46","creation_date":"994997158","6":"994997158"}]},"31":{"script_id":"31","0":"31","script_name":"a.vim","1":"a.vim","script_type":"utility","2":"utility","summary":"Alternate Files quickly (.c --> .h etc)","3":"Alternate Files quickly (.c --> .h etc)","description":"A few of quick commands to swtich between source files and header files quickly.\r\n\r\n:A switches to the header file corresponding to the current file being edited (or vise versa)\r\n:AS splits and switches\r\n:AV vertical splits and switches\r\n:AT new tab and switches\r\n:AN cycles through matches\r\n:IH switches to file under cursor\r\n:IHS splits and switches\r\n:IHV vertical splits and switches\r\n:IHT new tab and switches\r\n:IHN cycles through matches\r\n<Leader>ih switches to file under cursor\r\n<Leader>is switches to the alternate file of file under cursor (e.g. on  <foo.h> switches to foo.cpp)\r\n<Leader>ihn cycles through matches\r\n\r\nE.g. if you are editing foo.c and need to edit foo.h simply execute :A and you will be editting foo.h, to switch back to foo.c execute :A again. \r\n\r\nCan be configured to support a variety of languages. Builtin support for C, C++ and ADA95","4":"A few of quick commands to swtich between source files and header files quickly.\r\n\r\n:A switches to the header file corresponding to the current file being edited (or vise versa)\r\n:AS splits and switches\r\n:AV vertical splits and switches\r\n:AT new tab and switches\r\n:AN cycles through matches\r\n:IH switches to file under cursor\r\n:IHS splits and switches\r\n:IHV vertical splits and switches\r\n:IHT new tab and switches\r\n:IHN cycles through matches\r\n<Leader>ih switches to file under cursor\r\n<Leader>is switches to the alternate file of file under cursor (e.g. on  <foo.h> switches to foo.cpp)\r\n<Leader>ihn cycles through matches\r\n\r\nE.g. if you are editing foo.c and need to edit foo.h simply execute :A and you will be editting foo.h, to switch back to foo.c execute :A again. \r\n\r\nCan be configured to support a variety of languages. Builtin support for C, C++ and ADA95","install_details":"Drop a.vim into your favorite plugin directory or source the script from your .vimrc file\r\nDrop alternate.txt into you doc directory and run helptags","5":"Drop a.vim into your favorite plugin directory or source the script from your .vimrc file\r\nDrop alternate.txt into you doc directory and run helptags","first_name":"Mike","6":"Mike","last_name":"Sharpe","7":"Sharpe","releases":[{"0":"31","vim_version":"7.0","1":"7.0","script_version":"2.18","2":"2.18","version_comment":"Recent versions since 2.16 broke user defined alternate specifications. This patch fixes that.","3":"Recent versions since 2.16 broke user defined alternate specifications. This patch fixes that.","package":"a.vim","4":"a.vim","src_id":"7218","5":"7218","creation_date":"1181235659","6":"1181235659"},{"0":"31","vim_version":"7.0","1":"7.0","script_version":"2.17","2":"2.17","version_comment":"Fix a bug were spaces in filenames and\/or directory names would prevent the alternate file being openned. Thanks to Nathan Stien (for the bug report and patch) and Soeren Sonnenburg (for the bug report).","3":"Fix a bug were spaces in filenames and\/or directory names would prevent the alternate file being openned. Thanks to Nathan Stien (for the bug report and patch) and Soeren Sonnenburg (for the bug report).","package":"a.vim","4":"a.vim","src_id":"7162","5":"7162","creation_date":"1179952286","6":"1179952286"},{"0":"31","vim_version":"7.0","1":"7.0","script_version":"2.16","2":"2.16","version_comment":"Recent patches broke the script in some area, mainly in the area of file extensions which contain a dot...e.g. aspx.cs. Switched to using a dictionary instead of the curly brace variable things.","3":"Recent patches broke the script in some area, mainly in the area of file extensions which contain a dot...e.g. aspx.cs. Switched to using a dictionary instead of the curly brace variable things.","package":"a.vim","4":"a.vim","src_id":"6886","5":"6886","creation_date":"1174075287","6":"1174075287"},{"0":"31","vim_version":"7.0","1":"7.0","script_version":"2.15 doc","2":"2.15 doc","version_comment":"Docs for 2.15","3":"Docs for 2.15","package":"alternate.txt","4":"alternate.txt","src_id":"6347","5":"6347","creation_date":"1161987825","6":"1161987825"},{"0":"31","vim_version":"7.0","1":"7.0","script_version":"2.15","2":"2.15","version_comment":"Initial support for jumping to files under the cursor. New commands IH, IHS, IHV, IHT and IHN. Added sample macros for jumping to the source file corresponding to the header file under the cursor (e.g. jumping on #include <myfile.h> will find myfile.cpp).\r\n\r\nSee documentation for more details.","3":"Initial support for jumping to files under the cursor. New commands IH, IHS, IHV, IHT and IHN. Added sample macros for jumping to the source file corresponding to the header file under the cursor (e.g. jumping on #include <myfile.h> will find myfile.cpp).\r\n\r\nSee documentation for more details.","package":"a.vim","4":"a.vim","src_id":"6346","5":"6346","creation_date":"1161986403","6":"1161986403"},{"0":"31","vim_version":"7.0","1":"7.0","script_version":"2.14","2":"2.14","version_comment":"Added new :AN command which cycles through all matches after switching to a new file. E.g. vi a.c, :A switches to a.h, :AN might switch to a.hpp if a.h and a.hpp exist. Will only likely be an issue in a big project with with same named source\/header files around the place. Will likely only be an issue if you are using the search path and regex features of a.vim.","3":"Added new :AN command which cycles through all matches after switching to a new file. E.g. vi a.c, :A switches to a.h, :AN might switch to a.hpp if a.h and a.hpp exist. Will only likely be an issue in a big project with with same named source\/header files around the place. Will likely only be an issue if you are using the search path and regex features of a.vim.","package":"a.vim","4":"a.vim","src_id":"5698","5":"5698","creation_date":"1147640379","6":"1147640379"},{"0":"31","vim_version":"7.0","1":"7.0","script_version":"2.14 doc","2":"2.14 doc","version_comment":"Documentation for a.vim v2.14. Drop it in your doc directory and run helptags.","3":"Documentation for a.vim v2.14. Drop it in your doc directory and run helptags.","package":"alternate.txt","4":"alternate.txt","src_id":"5697","5":"5697","creation_date":"1147640199","6":"1147640199"},{"0":"31","vim_version":"7.0","1":"7.0","script_version":"2.13","2":"2.13","version_comment":"Added new \"AT\" command which finds the alternate file and opens in a new tab. Similarly to the \"A\" and \"AS\" commands, if the buffer is already open it simply switches to that buffer in the corresponding tab\/window. This script will only work with VIM7 from this version forward.","3":"Added new \"AT\" command which finds the alternate file and opens in a new tab. Similarly to the \"A\" and \"AS\" commands, if the buffer is already open it simply switches to that buffer in the corresponding tab\/window. This script will only work with VIM7 from this version forward.","package":"a.vim","4":"a.vim","src_id":"5653","5":"5653","creation_date":"1147013069","6":"1147013069"},{"0":"31","vim_version":"6.0","1":"6.0","script_version":"2.12","2":"2.12","version_comment":"Added alternate mappings for OCaml. Nothing more. No reason to upgrade...unless you use OCaml.","3":"Added alternate mappings for OCaml. Nothing more. No reason to upgrade...unless you use OCaml.","package":"a.vim","4":"a.vim","src_id":"4154","5":"4154","creation_date":"1113289516","6":"1113289516"},{"0":"31","vim_version":"6.0","1":"6.0","script_version":"2.11a","2":"2.11a","version_comment":"Fix a minor bug when adding alternate extensions. Thanks ilya.","3":"Fix a minor bug when adding alternate extensions. Thanks ilya.","package":"a.vim","4":"a.vim","src_id":"3563","5":"3563","creation_date":"1098215554","6":"1098215554"},{"0":"31","vim_version":"6.0","1":"6.0","script_version":"2.11","2":"2.11","version_comment":"Fix some bugs which have recently crept in. I gave this some regression testing...so I hope all are fixed now. Mot notably, vim foo\/a.c would not alternate to foo\/a.h. Not sure how that broke...but it is fixed now. Other features still appear to work. Let me know if there are issues.","3":"Fix some bugs which have recently crept in. I gave this some regression testing...so I hope all are fixed now. Mot notably, vim foo\/a.c would not alternate to foo\/a.h. Not sure how that broke...but it is fixed now. Other features still appear to work. Let me know if there are issues.","package":"a.vim","4":"a.vim","src_id":"3479","5":"3479","creation_date":"1096007657","6":"1096007657"},{"0":"31","vim_version":"6.0","1":"6.0","script_version":"2.10","2":"2.10","version_comment":"Added a new variable (g:alternateNoDefaultAlternate) which can be set in the .vimrc\/_vimrc file to prevent a.vim from creating new files. This is useful when it is not desired to have a.vim to alternate to the default alternation for a particular extension. E.g. if a.c is being editted and a.h does not exist anywhere and :A is done then if g:alternateNoDefaultAlternate is non-zero a.h will not be created. By default the value of g:alternateNoDefaultAlternate is 0 to maintain existing behaviour.","3":"Added a new variable (g:alternateNoDefaultAlternate) which can be set in the .vimrc\/_vimrc file to prevent a.vim from creating new files. This is useful when it is not desired to have a.vim to alternate to the default alternation for a particular extension. E.g. if a.c is being editted and a.h does not exist anywhere and :A is done then if g:alternateNoDefaultAlternate is non-zero a.h will not be created. By default the value of g:alternateNoDefaultAlternate is 0 to maintain existing behaviour.","package":"a.vim","4":"a.vim","src_id":"3455","5":"3455","creation_date":"1095273596","6":"1095273596"},{"0":"31","vim_version":"6.0","1":"6.0","script_version":"2.9","2":"2.9","version_comment":"Allow the extension of a file to be more than the text after the last dot. E.g. adding settings like\r\n\r\nlet g:alternateExtensions_{'aspx'} = \"aspx.cs,aspx.CS\"\r\nlet g:alternateExtensions_{'aspx.cs'} = \"aspx,ASPX\"\r\n\r\nwill allow a.vim to alternate between foo.aspx and foo.aspx.cs and vice versa. Previous versions would not accept .aspx.cs as an exstension. This version is ok with that.","3":"Allow the extension of a file to be more than the text after the last dot. E.g. adding settings like\r\n\r\nlet g:alternateExtensions_{'aspx'} = \"aspx.cs,aspx.CS\"\r\nlet g:alternateExtensions_{'aspx.cs'} = \"aspx,ASPX\"\r\n\r\nwill allow a.vim to alternate between foo.aspx and foo.aspx.cs and vice versa. Previous versions would not accept .aspx.cs as an exstension. This version is ok with that.","package":"a.vim","4":"a.vim","src_id":"3439","5":"3439","creation_date":"1094797703","6":"1094797703"},{"0":"31","vim_version":"6.0","1":"6.0","script_version":"2.8","2":"2.8","version_comment":"[CORRECTION]More enhancements from Bindu Wavell. A new search path type \r\nof \"reg:\" wasadded. This version allows alternation of files based on regxes. E.g.\r\n\"reg:\/inc\/src\/g\/\" will replace every instance of 'inc' with 'src' in the source\r\nfile path. This is useful for alternating between \/some\/path\/inc\/project\/foo.h\r\nto \/some\/path\/src\/project\/foo.c. Similarly \"reg:\/src\/inc\/g\/\" is the opposite\r\nalternation. See the comments for ExpandAlternatePath() for more information.\r\nSoon I will produce some formal documentation for this...until then the script\r\nis reasonably well commented.","3":"[CORRECTION]More enhancements from Bindu Wavell. A new search path type \r\nof \"reg:\" wasadded. This version allows alternation of files based on regxes. E.g.\r\n\"reg:\/inc\/src\/g\/\" will replace every instance of 'inc' with 'src' in the source\r\nfile path. This is useful for alternating between \/some\/path\/inc\/project\/foo.h\r\nto \/some\/path\/src\/project\/foo.c. Similarly \"reg:\/src\/inc\/g\/\" is the opposite\r\nalternation. See the comments for ExpandAlternatePath() for more information.\r\nSoon I will produce some formal documentation for this...until then the script\r\nis reasonably well commented.","package":"a.vim","4":"a.vim","src_id":"3200","5":"3200","creation_date":"1088665075","6":"1088665075"},{"0":"31","vim_version":"6.0","1":"6.0","script_version":"2.7","2":"2.7","version_comment":"Reworked all the logic for finding alternate files. The files in memory are prefered to files on disk now too. When there are multiple matches for a file found the file in memory is favour, files in the current directory are favoured over files on the path. Hopefully this fixes the inconsistencies in previous versions. Hopefully everything still works too.","3":"Reworked all the logic for finding alternate files. The files in memory are prefered to files on disk now too. When there are multiple matches for a file found the file in memory is favour, files in the current directory are favoured over files on the path. Hopefully this fixes the inconsistencies in previous versions. Hopefully everything still works too.","package":"a.vim","4":"a.vim","src_id":"3028","5":"3028","creation_date":"1084720910","6":"1084720910"},{"0":"31","vim_version":"6.0","1":"6.0","script_version":"2.6a","2":"2.6a","version_comment":"Remove reference to Decho which was accidentally left in after previous debuging. Sorry all.","3":"Remove reference to Decho which was accidentally left in after previous debuging. Sorry all.","package":"a.vim","4":"a.vim","src_id":"2833","5":"2833","creation_date":"1079256319","6":"1079256319"},{"0":"31","vim_version":"6.0","1":"6.0","script_version":"2.6","2":"2.6","version_comment":"Implemented a fix from Matt Perry, vi test.cc junktest.h and the :A would alternate to junktest.h and not test.h. Also some minor clean up of the directory search code. \r\n","3":"Implemented a fix from Matt Perry, vi test.cc junktest.h and the :A would alternate to junktest.h and not test.h. Also some minor clean up of the directory search code. \r\n","package":"a.vim","4":"a.vim","src_id":"2830","5":"2830","creation_date":"1079168831","6":"1079168831"},{"0":"31","vim_version":"6.0","1":"6.0","script_version":"2.5","2":"2.5","version_comment":"Fixed an inconsistency. In 2.4 :A would always switch to the alternate file, regardless of whether unsaved changes were in the current file. In some cases it was possible to lose changes. This update changes :A back to 2.3 behaviour, but with a nicer error message, and provides support for a :A! command which will force the switch. This seems more consistent with the builtin vim\/vi commands. Please let me know if there are any problems. ","3":"Fixed an inconsistency. In 2.4 :A would always switch to the alternate file, regardless of whether unsaved changes were in the current file. In some cases it was possible to lose changes. This update changes :A back to 2.3 behaviour, but with a nicer error message, and provides support for a :A! command which will force the switch. This seems more consistent with the builtin vim\/vi commands. Please let me know if there are any problems. ","package":"a.vim","4":"a.vim","src_id":"2669","5":"2669","creation_date":"1074577643","6":"1074577643"},{"0":"31","vim_version":"6.0","1":"6.0","script_version":"2.4","2":"2.4","version_comment":"Fix error which occured when alternating from a file which had not been saved.","3":"Fix error which occured when alternating from a file which had not been saved.","package":"a.vim","4":"a.vim","src_id":"2010","5":"2010","creation_date":"1053548672","6":"1053548672"},{"0":"31","vim_version":"6.0","1":"6.0","script_version":"2.3","2":"2.3","version_comment":"Added support provided by Bindu Wavell to search for the alternate file across directories.","3":"Added support provided by Bindu Wavell to search for the alternate file across directories.","package":"a.vim","4":"a.vim","src_id":"1240","5":"1240","creation_date":"1032868742","6":"1032868742"},{"0":"31","vim_version":"6.0","1":"6.0","script_version":"2.2","2":"2.2","version_comment":"minor clean up. Remove repeated code used to \r\nsetup the default alternate file mappings. No changes in functionality. No reason to upgrade.","3":"minor clean up. Remove repeated code used to \r\nsetup the default alternate file mappings. No changes in functionality. No reason to upgrade.","package":"a.vim","4":"a.vim","src_id":"657","5":"657","creation_date":"1015448566","6":"1015448566"},{"0":"31","vim_version":"6.0","1":"6.0","script_version":"2.1","2":"2.1","version_comment":"simplified the config using vim's curly brace variables. Should behave the same way version 2.0X behaves....no huge reason to upgrade.","3":"simplified the config using vim's curly brace variables. Should behave the same way version 2.0X behaves....no huge reason to upgrade.","package":"a.vim","4":"a.vim","src_id":"531","5":"531","creation_date":"1012659799","6":"1012659799"},{"0":"31","vim_version":"6.0","1":"6.0","script_version":"2.0.1","2":"2.0.1","version_comment":"Adds support for vertically splitting via the command :AV","3":"Adds support for vertically splitting via the command :AV","package":"a.vim","4":"a.vim","src_id":"518","5":"518","creation_date":"1012314681","6":"1012314681"},{"0":"31","vim_version":"6.0","1":"6.0","script_version":"2.0b","2":"2.0b","version_comment":"Added support for Ada95 extensions\r\nminor bug fixed too.","3":"Added support for Ada95 extensions\r\nminor bug fixed too.","package":"a.vim","4":"a.vim","src_id":"384","5":"384","creation_date":"1007075702","6":"1007075702"},{"0":"31","vim_version":"6.0","1":"6.0","script_version":"2.0a","2":"2.0a","version_comment":"bug fix. handle the cases were the is no alternate file.","3":"bug fix. handle the cases were the is no alternate file.","package":"a.vim","4":"a.vim","src_id":"381","5":"381","creation_date":"1006893951","6":"1006893951"},{"0":"31","vim_version":"6.0","1":"6.0","script_version":"2.0","2":"2.0","version_comment":"Complete rewrite. Now the supported extensions are configurable instead of being part of the code.\r\nNotes on how to configure are in the comments in the file. Expect bugs, please be brave. Will fix reported issue quickly.","3":"Complete rewrite. Now the supported extensions are configurable instead of being part of the code.\r\nNotes on how to configure are in the comments in the file. Expect bugs, please be brave. Will fix reported issue quickly.","package":"a.vim","4":"a.vim","src_id":"380","5":"380","creation_date":"1006883565","6":"1006883565"},{"0":"31","vim_version":"6.0","1":"6.0","script_version":"1.4","2":"1.4","version_comment":"Added support for .hpp\/.HPP files. ","3":"Added support for .hpp\/.HPP files. ","package":"a.vim","4":"a.vim","src_id":"379","5":"379","creation_date":"1006883385","6":"1006883385"},{"0":"31","vim_version":"6.0","1":"6.0","script_version":"1.3","2":"1.3","version_comment":"Take care of some issues with case-sensitivity of the extension on windows platforms.","3":"Take care of some issues with case-sensitivity of the extension on windows platforms.","package":"a.vim","4":"a.vim","src_id":"334","5":"334","creation_date":"1005435870","6":"1005435870"},{"0":"31","vim_version":"6.0","1":"6.0","script_version":"1.2","2":"1.2","version_comment":"Minor changes to cater for \"files\" which are in vim buffers but not on disk (yet).","3":"Minor changes to cater for \"files\" which are in vim buffers but not on disk (yet).","package":"a.vim","4":"a.vim","src_id":"333","5":"333","creation_date":"1005434219","6":"1005434219"},{"0":"31","vim_version":"6.0","1":"6.0","script_version":"1.1","2":"1.1","version_comment":"This is a plugin-ized version of 1.1 for vim 5.7","3":"This is a plugin-ized version of 1.1 for vim 5.7","package":"a.vim","4":"a.vim","src_id":"163","5":"163","creation_date":"1000281172","6":"1000281172"},{"0":"31","vim_version":"5.7","1":"5.7","script_version":"1.1","2":"1.1","version_comment":"Added copyright information.\r\nSupport .cc, .cxx, .C extensions for C++ too.\r\n","3":"Added copyright information.\r\nSupport .cc, .cxx, .C extensions for C++ too.\r\n","package":"a.vim","4":"a.vim","src_id":"129","5":"129","creation_date":"998474051","6":"998474051"},{"0":"31","vim_version":"5.7","1":"5.7","script_version":"1.0","2":"1.0","version_comment":"Corrected vim version. The script works with 5.7, but should work with 6.0 too. ","3":"Corrected vim version. The script works with 5.7, but should work with 6.0 too. ","package":"a.vim","4":"a.vim","src_id":"44","5":"44","creation_date":"994713166","6":"994713166"}]},"30":{"script_id":"30","0":"30","script_name":"python.vim","1":"python.vim","script_type":"utility","2":"utility","summary":"A set of menus\/shortcuts to work with Python files","3":"A set of menus\/shortcuts to work with Python files","description":"Written by Mikael Berthe.\r\n\r\nThis script can be useful when editing Python scripts. It provides the following menus:\r\n- Select a block of lines with the same indentation\r\n- Select a function\r\n- Select a class\r\n- Go to previous\/next class\/function\r\n- Go to the beginning\/end of a block\r\n- Comment\/uncomment the selection\r\n- Jump to the last\/next line with the same indent\r\n- Shift a block (left\/right)\r\n- Creates list of classes and functions for easy code navigation\r\nVersion 1.8+ requires Vim 7, earlier versions require Vim 6","4":"Written by Mikael Berthe.\r\n\r\nThis script can be useful when editing Python scripts. It provides the following menus:\r\n- Select a block of lines with the same indentation\r\n- Select a function\r\n- Select a class\r\n- Go to previous\/next class\/function\r\n- Go to the beginning\/end of a block\r\n- Comment\/uncomment the selection\r\n- Jump to the last\/next line with the same indent\r\n- Shift a block (left\/right)\r\n- Creates list of classes and functions for easy code navigation\r\nVersion 1.8+ requires Vim 7, earlier versions require Vim 6","install_details":"Copy to the $VIMFILES\/ftplugin directory.  For more information, please read the beginning of the script...","5":"Copy to the $VIMFILES\/ftplugin directory.  For more information, please read the beginning of the script...","first_name":"Jon","6":"Jon","last_name":"Franklin","7":"Franklin","releases":[{"0":"30","vim_version":"7.0","1":"7.0","script_version":"1.13","2":"1.13","version_comment":"Fix for bug that prevented multi-line class and function definitions from showing up in the IM-Python menu.  Patch provided by Branden Rolston.","3":"Fix for bug that prevented multi-line class and function definitions from showing up in the IM-Python menu.  Patch provided by Branden Rolston.","package":"python_fn.vim","4":"python_fn.vim","src_id":"9196","5":"9196","creation_date":"1220034393","6":"1220034393"},{"0":"30","vim_version":"7.0","1":"7.0","script_version":"1.12","2":"1.12","version_comment":"* Changed to ftplugin and renamed to avoid collision with vim's ftplugin\/python.vim. Patch provided by Christopher Lambacher\r\n* Fixed error opening python buffer with no classes or functions.  Patch provided by Chris Farrow\r\n* Removed duplicate ]f key\r\n*Fixed block manipulation bugs due to collision on ]], [[ mappings. See menu for new mappings","3":"* Changed to ftplugin and renamed to avoid collision with vim's ftplugin\/python.vim. Patch provided by Christopher Lambacher\r\n* Fixed error opening python buffer with no classes or functions.  Patch provided by Chris Farrow\r\n* Removed duplicate ]f key\r\n*Fixed block manipulation bugs due to collision on ]], [[ mappings. See menu for new mappings","package":"python_fn.vim","4":"python_fn.vim","src_id":"8704","5":"8704","creation_date":"1211042319","6":"1211042319"},{"0":"30","vim_version":"7.0","1":"7.0","script_version":"1.11","2":"1.11","version_comment":"Add shortcuts for all remaining menu options.","3":"Add shortcuts for all remaining menu options.","package":"python.vim","4":"python.vim","src_id":"6481","5":"6481","creation_date":"1164782934","6":"1164782934"},{"0":"30","vim_version":"7.0","1":"7.0","script_version":"1.10","2":"1.10","version_comment":"Add shortcuts for commenting\/uncommenting selections.","3":"Add shortcuts for commenting\/uncommenting selections.","package":"python.vim","4":"python.vim","src_id":"6390","5":"6390","creation_date":"1162985703","6":"1162985703"},{"0":"30","vim_version":"6.0","1":"6.0","script_version":"1.9","2":"1.9","version_comment":"Fixed bug in IM-Python menu where function and class names beginning with \"_\" were not included.","3":"Fixed bug in IM-Python menu where function and class names beginning with \"_\" were not included.","package":"python.vim","4":"python.vim","src_id":"6103","5":"6103","creation_date":"1156605447","6":"1156605447"},{"0":"30","vim_version":"6.0","1":"6.0","script_version":"1.8","2":"1.8","version_comment":"Applied a patch from Jon Franklin: IM-Python menu improvements.\r\nUpdated copyright and email address.","3":"Applied a patch from Jon Franklin: IM-Python menu improvements.\r\nUpdated copyright and email address.","package":"python.vim","4":"python.vim","src_id":"6079","5":"6079","creation_date":"1155858556","6":"1155858556"},{"0":"30","vim_version":"6.0","1":"6.0","script_version":"1.7","2":"1.7","version_comment":"Use <Down> instead of 'j', so it should work when j is mapped.","3":"Use <Down> instead of 'j', so it should work when j is mapped.","package":"python.vim","4":"python.vim","src_id":"2187","5":"2187","creation_date":"1059127612","6":"1059127612"},{"0":"30","vim_version":"6.0","1":"6.0","script_version":"1.6","2":"1.6","version_comment":"Works better with folding... Many thanks to Guy L. Oliver!","3":"Works better with folding... Many thanks to Guy L. Oliver!","package":"python.vim","4":"python.vim","src_id":"2071","5":"2071","creation_date":"1055424993","6":"1055424993"},{"0":"30","vim_version":"6.0","1":"6.0","script_version":"1.5","2":"1.5","version_comment":"Same as 1.4, I just fixed a typo in the comments and my e-mail address...","3":"Same as 1.4, I just fixed a typo in the comments and my e-mail address...","package":"python.vim","4":"python.vim","src_id":"1637","5":"1637","creation_date":"1042681077","6":"1042681077"},{"0":"30","vim_version":"6.0","1":"6.0","script_version":"1.4","2":"1.4","version_comment":"Entry for Adam's IM-Python menu update in the main script menu; some other minor changes...","3":"Entry for Adam's IM-Python menu update in the main script menu; some other minor changes...","package":"python.vim","4":"python.vim","src_id":"155","5":"155","creation_date":"999671163","6":"999671163"},{"0":"30","vim_version":"6.0","1":"6.0","script_version":"1.3","2":"1.3","version_comment":"I've added an IM-Python menu that holds the class definitions and function definitions.","3":"I've added an IM-Python menu that holds the class definitions and function definitions.","package":"python.vim","4":"python.vim","src_id":"128","5":"128","creation_date":"998469463","6":"998469463"},{"0":"30","vim_version":"6.0","1":"6.0","script_version":"1.1","2":"1.1","version_comment":"* Changed the name of the global variable\r\n* Added a new variable; one can choose not to select trailing comments","3":"* Changed the name of the global variable\r\n* Added a new variable; one can choose not to select trailing comments","package":"python.vim","4":"python.vim","src_id":"42","5":"42","creation_date":"994519208","6":"994519208"},{"0":"30","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"python.vim","4":"python.vim","src_id":"41","5":"41","creation_date":"994498262","6":"994498262"},{"0":"30","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"python.vim","4":"python.vim","src_id":"40","5":"40","creation_date":"994497075","6":"994497075"}]},"29":{"script_id":"29","0":"29","script_name":"sourceSafe.zip","1":"sourceSafe.zip","script_type":"utility","2":"utility","summary":"Check out files from Microsoft SourceSafe directly from vim","3":"Check out files from Microsoft SourceSafe directly from vim","description":"Interfaces with Microsoft Visual SourceSafe and provides a shortcut to the most frequently used operations such as checkin, checkout, get current file, check differences, and so on.  Key features:\r\n- Takes advantage of Vim6.0's built-in diff feature for comparing the working version with the one in VSS.\r\n- Displays a list of all files checked out by the current user in a separate window.  Operations on multiple files can be done from this window.\r\n- The lock status of the current buffer is displayed in the status bar.\r\n- Online documentation.\r\n- Commands are available in the command line and the menubar.\r\n- Easy configuration.","4":"Interfaces with Microsoft Visual SourceSafe and provides a shortcut to the most frequently used operations such as checkin, checkout, get current file, check differences, and so on.  Key features:\r\n- Takes advantage of Vim6.0's built-in diff feature for comparing the working version with the one in VSS.\r\n- Displays a list of all files checked out by the current user in a separate window.  Operations on multiple files can be done from this window.\r\n- The lock status of the current buffer is displayed in the status bar.\r\n- Online documentation.\r\n- Commands are available in the command line and the menubar.\r\n- Easy configuration.","install_details":"Unzip sourceSafe.zip then read the setup instructions in sourceSafe.vim.","5":"Unzip sourceSafe.zip then read the setup instructions in sourceSafe.vim.","first_name":"David","6":"David","last_name":"Eggum","7":"Eggum","releases":[{"0":"29","vim_version":"6.0","1":"6.0","script_version":"1.4c","2":"1.4c","version_comment":"Removed redundant query of current lock status. Updated contact info.","3":"Removed redundant query of current lock status. Updated contact info.","package":"sourceSafe.zip","4":"sourceSafe.zip","src_id":"1022","5":"1022","creation_date":"1026838715","6":"1026838715"},{"0":"29","vim_version":"6.0","1":"6.0","script_version":"1.4a","2":"1.4a","version_comment":"Bug fix plus additions suggested by a few users.","3":"Bug fix plus additions suggested by a few users.","package":"sourceSafe.zip","4":"sourceSafe.zip","src_id":"169","5":"169","creation_date":"1000389559","6":"1000389559"},{"0":"29","vim_version":"6.0","1":"6.0","script_version":"1.4","2":"1.4","version_comment":"Added online help and SS commands to the menubar, as well as many other features.  Improved script configuration method and fixed many bugs.  To setup, follow the instructions in sourceSafe.vim.","3":"Added online help and SS commands to the menubar, as well as many other features.  Improved script configuration method and fixed many bugs.  To setup, follow the instructions in sourceSafe.vim.","package":"sourceSafe.zip","4":"sourceSafe.zip","src_id":"165","5":"165","creation_date":"1000308582","6":"1000308582"},{"0":"29","vim_version":"6.0","1":"6.0","script_version":"1.3","2":"1.3","version_comment":"Added showAll window that displays all checked out files by the current user; VSS commands can be performed directly from this window.  Other misc. improvements.  Revamped the documentation.","3":"Added showAll window that displays all checked out files by the current user; VSS commands can be performed directly from this window.  Other misc. improvements.  Revamped the documentation.","package":"sourceSafe.zip","4":"sourceSafe.zip","src_id":"82","5":"82","creation_date":"997095633","6":"997095633"},{"0":"29","vim_version":"6.0","1":"6.0","script_version":"1.2","2":"1.2","version_comment":"Takes advantage of Vim 6.0's built-in diff feature, among other things.","3":"Takes advantage of Vim 6.0's built-in diff feature, among other things.","package":"sourceSafe.zip","4":"sourceSafe.zip","src_id":"57","5":"57","creation_date":"995893161","6":"995893161"},{"0":"29","vim_version":"6.0","1":"6.0","script_version":"1.1a","2":"1.1a","version_comment":"Much improved!  The current lock status is placed in the ruler, commands are done silently with results echo'ed to the vim window.  Version 1.1a fixes hang after undocheckout when changes have been made","3":"Much improved!  The current lock status is placed in the ruler, commands are done silently with results echo'ed to the vim window.  Version 1.1a fixes hang after undocheckout when changes have been made","package":"sourceSafe.zip","4":"sourceSafe.zip","src_id":"50","5":"50","creation_date":"995381930","6":"995381930"},{"0":"29","vim_version":"6.0","1":"6.0","script_version":"1.1","2":"1.1","version_comment":"Much improved!  The current lock status is placed in the ruler, commands are done silently with results echo'ed to the vim window.","3":"Much improved!  The current lock status is placed in the ruler, commands are done silently with results echo'ed to the vim window.","package":"sourceSafe.zip","4":"sourceSafe.zip","src_id":"49","5":"49","creation_date":"995370524","6":"995370524"},{"0":"29","vim_version":"5.7","1":"5.7","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"sourceSafe.zip","4":"sourceSafe.zip","src_id":"38","5":"38","creation_date":"994341491","6":"994341491"}]},"28":{"script_id":"28","0":"28","script_name":"vimxmms.tar.gz","1":"vimxmms.tar.gz","script_type":"utility","2":"utility","summary":"Control XMMS from Vim","3":"Control XMMS from Vim","description":"I found that most of the time the only reason I exit from my Vim window is to change songs in XMMS. This script uses libcall () and a little library I wrote to control XMMS from Vim. You can change songs, change the volume, delete the playing song, shuffle play and pause.","4":"I found that most of the time the only reason I exit from my Vim window is to change songs in XMMS. This script uses libcall () and a little library I wrote to control XMMS from Vim. You can change songs, change the volume, delete the playing song, shuffle play and pause.","install_details":"You need to have glib development package installed as well as the xmms development package. Then a simple \"make\" would do. Read the vimxmms.txt documentation included for the rest.","5":"You need to have glib development package installed as well as the xmms development package. Then a simple \"make\" would do. Read the vimxmms.txt documentation included for the rest.","first_name":"Danie","6":"Danie","last_name":"Roux","7":"Roux","releases":[{"0":"28","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"vimxmms.tar.gz","4":"vimxmms.tar.gz","src_id":"36","5":"36","creation_date":"994219548","6":"994219548"}]},"27":{"script_id":"27","0":"27","script_name":"format.vim","1":"format.vim","script_type":"utility","2":"utility","summary":"formats the current paragraph - smooth right and left","3":"formats the current paragraph - smooth right and left","description":"a function to format paragraphs of text by inserting spaces. text is nicely justified to current text width after use\t\t","4":"a function to format paragraphs of text by inserting spaces. text is nicely justified to current text width after use\t\t","install_details":"source the script (format.vim) \r\nplease use only on plain text.. using on codes gives UGLY results :-)","5":"source the script (format.vim) \r\nplease use only on plain text.. using on codes gives UGLY results :-)","first_name":"kartik","6":"kartik","last_name":"murari","7":"murari","releases":[{"0":"27","vim_version":"5.7","1":"5.7","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"format.vim","4":"format.vim","src_id":"35","5":"35","creation_date":"993964362","6":"993964362"}]},"26":{"script_id":"26","0":"26","script_name":"vimmailr.zip","1":"vimmailr.zip","script_type":"utility","2":"utility","summary":"Send (MAPI) mail from vim","3":"Send (MAPI) mail from vim","description":"This script and dll (source included) allows you to send email from within vim (via MAPI). Supports To, CC, pulling in a signature file, and adding a file attachment. Win32, obviously. Tested on Win2k only so far.\r\n\r\nEnjoy!","4":"This script and dll (source included) allows you to send email from within vim (via MAPI). Supports To, CC, pulling in a signature file, and adding a file attachment. Win32, obviously. Tested on Win2k only so far.\r\n\r\nEnjoy!","install_details":"See vimmailr.vim","5":"See vimmailr.vim","first_name":"Ward","6":"Ward","last_name":"Fuller","7":"Fuller","releases":[{"0":"26","vim_version":"6.0","1":"6.0","script_version":"1.3","2":"1.3","version_comment":"- Bullet proofed the parsing code in the DLL (again).\r\n- Now works with vim6 (but still not a plugin - you must source it).\r\n- Added the _vmm command. An even quicker way to send a message\r\n  entirely from the vim command line.\r\n- Added the _vmf command. A quick way of sending a file entirely\r\n  from the vim command line.\r\n- Includes mailit.cpp - a simple test app you can use to test the\r\n  dll outside of vim. Could be used to send messages in a batch file.\r\n- Changed the _mmh command to _vmh (for vim mailer header) to be\r\n  more consistent with the other commands in the script.\r\n","3":"- Bullet proofed the parsing code in the DLL (again).\r\n- Now works with vim6 (but still not a plugin - you must source it).\r\n- Added the _vmm command. An even quicker way to send a message\r\n  entirely from the vim command line.\r\n- Added the _vmf command. A quick way of sending a file entirely\r\n  from the vim command line.\r\n- Includes mailit.cpp - a simple test app you can use to test the\r\n  dll outside of vim. Could be used to send messages in a batch file.\r\n- Changed the _mmh command to _vmh (for vim mailer header) to be\r\n  more consistent with the other commands in the script.\r\n","package":"vimmailr.zip","4":"vimmailr.zip","src_id":"372","5":"372","creation_date":"1006698163","6":"1006698163"},{"0":"26","vim_version":"5.7","1":"5.7","script_version":"1.2","2":"1.2","version_comment":"Added support for bcc and multiple file attachments. Fix for lines ending in 0x0A not being handled properly. I've been told this does not work in 6.0 and that it should be a \"plugin\". Till I make the leap to 6.0 and figure out what that means, anyone wishing to lend a hand on the conversion is most welcome to do so :)","3":"Added support for bcc and multiple file attachments. Fix for lines ending in 0x0A not being handled properly. I've been told this does not work in 6.0 and that it should be a \"plugin\". Till I make the leap to 6.0 and figure out what that means, anyone wishing to lend a hand on the conversion is most welcome to do so :)","package":"vimmailr.zip","4":"vimmailr.zip","src_id":"83","5":"83","creation_date":"997101671","6":"997101671"},{"0":"26","vim_version":"5.7","1":"5.7","script_version":"1.1","2":"1.1","version_comment":"Initial upload","3":"Initial upload","package":"vimmailr.zip","4":"vimmailr.zip","src_id":"34","5":"34","creation_date":"993748591","6":"993748591"}]},"25":{"script_id":"25","0":"25","script_name":"mailbrowser.vim","1":"mailbrowser.vim","script_type":"utility","2":"utility","summary":"Browse Berkeley mbox format mailbox files","3":"Browse Berkeley mbox format mailbox files","description":"This script allows you to browse (read) email from a standard Berkeley mbox formatted mail file.  When you type :Mail or :Mail <filename>, it will scan the file for headers, extract them, and present you with a list of the mail items present in the file.  You can easily select mail items to view.  It does not (as yet) allow you to send mail in any form, or to delete mail from the mailbox.\r\n\r\nSee the script for more detailed usage information.","4":"This script allows you to browse (read) email from a standard Berkeley mbox formatted mail file.  When you type :Mail or :Mail <filename>, it will scan the file for headers, extract them, and present you with a list of the mail items present in the file.  You can easily select mail items to view.  It does not (as yet) allow you to send mail in any form, or to delete mail from the mailbox.\r\n\r\nSee the script for more detailed usage information.","install_details":"Drop it in $HOME\/.vim\/plugins","5":"Drop it in $HOME\/.vim\/plugins","first_name":"Mark","6":"Mark","last_name":"Waggoner","7":"Waggoner","releases":[{"0":"25","vim_version":"6.0","1":"6.0","script_version":"1.4","2":"1.4","version_comment":"Slightly more robust help file creation","3":"Slightly more robust help file creation","package":"mailbrowser.vim","4":"mailbrowser.vim","src_id":"127","5":"127","creation_date":"998406585","6":"998406585"},{"0":"25","vim_version":"6.0","1":"6.0","script_version":"1.3","2":"1.3","version_comment":"Added J and K mappings in mail window to go to previous & next message.\r\nFixed a globbing bug\r\nAdded experimental auto-installation of help file","3":"Added J and K mappings in mail window to go to previous & next message.\r\nFixed a globbing bug\r\nAdded experimental auto-installation of help file","package":"mailbrowser.vim","4":"mailbrowser.vim","src_id":"126","5":"126","creation_date":"998405257","6":"998405257"},{"0":"25","vim_version":"6.0","1":"6.0","script_version":"1.2","2":"1.2","version_comment":"Added ability to sort index on subject, sender, or file-order.  Cleaned up a few small bugs.  See the script for details.  ","3":"Added ability to sort index on subject, sender, or file-order.  Cleaned up a few small bugs.  See the script for details.  ","package":"mailbrowser.vim","4":"mailbrowser.vim","src_id":"109","5":"109","creation_date":"997866790","6":"997866790"},{"0":"25","vim_version":"6.0","1":"6.0","script_version":"1.1","2":"1.1","version_comment":"Silenced some unwanted messages. \r\nAdded flag for \"New\" (unread) mail to the index.\r\n:SMail now works to always split mail browser into new window","3":"Silenced some unwanted messages. \r\nAdded flag for \"New\" (unread) mail to the index.\r\n:SMail now works to always split mail browser into new window","package":"mailbrowser.vim","4":"mailbrowser.vim","src_id":"62","5":"62","creation_date":"996075216","6":"996075216"},{"0":"25","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"mailbrowser.vim","4":"mailbrowser.vim","src_id":"33","5":"33","creation_date":"993509434","6":"993509434"}]},"24":{"script_id":"24","0":"24","script_name":"LoadHeaderFile.vim","1":"LoadHeaderFile.vim","script_type":"utility","2":"utility","summary":"load filename from an #include line","3":"load filename from an #include line","description":"Here are the mappings I use for this script (which I'll use in my description)\r\n\r\nmap <F12> :call LoadHeaderFile( getline( \".\" ), 0 )<CR>\r\nmap <C-F12> :call LoadHeaderFile( getline( \".\" ), 1 )<CR>\r\n\r\nTo use the script, just have your cursor on a #include line and hit F12 to load the .h file or C-F12 to load the corresponding .cpp file.  It splits the window when it loads the file.  If it can't find the file it just gives you an error that it can't find the file.\r\n\r\nYou have to have your path set up correctly for it to work.  If you don't know how to do that, simply add a \"se path=.,c:\/path\/**,c:\/another path\/**\" to you _vimrc.  Obviously there is a better explanation of paths in the help.\r\n\r\nThe code works on includes with <> or \"\".  It only checks for .h and .cpp, but you could modify it to do more.  I kept it simple so it's quicker.\r\n\r\nAnd as I'm typing this up I noticed that the #include has to be at the beginning of the line...can't have spaces or tabs.  I'll fix that in the next version :)\r\n\r\nIf you see any flaws or ways to improve this script, please let me know since I'm still learning how to script.","4":"Here are the mappings I use for this script (which I'll use in my description)\r\n\r\nmap <F12> :call LoadHeaderFile( getline( \".\" ), 0 )<CR>\r\nmap <C-F12> :call LoadHeaderFile( getline( \".\" ), 1 )<CR>\r\n\r\nTo use the script, just have your cursor on a #include line and hit F12 to load the .h file or C-F12 to load the corresponding .cpp file.  It splits the window when it loads the file.  If it can't find the file it just gives you an error that it can't find the file.\r\n\r\nYou have to have your path set up correctly for it to work.  If you don't know how to do that, simply add a \"se path=.,c:\/path\/**,c:\/another path\/**\" to you _vimrc.  Obviously there is a better explanation of paths in the help.\r\n\r\nThe code works on includes with <> or \"\".  It only checks for .h and .cpp, but you could modify it to do more.  I kept it simple so it's quicker.\r\n\r\nAnd as I'm typing this up I noticed that the #include has to be at the beginning of the line...can't have spaces or tabs.  I'll fix that in the next version :)\r\n\r\nIf you see any flaws or ways to improve this script, please let me know since I'm still learning how to script.","install_details":"If you're using Vim 6.0, just put it in the plugins directory.  Otherwise, just source it with all your other functions.","5":"If you're using Vim 6.0, just put it in the plugins directory.  Otherwise, just source it with all your other functions.","first_name":"Garner","6":"Garner","last_name":"Halloran","7":"Halloran","releases":[{"0":"24","vim_version":"6.0","1":"6.0","script_version":"1.1","2":"1.1","version_comment":"A little more efficient pattern searching.  Added support for loading header files that don't end in .h (ie fstream).  Added support for loading .c files instead of just .cpp files.  Added loaded_LoadHeaderFile so you can disable the plugin.  Fixed bug where it didn't recognize a #include if it wasn't at the beginning of a line.","3":"A little more efficient pattern searching.  Added support for loading header files that don't end in .h (ie fstream).  Added support for loading .c files instead of just .cpp files.  Added loaded_LoadHeaderFile so you can disable the plugin.  Fixed bug where it didn't recognize a #include if it wasn't at the beginning of a line.","package":"LoadHeaderFile.vim","4":"LoadHeaderFile.vim","src_id":"37","5":"37","creation_date":"994320916","6":"994320916"},{"0":"24","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"LoadHeaderFile.vim","4":"LoadHeaderFile.vim","src_id":"31","5":"31","creation_date":"993225468","6":"993225468"}]},"23":{"script_id":"23","0":"23","script_name":"EnhCommentify.vim","1":"EnhCommentify.vim","script_type":"utility","2":"utility","summary":"comment lines in a program","3":"comment lines in a program","description":"The development of the script is done at http:\/\/kotka.de\/projects\/enhancedcommentify\/index.html. Releases may be downloaded from below.\r\n\r\nThere is a major rework for Vim7 underway. In case you are missing any features, this is the time to suggest them. Send me an email or report your bugs or suggestions in the trac at the link above. This is a serious request from me to the users. In the past a lof of people complained on mailing lists, that \"this doesn't work\" or \"that feature is missing\", without contacting me. If you don't tell the upstream author, then this won't change!\r\n\r\nStay tuned.","4":"The development of the script is done at http:\/\/kotka.de\/projects\/enhancedcommentify\/index.html. Releases may be downloaded from below.\r\n\r\nThere is a major rework for Vim7 underway. In case you are missing any features, this is the time to suggest them. Send me an email or report your bugs or suggestions in the trac at the link above. This is a serious request from me to the users. In the past a lof of people complained on mailing lists, that \"this doesn't work\" or \"that feature is missing\", without contacting me. If you don't tell the upstream author, then this won't change!\r\n\r\nStay tuned.","install_details":"Simply drop the script in your .vim\/plugin directory. There is a detailed EnhancedCommentify.txt, since there are to much options to explain here. Put it in your .vim\/doc directory and issue the ':helptags ~\/.vim\/doc' command. ':help EnhancedCommentify' should then give you any information you need in order to use the new features of the script.                                                                                ","5":"Simply drop the script in your .vim\/plugin directory. There is a detailed EnhancedCommentify.txt, since there are to much options to explain here. Put it in your .vim\/doc directory and issue the ':helptags ~\/.vim\/doc' command. ':help EnhancedCommentify' should then give you any information you need in order to use the new features of the script.                                                                                ","first_name":"Meikel","6":"Meikel","last_name":"Brandmeyer","7":"Brandmeyer","releases":[{"0":"23","vim_version":"6.0","1":"6.0","script_version":"2.3","2":"2.3","version_comment":"Still alive! Yeah! :-D\r\n\r\nFinally a new release....\r\n\r\nThis is mainly a bugfix release:\r\n* Fixed a typo in the apache detection. (thanks to Brian Neu)\r\n* Fixed handling of nested comment escape strings. (thanks to Samuel Ferencik)\r\n* Fixed broken keyboard mappings when wcm is set to <Tab>. (thanks to xpatriotx)\r\n\r\n* Added support for viki & deplate (thanks to Thomas Link)\r\n* Added support xslt, xsd & mail (thanks to Stefano Zacchiroli)\r\n* Added callback-functionality to enable extension of the script without actually modifying the script.\r\n","3":"Still alive! Yeah! :-D\r\n\r\nFinally a new release....\r\n\r\nThis is mainly a bugfix release:\r\n* Fixed a typo in the apache detection. (thanks to Brian Neu)\r\n* Fixed handling of nested comment escape strings. (thanks to Samuel Ferencik)\r\n* Fixed broken keyboard mappings when wcm is set to <Tab>. (thanks to xpatriotx)\r\n\r\n* Added support for viki & deplate (thanks to Thomas Link)\r\n* Added support xslt, xsd & mail (thanks to Stefano Zacchiroli)\r\n* Added callback-functionality to enable extension of the script without actually modifying the script.\r\n","package":"EnhancedCommentify-2.3.tar.gz","4":"EnhancedCommentify-2.3.tar.gz","src_id":"8319","5":"8319","creation_date":"1203607007","6":"1203607007"},{"0":"23","vim_version":"6.0","1":"6.0","script_version":"2.2","2":"2.2","version_comment":"New features:\r\n * Keybindings may be turned off in the different modes. (eg. no bindings in insert mode)\r\n * Keybindings may be local to the buffer now.\r\n * Keybindings may be turned off in case of an unknown filetype.\r\n\r\nBugfixes:\r\n * Fixed a problem with UseSyntax. (thanks to Pieter Naaijkens)\r\n * Fixed Ocaml support. (thanks to Zhang Le)","3":"New features:\r\n * Keybindings may be turned off in the different modes. (eg. no bindings in insert mode)\r\n * Keybindings may be local to the buffer now.\r\n * Keybindings may be turned off in case of an unknown filetype.\r\n\r\nBugfixes:\r\n * Fixed a problem with UseSyntax. (thanks to Pieter Naaijkens)\r\n * Fixed Ocaml support. (thanks to Zhang Le)","package":"EnhancedCommentify-2.2.tar.gz","4":"EnhancedCommentify-2.2.tar.gz","src_id":"3490","5":"3490","creation_date":"1096253888","6":"1096253888"},{"0":"23","vim_version":"6.0","1":"6.0","script_version":"2.1","2":"2.1","version_comment":"This is version 2.1 of the EnhancedCommentify Script.\r\nNew features:\r\n * one-block commenting for multipart comments\r\n * if possible, use commentstring option in order to determine the comment strings.\r\n * moved autocmd to BufWinEnter in order to fix modeline usage\r\n * experimental parsing of comments option to find out middle string for new one-block feature.\r\n\r\nBugfixes:\r\n * fixed problems with tabs if align-right option is used\r\n * fixed case sensitive check for overrideEL (thanks to Steve Hall)\r\n * fixed problems with javascript filetype (thanks to Brian Neu)\r\n * changed init-autocmd to BufWinEnter to fix usage of modeline\r\n","3":"This is version 2.1 of the EnhancedCommentify Script.\r\nNew features:\r\n * one-block commenting for multipart comments\r\n * if possible, use commentstring option in order to determine the comment strings.\r\n * moved autocmd to BufWinEnter in order to fix modeline usage\r\n * experimental parsing of comments option to find out middle string for new one-block feature.\r\n\r\nBugfixes:\r\n * fixed problems with tabs if align-right option is used\r\n * fixed case sensitive check for overrideEL (thanks to Steve Hall)\r\n * fixed problems with javascript filetype (thanks to Brian Neu)\r\n * changed init-autocmd to BufWinEnter to fix usage of modeline\r\n","package":"EnhancedCommentify-2.1.tar.gz","4":"EnhancedCommentify-2.1.tar.gz","src_id":"2677","5":"2677","creation_date":"1075119651","6":"1075119651"},{"0":"23","vim_version":"6.0","1":"6.0","script_version":"2.0","2":"2.0","version_comment":"Version 2.0 is finally out. With a whole bunch of changes. Most important:\r\nThe script is now released under BSD license. But this should be no restriction I think.\r\nBugfixes:\r\n * '\\'' is an invalid expression (thanks to Zak Beck)\r\n * AltOpen\/Close set to '' could cause problems (thanks to Ben Kibbey)\r\n * bug in keybinding code (thanks to Charles Campbell)\r\n * trouble with 'C' in cpo (thanks to Luc Hermitte)\r\nNew features:\r\n * produces now block comments, eg:\r\n    \/*int a;\r\n    char b;*\/\r\n * option to add ident string only at opener\r\n * options may now be set on a per buffer basis.\r\n\r\nI can only recommend (again!) to read the help file for new options and explanations for old ones.\r\nThis release contains script und helpfile in a tar.gz.\r\n","3":"Version 2.0 is finally out. With a whole bunch of changes. Most important:\r\nThe script is now released under BSD license. But this should be no restriction I think.\r\nBugfixes:\r\n * '\\'' is an invalid expression (thanks to Zak Beck)\r\n * AltOpen\/Close set to '' could cause problems (thanks to Ben Kibbey)\r\n * bug in keybinding code (thanks to Charles Campbell)\r\n * trouble with 'C' in cpo (thanks to Luc Hermitte)\r\nNew features:\r\n * produces now block comments, eg:\r\n    \/*int a;\r\n    char b;*\/\r\n * option to add ident string only at opener\r\n * options may now be set on a per buffer basis.\r\n\r\nI can only recommend (again!) to read the help file for new options and explanations for old ones.\r\nThis release contains script und helpfile in a tar.gz.\r\n","package":"EnhancedCommentify-2.0.tar.gz","4":"EnhancedCommentify-2.0.tar.gz","src_id":"1202","5":"1202","creation_date":"1031730167","6":"1031730167"}]},"22":{"script_id":"22","0":"22","script_name":"hunspchk.zip","1":"hunspchk.zip","script_type":"utility","2":"utility","summary":"Hungarian spell checker","3":"Hungarian spell checker","description":"(Hungarian description - see below)\r\n\r\nThe Hungarian spelling checker uses Vim's highlighting ability to make misspelled (Hungarian) words show up as \"Error\" (usually white on a red background).\r\n\r\nThe Vim-based Hungarian spell checker also supports entering words that the cursor is on into a temporary or permanent dictionary and allows one to skip to the previous or subsequent spelling error (if any).\r\n\r\nIdeea is based on Charles.Campbell's English spelling checker (see\r\nhttp:\/\/users.erols.com\/astronaut\/vim\/#Spelling)\r\n\r\n\r\nMagyar helyes\u00c3\u00adr\u00c3\u00a1s-ellen\u00c3\u00b5rz\u00c3\u00b5: a hib\u00c3\u00a1s szavakat pirossal kiemeli a ViM \"syntax\" parancsa seg\u00c3\u00adts\u00c3\u00a9g\u00c3\u00a9vel. Hib\u00c3\u00a1s az, ami nincs benne a script-ben.\r\nTerm\u00c3\u00a9szetesen a lista nem teljes; kieg\u00c3\u00a9sz\u00c3\u00adt\u00c3\u00a9seket sz\u00c3\u00advesen fogadok (legjobb egy saj\u00c3\u00a1t file-ba \u00c3\u00b6sszegy\u00c3\u00bbjteni t\u00c3\u00b6bbet \u00c3\u00a9s \u00c3\u00bagy elk\u00c3\u00bcldeni).\r\n\r\nInstall\u00c3\u00a1l\u00c3\u00a1s, saj\u00c3\u00a1t szavak gy\u00c3\u00bbjt\u00c3\u00a9se: ld. feljebb az angol sz\u00c3\u00b6veget, ill. a megjegyz\u00c3\u00a9seket a file elej\u00c3\u00a9n. V\u00c3\u00a9gs\u00c3\u00b5 esetben persze hozz\u00c3\u00a1m is lehet fordulni :-)","4":"(Hungarian description - see below)\r\n\r\nThe Hungarian spelling checker uses Vim's highlighting ability to make misspelled (Hungarian) words show up as \"Error\" (usually white on a red background).\r\n\r\nThe Vim-based Hungarian spell checker also supports entering words that the cursor is on into a temporary or permanent dictionary and allows one to skip to the previous or subsequent spelling error (if any).\r\n\r\nIdeea is based on Charles.Campbell's English spelling checker (see\r\nhttp:\/\/users.erols.com\/astronaut\/vim\/#Spelling)\r\n\r\n\r\nMagyar helyes\u00c3\u00adr\u00c3\u00a1s-ellen\u00c3\u00b5rz\u00c3\u00b5: a hib\u00c3\u00a1s szavakat pirossal kiemeli a ViM \"syntax\" parancsa seg\u00c3\u00adts\u00c3\u00a9g\u00c3\u00a9vel. Hib\u00c3\u00a1s az, ami nincs benne a script-ben.\r\nTerm\u00c3\u00a9szetesen a lista nem teljes; kieg\u00c3\u00a9sz\u00c3\u00adt\u00c3\u00a9seket sz\u00c3\u00advesen fogadok (legjobb egy saj\u00c3\u00a1t file-ba \u00c3\u00b6sszegy\u00c3\u00bbjteni t\u00c3\u00b6bbet \u00c3\u00a9s \u00c3\u00bagy elk\u00c3\u00bcldeni).\r\n\r\nInstall\u00c3\u00a1l\u00c3\u00a1s, saj\u00c3\u00a1t szavak gy\u00c3\u00bbjt\u00c3\u00a9se: ld. feljebb az angol sz\u00c3\u00b6veget, ill. a megjegyz\u00c3\u00a9seket a file elej\u00c3\u00a9n. V\u00c3\u00a9gs\u00c3\u00b5 esetben persze hozz\u00c3\u00a1m is lehet fordulni :-)","install_details":"Unzip the file, copy the .vim-script anywhere you like and source it. (I prefer to put it under syntax or under macros directory of the ViM distro.)\r\n\r\nFor more info (temporary wordlist, functions, etc.) see comments at the beginning of the file.","5":"Unzip the file, copy the .vim-script anywhere you like and source it. (I prefer to put it under syntax or under macros directory of the ViM distro.)\r\n\r\nFor more info (temporary wordlist, functions, etc.) see comments at the beginning of the file.","first_name":"Sandor","6":"Sandor","last_name":"Kopanyi","7":"Kopanyi","releases":[{"0":"22","vim_version":"6.0","1":"6.0","script_version":"1.11","2":"1.11","version_comment":"Badwords can contain accents","3":"Badwords can contain accents","package":"hunspchk.zip","4":"hunspchk.zip","src_id":"335","5":"335","creation_date":"1005457310","6":"1005457310"},{"0":"22","vim_version":"5.7","1":"5.7","script_version":"1.1","2":"1.1","version_comment":"Initial upload","3":"Initial upload","package":"hunspchk.zip","4":"hunspchk.zip","src_id":"29","5":"29","creation_date":"993080993","6":"993080993"}]},"21":{"script_id":"21","0":"21","script_name":"info.vim","1":"info.vim","script_type":"utility","2":"utility","summary":"GNU info documentation browser.","3":"GNU info documentation browser.","description":"requires vim 6.x and GNU info. adds new command `Info': without arguments it displays \"directory\" node, with single argument displays this file (eg `:Info libc'). with two arguments, first specifies file and second node to display (eg `:Info libc POSIX\\ Threads' -- note space escaping). within browser, press h key to see available key shortcuts.","4":"requires vim 6.x and GNU info. adds new command `Info': without arguments it displays \"directory\" node, with single argument displays this file (eg `:Info libc'). with two arguments, first specifies file and second node to display (eg `:Info libc POSIX\\ Threads' -- note space escaping). within browser, press h key to see available key shortcuts.","install_details":"copy it into ~\/.vim\/plugin\/, then restart vim (or do :runtime info.vim).","5":"copy it into ~\/.vim\/plugin\/, then restart vim (or do :runtime info.vim).","first_name":"Slavik","6":"Slavik","last_name":"Gorbanyov","7":"Gorbanyov","releases":[{"0":"21","vim_version":"6.0","1":"6.0","script_version":"1.7","2":"1.7","version_comment":"added varios workarounds for win32 environment.\r\nfixed multiline cross-references matching.","3":"added varios workarounds for win32 environment.\r\nfixed multiline cross-references matching.","package":"info.vim","4":"info.vim","src_id":"1516","5":"1516","creation_date":"1038666269","6":"1038666269"},{"0":"21","vim_version":"6.0","1":"6.0","script_version":"1.6","2":"1.6","version_comment":"script now properly follows hyperlinks split across two lines.","3":"script now properly follows hyperlinks split across two lines.","package":"info.vim","4":"info.vim","src_id":"1410","5":"1410","creation_date":"1037190663","6":"1037190663"},{"0":"21","vim_version":"6.0","1":"6.0","script_version":"1.5","2":"1.5","version_comment":"fixed issue with c-shell and stderr redirection. global search still does not work properly, sorry.","3":"fixed issue with c-shell and stderr redirection. global search still does not work properly, sorry.","package":"info.vim","4":"info.vim","src_id":"701","5":"701","creation_date":"1016646964","6":"1016646964"},{"0":"21","vim_version":"6.0","1":"6.0","script_version":"1.2","2":"1.2","version_comment":"Initial upload","3":"Initial upload","package":"info.vim","4":"info.vim","src_id":"26","5":"26","creation_date":"992711905","6":"992711905"}]},"20":{"script_id":"20","0":"20","script_name":"jcommenter.vim","1":"jcommenter.vim","script_type":"utility","2":"utility","summary":"A script for automatically generating JavaDoc comments","3":"A script for automatically generating JavaDoc comments","description":"Updated 29.12.2002 KB\r\n\r\nDescription:\r\nGenerates JavaDoc (and some other) comments for java-sources. This is triggered by executing the JCommentWriter()-function while the cursor is over something meaningfull, or if a selection exists, the selected text is parsed and the comment template is generated based on that.\r\n\r\nThe following comments are generated (in the appropriate situations):\r\n1. File comments: user specifies the template, generated when the cursor is on the first line of the file.\r\n2. Class comments: generated when on top of a class declaration\r\n3. Method comments: generated when on top of a metod declaration. @return, @params, and @throws are generated, if applicable. If executed on a method declaration which already has JavaDoc-comments, updates the javadoc-comments by removing\/adding tags as needed.\r\n4.  Field comments. Simply adds an empty JavaDoc-comment template above the field declaration\r\n5. Copy @<name> -tags. When executed on @something, creates a tag with the same name directly above the line the cursor is currently on.\r\n6. @throws for RuntimeExceptions. When executed on a line containing something like \"throw new RuntimeException()\", a @throws-tag is added to the previous JavaDoc-comment.\r\n7. Block-end comments. When executed on a line containing a '}'-character and possibly some whitespace (but nothing else), generates a one-line-comment describing what block the '}' is terminating. For example, the comment for \"aVeryLongMethod\" is  \"\/\/ END: aVeryLongMethod\".\r\n\r\nThere are a bunch of other functions to support the comment generation (see the start of the script for full documentation). The style of the comment templates is configurable (see the file for configuration and description of the options)","4":"Updated 29.12.2002 KB\r\n\r\nDescription:\r\nGenerates JavaDoc (and some other) comments for java-sources. This is triggered by executing the JCommentWriter()-function while the cursor is over something meaningfull, or if a selection exists, the selected text is parsed and the comment template is generated based on that.\r\n\r\nThe following comments are generated (in the appropriate situations):\r\n1. File comments: user specifies the template, generated when the cursor is on the first line of the file.\r\n2. Class comments: generated when on top of a class declaration\r\n3. Method comments: generated when on top of a metod declaration. @return, @params, and @throws are generated, if applicable. If executed on a method declaration which already has JavaDoc-comments, updates the javadoc-comments by removing\/adding tags as needed.\r\n4.  Field comments. Simply adds an empty JavaDoc-comment template above the field declaration\r\n5. Copy @<name> -tags. When executed on @something, creates a tag with the same name directly above the line the cursor is currently on.\r\n6. @throws for RuntimeExceptions. When executed on a line containing something like \"throw new RuntimeException()\", a @throws-tag is added to the previous JavaDoc-comment.\r\n7. Block-end comments. When executed on a line containing a '}'-character and possibly some whitespace (but nothing else), generates a one-line-comment describing what block the '}' is terminating. For example, the comment for \"aVeryLongMethod\" is  \"\/\/ END: aVeryLongMethod\".\r\n\r\nThere are a bunch of other functions to support the comment generation (see the start of the script for full documentation). The style of the comment templates is configurable (see the file for configuration and description of the options)","install_details":"Add the jcommenter.vim to your macros-folder (or whatever).\r\nHere's what I have in my .vimrc:\r\n\r\n  autocmd FileType java let b:jcommenter_class_author='Kalle Bj\u00c3\u00b6rklid (bjorklid@st.jyu.fi)'\r\n  autocmd FileType java let b:jcommenter_file_author='Kalle Bj\u00c3\u00b6rklid (bjorklid@st.jyu.fi)'\r\n  autocmd FileType java source $VIM\/macros\/jcommenter.vim\r\n  autocmd FileType java map <M-c> :call JCommentWriter()<CR>\r\n\r\nSo I use Alt-c for commenting the file\/methods\/attributes\/classes.","5":"Add the jcommenter.vim to your macros-folder (or whatever).\r\nHere's what I have in my .vimrc:\r\n\r\n  autocmd FileType java let b:jcommenter_class_author='Kalle Bj\u00c3\u00b6rklid (bjorklid@st.jyu.fi)'\r\n  autocmd FileType java let b:jcommenter_file_author='Kalle Bj\u00c3\u00b6rklid (bjorklid@st.jyu.fi)'\r\n  autocmd FileType java source $VIM\/macros\/jcommenter.vim\r\n  autocmd FileType java map <M-c> :call JCommentWriter()<CR>\r\n\r\nSo I use Alt-c for commenting the file\/methods\/attributes\/classes.","first_name":"Kalle","6":"Kalle","last_name":"Bj\u00c3\u00b6rklid","7":"Bj\u00c3\u00b6rklid","releases":[{"0":"20","vim_version":"6.0","1":"6.0","script_version":"1.3.1","2":"1.3.1","version_comment":"Fixed two bugs concerning the modifications for 1.3","3":"Fixed two bugs concerning the modifications for 1.3","package":"jcommenter.vim","4":"jcommenter.vim","src_id":"1587","5":"1587","creation_date":"1041168305","6":"1041168305"},{"0":"20","vim_version":"6.0","1":"6.0","script_version":"1.3","2":"1.3","version_comment":"Added check to see whether the script is already loaded\r\nOption to have an empty line automatically added before the generated comment if there was none previously. See config (\"b:jcommenter_add_empty_line\").\r\n","3":"Added check to see whether the script is already loaded\r\nOption to have an empty line automatically added before the generated comment if there was none previously. See config (\"b:jcommenter_add_empty_line\").\r\n","package":"jcommenter.vim","4":"jcommenter.vim","src_id":"1586","5":"1586","creation_date":"1041165975","6":"1041165975"},{"0":"20","vim_version":"6.0","1":"6.0","script_version":"1.2.1","2":"1.2.1","version_comment":"Added support for generating modelines.\r\nUser requests:\r\nAdded possibility to have default tag values.\r\nAdded possibility to have space between tag groups.","3":"Added support for generating modelines.\r\nUser requests:\r\nAdded possibility to have default tag values.\r\nAdded possibility to have space between tag groups.","package":"jcommenter.vim","4":"jcommenter.vim","src_id":"371","5":"371","creation_date":"1006658684","6":"1006658684"},{"0":"20","vim_version":"6.0","1":"6.0","script_version":"1.2","2":"1.2","version_comment":"A bunch of new features (some seem to be actually useful ;-) :\r\nComplete method comment updating: now adds\/removes @return- and @param-tags form existing doc comments if no more applicable.\r\nAdded a new public function (+ mappings for it) for searching incomplete doc-comments (This is nice - a quick way to complete comments and to jump to next incomplete comment)\r\nIf executed on a line like \"throw new RuntimeExeception()\" will add an exception declaration to prev. javadoc comments.\r\nCorrected a problem where updating didn't work if a new parameter's name began the same way than an existing one's.\r\nNow behaves correctly when \"extra stuff\" (after the '{') is included in the range.\r\nAdded mapping for insert-mode to config-file.\r\nAdded an abbreviation (see config-file)\r\nNow adds the method\/class\/if\/while\/for... name as an ending comment when executed on a line containing only whitespace and a '}'.\r\nComment generation can now be virtually fully automated by using an abbreviation for '{' (which is presented in the config-file).","3":"A bunch of new features (some seem to be actually useful ;-) :\r\nComplete method comment updating: now adds\/removes @return- and @param-tags form existing doc comments if no more applicable.\r\nAdded a new public function (+ mappings for it) for searching incomplete doc-comments (This is nice - a quick way to complete comments and to jump to next incomplete comment)\r\nIf executed on a line like \"throw new RuntimeExeception()\" will add an exception declaration to prev. javadoc comments.\r\nCorrected a problem where updating didn't work if a new parameter's name began the same way than an existing one's.\r\nNow behaves correctly when \"extra stuff\" (after the '{') is included in the range.\r\nAdded mapping for insert-mode to config-file.\r\nAdded an abbreviation (see config-file)\r\nNow adds the method\/class\/if\/while\/for... name as an ending comment when executed on a line containing only whitespace and a '}'.\r\nComment generation can now be virtually fully automated by using an abbreviation for '{' (which is presented in the config-file).","package":"jcommenter.vim","4":"jcommenter.vim","src_id":"302","5":"302","creation_date":"1003917111","6":"1003917111"},{"0":"20","vim_version":"6.0","1":"6.0","script_version":"1.12","2":"1.12","version_comment":"Fixed a problem which caused all methods to be interperted as constructors (no @return-tag generated).","3":"Fixed a problem which caused all methods to be interperted as constructors (no @return-tag generated).","package":"jcommenter.vim","4":"jcommenter.vim","src_id":"278","5":"278","creation_date":"1003229961","6":"1003229961"},{"0":"20","vim_version":"6.0","1":"6.0","script_version":"1.11","2":"1.11","version_comment":"Fixed an error concerning the removal of the return tag when updating the comments (the buffer was partially deleted from the line where the @return tag was to EOF)","3":"Fixed an error concerning the removal of the return tag when updating the comments (the buffer was partially deleted from the line where the @return tag was to EOF)","package":"jcommenter.vim","4":"jcommenter.vim","src_id":"105","5":"105","creation_date":"997783311","6":"997783311"},{"0":"20","vim_version":"6.0","1":"6.0","script_version":"1.1","2":"1.1","version_comment":"This is again a .vim file (and not a zip). The configuration file is pasted at the beginning of the script. Again, see the script\r\nfor instructions.\r\n\r\nCan now choose between '@throws' and '@exception' tags.\r\nWhen executed on single-line comments (\"\/** blah blah *\/\") expands them into multiline comments preserving the text\r\nPartial method documentation comment updating (adds tags instead of writing a new template)","3":"This is again a .vim file (and not a zip). The configuration file is pasted at the beginning of the script. Again, see the script\r\nfor instructions.\r\n\r\nCan now choose between '@throws' and '@exception' tags.\r\nWhen executed on single-line comments (\"\/** blah blah *\/\") expands them into multiline comments preserving the text\r\nPartial method documentation comment updating (adds tags instead of writing a new template)","package":"jcommenter.vim","4":"jcommenter.vim","src_id":"101","5":"101","creation_date":"997619579","6":"997619579"},{"0":"20","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"A note:\r\nsince there was two files in this version of the script, I zipped them. However, if you download the file, it has .vim-extension, so you have to rename it.\r\nI'm really sorry for the inconvience.","3":"A note:\r\nsince there was two files in this version of the script, I zipped them. However, if you download the file, it has .vim-extension, so you have to rename it.\r\nI'm really sorry for the inconvience.","package":"jcommenter.vim","4":"jcommenter.vim","src_id":"97","5":"97","creation_date":"997529445","6":"997529445"},{"0":"20","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Did a complete rewrite of the script-code (this is the main reason for the version-number leap).\r\nA separate config-file, which should be modified to reflect the user's preferences.\r\nMore variables for better customization.\r\nDue to the rewrite, should now be more robust\r\nCursor movement and auto-start insert mode\r\nBetter control over the look of the comment templates\r\n\r\nRead new installation and configuration instructions from the .vim files","3":"Did a complete rewrite of the script-code (this is the main reason for the version-number leap).\r\nA separate config-file, which should be modified to reflect the user's preferences.\r\nMore variables for better customization.\r\nDue to the rewrite, should now be more robust\r\nCursor movement and auto-start insert mode\r\nBetter control over the look of the comment templates\r\n\r\nRead new installation and configuration instructions from the .vim files","package":"jcommenter.vim","4":"jcommenter.vim","src_id":"96","5":"96","creation_date":"997528852","6":"997528852"},{"0":"20","vim_version":"5.7","1":"5.7","script_version":"0.41","2":"0.41","version_comment":"Fixed the problem with final method parameters.","3":"Fixed the problem with final method parameters.","package":"jcommenter.vim","4":"jcommenter.vim","src_id":"47","5":"47","creation_date":"995201123","6":"995201123"},{"0":"20","vim_version":"5.7","1":"5.7","script_version":"0.4","2":"0.4","version_comment":"Recognizes now methods that have whitespaces just before the '('.\r\nThe file comments can now be completely redefined without editing the script.\r\nThe comment-skeleton for fields is changed to correspond with the Sun's code conventions.","3":"Recognizes now methods that have whitespaces just before the '('.\r\nThe file comments can now be completely redefined without editing the script.\r\nThe comment-skeleton for fields is changed to correspond with the Sun's code conventions.","package":"jcommenter.vim","4":"jcommenter.vim","src_id":"39","5":"39","creation_date":"994424320","6":"994424320"},{"0":"20","vim_version":"5.7","1":"5.7","script_version":"0.3","2":"0.3","version_comment":"- Recognices interfaces (same as classes)\r\n- improved recognition for methods\/attributes\r\n- Added tag copying:\r\n   For example, when executed on the following line:\r\n      * @throws IOException If cannot read file\r\n   the result is:\r\n      * @throws IOException If cannot read file\r\n      * @throws\r\n   Not that life changing, but quite nice when you want to document those\r\n   RuntimeExceptions, or need to add another paramter.\r\n","3":"- Recognices interfaces (same as classes)\r\n- improved recognition for methods\/attributes\r\n- Added tag copying:\r\n   For example, when executed on the following line:\r\n      * @throws IOException If cannot read file\r\n   the result is:\r\n      * @throws IOException If cannot read file\r\n      * @throws\r\n   Not that life changing, but quite nice when you want to document those\r\n   RuntimeExceptions, or need to add another paramter.\r\n","package":"jcommenter.vim","4":"jcommenter.vim","src_id":"27","5":"27","creation_date":"992775483","6":"992775483"},{"0":"20","vim_version":"5.7","1":"5.7","script_version":"0.2 beta","2":"0.2 beta","version_comment":"Initial upload","3":"Initial upload","package":"jcommenter.vim","4":"jcommenter.vim","src_id":"25","5":"25","creation_date":"992433289","6":"992433289"}]},"19":{"script_id":"19","0":"19","script_name":"dl.vim","1":"dl.vim","script_type":"utility","2":"utility","summary":"converts file links to GetRight GRX files","3":"converts file links to GetRight GRX files","description":"Use this script when you have a www page with the list of downloadable \r\nlinks and want to download all\/some of them using GetRight.\r\n\r\nThe script assumes that you have a file, each line of which containing a link(s)\r\nto file you want to download. Such file may be produced, for examle, if You open \r\nsome html file and issue a command : \r\n\r\n:gl \/href=\".*zip\"\/ . write! >> files.grx\r\n:e files.grx\r\n\r\nWhen loaded, the script loads and maps following functions :\r\n1. UnHref() - which removes everything except URLs themselves, and puts every URL on a single line\r\n2. Ability to set the destination directory\r\n3. MakeList() - Function that converts pure URLs to GetRight acceptable information - before invoking it,\r\neach line should contain pure single URL.\r\n","4":"Use this script when you have a www page with the list of downloadable \r\nlinks and want to download all\/some of them using GetRight.\r\n\r\nThe script assumes that you have a file, each line of which containing a link(s)\r\nto file you want to download. Such file may be produced, for examle, if You open \r\nsome html file and issue a command : \r\n\r\n:gl \/href=\".*zip\"\/ . write! >> files.grx\r\n:e files.grx\r\n\r\nWhen loaded, the script loads and maps following functions :\r\n1. UnHref() - which removes everything except URLs themselves, and puts every URL on a single line\r\n2. Ability to set the destination directory\r\n3. MakeList() - Function that converts pure URLs to GetRight acceptable information - before invoking it,\r\neach line should contain pure single URL.\r\n","install_details":"Load the script using :so command, then use mapped functions. If you forgot the mappings,\r\nreload the script again, it shows brief description on loading.","5":"Load the script using :so command, then use mapped functions. If you forgot the mappings,\r\nreload the script again, it shows brief description on loading.","first_name":"Alex","6":"Alex","last_name":"Jakushev","7":"Jakushev","releases":[{"0":"19","vim_version":"5.7","1":"5.7","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"dl.vim","4":"dl.vim","src_id":"24","5":"24","creation_date":"992344690","6":"992344690"}]},"18":{"script_id":"18","0":"18","script_name":"calendar.vim","1":"calendar.vim","script_type":"utility","2":"utility","summary":"Open a calendar in a read-only buffer for viewing.","3":"Open a calendar in a read-only buffer for viewing.","description":"Requires the Unix command program 'cal' or its equivalent.  Really only provides a way of pulling up a calendar into a buffer in Vim.  The script opens a buffer if one doesn't exist.  The buffer is set up to be readonly and not modified (or modifiable if 6.0 or better).  Should work for both 5.7 and 6.0x.\r\n\r\nUsage is:  Cal 2001   | \" for current year calendar\r\n              Cal 4 2001 | \" for April of 2001 month  calendar","4":"Requires the Unix command program 'cal' or its equivalent.  Really only provides a way of pulling up a calendar into a buffer in Vim.  The script opens a buffer if one doesn't exist.  The buffer is set up to be readonly and not modified (or modifiable if 6.0 or better).  Should work for both 5.7 and 6.0x.\r\n\r\nUsage is:  Cal 2001   | \" for current year calendar\r\n              Cal 4 2001 | \" for April of 2001 month  calendar","install_details":"Copy to directory of your choice, make sure the 'cal' is in your path, and source it from your .vimrc.","5":"Copy to directory of your choice, make sure the 'cal' is in your path, and source it from your .vimrc.","first_name":"Douglas","6":"Douglas","last_name":"Potts","7":"Potts","releases":[{"0":"18","vim_version":"5.7","1":"5.7","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"calendar.vim","4":"calendar.vim","src_id":"23","5":"23","creation_date":"992263078","6":"992263078"}]},"17":{"script_id":"17","0":"17","script_name":"ls.vim","1":"ls.vim","script_type":"utility","2":"utility","summary":"Directory Browser for UNIX\/CYGWIN","3":"Directory Browser for UNIX\/CYGWIN","description":"A simple file\/directory browser written in vim script.","4":"A simple file\/directory browser written in vim script.","install_details":"so ls.vim\r\n\r\n:LS = start the directory browser...\r\n:LSL = start the directory browser, all files.","5":"so ls.vim\r\n\r\n:LS = start the directory browser...\r\n:LSL = start the directory browser, all files.","first_name":"Mike","6":"Mike","last_name":"Sharpe","7":"Sharpe","releases":[{"0":"17","vim_version":"5.7","1":"5.7","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"ls.vim","4":"ls.vim","src_id":"21","5":"21","creation_date":"992041364","6":"992041364"}]},"16":{"script_id":"16","0":"16","script_name":"compiler.tar.gz","1":"compiler.tar.gz","script_type":"utility","2":"utility","summary":"[Defunct] Part of functionality for Vim 6.0","3":"[Defunct] Part of functionality for Vim 6.0","description":"After a discussion of ways of setting the correct error format for various compilers on vim-dev, I threw together this script to allow you to do:\r\n:Compiler bcc55\r\n\r\nand have the errorformat for compiler be setup.  Currently it replaces the default errorformat, but is easily changed to be appended to the current value of errorformat.  Uses the :runtime command to search for a filename (this case, bcc55.vim) in a 'compiler' directory under one of the runtime directories.  Commonly, ~\/.vim\/compiler.","4":"After a discussion of ways of setting the correct error format for various compilers on vim-dev, I threw together this script to allow you to do:\r\n:Compiler bcc55\r\n\r\nand have the errorformat for compiler be setup.  Currently it replaces the default errorformat, but is easily changed to be appended to the current value of errorformat.  Uses the :runtime command to search for a filename (this case, bcc55.vim) in a 'compiler' directory under one of the runtime directories.  Commonly, ~\/.vim\/compiler.","install_details":"Drop compiler.vim into your plugin directory.  Create a subdirectory compiler\/ under one of the directories in your runtimepath, and copy the bcc55.vim script that is in this archive.","5":"Drop compiler.vim into your plugin directory.  Create a subdirectory compiler\/ under one of the directories in your runtimepath, and copy the bcc55.vim script that is in this archive.","first_name":"Douglas","6":"Douglas","last_name":"Potts","7":"Potts","releases":[{"0":"16","vim_version":"6.0","1":"6.0","script_version":"0.2","2":"0.2","version_comment":"Removed functions and user command (as of Vim 6.0aj :compiler command is included in the distribution), and updated the all of the compiler .vim files to fit the accepted format.","3":"Removed functions and user command (as of Vim 6.0aj :compiler command is included in the distribution), and updated the all of the compiler .vim files to fit the accepted format.","package":"compiler.tar.gz","4":"compiler.tar.gz","src_id":"28","5":"28","creation_date":"992952541","6":"992952541"},{"0":"16","vim_version":"6.0","1":"6.0","script_version":"0.1","2":"0.1","version_comment":"Initial upload","3":"Initial upload","package":"compiler.tar.gz","4":"compiler.tar.gz","src_id":"20","5":"20","creation_date":"992007053","6":"992007053"}]},"15":{"script_id":"15","0":"15","script_name":"ccase.vim","1":"ccase.vim","script_type":"utility","2":"utility","summary":"Script to setup maps\/menus to add in using Clearcase.","3":"Script to setup maps\/menus to add in using Clearcase.","description":"Based on what Vim detects you are running, allows for Unix or WinNT based Clearcase.  Script will setup command-line abbreviations to shortcut checking-in\/out, uncheckout, list checkouts (current directory, recurse directories, or all vobs), list version history.  Also sets up a Clearcase Menu if you are running a gui version of Vim, which provides the same operations.","4":"Based on what Vim detects you are running, allows for Unix or WinNT based Clearcase.  Script will setup command-line abbreviations to shortcut checking-in\/out, uncheckout, list checkouts (current directory, recurse directories, or all vobs), list version history.  Also sets up a Clearcase Menu if you are running a gui version of Vim, which provides the same operations.","install_details":"Vim 6.x:  Make sure to download the correct (new) version.\r\n\r\nVersion 1.36 and later:\r\nOnly one file, ccase.vim, and documentation is self installing the first time that VIM is started after putting ccase.vim in your plugin directory.\r\n\r\nVersions 1.35 and prior:\r\nUnpack the tar'ed and  gzip'ed file in your ~\/.vim directory, the files will go into plugin\/ccase.vim and doc\/ccase.txt.\r\n\r\nThen (from within vim) do\r\n:helptags ~\/.vim\/doc\r\n\r\nto rebuild the tags file.  For details, read\r\n:help add-local-help","5":"Vim 6.x:  Make sure to download the correct (new) version.\r\n\r\nVersion 1.36 and later:\r\nOnly one file, ccase.vim, and documentation is self installing the first time that VIM is started after putting ccase.vim in your plugin directory.\r\n\r\nVersions 1.35 and prior:\r\nUnpack the tar'ed and  gzip'ed file in your ~\/.vim directory, the files will go into plugin\/ccase.vim and doc\/ccase.txt.\r\n\r\nThen (from within vim) do\r\n:helptags ~\/.vim\/doc\r\n\r\nto rebuild the tags file.  For details, read\r\n:help add-local-help","first_name":"Douglas","6":"Douglas","last_name":"Potts","7":"Potts","releases":[{"0":"15","vim_version":"6.0","1":"6.0","script_version":"1.38","2":"1.38","version_comment":"Added a Change Checkout comments command, and associated menu item.\r\nAdded version line to allow for use by GetLatestVimScripts script by Dr. Charles (Chip) Campbell.","3":"Added a Change Checkout comments command, and associated menu item.\r\nAdded version line to allow for use by GetLatestVimScripts script by Dr. Charles (Chip) Campbell.","package":"ccase.vim","4":"ccase.vim","src_id":"3420","5":"3420","creation_date":"1094217908","6":"1094217908"},{"0":"15","vim_version":"6.0","1":"6.0","script_version":"1.36","2":"1.36","version_comment":"My changes:\r\nAdd User commands for all the regular cabbrevs used, so that diff commands and others may be issued on the command line with '-c'.\r\n\r\nChanges from Gary Johnson and WEN Guopeng:\r\nAddition of a diff with first version on this branch.\r\n\r\nStefan Berglund and WEN Guopeng:\r\nAlter 'ctpwv' to not use the $view variable, and instead get it from the system.\r\n\r\nChanges from WEN Guopeng:\r\nChanges to embed the ccase.vim documentation in the .vim file, and automatically install on startup, diff with merged version, and other wonderful addititions that I'm probably forgetting.\r\n","3":"My changes:\r\nAdd User commands for all the regular cabbrevs used, so that diff commands and others may be issued on the command line with '-c'.\r\n\r\nChanges from Gary Johnson and WEN Guopeng:\r\nAddition of a diff with first version on this branch.\r\n\r\nStefan Berglund and WEN Guopeng:\r\nAlter 'ctpwv' to not use the $view variable, and instead get it from the system.\r\n\r\nChanges from WEN Guopeng:\r\nChanges to embed the ccase.vim documentation in the .vim file, and automatically install on startup, diff with merged version, and other wonderful addititions that I'm probably forgetting.\r\n","package":"ccase.vim","4":"ccase.vim","src_id":"2580","5":"2580","creation_date":"1070957787","6":"1070957787"},{"0":"15","vim_version":"6.0","1":"6.0","script_version":"1.35","2":"1.35","version_comment":"- Added variable for listing checkouts by anyone, or just 'me'.\r\n- Added save of comment text into global var so it is accessable across\r\n  starts and stops of vim.\r\n- Replaces some echo's with echomsg's so they are saved in vim err list.\r\n- Moved autocmds around, so buffer-local kemaps aren't lost by the\r\n  autocmds which automatically refresh the listing upon BufEnter.\r\n- Added uncheckout functionality into Vim function instead of relying on\r\n  shell to do it.\r\n- MakeActiv now prompts for an activity comment.\r\n- Activity functions no show the activity comment, including the\r\n  activity list window.\r\n- For the activity and checkout list windows, open new files below and\r\n  to the right of the originating list window.\r\n- Added check for maps of <unique><script> already being there so\r\n  resourcing the plugin doesn't give errors.\r\n","3":"- Added variable for listing checkouts by anyone, or just 'me'.\r\n- Added save of comment text into global var so it is accessable across\r\n  starts and stops of vim.\r\n- Replaces some echo's with echomsg's so they are saved in vim err list.\r\n- Moved autocmds around, so buffer-local kemaps aren't lost by the\r\n  autocmds which automatically refresh the listing upon BufEnter.\r\n- Added uncheckout functionality into Vim function instead of relying on\r\n  shell to do it.\r\n- MakeActiv now prompts for an activity comment.\r\n- Activity functions no show the activity comment, including the\r\n  activity list window.\r\n- For the activity and checkout list windows, open new files below and\r\n  to the right of the originating list window.\r\n- Added check for maps of <unique><script> already being there so\r\n  resourcing the plugin doesn't give errors.\r\n","package":"ccase-1.35.tgz","4":"ccase-1.35.tgz","src_id":"2228","5":"2228","creation_date":"1060691995","6":"1060691995"},{"0":"15","vim_version":"6.0","1":"6.0","script_version":"1.31","2":"1.31","version_comment":"Incorporated Guillaume Lafage's changes for link resolution and\r\nimprovements for the 'list checkouts' and 'list activities' windows.\r\nNow double-click or Enter on a name in the list checkouts window will split-open that file, and double-click or Enter on an activity will set the current activity to be that of the activity under the cursor. \r\nSome updates to the help file, added a thanks section to recognize those who have contributed to ccase.vim (thanks\r\neveryone, I'm still open to more suggestions).","3":"Incorporated Guillaume Lafage's changes for link resolution and\r\nimprovements for the 'list checkouts' and 'list activities' windows.\r\nNow double-click or Enter on a name in the list checkouts window will split-open that file, and double-click or Enter on an activity will set the current activity to be that of the activity under the cursor. \r\nSome updates to the help file, added a thanks section to recognize those who have contributed to ccase.vim (thanks\r\neveryone, I'm still open to more suggestions).","package":"ccase-1.31.tgz","4":"ccase-1.31.tgz","src_id":"1893","5":"1893","creation_date":"1049371463","6":"1049371463"},{"0":"15","vim_version":"6.0","1":"6.0","script_version":"1.30","2":"1.30","version_comment":"added support for access to link files.","3":"added support for access to link files.","package":"ccase.vim.tgz","4":"ccase.vim.tgz","src_id":"1783","5":"1783","creation_date":"1046938722","6":"1046938722"},{"0":"15","vim_version":"6.0","1":"6.0","script_version":"1.30_bugfi","2":"1.30_bugfi","version_comment":"fix from Gary Johnson on cleartool describe, used to determine predecessor\r\nversion for ctpdif, escaping missing on space in filename, seen on Windows.\r\n","3":"fix from Gary Johnson on cleartool describe, used to determine predecessor\r\nversion for ctpdif, escaping missing on space in filename, seen on Windows.\r\n","package":"ccase-1.30-bugfixes.tgz","4":"ccase-1.30-bugfixes.tgz","src_id":"1324","5":"1324","creation_date":"1035177941","6":"1035177941"},{"0":"15","vim_version":"6.0","1":"6.0","script_version":"1.30","2":"1.30","version_comment":"Added buffer local settings to set the current activity, and update the\r\ncheckout list window on BufEnter.  Also added ability to create an UCM\r\nactivity (mkactiv).  See updates to the documentation (:h ccase-plugin).","3":"Added buffer local settings to set the current activity, and update the\r\ncheckout list window on BufEnter.  Also added ability to create an UCM\r\nactivity (mkactiv).  See updates to the documentation (:h ccase-plugin).","package":"ccase-1.30.tgz","4":"ccase-1.30.tgz","src_id":"1248","5":"1248","creation_date":"1032948970","6":"1032948970"},{"0":"15","vim_version":"6.0","1":"6.0","script_version":"1.29","2":"1.29","version_comment":"Implemented suggestion (ok, call it enhanced from his patch), such that the\r\nctpdif and ctqdif functions work properly when the filename you were editting\r\nwas a fully version qualified ClearCase name (ie. filename@@\/main\/my\/version\/1).\r\nThis is likely to happen if you open a specific file version via the ClearCase\r\nfile browser or version tree browser.\r\n\r\nSmall correction to use of variables local to the function (l:), not local\r\nto the script (s:).\r\n","3":"Implemented suggestion (ok, call it enhanced from his patch), such that the\r\nctpdif and ctqdif functions work properly when the filename you were editting\r\nwas a fully version qualified ClearCase name (ie. filename@@\/main\/my\/version\/1).\r\nThis is likely to happen if you open a specific file version via the ClearCase\r\nfile browser or version tree browser.\r\n\r\nSmall correction to use of variables local to the function (l:), not local\r\nto the script (s:).\r\n","package":"ccase-1.29.tgz","4":"ccase-1.29.tgz","src_id":"1203","5":"1203","creation_date":"1031745857","6":"1031745857"},{"0":"15","vim_version":"6.0","1":"6.0","script_version":"1.24.1","2":"1.24.1","version_comment":"Fixed goof in 'bd' command for results window, that would 'bd!' the first buffer\r\nmatching [acelrst] (ccase_results).\r\n\r\nPlease upgrade if you downloaded 1.24.\r\n\r\nSorry for the inconvience.\r\n","3":"Fixed goof in 'bd' command for results window, that would 'bd!' the first buffer\r\nmatching [acelrst] (ccase_results).\r\n\r\nPlease upgrade if you downloaded 1.24.\r\n\r\nSorry for the inconvience.\r\n","package":"ccase.tgz","4":"ccase.tgz","src_id":"1124","5":"1124","creation_date":"1029302613","6":"1029302613"},{"0":"15","vim_version":"6.0","1":"6.0","script_version":"1.25","2":"1.25","version_comment":"After several comments on the possible naming collision of the ccase results\r\nfile, I've changed the implementation so that it uses a generated filename for\r\nthe temp file that captures command output (via tempname()), and now use a\r\nspecial buffer to display the results.\r\n\r\nEnjoy.\r\n","3":"After several comments on the possible naming collision of the ccase results\r\nfile, I've changed the implementation so that it uses a generated filename for\r\nthe temp file that captures command output (via tempname()), and now use a\r\nspecial buffer to display the results.\r\n\r\nEnjoy.\r\n","package":"ccase.tgz","4":"ccase.tgz","src_id":"1114","5":"1114","creation_date":"1029224397","6":"1029224397"},{"0":"15","vim_version":"6.0","1":"6.0","script_version":"1.22","2":"1.22","version_comment":"Added checkout of elements as \"unreserved\" as suggested by Barry Nisly.  Plus some fixes to the documentation.","3":"Added checkout of elements as \"unreserved\" as suggested by Barry Nisly.  Plus some fixes to the documentation.","package":"ccase.tgz","4":"ccase.tgz","src_id":"765","5":"765","creation_date":"1018015061","6":"1018015061"},{"0":"15","vim_version":"6.0","1":"6.0","script_version":"1.17","2":"1.17","version_comment":"Small bugfix: corrected default setting of g:ccaseUseDialog.  Now checks\r\nto see if VIM was compiled with the GUI options.\r\n\r\nMAIN ADDITION:\r\nI finally forced myself to write up some documentation for this beast.\r\nHence it has now become ccase.tgz.\r\n\r\nContains:\r\ndoc\/ccase.txt\r\nplugin\/ccase.vim\r\n\r\nDon't forget to use :helptags to generate tags for\r\nnewly downloaded plugin documentation.","3":"Small bugfix: corrected default setting of g:ccaseUseDialog.  Now checks\r\nto see if VIM was compiled with the GUI options.\r\n\r\nMAIN ADDITION:\r\nI finally forced myself to write up some documentation for this beast.\r\nHence it has now become ccase.tgz.\r\n\r\nContains:\r\ndoc\/ccase.txt\r\nplugin\/ccase.vim\r\n\r\nDon't forget to use :helptags to generate tags for\r\nnewly downloaded plugin documentation.","package":"ccase.tgz","4":"ccase.tgz","src_id":"462","5":"462","creation_date":"1010754166","6":"1010754166"},{"0":"15","vim_version":"6.0","1":"6.0","script_version":"1.14","2":"1.14","version_comment":"Lots of enhancements to prompting, added\r\ndiff capability utilizing vim diff\r\nfunctionality.  Added more options for\r\ncheckin\/out comments, making an element,\r\netc.  Check it out.","3":"Lots of enhancements to prompting, added\r\ndiff capability utilizing vim diff\r\nfunctionality.  Added more options for\r\ncheckin\/out comments, making an element,\r\netc.  Check it out.","package":"ccase.vim","4":"ccase.vim","src_id":"311","5":"311","creation_date":"1004623142","6":"1004623142"},{"0":"15","vim_version":"6.0","1":"6.0","script_version":"1.11","2":"1.11","version_comment":"Per suggestion by Gerard van Wageningen, added prompt box capability as well as\r\nvim console prompt capability for checkin and checkout comments.  If using the\r\nGUI version and g:ccaseUseDialog is set to 1 (default) then the gui prompt box\r\nwill pop up for the comment to be added to the checkin\/out.  If g:ccaseUseDialog\r\nis set to 0, then prompt will be of the console variety.\r\n\r\nContinued suggestions are welcome!\r\n\r\n\r\nNote:\r\nScript version now matches cvs revision number.","3":"Per suggestion by Gerard van Wageningen, added prompt box capability as well as\r\nvim console prompt capability for checkin and checkout comments.  If using the\r\nGUI version and g:ccaseUseDialog is set to 1 (default) then the gui prompt box\r\nwill pop up for the comment to be added to the checkin\/out.  If g:ccaseUseDialog\r\nis set to 0, then prompt will be of the console variety.\r\n\r\nContinued suggestions are welcome!\r\n\r\n\r\nNote:\r\nScript version now matches cvs revision number.","package":"ccase.vim","4":"ccase.vim","src_id":"309","5":"309","creation_date":"1004439346","6":"1004439346"},{"0":"15","vim_version":"6.0","1":"6.0","script_version":"1.4","2":"1.4","version_comment":"Fixed bug in checking directory back in\r\nafter making element, in the new make\r\nelement functionality.","3":"Fixed bug in checking directory back in\r\nafter making element, in the new make\r\nelement functionality.","package":"ccase.vim","4":"ccase.vim","src_id":"216","5":"216","creation_date":"1001941662","6":"1001941662"},{"0":"15","vim_version":"6.0","1":"6.0","script_version":"1.3","2":"1.3","version_comment":"Added 'mkelem' functionality.  Function to make current file an element prompts to checkout directory if it is not already checkedout, adds file (not left checkedout), and prompts for whether directory is to be checked in again.","3":"Added 'mkelem' functionality.  Function to make current file an element prompts to checkout directory if it is not already checkedout, adds file (not left checkedout), and prompts for whether directory is to be checked in again.","package":"ccase.vim","4":"ccase.vim","src_id":"213","5":"213","creation_date":"1001933390","6":"1001933390"},{"0":"15","vim_version":"6.0","1":"6.0","script_version":"1.2","2":"1.2","version_comment":"Put in missing OpenIfNew function, that is used\r\nto open up a new 'results' buffer if one hasn't already been loaded.","3":"Put in missing OpenIfNew function, that is used\r\nto open up a new 'results' buffer if one hasn't already been loaded.","package":"ccase.vim","4":"ccase.vim","src_id":"202","5":"202","creation_date":"1001653962","6":"1001653962"},{"0":"15","vim_version":"6.0","1":"6.0","script_version":"1.1","2":"1.1","version_comment":"Cleaned up some things, and tried to make\r\nthe script more in the style of a Vim 6.0 plugin.\r\nStill has a ways to go for setting up mapleader yet.","3":"Cleaned up some things, and tried to make\r\nthe script more in the style of a Vim 6.0 plugin.\r\nStill has a ways to go for setting up mapleader yet.","package":"ccase.vim","4":"ccase.vim","src_id":"194","5":"194","creation_date":"1001486897","6":"1001486897"},{"0":"15","vim_version":"5.7","1":"5.7","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"ccase.vim","4":"ccase.vim","src_id":"19","5":"19","creation_date":"991983067","6":"991983067"}]},"14":{"script_id":"14","0":"14","script_name":"htmlcmd.vim","1":"htmlcmd.vim","script_type":"utility","2":"utility","summary":"Rich HTML\/XML commands","3":"Rich HTML\/XML commands","description":"This script handles a number of mundane tasks in HTML \/ XML.  It allows you to create a default HTML header (Alt+0),  to define headings <h1> .. <h6> (Alt+1.. Alt+6), to toggle bold, italic, underline, paragraphs & kbd commands.  It gives shortcuts for ordered\/unordered lists and row definitions.  \r\n\r\nThe script has commands to insert horizontal rules, line-breaks, and a number of  special symbols (just email me to add your favourite).  \r\n\r\nIt has imap mappings that give you ampersands (&&), smart-quotes (single - &' and double &\"), <, > symbols,   and more.  It allow you to insert these and text descriptors or as numbers (for strict XML)\r\n\r\nYou can close the next open tag (alt-;) or close all open tags at that point (alt->).  \r\nNot you may need to remap these for other platforms.\r\n\r\n\r\nIf you have defined 'htmlcmd_AUTOCLOSE' then there is some reasonably intrusive code that will close open tags: \r\ntry typing this\r\n<p>Testing<b>bold<\/p>\r\n\r\nThis should automatically close the <b>\r\n\r\nYou can also generate a quick Table Of Contents for your document based on <H1>..<H6> headings.  There is a menu item to insert it.. and any options you give \r\nare remembered for when you re-generate the TOC. \r\n\r\nGenerateTOC( [<headingtypes>| * ]) \r\n:GenTOC [<headingtypes>| * ]\r\n\r\nThe optional argument is a string of types for each indent level. Eg. \" 1ai.\" would mean level 1 is default (bullet), level 2 is a numbered list, level 3 has letters and level three has roman numerals. \r\nIt uses references where it can find them, and generates new ones where it can't.\r\nThe arguments supplied are remembered so the TOC can be regenerated without resuplying them.\r\nIf * is supplied as an argument, the script prompts for arguments - showing what the current values are.\r\n\r\nWhen used with buffermenu.vim - Menus (for TOC generation) are local to the buffer.\r\n","4":"This script handles a number of mundane tasks in HTML \/ XML.  It allows you to create a default HTML header (Alt+0),  to define headings <h1> .. <h6> (Alt+1.. Alt+6), to toggle bold, italic, underline, paragraphs & kbd commands.  It gives shortcuts for ordered\/unordered lists and row definitions.  \r\n\r\nThe script has commands to insert horizontal rules, line-breaks, and a number of  special symbols (just email me to add your favourite).  \r\n\r\nIt has imap mappings that give you ampersands (&&), smart-quotes (single - &' and double &\"), <, > symbols,   and more.  It allow you to insert these and text descriptors or as numbers (for strict XML)\r\n\r\nYou can close the next open tag (alt-;) or close all open tags at that point (alt->).  \r\nNot you may need to remap these for other platforms.\r\n\r\n\r\nIf you have defined 'htmlcmd_AUTOCLOSE' then there is some reasonably intrusive code that will close open tags: \r\ntry typing this\r\n<p>Testing<b>bold<\/p>\r\n\r\nThis should automatically close the <b>\r\n\r\nYou can also generate a quick Table Of Contents for your document based on <H1>..<H6> headings.  There is a menu item to insert it.. and any options you give \r\nare remembered for when you re-generate the TOC. \r\n\r\nGenerateTOC( [<headingtypes>| * ]) \r\n:GenTOC [<headingtypes>| * ]\r\n\r\nThe optional argument is a string of types for each indent level. Eg. \" 1ai.\" would mean level 1 is default (bullet), level 2 is a numbered list, level 3 has letters and level three has roman numerals. \r\nIt uses references where it can find them, and generates new ones where it can't.\r\nThe arguments supplied are remembered so the TOC can be regenerated without resuplying them.\r\nIf * is supplied as an argument, the script prompts for arguments - showing what the current values are.\r\n\r\nWhen used with buffermenu.vim - Menus (for TOC generation) are local to the buffer.\r\n","install_details":"Use as a filetype plugin  (tip - make a directory ftplugin\/html and place it in there)\r\nThe menu can also work with buffermenu.vim.\r\n\r\nBy using buffoptions, this should work with version 5.7 and greater as the 6.0 specific plugin-style codes are stripped in the latest version of buffoptions.\r\n\r\n","5":"Use as a filetype plugin  (tip - make a directory ftplugin\/html and place it in there)\r\nThe menu can also work with buffermenu.vim.\r\n\r\nBy using buffoptions, this should work with version 5.7 and greater as the 6.0 specific plugin-style codes are stripped in the latest version of buffoptions.\r\n\r\n","first_name":"Michael","6":"Michael","last_name":"Geddes","7":"Geddes","releases":[{"0":"14","vim_version":"6.0","1":"6.0","script_version":"2.5","2":"2.5","version_comment":"Added more menus - made them useful for detaching, and able to\r\ncustomise the name.\r\n","3":"Added more menus - made them useful for detaching, and able to\r\ncustomise the name.\r\n","package":"htmlcmd.vim","4":"htmlcmd.vim","src_id":"1165","5":"1165","creation_date":"1030392077","6":"1030392077"},{"0":"14","vim_version":"6.0","1":"6.0","script_version":"2.4","2":"2.4","version_comment":"Command  :GenTOC added  (calls GenerateTOC)\r\nThis now remembers the arguments supplied so the TOC can be regenerated without resuplying them.\r\nAlso supports  * as an argument - providing a Prompt for arguments - showing what the current values are.","3":"Command  :GenTOC added  (calls GenerateTOC)\r\nThis now remembers the arguments supplied so the TOC can be regenerated without resuplying them.\r\nAlso supports  * as an argument - providing a Prompt for arguments - showing what the current values are.","package":"htmlcmd.vim","4":"htmlcmd.vim","src_id":"752","5":"752","creation_date":"1017855143","6":"1017855143"},{"0":"14","vim_version":"5.7","1":"5.7","script_version":"2.3","2":"2.3","version_comment":"Fixed some maps that didn't have <buffer> specifed.  Added <localleader> to replace ',' as prefix.  Updated the doco.\r\nChanged the insert-map of '>' to be NOT mapped - define htmlcmd_AUTOCLOSE to map it.\r\nI would like some feedback on the response speed for large documents - any noteable examples would be good.\r\nAlso  -- any users who need to make modifications due to their setup, I would be interested in hearing from.\r\nEmail supplied in script.","3":"Fixed some maps that didn't have <buffer> specifed.  Added <localleader> to replace ',' as prefix.  Updated the doco.\r\nChanged the insert-map of '>' to be NOT mapped - define htmlcmd_AUTOCLOSE to map it.\r\nI would like some feedback on the response speed for large documents - any noteable examples would be good.\r\nAlso  -- any users who need to make modifications due to their setup, I would be interested in hearing from.\r\nEmail supplied in script.","package":"htmlcmd.vim","4":"htmlcmd.vim","src_id":"698","5":"698","creation_date":"1016563832","6":"1016563832"},{"0":"14","vim_version":"6.0","1":"6.0","script_version":"2.2","2":"2.2","version_comment":"Have redone the auto-closing maps to make them a lot quicker.\r\nAdded <m-;> to close a single tag and <m-s-;> to close all tags.\r\nAdded a menu for Table Of Contents","3":"Have redone the auto-closing maps to make them a lot quicker.\r\nAdded <m-;> to close a single tag and <m-s-;> to close all tags.\r\nAdded a menu for Table Of Contents","package":"htmlcmd.vim","4":"htmlcmd.vim","src_id":"270","5":"270","creation_date":"1003033211","6":"1003033211"},{"0":"14","vim_version":"6.0","1":"6.0","script_version":"2.1","2":"2.1","version_comment":"Fixed bug that stopped this working as an ftplugin","3":"Fixed bug that stopped this working as an ftplugin","package":"htmlcmd.vim","4":"htmlcmd.vim","src_id":"80","5":"80","creation_date":"996689700","6":"996689700"}]},"13":{"script_id":"13","0":"13","script_name":"closetag.vim","1":"closetag.vim","script_type":"utility","2":"utility","summary":"Functions and mappings to close open HTML\/XML tags","3":"Functions and mappings to close open HTML\/XML tags","description":"This script eases redundant typing when writing html or xml files (even if you're very good with ctrl-p and ctrl-n  :).  Hitting ctrl-_ will initiate a search for the most recent open tag above that is not closed in the intervening space and then insert the matching close tag at the cursor.  In normal mode, the close tag is inserted one character after cursor rather than at it, as if a<C-_> had been used.  This allows putting close tags at the ends of lines while in normal mode, but disallows inserting them in the first column.\r\n                                                                              \r\nFor HTML, a configurable list of tags are ignored in the matching process.  By default, the following tags will not be matched and thus not closed automatically: Area, Base, Br, DD, DT, HR, Img, Input, LI, Link, Meta, P, and Param.\r\n                                                                              \r\nFor XML, all tags must have a closing match or be terminated by \/>, as in <empty-element\/>.  These empty element tags are ignored for matching.\r\n                                                                              \r\nComments are not currently handled very well, so commenting out HTML in certain ways may cause a \"tag mismatch\" message and no completion.  ie, having '<!-- a href=\"blah\">link!<\/a -->' between the cursor and the most recent open tag above doesn't work.  Well matched tags in comments don't cause a problem.\r\n","4":"This script eases redundant typing when writing html or xml files (even if you're very good with ctrl-p and ctrl-n  :).  Hitting ctrl-_ will initiate a search for the most recent open tag above that is not closed in the intervening space and then insert the matching close tag at the cursor.  In normal mode, the close tag is inserted one character after cursor rather than at it, as if a<C-_> had been used.  This allows putting close tags at the ends of lines while in normal mode, but disallows inserting them in the first column.\r\n                                                                              \r\nFor HTML, a configurable list of tags are ignored in the matching process.  By default, the following tags will not be matched and thus not closed automatically: Area, Base, Br, DD, DT, HR, Img, Input, LI, Link, Meta, P, and Param.\r\n                                                                              \r\nFor XML, all tags must have a closing match or be terminated by \/>, as in <empty-element\/>.  These empty element tags are ignored for matching.\r\n                                                                              \r\nComments are not currently handled very well, so commenting out HTML in certain ways may cause a \"tag mismatch\" message and no completion.  ie, having '<!-- a href=\"blah\">link!<\/a -->' between the cursor and the most recent open tag above doesn't work.  Well matched tags in comments don't cause a problem.\r\n","install_details":"To use, place this file in your standard vim scripts directory, and source it while editing the file you wish to close tags in.  If the filetype is not set or the file is some sort of template with embedded HTML, you may get HTML style tag matching by first setting the closetag_html_style global variable.  Otherwise, the default is XML style tag matching.\r\n                                                                              \r\nExample:\r\n  :let g:closetag_html_style=1\r\n  :source ~\/.vim\/scripts\/closetag.vim\r\n                                                                              \r\nFor greater convenience, load this script in an autocommand:\r\n  :au Filetype html,xml,xsl source ~\/.vim\/scripts\/closetag.vim\r\n                                                                              \r\nAlso, set noignorecase for html files or edit b:unaryTagsStack to match your capitalization style.  You may set this variable before or after loading the script, or simply change the file itself.","5":"To use, place this file in your standard vim scripts directory, and source it while editing the file you wish to close tags in.  If the filetype is not set or the file is some sort of template with embedded HTML, you may get HTML style tag matching by first setting the closetag_html_style global variable.  Otherwise, the default is XML style tag matching.\r\n                                                                              \r\nExample:\r\n  :let g:closetag_html_style=1\r\n  :source ~\/.vim\/scripts\/closetag.vim\r\n                                                                              \r\nFor greater convenience, load this script in an autocommand:\r\n  :au Filetype html,xml,xsl source ~\/.vim\/scripts\/closetag.vim\r\n                                                                              \r\nAlso, set noignorecase for html files or edit b:unaryTagsStack to match your capitalization style.  You may set this variable before or after loading the script, or simply change the file itself.","first_name":"Steven","6":"Steven","last_name":"Mueller","7":"Mueller","releases":[{"0":"13","vim_version":"6.0","1":"6.0","script_version":"0.9.1","2":"0.9.1","version_comment":"Bugfix release: Changed function names to be script-local to avoid conflicts with other scripts' stack implementations.\r\n","3":"Bugfix release: Changed function names to be script-local to avoid conflicts with other scripts' stack implementations.\r\n","package":"closetag.vim","4":"closetag.vim","src_id":"4318","5":"4318","creation_date":"1116943891","6":"1116943891"},{"0":"13","vim_version":"5.7","1":"5.7","script_version":"0.9","2":"0.9","version_comment":"Added synID()-based comment awareness:\r\nComment checking is now handled by vim's internal syntax checking.  Closing tags outside comments only matches non-commented tags.  Closing tags in comments matches only tags within comments, skipping blocks of normal code (wee!).  Can be really slow if syn sync minlines is large.  Set the b:closetag_disable_synID variable to disable comment contexts if it's too slow.\r\n\r\nNormal mode closetag now uses <C-R> in insert mode rather than p in normal mode:  Tag closing no longer clobbers the unnamed register, and (for vim 6.0) Doesn't modify the undo buffer when no change was made.  Made closetag_html_style variable buffer-local.  Improved documentation (hopefully).\r\n\r\nConfiguration Variables rundown:\r\n- b:unaryTagsStack            Buffer local string containing a whitespace seperated list of element names that should be ignored while finding matching closetags.  Checking is done according to the current setting of the ignorecase option.\r\n- b:closetag_html_style       Define this (as with let b:closetag_html_style=1) and source the script again to set the unaryTagsStack to its default value for html.\r\n- b:closetag_disable_synID    Define this to disable comment checking if tag closing is too slow.\r\n","3":"Added synID()-based comment awareness:\r\nComment checking is now handled by vim's internal syntax checking.  Closing tags outside comments only matches non-commented tags.  Closing tags in comments matches only tags within comments, skipping blocks of normal code (wee!).  Can be really slow if syn sync minlines is large.  Set the b:closetag_disable_synID variable to disable comment contexts if it's too slow.\r\n\r\nNormal mode closetag now uses <C-R> in insert mode rather than p in normal mode:  Tag closing no longer clobbers the unnamed register, and (for vim 6.0) Doesn't modify the undo buffer when no change was made.  Made closetag_html_style variable buffer-local.  Improved documentation (hopefully).\r\n\r\nConfiguration Variables rundown:\r\n- b:unaryTagsStack            Buffer local string containing a whitespace seperated list of element names that should be ignored while finding matching closetags.  Checking is done according to the current setting of the ignorecase option.\r\n- b:closetag_html_style       Define this (as with let b:closetag_html_style=1) and source the script again to set the unaryTagsStack to its default value for html.\r\n- b:closetag_disable_synID    Define this to disable comment checking if tag closing is too slow.\r\n","package":"closetag.vim","4":"closetag.vim","src_id":"18","5":"18","creation_date":"991965227","6":"991965227"},{"0":"13","vim_version":"5.7","1":"5.7","script_version":"0.8","2":"0.8","version_comment":"Initial upload","3":"Initial upload","package":"closetag.vim","4":"closetag.vim","src_id":"15","5":"15","creation_date":"991776732","6":"991776732"}]},"12":{"script_id":"12","0":"12","script_name":"ctags.vim","1":"ctags.vim","script_type":"utility","2":"utility","summary":"Display function name in the title bar.","3":"Display function name in the title bar.","description":"This script uses exuberant ctags to build the list of tags for the current file.  CursorHold event is then used to update titlestring.\r\n\r\nUpon sourcing an autocommand is created with event type CursorHold.  It updates the title string using the function GetTagName.  Another autocommand of type BufEnter is created to generate tags for *.c, *.cpp and *.h files.\r\n\r\nFunction GenerateTags builds an array of tag names.\r\n\r\nFunction GetTagName takes line number argument and returns the tag name.","4":"This script uses exuberant ctags to build the list of tags for the current file.  CursorHold event is then used to update titlestring.\r\n\r\nUpon sourcing an autocommand is created with event type CursorHold.  It updates the title string using the function GetTagName.  Another autocommand of type BufEnter is created to generate tags for *.c, *.cpp and *.h files.\r\n\r\nFunction GenerateTags builds an array of tag names.\r\n\r\nFunction GetTagName takes line number argument and returns the tag name.","install_details":"Before sourcing the script do:\r\n    let g:ctags_path='\/path\/to\/ctags'\r\n    let g:ctags_args='-I __declspec+'        (or whatever other additional arguments you want to pass to ctags)\r\n\r\n:CTAGS command starts the script.","5":"Before sourcing the script do:\r\n    let g:ctags_path='\/path\/to\/ctags'\r\n    let g:ctags_args='-I __declspec+'        (or whatever other additional arguments you want to pass to ctags)\r\n\r\n:CTAGS command starts the script.","first_name":"Alexey","6":"Alexey","last_name":"Marinichev","7":"Marinichev","releases":[{"0":"12","vim_version":"5.7","1":"5.7","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"ctags.vim","4":"ctags.vim","src_id":"14","5":"14","creation_date":"991747223","6":"991747223"}]},"11":{"script_id":"11","0":"11","script_name":"drawing.vim","1":"drawing.vim","script_type":"utility","2":"utility","summary":"Ascii drawing primitives with mouse in vim GUI (box, arrow, line). (unstable)","3":"Ascii drawing primitives with mouse in vim GUI (box, arrow, line). (unstable)","description":"Read script file for macro definition. You can draw some box, line or arrow\r\nby marking an area in visual mode in vim. Both corner of the visual selection\r\nare the point used for drawing.\r\n\r\nThe script is vim 5.4 compatible.","4":"Read script file for macro definition. You can draw some box, line or arrow\r\nby marking an area in visual mode in vim. Both corner of the visual selection\r\nare the point used for drawing.\r\n\r\nThe script is vim 5.4 compatible.","install_details":"soucre the file in vim.","5":"soucre the file in vim.","first_name":"Sylvain","6":"Sylvain","last_name":"Viart","7":"Viart","releases":[{"0":"11","vim_version":"5.7","1":"5.7","script_version":"0.1u","2":"0.1u","version_comment":"Initial upload","3":"Initial upload","package":"drawing.vim","4":"drawing.vim","src_id":"13","5":"13","creation_date":"991728183","6":"991728183"}]},"10":{"script_id":"10","0":"10","script_name":"fortune.vim","1":"fortune.vim","script_type":"utility","2":"utility","summary":"put a signature file at end of e-mail (BRAM)","3":"put a signature file at end of e-mail (BRAM)","description":"This macro will add a signature (from\r\n~\/.fortunes) to the end of a file.\r\n(preferably an e-mail) This script\r\nwas copied from a macro from:\r\nhttp:\/\/www.moolenaar.net which was\r\nmade by Bram Moolenaar.  I changed it\r\nso it would stick on the sig then\r\nquit.","4":"This macro will add a signature (from\r\n~\/.fortunes) to the end of a file.\r\n(preferably an e-mail) This script\r\nwas copied from a macro from:\r\nhttp:\/\/www.moolenaar.net which was\r\nmade by Bram Moolenaar.  I changed it\r\nso it would stick on the sig then\r\nquit.","install_details":"just put this at the end of your .vimrc:\r\n\r\n     $ cat fortune.vim >> ~\/.vimrc\r\n\r\nor source it from your .vimrc:\r\n\r\n     $ cat fortune.vim | tail\r\n\r\n        ...\r\n        source fortune.vim\r\n","5":"just put this at the end of your .vimrc:\r\n\r\n     $ cat fortune.vim >> ~\/.vimrc\r\n\r\nor source it from your .vimrc:\r\n\r\n     $ cat fortune.vim | tail\r\n\r\n        ...\r\n        source fortune.vim\r\n","first_name":"adam","6":"adam","last_name":"seyfarth","7":"seyfarth","releases":[{"0":"10","vim_version":"6.0","1":"6.0","script_version":"1.5","2":"1.5","version_comment":"much much better in general, moved to a function...\r\nadded rotating, to make sure not to offend people :-)","3":"much much better in general, moved to a function...\r\nadded rotating, to make sure not to offend people :-)","package":"fortune.vim","4":"fortune.vim","src_id":"142","5":"142","creation_date":"999086070","6":"999086070"},{"0":"10","vim_version":"5.7","1":"5.7","script_version":"0.5","2":"0.5","version_comment":"Initial upload","3":"Initial upload","package":"fortune.vim","4":"fortune.vim","src_id":"11","5":"11","creation_date":"991667008","6":"991667008"}]},"9":{"script_id":"9","0":"9","script_name":"buffoptions.vim","1":"buffoptions.vim","script_type":"utility","2":"utility","summary":"Per-buffer options\/menus\/maps","3":"Per-buffer options\/menus\/maps","description":"BuffOptions.vim - Per-buffer options and mappings\r\nIntroduction:\r\nSome of Vim's options are set per-buffer, but not all. This extension allows you to set any options and also mappings for a particular buffer or filetype.\r\n\r\nThe idea is that you push options onto a stack (the old values are in fact what are pushed) with PushOption( ... ) and then restore the values with RestoreOptions(). \r\n\r\nAn extension to the filetypes allow easy use of these macros for a specific filetype. The autocommands filetypeEnter and filetypeLeave have been added.\r\n\r\nBase Commands:\r\nPushOption( option1|map1|menu1|abbrev1, value1, ...) - Push any number option\/value pairs where: \r\noptionn is a vim 'option' name. \r\nmapn is a map of the form '{n|v|o|i|c}map <lhs>' defining what kind of map is being defined (mandatory with multiple allowed) \r\nabbrevn is an insert mode abbreviation - the abbreviation is set by push and deleted by RestoreOptions() (as it is not possible to silently check for original abbreviations). \r\nmenun is a menu setting of the form '{a|n|v|o|i|c}menu <lhs>' defining where the menu is available. <lhs> can include the position of the menu (eg '100.100 Tools.Test') \r\nvaluen is the value or mapping to set. \r\nRestoreOptions() - Restore all options to their previous value \r\nautocomd User filetypeEnter - Called on 'BufEnter' of a file of filetype. \r\nautocomd User filetypeLeave - Called on 'BufLeave' of a file of filetype. \r\nReadFileTypeMap(types, filename) - Source filename with per-buffer map\/menu options defaulting to the specified list offiletypes. Lines of the form: \r\n\" FileTypes: cpp\r\nExample:\r\n\r\naug specialEdit\r\nau!\r\nau User sgmlEnter call PushOptions(\"keywordprg\",\"\/bin\/htmlkey\")\r\nau User cEnter call PushOptions(\"breakat\",\". )&|\",  \"complete\",\".,k\/usr\/dict,]\",  \"nmap <c-enter>\",\"<esc>o\")\r\nau User cEnter call PushOptions(\"amenu 10.100 Tools.Compile\\\\ C\",\":make<cr>\" )\r\n\r\nau User sgmlLeave,cLeave  call RestoreOptions()\r\naug END\r\n\r\n\r\nPer File mappings\r\nThis is not really recommended, as it gives the document virus a foot in... so be warned.\r\n\r\nGetOptionsFromFile(comment) is a little trick to allow mappings defined for a particular file within the file. The lines recognized are of the form:\r\n\r\n<comment>vimexe: <arguments>\r\n\r\nwhere the arguments are the same as for PushOption. And Comment is passed as an argument.\r\n\r\nDespite the given example, I would recomend that you map a key to parse the options from a file initially.\r\n\r\nNote that the options are cached, so once read, you would have to unlet b:VIMEXE to be able to get it to reparse.\r\n\r\n\r\naug MyOpts\r\nau!\r\nau User vimEnter call GetOptionsFromFile('\"')\r\nau User vimLeave call RestoreOptions() \r\naug END\r\n\r\nMappings from filetype files\r\nFor when you have a file that is used for the mappings for a particular filetype.\r\nAll lines in the file except those starting with map and menu will get executed. Any maps\/menus will get inserted into a BuffOption() for the specified filetype \r\n\r\nCommands:\r\nFTExe(Filetypes, command) - Have mapping\/menu command executed as a per-buffer option for the specified (comma separated) filetypes \r\nReadFileTypeMap(filetypes,filename) - Sets all map\/menu entries existing in filename to be specific to the filetypes specified and executes all other lines. Comment lines of the form: \r\n\"FileTypes: cpp,c,rc,idl\r\n\r\nwill cause the following maps\/menus to be for the specified filetypes. A blank filetype string causes the maps\/menus to be executed immediately.\r\n\r\nThis implementation requires the existance of buffoptions_mac.vim in the same directory as buffoptions.vim\r\nThe source code for that is in an if 0 block at the bottom of buffoptions.vim\r\n\r\n:SO filename - Call ReadFileTypeMap with blank original filetypes. \r\nExample:\r\nlet filename =$home.'\/vim\/txtsettings.vim'\r\ncall ReadFileTypeMap('txt',filename)\r\nSO ~\/vim\/txtsettings.vim\r\n","4":"BuffOptions.vim - Per-buffer options and mappings\r\nIntroduction:\r\nSome of Vim's options are set per-buffer, but not all. This extension allows you to set any options and also mappings for a particular buffer or filetype.\r\n\r\nThe idea is that you push options onto a stack (the old values are in fact what are pushed) with PushOption( ... ) and then restore the values with RestoreOptions(). \r\n\r\nAn extension to the filetypes allow easy use of these macros for a specific filetype. The autocommands filetypeEnter and filetypeLeave have been added.\r\n\r\nBase Commands:\r\nPushOption( option1|map1|menu1|abbrev1, value1, ...) - Push any number option\/value pairs where: \r\noptionn is a vim 'option' name. \r\nmapn is a map of the form '{n|v|o|i|c}map <lhs>' defining what kind of map is being defined (mandatory with multiple allowed) \r\nabbrevn is an insert mode abbreviation - the abbreviation is set by push and deleted by RestoreOptions() (as it is not possible to silently check for original abbreviations). \r\nmenun is a menu setting of the form '{a|n|v|o|i|c}menu <lhs>' defining where the menu is available. <lhs> can include the position of the menu (eg '100.100 Tools.Test') \r\nvaluen is the value or mapping to set. \r\nRestoreOptions() - Restore all options to their previous value \r\nautocomd User filetypeEnter - Called on 'BufEnter' of a file of filetype. \r\nautocomd User filetypeLeave - Called on 'BufLeave' of a file of filetype. \r\nReadFileTypeMap(types, filename) - Source filename with per-buffer map\/menu options defaulting to the specified list offiletypes. Lines of the form: \r\n\" FileTypes: cpp\r\nExample:\r\n\r\naug specialEdit\r\nau!\r\nau User sgmlEnter call PushOptions(\"keywordprg\",\"\/bin\/htmlkey\")\r\nau User cEnter call PushOptions(\"breakat\",\". )&|\",  \"complete\",\".,k\/usr\/dict,]\",  \"nmap <c-enter>\",\"<esc>o\")\r\nau User cEnter call PushOptions(\"amenu 10.100 Tools.Compile\\\\ C\",\":make<cr>\" )\r\n\r\nau User sgmlLeave,cLeave  call RestoreOptions()\r\naug END\r\n\r\n\r\nPer File mappings\r\nThis is not really recommended, as it gives the document virus a foot in... so be warned.\r\n\r\nGetOptionsFromFile(comment) is a little trick to allow mappings defined for a particular file within the file. The lines recognized are of the form:\r\n\r\n<comment>vimexe: <arguments>\r\n\r\nwhere the arguments are the same as for PushOption. And Comment is passed as an argument.\r\n\r\nDespite the given example, I would recomend that you map a key to parse the options from a file initially.\r\n\r\nNote that the options are cached, so once read, you would have to unlet b:VIMEXE to be able to get it to reparse.\r\n\r\n\r\naug MyOpts\r\nau!\r\nau User vimEnter call GetOptionsFromFile('\"')\r\nau User vimLeave call RestoreOptions() \r\naug END\r\n\r\nMappings from filetype files\r\nFor when you have a file that is used for the mappings for a particular filetype.\r\nAll lines in the file except those starting with map and menu will get executed. Any maps\/menus will get inserted into a BuffOption() for the specified filetype \r\n\r\nCommands:\r\nFTExe(Filetypes, command) - Have mapping\/menu command executed as a per-buffer option for the specified (comma separated) filetypes \r\nReadFileTypeMap(filetypes,filename) - Sets all map\/menu entries existing in filename to be specific to the filetypes specified and executes all other lines. Comment lines of the form: \r\n\"FileTypes: cpp,c,rc,idl\r\n\r\nwill cause the following maps\/menus to be for the specified filetypes. A blank filetype string causes the maps\/menus to be executed immediately.\r\n\r\nThis implementation requires the existance of buffoptions_mac.vim in the same directory as buffoptions.vim\r\nThe source code for that is in an if 0 block at the bottom of buffoptions.vim\r\n\r\n:SO filename - Call ReadFileTypeMap with blank original filetypes. \r\nExample:\r\nlet filename =$home.'\/vim\/txtsettings.vim'\r\ncall ReadFileTypeMap('txt',filename)\r\nSO ~\/vim\/txtsettings.vim\r\n","install_details":"Need to create buffoptions_mac.vim - the source is included inside buffoptions.vim.\r\n","5":"Need to create buffoptions_mac.vim - the source is included inside buffoptions.vim.\r\n","first_name":"Michael","6":"Michael","last_name":"Geddes","7":"Geddes","releases":[{"0":"9","vim_version":"5.7","1":"5.7","script_version":"2.1","2":"2.1","version_comment":"Allow sourced scripts to have <buffer> tags and <SID>  so that scripts can behave as file-type plugins for vim 6 as well as buffoptions SOURCE scripts for 5.6 and above.\r\nNote that the buffoptions_mac.vim will need to be recreated (extract it from the bottom of the file).","3":"Allow sourced scripts to have <buffer> tags and <SID>  so that scripts can behave as file-type plugins for vim 6 as well as buffoptions SOURCE scripts for 5.6 and above.\r\nNote that the buffoptions_mac.vim will need to be recreated (extract it from the bottom of the file).","package":"buffoptions.vim","4":"buffoptions.vim","src_id":"17","5":"17","creation_date":"991939639","6":"991939639"},{"0":"9","vim_version":"5.7","1":"5.7","script_version":"2.0","2":"2.0","version_comment":"Initial upload","3":"Initial upload","package":"buffoptions.vim","4":"buffoptions.vim","src_id":"10","5":"10","creation_date":"991612906","6":"991612906"}]},"8":{"script_id":"8","0":"8","script_name":"vimbuddy.vim","1":"vimbuddy.vim","script_type":"utility","2":"utility","summary":"Vimbuddy: An absolutely unuseful little thing","3":"Vimbuddy: An absolutely unuseful little thing","description":"Puts a smiley on your status line. Nose will rotate on <Left> and <Right>\r\nWill frown on errors and warnings","4":"Puts a smiley on your status line. Nose will rotate on <Left> and <Right>\r\nWill frown on errors and warnings","install_details":"Source vimbuddy.vim from your .vimrc or put into plugin\/ \r\nthen put the string \"%{VimBuddy()}\" into your 'statusline'","5":"Source vimbuddy.vim from your .vimrc or put into plugin\/ \r\nthen put the string \"%{VimBuddy()}\" into your 'statusline'","first_name":"Flemming","6":"Flemming","last_name":"Madsen","7":"Madsen","releases":[{"0":"8","vim_version":"7.0","1":"7.0","script_version":"0.9.2","2":"0.9.2","version_comment":"Ported to vim 7 (variable names fixed)","3":"Ported to vim 7 (variable names fixed)","package":"vimbuddy.vim","4":"vimbuddy.vim","src_id":"7481","5":"7481","creation_date":"1186703456","6":"1186703456"},{"0":"8","vim_version":"5.7","1":"5.7","script_version":"0.9.1","2":"0.9.1","version_comment":"Allow manual call without failing. Forgot the % in usage","3":"Allow manual call without failing. Forgot the % in usage","package":"vimbuddy.vim","4":"vimbuddy.vim","src_id":"806","5":"806","creation_date":"1019433467","6":"1019433467"},{"0":"8","vim_version":"5.7","1":"5.7","script_version":"0.9","2":"0.9","version_comment":"Initial upload","3":"Initial upload","package":"vimbuddy.vim","4":"vimbuddy.vim","src_id":"9","5":"9","creation_date":"991350758","6":"991350758"}]},"7":{"script_id":"7","0":"7","script_name":"ifdef highlighting","1":"ifdef highlighting","script_type":"syntax","2":"syntax","summary":"#ifdef highlighting in c\/c++\/idl","3":"#ifdef highlighting in c\/c++\/idl","description":"Provides highlighting for  #ifdef  #ifndef  #else  #endif  blocks, with the ability to mark a symbol as defined or undefined.\r\nHandles nesting of #ifdefs (and #if) as well, but does not handle  #if defined().\r\n\r\nSupports vim_ifdef:  modelines and .defines (_defines for win16\/win32s) files to specify defined\/undefined symbols.\r\n\r\nuse :Define <keyword>  or  :Undefine <keyword>     to dynamically specify defined or undefined sections.","4":"Provides highlighting for  #ifdef  #ifndef  #else  #endif  blocks, with the ability to mark a symbol as defined or undefined.\r\nHandles nesting of #ifdefs (and #if) as well, but does not handle  #if defined().\r\n\r\nSupports vim_ifdef:  modelines and .defines (_defines for win16\/win32s) files to specify defined\/undefined symbols.\r\n\r\nuse :Define <keyword>  or  :Undefine <keyword>     to dynamically specify defined or undefined sections.","install_details":"Place in syntax\/ directory within your runtime path.\r\n\r\nCan be invoked by appending .ifdef to your syntax. \r\neg with a modeline   vim: syntax=c.ifdef\r\n\r\nAlternatively, call from a syntax file after\/syntax\/c.vim (or cpp.vim or idl.vim)\r\n","5":"Place in syntax\/ directory within your runtime path.\r\n\r\nCan be invoked by appending .ifdef to your syntax. \r\neg with a modeline   vim: syntax=c.ifdef\r\n\r\nAlternatively, call from a syntax file after\/syntax\/c.vim (or cpp.vim or idl.vim)\r\n","first_name":"Michael","6":"Michael","last_name":"Geddes","7":"Geddes","releases":[{"0":"7","vim_version":"7.0","1":"7.0","script_version":"3.2","2":"3.2","version_comment":"Fix from Dr Chip (handle closing *\/ on next line after #ifdef)","3":"Fix from Dr Chip (handle closing *\/ on next line after #ifdef)","package":"ifdef.vim","4":"ifdef.vim","src_id":"16097","5":"16097","creation_date":"1311076157","6":"1311076157"},{"0":"7","vim_version":"7.0","1":"7.0","script_version":"3.1","2":"3.1","version_comment":"- Wu Hong fixed bug in Undefine() colouring\r\n- Stop errors in script due to undefined hl being cleared.\r\n- Added :Define, :Undefine with completion\r\n","3":"- Wu Hong fixed bug in Undefine() colouring\r\n- Stop errors in script due to undefined hl being cleared.\r\n- Added :Define, :Undefine with completion\r\n","package":"ifdef.vim","4":"ifdef.vim","src_id":"16021","5":"16021","creation_date":"1309661324","6":"1309661324"},{"0":"7","vim_version":"6.0","1":"6.0","script_version":"3.0","2":"3.0","version_comment":"- Renamed everything to be more clear, and reversed some of the include\ngroups from exclude groups \n\n- make use of ALL in groups. This seems to have fixed most bugs, but may have reintroduced some as well, however doing it this way round should prevent most interaction with other scripts.\n\n- Actually clear the cPreCondit highlight gtoup as we are taking it over.\n  Ditto cCppOut (#if 0) handling","3":"- Renamed everything to be more clear, and reversed some of the include\ngroups from exclude groups \n\n- make use of ALL in groups. This seems to have fixed most bugs, but may have reintroduced some as well, however doing it this way round should prevent most interaction with other scripts.\n\n- Actually clear the cPreCondit highlight gtoup as we are taking it over.\n  Ditto cCppOut (#if 0) handling","package":"ifdef.vim","4":"ifdef.vim","src_id":"3305","5":"3305","creation_date":"1091829523","6":"1091829523"},{"0":"7","vim_version":"6.0","1":"6.0","script_version":"2.3","2":"2.3","version_comment":"- Clean up some of the comments\r\n- Add comments for hilighting groups.\r\n- Ignore whitespace in .defines files. (TODO: Credit person who suggested this!)\r\n","3":"- Clean up some of the comments\r\n- Add comments for hilighting groups.\r\n- Ignore whitespace in .defines files. (TODO: Credit person who suggested this!)\r\n","package":"ifdef.vim","4":"ifdef.vim","src_id":"2706","5":"2706","creation_date":"1075650057","6":"1075650057"},{"0":"7","vim_version":"6.0","1":"6.0","script_version":"2.2","2":"2.2","version_comment":"- Add support for idl files.\r\n- Suggestions from ??? (let me know if this was you)\r\n    - Check for \\'shell\\' type and \\'shellslash\\'\r\n    - Don\\'t use has(\\\"windows\\\")\r\n","3":"- Add support for idl files.\r\n- Suggestions from ??? (let me know if this was you)\r\n    - Check for \\'shell\\' type and \\'shellslash\\'\r\n    - Don\\'t use has(\\\"windows\\\")\r\n","package":"ifdef.vim","4":"ifdef.vim","src_id":"2694","5":"2694","creation_date":"1075401033","6":"1075401033"},{"0":"7","vim_version":"6.0","1":"6.0","script_version":"2.1","2":"2.1","version_comment":"Minor bugfixes (use :p modifier in getting directory)\r\n- suggestions from Erik R.  \r\nDocumentation updates","3":"Minor bugfixes (use :p modifier in getting directory)\r\n- suggestions from Erik R.  \r\nDocumentation updates","package":"ifdef.vim","4":"ifdef.vim","src_id":"1594","5":"1594","creation_date":"1041436949","6":"1041436949"},{"0":"7","vim_version":"6.0","1":"6.0","script_version":"2.0","2":"2.0","version_comment":"- Added loading of ifdefs\r\n  - via ifdef modelines\r\n  - via .defines files\r\n- Added missing highlight link.. relinked ifdefed out comments to Debug\r\n- Conditional loading of functions\r\n","3":"- Added loading of ifdefs\r\n  - via ifdef modelines\r\n  - via .defines files\r\n- Added missing highlight link.. relinked ifdefed out comments to Debug\r\n- Conditional loading of functions\r\n","package":"ifdef.vim","4":"ifdef.vim","src_id":"1588","5":"1588","creation_date":"1041186158","6":"1041186158"},{"0":"7","vim_version":"6.0","1":"6.0","script_version":"1.3","2":"1.3","version_comment":"Fix up some group names so colours get picked up.","3":"Fix up some group names so colours get picked up.","package":"ifdef.vim","4":"ifdef.vim","src_id":"1562","5":"1562","creation_date":"1040236660","6":"1040236660"}]},"6":{"script_id":"6","0":"6","script_name":"keepcase.vim","1":"keepcase.vim","script_type":"utility","2":"utility","summary":"Functions for doing case-persistant substitutions","3":"Functions for doing case-persistant substitutions","description":"Usage: Using KeepCase or KeepCaseSameLen defined here, do a substitution like this:\r\n\r\n%s\/\\u\\<old_word\\>\/\\=KeepCaseSameLen(submatch(0), 'new_word')\/g\r\n\r\n* KeepCase( original_word , new_word )  \r\n  returns the new word maintaining case \r\n  simply uses heuristics to work out some different common situations\r\n    given   NewWord\r\n    Word   \t--> Newword\r\n    WORD    --> NEWWORD\r\n    word    --> newword\r\n    WoRd    --> NewWord\r\n    woRd    --> newWord\r\n\r\n* KeepCaseSameLen( original_word , new_word )    \r\n\tReturns the new word maintaining case\r\n\t  Keeps the case exactly the same letter-for-letter\r\n\t  It does work if the words aren't the same length, as it truncates or\r\n\t  just coppies the case of the word for the length of the original word.\r\n\r\n* :SubstituteCase#\\ctoto\\(Titi\\)tata#\\1Tutu#g\r\n     totoTitiTata -> titiTutu\r\n     TotoTitiTata -> TitiTutu\r\n     tototititata -> tititutu\r\n     tototitiTata -> titiTutu\r\n     TototitiTata -> TitiTutu\r\n","4":"Usage: Using KeepCase or KeepCaseSameLen defined here, do a substitution like this:\r\n\r\n%s\/\\u\\<old_word\\>\/\\=KeepCaseSameLen(submatch(0), 'new_word')\/g\r\n\r\n* KeepCase( original_word , new_word )  \r\n  returns the new word maintaining case \r\n  simply uses heuristics to work out some different common situations\r\n    given   NewWord\r\n    Word   \t--> Newword\r\n    WORD    --> NEWWORD\r\n    word    --> newword\r\n    WoRd    --> NewWord\r\n    woRd    --> newWord\r\n\r\n* KeepCaseSameLen( original_word , new_word )    \r\n\tReturns the new word maintaining case\r\n\t  Keeps the case exactly the same letter-for-letter\r\n\t  It does work if the words aren't the same length, as it truncates or\r\n\t  just coppies the case of the word for the length of the original word.\r\n\r\n* :SubstituteCase#\\ctoto\\(Titi\\)tata#\\1Tutu#g\r\n     totoTitiTata -> titiTutu\r\n     TotoTitiTata -> TitiTutu\r\n     tototititata -> tititutu\r\n     tototitiTata -> titiTutu\r\n     TototitiTata -> TitiTutu\r\n","install_details":"Place in plugin directory","5":"Place in plugin directory","first_name":"Michael","6":"Michael","last_name":"Geddes","7":"Geddes","releases":[{"0":"6","vim_version":"6.0","1":"6.0","script_version":"2.0","2":"2.0","version_comment":"Version from Luc Hermitte.  Includes :SubstituteCase command as well as some extra cases handled.","3":"Version from Luc Hermitte.  Includes :SubstituteCase command as well as some extra cases handled.","package":"keepcase.vim","4":"keepcase.vim","src_id":"6942","5":"6942","creation_date":"1175665618","6":"1175665618"},{"0":"6","vim_version":"6.0","1":"6.0","script_version":"1.1","2":"1.1","version_comment":"Initial upload","3":"Initial upload","package":"keepcase.vim","4":"keepcase.vim","src_id":"7","5":"7","creation_date":"991172832","6":"991172832"}]},"5":{"script_id":"5","0":"5","script_name":"DoxyGen Syntax","1":"DoxyGen Syntax","script_type":"syntax","2":"syntax","summary":"DoxyGen Highlighting on top of c\/c++\/java","3":"DoxyGen Highlighting on top of c\/c++\/java","description":"This Script has been moved into Vim7.\r\n\r\n:set syntax=cpp.doxygen\r\n\r\nProvides DoxyGen Highlighting on top of c\/c++\/idl\/java.  DoxyGen is close to JavaDoc that it should be fine for JavaDoc as well.  It supports most of the keywords in DoxyGen in one way or another.\r\n\r\nThere may be some problems where doxygen tags need to be included in exclusion groups of the c\/c++\/java\/idl files.\r\n\r\nAt the moment, it uses non-conventional colours, which I think is good, as it differentiates it from the source-code.  Please let me know if your opinion differs, especially if you have a set of standard defaults that would be appropriate.\r\n","4":"This Script has been moved into Vim7.\r\n\r\n:set syntax=cpp.doxygen\r\n\r\nProvides DoxyGen Highlighting on top of c\/c++\/idl\/java.  DoxyGen is close to JavaDoc that it should be fine for JavaDoc as well.  It supports most of the keywords in DoxyGen in one way or another.\r\n\r\nThere may be some problems where doxygen tags need to be included in exclusion groups of the c\/c++\/java\/idl files.\r\n\r\nAt the moment, it uses non-conventional colours, which I think is good, as it differentiates it from the source-code.  Please let me know if your opinion differs, especially if you have a set of standard defaults that would be appropriate.\r\n","install_details":"Needs to be sourced after the language files.\r\n To detect *.doxygen files as being doxygen, make the file\r\n ---------8<----------- .vim\\ftdetect\\doxygen.vim -----------\r\n  au BufNewFile,BufRead *.doxygen setfiletype doxygen\r\n ------------------------------------------------------------\r\n There are a few ways to add doxygen syntax hilighting to c,cpp,idl files,\r\n 1: create files .vim\/syntax\/c.vim  .vim\/syntax\/cpp.vim .vim\/syntax\/ which\r\n load the original syntax before loading doxygen.vim syntax hilighting.\r\n                                                                           \r\n 2: Before :syntax on in your _vimrc, put\r\n let mysyntaxfile='<some_path>\/doxygen_load.vim'\r\n and then create the following file.\r\n -----------8<--------- <some_path>\/doxygen_load.vim --------\r\n au! Syntax {cpp,c,idl}\r\n au Syntax {cpp,c,idl} runtime syntax\/doxygen.vim\r\n ------------------------------------------------------------","5":"Needs to be sourced after the language files.\r\n To detect *.doxygen files as being doxygen, make the file\r\n ---------8<----------- .vim\\ftdetect\\doxygen.vim -----------\r\n  au BufNewFile,BufRead *.doxygen setfiletype doxygen\r\n ------------------------------------------------------------\r\n There are a few ways to add doxygen syntax hilighting to c,cpp,idl files,\r\n 1: create files .vim\/syntax\/c.vim  .vim\/syntax\/cpp.vim .vim\/syntax\/ which\r\n load the original syntax before loading doxygen.vim syntax hilighting.\r\n                                                                           \r\n 2: Before :syntax on in your _vimrc, put\r\n let mysyntaxfile='<some_path>\/doxygen_load.vim'\r\n and then create the following file.\r\n -----------8<--------- <some_path>\/doxygen_load.vim --------\r\n au! Syntax {cpp,c,idl}\r\n au Syntax {cpp,c,idl} runtime syntax\/doxygen.vim\r\n ------------------------------------------------------------","first_name":"Michael","6":"Michael","last_name":"Geddes","7":"Geddes","releases":[{"0":"5","vim_version":"6.0","1":"6.0","script_version":"1.15","2":"1.15","version_comment":"1. \u00c2\u00a0Words like `Class#Member' is highlighted together as a link in my\r\n\u00c2\u00a0 \u00c2\u00a0 version.\r\n2. \u00c2\u00a0I used `doxygenHyperLink' instead of `doxygenHttpLink' and\r\n\u00c2\u00a0 \u00c2\u00a0 highlighted http, https, and ftp protocols.\r\n3. \u00c2\u00a0I added the missing `doxygenSpecialArgumentWord' to make `\\a' (not\r\n\u00c2\u00a0 \u00c2\u00a0 the word after) appear the same way as `\\c'.\r\n4. \u00c2\u00a0I made some adjustments in font choosing on non-Windows platforms.\r\n5. \u00c2\u00a0The `Last Change' date is not updated in your file.\r\n6. \u00c2\u00a0There are some trailing spaces in your file.","3":"1. \u00c2\u00a0Words like `Class#Member' is highlighted together as a link in my\r\n\u00c2\u00a0 \u00c2\u00a0 version.\r\n2. \u00c2\u00a0I used `doxygenHyperLink' instead of `doxygenHttpLink' and\r\n\u00c2\u00a0 \u00c2\u00a0 highlighted http, https, and ftp protocols.\r\n3. \u00c2\u00a0I added the missing `doxygenSpecialArgumentWord' to make `\\a' (not\r\n\u00c2\u00a0 \u00c2\u00a0 the word after) appear the same way as `\\c'.\r\n4. \u00c2\u00a0I made some adjustments in font choosing on non-Windows platforms.\r\n5. \u00c2\u00a0The `Last Change' date is not updated in your file.\r\n6. \u00c2\u00a0There are some trailing spaces in your file.","package":"doxygen.zip","4":"doxygen.zip","src_id":"4884","5":"4884","creation_date":"1134352933","6":"1134352933"},{"0":"5","vim_version":"6.0","1":"6.0","script_version":"1.14","2":"1.14","version_comment":"Fixed up  \\c words ending in )  (Wu Yongwei)\r\n - With auto-brief \/\/!< followed by \/** shouldn't supress the auto-brief in   the \/**. (Reported by Markus Trenkwalder)\r\n - Allow numbers in @link linkwords (Reporeted by Wu Yongwei)\r\n- Don't treat # preceded by a word-end as a Hash-special (Reported by Wu Yongwei)\r\n- include # (@c #include) in the small-specials allowed chars. (Wu  Yongwei)\r\n - Highlight http[s] links (Wu Yongwei)\r\n - Various (Wu Yongwei)","3":"Fixed up  \\c words ending in )  (Wu Yongwei)\r\n - With auto-brief \/\/!< followed by \/** shouldn't supress the auto-brief in   the \/**. (Reported by Markus Trenkwalder)\r\n - Allow numbers in @link linkwords (Reporeted by Wu Yongwei)\r\n- Don't treat # preceded by a word-end as a Hash-special (Reported by Wu Yongwei)\r\n- include # (@c #include) in the small-specials allowed chars. (Wu  Yongwei)\r\n - Highlight http[s] links (Wu Yongwei)\r\n - Various (Wu Yongwei)","package":"doxygen.zip","4":"doxygen.zip","src_id":"4702","5":"4702","creation_date":"1130408255","6":"1130408255"},{"0":"5","vim_version":"6.0","1":"6.0","script_version":"1.12","2":"1.12","version_comment":"- Fixed up ending of brief lines with respect to line @ commands and  end-comment. Not ending a brief no longer produces an error-comment.\r\n\r\n","3":"- Fixed up ending of brief lines with respect to line @ commands and  end-comment. Not ending a brief no longer produces an error-comment.\r\n\r\n","package":"doxygen.zip","4":"doxygen.zip","src_id":"3802","5":"3802","creation_date":"1106829006","6":"1106829006"},{"0":"5","vim_version":"6.0","1":"6.0","script_version":"1.11","2":"1.11","version_comment":"   - Allow doxygen comments inside brackets (Suggested by Zygmunt Krynicki)\r\n   - Restore correct font selection (Wu Yongwei)\r\n   - Don't end brief when encountering ? or ! as this isn't what happens with doxygen.\r\n   - Make punctuation an option.\r\n   - Make short words end with a , eg \\c word,  (Wu Yongwei)\r\n1.11\r\n   - Thanks to Joseph Barker for pointing out that I had a syntax error in  1.10\r\n","3":"   - Allow doxygen comments inside brackets (Suggested by Zygmunt Krynicki)\r\n   - Restore correct font selection (Wu Yongwei)\r\n   - Don't end brief when encountering ? or ! as this isn't what happens with doxygen.\r\n   - Make punctuation an option.\r\n   - Make short words end with a , eg \\c word,  (Wu Yongwei)\r\n1.11\r\n   - Thanks to Joseph Barker for pointing out that I had a syntax error in  1.10\r\n","package":"doxygen.zip","4":"doxygen.zip","src_id":"3797","5":"3797","creation_date":"1106676131","6":"1106676131"},{"0":"5","vim_version":"6.0","1":"6.0","script_version":"1.9","2":"1.9","version_comment":"Thanks to Toby Allsopp for this version:\r\n - Allow javadoc style auto-brief to be disabled\r\n - Move various definitions from single to multiline definitions \r\nAlso added the .txt help file.\r\n","3":"Thanks to Toby Allsopp for this version:\r\n - Allow javadoc style auto-brief to be disabled\r\n - Move various definitions from single to multiline definitions \r\nAlso added the .txt help file.\r\n","package":"doxygen.zip","4":"doxygen.zip","src_id":"3751","5":"3751","creation_date":"1105142287","6":"1105142287"},{"0":"5","vim_version":"6.0","1":"6.0","script_version":"1.8","2":"1.8","version_comment":" - Fix up some regions not marked as contained (code, verbatim, dot being\n highlighted outside of the doxygen region) (Toby Allsopp)\n - Only mark recognised HTML tags (Suggested by Mike Anderson)\n","3":" - Fix up some regions not marked as contained (code, verbatim, dot being\n highlighted outside of the doxygen region) (Toby Allsopp)\n - Only mark recognised HTML tags (Suggested by Mike Anderson)\n","package":"doxygen.vim","4":"doxygen.vim","src_id":"3695","5":"3695","creation_date":"1102704487","6":"1102704487"},{"0":"5","vim_version":"6.0","1":"6.0","script_version":"1.7","2":"1.7","version_comment":"  - Ignore Errors when loading from idl.\r\n  - Try and match # and \\c &c support to match what really happens. (Reported by Wu Yongwei)\r\n  - Don't go into doxygen mode for \/**\/\r\n  - Fix up syncing of brief after a \\def or similar line - character\r\n    immediately following a leading asterisk were being hilighted long.\r\n  - Try and work out a better default font for \\c\r\n  - add support for \\code \\endcode \\verbatim \\endverbatim (no contained elements) (suggested Yongwei)\r\n  - add contained support for dot (\\dot \\enddot)\r\n  - support html <!-- --> comments.\r\n  - support for params inside \\c \\ref brackets (can contain spaces?).\r\n  - highlight closing *\/ as error when found inside \\code, \\verbatim sections as well as \\c, \\ref sections with\r\n    unmatched brackets. \r\n","3":"  - Ignore Errors when loading from idl.\r\n  - Try and match # and \\c &c support to match what really happens. (Reported by Wu Yongwei)\r\n  - Don't go into doxygen mode for \/**\/\r\n  - Fix up syncing of brief after a \\def or similar line - character\r\n    immediately following a leading asterisk were being hilighted long.\r\n  - Try and work out a better default font for \\c\r\n  - add support for \\code \\endcode \\verbatim \\endverbatim (no contained elements) (suggested Yongwei)\r\n  - add contained support for dot (\\dot \\enddot)\r\n  - support html <!-- --> comments.\r\n  - support for params inside \\c \\ref brackets (can contain spaces?).\r\n  - highlight closing *\/ as error when found inside \\code, \\verbatim sections as well as \\c, \\ref sections with\r\n    unmatched brackets. \r\n","package":"doxygen.vim","4":"doxygen.vim","src_id":"3336","5":"3336","creation_date":"1092610657","6":"1092610657"},{"0":"5","vim_version":"6.0","1":"6.0","script_version":"1.6","2":"1.6","version_comment":" - Fix up # support.\r\n - Highlight \\\\endlink properly.\r\n - Don\\'t mark *\/ as an error where there is no brief, or @{ is used.\r\n","3":" - Fix up # support.\r\n - Highlight \\\\endlink properly.\r\n - Don\\'t mark *\/ as an error where there is no brief, or @{ is used.\r\n","package":"doxygen.vim","4":"doxygen.vim","src_id":"3312","5":"3312","creation_date":"1092168745","6":"1092168745"},{"0":"5","vim_version":"6.0","1":"6.0","script_version":"1.5","2":"1.5","version_comment":"- Make sure @c \\c and friends are equivalent for the start of a brief section.\n- Allow @c \\c and friends to cross lines. (Caveat, they can't be hard up  against a continuation '*' - it just gets tooo difficult).\n- Highlight a missing \\endlink as an error.\n- Fix multiline description without a '*' ","3":"- Make sure @c \\c and friends are equivalent for the start of a brief section.\n- Allow @c \\c and friends to cross lines. (Caveat, they can't be hard up  against a continuation '*' - it just gets tooo difficult).\n- Highlight a missing \\endlink as an error.\n- Fix multiline description without a '*' ","package":"doxygen.vim","4":"doxygen.vim","src_id":"3306","5":"3306","creation_date":"1091829671","6":"1091829671"},{"0":"5","vim_version":"6.0","1":"6.0","script_version":"1.4","2":"1.4","version_comment":"- Patches from Wu Yongwei\r\n  * Include '-' in inline \\c \\e maching.\r\n  * \\see, \\return are multiline desc.\r\n  * \\throw can now handle std::alloc (colons were confusing it)\r\n- Fixed support for <a href=> links.\r\n- Reported by Wu Yongwei\r\n  * Handle [in,out] in \\param.\r\n  * Handle non-terminating . in a brief description (eg A.B)\r\n  * allow leading asterix inside HTML marks.\r\n  * Fix up <a> link hilighting when interupted by new-lines and comment\r\n  continuations.\r\n  * Handle the case where \\c \\ref etc are used at the beginning of a 'brief'\r\n  line.\r\n- Fixed termination of multiline at start of new command.\r\n- Include John McGehee's instructions.\r\n","3":"- Patches from Wu Yongwei\r\n  * Include '-' in inline \\c \\e maching.\r\n  * \\see, \\return are multiline desc.\r\n  * \\throw can now handle std::alloc (colons were confusing it)\r\n- Fixed support for <a href=> links.\r\n- Reported by Wu Yongwei\r\n  * Handle [in,out] in \\param.\r\n  * Handle non-terminating . in a brief description (eg A.B)\r\n  * allow leading asterix inside HTML marks.\r\n  * Fix up <a> link hilighting when interupted by new-lines and comment\r\n  continuations.\r\n  * Handle the case where \\c \\ref etc are used at the beginning of a 'brief'\r\n  line.\r\n- Fixed termination of multiline at start of new command.\r\n- Include John McGehee's instructions.\r\n","package":"doxygen.vim","4":"doxygen.vim","src_id":"3295","5":"3295","creation_date":"1091481401","6":"1091481401"}]},"4":{"script_id":"4","0":"4","script_name":"ToggleCommentify.vim","1":"ToggleCommentify.vim","script_type":"utility","2":"utility","summary":"comment lines in a program","3":"comment lines in a program","description":"This is a (very) simple script to comment lines in a program. Currently supported languages are C, C++, the vim scripting language, python, and ox. Given the simplicity of the program it very easy to add support for new languages. The comments in the file should provide sufficient information on how to proceed.\r\n\r\n ","4":"This is a (very) simple script to comment lines in a program. Currently supported languages are C, C++, the vim scripting language, python, and ox. Given the simplicity of the program it very easy to add support for new languages. The comments in the file should provide sufficient information on how to proceed.\r\n\r\n ","install_details":"You can put the functions in the attachment directly into your .vimrc or in a separate file to be sourced. If you choose for the latter option add a statement such as ...\r\n\r\nexecute \"source ~\/vim\/myVimFiles\/ToggleCommentify.vim\"\r\n\r\n... to your .vimrc file\r\n\r\nTo call the functions add the following mappings in your .vimrc. \r\n \r\nmap <M-c>\t:call ToggleCommentify()<CR>j\r\nimap <M-c>\t<ESC>:call ToggleCommentify()<CR>j\r\n\r\nThe nice thing about these mapping is that you don't have to select a visual block to comment ... just keep the ALT-key pressed down and tap on 'c' as often as you need.","5":"You can put the functions in the attachment directly into your .vimrc or in a separate file to be sourced. If you choose for the latter option add a statement such as ...\r\n\r\nexecute \"source ~\/vim\/myVimFiles\/ToggleCommentify.vim\"\r\n\r\n... to your .vimrc file\r\n\r\nTo call the functions add the following mappings in your .vimrc. \r\n \r\nmap <M-c>\t:call ToggleCommentify()<CR>j\r\nimap <M-c>\t<ESC>:call ToggleCommentify()<CR>j\r\n\r\nThe nice thing about these mapping is that you don't have to select a visual block to comment ... just keep the ALT-key pressed down and tap on 'c' as often as you need.","first_name":"Vincent","6":"Vincent","last_name":"Nijs","7":"Nijs","releases":[{"0":"4","vim_version":"6.0","1":"6.0","script_version":"1.53","2":"1.53","version_comment":"Incorperated Bernhard Wagner's 12-Nov-2002 v1.52 xml changes\r\nWill make default mappings to <M-c> only if no map to <Plug>FtcTC and <M-c> is unused.\r\nMerged DLAC with this; DLAC = duplicate line and comment, simple mappings that are handy to use to save and comment a line before you mangle it. However this mangles mark z -- <Plug>FtcDlacNormal and <Plug>FtcDlacVisual; default is <S-C-c>\r\nBugfix:\tmismatched <Plug> names; This is <Plug>FtcTc (not FbmTc)\r\n","3":"Incorperated Bernhard Wagner's 12-Nov-2002 v1.52 xml changes\r\nWill make default mappings to <M-c> only if no map to <Plug>FtcTC and <M-c> is unused.\r\nMerged DLAC with this; DLAC = duplicate line and comment, simple mappings that are handy to use to save and comment a line before you mangle it. However this mangles mark z -- <Plug>FtcDlacNormal and <Plug>FtcDlacVisual; default is <S-C-c>\r\nBugfix:\tmismatched <Plug> names; This is <Plug>FtcTc (not FbmTc)\r\n","package":"FeralToggleCommentify.vim","4":"FeralToggleCommentify.vim","src_id":"1408","5":"1408","creation_date":"1037167186","6":"1037167186"},{"0":"4","vim_version":"6.0","1":"6.0","script_version":"1.52","2":"1.52","version_comment":"Added XML file type","3":"Added XML file type","package":"FeralToggleCommentify.vim","4":"FeralToggleCommentify.vim","src_id":"1404","5":"1404","creation_date":"1037116342","6":"1037116342"},{"0":"4","vim_version":"6.0","1":"6.0","script_version":"1.51","2":"1.51","version_comment":"*Hacked in eol comments and added html's <!-- --> comments.\r\n* saves cursor position\r\n* bugfix for + comment.\r\n* See file comments for more details.","3":"*Hacked in eol comments and added html's <!-- --> comments.\r\n* saves cursor position\r\n* bugfix for + comment.\r\n* See file comments for more details.","package":"FeralToggleCommentify.vim","4":"FeralToggleCommentify.vim","src_id":"1380","5":"1380","creation_date":"1036509543","6":"1036509543"},{"0":"4","vim_version":"6.0","1":"6.0","script_version":"1.3","2":"1.3","version_comment":"Added :TC, :UC, :CC to toggle, uncomment and comment. Ranges suported as is specifying the comment symbol. Previous maping of <M-c> preserved (still toggles the comment)\r\nI've made a mess but it but works quite nicely near as I can tell :) Please see the comments at the head of the file. If my changes meet your aproval I sugest renaming the file back to ToggleCommentify.vim -- only renamed it to avoid colisions and confusion. I was unable to reach Vincent via email so making my changes public here; Hope they are helpful!","3":"Added :TC, :UC, :CC to toggle, uncomment and comment. Ranges suported as is specifying the comment symbol. Previous maping of <M-c> preserved (still toggles the comment)\r\nI've made a mess but it but works quite nicely near as I can tell :) Please see the comments at the head of the file. If my changes meet your aproval I sugest renaming the file back to ToggleCommentify.vim -- only renamed it to avoid colisions and confusion. I was unable to reach Vincent via email so making my changes public here; Hope they are helpful!","package":"FeralToggleCommentify.vim","4":"FeralToggleCommentify.vim","src_id":"1033","5":"1033","creation_date":"1027242733","6":"1027242733"},{"0":"4","vim_version":"5.7","1":"5.7","script_version":"1.2","2":"1.2","version_comment":"Resolved problems with comments.","3":"Resolved problems with comments.","package":"ToggleCommentify.vim","4":"ToggleCommentify.vim","src_id":"22","5":"22","creation_date":"992085356","6":"992085356"},{"0":"4","vim_version":"5.7","1":"5.7","script_version":"1.1","2":"1.1","version_comment":"This version no longer uses 's:' (i.e., script-variables) as they are not supported in vim5.7 or vim5.8. Thanks to Rex Posadas for pointing this out to me.\r\n","3":"This version no longer uses 's:' (i.e., script-variables) as they are not supported in vim5.7 or vim5.8. Thanks to Rex Posadas for pointing this out to me.\r\n","package":"ToggleCommentify.vim","4":"ToggleCommentify.vim","src_id":"12","5":"12","creation_date":"991713847","6":"991713847"},{"0":"4","vim_version":"5.7","1":"5.7","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"ToggleCommentify.vim","4":"ToggleCommentify.vim","src_id":"5","5":"5","creation_date":"991120015","6":"991120015"}]},"3":{"script_id":"3","0":"3","script_name":"test_syntax.vim","1":"test_syntax.vim","script_type":"syntax","2":"syntax","summary":"example syntax file upload","3":"example syntax file upload","description":"Just an example of a syntax file uploaded to vim online - the actual script is empty. I just wanted to show how you can use vimonline.","4":"Just an example of a syntax file uploaded to vim online - the actual script is empty. I just wanted to show how you can use vimonline.","install_details":"Here is where I would describe how users should install the script. This is an example of a reference to a tip: vimtip #23. This is an example of a reference to a script: vimscript #24. You can also use vimtip#23 and vimscript#44 (no space).","5":"Here is where I would describe how users should install the script. This is an example of a reference to a tip: vimtip #23. This is an example of a reference to a script: vimscript #24. You can also use vimtip#23 and vimscript#44 (no space).","first_name":"Scott","6":"Scott","last_name":"Johnston","7":"Johnston","releases":[{"0":"3","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"test_syntax.vim","4":"test_syntax.vim","src_id":"4","5":"4","creation_date":"991064458","6":"991064458"}]},"2":{"script_id":"2","0":"2","script_name":"test.zip","1":"test.zip","script_type":"utility","2":"utility","summary":"example of a set of scripts zipped together","3":"example of a set of scripts zipped together","description":"Here is where I would put more details on the scripts I uploaded","4":"Here is where I would put more details on the scripts I uploaded","install_details":"Here is where I would describe how a user should install the script","5":"Here is where I would describe how a user should install the script","first_name":"Scott","6":"Scott","last_name":"Johnston","7":"Johnston","releases":[{"0":"2","vim_version":"6.0","1":"6.0","script_version":"1.2","2":"1.2","version_comment":"Here is an example of a new version of these scripts","3":"Here is an example of a new version of these scripts","package":"test.zip","4":"test.zip","src_id":"3","5":"3","creation_date":"991064245","6":"991064245"},{"0":"2","vim_version":"6.0","1":"6.0","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"test.zip","4":"test.zip","src_id":"2","5":"2","creation_date":"991064194","6":"991064194"}]},"1":{"script_id":"1","0":"1","script_name":"test.vim","1":"test.vim","script_type":"utility","2":"utility","summary":"example utility script file -- used for testing vimonline","3":"example utility script file -- used for testing vimonline","description":"This is an example of a utility script file. I added this so people could see what a script looks like in vimonline -- the file itself is empty. Originally this was just to show how people could use vimonline. Now I use it do do a final test of new code once I deploy it to production.","4":"This is an example of a utility script file. I added this so people could see what a script looks like in vimonline -- the file itself is empty. Originally this was just to show how people could use vimonline. Now I use it do do a final test of new code once I deploy it to production.","install_details":"Only an example of the install field","5":"Only an example of the install field","first_name":"Scott","6":"Scott","last_name":"Johnston","7":"Johnston","releases":[{"0":"1","vim_version":"5.7","1":"5.7","script_version":"1.0","2":"1.0","version_comment":"Initial upload","3":"Initial upload","package":"test.vim","4":"test.vim","src_id":"1","5":"1","creation_date":"991064087","6":"991064087"}]}}